diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 540f3656ce8..0710b971e74 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -25,3 +25,7 @@
 /_docs/_api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item.md @braze-inc/ingestion @lydia-xie @braze-inc/docs-team
 /_docs/_api/endpoints/messaging/send_messages/post_send_triggered_campaigns.md @braze-inc/ingestion @lydia-xie @braze-inc/docs-team
 /_docs/_api/endpoints/messaging/send_messages/post_send_triggered_canvases.md @braze-inc/ingestion @lydia-xie @braze-inc/docs-team
+
+# Currents Event Docs: Currents owns event payload auto-generation templates for these endpoints, and are codeowners to be notified when changes are made so that the templates can be kept in-sync.
+/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md @braze-inc/currents @braze-inc/docs-team
+/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md @braze-inc/currents @braze-inc/docs-team
diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE
index 66a7e5b67a2..1fdcc73f241 100644
--- a/.github/PULL_REQUEST_TEMPLATE
+++ b/.github/PULL_REQUEST_TEMPLATE
@@ -10,7 +10,7 @@ _Your reason here..._
 ### Related PRs, issues, or features (optional)
 <!--
 For related GitHub issues and features, add "Fixes #ISSUE_NUMBER".
-For Jira tickets, add the ticket number and a link to the ticket, like: [BD-NUMBER](LINK).
+For Jira tickets, add the ticket number and a link to the ticket, like: [BD-NUMBER](https://jira.braze.com/browse/BD-NUMBER).
 -->
 - N/A
 
diff --git a/Gemfile.lock b/Gemfile.lock
index aa0e23bb46d..b684d5b8c97 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -33,31 +33,31 @@ GIT
 GEM
   remote: https://rubygems.org/
   specs:
-    addressable (2.8.6)
-      public_suffix (>= 2.0.2, < 6.0)
+    addressable (2.8.7)
+      public_suffix (>= 2.0.2, < 7.0)
     algoliasearch (1.26.1)
       httpclient (~> 2.8, >= 2.8.3)
       json (>= 1.5.1)
     base64 (0.2.0)
     bigdecimal (3.1.8)
     colorator (1.1.0)
-    concurrent-ruby (1.3.1)
+    concurrent-ruby (1.3.4)
     em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
     eventmachine (1.2.7)
     execjs (2.9.1)
-    ffi (1.16.3)
+    ffi (1.17.0)
     filesize (0.2.0)
     forwardable-extended (2.6.0)
-    google-protobuf (4.27.0)
+    google-protobuf (4.28.3)
       bigdecimal
       rake (>= 13)
     http_parser.rb (0.8.0)
     httpclient (2.8.3)
-    i18n (1.14.5)
+    i18n (1.14.6)
       concurrent-ruby (~> 1.0)
-    jekyll (4.3.3)
+    jekyll (4.3.4)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
@@ -100,8 +100,8 @@ GEM
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
     progressbar (1.13.0)
-    public_suffix (5.0.5)
-    puma (6.4.2)
+    public_suffix (6.0.1)
+    puma (6.4.3)
       nio4r (~> 2.0)
     racc (1.8.0)
     rack (3.0.11)
@@ -123,13 +123,12 @@ GEM
     rb-fsevent (0.11.2)
     rb-inotify (0.11.1)
       ffi (~> 1.0)
-    rexml (3.3.2)
-      strscan
-    rouge (4.2.1)
+    rexml (3.3.9)
+    rouge (4.4.0)
     ruby2_keywords (0.0.5)
     safe_yaml (1.0.5)
-    sass-embedded (1.77.3)
-      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.80.4)
+      google-protobuf (~> 4.28)
       rake (>= 13)
     sassc (2.4.0)
       ffi (~> 1.9)
@@ -139,15 +138,14 @@ GEM
       rack-protection (= 4.0.0)
       rack-session (>= 2.0.0, < 3)
       tilt (~> 2.0)
-    strscan (3.1.0)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)
     tilt (2.3.0)
     uglifier (4.2.0)
       execjs (>= 0.3.0, < 3)
-    unicode-display_width (2.5.0)
+    unicode-display_width (2.6.0)
     verbal_expressions (0.1.5)
-    webrick (1.8.1)
+    webrick (1.8.2)
 
 PLATFORMS
   ruby
diff --git a/_config.yml b/_config.yml
index d209de6628c..717851feb2a 100644
--- a/_config.yml
+++ b/_config.yml
@@ -242,26 +242,22 @@ algolia:
   nodes_to_index: "p,h1,h2,h3,h4,h5,h6,tr,pre,details"
   max_record_size: 20000
   settings:
+    searchableAttributes:
+      - article_title
+      - nav_title
+      - unordered(headings)
+      - unordered(content)
+      - unordered(description)
     attributesForFaceting:
       - searchable(article_title)
-      - searchable(collection)
-      - searchable(type)
       - searchable(category)
+      - searchable(channel)
+      - searchable(collection)
+      - searchable(headings)
+      - searchable(nav_title)
       - searchable(platform)
+      - searchable(type)
       - searchable(url)
-      - searchable(nav_title)
-      - searchable(channel)
-    searchableAttributes:
-      - article_title
-      - description
-      - search_rank
-      - nav_title
-      - url
-      - Path_01
-      - collection,tags
-      - unordered(content)
-      - unordered(platform)
-      - channel
     customRanking:
       - desc(article_title)
       - desc(custom_ranking.heading)
diff --git a/_docs/_api/api_limits.md b/_docs/_api/api_limits.md
index ccdfc5aab1c..f3d202c624f 100644
--- a/_docs/_api/api_limits.md
+++ b/_docs/_api/api_limits.md
@@ -9,7 +9,7 @@ page_type: reference
 
 # Rate limits
 
-> The Braze API infrastructure is designed to handle high volumes of data across our customer base. To this end, we enforce API rate limits per workspace. 
+> The Braze API infrastructure is designed to handle high volumes of data across our customer base. To this end, we enforce API rate limits per workspace.
 
 A rate limit is the number of requests the API can receive in a given time period. Many load-based denial-of-service incidents in large systems are unintentional—caused by errors in software or configurations—not malicious attacks. Rate limits check that such errors don't deprive our customers of Braze API resources. If too many requests are sent in a given time frame, you may see error responses with a status code of `429`, which indicates the rate limit has been hit.
 
@@ -27,8 +27,8 @@ Requests not listed in this table share a total default rate limit of 250,000 re
 
 | Request Type                                                                                                                                                                                                                                           | Default API Rate Limit                                                                                                                                                                     |
 | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [`/users/track`][10]                                                                                                                                                                                                                                   | **Requests:** 50,000 requests per minute.<br><br>**Batching:** 75 events, 75 purchases, and 75 attributes per API request. See [Batching User Track requests](#batch-user-track) for more.<br><br>**Limits for Monthly Active Users CY 24-25:** see [Monthly Active Users CY 24-25 limits]({{site.baseurl}}/api/endpoints/user_data/post_user_track/#monthly-active-users-cy-24-25) |
-| [`/users/export/ids`][11]                                                                                                                                                                                                                              | 250 requests per minute.                                                                                                                                                                   |
+| [`/users/track`][10]                                                                                                                                                                                                                                   | **Requests:** 3,000 requests per three seconds.<br><br>**Batching:** 75 events, 75 purchases, and 75 attributes per API request. See [Batching User Track requests](#batch-user-track) for more.<br><br>**Limits for Monthly Active Users CY 24-25:** see [Monthly Active Users CY 24-25 limits]({{site.baseurl}}/api/endpoints/user_data/post_user_track/#monthly-active-users-cy-24-25) |
+| [`/users/export/ids`][11]                                                                                                                                                                                                                              | **If you onboarded on or after August 22, 2024:** 250 requests per minute. <br><br> **If you onboarded before August 22, 2024:** 2,500 requests per minute.                                                                                                                                                                   |
 | [`/users/delete`][12]<br>[`/users/alias/new`][13]<br>[`/users/alias/update`][45]<br>[`/users/identify`][14]<br>[`/users/merge`][44]                                                                                                                    | 20,000 requests per minute, shared between the endpoints.                                                                                                                                  |
 | [`/users/external_id/rename`][20]                                                                                                                                                                                                                      | 1,000 requests per minute.                                                                                                                                                                 |
 | [`/users/external_id/remove`][21]                                                                                                                                                                                                                      | 1,000 requests per minute.                                                                                                                                                                 |
@@ -44,7 +44,7 @@ Requests not listed in this table share a total default rate limit of 250,000 re
 | [`/catalogs/{catalog_name}/items`][34]<br>[`/catalogs/{catalog_name}/items`][35]<br>[`/catalogs/{catalog_name}/items`][36]                                                                                                                             | 16,000 requests per minute shared between the endpoints.                                                                                                                                   |
 | [`/catalogs/{catalog_name}/items/{item_id}`][37]<br>[`/catalogs/{catalog_name}/items/{item_id}`][38]<br>[`/catalogs/{catalog_name}/items`][39]<br>[`/catalogs/{catalog_name}/items/{item_id}`][40]<br>[`/catalogs/{catalog_name}/items/{item_id}`][41] | 50 requests per minute shared between the endpoints.                                                                                                                                       |
 | [`/scim/v2/Users/{id}`][22]<br>[`/scim/v2/Users?filter={userName@example.com}`][43]<br>[`/scim/v2/Users/{id}`][25]<br>[`/scim/v2/Users/{id}}`][24]<br>[`/scim/v2/Users/`][23]                                                                          | 5,000 requests per day, per company, shared between the endpoints.                                                                                                                         |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 <!-- Add during CDI endpoints GA
 | [`/cdi/integrations`][46] | 50 requests per minute. |
@@ -64,7 +64,7 @@ REST API rate limit increases are considered based on need for customers who are
 
 Each `/users/track` request can contain up to 75 event objects, 75 attribute objects, and 75 purchase objects. Each object (event, attribute, and purchase arrays) can update one user each. In total, this means a maximum of 225 users can be updated in a single call. In addition, a single user profile can be updated by multiple objects.
 
-Requests made to this endpoint will generally begin processing in this order: 
+Requests made to this endpoint will generally begin processing in this order:
 
 1. Attributes
 2. Events
@@ -111,10 +111,14 @@ Every single API request sent to Braze returns the following information in the
 | `X-RateLimit-Limit`     | The maximum number of requests that you can make in a specified interval (your rate limit). |
 | `X-RateLimit-Remaining` | The number of requests remaining in the current rate limit window.                          |
 | `X-RateLimit-Reset`     | The time at which the current rate limit window resets in UTC epoch seconds.                |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 This information is intentionally included in the header of the response to the API request rather than the Braze dashboard. This allows your system to better react in real time as you're interacting with our API. For example, if the `X-RateLimit-Remaining` value drops below a certain threshold, you might want to slow sending to make sure all transactional emails go out. Or, if it reaches zero, you might want to pause all sending until the time specified in `X-RateLimit-Reset` elapses.
 
+{% alert note %}
+HTTP headers will be returned in all lowercase characters. This behavior aligns with the HTTP/2 protocol that mandates all header field names must be lowercase. This differs from HTTP/1.X where header names were case-insensitive but were commonly written in various capitalizations.
+{% endalert %}
+
 If you have questions about API limits, contact your customer success manager or open a [support ticket][support].
 
 ### Optimal delay between endpoints
diff --git a/_docs/_api/basics.md b/_docs/_api/basics.md
index 982ca5b3fbe..1ad58bc22b9 100644
--- a/_docs/_api/basics.md
+++ b/_docs/_api/basics.md
@@ -26,7 +26,7 @@ alias: /api/api_key/
 | [Subscription groups]({{site.baseurl}}/api/endpoints/subscription_groups/) | List and update both SMS and email subscription groups stored in the Braze dashboard. |
 | [Templates]({{site.baseurl}}/api/endpoints/templates/)                     | Create and update templates for email messaging and Content Blocks.                   |
 | [User data]({{site.baseurl}}/api/endpoints/user_data/)                     | Identify, track, and manage your users.                                               |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## API definitions
 
@@ -54,13 +54,13 @@ For SDK integration, use the [SDK endpoint]({{site.baseurl}}/user_guide/administ
 |US-08| `https://dashboard-08.braze.com` | `https://rest.iad-08.braze.com` | `sdk.iad-08.braze.com` |
 |EU-01| `https://dashboard-01.braze.eu` | `https://rest.fra-01.braze.eu` | `sdk.fra-01.braze.eu` |
 |EU-02| `https://dashboard-02.braze.eu` | `https://rest.fra-02.braze.eu` | `sdk.fra-02.braze.eu` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ### API limits
 
 For most APIs, Braze has a default rate limit of 250,000 requests per hour. However, certain request types have their own rate limit applied to better handle high volumes of data across our customer base. For details, refer to [API rate limits]({{site.baseurl}}/api/api_limits/)
 
-### User IDs 
+### User IDs
 
 - **External user ID**: The `external_id` serves as a unique user identifier for whom you are submitting data. This identifier should be the same as the one you set in the Braze SDK in order to avoid creating multiple profiles for the same user.
 - **Braze user ID**: `braze_id` serves as a unique user identifier that is set by Braze. This identifier can be used to delete users through the REST API in addition to external_ids.
@@ -110,18 +110,18 @@ API key permissions are permissions you can assign a user or group to limit thei
 
 | Permission | Endpoint | Description |
 |---|---|---|
-| `users.track` | [`/users/track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) | Record user attributes, custom events, and purchases. | 
+| `users.track` | [`/users/track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) | Record user attributes, custom events, and purchases. |
 | `users.delete` | [`/users/delete`]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/) | Delete any user. |
 | `users.alias.new` | [`/users/alias/new`]({{site.baseurl}}/api/endpoints/user_data/post_user_alias/) |Create a new alias for an existing user. |
 | `users.identify` | [`/users/identify`]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/) |Identify an alias-only user with an external ID. |
 | `users.export.ids` | [`/users/export/ids`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/) |Query for user profile information by user ID. |
-| `users.export.segment` | [`/users/export/segment`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/) |Query for user profile information by segment. | 
+| `users.export.segment` | [`/users/export/segment`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/) |Query for user profile information by segment. |
 | `users.merge` | [`/users/merge`]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/) | Merges two existing users into each other. |
 | `users.external_ids.rename` | [`/users/external_ids/rename`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_rename/) | Change the external ID for an existing user. |
 | `users.external_ids.remove` | [`/users/external_ids/remove`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_remove/) | Remove the external ID for an existing user. |
 | `users.alias.update` | [`/users/alias/update`]({{site.baseurl}}/api/endpoints/user_data/post_users_alias_update/) | Update an alias for an existing user. |
 | `users.export.global_control_group` | [`/users/export/global_control_group`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_global_control_group/) | Query for user profile information in the Global Control Group. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
  {% endtab %}
  {% tab Email %}
@@ -134,7 +134,7 @@ API key permissions are permissions you can assign a user or group to limit thei
 | `email.bounce.remove` | [`/email/bounce/remove`]({{site.baseurl}}/api/endpoints/email/post_remove_hard_bounces/) | Remove email addresses from your hard bounce list. |
 | `email.spam.remove` | [`/email/spam/remove`]({{site.baseurl}}/api/endpoints/email/post_remove_spam/) | Remove email addresses from your spam list. |
 | `email.blacklist` | [`/email/blacklist`]({{site.baseurl}}/api/endpoints/email/post_blacklist/) | Blocklist email addresses. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Messages %}
@@ -147,7 +147,7 @@ API key permissions are permissions you can assign a user or group to limit thei
 | `messages.schedule.delete` | [`/messages/schedule/delete`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages/) | Delete a scheduled message. |
 | `messages.schedule_broadcasts` | [`/messages/scheduled_broadcasts`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/get_messages_scheduled/) | Query all scheduled broadcast messages. |
 | `messages.live_activity.update` | [`/messages/live_activity/update`]({{site.baseurl}}/api/endpoints/messaging/live_activity/update/) | Update an iOS Live Activity. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Campaigns %}
@@ -165,7 +165,7 @@ API key permissions are permissions you can assign a user or group to limit thei
 | `sends.id.create` | [`/sends/id/create`]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_create_send_ids/) | Create send ID for message blast tracking. |
 | `campaigns.url_info.details` | [`/campaigns/url_info/details`]({{site.baseurl}}) | Query for URL details of a specific message variation within a campaign. |
 | `transactional.send` | [`/transactional/v1/campaigns/{campaign_id}/send`]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_transactional_message/) | Allows for ability to send transactional messaging using the Transactional messaging endpoint. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Canvas %}
@@ -181,7 +181,7 @@ API key permissions are permissions you can assign a user or group to limit thei
 | `canvas.details` | [`/canvas/details`]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/) | Query for details of a specific Canvas. |
 | `canvas.data_summary` | [`/canvas/data_summary`]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_analytics_summary/) | Query for rollups of Canvas analytics over a time range. |
 | `canvas.url_info.details` | [`/canvas/url_info/details`]({{site.baseurl}}/get_canvas_link_alias/) | Query for URL details of a specific message variation within a Canvas step. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Segments %}
@@ -191,7 +191,7 @@ API key permissions are permissions you can assign a user or group to limit thei
 | `segments.list` | [`/segments/list`]({{site.baseurl}}/api/endpoints/export/segments/get_segment/) | Query for a list of segments. |
 | `segments.data_series` | [`/segments/data_series`]({{site.baseurl}}/api/endpoints/export/segments/get_segment_analytics/) | Query for segment analytics over a time range. |
 | `segments.details` | [`/segments/details`]({{site.baseurl}}/api/endpoints/export/segments/get_segment_details/) | Query for details of a specific segment. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Purchases %}
@@ -201,7 +201,7 @@ API key permissions are permissions you can assign a user or group to limit thei
 | `purchases.product_list` | [`/purchases/product_list`]({{site.baseurl}}/api/endpoints/export/purchases/get_list_product_id/) | Query for a list of products purchased in your app. |
 | `purchases.revenue_series` | [`/purchases/revenue_series`]({{site.baseurl}}/api/endpoints/export/purchases/get_revenue_series/) | Query for total money spent per day in your app over a time range. |
 | `purchases.quantity_series` | [`/purchases/quantity_series`]({{site.baseurl}}/api/endpoints/export/purchases/get_number_of_purchases/) | Query for the total number of purchases per day in your app over a time range. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Events %}
@@ -210,7 +210,7 @@ API key permissions are permissions you can assign a user or group to limit thei
 |---|---|---|
 | `events.list` | [`/events/list`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events/) | Query for a list of custom events. |
 | `events.data_series` | [`/events/data_series`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events_analytics/) | Query occurrences of a custom event over a time range. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab News Feed %}
@@ -224,7 +224,7 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 | `feed.list` | [`/feed/list`]({{site.baseurl}}/api/endpoints/export/news_feed/get_news_feed_cards/) | Query for a list of News Feed cards. |
 | `feed.data_series` | [`/feed/data_series`]({{site.baseurl}}/api/endpoints/export/news_feed/get_news_feed_card_analytics/) | Query for News Feed analytics over a time range. |
 | `feed.details` | [`/feed/details`]({{site.baseurl}}/api/endpoints/export/news_feed/get_news_feed_card_details/) | Query for details of a specific News Feed. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Sessions %}
@@ -232,7 +232,7 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 | Permission | Endpoint | Description |
 |---|---|---|
 | `sessions.data_series` | [`/sessions/data_series`]({{site.baseurl}}/api/endpoints/export/sessions/get_sessions_analytics/) | Query for sessions per day over a time range. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab KPIs %}
@@ -243,7 +243,7 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 | `kpi.mau.data_series` | [`/kpi/mau/data_series`]({{site.baseurl}}/api/endpoints/export/kpi/get_kpi_mau_30_days/) | Query for total unique active users over a 30-day rolling window over a time range. |
 | `kpi.new_users.data_series` | [`/kpi/new_users/data_series`]({{site.baseurl}}/api/endpoints/export/kpi/get_kpi_daily_new_users_date/) | Query for new users per day over a time range. |
 | `kpi.uninstalls.data_series` | [`/kpi/uninstalls/data_series`]({{site.baseurl}}/api/endpoints/export/kpi/get_kpi_uninstalls_date/) | Query for app uninstalls per day over a time range. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Templates %}
@@ -254,7 +254,7 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 | `templates.email.info` | [`/templates/email/info`]({{site.baseurl}}/api/endpoints/templates/email_templates/get_see_email_template_information/) | Query for information of a specific template. |
 | `templates.email.list` | [`/templates/email/list`]({{site.baseurl}}/api/endpoints/templates/email_templates/get_list_email_templates/) | Query for a list of email templates. |
 | `templates.email.update` | [`/templates/email/update`]({{site.baseurl}}/api/endpoints/templates/email_templates/post_update_email_template/) | Update an email template stored on the dashboard. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab SSO %}
@@ -262,7 +262,7 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 | Permission | Description |
 |---|---|---|
 | `sso.saml.login` | Set up identity provider-initiated login. For more information, refer to [Service Provider (SP) initiated login]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Content Blocks %}
@@ -273,7 +273,7 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 | `content_blocks.list` | [`/content_blocks/list`]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks/) | Query for a list of Content Blocks. |
 | `content_blocks.create` | [`/content_blocks/create`]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/post_create_email_content_block/) | Create a new Content Block on the dashboard. |
 | `content_blocks.update` | [`/content_blocks_update`]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/post_update_content_block/) | Update an existing Content Block on the dashboard. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Preference Center %}
@@ -284,7 +284,7 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 | `preference_center.list` | [`/preference_center/v1/list`]({{site.baseurl}}/api/endpoints/preference_center/get_list_preference_center/) | List preference centers. |
 | `preference_center.update` | [`/preference_center/v1`]({{site.baseurl}}/api/endpoints/preference_center/post_create_preference_center)<br><br>[`/preference_center/v1/{preferenceCenterExternalID}`]({{site.baseurl}}/api/endpoints/preference_center/put_update_preference_center/) | Create or update a preference center. |
 | `preference_center.user.get` | [`/preference_center/v1/{preferenceCenterExternalId}/url/{userId}`]({{site.baseurl}}/api/endpoints/preference_center/get_create_url_preference_center) | Get a preference center link for a user. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Subscription %}
@@ -294,7 +294,7 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 | `subscription.status.set` | [`/subscription/status/set`]({{site.baseurl}}/api/endpoints/subscription_groups/post_update_user_subscription_group_status/) | Set subscription group status. |
 | `subscription.status.get` | [`/subscription/status/get`]({{site.baseurl}}/api/endpoints/subscription_groups/get_list_user_subscription_group_status/) | Get subscription group status. |
 | `subscription.groups.get` | [`/subscription/user/status`]({{site.baseurl}}/api/endpoints/subscription_groups/get_list_user_subscription_groups/) | Get status of subscription groups that specific users are explicitly subscribed and unsubscribed to. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab SMS %}
@@ -303,7 +303,7 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 |---|---|---|
 | `sms.invalid_phone_numbers` | [`/sms/invalid_phone_numbers`]({{site.baseurl}}/api/endpoints/sms/get_query_invalid_numbers/) | Query for invalid phone numbers. |
 | `sms.invalid_phone_numbers.remove` | [`/sms/invalid_phone_numbers/remove`]({{site.baseurl}}/api/endpoints/sms/post_remove_invalid_numbers/) | Remove the invalid phone number flag from users. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Catalogs %}
@@ -323,14 +323,14 @@ News Feed is being deprecated. Braze recommends that customers who use our News
 | `catalogs.delete` | [`/catalogs/{catalog_name}`]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/delete_catalog/) | Delete a catalog. |
 | `catalogs.get_items` | [`/catalogs/{catalog_name}/items`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk/) | Get items preview from an existing catalog. |
 | `catalogs.replace_items` | [`/catalogs/{catalog_name}/items`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items/) | Replace items in an existing catalog. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
 
 ### Managing REST API keys
 
-You can view details for or delete existing REST API keys from **Settings** > **APIs and Identifiers** > **API Keys** tab. Note that REST API keys cannot be edited after they're created. 
+You can view details for or delete existing REST API keys from **Settings** > **APIs and Identifiers** > **API Keys** tab. Note that REST API keys cannot be edited after they're created.
 
 The **API Keys** tab includes the following information for each key:
 
@@ -341,7 +341,7 @@ The **API Keys** tab includes the following information for each key:
 | Created By   | The email address of the user who created the key. This field will show as "N/A" for keys created before June 2023. |
 | Date Created | The date this key was created.                                                                                      |
 | Last Seen    | The date this key was last used. This field will show as "N/A" for keys that have never been used.                  |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 To view the details of an API key, hover over the key and select <i class="fa-solid fa-eye" alt="View"></i> **View**. This includes all the permissions this key has, whitelisted IPs (if any), and if this key is opted into Braze IP whitelisting.
 
@@ -357,7 +357,7 @@ API keys are used to authenticate an API call. When you create a new REST API ke
 
 Given that REST API keys allow access to potentially sensitive REST API endpoints, secure these keys and only share them with trusted partners. They should never be publicly exposed. For example, do not use this key to make AJAX calls from your website or expose it in any other public manner.
 
-A good security practice is to assign a user only as much access as is necessary to complete their job: this principle can also be applied to API keys by assigning permissions to each key. These permissions give you better security and control over the different areas of your account. 
+A good security practice is to assign a user only as much access as is necessary to complete their job: this principle can also be applied to API keys by assigning permissions to each key. These permissions give you better security and control over the different areas of your account.
 
 {% alert warning %}
 Given that REST API keys allow access to potentially sensitive REST API endpoints, make sure they are stored and used securely. For example, do not use this key to make AJAX calls from your website or expose it in any other public manner.
@@ -367,7 +367,7 @@ If accidental exposure of a key occurs, it can be deleted from the Developer Con
 
 ### API IP allowlisting
 
-For additional security, you can specify a list of IP addresses and subnets which are allowed to make REST API requests for a given REST API key. This is referred to as allowlisting, or whitelisting. To allow specific IP addresses or subnets, add them to the **Whitelist IPs** section when creating a new REST API key: 
+For additional security, you can specify a list of IP addresses and subnets which are allowed to make REST API requests for a given REST API key. This is referred to as allowlisting, or whitelisting. To allow specific IP addresses or subnets, add them to the **Whitelist IPs** section when creating a new REST API key:
 
 ![Option to allowlist IPs when creating an API key.][26]
 
diff --git a/_docs/_api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field.md b/_docs/_api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field.md
index f1d2fe1148e..d13f53e4b28 100644
--- a/_docs/_api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field.md
+++ b/_docs/_api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field.md
@@ -34,7 +34,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | -------------- | -------- | --------- | -------------------------- |
 | `catalog_name` | Required | String    | Name of the catalog.       |
 | `field_name`   | Required | String    | Name of the catalog field. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -80,7 +80,7 @@ The status code `404` could return the following response body. Refer to [Troubl
 }
 ```
 
-## Troubleshooting 
+## Troubleshooting
 
 The following table lists possible returned errors and their associated troubleshooting steps.
 
@@ -90,6 +90,6 @@ The following table lists possible returned errors and their associated troubles
 | `field-referenced-by-selection` | Check that the catalog field is currently in use by a selection. |
 | `field-is-inventory`            | Check that the catalog field is used as an inventory field.      |
 | `invalid-field-name`            | Check that the catalog field name is valid.                      |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields.md b/_docs/_api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields.md
index 0dcaa209505..7fad8bae6da 100644
--- a/_docs/_api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields.md
+++ b/_docs/_api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields.md
@@ -33,14 +33,14 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter      | Required | Data Type | Description          |
 | -------------- | -------- | --------- | -------------------- |
 | `catalog_name` | Required | String    | Name of the catalog. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
 | Parameter | Required | Data Type | Description                                                                                                  |
 | --------- | -------- | --------- | ------------------------------------------------------------------------------------------------------------ |
 | `fields`  | Required | Array     | An array that contains field objects. The fields objects should contain the name and type of the new fields. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example Request
 
@@ -117,6 +117,6 @@ The following table lists possible returned errors and their associated troubles
 | `company-size-limit-already-reached` | The catalog storage size limit is reached.                                                             |
 | `request-includes-too-many-fields`   | Each request can support up to 50 new fields.                                                          |
 | `catalog-exceeds-fields-limit`       | Catalog cannot have more than 500 fields.                                                              |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk.md b/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk.md
index 51d5a72c7b3..04e9ee0514d 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk.md
@@ -15,7 +15,7 @@ description: "This article outlines details about the Delete multiple catalog it
 /catalogs/{catalog_name}/items
 {% endapimethod %}
 
-> Use this endpoint to delete multiple items in your catalog. 
+> Use this endpoint to delete multiple items in your catalog.
 
 Each request can support up to 50 items. This endpoint is asynchronous.
 
@@ -34,14 +34,14 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `items` | Required | Array | An array that contains item objects. The item objects should contain an `id` referencing the items Braze should delete. Up to 50 item objects are allowed per request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -103,6 +103,6 @@ The following table lists possible returned errors and their associated troubles
 | `items-missing-ids` | There are items that do not have item IDs. Check that each item has an item ID. |
 | `invalid-ids` | Item IDs can only include letters, numbers, hyphens, and underscores. |
 | `request-includes-too-many-items` | Your request has too many items. The item limit per request is 50. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk.md b/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk.md
index 1cfbf9617ab..096e674ef5a 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk.md
@@ -35,14 +35,14 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `items` | Required | Array | An array that contains item objects. The item objects should contain fields that exist in the catalog. Up to 50 item objects are allowed per request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -143,6 +143,6 @@ The following table lists possible returned errors and their associated troubles
 | `request-includes-too-many-items` | Your request has too many items. The item limit per request is 50. |
 | `too-deep-nesting-in-value-object` | Item objects can't have more than 50 levels of nesting. |
 | `unable-to-coerce-value` | Item types can't be converted. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk.md b/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk.md
index 40539155b2e..89641c0298f 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk.md
@@ -15,7 +15,7 @@ description: "This article outlines details about the Create multiple catalog it
 /catalogs/{catalog_name}/items
 {% endapimethod %}
 
-> Use this endpoint to create multiple items in your catalog. 
+> Use this endpoint to create multiple items in your catalog.
 
 Each request can support up to 50 items. This endpoint is asynchronous.
 
@@ -34,14 +34,14 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `items` | Required | Array | An array that contains item objects. The item objects should contain all of the fields in the catalog. Up to 50 item objects are allowed per request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -161,6 +161,6 @@ The following table lists possible returned errors and their associated troubles
 | `request-includes-too-many-items` | Your request has too many items. The item limit per request is 50. |
 | `too-deep-nesting-in-value-object` | Item objects can't have more than 50 levels of nesting. |
 | `unable-to-coerce-value` | Item types can't be converted. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items.md b/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items.md
index c1374947f88..2b70dc7e65c 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items.md
@@ -15,7 +15,7 @@ description: "This article outlines details about the Update multiple catalog it
 /catalogs/{catalog_name}/items
 {% endapimethod %}
 
-> Use this endpoint to update multiple items in your catalog. 
+> Use this endpoint to update multiple items in your catalog.
 
 If a catalog item doesn't exist, this endpoint will create the item in your catalog. Each request can support up to 50 catalog items. This endpoint is asynchronous.
 
@@ -34,14 +34,14 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `items` | Required | Array | An array that contains item objects. Each object must have an ID. The item objects should contain fields that exist in the catalog. Up to 50 item objects are allowed per request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -120,7 +120,7 @@ The following table lists possible returned errors and their associated troubles
 
 | Error | Troubleshooting |
 | --- | --- |
-| `catalog-not-found` | Check that the catalog name is valid. | 
+| `catalog-not-found` | Check that the catalog name is valid. |
 | `ids-not-string` | Confirm that each item ID is a string. |
 | `ids-not-unique` | Check that each item ID is unique. |
 | `ids-too-large` | Character limit for each item ID is 250 characters. |
@@ -133,6 +133,6 @@ The following table lists possible returned errors and their associated troubles
 | `too-deep-nesting-in-value-object` | Item objects can't have more than 50 levels of nesting. |
 | `request-includes-too-many-items` | Your request has too many items. The item limit per request is 50. |
 | `unable-to-coerce-value` | Item types can't be converted. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item.md b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item.md
index f0083e015a0..eb965155f1f 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item.md
@@ -15,7 +15,7 @@ description: "This article outlines details about the Delete catalog item Braze
 /catalogs/{catalog_name}/items/{item_id}
 {% endapimethod %}
 
-> Use this endpoint to delete an item in your catalog. 
+> Use this endpoint to delete an item in your catalog.
 
 {% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#0dcce797-1346-472f-9384-082f14541689 {% endapiref %}
 
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
 | `item_id` | Required | String | The ID of the catalog item. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
@@ -92,6 +92,6 @@ The following table lists possible returned errors and their associated troubles
 | `arbitrary-error` | An arbitrary error occurred. Please try again or contact [Support]({{site.baseurl}}/support_contact/). |
 | `catalog-not-found` | Check that the catalog name is valid. |
 | `item-not-found` | Check that the item to be deleted exists in your catalog. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details.md b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details.md
index c379a4b64b2..adc861d6599 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details.md
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
 | `item_id` | Required | String | The ID of the catalog item. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
@@ -102,6 +102,6 @@ The following table lists possible returned errors and their associated troubles
 | --- | --- |
 | `catalog-not-found` | Check that the catalog name is valid. |
 | `item-not-found` | Check that the item is in the catalog. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk.md b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk.md
index 90752a62819..620fb809905 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk.md
@@ -32,7 +32,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Query parameters
 
@@ -41,7 +41,7 @@ Note that each call to this endpoint will return 50 items. For a catalog with mo
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `cursor` | Optional | String | Determines the pagination of the catalog items. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
@@ -146,6 +146,6 @@ The following table lists possible returned errors and their associated troubles
 | --- | --- |
 | `catalog-not-found` | Check that the catalog name is valid. |
 | `invalid-cursor` | Check that your `cursor` is valid. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item.md b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item.md
index f57f1d88ed1..37a9b7a23cf 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item.md
@@ -33,14 +33,14 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
 | `item_id` | Required | String | The ID of the catalog item. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `items` | Required | Array | An array that contains item objects. The item objects should contain fields that exist in the catalog except for the `id` field. Only one item object is allowed per request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -132,6 +132,6 @@ The following table lists possible returned errors and their associated troubles
 | `request-includes-too-many-items` | You can only edit one catalog item per request. |
 | `too-deep-nesting-in-value-object` | Item objects can't have more than 50 levels of nesting. |
 | `unable-to-coerce-value` | Item types can't be converted. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item.md b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item.md
index a92aae57099..230c2ba85d2 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item.md
@@ -33,14 +33,14 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
 | `item_id` | Required | String | The ID of the catalog item. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `items` | Required | Array | An array that contains item objects. The item objects should contain all of the fields in the catalog except for the `id` field. Only one item object is allowed per request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example Request
 
@@ -121,11 +121,11 @@ The following table lists possible returned errors and their associated troubles
 | `invalid-fields` | Confirm that all fields you are sending in the API request already exist in the catalog. This is not related to the ID field mentioned in the error. |
 | `invalid-keys-in-value-object` | Item object keys can't include `.` or `$`. |
 | `item-already-exists` | The item already exists in the catalog. |
-| `item-array-invalid` | `items` must be an array of objects. | 
+| `item-array-invalid` | `items` must be an array of objects. |
 | `items-too-large` | Character limit for each item is 5,000 characters. |
 | `request-includes-too-many-items` | You can only create one catalog item per request. |
 | `too-deep-nesting-in-value-object` | Item objects can't have more than 50 levels of nesting. |
 | `unable-to-coerce-value` | Item types can't be converted. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item.md b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item.md
index 8c750f88494..951cf58bed7 100644
--- a/_docs/_api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item.md
+++ b/_docs/_api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item.md
@@ -15,7 +15,7 @@ description: "This article outlines details about the Update catalog item Braze
 /catalogs/{catalog_name}/items/{item_id}
 {% endapimethod %}
 
-> Use this endpoint to update an item in your catalog. 
+> Use this endpoint to update an item in your catalog.
 
 If the `item_id` isn't found, this endpoint will create the item in your catalog. This endpoint is synchronous.
 
@@ -35,14 +35,14 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
 | `item_id` | Required | String | The ID of the catalog item. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `items` | Required | Array | An array that contains item objects. The item objects should contain fields that exist in the catalog except for the `id` field. Only one item object is allowed per request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -120,11 +120,11 @@ The following table lists possible returned errors and their associated troubles
 | `invalid-fields` | Confirm that all fields you are sending in the API request already exist in the catalog. This is not related to the ID field mentioned in the error. |
 | `invalid-keys-in-value-object` | Item object keys can't include `.` or `$`. |
 | `item-already-exists` | The item already exists in the catalog. |
-| `item-array-invalid` | `items` must be an array of objects. | 
+| `item-array-invalid` | `items` must be an array of objects. |
 | `items-too-large` | Character limit for each item is 5,000 characters. |
 | `request-includes-too-many-items` | You can only create one catalog item per request. |
 | `too-deep-nesting-in-value-object` | Item objects can't have more than 50 levels of nesting. |
 | `unable-to-coerce-value` | Item types can't be converted. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_management/synchronous/delete_catalog.md b/_docs/_api/endpoints/catalogs/catalog_management/synchronous/delete_catalog.md
index ca8e790ebef..69009966cb0 100644
--- a/_docs/_api/endpoints/catalogs/catalog_management/synchronous/delete_catalog.md
+++ b/_docs/_api/endpoints/catalogs/catalog_management/synchronous/delete_catalog.md
@@ -32,7 +32,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `catalog_name` | Required | String | Name of the catalog. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -78,13 +78,13 @@ The status code `404` could return the following response body. Refer to [Troubl
 }
 ```
 
-## Troubleshooting 
+## Troubleshooting
 
 The following table lists possible returned errors and their associated troubleshooting steps.
 
 | Error | Troubleshooting |
 | --- | --- |
 | `catalog-not-found` | Check that the catalog name is valid. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog.md b/_docs/_api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog.md
index c423edd80ee..2ff3b6f1291 100644
--- a/_docs/_api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog.md
+++ b/_docs/_api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog.md
@@ -32,7 +32,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `catalogs` | Required | Array | An array that contains catalog objects. Only one catalog object is allowed for this request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ### Catalog object parameters
 
@@ -41,7 +41,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `name` | Required | String | The name of the catalog that you want to create. |
 | `description` | Required | String | The description of the catalog that you want to create. |
 | `fields` | Required | Array | An array of objects where the object contains keys `name` and `type`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -197,6 +197,6 @@ The following table lists possible returned errors and their associated troubles
 | `invalid-fields` | `fields` is not formatted correctly. |
 | `too-many-catalog-atoms` | You can only create one catalog per request. |
 | `too-many-fields` | Number of fields limit is 500. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection.md b/_docs/_api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection.md
index 77be6a3288e..05e7cd10a4c 100644
--- a/_docs/_api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection.md
+++ b/_docs/_api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection.md
@@ -34,7 +34,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | ---------------- | -------- | --------- | ------------------------------ |
 | `catalog_name`   | Required | String    | Name of the catalog.           |
 | `selection_name` | Required | String    | Name of the catalog selection. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -80,7 +80,7 @@ The status code `404` could return the following response body. Refer to [Troubl
 }
 ```
 
-## Troubleshooting 
+## Troubleshooting
 
 The following table lists possible returned errors and their associated troubleshooting steps.
 
@@ -88,6 +88,6 @@ The following table lists possible returned errors and their associated troubles
 | -------------------- | -------------------------------------------------------- |
 | `catalog-not-found`  | Check that the catalog name is valid.                    |
 | `invalid-selection`  | Check that the selection name is valid.                  |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections.md b/_docs/_api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections.md
index cc61678fd1b..55f186f3e0b 100644
--- a/_docs/_api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections.md
+++ b/_docs/_api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections.md
@@ -33,14 +33,14 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter      | Required | Data Type | Description          |
 | -------------- | -------- | --------- | -------------------- |
 | `catalog_name` | Required | String    | Name of the catalog. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
 | Parameter   | Required | Data Type | Description                                                                                                                                                        |
 | ----------- | -------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `selection` | Required | Object    | An object that contains selection criteria. The selection objects could contain `name`, `description`, `filters`, `results_limit`, `sort_field`, and `sort_order`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example Request
 
@@ -77,7 +77,7 @@ curl --location --request POST 'https://rest.iad-03.braze.com/catalogs/restauran
 | `boolean`  | `is`                                                    |
 | `time`     | `before`, `after`                                       |
 | `array`    | `includes value`, `does not include value`              |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Response
 
@@ -133,6 +133,6 @@ The following table lists possible returned errors and their associated troubles
 | `invalid-sort-field`                 | Check if the selection sort field is valid.                                                   |
 | `invalid-sort-order`                 | Check if the selection sort order is valid.                                                   |
 | `selection-contains-too-many-arrays` | Check if the selection contains more than one field with `array` type. Only one is supported. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/cdi/get_integration_list.md b/_docs/_api/endpoints/cdi/get_integration_list.md
index 7c49daf1da3..25dfa7e5a39 100644
--- a/_docs/_api/endpoints/cdi/get_integration_list.md
+++ b/_docs/_api/endpoints/cdi/get_integration_list.md
@@ -33,7 +33,7 @@ Each call to this endpoint will return 10 items. For a list with more than 10 in
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `cursor` | Optional | String | Determines the pagination of the integration list. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -95,7 +95,7 @@ The following table lists possible returned errors and their associated troubles
 | Error | Troubleshooting |
 | --- | --- |
 | `400 Invalid cursor` | Check that your `cursor` is valid. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For additional status codes and associated error messages, refer to [Fatal errors & responses]({{site.baseurl}}/api/errors/#fatal-errors).
 
diff --git a/_docs/_api/endpoints/cdi/get_job_sync_status.md b/_docs/_api/endpoints/cdi/get_job_sync_status.md
index 52a452b828b..1eb082cd5e3 100644
--- a/_docs/_api/endpoints/cdi/get_job_sync_status.md
+++ b/_docs/_api/endpoints/cdi/get_job_sync_status.md
@@ -30,7 +30,7 @@ To use this endpoint, you'll need to generate an API key with the `cdi.integrati
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `integration_id` | Required | String | Integration ID. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Query parameters
 
@@ -39,7 +39,7 @@ Each call to this endpoint will return 10 items. For an integration with more th
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `cursor` | Optional | String | Determines the pagination of the sync status. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -96,7 +96,7 @@ Link: </cdi/integrations/00000000-0000-0000-0000-000000000000/job_sync_status?cu
 | `partial` | Some rows failed to sync due to errors. |
 | `error` | No rows were synced. |
 | `config_error` | There was an error in integration configuration. Check your integration setup. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Troubleshooting
 
@@ -106,7 +106,7 @@ The following table lists possible returned errors and their associated troubles
 | --- | --- |
 | `400 Invalid cursor` | Check that your `cursor` is valid. |
 | `400 Invalid integration ID` | Check that your `integration_id` is valid. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For additional status codes and associated error messages, please refer to [Fatal errors & responses]({{site.baseurl}}/api/errors/#fatal-errors).
 
diff --git a/_docs/_api/endpoints/cdi/post_job_sync.md b/_docs/_api/endpoints/cdi/post_job_sync.md
index be0c0a0cda3..fa2b809135a 100644
--- a/_docs/_api/endpoints/cdi/post_job_sync.md
+++ b/_docs/_api/endpoints/cdi/post_job_sync.md
@@ -30,7 +30,7 @@ To use this endpoint, you'll need to generate an API key with the `cdi.integrati
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `integration_id` | Required | String | Integration ID. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -61,7 +61,7 @@ The following table lists possible returned errors and their associated troubles
 | `400 Invalid integration ID` | Check that your `integration_id` is valid. |
 | `404 Integration not found` | No integration exists for the given integration ID. Make sure that your integration ID is valid. |
 | `429 Another job is in progress` | There is a sync currently running for this integration. Try again after the sync has completed. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For additional status codes and associated error messages, please refer to [Fatal errors & responses]({{site.baseurl}}/api/errors/#fatal-errors).
 
diff --git a/_docs/_api/endpoints/email/delete_remove_subscription_state.md b/_docs/_api/endpoints/email/delete_remove_subscription_state.md
index 04745d9906f..aa7f12b8e86 100644
--- a/_docs/_api/endpoints/email/delete_remove_subscription_state.md
+++ b/_docs/_api/endpoints/email/delete_remove_subscription_state.md
@@ -24,7 +24,7 @@ description: "This article outlines the details about the Delete subscription st
 | --- | --- | --- | --- |
 | `email` | Yes | String | The email address of the user (must include at least one address and at most 50 addresses). |
 | `phone` | Yes | String | The phone number of the user (must include at least one phone number and at most 50 phone numbers). We recommend providing this in E.164 format. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -47,4 +47,4 @@ Authorization: Bearer YOUR_REST_API_KEY
 }
 ```
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/email/get_list_hard_bounces.md b/_docs/_api/endpoints/email/get_list_hard_bounces.md
index 16a7f5c9388..dd2423387e1 100644
--- a/_docs/_api/endpoints/email/get_list_hard_bounces.md
+++ b/_docs/_api/endpoints/email/get_list_hard_bounces.md
@@ -35,13 +35,13 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `limit` | Optional | Integer | Optional field to limit the number of results returned. Defaults to 100, maximum is 500. |
 | `offset` | Optional | Integer | Optional beginning point in the list to retrieve from. |
 | `email` | Optional<br>(see note) | String | If provided, we will return whether or not the user has hard bounced. Check that the email strings are formatted properly. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 You must provide either a `start_date` and `end_date`, OR an `email`. If you provide all three, `start_date`, `end_date`, and an `email`, we prioritize the emails given and disregard the date range.
 {% endalert %}
 
-If your date range has more than the `limit` number of hard bounces, you will need to make multiple API calls, each time increasing the `offset` until a call returns either fewer than `limit` or zero results. Including `offset` and `limit` parameters with `email` can return an empty response. 
+If your date range has more than the `limit` number of hard bounces, you will need to make multiple API calls, each time increasing the `offset` until a call returns either fewer than `limit` or zero results. Including `offset` and `limit` parameters with `email` can return an empty response.
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/email/get_query_by_email_or_phone.md b/_docs/_api/endpoints/email/get_query_by_email_or_phone.md
index 53014dbd788..cfa3adec89a 100644
--- a/_docs/_api/endpoints/email/get_query_by_email_or_phone.md
+++ b/_docs/_api/endpoints/email/get_query_by_email_or_phone.md
@@ -23,7 +23,7 @@ description: "This article outlines the details about the List subscription stat
 | --- | --- | --- | --- |
 | `email` | Yes | String | The email address of the user (must include at least one address and at most 50 addresses). |
 | `phone` | Yes | String | The phone number of the user (must include at least one phone number and at most 50 phone numbers). We recommend providing this in E.164 format. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -69,4 +69,4 @@ Authorization: Bearer YOUR-REST-API-KEY
 }
 ```
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/email/get_query_unsubscribed_email_addresses.md b/_docs/_api/endpoints/email/get_query_unsubscribed_email_addresses.md
index 23ef0e847cb..e2cd50b8883 100644
--- a/_docs/_api/endpoints/email/get_query_unsubscribed_email_addresses.md
+++ b/_docs/_api/endpoints/email/get_query_unsubscribed_email_addresses.md
@@ -38,7 +38,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `offset` | Optional | Integer | Optional beginning point in the list to retrieve from. |
 | `sort_direction` | Optional | String | Pass in the value `asc` to sort unsubscribes from oldest to newest. Pass in `desc` to sort from newest to oldest. If `sort_direction` is not included, the default order is newest to oldest. |
 | `email` | Optional <br>(see note) | String | If provided, we will return whether or not the user has unsubscribed. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 You must provide an `end_date`, as well as either an `email` or a `start_date`.
@@ -46,7 +46,7 @@ You must provide an `end_date`, as well as either an `email` or a `start_date`.
 
 If your date range has more than `limit` number of unsubscribes, you will need to make multiple API calls, each time increasing the `offset` until a call returns either fewer than `limit` or zero results.
 
-## Example request 
+## Example request
 ```
 curl --location --request GET 'https://rest.iad-01.braze.com/email/unsubscribes?start_date=2020-01-01&end_date=2020-02-01&limit=1&offset=1&sort_direction=desc&email=example@braze.com' \
 --header 'Authorization: Bearer YOUR-API-KEY-HERE'
diff --git a/_docs/_api/endpoints/email/post_blacklist.md b/_docs/_api/endpoints/email/post_blacklist.md
index c46544c9cd0..921c8817bc7 100644
--- a/_docs/_api/endpoints/email/post_blacklist.md
+++ b/_docs/_api/endpoints/email/post_blacklist.md
@@ -11,7 +11,7 @@ description: "This article outlines the details about the Blacklist emails Braze
 ---
 {% api %}
 # Blacklist emails
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /email/blacklist
 {% endapimethod %}
 
@@ -49,7 +49,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | -----------|----------| --------|------- |
 | `email` | Required | String or array | String email address to blacklist, or an array of up to 50 email addresses to blacklist. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -62,5 +62,3 @@ curl --location --request POST 'https://rest.iad-01.braze.com/email/blacklist' \
 ```
 
 {% endapi %}
-
-
diff --git a/_docs/_api/endpoints/email/post_blocklist.md b/_docs/_api/endpoints/email/post_blocklist.md
index dc2b9c65754..39e2ae470a1 100644
--- a/_docs/_api/endpoints/email/post_blocklist.md
+++ b/_docs/_api/endpoints/email/post_blocklist.md
@@ -10,12 +10,12 @@ description: "This article outlines the details about the Blocklist emails Braze
 ---
 {% api %}
 # Blocklist emails
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /email/blocklist
 {% endapimethod %}
 
 > Use this endpoint to unsubscribe a user from email and mark them as hard bounced.
- 
+
 {% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#d51155a1-a6e8-4dcc-9f2b-88c54ab9e8c6 {% endapiref %}
 
 ## Prerequisites
@@ -44,7 +44,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | -----------|----------| --------|------- |
 | `email` | Required | String or array | String email address to blocklist, or an array of up to 50 email addresses to blocklist. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/email/post_email_subscription_status.md b/_docs/_api/endpoints/email/post_email_subscription_status.md
index 1db45e0df7b..215faa928a2 100644
--- a/_docs/_api/endpoints/email/post_email_subscription_status.md
+++ b/_docs/_api/endpoints/email/post_email_subscription_status.md
@@ -10,11 +10,11 @@ description: "This article outlines the details about the Change user's email su
 ---
 {% api %}
 # Change email subscription status
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /email/status
 {% endapimethod %}
 
-> Use this endpoint to set the email subscription state for your users. 
+> Use this endpoint to set the email subscription state for your users.
 
 Users can be `opted_in`, `unsubscribed`, or `subscribed` (not specifically opted in or out).
 
@@ -50,7 +50,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | --------- | ---------| --------- | ----------- |
 | `email` | Required | String or array | String email address to modify, or an array of up to 50 email addresses to modify. |
 | `subscription_state` | Required | String | Either "subscribed", "unsubscribed", or "opted_in". |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/email/post_remove_hard_bounces.md b/_docs/_api/endpoints/email/post_remove_hard_bounces.md
index 2797ea0055c..4377574dd6a 100644
--- a/_docs/_api/endpoints/email/post_remove_hard_bounces.md
+++ b/_docs/_api/endpoints/email/post_remove_hard_bounces.md
@@ -44,7 +44,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | ----------|-----------| ---------|------ |
 | `email` | Required | String or array | String email address to modify, or an array of up to 50 email addresses to modify. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/email/post_remove_spam.md b/_docs/_api/endpoints/email/post_remove_spam.md
index e3aee15e490..937405c0c48 100644
--- a/_docs/_api/endpoints/email/post_remove_spam.md
+++ b/_docs/_api/endpoints/email/post_remove_spam.md
@@ -43,7 +43,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | ----------|-----------| --------|------- |
 | `email` | Required | String or array | String email address to modify, or an array of up to 50 email addresses to modify. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/export/campaigns/get_campaign_analytics.md b/_docs/_api/endpoints/export/campaigns/get_campaign_analytics.md
index 8aa3abca545..9bc7abd7055 100644
--- a/_docs/_api/endpoints/export/campaigns/get_campaign_analytics.md
+++ b/_docs/_api/endpoints/export/campaigns/get_campaign_analytics.md
@@ -35,7 +35,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `campaign_id` | Required | String | See [campaign API identifier]({{site.baseurl}}/api/identifier_types/).<br><br> The `campaign_id` for API campaigns can be found on the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page and the **Campaign Details** page within your dashboard, or you can use the [List campaigns endpoint]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaigns/). |
 | `length` | Required | Integer | Maximum number of days before `ending_at` to include in the returned series. Must be between 1 and 100 (inclusive). |
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request 
 
diff --git a/_docs/_api/endpoints/export/campaigns/get_campaign_details.md b/_docs/_api/endpoints/export/campaigns/get_campaign_details.md
index 1bde818d2ee..5205a9d20b4 100644
--- a/_docs/_api/endpoints/export/campaigns/get_campaign_details.md
+++ b/_docs/_api/endpoints/export/campaigns/get_campaign_details.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Export campaign details Br
 /campaigns/details
 {% endapimethod %}
 
-> Use this endpoint to retrieve relevant information on a specified campaign, which can be identified by the `campaign_id`. 
+> Use this endpoint to retrieve relevant information on a specified campaign, which can be identified by the `campaign_id`.
 
 If you want to retrieve Canvas data, refer to the [Export Canvas details]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/) endpoint.
 
@@ -33,9 +33,9 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 | --------- | -------- | --------- | ----------- |
 | `campaign_id` | Required | String | See [campaign API identifier]({{site.baseurl}}/api/identifier_types/).<br><br> The `campaign_id` for API campaigns can be found on the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page and the **Campaign Details** page within your dashboard; or you can use the [Export campaigns list endpoint](#campaign-list-endpoint). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
-## Example request 
+## Example request
 {% raw %}
 ```
 curl --location -g --request GET 'https://rest.iad-01.braze.com/campaigns/details?campaign_id={{campaign_identifier}}' \
@@ -118,17 +118,17 @@ The `messages` response will contain information about each message. The followi
     "data": {
         "pages": [
             {
-                "header": 
+                "header":
                     {
                          "text":(string) the display text for the header of the survey,
                     }
                 "choices": [
                     {
                        "choice_id": (string) the choice identifier,
-                       "text": (string) the display text, 
-                       "custom_attribute_key": (string) the custom attribute key, 
+                       "text": (string) the display text,
+                       "custom_attribute_key": (string) the custom attribute key,
                        "custom_attribute_value": (sting) the custom attribute value,
-                       "deleted": (boolean) deleted from live campaign, 
+                       "deleted": (boolean) deleted from live campaign,
                     },
                     ...
                 ]
diff --git a/_docs/_api/endpoints/export/campaigns/get_campaigns.md b/_docs/_api/endpoints/export/campaigns/get_campaigns.md
index 0be69178e92..c63c09d9819 100644
--- a/_docs/_api/endpoints/export/campaigns/get_campaigns.md
+++ b/_docs/_api/endpoints/export/campaigns/get_campaigns.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Export campaigns list Braz
 /campaigns/list
 {% endapimethod %}
 
-> Use this endpoint to export a list of campaigns, each of which will include its name, campaign API identifier, whether it is an API campaign, and tags associated with the campaign. 
+> Use this endpoint to export a list of campaigns, each of which will include its name, campaign API identifier, whether it is an API campaign, and tags associated with the campaign.
 
 The campaigns are returned in groups of 100 sorted by time of creation (oldest to newest by default).
 
@@ -36,10 +36,10 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `include_archived` | Optional | Boolean | Whether or not to include archived campaigns, defaults to false. |
 | `sort_direction` | Optional | String | - Sort creation time from newest to oldest: pass in the value `desc`.<br> - Sort creation time from oldest to newest: pass in the value `asc`. <br><br>If `sort_direction` is not included, the default order is oldest to newest. |
 | `last_edit.time[gt]` | Optional | Time | Filters the results and only returns campaigns that were edited greater than the time provided till now. Format is `yyyy-MM-DDTHH:mm:ss`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
- 
+
 ```
 curl --location -g --request GET 'https://rest.iad-01.braze.com/campaigns/list?page=0&include_archived=false&sort_direction=desc&last_edit.time[gt]=2020-06-28T23:59:59-5:00' \
 --header 'Authorization: Bearer YOUR-REST-API-KEY'
@@ -55,7 +55,7 @@ Authorization: Bearer YOUR-REST-API-KEY
     "campaigns" : [
         {
             "id" : (string) the Campaign API identifier,
-            "last_edited": (ISO 8601 string) the last edited time for the message 
+            "last_edited": (ISO 8601 string) the last edited time for the message
             "name" : (string) the campaign name,
             "is_api_campaign" : (boolean) whether the campaign is an API campaign,
             "tags" : (array) the tag names associated with the campaign formatted as strings
diff --git a/_docs/_api/endpoints/export/campaigns/get_send_analytics.md b/_docs/_api/endpoints/export/campaigns/get_send_analytics.md
index 845388cdd7a..1d7e013174b 100644
--- a/_docs/_api/endpoints/export/campaigns/get_send_analytics.md
+++ b/_docs/_api/endpoints/export/campaigns/get_send_analytics.md
@@ -36,9 +36,9 @@ This endpoint is for API campaigns only. To use this endpoint, you'll need an [A
 | `send_id` | Required | String | See [Send API identifier]({{site.baseurl}}/api/identifier_types/). |
 | `length` | Required | Integer | Maximum number of days before `ending_at` to include in the returned series. Must be between 1 and 100 (inclusive). |
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
-## Example request 
+## Example request
 
 {% raw %}
 ```
diff --git a/_docs/_api/endpoints/export/canvas/get_canvas_analytics.md b/_docs/_api/endpoints/export/canvas/get_canvas_analytics.md
index 26dc06cc0c9..6dd1584911d 100644
--- a/_docs/_api/endpoints/export/canvas/get_canvas_analytics.md
+++ b/_docs/_api/endpoints/export/canvas/get_canvas_analytics.md
@@ -37,7 +37,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `include_variant_breakdown` | Optional | Boolean | Whether or not to include variant statistics (defaults to `false`).  |
 | `include_step_breakdown` | Optional | Boolean | Whether or not to include step statistics (defaults to `false`). |
 | `include_deleted_step_data` | Optional | Boolean | Whether or not to include step statistics for deleted steps (defaults to `false`). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/export/canvas/get_canvas_analytics_summary.md b/_docs/_api/endpoints/export/canvas/get_canvas_analytics_summary.md
index baed506a671..93e6c4cdea5 100644
--- a/_docs/_api/endpoints/export/canvas/get_canvas_analytics_summary.md
+++ b/_docs/_api/endpoints/export/canvas/get_canvas_analytics_summary.md
@@ -37,7 +37,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `include_variant_breakdown` | Optional | Boolean | Whether or not to include variant statistics (defaults to `false`).  |
 | `include_step_breakdown` | Optional | Boolean | Whether or not to include step statistics (defaults to `false`). |
 | `include_deleted_step_data` | Optional | Boolean | Whether or not to include step statistics for deleted steps (defaults to `false`). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/export/canvas/get_canvas_details.md b/_docs/_api/endpoints/export/canvas/get_canvas_details.md
index 37cfa8096bd..d087db61515 100644
--- a/_docs/_api/endpoints/export/canvas/get_canvas_details.md
+++ b/_docs/_api/endpoints/export/canvas/get_canvas_details.md
@@ -31,7 +31,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 | --------- | -------- | --------- | ----------- |
 | `canvas_id` | Required | String | See [Canvas API Identifier]({{site.baseurl}}/api/identifier_types/) |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/export/canvas/get_canvases.md b/_docs/_api/endpoints/export/canvas/get_canvases.md
index 9bb0a83a6de..0836ca16662 100644
--- a/_docs/_api/endpoints/export/canvas/get_canvases.md
+++ b/_docs/_api/endpoints/export/canvas/get_canvases.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Export Canvas list Braze e
 /canvas/list
 {% endapimethod %}
 
-> Use this endpoint to export a list of Canvases, including the name, Canvas API identifier and associated tags. 
+> Use this endpoint to export a list of Canvases, including the name, Canvas API identifier and associated tags.
 
 Canvases are returned in groups of 100 sorted by time of creation (oldest to newest by default).
 
@@ -38,7 +38,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `include_archived` | Optional | Boolean | Whether or not to include archived Canvases, defaults to `false`. |
 | `sort_direction` | Optional | String | - Sort creation time from newest to oldest: pass in the value `desc`.<br> - Sort creation time from oldest to newest: pass in the value `asc`. <br><br>If `sort_direction` is not included, the default order is oldest to newest. |
 | `last_edit.time[gt]` | Optional | Time | Filters the results and only returns Canvases that were edited greater than the time provided until now. Format is `yyyy-MM-DDTHH:mm:ss`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/export/custom_attributes/get_custom_attributes.md b/_docs/_api/endpoints/export/custom_attributes/get_custom_attributes.md
index 305a2efc66c..90fc8b4669c 100644
--- a/_docs/_api/endpoints/export/custom_attributes/get_custom_attributes.md
+++ b/_docs/_api/endpoints/export/custom_attributes/get_custom_attributes.md
@@ -31,7 +31,7 @@ Note that each call to this endpoint will return 50 attributes. For more than 50
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `cursor` | Optional | String | Determines the pagination of the custom attributes. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example requests
 
diff --git a/_docs/_api/endpoints/export/custom_events/get_custom_events.md b/_docs/_api/endpoints/export/custom_events/get_custom_events.md
index 4b44aca4535..122d1af77e2 100644
--- a/_docs/_api/endpoints/export/custom_events/get_custom_events.md
+++ b/_docs/_api/endpoints/export/custom_events/get_custom_events.md
@@ -31,7 +31,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter| Required | Data Type | Description |
 | -------- | -------- | --------- | ----------- |
 | `page` | Optional | Integer | The page of event names to return, defaults to 0 (returns the first set of up to 250). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/export/custom_events/get_custom_events_analytics.md b/_docs/_api/endpoints/export/custom_events/get_custom_events_analytics.md
index 00e30101c20..db57322bbfa 100644
--- a/_docs/_api/endpoints/export/custom_events/get_custom_events_analytics.md
+++ b/_docs/_api/endpoints/export/custom_events/get_custom_events_analytics.md
@@ -36,7 +36,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
 | `app_id` | Optional | String | App API identifier retrieved from the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page to limit analytics to a specific app. |
 | `segment_id` | Optional | String | See [Segment API identifier]({{site.baseurl}}/api/identifier_types/). Segment ID indicating the analytics-enabled segment for which event analytics should be returned. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 
 ## Example request
@@ -45,7 +45,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 curl --location -g --request GET 'https://rest.iad-01.braze.com/events/data_series?event=event_name&length=24&unit=hour&ending_at=2014-12-10T23:59:59-05:00&app_id={{app_identifier}}&segment_id={{segment_identifier}}' \
 --header 'Authorization: Bearer YOUR-REST-API-KEY'
 ```
-{% endraw %} 
+{% endraw %}
 
 ## Response
 
diff --git a/_docs/_api/endpoints/export/custom_events/get_custom_events_data.md b/_docs/_api/endpoints/export/custom_events/get_custom_events_data.md
index ee1ca6f0467..d9b7f7b8e85 100644
--- a/_docs/_api/endpoints/export/custom_events/get_custom_events_data.md
+++ b/_docs/_api/endpoints/export/custom_events/get_custom_events_data.md
@@ -31,7 +31,7 @@ Note that each call to this endpoint will return 50 events. For more than 50 eve
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `cursor` | Optional | String | Determines the pagination of the custom events. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example requests
 
diff --git a/_docs/_api/endpoints/export/kpi/get_kpi_daily_new_users_date.md b/_docs/_api/endpoints/export/kpi/get_kpi_daily_new_users_date.md
index b4b6fcd6be4..b88056551c1 100644
--- a/_docs/_api/endpoints/export/kpi/get_kpi_daily_new_users_date.md
+++ b/_docs/_api/endpoints/export/kpi/get_kpi_daily_new_users_date.md
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `length` | Required | Integer | Maximum number of days before `ending_at` to include in the returned series. Must be between 1 and 100 (inclusive). |
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
 | `app_id` | Optional | String | App API identifier retrieved from the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page. If excluded, results for all apps in workspace will be returned. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/export/kpi/get_kpi_dau_date.md b/_docs/_api/endpoints/export/kpi/get_kpi_dau_date.md
index b028a7d17f7..eb15633cff7 100644
--- a/_docs/_api/endpoints/export/kpi/get_kpi_dau_date.md
+++ b/_docs/_api/endpoints/export/kpi/get_kpi_dau_date.md
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `length` | Required | Integer | Maximum number of days before `ending_at` to include in the returned series. Must be between 1 and 100 (inclusive). |
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
 | `app_id` | Optional | String | App API identifier retrieved from the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page. If excluded, results for all apps in workspace will be returned. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/export/kpi/get_kpi_mau_30_days.md b/_docs/_api/endpoints/export/kpi/get_kpi_mau_30_days.md
index 24cd404879e..0c1a472ba88 100644
--- a/_docs/_api/endpoints/export/kpi/get_kpi_mau_30_days.md
+++ b/_docs/_api/endpoints/export/kpi/get_kpi_mau_30_days.md
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `length` | Required | Integer | Maximum number of days before `ending_at` to include in the returned series. Must be between 1 and 100 (inclusive). |
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
 | `app_id` | Optional | String | App API identifier retrieved from the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page. If excluded, results for all apps in workspace will be returned. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/export/kpi/get_kpi_uninstalls_date.md b/_docs/_api/endpoints/export/kpi/get_kpi_uninstalls_date.md
index 3f937498b5b..c20286cd748 100644
--- a/_docs/_api/endpoints/export/kpi/get_kpi_uninstalls_date.md
+++ b/_docs/_api/endpoints/export/kpi/get_kpi_uninstalls_date.md
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `length` | Required | Integer | Maximum number of days before `ending_at` to include in the returned series. Must be between 1 and 100 (inclusive). |
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
 | `app_id` | Optional | String | App API identifier retrieved from the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page. If excluded, results for all apps in workspace will be returned. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/export/news_feed/get_news_feed_card_analytics.md b/_docs/_api/endpoints/export/news_feed/get_news_feed_card_analytics.md
index a9721982861..29d8d5a581a 100644
--- a/_docs/_api/endpoints/export/news_feed/get_news_feed_card_analytics.md
+++ b/_docs/_api/endpoints/export/news_feed/get_news_feed_card_analytics.md
@@ -38,7 +38,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `length` | Required | Integer | Maximum number of units (days or hours) before `ending_at` to include in the returned series. Must be between 1 and 100 (inclusive). |
 | `unit` | Optional | String | Unit of time between data points. Can be `day` or `hour`, defaults to `day`.  |
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/export/news_feed/get_news_feed_card_details.md b/_docs/_api/endpoints/export/news_feed/get_news_feed_card_details.md
index 41d5b64819a..bf2ecf29cdf 100644
--- a/_docs/_api/endpoints/export/news_feed/get_news_feed_card_details.md
+++ b/_docs/_api/endpoints/export/news_feed/get_news_feed_card_details.md
@@ -35,7 +35,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description            |
 | --------- | -------- | --------- | ---------------------- |
 | `card_id` | Required | String | See [Card API identifier]({{site.baseurl}}/api/identifier_types/). <br><br> The `card_id` for a given card can be found on the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page and on the card details page within your dashboard, or you can use the [Export News Feed cards list endpoint]({{site.baseurl}}/api/endpoints/export/news_feed/get_news_feed_cards/).|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/export/news_feed/get_news_feed_cards.md b/_docs/_api/endpoints/export/news_feed/get_news_feed_cards.md
index 677c3fbe815..ea48e9b52f8 100644
--- a/_docs/_api/endpoints/export/news_feed/get_news_feed_cards.md
+++ b/_docs/_api/endpoints/export/news_feed/get_news_feed_cards.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Export News Feed cards lis
 /feed/list
 {% endapimethod %}
 
-> Use this endpoint to export a list of News Feed cards, each of which will include its name and card API identifier. 
+> Use this endpoint to export a list of News Feed cards, each of which will include its name and card API identifier.
 
 The cards are returned in groups of 100 sorted by time of creation (oldest to newest by default).
 
@@ -39,7 +39,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `page` | Optional | Integer   | The page of cards to return, defaults to 0 (returns the first set of up to 100). |
 | `include_archived` | Optional | Boolean   | Whether or not to include archived cards, defaults to false. |
 | `sort_direction` | Optional | String | - Sort creation time from newest to oldest: pass in the value `desc`.<br> - Sort creation time from oldest to newest: pass in the value `asc`. <br><br>If `sort_direction` is not included, the default order is oldest to newest. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/export/purchases/get_list_product_id.md b/_docs/_api/endpoints/export/purchases/get_list_product_id.md
index b07890abc8a..0d03e31f2c1 100644
--- a/_docs/_api/endpoints/export/purchases/get_list_product_id.md
+++ b/_docs/_api/endpoints/export/purchases/get_list_product_id.md
@@ -31,7 +31,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `page` | Optional | String | The page of your product list that you want to view. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/export/purchases/get_number_of_purchases.md b/_docs/_api/endpoints/export/purchases/get_number_of_purchases.md
index d4ca4042c91..3ae14a19762 100644
--- a/_docs/_api/endpoints/export/purchases/get_number_of_purchases.md
+++ b/_docs/_api/endpoints/export/purchases/get_number_of_purchases.md
@@ -35,7 +35,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `unit` | Optional | String | Unit of time between data points. Can be day or hour, defaults to day. |
 | `app_id` | Optional | String | App API identifier retrieved from the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page. If excluded, results for all apps in a workspace will be returned. |
 | `product` | Optional | String | Name of product to filter response by. If excluded, results for all apps will be returned. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/export/purchases/get_revenue_series.md b/_docs/_api/endpoints/export/purchases/get_revenue_series.md
index 9ac5f97b6ed..c3598819a01 100644
--- a/_docs/_api/endpoints/export/purchases/get_revenue_series.md
+++ b/_docs/_api/endpoints/export/purchases/get_revenue_series.md
@@ -35,7 +35,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `unit` | Optional | String | Unit of time between data points. Can be day or hour, defaults to day. |
 | `app_id` | Optional | String | App API identifier retrieved from the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page. If excluded, results for all apps in a workspace will be returned. |
 | `product` | Optional | String | Name of product to filter response by. If excluded, results for all apps will be returned. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/export/segments/get_segment.md b/_docs/_api/endpoints/export/segments/get_segment.md
index 435d3e796e8..d3fa061bef2 100644
--- a/_docs/_api/endpoints/export/segments/get_segment.md
+++ b/_docs/_api/endpoints/export/segments/get_segment.md
@@ -14,7 +14,7 @@ description: "This article outlines details about Export the segments list Braze
 /segments/list
 {% endapimethod %}
 
-> Use this endpoint to export a list of segments, each of which will include its name, Segment API identifier, and whether it has analytics tracking enabled. 
+> Use this endpoint to export a list of segments, each of which will include its name, Segment API identifier, and whether it has analytics tracking enabled.
 
 The segments are returned in groups of 100 sorted by time of creation (oldest to newest by default). Archived segments are not included.
 
@@ -34,7 +34,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | -------- | -------- | --------- | ----------- |
 | `page` | Optional | Integer | The page of segments to return, defaults to 0 (returns the first set of up to 100). |
 | `sort_direction` | Optional | String | - Sort creation time from newest to oldest: pass in the value `desc`.<br> - Sort creation time from oldest to newest: pass in the value `asc`. <br><br>If `sort_direction` is not included, the default order is oldest to newest. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/export/segments/get_segment_analytics.md b/_docs/_api/endpoints/export/segments/get_segment_analytics.md
index 58ec757b00a..edfe445f965 100644
--- a/_docs/_api/endpoints/export/segments/get_segment_analytics.md
+++ b/_docs/_api/endpoints/export/segments/get_segment_analytics.md
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `segment_id` | Required | String | See [Segment API identifier]({{site.baseurl}}/api/identifier_types/).<br><br> The `segment_id` for a given segment can be found on the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page within your Braze account or you can use the [Export segment list endpoint]({{site.baseurl}}/api/endpoints/export/segments/get_segment/).  |
 | `length` | Required | Integer | Maximum number of days before `ending_at` to include in the returned series. Must be between 1 and 100 (inclusive). |
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/export/segments/get_segment_details.md b/_docs/_api/endpoints/export/segments/get_segment_details.md
index 7b69c39e88b..8fd2b426358 100644
--- a/_docs/_api/endpoints/export/segments/get_segment_details.md
+++ b/_docs/_api/endpoints/export/segments/get_segment_details.md
@@ -31,7 +31,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter    | Required | Data Type | Description            |
 | ------------ | -------- | --------- | ---------------------- |
 | `segment_id` | Required | String | See [Segment API identifier]({{site.baseurl}}/api/identifier_types/).<br><br> The `segment_id` for a given segment can be found on the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page within your Braze account or you can use the [Export segment list endpoint]({{site.baseurl}}/api/endpoints/export/segments/get_segment/).  |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
@@ -52,7 +52,7 @@ Authorization: Bearer YOUR-REST-API-KEY
       "updated_at" : (string) the date last updated as ISO 8601 date,
       "name" : (string) the segment name,
       "description" : (string) a human-readable description of filters,
-      "text_description" : (string) the segment description, 
+      "text_description" : (string) the segment description,
       "tags" : (array) the tag names associated with the segment formatted as strings,
       "teams" : (array) the names of the Teams associated with the campaign
 }
diff --git a/_docs/_api/endpoints/export/sessions/get_sessions_analytics.md b/_docs/_api/endpoints/export/sessions/get_sessions_analytics.md
index 8a6e59c59c1..8c1841cc54b 100644
--- a/_docs/_api/endpoints/export/sessions/get_sessions_analytics.md
+++ b/_docs/_api/endpoints/export/sessions/get_sessions_analytics.md
@@ -35,7 +35,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `ending_at` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | Date on which the data series should end. Defaults to time of the request. |
 | `app_id` | Optional | String | App API identifier retrieved from the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page to limit analytics to a specific app. |
 | `segment_id` | Optional | String | See [Segment API identifier]({{site.baseurl}}/api/identifier_types/). Segment ID indicating the analytics-enabled segment for which sessions should be returned. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/export/user_data/post_users_global_control_group.md b/_docs/_api/endpoints/export/user_data/post_users_global_control_group.md
index 494659d34a3..e8e10da61a7 100644
--- a/_docs/_api/endpoints/export/user_data/post_users_global_control_group.md
+++ b/_docs/_api/endpoints/export/user_data/post_users_global_control_group.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Export users in Global Con
 /users/export/global_control_group
 {% endapimethod %}
 
-> Use this endpoint to export all users within a Global Control Group. 
+> Use this endpoint to export all users within a Global Control Group.
 
 User data is exported as multiple files of user JSON objects separated by new lines (such as one JSON object per line). All users in a Global Control Group are included each time the files are generated. Braze doesn't store a history of when users are added and removed from a Global Control Group.
 
@@ -48,11 +48,11 @@ If you have added your [S3][1] or [Azure][2] credentials to Braze, then each fil
 | `RANDOM_UUID` | A random UUID generated by Braze at the time of the request. | `d9696570-dfb7-45ae-baa2-25e302r2da27` |
 | `TIMESTAMP_WHEN_EXPORT_STARTED` | Unix time (seconds since 2017-01-01:00:00:00Z) that the export was requested in UTC. | `1556044807` |
 | `filename` | Random per file. | `114f0226319130e1a4770f2602b5639a` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% enddetails %}
 
-We strongly suggest setting up your own S3 or Azure credentials when using this endpoint to enforce your own bucket policies on the export. If you do not have your cloud storage credentials provided, the response to the request provides the URL where a ZIP containing all the user files can be downloaded. The URL will only become a valid location after the export is ready. 
+We strongly suggest setting up your own S3 or Azure credentials when using this endpoint to enforce your own bucket policies on the export. If you do not have your cloud storage credentials provided, the response to the request provides the URL where a ZIP containing all the user files can be downloaded. The URL will only become a valid location after the export is ready.
 
 Be aware that if you do not provide your cloud storage credentials, there is a limitation on the amount of data that you can export from this endpoint. Depending on the fields you're exporting and the number of users, the file transfer may fail if it is too large. A best practice is to specify which fields you want to export using `fields_to_export` and specifying only the fields you need in order to keep the size of the transfer lower. If you are getting errors generating the file, consider breaking your user base up into more segments based on a random bucket number (for example, create a segment where random bucket number is less than 1,000 or between 1,000 and 2,000).
 
@@ -86,7 +86,7 @@ Individual custom attributes cannot be exported. However, all custom attributes
 |`callback_endpoint` | Optional | String | Endpoint to post a download URL to when the export is available. |
 |`fields_to_export` | Required* | Array of Strings | Name of user data fields to export, you may also export custom attributes. <br><br>*Beginning April 2021, new accounts must specify specific fields to export. |
 |`output_format` | Optional | String | When using your own S3 bucket, allows to specify file format as `zip` or `gzip`. Defaults to ZIP file format. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -133,7 +133,7 @@ The following is a list of valid `fields_to_export`. Using `fields_to_export` to
 | `total_revenue` | Float | Total revenue attributed to this user. Total revenue is calculated based on purchases the user made during conversion windows for the campaigns and Canvases they received. |
 | `uninstalled_at` | Timestamp | Date and time the user uninstalls the app. Omitted if the app has not been uninstalled. |
 | `user_aliases` | Object | [User aliases object]({{site.baseurl}}/api/objects_filters/user_alias_object#user-alias-object-specification) containing the `alias_name` and `alias_label`, if exists. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Response
 
@@ -260,7 +260,7 @@ User export object (we will include the least data possible - if a field is miss
     "attributed_source" : "braze_test_source_072219",
     "attributed_adgroup" : "braze_test_adgroup_072219",
     "attributed_ad" : "braze_test_ad_072219",
-    "custom_attributes": 
+    "custom_attributes":
       {
         "loyaltyId": "37c98b9d-9a7f-4b2f-a125-d873c5152856",
         "loyaltyPoints": "321",
diff --git a/_docs/_api/endpoints/export/user_data/post_users_identifier.md b/_docs/_api/endpoints/export/user_data/post_users_identifier.md
index 44492067b85..df10790e765 100644
--- a/_docs/_api/endpoints/export/user_data/post_users_identifier.md
+++ b/_docs/_api/endpoints/export/user_data/post_users_identifier.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Export users by identifier
 /users/export/ids
 {% endapimethod %}
 
-> Use this endpoint to export data from any user profile by specifying a user identifier. 
+> Use this endpoint to export data from any user profile by specifying a user identifier.
 
 Up to 50 `external_ids` or `user_aliases` can be included in a single request. Should you want to specify `device_id`, `email_address`, or `phone`, only one of any identifier can be included per request.
 
@@ -62,7 +62,7 @@ For customers who have onboarded with Braze on or after August 22, 2024, the req
 | `email_address`    | Optional | String                                                        | Email address of user.                                                                       |
 | `phone`            | Optional | String in [E.164](https://en.wikipedia.org/wiki/E.164) format | Phone number of user.                                                                        |
 | `fields_to_export` | Required | Array of strings                                              | Name of user data fields to export.                                                          |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -119,7 +119,7 @@ The following is a list of valid `fields_to_export`. Using `fields_to_export` to
 | `total_revenue`       | Float           | Total revenue attributed to this user. Total revenue is calculated based on purchases the user made during conversion windows for the campaigns and Canvases they received.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | `uninstalled_at`      | Timestamp       | Date and time the user uninstalls the app. Omitted if the app has not been uninstalled.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | `user_aliases`        | Object          | [User aliases object]({{site.baseurl}}/api/objects_filters/user_alias_object#user-alias-object-specification) containing the `alias_name` and `alias_label`, if exists.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Be aware that the `/users/export/ids` endpoint will pull together the entire user profile for this user, including data such as all campaigns and Canvases received, all custom events performed, all purchases made, and all custom attributes. As a result, this endpoint is slower than other REST API endpoints.
 
@@ -232,7 +232,7 @@ User export object (we will include the least data possible - if a field is miss
       {
         "name" : (string),
         "last_received" : (string) date,
-        "engaged" : 
+        "engaged" :
          {
            "opened_email" : (boolean),
            "opened_push" : (boolean),
@@ -316,10 +316,10 @@ User export object (we will include the least data possible - if a field is miss
     "attributed_source" : "braze_test_source_072219",
     "attributed_adgroup" : "braze_test_adgroup_072219",
     "attributed_ad" : "braze_test_ad_072219",
-    "push_subscribe" : "opted_in", 
+    "push_subscribe" : "opted_in",
     "push_opted_in_at": "2020-01-26T22:45:53.953Z",
     "email_subscribe" : "subscribed",
-    "custom_attributes": 
+    "custom_attributes":
     {
       "loyaltyId": "37c98b9d-9a7f-4b2f-a125-d873c5152856",
       "loyaltyPoints": "321",
@@ -379,12 +379,12 @@ User export object (we will include the least data possible - if a field is miss
         "name": "Email Unsubscribe",
         "api_campaign_id": "d72fdc84-ddda-44f1-a0d5-0e79f47ef942",
         "last_received": "2022-06-02T03:07:38.105Z",
-        "engaged": 
+        "engaged":
         {
            "opened_email": true
         },
         "converted": true,
-        "multiple_converted": 
+        "multiple_converted":
         {
           "Primary Conversion Event - A": true
         },
diff --git a/_docs/_api/endpoints/export/user_data/post_users_segment.md b/_docs/_api/endpoints/export/user_data/post_users_segment.md
index d2b2325ecc1..15bd9b3c712 100644
--- a/_docs/_api/endpoints/export/user_data/post_users_segment.md
+++ b/_docs/_api/endpoints/export/user_data/post_users_segment.md
@@ -54,7 +54,7 @@ If you have added your [S3][1], [Azure][2], or [Google Cloud Storage][3] credent
 | `RANDOM_UUID` | A random UUID generated by Braze at the time of the request. | `d9696570-dfb7-45ae-baa2-25e302r2da27` |
 | `TIMESTAMP_WHEN_EXPORT_STARTED` | Unix time (seconds since 2017-01-01:00:00:00Z) that the export was requested in UTC. | `1556044807` |
 | `filename` | Random per file. | `114f0226319130e1a4770f2602b5639a` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% enddetails %}
 
@@ -91,7 +91,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`fields_to_export` | Required* | Array of strings | Name of user data fields to export. You can also export all custom attributes by including `custom_attributes` in this parameter. <br><br>*Beginning April 2021, new accounts must specify specific fields to export. |
 | `custom_attributes_to_export` | Optional | Array of strings | Name of specific custom attribute to export. Up to 500 custom attributes can be exported. To create and manage custom attributes in the dashboard, go to **Data Settings** > **Custom Attributes**. |
 |`output_format` | Optional | String | The output format of your file. Defaults to `zip` file format. If you are using your own S3 bucket, you can specify `zip` or `gzip`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 If `custom_attributes` is included in the `fields_to_export` parameter, all custom attributes are exported regardless of what is in `custom_attributes_to_export`. If your goal is to export specific attributes, `custom_attributes` should not be included in the `fields_to_export` parameter. Instead, use the `custom_attributes_to_export` parameter.
@@ -158,7 +158,7 @@ The following is a list of valid `fields_to_export`. Using `fields_to_export` to
 | `total_revenue` | Float | Total revenue attributed to this user. Total revenue is calculated based on purchases the user made during conversion windows for the campaigns and Canvases they received. |
 | `uninstalled_at` | Timestamp | Date and time the user uninstalls the app. Omitted if the app has not been uninstalled. |
 | `user_aliases` | Object | [User aliases object]({{site.baseurl}}/api/objects_filters/user_alias_object#user-alias-object-specification) containing the `alias_name` and `alias_label`, if exists. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Important reminders
 
diff --git a/_docs/_api/endpoints/messaging/duplicate_campaigns.md b/_docs/_api/endpoints/messaging/duplicate_campaigns.md
index e488f8c6b72..b18125af03c 100644
--- a/_docs/_api/endpoints/messaging/duplicate_campaigns.md
+++ b/_docs/_api/endpoints/messaging/duplicate_campaigns.md
@@ -10,7 +10,7 @@ description: "This article outlines details about the Duplicate campaigns endpoi
 ---
 {% api %}
 # Duplicate campaigns via API
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /campaigns/duplicate
 {% endapimethod %}
 
@@ -50,7 +50,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`campaign_id`| Required | String | See [campaign identifier]({{site.baseurl}}/api/identifier_types/). |
 |`name`| Required | String | The name of the resulting campaign. |
 |`description`| Optional | String | The description field for the resulting campaign. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 
 ## Response
diff --git a/_docs/_api/endpoints/messaging/live_activity/start.md b/_docs/_api/endpoints/messaging/live_activity/start.md
index 1c447048a7b..352cdafb4db 100644
--- a/_docs/_api/endpoints/messaging/live_activity/start.md
+++ b/_docs/_api/endpoints/messaging/live_activity/start.md
@@ -66,7 +66,7 @@ To use this endpoint, you'll need to complete the following:
 | `external_user_ids` | Optional if `segment_id` or `audience` is provided | Array of strings | See [external user ID]({{site.baseurl}}/api/objects_filters/user_attributes_object/#braze-user-profile-fields).  |
 | `segment_id `  | Optional if `external_user_ids` or `audience` is provided | String    | See [segment identifier]({{site.baseurl}}/api/identifier_types/). |
 | `custom_audience` | Optional if `external_user_ids` or `segment_id` is provided | Connected audience object  | See [connected audience]({{site.baseurl}}/api/objects_filters/connected_audience/). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/messaging/live_activity/update.md b/_docs/_api/endpoints/messaging/live_activity/update.md
index 9eb1d5919d8..f552cafafb7 100644
--- a/_docs/_api/endpoints/messaging/live_activity/update.md
+++ b/_docs/_api/endpoints/messaging/live_activity/update.md
@@ -57,7 +57,7 @@ To use this endpoint, you'll need to complete the following:
 | `dismissal_date` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | This parameter defines the time to remove the Live Activity from the user's UI. If this time is in the past and `end_activity` is `true`, the Live Activity will be removed immediately.<br><br> If `end_activity` is `false` or omitted, this parameter only updates the Live Activity.|
 | `stale_date` | Optional | Datetime <br>([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) string) | This parameter tells the system when the Live Activity content is marked as outdated in the user's UI. |
 | `notification` | Optional | Object | Include an [`apple_push`]({{site.baseurl}}/api/objects_filters/messaging/apple_object/) object to define a push notification. This behavior of this push notification depends on if the user is active or if the user is using a proxy device. {::nomarkdown}<ul><li>If a <code>notification</code> is included and the user is active on their iPhone when the update is delivered, the updated Live Activity UI will slide down and display like a push notification.</li><li>If a <code>notification</code> is included and the user is not active on their iPhone, their screen will light up to display the updated Live Activity UI on their lock screen.</li><li>The <code>notification alert</code> will not display as a standard push notification. Additionally, if a user has a proxy device, like an Apple Watch, the <code>alert</code> will be displayed there.</li></ul>{:/} |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/get_messages_scheduled.md b/_docs/_api/endpoints/messaging/schedule_messages/get_messages_scheduled.md
index 29222f6334e..d4c19ecd974 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/get_messages_scheduled.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/get_messages_scheduled.md
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | Parameter | Required | Data Type | Description |
 | --------- | -------- | --------- | ----------- |
 | `end_time` | Required | String in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format | End date of the range to retrieve upcoming scheduled campaigns and Canvases. This is treated as midnight in UTC time by the API. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages.md b/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages.md
index 3a0008a40a9..47a748db0e9 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages.md
@@ -10,7 +10,7 @@ description: "This article outlines details about the Delete scheduled messages
 ---
 {% api %}
 # Delete scheduled messages
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /messages/schedule/delete
 {% endapimethod %}
 
@@ -44,7 +44,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | --------- | ---------| --------- | ----------- |
 | `schedule_id` | Required | String | The `schedule_id` to delete (obtained from the response to create schedule). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases.md b/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases.md
index a2088944f99..a10063ca7d9 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases.md
@@ -10,7 +10,7 @@ description: "This article outlines details about the Delete scheduled API-trigg
 ---
 {% api %}
 # Delete scheduled API-triggered Canvases
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /canvas/trigger/schedule/delete
 {% endapimethod %}
 
@@ -48,7 +48,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | --------- | ---------| --------- | ----------- |
 | `canvas_id`| Required | String | See [Canvas identifier]({{site.baseurl}}/api/identifier_types/). |
 | `schedule_id` | Required | String | The `schedule_id` to delete (obtained from the response to create schedule). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 
 ## Example request
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages.md b/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages.md
index fe8e93b6bbb..67ca6c3c09d 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages.md
@@ -10,7 +10,7 @@ description: "This article outlines details about the Delete scheduled API-trigg
 ---
 {% api %}
 # Delete scheduled API-triggered campaigns
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /campaigns/trigger/schedule/delete
 {% endapimethod %}
 
@@ -48,7 +48,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | --------- | ---------| --------- | ----------- |
 | `campaign_id`| Required | String | See [campaign identifier]({{site.baseurl}}/api/identifier_types/). |
 | `schedule_id` | Required | String | The `schedule_id` to delete (obtained from the response to create schedule). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 
 ## Example request
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_messages.md b/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_messages.md
index f5b2c28cd90..3dbc5af31d2 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_messages.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_messages.md
@@ -10,11 +10,11 @@ description: "This article outlines details about the Create scheduled messages
 ---
 {% api %}
 # Create scheduled messages
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /messages/schedule/create
 {% endapimethod %}
 
-> Use this endpoint to schedule a campaign, Canvas, or other message to be sent at a designated time and provides you with an identifier to reference that message for updates. 
+> Use this endpoint to schedule a campaign, Canvas, or other message to be sent at a designated time and provides you with an identifier to reference that message for updates.
 
 If you are targeting a segment, a record of your request will be stored in the [Developer Console](https://dashboard.braze.com/app_settings/developer_console/activitylog/) after all scheduled messages have been sent.
 
@@ -50,7 +50,7 @@ Authorization: Bearer YOUR-REST-API-KEY
   "send_id": (optional, string) see send identifier,
   "override_messaging_limits": (optional, bool) ignore frequency capping rules, defaults to false,
   "recipient_subscription_state": (optional, string) use this to send messages to only users who have opted in ('opted_in'), only users who have subscribed or are opted in ('subscribed') or to all users, including unsubscribed users ('all'), the latter being useful for transactional email messaging. Defaults to 'subscribed',
-  "schedule": { 
+  "schedule": {
     "time": (required, datetime as ISO 8601 string) time to send the message in UTC,
     "in_local_time": (optional, bool),
     "at_optimal_time": (optional, bool),
@@ -79,12 +79,12 @@ Authorization: Bearer YOUR-REST-API-KEY
 | `segment_id` | Optional | String | See [segment identifier]({{site.baseurl}}/api/identifier_types/). |
 | `campaign_id`|Optional|String| See [campaign identifier]({{site.baseurl}}/api/identifier_types/). |
 | `recipients` | Optional | Array of recipients objects | See [recipients object]({{site.baseurl}}/api/objects_filters/recipient_object/). |
-| `send_id` | Optional | String | See [send identifier]({{site.baseurl}}/api/identifier_types/). | 
+| `send_id` | Optional | String | See [send identifier]({{site.baseurl}}/api/identifier_types/). |
 | `override_messaging_limits` | Optional | Boolean | Ignore global rate limits for campaigns, defaults to false |
 |`recipient_subscription_state`| Optional | String | Use this to send messages to only users who have opted in (`opted_in`), only users who have subscribed or are opted in (`subscribed`) or to all users, including unsubscribed users (`all`). <br><br>Using `all` users is useful for transactional email messaging. Defaults to `subscribed`. |
 | `schedule` | Required | Schedule object | See [schedule object]({{site.baseurl}}/api/objects_filters/schedule_object/) |
 | `messages` | Optional | Messaging object | See [available messaging objects]({{site.baseurl}}/api/objects_filters/#messaging-objects). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -178,4 +178,3 @@ curl --location --request POST 'https://rest.iad-01.braze.com/messages/schedule/
 ```
 
 {% endapi %}
-
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns.md b/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns.md
index 9dad3fc951e..f1772cdb056 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns.md
@@ -10,11 +10,11 @@ description: "This article outlines details about the Schedule API-triggered cam
 ---
 {% api %}
 # Schedule API-triggered campaigns
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /campaigns/trigger/schedule/create
 {% endapimethod %}
 
-> Use this endpoint to send dashboard created campaign messages via API-triggered delivery, allowing you to decide what action should trigger the message to be sent. 
+> Use this endpoint to send dashboard created campaign messages via API-triggered delivery, allowing you to decide what action should trigger the message to be sent.
 
 You can pass in `trigger_properties` that will be templated into the message itself.
 
@@ -62,13 +62,13 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | --------- | ---------| --------- | ----------- |
 |`campaign_id`|Required|String| See [campaign identifier]({{site.baseurl}}/api/identifier_types/)|
-| `send_id` | Optional | String | See [send identifier]({{site.baseurl}}/api/identifier_types/). | 
+| `send_id` | Optional | String | See [send identifier]({{site.baseurl}}/api/identifier_types/). |
 | `recipients` | Optional | Array of recipients objects | See [recipients object]({{site.baseurl}}/api/objects_filters/recipient_object/). |
 | `audience` | Optional | Connected audience object | See [connected audience]({{site.baseurl}}/api/objects_filters/connected_audience/). |
 |`broadcast`| Optional | Boolean | You must set `broadcast` to true when sending a message to an entire segment that a campaign or Canvas targets. This parameter defaults to false (as of August 31, 2017). <br><br> If `broadcast` is set to true, a `recipients` list cannot be included. However, use caution when setting `broadcast: true`, as unintentionally setting this flag may cause you to send your message to a larger than expected audience. |
 | `trigger_properties` | Optional | Object | Personalization key-value pairs for all users in this send. See [trigger properties]({{site.baseurl}}/api/objects_filters/trigger_properties_object/). |
 | `schedule` | Required | Schedule object | See [schedule object]({{site.baseurl}}/api/objects_filters/schedule_object/). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases.md b/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases.md
index 5dc815e32b6..d8300f06693 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases.md
@@ -10,11 +10,11 @@ description: "This article outlines details about the Schedule API-triggered Can
 ---
 {% api %}
 # Schedule API-triggered Canvases
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /canvas/trigger/schedule/create
 {% endapimethod %}
 
-> Use this endpoint to schedule Canvas messages via API-triggered delivery, allowing you to decide what action should trigger the message to be sent. 
+> Use this endpoint to schedule Canvas messages via API-triggered delivery, allowing you to decide what action should trigger the message to be sent.
 
 You can pass in `canvas_entry_properties` that will be templated into the messages sent by the first steps of the Canvas.
 
@@ -68,7 +68,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`broadcast`| Optional | Boolean | You must set `broadcast` to true when sending a message to an entire segment that a campaign or Canvas targets. This parameter defaults to false (as of August 31, 2017). <br><br> If `broadcast` is set to true, a `recipients` list cannot be included. However, use caution when setting `broadcast: true`, as unintentionally setting this flag may cause you to send your message to a larger than expected audience. |
 | `canvas_entry_properties` | Optional | Object | Personalization key-value pairs for all users in this send. See [Canvas entry properties object]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object). |
 | `schedule` | Required | Schedule object | See [schedule object]({{site.baseurl}}/api/objects_filters/schedule_object/). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -156,4 +156,4 @@ Authorization: Bearer YOUR-API-KEY-HERE
 }
 ```
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_messages.md b/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_messages.md
index 8031e9acd59..3251a74ab23 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_messages.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_messages.md
@@ -10,11 +10,11 @@ description: "This article outlines details about the Update scheduled messages
 ---
 {% api %}
 # Update scheduled messages
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /messages/schedule/update
 {% endapimethod %}
 
-> Use this endpoint to update scheduled messages. 
+> Use this endpoint to update scheduled messages.
 
 This endpoint accepts updates to either the `schedule` or `messages` parameter or both. Your request must contain at least one of those two keys.
 
@@ -53,7 +53,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | `schedule_id` | Required | String | The `schedule_id` to update (obtained from the response to create schedule). |
 |`schedule` | Optional | Object | See [schedule object]({{site.baseurl}}/api/objects_filters/schedule_object/). |
 |`messages` | Optional | Object | See [available messaging objects]({{site.baseurl}}/api/objects_filters/#messaging-objects). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns.md b/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns.md
index c2297d9ac91..cb951761dce 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns.md
@@ -9,7 +9,7 @@ description: "This article outlines details about the Update scheduled API-trigg
 ---
 {% api %}
 # Update scheduled API-triggered campaigns
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /campaigns/trigger/schedule/update
 {% endapimethod %}
 
@@ -55,7 +55,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`campaign_id`|Required|String| See [campaign identifier]({{site.baseurl}}/api/identifier_types/)|
 | `schedule_id` | Required | String | The `schedule_id` to update (obtained from the response to create a schedule). |
 |`schedule` | Required | Object | See [schedule object]({{site.baseurl}}/api/objects_filters/schedule_object/). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases.md b/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases.md
index af41b9a4f4e..e6ccf7c1fab 100644
--- a/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases.md
+++ b/_docs/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases.md
@@ -10,18 +10,18 @@ description: "This article outlines details about the Update scheduled API-trigg
 ---
 {% api %}
 # Update scheduled API-triggered Canvases
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /canvas/trigger/schedule/update
 {% endapimethod %}
 
-> Use this endpoint to update scheduled API-triggered Canvases that were created in the dashboard. 
+> Use this endpoint to update scheduled API-triggered Canvases that were created in the dashboard.
 
 This allows you to decide what action should trigger the message to be sent. You can pass in `trigger_properties` that will be templated into the message itself.
 
 Note that to send messages with this endpoint, you must have a Canvas ID, created when you build a [Canvas]({{site.baseurl}}/api/identifier_types/#canvas-api-identifier).
 
-Any schedule will completely overwrite the one that you provided in the create schedule request or in previous update schedule requests. 
-  - For example, if you originally provide `"schedule" : {"time" : "2015-02-20T13:14:47", "in_local_time" : true}` and then in your update you provide `"schedule" : {"time" : "2015-02-20T14:14:47"}`, your message will now be sent at the provided time in UTC, not in the user's local time. 
+Any schedule will completely overwrite the one that you provided in the create schedule request or in previous update schedule requests.
+  - For example, if you originally provide `"schedule" : {"time" : "2015-02-20T13:14:47", "in_local_time" : true}` and then in your update you provide `"schedule" : {"time" : "2015-02-20T14:14:47"}`, your message will now be sent at the provided time in UTC, not in the user's local time.
   - Scheduled triggers that are updated very close to or during the time they were supposed to be sent will be updated with best efforts, so last-second changes could be applied to all, some, or none of your targeted users.
 
 {% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#8fdf158b-ce20-41d8-80e4-a9300a6706d4 {% endapiref %}
@@ -58,7 +58,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`canvas_id`|Required|String| See [Canvas identifier]({{site.baseurl}}/api/identifier_types/). |
 | `schedule_id` | Optional | String | The `schedule_id` to update (obtained from the response to create schedule). |
 |`schedule` | Required | Object | See [schedule object]({{site.baseurl}}/api/objects_filters/schedule_object/). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/messaging/send_messages/post_create_send_ids.md b/_docs/_api/endpoints/messaging/send_messages/post_create_send_ids.md
index 81dde309962..1e8de27e3d9 100644
--- a/_docs/_api/endpoints/messaging/send_messages/post_create_send_ids.md
+++ b/_docs/_api/endpoints/messaging/send_messages/post_create_send_ids.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Create send IDs Braze endp
 /sends/id/create
 {% endapimethod %}
 
-> Use this endpoint to create send IDs that can be used to send messages and track message performance programmatically, without campaign creation for each send. 
+> Use this endpoint to create send IDs that can be used to send messages and track message performance programmatically, without campaign creation for each send.
 
 Using the send identifier to track and send messages is useful if you are planning to programmatically generate and send content.
 
@@ -48,7 +48,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | --------- | ---------| --------- | ----------- |
 | `campaign_id` | Required | String | See [campaign identifier]({{site.baseurl}}/api/identifier_types/). |
 |`send_id`| Optional | String | See [send identifier]({{site.baseurl}}/api/identifier_types/). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/messaging/send_messages/post_send_messages.md b/_docs/_api/endpoints/messaging/send_messages/post_send_messages.md
index f9a4a704ea9..b123435c3fe 100644
--- a/_docs/_api/endpoints/messaging/send_messages/post_send_messages.md
+++ b/_docs/_api/endpoints/messaging/send_messages/post_send_messages.md
@@ -10,11 +10,11 @@ description: "This article outlines details about the Send messages immediately
 ---
 {% api %}
 # Send messages immediately via API only
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /messages/send
 {% endapimethod %}
 
-> Use this endpoint to send immediate messages to designated users via the Braze API. 
+> Use this endpoint to send immediate messages to designated users via the Braze API.
 
 Be sure to include Messaging Objects in your body to complete your requests.
 
@@ -80,7 +80,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`override_frequency_capping`| Optional | Boolean | Ignore `frequency_capping` for campaigns, defaults to `false`. |
 |`recipient_subscription_state`| Optional | String | Use this to send messages to only users who have opted in (`opted_in`), only users who have subscribed or are opted in (`subscribed`) or to all users, including unsubscribed users (`all`). <br><br>Using `all` users is useful for transactional email messaging. Defaults to `subscribed`. |
 |`messages`| Optional | Messaging objects | See [available messaging objects]({{site.baseurl}}/api/objects_filters/#messaging-objects). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -160,4 +160,3 @@ curl --location --request POST 'https://rest.iad-01.braze.com/messages/send' \
 Message sending endpoint responses will include the message's `dispatch_id` for reference back to the dispatch of the message. The `dispatch_id` is the ID of the message dispatch, meaning the unique ID for each "transmission" sent from Braze. For more information, refer to [Dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
 
 {% endapi %}
-
diff --git a/_docs/_api/endpoints/messaging/send_messages/post_send_transactional_message.md b/_docs/_api/endpoints/messaging/send_messages/post_send_transactional_message.md
index 68f6a4273ed..24caca72ce4 100644
--- a/_docs/_api/endpoints/messaging/send_messages/post_send_transactional_message.md
+++ b/_docs/_api/endpoints/messaging/send_messages/post_send_transactional_message.md
@@ -15,7 +15,7 @@ description: "This article outlines details about the Send transactional email m
 /transactional/v1/campaigns/{campaign_id}/send
 {% endapimethod %}
 
-> Use this endpoint to send immediate, one-off transactional messages to a designated user. 
+> Use this endpoint to send immediate, one-off transactional messages to a designated user.
 
 This endpoint is used alongside the creation of a Braze [Transactional Email campaign]({{site.baseurl}}/api/api_campaigns/transactional_campaigns) and corresponding campaign ID.
 
@@ -40,7 +40,7 @@ To use this endpoint, you'll need to generate an API key with the `transactional
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `campaign_id` | Required | String | ID of the campaign |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request body
 
@@ -70,7 +70,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`external_send_id`| Optional | String |  A Base64 compatible string. Validated against the following regex:<br><br> `/^[a-zA-Z0-9-_+\/=]+$/` <br><br>This optional field allows you to pass an internal identifier for this particular send, which will be included in events sent from the Transactional HTTP event postback. When passed, this identifier will also be used as a deduplication key, which Braze will store for 24 hours. <br><br>Passing the same identifier in another request will not result in a new instance of a send by Braze for 24 hours.|
 |`trigger_properties`|Optional|Object|See [trigger properties]({{site.baseurl}}/api/objects_filters/trigger_properties_object/). Personalization key-value pairs that will apply to the user in this request. |
 |`recipient`|Required|Object| The user you are targeting this message to. Can contain `attributes` and a single `external_user_id` or `user_alias`.<br><br>Note that if you provide an external user ID that doesn't already exist in Braze, passing any fields to the `attributes` object will create this user profile in Braze and send this message to the newly created user. <br><br>If you send multiple requests to the same user with different data in the `attributes` object, `first_name`, `last_name`, and `email` attributes will be updated synchronously and templated into your message. Custom attributes don't have this same protection, so proceed with caution when updating a user through this API and passing different custom attribute values in quick succession.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -91,7 +91,7 @@ curl -X POST \
   https://rest.iad-01.braze.com/transactional/v1/campaigns/{campaign_id}/send
 ```
 
-## Response 
+## Response
 
 The Send transactional email endpoint will respond with the message's `dispatch_id` which represents the instance of this message send. This identifier can be used along with events from the Transactional HTTP event postback to trace the status of an individual email sent to a single user.
 
@@ -117,10 +117,10 @@ The endpoint may also return an error code and a human-readable message in some
 | `The campaign is archived. Unarchive the campaign in order for trigger requests to take effect.` | The campaign ID provided corresponds to an archived campaign. |
 | `The campaign is paused. Resume the campaign in order for trigger requests to take effect.` | The campaign ID provided corresponds to a paused campaign. |
 | `campaign_id must be a string of the campaign api identifier` | The campaign ID provided is not a valid format. |
-| `Error authenticating credentials` | The API key provided is invalid | 
-| `Invalid whitelisted IPs `| The IP address sending the request is not on the IP whitelist (if it is being used) | 
+| `Error authenticating credentials` | The API key provided is invalid |
+| `Invalid whitelisted IPs `| The IP address sending the request is not on the IP whitelist (if it is being used) |
 | `You do not have permission to access this resource` | The API key used does not have permission to take this action |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Most endpoints at Braze have a rate limit implementation that will return a 429 response code if you have made too many requests. The transactional sending endpoint works differently—if you exceed your allotted rate limit, our system will continue to ingest the API calls, return success codes, and send the messages, however those messages may not be subject to the contractual SLA for the feature. Please reach out if you need more information about this functionality.
 
@@ -170,7 +170,7 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), this page
 | `aborted` | Braze was unable to successfully dispatch the message due to the user not having an emailable address, or Liquid abort logic was called in the message body. All aborted events include a `reason` field within the metadata object indicating why the message was aborted |
 |`delivered`| Message was accepted by the user's email inbox provider |
 |`bounced`| Message was rejected by the user's email inbox provider. All bounced events include a `reason` field within the metadata object reflecting the bounce error code provided by the inbox provider |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Example postback
 ```json
@@ -239,4 +239,3 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), this page
 
 
 {% endapi %}
-
diff --git a/_docs/_api/endpoints/messaging/send_messages/post_send_triggered_campaigns.md b/_docs/_api/endpoints/messaging/send_messages/post_send_triggered_campaigns.md
index ada578585f7..5c521e091bb 100644
--- a/_docs/_api/endpoints/messaging/send_messages/post_send_triggered_campaigns.md
+++ b/_docs/_api/endpoints/messaging/send_messages/post_send_triggered_campaigns.md
@@ -10,11 +10,11 @@ description: "This article outlines details about the Send campaigns via API-tri
 ---
 {% api %}
 # Send campaign messages via API-triggered delivery
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /campaigns/trigger/send
 {% endapimethod %}
 
-> Use this endpoint to send immediate, one-off messages to designated users via API-triggered delivery. 
+> Use this endpoint to send immediate, one-off messages to designated users via API-triggered delivery.
 
 API-triggered delivery allows you to house message content inside of the Braze dashboard while dictating when a message is sent, and to whom via your API.
 
@@ -48,9 +48,11 @@ Authorization: Bearer YOUR-REST-API-KEY
   "recipients": (optional, array; if not provided and broadcast is not set to `false`, message will send to the entire segment targeted by the campaign)
     [
       {
-      // Either "external_user_id" or "user_alias" is required. Requests must specify only one.
+      // Either "external_user_id" or "user_alias" or "email" is required. Requests must specify only one.
       "user_alias": (optional, user alias object) user alias of user to receive message,
       "external_user_id": (optional, string) external identifier of user to receive message,
+      "email": (optional, string) email address of user to receive message,
+      "prioritization": (optional, array) prioritization array; required when using email,
       "trigger_properties": (optional, object) personalization key-value pairs that will apply to this user (these key-value pairs will override any keys that conflict with the parent trigger_properties),
       "send_to_existing_only": (optional, boolean) defaults to true, can't be used with user aliases; if set to `false`, an attributes object must also be included,
       "attributes": (optional, object) fields in the attributes object will create or update an attribute of that name with the given value on the specified user profile before the message is sent and existing values will be overwritten
@@ -77,12 +79,16 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`audience`| Optional | Connected audience object| See [connected audience]({{site.baseurl}}/api/objects_filters/connected_audience/). |
 |`recipients`| Optional | Array | See [recipients object]({{site.baseurl}}/api/objects_filters/recipient_object/).<br><br>If `send_to_existing_only` is `false`, an attribute object must be included.<br><br>If `recipients` is not provided and `broadcast` is set to true, the message will send to the entire segment targeted by the campaign. |
 |`attachments`| Optional | Array | If `broadcast` is set to true, then `attachments` list cannot be included. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 - The recipients array may contain up to 50 objects, with each object containing a single `external_user_id` string and `trigger_properties` object.
-- When `send_to_existing_only` is `true`, Braze will only send the message to existing users. However, this flag can't be used with user aliases. 
+- When `send_to_existing_only` is `true`, Braze will only send the message to existing users. However, this flag can't be used with user aliases.
 - When `send_to_existing_only` is `false`, an attribute must be included. Braze will create a user with the `id` and attributes before sending the message.
 
+{% alert important %}
+Specifying a recipient by email address is currently in early access. Contact your customer success manager if you're interested in participating in this early access.
+{% endalert %}
+
 A user's subscription group status can be updated via the inclusion of a `subscription_groups` parameter within the `attributes` object. For more details, refer to [User attributes object]({{site.baseurl}}/api/objects_filters/user_attributes_object).
 
 ## Example request
@@ -161,7 +167,7 @@ curl --location --request POST 'https://rest.iad-01.braze.com/campaigns/trigger/
       "file_name" : "YourFileName",
       "url" : "https://exampleurl.com/YourFileName.pdf"
     }
-  ] 
+  ]
 }'
 ```
 
@@ -173,7 +179,7 @@ If your request encounters a fatal error, refer to [Errors and responses]({{site
 
 ## Attributes object for campaigns
 
-Braze has a messaging object called `attributes` that will allow you to add, create, or update attributes and values for a user before you send them an API-triggered campaign. Using the `campaign/trigger/send` endpoint as this API call will process the user attributes object before it processes and sends the campaign. This helps minimize the risk of there being issues caused by [race conditions]({{site.baseurl}}/help/best_practices/race_conditions/). 
+Braze has a messaging object called `attributes` that will allow you to add, create, or update attributes and values for a user before you send them an API-triggered campaign. Using the `campaign/trigger/send` endpoint as this API call will process the user attributes object before it processes and sends the campaign. This helps minimize the risk of there being issues caused by [race conditions]({{site.baseurl}}/help/best_practices/race_conditions/).
 
 {% alert important %}
 Looking for the Canvas version of this endpoint? Check out [Sending Canvas messages via API-triggered delivery]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/#create-send-endpoint).
diff --git a/_docs/_api/endpoints/messaging/send_messages/post_send_triggered_canvases.md b/_docs/_api/endpoints/messaging/send_messages/post_send_triggered_canvases.md
index d84f7f9ef3a..d146f3f1741 100644
--- a/_docs/_api/endpoints/messaging/send_messages/post_send_triggered_canvases.md
+++ b/_docs/_api/endpoints/messaging/send_messages/post_send_triggered_canvases.md
@@ -10,11 +10,11 @@ description: "This article outlines details about the Send Canvases via API-trig
 ---
 {% api %}
 # Send Canvas messages via API-triggered delivery
-{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
 /canvas/trigger/send
 {% endapimethod %}
 
-> Use this endpoint to send Canvas messages via API-triggered delivery. 
+> Use this endpoint to send Canvas messages via API-triggered delivery.
 
 API-triggered Delivery allows you to store message content in the Braze dashboard while dictating when a message is sent, and to whom via your API.
 
@@ -46,9 +46,11 @@ Authorization: Bearer YOUR-REST-API-KEY
   // Including 'audience' will only send to users in the audience
   "recipients": (optional, array; if not provided and broadcast is not set to 'false', message will send to the entire segment targeted by the Canvas)
     [{
-      // Either "external_user_id" or "user_alias" is required. Requests must specify only one.
+      // Either "external_user_id" or "user_alias" or "email" is required. Requests must specify only one.
       "user_alias": (optional, user alias object) user alias of user to receive message,
       "external_user_id": (optional, string) external identifier of user to receive message,
+      "email": (optional, string) email address of user to receive message,
+      "prioritization": (optional, array) prioritization array; required when using email,
       "canvas_entry_properties": (optional, object) personalization key-value pairs that will apply to this user (these key-value pairs will override any keys that conflict with the parent `canvas_entry_properties`)
       "send_to_existing_only": (optional, boolean) defaults to true, can't be used with user aliases
       "attributes": (optional, object) fields in the attributes object will create or update an attribute of that name with the given value on the specified user profile before the message is sent and existing values will be overwritten
@@ -66,10 +68,14 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`broadcast`| Optional | Boolean | You must set `broadcast` to true when sending a message to an entire segment that a campaign or Canvas targets. This parameter defaults to false (as of August 31, 2017). <br><br> If `broadcast` is set to true, a `recipients` list cannot be included. However, use caution when setting `broadcast: true`, as unintentionally setting this flag may cause you to send your message to a larger than expected audience. |
 |`audience`| Optional| Connected audience object | See [Connected audience]({{site.baseurl}}/api/objects_filters/connected_audience/). |
 |`recipients`| Optional | Array | See [Recipients object]({{site.baseurl}}/api/objects_filters/recipient_object/). If not provided and `broadcast` is set to true, the message will send to the entire segment targeted by the Canvas.<br><br> The `recipients` array may contain up to 50 objects, with each object containing a single `external_user_id` string and `canvas_entry_properties` object. Either `external_user_id` or `user_alias` is required for this call. Requests must specify only one. <br><br> When `send_to_existing_only` is `true`, Braze will only send the message to existing users—however this flag can't be used with user aliases. When `send_to_existing_only` is `false` and a user with the given `id` does not exist, Braze will create a user with that ID and attributes before sending the message.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 Customers using the API for server-to-server calls may need to allowlist the appropriate API URL if they're behind a firewall.
 
+{% alert important %}
+Specifying a recipient by email address is currently in early access. Contact your customer success manager if you're interested in participating in this early access.
+{% endalert %}
+
 {% alert note %}
 If you include both specific users in your API call and a target segment in the dashboard, the message will send to specifically the user profiles that are both in the API call and qualify for the segment filters.
 {% endalert %}
@@ -152,12 +158,12 @@ Message sending endpoint responses will include the message's `dispatch_id` for
 
 ### Example success response
 
-The status code `201` could return the following response body. If the Canvas is archived, stopped, or paused, the Canvas will not be sent through this endpoint. 
+The status code `201` could return the following response body. If the Canvas is archived, stopped, or paused, the Canvas will not be sent through this endpoint.
 
 ```
 {
-  "notice": "The Canvas is paused. Resume the Canvas to ensure trigger requests will take effect.", 
-  "dispatch_id": "example_dispatch_id", 
+  "notice": "The Canvas is paused. Resume the Canvas to ensure trigger requests will take effect.",
+  "dispatch_id": "example_dispatch_id",
   "message": "success"
 }
 ```
@@ -175,4 +181,3 @@ Looking for the campaigns version of this endpoint? Check out [Sending campaign
 {% endalert %}
 
 {% endapi %}
-
diff --git a/_docs/_api/endpoints/preference_center/get_create_url_preference_center.md b/_docs/_api/endpoints/preference_center/get_create_url_preference_center.md
index 64b0cdce73e..e848909abaf 100644
--- a/_docs/_api/endpoints/preference_center/get_create_url_preference_center.md
+++ b/_docs/_api/endpoints/preference_center/get_create_url_preference_center.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Generate preference center
 /preference_center/v1/{preferenceCenterExternalID}/url/{userID}
 {% endapimethod %}
 
-> Use this endpoint to generate a URL for a preference center. 
+> Use this endpoint to generate a URL for a preference center.
 
 Each preference center URL is unique to each user.
 
@@ -34,6 +34,7 @@ This endpoint has a rate limit of 1,000 requests per minute, per workspace.
 | --------- | ---------| --------- | ----------- |
 |`preferenceCenterExternalID`| Required | String | The ID for your preference center. |
 |`userID`| Required | String | The user ID. |
+{:  role="presentation" }
 
 ## Request parameters
 
@@ -41,7 +42,7 @@ This endpoint has a rate limit of 1,000 requests per minute, per workspace.
 | --------- | ---------| --------- | ----------- |
 |`preference_center_api_id`| Required | String | The ID for your preference center. |
 |`external_id`| Required | String | The external ID for a user. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
@@ -50,7 +51,7 @@ curl --location --request GET 'https://rest.iad-01.braze.com/preference_center/v
 --header 'Authorization: Bearer YOUR-API-KEY-HERE'
 ```
 
-## Response 
+## Response
 
 ```json
 {
@@ -62,4 +63,4 @@ curl --location --request GET 'https://rest.iad-01.braze.com/preference_center/v
 
 {% alert note %}
 This endpoint only generates URLs for the new preference center (such as preference centers created via API or the drag-and-drop editor).
-{% endalert %}
\ No newline at end of file
+{% endalert %}
diff --git a/_docs/_api/endpoints/preference_center/get_view_details_preference_center.md b/_docs/_api/endpoints/preference_center/get_view_details_preference_center.md
index 8e81a8905af..f06d5703c51 100644
--- a/_docs/_api/endpoints/preference_center/get_view_details_preference_center.md
+++ b/_docs/_api/endpoints/preference_center/get_view_details_preference_center.md
@@ -31,6 +31,7 @@ This endpoint has a rate limit of 1,000 requests per minute, per workspace.
 | Parameter | Required | Data Type | Description |
 | --------- | ---------| --------- | ----------- |
 |`preferenceCenterExternalID`| Required | String | The ID for your preference center. |
+{: role="presentation" }
 
 ## Request parameters
 
@@ -43,8 +44,8 @@ curl --location -g --request GET https://rest.iad-01.braze.com/preference_center
 --header 'Authorization: Bearer YOUR-REST-API-KEY'
 ```
 
-## Response 
-```json 
+## Response
+```json
 {
   "name": "My Preference Center",
   "preference_center_api_id": "preference_center_api_id",
diff --git a/_docs/_api/endpoints/preference_center/post_create_preference_center.md b/_docs/_api/endpoints/preference_center/post_create_preference_center.md
index 17f8c026df2..74567e2d473 100644
--- a/_docs/_api/endpoints/preference_center/post_create_preference_center.md
+++ b/_docs/_api/endpoints/preference_center/post_create_preference_center.md
@@ -56,7 +56,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`confirmation_page_html`| Required | String | The HTML for the confirmation page. |
 |`state` | Optional | String | Choose `active` or `draft`. Defaults to `active` if not specified. |
 |`options` | Optional | Object | Attributes: `meta-viewport-content`. When present, a `viewport` meta tag will be added to the page with `content= <value of attribute>`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 The preference center name can't be edited after it's created.
@@ -74,7 +74,7 @@ Refer to the following Liquid tags that can be included in your HTML to generate
 | --------- | ---------|
 |`{{subscribed_state.${email_global}}}`| Get the global email subscribed state for the user (such as "opted_in", "subscribed", or "unsubscribed". |
 |`{{subscribed_state.${<subscription_group_id>}}}`| Get the subscribed state of the specified subscription group for the user (such as "subscribed" or "unsubscribed"). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Form inputs and action
 
@@ -83,7 +83,7 @@ Refer to the following Liquid tags that can be included in your HTML to generate
 |`{% form_field_name :email_global_state %}`| Indicates that a specific form input element corresponds to the user's global email subscribed state. The user's selection state should be "opted_in", "subscribed", or "unsubscribed" when the form is submitted with selection data for the global email subscribed state. If it's a checkbox, the user will either be "opted_in" or "unsubscribed". For a hidden input, the "subscribed" state will also be valid. |
 |`{% form_field_name :subscription_group <subscription_group_id> %}`| Indicates that a specific form input element corresponds to a given subscription group. The user's selection state should be either "subscribed" or "unsubscribed" when the form is submitted with selection data for a specific subscription group. |
 |`{{preference_center_submit_url}}`| Generates URL for form submission. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endraw %}
 
@@ -102,7 +102,7 @@ Refer to the following Liquid tags that can be included in your HTML to generate
 ```
 {% endraw %}
 
-### HTML with form inputs 
+### HTML with form inputs
 
 {% raw %}
 ```
@@ -179,7 +179,7 @@ Refer to the following Liquid tags that can be included in your HTML to generate
       "
     >
       <div class="content" style="margin-left: 20px; margin-right: 20px">
-        
+
         <div>
           <h1
             style="color: #3accdd; font-size: 27px; font-weight: 400; margin-bottom: 40px; margin-top: 0"
@@ -205,7 +205,7 @@ Refer to the following Liquid tags that can be included in your HTML to generate
     Sub Group 1
   </label>
   <p class="subscription-group" style="font-size: 13px; line-height: 1.4em; min-height: 20px; padding-right: 20px; margin: 0 0 3px 23px;">
-    
+
   </p>
 </div>
 <div class="row" style="border-top-width: 1px; border-top-color: #dddde2; border-top-style: solid; background-color: #fff; padding: 15px 10px 14px;border-bottom: 1px solid rgb(221, 221, 226);">
@@ -215,7 +215,7 @@ Refer to the following Liquid tags that can be included in your HTML to generate
     Sub Group 2
   </label>
   <p class="subscription-group" style="font-size: 13px; line-height: 1.4em; min-height: 20px; padding-right: 20px; margin: 0 0 3px 23px;">
-    
+
   </p>
 </div>
 <div class="row" style="border-top-width: 1px; border-top-color: #dddde2; border-top-style: solid; background-color: #fff; padding: 15px 10px 14px;border-bottom: 1px solid rgb(221, 221, 226);">
@@ -225,7 +225,7 @@ Refer to the following Liquid tags that can be included in your HTML to generate
     Sub Group 3
   </label>
   <p class="subscription-group" style="font-size: 13px; line-height: 1.4em; min-height: 20px; padding-right: 20px; margin: 0 0 3px 23px;">
-    
+
   </p>
 </div>
 </div>
diff --git a/_docs/_api/endpoints/preference_center/put_update_preference_center.md b/_docs/_api/endpoints/preference_center/put_update_preference_center.md
index 85832694d7d..02383f1fcd3 100644
--- a/_docs/_api/endpoints/preference_center/put_update_preference_center.md
+++ b/_docs/_api/endpoints/preference_center/put_update_preference_center.md
@@ -31,7 +31,7 @@ This endpoint has a rate limit of 10 requests per minute, per workspace.
 | 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}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 
 ## Request body
@@ -62,7 +62,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`confirmation_page_html`| Required | String | The HTML for the confirmation page. |
 |`state` | Optional | String | Choose `active` or `draft`.|
 |`options` | Optional | Object | Attributes: `meta-viewport-content`. When present, a `viewport` meta tag will be added to the page with `content= <value of attribute>`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/scim/delete_existing_dashboard_user.md b/_docs/_api/endpoints/scim/delete_existing_dashboard_user.md
index 5fe12691056..c5e55d7c36b 100644
--- a/_docs/_api/endpoints/scim/delete_existing_dashboard_user.md
+++ b/_docs/_api/endpoints/scim/delete_existing_dashboard_user.md
@@ -34,7 +34,7 @@ To use this endpoint, you'll need a SCIM token. For more information, refer to [
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `id` | Required | String | The user's resource ID. This parameter is returned by the  `POST` `/scim/v2/Users/` or `GET`  `/scim/v2/Users?filter=userName eq "user@test.com"` methods. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request body
 
diff --git a/_docs/_api/endpoints/scim/get_search_existing_dashboard_user.md b/_docs/_api/endpoints/scim/get_search_existing_dashboard_user.md
index 805c914f3ce..bb69bfa4506 100644
--- a/_docs/_api/endpoints/scim/get_search_existing_dashboard_user.md
+++ b/_docs/_api/endpoints/scim/get_search_existing_dashboard_user.md
@@ -36,7 +36,7 @@ To use this endpoint, you'll need a SCIM token. For more information, refer to [
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `userName@example.com` | Required | String | The user's email. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request parameters
 
diff --git a/_docs/_api/endpoints/scim/get_see_user_account_information.md b/_docs/_api/endpoints/scim/get_see_user_account_information.md
index 78c2cac77f1..58bc59db3bc 100644
--- a/_docs/_api/endpoints/scim/get_see_user_account_information.md
+++ b/_docs/_api/endpoints/scim/get_see_user_account_information.md
@@ -32,7 +32,7 @@ To use this endpoint, you'll need a SCIM token. For more information, refer to [
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `id` | Required | String | The user's resource ID. This parameter is returned by the  `POST` `/scim/v2/Users/` or `GET`  `/scim/v2/Users?filter=userName eq "user@test.com"` methods. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request body
 ```json
diff --git a/_docs/_api/endpoints/scim/post_create_user_account.md b/_docs/_api/endpoints/scim/post_create_user_account.md
index d6a5f00a6cf..fe92700c18e 100644
--- a/_docs/_api/endpoints/scim/post_create_user_account.md
+++ b/_docs/_api/endpoints/scim/post_create_user_account.md
@@ -16,7 +16,7 @@ description: "This article outlines details about the Create new dashboard user
 /scim/v2/Users
 {% endapimethod %}
 
-> Use this endpoint to create a new dashboard user account by specifying email, given and family names, permissions (for setting permissions at the company, workspace, and team level). 
+> Use this endpoint to create a new dashboard user account by specifying email, given and family names, permissions (for setting permissions at the company, workspace, and team level).
 
 {% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#768a3c9d-ce1d-44fc-a0e4-d556b09f7aa3 {% endapiref %}
 
@@ -78,7 +78,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | `name` | Required | JSON object | This object contains the user's given name and family name. |
 | `department` | Required | String | Valid department string from the [department string documentation]({{site.baseurl}}/scim_api_appendix/#department-strings). |
 | `permissions` | Required | JSON object | Permissions object as described in the [permissions object documentation]({{site.baseurl}}/scim_api_appendix/#permissions-object). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```json
@@ -106,7 +106,7 @@ curl --location --request POST 'https://rest.iad-01.braze.com/scim/v2/Users' \
                          "teamPermissions": ["basic_access","export_user_data"]
                     }
                 ]
-            } 
+            }
         ]
     }
 }
@@ -138,7 +138,7 @@ curl --location --request POST 'https://rest.iad-01.braze.com/scim/v2/Users' \
                          "teamPermissions": ["basic_access","export_user_data"]
                     }
                 ]
-            } 
+            }
         ]
     }
 }
@@ -155,7 +155,7 @@ curl --location --request POST 'https://rest.iad-01.braze.com/scim/v2/Users' \
 | `permissions` | JSON object | Permissions object as described in the [permissions object documentation]({{site.baseurl}}/scim_api_appendix/#permissions-object). |
 | `id` | String | ID generated by Braze that is used for searching and managing user accounts. |
 | `lastSignInAt` | String | Date of last successful sign-on in UTC time. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Error states
 
@@ -174,6 +174,3 @@ Content-Type: text/json;charset=UTF-8
 ```
 
 {% endapi %}
-
-
-
diff --git a/_docs/_api/endpoints/scim/put_update_existing_user_account.md b/_docs/_api/endpoints/scim/put_update_existing_user_account.md
index ef729a23aca..b92fc07a6be 100644
--- a/_docs/_api/endpoints/scim/put_update_existing_user_account.md
+++ b/_docs/_api/endpoints/scim/put_update_existing_user_account.md
@@ -15,7 +15,7 @@ description: "This article outlines details about the Update existing dashboard
 /scim/v2/Users/{id}
 {% endapimethod %}
 
-> Use this endpoint to update an existing dashboard user account by specifying the resource `id` returned by the SCIM [`POST`]({{site.baseurl}}/scim/post_create_user_account/) method. 
+> Use this endpoint to update an existing dashboard user account by specifying the resource `id` returned by the SCIM [`POST`]({{site.baseurl}}/scim/post_create_user_account/) method.
 
 It allows you to update of given and family names, permissions (for setting permissions at the company, workspace, and team level) and department.
 
@@ -36,7 +36,7 @@ To use this endpoint, you'll need a SCIM token. For more information, refer to [
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `id` | Required | String | The user's resource ID. This parameter is returned by the  `POST` `/scim/v2/Users/` or `GET`  `/scim/v2/Users?filter=userName eq "user@test.com"` methods. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Request body
 ```
@@ -62,7 +62,7 @@ Authorization: Bearer YOUR-REST-API-KEY
                     {
                          "teamName": "Test Team",
                          "teamPermissions": ["admin"]
-                    } 
+                    }
                 ]
             },
             {
@@ -72,7 +72,7 @@ Authorization: Bearer YOUR-REST-API-KEY
                         "appGroupPermissionSetName":  "Test Permission Set"
                     }
                 ]
-            } 
+            }
         ]
    }
 }
@@ -86,7 +86,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | `name` | Required | JSON object | This object contains the user's given name and family name. |
 | `department` | Required | String | Valid department string from the [department string documentation]({{site.baseurl}}/scim_api_appendix/#department-strings). |
 | `permissions` | Required | JSON object | Permissions object as described in the [permissions object documentation]({{site.baseurl}}/scim_api_appendix/#permissions-object). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 
 ## Example request
@@ -114,7 +114,7 @@ curl --location --request PUT 'https://rest.iad-01.braze.com/scim/v2/Users/dfa24
                          "teamPermissions": ["admin"]
                     }
                 ]
-            } 
+            }
         ]
     }
 }
@@ -146,7 +146,7 @@ curl --location --request PUT 'https://rest.iad-01.braze.com/scim/v2/Users/dfa24
                          "teamPermissions": ["admin"]
                     }
                 ]
-            } 
+            }
         ]
     }
 }
@@ -167,4 +167,3 @@ Content-Type: text/html; charset=UTF-8
 ```
 
 {% endapi %}
-
diff --git a/_docs/_api/endpoints/sms/get_query_invalid_numbers.md b/_docs/_api/endpoints/sms/get_query_invalid_numbers.md
index a771e4a9aa4..6467e008110 100644
--- a/_docs/_api/endpoints/sms/get_query_invalid_numbers.md
+++ b/_docs/_api/endpoints/sms/get_query_invalid_numbers.md
@@ -35,7 +35,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `offset` | Optional | Integer | Optional beginning point in the list to retrieve from. |
 | `phone_numbers` | Optional <br>(see note) | Array of Strings in e.164 format | If provided, we will return the phone number if it has been found to be invalid. |
 | `reason` | Optional <br>(see note) | String | Available values are "provider_error" (provider error indicates phone cannot receive SMS) or "deactivated" (phone number has been deactivated). If omitted, all reasons are returned. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 You must provide either a `start_date` and an `end_date` OR `phone_numbers`. If you provide all three, `start_date`, `end_date`, and `phone_numbers`, we prioritize the given phone numbers and disregard the date range.
diff --git a/_docs/_api/endpoints/sms/post_remove_invalid_numbers.md b/_docs/_api/endpoints/sms/post_remove_invalid_numbers.md
index ea82229ccb0..b89156e0451 100644
--- a/_docs/_api/endpoints/sms/post_remove_invalid_numbers.md
+++ b/_docs/_api/endpoints/sms/post_remove_invalid_numbers.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Remove invalid phone numbe
 /sms/invalid_phone_numbers/remove
 {% endapimethod %}
 
-> Use this endpoint to remove "invalid" phone numbers from our invalid list. 
+> Use this endpoint to remove "invalid" phone numbers from our invalid list.
 
 This can be used to re-validate phone numbers after they have been marked as invalid.
 
@@ -46,7 +46,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | ----------|-----------| ---------|------ |
 | `phone_number` | Required | Array of strings in e.164 format | An array of up to 50 phone numbers to modify. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_api/endpoints/subscription_groups/get_list_user_subscription_group_status.md b/_docs/_api/endpoints/subscription_groups/get_list_user_subscription_group_status.md
index 6030d26f4c3..2c717df2ff9 100644
--- a/_docs/_api/endpoints/subscription_groups/get_list_user_subscription_group_status.md
+++ b/_docs/_api/endpoints/subscription_groups/get_list_user_subscription_group_status.md
@@ -47,7 +47,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `email` | Required* | String | The email address of the user. It can be passed as an array of strings with a maximum of 50.<br><br> Submitting both an email address and phone number (with no `external_id`) will result in an error. |
 | `phone` | Required* | String in [E.164](https://en.wikipedia.org/wiki/E.164) format | The phone number of the user. If email is not included, you must include at least one phone number (with a maximum of 50).<br><br> Submitting both an email address and phone number (with no `external_id`) will result in an error. |
 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 *One of `external_id` or `email` or `phone` is required for each user.
 
diff --git a/_docs/_api/endpoints/subscription_groups/get_list_user_subscription_groups.md b/_docs/_api/endpoints/subscription_groups/get_list_user_subscription_groups.md
index 32a50294779..171dd24fabc 100644
--- a/_docs/_api/endpoints/subscription_groups/get_list_user_subscription_groups.md
+++ b/_docs/_api/endpoints/subscription_groups/get_list_user_subscription_groups.md
@@ -45,7 +45,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/basics#rest-
 | `phone` | Required* | String in [E.164](https://en.wikipedia.org/wiki/E.164) format | The phone number of the user. Must include at least one phone number (with a maximum of 50). |
 | `limit` | Optional | Integer | The limit on the maximum number of results returned. Default (and maximum) `limit` is 100. |
 | `offset`  |  Optional | Integer | Number of templates to skip before returning the rest of the templates that fit the search criteria. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert tip %}
 If there are multiple users (multiple `external_ids`) who share the same email address, all users will be returned as a separate user (even if they have the same email address or subscription group).
diff --git a/_docs/_api/endpoints/subscription_groups/post_update_user_subscription_group_status.md b/_docs/_api/endpoints/subscription_groups/post_update_user_subscription_group_status.md
index ce7f07f4335..77283b06283 100644
--- a/_docs/_api/endpoints/subscription_groups/post_update_user_subscription_group_status.md
+++ b/_docs/_api/endpoints/subscription_groups/post_update_user_subscription_group_status.md
@@ -89,7 +89,7 @@ When creating new users via the [/users/track]({{site.baseurl}}/api/endpoints/us
 | `external_id` | Required* | Array of strings | The `external_id` of the user or users, may include up to 50 `id`s. |
 | `email` | Required* | String or array of strings | The email address of the user, can be passed as an array of strings. Must include at least one email address (with a maximum of 50). <br><br>If multiple users (`external_id`) in the same workspace share the same email address, then all users that share the email address are updated with the subscription group changes. |
 | `phone` | Required* | String in [E.164](https://en.wikipedia.org/wiki/E.164) format | The phone number of the user, can be passed as an array of strings. Must include at least one phone number (with a maximum of 50). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example requests
 
diff --git a/_docs/_api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2.md b/_docs/_api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2.md
index 0d8364931fc..b906bec1704 100644
--- a/_docs/_api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2.md
+++ b/_docs/_api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2.md
@@ -75,7 +75,7 @@ When creating new users via the [`/users/track` endpoint]({{site.baseurl}}/api/e
 | `external_ids` | Required* | Array of strings | The `external_id` of the user or users,  may include up to 50 `id`s. |
 | `emails` | Required* | String or array of strings | The email address of the user, can be passed as an array of strings. Must include at least one email address (with a maximum of 50). <br><br>If multiple users (`external_id`) in the same workspace share the same email address, all users that share the email address are updated with the subscription group changes. |
 | `phones` | Required* | String in [E.164](https://en.wikipedia.org/wiki/E.164) format | The phone numbers of the user, can be passed as an array of strings. Must include at least one phone number (with a maximum of 50). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 Note that you cannot include both `emails` and `phones` parameters. Also, `emails`, `phones`, and `external_ids` can all be sent individually.
diff --git a/_docs/_api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks.md b/_docs/_api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks.md
index 57da323e807..dda44bc5af9 100644
--- a/_docs/_api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks.md
+++ b/_docs/_api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks.md
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/api_key/) wi
 | `modified_before`  |  Optional | String in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format | Retrieve only Content Blocks updated at or before the given time. |
 | `limit` | Optional | Positive Number | Maximum number of Content Blocks to retrieve. Default to 100 if not provided, with a maximum acceptable value of 1000. |
 | `offset`  |  Optional | Positive Number | Number of Content Blocks to skip before returning rest of the templates that fit the search criteria. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -77,6 +77,6 @@ The following table lists possible returned errors and their associated troubles
 | `Content Block number limit exceeds maximum of 1000` | Change the `limit` parameter to an integer less than 1000. |
 | `Offset is invalid` | The `offset` parameter must be an integer greater than 0. |
 | Offset must be greater than 0 | Change the `offset` parameter to an integer greater than 0. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
diff --git a/_docs/_api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information.md b/_docs/_api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information.md
index 3024deba5dd..030db78102f 100644
--- a/_docs/_api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information.md
+++ b/_docs/_api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information.md
@@ -31,7 +31,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/api_key/) wi
 |---|---|---|---|
 | `content_block_id`  | Required | String | The Content Block identifier. <br><br>You can find this by either listing Content Block information through an API call or going to the [API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) page, then scrolling to the bottom and searching for your Content Block API identifier.|
 | `include_inclusion_data`  | Optional | Boolean | When set to `true`, the API returns back the Message Variation API identifier of campaigns and Canvases where this Content Block is included, to be used in subsequent calls.  The results exclude archived or deleted campaigns or Canvases. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
@@ -71,7 +71,7 @@ The following table lists possible returned errors and their associated troubles
 | `Content Block ID is invalid for this workspace` | This Content Block doesn't exist or is in a different company account or workspace. |
 | `Content Block has been deleted—content not available` | This Content Block, though it may have existed earlier, has been deleted. |
 | `Include Inclusion Data—error` | This parameter only accepts boolean values (true or false). Make sure the value for `include_inclusion_data` is not encapsulated in quotes (`""`), which causes the value to be sent as a string instead. See [request parameters](#request-parameters) for details. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 {% endapi %}
diff --git a/_docs/_api/endpoints/templates/content_blocks_templates/post_create_email_content_block.md b/_docs/_api/endpoints/templates/content_blocks_templates/post_create_email_content_block.md
index cfe5316668a..fd41174df13 100644
--- a/_docs/_api/endpoints/templates/content_blocks_templates/post_create_email_content_block.md
+++ b/_docs/_api/endpoints/templates/content_blocks_templates/post_create_email_content_block.md
@@ -51,7 +51,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 | `content` | Required | String | HTML or text content within the Content Block. |
 | `state` | Optional | String | Choose `active` or `draft`. Defaults to `active` if not specified. |
 | `tags` | Optional | Array of strings | [Tags]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) must already exist. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```json
@@ -102,7 +102,7 @@ The following table lists possible returned errors and their associated troubles
 | `Tags must be an array` | Tags must be formatted as an array of strings, for example `["marketing", "promotional", "transactional"]`. | |
 | `All tags must be strings` | Make sure your tags are encapsulated in quotes (`""`). |
 | `Some tags could not be found` | To add a tag when creating a Content Block, the tag must already exist in Braze. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 {% endapi %}
diff --git a/_docs/_api/endpoints/templates/content_blocks_templates/post_update_content_block.md b/_docs/_api/endpoints/templates/content_blocks_templates/post_update_content_block.md
index 9bfcd95f6c3..3f3291763eb 100644
--- a/_docs/_api/endpoints/templates/content_blocks_templates/post_update_content_block.md
+++ b/_docs/_api/endpoints/templates/content_blocks_templates/post_update_content_block.md
@@ -53,7 +53,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 | `content` | Optional | String | HTML or text content within Content Blocks.
 | `state` | Optional | String | Choose `active` or `draft`. Defaults to `active` if not specified. |
 | `tags` | Optional | Array of strings | [Tags]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) must already exist. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```json
@@ -61,7 +61,7 @@ curl --location --request POST 'https://rest.iad-01.braze.com/content_blocks/upd
 --header 'Content-Type: application/json' \
 --header 'Authorization: Bearer YOUR_REST_API_KEY' \
 --data-raw '{
-  "content_block_id" :"content_block_id", 
+  "content_block_id" :"content_block_id",
   "name": "content_block",
   "description": "This is my Content Block",
   "content": "HTML or text content within block",
@@ -107,7 +107,7 @@ The following table lists possible returned errors and their associated troubles
 | `Tags must be an array` | Tags must be formatted as an array of strings, for example `["marketing", "promotional", "transactional"]`. |
 | `All tags must be strings` | Make sure your tags are encapsulated in quotes (`""`). |
 | `Some tags could not be found` | To add a tag when creating a Content Block, the tag must already exist in Braze. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 {% endapi %}
diff --git a/_docs/_api/endpoints/templates/email_templates/get_list_email_templates.md b/_docs/_api/endpoints/templates/email_templates/get_list_email_templates.md
index e3c807643ff..afddcb48225 100644
--- a/_docs/_api/endpoints/templates/email_templates/get_list_email_templates.md
+++ b/_docs/_api/endpoints/templates/email_templates/get_list_email_templates.md
@@ -33,7 +33,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/api_key/) wi
 | `modified_before`  |  Optional | String in [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) format | Retrieve only templates updated at or before the given time. |
 | `limit` | Optional | Positive number | Maximum number of templates to retrieve. Default to 100 if not provided, with a maximum acceptable value of 1000. |
 | `offset`  |  Optional | Positive number | Number of templates to skip before returning rest of the templates that fit the search criteria. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
diff --git a/_docs/_api/endpoints/templates/email_templates/get_see_email_template_information.md b/_docs/_api/endpoints/templates/email_templates/get_see_email_template_information.md
index e2698e399ef..cb2c68feabc 100644
--- a/_docs/_api/endpoints/templates/email_templates/get_see_email_template_information.md
+++ b/_docs/_api/endpoints/templates/email_templates/get_see_email_template_information.md
@@ -34,7 +34,7 @@ To use this endpoint, you'll need an [API key]({{site.baseurl}}/api/api_key/) wi
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `email_template_id`  | Required | String | See [email template API identifier]({{site.baseurl}}/api/identifier_types/). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 {% raw %}
diff --git a/_docs/_api/endpoints/templates/email_templates/post_create_email_template.md b/_docs/_api/endpoints/templates/email_templates/post_create_email_template.md
index 80e66bc1d9f..1517f648806 100644
--- a/_docs/_api/endpoints/templates/email_templates/post_create_email_template.md
+++ b/_docs/_api/endpoints/templates/email_templates/post_create_email_template.md
@@ -13,7 +13,7 @@ description: "This article outlines details about the Create email templates Bra
 /templates/email/create
 {% endapimethod %}
 
-> Use this endpoint to create email templates on the Braze dashboard. 
+> Use this endpoint to create email templates on the Braze dashboard.
 
 These templates will be available on the **Templates & Media** page. The response from this endpoint will include a field for `email_template_id`, which can be used to update the template in subsequent API calls.
 
@@ -58,7 +58,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 |`preheader`|Optional|String|Email preheader used to generate previews in some clients.|
 |`tags`|Optional|String|[Tags]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) must already exist.|
 |`should_inline_css`|Optional|Boolean|Enables or disables the `inline_css` feature per template. If not provided, Braze will use the default setting for the app group. One of `true` or `false` is expected.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 
 ## Example request
@@ -88,6 +88,6 @@ The following table lists possible returned errors and their associated troubles
 | Some tags could not be found | To add a tag when creating an email template, the tag must already exist in Braze. |
 | Email must have valid Content Block names | The email might contain Content Blocks that don't exist in this environment. |
 | Invalid value for `should_inline_css`. One of `true` or `false` was expected | This parameter only accepts boolean values (true or false). Make sure the value for `should_inline_css` is not encapsulated in quotes (`""`), which causes the value to be sent as a string instead. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
diff --git a/_docs/_api/endpoints/templates/email_templates/post_update_email_template.md b/_docs/_api/endpoints/templates/email_templates/post_update_email_template.md
index 3f4e7d0e700..cb34c6682f0 100644
--- a/_docs/_api/endpoints/templates/email_templates/post_update_email_template.md
+++ b/_docs/_api/endpoints/templates/email_templates/post_update_email_template.md
@@ -14,7 +14,7 @@ description: "This article outlines details about the Update email template Braz
 /templates/email/update
 {% endapimethod %}
 
-> Use this endpoint to update email templates on the Braze dashboard. 
+> Use this endpoint to update email templates on the Braze dashboard.
 
 You can access an email template's `email_template_id` by navigating to it on the **Templates & Media** page. The [Create email template endpoint]({{site.baseurl}}/api/endpoints/templates/email_templates/post_create_email_template/) will also return an `email_template_id` reference.
 
@@ -61,7 +61,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 |`preheader`|Optional|String|Email preheader used to generate previews in some clients.|
 |`tags`|Optional|String|[Tags]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) must already exist.|
 |`should_inline_css`|Optional|Boolean|Enables or disables the `inline_css` feature per template. If not provided, Braze will use the default setting for the AppGroup. One of `true` or `false` is expected.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -90,6 +90,6 @@ The following table lists possible returned errors and their associated troubles
 | All tags must be strings | Make sure your tags are encapsulated in quotes (`""`). |
 | Some tags could not be found | To add a tag when creating an email template, the tag must already exist in Braze. |
 | Invalid value for `should_inline_css`. One of `true` or `false` was expected | This parameter only accepts boolean values (true or false). Make sure the value for `should_inline_css` is not encapsulated in quotes (`""`), which causes the value to be sent as a string instead. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
diff --git a/_docs/_api/endpoints/translations/get_bulk_translations_campaigns.md b/_docs/_api/endpoints/translations/get_bulk_translations_campaigns.md
index 0464e0694ba..5b06481753d 100644
--- a/_docs/_api/endpoints/translations/get_bulk_translations_campaigns.md
+++ b/_docs/_api/endpoints/translations/get_bulk_translations_campaigns.md
@@ -35,7 +35,7 @@ This endpoint has a rate limit of 250,000 requests per hour.
 | --------- | ---------| --------- | ----------- |
 |`campaign_id`| Required for translating a campaign | String | The ID of your campaign. |
 | `message_variation_id` | Required | String | The ID of your message. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 Note all translation IDs are considered universal unique identifiers (UUIDs), which can be found in **Multi-Language Support** settings or in the request response.
 
@@ -102,6 +102,6 @@ The following table lists possible returned errors and their associated troubles
 | `MULTI_LANGUAGE_NOT_ENABLED`            | Multi-language settings aren't turned on for your workspace.                       |
 | `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Only email campaigns or Canvas messages with emails can be translated.             |
 | `UNSUPPORTED_CHANNEL`                   | Only messages in email campaigns or Canvas messages with emails can be translated. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/translations/get_bulk_translations_canvases.md b/_docs/_api/endpoints/translations/get_bulk_translations_canvases.md
index f43cc53556b..1bddafb4d5d 100644
--- a/_docs/_api/endpoints/translations/get_bulk_translations_canvases.md
+++ b/_docs/_api/endpoints/translations/get_bulk_translations_canvases.md
@@ -35,7 +35,7 @@ This endpoint has a rate limit of 250,000 requests per hour.
 | --------- | ---------| --------- | ----------- |
 |`step_id`| Required | String | The ID of your Canvas step. |
 |`message_variation_id`| Required | String | The ID of your message. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 Note all translation IDs are considered universal unique identifiers (UUIDs), which can be found in **Multi-Language Support** settings or in the request response.
 
@@ -102,6 +102,6 @@ The following table lists possible returned errors and their associated troubles
 | `MULTI_LANGUAGE_NOT_ENABLED`            | Multi-language settings aren't turned on for your workspace.                       |
 | `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Only email campaigns or Canvas messages with emails can be translated.             |
 | `UNSUPPORTED_CHANNEL`                   | Only messages in email campaigns or Canvas messages with emails can be translated. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/translations/get_translation_campaign.md b/_docs/_api/endpoints/translations/get_translation_campaign.md
index 5a431f941d3..96c15b183f7 100644
--- a/_docs/_api/endpoints/translations/get_translation_campaign.md
+++ b/_docs/_api/endpoints/translations/get_translation_campaign.md
@@ -36,7 +36,7 @@ This endpoint has a rate limit of 250,000 requests per hour.
 |`campaign_id`| Required | String | The ID of your campaign. |
 |`message_variation_id`| Required | String | The ID for your message variation. |
 |`locale_id`| Required | String | The ID of the locale. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 Note all translation IDs are considered universal unique identifiers (UUIDs), which can be found in **Multi-Language Support** settings or in the request response.
 
@@ -105,6 +105,6 @@ The following table lists possible returned errors and their associated troubles
 | `MULTI_LANGUAGE_NOT_ENABLED`            | Multi-language settings aren't turned on for your workspace.                       |
 | `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Only email campaigns or Canvas messages with emails can be translated.             |
 | `UNSUPPORTED_CHANNEL`                   | Only messages in email campaigns or Canvas messages with emails can be translated. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/translations/get_translation_canvas.md b/_docs/_api/endpoints/translations/get_translation_canvas.md
index 858a1832c71..6d734c59e66 100644
--- a/_docs/_api/endpoints/translations/get_translation_canvas.md
+++ b/_docs/_api/endpoints/translations/get_translation_canvas.md
@@ -36,7 +36,7 @@ This endpoint has a rate limit of 250,000 requests per hour.
 |`step_id`| Required | String | The ID of your Canvas step. |
 |`message_variation_id`| Required | String | The ID for your message variation. |
 |`locale_id`| Required | String | The ID of the locale. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 Note all translation IDs are considered universal unique identifiers (UUIDs), which can be found in **Multi-Language Support** settings or in the request response.
 
@@ -105,6 +105,6 @@ The following table lists possible returned errors and their associated troubles
 | `MULTI_LANGUAGE_NOT_ENABLED`            | Multi-language settings aren't turned on for your workspace.                       |
 | `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Only email campaigns or Canvas messages with emails can be translated.             |
 | `UNSUPPORTED_CHANNEL`                   | Only messages in email campaigns or Canvas messages with emails can be translated. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/translations/put_update_translation_campaign.md b/_docs/_api/endpoints/translations/put_update_translation_campaign.md
index 201ecec657b..e4f0d6d0742 100644
--- a/_docs/_api/endpoints/translations/put_update_translation_campaign.md
+++ b/_docs/_api/endpoints/translations/put_update_translation_campaign.md
@@ -37,10 +37,10 @@ There are no path parameters for this endpoint.
 
 | Parameter | Required | Data Type | Description |
 | --------- | ---------| --------- | ----------- |
-| `campaign_id` | Required | String | The ID of your campaign. | 
+| `campaign_id` | Required | String | The ID of your campaign. |
 | `message_variation_id` | Required | String | The ID of your message. |
 |`locale_id`| Required | String | The ID of the locale. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 Note all translation IDs are considered universal unique identifiers (UUIDs), which can be found in **Multi-Language Support** settings or in the GET request response.
 
@@ -101,6 +101,6 @@ The following table lists possible returned errors and their associated troubles
 | `MULTI_LANGUAGE_NOT_ENABLED`            | Multi-language settings aren't turned on for your workspace.                       |
 | `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Only email campaigns or Canvas messages with emails can be translated.             |
 | `UNSUPPORTED_CHANNEL`                   | Only messages in email campaigns or Canvas messages with emails can be translated. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/translations/put_update_translation_canvas.md b/_docs/_api/endpoints/translations/put_update_translation_canvas.md
index 8fe52b52159..2b9f9ccdf29 100644
--- a/_docs/_api/endpoints/translations/put_update_translation_canvas.md
+++ b/_docs/_api/endpoints/translations/put_update_translation_canvas.md
@@ -40,7 +40,7 @@ There are no path parameters for this endpoint.
 |`step_id`| Required | String | The ID of your Canvas step. |
 |`message_variation_id`| Required | String | The ID of your message. |
 |`locale_id`| Required | String | The ID of the locale. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 Note all translation IDs are considered universal unique identifiers (UUIDs), which can be found in **Multi-Language Support** settings or in the GET request response.
 
@@ -100,7 +100,7 @@ The following table lists possible returned errors and their associated troubles
 |`MULTI_LANGUAGE_NOT_ENABLED`|Multi-language settings aren't turned on for your workspace.|
 |`MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE`|Only email campaigns or Canvas messages with emails can be translated.|
 |`UNSUPPORTED_CHANNEL`| Only messages in email campaigns or Canvas messages with emails can be translated.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
           INVALID_CAMPAIGN_ID = "Invalid campaign or step ID"
@@ -114,4 +114,4 @@ The following table lists possible returned errors and their associated troubles
           MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE = "This message does not have multi-language setup"
           UNSUPPORTED_CHANNEL = "This message type does not support multi-language"
 
-{% endapi %}
\ No newline at end of file
+{% endapi %}
diff --git a/_docs/_api/endpoints/user_data/external_id_migration/post_external_ids_remove.md b/_docs/_api/endpoints/user_data/external_id_migration/post_external_ids_remove.md
index bc40e65a991..e05be7e1f75 100644
--- a/_docs/_api/endpoints/user_data/external_id_migration/post_external_ids_remove.md
+++ b/_docs/_api/endpoints/user_data/external_id_migration/post_external_ids_remove.md
@@ -50,7 +50,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | --------- | ---------| --------- | ----------- |
 | `external_ids` | Required | Array of strings | External identifiers for the users to remove. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Request example
 ```
diff --git a/_docs/_api/endpoints/user_data/external_id_migration/post_external_ids_rename.md b/_docs/_api/endpoints/user_data/external_id_migration/post_external_ids_rename.md
index 926f1e68efa..3d7f697945b 100644
--- a/_docs/_api/endpoints/user_data/external_id_migration/post_external_ids_rename.md
+++ b/_docs/_api/endpoints/user_data/external_id_migration/post_external_ids_rename.md
@@ -54,7 +54,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | --------- | ---------| --------- | ----------- |
 | `external_id_renames` | Required | Array of external identifier rename objects | View request example and the following limitations for the structure of the external identifier rename object. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 - The `current_external_id` must be the user's primary ID, and cannot be a deprecated ID
 - The `new_external_id` must not already be in use as either a primary ID or a deprecated ID
diff --git a/_docs/_api/endpoints/user_data/post_user_alias.md b/_docs/_api/endpoints/user_data/post_user_alias.md
index 0049f2c7601..c32919ba565 100644
--- a/_docs/_api/endpoints/user_data/post_user_alias.md
+++ b/_docs/_api/endpoints/user_data/post_user_alias.md
@@ -50,7 +50,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 | Parameter | Required | Data Type | Description |
 | --------- | ---------| --------- | ----------- |
 | `user_aliases` | Required | Array of new user alias objects | See [user alias object]({{site.baseurl}}/api/objects_filters/user_alias_object/).<br><br> For more information on `alias_name` and `alias_label`, check out our [User Aliases]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases) documentation.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ### Endpoint request body with new user alias object specification
 
diff --git a/_docs/_api/endpoints/user_data/post_user_delete.md b/_docs/_api/endpoints/user_data/post_user_delete.md
index e4b77107da3..098f65cff60 100644
--- a/_docs/_api/endpoints/user_data/post_user_delete.md
+++ b/_docs/_api/endpoints/user_data/post_user_delete.md
@@ -53,7 +53,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 | `external_ids` | Optional | Array of strings           | External identifiers for the users to delete.                                                    |
 | `user_aliases` | Optional | Array of user alias object | [User aliases]({{site.baseurl}}/api/objects_filters/user_alias_object/) for the users to delete. |
 | `braze_ids`    | Optional | Array of strings           | Braze user identifiers for the users to delete.                                                  |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ### Deleting users by email
 If an `email` is specified as an identifier, an additional `prioritization` value is required in the identifier. The `prioritization` is an ordered array and should specify which user to delete if multiple users are found. This means deleting users will not occur if more than one user matches a prioritization.
diff --git a/_docs/_api/endpoints/user_data/post_user_identify.md b/_docs/_api/endpoints/user_data/post_user_identify.md
index 0ece05d4ff9..e60e7b44937 100644
--- a/_docs/_api/endpoints/user_data/post_user_identify.md
+++ b/_docs/_api/endpoints/user_data/post_user_identify.md
@@ -62,7 +62,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 | --------------------- | -------- | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `aliases_to_identify` | Required | Array of aliases to identify object | See [alias to identify object]({{site.baseurl}}/api/objects_filters/aliases_to_identify/) and [user alias object]({{site.baseurl}}/api/objects_filters/user_alias_object/). |
 | `merge_behavior`      | Optional | String                              | One of `none` or `merge` is expected.                                                                                                                                       |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 #### Merge_behavior field {#merge}
 
diff --git a/_docs/_api/endpoints/user_data/post_user_track.md b/_docs/_api/endpoints/user_data/post_user_track.md
index 63c1524a82b..28bd3714527 100644
--- a/_docs/_api/endpoints/user_data/post_user_track.md
+++ b/_docs/_api/endpoints/user_data/post_user_track.md
@@ -17,7 +17,7 @@ description: "This article outlines details about the Track user Braze endpoint.
 > Use this endpoint to record custom events and purchases and update user profile attributes.
 
 {% alert note %}
-Braze processes the data passed via API at face value, and customers should only pass deltas (changing data) to minimize unnecessary data point consumption. To read more, refer to [Data points]({{site.baseurl}}/user_guide/data_and_analytics/data_points/). 
+Braze processes the data passed through API at face value, and customers should only pass deltas (changing data) to minimize unnecessary data point consumption. To read more, refer to [Data points]({{site.baseurl}}/user_guide/data_and_analytics/data_points/). 
 {% endalert %}
 
 {% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#4cf57ea9-9b37-4e99-a02e-4373c9a4ee59 {% endapiref %}
@@ -58,7 +58,7 @@ For each request component listed in the following table, one of `external_id`,
 | `attributes` | Optional | Array of attributes objects | See [user attributes object]({{site.baseurl}}/api/objects_filters/user_attributes_object/) |
 | `events` | Optional | Array of event objects | See [events object]({{site.baseurl}}/api/objects_filters/event_object/) |
 | `purchases` | Optional | Array of purchase objects | See [purchases object]({{site.baseurl}}/api/objects_filters/purchase_object/) |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example requests
 
diff --git a/_docs/_api/endpoints/user_data/post_users_alias_update.md b/_docs/_api/endpoints/user_data/post_users_alias_update.md
index 8f2863d0213..6a9afbc411d 100644
--- a/_docs/_api/endpoints/user_data/post_users_alias_update.md
+++ b/_docs/_api/endpoints/user_data/post_users_alias_update.md
@@ -51,7 +51,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 | Parameter | Required | Data Type | Description |
 | --------- | --------- | --------- | ----------- |
 | `alias_updates` | Required | Array of update user alias objects | See [user alias object]({{site.baseurl}}/api/objects_filters/user_alias_object/).<br><br> For more information on `old_alias_name`, `new_alias_name`, and `alias_label`, refer to [User aliases]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ### Endpoint request body with update user alias object specification
 
diff --git a/_docs/_api/endpoints/user_data/post_users_merge.md b/_docs/_api/endpoints/user_data/post_users_merge.md
index aeb6a893998..6ae40d6a351 100644
--- a/_docs/_api/endpoints/user_data/post_users_merge.md
+++ b/_docs/_api/endpoints/user_data/post_users_merge.md
@@ -46,7 +46,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `merge_updates` | Required | Array | An object array. Each object should contain an `identifier_to_merge` object and an `identifier_to_keep` object, which should each reference a user either by `external_id`,  `user_alias`, `phone`, or `email`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ### Merge behavior
 
@@ -265,6 +265,6 @@ The following table lists possible error messages that may occur.
 | `a single request may not contain more than 50 merge updates` | You can only specify up to 50 merge updates in a single request. |
 | `identifiers must be objects with an 'external_id' property that is a string, 'user_alias' property that is an object, or 'email' property that is a string` | Check the identifiers in your request. |
 | `'merge_updates' must only have 'identifier_to_merge' and 'identifier_to_keep'` | Check that `merge_updates` only contains the two objects `identifier_to_merge` and `identifier_to_keep`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
diff --git a/_docs/_api/errors.md b/_docs/_api/errors.md
index eb94bdafcc9..8260f6aa28f 100644
--- a/_docs/_api/errors.md
+++ b/_docs/_api/errors.md
@@ -94,6 +94,6 @@ All of the following error codes indicate that no messages will be sent.
 | `403 Access Denied` | The REST API key you are using does not have sufficient permissions, check the API key permissions under the **Settings** page.|
 | `404 Not Found` | Invalid URL. |
 | `429 Rate Limited` | Over rate limit. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endraw %}
diff --git a/_docs/_api/objects_filters/connected_audience.md b/_docs/_api/objects_filters/connected_audience.md
index d1cabc0e068..e505d3e729b 100644
--- a/_docs/_api/objects_filters/connected_audience.md
+++ b/_docs/_api/objects_filters/connected_audience.md
@@ -62,7 +62,7 @@ The custom attribute's data type determines the comparisons that are valid for a
 | Numeric | `equals`, `not_equal`, `greater_than`, `greater_than_or_equal_to`, `less_than`, `less_than_or_equal_to`, `exists`, `does_not_exist` |
 | Boolean | `equals`, `does_not_equal`, `exists`, `does_not_exist` |
 | Time | `less_than_x_days_ago`, `greater_than_x_days_ago`, `less_than_x_days_in_the_future`, `greater_than_x_days_in_the_future`, `after`, `before`, `exists`, `does_not_exist` | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Attribute comparison caveats
 
@@ -70,7 +70,7 @@ The custom attribute's data type determines the comparisons that are valid for a
 | --- | --- |
 | `value` | The `value` is not required when using the `exists` or `does_not_exist` comparisons. `value` must be an ISO 8601 datetime string when using the `before` and `after` comparisons. |
 |`matches_regex` | When using the `matches_regex` comparison, the value passed must be a string. To read more about using regular expressions with Braze, refer to [Regular expressions]({{site.baseurl}}/user_guide/engagement_tools/segments/regex/#regex-with-braze) and [Custom attribute data types]({{site.baseurl}}/developer_guide/platform_wide/analytics_overview/#custom-attribute-data-types). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Custom attribute example
 
diff --git a/_docs/_api/objects_filters/event_object.md b/_docs/_api/objects_filters/event_object.md
index 23ffcf7c3a8..92abb695705 100644
--- a/_docs/_api/objects_filters/event_object.md
+++ b/_docs/_api/objects_filters/event_object.md
@@ -69,7 +69,7 @@ Property values can be any of the following data types:
 | Strings | 255 characters or fewer. |
 | Arrays | Arrays cannot include datetimes. |
 | Objects | Objects will be ingested as strings. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Event property objects that contain array or object values can have an event property payload of up to 50&nbsp;KB.
 
diff --git a/_docs/_api/objects_filters/messaging/android_object.md b/_docs/_api/objects_filters/messaging/android_object.md
index 2f86749543f..adf7e9885a5 100644
--- a/_docs/_api/objects_filters/messaging/android_object.md
+++ b/_docs/_api/objects_filters/messaging/android_object.md
@@ -41,7 +41,7 @@ You must include an Android push object in `messages` if you want users you have
 }
 ```
 
-You can send "Big Picture" notifications by specifying the key `appboy_image_url` in the `extra` object. The value for `appboy_image_url` should be a URL that links to where your image is hosted. Images need to be cropped to a 2:1 aspect ratio and should be at least 600 x 300 px. Images used for notifications will only display on devices running Jelly Bean (Android 4.1) or higher.
+You can send "Big Picture" notifications by specifying the key `appboy_image_url` in the `extra` object. The value for `appboy_image_url` should be a URL that links to where your image is hosted. Images need to be cropped to a 2:1 aspect ratio and should be at least 600 x 300 px.
 
 ### Additional parameter details
 
@@ -53,7 +53,7 @@ You can send "Big Picture" notifications by specifying the key `appboy_image_url
 | `push_icon_image_url` | The value for the large icon parameter should be a URL that links to where your image is hosted. <br> <br> Images need to be cropped to a 1:1 aspect ratio and should be at least 40x40. |
 | `notification_channel` | If this is not specified, Braze will attempt to send the notification payload with the [dashboard fallback][45] channel ID. For more, see [Notification channels][44] and refer to the steps for [defining notification channels][43] during integration. |
 | `send_to_sync` | For more information on `send_to_sync` messages, see [silent Android notifications][28]. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Android push action button object
 
diff --git a/_docs/_api/objects_filters/messaging/apple_object.md b/_docs/_api/objects_filters/messaging/apple_object.md
index b8944cc96f1..6311b1cb68a 100644
--- a/_docs/_api/objects_filters/messaging/apple_object.md
+++ b/_docs/_api/objects_filters/messaging/apple_object.md
@@ -77,7 +77,7 @@ You must include the `category` field in the Apple push object to use iOS push a
 | `ab_cat_confirm_cancel` | Confirm     | `ab_pb_confirm`            | OPEN_APP, URI, or DEEP_LINK |
 | `ab_cat_confirm_cancel` | Cancel      | `ab_pb_cancel`             | CLOSE                   |
 | `ab_cat_more`           | More        | `ab_pb_more`               | OPEN_APP, URI, or DEEP_LINK |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ```json
 {
diff --git a/_docs/_api/objects_filters/purchase_object.md b/_docs/_api/objects_filters/purchase_object.md
index 3281b0c49f4..ddd0b09c7aa 100644
--- a/_docs/_api/objects_filters/purchase_object.md
+++ b/_docs/_api/objects_filters/purchase_object.md
@@ -102,7 +102,7 @@ Property values can be any of the following data types:
 | Strings | 255 characters or fewer. |
 | Arrays | Arrays cannot include datetimes. |
 | Objects | Objects will be ingested as strings. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Event property objects that contain array or object values can have an event property payload of up to 50&nbsp;KB.
 
diff --git a/_docs/_api/objects_filters/recipient_object.md b/_docs/_api/objects_filters/recipient_object.md
index 83ba5ee50fc..6d698338ec6 100644
--- a/_docs/_api/objects_filters/recipient_object.md
+++ b/_docs/_api/objects_filters/recipient_object.md
@@ -11,7 +11,11 @@ description: "This reference article explains the different components of the Br
 
 > The recipients object allows you to request or write information in our endpoints.
 
-Either `external_user_id` or `user_alias` is required in this object. **Requests must specify only one.**
+Either `external_user_id`, `user_alias`, or `email` is required in this object. **Requests must specify only one.**
+
+{% alert important %}
+Specifying a recipient by email address is currently in early access. Contact your customer success manager if you're interested in participating in this early access.
+{% endalert %}
 
 The recipients object allows you to combine the [user alias object]({{site.baseurl}}/api/objects_filters/user_alias_object/), the [trigger properties object]({{site.baseurl}}/api/objects_filters/trigger_properties_object/), and the [Canvas entry properties object]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/).
 
@@ -21,6 +25,8 @@ The recipients object allows you to combine the [user alias object]({{site.baseu
 [{
   "user_alias": (optional, User Alias Object) User alias of user to receive message,
   "external_user_id": (optional, string) see External user ID,
+  "email": (optional, string) email address of user to receive message,
+  "prioritization": (optional, array) see Prioritization; required when using email,
   "trigger_properties": (optional, object) personalization key-value pairs for this user when sending a campaign or message; see Trigger Properties,
   "canvas_entry_properties": (optional, object) personalization key-value pairs for this user when triggering a Canvas; see Canvas Entry Properties
 }]
@@ -28,6 +34,7 @@ The recipients object allows you to combine the [user alias object]({{site.baseu
 
 - [User aliases]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases)
 - [External user ID]({{site.baseurl}}/api/objects_filters/user_attributes_object/#braze-user-profile-fields)
+- [Prioritization]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/#identifying-users-by-email)
 
 ## Recipient object deduping
 
diff --git a/_docs/_api/objects_filters/user_attributes_object.md b/_docs/_api/objects_filters/user_attributes_object.md
index 59175e5e8ac..2cf6c70c840 100644
--- a/_docs/_api/objects_filters/user_attributes_object.md
+++ b/_docs/_api/objects_filters/user_attributes_object.md
@@ -83,15 +83,30 @@ The following data types can be stored as a custom attribute:
 
 | Data Type | Notes |
 | --- | --- |
-| Arrays | Custom attribute arrays are one-dimensional sets; multi-dimensional arrays are not supported. Adding an element to a custom attribute array appends the element to the end of the array, unless it's already present, in which case it gets moved from its current position to the end of the array.<br><br>For example, if an array `['hotdog','hotdog','hotdog','pizza']` were imported, it will show in the array attribute as `['hotdog', 'pizza']` because only unique values are supported.<br><br>In addition to setting the values of an array by saying something like `"my_array_custom_attribute":[ "Value1", "Value2" ]` you may add to existing arrays by doing something like `"my_array_custom_attribute" : { "add" : ["Value3"] },` or remove values from an array by doing something like `"my_array_custom_attribute" : { "remove" : [ "Value1" ]}`<br><br>The maximum number of elements in custom attribute arrays defaults to 25, but can be increased up to 100 for an individual array. For more information, see [Arrays][6]. |
+| Arrays | Custom attribute arrays are supported. Adding an element to a custom attribute array appends the element to the end of the array, unless it's already present, in which case it gets moved from its current position to the end of the array.<br><br>For example, if an array `['hotdog','hotdog','hotdog','pizza']` were imported, it will show in the array attribute as `['hotdog', 'pizza']` because only unique values are supported.<br><br>In addition to setting the values of an array by saying something like `"my_array_custom_attribute":[ "Value1", "Value2" ]` you may add to existing arrays by doing something like `"my_array_custom_attribute" : { "add" : ["Value3"] },` or remove values from an array by doing something like `"my_array_custom_attribute" : { "remove" : [ "Value1" ]}`<br><br>The maximum number of elements in custom attribute arrays defaults to 25, but can be increased up to 100 for an individual array. For more information, see [Arrays][6]. |
+| Array of objects | Array of objects allows you to define a list of objects where each object contains a set of attributes. This can be useful if you need to store multiple sets of related data for a user, such as hotel stays, purchase history, or preferences. <br><br> For example, you can define a custom attribute on a user profile named `hotel_stays`. This custom attribute can be defined as an array where each object represents a separate stay, with attributes such as `hotel_name`, `check_in_date`, `nights_stayed`. For more details, see [this example](#array-of-objects-example). |
 | Booleans | `true` or `false` |
 | Dates | Must be stored in the [ISO 8601][19] format or in any of the following formats: <br>- `yyyy-MM-ddTHH:mm:ss:SSSZ` <br>- `yyyy-MM-ddTHH:mm:ss` <br>- `yyyy-MM-dd HH:mm:ss` <br>- `yyyy-MM-dd` <br>- `MM/dd/yyyy` <br>- `ddd MM dd HH:mm:ss.TZD YYYY` <br><br>Note that "T" is a time designator, not a placeholder, and should not be changed or removed. <br><br>Time attributes without a time zone will default to Midnight UTC (and will be formatted on the dashboard as the equivalent of Midnight UTC in the company's time zone). <br><br> Events with timestamps in the future will default to the current time. <br><br> For regular custom attributes, if the year is less than 0 or greater than 3000, Braze stores these values as strings on the user. |
 | Floats | Float custom attributes are positive or negative numbers with a decimal point. For example, you can use floats to store account balances or user ratings for products or services. |
 | Integers | Integer custom attributes may be incremented by positive or negative integers by assigning them an object with the field "inc" and the value by which you want to increment them. <br><br>Example: `"my_custom_attribute_2" : {"inc" : int_value},`|
+| Nested custom attributes | Nested custom attributes define a set of attributes as a property of another attribute. When you define a custom attribute object, you define a set of additional attributes for that object. For more information, refer to [Nested custom attributes]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support). |
 | Strings | String custom attributes are sequences of characters used to store text data. For example, you can use strings to store first and last names, email addresses, or preferences. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-For information regarding when you should use a custom event versus a custom attribute, see our respective documentation on [custom events]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/) and [custom attributes]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/).
+{% alert tip %}
+For information on when you should use a custom event versus a custom attribute, see our respective documentation on [custom events]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/) and [custom attributes]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/).
+{% endalert %}
+
+##### Array of objects example 
+
+This array of objects allows you to create segments based on specific criteria within the stays, and personalize your messages using the data from each stay with Liquid templates.
+
+```json
+"hotel_stays": [
+  { "hotel_name": "Ocean View Resort", "check_in_date": "2023-06-15", "nights_stayed": 5 },
+  { "hotel_name": "Mountain Lodge", "check_in_date": "2023-09-10", "nights_stayed": 3 }
+  ]
+```
 
 #### Braze user profile fields {#braze-user-profile-fields}
 
@@ -127,7 +142,7 @@ The following user profile fields are case sensitive, so be sure to reference th
 | subscription_groups| Array of objects with `subscription_group_id` and `subscription_state` string, for example, `[{"subscription_group_id" : "subscription_group_identifier", "subscription_state" : "subscribed"}]`. Available values for `subscription_state` are "subscribed" and "unsubscribed".|
 | time_zone | (string) Of time zone name from [IANA Time Zone Database][26] (for example, "America/New_York" or "Eastern Time (US & Canada)"). Only valid time zone values will be set. |
 | twitter | Hash containing any of `id` (integer), `screen_name` (string, X (formerly Twitter) handle), `followers_count` (integer), `friends_count` (integer), `statuses_count` (integer). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Language values that are explicitly set through this API will take precedence over the locale information Braze automatically receives from the device.
 
diff --git a/_docs/_contributing/content_management.md b/_docs/_contributing/content_management.md
index 39883f6622e..d41c75d0c25 100644
--- a/_docs/_contributing/content_management.md
+++ b/_docs/_contributing/content_management.md
@@ -29,7 +29,7 @@ As a contributor, you'll primarily work within the following directories.
 | [`_docs`](https://github.com/braze-inc/braze-docs/tree/develop/_docs)         | Contains all the written content for Braze Docs as text files written in Markdown. Text files are organized into directories and subdirectories mirroring the docs site, such as `_api` for the [API section]({{site.baseurl}}/api/home) and `user_guide` for the [User Guide section]({{site.baseurl}}/user_guide/introduction). |
 | [`_includes`](https://github.com/braze-inc/braze-docs/tree/develop/_includes) | Contains text files (called "includes") that can be reused in any file within the `_docs` directory. Typically, includes are short, modular pieces of content that don't use standard formatting. The files stored in this location are important for [content reuse](#content-reuse).                                            |
 | [`assets`](https://github.com/braze-inc/braze-docs/tree/develop/assets)       | Contains all the images for Braze Docs. Any text file in the `_docs` or `_includes` directory can link to this directory to display an image on its page.                                                                                                                                                                         |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 For a full walkthrough, see [Generating a preview]({{site.baseurl}}/contributing/generating_a_preview/).
@@ -54,7 +54,7 @@ Replace the following.
 | `METADATA_KEY`   | The key representing a supported metadata type. For more information, see [Metadata]({{site.baseurl}}/contributing/yaml_front_matter/metadata/). |
 | `METADATA_VALUE` | The value assigned to the metadata type's key. For more information, see [Metadata]({{site.baseurl}}/contributing/yaml_front_matter/metadata/).  |
 | `CONTENT`        | The page's content written in Markdown syntax.                                                                                           |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% tabs local %}
 {% tab example input %}
@@ -100,7 +100,7 @@ Replace the following.
 |-------------|-------------------------------------------------------------------------------------------------------------------------|
 | `ALT_TEXT`  | The alt text for the image. This is required to make Braze Docs equally accessible for those using screen readers. |
 | `IMAGE`     | The relative path to your image starting from the `img` directory.                                                      |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your in-line image should be similar to the following:
 
@@ -296,7 +296,7 @@ Replace the following:
 |-------------|----------------------------------------------------|
 | `LINK_TEXT` | The page title or related action.                  |
 | `SHORT_URL` | The page URL with `https://www.braze.com` removed. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your cross-reference link should be similar to the following:
 
@@ -324,7 +324,7 @@ Replace the following:
 |-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `RELATIVE_PATH` | (Optional) The relative path to the file from the `_includes` directory. This is only needed if you're including a file from a directory inside the `_includes` directory, such as `_includes/braze/upgrade_notice.md`. |
 | `FILE`          | The name of the file including the file extension.                                                                                                                                                                      |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% tabs local %}
 {% tab example input %}
diff --git a/_docs/_contributing/content_management/cross_referencing.md b/_docs/_contributing/content_management/cross_referencing.md
index 1acf598bd61..143d8d44051 100644
--- a/_docs/_contributing/content_management/cross_referencing.md
+++ b/_docs/_contributing/content_management/cross_referencing.md
@@ -34,7 +34,7 @@ Replace the following:
 |-------------|----------------------------------------------------|
 | `LINK_TEXT` | The page title or related action.                  |
 | `SHORT_URL` | The page URL with `https://www.braze.com` removed. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your in-line link should be similar to the following:
 
@@ -60,7 +60,7 @@ Replace the following:
 |-------------|----------------------------------------------------|
 | `LINK_TEXT` | The page title or related action.                  |
 | `SHORT_URL` | The page URL with `https://www.braze.com` removed. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your in-line link should be similar to the following:
 
diff --git a/_docs/_contributing/content_management/images.md b/_docs/_contributing/content_management/images.md
index cc2dc747d6e..bd758776681 100644
--- a/_docs/_contributing/content_management/images.md
+++ b/_docs/_contributing/content_management/images.md
@@ -32,7 +32,7 @@ Replace the following:
 |-------------|-------------------------------------------------------------------------------------------|
 | `DIRECTORY` | The name of the relevant directory. If there's no relevant directory, you may create one. |
 | `FILE`      | The name of the file including the file extension.                                        |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your image file should be similar to the following:
 
@@ -64,7 +64,7 @@ Replace the following:
 |-------------|-------------------------------------------------------------------------------------------------------------------------|
 | `ALT_TEXT`  | The alt text for the image. This is required to make Braze Docs equally accessible for those using screen readers. |
 | `IMAGE`     | The relative path to your image starting from the `img` directory.                                                      |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your in-line image should be similar to the following:
 
@@ -150,7 +150,7 @@ Replace the following:
 |-------------|-------------------------------------------------------------------------------------------|
 | `DIRECTORY` | The name of the relevant directory. If there's no relevant directory, you may create one. |
 | `FILE`      | The name of the file including the file extension.                                        |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your image file should be similar to the following:
 
diff --git a/_docs/_contributing/content_management/jekyll_collections.md b/_docs/_contributing/content_management/jekyll_collections.md
index 90cf89b3db7..2c92912b559 100644
--- a/_docs/_contributing/content_management/jekyll_collections.md
+++ b/_docs/_contributing/content_management/jekyll_collections.md
@@ -1,13 +1,13 @@
 ---
 nav_title: Jekyll Collections
-article_title: Jekyll collections
-description: "Learn how to create a Jekyll collection, so you can add a new primary section on Braze Docs."
+article_title: Jekyll Collections
+description: "Learn how to create a Jekyll collection so you can add a new primary section on Braze Docs."
 page_order: 6
 ---
 
 # Jekyll collections
 
-> Learn how to create a Jekyll collection, so you can add a new primary section on Braze Docs. For more information, see [Jekyll Collections](https://jekyllrb.com/docs/collections/).
+> Learn how to create a Jekyll collection to add a new primary section on Braze Docs. For more information, see [Jekyll Collections](https://jekyllrb.com/docs/collections/).
 
 {% alert important %}
 It's unlikely you'll need to create a new Jekyll collection for your content. If you're unsure where you should store your content, [create a GitHub issue](https://github.com/braze-inc/braze-docs/issues/new?assignees=&labels=issue&projects=&template=report_an_issue.md&title=).
@@ -36,7 +36,7 @@ Replace the following:
 | `COLLECTION_KEY`  | A single, unique word that represents your collection's name. Use lowercase letters only. |
 | `COLLECTION_TITLE`| The name of your collection in title case.        |
 | `COLLECTION_URL`  | The default URL for your collections landing page.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Your new collection should be similar to the following:
 
diff --git a/_docs/_contributing/content_management/redirecting_urls.md b/_docs/_contributing/content_management/redirecting_urls.md
index 0001e1333c4..988808a8ff5 100644
--- a/_docs/_contributing/content_management/redirecting_urls.md
+++ b/_docs/_contributing/content_management/redirecting_urls.md
@@ -66,7 +66,7 @@ Replace the following:
 |-----------------|------------------------------------------------------------------------------------------------|
 | `REDIRECT_FROM` | The URL you want to redirect _from_ with `https://www.braze.com/` removed from the URL string. |
 | `REDIRECT_TO`   | The URL you want to redirect _to_ with `https://www.braze.com/` removed from the URL string.   |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% multi_lang_include contributing/alerts/warning_urls_must_be_lowercase.md %}
 
@@ -93,7 +93,7 @@ Replace the following:
 |-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
 | `OLD_HEADING`     | The old heading in [Markdown syntax](https://www.markdownguide.org/basic-syntax/#an-example-putting-the-parts-together) with the `#` removed. |
 | `NEW_HEADING_URL` | The new heading URL you want to redirect _to_ with `https://www.braze.com/` removed from the URL string.                                      |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% multi_lang_include contributing/alerts/warning_urls_must_be_lowercase.md %}
 
diff --git a/_docs/_contributing/content_management/reusing_content.md b/_docs/_contributing/content_management/reusing_content.md
index bca6b8f5d8b..2bce7758b5f 100644
--- a/_docs/_contributing/content_management/reusing_content.md
+++ b/_docs/_contributing/content_management/reusing_content.md
@@ -44,7 +44,7 @@ As a contributor, you'll primarily work within the following directories.
 | [`_docs`](https://github.com/braze-inc/braze-docs/tree/develop/_docs)         | Contains all the written content for Braze Docs as text files written in Markdown. Text files are organized into directories and subdirectories mirroring the docs site, such as `_api` for the [API section]({{site.baseurl}}/api/home) and `user_guide` for the [User Guide section]({{site.baseurl}}/user_guide/introduction). |
 | [`_includes`](https://github.com/braze-inc/braze-docs/tree/develop/_includes) | Contains text files (called "includes") that can be reused in any file within the `_docs` directory. Typically, includes are short, modular pieces of content that don't use standard formatting. The files stored in this location are important for [content reuse](#content-reuse).                                            |
 | [`assets`](https://github.com/braze-inc/braze-docs/tree/develop/assets)       | Contains all the images for Braze Docs. Any text file in the `_docs` or `_includes` directory can link to this directory to display an image on its page.                                                                                                                                                                         |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 ```
 {% endraw %}
 
diff --git a/_docs/_contributing/content_management/sections.md b/_docs/_contributing/content_management/sections.md
index b63c6322c83..3ca47d612a8 100644
--- a/_docs/_contributing/content_management/sections.md
+++ b/_docs/_contributing/content_management/sections.md
@@ -35,7 +35,7 @@ Replace the following:
 | `SUBSECTION`      | If applicable, the name of the subsection your new content belongs to. For more information, see [Subsections]({{site.baseurl}}/contributing/content_management/#subsections).                                                                              |
 | `NEW_DIRECTORY`   | The name of your new section, which should follow the [Braze Docs Style Guide]({{site.baseurl}}/contributing/style_guide/). Use all lowercase characters, remove special characters, and replace spaces with underscores (`_`). This name must match `NEW_FILE`.       |
 | `NEW_FILE`        | The name of your new section, which should follow the [Braze Docs Style Guide]({{site.baseurl}}/contributing/style_guide/). Use all lowercase characters, remove special characters, and replace spaces with underscores (`_`). This name must match `NEW_DIRECTORY`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your directory structure should be similar to the following:
 
@@ -84,7 +84,7 @@ Replace the following:
 | `SHORT_DESCRIPTION`  | A short, 1-2 sentence description of your page. The `SHORT_DESCRIPTION` value in YAML the metadata is used for search engine results, while the `SHORT_DESCRIPTION` value after Heading 1 is used for the description rendered on the page. |
 | `HEADING`            | The title of your Heading 2 section.                                                                                                                                                                                                        |
 | `CONTENT`            | The body paragraph for your Heading 2 section.                                                                                                                                                                                              |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 This template is only to get you started&#8212;add [additional metadata]({{site.baseurl}}/contributing/yaml_front_matter/metadata/) and headings as needed.
diff --git a/_docs/_contributing/content_types.md b/_docs/_contributing/content_types.md
index 24f79f87122..44844e33c90 100644
--- a/_docs/_contributing/content_types.md
+++ b/_docs/_contributing/content_types.md
@@ -192,7 +192,7 @@ Release notes are a monthly compilation of product updates in Braze. Each update
 | AI and ML automation   | Updates on AI and machine learning capabilities within the platform.                  |
 | New Braze partnerships | Introduces new integrations with other platforms and services.          |
 | SDK updates            | Lists new SDKs or updates, including breaking changes and new features. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 You can use this template to create release notes for Braze Docs. For an example, see [January 9, 2024 release]({{site.baseurl}}/help/release_notes/2024/1_9_24/).
 
diff --git a/_docs/_contributing/git_and_github.md b/_docs/_contributing/git_and_github.md
index 5925fd0a134..8e3e2c30b99 100644
--- a/_docs/_contributing/git_and_github.md
+++ b/_docs/_contributing/git_and_github.md
@@ -99,6 +99,16 @@ When you're finished, select the pull request dropdown, then select **Draft pull
 
 ![The Braze Docs GitHub repository showing "Draft pull request".]({% image_buster /assets/img/contributing/github/draft_pull_request.png %}){: style="max-width:65%;"}
 
+## Allowing changes to pull requests
+
+In GitHub, go to the Braze Docs repository page and select **Pull requests**.
+
+![Braze Docs repository page with navigation menu containing Pull requests.]({% image_buster /assets/img/contributing/github/menu_pull_requests.png %})
+
+Open the relevant pull request, then check **Allow edits and access to secrets from maintainers**. This will let the Braze Docs team make style or formatting changes to your content.
+
+![A Pull Request showing the allow edits from maintainers checkbox.]({% image_buster /assets/img/contributing/github/allow_maintainers_to_edit.png %}){: style="max-width:50%;"}
+
 ## Requesting a review
 
 To request a PR review from a member of the Braze Docs team, open the [PR you previously created](#creating-a-pull-request) and select **Ready for review**.
diff --git a/_docs/_contributing/home.md b/_docs/_contributing/home.md
index e10d96f992a..8c4de5ee19f 100644
--- a/_docs/_contributing/home.md
+++ b/_docs/_contributing/home.md
@@ -88,7 +88,7 @@ table td {
     </tr>
 </tbody>
 </table>
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 As of writing, all software is free of cost. If you find that a product is no longer free, [please let us know](https://github.com/braze-inc/braze-docs/issues/new?assignees=&labels=issue&projects=&template=report_an_issue.md&title=).
@@ -157,4 +157,4 @@ If you're new to Git or docs-as-code, start with our tutorial: [Your first contr
 - [Content management]({{site.baseurl}}/contributing/content_management/)
 - [YAML metadata]({{site.baseurl}}/contributing/yaml_front_matter/metadata/)
 - [Generating a preview]({{site.baseurl}}/contributing/generating_a_preview/)
-- [Style guides]({{site.baseurl}}/contributing/style_guide)
+- [Style guides]({{site.baseurl}}/contributing/style_guide)
\ No newline at end of file
diff --git a/_docs/_contributing/styling_examples.md b/_docs/_contributing/styling_examples.md
index 32058034cb0..b92ddfe47e4 100644
--- a/_docs/_contributing/styling_examples.md
+++ b/_docs/_contributing/styling_examples.md
@@ -151,7 +151,7 @@ Lorem ipsum dolor ``sit amet, consectetur adipiscing elit``. Sed nec tortor at l
 | US-07    | `https://dashboard-07.braze.com`                                      | `https://rest.iad-07.braze.com` |
 | US-08    | `https://dashboard-08.braze.com`                                      | `https://rest.iad-08.braze.com` |
 | EU-01    | `https://dashboard.braze.eu` or<br> `https://dashboard-01.braze.eu`   | `https://rest.fra-01.braze.eu`  |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation"}
 {% endtab %}
 {% tab Markdown %}
 ```
@@ -167,22 +167,28 @@ Lorem ipsum dolor ``sit amet, consectetur adipiscing elit``. Sed nec tortor at l
 | US-08    | `https://dashboard-08.braze.com`                                      | `https://rest.iad-08.braze.com` |
 | EU-01    | `https://dashboard.braze.eu` or<br> `https://dashboard-01.braze.eu`   | `https://rest.fra-01.braze.eu`  |
 | EU-02    | `https://dashboard-02.braze.eu`                                       | `https://rest.fra-02.braze.eu`  |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation"}
 ```
 {% endtab %}
 {% endtabs %}
 
 #### Resetting Table word-break by column
-For tables columns which word-break should be reset to the default style, use Markdown options to add a class to the table using `.reset-td-br-1`, `.reset-td-br-2`, `.reset-td-br-3` , `.reset-td-br-4`, with the `#` corresponding to the column up to 4.
 
-#### Usage
+To reset the table word-break by column, use the following syntax:
+
+```markdown
+{: .reset-td-br-NUM .reset-td-br-NUM .reset-td-br-NUM .reset-td-br-NUM role="presentation"}
 ```
+
+Replace `NUM` with the corresponding column number, up to a maximum of 4 columns. If you have less than 4 columns, remove extra `.reset-td-br-NUM` placeholders. Your table should be similar to the following:
+
+```markdown
 | Event Name                                                       | Feed Type              | Description                                                  | Custom Attributes                                                             |
 | ---------------------------------------------------------------- | ---------------------- | ------------------------------------------------------------ | ----------------------------------------------------------------------------- |
 | UNBROKENWORDTHATISVERYLONGUNBROKENWORDTHATISVERYLONG             | Unbound Feed           | An email was successfully delivered to a User's mail server. | `campaign_id`, `canvas_step_id`, `canvas_id`, `canvas_variation_id`           |
 | `UNBROKENHIGHLIGHTTHATISVERYLONGUNBROKENHIGHLIGHTTHATISVERYLONG` | Unbound Feed           | User opened an email.                                        | `campaign_id`, `canvas_step_id`, `canvas_id`, `canvas_variation_id`           |
 | In-App Message Impression                                        | Platform-specific Feed | User viewed an In-App Message.                               | `app_id`, `campaign_id`, `canvas_step_id`, `canvas_id`, `canvas_variation_id` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation"}
 
 ```
 {% tabs local %}
@@ -202,7 +208,7 @@ For tables columns which word-break should be reset to the default style, use Ma
 | UNBROKENWORDTHATISVERYLONGUNBROKENWORDTHATISVERYLONG             | Unbound Feed           | An email was successfully delivered to a User's mail server. | `campaign_id`, `canvas_step_id`, `canvas_id`, `canvas_variation_id`           |
 | `UNBROKENHIGHLIGHTTHATISVERYLONGUNBROKENHIGHLIGHTTHATISVERYLONG` | Unbound Feed           | User opened an email.                                        | `campaign_id`, `canvas_step_id`, `canvas_id`, `canvas_variation_id`           |
 | In-App-Message-Impression                                        | Platform-specific Feed | User viewed an In-App Message.                               | `app_id`, `campaign_id`, `canvas_step_id`, `canvas_id`, `canvas_variation_id` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation"}
 {% endtab %}
 {% endtabs %}
 
diff --git a/_docs/_contributing/yaml_front_matter/metadata.md b/_docs/_contributing/yaml_front_matter/metadata.md
index 14799590fe9..6836c08ed80 100644
--- a/_docs/_contributing/yaml_front_matter/metadata.md
+++ b/_docs/_contributing/yaml_front_matter/metadata.md
@@ -26,7 +26,7 @@ Replace the following:
 |------------------|---------------------------------------------------------------------------------------------------------------------------|
 | `METADATA_KEY`   | The key representing a supported metadata type. Replace with a [metadata key](#required-keys) from the following section. |
 | `METADATA_VALUE` | The value assigned to the metadata key. Check a metadata key's supported values in the following section.                 |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your page should be similar to the following:
 
diff --git a/_docs/_contributing/your_first_contribution.md b/_docs/_contributing/your_first_contribution.md
index a75b94826b9..4249866b3c3 100644
--- a/_docs/_contributing/your_first_contribution.md
+++ b/_docs/_contributing/your_first_contribution.md
@@ -187,6 +187,10 @@ These comments will guide you through your PR description. When you're finished,
 
 ![An example pull request showing "Draft pull request".]({% image_buster /assets/img/contributing/github/draft_pull_request.png %}){: style="max-width:65%;"}
 
+Finally, check **Allow edits and access to secrets from maintainers**. This will let the Braze Docs team make style or formatting changes to your content during their review later.
+
+![A Pull Request showing the allow edits from maintainers checkbox.]({% image_buster /assets/img/contributing/github/allow_maintainers_to_edit.png %}){: style="max-width:50%;"}
+
 ## Step 4: Review your work
 
 Create your content by following the [Braze Docs Style Guide]({{sitebase.url}}/contributing/style_guide/) and reviewing your work in a site preview. If you need to make additional changes, see [Make additional changes](#step-6-make-additional-changes-optional). Otherwise, you can [request a review](#step-5-request-a-review) from the Braze Docs team.
diff --git a/_docs/_developer_guide/customization_guides/content_cards/customizing_feed.md b/_docs/_developer_guide/customization_guides/content_cards/customizing_feed.md
index 7ff0d2d1ea3..3653b9033db 100644
--- a/_docs/_developer_guide/customization_guides/content_cards/customizing_feed.md
+++ b/_docs/_developer_guide/customization_guides/content_cards/customizing_feed.md
@@ -103,7 +103,7 @@ function refresh() {
 
 
 {% alert important %}
-The default rate limit for manually refreshing the feed is 3 calls per 10 minutes per device to prevent performance degradation and errors.
+You can make up to five calls in quick succession. After that, one new call will be available every 180 seconds. The system will hold up to five calls for you to use at any time.
 {% endalert %}
 
 ## Customizing displayed card order
diff --git a/_docs/_developer_guide/platform_integration_guides/android/analytics/setting_custom_attributes.md b/_docs/_developer_guide/platform_integration_guides/android/analytics/setting_custom_attributes.md
index 27f3a3ff804..c15e36d92ab 100644
--- a/_docs/_developer_guide/platform_integration_guides/android/analytics/setting_custom_attributes.md
+++ b/_docs/_developer_guide/platform_integration_guides/android/analytics/setting_custom_attributes.md
@@ -266,7 +266,7 @@ To set up a subscription for your users (either email or push), call the functio
 | `OPTED_IN` | Subscribed, and explicitly opted in |
 | `SUBSCRIBED` | Subscribed, but not explicitly opted in |
 | `UNSUBSCRIBED` | Unsubscribed and/or explicitly opted out |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 No explicit opt-in is required by Android to send users push notifications. When a user is registered for push, they are set to `SUBSCRIBED` rather than `OPTED_IN` by default. Refer to [managing user subscriptions]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#managing-user-subscriptions) for more information on implementing subscriptions and explicit opt-ins.
diff --git a/_docs/_developer_guide/platform_integration_guides/android/content_cards/integration.md b/_docs/_developer_guide/platform_integration_guides/android/content_cards/integration.md
index 30f01fb4ce4..e5e00982a47 100644
--- a/_docs/_developer_guide/platform_integration_guides/android/content_cards/integration.md
+++ b/_docs/_developer_guide/platform_integration_guides/android/content_cards/integration.md
@@ -46,7 +46,7 @@ The [base card](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android
 |`getExpiredAt()` | Gets the expiration date of the card.|
 |`getIsRemoved()` | Returns a boolean that reflects whether the end user has dismissed this card.|
 |`getIsDismissible()`  | Returns a boolean that reflects whether the card is pinned.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Image only image card properties {#banner-image-card-for-android}
 
@@ -57,7 +57,7 @@ The [base card](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android
 |`getImageUrl()` | Returns the URL of the card's image.|
 |`getUrl()` | Returns the URL that will be opened after the card is clicked. It can be a HTTP(s) URL or a protocol URL.|
 |`getDomain()` | Returns link text for the property URL.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Captioned image card properties {#captioned-image-card-for-android}
 
@@ -70,7 +70,7 @@ The [base card](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android
 |`getDescription()` | Returns the body text for the card.|
 |`getUrl()` | Returns the URL that will be opened after the card is clicked. It can be a HTTP(s) URL or a protocol URL.|
 |`getDomain()` | Returns the link text for the property URL. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Classic card properties {#text-Announcement-card-for-android}
 
@@ -83,7 +83,7 @@ A classic card without an image included will result in a [text announcement car
 |`getUrl()` | Returns the URL that will be opened after the card is clicked. It can be a HTTP(s) URL or a protocol URL. | 
 |`getDomain()` | Returns the link text for the property URL. |
 |`getImageUrl()` | Returns the URL of the card's image, applies only to the classic Short News Card. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Card methods
 
@@ -94,5 +94,5 @@ All [`Card`](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sd
 |`logImpression()` | Manually log an impression to Braze for a particular card. |
 |`logClick()` | Manually log a click to Braze for a particular card. |
 |`setIsDismissed()` | Manually log a dismissal to Braze for a particular card. If a card is already marked as dismissed, it cannot be marked as dismissed again. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
diff --git a/_docs/_developer_guide/platform_integration_guides/android/in-app_messaging/customization/custom_listeners.md b/_docs/_developer_guide/platform_integration_guides/android/in-app_messaging/customization/custom_listeners.md
index d7b5904beee..07d82b529aa 100644
--- a/_docs/_developer_guide/platform_integration_guides/android/in-app_messaging/customization/custom_listeners.md
+++ b/_docs/_developer_guide/platform_integration_guides/android/in-app_messaging/customization/custom_listeners.md
@@ -97,7 +97,7 @@ The `InAppMessageOperation()` return value can control when the message should b
 | `DISPLAY_LATER` | The message will be returned to the stack and displayed at the next available opportunity |
 | `DISCARD` | The message will be discarded |
 | `null` | The message will be ignored. This method should **NOT** return `null` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 See [`InAppMessageOperation.java`](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.ui.inappmessage/-in-app-message-operation/index.html) for more details.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/android/in-app_messaging/troubleshooting.md b/_docs/_developer_guide/platform_integration_guides/android/in-app_messaging/troubleshooting.md
index bb2fd4da998..7661c39f218 100644
--- a/_docs/_developer_guide/platform_integration_guides/android/in-app_messaging/troubleshooting.md
+++ b/_docs/_developer_guide/platform_integration_guides/android/in-app_messaging/troubleshooting.md
@@ -13,62 +13,4 @@ channel:
 
 # Troubleshooting
 
-> This article provides several Android and FireOS in-app message troubleshooting scenarios.
-
-## Impressions
-
-#### Impression or click analytics aren't being logged
-
-If you have set an in-app message delegate to manually handle message display or click actions, you'll need to manually log clicks and impressions on the in-app message.
-
-#### Impressions are lower than expected
-
-Triggers take time to sync to the device on session start, so there can be a race condition if users log an event or purchase right after they start a session. One potential workaround could be changing the campaign to trigger off of session start, then segmenting off the intended event or purchase. Note that this would deliver the in-app message on the next session start after the event has occurred.
-
-## Expected in-app message did not display
-
-Most in-app message issues can be broken down into two main categories: delivery and display. To troubleshoot why an expected in-app message did not display on your device, you should first confirm that the [in-app message was delivered to the device](#troubleshooting-in-app-message-delivery), then [troubleshoot message display](#troubleshooting-in-app-message-display).
-
-## In-app message delivery {#troubleshooting-in-app-message-delivery}
-
-The SDK requests in-app messages from Braze servers on session start. To check if in-app messages are being delivered to your device, you'll need to make sure that in-app messages are being both requested by the SDK and returned by Braze servers.
-
-### Check if messages are requested and returned
-
-1. Add yourself as a [test user]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#adding-test-users) on the dashboard.
-2. Set up an in-app message campaign targeted at your user.
-3. Ensure that a new session occurs in your application.
-4. Use the [event user logs]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab) to check that your device is requesting in-app messages on session start. Find the SDK Request associated with your test user's session start event.
-  - If your app was meant to request triggered in-app messages, you should see `trigger` in the **Requested Responses** field under **Response Data**.
-  - If your app was meant to request original in-app messages, you should see  `in_app` in the **Requested Responses** field under **Response Data**.
-5. Use the [event user logs]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab) to check if the correct in-app messages are being returned in the response data.<br>![]({% image_buster /assets/img_archive/event_user_log_iams.png %})
-
-#### Troubleshoot messages not being requested
-
-If your in-app messages are not being requested, your app might not be tracking sessions correctly, as in-app messages are refreshed upon session start. Also, be sure that your app is actually starting a session based on your app's session timeout semantics:
-
-![The SDK request found in the event user logs displaying a successful session start event.]({% image_buster /assets/img_archive/event_user_log_session_start.png %})
-
-### Troubleshoot messages not being returned
-
-If your in-app messages are not being returned, you're likely experiencing a campaign targeting issue:
-
-- Your segment does not contain your user.
-  - Check your user's [**Engagement**]({{ site.baseurl }}/user_guide/engagement_tools/segments/using_user_search/#engagement-tab) tab to see if the correct segment appears under **Segments**.
-- Your user has previously received the in-app message and was not re-eligible to receive it again.
-  - Check the [campaign re-eligibility settings]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/) under the **Delivery** step of the **Campaign Composer** and make sure the re-eligibility settings align with your testing setup.
-- Your user hit the frequency cap for the campaign.
-  - Check the campaign [frequency cap settings]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping) and ensure they align with your testing setup.
-- If there was a control group on the campaign, your user may have fallen into the control group.
-  - You can check if this has happened by creating a segment with a received campaign variant filter, where the campaign variant is set to **Control**, and checking if your user fell into that segment.
-  - When creating campaigns for integration testing purposes, make sure to opt out of adding a control group.
-
-## In-app message display {#troubleshooting-in-app-message-display}
-
-If your app is successfully requesting and receiving in-app messages, but they are not being shown, some device-side logic may be preventing display:
-
-- Triggered in-app messages are rate-limited based on the [minimum time interval between triggers]({{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers), which defaults to 30 seconds.
-- If you have set a delegate to customize in-app message handling, check your delegate to ensure it is not affecting the in-app message display.
-- Failed image downloads will prevent in-app messages with images from displaying. Image downloads will always fail if the `BrazeInAppMessageManager` is not registered properly. Check your device logs to ensure that image downloads are not failing.
-- If the device orientation does not match the orientation specified by the in-app message, the in-app message will not display. Make sure that your device is in the correct orientation.
-
+{% multi_lang_include inapp_message_troubleshooting.md sdk="Android" %}
diff --git a/_docs/_developer_guide/platform_integration_guides/android/initial_sdk_setup/accessibility.md b/_docs/_developer_guide/platform_integration_guides/android/initial_sdk_setup/accessibility.md
index 1a5acc612d7..b5552e79cea 100644
--- a/_docs/_developer_guide/platform_integration_guides/android/initial_sdk_setup/accessibility.md
+++ b/_docs/_developer_guide/platform_integration_guides/android/initial_sdk_setup/accessibility.md
@@ -18,14 +18,14 @@ description: "This reference article covers how to implement specific Android SD
 In order to have Android Talkback/"VoiceOver" not read the contents behind an in-app message during display, enable the following SDK configuration:
 
 {% tabs %}
-{% tab braze.xml %}
+{% tab Braze XML %}
 
 ```xml
 <bool name="com_braze_device_in_app_message_accessibility_exclusive_mode_enabled">true</bool>
 ```
 
 {% endtab %}
-{% tab KOTLIN %}
+{% tab Kotlin %}
 
 ```kotlin
 val brazeConfigBuilder = BrazeConfig.Builder()
@@ -34,7 +34,7 @@ Braze.configure(this, brazeConfigBuilder.build())
 ```
 
 {% endtab %}
-{% tab JAVA %}
+{% tab Java %}
 
 ```java
 BrazeConfig.Builder brazeConfigBuilder = new BrazeConfig.Builder()
diff --git a/_docs/_developer_guide/platform_integration_guides/android/initial_sdk_setup/additional_customization_and_configuration.md b/_docs/_developer_guide/platform_integration_guides/android/initial_sdk_setup/additional_customization_and_configuration.md
index 4cdb3772bc1..613f3431f9a 100644
--- a/_docs/_developer_guide/platform_integration_guides/android/initial_sdk_setup/additional_customization_and_configuration.md
+++ b/_docs/_developer_guide/platform_integration_guides/android/initial_sdk_setup/additional_customization_and_configuration.md
@@ -66,7 +66,7 @@ Replace `MIN_LOG_LEVEL` with the **Constant** of the log level you'd like to set
 | `WARN`      | 5              | Logs warning messages for identifying potentially harmful situations.     |
 | `ERROR`     | 6              | Logs error messages for indicating application failure or serious issues. |
 | `ASSERT`    | 7              | Logs assertion messages when conditions are false during development.     |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 For example, the following code will forward log levels `2`, `3`, `4`, `5`, `6`, and `7` to the `Log` method.
 
@@ -102,7 +102,7 @@ Replace `MIN_LOG_LEVEL` with the **Value** of the log level you'd like to set as
 | `WARN`      | 5              | Logs warning messages for identifying potentially harmful situations.     |
 | `ERROR`     | 6              | Logs error messages for indicating application failure or serious issues. |
 | `ASSERT`    | 7              | Logs assertion messages when conditions are false during development.     |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 For example, the following code will forward log levels `2`, `3`, `4`, `5`, `6`, and `7` to the `Log` method.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/android/news_feed/integration.md b/_docs/_developer_guide/platform_integration_guides/android/news_feed/integration.md
index 4f9f0be6a0c..c9cc9a92cc1 100644
--- a/_docs/_developer_guide/platform_integration_guides/android/news_feed/integration.md
+++ b/_docs/_developer_guide/platform_integration_guides/android/news_feed/integration.md
@@ -41,7 +41,7 @@ The [base card](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android
 | `getUpdated()` | Returns the unix timestamp of the card's latest update time from Braze dashboard. |
 | `getCategories()` | Returns the list of categories assigned to the card, cards without a category will be assigned `ABKCardCategoryNoCategory`. |
 | `isInCategorySet(EnumSet)` | Returns true if the card belongs to the given category set. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Banner image card properties
 
@@ -52,7 +52,7 @@ The [base card](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android
 | `getImageUrl()` | Returns the URL of the card's image. |
 | `getUrl()` | Returns the URL that will be opened after the card is clicked on. It can be a HTTP or HTTPS URL or a protocol URL. |
 | `getDomain()` | Returns link text for the property URL. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Captioned image card properties
 
@@ -65,7 +65,7 @@ The [base card](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android
 | `getDescription()` | Returns the body text for the card. |
 | `getUrl()` | Returns the URL that will be opened after the card is clicked on.  It can be a HTTP or HTTPS URL or a protocol URL. |
 | `getDomain()` | Returns the link text for the property URL. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Text announcement card (captioned image without image) properties
 
@@ -77,7 +77,7 @@ The [base card](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android
 | `getDescription()` | Returns the body text for the card. |
 | `getUrl()` | Returns the URL that will be opened after the card is clicked on. It can be a HTTP or HTTPS URL or a protocol URL. |
 | `getDomain()` | Returns the link text for the property URL. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Short news card properties
 
@@ -90,7 +90,7 @@ The [base card](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android
 | `getDescription()` | Returns the body text for the card. |
 | `getUrl()` | Returns the URL that will be opened after the card is clicked on. It can be a HTTP or HTTPS URL or a protocol URL. |
 | `getDomain()` | Returns the link text for the property URL. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Session analytics
 
diff --git a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/customization/advanced_settings.md b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/customization/advanced_settings.md
index 3e84bdacc4a..4f7845abb3a 100644
--- a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/customization/advanced_settings.md
+++ b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/android/customization/advanced_settings.md
@@ -66,7 +66,7 @@ The priority levels that you can set on Android or Fire OS push notifications ar
 | Default  | Most notifications - use if your message doesn't explicitly fall under any of the other priority types | `0` |
 | Low      | Information that you want users to know about but does not require immediate action | `-1` |
 | Min      | Contextual or background information. | `-2` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Refer to Google's [Android notification](http://developer.android.com/design/patterns/notifications.html) documentation for more information.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/fireos/customization/advanced_settings.md b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/fireos/customization/advanced_settings.md
index 791a0506f05..264ca2a45fa 100644
--- a/_docs/_developer_guide/platform_integration_guides/android/push_notifications/fireos/customization/advanced_settings.md
+++ b/_docs/_developer_guide/platform_integration_guides/android/push_notifications/fireos/customization/advanced_settings.md
@@ -58,7 +58,7 @@ The priority levels that you can set on Android or Fire OS push notifications ar
 | Default  | Most notifications - use if your message doesn't explicitly fall under any of the other priority types | `0` |
 | Low      | Information that you want users to know about but does not require immediate action | `-1` |
 | Min      | Contextual or background information. | `-2` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Refer to Google's [Android notification](http://developer.android.com/design/patterns/notifications.html) documentation for more information.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/cordova/content_cards.md b/_docs/_developer_guide/platform_integration_guides/cordova/content_cards.md
index 6ca73eb693f..04e4d33f635 100644
--- a/_docs/_developer_guide/platform_integration_guides/cordova/content_cards.md
+++ b/_docs/_developer_guide/platform_integration_guides/cordova/content_cards.md
@@ -26,7 +26,7 @@ You can use these additional methods to build a custom Content Cards Feed within
 |`logContentCardClicked(cardId)`|Logs a click for the given Content Card ID.|
 |`logContentCardImpression(cardId)`|Logs an impression for the given Content Card ID.|
 |`logContentCardDismissed(cardId)`|Logs a dismissal for the given Content Card ID.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## GIF Support
 
diff --git a/_docs/_developer_guide/platform_integration_guides/flutter/content_cards.md b/_docs/_developer_guide/platform_integration_guides/flutter/content_cards.md
index ac027ace108..90505ae9b1a 100644
--- a/_docs/_developer_guide/platform_integration_guides/flutter/content_cards.md
+++ b/_docs/_developer_guide/platform_integration_guides/flutter/content_cards.md
@@ -25,7 +25,7 @@ You can use these additional methods to build a custom Content Cards Feed within
 | `braze.logContentCardClicked(contentCard)`    | Logs a click for the given Content Card object.                                                            |
 | `braze.logContentCardImpression(contentCard)` | Logs an impression for the given Content Card object.                                                      |
 | `braze.logContentCardDismissed(contentCard)`  | Logs a dismissal for the given Content Card object.                                                        |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Receiving Content Card data
 
diff --git a/_docs/_developer_guide/platform_integration_guides/flutter/push_notifications.md b/_docs/_developer_guide/platform_integration_guides/flutter/push_notifications.md
index 95c7bbd2525..adfc0ce3fba 100644
--- a/_docs/_developer_guide/platform_integration_guides/flutter/push_notifications.md
+++ b/_docs/_developer_guide/platform_integration_guides/flutter/push_notifications.md
@@ -104,7 +104,7 @@ For a full list of push notification fields, refer to the table below:
 | `brazeProperties` | Object    | Represents Braze properties associated with the campaign (key-value pairs). |
 | `ios`              | Object    | Represents iOS-specific fields. |
 | `android`          | Object    | Represents Android-specific fields. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Step 3: Test displaying push notifications
 
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/analytics/disabling_tracking.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/analytics/disabling_tracking.md
index c3ff42d6be8..782a0dceafc 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/analytics/disabling_tracking.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/analytics/disabling_tracking.md
@@ -19,4 +19,4 @@ Additionally, you can use the method [`wipeDataAndDisableForAppRun`](http://appb
 Unless a user uninstalls all apps from a vendor on a given device, the next Braze SDK and app runs after calling `wipeDataAndDisableForAppRun()` will result in our server re-identifying that user via their device identifier (IDFV). In order to fully remove all user data, you should combine a call to `wipeDataAndDisableForAppRun` with a request to delete data on the server via the Braze [REST API]({{site.baseurl}}/developer_guide/rest_api/user_data/#user-delete-endpoint).
 
 ## iOS SDK v5.7.0+
-For devices using iOS SDK v5.7.0 and above, when [disabling IDFV collection](https://www.braze.com/docs/developer_guide/platform_integration_guides/ios/initial_sdk_setup/other_sdk_customizations/swift_idfv/), calling [`wipeData`](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/wipedata()) will not result in our server re-identifying that user via their device identifier (IDFV).
\ No newline at end of file
+For devices using iOS SDK v5.7.0 and above, when [disabling IDFV collection]({{site.baseurl}}/developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/other_sdk_customizations/#optional-idfv-collection---swift/), calling [`wipeData`](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/wipedata()) will not result in our server re-identifying that user via their device identifier (IDFV).
\ No newline at end of file
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/analytics/setting_custom_attributes.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/analytics/setting_custom_attributes.md
index 0cb2708936e..0542d7b4944 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/analytics/setting_custom_attributes.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/analytics/setting_custom_attributes.md
@@ -253,7 +253,7 @@ To set up a subscription for your users (either email or push), call the functio
 | `ABKOptedin` | Subscribed, and explicitly opted in |
 | `ABKSubscribed` | Subscribed, but not explicitly opted in |
 | `ABKUnsubscribed` | Unsubscribed and/or explicitly opted out |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Users who grant permission for an app to send them push notifications default to the status of `ABKOptedin` as iOS requires an explicit opt-in.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/customization/customizing_feed.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/customization/customizing_feed.md
index 1e36c52df77..1932ce0f1ce 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/customization/customizing_feed.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/customization/customizing_feed.md
@@ -15,7 +15,7 @@ noindex: true
 
 You can create your own Content Cards interface by extending `ABKContentCardsTableViewController` to customize all UI elements and Content Cards behavior. The Content Card cells may also be subclassed and then used programmatically or by introducing a custom storyboard that registers the new classes. Check out the Content Cards [sample app](https://github.com/Appboy/appboy-ios-sdk/tree/master/Samples/ContentCards/BrazeContentCardsSampleApp) for a complete example. 
 
-It's also important to consider whether you should use a subclassing strategy versus a completely custom view controller and [subscribe for data updates]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/content_cards/integration/). For example, if you subclass the `ABKContentCardsTableViewController`, you can use the [`populateContentCards` method](#overriding-populated-content-cards) to filter and order cards (recommended). However, if you use a complete view controller customization, you have more control over the card behavior—such as displaying in a carousel or adding interactive elements—but you then have to rely on an observer to implement ordering and filtering logic. You must also implement the respective analytics methods to properly log impressions, dismissal events, and clicks.
+It's also important to consider whether you should use a subclassing strategy versus a completely custom view controller and [subscribe for data updates]({{site.baseurl}}/developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/integration/). For example, if you subclass the `ABKContentCardsTableViewController`, you can use the [`populateContentCards` method](#overriding-populated-content-cards) to filter and order cards (recommended). However, if you use a complete view controller customization, you have more control over the card behavior—such as displaying in a carousel or adding interactive elements—but you then have to rely on an observer to implement ordering and filtering logic. You must also implement the respective analytics methods to properly log impressions, dismissal events, and clicks.
 
 ## Customizing UI
 
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/customization/use_cases/carousel_view.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/customization/use_cases/carousel_view.md
index 6117014256a..faaf36e24bf 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/customization/use_cases/carousel_view.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/customization/use_cases/carousel_view.md
@@ -29,13 +29,13 @@ In terms of the level of development effort, the key differences between the bas
 
 ### Step 1: Create a custom view controller
 
-To create the Content Cards carousel, create your own custom view controller (such as `UICollectionViewController`) and [subscribe for data updates]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/content_cards/integration/#getting-the-data). Note that you won't be able to extend or subclass our default `ABKContentCardTableViewController`, as it's only able to handle our default Content Card types.
+To create the Content Cards carousel, create your own custom view controller (such as `UICollectionViewController`) and [subscribe for data updates]({{site.baseurl}}/developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/integration/#getting-the-data). Note that you won't be able to extend or subclass our default `ABKContentCardTableViewController`, as it's only able to handle our default Content Card types.
 
 ### Step 2: Implement analytics
 
 When creating a fully custom view controller, Content Card impressions, clicks, and dismissals are not automatically logged. You must implement the respective analytics methods to ensure impressions, dismissal events, and clicks get properly logged back to the Braze dashboard analytics.
 
-For information on the analytics methods, refer to [Card methods]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/content_cards/integration/#card-methods). 
+For information on the analytics methods, refer to [Card methods]({{site.baseurl}}/developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/integration/#card-methods). 
 
 {% alert note %}
 The same page also details the different properties inherited from our generic Content Card model class, which you may find useful during your view implementation.
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/implementation_guide.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/implementation_guide.md
index 1252b3323ca..2f422b1d1a3 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/implementation_guide.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/implementation_guide.md
@@ -14,7 +14,7 @@ noindex: true
 
 <br>
 {% alert important %}
-Looking for the basic Content Card developer integration guide? Find it [here]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/content_cards/integration/).
+Looking for the basic Content Card developer integration guide? Find it [here]({{site.baseurl}}/developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/integration/).
 {% endalert %}
 
 # Content Card implementation guide
@@ -460,7 +460,7 @@ Content Cards can be used in a message center format where each message is its o
 For the following message types, the key-value pair `class_type` should be added to your dashboard configuration. The values assigned here are arbitrary but should be distinguishable between class types. These key-value pairs are the key identifiers that the application looks at when deciding where to go when the user clicks on an abridged inbox message.
 
 {% tabs local %}
-{% tab Arbitrary custom view message (full page) %}
+{% tab Arbitrary custom view message - full page %}
 
 The key-value pairs for this use case include:
 
@@ -470,7 +470,7 @@ The key-value pairs for this use case include:
 ![]({% image_buster /assets/img/cc_implementation/full_page.png %}){: style="max-width:60%;"}
 
 {% endtab %}
-{% tab Webview message (HTML) %}
+{% tab Webview message - HTML %}
 
 The key-value pairs for this use case include:
 
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/integration.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/integration.md
index b1f857b3dd3..b44b2a317f0 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/integration.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/content_cards/integration.md
@@ -85,7 +85,7 @@ Braze offers three Content Card types: banner, captioned image, and classic. Eac
 | `url` | The URL that will be opened after the card is clicked on. It can be an HTTP(s) URL or a protocol URL.|
 | `openURLInWebView` | This property determines whether the URL will be opened within the app or in an external web browser.|
 | `extras`| An optional `NSDictionary` of `NSString` values.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Banner Content Card properties - ABKBannerContentCard
 
@@ -93,7 +93,7 @@ Braze offers three Content Card types: banner, captioned image, and classic. Eac
 |---|---|
 | `image` | This property is the URL of the card's image.|
 | `imageAspectRatio` | This property is the aspect ratio of the card's image and serves as a hint before image loading completes. Note that the property may not be supplied in certain circumstances. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Captioned image Content Card properties - ABKCaptionedImageCard
 
@@ -104,7 +104,7 @@ Braze offers three Content Card types: banner, captioned image, and classic. Eac
 | `title` | The title text for the card.|
 | `cardDescription` | The body text for the card.|
 | `domain` | The link text for the property URL, like @"blog.braze.com". It can be displayed on the card's UI to indicate the action/direction of clicking on the card.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Classic Content Card properties - ABKClassicContentCard
 
@@ -114,7 +114,7 @@ Braze offers three Content Card types: banner, captioned image, and classic. Eac
 | `title` | The title text for the card. |
 | `cardDescription` | The body text for the card. |
 | `domain` | The link text for the property URL, like @"blog.braze.com". It can be displayed on the card's UI to indicate the action and direction of clicking on the card. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Card methods
 
@@ -124,7 +124,7 @@ Braze offers three Content Card types: banner, captioned image, and classic. Eac
 | `logContentCardClicked` | Manually log a click to Braze for a particular card. The SDK will only log a card click when the card has the `url` property with a valid value. |
 | `logContentCardDismissed` | Manually log a dismissal to Braze for a particular card. The SDK will only log a card dismissal if the card's `dismissed` property is not already set to `true`. |
 | `isControlCard` | Determine if a card is the Control card for an A/B test. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For more details, refer to the [class reference documentation](https://appboy.github.io/appboy-ios-sdk/docs/interface_a_b_k_content_card.html)
 
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/behavior_on_click.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/behavior_on_click.md
index 1052a956300..c74791a07fb 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/behavior_on_click.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/behavior_on_click.md
@@ -43,7 +43,7 @@ The `inAppMessageClickActionType` can be set to one of the following values:
 | `ABKInAppMessageDisplayNewsFeed` | The News Feed will be displayed when the message is clicked, and the message will be dismissed. Note that the `uri` parameter will be ignored, and the `uri` property on the `ABKInAppMessage` will be set to nil. |
 | `ABKInAppMessageRedirectToURI` | The given URI will be displayed when the message is clicked, and the message will be dismissed. Note that the `uri` parameter cannot be nil. |
 | `ABKInAppMessageNoneClickAction` | The message will be dismissed when clicked. Note that the `uri` parameter will be ignored, and the `uri` property on the `ABKInAppMessage` will be set to nil. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 For in-app messages containing buttons, the message `clickAction` will also be included in the final payload if the click action is added prior to adding the button text.
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/handling_in_app_display.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/handling_in_app_display.md
index e80ee8c42f4..c91d8487992 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/handling_in_app_display.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/handling_in_app_display.md
@@ -59,7 +59,7 @@ You can customize in-app message handling by implementing this delegate method a
 | Objective-C: `ABKDisplayInAppMessageNow`<br>Swift: `displayInAppMessageNow` | The message will be displayed immediately. |
 | Objective-C: `ABKDisplayInAppMessageLater`<br>Swift: `displayInAppMessageLater` | The message will be not be displayed and will be placed back on the top of the stack. |
 | Objective-C: `ABKDiscardInAppMessage`<br>Swift: `discardInAppMessage`| The message will be discarded and will not be displayed. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 You can use the `beforeInAppMessageDisplayed:` delegate method to add in-app message display logic, customize in-app messages before Braze displays them, or opt-out of Braze's in-app message display logic and UI entirely.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/modal_dismissal.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/modal_dismissal.md
index 60f18b724aa..c70fd6ef89a 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/modal_dismissal.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/in-app_messaging/customization/modal_dismissal.md
@@ -31,4 +31,4 @@ You can also enable the feature at runtime by setting `ABKEnableDismissModalOnOu
 |----------|-------------|
 | `YES`       | Modal in-app messages will be dismissed on outside tap.     |
 | `NO`        | Default, modal in-app messages will not be dismissed on outside tap. |
-{: .reset-td-br-1 .reset-td-br-2}
\ No newline at end of file
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
\ No newline at end of file
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/ios_sdk_integration.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/ios_sdk_integration.md
index 38943285c75..745d522cefb 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/ios_sdk_integration.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/ios_sdk_integration.md
@@ -35,7 +35,7 @@ The following steps help you build a `BrazeManager` helper file that your produc
 ### Create BrazeManager.swift
 
 {% tabs local %}
-{% tab Create BrazeManager.swift %}
+{% tab Create BrazeManager swift %}
 
 ##### Create BrazeManager.swift
 To build out your `BrazeManager.swift` file, create a new Swift file named _BrazeManager_ to add to your project at your desired location. Next, Replace `import Foundation` with `import AppboyUI` for SPM (`import Appboy_iOS_SDK` for CocoaPods) and then create a `BrazeManager` class that will be used to host all Braze-related methods and variables. `Appboy_iOS_SDK`
@@ -100,7 +100,7 @@ class BrazeManager: NSObject {
 ### Initialize the SDK
 
 {% tabs local %}
-{% tab Step 1: Initialize SDK from BrazeManager.swift %}
+{% tab Step 1: Initialize SDK from BrazeManager swift %}
 
 ##### Initialize SDK from BrazeManager.swift
 Next, you must initialize the SDK. This guide assumes you have already [added the SDK]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/overview/) into your Xcode project. You must also have your [workspace SDK endpoint]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/completing_integration/#step-2-specify-your-data-cluster) and [`LogLevel`]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/other_sdk_customizations/#braze-log-level) set in your `Info.plist` file or in `appboyOptions`.
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/other_sdk_customizations.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/other_sdk_customizations.md
index f86e694076f..357c3385530 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/other_sdk_customizations.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/other_sdk_customizations.md
@@ -27,7 +27,7 @@ See the following list of available log levels:
 | 2        | Warning. Warning and higher log information will be logged to the iOS console.  |
 | 4        | Error. Error and higher log information will be logged to the iOS console.  |
 | 8        | Minimal. Minimal information will be logged to the iOS console. The SDK's default setting. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Verbose logging
 
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/overview.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/overview.md
index a4249307f56..c354d3928d3 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/overview.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/overview.md
@@ -12,22 +12,22 @@ description: "This landing page covers Braze SDK integration guides for CocoaPod
 guide_featured_title: "Basic integration options"
 guide_featured_list:
 - name: CocoaPods
-  link: /docs/developer_guide/platform_integration_guides/ios/initial_sdk_setup/installation_methods/cocoapods/
+  link: /developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/installation_methods/cocoapods/
   image: /assets/img/cocoapods.png
 - name: Swift Package Manager (SPM)
-  link: /docs/developer_guide/platform_integration_guides/ios/initial_sdk_setup/installation_methods/swift_package_manager/
+  link: /docs/developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/installation_methods/swift_package_manager/
   image: /assets/img/braze_icons/swift.svg
 - name: Carthage
-  link: /docs/developer_guide/platform_integration_guides/ios/initial_sdk_setup/installation_methods/carthage_integration/
+  link: /docs/developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/installation_methods/carthage_integration/
   image: /assets/img/carthage.png
 - name: Manual
-  link: /docs/developer_guide/platform_integration_guides/ios/initial_sdk_setup/installation_methods/manual_integration_options/
+  link: /docs/developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/installation_methods/manual_integration_options/
   image: /assets/img/braze_icons/tool-01.svg
 - name: "Completing the Integration"
-  link: /docs/developer_guide/platform_integration_guides/ios/initial_sdk_setup/completing_integration/
+  link: /docs/developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/completing_integration/
   image: /assets/img/braze_icons/flag-05.svg
 - name: "Other Optional SDK Customizations"
-  link: /docs/developer_guide/platform_integration_guides/ios/initial_sdk_setup/other_sdk_customizations/
+  link: /docs/developer_guide/platform_integration_guides/legacy_sdks/ios/initial_sdk_setup/ios_sdk_integration
   image: /assets/img/braze_icons/user-square.svg
 
 noindex: true
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/news_feed/integration.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/news_feed/integration.md
index d9a9f98dde7..fbe1196657f 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/news_feed/integration.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/news_feed/integration.md
@@ -85,7 +85,7 @@ Braze has five unique card types: banner image, captioned image, text announceme
 | `updated` | (Read only) The property is the unix timestamp of the card's latest update time from Braze dashboard. |
 | `categories` | The list of categories assigned to the card, cards without a category will be assigned `ABKCardCategoryNoCategory`.<br><br>Available categories:<br>- `ABKCardCategoryNoCategory`<br>- `ABKCardCategoryNews`<br>- `ABKCardCategoryAdvertising`<br>- `ABKCardCategoryAnnouncements`<br>- `ABKCardCategorySocial`<br>- `ABKCardCategoryAll` |
 | `extras` | An optional `NSDictionary` of `NSString` values. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Banner image card properties
 
@@ -94,7 +94,7 @@ Braze has five unique card types: banner image, captioned image, text announceme
 | `image` | (Required) This property is the URL of the card's image. |
 | `URL` | (Optional) The URL that will be opened after the card is clicked on. It can be an HTTP(S) URL or a protocol URL. |
 | `domain` | (Optional) The link text for the property URL, like @"blog.braze.com". It can be displayed on the card's UI to indicate the action and direction of clicking on the card but is hidden in the default Braze News Feed. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Captioned image card properties
 
@@ -105,7 +105,7 @@ Braze has five unique card types: banner image, captioned image, text announceme
 | `description` (Required) The body text for the card. |
 | `URL` | (Optional) The URL that will be opened after the card is clicked on. It can be an HTTP(S) URL or a protocol URL. |
 | `domain` | (Optional) The link text for the property URL, like @"blog.braze.com". It can be displayed on the card's UI to indicate the action and direction of clicking on the card. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Text announcement card (captioned image without image) properties
 
@@ -115,7 +115,7 @@ Braze has five unique card types: banner image, captioned image, text announceme
 | `description` | (Required) The body text for the card. |
 | `url` | (Optional) The URL that will be opened after the card is clicked on. It can be an HTTP(S) URL or a protocol URL. |
 | `domain` | (Optional) The link text for the property URL, like @"blog.braze.com". It can be displayed on the card's UI to indicate the action and direction of clicking on the card. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Classic card properties
 
@@ -126,7 +126,7 @@ Braze has five unique card types: banner image, captioned image, text announceme
 | `description` | (Required) The body text for the card. |
 | `URL` | (Optional) The URL that will be opened after the card is clicked on. It can be an HTTP(S) URL or a protocol URL. |
 | `domain` | (Optional) The link text for the property URL, like @"blog.braze.com". It can be displayed on the card's UI to indicate the action and direction of clicking on the card. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Card methods
 
@@ -134,7 +134,7 @@ Braze has five unique card types: banner image, captioned image, text announceme
 |---|---|
 | `logCardImpression` | Manually log an impression to Braze for a particular card. |
 | `logCardClicked` | Manually log a click to Braze for a particular card. The SDK will only log a card click when the card has the `url` property with a valid value. All subclasses of `ABKCard` have the `url` property. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Log feed display
 
diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/silent_push_notifications.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/silent_push_notifications.md
index a4a9978c12a..8a33c997657 100644
--- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/silent_push_notifications.md
+++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/silent_push_notifications.md
@@ -56,7 +56,7 @@ Braze has several features which rely on iOS silent push notifications:
 |---|---|
 |Uninstall Tracking | User receives a silent, nightly uninstall tracking push.|
 |Geofences | Silent syncing of geofences from server to device.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Refer to Apple's [instance method](https://developer.apple.com/documentation/uikit/uiapplicationdelegate/1623013-application) and [unreceived notifications](https://developer.apple.com/library/content/technotes/tn2265/_index.html#//apple_ref/doc/uid/DTS40010376-CH1-TNTAG23) documentation for more details.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/react_native/content_cards.md b/_docs/_developer_guide/platform_integration_guides/react_native/content_cards.md
index 9d2bd02b4be..92b8cc4e9e1 100644
--- a/_docs/_developer_guide/platform_integration_guides/react_native/content_cards.md
+++ b/_docs/_developer_guide/platform_integration_guides/react_native/content_cards.md
@@ -49,7 +49,7 @@ You can use these additional methods to build a custom Content Cards Feed within
 | `logContentCardImpression(cardId)`       | Logs an impression for the given Content Card ID.                                                      |
 | `logContentCardDismissed(cardId)`        | Logs a dismissal for the given Content Card ID.                                                        |
 | `processContentCardClickAction(cardId)`  | Perform the action of a particular card.                                                               |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Test displaying sample Content Card
 
@@ -93,7 +93,7 @@ The base card model provides foundational behavior for all cards.
 |`openURLInWebView` | Whether URLs for this card should be opened in Braze's WebView or not.                                            |
 |`isControl`   | Whether this card is a control card. Control cards should not be displayed to the user.                                |
 |`extras`      | The map of key-value extras for this card.                                                                             |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of the base card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/data-swift.struct) documentation.
 
@@ -106,7 +106,7 @@ Image only cards are clickable, full-sized images.
 |`type`             | The Content Card type, `IMAGE_ONLY`.                                                                              |
 |`image`            | The URL of the card's image.                                                                                      |
 |`imageAspectRatio` | The aspect ratio of the card's image. It is meant to serve as a hint before image loading completes. Note that the property may not be supplied in certain circumstances. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of the image only card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-image-only-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/imageonly-swift.struct) documentation.
 
@@ -122,7 +122,7 @@ Captioned image cards are clickable, full-sized images with accompanying descrip
 |`title`            | The title text for the card.                                                                                      |
 |`cardDescription`  | The description text for the card.                                                                                |
 |`domain`           | (Optional) The link text for the property URL, for example, `"braze.com/resources/"`. It can be displayed on the card's UI to indicate the action/direction of clicking on the card. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of the captioned image card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-captioned-image-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/captionedimage-swift.struct) documentation.
 
@@ -137,7 +137,7 @@ Classic cards have a title, description, and an optional image on the left of th
 |`title`            | The title text for the card.                                                                                      |
 |`cardDescription`  | The description text for the card.                                                                                |
 |`domain`           | (Optional) The link text for the property URL, for example, `"braze.com/resources/"`. It can be displayed on the card's UI to indicate the action/direction of clicking on the card. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of the classic (text announcement) Content Card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-text-announcement-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/classic-swift.struct) documentation. For a full reference of the classic image (short news) card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-short-news-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/classicimage-swift.struct) documentation.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/react_native/inapp_messages.md b/_docs/_developer_guide/platform_integration_guides/react_native/inapp_messages.md
index 7833b062c1e..b389cce3c42 100644
--- a/_docs/_developer_guide/platform_integration_guides/react_native/inapp_messages.md
+++ b/_docs/_developer_guide/platform_integration_guides/react_native/inapp_messages.md
@@ -194,7 +194,7 @@ The in-app message model provides the base for all in-app messages.
 |`extras`          | The message extras dictionary. Default value: `[:]`.                                                                   |
 |`buttons`         | The list of buttons on the in-app message.                                                                             |
 |`toString()`      | The message as a String representation.                                                                                |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of the in-app message model, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.inappmessage/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/inappmessage) documentation.
 
@@ -210,7 +210,7 @@ Buttons can be added to in-app messages to perform actions and log analytics. Th
 |`clickAction`     | The type of click action processed when the user clicks on the button. The three types are: `NEWS_FEED`, `URI`, and `NONE`. |
 |`id`              | The button ID on the message.                                                                                               |
 |`toString()`      | The button as a String representation.                                                                                      |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of button model, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.inappmessage/-message-button/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/inappmessage/button) documentation.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/react_native/push_notifications.md b/_docs/_developer_guide/platform_integration_guides/react_native/push_notifications.md
index f7a5de828ce..bdeb70be92c 100644
--- a/_docs/_developer_guide/platform_integration_guides/react_native/push_notifications.md
+++ b/_docs/_developer_guide/platform_integration_guides/react_native/push_notifications.md
@@ -146,7 +146,7 @@ For a full list of push notification fields, refer to the table below:
 | `braze_properties` | Object    | Represents Braze properties associated with the campaign (key-value pairs). |
 | `ios`              | Object    | Represents iOS-specific fields. |
 | `android`          | Object    | Represents Android-specific fields. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Step 3: Enable deep linking (optional)
 
diff --git a/_docs/_developer_guide/platform_integration_guides/react_native/react_sdk_setup.md b/_docs/_developer_guide/platform_integration_guides/react_native/react_sdk_setup.md
index d5958702d9b..36ac386977b 100644
--- a/_docs/_developer_guide/platform_integration_guides/react_native/react_sdk_setup.md
+++ b/_docs/_developer_guide/platform_integration_guides/react_native/react_sdk_setup.md
@@ -87,7 +87,7 @@ In your `app.json`, add the Braze Expo Plugin. You can provide the following con
 | `enableBrazeIosPushStories`                   | boolean | iOS only. Whether to enable Braze Push Stories for iOS.                                                                                                  |
 | `iosPushStoryAppGroup`                        | string  | iOS only. The app group used for iOS Push Stories.                                                                                                       |
 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Example configuration:
 
diff --git a/_docs/_developer_guide/platform_integration_guides/roku/analytics/setting_custom_attributes.md b/_docs/_developer_guide/platform_integration_guides/roku/analytics/setting_custom_attributes.md
index 548fdc9e167..ea0f88bdaf1 100644
--- a/_docs/_developer_guide/platform_integration_guides/roku/analytics/setting_custom_attributes.md
+++ b/_docs/_developer_guide/platform_integration_guides/roku/analytics/setting_custom_attributes.md
@@ -50,7 +50,7 @@ m.Braze.setCustomAttribute("boolAttribute", true)
 m.Braze.setCustomAttribute("intAttribute", 5)
 ```
 {% endtab %}
-{% tab Float/Double %}
+{% tab Float or Double %}
 ```brightscript
 m.Braze.setCustomAttribute("floatAttribute", 3.5)
 ```
@@ -112,7 +112,7 @@ You can set the following email subscription statuses for your users programmati
 | `OptedIn` | Subscribed, and explicitly opted in |
 | `Subscribed` | Subscribed, but not explicitly opted in |
 | `UnSubscribed` | Unsubscribed and/or explicitly opted out |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 >  These types fall under `BrazeConstants().SUBSCRIPTION_STATES`
 
diff --git a/_docs/_developer_guide/platform_integration_guides/roku/in-app_messaging/integration.md b/_docs/_developer_guide/platform_integration_guides/roku/in-app_messaging/integration.md
index b039c3fd59f..f80dcf69b57 100644
--- a/_docs/_developer_guide/platform_integration_guides/roku/in-app_messaging/integration.md
+++ b/_docs/_developer_guide/platform_integration_guides/roku/in-app_messaging/integration.md
@@ -54,7 +54,7 @@ The following lists the fields you will need to handle your in-app messages:
 | `image_url` | In-app message image URL. |
 | `message` | Message body text. |
 | `uri` | Your URI users will be sent to based on your `click_action`. This field must be included when `click_action` is `"URI"`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 For in-app messages containing buttons, the message `click_action` will also be included in the final payload if the click action is added prior to adding the button text.
@@ -71,7 +71,7 @@ There are also various styling fields that you could choose to use from the dash
 | `header_text_color` | Header text color. |
 | `message_text_color` | Message text color. |
 | `text_align` | "START", "CENTER", or "END". Your selected text alignment. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Alternatively, you could implement the in-app message and style it within your Roku application using a standard palette:
 
@@ -83,7 +83,7 @@ Alternatively, you could implement the in-app message and style it within your R
 | `id` | The ID value of the button itself. |
 | `text` | The text to display on the button. |
 | `uri` | Your URI users will be sent to based on your `click_action`. This field must be included when `click_action` is `"URI"`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Handling interactions
 
diff --git a/_docs/_developer_guide/platform_integration_guides/sdk_primer.md b/_docs/_developer_guide/platform_integration_guides/sdk_primer.md
index a80daa9a3bb..48df522462e 100644
--- a/_docs/_developer_guide/platform_integration_guides/sdk_primer.md
+++ b/_docs/_developer_guide/platform_integration_guides/sdk_primer.md
@@ -46,7 +46,7 @@ The Braze SDK caches data (sessions, custom events, etc.) and uploads it periodi
 |Great    |10 Seconds|
 |Good    |30 Seconds|
 |Poor    |60 Seconds|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 If there is no network connection, data is cached locally on the device until the network connection is re-established. When the connection is re-established, the data will be uploaded to Braze.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/advanced_use_cases/delayed_initialization.md b/_docs/_developer_guide/platform_integration_guides/swift/advanced_use_cases/delayed_initialization.md
index 724aaa60f9b..0e1d25f9a06 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/advanced_use_cases/delayed_initialization.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/advanced_use_cases/delayed_initialization.md
@@ -26,7 +26,7 @@ The Swift SDK does not capture non-Braze push notifications&#8212;these will con
 {% endalert %}
 
 {% tabs %}
-{% tab Swift (UIKit) %}
+{% tab Swift - UIKit %}
 ```swift
 func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
   // Prepare the SDK for delayed initialization
@@ -39,7 +39,7 @@ func application(_ application: UIApplication, didFinishLaunchingWithOptions lau
 ```
 {% endtab %}
 
-{% tab Swift (SwiftUI) %}
+{% tab Swift - SwiftUI %}
 SwiftUI applications require implementing the [@UIApplicationDelegateAdaptor](https://developer.apple.com/documentation/swiftui/uiapplicationdelegateadaptor) property wrapper to call the `prepareForDelayedInitialization()` method.
 
 ```swift
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/analytics/setting_custom_attributes.md b/_docs/_developer_guide/platform_integration_guides/swift/analytics/setting_custom_attributes.md
index 10b593cb959..7dd20d12a57 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/analytics/setting_custom_attributes.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/analytics/setting_custom_attributes.md
@@ -246,7 +246,7 @@ To set up a subscription for your users (either email or push), call the functio
 | `optedIn` | Subscribed, and explicitly opted in |
 | `subscribed` | Subscribed, but not explicitly opted in |
 | `unsubscribed` | Unsubscribed and/or explicitly opted out |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Users who grant permission for an app to send them push notifications default to the status of `optedIn` as iOS requires an explicit opt-in.
 
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/content_cards/integration.md b/_docs/_developer_guide/platform_integration_guides/swift/content_cards/integration.md
index b35336b9500..26c0f716637 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/content_cards/integration.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/content_cards/integration.md
@@ -115,7 +115,7 @@ Each card is initialized with a `Context` object, which contains various methods
 | `card.context?.logDismissed()`       | Log the content card dismissed event.                                                                                                    |
 | `card.context?.logError()`           | Log an error related to the content card.                                                                                                |
 | `card.context?.loadImage()`          | Load a given content card image from a URL. This method can be nil when the content card does not have an image.                         |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For more details, refer to the [`Context` class documentation](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcardraw/context-swift.class)
 
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/behavior_on_click.md b/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/behavior_on_click.md
index f1260db281a..4a0a3552995 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/behavior_on_click.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/behavior_on_click.md
@@ -45,7 +45,7 @@ The `clickAction` property on your `Braze.InAppMessage` defaults to `.none` but
 | `.url(URL, useWebView: Bool)` | Opens the given URL in an external browser. If `useWebView` is set to `true`, it will open in a web view. |
 | `.newsFeed` | News Feed will be displayed when the message is clicked, and the message will be dismissed.<br><br>**Note:** The News Feed is being deprecated. Check out the [migration guide]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/migrating_from_news_feed/) for more details. |
 | `.none` | The message will be dismissed when clicked. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 For in-app messages containing buttons, the message `clickAction` will also be included in the final payload if the click action is added prior to adding the button text.
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/modal_dismissal.md b/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/modal_dismissal.md
index 9643ae8806d..c079681bb79 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/modal_dismissal.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/modal_dismissal.md
@@ -35,6 +35,6 @@ The default value is `false`. This determines if the modal in-app message will b
 |----------|-------------|
 | `true`         | Modal in-app messages will be dismissed on outside tap.     |
 | `false`        | Default, modal in-app messages will not be dismissed on outside tap. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For more details on in-app message customization, refer to this [article](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/in-app-message-customization).
\ No newline at end of file
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/setting_delegates.md b/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/setting_delegates.md
index e349118ccb9..6709e9ded9c 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/setting_delegates.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/setting_delegates.md
@@ -97,7 +97,12 @@ func inAppMessage(
 {% endtab %}
 {% tab OBJECTIVE-C %}
 
-The `inAppMessage(_:prepareWith:)` method is not available in Objective-C.
+```objc
+- (void)inAppMessage:(BrazeInAppMessageUI *)ui
+         prepareWith:(BrazeInAppMessageUIPresentationContextRaw *)context {
+  context.preferredOrientation = BRZInAppMessageRawOrientationPortrait;
+}
+```
 
 {% endtab %}
 {% endtabs %}
@@ -216,7 +221,40 @@ func inAppMessage(
 {% endtab %}
 {% tab OBJECTIVE-C %}
 
-The `inAppMessage(_:prepareWith:)` method is not available in Objective-C.
+```objc
+- (void)inAppMessage:(BrazeInAppMessageUI *)ui
+         prepareWith:(BrazeInAppMessageUIPresentationContextRaw *)context {
+  switch (context.message.type) {
+    case BRZInAppMessageRawTypeSlideup: {
+      NSMutableDictionary *updatedThemes = [context.message.themes mutableCopy];
+      [updatedThemes removeObjectForKey:@"dark"];
+      context.message.themes = updatedThemes;
+      break;
+    }
+    case BRZInAppMessageRawTypeModal:
+    case BRZInAppMessageRawTypeFull:
+    {
+      NSMutableDictionary *updatedThemes = [context.message.themes mutableCopy];
+      [updatedThemes removeObjectForKey:@"dark"];
+      context.message.themes = updatedThemes;
+
+      NSMutableArray *updatedButtons = [NSMutableArray arrayWithCapacity:context.message.buttons.count];
+      for (BRZInAppMessageRawButton *button in context.message.buttons) {
+        BRZInAppMessageRawButtonTheme *lightTheme = BRZInAppMessageRawButtonTheme.defaultLight;
+        BRZInAppMessageRawButton *newButton = [button mutableCopy];
+        newButton.textColor = lightTheme.textColor;
+        newButton.backgroundColor = lightTheme.backgroundColor;
+        newButton.borderColor = lightTheme.borderColor;
+        [updatedButtons addObject:newButton];
+      }
+      context.message.buttons = updatedButtons;
+      break;
+    }
+    default:
+      break;
+  }
+}
+```
 
 {% endtab %}
 {% endtabs %}
@@ -296,7 +334,7 @@ For `Full`, `FullImage` and `HTML` in-app messages, the SDK will hide the status
 | `.auto`                             | The message view decides the status bar hidden state.                                 |
 | `.hidden`                           | Always hide the status bar.                                                           |
 | `.visible`                          | Always display the status bar.                                                        |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Customizing display timing 
 
@@ -330,7 +368,7 @@ Configure `BrazeInAppMessageUI.DisplayChoice` to return one of the following val
 | `.reenqueue`                        | The message will be not be displayed and will be placed back on the top of the stack.                                       |
 | `.later`                            | The message will be not be displayed and will be placed back on the top of the stack. (Deprecated, please use `.reenqueue`) |
 | `.discard`                          | The message will be discarded and will not be displayed.                                                                    |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Implementation samples
 
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/troubleshooting.md b/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/troubleshooting.md
index f7180f9b17f..72112f9427b 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/troubleshooting.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/troubleshooting.md
@@ -11,68 +11,7 @@ channel:
 
 # Troubleshooting
 
-> This reference article covers potential iOS in-app message troubleshooting topics.
-
-## Impressions
-
-### Impression or click analytics aren't being logged
-
-If you have set an in-app message delegate to manually handle message display or click actions, you'll need to manually [log clicks](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/inappmessage/logclick(buttonid:using:)) and [impressions](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/inappmessage/logimpression(using:)) on the in-app message.
-
-### Impressions are lower than expected
-
-Triggers take time to sync to the device on session start, so there can be a race condition if users log an event or purchase right after they start a session. One potential workaround could be changing the campaign to trigger off of session start, then segmenting off the intended event or purchase. Note that this would deliver the in-app message on the next session start after the event has occurred.
-
-## Expected in-app message did not display
-
-Most in-app message issues can be broken down into two main categories: delivery and display. To troubleshoot why an expected in-app message did not display on your device, you should first ensure that the [in-app message was delivered to the device](#troubleshooting-in-app-message-delivery), then [troubleshoot message display](#troubleshooting-in-app-message-display).
-
-### Troubleshooting in-app message delivery {#troubleshooting-in-app-message-delivery}
-
-The SDK requests in-app messages from Braze servers on session start. To check if in-app messages are being delivered to your device, you'll need to ensure that in-app messages are being both requested by the SDK and returned by Braze servers.
-
-#### Check if messages are requested and returned
-
-1. Add yourself as a [test user]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#adding-test-users) on the dashboard.
-2. Set up an in-app message campaign targeted at your user.
-3. Ensure that a new session occurs in your application.
-4. Use the [event user logs]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab) to check that your device is requesting in-app messages on session start. Find the SDK request associated with your test user's session start event.
-  - If your app was meant to request triggered in-app messages, you should see `trigger` in the **Requested Responses** field under **Response Data**.
-  - If your app was meant to request original in-app messages, you should see  `in_app` in the **Requested Responses** field under **Response Data**.
-5. Use the [event user logs]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab) to check if the correct in-app messages are being returned in the response data.<br>![]({% image_buster /assets/img_archive/event_user_log_iams.png %})
-
-#### Messages not being requested
-
-If your in-app messages are not being requested, your app might not be tracking sessions correctly, as in-app messages are refreshed upon session start. Also, be sure that your app is actually starting a session based on your app's session timeout semantics:
-
-![The SDK request found in the event user logs displaying a successful session start event.]({% image_buster /assets/img_archive/event_user_log_session_start.png %})
-
-#### Messages not being returned
-
-If your in-app messages are not being returned, you're likely experiencing a campaign targeting issue.
-
-##### Your segment does not contain your user
-Check your user's [**Engagement**]({{ site.baseurl }}/user_guide/engagement_tools/segments/user_profiles/#engagement-tab) tab to see if the correct segment appears under **Segments**.
-
-##### Your user has previously received the in-app message and was not re-eligible to receive it again
-Check the [campaign re-eligibility settings]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/) under the **Delivery** step of the **Campaign Composer** and make sure the re-eligibility settings align with your testing setup.
-
-##### Your user hit the frequency cap for the campaign
-Check the campaign [frequency cap settings]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping) and ensure they align with your testing setup.
-
-##### User fallen out of the control group
-If there was a control group on the campaign, your user may have fallen into the control group. You can check if this has happened by creating a segment with a received campaign variant filter, where the campaign variant is set to **Control**, and checking if your user fell into that segment. 
-
-When creating campaigns for integration testing purposes, make sure to opt out of adding a control group.
-
-### Troubleshooting in-app message display {#troubleshooting-in-app-message-display}
-
-If your app is successfully requesting and receiving in-app messages but they are not being shown, some device-side logic may be preventing display:
-
-- Triggered in-app messages are rate-limited based on the [minimum time interval between triggers]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers), which defaults to 30 seconds.
-- If you have set a delegate to customize in-app message handling, check your delegate to ensure it is not affecting in-app message display.
-- Failed image downloads will prevent in-app messages with images from displaying. Check your device logs to ensure that image downloads are not failing.
-- If the device orientation did not match the orientation specified by the in-app message, the in-app message will not display. Make sure that your device is in the correct orientation.
+{% multi_lang_include inapp_message_troubleshooting.md sdk="iOS" %}
 
 ### Troubleshooting asset loading (`NSURLError` code `-1008`)
 
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration.md b/_docs/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration.md
index 8db34325283..fda97ee9927 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration.md
@@ -32,7 +32,7 @@ The Braze Swift SDK contains a variety of standalone XCFrameworks, which gives y
 | `BrazeUICompat`            | No        | Compatibility library containing all the `ABK*` classes and methods that were available in the `AppboyUI` library from `Appboy-iOS-SDK` version 4.X.X. For usage details, refer to the minimal migration scenario in the [migration guide](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/appboy-migration-guide/). |
 | `SDWebImage`               | No        | Dependency used only by `BrazeUICompat` in the minimal migration scenario. |
 
-{: .ws-td-nw-1 .reset-td-br-1 .reset-td-br-2}
+{: .ws-td-nw-1 .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Step 3: Prepare your files
 
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/other_sdk_customizations.md b/_docs/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/other_sdk_customizations.md
index bc563b719c4..7e0814d4853 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/other_sdk_customizations.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/other_sdk_customizations.md
@@ -25,7 +25,7 @@ See the following list of available log levels:
 | `.info`     | `BRZLoggerLevelInfo`     | Log general SDK information (user changes, etc.) + `.error`. |
 | `.error`    | `BRZLoggerLevelError`    | Log errors.                                                       |
 | `.disabled` | `BRZLoggerLevelDisabled` | No logging occurs.                                                |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Setting log level
 
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/live_activities/faq.md b/_docs/_developer_guide/platform_integration_guides/swift/live_activities/faq.md
index b0ed682a805..4356698725d 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/live_activities/faq.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/live_activities/faq.md
@@ -76,7 +76,7 @@ The limits are defined by Apple and can vary based on a number of factors. They
 
 ### What other things should I watch out for during troubleshooting?
 
-- Check that you are using a `.p8` key for authentication.
+- Ensure that you are using a `.p8` key for authentication instead of a `.p12` or `.pem` file.
 - Check that your push provisioning profile matches the environment you’re testing. Universal certificates may be configured in the Braze dashboard to send to either the development or production Apple Push Notification service (APNs) environment. Using a development certificate for a production app or a production certificate for a development app will not work.
 
 
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/live_activities/live_activities.md b/_docs/_developer_guide/platform_integration_guides/swift/live_activities/live_activities.md
index efe30deec27..122482ca1f8 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/live_activities/live_activities.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/live_activities/live_activities.md
@@ -25,6 +25,7 @@ Additional prerequisites include:
 
 - Live Activities are only available for iPhones and iPads on iOS 16.1 and later. To use this feature, ensure that your project is targeting this iOS version.
 - The `Push Notification` entitlement must be added under **Signing & Capabilities** in your Xcode project.
+- Live Activities require using a `.p8` key to send the notification. Older files such as a `.p12` or `.pem` are not supported.
 - Starting with version 8.2.0 of the Braze Swift SDK, you can [remotely register a Live Activity](#step-2-start-the-activity). To use this feature, iOS 17.2 or later is required.
 
 {% alert note %}
diff --git a/_docs/_developer_guide/platform_integration_guides/swift/push_notifications/silent_push_notifications.md b/_docs/_developer_guide/platform_integration_guides/swift/push_notifications/silent_push_notifications.md
index 0ddeb98a005..f101811b8f3 100644
--- a/_docs/_developer_guide/platform_integration_guides/swift/push_notifications/silent_push_notifications.md
+++ b/_docs/_developer_guide/platform_integration_guides/swift/push_notifications/silent_push_notifications.md
@@ -21,7 +21,7 @@ Braze has several features which rely on silent push notifications:
 |---|---|
 |[Uninstall Tracking]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/uninstall_tracking/) | User receives a silent, nightly uninstall tracking push.|
 |[Geofences]({{site.baseurl}}/user_guide/engagement_tools/locations_and_geofences) | Silent syncing of geofences from server to device.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Setting up silent push notifications
 
diff --git a/_docs/_developer_guide/platform_integration_guides/unity/analytics/setting_custom_attributes.md b/_docs/_developer_guide/platform_integration_guides/unity/analytics/setting_custom_attributes.md
index 2f041c6f646..7d415e2fb8f 100644
--- a/_docs/_developer_guide/platform_integration_guides/unity/analytics/setting_custom_attributes.md
+++ b/_docs/_developer_guide/platform_integration_guides/unity/analytics/setting_custom_attributes.md
@@ -141,7 +141,7 @@ To set up a subscription for your users (either email or push), call the functio
 | `OPTED_IN` | Subscribed, and explicitly opted in |
 | `SUBSCRIBED` | Subscribed, but not explicitly opted in |
 | `UNSUBSCRIBED` | Unsubscribed and/or explicitly opted out |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 >  No explicit opt-in is required by Windows to send users push notifications. When a user is registered for push, they are set to `SUBSCRIBED` rather than `OPTED_IN` by default. To learn more, check out our documentation on [implementing subscriptions and explicit opt-ins][10].
 
diff --git a/_docs/_developer_guide/platform_integration_guides/unity/push_notifications/android.md b/_docs/_developer_guide/platform_integration_guides/unity/push_notifications/android.md
index 977efde0d5b..f603a26b326 100644
--- a/_docs/_developer_guide/platform_integration_guides/unity/push_notifications/android.md
+++ b/_docs/_developer_guide/platform_integration_guides/unity/push_notifications/android.md
@@ -113,3 +113,6 @@ Although Braze can handle standard deep links (such as website URLs, Android URI
 
 For setup guidance, visit [Deep Linking to In-App Resources](https://developer.android.com/training/app-links/deep-linking).
 
+## Adding Braze push notification icons
+
+To add push icons to your project, create an Android Archive (AAR) plug-in or Android library that contains the icon image files. For steps and information, refer to Unity's documentation: [Android Library Projects and Android Archive plug-ins](https://docs.unity3d.com/Manual/AndroidAARPlugins.html).
\ No newline at end of file
diff --git a/_docs/_developer_guide/platform_integration_guides/web/analytics/setting_custom_attributes.md b/_docs/_developer_guide/platform_integration_guides/web/analytics/setting_custom_attributes.md
index 335f886c8e2..186753ba07b 100644
--- a/_docs/_developer_guide/platform_integration_guides/web/analytics/setting_custom_attributes.md
+++ b/_docs/_developer_guide/platform_integration_guides/web/analytics/setting_custom_attributes.md
@@ -139,7 +139,7 @@ To set up a subscription for your users (either email or push), call the functio
 | `braze.User.NotificationSubscriptionTypes.OPTED_IN` | Subscribed, and explicitly opted in |
 | `braze.User.NotificationSubscriptionTypes.SUBSCRIBED` | Subscribed, but not explicitly opted in |
 | `braze.User.NotificationSubscriptionTypes.UNSUBSCRIBED` | Unsubscribed and/or explicitly opted out |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 When a user is registered for push, the browser forces them to choose to allow or block notifications, and if they choose to allow push, they are set `OPTED_IN` by default. 
 
diff --git a/_docs/_developer_guide/platform_integration_guides/web/browser_extensions.md b/_docs/_developer_guide/platform_integration_guides/web/browser_extensions.md
index 41c38b31228..13575f01506 100644
--- a/_docs/_developer_guide/platform_integration_guides/web/browser_extensions.md
+++ b/_docs/_developer_guide/platform_integration_guides/web/browser_extensions.md
@@ -36,7 +36,7 @@ Braze can be included in the following areas of your extension:
 | Popup Page | The [Popup](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Popups) page is a dialog that can be shown to users when clicking on your extension's icon in the browser toolbar.| Analytics, in-app messages, and Content Cards |
 | Background Scripts | [Background Scripts](https://developer.chrome.com/extensions/background_pages) (Manifest v2 only) allow your extension to inspect and interact with user navigation or modify webpages (for example, how ad blockers detect and change content on pages). | Analytics, in-app messages, and Content Cards.<br><br>Background scripts aren't visible to users, so for messaging, you would need to communicate with browser tabs or your popup page when displaying messages. |
 | Options Pages | The [Options Page](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Options_pages) lets your users toggle settings within your extension. It's a standalone HTML page that opens a new tab. | Analytics, in-app messages, and Content Cards |
-{: .reset-td-br-1 .reset-td-br-2, .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2, .reset-td-br-3 role="presentation" }
 
 ## Permissions
 
diff --git a/_docs/_developer_guide/platform_integration_guides/web/content_cards/integration.md b/_docs/_developer_guide/platform_integration_guides/web/content_cards/integration.md
index c22adee048b..3db41e7a948 100644
--- a/_docs/_developer_guide/platform_integration_guides/web/content_cards/integration.md
+++ b/_docs/_developer_guide/platform_integration_guides/web/content_cards/integration.md
@@ -60,7 +60,7 @@ When using the `toggleContentCards(parentNode, filterFunction)` and `showContent
 |---|---|
 |`parentNode` | The HTML node to render the Content Cards into. If the parent node already has a Braze Content Cards view as a direct descendant, the existing Content Cards will be replaced. For example, you should pass in `document.querySelector(".my-container")`.|
 |`filterFunction` | A filter or sort function for cards displayed in this view. Invoked with the array of `Card` objects, sorted by `{pinned, date}`. Expected to return an array of sorted `Card` objects to render for this user. If omitted, all cards will be displayed. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 [See the SDK reference docs](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#togglecontentcards) for more information on Content Card toggling.
 
@@ -85,7 +85,7 @@ All Content Cards have these shared properties:
 | `updated` | The UNIX timestamp of when this card was last modified. |
 | `viewed` | This property reflects whether the user viewed the card or not.|
 | `isControl` | This property is `true` when a card is a "control" group within an A/B test.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Image only Content Card properties - ImageOnly
 
@@ -102,7 +102,7 @@ All Content Cards have these shared properties:
 | `imageUrl` | The URL of the card's image.|
 | `linkText` | The display text for the URL. |
 | `url` | The URL that will be opened after the card is clicked on. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Captioned image Content Card properties - CaptionedImage
 
@@ -120,7 +120,7 @@ All Content Cards have these shared properties:
 | `linkText` | The display text for the URL. |
 | `title` | The title text for this card. |
 | `url` | The URL that will be opened after the card is clicked on. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Classic Content Card properties - ClassicCard
 
@@ -139,7 +139,7 @@ The [ClassicCard](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.clas
 | `linkText` | The display text for the URL. |
 | `title` | The title text for this card. |
 | `url` | The URL that will be opened after the card is clicked on. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Control group 
 
@@ -161,7 +161,7 @@ To determine if a Content Card is in the Control group for an A/B test, check th
 |[`getCachedContentCards`](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#getcachedcontentcards)|Get all currently available cards from the last Content Cards refresh.|
 |[`subscribeToContentCardsUpdates`](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#subscribetocontentcardsupdates)| Subscribe to Content Cards updates. <br> The subscriber callback will be called whenever Content Cards are updated. | 
 |[`dismissCard`](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.card.html#dismisscard)|Dismiss the card programmatically (available in v2.4.1).|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 For more details, refer to the [SDK reference documentation](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html)
 
diff --git a/_docs/_developer_guide/platform_integration_guides/web/cookies_and_storage.md b/_docs/_developer_guide/platform_integration_guides/web/cookies_and_storage.md
index b0af5b7c788..bf8e7db83a3 100644
--- a/_docs/_developer_guide/platform_integration_guides/web/cookies_and_storage.md
+++ b/_docs/_developer_guide/platform_integration_guides/web/cookies_and_storage.md
@@ -48,7 +48,7 @@ To stop Braze tracking in general, or to clear all stored browser data, see the
 |`ab.storage.deviceId.[your-api-key]`|Randomly-generated string used to identify anonymous users, and to differentiate users' devices and enables device-based messaging.|~200 bytes|
 |`ab.optOut`|Used to store a user's opt-out preference when `disableSDK` is called|~40 bytes|
 |`ab._gd`|Temporarily created (and then deleted) to determine the root-level cookie domain, which allows the SDK to work properly across sub-domains.|n/a|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Device properties
 
diff --git a/_docs/_developer_guide/platform_integration_guides/web/in-app_messaging/troubleshooting.md b/_docs/_developer_guide/platform_integration_guides/web/in-app_messaging/troubleshooting.md
index 087974bfd90..d0f39b2b0dc 100644
--- a/_docs/_developer_guide/platform_integration_guides/web/in-app_messaging/troubleshooting.md
+++ b/_docs/_developer_guide/platform_integration_guides/web/in-app_messaging/troubleshooting.md
@@ -10,54 +10,4 @@ description: "This page includes troubleshooting steps to take for common issues
 
 # Troubleshooting
 
-> This article provides several Web SDK troubleshooting scenarios.
-
-## Impressions are lower than expected
-
-Triggers take time to sync to the device on session start; this can result in a race condition if users log an event or purchase right after starting a session. One potential workaround could be changing the campaign to trigger off of session start, then segmenting off the intended event or purchase. Note that this would deliver the in-app message on the next session start after the event has occurred.
-
-## Expected in-app message did not display
-
-Most in-app message issues can be broken down into two main categories: delivery and display. To troubleshoot why an expected in-app message did not display on your device, you should first ensure that the [in-app message was delivered to the device](#troubleshooting-in-app-message-delivery), then [troubleshoot message display](#troubleshooting-in-app-message-display).
-
-## In-app message delivery {#troubleshooting-in-app-message-delivery}
-
-The SDK requests in-app messages from Braze servers on session start. To check if in-app messages are being delivered to your device, you'll need to ensure that in-app messages are being both requested by the SDK and returned by Braze servers.
-
-### Check if messages are requested and returned
-
-1. Add yourself as a [test user]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#adding-test-users) on the dashboard.
-2. Set up an in-app message campaign targeted at your user.
-3. Ensure that a new session occurs in your application.
-4. Use the [event user logs]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab) to check that your device is requesting in-app messages on session start. Find the SDK Request associated with your test user's session start event.
-  - If your app was meant to request triggered in-app messages, you should see `trigger` in the **Requested Responses** field under **Response Data**.
-  - If your app was meant to request original in-app messages, you should see  `in_app` in the **Requested Responses** field under **Response Data**.
-5. Use the [event user logs]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab) to check if the correct in-app messages are being returned in the response data.<br>![]({% image_buster /assets/img_archive/event_user_log_iams.png %})
-
-### Troubleshoot messages not being requested
-
-If your in-app messages are not being requested, your app might not be tracking sessions correctly, as in-app messages are refreshed upon session start. Also, be sure that your app is actually starting a session based on your app's session timeout semantics:
-
-![The SDK request found in the event user logs displaying a successful session start event.]({% image_buster /assets/img_archive/event_user_log_session_start.png %})
-
-### Troubleshoot messages not being returned
-
-If your in-app messages are not being returned, you're likely experiencing a campaign targeting issue:
-
-- Your segment does not contain your user.
-  - Check your user's [**Engagement**]({{ site.baseurl }}/user_guide/engagement_tools/segments/using_user_search/#engagement-tab) tab to see if the correct segment appears under **Segments**.
-- Your user has previously received the in-app message and was not re-eligible to receive it again.
-  - Check the [campaign re-eligibility settings]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/) under the **Delivery** step of the **Campaign Composer** and make sure the re-eligibility settings align with your testing setup.
-- Your user hit the frequency cap for the campaign.
-  - Check the campaign [frequency cap settings]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping) and ensure they align with your testing setup.
-- If there was a control group on the campaign, your user may have fallen into the control group.
-  - You can check if this has happened by creating a segment with a received campaign variant filter, where the campaign variant is set to **Control**, and checking if your user fell into that segment.
-  - When creating campaigns for integration testing purposes, make sure to opt out of adding a control group.
-
-## In-app message display {#troubleshooting-in-app-message-display}
-
-If your app is successfully requesting and receiving in-app messages, but they are not being shown, some device-side logic may be preventing display:
-
-- Triggered in-app messages are rate-limited based on the [minimum time interval between triggers]({{site.baseurl}}/developer_guide/platform_integration_guides/web/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers), which defaults to 30 seconds.
-- If you have custom in-app message handling through `braze.subscribeToInAppMessage` or `appboy.subscribeToNewInAppMessages`, check that subscription to ensure it is not affecting in-app message display.
-
+{% multi_lang_include inapp_message_troubleshooting.md sdk="Web" %}
diff --git a/_docs/_developer_guide/platform_integration_guides/xamarin/content_cards.md b/_docs/_developer_guide/platform_integration_guides/xamarin/content_cards.md
index 91e2c242460..67f725f56cd 100644
--- a/_docs/_developer_guide/platform_integration_guides/xamarin/content_cards.md
+++ b/_docs/_developer_guide/platform_integration_guides/xamarin/content_cards.md
@@ -56,7 +56,7 @@ The Braze Xamarin SDK has three unique Content Cards card types that share a bas
 |`isControlCard`    | Whether this card is a control card. Control cards should not be displayed to the user.                                |
 |`extras`           | The map of key-value extras for this card.                                                                             |
 |`isTest`           | Whether this card is a test card.                                                                                      |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of the base card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/data-swift.struct) documentation.
 
@@ -68,7 +68,7 @@ Banner cards are clickable, full-sized images.
 |-------------------|-------------------------------------------------------------------------------------------------------------------|
 |`image`            | The URL of the card's image.                                                                                      |
 |`imageAspectRatio` | The aspect ratio of the card's image. It is meant to serve as a hint before image loading completes. Note that the property may not be supplied in certain circumstances. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of the banner card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-image-only-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/imageonly-swift.struct) documentation (now renamed to image only).
 
@@ -83,7 +83,7 @@ Captioned image cards are clickable, full-sized images with accompanying descrip
 |`title`            | The title text for the card.                                                                                      |
 |`cardDescription`  | The description text for the card.                                                                                |
 |`domain`           | (Optional) The link text for the property URL, for example, `"braze.com/resources/"`. It can be displayed on the card's UI to indicate the action/direction of clicking on the card. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of the captioned image card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-captioned-image-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/captionedimage-swift.struct) documentation.
 
@@ -97,7 +97,7 @@ Classic cards have a title, description, and an optional image on the left of th
 |`title`            | The title text for the card.                                                                                      |
 |`cardDescription`  | The description text for the card.                                                                                |
 |`domain`           | (Optional) The link text for the property URL, for example, `"braze.com/resources/"`. It can be displayed on the card's UI to indicate the action/direction of clicking on the card. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For a full reference of the classic (text announcement) Content Card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-text-announcement-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/classic-swift.struct) documentation. For a full reference of the classic image (short news) card, see the [Android](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.models.cards/-short-news-card/index.html) and [iOS](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/contentcard/classicimage-swift.struct) documentation.
 
diff --git a/_docs/_developer_guide/platform_wide/feature_flags/about.md b/_docs/_developer_guide/platform_wide/feature_flags/about.md
index 2f32a77e0ff..dfd5b23feb7 100644
--- a/_docs/_developer_guide/platform_wide/feature_flags/about.md
+++ b/_docs/_developer_guide/platform_wide/feature_flags/about.md
@@ -169,7 +169,7 @@ if (featureFlag?.enabled) {
 
 We'll set up our A/B test in a [Feature Flag Experiment]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/experiments/).
 
-Now, 50% of users will see the old experience, while the other 50% will see the new experience. We can then analyze the two variants to determine which checkout flow resulted in a higher conversion rate.
+Now, 50% of users will see the old experience, while the other 50% will see the new experience. We can then analyze the two variants to determine which checkout flow resulted in a higher conversion rate. {% multi_lang_include metrics.md metric='Conversion Rate' %}
 
 ![A feature flag experiment splitting traffic into two 50 percent groups.]({% image_buster /assets/img/feature_flags/feature-flag-use-case-campaign-experiment.png %})
 
@@ -196,7 +196,7 @@ The following table describes the limitations that apply at a feature flag level
 | [Active feature flags](#active-feature-flags)                                                                     | 10 per workspace | 110 per workspace |
 | [Active campaign experiments]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/experiments/)          | 1 per workspace  | 100 per workspace |
 | [Feature Flag Canvas steps]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/feature_flags/) | Unlimited        | Unlimited         |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Active feature flags
 
diff --git a/_docs/_developer_guide/platform_wide/feature_flags/create.md b/_docs/_developer_guide/platform_wide/feature_flags/create.md
index 44e65c8abc9..5594e22474c 100644
--- a/_docs/_developer_guide/platform_wide/feature_flags/create.md
+++ b/_docs/_developer_guide/platform_wide/feature_flags/create.md
@@ -31,7 +31,7 @@ To manage feature flags in the dashboard, you'll either need to be an Administra
 |-------------------------------------------------------------------------------|-------------------------------------------|
 | **Manage Feature Flags**                                                      | View, create, and edit feature flags.     |
 | **Access Campaigns, Canvases, Cards, Feature Flags, Segments, Media Library** | View the list of available feature flags. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Creating a feature flag
 
@@ -50,7 +50,7 @@ Under **Details**, enter a name, ID, and description for your feature flag.
 | Name         | A human-readable title for your marketers and administrators.                                                                                                                                                       |
 | ID           | The unique ID you'll use in your code to check if this feature is [enabled for a user](#enabled). This ID cannot be changed later, so review our [ID naming best practices](#naming-conventions) before continuing. |
 | Description  | An optional description that gives some context about your feature flag.                                                                                                                                            |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Step 3: Create custom properties
 
@@ -860,7 +860,7 @@ Replace the following:
 | `BEHAVIOR`  | The behavior of the feature. In your code, be sure the behavior is disabled by default and avoid using phrases like `disabled` in the feature flag name. |
 | `PRODUCT`   | The product the feature belongs to.                                                                                       |
 | `FEATURE`    | The name of the feature.                                                                                                  |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Here's an example feature flag where `show` is the behavior, `animation_profile` is the product, and `driver` is the feature:
 
diff --git a/_docs/_developer_guide/platform_wide/feature_flags/faq.md b/_docs/_developer_guide/platform_wide/feature_flags/faq.md
index 2217f20559a..4fece1e12e0 100644
--- a/_docs/_developer_guide/platform_wide/feature_flags/faq.md
+++ b/_docs/_developer_guide/platform_wide/feature_flags/faq.md
@@ -103,6 +103,10 @@ Feature flags may be refreshed mid-session. There are scenarios where you may wa
 
 To control this, [listen for updates]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/create/#updates) to feature flags and determine whether to re-render your app based on which feature flags have changed. 
 
+### Why aren't users in my Global Control Group receiving feature flags experiments?
+
+You can't enable feature flags for users in your [Global Control Group]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/). This means users in your Global Control Group also can't be part of Feature Flag experiments.
+
 ## Additional questions?
 
 Have questions or feedback? Email our team: [feature-flags-feedback@braze.com](mailto:feature-flags-feedback@braze.com).
diff --git a/_docs/_developer_guide/platform_wide/getting_started/analytics_overview.md b/_docs/_developer_guide/platform_wide/getting_started/analytics_overview.md
index a75e748f670..da32dc90dd1 100644
--- a/_docs/_developer_guide/platform_wide/getting_started/analytics_overview.md
+++ b/_docs/_developer_guide/platform_wide/getting_started/analytics_overview.md
@@ -36,7 +36,7 @@ Custom events are actions taken by your users; they're best suited for tracking
 | Check if the custom event occurred **more than X (Max = 50) number of times** | **MORE THAN** | in the past **Y Days (Y = 1,3,7,14,21,30)** |
 | Check if the custom event occurred **less than X (Max = 50) number of times** | **LESS THAN** | in the past **Y Days (Y = 1,3,7,14,21,30)** |
 | Check if the custom event occurred **exactly X (Max = 50) number of times** | **EXACTLY** | in the past **Y Days (Y = 1,3,7,14,21,30)** |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Braze notes the number of times these events have occurred as well as the last time they were performed by each user for segmentation. On the **Custom Events** analytics page, you can view in aggregate how often each custom event occurs, as well as by segment over time for more detailed analysis. This is particularly useful to view how your campaigns have affected custom event activity by looking at the gray lines Braze overlays on the time-series to indicate the last time a campaign was sent.
 
@@ -95,7 +95,7 @@ The following table describes available segmentation options for string attribut
 | Check if the string attribute **does not match** an inputted string| **DOES NOT EQUAL** | **STRING** |
 | Check if the string attribute **exists** on a user's profile | **IS BLANK** | **N/A** |
 | Check if the string attribute **does not exist** on a user's profile | **IS NOT BLANK** | **N/A** |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert important %}
 When segmenting using the **DOES NOT MATCH REGEX** filter, it is required that there already exists a custom attribute with a value assigned in that user profile. Braze suggests using "OR" logic to check if a custom attribute is blank in order to properly target users.
@@ -138,7 +138,7 @@ The following table describes available segmentation options for array attribute
 | Check if the array attribute **contains a value which partially matches** an inputted value **OR** regular expression | **MATCHES REGEX** | **STRING** **OR** **REGULAR EXPRESSION** |
 | Check if the array attribute **has any value** | **HAS A VALUE** | **N/A** |
 | Check if the array attribute **is empty** | **IS EMPTY** | **N/A** |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 >  We use [Perl compatible regular expressions (PCRE)](http://www.regextester.com/pregsyntax.html).
 
@@ -161,7 +161,7 @@ The following table describes available segmentation options for time attributes
 | Check if the time attribute is **less than X number** of **days in the future** | **IN LESS THAN** | **NUMBER OF DAYS IN FUTURE**  |
 | Check if the time attribute **exists** on a user's profile | **BLANK** | **N/A** |
 | Check if the time attribute **does not exist** on a user's profile | **IS NOT BLANK** | **N/A** |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 #### Numbers {#integers}
 Numeric attributes have a wide variety of use cases. Incrementing number custom attributes are useful for storing the number of times a given action or event has occurred. Standard numbers have all sorts of usages, such as recording shoe size, waist size, or the number of times a user has viewed a certain product feature or category.
@@ -178,7 +178,7 @@ The following table describes available segmentation options for numeric attribu
 | Check if the numeric attribute **does not equal** a **number**| **DOES NOT EQUAL** | **NUMBER** |
 | Check if the numeric attribute **exists** on a user's profile | **EXISTS** | **N/A** |
 | Check if the numeric attribute **does not exist** on a user's profile | **DOES NOT EXIST** | **N/A** |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 #### Booleans (true/false)
 Boolean attributes are useful for storing subscription statuses and other simple binary data about your users. The input options that we provide allow you to find users that have explicitly had a variable set to a boolean in addition to those that don't have any record of that attribute recorded yet.
@@ -190,7 +190,7 @@ The following table describes available segmentation options for boolean attribu
 | Check if the boolean value **is** | **IS**  | **TRUE**, **FALSE**, **TRUE OR NOT SET**, or **FALSE OR NOT SET** |
 | Check if the boolean value **exists** on a user's profile | **EXISTS**  | **N/A** |
 | Check if the boolean value **does not exist** on a user's profile | **DOES NOT EXIST**  | **N/A** |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Purchase events / revenue tracking
 
@@ -210,7 +210,7 @@ The following table describes available segmentation options for purchase events
 | Check if the purchase occurred **more than X (Max = 50) number of times** | **MORE THAN** | in the past **Y Days (Y = 1,3,7,14,21,30)** |
 | Check if the purchase occurred **less than X (Max = 50) number of times** | **LESS THAN** | in the past **Y Days (Y = 1,3,7,14,21,30)** |
 | Check if the purchase occurred **exactly X (Max = 50) number of times** | **EXACTLY** | in the past **Y Days (Y = 1,3,7,14,21,30)** |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 >  If you would like to segment on the number of times a specific purchase has occurred, you should also record that purchase individually as an [incrementing custom attribute](#integers).
 
diff --git a/_docs/_developer_guide/platform_wide/getting_started/integration_overview.md b/_docs/_developer_guide/platform_wide/getting_started/integration_overview.md
index 727b1988b6d..0230bec8c00 100644
--- a/_docs/_developer_guide/platform_wide/getting_started/integration_overview.md
+++ b/_docs/_developer_guide/platform_wide/getting_started/integration_overview.md
@@ -181,7 +181,7 @@ Make sure your production and testing environments are set up before beginning Q
 |                           | Test that Content Cards are delivered and metrics logged. |
 |                           | Facilitate Connected Content (for example, AccuWeather). |
 |                           | Confirm all message channel integrations are working together properly. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 
 
diff --git a/_docs/_developer_guide/platform_wide/getting_started/platform_overview.md b/_docs/_developer_guide/platform_wide/getting_started/platform_overview.md
index f311ac7c523..198d8430b90 100644
--- a/_docs/_developer_guide/platform_wide/getting_started/platform_overview.md
+++ b/_docs/_developer_guide/platform_wide/getting_started/platform_overview.md
@@ -92,7 +92,7 @@ After you have defined a segment, Braze messaging tools allow you to engage with
 | [Web push]({{site.baseurl}}/user_guide/message_building_by_channel/push/web) | Send web browser notifications, even if your users aren't currently active on your site. |
 | [Webhooks]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/understanding_webhooks/) | Use webhooks to trigger non-app actions, providing other systems and applications with real-time data. |
 | [WhatsApp]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/)* | Directly connect with your users and customers by leveraging the popular peer-to-peer messaging platform: WhatsApp. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 <sup>**Available as an add-on feature.*</sup>
 
@@ -156,6 +156,6 @@ As a technical resource, you'll be involved in a lot of the nuts and bolts of Br
 | [SDK Changelogs]({{site.baseurl}}/developer_guide/platform_integration_guides/sdk_changelogs) | Braze has predictable monthly releases, in addition to releases for any critical issues and major OS updates. |
 | [Braze API Postman Collection](https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest) | Download our Postman collection here.  |
 | [Braze System Status Monitor](https://braze.statuspage.io/) | Our status page is updated whenever there are incidents or outages. Go to this page to subscribe to alerts. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 
diff --git a/_docs/_developer_guide/platform_wide/sdk_authentication.md b/_docs/_developer_guide/platform_wide/sdk_authentication.md
index b3b514bf800..0583fe0dc10 100644
--- a/_docs/_developer_guide/platform_wide/sdk_authentication.md
+++ b/_docs/_developer_guide/platform_wide/sdk_authentication.md
@@ -59,7 +59,7 @@ When generating the JWT, the following fields are expected:
 | `alg` | Yes  | The supported algorithm is `RS256`. |
 | `typ` | Yes  | The type should equal `JWT`.        |
 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 **JWT Payload**
 
@@ -67,10 +67,8 @@ When generating the JWT, the following fields are expected:
 | ----- | -------- | -------------------------------------------------------------------------------------- |
 | `sub` | Yes  | The "subject" should equal the User ID you supply Braze SDK when calling `changeUser`  |
 | `exp` | Yes | The "expiration" of when you want this token to expire.                                |
-| `aud` | No       | The "audience" claim is optional, and if set should equal `braze`                      |
-| `iss` | No       | The "issuer" claim is optional, and if set should equal your SDK API Key.              |
 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### JWT libraries
 
@@ -389,7 +387,7 @@ In the dashboard **Manage Settings** page, each app has three SDK Authentication
 | **Disabled** | Braze will not verify the JWT supplied for a user. (Default Setting)|
 | **Optional** | Braze will verify requests for logged-in users, but will not reject invalid requests. |
 | **Required** | Braze will verify requests for logged-in users and will reject invalid JWTs.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![]({% image_buster /assets/img/sdk-auth-settings.png %})
 
@@ -419,7 +417,7 @@ Data is available in real-time, and you can hover over points in the chart to se
 | 26 | `MISSING_TOKEN` | No token was provided in the request.|
 | 27 | `NO_MATCHING_PUBLIC_KEYS` | No public keys matched the provided token.|
 | 28 | `PAYLOAD_USER_ID_MISMATCH` | Not all user ids in the request payload match as is required.|
-{: .reset-td-br-1 .reset-td-br-2, .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2, .reset-td-br-3 role="presentation" }
 
 ## Frequently asked questions {#faq}
 
diff --git a/_docs/_help/accessibility.md b/_docs/_help/accessibility.md
index 8e95fb41661..e1b7cb5af3c 100644
--- a/_docs/_help/accessibility.md
+++ b/_docs/_help/accessibility.md
@@ -114,7 +114,7 @@ For example, consider how you might write a link to view a weather report.
 | Bad  | Better | Best |
 | --- | --- | --- | 
 | Click here | Click here to access today's weather | Today's weather |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 As with all content, keep it straightforward with as few extra words as possible.
 
diff --git a/_docs/_help/help_articles/api/attribute_name_id_across_sources.md b/_docs/_help/help_articles/api/attribute_name_id_across_sources.md
index 3b06ced3fec..b5526129778 100644
--- a/_docs/_help/help_articles/api/attribute_name_id_across_sources.md
+++ b/_docs/_help/help_articles/api/attribute_name_id_across_sources.md
@@ -34,7 +34,7 @@ Campaign and Canvas attributes are tied to [message engagement events]({{site.ba
 | Campaign ID | {% raw %}`{{campaign.${api_id}}}`{% endraw %} | N/A (used as an input for the API call itself) | campaign_id |
 | Variant name | {% raw %}`{{campaign.${message_name}}}`{% endraw %} | `messages.message_variation_id.name` | N/A (map variant name to variant ID using the Export campaign details endpoint) |
 | Variant ID | {% raw %}`{{campaign.${message_api_id}}}`{% endraw %} | `messages.message_variation_id` | `message_variation_api_id` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Canvas attributes
 
@@ -48,4 +48,4 @@ Campaign and Canvas attributes are tied to [message engagement events]({{site.ba
 | Step ID | {% raw %}`{{campaign.${api_id}}}`{% endraw %} | `steps.id` | `canvas_step_id` |
 | Message channel | N/A | `steps.messages.message_variation_id.channel` | N/A (inherent from event type, such as push send or email open) |
 | Message ID | {% raw %}`{{campaign.${message_api_id}}}`{% endraw %} | `steps.message.message_variation_id` | `canvas_step_message_variation_api_id` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
\ No newline at end of file
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
\ No newline at end of file
diff --git a/_docs/_help/help_articles/api/webhook_connected_content_errors.md b/_docs/_help/help_articles/api/webhook_connected_content_errors.md
index 84d29c7fd98..fae82e4f93b 100644
--- a/_docs/_help/help_articles/api/webhook_connected_content_errors.md
+++ b/_docs/_help/help_articles/api/webhook_connected_content_errors.md
@@ -119,13 +119,14 @@ table td {
 
 `5XX` errors indicate that there's an issue with the endpoint. These errors are typically caused by server-side issues.
 
-| Error code                    | What it means                                                                                      |
-|-------------------------------|----------------------------------------------------------------------------------------------------|
-| **500 Internal Server Error** | The endpoint encountered an unexpected condition that prevented it from completing the request.    |
-| **502 Bad Gateway**           | The endpoint received an invalid response from the upstream server.                                |
-| **503 Service Unavailable**   | The endpoint is currently unable to handle the request due to a temporary overload or maintenance. |
-| **504 Gateway Timeout**       | The endpoint didn't receive a timely response from the upstream server.                            |
-{: .reset-td-br-1 .reset-td-br-2}
+| Error code                    | What it means                                                                                                                                         |
+|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **500 Internal Server Error** | The endpoint encountered an unexpected condition that prevented it from completing the request.                                                       |
+| **502 Bad Gateway**           | The endpoint received an invalid response from the upstream server.                                                                                   |
+| **503 Service Unavailable**   | The endpoint is currently unable to handle the request due to a temporary overload or maintenance.                                                    |
+| **504 Gateway Timeout**       | The endpoint didn't receive a timely response from the upstream server.                                                                               |
+| **599 Connection Error**      | Braze experienced a network connect timeout error while trying to establish a connection to the endpoint, meaning the endpoint may be unstable or down. |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Resolving 5XX errors
 
diff --git a/_docs/_help/help_articles/email/email_bounces.md b/_docs/_help/help_articles/email/email_bounces.md
index 676747eda5f..bcfbe00220c 100644
--- a/_docs/_help/help_articles/email/email_bounces.md
+++ b/_docs/_help/help_articles/email/email_bounces.md
@@ -13,14 +13,13 @@ What do you do when a message from your email campaign bounces back from your us
 
 ## Hard bounces
 
-When an email message hard bounces, the email address is either invalid or does not exist. When this occurs, Braze marks the email address as invalid but does not update the user's [subscription status][1]. At this point, Braze will not attempt to send messages to these email addresses marked as invalid.
+{% multi_lang_include metrics.md metric='Hard Bounce' %}
+
+For more information, see [Hard bounce]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics/#hard-bounce).
 
 ## Soft bounces
 
-Soft bounces occur when your recipient's email address is valid or when the email message reaches the recipient's email server, but the message was rejected for a temporary issue. These temporary issues may occur when:
-- Your recipient's inbox is full
-- The message is too large for your recipient's inbox  
-- An email server was down
+{% multi_lang_include metrics.md metric='Soft Bounce' %} 
 
 If an email receives a soft bounce, we will usually retry within 72 hours, but the number of retry attempts varies from receiver to receiver.
 
diff --git a/_docs/_help/help_articles/email/universal_links.md b/_docs/_help/help_articles/email/universal_links.md
index e6722f3bcc7..b79fd993fb7 100644
--- a/_docs/_help/help_articles/email/universal_links.md
+++ b/_docs/_help/help_articles/email/universal_links.md
@@ -27,7 +27,7 @@ This table outlines the key differences between universal links and traditional
 | Purpose                | Seamlessly link web and app content on iOS and Android devices | Link to specific app content |
 | Function               | Directs to web pages or app content based on context           | Opens specific app screens   |
 | App Installation       | Opens app if the app is installed, otherwise opens web content | Requires app to be installed |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_help/help_articles/push/resetting_push_permissions.md b/_docs/_help/help_articles/push/resetting_push_permissions.md
index c0503662773..2284f5b208a 100644
--- a/_docs/_help/help_articles/push/resetting_push_permissions.md
+++ b/_docs/_help/help_articles/push/resetting_push_permissions.md
@@ -26,7 +26,7 @@ table {
 | ------- | ------------------------------------------------------------------- |
 | Mac      | `Fn` + `F12`<br>`Ctrl` + `Shift` + `I` |
 | Windows | `F12`<br>`Ctrl` + `Shift` + `I` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {:start="4"}
 4. In DevTools, navigate to the **Application** tab.
diff --git a/_docs/_help/release_notes.md b/_docs/_help/release_notes.md
index 961f7def2cc..b6b076c96fc 100644
--- a/_docs/_help/release_notes.md
+++ b/_docs/_help/release_notes.md
@@ -54,6 +54,98 @@ guide_featured_list:
 > <br>
 > For more information on any of the updates listed in this section, reach out to your account manager or [open a support ticket]({{site.baseurl}}/help/support/). You can also check out [our SDK Changelogs]({{site.baseurl}}/developer_guide/platform_integration_guides/sdk_changelogs/) to see more information on our monthly SDK releases, updates, and improvements.
 
+## October 15, 2024 release
+
+### Data flexibility
+
+#### Campaigns and Canvases
+
+While creating campaigns and Canvases, you can calculate the exact number of reachable users in your target audience instead of the default estimation by selecting [Calculate exact statistics]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/#statistics-for-segment-size).
+
+#### API Android objects
+
+The [`android_priority` parameter]({{site.baseurl}}/api/objects_filters/messaging/android_object/#additional-parameter-details) will accept values either “normal” or “high” to specify the FCM sender priority. By default, notification messages are sent with high priority, and data messages are sent with normal priority.
+
+For more information on how different values impact delivery, see [Android message priority](https://firebase.google.com/docs/cloud-messaging/android/message-priority/).
+
+#### SDK
+
+Use the [Braze SDK's built-in debugger]({{site.baseurl}}/developer_guide/platform_wide/debugging/) to troubleshoot issues for your SDK-powered channels without needing to enable verbose logging in your app.
+
+#### Live Activities
+
+We updated the [frequently asked questions]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/faq/) for Swift Live Activities with a few new questions and answers.
+
+#### Custom events
+
+[Event property objects]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-properties) that contain array or object values can now have an event property payload of up to 100&nbsp;KB.
+
+#### Random bucket numbers
+
+Use [random audience re-entry with random bucket numbers]({{site.baseurl}}/user_guide/engagement_tools/testing/random_bucket_numbers/#random-audience-re-entry-using-random-bucket-numbers) for A/B testing or targeting specific user groups in your campaigns.
+
+#### Segment Extensions
+
+You can [refresh segment extensions on a recurring schedule]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/#setting-up-a-recurring-refresh) by selecting the frequency at which the extensions will refresh (daily, weekly, or monthly) and the specific time the refresh will occur.
+
+### Robust channels
+
+#### SMS
+
+We added [Adding UTM parameters]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#using-link-shortening) to demonstrate how you can use UTM parameters in an SMS message, so you track the performance of campaigns in third-party analytics tools, such as Google Analytics.
+
+#### Landing pages
+
+[Connect your own domain]({{site.baseurl}}/user_guide/engagement_tools/landing_pages/connect_domain/) to your Braze workspace to customize your landing page URLs with your brand.
+
+#### LINE and Braze
+
+{% multi_lang_include release_type.md release="Beta" %}
+
+We added new documentation:
+
+- [LINE message types]({{site.baseurl}}/line/create/message_types/) covers the LINE message types you can compose, including aspects and limitations, and is part of the LINE beta collection.
+- [User account linking]({{site.baseurl}}/line/line_setup/#user-account-linking) allows users to link their LINE account to your app’s user account. You can then use Liquid in Braze, such as {% raw %}`{{line_id}}`{% endraw %}, to create a personalized URL for the user that passes the user's LINE ID back to your website or app, which can then be associated with a known user.
+
+#### WhatsApp and Braze
+
+[WhatsApp Business Accounts (WABA)]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/#step-2-whatsapp-setup) can now be shared with multiple Business Solution Providers.
+
+### New Braze partnerships
+
+#### Future Anthem - Dynamic Content
+
+The Braze and [Future Anthem]({{site.baseurl}}/partners/message_personalization/dynamic_content/future_anthem/) partnership leverages Amplifier AI to deliver content personalization, real-time experiences, and dynamic audiences. Amplifier AI works across sports, casinos, and lottery, allowing you to enhance Braze player profiles with industry-specific player attributes, such as a favorite game, engagement score, expected next bet, and more.
+
+### Settings
+
+#### Indentifier field-level encryption
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+Using [identifier field-level encryption]({{site.baseurl}}/user_guide/data_and_analytics/field_level_encryption/), you can seamlessly encrypt email addresses with AWS Key Management Service (KMS) to minimize personally identifiable information (PII) shared in Braze. Encryption replaces sensitive data with ciphertext, which is unreadable encrypted information.
+
+### 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.
+
+- [Swift SDK 10.3.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#1110)
+- [Swift SDK 11.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#1110)
+    - Adds support for [Swift 6 strict concurrency checking](https://developer.apple.com/documentation/swift/adoptingswift6)
+        - Relevant public Braze classes and data types now conform to the `Sendable` protocol and can be safely used across concurrency contexts.
+        - Main thread-only APIs are now marked with the `@MainActor` attribute.
+        - We recommend using Xcode 16.0 or later to take advantage of these features while minimizing the number of warnings generated by the compiler. Previous versions of Xcode may still be used, but some features may generate warnings.
+    - When integrating push notification support manually, you may need to update the `UNUserNotificationCenterDelegate` conformance to use the `@preconcurrency` attribute to prevent warnings.
+        - Applying the `@preconcurrency` attribute on protocol conformance is only available in Xcode 16.0 or later. Reference our sample integration code [here](https://github.com/braze-inc/braze-swift-sdk/tree/main/Examples/Swift/Sources/PushNotifications-Manual).
+- [React Native SDK 13.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#1300)
+    - Updates the native Android version bindings from [Braze Android SDK 31.1.0 to 32.1.0](https://github.com/braze-inc/braze-android-sdk/compare/v31.1.0...v32.1.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed).
+    - Updates the native iOS version bindings from [Braze Swift SDK 10.3.0 to 11.0.0](https://github.com/braze-inc/braze-swift-sdk/compare/10.3.0...11.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed).
+- [Flutter SDK 11.1.0](https://pub.dev/packages/braze_plugin/changelog#1110)
+- [Swift SDK 11.1.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#1110)
+- [Android SDK 33.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#3300)
+    - Updated Kotlin from 1.8 to Kotlin 2.0.
+- [Web SDK 5.5.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#550)
+
 ## September 17, 2024 release
 
 ### Data flexibility
@@ -748,97 +840,3 @@ The following SDK updates have been released. Breaking updates are listed below;
   - Updated the minimum iOS version to 12.0.
   - Updated the iOS bindings to use Braze Swift SDK 8.1.0.
   - Updated the Android bindings to use Braze Android SDK 30.1.1.
-
-## March 5, 2024 release
-
-### Google EU User Consent Policy
-
-Google is updating their [EU User Consent Policy](https://www.google.com/about/company/user-consent-policy/) in response to changes to the [Digital Markets Act (DMA)](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html), which is in effect as of March 6, 2024. This new change requires advertisers to disclose certain information to their EEA and UK end users, as well as obtain necessary consents from them. As part of this upcoming change, you can [collect both consent signals in Braze as custom attributes]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users). Braze will sync the data from these custom attributes to the appropriate consent fields in Google.
-
-### Data flexibility
-
-#### Merge duplicate users
-
-{% multi_lang_include release_type.md release="Early access" %}
-
-In the Braze dashboard, you can now [search for and merge duplicate users]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users) to maximize the effectiveness of your campaigns and Canvases. You can individually merge user profiles or perform a bulk merge, which merges all profiles with matching identifiers into the most recently updated user profile.
-
-#### Search for archived content
-
-In the Braze dashboard, you can now include [archived content in your search results]({{site.baseurl}}/user_guide/administrative/access_braze/global_search/#filter-for-archived-content) by selecting **Show Archived Content**.
-
-#### Message archiving support for AWS S3 and Google Cloud Storage
-
-You can use [message archiving]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/) to save a copy of your messages sent to users for archival or compliance purposes to your AWS S3 bucket, Azure Blob Storage container or Google Cloud Storage bucket.
-
-#### SQL table reference
-
-Visit the [SQL table reference]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/sql_segments_tables/) to see the tables and columns available to be queried in the Query Builder or when generating SQL Segment Extensions.
-
-### Unlocking creativity
-
-#### Tone control for AI copywriting
-
-You can now choose a [message tone]({{site.baseurl}}/user_guide/brazeai/generative_ai/ai_copywriting/#steps) to determine the style of the copy generated with the AI copywriting assistant.
-
-### Robust channels
-
-#### Card creation
-
-You can choose when Braze evaluates audience eligibility and personalization for new Content Card campaigns and Canvas steps by specifying when the card is [created]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/). 
-
-#### Preview user paths
-
-{% multi_lang_include release_type.md release="General availability" %}
-
-Experience the Canvas journey you’ve created for your users, including previewing the timing and messages they will receive. These [test runs]({{site.baseurl}}/preview_user_paths/) act as quality assurance that your messages are sent to the right audience, all before sending the Canvas.
-
-#### Quick push campaigns
-
-{% multi_lang_include release_type.md release="General availability" %}
-
-When creating a push campaign in Braze, you can select multiple platforms and devices to craft one message for all platforms in a single editing experience called [quick push]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/quick_push/). This feature is only available for campaigns.
-
-#### Custom list-unsubscribe header
-
-{% multi_lang_include release_type.md release="General availability" %}
-
-Adding a [custom list-unsubscribe header]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#custom-list-unsubscribe-header) to your email messaging allows your recipients to opt-out. This way, you can add your own configured one-click unsubscribe endpoint and an optional “mailto:”. Braze requires an input for URL to support a custom list-unsubscribe header because the one-click unsubscribe HTTP is a requirement from Yahoo and Gmail for bulk senders.
-
-#### Multiple pages for in-app messages
-
-{% multi_lang_include release_type.md release="Early access" %}
-
-[Adding pages to your in-app message]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/#multi-page) lets you guide users through a sequential flow, like an onboarding flow or welcome journey. You can manage pages from the **Pages** section of the **Build** tab.
-
-#### Randomize paths for an experiment path
-
-To always [randomize path assignment]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step) for an Experiment Path step, select **Randomized Paths in Experiment Paths** in the step. This option is not available when using either Winning or Personalized Paths.
-
-#### Email capture form
-
-[Email capture messages]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form/) allow you to easily prompt users of your site to submit their email address, after which it will be available in their user profile for use in all your messaging campaigns.
-
-### 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.
-
-- [AppboyKit iOS SDK 4.7.0](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.7.0)
-    - This will be the final release for the Objective-C SDK before end-of-life on March 1, 2024 (in favor of using the [Swift SDK](https://github.com/braze-inc/braze-swift-sdk/)).
-    - Updates the minimum required version of SDWebImage from 5.8.2 to 5.18.7. This version includes the privacy manifest for SDWebImage, which appears on the [privacy-impacting SDKs list](https://developer.apple.com/support/third-party-SDK-requirements/).
-- [Flutter SDK 8.1.0](https://pub.dev/packages/braze_plugin/changelog)
-- [Unity 5.2.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
-- [React Native SDK 8.4.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.4.0/CHANGELOG.md)
-- [Xamarin SDK Version 4.0.2](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
-- [Swift SDK 7.7.0-8.0.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#801)
-- [Android SDK 30.1.0-30.2.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
-- [Web SDK 5.1.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
-- [Cordova SDK 8.0.0-Cordova SDK 8.1.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
-    - Updated the native Android bridge [from Braze Android SDK 27.0.1 to 30.0.0](https://github.com/braze-inc/braze-android-sdk/compare/v27.0.0...v30.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed).
-    - Updated the native iOS bridge [from Braze Swift SDK 6.6.0 to 7.6.0](https://github.com/braze-inc/braze-swift-sdk/compare/6.6.0...7.6.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed).
-    - Renamed the `Banner` Content Card type to `ImageOnly`:
-        - `ContentCardTypes.BANNER` to `ContentCardTypes.IMAGE_ONLY`
-        - On Android, if the XML files in your project contain the word banner for Content Cards, it should be replaced with `image_only`.
-    - `BrazePlugin.getFeatureFlag(id)` will now return `null` if the feature flag does not exist.
-    - `BrazePlugin.subscribeToFeatureFlagsUpdates(function)` will only trigger when a refresh request completes with success or failure, and upon initial subscription if there was previously cached data from the current session.
-    - Removed the deprecated method `registerAppboyPushMessages`. Use `setRegisteredPushToken` instead.
diff --git a/_docs/_help/release_notes/2019/july.md b/_docs/_help/release_notes/2019/july.md
index a5cfe48bc8d..136e8b7d0b6 100644
--- a/_docs/_help/release_notes/2019/july.md
+++ b/_docs/_help/release_notes/2019/july.md
@@ -16,11 +16,11 @@ Braze had two (you read that right - **two**) product release cycles this month!
 
 [Single sign-on]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/) (SSO) provides companies a secure and centralized way of controlling access to the Braze dashboard. In short, a single set of credentials can be use to access different applications, including Braze.
 
-In addition to [Google Sign-In using OAuth 2.0 support](https://developers.google.com/identity/protocols/OAuth2), companies would like SSO with Security Assertion Markup Language (SAML) support. This enables them to seamlessly integrate with large identity providers (IdPs), including [Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/) and [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/), which support the latest industry standards (SAML 2.0).
+In addition to [Google Sign-In using OAuth 2.0 support](https://developers.google.com/identity/protocols/OAuth2), companies would like SSO with Security Assertion Markup Language (SAML) support. This enables them to seamlessly integrate with large identity providers (IdPs), including [Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/entra/) and [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/), which support the latest industry standards (SAML 2.0).
 
 Braze supports:
 - [OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/)
-- [Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/)
+- [Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/entra/)
 - [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/)
 
 ## Adjust event API key shows
diff --git a/_docs/_help/release_notes/2022/5_3_22.md b/_docs/_help/release_notes/2022/5_3_22.md
index 5be2b2e00db..84556a25645 100644
--- a/_docs/_help/release_notes/2022/5_3_22.md
+++ b/_docs/_help/release_notes/2022/5_3_22.md
@@ -31,7 +31,7 @@ As of April 2022, Android developers must complete Google Play's [Data safety fo
 
 ## RelayState SAML SSO
 
-Initial single sign-on set-up instructions have been updated to recommend use of a `RelayState` API key. For more information, refer to [SAML SSO setup]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/) and corresponding [OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/), [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/), and [Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/) articles. 
+Initial single sign-on set-up instructions have been updated to recommend use of a `RelayState` API key. For more information, refer to [SAML SSO setup]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/) and corresponding [OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/), [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/), and [Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/entra/) articles. 
 
 ## Talon.One integration updates
 
diff --git a/_docs/_help/release_notes/2024.md b/_docs/_help/release_notes/2024.md
index 97d07641cb0..a53a2322241 100644
--- a/_docs/_help/release_notes/2024.md
+++ b/_docs/_help/release_notes/2024.md
@@ -40,4 +40,7 @@ guide_menu_list:
   - name: September 17, 2024
     link: /docs/help/release_notes/2024/9_17_24/
     image: /assets/img/braze_icons/backpack.svg
+  - name: October 15, 2024
+    link: /docs/help/release_notes/2024/10_15_24/
+    image: /assets/img/braze_icons/magic-wand-02.svg
 ---
diff --git a/_docs/_help/release_notes/2024/10_15_24.md b/_docs/_help/release_notes/2024/10_15_24.md
new file mode 100644
index 00000000000..561a4574518
--- /dev/null
+++ b/_docs/_help/release_notes/2024/10_15_24.md
@@ -0,0 +1,98 @@
+---
+nav_title: October 15, 2024
+description: "This article contains release notes for October 15, 2024."
+page_order: 2
+page_type: reference
+---
+ 
+# October 15, 2024 release
+
+## Data flexibility
+
+### Campaigns and Canvases
+
+While creating campaigns and Canvases, you can calculate the exact number of reachable users in your target audience instead of the default estimation by selecting [Calculate exact statistics]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/#statistics-for-segment-size).
+
+### API Android objects
+
+The [`android_priority` parameter]({{site.baseurl}}/api/objects_filters/messaging/android_object/#additional-parameter-details) will accept values either “normal” or “high” to specify the FCM sender priority. By default, notification messages are sent with high priority, and data messages are sent with normal priority.
+
+For more information on how different values impact delivery, see [Android message priority](https://firebase.google.com/docs/cloud-messaging/android/message-priority/).
+
+### SDK
+
+Use the [Braze SDK's built-in debugger]({{site.baseurl}}/developer_guide/platform_wide/debugging/) to troubleshoot issues for your SDK-powered channels without needing to enable verbose logging in your app.
+
+### Live Activities
+
+We updated the [frequently asked questions]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/faq/) for Swift Live Activities with a few new questions and answers.
+
+### Custom events
+
+[Event property objects]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-properties) that contain array or object values can now have an event property payload of up to 100&nbsp;KB.
+
+### Random bucket numbers
+
+Use [random audience re-entry with random bucket numbers]({{site.baseurl}}/user_guide/engagement_tools/testing/random_bucket_numbers/#random-audience-re-entry-using-random-bucket-numbers) for A/B testing or targeting specific user groups in your campaigns.
+
+### Segment Extensions
+
+You can [refresh segment extensions on a recurring schedule]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/#setting-up-a-recurring-refresh) by selecting the frequency at which the extensions will refresh (daily, weekly, or monthly) and the specific time the refresh will occur.
+
+## Robust channels
+
+### SMS
+
+We added [Adding UTM parameters]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#using-link-shortening) to demonstrate how you can use UTM parameters in an SMS message, so you track the performance of campaigns in third-party analytics tools, such as Google Analytics.
+
+### Landing pages
+
+[Connect your own domain]({{site.baseurl}}/user_guide/engagement_tools/landing_pages/connect_domain/) to your Braze workspace to customize your landing page URLs with your brand.
+
+### LINE and Braze
+
+{% multi_lang_include release_type.md release="Beta" %}
+
+We added new documentation:
+
+- [LINE message types]({{site.baseurl}}/line/create/message_types/) covers the LINE message types you can compose, including aspects and limitations, and is part of the LINE beta collection.
+- [User account linking]({{site.baseurl}}/line/line_setup/#user-account-linking) allows users to link their LINE account to your app’s user account. You can then use Liquid in Braze, such as {% raw %}`{{line_id}}`{% endraw %}, to create a personalized URL for the user that passes the user's LINE ID back to your website or app, which can then be associated with a known user.
+
+### WhatsApp and Braze
+
+[WhatsApp Business Accounts (WABA)]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/#step-2-whatsapp-setup) can now be shared with multiple Business Solution Providers.
+
+## New Braze partnerships
+
+### Future Anthem - Dynamic Content
+
+The Braze and [Future Anthem]({{site.baseurl}}/partners/message_personalization/dynamic_content/future_anthem/) partnership leverages Amplifier AI to deliver content personalization, real-time experiences, and dynamic audiences. Amplifier AI works across sports, casinos, and lottery, allowing you to enhance Braze player profiles with industry-specific player attributes, such as a favorite game, engagement score, expected next bet, and more.
+
+## Settings
+
+### Indentifier field-level encryption
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+Using [identifier field-level encryption]({{site.baseurl}}/user_guide/data_and_analytics/field_level_encryption/), you can seamlessly encrypt email addresses with AWS Key Management Service (KMS) to minimize personally identifiable information (PII) shared in Braze. Encryption replaces sensitive data with ciphertext, which is unreadable encrypted information.
+
+## 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.
+
+- [Swift SDK 10.3.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#1110)
+- [Swift SDK 11.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#1110)
+    - Adds support for [Swift 6 strict concurrency checking](https://developer.apple.com/documentation/swift/adoptingswift6)
+        - Relevant public Braze classes and data types now conform to the `Sendable` protocol and can be safely used across concurrency contexts.
+        - Main thread-only APIs are now marked with the `@MainActor` attribute.
+        - We recommend using Xcode 16.0 or later to take advantage of these features while minimizing the number of warnings generated by the compiler. Previous versions of Xcode may still be used, but some features may generate warnings.
+    - When integrating push notification support manually, you may need to update the `UNUserNotificationCenterDelegate` conformance to use the `@preconcurrency` attribute to prevent warnings.
+        - Applying the `@preconcurrency` attribute on protocol conformance is only available in Xcode 16.0 or later. Reference our sample integration code [here](https://github.com/braze-inc/braze-swift-sdk/tree/main/Examples/Swift/Sources/PushNotifications-Manual).
+- [React Native SDK 13.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#1300)
+    - Updates the native Android version bindings from [Braze Android SDK 31.1.0 to 32.1.0](https://github.com/braze-inc/braze-android-sdk/compare/v31.1.0...v32.1.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed).
+    - Updates the native iOS version bindings from [Braze Swift SDK 10.3.0 to 11.0.0](https://github.com/braze-inc/braze-swift-sdk/compare/10.3.0...11.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed).
+- [Flutter SDK 11.1.0](https://pub.dev/packages/braze_plugin/changelog#1110)
+- [Swift SDK 11.1.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#1110)
+- [Android SDK 33.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#3300)
+    - Updated Kotlin from 1.8 to Kotlin 2.0.
+- [Web SDK 5.5.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#550)
\ No newline at end of file
diff --git a/_docs/_help/release_notes/deprecations/grouparoo.md b/_docs/_help/release_notes/deprecations/grouparoo.md
index 7584f42c791..72b84007678 100644
--- a/_docs/_help/release_notes/deprecations/grouparoo.md
+++ b/_docs/_help/release_notes/deprecations/grouparoo.md
@@ -23,7 +23,7 @@ The Braze and Grouparoo integration makes it easy to operationalize data stored
 | Grouparoo account and project | A Grouparoo account and project are required to take advantage of this partnership.<br><br>This integration is possible to use with the free community edition and enterprise solutions provided by Grouparoo. Setup will take place in the Grouparoo configuration user interface. |
 | Braze REST API key | A Braze REST API key with users and track permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_hidden/archive_docs/previous_in-app_message_generations.md b/_docs/_hidden/archive_docs/previous_in-app_message_generations.md
index 26bcc05d8b3..c52eaf79305 100644
--- a/_docs/_hidden/archive_docs/previous_in-app_message_generations.md
+++ b/_docs/_hidden/archive_docs/previous_in-app_message_generations.md
@@ -140,7 +140,7 @@ For all of the in-app message types listed in the following table, the following
 | Slideup                            |     1:1      |         140         |
 | Modal (Image Only)                 |     1:1      |         140         |
 | Modal (With Text)                  |    29:10     |         140         |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Keeping in-app message file sizes small
 
diff --git a/_docs/_hidden/archive_docs/windows_universal/analytics/setting_custom_attributes.md b/_docs/_hidden/archive_docs/windows_universal/analytics/setting_custom_attributes.md
index 748892dca37..6605cf26cd5 100644
--- a/_docs/_hidden/archive_docs/windows_universal/analytics/setting_custom_attributes.md
+++ b/_docs/_hidden/archive_docs/windows_universal/analytics/setting_custom_attributes.md
@@ -52,7 +52,7 @@ bool SetCustomAttribute(STRING_KEY, BOOL_VALUE);
 bool SetCustomAttribute(STRING_KEY, INT_VALUE);
 ```
 {% endtab %}
-{% tab Double/Float %}
+{% tab Double or Float %}
 ```csharp
 bool SetCustomAttribute(STRING_KEY, DOUBLE_VALUE);
 ```
@@ -119,7 +119,7 @@ To set up a subscription for your users (either email or push), you can set foll
 | `OptedIn` | Subscribed, and explicitly opted in |
 | `Subscribed` | Subscribed, but not explicitly opted in |
 | `UnSubscribed` | Unsubscribed and/or explicitly opted out |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 - `EmailNotificationSubscriptionType`
   - Users will be set to `Subscribed` automatically upon receipt of a valid email address, however, we suggest that you establish an explicit opt-in process and set this value to `OptedIn` upon receipt of explicit consent from your user.
diff --git a/_docs/_hidden/archived_layouts/api_glossary.md b/_docs/_hidden/archived_layouts/api_glossary.md
index 05b163d1fbd..8b04f666935 100644
--- a/_docs/_hidden/archived_layouts/api_glossary.md
+++ b/_docs/_hidden/archived_layouts/api_glossary.md
@@ -88,7 +88,7 @@ The response from this endpoint includes a field for `email_template_id`, which
 | `modified_before`  |  No | String in ISO 8601 | Retrieve only templates updated at or before the given time. |
 | `limit` | No | Positive Number | Maximum number of templates to retrieve, default to 100 if not provided, maximum acceptable value is 1000. |
 | `offset`  |  No | Positive Number | Number of templates to skip before returning rest of the templates that fit the search criteria. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 
 {% endapi %}
@@ -140,7 +140,7 @@ GET https://YOUR_REST_API_URL/templates/email/list
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `email_template_id`  | Yes | String | Your email template's API Identifier. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% endapi %}
 
@@ -208,7 +208,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 |---|---|---|---|
 | `email_template_id`  | Yes | String | Your email template's API Identifier. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% endapi %}
 
@@ -286,7 +286,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | push_tokens | Array of objects with `app_id` and `token` string. You may optionally provide a `device_id` for the device this token is associated with, for example, `[{"app_id": App Identifier, "token": "abcd", "device_id": "optional_field_value"}]`. If a `device_id` is not provided, one will be randomly generated. |
 | time_zone | (string) Of time zone name from [IANA Time Zone Database][26] (for example, "America/New_York" or "Eastern Time (US & Canada)"). Only valid time zone values will be set. |
 | twitter | Hash containing any of `id` (integer), `screen_name` (string, X (formerly Twitter) handle), `followers_count` (integer), `friends_count` (integer), `statuses_count` (integer). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
 
diff --git a/_docs/_hidden/archived_layouts/get_endpoint.md b/_docs/_hidden/archived_layouts/get_endpoint.md
index 75afe71b91c..b051229d89b 100644
--- a/_docs/_hidden/archived_layouts/get_endpoint.md
+++ b/_docs/_hidden/archived_layouts/get_endpoint.md
@@ -41,7 +41,7 @@ Use this endpoint to pull a list of phone numbers that have been deemed "invalid
 | `limit` | Optional | Integer | Optional field to limit the number of results returned. Defaults to 100, maximum is 500. |
 | `offset` | Optional | Integer | Optional beginning point in the list to retrieve from. |
 | `phone_numbers` | Optional <br>(see note) | Array of Strings in e.164 format | If provided, we will return the phone number if it has been found to be invalid. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 You must provide either a `start_date` and an `end_date` OR `phone_numbers`. If you provide all three, `start_date`, `end_date`, and `phone_numbers`, we prioritize the given phone numbers and disregard the date range.
diff --git a/_docs/_hidden/archived_layouts/partner_page_template.md b/_docs/_hidden/archived_layouts/partner_page_template.md
index f1384b05891..845ef384414 100644
--- a/_docs/_hidden/archived_layouts/partner_page_template.md
+++ b/_docs/_hidden/archived_layouts/partner_page_template.md
@@ -56,7 +56,7 @@ The following requirements are typical requirements you might need from Braze. W
 |---|---|---|---|
 |Braze workspace REST API key | Braze platform | **Settings** > **API Key** page | This description should tell you what to do with the workspace REST API key. |
 |Braze API endpoint | Braze platform | Check out our [listed endpoints]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints) or open a [support ticket]({{site.baseurl}}/braze_support/). | Description pending. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## [Type of Integration] Integration
 
diff --git a/_docs/_hidden/archived_layouts/partner_page_template_video.md b/_docs/_hidden/archived_layouts/partner_page_template_video.md
index 81458625d7c..09fb8e462b0 100644
--- a/_docs/_hidden/archived_layouts/partner_page_template_video.md
+++ b/_docs/_hidden/archived_layouts/partner_page_template_video.md
@@ -58,7 +58,7 @@ The following requirements are typical requirements you might need from Braze. W
 |---|---|---|---|
 |Braze workspace REST API key | Braze platform | **Settings** > **App Settings** page | This description should tell you what to do with the workspace REST API key. |
 |Braze API endpoint | Braze platform | Check out our [listed endpoints]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints) or open a [support ticket]({{site.baseurl}}/braze_support/). | Description pending. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## [Type of Integration] Integration
 
@@ -99,7 +99,7 @@ Make sure you define parameters or elements that users might have to adjust from
 | -------- | ----------- |
 | Page Title | You can title your page anything. You have to have this. |
 | My First Heading | We recommend putting this in caps. This is also optional. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ### Step 3: How Many Steps
@@ -143,7 +143,7 @@ Make sure you define parameters or elements that users might have to adjust from
 | -------- | ----------- |
 | Page Title | You can title your page anything. You have to have this. |
 | My First Heading | We recommend putting this in caps. This is also optional. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ## Use Cases
diff --git a/_docs/_hidden/archived_layouts/post_endpoint.md b/_docs/_hidden/archived_layouts/post_endpoint.md
index 249afcf2535..46b561f6b30 100644
--- a/_docs/_hidden/archived_layouts/post_endpoint.md
+++ b/_docs/_hidden/archived_layouts/post_endpoint.md
@@ -53,7 +53,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | Parameter | Required | Data Type | Description |
 | ----------|-----------| ---------|------ |
 | `phone_number` | Required | Array of strings in e.164 format | An array of up to 50 phone numbers to modify. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Example request
 
diff --git a/_docs/_hidden/archived_layouts/reference.md b/_docs/_hidden/archived_layouts/reference.md
index 11613c30d24..f9ccae939a5 100644
--- a/_docs/_hidden/archived_layouts/reference.md
+++ b/_docs/_hidden/archived_layouts/reference.md
@@ -80,7 +80,7 @@ Make sure you define parameters or elements that users might have to adjust from
 | -------- | ----------- |
 | Page Title | You can title your page anything. You have to have this. |
 | My First Heading | We recommend putting this in caps. This is also optional. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ## Topic 2 Regarding this Concept
diff --git a/_docs/_hidden/archived_layouts/reference_video.md b/_docs/_hidden/archived_layouts/reference_video.md
index 371c6d075af..006dbe2a9e6 100644
--- a/_docs/_hidden/archived_layouts/reference_video.md
+++ b/_docs/_hidden/archived_layouts/reference_video.md
@@ -85,7 +85,7 @@ Make sure you define parameters or elements that users might have to adjust from
 | -------- | ----------- |
 | Page Title | You can title your page anything. You have to have this. |
 | My First Heading | We recommend putting this in caps. This is also optional. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Topic 2 Regarding this concept
 
diff --git a/_docs/_hidden/archived_layouts/tutorial.md b/_docs/_hidden/archived_layouts/tutorial.md
index e115386633b..bc15eb83eeb 100644
--- a/_docs/_hidden/archived_layouts/tutorial.md
+++ b/_docs/_hidden/archived_layouts/tutorial.md
@@ -77,7 +77,7 @@ Make sure you define parameters or elements that users might have to adjust from
 | -------- | ----------- |
 | Page Title | You can title your page anything. You have to have this. |
 | My First Heading | We recommend putting this in caps. This is also optional. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Step 2: Do the next thing
 
diff --git a/_docs/_hidden/archived_layouts/tutorial_video.md b/_docs/_hidden/archived_layouts/tutorial_video.md
index e4374d2310b..e87965c9418 100644
--- a/_docs/_hidden/archived_layouts/tutorial_video.md
+++ b/_docs/_hidden/archived_layouts/tutorial_video.md
@@ -81,7 +81,7 @@ Make sure you define parameters or elements that users might have to adjust from
 | -------- | ----------- |
 | Page Title | You can title your page anything. You have to have this. |
 | My First Heading | We recommend putting this in caps. This is also optional. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ## Step 2: Do the next thing
diff --git a/_docs/_hidden/archived_layouts/use_case.md b/_docs/_hidden/archived_layouts/use_case.md
index 6c4fb4d9c1f..246a9e94b03 100644
--- a/_docs/_hidden/archived_layouts/use_case.md
+++ b/_docs/_hidden/archived_layouts/use_case.md
@@ -58,7 +58,7 @@ It's time to talk about measurement! How should the Braze User look to measure t
 | Conversion 1 | This is a conversion. You should measure it because "reasons". | Boolean. |
 | Conversion 2 | This is another conversion. You should measure it because "reasons". | Boolean. |
 | Age | This is a user attribute. You should measure it because "reasons". | Integer. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## How to Build This Campaign/Canvas
 
diff --git a/_docs/_hidden/archived_layouts/use_case_video.md b/_docs/_hidden/archived_layouts/use_case_video.md
index dce3776a766..f69f93f9c0e 100644
--- a/_docs/_hidden/archived_layouts/use_case_video.md
+++ b/_docs/_hidden/archived_layouts/use_case_video.md
@@ -61,7 +61,7 @@ It's time to talk about measurement! How should the Braze User look to measure t
 | Conversion 1 | This is a conversion. You should measure it because "reasons". | Boolean. |
 | Conversion 2 | This is another conversion. You should measure it because "reasons". | Boolean. |
 | Age | This is a user attribute. You should measure it because "reasons". | Integer. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## How to Build This Campaign/Canvas
 
@@ -97,7 +97,7 @@ Make sure you define parameters or elements that users might have to adjust from
 | -------- | ----------- |
 | Page Title | You can title your page anything. You have to have this. |
 | My First Heading | We recommend putting this in caps. This is also optional. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ### Step 2: Send Your Message at the Right Time
diff --git a/_docs/_hidden/compliance/home.md b/_docs/_hidden/compliance/home.md
index 9e2af2ea0fe..f4654d237d8 100644
--- a/_docs/_hidden/compliance/home.md
+++ b/_docs/_hidden/compliance/home.md
@@ -31,4 +31,7 @@ guide_menu_list:
 - name: WhatsApp Channel
   link: /docs/compliance_documentation_whatsapp/
   image: /assets/img/braze_icons/channel-whatsapp.svg
+- name: LINE Channel
+  link: /docs/compliance_documentation_line/
+  image: /assets/img/braze_icons/channel-line.svg
 ---
diff --git a/_docs/_hidden/compliance/line_channel.md b/_docs/_hidden/compliance/line_channel.md
new file mode 100644
index 00000000000..ccaf33d1691
--- /dev/null
+++ b/_docs/_hidden/compliance/line_channel.md
@@ -0,0 +1,32 @@
+---
+nav_title: Compliance Documentation for LINE Services
+article: Compliance Documentation for LINE Services
+permalink: /compliance_documentation_line/
+description: "Compliance documentation relating to the LINE channel."
+page_order: 5
+noindex: true
+---
+
+# Compliance Documentation for LINE Services (“LINE Channel”)
+
+_Revision Date: 23 October 2024_
+
+_(Effective as of the Revision Date; subject to change)_
+
+The following additional terms apply in relation to Customer’s use of the LINE Channel:
+
+## Pre-requisites
+
+To send Messages via the LINE Channel, customers must obtain a LINE Verified Official Account, which is approved and granted by LINE at its own discretion. Customers should ensure they obtain a Verified Official Account from LINE before purchasing Braze Message Credits for the use of the LINE Channel. 
+
+## Applicable Third-Party Provider Terms
+
+By using the LINE Channel, Customer agrees to comply with and be bound by, as applicable, all terms and policies required by LY Corporation, and its affiliates, (collectively “LINE”) including, without limitation, LINE Official Account Terms of Use, Official Account API Terms of Use, LINE Official Account Guidelines LINE User Data Policy, and any policies, terms, guidelines, and documentation incorporated by reference thereto (collectively, the “LINE Terms”). For the sake of clarity, Customer is responsible for: (i) ensuring that any data processed in connection with LINE is processed in accordance with the LINE Terms as applicable; and (ii) any fees or payments due to LINE for the use of the LINE services in connection with the LINE Channel.
+
+Notwithstanding anything to the contrary in the LINE Terms, Customer remains primarily liable for its use of the LINE services. 
+
+## General terms
+
+Without limiting the generality of any Customer obligations under the Agreement, and for the avoidance of doubt, Customer shall be solely responsible for obtaining all necessary rights, consents, and authorizations and providing legally adequate privacy notices in connection with its use of this Channel and obtaining all legally required consents and authorizations for sending, or receiving as applicable, Messages through this Channel.
+
+
diff --git a/_docs/_hidden/misc_reference/regex_reference.md b/_docs/_hidden/misc_reference/regex_reference.md
index 2d24b3488f7..1d048ddbfa6 100644
--- a/_docs/_hidden/misc_reference/regex_reference.md
+++ b/_docs/_hidden/misc_reference/regex_reference.md
@@ -36,7 +36,7 @@ This page serves as a quick reference guide for regular expression, including co
 | End of string | `$` |
 | A word boundary | `\n` |
 | None-word boundary | `\B` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% tab Meta sequence %}
 
@@ -75,7 +75,7 @@ This page serves as a quick reference guide for regular expression, including co
 | Control character Y | `\cY` |
 | Backspace character | `[\b]` |
 | Makes any character literal | `\` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% tab General tokens %}
 
@@ -85,7 +85,7 @@ This page serves as a quick reference guide for regular expression, including co
 | Carriage return | `\r` |
 | Tab | `\t` |
 | Null character | `\0` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Character class modifiers %}
@@ -107,7 +107,7 @@ This page serves as a quick reference guide for regular expression, including co
 | Lowercase letters | `[:xdigit:]` |
 | Uppercase letters | `[:<:]` |
 | Word characters | `[:>:]` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% tab Group constants %}
 
@@ -164,7 +164,7 @@ This page serves as a quick reference guide for regular expression, including co
 | Regex engine modifier | `(*LIMIT_RECURSION=d)` |
 | Regex engine modifier | `(*NO_AUTO_POSSESS)` |
 | Regex engine modifier | `(*NO_START_OPT)` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% tab Quantifiers %}
 
@@ -179,7 +179,7 @@ This page serves as a quick reference guide for regular expression, including co
 | Greedy quantifier | `a*` |
 | Lazy quantifier | `a*?` |
 | Possessive quanitifer | `a*+` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% tab Anchors %}
 
@@ -193,7 +193,7 @@ This page serves as a quick reference guide for regular expression, including co
 | Absolute end of string | `\z` |
 | A word boundary | `\b` |
 | A non-word boundary | `\B` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 
 {% tab Flags and modifiers %}
@@ -210,7 +210,7 @@ This page serves as a quick reference guide for regular expression, including co
 | Ungreedy | `U` |
 | Anchor | `A` |
 | Duplicate group names | `J` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Substitution %}
@@ -228,7 +228,7 @@ This page serves as a quick reference guide for regular expression, including co
 | Uppercase transformation | `\U` |
 | Lowercase transformation | `\L` |
 | Terminate any transformation | `\E` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% endtabs %}
 
diff --git a/_docs/_hidden/misc_reference/scim_api_appendix.md b/_docs/_hidden/misc_reference/scim_api_appendix.md
index ff051659f82..76f0c5f8b05 100644
--- a/_docs/_hidden/misc_reference/scim_api_appendix.md
+++ b/_docs/_hidden/misc_reference/scim_api_appendix.md
@@ -33,7 +33,7 @@ A valid permissions object is a JSON object with the following key-value pairs:
 | --- | --- | --- | --- |
 | `companyPermissions` | Optional | Array | Array of company-level permission strings from the [Company permission strings](#company) table, in which the presence of the string corresponds to the user having the corresponding permission. |
 | `appGroup` | Required | Array | Array of [workspace permission objects](#workspace-permission-object). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ### Workspace permissions object {#workspace-permission-object}
 
@@ -46,7 +46,7 @@ A valid app group permission object is a JSON object with the following key-valu
 | `appGroupPermissionSets` | Optional | Array | Array with a single [workspace permissions set object](#workspace-permissions-set-object). |
 | `appGroupPermissions` | Required | Array | Array of workspace-level permission strings from the [workspace permission strings](#workspace-strings) table, in which the presence of the string corresponds to the user having the corresponding permission for the specified workspace. |
 | `team` | Optional | Array | Array of [Team permission objects](#team-permissions-object). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ### Workspace permissions set object {#workspace-permissions-set-object}
 
@@ -56,7 +56,7 @@ A valid workspace permissions set object is a JSON object with the following key
 | --- | --- | --- | --- |
 | `appGroupPermissionSetName` | Optional | String | Name of the workspace permission set that is being assigned to the user for this workspace. |
 | `appGroupPermissionSetID` | Required if `appGroupPermissionSetName` is missing | String | ID of the workspace, serving as an alternative method of specifying the workspace permission set assigned to the user for this workspace. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ### Team permissions object
 
@@ -67,7 +67,7 @@ A valid team permission object is a JSON object with the following key-value pai
 | `teamName` | Optional | String | Name of the team, which can be used to specify which team the permissions within this object are for. |
 | `teamId` | Required if `teamName` is missing | String | ID of the team, serving as an alternative method of specifying the team. |
 | `teamPermissions` | Required | Array | Array of team-level permission strings from the [teams permission strings](#team) table, in which the presence of the string corresponds to the user having the corresponding permission for the specified team. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Appendix
 
@@ -78,7 +78,7 @@ A valid team permission object is a JSON object with the following key-value pai
 | Administrator | `admin` |
 | Can Manage Company Settings | `manage_company_settings` |
 | Can Add/Remove Workspaces| `add_remove_app_groups` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Workspace permission strings {#workspace-strings}
 
@@ -108,7 +108,7 @@ A valid team permission object is a JSON object with the following key-value pai
 | Manage Subscription Groups | `manage_subscription_groups` |
 | Manage Approval Settings | `manage_approval_settings` |
 | Manage Catalogs Dashboard Permission | `manage_catalogs_dashboard_permission` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Team permission strings {#team}
 
@@ -123,7 +123,7 @@ A valid team permission object is a JSON object with the following key-value pai
 | View User Profile | `view_user_profile` |
 | Manage Dashboard Users | `manage_dashboard_users` |
 | Manage Media Library Assets | `manage_media_library` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Department strings
 
@@ -136,4 +136,4 @@ A valid team permission object is a JSON object with the following key-value pai
 | Finance | `finance` |
 | Marketing / Editorial | `marketing` |
 | Product Management | `pm` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
diff --git a/_docs/_hidden/misc_reference/x-in-y-behavior.md b/_docs/_hidden/misc_reference/x-in-y-behavior.md
index 411e93daf59..f3a554746f1 100644
--- a/_docs/_hidden/misc_reference/x-in-y-behavior.md
+++ b/_docs/_hidden/misc_reference/x-in-y-behavior.md
@@ -11,14 +11,6 @@ The behavior of these filters will remain largely the same and will be defined b
 - "Days" are defined as in UTC.
 - The current UTC day is defined as "0".
 
-{% details Why has the UTC definition changed from "1" to "0"? %}
-Local time zone scheduling requires that users stay in segments for 24 hours. In the case of Y = 1 day, we were in some cases evaluating less than 24 hours of the user's history when determining who should be processed for the campaign or Canvas.
-
-The change will make the filter more intuitive and more consistent with the behavior of our other calendar functionality, such as our send "in 1 day" scheduling options.
-{% enddetails %}
-
-<br>
-
 ## Use case
 
 The following campaign shown sends at 9 pm on April 16. The audience's segmentation is "Made More than 2 Purchases in the past 3 days".
diff --git a/_docs/_hidden/other/airship_migration.md b/_docs/_hidden/other/airship_migration.md
index aea502ef748..75da0cb2000 100644
--- a/_docs/_hidden/other/airship_migration.md
+++ b/_docs/_hidden/other/airship_migration.md
@@ -14,7 +14,7 @@ page_type: reference
 Braze uses Apple's device token for iOS.
 
 | **Braze Perspective:**<br>We ensure customers can continuously communicate with their users (such as push notifications) when in the process of migrating from Airship to Braze (Whether it be a hard cutover to 100% Braze or a granular transition such as 50% Airship 50% Braze, etc.). |
-{: .reset-td-br-1}
+{: .reset-td-br-1 role="presentation" }
 
 #### Push token migration
 
@@ -44,7 +44,7 @@ At a high level, Braze is a truly unique tool in the customer engagement space.
 Braze requires separate channels for push (one for iOS, one for Android).
 
 | **Braze Perspective:**<br>We enable our customers to get the best of both worlds instead of having to make concessions. Being able to leverage the individual channel to its full capacity offers more flexibility for the marketer and an improved user experience. This allows us to adopt the latest features of each OS; for example, Android supported rich notifications before iOS. |
-{: .reset-td-br-1}
+{: .reset-td-br-1 role="presentation" }
 
 Braze is able to send push notifications to users who do not update their application with the Braze SDK installed. Given that Braze has a valid push token, Braze can send the push notification without the Braze SDK as APNs will handle the rest. It is crucial to note that push message **analytics will not be available for builds without the Braze SDK**.
 
@@ -59,7 +59,7 @@ To replace Airship's message center campaign functionality, we recommend creatin
 Braze offers multiple [segmentation]({{site.baseurl}}/user_guide/engagement_tools/segments/) filters to provide a rich user experience for your customers.
 
 | **Braze Perspective**:<br> Segments in Braze are fully dynamic, so users will enter and exit the segment as the defined conditions change. |
-{: .reset-td-br-1}
+{: .reset-td-br-1 role="presentation" }
 
 #### User segment migration
 
diff --git a/_docs/_hidden/other/credit_ratios.md b/_docs/_hidden/other/credit_ratios.md
index a597e212564..06a37407fd6 100644
--- a/_docs/_hidden/other/credit_ratios.md
+++ b/_docs/_hidden/other/credit_ratios.md
@@ -20,141 +20,113 @@ In the event that Meta modifies its pricing or packaging for WhatsApp, Braze res
 
 **Service Conversations**: End-user sends a message to the business. When the business sends a message in response, this begins the 24-hour window.
 
+{% alert note %}
+As of November 1, 2024, service-type conversations are free and will not deduct from purchased credits allotments.
+{% endalert %}
+
 **Utility Conversations**: Facilitate a specific, agreed-upon request or transaction or update to a customer about an ongoing transaction, including post-purchase notifications and recurring billing statements.
 
 | References | Credit Ratio |
 |------------|--------------|
 | WhatsApp - Argentina Authentication | 9.5 |
 | WhatsApp - Argentina Marketing | 16.5 |
-| WhatsApp - Argentina Service | 8.5 |
 | WhatsApp - Argentina Utility | 9 |
 | WhatsApp - Brazil Authentication | 8.5 |
 | WhatsApp - Brazil Marketing | 16.5 |
-| WhatsApp - Brazil Service | 8 |
 | WhatsApp - Brazil Utility | 2.1 |
 | WhatsApp - Chile Authentication | 14 |
 | WhatsApp - Chile Marketing | 23.5 |
-| WhatsApp - Chile Service | 12 |
 | WhatsApp - Chile Utility | 5.3 |
 | WhatsApp - Colombia Authentication | 2 |
 | WhatsApp - Colombia Marketing | 3.5 |
-| WhatsApp - Colombia Service | 1.5 |
 | WhatsApp - Colombia Utility | 0.1 |
 | WhatsApp - Egypt Authentication | 16.5 |
 | WhatsApp - Egypt Marketing | 28.5 |
-| WhatsApp - Egypt Service | 17 |
 | WhatsApp - Egypt Utility | 1.4 |
 | WhatsApp - France Authentication | 18.5 |
 | WhatsApp - France Marketing | 38 |
-| WhatsApp - France Service | 23 |
 | WhatsApp - France Utility | 8 |
 | WhatsApp - Germany Authentication | 20.5 |
 | WhatsApp - Germany Marketing | 36 |
-| WhatsApp - Germany Service | 21.5 |
 | WhatsApp - Germany Utility | 14.6 |
 | WhatsApp - India Authentication | 0.4 |
 | India Authentication - International | 7.4 |
 | WhatsApp - India Marketing | 2.5 |
-| WhatsApp - India Service | 1 |
 | WhatsApp - India Utility | 0.4 |
 | WhatsApp - Indonesia Authentication | 8 |
 | Indonesia Authentication - International | 36.1 |
 | WhatsApp - Indonesia Marketing | 11 |
-| WhatsApp - Indonesia Service | 5 |
 | WhatsApp - Indonesia Utility | 5.5 |
 | WhatsApp - Israel Authentication | 4.5 |
 | WhatsApp - Israel Marketing | 9.5 |
-| WhatsApp - Israel Service | 5 |
 | WhatsApp - Israel Utility | 1.4 |
 | WhatsApp - Italy Authentication | 10 |
 | WhatsApp - Italy Marketing | 18.5 |
-| WhatsApp - Italy Service | 10 |
 | WhatsApp - Italy Utility | 8 |
 | WhatsApp - Malaysia Authentication | 5 |
 | WhatsApp - Malaysia Marketing | 23 |
-| WhatsApp - Malaysia Service | 6 |
 | WhatsApp - Malaysia Utility | 3.7 |
 | WhatsApp - Mexico Authentication | 6.5 |
 | WhatsApp - Mexico Marketing | 11.5 |
-| WhatsApp - Mexico Service | 3 |
 | WhatsApp - Mexico Utility | 2.7 |
 | WhatsApp - Netherlands Authentication | 19 |
 | WhatsApp - Netherlands Marketing | 42.5 |
-| WhatsApp - Netherlands Service | 23.5 |
 | WhatsApp - Netherlands Utility | 13.3 |
 | WhatsApp - Nigeria Authentication | 7.5 |
 | WhatsApp - Nigeria Marketing | 13.5 |
-| WhatsApp - Nigeria Service | 8 |
 | WhatsApp - Nigeria Utility | 1.8 |
 | WhatsApp - North America Authentication | 3.5 |
 | WhatsApp - North America Marketing | 6.5 |
-| WhatsApp - North America Service | 2.5 |
 | WhatsApp - North America Utility | 1.1 |
 | WhatsApp - Other Authentication | 8 |
 | WhatsApp - Other Marketing | 16 |
-| WhatsApp - Other Service | 4 |
 | WhatsApp - Other Utility | 2 |
 | WhatsApp - Pakistan Authentication | 6 |
 | WhatsApp - Pakistan Marketing | 12.5 |
-| WhatsApp - Pakistan Service | 4 |
 | WhatsApp - Pakistan Utility | 1.4 |
 | WhatsApp - Peru Authentication | 10 |
 | WhatsApp - Peru Marketing | 18.5 |
-| WhatsApp - Peru Service | 5 |
 | WhatsApp - Peru Utility | 5.3 |
 | WhatsApp - Rest of Africa Authentication | 4 |
 | WhatsApp - Rest of Africa Marketing | 6 |
-| WhatsApp - Rest of Africa Service | 9.5 |
 | WhatsApp - Rest of Africa Utility | 1.6 |
 | WhatsApp - Rest of Asia Pacific Authentication | 11.5 |
 | WhatsApp - Rest of Asia Pacific Marketing | 19.5 |
-| WhatsApp - Rest of Asia Pacific Service | 6 |
 | WhatsApp - Rest of Asia Pacific Utility | 4.2 |
 | WhatsApp - Rest of Central & Eastern Europe Authentication | 15 |
 | WhatsApp - Rest of Central & Eastern Europe Marketing | 23 |
-| WhatsApp - Rest of Central & Eastern Europe Service | 6.5 |
 | WhatsApp - Rest of Central & Eastern Europe Utility | 9.4 |
 | WhatsApp - Rest of Latin America Authentication | 12 |
 | WhatsApp - Rest of Latin America Marketing | 19.5 |
-| WhatsApp - Rest of Latin America Service | 11 |
 | WhatsApp - Rest of Latin America Utility | 3 |
 | WhatsApp - Rest of Middle East Authentication | 4.5 |
 | WhatsApp - Rest of Middle East Marketing | 9 |
-| WhatsApp - Rest of Middle East Service | 6 |
 | WhatsApp - Rest of Middle East Utility | 4.2 |
 | WhatsApp - Rest of Western Europe Authentication | 10 |
 | WhatsApp - Rest of Western Europe Marketing | 15.5 |
-| WhatsApp - Rest of Western Europe Service | 10.5 |
 | WhatsApp - Rest of Western Europe Utility | 8 |
 | WhatsApp - Russia Authentication | 11.5 |
 | WhatsApp - Russia Marketing | 21.5 |
-| WhatsApp - Russia Service | 10.5 |
 | WhatsApp - Russia Utility | 10.6 |
 | WhatsApp - Saudi Arabia Authentication | 6 |
 | WhatsApp - Saudi Arabia Marketing | 11 |
-| WhatsApp - Saudi Arabia Service | 5 |
 | WhatsApp - Saudi Arabia Utility | 3.1 |
 | WhatsApp - South Africa Authentication | 5 |
 | WhatsApp - South Africa Marketing | 10 |
-| WhatsApp - South Africa Service | 4.5 |
 | WhatsApp - South Africa Utility | 2 |
 | WhatsApp - Spain Authentication | 9 |
 | WhatsApp - Spain Marketing | 16.5 |
-| WhatsApp - Spain Service | 10 |
 | WhatsApp - Spain Utility | 5.3 |
 | WhatsApp - Turkey Authentication | 2 |
 | WhatsApp - Turkey Marketing | 3 |
-| WhatsApp - Turkey Service | 1 |
 | WhatsApp - Turkey Utility | 1.4 |
 | WhatsApp - United Arab Emirates Authentication | 4.5 |
 | WhatsApp - United Arab Emirates Marketing | 9 |
-| WhatsApp - United Arab Emirates Service | 5 |
 | WhatsApp - United Arab Emirates Utility | 4.2 |
 | WhatsApp - United Kingdom Authentication | 9.5 |
 | WhatsApp - United Kingdom Marketing | 14 |
-| WhatsApp - United Kingdom Service | 10.5 |
 | WhatsApp - United Kingdom Utility | 5.8 |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## WhatsApp billing region breakdown
 
diff --git a/_docs/_hidden/other/generations.md b/_docs/_hidden/other/generations.md
index ad0939e511b..20fe5cca6a2 100644
--- a/_docs/_hidden/other/generations.md
+++ b/_docs/_hidden/other/generations.md
@@ -16,7 +16,7 @@ This chart highlights the features and message types that are currently availabl
 | **Generation 1** | • In-app triggered Fullscreen, Modal, and Slideup message types | Custom HTML Messages <br> • Web Email Capture Form <br> • Web Modal with Custom CSS |
 | **Generation 2** | • Text Alignment Controls <br> • Overlay behind Modal <br> • Image Safe Zone in Preview Window | Button Border |
 | **Generation 3** | • Button Border <br> • Refined Look & Feel for All Message Types <br> • Concept of Generations 1, 2 and 3 <br> • New Close X Asset <br> • Improved accessibility on Web <br> • Improved support on Notched Devices | (The latest Generation always has full feature support!) |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ![Difference in Generations]({% image_buster /assets/img/iam-generations-of-modals.png %})
 
diff --git a/_docs/_hidden/pricing/message_credits_delta_a3sy.md b/_docs/_hidden/pricing/message_credits_delta_a3sy.md
index 582a2e4bd05..5a8c30b82ea 100644
--- a/_docs/_hidden/pricing/message_credits_delta_a3sy.md
+++ b/_docs/_hidden/pricing/message_credits_delta_a3sy.md
@@ -8,14 +8,14 @@ hide_toc: true
 
 # Message Credits - Delta (Confidential)
 
-> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. We use Message Credits to provide a flexible and transparent experience when taking advantage of Braze messaging channels. You may use the allotment of credits purchased across any of the channels presented in the table on this page.
+> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. Message Credits provide a flexible and transparent experience when taking advantage of Braze messaging channels. Credits give you access to any of the channels presented in the table on this page.
 
 {% alert note %}
 Different channels will have different units of measure in reporting.<br><br>
 <b>WhatsApp:</b> Conversations<br>
 <b>SMS:</b> Segments<br>
 <b>MMS:</b> Segments<br><br>
-In other words, credits used for WhatsApp messages will be calculated on conversation initiations, and credits used for both SMS and MMS messages will be calculated on segments sent.
+In other words, credits per WhatsApp messages will be calculated on conversation initiations, and credits per for both SMS and MMS messages will be calculated on segments sent.
 <br><br>
 Lastly, carrier fees are billed separately (in arrears) and are not considered as part of this Message Credits SKU.
 {% endalert %}
@@ -28,8 +28,8 @@ Column definitions are as follows:
 | **Channel Credit Ratio** | Baseline credit amount for each channel |
 | **Destination** | Specific final region, country, or type of message being sent through the Braze platform |
 | **Multiplier** | Scaler to the Channel Credit Ratio, depending on pricing of the specific destination |
-| **Credits Used with 1 Send** | Exact number of Message Credits used to send one message<br> (credits per message = channel credit ratio x destination multiplier) |
-{: .reset-td-br-1 .reset-td-br-2}
+| **Credits per 1 Send** | Exact number of Message Credit to send one message<br> (credits per message = channel credit ratio x destination multiplier) |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ## Credit ratio table for Message Credits - Delta
@@ -45,7 +45,7 @@ Column definitions are as follows:
         <th><b>Channel Credit Ratio</b></th>
         <th><b>Destination</b></th>
         <th><b>Multiplier</b></th>
-        <th class="credits-column"><b>Credits Used with 1 Send</b></th>
+        <th class="credits-column"><b>Credits per 1 Send</b></th>
     </tr>
     <tr>
         <td>SMS - US / CA</td>
@@ -1769,13 +1769,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Argentina Service</td>
-        <td>0.85</td>
-        <td>8.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1797,13 +1790,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Brazil Service</td>
-        <td>0.80</td>
-        <td>8.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1825,13 +1811,6 @@ Column definitions are as follows:
         <td>2.35</td>
         <td>23.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Chile Service</td>
-        <td>1.20</td>
-        <td>12.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1853,13 +1832,6 @@ Column definitions are as follows:
         <td>0.35</td>
         <td>3.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Colombia Service</td>
-        <td>0.15</td>
-        <td>1.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1881,13 +1853,6 @@ Column definitions are as follows:
         <td>2.85</td>
         <td>28.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Egypt Service</td>
-        <td>1.70</td>
-        <td>17.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1909,13 +1874,6 @@ Column definitions are as follows:
         <td>3.80</td>
         <td>38.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>France Service</td>
-        <td>2.30</td>
-        <td>23.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1937,13 +1895,6 @@ Column definitions are as follows:
         <td>3.60</td>
         <td>36.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Germany Service</td>
-        <td>2.15</td>
-        <td>21.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1972,13 +1923,6 @@ Column definitions are as follows:
         <td>0.25</td>
         <td>2.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>India Service</td>
-        <td>0.10</td>
-        <td>1.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2007,13 +1951,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>11.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Indonesia Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2035,13 +1972,6 @@ Column definitions are as follows:
         <td>0.95</td>
         <td>9.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Israel Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2063,13 +1993,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>18.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Italy Service</td>
-        <td>1.00</td>
-        <td>10.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2091,13 +2014,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>23.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Malaysia Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2119,13 +2035,6 @@ Column definitions are as follows:
         <td>1.15</td>
         <td>11.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Mexico Service</td>
-        <td>0.30</td>
-        <td>3.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2147,13 +2056,6 @@ Column definitions are as follows:
         <td>4.25</td>
         <td>42.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Netherlands Service</td>
-        <td>2.35</td>
-        <td>23.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2175,13 +2077,6 @@ Column definitions are as follows:
         <td>1.35</td>
         <td>13.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Nigeria Service</td>
-        <td>0.80</td>
-        <td>8.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2203,13 +2098,6 @@ Column definitions are as follows:
         <td>0.65</td>
         <td>6.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>North America Service</td>
-        <td>0.25</td>
-        <td>2.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2231,13 +2119,6 @@ Column definitions are as follows:
         <td>1.60</td>
         <td>16.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Other Service</td>
-        <td>0.40</td>
-        <td>4.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2259,13 +2140,6 @@ Column definitions are as follows:
         <td>1.25</td>
         <td>12.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Pakistan Service</td>
-        <td>0.40</td>
-        <td>4.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2287,13 +2161,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>18.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Peru Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2315,13 +2182,6 @@ Column definitions are as follows:
         <td>0.60</td>
         <td>6.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Africa Service</td>
-        <td>0.95</td>
-        <td>9.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2343,13 +2203,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>19.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Asia Pacific Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2371,13 +2224,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>23.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Central &amp; Eastern Europe Service</td>
-        <td>0.65</td>
-        <td>6.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2399,13 +2245,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>19.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Latin America Service</td>
-        <td>1.10</td>
-        <td>11.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2427,13 +2266,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>9.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Middle East Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2455,13 +2287,6 @@ Column definitions are as follows:
         <td>1.55</td>
         <td>15.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Western Europe Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2483,13 +2308,6 @@ Column definitions are as follows:
         <td>2.15</td>
         <td>21.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Russia Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2511,13 +2329,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>11.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Saudi Arabia Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2539,13 +2350,6 @@ Column definitions are as follows:
         <td>1.00</td>
         <td>10.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>South Africa Service</td>
-        <td>0.45</td>
-        <td>4.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2567,13 +2371,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Spain Service</td>
-        <td>1.00</td>
-        <td>10.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2595,13 +2392,6 @@ Column definitions are as follows:
         <td>0.30</td>
         <td>3.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Turkey Service</td>
-        <td>0.10</td>
-        <td>1.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2623,13 +2413,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>9.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>United Arab Emirates Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2651,13 +2434,6 @@ Column definitions are as follows:
         <td>1.40</td>
         <td>14.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>United Kingdom Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2665,8 +2441,15 @@ Column definitions are as follows:
         <td>0.58</td>
         <td>5.80</td>
     </tr>
+    <tr>
+        <td>LINE</td>
+        <td>1</td>
+        <td>All regions</td>
+        <td>0.15</td>
+        <td>0.15</td>
+    </tr>
 </table>
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% enddetails %}
 
 ------
@@ -2700,7 +2483,7 @@ Authentication conversations will only be supported on a case-by-case basis and
 **Service Conversations:** User-initiated conversations that are responded to with a non-templated message.
 
 {% alert note %}
-User-initiated conversations that are responded to with a marketing or utility template will be charged as such.
+As of November 1, 2024, service-type conversations are free and will not deduct from purchased credits allotments.
 {% endalert %}
 
 ## Billing region breakdown
diff --git a/_docs/_hidden/pricing/message_credits_gamma_0dhr.md b/_docs/_hidden/pricing/message_credits_gamma_0dhr.md
index 1ef8a850770..8ae74683d18 100644
--- a/_docs/_hidden/pricing/message_credits_gamma_0dhr.md
+++ b/_docs/_hidden/pricing/message_credits_gamma_0dhr.md
@@ -8,14 +8,14 @@ hide_toc: true
 
 # Message Credits - Gamma (Confidential)
 
-> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. We use Message Credits to provide a flexible and transparent experience when taking advantage of Braze messaging channels. You may use the allotment of credits purchased across any of the channels presented in the table on this page.
+> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. Message Credits provide a flexible and transparent experience when taking advantage of Braze messaging channels. Credits give you access to any of the channels presented in the table on this page.
 
 {% alert note %}
 Different channels will have different units of measure in reporting.<br><br>
 <b>WhatsApp:</b> Conversations<br>
 <b>SMS:</b> Segments<br>
 <b>MMS:</b> Segments<br><br>
-In other words, credits used for WhatsApp messages will be calculated on conversation initiations, and credits used for both SMS and MMS messages will be calculated on segments sent.
+In other words, credits per WhatsApp messages will be calculated on conversation initiations, and credits per for both SMS and MMS messages will be calculated on segments sent.
 <br><br>
 Lastly, carrier fees are billed separately (in arrears) and are not considered as part of this Message Credits SKU.
 {% endalert %}
@@ -28,8 +28,8 @@ Column definitions are as follows:
 | **Channel Credit Ratio** | Baseline credit amount for each channel |
 | **Destination** | Specific final region, country, or type of message being sent through the Braze platform |
 | **Multiplier** | Scaler to the Channel Credit Ratio, depending on pricing of the specific destination |
-| **Credits Used with 1 Send** | Exact number of Message Credits used to send one message<br> (credits per message = channel credit ratio x destination multiplier) |
-{: .reset-td-br-1 .reset-td-br-2}
+| **Credits per 1 send** | Exact number of Message Credit to send one message<br> (credits per message = channel credit ratio x destination multiplier) |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ## Credit ratio table for Message Credits - Gamma
@@ -45,7 +45,7 @@ Column definitions are as follows:
         <th><b>Channel Credit Ratio</b></th>
         <th><b>Destination</b></th>
         <th><b>Multiplier</b></th>
-        <th class="credits-column"><b>Credits Used with 1 Send</b></th>
+        <th class="credits-column"><b>Credits per 1 send</b></th>
     </tr>
     <tbody><tr>
         <td>SMS - US / CA</td>
@@ -1769,13 +1769,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Argentina Service</td>
-        <td>0.85</td>
-        <td>8.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1797,13 +1790,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Brazil Service</td>
-        <td>0.80</td>
-        <td>8.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1825,13 +1811,6 @@ Column definitions are as follows:
         <td>2.35</td>
         <td>23.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Chile Service</td>
-        <td>1.20</td>
-        <td>12.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1853,13 +1832,6 @@ Column definitions are as follows:
         <td>0.35</td>
         <td>3.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Colombia Service</td>
-        <td>0.15</td>
-        <td>1.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1881,13 +1853,6 @@ Column definitions are as follows:
         <td>2.85</td>
         <td>28.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Egypt Service</td>
-        <td>1.70</td>
-        <td>17.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1909,13 +1874,6 @@ Column definitions are as follows:
         <td>3.80</td>
         <td>38.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>France Service</td>
-        <td>2.30</td>
-        <td>23.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1937,13 +1895,6 @@ Column definitions are as follows:
         <td>3.60</td>
         <td>36.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Germany Service</td>
-        <td>2.15</td>
-        <td>21.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1972,13 +1923,6 @@ Column definitions are as follows:
         <td>0.25</td>
         <td>2.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>India Service</td>
-        <td>0.10</td>
-        <td>1.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2007,13 +1951,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>11.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Indonesia Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2035,13 +1972,6 @@ Column definitions are as follows:
         <td>0.95</td>
         <td>9.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Israel Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2063,13 +1993,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>18.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Italy Service</td>
-        <td>1.00</td>
-        <td>10.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2091,13 +2014,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>23.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Malaysia Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2119,13 +2035,6 @@ Column definitions are as follows:
         <td>1.15</td>
         <td>11.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Mexico Service</td>
-        <td>0.30</td>
-        <td>3.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2147,13 +2056,6 @@ Column definitions are as follows:
         <td>4.25</td>
         <td>42.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Netherlands Service</td>
-        <td>2.35</td>
-        <td>23.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2175,13 +2077,6 @@ Column definitions are as follows:
         <td>1.35</td>
         <td>13.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Nigeria Service</td>
-        <td>0.80</td>
-        <td>8.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2203,13 +2098,6 @@ Column definitions are as follows:
         <td>0.65</td>
         <td>6.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>North America Service</td>
-        <td>0.25</td>
-        <td>2.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2231,13 +2119,6 @@ Column definitions are as follows:
         <td>1.60</td>
         <td>16.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Other Service</td>
-        <td>0.40</td>
-        <td>4.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2259,13 +2140,6 @@ Column definitions are as follows:
         <td>1.25</td>
         <td>12.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Pakistan Service</td>
-        <td>0.40</td>
-        <td>4.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2287,13 +2161,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>18.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Peru Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2315,13 +2182,6 @@ Column definitions are as follows:
         <td>0.60</td>
         <td>6.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Africa Service</td>
-        <td>0.95</td>
-        <td>9.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2343,13 +2203,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>19.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Asia Pacific Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2371,13 +2224,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>23.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Central &amp; Eastern Europe Service</td>
-        <td>0.65</td>
-        <td>6.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2399,13 +2245,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>19.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Latin America Service</td>
-        <td>1.10</td>
-        <td>11.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2427,13 +2266,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>9.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Middle East Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2455,13 +2287,6 @@ Column definitions are as follows:
         <td>1.55</td>
         <td>15.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Western Europe Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2483,13 +2308,6 @@ Column definitions are as follows:
         <td>2.15</td>
         <td>21.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Russia Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2511,13 +2329,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>11.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Saudi Arabia Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2539,13 +2350,6 @@ Column definitions are as follows:
         <td>1.00</td>
         <td>10.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>South Africa Service</td>
-        <td>0.45</td>
-        <td>4.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2567,13 +2371,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Spain Service</td>
-        <td>1.00</td>
-        <td>10.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2595,13 +2392,6 @@ Column definitions are as follows:
         <td>0.30</td>
         <td>3.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Turkey Service</td>
-        <td>0.10</td>
-        <td>1.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2623,13 +2413,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>9.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>United Arab Emirates Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2651,13 +2434,6 @@ Column definitions are as follows:
         <td>1.40</td>
         <td>14.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>United Kingdom Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2665,8 +2441,15 @@ Column definitions are as follows:
         <td>0.58</td>
         <td>5.80</td>
     </tr>
+    <tr>
+        <td>LINE</td>
+        <td>1</td>
+        <td>All regions</td>
+        <td>0.15</td>
+        <td>0.15</td>
+    </tr>
 </tbody></table>
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% enddetails %}
 
 ------
@@ -2700,7 +2483,7 @@ Authentication conversations will only be supported on a case-by-case basis and
 **Service Conversations:** User-initiated conversations that are responded to with a non-templated message.
 
 {% alert note %}
-User-initiated conversations that are responded to with a marketing or utility template will be charged as such.
+As of November 1, 2024, service-type conversations are free and will not deduct from purchased credits allotments.
 {% endalert %}
 
 ## Billing region breakdown
diff --git a/_docs/_hidden/pricing/message_credits_lambda_k5gh.md b/_docs/_hidden/pricing/message_credits_lambda_k5gh.md
index 02b2e7901b0..03b42a33b80 100644
--- a/_docs/_hidden/pricing/message_credits_lambda_k5gh.md
+++ b/_docs/_hidden/pricing/message_credits_lambda_k5gh.md
@@ -8,14 +8,14 @@ hide_toc: true
 
 # Message Credits - Lambda (Confidential)
 
-> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. We use Message Credits to provide a flexible and transparent experience when taking advantage of Braze messaging channels. You may use the allotment of credits purchased across any of the channels presented in the table on this page.
+> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. Message Credits provide a flexible and transparent experience when taking advantage of Braze messaging channels. Credits give you access to any of the channels presented in the table on this page.
 
 {% alert note %}
 Different channels will have different units of measure in reporting.<br><br>
 <b>WhatsApp:</b> Conversations<br>
 <b>SMS:</b> Segments<br>
 <b>MMS:</b> Segments<br><br>
-In other words, credits used for WhatsApp messages will be calculated on conversation initiations, and credits used for both SMS and MMS messages will be calculated on segments sent.
+In other words, credits per WhatsApp messages will be calculated on conversation initiations, and credits per for both SMS and MMS messages will be calculated on segments sent.
 <br><br>
 Lastly, carrier fees are billed separately (in arrears) and are not considered as part of this Message Credits SKU.
 {% endalert %}
@@ -28,8 +28,8 @@ Column definitions are as follows:
 | **Channel Credit Ratio** | Baseline credit amount for each channel |
 | **Destination** | Specific final region, country, or type of message being sent through the Braze platform |
 | **Multiplier** | Scaler to the Channel Credit Ratio, depending on pricing of the specific destination |
-| **Credits Used with 1 Send** | Exact number of Message Credits used to send one message<br> (credits per message = channel credit ratio x destination multiplier)  |
-{: .reset-td-br-1 .reset-td-br-2}
+| **Credits per 1 Send** | Exact number of Message Credit to send one message<br> (credits per message = channel credit ratio x destination multiplier)  |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ## Credit ratio table for Message Credits - Lambda
@@ -45,7 +45,7 @@ Column definitions are as follows:
         <th><b>Channel Credit Ratio</b></th>
         <th><b>Destination</b></th>
         <th><b>Multiplier</b></th>
-        <th class="credits-column"><b>Credits Used with 1 Send</b></th>
+        <th class="credits-column"><b>Credits per 1 Send</b></th>
     </tr>
     <tr>
         <td>SMS - US / CA</td>
@@ -1769,13 +1769,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Argentina Service</td>
-        <td>0.85</td>
-        <td>8.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1797,13 +1790,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Brazil Service</td>
-        <td>0.80</td>
-        <td>8.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1825,13 +1811,6 @@ Column definitions are as follows:
         <td>2.35</td>
         <td>23.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Chile Service</td>
-        <td>1.20</td>
-        <td>12.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1853,13 +1832,6 @@ Column definitions are as follows:
         <td>0.35</td>
         <td>3.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Colombia Service</td>
-        <td>0.15</td>
-        <td>1.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1881,13 +1853,6 @@ Column definitions are as follows:
         <td>2.85</td>
         <td>28.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Egypt Service</td>
-        <td>1.70</td>
-        <td>17.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1909,13 +1874,6 @@ Column definitions are as follows:
         <td>3.80</td>
         <td>38.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>France Service</td>
-        <td>2.30</td>
-        <td>23.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1937,13 +1895,6 @@ Column definitions are as follows:
         <td>3.60</td>
         <td>36.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Germany Service</td>
-        <td>2.15</td>
-        <td>21.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1972,13 +1923,6 @@ Column definitions are as follows:
         <td>0.25</td>
         <td>2.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>India Service</td>
-        <td>0.10</td>
-        <td>1.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2007,13 +1951,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>11.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Indonesia Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2035,13 +1972,6 @@ Column definitions are as follows:
         <td>0.95</td>
         <td>9.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Israel Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2063,13 +1993,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>18.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Italy Service</td>
-        <td>1.00</td>
-        <td>10.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2091,13 +2014,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>23.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Malaysia Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2119,13 +2035,6 @@ Column definitions are as follows:
         <td>1.15</td>
         <td>11.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Mexico Service</td>
-        <td>0.30</td>
-        <td>3.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2147,13 +2056,6 @@ Column definitions are as follows:
         <td>4.25</td>
         <td>42.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Netherlands Service</td>
-        <td>2.35</td>
-        <td>23.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2175,13 +2077,6 @@ Column definitions are as follows:
         <td>1.35</td>
         <td>13.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Nigeria Service</td>
-        <td>0.80</td>
-        <td>8.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2203,13 +2098,6 @@ Column definitions are as follows:
         <td>0.65</td>
         <td>6.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>North America Service</td>
-        <td>0.25</td>
-        <td>2.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2231,13 +2119,6 @@ Column definitions are as follows:
         <td>1.60</td>
         <td>16.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Other Service</td>
-        <td>0.40</td>
-        <td>4.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2259,13 +2140,6 @@ Column definitions are as follows:
         <td>1.25</td>
         <td>12.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Pakistan Service</td>
-        <td>0.40</td>
-        <td>4.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2287,13 +2161,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>18.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Peru Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2315,13 +2182,6 @@ Column definitions are as follows:
         <td>0.60</td>
         <td>6.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Africa Service</td>
-        <td>0.95</td>
-        <td>9.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2343,13 +2203,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>19.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Asia Pacific Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2371,13 +2224,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>23.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Central &amp; Eastern Europe Service</td>
-        <td>0.65</td>
-        <td>6.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2399,13 +2245,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>19.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Latin America Service</td>
-        <td>1.10</td>
-        <td>11.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2427,13 +2266,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>9.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Middle East Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2455,13 +2287,6 @@ Column definitions are as follows:
         <td>1.55</td>
         <td>15.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Western Europe Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2483,13 +2308,6 @@ Column definitions are as follows:
         <td>2.15</td>
         <td>21.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Russia Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2511,13 +2329,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>11.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Saudi Arabia Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2539,13 +2350,6 @@ Column definitions are as follows:
         <td>1.00</td>
         <td>10.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>South Africa Service</td>
-        <td>0.45</td>
-        <td>4.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2567,13 +2371,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Spain Service</td>
-        <td>1.00</td>
-        <td>10.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2595,13 +2392,6 @@ Column definitions are as follows:
         <td>0.30</td>
         <td>3.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Turkey Service</td>
-        <td>0.10</td>
-        <td>1.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2623,13 +2413,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>9.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>United Arab Emirates Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2637,13 +2420,6 @@ Column definitions are as follows:
         <td>0.42</td>
         <td>4.20</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>United Kingdom Authentication</td>
-        <td>0.95</td>
-        <td>9.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2651,13 +2427,6 @@ Column definitions are as follows:
         <td>1.40</td>
         <td>14.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>United Kingdom Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2665,8 +2434,15 @@ Column definitions are as follows:
         <td>0.58</td>
         <td>5.80</td>
     </tr>
+    <tr>
+        <td>LINE</td>
+        <td>1</td>
+        <td>All regions</td>
+        <td>0.15</td>
+        <td>0.15</td>
+    </tr>
 </table>
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% enddetails %}
 
 ------
@@ -2700,7 +2476,7 @@ Authentication conversations will only be supported on a case-by-case basis and
 **Service Conversations:** User-initiated conversations that are responded to with a non-templated message.
 
 {% alert note %}
-User-initiated conversations that are responded to with a marketing or utility template will be charged as such.
+As of November 1, 2024, service-type conversations are free and will not deduct from purchased credits allotments.
 {% endalert %}
 
 ## Billing region breakdown
diff --git a/_docs/_hidden/pricing/message_credits_sigma_pow2.md b/_docs/_hidden/pricing/message_credits_sigma_pow2.md
index 2d99db7bfe4..f432ee0c7a7 100644
--- a/_docs/_hidden/pricing/message_credits_sigma_pow2.md
+++ b/_docs/_hidden/pricing/message_credits_sigma_pow2.md
@@ -8,14 +8,14 @@ hide_toc: true
 
 # Message Credits - Sigma (Confidential)
 
-> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. We use Message Credits to provide a flexible and transparent experience when taking advantage of Braze messaging channels. You may use the allotment of credits purchased across any of the channels presented in the table on this page.
+> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. Message Credits provide a flexible and transparent experience when taking advantage of Braze messaging channels. Credits give you access to any of the channels presented in the table on this page.
 
 {% alert note %}
 Different channels will have different units of measure in reporting.<br><br>
 <b>WhatsApp:</b> Conversations<br>
 <b>SMS:</b> Segments<br>
 <b>MMS:</b> Segments<br><br>
-In other words, credits used for WhatsApp messages will be calculated on conversation initiations, and credits used for both SMS and MMS messages will be calculated on segments sent.
+In other words, credits per WhatsApp messages will be calculated on conversation initiations, and credits per for both SMS and MMS messages will be calculated on segments sent.
 <br><br>
 Lastly, carrier fees are billed separately (in arrears) and are not considered as part of this Message Credits SKU.
 {% endalert %}
@@ -28,8 +28,8 @@ Column definitions are as follows:
 | **Channel Credit Ratio** | Baseline credit amount for each channel |
 | **Destination** | Specific final region, country, or type of message being sent through the Braze platform |
 | **Multiplier** | Scaler to the Channel Credit Ratio, depending on pricing of the specific destination |
-| **Credits Used with 1 Send** | Exact number of Message Credits used to send one message<br> (credits per message = channel credit ratio x destination multiplier) |
-{: .reset-td-br-1 .reset-td-br-2}
+| **Credits per 1 send** | Exact number of Message Credit to send one message<br> (credits per message = channel credit ratio x destination multiplier) |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ## Credit ratio table for Message Credits - Sigma
@@ -45,7 +45,7 @@ Column definitions are as follows:
         <th><b>Channel Credit Ratio</b></th>
         <th><b>Destination</b></th>
         <th><b>Multiplier</b></th>
-        <th class="credits-column"><b>Credits Used with 1 Send</b></th>
+        <th class="credits-column"><b>Credits per 1 send</b></th>
     </tr>
     <tbody><tr>
         <td>SMS - US / CA</td>
@@ -1769,13 +1769,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>12.38</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Argentina Service</td>
-        <td>0.85</td>
-        <td>6.38</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -1797,13 +1790,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>12.38</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Brazil Service</td>
-        <td>0.80</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -1825,13 +1811,6 @@ Column definitions are as follows:
         <td>2.35</td>
         <td>17.63</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Chile Service</td>
-        <td>1.20</td>
-        <td>9.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -1853,13 +1832,6 @@ Column definitions are as follows:
         <td>0.35</td>
         <td>2.63</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Colombia Service</td>
-        <td>0.15</td>
-        <td>1.13</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -1881,13 +1853,6 @@ Column definitions are as follows:
         <td>2.85</td>
         <td>21.38</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Egypt Service</td>
-        <td>1.70</td>
-        <td>12.75</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -1909,13 +1874,6 @@ Column definitions are as follows:
         <td>3.80</td>
         <td>28.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>France Service</td>
-        <td>2.30</td>
-        <td>17.25</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -1937,13 +1895,6 @@ Column definitions are as follows:
         <td>3.60</td>
         <td>27.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Germany Service</td>
-        <td>2.15</td>
-        <td>16.13</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -1972,13 +1923,6 @@ Column definitions are as follows:
         <td>0.25</td>
         <td>1.88</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>India Service</td>
-        <td>0.10</td>
-        <td>0.75</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2007,13 +1951,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>8.25</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Indonesia Service</td>
-        <td>0.50</td>
-        <td>3.75</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2035,13 +1972,6 @@ Column definitions are as follows:
         <td>0.95</td>
         <td>7.13</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Israel Service</td>
-        <td>0.50</td>
-        <td>3.75</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2063,13 +1993,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>13.88</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Italy Service</td>
-        <td>1.00</td>
-        <td>7.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2091,13 +2014,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>17.25</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Malaysia Service</td>
-        <td>0.60</td>
-        <td>4.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2119,13 +2035,6 @@ Column definitions are as follows:
         <td>1.15</td>
         <td>8.63</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Mexico Service</td>
-        <td>0.30</td>
-        <td>2.25</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2147,13 +2056,6 @@ Column definitions are as follows:
         <td>4.25</td>
         <td>31.88</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Netherlands Service</td>
-        <td>2.35</td>
-        <td>17.63</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2175,13 +2077,6 @@ Column definitions are as follows:
         <td>1.35</td>
         <td>10.13</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Nigeria Service</td>
-        <td>0.80</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2203,13 +2098,6 @@ Column definitions are as follows:
         <td>0.65</td>
         <td>4.88</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>North America Service</td>
-        <td>0.25</td>
-        <td>1.88</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2231,13 +2119,6 @@ Column definitions are as follows:
         <td>1.60</td>
         <td>12.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Other Service</td>
-        <td>0.40</td>
-        <td>3.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2259,13 +2140,6 @@ Column definitions are as follows:
         <td>1.25</td>
         <td>9.38</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Pakistan Service</td>
-        <td>0.40</td>
-        <td>3.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2287,13 +2161,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>13.88</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Peru Service</td>
-        <td>0.50</td>
-        <td>3.75</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2315,13 +2182,6 @@ Column definitions are as follows:
         <td>0.60</td>
         <td>4.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Rest of Africa Service</td>
-        <td>0.95</td>
-        <td>7.13</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2343,13 +2203,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>14.63</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Rest of Asia Pacific Service</td>
-        <td>0.60</td>
-        <td>4.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2371,13 +2224,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>17.25</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Rest of Central &amp; Eastern Europe Service</td>
-        <td>0.65</td>
-        <td>4.88</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2399,13 +2245,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>14.63</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Rest of Latin America Service</td>
-        <td>1.10</td>
-        <td>8.25</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2427,13 +2266,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>6.75</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Rest of Middle East Service</td>
-        <td>0.60</td>
-        <td>4.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2455,13 +2287,6 @@ Column definitions are as follows:
         <td>1.55</td>
         <td>11.63</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Rest of Western Europe Service</td>
-        <td>1.05</td>
-        <td>7.88</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2483,13 +2308,6 @@ Column definitions are as follows:
         <td>2.15</td>
         <td>16.13</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Russia Service</td>
-        <td>1.05</td>
-        <td>7.88</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2511,13 +2329,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>8.25</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Saudi Arabia Service</td>
-        <td>0.50</td>
-        <td>3.75</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2539,13 +2350,6 @@ Column definitions are as follows:
         <td>1.00</td>
         <td>7.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>South Africa Service</td>
-        <td>0.45</td>
-        <td>3.38</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2567,13 +2371,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>12.38</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Spain Service</td>
-        <td>1.00</td>
-        <td>7.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2595,13 +2392,6 @@ Column definitions are as follows:
         <td>0.30</td>
         <td>2.25</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>Turkey Service</td>
-        <td>0.10</td>
-        <td>0.75</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2623,13 +2413,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>6.75</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>United Arab Emirates Service</td>
-        <td>0.50</td>
-        <td>3.75</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2651,13 +2434,6 @@ Column definitions are as follows:
         <td>1.40</td>
         <td>10.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>7.5</td>
-        <td>United Kingdom Service</td>
-        <td>1.05</td>
-        <td>7.88</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>7.5</td>
@@ -2665,8 +2441,15 @@ Column definitions are as follows:
         <td>0.58</td>
         <td>4.35</td>
     </tr>
+    <tr>
+        <td>LINE</td>
+        <td>1</td>
+        <td>All regions</td>
+        <td>0.15</td>
+        <td>0.15</td>
+    </tr>
     </tbody></table>
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% enddetails %}
 
 ------
@@ -2700,7 +2483,7 @@ Authentication conversations will only be supported on a case-by-case basis and
 **Service Conversations:** User-initiated conversations that are responded to with a non-templated message.
 
 {% alert note %}
-User-initiated conversations that are responded to with a marketing or utility template will be charged as such.
+As of November 1, 2024, service-type conversations are free and will not deduct from purchased credits allotments.
 {% endalert %}
 
 ## Billing region breakdown
diff --git a/_docs/_hidden/pricing/message_credits_theta_d9kw.md b/_docs/_hidden/pricing/message_credits_theta_d9kw.md
index 014dbe1a3be..7a8a5cd3dd0 100644
--- a/_docs/_hidden/pricing/message_credits_theta_d9kw.md
+++ b/_docs/_hidden/pricing/message_credits_theta_d9kw.md
@@ -8,14 +8,14 @@ hide_toc: true
 
 # Message Credits - Theta (Confidential)
 
-> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. We use Message Credits to provide a flexible and transparent experience when taking advantage of Braze messaging channels. You may use the allotment of credits purchased across any of the channels presented in the table on this page.
+> Message Credits is Braze’s cross-channel packaging structure for our native SMS, MMS, and WhatsApp offerings. Message Credits provide a flexible and transparent experience when taking advantage of Braze messaging channels. Credits give you access to any of the channels presented in the table on this page.
 
 {% alert note %}
 Different channels will have different units of measure in reporting.<br><br>
 <b>WhatsApp:</b> Conversations<br>
 <b>SMS:</b> Segments<br>
 <b>MMS:</b> Segments<br><br>
-In other words, credits used for WhatsApp messages will be calculated on conversation initiations, and credits used for both SMS and MMS messages will be calculated on segments sent.
+In other words, credits per WhatsApp messages will be calculated on conversation initiations, and credits per for both SMS and MMS messages will be calculated on segments sent.
 <br><br>
 Lastly, carrier fees are billed separately (in arrears) and are not considered as part of this Message Credits SKU.
 {% endalert %}
@@ -28,8 +28,8 @@ Column definitions are as follows:
 | **Channel Credit Ratio** | Baseline credit amount for each channel |
 | **Destination** | Specific final region, country, or type of message being sent through the Braze platform |
 | **Multiplier** | Scaler to the Channel Credit Ratio, depending on pricing of the specific destination |
-| **Credits Used with 1 Send** | Exact number of Message Credits used to send one message<br> (credits per message = channel credit ratio x destination multiplier) |
-{: .reset-td-br-1 .reset-td-br-2}
+| **Credits per 1 Send** | Exact number of Message Credit to send one message<br> (credits per message = channel credit ratio x destination multiplier) |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ## Credit ratio table for Message Credits - Theta
@@ -45,7 +45,7 @@ Column definitions are as follows:
         <th><b>Channel Credit Ratio</b></th>
         <th><b>Destination</b></th>
         <th><b>Multiplier</b></th>
-        <th class="credits-column"><b>Credits Used with 1 Send</b></th>
+        <th class="credits-column"><b>Credits per 1 Send</b></th>
     </tr>
     <tbody><tr>
         <td>SMS - US / CA</td>
@@ -1769,13 +1769,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Argentina Service</td>
-        <td>0.85</td>
-        <td>8.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1797,13 +1790,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Brazil Service</td>
-        <td>0.80</td>
-        <td>8.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1825,13 +1811,6 @@ Column definitions are as follows:
         <td>2.35</td>
         <td>23.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Chile Service</td>
-        <td>1.20</td>
-        <td>12.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1853,13 +1832,6 @@ Column definitions are as follows:
         <td>0.35</td>
         <td>3.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Colombia Service</td>
-        <td>0.15</td>
-        <td>1.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1881,13 +1853,6 @@ Column definitions are as follows:
         <td>2.85</td>
         <td>28.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Egypt Service</td>
-        <td>1.70</td>
-        <td>17.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1909,13 +1874,6 @@ Column definitions are as follows:
         <td>3.80</td>
         <td>38.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>France Service</td>
-        <td>2.30</td>
-        <td>23.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1937,13 +1895,6 @@ Column definitions are as follows:
         <td>3.60</td>
         <td>36.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Germany Service</td>
-        <td>2.15</td>
-        <td>21.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -1972,13 +1923,6 @@ Column definitions are as follows:
         <td>0.25</td>
         <td>2.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>India Service</td>
-        <td>0.10</td>
-        <td>1.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2007,13 +1951,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>11.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Indonesia Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2035,13 +1972,6 @@ Column definitions are as follows:
         <td>0.95</td>
         <td>9.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Israel Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2063,13 +1993,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>18.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Italy Service</td>
-        <td>1.00</td>
-        <td>10.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2091,13 +2014,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>23.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Malaysia Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2119,13 +2035,6 @@ Column definitions are as follows:
         <td>1.15</td>
         <td>11.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Mexico Service</td>
-        <td>0.30</td>
-        <td>3.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2147,13 +2056,6 @@ Column definitions are as follows:
         <td>4.25</td>
         <td>42.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Netherlands Service</td>
-        <td>2.35</td>
-        <td>23.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2175,13 +2077,6 @@ Column definitions are as follows:
         <td>1.35</td>
         <td>13.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Nigeria Service</td>
-        <td>0.80</td>
-        <td>8.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2203,13 +2098,6 @@ Column definitions are as follows:
         <td>0.65</td>
         <td>6.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>North America Service</td>
-        <td>0.25</td>
-        <td>2.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2231,13 +2119,6 @@ Column definitions are as follows:
         <td>1.60</td>
         <td>16.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Other Service</td>
-        <td>0.40</td>
-        <td>4.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2259,13 +2140,6 @@ Column definitions are as follows:
         <td>1.25</td>
         <td>12.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Pakistan Service</td>
-        <td>0.40</td>
-        <td>4.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2287,13 +2161,6 @@ Column definitions are as follows:
         <td>1.85</td>
         <td>18.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Peru Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2315,13 +2182,6 @@ Column definitions are as follows:
         <td>0.60</td>
         <td>6.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Africa Service</td>
-        <td>0.95</td>
-        <td>9.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2343,13 +2203,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>19.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Asia Pacific Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2371,13 +2224,6 @@ Column definitions are as follows:
         <td>2.30</td>
         <td>23.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Central &amp; Eastern Europe Service</td>
-        <td>0.65</td>
-        <td>6.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2399,13 +2245,6 @@ Column definitions are as follows:
         <td>1.95</td>
         <td>19.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Latin America Service</td>
-        <td>1.10</td>
-        <td>11.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2427,13 +2266,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>9.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Middle East Service</td>
-        <td>0.60</td>
-        <td>6.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2455,13 +2287,6 @@ Column definitions are as follows:
         <td>1.55</td>
         <td>15.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Rest of Western Europe Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2483,13 +2308,6 @@ Column definitions are as follows:
         <td>2.15</td>
         <td>21.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Russia Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2511,13 +2329,6 @@ Column definitions are as follows:
         <td>1.10</td>
         <td>11.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Saudi Arabia Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2539,13 +2350,6 @@ Column definitions are as follows:
         <td>1.00</td>
         <td>10.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>South Africa Service</td>
-        <td>0.45</td>
-        <td>4.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2567,13 +2371,6 @@ Column definitions are as follows:
         <td>1.65</td>
         <td>16.50</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Spain Service</td>
-        <td>1.00</td>
-        <td>10.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2595,13 +2392,6 @@ Column definitions are as follows:
         <td>0.30</td>
         <td>3.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>Turkey Service</td>
-        <td>0.10</td>
-        <td>1.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2623,13 +2413,6 @@ Column definitions are as follows:
         <td>0.90</td>
         <td>9.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>United Arab Emirates Service</td>
-        <td>0.50</td>
-        <td>5.00</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2651,13 +2434,6 @@ Column definitions are as follows:
         <td>1.40</td>
         <td>14.00</td>
     </tr>
-    <tr>
-        <td>WhatsApp</td>
-        <td>10</td>
-        <td>United Kingdom Service</td>
-        <td>1.05</td>
-        <td>10.50</td>
-    </tr>
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
@@ -2665,8 +2441,15 @@ Column definitions are as follows:
         <td>0.58</td>
         <td>5.80</td>
     </tr>
+    <tr>
+        <td>LINE</td>
+        <td>1</td>
+        <td>All regions</td>
+        <td>0.15</td>
+        <td>0.15</td>
+    </tr>
     </tbody></table>
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% enddetails %}
 
 ------
@@ -2700,7 +2483,7 @@ Authentication conversations will only be supported on a case-by-case basis and
 **Service Conversations:** User-initiated conversations that are responded to with a non-templated message.
 
 {% alert note %}
-User-initiated conversations that are responded to with a marketing or utility template will be charged as such.
+As of November 1, 2024, service-type conversations are free and will not deduct from purchased credits allotments.
 {% endalert %}
 
 ## Billing region breakdown
diff --git a/_docs/_hidden/pricing/whatsapp_pricing.md b/_docs/_hidden/pricing/whatsapp_pricing.md
new file mode 100644
index 00000000000..82a48fa1d93
--- /dev/null
+++ b/_docs/_hidden/pricing/whatsapp_pricing.md
@@ -0,0 +1,90 @@
+---
+nav_title: WhatsApp Pricing Updates
+permalink: "/whatsapp_pricing_updates/"
+hidden: true
+noindex: true
+hide_toc: true
+---
+
+# WhatsApp pricing updates
+
+Pricing changes from August 2024—November 2024
+
+*Last updated October 29th, 2024*
+
+## Utility conversations 
+
+On August 1, 2024, Meta lowered rates on utility conversations to encourage brands to facilitate more post-purchase customer journeys on the platform. We have passed through these cost reductions to your Message Credits or WhatsApp Credits entitlements in equal proportions. This update went into effect on the same day as Meta’s (August 1). 
+
+#### What are utility conversations? 
+
+Utility conversations enable you to follow-up on specific customer actions or requests. Examples include opt-in confirmation, order updates and confirmations, account updates or alerts (e.g. payment reminders), or feedback surveys.
+
+#### How can you benefit from this update? 
+
+We encourage you to take advantage of this update by using WhatsApp for transactional messaging. You can also consider shifting some of your transactional SMS messages to WhatsApp if it makes sense for your brand (based on your audience reach and engagement on each channel). For example, this may be a good option for customers in Asia, Latin America, and Europe where WhatsApp is a heavily used channel. 
+
+## Marketing conversations
+
+On October 1, 2024, Meta decreased pricing on United Kingdom marketing conversations by 25% to reflect current demand. We have passed through these cost reductions to your Message Credits or WhatsApp Credits entitlements in equal proportions. This update went into effect on the same day as Meta’s (October 1).
+
+#### What are marketing conversations? 
+
+Marketing conversations enable you to achieve a wide range of goals, from generating awareness to driving sales and retargeting customers. Examples include new product announcements, targeted promotions/offers, and cart abandonment campaigns.
+
+## Service conversations
+
+On November 1, 2024, all service conversations are free of charge. Service conversations will no longer consume Message Credits or WhatsApp Credits entitlements. This change will go into effect on the same day as Meta’s (November 1).
+
+#### What are service conversations? 
+
+Service conversations enable you to respond to customer inquiries. This includes conversations started by an end-user where the brand replies with a [response message]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create#response-messages) instead of a template message.
+
+#### How can you benefit from this update? 
+
+Some conversations that were previously charged as "service" will now be free. These include: 
+
+- [Unrecognized response campaigns]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/message_processing/user_messages#unrecognized-responses) where an end-user sends a message that is unrecognized and the brand replies with a generic message using [response messaging]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create#response-messages). For example, an end-user sends a message without a keyword and the brand responds with “We don’t recognize your message, please reach out to customer support."
+- Conversations that start when an end-user messages the brand a promoted keyword and the brand replies using a [response message]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create#response-messages). Common examples are opting into WhatsApp messaging or participating in a specific promotion.
+
+<br>
+
+Detailed information on the utility conversations decrease below:
+
+| Billing region                             | Utility percent decrease |
+|--------------------------------------------|--------------------------|
+| Argentina                                  | 16.7%                    |
+| Brazil                                     | 77.1%                    |
+| Chile                                      | 65.9%                    |
+| Colombia                                   | 97.6%                    |
+| Egypt                                      | 92.4%                    |
+| France                                     | 60.9%                    |
+| Germany                                    | 35.5%                    |
+| India                                       | 66.7%                    |
+| Indonesia                                  | 0.0%                     |
+| Israel                                     | 71.8%                    |
+| Italy                                      | 28.6%                    |
+| Malaysia                                   | 30.0%                    |
+| Mexico                                     | 62.4%                    |
+| Netherlands                                | 37.5%                    |
+| Nigeria                                    | 79.0%                    |
+| North America                              | 73.3%                    |
+| Other                                      | 77.2%                    |
+| Pakistan                                   | 78.7%                    |
+| Peru                                       | 52.3%                    |
+| Rest of Africa                             | 61.9%                    |
+| Rest of Asia Pacific                       | 66.7%                    |
+| Rest of Central & Eastern Europe          | 43.0%                    |
+| Rest of Latin America                      | 77.1%                    |
+| Rest of Middle East                        | 20.7%                    |
+| Rest of Western Europe                     | 28.6%                    |
+| Russia                                     | 16.1%                    |
+| Saudi Arabia                               | 54.4%                    |
+| South Africa                               | 62.0%                    |
+| Spain                                      | 47.4%                    |
+| Turkey                                     | 43.0%                    |
+| United Arab Emirates                       | 20.7%                    |
+| United Kingdom                             | 44.7%                    |
+{: .reset-td-br-1 .reset-td-br-2 }
+
+To get a better understanding of how you can take advantage of these updates, reach out to your customer success manager. 
\ No newline at end of file
diff --git a/_docs/_hidden/private_betas/canvas_triggered_iams.md b/_docs/_hidden/private_betas/canvas_triggered_iams.md
index 0fd09c8b93f..67d680e95ae 100644
--- a/_docs/_hidden/private_betas/canvas_triggered_iams.md
+++ b/_docs/_hidden/private_betas/canvas_triggered_iams.md
@@ -33,7 +33,7 @@ In the in-app message composer, you can choose when the in-app message will expi
 |---|---|---|
 | **A duration after the step is available** | Sets the in-app message to expire relative to when the step becomes available to the user. | An in-app message with a two-day expiration would become available after the step's delay elapses and audience options are checked. It would then be available for 2 days (48 hours) and during those two days, users may see the in-app message if they open the app. |
 | **On a specific date and time** | Select a specific date and time when the in-app message will be no longer available. | If you have a sale that ends on November 30, 2024, select this option so that users no longer see the associated in-app message when the sale ends. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Use cases
 
@@ -162,7 +162,11 @@ If you make changes to the in-app message priority in **Send Settings** of a dra
 
 ## Advancement behavior
 
-Message components automatically advance all users who enter the step. Note that it doesn't wait for the in-app message to trigger or display. There is no requirement to specify message advancement behavior, making configuring the overall step simpler. If you want to implement the **Advance when message sent** option, add a separate [audience path]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/audience_paths/) to filter users that didn't receive the previous step.
+Message components automatically advance all users who enter the step. Note that it doesn't wait for the in-app message to trigger or display. There is no requirement to specify message advancement behavior, making configuring the overall step simpler.
+
+When a user enters an in-app message step, they advance immediately out of it instead of being held for the expiration window. In this case, having a Delay step in your user journey can be helpful.
+
+If you want to implement the **Advance when message sent** option, add a separate [audience path]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/audience_paths/) to filter users that didn't receive the previous step.
 
 {% details Original Canvas editor %}
 
@@ -190,7 +194,7 @@ Steps with an in-app message and another channel have the following advancement
 |---|---|---|
 | Advance When Message Sent | Users must be sent an email, webhook, or push notification, or view the in-app message to advance to subsequent steps in the Canvas.  <br> <br>  If the in-app message expires and the user hasn't been sent the email, webhook, or push, or hasn't viewed the in-app message, they will exit the Canvas and will not advance to subsequent steps. |
 | Immediately Advance Audience | Everyone in the step's audience advances to the next steps after the delay elapses, whether they have seen the noted message or not. <br> <br> Users must match the step's segment and filter criteria to advance to the next steps. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![]({% image_buster /assets/img/push-advancement-behavior.png %})
 
diff --git a/_docs/_hidden/private_betas/create_banner_card.md b/_docs/_hidden/private_betas/create_banner_card.md
new file mode 100644
index 00000000000..2270064238a
--- /dev/null
+++ b/_docs/_hidden/private_betas/create_banner_card.md
@@ -0,0 +1,126 @@
+---
+nav_title: Creating a Banner Card
+article_title: Creating a Banner Card
+permalink: "/create_banner_card/"
+description: "This reference article covers how to create and send Banner Cards using Braze campaigns."
+page_type: reference
+---
+
+# Creating a Banner Card
+
+> This article covers how to create a Banner Card in Braze when you build campaigns.
+
+Similar to [Content Cards]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/about/), Banner Cards are embedded directly in your app or website so that you can engage users with an experience that feels natural. They’re a quick and seamless solution to create personalized messaging for your users all while extending the reach of other channels (such as email or push notifications). 
+
+Banner Cards are great for:
+
+- Highlighting featured content
+- Notifying users about upcoming events
+- Sharing updates on loyalty programs
+
+Because Banner Cards personalize each time a user starts a new session and can be configured to never expire, they’re a helpful tool to add to your engagement strategy.
+
+{% alert important %}
+Banner Cards are currently in early access. Contact your Braze account manager if you’re interested in participating in this early access.
+{% endalert %}
+
+## Prerequisite: Determine placement
+
+Before creating a Banner Card, you must designate areas in your app where you want to display the Banner Card. This is also referred to as the placement. After you create a placement, you can select it when creating your Banner Card campaign. If you already have a placement, skip to [step 1](#step-1-create-your-campaign).
+
+To create a placement:
+
+1. Go to **Settings** > **Banner Card Placements**.
+2. Give your Banner Card placement a name.
+3. (Optional) Add a description to explain where this Banner Card is intended to be placed.
+4. Enter a unique placement ID. Work with your developer team to define this ID, because they will need to use it during the integration. Avoid editing your placement ID after launch, as this can break the integration with your app or website.
+5. Select **Save**.
+
+Each placement can be used in up to 10 campaigns. 
+
+{% alert important %}
+Placement IDs are unique per workspace.
+{% endalert %}
+
+## Step 1: Create your campaign
+
+After determining your Banner Card placement, it’s time to build your campaign.
+
+1. Go to **Messaging** > **Campaigns** and select **Create Campaign**.
+2. Select **Banner Card**.
+3. Name your campaign something clear and meaningful.
+4. Add teams and tags as needed. Tags make your campaigns easier to find and build reports out of. For example, when using the Report Builder, you can filter by the relevant tags.
+5. Select a [placement](#prerequisite-determine-placement) to associate with your campaign. This is where the Banner Card will appear in your app or site.
+6. Add and name as many variants as you like for your campaign. You can choose different message types and layouts for each added variant. For more information on variants, refer to [Multivariate and A/B testing]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/).
+
+## Step 2: Compose a Banner Card
+
+To edit the details of your message’s content:
+
+1. Select **Edit message**. The composer will open.
+2. Choose a row style that fits your message. Drag and drop a row into the canvas area.
+3. Drag and drop blocks into the row to build your message.
+4. Define the [style](#styles) of your message.
+
+### Styles
+
+Select **Style** to adjust the settings to apply to all blocks in the message.
+
+![Style panel of the Banner Card composer.]({% image_buster /assets/img/banner_cards/banner_card_styles.png %})
+
+Here, you can provide custom styling such as background properties, border settings, and defaults to your Banner Cards. Styles applied here can be overridden for a specific block or row. To override styles, select the specific block or row to view its properties and make changes.
+
+### On-click behavior
+
+When your customer clicks on a link in the Banner Card, you can either navigate them deeper into your app or redirect them to another webpage.
+
+You can also choose to log a custom attribute or custom event. This will update your customer’s profile with custom data when they click the Banner Card.
+
+## Step 3: Build the remainder of your campaign
+
+Next, build the remainder of your campaign. Refer to the next sections for more details on how to best use our tools to build Banner Cards.
+
+### Choose a campaign duration
+
+Select the start date and time for the Banner Card campaign. 
+
+By default, Banner Cards last indefinitely. If desired, select **End Time** to specify an end date and time.
+
+### Choose users to target
+
+Next, target users by choosing segments or filters to narrow down your audience. You’ll automatically be given a snapshot of what that approximate segment population looks like right now. Keep in mind that exact segment membership is always calculated just before the message is sent.
+
+### Choose conversion events
+
+Braze allows you to track how often users perform specific actions, and conversion events, after receiving a campaign. You can allow up to a 30-day window during which a conversion will be counted if the user takes the specified action.
+
+## Step 4: Test and deploy
+
+After building your campaign, test and review it to make sure your campaign works as expected. Then, you’re ready to launch your Banner Card campaign!
+
+## Things to know
+
+### Banner Cards expiration
+
+By default, Banner Cards do not have an expiration date, but you can add an optional end date.
+
+### Placement management
+
+Placements are unique per workspace, and each placement can be used in up to 10 campaigns.
+
+Placement IDs must be unique to a workspace, and should not be edited after launch. Work with your developer team to define this ID, because they will need to use it during the integration. 
+
+### Analytics
+
+The following table defines key Banner Card metrics.
+
+| Metric               | Definition                                                                                                                                                       |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Total Impressions**     | Total Impressions is the number of times a Banner Card is loaded and appears on a user’s screen regardless of prior interaction.                               |
+| **Unique Impressions**    | _Unique Impressions_ is the total number of users who received and viewed a given message in a day; each user is only counted once.                              |
+| **Total Clicks**         | _Total Clicks_ is the total number of clicks within a Banner Card, regardless of whether the same user clicks multiple times.                                     |
+| **Unique Clicks**        | _Unique Clicks_ is the distinct number of recipients who have clicked within a Banner Card at least once and is measured by `dispatch_id`; each user is only counted once. |
+| **Primary Conversions**  | Includes both the count and rate of conversions for the [primary conversion event]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/conversion_events/#primary-conversion-event). The primary conversion event is determined when you build the campaign. {::nomarkdown}<ul><li><i>Conversions</i> are the number of times a user performs an event after clicking on the Banner Card. Each user is only counted once.</li><li><i>Conversion Rate</i> is the percentage of times the conversion event occurred compared to all recipients of a message. <br> <i>(Conversions) / (Unique Impressions)</i></li></ul>{:/} |
+{: .reset-td-br-1 .reset-td-br-2}
+
+For a full list of metrics, definitions, and calculations, refer to our [Report Metrics Glossary]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics/).
\ No newline at end of file
diff --git a/_docs/_hidden/private_betas/csv_events.md b/_docs/_hidden/private_betas/csv_events.md
index ba0155f1f5c..1927e860623 100644
--- a/_docs/_hidden/private_betas/csv_events.md
+++ b/_docs/_hidden/private_betas/csv_events.md
@@ -54,7 +54,7 @@ If you are uploading or updating user profiles that are alias only, you must hav
 | --- | --- | --- | --- | --- |
 | 182736485 | my_alt_identifier | Smith | smith@user.com | TRUE |
 | 182736486 | my_alt_identifier | Nguyen | nguyen@user.com | FALSE |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 When you provide both a `user_alias_name` and `user_alias_label` in your import, Braze will update any existing user with the same `user_alias_name` and `user_alias_label`. If a user isn't found, Braze will create a newly identified user with that `user_alias_name` set.
 
@@ -111,7 +111,7 @@ When importing customer data as attributes, the column headers you use must exac
 | `date_of_first_session` <br><br> `date_of_last_session`| String | May be passed in one of the following ISO-8601 formats: {::nomarkdown} <ul> <li> "YYYY-MM-DD" </li> <li> "YYYY-MM-DDTHH:MM:SS+00:00" </li> <li> "YYYY-MM-DDTHH:MM:SSZ" </li> <li> "YYYY-MM-DDTHH:MM:SS" (for example, 2019-11-20T18:38:57) </li> </ul> {:/} | No |
 | `subscription_group_id` | String | The `id` of your subscription group. This identifier can be found on the subscription group page of your dashboard. | No |
 | `subscription_state` | String | The subscription state for the subscription group specified by `subscription_group_id`. Allowed values are `unsubscribed` (not in subscription group) or `subscribed` (in subscription group). | No, but strongly recommended if `subscription_group_id` is used. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ##### About external IDs
 
@@ -133,7 +133,7 @@ The following data types are accepted in user import:
 | Number | Integer or float with no spaces or commas, floats must use a period (.) as the decimal separator |
 | String | Can contain commas as long as there are double quotation marks surrounding the column value |
 | Blank | Blank values will not overwrite existing values on the user profile, and you do not need to include all existing user attributes in your CSV file |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 Arrays and push tokens are not supported in user import. Especially for arrays, commas in your CSV file will be interpreted as a column separator, so any commas in values will cause errors parsing the file. <br>To upload these kinds of values, use the [`/users/track` endpoint]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) or [Cloud Data Ingestion]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/).
@@ -210,7 +210,7 @@ Custom events may have event properties. For example, the custom event rented_mo
 | `name`                                  | String    | A custom event of your users.                                                                                                                                                                                           | Yes                                                                                             |
 | `time`                                  | String    | The time of the event. May be passed in one of the following ISO-8601 formats: {::nomarkdown} <ul> <li> "YYYY-MM-DD" </li> <li> "YYYY-MM-DDTHH:MM:SS+00:00" </li> <li> "YYYY-MM-DDTHH:MM:SSZ" </li> <li> "YYYY-MM-DDTHH:MM:SS" (for example, 2019-11-20T18:38:57) </li> </ul> {:/} | Yes                                                                                             |
 | `<event name>.properties.<property name>` | Multiple  | An event property associated with a custom event. An example is `rented_movie.properties.title`                                                                                                                        | No                                                                                              |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 While external_id itself is not mandatory, you must include one of the following fields: <br>- `external_id`: A unique user identifier for your customer <br>- `braze_id`: A unique user identifier pulled for existing Braze users <br>- `user_alias_name`: A unique user identifier for an anonymous user
diff --git a/_docs/_hidden/private_betas/dashboard_builder.md b/_docs/_hidden/private_betas/dashboard_builder.md
index 1db338edf08..4a20a5541e5 100644
--- a/_docs/_hidden/private_betas/dashboard_builder.md
+++ b/_docs/_hidden/private_betas/dashboard_builder.md
@@ -46,7 +46,7 @@ Touches include `Email Click`, `Content Card Click`, `In-App Message Click`, `SM
 | Purchases per Product | A count of all purchases grouped by product. |
 | Revenue by Channel | Sum of all campaign and Canvas revenue events with a qualifying last-touch event, grouped by channel. | 
 | Revenue Time Series | Sum of all campaign and Canvas revenue events with a qualifying last-touch event, grouped by day in UTC. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Devices and carriers
 
@@ -56,7 +56,7 @@ Touches include `Email Click`, `Content Card Click`, `In-App Message Click`, `SM
 | Device Model | Count of users in the selected date range who opened a push notification, grouped by device model. |
 | Device Operating System | Count of users in the selected date range who opened a push notification, grouped by device operating system. |
 | Device Screen Size | Count of users in the selected date range who opened a push notification, grouped by device screen resolution (size). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Creating a customized dashboard
 
diff --git a/_docs/_hidden/private_betas/get_app_group_apps.md b/_docs/_hidden/private_betas/get_app_group_apps.md
index 116bbd8412f..3c58289d2b4 100644
--- a/_docs/_hidden/private_betas/get_app_group_apps.md
+++ b/_docs/_hidden/private_betas/get_app_group_apps.md
@@ -59,6 +59,6 @@ The following table lists possible returned errors and their associated troubles
 | --- | --- |
 | `401: Unauthorized` | API key does not have the required permissions. Make sure your API key has `apps.get` permissions. |
 | `403: Forbidden` | The feature flipper is not on for this company. Contact your customer success manager for assistance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
diff --git a/_docs/_hidden/private_betas/get_campaign_url_info.md b/_docs/_hidden/private_betas/get_campaign_url_info.md
index 285035bed03..cdfb4078cc2 100644
--- a/_docs/_hidden/private_betas/get_campaign_url_info.md
+++ b/_docs/_hidden/private_betas/get_campaign_url_info.md
@@ -31,7 +31,7 @@ description: "This article outlines details about the List link alias Braze endp
 | `campaign_id`  | Required | String | See [campaign API identifier]({{site.baseurl}}/api/identifier_types/#campaign-api-identifier).|
 | `message_variation_id `  |  Required | String | Message variant API identifier. You can find this on the campaign details page for a campaign, under the **API Identifier** section. |
 | `includes_link_id` | Optional | String | A specific link identifier (as assigned by Braze) or `null`. This is used to filter the results by a specific `link_id`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Example request
 ```
@@ -67,7 +67,7 @@ The following table lists possible returned errors and their associated troubles
 | --- | --- |
 | `Missing/Invalid Campaign ID` | The campaign API ID must be an API identifier. You can find this using the [Export campaigns list endpoint]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaigns/) or by logging into the dashboard. |
 | `Missing/Invalid Message Variant ID` | The message variant API ID must be an API identifier. You can find this using the [Export campaign details endpoint]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/) or by logging into the dashboard. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 {% endapi %}
diff --git a/_docs/_hidden/private_betas/get_canvas_url_info.md b/_docs/_hidden/private_betas/get_canvas_url_info.md
index f2e2a86b1b8..50cf8620d95 100644
--- a/_docs/_hidden/private_betas/get_canvas_url_info.md
+++ b/_docs/_hidden/private_betas/get_canvas_url_info.md
@@ -68,6 +68,6 @@ The following table lists possible returned errors and their associated troubles
 | --- | --- |
 | `Missing/Invalid Canvas ID` | The Canvas API ID must be an API identifier. You can find this using the [Export Canvas list endpoint]({{site.baseurl}}/api/endpoints/export/canvas/get_canvases/) or by logging into the dashboard. |
 | `Missing/Invalid Message Variant ID` | The message variant API ID must be an API identifier. You can find this using the [Export Canvas details endpoint]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/) or by logging into the dashboard. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
diff --git a/_docs/_hidden/private_betas/idle_campaigns.md b/_docs/_hidden/private_betas/idle_campaigns.md
index d1f139c2670..32281f26b39 100644
--- a/_docs/_hidden/private_betas/idle_campaigns.md
+++ b/_docs/_hidden/private_betas/idle_campaigns.md
@@ -35,7 +35,7 @@ Reference this table for how to keep an idle campaign active:
 | Campaigns that are scheduled one-time sends, and it’s seven days past the send date                 | Schedule a future send                            |
 | Campaigns that are scheduled or action-based, have end dates, and it’s seven days past the end date | Extend the end date                               |
 | Campaigns without an end date that have not sent messages in one year                                | Send one message or make any edit to the campaign |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Idle Canvases
 
@@ -56,7 +56,7 @@ Reference this table for how to keep an idle Canvas active:
 | Canvases that are scheduled one-time sends, and it’s seven days and maximum duration past the send date                 | Schedule a future send                          |
 | Canvases that are scheduled or action-based, have end dates, and it’s seven days and maximum duration past the end date | Extend the end date                             |
 | Canvases without end dates that have not sent messages in one year                                                      | Send one message or make any edit to the Canvas |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Frequently asked questions
 
diff --git a/_docs/_hidden/private_betas/multiple_stores.md b/_docs/_hidden/private_betas/multiple_stores.md
index 42c35859897..4e9b5d5615b 100644
--- a/_docs/_hidden/private_betas/multiple_stores.md
+++ b/_docs/_hidden/private_betas/multiple_stores.md
@@ -19,7 +19,7 @@ Support for multiple Shopify stores is available in beta, which may contain bugs
 | Create [email subscription group]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions#create-a-group) for each store | After the Email Subscription Group is created, you will designate it to the specific store during the “[Collect email or SMS subscribers]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/#step-5-collect-email-or-sms-subscribers)” step of the setup flow.<br><br>This is required for you to track which store’s Email subscription group your users belong to for compliance purposes. |
 | Audit and update segments, campaigns, and Canvas using Shopify attributes | The custom attributes collected from multiple stores will be in the format of a nested object, which differs from the current structure used in the overall Shopify integration, which is formatted as a string value. As a result, you'll need to update all segments, campaigns, or Canvas to the new format after connecting multiple stores to use the “Nested Custom Attribute” filter or update the “Change Custom Attribute” trigger event.<br><br>If you are not using any of the attributes today, you can ignore this. |
 | Audit and update Shopify alias | The `shopify_customer_id` alias will be migrated to {% raw %}`shopify_customer_id_{{storename}}`{% endraw %} after you connect more than one store. Make sure you are updating any internal systems to use the new alias. The legacy alias, `shopify_customer_id`, will be deprecated. If you are not using the alias today, you can ignore this. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 With Braze’s multiple-store support, you can:
diff --git a/_docs/_hidden/private_betas/post_duplicate_canvas.md b/_docs/_hidden/private_betas/post_duplicate_canvas.md
index ea8192f5c2d..7998c91d3fa 100644
--- a/_docs/_hidden/private_betas/post_duplicate_canvas.md
+++ b/_docs/_hidden/private_betas/post_duplicate_canvas.md
@@ -51,7 +51,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 |`name`| Required | String | The name of the resulting Canvas. |
 |`description`| Optional | String | The description field for the resulting Canvas. |
 |`tag_names` | Optional | String | The tags for the resulting Canvas. These must be existing tags. If you add new tags in the request, they will overwrite any tags that were on the original Canvas. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Response
 
diff --git a/_docs/_hidden/private_betas/post_track_users_bulk.md b/_docs/_hidden/private_betas/post_track_users_bulk.md
new file mode 100644
index 00000000000..d0f730ed1e6
--- /dev/null
+++ b/_docs/_hidden/private_betas/post_track_users_bulk.md
@@ -0,0 +1,264 @@
+---
+nav_title: "POST: Track Users (Bulk)"
+layout: api_page
+page_type: reference
+hidden: true
+permalink: /track_users_bulk/
+description: "This article outlines details about the Track users (bulk) endpoint."
+---
+
+{% api %}
+# Track users (bulk)
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %} 
+/users/track/bulk
+{% endapimethod %}
+
+> Use this endpoint to record custom events and purchases and update user profile attributes in bulk.
+
+{% alert important %}
+This endpoint is currently in beta. Contact your Braze account manager if you're interested in participating in the beta.
+{% endalert %}
+
+## When to use this endpoint
+
+Similar to the [POST: Track users endpoint]({{site.baseurl}}/api/endpoints/user_data/post_user_track/#prerequisites), you can use this endpoint to update user profiles. However, this endpoint is better suited for making bulk updates:
+
+- **Larger requests:** This endpoint allows for 10,000 users per request, meaning that you have to make fewer requests to achieve your bulk update needs.
+- **Prioritization:** During peak traffic conditions, requests from `/users/track` will be prioritized over requests from `/users/track/bulk`. Using both endpoints provides you with more control over data ingestion.
+
+Note that user updates to this endpoint will not trigger any action-based campaigns or action-based Canvases, trigger any exception events, or track towards conversion metrics. User updates to this endpoint are available for segmentation and personalization.
+
+Consider using this endpoint when you're backfilling many user profiles during onboarding or syncing large amounts of user profiles as part of a daily sync.
+
+## Prerequisites
+
+To use this endpoint, you’ll need an API key with the `users.track.bulk` permission.
+
+If you're using the API for server-to-server calls, you may need to allowlist the endpoint (for example, `rest.iad-01.braze.com`) if you're behind a firewall. Refer to the [endpoints per instance]({{site.baseurl}}/api/basics#endpoints) for more information.
+
+## Rate limit
+
+We apply a base speed limit of 5 requests per second to this endpoint for all customers.
+
+Each `/users/sync/bulk` request has a payload limit of 4&nbsp;MB, and may contain up to 10,000 event, attribute, or purchase objects.
+
+Each object (event, attribute, and purchase arrays) can update one user each, meaning up to 10,000 different users can be updated in a single request. A single user profile can be updated with up to 100 objects in a single request.
+
+{% alert note %}
+If you need your rate limit increased, reach out to your customer success manager.
+{% endalert %}
+
+
+## Request body
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+  "attributes": (optional, array of attributes object),
+  "events": (optional, array of event object),
+  "purchases": (optional, array of purchase object),
+}
+```
+
+### Request parameters
+
+{% alert important %}
+For each request component listed in the following table, one of `external_id`, `user_alias`, `braze_id`, `email`, or `phone` is required.
+{% endalert %}
+
+| Parameter | Required | Data Type | Description |
+| --------- | ---------| --------- | ----------- |
+| `attributes` | Optional | Array of attributes objects | See [user attributes object]({{site.baseurl}}/api/objects_filters/user_attributes_object/) |
+| `events` | Optional | Array of event objects | See [events object]({{site.baseurl}}/api/objects_filters/event_object/) |
+| `purchases` | Optional | Array of purchase objects | See [purchases object]({{site.baseurl}}/api/objects_filters/purchase_object/) |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
+
+## Example requests
+
+### Bulk update 10,000 user profiles in one request
+
+You can update up to 10,000 user profiles. Here’s a truncated example where the request consists of 10,000 attribute objects:
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track/bulk' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+    "attributes": [
+        {
+            "external_id": "user1",
+            "string_attribute": "fruit",
+            "boolean_attribute_1": true,
+            "integer_attribute": 25,
+            "array_attribute": [
+                "banana",
+                "apple"
+            ]
+        },
+        {
+            "external_id": "user2",
+            "string_attribute": "vegetables",
+            "boolean_attribute_1": false,
+            "integer_attribute": 25,
+            "array_attribute": [
+                "broccoli",
+                "asparagus",	
+            ]
+        },
+
+...
+
+        {
+            "external_id": "user10000",
+            "string_attribute": "nuts",
+            "boolean_attribute_1": true,
+            "integer_attribute": 25,
+            "array_attribute": [
+                "hazelnut",
+                "pistachio"
+            ]
+        }
+    ]
+}'
+```
+
+Here’s an example where the request consists of both attribute and event objects:
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track/bulk' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+    "attributes": [
+        {
+            "external_id": "user1",
+            "string_attribute": "fruit",
+            "boolean_attribute_1": true,
+            "integer_attribute": 25,
+            "array_attribute": [
+                "banana",
+                "apple"
+            ]
+        }
+    ],
+    "events": [
+        {
+            "external_id": "user2",
+            "app_id": "your_app_identifier",
+            "name": "rented_movie",
+            "time": "2022-12-06T19:20:45+01:00",
+            "properties": {
+                "release": {
+                    "studio": "FilmStudio",
+                    "year": "2022"
+                },
+                "cast": [
+                    {
+                        "name": "Actor1"
+                    },
+                    {
+                        "name": "Actor2"
+                    }
+                ]
+            }
+        },
+...
+        {
+            "external_id": "user10000",
+            "app_id": "your_app_identifier",
+            "name": "rented_movie",
+            "time": "2023-09-16T08:00:00+10:00",
+            "properties": {
+                "release": {
+                    "studio": "FilmStudio",
+                    "year": "1988"
+                },
+                "cast": [
+                    {
+                        "name": "Actor1"
+                    },
+                    {
+                        "name": "Actor2"
+                    }
+                ]
+            }
+        }
+    ]
+}'
+```
+
+## Responses
+
+### Successful messages
+
+Successful messages will be met with the following response:
+
+```json
+{
+  "message": "success",
+  "attributes_processed": (optional, integer), if attributes are included in the request, this will return an integer of the number of external_ids with attributes that were queued to be processed,
+  "events_processed": (optional, integer), if events are included in the request, this will return an integer of the number of events that were queued to be processed,
+  "purchases_processed": (optional, integer), if purchases are included in the request, this will return an integer of the number of purchases that were queued to be processed,
+}
+```
+
+#### Successful message with non-fatal errors
+
+If your message is successful but has non-fatal errors, such as one invalid event object out of a long list of events, then you will receive the following response:
+
+```json
+{
+  "message": "success",
+  "errors": [
+    {
+      <minor error message>
+    }
+  ]
+}
+```
+
+### Message with fatal errors
+
+If your message has a fatal error, you will receive the following response:
+
+```json
+{
+  "message": <fatal error message>,
+  "errors": [
+    {
+      <fatal error message>
+    }
+  ]
+}
+```
+
+#### Fatal error response codes
+
+For status codes and associated error messages that will be returned if your request encounters a fatal error, refer to [Fatal errors and responses]({{site.baseurl}}/api/errors/#fatal-errors).
+
+If you receive the error `provided external_id is blacklisted and disallowed`, your request may have included a “dummy user.” For more information, refer to [Spam blocking]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_archival/#spam-blocking).
+
+## Frequently asked questions
+
+### Should I use this endpoint or regular `/users/track`?
+
+We recommend using both.
+
+For large user profile backfills and syncs where triggering for action-based campaigns and Canvases, conversion tracking, and exception events are not needed, use `/users/track/bulk`. 
+
+For real-time use cases, use the `/users/track` endpoint.
+
+### What identifiers can I use in /users/track/bulk?
+
+One of `external_id`, `braze_id`, `user_alias`, `email`, or `phone` is required. For more examples, refer to our documentation for [user attributes object]({{site.baseurl}}/api/objects_filters/user_attributes_object/), [events object]({{site.baseurl}}/api/objects_filters/event_object/), or [purchases object]({{site.baseurl}}/api/objects_filters/purchase_object/). 
+
+### Can I include attributes, events, and purchases in 1 request?
+
+Yes. You cam construct your request with any amount of attributes, events, and purchase objects up to 10,000 objects per request.
+
+
+{% endapi %}
diff --git a/_docs/_hidden/private_betas/post_user_track_synchronous.md b/_docs/_hidden/private_betas/post_user_track_synchronous.md
index 919f2468f4a..6b3231d283c 100644
--- a/_docs/_hidden/private_betas/post_user_track_synchronous.md
+++ b/_docs/_hidden/private_betas/post_user_track_synchronous.md
@@ -66,7 +66,7 @@ For each request component listed in the following table, one of `external_id`,
 | `attributes` | Optional | One attributes object | See [user attributes object]({{site.baseurl}}/api/objects_filters/user_attributes_object/) |
 | `events` | Optional | One event object | See [events object]({{site.baseurl}}/api/objects_filters/event_object/) |
 | `purchases` | Optional | One purchase object | See [purchases object]({{site.baseurl}}/api/objects_filters/purchase_object/) |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Responses
 
diff --git a/_docs/_hidden/private_betas/rate_limiting.md b/_docs/_hidden/private_betas/rate_limiting.md
new file mode 100644
index 00000000000..e1b4b7c295d
--- /dev/null
+++ b/_docs/_hidden/private_betas/rate_limiting.md
@@ -0,0 +1,113 @@
+---
+article_title: Rate Limiting for Campaigns and Canvases
+permalink: /rate_limiting/
+page_type: reference
+description: "This reference article describes the previous Braze delivery speed rate limiting behavior."
+---
+
+# Rate limiting
+
+> This article describes the previous Braze delivery speed rate limiting behavior. The updated rate limiting behavior is described [here]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting#rate-limiting).
+
+Braze allows you to control marketing pressure by rate limiting your campaigns and Canvases, regulating the amount of outgoing traffic from your platform. You can implement two different types of rate limiting for your campaigns:
+
+1. **Delivery speed rate limiting** takes into consideration the bandwidth of your servers.
+2. **User-centric rate limiting** focuses on providing the best experience for the user. 
+
+For more information, refer to [About rate limiting]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#about-rate-limiting).
+
+## About delivery speed rate limiting
+
+If you anticipate large campaigns driving a spike in user activity and overloading your servers, you can specify a per-minute rate limit for sending messages&#8212;this means Braze will send no more than your set rate limit within a minute. 
+
+When targeting users during campaign creation, you can navigate to either **Target Audiences** (for campaigns) or **Send Settings** (for Canvas) to select a message delivery speed rate limit (in various increments from as low as 10 to as high as 500,000 messages per minute). Note that non-rate-limited campaigns may exceed these delivery limits.
+
+For instance, if you're trying to send 75,000 messages with a 10,000-per-minute rate limit, the delivery will be spread out over eight minutes. Your campaign will deliver no more than 10,000 messages for each of the first seven minutes, and 5,000 messages over the last minute. 
+
+### Considerations
+
+Messages sent using a rate limit won’t have the rate limit setting (such as 10,000 per minute) evenly sent out over 60 seconds. Instead, Braze makes sure no more than 10,000 messages are sent per minute (this could mean a higher percentage of the 10,000 messages are sent within the first half minute versus the last half minute). 
+
+Be wary of delaying time-sensitive messages with this form of rate limiting. If the message’s audience contains 30 million users but we set the rate limit to 10,000 per minute, a large portion of your user base won’t receive the message until the following day. 
+
+Be aware that messages will be aborted if they’re delayed 72 hours or more due to a low rate limit. The user who created the campaign will receive alerts in the dashboard and via email if the rate limit is too low.
+
+## Campaigns delivery speed rate limiting
+
+### Single-channel campaigns
+
+When sending a single-channel campaign with a delivery speed rate limit, the rate limit is applied for all messages together. For example, an email campaign with a rate limit of 10,000 messages per minute will send a maximum of 10,000 total messages per minute.
+
+
+| Maximum emails sent per minute | Maximum total messages sent per minute |
+|--------------------------------|----------------------------------------|
+| 10,000                         | 10,000                                 |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+
+### Multi-channel campaigns
+
+When sending a multi-channel campaign with a speed rate limit, each channel is sent independently of the others. As a consequence of this, the following may occur:
+
+- The total number of messages sent per minute could be more than the rate limit. For example, if your campaign has a rate limit of 10,000 per min and utilizes email and SMS, Braze can send a max of 20,000 total messages each minute (10,000 email and 10,000 webhooks).
+
+| Maximum emails sent per minute | Maximum SMS messages sent per minute | Maximum total messages sent per minute |
+|--------------------------------|--------------------------------------|----------------------------------------|
+| 10,000                         | 10,000                               | 20,000                                 |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
+
+- Users could receive the different channels at different times, and it is not necessarily predictable which channel they will get first. 
+
+For example, if you send a campaign that contains email and SMS, you may have 10,000 users with valid phone numbers, but 50,000 users with valid email addresses. If you set the campaign to send 100 messages per minute (a slow rate limit for the campaign size), a user could receive the SMS in the first batch of sends and the email in the last batch of sends, almost nine hours later.
+
+### Multi-platform push campaigns
+
+For push campaigns delivering on multiple platforms, the rate limit selected will be equally distributed across platforms. A push campaign leveraging Android and iOS with a 10,000 rate-limit per minute will equally distribute the 10,000 messages across the two platforms.
+
+| Maximum Android notifications sent per minute | Maximum iOS push notifications sent per minute | Maximum total push notifications sent per minute |
+|--------------------------------|--------------------------------------|----------------------------------------|
+| 10,000                         | 10,000                               | 10,000                                 |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
+
+## Canvas delivery speed rate limiting
+
+When sending a Canvas with a speed rate limit, each channel is sent independently of the others. As a consequence of this, the following may occur:
+
+- The total number of messages sent per minute could be more than the rate limit. 
+    - For example, if your Canvas has a rate limit of 10,000 per min and utilizes email and in-app messages, Braze can send up to 20,000 total messages each minute (10,000 email and 10,000 in-app messages).
+
+- Rate limits may impact the order in which users receive messages in a Canvas. 
+    - For example, if you send a Canvas that contains emails and push notifications to 50,000 users, it may be that all 50,000 have valid email addresses but only 10,000 users have valid push tokens. In this case, if you set the Canvas to send 1,000 messages per minute and there is a multi-channel Canvas step that contains both email and push, it is possible that a user can advance to the next Canvas step (and be eligible to receive this next step) after receiving only the push notification but not yet the email. 
+
+## Overview of previous and new rate limiting behavior
+
+Your Braze account is currently using the previous delivery speed rate limiting behavior. The information below details the overall difference between previous and new delivery speed rate limiting behavior:
+
+- **Single-channel campaigns and Canvases:** Rate limits will always be applied across all messages together.
+- **Multi-channel campaigns and Canvases (including multi-platform push):**
+
+
+<style>
+table td {
+    word-break: normal;
+}
+</style>
+
+<table>
+  <tr>
+    <th></th>
+    <th><b>Campaigns</b></th>
+    <th><b>Canvas</b></th>
+  </tr>
+  <tr>
+    <td><b>Previous</b></td>
+    <td>Applied for each channel separately, with push platforms* sharing the limit collectively</td>
+    <td>Applied for each channel separately, with push platforms* sharing the limit collectively</td>
+  </tr>
+  <tr>
+    <td><b>New</b></td>
+    <td>Applied separately per channel and push platform</td>
+    <td>Shared collectively</td>
+  </tr>
+</table>
+
+_*Push platforms include: Android, iOS, Web Push, and Kindle._
\ No newline at end of file
diff --git a/_docs/_partners/canvas_steps.md b/_docs/_partners/canvas_steps.md
index 819faf3e1b1..9ed6ba34e33 100644
--- a/_docs/_partners/canvas_steps.md
+++ b/_docs/_partners/canvas_steps.md
@@ -20,15 +20,18 @@ guide_featured_list:
 
 guide_menu_title: "Available sync partners"
 guide_menu_list:
+  - name: Criteo Audience Sync
+    link: /docs/partners/canvas_steps/criteo_audience_sync
+    image: /assets/img/braze_icons/lightning-01.svg
   - name: Facebook Audience Sync
     link: /docs/partners/canvas_steps/facebook_audience_sync
     image: /assets/img/braze_icons/facebook.svg
   - name: Google Audience Sync
     link: /docs/partners/canvas_steps/google_audience_sync
     image: /assets/img/braze_icons/google.svg
-  - name: Criteo Audience Sync
-    link: /docs/partners/canvas_steps/criteo_audience_sync
-    image: /assets/img/braze_icons/lightning-01.svg
+  - name: LinkedIn Audience Sync
+    link: /docs/partners/canvas_steps/linkedin_audience_sync
+    image: /assets/img/braze_icons/linkedin.svg
   - name: Pinterest Audience Sync
     link: /docs/partners/canvas_steps/pinterest_audience_sync
     image: /assets/img/braze_icons/pinterest.svg
diff --git a/_docs/_partners/canvas_steps/criteo_audience_sync.md b/_docs/_partners/canvas_steps/criteo_audience_sync.md
index 92290e4225a..7c0a688352a 100644
--- a/_docs/_partners/canvas_steps/criteo_audience_sync.md
+++ b/_docs/_partners/canvas_steps/criteo_audience_sync.md
@@ -2,7 +2,7 @@
 nav_title: Criteo
 article_title: Canvas Audience Sync to Criteo
 description: "This reference article will cover how to use Braze Audience Sync to Criteo, to deliver advertisements based upon behavioral triggers, segmentation, and more."
-page_order: 4
+page_order: 1
 alias: "/audience_sync_criteo/"
 
 Tool:
@@ -35,7 +35,7 @@ You will need to ensure that you have the following items created and/or complet
 | --- | --- | --- |
 | Criteo ad account | [Criteo](https://marketing.criteo.com/) | An active Criteo ad account tied to your brand.<br><br>Ensure that your Criteo admin has granted you the appropriate permissions to access Audiences. |
 | [Criteo Advertising Guidelines](https://www.criteo.com/advertising-guidelines/)<br>and<br>[Criteo Brand Safety Guidelines](https://www.criteo.com/wp-content/uploads/2017/11/Criteo-Brand-Safety-Guidelines-UK-March-2016.pdf) | Criteo | As an active Criteo customer, you must ensure that you can comply with Criteo’s Advertising and Brand Safety Guidelines prior to launching any Criteo campaigns. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration 
 
@@ -140,7 +140,7 @@ The following table includes metrics and descriptions to help you better underst
 | Users Pending | Number of users currently being processed by Braze to sync into Criteo. |
 | Users Errored | Number of users who were not synced to Criteo due to an API error after about 13 hours of retries. Potential causes of errors can include an invalid Criteo token or if the audience was deleted on Criteo. |
 | Exited Canvas | Number of users who have exited the Canvas. This occurs when the last step in a Canvas is an Audience Sync component. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 Remember that there will be a delay in reporting for users synced and users errored metrics due to the bulk flusher and the 13-hour retry, respectively.
diff --git a/_docs/_partners/canvas_steps/facebook_audience_sync.md b/_docs/_partners/canvas_steps/facebook_audience_sync.md
index d5f046f1930..3b804c9058d 100644
--- a/_docs/_partners/canvas_steps/facebook_audience_sync.md
+++ b/_docs/_partners/canvas_steps/facebook_audience_sync.md
@@ -2,7 +2,7 @@
 nav_title: Facebook
 article_title: Canvas Audience Sync to Facebook
 description: "This reference article will cover how to use Braze Audience Sync to Facebook, to deliver advertisements based upon behavioral triggers, segmentation, and more."
-page_order: 1
+page_order: 2
 alias: "/audience_sync_facebook/"
 
 Tool:
@@ -12,7 +12,7 @@ Tool:
 
 # Audience Sync to Facebook
 
-Using the Braze Audience Sync to Facebook, brands can elect to add their own users' data from their own Braze integration to Facebook Custom Audiences to deliver advertisements based upon behavioral triggers, segmentation, and more. Any criteria you'd typically use to trigger a message (Push, Email, SMS, Webhook, etc.) in a Braze Canvas based upon your user data can now be used to trigger an ad to that user in Facebook via Custom Audiences.
+Using the Braze Audience Sync to Facebook, brands can elect to add their own users' data from their own Braze integration to Facebook Custom Audiences to deliver advertisements based on behavioral triggers, segmentation, and more. Any criteria you'd typically use to trigger a message (push, email, SMS, or webhook) in a Braze Canvas based on your user data can now be used to trigger an ad to that user in Facebook using Custom Audiences.
 
 **Common use cases for syncing Custom Audiences include**:
 
@@ -21,7 +21,7 @@ Using the Braze Audience Sync to Facebook, brands can elect to add their own use
 - Creating suppression audiences to prevent users from receiving advertisements when they're already loyal consumers of your brand.
 - Creating Lookalike Audiences to acquire new users more efficiently.
 
-This feature gives brands the option to control what specific first-party data is shared with Facebook. At Braze, the integrations you can and cannot share your first-party data with are given the utmost consideration. For more information, refer to our [privacy policy](https://www.braze.com/privacy).
+This feature allows brands to control what specific first-party data is shared with Facebook. At Braze, the integrations you can and cannot share your first-party data with are given the utmost consideration. For more information, refer to our [privacy policy](https://www.braze.com/privacy).
 
 ## Prerequisites
 
@@ -29,10 +29,10 @@ You will need to confirm that you have the following items created and completed
 
 | Requirement | Origin | Description |
 | ----------- | ------ | ----------- |
-| Facebook Business Manager | [Facebook][1] | A centralized tool to manage your brand's Facebook assets (for example, ad accounts, pages, apps). |
-| Facebook Ad Account | [Facebook][2] | An active Facebook ad account tied to your brand's business manager.<br><br>Ensure that your Facebook business manager admin has granted you either "Manage Campaigns" or "Manage ad accounts" permissions to the Facebook ad accounts you plan to use with Braze. Also ensure that you have accepted your ad account terms and conditions. |
+| Facebook Business Manager | [Facebook][1] | A centralized tool to manage your brand's Facebook assets (for example, ad accounts, pages, and apps). |
+| Facebook Ad Account | [Facebook][2] | An active Facebook ad account tied to your brand's business manager.<br><br>Ensure that your Facebook business manager admin has granted you either "Manage Campaigns" or "Manage ad accounts" permissions to the Facebook ad accounts you plan to use with Braze. Also, ensure that you have accepted your ad account terms and conditions. |
 | Facebook Custom Audiences Terms | [Facebook][3] | Accept Facebook's Custom Audiences Terms for your Facebook ad accounts you plan to use with Braze. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 
@@ -128,7 +128,7 @@ Starting in July 2023, Meta is rolling out Meta work accounts to a small set of
  
 As users reach the Audience Sync Step, Braze will sync these users in near real-time while also respecting Facebook's Marketing API rate limits. What this means in practice is that Braze will try to batch and process as many users every 5 seconds before sending these users to Facebook. 
 
-Facebook's Marketing API rate limit states no more than &#126;190k API requests for each ad account in a 1 hour time period. If a Braze customer reaches this rate limit, Braze the Canvas will retry the sync for up to &#126;13 hours. If the sync is not possible, these users are listed under the Users Errored metric.
+Facebook's Marketing API rate limit states no more than &#126;190k API requests for each ad account in a 1 hour time period. If a Braze customer reaches this rate limit, Braze the Canvas will retry the sync for up to &#126;13 hours. If the sync isn't possible, these users are listed under the Users Errored metric.
 
 ## Understanding analytics
 
@@ -143,7 +143,7 @@ The following table includes metrics and descriptions to help you better underst
 | Users Pending | Number of users currently being processed by Braze to sync into Facebook. |
 | Users Errored | Number of users who were not synced to Facebook due to an API error after about 13 hours of retries. Potential causes of errors can include an invalid Facebook token or if the custom audience was deleted on Facebook. |
 | Exited Canvas | Number of users who have exited the Canvas. This occurs when the last step in a Canvas is a Facebook step. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 Remember that there will be a delay in reporting for users synced and users errored metrics due to the bulk flusher and the 13-hour retry, respectively.
@@ -156,17 +156,17 @@ You can simply disconnect and reconnect your Facebook account on the Facebook pa
 {% enddetails %}
 
 {% details Why is my Canvas not allowed to launch? %}
-- Make sure your system user token is authenticated and has access to the desired ad accounts in Facebook Business Manager
-- Make sure you have selected an ad account, entered a name for the new custom audience, and selected fields to match
+- Make sure your system user token is authenticated and has access to the desired ad accounts in Facebook Business Manager.
+- Make sure you have selected an ad account, entered a name for the new custom audience, and selected fields to match.
 - You may have reached the 500 custom audience limit on Facebook. Go into Facebook Audience Manager to delete some unneeded ones before creating any new Custom Audiences using Canvas.
 {% enddetails %}
 
 {% details How do I know if users have matched after passing users to Facebook? %}
-Facebook does not provide this information for privacy reasons.
+Facebook doesn't provide this information for privacy reasons.
 {% enddetails %}
 
 {% details Does Braze support value-based custom audiences? %}
-At this time, value-based custom audiences are not supported by Braze. If you are interested in syncing these types of custom audiences, submit [product feedback]({{site.baseurl}}/user_guide/administrative/access_braze/portal/).
+At this time, value-based custom audiences aren't supported by Braze. If you're interested in syncing these types of custom audiences, submit [product feedback]({{site.baseurl}}/user_guide/administrative/access_braze/portal/).
 {% enddetails %}
 
 {% details How do I resolve an issue with syncing a value-based lookalike custom audience? %}
@@ -182,16 +182,14 @@ At this time, value-based lookalike custom audiences are not supposed by Braze.
 {% enddetails %}
 
 {% details I’ve received an email related to Facebook custom audience terms of service. What should I do to resolve this? %}
-In order to use Audience Sync to Facebook, you will need to ensure that you have accepted these terms of service agreement. 
+To use Audience Sync to Facebook, you need to accept these terms of service agreement. 
 
-If your ad account is directly associated with your personal Facebook account, follow this link and accept the TOS: [https://www.facebook.com/ads/manage/customaudiences/tos.php](https://www.facebook.com/ads/manage/customaudiences/tos.php)
+- If your ad account is directly associated with your personal Facebook account, you can accept the TOS from within your personal account here: `https://www.facebook.com/ads/manage/customaudiences/tos.php?act=ACCOUNT_ID`.
+- If your ad account is tied to your company's Business Manager account, you need to accept the TOS from within your business manager account here: `https://business.facebook.com/customaudiences/value_based/tos.php?act=ACCOUNT_ID&business_id=BUSINESS_ID`.
 
-If your ad account is tied to your company's Business Manager account you will also need to accept the TOS from within your business manager account. following this link:<br>
-[https://business.facebook.com/customaudiences/value_based/tos.php?act=ACCOUNT_ID&business_id=BUSINESS_ID](https://business.facebook.com/customaudiences/value_based/tos.php?act=ACCOUNT_ID&business_id=BUSINESS_ID)
-
-Once you have accepted your Facebook custom audiences terms of service, you will need to do the following:
+After you have accepted your Facebook custom audience terms of service, do the following:
 1. Refresh your Facebook access token with Braze by disconnecting and reconnecting your Facebook account.
-2.  Re-enable your Facebook Audience Sync step by editing and updating your Canvas.
+2. Re-enable your Facebook Audience Sync step by editing and updating your Canvas.
 Braze will then be able to sync users as soon as they reach the Facebook audience step.
 {% enddetails %}
 
diff --git a/_docs/_partners/canvas_steps/google_audience_sync.md b/_docs/_partners/canvas_steps/google_audience_sync.md
index dc450601917..9ae07c289e1 100644
--- a/_docs/_partners/canvas_steps/google_audience_sync.md
+++ b/_docs/_partners/canvas_steps/google_audience_sync.md
@@ -5,7 +5,7 @@ alias: /google_audience_sync/
 description: "This reference article will cover how to use Braze Audience Sync to Google, to deliver advertisements based upon behavioral triggers, segmentation, and more."
 Tool:
   - Canvas
-page_order: 2
+page_order: 3
 
 ---
 
@@ -40,7 +40,7 @@ You must ensure the following items are created and completed before setting up
 | Google Ads Terms and Google Ads Policies | [Google](https://support.google.com/adspolicy/answer/54818?hl=en) | You must accept and ensure you comply with [Google’s Ad Terms](https://payments.google.com/u/0/paymentsinfofinder?hostOrigin=aHR0cHM6Ly9wYXltZW50cy5nb29nbGUuY29tOjQ0Mw..&sri=-40) and [Google’s Ad Policies](https://support.google.com/adspolicy/answer/6008942?sjid=15557182366992806023-NC), which include the [EU User Consent Policy](https://www.google.com/about/company/user-consent-policy/), as applicable to you, in your use of Braze Audience Sync.<br><br>Consult with your Legal Team on Google’s new EU User Consent Policy to ensure you are collecting appropriate consent in order to use Google Ads’ services for your EEA, UK, and Switzerland end users. |
 | Google Customer Match | [Google](https://support.google.com/google-ads/answer/6299717) |  Customer Match is not available for all advertisers.<br><br>**To use Customer Match, your account must have:**<br>• A good history of policy compliance<br>• A good payment history<br>• At least 90 days history in Google Ads<br>• More than USD 50,000 total lifetime spend. For advertisers whose accounts are managed in currencies other than USD, your spend amount will be converted to USD using the average monthly conversion rate for that currency.<br><br>If your account does not meet these criteria, then your account is currently ineligible to use Customer Match.<br><br>Connect with your Google Ads representative for more guidance on Customer Match availability for your account. |
 | Google Consent Signals | [Google](https://support.google.com/google-ads/answer/14310715) |  If you want to serve ads to EEA end users using Google’s Customer Match service, you’ll need to pass Braze the following custom attributes (boolean) as part of Google’s  EU User Consent Policy. More details can be found under [Collecting consent for EEA, UK, and Switzerland end users](#collecting-consent-for-eea-uk-and-switzerland-end-users): <br> - `$google_ad_user_data` <br> - `$google_ad_personalization` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 When using Braze SDKs to collect consent signals, ensure you meet the following minimum versions:
 
@@ -195,7 +195,7 @@ The following table includes metrics and descriptions to help you better underst
 | *Users Errored* | Number of users who were not synced to Google due to an error, after &#126;13 hours of retries. For specific errors, like Google Ads API service disruptions, Canvas will retry the sync for up to &#126;13 hours. If the sync is still not possible at that point, the *User Not Synced* will be populated. |
 | *Users Pending* | Number of users currently being processed by Braze to sync to Google. |
 | *Exited Canvas* | Number of users who have exited the Canvas. This occurs when the last step in a Canvas is a Google step. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Troubleshooting
 
diff --git a/_docs/_hidden/private_betas/linkedin_audience_sync.md b/_docs/_partners/canvas_steps/linkedin_audience_sync.md
similarity index 86%
rename from _docs/_hidden/private_betas/linkedin_audience_sync.md
rename to _docs/_partners/canvas_steps/linkedin_audience_sync.md
index 807d484db8e..f42a94f5877 100644
--- a/_docs/_hidden/private_betas/linkedin_audience_sync.md
+++ b/_docs/_partners/canvas_steps/linkedin_audience_sync.md
@@ -1,11 +1,12 @@
 ---
-nav_title: Audience Sync to LinkedIn
+nav_title: LinkedIn
 article_title: Canvas Audience Sync to LinkedIn
-permalink: /linkedin_audience_sync/
+alias: /linkedin_audience_sync/
 description: "This reference article will cover how to use Braze Audience Sync to LinkedIn to deliver advertisements based upon behavioral triggers, segmentation, and more."
 Tool:
   - Canvas
-hidden: true
+page_order: 4
+
 ---
 
 # Audience Sync to LinkedIn
@@ -32,23 +33,23 @@ You must make sure that you have the following items created, completed, or acce
 | --- | --- | --- |
 | LinkedIn ad account | [LinkedIn](https://www.linkedin.com/campaignmanager) | An active LinkedIn ad account tied to your brand.<br><br>Make sure that you have accepted any relevant LinkedIn terms and conditions to access and use that account and that your LinkedIn admin has granted you the appropriate permissions to manage Audiences. |
 | LinkedIn Terms & Policies | LinkedIn | Agree to comply with any of LinkedIn’s required terms, policies, guidelines, and documentation related to your use of the LinkedIn Audience Sync, including any terms, policies, guidelines, and documentation incorporated by reference therein, which may include LinkedIn’s: Services Terms, Ads Agreement, Data Processing Agreement, and Professional Community Guidelines. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 
 ### Step 1: Connect to LinkedIn
 
-In the Braze dashboard, go to **Technology Partners** and select **LinkedIn**. In the LinkedIn Audience Export module, click **Connect LinkedIn**.
+In the Braze dashboard, go to **Technology Partners** and select **LinkedIn**. In the **LinkedIn Audience Sync** section, select **Connect LinkedIn**.
 
-![LinkedIn technology page in Braze includes an Overview module and LinkedIn Audience Export module with the Connected LinkedIn button.][3]{: style="max-width:75%;"}
+![LinkedIn technology page in Braze includes an Overview section and LinkedIn Audience Sync section with the Connected LinkedIn button.][3]{: style="max-width:75%;"}
 
 You’ll then be redirected to the LinkedIn OAuth page to authorize Braze for the permissions related to your Audience Sync integration. After you have selected **Confirm**, you’ll be redirected back into Braze to select which LinkedIn ad accounts you wish to sync to. 
 
-![][7]{: style="max-width:75%;"}
+!["Braze Self Service" is selected as the ad account to connect.][7]{: style="max-width:75%;"}
 
 Once you have successfully connected, you will be returned to the partner page, where you can view which accounts are connected and disconnect existing accounts.
 
-![][6]{: style="max-width:75%;"}
+![A successfully connected LinkedIn account.][6]{: style="max-width:75%;"}
 
 Your LinkedIn connection will be applied at the Braze workspace level. If your LinkedIn admin removes you from your LinkedIn ad account, Braze will detect an invalid token. As a result, your active Canvases using LinkedIn will show errors, and Braze will not be able to sync users.
 
@@ -58,7 +59,7 @@ When building audiences for Ad Tracking, you may wish to include or exclude cert
 
 If you have collected the [iOS IDFA through the Braze SDK]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overviewother_sdk_customizations/#optional-idfa-collection), you will be able to use the **Ads Tracking Enabled** filter. Select the value as `true` to only send users into Audience Sync destinations where they have opted in. 
 
-![][5]{: style="max-width:75%;"}
+![An entry audience with the filter "Ad Tracking Enabled is true".][5]{: style="max-width:75%;"}
 
 If you are collecting `opt-ins`, `opt-outs`, `Do Not Sell Or Share`, or any other relevant custom attributes, you should include these within your Canvas entry criteria as a filter:
 
@@ -70,17 +71,17 @@ To learn more on how to comply with these Data Protection laws within the Braze
 
 Add a component in your Canvas and select Audience Sync. Click on the **Custom Audience** button to open the component editor.
 
-![][2]{: style="max-width:35%;"} ![][1]{: style="max-width:29%;"}
+![The Canvas editor with the list of available components.][2]{: style="max-width:35%;"} ![The selected Audience Sync component.][1]{: style="max-width:29%;"}
 
 ### Step 4: Sync setup
 
 Select **LinkedIn** as the desired Audience Sync partner.
 
-![][9]{: style="max-width:70%;"}
+![The "Set up Audience Sync" details with the multiple partners to choose from.][9]{: style="max-width:70%;"}
 
 Then select the desired LinkedIn ad account. Under the **Choose a New or Existing Audience** dropdown, type in the name of a new or existing audience.
 
-![][11]
+![Audience Sync to LinkedIn with Braze selected as the ad account.][11]
 
 {% tabs %}
 {% tab Create a New Audience %}
@@ -93,11 +94,11 @@ Enter a name for the new audience, select **Add Users to Audience**, and select
 
 Next, save your audience by clicking the **Create Audience** button at the bottom of the step editor.
 
-![]({% image_buster /assets/img/linkedin/linkedin10.png %})
+![An example "leads" audience with the selected Braze ad account, "leads" audience, the action to add users to the audience, and email, Android GAID, and first and last name as fields to match.]({% image_buster /assets/img/linkedin/linkedin10.png %})
 
 Users will be notified at the top of the step editor if the audience is created successfully or if errors arise during this process. Users can also reference this audience for user removal later in the Canvas journey because the audience was created in draft mode.
 
-![]({% image_buster /assets/img/linkedin/linkedin9.png %})
+![Confirmation that the "leads" audience was created.]({% image_buster /assets/img/linkedin/linkedin9.png %})
 
 When you launch a Canvas with a new audience, Braze syncs users in near real-time as they enter the Audience Sync component.
 
@@ -124,7 +125,7 @@ You can view the audience on LinkedIn by going into your ad account and selectin
 
 As users reach the Audience Sync Step, Braze will sync these users in near real-time while respecting LinkedIn’s API rate limits. In practice, Braze will try to batch and process as many users every 5 seconds before sending these users to LinkedIn.
 
-LinkedIn’s API rate limit states no more than ten queries per second and 100k users per request. If a Braze customer reaches this rate limit, Braze the Canvas will retry the sync for up to ~13 hours. If the sync is not possible, these users are listed under the Users Errored metric.
+LinkedIn’s API rate limit states no more than ten queries per second and 100,000 users per request. If a Braze customer reaches this rate limit, Braze the Canvas will retry the sync for up to about 13 hours. If the sync is not possible, these users are listed under the Users Errored metric.
 
 ## Understanding analytics
 
@@ -139,18 +140,18 @@ The following table includes metrics and descriptions to help you better underst
 | Users Pending | Number of users currently being processed by Braze to sync into LinkedIn. |
 | Users Errored | Number of users who were not synced to LinkedIn due to an API error after about 13 hours of retries. Potential causes of errors can include an invalid LinkedIn token or if the audience was deleted on LinkedIn. |
 | Exited Canvas | Number of users who have exited the Canvas. This occurs when the last step in a Canvas is an Audience Sync component. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 Remember that there will be a delay in reporting for users synced and users errored metrics due to the bulk flusher and the 13-hour retry, respectively.
 {% endalert %}
 
 {% alert important %}
-LinkedIn provides additional metrics around match rates within their platform. To review the match of your specific Audience Sync, click the Audience Sync step metrics to go into the **Canvas Step Details** page. 
+LinkedIn provides additional metrics around match rates within their platform. To review the match of your specific Audience Sync, select the Audience Sync step metrics to go into the **Canvas Step Details** page. 
 <br><br>
 Select the partner as **LinkedIn**, your ad account, and the audience to see the audience size and match rate from LinkedIn.
 
-![]({% image_buster /assets/img/linkedin/linkedin11.png %})
+![An example of Audience Sync step metrics with 10,000 entered users.]({% image_buster /assets/img/linkedin/linkedin11.png %})
 {% endalert %}
 
 ## Troubleshooting
diff --git a/_docs/_partners/canvas_steps/pinterest_audience_sync.md b/_docs/_partners/canvas_steps/pinterest_audience_sync.md
index 428f05065f0..33a3a24c0a6 100644
--- a/_docs/_partners/canvas_steps/pinterest_audience_sync.md
+++ b/_docs/_partners/canvas_steps/pinterest_audience_sync.md
@@ -2,7 +2,7 @@
 nav_title: Pinterest
 article_title: Canvas Audience Sync to Pinterest
 description: "This reference article will cover how to use Braze Audience Sync to Pinterest, to deliver advertisements based upon behavioral triggers, segmentation, and more."
-page_order: 3
+page_order: 5
 alias: "/audience_sync_pinterest/"
 
 Tool:
@@ -36,7 +36,7 @@ You must ensure the following items are created, completed, and/or accepted befo
 | Pinterest Business Hub | [Pinterest](https://www.pinterest.com/business/hub/) | A centralized tool to manage your brand's Pinterest assets (such as ad accounts, pages, apps). |
 | Pinterest ad account | [Pinterest](https://ads.pinterest.com/) | An active Pinterest ad account tied to your brand's Pinterest Business Hub.<br><br>Ensure that your Pinterest Business Hub admin has granted you admin permissions to the Pinterest ad accounts you plan to use with Braze. |
 | Pinterest terms & policies | Pinterest | Agree to comply with any of Pinterest’s required terms, policies, guidelines, and documentation related to your use of the Pinterest Audience Sync, including any terms, policies, guidelines, and documentation incorporated by reference therein, which may include: the Terms of Service, Business Terms of Service, Privacy Policy, Developer and API Terms of Service, Ad Data Terms, Advertising Guidelines, Advertising Services Agreement, Community Guidelines, and Brand Guidelines. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration 
 
@@ -128,7 +128,7 @@ The following table includes metrics and descriptions to help you better underst
 | Users Pending | Number of users currently being processed by Braze to sync into Pinterest. |
 | Users Errored | Number of users who were not synced to Pinterest due to an API error after about 13 hours of retries. Potential causes of errors can include an invalid Pinterest token or if the audience was deleted on Pinterest. |
 | Exited Canvas | Number of users who have exited the Canvas. This occurs when the last step in a Canvas is an Audience Sync component. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 Remember that there will be a delay in reporting for synced users and errored metrics due to the bulk flusher and the 13-hour retry, respectively.
diff --git a/_docs/_partners/canvas_steps/snapchat_audience_sync.md b/_docs/_partners/canvas_steps/snapchat_audience_sync.md
index 3227c180bfd..2ff5caf552d 100644
--- a/_docs/_partners/canvas_steps/snapchat_audience_sync.md
+++ b/_docs/_partners/canvas_steps/snapchat_audience_sync.md
@@ -2,7 +2,7 @@
 nav_title: Snapchat
 article_title: Canvas Audience Sync to Snapchat
 description: "This reference article will cover how to use Braze Audience Sync to Snapchat, to deliver advertisements based upon behavioral triggers, segmentation, and more."
-page_order: 4
+page_order: 6
 alias: "/audience_sync_snapchat/"
 
 Tool:
@@ -37,7 +37,7 @@ You must ensure the following items are created, completed and/or accepted befor
 | Snapchat Business Manager | Snapchat | A centralized tool to manage your brand's Snapchat assets (such as ad accounts, pages, apps). |
 | Snapchat ad account | Snapchat | An active Snapchat ad account tied to your brand's Snapchat Business Manager.<br><br>Ensure that your Snapchat Business Manager admin has granted you admin permissions to the Snapchat ad accounts you plan to use with Braze. |
 | Snapchat terms & policies | [Snapchat](https://www.snap.com/en-US/policies) | Agree to comply with any of Snapchat’s required terms, policies, guidelines, and documentation related to your use of the Snapchat Audience Sync, including any terms, policies, guidelines, and documentation incorporated by reference therein, which may include: the Terms of Service, Business Terms of Service, Developer Terms, Audience Match, Advertising Policies, Commercial Content Policy, Community Guidelines, and Supplier Responsibility. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration 
 
@@ -130,7 +130,7 @@ The following table includes metrics and descriptions to help you better underst
 | Users Pending | Number of users currently being processed by Braze to sync into Snapchat. |
 | Users Errored | Number of users who were not synced to Snapchat due to an API error after about 13 hours of retries. Potential causes of errors can include an invalid Snapchat token or if the audience was deleted on Snapchat. |
 | Exited Canvas | Number of users who have exited the Canvas. This occurs when the last step in a Canvas is an Audience Sync component. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 Remember that there will be a delay in reporting for synced users and errored metrics due to the bulk flusher and the 13-hour retry, respectively.
diff --git a/_docs/_partners/canvas_steps/tiktok_audience_sync.md b/_docs/_partners/canvas_steps/tiktok_audience_sync.md
index 7df43240466..dc53329e3c8 100644
--- a/_docs/_partners/canvas_steps/tiktok_audience_sync.md
+++ b/_docs/_partners/canvas_steps/tiktok_audience_sync.md
@@ -5,7 +5,7 @@ alias: /tiktok_audience_sync/
 description: "This reference article will cover how to use Braze Audience Sync to TikTok to deliver advertisements based upon behavioral triggers, segmentation, and more."
 Tool:
   - Canvas
-page_order: 5
+page_order: 7
 
 ---
 
@@ -36,7 +36,7 @@ You must ensure the following items are created, completed, and/or accepted befo
 | TikTok for Business Center Account | [TikTok](https://business.tiktok.com/) | A centralized tool to manage your brand's TikTok assets (such as ad accounts, pages, apps). |
 | TikTok Ad Account | [TikTok](https://ads.tiktok.com/) | An active TikTok ad account tied to your brand's Business Center account.<br><br>Ensure that your TikTok Business Center manager admin has granted you admin permissions to the TikTok ad accounts you plan to use with Braze. |
 | TikToK terms & policies | [TikTok](https://ads.tiktok.com/i18n/official/policy/terms) | Agree to comply with any of TikTok’s required terms, policies, guidelines, and documentation related to your use of the Pinterest Audience Sync, including any terms, policies, guidelines, and documentation incorporated by reference therein, which may include: the Commercial Terms of Service, Advertising Terms, Privacy Policy, Custom Audience Terms, Developer Terms of Service, Developer Data Sharing Agreement, Advertising Policies, Brand Guidelines, and Community Guidelines. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration 
 
@@ -129,7 +129,7 @@ The following table includes metrics and descriptions to help you better underst
 | Users Pending | Number of users currently being processed by Braze to sync into TikTok. |
 | Users Errored | Number of users who were not synced to TikTok due to an API error after about 13 hours of retries. Potential causes of errors can include an invalid TikTok token or if the audience was deleted on TikTok. |
 | Exited Canvas | Number of users who have exited the Canvas. This occurs when the last step in a Canvas is an Audience sync component. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 Remember that there will be a delay in reporting for users synced and users errored metrics due to the bulk flusher and the 13-hour retry, respectively.
diff --git a/_docs/_partners/data_and_infrastructure_agility/ab_testing/jacquard.md b/_docs/_partners/data_and_infrastructure_agility/ab_testing/jacquard.md
index 01cac7e6ace..56b8abccb76 100644
--- a/_docs/_partners/data_and_infrastructure_agility/ab_testing/jacquard.md
+++ b/_docs/_partners/data_and_infrastructure_agility/ab_testing/jacquard.md
@@ -20,7 +20,7 @@ Dynamic Optimisation, powered by Jacquard X, leverages Braze Currents and Connec
 | Jacquard account | A [Jacquard account][1] is required to take advantage of this partnership. |
 | Jacquard connect server token | A long string of characters that will serve as your Braze campaign's password to access your Jacquard language.<br><br>You can request this from your Jacquard customer success manager if you haven't already been provided it. |
 | Currents | In order to export data to Currents, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/advertising/liveramp.md b/_docs/_partners/data_and_infrastructure_agility/advertising/liveramp.md
index 3c762ef307b..b6204371ade 100644
--- a/_docs/_partners/data_and_infrastructure_agility/advertising/liveramp.md
+++ b/_docs/_partners/data_and_infrastructure_agility/advertising/liveramp.md
@@ -58,7 +58,7 @@ Next, create a data table with the [required format](https://docs.liveramp.com/i
 | Email Only      | The user's email addresses, such as `alex-lee@email.com`. |
 | Device          | This includes 3rd-party cookies, Mobile Advertising IDs (MAIDs), Connected TV IDs (CTV IDs), and RampIDs (resolved to a Household RampID). |
 | CIDs            | These are identifiers from a platform partner or an identity sync with LiveRamp, such as your internal Customer ID. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Braze identifiers
 
@@ -70,7 +70,7 @@ Braze’s event logs contain identifiers you can use within the LiveRamp native
 | `EMAIL_ADDRESS`   | Email address which can be used in conjunction with LiveRamp’s Email Only Resolution services |
 | `TO_PHONE_NUMBER` | Phone number, which can be used in conjunction with LiveRamp’s PII Resolution services. |
 | `EXTERNAL_USER_ID` | The external ID associated with a user, which can be used in conjunction with LiveRamp’s Device Resolution services (CID). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 The use of any client or brand-specific custom identifiers within LiveRamp’s application requires an [identity sync with LiveRamp](https://docs.liveramp.com/identity/en/getting-started-with-liveramp-identity.html).
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/actionableme.md b/_docs/_partners/data_and_infrastructure_agility/analytics/actionableme.md
index 24e03dcaaab..1a9c9262fb8 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/actionableme.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/actionableme.md
@@ -21,7 +21,7 @@ The Braze and actionable.me integration allows you to deploy a service to monito
 | actionable.me account | An actionable.me account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with the permissions listed in the next section.<br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/adikteev.md b/_docs/_partners/data_and_infrastructure_agility/analytics/adikteev.md
index 91270bb5fe0..b3cf3899e22 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/adikteev.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/adikteev.md
@@ -21,7 +21,7 @@ The Braze and Adikteev integration allows you to boost user retention by leverag
 | Adikteev account | An Adikteev account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with the permission `users.track`. <br><br> This can be created in the Braze dashboard from **Settings** > **APIs and Identifiers**. |
 | Braze REST endpoint | [Your REST endpoint URL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints). Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences.md b/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences.md
index cfae151bb06..926a7624372 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences.md
@@ -22,7 +22,7 @@ The Braze and Amplitude bi-directional integration allows you to [import your Am
 |---|---|
 | Amplitude account | An [Amplitude account](https://amplitude.com/) is required to take advantage of this partnership. |
 | Currents | In order to export data back into Amplitude, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
-{: .reset-td-br-1 .reset-td-br-2} 
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" } 
 
 ## Choose an integration 
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents.md
index b2b3f15220a..a8538d9e7f6 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents.md
@@ -21,7 +21,7 @@ The Braze and Amplitude bi-directional integration allows you to [sync your Ampl
 |---|---|
 | Amplitude account | An [Amplitude account](https://amplitude.com/) is required to take advantage of this partnership. |
 | Currents | In order to export data back into Amplitude, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
-{: .reset-td-br-1 .reset-td-br-2} 
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" } 
 
 ## Data export integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api.md b/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api.md
index 9831561a3df..d3a55cc0d2f 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api.md
@@ -28,7 +28,7 @@ The following table lays out the parameters you can use in your calls to the use
 | `get_cohort_ids` | Optional<br>(Defaults to false) | Return a list of all of the cohort IDs that this user is a part of that have been set up to be tracked. By default cohort membership is not tracked for users for any cohort. |
 | `get_computations` | Optional<br>(Defaults to false) | Return a list of all of the computations that are enabled for this user. |
 | `comp_id` | Optional | Return a single computation that might be enabled for this user. It will return a null value if it does not exist. If `get_computations` is true, all values will be fetched, including this one (unless it is archived or deleted).|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 The following table covers the parameters you can most typically expect to see in Amplitude's responses.
 
@@ -40,7 +40,7 @@ The following table covers the parameters you can most typically expect to see i
 | `is_control` | true if this user is part of the control group. |
 | `recommendation_source` | Name of the model that was used to generate this recommendation |
 | `last_updated` | Timestamp of when this recommendation was last generated and synced. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Common Amplitude endpoints
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/celebrus.md b/_docs/_partners/data_and_infrastructure_agility/analytics/celebrus.md
index 77c1b117829..c8d815423ec 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/celebrus.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/celebrus.md
@@ -15,7 +15,7 @@ description: "Integrating Braze and Celebrus."
 | Celebrus account | A Celebrus account is required to take advantage of this partnership. |
 | Data warehouse (optional) | When using the Celebrus connector for Braze custom attributes, you must have a data warehouse that is supported by the Braze Cloud Data Ingestion (CDI) integration, and configure CDI in the Braze dashboard. |
 | Braze SDK configuration settings (optional) | When using the Celebrus connector for Braze SDK, you must pass the SDK endpoint and SDK API Key. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Implementation
 After installing your Celebrus implementation, use the Celebrus connectors for Braze to integrate Celebrus data into Braze. There are two elements to the Celebrus integration for Braze: the Braze SDK and Braze custom attributes. You can deploy either or both depending on how you use Braze and the use cases you need.
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/clarisights.md b/_docs/_partners/data_and_infrastructure_agility/analytics/clarisights.md
index c9572a23f44..4bde284df96 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/clarisights.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/clarisights.md
@@ -22,7 +22,7 @@ The Braze and Clarisights integration allows you to import data from Braze campa
 | Braze REST API key | A Braze REST API key with the following permissions:  <br> - `campaigns.list` <br>  - `campaigns.details`<br> - `campaigns.data_series` <br> - `canvas.details`<br> - `canvas.list` <br>  - `canvas.data_series` <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
 | Braze workspace name | The name of the workspace associated with the Braze API key. This name will be used to identify the workspace integration on Clarisights. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/contentsquare.md b/_docs/_partners/data_and_infrastructure_agility/analytics/contentsquare.md
index 85d0eba0973..be612fc89bf 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/contentsquare.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/contentsquare.md
@@ -21,7 +21,7 @@ The Braze and Contentsquare integration allows you to send Live Signals (fraud,
 | Contentsquare account | A Contentsquare account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. To create a new key in the Braze dashboard, go to **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/datadog.md b/_docs/_partners/data_and_infrastructure_agility/analytics/datadog.md
index df6cca8c497..7179e866ff9 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/datadog.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/datadog.md
@@ -20,7 +20,7 @@ The Braze and Datadog integration allows customers to collect Braze data in Data
 | Requirement | Description |
 |---|---|
 | Datadog account | A Datadog account is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/inbox_monster.md b/_docs/_partners/data_and_infrastructure_agility/analytics/inbox_monster.md
index 15637480690..0fab630d3f3 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/inbox_monster.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/inbox_monster.md
@@ -22,7 +22,7 @@ The Braze and Inbox Monster integration allows you to eliminate manual seedlist
 | Braze REST API key             | A Braze REST API key with the following permissions:  <br> - `messages.send` <br>  - `templates.email.create`<br> - `templates.email.update` <br> - `templates.email.info`<br> - `templates.email.list` <br><br> And with the following whitelisted ips: <br> - `3.136.16.19` <br>  - `3.140.233.31`<br> - `18.220.127.138` <br><br> This can be created in the Braze dashboard from **Settings** > **APIs and Identifiers** in the **API Keys** tab |
 | Braze app identifier           | A Braze app identifier. <br><br>This can be found in the Braze dashboard from **Settings** > **APIs and Identifiers** in the **App Identifiers** tab.                                                                                                                                                                                                                                                                                                |
 | Braze endpoint                 | [Your Braze endpoint]({{site.baseurl}}/api/basics/#endpoints) aligns with your Braze dashboard URL.<br><br> For example, if your dashboard URL is `https://dashboard-03.braze.com`, your endpoint will be `dashboard-03`.                                                                                                                                                                                                                            |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/kubit.md b/_docs/_partners/data_and_infrastructure_agility/analytics/kubit.md
index cd0781fdb7c..b784de9e11a 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/kubit.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/kubit.md
@@ -20,7 +20,7 @@ The Braze and Kubit integration allows you to [import Kubit user cohorts]({{site
 |---|---|
 |Kubit enterprise account | A Kubit enterprise account is required to take advantage of this partnership. |
 | Matching user IDs | Your customer data in Kubit and Braze must have matching user IDs across the two platforms. This also includes anonymous UUIDs. Visit our [documentation]({{site.baseurl}}/developer_guide/platform_integration_guides/android/analytics/setting_user_ids/) to read about how Braze sets user IDs. |
-{: .reset-td-br-1 .reset-td-br-2} 
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" } 
 
 ## Analyzing Braze data in Kubit
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/looker.md b/_docs/_partners/data_and_infrastructure_agility/analytics/looker.md
index 0a96943be69..53de97cb588 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/looker.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/looker.md
@@ -21,7 +21,7 @@ The Braze and Looker integration allows Braze users to leverage first-party [Loo
 |Looker account | A [Looker account](https://looker.com/) is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][1]. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 #### Limitations
 
@@ -56,7 +56,7 @@ Be aware of different naming conventions! Custom names can cause incongruities i
 |---|---|
 | Message engagement analytics block | This block includes data around push, email, in-app messages, webhook, News Feed, conversion, Canvas entry, and campaign control group enrollment events. <br><br>Learn more about this [Looker Block](https://looker.com/platform/blocks/source/message-engagement-analytics-by-braze?latest&utm_campaign=7012R000000fxfC&utm_source=other&utm_medium=email&utm_content=brazedirectreferral&utm_term=braze_direct), or check out the [GitHub code](https://github.com/llooker/braze_message_engagement_block). |
 | User behavior analytics block | This block includes data around custom events, purchases, sessions, location events, and uninstalls.<br><br>Learn more about this [Looker Block](https://looker.com/platform/blocks/source/user-behavior-analytics-by-braze?latest&utm_campaign=7012R000000fxfC&utm_source=other&utm_medium=email&utm_content=brazedirectreferral&utm_term=braze_direct), or check out the [GitHub code](https://github.com/llooker/braze_retention_block). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Looker Actions
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/merkury.md b/_docs/_partners/data_and_infrastructure_agility/analytics/merkury.md
index a634d48e31f..4a86c0ab6fc 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/merkury.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/merkury.md
@@ -22,7 +22,7 @@ The Braze and Merkury integration allows you to leverages the `MerkuryID` to inc
 | Merkury tag | Place Merkle's Merkury tag on your website. |
 | Braze REST and SDK endpoint | Your REST or SDK endpoint URL. Your endpoint will depend on the [Braze URL for your instance]({{site.baseurl}}/api/basics/#endpoints). |
 | Braze REST API key | A Braze REST API key with `users.track, users.export.ids, users.export.segment, and segments.list` permissions. <br><br>This can be created within **Braze Dashboard > Developer Console > REST API Key > Create New API Key**. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert important %}
 The Merkury identity connector requests to Braze operate within Braze API rate limit specifications. Contact Braze or your Merkle account manager if you have any questions.<br><br>Merkury will send at least one request at the end of a qualified session.
@@ -48,7 +48,7 @@ The following fields will be populated by Merkury identity connector and need to
 | --- | --- | --- |
 | `hmid` | String | Merkle's Merkury ID |
 | `confidence_score` | Number | How confident Merkury was able to identify (1-8, lower is better) |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Step 4: Provide Merkle with user email universe
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents.md
index 83e0867a3c1..4601ecf7349 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents.md
@@ -21,7 +21,7 @@ The Braze and Mixpanel integration allows you to [import Mixpanel Cohorts into B
 |---|---|
 | Mixpanel account | A [Mixpanel account](https://mixpanel.com/) is required to take advantage of this partnership. |
 | Currents | In order to export data back into Mixpanel, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
-{: .reset-td-br-1 .reset-td-br-2} 
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" } 
 
 ## Data export integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/npaw.md b/_docs/_partners/data_and_infrastructure_agility/analytics/npaw.md
index ea89fb5a06f..ad469e7e7e1 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/npaw.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/npaw.md
@@ -20,7 +20,7 @@ hidden: true
 | YOUBORA API Key |[YOUBORA Settings](https://youbora.nicepeopleatwork.com/users/login)|An API Key generated on user sign up and can be located under **Settings** |
 | ID |[Braze Settings](https://dashboard.braze.com/sign_in) | YOUBORA gives you the options of whether to link the software to Braze via a ***Braze ID***, an ***external User ID***, or a ***User ID*** |
 | Endpoint |[Braze Settings](https://dashboard.braze.com/sign_in)| A fully customizable URL endpoint configurable through your Braze dashboard. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 # Analytics integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/saleswings.md b/_docs/_partners/data_and_infrastructure_agility/analytics/saleswings.md
index d4ed1a3e407..ecc489ef1ba 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/saleswings.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/saleswings.md
@@ -22,7 +22,7 @@ SalesWings allows marketing teams and marketing operations managers to qualify l
 | Braze REST API key | A Braze REST API key with `users.export.ids` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][2]. Your endpoint will depend on the Braze URL for your instance. |
 | Segment.com account (optional) | If you are a Segment.com user, you can send all lead engagement and profile data and identify events via Segment.com for lead profiling. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/scuba.md b/_docs/_partners/data_and_infrastructure_agility/analytics/scuba.md
index 9dcc7873602..78c521fcb84 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/scuba.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/scuba.md
@@ -20,7 +20,7 @@ To use Scuba Analytics with Braze, you'll need the following:
 |Scuba API Token | A Scuba API token you can retrieve from the `https://{scuba_hostname}/api/create_token` endpoint. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][1]. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Uploading your Scuba data to Braze
 
@@ -61,7 +61,7 @@ Replace the following:
 | `PERIOD_START`          | The start period as a BQL-compatible date. For more information, see [BQL syntax and usage][6].                                                                                                 |
 | `PERIOD_END`            | The end period as a BQL-compatible date. For more information, see [BQL syntax and usage][6].                                                                                                   |
 | `RECORD_LIMIT`          | **Optional**: The maximum number of records to return. If `scuba_record_limit` is omitted, Scuba will return a maximum of 100 records. To change this, assignin any non-negative number to `scuba_record_limit`.    |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Default behavior
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/snowplow.md b/_docs/_partners/data_and_infrastructure_agility/analytics/snowplow.md
index b4ee7676fbd..12c7d217cbe 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/snowplow.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/snowplow.md
@@ -28,7 +28,7 @@ Leverage Snowplow's rich behavioral data to drive powerful customer-centric inte
 | Google Tag Manager server-side | GTM-SS needs to be deployed and the [Snowplow client for GTM-SS][2] set up. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][3]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
@@ -73,7 +73,7 @@ The following table lists the required tag parameters you must include in your B
 | Braze REST API endpoint | Set this to the URL of your Braze REST [endpoint][3]. |
 | Braze API key | Set this to your Braze [API key][4] that will be included in each request. |
 | Braze `external_id` | Set this key to the client event property that corresponds to your users' `external_id` and will be used as the [Braze user identifier][5]. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Event mapping
 
@@ -85,7 +85,7 @@ The following table lists event mapping options concerning the Snowplow event as
 | Snowplow event context rules | Describes how the Braze tag will use the context entities attached to a Snowplow event. |
 | Extract entity from array if single element | Snowplow entities are always in arrays, as multiple of the same entity can be attached to an event. This option will pick the single element from the array if the array only contains a single element. |
 | Include all entities in the event object | Turned on by default. Includes all entities on an event within the Braze event's properties object. Disable this option to select individual entities for inclusion. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Advanced event mapping
 
@@ -99,7 +99,7 @@ If you want to include other properties from the client event and map them onto
 | Additional user property and event property mapping rules | Specify the property key from the client event and the properties' object key you would like to map it to (or leave the mapped key blank to keep the same name). You can use key path notation here (for example, `x-sp-tp2.p` for a Snowplow events platform or `x-sp-contexts.com_snowplowanalytics_snowplow_web_page_1.0.id` for a Snowplow events page view id (in array index 0) or pick non-Snowplow properties if using an alternative client.<br><br>Event property mapping rules populate the Braze event properties object.|
 | Include common user properties| Enabled by default, this option sets whether to include the `user_data` properties from the common event definition in the Braze user attributes object.|
 | Event time property | This option lets you specify the client event property to populate the event time (in ISO-8601 format) or leave it empty to use the current time (default behavior). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Entity mapping
 
@@ -113,7 +113,7 @@ The entity can be specified in two different formats:
 | Entity mapping option | Description |
 | --------- | ----------- |
 | Include unmapped entities in event | When remapping or moving some entities to user attributes with the preceding customization, this option enables you to ensure that all unmapped entities (such as any entities not found in the [event property rules](#event-property-rules)) will be included in the properties object of the Braze event. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 [1]: https://snowplowanalytics.com
 [2]: https://docs.snowplowanalytics.com/docs/forwarding-events-to-destinations/forwarding-events/google-tag-manager-server-side/snowplow-client-for-gtm-ss/
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/tellius.md b/_docs/_partners/data_and_infrastructure_agility/analytics/tellius.md
index 25a0b1fc85b..e8948296cd0 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/tellius.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/tellius.md
@@ -21,7 +21,7 @@ The Braze and Tellius integration empowers users to leverage data, without relyi
 | Tellius account | A Tellius account is required to take advantage of this partnership. You can start your Tellius journey with a [free trial](https://www.tellius.com/free-trial/)|
 | Snowflake Data Sharing program | For current Snowflake customers, contact your Braze representative about the Snowflake Data Sharing program to pipe your Braze data into your Snowflake instance.|
 | Snowflake Reader account | For non-Snowflake customers, contact your Braze representative about a Snowflake Reader account that can be provisioned for you to access your Braze data.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/thoughtspot.md b/_docs/_partners/data_and_infrastructure_agility/analytics/thoughtspot.md
index fd970f73bbc..dce623b9931 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/thoughtspot.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/thoughtspot.md
@@ -22,7 +22,7 @@ To start using ThoughtSpot on Braze, your data needs to be sent to a cloud data
 | ----------- | ----------- |
 | ThoughtSpot account | A ThoughtSpot account is required to take advantage of this partnership. |
 | Cloud data warehouse| Braze data is stored in Cloud Data Warehouse using Braze Currents. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## TML Blocks
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/analytics/wunderkind.md b/_docs/_partners/data_and_infrastructure_agility/analytics/wunderkind.md
index 30b7b4fc75b..8fd2461c322 100644
--- a/_docs/_partners/data_and_infrastructure_agility/analytics/wunderkind.md
+++ b/_docs/_partners/data_and_infrastructure_agility/analytics/wunderkind.md
@@ -19,7 +19,7 @@ The Braze and Wunderkind integration allows you to analyze the performance lift
 | Requirement | Description |
 | ----------- | ----------- |
 | Wunderkind account | A Wunderkind account is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/business_intelligence/sisu_data.md b/_docs/_partners/data_and_infrastructure_agility/business_intelligence/sisu_data.md
index 9cfaecb9b31..8ec796c4373 100644
--- a/_docs/_partners/data_and_infrastructure_agility/business_intelligence/sisu_data.md
+++ b/_docs/_partners/data_and_infrastructure_agility/business_intelligence/sisu_data.md
@@ -19,7 +19,7 @@ The Sisu Data and Braze integration allows you to understand across all campaign
 | ----------- | ----------- |
 | Sisu account | A [Sisu][3] account is required to take advantage of this partnership. |
 | Cloud warehouse | This integration assumes your Braze data is stored in a cloud warehouse (for example, Snowflake, BigQuery). To streamline this integration process, we recommend utilizing Braze's native functionality via [Currents][4]. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/cloud_storage/amazon_s3.md b/_docs/_partners/data_and_infrastructure_agility/cloud_storage/amazon_s3.md
index bcd586a14c0..6633917d7e3 100644
--- a/_docs/_partners/data_and_infrastructure_agility/cloud_storage/amazon_s3.md
+++ b/_docs/_partners/data_and_infrastructure_agility/cloud_storage/amazon_s3.md
@@ -21,7 +21,7 @@ The Braze and Amazon S3 integration leverages [Currents]({{site.baseurl}}/user_g
 | Amazon S3 account | An Amazon S3 account is required to take advantage of this partnership. |
 | Dedicated S3 bucket | Before integrating with Amazon S3, you must create an S3 bucket for your app.<br><br>If you already have an S3 bucket, we still recommend creating a new bucket specifically for Braze so you can limit permissions. Refer to the following instructions on how to create a new bucket. |
 | Currents | In order to export data back into Amazon S3, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Create a new S3 bucket
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents.md
index 242026d1a2c..283afa8d448 100644
--- a/_docs/_partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents.md
+++ b/_docs/_partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents.md
@@ -21,7 +21,7 @@ The Braze and Google Cloud Storage integration allows you to stream Currents dat
 | ----------- | ----------- |
 | Google Cloud Storage account | A Google Cloud Storage account is required to take advantage of this partnership. |
 | Currents | In order to export data back into Google Cloud Storage, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents.md
index 8a55f439de3..1f01b6d3077 100644
--- a/_docs/_partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents.md
+++ b/_docs/_partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents.md
@@ -21,7 +21,7 @@ The Braze and Microsoft Azure Blob Storage integration allows you to export data
 | ----------- | ----------- |
 | Microsoft Azure and Azure storage account | A Microsoft Azure and Azure storage account are required to take advantage of this partnership. |
 | Currents | To export data to Currents, you must have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/cohort_import/appsflyer_audiences.md b/_docs/_partners/data_and_infrastructure_agility/cohort_import/appsflyer_audiences.md
index 940a55dd4b9..5baa6565de2 100644
--- a/_docs/_partners/data_and_infrastructure_agility/cohort_import/appsflyer_audiences.md
+++ b/_docs/_partners/data_and_infrastructure_agility/cohort_import/appsflyer_audiences.md
@@ -19,7 +19,7 @@ search_tag: Partner
 | AppsFlyer account | An AppsFlyer account is required to take advantage of this partnership. |
 | iOS or Android app | This integration supports iOS and Android apps. Depending on your platform, code snippets may be required in your application. Details on these requirements can be found in step 1 of the integration process. |
 | AppsFlyer SDK | In addition to the required Braze SDK, you must install the [AppsFlyer SDK](https://support.appsflyer.com/hc/en-us/articles/207032126-SDK-integration-overview). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Data import integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/cohort_import/heap.md b/_docs/_partners/data_and_infrastructure_agility/cohort_import/heap.md
index 7be42b4ced7..0c6d48e8832 100644
--- a/_docs/_partners/data_and_infrastructure_agility/cohort_import/heap.md
+++ b/_docs/_partners/data_and_infrastructure_agility/cohort_import/heap.md
@@ -22,7 +22,7 @@ The Braze and Heap integration enables you to [import Heap data to Braze](#data-
 | Braze Data Import key | This can be captured in the Braze dashboard from **Partner Integrations** > **Technology Partners** and then select **Heap**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
 | Braze Currents | In order to export data from Braze to Heap, you will need [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) enabled on your account. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 - Re-engage users who have abandoned a funnel: Trigger re-engagement messaging when users abandon the purchase or subscription funnel.
diff --git a/_docs/_partners/data_and_infrastructure_agility/cohort_import/tinyclues.md b/_docs/_partners/data_and_infrastructure_agility/cohort_import/tinyclues.md
index c17199eb6bf..97a5cbc9318 100644
--- a/_docs/_partners/data_and_infrastructure_agility/cohort_import/tinyclues.md
+++ b/_docs/_partners/data_and_infrastructure_agility/cohort_import/tinyclues.md
@@ -19,7 +19,7 @@ The Braze and Tinyclues integration offers users a path to better CRM planning a
 | Requirement | Description |
 |---|---|
 | Tinyclues account | A Tinyclues account is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Data import integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md b/_docs/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md
index d45bc0e25db..917c5180143 100644
--- a/_docs/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md
+++ b/_docs/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md
@@ -22,7 +22,7 @@ This feature is currently in beta. For more information, contact your Treasure D
 | Braze Data Import key | This can be captured in the Braze dashboard from **Partner Integrations** > **Technology Partners** and then select **Heap**. |
 | Braze REST endpoint | [Your REST endpoint URL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints). Your endpoint will depend on the Braze URL for your instance. |
 | Static IP Address of Treasure Data | The static IP address of Treasure Data is the access point and source of the linkage for this Integration. To determine the static IP address, contact your Treasure Data Customer Success representative or Treasure Data Technical support. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Data import integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/crash_analytics/apteligent.md b/_docs/_partners/data_and_infrastructure_agility/crash_analytics/apteligent.md
index eafe71ebc79..d0ba6501dbf 100644
--- a/_docs/_partners/data_and_infrastructure_agility/crash_analytics/apteligent.md
+++ b/_docs/_partners/data_and_infrastructure_agility/crash_analytics/apteligent.md
@@ -19,7 +19,7 @@ The Braze and Apteligent integration provides detailed iOS crash reporting, allo
 | Requirement | Description |
 |---|---|
 | TestDrive account | A TestDrive account is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert warning %}
 This integration is currently only supported on iOS.
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/actioniq.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/actioniq.md
index 07513e73296..8d51890cb46 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/actioniq.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/actioniq.md
@@ -22,7 +22,7 @@ The Braze and ActionIQ integration allows brands to sync and map their ActionIQ
 | ActionIQ account | An ActionIQ account is required to take advantage of this integration. |
 | Braze REST API key | A Braze REST API key with `users.track` and `user.export.ids` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe.md
index 1914b7ea81c..356d48ba33f 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe.md
@@ -16,4 +16,7 @@ guide_featured_list:
 - name: Event Forwarding Extension
   link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/adobe/event_forwarding_extension/
   image: /assets/img/braze_icons/arrow-square-right.svg
+- name: Adobe for Currents
+  link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe_for_currents/
+  image: /assets/img/braze_icons/building-01.svg
 ---
\ No newline at end of file
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe.md
index 1649cfcc0c9..9a19c5d68d7 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe.md
@@ -26,7 +26,7 @@ The Adobe Experience Platform integration currently doesn't support dynamic audi
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze instance | Your Braze instance can be obtained from your Braze onboarding manager or can be found on the [API overview page]({{site.baseurl}}/api/basics/#endpoints). |
 | Braze REST endpoint | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 The sending of additional custom attributes will increase your data point usage. We suggest speaking with your customer success manager to better understand this potential data point increase.
@@ -94,7 +94,7 @@ Let's say your XDM profile schema and your Braze instance contains the following
 | --- | ------------------ | -------------- |
 | Attributes | - `person.name.firstname`<br>- `person.name.lastname`<br>- `mobilePhone.number`| - `FirstName`<br>- `LastName`<br>- `PhoneNumber`|
 | Identities | - `Email`<br>- Google Ad ID (`GAID`)<br>- Apple ID For Advertisers (`IDFA`) | - `external_id` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 The correct mapping would look like this:
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe_for_currents.md
new file mode 100644
index 00000000000..21348fb88bc
--- /dev/null
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe_for_currents.md
@@ -0,0 +1,88 @@
+---
+nav_title: Adobe for Currents
+article_title: Adobe for Currents
+alias: /partners/adobe_for_currents/
+description: "This reference article outlines the partnership between Braze Currents and Adobe, a customer data platform that allows brands to connect and map their Adobe data (custom attributes and segments) to Braze in real-time."
+page_type: partner
+tool: Currents
+search_tag: Partner
+---
+
+# Adobe for Currents
+
+> [Adobe](https://www.adobe.com/) is a customer data platform that allows brands to connect and map their Adobe data (custom attributes and segments) to Braze in real time.
+
+The Braze and Adobe integration allows you to seamlessly control the flow of information between the two systems. With [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/), you can also connect data to Adobe to make it actionable across the entire growth stack. 
+
+## Prerequisites
+
+| Requirement | Description |
+| ----------- | ----------- |
+| Currents | To export data back into Adobe, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
+| Adobe Experience Platform account | An [Adobe Experience Platform account](https://experience.adobe.com/#/platform/home) is required to take advantage of this partnership. |
+| Permission to create a connector | You need permissions to create a streaming source connection to use this integration. |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+
+## Integration
+
+### Step 1: Create an XDM schema in Adobe
+
+1. In Adobe Experience Platform, go to **Schemas** > select **Create schema** > select **Experience Event** > select **Next**.<br><br>![Adobe Schemas page for the schema called "Braze Currents Walk-Through".][1]<br><br>
+2. Provide a name and description for your schema. 
+3. In the **Composition** panel, configure your schema attributes:
+- In **Field groups**, select **Add** and then add the **Braze Currents User Event** field group.
+- Select **Save**.
+
+For more information on schemas, refer to Adobe's documentation on [creating schemas](https://experienceleague.adobe.com/en/docs/experience-platform/xdm/tutorials/create-schema-ui).
+
+### Step 2: Connect Braze to the Adobe Experience Platform
+
+1. In Adobe Experience Platform, go to **Sources** > **Catalog** > **Marketing automation**.
+2. Select **Add data** for Braze Currents.
+3. Upload the [Braze Currents sample file](https://github.com/Appboy/currents-examples/blob/master/sample-data/Adobe/adobe_examples.json).<br><br>![Adobe "Add data page".][2]<br><br>
+4. After your file is uploaded, provide your dataflow details, including information about your dataset and the schema that you are mapping to. 
+    - If this is your first time connecting a Braze Currents source, create a new dataset and make sure to use the schema you created in [Step 1](#step-1-create-an-xdm-schema-in-adobe). 
+    - If this isn't your first time, use any existing dataset that references the Braze schema.
+5. Configure mapping for your data and resolve the issues.
+    - Change the mapping for `id` from `to _braze.appID` to `_id` at the root level of the schema.
+    - Make sure `properties.is_amp` is mapped to `_braze.messaging.email.isAMP`.
+    - Delete the `time` and `timestamp` mapping, then select the add icon > **Add calculated field** and enter **time * 1000**. Select **Save**.
+    - Select **Map target field** next to the new source field and map it to **timestamp** at the root level of the schema. <br><br>![Adobe "Add data" page with mappings.][3]<br><br>
+6. Select **Validate** to confirm you resolved the issues.
+
+{% alert important %}
+Braze timestamps are expressed in seconds. To accurately reflect timestamps in Adobe Experience Platform, your calculated fields need to be in milliseconds. To convert seconds to milliseconds, use the calculation **time * 1000**.
+{% endalert %}
+
+{: start="7"}
+7. Select **Next**, review your dataflow details, and then select **Finish**.<br><br>![Adobe "Add data" page with no mapping errors.][4]
+
+### Step 3: Gather credentials
+
+Collect the following creditials to input into Braze, which will allow Braze to send data to Adobe Experience Platform.
+
+| Field         |Description                          |
+|---------------|-------------------------------------|
+| Client ID     | The client ID associated with your Adobe Experience Platform source. |
+| Client Secret | The client secret associated with your Adobe Experience Platform source. |
+| Tenant ID     | The tenant ID associated with your Adobe Experience Platform source. |
+| Sandbox Name  | The sandbox associated with your Adobe Experience Platform source.   |
+| Dataflow ID   | The dataflow ID associated with your Adobe Experience Platform source.   |
+| Streaming Endpoint  | The streaming endpoint associated with your Adobe Experience Platform source. Braze automatically converts this to the batch streaming endpoint. |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+
+### Step 4: Configure Currents to stream data to your data source
+
+1. In Braze, go to **Partner Integrations** > **Data Export**, and then select **Create New Current**. 
+2. Provide the following:
+    - A name for the connector
+    - Contact information for notifications about the connector
+    - The credentials from [Step 3](#step-3-gather-credentials)
+3. Select the events you want to receive.
+4. Optionally configure any desired field exclusions or transformations.
+5. Select **Launch Current**.
+
+[1]: {% image_buster /assets/img/adobe/currents_sources.png %} 
+[2]: {% image_buster /assets/img/adobe/currents_add_data.png %}
+[3]: {% image_buster /assets/img/adobe/currents_mapping.png %}
+[4]: {% image_buster /assets/img/adobe/currents_no_errors.png %}
\ No newline at end of file
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/event_forwarding_extension.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/event_forwarding_extension.md
index 7bfbe596b6d..db79576ffcf 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/event_forwarding_extension.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/event_forwarding_extension.md
@@ -31,7 +31,7 @@ Using various [tag](https://experienceleague.adobe.com/docs/experience-platform/
 | API | Rate Limits |
 | --- | --- |
 | User Track | 50,000 requests per minute.<br><br>Refer to the [User Track API documentation]({{site.baseurl}}/api/endpoints/user_data/post_user_track#rate-limit) for details.
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -43,7 +43,7 @@ To connect the Edge Network to Braze, the following are required:
 | --- | --- |
 | Braze instance | Your Braze instance can be obtained from your Braze onboarding manager or can be found on the [API overview page]({{site.baseurl}}/api/basics/#endpoints). |
 | Braze REST API key | A Braze REST API key with all permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Step 2: Create a secret
 
@@ -69,7 +69,7 @@ After installing the extension, create a new event forwarding [rule](https://exp
 | External user ID | A long, random, and well-distributed UUID or GUID. If you choose a different method to name your user IDs, they must also be long, random, and well-distributed. Learn more about [suggested user ID naming convention]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/setting_user_ids#suggested-user-id-naming-convention). |
 | Braze user ID | Braze user identifier. |
 | User alias | An alias serves as an alternative unique user identifier. Use aliases to identify users along different dimensions than your core user ID.<br><br>The user alias object consists of two parts: an `alias_name` for the identifier itself and an `alias_label` indicating the type of alias. Users can have multiple aliases with different labels but only one `alias_name` per `alias_label`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 To tie the event to a user, you must fill in either the `External User ID` field, the `Braze User Identifier` field, or the `User Alias` section.
@@ -84,7 +84,7 @@ To tie the event to a user, you must fill in either the `External User ID` field
 | Event time | Date-time as string in ISO 8601 or in `yyyy-MM-dd'T'HH:mm:ss:SSSZ` format. | Yes |
 | App identifier | The app identifier or `app_id` is a parameter associating activity with a specific app in your workspace. It designates which app within the workspace you are interacting with. | No |
 | Event Properties | A JSON object containing custom properties of the event. | No |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 The **Braze Send Event** action requires only an **Event Name** and **Event Time** to be specified, but you should include as much information as possible in the custom properties field. Refer to [event object]({{site.baseurl}}/api/objects_filters/event_object/) for more details.
@@ -109,7 +109,7 @@ User attributes can be a JSON object containing fields that will create or updat
 | Time Zone | Time zone name from [IANA Time Zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) database (for example, ’America/New_York’ or ’Eastern Time (US & Canada)’). |
 | Facebook | A hash containing any of `id` (string), `likes` (array of strings), `num_friends` (integer). |
 | Twitter | Hash containing any of id (integer), `screen_name` (string, X (formerly Twitter) handle), `followers_count` (integer), `friends_count` (integer), `statuses_count`(integer). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 All attributes added within the configuration will be sent each time the event is sent to Braze, regardless of whether the attribute's value has changed. When configuring user attributes, ensure you know how this will affect your data point consumption.
@@ -132,7 +132,7 @@ After installing the extension, create a new event forwarding [rule](https://exp
 | External user ID | A long, random, and well-distributed UUID or GUID. If you choose a different method to name your user IDs, they must also be long, random, and well-distributed. Learn more about [suggested user ID naming convention]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/setting_user_ids#suggested-user-id-naming-convention). |
 | Braze user ID | Braze user identifier. |
 | User alias | An alias serves as an alternative unique user identifier. Use aliases to identify users along different dimensions than your core user ID.<br><br>The user alias object consists of two parts: an `alias_name` for the identifier itself and an `alias_label` indicating the type of alias. Users can have multiple aliases with different labels but only one `alias_name` per `alias_label`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 To link the event to a user, you must complete either the `External User ID` field, the `Braze User Identifier` field, or the `User Alias` section.
@@ -150,7 +150,7 @@ To link the event to a user, you must complete either the `External User ID` fie
 | Quantity | The quantity purchased. If not provided, the default value will be 1. The maximum value must be lower than 100. | No |
 | App identifier | The app identifier or `app_id` is a parameter associating activity with a specific app in your workspace. It designates which app within the workspace you are interacting with. | No |
 | Purchase properties | A JSON object containing custom properties of the purchase. | No |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert note %}
 The **Send Purchase Event** action requires only a `Product ID`, `Purchase Time`, `Currency`, and `Price` to be specified, but you should include as much information as possible in the purchase properties field. Refer to [purchase object]({{site.baseurl}}/api/objects_filters/purchase_object/) for more details.
@@ -177,7 +177,7 @@ User attributes can be a JSON object containing fields that will create or updat
 | Time zone | Time zone name from [IANA Time Zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) database (for example, ’America/New_York’ or ’Eastern Time (US & Canada)’). |
 | Facebook | A hash containing any of `id` (string), `likes` (array of strings), `num_friends` (integer). |
 | Twitter | Hash containing any of id (integer), `screen_name` (string, X (formerly Twitter) handle), `followers_count` (integer), `friends_count` (integer), `statuses_count`(integer). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 All attributes added within the configuration will be sent each time the event is sent to Braze, regardless of whether the attribute's value has changed. When configuring user attributes, please ensure you know how this will affect your data point consumption. 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/amperity.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/amperity.md
index 4bdbe5cca28..58cfab7868a 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/amperity.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/amperity.md
@@ -30,7 +30,7 @@ The Braze and Amperity integration offers a unified view of your customers acros
 | Braze instance | Your Braze instance can be obtained from your Braze onboarding manager or be found on the [API overview page]({{site.baseurl}}/api/basics#endpoints). |
 | Braze REST endpoint | Your Braze endpoint URL. Your endpoint will depend on your Braze instance. |
 | Currents connector (optional) | The S3 Currents connector. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Data mapping
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/blueconic.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/blueconic.md
index 4247c637c2b..e6b08feb0ef 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/blueconic.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/blueconic.md
@@ -28,7 +28,7 @@ When using the integration, BlueConic will send deltas (changing data) on each s
 | S3 authentication | You will need access to an Amazon Web Services (S3) server to export and import the data. |
 | Access key ID<br>Secret access key | The access key ID and secret access key will allow you to authenticate your S3 server for importing and exporting. |
 | AWS bucket | You will need to connect to S3 within the plugin. After authentication, the available buckets will show in a dropdown menu. This is where files to be imported or exported are stored. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights.md
index adb505685b9..120a095295a 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights.md
@@ -19,7 +19,7 @@ The Braze and Dynamics 365 Customer Insights integration allows you to export cu
 | ----------- | ----------- |
 | Dynamics 365 Customer Insights account | [A Dynamics 365 Customer Insights](https://dynamics.microsoft.com/en-gb/ai/customer-insights/) account is required to take advantage of this partnership. You will need access as an administrator to view and edit connections within your Dynamics 365 Customer Insights account to access the necessary plugins. |
 | Braze REST API key | A Braze REST API key is required with all permissions granted. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/ketch.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/ketch.md
index 2c185cb8ae3..294d18001bd 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/ketch.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/ketch.md
@@ -23,7 +23,7 @@ Looking for guidance on creating subscription groups? Check out our articles for
 |---|---|
 | Ketch Account | A [Ketch](https://www.ketch.com) account with admin privileges is required activate this integration. |
 | Braze API key | A Braze REST API key with `users.track`, `subscription.status.get`, `subscription.status.set`, `users.delete`, `users.alias.new`, `users.export.ids`, `email.unsubscribe`, and `email.blacklist` permissions. <br><br> This can be created in the Braze dashboard (**Developer Console** > **REST API Key** > **Create New API Key**). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/lexer.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/lexer.md
index 5bf99dcebc4..e39c0583c9f 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/lexer.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/lexer.md
@@ -21,7 +21,7 @@ The Braze and Lexer integration allows you to sync data across the two platforms
 | Braze REST API key | A Braze REST API key with all `user` permissions (excluding `user.delete`) and `segment.list` permissions. The permission set may change as Lexer adds support for more Braze objects, so you may either want to grant more permissions now or plan to update these permissions in the future.<br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | Your [REST endpoint URL]({{site.baseurl}}/api/basics/#endpoints). Your endpoint will depend on the Braze URL for your instance. |
 | Amazon AWS S3 bucket and credentials | Before beginning the integration, you must have access credentials for an AWS S3 bucket connected to your Lexer hub (this may be a bucket you create or one that Lexer creates and manages for you). Visit [Lexer](https://learn.lexer.io/docs/amazon-s3) for guidance on this requirement. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/lytics.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/lytics.md
index 78c664799d1..aaf9ebc6278 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/lytics.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/lytics.md
@@ -31,7 +31,7 @@ Connect Braze to Lytics to [import](#importing-data-from-braze-to-lytics) email,
 | Lytics API Token | A Lytics REST API Token with Data Manager permissions. <br><br> This can be created within the Lytics dashboard from **Account Settings Console** > **Access Tokens** > **Create New Token**. |
 | Braze REST API key | A Braze REST API key with `users.track` permission. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze instance | Your [Braze instance]({{site.baseurl}}/user_guide/administrative/access_braze/sdk_endpoints). Contact your Braze onboarding manager for this information if you aren't sure. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle.md
index 8d9aee61940..7b4f723fa7e 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle.md
@@ -27,7 +27,7 @@ The Braze and mParticle integration allows you to seamlessly control the flow of
 | Braze instance | Your Braze instance can be found on the [API overview page]({{site.baseurl}}/api/basics/#endpoints). (For example: US-01, US-02, etc.) |
 | Braze app identifier key | Your app identifier key. <br><br>This can be found within the **Braze Dashboard > Manage Settings > API Key**. |
 | Workspace REST API key | (Server-to-server) A Braze REST API key<br><br>This can be created within the **Braze Dashboard > Developer Console > API Settings > API Key**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -109,7 +109,7 @@ To create an audience in mParticle:
 | External identity type   | The mParticle user identity type to forward as an external ID to Braze. We recommend leaving this to the default value, Customer ID.                                          |
 | Email identity type      | The mParticle user identity type to forward as the email to Braze.                                                                                                            |
 | Braze instance           | Specify which cluster your Braze data will be forwarded to.                                                                                                                   |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {:start="3"}
 3. Lastly **Save** your audience.
@@ -148,7 +148,7 @@ In mParticle, navigate to **Setup > Outputs > Add Outputs** and selected **Braze
 | Email identity type | The mParticle user identity type to forward as an email to Braze. We recommend leaving this to the default value, Email, |
 | Braze instance | The cluster your Braze data will be forwarded to; this should be the same cluster your dashboard is on. |
 | Enable event stream forwarding | (Server-to-server) When enabled, all events will be forwarded in real-time. If not, all events will be forwarded in bulk. When choosing to enable event stream forwarding, ensure that the data you are passing to Braze will respect [rate limits]({{site.baseurl}}/api/basics/#api-limits). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][10]
 
@@ -228,7 +228,7 @@ Braze doesn't support timestamps before year 0 or after year 3000 in `Time` type
 | Custom event | Custom event | mParticle custom events are recognized by Braze as a custom event. Event attributes are forwarded as custom event properties.<br><br>Event attributes passed to Braze as event properties support string, numeric, boolean, or date objects but do not support arrays or nested objects. |
 | Purchase commerce event | Purchase event | Purchase commerce events will be mapped to Braze purchase events. <br><br>Toggle the setting value for bundle commerce event data to log purchases at the order-level or product-level. For example, if `false`, a single incoming event with two unique products, promotions, or impressions would result in at least two outgoing Braze events. If set to `true`, it would result in a single outgoing event with a nested products, promotions or impressions array, respectively.<br><br>For more information on the additional commerce fields that will be logged, see [mParticle's documentation](https://docs.mparticle.com/integrations/braze/event/#purchase-events). <br><br>When setting "bundle commerce event data" as `false` product attributes passed to Braze as purchase event properties, support string, numeric, boolean, or date objects but do not support arrays or nested objects.|
 | All other commerce events | Custom event | All other commerce events will be mapped to custom events. <br><br>Toggle the setting value for bundle commerce event data to log purchases at the order-level or product-level. For example, if `false`, a single incoming event with two unique products, promotions, or impressions would result in at least two outgoing Braze events. If set to `true`, it would result in a single outgoing event with a nested products, promotions or impressions array, respectively.<br><br>In addition to certain default commerce values, product attributes will be logged as Braze event properties. For more information on the additional commerce fields that will be logged, see [mParticle's documentation](https://docs.mparticle.com/integrations/braze/event/#other-commerce-events)<br><br>When setting "bundle commerce event data" as `false` product attributes passed to Braze as event properties, support string, numeric, boolean, or date objects but do not support arrays or nested objects. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 #### User identity mapping
 For each mParticle output, you can select the external identity type to send to Braze as the `external_id`. While the default value is customer ID, you can choose to map another ID, such as `MPID`, to send to Braze as the `external_id`. Be aware that choosing an identifier other than customer ID may influence how data is sent in Braze. 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents.md
index 0d8ad4daf1d..a01c78cb62e 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents.md
@@ -22,7 +22,7 @@ The Braze and mParticle integration allows you to seamlessly control the flow of
 | Currents | In order to export data back into mParticle, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
 | mParticle account | An [mParticle account](https://app.mparticle.com/login) is required to take advantage of this partnership. |
 | mParticle server-to-server key and secret | These can be obtained by navigating to your mParticle dashboard and creating the [necessary feeds](#step-1-create-feeds) that allow mParticle to receive Braze interaction data for iOS, Android, and Web platforms.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## About mParticle credentials
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/octolis.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/octolis.md
index b6fd9fec654..ff712680878 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/octolis.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/octolis.md
@@ -27,7 +27,7 @@ The Braze and Octolis integration acts as middleware between your raw data sourc
 | Braze REST API key | A Braze REST API key with [**users.track**][1] permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][2]. Your endpoint will depend on the Braze URL for your instance. |
 | Braze app key | Your app identifier key. This can be found within the **Braze Dashboard > Manage Settings > API Key**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -86,7 +86,7 @@ Here is a specific definition of settings fields.
 | Which fields should be synced? | Octolis to Braze fields mapping. The list of all available fields appears in the dropdown menu. To send a computed field to Braze, you must first ensure that you created the corresponding column within your Braze entity. |
 | When do you want to sync the audience? | How the data will be sent to Braze: manually, in real-time, or programmed.  |
 | Sync when record is... | Create: For opt-ins, it is important that the Braze table remains master. You don't want Octolis to trigger a sync when the field is updated.<br><br>Update: On the other hand, for a first name field, for example, you want to be able to update the field in your Braze table each time a customer gives you a new entry. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Multi-keys deduplication
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/redpoint.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/redpoint.md
index f680d81f6f1..50c291ed068 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/redpoint.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/redpoint.md
@@ -29,7 +29,7 @@ You'll configure an export template and outbound channel for each mode.
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
 | Redpoint Data Management artifacts | The Braze integration is supported by a set of Redpoint Data Management artifacts. Contact [Redpoint Support][3] to request the artifacts for your version of Redpoint Data Management. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can create an API key at **Developer Console** > **API Settings**.
@@ -46,7 +46,7 @@ The following Redpoint custom attributes can be added to a Braze user profile.
 | `rpi_offers`         | Array of offer tags where the user is targeted in a Redpoint Outbound Delivery Braze channel execution                   |
 | `rpi_contact_ids`    | Array of offer history contact IDs where the user is targeted in a Redpoint Outbound Delivery Braze channel execution     |
 | `rpi_channel_exec_ids`| Array of channel execution IDs where the user is targeted in a Redpoint Outbound Delivery Braze channel execution       |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][4]{: style="max-width:75%;"}
 
@@ -73,7 +73,7 @@ The following table lists Redpoint CDP attributes and their corresponding Braze
 | Gender             | `gender`         |
 | Primary City       | `home_city`      |
 | Primary Phone      | `phone`          |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Add the **Output Name** attribute from the **Offer History** table. Lastly, add any additional custom Redpoint attributes you want to merge into Braze. For example, the following is an onboarding and upsert template with education, income, and marital status as additional attributes.
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack.md
index e5fec4a2814..f39f7db1dc3 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack.md
@@ -22,7 +22,7 @@ The Braze and RudderStack integration offers a native SDK integration for your A
 | Braze REST API key | A Braze REST API key with `users.track`, `users.identify`, `users.delete`, and `users.alias.new` permissions.<br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze app key | To get your app key in the Braze dashboard go to **Settings** > **App Settings** > **Identification** and find your app name. Save the associated identifier string.
 | Data center | Your data center aligns with your Braze dashboard [instance][15].  |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents.md
index 016a8691603..025495c6d8d 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents.md
@@ -21,7 +21,7 @@ The Braze and RudderStack integration allows you to leverage Braze Currents to e
 | RudderStack account | A [RudderStack account](https://app.rudderstack.com/login) is required to take advantage of this partnership. |
 | Braze destination | We suggest having [set up Braze as a destination]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack/#integration) in RudderStack. |
 | Currents | To export data back into RudderStack, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment.md
index 9ddb575584c..ad2f3f33aef 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment.md
@@ -26,7 +26,7 @@ The Braze and Segment integration allows you to track your users and route data
 | ----------- | ----------- |
 | Segment account | A [Segment account](https://app.segment.com/login) is required to take advantage of this partnership. |
 | Installed source and Segment source [libraries](https://segment.com/docs/sources/) | The origin of any data sent into Segment, such as mobile apps, websites, or backend servers.<br><br>You must install the libraries into your app, site, or server before being able to set up a successful `Source > Destination` flow. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -50,7 +50,7 @@ Your choice of connection mode will be determined by the type of Source the dest
 | ----------- | ------- |
 | [Side-by-side<br>(device-mode)](#side-by-side-sdk-integration) |Uses Segment's SDK to translate events into Braze's native calls, allowing access to deeper features and more comprehensive usage of Braze than the server-to-server integration.<br><br>Note that Segment does not support all Braze methods (for example, Content Cards). To use a Braze method that isn't mapped through a corresponding mapping, you will have to invoke the method by adding native Braze code to your codebase. |
 | [Server-to-server<br>(cloud-mode)](#server-to-server-integration) | Forwards data from Segment to Braze REST API endpoints.<br><br>Does not support Braze UI features such as in-app messaging, Content Cards, or push notifications. There also exists automatically captured data, such as device-level fields, that are unavailable through this method.<br><br>Consider a side-by-side integration if you wish to use these features.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 Visit [Segment](https://segment.com/docs/destinations/#connection-modes) to learn more about the two integration options (connection modes), including the benefits of each.
@@ -79,7 +79,7 @@ The Braze SDK you use will depend on which Segment SDK you use:
 | - | ----------- | --------- |
 | Preferred | [Analytics-Kotlin](https://github.com/segmentio/analytics-kotlin) | [Braze Segment Kotlin](https://github.com/braze-inc/braze-segment-kotlin) |
 | Legacy | [Analytics-Android](https://github.com/segmentio/analytics-android) | [Braze Segment Android](https://github.com/braze-inc/braze-segment-android) |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 {% endalert %}
@@ -105,7 +105,7 @@ The Braze SDK you use will depend on which Segment SDK you use:
 | - | ----------- | --------- |
 | Preferred | [Analytics-Swift](https://github.com/segmentio/analytics-swift) | [Braze Segment Swift](https://github.com/braze-inc/braze-segment-swift) |
 | Legacy | [Analytics-iOS](https://github.com/segmentio/analytics-ios) | [Braze Segment iOS](https://github.com/Appboy/appboy-segment-ios) |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endalert %}
 
 To set up Braze as a device-mode destination for your iOS source, choose **Classic** as the Destination framework and click **Save**. 
@@ -167,7 +167,7 @@ Define the settings for your destination. Not at all settings will apply to all
 | Custom API endpoint<br>(SDK endpoint) | Your Braze SDK endpoint that corresponds to your instance (such as `sdk.iad-01.braze.com`) | 
 | Endpoint region | Your Braze instance (such as US 01, US 02, EU 01, etc.) | 
 | Enable automatic in-app message registration | Disable this if you want to manually register in-app messages. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Web Device-Mode %}
@@ -202,7 +202,7 @@ Define the settings for your destination. Not at all settings will apply to all
 | Track only named pages | **Classic Destination Web Device-Mode (maintenance) Only**<br><br>Segment recommends migrating to the Web Actions framework destination where this setting can be [enabled through mappings](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping).<br><br>This will send only page calls to Braze with a name associated with them. |
 | Log purchase when revenue is present | **Classic Destination Web Device-Mode (maintenance) Only**<br><br>Segment recommends migrating to the Web Actions framework destination where this setting can be [enabled through mappings](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping).<br><br>When this option is enabled, all Track calls with the revenue property will trigger a purchase event. | 
 | Only track known users | **Classic Destination Web Device-Mode (maintenance) Only**<br><br>Segment recommends migrating to the Web Actions Framework destination where this setting can be enabled through mappings.<br><br>If enabled, this new setting delays calling of `window.appboy.initialize` until there is a valid `userId`. | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Cloud-Mode %}
@@ -213,7 +213,7 @@ Define the settings for your destination. Not at all settings will apply to all
 | REST API key | This can be found in your Braze dashboard under **Settings** > **API Keys**. | 
 | Custom REST API endpoint | Your Braze REST endpoint that corresponds to your instance (such as rest.iad-01.braze.com). | 
 | Update existing users only | **Classic Destination Cloud-Mode (Maintenance) Only**<br><br>Segment recommends migrating to the Cloud Actions Framework destination where this setting can be [enabled through mappings](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping).<br><br>Determines whether to update existing users only. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
@@ -231,7 +231,7 @@ Although user aliases are supported as an identifier in the Braze Cloud Mode (Ac
 | `userId` (`external_id`) | All |
 | Anonymous user | Device mode destinations |
 | User alias | Cloud mode destinations |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 The Cloud Mode (Actions) Destination offers a [Create Alias action](https://segment.com/docs/connections/destinations/catalog/actions-braze-cloud/#create-alias) that can be used to create an alias-only user or add an alias to an existing `external_id` profile. The [Identify User action](https://segment.com/docs/connections/destinations/catalog/actions-braze-cloud/#identify-user) can be used alongside the Create Alias action to merge an alias-only user with an `external_id` after one becomes available for the user. 
 
@@ -260,7 +260,7 @@ Certain Segment special traits map to standard attribute profile fields in Braze
 | `address.country` | `country` |
 | `address.city` | `home_city` |
 | `gender` | `gender` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Other reserved Braze profile fields such as `email_subscribe` and `push_subscribe` can be sent by using the Braze naming convention for these fields and passing them as traits within an identify call.
 
@@ -348,7 +348,7 @@ All other traits will be recorded as [custom attributes]({{site.baseurl}}/user_g
 | Identify with reserved traits | Set user attributes | Segment: `analytics.identify({email: "dawei@braze.com"});`<br> Braze: `Braze.getUser().setEmail("dawei@braze.com");`
 | Identify with custom traits | Set custom attributes | Segment: `analytics.identify({fav_cartoon: "Naruto"});`<br>Braze: `Braze.getUser().setCustomAttribute("fav_cartoon": "Naruto")`;
 | Identify with user ID and traits | Segment: Set External ID and Attribute | Combine preceding methods. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 In the [Web Mode Actions](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#update-user-profile) and [Cloud Mode Actions](https://segment.com/docs/connections/destinations/catalog/braze-cloud-mode-actions/#update-user-profile) destinations, the above mappings can be set using the Update User Profile Action.
 
@@ -372,7 +372,7 @@ In the [Web Mode Actions](https://segment.com/docs/connections/destinations/cata
 | [Track](https://segment.com/docs/spec/track/) | Logged as a [Custom Event]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-events). | Segment: `analytics.track("played_game");` <br>Braze: `Braze.logCustomEvent("played_game");`|
 | [Track with properties](https://segment.com/docs/spec/track/) | Logged as [Event Property]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-properties). | Segment: `analytics.track("played_game", {name: "BotW", weapon: "boomerang"});` <br>Braze: `Braze.logCustomEvent("played_game", { "name": "BotW", "weapon": "boomerang"});` |
 | [Track with product](https://segment.com/docs/spec/track/) | Logged as a [Purchase Event]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/logging_purchases/). | Segment: `analytics.track("Order Completed", {products: [product_id: "ab12", price: 19]});` <br>Braze: `Braze.logPurchase("ab12", 19);` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ##### Order completed {#order-completed}
 
@@ -436,7 +436,7 @@ Segment **does not** limit the number of data elements clients send to them. Seg
 | ----------------- | ------------------ |
 | Braze SDK endpoint | Custom API endpoint |
 | Braze REST endpoint | Custom REST API endpoint |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your Braze API endpoint (called the "Custom API Endpoint" in Segment) is the SDK endpoint that Braze sets up for your SDK (for example, `sdk.iad-03.braze.com`). Your Braze REST API endpoint (called the "Custom REST API Endpoint" in Segment) is the REST API endpoint (for example, `https://rest.iad-03.braze.com`)
 {% enddetails %}
@@ -447,7 +447,7 @@ Your Braze API endpoint (called the "Custom API Endpoint" in Segment) is the SDK
 | ----------------- | ------------------ |
 | Braze SDK endpoint | Custom API endpoint |
 | Braze REST endpoint | Custom REST API endpoint |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 The proper format must be followed to ensure that you input your Braze SDK endpoint correctly. Your Braze SDK endpoint must not include `https://` (for example, `sdk.iad-03.braze.com`), or else the Braze integration will break. This is required because Segment automatically prepends your endpoint with `https://`, resulting in Braze initializing with an invalid endpoint `https://https://sdk.iad-03.braze.com`.
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage.md
index 251bab5a453..2c0165aead1 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage.md
@@ -26,7 +26,7 @@ The Braze and Segment integration allows you to use [Engage](https://segment.com
 | Braze Cloud destination | You must have already [set up Braze as a destination]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings/) in your Segment integration.<br><br>This includes providing the correct Braze data center and REST API key in your [connection settings]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings). |
 | Braze data import key | To sync Engage audiences to Braze as cohorts, you must generate a Data Import key.<br><br>Cohort import is in early access, contact your Braze customer success manager to get access to this feature. |
 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Cohorts Destination integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_for_currents.md
index bdfdd7ee71a..fd8a7e4262d 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_for_currents.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_for_currents.md
@@ -23,7 +23,7 @@ The Braze and Segment integration allows you to leverage Braze Currents to expor
 | Segment account | A [Segment account](https://app.segment.com/login) is required to take advantage of this partnership. |
 | Braze destination | You must have already [set up Braze as a destination]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings/) in your Segment integration.<br><br>This includes providing the correct Braze data center and REST API key in your [connection settings]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings). |
 | Currents | In order to export data back into Segment, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/simondata.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/simondata.md
index b1ca9bad8a4..205013b4fcb 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/simondata.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/simondata.md
@@ -22,7 +22,7 @@ To get started, you need to authenticate your Braze account within your Simon Da
 | Simon Data          | You must have an existing Simon Data account to leverage the Braze integration from within Simon Data.                                                                    |
 | Braze REST API key  | A Braze REST API key with `users.track`, `campaigns.trigger.schedule.create`, and `campaigns.trigger.send` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze Dashboard URL | [Your REST endpoint URL][3]. Your endpoint will depend on the Braze URL for your instance.                                                                                |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium.md
index a07d53ff00b..9cb2b2513ef 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium.md
@@ -62,7 +62,7 @@ Tealium does not batch consent events (subscription preferences) or user deletio
 | Braze app identifier key (side-by-side only) | Your app identifier key. <br><br>This can be found within the **Braze Dashboard > Manage Settings > API Key**. |
 | Code version (side-by-side only) | Corresponds to SDK version and should be in major.minor format (for example, 3.2 not 3.0.1). The code version should be 3.0 or higher. |
 | REST API key (server-to-server only) | A Braze REST API key with `users.track` and `users.delete` permissions. <br><br>This can be created within **Braze Dashboard > Developer Console > REST API Key > Create New API Key**.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Choose your integration type
 
@@ -70,7 +70,7 @@ Tealium does not batch consent events (subscription preferences) or user deletio
 | ----------- | ------- |
 | [Side-by-side](#side-by-side-sdk-integration) | Uses Tealium's SDK to translate events into Braze's native calls, allowing access to deeper features and more comprehensive usage of Braze than the server-to-server integration.<br><br>If you plan on using Braze remote commands, note that Tealium does not support all Braze methods (for example, Content Cards). To use a Braze method that isn't mapped through a corresponding remote command, you will have to invoke the method by adding native Braze code to your codebase.|
 | [Server-to-server](#server-to-server-integration) | Forwards data from Tealium to Braze's REST API endpoints.<br><br>Does not support Braze UI features such as in-app messaging,  Content Cards, or push notifications. There also exists automatically captured data, such as device-level fields, that are not available through this method.<br><br>Consider a side-by-side integration if you wish to use these features.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Side-by-side SDK integration
 
@@ -84,7 +84,7 @@ Tealium offers two ways to integrate Mobile Remote Command, there is no loss of
 | --- | --- | --- |
 | **Remote command tag** | Easily modify the mappings and data sent to the remote command using the Tealium iQ UI.<br><br>This allows us to send additional data or events to a 3rd party SDK after the app is already in the app store, without the client having to update the app. | The Tag Management module in the app relies on a hidden webview to process JavaScript. |
 | **JSON configuration file**<br>([Recommended](https://docs.tealium.com/platforms/remote-commands/integrations/braze/#how-it-works)) | Using the JSON method eliminates the need to have a hidden webview in the app and greatly reduces memory consumption.<br><br>The JSON file can be hosted remotely or locally within the customer's app. | At the moment, there is no UI to manage this, so it requires a bit of extra effort.<br><br>Note: Tealium is working on adding a management UI that will solve this issue and bring the same level of flexibility to JSON remote commands as they have with the iQ Tag management version |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Use Braze mobile remote command data mappings to set default user attributes and custom attributes and track purchases and custom events. Refer to the following chart for corresponding Braze methods.
 
@@ -105,7 +105,7 @@ Use Braze mobile remote command data mappings to set default user attributes and
 | useralias | addAlias() |
 | userattribute | ABKUser() |
 | useridentifier | changeUser() |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 You can find more details on how to set up Braze mobile remote command and an overview of supported methods in the Tealium developer documentation:
 - [Remote command](https://docs.tealium.com/platforms/remote-commands/integrations/braze/#json-template)
@@ -205,7 +205,7 @@ This action allows you to track user, event, and purchase attributes all in one
 | Purchase | Use this field to track and map user purchase attributes like those in the Braze [purchase object]({{site.baseurl}}/api/objects_filters/purchase_object/).<br><br>- Purchase attributes `Product ID`, `Currency`, and `Price` are required for every mapped purchase.<br>- Purchase attribute `Time` is automatically set to now unless explicitly mapped.<br>- By default, new purchases will be created if one does not exist. By setting `Update Existing Only` to `true`, only existing purchases will be updated, and no new purchase will be created.<br>- Map array type attributes to add multiple purchase items. Array type attributes must be of equal length.<br>- Single value attributes can be used and will apply to each item.|
 | Purchase template | Templates can be used to transform data prior to it being sent to Braze.<br>- Define a purchase template if you need nested objects support.<br>- When a purchase template is defined, the configuration set up in the purchases section of your action will be ignored.<br>- Refer to Tealium's [Templates Guide](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/) to learn more.|
 | Purchase template variable | Provide product template variables as data input. Refer to Tealium's [Template Variables Guide](https://docs.tealium.com/server-side/connectors/webhook-connectors/template-variables/) to learn more. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![]({% image_buster /assets/img/tealium/track_user_example.png %})
 
@@ -217,7 +217,7 @@ This action allows you to delete users from the Braze dashboard.
 | Parameters | Description |
 | ---------- | ----------- |
 | User ID | Use this field to map the Tealium User ID field to it's Braze equivalent. <br><br>- Map one or more user ID attributes. When multiple IDs are specified, the first non-blank value is picked based on the following priority order: External ID, Braze ID, Alias Name, and Alias Label.<br>- When specifying a user alias, Alias Name and Alias Label should both be set.<br><br>For more information, see the Braze [`/users/delete` endpoint]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![]({% image_buster /assets/img/tealium/track_user_delete.png %})
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream.md
index 897167d7218..2fd610f3b2e 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream.md
@@ -26,7 +26,7 @@ Tealium AudienceStreams and EventStreams offer both batch and non-batch connecto
 | Tealium account | A [Tealium account](https://my.tealiumiq.com/) with server-side access is required. We recommend also using the client-side integrations to take advantage of this partnership. |
 | REST API key | A Braze REST API key with `users.track`, `users.delete`, and `subscription.status.set` permissions.<br><br>This can be created within **Braze dashboard > Developer Console > REST API Key > Create New API Key**|
 | [Braze REST endpoint][6] | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -144,7 +144,7 @@ Not all fields offered are required.
 {% endalert %}
 
 {% tabs local %}
-{% tab Track User (Batch and Non-Batch) %}
+{% tab Track User - Batch and Non-Batch %}
 
 This action allows you to track user, event, and purchase attributes all in one action. Although the Track User action is the same for both AudienceStream and EventStream, Tealium recommends setting user attribute mappings with AudienceStream actions and the event and purchase mappings with EventStream actions.
 
@@ -159,24 +159,24 @@ This action allows you to track user, event, and purchase attributes all in one
 | Purchase | Use this field to track and map user purchase attributes like those in the Braze [purchase object]({{site.baseurl}}/api/objects_filters/purchase_object/).<br><br>- Purchase attributes `Product ID`, `Currency`, and `Price` are required for every mapped purchase.<br>- Purchase attribute `Time` is automatically set to now unless explicitly mapped.<br>- By default, new purchases will be created if one does not exist. By setting `Update Existing Only` to `true`, only existing purchases will be updated, and no new purchase will be created.<br>- Map array type attributes to add multiple purchase items. Array type attributes must be of equal length.<br>- Single value attributes can be used and will apply to each item.|
 | Purchase template | Templates can be used to transform data prior to it being sent to Braze.<br>- Define a purchase template if you need nested objects support.<br>- When a purchase template is defined, the configuration set up in the purchases section of your action will be ignored.<br>- Refer to Tealium's [Templates Guide](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/) to learn more.|
 | Purchase template variable | Provide product template variables as data input. Refer to Tealium's [Template Variables Guide](https://docs.tealium.com/server-side/connectors/webhook-connectors/template-variables/) to learn more. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![]({% image_buster /assets/img/tealium/track_user_example2.png %}){: style="max-width:90%"}
 
 {% endtab %}
-{% tab Delete User (Non-Batch) %}
+{% tab Delete User - Non-Batch %}
 
 This action allows you to delete users from the Braze dashboard.
 
 | Parameters | Description |
 | ---------- | ----------- |
 | User ID | Use this field to map the Tealium User ID field to its Braze equivalent.<br><br>- Map one or more user ID attributes. When multiple IDs are specified, the first non-blank value is picked based on the following priority order: External ID, Braze ID, Alias Name, and Alias Label.<br>- When specifying a user alias, Alias Name and Alias Label should both be set.<br><br>For more information, see the Braze [`/users/delete` endpoint]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![]({% image_buster /assets/img/tealium/track_user_delete2.png %}){: style="max-width:90%"}
 
 {% endtab %}
-{% tab Update User Subscription Group Status (Non-Batch) %}
+{% tab Update User Subscription Group Status - Non-Batch %}
 This action allows you to add or remove users from Braze SMS or email subscription groups.
 
 | Parameters | Description |
@@ -184,7 +184,7 @@ This action allows you to add or remove users from Braze SMS or email subscripti
 | Group type | Use this field to denote if this is an SMS or Email subscription group. |
 | Update type | Map this action to an unsubscribe or subscription event 
 | Attributes | - Subscription group ID (required): The ID of the subscription group related to the group type mapped in the preceding field.<br>- External ID: The external ID of the user.<br><br>Email group specific:<br>- Email: The email address of the user.<br>**If the external ID is not defined, the email will be required.**<br><br>SMS group specific:<br>- Phone: The phone number in E.164 format. For example, +14155552671.<br>**If the external ID is not defined, the phone will be required.** |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![]({% image_buster /assets/img/tealium/update_subscription.png %}){: style="max-width:90%"}
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents.md
index c5338ef3884..87e66771d66 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents.md
@@ -23,7 +23,7 @@ The Braze and Tealium integration allows you to seamlessly control the flow of i
 | Tealium EventStream or Tealium AudienceStream | A [Tealium account](https://my.tealiumiq.com/) is required to take advantage of this partnership. |
 | Currents | In order to export data back into Tealium, you need to have [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) set up for your account. |
 | Tealium URL | These can be obtained by navigating to your Tealium dashboard and copying the ingestion URL.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/toovio.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/toovio.md
index 3f392abff35..d246a1868b9 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/toovio.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/toovio.md
@@ -21,7 +21,7 @@ The Braze and Toovio partnership provides near real-time message triggering, the
 | Toovio account | A Toovio account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze Currents | Braze Currents allows Braze clients to stream event or behavior data to a Braze data partner (AWS S3, Google Cloud Storage, or Microsoft Azure Blob Storage) for processing external to the Braze platform. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data.md
index 894c61c6942..dd4de14a82a 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data.md
@@ -24,7 +24,7 @@ The Braze and Treasure Data integration allows you to write job results from Tre
 | Treasure Data account | A [Treasure Data account](https://www.treasuredata.com/custom-demo/) is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track`, `users.delete`, `users.alias.new`, `users.identify` permissions.<br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][1]. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Use cases
 
@@ -68,7 +68,7 @@ The export results parameters are included in the following table:
 | `pre_formatted_fields`    | String | Use for array or JSON columns to keep the format. |
 | `track_record_type`       | Custom Events<br>Purchases<br>User Profile Attributes| Record type for **User - Track** mode |
 | `skip_on_invalid_records` | Boolean | If enabled, continue and ignore any invalid records for the JSON column. <br> Otherwise, the job stops. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert note %}
 Visit [Treasure Data](https://docs.treasuredata.com/display/public/INT/Braze+Export+Integration) for more information about pre-formatted fields, example queries, parameter details, and query export job scheduling.
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data_for_currents.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data_for_currents.md
index bd06f7687ba..faf91a34d7a 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data_for_currents.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data_for_currents.md
@@ -23,7 +23,7 @@ The Braze and Treasure Data integration allows you to seamlessly control the flo
 | Treasure Data | A [Treasure Data account][0] is required to take advantage of this partnership. |
 | Currents | To export data back into Treasure Data, you need to have [Braze Currents][2] set up for your account. |
 | Treasure Data URL | This can be obtained by navigating to your Treasure Data dashboard and copying the ingestion URL.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 Treasure Data logs each event in batches. For more information on how to query Treasure Data to get event counts, refer to [Braze Currents Import Integration](https://docs.treasuredata.com/articles/#!int/braze-currents-import-integration).
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/symphony.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/symphony.md
index 01f3f38c591..4a19954a18f 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/symphony.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/symphony.md
@@ -24,7 +24,7 @@ To create email marketing campaigns, onboard the raw emails to Zeotap by mapping
 | Client Name | This is your client name for your Braze account. You can find it by navigating to the Braze Console. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Instance | Your Braze instance can be obtained from your Braze onboarding manager or can be found on the [API overview page]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Integration
 
@@ -109,7 +109,7 @@ You can find details of all the Braze fields in this section.
 | Language | Dropdown selection | • The accepted format is `ISO-639-1` standard (for example, en).<br>• Onboard correctly formatted language and map to it. |
 | Date of Birth | Dropdown selection | Map to the `Date of Birth` field you are onboarding. |
 | Custom Attribute | Custom Data Input | Map any user attribute to a custom data input, which is then sent to Braze. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Viewing data on Braze console
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/zeotap.md b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/zeotap.md
index 1cb6288355c..c983795ad15 100644
--- a/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/zeotap.md
+++ b/_docs/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/zeotap.md
@@ -19,7 +19,7 @@ With the Zeotap and Braze integration, you can extend the scale and reach of you
 |Zeotap account | A [Zeotap account](https://zeotap.com/) is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][1]. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md b/_docs/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md
index 288c1e276e6..6b3aa24dd4e 100644
--- a/_docs/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md
+++ b/_docs/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md
@@ -21,7 +21,7 @@ The Braze and DataGrail integration allows you to detect consumer data collected
 | DataGrail account | A DataGrail account to take advantage of this partnership.<br>Contact your admin or email support@datagrail.io with any issues or questions regarding the integration. |
 | Braze API key | A Braze REST API key with `events.list`, `users.export.ids`, `users.delete`, and `users.track` permissions.<br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze instance | Your Braze instance can be obtained from your Braze onboarding manager or can be found on the [API overview page]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/data_privacy/onetrust.md b/_docs/_partners/data_and_infrastructure_agility/data_privacy/onetrust.md
index 6d480937800..cf34ea991ef 100644
--- a/_docs/_partners/data_and_infrastructure_agility/data_privacy/onetrust.md
+++ b/_docs/_partners/data_and_infrastructure_agility/data_privacy/onetrust.md
@@ -20,7 +20,7 @@ The Braze and OneTrust integration allows you to use the OneTrust workflow build
 | OneTrust account | A [OneTrust](https://www.onetrust.com/) account to take advantage of this partnership. |
 | Braze API key | A Braze REST API key with permissions required for the endpoint your OneTrust action will use.<br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze instance | Your Braze instance can be obtained from your Braze onboarding manager or can be found on the [API overview page]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/data_privacy/transcend.md b/_docs/_partners/data_and_infrastructure_agility/data_privacy/transcend.md
index fbfb4f63f5f..1166dfd3e48 100644
--- a/_docs/_partners/data_and_infrastructure_agility/data_privacy/transcend.md
+++ b/_docs/_partners/data_and_infrastructure_agility/data_privacy/transcend.md
@@ -20,7 +20,7 @@ The Braze and Transcend partnership helps users automate privacy requests by orc
 |---|---|
 | Transcend account | A [Transcend](https://app.transcend.io/) account with admin privileges is required to take advantage of this partnership. |
 | Braze API key | A Braze REST API key with `users.delete, users.alias.new, users.export.ids, email.unsubscribe,`and `email.blacklist` permissions.<br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/data_warehouses/snowflake.md b/_docs/_partners/data_and_infrastructure_agility/data_warehouses/snowflake.md
index 5bcb8f01694..a94e9451ea4 100644
--- a/_docs/_partners/data_and_infrastructure_agility/data_warehouses/snowflake.md
+++ b/_docs/_partners/data_and_infrastructure_agility/data_warehouses/snowflake.md
@@ -41,7 +41,7 @@ If you are interested in this integration, reach out to your Braze Account or cu
 | Requirement | Description |
 | ----------- | ----------- |
 | Snowflake account | A Snowflake account with admin-level permissions is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -79,7 +79,7 @@ Note the following differences between Braze and Snowflake naming conventions fo
 | ----------- | ----------- | ----------- |
 | `braze_id` | `"USER_ID"` | The unique identifier that is automatically assigned by Braze. |
 | `external_id` | `"EXTERNAL_USER_ID"` | The unique identifier of a user's profile that is set by the customer. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Important information and limitations
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier.md b/_docs/_partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier.md
index 91b3f272731..d81ef3d4ba6 100644
--- a/_docs/_partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier.md
+++ b/_docs/_partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier.md
@@ -25,7 +25,7 @@ Facebook Lead Ads is an ad format that allows businesses to collect lead informa
 | <a href="https://www.facebook.com/business/help/183277585892925?id=420299598837059/" target="_blank">Facebook Page</a> | You will need an active Facebook Page tied to your brand’s business manager. <br><br>Ensure that you have the "Manage Pages" permissions for each Facebook Page you plan to use with Braze. |
 | Braze REST endpoint | Ensure you know your [REST endpoint URL][1]. Your API endpoint matches the dashboard URL for your Braze instance. <br><br> For example, if your dashboard URL is `https://dashboard-03.braze.com`, your endpoint will be `dashboard-03`. |
 | Braze REST API key | Ensure you have a Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/payments/revenuecat.md b/_docs/_partners/data_and_infrastructure_agility/payments/revenuecat.md
index 42e61af3353..fdf2fa2de4a 100644
--- a/_docs/_partners/data_and_infrastructure_agility/payments/revenuecat.md
+++ b/_docs/_partners/data_and_infrastructure_agility/payments/revenuecat.md
@@ -25,7 +25,7 @@ At a minimum, you will need to enable the integration from the RevenueCat dashbo
 | Braze instance | Your Braze instance can be obtained from your Braze onboarding manager or can be found on the [API overview page]({{site.baseurl}}/api/basics/#endpoints).<br><br>RevenueCat requires the Braze instance to send server-side to the correct Braze REST endpoint. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze test REST API key (optional) | A test API key can be used for test and production purchases if you'd like these requests sent to separate Braze instances. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use Cases 
 
@@ -96,7 +96,7 @@ If you want to send an alternative unique user identifier different from the Rev
 |---|---|
 | `$brazeAliasName` | The Braze `alias_name` in the [user alias object][2] |
 | `$brazeAliasLabel` | The Braze `alias_label` in the [user alias object][2] |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Both attributes are required for the [user alias object][2] to be sent alongside your event data. These properties can be set manually, like any other [RevenueCat subscriber attribute][4]. Example code snippets are shown in step one.
 
@@ -126,7 +126,7 @@ Enter the event names that RevenueCat will send or select from the default event
 | Non Subscription Purchase | The purchase of any product that's not an auto-renewing subscription. |
 | Expiration | When a subscription expires. |
 | Billing Issue | When there has been a problem trying to charge the user. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For events that include revenue, RevenueCat will automatically record this amount along with the event in Braze, such as trial conversions and renewals.
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/support/pypestream.md b/_docs/_partners/data_and_infrastructure_agility/support/pypestream.md
index 1fa7794047d..b828a878db5 100644
--- a/_docs/_partners/data_and_infrastructure_agility/support/pypestream.md
+++ b/_docs/_partners/data_and_infrastructure_agility/support/pypestream.md
@@ -21,7 +21,7 @@ The Braze and Pypestream integration allows you to seamlessly orchestrate the en
 | Pypestream account | A [Pypestream account](https://www.pypestream.com/contact-us/) is required to take advantage of this partnership.<br><br>Once subscribed, the Pypestream team will help you set up your dedicated environment to begin building your conversational AI solution to integrate with Braze. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance]({{site.baseurl}}/api/basics/). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/support/zendesk.md b/_docs/_partners/data_and_infrastructure_agility/support/zendesk.md
index 86d585a4805..bc252b973eb 100644
--- a/_docs/_partners/data_and_infrastructure_agility/support/zendesk.md
+++ b/_docs/_partners/data_and_infrastructure_agility/support/zendesk.md
@@ -24,7 +24,7 @@ The Braze and Zendesk server-to-server integration allows you to utilize:
 | Zendesk API token | A Zendesk [API token][2] is required to send requests from Braze to the Zendesk ticket endpoint. |
 | Common identifier (recommended) | A [common identifier](#common-identifier) between Braze and Zendesk is recommended. |
 | Braze API key | A Braze API key is required to send requests from Zendesk to a Braze endpoint. Ensure that the API key you use has the correct permissions for the Braze endpoint your Zendesk webhook is using. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Braze to Zendesk integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/airbyte.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/airbyte.md
index 00eb26fd8e4..1c72443ba6b 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/airbyte.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/airbyte.md
@@ -21,7 +21,7 @@ The Braze and Airbyte integration allows users to create a data pipeline to coll
 | Airbyte Cloud account | An [Airbyte Cloud](https://cloud.airbyte.io/workspaces) account is required to take advantage of this integration. |
 | Braze REST API key | A Braze REST API key with all permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/census.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/census.md
index 4d703e8d49e..9ec757d2175 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/census.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/census.md
@@ -22,7 +22,7 @@ The Braze and Census integration allows you to dynamically import audiences or p
 | Braze REST API key | A Braze REST API key with all user data permissions (except for `users.delete`) and `segments.list` permissions. The permissions set may change as Census adds support for more Braze objects, so you may either want to grant more permissions now or plan to update these permissions in the future. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][2]. |
 | Data warehouse and data model | Before beginning the integration, you must have a data warehouse set up in Census and define a model of the subset of data you want to sync to Braze. Visit [Census documentation](https://docs.getcensus.com/destinations/braze) for a list of available data sources and guidance on model creation. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Integration
 
@@ -63,7 +63,7 @@ Census currently supports syncing of the following Braze objects:
 | Catalog | Update, Create, Mirror |
 | Subscription Group Membership | Mirror |
 | Event | Append |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Additionally, Census supports sending [structured data](https://docs.getcensus.com/destinations/braze#supported-objects) to Braze: 
 - User push tokens: To send push tokens, your data should be structured as an array of objects with 2-3 values: `app_id`, `token`, and an optional `device_id`.
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md
index 29bebf07451..51f6f2dd723 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md
@@ -24,7 +24,7 @@ The Braze and Fivetran integration allows users to create a zero-maintenance pip
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][1]. |
 | Braze Currents | [Braze Currents](https://www.braze.com/product/data-agility-management/currents/) should be connected to either Amazon S3 or Google Cloud Storage. |
 | Amazon S3 or Google Cloud Storage | This integration requires you have access to one Amazon S3 or Google Cloud Storage. |
-{: .reset-td-br-1 .reset-td-br-2} 
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" } 
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/growthloop.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/growthloop.md
index d55d7cf7196..bacb0859aec 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/growthloop.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/growthloop.md
@@ -21,7 +21,7 @@ The Braze and GrowthLoop integration allows you to segment customer data directl
 | GrowthLoop growth or enterprise account | A GrowthLoop account is required to take advantage of this partnership. |
 | Braze Rest API key | A Braze REST API key with all permissions.<br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][2].|
-{: .reset-td-br-1 .reset-td-br-2} 
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" } 
 
 ## Use cases
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch.md
index 031f3790f82..68780192da4 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch.md
@@ -22,7 +22,7 @@ This integration also allows you to [import user cohorts to Braze]({{site.baseur
 | Hightouch account | A Hightouch account is required to take advantage of this partnership.
 | Braze REST API key | A Braze REST API key with `users.track` and `users.export.ids` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][2].<br><br>Hightouch requires the name of the cluster your Braze instance sits on. For example, if your Braze endpoint is `https://rest.iad-01.braze.com`, you only need `iad-01`.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch_personalization_api.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch_personalization_api.md
index f00fbe3aa3a..0f44d6a26c0 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch_personalization_api.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch_personalization_api.md
@@ -26,7 +26,7 @@ Hightouch's Personalization API provides a REST endpoint to use within your Braz
 | Defined use cases | Before setting up the API, you must determine your use case for this integration. Reference the following list for common use cases. |
 | Data stored in a cloud data warehouse or other source | Hightouch integrates with [over 25+ data sources](https://hightouch.com/integrations) |
 | Hightouch API key | This can be created within **Hightouch > Settings > API keys > Add API key**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% tabs %}
 {% tab Use Cases %}
@@ -170,7 +170,7 @@ The following Liquid references would return this example data:
 | {% raw %}`{{artists.recommendations.concerts[0].artist}}`{% endraw %}| Aphex Twin |
 | {% raw %}`{{artists.recommendations.concerts[0].location}}`{% endraw %}| San Francisco, CA |
 | {% raw %}`{{artists.recommendations.upcoming_album_release.title}}`{% endraw %}| Universal Language |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Troubleshooting
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/metarouter.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/metarouter.md
index 606e5a3a3c9..c0a39c60ffc 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/metarouter.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/metarouter.md
@@ -30,7 +30,7 @@ Before you start, you'll need the following:
 | A MetaRouter account  | A [MetaRouter Enterprise account](https://enterprise.metarouter.io/).                                                                                |
 | Braze REST API key    | A Braze REST API key with `users.track` permissions. To create one go to **Settings** > **API Keys**.                                                |
 | A Braze REST endpoint | [Your REST endpoint URL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints). Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 If you're using the [older navigation]({{site.baseurl}}/navigation), you can create an API key at **Developer Console** > **API Settings**.
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/mozart_data.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/mozart_data.md
index 4319cbc7f51..52767a49d0c 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/mozart_data.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/mozart_data.md
@@ -40,7 +40,7 @@ table td {
 | Mozart Data account | A Mozart Data account is required to take advantage of this partnership. [Sign up here.](https://app.mozartdata.com/signup)|
 | Snowflake Account<br>Option 1: New Account | Select **Create a New Snowflake Account** during the Mozart Data account creation process for Mozart Data to provision a new Snowflake account for you. |
 | Snowflake Account<br>Option 2: Existing Account | If your organization already has a Snowflake account, you can use the Mozart Data Connected option.<br><br>Select the **Already Have a Snowflake Account** option to connect an existing Snowflake account. To pursue this option, a user with account-level permissions must [follow these steps](https://help.mozartdata.com/docs/setting-up-data-warehouse#existingsnowflakeaccount). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/nexla.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/nexla.md
index 6d4b2adf023..788a5f187c8 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/nexla.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/nexla.md
@@ -21,7 +21,7 @@ The Braze and Nexla integration allows customers that use [Currents]({{site.base
 | Nexla account | A [Nexla account][2] is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][1]. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/zapier.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/zapier.md
index e28c6b725c3..d69b9201fab 100644
--- a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/zapier.md
+++ b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/zapier.md
@@ -19,7 +19,7 @@ The Braze and Zapier partnership leverages the Braze API and Braze [webhooks][3]
 |---|---|
 | Zapier account | A Zapier account is required to take advantage of this partnership. |
 | Braze REST endpoint | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][0]. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/home.md b/_docs/_partners/home.md
index 00edad2a289..03bc80b70a9 100644
--- a/_docs/_partners/home.md
+++ b/_docs/_partners/home.md
@@ -304,4 +304,10 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/advertising/liveramp/
 - name: Inbox Monster
   url: /docs/partners/data_and_infrastructure_agility/analytics/inbox_monster/
+- name: mypostcard
+  url: /docs/partners/message_orchestration/additional_channels/direct_mail/mypostcard/
+- name: SEEN
+  url: /docs/partners/message_personalization/dynamic_content/seen
+- name: Dixa
+  url: /docs/partners/message_orchestration/additional_channels/instant_chat/dixa/
 ---
diff --git a/_docs/_partners/isv_partners/cohort_import.md b/_docs/_partners/isv_partners/cohort_import.md
index bbae720e865..92d6340d27f 100644
--- a/_docs/_partners/isv_partners/cohort_import.md
+++ b/_docs/_partners/isv_partners/cohort_import.md
@@ -24,7 +24,7 @@ Braze hosts our application on multiple clusters throughout the US and EU. The U
 | US-08 | `https://rest.iad-08.braze.com` |
 | EU-01 | `https://rest.fra-01.braze.eu`  |
 | EU-02 | `https://rest.fra-02.braze.eu`  |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Endpoint URLs
 
@@ -61,7 +61,7 @@ The Cohort name endpoint can be used to specify the name of a cohort based on it
 | `cohort_id` | String | Yes | Identifier for the cohort. This identifier should be unique for the specified client. |
 | `name` | String | Yes | Client-specified name for the cohort |
 | `created_at` | String | Yes | Timestamp in ISO-8601 format |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 #### Example request:
 
@@ -86,7 +86,7 @@ The User cohort endpoint allows for specifying which users have been added to or
 | `client_secret` | String | Yes | Data Import Key for the client whose cohort this belongs to. |
 | `cohort_id` | String | Yes | Identifier for the cohort. The identifier should be unique for the specified client. |
 | `cohort_changes` | Array of objects | Yes | Objects can have two fields. One, `user_ids`, is required and can be an array of `external_ids`, `device_ids`, and `aliases`. Each element is an ID for a user whose status in the cohort has changed. The second field, `should_remove`, is an optional boolean indicating whether the users in this object should be removed from the cohort instead of added. The default is false. The maximum combined length of the user IDs in a single request is 1,000.<br/><br/>Identified users can be matched by either their `external_id` or `alias`. Anonymous users can be matched by their `device_id`. If you pass in a device ID for an identified user, Braze will not add or remove that user. You must use external IDs or aliases for identified users. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 #### Example request:
 
@@ -126,6 +126,6 @@ Refer to the following table for errors codes specific to the Cohort Import endp
 |  | Partner not enabled for client with client secret: **&#60;client secret&#62;** |
 |  | Unauthorized access |
 | `423` | Resource locked |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For additional troubleshooting, refer to [Errors & Responses]({{site.baseurl}}/api/errors/), which covers the various errors and server responses that can come up while using the Braze API.
diff --git a/_docs/_partners/message_orchestration.md b/_docs/_partners/message_orchestration.md
index 505be88b7c7..ac9123759a1 100644
--- a/_docs/_partners/message_orchestration.md
+++ b/_docs/_partners/message_orchestration.md
@@ -107,4 +107,8 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/channel_extensions/surveys/typeform/
 - name: Friendbuy
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/friendbuy/
+- name: mypostcard
+  url: /docs/partners/message_orchestration/additional_channels/direct_mail/mypostcard/
+- name: Dixa
+  url: /docs/partners/message_orchestration/additional_channels/instant_chat/dixa/
 ---
diff --git a/_docs/_partners/message_orchestration/additional_channels.md b/_docs/_partners/message_orchestration/additional_channels.md
index b50316bd55f..7a62a4e9727 100644
--- a/_docs/_partners/message_orchestration/additional_channels.md
+++ b/_docs/_partners/message_orchestration/additional_channels.md
@@ -37,6 +37,9 @@ valid_partner_list:
 - name: Sendbird
   url: /docs/partners/message_orchestration/additional_channels/messaging/sendbird/      
 - name: Regal
-  url: /docs/partners/message_orchestration/additional_channels/messaging/regal/    
-
+  url: /docs/partners/message_orchestration/additional_channels/messaging/regal/
+- name: MyPostcard
+  url: /docs/partners/message_orchestration/additional_channels/messaging/mypostcard/      
+- name: Dixa
+  url: /docs/partners/message_orchestration/additional_channels/instant_chat/dixa/
 ---
diff --git a/_docs/_partners/message_orchestration/additional_channels/calendar/rokt_calendar.md b/_docs/_partners/message_orchestration/additional_channels/calendar/rokt_calendar.md
index 66d31944915..ebd3edcfb55 100644
--- a/_docs/_partners/message_orchestration/additional_channels/calendar/rokt_calendar.md
+++ b/_docs/_partners/message_orchestration/additional_channels/calendar/rokt_calendar.md
@@ -24,7 +24,7 @@ The Braze and Rokt Calendar integration allows your Rokt Calendar subscribers an
 | Braze REST API key | A Braze REST API key with `users.track` permissions. You will need to provide this key to your Rokt Calendar account manager.<br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | [Braze REST endpoint]({{site.baseurl}}/api/basics/#endpoints) | Your REST Endpoint URL. Your endpoint will depend on the Braze URL for your instance. |
 | External subscriber ID | This is the identifier used by the Rokt Calendar subscription process to match the calendar subscriber with the Braze user. This is something you pass to Rokt Calendar.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Audience segmentation {#audience-segmentation}
 
@@ -48,7 +48,7 @@ When Rokt Calendar creates a new user or matches an existing subscriber with a B
 | `rokt:subscription_id` | The subscription ID, serving as a unique identifier, related to the created subscription | `06423672-b6ba-4536-aa36-70788a7a0a36` |
 | `rokt:subscription_method` | Subscription method (webcal/Google) related to the created subscription. | `WebCal/f5733866ade2` |
 | `rokt:tags` | Calendar tags used  related to the created subscription. | `Test Calendar 1/All Teams/f5733866ade2 and Test Calendar 1/TeamI//f5733866ade2` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Rokt Calendar will also trigger a `subscribe` custom event as soon as the user has subscribed to your Rokt calendar that can be used either in Braze segmentation or be used as a trigger for a campaign or Canvas component.
 
@@ -182,7 +182,7 @@ The following fields include information that can be customized at the event lev
 | `eventEnd` <br>***Required**  | The start date and time of the event as it would appear in the calendar | `2019-02-21T16:00:00` |
 | `eventTz` <br>***Required**  | The time zone of the event as it would appear in the calendar, note that the list of applicable time zones can be found [here](https://roktcalendar-api.readme.io/docs/timezones). | `Eastern Standard Time` |
 | `notifyBefore` <br>***Required**  | The reminder time of the event as it would appear in the calendar, note that this is expressed in minutes | `15` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 {% endtab %}
 {% endtabs %}
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/direct_mail.md b/_docs/_partners/message_orchestration/additional_channels/direct_mail.md
index 6d63f615970..136aaff9a50 100644
--- a/_docs/_partners/message_orchestration/additional_channels/direct_mail.md
+++ b/_docs/_partners/message_orchestration/additional_channels/direct_mail.md
@@ -18,7 +18,7 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/additional_channels/direct_mail/lob/
 - name: optilyz
   url: /docs/partners/message_orchestration/additional_channels/direct_mail/optilyz/
-
-
+- name: mypostcard
+  url: /docs/partners/message_orchestration/additional_channels/direct_mail/mypostcard/
 
 ---
diff --git a/_docs/_partners/message_orchestration/additional_channels/direct_mail/inkit.md b/_docs/_partners/message_orchestration/additional_channels/direct_mail/inkit.md
index f65c880a163..82a553f2427 100644
--- a/_docs/_partners/message_orchestration/additional_channels/direct_mail/inkit.md
+++ b/_docs/_partners/message_orchestration/additional_channels/direct_mail/inkit.md
@@ -22,7 +22,7 @@ The Braze and Inkit integration allows you to generate documents and mail them d
 | Inkit API key<br><br>`<INKIT_API_TOKEN>` | This key is found on your [Inkit Dashboard](https://app.inkit.io/#/account/integrations) under the **Development** tab and will enable you to connect your Braze and Inkit accounts.|
 | Inkit template ID<br><br>`<INKIT_TEMPLATE_ID>` | After creating a template, you can copy the template ID from the **Templates** tab to use in your template in Braze.<br><br>For example, you might create a template called `invoice_template` in the Inkit environment with the Template ID: `tmpl_3bDScFl9cwr3OAVR1RSdEC`.
 | HTTP header | The HTTP header is part of the API request that you send from Braze to Inkit. In it, you will include your Inkit API key to authenticate and authorize calls to the Inkit API. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/direct_mail/lob.md b/_docs/_partners/message_orchestration/additional_channels/direct_mail/lob.md
index 31e8f44751b..70904bcf28a 100644
--- a/_docs/_partners/message_orchestration/additional_channels/direct_mail/lob.md
+++ b/_docs/_partners/message_orchestration/additional_channels/direct_mail/lob.md
@@ -20,7 +20,7 @@ The Braze and Lob integration leverages Braze webhooks and the Lob API to send m
 | ---| ---|
 |Lob account | A Lob account is required to take advantage of this partnership. |
 | Lob API key | You Lob API key can be found under the settings section under your name in the Lob dashboard. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -31,7 +31,7 @@ The HTTP URL to request in the webhook is different for each action you can make
 | API endpoint | Available endpoints |
 | ------------ | ------------------- |
 | https://api.lob.com/ | /v1/addresses<br>/v1/addresses/{id}<br>/v1/verify<br>/v1/postcards<br>/v1/postcards/{id}<br>/v1/letter<br>/v1/letter/{id}<br>/v1/checks<br>/v1/checks/{id}<br>/v1/bank_accounts<br>/v1/bank_accounts/{id}<br>/v1/bank_accounts/{id}/verify<br>/v1/areas<br>/v1/areas/{id}<br>/v1/routes/{zip_code}<br>/v1/routes<br>/v1/countries<br>/v1/states|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Step 2: Create your Braze webhook template
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/direct_mail/mypostcard.md b/_docs/_partners/message_orchestration/additional_channels/direct_mail/mypostcard.md
new file mode 100644
index 00000000000..16c77d62e4c
--- /dev/null
+++ b/_docs/_partners/message_orchestration/additional_channels/direct_mail/mypostcard.md
@@ -0,0 +1,109 @@
+---
+nav_title: MyPostcard
+article_title: MyPostcard
+page_order: 1
+description: "This reference article outlines the partnership between Braze and MyPostcard, which allows you to use direct mail as an additional channel for your CRM workflow."
+alias: /partners/mypostcard/
+page_type: partner
+search_tag: Partner
+
+---
+
+# MyPostcard
+
+> [MyPostcard][1], a leading global postcard app, empowers you to execute direct mail campaigns with ease, providing a seamless and profitable way to connect with your customers. 
+
+Use the MyPostcard and Braze integration to effortlessly send your customers print mailings.
+
+## Prerequisites
+
+| Requirement                      | Description                                                                                                             |
+|----------------------------------|-------------------------------------------------------------------------------------------------------------------------|
+| MyPostcard B2B account           | Registering with MyPostcard is required to take advantage of this integration.                                          |
+| B2B API key and credentials        | You can find your API Key and the credentials in the MyPostcard B2B Admin Tool.                                         |
+| Approved MyPostcard B2B campaign | To take advantage of this integration, you need to set up a print mailing campaign in the MyPostcard B2B tool. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
+
+## Use cases
+
+To elevate your direct mail campaigns, it’s crucial to move beyond traditional mass mailings and integrate print mailing seamlessly into your workflows. This approach allows you to reach specific customers who have opted out of your email newsletters or whose emails are marked as spam. With MyPostcard, you can effortlessly send print mailing campaigns directly through Braze.
+
+- Build intuitive workflows in Braze, incorporating print mail as a powerful new channel, without any technical expertise.
+- Unlock the potential of personalized print mailings with a few simple steps.
+- Benefit from a straightforward implementation that is backed by personalized support from a dedicated team.
+
+## Integration
+
+To integrate with MyPostcard, [log in or sign up][2] and create your first campaign to use it through [Braze webhooks][3].
+
+### Step 1: Create your Braze webhook template
+
+Create a MyPostcard webhook template to use in future campaigns or Canvases by navigating to **Templates** > **Webhook Templates** in the Braze platform.
+
+{% alert note %}
+If you are using the [older navigation]({{site.baseurl}}/navigation/), go to **Engagement** > **Templates & Media** > **Webhook Templates**.
+{% endalert %}
+
+If you would like to create a one-off MyPostcard webhook campaign or use an existing template, select **Webhook** in Braze when creating a new campaign. Fill out the following fields:
+
+| Field         | Description                                               |
+|---------------|-----------------------------------------------------------|
+| **Webhook URL** | The webhook URL as shown in the B2B Admin Tool.             |
+| **Request Body** | Raw Text (JSON format found in the B2B Admin Tool).        |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+
+#### Request method and headers
+
+MyPostcard requires an HTTP method along with the following HTTP headers to be included in the template.
+
+{% raw %}
+<table>
+  <thead>
+    <tr>
+      <th><strong>Field</strong></th>
+      <th><strong>Details</strong></th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td><strong>HTTP Method</strong></td>
+      <td><code>POST</code></td>
+    </tr>
+    <tr>
+      <td><strong>Username</strong></td>
+      <td><code>{{ '&lt;username&gt;' }}</code></td>
+    </tr>
+    <tr>
+      <td><strong>Password</strong></td>
+      <td><code>{{ '&lt;password&gt;' }}</code></td>
+    </tr>
+    <tr>
+      <td><strong>Content-Type</strong></td>
+      <td><code>application/json</code></td>
+    </tr>
+  </tbody>
+</table>
+{% endraw %}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+
+#### Request body
+
+Copy the request body displayed in the B2B Admin Tool, then fill in the placeholders with content using any Liquid personalization tags.
+
+![Compose Tab showing the JSON body and webhook information.][4]
+
+### Step 2: Preview your request
+
+Next, preview your request in the **Preview** panel or go to the **Test** tab, where you can choose a random user, an existing user, or create a custom user to test your webhook. Don’t forget to save your template before leaving the page!
+
+![Test Webhook Tab with different fields to validate the implementation.][5]
+
+{% alert important %}
+Remember to save your template before leaving the page! <br>Updated webhook templates can be found in the **Saved Webhook Templates** list when creating a new [webhook campaign]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/). 
+{% endalert %}
+
+[1]: https://www.mypostcard.com
+[2]: https://www.mypostcard.com/b2b/admin/
+[3]: https://www.braze.com/docs/user_guide/message_building_by_channel/webhooks
+[4]: {% image_buster /assets/img/mypostcard/mypostcard_compose.jpg %}
+[5]: {% image_buster /assets/img/mypostcard/mypostcard_test.jpg %}
diff --git a/_docs/_partners/message_orchestration/additional_channels/direct_mail/optilyz.md b/_docs/_partners/message_orchestration/additional_channels/direct_mail/optilyz.md
index f4e4d4e9619..5bb731878bb 100644
--- a/_docs/_partners/message_orchestration/additional_channels/direct_mail/optilyz.md
+++ b/_docs/_partners/message_orchestration/additional_channels/direct_mail/optilyz.md
@@ -21,7 +21,7 @@ Use the optilyz and Braze webhook integration to send your customers direct mail
 |optilyz account | An optilyz account is required to take advantage of this partnership. |
 | optilyz API key<br><br>`<OPTILYZ_API_KEY>`| Your optilyz customer success manager will provide you with your optilyz API key.<br><br>This API key will enable you to connect your Braze and optilyz accounts. |
 | optilyz automation ID<br><br>`<OPTILYZ_AUTOMATION_ID>` | The automation ID can be found in a box on the page header.<br><br>When logged into optilyz, you can navigate to the automation you want to send data into.<br>The automation must be activated first. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/instant_chat.md b/_docs/_partners/message_orchestration/additional_channels/instant_chat.md
index a71d7a71960..38716685799 100644
--- a/_docs/_partners/message_orchestration/additional_channels/instant_chat.md
+++ b/_docs/_partners/message_orchestration/additional_channels/instant_chat.md
@@ -2,7 +2,6 @@
 nav_title: Instant Chat
 article_title: Instant Chat Partners
 page_order: 2
-
 page_type: landing
 description: "This landing page lists Braze partners (Alloys) who allow you to coordinate your messages with instant chat services."
 
@@ -14,11 +13,14 @@ partner_top_header: "Instant Chat"
 valid_partner_list:
 - name: Messenger
   url: /docs/partners/message_orchestration/additional_channels/instant_chat/messenger/
-- name: LINE
-  url: /docs/partners/message_orchestration/additional_channels/messaging/line/  
 - name: Sendbird
   url: /docs/partners/message_orchestration/additional_channels/messaging/sendbird/  
 - name: Regal
   url: /docs/partners/message_orchestration/additional_channels/messaging/regal/  
-
+- name: Dixa
+  url: /docs/partners/message_orchestration/additional_channels/instant_chat/dixa/
+- name: Zendesk
+  url: /docs/partners/message_orchestration/additional_channels/instant_chat/zendesk_chat/
+- name: Front
+  url: /docs/partners/message_orchestration/additional_channels/instant_chat/front/
 ---
diff --git a/_docs/_partners/message_orchestration/additional_channels/instant_chat/dixa.md b/_docs/_partners/message_orchestration/additional_channels/instant_chat/dixa.md
new file mode 100644
index 00000000000..50d76278dd1
--- /dev/null
+++ b/_docs/_partners/message_orchestration/additional_channels/instant_chat/dixa.md
@@ -0,0 +1,87 @@
+---
+nav_title: Dixa
+article_title: Dixa
+description: "This article outlines the partnership between Braze and Dixa."
+alias: /partners/dixa/
+page_type: partner
+search_tag: Partner
+
+---
+
+# Dixa
+
+> [Dixa](https://www.dixa.com/) is a customer service platform designed to enhance support experiences by unifying communication channels such as chat, email, phone, and social media into a single interface. It helps businesses improve customer satisfaction and efficiency through intelligent routing, automation, and real-time performance insights.
+
+The Braze and Dixa integration offers a better view on all your users by providing customer service agents with real-time Braze data.
+
+## Prerequisites
+
+Before you start, you'll need the following:
+
+| Prerequisite          | Description                                                                                                                                                       |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| A Dixa account        | A Dixa admin account is required to take advantage of this partnership.                                                                                           |
+| A Braze REST API key  | A Braze REST API key with `users.export.ids` and `email.status` permissions.<br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
+| A Braze REST endpoint | [Your REST endpoint URL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints). Your endpoint will depend on the Braze URL for your instance.              |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+
+{% alert note %}
+If you're using the [older navigation]({{site.baseurl}}/navigation), you can create an API key at **Developer Console** > **API Settings**.
+{% endalert %}
+
+## Use cases
+
+Surface Braze data into the customer service agent view while communicating with your users on different communication channels, such as email, messenger, or chat.
+
+## Integration
+
+You must be a Dixa administrator to configure integrations within Dixa. For the Braze integration, in Dixa, go to **Settings** > **Integrations** > **Braze**.
+
+![][1]{: style="width:450px;"}
+
+### Step 1: Create the integration in Dixa
+
+On the **Create Braze widget** page, fill in the following required fields to create the integration:
+
+- **Widget name:** This is the name of the integration that will later be used in the conversation sidebar as the title.
+- **API URL:** This is the Braze REST API endpoint URL for your instance.
+- **API Key:** This is the Braze API key you created in the prerequisites.
+
+### Step 2: Configure the integration
+
+Next, configure the Braze and Dixa integration. Choose from the following options to adjust the view of the Braze widget in the conversation sidebar.
+
+#### Show the widget in the conversation sidebar
+
+This setting shows or hides the whole integration within the conversation sidebar in Dixa. 
+
+If you're actively configuring the integration, we recommend turning this off while you fill in the required fields. When you're finished configuring, you can turn it on again and Dixa agents can use the integration.
+
+#### Display customer details
+
+Choose to show or hide the user's details. The details contain data about location, email, phone number, email subscription state, push notification subscription state, and the duration of the membership in Braze. 
+
+#### Display the button to change the email subscription state
+
+The buttons are based on one of the three subscription states from Braze: `subscribed`, `opted-in`, and `unsubscribed`. If a user is `subscribed`, the agent can choose to `opt-in` or `unsubscribe`. When a user is `opted-in` or `unsubscribed`, it's only possible to switch between the two.
+
+#### Display a list of custom attributes
+
+Choose to show or hide the user's custom Braze attributes.
+
+#### Display a list of custom events
+
+Choose to show or hide the user's custom Braze events.
+
+#### Display a list of purchases
+
+Choose to show or hide a list products purchased by the user. Here, you can see how many times it was purchased. To view the first and last purchase date, hover above the item. 
+
+### Example integration
+
+The following shows an example of the integration:
+
+![The Braze and Dixa integration in Dixa that displays a user's email subscription state, custom attributes, custom events, and purchases.][2]{: style="width:350px;"}
+
+[1]: {% image_buster /assets/img/dixa/dixa-create-integration.png %}
+[2]: {% image_buster /assets/img/dixa/dixa-braze-integration.png %}
\ No newline at end of file
diff --git a/_docs/_partners/message_orchestration/additional_channels/instant_chat/line.md b/_docs/_partners/message_orchestration/additional_channels/instant_chat/line.md
deleted file mode 100644
index 112ecc9dde0..00000000000
--- a/_docs/_partners/message_orchestration/additional_channels/instant_chat/line.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-nav_title: LINE
-article_title: LINE
-alias: /partners/line/
-description: "This reference article outlines the partnership between Braze and LINE, one of the world's most popular instant messaging platforms."
-page_type: partner
-search_tag: Partner
-
----
-
-# LINE
-
-> [LINE](https://line.me/en/) is one of the world's most popular instant messaging platforms, used by hundreds of millions of monthly active users. Through this platform, brands can engage with their customers with rich and two-way messaging.
-
-The Braze and LINE integration allows you to leverage Braze webhooks, advanced segmentation, personalization, and triggering features to message your users in LINE through the [LINE messaging API](https://developers.line.biz/en/docs/messaging-api/overview/).
-
-## Prerequisites
-
-LINE allows both promotional and non-promotional messaging to users as long your brand has secured users' consent. To send messages to users, you must meet one of two conditions:
-- Users who have added your LINE official account as a friend
-- Users who haven't added your LINE official account as a friend but have sent a message to your LINE official account (excluding users who have blocked your LINE official account).
-<br><br>
-
-| Requirement | Description |
-| ----------- | ----------- | 
-| LINE business account | A LINE [official business account](https://www.linebiz.com/jp-en/) is required to take advantage of this partnership.<br><br>When sending LINE messages, your messages will all be associated with your LINE official account, resulting in users seeing your account name and page.|
-| Messaging API channel | When enabling the use of the messaging API in the LINE [official account manager](https://developers.line.biz/en/docs/messaging-api/getting-started/#using-oa-manager), a messaging API channel is created. This will be the channel you use to communicate with your customers. |
-| Channel access tokens |The [channel access token](https://developers.line.biz/en/docs/messaging-api/channel-access-tokens/) will allow you to send messages to users that have added your LINE official account as a friend. This token can be found in the **LINE Developer Console** under the **Messaging API** tab.
-| LINE user IDs | You will need to have users' LINE IDs (this ID is different from users' usernames) to send messages on LINE.<br><br>Once a user adds your LINE official account as a friend, you can access the user's LINE ID through LINE's Users API. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
-
-## Integration
-
-### Step 1: Collect customer LINE IDs
-
-To send messages in LINE, you need to collect your users' LINE IDs to identify your user and interact with them consistently. LINE IDs are not the same as the user's LINE usernames. LINE IDs are generated by LINE and can be used when interacting with LINE's APIs.
-
-LINE IDs can be obtained using the LINE [User ID API](https://developers.line.biz/en/reference/messaging-api/#get-follower-ids). This endpoint will return a list of LINE IDs for all users who have friended your LINE official account or sent your account a message and have not blocked you. 
-
-When making a GET request to the endpoint `https://api.line.me/v2/bot/followers/ids`, you will get the following:
-```json
-{
-   "userIds":[
-      "U4af4980629...",
-      "U0c229f96c4...",
-      "U95afb1d4df..."
-   ],
-   "next":"yANU9IA..."
-}
-```
-Once you obtain a list of LINE IDs, you will send them to Braze as a `line_id` custom attribute.
-
-### Step 2: Send IDs to Braze as custom attributes
-
-Coordinate and share this with your developers to send the `line_id` to Braze as [custom attributes]({{site.baseurl}}/user_guide/Data_and_Analytics/Custom_Data/Custom_Attributes/#custom-attributes).
-
-### Step 3: Set your channel access token as a Content Block.
-
-In Braze, navigate to **Templates & Media > Content Blocks Library > + Create Content Block** and create a Braze [Content Block]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/#content-blocks). Name this Content Block `LINE_Channel_AccessToken`. 
-
-Next, paste your channel access token in the Content Block body, and save it.
-
-![An image the Content Block showing the Content Block name, Liquid tag, and censored channel access token.][2]
-
-Once you've set the channel access token inside a Content Block, you will be able to use the LINE webhook template to send messages to users.
-
-### Step 4: Select a webhook template
-
-Go to **Templates** > **Webhook Templates** and choose one of the following LINE Messenger webhook templates:
-
-![A selection of available predesigned webhook templates.]({% image_buster /assets/img_archive/line_templates.png %}){: style="border:0px;"}
-
-{% alert note %}
-If you are using the [older navigation]({{site.baseurl}}/navigation), go to **Engagement** > **Templates & Media** > **Webhook Templates**.
-{% endalert %}
-
-{% tabs %}
-{% tab LINE Text %}
-The LINE [text](https://developers.line.biz/en/docs/messaging-api/message-types/#text-messages) webhook template will allow you to send text-based messages that support emojis.
-
-![The line messaging UI with two examples of what a text message will look like on their platform.]({% image_buster /assets/img_archive/line_text_type.png %}){: style="max-width:70%;border:0px;"}
-{% endtab %}
-{% tab LINE Sticker %}
-The LINE [sticker](https://developers.line.biz/en/docs/messaging-api/message-types/#sticker-messages) template will allow you to send sticker messages. Stickers can be used to make your bot app more expressive and engaging for your users. 
-
-To send a sticker, include the sticker's package ID and sticker ID in the message object. See the [list of available stickers](https://developers.line.biz/en/docs/messaging-api/sticker-list/) that can be sent with the Messaging API.
-
-![The line messaging UI with several examples of what sticker messages look like. These examples include a bear celebrating, a rabbit giving a thumbs up, and a yellow duck.]({% image_buster /assets/img_archive/line_sticker_type.png %}){: style="max-width:70%;border:0px;"}
-{% endtab %}
-{% tab LINE Image %}
-The LINE [image](https://developers.line.biz/en/docs/messaging-api/message-types/#image-messages) template allows you to send images to your LINE users.
-
-To send images, include URLs of the original image and a smaller preview image in the message object. The preview image is displayed in the chat, and the full image is opened when the image is tapped. Note that the URLs must use HTTPS over TLS 1.2 or later.
-
-![The line messaging UI showing what an image message will look like on their platform.]({% image_buster /assets/img_archive/line_image_type.png %})
-{% endtab %}
-{% tab LINE Carousel %}
-The LINE [carousel](https://developers.line.biz/en/docs/messaging-api/message-types/#carousel-template) template allows you to send messages with multiple column objects that users can cycle through. In addition to having buttons, you can also indicate in each column object a single action to be executed when a user taps anywhere in the image, title, or text area.
-
-![The line messaging UI showing a carousel message. This message includes a swipable content box that includes an image, description, a reserve button, and a call button. ]({% image_buster /assets/img_archive/line_carousel_type.png %}){: style="max-width:70%;border:0px;"}
-{% endtab %}
-{% endtabs %}
-
-### Step 5: Set up your webhook template
-
-In your webhook template, provide a template name and add teams and tags, as necessary. Next, enter your message, sticker ID, or image depending on the LINE template type you selected.
-
-The custom attribute `LINE ID` should be templated in the message body's `To:` field. If not, include the LINE ID as a custom attribute. This can be done by using the blue and white + button in the corner of the **Request Body** box.
-
-#### Previewing and Testing Your Webhook
-
-Before you send your message, test your webhook. Make sure your LINE ID is saved in Braze (or find it and test as a customized user), and use the preview to send the test message:
-
-![Test tab in the Braze webhook builder that shows you can preview the message by sending it to an existing user.][3]
-
-If you receive the message successfully, you can start to configure its delivery settings.
-
-## Using this integration
-
-Once set up, use this integration to target LINE users. First, [create a segment][62] for all users for whom the `LINE ID` exists as a custom attribute and turn on [analytics tracking][61] to track your Messenger subscription rates over time. 
-
-![Segment filter "line_id" set to "is not blank".][63]
-
-If you choose not to create a specific segment for Messenger subscribers, make sure to include a filter for `LINE ID` existing to avoid errors.
-
-You may also use other segmentation to target your LINE campaigns and the rest of the campaign creation process, as is with any other campaign.
-
-[1]: {% image_buster /assets/img_archive/line_channel_access_token.png %}
-[2]: {% image_buster /assets/img_archive/line_content_block_token.png %}
-[3]: {% image_buster /assets/img_archive/line_preview.png %}
-[61]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/
-[62]: {{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/#creating-a-segment
-[63]: {% image_buster /assets/img_archive/line_segment.png %}
diff --git a/_docs/_partners/message_orchestration/additional_channels/instant_chat/messenger.md b/_docs/_partners/message_orchestration/additional_channels/instant_chat/messenger.md
index 479189fbff3..817376e6e0b 100644
--- a/_docs/_partners/message_orchestration/additional_channels/instant_chat/messenger.md
+++ b/_docs/_partners/message_orchestration/additional_channels/instant_chat/messenger.md
@@ -34,7 +34,7 @@ Acknowledge the following before proceeding with integration:
 | App bot review and approval | Facebook | [https://developers.facebook.com/docs/messenger-platform/app-review](https://developers.facebook.com/docs/messenger-platform/app-review) | When you are ready to release your bot to the public, you must submit it to Facebook for review and approval. This review process allows us to ensure your Messenger bot abides by our policies and functions as expected before making it available to everyone on Messenger. |
 | Page-scope IDs (PSIDs) | Facebook | [https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messages](https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messages) | You need to have users PSIDs to send messages on Facebook Messenger. When a user interacts with your app via Messenger, Facebook will create a PSID. This PSID can be sent to Braze as a string custom attribute.
 | Page access token | Facebook | [https://developers.facebook.com/docs/messenger-platform/getting-started/app-setup#page_access_token](https://developers.facebook.com/docs/messenger-platform/getting-started/app-setup#page_access_token) | These access tokens are similar to user access tokens, except that they provide permission to APIs that read, write or modify the data belonging to a Facebook Page. To obtain a page access token, you need to obtain a user access token and ask for the `manage_pagespermission`. After you have the user access token, you then get the page access token via the Graph API.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/instant_chat/regal.md b/_docs/_partners/message_orchestration/additional_channels/instant_chat/regal.md
index 8b9758dac49..f03b07c2a4d 100644
--- a/_docs/_partners/message_orchestration/additional_channels/instant_chat/regal.md
+++ b/_docs/_partners/message_orchestration/additional_channels/instant_chat/regal.md
@@ -23,7 +23,7 @@ By integrating Regal and Braze, you can create a more consistent and personalize
 | Regal account | A Regal account is required to take advantage of this partnership. |
 | Regal API key | A Regal API key will allow sending events from Braze to Regal.<br><br>Email [support@regal.io](mailto:support@regal.io) to get this key. |
 | Braze Data Transformation | Data transformation is currently in early access. Contact your Braze customer success manager if you are interested in participating in the early access. This is necessary to receive data from Regal. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration: Sending data from Braze to Regal
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md b/_docs/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md
index c120b982340..ed09d3e11c3 100644
--- a/_docs/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md
+++ b/_docs/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md
@@ -26,7 +26,7 @@ By harnessing the joint capabilities of Braze and Sendbird Notifications, busine
 | Sendbird UIKit | You must have the Sendbird UIKit installed in your [iOS][2] or [Android][3] app. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/mobile_wallet/passkit.md b/_docs/_partners/message_orchestration/additional_channels/mobile_wallet/passkit.md
index 0eac8586b14..0fa11c5e6a7 100644
--- a/_docs/_partners/message_orchestration/additional_channels/mobile_wallet/passkit.md
+++ b/_docs/_partners/message_orchestration/additional_channels/mobile_wallet/passkit.md
@@ -22,7 +22,7 @@ The Braze and PassKit integration allows you to increase and measure the engagem
 | `userDefinedID` | To appropriately update custom events and custom attributes to your users between PassKit and Braze, you will need to set the Braze external ID as the `userDefinedID`. This `userDefinedID` will be used when making API calls to the PassKit endpoints. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][6]. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 
@@ -64,7 +64,7 @@ There are many different components you can include in your payload, but here as
 | --------- | -------- | ---- | ----------- |
 |`person.externalId` | Required | String | Set as the Braze external ID, this is crucial for the callbacks from PassKit back to Braze to work, allowing Braze users to have coupons for multiple offers in one campaign. Not enforced as unique. |
 | `members.member.externalId` | Optional | String | Set as the Braze external ID, you may use your external ID to update the membership pass. Setting this field enforces the user as unique within the membership program.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 For a full list of available fields, their types, and helpful descriptions, have a look at the [PassKit GitHub documentation][10].
 
@@ -220,7 +220,7 @@ Before you get started, here are the common JSON payload parameters that you can
 | `campaignId` (coupon) <br><br> `programId` (membership) | String | The ID for the campaign or program template you created in PassKit. To find this, head to the **Settings** tab in your PassKit pass project. |
 | `expiryDate` | IO8601 datetime | The pass expiry date. After the expiry date, the pass is automatically voided (see `isVoided`). This value will override the template and campaign end date value. |
 | `status` | String | The current status of a coupon, such as `REDEEMED` or `UNREDEEMED`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Step 1: Create your Braze webhook template
 
@@ -280,7 +280,7 @@ In addition to creating and updating passes, you can also retrieve your users' p
 **Liquid example responses**
 
 {% tabs local %}
-{% tab passes.redemptionDetails %}
+{% tab passes redemptionDetails %}
 
 ```json
 {
@@ -297,7 +297,7 @@ In addition to creating and updating passes, you can also retrieve your users' p
 ```
 
 {% endtab %}
-{% tab passes.status %}
+{% tab passes status %}
 ```
 UNREDEEMED 
 ```
diff --git a/_docs/_partners/message_orchestration/additional_channels/retargeting/facebook.md b/_docs/_partners/message_orchestration/additional_channels/retargeting/facebook.md
index 61d7fc911e6..12d66a8c82c 100644
--- a/_docs/_partners/message_orchestration/additional_channels/retargeting/facebook.md
+++ b/_docs/_partners/message_orchestration/additional_channels/retargeting/facebook.md
@@ -34,7 +34,7 @@ If you are participating in testing Meta Work Accounts in beta, ensure you disco
 | [Facebook Business Manager][1] | A centralized tool to manage your brand's Facebook assets (for example, ad accounts, pages, apps). |
 | [Facebook ad account][2] | An active Facebook ad account tied to your brand's business manager that you want to use with Braze custom audiences.<br><br>Ensure that your Facebook business manager administrator has granted you administrator permissions to the Facebook ad accounts you plan to use with Braze, and that you have accepted your ad account terms and conditions. Otherwise, you will not be able to access any Facebook ad accounts within Braze. |
 | [Facebook Custom Audiences Terms][3]| You must accept Facebook's Custom Audiences Terms for your Facebook ad accounts you plan to use with Braze.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/retargeting/jampp.md b/_docs/_partners/message_orchestration/additional_channels/retargeting/jampp.md
index 8d63ac22a7f..8dfd00fa8f4 100644
--- a/_docs/_partners/message_orchestration/additional_channels/retargeting/jampp.md
+++ b/_docs/_partners/message_orchestration/additional_channels/retargeting/jampp.md
@@ -30,7 +30,7 @@ This integration supports iOS and Android apps.
 | iOS app ID | Your unique Braze application identifier for iOS (such as "012345678"). |
 | Enable IDFA collection in Braze SDK | IDFA collection is optional within the Braze SDK and disabled by default. | 
 | Collection of Google advertising ID via custom attribute | Google advertising ID collection is optional for customers and can be collected as a [custom attribute][5].
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/retargeting/quikly.md b/_docs/_partners/message_orchestration/additional_channels/retargeting/quikly.md
index f6dd23e6c15..4b0a710bba5 100644
--- a/_docs/_partners/message_orchestration/additional_channels/retargeting/quikly.md
+++ b/_docs/_partners/message_orchestration/additional_channels/retargeting/quikly.md
@@ -22,7 +22,7 @@ The Braze and Quikly partnership allows you to accelerate conversions on events
 | Braze REST API key | A Braze REST API key with `users.track`, `subscription.status.set`, `users.export.ids`, and `subscription.status.get` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][2]. Your endpoint will depend on the Braze URL for your instance. |
 | Quikly API key (optional) | A Quikly API key provided by your client success manager (webhook only). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/additional_channels/retargeting/remerge.md b/_docs/_partners/message_orchestration/additional_channels/retargeting/remerge.md
index 22cb53eb374..ca236e9b839 100644
--- a/_docs/_partners/message_orchestration/additional_channels/retargeting/remerge.md
+++ b/_docs/_partners/message_orchestration/additional_channels/retargeting/remerge.md
@@ -23,7 +23,7 @@ The Braze and Remerge integration helps you develop robust, cross-channel lifecy
 | Android app ID | Your unique Braze application identifier for Android (such as "com.example"). |
 | iOS app ID | Your unique Braze application identifier for iOS (such as "012345678"). |
 | Enable IDFA collection in Braze SDK | IDFA collection is optional within the Braze SDK and disabled by default. | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/attribution/adjust.md b/_docs/_partners/message_orchestration/attribution/adjust.md
index e9b5d410e4e..5e0138b88c7 100644
--- a/_docs/_partners/message_orchestration/attribution/adjust.md
+++ b/_docs/_partners/message_orchestration/attribution/adjust.md
@@ -21,7 +21,7 @@ The Braze and Adjust integration lets you import non-organic install attribution
 | Adjust account | An Adjust account is required to take advantage of this partnership. |
 | iOS or Android app | This integration supports iOS and Android apps. Depending on your platform, code snippets may be required in your application. Details on these requirements can be found in step 1 of the integration process. |
 | Adjust SDK | In addition to the required Braze SDK, you must install the [Adjust SDK](https://dev.adjust.com/en/sdk). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -98,7 +98,7 @@ Assuming you configure your integration as suggested, Braze will map Adjust's da
 | `{campaign_name}` | Attributed Campaign |
 | `{adgroup_name}` | Attributed Adgroup |
 | `{creative_name}` | Attributed Ad |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Facebook and X (formerly Twitter) attribution data
 
diff --git a/_docs/_partners/message_orchestration/attribution/airbridge.md b/_docs/_partners/message_orchestration/attribution/airbridge.md
index eea4fdd032b..95a8edee576 100644
--- a/_docs/_partners/message_orchestration/attribution/airbridge.md
+++ b/_docs/_partners/message_orchestration/attribution/airbridge.md
@@ -21,7 +21,7 @@ The Braze and Airbridge integration lets you pass all non-organic install attrib
 | Airbridge account | An Airbridge account is required to take advantage of this partnership. |
 | iOS or Android app | This integration supports iOS and Android apps. Depending on your platform, code snippets may be required in your application. |
 | Airbridge SDK | In addition to the required Braze SDK, you must install the Airbridge [Android](https://help.airbridge.io/en/developers/android-sdk) or [iOS](https://help.airbridge.io/en/developers/ios-sdk) SDK. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/attribution/appsflyer/appsflyer.md b/_docs/_partners/message_orchestration/attribution/appsflyer/appsflyer.md
index b3558ae696d..c0896a2367c 100644
--- a/_docs/_partners/message_orchestration/attribution/appsflyer/appsflyer.md
+++ b/_docs/_partners/message_orchestration/attribution/appsflyer/appsflyer.md
@@ -27,7 +27,7 @@ You can also pass your AppsFlyer audiences (cohorts) directly to Braze with the
 | AppsFlyer SDK | In addition to the required Braze SDK, you must install the [AppsFlyer SDK](https://dev.appsflyer.com/hc/docs/getting-started).
 | Email domain setup complete | You must have completed the [IP and domain setup step]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/setting_up_ips_and_domains/) of setting up your email during Braze onboarding. |
 | SSL certificate | Your [SSL certificate]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/ssl#acquiring-an-ssl-certificate) must be configured. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -132,7 +132,7 @@ Assuming you configure your integration as suggested, Braze will map all non-org
 | `campaign` | Attributed Campaign |
 | `af_adset` | Attributed Adgroup |
 | `af_ad` | Attributed Ad |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Your user base can be segmented by attribution data in the Braze dashboard using the Install Attribution filters.
 
diff --git a/_docs/_partners/message_orchestration/attribution/branch/branch_for_attribution.md b/_docs/_partners/message_orchestration/attribution/branch/branch_for_attribution.md
index 02d4203867f..2275fc85e6e 100644
--- a/_docs/_partners/message_orchestration/attribution/branch/branch_for_attribution.md
+++ b/_docs/_partners/message_orchestration/attribution/branch/branch_for_attribution.md
@@ -23,7 +23,7 @@ The Braze and Branch integration will help you understand exactly when and where
 | Branch account | A Branch account is required to take advantage of this partnership. |
 | iOS or Android app | This integration supports iOS and Android apps. Depending on your platform, code snippets may be required in your application. Details on these requirements can be found in step 1 of the integration process. |
 | Branch SDK | In addition to the required Braze SDK, you must install the [Branch SDK](https://help.branch.io/developers-hub/docs/native-sdks-overview). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/attribution/kochava.md b/_docs/_partners/message_orchestration/attribution/kochava.md
index 14a01bfec0e..0b883317418 100644
--- a/_docs/_partners/message_orchestration/attribution/kochava.md
+++ b/_docs/_partners/message_orchestration/attribution/kochava.md
@@ -21,7 +21,7 @@ The Braze and Kochava integration helps power a more holistic understanding of y
 | Kochava account | A Kochava account is required to take advantage of this partnership. |
 | iOS or Android app | This integration supports iOS and Android apps. Depending on your platform, code snippets may be required in your application. Details on these requirements can be found in step 1 of the integration process. |
 | Kochava SDK | In addition to the required Braze SDK, you must install the [Kochava SDK](https://support.kochava.com/sdk-integration/). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/attribution/singular.md b/_docs/_partners/message_orchestration/attribution/singular.md
index 19246a685c6..aa1969ab898 100644
--- a/_docs/_partners/message_orchestration/attribution/singular.md
+++ b/_docs/_partners/message_orchestration/attribution/singular.md
@@ -21,7 +21,7 @@ The Braze and Singular integration allows you to import paid install attribution
 | Singular account | A Singular account is required to take advantage of this partnership. |
 | iOS or Android app | This integration supports iOS and Android apps. Depending on your platform, code snippets may be required in your application. Details on these requirements can be found in step 1 of the integration process. |
 | Singular SDK | In addition to the required Braze SDK, you must install the [Singular SDK](https://support.singular.net/hc/en-us/articles/360037640172-Getting-Started-with-the-Singular-SDK-S2S). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/attribution/vizbee_for_tv_deeplinking.md b/_docs/_partners/message_orchestration/attribution/vizbee_for_tv_deeplinking.md
index 5bc4511c742..e9e9c84e70c 100644
--- a/_docs/_partners/message_orchestration/attribution/vizbee_for_tv_deeplinking.md
+++ b/_docs/_partners/message_orchestration/attribution/vizbee_for_tv_deeplinking.md
@@ -22,7 +22,7 @@ The Braze and Vizbee integration allows you to use a single console to schedule
 | Vizbee account | A [Vizbee][1] account is required to take advantage of this partnership. You must register your app in Vizbee and have an assigned Vizbee ID. |
 | iOS or Android app | This integration supports iOS and Android apps. Depending on your platform, code snippets may be required in your application. |
 | Vizbee SDK | In addition to the required Braze SDK, you must install the Vizbee SDK. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/olo.md b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/olo.md
index 3d150cb1f9f..724c737b0cb 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/olo.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/olo.md
@@ -22,7 +22,7 @@ By integrating Olo and Braze, you can:
 | ----------- | ----------- |
 | Olo account | An Olo account with access to webhooks is required to take advantage of this partnership. Set up webhook subscriptions via the [self-service webhooks tool](https://olosupport.zendesk.com/hc/en-us/articles/360061153692-Self-Service-Webhooks) within the Olo Dashboard. |
 | Braze Data Transformation | A [Data Transformation URL]({{site.baseurl}}/data_transformation/) is necessary to receive data from Olo. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 A webhook is a way for Olo to send event-driven information to Braze about users and their actions, including events like Order Placed, Guest Opt In, Order Picked Up and more. The Olo Webhook delivers the event to Braze generally within seconds of the action being performed.
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify.md b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify.md
index 35aa6ab0229..06c3a1c3e1a 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify.md
@@ -32,7 +32,7 @@ Before you begin onboarding the integration, please review the following with yo
 |-------------|-------------
 |<i aria-hidden="true" class="fas fa-check" title="Supported"></i><span class="sr-only">Supported</span> | Supported
 |<i aria-hidden="true" class="fas fa-times" title="Not supported"></i><span class="sr-only">Supported</span> | Not supported
-{: .reset-td-br-1 .reset-td-br-2} 
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" } 
 
 | Features | Web SDK via Shopify ScriptTag | Direct web SDK integration via theme.liquid | Direct web SDK integration via Shopify Hydrogen
 |-------------|-------------|-------------|------------
@@ -47,7 +47,7 @@ Before you begin onboarding the integration, please review the following with yo
 | Default in-app message support   | <i class="fas fa-check" title="Supported"></i>  | <i class="fas fa-check" title="Supported"></i>  | <i class="fas fa-times" title="Not supported"></i>     
 | Default content cards support   | <i class="fas fa-times" title="Not supported"></i> | <i class="fas fa-times" title="Not supported"></i> | <i class="fas fa-times" title="Not supported"></i>   
 | Default web push support     | <i class="fas fa-times" title="Not supported"></i> | <i class="fas fa-times" title="Not supported"></i> | <i class="fas fa-times" title="Not supported"></i>
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}    
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }    
 
 {% tabs %}
 {% tab Shopify ScriptTag %}
diff --git a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs.md b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs.md
index 06b350bfe03..274a0ee02a5 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs.md
@@ -54,10 +54,6 @@ Refer to [Catalogs additional use cases]({{site.baseurl}}/user_guide/personaliza
 
 #### Supported Shopify catalog data
 
-{% alert note %}
-To access and use `product_handle` and `product_url`, disconnect and reconnect your Shopify catalog.
-{% endalert %}
-
 - `id`
 - `store_name`
 - `shopify_product_id`
@@ -84,6 +80,16 @@ To access and use `product_handle` and `product_url`, disconnect and reconnect y
 Modifying the Shopify catalog in any way may unintentionally interfere with real-time product syncs. Do not make any edits to the Shopify catalog, as these have the potential to be overridden by Shopify. Instead, make the necessary product updates in your Shopify instance.<br><br>To delete your Shopify catalog, go to the Shopify page and deactivate sync. Do not delete the Shopify catalog directly on the catalogs page. 
 {% endalert %}
 
+##### Using `product_handle` or `product_url`
+
+To access and use `product_handle` and `product_url`, disconnect and reconnect your Shopify catalog by doing the following.
+
+1. Go to the Shopify integration page > **Edit configuration**.<br><br>![Shopify integration page.]({% image_buster /assets/img/Shopify/edit_config.png %})
+
+{: start="2"}
+2. In the **Sync catalog** step, toggle off the catalog and then update the settings.
+3. Toggle on the catalog and update the settings.<br><br>![Shopify "Sync catalog" step with catalog toggle.]({% image_buster /assets/img/Shopify/catalog_toggle.png %})
+
 ## Back-in-stock and price-drop use cases 
 
 To set up back-in-stock notifications, follow the steps [here]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications#back-in-stock-notifications).
@@ -109,6 +115,6 @@ If your Shopify product sync runs into an error, it could be a result of the fol
 | Server Error | This occurs if there is a server error on Shopify’s side when we attempt to sync your products. | [Deactivate sync](#deactivate) and re-sync your entire inventory of products again. |
 | Duplicate SKU | This occurs if you use a SKU as your catalog item ID and have products with the same SKU. Since catalog item ID has to be unique, all your products must have unique SKUs. | Audit your full list of products and variants in Shopify to make sure that there are no duplicate SKUs. If there are duplicate SKUs, update these to be unique SKUs only in your Shopify store account. After this is corrected, [deactivate sync](#deactivate) and re-sync your entire inventory of products again. |
 | Catalog Limit Exceeded | This occurs if you exceed your catalog limit. Braze will be unable to finish the sync or keep the syncing active due to no more storage availability. | There are two solutions to this issue:<br><br>1. Reach out to your account manager to upgrade your tier to increase your catalog limit. <br><br>2. Free up storage space by deleting any of the following:<br>- Catalog items from other catalogs<br>- Other catalogs<br>- Selections created<br><br> After using either of the solutions, the sync must be deactivated and then re-synced. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 [1]: {% image_buster /assets/img/Shopify/sync_products_step1.png %}
\ No newline at end of file
diff --git a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/shopify_data_in_braze.md b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/shopify_data_in_braze.md
index 5fe18681009..026c3372281 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/shopify_data_in_braze.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/shopify_data_in_braze.md
@@ -803,7 +803,7 @@ After the app installation is complete, Braze automatically creates your webhook
 | `shopify_last_order_name` | The name of the customer's last order. This is directly related to the `name` field on the order resource. |
 | `shopify_zipcode` | The customer's zipcode from their default address. |
 | `shopify_province` | The customer's province from their default address. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Liquid personalization
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/yotpo.md b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/yotpo.md
index ac20de15827..fbf8539e149 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/ecommerce/yotpo.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/ecommerce/yotpo.md
@@ -20,7 +20,7 @@ With the Braze and Yotpo integration, you can dynamically pull and display star
 | Yotpo account | A Yotpo account is required to take advantage of this partnership. |
 | Yotpo reviews API key | This API will be implemented within the Connected Content code snippet.<br><br>For more information, refer to [finding your Yotpo app key and secret key](https://support.yotpo.com/en/article/finding-your-yotpo-app-key-and-secret-key). |
 | Yotpo loyalty API key | This API key and GUID will be implemented within the Connected Content code snippet.<br><br>For more information, refer to [finding your loyalty & referrals API key and GUID](https://support.yotpo.com/en/article/finding-your-loyalty-referrals-api-key-and-guid)|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Before continuing, confirm that the Yotpo product ID is the same as the `product_id` that will be pulled dynamically from Braze. This is mandatory for the integration to work. 
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/alpaco.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/alpaco.md
index 2a2b5e45487..1c2f49d8ce2 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/alpaco.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/alpaco.md
@@ -23,7 +23,7 @@ Alpaco supports [full Liquid](https://shopify.github.io/liquid/) variables, and
 | Alpaco account | An Alpaco account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with full **Templates** permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Cluster instance | Your Braze [cluster instance]({{site.baseurl}}/api/basics/#endpoints) aligns with your Braze dashboard and REST endpoint. <br><br> For example, if your dashboard URL is `https://dashboard-03.braze.com`, your endpoint will be `dashboard-03`.  |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/blayer.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/blayer.md
index 663a3c7d992..8d86a3a2fde 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/blayer.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/blayer.md
@@ -21,7 +21,7 @@ The Braze and B.Layer integration allows you to leverage the B.Layer in-app mess
 | Requirement | Description |
 | ----------- | ----------- |
 | B.Layer account | A [B.Layer](https://blayer.phiture.com) account is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/dyspatch.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/dyspatch.md
index 511877890ff..b9f52098d78 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/dyspatch.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/dyspatch.md
@@ -20,7 +20,7 @@ The Dyspatch and Braze integration allow you to simplify your email creation lif
 | ----------- | ----------- |
 | Dyspatch account | A [Dyspatch account][3] with an [owner or admin role][4] is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with full **Templates** permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/iam_studio.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/iam_studio.md
index d8362b5771b..99701391ac1 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/iam_studio.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/iam_studio.md
@@ -19,7 +19,7 @@ With the Braze and IAM Studio integration, you can easily insert customizable in
 | Requirement | Description |
 | ----------- | ----------- |
 | IAM Studio account | A [IAM Studio account](https://www.inappmessage.com/register) is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/knak.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/knak.md
index 5ec1f31d54d..b4d0afc648c 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/knak.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/knak.md
@@ -21,7 +21,7 @@ The Braze and Knak integration allows you to create fully responsive emails in m
 | Knak account | A Knak account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with full **Templates** permissions. <br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][2]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/sageflo.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/sageflo.md
index c4e2f55357f..165d4b6fea2 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/sageflo.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/sageflo.md
@@ -21,7 +21,7 @@ Give local teams the tools they need to market smarter, leveraging Braze's sophi
 | Sageflo Radiate account | A Sageflo Radiate account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with full `templates` and `campaigns` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your API endpoint matches the dashboard URL for your Braze instance. <br><br> For example, if your dashboard URL is `https://dashboard-03.braze.com`, your endpoint will be `dashboard-03`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/smartersends.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/smartersends.md
index a1161d83e1b..a56975bdb43 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/smartersends.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/smartersends.md
@@ -21,7 +21,7 @@ The Braze and SmarterSends partnership allows you to combine the power of Braze
 | Braze REST API key | A Braze REST API key with these permissions: {::nomarkdown}<ul><li><code>users.track</code></li><li><code>users.export.ids</code></li><li><code>messages.schedule.create</code></li><li><code>messages.schedule.update</code></li> <li><code>messages.schedule.delete</code></li><li><code>sends.id.create</code></li><li><code>segments.list</code></li><li><code>segments.data_series</code></li><li><code>segments.details</code></li><li><code>sends.data_series</code></li></ul>{:/} This can be created in the Braze dashboard from **Settings** > **API Keys**. For additional security, allowlist the SmarterSends IP address (available in your instance). |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
 | Braze API campaign ID | The [Braze API campaign ID]({{site.baseurl}}/api/api_campaigns/) is the unique identifier for all campaigns sent through SmarterSends. This can be created in the Braze dashboard at **Messaging** > **Campaigns**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can create an API key at **Developer Console** > **API Settings**.
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/stensul.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/stensul.md
index fd83b163f59..33325c7bb79 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/stensul.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/stensul.md
@@ -21,7 +21,7 @@ The Braze and Stensul integration allows you to export your HTML-formatted Stens
 | Stensul account | A Stensul account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with full **Templates** permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Cluster instance | Your Braze [cluster instance]({{site.baseurl}}/api/basics/#endpoints) aligns with your Braze dashboard and REST endpoint.  |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/stripo.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/stripo.md
index f1d19957d5f..e6f1d2764c0 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/stripo.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/stripo.md
@@ -21,7 +21,7 @@ The Braze and Stripo integration allows you to export your customized Stripo ema
 | Stripo account | A Stripo account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with full **Templates** permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Cluster instance | Your Braze [cluster instance]({{site.baseurl}}/api/basics/#endpoints) aligns with your Braze dashboard and REST endpoint.  |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/email_templates/taxi_for_email.md b/_docs/_partners/message_orchestration/channel_extensions/email_templates/taxi_for_email.md
index d4c499a0b83..131a36bb731 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/email_templates/taxi_for_email.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/email_templates/taxi_for_email.md
@@ -21,7 +21,7 @@ The Braze and Taxi integration leverages Taxi's simple yet powerful syntax to cr
 | Taxi for Email account | A Taxi for Email account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with full **Templates** permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze endpoint | [Your Braze endpoint]({{site.baseurl}}/api/basics/#endpoints) aligns with your Braze dashboard URL.<br><br> For example, if your dashboard URL is `https://dashboard-03.braze.com`, your endpoint will be `dashboard-03`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/antavo.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/antavo.md
index 5489d7a9b7b..ce4d2fcfab1 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/antavo.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/antavo.md
@@ -21,7 +21,7 @@ The Antavo and Braze integration allows you to use loyalty program-related data
 | Braze REST API key   | A Braze REST API key with `users.track` permissions.<br><br>To create a new API key in the Braze dashboard, go to **Settings** > **API Keys** and click **Create New API Key**.  |
 | Braze REST endpoint  | [Your REST endpoint URL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints). Your endpoint will depend on the Braze URL for your instance.                |
 | Braze app identifier | Your app identifier key. <br><br>To locate this key in the Braze dashboard, go to **Settings** > **API Keys** and find the **Identification** section. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/extole.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/extole.md
index 4812e805a56..0b8bf1251f2 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/extole.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/extole.md
@@ -21,7 +21,7 @@ With the Braze and Extole integration, you can pull customer events and attribut
 | Extole account | An Extole account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with the `users.track` permission. This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze API URL | Your Braze API URL is specific to your [Braze instance]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
@@ -55,7 +55,7 @@ Below are the default events, event properties, and user attributes Extole will
 | `extole_created_share_link` | A participant creates their share link by entering their email in the Extole Share Experience. | Event name  <br>Event time  <br>Partner (Extole)  <br>Funnel (advocate or friend)  <br>Program | <br>External ID <br>Email  <br>Share link |
 | `extole_shared` | A participant shares their referral link with a friend. | Event name  <br>Event time  <br>Partner (Extole)  <br>External ID  <br>Funnel (advocate or friend)  <br>Program  <br>Share channel | Email <br>First name <br>Last Name |
 | `outcome` - The outcome is dynamic based on the configuration of your program (such as `extole_shipped`, `extole_converted`)| A participant has converted or completed the desired outcome event configured for the program. | Dynamic per program | Email <br>First name <br>Last Name |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ### Extole subscription states
 
@@ -63,7 +63,7 @@ Below are the default events, event properties, and user attributes Extole will
 | ----------- | ----------- | ----------- | ----------- |
 | `subscribed` | A participant has opted-in to receive marketing messages. | N/A | Email  <br>List type  <br>External ID  <br>Email subscribe (opted in) |
 | `unsubscribed` | A participant has opted-out of receiving Extole email communications.| Email  <br>External ID  <br>Subscription state (unsubscribed)  <br>Subscription group ID  | List type |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ### Extole rewards
 
@@ -78,7 +78,7 @@ By default, Extole will send reward events in the `FULFILLED` state to Braze so
 | `FAILED` | An issue has prevented the reward from being issued or sent, requiring attention. | Email <br>Face value  <br>Coupon code  <br>Face value type  | Email <br>First name  <br>Last name |
 | `CANCELED` | The reward has been deactivated and will return to inventory. | Email <br>Face value  <br>Face value type  | Email <br>First name  <br>Last name |
 | `REVOKED` | The fulfilled reward has been invalidated. For example, Extole requested a supplier gift card and then determined that the card was sent in error. If the supplier supports revoking the reward, Extole will request the funds back, and the reward will no longer be valid. | Email <br>Face value   <br>Face value type  | Email <br>First name  <br>Last name |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 
 ## Customization
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/friendbuy.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/friendbuy.md
index f6bc5bc25ce..f4ddd76e082 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/friendbuy.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/friendbuy.md
@@ -21,7 +21,7 @@ Before you start, you'll need the following:
 | A Friendbuy account   | A [Friendbuy account][1] is required to take advantage of this partnership.                                                              |
 | A Braze REST API key  | A Braze REST API key with `users.track` permissions. This can be created in the Braze dashboard from **Settings** > **API Keys**.        |
 | A Braze REST endpoint | [Your REST endpoint URL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints), which depends on the URL for your Braze instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can create an API key at **Developer Console** > **API Settings**.
@@ -56,7 +56,7 @@ Go to back to your [Friendbuy account][1] and refresh the page. If your integrat
 | **Friendbuy Coupon Status**      | The status of the most recent coupon code distributed to the customer. Note: status will be 'distributed' or 'redeemed'                            | String    |
 | **Friendbuy Coupon Currency**    | Currency code (USD, CAD, etc.) or percent (%) associated with the most recent coupon code distributed to the customer.                             | String    |
 | **Friendbuy Coupon Campaign ID** | The Campaign ID associated with the coupon code generated for a customer.                                                                          | String    |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Default behavior
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/jebbit.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/jebbit.md
index d99d3b921b9..aebc936d3b0 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/jebbit.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/jebbit.md
@@ -21,7 +21,7 @@ The Braze and Jebbit integration lets you pass user emails and attributes from y
 |Jebbit account | A Jebbit account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with all user data permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 |Braze REST endpoint | Your REST endpoint URL. Your endpoint will depend on the Braze URL for [your instance]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/kognitiv.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/kognitiv.md
index f247d04e14c..06ed32afc80 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/kognitiv.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/kognitiv.md
@@ -20,7 +20,7 @@ The Braze and Kognitiv integration allows you to implement and evaluate your loy
 | Kognitiv account | A [Kognitiv][1] account is required to take advantage of this partnership. |
 | Kognitiv API key | A Kognitiv REST API key. This can be created within the **API Security Tokens** page. |
 | Braze REST endpoint | Your REST endpoint URL. Your endpoint will depend on the Braze URL for [your instance]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/nift.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/nift.md
index 9c68b512ce3..f7c858ed334 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/nift.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/nift.md
@@ -21,7 +21,7 @@ The Braze and Nift integration allows you to automatically trigger "thank-yous"
 | Nift account | A Nift account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with all user data permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | Your REST endpoint URL. Your endpoint will depend on the Braze URL for [your instance]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/punchh/code_generation.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/punchh/code_generation.md
index 0676e39aaa3..45b73a8e5ad 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/punchh/code_generation.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/punchh/code_generation.md
@@ -146,4 +146,4 @@ To link the coupon code inside an image:
 | `usage_exceeded` | The usage for this coupon code's campaign is full. Please try next time. | The usage of the code exceeds the number of users allowed to use it. For example, if the dashboard configuration allows a code to be used by 3,000 users and the number of users exceeds 3,000, this error will occur. |
 | `usage_exceeded_by_guest` | This promo code has already been processed. | The usage of the code by a user exceeds the number of times a user can use it. For example, the dashboard configuration allows a single code to be used three times by a user. If it is used more than that, this error will occur. |
 | `already_used_by_other_guest` | This promo code has already been used by some other guest. | Another user has already used the code. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/punchh/punchh.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/punchh/punchh.md
index 85b68170bfa..4879606fcce 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/punchh/punchh.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/punchh/punchh.md
@@ -29,7 +29,7 @@ The Braze and Punchh integration allows you to sync data for gifting and loyalty
 | Punchh account | You need an active Punchh account to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][6]. Your endpoint depends on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## What else should I know?
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/sessionm.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/sessionm.md
index a4bbe8b919e..b6095ff9e36 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/sessionm.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/sessionm.md
@@ -25,7 +25,7 @@ search_tag: Partner
 | SessionM | A SessionM Connect REST endpoint | Your endpoint will depend on the SessionM URL of your instance. Please reach out to your SessionM technical account manager or Delivery team to provide. |
 | SessionM | A SessionM Connect REST Authorization string | The SessionM Connect Basic Authorization string associated with your instance. This authentication string can be used for all connect based calls including get_user_offers. Please reach out to your SessionM technical account manager or Delivery team to provide. |
 | SessionM | A SessionM Connect REST Retailer ID | A unique guid identification to the specific customer associated with your instance. Reach out to your SessionM technical account manager or Delivery team. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert note %} 
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can create an API key at **Developer Console** > **API Settings**. 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/talonone.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/talonone.md
index a60bca60fa1..9a9e0e17481 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/talonone.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/talonone.md
@@ -21,7 +21,7 @@ The Braze and Talon.One integration can help take your loyalty or coupon program
 | ----------- | ----------- |
 |Talon.One account | A Talon.One account is required to take advantage of this partnership. |
 |Talon.One API key | In Talon.One, under **Settings** > **Developer Settings**, create a Braze 3rd party API key for the integration. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert warning %}
 Talon.One **_requires_** a maximum rate limit of 2,500 messages per minute. This rate limit can be [modified]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#delivery-speed-rate-limiting) in the Braze dashboard.
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/viralsweep.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/viralsweep.md
index 3b2e3dbf0af..a7965712b6a 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/viralsweep.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/viralsweep.md
@@ -21,7 +21,7 @@ The Braze and ViralSweep integration allows you to hold sweepstakes and contests
 | ViralSweep account | A ViralSweep account utilizing the business plan is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with all user data and email permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 |Braze REST endpoint | Your REST endpoint URL. Your endpoint will depend on the Braze URL for [your instance]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify.md
index 65112b3c053..4c6d2ed80ab 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify.md
@@ -27,7 +27,7 @@ The Braze and Voucherify integration allows you to grow your promotional campaig
 | ----------- | ----------- |
 |Voucherify account | A Voucherify account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content.md
index 7a4303ec9fd..e74b59cca8b 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content.md
@@ -92,7 +92,7 @@ You can modify {% raw %}`{{source_id}}`{% endraw %} and its effect on publicatio
 | {% raw %}`{{campaign.${api_id}}}`{% endraw %} | All customers within a single campaign will use the same publication. |
 | {% raw %}`{{${user_id}}}`{% endraw %} or {% raw %}`{{${braze_id}}}`{% endraw %} | Checks that every customer will use the same publication no matter which campaign is sent (you can use {% raw %}`${user_id}`{% endraw %} which is an {% raw %}`external_id`{% endraw %} and {% raw %}`${braze_id}`{% endraw %} which is an internal id). |
 | {% raw %}`{{campaign.${dispatch_id}}}`{% endraw %} and {% raw %}`{{campaign.${user_id}}}`{% endraw %} | Each customer within a single send-out will use the same unique publication. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Join-once %}
@@ -367,7 +367,7 @@ We're assuming you already have a Braze campaign or Canvas in which you want to
     | Europe (default) | https://api.voucherify.io/v1/publications     |
     | United States    | https://us1.api.voucherify.io/v1/publications |
     | Asia (Singapore) | https://as1.api.voucherify.io/v1/publications |
-    {: .reset-td-br-1 .reset-td-br-2}
+    {: .reset-td-br-1 .reset-td-br-2 role="presentation" }
     
 3.  Add your API keys for authentication. You can find `Voucherify-App-Id` and `Voucherify-App-Token` in your **Project Settings > General >Application Keys.**<br>![]({% image_buster /assets/img/voucherify/voucherify_cc_app_keys.png %}){: style="margin-top:15px;margin-bottom:15px;"}
     {% raw %}
diff --git a/_docs/_partners/message_orchestration/channel_extensions/surveys/ada.md b/_docs/_partners/message_orchestration/channel_extensions/surveys/ada.md
index 1a4a008def9..9a1c99bbe9c 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/surveys/ada.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/surveys/ada.md
@@ -21,7 +21,7 @@ The Braze and Ada integration allows you to augment user profiles with data coll
 | Ada account | An [Ada](https://ada.cx) account with the Braze and Answer Utilities applications enabled is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/surveys/digioh.md b/_docs/_partners/message_orchestration/channel_extensions/surveys/digioh.md
index 57a33e9eaa9..7ab78a9b13b 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/surveys/digioh.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/surveys/digioh.md
@@ -23,7 +23,7 @@ The Braze and Digioh integration allows you to use their flexible drag-and-drop
 |Digioh account | A [Digioh account](https://www.digioh.com/) is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze API `/users/track/` endpoint | Your REST endpoint URL with the `/users/track/` details appended to it. Your endpoint will depend on the [Braze URL for your instance][6].<br><br>For example, if your REST API endpoint is `https://rest.iad-01.braze.com` your `/users/track/` endpoint will be `https://rest.iad-01.braze.com/users/track/`. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Integration 
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/surveys/iterate.md b/_docs/_partners/message_orchestration/channel_extensions/surveys/iterate.md
index d579bd5ad4d..8b1469b0036 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/surveys/iterate.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/surveys/iterate.md
@@ -23,7 +23,7 @@ With the Braze SDK installed in your app or website, you can use the segmentatio
 |Iterate account | A [Iterate account](https://iteratehq.com) is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. To send surveys via Braze in-app messages, you'll also need the `kpi.mau.data_series` permission.<br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**.|
 | Braze REST endpoint  | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][6]. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_orchestration/channel_extensions/surveys/typeform.md b/_docs/_partners/message_orchestration/channel_extensions/surveys/typeform.md
index de34ec57970..4d00cc8407b 100644
--- a/_docs/_partners/message_orchestration/channel_extensions/surveys/typeform.md
+++ b/_docs/_partners/message_orchestration/channel_extensions/surveys/typeform.md
@@ -23,7 +23,7 @@ By integrating Braze and Typeform, you can:
 | ----------- | ----------- |
 | Typeform account | A Typeform account with access to webhooks is required to take advantage of this partnership. |
 | Braze Data Transformation | A [Data Transformation URL]({{site.baseurl}}/data_transformation/) is necessary to receive data from Typeform. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_orchestration/learning/edume.md b/_docs/_partners/message_orchestration/learning/edume.md
index 7754f9ae1cd..91ef94a6142 100644
--- a/_docs/_partners/message_orchestration/learning/edume.md
+++ b/_docs/_partners/message_orchestration/learning/edume.md
@@ -22,7 +22,7 @@ The Braze and eduMe integration leverages Braze [Connected Content]({{site.baseu
 | eduMe API key | You must request an API key from your eduMe customer success contact. This key will be used in your Braze Connected Content call. |
 | eduMe link signing secret | You must request your customer success contact at eduMe to set up a link signing secret for your organization. This secret is used to enable seamless links in Connected Content. You will not have to do anything with this secret. |
 | eduMe group and content IDs | These identifiers are needed to set up your Connected Content calls. Reach out to your eduMe customer service contact for help obtaining these identifiers. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization.md b/_docs/_partners/message_personalization.md
index eb4775724ad..dda43c887d4 100644
--- a/_docs/_partners/message_personalization.md
+++ b/_docs/_partners/message_personalization.md
@@ -75,4 +75,6 @@ valid_partner_list:
   url: /docs/partners/message_personalization/dynamic_content/niftyimages/
 - name: Future Anthem
   url: /docs/partners/message_personalization/dynamic_content/future_anthem
+- name: SEEN
+  url: /docs/partners/message_personalization/dynamic_content/seen
 ---
diff --git a/_docs/_partners/message_personalization/dynamic_content.md b/_docs/_partners/message_personalization/dynamic_content.md
index cb659a90e64..2e1055d2024 100644
--- a/_docs/_partners/message_personalization/dynamic_content.md
+++ b/_docs/_partners/message_personalization/dynamic_content.md
@@ -49,4 +49,6 @@ valid_partner_list:
   url: /docs/partners/message_personalization/dynamic_content/niftyimages
 - name: Future Anthem
   url: /docs/partners/message_personalization/dynamic_content/future_anthem
+- name: SEEN
+  url: /docs/partners/message_personalization/dynamic_content/seen
 ---
diff --git a/_docs/_partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize.md b/_docs/_partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize.md
index 48337150934..7963588a1ce 100644
--- a/_docs/_partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize.md
+++ b/_docs/_partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize.md
@@ -24,7 +24,7 @@ This reference article will help you understand the use cases Amazon Personalize
 | Amazon Web Service account | An AWS account is required to take advantage of this partnership. After you have an AWS account, you can access Amazon Personalize through the Amazon Personalize console, the AWS Command Line Interface (AWS CLI), or the AWS SDKs. |
 | Defined use cases | Before creating a model, you must determine your use case for this integration. Reference the following list for common use cases. |
 | Datasets | Amazon Personalize recommendation models require three different types of datasets, interactions, users, and items. Reference the following details to see the requirements for each dataset. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% tabs %}
 {% tab Use Cases %}
diff --git a/_docs/_partners/message_personalization/dynamic_content/certona.md b/_docs/_partners/message_personalization/dynamic_content/certona.md
index 2730e3c8e64..3fa43811202 100644
--- a/_docs/_partners/message_personalization/dynamic_content/certona.md
+++ b/_docs/_partners/message_personalization/dynamic_content/certona.md
@@ -20,7 +20,7 @@ The Braze and Certona integration leverages Certona's machine learning product r
 | ---| ---|
 | [Certona account](https://manage.certona.com/) | A Certona account is required to take advantage of this partnership. |
 | [Certona REST API endpoint](https://manage.certona.com/) | This endpoint is used directly in your Braze campaign message to pull recommended content based on user ID. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/dynamic_yield.md b/_docs/_partners/message_personalization/dynamic_content/dynamic_yield.md
index d9dd5fde4af..c4ebb9f4ea2 100644
--- a/_docs/_partners/message_personalization/dynamic_content/dynamic_yield.md
+++ b/_docs/_partners/message_personalization/dynamic_content/dynamic_yield.md
@@ -21,7 +21,7 @@ The Braze and Dynamic Yield partnership allows you to leverage Dynamic Yield's r
 | Requirement | Description |
 | ----------- | ----------- |
 | Dynamic Yield account | A [Dynamic Yield](https://adm.dynamicyield.com/users/sign_in#/r/dashboard) account is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/fresh_relevance.md b/_docs/_partners/message_personalization/dynamic_content/fresh_relevance.md
index ac81fcb75fc..d387d737473 100644
--- a/_docs/_partners/message_personalization/dynamic_content/fresh_relevance.md
+++ b/_docs/_partners/message_personalization/dynamic_content/fresh_relevance.md
@@ -27,7 +27,7 @@ The Braze and Fresh Relevance integration allows you to:
 | Braze REST API key | A Braze REST API key with permissions sufficient for the endpoints listed below. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][3]. Your endpoint will depend on the Braze URL for your instance. |
 | Braze campaign ID | The default Braze campaign that you want to use to send emails. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/future_anthem.md b/_docs/_partners/message_personalization/dynamic_content/future_anthem.md
index f1a7bcd3477..c45268e6bab 100644
--- a/_docs/_partners/message_personalization/dynamic_content/future_anthem.md
+++ b/_docs/_partners/message_personalization/dynamic_content/future_anthem.md
@@ -22,7 +22,7 @@ This feature is currently in Early Access. Please reach out to the Future Anthem
 | Future Anthem Account    | A Future Anthem account. |
 | Braze REST API key       | A Braze REST API key with the [`users.track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track). This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint      | The Braze [REST endpoint](https://www.braze.com/docs/developer_guide/rest_api/basics/#endpoints) that matches your instance, such as `rest.iad-01.com`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use Cases
 
@@ -53,7 +53,7 @@ These are the available Braze custom attributes. For more detailed information,
 | Accumulator Bet Recommendations | `{"Bet_1": "Halland Goal vs. Manchester United", "Bet_2": "Liverpool vs. Everton"}`| Object |
 | Accumulator Bet Recommendations | `{"Bet_1": 1.5, "Bet_2": 2}` | Object |
 | Bet Builder Bet Recommendations | `{"Sport":"American Football", "Competition":"NFL", "Event":"Seahwaks@Giants", "Market":"MoneyLine", "Selection":"Seahawks"}`| Object |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Bonus Recommendations %}
@@ -70,7 +70,7 @@ These are the available Braze custom attributes. For more detailed information,
 | Other bonus value recommendations in the future | 0 | Number |
 | Future CLTV  | 3126 | Number |
 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Game Recommendations %}
@@ -86,7 +86,7 @@ These are the available Braze custom attributes. For more detailed information,
 | Popular Games | Temple of Iris, Fishin’ Frenzy, Rishing Reward, Crazy Time, Fluffy Favourites | Array |
 | Trending Games | Pig Banker, Hyper Gold, Pyramid King, Gold Cash | Array |
 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 
 {% tab Player Cluster %}
@@ -94,15 +94,15 @@ These are the available Braze custom attributes. For more detailed information,
 | Subcategory | Example | Datatype |
 | ------- | ----------- |----------- |
 | Showcase what cluster the player is in | High Value Game Diverse| String |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 
-{% tab Player Sustain (Player potential risk) %}
+{% tab Player Sustain - Player potential risk %}
 
 | Subcategory | Example | Datatype |
 | ------- | ----------- |----------- |
 | Risk Score | 0.5| Number |
 | Risky Player | True | Boolean |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% endtabs %}
diff --git a/_docs/_partners/message_personalization/dynamic_content/judo.md b/_docs/_partners/message_personalization/dynamic_content/judo.md
index a3bb157a8a3..b424b6e9068 100644
--- a/_docs/_partners/message_personalization/dynamic_content/judo.md
+++ b/_docs/_partners/message_personalization/dynamic_content/judo.md
@@ -20,7 +20,7 @@ The Braze and Judo integration provides bespoke experiences in your campaigns an
 |---|---|
 | Judo Account | A [Judo](https://www.judo.app/) account is required to take advantage of this partnership. |
 | Judo SDK | The Judo SDK must be integrated into your [iOS](https://github.com/judoapp/judo-ios/) and/or [Android](https://github.com/judoapp/judo-android) apps. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/komo.md b/_docs/_partners/message_personalization/dynamic_content/komo.md
index 6db43286516..4438a1dd7bf 100644
--- a/_docs/_partners/message_personalization/dynamic_content/komo.md
+++ b/_docs/_partners/message_personalization/dynamic_content/komo.md
@@ -26,19 +26,19 @@ The Braze and Komo integration allows you to gather first and zero-party data th
 | Komo account | You will need an active Komo account to take advantage of this partnership. Visit [Komo][7] to start a trial now. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance.<br><br>For example, it should look something like: https://rest.iad-03.braze.com |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Use cases
 
 {% tabs local %}
-{% tab Data Capture (Form Submission) %}
+{% tab Data Capture - Form Submission %}
 
 When a user submits a customizable data capture form in Komo, the Komo fields mapped in the Braze integration will be passed to Braze via the `/users/track/` API call.
 
 Data capture forms exist either at the start or end of Cards.
 
 {% endtab %}
-{% tab Market Research (Coming soon) %}
+{% tab Market Research - Coming soon %}
 
 Coming soon, Komo will be adding the ability to pass through market research data captured when a user answers a quiz question, poll, personality test, swiper, etc. This data will enable you to enhance a user's profile beyond data captured in form submissions.
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/liftigniter.md b/_docs/_partners/message_personalization/dynamic_content/liftigniter.md
index 2f390002722..060dcd50c73 100644
--- a/_docs/_partners/message_personalization/dynamic_content/liftigniter.md
+++ b/_docs/_partners/message_personalization/dynamic_content/liftigniter.md
@@ -20,7 +20,7 @@ The LiftIgniter and Braze integration leverage Connected Content to allow you to
 | ---| ---|
 | LiftIgniter account | A [LiftIgniter account](https://console.liftigniter.com/login) is required to take advantage of this partnership. |
 | LiftIgniter API integration | You must [integrate](https://support.liftigniter.com/support/solutions/articles/30000024667-api-integration-overview) LiftIgniter into your site or app to be able to pull recommendations from there. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/movable_ink.md b/_docs/_partners/message_personalization/dynamic_content/movable_ink.md
index 116fc942f29..12daafc503e 100644
--- a/_docs/_partners/message_personalization/dynamic_content/movable_ink.md
+++ b/_docs/_partners/message_personalization/dynamic_content/movable_ink.md
@@ -20,7 +20,7 @@ Expand our creative capabilities by leveraging Movable Ink's Intelligent Creativ
 |---|---|
 | Movable Ink account | A Movable Ink account is required to take advantage of this partnership. |
 | Data source | You'll need to connect a data source to Movable Ink. This can be done through CSV, website import, or API. Make sure that you pass data with a unifying identifier between Braze and Movable Ink (for example, `external_id`).
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
@@ -48,7 +48,7 @@ Intelligent Creative has many offerings that Braze users can take advantage of.
 || Polling | ✗ | ✔* | * After voting, will leave the app to be a mobile landing page |
 || Scratch Off | ✔* | ✔* | * On click, will leave the app for the Scratch Off experience |
 || Video | ✔* | ✔* | * Animated GIFs only, <br>For Android, Braze requires [GIF support][GIFsupport] in implementation |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/movable_ink/customer_data_api.md b/_docs/_partners/message_personalization/dynamic_content/movable_ink/customer_data_api.md
index ca8777f4174..2c66c301795 100644
--- a/_docs/_partners/message_personalization/dynamic_content/movable_ink/customer_data_api.md
+++ b/_docs/_partners/message_personalization/dynamic_content/movable_ink/customer_data_api.md
@@ -26,7 +26,7 @@ For more information on Stories, the Movable Ink Customer Data API, and how Mova
 | Movable Ink API credentials | Movable Ink's Solutions team will generate API credentials for you. The API credentials consist of:{::nomarkdown}<ul><li>An endpoint URL (where the data will be sent to)</li><li>Username and password (used to authenticate the API)</li></ul>{:/} If desired, Movable Ink can supply the username and password as a base64-encoded value to be used as a basic authorization header value. |
 | Behavioral event payloads | You will need to share your event payloads with your Movable Ink Client Experience team. See [Sharing event payloads](#event-payloads) with Movable Ink for details. |
 | Creative assets and business logic | You will need to share creative assets with Movable Ink, including Adobe Photoshop (PSD) files directing Movable Ink on how to build the block and a fallback image. You will also need to provide business logic for how and when to display the partner-activated Content Block. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
@@ -52,7 +52,7 @@ For more information on Stories, the Movable Ink Customer Data API, and how Mova
 | --- | --- |
 | Content-Type | application/json |
 | Authorization | Enter the Basic Authentication you received from Movable Ink. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![Settings tab of the webhook composer in Braze with key-value pairs for Content-Type and Authorization.][img2]{: style="max-width:75%" }
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/movable_ink/dynamic_sms_link.md b/_docs/_partners/message_personalization/dynamic_content/movable_ink/dynamic_sms_link.md
index b9c4d369d49..c284108a673 100644
--- a/_docs/_partners/message_personalization/dynamic_content/movable_ink/dynamic_sms_link.md
+++ b/_docs/_partners/message_personalization/dynamic_content/movable_ink/dynamic_sms_link.md
@@ -19,7 +19,7 @@ search_tag: Partner
 | MMS sending capabilities | Confirm that you're set up for MMS through Braze.
 | [Link shortening]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/) | Confirm that link shortening is turned on. | 
 | Contact card | Your brand (the sender) must be saved as a contact on the user's phone for link preview to work with iOS. This can be done with a contact card or another method. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/offerfit.md b/_docs/_partners/message_personalization/dynamic_content/offerfit.md
index 714676f0c50..6511b20ce8a 100644
--- a/_docs/_partners/message_personalization/dynamic_content/offerfit.md
+++ b/_docs/_partners/message_personalization/dynamic_content/offerfit.md
@@ -22,7 +22,7 @@ The OfferFit and Braze integration allows you to automatically discover the righ
 | OfferFit License | An active OfferFit license is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with the following permissions: {::nomarkdown}<ul><li><code>users.export.ids</code></li><li><code>users.export.segment</code></li><li><code>messages.send</code></li><li><code>campaigns.trigger.send</code></li> <li><code>campaigns.list</code></li><li><code>campaigns.data_series</code></li><li><code>campaigns.details</code></li><li><code>canvas.trigger.send</code></li><li><code>canvas.list</code></li><li><code>canvas.data_series</code></li><li><code>canvas.details</code></li><li><code>segments.list</code></li><li><code>segments.data_series</code></li><li><code>segments.details</code></li><li><code>templates.create</code></li><li><code>templates.update</code></li><li><code>templates.info</code></li><li><code>templates.list</code></li></ul>{:/} This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST API endpoint | [Your REST API endpoint URL][1]. Your endpoint depends on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can create an API key at **Developer Console** > **API Settings**.
@@ -53,7 +53,7 @@ Your OfferFit license and use case will determine the Braze REST API endpoints y
 | [POST /templates/email/update]({{site.baseurl}}/api/endpoints/templates/email_templates/post_update_email_template/)      | Update an existing Braze HTML email template. |
 | [GET /templates/email/info]({{site.baseurl}}/api/endpoints/templates/email_templates/get_see_email_template_information/) | Retrieve the details of a specific Braze HTML email template. |
 | [GET /templates/email/list]({{site.baseurl}}/api/endpoints/templates/email_templates/get_list_email_templates/)           | Retrieve the list of all the Braze HTML email templates configured in Braze and their `subject line` and `HTML content`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
@@ -81,7 +81,7 @@ The OfferFit AI will learn from every customer interaction and apply those insig
 | **Referral** | Maximize new accounts opened through business credit card referrals from existing customers. | Fixed email sequence for all customers, with extensive A/B testing to determine the best sending times, cadence, etc. for the customer population. | Automate experimentation to determine ideal email, creative, sending time, and credit card to offer specific customers. |
 | **Lead Nurturing & Conversion** | Drive incremental revenue and pay the right amount for each customer. | As privacy policies change at Facebook and other platforms, prior approaches to personalized paid ads become last effective. | Leverage robust first-party data to automatically experiment on customer segments, biding methodology, bid levels, and creative. |
 | **Loyalty & Engagement** | Maximize purchases by new enrollees in customer loyalty program. | Customers received fixed sequence of emails in response to their actions. For example, all new enrollees in the loyalty program receive the same journey. | Experiment automatically with different email offers, creative, sending time, and frequency to maximize purchase and repurchase for each customer. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 
 ## Integration
diff --git a/_docs/_partners/message_personalization/dynamic_content/personalize.md b/_docs/_partners/message_personalization/dynamic_content/personalize.md
index ae50821c05c..de55dd69703 100644
--- a/_docs/_partners/message_personalization/dynamic_content/personalize.md
+++ b/_docs/_partners/message_personalization/dynamic_content/personalize.md
@@ -20,7 +20,7 @@ The Braze and Personalize.AI integration allows you to export data from Personal
 | Personalize.AI instance | A Personalize.AI instance is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with all permissions. <br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | Your REST endpoint URL. Your endpoint will depend on the [Braze URL for your instance][1]. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
@@ -68,7 +68,7 @@ For example, here is a set of customer attributes as they relate to an example c
 | `C4_Offer_Value` | $3 |
 | `C4_Item_Recom` | "Caesar Salad" |
 | `C4_Subject_Line` | "We miss you" |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
diff --git a/_docs/_partners/message_personalization/dynamic_content/playable.md b/_docs/_partners/message_personalization/dynamic_content/playable.md
index 92af115ddcf..20354578332 100644
--- a/_docs/_partners/message_personalization/dynamic_content/playable.md
+++ b/_docs/_partners/message_personalization/dynamic_content/playable.md
@@ -20,7 +20,7 @@ The Braze and Playable integration allows you to deliver your best content (high
 | ----------- | ----------- |
 | Playable Account | A Playable account is required to take advantage of this partnership. If you do not already have a Playable account, sign up [here][signup].
 Video Content | Upload video files to Playable or provide video URLs from websites like Facebook, Instagram, YouTube, X (formerly Twitter), TikTok, and more. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Implementation
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/seen.md b/_docs/_partners/message_personalization/dynamic_content/seen.md
new file mode 100644
index 00000000000..33182c3cbe1
--- /dev/null
+++ b/_docs/_partners/message_personalization/dynamic_content/seen.md
@@ -0,0 +1,127 @@
+---
+nav_title: SEEN
+article_title: SEEN
+description: "SEEN’s personalized videos has helped companies reach unmatched attention and engagement, throughout their customer journey."
+alias: /partners/seen/
+page_type: partner
+search_tag: Partner
+---
+
+# SEEN
+
+> [SEEN’s](https://seen.io/) personalized videos has helped companies reach unmatched attention and engagement, throughout their customer journey. Personalize videos with SEEN in three simple steps:<br>1. Design a video around your data.<br>2. Personalize it at scale in the cloud.<br>3. Distribute it where it works best.
+
+## Use cases
+
+SEEN offers automated video personalization across the entire the customer journey. Common uses include Onboarding, Loyalty, Sign-ups/Conversion, and Win-back/Anti-churn.
+
+## Prerequisites
+
+Before you start, you'll need the following:
+
+| Prerequisite          | Description                                                                                                                                |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| A SEEN campaign   | A SEEN campaign is required to take advantage of this partnership.                                                                     |
+| Data source   | You'll need to send data to SEEN to personalize your videos. Make sure you have all relevant data available in Braze, and that you pass data with **braze_id** as the identifier. |
+| Braze Data Transformation Webhook URL   | Braze Data Transformation will be used to reformat the incoming data from SEEN so it can be accepted by Braze’s /users/track endpoint. |
+
+## Rate limit
+
+The SEEN API currently accepts 1000 calls per hour.
+
+## Integrating SEEN with Braze
+
+In the following example, we will be sending users data to SEEN for video generation, and receiving a unique landing page link and a unique, personalized thumbnail back to Braze for distribution. This example uses a POST webhook to send data to SEEN, and data transformation to receive the data back to Braze. If you have multiple video campaigns with SEEN, repeat the process to connect Braze with all video campaigns.
+
+{% alert tip %}
+If you experience any issues, you can reach out to your Customer Success Manager at SEEN for assistance.
+{% endalert %}
+
+### Step 1: Create a webhook campaign
+
+Create a new [Webhook Campaign](https://www.braze.com/docs/user_guide/message_building_by_channel/webhooks) in Braze. Give your campaign a name, then refer to the following table to compose your webhook:
+
+{% raw %}
+<table>
+  <thead>
+    <tr>
+      <th><strong>Field</strong></th>
+      <th><strong>Details</strong></th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td><strong>Webhook URL</strong></td>
+      <td>Use the following webhook URL. You will receive your <code>campaign_slug</code> from SEEN to call the correct endpoint.<br><br><code>https://api.seen.io/v1/campaigns/{campaign_slug}/receivers/</code></td>
+    </tr>
+    <tr>
+      <td><strong>HTTP Method</strong></td>
+      <td>Use the <code>POST</code> method.</td>
+    </tr>
+    <tr>
+      <td><strong>Request body</strong></td>
+      <td>Enter your request body in raw text similar to the following.<br><br><pre><code>[
+    {
+    "first_name":"{{${first_name}}}",
+    "last_name":"{{${last_name}}}",
+    "email":"{{${email_address}}}",
+    "customer_id":"{{${braze_id}}}"
+    }
+]</code></pre><br>For more information, see <a href="https://docs.seen.io/api-documentation/ntRoJJ3rXoHzFXhA94JiHB/overview/tvy2F5tS3JRM7DfcHwz5fK#request-content">SEEN API</a>.</td>
+    </tr>
+    <tr>
+      <td><strong>Request headers</strong></td>
+      <td>Use the following information to fill out your request headers:<br>- <strong>Authorization:</strong> <code>Token {token}</code><br>- <strong>Content-Type:</strong> <code>application/json</code><br><br>You will receive your Authentication Token from SEEN.</td>
+    </tr>
+  </tbody>
+</table>
+{% endraw %}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+
+You can now test the webhook with a user by switching to the **Test** tab.
+
+If everything works as intended, go to Braze and set the rate at which the campaign sends to 10 **messages per minute**. This ensures that you won't exceed the SEEN's rate limit of 1000 calls per hour.
+
+### Step 2: Create data transformation
+
+1. Create new [Custom Attribute](https://www.braze.com/docs/user_guide/data_and_analytics/custom_data/custom_attributes/#managing-custom-attributes) fields for `landing_page_url` and `email_thumbnail_url`. These are the two attributes we will be using in this example.
+2. Open [Data Transformation](https://www.braze.com/docs/user_guide/data_and_analytics/data_transformation/creating_a_transformation/#prerequisites) tool under **Data Settings**, and select **Create transformation**.
+3. Give your transformation a name, then choose **Start from scratch** and set **Destination** to **POST: Track users**.
+4. Select **Share your Webhook URL with SEEN**.
+5. You can use the code below as the starting point for the transformation:
+
+```javascript
+let brazecall = {
+  "attributes": [
+    {
+      "braze_id": payload.customer_id,
+      "_update_existing_only": true,
+      "landing_page_url": payload.landing_page_url,
+      "email_thumbnail_url": payload.email_thumbnail_url
+    }
+  ]
+};
+return brazecall;
+```
+{% alert note %}
+If you want to include other data, make sure to include those as well. Remember to discuss with SEEN as well so that the callback payload includes all needed fields.
+{% endalert %}
+
+{: start="6"}
+6. Send a test payload to the provided endpoint. If you want to use the callback payload defined in [the SEEN documentation](https://docs.seen.io/api-documentation/ntRoJJ3rXoHzFXhA94JiHB/callbacks/k9DEbcgkq3Vr2pxbHyPQbp), you can send this yourself via [Postman](https://www.postman.com/) or another similar service:
+
+```json
+{
+        "customer_id": "101",
+        "campaign_slug": "onboarding",
+        "landing_page_url": "your.subdomain.com/v/12345",
+        "video_url": "https://motions.seen.io/298abdcf-1f0f-46e7-9c26-a35b4c1e83cc/d3c1dffdf063986ad521a63e3e68fd7d1100c90a/output.m3u8",
+        "thumbnail_url": "https://motions.seen.io/298abdcf-1f0f-46e7-9c26-a35b4c1e83cc/d3c1dffdf063986ad521a63e3e68fd7d1100c90a/thumbnail.jpg",
+        "email_thumbnail_url": "https://motions.seen.io/298abdcf-1f0f-46e7-9c26-a35b4c1e83cc/d3c1dffdf063986ad521a63e3e68fd7d1100c90a/email_thumbnail.jpg"
+       
+}
+```
+
+{: start="7"}
+7. Select **Validate** to make sure everything works as intended.
+8. If everything worked as intended, select **Save** and **Activate**.
diff --git a/_docs/_partners/message_personalization/dynamic_content/sheetlabs.md b/_docs/_partners/message_personalization/dynamic_content/sheetlabs.md
index 03a3b89ae83..1968e1f46fb 100644
--- a/_docs/_partners/message_personalization/dynamic_content/sheetlabs.md
+++ b/_docs/_partners/message_personalization/dynamic_content/sheetlabs.md
@@ -19,7 +19,7 @@ The Sheetlabs and Braze integration allows you to leverage [Connected Content][2
 | Requirement | Description |
 | ----------- | ----------- |
 | Sheetlabs account | A [Sheetlabs account][1] is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/storyly.md b/_docs/_partners/message_personalization/dynamic_content/storyly.md
index 3a2f8adf907..06d5d1247fa 100644
--- a/_docs/_partners/message_personalization/dynamic_content/storyly.md
+++ b/_docs/_partners/message_personalization/dynamic_content/storyly.md
@@ -24,7 +24,7 @@ The Braze and Storyly integration allows you to use your segments in Braze as an
 | Storyly SDK | You must install the [Storyly SDK](https://integration.storyly.io/). |
 | Braze REST API key | A Braze REST API key with the following permissions <br><br> `users.export.ids`<br> `users.export.segments`<br> `segments.list`<br> `segments.details` <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/stylitics.md b/_docs/_partners/message_personalization/dynamic_content/stylitics.md
index 09922ac17da..cb2cb999de7 100644
--- a/_docs/_partners/message_personalization/dynamic_content/stylitics.md
+++ b/_docs/_partners/message_personalization/dynamic_content/stylitics.md
@@ -21,7 +21,7 @@ Your Braze and Stylitics integration allows you to enhance your existing email c
 | Requirement | Description |
 | ----------- | ----------- |
 | Stylitics account | A [Stylitics](https://stylitics.com/) account is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/worthy.md b/_docs/_partners/message_personalization/dynamic_content/worthy.md
index 4ba6f451e0d..5673a71e7d2 100644
--- a/_docs/_partners/message_personalization/dynamic_content/worthy.md
+++ b/_docs/_partners/message_personalization/dynamic_content/worthy.md
@@ -30,7 +30,7 @@ search_tag: Partner
 | --- | --- |
 | [Worthy](https://worthy.ai/) account | A Worthy account is required to take advantage of this partnership. |
 | Braze SDK | You will need to configure the Braze SDK in your mobile application to send rich in-app messages. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/wsc_sports.md b/_docs/_partners/message_personalization/dynamic_content/wsc_sports.md
index 22342d4ee43..66127e04863 100644
--- a/_docs/_partners/message_personalization/dynamic_content/wsc_sports.md
+++ b/_docs/_partners/message_personalization/dynamic_content/wsc_sports.md
@@ -20,7 +20,7 @@ The Braze and WSC Sports integration allows you to include rich and robust sport
 | ----------- | ----------- |
 | WSC account | A WSC account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with **Messages**, **Segments**, **Campaigns** and **Canvas** permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/dynamic_content/wyng.md b/_docs/_partners/message_personalization/dynamic_content/wyng.md
index fac9f1f5dc5..65f5911f424 100644
--- a/_docs/_partners/message_personalization/dynamic_content/wyng.md
+++ b/_docs/_partners/message_personalization/dynamic_content/wyng.md
@@ -19,7 +19,7 @@ The Braze and Wyng integration allows you to leverage zero-party data earned via
 | ----------- | ----------- |
 | Wyng account | A Wyng account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/localization/crowdin.md b/_docs/_partners/message_personalization/localization/crowdin.md
index feabedc7824..b0b3360086e 100644
--- a/_docs/_partners/message_personalization/localization/crowdin.md
+++ b/_docs/_partners/message_personalization/localization/crowdin.md
@@ -22,7 +22,7 @@ The Braze and Crowdin integration allows you to translate email templates and Co
 | Crowdin translation project | To connect your Braze account with Crowdin or Crowdin Enterprise, you will first need to sign up and create a translation project. |
 | Braze REST API key | A Braze REST API key with all templates and Content Blocks permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze SDK endpoint | Your SDK endpoint URL will depend on the Braze URL for [your instance]({{site.baseurl}}/api/basics/#endpoints). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/localization/lokalise.md b/_docs/_partners/message_personalization/localization/lokalise.md
index d7adecced20..0d2523fb971 100644
--- a/_docs/_partners/message_personalization/localization/lokalise.md
+++ b/_docs/_partners/message_personalization/localization/lokalise.md
@@ -20,7 +20,7 @@ The Braze and Lokalise integration leverages Connected Content to allow you to e
 | ----------- | ----------- |
 | Lokalise account | A Lokalise account is required to take advantage of this partnership. |
 | Lokalise translation project | A Lokalise translation project should be created before setting up this integration. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Create a new Lokalise project
 
diff --git a/_docs/_partners/message_personalization/localization/phrase.md b/_docs/_partners/message_personalization/localization/phrase.md
index 16d4cabc5eb..a465b14817d 100644
--- a/_docs/_partners/message_personalization/localization/phrase.md
+++ b/_docs/_partners/message_personalization/localization/phrase.md
@@ -21,7 +21,7 @@ The Phrase and Braze integration allow you to translate email templates and Cont
 | Phrase TMS account | A Phrase TMS Ultimate or Enterprise account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with all permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/localization/smartling.md b/_docs/_partners/message_personalization/localization/smartling.md
index 760da270b14..22b3ac7001a 100644
--- a/_docs/_partners/message_personalization/localization/smartling.md
+++ b/_docs/_partners/message_personalization/localization/smartling.md
@@ -21,7 +21,7 @@ The Braze and Smartling integration allows you to translate email templates and
 | Smartling translation project | To connect your Braze account with Smartling, you must first sign up and [create a translation project][3]. |
 | Braze REST API key | A Braze REST API key with all templates and Content Blocks permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze REST endpoint | [Your REST endpoint URL][1]. Your endpoint will depend on the Braze URL for your instance. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/localization/transifex.md b/_docs/_partners/message_personalization/localization/transifex.md
index 63d7cfc7c35..7db9fb8de78 100644
--- a/_docs/_partners/message_personalization/localization/transifex.md
+++ b/_docs/_partners/message_personalization/localization/transifex.md
@@ -23,7 +23,7 @@ As of April 7, 2022, Transifex has deprecated their API versions 2 and 2.5 to ma
 | Requirement| Description|
 | ---| ---|
 |Transifex Account | A [Transifex account](https://www.transifex.com/signin/) is required to take advantage of this partnership. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/location/accuweather.md b/_docs/_partners/message_personalization/location/accuweather.md
index d180fe00a82..e23fdc21fc4 100644
--- a/_docs/_partners/message_personalization/location/accuweather.md
+++ b/_docs/_partners/message_personalization/location/accuweather.md
@@ -17,7 +17,7 @@ search_tag: Partner
 | Requirement | Description |
 |---|---|
 | AccuWeather API Key | Contact your AccuWeather account manager for compatible API keys to use in your request URLs.<br><br>Further instructions can be found on the [AccuWeather Enterprise API][57] page. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Available AccuWeather APIs
 
@@ -34,7 +34,7 @@ The following are the AccuWeather APIs you can reference within your Braze campa
 | [Imagery][54] | Get radar and satellite images. |
 | [Tropical][55] | Get current position, past positions, and forecasts for tropical cyclones worldwide. |
 | [Translations][56] | Get a list of available languages. Get translations for specific groups of phrases. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Connected Content example
 
diff --git a/_docs/_partners/message_personalization/location/bluedot.md b/_docs/_partners/message_personalization/location/bluedot.md
index 65552e183fd..7f214beaa2d 100644
--- a/_docs/_partners/message_personalization/location/bluedot.md
+++ b/_docs/_partners/message_personalization/location/bluedot.md
@@ -19,7 +19,7 @@ The Braze and Bluedot integration allows you to use Bluedot geofence location se
 | Requirement | Description |
 |---|---|
 | Bluedot Account | A Bluedot account is required to take advantage of this integration. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_personalization/location/foursquare.md b/_docs/_partners/message_personalization/location/foursquare.md
index 94a347c51a3..19e4718ef38 100644
--- a/_docs/_partners/message_personalization/location/foursquare.md
+++ b/_docs/_partners/message_personalization/location/foursquare.md
@@ -21,7 +21,7 @@ search_tag: Partner
 | Foursquare account | A Foursquare account is required to take advantage of this partnership. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | Braze workspace and App IDs | The Braze workspace and App IDs can be found in the [developer console]({{site.baseurl}}/api/api_key/). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/location/gimbal.md b/_docs/_partners/message_personalization/location/gimbal.md
index 4a98e85e715..6642cb40634 100644
--- a/_docs/_partners/message_personalization/location/gimbal.md
+++ b/_docs/_partners/message_personalization/location/gimbal.md
@@ -13,10 +13,15 @@ search_tag: Partner
 > [Gimbal](https://gimbal.com/) enables you to perfect your marketing relevance using location data. Their location SDK paired with geofencing software and beacons power relevant, personalized, proximity-aware mobile experiences.
 
 Combine your beacon or geofence support with Braze's targeting and messaging features to learn more about your user's physical actions and message them accordingly. This partnership integration opens up an array of use cases for:
+
 - **Marketing:** Send contextually relevant messaging and build experiential consumer journeys.
 - **Competitive Analysis:** Set up triggers around competitive locations to understand consumer trends and patterns.
 - **Audience Insights:** Understand your users' visitation behaviors and further segment based on those learnings.
 
+{% alert note %}
+This integration works the same for Gimbal beacons and Gimbal geofence solutions.
+{% endalert %}
+
 ## Prerequisites
 
 | Requirement| Description|
@@ -24,7 +29,7 @@ Combine your beacon or geofence support with Braze's targeting and messaging fea
 | [Gimbal manager account][1] | A Gimbal manager account is required to take advantage of this partnership. |
 |[Gimbal Location SDK](https://docs.gimbal.com/index.html) | The Gimbal Location SDK powers macro and micro location-based mobile experiences using proximity beacons and geofences that allow you to communicate more effectively with your app users. You must have the SDK implemented, and geofences (or beacons) set up. |
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## SDK integration
 
diff --git a/_docs/_partners/message_personalization/location/loplat.md b/_docs/_partners/message_personalization/location/loplat.md
index b814744fee5..2703b739ea1 100644
--- a/_docs/_partners/message_personalization/location/loplat.md
+++ b/_docs/_partners/message_personalization/location/loplat.md
@@ -21,7 +21,7 @@ The Braze and loplat integration allows you to use loplat's location services (s
 | loplat X account | A loplat X account is required to take advantage of this integration.<br><br>Email [support@loplat.com][3] to request a loplat X account. |
 | loplat SDK | loplat SDK recognizes users' store visits, processes location events, and distinguishes whether users are staying at a place or moving. You can use loplat SDK to analyze your store's footfall, send push messages when users enter your store, etc.<br><br>Note that the SDK is only available for Android and iOS. |
 | Braze REST API key | A Braze REST API key with the following permissions:<br>- `users.track`<br>- `campaigns.trigger.send`<br>- `campaigns.list`<br>- `canvas.trigger.send`<br>- `canvas.list`<br><br>This can be created in the Braze dashboard from **Settings** > **API Keys**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_partners/message_personalization/location/radar.md b/_docs/_partners/message_personalization/location/radar.md
index ba7d93fcb97..6c28929844b 100644
--- a/_docs/_partners/message_personalization/location/radar.md
+++ b/_docs/_partners/message_personalization/location/radar.md
@@ -24,7 +24,7 @@ Additionally, Radar Geo APIs can be leveraged to enrich or personalize your mark
 | Braze REST API key | A Braze REST API key with `users.track` permissions. <br><br> This can be created in the Braze dashboard from **Settings** > **API Keys**. |
 | App identifier | Your [app identifier]({{site.baseurl}}/api/identifier_types/?tab=app%20ids) can be found can be found within the Braze dashboard from **Settings** > **API Keys**. |
 | iOS API key<br>Android API key | These API keys can be found within the Braze dashboard from **Settings** > **App Settings**. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_partners/message_personalization/location/tangerine.md b/_docs/_partners/message_personalization/location/tangerine.md
index 7af20206901..47111953697 100644
--- a/_docs/_partners/message_personalization/location/tangerine.md
+++ b/_docs/_partners/message_personalization/location/tangerine.md
@@ -21,7 +21,7 @@ The Braze and Tangerine integration allows you to integrate raw campaign and imp
 | Store360 account | A Store360 account is required to take advantage of this partnership. |
 | Braze account ID | Your Braze app group ID. |
 | Matching user IDs | Your customer data in Store360 and Braze must have matching user IDs across the two platforms. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Use cases
 
diff --git a/_docs/_user_guide/administrative/access_braze/accessing_your_account.md b/_docs/_user_guide/administrative/access_braze/accessing_your_account.md
index 3637be0e9ea..c547eb809fd 100644
--- a/_docs/_user_guide/administrative/access_braze/accessing_your_account.md
+++ b/_docs/_user_guide/administrative/access_braze/accessing_your_account.md
@@ -22,7 +22,7 @@ Now that you've established where you need to log in, let's talk about how to lo
 You can either log in from the [Braze.com](https://www.braze.com) home site, or just use your dashboard URL that corresponds to your specific [Braze instance]({{site.baseurl}}/user_guide/administrative/access_braze/braze_instances/). For your convenience, Braze has several single sign on option such as:
 
 * [SAML SSO]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/)
-* [Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/)
+* [Microsoft Entra SSO]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/entra/)
 * [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/)
 * [OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/)
 
diff --git a/_docs/_user_guide/administrative/access_braze/global_search.md b/_docs/_user_guide/administrative/access_braze/global_search.md
index 4af59e0a584..ff02dda7c2d 100644
--- a/_docs/_user_guide/administrative/access_braze/global_search.md
+++ b/_docs/_user_guide/administrative/access_braze/global_search.md
@@ -56,7 +56,7 @@ table td {
 | Move between search results | <kbd>⬆</kbd> / <kbd>⬇</kbd>  |
 | Select a search result      | <kbd>Enter</kbd>    |
 | Close the search menu       | <kbd>Esc</kbd>  |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Content type and status tags
 
diff --git a/_docs/_user_guide/administrative/access_braze/navigation.md b/_docs/_user_guide/administrative/access_braze/navigation.md
index d61ca33ded5..bac83c744eb 100644
--- a/_docs/_user_guide/administrative/access_braze/navigation.md
+++ b/_docs/_user_guide/administrative/access_braze/navigation.md
@@ -192,7 +192,7 @@ The following table lists where each page is located in the new navigation. Some
 | User Import                   | Import Users                | **Audience** > **Import Users**                                  |
 | User Search                   | Search Users                | **Audience** > **Search Users**                                  |
 | Webhook Templates             | N/A                         | **Templates** > **Webhook Templates**                            |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
diff --git a/_docs/_user_guide/administrative/access_braze/portal.md b/_docs/_user_guide/administrative/access_braze/portal.md
index af68b17f765..29cb9145b3d 100644
--- a/_docs/_user_guide/administrative/access_braze/portal.md
+++ b/_docs/_user_guide/administrative/access_braze/portal.md
@@ -25,7 +25,7 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), you can fi
 | Planned Features | Features that we've committed to building and will begin development within the quarter. <br>There is no confirmed deadline as to when these features will be released. |
 | Under Consideration | Features we're considering building that our product team would like your feedback on. <br>These are ideas and no guarantee that we will build this feature. |
 | Submit Ideas | There are 10 product categories in which you can vote for general improvements or comment with a specific feature request or idea. <br>Our product team will receive and read your requests but an idea submission does not guarantee it will be built. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## How you can join the conversation
 
@@ -35,7 +35,7 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), you can fi
 | Comment on a feature | After you've ranked a feature, you can leave a comment with your feedback. |
 | Answer a Product Manager's question | Look for the "How Customers Can Help" on a feature card to answer questions from our product team. |
 | Submit an idea | Go to the portal's **Submit Ideas** page and select from one of ten cards to rank its importance. Include your idea or request in the comments! <br><br>Once submitted, your idea will be reviewed by a member of our product team. We cannot provide updates on the status of a request. Occasionally check back to see if your idea has been added to the "Under Consideration" or "Planned Features" sections. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Product feedback at Braze
 
diff --git a/_docs/_user_guide/administrative/access_braze/sdk_endpoints.md b/_docs/_user_guide/administrative/access_braze/sdk_endpoints.md
index 683833725f0..41779ca0c41 100644
--- a/_docs/_user_guide/administrative/access_braze/sdk_endpoints.md
+++ b/_docs/_user_guide/administrative/access_braze/sdk_endpoints.md
@@ -27,7 +27,7 @@ Logging in at [dashboard.braze.com](https://dashboard.braze.com) will automatica
 |US-08| `https://dashboard-08.braze.com` | `https://rest.iad-08.braze.com` | `sdk.iad-08.braze.com` |
 |EU-01| `https://dashboard-01.braze.eu` | `https://rest.fra-01.braze.eu` | `sdk.fra-01.braze.eu` |
 |EU-02| `https://dashboard-02.braze.eu` | `https://rest.fra-02.braze.eu` | `sdk.fra-02.braze.eu` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert important %}
 When integrating your SDK, use the SDK endpoint. When making calls to our REST API, use the REST endpoint.
diff --git a/_docs/_user_guide/administrative/access_braze/single_sign_on/entra.md b/_docs/_user_guide/administrative/access_braze/single_sign_on/entra.md
index 245550a9faa..477b6ddcccd 100644
--- a/_docs/_user_guide/administrative/access_braze/single_sign_on/entra.md
+++ b/_docs/_user_guide/administrative/access_braze/single_sign_on/entra.md
@@ -21,7 +21,7 @@ Upon setup, you will be asked to provide a sign-on URL and an Assertion Consumer
 | Assertion Consumer Service (ACS) URL | `https://<SUBDOMAIN>.braze.com/auth/saml/callback` <br> For some identity providers, this can also be referred to as the Reply URL, Audience URL, or Audience URI. |
 | Entity ID | `braze_dashboard`|
 | RelayState API key | To enable identity provider login, go to **Settings** > **API Keys** and create an API key with `sso.saml.login` permissions. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can find your API keys under **Settings** at **Developer Console** > **API Settings**.
@@ -109,7 +109,7 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), select you
 | `SAML Name` | This will appear as the button text on the login screen. This is typically your identity provider's name, like "Microsoft Entra." |
 | `Target URL` | This is the login URL provided by Microsoft Entra.|
 | `Certificate` | The `x.509` PEM encoded certificate is provided by your identity provider. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 If you want your Braze account users to only sign in with SAML SSO, you can [restrict single sign-on authentication]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/#restriction) from the **Company Settings** page.
diff --git a/_docs/_user_guide/administrative/access_braze/single_sign_on/okta.md b/_docs/_user_guide/administrative/access_braze/single_sign_on/okta.md
index 3c5f9a713f7..573774bbaa1 100644
--- a/_docs/_user_guide/administrative/access_braze/single_sign_on/okta.md
+++ b/_docs/_user_guide/administrative/access_braze/single_sign_on/okta.md
@@ -22,7 +22,7 @@ description: "This article will walk you through how to configure Braze to use O
 | Okta admin privileges | Make sure you have admin privileges before setting up Okta. |
 | Braze admin privileges | Make sure you have admin privileges before setting up Okta. |
 | RelayState API key | To enable IdP login, go to **Settings** > **API Keys** and create an API key with `sso.saml.login` permissions. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can find your API keys under **Settings** at **Developer Console** > **API Settings**.
@@ -51,7 +51,7 @@ From your Okta Admin dashboard, you will be provided a target URL (login URL) an
 | `SAML Name` | This will appear as the button text on the login screen. This is typically your identity provider's name, For example, "Okta". |
 | `Target URL` | This is the login URL provided by Okta Admin dashboard. Find it by going to **Applications** > your application > **General** tab > **App Embed Link** > **Embed Link**. |
 | `Certificate` | The `x.509` PEM encoded certificate is provided by your identity provider. You must copy and paste it into this field. Retrieve it in Okta by going to **SAML Signing Certificates** and selecting **Actions** > **Download certificate**. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Select **Save Changes** at the bottom of the page when completed.
 
diff --git a/_docs/_user_guide/administrative/access_braze/single_sign_on/onelogin.md b/_docs/_user_guide/administrative/access_braze/single_sign_on/onelogin.md
index 360f3d5a639..cb1363e3b5d 100644
--- a/_docs/_user_guide/administrative/access_braze/single_sign_on/onelogin.md
+++ b/_docs/_user_guide/administrative/access_braze/single_sign_on/onelogin.md
@@ -19,7 +19,7 @@ Upon setup, you will be asked to provide a sign-on URL and an Assertion Consumer
 |---|---|
 | Braze Domain | You will need your Braze domain to set up Braze within OneLogin. If your instance is `US-01`, you will need to input your dashboard URL into the OneLogin dashboard. <br><br> For example, if your dashboard URL is `https://dashboard-01.braze.com`, you need to input `dashboard-01.braze.com`.  |
 | RelayState API key | To enable IdP login, go to **Settings** > **API Keys** and create an API key with `sso.saml.login` permissions. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can find your API keys under **Settings** at **Developer Console** > **API Settings**.
@@ -53,7 +53,7 @@ On this page, input the following:
 | `SAML Name` | This will appear as the button text on the login screen. This is typically your identity provider's name, like "OneLogin". |
 | `Target URL` | This is the `SAML 2.0 Endpoint (HTTP)` URL provided by OneLogin.|
 | `Certificate` | The `x.509` PEM encoded certificate is provided by your OneLogin. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![Opening Security Settings in Braze and adding SAML SSO details.]({% image_buster /assets/img/samlsso.gif %})
 
diff --git a/_docs/_user_guide/administrative/access_braze/single_sign_on/set_up.md b/_docs/_user_guide/administrative/access_braze/single_sign_on/set_up.md
index 44d09d51a84..c349971e42a 100644
--- a/_docs/_user_guide/administrative/access_braze/single_sign_on/set_up.md
+++ b/_docs/_user_guide/administrative/access_braze/single_sign_on/set_up.md
@@ -20,7 +20,7 @@ Upon setup, you will be asked to provide a sign-on URL and an Assertion Consumer
 | Assertion Consumer Service (ACS) URL | `https://<SUBDOMAIN>.braze.com/auth/saml/callback` <br><br> For European Union domains, the ASC URL is `https://<SUBDOMAIN>.braze.eu/auth/saml/callback`. <br><br> For some IdPs, this can also be referred to as the Reply URL, Sign-On URL, Audience URL, or Audience URI. |
 | Entity ID | `braze_dashboard` |
 | RelayState API key | Go to **Settings** > **API Keys** and create an API key with `sso.saml.login` permissions, and then input the generated API key as the `RelayState` parameter within your IdP. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can find your API keys under **Settings** at **Developer Console** > **API Settings**.
@@ -63,7 +63,7 @@ On the same page, input the following:
 | `SAML Name` | This will appear as the button text on the login screen.<br>This is typically your identity provider's name, like "Okta." |
 | `Target URL` | This is provided after setting up Braze within your IdP.<br> Some IdPs reference this as the SSO URL or SAML 2.0 Endpoint. |
 | `Certificate` | The `x.509` certificate that is provided by your identity provider.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Make sure that your `x.509` certificate follows this format when adding it to the dashboard:
 
diff --git a/_docs/_user_guide/administrative/app_settings/company_settings/notification_preferences.md b/_docs/_user_guide/administrative/app_settings/company_settings/notification_preferences.md
index 9f3fd700822..606bcba1537 100644
--- a/_docs/_user_guide/administrative/app_settings/company_settings/notification_preferences.md
+++ b/_docs/_user_guide/administrative/app_settings/company_settings/notification_preferences.md
@@ -38,7 +38,7 @@ The following table lists available notifications:
 | Scheduled Campaign Limit Met | Notifies recipients when the limit for a recurring scheduled campaign has been reached. | Email, Webhook |
 | Scheduled Campaign Finished Sending | Notifies recipients when a scheduled campaign has finished sending. | Email, Webhook |
 | Weekly Analytics Report | Sends a summary of the past week's workspace activity to recipients every Monday. Recipients receive a summary for each workspace that they belong to. | Email |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Weekly analytics reporting
 
diff --git a/_docs/_user_guide/administrative/app_settings/company_settings/security_settings.md b/_docs/_user_guide/administrative/app_settings/company_settings/security_settings.md
index e0bfe110479..a951989f029 100644
--- a/_docs/_user_guide/administrative/app_settings/company_settings/security_settings.md
+++ b/_docs/_user_guide/administrative/app_settings/company_settings/security_settings.md
@@ -169,7 +169,7 @@ The following fields can be hidden from Braze users who don't have **View PII**
 | Standard attributes | Custom attributes |
 | ------------------- | ----------------- |
 | {::nomarkdown} <ul> <li>Email address </li> <li> Phone number </li> <li> First name </li> <li> Last name </li> <li> Gender </li> <li> Birthday </li> <li> Device IDs </li> <li> Most recent location </li> </ul> {:/} | {::nomarkdown} <ul> <li> All custom attributes<ul><li>Individual custom attributes can be marked as PII if you don't need to hide all attributes.</li></ul></li> </ul> {:/} |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Limited areas
 
@@ -182,7 +182,7 @@ The following assumes that all fields are set as PII and the users mentioned are
 | {::nomarkdown} <ul> <li> Segments </li> <li> Campaigns </li> <li> Canvas </li> </ul> {:/} | In the **User Data** dropdown: {::nomarkdown} <ul> <li> The user won't have the <b>CSV Export Email Address</b> option. </li> <li> The user won't be provided the preceding standard and customer attributes in the CSV file when selecting <b>CSV Export User Data</b>. </li> </ul> {:/} | |
 | Internal test group | The user won't have access to the preceding standard attributes of any user added to the internal test group. | |
 | Message activity log | The user won't have access to the preceding standard attributes for any users identified in the message activity log. | |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert note %}
 When previewing a message, the **View PII** permission isn't applied, so users can see the preceding standard attributes if they were referenced in the message through Liquid.
diff --git a/_docs/_user_guide/administrative/app_settings/email_settings.md b/_docs/_user_guide/administrative/app_settings/email_settings.md
index 763db8a14b7..269682b2eb9 100644
--- a/_docs/_user_guide/administrative/app_settings/email_settings.md
+++ b/_docs/_user_guide/administrative/app_settings/email_settings.md
@@ -118,7 +118,7 @@ The following table summarizes mailbox provider support for “mailto:” header
 | Apple Mail | Supported | Not supported | Not supported |
 | Outlook.com | Supported | Not supported | Not supported |
 | Yahoo! Mail | Supported* | Not supported | Supported |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 _*Yahoo and Gmail will eventually deprecate the "mailto:" header and will only support one-click._
 
@@ -154,7 +154,7 @@ Braze supports the following versions of the list-unsubscribe header:
 | One-click (RFC 8058) | Offers a straightforward way for recipients to opt-out from emails with a single click. This is a requirement from Yahoo and Gmail for bulk senders. |
 | List-unsubscribe URL or HTTPS | Provides recipients with a link that directs the recipient to a web page where they can unsubscribe. |
 | Mailto | Specifies an email address as the destination for the unsubscribe request message to be sent to from the recipient to the brand. <br><br> _To process mailto list-unsubscribe requests, such unsubscribe requests need to include the email address as stored in Braze for the End User who is unsubscribing. This may be provided by the "from-address" of the email from where the End User is unsubscribing, the encoded subject or the encoded body from the email received by the End User that they are unsubscribing from. In very limited cases, some inbox providers don't adhere to the [RFC 2368](https://datatracker.ietf.org/doc/html/rfc2368) protocol resulting in the email address not being properly passed. This can lead to an unsubscribe request not being able to be processed in Braze._ |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 When Braze receives a list-unsubscribe request from a user via any of the above methods, this user’s global email subscription state is set to unsubscribed. If there isn’t a match, Braze will not process this request.
 
diff --git a/_docs/_user_guide/administrative/app_settings/internal_groups_tab.md b/_docs/_user_guide/administrative/app_settings/internal_groups_tab.md
index a7dc1dcfb7b..d362ff22325 100644
--- a/_docs/_user_guide/administrative/app_settings/internal_groups_tab.md
+++ b/_docs/_user_guide/administrative/app_settings/internal_groups_tab.md
@@ -39,7 +39,7 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), you can fi
 | User Event Group| Used for verifying events or logs from your test device.|
 | Content Test Group | A similar concept to Test Lists. Can be used across push, email, and in-app messages to send a rendered copy of the message.|
 | Seed Group | Automatically sends a copy of the email to everyone the Seed Group upon send.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Adding test users
 
@@ -52,7 +52,7 @@ After you create your Internal Group, you can add test users as members of that
 | Identified Users |Search for the user by their external user ID or email address.|
 |Anonymous Users| Search by IP address. Then, provide a name for each test user that is added. This is the name that all event logs will be associated with on the [Event User Log]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/) page.|
 |Bulk Add Users|Copy and paste a list of email addresses or external IDs into the provided section. You can only add users that are already known in the dashboard. For more information, refer to [User Import]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/).|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Content Test Groups
 
diff --git a/_docs/_user_guide/administrative/app_settings/manage_your_braze_users.md b/_docs/_user_guide/administrative/app_settings/manage_your_braze_users.md
index 4d445270dea..a6d769b334f 100644
--- a/_docs/_user_guide/administrative/app_settings/manage_your_braze_users.md
+++ b/_docs/_user_guide/administrative/app_settings/manage_your_braze_users.md
@@ -21,3 +21,21 @@ guide_featured_list:
   link: /docs/user_guide/administrative/app_settings/manage_your_braze_users/teams/
   image: /assets/img/braze_icons/users-01.svg
 ---
+
+## What are the differences among teams, permission sets, and roles? 
+
+You can use team, permission sets, and user roles to manage dashboard user access and responsibilities within Braze. Each feature encompasses a different collection of permissions and access-controls.
+
+### Key differences
+
+At a high level, each feature has a different scope:
+- Permission sets control what dashboard users can do across all workspaces.
+- Roles control what dashboard users can do in specific workspaces.
+- Teams control the audiences that dashboard users can message.
+
+| Feature | What you can do |
+| - | - |
+| [Permission sets]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#creating-a-permission-set) | Bundle permissions related to specific subject areas or actions (such as for “Developers” and “Marketers”), then apply them to dashboard users who need the same permissions across different workspaces. |
+| [Roles]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#creating-a-role) | Bundle individual custom permissions and workspace-access controls into predefined roles (such as “Marketer - Fashion Brands” and “Marketer - Skincare Brands”), then assign a role to dashboard users to directly grant them the associated workspace access and permissions. |
+| [Teams]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/teams/) | Limit dashboard user access to resources based on the audience (such as customer base location, language, and custom attributes). |
+{: .reset-td-br-1 .reset-td-br-2 }
\ No newline at end of file
diff --git a/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/adding_users_to_your_dashboard.md b/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/adding_users_to_your_dashboard.md
index 3d2c2e85558..21a1862afbc 100644
--- a/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/adding_users_to_your_dashboard.md
+++ b/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/adding_users_to_your_dashboard.md
@@ -23,7 +23,7 @@ To add a new user:
 
 1. Go to **Settings** > **Company Users**.
 2. Click **+ Add New User**.
-3. Enter their information as prompted, including their email, department, and [user role]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#creating-a-role.
+3. Enter their information as prompted, including their email, department, and [user role]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#creating-a-role).
 
 {% alert tip %}
 The department listed in a user's profile determines what types of communications they receive from Braze. This is so everyone only receives the communications and alerts that are relevant to how they use Braze.
@@ -47,7 +47,7 @@ If your team uses Gmail and you're experiencing issues adding an email address,
 
 Suspending a user puts their account into an inactive state, where the user can no longer log in, but the data associated with their account is preserved. Only administrators can suspend or un-suspend Braze users.
 
-To suspend a user, go to **Settings** > **Company Users**, find their username and click <i class="fa-solid fa-user-lock"></i> **Suspend**.
+To suspend a user, go to **Settings** > **Company Users**, find their username and select <i class="fa-solid fa-user-lock"></i> **Suspend**.
 
 ![Suspend a user][4]
 
@@ -79,4 +79,4 @@ After a user is deleted, Braze does not keep any of the following data:
 [5]: {% image_buster /assets/img_archive/suspend_user2.png %}
 
 [27]: {% image_buster /assets/img/add-user.gif %} "Add a New User Process"
-[34]: {% image_buster /assets/img_archive/delete_user_new.png %}
\ No newline at end of file
+[34]: {% image_buster /assets/img_archive/delete_user_new.png %}
diff --git a/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/teams.md b/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/teams.md
index f4b261d58dc..e2f30b2c7e9 100644
--- a/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/teams.md
+++ b/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/teams.md
@@ -131,23 +131,9 @@ Select one or many teams to archive. If the team is not associated with any obje
 
 Braze admins can unarchive a team by selecting the archived team and selecting **Unarchive**.
 
-## How do teams differ from permission sets and roles? 
+## How do teams differ from permission sets and roles?
 
-You can use team, permission sets, and user roles to manage dashboard user access and responsibilities within Braze. Each feature encompasses a different collection of permissions and access-controls.
-
-### Key differences
-
-At a high level, each feature has a different scope:
-- Permission sets control what dashboard users can do across all workspaces.
-- Roles control what dashboard users can do in specific workspaces.
-- Teams control the audiences that dashboard users can message.
-
-| Feature | What you can do |
-| - | - |
-| [Permission sets]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#permission-sets/) | Bundle permissions related to specific subject areas or actions (such as for “Developers” and “Marketers”), then apply them to dashboard users who need the same permissions across different workspaces. |
-| [Roles]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#roles/) | Bundle individual custom permissions and workspace-access controls into predefined roles (such as “Marketer - Fashion Brands” and “Marketer - Skincare Brands”), then assign a role to dashboard users to directly grant them the associated workspace access and permissions. |
-| Teams | Limit dashboard user access to resources based on the audience (such as customer base location, language, and custom attributes). |
-{: .reset-td-br-1 .reset-td-br-2 }
+Refer to [Company users]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/) for a breakdown of the differences among teams, permission sets, and roles.
 
 [2]: {% image_buster /assets/img/teams.png %}
 [3]: {% image_buster /assets/img/teams1.png %}
diff --git a/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/user_permissions.md b/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/user_permissions.md
index bf4c25578df..e6ea9340aa7 100644
--- a/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/user_permissions.md
+++ b/_docs/_user_guide/administrative/app_settings/manage_your_braze_users/user_permissions.md
@@ -23,7 +23,7 @@ Use permission sets to bundle permissions related to specific subject areas or a
 |Developers|“Access Dev Console”|
 |Marketers|“Access Campaigns, Canvases, Cards, Feature Flags, Segments, Media Library, and Preference Centers” <br> “Manage Media Library Assets”|
 |User Management|“Manage Dashboard Users” <br> “Manage Teams”|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% endtabs %}
 
@@ -38,10 +38,14 @@ Roles allow for more structure by bundling together your individual custom permi
 | Marketer - Fashion Brands | {::nomarkdown}[DEV] Fashion Brand, [QA] Fashion Brand, [PROD] Fashion Brand {:/} | “Access Campaigns, Canvases, Cards, Feature Flags, Segments, Media Library, and Preference Center"<br>“Manage Media Library Assets” |
 | Marketer - Skincare Brands | {::nomarkdown}[DEV] Skincare Brand, [QA] Skincare Brand, [PROD] Skincare Brand {:/} | “Access Campaigns, Canvases, Cards, Feature Flags, Segments, Media Library, and Preference Centers” <br>“Manage Media Library Assets” |
 | User Management - All Brands | {::nomarkdown}[DEV] Fashion Brand, [QA] Fashion Brand, [PROD] Fashion Brand, [DEV] Skincare Brand, [QA] Skincare Brand, [PROD] Skincare Brand {:/} | “Manage Dashboard Users”<br>“Manage Teams” |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 {% endtab %}
 {% endtabs %}
 
+### How do permission sets and roles differ from teams?
+
+Refer to [Company users]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/) for a breakdown of the differences among teams, permission sets, and roles.
+
 ## Editing a user's permissions
 
 To edit a user's current [admin](#admin), [company](#company), or [workspace](#workspace) permissions, go to **Settings** > **Company Users**, then select their name.
@@ -74,7 +78,7 @@ To manage the following company-level permissions for a user, check or uncheck t
 |----------|-----------|
 |Manage company settings|Allows users to modify any company setting.|
 |Create and delete workspaces|Allows users to create and delete workspaces.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Workspace
 
@@ -150,4 +154,7 @@ As of April 2024, to create or update promotion code lists, Braze users need the
 |Workspace|View Usage Data|Allows users to view app usage, including the channel performance dashboards.|
 |Workspace|Merge Duplicate Users|Allows users to merge duplicate user profiles.|
 |Workspace|Preview Duplicate Users|Allows users to preview which user profiles are duplicated.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+|Workspace|Create and Edit Canvas Templates|Allows users to create and edit Canvas templates.|
+|Workspace|View Canvas Templates|Allows users to view Canvas templates.|
+|Workspace|Archive Canvas Templates|Allows users to archive Canvas templates.|
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
diff --git a/_docs/_user_guide/administrative/app_settings/message_activity_log_tab.md b/_docs/_user_guide/administrative/app_settings/message_activity_log_tab.md
index b96fac7fc05..3bd3283838c 100644
--- a/_docs/_user_guide/administrative/app_settings/message_activity_log_tab.md
+++ b/_docs/_user_guide/administrative/app_settings/message_activity_log_tab.md
@@ -58,7 +58,7 @@ The following messages listed are for example purposes and may not exactly match
 | Hard Bounce | The email account that you tried to reach does not exist. Try double-checking the recipient's email address for typos or unnecessary spaces. | Your message never reached this person's inbox because there was no inbox to reach. If you want to dig further in, messages like this can sometimes have links in the **View Details** column that will allow you to view the intended recipient's profile.|
 | Block | Spam message is rejected because of anti-spam policy. | Your message got categorized as spam. This mail error is logged for a user if we’ve received an event from the ESP indicating the email was dropped. It might just might be for that intended recipient, but if you're seeing this message a lot, you might want to re-evaluate your send habits or the content of your message. Also, think back—did you [warm up your IP][8]? If not, reach out to Braze for advice on getting this going.|
 | Aborted Message Error | empty-cart_web | If you have an app with a cart or you create a send with an abort message in the Liquid, you can customize what message is returned to you if the send is aborted. In this case, the message returned is empty-cart_web.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Why isn't my message listed here?
 
diff --git a/_docs/_user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines.md b/_docs/_user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines.md
index 52a5670316e..ff4a37c17dd 100644
--- a/_docs/_user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines.md
+++ b/_docs/_user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines.md
@@ -35,7 +35,7 @@ For **Brand personality**, think about what makes your brand unique. Include tra
 | Differentiation          | Unique qualities that set your brand apart from competitors.                         | We stand out by offering personalized customer service that goes above and beyond. |
 | Brand voice              | The tone and style of communication your brand uses.                                 | Our voice is casual yet informative, ensuring clarity without being too formal. |
 | Brand archetype          | The archetype that represents your brand’s persona (The Hero, The Creator, and so on).    | We embody the ‘Explorer’ archetype, always seeking new challenges and adventures. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Step 3: Define language that should be avoided (optional)
 
diff --git a/_docs/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics.md b/_docs/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics.md
index 1033d33bf67..72f31e63c99 100644
--- a/_docs/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics.md
+++ b/_docs/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics.md
@@ -48,7 +48,7 @@ Here's what we recommend for various ranges of _Prediction Quality_:
 | 40 - 60 | Good. This model will produce accurate predictions, but trying different audience settings may achieve even better results. |
 | 20 - 40| Fair. This model can provide accuracy and value, but consider trying different audience definitions to see if they increase performance. |
 | 0 - 20 | Poor. We recommend you change your audience definitions and try again. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 The prediction will be trained again every two weeks and updated alongside the prediction quality metric to keep your predictions updated on the most recent user behavior patterns. The last time this retraining occurred will be displayed on the predictions list page as well as on your prediction's analytics page.
 
diff --git a/_docs/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md b/_docs/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md
index d87ae1b1f41..0af3e2d0a9b 100644
--- a/_docs/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md
+++ b/_docs/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md
@@ -21,7 +21,7 @@ Here's what we recommend for various ranges of _Prediction Quality_:
 | 40 - 60 | Good. This model will produce accurate predictions, but trying different audience settings may achieve even better results. |
 | 20 - 40| Fair. This model can provide accuracy and value, but consider trying different audience definitions to see if they increase performance. |
 | 0 - 20 | Poor. We recommend you change your audience definitions and try again. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 The prediction will be trained again every two weeks and updated alongside the _Prediction Quality_ metric to keep your predictions updated on the most recent user behavior patterns. Additionally, each time this occurs, the last two weeks of predictions will be tested against actual user outcomes. The _Prediction Quality_ will then be calculated based on these real outcomes (rather than estimates). This is an automatic backtest (that is, testing a predictive model on historical data) to ensure the prediction is accurate in real-world scenarios. The last time this retraining and backtesting occurred will be displayed on the **Predictions** page and an individual prediction's analytics page. Even a preview prediction will perform this backtest once after its creation. This way, you can be sure of the accuracy of your customized prediction even with the free version of the feature.
 
diff --git a/_docs/_user_guide/brazeai/predictive_suite/predictive_events.md b/_docs/_user_guide/brazeai/predictive_suite/predictive_events.md
index fdbb9a6d07a..aeed79f0629 100644
--- a/_docs/_user_guide/brazeai/predictive_suite/predictive_events.md
+++ b/_docs/_user_guide/brazeai/predictive_suite/predictive_events.md
@@ -29,7 +29,7 @@ guide_featured_list:
 
 > Predictive Events give marketers a powerful tool for identifying and messaging users based on their likelihood to perform an event. When you create an event prediction, Braze trains a machine learning model using [gradient boosted decision trees](https://en.wikipedia.org/wiki/Gradient_boosting) to learn from previous activity and predict future activity.
 
-Once a prediction is built, users are assigned a [likelihood score]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_purchases/prediction_analytics/#purchase_score) between 0 and 100 denoting how likely they are to perform your selected event. The higher the score, the more likely a user is to perform that event. Users are also sorted by low, medium, and high likelihood categories.
+Once a prediction is built, users are assigned a [likelihood score]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics/#purchase_score) between 0 and 100 denoting how likely they are to perform your selected event. The higher the score, the more likely a user is to perform that event. Users are also sorted by low, medium, and high likelihood categories.
 
 The real value of Predictive Events lies using prediction results to create a segment or campaign. Marketers can build targeted campaigns directly on the **Prediction** page for immediate revenue-boosting results or save a segment for a future campaign or Canvas. Not sure who to target first? Read our [strategic considerations]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_purchases/messaging_users/#strategy) for messaging users based on their likelihood score.
 
@@ -43,7 +43,7 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), you can fi
 
 Prior to purchasing this feature, it is available in preview mode. This will allow you to see a demo prediction with synthetic data as well as create one preview prediction model at a time. This prediction will be created based on your actual user data, but it will not allow you to target users for messaging according to their likelihood score. It will also not update regularly after creation.
 
-With the Preview, you can also edit and rebuild this one prediction or archive it and create others to test the expected [prediction quality]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_purchases/prediction_analytics/#prediction_quality) of [different audiences]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_purchases/creating_a_purchase_prediction/#audience) and become familiar with the analytics.
+With the Preview, you can also edit and rebuild this one prediction or archive it and create others to test the expected [prediction quality]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics/#prediction_quality) of [different audiences]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_events/creating_an_event_prediction/#audience) and become familiar with the analytics.
 
 <br><br>
 
diff --git a/_docs/_user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics.md b/_docs/_user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics.md
index 8d4cb38f57c..41255549a96 100644
--- a/_docs/_user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics.md
+++ b/_docs/_user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics.md
@@ -69,7 +69,7 @@ Here's what we recommend for various ranges of _Prediction Quality_:
 | 40 - 60 | Good. This model will produce accurate predictions, but trying different audience settings may achieve even better results. |
 | 20 - 40| Fair. This model can provide accuracy and value, but consider trying different audience definitions to see if they increase performance. |
 | 0 - 20 | Poor. We recommend you change your audience definitions and try again. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 The prediction will be trained again every two weeks and updated alongside the prediction quality metric to keep your prediction updated on the most recent user behavior patterns. The last time this retraining occurred will be displayed on the predictions list page as well as on your prediction's analytics page. 
 
diff --git a/_docs/_user_guide/brazeai/recommendations/ai_item_recommendations.md b/_docs/_user_guide/brazeai/recommendations/ai_item_recommendations.md
index 103bfc682df..5d0ebc4178f 100644
--- a/_docs/_user_guide/brazeai/recommendations/ai_item_recommendations.md
+++ b/_docs/_user_guide/brazeai/recommendations/ai_item_recommendations.md
@@ -107,7 +107,7 @@ There are some requirements for selecting your property:
 - **If you selected Purchase Object:** Must be the `product_id` or a field of your interaction event's `properties`.
 - **If you selected Custom Event:** Must be a field of your custom event's `properties`.
 - Nested fields must be typed into the **Property Name** dropdown in dot notation with the format of `event_property.nested_property`. For example, if selecting the nested property `district_name` within the event property `location`, you would enter `location.district_name`.
-- The field can be in an array (of multiple catalog items within a single event). It will automatically be flattened.
+- The field can be inside an array of products, or end with an array of IDs. In either case, each product ID will be treated as a separate, sequential event with the same timestamp.
 
 #### Example mappings
 
@@ -163,13 +163,13 @@ This event has `"product_sku": "ADI-BL-7"`, which matches the first item in the
 
 ```json
 {
-  "events" : [
+  "events": [
     {
-      "external_id" : "user1",
-      "app_id" : "your-app-id",
-      "name" : "added_to_cart",
-      "time" : "2024-07-16T19:20:30+01:00",
-      "properties" : {
+      "external_id": "user1",
+      "app_id": "your-app-id",
+      "name": "added_to_cart",
+      "time": "2024-07-16T19:20:30+01:00",
+      "properties": {
         "product_sku": "ADI-BL-7"
       }
     }
@@ -177,6 +177,53 @@ This event has `"product_sku": "ADI-BL-7"`, which matches the first item in the
 }
 ```
 
+##### Example custom event object with an array of products
+
+If your event properties contain multiple products in an array, each product ID will be treated as a separate, sequential event. This event can use the property `products.sku` to match the first and third items in the sample catalog.
+
+```json
+{
+  "events": [
+    {
+      "external_id": "user1",
+      "app_id": "your-app-id",
+      "name": "added_to_cart",
+      "time": "2024-07-16T19:20:30+01:00",
+      "properties": {
+        "transaction_id": "2ff3f9a9-8803-4c3a-91da-14adbf93dc99",
+        "products": [
+          { "sku": "ADI-BL-7" },
+          { "sku": "ADI-WH-9" }
+        ]
+      }
+    }
+  ]
+}
+```
+
+##### Example custom event object with a nested object containing a product ID array
+
+If your product IDs are values in an array instead of objects, you can use the same notation and each product ID will be treated as a separate, sequential event. This can flexibly be combined with nested objects in the following event by configuring the property as `purchase.product_skus` to match the first and third items in the sample catalog.
+
+```json
+{
+  "events": [
+    {
+      "external_id": "user1",
+      "app_id": "your-app-id",
+      "name": "added_to_cart",
+      "time": "2024-07-16T19:20:30+01:00",
+      "properties": {
+        "transaction_id": "13791e08-7c22-4f6c-8cc6-832c76af3743",
+        "purchase": {
+          "product_skus": ["ADI-BL-7", "ADI-WH-9"]
+        }
+      }
+    }
+  ]
+}
+```
+
 {% endtab %}
 {% tab Purchase object %}
 
@@ -264,7 +311,7 @@ These metrics are defined in the following table.
 | Precision           | The percentage of time the model correctly guessed the next item a user purchased. Precision is heavily dependent on your specific catalog size and mix, and should be used as a guide to understand how often the model is correct.<br><br>In past testing, we have seen models perform well with precision numbers ranging from 6-20%. This metric updates when the model next retrains.  |
 | Coverage            | What percentage of available items in the catalog are recommended to at least one user. You can expect to see higher item coverage with personalized item recommendations over most popular ones. |
 | Recommendation type | Percentage of users who will receive personalized or most recent recommendations versus the fallback of most popular items. The fallback is sent to users who don’t have enough data to generate a personalized or most recent recommendation. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 The next section shows a breakdown of items in the catalog, split into two possible columns:
 
@@ -298,9 +345,9 @@ The following table describes the differences between the free and pro version o
 | :---------------------- | ------------------------------------- | :--------------------------------------- |
 | User update frequency<sup>1</sup>   | Weekly                                | Daily                                    |
 | Model retraining frequency  | Monthly                               | Monthly                                   |
-| Maximum recommendations | 1 recommendation per type<sup>1</sup> | 100 recommendations per type<sup>2</sup> |
+| Maximum recommendation models | 1 model per type<sup>2</sup> | 100 models per type<sup>2</sup> |
 
-<sup>1. This is the frequency at which user-specific item recommendations are updated (all models except Most Popular items, which updates when the model retrains). For example, if a user purchases an item recommended based on AI item recommendations, their recommended items will be updated according to this frequency</sup>
+<sup>1. This is the frequency at which user-specific item recommendations are updated (all models except Most Popular items, which updates when the model retrains). For example, if a user purchases an item recommended based on AI item recommendations, their recommended items will be updated according to this frequency</sup><br>
 <sup>2. Available recommendation types are AI Personalized, Most recent, Most popular, and Trending.</sup>
 
 ## Frequently asked questions
diff --git a/_docs/_user_guide/brazeai/recommendations/rules_based_recommendations.md b/_docs/_user_guide/brazeai/recommendations/rules_based_recommendations.md
index ca9783f4b92..a0eb2d3243d 100644
--- a/_docs/_user_guide/brazeai/recommendations/rules_based_recommendations.md
+++ b/_docs/_user_guide/brazeai/recommendations/rules_based_recommendations.md
@@ -142,7 +142,7 @@ Let’s say you have a health food app and want to create a Content Card campaig
 |`YOUR-API-URL` | Replace with the actual URL of your API. |
 |`RECOMMENDED_ITEM_IDS` | Replace with the actual name of your custom attribute that contains the IDs of recommended items. This attribute is expected to be a string of IDs separated by semicolons. |
 |`ITEM_ID` | Replace with the actual name of the attribute in your API response that corresponds to the item ID. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 This is a basic example and you might need to modify it further based on your specific needs and data structure. For more detailed guidance, refer to the [Liquid documentation]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/) or consult with a developer.
@@ -274,7 +274,7 @@ When deciding which recommendation engine suits your available resources and use
 | Updates to data in the product feed | Not supported | Supported if the recommendations aren’t often updated | Supported if recommendations are updated up to hourly | Supported and recommendations are updated up to real-time |
 | Generate recommendations within Braze UI | Supported | Supported | Supported | Not supported if generated outside of Braze |
 | No hosting, managing, troubleshooting recommendations data | Supported | Supported | Supported | Not supported |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 [1]: {% image_buster /assets/img/recs/catalog_items.png %}
 [2]: {% image_buster /assets/img/recs/content_card_preview.png %}
diff --git a/_docs/_user_guide/data_and_analytics/analytics/conversions_dashboard.md b/_docs/_user_guide/data_and_analytics/analytics/conversions_dashboard.md
index 6184e5d9c29..0c7f3ad154a 100644
--- a/_docs/_user_guide/data_and_analytics/analytics/conversions_dashboard.md
+++ b/_docs/_user_guide/data_and_analytics/analytics/conversions_dashboard.md
@@ -103,7 +103,7 @@ To download the time series data, select <i class="fas fa-bars"></i> and then se
 | Upon Click | Total number of conversions that occurred message click | Calculated as (Unique Click Conversions) / (Unique Recipients) | {::nomarkdown}<ul><li>Upon email click</li><li>Upon Content Card click</li><li>Upon IAM click</li></ul>{:/} |
 | Upon Impression | Total number of conversions that occurred after an impression | Calculated as (Unique Impression Conversions) / (Unique Recipients) | {::nomarkdown}<ul><li>Upon IAM impression</li><li>Upon Content Card impression</li></ul>{:/} |
 | Upon Last-Touch | Conversions that give all credit to the last-touched or clicked message during the conversion window. | Calculated as (Number of Touches) / (Unique Recipients) | Last-touch attribution is automatically selected if multiple channels are added to the report.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Terms to know
 
diff --git a/_docs/_user_guide/data_and_analytics/analytics/deliverability_center.md b/_docs/_user_guide/data_and_analytics/analytics/deliverability_center.md
index fa6612ffd92..9b3f0db654b 100644
--- a/_docs/_user_guide/data_and_analytics/analytics/deliverability_center.md
+++ b/_docs/_user_guide/data_and_analytics/analytics/deliverability_center.md
@@ -66,7 +66,7 @@ To help understand the ratings for IP reputation, refer to this table:
 | Medium/Fair | Known to generate positive engagement but occasionally receives spam complaints. Most of the emails from this domain will be sent to the inbox, except when spam complaints increase. |
 | Low | Known to receive elevated rates of spam complaints regularly. Emails from this sender will likely be filtered to the spam folder. |
 | Bad | Has a history of receiving elevated rates of spam complaints. Emails from this domain will almost always be rejected at connection time or filtered to the spam folder. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Domain reputation 
 
@@ -78,7 +78,7 @@ Use the following table to help monitor and understand your domain reputation ra
 | Medium/Fair | Known to generate positive engagement but has occasionally received a low volume of spam complaints. Most of the emails from this domain will reach the inbox (except when there is a notable increase in spam levels). |
 | Low | Known to receive spam complaints regularly. Emails from this sender will likely be filtered to the spam folder. |
 | Bad | Has a history of receiving elevated rates of spam complaints. Emails from this domain will almost always be rejected at connection time or filtered to the spam folder. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Authentication
 
@@ -89,7 +89,7 @@ Use the authentication dashboard to review the percentage of emails that have pa
 | SPF | Shows the percentage of emails that passed SPF versus all emails from the domain that attempted SPF. This excludes any spoofed mail. |
 | DKIM | Shows the percentage of emails that passed DKIM versus all emails from the domain that attempted DKIM. |
 | DMARC | Shows the percentage of emails that passed DMARC alignment versus all emails received from the domain that passed either SPF or DKIM. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Encryption
 
@@ -99,7 +99,7 @@ Refer to this table to understand what percentage of your inbound and outbound t
 | ----- | ---------- |
 | TLS Inbound | Shows the percentage of incoming mail (to Gmail) that passed TLS versus all mail received from that domain. |
 | TLS Outbound | Shows the percentage of outgoing mail (from Gmail) accepted over TLS versus all mail sent to that domain. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For more ideas on improving deliverability, read [Deliverability pitfalls and spam traps][6]. Be sure to reference our [Email best practices][7] for things you should check for before sending an email campaign.
 
@@ -134,7 +134,7 @@ Refer to this table to understand the filter results
 | Green | Judged to be spam by Microsoft’s spam filter up to 10% of the given time frame. |
 | Yellow | Judged to be spam by Microsoft’s spam filter between 10% and 90% of the given time frame. |
 | Red | Judged to be spam by Microsoft’s spam filter up to more than 90% of the given time frame.| 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Complaint rate
 
@@ -147,7 +147,7 @@ To calculate the complaint rate, divide the number of complaints by the number o
 | Less than 0.3% | The ideal complaint rate. |
 | More than 0.3% | Review your sign-up process, and ensure your unsubscribe link is working. Also, consider whether mail could be better personalized to your audience. |
 | More than 100% | Note that SNDS displays complaints for the day they were reported, not retroactively against the day the complained-about mail was delivered. | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Spam trap hits
 
diff --git a/_docs/_user_guide/data_and_analytics/analytics/email_performance_dashboard.md b/_docs/_user_guide/data_and_analytics/analytics/email_performance_dashboard.md
index 091cd652706..2cb0ba8c786 100644
--- a/_docs/_user_guide/data_and_analytics/analytics/email_performance_dashboard.md
+++ b/_docs/_user_guide/data_and_analytics/analytics/email_performance_dashboard.md
@@ -46,7 +46,7 @@ Each tile shows the rate metric first, followed by the count metric (with the ex
 | Other opens rate | Rate | (Total number of total other opens across each day in the date range) / (Total number of deliveries for date range)<br><br>Other opens includes emails that haven't been identified as machine opens, such as when a user opens an email. This metric is non-unique and is a sub-metric of total opens.  |
 | Unique click rate | Rate | (Total number of unique clicks across each day in the date range) / (Total number of deliveries for a date range) |
 | Unique click to open rate | Rate | (Total number of unique clicks across each day in the date range) / (Total number of unique opens across each day in the date range) |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Email insights dashboard 
 
@@ -105,7 +105,7 @@ Each tile shows the rate metric first, followed by the count metric (with the ex
 | Click rate | Rate | (Total number of clicks across each day in the date range) / (Total number of deliveries across each day in the date range) |
 | Total opt-ins | Rate | Total number of inbound message opt-ins across each day in the date range |
 | Total opt-outs | Rate | Total number of inbound message opt-outs across each day in the date range |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Dashboard filters
 
diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/available_partners.md b/_docs/_user_guide/data_and_analytics/braze_currents/available_partners.md
index 93df2e65288..1ffb41ed217 100644
--- a/_docs/_user_guide/data_and_analytics/braze_currents/available_partners.md
+++ b/_docs/_user_guide/data_and_analytics/braze_currents/available_partners.md
@@ -35,6 +35,7 @@ These customer data platforms collect and route information from multiple source
 * [Tealium][8]
 * [Treasure Data][10]
 * [RudderStack][9]
+* [Adobe][12]
 
 ## Behavioral analytics
 
@@ -58,4 +59,5 @@ These partners specialize in product analytics and business intelligence and can
 [8]: {{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents#tealium-for-currents
 [9]: {{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents/
 [10]: {{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data_for_currents/
-[11]: {{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/heap/
\ No newline at end of file
+[11]: {{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/heap/
+[12]: {{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe_for_currents/
\ No newline at end of file
diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md
index a48d3b38948..d867add0b36 100644
--- a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md
+++ b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md
@@ -65,7 +65,7 @@ Can't see the code because of the scroll bar? See how to fix that [here]({{site.
 | `<zone>` | For internal use by Braze. |
 | `<partition>` | For internal use by Braze. Integer. |
 | `<offset>`| For internal use by Braze. Integer. Note that different files sent within the same hour will have a different `<offset>` parameter. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 File naming conventions may change in the future, Braze recommends searching all keys in your bucket that have a prefix of &lt;your-bucket-prefix&gt;.
diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md b/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md
index c8b891a61e5..77654c174fd 100644
--- a/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md
+++ b/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md
@@ -13,17 +13,17 @@ Contact your Braze representative or open a [support ticket]({{site.baseurl}}/br
 
 {% details Explanation of customer behavior and user event structure and platform values %}
 
-### Event structure 
+### Event structure
 
-This customer behavior and user events breakdown shows what type of information is generally included in a customer behavior or user event. With a solid understanding of its components, your developers and business intelligence strategy team can use the incoming Currents event data to make data-driven reports, charts and take advantage of other valuable data metrics. 
+This customer behavior and user events breakdown shows what type of information is generally included in a customer behavior or user event. With a solid understanding of its components, your developers and business intelligence strategy team can use the incoming Currents event data to make data-driven reports, charts and take advantage of other valuable data metrics.
 
 ![Breakdown of a user event showing a purchase event with the listed properties grouped by user-specific properties, behavior-specific properties, and device-specific properties]({% image_buster /assets/img/customer_engagement_event.png %})
 
-Customer behavior and user events are comprised of **user-specific** properties, **behavior-specific** properties, and **device-specific** properties. 
+Customer behavior and user events are comprised of **user-specific** properties, **behavior-specific** properties, and **device-specific** properties.
 
 ### Platform values
 
-Certain events return a `platform` value that specifies the platform of the user's device. 
+Certain events return a `platform` value that specifies the platform of the user's device.
 <br>The following table details the possible returned values:
 
 | User device | Platform value |
@@ -35,13 +35,12 @@ Certain events return a `platform` value that specifies the platform of the user
 | Web | `web` |
 | tvOS | `tvos` |
 | Roku | `roku` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation"}
 
 {% enddetails %}
 
 {% alert important %}
-Note that these schemas only apply to the flat file event data we send to Data Warehouse Storage partners (Google Cloud Storage, Amazon S3, and Microsoft Azure Blob Storage), and are not available for Segment connectors. For schema that apply to other partners, refer to our list of [available partners]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/available_partners/) and check their respective pages.<br><br>Additionally, note that Currents will drop events with excessively large payloads of greater than 900&nbsp;KB. 
-
+Storage schemas apply to the flat file event data we send to data warehouse storage partners (such as Google Cloud Storage, Amazon S3, and Microsoft Azure Blob Storage). Some event and destination combinations listed here are not yet generally available. For information on which events are supported by various partners, refer to our list of [available partners]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/available_partners/) and check their respective pages.<br><br>Additionally, note that Currents will drop events with excessively large payloads of greater than 900&nbsp;KB.
 {% endalert %}
 {% api %}
 
@@ -53,27 +52,85 @@ Custom Events
 
 This event occurs when a specific custom event is triggered. Use this to track when users perform custom events in your application.
 
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// [Braze Custom Event] custom event name: users.behaviors.CustomEvent
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// [Braze Custom Event] custom event name: users.behaviors.CustomEvent
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(optional, string) API ID of the app on which this event occurred",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "name" : "(required, string) Name of the custom event",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "properties" : "(required, string) Custom properties stored as a JSON encoded string",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
 ```json
-// Custom Event: users.behaviors.CustomEvent
+// [Braze Custom Event] custom event name: users.behaviors.CustomEvent
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (optional, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "name": (required, string) name of the custom event,
-  "properties": (required, string) JSON encoded string of the properties for this event,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_model" : "(optional, string) Model of the device",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
 #### Property details
 - For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you will need to explicitly collect the iOS IDFA and Android Google ad ID through the native SDKs. Learn more about them here: [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/), [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
@@ -94,28 +151,93 @@ This event occurs when a user makes a purchase. Use this data to track when user
 Purchases are special custom events and come with a JSON encoded string of custom event properties the same way custom events do.
 {% endalert %}
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Purchase Event: users.behaviors.Purchase
+// Purchase: users.behaviors.Purchase
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (optional, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "product_id": (required, string) ID of the product purchased,
-  "price": (required, float) price of the purchase,
-  "currency": (required, string) three letter alpha ISO 4217 currency code,
-  "properties": (required, string) JSON encoded string of the custom properties for this event,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "currency" : "(required, string) Currency of the purchase",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "price" : "(required, float) Price of the purchase",
+    "product_id" : "(required, string) ID of the product purchased",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Purchase: users.behaviors.Purchase
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(optional, string) API ID of the app on which this event occurred",
+  "currency" : "(required, string) Currency of the purchase",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "price" : "(required, float) Price of the purchase",
+  "product_id" : "(required, string) ID of the product purchased",
+  "properties" : "(required, string) Custom properties stored as a JSON encoded string",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Purchase: users.behaviors.Purchase
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "currency" : "(required, string) Currency of the purchase",
+    "device_model" : "(optional, string) Model of the device",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "price" : "(required, float) Price of the purchase",
+  "productId" : "(required, string) ID of the product purchased",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
 #### Property details
 - For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you will need to explicitly collect the iOS IDFA and Android Google ad ID through the native SDKs. Learn more about them here: [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/), [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
 - If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, reach out to your customer success manager or account manager to enable the feature flipper for sending `ad_id`.
@@ -130,33 +252,86 @@ Purchases are special custom events and come with a JSON encoded string of custo
 Sessions
 {% endapitags %}
 
-This event occurs when a user starts their first session in your application. Use this data to track when users start sessions. 
+This event occurs when a user starts their first session in your application. Use this data to track when users start sessions.
 
 {% alert tip %}
 When a user starts their first session, both a `FirstSession` and a `SessionStart` event are fired.
 {% endalert %}
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Session Start: users.behaviors.app.FirstSession
+// First Session: users.behaviors.app.FirstSession
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "session_id": (required, string) ID of the session,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of the device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "device_id": (optional, string) ID of the device on which the session occurred,
-  "gender": (optional, string) gender of the user (This field has been deprecated and will always return null),
-  "country": (optional, string) country of the user (This field has been deprecated and will always return null),
-  "language": (optional, string) language of the user (This field has been deprecated and will always return null),
-  "sdk_version": (optional, string) version of the Braze SDK in use during the session (This field has been deprecated and will always return null)
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "session_id" : "(optional, string) UUID of the session",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// First Session: users.behaviors.app.FirstSession
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "country" : "(optional, string) Country of the user",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "gender" : "(optional, string) Gender of the user, one of ['M', 'F', 'O', 'N', 'P']",
+  "id" : "(required, string) Globally unique ID for this event",
+  "language" : "(optional, string) Language of the user",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "sdk_version" : "(optional, string) Version of the Braze SDK in use during the event",
+  "session_id" : "(required, string) UUID of the session",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// First Session: users.behaviors.app.FirstSession
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_model" : "(optional, string) Model of the device",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "session_id" : "(optional, string) UUID of the session"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
 {% endapi %}
 
 {% api %}
@@ -173,22 +348,74 @@ This event occurs when a user starts a session. Use this data to track when user
 When a user starts their first session, both a `FirstSession` and a `SessionStart` event are fired.
 {% endalert %}
 
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Session Start: users.behaviors.app.SessionStart
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "session_id" : "(optional, string) UUID of the session",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
 ```json
 // Session Start: users.behaviors.app.SessionStart
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "session_id": (required, string) ID of the session,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of the device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "device_id": (optional, string) ID of the device on which the session occurred
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "session_id" : "(required, string) UUID of the session",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
 }
 ```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Session Start: users.behaviors.app.SessionStart
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_model" : "(optional, string) Model of the device",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "session_id" : "(optional, string) UUID of the session"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
 
 {% endapi %}
 
@@ -206,23 +433,78 @@ This occurs when a user exits your application, therefore ending their current s
 When a user starts their first session, both a `FirstSession` and a `SessionStart` event are fired.
 {% endalert %}
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
 // Session End: users.behaviors.app.SessionEnd
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "duration": (optional, float) seconds session lasted,
-  "session_id": (required, string) ID of the session,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of the device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "device_id": (optional, string) ID of the device on which the session occurred
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "duration" : "(optional, float) Duration of the session in seconds",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "session_id" : "(optional, string) UUID of the session",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Session End: users.behaviors.app.SessionEnd
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "duration" : "(optional, float) Duration of the session in seconds",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "session_id" : "(required, string) UUID of the session",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Session End: users.behaviors.app.SessionEnd
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_model" : "(optional, string) Model of the device",
+    "duration" : "(optional, float) Duration of the session in seconds",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "session_id" : "(optional, string) UUID of the session"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
 {% endapi %}
 
 {% api %}
@@ -235,29 +517,98 @@ Locations
 
 This event is triggered when a user visits a specified location. Use this to track users triggering location events in your app.
 
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Location: users.behaviors.Location
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "alt_accuracy" : "(optional, float) Altitude accuracy of recorded location",
+    "altitude" : "(optional, float) Altitude of recorded location",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "latitude" : "(required, float) Latitude of recorded location",
+    "ll_accuracy" : "(optional, float) Accuracy of the latitude and longitude of recorded location",
+    "longitude" : "(required, float) Longitude of recorded location",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
 ```json
-// Location Event: users.behaviors.Location
+// Location: users.behaviors.Location
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "latitude": (required, float) latitude of recorded location,
-  "longitude": (required, float) longitude of recorded location,
-  "altitude": (optional, float) altitude of recorded location,
-  "ll_accuracy": (optional, float) latitude/longitude accuracy of recorded location,
-  "alt_accuracy": (optional, float) altitude accuracy of recorded location,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "alt_accuracy" : "(optional, float) Altitude accuracy of recorded location",
+  "altitude" : "(optional, float) Altitude of recorded location",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "latitude" : "(required, float) Latitude of recorded location",
+  "ll_accuracy" : "(optional, float) Accuracy of the latitude and longitude of recorded location",
+  "longitude" : "(required, float) Longitude of recorded location",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
 }
 ```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Location: users.behaviors.Location
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "alt_accuracy" : "(optional, float) Altitude accuracy of recorded location",
+    "altitude" : "(optional, float) Altitude of recorded location",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_model" : "(optional, string) Model of the device",
+    "latitude" : "(required, float) Latitude of recorded location",
+    "ll_accuracy" : "(optional, float) Accuracy of the latitude and longitude of recorded location",
+    "longitude" : "(required, float) Longitude of recorded location",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
 #### Property details
 - For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you will need to explicitly collect the iOS IDFA and Android Google ad ID through the native SDKs. Learn more about them here: [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/), [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
 - If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, reach out to your customer success manager or account manager to enable the feature flipper for sending `ad_id`.
@@ -273,17 +624,61 @@ Attribution
 
 This event occurs when an app installation is attributed to a source. Use this to track where your app installs are coming from.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Install Attribution Event: users.behaviors.InstallAttribution
+// Install Attribution: users.behaviors.InstallAttribution
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "source": (required, string) the source of the attribution
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "source" : "(optional, string) The source of the attribution",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Install Attribution: users.behaviors.InstallAttribution
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "source" : "(required, string) The source of the attribution",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Install Attribution: users.behaviors.InstallAttribution
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "source" : "(optional, string) The source of the attribution"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
 
 {% endapi %}
 
@@ -295,20 +690,25 @@ This event occurs when an app installation is attributed to a source. Use this t
 Random Bucket Number
 {% endapitags %}
 
-This user event occurs every time a new user is created within their workspace. During this event, each new user gets assigned a random bucket number that you can then use to create uniformly distributed segments of random users. Use this to group a range of random bucket number values and compare performance across your campaigns and campaign variants. 
+This user event occurs every time a new user is created within their workspace. During this event, each new user gets assigned a random bucket number that you can then use to create uniformly distributed segments of random users. Use this to group a range of random bucket number values and compare performance across your campaigns and campaign variants.
 
+{% tabs %}
+{% tab Cloud Storage %}
 ```json
-// Random Bucket Number Event: users.RandomBucketNumberUpdate
+// Random Bucket Number Update: users.RandomBucketNumberUpdate
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) AppGroup API ID,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) UTC time of the event in milliseconds since the epoch,
-  "random_bucket_number": (required, int) new random bucket number
-  "prev_random_bucket_number":  (optional, int) old random bucket number, optional
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "prev_random_bucket_number" : "(optional, int) Previous random bucket number",
+  "random_bucket_number" : "(required, int) New random bucket number",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
 {% alert important %}
 Note that this Currents event is only available for customers that have purchased an "all events connector" and is only available for storage event connectors (i.e Amazon S3, Microsoft Azure, Google Cloud Storage).
diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md b/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md
index 63e5910a4d9..d9eb8e29fff 100644
--- a/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md
+++ b/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md
@@ -9,7 +9,7 @@ tool: Currents
 search_rank: 6
 ---
 
-These schemas only apply to the flat file event data we send to Data Warehouse Storage partners (Google Cloud Storage, Amazon S3, and Microsoft Azure Blob Storage). For schemas that apply to the other partners, refer to our list of [available partners]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/available_partners/) and check their respective pages.
+Storage schemas apply to the flat file event data we send to Data Warehouse Storage partners (Google Cloud Storage, Amazon S3, and Microsoft Azure Blob Storage). For schemas that apply to the other partners, refer to our list of [available partners]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/available_partners/) and check their respective pages.
 
 Contact your account manager or open a [support ticket]({{site.baseurl}}/braze_support/) if you need access to additional event entitlements. If you can't find what you need in this article, check out our [Customer Behavior Events Library]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/customer_behavior_events/) or our [Currents sample data examples](https://github.com/Appboy/currents-examples/tree/master/sample-data).
 
@@ -27,15 +27,15 @@ Message engagement events are comprised of **user-specific** properties, **campa
 
 Note the naming conventions for user IDs.
 
-| Braze schema | Currents schema | Description | 
+| Braze schema | Currents schema | Description |
 | ----------- | ----------- | ----------- |
 | `braze_id` | `"USER_ID"` | The unique identifier that is automatically assigned by Braze. |
 | `external_id` | `"EXTERNAL_USER_ID"` | The unique identifier of a user's profile that is set by the customer. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation"}
 
 ### Platform values
 
-Certain events return a `platform` value that specifies the platform of the user's device. 
+Certain events return a `platform` value that specifies the platform of the user's device.
 <br>The following table details the possible returned values:
 
 | User device | Platform value |
@@ -47,7 +47,7 @@ Certain events return a `platform` value that specifies the platform of the user
 | Web | `web` |
 | tvOS | `tvos` |
 | Roku | `roku` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation"}
 
 {% enddetails %}
 
@@ -83,30 +83,188 @@ WhatsApp, Read
 
 This event occurs when an WhatsApp message is read by the end user.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
 // WhatsApp Read: users.messages.whatsapp.Read
 
 {
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received,
-  "canvas_variation_id": (optional, string) Canvas variation ID of the variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation this event belongs to,
-  "company_id": (optional, string) ID of the sending Company,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "external_user_id": (optional, string) External user ID of the user,
-  "from_phone_number": (optional, string) phone number used to send,
-  "message_variation_id": (optional, string) message variation ID of the variation this user received,
-  "message_variation_name": (optional, string) name of the message variation this user received,
-  "subscription_group_id": (optional, string) ID of the sending subscription group,
-  "time": (optional, int) 10-digit UTC time of the event in seconds since the epoch,
-  "to_phone_number": (optional, string) phone number of User receiving the message,
-  "user_id": (required, string) Braze ID of the user that performed this event
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, long) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// WhatsApp Read: users.messages.whatsapp.Read
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// WhatsApp Read: users.messages.whatsapp.Read
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, long) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// WhatsApp Read: users.messages.whatsapp.Read
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// WhatsApp Read: users.messages.whatsapp.Read
+
+{
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, long) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
 
 {% endapi %}
 {% api %}
@@ -119,1788 +277,8668 @@ WhatsApp, Delivery
 
 This event occurs when an WhatsApp message sent made it successfully to the end-users device.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
 // WhatsApp Delivery: users.messages.whatsapp.Delivery
 
 {
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) ID of the Canvas step this event belongs to,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) Canvas variation ID of the variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation this event belongs to,
-  "company_id": (optional, string) ID of the sending Company,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "external_user_id": (optional, string) External user ID of the user,
-  "from_phone_number": (optional, string) phone number used to send,
-  "message_variation_id": (optional, string) message variation ID of the variation this user received,
-  "message_variation_name": (optional, string) name of the message variation this user received,
-  "subscription_group_id": (optional, string) ID of the sending subscription group,
-  "time": (optional, int) 10-digit UTC time of the event in seconds since the epoch,
-  "to_phone_number": (optional, string) phone number of User receiving the message,
-  "user_id": (required, string) Braze ID of the user that performed this event
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, long) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
+{% endtab %}
 
-{% endapi %}
-
-{% api %}
-
-## WhatsApp failure events
-
-{% apitags %}
-WhatsApp, Failure
-{% endapitags %}
+{% tab Cloud Storage %}
+```json
+// WhatsApp Delivery: users.messages.whatsapp.Delivery
 
-This event occurs when WhatsApp cannot deliver the message to the user. A hard bounce signifies a permanent deliverability failure.
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
+{% tab mParticle %}
 ```json
-// WhatsApp Delivery Failure: users.messages.whatsapp.Failure
-
-{
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) ID of the Canvas step this event belongs to,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) Canvas variation ID of the variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation this event belongs to,
-  "company_id": (optional, string) ID of the sending Company,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "external_user_id": (optional, string) External user ID of the user,
-  "from_phone_number": (optional, string) phone number used to send,
-  "message_variation_id": (optional, string) message variation ID of the variation this user received,
-  "message_variation_name": (optional, string) name of the message variation this user received,
-  "provider_error_code": (optional, string) Error Code from WhatsApp,
-  "provider_error_title": (optional, string) Description of failure from WhatsApp,
-  "subscription_group_id": (optional, string) ID of the sending subscription group,
-  "time": (optional, int) 10-digit UTC time of the event in seconds since the epoch,
-  "to_phone_number": (optional, string) phone number of User receiving the message,
-  "user_id": (required, string) Braze ID of the user that performed this event
+// WhatsApp Delivery: users.messages.whatsapp.Delivery
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, long) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
 }
 ```
-{% endapi %}
-{% api %}
+{% endtab %}
 
-## WhatsApp send events
-
-{% apitags %}
-WhatsApp, Sends
-{% endapitags %}
+{% tab Amplitude %}
+```json
+// WhatsApp Delivery: users.messages.whatsapp.Delivery
 
-This event occurs when a send request was successfully communicated between Braze and WhatsApp. Though, this does not mean the message was received by the end user.
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// WhatsApp Send: users.messages.whatsapp.Send
+// WhatsApp Delivery: users.messages.whatsapp.Delivery
 
 {
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) ID of the Canvas step this event belongs to,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) Canvas variation ID of the variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation this event belongs to,
-  "company_id": (optional, string) ID of the sending Company,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "external_user_id": (optional, string) External user ID of the user,
-  "from_phone_number": (optional, string) phone number used to send,
-  "message_extras": (optional, string) Liquid tags related fields,
-  "message_variation_id": (optional, string) message variation ID of the variation this user received,
-  "message_variation_name": (optional, string) name of the message variation this user received,
-  "subscription_group_id": (optional, string) ID of the sending subscription group,
-  "time": (optional, int) 10-digit UTC time of the event in seconds since the epoch,
-  "to_phone_number": (optional, string) phone number of User receiving the message,
-  "user_id": (required, string) Braze ID of the user that performed this event
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, long) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
+
 {% endapi %}
 
 {% api %}
 
-## WhatsApp abort message events
+## WhatsApp failure events
 
 {% apitags %}
-WhatsApp, Abort
+WhatsApp, Failure
 {% endapitags %}
 
-This event occurs if a WhatsApp message was aborted based on Liquid aborts, Quiet Hours, etc.
+This event occurs when WhatsApp cannot deliver the message to the user. A hard bounce signifies a permanent deliverability failure.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// WhatsApp Abort: users.messages.whatsapp.Abort
+// WhatsApp Failure: users.messages.whatsapp.Failure
 
 {
-  "abort_log": (optional, string) log message describing abort details (MAX: 128 CHARS),
-  "abort_type": (optional, string) type of abort, e.g.: "liquid_abort_message", "quiet_hours", etc.,
-  "action": (optional, string) action taken in response to this message (for example, Subscribed, Unsubscribed, or None),
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) id of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) id of the Canvas step this event belongs to,
-  "canvas_step_message_variation_id": (optional, string) id of the Canvas step message variation this user received,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) Canvas variation ID of the variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation this event belongs to,
-  "company_id": (optional, string) id of the sending Company,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "external_user_id": (optional, string) External user ID of the user,
-  "message_variation_id": (optional, string) message variation ID of the variation this user received,
-  "message_variation_name": (optional, string) name of the message variation this user received,
-  "send_id": (optional, string) message send ID this message belongs to,
-  "subscription_group_id": (optional, string) ID of the sending subscription group,
-  "time": (optional, int) 10-digit UTC time of the event in seconds since the epoch,
-  "user_id": (required, string) Braze ID of the user that performed this event
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "provider_error_code" : "(required, string) Error code from WhatsApp",
+    "provider_error_title" : "(required, string) Description of error from WhatsApp",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, long) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
 ```
-{% endapi %}
-{% api %}
-
-## WhatsApp inbound received events
-
-{% apitags %}
-WhatsApp, InboundReceived
-{% endapitags %}
-
-This event occurs when one of your users sends a WhatsApp message to a phone number in one of your Braze WhatsApp subscription groups. 
+{% endtab %}
 
+{% tab Cloud Storage %}
 ```json
-// WhatsApp Inbound Received: users.messages.whatsapp.InboundReceive
+// WhatsApp Failure: users.messages.whatsapp.Failure
 
 {
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) ID of the Canvas step this event belongs to,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) Canvas variation ID of the variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation this event belongs to,
-  "company_id": (optional, string) ID of the sending Company,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "external_user_id": (optional, string) External user ID of the user,
-  "inbound_phone_number": (optional, string)the inbound number that the message was sent to,
-  "medial_urls": (optional, string[]) media urls from the user, 
-  "message_body": (optional, string) typed response from the user,
-  "message_variation_id": (optional, string) message variation ID of the variation this user received,
-  "message_variation_name": (optional, string) name of the message variation this user received,
-  "quick_reply_text": (optional, string) test of button pressed by the user,
-  "subscription_group_id": (optional, string) ID of the sending subscription group,
-  "time": (optional, int) 10-digit UTC time of the event in seconds since the epoch,
-  "user_phone_number": (optional, string) the user’s phone number from which the message was received,
-  "user_id": (required, string) Braze ID of the user that performed this event
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "provider_error_code" : "(required, string) Error code from WhatsApp",
+  "provider_error_title" : "(required, string) Description of error from WhatsApp",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
 }
 ```
-{% endapi %}
+{% endtab %}
 
-{% api %}
+{% tab mParticle %}
+```json
+// WhatsApp Failure: users.messages.whatsapp.Failure
 
-## Content Card abort message events
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "provider_error_code" : "(required, string) Error code from WhatsApp",
+          "provider_error_title" : "(required, string) Description of error from WhatsApp",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, long) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
-{% apitags %}
-Abort, Content Cards
-{% endapitags %}
+{% tab Amplitude %}
+```json
+// WhatsApp Failure: users.messages.whatsapp.Failure
 
-This event occurs if a Content Card message was aborted based on Liquid aborts, Quiet Hours, etc.
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "provider_error_code" : "(required, string) Error code from WhatsApp",
+    "provider_error_title" : "(required, string) Description of error from WhatsApp",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// Content Card Abort: users.messages.contentcard.Abort
+// WhatsApp Failure: users.messages.whatsapp.Failure
 
 {
-  "abort_log": (optional, string) log message describing abort details (MAX: 128 CHARS),
-  "abort_type": (optional, string) type of abort, e.g.: "liquid_abort_message", "quiet_hours", etc.,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) ID of the Canvas step this event belongs to,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) Canvas variation ID of the variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation this event belongs to,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "external_user_id": (optional, string) External user ID of the user,
-  "id": (required, string) globally unique ID of this event,
-  "message_variation_id": (optional, string) message variation ID of the variation this user received,
-  "message_variation_name": (optional, string) name of the message variation this user received,
-  "send_id": (optional, string) message send ID this message belongs to,
-  "time": (required, int) unix timestamp at which the event happened,
-  "timezone": (optional, string) timezone of the user,
-  "user_id": (required, string) Braze ID of the user that performed this event
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "provider_error_code" : "(required, string) Error code from WhatsApp",
+    "provider_error_title" : "(required, string) Description of error from WhatsApp",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, long) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
+
 {% endapi %}
 
 {% api %}
 
-## Email abort message events
+## WhatsApp send events
 
 {% apitags %}
-Abort, Email
+WhatsApp, Sends
 {% endapitags %}
 
-This event occurs if an email message was aborted based on Liquid aborts, Quiet Hours, etc.
+This event occurs when a send request was successfully communicated between Braze and WhatsApp. Though, this does not mean the message was received by the end user.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Email Abort: users.messages.email.Abort
+// WhatsApp Send: users.messages.whatsapp.Send
 
 {
-  "abort_log": (optional, string) log message describing abort details (MAX: 128 CHARS),
-  "abort_type": (optional, string) type of abort, e.g.: "liquid_abort_message", "quiet_hours", etc.,
-  "app_group_id": (optional, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) ID of the Canvas step this event belongs to,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) Canvas variation ID of the variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation this event belongs to,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "email_address": (required, string) email address of the user,
-  "external_user_id": (optional, string) External user ID of the user,
-  "id": (required, string) globally unique ID of this event,
-  "ip_pool": (optional, string) IP Pool from which the email send was made
-  "message_variation_id": (optional, string) message variation ID of the variation this user received,
-  "message_variation_name": (optional, string) name of the message variation this user received,
-  "send_id": (optional, string) message send ID this message belongs to,
-  "time": (required, int) unix timestamp at which the event happened,
-  "timezone": (optional, string) timezone of the user,
-  "user_id": (required, string) Braze ID of the user that performed this event, 
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, long) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-{% endapi %}
+{% endtab %}
 
-{% api %}
+{% tab Cloud Storage %}
+```json
+// WhatsApp Send: users.messages.whatsapp.Send
 
-## Push notification abort events
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-{% apitags %}
-Abort, Push
-{% endapitags %}
+{% tab mParticle %}
+```json
+// WhatsApp Send: users.messages.whatsapp.Send
 
-This event occurs if a push notification message was aborted based on Liquid aborts, Quiet Hours, etc.
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+          "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, long) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
+{% tab Amplitude %}
 ```json
-// Push Notification Abort: users.messages.pushnotification.Abort
+// WhatsApp Send: users.messages.whatsapp.Send
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// WhatsApp Send: users.messages.whatsapp.Send
 
 {
-  "abort_log": (optional, string) log message describing abort details (MAX: 128 CHARS),
-  "abort_type": (optional, string) type of abort, e.g.: "liquid_abort_message", "quiet_hours", etc.,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "app_id": (required, string) Braze ID of the app this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received
-  "canvas_step_name": (optional, string) API ID of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "device_id": (optional, string), ID of the device on which the event occurred,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "external_user_id": (optional, string) External user ID of the user,
-  "id": (required, string) unique ID of this event,
-  "message_variation_id": (optional, string) ID of the message variation this user received,
-  "message_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "platform": (required, string) platform of the device,
-  "send_id": (optional, string) message send ID this message belongs to,
-  "time": (required, int) unix timestamp at which the event happened,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "user_id": (required, string) Braze ID of the user that performed this event
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(required, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, long) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
+
 {% endapi %}
 
 {% api %}
 
-## SMS abort message events
+## WhatsApp abort message events
 
 {% apitags %}
-Abort, SMS
+WhatsApp, Abort
 {% endapitags %}
 
-This event occurs if an SMS message was aborted based on Liquid aborts, Quiet Hours, etc.
+This event occurs if a WhatsApp message was aborted based on Liquid aborts, Quiet Hours, etc.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// SMS Abort: users.messages.sms.Abort
+// WhatsApp Abort: users.messages.whatsapp.Abort
 
 {
-  "abort_log": (optional, string) log message describing abort details (MAX: 128 CHARS),
-  "abort_type": (optional, string) type of abort, e.g.: "liquid_abort_message", "quiet_hours", etc.,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received
-  "canvas_step_name": (optional, string) API ID of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "external_user_id": (optional, string) External user ID of the user,
-  "id": (required, string) globally unique ID of this event,
-  "message_variation_id": (optional, string) ID of the message variation this user received,
-  "message_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "subscription_group_id": (optional, string) ID of the subscription group targeted for this SMS message,
-  "time": (required, int) unix timestamp at which the event happened,
-  "user_id": (required, string) Braze ID of the user that performed this event
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, long) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-{% endapi %}
+{% endtab %}
 
-{% api %}
+{% tab Cloud Storage %}
+```json
+// WhatsApp Abort: users.messages.whatsapp.Abort
 
-## Webhook abort message events
+{
+  "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+  "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-{% apitags %}
-Abort,  Webhooks
-{% endapitags %}
+{% tab mParticle %}
+```json
+// WhatsApp Abort: users.messages.whatsapp.Abort
 
-This event occurs if a webhook message was aborted based on Liquid aborts, Quiet Hours, etc.
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+          "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, long) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
+{% tab Amplitude %}
 ```json
-// Webhook Abort: users.messages.webhook.Abort
+// WhatsApp Abort: users.messages.whatsapp.Abort
 
 {
-  "abort_log": (optional, string) log message describing abort details (MAX: 128 CHARS),
-  "abort_type": (optional, string) type of abort, e.g.: "liquid_abort_message", "quiet_hours", etc.,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "campaign_id": (optional, string) internal-use Braze ID of the campaign this event belongs to,
-  "campaign_name": (optional, string) name of the campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_message_variation_id": (optional, string) ID of the Canvas step message variation this user received
-  "canvas_step_name": (optional, string) API ID of the Canvas step this event belongs to,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation this event belongs to,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "external_user_id": (optional, string) External user ID of the user,
-  "id": (required, string) globally unique ID of this event,
-  "message_variation_id": (optional, string) ID of the message variation this user received,
-  "message_variation_name": (optional, string) name of the message variation the user is in if from a Canvas,
-  "send_id": (optional, string) message send ID this message belongs to,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform),
-  "time": (required, int) unix timestamp at which the event happened,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "user_id": (required, string) Braze ID of the user that performed this event
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
 }
 ```
-{% endapi %}
+{% endtab %}
+
+{% tab Segment %}
+```json
+// WhatsApp Abort: users.messages.whatsapp.Abort
 
+{
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, long) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
 
+{% endapi %}
 {% api %}
 
-## Canvas exit performed event events
+## WhatsApp inbound received events
 
 {% apitags %}
-Exit, Canvas
+WhatsApp, InboundReceived
 {% endapitags %}
 
-This event occurs when a user has exited a Canvas by performing an event.
+This event occurs when one of your users sends a WhatsApp message to a phone number in one of your Braze WhatsApp subscription groups.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Canvas Exit Performed Event: users.canvas.exit.PerformedEvent
+// WhatsApp Inbound Received: users.messages.whatsapp.InboundReceive
 
 {
-  "id": (required, string) globally unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user, 
-  "external_user_id": (optional, string) External user ID of the user,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "app_group_api_id": (optional, string) API ID of the workspace this user belongs to,
-  "time": (required, int) unix timestamp at which the event happened,
-  "canvas_id": (required, string) ID of the Canvas if from a Canvas,
-  "canvas_variation_id": (required, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_api_id": (optional, string) Braze ID of the experiment step this event belongs to,
-  "canvas_variation_api_id": (optional, string) API ID of the Canvas variation this event belongs to,
-  "canvas_step_api_id": (optional, string) API ID of the Canvas step this event belongs to
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+    "media_urls" : "(optional, array of string) Media URLs from the user",
+    "message_body" : "(optional, string) Typed response from the user",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "quick_reply_text" : "(optional, string) Text of button pressed by the user",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, long) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token",
+    "user_phone_number" : "(required, string) The user's phone number from which the message was received"
+  }
 }
 ```
-{% endapi %}
-
-{% api %}
-
-## Canvas exit matched audience events
+{% endtab %}
 
-{% apitags %}
-Exit, Canvas
-{% endapitags %}
+{% tab Cloud Storage %}
+```json
+// WhatsApp Inbound Received: users.messages.whatsapp.InboundReceive
 
-This event occurs when a user has exited a Canvas by matching an audience.
+{
+  "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+  "media_urls" : "(optional, array of string) Media URLs from the user",
+  "message_body" : "(optional, string) Typed response from the user",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "quick_reply_text" : "(optional, string) Text of button pressed by the user",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(optional, string) Braze user ID of the user who performed this event",
+  "user_phone_number" : "(required, string) The user's phone number from which the message was received"
+}
+```
+{% endtab %}
 
+{% tab mParticle %}
 ```json
-// Canvas Exit Matched Audience: users.canvas.exit.MatchedAudience
+// WhatsApp Inbound Received: users.messages.whatsapp.InboundReceive
 
 {
-  "id": (required, string) globally unique ID of this event,
-  "user_id": (required, string) Braze user ID of the user, 
-  "external_user_id": (optional, string) External user ID of the user,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "app_group_api_id": (optional, string) API ID of the workspace this user belongs to,
-  "time": (required, int) unix timestamp at which the event happened,
-  "canvas_id": (required, string) ID of the Canvas if from a Canvas,
-  "canvas_variation_id": (required, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_api_id": (optional, string) Braze ID of the experiment step this event belongs to,
-  "canvas_variation_api_id": (optional, string) API ID of the Canvas variation this event belongs to,
-  "canvas_step_api_id": (optional, string) API ID of the Canvas step this event belongs to
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+          "message_body" : "(optional, string) Typed response from the user",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "quick_reply_text" : "(optional, string) Text of button pressed by the user",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, long) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) The user's phone number from which the message was received"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
 }
 ```
-{% endapi %}
-{% api %}
-## Experiment split entry events
+{% endtab %}
 
-{% apitags %}
-Experiment Step, Canvas
-{% endapitags %}
+{% tab Amplitude %}
+```json
+// WhatsApp Inbound Received: users.messages.whatsapp.InboundReceive
 
-This event occurs when a user enters a Canvas experiment step path.
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+    "media_urls" : "(optional, array of string) Media URLs from the user",
+    "message_body" : "(optional, string) Typed response from the user",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "quick_reply_text" : "(optional, string) Text of button pressed by the user",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "user_phone_number" : "(required, string) The user's phone number from which the message was received"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, long) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// Experiment Step Split Path Entry: users.canvas.experimentstep.SplitEntry
+// WhatsApp Inbound Received: users.messages.whatsapp.InboundReceive
 
 {
-  "id": (required, string) globally unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user, 
-  "external_user_id": (optional, string) External user ID of the user,
-  "time": (required, int) unix timestamp at which the event happened,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "experiment_step_id": (required, string) Braze ID of the experiment step this event belongs to,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "experiment_split_id": (optional, string) Braze ID of the experiment split the user enrolled in,
-  "experiment_split_name": (optional, string) name of the experiment split the user enrolled in,
-  "in_control_group": (required, boolean) whether the user was enrolled in the control group
+  "context" : {
+    "traits" : {
+      "phone" : "(required, string) The user's phone number from which the message was received"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+    "media_urls" : "(optional, array of string) Media URLs from the user",
+    "message_body" : "(optional, string) Typed response from the user",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "quick_reply_text" : "(optional, string) Text of button pressed by the user",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, long) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
 {% endapi %}
 
 {% api %}
 
-## Experiment conversion events
+## Content Card abort message events
 
 {% apitags %}
-Experiment Step, Canvas
+Abort, Content Cards
 {% endapitags %}
 
-This event occurs when a user convert for a Canvas experiment step.
+This event occurs if a Content Card message was aborted based on Liquid aborts, Quiet Hours, etc.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Experiment Step Conversion: users.canvas.experimentstep.Conversion
+// Content Card Abort: users.messages.contentcard.Abort
 
 {
-  "id": (required, string) globally unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user, 
-  "external_user_id": (optional, string) External user ID of the user,
-  "app_id": (optional, string) Braze ID of the app this user belongs to,
-  "time": (required, int) unix timestamp at which the event happened,
-  "canvas_id": (required, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "experiment_step_id": (optional, string) Braze ID of the experiment step this event belongs to,
-  "experiment_split_id": (required, string) Braze ID of the experiment split variation this user received,
-  "experiment_split_name": (optional, string) name of the experiment split the user enrolled in,
-  "conversion_behavior_index": (optional, int) index of the conversion behavior,
-  "conversion_behavior": (optional, string) conversion behavior
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-{% endapi %}
-{% api %}
-
-## Push send events
-
-{% apitags %}
-Push, Sends
-{% endapitags %}
-
-This event occurs when Braze processes a push message for a user, communicating this to Apple Push Notification Service or Fire Cloud Messaging. This does not mean the push was delivered to the device, just that a message was sent.
+{% endtab %}
 
+{% tab Cloud Storage %}
 ```json
-// Push Notification Send: users.messages.pushnotification.Send
+// Content Card Abort: users.messages.contentcard.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,  
-  "platform": (required, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) name of the message variation the user is in if from a Canvas,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,  
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "device_id": (optional, string) ID of the device that we made a delivery attempt to,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device,
-  "message_extras": (optional, string) key-value pairs sent with this event
+  "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+  "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
 }
 ```
+{% endtab %}
 
-#### Property details
-- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
-- If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
-- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
-{% endapi %}
-{% api %}
+{% tab mParticle %}
+```json
+// Content Card Abort: users.messages.contentcard.Abort
 
-## Push open events
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+          "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
-{% apitags %}
-Push, Opens
-{% endapitags %}
+{% tab Amplitude %}
+```json
+// Content Card Abort: users.messages.contentcard.Abort
 
-This event occurs when a user directly clicks on the Push notification to open the application. Currently, Push Open Events refer specifically to "Direct Opens" rather than "Total Opens". This does not include statistics shown at the campaign level of "influenced opens" as these are not attributed at the user level.
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// Push Notification Open: users.messages.pushnotification.Open
+// Content Card Abort: users.messages.contentcard.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_step_message_variation_id": (optional, string) API ID of the Canvas step message variation this user received,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "device_id": (optional, string) ID of the device that we made a delivery attempt to,
-  "button_action_type": (optional, string) Action type of the push notification,
-  button. One of [URI, DEEP_LINK, NONE, CLOSE]. null if not
-  from a button click,
-  "button_string": (optional, string) identifier (button_string) of the push notification button clicked. null if not from a button click,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
-#### Property details
-- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
-- If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+{% endtab %}
+{% endtabs %}
+
 {% endapi %}
+
 {% api %}
 
-## Push notifications in the iOS foreground events
+## Email abort message events
 
 {% apitags %}
-Push, iOS, Sends
+Abort, Email
 {% endapitags %}
 
-This event is not supported by our [Swift SDK](https://github.com/braze-inc/braze-swift-sdk) and is now deprecated using our [Obj-C SDK](https://github.com/Appboy/appboy-ios-sdk).
+This event occurs if an email message was aborted based on Liquid aborts, Quiet Hours, etc.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Push Notification iOS Foreground: users.messages.pushnotification.IosForeground
-{
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "platform": (required, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "device_id": (optional, string) ID of the device that we made a delivery attempt to,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+// Email Abort: users.messages.email.Abort
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-#### Property details
-- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
-- If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
-{% endapi %}
-{% api %}
+{% endtab %}
 
-## Push notifications bounce
-
-{% apitags %}
-Push, Sends, Bounce
-{% endapitags %}
+{% tab Cloud Storage %}
+```json
+// Email Abort: users.messages.email.Abort
 
-This event occurs when an error is received from either Apple Push Notification Service or Fire Cloud Messaging. This means that the push message was bounced, and therefore not delivered to the user's device.
+{
+  "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+  "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "email_address" : "(required, string) Email address of the user",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "ip_pool" : "(optional, string) IP pool from which the email send was made",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
+{% tab mParticle %}
 ```json
-// Push Notification Bounce: users.messages.pushnotification.Bounce
+// Email Abort: users.messages.email.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (required, string) ID for the app on which the bounce occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "device_id": (optional, string) ID of the device that we made a delivery attempt to,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+          "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "ip_pool" : "(optional, string) IP pool from which the email send was made",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(required, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
 }
 ```
-#### Property details
-- If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, reach out to your customer success manager or account manager to enable the feature flipper for sending `ad_id`.
-{% endapi %}
-{% api %}
-
-## Email send events
+{% endtab %}
 
-{% apitags %}
-Email, Sends
-{% endapitags %}
+{% tab Amplitude %}
+```json
+// Email Abort: users.messages.email.Abort
 
-This event occurs when an email send request was successfully communicated between Braze and SendGrid. Though, this does not mean the email was received in the end user's inbox.
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// Email Send: users.messages.email.Send
+// Email Abort: users.messages.email.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "email_address": (required, string) email address for this event,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "ip_pool": (optional, string) IP pool used for message sending, 
-  "message_extras": (optional, string) key-value pairs sent with this event
+  "context" : {
+    "traits" : {
+      "email" : "(required, string) Email address of the user"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
-#### Property details
-
-- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
-- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
 {% endapi %}
 
-
 {% api %}
 
-## Email delivery events
+## Push notification abort events
 
 {% apitags %}
-Email, Delivery
+Abort, Push
 {% endapitags %}
 
-This event occurs when an email sent made it successfully to the end-users inbox.
+This event occurs if a push notification message was aborted based on Liquid aborts, Quiet Hours, etc.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Email Delivery: users.messages.email.Delivery
+// Push Notification Abort: users.messages.pushnotification.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "email_address": (required, string) email address for this event,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,  
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "sending_ip": (optional, string) the IP address from which the message was sent (Email Delivery, Bounce, and SoftBounce events only. Will only be shown on events if the message was actually attempted for delivery. For certain other bounces, the information could be lost if the recipient server has already accepted the mail and only later after the connection is closed decided it could not deliver the mail),
-  "ip_pool": (optional, string) IP pool used for message sending,
-  "esp": (optional, string) ESP related to the event (SparkPost or SendGrid),
-  "from_domain": (optional, string) sending domain for the email
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
+{% endtab %}
 
-#### Property details
-
-- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
-{% endapi %}
+{% tab Cloud Storage %}
+```json
+// Push Notification Abort: users.messages.pushnotification.Abort
 
-{% api %}
+{
+  "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+  "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(optional, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "platform" : "(required, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-## Email open events
+{% tab mParticle %}
+```json
+// Push Notification Abort: users.messages.pushnotification.Abort
 
-{% apitags %}
-Email, Opens
-{% endapitags %}
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+          "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
-This event occurs when a user opens an email. Multiple events may be generated for the same campaign if a user opens the email multiple times.
+{% tab Amplitude %}
+```json
+// Push Notification Abort: users.messages.pushnotification.Abort
 
-{% alert important %}
-It's known behavior that the email open event fields `browser`, `device_os`, `device_model`, and `mailbox_provider` are empty. You can ignore these for now.
-{% endalert %}
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// Email Open: users.messages.email.Open
+// Push Notification Abort: users.messages.pushnotification.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "email_address": (required, string) email address for this event,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),  
-  "user_agent": (optional, string) description of the user's system and browser for the event,
-  "ip_pool": (optional, string) IP pool used for message sending,
-  "machine_open": (optional, string) Indicator of whether the email was opened by an automated process, such as Apple or Google mail pre-fetching. Currently "true" or null, but additional granularity (for example, "Apple" or "Google" to indicate which process made the fetch) may be added in the future.,
-  "esp": (optional, string) ESP related to the event (SparkPost or SendGrid),
-  "from_domain": (optional, string) sending domain for the email,
-  "is_amp": (optional, boolean) indicates that this is an AMP event,
-  "device_class": (optional, string) type of device used, such as 'mobile', 'desktop', 'tablet', 'other',
-  "device_os": (optional, string) the operating system used, such as 'os x', 'android', 'iOS',
-  "browser": (optional, string) browser used, such as 'chrome', 'edge', 'safari',
-  "device_model": (optional, string) model of device used, such as 'iPhone',
-  "mailbox_provider": (optional, string) the mailbox provider
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "type" : "(required, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(required, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
-#### Property details
-
-- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
 {% endapi %}
 
 {% api %}
 
-## Email clicks events
+## SMS abort message events
 
 {% apitags %}
-Email, Clicks
+Abort, SMS
 {% endapitags %}
 
-This event occurs when a user clicks an email. Multiple events may be generated for the same campaign if a user clicks multiple times or clicks different links within the email.
-
-{% alert important %}
-It's known behavior that the email clicks event fields `browser`, `device_os`, `device_model`, and `mailbox_provider` are empty. You can ignore these for now.
-{% endalert %}
+This event occurs if an SMS message was aborted based on Liquid aborts, Quiet Hours, etc.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Email Click: users.messages.email.Click
+// SMS Abort: users.messages.sms.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Only included when campaign_id is present. Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "email_address": (required, string) email address for this event,
-  "url": (optional, string) the URL that was clicked,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "user_agent": (optional, string) description of the user's system and browser for the event,
-  "ip_pool": (optional, string) IP pool used for message sending,
-  "link_id": (optional, string) unique value generated by Braze for the URL - null unless link aliasing is enabled,
-  "link_alias": (optional, string) alias name set when the message was sent - null unless link aliasing is enabled,
-  "esp": (optional, string) ESP related to the event (SparkPost or SendGrid),
-  "from_domain": (optional, string) sending domain for the email,
-  "is_amp": (optional, boolean) indicates that this is an AMP event,
-  "device_class": (optional, string) type of device used, such as 'mobile', 'desktop', 'tablet', 'other',
-  "device_os": (optional, string) the operating system used, such as 'os x', 'android', 'iOS',
-  "browser": (optional, string) browser used, such as 'chrome', 'edge', 'safari',
-  "device_model": (optional, string) model of device used, such as 'iPhone',
-  "mailbox_provider": (optional, string) the mailbox provider
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
+{% endtab %}
 
-#### Property details
+{% tab Cloud Storage %}
+```json
+// SMS Abort: users.messages.sms.Abort
 
-- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
-{% endapi %}
+{
+  "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+  "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-{% api %}
+{% tab mParticle %}
+```json
+// SMS Abort: users.messages.sms.Abort
 
-## Email bounce event
+{
+  "device_info" : { },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+          "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
-{% apitags %}
-Email, Bounce
-{% endapitags %}
+{% tab Amplitude %}
+```json
+// SMS Abort: users.messages.sms.Abort
 
-This event occurs when an Internet Service Provider returns a hard bounce. A hard bounce signifies a permanent deliverability failure.
+{
+  "event_properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// Email Bounce: users.messages.email.Bounce
+// SMS Abort: users.messages.sms.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "email_address": (required, string) email address for this event,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "sending_ip": (optional, string) the IP address from which the message was sent (Email Delivery, Bounce, and SoftBounce events only. Will only be shown on events if the message was actually attempted for delivery. For certain other bounces, the information could be lost if the recipient server has already accepted the mail and only later after the connection is closed decided it could not deliver the mail),
-  "ip_pool": (optional, string) IP pool used for message sending (for certain bounce cases, IP pool will not be provided) ,
-  "bounce_reason": (optional, string) reason for bounce provided by server,
-  "esp": (optional, string) ESP related to the event (SparkPost or SendGrid),
-  "from_domain": (optional, string) sending domain for the email,
-  "is_drop": (optional, boolean) indicates that this event counts as a drop event
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
-#### Property details
-
-- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
 {% endapi %}
 
 {% api %}
 
-## Email soft bounce event
+## Webhook abort message events
 
 {% apitags %}
-Email, Bounce
+Abort, Webhooks
 {% endapitags %}
 
-This event occurs when an Internet Service Provider returns a soft bounce. A soft bounce signifies that an email could not be delivered because of a temporary deliverability failure.
+This event occurs if a webhook message was aborted based on Liquid aborts or Quiet Hours.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Email Soft Bounce: users.messages.email.SoftBounce
+// Webhook Abort: users.messages.webhook.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "email_address": (required, string) email address for this event,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "sending_ip": (optional, string) the IP address from which the message was sent (Email Delivery, Bounce, and SoftBounce events only. Will only be shown on events if the message was actually attempted for delivery. For certain other bounces, the information could be lost if the recipient server has already accepted the mail and only later after the connection is closed decided it could not deliver the mail),
-  "ip_pool": (optional, string) IP pool used for message sending(for certain bounce cases, IP pool will not be provided),
-  "bounce_reason": (optional, string) reason for bounce provided by server,
-  "esp": (optional, string) ESP related to the event (SparkPost or SendGrid),
-  "from_domain": (optional, string) sending domain for the email
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
+{% endtab %}
 
-#### Property details
+{% tab Cloud Storage %}
+```json
+// Webhook Abort: users.messages.webhook.Abort
 
-- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
-{% endapi %}
+{
+  "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+  "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-{% api %}
+{% tab mParticle %}
+```json
+// Webhook Abort: users.messages.webhook.Abort
 
-## Email spam events
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+          "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
-{% apitags %}
-Email, Spam
-{% endapitags %}
+{% tab Amplitude %}
+```json
+// Webhook Abort: users.messages.webhook.Abort
 
-This event occurs when the end-user hits the "spam" button on the email. Note that this does not represent the fact the email went into the spam folder as Braze does not track this.
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// Email Mark As Spam: users.messages.email.MarkAsSpam
+// Webhook Abort: users.messages.webhook.Abort
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "email_address": (required, string) email address for this event,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "user_agent": (optional, string) This field is no longer used in any destination for this event and will always be empty,
-  "ip_pool": (optional, string) IP pool used for message sending,
-  "esp": (optional, string) ESP related to the event (SparkPost or SendGrid),
-  "from_domain": (optional, string) sending domain for the email
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "abort_log" : "(optional, string) Log message describing abort details (up to 128 chars)",
+    "abort_type" : "(optional, string) Type of abort, one of ['liquid_abort_message', 'message_ttl', 'quiet_hours', 'template_parse_error']",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
-#### Property details
-
-The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
 {% endapi %}
 
-
 {% api %}
 
-## Email unsubscribe events
+## Canvas exit performed event events
 
 {% apitags %}
-Email, Subscription
+Exit, Canvas
 {% endapitags %}
 
-This event occurs when the end-user has clicked "unsubscribe" from the email.
-
-{% alert important %}
-The `Unsubscribe` event is actually a specialized click event that is fired when your user clicks on the unsubscribe link in the email (either a normal unsubscribe link within the email body or footer, or using the [list-unsubscribe header]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/email_settings#include-a-list-unsubscribe-header)), not when the user changes state to unsubscribed. If subscription state change is sent through the API, or via custom (non-Braze) unsubscription link, it will not trigger an event on Currents.
-{% endalert %}
+This event occurs when a user has exited a Canvas by performing an event.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Email Unsubscribe: users.messages.email.Unsubscribe
+// Exit Perform Event: users.canvas.exit.PerformedEvent
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform). Users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user.,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "email_address": (required, string) email address for this event,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "ip_pool": (optional, string) IP pool used for message sending
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-#### Property details
-
-The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
-{% endapi %}
+{% endtab %}
 
-{% api %}
+{% tab Cloud Storage %}
+```json
+// Exit Perform Event: users.canvas.exit.PerformedEvent
 
-## In-app message impression events
+{
+  "app_group_api_id" : "(optional, string) [DEPRECATED]",
+  "app_group_id" : "(required, string) API ID of the app group this user belongs to",
+  "canvas_api_id" : "(optional, string) [DEPRECATED]",
+  "canvas_id" : "(required, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_api_id" : "(optional, string) [DEPRECATED]",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_api_id" : "(optional, string) [DEPRECATED]",
+  "canvas_variation_id" : "(required, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-{% apitags %}
-In-App Messages, Impressions
-{% endapitags %}
+{% tab mParticle %}
+```json
+// Exit Perform Event: users.canvas.exit.PerformedEvent
 
-This event occurs when a user views an in-app message.
+{
+  "device_info" : { },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
+{% tab Amplitude %}
 ```json
-// In-App Message Impression: users.messages.inappmessage.Impression
+// Exit Perform Event: users.canvas.exit.PerformedEvent
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "card_id": (optional, string) ID of the card that was viewed,  
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device,
-  "message_extras": (optional, string) a JSON string of the tagged key-value pairs during Liquid rendering
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
 }
 ```
+{% endtab %}
 
-{% alert note %}
-The `message_extras` field is active as of April 4, 2024.
-{% endalert %}
-
-#### Property details
-- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
-- If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
-- `message_extras` allow you to annotate your in-app message impression events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. The following minimum SDK versions are required, refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more:
+{% tab Segment %}
+```json
+// Exit Perform Event: users.canvas.exit.PerformedEvent
 
-{% sdk_min_versions web:5.2.0 android:30.4.0 swift:8.4.0 %}
+{
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
 
 {% endapi %}
 
 {% api %}
 
-## In-app message click events
+## Canvas exit matched audience events
 
 {% apitags %}
-In-App Messages, Clicks
+Exit, Canvas
 {% endapitags %}
 
-This event occurs when a user clicks on an in-app message.
+This event occurs when a user has exited a Canvas by matching an audience.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// In-App Message Click: users.messages.inappmessage.Click
+// Exit Match Audience: users.canvas.exit.MatchedAudience
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "card_id": (optional, string) ID of the card that was viewed,  
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "button_id": (optional, string) index of the button clicked if it was a button that was clicked, tracking ID of the click if the event came from an appboyBridge.logClick or brazeBridge.logClick invocation, or choice_id if the in app-message type is a simple survey,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-#### Property details
-- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
-- If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
-{% endapi %}
+{% endtab %}
 
+{% tab Cloud Storage %}
+```json
+// Exit Match Audience: users.canvas.exit.MatchedAudience
 
-{% api %}
-
-## Webhook send events
+{
+  "app_group_api_id" : "(optional, string) [DEPRECATED]",
+  "app_group_id" : "(required, string) API ID of the app group this user belongs to",
+  "canvas_api_id" : "(optional, string) [DEPRECATED]",
+  "canvas_id" : "(required, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_api_id" : "(optional, string) [DEPRECATED]",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_api_id" : "(optional, string) [DEPRECATED]",
+  "canvas_variation_id" : "(required, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-{% apitags %}
-Webhooks, Sends
-{% endapitags %}
+{% tab mParticle %}
+```json
+// Exit Match Audience: users.canvas.exit.MatchedAudience
 
-This event occurs when a webhook was processed and sent to the third party specified in that webhook. Note that this does not signify whether or not the request was received.
+{
+  "device_info" : { },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
+{% tab Amplitude %}
 ```json
-// Webhook Send: users.messages.webhook.Send
+// Exit Match Audience: users.canvas.exit.MatchedAudience
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "message_extras": (optional, string) key-value pairs sent with this event
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
 }
 ```
-#### Property details
+{% endtab %}
 
-- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
+{% tab Segment %}
+```json
+// Exit Match Audience: users.canvas.exit.MatchedAudience
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
 
 {% endapi %}
 
 {% api %}
-## Content Card send events
+## Experiment split entry events
 
 {% apitags %}
-Content Cards, Sends
+Experiment Step, Canvas
 {% endapitags %}
 
-This event occurs when a Content Card gets sent to a user.
+This event occurs when a user enters a Canvas experiment step path.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Content Card Send: users.messages.contentcard.Send
+// Experiment Split Entry: users.canvas.experimentstep.SplitEntry
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "content_card_id": (required, string) ID of the content card that was sent,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_name": (optional, string) name of the Canvas,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "message_extras": (optional, string) key-value pairs sent with this event
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+    "experiment_split_name" : "(optional, string) Name of the experiment split",
+    "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-#### Property details
+{% endtab %}
 
-- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
-{% endapi %}
+{% tab Cloud Storage %}
+```json
+// Experiment Split Entry: users.canvas.experimentstep.SplitEntry
 
-{% api %}
-## Content Card impression events
+{
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+  "experiment_split_name" : "(optional, string) Name of the experiment split",
+  "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-{% apitags %}
+{% tab mParticle %}
+```json
+// Experiment Split Entry: users.canvas.experimentstep.SplitEntry
+
+{
+  "device_info" : { },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+          "experiment_split_name" : "(optional, string) Name of the experiment split",
+          "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to",
+          "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Experiment Split Entry: users.canvas.experimentstep.SplitEntry
+
+{
+  "event_properties" : {
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+    "experiment_split_name" : "(optional, string) Name of the experiment split",
+    "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to",
+    "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Experiment Split Entry: users.canvas.experimentstep.SplitEntry
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+    "experiment_split_name" : "(optional, string) Name of the experiment split",
+    "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to",
+    "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+{% endapi %}
+
+{% api %}
+
+## Experiment conversion events
+
+{% apitags %}
+Experiment Step, Canvas
+{% endapitags %}
+
+This event occurs when a user convert for a Canvas experiment step.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Experiment Step Conversion: users.canvas.experimentstep.Conversion
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+    "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+    "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+    "experiment_split_name" : "(optional, string) Name of the experiment split",
+    "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Experiment Step Conversion: users.canvas.experimentstep.Conversion
+
+{
+  "app_id" : "(optional, string) API ID of the app on which this event occurred",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+  "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+  "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+  "experiment_split_name" : "(optional, string) Name of the experiment split",
+  "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Experiment Step Conversion: users.canvas.experimentstep.Conversion
+
+{
+  "device_info" : { },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+          "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+          "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+          "experiment_split_name" : "(optional, string) Name of the experiment split",
+          "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Experiment Step Conversion: users.canvas.experimentstep.Conversion
+
+{
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+    "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+    "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+    "experiment_split_name" : "(optional, string) Name of the experiment split",
+    "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Experiment Step Conversion: users.canvas.experimentstep.Conversion
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+    "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+    "experiment_split_id" : "(optional, string) API ID of the experiment split the user enrolled in",
+    "experiment_split_name" : "(optional, string) Name of the experiment split",
+    "experiment_step_id" : "(optional, string) API ID of the experiment step this event belongs to"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+{% endapi %}
+
+{% api %}
+
+## Push send events
+
+{% apitags %}
+Push, Sends
+{% endapitags %}
+
+This event occurs when Braze processes a push message for a user, communicating this to Apple Push Notification Service or Fire Cloud Messaging. This does not mean the push was delivered to the device, just that a message was sent.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Push Notification Send: users.messages.pushnotification.Send
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Push Notification Send: users.messages.pushnotification.Send
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "platform" : "(required, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Push Notification Send: users.messages.pushnotification.Send
+
+{
+  "device_info" : {
+    "ios_advertising_id" : "(optional, string) Advertising identifier",
+    "android_advertising_id" : "(optional, string) Advertising identifier",
+    "microsoft_advertising_id" : "(optional, string) Advertising identifier",
+    "roku_advertising_id" : "(optional, string) Advertising identifier",
+    "limit_ad_tracking" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Push Notification Send: users.messages.pushnotification.Send
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Push Notification Send: users.messages.pushnotification.Send
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "type" : "(required, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(required, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
+- If you're using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
+  {% endapi %}
+  {% api %}
+
+## Push open events
+
+{% apitags %}
+Push, Opens
+{% endapitags %}
+
+This event occurs when a user directly clicks on the Push notification to open the application. Currently, Push Open Events refer specifically to "Direct Opens" rather than "Total Opens". This does not include statistics shown at the campaign level of "influenced opens" as these are not attributed at the user level.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Push Notification Open: users.messages.pushnotification.Open
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Push Notification Open: users.messages.pushnotification.Open
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "button_action_type" : "(optional, string) Action type of the push notification button, null if not from a button click. One of ['uri', 'deep_link', 'none', 'close']",
+  "button_string" : "(optional, string) Identifier (button_string) of the push notification button clicked. null if not from a button click",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_message_variation_id" : "(optional, string) API ID of the Canvas step message variation this user received",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Push Notification Open: users.messages.pushnotification.Open
+
+{
+  "device_info" : {
+    "ios_advertising_id" : "(optional, string) Advertising identifier",
+    "android_advertising_id" : "(optional, string) Advertising identifier",
+    "microsoft_advertising_id" : "(optional, string) Advertising identifier",
+    "roku_advertising_id" : "(optional, string) Advertising identifier",
+    "limit_ad_tracking" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "device_model" : "(optional, string) Model of the device",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Push Notification Open: users.messages.pushnotification.Open
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_model" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Push Notification Open: users.messages.pushnotification.Open
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "model" : "(optional, string) Model of the device",
+      "type" : "(optional, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
+- If you're using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+  {% endapi %}
+  {% api %}
+
+## Push notifications in the iOS foreground events
+
+{% apitags %}
+Push, iOS, Sends
+{% endapitags %}
+
+This event is not supported by our [Swift SDK](https://github.com/braze-inc/braze-swift-sdk) and is now deprecated using our [Obj-C SDK](https://github.com/Appboy/appboy-ios-sdk).
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Push Notification iOS Foreground Open: users.messages.pushnotification.IosForeground
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Push Notification iOS Foreground Open: users.messages.pushnotification.IosForeground
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "platform" : "(required, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Push Notification iOS Foreground Open: users.messages.pushnotification.IosForeground
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_model" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Push Notification iOS Foreground Open: users.messages.pushnotification.IosForeground
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "model" : "(optional, string) Model of the device",
+      "type" : "(optional, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
+- If you're using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+  {% endapi %}
+  {% api %}
+
+## Push notifications bounce
+
+{% apitags %}
+Push, Sends, Bounce
+{% endapitags %}
+
+This event occurs when an error is received from either Apple Push Notification Service or Fire Cloud Messaging. This means that the push message was bounced, and therefore not delivered to the user's device.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Push Notification Bounce: users.messages.pushnotification.Bounce
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Push Notification Bounce: users.messages.pushnotification.Bounce
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "platform" : "(optional, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Push Notification Bounce: users.messages.pushnotification.Bounce
+
+{
+  "device_info" : {
+    "ios_advertising_id" : "(optional, string) Advertising identifier",
+    "android_advertising_id" : "(optional, string) Advertising identifier",
+    "microsoft_advertising_id" : "(optional, string) Advertising identifier",
+    "roku_advertising_id" : "(optional, string) Advertising identifier",
+    "limit_ad_tracking" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Push Notification Bounce: users.messages.pushnotification.Bounce
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Push Notification Bounce: users.messages.pushnotification.Bounce
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "type" : "(optional, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- If you're using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, reach out to your customer success manager or account manager to enable the feature flipper for sending `ad_id`.
+  {% endapi %}
+  {% api %}
+
+## Email send events
+
+{% apitags %}
+Email, Sends
+{% endapitags %}
+
+This event occurs when an email send request was successfully communicated between Braze and SendGrid. Though, this does not mean the email was received in the end user's inbox.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Email Send: users.messages.email.Send
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Email Send: users.messages.email.Send
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "email_address" : "(required, string) Email address of the user",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "ip_pool" : "(optional, string) IP pool from which the email send was made",
+  "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Email Send: users.messages.email.Send
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+          "from_domain" : "(optional, string) Sending domain for the email",
+          "ip_pool" : "(optional, string) IP pool from which the email send was made",
+          "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(required, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Email Send: users.messages.email.Send
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Email Send: users.messages.email.Send
+
+{
+  "context" : {
+    "traits" : {
+      "email" : "(required, string) Email address of the user"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
+  {% endapi %}
+
+
+{% api %}
+
+## Email delivery events
+
+{% apitags %}
+Email, Delivery
+{% endapitags %}
+
+This event occurs when an email sent made it successfully to the end-users inbox.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Email Delivery: users.messages.email.Delivery
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Email Delivery: users.messages.email.Delivery
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "email_address" : "(required, string) Email address of the user",
+  "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_domain" : "(optional, string) Sending domain for the email",
+  "id" : "(required, string) Globally unique ID for this event",
+  "ip_pool" : "(optional, string) IP pool from which the email send was made",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "sending_ip" : "(optional, string) IP address from which the email send was made",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Email Delivery: users.messages.email.Delivery
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+          "from_domain" : "(optional, string) Sending domain for the email",
+          "ip_pool" : "(optional, string) IP pool from which the email send was made",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(required, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Email Delivery: users.messages.email.Delivery
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Email Delivery: users.messages.email.Delivery
+
+{
+  "context" : {
+    "traits" : {
+      "email" : "(required, string) Email address of the user"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+  {% endapi %}
+
+{% api %}
+
+## Email open events
+
+{% apitags %}
+Email, Opens
+{% endapitags %}
+
+This event occurs when a user opens an email. Multiple events may be generated for the same campaign if a user opens the email multiple times.
+
+{% alert important %}
+It's known behavior that the email open event fields `device_model` and `mailbox_provider` are empty. You can ignore these for now.
+{% endalert %}
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Email Open: users.messages.email.Open
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "device_os" : "(optional, string) Device operating system extracted from user_agent",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+    "machine_open" : "(optional, string) Populated to 'true' if the open event is triggered without user engagement, for example by an Apple device with Mail Privacy Protection enabled. Value may change over time to provide more granularity.",
+    "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Email Open: users.messages.email.Open
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+  "device_model" : "(optional, string) Model of the device",
+  "device_os" : "(optional, string) Device operating system extracted from user_agent",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "email_address" : "(required, string) Email address of the user",
+  "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_domain" : "(optional, string) Sending domain for the email",
+  "id" : "(required, string) Globally unique ID for this event",
+  "ip_pool" : "(optional, string) IP pool from which the email send was made",
+  "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+  "machine_open" : "(optional, string) Populated to 'true' if the open event is triggered without user engagement, for example by an Apple device with Mail Privacy Protection enabled. Value may change over time to provide more granularity.",
+  "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_agent" : "(optional, string) User agent on which the spam report occurred",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Email Open: users.messages.email.Open
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "device_model" : "(optional, string) Model of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "device_os" : "(optional, string) Device operating system extracted from user_agent",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+          "from_domain" : "(optional, string) Sending domain for the email",
+          "ip_pool" : "(optional, string) IP pool from which the email send was made",
+          "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+          "machine_open" : "(optional, string) Populated to 'true' if the open event is triggered without user engagement, for example by an Apple device with Mail Privacy Protection enabled. Value may change over time to provide more granularity.",
+          "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "user_agent" : "(optional, string) User agent on which the spam report occurred"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(required, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Email Open: users.messages.email.Open
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+    "device_model" : "(optional, string) Model of the device",
+    "device_os" : "(optional, string) Device operating system extracted from user_agent",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+    "machine_open" : "(optional, string) Populated to 'true' if the open event is triggered without user engagement, for example by an Apple device with Mail Privacy Protection enabled. Value may change over time to provide more granularity.",
+    "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Email Open: users.messages.email.Open
+
+{
+  "context" : {
+    "traits" : {
+      "email" : "(required, string) Email address of the user"
+    },
+    "device" : {
+      "model" : "(optional, string) Model of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "device_os" : "(optional, string) Device operating system extracted from user_agent",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+    "machine_open" : "(optional, string) Populated to 'true' if the open event is triggered without user engagement, for example by an Apple device with Mail Privacy Protection enabled. Value may change over time to provide more granularity.",
+    "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+  {% endapi %}
+
+{% api %}
+
+## Email clicks events
+
+{% apitags %}
+Email, Clicks
+{% endapitags %}
+
+This event occurs when a user clicks an email. Multiple events may be generated for the same campaign if a user clicks multiple times or clicks different links within the email.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Email Click: users.messages.email.Click
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "device_os" : "(optional, string) Device operating system extracted from user_agent",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+    "link_alias" : "(optional, string) Alias associated with this link ID",
+    "link_id" : "(optional, string) Unique ID for the link which was clicked, as created by Braze",
+    "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token",
+    "url" : "(optional, string) URL that the user clicked on",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Email Click: users.messages.email.Click
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+  "device_model" : "(optional, string) Model of the device",
+  "device_os" : "(optional, string) Device operating system extracted from user_agent",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "email_address" : "(required, string) Email address of the user",
+  "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_domain" : "(optional, string) Sending domain for the email",
+  "id" : "(required, string) Globally unique ID for this event",
+  "ip_pool" : "(optional, string) IP pool from which the email send was made",
+  "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+  "link_alias" : "(optional, string) Alias associated with this link ID",
+  "link_id" : "(optional, string) Unique ID for the link which was clicked, as created by Braze",
+  "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "url" : "(optional, string) URL that the user clicked on",
+  "user_agent" : "(optional, string) User agent on which the spam report occurred",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Email Click: users.messages.email.Click
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "device_model" : "(optional, string) Model of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "device_os" : "(optional, string) Device operating system extracted from user_agent",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+          "from_domain" : "(optional, string) Sending domain for the email",
+          "ip_pool" : "(optional, string) IP pool from which the email send was made",
+          "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+          "link_alias" : "(optional, string) Alias associated with this link ID",
+          "link_id" : "(optional, string) Unique ID for the link which was clicked, as created by Braze",
+          "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "url" : "(optional, string) URL that the user clicked on",
+          "user_agent" : "(optional, string) User agent on which the spam report occurred"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(required, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Email Click: users.messages.email.Click
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+    "device_model" : "(optional, string) Model of the device",
+    "device_os" : "(optional, string) Device operating system extracted from user_agent",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+    "link_alias" : "(optional, string) Alias associated with this link ID",
+    "link_id" : "(optional, string) Unique ID for the link which was clicked, as created by Braze",
+    "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "url" : "(optional, string) URL that the user clicked on",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Email Click: users.messages.email.Click
+
+{
+  "context" : {
+    "traits" : {
+      "email" : "(required, string) Email address of the user"
+    },
+    "device" : {
+      "model" : "(optional, string) Model of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "browser" : "(optional, string) Device browser - extracted from user_agent - on which the open occurred",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_class" : "(optional, string) Device class extracted from user_agent (mobile, desktop, tablet, etc...)",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "device_os" : "(optional, string) Device operating system extracted from user_agent",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "is_amp" : "(optional, boolean) Indicates that this is an AMP event",
+    "link_alias" : "(optional, string) Alias associated with this link ID",
+    "link_id" : "(optional, string) Unique ID for the link which was clicked, as created by Braze",
+    "mailbox_provider" : "(optional, string) Mailbox provider value returned by the esp for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "url" : "(optional, string) URL that the user clicked on",
+    "link_url" : "(optional, string) URL that the user clicked on",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+  {% endapi %}
+
+{% api %}
+
+## Email bounce event
+
+{% apitags %}
+Email, Bounce
+{% endapitags %}
+
+This event occurs when an Internet Service Provider returns a hard bounce. A hard bounce signifies a permanent deliverability failure.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Email Bounce: users.messages.email.Bounce
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "is_drop" : "(optional, boolean) Indicates that this event counts as a drop event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Email Bounce: users.messages.email.Bounce
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "email_address" : "(required, string) Email address of the user",
+  "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_domain" : "(optional, string) Sending domain for the email",
+  "id" : "(required, string) Globally unique ID for this event",
+  "ip_pool" : "(optional, string) IP pool from which the email send was made",
+  "is_drop" : "(optional, boolean) Indicates that this event counts as a drop event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "sending_ip" : "(optional, string) IP address from which the email send was made",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Email Bounce: users.messages.email.Bounce
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+          "from_domain" : "(optional, string) Sending domain for the email",
+          "ip_pool" : "(optional, string) IP pool from which the email send was made",
+          "is_drop" : "(optional, boolean) Indicates that this event counts as a drop event",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(required, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Email Bounce: users.messages.email.Bounce
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "is_drop" : "(optional, boolean) Indicates that this event counts as a drop event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Email Bounce: users.messages.email.Bounce
+
+{
+  "context" : {
+    "traits" : {
+      "email" : "(required, string) Email address of the user"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "is_drop" : "(optional, boolean) Indicates that this event counts as a drop event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+  {% endapi %}
+
+{% api %}
+
+## Email soft bounce event
+
+{% apitags %}
+Email, Bounce
+{% endapitags %}
+
+This event occurs when an Internet Service Provider returns a soft bounce. A soft bounce signifies that an email could not be delivered because of a temporary deliverability failure.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Email Soft Bounce: users.messages.email.SoftBounce
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Email Soft Bounce: users.messages.email.SoftBounce
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "email_address" : "(required, string) Email address of the user",
+  "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_domain" : "(optional, string) Sending domain for the email",
+  "id" : "(required, string) Globally unique ID for this event",
+  "ip_pool" : "(optional, string) IP pool from which the email send was made",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "sending_ip" : "(optional, string) IP address from which the email send was made",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Email Soft Bounce: users.messages.email.SoftBounce
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+          "from_domain" : "(optional, string) Sending domain for the email",
+          "ip_pool" : "(optional, string) IP pool from which the email send was made",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(required, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Email Soft Bounce: users.messages.email.SoftBounce
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Email Soft Bounce: users.messages.email.SoftBounce
+
+{
+  "context" : {
+    "traits" : {
+      "email" : "(required, string) Email address of the user"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "bounce_reason" : "(optional, string) The SMTP reason code and user friendly message received for this bounce event",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+  {% endapi %}
+
+{% api %}
+
+## Email spam events
+
+{% apitags %}
+Email, Spam
+{% endapitags %}
+
+This event occurs when the end-user hits the "spam" button on the email. Note that this does not represent the fact the email went into the spam folder as Braze does not track this.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Email Mark As Spam: users.messages.email.MarkAsSpam
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Email Mark As Spam: users.messages.email.MarkAsSpam
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "email_address" : "(required, string) Email address of the user",
+  "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_domain" : "(optional, string) Sending domain for the email",
+  "id" : "(required, string) Globally unique ID for this event",
+  "ip_pool" : "(optional, string) IP pool from which the email send was made",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_agent" : "(optional, string) User agent on which the spam report occurred",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Email Mark As Spam: users.messages.email.MarkAsSpam
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+          "from_domain" : "(optional, string) Sending domain for the email",
+          "ip_pool" : "(optional, string) IP pool from which the email send was made",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "user_agent" : "(optional, string) User agent on which the spam report occurred"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(required, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Email Mark As Spam: users.messages.email.MarkAsSpam
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Email Mark As Spam: users.messages.email.MarkAsSpam
+
+{
+  "context" : {
+    "traits" : {
+      "email" : "(required, string) Email address of the user"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "esp" : "(optional, string) ESP related to the event (Sparkpost or Sendgrid)",
+    "from_domain" : "(optional, string) Sending domain for the email",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+{% endapi %}
+
+
+{% api %}
+
+## Email unsubscribe events
+
+{% apitags %}
+Email, Subscription
+{% endapitags %}
+
+This event occurs when the end-user has clicked "unsubscribe" from the email.
+
+{% alert important %}
+The `Unsubscribe` event is actually a specialized click event that is fired when your user clicks on the unsubscribe link in the email (either a normal unsubscribe link within the email body or footer, or using the [list-unsubscribe header]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/email_settings#include-a-list-unsubscribe-header)), not when the user changes state to unsubscribed. If subscription state change is sent through the API, or via custom (non-Braze) unsubscription link, it will not trigger an event on Currents.
+{% endalert %}
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Email Unsubscribe: users.messages.email.Unsubscribe
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Email Unsubscribe: users.messages.email.Unsubscribe
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "email_address" : "(required, string) Email address of the user",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "ip_pool" : "(optional, string) IP pool from which the email send was made",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Email Unsubscribe: users.messages.email.Unsubscribe
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "ip_pool" : "(optional, string) IP pool from which the email send was made",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(required, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Email Unsubscribe: users.messages.email.Unsubscribe
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "email_address" : "(required, string) Email address of the user",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Email Unsubscribe: users.messages.email.Unsubscribe
+
+{
+  "context" : {
+    "traits" : {
+      "email" : "(required, string) Email address of the user"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "ip_pool" : "(optional, string) IP pool from which the email send was made",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+The behavior for `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps (except for entry steps, which can be scheduled) as triggered events, even when they are scheduled. Learn more about [dispatch ID behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+{% endapi %}
+
+{% api %}
+
+## In-app message impression events
+
+{% apitags %}
+In-App Messages, Impressions
+{% endapitags %}
+
+This event occurs when a user views an in-app message.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// In-App Message Impression: users.messages.inappmessage.Impression
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(optional, string) API ID of the card",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// In-App Message Impression: users.messages.inappmessage.Impression
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "card_id" : "(optional, string) API ID of the card",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// In-App Message Impression: users.messages.inappmessage.Impression
+
+{
+  "device_info" : {
+    "ios_advertising_id" : "(optional, string) Advertising identifier",
+    "android_advertising_id" : "(optional, string) Advertising identifier",
+    "microsoft_advertising_id" : "(optional, string) Advertising identifier",
+    "roku_advertising_id" : "(optional, string) Advertising identifier",
+    "limit_ad_tracking" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "device_model" : "(optional, string) Model of the device",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "card_id" : "(optional, string) API ID of the card",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// In-App Message Impression: users.messages.inappmessage.Impression
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(optional, string) API ID of the card",
+    "device_model" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// In-App Message Impression: users.messages.inappmessage.Impression
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "model" : "(optional, string) Model of the device",
+      "type" : "(optional, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(optional, string) API ID of the card",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+{% alert note %}
+The `message_extras` field will be active on April 4, 2024.
+{% endalert %}
+
+#### Property details
+
+- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
+- If you're using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+  {% endapi %}
+
+{% api %}
+
+## In-app message click events
+
+{% apitags %}
+In-App Messages, Clicks
+{% endapitags %}
+
+This event occurs when a user clicks on an in-app message.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// In-App Message Click: users.messages.inappmessage.Click
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "button_id" : "(optional, string) ID of the button clicked, if this click represents a click on a button",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(optional, string) API ID of the card",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// In-App Message Click: users.messages.inappmessage.Click
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "button_id" : "(optional, string) ID of the button clicked, if this click represents a click on a button",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "card_id" : "(optional, string) API ID of the card",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// In-App Message Click: users.messages.inappmessage.Click
+
+{
+  "device_info" : {
+    "ios_advertising_id" : "(optional, string) Advertising identifier",
+    "android_advertising_id" : "(optional, string) Advertising identifier",
+    "microsoft_advertising_id" : "(optional, string) Advertising identifier",
+    "roku_advertising_id" : "(optional, string) Advertising identifier",
+    "limit_ad_tracking" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "device_model" : "(optional, string) Model of the device",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "button_id" : "(optional, string) ID of the button clicked, if this click represents a click on a button",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "card_id" : "(optional, string) API ID of the card",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// In-App Message Click: users.messages.inappmessage.Click
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "button_id" : "(optional, string) ID of the button clicked, if this click represents a click on a button",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(optional, string) API ID of the card",
+    "device_model" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// In-App Message Click: users.messages.inappmessage.Click
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "model" : "(optional, string) Model of the device",
+      "type" : "(optional, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "button_id" : "(optional, string) ID of the button clicked, if this click represents a click on a button",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(optional, string) API ID of the card",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
+- If you're using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+  {% endapi %}
+
+
+{% api %}
+
+## Webhook send events
+
+{% apitags %}
+Webhooks, Sends
+{% endapitags %}
+
+This event occurs when a webhook was processed and sent to the third party specified in that webhook. Note that this does not signify whether or not the request was received.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Webhook Send: users.messages.webhook.Send
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Webhook Send: users.messages.webhook.Send
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Webhook Send: users.messages.webhook.Send
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Webhook Send: users.messages.webhook.Send
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Webhook Send: users.messages.webhook.Send
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
+
+{% endapi %}
+
+{% api %}
+## Content Card send events
+
+{% apitags %}
+Content Cards, Sends
+{% endapitags %}
+
+This event occurs when a Content Card gets sent to a user.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Content Card Send: users.messages.contentcard.Send
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Content Card Send: users.messages.contentcard.Send
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "content_card_id" : "(required, string) ID of the card that generated this event",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Content Card Send: users.messages.contentcard.Send
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "card_id" : "(required, string) ID of the card that generated this event",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Content Card Send: users.messages.contentcard.Send
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Content Card Send: users.messages.contentcard.Send
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
+  {% endapi %}
+
+{% api %}
+## Content Card impression events
+
+{% apitags %}
 Content Cards, Impressions
 {% endapitags %}
 
-This event occurs when a user views a Content Card.
+This event occurs when a user views a Content Card.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Content Card Impression: users.messages.contentcard.Impression
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Content Card Impression: users.messages.contentcard.Impression
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "content_card_id" : "(required, string) ID of the card that generated this event",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Content Card Impression: users.messages.contentcard.Impression
+
+{
+  "device_info" : {
+    "ios_advertising_id" : "(optional, string) Advertising identifier",
+    "android_advertising_id" : "(optional, string) Advertising identifier",
+    "microsoft_advertising_id" : "(optional, string) Advertising identifier",
+    "roku_advertising_id" : "(optional, string) Advertising identifier",
+    "limit_ad_tracking" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "device_model" : "(optional, string) Model of the device",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "card_id" : "(required, string) ID of the card that generated this event",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Content Card Impression: users.messages.contentcard.Impression
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_model" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Content Card Impression: users.messages.contentcard.Impression
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "model" : "(optional, string) Model of the device",
+      "type" : "(optional, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
+- If you're using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+  {% endapi %}
+
+{% api %}
+## Content Card click events
+
+{% apitags %}
+Content Cards, Clicks
+{% endapitags %}
+
+This event occurs when a user clicks a Content Card.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Content Card Click: users.messages.contentcard.Click
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Content Card Click: users.messages.contentcard.Click
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "content_card_id" : "(required, string) ID of the card that generated this event",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Content Card Click: users.messages.contentcard.Click
+
+{
+  "device_info" : {
+    "ios_advertising_id" : "(optional, string) Advertising identifier",
+    "android_advertising_id" : "(optional, string) Advertising identifier",
+    "microsoft_advertising_id" : "(optional, string) Advertising identifier",
+    "roku_advertising_id" : "(optional, string) Advertising identifier",
+    "limit_ad_tracking" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "device_model" : "(optional, string) Model of the device",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "card_id" : "(required, string) ID of the card that generated this event",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Content Card Click: users.messages.contentcard.Click
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_model" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Content Card Click: users.messages.contentcard.Click
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "model" : "(optional, string) Model of the device",
+      "type" : "(optional, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
+- If you're using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+  {% endapi %}
+
+
+{% api %}
+## Content Card dismissal events
+
+{% apitags %}
+Content Cards, Dismissal
+{% endapitags %}
+
+This event occurs when a user dismisses a Content Card.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Content Card Dismiss: users.messages.contentcard.Dismiss
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "$device" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "$os" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Content Card Dismiss: users.messages.contentcard.Dismiss
+
+{
+  "ad_id" : "(optional, string) Advertising identifier",
+  "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+  "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "content_card_id" : "(required, string) ID of the card that generated this event",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "device_model" : "(optional, string) Model of the device",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "os_version" : "(optional, string) Version of the operating system of the device",
+  "platform" : "(optional, string) Platform of the device",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Content Card Dismiss: users.messages.contentcard.Dismiss
+
+{
+  "device_info" : {
+    "ios_advertising_id" : "(optional, string) Advertising identifier",
+    "android_advertising_id" : "(optional, string) Advertising identifier",
+    "microsoft_advertising_id" : "(optional, string) Advertising identifier",
+    "roku_advertising_id" : "(optional, string) Advertising identifier",
+    "limit_ad_tracking" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred",
+    "device_model" : "(optional, string) Model of the device",
+    "platform" : "(optional, string) Platform of the device"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "card_id" : "(required, string) ID of the card that generated this event",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Content Card Dismiss: users.messages.contentcard.Dismiss
+
+{
+  "adid" : "(optional, string) Advertising identifier",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_model" : "(optional, string) Model of the device",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "os_version" : "(optional, string) Version of the operating system of the device",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "idfa" : "(optional, string) Advertising identifier",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Content Card Dismiss: users.messages.contentcard.Dismiss
+
+{
+  "context" : {
+    "traits" : { },
+    "device" : {
+      "model" : "(optional, string) Model of the device",
+      "type" : "(optional, string) Platform of the device"
+    }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "ad_id" : "(optional, string) Advertising identifier",
+    "ad_id_type" : "(optional, string) One of ['ios_idfa', 'google_ad_id', 'windows_ad_id', 'roku_ad_id']",
+    "ad_tracking_enabled" : "(optional, boolean) Whether advertising tracking is enabled for the device",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "card_id" : "(required, string) ID of the card that generated this event",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "platform" : "(optional, string) Platform of the device",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+#### Property details
+
+- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
+- If you're using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+  {% endapi %}
+
+
+{% api %}
+
+## SMS click events
+
+{% apitags %}
+SMS, Clicks
+{% endapitags %}
+
+This event occurs when a user clicks an SMS short link.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// SMS Short Link Click: users.messages.sms.ShortLinkClick
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "short_url" : "(required, string) Shortened url that was clicked",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token",
+    "url" : "(optional, string) URL that the user clicked on",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred",
+    "user_phone_number" : "(optional, string) The user's phone number from which the message was received"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// SMS Short Link Click: users.messages.sms.ShortLinkClick
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "short_url" : "(required, string) Shortened url that was clicked",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "url" : "(required, string) URL that the user clicked on",
+  "user_agent" : "(optional, string) User agent on which the spam report occurred",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event",
+  "user_phone_number" : "(optional, string) The user's phone number from which the message was received"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// SMS Short Link Click: users.messages.sms.ShortLinkClick
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "short_url" : "(required, string) Shortened url that was clicked",
+          "url" : "(optional, string) URL that the user clicked on",
+          "user_agent" : "(optional, string) User agent on which the spam report occurred"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) The user's phone number from which the message was received"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// SMS Short Link Click: users.messages.sms.ShortLinkClick
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "short_url" : "(required, string) Shortened url that was clicked",
+    "url" : "(optional, string) URL that the user clicked on",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred",
+    "user_phone_number" : "(optional, string) The user's phone number from which the message was received"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// SMS Short Link Click: users.messages.sms.ShortLinkClick
+
+{
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) The user's phone number from which the message was received"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "short_url" : "(required, string) Shortened url that was clicked",
+    "url" : "(optional, string) URL that the user clicked on",
+    "link_url" : "(optional, string) URL that the user clicked on",
+    "user_agent" : "(optional, string) User agent on which the spam report occurred"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+{% endapi %}
+{% api %}
+## SMS send events
+
+{% apitags %}
+SMS, Sends
+{% endapitags %}
+
+This event occurs when a user sends an SMS.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Content Card Impression: users.messages.contentcard.Impression
+// SMS Send: users.messages.sms.Send
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "category" : "(optional, string) Keyword category name, only populated for auto-reply messages: 'opt-in', 'opt-out', 'help', or custom value",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// SMS Send: users.messages.sms.Send
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "category" : "(optional, string) Keyword category name, only populated for auto-reply messages: 'opt-in', 'opt-out', 'help', or custom value",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// SMS Send: users.messages.sms.Send
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "category" : "(optional, string) Keyword category name, only populated for auto-reply messages: 'opt-in', 'opt-out', 'help', or custom value",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// SMS Send: users.messages.sms.Send
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "category" : "(optional, string) Keyword category name, only populated for auto-reply messages: 'opt-in', 'opt-out', 'help', or custom value",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// SMS Send: users.messages.sms.Send
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "content_card_id": (required, string) ID of the content card that was viewed/clicked/dismissed,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "category" : "(optional, string) Keyword category name, only populated for auto-reply messages: 'opt-in', 'opt-out', 'help', or custom value",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_extras" : "(optional, string) A JSON string of the tagged key-value pairs during liquid rendering",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
+
 #### Property details
-- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
-- If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+
+- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
+
 {% endapi %}
 
 {% api %}
-## Content Card click events
+
+## SMS sends to carrier events
 
 {% apitags %}
-Content Cards, Clicks
+SMS, Delivery
 {% endapitags %}
 
-This event occurs when a user clicks a Content Card.
+{% alert important %}
+`CarrierSend` is supported only for users on legacy infrastructure.
+{% endalert %}
+
+This event occurs when an SMS is sent to the carrier.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Content Card Click: users.messages.contentcard.Click
+// SMS Carrier Send: users.messages.sms.CarrierSend
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "content_card_id": (required, string) ID of the content card that was viewed/clicked/dismissed,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_name": (optional, string) name of the Canvas,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-#### Property details
-- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
-- If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// SMS Carrier Send: users.messages.sms.CarrierSend
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// SMS Carrier Send: users.messages.sms.CarrierSend
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// SMS Carrier Send: users.messages.sms.CarrierSend
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// SMS Carrier Send: users.messages.sms.CarrierSend
+
+{
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
 {% endapi %}
 
+{% api %}
+
+## SMS delivery events
+
+{% apitags %}
+SMS, Delivery
+{% endapitags %}
+
+This event occurs when an SMS was successfully delivered to the user's mobile phone.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// SMS Delivery: users.messages.sms.Delivery
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// SMS Delivery: users.messages.sms.Delivery
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// SMS Delivery: users.messages.sms.Delivery
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// SMS Delivery: users.messages.sms.Delivery
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// SMS Delivery: users.messages.sms.Delivery
+
+{
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+{% endapi %}
 
 {% api %}
-## Content Card dismissal events
+
+## SMS rejection events
 
 {% apitags %}
-Content Cards, Dismissal
+SMS, Rejection
 {% endapitags %}
 
-This event occurs when a user dismisses a Content Card.
+This event occurs when an SMS send gets rejected by the carrier, this can happen for several reasons. Use this event and the provided error codes to help troubleshoot issues with SMS delivery.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// SMS Rejection: users.messages.sms.Rejection
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "error" : "(optional, string) Error name",
+    "distinct_id" : "(required, string) External ID of the user",
+    "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "provider_error_code" : "(optional, string) Error code from WhatsApp",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// SMS Rejection: users.messages.sms.Rejection
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "error" : "(optional, string) Error name",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "provider_error_code" : "(optional, string) Error code from WhatsApp",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// SMS Rejection: users.messages.sms.Rejection
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "error" : "(optional, string) Error name",
+          "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "provider_error_code" : "(optional, string) Error code from WhatsApp",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// SMS Rejection: users.messages.sms.Rejection
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "error" : "(optional, string) Error name",
+    "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "provider_error_code" : "(optional, string) Error code from WhatsApp",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// SMS Rejection: users.messages.sms.Rejection
+
+{
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "error" : "(optional, string) Error name",
+    "from_phone_number" : "(optional, string) Phone number used to send in e.164 format (for example +14155552671)",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "provider_error_code" : "(optional, string) Error code from WhatsApp",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+{% endapi %}
+
+
+{% api %}
+
+## SMS delivery failure events
+
+{% apitags %}
+SMS, Delivery
+{% endapitags %}
+
+This event occurs when an SMS experiences delivery failure. Use this event and the provided error codes to help troubleshoot issues with SMS delivery.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// SMS Delivery Failure: users.messages.sms.DeliveryFailure
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "error" : "(optional, string) Error name",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "provider_error_code" : "(optional, string) Error code from WhatsApp",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// SMS Delivery Failure: users.messages.sms.DeliveryFailure
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "error" : "(optional, string) Error name",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "provider_error_code" : "(optional, string) Error code from WhatsApp",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "subscription_group_id" : "(optional, string) Subscription group API ID",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// SMS Delivery Failure: users.messages.sms.DeliveryFailure
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "error" : "(optional, string) Error name",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "provider_error_code" : "(optional, string) Error code from WhatsApp",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// SMS Delivery Failure: users.messages.sms.DeliveryFailure
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "error" : "(optional, string) Error name",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "provider_error_code" : "(optional, string) Error code from WhatsApp",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "to_phone_number" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// SMS Delivery Failure: users.messages.sms.DeliveryFailure
+
+{
+  "context" : {
+    "traits" : {
+      "phone" : "(optional, string) Phone number of the user receiving the message in e.164 format (for example +14155552671)"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "error" : "(optional, string) Error name",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "provider_error_code" : "(optional, string) Error code from WhatsApp",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
+}
+```
+{% endtab %}
+{% endtabs %}
+
+{% endapi %}
+{% api %}
+
+## SMS inbound received events
+
+{% apitags %}
+SMS, InboundReceived
+{% endapitags %}
+
+This event occurs when one of your users sends an SMS to a phone number in one of your Braze SMS subscription groups.
+
+When Braze receives an inbound SMS, we attribute that inbound message to any user that shares that phone number. As a result, you may receive multiple events per inbound message if multiple users in your Braze instance share the same phone number. If you require attribution of specific user IDs based on previous messages sent to that user, you can use the SMS Delivered event to attribute Inbound Received events to the user ID who most recently received a message from your Braze number.
+
+If we detect that this inbound message is a reply to an outbound campaign or Canvas component sent from Braze, we will also include the campaign or Canvas metadata with the event. Braze defines a reply as an inbound message coming within four hours of an outbound message. However, there is a one-minute cache for the attributed campaign information of the last outbound SMS received.
+
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// SMS Inbound Received: users.messages.sms.InboundReceive
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+    "media_urls" : "(optional, array of string) Media URLs from the user",
+    "message_body" : "(optional, string) Typed response from the user",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token",
+    "user_phone_number" : "(required, string) The user's phone number from which the message was received"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// SMS Inbound Received: users.messages.sms.InboundReceive
+
+{
+  "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+  "app_group_id" : "(required, string) API ID of the app group this user belongs to",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+  "media_urls" : "(optional, array of string) Media URLs from the user",
+  "message_body" : "(required, string) Typed response from the user",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "subscription_group_id" : "(optional, string) BSON ID of subscription group",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) Braze user ID of the user who performed this event",
+  "user_phone_number" : "(required, string) The user's phone number from which the message was received"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// SMS Inbound Received: users.messages.sms.InboundReceive
+
+{
+  "device_info" : { },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+          "message_body" : "(optional, string) Typed response from the user",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "subscription_group_id" : "(optional, string) Subscription group API ID"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : {
+    "$mobile" : "(required, string) The user's phone number from which the message was received"
+  },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// SMS Inbound Received: users.messages.sms.InboundReceive
+
+{
+  "event_properties" : {
+    "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+    "media_urls" : "(optional, array of string) Media URLs from the user",
+    "message_body" : "(optional, string) Typed response from the user",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID",
+    "user_phone_number" : "(required, string) The user's phone number from which the message was received"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// Content Card Dismiss: users.messages.contentcard.Dismiss
+// SMS Inbound Received: users.messages.sms.InboundReceive
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "content_card_id": (required, string) ID of the content card that was viewed/clicked/dismissed,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "dispatch_id": (optional, string) ID of the dispatch this message belongs to,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,  
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "canvas_name": (optional, string) name of the Canvas,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "device_id": (optional, string) ID of the device on which the event occurred,
-  "platform": (optional, string) platform of the device (one of 'ios', 'android', 'web', 'kindle', 'tvos', OR 'roku'),
-  "os_version": (optional, string) os version of device used for the action,
-  "device_model": (optional, string) hardware model of the device,
-  "ad_id": (optional, string) advertising identifier,
-  "ad_id_type": (optional, string) One of 'ios_idfa', 'google_ad_id', OR 'roku_ad_id',
-  "ad_tracking_enabled": (optional, boolean) whether advertising tracking is enabled for the device
+  "context" : {
+    "traits" : {
+      "phone" : "(required, string) The user's phone number from which the message was received"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "action" : "(required, string) Action taken in response to this message. (for example Subscribed, Unsubscribed or None).",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "inbound_phone_number" : "(required, string) The inbound number that the message was sent to",
+    "media_urls" : "(optional, array of string) Media URLs from the user",
+    "message_body" : "(optional, string) Typed response from the user",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "subscription_group_id" : "(optional, string) Subscription group API ID"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
-#### Property details
-- For `ad_id`, `ad_id_type` and `ad_tracking_enabled`, you need to explicitly collect the iOS IDFA and Android Google advertising ID through the native SDKs. Learn more about this setup for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id).
-- If you are using Kafka to ingest [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) data, contact your customer success manager to enable sending `ad_id`.
-{% endapi %}
+{% endtab %}
+{% endtabs %}
 
+{% endapi %}
 
 {% api %}
 
-## SMS click events
+## Feature flags impression events
 
 {% apitags %}
-SMS, Clicks
+FeatureFlags, Impression
 {% endapitags %}
 
-This event occurs when a user clicks an SMS short link. We only generate and send this event to Currents or Snowflake data sharing when a user clicks an SMS short link sent from a campaign where advanced [link shortening]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/) is enabled.
-
-```json
-// SMS Send: users.messages.sms.ShortLinkClick
-{
-  "id": (required, string) unique ID of this event,
-  "user_id": (required, string) Braze user ID of the user targeted by short_url,
-  "external_user_id": (optional, string) External ID of the user, null if short_url,
-  "app_group_id": (required, string) API ID of the workspace associated with the inbound phone number,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA timezone of the user at the time of the event, null if short_url did not use user click tracking,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign if from a campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas if from a Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation a user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "url": (required, string) original URL contained in message that was shortened for click tracking,
-  "short_url": (required, string) shortened URL that is sent to user for click tracking,
-  "user_agent": (optional, string) User-Agent header of the device performing the click event,
-  "user_phone_number": (optional, string) Phone number of the user that short_url was sent to
-}
-```
-{% endapi %}
-{% api %}
-## SMS send events
+This event occures whenever a user has had an opportunity to interact with your feature, or when they could have interacted if the feature is disabled (in the case of a control group in an A/B test).
 
-{% apitags %}
-SMS, Sends
-{% endapitags %}
+Feature flag impressions are only logged once per session.
 
-This event occurs when a user sends an SMS.
 
-```json
-// SMS Send: users.messages.sms.Send
-{
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform and users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "subscription_group_id": (optional, string) ID of the subscription group targeted for this SMS message,
-  "to_phone_number": (optional, string) the number the message was sent to,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) message send ID this message belongs to,
-  "category": (optional, string) If the SMS was sent as a result of auto-response to one of your global SMS keywords, the Category will be reflected here (e.g Opt-In, Opt-Out, Help)
-  "message_extras": (optional, string) key-value pairs sent with this event
-}
-```
-#### Property details
-- `message_extras` allow you to annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. Refer to [Message extras]({{site.baseurl}}/message_extras_tag/) to learn more.
 
 {% endapi %}
 
 {% api %}
 
-## SMS sends to carrier events
+## Campaign conversion events
 
 {% apitags %}
-SMS, Delivery
+Campaign, Conversion
 {% endapitags %}
 
+This event occurs when a user does an action that has been set as a conversion event in a campaign.
+
 {% alert important %}
-`CarrierSend` is supported only for users on legacy infrastructure.
+Note that the conversion event is encoded in the `conversion_behavior` field, which includes the type of conversion event, the window (timeframe), and additional information depending on the conversion event type. The `conversion_behavior_index` field represents which conversion event, such as 0 = A, 1 = B, 2 = C, 3 = D.
 {% endalert %}
 
-This event occurs when an SMS is sent to the carrier.
-
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// SMS Delivery: users.messages.sms.CarrierSend
-{
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform and users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "to_phone_number": (optional, string) the number the message was sent to,
-  "subscription_group_id": (optional, string) ID of the subscription group targeted for this SMS message,
-  "from_phone_number": (optional, string) the from phone number of the message (Delivered and Undelivered only),
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) message send ID this message belongs to (SMS Sends events only)
+// Campaign Conversion: users.campaigns.Conversion
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+    "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-{% endapi %}
-
-{% api %}
-
-## SMS delivery events
-
-{% apitags %}
-SMS, Delivery
-{% endapitags %}
-
-This event occurs when an SMS was successfully delivered to the user's mobile phone.
+{% endtab %}
 
+{% tab Cloud Storage %}
 ```json
-// SMS Delivery: users.messages.sms.Delivery
+// Campaign Conversion: users.campaigns.Conversion
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform and users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "to_phone_number": (optional, string) the number the message was sent to,
-  "subscription_group_id": (optional, string) ID of the subscription group targeted for this SMS message,
-  "from_phone_number": (optional, string) the from phone number of the message (Delivered and Undelivered only),
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) message send ID this message belongs to (SMS Sends events only)
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(optional, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(required, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+  "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
 }
 ```
-{% endapi %}
+{% endtab %}
 
-{% api %}
+{% tab mParticle %}
+```json
+// Campaign Conversion: users.campaigns.Conversion
 
-## SMS rejection events
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+          "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
-{% apitags %}
-SMS, Rejection
-{% endapitags %}
+{% tab Amplitude %}
+```json
+// Campaign Conversion: users.campaigns.Conversion
 
-This event occurs when an SMS send gets rejected by the carrier, this can happen for several reasons. Use this event and the provided error codes to help troubleshoot issues with SMS delivery.
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+    "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// SMS Rejection: users.messages.sms.Rejection
+// Campaign Conversion: users.campaigns.Conversion
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform and users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "to_phone_number": (optional, string) the number the message was sent to,
-  "subscription_group_id": (optional, string) ID of the subscription group targeted for this SMS message,
-  "from_phone_number": (optional, string) the from phone number of the message (Delivered and Undelivered only),
-  "error": (optional, string) the Braze provided error (Rejection and Delivery Failure events only),
-  "provider_error_code": (optional, string) the provider's reason code as to why the message was not sent (Rejection and Delivery Failure events only),
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) message send ID this message belongs to (SMS Sends events only)
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+    "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
+
 {% endapi %}
 
 
 {% api %}
 
-## SMS delivery failure events
+## Canvas conversion events
 
 {% apitags %}
-SMS, Delivery
+Canvas, Conversion
 {% endapitags %}
 
-This event occurs when an SMS experiences delivery failure. Use this event and the provided error codes to help troubleshoot issues with SMS delivery.
+This event occurs when a user does an action that has been set as a conversion event in Canvas.
+
+{% alert important %}
+Note that the conversion event is encoded in the `conversion_behavior` field, which includes the type of conversion event, the window (timeframe), and additional information depending on the conversion event type. The `conversion_behavior_index` field represents which conversion event, such as 0 = A, 1 = B, 2 = C, 3 = D.
+{% endalert %}
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// SMS Delivery Failure: users.messages.sms.DeliveryFailure
+// Canvas Conversion: users.canvas.Conversion
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "dispatch_id": (optional, string) ID of the message dispatch (unique ID for each 'transmission' sent from the Braze platform and users who are sent a schedule message get the same dispatch_id. Action-based or API-triggered messages get a unique dispatch_id per user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,  
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "to_phone_number": (optional, string) the number the message was sent to,
-  "subscription_group_id": (optional, string) ID of the subscription group targeted for this SMS message,
-  "error": (optional, string) the Braze provided error (Rejection and Delivery Failure events only),
-  "provider_error_code": (optional, string) the provider's reason code as to why the message was not sent (Rejection and Delivery Failure events only),
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) message send ID this message belongs to (SMS Sends events only)
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+    "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-{% endapi %}
-{% api %}
+{% endtab %}
 
-## SMS inbound received events
+{% tab Cloud Storage %}
+```json
+// Canvas Conversion: users.canvas.Conversion
 
-{% apitags %}
-SMS, InboundReceived
-{% endapitags %}
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(optional, string) API ID of the app on which this event occurred",
+  "canvas_id" : "(required, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(required, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+  "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-This event occurs when one of your users sends an SMS to a phone number in one of your Braze SMS subscription groups. 
+{% tab mParticle %}
+```json
+// Canvas Conversion: users.canvas.Conversion
 
-When Braze receives an inbound SMS, we attribute that inbound message to any user that shares that phone number. As a result, you may receive multiple events per inbound message if multiple users in your Braze instance share the same phone number. If you require attribution of specific user IDs based on previous messages sent to that user, you can use the SMS Delivered event to attribute Inbound Received events to the user ID who most recently received a message from your Braze number.
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+          "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+          "device_id" : "(optional, string) ID of the device on which the event occurred"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
-If we detect that this inbound message is a reply to an outbound campaign or Canvas component sent from Braze, we will also include the campaign or Canvas metadata with the event. Braze defines a reply as an inbound message coming within four hours of an outbound message. However, there is a one-minute cache for the attributed campaign information of the last outbound SMS received.
+{% tab Amplitude %}
+```json
+// Canvas Conversion: users.canvas.Conversion
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+    "conversion_behavior_index" : "(optional, int) Index of the conversion behavior"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// SMS Inbound Received: users.messages.sms.InboundReceive
+// Canvas Conversion: users.canvas.Conversion
+
 {
-  "id": (required, string) unique ID of this event,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "user_phone_number": (required, string) the phone number of the user who sent the message to your Braze number,
-  "subscription_group_id": (optional, string) ID of the subscription group which the phone number the user messaged belongs to,
-  "inbound_phone_number": (required, string) the phone number the message was sent to,
-  "action": (required, string) the subscription action Braze took as a result of this message (either `subscribed`, `unsubscribed` or `none` based on the message body. `None` indicates this inbound message did not match any of your keywords to opt-in or opt-out a user),
-  "message_body": (required, string) the body of the message sent by the user,
-  "media_urls": (optional, array of string) the media URLs sent by the user,
-  "campaign_id": (optional, string) ID of the campaign if Braze identifies this inbound message is a reply to a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if Braze identifies this inbound message is a reply to a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if Braze identifies this inbound message is a reply to a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "conversion_behavior" : "(optional, string) JSON-encoded string describing the conversion behavior",
+    "conversion_behavior_index" : "(optional, int) Index of the conversion behavior",
+    "device_id" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
+
 {% endapi %}
 
 
 {% api %}
 
-## Campaign conversion events
+## Canvas entry events
 
 {% apitags %}
-Campaign, Conversion
+Canvas, Entry
 {% endapitags %}
 
-This event occurs when a user does an action that has been set as a conversion event in a campaign.
-
-{% alert important %}
-Note that the conversion event is encoded in the `conversion_behavior` field, which includes the type of conversion event, the window (timeframe), and additional information depending on the conversion event type. The `conversion_behavior_index` field represents which conversion event, such as 0 = A, 1 = B, 2 = C, 3 = D.
-{% endalert %}
+This event occurs when a user enters into the Canvas. This event tells you which variant the user entered into.
 
+{% tabs %}
+{% tab Mixpanel %}
 ```json
-// Campaign Conversion Event: users.campaigns.Conversion
+// Canvas Entry: users.canvas.Entry
+
 {
-  "id": (required, string) unique ID of this event,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "app_id": (optional, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (required, string) ID of the campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (required, string) ID of the message variation,
-  "message_variation_name": (optional, string) the name of the message variation,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types)
-  "conversion_behavior_index": (optional, int) index of the conversion behavior,
-  "conversion_behavior": (optional, string) JSON-encoded string describing the conversion behavior
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
 }
 ```
-{% endapi %}
+{% endtab %}
 
+{% tab Cloud Storage %}
+```json
+// Canvas Entry: users.canvas.Entry
 
-{% api %}
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "canvas_id" : "(required, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(required, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
 
-## Canvas conversion events
+{% tab mParticle %}
+```json
+// Canvas Entry: users.canvas.Entry
 
-{% apitags %}
-Canvas, Conversion
-{% endapitags %}
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
 
-This event occurs when a user does an action that has been set as a conversion event in Canvas.
+{% tab Amplitude %}
+```json
+// Canvas Entry: users.canvas.Entry
 
-{% alert important %}
-Note that the conversion event is encoded in the `conversion_behavior` field, which includes the type of conversion event, the window (timeframe), and additional information depending on the conversion event type. The `conversion_behavior_index` field represents which conversion event, such as 0 = A, 1 = B, 2 = C, 3 = D.
-{% endalert %}
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
 
+{% tab Segment %}
 ```json
-// Canvas Conversion Event: users.canvas.Conversion
+// Canvas Entry: users.canvas.Entry
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_id": (optional, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "canvas_id": (required, string) ID of the Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (required, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (required, string) ID of the last step the user was sent before the conversion,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "conversion_behavior_index": (optional, int) index of the conversion behavior,
-  "conversion_behavior": (optional, string) JSON-encoded string describing the conversion behavior
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "in_control_group" : "(required, boolean) Whether the user was enrolled in the control group"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
-{% endapi %}
+{% endtab %}
+{% endtabs %}
 
+{% endapi %}
 
 {% api %}
 
-## Canvas entry events
+## Canvas step progression events
 
 {% apitags %}
-Canvas, Entry
+Canvas, StepProgression
 {% endapitags %}
 
-This event occurs when a user enters into the Canvas. This event tells you which variant the user entered into.
+This event occurs when a user progresses through a step in a Canvas with some outcome. Currently, only split steps – Audience Paths, Decision Split, Action Paths, Experiment – and Advance outcomes generate Step Progression events.
 
-```json
-// Canvas Entry Event: users.canvas.Entry
-{
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "canvas_id": (required, string) ID of the Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (required, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "in_control_group": (required, boolean) whether the user was enrolled in the control group for a Canvas
-}
-```
 
 {% endapi %}
 
@@ -1913,23 +8951,148 @@ Campaign, Entry
 
 This event occurs when a user is enrolled in a control variant set on a multi-variant campaign. This event is generated as there will be no channel send event for this user.
 
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Campaign Control Group Enrollment: users.campaigns.EnrollInControl
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Campaign Control Group Enrollment: users.campaigns.EnrollInControl
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(optional, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(required, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Campaign Control Group Enrollment: users.campaigns.EnrollInControl
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
 ```json
 // Campaign Control Group Enrollment: users.campaigns.EnrollInControl
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
+```json
+// Campaign Control Group Enrollment: users.campaigns.EnrollInControl
+
 {
-  "id": (required, string) unique ID of this event,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "app_id": (optional, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "campaign_id": (optional, string) ID of the campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation,
-  "message_variation_name": (optional, string) the name of the message variation,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types)
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "dispatch_id" : "(optional, string) ID of the dispatch this message belongs to",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
 {% endapi %}
 
@@ -1941,41 +9104,204 @@ This event occurs when a user is enrolled in a control variant set on a multi-va
 Subscription
 {% endapitags %}
 
-This event occurs when Braze receives a request to update the subscription state of the user, even if the request doesn’t alter the current subscription state for the user.
+This event occurs when the subscription state of a user in a subscription group changes.
 
 {% alert important %}
 Subscription groups are only available for email, SMS, and WhatsApp channels at this time.
 {% endalert %}
 
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Subscription Group State Change: users.behaviors.subscriptiongroup.StateChange
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "email_address" : "(optional, string) Email address of the user",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+    "subscription_group_id" : "(required, string) Subscription group API ID",
+    "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Subscription Group State Change: users.behaviors.subscriptiongroup.StateChange
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(optional, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "channel" : "(optional, string) Channel this event belongs to",
+  "email_address" : "(optional, string) Email address of the user",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "message_variation_name" : "(optional, string) Name of the message variation",
+  "phone_number" : "(optional, string) Phone number of the user in e.164 format (for example +14155552671)",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+  "subscription_group_id" : "(required, string) Subscription group API ID",
+  "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Subscription Group State Change: users.behaviors.subscriptiongroup.StateChange
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "device_id" : "(optional, string) ID of the device on which the event occurred",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+          "subscription_group_id" : "(required, string) Subscription group API ID",
+          "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(optional, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Subscription Group State Change: users.behaviors.subscriptiongroup.StateChange
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "email_address" : "(optional, string) Email address of the user",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+    "subscription_group_id" : "(required, string) Subscription group API ID",
+    "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'",
+    "timezone" : "(optional, string) Time zone of the user"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
 ```json
 // Subscription Group State Change: users.behaviors.subscriptiongroup.StateChange
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "email_address": (optional, string) email address for this user,
-  "phone_number": (optional, string) phone number of the user (presented in e.164 format),
-  "app_id": (optional, string) ID for the app on which the user action occurred,
-  "campaign_id": (optional, string) ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "message_variation_name": (optional, string) the name of the message variation if from a campaign,
-  "canvas_id": (optional, string) ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the step for this message if from a Canvas,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "subscription_group_id": (required, string) ID of the subscription group,
-  "subscription_status": (required, string) status of the subscription after the change: 'Subscribed', 'Unsubscribed', or 'Pending Double Opt-In',
-  "channel": (optional, string) either 'sms', 'email', or 'whats_app',
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch,
-  "timezone": (optional, string) IANA time zone of the user at the time of the event,
-  "send_id": (optional, string) ID of the message if specified for the campaign (See Send Identifier under API Identifier Types),
-  "state_change_source": (optional, string) Source of the state change, e.g: REST, SDK, Dashboard, Preference Center etc.
+  "context" : {
+    "traits" : {
+      "email" : "(optional, string) Email address of the user"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+    "subscription_group_id" : "(required, string) Subscription group API ID",
+    "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
 #### Property details
 
@@ -1993,8 +9319,7 @@ Subscription groups are only available for email, SMS, and WhatsApp channels at
 | Migration | When a user is updated by internal migrations or maintenance scripts |
 | User Merge | When a user is updated by the user merge process |
 | Canvas User Update Step | When a user is updated by the Canvas user update step |
-| List-Unsubscribe | When a user unsubscribes via Braze mailto or one-click list-unsubscribe header |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation"}
 
 {% endapi %}
 
@@ -2008,32 +9333,185 @@ Subscription
 
 This event occurs when Braze receives a request to update the global subscription state of the user, even if the request doesn't alter the current subscription state for the user.
 
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Global Subscription State Change: users.behaviors.subscription.GlobalStateChange
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "email_address" : "(optional, string) Email address of the user",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+    "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Global Subscription State Change: users.behaviors.subscription.GlobalStateChange
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(optional, string) API ID of the app on which this event occurred",
+  "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+  "campaign_name" : "(optional, string) Name of the campaign",
+  "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+  "canvas_name" : "(optional, string) Name of the Canvas",
+  "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+  "canvas_step_name" : "(optional, string) Name of the Canvas step",
+  "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+  "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+  "channel" : "(optional, string) Channel this event belongs to",
+  "email_address" : "(optional, string) Email address of the user",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+  "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+  "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+  "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "timezone" : "(optional, string) Time zone of the user",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Global Subscription State Change: users.behaviors.subscription.GlobalStateChange
+
+{
+  "device_info" : { },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+          "campaign_name" : "(optional, string) Name of the campaign",
+          "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+          "canvas_name" : "(optional, string) Name of the Canvas",
+          "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+          "canvas_step_name" : "(optional, string) Name of the Canvas step",
+          "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+          "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+          "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+          "message_variation_name" : "(optional, string) Name of the message variation",
+          "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+          "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+          "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'"
+        },
+        "custom_event_type" : "(required, string) The mParticle custom event type if the event_type is 'custom_event' (always 'other')",
+        "event_name" : "(required, string) The event type name, as it is exported to mParticle",
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "email" : "(optional, string) Email address of the user",
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Global Subscription State Change: users.behaviors.subscription.GlobalStateChange
+
+{
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "email_address" : "(optional, string) Email address of the user",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+    "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'",
+    "timezone" : "(optional, string) Time zone of the user"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
 ```json
-// Global State Change: users.behaviors.subscription.GlobalStateChange
-{
-  "id": (required, string) unique ID of this event,
-  "user_id": (required, string) Braze ID of the user with this global subscription state change,
-  "external_user_id": (optional, string) External ID of the user,
-  "email_address": (optional, string) User email address,
-  "state_change_source": (optional, string) Source of the state change, for example, REST, SDK, Dashboard, Preference Center, etc.,
-  "subscription_status": (required, string) Global subscription status: Subscribed, Unsubscribed and Opt-In,
-  "channel": (optional, string) Channel: only email for now,
-  "time": (required, int) 10-digit UTC time of the state change event in seconds since the epoch,
-  "timezone": (optional, string) IANA timezone of the user at the time of the event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "app_id": (optional, string) ID for the app on which the user action occurred,
-  "campaign_id": (optional, string) Braze ID of the campaign if from a campaign,
-  "campaign_name": (optional, string) name of the campaign,
-  "message_variation_id": (optional, string) ID of the message variation if from a campaign,
-  "canvas_id": (optional, string) Braze ID of the Canvas if from a Canvas,
-  "canvas_name": (optional, string) name of the Canvas,
-  "canvas_variation_id": (optional, string) ID of the Canvas variation the user is in if from a Canvas,
-  "canvas_variation_name": (optional, string) name of the Canvas variation the user is in if from a Canvas,
-  "canvas_step_id": (optional, string) ID of the Canvas step this event belongs to,
-  "canvas_step_name": (optional, string) name of the Canvas step this event belongs to,
-  "send_id": (optional, string) Message send ID this subscription state change action originated from
+// Global Subscription State Change: users.behaviors.subscription.GlobalStateChange
+
+{
+  "context" : {
+    "traits" : {
+      "email" : "(optional, string) Email address of the user"
+    },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "campaign_id" : "(optional, string) API ID of the campaign this event belongs to",
+    "campaign_name" : "(optional, string) Name of the campaign",
+    "canvas_id" : "(optional, string) API ID of the Canvas this event belongs to",
+    "canvas_name" : "(optional, string) Name of the Canvas",
+    "canvas_step_id" : "(optional, string) API ID of the Canvas step this event belongs to",
+    "canvas_step_name" : "(optional, string) Name of the Canvas step",
+    "canvas_variation_id" : "(optional, string) API ID of the Canvas variation this event belongs to",
+    "canvas_variation_name" : "(optional, string) Name of the Canvas variation this user received",
+    "message_variation_id" : "(optional, string) API ID of the message variation this user received",
+    "message_variation_name" : "(optional, string) Name of the message variation",
+    "send_id" : "(optional, string) Message send ID this message belongs to (SMS Sends events only)",
+    "state_change_source" : "(optional, string) Source of the state change, e.g: REST API, SDK, Dashboard, etc.",
+    "subscription_status" : "(required, string) Subscription status: 'Subscribed' or 'Unsubscribed'"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
 #### Property details
 
@@ -2051,7 +9529,7 @@ This event occurs when Braze receives a request to update the global subscriptio
 | Migration | When a user is updated by internal migrations or maintenance scripts |
 | User Merge | When a user is updated by the merging users process |
 | Canvas User Update Step | When a user is updated by the Canvas User Update step |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation"}
 
 {% endapi %}
 {% api %}
@@ -2067,17 +9545,116 @@ This event occurs when a user uninstalls an app. Use this data to track when use
 This event is not fired when the user actually uninstalls the app, as that's impossible to track exactly. Braze sends a daily silent push to determine if the app still exists on your user's device, and if we get an error on that silent push, it is assumed the app has been uninstalled.
 {% endalert %}
 
+{% tabs %}
+{% tab Mixpanel %}
+```json
+// Uninstall: users.behaviors.Uninstall
+
+{
+  "event" : "(required, string) The event type name, as it is exported to Mixpanel",
+  "properties" : {
+    "$partner_id" : "braze",
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_id" : "(optional, string) ID of the device on which the event occurred",
+    "distinct_id" : "(required, string) External ID of the user",
+    "$insert_id" : "(required, string) Globally unique ID for this event",
+    "time" : "(required, int) UNIX timestamp at which the event happened",
+    "token" : "(required, string) The Mixpanel API token"
+  }
+}
+```
+{% endtab %}
+
+{% tab Cloud Storage %}
+```json
+// Uninstall: users.behaviors.Uninstall
+
+{
+  "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+  "app_id" : "(required, string) API ID of the app on which this event occurred",
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "external_user_id" : "(optional, string) External ID of the user",
+  "id" : "(required, string) Globally unique ID for this event",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(required, string) Braze user ID of the user who performed this event"
+}
+```
+{% endtab %}
+
+{% tab mParticle %}
+```json
+// Uninstall: users.behaviors.Uninstall
+
+{
+  "device_info" : {
+    "ios_idfv" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "environment" : "(required, string) The mParticle environment (either 'development' or 'production')",
+  "events" : [
+    {
+      "data" : {
+        "custom_attributes" : {
+          "app_id" : "(optional, string) API ID of the app on which this event occurred",
+          "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+          "device_id" : "(optional, string) ID of the device on which the event occurred"
+        },
+        "source_message_id" : "(required, string) Globally unique ID for this event",
+        "timestamp_unixtime_ms" : "(required, int) UNIX timestamp at which the event happened"
+      },
+      "event_type" : "(required, string) mParticle event type (either 'uninstall' or 'custom_event')"
+    }
+  ],
+  "schema_version" : 2,
+  "user_attributes" : { },
+  "user_identities" : {
+    "customerid" : "(required, string) External ID of the user"
+  }
+}
+```
+{% endtab %}
+
+{% tab Amplitude %}
+```json
+// Uninstall: users.behaviors.Uninstall
+
+{
+  "device_id" : "(optional, string) ID of the device on which the event occurred",
+  "event_properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to"
+  },
+  "event_type" : "(required, string) The event type name, as it is exported to Amplitude",
+  "insert_id" : "(required, string) Globally unique ID for this event",
+  "library" : "Braze",
+  "time" : "(required, int) UNIX timestamp at which the event happened",
+  "user_id" : "(optional, string) External ID of the user"
+}
+```
+{% endtab %}
+
+{% tab Segment %}
 ```json
-// Uninstall Event: users.behaviors.Uninstall
+// Uninstall: users.behaviors.Uninstall
+
 {
-  "id": (required, string) unique ID of this event,
-  "app_group_id": (required, string) Braze ID of the workspace this user belongs to,
-  "user_id": (required, string) Braze user ID of the user,
-  "external_user_id": (optional, string) External ID of the user,
-  "device_id": (optional, string) ID of the device on which the session occurred,
-  "app_id": (required, string) ID for the app on which the user action occurred,
-  "time": (required, int) 10-digit UTC time of the event in seconds since the epoch
+  "context" : {
+    "traits" : { },
+    "device" : { }
+  },
+  "event" : "(required, string) The event type name, as it is exported to Segment",
+  "messageId" : "(required, string) Globally unique ID for this event",
+  "properties" : {
+    "app_id" : "(optional, string) API ID of the app on which this event occurred",
+    "app_group_id" : "(optional, string) API ID of the app group this user belongs to",
+    "device_id" : "(optional, string) ID of the device on which the event occurred"
+  },
+  "timestamp" : "(required, int) UNIX timestamp at which the event happened",
+  "type" : "track",
+  "userId" : "(required, string) External ID of the user"
 }
 ```
+{% endtab %}
+{% endtabs %}
 
 {% endapi %}
diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/setting_up_currents.md b/_docs/_user_guide/data_and_analytics/braze_currents/setting_up_currents.md
index f97b2300154..3cc881b9ccb 100644
--- a/_docs/_user_guide/data_and_analytics/braze_currents/setting_up_currents.md
+++ b/_docs/_user_guide/data_and_analytics/braze_currents/setting_up_currents.md
@@ -30,7 +30,7 @@ The following requirements are the basic, minimum requirements to integrate with
 | Partner API Key or Token | Usually the Partner's dashboard. | Just copy and paste it into the designated Braze field. | Braze has a designated field for this in the Integrations page for that Partner. We need this to map where we are sending your data. **It's important to keep your Partner Keys/Tokens up to date; invalid credentials may result in disabling your connector, and dropping events.**
 | Authentication Code/Key, Secret Key, Certification File | Contact a representative for your account with that Partner. May also exist in the Partner's dashboard. | Copy and paste keys into the designated Braze field. Generate and upload `.json` or other certification files into the appropriate place in Braze. | Braze has a designated field for this in the Integrations page for that Partner. This gives Braze credentials and authorizes us to write files to your Partner account. **It's important to keep your authentication details up to date; invalid credentials may result in disabling your connector, and dropping events.**
 | Bucket, Folder Path | Some partners organize and sort data by buckets. This should be found in the Partner's dashboard. | If this is required, be sure to copy the Bucket name or file path exactly into the designated space in Braze. We don't want your data to get lost! | Though this is required for some Partners, it's important to get right when you do need it. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert important %}
 It's important to keep your Partner Keys/Tokens and authentication details up to date; if your connector's credentials expire, the connector will stop sending events. If this persists for more than **48 hours**, the connector's events will be dropped and data will be permanently lost.
@@ -54,7 +54,7 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), you can fi
 
 ## Step 3: Add partner
 
-Add a partner, sometimes called a "Currents connector", by clicking the dropdown at the top of the screen.
+Add a partner, sometimes called a "Currents connector," by selecting the dropdown at the top of the screen.
 
 Each partner requires a different set of configuration steps. To enable each integration, refer to our list of [available partners]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/available_partners/) and follow the instructions in their respective pages.
 
diff --git a/_docs/_user_guide/data_and_analytics/cloud_ingestion/overview.md b/_docs/_user_guide/data_and_analytics/cloud_ingestion/overview.md
index 4dfc58bada9..d1a48990cdd 100644
--- a/_docs/_user_guide/data_and_analytics/cloud_ingestion/overview.md
+++ b/_docs/_user_guide/data_and_analytics/cloud_ingestion/overview.md
@@ -180,7 +180,7 @@ None of this has synced to Braze before, so add all of it to the source table fo
 | 2023-03-16 15:00:00 | 34567       | { "ATTRIBUTE_1": "234", "ATTRIBUTE_2":"blue", "ATTRIBUTE_3":"384", "ATTRIBUTE_4":"TRUE"}  |
 | 2023-03-16 15:00:00 | 45678       | { "ATTRIBUTE_1": "245", "ATTRIBUTE_2":"red", "ATTRIBUTE_3":"349", "ATTRIBUTE_4":"TRUE"}   |
 | 2023-03-16 15:00:00 | 56789       | { "ATTRIBUTE_1": "1938", "ATTRIBUTE_2":"red", "ATTRIBUTE_3":"813", "ATTRIBUTE_4":"FALSE"} |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 A sync runs, and Braze records that you synced all available data up until “2023-03-16 15:00:00”. Then, on the morning of day 2, you have an ETL that runs and some fields in your users table are updated (highlighted):
 
@@ -247,7 +247,7 @@ Now you need to add only the changed values into the CDI source table. These row
 | 2023-03-17 09:30:00 | 34567       | { "ATTRIBUTE_3":"495", "ATTRIBUTE_4":"FALSE"} |
 | 2023-03-17 09:30:00 | 45678       | { "ATTRIBUTE_2":"green"} |
 | 2023-03-17 09:30:00 | 56789       | { "ATTRIBUTE_3":"693"} |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 CDI will only sync the new rows, so the next sync that runs will only sync the last five rows.
 
@@ -599,6 +599,6 @@ We recommend that queries be completed within one hour for optimal performance a
 | Data type              | You can sync user attributes, events, and purchases through Cloud Data Ingestion.                                                                                                  |
 | Braze region           | This product is available in all Braze regions. Any Braze region can connect to any source data region.                                                                              |
 | Source region       | Braze will connect to your data warehouse or cloud environment in any region or cloud provider.                                                                                        |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 <br><br>
diff --git a/_docs/_user_guide/data_and_analytics/creating_a_formula.md b/_docs/_user_guide/data_and_analytics/creating_a_formula.md
index 2282f2ad6ca..1b92d421be8 100644
--- a/_docs/_user_guide/data_and_analytics/creating_a_formula.md
+++ b/_docs/_user_guide/data_and_analytics/creating_a_formula.md
@@ -68,7 +68,7 @@ table td {
 | DAU | MAU |
 | Sessions | DAU |
 | | Segment size |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Revenue dashboard
 
@@ -76,7 +76,7 @@ table td {
 | --- | --- |
 | Purchases (all) | DAU |
 | Select purchases (such as a gift card or product ID) | MAU |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Custom event dashboard
 
@@ -85,7 +85,7 @@ table td {
 | Custom event count | MAU |
 |  | DAU |
 |  | Segment size (only segments that have [analytics tracking][17] enabled can be used) |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 [9]: {{site.baseurl}}/user_guide/data_and_analytics/analytics/understanding_your_app_usage_data/
 [10]: {{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/exporting_revenue_data/
diff --git a/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes.md b/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes.md
index 041bb4951db..46d3b5b1665 100644
--- a/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes.md
+++ b/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes.md
@@ -21,6 +21,10 @@ To create and manage custom attributes in the dashboard, go to **Data Settings**
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can find **Custom Attributes** under **Manage Settings**.
 {% endalert %}
 
+![Four custom attributes that are booleans.]({% image_buster /assets/img/export_custom_attributes.png %})
+
+The **Last updated** column lists the last time the custom attribute was edited, such as when it was last set to blocklist or active. 
+
 From this page, you can view, manage, create, or blocklist existing custom attributes. Select the menu next to a custom attribute for the following actions:
 
 ### Blocklisting
@@ -103,7 +107,7 @@ Boolean attributes are useful for storing simple binary data about your users, l
 | Check if the boolean value **is** either true, false, true or not set, or false or not set | **IS**  | **TRUE**, **FALSE**, **TRUE OR NOT SET**, or **FALSE OR NOT SET** | If this filter specifies `coffee_drinker`, a user will match this filter in the following circumstances: <br> {::nomarkdown}<ul><li>If this filter is <code>true</code> and the user has the value <code>coffee_drinker</code></li><li>If this filter is <code>false</code> and the user doesn't have the value <code>coffee_drinker</code></li><li>If this filter is <code>true or not set</code> and the user has the value <code>coffee_drinker</code> or no value</li><li>If this filter is <code>false or not set</code> and the user doesn't have <code>coffee_drinker</code> or any value</li></ul>{:/} |
 | Check if the boolean value **exists** on a user's profile and is not null | **IS NOT BLANK**  | **N/A** | If this filter specifies `coffee_drinker` and a user has a value for the attribute `coffee_drinker`, the user will match this filter. | 
 | Check if the boolean value **does not exist** on a user's profile or is null | **IS BLANK**  | **N/A** | If this filter specifies `coffee_drinker`and a user either doesn’t have the attribute `coffee_drinker` or the value for `coffee_drinker` is null, the user will match this filter.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ### Numbers {#numbers}
 
@@ -125,7 +129,7 @@ Money spent should not be recorded by this method. Rather it should be recorded
 | Check if the numeric attribute **is less than** a **number**| **LESS THAN** | **NUMBER** | If this filter specifies `10` and a user profile has a value lesser than `10`, the user will match this filter. |
 | Check if the numeric attribute **exists** on a user's profile and is not null | **IS NOT BLANK** | **N/A** | If a user profile contains the specified numeric attribute, regardless of value, the user will match this filter. |
 | Check if the numeric attribute **does not exist** on a user's profile or is null | **IS BLANK** | **N/A** | If a user profile doesn't contain the specified numeric attribute or the attribute’s value is null, the user will match this filter.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 #### Number attribute details
 
@@ -150,19 +154,14 @@ Note that if you input any values with spaces in between, before, or after words
 | Check if the string attribute **does not exactly match any** of the inputted strings | **IS NONE OF** |**STRING**<br>Case sensitive; multiple strings allowed (256 maximum) | If this filter specifies `book`, `bookmark`, and `reading light`, and a user profile doesn't contain any of those strings, the user will match the filter.|
 | Check if the string attribute **partially matches any** of the inputted strings | **CONTAINS ANY OF** | **STRING**<br>Case sensitive; multiple strings allowed (256 maximum) | If this filter specifies `gold` and a user profile contains `gold` in any string, such as `gold_tier` or `former_gold_tier`, the user will match the filter. |
 | Check if the string attribute **does not partially match any** of the inputted strings | **DOESN'T CONTAIN ANY OF** | **STRING**<br>Case sensitive; multiple strings allowed (256 maximum) | If this filter specifies `gold` and a user profile doesn't contain `gold` in any string, the user will match this filter.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 A date string such as "12-1-2021" or "12/1/2021" will be converted to a datetime object and treated as a [time attribute]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#time).
 {% endalert %}
 
 {% 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 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)
+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.
 {% endalert %}
 
 ### Arrays {#arrays}
@@ -192,15 +191,14 @@ The option to increase the maximum length will not be available if the attribute
 | Check if the array attribute **does not include a value which partially match any** of the inputted values | **VALUES DON'T CONTAIN ANY OF** | **STRING**<br>Case sensitive; multiple values allowed (256 maximum) | If this filter specifies `gold` and a user profile array doesn't contain `gold` in any strings, the user will match this filter. This means users with string values like `gold_tier` and `former_gold_tier` won't match this filter.|
 | Check if the array attribute **includes all** of the inputted values | **IS ALL OF** | **STRING**<br>Case sensitive; multiple values allowed (256 maximum) | If this filter specifies `sci-fi, fantasy, romance` and a user profile has all of those values, the user will match this filter. The user can also have `horror` or other values and match this filter.|
 | Check if the array attribute **does not include all of** the inputted values | **ISN'T ALL OF** | **STRING**<br>Case sensitive; multiple values allowed (256 maximum)|  If this filter specifies `sci-fi, fantasy, romance` and a user profile doesn't have all of those values, the user will match this filter.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 {% alert tip %}
-For more on how to use our regular expressions filter, check out this documentation on [Perl compatible regular expressions](http://www.regextester.com/pregsyntax.html) (PCRE).
-<br>
-More resources on regex:
+For more on how to use regular expressions (regex), check out these resources:
+- [Perl compatible regular expressions (PCRE)](https://www.regextester.com/pregsyntax.html)
 - [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)
+- [Regex debugger and tester](https://www.regex101.com/)
+- [Regex tutorial](https://www.medium.com/factory-mind/regex-tutorial-a-simple-cheatsheet-by-examples-649dc1c3f285)
 {% endalert %}
 
 ### Time {#time}
@@ -225,7 +223,7 @@ The last date a custom event or purchase event occurred is automatically recorde
 | Check if the time attribute is **less than X number** of **days in the future** | **IN LESS THAN** | **NUMBER OF DAYS IN FUTURE**  | If this filter specifies `7` and a user profile has a date that is less than seven days in the future, the user will match this filter.|
 | Check if the time attribute **exists** on a user's profile and is not null | **IS NOT BLANK** | **N/A** | If this filter specifies a time attribute that is on a user profile, the user will match this filter.|
 | Check if the time attribute **does not exist** on a user's profile or is null | **IS BLANK** | **N/A** | If this filter specifies a time attribute that isn't on a user profile, the user will match this filter. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 #### Time attribute details
 
@@ -253,7 +251,7 @@ We've consolidated the list of operators available to use in attribute filters,
 | String | does not equal | is none of | At least 1 value |
 | Array | includes value | includes any of | At least 1 value |
 | Array | doesn't include value | includes none of | At least 1 value |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Purchase and revenue tracking {#purchase-revenue-tracking}
 
@@ -271,7 +269,7 @@ Using our purchase methods to record in-app purchases establishes the Lifetime V
 | Check if the purchase occurred **more than X (Max = 50) number of times** | **MORE THAN** | in the past **Y Days (Y = 1,3,7,14,21,30)** |  If this filter specifies `7` times and `21` days, and a user made more than seven purchases in the past 21 days, the user will match this filter.|
 | Check if the purchase occurred **less than X (Max = 50) number of times** | **LESS THAN** | in the past **Y Days (Y = 1,3,7,14,21,30)** | If this filter specifies `7` times and `21` days, and a user made less than seven purchases in the past 21 days, the user will match this filter.|
 | Check if the purchase occurred **exactly X (Max = 50) number of times** | **EXACTLY** | in the past **Y Days (Y = 1,3,7,14,21,30)** | If this filter specifies `7` times and `21` days, and a user made seven purchases in the past 21 days, the user will match this filter.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 {% alert tip %}
 If you would like to segment on the number of times a specific purchase has occurred, you should also record that purchase individually as an [incrementing custom attribute]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/setting_custom_attributes/#incrementingdecrementing-custom-attributes).
diff --git a/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects.md b/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects.md
index 032110d8a67..916bd75bb5a 100644
--- a/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects.md
+++ b/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects.md
@@ -17,7 +17,11 @@ description: "This reference article covers using an array of objects as a data
 - Arrays of objects have no limit on the number of items but do have a maximum size of 50&nbsp;KB.
 - Not all Braze Partners support arrays of objects. Refer to the [Partner documentation]({{site.baseurl}}/partners/home) to confirm if the integration supports this feature.
 
-Updating or removing items in an array requires identifying the item by key and value. As such, consider including a unique identifier for each item in the array. The uniqueness is scoped only to the array and is useful if you want to update and remove specific objects from your array. This is not enforced by Braze.
+Updating or removing items in an array requires identifying the item by key and value, so consider including a unique identifier for each item in the array. The uniqueness is scoped only to the array and is useful if you want to update and remove specific objects from your array. This is not enforced by Braze.
+
+{% alert tip %}
+For more information on using arrays of objects for user attributes objects, refer to [User attributes object]({{site.baseurl}}/api/objects_filters/user_attributes_object).
+{% endalert %}
 
 ## API example
 
@@ -478,17 +482,17 @@ When segmenting users based on arrays of objects, a user will qualify for the se
 
 Create a new segment and select **Nested Custom Attribute** as your filter. Then search for and select the name of your array of objects.
 
-![Filter by array of objects][1]
+![Filter by array of objects.][1]
 
 Use dot notation to specify which field in the array of objects you want to use. Start the text field with an empty set of square brackets `[]` to tell Braze that you're looking inside an array of objects. After that, add a period `.`, followed by the name of the field you want to use.
 
 For example, if you want to filter the `pets` array of objects based on the `type` field, enter `[].type` and choose which type of pet to filter for, such as `snake`.
 
-![Filter by pet type equals snake][3]
+![Filter by pet type equals snake.][3]
 
 Or you might filter for pets that have a `type` of `dog`. Here a user has at least one dog so that user qualifies into the segment of "any user who has at least one pet of type dog".
 
-![Filter by pet type equals dog][2]
+![Filter by pet type equals dog.][2]
 
 ### Levels of nesting
 
@@ -528,7 +532,7 @@ You can create a segment with up to one level of array nesting (array within ano
 ```
 {% endraw %}
 
-## Data Points
+## Data points
 
 Data points are consumed differently depending on whether you create, update, or remove a property.
 
diff --git a/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support.md b/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support.md
index a515de497c3..b74ea21ab30 100644
--- a/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support.md
+++ b/_docs/_user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support.md
@@ -253,8 +253,8 @@ If you haven't captured dates as object properties initially, we recommend resen
     {
       "external_id": "time_with_nca_test",
       "important_dates": {
-        "birthday": {"$time" : "1980-01-01T19:20:30Z"},
-        "wedding_anniversary": {"$time" : "2020-05-28T19:20:30Z"}
+        "birthday": {"$time" : "1980-01-01"},
+        "wedding_anniversary": {"$time" : "2020-05-28"}
       }
     }
   ]
@@ -437,7 +437,7 @@ If you want to reset the schema for an object array with an existing object, you
 
 If data does not appear as expected after regenerating the schema, the attribute may not be ingested often enough. User data is sampled on previous data sent to Braze for the given nested attribute. If the attribute isn't ingested enough, it won't be picked up for the schema.
 
-## Data Points
+## Data points
 
 Any key that is updated consumes a data point. For example, this object initialized in the user profile counts as seven (7) data points:
 
diff --git a/_docs/_user_guide/data_and_analytics/custom_data/custom_events.md b/_docs/_user_guide/data_and_analytics/custom_data/custom_events.md
index 516265ffa5d..7648ff1ffb5 100644
--- a/_docs/_user_guide/data_and_analytics/custom_data/custom_events.md
+++ b/_docs/_user_guide/data_and_analytics/custom_data/custom_events.md
@@ -108,7 +108,7 @@ The following table shows the filters available for segmenting users by custom e
 | Check if the custom event occurred **more than X (Max = 50) number of times** | **MORE THAN** | in the past **Y Days (Y = 1,3,7,14,21,30)** |
 | Check if the custom event occurred **less than X (Max = 50) number of times** | **LESS THAN** | in the past **Y Days (Y = 1,3,7,14,21,30)** |
 | Check if the custom event occurred **exactly X (Max = 50) number of times** | **EXACTLY** | in the past **Y Days (Y = 1,3,7,14,21,30)** |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Analytics
 
@@ -159,7 +159,7 @@ Property values can be any of the following data types:
 | Arrays | Arrays cannot include datetimes. |
 | Objects | Objects will be ingested as strings. |
 | Nested objects | Objects that are inside of other objects. For more, see the section in this article on [Nested objects](#nested-objects).
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Event property objects that contain array or object values can have an event property payload up to 100&nbsp;KB.
 
diff --git a/_docs/_user_guide/data_and_analytics/custom_data/managing_custom_data.md b/_docs/_user_guide/data_and_analytics/custom_data/managing_custom_data.md
index 1e2ab3951cb..9bc368bfbb3 100644
--- a/_docs/_user_guide/data_and_analytics/custom_data/managing_custom_data.md
+++ b/_docs/_user_guide/data_and_analytics/custom_data/managing_custom_data.md
@@ -135,7 +135,7 @@ If you choose to force the data type for an attribute, any data that comes in th
 | Boolean | Inputs of `1`, `true`, `t` (not case sensitive) will be stored as `true` |
 | Boolean | Inputs of `0`, `false`, `f` (not case sensitive) will be stored as `false` |
 | Number | Integers or Floats (such as `1`, `1.5`) will be stored as numbers |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For more information on specific filter options exposed by different data type comparisons, check out [Configuring reporting][43]. And for more information on the different available data types, refer to [Custom attribute data types][44].
 
diff --git a/_docs/_user_guide/data_and_analytics/data_points.md b/_docs/_user_guide/data_and_analytics/data_points.md
index 7a1d22297eb..ed267bacffa 100644
--- a/_docs/_user_guide/data_and_analytics/data_points.md
+++ b/_docs/_user_guide/data_and_analytics/data_points.md
@@ -56,7 +56,15 @@ The following actions do not consume data points:
 An array is an ordered collection of items stored within a custom attribute. In terms of consumption, updating an array costs one data point per API call. If you add values to an array incrementally, it will count as one data point per value. 
 
 {% alert tip %}
-If you set the whole array at once, it will count as a single data point. As such, arrays are a great tool to keep user profiles up-to-date with relevant information and reduce costs. 
+If you set the whole array at once, it will count as a single data point. As such, arrays are a great tool to keep user profiles up-to-date with relevant information and reduce costs.
+{% endalert %}
+
+#### Nested custom attributes
+
+Nested custom attributes refer to an object that defines a set of attributes as a property of another attribute. Every key in the object will count as a data point.
+
+{% alert note %}
+Updating a custom attribute object to `null` also consumes a data point.
 {% endalert %}
 
 #### CSV
@@ -101,7 +109,7 @@ Also, as subscription state changes do not consume data points, updating the `em
 | Twitter | Number of tweets |
 | Facebook | Likes |
 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Billable %}
@@ -154,7 +162,7 @@ table td {
 | Appsflyer cohort assignment | All assignments | |
 | Most recent location | All most recent locations | Entering or exiting geofences doesn't consume data points because geofence data is not stored against the user profile. Geofences are monitored by Apple and Google location services; Braze only gets notified upon a user triggering a geofence. |
 | Twitter | Username | |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
diff --git a/_docs/_user_guide/data_and_analytics/data_transformation/creating_a_transformation.md b/_docs/_user_guide/data_and_analytics/data_transformation/creating_a_transformation.md
index 2c7f7493b34..7df77c6f7e3 100644
--- a/_docs/_user_guide/data_and_analytics/data_transformation/creating_a_transformation.md
+++ b/_docs/_user_guide/data_and_analytics/data_transformation/creating_a_transformation.md
@@ -16,7 +16,7 @@ description: "This reference article provides steps to create a transformation u
 | --- | --- |
 | Two-factor authentication or SSO | You must have [two-factor authentication]({{site.baseurl}}/user_guide/administrative/app_settings/company_settings/security_settings/#two-factor-authentication) (2FA) or [single sign-on]({{site.baseurl}}/user_guide/administrative/app_settings/company_settings/security_settings/#single-sign-on-sso-authentication) (SSO) enabled for your account. |
 | Correct permissions | You must be either an account admin or a workspace admin, or have "Manage Transformations" user permissions. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Step 1: Identify a source platform
 
diff --git a/_docs/_user_guide/data_and_analytics/data_transformation/overview.md b/_docs/_user_guide/data_and_analytics/data_transformation/overview.md
index 6e829580575..335433a3268 100644
--- a/_docs/_user_guide/data_and_analytics/data_transformation/overview.md
+++ b/_docs/_user_guide/data_and_analytics/data_transformation/overview.md
@@ -35,7 +35,7 @@ The following table describes the differences between the free and pro version o
 |----|----|----|
 | Active transformations | Up to 5 per company | Up to 55 per company |
 | Per month | 300,000 incoming requests per month | 10,300,000 incoming requests per month |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert important %}
 To request an upgrade to Data Transformation Pro, contact your Braze account manager or select the **Request Upgrade** button in the Braze dashboard.
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/export_apis.md b/_docs/_user_guide/data_and_analytics/export_braze_data/export_apis.md
index 9fedf0b507d..73fdd176cbc 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/export_apis.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/export_apis.md
@@ -10,15 +10,17 @@ platform: API
 
 # Export APIs
 
-> Braze Export APIs allow you to programmatically export a JSON file of dashboard data. Refer to our [Export endpoints][24] for a list of data that you can access, as well as instructions and sample code for the export.
+> This page covers Braze Export APIs, which allow you to programmatically export a JSON file of dashboard data. Refer to [Export endpoints][24] for a list of data that you can access, including instructions and sample code for the export.
+
+## When to use export APIs instead of CVS downloads
 
 There are a few reasons why you would prefer this method over exporting a CSV directly from the dashboard:
 
- - Your file is very large. From our dashboard, you can export a CSV with at most 500,000 rows. If you're exporting data on a segment with over 500,000 users, you'll need to use our export API, which places no limit on how much you can export.
- -  You wish to interact with the data programmatically.
+ - Your file is very large. From our dashboard, you can export a CSV with at most 500,000 rows. If you're exporting data on a segment with over 500,000 users, you'll need to use our export API, which has no limit on how much you can export.
+ -  You want to interact with the data programmatically.
 
 {% alert tip %}
-For help with CSV and API exports, visit our [export troubleshooting]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/) article.
+For help with CSV and API exports, refer to [Export troubleshooting]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
 {% endalert %}
 
 [24]: {{site.baseurl}}/api/endpoints/export/
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/export_campaign_results_data.md b/_docs/_user_guide/data_and_analytics/export_braze_data/export_campaign_results_data.md
index 3b67d12c83a..7440e434292 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/export_campaign_results_data.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/export_campaign_results_data.md
@@ -12,15 +12,15 @@ tool:
 
 # Export campaign data
 
-> From the **Campaigns** page of the dashboard, select the campaign you wish to view and scroll down to the historical performance graphs, which can be exported.
+> From the **Campaigns** page of the dashboard, select the campaign you want to view and scroll down to the historical performance graphs, which can be exported.<br><br>This page covers how to export campaign results data from single, multi-channel, and multivariate campaigns, and how to export user data from the recipients.
 
 ## Multichannel campaigns
 
-For multichannel campaigns, the data that can be exported will depend on which messaging channels were used. Here's a list of all the data that can be exported from a campaign that used iOS push, Android push, email, and in-app messages:
+For multichannel campaigns, the data that can be exported depends on which messaging channels you used. Here's a list of all the data that can be exported from a campaign that used iOS push, Android push, email, and in-app messages:
 
 - Messages Sent by Date
     - Total Messages Sent
-    - Messages Sent Across Campaign's Channels (can include push, email and in-app message)
+    - Messages Sent Across Campaign's Channels (can include push, email, and in-app message)
 - Email Message Engagement by Date
     - Number of Emails Delivered
     - Number of Emails Sent
@@ -45,7 +45,7 @@ For multichannel campaigns, the data that can be exported will depend on which m
 
 ## Multivariate campaigns
 
-For multivariate campaigns, which use just one messaging channel, you'll be able to export data that shows how each variant performed on the specific messaging channel's analytics over time. You can view this data grouped by statistic or grouped by message variant.
+For multivariate campaigns, which use just one messaging channel, you can export data that shows how each variant performed on the specific messaging channel's analytics over time. You can view this data grouped by statistic or grouped by message variant.
 
 Push campaign results contain graphs for the following analytics:
 
@@ -83,16 +83,16 @@ Can't see the **User Data** button? To export user data, you need the **Export U
 
 The CSV output contains user profile data for every recipient of the campaign. Braze will generate the report in the background and email it to the user who is currently logged in.
 
-If you have linked your [Amazon S3 credentials][26] to Braze, then the CSV will also be uploaded in your S3 bucket. Otherwise, the link emailed to you will expire in a few hours.
+If you've linked your [Amazon S3 credentials][26] to Braze, then the CSV will also be uploaded in your S3 bucket. Otherwise, the link emailed to you will expire in a few hours.
 
-The exported file includes the same user data fields which are included when you [export user data for a segment][40]. In addition to those data fields, if you choose "Export All Recipient Data," then the exported file will also contain the following data for each user:
+The exported file includes the same user data fields that are included when you [export user data for a segment][40]. In addition to those data fields, if you choose "Export All Recipient Data," then the exported file will also contain the following data for each user:
 
 - Name of campaign variation received
 - API ID of campaign variation received
 - Whether user is in control group
 
 {% alert tip %}
-For help with CSV and API exports, visit our [export troubleshooting]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/) article.
+For help with CSV and API exports, check out [Export troubleshooting]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
 {% endalert %}
 
 [6]: {% image_buster /assets/img/campaign_export_example.png %}
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/export_canvas_data.md b/_docs/_user_guide/data_and_analytics/export_braze_data/export_canvas_data.md
index 5a355c34eff..51935f86e76 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/export_canvas_data.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/export_canvas_data.md
@@ -12,7 +12,7 @@ tool:
 
 # Export Canvas data
 
-> User data can be exported to a CSV. This data can be exported for your entire Canvas or a specific Canvas component.
+> User data can be exported to a CSV. This page covers how to export data for your entire Canvas or a specific Canvas component.
 
 ## Exporting data for a Canvas
 
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/export_custom_event_data.md b/_docs/_user_guide/data_and_analytics/export_braze_data/export_custom_event_data.md
index db5e0beab8a..16bf9cbd525 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/export_custom_event_data.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/export_custom_event_data.md
@@ -10,12 +10,12 @@ tool: Reports
 
 # Export custom event aggregates
 
-> The **Custom Events** report page of the dashboard allows you to view the occurrences of one or more custom events over time. If you view Detailed Statistics for custom events or custom events by the hour, you'll have the option of also viewing the data by specific segments.
+> This page covers the **Custom Events** report page of the dashboard, which allows you to view the occurrences of one or more custom events over time. If you view detailed statistics for custom events or custom events by the hour, you'll have the option of also viewing the data by specific segments.
 
 You can find the **Custom Events Report** under **Analytics**.
 
 {% alert note %}
-If you are using the [older navigation]({{site.baseurl}}/navigation), you can find **Custom Events** report page under **Data**.
+If you're using the [older navigation]({{site.baseurl}}/navigation), you can find **Custom Events** report page under **Data**.
 {% endalert %}
 
 ![Custom events][14]
@@ -32,7 +32,7 @@ You can export the following CSVs:
     - (Optional) Custom Events for Different Segments
 
 {% alert tip %}
-For help with CSV and API exports, visit our [export troubleshooting]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/) article.
+For help with CSV and API exports, refer to [Export troubleshooting]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
 {% endalert %}
 
 [14]: {% image_buster /assets/img_archive/Export_events.png %}
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md
index 6dfa94bc861..92db1ca0797 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md
@@ -9,24 +9,31 @@ description: "This reference article covers some common troubleshooting scenario
 
 # Export troubleshooting
 
-> The following lists error messages you may encounter while exporting data via CSV or API from Braze.
+> This page lists error messages you may encounter while exporting data through CSV or API from Braze.
 
 ## Common errors
 
 ### 'AccessDenied' 
 
-If you are using **your own S3 bucket**, this could happen because:
+#### When using your own S3 bucket
+
+If you're using **your own S3 bucket**, this could happen because:
+
 - The expected object is no longer in the S3 bucket; check with your engineers.
-- The configured S3 credentials within the Braze dashboard do not have the correct permissions; confirm the proper credentials with your team.
+- The configured S3 credentials within the Braze dashboard don't have the correct permissions; confirm the proper credentials with your team.
+
+#### When using a Braze S3 bucket
 
-If you are using a **Braze S3 bucket**, this could happen because:
-- The object is no longer there. This could occur if you clicked on a link for an export that ran 4+ hours ago. If this is the case, re-run your export.
-- You clicked on the download link right away, before the S3 was ready to serve the object. Wait a few minutes and try again. Larger reports will generally take longer. 
+If you're using a **Braze S3 bucket**, this could happen because:
+
+- The object is no longer there. This could occur if you clicked on a link for an export that ran over 4 hours ago. If this is the case, re-run your export.
+- You selected the download link right away, before the S3 was ready to serve the object. Wait a few minutes and try again. Larger reports will generally take longer. 
 - The export is too big, so our server ran out of memory trying to create this zip file. We'll automatically email the user attempting this export if this occurs. If you consistently run into this issue, we recommend that you use your own S3 buckets in the future.
 
 ### 'ExpiredToken'
 
-This will happen if the email was sent 4+ hours ago. Re-run the export and download it within 4 hours.
+This happens if the email was sent over 4 hours ago. Re-run the export and download it within 4 hours.
+
 This could also be caused by Braze no longer having access to the S3 bucket you are downloading the data to. Make sure you've updated your S3 credentials using these steps.
 
 ### "Looks like the file doesn't exist anymore, please check to make sure nothing is deleting objects from your bucket"
@@ -42,4 +49,4 @@ Braze will automatically prepend an apostrophe to a field in the CSV export if t
 - +
 - @
 
-For example, the field "-1943" will be exported as "'-1943". This does not apply to JSON exports, such as those returned by the [`/users/export/segment` endpoint]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/).
\ No newline at end of file
+For example, the field "-1943" will export as "'-1943". This doesn't apply to JSON exports, such as those returned by the [`/users/export/segment` endpoint]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/).
\ No newline at end of file
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/exporting_app_usage_data.md b/_docs/_user_guide/data_and_analytics/export_braze_data/exporting_app_usage_data.md
index 052c2422e63..5fabc84bd59 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/exporting_app_usage_data.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/exporting_app_usage_data.md
@@ -12,9 +12,9 @@ tool:
 
 # Exporting usage analytics
 
-> The **Home** page of the dashboard contains high-level data of app usage, as well as detailed statistics of different KPIs by date.
+> This page covers the **Home** page of the dashboard, which contains high-level data of app usage, as well as detailed statistics of different KPIs by date.
 
-To obtain CSVs of information from this page:
+To export CSVs of data from this page:
 
 1. Set the time frame and apps you want to view data for. By default, the dashboard shows the last 30 days of data for all apps.
 
@@ -27,7 +27,7 @@ To obtain CSVs of information from this page:
 ![Performance Over Time graph on the Home dashboard.][2]
 
 {:start="4"}
-4. Click <i class="fas fa-bars" title="Chart context menu"></i> and select your export option.
+4. Select <i class="fas fa-bars" title="Chart context menu"></i> and then select your export option.
 
 ## Available data
 
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/exporting_revenue_data.md b/_docs/_user_guide/data_and_analytics/export_braze_data/exporting_revenue_data.md
index e2009699260..a25961fbfed 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/exporting_revenue_data.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/exporting_revenue_data.md
@@ -11,23 +11,23 @@ tool:
 
 # Export revenue and total revenue data
 
-> On the [Revenue Report]({{site.baseurl}}/user_guide/data_and_analytics/reporting/revenue_report/) page of the dashboard you can view data on revenue over specific periods of time, a specific product revenue, and your app's total revenue.
+> This page covers the [Revenue Report]({{site.baseurl}}/user_guide/data_and_analytics/reporting/revenue_report/) page of the dashboard, where you can view data on revenue over specific periods of time, a specific product revenue, and your app's total revenue.
 
 You can find the **Revenue Report** under **Analytics**.
 
 {% alert note %}
-If you are using the [older navigation]({{site.baseurl}}/navigation), you can find **Revenue** under **Data**.
+If you're using the [older navigation]({{site.baseurl}}/navigation), you can find **Revenue** under **Data**.
 {% endalert %}
 
 {% alert tip %}
 Looking for more ways to get revenue data? Try adding purchase behavior (as well as purchase of a product) to campaigns or Canvases as [conversion events]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/conversion_events/).
 {% endalert %}
 
-To export your revenue data, click <i class="fas fa-bars" title="Chart context menu"></i> in the **Performance Over Time** graph and select your export option.
+To export your revenue data, select <i class="fas fa-bars" title="Chart context menu"></i> in the **Performance Over Time** graph and select your export option.
 
 ## Performance Over Time graph
 
-The following data can be accessed via the **Performance Over Time** graph:
+The following data can be viewed in the **Performance Over Time** graph:
 
 - KPI Formulas
 - Purchases
@@ -43,10 +43,12 @@ The following data can be accessed via the **Performance Over Time** graph:
 
 ## Total revenue
 
-You can view revenue statistics on a case-by-case basis on the [Campaign Analytics]({{site.baseurl}}/user_guide/data_and_analytics/reporting/campaign_analytics/) or [Canvas Analytics]({{site.baseurl}}/user_guide/engagement_tools/canvas/testing_canvases/measuring_and_testing_with_canvas_analytics/) pages. The Total Revenue statistic is generated from campaign recipients who have made a purchase within the campaign's primary conversion period.
+You can view revenue statistics on a case-by-case basis on the [Campaign Analytics]({{site.baseurl}}/user_guide/data_and_analytics/reporting/campaign_analytics/) or [Canvas Analytics]({{site.baseurl}}/user_guide/engagement_tools/canvas/testing_canvases/measuring_and_testing_with_canvas_analytics/) pages. 
+
+{% multi_lang_include metrics.md metric='Total Revenue' %}
 
 {% alert tip %}
-Revenue reports cannot be exported via API. For help with CSV exports, refer to [export troubleshooting]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+Revenue reports cannot be exported through API. For help with CSV exports, refer to [export troubleshooting]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
 {% endalert %}
 
 {% comment %}
@@ -60,11 +62,11 @@ You can view the following additional revenue metrics by generating a Campaign C
 - [Unique Direct Purchases][4]
 - [Revenue per Recipient][5]
 
-These metrics are based on last-click attribution, which means that in order for revenue to be attributed to a campaign, that campaign must:
+These metrics are based on last-click attribution, which means that revenue will be attributed to a campaign if that campaign:
 
-1. Be the last campaign the user clicked prior to purchasing
+1. Is the last campaign the user clicked prior to purchasing
     <br>**AND**<br>
-2. Be clicked by the user less than 3 days prior to purchasing
+2. Was clicked by the user less than 3 days prior to purchasing
 
 {% endcomment %}
 
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/faqs.md b/_docs/_user_guide/data_and_analytics/export_braze_data/faqs.md
index 6db8466f280..f02cb480f29 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/faqs.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/faqs.md
@@ -17,16 +17,16 @@ No. If you have provided S3 credentials, all your exports will appear in your S3
 
 ### Do I have to add S3 credentials to Braze to export data?
 
-No. If you do not add S3 credentials, your exports will appear in an S3 bucket belonging to Braze.
+No. If you don't add S3 credentials, your exports will appear in an S3 bucket belonging to Braze.
 
-### What happens if you set up S3 credentials in the dashboard but don't select "make this the default data export destination?"
+### What happens if you set up S3 credentials in the dashboard but don't select "Make this the default data export destination?"
 
-That checkbox will impact whether exports go to S3 or Azure, assuming you've added credentials for both.
+The **Make this the default data export destination** checkbox impacts whether exports go to S3 or Azure, assuming you've added credentials for both.
 
 ### Why did I receive multiple files when exporting user profiles to S3?
 
 This is expected behavior for workspaces with a lot of users. Braze will split your export into multiple files based on the number of users in your workspace. Generally, there is one file output per 5,000 users. Note that if you are exporting a small segment within a large workspace, you may still receive multiple files.
 
-### Why do I see duplicates when I export users by segment via rest API?
+### Why do I see duplicates when I export users by segment through REST API?
 
-This is a very rare edge case caused by the underlying architecture of the database provider. Duplicates are cleaned out every week; however, most weeks, no duplicates are cleared.
+This is a very rare occurence caused by the underlying architecture of the database provider. Duplicates are cleaned out every week; however, most weeks, no duplicates are cleared.
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/message_archiving.md b/_docs/_user_guide/data_and_analytics/export_braze_data/message_archiving.md
index 2f25dc44999..a81ee12e216 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/message_archiving.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/message_archiving.md
@@ -10,20 +10,20 @@ description: "This reference article covers message archiving, a feature that al
 
 # Message archiving
 
-> Message archiving lets you save a copy of messages sent to users for archival or compliance purposes to your AWS S3 bucket, Azure Blob Storage container or Google Cloud Storage bucket.
+> Message archiving lets you save a copy of messages sent to users for archival or compliance purposes to your AWS S3 bucket, Azure Blob Storage container or Google Cloud Storage bucket. <br><br> This article covers how to set up message archiving, JSON payloads references, and frequently asked questions.
 
 Message archiving is available as an add-on feature. To get started with message archiving, reach out to your Braze customer success manager.
 
-## Overview
+## How it works
 
 When this feature is turned on, if you have connected a cloud storage bucket to Braze and marked it as the default data export destination, Braze will write a gzipped JSON file to your cloud storage bucket for each message sent to a user through your selected channels (email, SMS, or push). 
 
-This file will contain the fields defined under [File references](#file-references) and reflect the final templated messages sent to the user. Any templated values defined in your campaign (for example, {% raw %}`{{${first_name}}}`{% endraw %}) will show the final value that the user received based on their profile information. This will allow you to retain a copy of the message sent to satisfy compliance, audit, or customer support requirements.
+This file will contain the fields defined under [File references](#file-references) and reflect the final templated messages sent to the user. Any templated values defined in your campaign (for example, {% raw %}`{{${first_name}}}`{% endraw %}) will show the final value that the user received based on their profile information. This allows you to retain a copy of the message sent to satisfy compliance, audit, or customer support requirements.
 
 If you set up credentials for multiple cloud storage providers, message archiving will only export to the one explicitly marked as the default data export destination. If no explicit default is provided and an AWS S3 bucket is connected, message archiving will upload to that bucket.
 
 {% alert important %}
-Turning on this feature will impact the delivery speed of your messages, as the file upload is performed immediately before the message send to ensure accuracy. This introduces additional latency into the Braze sending pipeline, affecting sending speeds.
+Turning on this feature will impact the delivery speed of your messages, as the file upload is performed immediately before the message send to maintain accuracy. This introduces additional latency into the Braze sending pipeline, affecting sending speeds.
 {% endalert %}
 
 The JSON will be saved in your storage bucket using the following key structure:
@@ -41,7 +41,7 @@ Braze downcases your push tokens before we hash them. This results in the push t
 
 ## Setting up message archiving
 
-This section describes how to set up message archiving for your workspace. Before proceeding, confirm that your company has purchased and turned on message archiving.
+This section guides you through setting up message archiving for your workspace. Before proceeding, confirm that your company has purchased and turned on message archiving.
 
 ### Step 1: Connect a cloud storage bucket
 
@@ -55,7 +55,7 @@ To select channels:
 
 1. Go to **Settings** > **Message Archiving**.
 2. Select your channels.
-3. Click **Save changes**.
+3. Select **Save changes**.
 
 ![The Message Archiving page has three channels to select: Email, Push, and SMS.][1]
 
@@ -160,7 +160,7 @@ The `extras` field referred to in this payload is from the key-value pairs added
 
 ### What templating is not included in the payload?
 
-Modifications done after the message leaves Braze will not be reflected in the file saved to your cloud storage bucket. This will include modifications our mail delivery partners make, like wrapping links for click tracking and inserting tracking pixels.
+Modifications done after the message leaves Braze won't be reflected in the file saved to your cloud storage bucket. This includes modifications our mail delivery partners make, like wrapping links for click tracking and inserting tracking pixels.
 
 ### What are messages under the "unassociated" value in the campaign path?
 
@@ -168,18 +168,18 @@ When a message is sent outside of a campaign or Canvas, the campaign ID in the f
 
 ### How do I find more information about this send?
 
-You can use either the `external_id` or `dispatch_id` in conjunction with the `user_id` to cross-reference the templated message with our Currents data to find more information like the timestamp it was delivered, whether or not the user opened or clicked the message, and more.
+You can use either the `external_id` or `dispatch_id` in conjunction with the `user_id` to cross-reference the templated message with our Currents data to find more information like the timestamp it was delivered, whether the user opened or clicked the message, and more.
 
 ### How are retries handled?
 
-Should your cloud storage bucket be unreachable, Braze will retry up to three times with a [backoff jitter](https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/#Jitter). AWS S3 rate limit retries are automatically handled by Braze.
+If your cloud storage bucket is unreachable, Braze will retry up to three times with a [backoff jitter](https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/#Jitter). AWS S3 rate limit retries are automatically handled by Braze.
 
 ### What happens if my credentials are invalid?
 
-If your cloud storage credentials become invalid at any point, Braze will not be able to save any messages to your cloud storage bucket, and those messages will be lost. We recommend configuring the [AWS credentials errors notification]({{site.baseurl}}/user_guide/administrative/company_settings/notification_preferences) preference to ensure you receive alerts for any credentials issues.
+If your cloud storage credentials become invalid at any point, Braze won't be able to save any messages to your cloud storage bucket, and those messages will be lost. We recommend configuring the [AWS credentials errors notification]({{site.baseurl}}/user_guide/administrative/company_settings/notification_preferences) preference so you'll receive alerts for any credentials issues.
 
-### Why does my archive file's "sent_at" timestamp differ slightly from the sent timestamp in Currents?
+### Why does my archive file's `sent_at` timestamp differ slightly from the sent timestamp in Currents?
 
-The rendered copy is uploaded immediately before sending the message to the end user. Because of cloud storage upload times, there may be a delay of a few seconds between the "sent_at" timestamp in the rendered copy versus the actual time the send occurs.
+The rendered copy is uploaded immediately before sending the message to the user. Because of cloud storage upload times, there may be a delay of a few seconds between the `sent_at` timestamp in the rendered copy versus the actual time the send occurs.
 
 [1]: {% image_buster /assets/img/message_archiving_settings.png %}
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/opening_csv_reports_in_excel.md b/_docs/_user_guide/data_and_analytics/export_braze_data/opening_csv_reports_in_excel.md
index 489dcdf8230..c6df5e6334f 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/opening_csv_reports_in_excel.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/opening_csv_reports_in_excel.md
@@ -9,6 +9,8 @@ description: "This reference article covers how to open CSV exports in Excel."
 
 # Opening CSV exports in Excel
 
+> This page covers how to open CSV exports into Excel.
+
 ## Set Excel as the default program
 
 While CSV files are usually automatically opened in Excel by default, this may not always be the case. Refer to the [Windows][20] and [Apple][21] troubleshooting articles for steps to set Excel as your default program.
diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/segment_data_to_csv.md b/_docs/_user_guide/data_and_analytics/export_braze_data/segment_data_to_csv.md
index 098833f4939..4c695fdd944 100644
--- a/_docs/_user_guide/data_and_analytics/export_braze_data/segment_data_to_csv.md
+++ b/_docs/_user_guide/data_and_analytics/export_braze_data/segment_data_to_csv.md
@@ -9,13 +9,15 @@ description: "This reference article covers how to export segment data to CSV."
 
 # Exporting segment data to CSV
 
-> To request a CSV export of user data from a segment, select the **User Data** dropdown while editing a segment and select to export either the user data or email addresses for the segment.
+> This page covers how to request a CSV export of user data from a segment, and the data included in the export.
 
-![][1]
+To export segment data to a CSV, select the **User Data** dropdown while editing a segment and select to export either the user data or email addresses for the segment.
+
+![Segment Details section with User Data dropdown showing export options.][1]
 
 You can also request a CSV export from the main **Segments** page by selecting the <i class="fas fa-gear"></i> **Settings** dropdown for a segment:
 
-![][2]
+![Settings dropdown on the main Segments page.][2]
 
 {% alert tip %}
 To export data from all your user profiles, create a segment with no filters, and then request a CSV export.
@@ -27,7 +29,7 @@ The CSV output contains the data from each user profile captured in the segment
 Due to file size restrictions, your export may fail if the estimated size of your segment is over 500,000 users. Note that this restriction uses the estimated size of your segment, and not the exact calculation. For more details, see [Exporting large segments]({{site.baseurl}}/help/help_articles/segments/exporting_large_segments/).
 {% endalert %}
 
-If you've linked your [Amazon S3 credentials][26] to Braze, the CSV will instead be uploaded in your S3 bucket under the key `segment-export/SEGMENT_ID/YYYY-MM-dd/users-RANDOMSTRING.zip`. The link emailed to you will expire after one day of exporting and requires that you are logged into the dashboard for access.
+If you've linked your [Amazon S3 credentials][26] to Braze, the CSV will instead be uploaded in your S3 bucket under the key `segment-export/SEGMENT_ID/YYYY-MM-dd/users-RANDOMSTRING.zip`. The link emailed to you will expire after one day of exporting, and requires you to be logged into the dashboard for access.
 
 ## Data included in export
 
@@ -87,7 +89,7 @@ The following is included in your export depending on your selection.
 | unsubscribed_from_emails_at | Email unsubscribe date |
 | opted_in_to_emails_at       | Email opt-in date      |
 | user_aliases                | User aliases, if any   |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 For help with CSV and API exports, visit our [troubleshooting]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/) article.
diff --git a/_docs/_user_guide/data_and_analytics/ideas_and_strategies.md b/_docs/_user_guide/data_and_analytics/ideas_and_strategies.md
new file mode 100644
index 00000000000..41cb0d112bd
--- /dev/null
+++ b/_docs/_user_guide/data_and_analytics/ideas_and_strategies.md
@@ -0,0 +1,6 @@
+---
+nav_title: Ideas and Strategies
+page_order: 16
+noindex: true
+config_only: true
+---
\ No newline at end of file
diff --git a/_docs/_user_guide/data_and_analytics/ideas_and_strategies/b2b_data_models.md b/_docs/_user_guide/data_and_analytics/ideas_and_strategies/b2b_data_models.md
new file mode 100644
index 00000000000..cf8167cd2c9
--- /dev/null
+++ b/_docs/_user_guide/data_and_analytics/ideas_and_strategies/b2b_data_models.md
@@ -0,0 +1,208 @@
+---
+nav_title: B2B Data Models
+article_title: Creating a B2B Data Model
+page_order: 0
+page_type: reference
+description: "Learn how to use Braze data tools to create B2B models."
+---
+
+# Creating a B2B data model
+
+> This use case demonstrates how you can use Braze data tools to create an effective and efficient B2B data model that helps you target, trigger, personalize, and send messages to your business users. 
+
+{% alert note %}
+These recommendations may change over time as Braze builds out our B2B capabilities.
+{% endalert %}
+
+Before we get into how you can set up your B2B data model, let’s go over several concepts and terms you should know.
+
+There are four primary B2B objects that you need to execute B2B campaigns.
+
+| Object | Description |
+| --- | --- |
+| Leads | A record of potential customers who have shown interest in a product or service but haven't yet been qualified as an opportunity. |
+| Contacts | Typically, individuals who have been qualified and converted from a lead to a contact to pursue a sales opportunity. |
+| Opportunities | A record that tracks the details of a potential sale or deal in progress
+| Accounts | A record of an organization that is a qualified potential customer, an existing customer, a partner, or a competitor who has a relationship of similar significance. |
+{: .reset-td-br-1 .reset-td-br-2 }
+
+Within Braze, these four objects are combined and reduced into two objects: user profiles and business objects.
+
+| Braze B2B object | Description | Original B2B objects  |
+| --- | --- | --- |
+| User profiles | These map directly to leads and contacts in your sales CRM system. Because leads are captured by Braze, they are automatically created as leads in your sales CRM system. As they are converted to contacts, the contact IDs and details sync back to Braze. |Leads<br> Contacts |
+| Business objects | These map to any non-user objects in your sales CRM system. This includes your sales specific objects, such as account objects and opportunity objects. | Accounts<br> Opportunities |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
+
+## Step 1: Create your business objects in Braze
+
+Business objects are any non-user centric dataset. In a B2B context, these include your account and opportunity data, and any other pertinent non-user centric dataset that your company tracks.
+
+There are two methods to create and manage your business objects in Braze, catalogs and connected sources. 
+
+| Method | Description |
+| --- | --- |
+| [Catalogs]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs) | These are independent data objects (supplemental data objects) on the primary user profile in Braze. In a B2B context, you would likely have catalogs for your accounts and opportunities. |
+| [Connected sources]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/connected_sources/) | These allow Braze to directly query your data warehouse. You're likely already syncing your lead, contact, opportunity, and account objects to your data warehouse on a regular basis, so you can point Braze segmentation directly to that warehouse and activate it in a zero-copy environment. |
+{: .reset-td-br-1 .reset-td-br-2 }
+
+### Option 1: Use catalogs for accounts and opportunities
+
+Catalogs are data tables that are hosted and managed in Braze. While account and opportunity data originates from your sales CRM system of choice, you would be duplicating these in Braze to be used for marketing purposes: account-based segmentation, account-based marketing, lead management, and more.
+
+For this option, we recommend creating one catalog for your accounts and one for your opportunities, and updating them frequently by sending Braze updates through our [catalogs API]({{site.baseurl}}/api/endpoints/catalogs/) or [catalogs Cloud Data Ingestion (CDI)]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/sync_catalogs_data/). When creating these catalogs, make sure the `id` (first column) of your catalog matches the `id` in your sales CRM system.
+
+#### Map over your CRM fields
+
+The tables below include a few examples of fields you can map over from your CRM’s account and opportunity objects.
+
+{% tabs %}
+{% tab Account catalog %}
+
+In this use case, Salesforce is the example CRM system. You can map over any field that is included in your CRM's objects.
+
+<table border="1">
+  <tr>
+    <th><b>Braze object</b></th>
+    <th><b>Braze field</b></th>
+    <th><b>CRM object (Salesforce)</b></th>
+    <th><b>CRM field (Salesforce)</b></th>
+  </tr>
+  <tr>
+    <td rowspan="4">Catalog &gt; Account catalog</td>
+    <td><code>id</code></td>
+    <td><code>account</code></td>
+    <td><code>id</code></td>
+  </tr>
+  <tr>
+    <td><code>AccountName</code></td>
+    <td><code>account</code></td>
+    <td><code>Account Name</code></td>
+  </tr>
+  <tr>
+    <td><code>Type</code></td>
+    <td><code>account</code></td>
+    <td><code>Type</code></td>
+  </tr>
+  <tr>
+    <td><code>OTHER_FIELDS</code></td>
+    <td><code>account</code></td>
+    <td><code>OTHER_FIELDS</code></td>
+  </tr>
+</table>
+
+##### Example table of mapped account fields
+
+![Table of Salesforce accounts with respective information, such as billing address and account owner.]({% image_buster /assets/img/b2b/sf_accounts.png %})
+
+{% endtab %}
+{% tab Opportunity catalog %}
+
+In this use case, Salesforce is the example CRM system. You can map over any field that is included in your CRM's objects.
+
+<table border="1">
+  <tr>
+    <th><b>Braze object</b></th>
+    <th><b>Braze field</b></th>
+    <th><b>CRM object (Salesforce)</b></th>
+    <th><b>CRM field (Salesforce)</b></th>
+  </tr>
+  <tr>
+    <td rowspan="4">Catalog &gt; Opportunity catalog</td>
+    <td><code>id</code></td>
+    <td><code>opportunity</code></td>
+    <td><code>id</code></td>
+  </tr>
+  <tr>
+    <td><code>OpportunityName</code></td>
+    <td><code>opportunity</code></td>
+    <td><code>Opportunity Name</code></td>
+  </tr>
+  <tr>
+    <td><code>Territory</code></td>
+    <td><code>opportunity</code></td>
+    <td><code>Territory</code></td>
+  <tr>
+    <td><code>OTHER_FIELDS</code></td>
+    <td><code>opportunity</code></td>
+    <td><code>OTHER_FIELDS</code></td>
+  </tr>
+  </tr>
+</table>
+
+##### Example table of mapped opportunity fields
+
+![Table of Salesforce opportunities with respective information, such as billing address and account owner.]({% image_buster /assets/img/b2b/sf_opportunities.png %})
+
+{% endtab %}
+{% endtabs %}
+
+### Option 2: Use connected sources for accounts and opportunities
+
+Connected sources are data tables that are hosted by you in your own data warehouse and queried by Braze [CDI segments]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/cdi_segments/). Unlike catalogs, instead of duplicating your business objects (accounts and opportunities) in Braze, you’d be keeping them in your data warehouse and using your warehouse as the source of truth.
+
+To set up connected sources, refer to [Integrating connected sources]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/connected_sources#integrating-connected-sources).
+
+## Step 2: Relate your business objects to user profiles
+
+User profiles are the primary object in Braze, which power the majority of your demographic segmentation, triggering and personalization. User profiles include [default user data]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/) collected by our SDK and other sources, including [custom data]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/), which takes the form of either attributes (demographic data), events (behavioral data) or purchases (transactional data).
+
+### Step 2.1: Map sales CRM IDs to Braze
+
+First, make sure Braze and your CRM of choice have a common identifier to share data to. We suggest using the following table to map your sales CRM ID fields back to the Braze user object. The table below has Salesforce as the CRM system, but this can be done with any CRM.
+
+#### Braze object: User
+
+| Braze field | CRM object (Salesforce) | CRM field (Salesforce) | Additional information |
+| --- | --- | --- | --- |
+| `Aliases.salesforce_lead_id` | Lead | `id` |  - User alias label: `salesforce_lead_id` <br>- User alias name: `lead_id`|
+| `Aliases.salesforce_contact_id` | Contact | `id` | - User alias label: `salesforce_contact_id` <br>- User alias name: `contact_id` |
+| `AccountId` | Contact | `AccountId` | 
+| `OpportunityId` (optional, scalar) <br>or<br> `Opportunities` (optional, array) | Opportunity | `id` | 
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 }
+
+{% alert note %}
+We recommend using [aliases]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases) instead of `external_id` to map Salesforce lead and contact identifiers back to Braze. This is because it reduces the amount of lookups required when identifying and running your product-led growth style initiatives.
+{% endalert %}
+
+After you have your IDs in sync, you need to relate your Braze user profiles with your business objects. 
+
+### Step 2.2: Create a relationship between user profiles and your business objects
+
+#### Option 1: When using catalogs for business objects
+
+Now that your opportunity and account details are accounted for as Braze catalogs, you need to create a relationship between those catalogs and the user profiles you want to send messages to. Currently, this requires two steps:
+
+1. Include the account (such as `account_id (string)`), opportunity ID (such as `opportunity_ids (array)`), or both on the user profile as attributes.
+2. Log an event (such as `account_linked`) that includes the account ID as an event property.
+
+```json
+{
+  "attributes" : [
+    {
+      "external_id" : "user1",
+      "accountId" : "001J7000004K7AF",
+      "opportunityIds" : [
+"0064J000004EU59",
+"0064J000004EU5G"
+]
+    }
+  ],
+  "events" : [
+    {
+      "external_id" : "user1",
+      "name" : "account_linked",
+      "time" : "2013-07-16T19:20:45+01:00",
+      "properties": {
+        "account_id": "xyz123"
+      }
+    }
+  ]
+}
+```
+
+#### Option 2: When using connected sources
+
+One of your connected source’s tables should include a `user_id` that matches the `external_user_id` set in Braze for your users. The user profile setup above uses your lead and `contact_ids` as your `external_id`, so you should ensure your lead/contact tables include these IDs.
+
+In addition to ensuring the IDs match, we recommend writing basic account-level data such as `account_id`, `opportunity_id`, and even common firmographic attributes such as `industry` to the user profiles for efficient segmentation and personalization.
\ No newline at end of file
diff --git a/_docs/_user_guide/data_and_analytics/query_builder.md b/_docs/_user_guide/data_and_analytics/query_builder.md
index 5a3706dca97..4b837de1a67 100644
--- a/_docs/_user_guide/data_and_analytics/query_builder.md
+++ b/_docs/_user_guide/data_and_analytics/query_builder.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Query Builder
 article_title: Query Builder
-page_order: 100
+page_order: 15
 page_type: reference
 description: "This reference article describes how to build reports using Braze data from Snowflake in the Query Builder."
 tool: Reports
@@ -96,6 +96,23 @@ FROM USERS_MESSAGES_EMAIL_SEND_SHARED
 WHERE to_date(to_timestamp_ntz(time)) >= DATEADD('month', -1, date_trunc('day',CURRENT_DATE()));
 ```
 
+If you query for the `CANVAS_ID`, `CANVAS_VARIATION_API_ID`, or `CAMPAIGN_ID`, their associated name columns will automatically be included in the results table. You don’t need to include them in the `SELECT` query itself.
+
+| ID name | Associated name column |
+| --- | --- |
+| `CANVAS_ID` | Canvas Name |
+| `CANVAS_VARIATION_API_ID` | Canvas Variant Name |
+| `CAMPAIGN_ID` | Campaign Name |
+{: .reset-td-br-1 .reset-td-br-2 }
+
+This query retrieves all three IDs and their associated name columns with a maximum of 100 rows:
+
+```sql
+SELECT CANVAS_ID, CANVAS_VARIATION_API_ID, CAMPAIGN_ID
+FROM USERS_MESSAGES_EMAIL_SEND_SHARED 
+LIMIT 100
+```
+
 ### Troubleshooting
 
 Your query may fail for any of the following reasons:
@@ -164,7 +181,7 @@ All four types are shown if both `start_date` and `end_date` are used with the s
 | Start date | Specifies a start date | Requires `start_date` |
 | End date | Specifies an end date | Requires `end_date` |
 | Date range | Specifies both a start and end date | Requires both `start_date` and `end_date` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 - **Replacement value:** Replaces `start_date` and `end_date` with a Unix timestamp in seconds for a specified date in UTC, such as `1696517353`.
 - **Usage example:** For all of relative, start date, end date, and date range variables:
diff --git a/_docs/_user_guide/data_and_analytics/query_builder/query_templates.md b/_docs/_user_guide/data_and_analytics/query_builder/query_templates.md
index 93126e78c5f..80551dfca9a 100644
--- a/_docs/_user_guide/data_and_analytics/query_builder/query_templates.md
+++ b/_docs/_user_guide/data_and_analytics/query_builder/query_templates.md
@@ -10,7 +10,7 @@ tool: Reports
 
 # Query Builder templates
 
-> Access [Query Builder]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/) templates by selecting **Query Template** when creating a report. All templates surface data from up to the last 60 days, but you can directly edit that and other values in the editor.
+> Access [Query Builder]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/) templates by selecting **Query Template** when creating a report. All templates surface data from up to the last 60 days, but you can directly edit that and other values in the editor.<br><br>For definitions of the metrics that may appear in your Query Builder reports, refer to the [Report Metrics Glossary]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics) and filter by the respective channel.
 
 ## Channel templates
 
diff --git a/_docs/_user_guide/data_and_analytics/report_metrics.md b/_docs/_user_guide/data_and_analytics/report_metrics.md
index 47275954e88..250ddaf76d0 100644
--- a/_docs/_user_guide/data_and_analytics/report_metrics.md
+++ b/_docs/_user_guide/data_and_analytics/report_metrics.md
@@ -24,7 +24,19 @@ tool: Reports
 Email
 {% endapitags %}
 
-The total number of users who clicked into the AMP version of your AMP HTML Email.
+{% multi_lang_include metrics.md metric='AMP Clicks' %}
+
+{% endapi %}
+
+{% api %}
+
+### AMP Opens
+
+{% apitags %}
+Email
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='AMP Opens' %}
 
 {% endapi %}
 
@@ -36,7 +48,9 @@ The total number of users who clicked into the AMP version of your AMP HTML Emai
 All
 {% endapitags %}
 
-The percentage of users who received a particular message. This number is received from Braze.
+{% multi_lang_include metrics.md metric='Audience' %}
+
+<span class="calculation-line">Calculation: (Number of Recipients in Variant) / (Unique Recipients)</span>
 
 {% endapi %}
 
@@ -48,9 +62,27 @@ The percentage of users who received a particular message. This number is receiv
 Email, Web Push, iOS Push
 {% endapitags %}
 
-The total number of unsuccessful messages. This could occur because there isn't a valid push token, the email addresses were incorrect or deactivated, or the user unsubscribed after the campaign was launched. An email bounce for customers using SendGrid consists of hard bounces, spam, and emails sent to invalid addresses.
+{% multi_lang_include metrics.md metric='Bounces' %} This could occur because there isn't a valid push token, the user unsubscribed after the campaign was launched, or the email address is inaccurate or deactivated.
+
+#### Email
+
+An email bounce for customers using SendGrid consists of hard bounces, spam (`spam_report_drops`), and emails sent to invalid addresses (`invalid_emails`).
+
+For email, *Bounce %* or *Bounce Rate* is the percentage of messages that were unsuccessfully sent or designated as "returned" or "not received" from send services used or not received by the intended emailable users.
+
+#### Push
 
-<span class="calculation-line">Calculation: (Bounces) / (Sends)</span>
+These users have been automatically unsubscribed from all future push notifications. 
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><i>Bounces</i> :Count</li>
+        <li><i>Bounce %</i> or <i>Bounce Rate %</i>: (Sends - Bounces) / (Sends)</li>
+    </ul>
+</span>
+{:/}
 
 {% endapi %}
 
@@ -62,7 +94,7 @@ The total number of unsuccessful messages. This could occur because there isn't
 iOS Push, Android Push
 {% endapitags %}
 
-Push Story Notifications record a body click when the notification is clicked. It will not be recorded when a message is expanded, or for action button clicks.
+{% multi_lang_include metrics.md metric='Body Click' %}
 
 <span class="calculation-line">Calculation: (Body Clicks) / (Impressions)</span>
 
@@ -76,10 +108,7 @@ Push Story Notifications record a body click when the notification is clicked. I
 In-App Message
 {% endapitags %}
 
-Occurs when someone clicks on any of the following in-app message types:
-- Slide-up
-- Modal
-- Fullscreen that has no buttons
+{% multi_lang_include metrics.md metric='Body Clicks' %} For more details, refer to the SDK changelogs for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/changelog/objc_changelog#3310) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/changelog#1100).
 
 <span class="calculation-line">Calculation: (Body Clicks) / (Impressions)</span>
 
@@ -93,7 +122,7 @@ Occurs when someone clicks on any of the following in-app message types:
 In-App Message
 {% endapitags %}
 
-The total number of clicks on Button 1 of the message.
+{% multi_lang_include metrics.md metric='Button 1 Clicks' %}
 
 <span class="calculation-line">Calculation: (Button 1 Clicks) / (Impressions)</span>
 
@@ -107,7 +136,7 @@ The total number of clicks on Button 1 of the message.
 In-App Message
 {% endapitags %}
 
-The total number of clicks on Button 2 of the message.
+{% multi_lang_include metrics.md metric='Button 2 Clicks' %}
 
 <span class="calculation-line">Calculation: (Button 2 Clicks) / (Impressions)</span>
 
@@ -121,7 +150,7 @@ The total number of clicks on Button 2 of the message.
 In-App Message
 {% endapitags %}
 
-The total number of choices selected when the user clicks the submit button on the survey question page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/).
+{% multi_lang_include metrics.md metric='Choices Submitted' %}
 
 {% endapi %}
 
@@ -133,7 +162,7 @@ The total number of choices selected when the user clicks the submit button on t
 Email
 {% endapitags %}
 
-The percentage of opened emails that were clicked. This metric is only available in the [Report Builder]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/).
+{% multi_lang_include metrics.md metric='Click-to-Open Rate' %}
 
 <span class="calculation-line">Calculation: (Unique Clicks) / (Unique Opens) (for Email)</span>
 
@@ -147,7 +176,7 @@ The percentage of opened emails that were clicked. This metric is only available
 SMS
 {% endapitags %}
 
-The carrier has confirmed that the SMS was delivered to the target phone number. As a Braze customer, deliveries are charged toward your SMS allotment.
+{% multi_lang_include metrics.md metric='Confirmed Deliveries' %} As a Braze customer, deliveries are charged toward your SMS allotment. 
 
 <span class="calculation-line">Calculation: Count</span>
 
@@ -161,7 +190,7 @@ The carrier has confirmed that the SMS was delivered to the target phone number.
 Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS, WhatsApp
 {% endapitags %}
 
-The percentage of confidence that a certain variant of a message is outperforming the control group.
+{% multi_lang_include metrics.md metric='Confidence' %}
 
 {% endapi %}
 
@@ -173,7 +202,7 @@ The percentage of confidence that a certain variant of a message is outperformin
 In-App Message
 {% endapitags %}
 
-The total clicks on the call to action button on the confirmation page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/).
+{% multi_lang_include metrics.md metric='Confirmation Page Button' %}
 
 {% endapi %}
 
@@ -185,7 +214,7 @@ The total clicks on the call to action button on the confirmation page of a [sim
 In-App Message
 {% endapitags %}
 
-The total clicks on the close (x) button on the confirmation page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/).
+{% multi_lang_include metrics.md metric='Confirmation Page Dismissals' %}
 
 {% endapi %}
 
@@ -197,7 +226,29 @@ The total clicks on the close (x) button on the confirmation page of a [simple s
 Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS
 {% endapitags %}
 
-Additional conversion events added after the primary conversion event. The number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign. <br><br> This defined event is determined by the marketer when building the campaign. For email, push, and webhooks, we start tracking conversions after the initial send. For Content Cards and in-app messages, this count begins when they view a Content Card or message for the first time.
+{% multi_lang_include metrics.md metric='Conversions (B, C, D)' %} This defined event is determined by the marketer when building the campaign. For email, push, and webhooks, we start tracking conversions after the initial send. For Content Cards, this count begins when they view a Content Card for the first time.
+
+#### In-app messages
+
+For in-app messages, a conversion is counted if the user has received and viewed the in-app message campaign, and subsequently performs the specific conversion event within the defined conversion window, regardless of whether they clicked on the message or not.
+
+Conversions are attributed to the most recently received message. If re-eligibility is enabled, the conversion will be assigned to the latest in-app message received, provided that it occurs within the defined conversion window. However, if the in-app message has already been assigned a conversion, then the new conversion cannot be logged for that specific message. This means that each in-app message delivery is associated with only one conversion.
+
+{% endapi %}
+
+{% api %}
+
+### Total Conversions
+
+{% apitags %}
+In-App Message
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Total Conversions' %}
+
+When a user views an in-app message campaign only once, only one conversion is counted, even if they perform the conversion event multiple times later on. However, if re-eligibility is turned on and the user sees the in-app message campaign multiple times, *Total Conversions* can increase once for each time the user logs an impression for a new instance of the in-app message campaign. 
+
+For example, if a user triggers an in-app message twice and converts after each in-app message impression (resulting in two conversions), then *Total Conversions* will increase by two. However, if there was only one in-app message impression followed by two conversion events, only one conversion will be logged, and *Total Conversions* will increase by one.
 
 {% endapi %}
 
@@ -209,9 +260,23 @@ Additional conversion events added after the primary conversion event. The numbe
 Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS
 {% endapitags %}
 
-The percentage of times a defined event occurred compared to all recipients of a sent message. This defined event is determined when you build the campaign.
+{% multi_lang_include metrics.md metric='Conversion Rate' %}
 
-<span class="calculation-line">Calculation: (Primary Conversions) / (Unique Recipients)</span>
+#### In-app messages
+
+The metric of total daily <i>Unique Impressions</i> is used to calculate the <i>Conversion Rate</i> for in-app messages.
+
+Impressions for in-app messages can only be counted once per day. On the other hand, the number of times a user completes a desired action (a "conversion") can increase within a 24-hour period. While conversions can happen more than once per day, impressions cannot. Therefore, if a user completes a conversion multiple times within a day, the <i>Conversion Rate</i> can increase accordingly, but impressions will only be counted once.
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><b>In-App Messages</b>: (Primary Conversions) / (Unique Impressions)</li>
+        <li><b>Other Channels</b>: (Primary Conversions) / (Unique Recipients)</li>
+    </ul>
+</span>
+{:/}
 
 {% endapi %}
 
@@ -223,7 +288,7 @@ The percentage of times a defined event occurred compared to all recipients of a
 All
 {% endapitags %}
 
-The number of days after receiving the message during which user actions are tracked and attributed to a conversion event. Conversions that occur after this window are not attributed to the conversion event.
+{% multi_lang_include metrics.md metric='Conversion Window' %}
 
 {% endapi %}
 
@@ -235,9 +300,17 @@ The number of days after receiving the message during which user actions are tra
 Email, Web Push, iOS Push, Android Push, WhatsApp
 {% endapitags %}
 
-The total number of message requests that are accepted by the receiving server. This doesn't mean the message was delivered to a device, only that the message was accepted by the server.
+{% multi_lang_include metrics.md metric='Deliveries' %} For emails, *Deliveries* is the total number of messages (Sends) successfully sent to and received by emailable parties.
 
-<span class="calculation-line">Calculation: Count</span>
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><i>Deliveries</i>: Count</li>
+        <li><i>Deliveries %</i>: (Sends - Bounces) / (Sends)</li>
+    </ul>
+</span>
+{:/}
 
 {% endapi %}
 
@@ -249,7 +322,9 @@ The total number of message requests that are accepted by the receiving server.
 SMS
 {% endapitags %}
 
-The SMS could not be sent due to queues overflow (sending SMS at a rate higher than your long or short codes can handle).
+{% multi_lang_include metrics.md metric='Delivery Failures' %}
+
+Reach out to <a href="/docs/braze_support/">Braze Support</a> for assistance in understanding the reasons for delivery failures.
 
 <span class="calculation-line">Calculation: (Sends) - (Sends to Carrier)</span>
 
@@ -263,7 +338,7 @@ The SMS could not be sent due to queues overflow (sending SMS at a rate higher t
 iOS Push
 {% endapitags %}
 
-The total number (and percentage) of push notifications that were directly opened from that push.
+{% multi_lang_include metrics.md metric='Direct Opens' %}
 
 <span class="calculation-line">Calculation: (Direct Opens) / (Deliveries)</span>
 
@@ -271,13 +346,39 @@ The total number (and percentage) of push notifications that were directly opene
 
 {% api %}
 
+### Emailable
+
+{% apitags %}
+Email
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Emailable' %}
+
+<span class="calculation-line">Calculation: Count</span>
+
+{% endapi %}
+
+{% api %}
+
 ### Errors
 
 {% apitags %}
 Webhook
 {% endapitags %}
 
-The number of errors returned by webhook events (incremented during the sending process).
+{% multi_lang_include metrics.md metric='Errors' %} Errors are included in the <i>Sends</i> count but are not included in the <i>Unique Recipients</i> count.
+
+{% endapi %}
+
+{% api %}
+
+### Estimated Real Opens
+
+{% apitags %}
+Email
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Estimated Real Opens' %}
 
 {% endapi %}
 
@@ -289,7 +390,35 @@ The number of errors returned by webhook events (incremented during the sending
 WhatsApp
 {% endapitags %}
 
-The WhatsApp message couldn't send because the internet service provider returned a hard bounce. A hard bounce signifies a permanent deliverability failure.
+{% multi_lang_include metrics.md metric='Failures' %} Failures are included in the <i>Sends</i> count but not in the <i>Deliveries</i> count.</td>
+
+<span class="calculation-line">Calculation (<i>Failure Rate</i>): (Failures) / (Sends)</span>
+
+{% endapi %}
+
+{% api %}
+
+### Hard Bounce
+
+{% apitags %}
+Email
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Hard Bounce' %} 
+
+When this occurs, Braze marks the email address as invalid but does not update the user's [subscription status]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/). If an email receives a hard bounce, we will stop any future requests to this email address.
+
+{% endapi %}
+
+{% api %}
+
+### Help
+
+{% apitags %}
+SMS
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Help' %} A user reply is measured anytime a user sends an inbound message within four hours of receiving your message.
 
 {% endapi %}
 
@@ -301,7 +430,7 @@ The WhatsApp message couldn't send because the internet service provider returne
 iOS Push, Android Push
 {% endapitags %}
 
-The total number (and percentage) of users who opened the app after the push notification was sent, without directly opening the push.
+{% multi_lang_include metrics.md metric='Influenced Opens' %}
 
 <span class="calculation-line">Calculation: (Influenced Opens) / (Deliveries)</span>
 
@@ -309,13 +438,61 @@ The total number (and percentage) of users who opened the app after the push not
 
 {% api %}
 
+### Machine Opens
+
+{% apitags %}
+Email
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Machine Opens' %} This metric is tracked starting November 11, 2021 for SendGrid and December 2, 2021 for SparkPost.
+
+{% endapi %}
+
+{% api %}
+
+### Opens
+
+{% apitags %}
+Web Push, iOS Push, Android Push
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Opens' %}
+
+{% endapi %}
+
+{% api %}
+
+### Opt-Out
+
+{% apitags %}
+SMS
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Opt-Out' %} A user reply is measured anytime a user sends an inbound message within four hours of receiving your message.
+
+{% endapi %}
+
+{% api %}
+
+### Other Opens
+
+{% apitags %}
+Email
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Other Opens' %} Note that a user can also open an email (such as the open counts toward Other Opens) before a Machine Opens count is logged. If a user opens an email once (or more) after a machine open event from a non-Apple Mail inbox, then the amount of times that the user opens the email is calculated toward Other Opens and only once toward Unique Opens.
+
+{% endapi %}
+
+{% api %}
+
 ### Pending Retry
 
 {% apitags %}
 Email
 {% endapitags %}
 
-The number of requests that were temporarily rejected, by the receiving server, but still attempted for re-delivery by the email service provider (ESP). The ESP will retry delivery until a timeout period is reached (typically after 72 hours).
+{% multi_lang_include metrics.md metric='Pending Retry' %}
 
 {% endapi %}
 
@@ -327,7 +504,17 @@ The number of requests that were temporarily rejected, by the receiving server,
 Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS, WhatsApp
 {% endapitags %}
 
-The number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign. This defined event is determined by the marketer when building the campaign. <br><br>For email, push, and webhooks, we start tracking conversions after the initial send. For Content Cards and in-app messages, this count begins when they view a Content Card or message for the first time.
+{% multi_lang_include metrics.md metric='Primary Conversions (A) or Primary Conversion Event' %} For email, push, and webhooks, we start tracking conversions after the initial send. For Content Cards and in-app messages, this count begins when they view a Content Card or message for the first time.
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><i>Primary Conversions (A) or Primary Conversion Event</i>: Count</li>
+        <li><i>Primary Conversions (A) %</i> or <i>Primary Conversion Event Rate</i>: (Primary Conversions) / (Unique Recipients)</li>
+    </ul>
+</span>
+{:/}
 
 {% endapi %}
 
@@ -339,7 +526,7 @@ The number of times a defined event occurred after interacting with or viewing a
 WhatsApp
 {% endapitags %}
 
-When the user reads the WhatsApp message. The user's read receipts must be "On" for Braze to track reads.
+{% multi_lang_include metrics.md metric='Reads' %}
 
 {% endapi %}
 
@@ -351,10 +538,12 @@ When the user reads the WhatsApp message. The user's read receipts must be "On"
 Email, Content Cards, In-App Message, Web Push, iOS Push, Android Push, SMS, WhatsApp
 {% endapitags %}
 
+{% multi_lang_include metrics.md metric='Received' %} 
+
 - Content Cards: Received when users view the card in the app.
 - Push: Received when messages are sent from the Braze server to the push provider.
 - Email: Received when messages are sent from the Braze server to the email service provider.
-- SMS/MMS: "Delivered" after the SMS provider receives confirmation from the upstream carrier and destination device.
+- SMS/MMS: “Delivered” after the SMS provider receives confirmation from the upstream carrier and destination device.
 - In-app message: Received at the time of display based on the trigger action defined.
 - WhatsApp: Received at the time of display based on the trigger action defined.
 
@@ -368,7 +557,33 @@ Email, Content Cards, In-App Message, Web Push, iOS Push, Android Push, SMS, Wha
 SMS
 {% endapitags %}
 
-The SMS has been rejected by the carrier. This can happen for several reasons, including carrier content filtering, availability of the destination device, the phone number is no longer in service, and similar. As a Braze customer, rejections are charged toward your SMS allotment.
+{% multi_lang_include metrics.md metric='Rejections' %} As a Braze customer, rejections are charged toward your SMS allotment.
+
+<span class="calculation-line">Calculation: Count</span>
+
+{% endapi %}
+
+{% api %}
+
+### Revenue
+
+{% apitags %}
+Email
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Revenue' %}
+
+{% endapi %}
+
+{% api %}
+
+### Sent
+
+{% apitags %}
+SMS
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Sent' %}
 
 <span class="calculation-line">Calculation: Count</span>
 
@@ -382,10 +597,13 @@ The SMS has been rejected by the carrier. This can happen for several reasons, i
 Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS, WhatsApp, LINE
 {% endapitags %}
 
-*Sends*, or *Messages Sent*, is the total number of messages sent in a campaign. After launching a scheduled campaign, this metric will include all messages sent, regardless of whether they have been sent out yet due to rate limiting. This doesn't mean the message was received or delivered to a device, only that the message was sent. This metric is provided by Braze.
+{% multi_lang_include metrics.md metric='Sends' %} This metric is provided by Braze. Note that upon launching a scheduled campaign, this metric will include all messages sent, regardless of whether they have been sent out yet due to rate limiting.
 
 {% alert tip %}
-For Content Cards, this metric is calculated differently depending on what you selected for **Card creation**. See [Card creation]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/) for details.
+For Content Cards, this metric is calculated differently depending on what you selected for [Card creation]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/):
+
+- **At launch or step entry:** The number of cards created and available to be seen. This doesn't count whether the users viewed the card.
+- **At first impression:** The number of cards displayed to users.
 {% endalert %}
 
 <span class="calculation-line">Calculation: Count</span>
@@ -394,17 +612,34 @@ For Content Cards, this metric is calculated differently depending on what you s
 
 {% api %}
 
-### Sends to Carrier
+### Messages Sent
 
 {% apitags %}
-SMS
+Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS, WhatsApp, LINE
 {% endapitags %}
 
-{% alert note %}
-*Sends to Carrier* is deprecated, but will continue to be supported for users that already have it.
+{% multi_lang_include metrics.md metric='Messages Sent' %}  This metric is provided by Braze. Note that upon launching a scheduled campaign, this metric will include all messages sent, regardless of whether they have been sent out yet due to rate limiting.
+
+{% alert tip %}
+For Content Cards, this metric is calculated differently depending on what you selected for [Card creation]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/):
+
+- **At launch or step entry:** The number of cards created and available to be seen. This doesn't count whether the users viewed the card.
+- **At first impression:** The number of cards displayed to users.
 {% endalert %}
 
-The sum of Confirmed Deliveries, Rejections, and Sends where delivery or rejection wasn't confirmed by the carrier. This includes instances where carriers don't provide delivery or rejected confirmation, as some carriers don't provide this confirmation or can't do so at the time of send.
+<span class="calculation-line">Calculation: Count</span>
+
+{% endapi %}
+
+{% api %}
+
+### Sends to Carrier
+
+{% apitags %}
+SMS
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Sends to Carrier' %} 
 
 <span class="calculation-line">Calculation: Count</span>
 
@@ -412,15 +647,35 @@ The sum of Confirmed Deliveries, Rejections, and Sends where delivery or rejecti
 
 {% api %}
 
+### Soft Bounce
+
+{% apitags %}
+Email
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Soft Bounce' %} If an email receives a soft bounce, we will usually retry within 72 hours, but the number of retry attempts varies from receiver to receiver.
+
+{% endapi %}
+
+{% api %}
+
 ### Spam
 
 {% apitags %}
 Email
 {% endapitags %}
 
-The total number of emails delivered that were marked as "spam."
+{% multi_lang_include metrics.md metric='Spam' %}
 
-<span class="calculation-line">Calculation: (Marked as Spam) / (Sends)</span>
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><i>Spam</i>: Count</li>
+        <li><i>Spam %</i> or <i>Spam Rate %</i>: (Marked as Spam) / (Sends)</li>
+    </ul>
+</span>
+{:/}
 
 {% endapi %}
 
@@ -432,7 +687,7 @@ The total number of emails delivered that were marked as "spam."
 In-App Message
 {% endapitags %}
 
-The total clicks on the close (x) button on the survey question page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/).
+{% multi_lang_include metrics.md metric='Survey Page Dismissals' %}
 
 {% endapi %}
 
@@ -444,7 +699,7 @@ The total clicks on the close (x) button on the survey question page of a [simpl
 In-App Message
 {% endapitags %}
 
-The total clicks on the submit button of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/).
+{% multi_lang_include metrics.md metric='Survey Submissions' %}
 
 {% endapi %}
 
@@ -456,7 +711,7 @@ The total clicks on the submit button of a [simple survey]({{site.baseurl}}/user
 Email, Content Cards, SMS, LINE
 {% endapitags %}
 
-The total number (and percentage) of users who clicked within the delivered email, card, or message. For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached.
+{% multi_lang_include metrics.md metric='Total Clicks' %} For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached. For AMP emails, this is the total clicks in the HTML and plaintext versions.
 
 {::nomarkdown}
 <span class="calculation-line">
@@ -479,7 +734,7 @@ The total number (and percentage) of users who clicked within the delivered emai
 Content Cards
 {% endapitags %}
 
-The number of times Content Cards from a campaign have been dismissed. If a user dismisses a message twice, they will be only counted once.
+{% multi_lang_include metrics.md metric='Total Dismissals' %}
 
 <span class="calculation-line">Calculation: Count</span>
 
@@ -493,7 +748,9 @@ The number of times Content Cards from a campaign have been dismissed. If a user
 In-App Message, Content Cards
 {% endapitags %}
 
-The number of times the in-app message has been viewed (if a user is shown a message twice, they will be counted twice). This number is a sum of the number of impression events that Braze receives from the SDKs.
+{% multi_lang_include metrics.md metric='Total Impressions' %} For Content Cards, this is the total count of impressions logged for a given Content Card. This can increment multiple times for the same user.
+
+For in-app messages, if there are multiple devices and re-eligibility is off, the user should only see the in-app message once. Even if the user uses multiple devices, they will only see it on the first device that is targeted. This assumes that the profile has consolidated devices and a user has one user ID that they are logged into across devices. If re-eligibility is on an impression is logged for every time that user sees the in-app message.
 
 <span class="calculation-line">Calculation: Count</span>
 
@@ -507,7 +764,7 @@ The number of times the in-app message has been viewed (if a user is shown a mes
 Email, iOS Push, Android Push, Web Push, LINE
 {% endapitags %}
 
-The total number of messages that were opened. For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached.
+{% multi_lang_include metrics.md metric='Total Opens' %}  For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached. For AMP emails, this is the total opens for the HTML and plaintext versions. 
 
 {::nomarkdown}
 <span class="calculation-line">
@@ -520,7 +777,6 @@ The total number of messages that were opened. For LINE, this is tracked after a
 </span>
 {:/}
 
-
 {% endapi %}
 
 {% api %}
@@ -531,7 +787,7 @@ The total number of messages that were opened. For LINE, this is tracked after a
 Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS, WhatsApp
 {% endapitags %}
 
-The total revenue in dollars from campaign recipients within the set primary conversion window. This metric is only available on Campaign Comparison Reports, via the [Report Builder]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/).
+{% multi_lang_include metrics.md metric='Total Revenue' %} This metric is only available on Campaign Comparison Reports through the <a href='https://braze.com/docs/user_guide/data_and_analytics/reporting/report_builder/'>Report Builder</a>
 
 {% endapi %}
 
@@ -543,16 +799,15 @@ The total revenue in dollars from campaign recipients within the set primary con
 Email, Content Cards, LINE
 {% endapitags %}
 
-The distinct number of recipients who have clicked within a message at least once. This is tracked over a 7-day period for Email. This includes clicks on Braze-provided unsubscribe links.
-
-For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached. 
+{% multi_lang_include metrics.md metric='Unique Clicks' %} This is tracked over a seven-day period for email. This includes clicks on Braze-provided unsubscribe links. For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached.
 
 {::nomarkdown}
 <span class="calculation-line">
     Calculation:
     <ul>
-        <li><b>Email:</b> (Unique Clicks) / (Deliveries)</li>
-        <li><b>Content Cards:</b> (Unique Clicks) / (Unique Impressions)</li>
+        <li><i>Unique Clicks</i>: Count</li>
+        <li><b>Content Cards</b> <i>Unique Clicks %</i> or <i>Unique Clicks Rate</i>: (Unique Clicks) / (Unique Impressions)</li>
+        <li><b>Email</b> <i>Unique Clicks %</i> or <i>Unique Clicks Rate</i>: (Unique Clicks) / (Deliveries)</li>
     </ul>
 </span>
 {:/}
@@ -567,7 +822,7 @@ For LINE, this is tracked after a minimum threshold of 20 messages per day has b
 Content Cards
 {% endapitags %}
 
-The number of users who have dismissed Content Cards from a campaign. A user dismissing a Content Card from a campaign multiple times represents one unique dismissal.
+{% multi_lang_include metrics.md metric='Unique Dismissals' %}
 
 <span class="calculation-line">Calculation: (Unique Dismissals) / (Unique Impressions)</span>
 
@@ -581,7 +836,7 @@ The number of users who have dismissed Content Cards from a campaign. A user dis
 In-App Message, Content Cards
 {% endapitags %}
 
-The total number of users who received and viewed a given in-app message or card in a day. For in-app messages, unique impressions can be incremented again after 24 hours if re-eligibility is on and a user performs the trigger action. Conversely, the count should not increment the second time a user views a Content Card. This number is received from Braze.
+{% multi_lang_include metrics.md metric='Unique Impressions' %} For in-app messages, unique impressions can be incremented again after 24 hours if re-eligibility is on and a user performs the trigger action. If re-eligibilty is on, <i>Unique Impressions</i> = <i>Unique Recipients</i>. <br><br>For Content Cards, the count should not increment the second time a user views a card. 
 
 <span class="calculation-line">Calculation: Count</span>
 
@@ -595,9 +850,17 @@ The total number of users who received and viewed a given in-app message or card
 Email, LINE
 {% endapitags %}
 
-This is the total number of delivered emails that have been opened by a single user at least once and are tracked over a 7-day period. For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached.
+{% multi_lang_include metrics.md metric='Unique Opens' %} For email, this is tracked over a 7 day period. For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached.
 
-<span class="calculation-line">Calculation: (Unique Opens) / (Deliveries)</span>
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><i>Unique Opens</i>: Count</li>
+        <li><i>Unique Opens %</i> or <i>Unique Open Rate</i>: (Unique Opens) / (Deliveries)</li>
+    </ul>
+</span>
+{:/}
 
 {% endapi %}
 
@@ -609,7 +872,9 @@ This is the total number of delivered emails that have been opened by a single u
 All
 {% endapitags %}
 
-The number of unique daily recipients, or users who received a particular message in a day. This number is received from Braze and is based on the `user_id`.
+{% multi_lang_include metrics.md metric='Unique Recipients' %}
+
+Because a viewer can be a unique recipient every day, you should expect this to be higher than <i>Unique Impressions</i>. This number is received from Braze and is based on the `user_id`.
 
 <span class="calculation-line">Calculation: Count</span>
 
@@ -617,13 +882,35 @@ The number of unique daily recipients, or users who received a particular messag
 
 {% api %}
 
+### Unsubscribers or Unsub
+
+{% apitags %}
+Email
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Unsubscribers or Unsub' %}
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><i>Unsubscribers</i> or <i>Unsub</i>: Count</li>
+        <li><i>Unsubscribers %</i> or <i>Unsub Rate</i>: (Unsubscribes) / (Deliveries)</li>
+    </ul>
+</span>
+{:/}
+
+{% endapi %}
+
+{% api %}
+
 ### Unsubscribes
 
 {% apitags %}
 Email
 {% endapitags %}
 
-The number of recipients whose subscription state changed to unsubscribed as a result of clicking the Braze provided unsubscribe URL.
+{% multi_lang_include metrics.md metric='Unsubscribes' %}
 
 <span class="calculation-line">Calculation: (Unsubscribes) / (Deliveries)</span>
 
@@ -637,8 +924,8 @@ The number of recipients whose subscription state changed to unsubscribed as a r
 Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS, WhatsApp
 {% endapitags %}
 
-Variation of a campaign, differing as defined by the creator.
+{% multi_lang_include metrics.md metric='Variation' %}
 
 <span class="calculation-line">Calculation: Count</span>
 
-{% endapi %}
+{% endapi %}
\ No newline at end of file
diff --git a/_docs/_user_guide/data_and_analytics/reporting/data_by_segments.md b/_docs/_user_guide/data_and_analytics/reporting/data_by_segments.md
index e6b7861a198..dc4c4a37c24 100644
--- a/_docs/_user_guide/data_and_analytics/reporting/data_by_segments.md
+++ b/_docs/_user_guide/data_and_analytics/reporting/data_by_segments.md
@@ -134,7 +134,7 @@ Your results will show purchase metrics by segment for the variants or steps you
 - **Columns:** Purchase metrics
 
 {% endtab %}
-{% tab Top/bottom messaging for email engagement %}
+{% tab Top or bottom messaging for email engagement %}
 
 ### Viewing metrics for the top or bottom performers
 
@@ -168,7 +168,7 @@ To view this report, you must specify the following variables in the **Variables
 Your results will show the top (or bottom) campaigns, Canvases, or Canvas steps that you selected. For example, if you selected the top 10 campaigns for click rate, your results will show the top 10 campaigns ordered from highest to lowest click rate. Your columns will display all of the email engagement metrics for each row (campaigns, Canvases, or Message steps).
 
 {% endtab %}
-{% tab Top/bottom messaging for purchases %}
+{% tab Top or bottom messaging for purchases %}
 
 ### Viewing metrics for the top or bottom performers
 
@@ -207,7 +207,7 @@ Your results will show the top (or bottom) campaigns, Canvases, or Canvas steps
 {% endtab %}
 {% tab Push performance by segment %}
 
-## Viewing push metrics for segments
+### Viewing push metrics for segments
 
 This report in the [Variables](#variables) tab displays push metrics broken down by segments. 
 
diff --git a/_docs/_user_guide/data_and_analytics/reporting/engagement_reports.md b/_docs/_user_guide/data_and_analytics/reporting/engagement_reports.md
index 61f7656a510..aaabf2c4991 100644
--- a/_docs/_user_guide/data_and_analytics/reporting/engagement_reports.md
+++ b/_docs/_user_guide/data_and_analytics/reporting/engagement_reports.md
@@ -73,7 +73,7 @@ The **Add Stats** step shows you statistics for the types of campaigns or Canvas
 | In-app message | Impressions, Clicks, First Button Clicks, Second Button Clicks |
 | Webhook  |  Sends, Errors |
 | SMS | Sends, Sends to Carrier, Confirmed Deliveries, Delivery Failures, Rejections |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 *Sends to Carrier* is deprecated, but will continue to be supported for users that already have it.
diff --git a/_docs/_user_guide/data_and_analytics/reporting/global_control_group_reporting.md b/_docs/_user_guide/data_and_analytics/reporting/global_control_group_reporting.md
index e5d941760c0..9f32aa27c73 100644
--- a/_docs/_user_guide/data_and_analytics/reporting/global_control_group_reporting.md
+++ b/_docs/_user_guide/data_and_analytics/reporting/global_control_group_reporting.md
@@ -45,6 +45,6 @@ Before May 2024, the Global Control Group was excluded from user archival, but t
 | Estimated Group Size | The estimated number of users in your control and treatment groups during selected time period. | The maximum membership size your control and treatment groups reached during the time period you chose for the report. |
 | Total Number of Events | The total number of times the selected event occurred during the chosen time period. This is not unique (for example, if a user performs an event twice during the time period, the event gets incremented twice). | Sum of the number of times an event occurred each day during the chosen time period. |
 | Events Per User | The estimated average number of times users in each group completed your conversion events during the selected time period. | Total events ÷ estimated group size. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 [6]: {% image_buster /assets/img/control_group/control_group6.png %}
\ No newline at end of file
diff --git a/_docs/_user_guide/data_and_analytics/reporting/report_builder.md b/_docs/_user_guide/data_and_analytics/reporting/report_builder.md
index e48eaee3195..d10d458bf3c 100644
--- a/_docs/_user_guide/data_and_analytics/reporting/report_builder.md
+++ b/_docs/_user_guide/data_and_analytics/reporting/report_builder.md
@@ -54,7 +54,7 @@ The following are the differences between these two options:
 | **Building Report** | You will be able to narrow down your campaign list using filters, and then check off specific campaigns. | You will build your report by using the filter options to narrow down your campaign list. |
 | **Saving and Viewing Report** | You can save your report. The next time you view it, you will be able to view the same campaign you previously added, as these campaigns still fall under your "Last Sent" filter. | You can save your report. The next time you view it, the report will automatically update to include all campaigns that currently match your filters. |
 | **Editing Report** | You can click Edit Report to add or delete campaigns from your report | You can edit your report by adjusting your filter criteria. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert note %} 
 Both **Manual** and **Automated** reports can include a maximum of 250 campaigns in a report. 
diff --git a/_docs/_user_guide/data_and_analytics/reporting/reports_overview.md b/_docs/_user_guide/data_and_analytics/reporting/reports_overview.md
index 58dceaf903b..bbcfcbca084 100644
--- a/_docs/_user_guide/data_and_analytics/reporting/reports_overview.md
+++ b/_docs/_user_guide/data_and_analytics/reporting/reports_overview.md
@@ -165,7 +165,7 @@ You can export the following statistics depending on your message channel:
 | In-app message | Impressions, Clicks, First Button Clicks, Second Button Clicks |
 | Webhook  |  Sends, Errors |
 | SMS | Sends, Sends to Carrier, Confirmed Deliveries, Delivery Failures, Rejections |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 More questions you can answer with this report:
 
diff --git a/_docs/_user_guide/data_and_analytics/reporting/retention_reports.md b/_docs/_user_guide/data_and_analytics/reporting/retention_reports.md
index 8a36c5f7b44..35c5d75fd78 100644
--- a/_docs/_user_guide/data_and_analytics/reporting/retention_reports.md
+++ b/_docs/_user_guide/data_and_analytics/reporting/retention_reports.md
@@ -138,7 +138,7 @@ Some use cases for showing performance by variant:
 - **Date Range**: Set on the Campaign or Canvas **Details** page, the date range includes all users who received the campaign or Canvas during this window, and of those users, the data of those that performed their retention event during the date range will appear in the report. Each day the retention rate, percentage change from the control group, and confidence are measured.
 - **Retention Rate**: Shows the retention rate by variant. The retention rate is equivalent to the number of users that performed the retention event divided by the total users that have received the campaign or Canvas.
 - **Percentage Change from Control**: Quantifies the percentage change per variant from the control group.
-- **Confidence**: Braze compares each variant's conversion rate against the control's conversion rate with a statistical procedure called a Z Test to calculate a [confidence]({{site.baseurl}}/user_guide/intelligence/multivariate_testing/#understanding-confidence) percentage. This percentage signifies how confidently that variant is performing better than the control group.
+- **Confidence**: {% multi_lang_include metrics.md metric='Confidence' %} Braze compares each variant's conversion rate against the control's conversion rate with a statistical procedure called a Z Test to calculate a [confidence]({{site.baseurl}}/user_guide/intelligence/multivariate_testing/#understanding-confidence) percentage.
 - **Units**: You can adjust the units between the percentage of users and the number of users in the upper right-hand corner of the chart, specific units may prove to be more significant when judging the impact of a campaign or Canvas.
 - **Variant Graph**: This graph summarizes the results by variant for the selected date range.
 
diff --git a/_docs/_user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data.md b/_docs/_user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data.md
index fddcd843aeb..29780096d39 100644
--- a/_docs/_user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data.md
+++ b/_docs/_user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data.md
@@ -29,14 +29,42 @@ When you turn [analytics tracking on for a segment][9], Braze will let you view
 
 You will see the following segment statistics, which update in real-time as you add or delete filters:
 
-| Statistic | Description |
-| --------- | --- |
-| **Total Users** | How many users your app has in total. |
-| **Selected Users** | How many users are in your segment and what percentage of your total user base they are. |
-| **LTV (Paying Users)** | The lifetime value per user (LTV) in this segment and the lifetime value per paying user in this segment. The LTV is calculated by dividing your lifetime revenue by lifetime users. |
-| **Emailable (Opted In)** | Emailable refers to all users who can be reached via email. These users have provided an email address and have not opted out. Opted In refers to users who have explicitly opted in to email. Due to [spam regulations][6], it's often a good idea to ask your users to explicitly opt-in by implementing a double opt-in policy where users must click a link in an initial confirmation email. To encourage more users to opt-in, you can target a message at [those who have neither opted in nor out][5]. |
-| **Push Enabled (Opted In)** | Push enabled refers to the number of users with at least one push token. Some users may have multiple push tokens (for example, if they own an iPhone and iPad), so the number of push notifications you send to this segment may be greater than the number of "push enabled" users. Opted In refers to the number of users who have explicitly opted in to push notifications. Users must always explicitly opt-in for you to send them pushes. |
-{: .reset-td-br-1 .reset-td-br-2}
+<style>
+    .no-split {
+        word-break: keep-all;
+    }
+</style>
+
+<table>
+    <thead>
+        <tr>
+            <th>Statistic</th>
+            <th>Definition</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td class="no-split">Total Users</td>
+            <td class="no-split">How many users your app has in total.</td>
+        </tr>
+        <tr>
+            <td class="no-split">Selected Users</td>
+            <td class="no-split">How many users are in your segment and what percentage of your total user base they are.</td>
+        </tr>
+        <tr>
+            <td class="no-split">LTV (Paying Users)</td>
+            <td class="no-split">The lifetime value per user (LTV) in this segment and the lifetime value per paying user in this segment. The LTV is calculated by dividing your lifetime revenue by lifetime users.</td>
+        </tr>
+        <tr>
+            <td class="no-split">Emailable (Opted-In)</td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Emailable' %} Due to <a href="/docs/help/best_practices/spam_regulations/#spam-regulationsspam regulations">spam regulations</a> it's often a good idea to ask your users to explicitly opt-in by implementing a double opt-in policy where users must click a link in an initial confirmation email. To encourage more users to opt-in, you can target a message at <a href="/docs/user_guide/message_building_by_channel/email/managing_user_subscriptions/#segmenting-by-user-subscriptions">those who have neither opted in nor out</a>.</td>
+        </tr>
+        <tr>
+            <td class="no-split">Push Enabled (Opted-In)</td>
+            <td class="no-split">Push enabled refers to the number of users with at least one push token. Some users may have multiple push tokens (for example, if they own an iPhone and iPad), so the number of push notifications you send to this segment may be greater than the number of "push enabled" users. Opted In refers to the number of users who have explicitly opted in to push notifications. Users must always explicitly opt-in for you to send them pushes.</td>
+        </tr>
+    </tbody>
+</table>
 
 ### Segment Insights
 
@@ -108,8 +136,6 @@ You won’t be able to access data from time periods prior to when this feature
 If your company turned on this feature on October 2, and turned on analytics tracking for Segment B on October 3, then you can only see data for Segment B for the campaigns and Canvases that recorded metrics after October 3.
 
 
-
-
 [1]: {% image_buster /assets/img_archive/segments.png %}
 [2]: {% image_buster /assets/img_archive/A_Tracking.png %}
 [3]: {{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/#creating-a-segment
diff --git a/_docs/_user_guide/data_and_analytics/user_data_collection/best_practices.md b/_docs/_user_guide/data_and_analytics/user_data_collection/best_practices.md
index d05c9747059..cda1dea3d2c 100644
--- a/_docs/_user_guide/data_and_analytics/user_data_collection/best_practices.md
+++ b/_docs/_user_guide/data_and_analytics/user_data_collection/best_practices.md
@@ -23,18 +23,8 @@ If an unknown user were to view your site and then, at a later date, create an a
 
 When a user enters content through a web form, check if a user with that email already exists within your database. This can be done in one of two ways:
 
-- **Check internal database (recommended):** If you have an external record or database containing the provided user information that exists outside of Braze, reference this at the time of email submission or account creation to confirm the information hasn't already been captured.<br><br>
-- **[`/users/export/id` endpoint]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/):** Run the following call and check if the returned users array is empty or contains a value:
-  ```json
-  --data-raw '{
-    "email_address": "example@braze.com",
-    "fields_to_export": ["external_id", "user_aliases"]
-  }'
-  ```
-
-{% alert important %}
-We recommend that you lightly use this endpoint when querying a single user, as we apply a rate limit of 2,500 requests per minute to this endpoint. For more information on endpoint rate limits, refer to [Rate limits by request type]({{site.baseurl}}/api/api_limits/#rate-limits-by-request-type).
-{% endalert %}
+- **Check internal database (recommended):** If you have an external record or database containing the provided user information that exists outside of Braze, reference this at the time of email submission or account creation to confirm the information hasn't already been captured.
+- **[`/users/track` endpoint]({{site.baseurl}}/api/endpoints/user_data/post_user_track/):** Use `email` as an identifier, and a new user profile will be created if the email address doesn't exist yet.
 
 ### Step 2: Log or update user
 
@@ -69,7 +59,9 @@ As your user data grows, you can merge duplicate user profiles from the Braze da
 
 You can also use the [Merge users endpoint]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/) to merge one user profile into another. 
 
-Note that after user profiles are merged, this action cannot be undone.
+{% alert note %}
+After user profiles are merged, this action cannot be undone.
+{% endalert %}
 
 ## Additional resources
 - Check out our article on the Braze [user profile lifecycle]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/) for additional context.<br>
diff --git a/_docs/_user_guide/data_and_analytics/user_data_collection/sdk_data_collection.md b/_docs/_user_guide/data_and_analytics/user_data_collection/sdk_data_collection.md
index d8cb892af9f..c320964f76d 100644
--- a/_docs/_user_guide/data_and_analytics/user_data_collection/sdk_data_collection.md
+++ b/_docs/_user_guide/data_and_analytics/user_data_collection/sdk_data_collection.md
@@ -32,7 +32,7 @@ The following lists the strictly necessary data generated and received by Braze
 | SDK message interaction data | Push direct opens, in-app message interactions, Content Card interactions | This attribute is used for quality control purposes, like checking that a message was received and that sending isn't duplicated. |
 | SDK version | Current SDK version | This attribute is used to only send messages to compatible devices and avoid service disruption. |
 | Session ID and session timestamp | Session identifier, a randomly generated string and session timestamp | Used to determine whether the user is starting a new or existing session and to determine re-eligibility of messages intended for this user.<br><br>Certain messaging channels such as in-app messages and Content Cards are synchronized to the device upon session start. Our backend will then use data related to when it last contacted Braze servers (which the device stores and sends back) to know if the user is eligible for any new messages.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ### Calculated metrics
 
@@ -55,7 +55,7 @@ Calculated metrics include the following attributes.
 | Received message from campaign with tag        | Boolean. This filter targets users based on whether they have received a campaign that currently has a tag.                  |
 | Retarget campaign                              | Boolean. This filter targets users based on whether they have opened or clicked on a specific email, push, or in-app message in the past. |
 | Uninstalled                                    | Boolean and time |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert important %}
 If you're interested in only the minimum integration, and you integrate with mParticle, Segment, Tealium, or GTM, note the following:
@@ -79,7 +79,7 @@ In addition to the minimum integration data, the following attributes are automa
 | Resolution              | Android, iOS, Web | Device or browser resolution                                                          | Optionally used for device-based message targeting. The format of this value is "`<width>`x`<height>`".                                                                 |
 | Time zone               | Android, iOS, Web | Device or browser time zone                                                           | This attribute is used to send messages at the appropriate time, according to each user's local time zone.                                                   |
 | User agent              | Web               | [User agent](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent) | This attribute is used to only send messages to compatible devices. It can also be used within segmentation.                                                 |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 To learn more about tracking device-level properties (such as device wireless carrier, time zone, resolution, and others), see the platform-specific documentation: [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/storage/ "Android allowlist documentation"), [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/storage/ "iOS allowlist documentation"), [Web]({{site.baseurl}}/developer_guide/platform_integration_guides/web/cookies_and_storage/#device-properties "Web allowlist documentation").
 
@@ -92,7 +92,7 @@ By default, the following attributes aren't collected. Each attribute needs to b
 | Device Ad Tracking Enabled | Android, iOS | On iOS:<br>[`set(adTrackingEnabled:)`](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/set(adtrackingenabled:))<br><br>On Android:<br>[`Braze.setGoogleAdvertisingId()`](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze/-i-braze/set-google-advertising-id.html) | This property requires additional app-level permissions, which must be granted by the integrator.                                                                                                                                                                                      |
 | Device IDFA                | iOS          | Device identifier for advertisers                                                                                                                                                                                                                                                                                         | This requires the Ad Tracking Transparency framework, which will trigger additional privacy review from the App Store. For more details, see [`set(identifierForAdvertiser:)`](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/set(identifierforadvertiser:)) |
 | Google Advertising ID      | Android      | Identifier for advertising within Google Play apps                                                                                                                                                                                                                                                                        | This requires the app to retrieve the GAID and pass it to Braze. For more details, refer to [Optional Google Advertising ID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection).                                         |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ## Personalized integration
 
diff --git a/_docs/_user_guide/data_and_analytics/user_data_collection/user_import.md b/_docs/_user_guide/data_and_analytics/user_data_collection/user_import.md
index 6a2aa41462d..384a7453410 100644
--- a/_docs/_user_guide/data_and_analytics/user_data_collection/user_import.md
+++ b/_docs/_user_guide/data_and_analytics/user_data_collection/user_import.md
@@ -10,8 +10,6 @@ description: "This reference article covers how to import users into your Braze
 
 > Braze offers a variety of ways to import user data into the platform: SDKs, APIs, cloud data ingestion, technology partner integrations, and CSVs.
 
-{% multi_lang_include email-via-sms-warning.md %}
-
 Before proceeding, note that Braze does not sanitize (validate or properly format) HTML data during import. This means that script tags must be stripped for all import data meant for web personalization.
 
 When importing data into Braze that is specifically meant for personalization usage in a web browser, ensure that it is stripped of HTML, JavaScript, or any other script tag that potentially could be leveraged maliciously when rendered in a web browser.  
@@ -103,7 +101,7 @@ Setting `language` or `country` on a user through CSV import or API will prevent
 | `date_of_first_session` <br><br> `date_of_last_session`| String | May be passed in one of the following ISO 8601 formats: {::nomarkdown} <ul> <li> "YYYY-MM-DD" </li> <li> "YYYY-MM-DDTHH:MM:SS+00:00" </li> <li> "YYYY-MM-DDTHH:MM:SSZ" </li> <li> "YYYY-MM-DDTHH:MM:SS" (for example, 2019-11-20T18:38:57) </li> </ul> {:/} | No |
 | `subscription_group_id` | String | The `id` of your subscription group. This identifier can be found on the subscription group page of your dashboard. | No |
 | `subscription_state` | String | The subscription state for the subscription group specified by `subscription_group_id`. Allowed values are `unsubscribed` (not in subscription group) or `subscribed` (in subscription group). | No, but strongly recommended if `subscription_group_id` is used |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert note %}
 While `external_id` itself is not mandatory, you **must** include one of these fields:
@@ -171,7 +169,7 @@ If you are uploading or updating user profiles that are alias only, you must hav
 | --- | --- | --- | --- | --- |
 | 182736485 | my_alt_identifier | Smith | smith@user.com | TRUE |
 | 182736486 | my_alt_identifier | Nguyen | nguyen@user.com | FALSE |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 When you provide both a `user_alias_name` and `user_alias_label` in your import, Braze will update any existing user with the same `user_alias_name` and `user_alias_label`. If a user isn't found, Braze will create a newly identified user with that `user_alias_name` set.
 
@@ -268,6 +266,10 @@ You can set the name of the segment or accept the default, which is the name of
 
 The filter used to create the segment selects users who were created or updated in a selected import and is available with all other filters in the edit segment page.
 
+## Considerations
+
+{% multi_lang_include email-via-sms-warning.md %}
+
 ## Troubleshooting
 
 ### Missing rows
diff --git a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md
index 46a289b8a9b..467b1bb97e8 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting.md
@@ -12,9 +12,12 @@ description: "This reference article discusses the concept of rate limiting and
 
 > Rate limiting and frequency capping can be used together to make sure your users are getting the messages they need to, and none of the ones they don't.
 
-## Rate limiting
+## About rate limiting
 
-Braze allows you to control marketing pressure by rate limiting your campaigns, regulating the amount of outgoing traffic from your platform. You can implement two different types of rate limiting for your campaigns. The first focuses on providing the best experience for the user, while the second takes into consideration the bandwidth of your servers.
+Braze allows you to control marketing pressure by rate limiting your campaigns, regulating the amount of outgoing traffic from your platform. You can implement two different types of rate limiting for your campaigns: 
+
+1. [**User-centric rate limiting:**](#user-centric-rate-limiting) Focuses on providing the best experience for the user.
+2. [**Delivery speed rate limiting:**](#delivery-speed-rate-limiting) Takes into consideration the bandwidth of your servers.
 
 ### User-centric rate limiting
 
@@ -37,80 +40,97 @@ Let's say we've created a segment named "Retargeting Filter Showcase" with a fil
 
 If you have other more targeted segments receiving notifications recently, you may not want your users to be targeted by more generic campaigns directed at this segment. Appending the "Last Received Push Campaign" filter to this segment, the user has ensured that if they've received another notification in the past 24 hours, they will slide out of this segment for the next 24 hours. If they still meet the other criteria of the segment 24 hours later and haven't received any more notifications they will slide back into the segment.
 
-![][1]
+![Segment Details section with the "Last Received Any Message" segment filter highlighted.][1]
 
 Appending this filter to all segments targeted by campaigns would cause your users to receive a maximum of one push every 24 hours. You could then prioritize your messaging by ensuring that your most important messages are delivered before less important messages.
 
 #### Setting a maximum user cap
 
-Additionally, in the **Target Users** step of your campaign composition, you can limit the total number of users that will receive your message. This feature serves as a check that is independent of your campaign filters, allowing you to freely segment users without needing to worry about over-spamming.
+In the **Target Users** step of your campaign composition, you can also limit the total number of users that will receive your message. This serves as a check that's independent of your campaign filters, allowing you to freely segment users without worrying about over-spamming.
 
-![][2]
+![Audience Summary with a selected checkbox for limiting the number of people who receive the campaign.][2]
 
 By selecting the maximum user limit, you can limit the rate at which your users receive notifications on a per-channel basis or globally across all message types.
 
 ##### Maximum user cap with optimizations
 
-If you are using an optimization like Winning Variant or Personalized Variant, the campaign will consist of two sends: the initial experiment and the final send. 
+If you're using an optimization like Winning Variant or Personalized Variant, the campaign will consist of two sends: the initial experiment and the final send. 
 
-To set up a maximum user cap in this scenario, select **Limit the number of people who will receive this campaign**, then select **In total this campaign should**, and enter an audience limit. Your audience limit will be split up by the percentages shown in the A/B Testing panel. 
+To set up a maximum user cap in this scenario, select **Limit the number of people who will receive this campaign**, then select **In total this campaign should**, and enter an audience limit. Your audience limit will be split up by the percentages shown in the **A/B Testing** panel. 
 
 If you select **Every time the campaign is scheduled**, those two phases will be separately limited to the number set. This is typically not desirable.
 
 #### Setting a maximum impression cap
 
-For in-app messages and Content Cards, you can control marketing pressure by setting a maximum number of impressions that will be displayed to your user base, after which Braze will not send down more messages to your users. However, it is important to note that this cap is not exact. New Content Cards and in-app message rules are sent down to an app on session start, meaning that Braze can send a message to the user before the cap is hit, but by the time the user triggers the message, the cap has now been hit. In this situation, the device will still display the message.
-
-For example, let's say you have a game with an in-app message that triggers when a user beats a level, and you cap it at 100 impressions. There have been 99 impressions so far. Alice and Bob both open the game and Braze tells their devices that they are eligible to receive the message when they beat a level. Alice beats a level first and gets the message. Bob beats the level next, but since his device has not communicated with Braze servers since his session started, his device is unaware that the message has met its cap and he will also receive the message. However, when an impression cap has been hit, the next time any device requests the list of eligible in-app messages, that message will not be sent down and will be removed from that device.
+For in-app messages and Content Cards, you can control marketing pressure by setting a maximum number of impressions that will be displayed to your user base, after which Braze will not send down more messages to your users. However, it is important to note that this cap is not exact. 
 
-### Rate limiting and Canvas components
+New Content Cards and in-app message rules are sent down to an app on session start, meaning that Braze can send a message to the user before the cap is hit, but by the time the user triggers the message, the cap has now been hit. In this situation, the device will still display the message.
 
-Rate limits apply to all message sending across a Canvas. If multiple channels are utilized in a Canvas or Canvas step, the rate limit will be shared across channels. 
+For example, let's say you have a game with an in-app message that triggers when a user beats a level, and you cap it at 100 impressions. There have been 99 impressions so far. Alice and Bob both open the game and Braze tells their devices that they are eligible to receive the message when they beat a level. Alice beats a level first and gets the message. Bob beats the level next, but because his device hasn't communicated with Braze servers since his session started, his device is unaware that the message has met its cap and he will also receive the message. However, when an impression cap has been hit, the next time any device requests the list of eligible in-app messages, that message will not be sent down and will be removed from that device.
 
 ### Rate limiting and A/B testing
 
-When using rate limiting with an A/B test, the rate limit isn't applied to the control group in the same way as the test group, which is a potential source of time bias. Use appropriate conversion windows to avoid this bias.
+When using rate limiting with an A/B test, the rate limit isn't applied to the control group in the same way as the test group, which is a potential source of time bias. To avoid this bias, use appropriate conversion windows.
 
 ### Delivery speed rate limiting
 
-If you anticipate large campaigns driving a spike in user activity and overloading your servers, you can specify a per-minute rate limit for sending messages—this means Braze will send no more than your rate-limited setting within a minute. When targeting users during campaign creation, you can navigate to **Advanced Options** to select a rate limit (in various increments from as low as 50 to as high as 500,000 messages per minute). Note that non-rate-limited campaigns may exceed these delivery limits. Be aware, however, that messages will be aborted if they're delayed 72 hours or more due to a low rate limit. The user who created the campaign will receive alerts in the dashboard and via email if the rate limit is too low.
+If you anticipate large campaigns driving a spike in user activity and overloading your servers, you can specify a per-minute rate limit for sending messages—this means Braze will send no more than your rate-limited setting within a minute.
 
-![][3]
+When targeting users during campaign creation, you can navigate to **Target Audiences** (for campaigns) or **Send Settings** (for Canvas) to select a rate limit (in various increments from as low as 10 to as high as 500,000 messages per minute). 
 
-For instance, if you are trying to send out 75,000 messages with a 10,000-per-minute rate limit, the delivery will be spread out over 8 minutes. Your campaign will deliver no more than 10,000 for each of the first seven minutes, and 5,000 over the last minute. Note that messages sent using a rate limit won't have the rate limit setting (such as 10,000 per minute) evenly sent out over 60 seconds. Instead, Braze makes sure no more than 10,000 per minute messages are sent (this could mean a higher percentage of the 10,000 messages are sent within the first half minute versus the last half minute). Be wary of delaying time-sensitive messages with this form of rate limiting. If the segment contains 30 million users but we set the rate limit to 10,000 per minute, a large portion of your user base won't receive the message until the following day.
+Note that non-rate-limited campaigns may exceed these delivery limits. However, be aware that messages will be aborted if they’re delayed 72 hours or more due to a low rate limit. If the rate limit is too low, the creator of the campaign will receive alerts in the dashboard and by email.
 
-{% alert important %}
-When sending a multichannel campaign with a speed rate limit, each channel is sent independently of the others. The effect is that users could receive the different channels at different times, and it is not predictable which channel they will get first. For example, if you send a campaign that contains an email and a push notification, you may have 10,000 users with valid push tokens but 50,000 users with valid email addresses. If you set the campaign to send 100 messages per minute (a slow rate limit for the campaign size), a user could receive the push notification in the first batch of sends and the email in the last batch of sends, almost nine hours later.
-{% endalert %}
+![Audience Summary with a selected checkbox for limiting the rate at which the campaign will end, and rate being 500,000 per minute.][3]
 
-#### Rate limiting and Connected Content retries
+As another example, if you are trying to send out 75,000 messages with a 10,000-per-minute rate limit, the delivery will be spread out over 8 minutes. Your campaign will deliver no more than 10,000 messages for each of the first seven minutes, and 5,000 over the last minute. 
+
+Note that rate-limited messages may not be sent evenly over the course of each minute. Using the example of a 10,000-per-minute rate limit, this means Braze makes sure no more than 10,000 messages are sent per minute. This could mean a higher percentage of the 10,000 messages are sent within the first half minute versus the last half minute. 
 
-When the [Connected Content Retry][19] feature is enabled, Braze will retry call failures while respecting the rate limit you set for each resend. Let's think again about the 75,000 messages with a 10,000 per minute rate limit. In the first minute, the call fails or is slow and only sends 4,000 messages.
+{% alert important %}
+Be wary of delaying time-sensitive messages with this form of rate limiting. If the segment contains 30 million users but we set the rate limit to 10,000 per minute, a large portion of your user base won’t receive the message until the following day.
+{% endalert %}
 
-Instead of attempting to make up for the delay and send the remaining 4,000 messages in the second minute or add it to the 10,000 it is already set to send, Braze will move those 6,000 failed messages to the "back of the queue" and add an additional minute, if necessary, to the total minutes it would take to send your message.
+#### Single-channel campaigns
 
-|Minute|No Failure|6,000 Failure in Minute 1|
-|---|---|---|
-|1|10,000|4,000|
-|2|10,000|10,000|
-|3|10,000|10,000|
-|4|10,000|10,000|
-|5|10,000|10,000|
-|6|10,000|10,000|
-|7|10,000|10,000|
-|8|5,000|10,000|
-|9|0|6,000|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+When sending a single-channel campaign with a speed rate limit, the rate limit is applied for all messages together.
 
 #### Multichannel campaigns
 
-Keep in mind that the per-minute rate limit is adjusted on a per-campaign basis. If multiple channels are utilized within a campaign, the rate limit will apply to each of those channels. If your campaign utilizes email and in-app banners with a rate limit of 10,000 per minute, we will send 20,000 total messages each minute (10,000 email and 10,000 push).
+When sending a multi-channel campaign with a speed rate limit, each channel is sent independently of the others. As a result, the following may occur:
+
+- The total number of messages sent per minute could be more than the rate limit. 
+    - For example, if your campaign has a rate limit of 10,000 per minute and uses email and SMS, Braze can send a max of 20,000 total messages each minute (10,000 email and 10,000 SMS).
+- Users could receive the different channels at different times, and it is not predictable which channel they will get first. 
+    - For example, if you send a campaign that contains an email and an SMS, you may have 10,000 users with valid phone numbers and 50,000 users with valid email addresses. If you set the campaign to send 100 messages per minute (a slow rate limit for the campaign size), a user could receive the SMS in the first batch of sends and the email in the last batch of sends, almost nine hours later.
 
 #### Multi-platform push campaigns
 
-For push campaigns delivering on multiple platforms, the rate limit selected will be equally distributed across platforms. A push campaign leveraging Android and iOS with a 10,000 rate-limit per minute will equally distribute the 10,000 messages across the two platforms.
+For push campaigns delivering on multiple platforms, the selected rate limit will be equally distributed across platforms. A push campaign leveraging Android and iOS with a 10,000 rate-limit per minute will equally distribute the 10,000 messages across the two platforms.
+
+#### Canvas delivery speed rate limiting {#canvas-delivery-speed}
+
+When sending a Canvas with a speed rate limit, the rate limit is shared between channels. This means the total number of messages sent per minute from the Canvas will not exceed the rate limit. For example, if your Canvas has a rate limit of 10,000 per minute and uses email and SMS, Braze will send a total of 10,000 messages per minute across email and SMS.
+
+#### Rate limiting and Connected Content retries
+
+When the [Connected Content Retry][19] feature is turned on, Braze will retry call failures while respecting the rate limit you set for each resend. Let’s consider the scenario of 75,000 messages with a 10,000 per minute rate limit. In the first minute, the call fails or is slow and only sends 4,000 messages.
+
+Instead of attempting to make up for the delay and send the remaining 4,000 messages in the second minute or add it to the 10,000 it is already set to send, Braze will move those 6,000 failed messages to the “back of the queue” and add an additional minute, if necessary, to the total minutes it would take to send your message.
+
+| Minute | No Failure | 6,000 Failure in Minute 1 |
+|--------|------------|---------------------------|
+| 1      | 10,000     | 4,000                     |
+| 2      | 10,000     | 10,000                    |
+| 3      | 10,000     | 10,000                    |
+| 4      | 10,000     | 10,000                    |
+| 5      | 10,000     | 10,000                    |
+| 6      | 10,000     | 10,000                    |
+| 7      | 10,000     | 10,000                    |
+| 8      | 5,000      | 10,000                    |
+| 9      | 0          | 6,000                     |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
-## Frequency capping
+## About frequency capping
 
 As your user base continues to grow and your messaging scales to include lifecycle, triggered, transactional, and conversion campaigns, it's important to prevent your notifications from appearing "spammy" or disruptive. By providing greater control over your users' experience, frequency capping enables you to create the campaigns you desire without overwhelming your audience.
 
@@ -119,7 +139,7 @@ As your user base continues to grow and your messaging scales to include lifecyc
 Frequency capping is applied at the campaign or Canvas component send level and can be set up for each workspace from **Settings** > **Frequency Capping Rules**.
 
 {% alert note %}
-If you are using the [older navigation]({{site.baseurl}}/navigation), this page is called **Global Message Settings** and is located under **Engagement**.
+If you're using the [older navigation]({{site.baseurl}}/navigation), this page is called **Global Message Settings** and is located under **Engagement**.
 {% endalert %}
 
 By default, frequency capping is toggled on when new campaigns are created. From here, you can choose the following:
@@ -132,7 +152,7 @@ This time frame can be measured in minutes, days, weeks (seven days), or months,
 
 Each line of frequency caps will be connected using the `AND` operator, and you can add up to 10 rules per workspace. In addition, you may include multiple caps for the same message types. For instance, you can cap users to no more than one push per day and no more than three pushes per week.
 
-![][14]
+![Frequency capping section with lists of campaigns and Canvases that rules will and will not apply to.][14]
 
 ### Delivery rules
 
@@ -148,7 +168,7 @@ By default, new campaigns and Canvases that do not obey frequency caps will also
 This behavior changes the default behavior when you turn off frequency capping for a campaign or Canvas. The changes are backward compatible and do not impact messages that are currently live.
 {% endalert %}
 
-![][18]
+![Delivery Controls section with Frequency Capping turned on.][18]
 
 Different channels within a multichannel campaign will individually count  the frequency cap. For instance, if you create a multichannel campaign with both push and email and have frequency capping set up for both of those channels, then the push will count toward one push campaign and the email message will count toward one email message campaign. The campaign will also count toward one "campaign of any type." If users are capped to one push and one email campaign per day and a user receives this multichannel campaign, then they will no longer be eligible for push or email campaigns for the rest of the day (unless a campaign ignores frequency capping rules).
 
@@ -177,7 +197,7 @@ This scenario uses the following frequency capping rules:
 - A user triggers the same campaign, `Campaign ABC` three times over the course of a week.
 - This user triggers `Campaign ABC` once on Monday, once on Wednesday, and once on Thursday.
 
-![]({% image_buster /assets/img/standard_rules_fnfn.png %})
+![Frequency Capping section with the rule of sending no more than 2 push notification campaigns/Canvas steps from all campaigns/Canvas steps to a user every 1 week.]({% image_buster /assets/img/standard_rules_fnfn.png %})
 
 **Then, the expected behavior is that:**
 
@@ -198,7 +218,7 @@ You can also combine regular frequency capping with frequency capping by tags. C
 1. No more than three push notification campaigns or Canvas components per week from all campaign and Canvas steps. <br>**AND**
 2. No more than two push notification campaign or Canvas components per week with the tag `promotional`.
 
-![][12]
+![Frequency Capping section with two rules limiting how many push notification campaigns/Canvases can be sent to a user every 1 week.][12]
 
 As a result, your users will receive no more than three campaign sends per week over all campaigns and Canvas steps and no more than two push notification campaigns or Canvas components with the tag `promotional`.
 
@@ -213,7 +233,7 @@ When rules conflict, the most restrictive, applicable frequency capping rule wil
 1. No more than one push notification campaign or Canvas component per week from all campaign and Canvas components. <br>**AND**
 2. No more than three push notification campaigns or Canvas components per week with the tag `promotional`.
 
-![][11]
+![Frequency Capping section with conflicting rules to limit how many push notification campaigns/Canvas steps are sent to a user every 1 week.][11]
 
 In this example, your user will not receive more than one push notification campaign or Canvas components with the tag "promotional" in a given week, because you've specified that users should not receive more than one push notification campaign or Canvas component from all campaigns and Canvas components. In other words, the most restrictive applicable frequency rule is the rule that will be applied to a given user.
 
@@ -238,7 +258,7 @@ Consider the following campaigns and frequency capping by tag rule:
 |---|---|
 | The `promotional` tag is removed from **Campaign A** after your user received the message, but before **Campaign B has sent.** | Your user will receive **Campaign B**.|
 | The `promotional` tag is mistakenly removed from **Campaign A** after your user received the message. <br> The tag is added back to **Campaign A** on Tuesday, before **Campaign B** is sent. | Your user will not receive **Campaign B**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Sending at large scales {#sending-at-large-scales}
 
diff --git a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign.md b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign.md
index 0ab14e5fab1..c6f79b85e1b 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign.md
@@ -24,7 +24,7 @@ This section covers time-based scheduling and delivery options for [scheduled de
 | Definition | Time Zone |
 | ---------- | --------- |
 | Send message at a designated time, on a specific calendar date. | Company's time zone. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![A campaign with the option "Send at a designated time" selected to send once starting at 9 am on July 13, 2021.][2]
 
@@ -33,7 +33,7 @@ This section covers time-based scheduling and delivery options for [scheduled de
 | Definition | Time Zone |
 | ---------- | --------- |
 | User's optimal time. Each user will receive the campaign at the time they are most likely to engage. To learn more, check out [Intelligent Timing]({{site.baseurl}}/user_guide/brazeai/intelligence/intelligent_timing/). | If you select a specific time as your [fallback]({{site.baseurl}}/user_guide/brazeai/intelligence/intelligent_timing/#fallback-options), this will be sent in the user's local time. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![A campaign with the option "Intelligent Timing" selected to send once at the optimal time on July 13, 2021 with a custom fallback time of 9 am for users without enough data in their profiles to calculate an optimal time.][3]
 
@@ -42,7 +42,7 @@ This section covers time-based scheduling and delivery options for [scheduled de
 | Definition | Time Zone |
 | ---------- | --------- |
 | Allows you to deliver messages to a segment based on a user's [individual time zone]({{site.baseurl}}/user_guide/engagement_tools/campaigns/faq/#when-does-braze-evaluate-users-for-local-time-zone-delivery). | User's local time. If a user's time zone isn't set, this will fall back to company time zone. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![A campaign with the option "Send at a designated time" selected to send once starting at 9 am on July 13, 2021 with the checkbox "Send Campaign to users in their local time zone" selected.][4]
 
@@ -51,7 +51,7 @@ This section covers time-based scheduling and delivery options for [scheduled de
 | Definition | Time Zone |
 | ---------- | --------- |
 | After a user is messaged by this campaign, specify when they will become re-eligible to receive the campaign again. [Learn more]({{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/delivery_types/reeligibility/#campaigns). | N/A |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![A campaign with the selected checkbox "Allow users to become re-eligible to receive campaign" after one week.][5]
 
@@ -70,7 +70,7 @@ When choosing your delay length, keep in mind that if you set a delay that is lo
 | Definition | Time Zone |
 | ---------- | --------- |
 | Send message immediately after the user performs the trigger action. | N/A |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![Schedule Delay set to send campaign immediately after the trigger event occurs.][6]
 
@@ -79,7 +79,7 @@ When choosing your delay length, keep in mind that if you set a delay that is lo
 | Definition | Time Zone |
 | ---------- | --------- |
 | Send message after a delay. You can specify a delay in seconds, minutes, hours, days, or weeks. For [in-app message campaigns]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/about), you can set a delay up to two hours only. | N/A |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![Schedule Delay set to send campaign after one day after the trigger event occurs.][7]
 
@@ -88,7 +88,7 @@ When choosing your delay length, keep in mind that if you set a delay that is lo
 | Definition | Time Zone |
 | ---------- | --------- |
 | Send message on the next specified day of the week, at a selected time of day. | Select between **user's local time** or **company time** |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For example, suppose you select "Send on the next Saturday at 3:15 pm". If a user performs the trigger event on a Saturday, they would receive that message on the next Saturday in seven days. If they enter on a Friday, the next Saturday would be in one day.
 
@@ -99,7 +99,7 @@ For example, suppose you select "Send on the next Saturday at 3:15 pm". If a use
 | Definition | Time Zone |
 | ---------- | --------- |
 | Send message in a specific number of days at a specified time. | Select between **user's local time** or **company time** |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Braze calculates the delay as `day of the week` + `calendar days`, then adds the `time`. For example, suppose the user performs the trigger event on Monday at 9 pm, and the schedule delay is set to "Send campaign in 1 day at 9 am". That message will be delivered on Tuesday at 9 am because Braze calculates the delay as `Monday` + `1 calendar day` and then adds on `9 am`.
 
@@ -110,7 +110,7 @@ Braze calculates the delay as `day of the week` + `calendar days`, then adds the
 | Definition | Time Zone |
 | ---------- | --------- |
 | Prevent messages from being sent during specified hours. If a message triggers during Quiet Hours, you can choose between canceling the message, or sending at the next available time (such as sending at the end of your Quiet Hours). | User's local time. If a user's time zone isn't set, this will fall back to company time zone. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![A campaign with Quiet Hours enabled. In this example, messages will not send between 12 am and 8 am in the user's local time. If a message triggers during Quiet Hours, then the message will be sent at the next available time.][10]
 
@@ -119,7 +119,7 @@ Braze calculates the delay as `day of the week` + `calendar days`, then adds the
 | Definition | Time Zone |
 | ---------- | --------- |
 | After a user is messaged by this campaign, specify when they will become [re-eligible]({{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/delivery_types/reeligibility/#campaigns) to receive the campaign again. | N/A |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![A campaign with the selected checkbox "Allow users to become re-eligible to receive campaign" after one week.][5]
 
@@ -128,7 +128,7 @@ Braze calculates the delay as `day of the week` + `calendar days`, then adds the
 | Definition | Time Zone |
 | ---------- | --------- |
 | Limit how many times each user should receive the campaign within a certain time frame, which can be measured in minutes, days, weeks (7 days), and months. For more information, refer to [frequency capping]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#frequency-capping). | User's local time. If a user's time zone isn't set, this will fall back to company time zone. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 By default, frequency capping is toggled off for new Canvases. Frequency capping is applied at the step level, not at the Canvas entry level.
 
@@ -139,7 +139,7 @@ Frequency capping is based on calendar days, not a 24-hour period. This means th
 | Definition | Time Zone |
 | ---------- | --------- |
 | The maximum amount of time that may pass between a user receiving a campaign and performing the assigned action for it to be considered a conversion. For more information, refer to [conversion events]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/conversion_events/). | N/A |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 
diff --git a/_docs/_user_guide/engagement_tools/campaigns/faq.md b/_docs/_user_guide/engagement_tools/campaigns/faq.md
index db5564ccb73..75f64b4f24b 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/faq.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/faq.md
@@ -167,7 +167,7 @@ Action-based delivery campaigns or event-triggered campaigns are very effective
 | Pros | Cons | 
 | ---- | ---- |
 | • Visibility of incoming JSON payloads into the platform (if event triggered by test user) via the **Message Activity Log**<br><br>• Personalization elements are included in the custom event properties<br><br>• Custom event can be used to create Segments of users eligible for the message | • Consumes data points |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### API-triggered
 
@@ -176,5 +176,5 @@ API-triggered or server-trigger campaigns are ideal for more advanced transactio
 | Pros | Cons | 
 | ---- | ---- |
 | • Does not consume data points<br><br>• Personalization elements are included in the JSON payload properties | • Does not allow you to create a segment of users eligible for the message in the JSON payload properties<br><br>• Not able to see incoming JSON payloads via the **Message Activity Log**|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
diff --git a/_docs/_user_guide/engagement_tools/campaigns/getting_started/campaign_basics.md b/_docs/_user_guide/engagement_tools/campaigns/getting_started/campaign_basics.md
index e079c9aacd3..33ebe95f779 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/getting_started/campaign_basics.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/getting_started/campaign_basics.md
@@ -50,7 +50,7 @@ You can use pre-defined [segments]({{site.baseurl}}/user_guide/engagement_tools/
 | Marketing Activity | Segment customers based on universal behaviors like last engagement or received campaigns. |
 | User Attributes | Segment customers by their constant attributes and characteristics. |
 | Install Attribution | Segment customers by their first source, ad group, campaign, or ad. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### The "why": Identify conversion events
 
diff --git a/_docs/_user_guide/engagement_tools/campaigns/ideas_and_strategies/localizing_a_campaign.md b/_docs/_user_guide/engagement_tools/campaigns/ideas_and_strategies/localizing_a_campaign.md
index 5fd0215a1fe..c372e25f4cc 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/ideas_and_strategies/localizing_a_campaign.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/ideas_and_strategies/localizing_a_campaign.md
@@ -41,7 +41,7 @@ In the "one template for all" approach, localization is applied to a single temp
 | --- | --- |
 | - Centralized approach<br>- Reduced email build time, no need to build out an email multiple times | - Manual report building<br>- Campaign report shows aggregated metrics rather than metrics per country<br>- Need to thoroughly test Liquid to ensure it populates as expected<br>- Depending on how you pull in the country value or how many counties you have set up, it could be tricky to test each country<br>- Harder to schedule sends for specific times across time zones<br>- Harder to use if you want to send separate content per country. |
 | --- | --- | --- |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab One template per country %}
@@ -55,7 +55,7 @@ The "one template per country" approach separates templating into different send
 | Advantages | Considerations |
 | --- | --- |
 | - Scalable to multiple locations<br>- Reporting on revenue per country within Braze (such as per campaign)<br>- Flexibility if there is drastically different content per country | - Requires strategic structuring<br>- More build effort required (such as separate campaigns for each country) |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
@@ -72,7 +72,7 @@ After a Canvas is sent, the dashboard provides aggregated [Canvas Analytics]({{s
 | Advantages | Considerations |
 | --- | --- |
 | - Centralized approach<br>- Reduced email build time - no need to build out an email multiple times. | - Manual report building<br>- Canvas report shows aggregated metrics rather than metrics per country<br>- Need to thoroughly test Liquid to ensure it populates as expected<br>- Depending on how you pull in the country value or how many counties you have set up, it could be tricky to test each country<br>- Harder to schedule sends for specific times across time zones<br>- Harder to use if you want to send separate content per country. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab One journey per country %}
@@ -88,7 +88,7 @@ Once sent, the dashboard provides dynamic analytics per country and within user-
 | Advantages | Considerations |
 | --- | --- |
 | - Reporting on revenue per country within Braze (such as per Canvas, variant, or step)<br>- Flexibility if there is drastically different content per country<br>- Can add other channels as part of the journey in the future | - Requires strategic structuring<br>- More build effort required (such as separate message steps for each country)<br>- Canvas can become large and difficult to read if you have custom, complex journeys for each country in a single Canvas. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
diff --git a/_docs/_user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features.md b/_docs/_user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features.md
index 3ef7075eece..d2acf9a6f44 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features.md
@@ -65,7 +65,7 @@ Once Braze receives data from version 2.0.0 of your app, you can target users wi
 | Greater than 2.0.0 | 2.5.1 | The user and all future installs will be in the segment. |
 | Greater than 2.0.0 | 1.9.9 | The user is not in the segment. |
 | Less than or equal to 2.0.0 | 3.0.1 | The user is not in the segment. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### App version name
 
diff --git a/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/archiving_campaigns.md b/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/archiving_campaigns.md
index 01693104204..79cd9833705 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/archiving_campaigns.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/archiving_campaigns.md
@@ -11,38 +11,29 @@ tool:
 
 # Archiving campaigns
 
-> If you'd like to stop a campaign from sending or clear it from your dashboard, you can archive it. Go to the **Campaigns** page, click the gear icon next to the campaign's name and click **Archive**.
+> Archiving campaigns can be a simple and effective way of organizing your workspace. As you continue building more campaigns, you can make sure your focus is on active and relevant messaging efforts.
 
-![][1]
+To stop a campaign from sending or clear it from your dashboard, you can archive it:
 
-When you archive a campaign, no further messages from that campaign will be delivered. In the case of in-app messages, no further in-app messages from that campaign will be displayed to users.
-
-There are also bulk actions you can use, such as deactivating and archiving multiple campaigns by checking the boxes next to the campaigns and clicking the relevant button.
-
-![][3]
+1. Go to **Messaging** > **Campaigns**.
+2. Hover over the campaign's row and select the <i class="fas fa-ellipsis-vertical"></i> menu. 
+3. Select **Archive**.
 
-To view archived messages from the **Campaigns** page, select the **Archived** folder.
+When you archive a campaign, no further messages from that campaign will be delivered. In the case of in-app messages, no further in-app messages from that campaign will be displayed to users.
 
-![][2]
+There are also bulk actions you can use by selecting the checkboxes next to the campaigns and selecting the relevant option.
 
 ## Unarchiving campaigns
 
-While clicking on an archived campaign will allow you to view its past results, you won't be able to edit the campaign. You will need to unarchive campaign in order to edit it. To unarchive a campaign, you must select the campaign within the **Archived** folder and click **Unarchive Selected**.
-
-![][4]
+While selecting an archived campaign will allow you to view its past results, you won't be able to edit the campaign. You'll need to unarchive the campaign to edit it. To unarchive a campaign:
 
-Unarchiving a campaign does not make it live. This will simply move your campaign to the **Active** campaign folder where you can make edits and review how the campaign is set up. At this point, your campaign will be stopped and won't send any messages. 
+2. Hover over the archived campaign's row and select the <i class="fas fa-ellipsis-vertical"></i> menu. 
+3. Select **Unarchive**.
 
-If you wish to resume the campaign and begin sending messages, click the gear icon next to the campaign and select **Resume**.
+Unarchiving a campaign doesn't make it live. This just updates your campaign status to **Active**. At this point, you can edit and review how the campaign is set up, and your campaign will be stopped and won't send any messages.
 
-![][5]
+If you want to resume the campaign and begin sending messages, select the gear icon next to the campaign and select **Resume**.
 
 {% alert warning %}
-When you archive a Segment, any campaigns using it will also be archived.
+When you archive a segment, any campaigns using it will also be archived.
 {% endalert %}
-
-[1]: {% image_buster /assets/img_archive/Archiving.png %}
-[2]: {% image_buster /assets/img_archive/Include_archived.png %}
-[3]: {% image_buster /assets/img_archive/Archive_pause_selected.png %}
-[4]: {% image_buster /assets/img_archive/unarchive_selected.png %}
-[5]: {% image_buster /assets/img_archive/resume_unarchived.png %}
diff --git a/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/copying_to_workspace.md b/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/copying_to_workspace.md
index c6a2f538314..e48956e3686 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/copying_to_workspace.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/copying_to_workspace.md
@@ -10,42 +10,25 @@ tool: Campaigns
 
 # Copying across workspaces
 
-> Copying campaigns across workspaces lets you jumpstart your message composition by starting with a copy of a campaign in a different workspace. This copy will remain as a draft until you edit and launch, helping you keep and build off your successful messaging strategies.
+> Copying campaigns across workspaces lets you jumpstart your message composition by starting with a copy of a campaign in a different workspace. This copy will remain as a draft until you edit and launch, helping you keep and build off your successful messaging strategies.<br><br>This page covers how to copy campaigns to different workspaces and lists what is and isn't copied over.
 
 {% alert important %}
-Copying campaigns across workspaces is generally available for the following supported channels: SMS, in-app messages, email, email templates, and Content Blocks. Other channel support will be coming soon.
+Copying campaigns across workspaces is generally available for the following supported channels: SMS, in-app messages, email, email templates, and Content Blocks. Other channel support (such as for push and content cards) isn't available yet.
 {% endalert %}
 
 ## How to copy a campaign to a different workspace
 
 ![][1]{: style="float:right;max-width:70%;margin-left:15px;"}
 
-Select the <i class="fas fa-cog"></i> gear icon next to the selected campaign, and click **Copy to Workspace**. After copying, we recommend reviewing and testing your campaign to ensure that all fields are working properly.
+Select the <i class="fas fa-cog"></i> gear icon next to the selected campaign, and select **Copy to Workspace**. After copying, we recommend reviewing and testing your campaign to confirm that all fields work properly.
 
 When you copy a campaign across workspaces, fields such as campaign name and description, variants, delivery schedule type, and conversion behaviors are copied. For email campaigns, fields such as email body, subject, and preheader are also copied over to the destination workspace. 
 
 Note that multi-channel campaigns with unsupported channels can't be copied over to a different workspace.
 
-### Copying campaigns that contain Liquid
-
-For message bodies that include Liquid references, the references are copied over to the destination workspace, but they may not function as expected. This means if a campaign from Workspace A is copied to Workspace B, then Workspace B can't reference Workspace A's details, including Liquid references. For example, fields like trigger actions and audience filters aren't copied over.
-
-Note the following Liquid references with dependencies when copying campaigns across workspaces:
-
-- Catalog item tags
-- Connected Content tags
-- Content Blocks
-- Custom attributes
-- Preference centers
-- Product recommendations
-- Subscription state tags
-- Voucher and promotion tags
-
-When you copy a campaign across workspaces, Content Blocks won't be copied. However, a Content Block can be referenced in the destination workspace if a block with the same name exists. Alternatively, you can create the Content Block (or these Liquid references) in the destination workspace to avoid errors when launching a campaign.
-
 ### What's copied across workspaces
 
-Note the following is not a comprehensive list of what is copied across workspaces and what is omitted. As a best practice, check the campaign details and test to ensure your campaign works as expected.
+Note the following is not a comprehensive list of what is copied across workspaces and what is omitted. As a best practice, check the campaign details and test to confirm your campaign works as expected.
 
 {% tabs %}
 {% tab Campaigns %}
@@ -62,7 +45,7 @@ Note the following is not a comprehensive list of what is copied across workspac
 | Reoccurring schedule |  | 
 | Is Transactional |  | 
 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Conversion Behaviors %}
@@ -73,7 +56,7 @@ Note the following is not a comprehensive list of what is copied across workspac
 | Campaign interaction |  Campaign ID | 
 | Custom event name |  | 
 | Product name |  | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Actions %}
@@ -82,7 +65,7 @@ Note the following is not a comprehensive list of what is copied across workspac
 |---|---|
 | Action types | Send count |
 | Message variations |  |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Message Variations %}
@@ -93,7 +76,7 @@ Note the following is not a comprehensive list of what is copied across workspac
 | Type |  Seed group IDs | 
 |  |  Link template IDs | 
 |  |  Internal user group IDs | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Email Message Variation %}
@@ -105,7 +88,7 @@ Note the following is not a comprehensive list of what is copied across workspac
 | Title |  BCC | 
 | Subject |  Link template | 
 |  |  Link aliasing |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Email Body %}
@@ -117,7 +100,7 @@ Note the following is not a comprehensive list of what is copied across workspac
 | Preheader |  | 
 | Inline CSS |  | 
 | AMP HTML |  |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Email Templates %}
@@ -128,7 +111,7 @@ Note the following is not a comprehensive list of what is copied across workspac
 | Description | Image IDs | 
 | Subject | Territories | 
 | Headers | Tags | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Content Blocks %}
@@ -139,7 +122,7 @@ Note the following is not a comprehensive list of what is copied across workspac
 | Description | API keys | 
 | Content | Territories | 
 | HTML and drag-and-drop content | Tags | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab SMS Message Variation %}
@@ -150,10 +133,27 @@ Note the following is not a comprehensive list of what is copied across workspac
 | Link shortening | VCF media items | 
 | Click tracking |  | 
 | Media items |  | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
 
+### Copying campaigns that contain Liquid
+
+For message bodies that include Liquid references, the references are copied over to the destination workspace, but they may not function as expected. This means if a campaign from Workspace A is copied to Workspace B, then Workspace B can't reference Workspace A's details, including Liquid references. For example, fields like trigger actions and audience filters aren't copied over.
+
+Note the following Liquid references with dependencies when copying campaigns across workspaces:
+
+- Catalog item tags
+- Connected Content tags
+- Content Blocks
+- Custom attributes
+- Preference centers
+- Product recommendations
+- Subscription state tags
+- Voucher and promotion tags
+
+When you copy a campaign across workspaces, Content Blocks won't be copied. However, a Content Block can be referenced in the destination workspace if a block with the same name exists. Alternatively, you can create the Content Block (or these Liquid references) in the destination workspace to avoid errors when launching a campaign.
+
 [1]: {% image_buster /assets/img_archive/clone_campaign.png %}
 
diff --git a/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/duplicating_segments_and_campaigns.md b/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/duplicating_segments_and_campaigns.md
index 90bc5f89928..089b4d6dbc5 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/duplicating_segments_and_campaigns.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/duplicating_segments_and_campaigns.md
@@ -13,27 +13,37 @@ tool:
 
 # Duplicating segments, campaigns, and Canvases
 
-> You can duplicate pre-existing segments, campaigns, and Canvases to continually iterate and build off your successful strategies. You can duplicate these items when viewing them as a list on their respective page in the dashboard (Segments, Campaigns, or Canvas).
+> You can duplicate pre-existing segments, campaigns, and Canvases to continually iterate and build off your successful strategies. You can duplicate these items when viewing them as a list on their respective page in the dashboard (**Segments**, **Campaigns**, or **Canvas**).
 
-For more on segments and campaigns, check out our [Braze Learning course](https://learning.braze.com/quick-overview-segment-and-campaign-setup)!
+{% alert tip %}
+For more on segments and campaigns, check out our [Braze Learning course](https://learning.braze.com/quick-overview-segment-and-campaign-setup).
+{% endalert %}
 
-## Duplicating segments or campaigns
+## Duplicating campaigns and segments
 
-To duplicate a segment or campaign, click <i class="fas fa-gear"></i> **More actions** next to the list item and select **Duplicate**. Your new segment or campaign will automatically be titled "Copy of [Original Name]" and you'll be brought to its editing page. Duplicates of campaigns will remain in drafts until your edit and launch them.
+To duplicate a segment or campaign, do the following: 
+1. Go to **Messaging** > **Campaigns** or **Audience** > **Segments**.
+2. Hover over the campaign or segment and select <i class="fas fa-gear"></i> **More actions**.
+3. Select **Duplicate**. 
 
-| ![Duplicate segment]({% image_buster /assets/img_archive/duplicate_segment.png %}) | ![Duplicate campaign]({% image_buster /assets/img_archive/duplicate_campaign.png %})
+Your new segment or campaign will automatically be titled "Copy of [Original Name]" and you'll be brought to its editing page. Duplicates of campaigns will remain in drafts until your edit and launch them.
 
 ## Duplicating Canvases
 
-{% alert important %}
-As of February 28, 2023, you can no longer create or duplicate Canvases using the original Canvas experience. Braze recommends that customers who use the original Canvas experience move to Canvas Flow. It's an improved editing experience to better build and manage Canvases. Learn more about [cloning your Canvases to Canvas Flow]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases/).
-{% endalert %}
+To duplicate a Canvas, do the following:
+
+1. Go to **Messaging** > **Canvas**.
+2. Hover over the Canvas row and select <i class="fas fa-ellipsis-vertical"></i> **More actions**.
+3. Select **Duplicate**. 
+
+Your new Canvas will automatically be titled "Copy of [Original Name]" and you'll be brought to its editing page. Duplicates of Canvases will remain drafts until you edit and launch them.
+
+![Canvas list page with the option to duplicate a Canvas named "api_triggered_canvas 3".]({% image_buster /assets/img_archive/duplicate_canvas.png %})
 
-To duplicate a Canvas, click <i class="fas fa-ellipsis-vertical"></i> **More actions** next to a Canvas and select **Duplicate**. Your new Canvas will automatically be titled "Copy of [Original Name]" and you'll be brought to its editing page. Duplicates of Canvases will remain drafts until you edit and launch them.
+{% details Original Canvas editor %}
 
-![Duplicate Canvas][5]
+As of February 28, 2023, you can no longer create or duplicate Canvases using the original Canvas experience. 
 
+Braze recommends that customers who use the original Canvas experience move to Canvas Flow. It's an improved editing experience to better build and manage Canvases. Learn more about [cloning your Canvases to Canvas Flow]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases/).
 
-[3]: {% image_buster /assets/img_archive/duplicate_segment.png %}
-[4]: {% image_buster /assets/img_archive/duplicate_campaign.png %}
-[5]: {% image_buster /assets/img_archive/duplicate_canvas.png %}
+{% enddetails %}
diff --git a/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/search_campaigns.md b/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/search_campaigns.md
index 2688dce800c..e53292048dc 100644
--- a/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/search_campaigns.md
+++ b/_docs/_user_guide/engagement_tools/campaigns/managing_campaigns/search_campaigns.md
@@ -3,7 +3,7 @@ nav_title: Searching for Campaigns
 article_title: Searching for Campaigns
 page_order: 10
 page_type: reference
-description: "This article covers how to use the campaign search to find campaigns."
+description: "This article describes the various ways you can search for campaigns on the campaign list page."
 tool:
   - Campaigns
 
@@ -11,38 +11,43 @@ tool:
 
 # Searching for campaigns
 
-> This article covers how you can use the search field of the campaigns list to refine your results.
+> As you build more campaigns in your workspace, you can adjust the filters and columns in the campaign list to sort and organize these campaigns. Using a combination of these search methods can help to narrow down your results, especially as your list of campaigns grows.
 
-## Filters
+There are several ways you can search for campaigns on the campaign list page by selecting:
 
-Use the filters in the side menu to group results by creator, editor, send dates, or channel, or select **Only Show Mine** to limit your search results to campaigns you've created. You can also filter by status and [tags]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) to further narrow down your results.
+- Status
+- Tags
+- Filters
+- Columns
 
-![][2]
+You can use the search bar to enter keywords and phrases that are related to your campaign name. To do an exact search, use quotation marks ("") to surround your search phrase. For example, to search specifically for webhook test campaigns, enter `"webhook test"` in the search bar.
 
-Expand the search dropdown to filter by last editor, target segment, messaging channel, or date.
+![The campaign list page with three campaigns listed. The page is organized to show active campaigns. The columns are Name, Status, Stop date, Campaign type, and Sent to organize the view.]({% image_buster /assets/img/campaign_list_example.png %})
 
-![][3]
+### Selecting a status
 
-## Search syntax
+By default, the campaign list will show your active and idle campaigns. You can select the dropdown to view campaigns by their status (active, draft, archived, stopped, and idle).
 
-Selecting a campaign filter will automatically add the appropriate syntax to the search field. However, you can manually enter these filters as well. When using manual search, the syntax is the filter name, followed by a colon, followed by your input. For example, to search for push campaigns, enter `channel:push`.
+For example, if you want to audit your campaign drafts, select **Status** > **Draft** to focus your campaign list.
 
-Here's a list of supported search filters:
+### Searching by tags
 
-| Search for | Filter | Input |
-| --- | --- | --- |
-| Campaign API identifier | `api_id` | A specific [campaign API identifier]({{site.baseurl}}/api/identifier_types#api-identifier-types) |
-| Segment a campaign targets | `segment` | Segment name |
-| Messaging channel that a campaign targets | `channel` | One of the following: <br>-`content_cards` <br>- `email`<br>- `push`<br>- `sms` (returns both SMS and MMS)<br>- `webhook`
-| Status or delivery type | `status` | One of the following: <br>- `one-time` <br>- `recurring` <br>- `triggered` <br>- `multivariate` <br>- `transactional` <br> - `drafts` <br> - `stopped` <br> - `archived` <br> - `all` |
-| Tag | `tag` | - A single tag name <br>- A list of tag names separated by commas |
-| Most recent editor | `edited_by` | A user's email address |
-| Date campaign was created | `created` | - A single date in the format `YYYY/MM/DD`<br> - A range of dates in the format `YYYY/MM/DD-YYYY/MM/DD` |
-| Date campaign was last edited | `edited` | - A single date in the format `YYYY/MM/DD`<br> - A range of dates in the format `YYYY/MM/DD-YYYY/MM/DD` |
-| Date campaign was last sent | `sent` | - A single date in the format `YYYY/MM/DD`<br> - A range of dates in the format `YYYY/MM/DD-YYYY/MM/DD` |
-| Campaigns you created | `created_by_me` | `true` |
+Searching your campaigns by [tags]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) can further narrow down your results. For example, if you're trying to find all the campaigns you built for targeting new customers, frequent buyers, lapsed customers, you could search these campaigns by their shared tag **Targeting by customer type**.
 
+### Adjusting filters
 
-[1]: {% image_buster /assets/img_archive/campaign_search.png %}
-[2]: {% image_buster /assets/img_archive/campaign_search2.png %}
-[3]: {% image_buster /assets/img_archive/campaign_search3.png %}
+Use the filters to group results by the following campaign details:
+
+- Campaign type 
+- Who created the campaign
+- Who last edited the campaign
+- Entry schedule
+- Target segment
+- Teams
+- Campaigns with expired interaction data
+
+You can also search by selecting the date range for when the campaign was last created or last edited. This can be especially useful if you're searching for campaigns used during a promotional period.
+
+### Organizing columns
+
+When you select **Columns**, you can adjust the information of the campaign list page to display relevant campaign details by selecting the respective checkboxes. For example, if  you want to set up the campaign list to show only action-based webhook campaigns by your marketing team, you could select **Campaign type**, **Entry schedule**, and **Teams** as your columns.
diff --git a/_docs/_user_guide/engagement_tools/canvas/canvas_components/action_paths.md b/_docs/_user_guide/engagement_tools/canvas/canvas_components/action_paths.md
index 211a62d03fb..576e623cc05 100644
--- a/_docs/_user_guide/engagement_tools/canvas/canvas_components/action_paths.md
+++ b/_docs/_user_guide/engagement_tools/canvas/canvas_components/action_paths.md
@@ -75,7 +75,7 @@ If users enter into an action path multiple times and have multiple entries in t
 |---|--------------|
 | **Off** | When a relevant action is performed, Braze will deduplicate entries and immediately advance the earliest entry through the relevant action group. <br><br/> When a relevant action is not performed, all entries will advance at the end of the relevant evaluation window. No deduplication will occur. |
 | **On** | All entries will advance at the end of the relevant evaluation window. No deduplication will occur. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Note that the rankings aren't [editable after launch]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch/).
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/canvas_components/decision_split.md b/_docs/_user_guide/engagement_tools/canvas/canvas_components/decision_split.md
index 1164ddbb4c8..d90c04d19d8 100644
--- a/_docs/_user_guide/engagement_tools/canvas/canvas_components/decision_split.md
+++ b/_docs/_user_guide/engagement_tools/canvas/canvas_components/decision_split.md
@@ -56,7 +56,7 @@ Refer to the following table for descriptions of analytics for this step:
 | Entered | The total number of times the step has been entered. If your Canvas has re-eligibility and a user enters a Decision Split step twice, two entries will be recorded. |
 | Yes | The number of entries that met the specified criteria and proceeded down the "yes" path. |
 | No | The number of entries that did not meet the specified criteria and proceeded down the "no" path. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 [1]: {% image_buster /assets/img/decision-split-1.png %}
 [2]: {% image_buster /assets/img/define-split-2.png %}
diff --git a/_docs/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md b/_docs/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md
index 1edc75f634e..3fcb4f2a6a5 100644
--- a/_docs/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md
+++ b/_docs/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md
@@ -75,7 +75,7 @@ Delays have three statistics available in the analytics view of an active or pre
 | `Entered` | Reflects the number of times the step has been entered. If your Canvas has re-eligibility and a user enters a delay step twice, two entries will be recorded. |
 | `Proceeded to Next Step` | Reflects the number of entries that proceeded to the next step in the Canvas. |
 | `Exited Canvas` | Reflects the number of entries that exited the Canvas and did not proceed to the next step. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Time series for these analytics are available in the expanded component view.
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths.md b/_docs/_user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths.md
index 70164c2c649..e7e63e61b81 100644
--- a/_docs/_user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths.md
+++ b/_docs/_user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths.md
@@ -61,7 +61,7 @@ When the experiment window passes and the experiment is complete, Braze will sen
 ![]({% image_buster /assets/img/experiment_step/experiment_personalized_delay_group_complete.png %}){: style="max-width:75%;" }
 
 {% endtab %}
-{% tab Recurring, action-triggered, or API-triggered Canvas %}
+{% tab Recurring or action-triggered or API-triggered Canvas %}
 
 You can test up to four paths in a single Experiment Path. Add your paths and finish setting up your Canvas as needed, then launch it.  
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/canvas_components/message_step.md b/_docs/_user_guide/engagement_tools/canvas/canvas_components/message_step.md
index 5a415b735f1..7044ec9f771 100644
--- a/_docs/_user_guide/engagement_tools/canvas/canvas_components/message_step.md
+++ b/_docs/_user_guide/engagement_tools/canvas/canvas_components/message_step.md
@@ -104,7 +104,7 @@ Refer to the following table for definitions of Message component metrics:
 | Unique Recipients | The number of users who have received messages from this step. |
 | Primary Conversion Event | The number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign. You define this event when building the campaign. |
 | Revenue | The total revenue in dollars from campaign recipients within the set primary conversion window. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][3]{: style="max-width:20%;"}
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_by_channel/content-cards_in_canvas.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_by_channel/content-cards_in_canvas.md
index ad76f577103..c1ccf810aba 100644
--- a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_by_channel/content-cards_in_canvas.md
+++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_by_channel/content-cards_in_canvas.md
@@ -65,7 +65,7 @@ If a step contains only Content Cards (and no other messaging channel), you can
 |---|---|
 | Advance When Message Sent | Users will advance to the next steps of the Canvas when the Content Card has been successfully sent. Use this option when you want users to advance only if the card will be sent and not aborted. |
 | Immediately Advance Audience | Users will advance to the next steps of the Canvas when the Content Card sending is attempted. If the card is aborted and not sent, users will still advance to the next step. Use this option when you want users to advance regardless of whether the content card is sent successfully or aborted. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][2]
 
@@ -77,7 +77,7 @@ Canvas components with a Content Card and another messaging channel have the fol
 |---|---|
 | Advance When Message Sent | Users will advance to the next steps of the Canvas when at least one of the message types in this step have been sent successfully.|
 | Immediately Advance Audience | When this option is selected, everyone in the component's audience will advance to the next steps after the delay elapses, whether they have seen the noted message or not.  <br> <br> _Users must match the component's segment and filter criteria to advance to next steps._ |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][3]
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_by_channel/in-app_messages_in_canvas.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_by_channel/in-app_messages_in_canvas.md
index 465ead26acc..8bfe94b216a 100644
--- a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_by_channel/in-app_messages_in_canvas.md
+++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_by_channel/in-app_messages_in_canvas.md
@@ -32,7 +32,7 @@ In the in-app message composer, you can choose when the in-app message will expi
 |---|---|---|
 | Message expires after specified period | The first option allows you to expire the in-app message relative to when the step becomes available to the user. | For example, an in-app message with a two-day expiration would become available after the step's delay elapses and audience options are checked. It would then be available for 2 days (48 hours) and during those two days, users may see the in-app message if they open the app. |
 | Message expires by specified date | The second option allows you to choose a specific date and time when the in-app message will be no longer available. | For example, if you have a sale that ended at a specific date and time, you might select this option so that users no longer see the associated in-app message when the sale ends. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Use cases
 
@@ -182,7 +182,7 @@ Steps with an in-app message and another channel have the following advancement
 |---|---|---|
 | Advance When Message Sent | Users must be sent an email, webhook, or push notification, or view the in-app message to advance to subsequent steps in the Canvas.  <br> <br>  If the in-app message expires and the user hasn't been sent the email, webhook, or push, or hasn't viewed the in-app message, they will exit the Canvas and will not advance to subsequent steps. |
 | Immediately Advance Audience | Everyone in the step's audience advances to the next steps after the delay elapses, whether they have seen the noted message or not.  <br> <br> Users must match the step's segment and filter criteria to advance to the next steps. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][3]
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_comments.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_comments.md
index 8d7fdd37a95..53e14b06bb8 100644
--- a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_comments.md
+++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_comments.md
@@ -36,7 +36,7 @@ You can also use keyboard shortcuts to add comments:
 | --- | --- |
 | <kbd>⌘</kbd> + <kbd>Enter</kbd> | <kbd>Ctrl</kbd> + <kbd>Enter</kbd>|
 | <kbd>Tab</kbd> + <kbd>Enter</kbd> | <kbd>Tab</kbd> + <kbd>Enter</kbd> |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 To view an existing comment, open the sidebar or select the <i class="fas fa-comment"></i> comment icon next to the step name. You can also reply to existing comments in a thread. 
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties.md
index 66b42a9980c..b4d73f4f382 100644
--- a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties.md
+++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties.md
@@ -29,7 +29,7 @@ Refer to the following table for a summary of differences between `canvas_entry_
 | **Persistence** | Can be referenced by all [Message][1] steps for the duration of a Canvas built using Canvas Flow. | - Can only be referenced once. <br> - Cannot be referenced by any subsequent Message steps. |
 | **Original Canvas behavior** | - Must have persistent entry properties turned on. <br> - Can only reference `canvas_entry_properties` in the first full step of a Canvas. The Canvas must be action-based or API triggered. | - Can reference `event_properties` in any full step that uses action-based delivery in a Canvas. <br> - Cannot be used in scheduled full steps other than the first full step of an action-based Canvas. However, if a user is using a [Canvas component][2], the behavior follows the Canvas Flow rules for `event_properties`. |
 | **Canvas Flow behavior** | Can reference `canvas_entry_properties` in any step of a Canvas. | - Can reference `event_properties` in the first Message step **after** an [Action Paths][3] step where the action taken is a custom event or purchase event. <br> - Cannot be after the Everyone Else path of the Action Paths step. <br> - Can have other non-Message Canvas components in between the Action Paths and Message steps. If one of these non-Message components is an Action Paths step, the user can go through that action path's Everyone Else path. | 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Note that Canvas entry properties are only available for reference in Liquid. To filter on the properties within the Canvas, use [event property segmentation]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/nested_objects/) instead.
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/preview_user_paths.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/preview_user_paths.md
index 6bc99968223..77f108a098e 100644
--- a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/preview_user_paths.md
+++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/preview_user_paths.md
@@ -1,6 +1,7 @@
 ---
 nav_title: Preview User Paths
 article_title: Preview User Paths
+page_order: 0.3
 alias: /preview_user_paths/
 description: "This reference article covers how to preview user paths in Canvas."
 Tool:
diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/rate_limiting.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/rate_limiting.md
new file mode 100644
index 00000000000..19548143eae
--- /dev/null
+++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/rate_limiting.md
@@ -0,0 +1,6 @@
+---
+nav_title: Rate Limiting
+page_order: 3.9
+layout: redirect
+redirect_to: /docs/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#canvas-delivery-speed
+---
\ No newline at end of file
diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/time_based_canvas.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/time_based_canvas.md
index 16d97a731c0..a6e160df4c5 100644
--- a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/time_based_canvas.md
+++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/time_based_canvas.md
@@ -23,7 +23,7 @@ As of February 28, 2023, you can no longer create or duplicate Canvases using th
 | Definition |  Time Zone |
 | --- | --- |
 | Send message immediately after the user receives the previous step, or if this is the first step, immediately after the user enters the Canvas. | N/A |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][1]
 
@@ -32,7 +32,7 @@ As of February 28, 2023, you can no longer create or duplicate Canvases using th
 | Definition |  Time Zone |
 | --- | --- |
 | Send message after a delay. You can specify a delay in seconds, minutes, hours, days, or weeks.  | N/A |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][2]
 
@@ -41,7 +41,7 @@ As of February 28, 2023, you can no longer create or duplicate Canvases using th
 | Definition |  Time Zone |
 | --- | --- |
 | Send message on the next specified day of the week, at a selected time of day.  | Select between **user's local time** or **company time** |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For example, suppose you select "Send on the next Saturday at 3:15 pm". If a user enters the Canvas on a Saturday, they would receive that message on the next Saturday in seven days. If they enter on a Friday, the next Saturday would be in one day.
 
@@ -62,7 +62,7 @@ Canvas calculates the delay as `day of the week` + `calendar days`, then adds th
 | Definition | Time Zone |
 | ---------- | ----- |
 | [Intelligent Timing]({{site.baseurl}}/user_guide/brazeai/intelligence/intelligent_timing/) calculates the optimal send time based on a statistical analysis of your user's past interactions with your messaging (on a per channel basis) and app. | If you select **a specific time** as your [fallback]({{site.baseurl}}/user_guide/brazeai/intelligence/intelligent_timing/#fallback-options), this will be sent in the user's local time. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][5]
 
@@ -71,7 +71,7 @@ Canvas calculates the delay as `day of the week` + `calendar days`, then adds th
 | Definition | Time Zone |
 | --- | --- |
 | Limit how many times each user should receive the Canvas within a certain time frame, which can be measured in minutes, days, weeks (seven days), and months. | User's local time. If a user's time zone isn't set, this will fall back to company time zone. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 [Frequency capping]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#frequency-capping) is based on calendar days, not a 24-hour period. This means that you could set up a frequency capping rule of sending no more than one campaign a day, but if a user receives a message at 11 pm in their local time, they can still receive another message an hour later (on midnight the next calendar day).
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/ideas_and_strategies/lead_scoring.md b/_docs/_user_guide/engagement_tools/canvas/ideas_and_strategies/lead_scoring.md
index 61d0c9ad1bd..16c94091a41 100644
--- a/_docs/_user_guide/engagement_tools/canvas/ideas_and_strategies/lead_scoring.md
+++ b/_docs/_user_guide/engagement_tools/canvas/ideas_and_strategies/lead_scoring.md
@@ -103,7 +103,7 @@ In each User Update step’s **Compose** tab, do the following for the respectiv
 | **Attribute Name** | Select the lead score attribute you selected in step 2 (`lead score`).|
 | **Action** | Change the action to **Increment By** if the path increases the score or **Decrement By** if the path decreases the score |
 | **Increment By** or **Decrement By** | Enter the number of points that will be increased or decreased from the lead score.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Step 5: Launch your Canvas
 
diff --git a/_docs/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md b/_docs/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md
index 2436c67d859..69142a8e6e2 100644
--- a/_docs/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md
+++ b/_docs/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md
@@ -114,7 +114,10 @@ If you intend to make larger edits that lead to creating a new Canvas copy entir
 
 ### Deleting variants
 
-When variants are deleted from a Canvas, the steps within the variant (including those shared by other variants) will be deleted. When the steps are deleted, you won't be able to view their Canvas analytics. Note that users in deleted variants are exited from the steps, and any following messages are not sent. 
+When variants are deleted from a Canvas, the following occurs:
+- Steps within the variant (including those shared by other variants) will be deleted. 
+- The step analytics and the top-level analytics for the Canvas, such as _Total Entries_, _Total Exits_, and _Conversion Rate_, will be deleted.
+- Users in deleted variants are exited from the steps, and any following messages are not sent.
 
 ## Best practices
 
diff --git a/_docs/_user_guide/engagement_tools/landing_pages/connect_domain.md b/_docs/_user_guide/engagement_tools/landing_pages/connect_domain.md
new file mode 100644
index 00000000000..ddbfb4619f2
--- /dev/null
+++ b/_docs/_user_guide/engagement_tools/landing_pages/connect_domain.md
@@ -0,0 +1,64 @@
+---
+nav_title: Connecting Your Domain
+article_title: Connecting Your Domain
+description: "This article covers how to connect your own custom domain to Braze landing pages."
+page_order: 1
+alias: /landing_pages/connect_domain/
+---
+
+# Connecting your domain
+
+> Connect your own domain to your Braze workspace to customize your landing page URLs with your brand.
+
+{% alert note %}
+Landing pages are currently in beta. Contact your Braze account manager if you’re interested in participating in this beta.
+{% endalert %}
+
+To connect a domain or subdomain to your Braze account, have an administrator follow the steps below.
+
+1. Go to **Settings** > **Landing Page Settings**.
+2. Enter the domain or subdomain you want to connect and select **Submit**. For example, `forms.example.com`.
+3. Copy and paste the **TXT** and **CNAME** records into the DNS settings of your domain provider.
+4. Return to the Braze dashboard to verify the connection.
+
+![Landing Page Settings page with one TXT and two CNAME records listed with their respective names and values.][1]
+
+{% alert note %}
+Depending on your domain provider, the connection can take up to 48 hours. When the process is complete, we’ll start using your custom domain for your landing pages in the Braze dashboard.
+{% endalert %}
+
+## Using your domain in Braze
+
+After your domain verification is completed, it will be used by default in Braze. For example, if you connect the subdomain `forms.example.com`, your landing page URLs will be updated to look like `forms.example.com/holiday-sale`.
+
+{% alert note %}
+Custom domain deletion is coming soon. Contact your customer success manager if you need to remove your subdomain.
+{% endalert %}
+
+## Resources from domain providers
+
+Listed below are resources for creating and managing DNS records with commonly used domain providers. If you're using a different provider, refer to that provider's documentation or contact their support team for information.
+
+| Domain provider | Resources |
+| --- | --- |
+| Bluehost | [DNS Records Explained](https://my.bluehost.com/hosting/help/508)<br> [DNS Management Add Edit or Delete DNS Entries](https://my.bluehost.com/hosting/help/559) |
+| Dreamhost | [How do I add custom DNS records?](https://help.dreamhost.com/hc/en-us/articles/360035516812) |
+| GoDaddy | [Add a CNAME record](https://www.godaddy.com/help/add-a-cname-record-19236?) |
+| Cloudflare | [Manage DNS records](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/) |
+| Squarespace | [Adding custom DNS settings](https://support.squarespace.com/hc/en-us/articles/360002101888-Adding-custom-DNS-records-to-your-Squarespace-managed-domain) |
+
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+
+## Troubleshooting 
+
+### My domain connection failed
+
+Verify that your domain was entered correctly and that it matches what you submitted to Braze from your domain provider account. If it's correct and matches, check the TXT and CNAME records provided by Braze. They should match the records you entered into your domain provider account.
+
+## Frequently asked questions
+
+### Can I connect multiple subdomains to my workspace or connect one subdomain to multiple workspaces?
+
+No, you currently can only connect one subdomain to a workspace.
+
+[1]: {% image_buster /assets/img/landing_pages/connect_subdomain.png %}
diff --git a/_docs/_user_guide/engagement_tools/landing_pages/connect_subdomain.md b/_docs/_user_guide/engagement_tools/landing_pages/connect_subdomain.md
deleted file mode 100644
index 5179a4f041f..00000000000
--- a/_docs/_user_guide/engagement_tools/landing_pages/connect_subdomain.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-nav_title: Connecting a Subdomain
-article_title: Connecting a Subdomain
-description: "This article covers how to connect your third-party domain's subdomains to your Braze account."
-page_order: 1
-alias: /landing_pages/connect_subdomain/
----
-
-# Connecting a subdomain
-
-> If you own a domain through a third-party service, you can connect its subdomains to your Braze account. You can then use subdomains with your Braze-hosted landing pages to brand and customize your URLs. 
-
-{% alert note %}
-Landing pages are currently in beta. Contact your Braze account manager if you’re interested in participating in this beta.
-{% endalert %}
-
-To connect a subdomain to your Braze account, have an administrator follow the steps below.
-
-1. Go to **Settings** > **Landing Page Settings**.
-2. Enter the subdomain you want to connect and select **Submit**.
-3. Copy and paste the **TXT** and **CNAME** records into the relevant settings of your domain provider account.
-4. Return to the Braze dashboard to verify the connection.
-
-![Landing Page Settings page with one TXT and two CNAME records listed with their respective names and values.][1]
-
-{% alert note %}
-Depending on your domain provider, the subdomain connection can take up to 48 hours. When the process is complete, we’ll update your **Landing Page Settings** page.
-{% endalert %}
-
-## Using your subdomain
-
-After your subdomain verification is complete, you can use your subdomain for your Braze-hosted landing pages by default. For example, if you connect the subdomain `promo.example.com`, you can add a URL to your landing page that looks like `promo.example.com/holiday-sale`.
-
-{% alert note %}
-Contact your customer success manager if you need to remove your subdomain.
-{% endalert %}
-
-## Resources from domain providers
-
-Listed below are resources for creating and managing DNS records with commonly used domain providers. If you're using a different provider, refer to that provider's documentation or contact their support team for information.
-
-| Domain provider | Resources |
-| --- | --- |
-| Bluehost | [DNS Records Explained](https://my.bluehost.com/hosting/help/508)<br> [DNS Management Add Edit or Delete DNS Entries](https://my.bluehost.com/hosting/help/559) |
-| Dreamhost | [How do I add custom DNS records?](https://help.dreamhost.com/hc/en-us/articles/360035516812) |
-| GoDaddy | [Add a CNAME record](https://www.godaddy.com/help/add-a-cname-record-19236?) |
-{: .reset-td-br-1 .reset-td-br-2}
-
-## Troubleshooting 
-
-### My subdomain connection failed
-
-Verify that your subdomain was entered correctly and that it matches what you submitted to Braze from your domain provider account. If it's correct and matches, check the TXT and CNAME records provided by Braze. They should match the records you entered into your domain provider account.
-
-## Frequently asked questions
-
-### Can I connect multiple subdomains to my workspace or connect one subdomain to multiple workspaces?
-
-No, you currently can only connect one subdomain to a workspace.
-
-[1]: {% image_buster /assets/img/landing_pages/connect_subdomain.png %}
\ No newline at end of file
diff --git a/_docs/_user_guide/engagement_tools/landing_pages/drag_and_drop.md b/_docs/_user_guide/engagement_tools/landing_pages/drag_and_drop.md
index 0a017073703..c2dee80407e 100644
--- a/_docs/_user_guide/engagement_tools/landing_pages/drag_and_drop.md
+++ b/_docs/_user_guide/engagement_tools/landing_pages/drag_and_drop.md
@@ -40,7 +40,7 @@ We suggest following these best practices:
 | Site description | A text snippet that displays in search results. | Use between 140-160 characters.|
 | Favicon | The icon that appears next to the site title on the browser tab. | Use an aspect ratio of 1:1, and a supported file type of PNG, JPEG, or ICO. |
 | URL handle | This is the link users will click to navigate to your landing page. | This must be unique. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert note %}
 Custom subdomain support is not available during the beta.
@@ -60,6 +60,8 @@ The editor uses two types of components for landing page composition: rows and b
 
 #### Form block
 
+Use various form block components to log custom and standard profile attributes and custom events. The input field form block can log both standard and custom attributes for your users, and the phone capture and email capture form blocks can capture phone and email fields for your users' form submissions. Button actions can be logged as custom attributes, custom events, or both on form submission. 
+
 If you include a form block, you must include at least one button with the toggle turned on for **Submit form when button is clicked**. You should also create another landing page for the [confirmation state](#confirmation-state).
 
 ![A form block that registers a new customer and will send a discount code to their email.][5]{: style="max-width:70%;"}
@@ -111,7 +113,7 @@ During the beta, each form submission on a landing page will create a new anonym
 When a user submits a form, a new Braze user profile is created with the submitted user data.
 
 {% alert note %}
-During the beta, Braze will create a new user with each form submission regardless of where the user clicks on the landing page.
+During the beta, Braze will create a new user upon every form submission.
 {% endalert %}
 
 ### Are there any technical requirements to publish a landing page?
diff --git a/_docs/_user_guide/engagement_tools/locations_and_geofences/location_tracking.md b/_docs/_user_guide/engagement_tools/locations_and_geofences/location_tracking.md
index 2f424c590b8..25aeadb2de6 100644
--- a/_docs/_user_guide/engagement_tools/locations_and_geofences/location_tracking.md
+++ b/_docs/_user_guide/engagement_tools/locations_and_geofences/location_tracking.md
@@ -47,13 +47,13 @@ Authorization: Bearer YOUR-REST-API-KEY
 }
 ```
 
-## Technology partners
+## Partnership support for beacon and geofence
 
-You can also leverage location tracking with some of our partners: 
+Combining existing beacon or geofence support with our targeting and messaging features gives you more information about your users' physical actions so you can message them accordingly. You can leverage location tracking with some of our partners: 
 
 - [Radar][6]
-- [Foursquare][7]
 - [Gimbal][10]
+- [Foursquare][7]
 
 ## Frequently asked questions
 
diff --git a/_docs/_user_guide/engagement_tools/news_feed/creating_a_news_feed_item.md b/_docs/_user_guide/engagement_tools/news_feed/creating_a_news_feed_item.md
index be8eb7ae5f6..507e079a06a 100644
--- a/_docs/_user_guide/engagement_tools/news_feed/creating_a_news_feed_item.md
+++ b/_docs/_user_guide/engagement_tools/news_feed/creating_a_news_feed_item.md
@@ -66,7 +66,7 @@ Banner cards consist of:
 |          Classic         | 1:1 (110 pixels wide minimum) |          500&nbsp;KB         |         1&nbsp;MB        | PNG, JPEG, GIF |
 |          Captioned image         | 4:3 (600 pixels wide minimum) |          500&nbsp;KB         |         1&nbsp;MB        | PNG, JPEG, GIF |
 |          Banner         | 6:1 (600 pixels wide minimum) |          500&nbsp;KB         |         1&nbsp;MB        | PNG, JPEG, GIF |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 - PNG files are recommended.
 - A custom image loading library is required to display GIFs on Android. We recommend Glide.
diff --git a/_docs/_user_guide/engagement_tools/segments.md b/_docs/_user_guide/engagement_tools/segments.md
index 1f2a10cb012..a4459457192 100644
--- a/_docs/_user_guide/engagement_tools/segments.md
+++ b/_docs/_user_guide/engagement_tools/segments.md
@@ -46,9 +46,6 @@ guide_menu_list:
   - name: Location Targeting
     link: /docs/user_guide/engagement_tools/segments/location_targeting/
     image: /assets/img/braze_icons/marker-pin-06.svg
-  - name: Beacon and Geofence Support
-    link: /docs/user_guide/engagement_tools/segments/beacon_support/
-    image: /assets/img/braze_icons/marker-pin-01.svg
   - name: Regular Expressions
     link: /docs/user_guide/engagement_tools/segments/regex/
     image: /assets/img/braze_icons/search-sm.svg
diff --git a/_docs/_user_guide/engagement_tools/segments/beacon_support.md b/_docs/_user_guide/engagement_tools/segments/beacon_support.md
deleted file mode 100644
index f9abcf47145..00000000000
--- a/_docs/_user_guide/engagement_tools/segments/beacon_support.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-nav_title: Beacon and Geofence Support
-article_title: Beacon and Geofence Support
-page_order: 7
-page_type: reference
-tool: 
-  - Segments
-  - Location
-description: "This article briefly discusses Beacon and Geofence support and how to use your location partner account to begin location tracking."
-
----
-
-# Beacon and geofence support
-
-> This article briefly discusses Beacon and Geofence support and how to use your location partner account to begin location tracking.
-
-Combining existing beacon or geofence support with our targeting and messaging features allows you to learn more about your user's physical actions and message them accordingly.
-
-## Radar support
-
-Radar has full support for unlimited custom geofences, pre-built POI geofences, beacon detection, region detection, trip tracking, and more. When you enable the Radar and Braze integration, Radar forwards real time location events and user attributes which can be used to trigger real time campaigns, power last mile pickup and delivery operations, optimize fleet tracking and shipping logistics, or build user segments based on location patterns. Additionally, Radar Geo APIs can be leveraged to enrich or personalize your marketing campaigns through Connected Content. Visit [Radar integrations]({{site.baseurl}}/partners/message_personalization/location/radar/#radar) to learn more.
-
-## Gimbal places support
-
-Connecting your Gimbal Account to Braze lets you track when your users enter or leave your defined places and trigger events off of these entries and exits. In addition, you can track extra information like the Place name or the Dwell visit as an event property so that you can personalize your messaging even further. Refer to Gimbal's documentation along with our instructions for [iOS][1] and [Android][2] integration. 
-
-{% alert note %}
-Note that this will work the same for Gimbal's beacons as well as their geofence solutions.
-{% endalert %}
-
-[1]: {{site.baseurl}}/developer_guide/platform_integration_guides/ios/advanced_use_cases/beacon_integration/
-[2]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/advanced_use_cases/beacon_integration/#beacon-integration
diff --git a/_docs/_user_guide/engagement_tools/segments/location_targeting.md b/_docs/_user_guide/engagement_tools/segments/location_targeting.md
index 469c670a0c4..ad2d529dd80 100644
--- a/_docs/_user_guide/engagement_tools/segments/location_targeting.md
+++ b/_docs/_user_guide/engagement_tools/segments/location_targeting.md
@@ -42,9 +42,13 @@ For polygonal regions, you can more specifically designate which areas you wish
 
 ![An outline of New York state as the selected polygonal region.][4]{: style="max-width:70%;"}
 
-{% alert tip %}
-Interested in taking advantage of location targeting with the help of a Braze partner? Check out our available Braze [contextual location partners]({{site.baseurl}}/partners/message_personalization/location/).
-{% endalert %}
+## Partnership support for beacon and geofence
+
+Combining existing beacon or geofence support with our targeting and messaging features gives you more information about your users' physical actions so you can message them accordingly. You can leverage location tracking with some of our partners: 
+
+- [Radar][6]
+- [Gimbal][10]
+- [Foursquare][7]
 
 [1]: {% image_buster /assets/img_archive/createsegment2.png %}
 [2]: {% image_buster /assets/img_archive/filter_recent_location.png %}
diff --git a/_docs/_user_guide/engagement_tools/segments/segment_insights.md b/_docs/_user_guide/engagement_tools/segments/segment_insights.md
index 535b5f68528..9dfdcefb47f 100644
--- a/_docs/_user_guide/engagement_tools/segments/segment_insights.md
+++ b/_docs/_user_guide/engagement_tools/segments/segment_insights.md
@@ -35,7 +35,7 @@ The baseline segment can either be a specific segment you select, or a segment c
 | Lifetime Revenue | Average lifetime revenue for segment users | user lifetime spend |
 | Time to First Purchase | Average time between segment users' first session and first purchase | date of first purchase – date of first session |
 | Time Since Last Purchase | Average time between segment users' last purchase and now | today – date of last purchase |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 You can easily share specific comparisons with your teammates using the page's unique URL, and you can also click beneath each segment to reveal more information about that segment. These comparisons will reset when you switch between workspaces.
 
diff --git a/_docs/_user_guide/engagement_tools/segments/sql_segments/catalog_segments.md b/_docs/_user_guide/engagement_tools/segments/sql_segments/catalog_segments.md
index 92cee50d79f..f5827e91b8a 100644
--- a/_docs/_user_guide/engagement_tools/segments/sql_segments/catalog_segments.md
+++ b/_docs/_user_guide/engagement_tools/segments/sql_segments/catalog_segments.md
@@ -35,7 +35,7 @@ Here are guidelines to select the variables:
 | `Catalog field`| The field in your catalog that contains the same values as your `Custom event property`. This is often a type of ID. In the ecommerce use case, this would be `shopify_id`. |
 | `Custom event` | The name of your custom event, which is the same event that contains a property with values matching your `Catalog field`. In the ecommerce use case, this would be `Made Order`. |
 | `Custom event property` | The name of your custom event property, which matches values with your `Catalog field`. In the ecommerce example use case, this would be `Shopify_ID.`|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {: start="4"}
 4. If needed, fill in additional optional fields for your use case to segment by a particular field value within your catalog:
@@ -64,7 +64,7 @@ You would set up a catalog segment by using the following variables:
 | `Custom event property` | doctor ID |
 | `(Under Filter SQL Results) Catalog field` | Specialty |
 | `(Under Filter SQL Results) Value`| Dental |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### SaaS platform
 
@@ -84,7 +84,7 @@ You would set up a catalog segment by using the following variables:
 | `Custom event property` | account ID |
 | `(Under Filter SQL Results) Catalog field` | Classification |
 | `(Under Filter SQL Results) Value` | Enterprise |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Frequently asked questions
 
diff --git a/_docs/_user_guide/engagement_tools/segments/sql_segments/sql_segments_tables.md b/_docs/_user_guide/engagement_tools/segments/sql_segments/sql_segments_tables.md
index d8ad8be032b..fff8908dfbf 100644
--- a/_docs/_user_guide/engagement_tools/segments/sql_segments/sql_segments_tables.md
+++ b/_docs/_user_guide/engagement_tools/segments/sql_segments/sql_segments_tables.md
@@ -121,7 +121,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] Advertising identifier
 `ad_id_type` | `null,`&nbsp;`string` | One of `ios_idfa`, `google_ad_id`, `windows_ad_id`, OR `roku_ad_id`
 `ad_tracking_enabled` | `null, boolean` | Whether advertising tracking is enabled for the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_INSTALLATTRIBUTION_SHARED {#USERS_BEHAVIORS_INSTALLATTRIBUTION_SHARED}
 
@@ -134,7 +134,7 @@ Field | Type | Description
 `app_group_api_id` | `null,`&nbsp;`string` | API ID of the workspace this user belongs to
 `time` | `int` | Unix timestamp at which the user installed
 `source` | `string` | the source of the attribution
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_LOCATION_SHARED {#USERS_BEHAVIORS_LOCATION_SHARED}
 
@@ -159,7 +159,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] Advertising identifier
 `ad_id_type` | `null,`&nbsp;`string` | One of `ios_idfa`, `google_ad_id`, `windows_ad_id`, OR `roku_ad_id`
 `ad_tracking_enabled` | `null, boolean` | Whether advertising tracking is enabled for the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_PURCHASE_SHARED {#USERS_BEHAVIORS_PURCHASE_SHARED}
 
@@ -183,7 +183,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] Advertising identifier
 `ad_id_type` | `null,`&nbsp;`string` | One of `ios_idfa`, `google_ad_id`, `windows_ad_id`, OR `roku_ad_id`
 `ad_tracking_enabled` | `null, boolean` | Whether advertising tracking is enabled for the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_UNINSTALL_SHARED {#USERS_BEHAVIORS_UNINSTALL_SHARED}
 
@@ -196,7 +196,7 @@ Field | Type | Description
 `app_group_api_id` | `null,`&nbsp;`string` | API ID of the workspace this user belongs to
 `app_api_id` | `null,`&nbsp;`string` | API ID of the app that was uninstalled
 `time` | `int` | Unix timestamp at which the user uninstalled
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_UPGRADEDAPP_SHARED {#USERS_BEHAVIORS_UPGRADEDAPP_SHARED}
 
@@ -215,7 +215,7 @@ Field | Type | Description
 `device_model` | `null,`&nbsp;`string` | Model of the device
 `old_app_version` | `null,`&nbsp;`string` | Old version of the app
 `new_app_version` | `null,`&nbsp;`string` | New version of the app
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_APP_FIRSTSESSION_SHARED {#USERS_BEHAVIORS_APP_FIRSTSESSION_SHARED}
 
@@ -237,7 +237,7 @@ Field | Type | Description
 `platform` | `null,`&nbsp;`string` | Platform of the device
 `os_version` | `null,`&nbsp;`string` | Version of the operating system of the device
 `device_model` | `null,`&nbsp;`string` | Model of the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_APP_NEWSFEEDIMPRESSION_SHARED {#USERS_BEHAVIORS_APP_NEWSFEEDIMPRESSION_SHARED}
 
@@ -254,7 +254,7 @@ Field | Type | Description
 `platform` | `null,`&nbsp;`string` | Platform of the device
 `os_version` | `null,`&nbsp;`string` | Version of the operating system of the device
 `device_model` | `null,`&nbsp;`string` | Model of the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_APP_SESSIONEND_SHARED {#USERS_BEHAVIORS_APP_SESSIONEND_SHARED}
 
@@ -273,7 +273,7 @@ Field | Type | Description
 `platform` | `null,`&nbsp;`string` | Platform of the device
 `os_version` | `null,`&nbsp;`string` | Version of the operating system of the device
 `device_model` | `null,`&nbsp;`string` | Model of the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_APP_SESSIONSTART_SHARED {#USERS_BEHAVIORS_APP_SESSIONSTART_SHARED}
 
@@ -291,7 +291,7 @@ Field | Type | Description
 `platform` | `null,`&nbsp;`string` | Platform of the device
 `os_version` | `null,`&nbsp;`string` | Version of the operating system of the device
 `device_model` | `null,`&nbsp;`string` | Model of the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_GEOFENCE_DATAEVENT_SHARED {#USERS_BEHAVIORS_GEOFENCE_DATAEVENT_SHARED}
 
@@ -311,7 +311,7 @@ Field | Type | Description
 `event_type` | `string` | What kind of geofence event was triggered. (for example, 'enter' or 'exit')
 `location_set_id` | `string` | The ID of the location set of the geofence that was triggered
 `geofence_id` | `string` | The ID of the geofence that was triggered
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_GEOFENCE_RECORDEVENT_SHARED {#USERS_BEHAVIORS_GEOFENCE_RECORDEVENT_SHARED}
 
@@ -331,7 +331,7 @@ Field | Type | Description
 `event_type` | `string` | What kind of geofence event was triggered. (for example, 'enter' or 'exit')
 `location_set_id` | `string` | The ID of the location set of the geofence that was triggered
 `geofence_id` | `string` | The ID of the geofence that was triggered
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_SUBSCRIPTION_GLOBALSTATECHANGE_SHARED {#USERS_BEHAVIORS_SUBSCRIPTION_GLOBALSTATECHANGE_SHARED}
 
@@ -356,7 +356,7 @@ Field | Type | Description
 `canvas_variation_api_id` | `null,`&nbsp;`string` | API ID of the Canvas variation this event belongs to
 `canvas_step_api_id` | `null,`&nbsp;`string` | API ID of the Canvas step this event belongs to
 `send_id` | `null,`&nbsp;`string` | Message send ID this subscription state change action originated from
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_BEHAVIORS_SUBSCRIPTIONGROUP_STATECHANGE_SHARED {#USERS_BEHAVIORS_SUBSCRIPTIONGROUP_STATECHANGE_SHARED}
 
@@ -384,7 +384,7 @@ Field | Type | Description
 `timezone` | `null,`&nbsp;`string` | Time zone of the user
 `send_id` | `null,`&nbsp;`string` | Message send ID this subscription state change action originated from
 `state_change_source` | `null,`&nbsp;`string` | Source of the state change (REST, SDK, Dashboard, etc)
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Campaigns
 
@@ -409,7 +409,7 @@ Field | Type | Description
 `country` | `null,`&nbsp;`string` | [PII] Country of the user
 `timezone` | `null,`&nbsp;`string` | Time zone of the user
 `language` | `null,`&nbsp;`string` | [PII] Language of the user
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CAMPAIGNS_ENROLLINCONTROL_SHARED {#USERS_CAMPAIGNS_ENROLLINCONTROL_SHARED}
 
@@ -431,7 +431,7 @@ Field | Type | Description
 `country` | `null,`&nbsp;`string` | [PII] Country of the user
 `timezone` | `null,`&nbsp;`string` | Time zone of the user
 `language` | `null,`&nbsp;`string` | [PII] Language of the user
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CAMPAIGNS_FREQUENCYCAP_SHARED {#USERS_CAMPAIGNS_FREQUENCYCAP_SHARED}
 
@@ -453,7 +453,7 @@ Field | Type | Description
 `country` | `null,`&nbsp;`string` | [PII] Country of the user
 `timezone` | `null,`&nbsp;`string` | Time zone of the user
 `language` | `null,`&nbsp;`string` | [PII] Language of the user
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CAMPAIGNS_REVENUE_SHARED {#USERS_CAMPAIGNS_REVENUE_SHARED}
 
@@ -476,7 +476,7 @@ Field | Type | Description
 `timezone` | `null,`&nbsp;`string` | Time zone of the user
 `language` | `null,`&nbsp;`string` | [PII] Language of the user
 `revenue` | `long` | The amount of USD revenue in cents generated
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Canvas
 
@@ -503,7 +503,7 @@ Field | Type | Description
 | `timezone`                             | `string`,&nbsp;`null`    | Time zone of the user                                                                                            |
 | `language`                             | `string`,&nbsp;`null`    | [PII] Language of the user                                                                                      |
 | `sf_created_at`                        | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                                                                   |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CANVAS_ENTRY_SHARED {#USERS_CANVAS_ENTRY_SHARED}
 
@@ -526,7 +526,7 @@ Field | Type | Description
 | `language`                | `string`,&nbsp;`null`    | [PII] Language of the user                                           |
 | `in_control_group`        | `boolean`,&nbsp;`null`   | True if the user was enrolled in the control group                   |
 | `sf_created_at`           | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                        |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CANVAS_EXIT_MATCHEDAUDIENCE_SHARED {#USERS_CANVAS_EXIT_MATCHEDAUDIENCE_SHARED}
 
@@ -545,7 +545,7 @@ Field | Type | Description
 | `canvas_step_api_id`      | `string`,&nbsp;`null`    | API ID of the Canvas step this event belongs to                      |
 | `sf_created_at`           | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                        |
 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CANVAS_EXIT_PERFORMEDEVENT_SHARED {#USERS_CANVAS_EXIT_PERFORMEDEVENT_SHARED}
 
@@ -563,7 +563,7 @@ Field | Type | Description
 | `canvas_variation_api_id` | `string`,&nbsp;`null`    | API ID of the Canvas variation this event belongs to                 |
 | `canvas_step_api_id`      | `string`,&nbsp;`null`    | API ID of the Canvas step this event belongs to                      |
 | `sf_created_at`           | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                        |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CANVAS_EXPERIMENTSTEP_CONVERSION_SHARED {#USERS_CANVAS_EXPERIMENTSTEP_CONVERSION_SHARED}
 
@@ -583,7 +583,7 @@ Field | Type | Description
 | `experiment_step_api_id`    | `string`,&nbsp;`null`    | API ID of the Experiment step this event belongs to                                                             |
 | `conversion_behavior_index` | `int`,&nbsp;`null`       | Type of conversion event the user performed where "0" is a primary conversion and "1" is a secondary conversion |
 | `sf_created_at`             | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                                                                   |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CANVAS_EXPERIMENTSTEP_SPLITENTRY_SHARED {#USERS_CANVAS_EXPERIMENTSTEP_SPLITENTRY_SHARED}
 
@@ -603,7 +603,7 @@ Field | Type | Description
 | `in_control_group`        | `boolean`,&nbsp;`null`   | True if the user was enrolled in the control group                   |
 | `sf_created_at`           | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                        |
 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CANVAS_FREQUENCYCAP_SHARED {#USERS_CANVAS_FREQUENCYCAP_SHARED}
 
@@ -627,7 +627,7 @@ Field | Type | Description
 | `timezone`                             | `string`,&nbsp;`null`    | Time zone of the user                                                 |
 | `language`                             | `string`,&nbsp;`null`    | [PII] Language of the user                                           |
 | `sf_created_at`                        | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                        |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_CANVAS_REVENUE_SHARED {#USERS_CANVAS_REVENUE_SHARED}
 
@@ -651,7 +651,7 @@ Field | Type | Description
 | `language`                             | `string`,&nbsp;`null`    | [PII] Language of the user                                           |
 | `revenue`                              | `int`,&nbsp;`null`       | Amount of revenue generated in USD, displayed as cents               |
 | `sf_created_at`                        | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                        |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Messages
 
@@ -681,7 +681,7 @@ Field | Type | Description
 `language` | `null,`&nbsp;`string` | [PII] Language of the user
 `abort_type` | `null,`&nbsp;`string` | Type of abort, one of: `liquid_abort_message`, `quiet_hours`, `rate_limit`
 `abort_log` | `null,`&nbsp;`string` | [PII] Log message describing abort details (maximum of 128 characters)
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_CONTENTCARD_CLICK_SHARED {#USERS_MESSAGES_CONTENTCARD_CLICK_SHARED}
 
@@ -719,7 +719,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] Advertising identifier
 `ad_id_type` | `null,`&nbsp;`string` | One of `ios_idfa`, `google_ad_id`, `windows_ad_id`, OR `roku_ad_id`
 `ad_tracking_enabled` | `null, boolean` | Whether advertising tracking is enabled for the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_CONTENTCARD_DISMISS_SHARED {#USERS_MESSAGES_CONTENTCARD_DISMISS_SHARED}
 
@@ -757,7 +757,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] Advertising identifier
 `ad_id_type` | `null,`&nbsp;`string` | One of `ios_idfa`, `google_ad_id`, `windows_ad_id`, OR `roku_ad_id`
 `ad_tracking_enabled` | `null, boolean` | Whether advertising tracking is enabled for the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_CONTENTCARD_IMPRESSION_SHARED {#USERS_MESSAGES_CONTENTCARD_IMPRESSION_SHARED}
 
@@ -795,7 +795,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] Advertising identifier
 `ad_id_type` | `null,`&nbsp;`string` | One of `ios_idfa`, `google_ad_id`, `windows_ad_id`, OR `roku_ad_id`
 `ad_tracking_enabled` | `null, boolean` | Whether advertising tracking is enabled for the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_CONTENTCARD_SEND_SHARED {#USERS_MESSAGES_CONTENTCARD_SEND_SHARED}
 
@@ -822,7 +822,7 @@ Field | Type | Description
 `timezone` | `null,`&nbsp;`string` | Time zone of the user
 `language` | `null,`&nbsp;`string` | [PII] Language of the user
 `content_card_id` | `string` | ID of the card that generated this event
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_EMAIL_ABORT_SHARED {#USERS_MESSAGES_EMAIL_ABORT_SHARED}
 
@@ -852,7 +852,7 @@ Field | Type | Description
 `ip_pool` | `null,`&nbsp;`string` | IP Pool from which the email send was made
 `abort_type` | `null,`&nbsp;`string` | Type of abort, one of: `liquid_abort_message`, `quiet_hours`, `rate_limit`
 `abort_log` | `null,`&nbsp;`string` | [PII] Log message describing abort details (maximum of 128 characters)
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_EMAIL_BOUNCE_SHARED {#USERS_MESSAGES_EMAIL_BOUNCE_SHARED}
 
@@ -885,7 +885,7 @@ Field | Type | Description
 `esp` | `null,`&nbsp;`string` | ESP related to the event (SparkPost or SendGrid)
 `from_domain` | `null,`&nbsp;`string` | Sending domain for the email
 `is_drop` | `null, boolean` | Indicates that this event counts as a drop event
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_EMAIL_CLICK_SHARED {#USERS_MESSAGES_EMAIL_CLICK_SHARED}
 
@@ -920,7 +920,7 @@ Field | Type | Description
 `esp` | `null,`&nbsp;`string` | ESP related to the event (SparkPost or SendGrid)
 `from_domain` | `null,`&nbsp;`string` | Sending domain for the email
 `is_amp` | `null, boolean` | Indicates that this is an AMP event
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_EMAIL_DELIVERY_SHARED {#USERS_MESSAGES_EMAIL_DELIVERY_SHARED}
 
@@ -951,7 +951,7 @@ Field | Type | Description
 `ip_pool` | `null,`&nbsp;`string` | IP Pool from which the email send was made
 `esp` | `null,`&nbsp;`string` | ESP related to the event (SparkPost or SendGrid)
 `from_domain` | `null,`&nbsp;`string` | Sending domain for the email
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_EMAIL_MARKASSPAM_SHARED {#USERS_MESSAGES_EMAIL_MARKASSPAM_SHARED}
 
@@ -982,7 +982,7 @@ Field | Type | Description
 `ip_pool` | `null,`&nbsp;`string` | IP Pool from which the email send was made
 `esp` | `null,`&nbsp;`string` | ESP related to the event (SparkPost or SendGrid)
 `from_domain` | `null,`&nbsp;`string` | Sending domain for the email
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_EMAIL_OPEN_SHARED {#USERS_MESSAGES_EMAIL_OPEN_SHARED}
 
@@ -1015,7 +1015,7 @@ Field | Type | Description
 `esp` | `null,`&nbsp;`string` | ESP related to the event (SparkPost or SendGrid)
 `from_domain` | `null,`&nbsp;`string` | Sending domain for the email
 `is_amp` | `null, boolean` | Indicates that this is an AMP event
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_EMAIL_SEND_SHARED {#USERS_MESSAGES_EMAIL_SEND_SHARED}
 
@@ -1047,7 +1047,7 @@ Field | Type | Description
 `esp` | `null,`&nbsp;`string` | ESP related to the event (SparkPost or SendGrid)
 `from_domain` | `null,`&nbsp;`string` | Sending domain for the email
 `sf_created_at` | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_EMAIL_SOFTBOUNCE_SHARED {#USERS_MESSAGES_EMAIL_SOFTBOUNCE_SHARED}
 
@@ -1079,7 +1079,7 @@ Field | Type | Description
 `bounce_reason` | `null,`&nbsp;`string` | [PII] The SMTP reason code and user friendly message received for this bounce event
 `esp` | `null,`&nbsp;`string` | ESP related to the event (SparkPost or SendGrid)
 `from_domain` | `null,`&nbsp;`string` | Sending domain for the email
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_EMAIL_UNSUBSCRIBE_SHARED {#USERS_MESSAGES_EMAIL_UNSUBSCRIBE_SHARED}
 
@@ -1107,7 +1107,7 @@ Field | Type | Description
 `language` | `null,`&nbsp;`string` | [PII] Language of the user
 `email_address` | `string` | [PII] email address of the user
 `ip_pool` | `null,`&nbsp;`string` | IP Pool from which the email send was made
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_INAPPMESSAGE_ABORT_SHARED {#USERS_MESSAGES_INAPPMESSAGE_ABORT_SHARED}
 
@@ -1148,7 +1148,7 @@ Field | Type | Description
 `ad_tracking_enabled` | `null, boolean` | Whether advertising tracking is enabled for the device
 `abort_type` | `null,`&nbsp;`string` | Type of abort, one of: `liquid_abort_message`, `quiet_hours`, `rate_limit`
 `abort_log` | `null,`&nbsp;`string` | [PII] Log message describing abort details (maximum of 128 characters)
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_INAPPMESSAGE_CLICK_SHARED {#USERS_MESSAGES_INAPPMESSAGE_CLICK_SHARED}
 
@@ -1188,7 +1188,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] Advertising identifier
 `ad_id_type` | `null,`&nbsp;`string` | One of `ios_idfa`, `google_ad_id`, `windows_ad_id`, OR `roku_ad_id`
 `ad_tracking_enabled` | `null, boolean` | Whether advertising tracking is enabled for the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_INAPPMESSAGE_IMPRESSION_SHARED {#USERS_MESSAGES_INAPPMESSAGE_IMPRESSION_SHARED}
 
@@ -1227,7 +1227,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] Advertising identifier
 `ad_id_type` | `null,`&nbsp;`string` | One of `ios_idfa`, `google_ad_id`, `windows_ad_id`, OR `roku_ad_id`
 `ad_tracking_enabled` | `null, boolean` | Whether advertising tracking is enabled for the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_NEWSFEEDCARD_ABORT_SHARED {#USERS_MESSAGES_NEWSFEEDCARD_ABORT_SHARED}
 
@@ -1254,7 +1254,7 @@ Field | Type | Description
 `browser` | `null,`&nbsp;`string` | browser of the device
 `abort_type` | `null,`&nbsp;`string` | Type of abort, one of: `liquid_abort_message`, `quiet_hours`, `rate_limit`
 `abort_log` | `null,`&nbsp;`string` | [PII] Log message describing abort details (maximum of 128 characters)
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_NEWSFEEDCARD_CLICK_SHARED {#USERS_MESSAGES_NEWSFEEDCARD_CLICK_SHARED}
 
@@ -1279,7 +1279,7 @@ Field | Type | Description
 `resolution` | `null,`&nbsp;`string` | resolution of the device
 `carrier` | `null,`&nbsp;`string` | carrier of the device
 `browser` | `null,`&nbsp;`string` | browser of the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_NEWSFEEDCARD_IMPRESSION_SHARED {#USERS_MESSAGES_NEWSFEEDCARD_IMPRESSION_SHARED}
 
@@ -1304,7 +1304,7 @@ Field | Type | Description
 `resolution` | `null,`&nbsp;`string` | resolution of the device
 `carrier` | `null,`&nbsp;`string` | carrier of the device
 `browser` | `null,`&nbsp;`string` | browser of the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_PUSHNOTIFICATION_ABORT_SHARED {#USERS_MESSAGES_PUSHNOTIFICATION_ABORT_SHARED}
 
@@ -1334,7 +1334,7 @@ Field | Type | Description
 `platform` | `string` | Platform of the device
 `abort_type` | `null,`&nbsp;`string` | Type of abort, one of: `liquid_abort_message`, `quiet_hours`, `rate_limit`
 `abort_log` | `null,`&nbsp;`string` | [PII] Log message describing abort details (maximum of 128 characters)
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_PUSHNOTIFICATION_BOUNCE_SHARED {#USERS_MESSAGES_PUSHNOTIFICATION_BOUNCE_SHARED}
 
@@ -1366,7 +1366,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] advertising ID of the device that we made a delivery attempt to
 `ad_id_type` | `null,`&nbsp;`string` | Type of the advertising id
 `ad_tracking_enabled` | `null, boolean` | Whether or not tracking is enabled for advertising
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_PUSHNOTIFICATION_INFLUENCEDOPEN_SHARED {#USERS_MESSAGES_PUSHNOTIFICATION_INFLUENCEDOPEN_SHARED}
 
@@ -1400,7 +1400,7 @@ Field | Type | Description
 `resolution` | `null,`&nbsp;`string` | Resolution of the device
 `carrier` | `null,`&nbsp;`string` | Carrier of the device
 `browser` | `null,`&nbsp;`string` | Browser of the device
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_PUSHNOTIFICATION_IOSFOREGROUND_SHARED {#USERS_MESSAGES_PUSHNOTIFICATION_IOSFOREGROUND_SHARED}
 
@@ -1437,7 +1437,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] advertising ID of the device that we made a delivery attempt to
 `ad_id_type` | `null,`&nbsp;`string` | Type of the advertising id
 `ad_tracking_enabled` | `null, boolean` | Whether or not tracking is enabled for advertising
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_PUSHNOTIFICATION_OPEN_SHARED {#USERS_MESSAGES_PUSHNOTIFICATION_OPEN_SHARED}
 
@@ -1478,7 +1478,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] advertising ID of the device that we made a delivery attempt to
 `ad_id_type` | `null,`&nbsp;`string` | Type of the advertising id
 `ad_tracking_enabled` | `null, boolean` | Whether or not tracking is enabled for advertising
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_PUSHNOTIFICATION_SEND_SHARED {#USERS_MESSAGES_PUSHNOTIFICATION_SEND_SHARED}
 
@@ -1510,7 +1510,7 @@ Field | Type | Description
 `ad_id` | `null,`&nbsp;`string` | [PII] advertising ID of the device that we made a delivery attempt to
 `ad_id_type` | `null,`&nbsp;`string` | Type of the advertising id
 `ad_tracking_enabled` | `null, boolean` | Whether or not tracking is enabled for advertising
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_SMS_ABORT_SHARED {#USERS_MESSAGES_SMS_ABORT_SHARED}
 
@@ -1532,7 +1532,7 @@ Field | Type | Description
 `subscription_group_api_id` | `null,`&nbsp;`string` | External ID of the subscription group
 `abort_type` | `null,`&nbsp;`string` | Type of abort, one of: `liquid_abort_message`, `quiet_hours`, `rate_limit`
 `abort_log` | `null,`&nbsp;`string` | [PII] Log message describing abort details (maximum of 128 characters)
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_SMS_CARRIERSEND_SHARED {#USERS_MESSAGES_SMS_CARRIERSEND_SHARED}
 
@@ -1561,7 +1561,7 @@ Field | Type | Description
 `to_phone_number` | `null,`&nbsp;`string` | [PII] phone number of the recipient
 `from_phone_number` | `null,`&nbsp;`string` | phone number from which the SMS message was sent
 `subscription_group_api_id` | `null,`&nbsp;`string` | external ID of the subscription group
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_SMS_DELIVERY_SHARED {#USERS_MESSAGES_SMS_DELIVERY_SHARED}
 
@@ -1590,7 +1590,7 @@ Field | Type | Description
 `to_phone_number` | `null,`&nbsp;`string` | [PII] phone number of the recipient
 `from_phone_number` | `null,`&nbsp;`string` | Phone number from which the SMS message was sent
 `subscription_group_api_id` | `null,`&nbsp;`string` | External ID of the subscription group
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_SMS_DELIVERYFAILURE_SHARED {#USERS_MESSAGES_SMS_DELIVERYFAILURE_SHARED}
 
@@ -1620,7 +1620,7 @@ Field | Type | Description
 `subscription_group_api_id` | `null,`&nbsp;`string` | external ID of the subscription group
 `error` | `null,`&nbsp;`string` | error name
 `provider_error_code` | `null,`&nbsp;`string` | error code from SMS service provider
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_SMS_INBOUNDRECEIVE_SHARED {#USERS_MESSAGES_SMS_INBOUNDRECEIVE_SHARED}
 
@@ -1646,7 +1646,7 @@ Field | Type | Description
 `canvas_variation_api_id` | `null,`&nbsp;`string` | API ID of the Canvas variation this event belongs to
 `canvas_step_api_id` | `null,`&nbsp;`string` | API ID of the Canvas step this event belongs to
 `canvas_step_message_variation_api_id` | `null,`&nbsp;`string` | API ID of the Canvas step message variation this event belongs to
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_SMS_REJECTION_SHARED {#USERS_MESSAGES_SMS_REJECTION_SHARED}
 
@@ -1677,7 +1677,7 @@ Field | Type | Description
 `subscription_group_api_id` | `null,`&nbsp;`string` | external ID of the subscription group
 `error` | `null,`&nbsp;`string` | error name
 `provider_error_code` | `null,`&nbsp;`string` | error code from SMS service provider
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_SMS_SEND_SHARED {#USERS_MESSAGES_SMS_SEND_SHARED}
 
@@ -1706,7 +1706,7 @@ Field | Type | Description
 `to_phone_number` | `null,`&nbsp;`string` | [PII] phone number of the recipient
 `subscription_group_api_id` | `null,`&nbsp;`string` | external ID of the subscription group
 `category` | `null,`&nbsp;`string` | Keyword Category Name, only populated for auto-reply messages: 'Opt-in', 'Opt-out', 'Help', or custom value
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_SMS_SHORTLINKCLICK_SHARED {#USERS_MESSAGES_SMS_SHORTLINKCLICK_SHARED}
 
@@ -1730,7 +1730,7 @@ Field | Type | Description
 `short_url` | `string` | shortened URL that was clicked
 `user_agent` | `null,`&nbsp;`string` | user agent requesting short_url
 `user_phone_number` | `string` | [PII] the user's phone number
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_WEBHOOK_ABORT_SHARED {#USERS_MESSAGES_WEBHOOK_ABORT_SHARED}
 
@@ -1758,7 +1758,7 @@ Field | Type | Description
 `language` | `null,`&nbsp;`string` | [PII] Language of the user
 `abort_type` | `null,`&nbsp;`string` | Type of abort, one of: `liquid_abort_message`, `quiet_hours`, `rate_limit`
 `abort_log` | `null,`&nbsp;`string` | [PII] Log message describing abort details (maximum of 128 characters)
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_WEBHOOK_SEND_SHARED {#USERS_MESSAGES_WEBHOOK_SEND_SHARED}
 
@@ -1784,7 +1784,7 @@ Field | Type | Description
 `country` | `null,`&nbsp;`string` | [PII] Country of the user
 `timezone` | `null,`&nbsp;`string` | Time zone of the user
 `language` | `null,`&nbsp;`string` | [PII] Language of the user
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_WHATSAPP_ABORT_SHARED {#USERS_MESSAGES_WHATSAPP_ABORT_SHARED}
 
@@ -1812,7 +1812,7 @@ Field | Type | Description
 `abort_type` | `null,`&nbsp;`string` | Type of abort, one of: `liquid_abort_message`, `quiet_hours`, `rate_limit`
 `abort_log` | `null,`&nbsp;`string` | [PII] Log message describing abort details (maximum of 128 characters)
 `sf_created_at` | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe      
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_WHATSAPP_DELIVERY_SHARED {#USERS_MESSAGES_WHATSAPP_DELIVERY_SHARED}
 
@@ -1839,7 +1839,7 @@ Field | Type | Description
 `canvas_step_message_variation_api_id` | `null,`&nbsp;`string` | API ID of the Canvas step message variation this user received
 `dispatch_id` | `null,`&nbsp;`string` | ID of the dispatch this message belongs to
 `sf_created_at` | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe      
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_WHATSAPP_FAILURE_SHARED {#USERS_MESSAGES_WHATSAPP_FAILURE_SHARED}
 
@@ -1868,7 +1868,7 @@ Field | Type | Description
 `provider_error_code` | `null,`&nbsp;`string` | Error code from WhatsApp
 `provider_error_title` | `null, `&nbsp;`string` | Error title from WhatsApp
 `sf_created_at` | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe      
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_WHATSAPP_INBOUNDRECEIVE_SHARED {#USERS_MESSAGES_WHATSAPP_INBOUNDRECEIVE_SHARED}
 
@@ -1898,7 +1898,7 @@ Field | Type | Description
 `media_urls` | `null, {"type"=>"array", "items"=>["null", "string"]}` | Media URLs from the user
 `action` | `string` | Action taken in response to this message. For example, `Subscribed`, `Unsubscribed`, or `None`.
 `sf_created_at` | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe      
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_WHATSAPP_READ_SHARED {#USERS_MESSAGES_WHATSAPP_READ_SHARED}
 
@@ -1925,7 +1925,7 @@ Field | Type | Description
 `canvas_step_message_variation_api_id` | `null,`&nbsp;`string` | API ID of the Canvas step message variation this user received
 `dispatch_id` | `null,`&nbsp;`string` | ID of the dispatch this message belongs to
 `sf_created_at` | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe      
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_MESSAGES_WHATSAPP_SEND_SHARED {#USERS_MESSAGES_WHATSAPP_SEND_SHARED}
 
@@ -1953,7 +1953,7 @@ Field | Type | Description
 `dispatch_id` | `null,`&nbsp;`string` | ID of the dispatch this message belongs to
 `message_extras` | `null,`&nbsp;`string` | [PII] A JSON string of the tagged key-value pairs during Liquid rendering
 `sf_created_at` | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe      
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Users
 
@@ -1970,7 +1970,7 @@ Field | Type | Description
 | `random_bucket_number`      | `int`,&nbsp;`null`       | Current random bucket number assigned to the user  |
 | `prev_random_bucket_number` | `int`,&nbsp;`null`       | Previous random bucket number assigned to the user |
 | `sf_created_at`             | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe      |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_USERDELETEREQUEST_SHARED {#USERS_USERDELETEREQUEST_SHARED}
 
@@ -1982,7 +1982,7 @@ Field | Type | Description
 | `app_group_api_id` | `string`,&nbsp;`null`    | API ID of the workspace this user belongs to                  |
 | `time`             | `int`,&nbsp;`null`       | Unix timestamp at which the user delete request was processed |
 | `sf_created_at`    | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                 |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### USERS_USERORPHAN_SHARED {#USERS_USERORPHAN_SHARED}
 
@@ -1998,4 +1998,4 @@ Field | Type | Description
 | `time`             | `int`,&nbsp;`null`       | Unix timestamp at which the user was orphaned                                 |
 | `orphaned_by_id`   | `string`,&nbsp;`null`    | Braze ID of the user whose profile was merged with the orphaned user's profile |
 | `sf_created_at`    | `timestamp`,&nbsp;`null` | When this event was picked up by the Snowpipe                                 |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
diff --git a/_docs/_user_guide/engagement_tools/segments/user_profiles.md b/_docs/_user_guide/engagement_tools/segments/user_profiles.md
index 9d98a79e196..80d7e7496d0 100644
--- a/_docs/_user_guide/engagement_tools/segments/user_profiles.md
+++ b/_docs/_user_guide/engagement_tools/segments/user_profiles.md
@@ -59,7 +59,7 @@ The **Overview** tab contains basic information about a user and their interacti
 | Recent devices | How many devices they logged in on, details on each device, and their associated advertising IDs (if any). |
 | Custom events | Which custom events this user has performed, how many times, and when they last performed each event. |
 | Purchases | Lifetime revenue attributed to this user, their last purchase, total number of purchases, and a list of each purchase. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For more information on this data, see [User Data Collection][12].
 
@@ -79,7 +79,7 @@ The **Engagement** tab contains information about a user's interactions with the
 | Miscellaneous | The user's [random bucket number]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/ab_testing_with_random_buckets/). |
 | Canvas messages received | Canvas messages this user has received and when. Select a message from the list to view it. |
 | Predictions | [Churn prediction]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn) and [event prediction]({{site.baseurl}}/user_guide/predictive_suite/predictive_purchases) scores for this user. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ![][3]
 
@@ -109,7 +109,7 @@ The following message engagement events are available for email, SMS, push, in-a
 | In-app message | Click<br>Impression |
 | Content Cards | Click<br>Dismiss<br>Impression<br>Send |
 | Webhooks | Send |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ##### Message abort events
 
diff --git a/_docs/_user_guide/engagement_tools/segments/user_profiles/duplicate_users.md b/_docs/_user_guide/engagement_tools/segments/user_profiles/duplicate_users.md
index 1a6e7588449..c5533a7d40d 100644
--- a/_docs/_user_guide/engagement_tools/segments/user_profiles/duplicate_users.md
+++ b/_docs/_user_guide/engagement_tools/segments/user_profiles/duplicate_users.md
@@ -70,10 +70,14 @@ In the following example, Braze uses the user's external ID to flag duplicate pr
 | alex@company.com     |   A8i3mkd99          |      (555) 123-4567 | 65fcaa547f470494d1370 | email               | TRUE            | FALSE            |
 | alex@company.com |  |      (555) 987-6543 | 65fcaa547f47d004d1348 | email               | FALSE           | TRUE             |
 | alex@company.com |   |      (555) 321-0987 | 65fcaa547f47d0049135c | email               | FALSE           | TRUE             |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 {% endtab %}
 {% endtabs %}
 
+#### Merge behavior
+
+Braze will fill empty fields on the kept profile with values from the merged profile. For a list of the fields that will be filled, refer to [Merge behavior]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/#merge-behavior).
+
 ### Step 3: Merge your duplicates
 
 If you're satisfied with the results of your preview, select **Merge all duplicates**.
diff --git a/_docs/_user_guide/engagement_tools/templates_and_media/content_blocks.md b/_docs/_user_guide/engagement_tools/templates_and_media/content_blocks.md
index 3171578048b..6ea86affb2d 100644
--- a/_docs/_user_guide/engagement_tools/templates_and_media/content_blocks.md
+++ b/_docs/_user_guide/engagement_tools/templates_and_media/content_blocks.md
@@ -47,7 +47,7 @@ There are two types of editors used to create a Content Block—classic and drag
 | Content Size | Maximum of 50kB (kilobyte). |
 | Placement | Content Blocks cannot be used within an email footer. |
 | Creation | HTML editor or drag-and-drop editor. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 When creating Content Blocks, it sometimes helps to visualize HTML and Liquid by adding line breaks. If these line breaks are left in during sending, you risk having extraneous spaces that can affect how the block will render. To avoid this, use the **Capture** tag on your block along with the **&#124; strip** filter. 
diff --git a/_docs/_user_guide/engagement_tools/testing/global_control_group.md b/_docs/_user_guide/engagement_tools/testing/global_control_group.md
index 787710532a1..4ce3a597cc2 100644
--- a/_docs/_user_guide/engagement_tools/testing/global_control_group.md
+++ b/_docs/_user_guide/engagement_tools/testing/global_control_group.md
@@ -31,6 +31,10 @@ Braze randomly selects multiple ranges of [random bucket numbers]({{site.baseurl
 
 Braze measures the behaviors of users in your control group and users in your treatment sample. Your treatment sample is a random selection of users not in your control group, generated using the same Random Bucket Number method.
 
+### Exclude users from feature flags
+
+You can't enable [feature flags]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/feature_flags/) for users in your Global Control Group. This means users in your Global Control Group also can't be part of feature flag experiments.
+
 ## Create a Global Control Group
 
 ### Step 1: Navigate to the Global Control Group Settings
@@ -98,7 +102,7 @@ As you set up your global control groups and view reporting, here are errors you
 | Global Control Group report does not have any data. | If you access the Global Control Group Report without having saved a Global Control Group, you will not see any data in the report. Create and save a Global Control Group and try again. |
 | My conversion rate is 0% or I'm not seeing the graph display, even though there are more than zero events occurring. | If the number of conversions is very small and your control or treatment groups are very large, then the conversion rate may round to 0%, and thus not show up in the graph. You can verify this by checking the Total Number of Events metric. You could compare the effectiveness of your two groups using the incremental uplift percent metric.  |
 | My conversion rate (or other metrics) are changing drastically depending on the time period I'm viewing data for. | If you're viewing data over short time periods, it's possible for your metrics to fluctuate day to day or week to week. We recommend that you view metrics over the course of at least one month. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Things to watch out for {#things-to-watch-for}
 
diff --git a/_docs/_user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign.md b/_docs/_user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign.md
index 961ac805d6b..5779789a6c4 100644
--- a/_docs/_user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign.md
+++ b/_docs/_user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign.md
@@ -93,7 +93,7 @@ What levers do you have to pull and what are the desired effects? While there ar
 | Push | Copy <br> Image and Emoji Usage <br> Deep Links  <br> Presentation of numbers (for example, "triple" versus "increase by 200%")  <br> Presentation of time (for example, "ends at midnight" versus "ends in 6 hours") | Opens  <br> Conversion Rate |
 | Email | Subject <br> Display Name <br> Salutation <br> Body Copy <br> Image and Emoji Usage <br> Presentation of numbers (for example, "triple" versus "increase by 200%") <br> Presentation of time (for example, "ends at midnight" versus "ends in 6 hours") | Opens  <br> Conversion Rate |
 | In-app message | Aspects listed for "push" <br> [Message format][7] | Click <br> Conversion Rate |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert tip %}
 When running A/B tests, don't forget to generate [funnel reports]({{site.baseurl}}/user_guide/data_and_analytics/reporting/funnel_reports/) that let you understand how each variant impacted your conversion funnel, especially if "conversion" for your business involves taking multiple steps or actions.
diff --git a/_docs/_user_guide/engagement_tools/testing/multivariant_testing/optimizations.md b/_docs/_user_guide/engagement_tools/testing/multivariant_testing/optimizations.md
index c3bcfce2d9e..eef920aba31 100644
--- a/_docs/_user_guide/engagement_tools/testing/multivariant_testing/optimizations.md
+++ b/_docs/_user_guide/engagement_tools/testing/multivariant_testing/optimizations.md
@@ -31,7 +31,7 @@ Sending the Winning Variant is similar to a standard A/B test. Users in this gro
 | Initial test start date | The date and time the initial test starts. |
 | Initial test end date | The date and time the initial test ends. This is when the Winning Variant is sent to the remaining users.<br><br>When sending in users' local time or with Intelligent Timing, the Winning Variant must be sent at least 24 hours after the A/B test to ensure delivery to all users in the Winning Variant group. |
 | Fallback | What happens if no variant wins by a statistically significant margin. Choose between sending the best performing variant anyway, or ending the test and not sending any further messages. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Personalized Variant
 
@@ -48,7 +48,7 @@ To determine the best variant for each user, Braze will send an initial test to
 | Initial test start date | The date and time the initial test starts. |
 | Initial test end date | The date and time the initial test ends. This is when Personalized Variants are sent to the remaining users. We recommend 24 hours as a baseline to ensure statistically significant and meaningful results. The more time you allow for the test, the more responses will be received and the more Braze can optimize. This is especially important for email campaigns. Initial tests for Personalized Variants shouldn't last any less than 4 hours.<br><br>When sending in users' local time or with Intelligent Timing, Personalized Variants must be sent at least 24 hours after the A/B test to ensure delivery to all users in the Personalized Variant group. |
 | Fallback | What happens if no Personalized Variants are found. Choose between sending the Winning Variant instead, or ending the test and not sending any further messages. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Analytics
 
diff --git a/_docs/_user_guide/getting_started/campaigns_canvases.md b/_docs/_user_guide/getting_started/campaigns_canvases.md
index b91fe07cdeb..7f3bb548049 100644
--- a/_docs/_user_guide/getting_started/campaigns_canvases.md
+++ b/_docs/_user_guide/getting_started/campaigns_canvases.md
@@ -24,7 +24,7 @@ While campaigns can be built uniquely depending on the channel, there are four m
 | A/B testing          | For campaigns targeting a single channel, you can send more than one version of the same campaign and see which one comes out on top. You can test copy, personalization, and more for up to eight different versions with a [multivariate campaign]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/). |
 | API                  | [API campaigns]({{site.baseurl}}/api/api_campaigns/) let you send timely messages as quickly as possible. Unlike other campaign types, you don't specify the message, recipients, or schedule in the Braze dashboard. Instead, you pass these identifiers into your API calls. These are typically used for real-time transactional messaging or breaking news.  |
 | Transactional Emails | Braze [Transactional Emails]({{site.baseurl}}/user_guide/message_building_by_channel/email/transactional_message_api_campaign/) are purpose-built for sending automated, non-promotional email messages to facilitate an agreed-upon transaction between you and your customers. They send business-critical notifications to a single user where speed is of the utmost importance. *Available for select packages.* |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 Regular and A/B test campaigns can be scheduled (such as informing a list of users about an upcoming event) or automated to send in response to a user's action (such as sending an email when someone subscribes to your newsletter). Learn more about [scheduling campaigns]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types).
@@ -75,7 +75,7 @@ The following table outlines our supported channels.
 | [Content Cards]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/about/)*       | Provide an inbox within your app or website where users can receive and interact with messages, or display messages in a carousel, as a banner, and more. |
 | [Connected TV]({{site.baseurl}}/developer_guide/platform_wide/tv_and_ott/)                           | Engage with users on connected television platforms.                                                                                                   |
 | [Webhooks]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/understanding_webhooks/) | Enable real-time communication and integration with external systems through custom HTTP callbacks.                                                    |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 <sup>**Available as an add-on feature.*</sup>
 
diff --git a/_docs/_user_guide/getting_started/integration.md b/_docs/_user_guide/getting_started/integration.md
index 25f90591c01..4a61fb0a1a4 100644
--- a/_docs/_user_guide/getting_started/integration.md
+++ b/_docs/_user_guide/getting_started/integration.md
@@ -49,7 +49,7 @@ Be sure to tell your developers which channels you want to use to ensure that im
 | Content Cards | To get started with [Content Cards]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/about/), reach out to your Braze customer success manager. |
 | SMS & MMS | Check out the [SMS Setup]({{site.baseurl}}/user_guide/onboarding_with_braze/sms_setup) section for more details on integration. |
 | Webhooks | Requires SDK implementation as well as channel-specific steps. | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 You can use Braze to create accessible messaging campaigns across each channel. Work with your developers to ensure that you meet accessibility standards in your implementation.
diff --git a/_docs/_user_guide/getting_started/terms_to_know.md b/_docs/_user_guide/getting_started/terms_to_know.md
index e745a456c49..8f8785f7bde 100644
--- a/_docs/_user_guide/getting_started/terms_to_know.md
+++ b/_docs/_user_guide/getting_started/terms_to_know.md
@@ -71,7 +71,7 @@ glossaries:
   - name: Monthly Active User (MAU)
     description: Any user who has a session within the last 30 days.
   - name: Multichannel Messaging
-    description: Messaging a user across various mediums, such as a combination of email, web push, and mobile push notifications. <a href="https://www.braze.com/docs/developer_guide/platform_wide/platform_features/#multi-channel-messaging">Messaging channels</a> are best used in concert and with regularity to re-engage lost users, retain active users, and energize your brand ambassadors.
+    description: Messaging a user across various mediums, such as a combination of email, web push, and mobile push notifications. <a href="https://www.braze.com/docs/developer_guide/platform_wide/getting_started/platform_overview/#multichannel-messaging">Messaging channels</a> are best used in concert and with regularity to re-engage lost users, retain active users, and energize your brand ambassadors.
   - name: Multivariate Testing
     description: <a href="https://www.braze.com/docs/user_guide/engagement_tools/testing/multivariant_testing/#multivariate-and-ab-testing/">Multivariate testing</a> allows you to test multiple variables by comparing two or more versions of a message to assess which variant performs the best.
   - name: New User
diff --git a/_docs/_user_guide/message_building_by_channel/content_cards/create.md b/_docs/_user_guide/message_building_by_channel/content_cards/create.md
index 374c68bd67f..80b837ad3e9 100644
--- a/_docs/_user_guide/message_building_by_channel/content_cards/create.md
+++ b/_docs/_user_guide/message_building_by_channel/content_cards/create.md
@@ -14,33 +14,31 @@ search_rank: 3.9
 
 # Creating a Content Card
 
-> This article covers how to create a Content Card in Braze. Here, we'll cover choosing a messaging type, composing your card, and scheduling your message delivery.
-
-You can create a Content Card using the Braze platform using campaigns and Canvases.
+> This article covers how to create a Content Card in Braze when you build campaigns and Canvases. Here, we'll walk you through choosing a messaging type, composing your card, and scheduling your message delivery.
 
 ## Step 1: Choose where to build your message
 
-Not sure whether your message should be send using a campaign or a Canvas? Campaigns are better for single, simple messaging campaigns, while Canvases are better for multi-step user journeys.
+Not sure whether your message should be sent with a campaign or a Canvas? Campaigns are better for single, simple messaging campaigns (such as informing users about a new product with a single message), while Canvases are better for multi-step user journeys (such as sending tailored product suggestions based on user behavior over time).
 
 {% tabs %}
 {% tab Campaign %}
 
 **Steps:**
 
-1. Go to **Messaging** > **Campaigns** and click <i class="fas fa-plus"></i> **Create Campaign**.
+1. Go to **Messaging** > **Campaigns** and select <i class="fas fa-plus"></i> **Create Campaign**.
 {% alert note %}
-If you are using the [older navigation]({{site.baseurl}}/navigation), you can find **Campaigns** under **Engagement**.
+If you're using the [older navigation]({{site.baseurl}}/navigation), you can find **Campaigns** under **Engagement**.
 {% endalert %}
 
 {:start="2"}
-2. Select **Content Cards**, or, for campaigns targeting multiple channels, select **Multichannel Campaign**.
+2. Select **Content Cards** or, for campaigns targeting multiple channels, select **Multichannel Campaign**.
 3. Name your campaign something clear and meaningful.
 4. Add [Teams]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/teams/) and [Tags]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) as needed.
-   * Tags make your campaigns easier to find and build reports out of. For example, when using the [Report Builder]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/), you can filter by particular tags.
-5. Add and name as many variants as you need for your campaign. You can choose different platforms, message types, and layouts for each of your added variants. For more on this topic, refer to [Multivariate and A/B testing]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/).
+   * Tags make your campaigns easier to find and build reports out of. For example, when using the [Report Builder]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/), you can filter by the relevant tags.
+5. Add and name as many variants as you like for your campaign. You can choose different platforms, message types, and layouts for each of your added variants. For more on variants, refer to [Multivariate and A/B testing]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/).
 
 {% alert tip %}
-If all of the messages in your campaign are going to be similar or have the same content, compose your message before adding additional variants. You can then choose **Copy from Variant** from the **Add Variant** dropdown.
+If all of the messages in your campaign are going to be similar or have the same content, compose your message before adding additional variants. You can then select **Copy from Variant** from the **Add Variant** dropdown.
 {% endalert %}
 
 {% endtab %}
@@ -49,29 +47,29 @@ If all of the messages in your campaign are going to be similar or have the same
 **Steps:**
 
 1. [Create your Canvas]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/) using the Canvas composer.
-2. After you've set up your Canvas, add a Message step in the Canvas builder. Name your step something clear and meaningful.
+2. After setting up your Canvas, add a Message step in the Canvas builder. Name your step something clear and meaningful.
 3. Select **Content Cards** as your messaging channel.
 4. Choose when Braze calculates audience eligibility and personalization for the Content Card. This can be at step entry or at first impression (recommended). Steps containing Content Cards can be scheduled or action-based.
 5. Choose whether to remove Content Cards when users complete a purchase or perform a custom event.
 6. Set an expiration for the Content Card (time in feed). This can be after a duration of time or at a specific time.
-7. Filter your audience for this step as necessary in the **Delivery Settings**. You can further refine the recipients of this step by specifying segments and adding additional filters. Audience options will be checked after the delay, at the time messages are sent.
-8. Choose any other messaging channels that you would like to pair with your message.
+7. Filter your audience, or the receipients, for this step as necessary in the **Delivery Settings**. You can further refine your audience by specifying segments and adding additional filters. Audience options will be checked after the delay, at the time messages are sent.
+8. Choose any other messaging channels that you want to pair with your message.
 
 {% endtab %}
 {% endtabs %}
 
 ## Step 2: Specify your message types
 
-Next, select a **Card Type**. Braze provides three essential Content Card types: Classic, Captioned Image, and Image Only.
+Select one of three essential Content Card types: Classic, Captioned Image, and Image Only. 
 
-To learn more about the expected behavior and look of each of these message types, refer to [Creative Details]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/creative_details/), or check out the links in the following table. These Content Card types are accepted by both mobile apps and web applications.
+To learn more about the expected behavior and look of each type, refer to [Creative Details]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/creative_details/), or check out the links in the following table. These Content Card types are accepted by both mobile apps and web applications.
 
 | Message Type | Example | Description |
 |---|---|---|
 |[Classic]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/creative_details/#classic)| ![Classic Content Card]({% image_buster/assets/img_archive/cc_steppington_classic.png %}) |The Classic Card has a simple layout with a bolded title, message text, and an optional image that sits to the left of the title and text. It's best to use a square image or icon with the Classic Card. |
-|[Captioned Image]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/creative_details/#captioned-image)| ![Captioned Content Card]({% image_buster/assets/img_archive/cc_steppington_captioned.png %}) | The Captioned Image Card allows you to showcase your content with copy and an attention-grabbing image. |
-|[Image Only]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/creative_details/#banner)| ![Image Only Content Card]({% image_buster/assets/img_archive/cc_steppington_banner.png %}) | The Image Only Card allows you to get creative and command attention with space for images, GIFs, and other non-text based content. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+|[Captioned Image]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/creative_details/#captioned-image)| ![Captioned Content Card]({% image_buster/assets/img_archive/cc_steppington_captioned.png %}) | The Captioned Image Card showcases your content with copy and an attention-grabbing image. |
+|[Image Only]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/creative_details/#banner)| ![Image Only Content Card]({% image_buster/assets/img_archive/cc_steppington_banner.png %}) | The Image Only Card commands attention with space for images, GIFs, and other creative non-text content. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Step 3: Compose a Content Card
 
@@ -83,25 +81,27 @@ The content here varies based on the **Card Type** chosen in the previous step,
 
 #### Language
 
-Click **Add Languages** and select your desired languages from the provided list. This will insert [Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/conditional_logic/#conditional-logic) into your message. We recommend selecting your languages before writing your content so you can fill in your text where it belongs in the Liquid. See our [full list of available languages][18].
+Select **Add Languages** to add your desired languages from the provided list. This will insert [Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/conditional_logic/#conditional-logic) into your message. We recommend selecting your languages before writing your content so you can fill in your text where it belongs in the Liquid. See our [full list of available languages][18].
+
+![A window with English, Spanish, and French selected for the languages, and title, description, and link text selected for fields to internationalize.][2]{: style="max-width:70%;"}
 
 #### Title and message
 
-Write anything you want. There are no limits, but the faster you can get your message across and get your customer clicking—the better! We recommend clear and concise titles and message content. These fields are not provided for Image Only Cards.
+Write anything you want. There are no limits, but the faster you can get your message across and get your customer clicking, the better! We recommend clear and concise titles and message content. Note that these fields aren't provided for Image Only Cards.
 
 #### Image
 
-To add an image to your Content Card, click **Add Image** or provide an image URL. Clicking **Add Image** opens the **Media Library**, where you can select a previously uploaded image or add a new one. Each message type and platform may have its own suggested proportions and requirements—be sure to check what those are before commissioning or making an image from scratch! Content Card message fields are limited to 2&nbsp;KB in total size.
+Add an image to your Content Card by selecting **Add Image** or providing an image URL. Selecting **Add Image** opens the **Media Library**, where you can select a previously uploaded image or add a new one. Each message type and platform may have its own suggested proportions and requirements, so be sure to check what those are before commissioning or making an image from scratch! Keep in mind that Content Card message fields are limited to 2&nbsp;KB in total size.
 
 #### Pin to top
 
-A pinned card will display at the top of a user's feed and can't be dismissed by the user. If more than one card in a user's feed is pinned, the pinned cards will display in chronological order. After a card has been sent, you cannot update its pinned option retroactively. Changing this option after a campaign has been sent will only affect future sends.
+A pinned card will display at the top of a user's feed and can't be dismissed by the user. If more than one card in a user's feed is pinned, the pinned cards will display in chronological order. After a card has been sent, you can't retroactively update its pinned option. Changing this option after a campaign has been sent will only affect future sends.
 
 ![Side-by-side of the Content Card preview in Braze for Mobile and Web with the option "Pin this card to the top of the feed" selected.][1]{:style="border:none"}
 
 #### On-click behavior
 
-When your customer clicks on a presented link in the card, your link can either lead them deeper into your app or to another site. If you choose an on-click behavior for your Content Card, remember to update your **Link Text** accordingly!
+When your customer clicks on a presented link in the card, your link can either lead them deeper into your app or to another site. If you choose an on-click behavior for your Content Card, remember to update your **Link Text** accordingly.
 
 The following actions are available to take for Content Card links:
 
@@ -111,19 +111,19 @@ The following actions are available to take for Content Card links:
 | [Deep Link into App]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/deep_linking_to_in-app_content/#deep-linking-to-in-app-content) | Deep link into an existing screen in your app. |
 | Log Custom Event | Choose a [custom event]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/) to trigger. Can be used to display another Content Card or trigger additional messaging. |
 | Log Custom Attribute | Choose a [custom attribute]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/) to set for the current user. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 **Note**: The __Log Custom Event__ and __Log Custom Attribute__ options require the following SDK Version compatibility:
 
 {% sdk_min_versions swift:5.4.0 android:21.0.0 web:4.0.3 %}
 
 {% alert warning %}
-Content Card message fields are limited to 2&nbsp;KB in total size, calculated by adding the byte-size length of the following fields: Title, Message, Image URL, Link Text, Link URL(s), and Key/Value Pairs (names + values). Messages that exceed this size will not be sent. Note that this does not include the size of the image but rather the length of the Image URL.
+Content Card message fields are limited to 2&nbsp;KB in total size, calculated by adding the byte-size length of the following fields: Title, Message, Image URL, Link Text, Link URL(s), and Key-Value Pairs (names + values). Messages that exceed this size will not be sent. Note that this does not include the size of the image but rather the length of the Image URL.
 {% endalert %}
 
 ## Step 4: Configure additional settings (optional)
 
-You can use [key-value pairs][19] to create categories for your Cards, create [multiple Content Card feeds]({{site.baseurl}}/developer_guide/customization_guides/content_cards/customizing_feed/#multiple-feeds) and customize how cards are sorted.
+You can use [key-value pairs][19] to create categories for your Cards, create [multiple Content Card feeds]({{site.baseurl}}/developer_guide/customization_guides/content_cards/customizing_feed/#multiple-feeds), and customize how cards are sorted.
 
 To add key-value pairs to your message, switch to the **Settings** tab and click **Add New Pair**.
 
@@ -132,16 +132,16 @@ To add key-value pairs to your message, switch to the **Settings** tab and click
 {% tabs %}
 {% tab Campaign %}
 
-Build the remainder of your campaign; see the following sections for further details on how to best use our tools to build Content Cards.
+Build the remainder of your campaign. Continue to the next sections for additional details on how to best use our tools to build Content Cards.
 
 #### Choose delivery schedule or trigger
 
-Content Cards can be delivered based on a scheduled time, an action, or based on an API trigger. For more, refer to [Scheduling your campaign]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/).
+Content Cards can be delivered based on a scheduled time, an action, or an API trigger. For more, refer to [Scheduling your campaign]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/).
 
 You can also set the campaign's duration and [Quiet Hours]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign/#quiet-hours) and determine the Content Card's expiration. Set a specific expiration date or the days until a Card expires, up to 30 days. All variants have identical expiration dates.
 
 {% alert note %}
-Frequency Capping does not apply to Content Cards.
+Frequency Capping doesn't apply to Content Cards.
 {% endalert %}
 
 ##### Scheduled delivery
@@ -150,7 +150,7 @@ For Content Card campaigns with scheduled delivery, you can choose when Braze ev
 
 #### Choose users to target
 
-Next, you need to [target users]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/) by choosing segments or filters to narrow down your audience. You'll automatically be given a snapshot of what that approximate segment population looks like right now. Keep in mind that exact segment membership is always calculated just before the message is sent.
+Next, [target users]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/) by choosing segments or filters to narrow down your audience. You'll automatically be given a snapshot of what that approximate segment population looks like right now. Keep in mind that exact segment membership is always calculated just before the message is sent.
 
 #### Choose conversion events
 
@@ -160,14 +160,14 @@ Braze allows you to track how often users perform specific actions, [conversion
 
 {% tab Canvas %}
 
-If you haven't done so already, complete the remaining sections of your Canvas component. For further details on how build out the rest of your Canvas, implement multivariate testing and Intelligent Selection, and more, refer to the [Build your Canvas]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-3-build-your-canvas) step of our Canvas documentation.
+If you haven't done so already, complete the remaining sections of your Canvas component. For further details on how build out the rest of your Canvas, implement [multivariate testing]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/) and [Intelligent Selection]({{site.baseurl}}/user_guide/brazeai/intelligence/intelligent_selection/), and more, refer to the [Build your Canvas]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-3-build-your-canvas) step of our Canvas documentation.
 
 {% endtab %}
 {% endtabs %}
 
 ## Step 6: Review and deploy
 
-After you've finished building the last of your campaign or Canvas, review its details, [test it]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/testing/), then send it!
+After you've finished building the last of your campaign or Canvas, review its details, [test it]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/testing/), then send it when you're ready.
 
 {% alert warning %}
 After a Content Card is launched, it can't be edited. It can only be stopped from sending to new users and removed from users' feeds. Refer to [Updating sent cards]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/#updating-launched-cards) to understand how you can approach this scenario.
@@ -179,14 +179,14 @@ Next, check out [Content Card reporting]({{site.baseurl}}/user_guide/message_bui
 
 ### Sending behavior
 
-Once Content Cards have been sent, similar to emails, they sit waiting in an "inbox" ready to be delivered to the user. After content is pulled into the Content Card (at time of displaying), the content cannot be changed during its lifespan. This applies even if you are calling an API through Connected Content, and the data from the endpoint changes. This data will not get updated. It can only be stopped from sending to new users and removed from users' feeds. If you modify a campaign, only future cards that are sent will have the update.
+After Content Cards have been sent, they sit waiting in an "inbox" ready to be delivered to the user (similar to what happens for emails). After content is pulled into the Content Card (at time of displaying), the content cannot be changed during its lifespan. This applies even if you're calling an API through Connected Content, and the data from the endpoint changes. This data won't get updated. It can only be stopped from sending to new users and removed from users' feeds. If you modify a campaign, only future cards that are sent will have the update.
 
-If you need to remove old cards, you must stop the campaign to do so. To stop a campaign, open your Content Card campaign and select **Stop Campaign**. Stopping the campaign will prompt you to decide how to handle users that have already received your card. If you would like to remove the Content Card from your users' feeds, select **Remove card from feed**. The card will then be hidden by the SDK on the next sync.
+If you need to remove old cards, you must first stop the campaign. To stop a campaign, open your Content Card campaign and select **Stop Campaign**. Stopping the campaign will prompt you to decide how to handle users that have already received your card. If you want to remove the Content Card from your users' feeds, select **Remove card from feed**. The card will then be hidden by the SDK on the next sync.
 
 ![Dialog for confirming Content Card deactivation][25]{: style="max-width:75%" }
 
 {% alert tip %}
-Do you want to have Content Cards that seem to last longer than the 30-day max? One way to accomplish this is to:
+Do you want your Content Cards to seem like they're lasting longer than the 30-day max? One way to accomplish this is to:
 
 1. Set the duration of the Content Card for 30 days.
 2. Set the campaign re-eligibility to 30 days.
@@ -199,7 +199,7 @@ Voila!
 
 Some Content Cards are only relevant up until a user performs some action. For example, a card nudging users to activate their account shouldn't be shown after the user completes that onboarding task.
 
-Within a campaign or Canvas Message, you can optionally add a **Removal Event** to specify which custom events or purchases should cause previously sent cards to be removed from that user's feed; triggered via SDK or REST API.
+Within a campaign or Canvas message, you can optionally add a **Removal Event** to specify which custom events or purchases should cause previously sent cards to be removed from that user's feed—triggered by the SDK or REST API.
 
 {% alert tip %}
 You can specify multiple custom events and purchases that should remove a card from a user's feed. When **any** of those actions are performed by the user, any existing cards sent by the campaign's cards will be removed. Any future eligible cards will continue to be sent according to the message's schedule.
@@ -209,7 +209,7 @@ You can specify multiple custom events and purchases that should remove a card f
 
 ### Updating launched cards
 
-Content Cards cannot be edited after they are sent. If you find you need to make changes to cards that have already been sent, consider using [Campaign Re-eligibility]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/) as shown in the following options.
+Content Cards can't be edited after they are sent. If you find you need to make changes to cards that have already been sent, consider using [campaign re-eligibility]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/) as shown in the following options.
 
 {% alert note %}
 Content Cards using [at first impression]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/#differences-between-creating-cards-at-launch-or-entry-versus-at-first-impression) use impression time to calculate re-eligibility&#8212;however, all other Content Card types use whichever send time or impression time is latest.
@@ -219,10 +219,12 @@ Content Cards using [at first impression]({{site.baseurl}}/user_guide/message_bu
 
 One approach is to archive the campaign and remove active cards from the feed. Then you can duplicate the campaign and launch it with updates so that any eligible users would received the updated cards.
 
-* If users should never be re-eligible for a Content Card, you can filter for users who have not received the previous version of the Content Card by setting the filter `Received Message from Campaign` to the condition to `Has Not`.
+* If users should never be re-eligible for a Content Card, you can filter for users who haven't received the previous version of the Content Card by setting the filter `Received Message from Campaign` to the condition to `Has Not`.
 * If users who received the prior card should be re-eligible in X days, you can set the filter for `Last Received Message from specific campaign` to more than X days ago **OR** `Received Message from Campaign` with the `Has Not` condition.
 
-**Example:** A campaign is triggered off of session start with re-eligibility set to 30 days. A user received the campaign two days ago and you want to change the copy. First archive the campaign and remove the cards from feed. Then duplicate the campaign and re-launch with the new copy. If the user has a session again, they will receive the new card immediately.
+##### Use case
+
+Let's say you've set a campaign to be triggered by a session start and it has re-eligibility set to 30 days. A user received the campaign two days ago, and you want to change the copy. First, you'd archive the campaign and remove the cards from feed. Second, you'd duplicate the campaign and re-launch with the new copy. If the user has another session, they'll immediately receive the new card.
 
 ##### Impact
 
@@ -230,7 +232,7 @@ One approach is to archive the campaign and remove active cards from the feed. T
 * **Existing Recipients:** New and existing recipients would see the updated card at the next feed refresh if they are eligible.
 
 {% alert tip %}
-This option is recommended for messages where you are showing latest content in the card (for example, home page banners), changes must be shown immediately, or when re-eligibility is off.
+We recommend this option for messages where you are showing the latest content in the card (such as home page banners), changes must be shown immediately, or when re-eligibility is turned off.
 {% endalert %}
 
 #### Option 2: Stop and relaunch
@@ -244,23 +246,26 @@ If a card has re-eligibility turned on, you could chose to:
 
 With this approach, newly eligible users will get the new card and previous recipients would get the new card when they're re-eligible.
 
-**Example:** A campaign is triggered off of session start with re-eligibility set to 30 days. A user received the campaign two days ago, and you want to change the copy. First, stop the campaign and remove the card from the feed. Then re-publish the campaign with the new copy. If the user has a session again, they will receive the new card in 28 days.
+##### Use case
+
+Let's say you have a campaign that's triggered by a session start and has re-eligibility set to 30 days. A user received the campaign two days ago, and you want to change the copy. First, stop the campaign and remove the card from the feed. Second, re-publish the campaign with the new copy. If the user has another session, they'll receive the new card in 28 days.
 
 ##### Impact
 
-* **Reporting:** One campaign will contain all reporting analytics for the card versions launched. Braze will not differentiate between versions launched.
+* **Reporting:** One campaign will contain all reporting analytics for the card versions launched. Braze won't differentiate between the versions launched.
 * **Existing recipients:** Users who have already received the card would not receive the updated cards until they become re-eligible. If re-eligibility is turned off, they would never receive the new card.
 
 {% alert tip %}
-This option is recommended for unique messages in a notification center or message inbox (for example, promotions), when it’s important for analytics to be unified, or when timeliness of the message is not a concern (such as existing recipients can wait for the eligibility window before seeing the updated cards).
+We recommend using this option for unique messages in a notification center or message inbox (such as promotions), when it’s important for analytics to be unified, or when timeliness of the message isn't a concern (such as existing recipients can wait for the eligibility window before seeing the updated cards).
 {% endalert %}
 
 #### Keeping cards in users' feeds
 
-If desired, you could keep an active Content Card campaign in users' feeds and not remove them. When edits are made to the live campaign, it means the previous unedited version of the campaign card would still be live, and only users that meet the criteria after the edits will see the new version. However, users already exposed to the campaign may see two versions of the card.
+If desired, you could keep an active Content Card campaign in users' feeds and not remove them. When the live campaign is edited, the previous unedited version of the campaign card will still be live, and only users that meet the criteria after the edits will see the new version. However, users already exposed to the campaign may see two versions of the card.
 
 [18]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/advanced_use_cases/localization/#languages-supported
 [19]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/key_value_pairs/
 [24]: {% image_buster /assets/img/content_card_compose.png %}
 [25]: {% image_buster /assets/img/cc_remove.png %}
 [1]: {% image_buster /assets/img/cc_pin_to_top.png %}
+[2]: {% image_buster /assets/img/add_languages.png %}
diff --git a/_docs/_user_guide/message_building_by_channel/content_cards/creative_details.md b/_docs/_user_guide/message_building_by_channel/content_cards/creative_details.md
index 9a84a97d640..f0dd2ba93af 100644
--- a/_docs/_user_guide/message_building_by_channel/content_cards/creative_details.md
+++ b/_docs/_user_guide/message_building_by_channel/content_cards/creative_details.md
@@ -28,7 +28,7 @@ The classic card is great for standard messaging and notifications or even visua
 | Message Text | 13px; Regular Weight <br> Two to four lines of text is ideal. <br> You may use Liquid here to personalize your message. |
 | Link Text | Optional. <br> 13&nbsp;px <br> Link to web page or deep link to within  your app. |
 | Image | Optional. <br> Must be 1:1 ratio. <br> We recommend an image quality of 60 x 60&nbsp;px. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Captioned Image %}
@@ -43,7 +43,7 @@ The Captioned Image card is a great way to show off and attract attention to imp
 | Message Text | 13px; Regular Weight <br> Two to four lines of text is ideal. <br> You may use Liquid here to personalize your message. |
 | Link Text | Optional. <br> 13&nbsp;px <br> Link to web page or deep link to within your app. |
 | Image | Suggested be 4:3 ratio. <br> 600&nbsp;px minimum width.  <br> Supports high-resolution PNG, JPEG, and GIF. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Banner %}
@@ -56,7 +56,7 @@ If you want fancy, the banner card is for you. This is completely customized to
 | --- | ---|
 | Linked Card | Optional. <br> 13&nbsp;px <br> On-click behavior link to a web page or a deep link to within your app. |
 | Image | Any aspect ratio supported. <br> 600&nbsp;px minimum width.  <br> Supports high-resolution PNG, JPEG, and GIF. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
@@ -84,7 +84,7 @@ Keep Content Cards relevant by setting them to dismiss when a user takes relevan
 | Content Cards for Android | Content Cards for iOS | Content Cards for Web |
 | --- | --- |---|
 | The Android SDK does not provide animated GIF support by default. For more details on activating GIF support, refer to [GIFs]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/GIFs/). | The Swift SDK does not provide animated GIF support by default. For more details on activating GIF support, refer to the [GIF support tutorial](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/c3-gif-support). | GIF support is included by default in the Web SDK integration. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 <br><br>
 
@@ -94,4 +94,4 @@ Keep Content Cards relevant by setting them to dismiss when a user takes relevan
 [4]: {{site.baseurl}}/developer_guide/customization_guides/content_cards
 [5]: {% image_buster /assets/img/dismissal-cc.png %}
 [6]: {% image_buster /assets/img/empty-cc.png %}
-[7]: {{site.baseurl}}/developer_guide/customization_guides/customization_overview
+[7]: {{site.baseurl}}/developer_guide/customization_guides/customization_overview
\ No newline at end of file
diff --git a/_docs/_user_guide/message_building_by_channel/content_cards/migrating_from_news_feed.md b/_docs/_user_guide/message_building_by_channel/content_cards/migrating_from_news_feed.md
index b947deab6de..d125d82cf10 100644
--- a/_docs/_user_guide/message_building_by_channel/content_cards/migrating_from_news_feed.md
+++ b/_docs/_user_guide/message_building_by_channel/content_cards/migrating_from_news_feed.md
@@ -41,7 +41,7 @@ The following table further outlines the difference in supported features betwee
 | [Available in Canvas][2] | <i class="fas fa-times" title="Not supported"></i> | <i class="fas fa-check" title="Supported"></i> |
 | [Connected Content][5] | <i class="fas fa-times" title="Not supported"></i> | <i class="fas fa-check" title="Supported"></i> |
 | Personalization and segmentation | Templated at impression | Templated at send or first impression |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Implementation
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/about.md b/_docs/_user_guide/message_building_by_channel/email/about.md
index 0a76d39ad33..7a9e67ba090 100644
--- a/_docs/_user_guide/message_building_by_channel/email/about.md
+++ b/_docs/_user_guide/message_building_by_channel/email/about.md
@@ -33,7 +33,7 @@ Here are some great use cases to get you inspired!
 | Multimedia content | Ease of multimedia content placement that engages users such as videos and images. |
 | Newsletters | Conveniently send monthly or weekly newsletters to maintain user engagement. |
 | Transactions | Notify users of recent purchases and deliver important product and shipping information with [transactional emails][3].
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 [1]: {{site.baseurl}}/user_guide/message_building_by_channel/email/html_editor/creating_an_email_campaign/
diff --git a/_docs/_user_guide/message_building_by_channel/email/amphtml.md b/_docs/_user_guide/message_building_by_channel/email/amphtml.md
index 8677b985d0f..79ca135ed75 100644
--- a/_docs/_user_guide/message_building_by_channel/email/amphtml.md
+++ b/_docs/_user_guide/message_building_by_channel/email/amphtml.md
@@ -23,7 +23,7 @@ Braze is not responsible for users registering with Google or meeting the necess
 | Gmail account enablement | See [Enabling Gmail account](#enabling-gmail-account). |
 | Google sender authentication | Gmail [authenticates the sender](https://developers.google.com/gmail/ampemail/security-requirements#sender_authentication) of AMP emails with DKIM, SPF, and DMARC. These must be set up for your account. <br><br>- [Domain Keys Identified Mail](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) (DKIM) <br>- [Sender Policy Framework](https://en.wikipedia.org/wiki/Sender_Policy_Framework)(SPF)<br>- [Domain-based Message Authentication, Reporting, and Conformance](https://en.wikipedia.org/wiki/DMARC)(DMARC)
 | AMP email elements | A compelling AMP email includes the strategic use of various components. Refer to the Essentials tab in the [Components](#components) section below. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Supported clients
 
@@ -97,7 +97,7 @@ These are what make an AMP HTML email...AMP'ed! Each of these elements is requir
 | Identification <br><br> `⚡4email` or `amp4email`| Identifies your email as an AMP HTML email. | `<!doctype html>` <br> `<html ⚡4email>` <br> `<head>` |
 | Load AMP runtime <br><br> `<script>` | Allows AMP to run in your email using JavaScript. | `<script async src="https://cdn.ampproject.org/v0.js"></script>`|
 | CSS Boilerplate | Hides content until AMP is loaded. <br> Email providers who support AMP emails enforce security checks that only allow vetted AMP scripts to run in their clients. | `<style amp4email-boilerplate>body{visibility:hidden}</style>` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
   {% endtab %}
   {% tab Dynamic %}
@@ -108,7 +108,7 @@ Use these components to create dynamic layouts and behaviors in your emails.
 |---------|--------------|---------|
 | [Accordion](https://amp.dev/documentation/components/amp-accordion?format=email) <br><br> `amp-accordion`| Allows users to view the content outline and jump to any section. | `<script async custom-element="amp-accordion" src="https://cdn.ampproject.org/v0/amp-accordion-0.1.js"></script>` |
 | [Forms](https://amp.dev/documentation/components/amp-form?format=email) <br><br> `amp-form`| Create forms to submit input fields in an AMP document. | `<script async custom-element="amp-form" src="https://cdn.ampproject.org/v0/amp-form-0.1.js"></script>` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert note %}
 Any component that requires authenticating the user must use [Google access tokens](https://developers.google.com/gmail/ampemail/authenticating-requests#access_tokens) or [proxy assertion tokens](https://developers.google.com/gmail/ampemail/authenticating-requests#proxy_assertion_tokens).
@@ -123,7 +123,7 @@ Any component that requires authenticating the user must use [Google access toke
 | [Animated Image](https://amp.dev/documentation/components/amp-anim?format=email) <br><br> `amp-anim`| Displays an animated image (usually a GIF) managed via runtime. | `<script async custom-element="amp-anim" src="https://cdn.ampproject.org/v0/amp-anim-0.1.js"></script>` |
 | [Carousel](https://amp.dev/documentation/components/amp-carousel?format=email) <br><br> `amp-carousel`| Displays multiple similar pieces of content along a horizontal axis. | `<script async custom-element="amp-carousel" src="https://cdn.ampproject.org/v0/amp-carousel-0.1.js"></script>` |
 | [Image](https://amp.dev/documentation/components/amp-img?format=email) | A runtime-managed replacement for the HTML `img` tag. <br>  You can also create a [lightbox for your image](https://amp.dev/documentation/components/amp-image-lightbox?format=email). | `<amp-img alt="A view of the sea"` <br> `src="images/sea.jpg"` <br> `width="900"` <br>  `height="675"` <br>  `layout="responsive">`  <br> `</amp-img>` |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert note %}
 Any component that requires authenticating the user must use [Google access tokens](https://developers.google.com/gmail/ampemail/authenticating-requests#access_tokens) or [proxy assertion tokens](https://developers.google.com/gmail/ampemail/authenticating-requests#proxy_assertion_tokens).
@@ -135,7 +135,7 @@ Any component that requires authenticating the user must use [Google access toke
 | Component | Description |
 |---------|--------------|
 | [Data Binding & Expressions](https://amp.dev/documentation/components/amp-anim?format=email) <br><br> `amp-bind`| Adds custom stateful interactivity to your AMP pages via data binding and JavaScript-like expressions. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 Any component that requires authenticating the user must use [Google access tokens](https://developers.google.com/gmail/ampemail/authenticating-requests#access_tokens) or [proxy assertion tokens](https://developers.google.com/gmail/ampemail/authenticating-requests#proxy_assertion_tokens).
@@ -195,13 +195,38 @@ By wrapping your content around the `raw` tag, the Braze processing engine will
 
 ## Metrics and analytics
 
-| Metric | Details |
-|---|---|
-| Total Opens | Total opens for the HTML and plaintext versions of your AMP email. |
-| Total Clicks | Total clicks in the HTML and plaintext versions of your AMP email. |
-| AMP Opens | Total count for opens in your AMP HTML email and AMP HTML versions of the email. |
-| AMP Clicks | Total count for clicks in your AMP HTML email, cumulative count of the HTML, plaintext, and AMP HTML versions of the email. |
-{: .reset-td-br-1 .reset-td-br-2}  
+<style>
+    .no-split {
+        word-break: keep-all;
+    }
+</style>
+
+<table>
+    <thead>
+        <tr>
+            <th>Metric</th>
+            <th>Details</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td class="no-split">Total Opens</td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Total Opens' %} For AMP emails, this is the total opens for the HTML and plaintext versions.</td>
+        </tr>
+        <tr>
+            <td class="no-split">Total Clicks</td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Total Clicks' %} For AMP emails, this is the total clicks in the HTML and plaintext versions.</td>
+        </tr>
+        <tr>
+            <td class="no-split">AMP Opens</td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='AMP Opens' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split">AMP Clicks</td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='AMP Clicks' %}</td>
+        </tr>
+    </tbody>
+</table>
 
 ## Testing and troubleshooting
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/apple_mail/email_private_relay_apple_SSO.md b/_docs/_user_guide/message_building_by_channel/email/apple_mail/email_private_relay_apple_SSO.md
index 9e1a42d3bed..3895bed9dd0 100644
--- a/_docs/_user_guide/message_building_by_channel/email/apple_mail/email_private_relay_apple_SSO.md
+++ b/_docs/_user_guide/message_building_by_channel/email/apple_mail/email_private_relay_apple_SSO.md
@@ -35,7 +35,7 @@ Refer to this table for the components used when adding email addresses with App
 |---|---|
 | UID | This value is provided in your DNS records that are provided by Braze (from SendGrid). Do not include the letter "u" in your UID in the email address. For example, if your UID is presented in SendGrid as `u1234567.wl134.sendgrid.net`, then `1234567` is the UID value. <br><br> If you don't have access to your DNS records, contact your Braze customer success manager to provide your UID. |
 | Whitelabeled Subdomain and Domain | The initial domain and subdomain you entered into SendGrid. You can also use the **HOST Value** in your DNS records in SendGrid. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Sending emails for SparkPost
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/best_practices/email_styling.md b/_docs/_user_guide/message_building_by_channel/email/best_practices/email_styling.md
index c42997f5627..ccbcfc7bd30 100644
--- a/_docs/_user_guide/message_building_by_channel/email/best_practices/email_styling.md
+++ b/_docs/_user_guide/message_building_by_channel/email/best_practices/email_styling.md
@@ -57,7 +57,7 @@ Here are some best practices to keep in mind when writing your preheaders:
   | Android Gmail          | 24      |
   | iOS Native             | 82      |
   | iOS Gmail              | 30      |
-  {: .reset-td-br-1 .reset-td-br-2}
+  {: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
   |  Desktop Email Client  |  Limit  |
   |:----------------------:|:-------:|
@@ -65,7 +65,7 @@ Here are some best practices to keep in mind when writing your preheaders:
   | Outlook '13            | 38      |
   | Outlook for Mac '15   | 53      |
   | Outlook '16            | 50      |
-  {: .reset-td-br-1 .reset-td-br-2}
+  {: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
   |  Webmail Email Client  |  Limit  |
@@ -75,7 +75,7 @@ Here are some best practices to keep in mind when writing your preheaders:
   | Outlook.com            | 49      |
   | Office 365             | 40      |
   | Mail.ru                | 64      |
-  {: .reset-td-br-1 .reset-td-br-2}
+  {: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Email size
 
@@ -84,7 +84,7 @@ Make sure to limit your email size. Email bodies larger than 102&nbsp;KB are not
 |   Text Only   | Text With Images |     Email Width    |
 |:-------------:|:----------------:|:------------------:|
 | 25&nbsp;KB maximum |   60&nbsp;KB maximum   | 600 pixels maximum |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Text length
 
@@ -95,7 +95,7 @@ Refer to the following table for recommended text lengths.
 | Subject Line Length | 35 characters maximum (for optimal mobile display) (6 to 10 words) |
 | Sender Name Length | 25 characters maximum (for optimal mobile display) |
 | Preheader Length | 85 characters maximum |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Image size
 
@@ -104,7 +104,7 @@ Refer to the following table for recommended image sizes. Smaller, high-quality
 |     Size    | Header Image Width |  Body Image Width  |   File Types  |
 |:-----------:|:------------------:|:------------------:|:-------------:|
 | 5&nbsp;MB maximum | 600 pixels maximum | 480 pixels maximum | PNG, JPEG, GIF |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 ## Deep linking
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/custom_email_footer.md b/_docs/_user_guide/message_building_by_channel/email/custom_email_footer.md
index 0c62a37c9fd..8c3ae4bf670 100644
--- a/_docs/_user_guide/message_building_by_channel/email/custom_email_footer.md
+++ b/_docs/_user_guide/message_building_by_channel/email/custom_email_footer.md
@@ -63,7 +63,7 @@ When creating a custom footer, Braze suggests using [attributes for personalizat
 | User's Custom Opt-In URL | {% raw %}`{{${set_user_to_opted_in_url}}}`{% endraw %} |
 | User's Custom Subscribe URL | {% raw %}`{{${set_user_to_subscribed_url}}}`{% endraw %}|
 | User's Custom Braze Preference Center URL | {% raw %}`{{${preference_center_url}}}`{% endraw %} |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Including an unsubscribe link and opt-in link
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks.md b/_docs/_user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks.md
index 287a31f5c10..c9d1bf1e5b4 100644
--- a/_docs/_user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks.md
+++ b/_docs/_user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks.md
@@ -39,7 +39,7 @@ The following table describes how users can use each editor block type.
 |`Icons`| Inserts an icon. Custom images can be uploaded. An oversized placeholder icon will be used until an image is uploaded. |
 |`HTML`| Inserts raw HTML. Great for advanced Liquid such as Connected Content or conditional statements. | 
 |`Menu`| Creates a flexible menu for the message you're designing. |
-{: .reset-td-br-1 .reset-td-br-2} 
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" } 
 
 ## Properties
 
@@ -59,7 +59,7 @@ Details for each editor block's properties are provided in the following tables.
 |`Line height`| Modifies the distance between lines of text. |
 |`Line spacing`| Modifies the distance in between each character. |
 |`Text direction`| Default left-to-right, but can be edited to be right-to-left. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Paragraph
 
@@ -77,7 +77,7 @@ Refer to the following table for details on the `Paragraph` editor block propert
 |`Line height`| Modifies the distance between lines of text. |
 |`Letter spacing`| Modifies the distance in between each character. |
 |`Text direction`| Default left-to-right, but can be edited to be right-to-left. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### List
 
@@ -99,7 +99,7 @@ Refer to the following table for details on the `List` editor block properties.
 |`Line height`| Modifies the distance between lines of text. |
 |`Letter spacing`| Modifies the distance in between each character. |
 |`Text direction`| Default left-to-right, but can be edited to be right-to-left. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Button
 
@@ -109,7 +109,7 @@ Refer to the following table for details on the `Button` editor block.
 |---|---|
 |`Link Type`| Determines the action when clicking the button and sets the appropriate link protocol. |
 |`URL`| Dynamic based on the selected `Link Type`.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Divider
 
@@ -121,7 +121,7 @@ Refer to the following table for details on the `Divider` editor block.
 |`Line`| The different line formats, whether dotted, spotted, or solid.  In addition, you can modify the thickness and color of the divider line. |
 |`Width `| Adjusts the spread of the divider in increments of 5.  |
 |`Align`| Moves the line to be either left, center, or right-oriented. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Spacer
 
@@ -130,7 +130,7 @@ Refer to the following table for details on the `Spacer` editor block.
 | properties | description |
 |---|---|
 |`Height`| Adjusts the height of the spacer block. The default is 60px.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Image
 
@@ -142,7 +142,7 @@ Refer to the following table for details on the `Image` editor block. For dynami
 |`Align`| Moves the image to be either left, center or right-oriented. |
 |`URL`| The hosted address for your image. |
 |`Alternate text`| The written copy that appears in place of an image when the image fails to load. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 For `Auto Width`, automatic image resizing picks the best size for the image based on a combination of image width and available space in the layout:
@@ -161,7 +161,7 @@ Refer to the following table for details on the `Video` editor block.
 |`Play Icon Style`| Includes different options for the play button located at the top of a video image. |
 |`Play Icon Color`| Option to select either **Light** or **Dark** for the play button. |
 |`Play Icon Size`| Choose the pixel size for the play button. Pre-fixed range from 50&nbsp;px to 80&nbsp;px (incremented by 5&nbsp;px). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 Videos hosted by Vimeo will only work if they are set to public. All other security settings available within Vimeo (for example, "Hide from Vimeo.com") will generate a different link format that is not supported by this Content Block. These types of links are altered by the builder, which prevents Braze from generating a thumbnail.
@@ -177,7 +177,7 @@ Refer to the following table for details on the `Social` editor block.
 |`Configure icon collection`| Sets the URL for each social icon. Includes the **More options** toggle to edit the title and alternative text. |
 |`Align`| Moves the social icon to be left, center or right-oriented.
 |`Icon spacing`| Determines the spacing between each social icon. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Icons
 
@@ -195,7 +195,7 @@ Refer to the following table for details on the `Icons` editor block.
 |`Icon size`| Determines the size of your icon. |
 |`Icon spacing`| Modifies the space of the icon. |
 |`Icon padding`| Modifies the padding of the icon. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### HTML
 
@@ -204,7 +204,7 @@ Refer to the following table for details on the `HTML` editor block.
 | properties | description |
 |---|---|
 |`html editor`| Enter the raw HTML. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Menu
 
@@ -224,7 +224,7 @@ Refer to the following table for details on the `Menu` editor block.
 |`Mobile menu`| Includes options to modify the icon size, color, and icon type when shown on a mobile device. |
 |`Item padding`| Modifies the padding by using either the **+** or **-** button, or by entering a specific number. |
 |`All sides`| Sets a consistent padding number if `Item padding` is disabled. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Add Liquid personalization
 
@@ -233,4 +233,4 @@ Refer to the following table for details on `Add Personalization`.
 | name | description |
 |---|---|
 | `Add Personalization` | Allows you to lookup standard Liquid snippets such as standard (default) attributes, custom attributes, Content Blocks, and more. | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
diff --git a/_docs/_user_guide/message_building_by_channel/email/email_setup.md b/_docs/_user_guide/message_building_by_channel/email/email_setup.md
index f7196fdbdad..457657e8b42 100644
--- a/_docs/_user_guide/message_building_by_channel/email/email_setup.md
+++ b/_docs/_user_guide/message_building_by_channel/email/email_setup.md
@@ -47,7 +47,7 @@ Before you start sending emails, there are some things you need. Refer to the fo
 | Whitelabeled Domains | These consist of a domain and a subdomain. By using whitelabeling, you can pass email authentication checks for DKIM and SPF. | The Braze Onboarding team will generate these domains for you, but you must choose their names. |
 | Subdomains | This is a subdivision of a domain (such as "@news.company.com") within your email address. Having a subdomain will prevent any errors that could damage your company's official email reputation. | The Onboarding team will generate this for you, but you must decide the name of the subdomain. You cannot use subdomains that are currently being used outside of Braze. |
 | IP Pools | These are an optional configuration used to separate out the reputation of different types of email (such as "promotional" and "transactional") to prevent the reputation of one from impacting the other and support higher deliverability. | The Onboarding team will set up the pools for you. Then, when composing your email, select your email's IP pool from the **IP Pool** dropdown on the **Target Users** page.|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## IP warming
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/email_setup/authentication.md b/_docs/_user_guide/message_building_by_channel/email/email_setup/authentication.md
index e48796a267e..acef4a95e09 100644
--- a/_docs/_user_guide/message_building_by_channel/email/email_setup/authentication.md
+++ b/_docs/_user_guide/message_building_by_channel/email/email_setup/authentication.md
@@ -47,7 +47,7 @@ The policy you have in your DMARC record will tell the participating recipient e
 | None | Tell the mailbox provider to perform no actions against messages that fail. |
 | Quarantine | Tell the mailbox provider to send messages that fail to the spam folder. |
 | Reject | Tell the mailbox provider that messages that fail will go to the spam folder and should be blocked. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 #### How to check your domain's DMARC authentication
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/email_setup/consent_and_address_collection.md b/_docs/_user_guide/message_building_by_channel/email/email_setup/consent_and_address_collection.md
index a3810715bbb..8e23782df47 100644
--- a/_docs/_user_guide/message_building_by_channel/email/email_setup/consent_and_address_collection.md
+++ b/_docs/_user_guide/message_building_by_channel/email/email_setup/consent_and_address_collection.md
@@ -21,7 +21,7 @@ There are three email subscription states for a user: **opted in**, **subscribed
 | Opted In | These customers have clicked on the link in a confirmation email and actively opted in to receiving your messages. |
 | Subscribed | By default, users are subscribed to email as long as they have a valid email address stored on their profile. users remain subscribed until they unsubscribe or opt-in. |
 | Unsubscribed | To be marked as unsubscribed, a customer has either explicitly unsubscribed from your emails or has marked an email as spam. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Address collection methods
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/email_setup/deliverability_pitfalls_and_spam_traps.md b/_docs/_user_guide/message_building_by_channel/email/email_setup/deliverability_pitfalls_and_spam_traps.md
index 1fa1add70ac..c55b78f58e4 100644
--- a/_docs/_user_guide/message_building_by_channel/email/email_setup/deliverability_pitfalls_and_spam_traps.md
+++ b/_docs/_user_guide/message_building_by_channel/email/email_setup/deliverability_pitfalls_and_spam_traps.md
@@ -19,7 +19,7 @@ Your email deliverability can be affected by any of the following spam traps:
 | Typo Traps | Email addresses containing common typos. |
 | Spam Complaints | When your email is marked as spam by a customer. |
 | High Bounce Rate | When your email consistently fails to deliver because the recipient's address is invalid. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## How to avoid spam traps
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/html_editor/gmail_promotions_tab.md b/_docs/_user_guide/message_building_by_channel/email/html_editor/gmail_promotions_tab.md
index dceff0cdcd2..769e6aa4631 100644
--- a/_docs/_user_guide/message_building_by_channel/email/html_editor/gmail_promotions_tab.md
+++ b/_docs/_user_guide/message_building_by_channel/email/html_editor/gmail_promotions_tab.md
@@ -50,7 +50,7 @@ Promotion cards in your product carousel are helpful to provide images to your o
 | Currency | (optional) The currency of the price. |
 | Price | The price of the promotion. |
 | Discount Value | The amount discounted from the original price. | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 We recommend uploading your product images to the media library, then copy and pasting the URLs into the appropriate fields. Only static image formats (PNG and JPEG), are accepted. Some image formats (GIF) will upload but not display as expected.
diff --git a/_docs/_user_guide/message_building_by_channel/email/managing_user_subscriptions.md b/_docs/_user_guide/message_building_by_channel/email/managing_user_subscriptions.md
index e6f42c03294..1fc5bbc8786 100644
--- a/_docs/_user_guide/message_building_by_channel/email/managing_user_subscriptions.md
+++ b/_docs/_user_guide/message_building_by_channel/email/managing_user_subscriptions.md
@@ -23,7 +23,7 @@ Braze has three global subscription states for email users (listed in the follow
 | Opted-in | A user has explicitly confirmed they want to receive email. We recommend an explicit opt-in process to get consent from users to send emails. |
 | Subscribed | A user has neither unsubscribed nor explicitly opted-in to receive emails. This is the default subscription state when a user profile is created. |
 | Unsubscribed | A user has explicitly unsubscribed from your emails. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 Braze does not count subscription state changes against your data points, globally, and around subscription groups.
@@ -41,7 +41,9 @@ Refer to our [IP warming]({{site.baseurl}}/user_guide/onboarding_with_braze/emai
 
 ### Bounces and invalid emails
 
-Hard bounces can happen if the email is invalid or doesn't exist. In this case, Braze will mark the user's email address as invalid and will not attempt to send any further emails to that email address. If that user changes their email address, then we will resume sending emails to them since their new email may be valid. Soft bounces are automatically retried for 72 hours.
+{% multi_lang_include metrics.md metric='Hard Bounce' %} {% multi_lang_include metrics.md metric='Soft Bounce' %} 
+
+If that user changes their email address, then we will resume sending emails to them since their new email may be valid. Soft bounces are automatically retried for 72 hours.
 
 ### Updating email subscription states
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/preference_center/overview.md b/_docs/_user_guide/message_building_by_channel/email/preference_center/overview.md
index 0dad5255875..d1c3b3c7e1c 100644
--- a/_docs/_user_guide/message_building_by_channel/email/preference_center/overview.md
+++ b/_docs/_user_guide/message_building_by_channel/email/preference_center/overview.md
@@ -9,12 +9,12 @@ channel:
 
 # Preference center overview
 
-> Setting up a preference center provides a one-stop shop for your users to edit and manage their notification preferences for your [email messaging]({{site.baseurl}}/user_guide/message_building_by_channel/email/).<br><br>The following article provides instructions on how to build an API-generated preference center, but you can also build a preference center using the [drag-and-drop editor]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center/dnd_preference_center/).
+> Setting up a preference center provides a one-stop shop for your users to edit and manage their notification preferences for your [email messaging]({{site.baseurl}}/user_guide/message_building_by_channel/email/). This article includes steps for building an API-generated preference center, but you can also build a preference center using the [drag-and-drop editor]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center/dnd_preference_center/).
 
 In the Braze dashboard, go to **Audience** > **Subscriptions** > **Email Preference Center**.
 
 {% alert note %}
-If you are using the [older navigation]({{site.baseurl}}/navigation), this page is located at **Users** > **Subscription Groups > Email Preference Center**.
+If you're using the [older navigation]({{site.baseurl}}/navigation), this page is located at **Users** > **Subscription Groups** > **Email Preference Center**.
 {% endalert %}
 
 This is where you can manage and view each subscription group. Each subscription group you create is added to this preference center list. You can create multiple preference centers.
@@ -23,7 +23,7 @@ This is where you can manage and view each subscription group. Each subscription
 The preference center is intended to be used within the Braze email channel. The preference center links are dynamic based on each user and cannot be hosted externally.
 {% endalert %}
 
-## Create a preference center via API
+## Creating a preference center with API
 
 By using the [Preference Center Braze endpoints]({{site.baseurl}}/api/endpoints/preference_center), you can create a preference center, a website hosted by Braze, that can display your user's subscription state and subscription group statuses. Using HTML and CSS, your developer team can build the preference center using HTML and CSS so that the styling of the page matches your brand guidelines.
 
@@ -37,19 +37,19 @@ Using Liquid enables you to retrieve the names of your subscription groups, and
 | Valid workspace with an email, SMS, or WhatsApp subscription group | A working workspace with valid users and an email, SMS, or WhatsApp subscription group. |
 | Valid user | A user with an email address and an external ID. |
 | Generated API key with preference center permissions | In the Braze dashboard, go to **Settings** > **API Keys** to confirm that you have access to an API key with preference center permissions. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 If you are using the [older navigation]({{site.baseurl}}/navigation), you can create an API key from **Developer Console** > **API Settings**.
 {% endalert %}
 
-### Step 1: Create a preference center via API
+### Step 1: Use the Create preference center endpoint
 
 Let's begin building a preference center using the [Create preference center endpoint]({{site.baseurl}}/api/endpoints/preference_center/post_create_preference_center/). To customize your preference center, you can include HTML that aligns with your branding in the `preference_center_page_html` field and `confirmation_page_html` field.
 
 The [Generate preference center URL endpoint]({{site.baseurl}}/api/endpoints/preference_center/get_create_url_preference_center/) allows you to grab the preference center URL for a specific user outside of an email that is sent through Braze.
 
-### Step 2: Include in email campaign
+### Step 2: Include in your email campaign
 
 {% multi_lang_include preference_center_warning.md %}
 
@@ -57,7 +57,7 @@ To place a link to the preference center in your emails, use the following Liqui
 
 {% raw %}
 ```liquid
-{{preference_center.${preference_center_name_example}}}
+{{preference_center.${kitchenerie_preference_center_example}}}
 ```
 {%endraw%}
 
@@ -65,7 +65,7 @@ You can also use a combination of HTML that includes Liquid. For example, you ca
 
 {% raw %}
 ```html
-<a href="{{preference_center.${preference_center_name_example}}}">Edit your preferences</a>
+<a href="{{preference_center.${kitchenerie_preference_center_example}}}">Edit your preferences</a>
 ```
 {%endraw%}
 
@@ -117,3 +117,11 @@ This approach does not require query string value-pairs embedded in the URL as t
     "category": offers
 }
 ```
+
+## Frequently asked questions
+
+### I haven't created a preference center. Why am I seeing "PreferenceCenterBrazeDefault" on my dashboard?
+
+This is used to render the preference center when legacy Liquid {%raw%}`${preference_center_url}`{%endraw%} is used, meaning Canvas steps or templates that reference either {%raw%}`${preference_center_url}` or `preference_center.${PreferenceCenterBrazeDefault}`{%endraw%} won't work. This also applies to previously sent messages that included the legacy Liquid or "PreferenceCenterBrazeDefault" as part of the message. 
+
+If you reference {%raw%}`${preference_center_url}`{%endraw%} in a new message again, a preference center named "PreferenceCenterBrazeDefault" will be created again.
\ No newline at end of file
diff --git a/_docs/_user_guide/message_building_by_channel/email/reporting_and_analytics/analytics_glossary.md b/_docs/_user_guide/message_building_by_channel/email/reporting_and_analytics/analytics_glossary.md
index 1fc1d338176..1ef6ba10ed2 100644
--- a/_docs/_user_guide/message_building_by_channel/email/reporting_and_analytics/analytics_glossary.md
+++ b/_docs/_user_guide/message_building_by_channel/email/reporting_and_analytics/analytics_glossary.md
@@ -1,86 +1,358 @@
 ---
 nav_title: Email Analytics Glossary
-article_title: Email Analytics Glossary 
+article_title: Email Analytics Glossary
+layout: email_report_metrics
 page_order: 0
-layout: glossary_page
-glossary_top_header: "Email analytics glossary"
-glossary_top_text: "These are terms you'll find in the analytics section of your email campaign or Canvas, post-launch. Search for the metrics you need in this glossary. <br><br> This glossary does not necessarily include metrics you might see in Currents or in other downloaded reports outside of your Braze account."
-
+excerpt_separator: ""
+page_type: glossary
 description: "This glossary includes the terms you will find in the analytics section of your email campaign or Canvas, post-launch. This glossary does not include Currents metrics."
-channel:
+channel: 
   - email
+---
 
-glossaries:
-  - name: "Variation"
-    description: Variation of a campaign, differing as defined by the creator.
-    calculation: Count
-  - name: "Emailable"
-    description: Users who have an email address on record and have explicitly opted in or subscribed.
-    calculation: Count
-  - name: "Audience %"
-    description: Percentage of users who received a particular variant.
-    calculation: Number of Recipients in Variant / Unique Recipients
-  - name: "Unique Recipients"
-    description: Unique Daily Recipients. The number of users who received a particular message in a day. This number is received from Braze.
-    calculation: Count
-  - name: "Sends or Messages Sent"
-    description: The total number of messages sent in an email campaign. This number is received from Braze. Note that upon launching a scheduled campaign, this metric will include all messages sent, regardless of whether they have been sent out yet due to rate limiting.
-    calculation: Count
-  - name: "Deliveries"
-    description: The total number of messages (Sends) successfully sent to and received by emailable recipients.
-    calculation: Sends - Bounces
-  - name: "Deliveries %"
-    description: The total number of messages (Sends) successfully sent to and received by emailable parties.
-    calculation: (Sends - Bounces) / (Sends)
-  - name: "Bounces"
-    description: The total number of messages that were unsuccessfully delivered to the intended recipients. This could occur because the email addresses were incorrect or deactivated. There are two types of <br>bounces:<br><br> -<b>Hard Bounces</b>&#58; A hard bounce is when an email fails to deliver to the recipient due to a permanent delivery error. A hard bounce might occur because the domain name doesn't exist or because the recipient is unknown. If an email receives a hard bounce, we will stop any future requests to this email address. <br><br>-<b>Soft Bounces</b>&#58; A soft bounce is when an email fails to deliver to the recipient due to a temporary delivery error, even though the recipient’s email address is valid. A soft bounce might occur because the recipient's inbox is full, the server was down, or the message was too large for the recipient's inbox. If an email receives a soft bounce, we will usually retry within 72 hours, but the number of retry attempts varies from receiver to receiver. <br><br> You can view your hard and soft bounces in the <a href='/docs/user_guide/administrative/app_settings/developer_console/message_activity_log_tab/#message-activity-log-tab'>Message Activity Log</a>. <br><br><i> An email bounce for customers using SendGrid consists of hard bounces, spam, and emails sent to invalid addresses. </i>
-    calculation: Count
-  - name: "Bounces % or Bounce Rate"
-    description: The percentage of messages that were hard bounced by the intended recipients. This could occur because the email address is invalid, does not exist, or is deactivated.
-    calculation: Bounces / Sends
-  - name: "Spam"
-    description: The total number of emails delivered that were marked as "spam." Braze automatically unsubscribes users that marked an email as spam, and those users won't be targeted by future emails.
-    calculation: (Marked as Spam) / (Sends)
-  - name: "Spam % or Spam Rate"
-    description: The percentage of emails delivered that were marked or otherwise designated as "spam." Braze automatically unsubscribes users that marked an email as spam, and those users won't be targeted by future emails.
-    calculation: (Marked as Spam) / (Sends)
-  - name: "Unique Opens"
-    description: The total number of delivered emails that have been opened by a single user or machine at least once. This is tracked over a 7 day period for Email.
-    calculation: (Unique Opens) / (Deliveries)
-  - name: "Unique Opens % or Unique Open Rate"
-    description: The percentage of delivered emails that have been opened by a single user at least once. This is tracked over a 7 day period for Email.
-    calculation: (Unique Opens) / (Deliveries)
-  - name: "Unique Clicks"
-    description: Distinct number of recipients who have clicked within a message at least once. This is tracked over a 7 day period for Email and measured by <a href='/docs/help/help_articles/data/dispatch_id/'>dispatch_id</a>
-    calculation: Count
-  - name: "Unique Clicks % or Click Rate"
-    description: Distinct number of recipients who have clicked within a message at least once. This is tracked over a 7 day period for Email.
-    calculation: Unique Clicks / Deliveries
-  - name: "Unsubscribers or Unsub"
-    description: Number of messages resulting in an unsubscription. Unsubscriptions occur when a user clicks on the Braze unsubscribe link.
-    calculation: Count
-  - name: "Unsubscribers % or Unsub Rate"
-    description: Percentage of messages delivered which resulted in an unsubscription. Unsubscriptions occur when a user clicks on the Braze unsubscribe link.
-    calculation: Unsubscribes / Deliveries
-  - name: "Revenue"
-    description: The total revenue in dollars from campaign recipients within the set <a href='/docs/user_guide/engagement_tools/campaigns/testing_and_more/conversion_events/#primary-conversion-event'>primary conversion window</a>.
-    calculation: Count
-  - name: "Primary Conversions (A) or Primary Conversion Event"
-    description: The number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign. This defined event is determined by the marketer when building the campaign.
-    calculation: Count
-  - name: "Primary Conversions (A) % or Primary Conversion Event Rate"
-    description: The percentage of times a defined event occurred after interacting with or viewing a received message from a Braze campaign. This defined event is determined by the marketer when building the campaign.
-    calculation: "Primary Conversions / Unique Recipients"
-  - name: "Confidence"
-    description: The percentage of confidence that a certain variant of a message is outperforming the control group.
-  - name: "Machine Opens"
-    description: Includes the proportion of "opens" that are affected by Apple's Mail Privacy Protection (MPP) for iOS 15. For example, if a user opens an email using the Mail app on an Apple device, this will be logged as a <i>Machine Opens</i>. This metric is tracked starting November 11, 2021 for SendGrid and December 2, 2021 for SparkPost.
-    calculation: Count
-  - name: "Other Opens"
-    description: Includes emails that haven't been identified as <i>Machine Opens</i> . For example, when a user opens an email on another platform (such as Gmail app on a phone, Gmail on desktop browser), this will be logged as an  <i>Other Opens</i>. Note that a user can also open an email (such as the open counts toward <i>Other Opens</i>) before a <i>Machine Opens</i> count is logged. If a user opens an email once (or more) after a machine open event from a non-Apple Mail inbox, then the amount of times that the user opens the email is calculated toward <i>Other Opens</i> and only once toward <i>Unique Opens</i>.
-    calculation: Count
-  - name: "Click to Open Rate"
-    description: The percentage of unique emails opened that have been clicked at least once.
-    calculation: Unique Clicks / Unique Opens
+<style>
+  .calculation-line {
+    color: #76848C;
+    font-size: 14px;
+  }
+</style>
 
----
+{% api %}
+
+### Variation
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Variation' %}
+
+<span class="calculation-line">Calculation: Count</span>
+
+{% endapi %}
+
+{% api %}
+
+### Emailable
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Emailable' %}
+
+<span class="calculation-line">Calculation: Count</span>
+
+{% endapi %}
+
+{% api %}
+
+### Audience %
+
+{% apitags %}
+Percentage
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Audience' %}
+
+<span class="calculation-line">Calculation: (Number of Recipients in Variant) / (Unique Recipients)</span>
+
+{% endapi %}
+
+{% api %}
+
+### Unique Recipients
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Unique Recipients' %} This number is received from Braze.
+
+<span class="calculation-line">Calculation: Count</span>
+
+{% endapi %}
+
+{% api %}
+
+### Sends
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Sends' %}  This metric is provided by Braze.
+
+<span class="calculation-line">Calculation: Count</span>
+
+{% endapi %}
+
+{% api %}
+
+### Messages Sent
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Messages Sent' %}  This metric is provided by Braze.
+
+<span class="calculation-line">Calculation: Count</span>
+
+{% endapi %}
+
+{% api %}
+
+### Deliveries
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Deliveries' %} For emails, *Deliveries* is the total number of messages (Sends) successfully sent to and received by emailable parties.
+
+<span class="calculation-line">Calculation: (Sends) - (Bounces) </span>
+
+{% endapi %}
+
+{% api %}
+
+### Deliveries %
+
+{% apitags %}
+Percentage
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Deliveries %' %}
+
+<span class="calculation-line">Calculation: (Sends - Bounces) / (Sends) </span>
+
+{% endapi %}
+
+{% api %}
+
+### Bounces
+
+{% apitags %}
+Count, Percentage
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Bounces' %} 
+
+For email, *Bounce %* or *Bounce Rate* is the percentage of messages that were unsuccessfully sent or designated as "returned" or "not received" from send services used or not received by the intended emailable users.
+
+An email bounce for customers using SendGrid consists of hard bounces, spam (`spam_report_drops`), and emails sent to invalid addresses (`invalid_emails`).
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><b><i>Bounces</i>:</b> Count</li>
+        <li><b><i>Bounce %</i> or <i>Bounce Rate %</i>:</b> (Bounces) / (Sends)</li>
+    </ul>
+</span>
+{:/}
+
+{% endapi %}
+
+{% api %}
+
+### Hard Bounce
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Hard Bounce' %} 
+
+<span class="calculation-line">Calculation: Count </span>
+
+{% endapi %}
+
+{% api %}
+
+### Soft Bounce
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Soft Bounce' %} If an email receives a soft bounce, we will usually retry within 72 hours, but the number of retry attempts varies from receiver to receiver.
+
+<span class="calculation-line">Calculation: Count </span>
+
+{% endapi %}
+
+{% api %}
+  
+### Spam
+
+{% apitags %}
+Count, Percentage
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Spam' %}
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><b><i>Spam</i>:</b> Count</li>
+        <li><b><i>Spam %</i> or <i>Spam Rate %</i>:</b> (Marked as Spam) / (Sends)</li>
+    </ul>
+</span>
+{:/}
+
+{% endapi %}
+
+{% api %}
+  
+### Unique Opens
+
+{% apitags %}
+Count, Percentage
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Unique Opens' %} For email, this is tracked over a 7 day period.
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><b><i>Unique Opens</i>:</b> Count</li>
+        <li><b><i>Unique Opens %</i> or <i>Unique Open Rate</i>:</b> (Unique Opens) / (Deliveries)</li>
+    </ul>
+</span>
+{:/}
+
+{% endapi %}
+
+{% api %}
+
+### Unique Clicks
+
+{% apitags %}
+Count, Percentage
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Unique Clicks' %} This is tracked over a seven-day period for email and measured by <a href='/docs/help/help_articles/data/dispatch_id/'>dispatch_id</a>. This includes clicks on Braze-provided unsubscribe links.
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><b><i>Unique Clicks</i>:</b> Count</li>
+        <li><b><i>Unique Clicks %</i> or <i>Click Rate</i>:</b> (Unique Clicks) / (Deliveries)</li>
+    </ul>
+</span>
+{:/}
+
+{% endapi %}
+
+{% api %}
+  
+### Unsubscribers or Unsub
+
+{% apitags %}
+Count, Percentage
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Unsubscribers or Unsub' %}
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><b><i>Unsubscribers</i> or <i>Unsub</i>:</b> Count</li>
+        <li><b><i>Unsubscribers %</i> or <i>Unsub Rate</i>:</b> (Unsubscribes) / (Deliveries)</li>
+    </ul>
+</span>
+{:/}
+
+{% endapi %}
+
+{% api %}
+
+### Revenue
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Revenue' %}
+
+<span class="calculation-line">Calculation: Count </span>
+
+{% endapi %}
+
+{% api %}
+
+### Primary Conversions (A) or Primary Conversion Event
+
+{% apitags %}
+Count, Percentage
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Primary Conversions (A) or Primary Conversion Event' %} For email, push, and webhooks, we start tracking conversions after the initial send.
+
+{::nomarkdown}
+<span class="calculation-line">
+    Calculation:
+    <ul>
+        <li><b><i>Primary Conversions (A)</i> or <i>Primary Conversion Event</i>:</b> Count</li>
+        <li><b><i>Primary Conversions (A) %</i> or <i>Primary Conversion Event Rate</i>:</b> (Primary Conversions) / (Unique Recipients)</li>
+    </ul>
+</span>
+{:/}
+
+{% endapi %}
+
+{% api %}
+
+### Confidence
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Confidence' %}
+
+{% endapi %}
+
+{% api %}
+
+### Machine Opens
+  
+{% multi_lang_include metrics.md metric='Machine Opens' %} This metric is tracked starting November 11, 2021 for SendGrid and December 2, 2021 for SparkPost.
+
+<span class="calculation-line">Calculation: Count </span>
+
+{% endapi %}
+
+{% api %}
+
+### Other Opens
+
+{% apitags %}
+Count
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Other Opens' %} Note that a user can also open an email (such as the open counts toward <i>Other Opens</i>) before a <i>Machine Opens</i> count is logged. If a user opens an email once (or more) after a machine open event from a non-Apple Mail inbox, then the amount of times that the user opens the email is calculated toward <i>Other Opens</i> and only once toward <i>Unique Opens</i>.
+
+<span class="calculation-line">Calculation: Count </span>
+
+{% endapi %}
+
+{% api %}
+
+### Click-to-Open Rate
+
+{% apitags %}
+Percentage
+{% endapitags %}
+
+{% multi_lang_include metrics.md metric='Click-to-Open Rate' %}
+
+<span class="calculation-line">Calculation: (Unique Clicks) / (Unique Opens) (for Email)</span>
+
+{% endapi %}
\ No newline at end of file
diff --git a/_docs/_user_guide/message_building_by_channel/email/templates/html_email_template.md b/_docs/_user_guide/message_building_by_channel/email/templates/html_email_template.md
index f5892f12962..1413317ed50 100644
--- a/_docs/_user_guide/message_building_by_channel/email/templates/html_email_template.md
+++ b/_docs/_user_guide/message_building_by_channel/email/templates/html_email_template.md
@@ -54,7 +54,7 @@ There are several email error messages you may receive when uploading an HTML te
 |Images over 5&nbsp;MB| Reduce the number of images and try uploading again. |
 |Extra Images| There may be additional images in your file that are not referenced in your HTML file. This will not cause a fail error, but the extra images will be discarded. If those images were supposed to be referenced in the HTML file, then check the content, correct any errors, and try uploading again.|
 |Missing Images| If there are images referenced in your HTML file, but those images are not included in the image folder of the ZIP file, you will receive a file error. Inspect your file and correct any errors (like misspellings), or add the missing images to your ZIP file and try uploading again.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Step 4: Finish and save your template
 
diff --git a/_docs/_user_guide/message_building_by_channel/email/templates/link_aliasing.md b/_docs/_user_guide/message_building_by_channel/email/templates/link_aliasing.md
index c05d1c54099..1123d24be3b 100644
--- a/_docs/_user_guide/message_building_by_channel/email/templates/link_aliasing.md
+++ b/_docs/_user_guide/message_building_by_channel/email/templates/link_aliasing.md
@@ -3,7 +3,7 @@ nav_title: Link Aliasing
 article_title: Link Aliasing
 alias: /link_aliasing/
 page_order: 3
-description: "This article describes how link aliasing works and what your links will look like."
+description: "This article describes how link aliasing works and provides examples for what your links will look like."
 channel:
   - email
 
@@ -11,70 +11,61 @@ channel:
 
 # [![Braze Learning course]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/link-aliasing){: style="float:right;width:120px;border:0;" class="noimgborder"}Link aliasing
  
-> Use link aliasing to create recognizable, user-generated names to identify links sent in email messages from Braze. These links are available for segmentation retargeting, action-based triggering, and link analytics. Link aliasing gives you the ability to retarget users that have clicked specific links, allowing you to create action-based triggers when users click a specific aliased link.
+> Use link aliasing to create recognizable, user-generated names to identify links sent in email messages from Braze. These links are available for segmentation retargeting, action-based triggering, and link analytics.
+
+## About link aliasing
+
+With link aliasing, you can create user-generated names to identify and track links sent in emails. This way, you can efficiently use these recognizable link aliases in your emails to track engagement and analyze campaign performance, without needing to reference the full link.
+
+With link aliasing, you can:
+
+- **Retarget users who have clicked specific links:** Identify and target users who have clicked a link.
+- **Create action-based triggers:** Send an email when a user clicks a link.
+- **Analyze metrics:** Compare how many users have clicked Link A versus Link B.
+
+### How it works
+
+Braze uniquely identifies links within emails by appending an extra parameter called the `lid` (also known as the link identifier) to every link URL. This `lid` value allows Braze to track, monitor, and aggregate user interactions with the link even if the rest of the URL parameters may differ. This helps to provide insights into how users engage with the content in your email campaigns.
 
 ## Creating a link alias
 
-Link aliasing works by decorating a Braze-generated query parameter on links in the email channel. To create a link alias, follow these steps: 
+To create a link alias, follow these steps: 
 
-1. Open your email body.
-2. Click the **Link Management** tab.
+1. In your campaign or Canvas component, go to your email body.
+2. Select the **Link Management** tab.
 3. Braze automatically generates unique default link aliases for each of your links.
 4. Give the alias a name. Aliases must be uniquely named per email campaign variant or Canvas component. 
 
 You can also set an alias that will be used to reference a specific link when dealing with reporting or segmentation. 
 
-![][2]
+![Link Management page with four link aliases.][2]
 
-Link aliasing is only supported in `href` attributes within HTML anchor tags where it is safe to append a query parameter. It's best to include a question mark (?) at the end of your link so that Braze can easily append the `lid` value. Without appending the `lid` value, Braze will not recognize the URL for link aliasing.
+{% alert note %}
+Link aliasing is only supported in `href` attributes within HTML anchor tags where it is safe to append a query parameter. It's best practice to include a question mark (?) at the end of your link so that Braze can easily append the `lid` value. Without appending the `lid` value, Braze will not recognize the URL for link aliasing.
+{% endalert %}
 
-### Managing link aliases
+## Managing link aliases
 
-Follow these steps to view all of your tracked link aliases:
+To view all of your tracked link aliases, do the following:
 
 1. Go to **Settings** > **Email Preferences** under **Workspace Settings**.
-2. Click the **Link Aliasing Settings** tab.
+2. Select the **Link Aliasing Settings** tab.
 
 {% alert important %}
 If you are using the [older navigation]({{site.baseurl}}/user_guide/administrative/access_braze/navigation/), these settings are under **Manage Settings**.
 {% endalert %}
 
-Here, you can also sort and search through all link aliases.
-
-![Tracked Link Aliases page that shows a link alias named "test" that is an active part of a Canvas step.][8]
-
-#### Untracking link aliases
-
-On the **Link Aliasing Settings** tab, you can turn off tracking for link aliases.
+Here, you can sort, search, and turn off tracking for link aliases.
 
-1. Select the link alias.
-2. Click **Turn off tracking**.  
+![Tracked Link Aliases page that shows two link aliases named "TechPartners" and "Help" that are associated with a campaign named "Email_Survey".][8]
 
-#### Link aliases and user profile data
-
-In Braze, if you have a link alias in your app or website and a user clicks on it, the event is recorded in the user's profile with the alias. Later, if you decide to rename this link alias, the previous click data in the user profile **will not** be updated, meaning it will still show as the previous link alias. So, if you target users based on the the new link alias, it will not include the data from the previous link alias.
-
-### Checking workflows
+{% alert tip %}
+Use the [List link alias for campaign]({{site.baseurl}}/get_campaign_link_alias/) and [List link alias for Canvas]({{site.baseurl}}/get_canvas_link_alias/) endpoints to extract the `alias` set in each message variant in a campaign or an email-specific Canvas component.
+{% endalert %}
 
 Braze recommends evaluating the links within the email, adding link templates, and providing a naming convention that works for segmentation and reporting purposes. This helps you keep track of all links.
 
-When link aliasing is enabled, messages, Content Blocks, and link templates are not modified. Any existing messages using link templates or Content Blocks will be the same. However, when you update a message, link alias markup will apply to all of the links, so you'll need to reapply the link templates for the links to be visible.
-
-### Extracting data
-
-Use the [List link alias for campaign][3] and [List link alias for Canvas][4] endpoints to extract the `alias` set in each message variant in a campaign or an email-specific Canvas component.
-
-## Link aliasing in Content Blocks
-
-New Content Blocks will have their links modified where Braze will append a `lid={{placeholder}}` to each link where applicable. This placeholder value is resolved when inserted into an email message variant.
-
-To modify the links within existing Content Blocks that were created before Braze enabled link aliasing, duplicate the existing Content Blocks, then modify the links within the duplicated Content Blocks.
-
-When a Content Block without a `lid` value is inserted into a new message, the links from that Content Block are not tracked with an alias. When a new Content Block is inserted into an "old" message variant, the links from that message variant will be recognized by link aliasing. Links from the Content Block are also recognized. However, "old" Content Blocks cannot nest "new" Content Blocks.
-
-{% alert tip %}
-For Content Blocks, Braze recommends creating copies of existing Content Blocks to use in new messages. This can be done by bulk duplicating to prevent scenarios where you might reference a Content Block that has not been enabled for link aliasing in a new message.
-{% endalert %}
+When link aliasing is turned on, messages, Content Blocks, and link templates are not modified. Any existing messages using link templates or Content Blocks will be the same. However, when you update a message, link alias markup will apply to all of the links, so you'll need to reapply the link templates for the links to be visible.
 
 ## How links are updated with link aliasing
 
@@ -87,7 +78,7 @@ The following tables provide examples of links in an email body, link aliasing r
 | Link in Email Body    | Link with Aliasing                     |
 |-----------------------|----------------------------------------|
 | https://www.braze.com | https://www.braze.com?lid=slfdldtqdhdk |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Link with more query parameters
 
@@ -96,7 +87,7 @@ The following tables provide examples of links in an email body, link aliasing r
 | Link in Email Body                                            | Link with Aliasing                                                             |
 |---------------------------------------------------------------|--------------------------------------------------------------------------------|
 | https://www.braze.com?utm_campaign=retention&utm_source=email | https://www.braze.com?utm_campaign=retention&utm_source=email&lid=0goty30mviyz |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### HTML link
 
@@ -105,7 +96,7 @@ The following tables provide examples of links in an email body, link aliasing r
 | Link in Email Body                                                | Link with Aliasing                                                                |
 |-------------------------------------------------------------------|-----------------------------------------------------------------------------------|
 | {%raw%}`<a href="{{custom_attribute.{product_url}}}?">`{%endraw%} | {%raw%}`<a href="{{custom_attribute.{product_url}}}?lid=ac7a548g5kl7">`{%endraw%} |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Link with anchor
 
@@ -114,7 +105,7 @@ The following tables provide examples of links in an email body, link aliasing r
 | Link in Email Body                               | Link with Aliasing                                                |
 |--------------------------------------------------|-------------------------------------------------------------------|
 | https://www.braze.com#bookmark1?utm_source=email | https://www.braze.com?lid=eqslgd5a9m3y#bookmark1?utm_source=email |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Link with anchor and capture tag
 
@@ -123,47 +114,9 @@ The following tables provide examples of links in an email body, link aliasing r
 | Link in Email Body                                                                        | Link with Aliasing                                                                                           |
 |-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|
 | {%raw%}`<a href="https://www.braze.com/promotions#special-offer">Check out our special offer!</a>`{%endraw%}  | {%raw%}`<a href="https://www.braze.com/promotions#special-offer?lid={{link_alias}}">Check out our special offer!</a>` {%endraw%} |
-{: .reset-td-br-1 .reset-td-br-2}
-
-## Link aliasing for URLs generated via Liquid
-
-For URLs that are generated by an `assign` statement in the HTML or in a Content Block, we recommend adding a question mark (?) into the anchor tag. This will help Braze append query parameters (`lid = somevalue`) so link aliasing can work properly. Without identifying where to append query parameters, link aliasing will not recognize these URLs.
-
-### Example
-
-Check out this link aliasing example for the recommended formatting of the anchor tag:
-
-{% raw %}
-```liquid
-{% assign link1 = "https://www.braze1.com" %}
-
-<a href="{{link1}}?">Click Here</a>
-```
-{% endraw %}
-
-If the link has parameters within it that contain a question mark (`?`), you can replace it in the anchor tag with an ampersand (`&`), such as in this example:
-
-{% raw %}
-```liquid
-{% assign link_with_params = "https://www.braze1.com?param_1&param_2" %}
-
-<a href="{{link_with_params}}&">Click Here</a>
-```
-{% endraw %}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-## Link templates
-
-For new message variants, any existing [link template]({{site.baseurl}}/user_guide/message_building_by_channel/email/templates/link_template/) can be used from the **Link Management** tab. For messages that were launched with a link template, they still will be applied. If an existing message is modified, the link template must be reapplied through the **Link Management** tab. 
-
-{% alert note %}
-Link templates can only be applied for links visible in the **Link Management** tab. This means that links without the `lid` URL parameter, such as "old" Content Blocks or links that cannot be marked up, will not be eligible for link templates. To fix this, we recommend copying "old" Content Blocks or including a question mark (?) or ampersand (&) in the `href` attribute for the URL.
-{% endalert %}
-
-## Link segmentation
-
-The retargeting of aliases filters allow you to create segmentation filters based on your customers clicking a specifically tracked alias from either an email campaign or Canvas component. This filter is only available for campaigns or Canvases that have tracked aliases present.
-
-### Tracking links
+## Tracking link aliases
 
 In the **Link Management** tab, select which aliases you would like to be "tracked" for segmentation purposes and to be present in segmentation filters. Note that tracked aliases are only for segmentation purposes and will have no impact on your link being tracked for reporting purposes.
 
@@ -190,41 +143,33 @@ Braze allows you to select unlimited links to track, though you may only retarge
 Braze only tracks up to the last 100 clicked link aliases at the profile level. 
 {% endalert %}
 
-### Untracking links
-
-Untracking a link will not reallocate existing segments with the filter to the untracked alias. The old data will remain on the user profiles until it's replaced by newer data. The following segmentation filters will continue to exist, but new segments cannot be created with that filter.
-
-For segmentation purposes, only 100 links can be tracked per workspace by default. Links in archived messages are automatically untracked. However, if archived messages are unarchived, the links will need to be tracked again. When link aliases are tracked, link reporting is indexed by the alias instead of top-level domains or full URLs.
-
-![][1]
-
-### Segment filters
+### Action-based filters
+ 
+You can create action-based messages targeting any link (tracked or not tracked) or retarget users based on if they clicked an alias across any email campaign or Canvas component.
 
-The following segment filters apply to click events that are tracked at the time the event is processed. This means untracking links won't remove existing data and tracking a link won't backfill the data.
+![Action-Based Options to target users who have clicked an alias in a Canvas component or interacted with a campaign.][6]
 
-#### Clicked Alias in Campaign
+### Segmentation filters
 
-Retarget users based on the specific alias that was clicked in a campaign. Only the campaigns that have aliases which were tracked will be reflected here.
+In Braze, if you have a link alias in your email and a user clicks on it, the event is recorded in the user's profile with the alias.
 
-#### Clicked Alias in Canvas Step
+If you use the "Clicked Alias in Any Campaign or Canvas Step" segmentation filter and later decide to rename this link alias, the previous click data in the user profile **will not** be updated, meaning it will still show as the previous link alias. So, if you target users based on the the new link alias, it will not include the data from the previous link alias.
 
-Retarget users based on the specific alias that was clicked in a Canvas component. A pipe delimited filter option displays the Canvas and Canvas component, followed by the alias within the Canvas component. Only Canvas steps with tracked aliases will be shown here.
+If you use the "Clicked Alias in Campaign" or "Clicked Alias in Canvas" segmentation filter, this will filter your users by whether they clicked a specific alias in a specific campaign or Canvas. If multiple users share the same email address and the link alias is clicked, all other users who share the email address will have their user profiles updated. 
 
-#### Clicked Alias in Campaign or Canvas
+The following segmentation filters apply to click events that are tracked at the time the event is processed. This means untracking links won't remove existing data and tracking a link won't backfill the data. For more details, see [Segmentation filters]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters).
 
-Retarget users based on any alias that was clicked in the campaign or Canvas component. Because aliases are considered "global", any global alias will target link clicks from all campaigns and Canvas steps.
+#### Untracking links
 
-![][5]
+Untracking a link won't reallocate existing segments with the filter to the untracked alias. The old data will remain on the user profiles until it’s replaced by newer data.
 
-### Action-based filters
- 
-You can create action-based messages targeting any link (tracked or not tracked) or retarget users based on if they clicked an alias across any email campaign or Canvas component. 
+For segmentation purposes, only 100 links can be tracked per workspace by default. Links in archived messages are automatically untracked. However, if archived messages are unarchived, the links will need to be tracked again. When link aliases are tracked, link reporting is indexed by the alias instead of top-level domains or full URLs.
 
-![][6]
+![Campaign Analytics tab that displays three link aliases and their total clicks.][1]
 
 ### Email clicks event
 
-The [email clicks event][7] occurs when a user clicks an email. Multiple events may be generated for the same campaign if a user clicks multiple times or clicks different links within the email. There are two additional fields for the email clicks event when link aliasing is enabled: `link_id` and `link_alias`.
+If you export your engagement data with Currents, an email click event will be slightly different if you have link aliasing enabled. It will have two additional fields for the [email clicks event]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events#email-clicks-events/) when link aliasing is turned on: `link_id` and `link_alias`.
 
 ```json
 // Email Click: users.messages.email.Click
@@ -261,12 +206,47 @@ The behavior for `dispatch_id` differs between Canvas and campaigns because Braz
 _Update noted in August 2019._
 {% endalert %}
 
+## Link aliasing in Content Blocks
+
+New Content Blocks will have their links modified where Braze will append a `lid={{placeholder}}` to each link where applicable. This placeholder value is resolved when inserted into an email message variant.
+
+To modify the links within existing Content Blocks that were created before Braze enabled link aliasing, duplicate the existing Content Blocks, then modify the links within the duplicated Content Blocks.
+
+When a Content Block without a `lid` value is inserted into a new message, the links from that Content Block are not tracked with an alias. When a new Content Block is inserted into an "old" message variant, the links from that message variant will be recognized by link aliasing. Links from the Content Block are also recognized. However, "old" Content Blocks cannot nest "new" Content Blocks.
+
+{% alert tip %}
+For Content Blocks, Braze recommends creating copies of existing Content Blocks to use in new messages. This can be done by bulk duplicating to prevent scenarios where you might reference a Content Block that has not been enabled for link aliasing in a new message.
+{% endalert %}
+
+## Link aliasing for URLs generated via Liquid
+
+For URLs that are generated by an `assign` statement in the HTML or in a Content Block, we recommend adding a question mark (?) into the anchor tag. This will help Braze append query parameters (`lid = somevalue`) so link aliasing can work properly. Without identifying where to append query parameters, link aliasing will not recognize these URLs.
+
+### Example
+
+Check out this link aliasing example for the recommended formatting of the anchor tag:
+
+{% raw %}
+```liquid
+{% assign link1 = "https://www.braze1.com" %}
+
+<a href="{{link1}}?">Click Here</a>
+```
+{% endraw %}
+
+If the link has parameters within it that contain a question mark (`?`), you can replace it in the anchor tag with an ampersand (`&`), such as in this example:
+
+{% raw %}
+```liquid
+{% assign link_with_params = "https://www.braze1.com?param_1&param_2" %}
+
+<a href="{{link_with_params}}&">Click Here</a>
+```
+{% endraw %}
+
 
 [1]: {% image_buster /assets/img/link_aliasing_click_table.png %}
 [2]: {% image_buster /assets/img/link_aliasing_composer.png %}
-[3]: {{site.baseurl}}/get_campaign_link_alias/ 
-[4]: {{site.baseurl}}/get_canvas_link_alias/
 [5]: {% image_buster /assets/img/link_aliasing_segmentation_filters.png %}
 [6]: {% image_buster /assets/img/link_aliasing_action_based_filters.png %}
-[7]: {{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events#email-clicks-events/
 [8]: {% image_buster /assets/img/tracked_aliases.png %}
\ No newline at end of file
diff --git a/_docs/_user_guide/message_building_by_channel/email/using_locales.md b/_docs/_user_guide/message_building_by_channel/email/using_locales.md
index 70982b74bf9..3e0d0f3cd1e 100644
--- a/_docs/_user_guide/message_building_by_channel/email/using_locales.md
+++ b/_docs/_user_guide/message_building_by_channel/email/using_locales.md
@@ -69,4 +69,4 @@ Yes. However, be sure to check that the HTML styling is not translated with the
 | The translation file includes locales that don't exist in **Multi-Language Support** settings.                                                           | These locales will not be saved in Braze.                                                                      |
 | The translation file includes text blocks that don't exist in the current message (such as the current draft at the time the translations are uploaded). | The text blocks that don't exist in your current message will not be saved from the translation file to Braze. |
 | Removing a locale from the message after that locale has already been uploaded to the message as part of the translation file.                           | Removing the locale will remove any translations associated with the locale in your message.                   |
-{: .reset-td-br-1 .reset-td-br-2}
\ No newline at end of file
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
\ No newline at end of file
diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/about.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/about.md
index 59832911ac7..99ba2ea6f64 100644
--- a/_docs/_user_guide/message_building_by_channel/in-app_messages/about.md
+++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/about.md
@@ -25,7 +25,7 @@ With the rich level of content offered by in-app messages, you can leverage this
 | Sales and promotions | Use modal in-app messages to greet customers with visually appealing media containing static promotion codes or offers. Incentivize them to make purchases or conversions when they otherwise wouldn't have. |
 | Encouraging feature adoption | Encourage customers to use other parts of your app or take advantage of a service. |
 | Highly personalized campaigns | Place in-app messages as the first thing your customers see when they enter your app or site. Add in some Braze personalization features, such as [Connected Content][3], to compel users to take action and therefore make your outreach more effective.
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Other use cases to consider include the following:
 
diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details.md
index 9d52ae95a56..49229097674 100644
--- a/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details.md
+++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details.md
@@ -56,7 +56,7 @@ In general, Braze recommends using images that fit into a 16:10 screen.
 |--- | --- | --- |
 | Image + Text | 6:5 aspect ratio<br>High-res 1200 x 1000&nbsp;px<br> Minimum 600 x 500&nbsp;px | Cropping can occur on all sides, but the image will always fill the top 50% of the viewport |
 | Image Only | 3:5 aspect ratio<br>High-res 1200 x 2000&nbsp;px<br> Minimum 600 x 1000&nbsp;px | Cropping can occur on the left and right edges on taller devices |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 [Further details for fullscreens]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen)
 
@@ -70,7 +70,7 @@ In general, Braze recommends using images that fit into a 16:10 screen.
 |--- | --- | ------ |
 | Image + Text | 29:10 aspect ratio<br>High-res 1450 x 500&nbsp;px<br> Minimum 600 x 205&nbsp;px | Tall images will scale down and be horizontally centered. Wide images will be clipped on the left and right edges. |
 | Image Only | Nearly any aspect ratio<br>High-res up to 1200 x 2000&nbsp;px<br> Minimum 600 x 600&nbsp;px | The message will resize to fit images of most aspect ratios. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 [Further details for modals]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/creative_details/modal)
 
@@ -82,7 +82,7 @@ In general, Braze recommends using images that fit into a 16:10 screen.
 | Layout | Asset Size | Notes |
 |--- | --- | --- |
 | Image + Text | 1:1 aspect ratio<br>High-res 150 x 150&nbsp;px<br> Minimum 50 x 50&nbsp;px | Images of various aspect ratios will fit into a square image container, without cropping. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 [Further details for slideups]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/creative_details/slideup)
 
diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen.md
index 33759183853..efaad344f3c 100644
--- a/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen.md
+++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen.md
@@ -44,7 +44,7 @@ Fullscreen in-app messages will fill the entire height of a device and crop hori
 |--- | --- | --- |
 | Image and text | 6:5 aspect ratio<br> High-res 1200 x 1000&nbsp;px<br> Minimum 600 x 500&nbsp;px | Cropping can occur on all sides, but the image will always fill the top 50% of the viewport |
 | Image only | 3:5 aspect ratio<br> High-res 1200 x 2000&nbsp;px<br> Minimum 600 x 1000&nbsp;px | Cropping can occur on the left and right edges on taller devices |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Landscape
 
@@ -52,7 +52,7 @@ Fullscreen in-app messages will fill the entire height of a device and crop hori
 |--- | --- | --- |
 | Image and text | 10:3 aspect ratio<br> High-res 2000 x 600px<br> Minimum 1000 x 300&nbsp;px | Cropping can occur on all sides, but the image will always fill the top 50% of the viewport |
 | Image only | 5:3 aspect ratio<br> High-res 2000 x 1200px<br> Minimum 1000 x 600&nbsp;px | Cropping can occur on the left and right edges on taller devices |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Image safe zone
 
diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details/slideup.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details/slideup.md
index 59a177bc911..05827e6fa62 100644
--- a/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details/slideup.md
+++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/creative_details/slideup.md
@@ -29,7 +29,7 @@ Slideup messages can contain up to three lines of copy before truncation with el
 | Layout | Asset Size | Notes |
 |--- | --- | --- |
 | Image + Text | 1:1 aspect ratio<br>High-res 150 x 150&nbsp;px<br> Minimum 50 x 50&nbsp;px | Images of various aspect ratios will fit into a square image container, without cropping. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 You should always [preview and test your messages]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/testing/) on a variety of devices to ensure that the most important areas of your image and message appear as expected. Note that when previewing your message on the composer, the actual rendering on devices may differ.
 
diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create.md
index e1770506be9..d11e5d27d14 100644
--- a/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create.md
+++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create.md
@@ -26,7 +26,7 @@ Not sure whether your in-app message should be sent using a campaign or a [Canva
 | Minimum SDK version                                                          | Recommended SDK version                                                       |
 | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
 | {::nomarkdown}{% sdk_min_versions swift:5.0.0 android:8.0.0 web:2.5.0 %}{:/} | {::nomarkdown}{% sdk_min_versions swift:6.5.0 android:26.0.0 web:4.8.1 %}{:/} |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% details More information on minimum SDKs %}
 
@@ -42,7 +42,7 @@ The following outlines the individual minimum SDK requirements for these feature
 | Text links*                                                         | Request push primer                                                           |
 | ------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
 | {::nomarkdown}{% sdk_min_versions swift:6.2.0 android:26.0.0 %}{:/} | {::nomarkdown}{% sdk_min_versions web:4.8.1 swift:6.5.0 android:26.0.0 %}{:/} |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 *If you include a link in your in-app message that redirects to a URL and the end user is not on the minimum SDK versions specified, clicking on the link will close the message and the user will not be able to return to the message to submit the form.
 
diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/editor_blocks.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/editor_blocks.md
index 2fa49ad16b8..ee1c69d4d8f 100644
--- a/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/editor_blocks.md
+++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/editor_blocks.md
@@ -24,7 +24,7 @@ The following table describes how you can use each editor block type.
 | Button | Adds a standard button. Properties for this block allow for editing, setting links, and logging analytics. |
 | Spacer | Adds space or padding between other blocks. |
 | Custom Code (early access) | Inserts raw HTML, CSS, and JS.  |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Properties
 
@@ -41,7 +41,7 @@ Details for each editor block's properties are provided in the following tables.
 | Align | Moves the text to be aligned left, center, right, or justified |
 | Line Height | Modifies the distance between lines of text |
 | Letter spacing | Modifies the distance in between each character |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Image
 
@@ -51,7 +51,7 @@ Details for each editor block's properties are provided in the following tables.
 | Align | Moves the image to be left, center or right-oriented |
 | URL | The hosted address for your image |
 | Alternate text | The written copy that appears in place of an image if the image fails to load. Screen readers announce alt text to explain images, so use plain language to provide key information about an image |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Button
 
@@ -60,7 +60,7 @@ Details for each editor block's properties are provided in the following tables.
 | Corner Radius | Determines how round you would like the corners |
 | On-click Behavior | Determines the action when clicking the button and sets the appropriate link protocol |
 | URL | Dynamic based on the selected On-click behavior |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Spacer
 
@@ -68,11 +68,11 @@ Details for each editor block's properties are provided in the following tables.
 | --- | --- |
 | Background color | Modifies the background color of the spacer |
 | Height | Modifies the height of the spacer. You can also modify this by using the resize handles on the spacer. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Custom Code
 
 | Name | Description |
 | --- | --- |
 | Custom Code | Allows you to add, edit, or delete HTML, CSS, and JavaScript for an in-app message. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/style_settings.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/style_settings.md
index 5948c63c520..194de00f652 100644
--- a/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/style_settings.md
+++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/style_settings.md
@@ -138,4 +138,4 @@ You can also use keyboard shortcuts to copy and paste styles:
 | ------------ | ---------------------------------------------- | ------------------------------------------------- |
 | Copy styles  | <kbd>⌘</kbd> + <kbd>Shift</kbd> + <kbd>c</kbd> | <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>c</kbd> |
 | Paste styles | <kbd>⌘</kbd> + <kbd>Shift</kbd> + <kbd>v</kbd> | <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>v</kbd> |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/create.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/create.md
index 75bf90ba010..aad2a51512a 100644
--- a/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/create.md
+++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/create.md
@@ -69,7 +69,7 @@ Start by choosing which platforms should receive the message. Use this selection
 | Mobile Apps | iOS & Android SDKs|
 | Web Browsers | Web SDK|
 | Both Mobile Apps & Web Browsers | iOS, Android & Web SDKs|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Step 3: Specify your message types
 
@@ -233,7 +233,7 @@ When your customer clicks on a button in your in-app message, the following acti
 | Log Custom Event | Choose a [custom event]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/) to trigger. Can be used to display another in-app message or trigger additional messaging. |
 | Log Custom Attribute | Choose a [custom attribute]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/) to set for the current user. |
 | Request Push Permission | Shows the native push permission. Read more about [push priming]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_primer_messages/), as well as [best practices]({{site.baseurl}}/user_guide/message_building_by_channel/push/users_and_subscriptions/#best-practices) for priming users for push. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Note: the __Request Push Permission__, __Log Custom Event__, and __Log Custom Attribute__ options require the following SDK minimum versions:
 
@@ -279,7 +279,7 @@ The content of the **Style** tab varies based on your chosen message options in
 |Background Color | HEX color code. | Your desired HEX color will display. You will also be able to choose the opacity of the color. This is the background of the entire message and will clearly display behind your text body. |
 |Screen Overlay | HEX color code. | Your desired HEX color will display. You will also be able to choose the opacity of the color. Only available for newer Braze SDK versions. This is the frame around the entire message. |
 |Chevron or other Close Message Option | HEX color code. | Your desired HEX color will display. You will also be able to choose the opacity of the color. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Always [preview and test]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/testing/) your message before sending.
 
diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/customize/html_in-app_messages.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/customize/html_in-app_messages.md
index a4bac66bc18..db46bd532a1 100644
--- a/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/customize/html_in-app_messages.md
+++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/customize/html_in-app_messages.md
@@ -173,7 +173,7 @@ The following file types are supported for upload:
 | SVG Images       | `.svg`                            |
 | JavaScript Files | `.js`                             |
 | CSS Files        | `.css`                            |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Braze recommends uploading assets to the media library for two reasons:
 
@@ -215,7 +215,7 @@ You can track performance within your custom code in-app message using the [`bra
 | Button 2   | `brazeBridge.logClick("1")` |
 | Body click | `brazeBridge.logClick()`    |
 | Custom button tracking |`brazeBridge.logClick("your custom name here")`|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 This method of button tracking replaces the prior automatic click tracking methods (such as `?abButtonId=0`), which have been removed.
diff --git a/_docs/_user_guide/message_building_by_channel/line.md b/_docs/_user_guide/message_building_by_channel/line.md
index 16750a4b004..07fe0cb3a47 100644
--- a/_docs/_user_guide/message_building_by_channel/line.md
+++ b/_docs/_user_guide/message_building_by_channel/line.md
@@ -6,10 +6,9 @@ layout: dev_guide
 channel:
   - LINE
 guide_top_header: "LINE"
-guide_top_text: "[LINE](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf) is the most popular messaging app in Japan, with over 95 million monthly active users. In addition to messaging, LINE offers its users an “all-in-one” platform for social media, gaming, shopping, and payments.<br><br>You can integrate your LINE accounts with Braze to leverage your zero- and first-party customer data to send compelling LINE messages to the right customers based on their preferences, behaviors, and cross-channel interactions.<br><br>LINE access is in beta and only available in select Braze packages. Reach out to your account manager or customer success manager to get started."
+guide_top_text: "[LINE](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf) is the most popular messaging app in Japan, with over 95 million monthly active users. In addition to messaging, LINE offers its users an “all-in-one” platform for social media, gaming, shopping, and payments.<br><br>You can integrate your LINE accounts with Braze to leverage your zero- and first-party customer data to send compelling LINE messages to the right customers based on their preferences, behaviors, and cross-channel interactions.<br><br>Sending LINE messages from Braze will draw from your account's Message Credits."
 description: "This landing page is home to the LINE channel. Here, you can find articles on setting up LINE, LINE subscription groups, LINE campaigns, LINE reporting, and more."
-hidden: true
-permalink: /line/
+alias: /line/
 
 guide_featured_title: "LINE"
 guide_featured_list:
diff --git a/_docs/_user_guide/message_building_by_channel/line/create.md b/_docs/_user_guide/message_building_by_channel/line/create.md
index 90ba18d14f9..b7ed39d9c1e 100644
--- a/_docs/_user_guide/message_building_by_channel/line/create.md
+++ b/_docs/_user_guide/message_building_by_channel/line/create.md
@@ -8,17 +8,12 @@ tool:
  - Campaigns
 channel:
  - LINE
-hidden: true
-permalink: /line/create/
+alias: /line/create/
 ---
 
 # Creating a LINE message
 
-> LINE campaigns can directly reach and programmatically chat with your customers. You can use Liquid and other dynamic content to create a personal experience with your users and create an environment that fosters and enhances an unobtrusive user experience with your brand.<br><br>This article is part of the LINE beta collection. [Return to the main page](https://www.braze.com/docs/line/).
-
-{% alert important %}
-LINE access is in beta and only available in select Braze packages. Reach out to your account manager or customer success manager to get started.
-{% endalert %}
+> LINE campaigns can directly reach and programmatically chat with your customers. You can use Liquid and other dynamic content to create a personal experience with your users and create an environment that fosters and enhances an unobtrusive user experience with your brand.
 
 ## Prerequisites
 
@@ -28,6 +23,7 @@ Before creating a LINE message, do the following:
 2. Acknolwedge policies, limits, and content rules.
 3. [Set up your LINE connection]({{site.basesurl}}/user_guide/message_building_by_channel/line/line_setup/).
 
+Sending LINE messages from Braze will draw from your account's Message Credits.
 
 ## Step 1: Choose where to build your message
 
@@ -47,9 +43,8 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), you can fi
 2. Select **LINE**, or, for campaigns targeting multiple channels, select **Multichannel Campaign**.
 3. Name your campaign something clear and meaningful.
 4. Add [Teams]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/teams/) and [Tags]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) as needed.
-   * Tags make your campaigns easier to find and build reports out of. For example, when using the [Report Builder]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/), you can filter by particular tags.
+   * Tags make your campaigns easier to find and build reports out of.
 5. Add and name as many variants as you need for your campaign. You can choose different platforms, message types, and layouts for each of your added variants. For more on this topic, refer to [Multivariate and A/B testing]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/).
-6. Select a [subscription group]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/) to ensure you're sending your message to the proper users. When selecting a subscription group, Braze will automatically add a segmenting filter, ensuring that only users subscribed will receive the campaign. Only long codes and short codes that belong to that subscription group will be used to send SMS to target users.
 
 {% alert tip %}
 If all of the messages in your campaign are going to be similar or have the same content, compose your message before adding additional variants. You can then choose **Copy from Variant** from the **Add Variant** dropdown.
@@ -72,9 +67,9 @@ If all of the messages in your campaign are going to be similar or have the same
 
 ## Step 2: Compose your LINE message
 
-Write your message using languages and personalization (such as Liquid or Connected Content) as needed. LINE allows up to five message bubbles in each message, which can be text or image messages.
+Write your message using personalization (such as Liquid or Connected Content) as needed. LINE allows up to five message bubbles in each message, which can be any of the available messages layouts: text, image, rich, or card-based.
 
-![LINE composer with a message displayed in the preview.][1]{: style="max-width:70%;"}
+![LINE composer with a message displayed in the preview.][1]
 
 {% alert tip %}
 If you plan to use Liquid, be sure to include a default value for your personalization. This will prevent recipients with incomplete user profiles from receiving a blank placeholder. For example, instead of a user receiving the message "Hi, !", they might receive the message "Hi, new subscriber!".
diff --git a/_docs/_user_guide/message_building_by_channel/line/create/message_types.md b/_docs/_user_guide/message_building_by_channel/line/create/message_types.md
index 80c2a8e044e..f4fb6b13f69 100644
--- a/_docs/_user_guide/message_building_by_channel/line/create/message_types.md
+++ b/_docs/_user_guide/message_building_by_channel/line/create/message_types.md
@@ -8,17 +8,12 @@ tool:
  - Campaigns
 channel:
  - LINE
-hidden: true
-permalink: /line/create/message_types/
+alias: /line/create/message_types/
 ---
 
 # LINE message types
 
-> This article covers the LINE message types you can compose, including aspects and limitations, and is part of the LINE beta collection. [Return to the main page]({{site.baseurl}}/line/).
-
-{% alert important %}
-LINE access is in beta and only available in select Braze packages. Reach out to your account manager or customer success manager to get started.
-{% endalert %}
+> This article covers the LINE message types you can compose, including aspects and limitations.
 
 When you compose a LINE message, you can drag-and-drop message types into the composer and then customize them.
 
@@ -58,7 +53,7 @@ Use URL images for use cases that incorporate:
 | Image file URL length | 2,000 characters maximum  |
 | Image format          | PNG, JPEG             |
 | File size     |  10&nbsp;MB maximum |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Rich messages (image map)
 
@@ -79,7 +74,7 @@ Use cases include:
 | Image format          | PNG (can be transparent), JPEG             |
 | Aspect ratio          | 1:1 (width:height)
 | File size     |  10&nbsp;MB maximum |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### URI link 
 
@@ -87,7 +82,7 @@ Use cases include:
 |--------------------------|----------------------------|
 | Character count      | 1,000 maximum |
 | Schemes              | HTTP, HTTPS, LINE, tel |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Text 
 
@@ -111,7 +106,7 @@ Use cases include:
 | Columns                  | 10 maximum |
 | Aspect ratio             | Rectangle: 1.51:1 <br> Square: 1:1  |
 | Title                    | 40 characters maximum
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ### Image
@@ -122,7 +117,7 @@ Use cases include:
 | Image format              | JPEG or PNG |
 | Width                     | 1,024 pixels  |
 | File size                 | 1 MB |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 ### Text
@@ -131,7 +126,7 @@ Use cases include:
 |-------------------------|----------------------------|
 | Characters              | 120 maximum (no image or title) <br> 60 maximum (message with an image or title)  |
 | Actions                 | 3 maximum |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 [1]: {% image_buster /assets/img/line/line_text_message.png %}
diff --git a/_docs/_user_guide/message_building_by_channel/line/line_setup.md b/_docs/_user_guide/message_building_by_channel/line/line_setup.md
index b910e606ba9..b5cbeffea14 100644
--- a/_docs/_user_guide/message_building_by_channel/line/line_setup.md
+++ b/_docs/_user_guide/message_building_by_channel/line/line_setup.md
@@ -7,29 +7,26 @@ search_tag: Partner
 page_order: 0
 channel:
  - LINE
-hidden: true
-permalink: /line/line_setup/
+alias: /line/line_setup/
 ---
 
 
 # LINE setup
 
-> This article covers how to set up the LINE channel in Braze and is part of the LINE beta collection. [Return to the main page](https://www.braze.com/docs/line/).
-
-{% alert important %}
-LINE access is in beta and only available in select Braze packages. Reach out to your account manager or customer success manager to get started.
-{% endalert %}
+> This article covers how to set up the LINE channel in Braze, including how to set up users, reconcile user IDs, and create LINE test users in Braze.
 
 ## Prerequisites
 
 You'll need the following to integrate LINE with Braze:
 
 - [LINE business account](https://www.linebiz.com/jp-en/manual/OfficialAccountManager/tutorial-steps/?list=7171)
-- [Premium or verified account](https://www.infobip.com/docs/line/get-started#premium-id-line-official-account) status (necessary for syncing existing followers)
+- Premium or verified account status (necessary for syncing existing followers)
    - View [LINE's account guidelines](https://terms2.line.me/official_account_guideline_oth)
 - [LINE developers account](https://developers.line.biz/en/docs/line-developers-console/login-account/)
 - [LINE messaging API channel](https://developers.line.biz/en/docs/line-developers-console/overview/#channel)
 
+Sending LINE messages from Braze will draw from your account's Message Credits.
+
 ## Types of LINE accounts
 
 | Account type | Description |
@@ -37,7 +34,7 @@ You'll need the following to integrate LINE with Braze:
 | Unverified account | An unreviewed account that can be obtained by anyone (individual or corporate). This account is represented with a gray badge and won't appear in search results within the LINE app. |
 | Verified account | An account that has passed the LINE Yahoo screening. This account is represented with a blue badge and will appear in search results within the LINE app.<br><br>This account is only available for accounts based in Japan, Taiwan, Thailand, and Indonesia.  |
 | Premium account | An account that has passed the LINE Yahoo screening. This account is represented with a green badge and will appear in search results within the LINE app. This account type is automatically granted during the screening at LINE's discretion. |
-{: .reset-td-br-1 .resest-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Required account type
 
@@ -54,8 +51,6 @@ Verified accounts are only available for accounts based in Japan, Taiwan, Thaila
 3. Enter the required information.
 4. Wait for a notification with the review results.
 
-If you want to sync users who followed a specific channel before that channel was synced with Braze, ask your customer success manager or account manager to [submit a request](https://servicedesk.braze.com/plugins/servlet/desk/portal/12) to the WhatsApp team.
-
 ## Integrating LINE
 
 To set up consistent user updates, bring over existing users' LINE IDs, and sync them all to LINE’s subscription states:
@@ -68,6 +63,8 @@ To set up consistent user updates, bring over existing users' LINE IDs, and sync
 
 ## Step 1: Import or update existing LINE users
 
+This step is necessary if you have an existing and identified LINE user, as Braze will later automatically pull their subscription state and update the correct user profile. If you haven’t previously reconciled users with their LINE ID, skip this step. 
+
 You can import or update users using any of the methods that Braze supports, including the [`/users/track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) endpoint, [CSV import]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv-import), or [Cloud Data Ingestion]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/). 
 
 Regardless of the method you use, update the `native_line_id` to provide the user’s LINE ID. To learn more the `native_line_id`, see [User setup](#user-setup).
@@ -78,9 +75,9 @@ The subscription group state shouldn't be specified, and it will be ignored. LIN
 
 ## Step 2: Integrate LINE channel
 
-After your existing LINE user base is imported into or updated in Braze, you can integrate your channel. After integration, new followers of your LINE channel will have unidentified user profiles created when they follow the channel.
+After the integration process completes, Braze will automatically pull that channel’s LINE followers into Braze. For any LINE IDs that are already associated with a Braze user profile, each profile will be updated with the “subscribed” status, and any LINE IDs that are remaining will generate anonymous users. Additionally, new followers of your LINE channel will have unidentified user profiles created when they follow the channel.
 
-### Step 2.1: Connect your LINE channel to Braze
+### Step 2.1: Edit webhook settings
 
 1. In LINE, go the **Messaging API** tab and edit your **Webhook settings**:
    - Set the **Webhook URL** to `https://anna.braze.com/line/events`.
@@ -94,7 +91,7 @@ After your existing LINE user base is imported into or updated in Braze, you can
 | Channel ID | Select your provider and then go to **Channels** > your channel > **Basic settings** |
 | Channel secret | Select your provider and then go to **Channels** > your channel > **Basic settings** |
 | Channel access token | Select your provider and then go to **Channels** > your channel > **Messaging API**. If there isn't a channel access token, select **Issue**. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {: start="3"}
 3. Go to your **Settings** page > **Response settings** and do the following:
@@ -104,7 +101,7 @@ After your existing LINE user base is imported into or updated in Braze, you can
 
 ![Response settings page with toggles for how your account will handle chats.][2]{: style="max-width:80%;"}
 
-### Step 2.2: Set up your LINE subscription group in Braze
+### Step 2.2: Generate LINE subscription groups in Braze
 
 1. Go to the Braze Technology Partners page for LINE and input the information you noted from your LINE **Providers** tab:
    - Provider ID
@@ -119,9 +116,9 @@ After your existing LINE user base is imported into or updated in Braze, you can
 
 ![LINE subscription groups section displaying one subscription group for the "LINE" channel.][4]{: style="max-width:80%;"}
 
-## Step 3: Request a subscription status sync
+## Step 3: Reconcile user IDs
 
-We recommend syncing all LINE followers before going live. This updates all followers' user profiles with the correct subscription status. That way, if users follow your LINE channel before they're identified in your app, there's an existing user profile to update or merge.
+Combine your users' LINE IDs with their existing Braze user profiles by following the steps in [User ID reconciliation](#user-id-reconciliation).
 
 ## Step 4: Change your user update methods 
 
@@ -201,34 +198,28 @@ To learn more about managing duplicate users in Braze, see [Duplicate Users]({{s
 
 ## User setup
 
-LINE is the source of truth for user subscription states. Even if you have the LINE ID for a user (`native_line_id`), if that user hasn't followed the LINE channel you're sending from, LINE won't deliver that channel's messages to the user.
+LINE is the source of truth for user subscription states. Even if you have the LINE ID for a user (`native_line_id`), if that user hasn't followed the LINE channel you're sending from, LINE won't deliver messages to the user.
 
 To help manage this, Braze offers tooling and logic that supports a well-integrated user base, including subscription syncing and event updates for LINE follows and unfollows.
 
 ### Subscription syncing and event logic
 
-1. **Subscription sync tool:** This can be used to gather the list of all the LINE IDs that are following your channel. There are two ways to use this tool:
-
-| Usage | Description |
-| --- | --- |
-| Only update existing user profiles | All Braze user profiles that have a `native_line_id` that follows the LINE channel will be updated to have a subscription group status of `subscribed`. |
-| Update existing profile and create new | All Braze user profiles that have a `native_line_id` that follows the LINE channel will be updated to have a subscription group status of `subscribed`. <br><br> Any follower of the LINE channel that doesn't have a Braze user profile with the `native_line_id` will have:<br> - An anonymous user profile created with `native_line_id` set to the user LINE ID following the channel <br>- A user alias `line_id` set to the user LINE ID following the channel <br>- A subscription group status of `subscribed`. |
-{: .reset-td-br-1 .reset-td-br-2}
+1. **Subscription sync tool:** This tool is automatically deployed after a successful LINE channel integration. Use it to update existing profiles and create new profiles.<br><br>All Braze user profiles that have a `native_line_id` that follows the LINE channel will be updated to have a subscription group status of `subscribed`. Any follower of the LINE channel that doesn't have a Braze user profile with the `native_line_id` will have:<br><br>- An anonymous user profile created with `native_line_id` set to the user LINE ID following the channel <br>- A user alias `line_id` set to the user LINE ID following the channel <br>- A subscription group status of `subscribed`
 
 {: start="2"}
-2. **Event updates:** These can be used to update a user's subscription status. When Braze receives user event updates for the integrated LINE channel and the event is a follow, the user profile will have a subscription group status of `subscribed`. If the event is an unfollow, the user profile will have a subscription group status of `unsubscribed`.<br><br>- All Braze user profiles with a matching `native_line_id` will be automatically updated. <br>- If no matching user profile exists for an event, Braze will [create an anonymous user](https://www.braze.com/docs/line/user_management/).
+2. **Event updates:** These are used to update a user's subscription status. When Braze receives user event updates for the integrated LINE channel and the event is a follow, the user profile will have a subscription group status of `subscribed`. If the event is an unfollow, the user profile will have a subscription group status of `unsubscribed`.<br><br>- All Braze user profiles with a matching `native_line_id` will be automatically updated. <br>- If no matching user profile exists for an event, Braze will [create an anonymous user](https://www.braze.com/docs/line/user_management/).
 
 ## Use cases
 
 These are use cases of how users can be updated after you follow the setup steps above.
 
-##### Existing user profile follows LINE channel 
+##### Existing Braze user profile already follows LINE channel
 
 1. The Braze user profile is updated with a `native_line_id` attribute. Its default subscription status is `unsubscribed`.
 2. The subscription sync tool is run, finds that the user is following the LINE channel, and then updates the user profile with the subscription status `subscribed`.
 3. If any subscription status changes occur (such as the user blocks, unfriends, or refollows the channel), Braze receives the update from LINE and updates the user profile with the `native_line_id` accordingly.
 
-##### Existing user profile blocks, unfriends, or unfollows LINE channel 
+##### Existing user profile has blocked, unfriended, or unfollowed LINE channel 
 
 1. The Braze user profile is updated with a `native_line_id` attribute. Its default subscription status is `unsubscribed`.
 2. The subscription sync tool doesn't find that the user is following the LINE channel and the user’s subscription status remains as `unsubscribed`.
@@ -272,7 +263,10 @@ These are use cases of how users can be updated after you follow the setup steps
 
 LINE IDs are automatically received by Braze when a user follows your channel, or when you use the one-time “sync followers” workflow. LINE IDs are also specific to the channel that users follow, so it's unlikely that users can provide their LINE IDs.
 
-To combine a LINE ID with an existing Braze user profile, you can use the LINE login method.
+There are two ways to combine a LINE ID with an existing Braze user profile:
+
+- [LINE login](#line-login)
+- [User account linking](#user-account-linking)
 
 ### LINE Login
 
diff --git a/_docs/_user_guide/message_building_by_channel/line/line_users.md b/_docs/_user_guide/message_building_by_channel/line/line_users.md
index 3f49525fee6..fd64c7831bd 100644
--- a/_docs/_user_guide/message_building_by_channel/line/line_users.md
+++ b/_docs/_user_guide/message_building_by_channel/line/line_users.md
@@ -4,5 +4,4 @@ config_only: true
 noindex: true
 layout: blank_config
 page_order: 4
-hidden: true
 ---
diff --git a/_docs/_user_guide/message_building_by_channel/line/line_users/subscription_groups.md b/_docs/_user_guide/message_building_by_channel/line/line_users/subscription_groups.md
index 0d252e34468..8c4798ca961 100644
--- a/_docs/_user_guide/message_building_by_channel/line/line_users/subscription_groups.md
+++ b/_docs/_user_guide/message_building_by_channel/line/line_users/subscription_groups.md
@@ -6,17 +6,12 @@ description: "This article covers LINE message subscription groups."
 page_type: reference
 channel:
  - LINE
-hidden: true
-permalink: /line/subscription_groups/
+alias: /line/subscription_groups/
 ---
 
 # LINE subscription groups
 
-> There are two subscription states for LINE users: subscribed and unsubscribed. LINE can have up to 100 subscription groups per workspace, with each subscription group connected to its own LINE channel.<br><br>This article is part of the LINE beta collection. [Return to main page](https://www.braze.com/docs/line/).
-
-{% alert important %}
-LINE access is in beta and only available in select Braze packages. Reach out to your account manager or customer success manager to get started.
-{% endalert %}
+> There are two subscription states for LINE users: subscribed and unsubscribed. LINE can have up to 100 subscription groups per workspace, with each subscription group connected to its own LINE channel.
 
 | State | Definition |
 | --- | --- |
diff --git a/_docs/_user_guide/message_building_by_channel/line/line_users/user_management.md b/_docs/_user_guide/message_building_by_channel/line/line_users/user_management.md
index c0653dd9b9b..169beaa37a8 100644
--- a/_docs/_user_guide/message_building_by_channel/line/line_users/user_management.md
+++ b/_docs/_user_guide/message_building_by_channel/line/line_users/user_management.md
@@ -6,13 +6,12 @@ description: "This article covers the LINE user ID and how to set it."
 page_type: reference
 channel:
  - LINE
-hidden: true
-permalink: /line/user_management/
+alias: /line/user_management/
 ---
 
 # LINE user management
 
-> The LINE user ID is stored on the user profile attribute called `native_line_id`. This identifier is used to send messages on a user on the LINE channel. This article covers the `native_line_id` attribute and is part of the LINE beta collection. [Return to the main page](https://www.braze.com/docs/line/).
+> The LINE user ID is stored on the user profile attribute called `native_line_id`, which is used to send messages to a user on the LINE channel. This article covers how to set and find the `native_line_id` attribute.
 
 Customer user data is represented in a [Braze user profile]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/). A user profile stores information and attributes about a company’s users, such as first names and email addresses. 
 
diff --git a/_docs/_user_guide/message_building_by_channel/line/messaging_users.md b/_docs/_user_guide/message_building_by_channel/line/messaging_users.md
index 81b96fa3a97..4cbe6d6b6d2 100644
--- a/_docs/_user_guide/message_building_by_channel/line/messaging_users.md
+++ b/_docs/_user_guide/message_building_by_channel/line/messaging_users.md
@@ -6,20 +6,15 @@ description: "This reference article covers how chat with users by using templat
 page_type: reference
 channel:
  - LINE
-hidden: true
-permalink: /line/messaging_users/
+alias: /line/messaging_users/
 ---
 
 # Messaging LINE users
 
-> LINE is a two-way communication channel. You can go beyond sending users messages and engage in conversations with users by using templated campaigns and Canvases.<br><br>This article is part of the LINE beta collection. [Return to the main page](https://www.braze.com/docs/line/).
+> LINE is a two-way communication channel. You can go beyond sending users messages and engage in conversations with users by using templated campaigns and Canvases. This article covers the details of messaging users, such as how to set trigger words for inbound messages and unrecognized responses.
 
 There are various methods to converse with users through LINE, such as using LINE trigger words. You can also use calls-to-action (CTAs) to encourage user engagement with your LINE messaging.
 
-{% alert important %}
-LINE access is in beta and only available in select Braze packages. Reach out to your account manager or customer success manager to get started.
-{% endalert %}
-
 ## Action-based triggers
 
 You can create campaigns and Canvases that start, branch, and have mid-journey changes when you receive an inbound LINE message (a message sent from a user) that contains a trigger word. Make sure you choose trigger words that match what you expect users to send.
diff --git a/_docs/_user_guide/message_building_by_channel/line/reporting.md b/_docs/_user_guide/message_building_by_channel/line/reporting.md
index 2a11e779ceb..2c94550b596 100644
--- a/_docs/_user_guide/message_building_by_channel/line/reporting.md
+++ b/_docs/_user_guide/message_building_by_channel/line/reporting.md
@@ -12,7 +12,7 @@ permalink: /line/reporting/
 
 # LINE reporting
 
-> After launching your campaign or Canvas, you can view key metrics on the campaign details page or Canvas analytics.<br><br>This article is part of the LINE beta collection. [Return to the main page](https://www.braze.com/docs/line/).
+> After launching your campaign or Canvas, you can view key metrics on the campaign details page or Canvas analytics. This article covers where you can find those metrics and what they represent.
 
 {% alert tip %}
 Looking for definitions for the terms and metrics in your report? Refer to [Report metrics glossary]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics/).
@@ -49,6 +49,7 @@ If you want to simplify your view, select **+ Add/Remove Columns** and clear any
 Here are some key LINE metrics you may see in your analytics. To see the definitions of all LINE metrics used in Braze, refer to [Report metrics glossary]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics/).
 
 | Term | Definition |
+| --- | --- |
 | Sends | The total number of sends successfully communicated between Braze and LINE. This does not mean the message was received by the user. |
 | Unique Opens | The total number of LINE messages sent that were opened by users after a minimum threshold of 20 messages per day has been reached. |
 | Total Opens | The total number of times that the LINE messages sent were opened by users after a minimum threshold of 20 messages per day has been reached. |
@@ -70,9 +71,5 @@ The **Conversion Event Details** panel shows you the performance of your convers
 
 The **Conversion Correlation** panel gives you insight into what user attributes and behaviors help or hurt the outcomes you set for campaigns. For more information, refer to [Conversion correlation]({{site.baseurl}}/user_guide/engagement_tools/testing/conversion_correlation).
 
-## LINE user IDs 
-
-LINE user IDs are specific to each user per provider. Users are unlikely to know their LINE ID (unlike their email or phone number), as their LINE ID changes for each brand they follow.
-
 
 [1]: {% image_buster /assets/img/line/line_performance.png %}
\ No newline at end of file
diff --git a/_docs/_user_guide/message_building_by_channel/push/about.md b/_docs/_user_guide/message_building_by_channel/push/about.md
index 33c6285d54e..eecbc60c0f0 100644
--- a/_docs/_user_guide/message_building_by_channel/push/about.md
+++ b/_docs/_user_guide/message_building_by_channel/push/about.md
@@ -29,7 +29,7 @@ Push notifications are a great tool for attracting new users and making re-engag
 | First Purchases | After users are comfortable using your app, you can use push notifications to help convert them into in-app purchasers. |
 | New Features | Push notifications can be effective in notifying disengaged users about new features that might attract them back to your app. |
 | Time Sensitive Offers | If you have a clock ticking on an offer, sometimes push is a great way to let your users know about it before it expires. These messages generally carry a high sense of urgency and are optimal for reminding recently-lapsed users about your app.<br><br> For example, suppose your app is a game and you offer your users an in-game currency bonus if they maintain a streak of playing the game daily. Alerting a user that that streak is in danger of being broken could be a reasonable push if they've exceeded a certain number of days. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For more information on re-engaging lapsed users, see our [Quick Wins][23] page on the topic.
 
@@ -56,12 +56,12 @@ Your push messages must fall within the guidelines of the Apple App Store and Go
 |[3.2.2][9] Unacceptable: (i) Creating an interface for displaying third-party apps, extensions, or plug-ins similar to the App Store or as a general-interest collection.| 
 |[4.5.4][7] Push Notifications must not be required for the app to function, and should not be used to send sensitive personal or confidential information. Push Notifications should not be used for promotions or direct marketing purposes unless customers have explicitly opted in to receive them via consent language displayed in your app’s UI, and you provide a method in your app for a user to opt out from receiving such messages.|
 |[4.10](https://developer.apple.com/app-store/review/guidelines/#monetizing-built-in-capabilities) You may not monetize built-in capabilities provided by the hardware or operating system, such as Push Notifications, the camera, or the gyroscope; or Apple services and technologies, such as Apple Music access, iCloud storage, or Screen Time APIs.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 |Google Play Store Policy|
 |---|
 |[Unauthorized Use or Imitation of System Functionality][10] We don't allow apps or ads that mimic or interfere with system functionality, such as notifications or warnings. System-level notifications may only be used for an app's integral features, such as an airline app that notifies users of special deals, or a game that notifies users of in-game promotions.|
-{: .reset-td-br-1}
+{: .reset-td-br-1 role="presentation" }
 
 [1]: {% image_buster /assets/img/red-dress.gif %}
 [2]: {% image_buster /assets/img/ios_push.png %}
diff --git a/_docs/_user_guide/message_building_by_channel/push/advanced_push_options/push_action_buttons.md b/_docs/_user_guide/message_building_by_channel/push/advanced_push_options/push_action_buttons.md
index efc7c811168..c67e80497dd 100644
--- a/_docs/_user_guide/message_building_by_channel/push/advanced_push_options/push_action_buttons.md
+++ b/_docs/_user_guide/message_building_by_channel/push/advanced_push_options/push_action_buttons.md
@@ -68,7 +68,7 @@ The following table outlines how many characters you can add before your button
 | 1 | 46 characters |
 | 2 | 20 characters |
 | 3 | 11 characters |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 [1]: {% image_buster /assets/img_archive/push_action_example.png %}
diff --git a/_docs/_user_guide/message_building_by_channel/push/advanced_push_options/push_stories.md b/_docs/_user_guide/message_building_by_channel/push/advanced_push_options/push_stories.md
index cfedc990d0b..2550c999c77 100644
--- a/_docs/_user_guide/message_building_by_channel/push/advanced_push_options/push_stories.md
+++ b/_docs/_user_guide/message_building_by_channel/push/advanced_push_options/push_stories.md
@@ -16,7 +16,7 @@ channel:
 | Android Example (Expanded) | IOS Example (Expanded) |
 | :-----: | :----------: |
 | ![][1] | ![][2] |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert note %}
 On iOS SDK versions 3.13.0+, due to a change in how the SDK downloads images, a thumbnail of the first image will not show on the condensed view of the push. Ensure that your message copy prompts users to expand the push to see the images.
diff --git a/_docs/_user_guide/message_building_by_channel/push/android/advanced_campaign_settings.md b/_docs/_user_guide/message_building_by_channel/push/android/advanced_campaign_settings.md
index b193bd92de6..6440f7c306d 100644
--- a/_docs/_user_guide/message_building_by_channel/push/android/advanced_campaign_settings.md
+++ b/_docs/_user_guide/message_building_by_channel/push/android/advanced_campaign_settings.md
@@ -73,7 +73,7 @@ Refer to the following table for priority levels that you can set on Android or
 | Default | Most notifications. Use if your message doesn't explicitly fall under any of the other priority types. | `0` |
 | Low | Information that you want users to know about but does not require immediate action. | `-1`|
 | Min | Contextual or background information. | `-2`|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 For more information, refer to Google's documentation on [Android notifications][2].
 
@@ -101,7 +101,7 @@ Android push notifications provide the option to specify if your notification fa
 | Status | Ongoing information about device or contextual status. |
 | System | System or device status update. Reserved for system use. |
 | Transport | Media transport control for playback. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Push visibility
 
@@ -112,7 +112,7 @@ Android push notifications provide an optional field to determine how a notifica
 | Public | Notification appears on the lock screen |
 | Private | Notification is shown with "Content hidden" as the message |
 | Secret | Notification is not shown on the lock screen |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Additionally, Android users can override how push notifications appear on their lock screen by changing the notification privacy setting on their device. This setting will override the visibility from the push notification.
 
diff --git a/_docs/_user_guide/message_building_by_channel/push/android/notification_channels.md b/_docs/_user_guide/message_building_by_channel/push/android/notification_channels.md
index 272b1e6f536..879ab576f47 100644
--- a/_docs/_user_guide/message_building_by_channel/push/android/notification_channels.md
+++ b/_docs/_user_guide/message_building_by_channel/push/android/notification_channels.md
@@ -65,7 +65,7 @@ To better understand the expected behavior for channels, refer to the following
 |**Company XYZ** updates to an SDK that supports Android O <br>**Company XYZ** does not add any channels to the Braze dashboard<br>**Company XYZ** renames their SDK default channel to "Marketing" | Push notifications sent to Android O devices will create a channel called "Marketing" and notifications will be sent through the "Marketing" channel
 |**Company LMN** updates to an SDK that supports Android O <br>**Company LMN** defines two channels in their application code, "Promotions" and "Order Updates" <br>**Company LMN** adds the channel IDs for "Promotions" and "Order Updates" to the Braze dashboard <br>**Company LMN** designates "Promotions" as the dashboard fallback channel<br>**Company LMN** renames their SDK default channel to "Marketing" | Push notifications sent to Android O devices will not create a channel<br><br>Unless the marketer explicitly specifies that notifications should send through the "Order Updates" or "Marketing" channel, all notifications created before the channels were added to the dashboard will send through the "Promotions" channel<br><br>The SDK default channel, "Marketing" is only created and used if the company attempts to send a notification through an invalid channel ID or if explicitly selected
 |**Company HIJ** updates to Android O but does not update to Braze Android SDK to 2.1.0 or later | Notifications sent to users running Android O or later do not appear |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Adding channels to the Braze dashboard
 
diff --git a/_docs/_user_guide/message_building_by_channel/push/android/rich_notifications.md b/_docs/_user_guide/message_building_by_channel/push/android/rich_notifications.md
index 905d9c382c9..6abe10c75db 100644
--- a/_docs/_user_guide/message_building_by_channel/push/android/rich_notifications.md
+++ b/_docs/_user_guide/message_building_by_channel/push/android/rich_notifications.md
@@ -19,7 +19,6 @@ tool:
 ## Requirements
 
 - Android rich notifications aren't available when creating a quick push campaign.
-- The expanded notification view is only available on devices using Jelly Bean (Android 4.1) or later. If a user's device isn't running on these systems, they will not see the notification image.
 - Android Extended Notification images must be 2:1 ratio, but do not have a size limit.
 - Android also allows for setting a separate image for the standard notification view. These are the recommended size images: 
   - Small: 512x256
diff --git a/_docs/_user_guide/message_building_by_channel/push/best_practices/message_format.md b/_docs/_user_guide/message_building_by_channel/push/best_practices/message_format.md
index f6ac6615f88..a3fb471da00 100644
--- a/_docs/_user_guide/message_building_by_channel/push/best_practices/message_format.md
+++ b/_docs/_user_guide/message_building_by_channel/push/best_practices/message_format.md
@@ -24,7 +24,7 @@ For best results, refer to the following image size and message length guideline
 (iOS) 2:1 *Recommended* | 500&nbsp;KB | 5&nbsp;MB | PNG, JPEG, GIF
 (Android) Push icon | 500&nbsp;KB | 5&nbsp;MB | PNG, JPEG
 (Android) Expanded notification | 500&nbsp;KB | 5&nbsp;MB | PNG, JPEG
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% endtab %}
 {% tab Text %}
@@ -48,7 +48,7 @@ Wondering how many characters you can use in an iOS push notification without it
 pre iOS 8 | 0.256 KB
 post iOS 8 | 2 KB
 Android (FCM) | 4 KB
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% tab Image Example %}
@@ -95,7 +95,7 @@ Chrome | 192 x 192 ≥
 Firefox | 192 x 192 ≥
 Safari | 192 x 192 ≥ (Icons are configurable on a per-campaign basis with Safari 16 on macOS 13+)
 Opera | 192x192 ≥
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 | **Browser** | **Platform** | **Large Image Size**
 | --- | --- | ---
@@ -109,7 +109,7 @@ Safari | macOS | N/A
 Chrome | macOS | N/A
 Firefox | macOS | N/A
 Opera | macOS | N/A
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endtab %}
 {% tab Text %}
@@ -126,7 +126,7 @@ Chrome | macOS | 35 | 50
 Safari | macOS | 38 | 84
 Firefox | macOS | 38 | 42
 Opera | macOS | 38 | 42
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
diff --git a/_docs/_user_guide/message_building_by_channel/push/creating_a_push_message.md b/_docs/_user_guide/message_building_by_channel/push/creating_a_push_message.md
index 219b4022c8d..bca5fdcfa4d 100644
--- a/_docs/_user_guide/message_building_by_channel/push/creating_a_push_message.md
+++ b/_docs/_user_guide/message_building_by_channel/push/creating_a_push_message.md
@@ -75,7 +75,7 @@ There are a few different ways to do this depending on your previous selections:
 | Push notification campaign | Select one or more platforms and devices. If you choose to target multiple devices and platforms, you’re automatically creating a quick push campaign. This provides an editing experience optimized for crafting one message for all selected platforms in a single editor. See [Quick push campaigns]({{site.baseurl}}/quick_push) to understand what's different in this editing experience. |
 | Multichannel campaign | Select **Add Messaging Channel** to add additional push platforms. Because platform selections are specific to each variant, you can try testing message engagement per platform.
 | Canvas | In your Message step, select **+ Add more** to add additional push platforms. Similar to multichannel campaigns, platform selections are specific to each variant. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Step 3: Select notification type (iOS and Android)
 
diff --git a/_docs/_user_guide/message_building_by_channel/push/ios/notification_options.md b/_docs/_user_guide/message_building_by_channel/push/ios/notification_options.md
index fcd7de6fe05..46d233ddf77 100644
--- a/_docs/_user_guide/message_building_by_channel/push/ios/notification_options.md
+++ b/_docs/_user_guide/message_building_by_channel/push/ios/notification_options.md
@@ -148,7 +148,7 @@ Refer to the following table for interruption levels and their descriptions.
 |[Active](https://developer.apple.com/documentation/usernotifications/unnotificationinterruptionlevel/active) (default)|Will only make a sound, vibration, and turn on the screen if the user is not in Focus Mode.|Notifications that require immediate attention, unless the user has Focus Mode enabled.|No|
 |[Time Sensitive](https://developer.apple.com/documentation/usernotifications/unnotificationinterruptionlevel/timesensitive)|Will make a sound, vibrate, and turn on the screen even while in Focus Mode. This requires that the **Time Sensitive Notifications capability** is added your app in Xcode|Timely notifications that should disturb users regardless of their Focus mode, such as a ride share or delivery notification.|Yes|
 |[Critical](https://developer.apple.com/documentation/usernotifications/unnotificationinterruptionlevel/critical)|Will make a sound, vibrate, and turn on the screen even if the phone's **Do Not Disturb** switch is enabled. This [requires explicit approval by Apple](https://developer.apple.com/contact/request/notifications-critical-alerts-entitlement/).|Emergencies such as severe weather or safety alerts|Yes|
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation" }
 
 To change the interruption level for an iOS push notification, select the **Settings** tab and choose the desired level from the **Interruption Level** dropdown menu.
 
diff --git a/_docs/_user_guide/message_building_by_channel/push/push_registration.md b/_docs/_user_guide/message_building_by_channel/push/push_registration.md
index e37efbe5529..2ba7eff66da 100644
--- a/_docs/_user_guide/message_building_by_channel/push/push_registration.md
+++ b/_docs/_user_guide/message_building_by_channel/push/push_registration.md
@@ -57,7 +57,7 @@ Platforms deal with push token registration and push permissions in different wa
 | Get a push token | Send a push token |
 | ---------------- | ----------------- |
 | Applications must register with a push provider in order to get a push token for a device. | Developers can then target the device using the push token generated by FCM/APNs.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Check user's push subscription state
 
@@ -90,7 +90,7 @@ Check out the following chart for actions that lead to push tokens changes or re
 | `changeUser()` method called | The Braze `changeUser()` method switches the user ID that the SDKs are assigning user behavior data to. This method is usually called when a user logs into an application. When `changeUser()` is called with a different or new user ID on a specific device, that device's push token will be moved to the appropriate Braze profile with corresponding user ID. |
 | Push error occurs | Some common push errors that lead to token removal include `MismatchSenderId`, `InvalidRegistration`, and other types of push bounces. <br><br>Check out our full list of common [push errors][errors]. |
 | User uninstalls | When a user uninstalls the application from a device, Braze will remove the user's push token from the profile. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### What does this look like on a broader scale?
 
@@ -103,7 +103,7 @@ If we want to launch a campaign, we create a campaign in Braze that generates a
 | Registration steps | Messaging steps |
 | ------------------ | --------------- |
 | 1. Customer (device) registers to push provider<br>2. Provider generates and delivers push token<br>3. Flush tokens in Braze |1. Braze sends push payload to provider<br>2. Provider delivers the push payload to the device<br>3. SDK passes messaging stats to Braze |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Frequently asked questions
 
diff --git a/_docs/_user_guide/message_building_by_channel/push/users_and_subscriptions.md b/_docs/_user_guide/message_building_by_channel/push/users_and_subscriptions.md
index 3388a57696d..6d9bcf3e705 100644
--- a/_docs/_user_guide/message_building_by_channel/push/users_and_subscriptions.md
+++ b/_docs/_user_guide/message_building_by_channel/push/users_and_subscriptions.md
@@ -30,7 +30,7 @@ By default, for your user to receive your messages through push, their push subs
 |`Subscribed`| Default push subscription state when a user profile is created in Braze. |
 |`Opted-In`| A user has explicitly expressed a preference to receive push notifications. Braze will automatically move a user's opt-in state to `Opted-In` if a user accepts an OS-level push prompt.<br><br>This does not apply to Android 12 or below users.|
 |`Unsubscribed`| A user explicitly unsubscribed from push through your application or other methods your brand provides. By default, Braze push campaigns only target users that are `Subscribed` or `Opted-in` for push.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert important %}
 Braze does not automatically change a user's push subscription state to `Unsubscribed`. Remember that if a user's push subscription state is `Unsubscribed`, then the user's `Push Enabled` filter in segmentation will be `false`.
@@ -96,7 +96,7 @@ Because a user's decision is final and you can't ask again after they decline, u
 |iOS| ![An iOS native push prompt asking "My App would like to send you notifications" with two buttons, "Don't Allow" and "Allow" at the bottom of the message.][ios-push-prompt]{: style="max-width:410px;"} | This does not apply when requesting [provisional push](#provisional-push) permission.|
 |Android| ![An Android push message asking "Allow Kitchenerie to send you notifications?" with two buttons, "Allow" and "Don't allow" at the bottom of the message.][android-push-prompt]{: style="max-width:410px;"} | This push permission was introduced in Android 13. Before Android 13, permission was not required to send push.|
 |Web| ![A web browser's native push prompt asking "Braze.com wants to show notification" with two buttons, "Block" and "Allow" at the bottom of the message.][web-push-prompt]{: style="max-width:410px;"} | |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Android
 
diff --git a/_docs/_user_guide/message_building_by_channel/push/web.md b/_docs/_user_guide/message_building_by_channel/push/web.md
index c9788a746c6..85fb5f0d641 100644
--- a/_docs/_user_guide/message_building_by_channel/push/web.md
+++ b/_docs/_user_guide/message_building_by_channel/push/web.md
@@ -38,7 +38,7 @@ Here are some examples of common web push message use cases.
 | App download | Draw web users to your mobile app to help them get even more value out of your products. Consider leveraging personalization to highlight app benefits based on their current engagement patterns. |
 | Discounts and sales | Increase customer awareness of time-sensitive events and promotions. Message across multiple channels, including web push, to increase awareness of your brand's promotions. |
 | Cart abandonment | Send automated reminders to users who haven't finished their transactions to bring them back to the checkout flow. <br><br>Research conducted by Braze found that web push is 53% more effective than email and 23% more impactful than mobile push at getting recipients to come back and complete a purchase. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Prerequisites to use web push
 
diff --git a/_docs/_user_guide/message_building_by_channel/sms/about_sms.md b/_docs/_user_guide/message_building_by_channel/sms/about_sms.md
index 8b1a5d333d5..77aae027ad3 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/about_sms.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/about_sms.md
@@ -23,7 +23,7 @@ SMS, also known as Short Message Service, is used to send text messages to mobil
 | General Marketing | SMS messages are a direct, flexible, and efficient way to communicate upcoming deals, favorable sales, and current or anticipated products to your customers. |
 | Reminders | SMS messages can be effective in notifying users who have set an appointment for a service. For example, sending an SMS message reminding a customer the day before a doctor's appointment will help minimize missed appointments, saving both you and your customers time and money. |
 | Transactional Messages | SMS messages are an efficient way to send out transactional notifications such as order confirmations and shipping information, providing them all the information they need in one convenient place. Note that legal guidelines exist that must be adhered to when sending Transactional Messages. If you are unsure of these guidelines, reach out to your internal legal team.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Requirements
 
@@ -34,7 +34,7 @@ Before you start sending SMS, there are some things you need. Refer to the follo
 | A dedicated phone number (either a Short Code or Long Code) | A dedicated phone number provided exclusively to a single brand or host. | Braze handles acquiring these numbers for you. Learn more about [short and long codes]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup/short_and_long_codes/).|
 | List of users with phone numbers | Before you can start sending messages, you must add users to your account. Additionally, you must know the approximate size of your audience.  | Users are initially added to Braze through our backend. You must pass this list to us to upload for you. Phone numbers must be formatted as a 10-digit number, as well as a country area code. Learn more about [user phone numbers]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/). |
 | [SMS keywords and responses]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/) | All base keywords must have responses attributed to it before you can begin messaging | You should list these out and send them to your Braze representative or onboarding manager during your onboarding process. View [SMS keyword templates]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/sending_phone_numbers/#short-code-application). |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Terms to know
 
@@ -42,7 +42,7 @@ Before you start sending SMS, there are some things you need. Refer to the follo
 - **Long codes:** A 10-digit code that is used to address SMS messages. Most average phone numbers are considered long codes (e.g 123-456-7891). These codes are used to address and send SMS messages.<br><br>
 - **Subscription group:** A collection of sending phone numbers (such as short codes, long codes, and/or alphanumeric sender IDs) that are used for a specific type of messaging purpose. For example, if a brand has plans to send both transactional and promotional SMS messaging, two Subscription Groups with separate pools of sending phone numbers will need to be set up within your Braze dashboard.<br><br>
 - **Message segment and character limits:** A message segment refers to how many segments your initial SMS message will be split into. Each message has a character limit that if exceeded, will cause the message to be broken into segments. Based on what encoding standards you use (UTF-2 or GSM-7), there are varying character limits. Reference our [message copy limits][2] for more information on messaging segmentation and message character limits.<br><br>
-- **Common SMS campaign metrics:** <br>*Sent*, *Sends to Carrier*, *Delivery Failure*, *Confirmed Delivery*, *Rejections*, *Opt-Out*, and *Help*. <br>For information on these metrics, refer to [SMS reporting][1]. Note that *Sends to Carrier* is deprecated, but will continue to be supported for users that already have it.
+- **Common SMS campaign metrics:** <br>*Sent*, *Sends to Carrier*, *Delivery Failure*, *Confirmed Delivery*, *Rejections*, *Opt-Out*, and *Help*. <br>For information on these and other SMS metrics, refer to [SMS reporting][1]. Note that *Sends to Carrier* is deprecated, but will continue to be supported for users that already have it.
 
 <br><br>
 
diff --git a/_docs/_user_guide/message_building_by_channel/sms/campaign/link_shortening.md b/_docs/_user_guide/message_building_by_channel/sms/campaign/link_shortening.md
index ee17cfaff29..12ed866317e 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/campaign/link_shortening.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/campaign/link_shortening.md
@@ -90,7 +90,7 @@ Link shortening is also enabled for API-only messages through the [`/messages/se
 | --------- | ---------| --------- | ----------- |
 |`link_shortening_enabled`| Optional | Boolean | Set `link_shortening_enabled` to `true` to turn on link shortening and campaign-level click tracking. To use tracking, a `campaign_id` and `message_variation_id` must be present.|
 |`user_click_tracking_enabled`| Optional | Boolean | Set `user_click_tracking_enabled` to `true` to turn on link shortening, and campaign-level and user-level click tracking. You can use the tracked data to create segments of users who clicked URLs. To use tracking, a `campaign_id` and `message_variation_id` must be present. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 For a full list of request parameters, go to [request parameters]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_messages/#request-parameters).
 
diff --git a/_docs/_user_guide/message_building_by_channel/sms/campaign/segments.md b/_docs/_user_guide/message_building_by_channel/sms/campaign/segments.md
index 57778a3ac31..bfc268cc09d 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/campaign/segments.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/campaign/segments.md
@@ -49,7 +49,7 @@ Regardless of the encoding type, each SMS message sent out by Braze has a limit
 | 1072 - 1224 characters | 8 segments |
 | 1225 - 1377 characters | 9 segments |
 | 1378 - 1530 characters | 10 segments |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% tab UCS-2 encoding %}
 | Number of characters | How many segments? |
@@ -64,7 +64,7 @@ Regardless of the encoding type, each SMS message sent out by Braze has a limit
 | 470 - 536 characters | 8 segments |
 | 537 - 603 characters | 9 segments |
 | 604 - 670 characters | 10 segments |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 {% endtab %}
 {% endtabs %}
 
diff --git a/_docs/_user_guide/message_building_by_channel/sms/keywords/keyword_handling.md b/_docs/_user_guide/message_building_by_channel/sms/keywords/keyword_handling.md
index ca5265756c8..d0cc02bfea9 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/keywords/keyword_handling.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/keywords/keyword_handling.md
@@ -39,7 +39,7 @@ The following rules apply to keywords and keyword responses:
 | Keywords | Keyword responses |
 | -------- | ----------------- |
 | - Valid UTF-8 encoded characters<br>- Maximum of 20 keywords per category total<br>- Maximum length of 34 characters<br>- Minimum length of 1 character <br>- Cannot contain spaces<br>- Required to be case insensitive and unique across the subscription group | - Cannot be blank<br>- Maximum length of 300 characters<br>- Valid UTF-8 characters |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% alert tip %}
 Interested in seeing how these keywords can be used in your campaigns and Canvases to retarget and trigger messages? Visit our [SMS retargeting]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/retargeting/) article for more information.
@@ -62,7 +62,7 @@ You can manage your own responses that are sent to users after they text in a ke
 | Keywords | Keyword responses |
 | -------- | ----------------- |
 | - Valid UTF-8 encoded characters<br>- Maximum of 20 keywords per category total<br>- Maximum length of 34 characters<br>- Minimum length of 1 character <br>- Cannot contain spaces<br>- Required to be case insensitive and unique across the subscription group | - Cannot be blank<br>- Maximum length of 300 characters<br>- Valid UTF-8 characters |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
diff --git a/_docs/_user_guide/message_building_by_channel/sms/keywords/optin_optout.md b/_docs/_user_guide/message_building_by_channel/sms/keywords/optin_optout.md
index b412539cc90..91899b24c29 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/keywords/optin_optout.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/keywords/optin_optout.md
@@ -24,7 +24,7 @@ Braze will process the following keywords automatically and update the subscript
 |Opt-in| `START`<br> `YES`<br> `UNSTOP` | Any inbound request with one of these `Opt-In` keywords will result in a subscription group state change to `subscribed`. Additionally, the pool of numbers associated with that subscription group will now be able to send an SMS message to that customer. <br><br>User will receive your defined Opt-In auto response.  |
 |Opt-out| `STOP`<br> `STOPALL`<br> `UNSUBSCRIBE`<br> `CANCEL`<br> `END`<br> `QUIT` | Any inbound request with one of these `Opt-Out` keywords will result in a subscription group state change to `unsubscribed`. Additionally, the pool of numbers associated with that subscription group will no longer be able to send an SMS message to that customer.<br><br>User will receive your defined Opt-Out auto response. |
 | Help | `HELP`<br> `INFO` | User will receive your defined Help auto response. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 Only the **exact, single-word message** will be processed (case insensitive). Keywords such as `STOP PLEASE` will be ignored unless [fuzzy opt-out][fuzzylink] is turned on.
 
diff --git a/_docs/_user_guide/message_building_by_channel/sms/keywords/sms_double_opt_in.md b/_docs/_user_guide/message_building_by_channel/sms/keywords/sms_double_opt_in.md
index 017aa40aace..99716d9dd66 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/keywords/sms_double_opt_in.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/keywords/sms_double_opt_in.md
@@ -46,7 +46,7 @@ To turn on SMS double opt-in, navigate to the **SMS Global Keywords** table in t
 | | Reply Message | This is the initial response that a user will receive after texting an opt-in keyword (for example, “Reply Y to confirm you want to receive messages from this number. Msg&Data Rates may apply.” )
 | Double Opt-In Confirmation | Keywords | These are the keywords a user can reply with to confirm their opt-in intent. At least one keyword is required. These keywords should be specified in the **Opt-In Prompt Reply Message** field.
 | | Reply Message | This is the confirmation response that a user will receive after they have explicitly confirmed their opt-in and are now messageable via SMS. The user’s subscription group status will be set to `Subscribed`.
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 When a user receives an opt-in prompt, they have 30 days to confirm their opt-in intent. If a user wants to subscribe after the 30-day window, they need to text an opt-in keyword to start the double opt-in workflow again.
 
@@ -72,7 +72,7 @@ Shopify | Users will not be entered into the SMS double opt-in workflow when the
 User Import | Users will not be entered into the SMS double opt-in workflow when their subscription status is set by User Import.
 [Preference Center]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center) | Users will automatically enter into the SMS double opt-in workflow when subscribed via a preference center.
 User Update Step | Users can be entered into the SMS double opt-in workflow when their subscription status is set via the User Update step and the optional parameter `use_double_opt_in_logic` is passed as `true`. If this parameter is omitted, users will not be entered into the SMS double opt-in workflow.
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Multi-language support
 For inbound messages, SMS double opt-in is supported for all languages defined in the subscription group. This means you can define your auto-responses in different languages and Braze will send the auto-response associated with a specific language when a matching keyword is received.
diff --git a/_docs/_user_guide/message_building_by_channel/sms/mms/about_mms.md b/_docs/_user_guide/message_building_by_channel/sms/mms/about_mms.md
index e0f550f1635..32a02a24788 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/mms/about_mms.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/mms/about_mms.md
@@ -19,7 +19,7 @@ search_rank: 2
 | --- | --- |
 | Promotions | Reach users with high-visibility SMS campaigns but also leverage the media aspect of MMS to entice buyers with what you're offering. | 
 | Re-engagement campaigns | Re-engage customers who opted in to receive SMS when all other channels fail to bring them back. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Get to know MMS
 
diff --git a/_docs/_user_guide/message_building_by_channel/sms/mms/create.md b/_docs/_user_guide/message_building_by_channel/sms/mms/create.md
index f82cb21f4e9..c6c48043e16 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/mms/create.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/mms/create.md
@@ -45,7 +45,7 @@ Creating an MMS message requires your subscription group to be configured for MM
 |--------------------------|----------------------------|
 | Size                     | 600&nbsp;KB maximum        |
 | File Types               | PNG, JPEG, GIF             |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Previewing an MMS message
 
diff --git a/_docs/_user_guide/message_building_by_channel/sms/phone_numbers/10dlc.md b/_docs/_user_guide/message_building_by_channel/sms/phone_numbers/10dlc.md
index c7cff2850e2..da2e87f527b 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/phone_numbers/10dlc.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/phone_numbers/10dlc.md
@@ -44,7 +44,7 @@ Registering with A2P 10DLC may include several types of fees:
 | Registration Fees | Nominal fees applied when registering your brand and use case across all major US networks. |
 | Secondary Vetting Fees | Brands can appeal their [Brand Trust Score](#trust-score) and request a secondary vetting process to improve their overall throughput; there is a fee associated with this process. |
 | Carrier Fees | Fees charged by carriers for outbound SMS and MMS messages sent to users after 10DLC registration. Starting October 1, 2021, carrier fees will be higher on unregistered traffic (standard long codes) than registered traffic (10DLC). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Visit the Twilio 10DLC article to check out updated [fee estimates](https://support.twilio.com/hc/en-us/articles/1260803965530-What-pricing-and-fees-are-associated-with-the-A2P-10DLC-service-).
 
@@ -61,7 +61,7 @@ The Campaign Registry (TCR) is a third-party agency that uses a reputation algor
 | High | 75-100 | 75 MPS | 75 MPS | 75 MPS |
 | Medium | 50-74 | 40 MPS | 40 MPS | 40 MPS |
 | Low | 1-49 | 4 MPS | 4 MPS | 4 MPS | 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% alert tip %}
 Companies listed in the Russel 3000 Index will be granted a high throughput and brand trust score after 10DLC registration and review. 
@@ -90,7 +90,7 @@ Depending on your use case, the trust score needed to achieve the maximum throug
 | 2FA | Any authentication of account verification, such as OTP. | 
 | Security Alerts | Notification of a compromised system. |
 | Fraud Alerts | Messaging about potentially fraudulent activity. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% tabs %}
 {% tab Declared Use Case %}
@@ -101,19 +101,19 @@ A declared use case means you have chosen one specific non-marketing use case (f
 | 75-100 | 225 MPS | 75 MPS | 75 MPS | 75 MPS |
 | 50-74	 | 120 MPS | 40 MPS | 40 MPS | 40 MPS |
 | 1-49 | 12 MPS | 4 MPS | 4 MPS | 4 MPS| 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% endtab %}
-{% tab Mixed/Marketing Use Case %}
+{% tab Mixed Marketing Use Case %}
 
-Mixed/Marketing use cases can be registered for customers who want to send messages for multiple use cases from the same set of numbers or for marketing.
+Mixed marketing use cases can be registered for customers who want to send messages for multiple use cases from the same set of numbers or for marketing.
 
 | Trust Score | Total throughput toward major US networks | AT&T | T-Mobile  | Verizon |
 | --- | ----------- | ---- | -------- | ------- |
 | 75-100 | 225 MPS | 75 MPS | 75 MPS | 75 MPS |
 | 50-74 | 120 MPS | 40 MPS | 40 MPS | 40 MPS |
 | 1-49 | 12 MPS | 4 MPS | 4 MPS | 4 MPS| 
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 {% endtab %}
 {% endtabs %}
diff --git a/_docs/_user_guide/message_building_by_channel/sms/phone_numbers/10dlc/10dlc_application.md b/_docs/_user_guide/message_building_by_channel/sms/phone_numbers/10dlc/10dlc_application.md
index dfbd031ac3f..f0b92a01964 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/phone_numbers/10dlc/10dlc_application.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/phone_numbers/10dlc/10dlc_application.md
@@ -46,7 +46,7 @@ All US carriers require the below company information for new campaign submissio
 | Full Legal Business Address (Street, City, State, Zip)        |                                                               |                                                              |
 | Company Type (private, non-profit, government, public (please provide ticker symbol)) |                                       |                                                              |
 | If public, provide your ticker symbol                         |                                                               |                                                              |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## SMS campaign information
 
@@ -72,5 +72,5 @@ We'll need to register each SMS subscription group that contains a US long code
 | Estimated Daily Volume | | Please indicate the estimated average number of messages sent per day for this particular use case/subscription group, for example, 10,000. |
 | Call to Action Checklist | | {::nomarkdown} <p>Call to Action should include the following:</p><ol><li>Product Description</li><li>Message Frequency Disclosure</li><li>Link to Complete Terms and Conditions</li><li>Link to Complete Privacy Policy</li><li>STOP keyword instructions</li><li>HELP keyword instructions</li><li>“Message and Data Rates” may apply disclosure</li></ol> {:/} |
 | Call to Action Example | | ![Example of call-to-action containing all the required details.]({{site.baseurl}}/assets/img_archive/10dlc_cta_example.png) |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
diff --git a/_docs/_user_guide/message_building_by_channel/sms/sms_laws_and_regulations.md b/_docs/_user_guide/message_building_by_channel/sms/sms_laws_and_regulations.md
index 3d356404683..0050deb01cf 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/sms_laws_and_regulations.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/sms_laws_and_regulations.md
@@ -43,7 +43,7 @@ There are the six rules you should follow:
 
 Here are some links you might need to consult as you build up your SMS campaign:
 
-- [CTIA's Messaging Principles and Best Practices for 2019](https://api.ctia.org/wp-content/uploads/2019/07/190719-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf)
+- [CTIA's Messaging Principles and Best Practices for 2023](https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf)
 - [Twilio's Guide to US SMS Compliance](https://www.twilio.com/learn/call-and-text-marketing/guide-to-us-sms-compliance)
 - [Acoustic's United States SMS compliance and resources](https://help.goacoustic.com/hc/en-us/articles/360043717414-United-States-SMS-compliance-and-resources)
 
diff --git a/_docs/_user_guide/message_building_by_channel/sms/sms_subscription_group.md b/_docs/_user_guide/message_building_by_channel/sms/sms_subscription_group.md
index b203c71e2d6..a2c0815d80f 100644
--- a/_docs/_user_guide/message_building_by_channel/sms/sms_subscription_group.md
+++ b/_docs/_user_guide/message_building_by_channel/sms/sms_subscription_group.md
@@ -21,7 +21,7 @@ There are two subscription states for SMS users: `subscribed` and `unsubscribed`
 | --------- | ---------- |
 | Subscribed | User has explicitly confirmed that they want to receive SMS from a specific subscription group. A user can be subscribed either by having their subscription state updated through the Braze subscription API or by texting an opt-in keyword response. A user must be subscribed to an SMS subscription group in order to receive an SMS. |
 | Unsubscribed | User has explicitly opt-ed out of messaging from your SMS subscription group and the sending-phone numbers inside the subscription group. They can unsubscribe by texting an opt-out keyword response or a brand can unsubscribed users through the [Braze subscription API][4]. Users unsubscribed from an SMS subscription Group will no longer receive any SMS from sending phone numbers that belong to the subscription group.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### How users' SMS subscription groups get set 
 
diff --git a/_docs/_user_guide/message_building_by_channel/webhooks/creating_a_webhook.md b/_docs/_user_guide/message_building_by_channel/webhooks/creating_a_webhook.md
index 3b244918f4f..e0f7cf04b64 100644
--- a/_docs/_user_guide/message_building_by_channel/webhooks/creating_a_webhook.md
+++ b/_docs/_user_guide/message_building_by_channel/webhooks/creating_a_webhook.md
@@ -198,7 +198,7 @@ Like other campaigns, Braze tracks the delivery of your webhook campaigns and th
 | 429 (rate limited)  | No | Yes |
 | Other 4xx (client error)  | No | No |
 | 5xx (server error)   | No | Yes |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert note %}
 For 500-level errors, Braze will retry the webhook send up to 5 times over 30 minutes using exponential backoff. For all other errors, Braze will continue to retry for up to 24 hours.
diff --git a/_docs/_user_guide/message_building_by_channel/webhooks/understanding_webhooks.md b/_docs/_user_guide/message_building_by_channel/webhooks/understanding_webhooks.md
index ff55aa5c31d..0cf92a89390 100644
--- a/_docs/_user_guide/message_building_by_channel/webhooks/understanding_webhooks.md
+++ b/_docs/_user_guide/message_building_by_channel/webhooks/understanding_webhooks.md
@@ -46,7 +46,7 @@ A webhook consists of the following three parts:
 | [HTTP method](#methods) | Like APIs, webhooks need request methods. These are given to the URL the webhook hits, and tells the endpoint what to do with the information given. There are four HTTP methods you can specify: POST, GET, PUT, and DELETE. |
 | HTTP URL | The URL address of your webhook endpoint. The endpoint is the place where you'll be sending the information that you're capturing in the webhook. |
 | Request body | This part of the webhook contains the information that you're communicating to the endpoint. The request body can be JSON key-value pairs or raw text. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### HTTP methods {#methods}
 
@@ -58,7 +58,7 @@ The following table describes the four different HTTP methods you can specify in
 | GET | This method retrieves existing information, as opposed to writing new information. This is the most common method used when asking for data from a server. For example, consider the [`/segments/list` endpoint]({{site.baseurl}}/api/endpoints/export/segments/get_segment/). If you were to make a GET request, it would return a list of your segments.
 | PUT | This method updates information on the endpoint, replacing any existing information with what's in the request body. 
 | DELETE | This method deletes the resource in the HTTP URL. 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Webhooks in Braze
 
diff --git a/_docs/_user_guide/message_building_by_channel/whatsapp/overview.md b/_docs/_user_guide/message_building_by_channel/whatsapp/overview.md
index 3b2c2f25167..943d8af3c9c 100644
--- a/_docs/_user_guide/message_building_by_channel/whatsapp/overview.md
+++ b/_docs/_user_guide/message_building_by_channel/whatsapp/overview.md
@@ -32,7 +32,7 @@ Acknowledge the following before proceeding with integration:
 | Meta Business Manager account | A Meta Business account is required to leverage this messaging channel. |
 | WhatsApp Business account | A WhatsApp Business account is required to leverage this messaging channel. |
 | WhatsApp phone number | You must acquire a phone number that meets WhatsApp's requirements for [Cloud API](https://developers.facebook.com/docs/whatsapp/cloud-api/phone-numbers) or [On-Premises API](https://developers.facebook.com/docs/whatsapp/on-premises/phone-numbers) for use of the messaging channel.  | 
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Integration
 
diff --git a/_docs/_user_guide/message_building_by_channel/whatsapp/user_subscription.md b/_docs/_user_guide/message_building_by_channel/whatsapp/user_subscription.md
index d7302edeb19..c6174660322 100644
--- a/_docs/_user_guide/message_building_by_channel/whatsapp/user_subscription.md
+++ b/_docs/_user_guide/message_building_by_channel/whatsapp/user_subscription.md
@@ -21,7 +21,7 @@ There are two subscription states for WhatsApp users: `subscribed` and `unsubscr
 | --- | --- |
 | Subscribed | User has explicitly confirmed that they want to receive WhatsApp messages from a specific company. Users can be subscribed by having their subscription state updated through the Braze subscription API or by deploying an opt-in strategy, as per WhatsApp's guidelines. |
 | Unsubscribed | User either hasn’t explicitly given consent for opt-in or their opt-in status has been explicitly removed. <br><br> Users unsubscribed from a WhatsApp subscription group will no longer receive any WhatsApp messages from sending phone numbers that belong to the subscription group. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4 role="presentation" }
 
 ### Setting users' WhatsApp subscription groups
 
diff --git a/_docs/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create.md b/_docs/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create.md
index aa8f991786f..87859258948 100644
--- a/_docs/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create.md
+++ b/_docs/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create.md
@@ -187,7 +187,7 @@ Images (JPEG and PNG) | Must be 8-bit, RGB or RGBA, and up to 5 MB for any type
 Body text | Supports variable parameters
 Footer text | Supports variable parameters 
 CTAs | See [Calls to actions](#ctas).
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 #### Calls to actions {#ctas}
 
@@ -195,11 +195,13 @@ You can add the following calls to action in your WhatsApp messages:
 
 CTA type    | Details
 ----------- |---------------- 
-Visit website | Available for message templates only. <br>One button maximum (including variable parameters).
+Visit website | One button maximum (including variable parameters).
 Call phone number | Available for message templates only. <br>One button maximum.
 Custom quick reply buttons | Three buttons maximum. 
 Marketing opt-out button | This option does not automatically update subscription statuses. <br><br>For setup instructions, see [Opt-ins & Opt-Outs]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/message_processing/opt-ins_and_opt-outs/#marketing-opt-out-selection).
-{: .reset-td-br-1 .reset-td-br-2}
+Coupon code message templates | Available for message templates only. <br>These can be opened and edited like other message templates, and are compatible with Liquid and Braze promotion codes. 
+CTA response messages  | Create a response message that includes a call to action button.
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ### Inbound messages
 
@@ -213,7 +215,7 @@ Audio| audio/aac<br>audio/mp4<br>audio/mpeg<br>audio/amr<br>audio/ogg (only Opus
 Documents | text/plain<br>application/pdf<br>application/vnd.ms-powerpoint<br>application/msword<br>application/vnd.ms-excel<br>application/vnd.openxmlformats-officedocument.wordprocessingml.document<br>application/vnd.openxmlformats-officedocument.presentationml.presentation<br>application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
 CTAs | See [Calls to actions](#ctas).
 Video | video/mp4, video/3gp<br><br>Only H.264 video codec and AAC audio codec are supported. We support videos with a single audio stream or no audio stream.
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 
 
diff --git a/_docs/_user_guide/onboarding_faq.md b/_docs/_user_guide/onboarding_faq.md
index e7e2ee857cb..e1fd1e08d17 100644
--- a/_docs/_user_guide/onboarding_faq.md
+++ b/_docs/_user_guide/onboarding_faq.md
@@ -88,7 +88,7 @@ By default, for your user to receive your messages through push, their push subs
 |Subscribed| Default push subscription state when a user profile is created in Braze. |
 |Opted-In| A user has explicitly expressed a preference to receive push notifications. Braze will automatically move a user's opt-in state to `Opted-In` if a user accepts an OS-level push prompt.<br><br>This does not apply to users on Android 12 or below.|
 |Unsubscribed| A user explicitly unsubscribed from push through your application or other methods your brand provides. By default, Braze push campaigns only target users that are `Subscribed` or `Opted-in` for push.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endapi %}
 {% api %}
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/catalogs/catalog.md b/_docs/_user_guide/personalization_and_dynamic_content/catalogs/catalog.md
index 30a77c384eb..5614c1cf40a 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/catalogs/catalog.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/catalogs/catalog.md
@@ -171,7 +171,7 @@ The following table describes the differences between the free and pro version o
 | Characters limit for item value       | Up to 5,000 characters in one value. For example, if you had a field labeled `description`, the maximum number of characters within the field is 5,000. | Up to 5,000 characters in one value. For example, if you had a field labeled `description`, the maximum number of characters within the field is 5,000. |
 | Characters limit for item column name | Up to 250 characters                                                                                                                                    | Up to 250 characters                                                                                                                                    |
 | Selections                            | Up to 30 selections per catalog                                                                                                                         | Up to 30 selections per catalog                                                                                                                         |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ### Catalog storage
 
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/connected_content/public_apis.md b/_docs/_user_guide/personalization_and_dynamic_content/connected_content/public_apis.md
index fbb18ee9493..2f6973daf7b 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/connected_content/public_apis.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/connected_content/public_apis.md
@@ -22,7 +22,7 @@ Public APIs can be subject to usage restrictions and rate limiting.  Be sure to
 | [OpenWeatherMap][7] | Provides current weather data, 5 and 16 day forecast, and historical data. |
 | [NYT Article Search][8] | Provides NYT article data which includes headline, topic, URL, date, abstract, etc. |
 | [The Guardian API][9] | Provides Guardian article data which includes headline, topic, URL, date, abstract, etc.|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Events and ticketing
 
@@ -33,14 +33,14 @@ Public APIs can be subject to usage restrictions and rate limiting.  Be sure to
 | [Eventbrite][19] | Provides data on a variety of public events. |
 | [Eventful][20] | Provides data on a variety of public events |
 | [Ticketmaster][38] | Provides data on public events, venues, and prices |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Food and drink
 
 |  API  | Description |
 | --------- | --- |
 | [BreweryDB][40] | Provides information on breweries, beers, and beer events. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Finance
 
@@ -48,7 +48,7 @@ Public APIs can be subject to usage restrictions and rate limiting.  Be sure to
 | --------- | --- |
 | [Barchart OnDemand][36] | Provides a variety of stock, futures, and foreign exchange data. |
 | [CoinDesk][37] | Provides a variety of cryptocurrency data. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Health
 
@@ -57,7 +57,7 @@ Public APIs can be subject to usage restrictions and rate limiting.  Be sure to
 | [AirVisual][42] | Provides Air quality and weather data. |
 | [Nutritionix Worlds][43] | Provides verified nutrition data. |
 | [USDA Nutrients][45] | Provides access to the National Nutrient Database. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Music
 
@@ -68,14 +68,14 @@ Public APIs can be subject to usage restrictions and rate limiting.  Be sure to
 | [Bandsintown][13] | Provides local concert information and recommends live music events. |
 | [Songkick][22] | Provides live music information with artists, venues, locations, etc. |
 | [Discogs][21] | Provides information on artists, labels, and recordings. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Product information
 
 |	 API 	| Description |
 | --------- | --- |
 | [eBay][15] | Provides live eBay data including item data, popular searches, and more. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 ## Miscellaneous
 
@@ -85,7 +85,7 @@ Public APIs can be subject to usage restrictions and rate limiting.  Be sure to
 | [Clearbit][27] | Provides company logo images. |
 | [London Unified][28] and [NYC MTA][29] | Provide real-time public transit data including line statuses, arrival times, etc. |
 | [Sunrise and Sunset][39] | Provides Sunset and sunrise times for a given latitude and longitude. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 [7]: http://openweathermap.org/api
 [8]: https://developer.nytimes.com/docs/articlesearch-product/1/overview
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/key_value_pairs.md b/_docs/_user_guide/personalization_and_dynamic_content/key_value_pairs.md
index 5d29c43fb33..c5b4d257ef5 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/key_value_pairs.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/key_value_pairs.md
@@ -32,7 +32,7 @@ Apple Push Notification service (APNs) supports setting alert preferences and se
 | badge             | number                      | Governs the number that is displayed as the badge on the app icon                                                                                                                              |
 | sound             | string                      | The name of the sound file to play as an alert; must be in the app's bundle or ```Library/Sounds``` folder                                                                                    |
 | content-available | number                      | Input values of 1 signal to the app the availability of new information upon launch or session resumption |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 
 ##### Alert properties library
@@ -47,7 +47,7 @@ Apple Push Notification service (APNs) supports setting alert preferences and se
 | loc-key        | string or null           | A key that sets the notification message for the current localization from the ```Localizable.strings``` file                                  |
 | loc-args       | array of strings         | String values that can appear in place of the localization format specifiers in loc-key                                                       |
 | launch-image   | strings                  | The name of an image file in the app bundle you wish to be used as the launch image when users tap the action button or move the action slide |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 The Braze message composer automatically handles the creation of the following keys: **alert** and **its properties**, **content-available**, **sound**, and **category**. 
 
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid.md
index a007bbe5e91..b5e47ac2a6e 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid.md
@@ -55,14 +55,14 @@ For example, you can retrieve a custom attribute from a user profile that is an
 Liquid templating language supports the use of objects, tags, and filters.
 
 - [**Objects**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/) allow you to insert personalized attributes into your messages.
-- [**Tags**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/) allow you to insert data into messaging and use conditional logic to send messages if outlines conditions are met. For example, you can use tags to include intelligent logic, such as "if" statements, in your campaigns.
-- [**Filters**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/filters/) allow you to reformat personalized attributes and dynamic content. For example, you could convert a timestamp, such as *2016-09-07 08:43:50 UTC*, into a date, such as *September 7, 2016*.
+- [**Tags**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/) allow you to insert data into messaging and use conditional logic to send messages if certain conditions are met. For example, you can use tags to include intelligent logic, such as "if" statements, in your campaigns.
+- [**Filters**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/filters/) allow you to reformat personalized attributes and dynamic content. For example, you could use the [`date` filter]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/filters/#date-filter) to convert a timestamp, such as *2016-09-07 08:43:50 UTC*, into a date, such as *September 7, 2016*.
 
 {% alert warning %}
-Braze does not currently support 100% of Shopify's Liquid, only certain portions which we have attempted to outline in our documentation. We highly recommend testing all messages using Liquid before sending them to reduce the risk of errors or using unsupported Liquid.
+Braze currently doesn't support 100% of Shopify's Liquid, only certain portions which we have attempted to outline in our documentation. We highly recommend testing all messages using Liquid before sending them to reduce the risk of errors or using unsupported Liquid.
 {% endalert %}
 
-### Liquid 5
+### Liquid 5 support
 
 Braze supports Liquid up to and including **Liquid 5 from Shopify**. Liquid implementation supports syntax personalization tag types and whitespace control. For more information on specific tags, refer to [syntax tags]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#syntax-tags).
 
@@ -74,18 +74,21 @@ The following new array and math filters are available for use in your Liquid as
 - `sort_natural`
 - `where`
 
-Refer to our [Filters]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/filters/) article for definitions.
+Refer to [Filters]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/filters/) for definitions.
 
 ### Liquid updates
 
+#### Color labels
+
 Each Liquid element corresponds to a color, allowing you to differentiate your Liquid at-a-glance in your Liquid editor.
 
 ![]({% image_buster /assets/img/liquid_color_code.png %})
 
-You can also leverage predicative Liquid for custom attributes, attribute names, and more as you build your personalized messages.
+#### Predictive Liquid
 
-![]({% image_buster /assets/img/liquid_auto_complete.gif %}){: style="max-width:70%;"}
+You can also leverage predictive Liquid for custom attributes, attribute names, and more as you build your personalized messages.
 
+![]({% image_buster /assets/img/liquid_auto_complete.gif %}){: style="max-width:70%;"}
 
 ## Terms to know
 
@@ -95,12 +98,12 @@ These terms are reinterpreted from [**Shopify's documentation**](https://shopify
 
 | Term | Definition | Example |  
 |---|---|---|
-| Liquid | An commonly-used, customer-facing template language created by Shopify and written in Ruby; used to load/pull dynamic content. | `{{${first_name}}}` will insert a user's first name into a message. |
+| Liquid | A commonly-used, customer-facing template language created by Shopify and written in Ruby that is used to load and pull dynamic content. | `{{${first_name}}}` will insert a user's first name into a message. |
 | Object | A denotation of a variable and location of the intended variable name that tells Liquid where to show content in the message. | `{{${city}}}` will insert a user's city into a message. |
-| Conditional logic tag | Tags create logic and control the flow of message content. In Braze, conditional logic tags are used to create exceptions and variations in messages based on certain, predefined criteria. | ```{% if ${language} == 'en' %}``` will trigger your message in a designated way in the event that a user has designated "English" as their language. |
-| Filters | Used to change, narrow, or reformat the output of the Liquid object. It is often used to create mathematical operations. | ```{{"Big Sale" | upcase}}``` will cause the words "Big Sale" to appear as "BIG SALE" in the message. |
+| Conditional logic tag | Used to create logic and control the flow of message content. In Braze, conditional logic tags are used to create exceptions and variations in messages based on certain, predefined criteria. | ```{% if ${language} == 'en' %}``` will trigger your message in a designated way in the event that a user has designated "English" as their language. |
+| Filters | Used to change, narrow, or reformat the output of the Liquid object. It's often used to create mathematical operations. | ```{{"Big Sale" | upcase}}``` will cause the words "Big Sale" to appear as "BIG SALE" in the message. |
 | Operators | Used in messages to create dependencies or criteria that can affect which message your user receives. | If a user meets the defined criteria in a message tagged with `{% custom_attribute.${Total_Revenue} > 0%}`, they will receive the message. If not, they will receive another designated message (or not), depending on what you set. |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endraw %}
 
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/aborting_messages.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/aborting_messages.md
index 9baffceef57..3350cf4e8b5 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/aborting_messages.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/aborting_messages.md
@@ -61,6 +61,10 @@ You can also have the abort message log something to your Message Activity Log b
 
 ![Message error log in the Developer Console with an abort message of "language was nil".][26]
 
+## Query for abort messages
+
+You can use [Query Builder]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/) or your own data warehouse, if it's connected to Braze, to query for specific abort messages that are triggered when Liquid logic causes a message to abort.
+
 [15]: {% image_buster /assets/img_archive/liquid_abort.png %}
 [26]: {% image_buster /assets/img_archive/developer_console.png %}
 [31]:https://docs.shopify.com/themes/liquid/tags/variable-tags
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters.md
index 0c55a3c5a1e..552e49b9b5f 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters.md
@@ -8,6 +8,8 @@ description: "This reference article lists advanced filters, examples, and how t
 
 # Advanced filters
 
+> This reference article provides an overview of advanced filters in Liquid and how they can be used.
+
 ## Encoding filters
 
 {% raw %}
@@ -21,7 +23,7 @@ description: "This reference article lists advanced filters, examples, and how t
 `hmac_sha1_base64` | Returns hmac-sha1 signature, encoded as a base64 string | `{{'hey' | hmac_sha1_base64: 'secret_key'}}` | KjlpvtJb/u+wCspAY+uVkLTfjw4= |
 `hmac_sha256_hex` | Returns hmac-sha256 signature, encoded as a hex string | `{{'hey' | hmac_sha256_hex: 'secret_key'}}` | 8df897f8da3d7992fe57c8dbc6f27578cfbf2dcc4d0fbb4000b8c924841d508e |
 `hmac_sha256_base64` | Returns hmac-sha256 signature, encoded as a base64 string | `{{'hey' | hmac_sha256_base64: 'secret_key'}}` | jfiX+No9eZL+V8jbxvJ1eM+/LcxND7tAALjJJIQdUI4= |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## URL filters
 
@@ -30,7 +32,7 @@ description: "This reference article lists advanced filters, examples, and how t
 | `url_escape` | Identifies all characters in a string that are not allowed in URLS, and replaces the characters with their escaped variants | `{{'hey<>hi' | url_escape}}` | hey%3C%3Ehi |
 | `url_param_escape` | Replaces all characters in a string that are not allowed in URLs with their escaped variants, including the ampersand (&) | `{{'hey<&>hi' | url_param_escape}` | hey%3C%26%3Ehi |
 | `url_encode` | Encodes a string that is URL friendly | `{{ 'google search' | url_encode }}` | google+search |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% endraw %}
 {% alert tip %}
@@ -49,7 +51,7 @@ The `assign` tag can be combined with HTML to save you time and effort when crea
 | filter name | filter description |
 |---|---|---|---|
 | `property_accessor` | Takes a hash and hash key and returns the value in that hash at that key |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 **Example hash:** `{"a" => 42, "b" => 0}`
 **Example input:** `{{hash | property_accessor: 'a'}}`
@@ -70,14 +72,14 @@ There is no way to instantiate a hash as a variable (such as an expression) in L
 | filter name | filter description | example input | example output |
 |---|---|---|---|
 | `number_with_delimiter` | Formats a number with commas | `{{ 123456 | number_with_delimiter }}` | 123,456 |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## JSON escape / string escape filter
 
 | filter name | filter description |
 |---|---|---|---|
 | `json_escape` | Escapes any special characters in a string (such as double quote `""` and backslash '\'). |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 This filter should always be used when personalizing a string in a JSON dictionary and is useful for webhooks in particular.
 {% endraw %}
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras.md
index 5113e55f2ee..ee960f75739 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras.md
@@ -8,13 +8,13 @@ alias: "/message_extras_tag/"
 
 # Message extras Liquid tag
 
-> Using the `message_extras` Liquid tag, you can annotate your send events with dynamic data from Connected Content, Catalogs, custom attributes (such as language, country), Canvas entry properties, or other data sources.
+> Use the `message_extras` Liquid tag to annotate your send events with dynamic data from Connected Content, Catalogs, custom attributes (such as language, country), Canvas entry properties, or other data sources.
 
 The `message_extras` Liquid tag appends key-value pairs to the corresponding send event in Currents and Snowflake Data Sharing. 
 
 To send dynamic or extra data back to your Currents or Snowflake Data Sharing send event, insert the proper Liquid tag into your message body. 
 
-The following is an example of the standard Liquid tag format for `message_extras`:
+Here's an example of the standard Liquid tag format for `message_extras`:
 
 {% raw %}
 ```liquid
@@ -22,21 +22,21 @@ The following is an example of the standard Liquid tag format for `message_extra
 ```
 {% endraw %}
 
-You can add these tags as needed for your key-value pairs in the message body. However, the length of all keys and values should not exceed 1&nbsp;KB. In Currents and Snowflake Data Sharing, you'll see a new event field called `message_extras` for your send events. This will generate a JSON serialized string in one field.
+You can add these tags as needed for your key-value pairs in the message body. However, the length of all keys and values shouldn't exceed 1&nbsp;KB. In Currents and Snowflake Data Sharing, you'll see a new event field called `message_extras` for your send events. This will generate a JSON serialized string in one field.
 
 ## Supported channels
 
 The `message_extras` tag is supported for all message types with a send event, along with in-app message impression events. Using `message_extras` with in-app messages requires certain [minimum SDK versions](#iam-sdk) to be met.
 
-## How to use
+## How to use the `message_extras` tag
 
-1. In the message body for the channel, input the `message_extras` Liquid tag. Or, you can use the **Add Personalization** modal and select **Message Extras** for the personalization type. <br>![The Add Personalization modal with Message Extras selected as the personalization type.][1]{: style="max-width:70%;"}
+1. In the message body for the channel, enter the `message_extras` Liquid tag. Or, you can use the **Add Personalization** modal and select **Message Extras** for the personalization type. <br>![The Add Personalization modal with Message Extras selected as the personalization type.][1]{: style="max-width:70%;"}
 2. Enter the [key-value pair]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/key_value_pairs/) for each `message_extras` tag. <br>![An example of key-value pairs for the message extras tag. The title field reads "Your New Favorites." The message reads key-value pairs for the message extras tag and the following sentence: "We're excited to bring you a side selection of fresh and exciting products that are sure to become your new go-to favorites"][2]{: style="max-width:70%;"}
 3. After your campaign or Canvas has been sent, Braze will attach the dynamic data at the send time via the Currents or Snowflake Data Sharing send events to the `message_extras` field.
 
 ## Checking syntax
 
-Any other input that doesn't match the aforementioned tag standard may fail to pass to Currents or Snowflake. Check that your syntax or formatting doesn't include any of the following:
+Any other input that doesn't match the tag standard discussed above may fail to pass to Currents or Snowflake. Check that your syntax or formatting doesn't include any of the following:
 
 - Non-existent, empty, or mistyped delimiters
 - Duplicate keys (Braze will default to sending the key-value pair that is encountered first)
@@ -56,7 +56,7 @@ Any other input that doesn't match the aforementioned tag standard may fail to p
 
 #### How can I associate the message_extras field in the send events to my engagement events like opens and clicks? 
 
-A `dispatch_id` is generated and provided in your send events, which can be used as a unique identifier to tie to specific click, open or delivered events. You will be able to utilize and query this field in Currents or Snowflake. Learn more about [`dispatch_id` behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+A `dispatch_id` is generated and provided in your send events, which can be used as a unique identifier to tie to specific click, open or delivered events. You'll be able to use and query this field in Currents or Snowflake. Learn more about [`dispatch_id` behavior]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
 
 #### Can I use message_extras with in-app messages? {#iam-sdk}
 
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/conditional_logic.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/conditional_logic.md
index bf4bd6c0f8d..72ef773ed60 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/conditional_logic.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/conditional_logic.md
@@ -8,7 +8,9 @@ description: "This reference article covers how tags can and should be used in y
 
 # Conditional messaging logic
 
-> [Tags][7] allow you to include programming logic in your messaging campaigns. Tags can be used for executing conditional statements as well as for advanced use cases, like assigning variables or iterating through a block of code.
+> [Tags][7] allow you to include programming logic in your messaging campaigns. Tags can be used for executing conditional statements as well as for advanced use cases, like assigning variables or iterating through a block of code. <br><br>This page covers how tags can and should be used, such as how to account for null, nil, and blank attribute values, and how to reference custom attributes.
+
+## Formatting tags
 
 {% raw %}
 A tag must be wrapped in `{% %}`.
@@ -65,7 +67,7 @@ In this example, we use tags with "if", "elsif" and "else" statements to deliver
 {% if ${language} == 'en' %}
 This is a message in English from Braze!
 ```
-If the customer's language is English, the first condition is met and the customer will receive a message in English.
+If the user's language is English, the first condition is met and the user will receive a message in English.
 
 ```liquid
 {% elsif ${language} == 'es' %}
@@ -74,21 +76,20 @@ Este es un mensaje en español de Braze !
 这是一条来自Braze的中文消息。
 ```
 
-You can specify as many conditional statements as you'd like. Subsequent conditions will be checked if the previous conditions are not met. In this example, if a customer's device is not set to English this code will check to see if the customer's device is set to Spanish or Chinese. If the customer's device meets one of these conditions, the customer will receive a message in the relevant language.
+You can specify as many conditional statements as you'd like. Subsequent conditions will be checked if the previous conditions are not met. In this example, if a user's device is not set to English this code will check to see if the user's device is set to Spanish or Chinese. If the user's device meets one of these conditions, the user will receive a message in the relevant language.
 
 ```liquid
 {% else %}
-This is a message from Braze! This is going to go to anyone who did not match the other specified languages!
+This is a message from Braze! This is going to go to anyone who didn't match the other specified languages!
 ```
 
-You have the option to include an `{% else %}` statement in your conditional logic. If none of the conditions that you set are met, the `{% else %}`  statement specifies the message that should send. In this case, we default to English if a customer's language is not English, Spanish, or Chinese.
+You have the option to include an `{% else %}` statement in your conditional logic. If none of the conditions that you set are met, the `{% else %}`  statement specifies the message that should send. In this case, we default to English if a user's language is not English, Spanish, or Chinese.
 
 ```liquid
 {% endif %}
 ```
 
-The `{% endif %}`  tag signals that you've finished your conditional logic. You must include the
-`{% endif %}`  tag in any message with conditional logic. If you do not include an `{% endif %}`  tag in your conditional logic, you'll get an error as Braze will be unable to parse your message.
+The `{% endif %}` tag signals that you've finished your conditional logic. You must include the `{% endif %}` tag in any message with conditional logic. If you don't include an `{% endif %}` tag in your conditional logic, you'll get an error as Braze will be unable to parse your message.
 
 {% endraw %}
 
@@ -98,9 +99,9 @@ Conditional logic is a useful way to account for attribute values that aren't se
 
 ### Null and nil attribute values
 
-A null or nil value occurs when the value of a custom attribute has not been set. For example, a user who has not yet set their first name will not have a first name logged in Braze.
+A null or nil value occurs when the value of a custom attribute hasn't been set. For example, a user who hasn't yet set their first name won't have a first name logged in Braze.
 
-In some circumstances, you may wish to send a completely different message to users who have a first name set and users who do not have a first name set.
+In some circumstances, you may wish to send a completely different message to users who have a first name set and users who don't have a first name set.
 
 The following tag allows you to specify a message for users with a null "first name" attribute:
 
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/filters.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/filters.md
index c3bc1642a71..d0d220752d0 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/filters.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/filters.md
@@ -10,10 +10,16 @@ description: "This reference page lists filters that can be used to reformat sta
 
 > This reference article provides an overview of filters in Liquid, and covers which filters are supported by Braze. Looking for ideas on how you can use these filters? Check out our [Liquid use case library]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases/).
 
-{% raw %}
-
 Filters are how you can modify the output of numbers, strings, variables, and objects in Liquid. You can use filters to reformat static or dynamic text, such as changing a string from lowercase to uppercase or to perform mathematical operations, like addition or division.
 
+{% alert important %}
+Braze does not support all Liquid filters from Shopify. This page attempts to outline the Liquid filters that Braze has tested, but it may not be a complete list. Always test your Liquid before sending out any messages. <br><br>If you have any questions about a filter that is not listed here, reach out to your customer success manager.
+{% endalert %}
+
+## Filter syntax
+
+{% raw %}
+
 Filters must be placed within an output tag `{{ }}` and are denoted by a pipe character `|`.
 
 {% endraw %}
@@ -37,6 +43,8 @@ BIG SALE
 
 In this example, `Big Sale` is a string, and `upcase` is the filter being applied.
 
+### Syntax for multiple filters
+
 You can use multiple filters on one output. They are applied from left to right.
 
 {% tabs local %}
@@ -56,11 +64,6 @@ SALE
 {% endtab %}
 {% endtabs %}
 
-{% alert important %}
-Braze does not support all Liquid filters from Shopify. This page attempts to outline the Liquid filters that Braze has tested, but it may not be a complete list. Always test your Liquid before sending out any messages. 
-<br><br>If you have any questions about a filter that is not listed here, reach out to your customer success manager.
-{% endalert %}
-
 ## Array filters
 
 Array filters are used to change the output of arrays.
@@ -80,7 +83,7 @@ Array filters are used to change the output of arrays.
 | [sort_natural][1.11] | Sorts the items in an array in case-insensitive alphabetical order.                                                | ✅  Yes   |
 | [uniq][1.12]         | Removes any duplicate instances of elements in an array.                                                           | ✅  Yes   |
 | [where][1.13]        | Filters an array to only include items with a specific property value.                                             | ✅  Yes   |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Color filters
 
@@ -92,7 +95,7 @@ Array filters are used to change the output of arrays.
 
 ## Math filters
 
-Math filters allow you to perform mathematical operations. Remember—if you use multiple filters on one output, they are applied from left to right.
+Math filters allow you to perform mathematical operations. If you use multiple filters on one output, they will be applied from left to right.
 
 | Filter  | Definition      | Supported |
 | :------ |:----------------| :-------- |
@@ -107,7 +110,7 @@ Math filters allow you to perform mathematical operations. Remember—if you use
 | [round][4.9]      | Rounds the output to the nearest integer or specified number of decimals.  | ✅  Yes   |
 | [times][4.10]     | Multiplies an output by a number.       | ✅  Yes   |
 | [modulo][4.11]    | Divides an output by a number and returns the remainder.   | ✅  Yes   |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert tip %}
 When dividing integers (whole numbers) by integers in Liquid, if the answer is a float (number with a decimal), Liquid will automatically round down to the nearest integer. However, dividing integers by floats will always give you a float. That means you can turn your integers into a float (1.0, 2.0, 3.0) to return a float.
@@ -131,13 +134,18 @@ This example wouldn't work because you can't reference multiple custom attribute
 1. One to assign the custom attribute to a variable,
 2. One to perform the addition.
 
-For example, let's say we want to calculate a user's current balance by adding their gift card balance and rewards balance. First, use the `assign` tag to substitute the custom attribute of `current_rewards_balance` with the term "balance". This means that you now have a variable named `balance`, which you can manipulate.
+#### Use case: Calculate current balance
+
+Let's say we want to calculate a user's current balance by adding their gift card balance and rewards balance.
+
+1. Use the `assign` tag to substitute the custom attribute of `current_rewards_balance` with the term "balance". This means that you now have a variable named `balance`, which you can manipulate.
 
 ```liquid
 {% assign balance = {{custom_attribute.${current_rewards_balance}}} %}
 ```
 
-Next, use the `plus` filter to combine each user's gift card balance with their rewards balance, signified by the `{{balance}}` object. 
+{: start="2"}
+2. Use the `plus` filter to combine each user's gift card balance with their rewards balance, signified by the `{{balance}}` object. 
 {% endraw %}
 {% tabs local %}
 {% tab Input %}
@@ -166,7 +174,7 @@ If you're updating a user on their purchase, an account balance, or anything reg
 | [money][5.1]      | Formats numbers to ensure that decimals are in the proper place, and zeros are not dropped off the end of any numbers.   | ✅  Yes   |
 | [money_with_currency][5.2]    | Formats numbers with the currency symbol.     | ⛔  No    |
 | [money_without_currency][5.4]     | Formats numbers without the currency symbol.      | ⛔  No    |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 {% alert important %}
 To properly format a number with the `money` filter, remove any commas in the number and add the `plus: 0` filter before the `money` filter. For example, see the following Liquid:<br><br>
@@ -181,11 +189,11 @@ To properly format a number with the `money` filter, remove any commas in the nu
 ### Shopify money filter versus Braze money filter
 
 {% alert warning %}
-The behavior of the Shopify `money` filter differs from how it is used in Braze. Refer to the following examples for an accurate depiction of the expected behavior.
+The behavior of the Shopify `money` filter differs from how it's used in Braze. Refer to the following examples for an accurate depiction of the expected behavior.
 {% endalert %}
 
 {% raw %}
-In the event you are inputting a custom attribute (like `account_balance`), you should always use the `money` filter to ensure that your decimals are in the proper place, and zeros are not dropped off the end of any numbers:
+In the event you are inputting a custom attribute (like `account_balance`), you should always use the `money` filter to put your decimals in the proper place and prevent zeros from dropping off the end of any numbers:
 
 ```liquid
 ${{custom_attribute.${account_balance} | money}}
@@ -196,9 +204,9 @@ ${{custom_attribute.${account_balance} | money}}
 | :------------------------------------------ | :------------------------------------------ |
 | ![With money filter][1]                     | ![Without money filter][2]                  |
 | Where `account_balance` is input at `17.8`. | Where `account_balance` is input at `17.8`. |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-The `money` filter in Braze differs from Shopify in that it does not automatically apply decimal points according to a preset setting. For example, take the following scenario where `rewards_redeemed` contains a value of `145`:
+The `money` filter in Braze differs from Shopify because it doesn't automatically apply decimal points according to a preset setting. For example, take the following scenario where `rewards_redeemed` contains a value of `145`:
 
 {% tabs local %}
 {% tab Input %}
@@ -241,7 +249,7 @@ $1.45
 String filters are used to manipulate the outputs and variables of strings. Strings are a combination of alphanumeric characters and must be wrapped in straight quotes.
 
 {% alert note %}
-Straight quotes are different from curly quotes in Liquid. Be careful when copying and pasting Liquid from a text editor into Braze, as curly quotes will cause errors with your Liquid. If you are writing your Liquid directly into Braze, straight quotes will be applied automatically.
+Straight quotes are different from curly quotes in Liquid. Be careful when copying and pasting Liquid from a text editor into Braze, as curly quotes will cause errors with your Liquid. If you're writing your Liquid directly into Braze, straight quotes will be applied automatically.
 {% endalert %}
 
 | Filter          | Description     | Supported |
@@ -274,11 +282,11 @@ Straight quotes are different from curly quotes in Liquid. Be careful when copyi
 | [truncate][6.26]    | Truncates a string down to the number of characters passed as the first parameter. An ellipsis (...) is appended to the truncated string and is included in the character count.    | ✅  Yes   |
 | [truncatewords][6.27]   | Truncates a string down to the number of words passed as the first parameter. An ellipsis (...) is appended to the truncated string.    | ✅  Yes   |
 | [upcase][6.28]   | Converts a string into uppercase.      | ✅  Yes   |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## Additional filters
 
-The following general filters serve many different purposes, including formatting or converting content.
+The following general filters serve many purposes, including formatting or converting content.
 
 | Filter                | Description                                                                                                                      | Supported |
 | --------------------- | -------------------------------------------------------------------------------------------------------------------------------- | :-------- |
@@ -286,8 +294,8 @@ The following general filters serve many different purposes, including formattin
 | [default][7.2]        | Sets a default value for any variable with no assigned value. Can be used with strings, arrays, and hashes.      | ✅  Yes   |
 | [format_address][7.3] | Formats an address to print the elements of the address in order according to their locale.        | ⛔  No    |
 | [highlight][7.4]      | Wraps words inside search results with an HTML `<strong>` tag with the class highlight if it matches the submitted search terms. | ⛔  No    |
-| `time_zone`             | Refer to [Time Zone Filter](#time-zone-filter) for more.     | ✅  Yes   |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+| `time_zone`             | Refer to [Time Zone Filter](#time-zone-filter).     | ✅  Yes   |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 You can find more supported filters, such as encoding and URL filters, on our [Advanced Filters]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/) page.
 
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/operators.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/operators.md
index a810b6425ff..0cc9b31c3c2 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/operators.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/operators.md
@@ -8,7 +8,9 @@ description: "This reference page notes the operators that Liquid supports, as w
 
 # Operators
 
-Liquid supports many [operators][25] that can be used in your conditional statements. Note that parentheses are invalid characters in Liquid and prevents your tags from working.
+> Liquid supports many [operators][25] that can be used in your conditional statements. This page covers the operators that Liquid supports and provides use cases of how you can use them in your messages.
+
+This table lists the operators that are supported. Note that parentheses are invalid characters in Liquid and prevents your tags from working.
 
 |   Syntax| Operator Description|
 |---------|-----------|
@@ -21,13 +23,13 @@ Liquid supports many [operators][25] that can be used in your conditional statem
 | or | condition A or condition B|
 | and | condition A and condition B|
 | contains | checks to see if a string or string array contains a string|
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
-## Operator examples
+## Use cases
 
-Here are some examples of how these operators could be helpful for your marketing campaigns:
+Here are some use cases of how these operators could be helpful for your marketing campaigns:
 
-### Choose message via integer custom attribute
+### Choose message with an integer custom attribute
 
 {% raw %}
 ```liquid
@@ -41,7 +43,7 @@ Buy now! Would 5% off convince you?
 
 ![][13]{: width="100%"}
 
-In this example, if a customer's "Total Spend" custom attribute is greater than `0`, they will get the message:
+In this use case, if a customer's "Total Spend" custom attribute is greater than `0`, they will get the message:
 
 ```
 Thanks for purchasing! Here's another 10% off!
@@ -52,7 +54,7 @@ If a customer's "Total Spend" custom attribute does not exist or is equal to `0`
 Buy now! Would 5% off convince you?
 ```
 
-### Choose message via string custom attribute
+### Choose message with a string custom attribute
 
 {% raw %}
 
@@ -68,7 +70,7 @@ Hey! Get in here and play this Game!
 
 ![][14]
 
-In this example, if you have played a certain game, you'll receive the following message:
+In this use case, if you have played a certain game, you'll receive the following message:
 
 ```
 You played our Game! We're so happy!
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/setting_default_values.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/setting_default_values.md
index f4e4ea25e46..dc062b100b0 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/setting_default_values.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/setting_default_values.md
@@ -10,7 +10,9 @@ description: "This reference article cover how to set default fallback values fo
 
 {% raw %}
 
-> Default fallback values can be set for any personalization attribute that you use in your messages. 
+> Default fallback values can be set for any personalization attribute that you use in your messages. This article covers how default values work, how to set them up, and how to use them in your messages.
+
+## How they work
 
 Default values can be added by specifying a [Liquid Filter][3] (use `|` to distinguish the filter inline, as shown) with the name "default."
 
@@ -18,7 +20,7 @@ Default values can be added by specifying a [Liquid Filter][3] (use `|` to disti
 | default: 'Insert Your Desired Default Here'
 ```
 
-If a default value is not provided and the field is missing or not set on the user, the field will be blank in the message.
+If a default value isn't provided and the field is missing or not set on the user, the field will be blank in the message.
 
 The following example shows the correct syntax for adding a default value. In this case, the words "Valued User" will replace the attribute `{{ ${first_name} }}` if a user's `first_name` field is empty or unavailable.
 
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags.md
index 7ff7909a009..4c8d89ac9c6 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags.md
@@ -10,11 +10,13 @@ search_rank: 1
 
 > This reference article covers a complete list of supported Liquid personalization tags.
 
+## Summary of supported tags
+
 As a convenience, a summary of supported personalization tags are provided. For more detail on each kind of tag and best practices, continue reading.
 
 {% raw %}
 
-| Personalization Tag Type | Tags |
+| Personalization tag type | Tags |
 | -------------  | ---- |
 | Standard (Default) Attributes | `{{${city}}}` <br> `{{${country}}}` <br> `{{${date_of_birth}}}` <br> `{{${email_address}}}` <br> `{{${first_name}}}` <br> `{{${gender}}}` <br> `{{${language}}}` <br> `{{${last_name}}}` <br> `{{${last_used_app_date}}}` <br> `{{${most_recent_app_version}}}` <br> `{{${most_recent_locale}}}` <br> `{{${most_recent_location}}}` <br> `{{${phone_number}}}` <br> `{{${time_zone}}}` <br> `{{${user_id}}}` <br> `{{${braze_id}}}` <br> `{{${random_bucket_number}}}` <br> `{{subscribed_state.${email_global}}}` <br> `{{subscribed_state.${subscription_group_id}}}` |
 | Device Attributes | `{{most_recently_used_device.${carrier}}}` <br> `{{most_recently_used_device.${id}}}` <br> `{{most_recently_used_device.${idfa}}}` <br> `{{most_recently_used_device.${model}}}` <br> `{{most_recently_used_device.${os}}}` <br> `{{most_recently_used_device.${platform}}}` <br> `{{most_recently_used_device.${google_ad_id}}}` <br> `{{most_recently_used_device.${roku_ad_id}}}` <br> `{{most_recently_used_device.${foreground_push_enabled}}}`|
@@ -30,21 +32,21 @@ As a convenience, a summary of supported personalization tags are provided. For
 | Canvas Entry Properties| `{{canvas_entry_properties}}` |
 | Custom Attributes <br> (These are custom to your workspace.) | `{{custom_attribute.${your_custom_attribute}}}` |
 | [API trigger Properties][75] |`{{api_trigger_properties}}` |
-{: .reset-td-br-1 .reset-td-br-2}
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endraw %}
 
 Refer to this help article to learn more about [how some of these attributes differ across sources in Braze]({{site.baseurl}}/help/help_articles/api/attribute_name_id_across_sources/).
 
 {% alert important %}
-Campaign, Card, and Canvas attributes are only supported in their corresponding messaging templates (for example, `dispatch_id` is not available in in-app message campaigns).
+Campaign, Card, and Canvas attributes are only supported in their corresponding messaging templates (for example, `dispatch_id` isn't available in in-app message campaigns).
 {% endalert %}
 
-#### Canvas and campaign tag differences 
+### Canvas and campaign tag differences 
 
 The behavior for the following tags differs between Canvas and campaigns:
 {% raw %}
-- `dispatch_id` differs between Canvas and campaigns because Braze treats Canvas steps as triggered events, even when they are "scheduled" (except for Entry Steps, which can be scheduled). To learn more, refer to [Dispatch ID behavior][50].
+- `dispatch_id` behavior differs because Braze treats Canvas steps as triggered events, even when they are "scheduled" (except for Entry Steps, which can be scheduled). To learn more, refer to [Dispatch ID behavior][50].
 - Using the `{{campaign.${name}}}` tag with Canvas will display the Canvas component name. When using this tag with campaigns, it will display the campaign name.
 {% endraw %}
 
@@ -57,7 +59,7 @@ You can template in the following attributes for the user's most recent device a
 |Tag | Description |
 |---|---|
 |`{{most_recently_used_device.${browser}}}` | The most recently used browser on the user's device. Examples include "Chrome" and "Safari". |
-|`{{most_recently_used_device.${id}}}` | This is the Braze device identifier. On iOS, this can be the Apple Identifier for Vendor (IDFV) or a UUID. For Android and other platforms it is a randomly generated UUID. |
+|`{{most_recently_used_device.${id}}}` | The Braze device identifier. On iOS, this can be the Apple Identifier for Vendor (IDFV) or a UUID. For Android and other platforms it is a randomly generated UUID. |
 | `{{most_recently_used_device.${carrier}}}` | The most recently used device's telephone service carrier, if available. Examples include "Verizon" and "Orange". |
 | `{{most_recently_used_device.${ad_tracking_enabled}}}` | If the device has ad tracking enabled or not. This is a boolean value (`true` or `false`). |
 | `{{most_recently_used_device.${idfa}}}` | For iOS devices, this value will be the Identifier for Advertising (IDFA) if your application is configured with our [optional IDFA collection][40]. For non-iOS devices, this value will be null. |
@@ -66,8 +68,7 @@ You can template in the following attributes for the user's most recent device a
 | `{{most_recently_used_device.${model}}}` | The device's model name, if available. Examples include "iPhone 6S" and "Nexus 6P" and "Firefox". |
 | `{{most_recently_used_device.${os}}}` | The device's operating system, if available. Examples include "iOS 9.2.1" and "Android (Lollipop)" and "Windows". |
 | `{{most_recently_used_device.${platform}}}` | The device's platform, if available. If set, the value will be one of `ios`, `android`, `kindle`, `android_china`, `web`, or `tvos`. |
-{: .reset-td-br-1 .reset-td-br-2}
-
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 Because there are such a wide range of device carriers, model names, and operating systems, we advise that you thoroughly test any Liquid that conditionally depends on any of those values. These values will be `null` if they are not available on a particular device.
 
@@ -78,8 +79,8 @@ For in-app messages, you can use the following app attributes within Liquid. The
 |Tag | Description |
 |------------------|---|
 | `{{app.${api_id}}}` | The API key of the app requesting the message. For example, you use this key in conjunction with `abort_message()` Liquid to avoid sending in-app messages to certain apps, such as TV platforms or development builds that use a separate SDK API key.|
-| `{{app.${name}}}` | The name of the app (as defined in the Braze dashboard) requesting the message|
-{: .reset-td-br-1 .reset-td-br-2}
+| `{{app.${name}}}` | The name of the app (as defined in the Braze dashboard) requesting the message. |
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 For example, this Liquid code will abort a message if the requesting apps are not one of the two API keys in the list:
 
@@ -94,7 +95,7 @@ User is in list of apps
 
 ## Targeted device information
 
-For push notification and in-app message channels, you can template in the following attributes for the device to which a message is being sent. That is, a push notification or in-app message can include device attributes of the device on which the message is being read. Note that these attributes will not work for Content Cards. 
+For push notification and in-app message channels, you can template in the following attributes for the device to which a message is being sent. That is, a push notification or in-app message can include device attributes of the device on which the message is being read. Note that these attributes won't work for Content Cards. 
 
 |Tag | Description |
 |------------------|---|
@@ -107,21 +108,23 @@ For push notification and in-app message channels, you can template in the follo
 | `{{targeted_device.${os}}}` | The device's operating system, if available. Examples include "iOS 9.2.1" and "Android (Lollipop)" and "Windows". |
 | `{{targeted_device.${platform}}}` | The device's platform, if available. If set, the value will be one of `ios`, `android`, `kindle`, `android_china`, `web`, or `tvos`. You can also use the `most_recently_used_device` personalization tag. |
 | `{{targeted_device.${foreground_push_enabled}}}` | This value will be `true` when the targeted device is enabled for foreground push, `false` otherwise. |
-{: .reset-td-br-1 .reset-td-br-2}
-
+{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
 
 {% endraw %}
 
+Because there are such a wide range of device carriers, model names, and operating systems, we advise that you thoroughly test any logic that conditionally depends on any of those values. These values will be `null` if they are not available on a particular device. 
 
-Because there are such a wide range of device carriers, model names, and operating systems, we advise that you thoroughly test any logic that conditionally depends on any of those values. These values will be `null` if they are not available on a particular device. Furthermore, for push notifications, it is possible that Braze may be unable to discern the device attached to the push notification under certain circumstances such as if the push token was imported via API, resulting in values being `null` for those messages.
+Furthermore, for push notifications, it's possible that Braze won't be able to discern the device attached to the push notification under certain circumstances such as if the push token was imported through API, resulting in values being `null` for those messages.
 
 ![Example of using a default value of "there" when using a first name variable in a push message.][4]
 
-In some circumstances, you may opt to use [conditional logic][17] instead of setting a default value. Conditional logic allows you to send messages that differ based on the value of a custom attribute.
+### Using conditional logic instead of a default value
 
-Additionally, you can use conditional logic to [abort messages][18] to customers with null or blank attribute values.
+In some circumstances, you may opt to use [conditional logic][17] instead of setting a default value. Conditional logic allows you to send messages that differ based on the value of a custom attribute. Additionally, you can use conditional logic to [abort messages][18] to customers with null or blank attribute values. 
 
-For example, if you're sending a rewards balance notification to customers, there isn't a good way to account for customers with low and null balances using default values.
+#### Use case
+
+For example, let's say you're sending a rewards balance notification to customers. There isn't a good way to account for customers with low and null balances using default values.
 
 In this case, there are two options that may work better than setting a default value:
 
@@ -139,7 +142,7 @@ In this case, there are two options that may work better than setting a default
 
 {% endraw %}
 
-2. Send a completely different message to these customers, perhaps something along the lines of:
+2. Send a completely different message to these customers, such as:
 
 {% raw %}
 
@@ -151,7 +154,7 @@ In this case, there are two options that may work better than setting a default
    {% endif %}
    ```
 
-In this example, a user with a blank or null first name will get the message "Thanks for downloading". You should include a [default value][47] for first name to make sure that your customer does not see Liquid in the event of a mistake.
+In this use case, a user with a blank or null first name will get the message "Thanks for downloading". You should include a [default value][47] for first name to make sure that your customer doesn't see Liquid in the event of a mistake.
 
 {% endraw %}
 
@@ -159,21 +162,8 @@ In this example, a user with a blank or null first name will get the message "Th
 
 You can use the `assign` tag to create a variable in the message composer. After you create a variable, you can reference that variable in your messaging logic or message.
 
-Let's say that you allow your customers to cash in their rewards points for prizes after they accrue 100 rewards points. So, you only want to message customers who would have a points balance greater than or equal to 100 if they made that additional purchase:
-
-{% raw %}
-```liquid
-{% assign new_points_balance = {{custom_attribute.${current_rewards_balance} | plus: 50}} %}
-{% if new_points_balance >= 100 %}
-Make a purchase to bring your rewards points to {{new_points_balance}} and cash in today!
-{% else %}
-{% abort_message('not enough points') %}
-{% endif %}
-```
 This tag comes in handy when you want to reformat content that is returned from our [Connected Content][4] feature. You can read more in Shopify's documentation on [variable tags][31].
 
-{% endraw %}
-
 {% alert tip %}
 Find yourself assigning the same variables in every message? Instead of writing out the `assign` tag over and over again, you can save that tag as a Content Block and put it at the top of your message instead.
 
@@ -185,10 +175,27 @@ Find yourself assigning the same variables in every message? Instead of writing
 As long as the Content Block is at the top of your message, every time the variable is inserted into your message as an object, it will refer to your chosen custom attribute!
 {% endalert %}
 
+### Use case
+
+Let's say that you allow your customers to cash in their rewards points for prizes after they accrue 100 rewards points. So, you only want to message customers who would have a points balance greater than or equal to 100 if they made that additional purchase:
+
+{% raw %}
+```liquid
+{% assign new_points_balance = {{custom_attribute.${current_rewards_balance} | plus: 50}} %}
+{% if new_points_balance >= 100 %}
+Make a purchase to bring your rewards points to {{new_points_balance}} and cash in today!
+{% else %}
+{% abort_message('not enough points') %}
+{% endif %}
+```
+{% endraw %}
+
 ## Iteration tags
 
 {% raw %}
-Iteration tags can be used to run a block of code repeatedly. This example features the `for` tag.
+Iteration tags can be used to run a block of code repeatedly. The use case below features the `for` tag.
+
+### Use case
 
 Let's say that you're having a sale on Nike sneakers and want to message customers who've expressed interest in Nike. You have an array of product brands viewed on each customer's profile. This array could contain up to 25 product brands, but you only want to message customers who viewed a Nike product as one of their 5 most recent product views.
 
@@ -205,9 +212,9 @@ Sale on Converse!
 {% endif %}
 ```
 
-In this example, we check the first five items in the sneaker brands viewed array. If one of those items is converse, we create the converse_viewer variable and set it to true.
+In this use case, we check the first five items in the sneaker brands viewed array. If one of those items is converse, we create the `converse_viewer` variable and set it to true.
 
-Then, we send the sale message when converse_viewer is true. Otherwise, we abort the message.
+Then, we send the sale message when `converse_viewer` is true. Otherwise, we abort the message.
 
 This is a simple example of how iteration tags can be used in the Braze message composer. You can find more information in Shopify's documentation on [iteration tags][32].
 
@@ -230,14 +237,16 @@ You can utilize the HTTP status from a [Connected Content][38] call by first sav
 {% endraw %}
 
 {% alert note %}
-  This key will only be automatically added to the Connected Content object if the endpoint returns a JSON object. If the endpoint returns an array or other type, then that key cannot be set automatically in the response.
+This key will only be automatically added to the Connected Content object if the endpoint returns a JSON object. If the endpoint returns an array or other type, then that key can't be set automatically in the response.
 {% endalert %}
 
 ## Sending messages based on language, most recent locale, and time zone
 
 In some situations you may wish to send messages that are specific to particular locales. For example, Brazilian Portuguese is typically different than European Portuguese.
 
-Here's an example of how you can use most recent locale to further localize an internationalized message.
+### Use case: Localize based on recent locale
+
+Here's a use case of how you can use most recent locale to further localize an internationalized message.
 
 {% raw %}
 
@@ -263,9 +272,13 @@ Message in default language
 {% endif %}
 ```
 
-In this example, customers with a most recent locale of 'pt_BR' will get a message in Brazilian Portuguese, and customers with a most recent locale of 'pt_PT' will get a message in European Portuguese. Customers who don't meet the first two conditions but have their language set to Portuguese will get a message in whatever you'd like the default Portuguese language type to be.
+In this use case, customers with a most recent locale of `pt_BR` will get a message in Brazilian Portuguese, and customers with a most recent locale of `pt_PT` will get a message in European Portuguese. Customers who don't meet the first two conditions but have their language set to Portuguese will get a message in whatever you'd like the default Portuguese language type to be.
+
+### Use case: Target users by time zone
+
+You can also target users by their time zone. For example, send one message if they are based in EST and another if they are PST. To do this, save the current time in UTC, and compare an if/else statement with the user's current time to send the right message for the right time zone. You should set the campaign to send in the user's local time zone, to give them the campaign at the right time. 
 
-You can also target users by their time zone. For example, send one message if they are based in EST and another if they are PST. To do this, save the current time in UTC, and compare an if/else statement with the user's current time to ensure you're sending the right message for the right time zone. You should set the campaign to send in the user's local time zone, to ensure they are getting the campaign at the right time. See the following example for how to write a message that will go out between 2 pm and 3 pm and will have a specific message for each time zone.
+See the following use case for how to write a message that will go out between 2 pm and 3 pm and will have a specific message for each time zone.
 
 ```liquid
 {% assign hour_in_utc = 'now' | date: '%H' | plus:0 %}
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/using_liquid.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/using_liquid.md
index ba95edc93a3..49d96149552 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/using_liquid.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/using_liquid.md
@@ -8,39 +8,21 @@ search_rank: 2
 
 # [![Braze Learning course]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/path/dynamic-personalization-with-liquid){: style="float:right;width:120px;border:0;" class="noimgborder"}Using Liquid
 
-{% raw %}
-
-> There are a variety of user attributes that you can use to dynamically insert personal information into your messaging.
-
-If you include the following text in your message: `{{${first_name}}}`, the user's first name (pulled from the user's profile) will be substituted when the message is sent. If you would like to use the value of a custom attribute, you must add the namespace "custom_attribute" to the variable. For example, to use a custom attribute named "zip code", you would include `{{custom_attribute.${zip code}}}` in your message.
-
-The following values can be substituted into a message, depending on their availability:
-
-- [Basic user information][1] (for example, `first_name`, `last_name`, `email_address`)
-- [Custom attributes][2]
-    - [Nested custom attributes][3]
-- [Custom event properties][11]
-- [Most recently used device information][39]
-- [Target device information][40]
-
-You can also pull content directly from a web server via Braze [Connected Content][9].
-{% endraw %}
+> This article will show how you can use a variety of user attributes to dynamically insert personal information into your messaging.
 
-{% alert important %}
-Braze currently supports Liquid up to and including **Liquid 5 from Shopify**.
-{% endalert %}
+Liquid is an open-source template language developed by Shopify and written in Ruby. You can use it in Braze to pull user profile data into your messages and customize that data. For example, you can use Liquid tags to create conditional messages, such as sending different offers based on a user's subscription anniversary date. Additionally, filters can manipulate data, like formatting a user's registration date from a timestamp into a more readable format, such as "January 15, 2022." For further details on Liquid syntax and its capabilities, refer to [Supported personalization tags][1].
 
-## Using Liquid
+## How it works
 
-{% raw %}
-
-Once you know the [Liquid tags available][1], using Liquid can elevate the personalization in your messages to impressive heights. Liquid tags act as placeholders in your messages that can pull in consented information from your user's account and enable personalization and relevant messaging practices.
+Liquid tags act as placeholders in your messages that can pull in consented information from your user's account and enable personalization and relevant messaging practices.
 
 In the following block, you can see that a dual usage of a Liquid tag to call the user's first name, as well as a default tag in the event that a user would not have their first name registered.
 
+{% raw %}
 ```liquid
 Hi {{ ${first_name} | default: 'Valued User' }}, thanks for using the App!
 ```
+{% endraw %}
 
 To a user named Janet Doe, the message would appear to the user as either:
 
@@ -54,6 +36,27 @@ Or...
 Hi Valued User, thanks for using the App!
 ```
 
+## Supported values to substitute
+
+The following values can be substituted into a message, depending on their availability:
+
+- [Basic user information][1] (for example, `first_name`, `last_name`, `email_address`)
+- [Custom attributes][2]
+    - [Nested custom attributes][3]
+- [Custom event properties][11]
+- [Most recently used device information][39]
+- [Target device information][40]
+
+You can also pull content directly from a web server through Braze [Connected Content][9].
+
+{% alert important %}
+Braze currently supports Liquid up to and including Liquid 5 from Shopify.
+{% endalert %}
+
+## Using Liquid
+
+Using [Liquid tags][1], you can elevate the quality of your messages by enriching them with a personal touch. 
+
 ### Liquid syntax
 
 Liquid follows a specific structure, or syntax, that you'll need to keep in mind as you're crafting dynamic personalization. Here are a few basic rules to keep in mind:
@@ -62,6 +65,14 @@ Liquid follows a specific structure, or syntax, that you'll need to keep in mind
 2. **Brackets come in pairs:** Every bracket must both open and close **{ }**. Make sure to use curly brackets!
 3. **If statements come in pairs:** For every `if`, you need an `endif` to indicate the `if` statement has ended.
 
+#### Default attributes and custom attributes
+
+{% raw %}
+
+If you include the following text in your message: `{{${first_name}}}`, the user's first name (pulled from the user's profile) will be substituted when the message is sent. You can use the same format with other default user attributes.
+
+If you would like to use the value of a custom attribute, you must add the namespace "custom_attribute" to the variable. For example, to use a custom attribute named "zip code", you would include `{{custom_attribute.${zip code}}}` in your message.
+
 ### Inserting tags
 
 You can insert tags by typing two open curly brackets `{{` in any message, which will trigger an auto-completion feature that will continue to update as you type. You can even select a variable from the options that appear as you type.
@@ -72,25 +83,24 @@ If you're using a custom tag, you can copy and paste the tag into whatever messa
 
 {% alert note %}
 
-If you choose to use Liquid in your email messages, be sure to:
+If you use Liquid in your email messages, be sure to:
 
-1. Insert it using the HTML editor as opposed to the classic editor. The Classic Editor may parse the Liquid as plaintext.
+1. Insert it using the HTML editor as opposed to the classic editor. The classic editor may parse the Liquid as plaintext. For example, the Liquid would parse as {% raw %}`Hi {{ ${first_name} }}, thanks for using our service!`{% endraw %} instead of templating in the user's first name.
 2. Place Liquid code within the `<body>` tag only. Placing it outside this tag may cause inconsistent rendering upon delivery.
 
 {% endalert %}
 
 {% raw %}
 
+### Inserting pre-formatted variables
 
-### Pre-formatted variables
-
-You can insert pre-formatted variables with defaults through the "Insert Personalization Attribute" modal located on the top-right of any templated text field.
+You can insert pre-formatted variables with defaults through the **Add Personalization** modal located on the top-right of any templated text field.
 
-![Plus buttons to insert personalization attributes on text fields that support Liquid in Braze][44]{: style="max-width:70%;"}
+![The Add Personalization modal that appears after selecting insert personalization. The modal has fields for personalization type, attribute, optional default value, and displays a preview of the Liquid syntax][44]{: style="max-width:70%;"}
 
-The modal will insert Liquid with your specified default value at the point that your cursor was. The insertion point is also specified via the preview box, which has the before and after text. If a block of text is highlighted, the highlighted text will be replaced.
+The modal will insert Liquid with your specified default value at the point that your cursor was. The insertion point is also specified by the preview box, which has the before and after text. If a block of text is highlighted, the highlighted text will be replaced.
 
-![Add Personalization modal that appears after clicking insert personalization. The modal has fields for personalization type, attribute, optional default value, and displays a preview of the Liquid syntax.][45]
+![A GIF of the Add Personalization modal that shows the user insertting "fellow traveler" as a default value, and the modal replacing the highlighted text "name" in the composer with the Liquid snippet.][45]
 
 {% endraw %}
 
@@ -99,13 +109,26 @@ The modal will insert Liquid with your specified default value at the point that
 {% raw %}
 Some operations in Liquid require you to store the value you want to manipulate as a variable. This is often the case if your Liquid statement includes multiple attributes, event properties, or filters.
 
-For example, let's say you want to add two custom data integers together. You can't simply use:
+For example, let's say you want to add two custom data integers together. 
+
+#### Incorrect Liquid example
+
+You can't use:
 
 ```liquid
 {{custom_attribute.${one}}} | plus: {{custom_attribute.${two}}}
 ```
 
-This Liquid doesn't work because you can't reference multiple attributes in one line; you would need to assign a variable to at least one of these values before the math functions take place. Adding two custom attributes would require two lines of Liquid: one to assign the custom attribute to a variable, and one to perform the addition.
+This Liquid doesn't work because you can't reference multiple attributes in one line; you need to assign a variable to at least one of these values before the math functions take place. Adding two custom attributes would require two lines of Liquid: one to assign the custom attribute to a variable, and one to perform the addition.
+
+#### Correct Liquid example
+
+You can use:
+
+```liquid
+{% assign value_one = {{custom_attribute.${one}}} %}
+{% assign result = value_one | plus: {{custom_attribute.${two}}} %}
+```
 
 #### Tutorial: Using variables to calculate a balance
 
@@ -130,8 +153,8 @@ Find yourself assigning the same variables in every message? Instead of writing
 
 1. [Create a Content Block]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/#create-a-content-block).
 2. Give your Content Block a name (no spaces or special characters).
-3. Click **Edit** at the bottom of the page.
-4. Type in your `assign` tags.
+3. Select **Edit** at the bottom of the page.
+4. Enter your `assign` tags.
 
 As long as the Content Block is at the top of your message, every time the variable is inserted into your message as an object, it will refer to your chosen custom attribute!
 {% endalert %}
@@ -144,4 +167,4 @@ As long as the Content Block is at the top of your message, every time the varia
 [39]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#most-recently-used-device-information
 [40]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#targeted-device-information
 [44]: {% image_buster /assets/img_archive/insert_liquid_var_arrow.png %}
-[45]: {% image_buster /assets/img_archive/insert_var_shot.png %}
+[45]: {% image_buster /assets/img_archive/insert_var_shot.gif %}
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/promotion_codes.md b/_docs/_user_guide/personalization_and_dynamic_content/promotion_codes.md
index 8e32e2b200d..46260df38a0 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/promotion_codes.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/promotion_codes.md
@@ -59,7 +59,12 @@ You also have the option to set up optional and customized threshold alerts. If
 
 ### Step 4: Promotion code upload
 
-Braze does not manage code creation or redemption. As a result, you'll have to generate your promotion codes to a CSV file and upload them to Braze. You can use our built-in integration with [Voucherify]({{site.baseurl}}/partners/channel_extensions/loyalty/voucherify/) or [Talon.One]({{site.baseurl}}/partners/channel_extensions/loyalty/talonone/) to create and export promotion codes. Make sure that there is only one code on each row.
+Braze does not manage code creation or redemption, meaning you must generate your promotion codes to a CSV file and upload them to Braze. Make sure the CSV file follows these guidelines:
+
+- Includes a column for promotion codes.
+- Has one promotion code per row.
+
+You can use our built-in integration with [Voucherify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/voucherify/) or [Talon.One]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/talonone/) to create and export promotion codes.
 
 {% alert note %}
 The maximum file size is 100&nbsp;MB and the maximum list size is 20MM of unused codes. If you find the wrong file was uploaded, upload a new one, and the previous one will be replaced.
diff --git a/_docs/_user_guide/personalization_and_dynamic_content/promotion_codes/migrating_from_data_feeds.md b/_docs/_user_guide/personalization_and_dynamic_content/promotion_codes/migrating_from_data_feeds.md
index dff01d6ac10..d8100c3c3e4 100644
--- a/_docs/_user_guide/personalization_and_dynamic_content/promotion_codes/migrating_from_data_feeds.md
+++ b/_docs/_user_guide/personalization_and_dynamic_content/promotion_codes/migrating_from_data_feeds.md
@@ -22,7 +22,7 @@ There are a few differences between promotion code lists and Data Feeds.
 | Descriptions     | Yes             | No           |
 | Expiration Dates | Yes             | No           |
 | Creation Method  | Uploading a CSV | Pasting text |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 role="presentation" }
 
 ## How to migrate
 
diff --git a/_includes/campaign_analytics.md b/_includes/campaign_analytics.md
index e1d7661a795..d4ca151bf67 100644
--- a/_includes/campaign_analytics.md
+++ b/_includes/campaign_analytics.md
@@ -163,17 +163,55 @@ In this view, you can use the **Show Heatmap** toggle to bring up a visual view
 
 #### Content Card metrics
 
-Here is a breakdown of some key metrics you may see while reviewing your message performance. For the definitions of all Content Cards metrics, refer to the [Report Metrics Glossary][1] and filter by Content Cards.
-
-| Term | Definition |
-| -- | -- |
-| Messages Sent | This is calculated differently depending on what you selected for [Card creation]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/#differences-between-creating-cards-at-launch-or-entry-versus-at-first-impression):<br><br>  {::nomarkdown}<ul><li><b>At launch or step entry:</b> The number of cards created and available to be seen. This doesn't count whether the users viewed the card.</li><li><b>At first impression:</b> The number of cards displayed to users.</li></ul>{:/} |
-| Total Impressions | The total count of impressions logged for a given Content Card. This can increment multiple times for the same user. |
-| Unique Impressions | The number of users who have viewed a given card. This count doesn't increment the second time that a user views a card. |
-| Unique Recipients | The total number of viewers (unique, but only unique per day) that have viewed the particular card. Because a viewer can be a unique recipient every day, you should expect this to be higher than Unique Impressions. |
-| Unique Clicks | The number of recipients who have clicked the CTA link of a Content Card at least once—excluding clicks on Braze-provided unsubscribe links. Measured by [`dispatch_id`]({{site.baseurl}}/help/help_articles/data/dispatch_id/). |
-Unique Dismissals | The number of users who have dismissed Content Cards from a campaign. A user dismissing a Content Card from a campaign multiple times represents one unique dismissal. |
-{: .reset-td-br-1 .reset-td-br-2}
+Here is a breakdown of some key metrics you may see while reviewing your message performance. For the full definitions of all Content Cards metrics, refer to the [Report Metrics Glossary][1] and filter by Content Cards.
+
+<style>
+    .no-split {
+        word-break: keep-all;
+    }
+</style>
+
+<table>
+    <thead>
+        <tr>
+            <th>Metric</th>
+            <th>Definition</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#messages-sent">Messages Sent</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Messages Sent' %} <br><br>
+                This is calculated differently depending on what you selected for 
+                <a href="/docs/user_guide/message_building_by_channel/content_cards/create/card_creation/#differences-between-creating-cards-at-launch-or-entry-versus-at-first-impression">Card creation</a>:<br><br>
+                <ul>
+                    <li><b>At launch or step entry:</b> The number of cards created and available to be seen. This doesn't count whether the users viewed the card.</li>
+                    <li><b>At first impression:</b> The number of cards displayed to users.</li>
+                </ul>
+            </td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#total-impressions">Total Impressions</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Total Impressions' %} This can increment multiple times for the same user.</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#unique-impressions">Unique Impressions</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Unique Impressions' %} <span style="white-space: nowrap">This count</span> doesn't increment the second time that a user views a card.</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#unique-recipients">Unique Recipients</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Unique Recipients' %} <br><br> Because a viewer can be a unique recipient every day, you should expect this to be higher than <i>Unique Impressions</i>.</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#unique-clicks">Unique Clicks</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Unique Clicks' %} This includes clicks on Braze-provided unsubscribe links.</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#unique-dismissals">Unique Dismissals</a></td>
+            <td>{% multi_lang_include metrics.md metric='Unique Dismissals' %}</td>
+        </tr>
+    </tbody>
+</table>
 
 {% alert note %}
 Regarding how impressions are logged, there are some nuances between web, Android, and iOS. Generally speaking, Braze logs an impression when a card is seen, which is after a user scrolls to the specific Content Card in their feed.
@@ -197,22 +235,74 @@ Your _Messages Sent_ refers to Content Cards available to be seen, while _Unique
 
 #### Email metrics
 
-Here are some key email-specific metrics that you won't see in other channels. To see the definitions of all email metrics used in Braze, refer to our [Email Analytics Glossary]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/analytics_glossary/).
-
-| Metric | Definition |
-| --- | --- |
-| Unique Clicks | The number of recipients that clicked within the email sent. This is tracked over a 7-day period and is measured by [`dispatch_id`]({{site.baseurl}}/help/help_articles/data/dispatch_id/). This number should be between 5–10%. Anything greater than 10% is exceptional! |
-| Unique Opens | The number of recipients that opened your email. This can also include emails that are machine opened and is tracked over a 7-day period. This number should be between 10–20%. Anything greater than 20% is exceptional! |
-| Click to Open Rate | The percentage of unique emails opened that have been clicked at least once. |
-| Spam Rate | The percentage of delivered emails marked or designated as spam. If this metric is greater than 0.08, that could be a sign that either your message copy is too salesy, or you should reconsider your email address collection methods (to confirm you're messaging those who are interested in your correspondence). |
-| Unsubscribers (Unsubs) | The number of messages resulting in an unsubscription. This occurs when a user clicks the unsubscribe link in your email. |
-| Other Opens | The number of recipients that opened your email, including emails that haven't been identified as _Machine Opens_. <br>For example, when a user opens an email on another platform (such as Gmail app on a phone, Gmail on desktop browser), this will be logged as an _Other Opens_. Note that a user can also open an email (such as the open counts toward _Other Opens_) before a _Machine Opens_ count is logged. If a user opens an email once (or more) after a machine open event from a non-Apple Mail inbox, then the amount of times that the user opens the email is calculated toward _Other Opens_ and only once toward _Unique Opens_. |
-| Estimated Real Opens | An estimate of how many unique opens there would be if machine opens did not exist. This is the result of a proprietary Braze statistical model. See the following section for details. |
-| Machine Opens | Includes the proportion of “opens” that are affected by Apple's Mail Privacy Protection (MPP) for iOS 15. <br>For example, if a user opens an email using the Mail app on an Apple device, this will be logged as a _Machine Opens_. This metric is tracked starting November 11, 2021 for SendGrid and December 2, 2021 for SparkPost. |
-| Bounces | The total number of messages that were unsuccessfully delivered to the intended recipients. This could occur because the email addresses were incorrect or deactivated. |
-| Hard Bounces | A hard bounce is when an email fails to deliver to the recipient due to a permanent delivery error. A hard bounce might occur because the domain name doesn't exist or because the recipient is unknown. If an email receives a hard bounce, we will stop any future requests to this email address. |
-| Soft Bounces | A soft bounce is when an email fails to deliver to the recipient due to a temporary delivery error, even though the recipient’s email address is valid. A soft bounce might occur because the recipient's inbox is full, the server was down, or the message was too large for the recipient's inbox. If an email receives a soft bounce, we will usually retry within 72 hours, but the number of retry attempts varies from receiver to receiver. You can view your hard and soft bounces in the [Message Activity Log]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/message_activity_log_tab/#message-activity-log-tab). |
-{: .reset-td-br-1 .reset-td-br-2}
+Here are some key email-specific metrics that you won't see in other channels. To see the full definitions of all email metrics used in Braze, refer to our [Email Analytics Glossary]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/analytics_glossary/).
+
+<style>
+    .no-split {
+        word-break: keep-all;
+    }
+</style>
+
+<table>
+    <thead>
+        <tr>
+            <th>Metric</th>
+            <th>Definition</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#unique-clicks">Unique Clicks</a></td>
+            <td class="no-split">
+                {% multi_lang_include metrics.md metric='Unique Clicks' %} This is tracked over a seven-day period for email and measured by <a href='https://braze.com/docs/help/help_articles/data/dispatch_id/'>dispatch_id</a>. This includes clicks on Braze-provided unsubscribe links. This number should be between 5–10%. Anything greater than 10% is exceptional!
+            </td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#unique-opens">Unique Opens</a></td>
+            <td class="no-split">
+                {% multi_lang_include metrics.md metric='Unique Opens' %} For email, this is tracked over a 7 day period. This number should be between 10–20%. Anything greater than 20% is exceptional!
+            </td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#click-to-open-rate">Click-to-Open Rate</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Click-to-Open Rate' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#spam">Spam Rate</a></td>
+            <td class="no-split">
+                {% multi_lang_include metrics.md metric='Spam' %} If this metric is greater than 0.08, that could be a sign that either your message copy is too salesy, or you should reconsider your email address collection methods (to confirm you're messaging those who are interested in your correspondence).
+            </td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#unsubscribers-or-unsub">Unsubscribers or Unsub</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Unsubscribers or Unsub' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#other-opens">Other Opens</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Other Opens' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#estimated-real-opens">Estimated Real Opens</a></td>
+            <td class="no-split"> {% multi_lang_include metrics.md metric='Estimated Real Opens' %} See the following section for details.</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#machine-opens">Machine Opens</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Machine Opens' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#bounces">Bounces</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Bounces' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#hard-bounce">Hard Bounce</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Hard Bounce' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#soft-bounce">Soft Bounce</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Soft Bounce' %}</td>
+        </tr>
+    </tbody>
+</table>
 
 ##### Estimated real open rate {#estimated-real-open-rate}
 
@@ -230,35 +320,91 @@ Estimated Real Open Rate is only available in campaigns, and is not reported in
 
 #### In-app message metrics
 
-Here are some key in-app message metrics you may see in your analytics. To see the definitions of all in-app message metrics used in Braze, refer to our [Report Metrics Glossary][1].
-
-| Term                   | Definition                                                                                                         |
-|------------------------|-------------------------------------------------------------------------------------------------------------------|
-| Body Clicks*           | Occurs when a user clicks on the message itself and not one of the buttons. This only applies to messages created with the traditional editor. |
-| Button 1 and Button 2 Clicks | The percentage of recipients that pressed that specific button.                                                |
-| Unique Impressions     | The total number of people who actually received and viewed the in-app message. If a user receives the message twice within 24 hours, only one impression is counted that day. <br><br> **If re-eligibility is on:** {::nomarkdown}<ul><li>Unique impressions can be incremented again after 24 hours if re-eligibility is on and a user performs the trigger action again.</li><li>For in-app messages, *Unique Impressions* = *Unique Recipients* since impressions and recipients both increment after 24 hours.</li></ul>{:/} |
-| Total Impressions            | The number of users whose devices reported that the message had been delivered. If a user receives the message twice, they are counted twice. <br><br> **If there are multiple devices:** {::nomarkdown}<ul><li>If re-eligibility is off, the user should only see the in-app message once. Even if the user uses multiple devices, they will only see it on the first device that is targeted. This assumes that the profile has consolidated devices and a user has one user ID that they are logged into across devices. </li></ul>{:/} **If re-eligibility is on:** {::nomarkdown}<ul><li>An impression is logged for every time that user sees the in-app message.</li></ul>{:/} |
-| Conversion             | Conversion tracking starts once a user logs an impression of an in-app message. A conversion is counted if the user has received and viewed the in-app message campaign, and subsequently performs the specific conversion event within the defined conversion window, regardless of whether they clicked on the message or not. <br><br> Conversions are attributed to the most recently received message. If re-eligibility is enabled, the conversion will be assigned to the latest in-app message received, provided that it occurs within the defined conversion window. However, if the in-app message has already been assigned a conversion, then the new conversion cannot be logged for that specific message. This ensures that each in-app message delivery is associated with only one conversion. |
-| Total Conversions      | When a user views an in-app message campaign only once, only one conversion is counted, even if they perform the conversion event multiple times later on. However, if re-eligibility is turned on and the user sees the in-app message campaign multiple times, _Total Conversions_ can increase once for each time the user logs an impression for a new instance of the in-app message campaign. <br><br> For example, if a user triggers an in-app message twice and converts after each in-app message impression (resulting in two conversions), then _Total Conversions_ will increase by two. However, if there was only one in-app message impression followed by two conversion events, only one conversion will be logged, and _Total Conversions_ will increase by one. |
-| Conversion Rate        | The metric of total daily unique impressions (_Unique Impressions_) is used to calculate the conversion rate. <br><br> Conversion Rate = (Primary Conversions) / (Unique Impressions) <br><br> Impressions for in-app messages can only be counted once per day. On the other hand, the number of times a user completes a desired action (a "conversion") can increase within a 24-hour period. While conversions can happen more than once per day, impressions cannot. Therefore, if a user completes a conversion multiple times within a day, the _Conversion Rate_ can increase accordingly, but impressions will only be counted once. |
-{: .reset-td-br-1 .reset-td-br-2}
-
-{% alert note %}
-*Body clicks are not automatically collected for in-app messages created with the drag-and-drop editor and the custom code editor. For more details, refer to the SDK changelogs for [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/changelog/objc_changelog#3310) and [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/changelog#1100).
-{% endalert %}
+Here are some key in-app message metrics you may see in your analytics. To see the full definitions of all in-app message metrics used in Braze, refer to our [Report Metrics Glossary][1].
+
+<style>
+    .no-split {
+        word-break: keep-all;
+    }
+</style>
+
+<table>
+    <thead>
+        <tr>
+            <th>Metric</th>
+            <th>Definition</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#body-clicks">Body Clicks</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Body Clicks' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#button-1-clicks">Button 1 Clicks</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Button 1 Clicks' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#button-2-clicks">Button 2 Clicks</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Button 2 Clicks' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#unique-impressions">Unique Impressions</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Unique Impressions' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#total-impressions">Total Impressions</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Total Impressions' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#conversions-b-c-d">Conversions (B, C, D)</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Conversions (B, C, D)' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#total-conversions">Total Conversions</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Total Conversions' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#conversion-rate">Conversion Rate</a></td>
+            <td>{% multi_lang_include metrics.md metric='Conversion Rate' %}</td>
+        </tr>
+    </tbody>
+</table>
 
 {% elsif include.channel == "push" %}
 
 #### Push metrics
 
-Here is a breakdown of some key metrics you may see while reviewing your message performance. For the definitions of all push metrics, refer to the [Report Metrics Glossary][1] and filter by push.
-
-| Term | Description |
-| --------- | --- |
-| Bounces | The push notifications sent to these users were undeliverable. These users have been automatically unsubscribed from all future push notifications. See [Bounced push notifications](#bounced-push). |
-| Direct Opens | Instances in which a user opened your app by interacting directly with a push notification. |
-| Opens | Instances including both _Direct Opens_ and _Influenced Opens_ in which the Braze SDK has determined, using a proprietary algorithm, that a push notification has caused a user to open the app. |
-{: .reset-td-br-1 .reset-td-br-2}
+Here is a breakdown of some key metrics you may see while reviewing your message performance. For the full definitions of all push metrics, refer to the [Report Metrics Glossary][1] and filter by push.
+
+<style>
+    .no-split {
+        word-break: keep-all;
+    }
+</style>
+
+<table>
+    <thead>
+        <tr>
+            <th>Metric</th>
+            <th>Description</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#bounces">Bounces</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Bounces' %} See <a href="#bounced-push">Bounced push notifications</a>.</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#direct-opens">Direct Opens</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Direct Opens' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#opens">Opens</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Opens' %}</td>
+        </tr>
+    </tbody>
+</table>
 
 Push unsubscribes are not included as a metric in campaign analytics. Refer to [Tracking push unsubscribes]({{site.baseurl}}/help/help_articles/push/push_unsubscribes) for steps on how to manually track this metric.
 
@@ -293,49 +439,130 @@ Firebase Cloud Messaging (FCM) bounces could occur in three cases:
 
 #### SMS metrics
 
-Here is a breakdown of some key metrics you may see while reviewing your message performance. For the definitions of all SMS metrics, refer to the [Report Metrics Glossary][1] and filter by SMS.
-
-| Term | Definition |
-| -- | -- |
-| Sent | A campaign or Canvas step has been launched or triggered, and an SMS has been sent from Braze. It is possible that the SMS does not reach a user's device due to errors, as explained below. |
-| Sends to Carrier | This metric is deprecated, but will continue to be supported for users that already have it. <br><br> Braze has attempted to send the SMS through to the carriers. This stat is the sum of _Confirmed Deliveries_, Rejections, and sends where the carrier did not confirm delivery or rejection. There are instances where carriers do not provide delivery or rejected confirmation, as some carriers do not provide this confirmation or were unable to do so at the time of sending. Note that this metric does not exist for all Braze mobile aggregators. |
-| Delivery Failures | Messages that were not attempted to be sent due to a failed outcome within aggregator logs. This could be due to queue overflow or invalid recipient number, depending on the associated aggregator error code. Reach out to [Braze Support]({{site.baseurl}}/braze_support/) for assistance in understanding the reasons for delivery failures. |
-| Confirmed Delivery | The carrier has confirmed that the SMS was delivered to the target phone number. As a Braze customer, deliveries are charged toward your SMS allotment. |
-| Rejections | The SMS has been rejected by the carrier. This can happen for several reasons, including carrier content filtering, availability of the destination device or the phone number is no longer in service. As a Braze customer, rejections are charged toward your SMS allotment. |
-| Opt-Out | A user replied to your message with an [opt-out keyword]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/keyword_handling/#default-opt-in-opt-out-keywords) and was unsubscribed from your SMS program. A user reply is measured anytime a user sends an inbound message within four hours of receiving your message. |
-| Help | A user replied to your message with a [HELP keyword]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/keyword_handling/#default-opt-in-opt-out-keywords) and was dispatched a HELP auto-response. A user reply is measured anytime a user sends an inbound message within four hours of receiving your message. |
-| Total Clicks | The total number (and percentage) of users who clicked within the delivered message. |
-{: .reset-td-br-1 .reset-td-br-2}
+Here is a breakdown of some key metrics you may see while reviewing your message performance. For the full definitions of all SMS metrics, refer to the [Report Metrics Glossary][1] and filter by SMS.
+
+<style>
+    .no-split {
+        word-break: keep-all;
+    }
+</style>
+
+<table>
+    <thead>
+        <tr>
+            <th>Metric</th>
+            <th>Definition</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#sent">Sent</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Sent' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#sends-to-carrier">Sends to Carrier</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Sends to Carrier' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#delivery-failures">Delivery Failures</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Delivery Failures' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#confirmed-delivery">Confirmed Delivery</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Confirmed Deliveries' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#rejections">Rejections</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Rejections' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#opt-out">Opt-Out</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Opt-Out' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#help">Help</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Help' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#total-clicks">Total Clicks</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Total Clicks' %}</td>
+        </tr>
+    </tbody>
+</table>
 
 {% elsif include.channel == "webhook" %}
 
 #### Webhook metrics
 
-Here are some key webhook metrics you may see in your analytics. To see the definitions of all webhook metrics used in Braze, refer to our [Report Metrics Glossary][1].
-
-| Term | Definition |
-| --- | --- |
-| Unique Recipients | The total number of users (unique, but only unique per day) that have received the particular webhook. |
-| Sends | _Sends_ (and _Messages Sent_) include all attempted sends, successful and unsuccessful. This metric counts when a webhook was processed and sent to the third party specified in that webhook, and does not signify whether or not the request was received. |
-| Errors | The total number of sends that were not successful. Errors are included in the _Sends_ count but are not included in the _Unique Recipients_ count. |
-{: .reset-td-br-1 .reset-td-br-2}
+Here are some key webhook metrics you may see in your analytics. To see th full definitions of all webhook metrics used in Braze, refer to our [Report Metrics Glossary][1].
+
+<style>
+    .no-split {
+        word-break: keep-all;
+    }
+</style>
+
+<table>
+    <thead>
+        <tr>
+            <th>Metric</th>
+            <th>Definition</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#unique-recipients">Unique Recipients</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Unique Recipients' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#sends">Sends</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Sends' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#errors">Errors</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Errors' %}</td>
+        </tr>
+    </tbody>
+</table>
 
 {% elsif include.channel == "whatsapp" %}
 
 #### WhatsApp metrics
 
-Here are some key WhatsApp metrics you may see in your analytics. To see the definitions of all WhatsApp metrics used in Braze, refer to our [Report Metrics Glossary][1].
-
-| Term | Definition |
-| --- | --- |
-| Sends | The total number of sends successfully communicated between Braze and WhatsApp. However, this does not necessarily mean the message was received by the end user. |
-| Deliveries | The total number of WhatsApp messages sent that successfully made it to the end user's device. | 
-| Delivery rate | The percentage of users who had a delivery over users who had a send. Calculation: (Deliveries) / (Sends)|
-| Reads | When a WhatsApp message is read by the end user. The end user's read receipts must be "on" for Braze to track reads. | 
-| Read rate | The percentage of users who read the message over users who had a send. Calculation: (Reads) / (Sends)|
-| Failures | The total number of sends that were not successful because WhatsApp could not deliver the message to the end user. Failures are included in the _Sends_ count but not in the _Deliveries_ count. | 
-| Failure rate | The percentage of users who had unsuccessful sends over users who had a successful send. Calculation: (Failures) / (Sends)|
-{: .reset-td-br-1 .reset-td-br-2}
+Here are some key WhatsApp metrics you may see in your analytics. To see the full definitions of all WhatsApp metrics used in Braze, refer to our [Report Metrics Glossary][1].
+
+<style>
+    .no-split {
+        word-break: keep-all;
+    }
+</style>
+
+<table>
+    <thead>
+        <tr>
+            <th>Metric</th>
+            <th>Definition</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#sends">Sends</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Sends' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#deliveries">Deliveries</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Deliveries' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#reads">Reads</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Reads' %}</td>
+        </tr>
+        <tr>
+            <td class="no-split"><a href="/docs/user_guide/data_and_analytics/report_metrics/#failures">Failures</a></td>
+            <td class="no-split">{% multi_lang_include metrics.md metric='Failures' %}</td>
+        </tr>
+    </tbody>
+</table>
 
 #### End-user blocking and reporting metrics
 
diff --git a/_includes/contributing/templates/basic.md b/_includes/contributing/templates/basic.md
index e5ccf2ba73d..7f2b8bf4786 100644
--- a/_includes/contributing/templates/basic.md
+++ b/_includes/contributing/templates/basic.md
@@ -10,7 +10,7 @@ description: "SHORT_DESCRIPTION."
 alias: /OPTIONAL_SHORT_ARTICLE_TITLE/
 page_type: reference
 layout: OPTIONAL_LAYOUT_FILE
-—
+---
 
 <!-- The title of your page, used to render the in-page title. -->
 # ARTICLE_TITLE
diff --git a/_includes/contributing/templates/explanation.md b/_includes/contributing/templates/explanation.md
index 66496893b22..16f6f94eeda 100644
--- a/_includes/contributing/templates/explanation.md
+++ b/_includes/contributing/templates/explanation.md
@@ -8,7 +8,7 @@ description: "SHORT_DESCRIPTION."
 alias: /OPTIONAL_SHORT_ARTICLE_TITLE/
 page_type: reference
 layout: OPTIONAL_LAYOUT_FILE
-—--
+---
 
 # ARTICLE_TITLE
 
diff --git a/_includes/contributing/templates/how_to_guide.md b/_includes/contributing/templates/how_to_guide.md
index 09baf54203f..3bd52608672 100644
--- a/_includes/contributing/templates/how_to_guide.md
+++ b/_includes/contributing/templates/how_to_guide.md
@@ -8,7 +8,7 @@ description: "SHORT_DESCRIPTION."
 alias: /OPTIONAL_SHORT_ARTICLE_TITLE/
 page_type: reference
 layout: OPTIONAL_LAYOUT_FILE
-—--
+---
 
 # ARTICLE_TITLE
 
diff --git a/_includes/contributing/templates/reference.md b/_includes/contributing/templates/reference.md
index 66496893b22..16f6f94eeda 100644
--- a/_includes/contributing/templates/reference.md
+++ b/_includes/contributing/templates/reference.md
@@ -8,7 +8,7 @@ description: "SHORT_DESCRIPTION."
 alias: /OPTIONAL_SHORT_ARTICLE_TITLE/
 page_type: reference
 layout: OPTIONAL_LAYOUT_FILE
-—--
+---
 
 # ARTICLE_TITLE
 
diff --git a/_includes/contributing/templates/technology_partner.md b/_includes/contributing/templates/technology_partner.md
index 3b15fd6a753..9c4e367b55b 100644
--- a/_includes/contributing/templates/technology_partner.md
+++ b/_includes/contributing/templates/technology_partner.md
@@ -10,13 +10,12 @@ description: "SHORT_DESCRIPTION."
 alias: /partners/PARTNER_NAME/
 page_type: partner
 search_tag: Partner
-layout: dev_guide
 ---
 
-<!-- In most cases, the ARTICLE_TITLE will be your company name. If your tool requires several seperate pages on Braze Docs, you can add a relevant page descriptor to your title, such as "MyCompany Analytics." -->
+<!-- In most cases, the ARTICLE_TITLE will be your company name. If your tool requires several separate pages on Braze Docs, you can add a relevant page descriptor to your title, such as "MyCompany Analytics." -->
 # ARTICLE_TITLE
 
-<!-- The description starts with a '>' character and contains an introduction to your company, a link to your main site, and a consice overview of your integration. In a following paragraph, highlight the the relationship between your company and Braze and how this partnership helps your customers. -->
+<!-- The description starts with a '>' character and contains an introduction to your company, a link to your main site, and a concise overview of your integration. In a following paragraph, highlight the the relationship between your company and Braze and how this partnership helps your customers. -->
 > DESCRIPTION.
 
 ADDITIONAL_INFORMATION.
@@ -42,7 +41,7 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), you can cr
 
 CONTENT.
 
-<!-- Create step-by-step instructions for integrating your tool with Braze. It's important to be concise and only outline the minimum neccesary steps. -->
+<!-- Create step-by-step instructions for integrating your tool with Braze. It's important to be concise and only outline the minimum necessary steps. -->
 ## Integrating TOOL_NAME
 
 CONTENT.
@@ -87,7 +86,7 @@ CONTENT.
 
 CONTENT.
 
-<!-- An optional section you can use to outline additional customization steps. It's important to be concise and only outline the minimum neccesary steps. -->
+<!-- An optional section you can use to outline additional customization steps. It's important to be concise and only outline the minimum necessary steps. -->
 ## Customizing TOOL_NAME
 
 ### Step 1: ACTION_TO_COMPLETE
@@ -98,7 +97,7 @@ CONTENT.
 
 CONTENT.
 
-<!-- A section outlinning how to use your integration with Braze. For example: how to access the data sent to Braze, or how to leverage your integration with Braze messaging. -->
+<!-- A section outlining how to use your integration with Braze. For example: how to access the data sent to Braze, or how to leverage your integration with Braze messaging. -->
 ## Using TOOL_NAME with Braze
 
 ### Step 1: ACTION_TO_COMPLETE
diff --git a/_includes/contributing/templates/tutorial.md b/_includes/contributing/templates/tutorial.md
index 3feb650a753..6b1d30883b9 100644
--- a/_includes/contributing/templates/tutorial.md
+++ b/_includes/contributing/templates/tutorial.md
@@ -8,7 +8,7 @@ description: "SHORT_DESCRIPTION."
 alias: /OPTIONAL_SHORT_ARTICLE_TITLE/
 page_type: tutorial
 layout: OPTIONAL_LAYOUT_FILE
-—--
+---
 
 # Tutorial: WHAT_THE_USER_WILL_DO
 
diff --git a/_includes/feedback.html b/_includes/feedback.html
index abaa4ae23d6..7cb00a99cff 100644
--- a/_includes/feedback.html
+++ b/_includes/feedback.html
@@ -1,6 +1,6 @@
 <div class="gitedit_div">
     <a href="{{site.github_baseurl}}{{page.relative_path }}" class="extignore" target="_blank">
-        <img src="{{site.baseurl}}/assets/img/{{site.github_icon}}" /> &nbsp; {{ site.data.i18n[site.language]['edit_github'] | default: "Edit this page on GitHub" }}
+        <img src="{{site.baseurl}}/assets/img/{{site.github_icon}}" alt="Github" /> &nbsp; {{ site.data.i18n[site.language]['edit_github'] | default: "Edit this page on GitHub" }}
     </a>
 </div>
 
@@ -13,11 +13,11 @@
 
     <div id="feedback_answer">
       <ul class="list-inline rating-list">
-        <li class="inline-star"><i class="fas fa-star" data-value="Very Helpful" title="Very Helpful"></i></li>
-        <li class="inline-star"><i class="fas fa-star" data-value="Helpful" title="Helpful"></i></li>
-        <li class="inline-star"><i class="fas fa-star" data-value="Somewhat Helpful" title="Somewhat Helpful"></i></li>
-        <li class="inline-star"><i class="fas fa-star" data-value="Unhelpful" title="Unhelpful"></i></li>
-        <li class="inline-star"><i class="fas fa-star" data-value="Very Unhelpful" title="Very Unhelpful"></i></li>
+        <li class="inline-star" tabindex="0"><i class="fas fa-star" data-value="Very Helpful" title="Very Helpful"></i></li>
+        <li class="inline-star" tabindex="0"><i class="fas fa-star" data-value="Helpful" title="Helpful"></i></li>
+        <li class="inline-star" tabindex="0"><i class="fas fa-star" data-value="Somewhat Helpful" title="Somewhat Helpful"></i></li>
+        <li class="inline-star" tabindex="0"><i class="fas fa-star" data-value="Unhelpful" title="Unhelpful"></i></li>
+        <li class="inline-star" tabindex="0"><i class="fas fa-star" data-value="Very Unhelpful" title="Very Unhelpful"></i></li>
       </ul>
     </div>
     <div id="feedback_comment_div">
@@ -37,4 +37,4 @@
     var feedback_site = '{{site.baseurl}}{{page.url}}';
     var feedback_article_title = '{{page.article_title}}';
     var feedback_nav_title = '{{page.nav_title}}';
-</script>
\ No newline at end of file
+</script>
diff --git a/_includes/header.html b/_includes/header.html
index 450267cea47..638e3a3b9b0 100644
--- a/_includes/header.html
+++ b/_includes/header.html
@@ -11,7 +11,7 @@
 
 <header id="header_nav" >
 
-  <nav class="navbar navbar-expand-md  flex-column-md flex-md-row navbar-dark">
+  <nav class="navbar navbar-expand-md  flex-column-md flex-md-row navbar-dark" aria-label="Header Navigation" title="Header Navigation">
     <div id="header_wrapper">
       <div id="nav_logo">
            <a id="logo" href="{{site.baseurl}}/"><img src="{{site.baseurl}}/assets/img/logos/braze-logo-white.svg" alt="Braze"></a>
@@ -55,9 +55,9 @@
 					<ul id="braze_header_lang">
 						<li class="nav-item nav-item-lang-li">
 							<div id="nav-item-lang">
-							<label for="lang_select"><i class="fa-solid fa-globe"></i>
+							<label for="lang_select"><i class="fa-solid fa-globe">&nbsp;</i>
 							</label>
-							<select class="lang-select" id="lang_select">
+							<select class="lang-select" id="lang_select" aria-label="language select">
 								<option value="en">EN</option>
 								<option value="fr">FR</option>
 								<option value="ja">JA</option>
@@ -80,9 +80,9 @@
 
     <div class="navbarCollapse d-md-none" id="dropdown_navbar">
       <div id="dropdown_navbar_lang">
-        <label for="lang_select"><i class="fa-solid fa-globe"></i>
+        <label for="lang_select"><i class="fa-solid fa-globe">&nbsp;</i>
         </label>
-        <select class="lang-select" id="lang_select_responsive">
+        <select class="lang-select" id="lang_select_responsive" aria-label="language select">
           <option value="en">EN</option>
 					<option value="fr">FR</option>
           <option value="ja">JA</option>
@@ -181,4 +181,4 @@
 <div id="braze_banner" >
 	Notre page de documentation en français est en cours de maintenance. Veuillez vous référer à la <a href="https://www.braze.com/docs/">documentation en anglais</a>  pour accéder aux informations les plus récentes.
 </div>
-{%- endif -%}
\ No newline at end of file
+{%- endif -%}
diff --git a/_includes/inapp_message_troubleshooting.md b/_includes/inapp_message_troubleshooting.md
new file mode 100644
index 00000000000..b02682153d9
--- /dev/null
+++ b/_includes/inapp_message_troubleshooting.md
@@ -0,0 +1,104 @@
+## Basic Checks
+
+#### My in-app message wasn't shown for one user
+
+1. Was the user in the segment at session start, when the SDK requests new in-app messages?
+2. Was the user eligible or re-eligible to receive the in-app message per campaign targeting rules?
+3. Was the user affected by a frequency cap?
+4. Was the user in a control group? Check whether your campaign is configured is configured for AB Testing.
+5. Was a different, higher priority in-app message displayed in place of the expected message?
+6. Was my device in the correct orientation specified by the campaign?
+7. Was my message suppressed by the default 30-second minimum time interval between triggers, enforced by the SDK?
+
+#### My in-app message wasn't shown to all users on this platform
+
+1. Is your campaign configured to target either Mobile Apps or Web Browsers as appropriate? As an example, if your campaign only targets Web Browsers, it will not send to Android devices.
+2. Did you implement a custom UI, and is it working as intended? Is there other app-side custom handling or suppression that could be interfering with display? 
+3. Has this particular platform and app version ever shown in-app messages successfully?
+4. Did the trigger take place locally on the device? Note that a REST call can't be used to trigger an in-app message in the SDK.
+
+#### My in-app message wasn't shown for all users
+
+1. Was the Trigger Action set up properly in the dashboard, as well as in the app integration?
+2. Was a different, higher priority in-app message displayed in place of the expected message?
+3. Are you on a recent version of the SDK? Some in-app message types have SDK version requirements.
+4. Have sessions been integrated properly in your integration? Are session analytics working for this app?
+
+For more in-depth discussion of these scenarios, visit [the advanced troubleshooting section](#troubleshooting-in-app-advanced).
+
+## Issues with Impressions and Click Analytics
+
+{% if include.sdk == "iOS" %}
+#### Impressions and Clicks aren't being logged
+
+If you have set an in-app message delegate to manually handle message display or click actions, you must manually [log clicks](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/inappmessage/logclick(buttonid:using:)) and [impressions](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/inappmessage/logimpression(using:)) on the in-app message.
+{% elsif include.sdk == "Android" %}
+#### Impressions and Clicks aren't being logged
+If you have set an in-app message delegate to manually handle message display or click actions, you must manually log clicks and impressions on the in-app message.
+{% endif %}
+
+#### Impressions are lower than expected
+
+Triggers take time to sync to the device on session start, so there can be a race condition if users log an event or purchase right after they start a session. One potential workaround could be changing the campaign to trigger off of session start, then segmenting off the intended event or purchase. Note that this would deliver the in-app message on the next session start after the event has occurred.
+
+## Advanced Troubleshooting {#troubleshooting-in-app-advanced}
+
+Most in-app message issues can be broken down into two main categories: delivery and display. To troubleshoot why an expected in-app message did not display on your device, confirm that the [in-app message was delivered to the device](#troubleshooting-in-app-message-delivery), then [troubleshoot message display](#troubleshooting-in-app-message-display).
+
+### Troubleshooting in-app message delivery {#troubleshooting-in-app-message-delivery}
+
+The SDK requests in-app messages from Braze servers on session start. To check if in-app messages are being delivered to your device, you'll need to make sure that in-app messages are being both requested by the SDK and returned by Braze servers.
+
+#### Check if messages are requested and returned
+
+1. Add yourself as a [test user]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#adding-test-users) on the dashboard.
+2. Set up an in-app message campaign targeted at your user.
+3. Ensure that a new session occurs in your application.
+4. Use the [event user logs]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab) to check that your device is requesting in-app messages on session start. Find the SDK Request associated with your test user's session start event.
+  - If your app was meant to request triggered in-app messages, you should see `trigger` in the **Requested Responses** field under **Response Data**.
+  - If your app was meant to request original in-app messages, you should see  `in_app` in the **Requested Responses** field under **Response Data**.
+5. Use the [event user logs]({{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab) to check if the correct in-app messages are being returned in the response data.<br>![]({% image_buster /assets/img_archive/event_user_log_iams.png %})
+
+##### Troubleshoot messages not being requested
+
+If your in-app messages are not being requested, your app might not be tracking sessions correctly, as in-app messages are refreshed upon session start. Also, be sure that your app is actually starting a session based on your app's session timeout semantics:
+
+![The SDK request found in the event user logs displaying a successful session start event.]({% image_buster /assets/img_archive/event_user_log_session_start.png %})
+
+##### Troubleshoot messages not being returned
+
+If your in-app messages are not being returned, you're likely experiencing a campaign targeting issue:
+
+- Your segment does not contain your user.
+  - Check your user's [**Engagement**]({{ site.baseurl }}/user_guide/engagement_tools/segments/using_user_search/#engagement-tab) tab to see if the correct segment appears under **Segments**.
+- Your user has previously received the in-app message and was not re-eligible to receive it again.
+  - Check the [campaign re-eligibility settings]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/) under the **Delivery** step of the **Campaign Composer** and make sure the re-eligibility settings align with your testing setup.
+- Your user hit the frequency cap for the campaign.
+  - Check the campaign [frequency cap settings]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping) and ensure they align with your testing setup.
+- If there was a control group on the campaign, your user may have fallen into the control group.
+  - You can check if this has happened by creating a segment with a received campaign variant filter, where the campaign variant is set to **Control**, and checking if your user fell into that segment.
+  - When creating campaigns for integration testing purposes, make sure to opt out of adding a control group.
+
+
+### Troubleshooting in-app message display {#troubleshooting-in-app-message-display}
+
+If your app is successfully requesting and receiving in-app messages, but they are not being shown, device-side logic may be preventing display:
+
+{% if include.sdk == "iOS" %}
+- Triggered in-app messages are rate-limited based on the [minimum time interval between triggers]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers), which defaults to 30 seconds.
+{% elsif include.sdk == "Android" %}
+- Triggered in-app messages are rate-limited based on the [minimum time interval between triggers]({{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers), which defaults to 30 seconds.
+{% elsif include.sdk == "Web" %}
+- Triggered in-app messages are rate-limited based on the [minimum time interval between triggers]({{site.baseurl}}/developer_guide/platform_integration_guides/web/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers), which defaults to 30 seconds.
+{% endif %}
+- Failed image downloads will prevent in-app messages with images from displaying. Check your device logs to ensure that image downloads are not failing.
+{% case include.sdk %}
+  {% when "iOS", "Android" %}
+- If you have set a delegate to customize in-app message handling, check your delegate to ensure it is not affecting the in-app message display.
+  {% when "Web" %}
+- If you have custom in-app message handling through `braze.subscribeToInAppMessage` or `appboy.subscribeToNewInAppMessages`, check that subscription to ensure it is not affecting in-app message display.
+{% endcase %}
+{% case include.sdk %}
+  {% when "iOS", "Android" %}
+- If the device orientation does not match the orientation specified by the in-app message, the in-app message will not display. Make sure that your device is in the correct orientation.
+{% endcase %}
\ No newline at end of file
diff --git a/_includes/left_nav_menu.html b/_includes/left_nav_menu.html
index e83dec5dfc5..78726f14832 100644
--- a/_includes/left_nav_menu.html
+++ b/_includes/left_nav_menu.html
@@ -13,7 +13,7 @@
 {%-assign nav_level = 2 -%}
 {%-endunless -%}
 
-<button id="sidebar_toggle" class="btn btn-info d-print-none" href="#" >
+<button id="sidebar_toggle" class="btn btn-info d-print-none" href="#" aria-label="Side Navigation Toggle" title="Side Navigation Toggle">
    <i class="fas fa-chevron-left"></i>
 </button>
 {%- unless hide_nav_filter -%}
@@ -31,7 +31,7 @@
 </div>
 {%- endunless -%}
 
-<nav class="bd-links navbar navbar-expand-lg navbar-light" id="left_navmenu">
+<nav class="bd-links navbar navbar-expand-lg navbar-light" id="left_navmenu" aria-label="Left Navigation" title="Left Navigation">
   {%- unless hide_nav_filter -%}
     <div id="filter-msg"  class="flex-column flex-nowrap d-none"></div>
   {%- endunless -%}
diff --git a/_includes/metrics.md b/_includes/metrics.md
new file mode 100644
index 00000000000..096917d9eb4
--- /dev/null
+++ b/_includes/metrics.md
@@ -0,0 +1,241 @@
+{% if include.metric == "AMP Clicks" %}
+<i>AMP Clicks</i> is the total number of clicks in your AMP HTML email, cumulative of the HTML, plaintext, and AMP HTML versions of the email.
+{% endif %}
+
+{% if include.metric == "AMP Opens" %}
+<i>AMP Opens</i> is the total count for opens in your AMP HTML email and AMP HTML versions of the email.
+{% endif %}
+
+{% if include.metric == "Audience" %}
+<i>Audience</i> is the percentage of users who received a particular message. This number is received from Braze.
+{% endif %}
+
+{% if include.metric == "Bounces" %}
+<i>Bounces</i> is the total number of messages that were unsuccessfully delivered to the intended recipients. 
+{% endif %}
+
+{% if include.metric == "Estimated Real Opens" %}
+<i>Estimated Real Opens</i> is an estimate of how many unique opens there would be if machine opens did not exist, and is the result of a proprietary Braze statistical model.
+{% endif %}
+
+{% if include.metric == "Help" %}
+<i>Help</i> is when a user replied to your message with a <a href="https://braze.com/docs/user_guide/message_building_by_channel/sms/keywords/keyword_handling/#default-opt-in-opt-out-keywords">HELP keyword</a> and was dispatched a HELP auto-response. 
+{% endif %}
+
+{% if include.metric == "Hard Bounce" %}
+A <i>Hard Bounce</i> is when an email fails to deliver to the recipient due to a permanent delivery error. A hard bounce might occur because the domain name doesn't exist or because the recipient is unknown. 
+{% endif %}
+
+{% if include.metric == "Soft Bounce" %}
+A <i>Soft Bounce</i> is when an email fails to deliver to the recipient due to a temporary delivery error, even though the recipient’s email address is valid. A soft bounce might occur because the recipient's inbox is full, the server was down, or the message was too large for the recipient's inbox.
+{% endif %}
+
+{% if include.metric == "Body Click" %}
+Push Story Notifications record a <i>Body Click</i> when the notification is clicked. It will not be recorded when a message is expanded, or for action button clicks.
+{% endif %}
+
+{% if include.metric == "Body Clicks" %}
+<i>Body Clicks</i> occur when a user clicks on a message that doesn't have buttons (Button 1, Button 2) and was created with the traditional editor, and when a message created with the HTML editor or drag-and-drop editor uses <code>brazeBridge.logClick()</code> with no arguments.
+{% endif %}
+
+{% if include.metric == "Button 1 Clicks" %}
+<i>Button 1 Clicks</i> is the total number of clicks on Button 1 of the message.
+{% endif %}
+
+{% if include.metric == "Button 2 Clicks" %}
+<i>Button 2 Clicks</i> is the total number of clicks on Button 2 of the message.
+{% endif %}
+
+{% if include.metric == "Choices Submitted" %}
+<i>Choices Submitted</i> is the total number of choices selected when the user clicks the submit button on the survey question page of a <a href='https://braze.com/docs/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/'>simple survey</a>.
+{% endif %}
+
+{% if include.metric == "Click-to-Open Rate" %}
+<i>Click-to-Open Rate</i> is the percentage of delivered emails that have been opened by a single user or machine at least once, and is only available in the <a href='https://braze.com/docs/user_guide/data_and_analytics/reporting/report_builder/'>Report Builder</a>.
+{% endif %}
+
+{% if include.metric == "Confirmed Deliveries" %}
+<i>Confirmed Deliveries</i> are when the carrier has confirmed the message was delivered to the target phone number.
+{% endif %}
+
+{% if include.metric == "Confidence" %}
+<i>Confidence</i> is the percentage of confidence that a certain variant of a message is outperforming the control group.
+{% endif %}
+
+{% if include.metric == "Confirmation Page Button" %}
+<i>Confirmation Page Button</i> is the total clicks on the call to action button on the confirmation page of a <a href='https://braze.com/docs/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/'>simple survey</a>.
+{% endif %}
+
+{% if include.metric == "Confirmation Page Dismissals" %}
+<i>Confirmation Page Dismissals</i> is the total clicks on the close (x) button on the confirmation page of a <a href='https://braze.com/docs/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/'>simple survey</a>.
+{% endif %}
+
+{% if include.metric == "Conversion Rate" %}
+<i>Conversion Rate</i> is the percentage of times a defined event occurred compared to all recipients of a message. This defined event is determined when you build the campaign.
+{% endif %}
+
+{% if include.metric == "Conversion Window" %}
+<i>Conversion Window</i> is the number of days after receiving the message during which user actions are tracked and attributed to a conversion event. Conversions that occur after this window are not attributed to the conversion event.
+{% endif %}
+
+{% if include.metric == "Conversions (B, C, D)" %}
+<i>Conversions (B, C, D)</i> are additional conversion events added after the primary conversion event. The number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign.
+{% endif %}
+
+{% if include.metric == "Total Conversions" %}
+<i>Total Conversions</i> is the total number of times a user completes a specific conversion event after viewing an in-app message campaign.
+{% endif %}
+
+{% if include.metric == "Deliveries" %}
+<i>Deliveries</i> is the total number of message requests that are accepted by the receiving server. This doesn’t mean the message was delivered to a device, only that the message was accepted by the server. 
+{% endif %}
+
+{% if include.metric == "Deliveries %" %}
+<i>Deliveries %</i> is the percentage of total number of messages (Sends) successfully sent to and received by emailable parties.
+{% endif %}
+
+{% if include.metric == "Delivery Failures" %}
+<i>Delivery Failures</i> are when the SMS couldn't be sent because of queues overflowing (sending SMS at a rate higher than your long or short codes can handle).
+{% endif %}
+
+{% if include.metric == "Direct Opens" %}
+<i>Direct Opens</i> is the total number (and percentage) of push notifications that were directly opened from that push.
+{% endif %}
+
+{% if include.metric == "Emailable" %}
+<i>Emailable</i> is the total number of users who have an email address on record and have explicitly opted in or subscribed.
+{% endif %}
+
+{% if include.metric == "Errors" %}
+<i>Errors</i> is the number of errors returned by webhook events (incremented during the sending process).
+{% endif %}
+
+{% if include.metric == "Failures" %}
+<i>Failures</i> are when the WhatsApp message couldn’t send because the internet service provider returned a hard bounce. A hard bounce signifies a permanent deliverability failure.
+{% endif %}
+
+{% if include.metric == "Influenced Opens" %}
+<i>Influenced Opens</i> is the total number (and percentage) of users who opened the app after the push notification was sent, without directly opening the push.
+{% endif %}
+
+{% if include.metric == "Machine Opens" %}
+<i>Machine Opens</i> includes the proportion of "opens" that are affected by Apple's Mail Privacy Protection (MPP) for iOS 15. For example, if a user opens an email using the Mail app on an Apple device, this will be logged as a <i>Machine Opens</i>.
+{% endif %}
+
+{% if include.metric == "Other Opens" %}
+<i>Other Opens</i> includes emails that haven't been identified as <i>Machine Opens</i>. For example, when a user opens an email on another platform (such as Gmail app on a phone, Gmail on desktop browser), this will be logged as an <i>Other Opens</i>.
+{% endif %}
+
+{% if include.metric == "Opens" %}
+<i>Opens</i> are instances including both <i>Direct Opens</i> and <i>Influenced Opens</i> in which the Braze SDK has determined, using a proprietary algorithm, that a push notification has caused a user to open the app.
+{% endif %}
+
+{% if include.metric == "Opt-Out" %}
+<i>Opt-Out</i> is when a user replied to your message with an <a href="https://braze.com/docs/user_guide/message_building_by_channel/sms/keywords/keyword_handling/#default-opt-in-opt-out-keywords">opt-out keyword</a> and was unsubscribed from your SMS program. 
+{% endif %}
+
+{% if include.metric == "Pending Retry" %}
+<i>Pending Retry</i> is the number of requests that were temporarily rejected, by the receiving server, but still attempted for re-delivery by the email service provider (ESP). The ESP will retry delivery until a timeout period is reached (typically after 72 hours).
+{% endif %}
+
+{% if include.metric == "Primary Conversions (A) or Primary Conversion Event" %}
+<i>Pending Conversions (A)</i> or <i>Primary Conversion Event</i> is the number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign. This defined event is determined by you when building the campaign.
+{% endif %}
+
+{% if include.metric == "Reads" %}
+<i>Reads</i> is when the user reads the WhatsApp message. The user’s read receipts must be “On” for Braze to track reads.
+{% endif %}
+
+{% if include.metric == "Received" %}
+<i>Received</i> is defined differently per channel, and can be when users view the message, users perform a defined trigger action, or the message is sent to the message provider.
+{% endif %}
+
+{% if include.metric == "Rejections" %}
+<i>Rejections</i> are when the SMS has been rejected by the carrier. This can happen for several reasons, including carrier content filtering, availability of the destination device, the phone number is no longer in service, and similar. 
+{% endif %}
+
+{% if include.metric == "Revenue" %}
+<i>Revenue</i> is the total revenue in dollars from campaign recipients within the set <a href='/docs/user_guide/engagement_tools/campaigns/building_campaigns/conversion_events'>primary conversion window</a>.
+{% endif %}
+
+{% if include.metric == "Messages Sent" %}
+<i>Messages Sent</i> is the total number of messages sent in a campaign. After launching a scheduled campaign, this metric will include all messages sent, regardless of whether they have been sent out yet due to rate limiting. This doesn’t mean the message was received or delivered to a device, only that the message was sent.
+{% endif %}
+
+{% if include.metric == "Sent" %}
+<i>Sent</i> is every time a campaign or Canvas step has been launched or triggered, and an SMS has been sent from Braze. It's possible that the SMS didn't reach a user's device due to errors.
+{% endif %}
+
+{% if include.metric == "Sends" %}
+<i>Sends</i> is the total number of messages sent in a campaign. After launching a scheduled campaign, this metric will include all messages sent, regardless of whether they have been sent out yet due to rate limiting. This doesn’t mean the message was received or delivered to a device, only that the message was sent.
+{% endif %}
+
+{% if include.metric == "Sends to Carrier" %}
+<i>Sends to Carrier</i> is deprecated, but will continue to be supported for users that already have it. It's the sum of <i>Confirmed Deliveries</i>, <i>Rejections</i>, and <i>Sends</i> where delivery or rejection wasn’t confirmed by the carrier. This includes instances where carriers don’t provide delivery or rejected confirmation, as some carriers don’t provide this confirmation or can’t do so at the time of send.
+{% endif %}
+
+{% if include.metric == "Spam" %}
+<i>Spam</i> is the total number of emails delivered that were marked as "spam." Braze automatically unsubscribes users that marked an email as spam, and those users won't be targeted by future emails.
+{% endif %}
+
+{% if include.metric == "Survey Page Dismissals" %}
+<i>Survey Page Dismissals</i> is the total clicks on the close (x) button on the survey question page of a <a href='https://braze.com/docs/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/'>simple survey</a>.
+{% endif %}
+
+{% if include.metric == "Survey Submissions" %}
+<i>Survey Submissions</i> is the total clicks on the submit button of a <a href='https://braze.com/docs/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/'>simple survey</a>.
+{% endif %}
+
+{% if include.metric == "Total Clicks" %}
+<i>Total Clicks</i> is the total number (and percentage) of users who clicked within the delivered message.
+{% endif %}
+
+{% if include.metric == "Total Dismissals" %}
+<i>Total Dismissals</i> is the number of times Content Cards from a campaign have been dismissed. If a user dismisses a message twice, they will be only counted once.
+{% endif %}
+
+{% if include.metric == "Total Impressions" %}
+<i>Total Impressions</i> is the number of times the message has been viewed (if a user is shown a message twice, they will be counted twice). This number is a sum of the number of impression events that Braze receives from the SDKs.
+{% endif %}
+
+{% if include.metric == "Total Opens" %}
+<i>Total Opens</i> is the total number of messages that were opened.
+{% endif %}
+
+{% if include.metric == "Total Revenue" %}
+<i>Total Revenue</i> is the total revenue in dollars from campaign recipients within the set primary conversion window.
+{% endif %}
+
+{% if include.metric == "Unique Clicks" %}
+<i>Unique Clicks</i> is the distinct number of recipients who have clicked within a message at least once and is measured by <a href='https://braze.com/docs/help/help_articles/data/dispatch_id/'>dispatch_id</a>.
+{% endif %}
+
+{% if include.metric == "Unique Dismissals" %}
+<i>Unique Dismissals</i> is the number of users who have dismissed Content Cards from a campaign. A user dismissing a Content Card from a campaign multiple times represents one unique dismissal.
+{% endif %}
+
+<!-- Unique Impressions & Unique Recipients have a dedicated section in campaign_analytics.md -->
+
+{% if include.metric == "Unique Impressions" %}
+<i>Unique Impressions</i> is the total number of users who received and viewed a given message in a day.
+{% endif %}
+
+{% if include.metric == "Unique Recipients" %}
+<i>Unique Recipients</i> is the number of unique daily recipients, or users who received a particular message in a day.
+{% endif %}
+
+{% if include.metric == "Unique Opens" %}
+<i>Unique Opens</i> is the total number of delivered messages that have been opened by a single user at least once and are tracked over a seven-day period.
+{% endif %}
+
+{% if include.metric == "Unsubscribers or Unsub" %}
+<i>Unsubscribers</i> or <i>Unsub</i> is the number of messages resulting in an unsubscription. Unsubscriptions occur when a user clicks on the Braze unsubscribe link.
+{% endif %}
+
+{% if include.metric == "Unsubscribes" %}
+<i>Unsubscribes</i> is the number of recipients whose subscription state changed to unsubscribed as a result of clicking the Braze provided unsubscribe URL.
+{% endif %}
+
+{% if include.metric == "Variation" %}
+<i>Variation</i> is the number of variations of a campaign, differing as defined by the creator.
+{% endif %}
\ No newline at end of file
diff --git a/_includes/rate_limits.md b/_includes/rate_limits.md
index bcbdc4c40a1..290224dbbbf 100644
--- a/_includes/rate_limits.md
+++ b/_includes/rate_limits.md
@@ -33,7 +33,7 @@ We apply a rate limit of 1,000 requests per minute to this endpoint, as document
 <!---/users/track-->
 
 {% elsif include.endpoint == "users track" %}
-We apply a base speed limit of 50,000 requests per minute to this endpoint for all customers. Each `/users/track` request can contain up to 75 event objects, 75 attribute objects, and 75 purchase objects. Each object (event, attribute, and purchase arrays) can update one user each. In total, this means a maximum of 225 users can be updated in a single call. In addition, a single user profile can be updated by multiple objects.
+Starting on October 28th, 2024, we apply a base speed limit of 3,000 requests per three seconds to this endpoint for all customers. Each `/users/track` request can contain up to 75 event objects, 75 attribute objects, and 75 purchase objects. Each object (event, attribute, and purchase arrays) can update one user each. In total, this means a maximum of 225 users can be updated in a single call. In addition, a single user profile can be updated by multiple objects.
 
 Different limits apply to customers who have purchased **Monthly Active Users - CY 24-25**. For details on these limits, see [Monthly Active Users - CY 24-25 limits]({{site.baseurl}}/api/endpoints/user_data/post_user_track/#monthly-active-users-cy-24-25).
 
diff --git a/_includes/search_page.html b/_includes/search_page.html
index 7e66dc00926..0b4a821d2c3 100644
--- a/_includes/search_page.html
+++ b/_includes/search_page.html
@@ -38,6 +38,7 @@ <h1 style="padding-top: 40px; color: #212123">Advanced Search</h1>
 					Braze Learning &nbsp;<img
 						src="{{site.baseurl}}/assets/img/braze_learning.png"
 						height="18px"
+						alt="Braze Learning"
 					/>
 					<hr />
 				</div>
diff --git a/_lang/_config_fr.yml b/_lang/_config_fr.yml
index 99618f5bfc8..0584dcf0d21 100644
--- a/_lang/_config_fr.yml
+++ b/_lang/_config_fr.yml
@@ -17,20 +17,11 @@ source: '.'
 
 lab_index_name: "DocSearch_French"
 
-# Allows the DocSearch element to be inspected. Set to true locally, but don't
-# check in in that state, or it will cause undesirable behavior in prod.
-search_debug: false
-
-# For local testing, set to false to increase build time by not pulling partner api
-# and markdown data. MAKE SURE TO TURN BACK ON PRIOR TO COMMIT.
-partner_api: true
-markdown_api: true
-
 # GitHub config
 github_baseurl: 'https://github.com/braze-inc/braze-docs/blob/develop/_lang/fr/'
 
 # Collections directory
-collections_dir: _lang/fr/
+collections_dir: _lang/fr_fr/
 
 
 collections:
diff --git a/_lang/_config_ja.yml b/_lang/_config_ja.yml
index da1201a4e06..dcc0320c350 100644
--- a/_lang/_config_ja.yml
+++ b/_lang/_config_ja.yml
@@ -17,15 +17,6 @@ source: '.'
 
 lab_index_name: "DocSearch_Japanese"
 
-# Allows the DocSearch element to be inspected. Set to true locally, but don't
-# check in in that state, or it will cause undesirable behavior in prod.
-search_debug: false
-
-# For local testing, set to false to increase build time by not pulling partner api
-# and markdown data. MAKE SURE TO TURN BACK ON PRIOR TO COMMIT.
-partner_api: true
-markdown_api: true
-
 # GitHub config
 github_baseurl: 'https://github.com/braze-inc/braze-docs/blob/develop/_lang/ja/'
 
diff --git a/_lang/_config_ko.yml b/_lang/_config_ko.yml
index 33926f2812c..68782b02530 100644
--- a/_lang/_config_ko.yml
+++ b/_lang/_config_ko.yml
@@ -17,15 +17,6 @@ source: '.'
 
 lab_index_name: "DocSearch_Korean"
 
-# Allows the DocSearch element to be inspected. Set to true locally, but don't
-# check in in that state, or it will cause undesirable behavior in prod.
-search_debug: false
-
-# For local testing, set to false to increase build time by not pulling partner api
-# and markdown data. MAKE SURE TO TURN BACK ON PRIOR TO COMMIT.
-partner_api: true
-markdown_api: true
-
 # GitHub config
 github_baseurl: 'https://github.com/braze-inc/braze-docs/blob/develop/_lang/ko/'
 
diff --git a/_lang/fr_fr/_api/api_campaigns.md b/_lang/fr_fr/_api/api_campaigns.md
new file mode 100644
index 00000000000..9d51ce084a4
--- /dev/null
+++ b/_lang/fr_fr/_api/api_campaigns.md
@@ -0,0 +1,49 @@
+---
+nav_title: Campagnes API
+article_title: Campagnes API
+page_order: 5
+description: "Cet article de référence explique comment générer un identifiant de campagne à inclure dans vos appels API et comment configurer cette campagne."
+page_type: reference
+tool: Campaigns
+
+---
+# Campagnes API
+
+> Cet article de référence explique comment générer un `campaign_id` à inclure dans vos appels d’API et comment configurer cette campagne.
+
+Les campagnes API sont généralement utilisées pour l’envoi de messages transactionnels. Lors de la création de campagnes API (et non de [campagnes déclenchées par l'API]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/api_triggered_delivery/)), le tableau de bord de Braze n'est utilisé que pour générer un `campaign_id`, qui vous permet de suivre l'analyse/analytique pour les rapports de campagne. Vous pouvez également générer un ID de variation de message qui est différent pour chaque variante de votre campagne. 
+
+Vous enverrez alors cette information à votre équipe de développement pour l’utiliser dans la requête API, avec les éléments suivants :
+- Copie de campagne
+- Appartenance à une audience
+- Ressources
+
+Après le début de la campagne, vous pouvez voir les résultats dans le tableau de bord. Les campagnes API utilisent les [API d'envoi de messages de]({{site.baseurl}}/api/endpoints/messaging/) Braze, qui disposent des mêmes options de reporting détaillé et de reciblage que les campagnes créées entièrement via le tableau de bord.
+
+{% alert warning %}
+Tous les utilisateurs sont éligibles pour les campagnes API, même ceux de votre groupe de contrôle global, étant donné que les campagnes API sont généralement transactionnelles. Un en-tête de [liste de désabonnement en un clic]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#list-unsubscribe) n'est pas ajouté à ces envois. Si vous souhaitez ajouter un en-tête de liste de désabonnement en un seul clic à toutes les campagnes API, contactez votre gestionnaire satisfaction client.
+{% endalert %}
+
+## Créer une nouvelle campagne
+
+Allez dans **Messagerie** > **Campagnes** et cliquez sur **Créer une campagne**, puis sélectionnez **Campagnes API**. Vous pouvez maintenant passer à la configuration de votre campagne API.
+
+Une [campagne déclenchée par l'API]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/api_triggered_delivery/) est différente d'une campagne API.
+
+## Configurer votre campagne
+
+Pour configurer votre campagne, procédez comme suit :
+
+1. Ajoutez un titre descriptif pour pouvoir trouver les résultats sur notre page Campagnes après avoir envoyé vos messages.
+2. Cliquez sur **Ajouter un message** et ajoutez les types d'envoi de messages qui seront inclus dans votre campagne API. Ceci vous permettra de générer un `campaign_id` et un ID de variation de message qui changera pour chaque canal que vous ajoutez. 
+3. Vous pouvez éventuellement ajouter un événement de conversion pour suivre les conversions de l’utilisateur sur une action spécifique ou un objectif de campagne.
+4. Cliquez sur **Enregistrer la campagne** et vous êtes prêt à commencer votre campagne API !
+
+## Appels API
+
+Après l’enregistrement de votre campagne API, intégrez ce qui suit dans votre requête API : 
+- Les champs `campaign_id` générés avec votre demande d'API sont indiqués dans les [points de terminaison d'envoi de messages.][2]
+- Un [objet message]({{site.baseurl}}/api/objects_filters/#messaging-objects) pour chaque plate-forme incluse dans la campagne. Dans l’objet de message, renseignez l’ID de variation de message. Cela permet de spécifier que les statistiques doivent être collectées et affichées sous cette variante. Les objets de message suivants sont pris en charge : Android, Cartes de contenu, e-mail, iOS, Kindle, SMS/MMS, notification push Web et webhook.
+
+[2]: {{site.baseurl}}/api/endpoints/messaging/#send-endpoints
+
diff --git a/_lang/fr_fr/_api/api_campaigns/transactional_api_campaign.md b/_lang/fr_fr/_api/api_campaigns/transactional_api_campaign.md
new file mode 100644
index 00000000000..42d3aae7378
--- /dev/null
+++ b/_lang/fr_fr/_api/api_campaigns/transactional_api_campaign.md
@@ -0,0 +1,5 @@
+---
+nav_title: Campagnes transactionnelles
+layout: redirect
+redirect_to: /docs/user_guide/message_building_by_channel/email/transactional_message_api_campaign/
+---
diff --git a/_lang/fr_fr/_api/api_limits.md b/_lang/fr_fr/_api/api_limits.md
new file mode 100644
index 00000000000..6545f9a2048
--- /dev/null
+++ b/_lang/fr_fr/_api/api_limits.md
@@ -0,0 +1,173 @@
+---
+nav_title: Limites de débit
+article_title: Limites de débit de l’API
+page_order: 4.5
+description: "Cet article de référence couvre les limites de débit de l’API pour l’infrastructure API Braze."
+page_type: reference
+
+---
+
+# Limites de débit
+
+> L’infrastructure API Braze est conçue pour gérer des volumes élevés de données sur l’ensemble de notre base de clients. À cette fin, nous appliquons des limites de débit à l’API par espace de travail. 
+
+Une limite de débit correspond au nombre de demandes que l’API peut recevoir sur une période donnée. De nombreux incidents de déni de service basés sur la charge dans les grands systèmes sont involontaires, causés par des erreurs dans les logiciels ou les configurations, et non par des attaques malveillantes. Les limites de débit permettent de vérifier que de telles erreurs ne privent pas nos clients des ressources de l'API de Braze. Si trop de demandes sont envoyées dans un délai donné, vous risquez de recevoir des réponses d’erreur avec un code de statut de `429`, qui indique que la limite de débit a été atteinte.
+
+{% alert warning %}
+Les limites de débit de l’API sont sujettes à modification en fonction de l’utilisation propre à notre système. Nous encourageons des limites raisonnables lors de l’appel d’API afin d’éviter tout dommage ou toute mauvaise utilisation.
+{% endalert %}
+
+## Limites de débit par type de demande
+
+Le tableau suivant répertorie les limites de débit d’API par défaut pour différents types de demandes. Ces limites par défaut peuvent être augmentées sur demande. Contactez votre gestionnaire du succès des clients pour plus d’informations.
+
+{% alert note %}
+Les requêtes qui ne figurent pas dans ce tableau partagent une limite de débit totale par défaut de 250 000 requêtes par heure.
+{% endalert %}
+
+| Type de demande | Limite de débit par défaut de l’API |
+| --- | --- |
+| [`/users/track`][10] | **Demandes :** 50 000 demandes par minute.<br><br>**Traitement par lot :** 75 événements, 75 achats et 75 attributs par requête d'API. Pour en savoir plus, consultez la rubrique [Mise en lot des demandes de suivi des utilisateurs](#batch-user-track). |
+| [`/users/export/ids`][11] | 2 500 demandes par minute. |
+| [`/users/delete`][12]<br>[`/users/alias/new`][13]<br>[`/users/alias/update`][45]<br>[`/users/identify`][14]<br>[`/users/merge`][44] | 20 000 demandes par minute, partagées entre les endpoints. |
+| [`/users/external_id/rename`][20] | 1 000 demandes par minute. |
+| [`/users/external_id/remove`][21] | 1 000 demandes par minute. |
+| [`/events/list`][15] | 1 000 demandes par heure, partagées avec l’endpoint `/purchases/product_list`. |
+| [`/purchases/product_list`][16] | 1 000 demandes par heure, partagées avec l’endpoint `/events/list`. |
+| [`/campaigns/data_series`][17.3] | 50 000 demandes par minute. |
+| [`/messages/send`][17]<br>[`/campaigns/trigger/send`][17.1]<br>[`/canvas/trigger/send`][17.2]| 250 requêtes par minute pour les appels de diffusion (lorsque vous ne spécifiez qu'un segment ou une audience connectée). Sinon, 250 000 requêtes par heure réparties entre les endpoints. |
+| [`/sends/id/create`][18] | 100 demandes par jour. |
+| [`/subscription/status/set`][19] | 5 000 demandes par minute. |
+| [`/preference_center/v1/{preferenceCenterExternalId}/url/{userId}`][26]<br>[`/preference_center/v1/list`][27]<br>[`/preference_center/v1/{preferenceCenterExternalId}`][28] | 1 000 demandes par minute, par espace de travail. |
+| [`/preference_center/v1`][29]<br>[`/preference_center/v1/{preferenceCenterExternalId}`][30] | 10 demandes par minute, par espace de travail. |
+| [`/catalogs/{catalog_name}`][31]<br>[`/catalogs`][32]<br>[`/catalogs`][33] | 50 demandes par minute, partagées entre les endpoints. |
+| [`/catalogs/{catalog_name}/items`][34]<br>[`/catalogs/{catalog_name}/items`][35]<br>[`/catalogs/{catalog_name}/items`][36] | 16 000 requêtes par minute réparties entre les endpoints. |
+| [`/catalogs/{catalog_name}/items/{item_id}`][37]<br>[`/catalogs/{catalog_name}/items/{item_id}`][38]<br>[`/catalogs/{catalog_name}/items`][39]<br>[`/catalogs/{catalog_name}/items/{item_id}`][40]<br>[`/catalogs/{catalog_name}/items/{item_id}`][41] | 50 demandes par minute, partagées entre les endpoints. |
+| [`/scim/v2/Users/{id}`][22]<br>[`/scim/v2/Users?filter={userName@example.com}`][43]<br>[`/scim/v2/Users/{id}`][25]<br>[`/scim/v2/Users/{id}}`][24]<br>[`/scim/v2/Users/`][23] | 5 000 demandes par jour, partagées entre les endpoints. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+<!-- Add during CDI endpoints GA
+| [`/cdi/integrations`][46] | 50 requests per minute. |
+| [`/cdi/integrations/{integration_id}/sync`][47] | 20 requests per minute. |
+| [`/cdi/integrations/{integration_id}/job_sync_status`][48] | 100 requests per minute. |
+-->
+
+## Traitement des demandes d’API par lot
+
+Les API de Braze sont créées pour prendre en charge la mise en lots. Grâce au traitement par lot, Braze peut récupérer autant de données que possible en un seul appel d’API afin de limiter le nombre d’appels d’API à passer. Il est plus efficace pour Braze de traiter les données par lots que de les traiter par appel. Par exemple, la gestion de 1 000 appels d’API par lots nécessite moins de ressources que la gestion de 75 000 appels individuels. L’utilisation du traitement par lot est extrêmement importante pour les applications qui peuvent nécessiter plus de 75 000 appels par heure.
+
+{% alert note %}
+Selon les besoins des clients qui utilisent les capacités de traitement par lot de l’API, des augmentations de limite de débit API REST peuvent être envisagées.
+{% endalert %}
+
+### Requêtes User Track (Suivi Utilisateur) en lot {#batch-user-track}
+
+Chaque demande `/users/track` peut contenir jusqu’à 75 objets d’événement, 75 objets d’attributs et 75 objets d’achats. Chaque objet (événement, attribut et tableau d’achat) peut mettre à jour un utilisateur chacun. Au total, cela signifie qu’un maximum de 225 utilisateurs peuvent être mis à jour en un seul appel. En outre, un profil utilisateur unique peut être mis à jour par plusieurs objets.
+
+Les demandes adressées à cet endpoint commencent généralement à traiter dans cet ordre : 
+
+1. Attributs
+2. Événements
+3. Achats
+
+### Demandes de traitement par lot aux endpoints de messagerie
+
+Une seule demande adressée aux [endpoints de messages][1] peut atteindre l'un des éléments suivants :
+
+- Jusqu’à 50 `external_ids` spécifiques, chacun avec des paramètres de message individuels
+- Un segment de toute taille créé dans le tableau de bord de Braze, spécifié par son `segment_id`
+- Les utilisateurs qui correspondent à des filtres d'audience supplémentaires de toute taille, définis dans la demande comme un objet d'[audience connecté.][2] 
+
+### Exemple de demande de lot
+
+L’exemple suivant utilise `external_id` pour effectuer un appel API pour les e-mails et SMS.
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/v2/subscription/status/set' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "subscription_groups":[
+    {
+      "subscription_group_id":"subscription_group_identifier",
+      "subscription_state":"subscribed",
+      "external_ids":["example-user","example1@email.com"]
+    },
+    {
+      "subscription_group_id":"subscription_group_identifier",
+      "subscription_state":"subscribed",
+      "external_ids":["example-user","example1@email.com"]
+    }
+  ]
+}
+```
+
+## Surveiller vos limites de débit
+
+Chaque demande API envoyée à Braze renvoie les informations suivantes dans les en-têtes de réponse :
+
+Nom d’en-tête             | Description
+----------------------- | -----------------------
+`X-RateLimit-Limit`     | Nombre maximum de demandes que vous pouvez effectuer dans un intervalle spécifié (votre limite de débit).
+`X-RateLimit-Remaining` | Nombre de demandes restant dans la fenêtre de limite de débit actuelle.
+`X-RateLimit-Reset`     | Heure à laquelle la fenêtre de limite de débit actuelle se réinitialise en secondes d’époque UTC.
+{: .reset-td-br-1 .reset-td-br-2}
+
+Ces informations sont intentionnellement incluses dans l’en-tête de la réponse à la demande API plutôt que sur le tableau de bord de Braze. Cela permet à votre système de mieux réagir en temps réel lorsque vous interagissez avec notre API. Par exemple, si la valeur de `X-RateLimit-Remaining` passe en dessous d'un certain seuil, vous pouvez ralentir l'envoi pour vous assurer que tous les e-mails transactionnels sont envoyés. Ou, si elle atteint zéro, vous voudrez peut-être suspendre tous les envois jusqu’à ce que le temps spécifié dans `X-RateLimit-Reset` s’écoule.
+
+Si vous avez des questions sur les limites de l'API, contactez votre gestionnaire satisfaction client ou ouvrez un [ticket d'assistance.][support]
+
+### Délai optimal entre les endpoints
+
+{% alert note %}
+Nous vous recommandons de laisser un délai de 5 minutes entre des appels d’endpoint consécutifs pour réduire les possibilités d’erreur.
+{% endalert %}
+
+Il est crucial de comprendre le délai optimal entre les endpoints lors de la réalisation d’appels consécutifs vers l’API Braze. Des problèmes surviennent lorsque les endpoints dépendent de la réussite du traitement d’autres endpoints, et s’ils sont appelés trop tôt, ils peuvent provoquer des erreurs. Par exemple, si vous attribuez un alias à un utilisateur par l'intermédiaire de notre point d'accès `/user/alias/new`, puis que vous utilisez cet alias pour envoyer un événement personnalisé par l'intermédiaire de notre point d'accès `/users/track`, combien de temps devez-vous attendre ?
+
+Dans des conditions normales, le temps pour que la cohérence éventuelle de nos données se produise est de 10 à 100 ms (1/10 d’une seconde). Toutefois, dans certains cas, il faut plus de temps pour que cette cohérence se produise. Nous vous recommandons donc de prévoir un délai de 5 minutes entre les appels suivants afin de minimiser la probabilité d'une erreur.
+
+[1]: {{site.baseurl}}/api/endpoints/messaging/
+[2]: {{site.baseurl}}/api/objects_filters/connected_audience/
+[support]: {{site.baseurl}}/braze_support/
+[10]: {{site.baseurl}}/api/endpoints/user_data/post_user_track/
+[11]: {{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/
+[12]: {{site.baseurl}}/api/endpoints/user_data/post_user_delete/
+[13]: {{site.baseurl}}/api/endpoints/user_data/post_user_alias/
+[14]: {{site.baseurl}}/api/endpoints/user_data/post_user_identify/
+[15]: {{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events/
+[16]: {{site.baseurl}}/api/endpoints/export/purchases/get_list_product_id/
+[17]: {{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_messages/
+[17.1]: {{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns/
+[17.2]: {{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/
+[17.3]: {{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_analytics/
+[18]: {{site.baseurl}}/api/endpoints/messaging/send_messages/post_create_send_ids/
+[19]: {{site.baseurl}}/api/endpoints/subscription_groups/post_update_user_subscription_group_status/
+[20]: {{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_rename/
+[21]: {{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_remove/
+[22]: {{site.baseurl}}/get_see_user_account_information/
+[23]: {{site.baseurl}}/post_create_user_account/
+[24]: {{site.baseurl}}/delete_existing_dashboard_user/
+[25]: {{site.baseurl}}/post_update_existing_user_account/
+[26]: {{site.baseurl}}/api/endpoints/preference_center/get_create_url_preference_center/
+[27]: {{site.baseurl}}/api/endpoints/preference_center/get_list_preference_center/
+[28]: {{site.baseurl}}/api/endpoints/preference_center/get_view_details_preference_center/
+[29]: {{site.baseurl}}/api/endpoints/preference_center/post_create_preference_center/
+[30]: {{site.baseurl}}/api/endpoints/preference_center/put_update_preference_center/
+[31]: {{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/delete_catalog/
+[32]: {{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/get_list_catalogs/
+[33]: {{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog/
+[34]: {{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk/
+[35]: {{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk/
+[36]: {{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk/
+[37]: {{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item/
+[38]: {{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details/
+[39]: {{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk/
+[40]: {{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item/
+[41]: {{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item/
+[43]: {{site.baseurl}}/get_search_existing_dashboard_user_email/
+[44]: {{site.baseurl}}/api/endpoints/user_data/post_users_merge/
+[45]: {{site.baseurl}}/api/endpoints/user_data/post_users_alias_update/
+[46]: {{site.baseurl}}/api/endpoints/cdi/get_integration_list/
+[47]: {{site.baseurl}}/api/endpoints/cdi/job_sync/
+[48]: {{site.baseurl}}/api/endpoints/cdi/job_sync_status/
diff --git a/_lang/fr_fr/_api/basics.md b/_lang/fr_fr/_api/basics.md
new file mode 100644
index 00000000000..848515cdf31
--- /dev/null
+++ b/_lang/fr_fr/_api/basics.md
@@ -0,0 +1,406 @@
+---
+nav_title: "Overview API"
+article_title: Overview API
+page_order: 2.1
+description: "Cet article de référence couvre les fondamentaux de l’API, y compris ce qu’est une API REST, sa terminologie et un aperçu des clés API."
+page_type: reference
+alias: /api/api_key/
+---
+
+# Overview API
+
+> Cet article de référence couvre les bases de l'API, y compris la terminologie commune et un aperçu des clés de l'API REST, des permissions et de la manière de les sécuriser.
+
+## Collection d’API REST de Braze
+
+| Collection                                                                 | Objectif                                                                               |
+|----------------------------------------------------------------------------|---------------------------------------------------------------------------------------|
+| [Catalogues]({{site.baseurl}}/api/endpoints/catalogs/)                       | Créez et gérez des catalogues et des éléments de catalogue à référencer dans vos campagnes Braze.    |
+| [Ingestion de données cloud]({{site.baseurl}}/api/endpoints/cdi/)                | Gérez les intégrations et les synchronisations de votre entrepôt de données.                                    |
+| [Listes et adresses e-mail]({{site.baseurl}}/api/endpoints/email/)         | Configurez et gérez la synchronisation bidirectionnelle entre Braze et vos paramètres d'e-mail.           |
+| [Exporter]({{site.baseurl}}/api/endpoints/export/)                           | Accédez et exportez divers détails de vos campagnes, Canvas, KPI, et plus encore.        |
+| [Messages]({{site.baseurl}}/api/endpoints/messaging/)                      | Planifiez, envoyez et gérez vos campagnes et vos canevas.                               |
+| [Centre de préférences]({{site.baseurl}}/api/endpoints/preference_center/)     | Créez votre centre de préférences et actualisez son style.                            |
+| [SCIM]({{site.baseurl}}/api/endpoints/scim/)                               | Gérer les identités des utilisateurs dans les applications et services basés sur le cloud.                      |
+| [SMS]({{site.baseurl}}/api/endpoints/sms/)                                 | Gérez les numéros de téléphone de vos utilisateurs dans vos groupes d'abonnements.                         |
+| [Groupes d’abonnement]({{site.baseurl}}/api/endpoints/subscription_groups/) | Répertoriez et mettez à jour les groupes d'abonnement SMS et e-mail stockés dans le tableau de bord de Braze. |
+| [Modèles]({{site.baseurl}}/api/endpoints/templates/)                     | Créez et mettez à jour des modèles pour les envois de messages par e-mail et les blocs de contenu.                   |
+| [Données utilisateur]({{site.baseurl}}/api/endpoints/user_data/)                     | Identifiez, suivez et gérez vos utilisateurs.                                               |
+{: .reset-td-br-1 .reset-td-br-2}
+
+## Définitions relatives aux API
+
+Voici un aperçu des termes que vous pouvez rencontrer dans la documentation de l’API REST de Braze.
+
+### Endpoints
+
+Braze gère un certain nombre d'instances différentes pour notre tableau de bord et nos endpoints REST. Une fois votre compte provisionné ; vous vous connecterez à l’une des URL suivantes. Utilisez le bon Endpoint REST en vous basant sur l’instance qui vous a été provisionnée. Si vous n'êtes pas sûr, ouvrez un \[ticket d'assistance]\[support] ou utilisez le tableau suivant pour faire correspondre l'URL du tableau de bord que vous utilisez au point de terminaison REST correct.
+
+{% alert important %}
+Lorsque vous utilisez des endpoints pour les appels API, utilisez l'endpoint REST.
+
+Pour l’intégration SDK, utilisez l’[endpoint SDK]({{site.baseurl}}/user_guide/administrative/access_braze/sdk_endpoints/) et non pas l’endpoint REST.
+{% endalert %}
+
+|Instance|URL|Endpoint REST|Endpoint SDK|
+|---|---|---|
+|US-01| `https://dashboard-01.braze.com` | `https://rest.iad-01.braze.com` | `sdk.iad-01.braze.com` |
+|US-02| `https://dashboard-02.braze.com` | `https://rest.iad-02.braze.com` | `sdk.iad-02.braze.com` |
+|US-03| `https://dashboard-03.braze.com` | `https://rest.iad-03.braze.com` | `sdk.iad-03.braze.com` |
+|US-04| `https://dashboard-04.braze.com` | `https://rest.iad-04.braze.com` | `sdk.iad-04.braze.com` |
+|US-05| `https://dashboard-05.braze.com` | `https://rest.iad-05.braze.com` | `sdk.iad-05.braze.com` |
+|US-06| `https://dashboard-06.braze.com` | `https://rest.iad-06.braze.com` | `sdk.iad-06.braze.com` |
+|US-07| `https://dashboard-07.braze.com` | `https://rest.iad-07.braze.com` | `sdk.iad-07.braze.com` |
+|US-08| `https://dashboard-08.braze.com` | `https://rest.iad-08.braze.com` | `sdk.iad-08.braze.com` |
+|EU-01| `https://dashboard-01.braze.eu` | `https://rest.fra-01.braze.eu` | `sdk.fra-01.braze.eu` |
+|EU-02| `https://dashboard-02.braze.eu` | `https://rest.fra-02.braze.eu` | `sdk.fra-02.braze.eu` |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+### Limites de l’API
+
+Pour la plupart des API, la limite de débit par défaut définie par Braze est de 250 000 requêtes par heure. Cependant, certains types de requêtes ont leur propre limite de débit pour une meilleure gestion des grands volumes de données de notre base client. Consultez les []({{site.baseurl}}/api/api_limits/)limites de débit de l’API]({{site.baseurl}}/api/api_limits/) pour plus d’informations
+
+### ID utilisateur 
+
+- **ID externe**: Le `external_id` sert d’identifiant utilisateur unique pour lequel vous soumettez des données. Cet identifiant doit être identique à celui que vous avez défini dans le SDK Braze afin d’éviter de créer plusieurs profils pour le même utilisateur.
+- **ID de l'utilisateur de Braze**: `braze_id` sert d'identifiant unique de l'utilisateur, défini par Braze. Cet identifiant peut être utilisé pour supprimer des utilisateurs via l'API REST, en plus des external_ids.
+
+Pour plus d'informations, consultez les articles suivants en fonction de votre plateforme : [iOS][9], [Android][10] et [Web.][13]
+
+## Clé API REST
+
+Une clé d’interface de programmation d’application REST (clé API REST) est un code unique qui est passé dans une API pour authentifier l’appel API et identifier l’application ou l’utilisateur d’appel. L’accès API s’effectue à l’aide des requêtes Web HTTPS dans l’endpoint de l’API REST de votre entreprise.  Chez Braze, nous utilisons conjointement les clés API REST et nos clés d’identification App pour accéder aux données, et les suivre, les envoyer, les exporter et les analyser afin de vous assurer que tout fonctionne bien de votre côté et du nôtre.
+
+Les espaces de travail et les clés API vont de pair chez Braze. Les espaces de travail sont conçus pour héberger des versions de la même application sur plusieurs plateformes. De nombreux clients utilisent également des espaces de travail pour contenir des versions gratuites et premium de leurs applications sur la même plateforme. Comme vous pouvez le constater, ces espaces de travail utilisent également l’API REST et possèdent leurs propres clés API REST. Ces clés peuvent être personnalisées individuellement pour inclure l’accès à des endpoints spécifiques sur l’API. Chaque appel à l’API doit inclure une clé ayant accès à l’endpoint.
+
+Nous faisons référence à la clé API REST et à la clé API de l’espace de travail en tant que `api_key`. Le `api_key` est inclus dans chaque requête en tant qu'en-tête de requête et agit comme une clé d'authentification qui vous permet d'utiliser nos API REST. Ces API REST sont utilisées pour suivre les utilisateurs, envoyer des messages, exporter des données utilisateur, etc. Quand vous créez une nouvelle clé API REST, vous devez lui accorder l’accès à des endpoints spécifiques. En affectant des autorisations spécifiques à une clé API, vous pouvez limiter de façon précise les appels qu’une clé API peut authentifier.
+
+![Panneau des clés API REST sur la page Clés API.][27]
+
+{% alert tip %}
+En plus des clés API REST, il existe un troisième type appelé Clés d’identification qui permet de référencer des objets spécifiques tels que des applications, des modèles, des Canvas, des campagnes, des cartes de contenu et des segments de l’API. Pour plus d’informations, consultez la rubrique [Types d’identifiant API]({{site.baseurl}}/api/identifier_types/).
+{% endalert %}
+
+### Autorisations de clé API REST
+
+Les autorisations de clés API sont des autorisations que vous pouvez affecter à un utilisateur ou un groupe pour limiter leur accès à certains appels API. Pour afficher la liste des autorisations de votre clé API, allez dans **Paramètres** > **Clés API**, et sélectionnez votre clé API.
+
+{% tabs %}
+{% tab Données de l'utilisateur %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `users.track` | [`/users/track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) | Enregistrer les attributs utilisateur, les événements personnalisés et les achats. | 
+| `users.delete` | [`/users/delete`]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/) | Supprimer un utilisateur. |
+| `users.alias.new` | [`/users/alias/new`]({{site.baseurl}}/api/endpoints/user_data/post_user_alias/) |Créer un nouvel alias pour un utilisateur existant. |
+| `users.identify` | [`/users/identify`]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/) |Identifier un utilisateur alias d'un ID externe. |
+| `users.export.ids` | [`/users/export/ids`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/) |Extraire les données de profil utilisateur par ID d'utilisateur. |
+| `users.export.segment` | [`/users/export/segment`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/) |Demande d'informations sur le profil utilisateur par segmentation. | 
+| `users.merge` | [`/users/merge`]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/) | Fusionne deux utilisateurs existants. |
+| `users.external_ids.rename` | [`/users/external_ids/rename`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_rename/) | Changer l’ID externe d’un utilisateur existant. |
+| `users.external_ids.remove` | [`/users/external_ids/remove`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_remove/) | Supprimer l’ID externe d’un utilisateur existant. |
+| `users.alias.update` | [`/users/alias/update`]({{site.baseurl}}/api/endpoints/user_data/post_users_alias_update/) | Mettre à jour un alias pour un utilisateur existant. |
+| `users.export.global_control_group` | [`/users/export/global_control_group`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_global_control_group/) | Extraire les données des profils d'utilisateur dans le groupe de contrôle global. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+ {% endtab %}
+ {% tab E-mail %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `email.unsubscribe` | [`/email/unsubscribes`]({{site.baseurl}}/api/endpoints/email/get_query_unsubscribed_email_addresses/) | Extraire les adresses e-mail désinscrites.  |
+| `email.status` | [`/email/status`]({{site.baseurl}}/api/endpoints/email/post_email_subscription_status/) | Modifier l’état de l’adresse e-mail. |
+| `email.hard_bounces` | [`/email/hard_bounces`]({{site.baseurl}}/api/endpoints/email/get_list_hard_bounces/) | Extraire les adresses e-mail ayant reçu un échec d'envoi définitif. |
+| `email.bounce.remove` | [`/email/bounce/remove`]({{site.baseurl}}/api/endpoints/email/post_remove_hard_bounces/) | Supprimer des adresses e-mail de votre liste d'e-mails ayant reçu un échec d'envoi définitif. |
+| `email.spam.remove` | [`/email/spam/remove`]({{site.baseurl}}/api/endpoints/email/post_remove_spam/) | Supprimer les adresses e-mail de votre liste de spam. |
+| `email.blacklist` | [`/email/blacklist`]({{site.baseurl}}/api/endpoints/email/post_blacklist/) | Liste de blocage des adresses e-mail. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Messages %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `messages.send` | [`/messages/send `]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_messages/) | Envoyez un message immédiat à des utilisateurs spécifiques. |
+| `messages.schedule.create` | [`/messages/schedule/create`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_schedule_messages/) | Planifier un message à envoyer à une heure précise. |
+| `messages.schedule.update` | [`/messages/schedule/update`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_update_scheduled_messages/) | Mettre à jour un message planifié. |
+| `messages.schedule.delete` | [`/messages/schedule/delete`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages/) | Supprimer un message planifié. |
+| `messages.schedule_broadcasts` | [`/messages/scheduled_broadcasts`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/get_messages_scheduled/) | Extraire tous les messages de diffusion programmés. |
+| `messages.live_activity.update` | [`/messages/live_activity/update`]({{site.baseurl}}/api/endpoints/messaging/live_activity/update/) | Mettre à jour une activité iOS Live. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Campagnes %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `campaigns.trigger.send` | [`/campaigns/trigger/send`]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns/) | Déclencher l’envoi d’une campagne existante. |
+| `campaigns.trigger.schedule.create` | [`/campaigns/trigger/schedule/create`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns/) | Planifier le futur envoi d’une campagne avec une livraison déclenchée par API. |
+| `campaigns.trigger.schedule.update` | [`/campaigns/trigger/schedule/update`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns/) | Mettre à jour une campagne planifiée avec une livraison déclenchée par API. |
+| `campaigns.trigger.schedule.delete` | [`/campaigns/trigger/schedule/delete`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages/) |Supprimez une campagne planifiée avec une réception/distribution déclenchée par l'API. |
+| `campaigns.list` | [`/campaigns/list`]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaigns/) | Extraire la liste des campagnes. |
+| `campaigns.data_series` | [`/campaigns/data_series`]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_analytics/) | Extraire les données d'analyse d'une campagne sur une période donnée. |
+| `campaigns.details` | [`/campaigns/details`]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/) | Extraire les données d’une campagne spécifique. |
+| `sends.data_series` | [`/sends/data_series`]({{site.baseurl}}/api/endpoints/export/campaigns/get_send_analytics/) | Extraire l’analyse des messages envoyés sur une période donnée. |
+| `sends.id.create` | [`/sends/id/create`]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_create_send_ids/) | Créez un ID d'envoi pour le suivi de l'envoi des messages. |
+| `campaigns.url_info.details` | [`/campaigns/url_info/details`]({{site.baseurl}}) | Extraire les données des URL d’une variation de message donnée dans une campagne. |
+| `transactional.send` | [`/transactional/v1/campaigns/{campaign_id}/send`]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_transactional_message/) | Permet d'envoyer des messages transactionnels à l'aide de l'endpoint de messagerie transactionnelle. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endtab %}
+{% tab Canvas %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `canvas.trigger.send` | [`/canvas/trigger/send`]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/) | Déclencher l’envoi d’un canvas existant. |
+| `canvas.trigger.schedule.create` | [`/canvas/trigger/schedule/create`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases/) | Planifier le futur envoi d’un canvas avec un envoi déclenché par API. |
+| `canvas.trigger.schedule.update` | [`/canvas/trigger/schedule/update`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases/) | Mettre à jour un canvas planifié avec un envoi déclenché par API. |
+| `canvas.trigger.schedule.delete` | [`/canvas/trigger/schedule/delete`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases/)| Supprimer un canvas programmé avec un envoi déclenché par API. |
+| `canvas.list` | [`/canvas/list`]({{site.baseurl}}/api/endpoints/export/canvas/get_canvases/) |  Extraire la liste des Canvas. |
+| `canvas.data_series` | [`/canvas/data_series`]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_analytics/) | Extraire l'analyse de Canvas sur une période donnée. |
+| `canvas.details` | [`/canvas/details`]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/) | Extraire les données d’un Canvas spécifique. |
+| `canvas.data_summary` | [`/canvas/data_summary`]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_analytics_summary/) | Extraire les cumuls des analyses de Canvas sur une période donnée. |
+| `canvas.url_info.details` | [`/canvas/url_info/details`]({{site.baseurl}}/get_canvas_link_alias/) | Demande d'informations sur l'URL d'une variation de message spécifique au sein d'une étape du canvas. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Segmentations %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `segments.list` | [`/segments/list`]({{site.baseurl}}/api/endpoints/export/segments/get_segment/) | Demande d'une liste de segments. |
+| `segments.data_series` | [`/segments/data_series`]({{site.baseurl}}/api/endpoints/export/segments/get_segment_analytics/) | Demande d'analyses/analytiques de segments sur une période donnée. |
+| `segments.details` | [`/segments/details`]({{site.baseurl}}/api/endpoints/export/segments/get_segment_details/) | Demande de détails sur un segment spécifique. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Achats %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `purchases.product_list` | [`/purchases/product_list`]({{site.baseurl}}/api/endpoints/export/purchases/get_list_product_id/) | Extraire la liste des produits achetés dans votre application. |
+| `purchases.revenue_series` | [`/purchases/revenue_series`]({{site.baseurl}}/api/endpoints/export/purchases/get_revenue_series/) | Extraire le montant total dépensé par jour dans votre application sur une période donnée. |
+| `purchases.quantity_series` | [`/purchases/quantity_series`]({{site.baseurl}}/api/endpoints/export/purchases/get_number_of_purchases/) | Extraire le nombre total d’achats effectués par jour dans votre application sur une période donnée. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Evénements %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `events.list` | [`/events/list`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events/) | Extraire la liste des événements personnalisés. |
+| `events.data_series` | [`/events/data_series`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events_analytics/) | Extraire les occurrences d’un événement personnalisé sur une période donnée. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Fil d'actualité %}
+
+{% alert note %}
+Le Fil d’actualité est obsolète. Braze recommande aux clients qui utilisent notre outil de fil d’actualités de passer à notre canal de communication de cartes de contenu : il est plus flexible, plus personnalisable et plus fiable. Consultez le [guide de migration]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/migrating_from_news_feed/) pour en savoir plus.
+{% endalert %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `feed.list` | [`/feed/list`]({{site.baseurl}}/api/endpoints/export/news_feed/get_news_feed_cards/) | Extraire la liste des cartes de fil d’actualité. |
+| `feed.data_series` | [`/feed/data_series`]({{site.baseurl}}/api/endpoints/export/news_feed/get_news_feed_card_analytics/) | Extraire les analyses du fil d’actualité sur une période donnée. |
+| `feed.details` | [`/feed/details`]({{site.baseurl}}/api/endpoints/export/news_feed/get_news_feed_card_details/) | Extraire les données d'un fil d’actualité spécifique. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Sessions %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `sessions.data_series` | [`/sessions/data_series`]({{site.baseurl}}/api/endpoints/export/sessions/get_sessions_analytics/) | Extraire les sessions par jour sur une période donnée. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab ICP %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `kpi.dau.data_series` | [`/kpi/dau/data_series`]({{site.baseurl}}/api/endpoints/export/kpi/get_kpi_dau_date/) |  Extraire les utilisateurs actifs uniques par jour sur une période donnée. |
+| `kpi.mau.data_series` | [`/kpi/mau/data_series`]({{site.baseurl}}/api/endpoints/export/kpi/get_kpi_mau_30_days/) | Extraire les utilisateurs actifs uniques sur une fenêtre de 30 jours glissants sur une période donnée. |
+| `kpi.new_users.data_series` | [`/kpi/new_users/data_series`]({{site.baseurl}}/api/endpoints/export/kpi/get_kpi_daily_new_users_date/) | Extraire les nouveaux utilisateurs par jour sur une période donnée. |
+| `kpi.uninstalls.data_series` | [`/kpi/uninstalls/data_series`]({{site.baseurl}}/api/endpoints/export/kpi/get_kpi_uninstalls_date/) | Extraire les désinstallations d’applications par jour sur une période donnée. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Modèles %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `templates.email.create` | [`/templates/email/create`]({{site.baseurl}}/api/endpoints/templates/email_templates/post_create_email_template/) | Créer un nouveau modèle d’e-mail sur le tableau de bord. |
+| `templates.email.info` | [`/templates/email/info`]({{site.baseurl}}/api/endpoints/templates/email_templates/get_see_email_template_information/) | Extraire les données d’un modèle spécifique. |
+| `templates.email.list` | [`/templates/email/list`]({{site.baseurl}}/api/endpoints/templates/email_templates/get_list_email_templates/) | Extraire la liste des modèles d’e-mail. |
+| `templates.email.update` | [`/templates/email/update`]({{site.baseurl}}/api/endpoints/templates/email_templates/post_update_email_template/) | Mettre à jour un modèle d’e-mail stocké sur le tableau de bord. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab SSO %}
+
+| Autorisation | Description |
+|---|---|---|
+| `sso.saml.login` | Configurer l'identifiant initié par le fournisseur d'identité. Pour plus d'informations, reportez-vous à l'[identification initiée par le fournisseur de services (PS)]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Blocs de contenu %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `content_blocks.info` | [`/content_blocks/info`]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information/) | Extraire les données d’un modèle spécifique. |
+| `content_blocks.list` | [`/content_blocks/list`]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks/) | Extraire la liste des blocs de contenu. |
+| `content_blocks.create` | [`/content_blocks/create`]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/post_create_email_content_block/) | Créer un nouveau bloc de contenu sur le tableau de bord. |
+| `content_blocks.update` | [`/content_blocks_update`]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/post_update_content_block/) | Mettre à jour un bloc de contenu existant dans le tableau de bord. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Centre de préférences %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `preference_center.get` | [`/preference_center/v1/{preferenceCenterExternalId}`]({{site.baseurl}}/api/endpoints/preference_center/get_view_details_preference_center) | Obtenir un centre de préférences. |
+| `preference_center.list` | [`/preference_center/v1/list`]({{site.baseurl}}/api/endpoints/preference_center/get_list_preference_center/) | Répertorier les centres de préférences. |
+| `preference_center.update` | [`/preference_center/v1`]({{site.baseurl}}/api/endpoints/preference_center/post_create_preference_center)<br><br>[`/preference_center/v1/{preferenceCenterExternalID}`]({{site.baseurl}}/api/endpoints/preference_center/put_update_preference_center/) | Créez ou mettez à jour un centre de préférences. |
+| `preference_center.user.get` | [`/preference_center/v1/{preferenceCenterExternalId}/url/{userId}`]({{site.baseurl}}/api/endpoints/preference_center/get_create_url_preference_center) | Obtenir le lien d’un centre de préférence pour un utilisateur. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Abonnement %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `subscription.status.set` | [`/subscription/status/set`]({{site.baseurl}}/api/endpoints/subscription_groups/post_update_user_subscription_group_status/) | Définir le statut du groupe d’abonnement. |
+| `subscription.status.get` | [`/subscription/status/get`]({{site.baseurl}}/api/endpoints/subscription_groups/get_list_user_subscription_group_status/) | Obtenir le statut du groupe d’abonnement. |
+| `subscription.groups.get` | [`/subscription/user/status`]({{site.baseurl}}/api/endpoints/subscription_groups/get_list_user_subscription_groups/) | Obtenir le statut des groupes d'abonnement auxquels des utilisateurs spécifiques sont explicitement abonnés et désabonnés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab SMS %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `sms.invalid_phone_numbers` | [`/sms/invalid_phone_numbers`]({{site.baseurl}}/api/endpoints/sms/get_query_invalid_numbers/) | Extraire les numéros de téléphone non valides. |
+| `sms.invalid_phone_numbers.remove` | [`/sms/invalid_phone_numbers/remove`]({{site.baseurl}}/api/endpoints/sms/post_remove_invalid_numbers/) | Supprimer le drapeau de numéro de téléphone non valide d’utilisateurs. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% tab Catalogues %}
+
+| Autorisation | Endpoint | Description |
+|---|---|---|
+| `catalogs.add_items` | [`/catalogs/{catalog_name}/items`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk/) | Ajouter plusieurs produits à un catalogue existant. |
+| `catalogs.update_items` | [`/catalogs/{catalog_name}/items`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk/) | Mettre à jour plusieurs produits dans un catalogue existant. |
+| `catalogs.delete_items` | [`/catalogs/{catalog_name}/items`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk) | Supprimer plusieurs produits d’un catalogue existant. |
+| `catalogs.get_item` | [`/catalogs/{catalog_name}/items/{item_id}`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details/) | Obtenir un produit unique d’un catalogue existant. |
+| `catalogs.update_item` | [`/catalogs/{catalog_name}/items/{item_id}`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item/) | Mettre à jour un produit unique dans un catalogue existant. |
+| `catalogs.create_item` | [`/catalogs/{catalog_name}/items/{item_id}`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item/) | Créer un produit unique dans un catalogue existant. |
+| `catalogs.delete_item` | [`/catalogs/{catalog_name}/items/{item_id}`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item/) | Supprimer un produit unique d’un catalogue existant. |
+| `catalogs.replace_item` | [` /catalogs/{catalog_name}/items/{item_id}`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item/) | Remplacer un produit unique d’un catalogue existant. |
+| `catalogs.create` | [`/catalogs`]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog/) | Créer un catalogue. |
+| `catalogs.get` | [`/catalogs`]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/get_list_catalogs/) | Obtenir une liste de catalogues |
+| `catalogs.delete` | [`/catalogs/{catalog_name}`]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/delete_catalog/) | Supprimer un catalogue. |
+| `catalogs.get_items` | [`/catalogs/{catalog_name}/items`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk/) | Obtenir l’aperçu des produits d’un catalogue existant. |
+| `catalogs.replace_items` | [`/catalogs/{catalog_name}/items`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items/) | Remplacer des articles dans un catalogue existant. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% endtab %}
+{% endtabs %}
+
+## Créer des clés API REST
+
+Pour créer une nouvelle clé d’API REST :
+
+1. Allez dans **Paramètres** > **API et identifiants**.
+
+{% alert note %}
+Si vous utilisez l'[ancienne navigation]({{site.baseurl}}/navigation), vous pouvez créer une clé API à partir de la **console de développement** > **Paramètres API.**
+{% endalert %}
+
+{:start="2"}
+2\. Sélectionnez **Créer une clé API**.
+3\. Donnez un nom à votre nouvelle clé pour l'identifier d'un coup d'œil.
+4\. Spécifier les sous-réseaux et [adresses IP autorisés](#api-ip-allowlisting) pour cette nouvelle clé.
+5\. Sélectionnez les [autorisations](#rest-api-key-permissions) que vous souhaitez associer à votre nouvelle clé.
+
+{% alert important %}
+N'oubliez pas qu'après avoir créé une nouvelle clé API, vous ne pouvez pas modifier l'étendue des autorisations ou les adresses IP autorisées. Cette restriction est en place pour des raisons de sécurité. Si vous devez modifier le périmètre d’une clé, créez une nouvelle clé avec les autorisations mises à jour et implémentez cette clé à la place de l’ancienne. Une fois la mise en œuvre terminée, vous pouvez supprimer l'ancienne clé.
+{% endalert %}
+
+## Gestion des clés API REST
+
+Les clés API REST ne peuvent pas être modifiées après leur création. Toutefois, vous pouvez afficher les détails des clés API REST existantes ou les supprimer à partir de la page **Clés API.**  La liste **Clés API Rest** affiche les informations suivantes en un coup d’œil pour chaque clé :
+
+| Champ        | Description                                                                                                         |
+| ------------ | :------------------------------------------------------------------------------------------------------------------ |
+| Nom de clé API | Nom donné à la clé lors de sa création.                                                                            |
+| Identifiant   | La clé API.                                                                                                        |
+| Créé par   | L'adresse e-mail de l'utilisateur qui a créé la clé. Ce champ indiquera "N/A" pour les clés créées avant juin 2023. |
+| Date de création | Date de création de cette clé.                                                                                      |
+| Vu pour la dernière fois    | Date de la dernière utilisation de cette clé. Ce champ indiquera "N/A" pour les clés qui n'ont jamais été utilisées.                  |
+{: .reset-td-br-1 .reset-td-br-2}
+
+Pour afficher les détails d’une clé spécifique, sélectionnez celle-ci dans la liste. Vous pouvez alors voir toutes les autorisations dont dispose cette clé, les adresses IP inscrites sur la liste blanche (le cas échéant) et si cette clé est inscrite sur la liste blanche des adresses IP de Braze.
+
+![][30]
+
+Notez que lors de la [suppression d'un utilisateur]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/adding_users_to_your_dashboard/), les clés API associées qu'il a créées ne seront pas supprimées. Pour supprimer une clé, cliquez sur <i class="fas fa-gear" alt="Settings"></i> l’option correspondante et sélectionnez-la.
+
+![][29]
+
+## Sécurité clé API REST
+
+Les clés API servent à authentifier les appels de l’API. Quand vous créez une nouvelle clé API REST, vous devez lui accorder l’accès à des endpoints spécifiques. En affectant des autorisations spécifiques à une clé API, vous pouvez limiter de façon précise les appels qu’une clé API peut authentifier.
+
+Étant donné que les clés API REST permettent d’accéder à des endpoints API REST potentiellement sensibles, sécurisez ces clés et partagez-les uniquement avec des partenaires de confiance. Elles ne doivent jamais être exposées publiquement. Par exemple, n’utilisez pas cette clé pour faire des appels AJAX depuis votre site Web ou pour l’exposer autrement de façon publique.
+
+Une bonne pratique de sécurité est d’accorder à un utilisateur uniquement les accès nécessaires pour qu’il puisse accomplir son travail ; ce principe peut également être appliqué aux Clés API en affectant des autorisations pour chaque clé. Ces autorisations vous offrent une meilleure sécurité et un meilleur contrôle sur les différentes parties de votre compte. 
+
+![Autorisations de clé API disponibles lors de la création d’une clé API.][25]
+
+{% alert warning %}
+Étant donné que les clés d'API REST permettent d'accéder à des endpoints d'API REST potentiellement sensibles, assurez-vous qu'elles sont stockées et utilisées en toute sécurité. Par exemple, n’utilisez pas cette clé pour faire des appels AJAX depuis votre site Web ou pour l’exposer autrement de façon publique.
+{% endalert %}
+
+En cas d’exposition accidentelle d’une clé, elle pourra être supprimée à partir de la console de développement. Pour obtenir de l'aide dans cette procédure, ouvrez un \[ticket d'assistance]\[assistance].
+
+### Liste d’adresses IP autorisées
+
+Pour renforcer la sécurité, vous pouvez établir une liste des adresses IP et sous-réseaux qui sont exclusivement autorisés à envoyer des requêtes à l’API REST pour une clé API REST donnée. Vous définissez pour cela une liste d’autorisations, également appelée « Liste blanche ». Pour autoriser des adresses IP ou des sous-réseaux spécifiques, indiquez-les dans la section **Liste blanche d’adresses IP (Whitelist IPs) **lors de la création d’une nouvelle clé API REST : 
+
+![Possibilité de créer une liste blanche d’adresses IP lors de la création d’une clé API][26]
+
+Si vous n’en spécifiez aucune, les requêtes pourront être envoyées depuis n’importe quelle adresse IP.
+
+{% alert tip %}
+Vous créez un Webhook Braze à Braze en utilisant une liste blanche ? Consultez notre liste d'[adresses IP à mettre sur liste blanche.]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/#ip-whitelisting)
+{% endalert %}
+
+## Ressources complémentaires
+
+### Bibliothèque client Ruby
+
+Si vous utilisez Ruby pour implémenter Braze, vous pouvez utiliser notre [Bibliothèque Client Ruby](https://github.com/braze-inc/braze-api-client-ruby) pour réduire le temps d’importation des données. Une bibliothèque cliente est une collection de code spécifique à un langage de programmation (dans ce cas, Ruby) qui facilite l’utilisation d’une API.
+
+La bibliothèque client Ruby prend en charge les [endpoints Utilisateur]({{site.baseurl}}/api/endpoints/user_data).
+
+{% alert note %}
+Cette bibliothèque cliente est actuellement en version bêta. Voulez-vous nous aider à améliorer cette bibliothèque ? Envoyez-nous vos commentaires à [smb-product@braze.com](mailto:smb-product@braze.com).
+{% endalert %}
+
+[1]: https://en.wikipedia.org/wiki/UTF-8
+[7]: {{site.baseurl}}/api/objects_filters/connected_audience/
+[9]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/setting_user_ids/
+[10]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/analytics/setting_user_ids/
+[13]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/setting_user_ids/
+[2]: {{site.baseurl}}/api/identifier_types/
+[5]: {{site.baseurl}}/api/basics/
+[6]: https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#intro
+[25]: {% image_buster /assets/img_archive/api-key-permissions.png %}
+[26]: {% image_buster /assets/img_archive/api-key-ip-whitelisting.png %}
+\[support]: {{site.baseurl}}/braze_support/
+[28]: {% image_buster /assets/img_archive/create-new-key.png %}
+[29]: {% image_buster /assets/img_archive/api-key-options.png %}
+[27]: {% image_buster /assets/img_archive/rest-api-key.png %}
+[30]: {% image_buster /assets/img_archive/view-api-key.png %}
diff --git a/_lang/fr_fr/_api/data_retention.md b/_lang/fr_fr/_api/data_retention.md
new file mode 100644
index 00000000000..b4611c0e762
--- /dev/null
+++ b/_lang/fr_fr/_api/data_retention.md
@@ -0,0 +1,67 @@
+---
+nav_title: Conservation des données
+article_title: Conservation des données
+alias: /data_retention/
+description: "Cet article de référence couvre les informations générales sur la conservation des données de Braze. "
+page_type: reference
+page_order: 2.5
+
+---
+
+<!--
+Warning! Don't make any changes to this document without approval from the legal department.
+-->
+
+# Informations sur la conservation des données de Braze
+
+*Dernière révision le 1er avril 2024*
+
+> Cet article couvre les informations générales sur la conservation des données de Braze.<br><br>Les données enregistrées dans Braze sont conservées et peuvent être utilisées pour la segmentation, la personnalisation et le ciblage pour la durée de vie du compte du client. Ceci signifie que les données telles que les attributs du profil utilisateur, les attributs personnalisés, les événements personnalisés et les achats sont enregistrés indéfiniment pour les utilisateurs actifs pendant la durée du contrat sauf si elles sont supprimées par le client.<br><br>Braze dispose de fonctionnalités, de processus et d’API pour implémenter automatiquement de bonnes pratiques d’hygiène des données à des fins de conformité avec le RGPD et d’autres recommandations. Ceux-ci sont décrits ci-dessous.
+
+## Conservation des données gérée par les clients via le tableau de bord ou l’API de Braze
+
+Braze permet à ses clients de supprimer eux-mêmes des profils utilisateurs entiers et des données d'attribut à partir de leur espace de travail.
+
+Cela signifie que vous pouvez : 
+- Supprimez des profils utilisateurs à l'aide de l'[endpoint API Delete user de]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/) Braze [.]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/) 
+- Supprimer (null) ou modifier des attributs sur des profils utilisateurs en utilisant l'[endpoint de l'API]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) Braze [Track user.]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)
+
+Les événements comportementaux ne peuvent pas être supprimés d’un profil d’utilisateur (événements personnalisés, sessions, campagnes, achats). Pour supprimer ces événements, vous devez supprimer l’ensemble du profil utilisateur.
+
+Pour des raisons de respect de la vie privée, vous pouvez être amené à supprimer toutes les données personnelles relatives à un utilisateur à la demande de ce dernier. Vous trouverez des instructions sur notre page d'[assistance technique relative à la protection des données]({{site.baseurl}}/help/dp-technical-assistance/#the-right-to-erasure).
+
+{% alert note %}
+Un utilisateur peut avoir plusieurs profils, et vous devrez peut-être supprimer plusieurs profils pour supprimer toutes les données relatives à un seul utilisateur. Suivez les instructions de la page d’assistance technique sur la protection des données pour supprimer complètement toutes les données concernant un utilisateur.
+{% endalert %}
+
+## Conservation des données gérée par Braze pour des fonctionnalités spécifiques des Services Braze
+
+#### Base de données Braze : Archivage/suppression automatique des utilisateurs inactifs
+
+Chaque semaine, Braze exécute un processus visant à supprimer les utilisateurs inactifs et dormants des services Braze. En général, il s'agit d'utilisateurs qui ne sont pas joignables (par exemple, qui n'ont pas d'adresse e-mail, pas de numéro de téléphone, pas de jeton push, qui n'utilisent pas vos apps ou ne visitent pas vos sites web), qui n'ont eu aucune activité enregistrée sur leur profil utilisateur et qui n'ont pas reçu de message ou n'ont pas été engagés avec l'utilisation de Braze. Ceci est mis en place pour respecter les principes et recommandations du RGPD. Vous pouvez en savoir plus sur ce processus en consultant notre page consacrée [aux définitions de l'archivage utilisateur]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_archival/).
+
+{% alert note %}
+Les clients ont un contrôle total sur le statut inactif ou dormant des utilisateurs et peuvent empêcher l’archivage des profils utilisateurs en enregistrant un point de donnée à intervalle régulier. Braze Canvas offre la possibilité de le faire automatiquement, ce qui vous permet de désactiver efficacement cette fonctionnalité pour certains ou pour tous vos utilisateurs inactifs ou dormants. 
+{% endalert %}
+
+#### Données sur les interactions de campagne et de Canvas 
+
+Les données d'interaction des messages se réfèrent à la manière dont un utilisateur interagit avec une campagne ou une variante du canvas qu'il a reçu (par exemple, lorsqu'un utilisateur ouvre la campagne A ou qu'un utilisateur reçoit la variante A). Ces données sont utilisées à des fins de reciblage. Pour en savoir plus sur la disponibilité des données d’interaction de messagerie, consultez [À propos de la disponibilité des données d’interaction de messagerie]({{site.baseurl}}/messaging_interaction_data/).
+
+## Conservation des données gérée par Braze
+
+Les politiques de conservation ci-dessous concernent la conformité de Braze avec les réglementations RGPD et relatives à la confidentialité et concernent le stockage des données transitoires au fur et à mesure qu’elles passent dans nos systèmes internes. Ces politiques de conservation n’ont pas d’impact sur les Services de Braze et sont des informations destinées à vos équipes juridiques et de protection de la vie privée.
+
+#### Serveurs Braze : Conservation à court terme à des fins de recouvrement
+
+Les données envoyées par Braze à certains sous-processeurs peuvent se maintenir dans les systèmes internes de Braze pendant un maximum de 90 jours.
+
+#### Conservation des données du Data Lake de Braze
+
+Les données disponibles pour les clients dans le tableau de bord de Braze sont principalement agrégées. Les journaux détaillés sont conservés dans une base de données distincte créée par Braze (le « Data Lake », anciennement appelé « BI Database »). Les données du Data Lake sont utilisées pour l’agrégation de rapports et d’autres fonctionnalités avancées.
+
+Si vous utilisez nos API pour supprimer des profils utilisateurs ou bien supprimer ou modifier des attributs des profils utilisateurs, les données peuvent prendre jusqu’à deux semaines pour être supprimées du Data Lake de Braze. Supprimer des données dans le Data Lake n’aura pas d’effet sur la segmentation ou la personnalisation mais garantit que les données sont supprimées de tous les systèmes de Braze.
+
+#### Serveurs de sauvegarde Braze
+
+Lorsque les données sont supprimées de votre instance de production, elles restent dans les serveurs de sauvegarde de Braze pendant six mois, puis sont supprimées conformément à nos processus internes.
diff --git a/_lang/fr_fr/_api/endpoints.md b/_lang/fr_fr/_api/endpoints.md
new file mode 100644
index 00000000000..c5e56bf269a
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints.md
@@ -0,0 +1,8 @@
+---
+nav_title: Endpoints
+page_order: 1
+config_only: true
+noindex: true
+layout: redirect
+redirect_to: /docs/api/home/
+---
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs.md b/_lang/fr_fr/_api/endpoints/catalogs.md
new file mode 100644
index 00000000000..af304eef4de
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs.md
@@ -0,0 +1,80 @@
+---
+nav_title: Catalogues
+article_title: Endpoints des catalogues
+page_order: 0
+layout: dev_guide
+
+search_tag: Endpoint
+description: "Cette page d’accueil répertorie les endpoints des catalogues de Braze."
+page_type: landing
+
+guide_top_header: "Endpoints des catalogues"
+guide_top_text: "Utilisez les endpoints des catalogues de Braze pour ajouter, modifier et gérer vos catalogues et vos détails de produits du catalogue. Pour les modifications en masse de votre catalogue, utilisez les endpoints de catalogue asynchrones. <br><br> Vous avez besoin d’aide pour créer un catalogue ? Consultez notre article consacré à <a href='/docs/user_guide/personalization_and_dynamic_content/catalog/'>la création et l’utilisation des catalogues</a>."
+
+guide_featured_title: "Points d'extrémité pour la gestion du catalogue"
+guide_featured_list:
+  - name: "DELETE : Supprimer un catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_management/synchronous/delete_catalog/
+    image: /assets/img/braze_icons/edit-05.svg
+  - name: "GET : Lister des catalogues"
+    link: /docs/api/endpoints/catalogs/catalog_management/synchronous/get_list_catalogs/
+    image: /assets/img/braze_icons/list.svg
+  - name: "POST : Créer un catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog/
+    image: /assets/img/braze_icons/check-square-broken.svg
+
+guide_menu_title2: "Asynchronous catalog items endpoints"
+guide_menu_list2:
+  - name: "DELETE : Supprimer plusieurs endpoints des produits du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk/
+    image: /assets/img/braze_icons/edit-05.svg
+  - name: "PATCH : Éditer plusieurs produits du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk/
+    image: /assets/img/braze_icons/user-edit.svg
+  - name: "POST : Créer plusieurs produits du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk/
+    image: /assets/img/braze_icons/check-square-broken.svg
+  - name: "PUT : Mise à jour de plusieurs éléments du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items/
+    image: /assets/img/braze_icons/user-circle.svg
+
+guide_menu_title3: "Synchronous catalog items endpoints"
+guide_menu_list3:  
+  - name: "DELETE : Supprimer un produit du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item/
+    image: /assets/img/braze_icons/edit-05.svg
+  - name: "GET : Lister les détails du produit du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details/
+    image: /assets/img/braze_icons/list.svg
+  - name: "GET : Lister les détails de plusieurs produits du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk/
+    image: /assets/img/braze_icons/list.svg
+  - name: "PATCH : Éditer un produit du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item/
+    image: /assets/img/braze_icons/user-edit.svg
+  - name: "POST : Créer un produit du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item/
+    image: /assets/img/braze_icons/check-square-broken.svg
+  - name: "PUT : Mise à jour de l'article du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item/
+    image: /assets/img/braze_icons/user-circle.svg
+
+guide_menu_title4: "Asynchronous catalog fields endpoints"
+guide_menu_list4:
+  - name: "POST : Créer des champs de catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields/
+    image: /assets/img/braze_icons/check-square-broken.svg
+  - name: "DELETE : Supprimer un champ du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field/
+    image: /assets/img/braze_icons/edit-05.svg
+
+guide_menu_title5: "Asynchronous catalog selections endpoints"
+guide_menu_list5:
+  - name: "POST : Créer des sélections dans le catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections/
+    image: /assets/img/braze_icons/check-square-broken.svg
+  - name: "DELETE : Supprimer la sélection du catalogue"
+    link: /docs/api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection/
+    image: /assets/img/braze_icons/edit-05.svg
+
+---
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields.md
new file mode 100644
index 00000000000..53ee56c4e86
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields.md
@@ -0,0 +1,6 @@
+---
+nav_title: Champs du catalogue
+config_only: true
+noindex: true
+page_order: 3
+---
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields/asynchronous.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields/asynchronous.md
new file mode 100644
index 00000000000..ddd3d46c71e
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields/asynchronous.md
@@ -0,0 +1,6 @@
+---
+nav_title: Asynchrone
+config_only: true
+noindex: true
+page_order: 1
+---
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field.md
new file mode 100644
index 00000000000..3601810797b
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field.md
@@ -0,0 +1,95 @@
+---
+nav_title: "DELETE : Supprimer un champ du catalogue"
+article_title: "DELETE : Supprimer un champ du catalogue"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente les détails du point de terminaison Supprimer le champ de catalogue de Braze."
+
+---
+{% api %}
+# Supprimer un champ du catalogue
+{% apimethod delete %}
+/catalogs/{catalog_name}/fields/{field_name}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer un champ de catalogue.
+{% alert important %}
+Cet endpoint est actuellement en accès anticipé. Contactez votre gestionnaire de satisfaction client si vous souhaitez participer à cet accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.delete_fields`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='asynchronous catalog fields' %}
+
+## Paramètres de chemin
+
+| Paramètre      | Requis | Type de données | Description                |
+| -------------- | -------- | --------- | -------------------------- |
+| `catalog_name` | Requis | Chaîne de caractères    | Nom du catalogue.       |
+| `field_name`   | Requis | Chaîne de caractères    | Nom du champ du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request DELETE 'https://rest.iad-03.braze.com/catalogs/restaurants/fields/ratings' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+```
+
+## Réponse
+
+Deux réponses de code de statut existent pour cet endpoint : `202` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant :
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `404` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "catalog-not-found",
+      "message": "Could not find catalog",
+      "parameters": [
+        "catalog_name"
+      ],
+      "parameter_values": [
+        "restaurants"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes 
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur                           | Résolution des problèmes                                                  |
+| ------------------------------- | ---------------------------------------------------------------- |
+| `catalog-not-found`             | Vérifiez que le nom du catalogue est valide.                            |
+| `field-referenced-by-selection` | Vérifiez que le champ du catalogue est actuellement utilisé par une sélection. |
+| `field-is-inventory`            | Vérifiez que le champ du catalogue est utilisé comme champ d'inventaire.      |
+| `invalid-field-name`            | Vérifiez que le nom du champ du catalogue est valide.                      |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields.md
new file mode 100644
index 00000000000..b0d7b2a3e6d
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields.md
@@ -0,0 +1,122 @@
+---
+nav_title: "POST : Créer des champs de catalogue"
+article_title: "POST : Créer des champs de catalogue"
+search_tag: Endpoint
+page_order: 2
+
+layout: api_page
+page_type: reference
+description: "Cet article présente les détails du point de terminaison Créer des champs de catalogue Braze."
+
+---
+{% api %}
+# Créer des champs de catalogue
+{% apimethod post %}
+/catalogs/{catalog_name}/fields
+{% endapimethod %}
+
+> Utilisez cet endpoint pour créer plusieurs champs dans votre catalogue.
+{% alert important %}
+Cet endpoint est actuellement en accès anticipé. Contactez votre gestionnaire de satisfaction client si vous souhaitez participer à cet accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.create_fields`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='asynchronous catalog fields' %}
+
+## Paramètres de chemin
+
+| Paramètre      | Requis | Type de données | Description          |
+| -------------- | -------- | --------- | -------------------- |
+| `catalog_name` | Requis | Chaîne de caractères    | Nom du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description                                                                                                  |
+| --------- | -------- | --------- | ------------------------------------------------------------------------------------------------------------ |
+| `fields`  | Requis | Tableau     | Un tableau qui contient des objets de champ. Les objets champs doivent contenir le nom et le type des nouveaux champs. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request POST 'https://rest.iad-03.braze.com/catalogs/restaurants/fields' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "fields": [
+    {
+      "name": "Name",
+      "type": "string"
+    },
+    {
+      "name": "Ratings",
+      "type": "number"
+    },
+    {
+      "name": "Loyalty_Program",
+      "type": "boolean"
+    },
+    {
+      "name": "Created_At",
+      "type": "time"
+    }
+  ]
+}'
+```
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `202`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "catalog-not-found",
+      "message": "Could not find catalog",
+      "parameters": [
+        "catalog_name"
+      ],
+      "parameter_values": [
+        "restaurants"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur                                | Résolution des problèmes                                                                                        |
+|--------------------------------------|--------------------------------------------------------------------------------------------------------|
+| `arbitrary-error`                    | Une erreur arbitraire est survenue. Veuillez réessayer ou contacter l'[assistance.]({{site.baseurl}}/support_contact/) |
+| `catalog-not-found`                  | Vérifiez que le nom du catalogue est valide.                                                                  |
+| `company-size-limit-already-reached` | La limite de taille de stockage du catalogue est atteinte.                                                             |
+| `request-includes-too-many-fields`   | Chaque demande peut contenir jusqu'à 50 nouveaux champs.                                                          |
+| `catalog-exceeds-fields-limit`       | Le catalogue ne peut pas comporter plus de 500 champs.                                                              |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items.md
new file mode 100644
index 00000000000..63dc40e73ac
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items.md
@@ -0,0 +1,6 @@
+---
+nav_title: Produits du catalogue
+config_only: true
+noindex: true
+page_order: 2
+---
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous.md
new file mode 100644
index 00000000000..97dcc8cd52d
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous.md
@@ -0,0 +1,6 @@
+---
+nav_title: Asynchrone
+config_only: true
+noindex: true
+page_order: 1
+---
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk.md
new file mode 100644
index 00000000000..66f1da1f727
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk.md
@@ -0,0 +1,108 @@
+---
+nav_title: "DELETE : Supprimer plusieurs produits du catalogue"
+article_title: "DELETE : Supprimer plusieurs produits du catalogue"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Supprimer plusieurs produits du catalogue."
+
+---
+{% api %}
+# supprimer plusieurs produits du catalogue
+{% apimethod delete %}
+/catalogs/{catalog_name}/items
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer plusieurs produits de votre catalogue. 
+
+Chaque requête peut prendre en charge jusqu’à 50 objets. Cet endpoint est asynchrone.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#647c82e8-8b38-4df2-bde2-b1d8e19fd332 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.delete_items`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='asynchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `items` | Requis | Tableau | Un tableau qui contient certains objets Produit. Les objets Produit doivent contenir un `id` faisant référence aux produits que Braze doit supprimer. Jusqu’à 50 objets sont autorisés par requête. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request DELETE 'https://rest.iad-03.braze.com/catalogs/restaurants/items' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "items": [
+    {"id": "restaurant1"},
+    {"id": "restaurant2"},
+    {"id": "restaurant3"}
+  ]
+}'
+```
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `202`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "items-missing-ids",
+      "message": "There are 1 item(s) that do not have ids",
+      "parameters": [],
+      "parameter_values": []
+    }
+  ],
+  "message": "Invalid Request",
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+| `ids-too-large` | Les ID de produit ne peuvent pas contenir plus de 250 caractères. |
+| `ids-not-unique` | Vérifiez que les ID de produit dans la requête sont uniques. |
+| `ids-not-strings` | Les ID de produit doivent être de type chaîne de caractères. |
+| `items-missing-ids` | Il y a des produits qui n’ont pas d’ID de produit. Vérifiez que chaque produit possède un ID de produit. |
+| `invalid-ids` | Ces ID de produit peuvent uniquement inclure des lettres, des chiffres, des traits d’union et des traits de soulignement. |
+| `request-includes-too-many-items` | Votre requête contient trop de produits. La limite de produit par requête est de 50. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk.md
new file mode 100644
index 00000000000..3136f0464bb
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk.md
@@ -0,0 +1,148 @@
+---
+nav_title: "PATCH : Éditer plusieurs produits du catalogue"
+article_title: "PATCH : Éditer plusieurs produits du catalogue"
+alias: /catalogs_items_patch/
+search_tag: Endpoint
+page_order: 2
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Éditer plusieurs produits du catalogue."
+
+---
+{% api %}
+# modifier plusieurs produits du catalogue
+{% apimethod patch %}
+/catalogs/{catalog_name}/items
+{% endapimethod %}
+
+> Utilisez cet endpoint pour modifier plusieurs éléments existants dans votre catalogue.
+
+Chaque requête peut prendre en charge jusqu’à 50 objets. Cet endpoint est asynchrone.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#03f3548e-4139-4f60-812d-7e1a695a738a {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.update_items`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='asynchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `items` | Requis | Tableau | Un tableau qui contient certains objets Produit. Les objets Produits devraient contenir des champs qui existent dans le catalogue. Jusqu’à 50 objets sont autorisés par requête. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request PATCH 'https://rest.iad-03.braze.com/catalogs/restaurants/items' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "items": [
+    {
+      "id": "restaurant1",
+      "Name": "Restaurant",
+      "Loyalty_Program": false,
+      "Location": {
+        "Latitude": 33.6112,
+        "Longitude": -117.8711
+      },
+      "Top_Dishes": {
+        "$add": [
+          "Biscuits",
+          "Coleslaw"
+        ],
+        "$remove": [
+          "French Fries"
+        ]
+      },
+      "Open_Time": "2021-09-03T09:03:19.967+00:00"
+    },
+    {
+      "id": "restaurant3",
+      "City": "San Francisco",
+      "Rating": 2,
+      "Top_Dishes": [
+        "Buffalo Wings",
+        "Philly Cheesesteak"
+      ]
+    }
+  ]
+}'
+```
+
+{% alert note %}
+Les opérateurs `$add` et `$remove` ne s'appliquent qu'aux champs de type tableau et ne sont pris en charge que par les endpoints PATCH.
+{% endalert %}
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `202`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "invalid-fields",
+      "message": "Some of the fields given do not exist in the catalog",
+      "parameters": [
+        "id"
+      ],
+      "parameter_values": [
+        "restaurant1"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+| `ids-too-large` | Les ID de produit ne peuvent pas contenir plus de 250 caractères. |
+| `ids-not-strings` | Les ID de produit doivent être de type chaîne de caractères. |
+| `ids-not-unique` | Les ID de produit doivent être uniques au sein de la requête. |
+| `invalid-ids` | Ces ID de produit peuvent uniquement inclure des lettres, des chiffres, des traits d’union et des traits de soulignement. |
+| `invalid-fields` | Confirmez que tous les champs que vous envoyez dans la requête API existent déjà dans le catalogue. Cela n'a rien à voir avec le champ ID mentionné dans l'erreur. |
+| `invalid-keys-in-value-object` | Les clés d’objet de produit ne peuvent pas inclure `.` ou `$`. |
+| `items-missing-ids` | Il y a des produits qui n’ont pas d’ID de produit. Vérifiez que chaque produit possède un ID de produit. |
+| `item-array-invalid` | `items` doit être un tableau d’objets. |
+| `items-too-large` | Les valeurs de produits ne peuvent pas dépasser 5 000 caractères. |
+| `request-includes-too-many-items` | Votre requête contient trop de produits. La limite de produit par requête est de 50. |
+| `too-deep-nesting-in-value-object` | Les objets de produit ne peuvent pas avoir plus de 50 niveaux d’imbrication. |
+| `unable-to-coerce-value` | Les types de produits ne peuvent pas être convertis. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk.md
new file mode 100644
index 00000000000..ecf55550e5f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk.md
@@ -0,0 +1,166 @@
+---
+nav_title: "POST : Créer plusieurs produits du catalogue"
+article_title: "POST : Créer plusieurs produits du catalogue"
+search_tag: Endpoint
+page_order: 3
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Créer plusieurs produits du catalogue."
+
+---
+{% api %}
+# Créer plusieurs produits du catalogue
+{% apimethod post %}
+/catalogs/{catalog_name}/items
+{% endapimethod %}
+
+> Utilisez cet endpoint pour créer plusieurs produits dans votre catalogue. 
+
+Chaque requête peut prendre en charge jusqu’à 50 objets. Cet endpoint est asynchrone.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#cea18bb3-b83a-4160-81fe-8cd42aa6e7cc {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.add_items`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='asynchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `items` | Requis | Tableau | Un tableau qui contient certains objets Produit. Les objets Produits devraient contenir tous les champs qui existent dans le catalogue. Jusqu’à 50 objets sont autorisés par requête. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request POST 'https://rest.iad-03.braze.com/catalogs/restaurants/items' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "items": [
+    {
+      "id": "restaurant1",
+      "Name": "Restaurant1",
+      "City": "New York",
+      "Cuisine": "American",
+      "Rating": 5,
+      "Loyalty_Program": true,
+      "Location": {
+        "Latitude": 33.6112,
+        "Longitude": -117.8711
+      },
+      "Top_Dishes": [
+        "Hamburger",
+        "Deluxe Cheeseburger"
+      ],
+      "Created_At": "2022-11-01T09:03:19.967+00:00"
+    },
+    {
+      "id": "restaurant2",
+      "Name": "Restaurant2",
+      "City": "New York",
+      "Cuisine": "American",
+      "Rating": 10,
+      "Loyalty_Program": true,
+      "Location": {
+        "Latitude": 40.7413,
+        "Longitude": -73.9764
+      },
+      "Top_Dishes": [
+        "Hot Dog",
+        "French Fries"
+      ],
+      "Created_At": "2022-11-02T09:03:19.967+00:00"
+    },
+    {
+      "id": "restaurant3",
+      "Name": "Restaurant3",
+      "City": "New York",
+      "Cuisine": "American",
+      "Rating": 3,
+      "Loyalty_Program": false,
+      "Location": {
+        "Latitude": 40.7489,
+        "Longitude": -73.9972
+      },
+      "Top_Dishes": [
+        "Buffalo Wings",
+        "Philly Cheesesteak"
+      ],
+      "Created_At": "2022-11-03T09:03:19.967+00:00"
+    }
+  ]
+}'
+```
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `202`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "invalid-fields",
+      "message": "Some of the fields given do not exist in the catalog",
+      "parameters": [
+        "id"
+      ],
+      "parameter_values": [
+        "restaurant1"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+| `ids-not-strings` | Les ID de produit doivent être de type chaîne de caractères. |
+| `ids-not-unique` | Les ID de produit doivent être uniques au sein de la requête. |
+| `ids-too-large` | Les ID de produit ne peuvent pas contenir plus de 250 caractères. |
+| `invalid-ids` | Ces ID de produit peuvent uniquement inclure des lettres, des chiffres, des traits d’union et des traits de soulignement. |
+| `invalid-fields` | Confirmez que tous les champs que vous envoyez dans la requête API existent déjà dans le catalogue. Cela n'a rien à voir avec le champ ID mentionné dans l'erreur. |
+| `invalid-keys-in-value-object` | Les clés d’objet de produit ne peuvent pas inclure `.` ou `$`. |
+| `item-array-invalid` | `items` doit être un tableau d’objets. |
+| `items-missing-ids` | Il y a des produits qui n’ont pas d’ID de produit. Vérifiez que chaque produit possède un ID de produit. |
+| `items-too-large` | Les valeurs de produits ne peuvent pas dépasser 5 000 caractères. |
+| `request-includes-too-many-items` | Votre requête contient trop de produits. La limite de produit par requête est de 50. |
+| `too-deep-nesting-in-value-object` | Les objets de produit ne peuvent pas avoir plus de 50 niveaux d’imbrication. |
+| `unable-to-coerce-value` | Les types de produits ne peuvent pas être convertis. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items.md
new file mode 100644
index 00000000000..493677ec4b0
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items.md
@@ -0,0 +1,138 @@
+---
+nav_title: "PUT : Mise à jour de plusieurs éléments du catalogue"
+article_title: "PUT : Mise à jour de plusieurs éléments du catalogue"
+search_tag: Endpoint
+page_order: 4
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour plusieurs produits du catalogue."
+
+---
+{% api %}
+# Mettre à jour les produits du catalogue
+{% apimethod put %}
+/catalogs/{catalog_name}/items
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour plusieurs produits de votre catalogue. 
+
+Si un élément du catalogue n'existe pas, cet endpoint créera l'élément dans votre catalogue. Chaque requête peut prendre en charge jusqu’à 50 produits du catalogue. Cet endpoint est asynchrone.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#ab30a4fc-60bc-4460-885c-1b92af8bc061 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.replace_items`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='asynchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `items` | Requis | Tableau | Un tableau qui contient certains objets Produit. Chaque produit doit avoir un ID. Les objets Produits devraient contenir des champs qui existent dans le catalogue. Jusqu’à 50 objets sont autorisés par requête. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request PUT 'https://rest.iad-03.braze.com/catalogs/restaurants/items' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "items": [
+    {
+      "id": "restaurant1",
+      "Name": "Restaurant",
+      "Loyalty_Program": false,
+      "Location": {
+        "Latitude": 33.6112,
+        "Longitude": -117.8711
+      },
+      "Top_Dishes": [
+        "Hamburger",
+        "Deluxe Cheeseburger"
+      ],
+      "Open_Time": "2021-09-03T09:03:19.967+00:00"
+    },
+    {
+      "id": "restaurant3",
+      "City": "San Francisco",
+      "Rating": 2,
+      "Top_Dishes": [
+        "Hot Dog",
+        "French Fries"
+      ]
+    }
+  ]
+}'
+```
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `202`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "invalid-fields",
+      "message": "Some of the fields given do not exist in the catalog",
+      "parameters": [
+        "id"
+      ],
+      "parameter_values": [
+        "restaurant1"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. | 
+| `ids-not-string` | Confirmez que chaque ID de produit est une chaîne de caractères. |
+| `ids-not-unique` | Vérifiez que chaque ID de produit est unique. |
+| `ids-too-large` | La limite de caractères pour chaque ID de produit est de 250 caractères. |
+| `item-array-invalid` | `items` doit être un tableau d’objets. |
+| `items-missing-ids` | Confirmez que chaque produit a un ID. |
+| `items-too-large` | Les valeurs de produits ne peuvent pas dépasser 5 000 caractères. |
+| `invalid-ids` | Les caractères pris en charge pour les ID de produits sont les lettres, les nombres, les tirets et les traits de soulignement. |
+| `invalid-fields` | Confirmez que tous les champs que vous envoyez dans la requête API existent déjà dans le catalogue. Cela n'a rien à voir avec le champ ID mentionné dans l'erreur. |
+| `invalid-keys-in-value-object` | Les clés d’objet de produit ne peuvent pas inclure `.` ou `$`. |
+| `too-deep-nesting-in-value-object` | Les objets de produit ne peuvent pas avoir plus de 50 niveaux d’imbrication. |
+| `request-includes-too-many-items` | Votre requête contient trop de produits. La limite de produit par requête est de 50. |
+| `unable-to-coerce-value` | Les types de produits ne peuvent pas être convertis. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous.md
new file mode 100644
index 00000000000..e3843455f74
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous.md
@@ -0,0 +1,6 @@
+---
+nav_title: Synchrone
+config_only: true
+noindex: true
+page_order: 2
+---
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item.md
new file mode 100644
index 00000000000..c71b43ec9db
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item.md
@@ -0,0 +1,97 @@
+---
+nav_title: "DELETE : Supprimer un produit du catalogue"
+article_title: "DELETE : Supprimer un produit du catalogue"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Supprimer un produit du catalogue."
+
+---
+{% api %}
+# Supprimer un produit du catalogue
+{% apimethod delete %}
+/catalogs/{catalog_name}/items/{item_id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer un produit de votre catalogue. 
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#0dcce797-1346-472f-9384-082f14541689 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.delete_item`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='synchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+| `item_id` | Requis | Chaîne de caractères | L’ID du produit du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+Cet endpoint n’a pas de corps de demande.
+
+## Exemple de demande
+
+```
+curl --location --request DELETE 'https://rest.iad-03.braze.com/catalogs/restaurants/items/restaurant1' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `202`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "item-not-found",
+      "message": "Could not find item",
+      "parameters": [
+        "item_id"
+      ],
+      "parameter_values": [
+        "restaurant34"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `arbitrary-error` | Une erreur arbitraire est survenue. Veuillez réessayer ou contacter l'[assistance.]({{site.baseurl}}/support_contact/) |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+| `item-not-found` | Vérifiez que le produit à supprimer existe dans votre catalogue. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details.md
new file mode 100644
index 00000000000..a1b20eca7bb
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details.md
@@ -0,0 +1,107 @@
+---
+nav_title: "GET : Lister les détails du produit du catalogue"
+article_title: "GET : Lister les détails du produit du catalogue"
+search_tag: Endpoint
+page_order: 2
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Lister les détails du produit du catalogue."
+
+---
+{% api %}
+# Lister les détails du produit du catalogue
+{% apimethod get %}
+/catalogs/{catalog_name}/items/{item_id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour renvoyer un produit de catalogue et son contenu.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#52c6631c-7366-48e5-9e0e-16de7b6285cc {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.get_item`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='synchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+| `item_id` | Requis | Chaîne de caractères | L’ID du produit du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+Cet endpoint n’a pas de corps de demande.
+
+## Exemple de demande
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/catalogs/restaurants/items/restaurant1' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+Deux réponses de code de statut existent pour cet endpoint : `200` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `200` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "items": [
+    {
+      "id": "restaurant3",
+      "Name": "Restaurant1",
+      "City": "New York",
+      "Cuisine": "American",
+      "Rating": 5,
+      "Loyalty_Program": true,
+      "Open_Time": "2022-11-01T09:03:19.967Z"
+    }
+  ],
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `404` pourrait retourner la réponse suivante. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "item-not-found",
+      "message": "Could not find item",
+      "parameters": [
+        "item_id"
+      ],
+      "parameter_values": [
+        "restaurant34"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées, le cas échéant.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+| `item-not-found` | Vérifiez que ce produit est dans le catalogue. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk.md
new file mode 100644
index 00000000000..31f4f6862a3
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk.md
@@ -0,0 +1,151 @@
+---
+nav_title: "GET : Lister les détails de plusieurs produits du catalogue"
+article_title: "GET : Lister les détails de plusieurs produits du catalogue"
+search_tag: Endpoint
+page_order: 3
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Lister les détails de plusieurs produits du catalogue."
+
+---
+{% api %}
+# Lister les détails de plusieurs produits du catalogue
+{% apimethod get %}
+/catalogs/{catalog_name}/items
+{% endapimethod %}
+
+> Utilisez cet endpoint pour retourner plusieurs produits du catalogue et leur contenu.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#63a19dd5-10e0-4649-bdf0-097216748bbb {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.get_items`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='synchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de recherche
+
+Notez que chaque appel de cet endpoint retournera 50 produits. Pour un catalogue comportant plus de 50 produits, utilisez l’en-tête `Link` pour extraire les données de la page suivante, comme indiqué dans l’exemple de réponse ci-dessous.
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `cursor` | Facultatif | Chaîne de caractères | Détermine la pagination des produits du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+Cet endpoint n’a pas de corps de demande.
+
+## Exemple de requêtes
+
+### Sans curseur
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/catalogs/restaurants/items' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+### Avec curseur
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/catalogs/restaurants/items?cursor=c2tpcDow' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `200`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `200` pourrait retourner l’en-tête et le corps de réponse suivant.
+
+{% alert note %}
+L’en-tête `Link` n’existera pas si le catalogue possède 50 produits ou moins. Pour les appels sans curseur, `prev` ne s’affichera pas. Lors de la consultation de la dernière page de produits, `next` ne s’affichera pas.
+{% endalert %}
+
+```
+Link: </catalogs/all_restaurants/items?cursor=c2tpcDow>; rel="prev",</catalogs/all_restaurants/items?cursor=c2tpcDoxMDA=>; rel="next"
+```
+
+```json
+{
+  "items": [
+    {
+      "id": "restaurant1",
+      "Name": "Restaurant1",
+      "City": "New York",
+      "Cuisine": "American",
+      "Rating": 5,
+      "Loyalty_Program": true,
+      "Open_Time": "2022-11-02T09:03:19.967Z"
+    },
+    {
+      "id": "restaurant2",
+      "Name": "Restaurant2",
+      "City": "New York",
+      "Cuisine": "American",
+      "Rating": 10,
+      "Loyalty_Program": true,
+      "Open_Time": "2022-11-02T09:03:19.967Z"
+    },
+    {
+      "id": "restaurant3",
+      "Name": "Restaurant3",
+      "City": "New York",
+      "Cuisine": "American",
+      "Rating": 5,
+      "Loyalty_Program": false,
+      "Open_Time": "2022-11-02T09:03:19.967Z"
+    }
+  ],
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "invalid-cursor",
+      "message": "'cursor' is not valid",
+      "parameters": [
+        "cursor"
+      ],
+      "parameter_values": [
+        "bad-cursor"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+| `invalid-cursor` | Vérifiez que votre `cursor` est valide. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item.md
new file mode 100644
index 00000000000..eac77a8acd7
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item.md
@@ -0,0 +1,137 @@
+---
+nav_title: "PATCH : Éditer un produit du catalogue"
+article_title: "PATCH : Éditer un produit du catalogue"
+search_tag: Endpoint
+page_order: 4
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Éditer un produit du catalogue."
+
+---
+{% api %}
+# Éditer un produit du catalogue
+{% apimethod patch %}
+/catalogs/{catalog_name}/items/{item_id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour modifier un élément existant dans votre catalogue.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#e35976ae-ff77-42b7-b691-a883c980d8c0 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.update_item`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='synchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+| `item_id` | Requis | Chaîne de caractères | L’ID du produit du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `items` | Requis | Tableau | Un tableau qui contient certains objets Produit. Les objets Produits devraient contenir les champs qui existent dans le catalogue à l’exception du champ `id`. Un seul objet de produit est autorisé par requête. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request PATCH 'https://rest.iad-03.braze.com/catalogs/restaurants/items/restaurant1' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "items": [
+    {
+      "Name": "Restaurant",
+      "Loyalty_Program": false,
+      "Location": {
+        "Latitude": 33.6112,
+        "Longitude": -117.8711
+      },
+      "Top_Dishes": {
+        "$add": [
+          "Biscuits",
+          "Coleslaw"
+        ],
+        "$remove": [
+          "French Fries"
+        ]
+      },
+      "Open_Time": "2021-09-03T09:03:19.967+00:00"
+    }
+  ]
+}'
+```
+
+{% alert note %}
+Les opérateurs `$add` et `$remove` ne s'appliquent qu'aux champs de type tableau et ne sont pris en charge que par les endpoints PATCH.
+{% endalert %}
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `200`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `200` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "invalid-fields",
+      "message": "Some of the fields given do not exist in the catalog",
+      "parameters": [
+        "id"
+      ],
+      "parameter_values": [
+        "restaurant1"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `arbitrary-error` | Une erreur arbitraire est survenue. Veuillez réessayer ou contacter l'[assistance.]({{site.baseurl}}/support_contact/) |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+| `filtered-set-field-too-long` | La valeur du champ est utilisée dans un ensemble filtré qui dépasse la limite de caractères pour un produit. |
+| `id-in-body` | Un ID de produit existe déjà dans le catalogue. |
+| `ids-too-large` | La limite de caractères pour chaque ID de produit est de 250 caractères. |
+| `invalid-ids` | Les caractères pris en charge pour les ID de produits sont les lettres, les nombres, les tirets et les traits de soulignement. |
+| `invalid-fields` | Confirmez que les champs de la requête existent dans le catalogue. |
+| `invalid-keys-in-value-object` | Les clés d’objet de produit ne peuvent pas inclure `.` ou `$`. |
+| `item-not-found` | Vérifiez que ce produit est dans le catalogue. |
+| `item-array-invalid` | `items` doit être un tableau d’objets. |
+| `items-too-large` | La limite de caractères pour chaque produit est de 5 000 caractères. |
+| `request-includes-too-many-items` | Vous ne pouvez modifier qu’un produit de catalogue par requête. |
+| `too-deep-nesting-in-value-object` | Les objets de produit ne peuvent pas avoir plus de 50 niveaux d’imbrication. |
+| `unable-to-coerce-value` | Les types de produits ne peuvent pas être convertis. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item.md
new file mode 100644
index 00000000000..7efaf163b41
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item.md
@@ -0,0 +1,131 @@
+---
+nav_title: "POST : Créer un produit du catalogue"
+article_title: "POST : Créer un produit du catalogue"
+search_tag: Endpoint
+page_order: 5
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Créer un produit du catalogue."
+
+---
+{% api %}
+# Créer un produit du catalogue
+{% apimethod post %}
+/catalogs/{catalog_name}/items/{item_id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour créer un produit dans votre catalogue.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#820c305b-ea6a-4b71-811a-55003a212a40 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.create_item`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='synchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+| `item_id` | Requis | Chaîne de caractères | L’ID du produit du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `items` | Requis | Tableau | Un tableau qui contient certains objets Produit. Les objets de produits devraient contenir tous les champs qui existent dans le catalogue à l’exception du champ `id`. Un seul objet de produit est autorisé par requête. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request POST 'https://rest.iad-03.braze.com/catalogs/restaurants/items/restaurant1' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "items": [
+    {
+      "Name": "Restaurant1",
+      "City": "New York",
+      "Cuisine": "American",
+      "Rating": 5,
+      "Loyalty_Program": true,
+      "Location": {
+        "Latitude": 33.6112,
+        "Longitude": -117.8711
+      },
+      "Top_Dishes": [
+        "Hamburger",
+        "Deluxe Cheeseburger"
+      ],
+      "Created_At": "2022-11-01T09:03:19.967+00:00"
+    }
+  ]
+}'
+```
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `201`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `201` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "invalid-fields",
+      "message": "Some of the fields given do not exist in the catalog",
+      "parameters": [
+        "id"
+      ],
+      "parameter_values": [
+        "restaurant1"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `arbitrary-error` | Une erreur arbitraire est survenue. Veuillez réessayer ou contacter l'[assistance.]({{site.baseurl}}/support_contact/) |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+| `filtered-set-field-too-long` | La valeur du champ est utilisée dans un ensemble filtré qui dépasse la limite de caractères pour un produit. |
+| `id-in-body` | Enlevez n’importe quel ID de produit dans le corps de la requête. |
+| `ids-too-large` | La limite de caractères pour chaque ID de produit est de 250 caractères. |
+| `invalid-ids` | Les caractères pris en charge pour les ID de produits sont les lettres, les nombres, les tirets et les traits de soulignement. |
+| `invalid-fields` | Confirmez que tous les champs que vous envoyez dans la requête API existent déjà dans le catalogue. Cela n'a rien à voir avec le champ ID mentionné dans l'erreur. |
+| `invalid-keys-in-value-object` | Les clés d’objet de produit ne peuvent pas inclure `.` ou `$`. |
+| `item-already-exists` | Ce produit existe déjà dans le catalogue. |
+| `item-array-invalid` | `items` doit être un tableau d’objets. | 
+| `items-too-large` | La limite de caractères pour chaque produit est de 5 000 caractères. |
+| `request-includes-too-many-items` | Vous ne pouvez créer qu’un produit de catalogue par requête. |
+| `too-deep-nesting-in-value-object` | Les objets de produit ne peuvent pas avoir plus de 50 niveaux d’imbrication. |
+| `unable-to-coerce-value` | Les types de produits ne peuvent pas être convertis. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item.md
new file mode 100644
index 00000000000..6dcbff495ec
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item.md
@@ -0,0 +1,130 @@
+---
+nav_title: "PUT : Mise à jour de l'article du catalogue"
+article_title: "PUT : Mise à jour de l'article du catalogue"
+search_tag: Endpoint
+page_order: 6
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour un produit du catalogue."
+
+---
+{% api %}
+# Mettre à jour un produit du catalogue
+{% apimethod put %}
+/catalogs/{catalog_name}/items/{item_id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour un produit dans votre catalogue. 
+
+Si l’`item_id` n'est pas trouvé, cet endpoint créera le produit dans votre catalogue. Cet endpoint est synchrone.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#b2871ed7-734e-4a37-b8f1-e11584e569f5 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.replace_item`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='synchronous catalog item' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+| `item_id` | Requis | Chaîne de caractères | L’ID du produit du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `items` | Requis | Tableau | Un tableau qui contient certains objets Produit. Les objets Produits devraient contenir les champs qui existent dans le catalogue à l’exception du champ `id`. Un seul objet de produit est autorisé par requête. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request PUT 'https://rest.iad-03.braze.com/catalogs/restaurants/items/restaurant1' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "items": [
+    {
+      "Name": "Restaurant",
+      "Loyalty_Program": false,
+      "Location": {
+        "Latitude": 33.6112,
+        "Longitude": -117.8711
+      },
+      "Top_Dishes": [
+        "Hamburger",
+        "Deluxe Cheeseburger"
+      ],
+      "Open_Time": "2021-09-03T09:03:19.967+00:00"
+    }
+  ]
+}'
+```
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `200`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `200` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "invalid-fields",
+      "message": "Some of the fields given do not exist in the catalog",
+      "parameters": [
+        "id"
+      ],
+      "parameter_values": [
+        "restaurant1"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `arbitrary-error` | Une erreur arbitraire est survenue. Veuillez réessayer ou contacter l'[assistance.]({{site.baseurl}}/support_contact/) |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+| `filtered-set-field-too-long` | La valeur du champ est utilisée dans un ensemble filtré qui dépasse la limite de caractères pour un produit. |
+| `id-in-body` | Enlevez n’importe quel ID de produit dans le corps de la requête. |
+| `ids-too-large` | La limite de caractères pour chaque ID de produit est de 250 caractères. |
+| `invalid-ids` | Les caractères pris en charge pour les ID de produits sont les lettres, les nombres, les tirets et les traits de soulignement. |
+| `invalid-fields` | Confirmez que tous les champs que vous envoyez dans la requête API existent déjà dans le catalogue. Cela n'a rien à voir avec le champ ID mentionné dans l'erreur. |
+| `invalid-keys-in-value-object` | Les clés d’objet de produit ne peuvent pas inclure `.` ou `$`. |
+| `item-already-exists` | Ce produit existe déjà dans le catalogue. |
+| `item-array-invalid` | `items` doit être un tableau d’objets. | 
+| `items-too-large` | La limite de caractères pour chaque produit est de 5 000 caractères. |
+| `request-includes-too-many-items` | Vous ne pouvez créer qu’un produit de catalogue par requête. |
+| `too-deep-nesting-in-value-object` | Les objets de produit ne peuvent pas avoir plus de 50 niveaux d’imbrication. |
+| `unable-to-coerce-value` | Les types de produits ne peuvent pas être convertis. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_management.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management.md
new file mode 100644
index 00000000000..5f2476f76d9
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management.md
@@ -0,0 +1,6 @@
+---
+nav_title: Gestion du catalogue
+config_only: true
+noindex: true
+page_order: 1
+---
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous.md
new file mode 100644
index 00000000000..fbd11244256
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous.md
@@ -0,0 +1,6 @@
+---
+nav_title: Synchrone
+config_only: true
+noindex: true
+page_order: 1
+---
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous/delete_catalog.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous/delete_catalog.md
new file mode 100644
index 00000000000..4375a570354
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous/delete_catalog.md
@@ -0,0 +1,90 @@
+---
+nav_title: "DELETE : Supprimer un catalogue"
+article_title: "DELETE : Supprimer un catalogue"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Supprimer un catalogue."
+
+---
+{% api %}
+# Supprimer un catalogue
+{% apimethod delete %}
+/catalogues/{nom_du_catalogue}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer un catalogue.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#c0915a86-797a-4486-8217-24cd1c689d0f {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.delete`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='synchronous catalog' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalog_name` | Requis | Chaîne de caractères | Nom du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request DELETE 'https://rest.iad-03.braze.com/catalogs/restaurants' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+```
+
+## Réponse
+
+Deux réponses de code de statut existent pour cet endpoint : `200` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `200` pourrait renvoyer le corps de réponse suivant :
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `404` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "catalog-not-found",
+      "message": "Could not find catalog",
+      "parameters": [
+        "catalog_name"
+      ],
+      "parameter_values": [
+        "restaurants"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes 
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `catalog-not-found` | Vérifiez que le nom du catalogue est valide. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous/get_list_catalogs.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous/get_list_catalogs.md
new file mode 100644
index 00000000000..577d14057a6
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous/get_list_catalogs.md
@@ -0,0 +1,120 @@
+---
+nav_title: "GET : Lister des catalogues"
+article_title: "GET : Lister des catalogues"
+search_tag: Endpoint
+page_order: 2
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Lister des catalogues."
+
+---
+{% api %}
+# Lister des catalogues
+{% apimethod get %}
+/catalogs
+{% endapimethod %}
+
+> Utilisez cet endpoint pour obtenir la liste des catalogues d'un espace de travail.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#7d65fb86-ccf7-423f-9eb2-f68ab36df824 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.get`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='synchronous catalog' %}
+
+## Paramètres de chemin et de requête
+
+Cet endpoint n’a pas de paramètres de chemin ni de requête.
+
+## Exemple de demande
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/catalogs' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+### Exemple de réponse réussie
+
+Le code de statut `200` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "catalogs": [
+    {
+      "description": "My Restaurants",
+      "fields": [
+        {
+          "name": "id",
+          "type": "string"
+        },
+        {
+          "name": "Name",
+          "type": "string"
+        },
+        {
+          "name": "City",
+          "type": "string"
+        },
+        {
+          "name": "Cuisine",
+          "type": "string"
+        },
+        {
+          "name": "Rating",
+          "type": "number"
+        },
+        {
+          "name": "Loyalty_Program",
+          "type": "boolean"
+        },
+        {
+          "name": "Created_At",
+          "type": "time"
+        }
+      ],
+      "name": "restaurants",
+      "num_items": 10,
+      "updated_at": "2022-11-02T20:04:06.879+00:00"
+    },
+    {
+      "description": "My Catalog",
+      "fields": [
+        {
+          "name": "id",
+          "type": "string"
+        },
+        {
+          "name": "string_field",
+          "type": "string"
+        },
+        {
+          "name": "number_field",
+          "type": "number"
+        },
+        {
+          "name": "boolean_field",
+          "type": "boolean"
+        },
+        {
+          "name": "time_field",
+          "type": "time"
+        },
+      ],
+      "name": "my_catalog",
+      "num_items": 3,
+      "updated_at": "2022-11-02T09:03:19.967+00:00"
+    },
+  ],
+  "message": "success"
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog.md
new file mode 100644
index 00000000000..a7fa7c0cb17
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog.md
@@ -0,0 +1,202 @@
+---
+nav_title: "POST : Créer un catalogue"
+article_title: "POST : Créer un catalogue"
+search_tag: Endpoint
+page_order: 3
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Créer un catalogue."
+
+---
+{% api %}
+# Créer un catalogue
+{% apimethod post %}
+/catalogs
+{% endapimethod %}
+
+> Utilisez cet endpoint pour créer un catalogue.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#af9f3e2d-b7e7-49e7-aa64-f4652892be6e {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.create`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='synchronous catalog' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `catalogs` | Requis | Tableau | Un tableau qui contient des objets Catalogue. Un seul objet Catalogue est autorisé pour cette requête. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+### Paramètres de l’objet Catalogue
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `name` | Requis | Chaîne de caractères | Le nom du catalogue que vous voulez créer. |
+| `description` | Requis | Chaîne de caractères | La description du catalogue que vous voulez créer. |
+| `fields` | Requis | Tableau | Un tableau d’objets dans lequel l’objet contient les clés `name` et `type`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-03.braze.com/catalogs' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "catalogs": [
+    {
+      "name": "restaurants",
+      "description": "My Restaurants",
+      "fields": [
+        {
+          "name": "id",
+          "type": "string"
+        },
+        {
+          "name": "Name",
+          "type": "string"
+        },
+        {
+          "name": "City",
+          "type": "string"
+        },
+        {
+          "name": "Cuisine",
+          "type": "string"
+        },
+        {
+          "name": "Rating",
+          "type": "number"
+        },
+        {
+          "name": "Loyalty_Program",
+          "type": "boolean"
+        },
+        {
+          "name": "Location",
+          "type": "object"
+        },
+        {
+          "name": "Top_Dishes",
+          "type": "array"
+        },
+        {
+          "name": "Created_At",
+          "type": "time"
+        }
+      ]
+    }
+  ]
+}'
+```
+
+## Réponse
+
+Deux réponses de code de statut existent pour cet endpoint : `201` et `400`.
+
+### Exemple de réponse réussie
+
+Le code de statut `201` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "catalogs": [
+    {
+      "description": "My Restaurants",
+      "fields": [
+        {
+          "name": "id",
+          "type": "string"
+        },
+        {
+          "name": "Name",
+          "type": "string"
+        },
+        {
+          "name": "City",
+          "type": "string"
+        },
+        {
+          "name": "Cuisine",
+          "type": "string"
+        },
+        {
+          "name": "Rating",
+          "type": "number"
+        },
+        {
+          "name": "Loyalty_Program",
+          "type": "boolean"
+        },
+        {
+          "name": "Location",
+          "type": "object"
+        },
+        {
+          "name": "Top_Dishes",
+          "type": "array"
+        },
+        {
+          "name": "Created_At",
+          "type": "time"
+        }
+      ],
+      "name": "restaurants",
+      "num_items": 0,
+      "updated_at": "2022-11-02T20:04:06.879+00:00"
+    }
+  ],
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "catalog-name-already-exists",
+      "message": "A catalog with that name already exists",
+      "parameters": [
+        "name"
+      ],
+      "parameter_values": [
+        "restaurants"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `catalog-array-invalid` | `catalogs` doit être un tableau d’objets. |
+| `catalog-name-already-exists` | Un catalogue avec ce nom existe déjà. |
+| `catalog-name-too-large`  | La limite de caractères d’un nom de catalogue est de 250. |
+| `description-too-long` | La limite de caractères pour la description est de 250. |
+| `field-names-not-unique` | Le même nom de champ est référencé deux fois. |
+| `field-names-too-large` | La limite de caractères d’un nom de champ est de 250. |
+| `id-not-first-column` | Le champ `id` doit être le premier champ dans le tableau. Vérifiez que le type est une chaîne de caractères. |
+| `invalid-catalog-name` | Le nom de catalogue peut uniquement inclure des chiffres, des lettres, des traits d’union et des traits de soulignement. |
+| `invalid-field-names` | Les champs peuvent uniquement inclure des chiffres, des lettres, des traits d’union et des traits de soulignement. |
+| `invalid-field-types` | Assurez-vous que les types des champs sont valides. |
+| `invalid-fields` | `fields` n’est pas formaté correctement. |
+| `too-many-catalog-atoms` | Vous ne pouvez créer qu’un catalogue par requête. |
+| `too-many-fields` | Le nombre de champs est limité à 500. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections.md
new file mode 100644
index 00000000000..d4b2265cf97
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections.md
@@ -0,0 +1,6 @@
+---
+nav_title: Sélections du catalogue
+config_only: true
+noindex: true
+page_order: 4
+---
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections/asynchronous.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections/asynchronous.md
new file mode 100644
index 00000000000..ddd3d46c71e
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections/asynchronous.md
@@ -0,0 +1,6 @@
+---
+nav_title: Asynchrone
+config_only: true
+noindex: true
+page_order: 1
+---
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection.md
new file mode 100644
index 00000000000..639dcc6b2cf
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection.md
@@ -0,0 +1,93 @@
+---
+nav_title: "DELETE : Supprimer la sélection du catalogue"
+article_title: "DELETE : Supprimer la sélection du catalogue"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente les détails du point de terminaison Supprimer la sélection de catalogue de Braze."
+
+---
+{% api %}
+# Supprimer la sélection du catalogue
+{% apimethod delete %}
+/catalogs/{catalog_name}/selections/{selection_name}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer une sélection de catalogue.
+{% alert important %}
+Cet endpoint est actuellement en accès anticipé. Contactez votre gestionnaire de satisfaction client si vous souhaitez participer à cet accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.delete_selection`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='asynchronous catalog selections' %}
+
+## Paramètres de chemin
+
+| Paramètre        | Requis | Type de données | Description                    |
+| ---------------- | -------- | --------- | ------------------------------ |
+| `catalog_name`   | Requis | Chaîne de caractères    | Nom du catalogue.           |
+| `selection_name` | Requis | Chaîne de caractères    | Nom de la sélection du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request DELETE 'https://rest.iad-03.braze.com/catalogs/restaurants/selections/favorite_list' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+```
+
+## Réponse
+
+Deux réponses de code de statut existent pour cet endpoint : `202` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant :
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `404` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "catalog-not-found",
+      "message": "Could not find catalog",
+      "parameters": [
+        "catalog_name"
+      ],
+      "parameter_values": [
+        "restaurants"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes 
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur                | Résolution des problèmes                                          |
+| -------------------- | -------------------------------------------------------- |
+| `catalog-not-found`  | Vérifiez que le nom du catalogue est valide.                    |
+| `invalid-selection`  | Vérifiez que le nom de la sélection est valide.                  |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections.md b/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections.md
new file mode 100644
index 00000000000..6d9e50a3150
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections.md
@@ -0,0 +1,138 @@
+---
+nav_title: "POST : Créer une sélection de catalogue"
+article_title: "POST : Créer une sélection de catalogue"
+search_tag: Endpoint
+page_order: 2
+
+layout: api_page
+page_type: reference
+description: "Cet article présente les détails du point de terminaison Créer une sélection de catalogue Braze."
+
+---
+{% api %}
+# Créer une sélection dans le catalogue
+{% apimethod post %}
+/catalogs/{catalog_name}/selections
+{% endapimethod %}
+
+> Utilisez cet endpoint pour créer une sélection dans votre catalogue.
+{% alert important %}
+Cet endpoint est actuellement en accès anticipé. Contactez votre gestionnaire de satisfaction client si vous souhaitez participer à cet accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `catalogs.create_selection`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='asynchronous catalog selections' %}
+
+## Paramètres de chemin
+
+| Paramètre      | Requis | Type de données | Description          |
+| -------------- | -------- | --------- | -------------------- |
+| `catalog_name` | Requis | Chaîne de caractères    | Nom du catalogue. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+| Paramètre   | Requis | Type de données | Description                                                                                                                                                        |
+| ----------- | -------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `selection` | Requis | Objet    | Un objet qui contient des critères de sélection. Les objets de sélection peuvent contenir `name`, `description`, `filters`, `results_limit`, `sort_field`, et `sort_order`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request POST 'https://rest.iad-03.braze.com/catalogs/restaurants/selections' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "selection": {
+    "name": "favorite-restaurants",
+    "description": "Favorite restaurants in NYC",
+    "filters": [
+      {
+        "field": "City",
+        "operator": "equals",
+        "value": "NYC"
+      },
+      {
+        "field": "Rating",
+        "operator": "greater than",
+        "value": 7
+      }
+    ]
+  }
+}'
+```
+
+### Opérateurs de filtrage
+
+| Type de champ | Opérateurs pris en charge                                     |
+| ---------- | ------------------------------------------------------- |
+| `string`   | `equals`, `does not equal`                              |
+| `number`   | `equals`, `does not equal`, `greater than`, `less than` |
+| `boolean`  | `is`                                                    |
+| `time`     | `before`, `after`                                       |
+| `array`    | `includes value`, `does not include value`              |
+{: .reset-td-br-1 .reset-td-br-2}
+
+## Réponse
+
+Trois réponses de code de statut existent pour cet endpoint : `202`, `400` et `404`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "errors": [
+    {
+      "id": "catalog-not-found",
+      "message": "Could not find catalog",
+      "parameters": [
+        "catalog_name"
+      ],
+      "parameter_values": [
+        "restaurants"
+      ]
+    }
+  ],
+  "message": "Invalid Request"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur                                | Résolution des problèmes                                                                               |
+|--------------------------------------|-----------------------------------------------------------------------------------------------|
+| `catalog-not-found`                  | Vérifiez que le nom du catalogue est valide.                                                         |
+| `company-size-limit-already-reached` | La limite de taille de stockage du catalogue est atteinte.                                                    |
+| `selection-limit-reached`            | La limite des sélections du catalogue est atteinte.                                                      |
+| `invalid-selection`                  | Vérifiez que la sélection est valide.                                                            |
+| `too-many-filters`                   | Vérifiez si la sélection comporte trop de filtres.                                                  |
+| `selection-name-already-exists`      | Vérifier si le nom de la sélection existe déjà dans le catalogue.                                    |
+| `selection-has-invalid-filter`       | Vérifiez que le filtre de sélection est valide.                                                       |
+| `selection-invalid-results-limit`    | Vérifiez que la limite des résultats de la sélection est valide.                                                |
+| `invalid-sorting`                    | Vérifier si le tri de la sélection est valide.                                                      |
+| `invalid-sort-field`                 | Vérifier si le champ de tri de la sélection est valide.                                                   |
+| `invalid-sort-order`                 | Vérifier si l'ordre de tri de la sélection est valide.                                                   |
+| `selection-contains-too-many-arrays` | Vérifiez si la sélection contient plus d'un champ de type `array`. Un seul est pris en charge. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/cdi.md b/_lang/fr_fr/_api/endpoints/cdi.md
new file mode 100644
index 00000000000..b098cd1bf37
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/cdi.md
@@ -0,0 +1,28 @@
+---
+nav_title: Ingestion de données cloud
+article_title: "Points de terminaison d'ingestion de données cloud"
+search_tag: Endpoint
+page_order: 0.5
+layout: dev_guide
+alias: /api/cdi/
+
+description: "Cette page d'accueil répertorie les endpoints d'ingestion de données cloud dans Braze."
+page_type: landing
+
+guide_top_header: "Points de terminaison d'ingestion de données cloud"
+guide_top_text: "Utilisez les points de terminaison d'ingestion de données cloud de Braze pour gérer vos intégrations et synchronisations de data warehouse."
+
+guide_featured_title: ""
+guide_featured_list:
+  - name: "GET : Intégrations de liste"
+    link: /docs/api/cdi/get_integration_list/
+    image: /assets/img/braze_icons/list.svg
+  - name: "GET : Liste Statut de Synchronisation des Emplois"
+    link: /docs/api/cdi/get_job_sync
+    image: /assets/img/braze_icons/list.svg
+  - name: "POST : Déclencher la synchronisation"
+    link: /docs/api/cdi/post_trigger_sync/
+    image: /assets/img/braze_icons/play.svg
+
+---
+
diff --git a/_lang/fr_fr/_api/endpoints/cdi/get_integration_list.md b/_lang/fr_fr/_api/endpoints/cdi/get_integration_list.md
new file mode 100644
index 00000000000..253b10abf6b
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/cdi/get_integration_list.md
@@ -0,0 +1,102 @@
+---
+nav_title: "GET : Intégrations de listes"
+article_title: "GET : Intégrations de listes"
+search_tag: Endpoint
+page_order: 1
+alias: /api/cdi/get_integration_list/
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Lister des intégrations."
+
+---
+{% api %}
+# Intégrations de listes
+{% apimethod get %}
+/cdi/integrations
+{% endapimethod %}
+
+> Utilisez cet endpoint pour obtenir une liste des intégrations existantes.
+
+
+{% alert note %}
+Pour utiliser cet endpoint, vous devrez générer une clé API avec l’autorisation `cdi.integration_list`.
+{% endalert %}
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='cdi list integrations' %}
+
+## Paramètres de recherche
+
+Chaque appel à cet endpoint renverra 10 éléments. Pour une liste comportant plus de 10 intégrations, utilisez l'en-tête `Link` pour récupérer les données à la page suivante, comme le montre l'exemple de réponse.
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `cursor` | Facultatif | Chaîne de caractères | Détermine la pagination de la liste d'intégration. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+### Sans curseur
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/cdi/integrations' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+### Avec curseur
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/cdi/integrations?cursor=c2tpcDow' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+### Exemple de réponse réussie
+
+Le code de statut `200` pourrait renvoyer le corps de réponse suivant.
+
+{% alert note %}
+L’en-tête `Link` n’existera pas s’il y a, au total, 10 intégrations ou moins. Pour les appels sans curseur, `prev` ne s’affichera pas. Lors de la consultation de la dernière page de produits, `next` ne s’affichera pas.
+{% endalert %}
+
+```
+Link: </cdi/integrations?cursor=c2tpcDow>; rel="prev",</cdi/integrations?cursor=c2tpcDoxMDA=>; rel="next"
+```
+
+```json
+{
+  "results": [
+    {
+      "integration_id": (string) integration ID,
+      "app_group_id": (string) app group ID,
+      "integration_name": (string) integration name,
+      "integration_type": (string) integration type,
+      "integration_status": (string) integration status,
+      "contact_emails": (string) contact email(s),
+      "last_updated_at": (string) last timestamp that was synced in ISO 8601,
+      "warehouse_type": (string) data warehouse type,
+      "last_job_start_time": (string) timestamp of the last sync run in ISO 8601,
+      "last_job_status": (string) status of the last sync run,
+      "next_scheduled_run": (string) timestamp of the next scheduled sync in ISO 8601,
+    },
+  ],
+  "message": "success"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `400 Invalid cursor` | Vérifiez que votre `cursor` est valide. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+Pour connaître les autres codes d'état et les messages d'erreur associés, reportez-vous à la section [Erreurs fatales et réponses.]({{site.baseurl}}/api/errors/#fatal-errors)
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/cdi/get_job_sync_status.md b/_lang/fr_fr/_api/endpoints/cdi/get_job_sync_status.md
new file mode 100644
index 00000000000..44fd283a856
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/cdi/get_job_sync_status.md
@@ -0,0 +1,113 @@
+---
+nav_title: "GET : Liste de l'état de synchronisation des travaux"
+article_title: "GET : Liste de l'état de synchronisation des travaux"
+search_tag: Endpoint
+page_order: 1
+alias: /api/cdi/get_job_sync/
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Répertorier l’état de synchronisation d’une tâche."
+
+---
+{% api %}
+# Liste de l'état de synchronisation des travaux
+{% apimethod get %}
+/cdi/integrations/{integration_id}/job_sync_status
+{% endapimethod %}
+
+> Utilisez cet endpoint pour renvoyer une liste des états de synchronisation passés pour une intégration donnée.
+
+{% alert note %}
+Pour utiliser cet endpoint, vous devrez générer une clé API avec l’autorisation `cdi.integration_job_status`.
+{% endalert %}
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='cdi job sync status' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `integration_id` | Requis | Chaîne de caractères | ID d'intégration. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de recherche
+
+Chaque appel à cet endpoint renverra 10 éléments. Pour une intégration avec plus de 10 synchronisations, utilisez l'en-tête `Link` pour récupérer les données sur la page suivante, comme le montre l'exemple de réponse suivant.
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `cursor` | Facultatif | Chaîne de caractères | Détermine la pagination de l'état de synchronisation. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+### Sans curseur
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/cdi/integrations/00000000-0000-0000-0000-000000000000/job_sync_status' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+### Avec curseur
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/cdi/integrations/00000000-0000-0000-0000-000000000000/job_sync_status?cursor=c2tpcDow' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+### Exemple de réponse réussie
+
+Le code de statut `200` pourrait renvoyer le corps de réponse suivant.
+
+{% alert note %}
+L'en-tête `Link` n'existe pas si le nombre total de synchronisations est inférieur ou égal à 10. Pour les appels sans curseur, `prev` ne s’affichera pas. Lors de la consultation de la dernière page de produits, `next` ne s’affichera pas.
+{% endalert %}
+
+```
+Link: </cdi/integrations/00000000-0000-0000-0000-000000000000/job_sync_status?cursor=c2tpcDow>; rel="prev",</cdi/integrations00000000-0000-0000-0000-000000000000/job_sync_status?cursor=c2tpcDoxMDA=>; rel="next"
+```
+
+```json
+{
+  "results": [
+    {
+        "job_status": (string) status of the sync, see below for explanation of different statuses,
+        "sync_start_time": (string) time the sync started in ISO 8601,
+        "sync_finish_time": (string) time the sync finished in ISO 8601,
+        "last_timestamp_synced": (string) last UPDATED_AT timestamp processed by the sync in ISO 8601,
+        "rows_synced": (integer) number of rows successfully synced to Braze,
+        "rows_failed_with_errors": (integer) number of rows failed because of errors,
+    },
+  ],
+  "message": "success"
+}
+```
+
+| état_du_travail | Explication |
+| --- | --- |
+| `running` | Le travail est en cours d'exécution. |
+| `success` | Toutes les lignes ont été synchronisées avec succès. |
+| `partial` | Certaines lignes n'ont pas été synchronisées en raison d'erreurs. |
+| `error` | Aucune ligne n'a été synchronisée. |
+| `config_error` | Une erreur s'est produite dans la configuration de l'intégration. Vérifiez votre configuration d'intégration. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `400 Invalid cursor` | Vérifiez que votre `cursor` est valide. |
+| `400 Invalid integration ID` | Vérifiez que votre `integration_id` est valide. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+Pour connaître les autres codes d'état et les messages d'erreur associés, veuillez vous reporter à la section [Erreurs fatales et réponses.]({{site.baseurl}}/api/errors/#fatal-errors)
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/cdi/post_job_sync.md b/_lang/fr_fr/_api/endpoints/cdi/post_job_sync.md
new file mode 100644
index 00000000000..8776b507b2f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/cdi/post_job_sync.md
@@ -0,0 +1,68 @@
+---
+nav_title: "POST : Synchronisation des déclencheurs"
+article_title: "POST : Synchronisation des déclencheurs"
+search_tag: Endpoint
+page_order: 2
+alias: /api/cdi/post_trigger_sync/
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Déclencher la synchronisation."
+
+---
+{% api %}
+# Déclencher une synchronisation
+{% apimethod post %}
+/cdi/integrations/{integration_id}/sync
+{% endapimethod %}
+
+> Utilisez cet endpoint pour déclencher une synchronisation pour une intégration donnée.
+
+{% alert note %}
+Pour utiliser cet endpoint, vous devrez générer une clé API avec l’autorisation `cdi.integration_sync`.
+{% endalert %}
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='cdi job sync' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `integration_id` | Requis | Chaîne de caractères | ID d'intégration. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request POST 'https://rest.iad-03.braze.com/cdi/integrations/00000000-0000-0000-0000-000000000000/sync' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant :
+
+```json
+{
+  "message": "success"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `400 Invalid integration ID` | Vérifiez que votre `integration_id` est valide. |
+| `404 Integration not found` | Il n'existe pas d'intégration pour l'ID d'intégration donné. Assurez-vous que votre ID d'intégration est valide. |
+| `429 Another job is in progress` | Une synchronisation est actuellement en cours pour cette intégration. Réessayez une fois la synchronisation terminée. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+Pour connaître les autres codes d'état et les messages d'erreur associés, veuillez vous reporter à la section [Erreurs fatales et réponses.]({{site.baseurl}}/api/errors/#fatal-errors)
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/email.md b/_lang/fr_fr/_api/endpoints/email.md
new file mode 100644
index 00000000000..41bfe58efec
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email.md
@@ -0,0 +1,37 @@
+---
+nav_title: "Listes et adresses e-mail"
+article_title: Endpoints des listes et adresses e-mail
+search_tag: Endpoint
+page_order: 1
+layout: dev_guide
+
+description: "Cette page d’accueil explique et répertorie les endpoints Braze de listes et adresses e-mail."
+page_type: landing
+
+guide_top_header: "Endpoints des listes et adresses e-mail"
+guide_top_text: "Grâce à cet ensemble d'endpoints, vous pouvez mettre à jour l'état de l'abonnement d'un utilisateur à un e-mail et utiliser l'API de Braze pour mettre en place une synchronisation bidirectionnelle entre Braze et d'autres systèmes d'e-mail ou votre propre base de données."
+
+guide_featured_title: ""
+guide_featured_list:
+  - name: "GET : Répertorier les échecs d'envoi définitifs"
+    link: /docs/api/endpoints/email/get_list_hard_bounces/
+    image: /assets/img/braze_icons/message-plus-square.svg
+  - name: "GET : Extraire les adresses e-mail désinscrites"
+    link: /docs/api/endpoints/email/get_query_unsubscribed_email_addresses/
+    image: /assets/img/braze_icons/mail-01.svg
+  - name: "POST : Modifier le statut de l’abonnement aux e-mails"
+    link: /docs/api/endpoints/email/post_email_subscription_status/
+    image: /assets/img/braze_icons/at-sign.svg
+  - name: "POST : Supprimer les e-mails ayant reçu un échec d'envoi définitif"
+    link: /docs/api/endpoints/email/post_remove_hard_bounces/
+    image: /assets/img/braze_icons/message-plus-square.svg
+  - name: "POST : Supprimer les courriers indésirables"
+    link: /docs/api/endpoints/email/post_remove_spam/
+    image: /assets/img/braze_icons/mail-04.svg
+  - name: "POST : Ajouter l’e-mail à la liste de blocage"
+    link: /docs/api/endpoints/email/post_blocklist/
+    image: /assets/img/braze_icons/mail-04.svg
+---
+{% comment %}
+redirection à partir de email_sync.md
+{% endcomment %}
diff --git a/_lang/fr_fr/_api/endpoints/email/delete_remove_subscription_state.md b/_lang/fr_fr/_api/endpoints/email/delete_remove_subscription_state.md
new file mode 100644
index 00000000000..1ef3b2c2d53
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email/delete_remove_subscription_state.md
@@ -0,0 +1,50 @@
+---
+nav_title: "DELETE : Supprimer le statut d’abonnement par adresse e-mail ou numéro de téléphone"
+article_title: "DELETE : Supprimer le statut d’abonnement par adresse e-mail ou numéro de téléphone"
+search_tag: Endpoint
+page_order: 0
+hidden: true
+layout: api_page
+page_type: reference
+description: "Cet article présente les détails concernant l’endpoint Supprimer le statut d’abonnement par adresse e-mail ou numéro de téléphone de Braze."
+
+---
+
+{% api %}
+# Supprimer le statut d’abonnement par adresse e-mail ou numéro de téléphone
+{% apimethod delete %}
+/utilisateurs/abonnement
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer la valeur de l'état de l'abonnement basée sur une adresse e-mail ou un numéro de téléphone.
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --- | --- | --- | --- |
+| `email` | Oui | Chaîne de caractères | L'adresse e-mail de l'utilisateur (doit comprendre au moins une adresse et au plus 50 adresses). |
+| `phone` | Oui | Chaîne de caractères | Le numéro de téléphone de l'utilisateur (doit comprendre au moins un numéro de téléphone et au plus 50 numéros de téléphone). Nous vous recommandons de fournir ces informations sous le format E.164. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+  {phone: "+12125551212"},
+  {email: "dont.spam@me.com"},
+  {phone: "+17185551212"}
+}
+```
+
+## Réponse
+
+```json
+{
+  "status": "The emails and/or phone numbers have been queued for deletion",
+  "message": "success"
+}
+```
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/email/get_list_hard_bounces.md b/_lang/fr_fr/_api/endpoints/email/get_list_hard_bounces.md
new file mode 100644
index 00000000000..82a4f0ba2e0
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email/get_list_hard_bounces.md
@@ -0,0 +1,76 @@
+---
+nav_title: "GET : Extraire les e-mails ayant reçu un échec d'envoi définitif"
+article_title: "GET : Extraire les e-mails ayant reçu un échec d'envoi définitif"
+search_tag: Endpoint
+page_order: 1
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Interroger ou lister les adresses e-mail ayant reçu un échec d'envoi définitif."
+
+---
+{% api %}
+# Extraire les e-mails ayant reçu un échec d'envoi définitif
+{% apimethod get %}
+/email/rebonds_durs
+{% endapimethod %}
+
+> Utilisez cet endpoint pour extraire une liste d’adresses e-mail ayant rejeté définitivement vos e-mails au cours d'une certaine période.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#7c2ef84f-ddf5-451a-a72c-beeabc06ad9d {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `email.hard_bounces`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| ----------|-----------| ----------|----- |
+| `start_date` | Facultatif<br>(voir la note) | Chaîne de caractères au format YYYY-MM-DD| Date de début de la période pour récupérer les échecs d'envoi définitifs. Doit être antérieure à `end_date`. Ce traitement est effectué à minuit (UTC) par l’API. |
+| `end_date` | Facultatif<br>(voir la note) | Chaîne de caractères au format YYYY-MM-DD | Date de fin de la période d'extraction des échecs d'envoi définitifs. Ce traitement est effectué à minuit (UTC) par l’API. |
+| `limit` | Facultatif | Entier | Champ facultatif pour limiter le nombre de résultats renvoyés. Par défaut à 100, le maximum est 500. |
+| `offset` | Facultatif | Entier | Point de départ facultatif dans la liste où récupérer les informations. |
+| `email` | Facultatif<br>(voir la note) | Chaîne de caractères | S’il est fourni, nous enverrons un message indiquant si l’utilisateur a reçu un échec d'envoi définitif ou non. Vérifiez que les chaînes d'e-mails sont correctement formatées. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+{% alert note %}
+Vous devez fournir une `start_date` et une `end_date`, OU un `email`. Si vous fournissez les trois, une `start_date`, une `end_date`, et un `email`, nous donnerons la priorité aux e-mails communiqués et ignorerons la plage de dates.
+{% endalert %}
+
+Si votre plage de dates dépasse le nombre `limit` d'échecs d'envoi définitifs, vous devrez effectuer plusieurs appels d’API, en augmentant à chaque fois le `offset` jusqu’à ce qu’un appel renvoie un résultat inférieur à `limit` ou égal à zéro. L'inclusion des paramètres `offset` et `limit` avec `email` peut renvoyer une réponse vide. 
+
+## Exemple de demande
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/email/hard_bounces?start_date=2019-01-01&end_date=2019-02-01&limit=100&offset=1&email=example@braze.com' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE'
+```
+
+## Réponse
+Les entrées sont répertoriées par ordre décroissant.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "emails": [
+    {
+      "email": (string) an email that has hard bounced,
+      "unsubscribed_at": (string) the time the email hard bounced in ISO 8601
+    },
+    {
+      "email": (string) an email that has hard bounced,
+      "unsubscribed_at": (string) the time the email hard bounced in ISO 8601
+    },
+    {
+      "email": (string) an email that has hard bounced,
+      "unsubscribed_at": (string) the time the email hard bounced in ISO 8601
+    }
+  ],
+  "message": "success"
+}
+```
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/email/get_query_by_email_or_phone.md b/_lang/fr_fr/_api/endpoints/email/get_query_by_email_or_phone.md
new file mode 100644
index 00000000000..0a99b6b12d2
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email/get_query_by_email_or_phone.md
@@ -0,0 +1,72 @@
+---
+nav_title: "GET : Liste de l'État d'abonnement avec l'adresse e-mail ou le numéro de téléphone"
+article_title: "GET : Liste de l'État d'abonnement avec l'adresse e-mail ou le numéro de téléphone"
+search_tag: Endpoint
+page_order: 2
+hidden: true
+layout: api_page
+page_type: reference
+description: "Cet article présente les détails de l'état de l'abonnement à la liste avec une adresse e-mail ou un numéro de téléphone du point de terminaison Braze."
+
+---
+{% api %}
+# Liste de l'état de l'abonnement avec une adresse e-mail ou un numéro de téléphone
+{% apimethod get %}
+/utilisateurs/abonnement
+{% endapimethod %}
+
+> Utilisez cet endpoint pour renvoyer la valeur de l'état de l'abonnement en fonction d'une adresse e-mail ou d'un numéro de téléphone.
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --- | --- | --- | --- |
+| `email` | Oui | Chaîne de caractères | L'adresse e-mail de l'utilisateur (doit comprendre au moins une adresse et au plus 50 adresses). |
+| `phone` | Oui | Chaîne de caractères | Le numéro de téléphone de l'utilisateur (doit comprendre au moins un numéro de téléphone et au plus 50 numéros de téléphone). Nous vous recommandons de fournir ces informations sous le format E.164. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/users/subscriptions?phone=+12123355555&email=example%40braze.com' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY'
+```
+
+## Réponse
+
+Les entrées sont répertoriées par ordre décroissant.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "emails": [
+    {
+      "email": "example@braze.com",
+      "email_subscribe": {
+        "email_subscription_event_date": "2019-11-20T19:58:04.825Z",
+        "email_subscription_state": "Subscribed"
+      },
+      "subscription_group": [
+        {
+          "subscription_group_id": "5f5536d2a76e0f4e323a1234",
+          "subscription_group_event_date": "2021-03-11T21:29:22.347Z",
+          "subscription_group_state": "Unsubscribed"
+        }
+      ],
+      "hard_bounced_at": null,
+      "spam_at": null
+    }
+  ],
+	"phone": [{
+		"phone": "+12123355555",
+		"subscription_group": [{
+			"subscription_group_id": "3f5536d2a76e0f4e323a5555",
+			"subscription_group_state": "Subsscribed",
+			"subscription_group_event_date": "2021-03-11T21:29:22.347Z"
+		}]
+	}],
+	"message": "success"
+}
+```
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/email/get_query_unsubscribed_email_addresses.md b/_lang/fr_fr/_api/endpoints/email/get_query_unsubscribed_email_addresses.md
new file mode 100644
index 00000000000..036dd9e8e45
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email/get_query_unsubscribed_email_addresses.md
@@ -0,0 +1,80 @@
+---
+nav_title: "GET : Requête de la liste des adresses e-mail désinscrites"
+article_title: "GET : Requête de la liste des adresses e-mail désinscrites"
+search_tag: Endpoint
+page_order: 3
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Récupérer la liste ou Interroger les désabonnements par e-mail."
+
+---
+{% api %}
+# Extraire la liste des adresses e-mail désinscrites
+{% apimethod get %}
+/email/unsubscribes
+{% endapimethod %}
+
+> Utilisez cet endpoint pour renvoyer les e-mails qui ont été désinscrits entre le `start_date` et le `end_date`. Pour un historique complet de l'état de l'abonnement, utilisez [Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents) pour suivre ces données.
+
+Vous pouvez utiliser cet endpoint pour configurer une synchronisation bidirectionnelle entre Braze et d’autres systèmes de messagerie ou votre propre base de données.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#d2966b81-188a-407b-ba7e-e6c252c44b4a {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `email.unsubscribe`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| ----------|-----------| ---------|------ |
+| `start_date` | Facultatif <br>(voir la note) | Chaîne de caractères au format YYYY-MM-DD| Date de début de l'intervalle de récupération des désabonnements, doit être antérieure à la date de fin. Ce traitement est effectué à minuit (UTC) par l’API. |
+| `end_date` | Facultatif <br>(voir la note) | Chaîne de caractères au format YYYY-MM-DD | La date de fin de la plage pour récupérer les désinscriptions. Ce traitement est effectué à minuit (UTC) par l’API. |
+| `limit` | Facultatif | Entier | Champ facultatif pour limiter le nombre de résultats renvoyés. Par défaut à 100, le maximum est 500. |
+| `offset` | Facultatif | Entier | Point de départ facultatif dans la liste où récupérer les informations. |
+| `sort_direction` | Facultatif | Chaîne de caractères | Indiquez la valeur `asc` pour trier les désinscriptions de la plus ancienne à la plus récente. Indiquez la valeur `desc` pour trier de la plus récente à la plus ancienne. Si `sort_direction` n’est pas inclus, l’ordre par défaut est du plus récent au plus ancien. |
+| `email` | Facultatif <br>(voir la note) | Chaîne de caractères | S’il est fourni, nous renverrons si l’utilisateur s’est désinscrit ou pas. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+{% alert note %}
+Vous devez fournir une `end_date`, ainsi qu’un `email` ou une `start_date`.
+{% endalert %}
+
+Si votre plage de dates dépasse le nombre `limit` de désinscriptions, vous devrez effectuer plusieurs appels d’API, en augmentant à chaque fois le `offset` jusqu’à ce qu’un appel renvoie un résultat inférieur à `limit` ou égal à zéro.
+
+## Exemple de demande 
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/email/unsubscribes?start_date=2020-01-01&end_date=2020-02-01&limit=1&offset=1&sort_direction=desc&email=example@braze.com' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE'
+```
+
+## Réponse
+
+Les entrées sont répertoriées par ordre décroissant.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "emails": [
+    {
+      "email": (string) an email that has been unsubscribed,
+      "unsubscribed_at": (string) the time the email was unsubscribed in ISO 8601
+    },
+    {
+      "email": (string) an email that has been unsubscribed,
+      "unsubscribed_at": (string) the time the email was unsubscribed in ISO 8601
+    },
+    {
+      "email": (string) an email that has been unsubscribed,
+      "unsubscribed_at": (string) the time the email was unsubscribed in ISO 8601
+    }
+  ],
+  "message": "success"
+}
+```
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/email/post_blacklist.md b/_lang/fr_fr/_api/endpoints/email/post_blacklist.md
new file mode 100644
index 00000000000..a69b748130c
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email/post_blacklist.md
@@ -0,0 +1,66 @@
+---
+nav_title: "POST : Ajouter des e-mails à la liste noire"
+article_title: "POST : Ajouter des e-mails à la liste noire"
+search_tag: Endpoint
+page_order: 10
+layout: api_page
+page_type: reference
+alias: /blacklist/
+description: "Cet article présente en détail l’endpoint Braze Mettre des e-mails en liste noire."
+
+---
+{% api %}
+# Ajouter des e-mails à la liste noire
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/email/blacklist
+{% endapimethod %}
+
+{% alert important %}
+Braze a publié le [`/email/blocklist` point de terminaison]({{site.baseurl}}/api/endpoints/email/post_blocklist/) avec la même fonctionnalité que le point de terminaison `/email/blacklist`. Nous vous recommandons d'utiliser plutôt le point de terminaison `/email/blocklist`.
+{% endalert %}
+
+> Utilisez cet endpoint pour désinscrire un utilisateur des e-mails et le marquer comme rejeté définitivement.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#d51155a1-a6e8-4dcc-9f2b-88c54ab9e8c6 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `email.blacklist`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "email": ["blacklist_email1","blacklist_email2"]
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| -----------|----------| --------|------- |
+| `email` | Requis | Chaîne de caractères ou tableau | Envoyez une adresse e-mail par chaîne de caractères ou un tableau de 50 adresses e-mail à la liste noire. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/email/blacklist' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+--data-raw '{
+  "email": ["blacklist_email1","blacklist_email2"]
+}'
+```
+
+{% endapi %}
+
+
diff --git a/_lang/fr_fr/_api/endpoints/email/post_blocklist.md b/_lang/fr_fr/_api/endpoints/email/post_blocklist.md
new file mode 100644
index 00000000000..9191327b25d
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email/post_blocklist.md
@@ -0,0 +1,59 @@
+---
+nav_title: "POST : Ajouter des e-mails à la liste de blocage"
+article_title: "POST : Ajouter des e-mails à la liste de blocage"
+search_tag: Endpoint
+page_order: 8
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre des e-mails en liste de blocage."
+
+---
+{% api %}
+# Ajouter des e-mails à la liste de blocage
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/email/blocklist
+{% endapimethod %}
+
+> Utilisez cet endpoint pour désinscrire un utilisateur des e-mails et le marquer comme rejeté définitivement.
+ 
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#d51155a1-a6e8-4dcc-9f2b-88c54ab9e8c6 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `email.blacklist`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "email": ["blocklist_email1","blocklist_email2"]
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| -----------|----------| --------|------- |
+| `email` | Requis | Chaîne de caractères ou tableau | Adresse e-mail par chaîne de caractères ou un tableau de 50 adresses e-mail à ajouter à la liste de blocage. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/email/blocklist' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+--data-raw '{
+  "email": ["blocklist_email1","blocklist_email2"]
+}'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/email/post_email_subscription_status.md b/_lang/fr_fr/_api/endpoints/email/post_email_subscription_status.md
new file mode 100644
index 00000000000..8381fbd13cc
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email/post_email_subscription_status.md
@@ -0,0 +1,67 @@
+---
+nav_title: "POST : Modifier le statut de l’abonnement aux e-mails"
+article_title: "POST : Modifier le statut de l’abonnement aux e-mails"
+search_tag: Endpoint
+page_order: 5
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Modifier le statut d’abonnement aux e-mails de l’utilisateur."
+
+---
+{% api %}
+# Modifier le statut de l’abonnement aux e-mails
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/email/status
+{% endapimethod %}
+
+> Utilisez cet endpoint pour définir l’état de l’abonnement aux e-mails de vos utilisateurs. 
+
+Les utilisateurs peuvent avoir le statut `opted_in`, `unsubscribed`, ou `subscribed` (sans confirmation d’abonnement/de désabonnement spécifique).
+
+Vous pouvez définir l’état de l’abonnement aux e-mails pour une adresse e-mail qui n’est pas encore associée à l’un de vos utilisateurs dans Braze. Lorsque cette adresse e-mail est ensuite associée à un utilisateur, l’état de l’abonnement aux e-mails que vous avez téléchargé sera automatiquement défini.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#be852462-0cda-4a48-b68b-85bd8a9f2147 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `email.status`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "email": "example@braze.com",
+  "subscription_state": "subscribed"
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `email` | Requis | Chaîne de caractères ou tableau | Envoyez une adresse e-mail par chaîne de caractères ou un tableau de 50 adresses e-mail pour effectuer des modifications. |
+| `subscription_state` | Requis | Chaîne de caractères | Soit "abonné", "désabonné" ou "opted_in". |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/email/status' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+--data-raw '{
+  "email": "example@braze.com",
+  "subscription_state": "subscribed"
+}'
+```
+
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/email/post_remove_hard_bounces.md b/_lang/fr_fr/_api/endpoints/email/post_remove_hard_bounces.md
new file mode 100644
index 00000000000..dfd5b969aa4
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email/post_remove_hard_bounces.md
@@ -0,0 +1,59 @@
+---
+nav_title: "POST : Supprimer les e-mails ayant reçu un échec d'envoi définitif"
+article_title: "POST : Supprimer les e-mails ayant reçu un échec d'envoi définitif"
+search_tag: Endpoint
+page_order: 6
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Supprimer les adresses e-mail ayant reçu un échec d'envoi définitif."
+
+---
+{% api %}
+# Supprimer les e-mails ayant reçu un échec d'envoi définitif
+{% apimethod post %}
+/email/bounce/remove
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer les adresses e-mail de votre liste de rebonds de Braze et de la liste de rebonds mise à jour par votre fournisseur d’e-mails.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#7b87a884-fa20-4085-b9f1-18363103575f {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `email.bounce.remove`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "email": "example@braze.com"
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| ----------|-----------| ---------|------ |
+| `email` | Requis | Chaîne de caractères ou tableau | Envoyez une adresse e-mail par chaîne de caractères ou un tableau de 50 adresses e-mail pour effectuer des modifications. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/email/bounce/remove' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "email": "example@braze.com"
+}'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/email/post_remove_spam.md b/_lang/fr_fr/_api/endpoints/email/post_remove_spam.md
new file mode 100644
index 00000000000..a06ab8fb9ac
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/email/post_remove_spam.md
@@ -0,0 +1,57 @@
+---
+nav_title: "POST : Supprimer les adresses e-mail de la liste des courriers indésirables"
+article_title: "POST : Supprimer les adresses e-mail de la liste des courriers indésirables"
+search_tag: Endpoint
+page_order: 7
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Supprimer les adresses e-mail de la liste des courriers indésirables."
+
+---
+{% api %}
+# Supprimer les adresses e-mail de la liste des courriers indésirables
+{% apimethod post %}
+/email/spam/remove
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer les adresses e-mail de votre liste de courriers indésirables de Braze et de la liste de courriers indésirables mise à jour par votre fournisseur d’e-mails.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#1614a82f-510a-4c37-95a6-8207a125e487 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `email.spam.remove`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "email": "example@braze.com"
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| ----------|-----------| --------|------- |
+| `email` | Requis | Chaîne de caractères ou tableau | Envoyez une adresse e-mail par chaîne de caractères ou un tableau de 50 adresses e-mail pour effectuer des modifications. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/email/spam/remove' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "email": "example@braze.com"
+}'
+```
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export.md b/_lang/fr_fr/_api/endpoints/export.md
new file mode 100644
index 00000000000..22f373c5df1
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export.md
@@ -0,0 +1,132 @@
+---
+nav_title: Exporter
+article_title: Endpoints d’exportation
+search_tag: Endpoint
+page_order: 2
+
+layout: dev_guide
+
+#Required
+description: "Cette page d’accueil explique et répertorie les endpoints Braze d’exportation."
+page_type: landing
+
+guide_top_header: "Endpoints d’exportation"
+guide_top_text: "Avec cette collection de points de terminaison, vous pouvez accéder et exporter divers niveaux de détails sur vos KPI, cartes de flux d'actualités, sessions d'application, utilisateurs, segments, campagnes et Canvases. <br> <br> Assurez-vous de connaître votre <a href='/docs/user_guide/administrative/access_braze/braze_instances/' target='_blank'>instance Braze</a>, <a href='/docs/api/api_key/' target='_blank'>clé API</a> et <a href='/docs/api/identifier_types/' target='_blank'>identifiant d’API</a> lors de l’élaboration de vos paramètres et corps de requête."
+
+guide_featured_title: "Exporter les points de terminaison de la campagne"
+guide_featured_list:
+  - name: "GET : Analyse de campagne"
+    link: /docs/api/endpoints/export/campaigns/get_campaign_analytics/
+    image: /assets/img/braze_icons/bar-chart-01.svg
+  - name: "GET : Détails de la campagne"
+    link: /docs/api/endpoints/export/campaigns/get_campaign_details/
+    image: /assets/img/braze_icons/bar-chart-01.svg
+  - name: "GET : Liste des campagnes"
+    link: /docs/api/endpoints/export/campaigns/get_campaigns/
+    image: /assets/img/braze_icons/bar-chart-01.svg
+  - name: "GET : Envoyer des analyses"
+    link: /docs/api/endpoints/export/campaigns/get_send_analytics/
+    image: /assets/img/braze_icons/bar-chart-01.svg
+
+guide_menu_title: "Export Canvas endpoints"
+guide_menu_list:
+  - name: "GET : Analyse des séries de données de Canvas"
+    link: /docs/api/endpoints/export/canvas/get_canvas_analytics/
+    image: /assets/img/braze_icons/dataflow-03.svg
+  - name: "GET : Résumé de l’analyse des Canvas"
+    link: /docs/api/endpoints/export/canvas/get_canvas_analytics_summary/
+    image: /assets/img/braze_icons/dataflow-03.svg
+  - name: "GET : Informations relatives au canvas"
+    link: /docs/api/endpoints/export/canvas/get_canvas_details/
+    image: /assets/img/braze_icons/dataflow-03.svg
+  - name: "GET : Liste des Canvas"
+    link: /docs/api/endpoints/export/canvas/get_canvases/
+    image: /assets/img/braze_icons/dataflow-03.svg
+
+guide_menu_title2: "Export custom events endpoints"
+guide_menu_list2:
+  - name: "GET : Événements personnalisés"
+    link: /docs/api/endpoints/export/custom_events/get_custom_events_data/
+    image: /assets/img/braze_icons/line-chart-up-01.svg
+  - name: "GET : Liste des événements personnalisés"
+    link: /docs/api/endpoints/export/custom_events/get_custom_events/
+    image: /assets/img/braze_icons/line-chart-up-01.svg
+  - name: "GET : Analyse d’événements personnalisés"
+    link: /docs/api/endpoints/export/custom_events/get_custom_events_analytics/
+    image: /assets/img/braze_icons/line-chart-up-01.svg
+
+guide_menu_title3: "Export KPI endpoints"
+guide_menu_list3:
+  - name: "GET : Indicateurs clé de performance pour les nouveaux utilisateurs quotidiens par date"
+    link: /docs/api/endpoints/export/kpi/get_kpi_daily_new_users_date/
+    image: /assets/img/braze_icons/target-04.svg
+  - name: "GET : Indicateurs clé de performance pour les utilisateurs actifs quotidiens par date"
+    link: /docs/api/endpoints/export/kpi/get_kpi_dau_date/
+    image: /assets/img/braze_icons/target-04.svg
+  - name: "GET : Indicateurs clé de performance pour les utilisateurs actifs mensuels au cours des 30 derniers jours"
+    link: /docs/api/endpoints/export/kpi/get_kpi_mau_30_days/
+    image: /assets/img/braze_icons/target-04.svg
+  - name: "GET : Indicateurs clé de performance pour les désinstallations par date"
+    link: /docs/api/endpoints/export/kpi/get_kpi_uninstalls_date/
+    image: /assets/img/braze_icons/target-04.svg
+
+guide_menu_title4: "Export News Feed endpoints"
+guide_menu_list4:
+  - name: "GET : Statistiques d’engagement de carte de fil d’actualité"
+    link: /docs/api/endpoints/export/news_feed/get_news_feed_card_analytics/
+    image: /assets/img/braze_icons/download-cloud-01.svg
+  - name: "GET : Informations relatives à la carte de fil d’actualité"
+    link: /docs/api/endpoints/export/news_feed/get_news_feed_card_details/
+    image: /assets/img/braze_icons/download-cloud-01.svg
+  - name: "GET : Liste des cartes de fil d’actualité"
+    link: /docs/api/endpoints/export/news_feed/get_news_feed_cards/
+    image: /assets/img/braze_icons/download-cloud-01.svg
+
+guide_menu_title5: "Export purchase endpoints"
+guide_menu_list5:
+  - name: "GET : Liste des identifiants de produit"
+    link: /docs/api/endpoints/export/purchases/get_list_product_id/
+    image: /assets/img/braze_icons/list.svg
+  - name: "GET : Nombre d'achats"
+    link: /docs/api/endpoints/export/purchases/get_number_of_purchases/
+    image: /assets/img/braze_icons/list.svg
+  - name: "GET : Données de revenus par temps"
+    link: /docs/api/endpoints/export/purchases/get_revenue_series/
+    image: /assets/img/braze_icons/list.svg
+
+guide_menu_title6: "Export segment endpoints"
+guide_menu_list6:
+  - name: "GET : Liste des segments"
+    link: /docs/api/endpoints/export/segments/get_segment/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "GET : Analyses des segments"
+    link: /docs/api/endpoints/export/segments/get_segment_analytics/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "GET : Informations relatives au segment"
+    link: /docs/api/endpoints/export/segments/get_segment_details/
+    image: /assets/img/braze_icons/users-01.svg
+
+guide_menu_title7: "Export sessions endpoint"
+guide_menu_list7:
+  - name: "GET : Données de la série temporelle des sessions App"
+    link: /docs/api/endpoints/export/sessions/get_sessions_analytics/
+    image: /assets/img/braze_icons/tablet-01.svg
+
+guide_menu_title8: "Export user data endpoints"
+guide_menu_list8:
+  - name: "POST : Données utilisateur par identifiant"
+    link: /docs/api/endpoints/export/user_data/post_users_identifier/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "POST : Données utilisateur par segment"
+    link: /docs/api/endpoints/export/user_data/post_users_segment/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "POST : Données utilisateur par groupe de contrôle global"
+    link: /docs/api/endpoints/export/user_data/post_users_global_control_group/
+    image: /assets/img/braze_icons/users-01.svg
+
+guide_menu_title9: "Export custom attributes endpoints"
+guide_menu_list9:
+  - name: "GET : Attributs personnalisés"
+    link: /docs/api/endpoints/export/custom_attributes/get_custom_attributes/
+    image: /assets/img/braze_icons/line-chart-up-01.svg
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/campaigns.md b/_lang/fr_fr/_api/endpoints/export/campaigns.md
new file mode 100644
index 00000000000..03752b21f16
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/campaigns.md
@@ -0,0 +1,6 @@
+---
+nav_title: Campagnes
+config_only: true
+noindex: true
+page_order: 1
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/campaigns/get_campaign_analytics.md b/_lang/fr_fr/_api/endpoints/export/campaigns/get_campaign_analytics.md
new file mode 100644
index 00000000000..a85b2eafc20
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/campaigns/get_campaign_analytics.md
@@ -0,0 +1,294 @@
+---
+nav_title: "GET : Exporter l'analyse/analytique de la campagne (si utilisée comme adjectif)"
+article_title: "GET : Exporter l'analyse/analytique de la campagne (si utilisée comme adjectif)"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les analyses de campagne."
+
+---
+{% api %}
+# Exporter les analyses de campagne
+{% apimethod get %}
+/campagnes/séries_de_données
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer quotidiennement une série de diverses statistiques pour une campagne sur la durée. 
+
+Les données renvoyées comprennent le nombre de messages envoyés, ouverts, cliqués ou convertis par canal de communication.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#c07b5ebd-0246-471e-b154-416d63ae28a1 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `campaigns.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='export campaign analytics' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `campaign_id` | Requis | Chaîne de caractères | Voir l'[identifiant API de la campagne.]({{site.baseurl}}/api/identifier_types/)<br><br> Vous trouverez l'adresse `campaign_id` pour les campagnes API sur la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) et la page **Détails de la campagne** dans votre tableau de bord, ou vous pouvez utiliser l'[endpoint Liste des campagnes.]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaigns/) |
+| `length` | Requis | Entier | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `ending_at` | Facultatif | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande 
+
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/campaigns/data_series?campaign_id={{campaign_identifier}}&length=7&ending_at=2020-06-28T23:59:59-5:00' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponses
+
+### Réponse multicanaux
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time" : (string) the date as ISO 8601 date,
+            "messages" : {
+                "ios_push" : [
+                    {
+                      "variation_name": (string) the name of the message in the dashboard (eg., "iOS_Push"),
+                      "sent" : (int) the number of sends,
+                      "direct_opens" : (int) the number of direct opens,
+                      "total_opens" : (int) the number of total opens,
+                      "bounces" : (int) the number of bounces,
+                      "body_clicks" : (int) the number of body clicks,
+                      "revenue": (float) the number of dollars of revenue (USD),
+                      "unique_recipients": (int) the number of unique recipients,
+                      "conversions": (int) the number of conversions,
+                      "conversions_by_send_time": (int) the number of conversions attributed to the date the campaign was sent,
+                      "conversions1": (optional, int) the number of conversions for the second conversion event,
+                      "conversions1_by_send_time": (optional, int) the number of conversions for the second conversion event attributed to the date the campaign was sent,
+                      "conversions2": (optional, int) the number of conversions for the third conversion event,
+                      "conversions2_by_send_time": (optional, int) the number of conversions for the third conversion event attributed to the date the campaign was sent,
+                      "conversions3": (optional, int) the number of conversions for the fourth conversion event,
+                      "conversions3_by_send_time": (optional, int) the number of conversions for the fourth conversion event attributed to the date the campaign was sent
+                      "carousel_slide_[NUM]_[TITLE]_click": (optional, int) the number of carousel slide clicks,
+                      "notif_button_[NUM]_[TITLE]_click": (optional, int) the number of notification button clicks
+                    }
+                ],
+                "android_push" : [
+                    {
+                      "sent" : (int) the number of sends,
+                      "direct_opens" : (int) the number of direct opens,
+                      "total_opens" : (int)the number of total opens,
+                      "bounces" : (int) the number of bounces,
+                      "body_clicks" : (int) the number of body clicks
+                    }
+                ],
+                "webhook": [
+                    {
+                      "sent": (int) the number of sends,
+                      "errors": (int) the number of errors
+                    }
+                ],
+                "email" : [
+                    {
+                      "sent": (int) the number of sends,
+                      "opens": (int) the number of opens,
+                      "unique_opens": (int) the number of unique opens,
+                      "clicks": (int) the number of clicks,
+                      "unique_clicks": (int) the number of unique clicks,
+                      "unsubscribes": (int) the number of unsubscribes,
+                      "bounces": (int) the number of bounces,
+                      "delivered": (int) the number of messages delivered,
+                      "reported_spam": (int) the number of messages reported as spam
+                    }
+                ],
+                "sms" : [
+                  {
+                    "sent": (int) the number of sends,
+                    "sent_to_carrier" : (int) the number of messages sent to the carrier,
+                    "delivered": (int) the number of delivered messages,
+                    "rejected": (int) the number of rejected messages,
+                    "delivery_failed": (int) the number of failed deliveries,
+                    "clicks": (int) the number of clicks on shortened links,
+                    "opt_out" : (int) the number of opt outs,
+                    "help" : (int) the number of help messages received
+                  }
+                ],
+                "whats_app": [
+                    {
+                        "variation_name": (string) the name of the message in the dashboard,
+                        "variation_api_id": (string) the variation API identifier,
+                        "sent": (int) the number of sends, 
+                        "delivered": (int) the number of delivered messages,
+                        "failed": (int) the number of failed deliveries,
+                        "read": (int) the number of opened messages,
+                        "revenue": (float) the number of dollars of revenue (USD),
+                        "unique_recipients": (int) the number of unique recipients,
+                        "conversions": (int) the number of conversions,
+                        "conversions_by_send_time": (int) the number of conversions attributed to the date the campaign was sent,
+                        "conversions1": (optional, int) the number of conversions for the second conversion event,
+                        "conversions1_by_send_time": (optional, int) the number of conversions for the second conversion event attributed to the date the campaign was sent,
+                        "conversions2": (optional, int) the number of conversions for the third conversion event,
+                        "conversions2_by_send_time": (optional, int) the number of conversions for the third conversion event attributed to the date the campaign was sent,
+                        "conversions3": (optional, int) the number of conversions for the fourth conversion event,
+                        "conversions3_by_send_time": (optional, int) the number of conversions for the fourth conversion event attributed to the date the campaign was sent
+                    },
+                    {
+                        "variation_name": (string) the name of the message in the dashboard,
+                        "variation_api_id": (string) the variation API identifier,
+                        "enrolled": (optional, int) the number of enrolled users,
+                        "revenue": (float) the number of dollars of revenue (USD),
+                        "unique_recipients": (int) the number of unique recipients,
+                        "conversions": (int) the number of conversions,
+                        "conversions_by_send_time": (int) the number of conversions attributed to the date the campaign was sent,
+                        "conversions1": (optional, int) the number of conversions for the second conversion event,
+                        "conversions1_by_send_time": (optional, int) the number of conversions for the second conversion event attributed to the date the campaign was sent,
+                        "conversions2": (optional, int) the number of conversions for the third conversion event,
+                        "conversions2_by_send_time": (optional, int) the number of conversions for the third conversion event attributed to the date the campaign was sent,
+                        "conversions3": (optional, int) the number of conversions for the fourth conversion event,
+                        "conversions3_by_send_time": (optional, int) the number of conversions for the fourth conversion event attributed to the date the campaign was sent
+                    }
+                ]
+            },
+            "conversions_by_send_time": (optional, int),
+            "conversions1_by_send_time": (optional, int),
+            "conversions2_by_send_time": (optional, int),
+            "conversions3_by_send_time": (optional, int),
+            "conversions": (optional, int),
+            "conversions1": (optional, int),
+            "conversions2": (optional, int),
+            "conversions3": (optional, int),
+            "unique_recipients": (int),
+            "revenue": (optional, float)
+            }
+         ],
+                "content_cards" : [
+                  { 
+                    "variation_name": (string) the variation name, 
+                    "variation_api_id": (string) the variation API identifier, 
+                    "sent": (int) the number of sends, 
+                    "total_impressions": (int) the number of total impressions, 
+                    "unique_impressions": (int) the number of unique impressions,
+                    "total_clicks": (int) the number of total clicks, 
+                    "unique_clicks": (int) the number of unique clicks, 
+                    "total_dismissals": (int) the number of total dismissals, 
+                    "unique_dismissals": (int) the number of unique dismissals, 
+                    "revenue": (float) the number of dollars of revenue (USD),
+                    "unique_recipients": (int) the number of unique recipients,
+                    "conversions": (int) the number of conversions,
+                    "conversions_by_send_time": (int) the number of conversions attributed to the date the campaign was sent,
+                    "conversions1": (optional, int) the number of conversions for the second conversion event,
+                    "conversions1_by_send_time": (optional, int) the number of conversions for the second conversion event attributed to the date the campaign was sent,
+                    "conversions2": (optional, int) the number of conversions for the third conversion event,
+                    "conversions2_by_send_time": (optional, int) the number of conversions for the third conversion event attributed to the date the campaign was sent,
+                    "conversions3": (optional, int) the number of conversions for the fourth conversion event,
+                    "conversions3_by_send_time": (optional, int) the number of conversions for the fourth conversion event attributed to the date the campaign was sent
+                  }
+                ]
+              },
+           "conversions_by_send_time": (optional, int),
+           "conversions1_by_send_time": (optional, int),
+           "conversions2_by_send_time": (optional, int),
+           "conversions3_by_send_time": (optional, int),
+           "conversions": (int),
+           "conversions1": (optional, int),
+           "conversions2": (optional, int),
+           "conversions3": (optional, int),
+           "unique_recipients": (int),
+           "revenue": (optional, float)
+        },
+        ...
+    ],
+    ...
+}
+```
+
+### Réponse multivariées
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "data" : [
+        {
+            "time" : (string) the date as ISO 8601 date,
+            "conversions" : (int) the number of conversions,
+            "revenue": (float) the number of dollars of revenue (USD),
+            "conversions_by_send_time": (int) the number of conversions attributed to the date the campaign was sent,
+            "messages" : {
+               "trigger_in_app_message": [{
+                    "variation_name": (optional, string) the variation name,
+                    "impressions": (int) the number of impressions,
+                    "clicks": (int) the number of clicks,
+                    "first_button_clicks": (int) the number of first button clicks,
+                    "second_button_clicks": (int) the number of second button clicks,
+                    "revenue": (float) the number of dollars of revenue (USD),
+                    "unique_recipients": (int) the number of unique recipients,
+                    "conversions": (int) the number of conversions,
+                    "conversions_by_send_time": (int) the number of conversions attributed to the date the campaign was sent,
+                    "conversions1": (optional, int) the number of conversions for the second conversion event,
+                    "conversions1_by_send_time": (optional, int) the number of conversions for the second conversion event attributed to the date the campaign was sent,
+                    "conversions2": (optional, int) the number of conversions for the third conversion event,
+                    "conversions2_by_send_time": (optional, int) the number of conversions for the third conversion event attributed to the date the campaign was sent,
+                    "conversions3": (optional, int) the number of conversions for the fourth conversion event,
+                    "conversions3_by_send_time": (optional, int) the number of conversions for the fourth conversion event attributed to the date the campaign was sent
+      			}, {
+      				"variation_name": (optional, string) the variation name,
+      				"impressions": (int) the number of impressions,
+      				"clicks": (int) the number of clicks,
+      				"first_button_clicks": (int) the number of first button clicks,
+      				"second_button_clicks": (int) the number of second button clicks,
+                    "revenue": (float) the number of dollars of revenue (USD),
+                    "unique_recipients": (int) the number of unique recipients,
+                    "conversions": (int) the number of conversions,
+                    "conversions_by_send_time": (int) the number of conversions attributed to the date the campaign was sent,
+                    "conversions1": (optional, int) the number of conversions for the second conversion event,
+                    "conversions1_by_send_time": (optional, int) the number of conversions for the second conversion event attributed to the date the campaign was sent,
+                    "conversions2": (optional, int) the number of conversions for the third conversion event,
+                    "conversions2_by_send_time": (optional, int) the number of conversions for the third conversion event attributed to the date the campaign was sent,
+                    "conversions3": (optional, int) the number of conversions for the fourth conversion event,
+                    "conversions3_by_send_time": (optional, int) the number of conversions for the fourth conversion event attributed to the date the campaign was sent
+      			}, {
+      				"variation_name": (optional, string) the variation name,
+      				"revenue": (float) the number of dollars of revenue (USD),
+      				"unique_recipients": (int) the number of unique recipients,
+      				"conversions": (int) the number of conversions,
+                    "conversions_by_send_time": (int) the number of conversions attributed to the date the campaign was sent,
+                    "conversions1": (optional, int) the number of conversions for the second conversion event,
+                    "conversions1_by_send_time": (optional, int) the number of conversions for the second conversion event attributed to the date the campaign was sent,
+                    "conversions2": (optional, int) the number of conversions for the third conversion event,
+                    "conversions2_by_send_time": (optional, int) the number of conversions for the third conversion event attributed to the date the campaign was sent,
+                    "conversions3": (optional, int) the number of conversions for the fourth conversion event,
+                    "conversions3_by_send_time": (optional, int) the number of conversions for the fourth conversion event attributed to the date the campaign was sent
+      				"enrolled": (optional, int) the number of enrolled users
+      			}]
+      		},
+      		"conversions_by_send_time": (optional, int),
+      		"conversions1_by_send_time": (optional, int),
+      		"conversions2_by_send_time": (optional, int),
+      		"conversions3_by_send_time": (optional, int),
+      		"conversions": (optional, int),
+      		"conversions1": (optional, int),
+      		"conversions2": (optional, int),
+      		"conversions3": (optional, int),
+      		"unique_recipients": (int),
+      		"revenue": (optional, float)
+         }],
+         ...
+}
+```
+
+Les types de messages possibles sont `email`, `in_app_message`, `webhook`, `android_push`, `ios_push`, `kindle_push` et `web_push`. Tous les types de messages des notifications push auront les mêmes statistiques que celles d’`android_push`.
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/campaigns/get_campaign_details.md b/_lang/fr_fr/_api/endpoints/export/campaigns/get_campaign_details.md
new file mode 100644
index 00000000000..8ab18072dce
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/campaigns/get_campaign_details.md
@@ -0,0 +1,289 @@
+---
+nav_title: "GET : Exporter les détails de la campagne"
+article_title: "GET : Exporter les détails de la campagne"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les informations relatives à la campagne."
+
+---
+{% api %}
+# Exporter les informations relatives à la campagne
+{% apimethod get %}
+/campaigns/details
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer des informations pertinentes sur une campagne spécifique, qui peuvent être identifiées par le `campaign_id`. 
+
+Si vous souhaitez récupérer les données du Canvas, reportez-vous au point de terminaison [Exporter les détails du Canvas]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#aad2a811-7237-43b1-9d64-32042eabecd9 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `campaigns.details`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `campaign_id` | Requis | Chaîne de caractères | Voir l'[identifiant API de la campagne.]({{site.baseurl}}/api/identifier_types/)<br><br> Vous trouverez l'adresse `campaign_id` pour les campagnes API sur la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) et sur la page **Détails de la campagne** dans votre tableau de bord ; vous pouvez également utiliser l'[endpoint Exporter la liste des campagnes.](#campaign-list-endpoint) |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande 
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/campaigns/details?campaign_id={{campaign_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponses
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "created_at" : (string) the date created as ISO 8601 date,
+    "updated_at" : (string) the date last updated as ISO 8601 date,
+    "archived": (boolean) whether this campaign is archived,
+    "draft": (boolean) whether this campaign is a draft,
+    "name" : (string) the campaign name,
+    "description" : (string) the campaign description,
+    "schedule_type" : (string) the type of scheduling action,
+    "channels" : (array) the list of channels to send via,
+    "first_sent" : (string) the date and hour of first sent as ISO 8601 date,
+    "last_sent" : (string) the date and hour of last sent as ISO 8601 date,
+    "tags" : (array) the tag names associated with the campaign,
+    "teams" : (array) the names of the Teams associated with the campaign,
+    "messages": {
+        "message_variation_id": (string) { // <=This is the actual id
+            "channel": (string) the channel type of the message, must be either email, ios_push, webhook, content_card, in-app_message, or sms,
+            "name": (string) the name of the message in the dashboard (eg., "Variation 1")
+            ... channel-specific fields for this message, see the following messages section ...
+        }
+    },
+    "conversion_behaviors": (array) the conversion event behaviors assigned to the campaign, see the following conversions behavior section.
+}
+```
+
+### Messages par canal
+
+La réponse `messages` contiendra des informations sur chaque message. Voici des exemples de réponses de message pour chaque canal :
+
+#### Notification push
+
+```json
+{
+    "channel": (string) the description of the channel, such as "ios_push" or "android_push"
+    "alert": (string) the alert body text,
+    "extras": (hash) any key-value pairs provided
+}
+```
+
+#### E-mail
+
+```json
+{
+    "channel": "email",
+    "name": (string) the name of the variant,
+    "extras": (array) the email extras,
+    "subject": (string) the subject,
+    "body": (string) the HTML body,
+    "from": (string) the from address and display name,
+    "reply_to": (string) the reply-to for message, if different than "from" address,
+    "title": (string) the name of the email,
+    "amp_body": (string) the AMP HTML body,
+    "preheader": (string) the preheader,
+    "custom_plain_text": (string) the custom plain text,
+    "should_inline_css": (boolean) whether there should be inline CSS,
+    "should_whitespace_header": (boolean) whether there should be a whitespace header,
+    "email_headers": (array) list of email headers
+}
+```
+
+#### in-app Messages
+
+```json
+{
+    "type": (string) the description of in-app message type, such as "survey",
+    "data": {
+        "pages": [
+            {
+                "header": 
+                    {
+                         "text":(string) the display text for the header of the survey,
+                    }
+                "choices": [
+                    {
+                       "choice_id": (string) the choice identifier,
+                       "text": (string) the display text, 
+                       "custom_attribute_key": (string) the custom attribute key, 
+                       "custom_attribute_value": (sting) the custom attribute value,
+                       "deleted": (boolean) deleted from live campaign, 
+                    },
+                    ...
+                ]
+            }
+        ]
+    }
+}
+```
+
+#### Cartes de contenu
+
+```json
+{
+    "channel": "content_cards",
+    "name": (string) the name of variant,
+    "extras": (hash) any key-value pairs provided; only present if at least one key-value pair has been set
+}
+```
+
+#### Webhook
+
+```json
+{
+    "channel": "webhook",
+    "url": (string) the URL for webhook,
+    "body": (string) the payload body,
+    "type": (string) the body content type,
+    "headers": (hash) the specified request headers,
+    "method": (string) the HTTP method, either POST or GET
+}
+```
+
+#### SMS
+
+```json
+{
+  "channel": "sms",
+  "body": (string) the payload body,
+  "from": (string) the list of numbers associated with the subscription group,
+  "subscription_group_id": (string) the API id of the subscription group targeted in the SMS message
+}
+```
+
+#### WhatsApp
+
+##### Messages types
+
+```json
+{
+  "channel": "whats_app",
+  "subscription_group_id": (string) the API ID of the subscription group selected in the WhatsApp message
+  "from": (array) the list of strings of the numbers associated with the subscription group,
+  "template_name": (string) the name of the WhatsApp template being sent,
+  "template_language_code": (string) the language code of the WhatsApp template being sent,
+  "header_variables": (array) the list of strings, if present, of Liquid variables being inserted into header of WhatsApp template being sent,
+  "body_variables": (array) the list of strings, if present, of Liquid variables being inserted into body of WhatsApp template being sent,
+  "button_variables": (array) the list of strings, if present, of Liquid variables being inserted into buttons of WhatsApp template being sent
+}
+```
+
+##### Messages d'envoi de messages
+
+```json
+{
+  "channel": "whats_app",
+  "subscription_group_id": (string) the API ID of the subscription group selected in the WhatsApp message,
+  "from": (array) list of strings of the numbers associated with the subscription group,
+  "layout": (string) the name of the WhatsApp template being sent (text or media or quick-reply),
+  "header_text": (string, optional) the text, if present, of the header of the message being sent,
+  "body_text": (string, optional) the text, if present, of the body of the message being sent,
+  "footer_text": (string, optional) the text, if present, of the footer of the message being sent,
+  "buttons": (array) list of button objects in the message being sent ({"text": (string) the text of the button})
+}
+```
+
+#### Messages de contrôle
+
+```json
+{
+    "channel": (string) the description of the channel that the control is for,
+    "type": "control"
+}
+```
+
+### Comportements de conversion
+
+Le tableau `conversion_behaviors` contiendra des informations sur chaque comportement relatif aux événements de conversion défini pour la campagne. Ces comportements sont dans l’ordre défini par la campagne. Par exemple, l’événement de conversion A sera le premier élément du tableau, l’événement de conversion B sera le deuxième, etc. Les listes suivantes présentent des exemples de comportement relatif aux événements de conversion :
+
+#### Clique sur l’e-mail
+
+```json
+{
+    "type": "Clicks Email",
+    "window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours
+}
+```
+
+#### Ouvre l’e-mail
+
+```json
+{
+    "type": "Opens Email",
+    "window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours
+}
+```
+
+#### Achète (tout achat)
+
+```json
+{
+    "type": "Makes Any Purchase",
+    "window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours
+}
+```
+
+#### Achète (produit spécifique)
+
+```json
+{
+    "type": "Makes Specific Purchase",
+    "window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours,
+    "product": (string) the name of the product, such as "Feline Body Armor"
+}
+```
+
+#### Effectue un événement personnalisé
+
+```json
+{
+    "type": "Performs Custom Event",
+    "window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours,
+    "custom_event_name": (string) the name of the event, such as "Used Feline Body Armor"
+}
+```
+
+#### Met à niveau l’application
+
+```json
+{
+    "type": "Upgrades App",
+    "window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours,
+    "app_ids": (array or null) array of app ids, such as ["12345", "67890"], or `null` if "Track sessions for any app" is selected in the UI
+}
+```
+
+#### Utilise l’application
+
+```json
+{
+    "type": "Starts Session",
+    "window": (integer) the number of seconds during which the user can convert on this event, such as 86400, which is 24 hours,
+    "app_ids": (array or null) array of app ids, such as ["12345", "67890"], or `null` if "Track sessions for any app" is selected in the UI
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/campaigns/get_campaigns.md b/_lang/fr_fr/_api/endpoints/export/campaigns/get_campaigns.md
new file mode 100644
index 00000000000..f85e5293f3c
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/campaigns/get_campaigns.md
@@ -0,0 +1,72 @@
+---
+nav_title: "GET : Exporter la liste des campagnes"
+article_title: "GET : Exporter la liste des campagnes"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter la liste des campagnes."
+
+---
+{% api %}
+# Exporter la liste des campagnes
+{% apimethod get %}
+/campaigns/list
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter une liste de campagnes, chacune incluant son nom, l’identifiant API de la campagne, s’il s’agit d’une campagne par API, et les balises associées à la campagne. 
+
+Les campagnes sont renvoyées par groupes de 100 triés par date de création (des plus anciens aux plus récents par défaut).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#f3b0b3ef-04fb-4a31-8570-e6ad88dacb18 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `campaigns.list`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `page` | Facultatif | Entier | La page des campagnes à renvoyer, par défaut sur 0 (renvoie le premier ensemble jusqu’à 100 éléments). |
+| `include_archived` | Facultatif | Valeur booléenne | S’il faut inclure ou non des campagnes archivées, par défaut sur Faux. |
+| `sort_direction` | Facultatif | Chaîne de caractères | \- Trier l’heure de création de la plus récente à la plus ancienne : indiquer la valeur `desc`.<br> \- Trier l’heure de création de la plus ancienne à la plus récente : indiquer la valeur `asc`. <br><br>Si `sort_direction` n’est pas inclus, l’ordre par défaut est de la plus ancienne à la plus récente. |
+| `last_edit.time[gt]` | Facultatif | Date | Filtre les résultats et renvoie uniquement les campagnes qui ont été modifiées au-delà de l’heure indiquée jusqu’à maintenant. Le format est `yyyy-MM-DDTHH:mm:ss`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+ 
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/campaigns/list?page=0&include_archived=false&sort_direction=desc&last_edit.time[gt]=2020-06-28T23:59:59-5:00' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "campaigns" : [
+        {
+            "id" : (string) the Campaign API identifier,
+            "last_edited": (ISO 8601 string) the last edited time for the message 
+            "name" : (string) the campaign name,
+            "is_api_campaign" : (boolean) whether the campaign is an API campaign,
+            "tags" : (array) the tag names associated with the campaign formatted as strings
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/campaigns/get_send_analytics.md b/_lang/fr_fr/_api/endpoints/export/campaigns/get_send_analytics.md
new file mode 100644
index 00000000000..9774109e884
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/campaigns/get_send_analytics.md
@@ -0,0 +1,105 @@
+---
+nav_title: "GET : Export Send Analytics (si utilisé comme adjectif)"
+article_title: "GET : Export Send Analytics (si utilisé comme adjectif)"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter l’analyse d’envoi."
+
+---
+{% api %}
+# Exporter l’analyse d’envoi
+{% apimethod get %}
+/sends/data_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer une série quotidienne de diverses statistiques pour un `send_id` suivi pour les campagnes API.
+
+Braze stocke les envois d’analyse pendant 14 jours après l’envoi. Les conversions de la campagne seront attribuées à la dernière adresse `send_id` qu'un utilisateur donné a reçue dans le cadre de la campagne.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#76f822a8-a13b-4bfb-b20e-72b5013dfe86 {% endapiref %}
+
+## Conditions préalables
+
+Cet endpoint est réservé aux campagnes API. Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `sends.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- |------------ |
+| `campaign_id` | Requis | Chaîne de caractères | Voir l'[identifiant API de la campagne.]({{site.baseurl}}/api/identifier_types/) |
+| `send_id` | Requis | Chaîne de caractères | Voir l'[identifiant de l'API d'envoi.]({{site.baseurl}}/api/identifier_types/) |
+| `length` | Requis | Entier | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `ending_at` | Facultatif | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande 
+
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/sends/data_series?campaign_id={{campaign_identifier}}&send_id={{send_identifier}}&length=30&ending_at=2014-12-10T23:59:59-05:00' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time": (string) the date as ISO 8601 date,
+            "messages": {
+                "ios_push" : [
+                    {
+                      "variation_name": (string) variation name,
+                      "sent": (int) the number of sends,
+                      "delivered": (int) the number of messages successfully delivered,
+                      "undelivered": (int) the number of undelivered,
+                      "delivery_failed": (int) the number of rejected,
+                      "direct_opens": (int) the number of direct opens,
+                      "total_opens": (int) the number of total opens,
+                      "bounces": (int) the number of bounces,
+                      "body_clicks": (int) the number of body clicks,
+                      "revenue": (float) the number of dollars of revenue (USD),
+                      "unique_recipients": (int) the number of unique recipients at the campaign-level,
+                      "conversions": (int) the number of conversions,
+                      "conversions_by_send_time": (int) the number of conversions attributed to the date the campaign was sent,
+                      "conversions1": (optional, int) the number of conversions for the second conversion event,
+                      "conversions1_by_send_time": (optional, int) the number of conversions for the second conversion event attributed to the date the campaign was sent,
+                      "conversions2": (optional, int) the number of conversions for the third conversion event,
+                      "conversions2_by_send_time": (optional, int) the number of conversions for the third conversion event attributed to the date the campaign was sent,
+                      "conversions3": (optional, int) the number of conversions for the fourth conversion event,
+                      "conversions3_by_send_time": (optional, int) the number of conversions for the fourth, conversion event attributed to the date the campaign was sent
+                      }
+                  ]
+            },
+        "conversions_by_send_time": (optional, int),
+        "conversions1_by_send_time": (optional, int),
+        "conversions2_by_send_time": (optional, int),
+        "conversions3_by_send_time": (optional, int),
+        "conversions": (int),
+        "conversions1": (optional, int),
+        "conversions2": (optional, int),
+        "conversions3": (optional, int),
+        "unique_recipients": (int),
+        "revenue": (optional, float)
+      }
+    ],
+  "message": "success"
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/canvas.md b/_lang/fr_fr/_api/endpoints/export/canvas.md
new file mode 100644
index 00000000000..eb4c2707766
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/canvas.md
@@ -0,0 +1,6 @@
+---
+nav_title: Canvas
+config_only: true
+noindex: true
+page_order: 2
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/canvas/get_canvas_analytics.md b/_lang/fr_fr/_api/endpoints/export/canvas/get_canvas_analytics.md
new file mode 100644
index 00000000000..4c830990a12
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/canvas/get_canvas_analytics.md
@@ -0,0 +1,123 @@
+---
+nav_title: "GET : Exportation de la série de données Canvas Analytics (si utilisée en tant qu'adjectif)"
+article_title: "GET : Exportation de la série de données Canvas Analytics (si utilisée en tant qu'adjectif)"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter l’analyse des séries de données de Canvas."
+
+---
+{% api %}
+# Exporter l’analyse des séries de données de Canvas
+{% apimethod get %}
+/canvas/data_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter des données de série temporelles pour un Canvas.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#0fd61e93-7edf-4d87-a8dc-052420aefb73 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `canvas_id` | Requis | Chaîne de caractères | Voir l'[identifiant de l'API Canvas]({{site.baseurl}}/api/identifier_types/). |
+| `ending_at` | Requis | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle l’exportation de données doit se terminer. Par défaut, l’heure de la demande. |
+| `starting_at` | En option* | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle l’exportation de données doit commencer. <br><br>\* L'adresse `length` ou `starting_at` est requise. |
+| `length` | En option* | Chaîne de caractères | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 14 (inclus). <br><br>\* L'adresse `length` ou `starting_at` est requise. |
+| `include_variant_breakdown` | Facultatif | Valeur booléenne | S’il faut inclure ou non des statistiques de variante (par défaut sur `false`).  |
+| `include_step_breakdown` | Facultatif | Valeur booléenne | S’il faut inclure ou non des statistiques d’étape (par défaut sur `false`). |
+| `include_deleted_step_data` | Facultatif | Valeur booléenne | S’il faut inclure ou non des statistiques d’étape pour les étapes supprimées (par défaut sur `false`). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/canvas/data_series?canvas_id={{canvas_id}}&ending_at=2018-05-30T23:59:59-5:00&starting_at=2018-05-28T23:59:59-5:00&include_variant_breakdown=true&include_step_breakdown=true&include_deleted_step_data=true' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "data": {
+    "name": (string) the Canvas name,
+    "stats": [
+      {
+        "time": (string) the date as ISO 8601 date,
+        "total_stats": {
+          "revenue": (float) the number of dollars of revenue (USD),
+          "conversions": (int) the number of conversions,
+          "conversions_by_entry_time": (int) the number of conversions for the conversion event by entry time,
+          "entries": (int) the number of entries
+        },
+        "variant_stats": (optional) {
+          "00000000-0000-0000-0000-0000000000000": (string) the API identifier for the variant {
+            "name": (string) the name of variant,
+            "revenue": (float) the number of dollars of revenue (USD),
+            "conversions": (int) the number of conversions,
+            "conversions_by_entry_time": (int) the number of conversions for the conversion event by entry time,
+            "entries": (int) the number of entries
+          },
+          ... (more variants)
+        },
+        "step_stats": (optional) {
+          "00000000-0000-0000-0000-0000000000000": (string) the API identifier for the step {
+            "name": (string) the name of step,
+            "revenue": (float) the the number of dollars of revenue (USD),
+            "conversions": (int) the the number of conversions,
+            "conversions_by_entry_time": (int) the number of conversions for the conversion event by entry time,
+            "messages": {
+              "email": [
+                {
+                  "sent": (int) the number of sends,
+                  "opens": (int) the number of opens,
+                  "unique_opens": (int) the number of unique opens,
+                  "clicks": (int) the number of clicks
+                  ... (more stats)
+                }
+              ],
+              "sms" : [
+                {
+                  "sent": (int) the number of sends,
+                  "sent_to_carrier" : (int) the number of messages sent to the carrier,
+                  "delivered": (int)the number of delivered messages,
+                  "rejected": (int) the number of rejected messages,
+                  "delivery_failed": (int) the number of failed deliveries,
+                  "clicks": (int) the number of clicks on shortened links,
+                  "opt_out" : (int) the number of opt outs,
+                  "help" : (int) the number of help messages received
+                }
+              ],
+              ... (more channels)
+            }
+          },
+          ... (more steps)
+        }
+      },
+      ... (more stats by time)
+    ]
+  },
+  "message": (required, string) the status of the export, returns 'success' when completed without errors
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/canvas/get_canvas_analytics_summary.md b/_lang/fr_fr/_api/endpoints/export/canvas/get_canvas_analytics_summary.md
new file mode 100644
index 00000000000..cfdd3cd777f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/canvas/get_canvas_analytics_summary.md
@@ -0,0 +1,103 @@
+---
+nav_title: "GET : Exporter les données du canvas Résumé des analyses"
+article_title: "GET : Exporter les données du canvas Résumé des analyses"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter le résumé analyse des données de Canvas."
+
+---
+{% api %}
+# Exporter le résumé analyse des données de Canvas
+{% apimethod get %}
+/toile/résumé_des_données
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter des cumuls de données de série temporelles pour un Canvas, fournissant ainsi un résumé concis des résultats de Canvas.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#1eb1b760-6b00-4c03-bcfb-12646f2ba6da {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.data_summary`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `canvas_id` | Requis | Chaîne de caractères | Voir [identifiant de l'API Canvas]({{site.baseurl}}/api/identifier_types/). |
+| `ending_at` | Requis | DateTime <br>(string [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)) | Date à laquelle l’exportation de données doit se terminer. Par défaut, l’heure de la demande. |
+| `starting_at` | Optionnel* | DateTime <br>(string [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)) | Date à laquelle l’exportation de données doit commencer. <br><br>Soit `length` ou `starting_at` est requis. |
+| `length` | Optionnel* | Chaîne de caractères | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 14 (inclus). <br><br>Soit `length` ou `starting_at` est requis. |
+| `include_variant_breakdown` | Facultatif | Valeur booléenne | S’il faut inclure ou non des statistiques de variante (par défaut sur `false`).  |
+| `include_step_breakdown` | Facultatif | Valeur booléenne | S’il faut inclure ou non des statistiques d’étape (par défaut sur `false`). |
+| `include_deleted_step_data` | Facultatif | Valeur booléenne | S’il faut inclure ou non des statistiques d’étape pour les étapes supprimées (par défaut sur `false`). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/canvas/data_summary?canvas_id={{canvas_id}}&ending_at=2018-05-30T23:59:59-5:00&starting_at=2018-05-28T23:59:59-5:00&length=5&include_variant_breakdown=true&include_step_breakdown=true&include_deleted_step_data=true' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "data": {
+    "name": (string) the Canvas name,
+    "total_stats": {
+      "revenue": (float) the number of dollars of revenue (USD),
+      "conversions": (int) the number of conversions,
+      "conversions_by_entry_time": (int) the number of conversions for the conversion event by entry time,
+      "entries": (int) the number of entries
+    },
+    "variant_stats": (optional) {
+      "00000000-0000-0000-0000-0000000000000": (string) the API identifier for the variant {
+        "name": (string) the name of variant,
+        "revenue": (float) the number of dollars of revenue (USD),
+        "conversions": (int) the number of conversions,
+        "entries": (int) the number of entries
+      },
+      ... (more variants)
+    },
+    "step_stats": (optional) {
+      "00000000-0000-0000-0000-0000000000000": (string) the API identifier for the step {
+        "name": (string) the name of step,
+        "revenue": (float) the number of dollars of revenue (USD),
+        "conversions": (int) the number of conversions,
+        "conversions_by_entry_time": (int) the number of conversions for the conversion event by entry time,
+        "messages": {
+          "android_push": (name of channel) [
+            {
+              "sent": (int) the number of sends,
+              "opens": (int) the number of opens,
+              "influenced_opens": (int) the number of influenced opens,
+              "bounces": (int) the number of bounces
+              ... (more stats for channel)
+            }
+          ],
+          ... (more channels)
+        }
+      },
+      ... (more steps)
+    }
+  },
+  "message": (required, string) the status of the export, returns 'success' when completed without errors
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/canvas/get_canvas_details.md b/_lang/fr_fr/_api/endpoints/export/canvas/get_canvas_details.md
new file mode 100644
index 00000000000..db668a75eac
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/canvas/get_canvas_details.md
@@ -0,0 +1,227 @@
+---
+nav_title: "GET : Exporter les détails de la toile"
+article_title: "GET : Exporter les détails de la toile"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze les détails du Canvas."
+
+---
+{% api %}
+# Exporter les détails du Canvas
+{% apimethod get %}
+/canvas/details
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter des métadonnées sur un Canvas, telles que le nom, l’heure de création, l’état actuel, etc.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#5188873c-13a3-4aaf-a54b-9fa1daeac5f8 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.details`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `canvas_id` | Requis | Chaîne de caractères | Voir [Identifiant de l'API Canvas]({{site.baseurl}}/api/identifier_types/) |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/canvas/details?canvas_id={{canvas_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponses
+
+{% alert note %}
+Toutes les étapes Canvas ont un champ `next_paths` qui est un tableau de données `{name, next_step_id}`. Pour les étapes complètes et les étapes de message, le champ `next_step_ids` sera présent mais ne contiendra pas de données pour les autres étapes de Canvas Flow.
+{% endalert %}
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "created_at": (string) the date created as ISO 8601 date,
+  "updated_at": (string) the date updated as ISO 8601 date,
+  "name": (string) the Canvas name,
+  "description": (string) the Canvas description,
+  "archived": (boolean) whether this Canvas is archived,
+  "draft": (boolean) whether this Canvas is a draft,
+  "schedule_type": (string) the type of scheduling action,
+  "first_entry": (string) the date of first entry as ISO 8601 date,
+  "last_entry": (string) the date of last entry as ISO 8601 date,
+  "channels": (array of strings) step channels used with Canvas,
+  "variants": [
+    {
+      "name": (string) the name of variant,
+      "id": (string) the API identifier of the variant,
+      "first_step_ids": (array of strings) the API identifiers for first steps in variant,
+      "first_step_id": (string) the API identifier of first step in variant (deprecated in November 2017, only included if the variant has only one first step)
+    },
+    ... (more variations)
+  ],
+  "tags": (array of strings) the tag names associated with the Canvas,
+  "teams" : (array) the names of the Teams associated with the Canvas,
+  "steps": [
+    {
+      "name": (string) the name of step,
+      "type" (string) the type of Canvas component,
+      "id": (string) the API identifier of the step,
+      "next_step_ids": (array of strings) IDs for next steps that are full steps or Message steps,
+      "next_paths": { (array of objects)
+      // for Decision Splits, this property should evaluate to "Yes" or "No"
+      // for Audience Path and Action Paths, this property should evaluate to the group name
+      // for Experiment Paths, this property should evaluate to the path name
+      // for other steps, this property should evaluate to "null"
+        "name": (string) name the name of step,
+        "next_step_id": (string) IDs for next steps that are full steps or Message steps,
+        }
+      "channels": (array of strings) the channels used in step,
+      "messages": {
+          "message_variation_id": (string) {  // <=This is the actual id
+              "channel": (string) the channel type of the message (for example, "email"),
+              // channel-specific fields for this message, see Campaign Details endpoint API Response for example message responses
+          }
+      }
+    },
+    ... (more steps)
+  ],
+  "message": (required, string) the status of the export, returns 'success' when completed without errors
+}
+```
+
+### Messages par canal
+
+Voici un exemple de réponse qui inclut les messages Canvas envoyés par différents canaux (e-mail, push, SMS et messages in-app) :
+
+```json
+{
+  "message": "success",
+  "created_at": "2023-01-01T12:00:00Z",
+  "updated_at": "2023-01-10T12:00:00Z",
+  "name": "Multi-Channel Engagement",
+  "description": "Complete profile reminder via multiple channels",
+  "archived": false,
+  "draft": false,
+  "schedule_type": "date",
+  "first_entry": "2023-01-01T12:00:00Z",
+  "last_entry": "2023-01-10T12:00:00Z",
+  "channels": ["email", "push", "sms", "in_app_message"],
+  "variants": [
+    {
+      "name": "Variant 1",
+      "id": "variant_1_id",
+      "first_step_ids": ["step_1"]
+    }
+  ],
+  "tags": ["engagement", "multi-channel"],
+  "teams": ["Marketing Team"],
+  "steps": [
+    {
+      "name": "Welcome Email",
+      "type": "email",
+      "id": "step_1",
+      "next_step_ids": ["step_2"],
+      "next_paths": [
+        {
+          "name": "Next Step",
+          "next_step_id": "step_2"
+        }
+      ],
+      "channels": ["email"],
+      "messages": {
+        "message_1": {
+          "channel": "email",
+          "subject": "Welcome to Kitchenerie!",
+          "body": "<html><body>Welcome to the Kitchenerie family, {{first_name}}!</body></html>",
+          "created_at": "2023-01-01T12:00:00Z",
+          "updated_at": "2023-01-01T12:00:00Z"
+        }
+      }
+    },
+    {
+      "name": "Follow-Up Push Notification",
+      "type": "push",
+      "id": "step_2",
+      "next_step_ids": ["step_3"],
+      "next_paths": [
+        {
+          "name": "Next Step",
+          "next_step_id": "step_3"
+        }
+      ],
+      "channels": ["push"],
+      "messages": {
+        "message_2": {
+          "channel": "push",
+          "title": "Don't Forget to Complete Your Kitchenerie Profile",
+          "body": "Complete your Kitchenerie profile for access to special offers and local events.",
+          "created_at": "2023-01-02T12:00:00Z",
+          "updated_at": "2023-01-02T12:00:00Z"
+        }
+      }
+    },
+    {
+      "name": "Reminder SMS",
+      "type": "sms",
+      "id": "step_3",
+      "next_step_ids": ["step_4"],
+      "next_paths": [
+        {
+          "name": "Next Step",
+          "next_step_id": "step_4"
+        }
+      ],
+      "channels": ["sms"],
+      "messages": {
+        "message_3": {
+          "channel": "sms",
+          "body": "Hi {{first_name}}, remember to complete Kitchenerie your profile!",
+          "created_at": "2023-01-03T12:00:00Z",
+          "updated_at": "2023-01-03T12:00:00Z"
+        }
+      }
+    },
+    {
+      "name": "In-App Message",
+      "type": "in_app_message",
+      "id": "step_4",
+      "next_step_ids": [],
+      "next_paths": [],
+      "channels": ["in_app_message"],
+      "messages": {
+        "message_4": {
+          "channel": "in_app_message",
+          "header": "Complete Your Kitchenerie Profile",
+          "body": "Complete your Kitchenerie profile to unlock access to savings and local events!",
+          "created_at": "2023-01-04T12:00:00Z",
+          "updated_at": "2023-01-04T12:00:00Z"
+        }
+      }
+    }
+  ],
+  "entry_criteria": {
+    "segment_id": "new_users_segment"
+  },
+  "exit_criteria": {
+    "event_name": "completed_profile"
+  }
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/canvas/get_canvases.md b/_lang/fr_fr/_api/endpoints/export/canvas/get_canvases.md
new file mode 100644
index 00000000000..28a19026ab7
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/canvas/get_canvases.md
@@ -0,0 +1,73 @@
+---
+nav_title: "GET : Exporter la liste des toiles"
+article_title: "GET : Exporter la liste des toiles"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter la liste des Canvas."
+
+---
+{% api %}
+# Exporter la liste des Canvas
+{% apimethod get %}
+/canvas/list
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter une liste de Canvas, y compris le nom, l’identifiant de l’API Canvas et les balises associées. 
+
+Les Canvas sont renvoyés par groupes de 100 triés par date de création (des plus anciens aux plus récents par défaut).
+
+Les Canvas archivés ne seront pas inclus dans la réponse API, sauf si le champ `include_archived` est spécifié. En revanche, les Canvas arrêtés, mais non archivés seront renvoyés par défaut.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#e6c150d7-fceb-4b10-91e2-a9ca4d5806d1 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.list`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `page` | Facultatif | Entier | La page des Canvas à renvoyer, par défaut sur `0` (renvoie le premier ensemble jusqu’à 100 éléments) |
+| `include_archived` | Facultatif | Valeur booléenne | S’il faut inclure ou non des Canvas archivés, par défaut sur `false`. |
+| `sort_direction` | Facultatif | Chaîne de caractères | \- Trier l’heure de création de la plus récente à la plus ancienne : indiquer la valeur `desc`.<br> \- Trier l’heure de création de la plus ancienne à la plus récente : indiquer la valeur `asc`. <br><br>Si `sort_direction` n’est pas inclus, l’ordre par défaut est de la plus ancienne à la plus récente. |
+| `last_edit.time[gt]` | Facultatif | Date | Filtre les résultats et renvoie uniquement les Canvas qui ont été modifiés au-delà de l’heure indiquée jusqu’à maintenant. Le format est `yyyy-MM-DDTHH:mm:ss`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/canvas/list?page=1&include_archived=false&sort_direction=desc&last_edit.time[gt]=2020-06-28T23:59:59-5:00' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "canvases" : [
+  	{
+  		"id" : (string) the Canvas API identifier,
+  		"last_edited": (ISO 8601 string) the last edited time for the message,
+  		"name" : (string) the Canvas name,
+  		"tags" : (array) the tag names associated with the Canvas formatted as strings,
+  	},
+    ... (more Canvases)
+  ],
+  "message": (required, string) the status of the export, returns 'success' when completed without errors
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/custom_attributes.md b/_lang/fr_fr/_api/endpoints/export/custom_attributes.md
new file mode 100644
index 00000000000..2e02a0ab370
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/custom_attributes.md
@@ -0,0 +1,6 @@
+---
+nav_title: Attributs personnalisés
+config_only: true
+noindex: true
+page_order: 10
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/custom_attributes/get_custom_attributes.md b/_lang/fr_fr/_api/endpoints/export/custom_attributes/get_custom_attributes.md
new file mode 100644
index 00000000000..91ecada7db8
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/custom_attributes/get_custom_attributes.md
@@ -0,0 +1,83 @@
+---
+nav_title: "GET : Exporter des attributs personnalisés"
+article_title: "GET : Exporter des attributs personnalisés"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente les détails du point de terminaison Exportation d'attributs personnalisés de Braze."
+
+---
+{% api %}
+# Exporter des attributs personnalisés
+{% apimethod get %}
+/custom_attributes
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter une liste d'attributs personnalisés enregistrés pour votre appli. Les attributs sont renvoyés par groupes de 50, triés par ordre alphabétique.
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `custom_attributes.get`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='custom_attributes' %}
+
+## Paramètres de recherche
+
+Notez que chaque appel à cet endpoint renverra 50 attributs. Pour plus de 50 attributs, utilisez l'en-tête `Link` pour récupérer les données sur la page suivante, comme le montre l'exemple de réponse suivant.
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `cursor` | Facultatif | Chaîne de caractères | Détermine la pagination des attributs personnalisés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de requêtes
+
+### Sans curseur
+
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/custom_attributes' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+### Avec curseur
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/custom_attributes?cursor=c2tpcDow' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "attributes" : [
+        {
+            "array_length": 100, (number) the maximum array length, or null if not applicable,
+            "data_type": "Number", (string) the data type,
+            "description": "The attribute description", (string) the attribute description,
+            "name": "The attribute name", (string) the attribute name,
+            "status": "Active", (string) the attribute status,
+            "tag_names": ["Tag One", "Tag Two"] (array) the tag names associated with the attribute formatted as strings,
+        },
+        ...
+    ]
+}
+```
+
+### Codes de réponse des erreurs fatales {#fatal-export}
+
+Pour connaître les codes d'état et les messages d'erreur associés qui seront renvoyés si votre requête rencontre une erreur fatale, reportez-vous à la section [Erreurs fatales.]({{site.baseurl}}/api/errors/#fatal-errors)
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/custom_events.md b/_lang/fr_fr/_api/endpoints/export/custom_events.md
new file mode 100644
index 00000000000..9ad34debd71
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/custom_events.md
@@ -0,0 +1,6 @@
+---
+nav_title: Événements personnalisés
+config_only: true
+noindex: true
+page_order: 3
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/custom_events/get_custom_events.md b/_lang/fr_fr/_api/endpoints/export/custom_events/get_custom_events.md
new file mode 100644
index 00000000000..fc6d77fca28
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/custom_events/get_custom_events.md
@@ -0,0 +1,66 @@
+---
+nav_title: "GET : Exporter la liste des événements personnalisés"
+article_title: "GET : Exporter la liste des événements personnalisés"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter la liste des événements personnalisés."
+
+---
+{% api %}
+# Exporter la liste des événements personnalisés
+{% apimethod get %}
+/events/list
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter une liste d’événements personnalisés qui ont été enregistrés pour votre application. Les noms des événements sont renvoyés par groupes de 250, triés par ordre alphabétique.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#93ecd8a5-305d-4b72-ae33-2d74983255c1 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `events.list`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='events list' %}
+
+## Paramètres de demande
+
+| Paramètre| Requis | Type de données | Description |
+| -------- | -------- | --------- | ----------- |
+| `page` | Facultatif | Entier | La page des noms d’événement à renvoyer, par défaut sur 0 (renvoie le premier ensemble jusqu’à 250 éléments). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/events/list?page=3' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "events" : [
+        "Event A", (string) the event name,
+        "Event B", (string) the event name,
+        "Event C", (string) the event name,
+        ...
+    ]
+}
+```
+
+### Codes de réponse des erreurs fatales {#fatal-export}
+
+Pour les codes d'état et les messages d'erreur associés qui seront renvoyés si votre demande rencontre une erreur fatale, consultez [Erreurs fatales et réponses]({{site.baseurl}}/api/errors/#fatal-errors).
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/custom_events/get_custom_events_analytics.md b/_lang/fr_fr/_api/endpoints/export/custom_events/get_custom_events_analytics.md
new file mode 100644
index 00000000000..71ba36e3f61
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/custom_events/get_custom_events_analytics.md
@@ -0,0 +1,75 @@
+---
+nav_title: "GET : Exportation d'analyses d'événements personnalisés (si utilisés comme adjectifs)"
+article_title: "GET : Exportation d'analyses/analytiques d'événements personnalisés (si utilisés)"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter l’analyse d’événements personnalisés."
+
+---
+{% api %}
+# Exporter l’analyse d’événements personnalisés
+{% apimethod get %}
+/events/data_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer une série du nombre d’occurrences d’un événement personnalisé dans votre application sur une période donnée.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#0bd1ab63-d1a5-4301-8d17-246cf24a178c {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `events.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre| Requis | Type de données | Description |
+| -------- | -------- | --------- | ----------- |
+| `event` | Requis | Chaîne de caractères | Le nom de l’événement personnalisé pour lequel renvoyer l’analyse. |
+| `length` | Requis | Entier | Nombre maximum d’unités (jours ou heures) avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `unit` | Facultatif | Chaîne de caractères | Unité de temps entre les points de données. Peut être `day` ou `hour`, valeur par défaut `day`.  |
+| `ending_at` | Facultatif | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+| `app_id` | Facultatif | Chaîne de caractères | Identifiant de l'API de l'application récupéré à partir de la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) pour limiter l'analyse/analytique à une application spécifique. |
+| `segment_id` | Facultatif | Chaîne de caractères | Voir l'[identifiant API du segment.]({{site.baseurl}}/api/identifier_types/) ID de segment indiquant le segment à analyser pour lequel l’analyse d’événement doit être renvoyée. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/events/data_series?event=event_name&length=24&unit=hour&ending_at=2014-12-10T23:59:59-05:00&app_id={{app_identifier}}&segment_id={{segment_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %} 
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time" : (string) the point in time - as ISO 8601 extended when unit is "hour" and as ISO 8601 date when unit is "day",
+            "count" : (int) the number of occurrences of provided custom event
+        },
+        ...
+    ]
+}
+```
+
+### Codes de réponse des erreurs fatales {#fatal-export}
+
+Pour connaître les codes d'état et les messages d'erreur associés qui seront renvoyés si votre demande rencontre une erreur fatale, reportez-vous à la section [Erreurs fatales et réponses.]({{site.baseurl}}/api/errors/#fatal-errors)
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/custom_events/get_custom_events_data.md b/_lang/fr_fr/_api/endpoints/export/custom_events/get_custom_events_data.md
new file mode 100644
index 00000000000..31a72eeee3d
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/custom_events/get_custom_events_data.md
@@ -0,0 +1,82 @@
+---
+nav_title: "GET : Exportation d'événements personnalisés"
+article_title: "GET : Exportation d'événements personnalisés"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente les détails du point de terminaison Exportation d'événements personnalisés Braze."
+
+---
+{% api %}
+# Exporter des événements personnalisés
+{% apimethod get %}
+/événements
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter une liste d'événements personnalisés enregistrés pour votre appli. Les événements sont renvoyés par groupes de 50, triés par ordre alphabétique.
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `events.get`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='events' %}
+
+## Paramètres de recherche
+
+Notez que chaque appel à cet endpoint renverra 50 événements. Pour plus de 50 événements, utilisez l'en-tête `Link` pour récupérer les données sur la page suivante, comme le montre l'exemple de réponse suivant.
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `cursor` | Facultatif | Chaîne de caractères | Détermine la pagination des événements personnalisés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de requêtes
+
+### Sans curseur
+
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/events' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+### Avec curseur
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/events?cursor=c2tpcDow' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "events" : [
+        {
+            "name": "The event name", (string) the event name,
+            "description": "The event description", (string) the event description,
+            "included_in_analytics_report": false, (boolean) the analytics report inclusion,
+            "status": "Active", (string) the event status,
+            "tag_names": ["Tag One", "Tag Two"] (array) the tag names associated with the event formatted as strings,
+        },
+        ...
+    ]
+}
+```
+
+### Codes de réponse des erreurs fatales {#fatal-export}
+
+Pour connaître les codes d'état et les messages d'erreur associés qui seront renvoyés si votre requête rencontre une erreur fatale, reportez-vous à la section [Erreurs fatales.]({{site.baseurl}}/api/errors/#fatal-errors)
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/kpi.md b/_lang/fr_fr/_api/endpoints/export/kpi.md
new file mode 100644
index 00000000000..704a3ef808f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/kpi.md
@@ -0,0 +1,6 @@
+---
+nav_title: Indicateurs clé de performance
+config_only: true
+noindex: true
+page_order: 4
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_daily_new_users_date.md b/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_daily_new_users_date.md
new file mode 100644
index 00000000000..8de976206c3
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_daily_new_users_date.md
@@ -0,0 +1,67 @@
+---
+nav_title: "GET : Exporter les nouveaux utilisateurs quotidiens par date"
+article_title: "GET : Exporter les utilisateurs de Daily News par date"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les nouveaux utilisateurs quotidiens."
+
+---
+{% api %}
+# Exporter les nouveaux utilisateurs quotidiens par date
+{% apimethod get %}
+/kpi/new_users/data_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer quotidiennement une série du nombre total de nouveaux utilisateurs à chaque date.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#07756c39-cfa0-40a0-8101-03f8791cec01 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `kpi.new_users.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre| Requis | Type de données | Description |
+| -------- | -------- | --------- | ----------- |
+| `length` | Requis | Entier | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `ending_at` | Facultatif | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+| `app_id` | Facultatif | Chaîne de caractères | Identifiant de l'API de l'application récupéré à partir de la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/). En cas d'exclusion, les résultats de toutes les applications de l'espace de travail seront renvoyés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/kpi/new_users/data_series?length=14&ending_at=2018-06-28T23:59:59-5:00&app_id={{app_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time" : (string) the date as ISO 8601 date,
+            "new_users" : (int) the number of daily new users
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_dau_date.md b/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_dau_date.md
new file mode 100644
index 00000000000..a68a1ce924e
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_dau_date.md
@@ -0,0 +1,67 @@
+---
+nav_title: "GET : Exporter les utilisateurs actifs par jour par date"
+article_title: "GET : Exporter les utilisateurs actifs par jour par date"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les utilisateurs actifs quotidiens."
+
+---
+{% api %}
+# Exporter les utilisateurs actifs quotidiens par date
+{% apimethod get %}
+/kpi/dau/data_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer quotidiennement une série du nombre total d’utilisateurs actifs uniques à chaque date.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#90a64560-65aa-4f71-a8ef-1edf49321986 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `kpi.dau.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre| Requis | Type de données | Description |
+| -------- | -------- | --------- | ----------- |
+| `length` | Requis | Entier | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `ending_at` | Facultatif | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+| `app_id` | Facultatif | Chaîne de caractères | Identifiant de l'API de l'application récupéré à partir de la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/). En cas d'exclusion, les résultats de toutes les applications de l'espace de travail seront renvoyés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/kpi/dau/data_series?length=10&ending_at=2018-06-28T23:59:59-5:00&app_id={{app_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time" : (string) the date as ISO 8601 date,
+            "dau" : (int) the number of daily active users
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_mau_30_days.md b/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_mau_30_days.md
new file mode 100644
index 00000000000..839f6a5796e
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_mau_30_days.md
@@ -0,0 +1,67 @@
+---
+nav_title: "GET : Exporter les utilisateurs actifs mensuels pour les 30 derniers jours"
+article_title: "GET : Exporter les utilisateurs actifs mensuels pour les 30 derniers jours"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les utilisateurs actifs mensuels."
+
+---
+{% api %}
+# Exporter les utilisateurs actifs mensuels des 30 derniers jours
+{% apimethod get %}
+/kpi/mau/data_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer quotidiennement une série du nombre total d’utilisateurs actifs uniques sur une période de 30 jours glissants.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#68f45461-3bf1-425c-b918-f0bbf3f87149 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `kpi.mau.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre| Requis | Type de données | Description |
+| -------- | -------- | --------- | ----------- |
+| `length` | Requis | Entier | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `ending_at` | Facultatif | DateTime <br>chaîne ([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+| `app_id` | Facultatif | Chaîne de caractères | Identifiant de l'API de l'application récupéré à partir de la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/). Si exclu, les résultats de toutes les applications dans l'espace de travail seront renvoyés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/kpi/mau/data_series?length=7&ending_at=2018-06-28T23:59:59-05:00&app_id={{app_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time" : (string) the date as ISO 8601 date,
+            "mau" : (int) the number of monthly active users
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_uninstalls_date.md b/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_uninstalls_date.md
new file mode 100644
index 00000000000..979d6e3b08d
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/kpi/get_kpi_uninstalls_date.md
@@ -0,0 +1,67 @@
+---
+nav_title: "GET : Exporter les KPI pour les désinstallations quotidiennes d'applications par date"
+article_title: "GET : Exporter les KPI pour les désinstallations quotidiennes d'applications par date"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les désinstallations quotidiennes d’application par date."
+
+---
+{% api %}
+# Exporter les KPI pour les désinstallations quotidiennes d’application par date
+{% apimethod get %}
+/kpi/uninstalls/data_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer quotidiennement une série du nombre total de désinstallations à chaque date.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#59c4d592-3e77-42f8-8ff1-d5d250acbeae {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `kpi.uninstalls.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre| Requis | Type de données | Description |
+| -------- | -------- | --------- | ----------- |
+| `length` | Requis | Entier | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `ending_at` | Facultatif | DateTime <br>(string [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+| `app_id` | Facultatif | Chaîne de caractères | Identifiant de l'API de l'application récupéré à partir de la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/). Si exclu, les résultats de toutes les applications dans l'espace de travail seront renvoyés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/kpi/uninstalls/data_series?length=14&ending_at=2018-06-28T23:59:59-5:00&app_id={{app_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time" : (string) the date as ISO 8601 date,
+            "uninstalls" : (int) the number of uninstalls
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/news_feed.md b/_lang/fr_fr/_api/endpoints/export/news_feed.md
new file mode 100644
index 00000000000..3d6c57bc195
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/news_feed.md
@@ -0,0 +1,6 @@
+---
+nav_title: Fil d’actualité
+config_only: true
+noindex: true
+page_order: 5
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/news_feed/get_news_feed_card_analytics.md b/_lang/fr_fr/_api/endpoints/export/news_feed/get_news_feed_card_analytics.md
new file mode 100644
index 00000000000..eb597c1fe4f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/news_feed/get_news_feed_card_analytics.md
@@ -0,0 +1,75 @@
+---
+nav_title: "GET : Exportation du fil d'actualité Analyse des cartes (si utilisé comme carte adjective d'actualité)"
+article_title: "GET : Exportation du fil d'actualité Analyse des cartes (si utilisé comme carte adjective d'actualité)"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter l’analyse des cartes de fil d’actualité."
+
+---
+{% api %}
+# Exporter l’analyse des cartes de fil d’actualité
+{% apimethod get %}
+/feed/data_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer quotidiennement une série de statistiques d’engagement pour une carte au fil du temps.
+
+{% alert note %}
+Le Fil d’actualité est obsolète. Braze recommande aux clients qui utilisent notre outil de fil d’actualités de passer à notre canal de communication de cartes de contenu : il est plus flexible, plus personnalisable et plus fiable. Consultez le [guide de migration]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/migrating_from_news_feed/) pour en savoir plus.
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#9cdc3b1e-641e-4d62-b9e8-42d04ee9d4d8 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `feed.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre   | Requis | Type de données | Description |
+| ----------- | -------- | --------- | ----------- |
+| `card_id` | Requis | Chaîne de caractères | Voir l'[identifiant API de la carte]({{site.baseurl}}/api/identifier_types/). <br><br> Vous trouverez le site `card_id` pour une carte donnée sur la page des [clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) et sur la page des détails de la carte dans votre tableau de bord, ou vous pouvez utiliser le [point de terminaison Exporter la liste des cartes du fil d'actualité]({{site.baseurl}}/api/endpoints/export/news_feed/get_news_feed_cards/).|
+| `length` | Requis | Entier | Nombre maximum d’unités (jours ou heures) avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `unit` | Facultatif | Chaîne de caractères | Unité de temps entre les points de données. Peut être `day` ou `hour`, valeur par défaut `day`.  |
+| `ending_at` | Facultatif | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/feed/data_series?card_id={{card_identifier}}&length=14&unit=day&ending_at=2018-06-28T23:59:59-5:00' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time" : (string) the point in time - as ISO 8601 extended when unit is "hour" and as ISO 8601 date when unit is "day",
+            "clicks" : (int) the number of clicks,
+            "impressions" : (int) the number of impressions,
+            "unique_clicks" : (int) the number of unique clicks,
+            "unique_impressions" : (int) the number of unique impressions
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/news_feed/get_news_feed_card_details.md b/_lang/fr_fr/_api/endpoints/export/news_feed/get_news_feed_card_details.md
new file mode 100644
index 00000000000..4827de0b68c
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/news_feed/get_news_feed_card_details.md
@@ -0,0 +1,74 @@
+---
+nav_title: "GET : Détails de la carte de fil d'actualité pour l'exportation"
+article_title: "GET : Détails de la carte de fil d'actualité pour l'exportation"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les informations relatives à la carte de fil d’actualité."
+
+---
+{% api %}
+# Exporter les informations relatives à la carte de fil d’actualité
+{% apimethod get %}
+/feed/details
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer des informations pertinentes sur une carte, qui peuvent être identifiées par le `card_id`.
+
+{% alert note %}
+Le Fil d’actualité est obsolète. Braze recommande aux clients qui utilisent notre outil de fil d’actualités de passer à notre canal de communication de cartes de contenu : il est plus flexible, plus personnalisable et plus fiable. Consultez le [guide de migration]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/migrating_from_news_feed/) pour en savoir plus.
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#5b1401a6-f12c-4827-82c9-8dc604f1671e {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `feed.details`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description            |
+| --------- | -------- | --------- | ---------------------- |
+| `card_id` | Requis | Chaîne de caractères | Voir l'[identifiant API de la carte]({{site.baseurl}}/api/identifier_types/). <br><br> Vous trouverez le site `card_id` pour une carte donnée sur la page des [clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) et sur la page des détails de la carte dans votre tableau de bord, ou vous pouvez utiliser le [point de terminaison Exporter la liste des cartes du fil d'actualité]({{site.baseurl}}/api/endpoints/export/news_feed/get_news_feed_cards/).|
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/feed/details?card_id={{card_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) The status of the export, returns 'success' when completed without errors,
+    "created_at" : (string) the ate created as ISO 8601 date,
+    "updated_at" : (string) the ate last updated as ISO 8601 date,
+    "name" : (string) the card name,
+    "publish_at" : (string) the date the card was published as ISO 8601 date,
+    "end_at" : (string) the date the card will stop displaying for users as ISO 8601 date,
+    "tags" : (array) the tag names associated with the card,
+    "title" : (string) the title of the card,
+    "image_url" : (string) the image URL used by this card,
+    "extras" : (dictionary) a dictionary containing key-value pair data attached to this card,
+    "description" : (string) the description text used by this card,
+    "archived": (boolean) whether this Card is archived,
+    "draft": (boolean) whether this Card is a draft,
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/news_feed/get_news_feed_cards.md b/_lang/fr_fr/_api/endpoints/export/news_feed/get_news_feed_cards.md
new file mode 100644
index 00000000000..6da3dcb2f85
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/news_feed/get_news_feed_cards.md
@@ -0,0 +1,73 @@
+---
+nav_title: "GET : Exporter la liste des cartes du fil d'actualité"
+article_title: "GET : Exporter la liste des cartes du fil d'actualité"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter la liste des cartes de fil d’actualités."
+
+---
+{% api %}
+# Exporter la liste des cartes de fil d’actualités
+{% apimethod get %}
+/feed/list
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter une liste de cartes de fil d’actualité, chacune incluant son nom et son identifiant API de carte. 
+
+Les cartes sont renvoyées par groupes de 100 triées par date de création (des plus anciennes aux plus récentes par défaut).
+
+{% alert note %}
+Le Fil d’actualité est obsolète. Braze recommande aux clients qui utilisent notre outil de fil d’actualités de passer à notre canal de communication de cartes de contenu : il est plus flexible, plus personnalisable et plus fiable. Consultez le [guide de migration]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/migrating_from_news_feed/) pour en savoir plus.
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#9fa7a3bc-4a02-4de2-bc4c-8f111750665e {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `feed.list`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `page` | Facultatif | Entier   | La page des cartes à renvoyer, par défaut sur 0 (renvoie le premier ensemble jusqu’à 100 éléments). |
+| `include_archived` | Facultatif | Valeur booléenne   | S’il faut inclure ou non des cartes archivées, par défaut sur Faux. |
+| `sort_direction` | Facultatif | Chaîne de caractères | \- Trier l’heure de création de la plus récente à la plus ancienne : indiquer la valeur `desc`.<br> \- Trier l’heure de création de la plus ancienne à la plus récente : indiquer la valeur `asc`. <br><br>Si `sort_direction` n’est pas inclus, l’ordre par défaut est de la plus ancienne à la plus récente. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/feed/list?page=1&include_archived=true&sort_direction=desc' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "cards" : [
+        {
+            "id" : (string) the card API identifier,
+            "type" : (string) type of the card - NewsItem (classic cards), CaptionedImage, Banner
+            "title" : (string) the title of the card,
+            "tags" : (array) the tag names associated with the card
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/purchases.md b/_lang/fr_fr/_api/endpoints/export/purchases.md
new file mode 100644
index 00000000000..2737c237738
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/purchases.md
@@ -0,0 +1,6 @@
+---
+nav_title: Achats
+config_only: true
+noindex: true
+page_order: 6
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/purchases/get_list_product_id.md b/_lang/fr_fr/_api/endpoints/export/purchases/get_list_product_id.md
new file mode 100644
index 00000000000..5ecf15a6b4e
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/purchases/get_list_product_id.md
@@ -0,0 +1,61 @@
+---
+nav_title: "GET : Exporter les ID des produits"
+article_title: "GET : Exporter les ID des produits"
+search_tag: Endpoint
+page_order: 1
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les ID de produit."
+
+---
+{% api %}
+# Exporter les ID de produit
+{% apimethod get %}
+/purchases/product_list
+{% endapimethod %}
+
+> Utilisez cet endpoint pour renvoyer les listes paginées d’ID de produit.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#dff4ed40-81f5-451d-9d44-accc0e932285{% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `purchases.product_list`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='purchases product list' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `page` | Facultatif | Chaîne de caractères | La page de votre liste de produits que vous souhaitez consulter. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+{% raw %}
+```
+https://rest.iad-01.braze.com/purchases/product_list?page=1
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "products": [
+    "product_name" (string), the name of the product
+  ],
+  "message": "success"
+}
+```
+
+{% endapi %}
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
diff --git a/_lang/fr_fr/_api/endpoints/export/purchases/get_number_of_purchases.md b/_lang/fr_fr/_api/endpoints/export/purchases/get_number_of_purchases.md
new file mode 100644
index 00000000000..3ec357af09d
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/purchases/get_number_of_purchases.md
@@ -0,0 +1,68 @@
+---
+nav_title: "GET : Exportation Nombre d'achats"
+article_title: "GET : Exportation Nombre d'achats"
+search_tag: Endpoint
+page_order: 3
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter le nombre d’achats."
+
+---
+{% api %}
+# Nombre d'achats à l'exportation
+{% apimethod get %}
+/achats/séries_quantités
+{% endapimethod %}
+
+> Utilisez cet endpoint pour renvoyer le nombre total d'achats dans votre appli sur une plage de temps.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#6ac59282-d231-4317-88df-f7f12169b94e{% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `purchases.quantity_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='purchases product list' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `ending_at` | Facultatif | Datetime[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle l’exportation de données doit se terminer. Par défaut, l’heure de la demande. |
+| `length` | Requis | Entier | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `unit` | Facultatif | Chaîne de caractères | Unité de temps entre les points de données. Il peut s'agir d'un jour ou d'une heure, la valeur par défaut étant le jour. |
+| `app_id` | Facultatif | Chaîne de caractères | Identifiant de l'API de l'application récupéré à partir de la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/). En cas d'exclusion, les résultats de toutes les applications d'un espace de travail seront renvoyés. |
+| `product` | Facultatif | Chaîne de caractères | Nom du produit par lequel filtrer les réponses. En cas d'exclusion, les résultats de toutes les applications seront renvoyés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/purchases/quantity_series?length=100' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "message": (required, string) the status of the export, returns 'success' when completed without errors,
+  "data" : [
+    {
+      "time" : (string) the date as ISO 8601 date,
+      "purchase_quantity" : (int) the number of items purchased in the time period
+      },
+    ...
+  ]
+}
+```
+
+{% endapi %}
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
diff --git a/_lang/fr_fr/_api/endpoints/export/purchases/get_revenue_series.md b/_lang/fr_fr/_api/endpoints/export/purchases/get_revenue_series.md
new file mode 100644
index 00000000000..9a4e5a89418
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/purchases/get_revenue_series.md
@@ -0,0 +1,68 @@
+---
+nav_title: "GET : Exporter des données de revenus"
+article_title: "GET : Exporter des données de revenus"
+search_tag: Endpoint
+page_order: 2
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter des données de revenus."
+
+---
+{% api %}
+# Exporter les données des chiffres d'affaires par période
+{% apimethod get %}
+/purchases/revenue_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour renvoyer l'argent total dépensé dans votre application sur une plage de temps.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#f6e05f9a-13c0-4d66-8caa-4a376d25749f{% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `purchases.revenue_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='purchases product list' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `ending_at` | Facultatif | Datetime[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle l’exportation de données doit se terminer. Par défaut, l’heure de la demande. |
+| `length` | Requis | Entier | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `unit` | Facultatif | Chaîne de caractères | Unité de temps entre les points de données. Il peut s'agir d'un jour ou d'une heure, la valeur par défaut étant le jour. |
+| `app_id` | Facultatif | Chaîne de caractères | Identifiant de l'API de l'application récupéré à partir de la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/). En cas d'exclusion, les résultats de toutes les applications d'un espace de travail seront renvoyés. |
+| `product` | Facultatif | Chaîne de caractères | Nom du produit par lequel filtrer les réponses. En cas d'exclusion, les résultats de toutes les applications seront renvoyés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/purchases/revenue_series?length=100' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "message": (required, string) the status of the export, returns 'success' when completed without errors,
+  "data" : [
+    {
+      "time" : (string) the date as ISO 8601 date,
+      "revenue" : (int) amount of revenue for the time period
+      },
+    ...
+  ]
+}
+```
+
+{% endapi %}
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
diff --git a/_lang/fr_fr/_api/endpoints/export/segments.md b/_lang/fr_fr/_api/endpoints/export/segments.md
new file mode 100644
index 00000000000..e4ed0d6ae69
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/segments.md
@@ -0,0 +1,6 @@
+---
+nav_title: Segments
+config_only: true
+noindex: true
+page_order: 7
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/segments/get_segment.md b/_lang/fr_fr/_api/endpoints/export/segments/get_segment.md
new file mode 100644
index 00000000000..fb44c163824
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/segments/get_segment.md
@@ -0,0 +1,68 @@
+---
+nav_title: "GET : Exporter la liste des segments"
+article_title: "GET : Exporter la liste des segments"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter la liste des segments."
+
+---
+{% api %}
+# Exporter la liste des segments
+{% apimethod get %}
+/segments/list
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter une liste de segments, chacun incluant son nom, l’identifiant API du segment et s’il a un suivi des analyses activé. 
+
+Les segments sont renvoyés par groupes de 100 triés par date de création (des plus anciens aux plus récents par défaut). Les segments archivés ne sont pas inclus.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#1349e6f4-3ce7-4e60-b3e9-951c99c0993f {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `segments.list`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre| Requis | Type de données | Description |
+| -------- | -------- | --------- | ----------- |
+| `page` | Facultatif | Entier | La page des segments à renvoyer, par défaut sur 0 (renvoie le premier ensemble jusqu’à 100 éléments). |
+| `sort_direction` | Facultatif | Chaîne de caractères | \- Trier l’heure de création de la plus récente à la plus ancienne : indiquer la valeur `desc`.<br> \- Trier l’heure de création de la plus ancienne à la plus récente : indiquer la valeur `asc`. <br><br>Si `sort_direction` n’est pas inclus, l’ordre par défaut est de la plus ancienne à la plus récente. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/segments/list?page=1&sort_direction=desc' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "segments" : [
+        {
+            "id" : (string) the Segment API identifier,
+            "name" : (string) segment name,
+            "analytics_tracking_enabled" : (boolean) whether the segment has analytics tracking enabled,
+            "tags" : (array) the tag names associated with the segment formatted as strings
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/segments/get_segment_analytics.md b/_lang/fr_fr/_api/endpoints/export/segments/get_segment_analytics.md
new file mode 100644
index 00000000000..5a5022b45af
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/segments/get_segment_analytics.md
@@ -0,0 +1,67 @@
+---
+nav_title: "GET : Analyse/analytique des segments d'exportation (si utilisés comme adjectifs)"
+article_title: "GET : Analyse/analytique des segments d'exportation (si utilisés comme adjectifs)"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter l'analyse de segment."
+
+---
+{% api %}
+# Exporter l'analyse de segment
+{% apimethod get %}
+/segments/data_series
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer quotidiennement une série de la taille estimée d’un segment au fil du temps.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#62d9d142-cdec-4aea-a287-c13efea7415e {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `segments.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `segment_id` | Requis | Chaîne de caractères | Voir l'[identifiant API du segment.]({{site.baseurl}}/api/identifier_types/)<br><br> Vous trouverez l'adresse `segment_id` pour un segment donné sur la page des [clés API de]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) votre compte Braze ou vous pouvez utiliser l'[endpoint Exporter la liste des segments]({{site.baseurl}}/api/endpoints/export/segments/get_segment/).  |
+| `length` | Requis | Entier | Nombre maximum de jours avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `ending_at` | Facultatif | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/segments/data_series?segment_id={{segment_identifier}}&length=14&ending_at=2018-06-27T23:59:59-5:00' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time" : (string) the date as ISO 8601 date,
+            "size" : (int) the size of the segment on that date
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/segments/get_segment_details.md b/_lang/fr_fr/_api/endpoints/export/segments/get_segment_details.md
new file mode 100644
index 00000000000..fbf9b80751f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/segments/get_segment_details.md
@@ -0,0 +1,65 @@
+---
+nav_title: "GET : Détails de la segmentation des exportations"
+article_title: "GET : Détails de la segmentation des exportations"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les informations relatives au segment."
+
+---
+{% api %}
+# Exporter les informations relatives au segment
+{% apimethod get %}
+/segments/details
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer des informations pertinentes sur un segment, qui peuvent être identifiées par le `segment_id`.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#aab56ed9-0a28-476a-8b57-b79786dbb9c1 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `segments.details`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre    | Requis | Type de données | Description            |
+| ------------ | -------- | --------- | ---------------------- |
+| `segment_id` | Requis | Chaîne de caractères | Voir l'[identifiant API du segment.]({{site.baseurl}}/api/identifier_types/)<br><br> Vous trouverez l'adresse `segment_id` pour un segment donné sur la page des [clés API de]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) votre compte Braze ou vous pouvez utiliser l'[endpoint Exporter la liste des segments]({{site.baseurl}}/api/endpoints/export/segments/get_segment/).  |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/segments/details?segment_id={{segment_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+      "message": (required, string) the status of the export, returns 'success' when completed without errors,
+      "created_at" : (string) the date created as ISO 8601 date,
+      "updated_at" : (string) the date last updated as ISO 8601 date,
+      "name" : (string) the segment name,
+      "description" : (string) a human-readable description of filters,
+      "text_description" : (string) the segment description, 
+      "tags" : (array) the tag names associated with the segment formatted as strings,
+      "teams" : (array) the names of the Teams associated with the campaign
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/sessions.md b/_lang/fr_fr/_api/endpoints/export/sessions.md
new file mode 100644
index 00000000000..7e6b6802c5b
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/sessions.md
@@ -0,0 +1,6 @@
+---
+nav_title: Sessions
+config_only: true
+noindex: true
+page_order: 8
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/sessions/get_sessions_analytics.md b/_lang/fr_fr/_api/endpoints/export/sessions/get_sessions_analytics.md
new file mode 100644
index 00000000000..8b46108fb76
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/sessions/get_sessions_analytics.md
@@ -0,0 +1,69 @@
+---
+nav_title: "GET : Exporter les sessions d'application par heure"
+article_title: "Get : Exporter les sessions d'application par heure"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les analyses de sessions d'application par heure."
+
+---
+{% api %}
+# Exporter les sessions d'application par heure
+{% apimethod get %}
+/sessions/séries de données
+{% endapimethod %}
+
+> Utilisez cet endpoint pour récupérer une série du nombre de sessions de votre application sur une période donnée.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#79efb6a9-62ec-4b8a-bf4a-e96313aa4be1 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `sessions.data_series`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre| Requis | Type de données | Description |
+| -------- | -------- | --------- | ----------- |
+| `length` | Requis | Entier | Nombre maximum d’unités (jours ou heures) avant `ending_at` à inclure dans la série renvoyée. Doit être compris entre 1 et 100 (inclus). |
+| `unit` | Facultatif | Chaîne de caractères | Unité de temps entre les points de données. Peut être `day` ou `hour`, valeur par défaut `day`.  |
+| `ending_at` | Facultatif | DateTime <br>[(](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Date à laquelle la série de données doit se terminer. Par défaut, l’heure de la demande. |
+| `app_id` | Facultatif | Chaîne de caractères | Identifiant de l'API de l'application récupéré à partir de la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) pour limiter l'analyse/analytique à une application spécifique. |
+| `segment_id` | Facultatif | Chaîne de caractères | Voir l'[identifiant API du segment.]({{site.baseurl}}/api/identifier_types/) ID de segment indiquant le segment à analyser pour lequel les sessions doivent être renvoyées. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/sessions/data_series?length=14&unit=day&ending_at=2018-06-28T23:59:59-5:00&app_id={{app_identifier}}&segment_id={{segment_identifier}}' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "data" : [
+        {
+            "time" : (string) point in time - as ISO 8601 extended when unit is "hour" and as ISO 8601 date when unit is "day",
+            "sessions" : (int)
+        },
+        ...
+    ]
+}
+```
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/user_data.md b/_lang/fr_fr/_api/endpoints/export/user_data.md
new file mode 100644
index 00000000000..a1fa377f9b0
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/user_data.md
@@ -0,0 +1,6 @@
+---
+nav_title: Données utilisateur
+config_only: true
+noindex: true
+page_order: 9
+---
diff --git a/_lang/fr_fr/_api/endpoints/export/user_data/post_users_global_control_group.md b/_lang/fr_fr/_api/endpoints/export/user_data/post_users_global_control_group.md
new file mode 100644
index 00000000000..5b633980656
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/user_data/post_users_global_control_group.md
@@ -0,0 +1,317 @@
+---
+nav_title: "POST : Exportation du profil utilisateur par groupe de contrôle global"
+article_title: "POST : Exportation du profil utilisateur par groupe de contrôle global"
+search_tag: Endpoint
+page_order: 6
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les utilisateurs dans les groupes de contrôle globaux."
+
+---
+{% api %}
+# Exporter le profil utilisateur par groupe de contrôle global
+{% apimethod post %}
+/users/export/global_control_group
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter tous les utilisateurs d’un groupe de contrôle global. 
+
+Les données des utilisateurs sont exportées sous la forme de plusieurs fichiers d'objets JSON d'utilisateurs séparés par de nouvelles lignes (par exemple, un objet JSON par ligne). Tous les utilisateurs d'un groupe de contrôle global sont inclus à chaque fois que les fichiers sont générés. Braze ne conserve pas l'historique des ajouts et suppressions d'utilisateurs dans un groupe de contrôle global.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#aa3d8b90-d984-48f0-9287-57aa30469de2 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `users.export.global_control_group`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Informations relatives à la réponse basée sur les informations d’identification
+
+Si vous avez ajouté vos identifiants [S3][1] ou [Azure][2] à Braze, alors chaque fichier sera téléchargé dans votre compartiment S3 sous la forme d'un fichier ZIP dont le format de clé ressemble à `segment-export/SEGMENT_ID/YYYY-MM-dd/RANDOM_UUID-TIMESTAMP_WHEN_EXPORT_STARTED/filename.zip`. Si vous utilisez Azure, assurez-vous que la case **Faire de cette destination la destination par défaut de l'exportation de données est** cochée dans la page d'aperçu du partenaire Azure dans Braze. Nous allons généralement créer 1 fichier pour 5 000 utilisateurs pour optimiser le traitement. L'exportation de segments plus petits au sein d'un grand espace de travail peut donner lieu à plusieurs fichiers. Vous pouvez alors décompresser les fichiers et concaténer tous les fichiers `json` dans un fichier unique si nécessaire. Si vous spécifiez un `output_format` de `gzip`, l’extension de fichier sera `.gz` au lieu de `.zip`.
+
+{% details Exportation de la répartition des chemins pour ZIP %}
+**Format ZIP :**
+`bucket-name/segment-export/SEGMENT_ID/YYYY-MM-dd/RANDOM_UUID-TIMESTAMP_WHEN_EXPORT_STARTED/filename.zip`
+
+**Exemple ZIP :**
+`braze.docs.bucket/segment-export/abc56c0c-rd4a-pb0a-870pdf4db07q/2019-04-25/d9696570-dfb7-45ae-baa2-25e302r2da27-1556044807/114f0226319130e1a4770f2602b5639a.zip`
+
+| Propriété | Détails | Montré dans l'exemple comme |
+|---|---|
+| `bucket-name` | Résolu en fonction du nom de votre compartiment. | `braze.docs.bucket` |
+| `segment-export` | Résolu. | `segment-export` |
+| `SEGMENT_ID` | Inclus dans la demande d’exportation. | `abc56c0c-rd4a-pb0a-870pdf4db07q` |
+| `YYYY-MM-dd` | Date à laquelle la fonction de rappel réussi est reçue. | `2019-04-25` |
+| `RANDOM_UUID` | Un UUID aléatoire généré par Braze au moment de la demande. | `d9696570-dfb7-45ae-baa2-25e302r2da27` |
+| `TIMESTAMP_WHEN_EXPORT_STARTED` | Heure Unix (secondes depuis 2017-01-01:00:00:00Z) à laquelle l'exportation a été demandée en UTC. | `1556044807` |
+| `filename` | Aléatoire par fichier. | `114f0226319130e1a4770f2602b5639a` |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% enddetails %}
+
+Nous vous conseillons vivement de configurer vos propres identifiants S3 ou Azure lorsque vous utilisez cet endpoint afin d'appliquer vos propres politiques de compartiment sur l'exportation. Si vous ne disposez pas de vos identifiants de stockage en nuage, la réponse à la demande fournit l'URL où un fichier ZIP contenant tous les fichiers de l'utilisateur peut être téléchargé. L'URL ne deviendra un emplacement/localisation valide qu'une fois l'exportation prête. 
+
+Sachez que si vous ne fournissez pas vos informations d’identification pour votre stockage cloud, il existe une limitation de la quantité de données que vous pouvez exporter à partir de cet endpoint. En fonction des champs que vous exportez et du nombre d’utilisateurs, le transfert de fichiers peut échouer si la quantité de données demandées est trop importante. La meilleure pratique consiste à spécifier les champs que vous souhaitez exporter en utilisant `fields_to_export` et à ne spécifier que les champs dont vous avez besoin afin de réduire la taille du transfert. Si vous obtenez des erreurs lors de la génération du fichier, envisagez de diviser votre base d'utilisateurs en plusieurs segments sur la base d'un numéro de compartiment aléatoire (par exemple, créez un segment dans lequel le numéro de compartiment aléatoire est inférieur à 1 000 ou compris entre 1 000 et 2 000).
+
+Dans l’un ou l’autre scénario, vous pouvez éventuellement fournir un `callback_endpoint` à notifier lorsque l’exportation est prête. Si le `callback_endpoint` est fourni, nous ferons une demande Post à l’adresse indiquée lorsque le téléchargement sera prêt. Le corps du Post sera "success":true. Si vous n’avez pas ajouté vos informations d’identification pour votre stockage cloud à Braze, le corps du Post contiendra également l’attribut `url` avec l’URL de téléchargement comme valeur.
+
+Les bases d’utilisateurs plus grandes entraîneront des temps d’exportation plus longs. Par exemple, une application avec 20 millions d’utilisateurs peut prendre une heure ou plus.
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "callback_endpoint" : (optional, string) endpoint to post a download URL to when the export is available,
+  "fields_to_export" : (required, array of string) name of user data fields to export, for example, ['first_name', 'email', 'purchases'],
+  "output_format" : (optional, string) When using your own S3 bucket, allows to specify file format as 'zip' or 'gzip'. Defaults to zip file format
+}
+```
+
+{% alert warning %}
+Les attributs personnalisés individuels ne peuvent pas être exportés. Cependant, tous les attributs personnalisés peuvent être exportés en incluant custom_attributes dans le tableau fields_to_export (par exemple, `['first_name', 'email', 'custom_attributes']`).
+{% endalert %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --- | ----------- | --------- | ------- |
+|`callback_endpoint` | Facultatif | Chaîne de caractères | Endpoint auquel publier une URL de téléchargement lorsque l’exportation est disponible. |
+|`fields_to_export` | Obligatoire* | Tableau de chaînes de caractères | Nom des champs de données utilisateur à exporter. Vous pouvez également exporter des attributs personnalisés. <br><br>\*À partir d’avril 2021, les nouveaux comptes doivent préciser des champs spécifiques à exporter. |
+|`output_format` | Facultatif | Chaîne de caractères | Lorsque vous utilisez votre propre compartiment S3, vous pouvez spécifier le format de fichier `zip` ou `gzip`. Le format de fichier ZIP est défini par défaut. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/export/global_control_group' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "callback_endpoint" : "",
+  "fields_to_export" : ["email", "braze_id"],
+  "output_format" : "zip"
+}'
+```
+
+## Champs à exporter
+
+Voici une liste des `fields_to_export` valides. Utiliser `fields_to_export` pour minimiser les données renvoyées peut améliorer le temps de réponse de cet endpoint d’API :
+
+| Champ à exporter | Type de données | Description |
+|---|---|---|
+| `apps` | Tableau | Les applications pour lesquelles l’utilisateur a enregistré des sessions, ce qui comprend les champs :<br><br>- `name` : nom de l’application<br>- `platform` : plateforme de l’application telle qu’iOS, Android ou Web<br>- `version` : numéro ou nom de version de l’application <br>- `sessions` : nombre total de sessions pour cette application<br>- `first_used` : date de la première session<br>- `last_used` : date de la dernière session<br><br>Tous les champs sont des chaînes de caractères. |
+| `attributed_campaign` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant d’une campagne donnée. |
+| `attributed_source` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant de la plateforme sur laquelle était l’annonce. |
+| `attributed_adgroup` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant pour un sous-groupe optionnel sous la campagne. |
+| `attributed_ad` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant d'un sous-groupement facultatif en dessous de la campagne et du groupe d'annonces. |
+| `braze_id` | Chaîne de caractères | Identifiant utilisateur unique spécifique à l’appareil défini par Braze pour cet utilisateur. |
+| `country` | Chaîne de caractères | Pays de l'utilisateur selon la norme [ISO 3166-1 alpha-2.](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)  |
+| `created_at` | Chaîne de caractères | Date et heure de la création du profil utilisateur au format ISO 8601. |
+| `custom_attributes` | Objet | Paires clé-valeur de l’attribut personnalisé de cet utilisateur. |
+| `custom_events` | Tableau | Événements personnalisés attribués à cet utilisateur dans les 90 derniers jours. |
+| `devices` | Tableau | Informations sur l’appareil de l’utilisateur qui devraient contenir les éléments suivants selon la plateforme :<br><br>- `model` : Nom du modèle de l’appareil<br>- `os` : Système d’exploitation de l’appareil<br>- `carrier` : Fournisseur de services de l’appareil, si disponible<br>- `idfv`: (iOS) Identifiant de l'appareil Braze, l'identifiant Apple pour le vendeur, s'il existe.<br>- `idfa` : (iOS) Identifiant publicitaire, s’il existe<br>- `device_id` : (Android) Identifiant de l’appareil Braze<br>- `google_ad_id` : (Android) Identifiant publicitaire Google Play, s’il existe<br>- `roku_ad_id` : (Roku) Identifiant publicitaire Roku<br>- `ad_tracking_enabled` : Si le suivi des annonces est activé sur l’appareil, peut être vrai ou faux |
+| `dob` | Chaîne de caractères | Date de naissance de l’utilisateur au format `YYYY-MM-DD`. |
+| `email` | Chaîne de caractères | Adresse e-mail de l’utilisateur. |
+| `external_id` | Chaîne de caractères | Identifiant utilisateur unique pour les utilisateurs identifiés. |
+| `first_name` | Chaîne de caractères | Prénom de l’utilisateur. |
+| `gender` | Chaîne de caractères | Genre de l’utilisateur. Les valeurs possibles sont :<br><br>- `M` : masculin<br>- `F` : féminin<br>- `O` : autre<br>- `N` : sans objet<br>- `P` : préfère ne pas répondre<br>- `nil` : inconnu |
+| `home_city` | Chaîne de caractères | Ville de résidence de l’utilisateur. |
+| `language` | Chaîne de caractères | Langue de l’utilisateur à la norme ISO-639-1. |
+| `last_coordinates` | Tableau de floats | Dernier emplacement de l’appareil de l’utilisateur, au format `[longitude, latitude]`. |
+| `last_name` | Chaîne de caractères | Nom de famille de l’utilisateur. |
+| `phone` | Chaîne de caractères | Numéro de téléphone de l'utilisateur au format E.164. |
+| `purchase`s | Tableau | Achats réalisés par cet utilisateur au cours des 90 derniers jours. |
+| `random_bucket` | Entier | [Numéro de compartiment aléatoire]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events#random-bucket-number-event) de l'utilisateur, utilisé pour créer des segments uniformément distribués d'utilisateurs aléatoires. |
+| `time_zone` | Chaîne de caractères | Fuseau horaire de l’utilisateur au même format que la base de données de fuseaux horaires IANA. |
+| `total_revenue` | Float | Revenus totaux attribués à cet utilisateur. Les revenus totaux sont calculés à partir des achats réalisés par l’utilisateur pendant la fenêtre de conversion pour les campagnes et les Canvas qu’il a reçus. |
+| `uninstalled_at` | Date/heure | Date et heure de désinstallation de l’application par l’utilisateur. Absent si l’application n’a pas été désinstallée. |
+| `user_aliases` | Objet | [Objet aliasing de l'utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object#user-alias-object-specification) contenant les adresses `alias_name` et `alias_label`, si elles existent. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "object_prefix": (required, string) the filename prefix that will be used for the JSON file produced by this export, for example,'bb8e2a91-c4aa-478b-b3f2-a4ee91731ad1-1464728599',
+    "url" : (optional, string) the URL where the segment export data can be downloaded if you do not have your own S3 credentials
+}
+```
+
+Après la mise à disposition de l'URL, celle-ci n'est valable que pour quelques heures. Par conséquent, nous vous recommandons fortement d’ajouter vos propres informations d’identification S3 dans Braze.
+
+### Exemple de sortie d'un fichier d'exportation utilisateur
+
+Objet Exportation utilisateur (nous inclurons le moins de données possible. S’il manque un champ de l’objet, il doit être considéré comme nul, faux ou vide) :
+
+{% tabs %}
+{% tab Tous les domaines %}
+
+```json
+{
+    "created_at" : (string),
+    "external_id" : (string),
+    "user_aliases" : [
+      {
+        "alias_name" : (string),
+        "alias_label" : (string)
+      }
+    ],
+    "braze_id": (string),
+    "first_name" : (string),
+    "last_name" : (string),
+    "email" : (string),
+    "dob" : (string) date for the user's date of birth,
+    "home_city" : (string),
+    "country" : (string) ISO-3166-1 alpha-2 standard,
+    "phone" : (string),
+    "language" : (string) ISO-639-1 standard,
+    "time_zone" : (string),
+    "last_coordinates" : (array of float) [lon, lat],
+    "gender" : (string) "M" | "F",
+    "total_revenue" : (float),
+    "attributed_campaign" : (string),
+    "attributed_source" : (string),
+    "attributed_adgroup" : (string),
+    "attributed_ad" : (string),
+    "custom_attributes" : (object) custom attribute key-value pairs,
+    "custom_events" : [
+      {
+        "name" : (string),
+        "first" : (string) date,
+        "last" : (string) date,
+        "count" : (int)
+      },
+      ...
+    ],
+    "purchases" : [
+      {
+        "name" : (string),
+        "first" : (string) date,
+        "last" : (string) date,
+         "count" : (int)
+      },
+      ...
+    ],
+    "devices" : [
+      {
+        "model" : (string),
+        "os" : (string),
+        "carrier" : (string),
+        "idfv" : (string) only included for iOS devices when IDFV collection is enabled,
+        "idfa" : (string) only included for iOS devices when IDFA collection is enabled,
+        "google_ad_id" : (string) only included for Android devices when Google Play Advertising Identifier collection is enabled,
+        "roku_ad_id" : (string) only included for Roku devices,
+        "ad_tracking_enabled" : (bool)
+      },
+      ...
+    ],
+    "apps" : [
+      {
+        "name" : (string),
+        "platform" : (string),
+        "version" : (string),
+        "sessions" : (string),
+        "first_used" : (string) date,
+        "last_used" : (string) date
+      },
+      ...
+    ],
+}
+```
+
+{% endtab %}
+{% tab Exemple de sortie %}
+
+```json
+{
+    "created_at" : "2020-07-10 15:00:00.000 UTC",
+    "external_id" : "A8i3mkd99",
+    "user_aliases" : [
+      {
+        "alias_name" : "user_123",
+        "alias_label" : "amplitude_id"
+      }
+    ],
+    "braze_id": "5fbd99bac125ca40511f2cb1",
+    "random_bucket" : 2365,
+    "first_name" : "Jane",
+    "last_name" : "Doe",
+    "email" : "example@braze.com",
+    "dob" : "1980-12-21",
+    "home_city" : "Chicago",
+    "country" : "US",
+    "phone" : "+442071838750",
+    "language" : "en",
+    "time_zone" : "Eastern Time (US & Canada)",
+    "last_coordinates" : [41.84157636433568, -87.83520818508256],
+    "gender" : "F",
+    "total_revenue" : 65,
+    "attributed_campaign" : "braze_test_campaign_072219",
+    "attributed_source" : "braze_test_source_072219",
+    "attributed_adgroup" : "braze_test_adgroup_072219",
+    "attributed_ad" : "braze_test_ad_072219",
+    "custom_attributes": 
+      {
+        "loyaltyId": "37c98b9d-9a7f-4b2f-a125-d873c5152856",
+        "loyaltyPoints": "321",
+        "loyaltyPointsNumber": 107
+      },
+    "custom_events": [
+      {
+          "name": "Loyalty Acknowledgement",
+          "first": "2021-06-28T17:02:43.032Z",
+          "last": "2021-06-28T17:02:43.032Z",
+          "count": 1
+      },
+      ...
+    ],
+    "purchases": [
+      {
+        "name": "item_40834",
+        "first": "2021-09-05T03:45:50.540Z",
+        "last": "2022-06-03T17:30:41.201Z",
+        "count": 10
+      },
+      ...
+    ],
+    "devices": [
+      {
+        "model": "Pixel XL",
+        "os": "Android (Q)",
+        "carrier": null,
+        "device_id": "312ef2c1-83db-4789-967-554545a1bf7a",
+        "ad_tracking_enabled": true
+      },
+      ...
+    ],
+    "apps": [
+      {
+        "name": "MovieCannon",
+        "platform": "Android",
+        "version": "3.29.0",
+        "sessions": 1129,
+        "first_used": "2020-02-02T19:56:19.142Z",
+        "last_used": "2021-11-11T00:25:19.201Z"
+      },
+      ...
+    ],
+}
+```
+
+{% endtab %}
+{% endtabs %}
+
+[1]: {{site.baseurl}}/partners/data_and_infrastructure_agility/cloud_storage/amazon_s3
+[2]: {{site.baseurl}}/partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents/
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/user_data/post_users_identifier.md b/_lang/fr_fr/_api/endpoints/export/user_data/post_users_identifier.md
new file mode 100644
index 00000000000..d32af2c04ba
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/user_data/post_users_identifier.md
@@ -0,0 +1,428 @@
+---
+nav_title: "POST : Exporter le profil utilisateur par identifiant"
+article_title: "POST : Exporter le profil utilisateur par identifiant"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les utilisateurs par identifiant."
+
+---
+{% api %}
+# Exporter le profil utilisateur par identifiant
+{% apimethod post %}
+/users/export/ids
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter des données à partir de n’importe quel profil utilisateur en spécifiant un identifiant utilisateur. 
+
+Vous pouvez inclure jusqu’à 50 `external_ids` ou `user_aliases` dans une seule requête. Si vous souhaitez spécifier un `device_id`, une `email_address` ou un `phone`, un seul de ces identifiants peut être inclus par requête.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#b9750447-9d94-4263-967f-f816f0c76577 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `users.export.ids`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='users export ids' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "external_ids": (optional, array of strings) External identifiers for users you wish to export,
+  "user_aliases": (optional, array of user alias objects) user aliases for users to export,
+  "device_id": (optional, string) Device identifier as returned by various SDK methods such as `getDeviceId`,
+  "braze_id": (optional, string) Braze identifier for a particular user,
+  "email_address": (optional, string) Email address of user,
+  "phone": (optional, string) Phone number of user,
+  "fields_to_export": (optional, array of strings) Name of user data fields to export. Defaults to all if not provided
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|-----|-----|-----|-----|
+|`external_ids` | Facultatif | Tableau de chaînes de caractères | Identifiants externes des utilisateurs que vous souhaitez exporter. |
+|`user_aliases` | Facultatif | Tableau d’objets Alias utilisateur | [Alias de l']({{site.baseurl}}/api/objects_filters/user_alias_object/) utilisateur pour les utilisateurs à exporter. |
+|`device_id` | Facultatif | Chaîne de caractères | L’identifiant d’appareil, tel que renvoyé par diverses méthodes SDK, telles que `getDeviceId`. |
+|`braze_id` | Facultatif | Chaîne de caractères | Identifiant Braze d’un utilisateur particulier. |
+|`email_address` | Facultatif | Chaîne de caractères | Adresse e-mail de l’utilisateur. |
+|`phone` | Facultatif | Chaîne de caractères dans [E.164](https://en.wikipedia.org/wiki/E.164) format | Numéro de téléphone de l’utilisateur. |
+|`fields_to_export` | Facultatif | Tableau de chaînes de caractères | Nom des champs de données utilisateur à exporter. Par défaut sur Tous, si non renseigné. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/export/ids' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "external_ids": ["user_identifier1", "user_identifier2"],
+  "user_aliases": [
+    {
+      "alias_name": "example_alias",
+      "alias_label": "example_label"
+    }
+  ],
+  "device_id": "1234567",
+  "braze_id": "braze_identifier",
+  "email_address": "example@braze.com",
+  "phone": "11112223333",
+  "fields_to_export": ["first_name", "email", "purchases"]
+}'
+```
+
+## Champs à exporter
+
+Voici une liste des `fields_to_export` valides. Utiliser `fields_to_export` pour minimiser les données renvoyées peut améliorer le temps de réponse de cet endpoint d’API :
+
+| Champ à exporter | Type de données | Description |
+|---|---|---|
+| `apps` | Tableau | Les applications pour lesquelles l’utilisateur a enregistré des sessions, ce qui comprend les champs :<br><br>- `name` : nom de l’application<br>- `platform` : plateforme de l’application telle qu’iOS, Android ou Web<br>- `version` : numéro ou nom de version de l’application <br>- `sessions` : nombre total de sessions pour cette application<br>- `first_used` : date de la première session<br>- `last_used` : date de la dernière session<br><br>Tous les champs sont des chaînes de caractères. |
+| `attributed_campaign` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant d’une campagne donnée. |
+| `attributed_source` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant de la plateforme sur laquelle était l’annonce. |
+| `attributed_adgroup` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant pour un sous-groupe optionnel sous la campagne. |
+| `attributed_ad` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant d'un sous-groupement facultatif en dessous de la campagne et du groupe d'annonces. |
+| `braze_id` | Chaîne de caractères | Identifiant utilisateur unique spécifique à l’appareil défini par Braze pour cet utilisateur. |
+| `country` | Chaîne de caractères | Pays de l'utilisateur selon la norme [ISO 3166-1 alpha-2.](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)  |
+| `created_at` | Chaîne de caractères | Date et heure de la création du profil utilisateur au format ISO 8601. |
+| `custom_attributes` | Objet | Paires clé-valeur de l’attribut personnalisé de cet utilisateur. |
+| `custom_events` | Tableau | Événements personnalisés attribués à cet utilisateur dans les 90 derniers jours. |
+| `devices` | Tableau | Informations sur l’appareil de l’utilisateur qui devraient contenir les éléments suivants selon la plateforme :<br><br>- `model` : Nom du modèle de l’appareil<br>- `os` : Système d’exploitation de l’appareil<br>- `carrier` : Fournisseur de services de l’appareil, si disponible<br>- `idfv`: (iOS) Identifiant de l'appareil Braze, l'identifiant Apple pour le vendeur, s'il existe.<br>- `idfa` : (iOS) Identifiant publicitaire, s’il existe<br>- `device_id` : (Android) Identifiant de l’appareil Braze<br>- `google_ad_id` : (Android) Identifiant publicitaire Google Play, s’il existe<br>- `roku_ad_id` : (Roku) Identifiant publicitaire Roku<br>- `ad_tracking_enabled` : Si le suivi des annonces est activé sur l’appareil, peut être vrai ou faux |
+| `dob` | Chaîne de caractères | Date de naissance de l’utilisateur au format `YYYY-MM-DD`. |
+| `email` | Chaîne de caractères | Adresse e-mail de l’utilisateur. |
+| `external_id` | Chaîne de caractères | Identifiant utilisateur unique pour les utilisateurs identifiés. |
+| `first_name` | Chaîne de caractères | Prénom de l’utilisateur. |
+| `gender` | Chaîne de caractères | Genre de l’utilisateur. Les valeurs possibles sont :<br><br>- `M` : masculin<br>- `F` : féminin<br>- `O` : autre<br>- `N` : sans objet<br>- `P` : préfère ne pas répondre<br>- `nil` : inconnu |
+| `home_city` | Chaîne de caractères | Ville de résidence de l’utilisateur. |
+| `language` | Chaîne de caractères | Langue de l’utilisateur à la norme ISO-639-1. |
+| `last_coordinates` | Tableau de floats | Dernier emplacement de l’appareil de l’utilisateur, au format `[longitude, latitude]`. |
+| `last_name` | Chaîne de caractères | Nom de famille de l’utilisateur. |
+| `phone` | Chaîne de caractères | Numéro de téléphone de l'utilisateur au format E.164. |
+| `purchases` | Tableau | Achats réalisés par cet utilisateur au cours des 90 derniers jours. |
+| `push_tokens` | Tableau | Identifiant anonyme unique qui spécifie où envoyer les notifications d'une app. |
+| `random_bucket` | Entier | [Numéro de compartiment aléatoire]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events#random-bucket-number-event) de l'utilisateur, utilisé pour créer des segments uniformément distribués d'utilisateurs aléatoires. |
+| `time_zone` | Chaîne de caractères | Fuseau horaire de l’utilisateur au même format que la base de données de fuseaux horaires IANA. |
+| `total_revenue` | Float | Revenus totaux attribués à cet utilisateur. Les revenus totaux sont calculés à partir des achats réalisés par l’utilisateur pendant la fenêtre de conversion pour les campagnes et les Canvas qu’il a reçus. |
+| `uninstalled_at` | Date/heure | Date et heure de désinstallation de l’application par l’utilisateur. Absent si l’application n’a pas été désinstallée. |
+| `user_aliases` | Objet | [Objet aliasing de l'utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object#user-alias-object-specification) contenant les adresses `alias_name` et `alias_label`, si elles existent. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+Sachez que l’endpoint `/users/export/ids` extraira l’intégralité du profil utilisateur de cet utilisateur, y compris les données telles que toutes les campagnes et les Canvas reçus, tous les événements personnalisés et tous les achats effectués, et tous les attributs personnalisés. Par conséquent, cet endpoint est plus lent que les autres endpoints d’API REST.
+
+Selon les données demandées, cet endpoint d’API peut ne pas être suffisant pour répondre à vos besoins en raison de la limite de débit à 2 500 demandes par minute. Si vous prévoyez d’utiliser cet endpoint régulièrement pour exporter des utilisateurs, envisagez plutôt de le faire par segment, ce qui est asynchrone et plus optimisé pour les extractions de données plus importantes.
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "users" : (array of object) the data for each of the exported users, may be empty if no users are found,
+    "invalid_user_ids" : (optional, array of string) each of the identifiers provided in the request that did not correspond to a known user
+}
+```
+
+L'exemple suivant illustre les données accessibles via cet endpoint.
+
+### Exemple de sortie d'un fichier d'exportation utilisateur
+
+Objet Exportation utilisateur (nous inclurons le moins de données possible. S’il manque un champ de l’objet, il doit être considéré comme nul, faux ou vide) :
+
+{% tabs %}
+{% tab Tous les domaines %}
+
+```json
+{
+    "created_at": (string),
+    "external_id" : (string),
+    "user_aliases" : [
+      {
+        "alias_name" : (string),
+        "alias_label" : (string)
+      }
+    ],
+    "braze_id": (string),
+    "first_name" : (string),
+    "last_name" : (string),
+    "email" : (string),
+    "dob" : (string) date for the user's date of birth,
+    "home_city" : (string),
+    "country" : (string) ISO-3166-1 alpha-2 standard,
+    "phone" : (string),
+    "language" : (string) ISO-639-1 standard,
+    "time_zone" : (string),
+    "last_coordinates" : (array of float) [lon, lat],
+    "gender" : (string) "M" | "F",
+    "total_revenue" : (float),
+    "attributed_campaign" : (string),
+    "attributed_source" : (string),
+    "attributed_adgroup" : (string),
+    "attributed_ad" : (string),
+    "push_subscribe" : (string) "opted_in" | "subscribed" | "unsubscribed",
+    "email_subscribe" : (string) "opted_in" | "subscribed" | "unsubscribed",
+    "custom_attributes" : (object) custom attribute key-value pairs,
+    "custom_events" : [
+      {
+        "name" : (string),
+        "first" : (string) date,
+        "last" : (string) date,
+        "count" : (int)
+      },
+      ...
+    ],
+    "purchases" : [
+      {
+        "name" : (string),
+        "first" : (string) date,
+        "last" : (string) date,
+        "count" : (int)
+      },
+      ...
+    ],
+    "devices" : [
+      {
+        "model" : (string),
+        "os" : (string),
+        "carrier" : (string),
+        "idfv" : (string) only included for iOS devices when IDFV collection is enabled,
+        "idfa" : (string) only included for iOS devices when IDFA collection is enabled,
+        "google_ad_id" : (string) only included for Android devices when Google Play Advertising Identifier collection is enabled,
+        "roku_ad_id" : (string) only included for Roku devices,
+        "ad_tracking_enabled" : (bool)
+      },
+      ...
+    ],
+    "push_tokens" : [
+      {
+        "app" : (string) app name,
+        "platform" : (string),
+        "token" : (string)
+      },
+      ...
+    ],
+    "apps" : [
+      {
+        "name" : (string),
+        "platform" : (string),
+        "version" : (string),
+        "sessions" : (integer),
+        "first_used" : (string) date,
+        "last_used" : (string) date
+      },
+      ...
+    ],
+    "campaigns_received" : [
+      {
+        "name" : (string),
+        "last_received" : (string) date,
+        "engaged" : 
+         {
+           "opened_email" : (bool),
+           "opened_push" : (bool),
+           "clicked_email" : (bool),
+           "clicked_triggered_in_app_message" : (bool)
+          },
+          "converted" : (bool),
+          "api_campaign_id" : (string),
+          "variation_name" : (optional, string) exists only if it is a multivariate campaign,
+          "variation_api_id" : (optional, string) exists only if it is a multivariate campaign,
+          "in_control" : (optional, bool) exists only if it is a multivariate campaign
+        },
+      ...
+    ],
+    "canvases_received": [
+      {
+        "name": (string),
+        "api_canvas_id": (string),
+        "last_received_message": (string) date,
+        "last_entered": (string) date,
+        "variation_name": (string),
+        "in_control": (bool),
+        "last_exited": (string) date,
+        "steps_received": [
+          {
+            "name": (string),
+            "api_canvas_step_id": (string),
+            "last_received": (string) date
+          },
+          {
+            "name": (string),
+            "api_canvas_step_id": (string),
+            "last_received": (string) date
+          },
+          {
+            "name": (string),
+            "api_canvas_step_id": (string),
+            "last_received": (string) date
+          }
+        ]
+      },
+      ...
+    ],
+    "cards_clicked" : [
+      {
+        "name" : (string)
+      },
+      ...
+    ]
+}
+```
+
+{% endtab %}
+{% tab Exemple de sortie %}
+
+```json
+{
+    "created_at" : "2020-07-10 15:00:00.000 UTC",
+    "external_id" : "A8i3mkd99",
+    "user_aliases" : [
+      {
+        "alias_name" : "user_123",
+        "alias_label" : "amplitude_id"
+      }
+    ],
+    "braze_id": "5fbd99bac125ca40511f2cb1",
+    "random_bucket" : 2365,
+    "first_name" : "Jane",
+    "last_name" : "Doe",
+    "email" : "example@braze.com",
+    "dob" : "1980-12-21",
+    "home_city" : "Chicago",
+    "country" : "US",
+    "phone" : "+442071838750",
+    "language" : "en",
+    "time_zone" : "Eastern Time (US & Canada)",
+    "last_coordinates" : [41.84157636433568, -87.83520818508256],
+    "gender" : "F",
+    "total_revenue" : 65,
+    "attributed_campaign" : "braze_test_campaign_072219",
+    "attributed_source" : "braze_test_source_072219",
+    "attributed_adgroup" : "braze_test_adgroup_072219",
+    "attributed_ad" : "braze_test_ad_072219",
+    "push_subscribe" : "opted_in", 
+    "push_opted_in_at": "2020-01-26T22:45:53.953Z",
+    "email_subscribe" : "subscribed",
+    "custom_attributes": 
+    {
+      "loyaltyId": "37c98b9d-9a7f-4b2f-a125-d873c5152856",
+      "loyaltyPoints": "321",
+       "loyaltyPointsNumber": 107
+    },
+    "custom_events": [
+      {
+        "name": "Loyalty Acknowledgement",
+        "first": "2021-06-28T17:02:43.032Z",
+        "last": "2021-06-28T17:02:43.032Z",
+        "count": 1
+      },
+      ...
+    ],
+    "purchases": [
+      {
+        "name": "item_40834",
+        "first": "2021-09-05T03:45:50.540Z",
+        "last": "2022-06-03T17:30:41.201Z",
+        "count": 10
+      },
+      ...
+    ],
+    "devices": [
+      {
+        "model": "Pixel XL",
+        "os": "Android (Q)",
+        "carrier": null,
+        "device_id": "312ef2c1-83db-4789-967-554545a1bf7a",
+        "ad_tracking_enabled": true
+      },
+      ...
+    ],
+    "push_tokens": [
+      {
+        "app": "MovieCanon",
+        "platform": "Android",
+        "token": "12345abcd",
+        "device_id": "312ef2c1-83db-4789-967-554545a1bf7a",
+        "notifications_enabled": true
+      },
+      ...
+    ],
+    "apps": [
+      {
+        "name": "MovieCannon",
+        "platform": "Android",
+        "version": "3.29.0",
+        "sessions": 1129,
+        "first_used": "2020-02-02T19:56:19.142Z",
+        "last_used": "2021-11-11T00:25:19.201Z"
+      },
+      ...
+    ],
+    "campaigns_received": [
+      {
+        "name": "Email Unsubscribe",
+        "api_campaign_id": "d72fdc84-ddda-44f1-a0d5-0e79f47ef942",
+        "last_received": "2022-06-02T03:07:38.105Z",
+        "engaged": 
+        {
+           "opened_email": true
+        },
+        "converted": true,
+        "multiple_converted": 
+        {
+          "Primary Conversion Event - A": true
+        },
+        "in_control": false,
+        "variation_name": "Variant 1",
+        "variation_api_id": "1bddc73a-a134-4784-9134-5b5574a9e0b8"
+      },
+      ...
+    ],
+    "canvases_received": [
+      {
+        "name": "Non Global  Holdout Group 4/21/21",
+        "api_canvas_id": "46972a9d-dc81-473f-aa03-e3473b4ed781",
+        "last_received_message": "2021-07-07T20:46:24.136Z",
+        "last_entered": "2021-07-07T20:45:24.000+00:00",
+        "variation_name": "Variant 1",
+        "in_control": false,
+        "last_entered_control_at": null,
+        "last_exited": "2021-07-07T20:46:24.136Z",
+        "steps_received": [
+          {
+            "name": "Step",
+            "api_canvas_step_id": "43d1a349-c3c8-4be1-9fbe-ce708e4d1c39",
+            "last_received": "2021-07-07T20:46:24.136Z"
+          },
+          ...
+        ]
+      }
+      ...
+    ],    
+    "cards_clicked" : [
+      {
+        "name" : "Loyalty Promo"
+      },
+      ...
+    ]
+}
+```
+
+{% endtab %}
+{% endtabs %}
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/export/user_data/post_users_segment.md b/_lang/fr_fr/_api/endpoints/export/user_data/post_users_segment.md
new file mode 100644
index 00000000000..0ed83e63959
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/export/user_data/post_users_segment.md
@@ -0,0 +1,478 @@
+---
+nav_title: "POST : Exporter le profil utilisateur par segmentation"
+article_title: "POST : Exporter le profil utilisateur par segmentation"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Exporter les utilisateurs par segment."
+
+---
+{% api %}
+# Exporter le profil utilisateur par segment
+{% apimethod post %}
+/users/export/segment
+{% endapimethod %}
+
+> Utilisez cet endpoint pour exporter tous les utilisateurs d’un segment. 
+
+{% alert important %}
+Lors de l'utilisation de cet endpoint, notez les points suivants :<br><br>1\. Le champ `fields_to_export` de cette demande d'API est **obligatoire**.<br>2\. Les champs pour `custom_events`, `purchases`, `campaigns_received`, et `canvases_received` contiennent uniquement les données des 90 derniers jours.
+{% endalert %}
+
+Les données des utilisateurs sont exportées sous la forme de plusieurs fichiers d'objets JSON d'utilisateurs séparés par de nouvelles lignes (par exemple, un objet JSON par ligne). Les données sont exportées vers une URL générée automatiquement ou vers un compartiment S3 si cette intégration est déjà configurée.
+
+Notez qu’une entreprise peut exécuter au maximum une exportation par segment à l’aide de cet endpoint à un moment donné. Attendez la fin de l'exportation avant de réessayer. 
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#cfa6fa98-632c-4f25-8789-6c3f220b9457 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `users.export.segment`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Informations relatives à la réponse basée sur les informations d’identification
+
+Si vous avez ajouté vos identifiants [S3][1], [Azure][2] ou [Google cloud storage][3] à Braze, alors chaque fichier sera téléchargé dans votre compartiment S3 sous la forme d'un fichier ZIP dont le format de clé ressemble à `segment-export/SEGMENT_ID/YYYY-MM-dd/RANDOM_UUID-TIMESTAMP_WHEN_EXPORT_STARTED/filename.zip`. Si vous utilisez Azure, assurez-vous que la case **Faire de cette destination la destination par défaut de l'exportation de données est** cochée dans la page d'aperçu du partenaire Azure dans Braze. Nous allons généralement créer 1 fichier pour 5 000 utilisateurs pour optimiser le traitement. L'exportation de segments plus petits au sein d'un grand espace de travail peut donner lieu à plusieurs fichiers. Vous pouvez alors décompresser les fichiers et concaténer tous les fichiers `json` dans un fichier unique si nécessaire. Si vous spécifiez un `output_format` de `gzip`, l’extension de fichier sera `.gz` au lieu de `.zip`.
+
+{% details Exportation de la répartition des chemins pour ZIP %}
+**Format ZIP :**
+`bucket-name/segment-export/SEGMENT_ID/YYYY-MM-dd/RANDOM_UUID-TIMESTAMP_WHEN_EXPORT_STARTED/filename.zip`
+
+**Exemple ZIP :**
+`braze.docs.bucket/segment-export/abc56c0c-rd4a-pb0a-870pdf4db07q/2019-04-25/d9696570-dfb7-45ae-baa2-25e302r2da27-1556044807/114f0226319130e1a4770f2602b5639a.zip`
+
+| Propriété | Détails | Montré dans l'exemple comme |
+|---|---|
+| `bucket-name` | Résolu en fonction du nom de votre compartiment. | `braze.docs.bucket` |
+| `segment-export` | Résolu. | `segment-export` |
+| `SEGMENT_ID` | Inclus dans la demande d’exportation. | `abc56c0c-rd4a-pb0a-870pdf4db07q` |
+| `YYYY-MM-dd` | Date à laquelle la fonction de rappel réussi est reçue. | `2019-04-25` |
+| `RANDOM_UUID` | Un UUID aléatoire généré par Braze au moment de la demande. | `d9696570-dfb7-45ae-baa2-25e302r2da27` |
+| `TIMESTAMP_WHEN_EXPORT_STARTED` | Heure Unix (secondes depuis 2017-01-01:00:00:00Z) à laquelle l'exportation a été demandée en UTC. | `1556044807` |
+| `filename` | Aléatoire par fichier. | `114f0226319130e1a4770f2602b5639a` |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+{% enddetails %}
+
+Nous vous conseillons vivement de configurer vos propres identifiants S3 ou Azure lorsque vous utilisez cet endpoint afin d'appliquer vos propres politiques de compartiment sur l'exportation. Si vous n'avez pas vos identifiants de stockage en nuage, la réponse à la demande fournit l'URL où un fichier ZIP contenant tous les fichiers de l'utilisateur peut être téléchargé. L'URL ne deviendra un emplacement/localisation valide qu'une fois l'exportation prête. 
+
+Sachez que si vous ne fournissez pas vos identifiants de stockage dans le cloud, la quantité de données que vous pouvez exporter depuis cet endpoint est limitée. En fonction des champs que vous exportez et du nombre d’utilisateurs, le transfert de fichiers peut échouer si la quantité de données demandées est trop importante. Une bonne pratique consiste à spécifier les champs que vous souhaitez exporter à l’aide de `fields_to_export` et à ne préciser que les champs dont vous avez besoin afin de réduire la taille du transfert. Si vous obtenez des erreurs lors de la génération du fichier, envisagez de diviser votre base d'utilisateurs en plusieurs segments sur la base d'un numéro de compartiment aléatoire (par exemple, créez un segment dans lequel le numéro de compartiment aléatoire est inférieur à 1 000 ou compris entre 1 000 et 2 000).
+
+Dans l’un ou l’autre scénario, vous pouvez éventuellement fournir un `callback_endpoint` à notifier lorsque l’exportation est prête. Si le `callback_endpoint` est fourni, nous ferons une demande Post à l’adresse indiquée lorsque le téléchargement sera prêt. Le corps du Post sera "success":true. Si vous n’avez pas ajouté d’informations d’identification S3 à Braze, le corps du Post contiendra également l’attribut `url` avec l’URL de téléchargement comme valeur.
+
+Les bases d’utilisateurs plus grandes entraîneront des temps d’exportation plus longs. Par exemple, une application avec 20 millions d’utilisateurs peut prendre une heure ou plus.
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "segment_id" : (required, string) identifier for the segment to be exported,
+  "callback_endpoint" : (optional, string) endpoint to post a download URL when the export is available,
+  "fields_to_export" : (required, array of string) name of user data fields to export, you may also export custom attributes. New accounts must specify specific fields to export,
+  "output_format" : (optional, string) when using your own S3 bucket,  specifies file format as 'zip' or 'gzip'. Defaults to ZIP file format
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+|`segment_id` | Requis | Chaîne de caractères | Identifiant du segment à exporter. Voir [identifiant de segmentation]({{site.baseurl}}/api/identifier_types/).<br><br>Vous trouverez le site `segment_id` pour un segment donné sur la page des [clés API de]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) votre compte Braze ou vous pouvez utiliser l'[endpoint de la liste des segments]({{site.baseurl}}/api/endpoints/export/segments/get_segment/).|
+|`callback_endpoint` | Facultatif | Chaîne de caractères | Endpoint auquel publier une URL de téléchargement lorsque l’exportation est disponible. |
+|`fields_to_export` | Obligatoire* | Tableau de chaînes de caractères | Nom des champs de données utilisateur à exporter. Vous pouvez également exporter tous les attributs personnalisés en incluant `custom_attributes` dans ce paramètre. <br><br>\*À partir d’avril 2021, les nouveaux comptes doivent préciser des champs spécifiques à exporter. |
+| `custom_attributes_to_export` | Facultatif | Tableau de chaînes de caractères | Nom de l'attribut personnalisé spécifique à exporter. Il est possible d'exporter jusqu'à 500 attributs personnalisés. Pour créer et gérer des attributs personnalisés dans le tableau de bord, allez dans **Paramètres des données** > Attributs personnalisés. |
+|`output_format` | Facultatif | Chaîne de caractères | Le format de sortie de votre fichier. Format de fichier `zip` par défaut. Si vous utilisez votre propre compartiment S3, vous pouvez spécifier `zip` ou `gzip`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+{% alert note %}
+Si `custom_attributes` est inclus dans le paramètre `fields_to_export`, tous les attributs personnalisés sont exportés, quel que soit le contenu de `custom_attributes_to_export`. Si votre objectif est d’exporter des attributs spécifiques, `custom_attributes` ne doit pas être inclus dans le paramètre `fields_to_export`. Utilisez plutôt le paramètre `custom_attributes_to_export`.
+{% endalert %}
+
+## Exemple de demande d'exportation de tous les attributs personnalisés
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/export/segment' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "segment_id" : "segment_identifier",
+  "callback_endpoint" : "example_endpoint",
+  "fields_to_export" : ["first_name", "email", "purchases", "custom_attributes"],
+  "output_format" : "zip"
+}'
+```
+
+## Exemple de demande d'exportation d'attributs personnalisés spécifiques
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/export/segment' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "segment_id" : "segment_identifier",
+  "callback_endpoint" : "example_endpoint",
+  "fields_to_export" : ["first_name", "email", "purchases"],
+  "custom_attributes_to_export" : ["allergies", "favorite_food"],
+  "output_format" : "zip"
+}'
+```
+
+## Champs à exporter
+
+Voici une liste des `fields_to_export` valides. L'utilisation de `fields_to_export` pour minimiser les données renvoyées peut améliorer le temps de réponse de ce point de terminaison de l'API :
+
+| Champ à exporter | Type de données | Description |
+|---|---|---|
+| `apps` | Tableau | Les applications pour lesquelles l’utilisateur a enregistré des sessions, ce qui comprend les champs :<br><br>- `name` : nom de l’application<br>- `platform` : plateforme de l’application telle qu’iOS, Android ou Web<br>- `version` : numéro ou nom de version de l’application <br>- `sessions` : nombre total de sessions pour cette application<br>- `first_used` : date de la première session<br>- `last_used` : date de la dernière session<br><br>Tous les champs sont des chaînes de caractères. |
+| `attributed_campaign` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant d’une campagne donnée. |
+| `attributed_source` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant de la plateforme sur laquelle était l’annonce. |
+| `attributed_adgroup` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant pour un sous-groupe optionnel sous la campagne. |
+| `attributed_ad` | Chaîne de caractères | Données provenant des [intégrations d'attribution]({{site.baseurl}}/partners/message_orchestration/attribution), si elles sont configurées. Identifiant d'un sous-groupement facultatif en dessous de la campagne et du groupe d'annonces. |
+| `braze_id` | Chaîne de caractères | Identifiant utilisateur unique spécifique à l’appareil défini par Braze pour cet utilisateur. |
+| `country` | Chaîne de caractères | Pays de l'utilisateur selon la norme [ISO 3166-1 alpha-2.](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)  |
+| `created_at` | Chaîne de caractères | Date et heure de la création du profil utilisateur au format ISO 8601. |
+| `custom_attributes` | Objet | Paires clé-valeur de l’attribut personnalisé de cet utilisateur. |
+| `custom_events` | Tableau | Événements personnalisés attribués à cet utilisateur dans les 90 derniers jours. |
+| `devices` | Tableau | Informations sur l’appareil de l’utilisateur qui devraient contenir les éléments suivants selon la plateforme :<br><br>- `model` : Nom du modèle de l’appareil<br>- `os` : Système d’exploitation de l’appareil<br>- `carrier` : Fournisseur de services de l’appareil, si disponible<br>- `idfv`: (iOS) Identifiant de l'appareil Braze, l'identifiant Apple pour le vendeur, s'il existe.<br>- `idfa` : (iOS) Identifiant publicitaire, s’il existe<br>- `device_id` : (Android) Identifiant de l’appareil Braze<br>- `google_ad_id` : (Android) Identifiant publicitaire Google Play, s’il existe<br>- `roku_ad_id` : (Roku) Identifiant publicitaire Roku<br>- `ad_tracking_enabled` : Si le suivi des annonces est activé sur l’appareil, peut être vrai ou faux |
+| `dob` | Chaîne de caractères | Date de naissance de l’utilisateur au format `YYYY-MM-DD`. |
+| `email` | Chaîne de caractères | Adresse e-mail de l’utilisateur. |
+| `external_id` | Chaîne de caractères | Identifiant utilisateur unique pour les utilisateurs identifiés. |
+| `first_name` | Chaîne de caractères | Prénom de l’utilisateur. |
+| `gender` | Chaîne de caractères | Genre de l’utilisateur. Les valeurs possibles sont :<br><br>- `M` : masculin<br>- `F` : féminin<br>- `O` : autre<br>- `N` : sans objet<br>- `P` : préfère ne pas répondre<br>- `nil` : inconnu |
+| `home_city` | Chaîne de caractères | Ville de résidence de l’utilisateur. |
+| `language` | Chaîne de caractères | Langue de l’utilisateur à la norme ISO-639-1. |
+| `last_coordinates` | Tableau de floats | Dernier emplacement de l’appareil de l’utilisateur, au format `[longitude, latitude]`. |
+| `last_name` | Chaîne de caractères | Nom de famille de l’utilisateur. |
+| `phone` | Chaîne de caractères | Numéro de téléphone de l'utilisateur au format E.164. |
+| `purchases` | Tableau | Achats réalisés par cet utilisateur au cours des 90 derniers jours. |
+| `push_tokens` | Tableau | Informations sur les jetons de poussée de l'utilisateur. |
+| `random_bucket` | Entier | [Numéro de compartiment aléatoire]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events#random-bucket-number-event) de l'utilisateur, utilisé pour créer des segments uniformément distribués d'utilisateurs aléatoires. |
+| `time_zone` | Chaîne de caractères | Fuseau horaire de l’utilisateur au même format que la base de données de fuseaux horaires IANA. |
+| `total_revenue` | Float | Revenus totaux attribués à cet utilisateur. Les revenus totaux sont calculés à partir des achats réalisés par l’utilisateur pendant la fenêtre de conversion pour les campagnes et les Canvas qu’il a reçus. |
+| `uninstalled_at` | Date/heure | Date et heure de désinstallation de l’application par l’utilisateur. Absent si l’application n’a pas été désinstallée. |
+| `user_aliases` | Objet | [Objet aliasing de l'utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object#user-alias-object-specification) contenant les adresses `alias_name` et `alias_label`, si elles existent. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+## Rappels importants
+
+- Les champs pour `custom_events`, `purchases`, `campaigns_received`, et `canvases_received` contiennent uniquement les données des 90 derniers jours.
+- `custom_events` et `purchases` contiennent tous les deux des champs pour `first` et `count`. Ces deux champs reflèteront les informations de tout le temps et ne seront pas limités aux données des 90 derniers jours. Par exemple, si un utilisateur particulier a effectué l'événement pour la première fois il y a 90 jours, cela sera reflété avec précision dans le champ `first`, et le champ `count` prendra également en compte les événements qui se sont produits avant les 90 derniers jours.
+- Le nombre d’exportations de segments simultanées qu’une entreprise peut exécuter au niveau de l’endpoint est plafonné à 100. Les tentatives qui dépassent cette limite entraîneront une erreur.
+- Si vous tentez d’exporter un segment une deuxième fois alors que la première tâche d’exportation est toujours en cours d’exécution, une erreur 429 s’affiche.
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "message": (required, string) the status of the export, returns 'success' when completed without errors,
+    "object_prefix": (required, string) the filename prefix that will be used for the JSON file produced by this export, for example, 'bb8e2a91-c4aa-478b-b3f2-a4ee91731ad1-1464728599',
+    "url" : (optional, string) the URL where the segment export data can be downloaded if you do not have your own S3 credentials
+}
+```
+
+Après la mise à disposition de l'URL, celle-ci n'est valable que pour quelques heures. Par conséquent, nous vous recommandons fortement d’ajouter vos propres informations d’identification S3 dans Braze.
+
+## Exemple de sortie d'un fichier d'exportation utilisateur
+
+Objet Exportation utilisateur (nous inclurons le moins de données possible. S’il manque un champ de l’objet, il doit être considéré comme nul, faux ou vide) :
+
+{% tabs %}
+{% tab Tous les domaines %}
+
+```json
+{
+    "created_at": (string),
+    "external_id" : (string),
+    "user_aliases" : [
+      {
+        "alias_name" : (string),
+        "alias_label" : (string)
+      }
+    ],
+    "braze_id": (string),
+    "first_name" : (string),
+    "last_name" : (string),
+    "email" : (string),
+    "dob" : (string) date for the user's date of birth,
+    "home_city" : (string),
+    "country" : (string) ISO-3166-1 alpha-2 standard,
+    "phone" : (string),
+    "language" : (string) ISO-639-1 standard,
+    "time_zone" : (string),
+    "last_coordinates" : (array of float) [lon, lat],
+    "gender" : (string) "M" | "F",
+    "total_revenue" : (float),
+    "attributed_campaign" : (string),
+    "attributed_source" : (string),
+    "attributed_adgroup" : (string),
+    "attributed_ad" : (string),
+    "push_subscribe" : (string) "opted_in" | "subscribed" | "unsubscribed",
+    "email_subscribe" : (string) "opted_in" | "subscribed" | "unsubscribed",
+    "custom_attributes" : (object) custom attribute key-value pairs,
+    "custom_events" : [
+      {
+        "name" : (string),
+        "first" : (string) date,
+        "last" : (string) date,
+        "count" : (int)
+      },
+      ...
+    ],
+    "purchases" : [
+      {
+        "name" : (string),
+        "first" : (string) date,
+        "last" : (string) date,
+        "count" : (int)
+      },
+      ...
+    ],
+    "devices" : [
+      {
+        "model" : (string),
+        "os" : (string),
+        "carrier" : (string),
+        "idfv" : (string) only included for iOS devices when IDFV collection is enabled,
+        "idfa" : (string) only included for iOS devices when IDFA collection is enabled,
+        "google_ad_id" : (string) only included for Android devices when Google Play Advertising Identifier collection is enabled,
+        "roku_ad_id" : (string) only included for Roku devices,
+        "ad_tracking_enabled" : (bool)
+      },
+      ...
+    ],
+    "push_tokens" : [
+      {
+        "app" : (string) app name,
+        "platform" : (string),
+        "token" : (string)
+      },
+      ...
+    ],
+    "apps" : [
+      {
+        "name" : (string),
+        "platform" : (string),
+        "version" : (string),
+        "sessions" : (integer),
+        "first_used" : (string) date,
+        "last_used" : (string) date
+      },
+      ...
+    ],
+    "campaigns_received" : [
+      {
+        "name" : (string),
+        "last_received" : (string) date,
+        "engaged" : 
+         {
+           "opened_email" : (bool),
+           "opened_push" : (bool),
+           "clicked_email" : (bool),
+           "clicked_triggered_in_app_message" : (bool)
+          },
+          "converted" : (bool),
+          "api_campaign_id" : (string),
+          "variation_name" : (optional, string) exists only if it is a multivariate campaign,
+          "variation_api_id" : (optional, string) exists only if it is a multivariate campaign,
+          "in_control" : (optional, bool) exists only if it is a multivariate campaign
+        },
+      ...
+    ],
+    "canvases_received": [
+      {
+        "name": (string),
+        "api_canvas_id": (string),
+        "last_received_message": (string) date,
+        "last_entered": (string) date,
+        "variation_name": (string),
+        "in_control": (bool),
+        "last_exited": (string) date,
+        "steps_received": [
+          {
+            "name": (string),
+            "api_canvas_step_id": (string),
+            "last_received": (string) date
+          },
+          {
+            "name": (string),
+            "api_canvas_step_id": (string),
+            "last_received": (string) date
+          },
+          {
+            "name": (string),
+            "api_canvas_step_id": (string),
+            "last_received": (string) date
+          }
+        ]
+      },
+      ...
+    ],
+    "cards_clicked" : [
+      {
+        "name" : (string)
+      },
+      ...
+    ]
+}
+```
+
+{% endtab %}
+{% tab Exemple de sortie %}
+
+```json
+{
+    "created_at" : "2020-07-10 15:00:00.000 UTC",
+    "external_id" : "A8i3mkd99",
+    "user_aliases" : [
+      {
+        "alias_name" : "user_123",
+        "alias_label" : "amplitude_id"
+      }
+    ],
+    "braze_id": "5fbd99bac125ca40511f2cb1",
+    "random_bucket" : 2365,
+    "first_name" : "Jane",
+    "last_name" : "Doe",
+    "email" : "example@braze.com",
+    "dob" : "1980-12-21",
+    "home_city" : "Chicago",
+    "country" : "US",
+    "phone" : "+442071838750",
+    "language" : "en",
+    "time_zone" : "Eastern Time (US & Canada)",
+    "last_coordinates" : [41.84157636433568, -87.83520818508256],
+    "gender" : "F",
+    "total_revenue" : 65,
+    "attributed_campaign" : "braze_test_campaign_072219",
+    "attributed_source" : "braze_test_source_072219",
+    "attributed_adgroup" : "braze_test_adgroup_072219",
+    "attributed_ad" : "braze_test_ad_072219",
+    "push_subscribe" : "opted_in", 
+    "push_opted_in_at": "2020-01-26T22:45:53.953Z",
+    "email_subscribe" : "subscribed",
+    "custom_attributes": 
+    {
+      "loyaltyId": "37c98b9d-9a7f-4b2f-a125-d873c5152856",
+      "loyaltyPoints": "321",
+       "loyaltyPointsNumber": 107
+    },
+    "custom_events": [
+      {
+        "name": "Loyalty Acknowledgement",
+        "first": "2021-06-28T17:02:43.032Z",
+        "last": "2021-06-28T17:02:43.032Z",
+        "count": 1
+      },
+      ...
+    ],
+    "purchases": [
+      {
+        "name": "item_40834",
+        "first": "2021-09-05T03:45:50.540Z",
+        "last": "2022-06-03T17:30:41.201Z",
+        "count": 10
+      },
+      ...
+    ],
+    "devices": [
+      {
+        "model": "Pixel XL",
+        "os": "Android (Q)",
+        "carrier": null,
+        "device_id": "312ef2c1-83db-4789-967-554545a1bf7a",
+        "ad_tracking_enabled": true
+      },
+      ...
+    ],
+    "push_tokens": [
+      {
+        "app": "MovieCanon",
+        "platform": "Android",
+        "token": "12345abcd",
+        "device_id": "312ef2c1-83db-4789-967-554545a1bf7a",
+        "notifications_enabled": true
+      },
+      ...
+    ],
+    "apps": [
+      {
+        "name": "MovieCannon",
+        "platform": "Android",
+        "version": "3.29.0",
+        "sessions": 1129,
+        "first_used": "2020-02-02T19:56:19.142Z",
+        "last_used": "2021-11-11T00:25:19.201Z"
+      },
+      ...
+    ],
+    "campaigns_received": [
+      {
+        "name": "Email Unsubscribe",
+        "api_campaign_id": "d72fdc84-ddda-44f1-a0d5-0e79f47ef942",
+        "last_received": "2022-06-02T03:07:38.105Z",
+        "engaged": 
+        {
+           "opened_email": true
+        },
+        "converted": true,
+        "multiple_converted": 
+        {
+          "Primary Conversion Event - A": true
+        },
+        "in_control": false,
+        "variation_name": "Variant 1",
+        "variation_api_id": "1bddc73a-a134-4784-9134-5b5574a9e0b8"
+      },
+      ...
+    ],
+    "canvases_received": [
+      {
+        "name": "Non Global  Holdout Group 4/21/21",
+        "api_canvas_id": "46972a9d-dc81-473f-aa03-e3473b4ed781",
+        "last_received_message": "2021-07-07T20:46:24.136Z",
+        "last_entered": "2021-07-07T20:45:24.000+00:00",
+        "variation_name": "Variant 1",
+        "in_control": false,
+        "last_entered_control_at": null,
+        "last_exited": "2021-07-07T20:46:24.136Z",
+        "steps_received": [
+          {
+            "name": "Step",
+            "api_canvas_step_id": "43d1a349-c3c8-4be1-9fbe-ce708e4d1c39",
+            "last_received": "2021-07-07T20:46:24.136Z"
+          },
+          ...
+        ]
+      }
+      ...
+    ],    
+    "cards_clicked" : [
+      {
+        "name" : "Loyalty Promo"
+      },
+      ...
+    ]
+}
+```
+
+{% endtab %}
+{% endtabs %}
+
+{% alert tip %}
+Pour obtenir de l’aide sur les exportations CSV et de l’API, consultez la section [Résolution des problèmes d’exportation]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/).
+{% endalert %}
+
+[1]: {{site.baseurl}}/partners/data_and_infrastructure_agility/cloud_storage/amazon_s3
+[2]: {{site.baseurl}}/partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents/
+[3]: {{site.baseurl}}/partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents/
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging.md b/_lang/fr_fr/_api/endpoints/messaging.md
new file mode 100644
index 00000000000..066167dcd9a
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging.md
@@ -0,0 +1,83 @@
+---
+nav_title: Messages
+article_title: Endpoints de messagerie
+search_tag: Endpoint
+page_order: 3
+local_redirect: #app-group-rest-api-key #app-identifier #external-user-id #segment-identifier #campaign-identifier #canvas-identifier #trigger-properties #canvas-identifier #server-responses #fatal-errors #responses-for-tracked-send-ids #messaging-queued #canvas-entry-properties
+  app-group-rest-api-key: '/docs/api/basics/#rest-api-key'
+  app-identifier: '/docs/api/identifier_types/'
+  external-user-id: '/docs/api/objects_filters/user_attributes_object/#braze-user-profile-fields'
+  segment-identifier: '/docs/api/identifier_types/'
+  campaign-identifier: '/docs/api/identifier_types/'
+  canvas-identifier: '/docs/api/identifier_types/'
+  send-identifier: '/docs/api/identifier_types/'
+  trigger-properties: '/docs/api/objects_filters/trigger_properties_object'
+  canvas-entry-properties: '/docs/api/objects_filters/canvas_entry_properties_object'
+  server-responses: '/docs/api/errors/'
+  messaging-queued: '/docs/api/errors/'
+  responses-for-tracked-send-ids: '/docs/api/errors/'
+  fatal-errors: '/docs/api/errors/'
+
+layout: dev_guide
+
+#Required
+description: "Cette page d’accueil liste les endpoints Braze d’envoi de messages."
+page_type: landing
+
+guide_top_header: "Endpoints de messagerie"
+guide_top_text: "L’API de messagerie Braze vous offre deux options pour envoyer des messages à vos utilisateurs. Vous pouvez fournir le contenu et la configuration du message dans la demande d'API à l'aide de l'attribut <code class='highlighter-rouge'>/messages/send</code> et les endpoints `/messages/schedule`. Vous pouvez également gérer les détails de votre message avec une campagne déclenchée par l'API dans le tableau de bord de Braze et contrôler simplement quand et à qui il est envoyé avec les endpoints `/campaigns/trigger/send` et `/campaigns/trigger/schedule`. Les sections suivantes détaillent la spécification de demande pour les deux méthodes. <br> <br> De la même manière que pour les autres campagnes, vous pouvez limiter le nombre de fois qu'un utilisateur donné peut recevoir une campagne API de messages en configurant les [paramètres de rééligibilité](/docs/user_guide/engagement_tools/campagnes/building_campaigns/delivery_types/api_triggered_delivery/#re-eligibility-with-api-triggered-campaigns) dans le tableau de bord de Braze. Braze ne livrera pas de messages API aux utilisateurs qui ne sont pas rééligibles pour la campagne, quel que soit le nombre de demandes API envoyées. <br> <br> Les endpoints d'envoi de messages vous permettent d'envoyer des messages immédiats à des utilisateurs désignés. Si vous ciblez un segmentation, un enregistrement de votre demande sera stocké dans le **Journal d'activité des messages**. Utilisez les endpoints Schedule Message pour envoyer des messages à une heure donnée, et pour modifier ou annuler des messages que vous avez déjà planifiés."
+
+guide_featured_title: "Points d'extrémité des messages de planification"
+guide_featured_list:
+  - name: "GET : Répertorier les campagnes et Canvas planifiés à venir"
+    link: /docs/api/endpoints/messaging/schedule_messages/get_messages_scheduled/
+    image: /assets/img/braze_icons/calendar-date.svg
+  - name: "POST : Supprimer les messages planifiés"
+    link: /docs/api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages/
+    image: /assets/img/braze_icons/calendar-minus-01.svg
+  - name: "POST : Supprimer des campagnes planifiées déclenchées par API"
+    link: /docs/api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages/
+    image: /assets/img/braze_icons/calendar-minus-01.svg
+  - name: "POST : Supprimer des Canvas planifiés déclenchés par API"
+    link: /docs/api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases/
+    image: /assets/img/braze_icons/calendar-minus-01.svg
+  - name: "POST : Planifier les messages"
+    link: /docs/api/endpoints/messaging/schedule_messages/post_schedule_messages/
+    image: /assets/img/braze_icons/calendar-plus-01.svg
+  - name: "POST : Planifier des messages de campagne déclenchés par API"
+    link: /docs/api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: "POST : Planifier des messages Canvas déclenchés par API"
+    link: /docs/api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: "POST : Mettre à jour les messages planifiés"
+    link: /docs/api/endpoints/messaging/schedule_messages/post_update_scheduled_messages/
+    image: /assets/img/braze_icons/calendar-date.svg
+  - name: "POST : Mettre à jour les messages de campagnes planifiés déclenchés par API"
+    link: /docs/api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns/
+    image: /assets/img/braze_icons/calendar-date.svg
+  - name: "POST : Mettre à jour des messages Canvas planifiés déclenchés par API"
+    link: /docs/api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+
+guide_menu_title: "Send messages endpoints"
+guide_menu_list:
+  - name: "POST : Créer des ID d’envoi"
+    link: /docs/api/endpoints/messaging/send_messages/post_create_send_ids/
+    image: /assets/img/braze_icons/user-square.svg
+  - name: "POST : Envoyer les messages immédiatement"
+    link: /docs/api/endpoints/messaging/send_messages/post_send_messages/
+    image: /assets/img/braze_icons/send-01.svg
+  - name: "POST : Envoyer immédiatement les messages de campagnes déclenchés par API"
+    link: /docs/api/endpoints/messaging/send_messages/post_send_triggered_campaigns/
+    image: /assets/img/braze_icons/inbox-01.svg
+  - name: "POST : Envoyer immédiatement les messages Canvas déclenchés par API"
+    link: /docs/api/endpoints/messaging/send_messages/post_send_triggered_canvases/
+    image: /assets/img/braze_icons/inbox-01.svg
+
+guide_menu_title2: "Live Activity endpoints"
+guide_menu_list2:
+  - name: "POST : Mettre à jour l’activité en direct"
+    link: /docs/api/endpoints/messaging/live_activity/update/
+    image: /assets/img/braze_icons/tablet-01.svg
+---
diff --git a/_lang/fr_fr/_api/endpoints/messaging/duplicate_campaigns.md b/_lang/fr_fr/_api/endpoints/messaging/duplicate_campaigns.md
new file mode 100644
index 00000000000..29a41d5a918
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/duplicate_campaigns.md
@@ -0,0 +1,65 @@
+---
+nav_title: "POST : Campagnes en double"
+article_title: "POST : Campagnes en double"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Dupliquer des campagnes."
+
+---
+{% api %}
+# Dupliquer des campagnes via l'API
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/campagnes/duplicate
+{% endapimethod %}
+
+> Utilisez cet endpoint pour dupliquer des campagnes. Cet endpoint de l'API est similaire à la [duplication des campagnes dans le tableau de bord de Braze][1].
+
+{% alert important %}
+La duplication d'une campagne via l'API est actuellement en accès anticipé. Contactez votre gestionnaire de compte Braze si vous souhaitez participer à l’accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous devrez générer une clé API avec l’autorisation `campaigns.duplicate`.
+
+## Limite de débit
+
+Ce point d'accès est limité à 100 appels d’API par minute.
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "campaign_id": (required, string) The campaign identifier,
+  "name": (required, string) The name of the resulting campaign,
+  "description": (optional, string) The description of the resulting campaign,
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`campaign_id`| Requis | Chaîne de caractères | Voir [identifiant de campagne]({{site.baseurl}}/api/identifier_types/). |
+|`name`| Requis | Chaîne de caractères | Le nom de la campagne résultante. |
+|`description`| Facultatif | Chaîne de caractères | Le champ de description de la campagne résultante. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+
+## Réponse
+
+Cet endpoint renverra un code de statut `202` et la création de la campagne se fera de manière asynchrone. Vous pouvez utiliser le [téléchargement d'événements de sécurité][2] pour consulter les enregistrements relatifs à la duplication des campagnes et à la clé API utilisée.
+
+
+
+[1]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/duplicating_segments_and_campaigns#duplicating-segments-campaigns-and-canvases
+[2]: {{site.baseurl}}/user_guide/administrative/app_settings/company_settings/security_settings/?redirected=true#security-event-download
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/live_activity.md b/_lang/fr_fr/_api/endpoints/messaging/live_activity.md
new file mode 100644
index 00000000000..7c8a1915846
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/live_activity.md
@@ -0,0 +1,5 @@
+---
+nav_title: Activité en direct
+config_only: true
+noindex: true
+---
diff --git a/_lang/fr_fr/_api/endpoints/messaging/live_activity/start.md b/_lang/fr_fr/_api/endpoints/messaging/live_activity/start.md
new file mode 100644
index 00000000000..422131d2f39
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/live_activity/start.md
@@ -0,0 +1,130 @@
+---
+nav_title: "POST : Démarrer une ligne/en production/instantanée"
+article_title: "POST : Démarrer une ligne/en production/instantanée"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente les détails de l'endpoint Démarrer une ligne/en production/instantané."
+
+---
+{% api %}
+# Démarrer une ligne/en production/instantanée
+{% apimethod post %}
+/messages/live_activity/start
+{% endapimethod %}
+
+> Utilisez cet endpoint pour démarrer à distance les [activités en direct]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/) affichées dans votre app iOS. Cet endpoint nécessite une configuration supplémentaire.
+
+Après avoir créé une activité en direct, vous pouvez effectuer une requête POST pour démarrer à distance votre activité pour n'importe quel segment/instantané. Pour en savoir plus sur les activités en direct d'Apple, consultez [Démarrage et mise à jour des activités en direct avec les notifications push d'ActivityKit.](https://developer.apple.com/documentation/activitykit/starting-and-updating-live-activities-with-activitykit-push-notifications)
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#2300226e-f26a-4154-9bcc-5883f1f294cd {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous devrez effectuer les opérations suivantes :
+
+- Générez une clé API avec l’autorisation `messages.live_activity.start`.
+- [Créez une activité en direct]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/#step-1-create-a-live-activity) à l’aide du SDK Braze Swift.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```json
+{
+  "app_id": "(required, string) App API identifier retrieved from the Developer Console.",
+  "activity_id": "(required, string) Define a custom string as your `activity_id`. You will use this ID when you wish to send update or end events to your Live Activity.",
+  "activity_attributes_type": "(required, string) The activity attributes type you define within `liveActivities.registerPushToStart` in your app",
+  "activity_attributes": "(required, object) The static attribute values for the activity type (such as the sports team names, which don't change)",
+  "content_state": "(required, object) You define the ContentState parameters when you create your Live Activity. Pass the updated values for your ContentState using this object. The format of this request must match the shape you initially defined.",
+  "dismissal_date": "(optional, datetime in ISO-8601 format) The time to remove the Live Activity from the user’s UI. If this time is in the past, the Live Activity will be removed immediately.",
+  "stale_date": "(optional, datetime in ISO-8601 format) The time the Live Activity content is marked as outdated in the user’s UI.",
+  "notification": "(required, object) Include an `apple_push` object to define a push notification that creates an alert for the user, displayed on paired watchOS devices. Should include `notification.alert.title` and `notification.alert.body`",
+  // One of the following:
+  "external_user_ids": "(optional, array of strings) see external user identifier",
+  "custom_audience": "(optional, connected audience object) see connected audience",
+  "segment_id": "(optional, string) see segment identifier"
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données| Description  |
+|-----------|----------|----------|--------------|
+| `app_id` | Requis | Chaîne de caractères | [Identifiant de l'API]({{site.baseurl}}/api/identifier_types/#the-app-identifier) de l [']({{site.baseurl}}/api/identifier_types/#the-app-identifier) application récupéré à partir de la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/).  |
+| `activity_id` | Requis | Chaîne de caractères  | Définissez une chaîne de caractères personnalisée comme votre `activity_id`. Vous utiliserez cet ID lorsque vous souhaiterez envoyer des événements de mise à jour ou de fin à votre ligne/en production/instantanée.  |
+| `activity_attributes_type`  | Requis | Chaîne de caractères | Le type d'attributs d'activité que vous définissez à l'adresse `liveActivities.registerPushToStart` dans votre application.  |
+| `activity_attributes` | Requis | Objet  | Les valeurs d'attributs statiques pour le type d'activité (comme les noms des équipes sportives, qui ne changent pas). |
+| `content_state` | Requis | Objet  | Vous définissez les paramètres `ContentState` lorsque vous créez votre activité en direct. Transmettez les valeurs mises à jour pour votre `ContentState` en utilisant cet objet.<br><br>Le format de cette requête doit correspondre à la forme que vous avez initialement définie. |
+| `dismissal_date` | Facultatif | DateTime <br>([](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Ce paramètre définit le moment de suppression de l’activité en direct de l’interface utilisateur. |
+| `stale_date` | Facultatif | DateTime <br>([](https://en.wikipedia.org/wiki/ISO_8601) chaîne de caractères[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ) | Ce paramètre indique au système quand le contenu de l’activité en direct devient obsolète dans l’interface utilisateur. |
+| `notification` | Requis | Objet | Incluez un objet [`apple_push`]({{site.baseurl}}/api/objects_filters/messaging/apple_object/) pour définir une notification push. Le comportement de cette notification push dépend du fait que l’utilisateur soit actif ou utilise un appareil proxy. {::nomarkdown}<ul><li>Si un <code>notification</code> est inclus et que l’utilisateur est actif sur son iPhone lorsque la mise à jour est livrée, l’interface utilisateur de l’activité en direct mise à jour glissera vers le bas et s’affichera comme une notification push.</li><li>Si un <code>notification</code> est inclus et que l’utilisateur n’est pas actif sur son iPhone, son écran s’allume pour afficher l’interface utilisateur de l’activité en direct mise à jour sur son écran de verrouillage.</li><li>Le paramètre <code>notification alert</code> ne s’affichera pas comme une notification push standard. De plus, si un utilisateur dispose d’un appareil proxy, comme une Apple Watch, le <code>alert</code> s’affichera ici.</li></ul>{:/} |
+| `external_user_ids` | Facultatif si `segment_id` ou `audience` est fourni | Tableau de chaînes de caractères | Voir [ID externe]({{site.baseurl}}/api/objects_filters/user_attributes_object/#braze-user-profile-fields).  |
+| `segment_id `  | Facultatif si `external_user_ids` ou `audience` est fourni | Chaîne de caractères    | Voir [identifiant de segmentation]({{site.baseurl}}/api/identifier_types/). |
+| `custom_audience` | Facultatif si `external_user_ids` ou `segment_id` est fourni | Objet Audience connectée  | Voir [audience connectée]({{site.baseurl}}/api/objects_filters/connected_audience/). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/messages/live_activity/start' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer {YOUR-REST-API-KEY}' \
+--data-raw '{
+    "app_id": "{YOUR-APP-API-IDENTIFIER}",
+    "activity_id": "football-chiefs-bills-2024-01-21",
+    "content_state": {
+        "teamOneScore": 0,
+        "teamTwoScore": 0
+    },
+    "activity_attributes_type": "FootballActivity",
+    "activity_attributes": {
+        "team1Name": "Chiefs",
+        "team2Name": "Bills"
+    },
+    "dismissal_date": "2024-01-22T00:00:00+0000",
+    "stale_date": "2024-01-22T16:55:49+0000",
+    "notification": {
+        "alert": {
+            "body": "The game is starting! Tune in soon!",
+            "title": "Chiefs v. Bills"
+        }
+    },
+    // One of the following required:
+    "segment_id": "{YOUR-SEGMENT-API-IDENTIFIER}", // Optional
+    "custom_audience": {...}, // Optional
+    "external_user_ids": ["user-id1", "user-id2"], // Optional
+}'
+```
+
+## Réponse
+
+Deux réponses de code de statut existent pour cet endpoint : `201` et `4XX`.
+
+### Exemple de réponse réussie
+
+Un code de statut `201` est renvoyé si la requête a été formatée correctement et que nous l’avons reçue. Le code de statut `201` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+La classe du code de statut `4XX` indique une erreur client. Reportez-vous à l'[article sur les erreurs et réponses de l'API]({{site.baseurl}}/api/errors/) pour plus d'informations sur les erreurs que vous pouvez rencontrer.
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. 
+
+```json
+{
+    "error": "\nProblem:\n  message body does not match declared format\nResolution:\n  when specifying application/json as content-type, you must pass valid application/json in the request's 'body' "
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/live_activity/update.md b/_lang/fr_fr/_api/endpoints/messaging/live_activity/update.md
new file mode 100644
index 00000000000..b5d3752607c
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/live_activity/update.md
@@ -0,0 +1,113 @@
+---
+nav_title: "POST : Mettre à jour l’activité en direct"
+article_title: "POST : Mettre à jour l’activité en direct"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Mettre à jour l’activité en direct."
+
+---
+{% api %}
+# Mettre à jour l’activité en direct
+{% apimethod post %}
+/messages/live_activity/update
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour et terminer les [activités en direct]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/) affichées par votre application iOS. Cet endpoint nécessite une configuration supplémentaire.
+
+Après avoir enregistré une activité en direct, vous pouvez passer une charge utile JSON pour mettre à jour votre service de notification push Apple (APNs). Consultez la documentation d'Apple sur [la mise à jour de votre activité en direct avec des charges utiles de notification push](https://developer.apple.com/documentation/activitykit/updating-and-ending-your-live-activity-with-activitykit-push-notifications) pour plus d'informations.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#2300226e-f26a-4154-9bcc-5883f1f294cd {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous devrez effectuer les opérations suivantes :
+
+- Générez une clé API avec l’autorisation `messages.live_activity.update`.
+- Enregistrez une activité en direct [à distance]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/?tab=remote#step-2-start-the-activity) ou [localement]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/?tab=local#step-2-start-the-activity) à l'aide du SDK Braze Swift.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```json
+{
+   "app_id": "(required, string) App API identifier retrieved from the Developer Console.",
+   "activity_id": "(required, string) When you register your Live Activity using launchActivity, you use the pushTokenTag parameter to name the Activity’s push token to a custom string. Set activity_id to this custom string to define which Live Activity you want to update.",
+   "content_state": "(required, object) You define the ContentState parameters when you create your Live Activity. Pass the updated values for your ContentState using this object. The format of this request must match the shape you initially defined.",
+   "end_activity": "(optional, boolean) If true, this request ends the Live Activity.",
+   "dismissal_date": "(optional, datetime in ISO-8601 format) The time to remove the Live Activity from the user’s UI. If this time is in the past, the Live Activity will be removed immediately.",
+   "stale_date": "(optional, datetime in ISO-8601 format) The time the Live Activity content is marked as outdated in the user’s UI.",
+   "notification": "(optional, object ) Include an `apple_push` object to define a push notification that creates an alert for the user."
+ }
+ ```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `app_id` | Requis | Chaîne de caractères | Identifiant [API]({{site.baseurl}}/api/identifier_types/#the-app-identifier) récupéré depuis la page [Clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/).  |
+| `activity_id` | Requis | Chaîne de caractères | Lorsque vous enregistrez votre Activité en direct en utilisant [`launchActivity`](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/liveactivities-swift.class), vous utilisez le paramètre `pushTokenTag` pour nommer le jeton push de l'Activité avec une chaîne personnalisée.<br><br>Définissez l’`activity_id` vers cette chaîne de caractères personnalisée pour définir l’activité en direct que vous souhaitez mettre à jour. |
+| `content_state` | Requis | Objet | Vous définissez les paramètres `ContentState` lorsque vous créez votre activité en direct. Transmettez les valeurs mises à jour pour votre `ContentState` en utilisant cet objet.<br><br>Le format de cette requête doit correspondre à la forme que vous avez initialement définie. |
+| `end_activity` | Facultatif | Valeur booléenne | Si `true`, cette requête met fin à l’activité en direct. |
+| `dismissal_date` | Facultatif | DateTime <br>chaîne ([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)) | Ce paramètre définit le moment de suppression de l’activité en direct de l’interface utilisateur. Si cette heure est dans le passé et `end_activity` est `true`, l'Activité en direct sera supprimée immédiatement.<br><br> Si `end_activity` est `false` ou omis, ce paramètre met uniquement à jour l'Activité en direct.|
+| `stale_date` | Facultatif | DateTime <br>chaîne ([ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)) | Ce paramètre indique au système quand le contenu de l’activité en direct devient obsolète dans l’interface utilisateur. |
+| `notification` | Facultatif | Objet | Inclure un [`apple_push`]({{site.baseurl}}/api/objects_filters/messaging/apple_object/) objet pour définir une notification push. Le comportement de cette notification push dépend du fait que l’utilisateur soit actif ou utilise un appareil proxy. {::nomarkdown}<ul><li>Si un <code>notification</code> est inclus et que l’utilisateur est actif sur son iPhone lorsque la mise à jour est livrée, l’interface utilisateur de l’activité en direct mise à jour glissera vers le bas et s’affichera comme une notification push.</li><li>Si un <code>notification</code> est inclus et que l’utilisateur n’est pas actif sur son iPhone, son écran s’allume pour afficher l’interface utilisateur de l’activité en direct mise à jour sur son écran de verrouillage.</li><li>Le paramètre <code>notification alert</code> ne s’affichera pas comme une notification push standard. De plus, si un utilisateur dispose d’un appareil proxy, comme une Apple Watch, le <code>alert</code> s’affichera ici.</li></ul>{:/} |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Exemple de demande
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/messages/live_activity/update' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer {YOUR-REST-API-KEY}' \
+--data-raw '{
+    "app_id": "{YOUR-APP-API-IDENTIFIER}",
+    "activity_id": "live-activity-1",
+    "content_state": {
+        "teamOneScore": 2,
+        "teamTwoScore": 4
+    },
+    "end_activity": false,
+    "dismissal_date": "2023-02-28T00:00:00+0000",
+    "stale_date": "2023-02-27T16:55:49+0000",
+    "notification": {
+        "alert": {
+            "body": "It's halftime! Let's look at the scores",
+            "title": "Halftime"
+        }
+    }
+}'
+```
+
+## Réponse
+
+Deux réponses de code de statut existent pour cet endpoint : `201` et `4XX`.
+
+### Exemple de réponse réussie
+
+Un code de statut `201` est renvoyé si la requête a été formatée correctement et que nous l’avons reçue. Le code de statut `201` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+La classe du code de statut `4XX` indique une erreur client. Reportez-vous à l'article [erreurs et réponses de l'API]({{site.baseurl}}/api/errors/) pour plus d'informations sur les erreurs que vous pouvez rencontrer.
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. 
+
+```json
+{
+    "error": "\nProblem:\n  message body does not match declared format\nResolution:\n  when specifying application/json as content-type, you must pass valid application/json in the request's 'body' "
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages.md
new file mode 100644
index 00000000000..c9e9db9e537
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages.md
@@ -0,0 +1,5 @@
+---
+nav_title: Planifier les messages
+config_only: true
+noindex: true
+---
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/get_messages_scheduled.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/get_messages_scheduled.md
new file mode 100644
index 00000000000..9f81758f361
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/get_messages_scheduled.md
@@ -0,0 +1,63 @@
+---
+nav_title: "GET : Répertorier les campagnes et Canvas planifiés à venir"
+article_title: "GET : Répertorier les campagnes et Canvas planifiés à venir"
+search_tag: Endpoint
+page_order: 0
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Répertorier les campagnes et Canvas planifiés à venir."
+
+---
+{% api %}
+# Répertorier les campagnes et Canvas planifiés à venir
+{% apimethod get %}
+/messages/scheduled_broadcasts
+{% endapimethod %}
+
+> Utilisez cet endpoint pour renvoyer une liste JSON des informations sur les campagnes planifiées et les Canvas saisis entre maintenant et un `end_time` spécifié dans la demande.
+
+Les messages quotidiens et récurrents n’apparaîtront qu’une seule fois lors de leur occurrence suivante. Les résultats renvoyés dans cet endpoint comprennent les campagnes et les toiles créées et planifiées dans le tableau de bord Braze.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#6f623cc3-383b-4bf7-b14d-7c56fc5562f5 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `messages.schedule_broadcasts`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `end_time` | Requis | Chaîne de caractères au format [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)  | Date de fin de la plage pour récupérer les campagnes et Canvas planifiés. Ce traitement est effectué à minuit (UTC) par l’API. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/messages/scheduled_broadcasts?end_time=2018-09-01T00:00:00-04:00' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "scheduled_broadcasts": [
+    {
+      "name": (string) the name of the scheduled broadcast,
+      "id": (stings) the Canvas or campaign identifier,
+      "type": (string) the broadcast type either Canvas or Campaign,
+      "tags": (array) an array of tag names formatted as strings,
+      "next_send_time": (string) The next send time formatted in ISO 8601, may also include time zone if not local/intelligent delivery,
+      "schedule_type": (string) The schedule type, either local_time_zones, intelligent_delivery or the name of your company's time zone,
+    },
+  ]
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages.md
new file mode 100644
index 00000000000..d4b2e9839d7
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages.md
@@ -0,0 +1,59 @@
+---
+nav_title: "POST : Supprimer les messages planifiés"
+article_title: "POST : Supprimer les messages planifiés"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Supprimer les messages planifiés."
+
+---
+{% api %}
+# Supprimer les messages planifiés
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/messages/schedule/delete
+{% endapimethod %}
+
+> Utilisez cet endpoint pour annuler un message que vous avez déjà planifié avant qu’il ne soit envoyé.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#5e89355c-0a5d-4d8b-8d89-2fd99bac36b0 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `messages.schedule.delete`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "schedule_id": (required, string) the `schedule_id` to delete (obtained from the response to create schedule)
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `schedule_id` | Requis | Chaîne de caractères | Le `schedule_id` à supprimer (obtenu à partir de la réponse pour créer une planification). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/messages/schedule/delete' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "schedule_id": "schedule_identifier"
+}'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases.md
new file mode 100644
index 00000000000..d7d05ed830c
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases.md
@@ -0,0 +1,65 @@
+---
+nav_title: "POST : Supprimer des Canvas planifiés déclenchés par API"
+article_title: "POST : Supprimer des Canvas planifiés déclenchés par API"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Supprimer des Canvas déclenchés par API et planifiés."
+
+---
+{% api %}
+# Supprimer les toiles planifiées déclenchées par l'API
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/canvas/trigger/schedule/delete
+{% endapimethod %}
+
+> L’endpoint de suppression de la planification vous permet d’annuler un message que vous avez déjà planifié dans des Canvas déclenchés par API avant qu’il ne soit envoyé.
+
+Les messages ou déclencheurs planifiés qui sont supprimés peu de temps avant ou pendant l’heure où ils sont censés être envoyés seront mis à jour dans les meilleurs délais, de sorte que les suppressions de dernière minute pourraient être appliquées à tous, certains ou aucun de vos utilisateurs ciblés.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#7d34037f-4bf2-4fab-bc9c-c972988051a7 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.trigger.schedule.delete`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "canvas_id": (required, string) the Canvas identifier,
+  "schedule_id": (required, string) the `schedule_id` to delete (obtained from the response to create schedule)
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `canvas_id`| Requis | Chaîne de caractères | Voir [Identifiant Canvas]({{site.baseurl}}/api/identifier_types/). |
+| `schedule_id` | Requis | Chaîne de caractères | Le `schedule_id` à supprimer (obtenu à partir de la réponse pour créer une planification). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/canvas/trigger/schedule/delete' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "canvas_id": "canvas_identifier",
+  "schedule_id": "schedule_identifier"
+}'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages.md
new file mode 100644
index 00000000000..a520e4564db
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages.md
@@ -0,0 +1,65 @@
+---
+nav_title: "POST : Supprimer des campagnes planifiées déclenchées par API"
+article_title: "POST : Supprimer des campagnes planifiées déclenchées par API"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Planifier des campagnes déclenchées par API et planifiées."
+
+---
+{% api %}
+# Supprimer des campagnes planifiées déclenchées par API
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/campaigns/trigger/schedule/delete
+{% endapimethod %}
+
+> Utilisez cet endpoint pour annuler un message Canvas que vous avez déjà planifié dans des campagnes déclenchées par API avant qu’il ne soit envoyé.
+
+Les messages ou déclencheurs planifiés qui sont supprimés peu de temps avant ou pendant l’heure où ils sont censés être envoyés seront mis à jour dans les meilleurs délais, de sorte que les suppressions de dernière minute pourraient être appliquées à tous, certains ou aucun de vos utilisateurs ciblés.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#7d34037f-4bf2-4fab-bc9c-c972988051a7 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `campaigns.trigger.schedule.delete`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "campaign_id": (required, string) the campaign identifier,
+  "schedule_id": (required, string) the `schedule_id` to delete (obtained from the response to create schedule)
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `campaign_id`| Requis | Chaîne de caractères | Voir [identifiant de campagne]({{site.baseurl}}/api/identifier_types/). |
+| `schedule_id` | Requis | Chaîne de caractères | Le `schedule_id` à supprimer (obtenu à partir de la réponse pour créer une planification). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/campaigns/trigger/schedule/delete' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "campaign_id": "campaign_identifier",
+  "schedule_id": "schedule_identifier"
+}'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_schedule_messages.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_schedule_messages.md
new file mode 100644
index 00000000000..efb0b091bd2
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_schedule_messages.md
@@ -0,0 +1,181 @@
+---
+nav_title: "POST : Créer des messages planifiés"
+article_title: "POST : Créer des messages planifiés"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Créer des messages planifiés."
+
+---
+{% api %}
+# Créer des messages planifiés
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/messages/schedule/create
+{% endapimethod %}
+
+> Cet endpoint permet de planifier l'envoi d'une campagne, d'un Canvas ou d'un autre message à une heure donnée et fournit un identifiant permettant de référencer ce message pour les mises à jour. 
+
+Si vous ciblez un segment, un enregistrement de votre demande sera stocké dans la [console de développement](https://dashboard.braze.com/app_settings/developer_console/activitylog/) après l'envoi de tous les messages planifiés.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#25272fb8-bc39-41df-9a41-07ecfd76cb1d {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `messages.schedule.create`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' category='message endpoints' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  // You will need to include at least one of 'segment_id', 'external_user_ids', and 'audience'
+  // Including 'segment_id' will send to members of that segment
+  // Including 'external_user_ids' and/or 'user_aliases' will send to those users
+  // Including both a Segment and users will send to the provided users if they are in the segment
+  "broadcast": (optional, boolean) see broadcast -- defaults to false on 8/31/17, must be set to true if users are not specified,
+  "external_user_ids": (optional, array of strings) see external user identifier,
+  "user_aliases": (optional, array of user alias object) see user alias,
+  "audience": (optional, connected audience object) see connected audience,
+  "segment_id": (optional, string) see segment identifier,
+  "campaign_id": (optional, string) see campaign identifier,
+  "send_id": (optional, string) see send identifier,
+  "override_messaging_limits": (optional, bool) ignore frequency capping rules, defaults to false,
+  "recipient_subscription_state": (optional, string) use this to send messages to only users who have opted in ('opted_in'), only users who have subscribed or are opted in ('subscribed') or to all users, including unsubscribed users ('all'), the latter being useful for transactional email messaging. Defaults to 'subscribed',
+  "schedule": { 
+    "time": (required, datetime as ISO 8601 string) time to send the message in UTC,
+    "in_local_time": (optional, bool),
+    "at_optimal_time": (optional, bool),
+  },
+  "messages": {
+    "apple_push": (optional, apple push object),
+    "android_push": (optional, android push object),
+    "kindle_push": (optional, kindle/fireOS push object),
+    "web_push": (optional, web push object),
+    "email": (optional, email object),
+    "webhook": (optional, webhook object),
+    "content_card": (optional, content card object),
+    "sms": (optional, SMS object)
+  }
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`broadcast`| Facultatif | Valeur booléenne | Vous devez définir `broadcast` sur « true » lorsque vous envoyez un message à un segment entier qui est ciblé par une campagne ou un Canvas. Ce paramètre est défini sur Faux par défaut (au 31 août 2017). <br><br> Si `broadcast` est défini sur « true », une liste `recipients` ne peut pas être incluse. Cependant, faites attention lors de la configuration de `broadcast: true` car en configurant involontairement cet indicateur, vous pourriez envoyer votre message à une audience plus importante que prévue. |
+| `external_user_ids` | Facultatif | Tableau de chaînes de caractères | Voir [identifiant d'utilisateur externe]({{site.baseurl}}/api/objects_filters/user_attributes_object/#braze-user-profile-fields). |
+| `user_aliases` | Facultatif | Tableau des objets Alias utilisateur | Voir l'[objet alias d'utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object/). |
+| `audience` | Facultatif | Objet Audience connectée | Voir [audience connectée]({{site.baseurl}}/api/objects_filters/connected_audience/). |
+| `segment_id` | Facultatif | Chaîne de caractères | Voir [identifiant de segmentation]({{site.baseurl}}/api/identifier_types/). |
+| `campaign_id`|Facultatif|Chaîne de caractères| Voir [identifiant de campagne]({{site.baseurl}}/api/identifier_types/). |
+| `recipients` | Facultatif | Tableau des objets Destinataires | Voir [objet destinataire]({{site.baseurl}}/api/objects_filters/recipient_object/). |
+| `send_id` | Facultatif | Chaîne de caractères | Voir [identifiant d'envoi]({{site.baseurl}}/api/identifier_types/). | 
+| `override_messaging_limits` | Facultatif | Valeur booléenne | Ignorer les limites de débit globales pour les campagnes, définies sur Faux par défaut |
+|`recipient_subscription_state`| Facultatif | Chaîne de caractères | Utilisez cette option pour envoyer des messages uniquement aux utilisateurs qui ont confirmé l’abonnement (`opted_in`), aux utilisateurs qui ont souscrit à ou confirmé l’abonnement (`subscribed`) ou à tous les utilisateurs, y compris les utilisateurs désabonnés (`all`). <br><br>Appliquer l’option `all` pour les utilisateurs est utile pour les e-mails transactionnels. Par défaut, `subscribed`. |
+| `schedule` | Requis | Objet Planification | Voir [objet de planification]({{site.baseurl}}/api/objects_filters/schedule_object/) |
+| `messages` | Facultatif | Objet Messagerie | Voir les [objets d'envoi de messages disponibles]({{site.baseurl}}/api/objects_filters/#messaging-objects). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/messages/schedule/create' \
+--data-raw '{
+  "broadcast": "false",
+  "external_user_ids": "external_user_identifiers",
+  "user_aliases": {
+    "alias_name" : "example_name",
+    "alias_label" : "example_label"
+  },
+  "segment_id": "segment_identifiers",
+  "audience": {
+    "AND": [
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "eye_color",
+          "comparison": "equals",
+          "value": "blue"
+        }
+      },
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "favorite_foods",
+          "comparison": "includes_value",
+          "value": "pizza"
+        }
+      },
+      {
+        "OR": [
+          {
+            "custom_attribute": {
+              "custom_attribute_name": "last_purchase_time",
+              "comparison": "less_than_x_days_ago",
+              "value": 2
+            }
+          },
+          {
+            "push_subscription_status": {
+              "comparison": "is",
+              "value": "opted_in"
+            }
+          }
+        ]
+      },
+      {
+        "email_subscription_status": {
+          "comparison": "is_not",
+          "value": "subscribed"
+        }
+      },
+      {
+        "last_used_app": {
+          "comparison": "after",
+          "value": "2019-07-22T13:17:55+0000"
+        }
+      }
+    ]
+  },
+  "campaign_id": "campaign_identifier",
+  "send_id": "send_identifier",
+  "override_messaging_limits": false,
+  "recipient_subscription_state": "subscribed",
+  "schedule": {
+    "time": "",
+    "in_local_time": true,
+    "at_optimal_time": true
+  },
+  "messages": {
+    "apple_push": (optional, Apple Push Object),
+    "android_push": (optional, Android Push Object),
+    "kindle_push": (optional, Kindle/FireOS Push Object),
+    "web_push": (optional, Web Push Object),
+    "email": (optional, Email object)
+    "webhook": (optional, Webhook object)
+    "content_card": (optional, Content Card Object)
+  }
+}'
+```
+
+## Réponse
+
+### Exemple de réponse réussie
+
+```json
+{
+    "dispatch_id": (string) the dispatch identifier,
+    "schedule_id": (string) the schedule identifier,
+    "message": "success"
+}
+```
+
+{% endapi %}
+
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns.md
new file mode 100644
index 00000000000..3afb6bdb787
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns.md
@@ -0,0 +1,160 @@
+---
+nav_title: "POST : Planifier des campagnes déclenchées par l'API"
+article_title: "POST : Planifier des campagnes déclenchées par l'API"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Planifier des campagnes déclenchées par API."
+
+---
+{% api %}
+# Planifier des campagnes déclenchées par API
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/campaigns/trigger/schedule/create
+{% endapimethod %}
+
+> Utilisez cet endpoint pour envoyer des messages de campagne créés dans le tableau de bord via une réception/distribution déclenchée par l'API, ce qui vous permet de décider quelle action doit déclencher l'envoi du message. 
+
+Vous pouvez indiquer les `trigger_properties` qui seront modélisées dans le message lui-même.
+
+Notez que pour envoyer des messages avec cet endpoint, vous devez disposer d'un [ID de campagne]({{site.baseurl}}/api/identifier_types/), créé lorsque vous créez une [campagne déclenchée par l'API]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/api_triggered_delivery/).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#b7e61de7-f2c2-49c9-9e46-b85a0aa01bba {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `campaigns.trigger.schedule.create`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' category='message endpoints' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "campaign_id": (required, string) see campaign identifier,
+  "send_id": (optional, string) see send identifier,
+  // Including 'recipients' will send only to the provided user ids if they are in the campaign's segment
+  "recipients": (optional, array of recipients object),
+  // for any keys that conflict between these trigger properties and those in a Recipients Object, the value from the Recipients Object will be used
+  "audience": (optional, connected audience object) see connected audience,
+  // Including 'audience' will only send to users in the audience
+  // If 'recipients' and 'audience' are not provided and broadcast is not set to 'false',
+  // the message will send to entire segment targeted by the campaign
+  "broadcast": (optional, boolean) see broadcast -- defaults to false on 8/31/17, must be set to true if "recipients" object is omitted,
+  "trigger_properties": (optional, object) personalization key-value pairs for all users in this send; see trigger properties,
+  "schedule": {
+    "time": (required, datetime as ISO 8601 string) time to send the message,
+    "in_local_time": (optional, bool),
+    "at_optimal_time": (optional, bool),
+  }
+}
+```
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`campaign_id`|Requis|Chaîne de caractères| Voir [identifiant de campagne]({{site.baseurl}}/api/identifier_types/)|
+| `send_id` | Facultatif | Chaîne de caractères | Voir [identifiant d'envoi]({{site.baseurl}}/api/identifier_types/). | 
+| `recipients` | Facultatif | Tableau des objets Destinataires | Voir [objet destinataire]({{site.baseurl}}/api/objects_filters/recipient_object/). |
+| `audience` | Facultatif | Objet Audience connectée | Voir [audience connectée]({{site.baseurl}}/api/objects_filters/connected_audience/). |
+|`broadcast`| Facultatif | Valeur booléenne | Vous devez définir `broadcast` sur « true » lorsque vous envoyez un message à un segment entier qui est ciblé par une campagne ou un Canvas. Ce paramètre est défini sur Faux par défaut (au 31 août 2017). <br><br> Si `broadcast` est défini sur « true », une liste `recipients` ne peut pas être incluse. Cependant, faites attention lors de la configuration de `broadcast: true` car en configurant involontairement cet indicateur, vous pourriez envoyer votre message à une audience plus importante que prévue. |
+| `trigger_properties` | Facultatif | Objet | Personnalisation des paires clé-valeur pour tous les utilisateurs de cet envoi. Voir les [propriétés du déclencheur]({{site.baseurl}}/api/objects_filters/trigger_properties_object/). |
+| `schedule` | Requis | Objet Planification | Voir [objet de planification]({{site.baseurl}}/api/objects_filters/schedule_object/). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/campaigns/trigger/schedule/create' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "campaign_id": "campaign_identifier",
+  "send_id": "send_identifier",
+  "recipients": [
+    {
+      "user_alias": "example_alias",
+      "external_user_id": "external_user_identifier",
+      "trigger_properties": {}
+    }
+  ],
+  "audience": {
+    "AND": [
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "eye_color",
+          "comparison": "equals",
+          "value": "blue"
+        }
+      },
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "favorite_foods",
+          "comparison": "includes_value",
+          "value": "pizza"
+        }
+      },
+      {
+        "OR": [
+          {
+            "custom_attribute": {
+              "custom_attribute_name": "last_purchase_time",
+              "comparison": "less_than_x_days_ago",
+              "value": 2
+            }
+          },
+          {
+            "push_subscription_status": {
+              "comparison": "is",
+              "value": "opted_in"
+            }
+          }
+        ]
+      },
+      {
+        "email_subscription_status": {
+          "comparison": "is_not",
+          "value": "subscribed"
+        }
+      },
+      {
+        "last_used_app": {
+          "comparison": "after",
+          "value": "2019-07-22T13:17:55+0000"
+        }
+      }
+    ]
+  },
+  "broadcast": false,
+  "trigger_properties": {},
+  "schedule": {
+    "time": "",
+    "in_local_time": false,
+    "at_optimal_time": false
+  }
+}'
+```
+
+## Réponse
+
+### Exemple de réponse réussie
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-API-KEY-HERE
+{
+{
+    "dispatch_id": "dispatch_identifier",
+    "schedule_id": "schedule_identifier",
+    "message": "success"
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases.md
new file mode 100644
index 00000000000..11431c49790
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases.md
@@ -0,0 +1,159 @@
+---
+nav_title: "POST : Planification des toiles déclenchées par l'API"
+article_title: "POST : Planification des toiles déclenchées par l'API"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Planifier des Canvas déclenchés par API."
+
+---
+{% api %}
+# Planifier des Canvas déclenchés par API
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/canvas/trigger/schedule/create
+{% endapimethod %}
+
+> Utilisez cet endpoint pour planifier des messages Canvas via une réception/distribution déclenchée par l'API, ce qui vous permet de décider quelle action doit déclencher l'envoi du message. 
+
+Vous pouvez indiquer les `canvas_entry_properties` qui seront modélisées dans les messages envoyés dès les premières étapes du Canvas.
+
+Notez que pour envoyer des messages avec cet endpoint, vous devez disposer d'un [ID Canvas]({{site.baseurl}}/api/identifier_types/#canvas-api-identifier), créé lorsque vous créez un Canvas.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#4bc75890-b807-405d-b226-5aca284e6b7d {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.trigger.schedule.create`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' category='message endpoints' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "canvas_id": (required, string) see Canvas identifier,
+  // Including 'recipients' will send only to the provided user ids if they are in the campaign's segment
+  "recipients": (optional, array of recipients object),
+  // for any keys that conflict between these trigger properties and those in a Recipients Object, the value from the
+  // Recipients Object will be used
+  "audience": (optional, connected audience object) see connected audience,
+  // Including 'audience' will only send to users in the audience
+  // If 'recipients' and 'audience' are not provided and broadcast is not set to 'false',
+  // the message will send to entire segment targeted by the Canvas
+  "broadcast": (optional, boolean) see broadcast -- defaults to false on 8/31/17, must be set to true if "recipients" object is omitted,
+  "canvas_entry_properties": (optional, object) personalization key-value pairs for the first step for all users in this send; see trigger properties,
+  "schedule": {
+    "time": (required, datetime as ISO 8601 string) time to send the message,
+    "in_local_time": (optional, bool),
+    "at_optimal_time": (optional, bool),
+  }
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`canvas_id`|Requis|Chaîne de caractères| Voir [Identifiant Canvas]({{site.baseurl}}/api/identifier_types/). |
+| `recipients` | Facultatif | Tableau des objets Destinataires | Voir [objet destinataire]({{site.baseurl}}/api/objects_filters/recipient_object/). |
+| `audience` | Facultatif | Objet Audience connectée | Voir [audience connectée]({{site.baseurl}}/api/objects_filters/connected_audience/). |
+|`broadcast`| Facultatif | Valeur booléenne | Vous devez définir `broadcast` sur « true » lorsque vous envoyez un message à un segment entier qui est ciblé par une campagne ou un Canvas. Ce paramètre est défini sur Faux par défaut (au 31 août 2017). <br><br> Si `broadcast` est défini sur « true », une liste `recipients` ne peut pas être incluse. Cependant, faites attention lors de la configuration de `broadcast: true` car en configurant involontairement cet indicateur, vous pourriez envoyer votre message à une audience plus importante que prévue. |
+| `canvas_entry_properties` | Facultatif | Objet | Personnalisation des paires clé-valeur pour tous les utilisateurs de cet envoi. Voir l'[objet des propriétés de l'entrée Canvas]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object). |
+| `schedule` | Requis | Objet Planification | Voir [objet de planification]({{site.baseurl}}/api/objects_filters/schedule_object/). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/canvas/trigger/schedule/create' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "canvas_id": "canvas_identifier",
+  "recipients": [
+    {
+      "user_alias": "example_alias",
+      "external_user_id": "external_user_identifier",
+      "canvas_entry_properties": {}
+    }
+  ],
+  "audience": {
+    "AND": [
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "eye_color",
+          "comparison": "equals",
+          "value": "blue"
+        }
+      },
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "favorite_foods",
+          "comparison": "includes_value",
+          "value": "pizza"
+        }
+      },
+      {
+        "OR": [
+          {
+            "custom_attribute": {
+              "custom_attribute_name": "last_purchase_time",
+              "comparison": "less_than_x_days_ago",
+              "value": 2
+            }
+          },
+          {
+            "push_subscription_status": {
+              "comparison": "is",
+              "value": "opted_in"
+            }
+          }
+        ]
+      },
+      {
+        "email_subscription_status": {
+          "comparison": "is_not",
+          "value": "subscribed"
+        }
+      },
+      {
+        "last_used_app": {
+          "comparison": "after",
+          "value": "2019-07-22T13:17:55+0000"
+        }
+      }
+    ]
+  },
+  "broadcast": false,
+  "canvas_entry_properties": {},
+  "schedule": {
+    "time": "",
+    "in_local_time": false,
+    "at_optimal_time": false
+  }
+}'
+```
+
+## Réponse
+
+### Exemple de réponse réussie
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-API-KEY-HERE
+{
+{
+    "dispatch_id": "dispatch_identifier",
+    "schedule_id": "schedule_identifier",
+    "message": "success"
+}
+```
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_update_scheduled_messages.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_update_scheduled_messages.md
new file mode 100644
index 00000000000..abcea428d83
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_update_scheduled_messages.md
@@ -0,0 +1,87 @@
+---
+nav_title: "POST : Mettre à jour les messages planifiés"
+article_title: "POST : Mettre à jour les messages planifiés"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour les messages planifiés."
+
+---
+{% api %}
+# Mettre à jour les messages planifiés
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/messages/schedule/update
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour les messages planifiés. 
+
+Cet endpoint accepte les mises à jour du paramètre `schedule` ou du paramètre `messages` ou des deux. Votre demande doit contenir au moins une des deux clés.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#f61edf74-4467-4551-b9c4-a4b8d188cd7a {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `messages.schedule.update`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "schedule_id": (required, string) the `schedule_id` to update (obtained from the response to create schedule),
+  "schedule": {
+    // optional, see create schedule documentation
+  },
+  "messages": {
+    // optional, see available messaging objects documentation
+  }
+}
+```
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `schedule_id` | Requis | Chaîne de caractères | Le `schedule_id` à mettre à jour (obtenu à partir de la réponse pour créer une planification). |
+|`schedule` | Facultatif | Objet | Voir [objet de l'horaire]({{site.baseurl}}/api/objects_filters/schedule_object/). |
+|`messages` | Facultatif | Objet | Voir [les objets de messagerie disponibles]({{site.baseurl}}/api/objects_filters/#messaging-objects). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/messages/schedule/update' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "schedule_id": "schedule_identifier",
+  "schedule": {
+    "time": "2017-05-24T20:30:36Z"
+   },
+  "messages": {
+    "apple_push": {
+      "alert": "Updated Message!",
+      "badge": 1
+    },
+    "android_push": {
+      "title": "Updated title!",
+      "alert": "Updated message!"
+    },
+    "sms": {  
+      "subscription_group_id": "subscription_group_identifier",
+      "message_variation_id": "message_variation_identifier",
+      "body": "This is my SMS body.",
+      "app_id": "app_identifier"
+    }
+  }
+}'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns.md
new file mode 100644
index 00000000000..7964ac605e2
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns.md
@@ -0,0 +1,75 @@
+---
+nav_title: "POST : Mettre à jour les campagnes déclenchées par l'API planifiées"
+article_title: "POST : Mettre à jour les campagnes déclenchées par l'API planifiées"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour des campagnes planifiées déclenchées par API."
+
+---
+{% api %}
+# Mettre à jour les campagnes planifiées déclenchées par API
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/campaigns/trigger/schedule/update
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour des campagnes planifiées déclenchées par API et créées dans le tableau de bord, ce qui vous permet de décider quelle action doit déclencher le message à envoyer.
+
+Vous pouvez indiquer les `trigger_properties` qui seront modélisées dans le message lui-même.
+
+Notez que pour envoyer des messages avec ce point de terminaison, vous devez avoir un ID de campagne, créé lorsque vous construisez une [campagne déclenchée par API]({{site.baseurl}}/api/api_campaigns/).
+
+Toute planification écrasera complètement celle que vous avez établie dans la demande de création de planification ou dans les demandes de mise à jour de planification précédentes. Par exemple, si vous indiquez initialement `"schedule" : {"time" : "2015-02-20T13:14:47", "in_local_time" : true}` et, que dans votre mise à jour, vous renseignez `"schedule" : {"time" : "2015-02-20T14:14:47"}`, votre message sera envoyé à l’heure indiquée (UTC), et non à l’heure locale de l’utilisateur. Les déclencheurs planifiés qui sont mis à jour peu de temps avant ou pendant la période où ils sont censés être envoyés seront mis à jour dans les meilleurs délais, de sorte que les changements de dernière minute pourraient être appliqués à tous, certains ou aucun de vos utilisateurs ciblés.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#6d2a6e66-9d6f-4ae1-965a-79fa52b86b1d {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `campaigns.trigger.schedule.update`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "campaign_id": (required, string) see campaign identifier,
+  "schedule_id": (required, string) the `schedule_id` to update (obtained from the response to create schedule),
+  "schedule": {
+    // required, see create schedule documentation
+  }
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`campaign_id`|Requis|Chaîne de caractères| Voir [identifiant de la campagne]({{site.baseurl}}/api/identifier_types/)|
+| `schedule_id` | Requis | Chaîne de caractères | Le `schedule_id` à mettre à jour (obtenu à partir de la réponse pour créer un calendrier). |
+|`schedule` | Requis | Objet | Voir [objet de l'horaire]({{site.baseurl}}/api/objects_filters/schedule_object/). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/campaigns/trigger/schedule/update' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "campaign_id": "campaign_identifier",
+  "schedule_id": "schedule_identifier",
+  "schedule": {
+    "time": "2017-05-24T21:30:00Z",
+    "in_local_time": true
+  }
+}'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases.md b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases.md
new file mode 100644
index 00000000000..d1570c5ae76
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases.md
@@ -0,0 +1,78 @@
+---
+nav_title: "POST : Mise à jour des canevas déclenchés par l'API planifiée"
+article_title: "POST : Mise à jour des canevas déclenchés par l'API planifiée"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour des Canvas planifiés déclenchés par API."
+
+---
+{% api %}
+# Mise à jour des Canvases déclenchées par l'API planifiée
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/canvas/trigger/schedule/update
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour des Canvas déclenchés par API planifiés qui ont été créés dans le tableau de bord. 
+
+Ceci vous permet de décider quelle action doit déclencher l’envoi du message. Vous pouvez indiquer les `trigger_properties` qui seront modélisées dans le message lui-même.
+
+Notez que pour envoyer des messages avec ce point de terminaison, vous devez avoir un ID Canvas, créé lorsque vous construisez un [Canvas]({{site.baseurl}}/api/identifier_types/#canvas-api-identifier).
+
+Toute planification écrasera complètement celle que vous avez établie dans la demande de création de planification ou dans les demandes de mise à jour de planification précédentes. 
+  - Par exemple, si vous indiquez initialement `"schedule" : {"time" : "2015-02-20T13:14:47", "in_local_time" : true}` et, que dans votre mise à jour, vous renseignez `"schedule" : {"time" : "2015-02-20T14:14:47"}`, votre message sera envoyé à l’heure indiquée (UTC), et non à l’heure locale de l’utilisateur. 
+  - Les déclencheurs planifiés qui sont mis à jour peu de temps avant ou pendant la période où ils sont censés être envoyés seront mis à jour dans les meilleurs délais, de sorte que les changements de dernière minute pourraient être appliqués à tous, certains ou aucun de vos utilisateurs ciblés.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#8fdf158b-ce20-41d8-80e4-a9300a6706d4 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.trigger.schedule.update`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "canvas_id": (required, string) see Canvas identifier,
+  "schedule_id": (required, string) the `schedule_id` to update (obtained from the response to create schedule),
+  "schedule": {
+    // required, see create schedule documentation
+  }
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`canvas_id`|Requis|Chaîne de caractères| Voir [identifiant de Canvas]({{site.baseurl}}/api/identifier_types/). |
+| `schedule_id` | Facultatif | Chaîne de caractères | Le `schedule_id` à mettre à jour (obtenu à partir de la réponse pour créer une planification). |
+|`schedule` | Requis | Objet | Voir [objet de l'horaire]({{site.baseurl}}/api/objects_filters/schedule_object/). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/canvas/trigger/schedule/update' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "canvas_id": "canvas_identifier",
+  "schedule_id": "schedule_identifier",
+  "schedule": {
+    "time": "2017-05-24T21:30:00Z",
+    "in_local_time": true
+  }
+}'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/send_messages.md b/_lang/fr_fr/_api/endpoints/messaging/send_messages.md
new file mode 100644
index 00000000000..c1e08426189
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/send_messages.md
@@ -0,0 +1,5 @@
+---
+nav_title: Envoyer les messages
+config_only: true
+noindex: true
+---
diff --git a/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_create_send_ids.md b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_create_send_ids.md
new file mode 100644
index 00000000000..509cea0f465
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_create_send_ids.md
@@ -0,0 +1,77 @@
+---
+nav_title: "POST : Créer des ID d’envoi"
+article_title: "POST : Créer des ID d’envoi"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Créer des ID d’envoi."
+
+---
+{% api %}
+# Créer des ID d’envoi
+{% apimethod post %}
+/sends/id/create
+{% endapimethod %}
+
+> Utilisez cet endpoint pour créer des ID d’envoi pouvant être utilisés pour envoyer des messages et suivre leur performance de manière programmatique sans créer de campagne pour chaque envoi. 
+
+L’utilisation de l’identifiant d’envoi pour suivre et envoyer des messages est utile si vous prévoyez de générer et d’envoyer du contenu via un programme.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#74a04e53-659f-4473-abc5-0f6f735550ff {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous devrez générer une clé API avec l’autorisation `sends.id.create`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='sends id create' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "campaign_id": (required, string) see campaign identifier,
+  "send_id": (optional, string) see send identifier
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `campaign_id` | Requis | Chaîne de caractères | Voir [identifiant de campagne]({{site.baseurl}}/api/identifier_types/). |
+|`send_id`| Facultatif | Chaîne de caractères | Voir [identifiant d'envoi]({{site.baseurl}}/api/identifier_types/). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/sends/id/create' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "campaign_id": "campaign_identifier",
+  "send_id": "send_identifier"
+}'
+```
+
+## Réponse
+
+### Exemple de réponse réussie
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "message": "success",
+  "send_id" : (string) the send identifier
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_messages.md b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_messages.md
new file mode 100644
index 00000000000..78d5fbdfed5
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_messages.md
@@ -0,0 +1,163 @@
+---
+nav_title: "POST : Envoyer des messages immédiatement via API uniquement"
+article_title: "POST : Envoyer des messages immédiatement via API uniquement"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Envoyer des messages immédiatement via API uniquement."
+
+---
+{% api %}
+# Envoyer des messages immédiatement via API uniquement
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/messages/send
+{% endapimethod %}
+
+> Utilisez cet endpoint pour envoyer des messages immédiats aux utilisateurs désignés via l'API de Braze. 
+
+Veillez à inclure les objets Messagerie dans votre corps pour finaliser vos demandes.
+
+Si vous souhaitez cibler un segment, un enregistrement de votre requête sera stocké dans la [console de développement](https://dashboard.braze.com/app_settings/developer_console/activitylog/).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#946cb701-96e3-48d7-868c-f079785b6d24 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous devrez générer une clé API avec l’autorisation `messages.send`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='send endpoints' category='message send endpoint' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+   // You will need to include at least one of 'segment_id', 'external_user_ids', and 'audience'
+   // Including 'segment_id' will send to members of that segment
+   // Including 'external_user_ids' and/or 'user_aliases' will send to those users
+   // Including both will send to the provided users if they are in the segment
+   "broadcast": (optional, boolean) see broadcast -- defaults to false on 8/31/17, must be set to true if no external_user_ids or aliases are provided,
+   "external_user_ids": (optional, array of strings) see external user identifier,
+   "user_aliases": (optional, array of user alias object) see user alias,
+   "segment_id": (optional, string) see segment identifier,
+   "audience": (optional, connected audience object) see connected audience,
+   "campaign_id": (optional*, string) *required if you wish to track campaign stats (for example, sends, clicks, bounces, etc). see campaign identifier,
+   "send_id": (optional, string) see send identifier,
+   "override_frequency_capping": (optional, bool) ignore frequency_capping for campaigns, defaults to false,
+   "recipient_subscription_state": (optional, string) use this to send messages to only users who have opted in ('opted_in'), only users who have subscribed or are opted in ('subscribed') or to all users, including unsubscribed users ('all'), the latter being useful for transactional email messaging. Defaults to 'subscribed',
+   "messages": {
+     "apple_push": (optional, apple push object),
+     "android_push": (optional, android push object),
+     "kindle_push": (optional, kindle/fireOS push object),
+     "web_push": (optional, web push object),
+     "email": (optional, email object),
+     "webhook": (optional, webhook object),
+     "content_card": (optional, content card object),
+     "sms": (optional, SMS object),
+     "whats_app": (optional, WhatsApp object)
+   }
+ }
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`broadcast`| Facultatif | Valeur booléenne | Vous devez définir `broadcast` sur « true » lorsque vous envoyez un message à un segment entier qui est ciblé par une campagne ou un Canvas. Ce paramètre est défini sur Faux par défaut (au 31 août 2017). <br><br> Si `broadcast` est défini sur « true », une liste `recipients` ne peut pas être incluse. Cependant, faites attention lors de la configuration de `broadcast: true` car en configurant involontairement cet indicateur, vous pourriez envoyer votre message à une audience plus importante que prévue. |
+|`external_user_ids` | Facultatif | Tableau de chaînes de caractères | Voir [ID externe]({{site.baseurl}}/api/objects_filters/user_attributes_object/#braze-user-profile-fields). |
+|`user_aliases`| Facultatif | Tableau des objets Alias utilisateur| Voir l'[objet alias d'utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object/). |
+|`segment_id `| Facultatif | Chaîne de caractères | Voir [identifiant de segmentation]({{site.baseurl}}/api/identifier_types/). |
+|`audience`| Facultatif | Objet Audience connectée | Voir [audience connectée]({{site.baseurl}}/api/objects_filters/connected_audience/). |
+|`campaign_id`| En option* | Chaîne de caractères | Pour plus d'informations, voir l'[identifiant de la campagne]({{site.baseurl}}/api/identifier_types/). <br><br>\*Nécessaire si vous souhaitez suivre les statistiques de la campagne (par exemple, les envois, les clics, les rebonds, etc.) sur le tableau de bord de Braze. |
+|`send_id`| Facultatif | Chaîne de caractères | Voir [identifiant d'envoi]({{site.baseurl}}/api/identifier_types/) |
+|`override_frequency_capping`| Facultatif | Valeur booléenne | Ignorez `frequency_capping` pour les campagnes, la valeur par défaut est `false`. |
+|`recipient_subscription_state`| Facultatif | Chaîne de caractères | Utilisez cette option pour envoyer des messages uniquement aux utilisateurs qui ont confirmé l’abonnement (`opted_in`), aux utilisateurs qui ont souscrit à ou confirmé l’abonnement (`subscribed`) ou à tous les utilisateurs, y compris les utilisateurs désabonnés (`all`). <br><br>Appliquer l’option `all` pour les utilisateurs est utile pour les e-mails transactionnels. Par défaut, `subscribed`. |
+|`messages`| Facultatif | Objets Messagerie | Voir les [objets d'envoi de messages disponibles]({{site.baseurl}}/api/objects_filters/#messaging-objects). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/messages/send' \
+--data-raw '{
+  "broadcast": "false",
+  "external_user_ids": "external_user_identifiers",
+  "user_aliases": {
+    "alias_name": "example_name",
+    "alias_label": "example_label"
+  },
+  "segment_id": "segment_identifier",
+  "audience": {
+    "AND": [
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "eye_color",
+          "comparison": "equals",
+          "value": "blue"
+        }
+      },
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "favorite_foods",
+          "comparison": "includes_value",
+          "value": "pizza"
+        }
+      },
+      {
+        "OR": [
+          {
+            "custom_attribute": {
+              "custom_attribute_name": "last_purchase_time",
+              "comparison": "less_than_x_days_ago",
+              "value": 2
+            }
+          },
+          {
+            "push_subscription_status": {
+              "comparison": "is",
+              "value": "opted_in"
+            }
+          }
+        ]
+      },
+      {
+        "email_subscription_status": {
+          "comparison": "is_not",
+          "value": "subscribed"
+        }
+      },
+      {
+        "last_used_app": {
+          "comparison": "after",
+          "value": "2019-07-22T13:17:55+0000"
+        }
+      }
+    ]
+  },
+  "campaign_id": "campaign_identifier",
+  "send_id": "send_identifier",
+  "override_frequency_capping": "false",
+  "recipient_subscription_state": "all",
+  "messages": {
+    "android_push": "(optional, Android Push Object)",
+    "apple_push": "(optional, Apple Push Object)",
+    "content_card": "(optional, Content Card Object)",
+    "email": "(optional, Email Object)",
+    "kindle_push": "(optional, Kindle/FireOS Push Object)",
+    "web_push": "(optional, Web Push Object)"
+  }
+}'
+```
+
+## Informations relatives à la réponse
+
+Les réponses des endpoints d’envoi de messages incluront le `dispatch_id` du message pour y faire référence lors de l’envoi. Le `dispatch_id` est l’identifiant de la transmission du message, c’est un ID unique pour chaque « dispatch » envoyé par Braze. Pour plus d'informations, consultez [Comportement du Dispatch ID]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+
+{% endapi %}
+
diff --git a/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_transactional_message.md b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_transactional_message.md
new file mode 100644
index 00000000000..ec510447407
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_transactional_message.md
@@ -0,0 +1,242 @@
+---
+nav_title: "POST : Envoyer des e-mails transactionnels via une livraison déclenchée par API"
+article_title: "POST : Envoyer des e-mails transactionnels via une livraison déclenchée par API"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Envoyer des e-mails transactionnels via une livraison déclenchée par API."
+
+---
+
+{% api %}
+# Envoyer des e-mails transactionnels via une livraison déclenchée par API
+{% apimethod post %}
+/transactional/v1/campaigns/{campaign_id}/send
+{% endapimethod %}
+
+> Utilisez cet endpoint pour envoyer des messages transactionnels immédiats et ponctuels à un utilisateur désigné. 
+
+Cet endpoint est utilisé parallèlement à la création d'une [campagne d'e-mails transactionnels de]({{site.baseurl}}/api/api_campaigns/transactional_campaigns) Braze et de l'ID de campagne correspondant.
+
+{% alert important %}
+L’e-mail transactionnel est actuellement disponible dans certains forfaits Braze. Contactez votre gestionnaire du succès des clients Braze pour plus d’informations.
+{% endalert %}
+
+Similaire à l'[endpoint de campagne Send triggered]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns/), ce type de campagne vous permet d'héberger le contenu du message à l'intérieur du tableau de bord de Braze tout en dictant quand et à qui un message est envoyé via votre API. Contrairement au point de terminaison Send triggered campaign, qui accepte une audience ou un segment auquel envoyer des messages, une demande à ce point de terminaison doit spécifier un utilisateur unique par `external_user_id` ou `user_alias`, car ce type de campagne est créé pour l'envoi de messages 1:1 d'alertes telles que des confirmations de commande ou des réinitialisations de mot de passe.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#cec874e1-fa51-42a6-9a8d-7fc57d6a63bc {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous devrez générer une clé API avec l’autorisation `transactional.send`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='transactional email' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `campaign_id` | Requis | Chaîne de caractères | ID de la campagne |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "external_send_id": (optional, string) see the following request parameters,
+  "trigger_properties": (optional, object) personalization key-value pairs that will apply to the user in this request,
+  "recipient": (required, object)
+    {
+      // Either "external_user_id" or "user_alias" is required. Requests must specify only one.
+      "user_alias": (optional, User alias object) User alias of the user to receive message,
+      "external_user_id": (optional, string) External identifier of user to receive message,
+      "attributes": (optional, object) fields in the attributes object will create or update an attribute of that name with the given value on the specified user profile before the message is sent and existing values will be overwritten
+    }
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`external_send_id`| Facultatif | Chaîne de caractères |  Une chaîne de caractères compatible Base64. Validé par rapport aux expressions régulières suivantes :<br><br> `/^[a-zA-Z0-9-_+\/=]+$/` <br><br>Ce champ facultatif vous permet de transmettre un identifiant interne pour cet envoi particulier, qui sera inclus dans les événements envoyés à partir du postback de l’événement HTTP transactionnel. Lorsqu’il est communiqué, cet identifiant est également utilisé comme clé de déduplication, que Braze conservera pendant 24 heures. <br><br>Le fait d’indiquer le même identifiant à une autre demande n’entraînera pas de nouvelle instance d’envoi par Braze pendant 24 heures.|
+|`trigger_properties`|Facultatif|Objet|Voir les [propriétés du déclencheur]({{site.baseurl}}/api/objects_filters/trigger_properties_object/). Les paires clé-valeur de personnalisation qui s’appliquent à l’utilisateur de cette demande. |
+|`recipient`|Requis|Objet| L’utilisateur que vous ciblez avec ce message. Peut contenir des `attributes` et un seul `external_user_id` ou `user_alias`.<br><br>Notez que si vous fournissez un ID utilisateur externe qui n’existe pas déjà dans Braze, la transmission d’un des champs à l’objet `attributes` aura pour effet de créer ce profil utilisateur dans Braze et d’envoyer ce message à l’utilisateur nouvellement créé. <br><br>Si vous envoyez plusieurs demandes au même utilisateur avec des données différentes dans l'objet `attributes`, les attributs `first_name`, `last_name` et `email` seront mis à jour de manière synchrone et intégrés dans votre message. Les attributs personnalisés n’ont pas cette même protection, procédez donc avec prudence lors de la mise à jour d’un utilisateur via cette API et de la transmission des différentes valeurs d’attributs personnalisés en succession rapide.|
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl -X POST \
+  -H 'Content-Type:application/json' \
+  -H 'Authorization: Bearer YOUR-REST-API-KEY' \
+  -d '{
+        "external_send_id" : YOUR_BASE64_COMPATIBLE_ID
+        "trigger_properties": {
+          "example_string_property": YOUR_EXAMPLE_STRING,
+          "example_integer_property": YOUR_EXAMPLE_INTEGER
+        },
+        "recipient": {
+          "external_user_id": TARGETED_USER_ID_STRING
+        }
+      }' \
+  https://rest.iad-01.braze.com/transactional/v1/campaigns/{campaign_id}/send
+```
+
+## Réponse 
+
+L'endpoint d'envoi d'e-mail transactionnel répondra avec le message `dispatch_id` qui représente l'instance de cet envoi de message. Cet identifiant peut être utilisé avec les événements du postback de l’événement HTTP transactionnel pour tracer le statut d’un e-mail individuel envoyé à un utilisateur unique.
+
+### Exemple de réponses
+
+```json
+{
+    "dispatch_id": A randomly-generated unique ID of the instance of this send
+    "status": Current status of the message
+    "metadata" : Object containing additional information about the send instance
+}
+```
+
+## Résolution des problèmes
+
+L’endpoint peut renvoyer également, dans certains cas, un code d’erreur et un message lisible par un être humain, qui sont souvent des erreurs de validation. Voici quelques-unes des erreurs fréquentes pouvant être obtenues lorsque vous réalisez des requêtes invalides.
+
+| Erreur | Résolution des problèmes |
+| ----- | --------------- |
+| `The campaign is not a transactional campaign. Only transactional campaigns may use this endpoint` | L’ID de campagne fourni n’est pas pour une campagne transactionnelle. |
+| `The external reference has been queued.  Please retry to obtain send_id.` | L'identifiant external_send_id a été créé récemment, essayez un nouvel identifiant external_send_id si vous avez l'intention d'envoyer un nouveau message. |
+| `Campaign does not exist` | L’ID fourni pour la campagne ne correspond pas à une campagne existante. |
+| `The campaign is archived. Unarchive the campaign in order for trigger requests to take effect.` | L’ID de campagne fourni correspond à une campagne archivée. |
+| `The campaign is paused. Resume the campaign in order for trigger requests to take effect.` | L’ID de campagne fourni correspond à une campagne en pause. |
+| `campaign_id must be a string of the campaign api identifier` | L’ID fourni pour la campagne n’est pas dans un format valide. |
+| `Error authenticating credentials` | La clé API fournie est invalide | 
+| `Invalid whitelisted IPs `| L'adresse IP qui envoie la demande ne figure pas sur la liste blanche des adresses IP (si elle est utilisée). | 
+| `You do not have permission to access this resource` | La clé API n’a pas la permission d’effectuer cette action |
+{: .reset-td-br-1 .reset-td-br-2}
+
+La plupart des endpoints Braze ont une implémentation de limites de débit qui renverra un code de réponse 429 si vous avez effectué trop de requêtes. L'endpoint d'envoi transactionnel fonctionne différemment : si vous dépassez la limite de débit qui vous a été attribuée, notre système continuera d'ingérer les appels API, de renvoyer les codes de réussite et d'envoyer les messages, mais ces derniers ne seront peut-être pas soumis à l'accord de niveau de service (SLA) contractuel pour la fonctionnalité. Veuillez nous contacter si vous désirez plus d’informations concernant cette fonctionnalité.
+
+## Postback de l’événement HTTP transactionnel
+
+Tous les e-mails transactionnels sont complétés par des postbacks de statut d’événement envoyés en tant que requête HTTP à l’URL spécifiée. Cela vous permet d’évaluer le statut du message en temps réel et de prendre des mesures pour atteindre l’utilisateur sur un autre canal si le message n’est pas reçu ou recourir à un système interne si Braze connaît une certaine latence.
+
+Afin d'associer les événements entrants à une instance particulière d'envoi, vous pouvez choisir de capturer et de stocker le site `dispatch_id` de Braze renvoyé dans la [réponse de l'API](#example-response), ou de transmettre votre propre identifiant dans le champ `external_send_id`. Un exemple de valeur que vous pouvez choisir de transmettre à ce champ peut être un ID de commande, où après avoir terminé la commande 1234, un message de confirmation de commande est envoyé à l’utilisateur par le biais de Braze, et l’`external_send_id : 1234` est inclus dans la demande. Tous les postbacks d’événements suivants, tels que `Sent` et `Delivered` comprennent `external_send_id : 1234` dans la charge utile vous permettant de confirmer que l’utilisateur a reçu correctement son e-mail de confirmation de commande.
+
+Pour commencer à utiliser le retour d'événement HTTP transactionnel, accédez à **Paramètres** > **Préférences e-mail** dans votre tableau de bord Braze et localisez la section **Retour d'état d'événement transactionnel.** Saisissez l'URL que vous souhaitez recevoir en retour.
+
+{% alert note %}
+Si vous utilisez l'[ancienne navigation]({{site.baseurl}}/navigation), cette page se trouve sous **Gérer les paramètres** > Paramètres de l'e-mail.
+{% endalert %}
+
+![]({% image_buster /assets/img/transactional_webhook_url.png %})
+
+### Corps de postback
+
+```json
+{
+  "dispatch_id": (string, a randomly-generated unique ID of the instance of this send),
+  "status": (string, Current status of message from the following message status table,
+  "metadata" : (object, additional information relating to the execution of an event)
+   {
+     "external_send_id" : (string, If provided at the time of the request, Braze will pass your internal identifier for this send for all postbacks),
+     "campaign_api_id" : (string, API identifier of this transactional campaign),
+     "received_at": (ISO 8601 DateTime string, Timestamp of when the request was received by Braze, only included for events with "sent" status),
+     "enqueued_at": (ISO 8601 DateTime string, Timestamp of when the request was enqueued by Braze, only included for events with "sent" status),
+     "executed_at": (ISO 8601 DateTime string, Timestamp of when the request was processed by Braze, only included for events with "sent" status),
+     "sent_at": (ISO 8601 DateTime string, Timestamp of when the request was sent to the ESP by Braze, only included for events with "sent" status),
+     "processed_at" : (ISO 8601 DateTime string, Timestamp the event was processed by the ESP, only included for events with "processed" status),
+     "delivered_at" : (ISO 8601 DateTime string, Timestamp the event was delivered to the user's inbox provider, only included for events with "processed" status),
+     "bounced_at" : (ISO 8601 DateTime string, Timestamp the event was bounced by the user's inbox provider, only included for events with "bounced" status),
+     "aborted_at" : (ISO 8601 DateTime string, Timestamp the event was Aborted by Braze, only included for events with "aborted" status),
+     "reason" : (string, The reason Braze or the Inbox provider was unable to process this message to the user, only included for events with "aborted" or "bounced" status),
+   }
+}
+```
+
+#### Statut du message
+
+|  État | Description |
+| ------------ | ----------- |
+| `sent` | Message envoyé avec succès à un partenaire d'envoi d'e-mail de Braze |
+| `processed` | Le partenaire d’envoi d’e-mail a reçu et préparé avec succès le message pour l’envoyer au fournisseur de messagerie de l’utilisateur |
+| `aborted` | Braze n’a pas réussi à envoyer le message, car l’adresse de l’utilisateur ne permet pas de recevoir des e-mails ou la logique d’interruption de Liquid a été appelée dans le corps du message. Tous les événements abandonnés comprennent un champ `reason` dans l’objet de métadonnées indiquant pourquoi le message a été abandonné |
+|`delivered`| Le message a été accepté par le fournisseur de messagerie de l’utilisateur |
+|`bounced`| Le message a été rejeté par le fournisseur de messagerie de l’utilisateur. Tous les événements renvoyés comprennent un champ `reason` dans l’objet de métadonnées reflétant le code d’erreur de rebond indiqué par le fournisseur de messagerie |
+{: .reset-td-br-1 .reset-td-br-2}
+
+### Exemple de postback
+```json
+
+// Sent Event
+{
+    "dispatch_id": "acf471119f7449d579e8089032003ded",
+    "status": "sent",
+    "metadata": {
+      "received_at": "2020-08-31T18:58:41.000+00:00",
+      "enqueued_at": "2020-08-31T18:58:41.000+00:00",
+      "executed_at": "2020-08-31T18:58:41.000+00:00",
+      "sent_at": "2020-08-31T18:58:42.000+00:00",
+      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
+      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
+    }
+}
+
+// Processed Event
+{
+    "dispatch_id": "acf471119f7449d579e8089032003ded",
+    "status": "processed",
+    "metadata": {
+      "processed_at": "2020-08-31T18:58:42.000+00:00",
+      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
+      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
+    }
+}
+
+// Aborted
+{
+    "dispatch_id": "acf471119f7449d579e8089032003ded",
+    "status": "aborted",
+    "metadata": {
+      "reason": "User not emailable",
+      "aborted_at": "2020-08-31T19:04:51.000+00:00",
+      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
+      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
+    }
+}
+
+// Delivered Event
+{
+    "dispatch_id": "acf471119f7449d579e8089032003ded",
+    "status": "delivered",
+    "metadata": {
+      "delivered_at": "2020-08-31T18:27:32.000+00:00",
+      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
+      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
+    }
+}
+
+// Bounced Event
+{
+    "dispatch_id": "acf471119f7449d579e8089032003ded",
+    "status": "bounced",
+    "metadata": {
+      "bounced_at": "2020-08-31T18:58:43.000+00:00",
+      "reason": "550 5.1.1 The email account that you tried to reach does not exist",
+      "campaign_api_id": "417220e4-5a2a-b634-7f7d-9ec891532368",
+      "external_send_id" : "34a2ceb3cf6184132f3d816e9984269a"
+    }
+}
+
+```
+
+
+{% endapi %}
+
diff --git a/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_triggered_campaigns.md b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_triggered_campaigns.md
new file mode 100644
index 00000000000..28ea8063246
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_triggered_campaigns.md
@@ -0,0 +1,182 @@
+---
+nav_title: "POST : Envoyez des campagnes via une réception/distribution déclenchée par l'API"
+article_title: "POST : Envoyez des campagnes via une réception/distribution déclenchée par l'API"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Envoyer des campagnes via une livraison déclenchée par API."
+
+---
+{% api %}
+# Envoyer des messages de campagne via une livraison déclenchée par API
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/campaigns/trigger/send
+{% endapimethod %}
+
+> Utilisez cet endpoint pour envoyer des messages immédiats et ponctuels à des utilisateurs désignés via une réception/distribution déclenchée par l'API. 
+
+La livraison déclenchée par API vous permet de stocker le contenu d’un message dans le tableau de bord de Braze, tout en indiquant quand et à qui un message est envoyé via votre API.
+
+Si vous souhaitez cibler un segment, un enregistrement de votre requête sera stocké dans la [console de développement](https://dashboard.braze.com/app_settings/developer_console/activitylog/). Pour envoyer des messages avec cet endpoint, vous devez disposer d'un [ID de campagne](https://www.braze.com/docs/api/identifier_types/) créé lorsque vous créez une [campagne déclenchée par l'API]({{site.baseurl}}/api/api_campaigns/).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#aef185ae-f591-452a-93a9-61d4bc023b05 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous devrez générer une clé API avec l’autorisation `campaigns.trigger.send`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='send endpoints' category='message endpoints' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "campaign_id": (required, string) see campaign identifier,
+  "send_id": (optional, string) see send identifier,
+  "trigger_properties": (optional, object) personalization key-value pairs that will apply to all users in this request,
+  "broadcast": (optional, boolean) see broadcast -- defaults to false on 8/31/17, must be set to true if "recipients" is omitted,
+  "audience": (optional, connected audience object) see connected audience,
+  // Including 'audience' will only send to users in the audience
+  "recipients": (optional, array; if not provided and broadcast is not set to `false`, message will send to the entire segment targeted by the campaign)
+    [
+      {
+      // Either "external_user_id" or "user_alias" is required. Requests must specify only one.
+      "user_alias": (optional, user alias object) user alias of user to receive message,
+      "external_user_id": (optional, string) external identifier of user to receive message,
+      "trigger_properties": (optional, object) personalization key-value pairs that will apply to this user (these key-value pairs will override any keys that conflict with the parent trigger_properties),
+      "send_to_existing_only": (optional, boolean) defaults to true, can't be used with user aliases; if set to `false`, an attributes object must also be included,
+      "attributes": (optional, object) fields in the attributes object will create or update an attribute of that name with the given value on the specified user profile before the message is sent and existing values will be overwritten
+    }
+  ],
+  "attachments": (optional, array) array of JSON objects that define the files you need attached, defined by "file_name" and "url",
+    [
+      {  
+       "file_name": (required, string) the name of the file you want to attach to your email, excluding the extension (for example, ".pdf"). Attach files up to 2 MB. This is required if you use "attachments",
+       "url": (required, string) the corresponding URL of the file you want to attach to your email. The file name's extension will be detected automatically from the URL defined, which should return the appropriate "Content-Type" as a response header. This is required if you use "attachments",
+      }
+    ]
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`campaign_id`|Requis|Chaîne de caractères|Voir [identifiant de campagne]({{site.baseurl}}/api/identifier_types/). |
+|`send_id`| Facultatif | Chaîne de caractères | Voir [identifiant d'envoi]({{site.baseurl}}/api/identifier_types/). |
+|`trigger_properties`| Facultatif | Objet | Voir les [propriétés du déclencheur]({{site.baseurl}}/api/objects_filters/trigger_properties_object/). Les paires clé-valeur de personnalisation qui s’appliquent à tous les utilisateurs de cette demande. |
+|`broadcast`| Facultatif | Valeur booléenne | Vous devez définir `broadcast` sur « true » lorsque vous envoyez un message à un segment entier qui est ciblé par une campagne ou un Canvas. Ce paramètre est défini sur Faux par défaut (au 31 août 2017). <br><br> Si `broadcast` est défini sur « true », une liste `recipients` ne peut pas être incluse. Cependant, faites attention lors de la configuration de `broadcast: true` car en configurant involontairement cet indicateur, vous pourriez envoyer votre message à une audience plus importante que prévue. |
+|`audience`| Facultatif | Objet Audience connectée| Voir [audience connectée]({{site.baseurl}}/api/objects_filters/connected_audience/). |
+|`recipients`| Facultatif | Tableau | Voir [objet destinataire]({{site.baseurl}}/api/objects_filters/recipient_object/).<br><br>Si `send_to_existing_only` est `false`, un objet Attribut doit être inclus.<br><br>Si `recipients` n'est pas fourni et que `broadcast` a la valeur "true", le message sera envoyé à l'ensemble du segment ciblé par la campagne. |
+|`attachments`| Facultatif | Tableau | Si `broadcast` est défini comme vrai, la liste `attachments` ne peut pas être incluse. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+- Le tableau des destinataires peut contenir jusqu’à 50 objets, avec chaque objet contenant une seule chaîne de caractères `external_user_id` et objet `trigger_properties`.
+- Quand `send_to_existing_only` est défini sur `true`, Braze envoie uniquement le message aux utilisateurs existants. Cependant, cet indicateur ne peut pas être utilisé avec les alias utilisateur. 
+- Lorsque `send_to_existing_only` est `false`, un attribut doit être inclus. Braze créera un utilisateur avec le site `id` et les attributs avant d'envoyer le message.
+
+Le statut du groupe d'abonnement d'un utilisateur peut être mis à jour en incluant un paramètre `subscription_groups` dans l’objet `attributes`. Pour plus de détails, consultez [Objet Attributs d’utilisateur]({{site.baseurl}}/api/objects_filters/user_attributes_object).
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/campaigns/trigger/send' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "campaign_id": "campaign_identifier",
+  "send_id": "send_identifier",
+  "trigger_properties": "",
+  "broadcast": false,
+  "audience": {
+    "AND": [
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "eye_color",
+          "comparison": "equals",
+          "value": "blue"
+        }
+      },
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "favorite_foods",
+          "comparison": "includes_value",
+          "value": "pizza"
+        }
+      },
+      {
+        "OR": [
+          {
+            "custom_attribute": {
+              "custom_attribute_name": "last_purchase_time",
+              "comparison": "less_than_x_days_ago",
+              "value": 2
+            }
+          },
+          {
+            "push_subscription_status": {
+              "comparison": "is",
+              "value": "opted_in"
+            }
+          }
+        ]
+      },
+      {
+        "email_subscription_status": {
+          "comparison": "is_not",
+          "value": "subscribed"
+        }
+      },
+      {
+        "last_used_app": {
+          "comparison": "after",
+          "value": "2019-07-22T13:17:55+0000"
+        }
+      }
+    ]
+  },
+  "recipients": [
+    {
+      "user_alias": {
+        "alias_name" : "example_name",
+        "alias_label" : "example_label"
+      },
+      "external_user_id": "external_user_identifier",
+      "trigger_properties": "",
+      "send_to_existing_only": true,
+      "attributes": {
+        "first_name" : "Alex"
+      }
+    }
+  ],
+  "attachments": [
+    {
+      "file_name" : "YourFileName",
+      "url" : "https://exampleurl.com/YourFileName.pdf"
+    }
+  ] 
+}'
+```
+
+## Informations relatives à la réponse
+
+Les réponses des endpoints d’envoi de messages incluront le `dispatch_id` du message pour y faire référence lors de l’envoi. Le `dispatch_id` est l'ID de l'envoi de messages, un ID unique pour chaque transmission envoyée depuis Braze. Lorsque vous utilisez cet endpoint, vous recevez un seul `dispatch_id` pour un ensemble complet d’utilisateurs regroupés. Pour plus d'informations sur `dispatch_id`, consultez notre documentation sur le [comportement du Dispatch ID]({{site.baseurl}}/help/help_articles/data/dispatch_id/).
+
+## Endpoint Créer un envoi
+
+**Utilisation de l'objet Attributs dans les campagnes**
+
+Braze dispose d'un objet d'envoi de messages appelé `attributes` qui vous permettra d'ajouter, de créer ou de mettre à jour les attributs et les valeurs d'un utilisateur avant de lui envoyer une campagne déclenchée par l'API. En utilisant l’endpoint `campaign/trigger/send` car cet appel d'API traitera l'objet Attributs d’utilisateur avant de traiter et d'envoyer la campagne. Cela permet de minimiser le risque de problèmes causés par des [conditions de concurrence]({{site.baseurl}}/help/best_practices/race_conditions/). 
+
+{% alert important %}
+Vous recherchez la version Canvas de cet endpoint ? Consultez la rubrique [Envoi de messages canvas via la réception/distribution déclenchée par l'API]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/#create-send-endpoint).
+{% endalert %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_triggered_canvases.md b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_triggered_canvases.md
new file mode 100644
index 00000000000..16640463287
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/messaging/send_messages/post_send_triggered_canvases.md
@@ -0,0 +1,180 @@
+---
+nav_title: "POST : Envoyer des messages Canvas via la livraison déclenchée par API"
+article_title: "POST : Envoyer des messages Canvas via la livraison déclenchée par API"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Envoyer des Canvas via une livraison déclenchée par API."
+
+---
+{% api %}
+# Envoyer des messages Canvas via une livraison déclenchée par API
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/canvas/trigger/send
+{% endapimethod %}
+
+> Utilisez cet endpoint pour envoyer des messages Canvas via la livraison déclenchée par API. 
+
+La livraison déclenchée par API vous permet de stocker le contenu d’un message dans le tableau de bord de Braze, tout en indiquant quand et à qui un message est envoyé via votre API.
+
+Avant de pouvoir envoyer des messages avec cet endpoint, vous devez disposer d'un [ID Canvas]({{site.baseurl}}/api/identifier_types/#canvas-api-identifier) (qui est créé lorsque vous créez un Canvas).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#c9a8a5fe-a101-4755-99f2-73aa8fc146fe {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous devrez générer une clé API avec l’autorisation `canvas.trigger.send`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='send endpoints' category='message endpoints' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "canvas_id": (required, string) see Canvas identifier,
+  "canvas_entry_properties": (optional, object) personalization key-value pairs that will apply to all users in this request,
+  "broadcast": (optional, boolean) see Broadcast -- defaults to false on 8/31/17, must be set to true if `recipients` is omitted,
+  "audience": (optional, connected audience object) see connected audience,
+  // Including 'audience' will only send to users in the audience
+  "recipients": (optional, array; if not provided and broadcast is not set to 'false', message will send to the entire segment targeted by the Canvas)
+    [{
+      // Either "external_user_id" or "user_alias" is required. Requests must specify only one.
+      "user_alias": (optional, user alias object) user alias of user to receive message,
+      "external_user_id": (optional, string) external identifier of user to receive message,
+      "canvas_entry_properties": (optional, object) personalization key-value pairs that will apply to this user (these key-value pairs will override any keys that conflict with the parent `canvas_entry_properties`)
+      "send_to_existing_only": (optional, boolean) defaults to true, can't be used with user aliases
+      "attributes": (optional, object) fields in the attributes object will create or update an attribute of that name with the given value on the specified user profile before the message is sent and existing values will be overwritten
+    }],
+    ...
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`canvas_id`| Requis | Chaîne de caractères | Voir [Identifiant Canvas]({{site.baseurl}}/api/identifier_types/). |
+|`canvas_entry_properties`| Facultatif | Objet | Voir [Propriétés de l'entrée dans le canevas.]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/) Les paires clé-valeur de personnalisation qui s’appliquent à tous les utilisateurs de cette demande. La limite maximale de taille de l’objet Propriétés d’entrées de Canvas est de 50 Ko. |
+|`broadcast`| Facultatif | Valeur booléenne | Vous devez définir `broadcast` sur « true » lorsque vous envoyez un message à un segment entier qui est ciblé par une campagne ou un Canvas. Ce paramètre est défini sur Faux par défaut (au 31 août 2017). <br><br> Si `broadcast` est défini sur « true », une liste `recipients` ne peut pas être incluse. Cependant, faites attention lors de la configuration de `broadcast: true` car en configurant involontairement cet indicateur, vous pourriez envoyer votre message à une audience plus importante que prévue. |
+|`audience`| Facultatif| Objet Audience connectée | Voir l'[audience connectée]({{site.baseurl}}/api/objects_filters/connected_audience/). |
+|`recipients`| Facultatif | Tableau | Voir l'[objet Destinataires]({{site.baseurl}}/api/objects_filters/recipient_object/). Si non renseigné et que `broadcast` est défini sur Vrai, le message sera envoyé au segment entier ciblé par Canvas.<br><br> Le tableau `recipients` peut contenir jusqu’à 50 objets, avec chaque objet contenant une seule chaîne de caractères `external_user_id` et objet `canvas_entry_properties`. `external_user_id` ou `user_alias` est requis pour cet appel. Les demandes ne doivent en spécifier qu’un seul des deux. <br><br> Quand `send_to_existing_only` est défini sur `true`, Braze envoie uniquement le message aux utilisateurs existants, mais cet indicateur ne peut pas être utilisé avec les alias utilisateur. Quand `send_to_existing_only` est défini sur `false` et qu’un utilisateur avec l’`id` donné n’existe pas, Braze crée un utilisateur avec cet ID et cet attribut avant d’envoyer le message.|
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+Les clients qui utilisent l'API pour des appels de serveur à serveur peuvent avoir besoin d'autoriser l'URL API appropriée s'ils sont derrière un pare-feu.
+
+{% alert note %}
+Si vous incluez des utilisateurs spécifiques dans votre appel d’API et un segment cible dans le tableau de bord, le message sera envoyé spécifiquement aux profils d’utilisateur qui sont dans l’appel d’API et qui correspondent aux filtres de segment.
+{% endalert %}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/canvas/trigger/send' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "canvas_id": "canvas_identifier",
+  "canvas_entry_properties": {"product_name" : "shoes", "product_price" : 79.99},
+  "broadcast": false,
+  "audience": {
+    "AND": [
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "eye_color",
+          "comparison": "equals",
+          "value": "blue"
+        }
+      },
+      {
+        "custom_attribute": {
+          "custom_attribute_name": "favorite_foods",
+          "comparison": "includes_value",
+          "value": "pizza"
+        }
+      },
+      {
+        "OR": [
+          {
+            "custom_attribute": {
+              "custom_attribute_name": "last_purchase_time",
+              "comparison": "less_than_x_days_ago",
+              "value": 2
+            }
+          },
+          {
+            "push_subscription_status": {
+              "comparison": "is",
+              "value": "opted_in"
+            }
+          }
+        ]
+      },
+      {
+        "email_subscription_status": {
+          "comparison": "is_not",
+          "value": "subscribed"
+        }
+      },
+      {
+        "last_used_app": {
+          "comparison": "after",
+          "value": "2019-07-22T13:17:55+0000"
+        }
+      }
+    ]
+  },
+  "recipients": [
+    {
+      "user_alias": {
+        "alias_name" : "example_name",
+        "alias_label" : "example_label"
+      },
+      "external_user_id": "user_identifier",
+      "trigger_properties": "",
+      "canvas_entry_properties": "",
+      "send_to_existing_only": true,
+      "attributes": {
+          "first_name" : "Alex"
+      }
+    }
+  ]
+}'
+```
+
+## Informations relatives à la réponse
+
+Les réponses des endpoints d’envoi de messages incluront le `dispatch_id` du message pour y faire référence lors de l’envoi. Le `dispatch_id` est l’ID de distribution du message (ID unique pour chaque « transmission » envoyée depuis la plateforme Braze). Consultez [Comportement du Dispatch ID]({{site.baseurl}}/help/help_articles/data/dispatch_id/) pour plus d’informations.
+
+### Exemple de réponse réussie
+
+Le code d'état 201 pourrait renvoyer le corps de réponse suivant. Si le Canvas est archivé, arrêté ou en pause, le Canvas ne sera pas envoyé via ce point de terminaison. 
+
+```
+{
+  "notice": "The Canvas is paused. Resume the Canvas to ensure trigger requests will take effect.", 
+  "dispatch_id": "example_dispatch_id", 
+  "message": "success"
+}
+```
+
+Si votre Canvas est archivé, vous verrez ce message `notice`: "The Canvas" est archivé. Désarchivez le Canvas pour vous assurer que les demandes de déclencheurs prendront effet." Si votre Canvas n'est pas actif, vous verrez ce message `notice`: "La toile est en pause. Reprenez le Canvas pour vous assurer que les demandes de déclencheurs prendront effet."
+
+## Endpoint Créer un envoi
+
+**Utilisation de l'objet Attributs dans Canvas**
+
+Braze dispose d’un objet Messagerie appelé `Attributes` qui vous permet d’ajouter, de créer ou de mettre à jour les attributs et les valeurs d’un utilisateur avant de lui envoyer un Canvas déclenché par API en utilisant l’endpoint `canvas/trigger/send`, car cet appel d’API traitera l’objet Attributs utilisateur avant qu’il ne traite et envoie le Canvas. Cela permet de minimiser le risque de problèmes causés par des [conditions de concurrence]({{site.baseurl}}/help/best_practices/race_conditions/).
+
+{% alert important %}
+Vous recherchez la version des campagnes de cet endpoint ? Consultez la rubrique [Envoi de messages de campagne via la réception/distribution déclenchée par l'API]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns/).
+{% endalert %}
+
+{% endapi %}
+
diff --git a/_lang/fr_fr/_api/endpoints/preference_center.md b/_lang/fr_fr/_api/endpoints/preference_center.md
new file mode 100644
index 00000000000..8329f6c1f4f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/preference_center.md
@@ -0,0 +1,30 @@
+---
+nav_title: Centre de préférences
+article_title: Endpoints du centre de préférences
+search_tag: Endpoint
+page_order: 4
+layout: dev_guide
+
+description: "Cette page d’accueil répertorie les endpoints Braze du centre de préférences."
+page_type: landing
+
+guide_top_header: "Endpoints du centre de préférences"
+guide_top_text: "Utilisez les endpoints de cette section pour créer un centre de préférences, c'est-à-dire un site web hébergé par Braze qui peut afficher le statut de l'abonnement de votre utilisateur et les statuts du groupe d'abonnement. À l'aide de HTML et de CSS, votre équipe de développeurs peut créer votre centre de préférences de manière à ce que le style de la page corresponde aux lignes directrices de votre marque.<br><br>Consultez l'<a href='/docs/user_guide/message_building_by_channel/email/preference_center/overview/'>aperçu du centre</a> de préférences pour plus de détails sur la façon de créer et de personnaliser votre centre de préférences."
+
+guide_featured_list:
+  - name: "GET : Créer un URL de centre de préférences"
+    link: /docs/api/endpoints/preference_center/get_create_url_preference_center/
+    image: /assets/img/braze_icons/tool-01.svg
+  - name: "GET : Répertorier les centres de préférences"
+    link: /docs/api/endpoints/preference_center/get_list_preference_center/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "GET : Afficher les détails du centre de préférences"
+    link: /docs/api/endpoints/preference_center/get_view_details_preference_center/
+    image: /assets/img/braze_icons/mail-04.svg
+  - name: "POST : Créer un centre de préférences"
+    link: /docs/api/endpoints/preference_center/post_create_preference_center/
+    image: /assets/img/braze_icons/check-square-broken.svg
+  - name: "PUT : Mettre à jour un centre de préférences"
+    link: /docs/api/endpoints/preference_center/put_update_preference_center/
+    image: /assets/img/braze_icons/check-square-broken.svg
+---
diff --git a/_lang/fr_fr/_api/endpoints/preference_center/get_create_url_preference_center.md b/_lang/fr_fr/_api/endpoints/preference_center/get_create_url_preference_center.md
new file mode 100644
index 00000000000..1c003f010e0
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/preference_center/get_create_url_preference_center.md
@@ -0,0 +1,65 @@
+---
+nav_title: "GET : Générer l’URL du centre de préférences"
+article_title: "GET : Générer l’URL du centre de préférences"
+search_tag: Endpoint
+page_order: 1
+layout: api_page
+page_type: reference
+description: "Cet article précise des détails concernant l’endpoint de Braze Générer l’URL du centre de préférences."
+
+---
+{% api %}
+# Générer l’URL du centre de préférences
+{% apimethod get %}
+/preference_center/v1/{preferenceCenterExternalID}/url/{userID}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour générer une URL pour un centre de préférences. 
+
+Chaque URL de centre de préférence est unique pour un utilisateur.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#0bc750ff-068e-4391-897e-6eddca2561cd {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `preference_center.user.get`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 1 000 requêtes par minute, par espace de travail.
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`preferenceCenterExternalID`| Requis | Chaîne de caractères | L’ID de votre centre de préférences. |
+|`userID`| Requis | Chaîne de caractères | L'ID utilisateur. |
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`preference_center_api_id`| Requis | Chaîne de caractères | L’ID de votre centre de préférences. |
+|`external_id`| Requis | Chaîne de caractères | L’ID externe pour un utilisateur. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/preference_center/v1/$preference_center_external_id/url/$user_external_id' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE'
+```
+
+## Réponse 
+
+```json
+{
+  "preference_center_url": "https://www.example.com/preferences"
+}
+```
+
+{% endapi %}
+
+{% alert note %}
+Ce point de terminaison génère uniquement des URL pour le nouveau centre de préférences (comme les centres de préférences créés via l'API ou l'éditeur par glisser-déposer).
+{% endalert %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/preference_center/get_list_preference_center.md b/_lang/fr_fr/_api/endpoints/preference_center/get_list_preference_center.md
new file mode 100644
index 00000000000..e549abef801
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/preference_center/get_list_preference_center.md
@@ -0,0 +1,73 @@
+---
+nav_title: "GET : Répertorier les centres de préférences"
+article_title: "GET : Répertorier les centres de préférences"
+search_tag: Endpoint
+page_order: 2
+layout: api_page
+page_type: reference
+description: "Cet article précise des détails concernant l’endpoint de Braze Répertorier les centres de préférences."
+
+---
+{% api %}
+# Répertorier les centres de préférences
+{% apimethod get %}
+/preference_center/v1/list
+{% endapimethod %}
+
+> Utilisez cet endpoint pour répertorier vos centres de préférences disponibles.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#dd8f6667-5eba-4e19-a29e-ba74644c0b8e {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `preference_center.list`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 1 000 requêtes par minute, par espace de travail.
+
+## Paramètres de chemin et de requête
+
+Cet endpoint n’a pas de paramètres de chemin ni de requête.
+
+## Exemple de demande
+
+```
+curl --location -g --request GET https://rest.iad-01.braze.com/preference_center/v1/list \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+```json
+{
+  "preference_centers": [
+    {
+      "name": "My Preference Center 1",
+      "preference_center_api_id": "preference_center_api_id",
+      "created_at": "2022-08-17T15:46:10Z",
+      "updated_at": "2022-08-17T15:46:10Z"
+    },
+    {
+      "name": "My Preference Center 2",
+      "preference_center_api_id": "preference_center_api_id",
+      "created_at": "2022-08-19T11:13:06Z",
+      "updated_at": "2022-08-19T11:13:06Z"
+    },
+    {
+      "name": "My Preference Center 3",
+      "preference_center_api_id": "preference_center_api_id",
+      "created_at": "2022-08-19T11:30:50Z",
+      "updated_at": "2022-08-19T11:30:50Z"
+    },
+    {
+      "name": "My Preference Center 4",
+      "preference_center_api_id": "preference_center_api_id",
+      "created_at": "2022-09-13T20:41:34Z",
+      "updated_at": "2022-09-13T20:41:34Z"
+    }
+  ]
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/preference_center/get_view_details_preference_center.md b/_lang/fr_fr/_api/endpoints/preference_center/get_view_details_preference_center.md
new file mode 100644
index 00000000000..0fc7468544a
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/preference_center/get_view_details_preference_center.md
@@ -0,0 +1,64 @@
+---
+nav_title: "GET : Afficher les détails du centre de préférences"
+article_title: "GET : Afficher les détails du centre de préférences"
+search_tag: Endpoint
+page_order: 3
+layout: api_page
+page_type: reference
+description: "Cet article précise des détails concernant l’endpoint de Braze Afficher les détails du centre de préférences."
+
+---
+{% api %}
+# Afficher les détails du centre de préférences
+{% apimethod get %}
+/preference_center/v1/{preferenceCenterExternalID}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour afficher les détails de vos centres de préférences, y compris la date de leur création et de leurs mises à jour.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#6a47fd7c-2997-4832-aedb-d101a2dd03a5 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `preference_center.get`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 1 000 requêtes par minute, par espace de travail.
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`preferenceCenterExternalID`| Requis | Chaîne de caractères | L’ID de votre centre de préférences. |
+
+## Paramètres de demande
+
+Cet endpoint n’a pas de paramètres de requête.
+
+## Exemple de demande
+
+```
+curl --location -g --request GET https://rest.iad-01.braze.com/preference_center/v1/preference_center_external_id \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse 
+```json 
+{
+  "name": "My Preference Center",
+  "preference_center_api_id": "preference_center_api_id",
+  "created_at": "example_time_created",
+  "updated_at": "example_time_updated",
+  "preference_center_title": "Example preference center title",
+  "preference_center_page_html": "HTML for preference center here",
+  "confirmation_page_html": "HTML for confirmation page here",
+  "redirect_page_html": null,
+  "preference_center_options": {
+    "meta-viewport-content": "width=device-width, initial-scale=2"
+  },
+  "state": "active"
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/preference_center/post_create_preference_center.md b/_lang/fr_fr/_api/endpoints/preference_center/post_create_preference_center.md
new file mode 100644
index 00000000000..86881db0ec6
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/preference_center/post_create_preference_center.md
@@ -0,0 +1,273 @@
+---
+nav_title: "POST : Créer un centre de préférences"
+article_title: "POST : Créer un centre de préférences"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article précise des détails concernant l’endpoint de Braze Créer un centre de préférences."
+
+---
+{% api %}
+# Créer un centre de préférences
+{% apimethod post %}
+/preference_center/v1
+{% endapimethod %}
+
+> Utilisez cet endpoint pour créer un centre de préférences permettant aux utilisateurs de gérer leurs préférences en matière de notification pour vos campagnes d'e-mail. Reportez-vous à la section [Créer un centre de préférences via l'API]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center/overview/#create-a-preference-center-via-api) pour savoir comment créer un centre de préférences généré par l'API.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#e15d7065-2cbc-4eb3-ae16-32efe43357a6 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `preference_center.update`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 10 requêtes par minute, par espace de travail.
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "name": "string",
+  "preference_center_title": "string",
+  "preference_center_page_html": "string",
+  "confirmation_page_html": "string",
+  "state": (optional) Choose `active` or `draft`. Defaults to `active` if not specified,
+  "options": {
+    "meta-viewport-content": "string", (optional) Only the `content` value of the meta tag
+  }
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`name`| Requis | Chaîne de caractères | Le nom du centre de préférences qui se conforme aux exigences suivantes : <br>\- Comprend uniquement des lettres, des chiffres, des traits d’union et des traits de soulignement <br>\- N’a pas d’espaces |
+|`preference_center_title`| Facultatif | Chaîne de caractères | Le titre des pages du centre de préférences et de confirmation. Si aucun titre n’est précisé, le titre des pages passera par défaut à « Centre de préférences ». |
+|`preference_center_page_html`| Requis | Chaîne de caractères | L’HTML de la page du centre de préférences. |
+|`confirmation_page_html`| Requis | Chaîne de caractères | L’HTML de la page de confirmation. |
+|`state` | Facultatif | Chaîne de caractères | Choisir `active` ou `draft`. Défini par défaut sur `active` si cela n’est pas spécifié. |
+|`options` | Facultatif | Objet | Attributs : `meta-viewport-content`. Le cas échéant, une étiquette méta `viewport` sera ajoutée à la page avec `content= <value of attribute>`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+{% alert note %}
+Le nom du centre de préférences ne peut pas être modifié après sa création.
+{% endalert %}
+
+### Balises Liquid
+
+Référez-vous aux balises Liquid suivantes qui peuvent être intégrées à votre HTML pour générer un état d’abonnement de l’utilisateur sur la page du centre de préférences.
+
+{% raw %}
+
+#### État d’abonnement utilisateur
+
+| Liquid | Description |
+| --------- | ---------|
+|`{{subscribed_state.${email_global}}}`| Obtenir l'état global de l'abonnement à l'e-mail pour l'utilisateur (tel que "opted_in", "subscribed", ou "unsubscribed"). |
+|`{{subscribed_state.${<subscription_group_id>}}}`| Obtenir l'état abonné du groupe d'abonnement spécifié pour l'utilisateur (tel que "abonné" ou "désabonné"). |
+{: .reset-td-br-1 .reset-td-br-2}
+
+#### Saisies de formulaire et action
+
+| Liquid | Description |
+| --------- | ---------|
+|`{% form_field_name :email_global_state %}`| Indique qu’un élément de saisie de formulaire particulier correspond à l’état global d’abonnement aux e-mails de l’utilisateur. L'état de sélection de l'utilisateur doit être "opted_in", "abonné" ou "désabonné" lorsque le formulaire est abonné avec des données de sélection pour l'état d'abonnement global à l'e-mail. S'il s'agit d'une case à cocher, l'utilisateur sera soit « opted_in », soit « désabonné ». Pour un input caché, l’état « abonné » sera aussi valide. |
+|`{% form_field_name :subscription_group <subscription_group_id> %}`| Indique qu’un élément de saisie de formulaire particulier correspond à un groupe d’abonnement particulier. L’état de sélection de l’utilisateur devrait être « abonné » ou « désabonné » lorsque le formulaire est soumis avec des données de sélection pour un groupe d’abonnement particulier. |
+|`{{preference_center_submit_url}}`| Produit une URL pour la soumission du formulaire. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endraw %}
+
+## Exemple de réponses
+
+### Créer un centre de préférences
+
+{% raw %}
+```
+{
+  "preference_center_api_id": "preference_center_api_id_example",
+  "liquid_tag": "{{preference_center.${MyPreferenceCenter2022-09-22}}}",
+  "created_at": "2022-09-22T18:28:07+00:00",
+  "message": "success"
+}
+```
+{% endraw %}
+
+### HTML avec entrées de formulaire 
+
+{% raw %}
+```
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta name="robots" content="noindex" />
+    <title>Email Preferences</title>
+    <script type="text/javascript">
+      window.onload = () => {
+        const globalUnsubscribed = '{{subscribed_state.${email_global}}}' == "unsubscribed";
+        const globalSubscribedValue = '{{subscribed_state.${email_global}}}' == "opted_in" ? "opted_in" : "subscribed";
+        const idStates = [
+          // input format: [API_ID, '{{subscribed_state.${API_ID}}}' == "subscribed"][]
+          ['3d2ae07a-f2ff-4318-bdff-e394f2d3a4ec', '{{subscribed_state.${3d2ae07a-f2ff-4318-bdff-e394f2d3a4ec}}}' == 'subscribed'],['7d89bdc3-4aa1-4592-8b8a-4c8b7161c875', '{{subscribed_state.${7d89bdc3-4aa1-4592-8b8a-4c8b7161c875}}}' == 'subscribed'],['5444d32e-2815-4258-964c-b9690d4ccb94', '{{subscribed_state.${5444d32e-2815-4258-964c-b9690d4ccb94}}}' == 'subscribed']
+        ];
+
+        const setState = (id, subscribed) => {
+          document.querySelector(`#checkbox-${id}`).checked = subscribed;
+          document.querySelector(`#value-${id}`).value = subscribed ? "subscribed" : "unsubscribed";
+        };
+        const setGlobal = (unsubscribed) => {
+          document.querySelector(`#checkbox-global`).checked = unsubscribed;
+          document.querySelector(`#value-global`).value = unsubscribed ? "unsubscribed" : globalSubscribedValue;
+          idStates.forEach(([id]) => {
+            document.querySelector(`#checkbox-${id}`).disabled = unsubscribed;
+          });
+        };
+
+        idStates.forEach(([id, state]) => {
+          setState(id, state);
+          document.querySelector(`#checkbox-${id}`).onchange = ((e) => {
+            setState(id, e.target.checked);
+          });
+        });
+        setGlobal(globalUnsubscribed);
+        document.querySelector(`#checkbox-global`).onchange = ((e) => {
+          setGlobal(e.target.checked);
+        });
+      };
+    </script>
+    <style>
+      body {
+        background: #fff;
+        margin: 0;
+      }
+      @media (max-width: 600px) {
+        .main-container {
+          margin-top: 0;
+          width: 100%;
+        }
+        .main-container .content .email-input {
+          width: 100%;
+        }
+      }
+    </style>
+  </head>
+  <body class="vsc-initialized" style="margin: 0" bgcolor="#fff">
+    <div
+      class="main-container"
+      style="
+        background-color: #fff;
+        color: #333335;
+        font-family:
+          Sailec W00 Medium,
+          helvetica,
+          arial,
+          sans-serif;
+        margin-left: auto;
+        margin-right: auto;
+        margin-top: 30px;
+        width: 600px;
+        padding: 15px 0 5px;
+      "
+    >
+      <div class="content" style="margin-left: 20px; margin-right: 20px">
+        
+        <div>
+          <h1
+            style="color: #3accdd; font-size: 27px; font-weight: 400; margin-bottom: 40px; margin-top: 0"
+            align="center"
+          >
+            Manage Email Preferences
+          </h1>
+          <p class="intro-text" style="font-size: 14px; margin-bottom: 20px" align="center">
+            Select the emails that you want to receive.
+          </p>
+        </div>
+
+        <form action="{{ preference_center_submit_url }}" method="post" accept-charset="UTF-8">
+          <div>
+            <h3 style="font-size: 15px; margin-bottom: 15px; margin-left: 5px; margin-top: 40px">
+              Email Address: <span class="displayed-email" style="font-weight: 400">{{${email_address}}}</span>
+            </h3>
+          </div>
+          <div class="subscription-groups-holder" style="margin-bottom: 20px"><div class="row" style="border-top-width: 1px; border-top-color: #dddde2; border-top-style: solid; background-color: #fff; padding: 15px 10px 14px;border-bottom: 1px solid rgb(221, 221, 226);">
+  <label style="color: #27368f; cursor: pointer; font-size: 15px; font-weight: 700;">
+    <input type="checkbox" id="checkbox-3d2ae07a-f2ff-4318-bdff-e394f2d3a4ec" class="sub_group" style="margin-right: 4px;">
+    <input type="hidden" name="{% form_field_name :subscription_group 3d2ae07a-f2ff-4318-bdff-e394f2d3a4ec %}" id="value-3d2ae07a-f2ff-4318-bdff-e394f2d3a4ec" />
+    Sub Group 1
+  </label>
+  <p class="subscription-group" style="font-size: 13px; line-height: 1.4em; min-height: 20px; padding-right: 20px; margin: 0 0 3px 23px;">
+    
+  </p>
+</div>
+<div class="row" style="border-top-width: 1px; border-top-color: #dddde2; border-top-style: solid; background-color: #fff; padding: 15px 10px 14px;border-bottom: 1px solid rgb(221, 221, 226);">
+  <label style="color: #27368f; cursor: pointer; font-size: 15px; font-weight: 700;">
+    <input type="checkbox" id="checkbox-7d89bdc3-4aa1-4592-8b8a-4c8b7161c875" class="sub_group" style="margin-right: 4px;">
+    <input type="hidden" name="{% form_field_name :subscription_group 7d89bdc3-4aa1-4592-8b8a-4c8b7161c875 %}" id="value-7d89bdc3-4aa1-4592-8b8a-4c8b7161c875" />
+    Sub Group 2
+  </label>
+  <p class="subscription-group" style="font-size: 13px; line-height: 1.4em; min-height: 20px; padding-right: 20px; margin: 0 0 3px 23px;">
+    
+  </p>
+</div>
+<div class="row" style="border-top-width: 1px; border-top-color: #dddde2; border-top-style: solid; background-color: #fff; padding: 15px 10px 14px;border-bottom: 1px solid rgb(221, 221, 226);">
+  <label style="color: #27368f; cursor: pointer; font-size: 15px; font-weight: 700;">
+    <input type="checkbox" id="checkbox-5444d32e-2815-4258-964c-b9690d4ccb94" class="sub_group" style="margin-right: 4px;">
+    <input type="hidden" name="{% form_field_name :subscription_group 5444d32e-2815-4258-964c-b9690d4ccb94 %}" id="value-5444d32e-2815-4258-964c-b9690d4ccb94" />
+    Sub Group 3
+  </label>
+  <p class="subscription-group" style="font-size: 13px; line-height: 1.4em; min-height: 20px; padding-right: 20px; margin: 0 0 3px 23px;">
+    
+  </p>
+</div>
+</div>
+
+          <div class="unsub-all" style="cursor: pointer; font-size: 13px; margin-bottom: 20px" align="center">
+            <label>
+              <input type="checkbox" id="checkbox-global" />
+              <input
+                type="hidden"
+                id="value-global"
+                name="{% form_field_name :email_global_state %}"
+              />
+              <i> Unsubscribe from all of the above types of emails </i>
+            </label>
+          </div>
+
+          <div>
+            <input
+              class="save"
+              type="submit"
+              value="Save"
+              style="
+                background-color: rgb(71, 204, 163);
+                color: #fff;
+                cursor: pointer;
+                display: block;
+                font-size: 16px;
+                text-align: center;
+                text-decoration: none;
+                width: 200px;
+                margin: 0 auto 20px;
+                padding: 12px;
+                border-style: none;
+              "
+            />
+          </div>
+        </form>
+      </div>
+    </div>
+  </body>
+</html>
+```
+{% endraw %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/preference_center/put_update_preference_center.md b/_lang/fr_fr/_api/endpoints/preference_center/put_update_preference_center.md
new file mode 100644
index 00000000000..1ae2648bb18
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/preference_center/put_update_preference_center.md
@@ -0,0 +1,97 @@
+---
+nav_title: "PUT : Mettre à jour un centre de préférences"
+article_title: "PUT : Mettre à jour un centre de préférences"
+search_tag: Endpoint
+page_order: 5
+layout: api_page
+page_type: reference
+description: "Cet article précise des détails concernant l’endpoint de Braze Mettre à jour un centre de préférences."
+
+---
+{% api %}
+# Mettre à jour un centre de préférences
+{% apimethod put %}
+/preference_center/v1/{preferenceCenterExternalID}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour un centre de préférences.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#bf1b43db-3f1b-461f-ad9a-2fbe35b804d7 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `preference_center.update`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 10 requêtes par minute, par espace de travail.
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`preferenceCenterExternalID`| Requis | Chaîne de caractères | L’ID de votre centre de préférences. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```
+{
+  "name": "preference_center_name",
+  "preference_center_title": "string",
+  "preference_center_page_html": "string",
+  "confirmation_page_html": "string",
+  "options": {
+    "meta-viewport-content": "string", (optional) Only the `content` value of the meta tag
+  }
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`preference_center_page_html`| Requis | Chaîne de caractères | L’HTML de la page du centre de préférences. |
+|`preference_center_title`| Facultatif | Chaîne de caractères | Le titre des pages du centre de préférences et de confirmation. Si aucun titre n’est précisé, le titre des pages passera par défaut à « Centre de préférences ». |
+|`confirmation_page_html`| Requis | Chaîne de caractères | L’HTML de la page de confirmation. |
+|`state` | Facultatif | Chaîne de caractères | Choisir `active` ou `draft`.|
+|`options` | Facultatif | Objet | Attributs : `meta-viewport-content`. Le cas échéant, une étiquette méta `viewport` sera ajoutée à la page avec `content= <value of attribute>`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+{% raw %}
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/preference_center/v1/{preferenceCenterExternalId}' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+--data-raw '{
+  "name": "Example",
+  "preference_center_title": "Example Preference Center Title",
+  "preference_center_page_html": "HTML for preference center here",
+  "confirmation_page_html": "HTML here with a message to users here",
+  "state": "active"
+}
+'
+```
+{% endraw %}
+
+## Exemple de réponse
+{% raw %}
+```
+{
+  "preference_center_api_id": "8efc52aa-935e-42b7-bd6b-98f43bb9b0f1",
+  "created_at": "2022-09-22T18:28:07Z",
+  "updated_at": "2022-09-22T18:32:07Z",
+  "message": "success"
+}
+```
+{% endraw %}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/scim.md b/_lang/fr_fr/_api/endpoints/scim.md
new file mode 100644
index 00000000000..0f6eeabedff
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/scim.md
@@ -0,0 +1,33 @@
+---
+nav_title: SCIM
+article_title: Endpoints SCIM
+search_tag: Endpoint
+page_order: 5
+layout: dev_guide
+alias: /scim/
+
+description: "Cette page d'accueil répertorie les endpoints SCIM de Braze."
+page_type: landing
+
+guide_top_header: "Endpoints SCIM"
+guide_top_text: "La spécification [System for Cross-domain Identity Management (SCIM)](http://www.simplecloud.info/) est conçue pour faciliter la gestion des identités des utilisateurs dans les applications et services basés sur le cloud en fournissant un schéma défini pour conseiller les utilisateurs et les groupes. Utilisez les endpoints SCIM de Braze pour gérer le provisionnement automatisé des utilisateurs."
+
+guide_featured_title: ""
+guide_featured_list:
+  - name: "POST : Créer un compte utilisateur de tableau de bord"
+    link: /docs/post_create_user_account/
+    image: /assets/img/braze_icons/plus-circle.svg
+  - name: "GET : Rechercher un compte utilisateur de tableau de bord existant"
+    link: /docs/get_see_user_account_information/
+    image: /assets/img/braze_icons/eye.svg
+  - name: "GET : Effectuer une recherche par e-mail d’un compte utilisateur de tableau de bord existant"
+    link: /docs/get_search_existing_dashboard_user_email/
+    image: /assets/img/braze_icons/eye.svg
+  - name: "PUT : Mettre à jour le compte utilisateur de tableau de bord"
+    link: /docs/post_update_existing_user_account/
+    image: /assets/img/braze_icons/pencil-01.svg
+  - name: "DELETE : Supprimer le compte utilisateur de tableau de bord"
+    link: /docs/delete_existing_dashboard_user/
+    image: /assets/img/braze_icons/trash-01.svg
+---
+
diff --git a/_lang/fr_fr/_api/endpoints/scim/delete_existing_dashboard_user.md b/_lang/fr_fr/_api/endpoints/scim/delete_existing_dashboard_user.md
new file mode 100644
index 00000000000..464af15928c
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/scim/delete_existing_dashboard_user.md
@@ -0,0 +1,75 @@
+---
+nav_title: "DELETE : Supprimer le compte utilisateur de tableau de bord"
+article_title: "DELETE : Supprimer le compte utilisateur de tableau de bord"
+alias: /delete_existing_dashboard_user/
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Supprimer un compte utilisateur de tableau de bord."
+---
+
+{% api %}
+# Supprimer un compte utilisateur de tableau de bord
+{% apimethod delete %}
+/scim/v2/Users/{id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer définitivement un utilisateur de tableau de bord existant en spécifiant la ressource `id` renvoyée par la méthode SCIM [`POST`]({{site.baseurl}}/scim/post_create_user_account/) . 
+
+Cette opération est similaire à la suppression d'un utilisateur dans la section **Utilisateurs de l'entreprise** du tableau de bord Braze. Pour plus d’informations sur la manière d’obtenir un jeton SCIM, consultez la section [Provisionnement automatisé des utilisateurs]({{site.baseurl}}/scim/automated_user_provisioning/).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#9c7c71ea-afd6-414a-99d1-4eb1fe274f16 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d’un jeton SCIM. Pour plus d’informations, consultez la section [Provisionnement automatisé des utilisateurs]({{site.baseurl}}/scim/automated_user_provisioning/).
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='delete dashboard user' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `id` | Requis | Chaîne de caractères | L’ID de ressource de l’utilisateur. Ce paramètre est renvoyé par les méthodes `POST` `/scim/v2/Users/` ou `GET` `/scim/v2/Users?filter=userName eq "user@test.com"`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Corps de la demande
+
+```json
+Content-Type: application/json
+X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+## Exemple de demande
+```json
+curl --location --request DELETE 'https://rest.iad-01.braze.com/scim/v2/Users/dfa245b7-24195aec-887bb3ad-602b3340' \
+--header 'Content-Type: application/json' \
+--header 'X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE' \
+--header 'Authorization: Bearer YOUR-SCIM-TOKEN-HERE' \
+```
+
+## Réponse
+
+### Exemple de réponse échouée
+
+```json
+HTTP/1.1 204 Not Found
+Content-Type: text/html; charset=UTF-8
+```
+
+Si cet ID ne correspond à aucun développeur dans Braze, l’endpoint répondra avec :
+```json
+HTTP/1.1 404 Not Found
+Content-Type: text/html; charset=UTF-8
+
+{
+    "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
+    "detail": "User not found",
+    "status": 404
+}
+```
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/scim/get_search_existing_dashboard_user.md b/_lang/fr_fr/_api/endpoints/scim/get_search_existing_dashboard_user.md
new file mode 100644
index 00000000000..481569b9348
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/scim/get_search_existing_dashboard_user.md
@@ -0,0 +1,95 @@
+---
+nav_title: "GET : Effectuer une recherche par e-mail d’un compte utilisateur de tableau de bord existant"
+article_title: "GET : Effectuer une recherche par e-mail d’un compte utilisateur de tableau de bord existant"
+alias: /get_search_existing_dashboard_user_email/
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Effectuer une recherche par e-mail d’un compte utilisateur du tableau de bord existant."
+---
+
+{% api %}
+# Effectuer une recherche par e-mail d’un compte utilisateur de tableau de bord existant
+{% apimethod get %}
+scim/v2/Users?filter=userName%20eq%20"user%40test.com"
+{% endapimethod %}
+
+> Utilisez cet endpoint pour rechercher un compte utilisateur de tableau de bord existant en spécifiant son e-mail dans le paramètre de requête du filtre. 
+
+Veuillez prendre en compte que, lorsque le paramètre de recherche est encodé par URL, il s’affichera ainsi :
+
+`/scim/v2/Users?filter=userName%20eq%20%22user@test.com%22`
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#5037d810-b822-4c54-bb51-f30470a42a95 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d’un jeton SCIM. Pour plus d’informations, consultez la section [Provisionnement automatisé des utilisateurs]({{site.baseurl}}/scim/automated_user_provisioning/).
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='look up dashboard user email' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `userName@example.com` | Requis | Chaîne de caractères | L’adresse e-mail de l’utilisateur. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Paramètres de demande
+
+```json
+Content-Type: application/json
+X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+## Exemple de demande
+```json
+curl --location --request GET \ 'https://rest.iad-01.braze.com/scim/v2/Users?filter=userName%20eq%20%22user@test.com%22' \
+--header 'Content-Type: application/json' \
+--header 'X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+```
+
+## Réponse
+```json
+{
+    "schemas": ["urn:ietf:params:scim:api:messages:2.0:ListResponse"],
+    "totalResults": 1,
+    "Resources": [
+        {
+            "userName": "user@test.com",
+            "id": "dfa245b7-24195aec-887bb3ad-602b3340",
+            "name": {
+                "givenName": "Test",
+                "familyName": "User"
+            },
+            "department": "finance",
+            "lastSignInAt": "Thursday, January 1, 1970 12:00:00 AM",
+            "permissions": {
+                "companyPermissions": ["manage_company_settings"],
+                "appGroup": [
+                    {
+                        "appGroupId": "241adcd25789fabcded",
+                        "appGroupName": "Test Workspace",
+                        "appGroupPermissions": ["basic_access","send_campaigns_canvases"],
+                        "team": [
+                            {
+                                "teamId": "241adcd25789fabcded",
+                                "teamName": "Test Team",                  
+                                "teamPermissions": ["admin"]
+                            }
+                        ]
+                    } 
+                ]
+            }
+        }
+    ]
+}
+```
+
+{% endapi %}
+
diff --git a/_lang/fr_fr/_api/endpoints/scim/get_see_user_account_information.md b/_lang/fr_fr/_api/endpoints/scim/get_see_user_account_information.md
new file mode 100644
index 00000000000..b712e59621e
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/scim/get_see_user_account_information.md
@@ -0,0 +1,84 @@
+---
+nav_title: "GET : Rechercher un compte utilisateur de tableau de bord existant"
+article_title: "GET : Rechercher un compte utilisateur de tableau de bord existant"
+alias: /get_see_user_account_information/
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Rechercher un compte utilisateur de tableau de bord existant."
+---
+
+{% api %}
+# Rechercher un compte utilisateur de tableau de bord existant
+{% apimethod get %}
+/scim/v2/Users/{id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour rechercher un compte utilisateur du tableau de bord existant en spécifiant la ressource `id` retournée par la méthode [`POST`]({{site.baseurl}}/scim/post_create_user_account/) SCIM. 
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#3df40764-8f74-4532-aed3-ab8a6cb92122 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d’un jeton SCIM. Pour plus d’informations, consultez la section [Provisionnement automatisé des utilisateurs]({{site.baseurl}}/scim/automated_user_provisioning/).
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='look up dashboard user' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `id` | Requis | Chaîne de caractères | L’ID de ressource de l’utilisateur. Ce paramètre est renvoyé par les méthodes `POST` `/scim/v2/Users/` ou `GET` `/scim/v2/Users?filter=userName eq "user@test.com"`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Corps de la demande
+```json
+Content-Type: application/json
+X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+## Exemple de demande
+```json
+curl --location --request GET 'https://rest.iad-01.braze.com/scim/v2/Users/dfa245b7-24195aec-887bb3ad-602b3340' \
+--header 'Content-Type: application/json' \
+--header 'X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+```
+
+## Réponse
+```json
+{
+    "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
+    "id": "dfa245b7-24195aec-887bb3ad-602b3340",
+    "userName": "user@test.com",
+    "name": {
+        "givenName": "Test",
+        "familyName": "User"
+    },
+    "department": "finance",
+    "lastSignInAt": "Thursday, January 1, 1970 12:00:00 AM",
+    "permissions": {
+        "companyPermissions": ["manage_company_settings"],
+        "appGroup": [
+            {
+                "appGroupId": "241adcd25789fabcded",
+                "appGroupName": "Test Workspace",
+                "appGroupPermissions": ["basic_access","send_campaigns_canvases"],
+                "team": [
+                    {
+                         "teamId": "241adcd25789fabcded",
+                         "teamName": "Test Team",                  
+                         "teamPermissions": ["admin"]
+                    }
+                ]
+            } 
+        ]
+    }
+}
+```
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/scim/post_create_user_account.md b/_lang/fr_fr/_api/endpoints/scim/post_create_user_account.md
new file mode 100644
index 00000000000..60107de6d8a
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/scim/post_create_user_account.md
@@ -0,0 +1,179 @@
+---
+nav_title: "POST : Créer un nouveau compte utilisateur de tableau de bord"
+article_title: "POST : Créer un nouveau compte utilisateur de tableau de bord"
+alias: /post_create_user_account/
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Créer un nouveau compteur utilisateur de tableau de bord."
+
+---
+
+{% api %}
+# Créer un nouveau compte utilisateur de tableau de bord
+{% apimethod post %}
+/scim/v2/Users
+{% endapimethod %}
+
+> Utilisez ce point de terminaison pour créer un nouveau compte utilisateur de tableau de bord en spécifiant l'e-mail, les prénoms et noms de famille, les autorisations (pour définir les autorisations au niveau de l'entreprise, de l'espace de travail et de l'équipe). 
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#768a3c9d-ce1d-44fc-a0e4-d556b09f7aa3 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d’un jeton SCIM. Pour plus d’informations, consultez la section [Provisionnement automatisé des utilisateurs]({{site.baseurl}}/scim/automated_user_provisioning/).
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='créer un utilisateur de tableau de bord' %}
+
+## Corps de la demande
+```
+Content-Type: application/json
+X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE
+Authorization: Bearer YOUR-REST-API-KEY
+```
+```
+{
+    "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
+    "userName": "user@test.com",
+    "name": {
+        "givenName": "Test",
+        "familyName": "User"
+    },
+    "department": "finance",
+    "permissions": {
+        "companyPermissions": ["manage_company_settings"],
+        "appGroup": [
+            {
+                "appGroupName": "Test Workspace",
+                "appGroupPermissions": ["basic_access","send_campaigns_canvases"],
+                "team": [
+                    {
+                         "teamName": "Test Team",                  
+                         "teamPermissions": ["basic_access","export_user_data"]
+                    }
+                ]
+            },
+            {
+                "appGroupName": "Other Test Workspace",
+                "appGroupPermissionSets": [
+                    {
+                        "appGroupPermissionSetName":  "Test Permission Set"
+                    }
+                ]
+            }
+        ]
+    }
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `schemas` | Requis | Tableau de chaînes de caractères | Nom du schéma SCIM 2.0 attendu pour l’objet Utilisateur. |
+| `userName` | Requis | Chaîne de caractères | L’adresse e-mail de l’utilisateur. |
+| `name` | Requis | Object JSON | Cet objet contient le prénom et le nom de famille de l’utilisateur. |
+| `department` | Requis | Chaîne de caractères | Chaîne de département valide de la [documentation de chaîne de département]({{site.baseurl}}/scim_api_appendix/#department-strings). |
+| `permissions` | Requis | Object JSON | Objet des autorisations comme décrit dans la [documentation de l'objet des autorisations]({{site.baseurl}}/scim_api_appendix/#permissions-object). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/scim/v2/Users' \
+--header 'Content-Type: application/json' \
+--header 'X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+--data raw '{
+    "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
+    "userName": "user@test.com",
+    "name": {
+        "givenName": "Test",
+        "familyName": "User"
+    },
+    "department": "finance",
+    "permissions": {
+        "companyPermissions": ["manage_company_settings"],
+        "appGroup": [
+            {
+                "appGroupName": "Test Workspace",
+                "appGroupPermissions": ["basic_access","send_campaigns_canvases"],
+                "team": [
+                    {
+                         "teamName": "Test Team",                  
+                         "teamPermissions": ["basic_access","export_user_data"]
+                    }
+                ]
+            } 
+        ]
+    }
+}
+```
+
+## Réponse
+```json
+{
+    "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
+    "id": "dfa245b7-24195aec-887bb3ad-602b3340",
+    "userName": "user@test.com",
+    "name": {
+        "givenName": "Test",
+        "familyName": "User"
+    },
+    "department": "finance",
+    "lastSignInAt": "Thursday, January 1, 1970 12:00:00 AM",
+    "permissions": {
+        "companyPermissions": ["manage_company_settings"],
+        "appGroup": [
+            {
+                "appGroupId": "241adcd25789fabcded",
+                "appGroupName": "Test Workspace",
+                "appGroupPermissions": ["basic_access","send_campaigns_canvases"],
+                "team": [
+                    {
+                         "teamId": "2519dafcdba238ae7",
+                         "teamName": "Test Team",                  
+                         "teamPermissions": ["basic_access","export_user_data"]
+                    }
+                ]
+            } 
+        ]
+    }
+}
+```
+
+## Paramètres de réponse
+
+| Paramètre | Type de données | Description |
+| --------- | --------- | ----------- |
+| `schemas` | Tableau de chaînes de caractères | Nom du schéma SCIM 2.0 attendu pour l’objet Utilisateur. |
+| `userName` | Chaîne de caractères | L’adresse e-mail de l’utilisateur. |
+| `name` | Object JSON | Cet objet contient le prénom et le nom de famille de l’utilisateur. |
+| `department` | Chaîne de caractères | Chaîne de département valide de la [documentation de chaîne de département]({{site.baseurl}}/scim_api_appendix/#department-strings). |
+| `permissions` | Object JSON | Objet des autorisations comme décrit dans la [documentation de l'objet des autorisations]({{site.baseurl}}/scim_api_appendix/#permissions-object). |
+| `id` | Chaîne de caractères | ID généré par Braze qui est utilisé pour rechercher et gérer les comptes utilisateurs. |
+| `lastSignInAt` | Chaîne de caractères | Date de la dernière connexion réussie en temps UTC. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+### États relatifs aux d’erreur
+
+Si un utilisateur avec cette adresse e-mail existe déjà dans Braze, l’endpoint répondra avec :
+
+```json
+HTTP/1.1 409 Conflict
+Date: Tue, 10 Sep 2019 02:22:30 GMT
+Content-Type: text/json;charset=UTF-8
+
+{
+  "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
+  "detail": "User already exists in the database.",
+  "status": 409
+}
+```
+
+{% endapi %}
+
+
+
diff --git a/_lang/fr_fr/_api/endpoints/scim/put_update_existing_user_account.md b/_lang/fr_fr/_api/endpoints/scim/put_update_existing_user_account.md
new file mode 100644
index 00000000000..71c46ef29cf
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/scim/put_update_existing_user_account.md
@@ -0,0 +1,170 @@
+---
+nav_title: "PUT : Mettre à jour le compte utilisateur de tableau de bord"
+article_title: "PUT : Mettre à jour le compte utilisateur de tableau de bord"
+alias: /post_update_existing_user_account/
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour un compte utilisateur de tableau de bord existant."
+---
+
+{% api %}
+# Mettre à jour un compte utilisateur de tableau de bord
+{% apimethod put %}
+/scim/v2/Users/{id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour un compte utilisateur de tableau de bord existant en spécifiant la ressource `id` renvoyée par la méthode SCIM [`POST`]({{site.baseurl}}/scim/post_create_user_account/) . 
+
+Il vous permet de mettre à jour les noms et prénoms, les autorisations (pour définir les autorisations au niveau de l'entreprise, de l'espace de travail et de l'équipe) et le département.
+
+Pour des raisons de sécurité, `userName` (adresse e-mail) ne peut pas actuellement être mis à jour à l’aide de cet endpoint. Si vous souhaitez modifier le `userName` (adresse e-mail) d'un utilisateur, contactez l'[assistance]({{site.baseurl}}/support_contact/).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#5f9a1642-988e-4011-8fb8-db4340ea1ac7 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d’un jeton SCIM. Pour plus d’informations, consultez la section [Provisionnement automatisé des utilisateurs]({{site.baseurl}}/scim/automated_user_provisioning/).
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='update dashboard user' %}
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `id` | Requis | Chaîne de caractères | L’ID de ressource de l’utilisateur. Ce paramètre est renvoyé par les méthodes `POST` `/scim/v2/Users/` ou `GET` `/scim/v2/Users?filter=userName eq "user@test.com"`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## Corps de la demande
+```
+Content-Type: application/json
+X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE
+Authorization: Bearer YOUR-REST-API-KEY
+```
+```json
+{
+    "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
+    "name": {"name": {
+        "givenName": "Test",
+        "familyName": "User"
+    },
+    "department": "finance",
+    "permissions": {
+        "companyPermissions": ["manage_company_settings"],
+        "appGroup": [
+            {
+                "appGroupName": "Test Workspace",
+                "appGroupPermissions": ["basic_access","send_campaigns_canvases"],
+                "team": [
+                    {
+                         "teamName": "Test Team",
+                         "teamPermissions": ["admin"]
+                    } 
+                ]
+            },
+            {
+                "appGroupName": "Other Test Workspace",
+                "appGroupPermissionSets": [
+                    {
+                        "appGroupPermissionSetName":  "Test Permission Set"
+                    }
+                ]
+            } 
+        ]
+   }
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | -------- | --------- | ----------- |
+| `schemas` | Requis | Tableau de chaînes de caractères | Nom du schéma SCIM 2.0 attendu pour l’objet Utilisateur. |
+| `name` | Requis | Object JSON | Cet objet contient le prénom et le nom de famille de l’utilisateur. |
+| `department` | Requis | Chaîne de caractères | Chaîne de [caractères]({{site.baseurl}}/scim_api_appendix/#department-strings) valide du département, tirée de la [documentation sur les chaînes de caractères du département]({{site.baseurl}}/scim_api_appendix/#department-strings). |
+| `permissions` | Requis | Object JSON | Objet de permissions tel que décrit dans la [documentation de l'objet de permissions]({{site.baseurl}}/scim_api_appendix/#permissions-object). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+
+## Exemple de demande
+```json
+curl --location --request PUT 'https://rest.iad-01.braze.com/scim/v2/Users/dfa245b7-24195aec-887bb3ad-602b3340' \
+--header 'Content-Type: application/json' \
+--header 'X-Request-Origin: YOUR-REQUEST-ORIGIN-HERE' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+--data raw '{
+    "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
+    "name": {
+        "givenName": "Test",
+        "familyName": "User"
+    },
+    "department": "finance",
+    "permissions": {
+        "companyPermissions": ["manage_company_settings"],
+        "appGroup": [
+            {
+                "appGroupName": "Test Workspace",
+                "appGroupPermissions": ["basic_access","send_campaign_canvases"],
+                "team": [
+                    {
+                         "teamName": "Test Team",                  
+                         "teamPermissions": ["admin"]
+                    }
+                ]
+            } 
+        ]
+    }
+}
+```
+
+## Réponse
+```json
+{
+    "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
+    "id": "dfa245b7-24195aec-887bb3ad-602b3340",
+    "userName": "user@test.com",
+    "name": {
+        "givenName": "Test",
+        "familyName": "User"
+    },
+    "department": "finance",
+    "lastSignInAt": "Thursday, January 1, 1970 12:00:00 AM",
+    "permissions": {
+        "companyPermissions": ["manage_company_settings"],
+        "appGroup": [
+            {
+                "appGroupId": "241adcd25789fabcded",
+                "appGroupName": "Test Workspace",
+                "appGroupPermissions": ["basic_access","send_campaigns_canvases"],
+                "team": [
+                    {
+                         "teamId": "2519dafcdba238ae7",
+                         "teamName": "Test Team",                  
+                         "teamPermissions": ["admin"]
+                    }
+                ]
+            } 
+        ]
+    }
+}
+```
+
+### États relatifs aux d’erreur
+Si un utilisateur avec cet ID n’existe pas dans Braze, l’endpoint répondra avec :
+
+```json
+HTTP/1.1 404 Not Found
+Content-Type: text/html; charset=UTF-8
+
+{
+    "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
+    "detail": "User not found",
+    "status": 404
+}
+```
+
+{% endapi %}
+
diff --git a/_lang/fr_fr/_api/endpoints/sms.md b/_lang/fr_fr/_api/endpoints/sms.md
new file mode 100644
index 00000000000..a17eca4889f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/sms.md
@@ -0,0 +1,22 @@
+---
+nav_title: SMS
+article_title: Endpoints SMS
+search_tag: Endpoint
+page_order: 6
+layout: dev_guide
+
+description: "Cette page d’accueil répertorie les endpoints Braze de SMS."
+page_type: landing
+
+guide_top_header: "Endpoints SMS"
+guide_top_text: "Utilisez les endpoints SMS de Braze pour gérer les numéros de téléphone de vos utilisateurs dans vos groupes d’abonnement."
+
+guide_featured_title: ""
+guide_featured_list:
+  - name: "GET : Extraire les numéros de téléphone non valides"
+    link: /docs/api/endpoints/sms/get_query_invalid_numbers/
+    image: /assets/img/braze_icons/clipboard-check.svg
+  - name: "POST : Supprimer les numéros de téléphone non valides"
+    link: /docs/api/endpoints/sms/post_remove_invalid_numbers/
+    image: /assets/img/braze_icons/phone.svg
+---
diff --git a/_lang/fr_fr/_api/endpoints/sms/get_query_invalid_numbers.md b/_lang/fr_fr/_api/endpoints/sms/get_query_invalid_numbers.md
new file mode 100644
index 00000000000..c291613f50f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/sms/get_query_invalid_numbers.md
@@ -0,0 +1,79 @@
+---
+nav_title: "GET : Extraire les numéros de téléphone non valides"
+article_title: "GET : Extraire les numéros de téléphone non valides"
+search_tag: Endpoint
+page_order: 1
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Interroger les numéros de téléphone non valides."
+---
+{% api %}
+# Extraire les numéros de téléphone non valides
+{% apimethod get %}
+/sms/invalid_phone_numbers
+{% endapimethod %}
+
+> Utilisez cet endpoint pour obtenir une liste des numéros de téléphone qui ont été marqués comme "invalides" dans un certain laps de temps. Pour plus d'informations, consultez la documentation sur la [gestion des numéros de téléphone non valides]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/#handling-invalid-phone-numbers).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#81ceae19-15d1-4ac1-ad22-a6b86a92456d {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `sms.invalid_phone_numbers`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| ----------|-----------| ----------|----- |
+| `start_date` | Facultatif <br>(voir la note) | Chaîne de caractères au format YYYY-MM-DD| La date de début de la plage pour récupérer les numéros de téléphone non valides doit être antérieure à `end_date`. Ce traitement est effectué à minuit (UTC) par l’API. |
+| `end_date` | Facultatif <br>(voir la note) | Chaîne de caractères au format YYYY-MM-DD | Date de fin de la plage pour récupérer les numéros de téléphone non valides. Ce traitement est effectué à minuit (UTC) par l’API. |
+| `limit` | Facultatif | Entier | Champ facultatif pour limiter le nombre de résultats renvoyés. Par défaut à 100, le maximum est 500. |
+| `offset` | Facultatif | Entier | Point de départ facultatif dans la liste où récupérer les informations. |
+| `phone_numbers` | Facultatif <br>(voir la note) | Tableau de chaînes de caractères au format e.164  | S’il est fourni, nous renverrons le numéro de téléphone s’il s’avère non valide. |
+| `reason` | Facultatif <br>(voir la note) | Chaîne de caractères | Les valeurs disponibles sont "provider_error" (l'erreur du fournisseur indique que le téléphone ne peut pas recevoir de SMS) ou "deactivated" (le numéro de téléphone a été désactivé). En cas d'omission, tous les motifs sont renvoyés. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+{% alert note %}
+Vous devez fournir une `start_date` et une `end_date`, OU un `phone_numbers`. Si vous fournissez les trois, une `start_date`, une `end_date`, et un `phone_numbers`, nous donnerons la priorité aux numéros de téléphone communiqués et ignorerons la plage de dates.
+{% endalert %}
+
+Si votre plage de dates dépasse le nombre `limit` de numéros de téléphone non valides, vous devrez effectuer plusieurs appels d’API, en augmentant à chaque fois le `offset` jusqu’à ce qu’un appel renvoie un résultat inférieur à `limit` ou égal à zéro.
+
+## Exemple de demande
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/sms/invalid_phone_numbers?start_date=2019-01-01&end_date=2019-02-01&limit=100&offset=1&phone_numbers[]=12345678901' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE'
+```
+
+## Réponse
+Les entrées sont répertoriées par ordre décroissant.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "sms": [
+    {
+      "phone": (string) phone number in e.164 format,
+      "invalid_detected_at": (string) the time the invalid number was detected in ISO 8601
+      "reason" : "provider_error"
+    },
+    {
+      "phone": (string) phone number in e.164 format,
+      "invalid_detected_at": (string) the time the invalid number was detected in ISO 8601
+      "reason" : "deactivated"
+    },
+    {
+      "phone": (string) phone number in e.164 format,
+      "invalid_detected_at": (string) the time the invalid number was detected in ISO 8601
+      "reason" : "provider_error"
+    }
+  ],
+  "message": "success"
+}
+```
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/sms/post_remove_invalid_numbers.md b/_lang/fr_fr/_api/endpoints/sms/post_remove_invalid_numbers.md
new file mode 100644
index 00000000000..88590a63849
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/sms/post_remove_invalid_numbers.md
@@ -0,0 +1,62 @@
+---
+nav_title: "POST : Supprimer les numéros de téléphone non valides"
+article_title: "POST : Supprimer les numéros de téléphone non valides"
+search_tag: Endpoint
+page_order: 2
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Supprimer les numéros de téléphone non valides."
+
+---
+{% api %}
+# Supprimer les numéros de téléphone non valides
+{% apimethod post %}
+/sms/invalid_phone_numbers/remove
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer les numéros de téléphone "non valides" de notre liste de numéros non valides. 
+
+Cela peut être utilisé pour revalider les numéros de téléphone après avoir été marqués comme non valides.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#76495aac-8c2d-4e1a-8cac-12e3856ab1d3 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `sms.invalid_phone_numbers.remove`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "phone_numbers": (required, array of string in e.164 format)
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| ----------|-----------| ---------|------ |
+| `phone_number` | Requis | Tableau de chaînes de caractères au format e.164  | Un tableau de 50 numéros de téléphone à modifier. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/sms/invalid_phone_numbers/remove' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "phone_numbers" : ["12183095514","14255551212"]
+}'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/subscription_groups.md b/_lang/fr_fr/_api/endpoints/subscription_groups.md
new file mode 100644
index 00000000000..a6d9e812f04
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/subscription_groups.md
@@ -0,0 +1,31 @@
+---
+nav_title: Groupes d’abonnement
+article_title: Endpoint des groupes d’abonnement
+page_order: 7
+layout: dev_guide
+
+#Required
+description: "Cette page d’accueil explique et répertorie les endpoints des groupes d’abonnement Braze pour les e-mails et les SMS."
+page_type: landing
+search_tag: Endpoint
+
+guide_top_header: "Endpoint des groupes d’abonnement"
+guide_top_text: "Utilisez les API REST de groupe d'abonnement pour gérer de manière programmatique les groupes d'abonnement que vous avez stockés dans le tableau de bord de Braze, sur la page **Groupe d'abonnement**. Ceci s’applique aux groupes d’abonnement aux SMS et aux e-mails.<br><br> Vous recherchez des conseils sur la création de groupes d’abonnement ? Consultez nos articles sur les <a href='/docs/user_guide/message_building_by_channel/sms/sms_subscription_group//'>groupes d’abonnement aux SMS</a> et les <a href='/docs/user_guide/message_building_by_channel/email/managing_user_subscriptions/'>groupes d’abonnement aux e-mails</a>."
+
+guide_featured_title: ""
+guide_featured_list:
+  - name: "GET : Répertorier le statut du groupe d’abonnement de l’utilisateur"
+    link: /docs/api/endpoints/subscription_groups/get_list_user_subscription_group_status/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "GET : Répertorier les groupes d’abonnement de l’utilisateur"
+    link: /docs/api/endpoints/subscription_groups/get_list_user_subscription_groups/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "POST : Mettre à jour le statut du groupe d’abonnement de l’utilisateur"
+    link: /docs/api/endpoints/subscription_groups/post_update_user_subscription_group_status/
+    image: /assets/img/braze_icons/user-plus-01.svg
+  - name: "POST : Mettre à jour le statut du groupe d’abonnement de l’utilisateur V2"
+    link: /docs/api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2/
+    image: /assets/img/braze_icons/user-edit.svg
+---
+<br>
+<br>
diff --git a/_lang/fr_fr/_api/endpoints/subscription_groups/get_list_user_subscription_group_status.md b/_lang/fr_fr/_api/endpoints/subscription_groups/get_list_user_subscription_group_status.md
new file mode 100644
index 00000000000..dd75aa8bcb4
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/subscription_groups/get_list_user_subscription_group_status.md
@@ -0,0 +1,101 @@
+---
+nav_title: "GET : Répertorier le statut du groupe d’abonnement des utilisateurs"
+article_title: "GET : Répertorier le statut du groupe d’abonnement de l’utilisateur"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Répertorier le statut du groupe d’abonnement des utilisateurs."
+
+---
+{% api %}
+# Répertorier le statut du groupe d’abonnement de l’utilisateur
+{% apimethod get %}
+/subscription/status/get
+{% endapimethod %}
+
+> Utilisez cet endpoint pour obtenir le statut d’abonnement d’un utilisateur dans un groupe d’abonnement.
+
+Ces groupes seront disponibles sur la page des **groupes d'abonnement**. La réponse de cet endpoint inclura l’ID externe et le statut abonné, désabonné, ou inconnu pour le groupe d’abonnement spécifique demandé dans l’appel d’API. Cette option permet de mettre à jour le statut du groupe d’abonnement dans les appels d’API ultérieurs ou de l’afficher sur une page Web hébergée.
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour les **groupes d'abonnement e-mail**:
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#488c8923-fa44-4124-9245-036d13c615f2 {% endapiref %}
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour les **groupes d'abonnement SMS**:
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#4b8515b8-067f-41fd-b213-8bb2d18b1557 {% endapiref %}
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour **WhatsApp Groups :**
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#4b8515b8-067f-41fd-b213-8bb2d18b1557 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `subscription.status.get`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| [`subscription_group_id`]({{site.baseurl}}/api/identifier_types/?tab=subscription%20group%20ids)  | Requis | Chaîne de caractères | L’`id` de votre groupe d’abonnement. |
+| `external_id`  |  Obligatoire* | Chaîne de caractères | L’`external_id` de l’utilisateur (maximum 50 `external_ids`, minimum 1). <br><br>Lorsqu’un `external_id` et un `email`/`phone` sont transmis, seuls le ou les `external_id`(s) fournis seront appliqués à la requête. |
+| `email` | Obligatoire* | Chaîne de caractères | L’adresse e-mail de l’utilisateur. Il peut être transmis comme un tableau de chaînes de caractères avec un maximum de 50 éléments.<br><br> Envoyer une adresse e-mail et un numéro de téléphone en même temps (sans `external_id`) entraînera une erreur. |
+| `phone` | Obligatoire* | Chaîne de caractères dans [E.164](https://en.wikipedia.org/wiki/E.164) format | Le numéro de téléphone de l’utilisateur. Si l’e-mail n’est pas inclus, vous devez ajouter au moins un numéro de téléphone (avec un maximum de 50).<br><br> Envoyer une adresse e-mail et un numéro de téléphone en même temps (sans `external_id`) entraînera une erreur. |
+
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+\*Chaque utilisateur doit disposer d'une des options suivantes : `external_id`, `email` ou `phone`.
+
+- Pour les groupes d'abonnement aux SMS et à WhatsApp, un `external_id` ou un `phone` est nécessaire.  Lorsque les deux sont soumis, seul l’`external_id` est utilisé pour l'interrogation et le numéro de téléphone est appliqué à cet utilisateur.
+- Pour les groupes d’abonnement aux e-mails, `external_id` ou `email` est nécessaire.  Lorsque les deux sont soumis, seul l’`external_id` est utilisé pour la requête et l’adresse e-mail est appliquée à cet utilisateur.
+
+## Exemple de demande 
+
+{% tabs %}
+{% tab Utilisateurs multiples %}
+{% raw %}
+```
+https://rest.iad-03.braze.com/subscription/status/get?subscription_group_id={{subscription_group_id}}&external_id[]=1&external_id[]=2
+```
+{% endraw %}
+{% endtab %}
+{% tab SMS et WhatsApp %}
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/subscription/status/get?subscription_group_id={{subscription_group_id}}&phone=+11112223333' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+{% endtab %}
+{% tab E-mail %}
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/subscription/status/get?subscription_group_id={{subscription_group_id}}&email=example@braze.com' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+{% endtab %}
+{% endtabs %}
+
+## Réponse
+
+Toutes les réponses réussies renverront `Subscribed`, `Unsubscribed`, ou `Unknown` selon le statut et l’historique de l’utilisateur avec le groupe d’abonnement.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "status": {
+    "1": "Unsubscribed",
+    "2": "Subscribed"
+  },
+  "message": "success"
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/subscription_groups/get_list_user_subscription_groups.md b/_lang/fr_fr/_api/endpoints/subscription_groups/get_list_user_subscription_groups.md
new file mode 100644
index 00000000000..c5bf1165bf8
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/subscription_groups/get_list_user_subscription_groups.md
@@ -0,0 +1,79 @@
+---
+nav_title: "GET : Répertorier les groupes d’abonnement de l’utilisateur"
+article_title: "GET : Répertorier les groupes d’abonnement de l’utilisateur"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Répertorier les groupes d’abonnement de l’utilisateur."
+
+---
+{% api %}
+# Répertorier les groupes d’abonnement de l’utilisateur
+{% apimethod get %}
+/subscription/user/status
+{% endapimethod %}
+
+> Utilisez cet endpoint pour répertorier et obtenir les groupes d’abonnement d’un utilisateur donné.
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour les **groupes d'abonnement e-mail**:
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#d1c3b617-22f1-47bf-9ee8-499526824470 {% endapiref %}
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour les **groupes d'abonnement SMS**:
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#54bd7ca8-60d9-4654-aff5-406479f3c666 {% endapiref %}
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour **WhatsApp Groups :**
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#54bd7ca8-60d9-4654-aff5-406479f3c666 {% endapiref %}
+
+## Pré-requis
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `subscription.groups.get`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `external_id`  | Requis | Chaîne de caractères | L’`external_id` de l’utilisateur (maximum 50 `external_ids`, minimum 1). |
+| `email`  |  Obligatoire* | Chaîne de caractères | L’adresse e-mail de l’utilisateur peut être transmise comme un tableau de chaînes de caractères. Doit inclure au moins une adresse e-mail (maximum 50). |
+| `phone` | Obligatoire* | Chaîne de caractères dans [E.164](https://en.wikipedia.org/wiki/E.164) format | Le numéro de téléphone de l’utilisateur. Doit inclure au moins un numéro de téléphone (maximum 50). |
+| `limit` | Facultatif | Entier | La limite du nombre maximum de résultats renvoyés. La `limit` par défaut (et au maximum) est de 100. |
+| `offset`  |  Facultatif | Entier | Nombre de modèles à ignorer avant de renvoyer le reste des modèles qui correspondent aux critères de recherche. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+{% alert tip %}
+S’il existe plusieurs utilisateurs (plusieurs `external_ids`) qui partagent la même adresse e-mail, tous les utilisateurs seront renvoyés en tant qu’utilisateurs distincts (même s’ils ont la même adresse e-mail ou le même groupe d’abonnement).
+{% endalert %}
+
+## Exemple de demande 
+
+{% tabs %}
+{% tab Utilisateurs multiples %}
+{% raw %}
+`https://rest.iad-03.braze.com/subscription/user/status?external_id[]=1&external_id[]=2`
+{% endraw %}
+{% endtab %}
+{% tab SMS et WhatsApp %}
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/subscription/user/status?external_id={{external_id}}&limit=100&offset=1&phone=+11112223333' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+{% endtab %}
+{% tab E-mail %}
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/subscription/user/status?external_id={{external_id}}&email=example@braze.com&limit=100&offset=0' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+{% endtab %}
+{% endtabs %}
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/subscription_groups/post_update_user_subscription_group_status.md b/_lang/fr_fr/_api/endpoints/subscription_groups/post_update_user_subscription_group_status.md
new file mode 100644
index 00000000000..82c3a13a8c0
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/subscription_groups/post_update_user_subscription_group_status.md
@@ -0,0 +1,141 @@
+---
+nav_title: "POST : Mettre à jour le statut du groupe d’abonnement de l’utilisateur"
+article_title: "POST : Mettre à jour le statut du groupe d’abonnement de l’utilisateur"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour le statut du groupe d’abonnement de l’utilisateur."
+---
+{% api %}
+# Mettre à jour le statut du groupe d’abonnement de l’utilisateur
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/subscription/status/set
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour en masse le statut d’abonnement jusqu’à 50 utilisateurs sur le tableau de bord de Braze. 
+
+Vous pouvez accéder au site `subscription_group_id` d'un groupe d'abonnement en accédant à la page **Groupe d'abonnement**.
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour les **groupes d'abonnement e-mail**:
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#8895e87e-6324-47a3-a833-adf29a258bb9 {% endapiref %}
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour les **groupes d'abonnement SMS**:
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#72558b32-7dbe-4cba-bd22-a7ce513076dd {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `subscription.status.set`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='subscription status set' %}
+
+## Corps de la demande
+
+{% tabs %}
+{% tab SMS %}
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+   "subscription_group_id": (required, string) the id of your subscription group,
+   "subscription_state": (required, string) available values are "unsubscribed" (not in subscription group) or "subscribed" (in subscription group),
+   "external_id": (required*, array of strings) the external ID of the user or users, may include up to 50 IDs,
+   "phone": (required*, array of strings in E.164 format) The phone number of the user (must include at least one phone number and at most 50 phone numbers),
+   // SMS subscription group - one of external_id or phone is required
+ }
+```
+\* Groupes d'abonnement SMS : Uniquement `external_id` ou `phone` est accepté.
+
+{% endtab %}
+{% tab E-mail %}
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+   "subscription_group_id": (required, string) the id of your subscription group,
+   "subscription_state": (required, string) available values are "unsubscribed" (not in subscription group) or "subscribed" (in subscription group),
+   "external_id": (required*, array of strings) the external ID of the user or users, may include up to 50 IDs,
+   "email": (required*, array of strings) the email address of the user (must include at least one email and at most 50 emails),
+   // Email subscription group - one of external_id or email is required
+   // Note that sending an email address that is linked to multiple profiles will update all relevant profiles
+ }
+```
+\* Groupes d'abonnement e-mail : `email` ou `external_id` est nécessaire.
+{% endtab %}
+{% endtabs %}
+
+Cette propriété ne doit pas être utilisée pour mettre à jour les informations de profil d’un utilisateur. Utilisez plutôt la propriété [/users/track.]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) 
+
+{% alert tip %}
+Lorsque vous créez de nouveaux utilisateurs via l'endpoint [/users/track]({{site.baseurl}}/api/endpoints/user_data/post_user_track/), vous pouvez définir des groupes d'abonnement dans l'objet des attributs de l'utilisateur, ce qui vous permet de créer un utilisateur et de définir l'état du groupe d'abonnement en un seul appel d'API.
+{% endalert %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| [`subscription_group_id`]({{site.baseurl}}/api/identifier_types/?tab=subscription%20group%20ids) | Requis | Chaîne de caractères | L’`id` de votre groupe d’abonnement. |
+| `subscription_state` | Requis | Chaîne de caractères | Les valeurs disponibles sont `unsubscribed` (pas dans le groupe d’abonnement) ou `subscribed` (dans le groupe d’abonnement). |
+| `external_id` | Obligatoire* | Tableau de chaînes de caractères | L’`external_id` de l’utilisateur ou des utilisateurs (50 `id`s max). |
+| `email` | Obligatoire* | Chaîne de caractères ou tableau de chaînes de caractères | L’adresse e-mail de l’utilisateur peut être transmise comme un tableau de chaînes de caractères. Doit inclure au moins une adresse e-mail (maximum 50). <br><br>Si plusieurs utilisateurs (`external_id`) d'un même espace de travail partagent la même adresse e-mail, tous les utilisateurs qui partagent cette adresse sont mis à jour en fonction des modifications apportées au groupe d'abonnement. |
+| `phone` | Obligatoire* | Chaîne de caractères dans [E.164](https://en.wikipedia.org/wiki/E.164) format | Le numéro de téléphone de l’utilisateur peut être transmis comme un tableau de chaînes de caractères. Doit inclure au moins un numéro de téléphone (maximum 50). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de requêtes
+
+### E-mail
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/subscription/status/set' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "subscription_group_id": "subscription_group_identifier",
+  "subscription_state": "unsubscribed",
+  "external_id": "external_identifier",
+  "email": ["example1@email.com", "example2@email.com"]
+}
+'
+```
+
+### SMS
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/subscription/status/set' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "subscription_group_id": "subscription_group_identifier",
+  "subscription_state": "unsubscribed",
+  "external_id": "external_identifier",
+  "phone": ["+12223334444", "+11112223333"]
+}
+'
+```
+
+## Exemple de réponse réussie
+
+Le code de statut `201` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+    "message": "success"
+}
+```
+
+{% alert important %}
+L’endpoint accepte uniquement la valeur `email` ou `phone`, et non les deux. Si vous disposez des deux, vous recevrez cette réponse : `{"message":"Either an email address or a phone number should be provided, but not both."}`
+{% endalert %}
+
+{% endapi %}
+
diff --git a/_lang/fr_fr/_api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2.md b/_lang/fr_fr/_api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2.md
new file mode 100644
index 00000000000..c702da2e840
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2.md
@@ -0,0 +1,144 @@
+---
+nav_title: "POST : Mettre à jour le statut du groupe d’abonnement de l’utilisateur V2"
+alias: /post_update_user_subscription_group_status_v2/
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze V2 Mettre à jour le statut du groupe d’abonnement de l’utilisateur."
+
+platform: API
+channel:
+  - Email
+---
+
+{% api %}
+# Mettre à jour le statut du groupe d’abonnement de l’utilisateur (V2)
+{% apimethod post %}
+/v2/subscription/status/set
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour en masse le statut d’abonnement jusqu’à 50 utilisateurs sur le tableau de bord de Braze. 
+
+Vous pouvez accéder au site `subscription_group_id` d'un groupe d' **abonnement** en accédant à la page **Groupe d'abonnements**.
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour les **groupes d'abonnement e-mail**:
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#b1b9a0e0-6329-4df2-a465-53347f410662 {% endapiref %}
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour les **groupes d'abonnement SMS**:
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#81a5fe65-588b-4b61-82d8-5ce68b681409 {% endapiref %}
+
+Si vous souhaitez voir des exemples ou tester cet endpoint pour **WhatsApp Groups :**
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#81a5fe65-588b-4b61-82d8-5ce68b681409 {% endapiref %}
+
+## Pré-requis
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `subscription.status.set`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='subscription status set' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "subscription_groups":[
+    {
+      "subscription_group_id": (required, string),
+      "subscription_state": (required, string)
+      "external_ids": (required*, array of strings),
+      "emails": (required*, array of strings),
+      "phones": (required*, array of strings in E.164 format),
+    }
+  ]
+}
+```
+\* Notez que vous ne pouvez pas inclure à la fois les paramètres `emails` et `phones`. De plus, `emails`, `phones` et `external_ids` peuvent tous être envoyés individuellement.
+
+{% alert tip %}
+Lorsque vous créez de nouveaux utilisateurs via l'[endpoint`/users/track` ]({{site.baseurl}}/api/endpoints/user_data/post_user_track/), vous pouvez définir des groupes d'abonnement dans l'objet des attributs de l'utilisateur, ce qui vous permet de créer un utilisateur et de définir l'état du groupe d'abonnement en un seul appel d'API.
+{% endalert %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| [`subscription_group_id`]({{site.baseurl}}/api/identifier_types/?tab=subscription%20group%20ids) | Requis | Chaîne de caractères | L’`id` de votre groupe d’abonnement. |
+| `subscription_state` | Requis | Chaîne de caractères | Les valeurs disponibles sont `unsubscribed` (pas dans le groupe d’abonnement) ou `subscribed` (dans le groupe d’abonnement). |
+| `external_ids` | Obligatoire* | Tableau de chaînes de caractères | L’`external_id` de l’utilisateur ou des utilisateurs (50 `id`s max). |
+| `emails` | Obligatoire* | Chaîne de caractères ou tableau de chaînes de caractères | L’adresse e-mail de l’utilisateur peut être transmise comme un tableau de chaînes de caractères. Doit inclure au moins une adresse e-mail (maximum 50). <br><br>Si plusieurs utilisateurs (`external_id`) du même espace de travail partagent la même adresse e-mail, tous les utilisateurs qui partagent l'adresse e-mail sont mis à jour avec les modifications apportées au groupe d'abonnement. |
+| `phones` | Obligatoire* | Chaîne de caractères dans [E.164](https://en.wikipedia.org/wiki/E.164) format | Les numéros de téléphone de l’utilisateur, peuvent être transmis comme un tableau de chaînes de caractères. Doit inclure au moins un numéro de téléphone (maximum 50). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+{% alert note %}
+Notez que vous ne pouvez pas inclure à la fois les paramètres `emails` et `phones`. De plus, `emails`, `phones` et `external_ids` peuvent tous être envoyés individuellement.
+{% endalert %}
+
+### Exemple de requêtes
+
+L’exemple suivant utilise `external_id` pour effectuer un appel API pour les e-mails et SMS.
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/v2/subscription/status/set' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "subscription_groups":[
+    {
+      "subscription_group_id":"subscription_group_identifier",
+      "subscription_state":"subscribed",
+      "external_ids":["example-user","example1@email.com"]
+    },
+    {
+      "subscription_group_id":"subscription_group_identifier",
+      "subscription_state":"subscribed",
+      "external_ids":["example-user","example1@email.com"]
+    }
+  ]
+}
+```
+
+## E-mail
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/v2/subscription/status/set' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "subscription_groups":[
+    {
+      "subscription_group_id":"subscription_group_identifier",
+      "subscription_state":"subscribed",
+      "emails":["example1@email.com","example2@email.com"]
+    }
+  ]
+}
+'
+```
+
+## SMS et WhatsApp
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/v2/subscription/status/set' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "subscription_groups":[
+    {
+      "subscription_group_id":"subscription_group_identifier",
+      "subscription_state":"subscribed",
+      "phones":["+12223334444","+15556667777"]
+    }
+  ]
+}
+'
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/templates.md b/_lang/fr_fr/_api/endpoints/templates.md
new file mode 100644
index 00000000000..fa906b34dd5
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates.md
@@ -0,0 +1,46 @@
+---
+nav_title: Modèles
+article_title: Endpoints des modèles
+page_order: 8
+layout: dev_guide
+
+search_tag: Endpoint
+description: "Cette page d’accueil explique et répertorie les endpoints des modèles de Braze pour les e-mails et les blocs de contenu d’e-mail."
+page_type: landing
+
+guide_top_header: "Endpoints des modèles"
+guide_top_text: "Les endpoints Template vous permettent de créer et de gérer vos modèles d'e-mail et de blocs de contenu. <br><br> Vous souhaitez obtenir davantage de conseils sur la création de modèles pour les e-mails et les blocs de contenu ? Consultez notre <a href='/docs/user_guide/message_building_by_channel/email/templates/'>section</a> dédiée aux <a href='/docs/user_guide/message_building_by_channel/email/templates/'>modèles d'e-mail</a> et notre <a href='/docs/user_guide/engagement_tools/templates_and_media/content_blocks/'>article sur les blocs de contenu</a>."
+
+guide_featured_title: "Points d'endpoint des modèles d'e-mail"
+guide_featured_list:
+  - name: "GET : Répertorier les modèles d’e-mail disponibles"
+    link: /docs/api/endpoints/templates/email_templates/get_list_email_templates/
+    image: /assets/img/braze_icons/mail-01.svg
+  - name: "GET : Voir les informations sur les modèles d’e-mail"
+    link: /docs/api/endpoints/templates/email_templates/get_see_email_template_information/
+    image: /assets/img/braze_icons/copy-04.svg
+  - name: "POST : Créer un modèle d’e-mail"
+    link: /docs/api/endpoints/templates/email_templates/post_create_email_template/
+    image: /assets/img/braze_icons/mail-01.svg
+  - name: "POST : Mettre à jour le modèle d’e-mail"
+    link: /docs/api/endpoints/templates/email_templates/post_update_email_template/
+    image: /assets/img/braze_icons/mail-01.svg
+
+guide_menu_title: "Content Block template endpoints"
+guide_menu_list:
+  - name: "GET : Répertorier les blocs de contenu disponibles"
+    link: /docs/api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks/
+    image: /assets/img/braze_icons/mail-01.svg
+  - name: "GET : Voir les informations disponibles sur le bloc de contenu"
+    link: /docs/api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information/
+    image: /assets/img/braze_icons/copy-04.svg
+  - name: "POST : Créer des blocs de contenu"
+    link: /docs/api/endpoints/templates/content_blocks_templates/post_create_email_content_block/
+    image: /assets/img/braze_icons/layout-grid-01.svg
+  - name: "POST : Mettre à jour le bloc de contenu"
+    link: /docs/api/endpoints/templates/content_blocks_templates/post_update_content_block/
+    image: /assets/img/braze_icons/mail-04.svg
+---
+{% comment %}
+redirection depuis email_templates.md
+{% endcomment %}
diff --git a/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates.md b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates.md
new file mode 100644
index 00000000000..4406e742bc0
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates.md
@@ -0,0 +1,5 @@
+---
+nav_title: Modèles de bloc de contenu
+config_only: true
+noindex: true
+---
diff --git a/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks.md b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks.md
new file mode 100644
index 00000000000..e2f2f6a0117
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks.md
@@ -0,0 +1,82 @@
+---
+nav_title: "GET : Répertorier les blocs de contenu disponibles"
+article_title: "GET : Répertorier les blocs de contenu disponibles"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Répertorier les blocs de contenu disponibles."
+
+---
+{% api %}
+# Répertorier les blocs de contenu disponibles
+{% apimethod get %}
+/content_blocks/list
+{% endapimethod %}
+
+> Utilisez cet endpoint pour dresser la liste des informations relatives à vos [blocs contenus]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/) existants.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#6d87048f-68fd-46c9-aa15-3a970e99540e {% endapiref %}
+
+## Conditions préalables
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `content_blocks.list`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `modified_after`  | Facultatif | Chaîne de caractères au format [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)  | Récupérer uniquement les blocs de contenu mis à jour à partir de l'heure donnée. |
+| `modified_before`  |  Facultatif | Chaîne de caractères au format [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)  | Récupérer uniquement les blocs de contenu mis à jour au plus tard à l'heure donnée. |
+| `limit` | Facultatif | Nombre positif | Nombre maximum de blocs de contenu à récupérer. Par défaut à 100 si non renseigné, avec une valeur maximale acceptable de 1 000. |
+| `offset`  |  Facultatif | Nombre positif | Nombre de blocs de contenu à ignorer avant de renvoyer le reste des modèles correspondant aux critères de recherche. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/content_blocks/list?modified_after=2020-01-01T01:01:01.000000&modified_before=2020-02-01T01:01:01.000000&limit=100&offset=1' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+  "count": "integer",
+  "content_blocks": [
+    {
+      "content_block_id": (string) the Content Block identifier,
+      "name": (string) the name of the Content Block,
+      "content_type": (string) the content type, html or text,
+      "liquid_tag": (string) the Liquid tags,
+      "inclusion_count" : (integer) the inclusion count,
+      "created_at": (string) The time the Content Block was created in ISO 8601,
+      "last_edited": (string) The time the Content Block was last edited in ISO 8601,
+      "tags": (array) An array of tags formatted as strings,
+    }
+  ]
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `Modified after time is invalid` | La date fournie n’est pas une date valide ou analysable. Reformater cette valeur en tant que chaîne de caractères au format ISO 8601 (`yyyy-mm-ddThh:mm:ss.ffffff`). |
+| `Modified before time is invalid` | La date fournie n’est pas une date valide ou analysable. Reformater cette valeur en tant que chaîne de caractères au format ISO 8601 (`yyyy-mm-ddThh:mm:ss.ffffff`). |
+| `Modified after time must be earlier than or the same as modified before time.` | Modifier la valeur `modified_after` à une heure antérieure à l’heure `modified_before`. |
+| `Content Block number limit is invalid` | Le paramètre `limit` doit être un entier (nombre positif) supérieur à 0. |
+| `Content Block number limit must be greater than 0` | Modifier le paramètre `limit` à un entier supérieur à 0. |
+| `Content Block number limit exceeds maximum of 1000` | Modifier le paramètre `limit` à un entier inférieur à 1 000. |
+| `Offset is invalid` | Le paramètre `offset` doit être un entier supérieur à 0. |
+| Le décalage doit être supérieur à 0 | Modifier le paramètre `offset` à un entier supérieur à 0. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information.md b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information.md
new file mode 100644
index 00000000000..aa92bccaf48
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information.md
@@ -0,0 +1,77 @@
+---
+nav_title: "GET : Voir les informations sur les blocs de contenu"
+article_title: "GET : Voir les informations sur les blocs de contenu"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Afficher les informations sur les blocs de contenu."
+---
+
+{% api %}
+# Voir les informations sur les blocs de contenu
+{% apimethod get %}
+/content_blocks/info
+{% endapimethod %}
+
+> Utilisez cet endpoint pour appeler les informations relatives à vos [blocs de contenu]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/) existants.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#589adda3-0def-4369-9ddc-eae71923c0ee {% endapiref %}
+
+## Conditions préalables
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `content_blocks.info`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `content_block_id`  | Requis | Chaîne de caractères | L'identifiant du bloc de contenu. <br><br>Vous pouvez le trouver soit en listant les informations du bloc de contenu par le biais d'un appel API, soit en vous rendant sur la page des [clés API]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/), puis en défilant vers le bas et en recherchant votre identifiant API du bloc de contenu.|
+| `include_inclusion_data`  | Facultatif | Valeur booléenne | Lorsqu'elle est définie sur `true`, l'API renvoie l'identifiant API de la variation de message des campagnes et des canevas dans lesquels ce bloc de contenu est inclus, afin qu'il soit utilisé dans les appels ultérieurs.  Les résultats excluent les campagnes ou Canvas archivé(e)s ou supprimé(e)s. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/content_blocks/info?content_block_id={{content_block_id}}&include_inclusion_data=false' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+  "content_block_id": (string) the Content Block identifier,
+  "name": (string) the name of the Content Block,
+  "content": (string) the content in the Content Block,
+  "description": (string) the Content Block description,
+  "content_type": (string) the content type, html or text,
+  "tags": (array) An array of tags formatted as strings,
+  "created_at": (string) The time the Content Block was created in ISO 8601,
+  "last_edited": (string) The time the Content Block was last edited in ISO 8601,
+  "inclusion_count" : (integer) the inclusion count,
+  "inclusion_data": (array) the inclusion data,
+  "message": "success",
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `Content Block ID cannot be blank` | Assurez-vous qu’un bloc de contenu est répertorié dans votre demande et compris entre des guillemets (`""`). |
+| `Content Block ID is invalid for this workspace` | Ce bloc de contenu n'existe pas ou se trouve dans un compte d'entreprise ou un espace de travail différent. |
+| `Content Block has been deleted—content not available` | Ce bloc de contenu, bien qu’il ait pu exister, a été supprimé. |
+| `Include Inclusion Data—error` | Ce paramètre accepte uniquement les valeurs booléennes (vrai ou faux). Assurez-vous que la valeur de `include_inclusion_data` n’est pas comprise entre des guillemets (`""`), sinon la valeur est envoyée comme chaîne de caractères. Voir les [paramètres de la demande](#request-parameters) pour plus de détails. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/post_create_email_content_block.md b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/post_create_email_content_block.md
new file mode 100644
index 00000000000..7db274087b8
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/post_create_email_content_block.md
@@ -0,0 +1,108 @@
+---
+nav_title: "POST : Créer un bloc de contenu"
+article_title: "POST : Créer un bloc de contenu"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Créer des blocs de contenu."
+
+---
+{% api %}
+# Créer un bloc de contenu
+{% apimethod post %}
+/content_blocks/create
+{% endapimethod %}
+
+> Utilisez cet endpoint pour créer un [bloc de contenu]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#f1cefa8b-7a28-4e64-b579-198a4610d0a5 {% endapiref %}
+
+## Conditions préalables
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `content_blocks.create`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+  "name": (required, string) Must be less than 100 characters,
+  "description": (optional, string) The description of the Content Block. Must be less than 250 character,
+  "content": (required, string) HTML or text content within Content Block,
+  "state": (optional, string) Choose `active` or `draft`. Defaults to `active` if not specified,
+  "tags": (optional, array of strings) Tags must already exist
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `name` | Requis | Chaîne de caractères | Nom du bloc de contenu. Doit contenir moins de 100 caractères. |
+| `description` | Facultatif | Chaîne de caractères | Description du bloc de contenu. Doit contenir moins de 250 caractères. |
+| `content` | Requis | Chaîne de caractères | HTML ou contenu texte dans le bloc de contenu. |
+| `state` | Facultatif | Chaîne de caractères | Choisir `active` ou `draft`. Défini par défaut sur `active` si cela n’est pas spécifié. |
+| `tags` | Facultatif | Tableau de chaînes de caractères | Les [étiquettes]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) doivent déjà exister. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/content_blocks/create' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+  "name": "content_block",
+  "description": "This is my Content Block",
+  "content": "HTML content within block",
+  "state": "draft",
+  "tags": ["marketing"]
+}'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+  "content_block_id": (string) Your newly generated block id,
+  "liquid_tag": (string) The generated block tag from the Content Block name,
+  "created_at": (string) The time the Content Block was created in ISO 8601,
+  "message": "success"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `Content cannot be blank` | |
+| `Content must be a string` | Assurez-vous que votre contenu est compris entre des guillemets (`""`). |
+| `Content must be smaller than 50kb` | Le contenu de votre bloc de contenu doit être inférieur à 50 Ko. |
+| `Content contains malformed liquid` | Le langage Liquid fourni n’est pas valide ou pas analysable. Réessayez avec un langage Liquid valide ou contactez-nous pour obtenir de l’aide. |
+| `Content Block cannot be referenced within itself` | |
+| `Content Block description cannot be blank` | |
+| `Content Block description must be a string` | Assurez-vous que la description de votre bloc de contenu est comprise entre des guillemets (`""`). |
+| `Content Block description must be shorter than 250 characters` | |
+| `Content Block name cannot be blank` | |
+| `Content Block name must be shorter than 100 characters` | |
+| `Content Block name can only contain alphanumeric characters` | Les noms de bloc de contenu peuvent comprendre l’un des caractères suivants : les lettres (majuscules ou minuscules) de `A` à `Z`, les chiffres de `0` à `9`, les tirets `-`, et les traits de soulignement `_`. Il ne peut pas contenir de caractères non alphanumériques comme des émojis, `!`, `@`, `~`, `&` et d’autres caractères « spéciaux ». |
+| `Content Block with this name already exists` | Essayez un autre nom. |
+| `Content Block state must be either active or draft` | |
+| `Tags must be an array` | Les balises doivent être un tableau de chaînes de caractères, par exemple `["marketing", "promotional", "transactional"]`. | |
+| `All tags must be strings` | Assurez-vous que vos balises sont comprises entre des guillemets (`""`). |
+| `Some tags could not be found` | Pour ajouter une balise lors de la création d’un bloc de contenu, la balise doit déjà exister dans Braze. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/post_update_content_block.md b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/post_update_content_block.md
new file mode 100644
index 00000000000..a0fa8aceace
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/content_blocks_templates/post_update_content_block.md
@@ -0,0 +1,113 @@
+---
+nav_title: "POST : Mettre à jour le bloc de contenu"
+article_title: "POST : Mettre à jour le bloc de contenu"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour des blocs de contenu."
+
+---
+{% api %}
+# Mettre à jour le bloc de contenu
+{% apimethod post %}
+/content_blocks/update
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour un [bloc de contenu]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/).
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#4782239a-cb60-4217-9de0-51411434d57d {% endapiref %}
+
+## Conditions préalables
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `content_blocks.update`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+  "content_block_id" : (required, string) Content Block's API identifier.
+  "name": (optional, string) Must be less than 100 characters,
+  "description": (optional, string) The description of the Content Block. Must be less than 250 character,
+  "content": (optional, string) HTML or text content within Content Block,
+  "state": (optional, string) Choose `active` or `draft`. Defaults to `active` if not specified,
+  "tags": (optional, array of strings) Tags must already exist
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `content_block_id`|	Requis |	Chaîne de caractères | L'identifiant API de votre bloc de contenu.|
+| `name` | Facultatif | Chaîne de caractères | Nom du bloc de contenu. Doit contenir moins de 100 caractères. |
+| `description` | Facultatif | Chaîne de caractères | Description du bloc de contenu. Doit contenir moins de 250 caractères. |
+| `content` | Facultatif | Chaîne de caractères | Contenu HTML ou texte dans les blocs de contenu.
+| `state` | Facultatif | Chaîne de caractères | Choisir `active` ou `draft`. Défini par défaut sur `active` si cela n’est pas spécifié. |
+| `tags` | Facultatif | Tableau de chaînes de caractères | Les [étiquettes]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) doivent déjà exister. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/content_blocks/update' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+  "content_block_id" :"content_block_id", 
+  "name": "content_block",
+  "description": "This is my Content Block",
+  "content": "HTML or text content within block",
+  "state": "draft",
+  "tags": ["marketing"]
+}'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+  "content_block_id": (string) Your newly generated block id,
+  "liquid_tag": (string) The generated block tag from the Content Block name,
+  "created_at": (string) The time the Content Block was created in ISO 8601,
+  "message": "success"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| `Content cannot be blank` |
+| `Content must be a string` | Assurez-vous que votre contenu est compris entre des guillemets (`""`). |
+| `Content must be smaller than 50kb` | Le contenu de votre bloc de contenu doit être inférieur à 50 Ko. |
+| `Content contains malformed liquid` | Le langage Liquid fourni n’est pas valide ou pas analysable. Réessayez avec un langage Liquid valide ou contactez-nous pour obtenir de l’aide. |
+| `Content Block cannot be referenced within itself` |
+| `Content Block description cannot be blank` |
+| `Content Block description must be a string` | Assurez-vous que la description de votre bloc de contenu est comprise entre des guillemets (`""`). |
+| `Content Block description must be shorter than 250 characters` |
+| `Content Block name cannot be blank` |
+| `Content Block name must be shorter than 100 characters` |
+| `Content Block name can only contain alphanumeric characters` | Les noms de bloc de contenu peuvent comprendre l’un des caractères suivants : les lettres (majuscules ou minuscules) de `A` à `Z`, les chiffres de `0` à `9`, les tirets `-`, et les traits de soulignement `_`. Il ne peut pas contenir de caractères non alphanumériques comme des émojis, `!`, `@`, `~`, `&` et d’autres caractères « spéciaux ». |
+| `Content Block with this name already exists` | Essayez un autre nom. |
+| `Content Block name cannot be updated for active Content Blocks` |
+| `Content Block state must be either active or draft` |
+| `Active Content Block can not be updated to Draft. Create a new Content Block.` |
+| `Tags must be an array` | Les balises doivent être un tableau de chaînes de caractères, par exemple `["marketing", "promotional", "transactional"]`. |
+| `All tags must be strings` | Assurez-vous que vos balises sont comprises entre des guillemets (`""`). |
+| `Some tags could not be found` | Pour ajouter une balise lors de la création d’un bloc de contenu, la balise doit déjà exister dans Braze. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/templates/email_templates.md b/_lang/fr_fr/_api/endpoints/templates/email_templates.md
new file mode 100644
index 00000000000..aad0fbf20d1
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/email_templates.md
@@ -0,0 +1,5 @@
+---
+nav_title: Modèles d’e-mail
+config_only: true
+noindex: true
+---
diff --git a/_lang/fr_fr/_api/endpoints/templates/email_templates/get_list_email_templates.md b/_lang/fr_fr/_api/endpoints/templates/email_templates/get_list_email_templates.md
new file mode 100644
index 00000000000..9912e0aef3c
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/email_templates/get_list_email_templates.md
@@ -0,0 +1,66 @@
+---
+nav_title: "GET : Répertorier les modèles d’e-mail disponibles"
+article_title: "GET : Répertorier les modèles d’e-mail disponibles"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Répertorier les modèles d’e-mail disponibles."
+
+---
+{% api %}
+# Répertorier les modèles d’e-mail disponibles
+{% apimethod get %}
+/templates/email/list
+{% endapimethod %}
+
+> Utilisez cet endpoint pour obtenir une liste des modèles d’e-mails disponibles sur votre compte Braze.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#eec24bf4-a3f4-47cb-b4d8-bb8f03964cca {% endapiref %}
+
+## Conditions préalables
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `templates.email.list`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `modified_after`  | Facultatif | Chaîne de caractères au format [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)  | Récupérer uniquement les modèles mis à jour à l’heure donnée ou après. |
+| `modified_before`  |  Facultatif | Chaîne de caractères au format [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)  | Récupérer uniquement les modèles mis à jour à l’heure donnée ou avant. |
+| `limit` | Facultatif | Nombre positif | Nombre maximum de modèles à récupérer. Par défaut à 100 si non renseigné, avec une valeur maximale acceptable de 1 000. |
+| `offset`  |  Facultatif | Nombre positif | Nombre de modèles à ignorer avant de renvoyer le reste des modèles qui correspondent aux critères de recherche. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/templates/email/list?modified_after=2020-01-01T01:01:01.000000&modified_before=2020-02-01T01:01:01.000000&limit=1&offset=0' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY'
+```
+
+## Réponse 
+
+{% alert important %}
+Les modèles créés à l'aide de l'éditeur par glisser-déposer pour l'e-mail ne sont pas fournis dans cette réponse.
+{% endalert %}
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+  "count": the number of templates returned
+  "templates": [template with the following properties]:
+    "email_template_id": (string) your email template's API Identifier,
+    "template_name": (string) the name of your email template,
+    "created_at": (string) the time the email was created at in ISO 8601,
+    "updated_at": (string) the time the email was updated in ISO 8601,
+    "tags": (array of strings) tags appended to the template
+}
+```
+{% endapi %}
+
+
+
diff --git a/_lang/fr_fr/_api/endpoints/templates/email_templates/get_see_email_template_information.md b/_lang/fr_fr/_api/endpoints/templates/email_templates/get_see_email_template_information.md
new file mode 100644
index 00000000000..719afb2c8e4
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/email_templates/get_see_email_template_information.md
@@ -0,0 +1,69 @@
+---
+nav_title: "GET : Voir les informations sur les modèles d’e-mail"
+article_title: "GET : Voir les informations sur les modèles d’e-mail"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Afficher les modèles d’e-mail."
+
+---
+{% api %}
+# Voir les informations sur les modèles d’e-mail
+{% apimethod get %}
+/templates/email/info
+{% endapimethod %}
+
+> Utilisez cet endpoint pour obtenir des informations sur vos modèles d’e-mail.
+
+{% alert important %}
+Les modèles créés à l'aide de l'éditeur par glisser-déposer pour l'e-mail ne sont pas acceptés.
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#e98d2d5b-62fe-4358-b391-9fe9e460d0ac {% endapiref %}
+
+## Conditions préalables
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `templates.email.info`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `email_template_id`  | Requis | Chaîne de caractères | Voir l'[identifiant API du modèle d'e-mail]({{site.baseurl}}/api/identifier_types/). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/templates/email/info?email_template_id={{email_template_id}}' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY'
+```
+{% endraw %}
+
+## Réponse 
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+  "email_template_id": (string) Your email template's API Identifier,
+  "template_name": (string) The name of your email template,
+  "description": (string) The email template description,
+  "subject": (string) The email template subject line,
+  "preheader": (optional, string) The email preheader used to generate previews in some clients),
+  "body": (optional, string) The email template body that may include HTML,
+  "plaintext_body": (optional, string) A plaintext version of the email template body,
+  "should_inline_css": (optional, boolean) Whether there is inline CSS in the body of the template - defaults to the css inlining value for the workspace,
+  "tags": (string) Tag names,
+  "created_at": (string) The time the email was created at in ISO 8601,
+  "updated_at": (string) The time the email was updated in ISO 8601
+}
+```
+
+Les images de cette réponse apparaîtront dans la variable `body` sous forme HTML.
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/templates/email_templates/post_create_email_template.md b/_lang/fr_fr/_api/endpoints/templates/email_templates/post_create_email_template.md
new file mode 100644
index 00000000000..d2127c0a9e1
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/email_templates/post_create_email_template.md
@@ -0,0 +1,93 @@
+---
+nav_title: "POST : Créer un modèle d’e-mail"
+article_title: "POST : Créer des modèles d’e-mail"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Créer des modèles d’e-mail."
+---
+{% api %}
+# Créer un modèle d’e-mail
+{% apimethod post %}
+/templates/email/create
+{% endapimethod %}
+
+> Utilisez cet endpoint pour créer des modèles d’e-mail sur le tableau de bord de Braze. 
+
+Ces modèles seront disponibles sur la page **Modèles et médias.**  La réponse de cet endpoint comprend un champ pour `email_template_id`, qui peut être utilisé pour mettre à jour le modèle lors des appels d’API suivants.
+
+Le statut de l’abonnement aux e-mails des utilisateurs peut être mis à jour et récupéré via Braze à l’aide d’une API RESTful. Vous pouvez utiliser l’API pour configurer une synchronisation bidirectionnelle entre Braze et d’autres systèmes de messagerie ou votre propre base de données. Toutes les demandes d’API sont faites sur HTTPS.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#5eb1fe0d-2795-474d-aaf2-c4e2977dc94b {% endapiref %}
+
+## Conditions préalables
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `templates.email.create`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+   "template_name": (required, string) The name of your email template,
+   "subject": (required, string) The email template subject line,
+   "body": (required, string) The email template body that may include HTML,
+   "plaintext_body": (optional, string) A plaintext version of the email template body,
+   "preheader": (optional, string) The email preheader used to generate previews in some clients,
+   "tags": (optional, Array of Strings) Tags must already exist,
+   "should_inline_css": (optional, Boolean) If `true`, the `inline_css` feature is used on this template.
+ }
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`template_name`|Requis|Chaîne de caractères|Nom de votre modèle d’e-mail|
+|`subject`|Requis|Chaîne de caractères|Ligne Objet du modèle d’e-mail.|
+|`body`|Requis|Chaîne de caractères|Corps du modèle d’e-mail pouvant inclure du HTML.|
+|`plaintext_body`|Facultatif|Chaîne de caractères|Une version en texte brut du corps du modèle d’e-mail.|
+|`preheader`|Facultatif|Chaîne de caractères|Accroche d’e-mail utilisée pour générer des aperçus chez certains clients.|
+|`tags`|Facultatif|Chaîne de caractères|Les [étiquettes]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) doivent déjà exister.|
+|`should_inline_css`|Facultatif|Valeur booléenne|Active ou désactive la fonction `inline_css` par modèle. S'il n'est pas fourni, Braze utilisera le paramètre par défaut pour le groupe d'applications. `true` ou `false` est attendu.|
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/templates/email/create' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+  "template_name": "email_template_name",
+  "subject": "Welcome to my email template!",
+  "body": "This is the text within my email body and https://www.braze.com/ here is a link to Braze.com.",
+  "plaintext_body": "This is the text within my email body and here is a link to https://www.braze.com/.",
+  "preheader": "My preheader is pretty cool.",
+  "tags": ["Tag1", "Tag2"]
+}'
+```
+
+## Erreurs possibles
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées, le cas échéant.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| Le nom du modèle est obligatoire | Saisissez un nom de modèle. |
+| Les balises doivent être un tableau | Les balises doivent être un tableau de chaînes de caractères, par exemple `["marketing", "promotional", "transactional"]`. |
+| Toutes les balises doivent être des chaînes de caractères | Assurez-vous que vos balises sont comprises entre des guillemets (`""`). |
+| Certaines balises sont introuvables | Pour ajouter une balise lors de la création d’un modèle d’e-mail, la balise doit déjà exister dans Braze. |
+| L’e-mail doit comporter des noms de bloc de contenu valides | L’e-mail peut contenir des blocs de contenu qui n’existent pas dans cet environnement. |
+| Valeur non valide pour `should_inline_css`. `true` ou `false` était attendu | Ce paramètre accepte uniquement les valeurs booléennes (vrai ou faux). Assurez-vous que la valeur de `should_inline_css` n’est pas comprise entre des guillemets (`""`), sinon la valeur est envoyée comme chaîne de caractères. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/templates/email_templates/post_update_email_template.md b/_lang/fr_fr/_api/endpoints/templates/email_templates/post_update_email_template.md
new file mode 100644
index 00000000000..eba7d8eec60
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/templates/email_templates/post_update_email_template.md
@@ -0,0 +1,95 @@
+---
+nav_title: "POST : Mettre à jour le modèle d’e-mail"
+article_title: "POST : Mettre à jour les modèles d’e-mail"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour les modèles d’e-mail."
+
+---
+{% api %}
+# Mettre à jour les modèles d’e-mail existants
+{% apimethod post %}
+/templates/email/update
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour des modèles d’e-mail sur le tableau de bord de Braze. 
+
+Vous pouvez accéder au site `email_template_id` d'un modèle d'e-mail en naviguant jusqu'à lui sur la page **Modèles et médias.**  L’[endpoint Créer un modèle d’e-mail]({{site.baseurl}}/api/endpoints/templates/email_templates/post_create_email_template/) renvoie également une référence `email_template_id`.
+
+Tous les champs autres que l’`email_template_id` sont facultatifs, mais vous devez spécifier au moins un champ à mettre à jour.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#afb25494-3350-458d-932d-5bf4220049fa {% endapiref %}
+
+## Conditions préalables
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `templates.email.update`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='default' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+  "email_template_id": (required, string) Your email template's API Identifier,
+  "template_name": (optional, string) The name of your email template,
+  "subject": (optional, string) The email template subject line,
+  "body": (optional, string) The email template body that may include HTML,
+  "plaintext_body": (optional, string) A plaintext version of the email template body,
+  "preheader": (optional, string) The email preheader used to generate previews in some clients,
+  "tags": (optional, array of Strings) Tags must already exist,
+  "should_inline_css": (optional, Boolean) If `true`, the `inline_css` feature will be applied to the template.
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`email_template_id`| Requis |Chaîne de caractères|[L'identifiant API de votre modèle d'e-mail]({{site.baseurl}}/api/identifier_types/).|
+|`template_name`|Facultatif|Chaîne de caractères|Nom de votre modèle d’e-mail|
+|`subject`|Facultatif|Chaîne de caractères|Ligne Objet du modèle d’e-mail.|
+|`body`|Facultatif|Chaîne de caractères|Corps du modèle d’e-mail pouvant inclure du HTML.|
+|`plaintext_body`|Facultatif|Chaîne de caractères|Une version en texte brut du corps du modèle d’e-mail.|
+|`preheader`|Facultatif|Chaîne de caractères|Accroche d’e-mail utilisée pour générer des aperçus chez certains clients.|
+|`tags`|Facultatif|Chaîne de caractères|Les [étiquettes]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/) doivent déjà exister.|
+|`should_inline_css`|Facultatif|Valeur booléenne|Active ou désactive la fonction `inline_css` par modèle. Si non renseigné, Braze utilisera le paramètre par défaut de l’AppGroup. `true` ou `false` est attendu.|
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/templates/email/update' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+  "email_template_id": "email_template_id",
+  "template_name": "Weekly Newsletter",
+  "subject": "This Week'\''s Styles",
+  "body": "Check out this week'\''s digital lookbook to inspire your outfits. Take a look at https://www.braze.com/",
+  "plaintext_body": "This is the updated text within my email body and here is a link to https://www.braze.com/.",
+  "preheader": "We want you to have the best looks this summer",
+  "tags": ["Tag1", "Tag2"]
+}'
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées, le cas échéant.
+
+| Erreur | Résolution des problèmes |
+| --- | --- |
+| Le nom du modèle est obligatoire | Saisissez un nom de modèle. |
+| Les balises doivent être un tableau | Les balises doivent être un tableau de chaînes de caractères, par exemple `["marketing", "promotional", "transactional"]`. |
+| Toutes les balises doivent être des chaînes de caractères | Assurez-vous que vos balises sont comprises entre des guillemets (`""`). |
+| Certaines balises sont introuvables | Pour ajouter une balise lors de la création d’un modèle d’e-mail, la balise doit déjà exister dans Braze. |
+| Valeur non valide pour `should_inline_css`. `true` ou `false` était attendu | Ce paramètre accepte uniquement les valeurs booléennes (vrai ou faux). Assurez-vous que la valeur de `should_inline_css` n’est pas comprise entre des guillemets (`""`), sinon la valeur est envoyée comme chaîne de caractères. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/translations.md b/_lang/fr_fr/_api/endpoints/translations.md
new file mode 100644
index 00000000000..1cd1fad627a
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/translations.md
@@ -0,0 +1,38 @@
+---
+nav_title: Traductions
+article_title: Endpoints de traduction
+search_tag: Endpoint
+page_order: 9
+layout: dev_guide
+
+description: "Cette page d’accueil répertorie les endpoints de traduction de Braze."
+page_type: landing
+
+guide_top_header: "Endpoints de traduction"
+guide_top_text: "Utilisez les endpoints de traduction de Braze pour gérer et mettre à jour les traductions de vos campagnes et canvas."
+
+guide_featured_title: ""
+guide_featured_list:
+  - name: "GET : Voir les traductions pour une campagne"
+    link: /docs/api/endpoints/translations/get_bulk_translations_campaigns/
+    image: /assets/img/braze_icons/message-plus-square.svg
+  - name: "GET : Afficher les traductions d’un canvas"
+    link: /docs/api/endpoints/translations/get_bulk_translations_canvases/
+    image: /assets/img/braze_icons/message-plus-square.svg
+  - name: "GET : Voir la traduction pour une campagne"
+    link: /docs/api/endpoints/translations/get_translation_campaign/
+    image: /assets/img/braze_icons/message-plus-square.svg
+  - name: "GET : Afficher la traduction d’un canvas"
+    link: /docs/api/endpoints/translations/get_translation_canvas/
+    image: /assets/img/braze_icons/message-plus-square.svg
+  - name: "PUT : Mettre à jour la traduction dans une campagne"
+    link: /docs/api/endpoints/translations/put_update_translation_campaign/
+    image: /assets/img/braze_icons/target-04.svg
+  - name: "PUT : Mise à jour de la traduction dans un canvas"
+    link: /docs/api/endpoints/translations/put_update_translation_canvas/
+    image: /assets/img/braze_icons/target-04.svg
+---
+
+{% alert important %}
+Les endpoints de traduction de Braze sont actuellement en accès anticipé. Contactez votre gestionnaire de compte Braze si vous souhaitez participer à l’accès anticipé.
+{% endalert %}
diff --git a/_lang/fr_fr/_api/endpoints/translations/get_bulk_translations_campaigns.md b/_lang/fr_fr/_api/endpoints/translations/get_bulk_translations_campaigns.md
new file mode 100644
index 00000000000..7fc87f852ad
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/translations/get_bulk_translations_campaigns.md
@@ -0,0 +1,104 @@
+---
+nav_title: "GET : Afficher les traductions d'une campagne"
+article_title: "GET : Afficher les traductions d'une campagne"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article décrit en détail l’endpoint Afficher les traductions pour une campagne."
+---
+
+{% api %}
+# Voir les traductions pour une campagne
+{% apimethod get %}
+/campagnes/traductions
+{% endapimethod %}
+
+> Utilisez ce point de terminaison pour voir toutes les traductions de chaque variante de message dans une campagne.
+
+{% alert important %}
+La visualisation des traductions des messages de campagne via l'API est actuellement en accès anticipé. Contactez votre gestionnaire de compte Braze si vous souhaitez participer à l’accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `campaigns.translations.get`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 250 000 requêtes par jour.
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`campaign_id`| Requis pour traduire une campagne | Chaîne de caractères | L'ID de votre campagne. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/campaign/translations' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+Quatre réponses de code de statut existent pour cet endpoint : `200`, `400`, `404` et `429`.
+
+## Exemple de réponse réussie
+
+Le code de statut `200` pourrait retourner l’en-tête et le corps de réponse suivant.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+	"translations": [
+		{
+			"locale": {
+ 				"name": "zh-HK",
+ 				"country": "Hong Kong",
+ 				"language": "Chinese (Traditional)",
+			},
+			"translation_map": {
+				"id_0": "Hello",
+				"id_1": "My name is Jacky",
+				"id_2": "Where is the library?"
+			}
+		}
+	]
+}
+```
+
+## Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+	"errors": [
+		{
+			"message": "This message does not support multi-language."
+		}
+	]
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Message d’erreur                           | Résolution des problèmes                                                                    |
+|-----------------------------------------|------------------------------------------------------------------------------------|
+| `INVALID_CAMPAIGN_ID`                   | Confirmez que l'ID de la campagne correspond à la campagne que vous traduisez.                   |
+| `INVALID_MESSAGE_VARIATION_ID`          | Confirmez que votre identifiant de message est correct.                                                |
+| `MESSAGE_NOT_FOUND`                     | Vérifiez que le message à traduire.                                           |
+| `MULTI_LANGUAGE_NOT_ENABLED`            | Les paramètres multilingues ne sont pas activés pour votre espace de travail.                       |
+| `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Seules les campagnes par e-mail ou les messages Canvas avec des e-mails peuvent être traduits.             |
+| `UNSUPPORTED_CHANNEL`                   | Seuls les messages dans les campagnes par e-mail ou les messages Canvas avec des e-mails peuvent être traduits. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/translations/get_bulk_translations_canvases.md b/_lang/fr_fr/_api/endpoints/translations/get_bulk_translations_canvases.md
new file mode 100644
index 00000000000..748f61bcf2f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/translations/get_bulk_translations_canvases.md
@@ -0,0 +1,105 @@
+---
+nav_title: "GET : Afficher les traductions d’un canvas"
+article_title: "GET : Afficher les traductions d’un canvas"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Répertorier les traductions pour un canvas."
+---
+
+{% api %}
+# Répertorier les traductions pour un canvas
+{% apimethod get %}
+/canvases/translations
+{% endapimethod %}
+
+> Utilisez cet endpoint pour afficher toutes les traductions d'un Canvas.
+
+{% alert important %}
+L’affichage des traductions d’un canvas via l’API est actuellement en accès anticipé. Contactez votre gestionnaire de compte Braze si vous souhaitez participer à l’accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.translations.get`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 250 000 requêtes par jour.
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`canvas_id`| Requis | Chaîne de caractères | L'ID de votre Canvas. |
+|`step_id`| Requis | Chaîne de caractères | L'ID de votre étape du canvas. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/canvas/translations' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+Quatre réponses de code de statut existent pour cet endpoint : `200`, `400`, `404` et `429`.
+
+## Exemple de réponse réussie
+
+Le code de statut `200` pourrait retourner l’en-tête et le corps de réponse suivant.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+	"translations": [
+		{
+			"locale": {
+ 				"name": "zh-HK",
+ 				"country": "Hong Kong",
+ 				"language": "Chinese (Traditional)",
+			},
+			"translation_map": {
+				"id_0": "Hello",
+				"id_1": "My name is Jacky",
+				"id_2": "Where is the library?"
+			}
+		}
+	]
+}
+```
+
+## Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+	"errors": [
+		{
+			"message": "This message does not support multi-language."
+		}
+	]
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Message d’erreur                           | Résolution des problèmes                                                                    |
+|-----------------------------------------|------------------------------------------------------------------------------------|
+| `INVALID_CAMPAIGN_ID`                   | Confirmez que l'ID de la campagne correspond à la campagne que vous traduisez.                   |
+| `INVALID_MESSAGE_VARIATION_ID`          | Confirmez que l'ID de votre message est correct.                                                |
+| `MESSAGE_NOT_FOUND`                     | Vérifiez que le message à traduire.                                           |
+| `MULTI_LANGUAGE_NOT_ENABLED`            | Les paramètres multilingues ne sont pas activés pour votre espace de travail.                       |
+| `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Seules les campagnes de communication par e-mail ou les messages canvas contenant des e-mails peuvent être traduits.             |
+| `UNSUPPORTED_CHANNEL`                   | Seuls les messages des campagnes de communication par e-mail ou les envois de canvas par e-mail peuvent être traduits. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/translations/get_translation_campaign.md b/_lang/fr_fr/_api/endpoints/translations/get_translation_campaign.md
new file mode 100644
index 00000000000..e47f773d8b2
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/translations/get_translation_campaign.md
@@ -0,0 +1,109 @@
+---
+nav_title: "GET : Voir la traduction pour une campagne"
+article_title: "GET : Voir la traduction pour une campagne"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article décrit en détail l’endpoint Afficher les traductions pour une campagne."
+---
+
+{% api %}
+# Voir la traduction d'une campagne
+{% apimethod get %}
+/campaign/translations/?locale_id={locale_id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour afficher un message de campagne traduit afin de voir à quoi ressemble ce message pour un utilisateur.
+
+{% alert important %}
+L'affichage d'un message de campagne traduit via l'API est actuellement en accès anticipé. Contactez votre gestionnaire de compte Braze si vous souhaitez participer à l’accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `campaigns.translations.get`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 250 000 requêtes par jour.
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`campaign_id`| Requis | Chaîne de caractères | L'ID de votre campagne. |
+|`message_variation_id`| Requis | Chaîne de caractères | L'ID de la variation de votre message. |
+|`locale_id`| Requis | Chaîne de caractères | L'ID de la locale. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+
+## Exemple de demande
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/campaign/translations/?locale_id={locale_id}' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+Quatre réponses de code de statut existent pour cet endpoint : `200`, `400`, `404` et `429`.
+
+## Exemple de réponse réussie
+
+Le code de statut `200` pourrait retourner l’en-tête et le corps de réponse suivant.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+	"translations": [
+		{
+			"locale": {
+ 				"name": "es-MX",
+ 				"country": "Mexico",
+ 				"language": "Spanish",
+			},
+			"translation_map": {
+				"id_0": "Hello",
+				"id_1": "My name is Jacky",
+				"id_2": "Where is the library?"
+			}
+		}
+	]
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+	"errors": [
+		{
+			"message": "Invalid locale ID"
+		}
+	]
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Message d’erreur                           | Résolution des problèmes                                                                    |
+|-----------------------------------------|------------------------------------------------------------------------------------|
+| `INVALID_CAMPAIGN_ID`                   | Confirmez que l'ID de la campagne correspond à la campagne que vous traduisez.                   |
+| `INVALID_LOCALE_ID`                     | Confirmez que votre ID local existe dans la traduction de votre message.                         |
+| `INVALID_MESSAGE_VARIATION_ID`          | Confirmez que l'ID de votre message est correct.                                                |
+| `MESSAGE_NOT_FOUND`                     | Vérifiez que le message à traduire.                                           |
+| `LOCALE_NOT_FOUND`                      | Confirmez que le paramètre local existe dans vos paramètres multilingues.                         |
+| `MULTI_LANGUAGE_NOT_ENABLED`            | Les paramètres multilingues ne sont pas activés pour votre espace de travail.                       |
+| `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Seules les campagnes de communication par e-mail ou les messages canvas contenant des e-mails peuvent être traduits.             |
+| `UNSUPPORTED_CHANNEL`                   | Seuls les messages des campagnes de communication par e-mail ou les envois de canvas par e-mail peuvent être traduits. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/translations/get_translation_canvas.md b/_lang/fr_fr/_api/endpoints/translations/get_translation_canvas.md
new file mode 100644
index 00000000000..a036fdb9ee4
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/translations/get_translation_canvas.md
@@ -0,0 +1,108 @@
+---
+nav_title: "GET : Afficher la traduction d’un canvas"
+article_title: "GET : Afficher la traduction d’un canvas"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Afficher la traduction d’un canvas."
+---
+
+{% api %}
+# Afficher la traduction d’un canvas
+{% apimethod get %}
+/canvas/translations/?locale_id={locale_id}
+{% endapimethod %}
+
+> Utilisez cet endpoint pour afficher un message traduit afin de voir à quoi ressemble ce message pour un utilisateur.
+
+{% alert important %}
+L’affichage d’un message traduit pour un canvas via l’API est actuellement en accès anticipé. Contactez votre gestionnaire de compte Braze si vous souhaitez participer à l’accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.translations.get`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 250 000 requêtes par jour.
+
+## Paramètres de chemin
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`canvas_id`| Requis | Chaîne de caractères | L'ID de votre Canvas. |
+|`message_variation_id`| Requis | Chaîne de caractères | L'ID de la variation de votre message. |
+|`locale_id`| Requis | Chaîne de caractères | L'ID de la locale. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```
+curl --location --request GET 'https://rest.iad-03.braze.com/canvas/translations/?locale_id={locale_id}' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Réponse
+
+Quatre réponses de code de statut existent pour cet endpoint : `200`, `400`, `404` et `429`.
+
+## Exemple de réponse réussie
+
+Le code de statut `200` pourrait retourner l’en-tête et le corps de réponse suivant.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+	"translations": [
+		{
+			"locale": {
+ 				"name": "es-MX",
+ 				"country": "Mexico",
+ 				"language": "Spanish",
+			},
+			"translation_map": {
+				"id_0": "Hello",
+				"id_1": "My name is Jacky",
+				"id_2": "Where is the library?"
+			}
+		}
+	]
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+	"errors": [
+		{
+			"message": "Invalid locale ID"
+		}
+	]
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Message d’erreur                           | Résolution des problèmes                                                                    |
+|-----------------------------------------|------------------------------------------------------------------------------------|
+| `INVALID_CAMPAIGN_ID`                   | Confirmez que l'ID de la campagne correspond à la campagne que vous traduisez.                   |
+| `INVALID_LOCALE_ID`                     | Confirmez que votre ID local existe dans la traduction de votre message.                         |
+| `INVALID_MESSAGE_VARIATION_ID`          | Confirmez que l'ID de votre message est correct.                                                |
+| `MESSAGE_NOT_FOUND`                     | Vérifiez que le message à traduire.                                           |
+| `LOCALE_NOT_FOUND`                      | Confirmez que le paramètre local existe dans vos paramètres multilingues.                         |
+| `MULTI_LANGUAGE_NOT_ENABLED`            | Les paramètres multilingues ne sont pas activés pour votre espace de travail.                       |
+| `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Seules les campagnes de communication par e-mail ou les messages canvas contenant des e-mails peuvent être traduits.             |
+| `UNSUPPORTED_CHANNEL`                   | Seuls les messages des campagnes de communication par e-mail ou les envois de canvas par e-mail peuvent être traduits. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/translations/put_update_translation_campaign.md b/_lang/fr_fr/_api/endpoints/translations/put_update_translation_campaign.md
new file mode 100644
index 00000000000..c3b836f07e3
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/translations/put_update_translation_campaign.md
@@ -0,0 +1,102 @@
+---
+nav_title: "PUT : Mettre à jour la traduction dans une campagne"
+article_title: "PUT : Mettre à jour la traduction dans une campagne"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour la traduction dans une campagne."
+---
+
+{% api %}
+# Mise à jour de la traduction dans une campagne
+{% apimethod put %}
+/campagnes/traductions
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour plusieurs traductions pour une campagne.
+
+{% alert important %}
+La mise à jour d'une traduction dans une campagne via l'API est actuellement en accès anticipé. Contactez votre gestionnaire de compte Braze si vous souhaitez participer à l’accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `campaigns.translations.update`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 250 000 requêtes par jour.
+
+## Paramètres de chemin
+
+Cet endpoint n’a pas de chemin de paramètres.
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`locale_id`| Requis | Chaîne de caractères | L'ID de la locale. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "campaign_id": "9a0ba932-11c0-4c33-b529-e79aafc12409",
+    "message_variation_id": "f5896eec-847d-4c0d-a4b6-7695e67520d7",
+    "locale_id": "3fa10d31-83ae-4ff4-9631-f52cea9ec8fa",
+    "translation_map": {
+        "id_4": "¿Dónde está la biblioteca? Me llamo T-Bone, La araña discoteca.",
+        "subject_1": "¿Dónde está la biblioteca? Me llamo T-Bone, La araña discoteca.",
+        "id_1": "¿Dónde está la biblioteca? Me llamo T-Bone, La araña discoteca.",
+        "image": "¿Dónde está la biblioteca? Me llamo T-Bone, La araña discoteca."
+    }
+}
+```
+
+## Exemple de réponse réussie
+
+```json
+{
+	"message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+	"errors": [
+		{
+			"message": "Something went wrong. Translation IDs are mismatched or translated text exceeds limits."
+		}
+	]
+}
+```
+
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Message d’erreur                           | Résolution des problèmes                                                                    |
+|-----------------------------------------|------------------------------------------------------------------------------------|
+| `INVALID_CAMPAIGN_ID`                   | Confirmez que l'ID de la campagne correspond à la campagne que vous traduisez.                   |
+| `INVALID_LOCALE_ID`                     | Confirmez que votre ID local existe dans la traduction de votre message.                         |
+| `INVALID_MESSAGE_VARIATION_ID`          | Confirmez que l'ID de votre message est correct.                                                |
+| `INVALID_TRANSLATION_OBJECT`            | Les ID de traduction ne correspondent pas ou le texte traduit dépasse les limites.                  |
+| `MESSAGE_NOT_FOUND`                     | Vérifiez que le message à traduire.                                           |
+| `LOCALE_NOT_FOUND`                      | Confirmez que le paramètre local existe dans vos paramètres multilingues.                         |
+| `MISSING_TRANSLATIONS`                  | Les ID de traduction doivent correspondre au message.                                         |
+| `MULTI_LANGUAGE_NOT_ENABLED`            | Les paramètres multilingues ne sont pas activés pour votre espace de travail.                       |
+| `MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE` | Seules les campagnes de communication par e-mail ou les messages canvas contenant des e-mails peuvent être traduits.             |
+| `UNSUPPORTED_CHANNEL`                   | Seuls les messages des campagnes de communication par e-mail ou les envois de canvas par e-mail peuvent être traduits. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/translations/put_update_translation_canvas.md b/_lang/fr_fr/_api/endpoints/translations/put_update_translation_canvas.md
new file mode 100644
index 00000000000..7420cb09522
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/translations/put_update_translation_canvas.md
@@ -0,0 +1,113 @@
+---
+nav_title: "PUT : Mise à jour de la traduction dans un canvas"
+article_title: "PUT : Mise à jour de la traduction dans un canvas"
+search_tag: Endpoint
+page_order: 1
+
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Mettre à jour la traduction dans un canvas."
+---
+
+{% api %}
+# Mise à jour de la traduction dans un canvas
+{% apimethod put %}
+/canvas/translations
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour plusieurs traductions pour un Canvas.
+
+{% alert important %}
+La mise à jour d’une traduction pour les messages de canvas via l’API est actuellement en accès anticipé. Contactez votre gestionnaire de compte Braze si vous souhaitez participer à l’accès anticipé.
+{% endalert %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/basics#rest-api-key/) avec l’autorisation `canvas.translations.update`.
+
+## Limite de débit
+
+Cet endpoint a une limitation du débit de 250 000 requêtes par jour.
+
+## Paramètres de chemin
+
+Cet endpoint n’a pas de chemin de paramètres.
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+|`locale_id`| Requis | Chaîne de caractères | L'ID de la locale. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+    "canvas_id": "9a0ba932-11c0-4c33-b529-e79aafc12409",
+    "message_variation_id": "f5896eec-847d-4c0d-a4b6-7695e67520d7",
+    "locale_id": "3fa10d31-83ae-4ff4-9631-f52cea9ec8fa",
+    "translation_map": {
+        "id_4": "¿Dónde está la biblioteca? Me llamo T-Bone, La araña discoteca.",
+        "subject_1": "¿Dónde está la biblioteca? Me llamo T-Bone, La araña discoteca.",
+        "id_1": "¿Dónde está la biblioteca? Me llamo T-Bone, La araña discoteca.",
+        "image": "¿Dónde está la biblioteca? Me llamo T-Bone, La araña discoteca."
+    }
+}
+```
+
+## Exemple de réponse réussie
+
+```json
+{
+	"message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+	"errors": [
+		{
+			"message": "Something went wrong. Translation IDs are mismatched or translated text exceeds limits."
+		}
+	]
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les erreurs renvoyées possibles et les étapes de résolution des problèmes associées.
+
+| Message d’erreur | Résolution des problèmes |
+| --- | --- |
+|`INVALID_CAMPAIGN_ID`|Confirmez que l'ID de la campagne correspond à la campagne que vous traduisez.|
+|`INVALID_LOCALE_ID`|Confirmez que votre ID local existe dans la traduction de votre message.|
+|`INVALID_MESSAGE_VARIATION_ID`|Confirmez que l'ID de votre message est correct.|
+|`INVALID_TRANSLATION_OBJECT`|Les ID de traduction ne correspondent pas ou le texte traduit dépasse les limites.|
+|`MESSAGE_NOT_FOUND`|Vérifiez que le message à traduire.|
+|`LOCALE_NOT_FOUND`| Confirmez que le paramètre local existe dans vos paramètres multilingues. |
+|`MISSING_TRANSLATIONS`|Les ID de traduction doivent correspondre au message.|
+|`MULTI_LANGUAGE_NOT_ENABLED`|Les paramètres multilingues ne sont pas activés pour votre espace de travail.|
+|`MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE`|Seules les campagnes de communication par e-mail ou les messages canvas contenant des e-mails peuvent être traduits.|
+|`UNSUPPORTED_CHANNEL`| Seuls les messages des campagnes de communication par e-mail ou les envois de canvas par e-mail peuvent être traduits.|
+{: .reset-td-br-1 .reset-td-br-2}
+
+
+          INVALID_CAMPAIGN_ID = "Invalid campaign or step ID"
+          INVALID_LOCALE_ID = "Invalid locale ID"
+          INVALID_MESSAGE_VARIATION_ID = "Invalid message ID"
+          INVALID_TRANSLATION_OBJECT = "Invalid translation object"
+          MESSAGE_NOT_FOUND = "Message not found"
+          LOCALE_NOT_FOUND = "Locale not found"
+          MISSING_TRANSLATIONS = "Missing translations from the request body"
+          MULTI_LANGUAGE_NOT_ENABLED = "Multi-language feature is not enabled on this company"
+          MULTI_LANGUAGE_NOT_ENABLED_ON_MESSAGE = "This message does not have multi-language setup"
+          UNSUPPORTED_CHANNEL = "This message type does not support multi-language"
+
+{% endapi %}
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/endpoints/user_data.md b/_lang/fr_fr/_api/endpoints/user_data.md
new file mode 100644
index 00000000000..886e46f0f98
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data.md
@@ -0,0 +1,49 @@
+---
+nav_title: Données utilisateur
+article_title: Endpoints des données utilisateur
+search_tag: Endpoint
+page_order: 9
+
+local_redirect: #event-object-specification #purchase-object-specification
+  event-object-specification: '/docs/api/objects_filters/event_object/'
+  purchase-object-specification: '/docs/api/objects_filters/purchase_object/'
+
+layout: dev_guide
+
+#Required
+description: "Cette page d’accueil liste les endpoints Braze de données utilisateur."
+page_type: landing
+
+guide_top_header: "Endpoints des données utilisateur"
+guide_top_text: "Les endpoints de données utilisateur de Braze vous permettent de suivre les informations sur vos utilisateurs en enregistrant des données les concernant qui proviennent de l'extérieur de votre application mobile. Vous pouvez également utiliser cette API pour supprimer des utilisateurs à des fins de test ou autres. <br> <br> Tous les endpoints de l'API ont une limite de 4 Mo de données. Les tentatives d'envoi de plus de 4 Mo de données échoueront avec un message HTTP 413 Request Entity Too Large. <br> <br> Les exemples de cette section contiennent l'URL https://rest.iad-01.braze.com, mais il se peut que vous deviez utiliser une URL d'endpoint différente (par exemple, si vous êtes hébergé dans le centre de données européen de Braze ou si vous disposez d'une installation Braze dédiée). Votre gestionnaire du succès des clients Braze vous informera si vous devez utiliser une URL d’endpoint différente."
+
+guide_featured_title: "Endpoints des données utilisateur"
+guide_featured_list:
+  - name: "POST : Créer un nouvel alias utilisateur"
+    link: /docs/api/endpoints/user_data/post_user_alias/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "POST : Mise à jour d'un alias d'utilisateur"
+    link: /docs/api/endpoints/user_data/post_users_alias_update/
+    image: /assets/img/braze_icons/user-edit.svg
+  - name: "POST : Supprimer les données utilisateur"
+    link: /docs/api/endpoints/user_data/post_user_delete/
+    image: /assets/img/braze_icons/user-minus-01.svg
+  - name: "POST : Identifier un utilisateur"
+    link: /docs/api/endpoints/user_data/post_user_identify/
+    image: /assets/img/braze_icons/user-circle.svg
+  - name: "POST : Suivre les utilisateurs"
+    link: /docs/api/endpoints/user_data/post_user_track/
+    image: /assets/img/braze_icons/database-01.svg
+  - name: "POST : Fusionner les utilisateurs"
+    link: /docs/api/endpoints/user_data/post_users_merge/
+    image: /assets/img/braze_icons/users-01.svg
+
+guide_menu_title: "External ID migration endpoints"
+guide_menu_list:
+  - name: "POST : Renommer des ID externes"
+    link: /docs/api/endpoints/user_data/external_id_migration/post_external_ids_rename/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "POST : Supprimer les ID externes obsolètes"
+    link: /docs/api/endpoints/user_data/external_id_migration/post_external_ids_remove/
+    image: /assets/img/braze_icons/user-minus-01.svg
+---
diff --git a/_lang/fr_fr/_api/endpoints/user_data/external_id_migration.md b/_lang/fr_fr/_api/endpoints/user_data/external_id_migration.md
new file mode 100644
index 00000000000..f8527de6e0f
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data/external_id_migration.md
@@ -0,0 +1,22 @@
+---
+nav_title: Migration de l’ID externe
+article_title: "Migration de l’ID externe"
+search_tag: Endpoint
+page_order: 7
+layout: dev_guide
+
+description: "Cette page d’accueil explique et répertorie la fonction de migration de l’ID externe de Braze."
+page_type: landing
+
+guide_top_header: "Migration de l’ID externe"
+guide_top_text: "L’API de migration de l’ID externe vous permet de renommer des ID externes existants (création d’un nouvel ID principal et suppression de l’ID existant) et suppression des ID obsolètes après la migration. <br><br> Nous avons conçu cette solution pour permettre plusieurs identifiants externes afin de prendre en charge une période de migration pendant laquelle les anciennes versions de vos applications encore en circulation qui utilisent l'ancien schéma de dénomination des identifiants externes ne se cassent pas. Nous recommandons vivement de supprimer les identifiants externes obsolètes lorsque votre ancien schéma de dénomination n'est plus utilisé."
+
+guide_featured_title: "Endpoints de migration de l’ID externe"
+guide_featured_list:
+  - name: "POST : Renommer des ID externes"
+    link: /docs/api/endpoints/user_data/external_id_migration/post_external_ids_rename/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: "POST : Supprimer les ID externes obsolètes"
+    link: /docs/api/endpoints/user_data/external_id_migration/post_external_ids_remove/
+    image: /assets/img/braze_icons/user-minus-01.svg
+---
diff --git a/_lang/fr_fr/_api/endpoints/user_data/external_id_migration/post_external_ids_remove.md b/_lang/fr_fr/_api/endpoints/user_data/external_id_migration/post_external_ids_remove.md
new file mode 100644
index 00000000000..74f3179d92a
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data/external_id_migration/post_external_ids_remove.md
@@ -0,0 +1,88 @@
+---
+nav_title: "POST : Supprimer l'ID externe"
+article_title: "POST : Supprimer l'ID externe"
+search_tag: Endpoint
+page_order: 2
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Supprimer des ID externes."
+
+---
+{% api %}
+# Supprimer des ID externes
+{% apimethod post %}
+/users/external_ids/remove
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer les anciens ID externes obsolètes de vos utilisateurs. 
+
+Vous pouvez envoyer jusqu’à 50 ID externes par demande. 
+
+{% alert warning %}
+Cet endpoint supprime complètement l’ID obsolète et ne peut pas être annulé. Utilisez cet endpoint pour enlever des `external_ids` obsolètes qui sont toujours associés à des utilisateurs dans votre système peut vous empêcher définitivement de trouver les données de ces utilisateurs.
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#e16b5340-5f44-42b6-9033-2398faf8908e {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `users.external_ids.remove`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='external id migration' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "external_ids" : (required, array of external identifiers to remove)
+}
+```
+
+### Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `external_ids` | Requis | Tableau de chaînes de caractères | Identifiants externes pour les utilisateurs à supprimer. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/external_ids/remove' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "external_ids" :[
+    "existing_deprecated_external_id_string",
+    ...
+  ]
+}'
+```
+{% alert important %}
+Seuls les ID obsolètes peuvent être supprimés ; la tentative de suppression d’un ID externe principal entraînera une erreur.
+{% endalert %}
+
+## Réponse 
+La réponse confirmera toutes les suppressions réussies et les suppressions infructueuses avec les erreurs associées. Les messages d’erreur dans le champ `removal_errors` référenceront l’index dans le tableau de la demande d’origine.
+
+```
+{
+  "message" : (string) status message,
+  "removed_ids" : (array of strings) successful remove operations,
+  "removal_errors": (array of arrays) <minor error message>
+}
+```
+
+Le champ `message` renverra `success` pour toutes les demandes valides. Des erreurs plus spécifiques sont saisies dans le tableau `removal_errors`. Le champ `message` renvoie une erreur dans les cas suivants :
+- Clé API non valide
+- Tableau `external_ids` vide
+- Tableau `external_ids` avec plus de 50 éléments
+- Atteinte de la limite de débit (plus de 1 000 requêtes/minute)
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/user_data/external_id_migration/post_external_ids_rename.md b/_lang/fr_fr/_api/endpoints/user_data/external_id_migration/post_external_ids_rename.md
new file mode 100644
index 00000000000..f52ee471c8d
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data/external_id_migration/post_external_ids_rename.md
@@ -0,0 +1,112 @@
+---
+nav_title: "POST : Renommer l'ID externe"
+article_title: "POST : Renommer l'ID externe"
+search_tag: Endpoint
+page_order: 1
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Renommer des ID externes."
+
+---
+{% api %}
+# Renommer des ID externes
+{% apimethod post %}
+/users/external_ids/rename
+{% endapimethod %}
+
+> Utilisez cet endpoint pour renommer les ID externes de vos utilisateurs. 
+
+Vous pouvez envoyer jusqu’à 50 objets renommés par demande. 
+
+Cet endpoint définit un nouvel `external_id` (principal) pour l’utilisateur et rend son `external_id` existant obsolète. Cela signifie que l’utilisateur peut être identifié par l’un ou l’autre des `external_id` jusqu’à ce que celui qui est obsolète soit supprimé. La présence de plusieurs ID externes permet de prévoir une période de migration pour que les versions antérieures de vos applications qui utilisent l’ancien schéma de nommage des ID externes ne s’interrompent pas. 
+
+Une fois que votre ancien schéma de nommage n'est plus utilisé, nous vous recommandons vivement de supprimer les ID externes obsolètes à l'aide de l'[endpoint`/users/external_ids/remove`.]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_remove)
+
+{% alert warning %}
+Assurez-vous de supprimer les ID externes obsolètes à l’aide de l’endpoint `/users/external_ids/remove` plutôt que `/users/delete`. L’envoi d’une demande à `/users/delete` avec l’ID externe obsolète supprime entièrement le profil utilisateur et ne peut pas être annulé.
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#17682d2b-1546-4a3c-9703-aa5a12861d7c {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `users.external_ids.rename`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='external id migration' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "external_id_renames" : (required, array of external ID rename objects)
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `external_id_renames` | Requis | Tableau des objets Renommer des identifiants externes | Afficher l’exemple de demande et les limitations suivantes pour la structure de l’objet Renommer des identifiants externes. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+- Le `current_external_id` doit être l’ID principal de l’utilisateur et ne peut pas être un ID obsolète
+- Le `new_external_id` ne doit pas déjà être utilisé comme ID principal ou ID obsolète
+- Les `current_external_id` et `new_external_id` ne peuvent pas être identiques
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/external_ids/rename' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "external_id_renames" :[
+    {
+      "current_external_id": "existing_external_id",
+      "new_external_id" : "new_external_id"
+    }
+  ]
+}'
+```
+
+## Réponse 
+La réponse confirmera tous les renommages réussis et les renommages infructueux avec toutes les erreurs associées. Les messages d’erreur dans le champ `rename_errors` référenceront l’index de l’objet dans le tableau de la demande d’origine.
+
+```
+{
+  "message" : (string) status message,
+  "external_ids" : (array of strings) successful rename operations,
+  "rename_errors": (array of arrays) <minor error message>
+}
+```
+
+Le champ `message` renverra `success` pour toutes les demandes valides. Des erreurs plus spécifiques sont saisies dans le tableau `rename_errors`. Le champ `message` renvoie une erreur dans les cas suivants :
+- Clé API non valide
+- Tableau `external_id_renames` vide
+- Tableau `external_id_renames` avec plus de 50 objets
+- Atteinte de la limite de débit (plus de 1 000 requêtes/minute)
+
+## Foire aux questions
+
+**Cela a-t-il un impact sur le MAU ?**<br>
+Non, puisque le nombre d’utilisateurs restera le même, ils auront simplement un nouvel `external_id`.
+
+**Le comportement des utilisateurs change-t-il au cours du temps ?**<br>
+Non, étant donné que l’utilisateur est toujours le même et que tous ses comportements historiques sont toujours liés à lui.
+
+**Est-il possible de l’exécuter sur des espaces de travail de développement/préproduction ?**<br>
+Oui. En fait, nous vous recommandons vivement d'effectuer un test de migration sur un espace de travail de développement ou de mise à disposition, et de vous assurer que tout s'est bien déroulé avant d'exécuter la migration sur les données de production.
+
+**Est-ce que cela consomme des points de données ?**<br>
+Cette fonctionnalité ne coûte pas de points de données.
+
+**Quel est le délai d’obsolescence recommandé ?**<br>
+Nous n'avons pas de limite stricte quant à la durée pendant laquelle vous pouvez conserver des ID externes dépréciés, mais nous vous recommandons vivement de les supprimer lorsqu'il n'est plus nécessaire de référencer les utilisateurs par l'ID déprécié.
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/user_data/post_user_alias.md b/_lang/fr_fr/_api/endpoints/user_data/post_user_alias.md
new file mode 100644
index 00000000000..29782bac20d
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data/post_user_alias.md
@@ -0,0 +1,94 @@
+---
+nav_title: "POST : Créer un nouvel alias utilisateur"
+article_title: "POST : Créer un nouvel alias utilisateur"
+search_tag: Endpoint
+page_order: 1
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Créer un nouvel alias utilisateur."
+
+---
+{% api %}
+# Créer un nouvel alias utilisateur
+{% apimethod post %}
+/users/alias/new
+{% endapimethod %}
+
+> Utilisez cet endpoint pour ajouter de nouveaux alias utilisateur pour les utilisateurs identifiés existants, ou pour créer de nouveaux utilisateurs non identifiés.
+
+Vous pouvez spécifier jusqu’à 50 alias de l’utilisateur par requête.
+
+L'**ajout d'un alias d'utilisateur pour un utilisateur existant** nécessite qu'une adresse `external_id` soit incluse dans le nouvel objet alias d'utilisateur. Si un `external_id` indiqué dans l’objet qu’aucun utilisateur ne possède cet `external_id`, l’alias ne sera ajouté à aucun utilisateur. Faute d’un `external_id`, un utilisateur sera créé quand même, mais il devra être identifié ultérieurement. Vous pouvez le faire en utilisant l’« identification des utilisateurs » et l’endpoint `users/identify`.
+
+**La création d'un nouvel utilisateur alias uniquement** nécessite que l’`external_id` soit omis du nouvel objet Alias d’utilisateur. Une fois l’utilisateur créé, utilisez l’endpoint `/users/track` pour associer l’utilisateur alias uniquement aux attributs, événements et achats, et l’endpoint `/users/identify` pour identifier l’utilisateur avec un `external_id`.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#5cf18e64-fd02-452f-8c90-9a0f7c4d0487 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `users.alias.new`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='users alias new' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+  "user_aliases" : (required, array of new user alias object)
+}
+```
+
+### Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `user_aliases` | Requis | Objets Tableau des nouveaux alias utilisateur | Voir l'[objet alias d'utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object/).<br><br> Pour plus d'informations sur `alias_name` et `alias_label`, consultez notre documentation sur les [alias de l'utilisateur]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases).|
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+### Corps de demande d’endpoint avec spécification de l’objet Nouvel alias utilisateur
+
+```json
+{
+  "external_id" : (optional, string),
+  "alias_name" : (required, string),
+  "alias_label" : (required, string)
+}
+```
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/alias/new' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+  "user_aliases" :[
+    {
+      "external_id": "external_identifier",
+      "alias_name" : "example_name",
+      "alias_label" : "example_label"
+    }
+  ]
+}'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+    "aliases_processed": 1,
+    "message": "success"
+}
+```
+
+
+{% endapi %}
+
diff --git a/_lang/fr_fr/_api/endpoints/user_data/post_user_delete.md b/_lang/fr_fr/_api/endpoints/user_data/post_user_delete.md
new file mode 100644
index 00000000000..9477d345492
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data/post_user_delete.md
@@ -0,0 +1,103 @@
+---
+nav_title: "POST : Supprimer des utilisateurs"
+article_title: "POST : Supprimer des utilisateurs"
+search_tag: Endpoint
+page_order: 5
+layout: api_page
+page_type: reference
+description: "Cet article décrit les détails de l'endpoint Braze pour supprimer des utilisateurs."
+
+---
+{% api %}
+# Supprimer les utilisateurs
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/users/delete
+{% endapimethod %}
+
+> Utilisez cet endpoint pour supprimer un profil utilisateur en spécifiant un identifiant utilisateur connu.
+
+Vous pouvez inclure jusqu’à 50 `external_ids`, `user_aliases`, ou `braze_ids` dans une seule demande. Seul un des `external_ids`, `user_aliases`, ou `braze_ids` peut être inclus dans une seule demande.
+
+{% alert warning %}
+La suppression des profils utilisateur ne peut pas être annulée. Cette action supprimera définitivement les utilisateurs susceptibles de provoquer des écarts dans vos données. En savoir plus sur ce qui se passe lorsque vous [supprimez un profil utilisateur via l'API]({{site.baseurl}}/help/help_articles/api/delete_user/) dans notre documentation d'aide.
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#22e91d00-d178-4b4f-a3df-0073ecfcc992 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `users.delete`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='users delete' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+  "external_ids" : (optional, array of string) External ids for the users to delete,
+  "user_aliases" : (optional, array of user alias objects) User aliases for the users to delete,
+  "braze_ids" : (optional, array of string) Braze user identifiers for the users to delete
+}
+```
+### Paramètres de demande
+
+| Paramètre      | Requis | Type de données                  | Description                                                                                      |
+| -------------- | -------- | -------------------------- | ------------------------------------------------------------------------------------------------ |
+| `external_ids` | Facultatif | Tableau de chaînes de caractères           | Identifiants externes pour les utilisateurs à supprimer.                                                    |
+| `user_aliases` | Facultatif | Tableau d’objets Alias utilisateur | [Alias utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object/) pour les utilisateurs à supprimer. |
+| `braze_ids`    | Facultatif | Tableau de chaînes de caractères           | Identifiants utilisateur de Braze pour les utilisateurs à supprimer.                                                  |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+### Suppression des utilisateurs par e-mail
+Si un `email` est spécifié comme identifiant, une valeur `prioritization` supplémentaire est requise dans l'identifiant. Le `prioritization` est un tableau ordonné et doit spécifier quel utilisateur supprimer si plusieurs utilisateurs sont trouvés. Cela signifie que la suppression des utilisateurs ne se produira pas si plus d'un utilisateur correspond à une priorisation.
+
+Les valeurs autorisées pour le tableau sont : `identified`, `unidentified`, `most_recently_updated`. `most_recently_updated` fait référence à la priorisation de l'utilisateur mis à jour le plus récemment.
+
+Une seule des options suivantes peut exister dans le tableau de priorisation à la fois :
+- `identified` fait référence à la priorisation d'un utilisateur avec un `external_id`
+- `unidentified` fait référence à la priorisation d'un utilisateur sans un `external_id`
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/delete' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+  "external_ids": ["external_identifier1", "external_identifier2"],
+  "braze_ids": ["braze_identifier1", "braze_identifier2"],
+  "user_aliases": [
+    {
+      "alias_name": "user_alias1", "alias_label": "alias_label1"
+    },
+    {
+      "alias_name": "user_alias2", "alias_label": "alias_label2"
+    }
+  ],
+  "email_addresses": [
+    {
+      "email": "john.smith@braze.com",
+      "prioritization": ["unidentified", "most_recently_updated"]
+    }
+  ]
+}'
+```
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+  "deleted" : (required, integer) number of user ids queued for deletion
+}
+```
+{% endapi %}
+
+
diff --git a/_lang/fr_fr/_api/endpoints/user_data/post_user_identify.md b/_lang/fr_fr/_api/endpoints/user_data/post_user_identify.md
new file mode 100644
index 00000000000..cd40e34840d
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data/post_user_identify.md
@@ -0,0 +1,158 @@
+---
+nav_title: "POST : Identifier les utilisateurs"
+article_title: "POST : Identifier les utilisateurs"
+search_tag: Endpoint
+page_order: 3
+layout: api_page
+page_type: reference
+alias: /users_identify_merge/
+description: "Cet article présente en détail l’endpoint Braze Identifier les utilisateurs."
+
+---
+{% api %}
+# Identifier les utilisateurs
+{% apimethod post %}
+/users/identify
+{% endapimethod %}
+
+> Utilisez cet endpoint pour identifier un utilisateur non identifié (alias uniquement). 
+
+{% alert important %}
+À compter du 7 août 2023, cet endpoint fusionnera les données de tous les appels. Cela signifie que [`merge_behavior`](#merge) sera réglé sur `merge` pour tous les appels.
+{% endalert %}
+
+Appeler `/users/identify` combine le profil alias uniquement avec le profil identifié, et supprime le profil alias uniquement.
+
+Identifier un utilisateur nécessite un `external_id` à inclure dans l’objet `aliases_to_identify`. Si aucun utilisateur ne porte cet `external_id`, l’`external_id` sera simplement ajouté au dossier de l’utilisateur alias, et l’utilisateur sera considéré comme identifié. Vous pouvez ajouter jusqu’à 50 alias utilisateur par demande.
+
+Ensuite, vous pouvez associer plusieurs alias d’utilisateur supplémentaires à un seul `external_id`. 
+- Lorsque ces associations ultérieures sont effectuées avec le champ `merge_behavior` défini sur `none`, seuls les jetons de notification push et l’historique des messages associés à l’alias d’utilisateur sont conservés. Tous les attributs, événements ou achats deviendront « orphelins » et non disponibles pour l’utilisateur identifié. Une solution consiste à exporter les données de l'utilisateur aliasé avant l'identification à l'aide de l' [endpoint`/users/export/ids` ]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/), puis à réassocier les attributs, les événements et les achats à l'utilisateur identifié.
+- Lorsque des associations sont faites avec le champ `merge_behavior` défini sur `merge`, cet endpoint fusionnera les [champs spécifiques](#merge) trouvés sur l'utilisateur anonyme avec ceux de l'utilisateur identifié.
+
+{% alert tip %}
+Pour éviter toute perte inattendue de données lors de l'identification des utilisateurs, nous vous recommandons vivement de vous reporter d'abord aux [meilleures pratiques en]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/best_practices/#capturing-user-data-when-alias-only-user-info-is-already-present) matière de [collecte de données]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/best_practices/#capturing-user-data-when-alias-only-user-info-is-already-present) pour savoir comment capturer les données des utilisateurs lorsque des informations sur les utilisateurs sous forme d'alias seulement sont déjà présentes.
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#5f74e0f7-0620-4c7b-b0a2-f5f38fdbff58 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `users.identify`.
+
+## Limite de débit 
+Une limite de débit est appliquée aux demandes faites au niveau de cet endpoint pour les clients qui ont rejoint Braze le 16 septembre 2021 ou plus tard. Pour plus d'informations, consultez [Limites de l'API]({{site.baseurl}}/api/basics/#api-limits).
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+   "aliases_to_identify" : (required, array of alias to identify objects), 
+   "merge_behavior": (optional, string) one of 'none' or 'merge' is expected
+}
+```
+
+### Paramètres de demande
+
+| Paramètre             | Requis | Type de données                           | Description                                                                                                                                                                 |
+| --------------------- | -------- | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `aliases_to_identify` | Requis | Tableau d’alias pour identifier l’objet | Voir [alias pour identifier l'objet]({{site.baseurl}}/api/objects_filters/aliases_to_identify/) et [alias d'utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object/). |
+| `merge_behavior`      | Facultatif | Chaîne de caractères                              | `none` ou `merge` est attendu.                                                                                                                                       |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+#### Champ Merge_behavior {#merge}
+
+Définir le champ `merge_behavior` sur `merge` paramètre l’endpoint pour fusionner tous les champs suivants trouvés **exclusivement** depuis l’utilisateur anonyme vers l’utilisateur identifié. 
+- Prénom
+- Nom
+- E-mail
+- Genre
+- Date de naissance
+- Numéro de téléphone
+- Fuseau horaire
+- Ville d’origine
+- Pays
+- Langue
+- Décompte des sessions (la somme des sessions des deux profils)
+- Date de la première session (Braze choisira la date la plus ancienne parmi les deux)
+- Date de la dernière session (Braze choisira la date la plus récente parmi les deux)
+- Attributs personnalisés
+- Données d'événements personnalisés et d'événements d'achat
+- Propriétés de l’événement d’achat et personnalisées pour la segmentation « X fois en Y jours » (où X <= 50 et Y <= 30)
+- Résumé des événements personnalisés pouvant être segmentés
+  - Nombre d’événements (la somme des deux profils)
+  - Événement survenu pour la première fois (Braze choisira la date la plus ancienne parmi les deux)
+  - Événement survenu pour la dernière fois (Braze choisira la date la plus récente parmi les deux)
+- Total des achats intégrés à l’application en centimes (la somme des deux profils)
+- Nombre total d’achats (la somme des deux profils)
+- Date du premier achat (Braze choisira la date la plus ancienne parmi les deux)
+- Date du dernier achat (Braze choisira la date la plus récente parmi les deux)
+- Résumés des applications
+- Champs Last_X_at (Braze mettra à jour les champs si les champs du profil orphelins sont plus récents).
+- Résumés de campagne (Braze choisira les champs de date les plus récents)
+- Résumés du flux de travail (Braze choisira les champs de date les plus récents)
+- Message et historique d’engagement du message
+
+L’un des champs suivants a été trouvé sur l’utilisateur anonyme ou l’utilisateur identifié :
+- Nombre d’événements d’achats et personnalisés, ainsi que les horodatages correspondant à la première et dernière dates 
+  - Ces champs fusionnés mettront à jour les filtres « pour X événements en Y jours ». Pour les événements d’achat, ces filtres incluent « nombre d’achats en Y jours » et « argent dépensé au cours des Y derniers jours ».
+
+Les données de session ne seront fusionnées que si l’application existe sur les deux profils utilisateurs. Par exemple, si votre utilisateur cible ne dispose pas d’un résumé d’application pour « ABCApp », mais que votre utilisateur d’origine l’a, l’utilisateur cible disposera du résumé d’application pour « ABCApp » sur son profil après la fusion. 
+
+Configurer le champ sur `none` ne fusionnera aucune donnée utilisateur avec le profil utilisateur identifié.
+
+### Identifier les utilisateurs par e-mail
+Si un `email` est spécifié comme identifiant, une valeur `prioritization` supplémentaire est requise dans l'identifiant. `prioritization` doit être un tableau spécifiant l'utilisateur à fusionner si plusieurs utilisateurs ont été trouvés. `prioritization` est un tableau ordonné, ce qui signifie que si plus d'un utilisateur correspond à un ordre de priorité, la fusion n'aura pas lieu.
+
+Les valeurs autorisées pour le tableau sont les suivantes : `identified`, `unidentified`, `most_recently_updated`. `most_recently_updated` signifie que la priorité est accordée à l'utilisateur ayant effectué la dernière mise à jour.
+
+Une seule des options suivantes peut exister à la fois dans le tableau de priorisation :
+- `identified` Il s'agit de donner la priorité à un utilisateur ayant une `external_id`
+- `unidentified` Il s'agit de donner la priorité à un utilisateur qui n'a pas de `external_id`
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/identify' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+  "aliases_to_identify": [
+    {
+      "external_id": "external_identifier",
+      "user_alias": {
+          "alias_name": "example_alias",
+          "alias_label": "example_label"
+      }
+    }
+  ],
+  "emails_to_identify": [
+    {
+      "external_id": "external_identifier_2",
+      "email": "john.smith@braze.com",
+      "prioritization": ["unidentified", "most_recently_updated"]
+    }
+  ]
+  "merge_behavior": "merge"
+}'
+```
+
+{% alert tip %}
+Pour plus d'informations sur `alias_name` et `alias_label`, consultez notre documentation sur les [alias utilisateurs.]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases) 
+{% endalert %}
+
+## Réponse
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+    "aliases_processed": 1,
+    "message": "success"
+}
+```
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/user_data/post_user_track.md b/_lang/fr_fr/_api/endpoints/user_data/post_user_track.md
new file mode 100644
index 00000000000..d3bdafe8203
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data/post_user_track.md
@@ -0,0 +1,297 @@
+---
+nav_title: "POST : Suivre les utilisateurs"
+article_title: "POST : Suivre les utilisateurs"
+search_tag: Endpoint
+page_order: 4
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Suivi utilisateur."
+
+---
+{% api %}
+# Suivi utilisateur
+{% apimethod post core_endpoint|https://www.braze.com/docs/core_endpoints %}
+/users/track
+{% endapimethod %}
+
+> Utilisez cet endpoint pour enregistrer les événements et les achats personnalisés et mettre à jour les attributs du profil utilisateur.
+
+{% alert note %}
+Braze traite les données transmises via l'API à leur valeur nominale, et les clients ne doivent transmettre que des deltas (données changeantes) afin de minimiser la consommation inutile de points de données. Pour en savoir plus, consultez la rubrique [Points de données]({{site.baseurl}}/user_guide/data_and_analytics/data_points/).
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#4cf57ea9-9b37-4e99-a02e-4373c9a4ee59 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `users.track`.
+
+Les clients utilisant l'API pour les appels de serveur à serveur devront peut-être inscrire `rest.iad-01.braze.com` dans la liste des autorisations s'ils sont derrière un pare-feu.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='users track' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+  "attributes": (optional, array of attributes object),
+  "events": (optional, array of event object),
+  "purchases": (optional, array of purchase object),
+}
+```
+
+### Paramètres de demande
+
+{% alert important %}
+Pour chaque composant de requête répertorié dans le tableau suivant, l'un des éléments suivants est requis : `external_id`, `user_alias`, `braze_id`, `email` ou `phone`.
+{% endalert %}
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | ---------| --------- | ----------- |
+| `attributes` | Facultatif | Tableau d’objets Attributs | Voir [objet attributs de l'utilisateur]({{site.baseurl}}/api/objects_filters/user_attributes_object/) |
+| `events` | Facultatif | Tableau d’objets Événement | Voir l'[objet "événements"]({{site.baseurl}}/api/objects_filters/event_object/). |
+| `purchases` | Facultatif | Tableau d’objets Achat | Voir les [achats d'objets]({{site.baseurl}}/api/objects_filters/purchase_object/) |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+## Exemple de requêtes
+
+### Mise à jour d'un profil utilisateur par adresse e-mail
+
+Vous pouvez mettre à jour un profil utilisateur par adresse e-mail en utilisant l'endpoint `/users/track`. 
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+    "attributes": [
+        {
+            "email": "test@braze.com",
+            "string_attribute": "fruit",
+            "boolean_attribute_1": true,
+            "integer_attribute": 25,
+            "array_attribute": [
+                "banana",
+                "apple"
+            ]
+        }
+    ],
+    "events": [
+        {
+            "email": "test@braze.com",
+            "app_id": "your_app_identifier",
+            "name": "rented_movie",
+            "time": "2022-12-06T19:20:45+01:00",
+            "properties": {
+                "release": {
+                    "studio": "FilmStudio",
+                    "year": "2022"
+                },
+                "cast": [
+                    {
+                        "name": "Actor1"
+                    },
+                    {
+                        "name": "Actor2"
+                    }
+                ]
+            }
+        },
+        {
+            "user_alias": {
+                "alias_name": "device123",
+                "alias_label": "my_device_identifier"
+            },
+            "app_id": "your_app_identifier",
+            "name": "rented_movie",
+            "time": "2013-07-16T19:20:50+01:00"
+        }
+    ],
+    "purchases": [
+        {
+            "email": "test@braze.com",
+            "app_id": "your_app_identifier",
+            "product_id": "product_name",
+            "currency": "USD",
+            "price": 12.12,
+            "quantity": 6,
+            "time": "2017-05-12T18:47:12Z",
+            "properties": {
+                "color": "red",
+                "monogram": "ABC",
+                "checkout_duration": 180,
+                "size": "Large",
+                "brand": "Backpack Locker"
+            }
+        }
+    ]
+}'
+```
+
+### Mise à jour d'un profil utilisateur par numéro de téléphone
+
+Vous pouvez mettre à jour un profil utilisateur par numéro de téléphone en utilisant l’endpoint `/users/track`. Cet endpoint ne fonctionne que si vous indiquez un numéro de téléphone valide.
+
+{% alert important %}
+Si vous incluez une demande avec à la fois un e-mail et un téléphone, Braze utilisera l'e-mail comme identifiant.
+{% endalert %}
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+    "attributes": [
+        {
+            "phone": "+15043277269",
+            "string_attribute": "fruit",
+            "boolean_attribute_1": true,
+            "integer_attribute": 25,
+            "array_attribute": [
+                "banana",
+                "apple"
+            ]
+        }
+    ],
+}'
+```
+### Définir les groupes d'abonnement
+
+Cet exemple montre comment créer un utilisateur et définir son groupe d'abonnement dans l'objet attributs de l'utilisateur. 
+
+La mise à jour de l'état de l'abonnement avec cet endpoint mettra à jour l'utilisateur spécifié par son `external_id` (par exemple User1) et mettra à jour l'état de l'abonnement de tous les utilisateurs ayant le même e-mail que cet utilisateur (User1).
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+  "attributes": [
+  {
+    "external_id": "user_identifier",
+    "email": "example@email.com",
+    "email_subscribe": "subscribed",
+    "subscription_groups": [{
+      "subscription_group_id": "subscription_group_identifier_1",
+      "subscription_state": "unsubscribed"
+      },
+      {
+        "subscription_group_id": "subscription_group_identifier_2",
+        "subscription_state": "subscribed"
+        },
+        {
+          "subscription_group_id": "subscription_group_identifier_3",
+          "subscription_state": "subscribed"
+        }
+      ]
+    }
+  ]
+}'
+```
+
+### Exemple de requête pour créer un utilisateur alias uniquement.
+
+Vous pouvez utiliser l’endpoint `/users/track` pour créer un nouvel utilisateur alias uniquement en définissant la clé `_update_existing_only` avec une valeur `false` dans le corps de la requête. Si cette valeur est omise, le profil utilisateur alias uniquement ne sera pas créé. Un utilisateur alias uniquement permet de s’assurer qu’un seul profil avec cet alias existe. C’est notamment utile lorsque vous construisez une nouvelle intégration, car cela empêche la création de doublons de profil utilisateur
+
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+{
+    "attributes": [
+        {
+            "_update_existing_only": false,
+            "user_alias": {
+                "alias_name": "example_name",
+                "alias_label": "example_label"
+            },
+            "email": "email@example.com"
+        }
+    ],
+}'
+```
+
+
+## Réponses
+
+Lorsque vous utilisez l'une des requêtes API susmentionnées, vous devriez recevoir l'une des trois réponses générales suivantes : un [message de réussite](#successful-message), un [message de réussite avec des erreurs non fatales](#successful-message-with-non-fatal-errors) ou un [message avec des erreurs fatales](#message-with-fatal-errors).
+
+### Message réussi
+
+Les messages réussis seront envoyés avec la réponse suivante :
+
+```json
+{
+  "message": "success",
+  "attributes_processed": (optional, integer), if attributes are included in the request, this will return an integer of the number of external_ids with attributes that were queued to be processed,
+  "events_processed": (optional, integer), if events are included in the request, this will return an integer of the number of events that were queued to be processed,
+  "purchases_processed": (optional, integer), if purchases are included in the request, this will return an integer of the number of purchases that were queued to be processed,
+}
+```
+
+### Message réussi sans erreurs fatales
+
+Si votre message est réussi, mais qu’il y a des erreurs non fatales, comme un objet Événement non valide hors d’une longue liste d’événements, vous recevrez la réponse suivante :
+
+```json
+{
+  "message": "success",
+  "errors": [
+    {
+      <minor error message>
+    }
+  ]
+}
+```
+
+Pour les messages de réussite, toutes les données non affectées par une erreur dans le tableau `errors` continueront d’être traitées. 
+
+### Message avec erreurs fatales
+
+Si votre message contient une erreur fatale, vous recevrez la réponse suivante :
+
+```json
+{
+  "message": <fatal error message>,
+  "errors": [
+    {
+      <fatal error message>
+    }
+  ]
+}
+```
+
+### Codes de réponse des erreurs fatales
+
+Pour connaître les codes d'état et les messages d'erreur associés qui seront renvoyés si votre demande rencontre une erreur fatale, reportez-vous à la section [Erreurs fatales et réponses.]({{site.baseurl}}/api/errors/#fatal-errors)
+
+Si vous recevez le message d'erreur "provided external_id is blacklistted and disallowed", il se peut que votre demande contienne un "utilisateur fictif". Pour plus d'informations, reportez-vous à la section [Blocage des spams.]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_archival/#spam-blocking) 
+
+## Foire aux questions
+
+{% multi_lang_include email-via-sms-warning.md %}
+
+### Que se passe-t-il lorsque plusieurs profils avec la même adresse e-mail sont trouvés ?
+Si l’`external_id` existe, le profil le plus récemment mis à jour avec un ID externe sera utilisé en priorité pour les mises à jour. Si l’`external_id` n’existe pas, le profil le plus récemment mis à jour sera utilisé en priorité pour les mises à jour.
+
+### Que se passe-t-il si aucun profil avec l’adresse e-mail n’existe actuellement ?
+Un nouveau profil sera créé, ainsi qu'un utilisateur exclusivement par e-mail. Aucun alias ne sera créé. Le champ e-mail sera défini sur test@braze.com, comme indiqué dans l'exemple de demande de mise à jour d'un profil utilisateur par l'adresse e-mail.
+
+### Comment utiliser `/users/track` pour importer des données utilisateur héritées ?
+Vous pouvez soumettre des données via l'API de Braze pour un utilisateur qui n'a pas encore utilisé votre application mobile afin de générer un profil utilisateur. Si l’utilisateur se sert ultérieurement de l’application, toutes les informations qui suivent son identification via le SDK seront fusionnées avec le profil utilisateur existant que vous avez créé via l’appel d’API. Tout comportement de l'utilisateur enregistré de manière anonyme par le SDK avant l'identification sera perdu lors de la fusion avec le profil utilisateur existant généré par l'API.
+
+L’outil de segmentation inclura ces utilisateurs, qu’ils aient utilisé l’application ou pas. Si vous souhaitez exclure les utilisateurs téléchargés via l'API utilisateur qui n'ont pas encore utilisé l'application, ajoutez le filtre `Session Count > 0`.
+
+### Comment `/users/track` gère-t-il les événements en double ?
+
+Chaque objet d'événement du tableau d'objets représente une occurrence unique d'un événement personnalisé par un utilisateur à un moment donné. Cela signifie que chaque événement intégré dans Braze possède son propre ID, de sorte que les événements "dupliqués" sont traités comme des événements distincts et uniques.
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/endpoints/user_data/post_users_alias_update.md b/_lang/fr_fr/_api/endpoints/user_data/post_users_alias_update.md
new file mode 100644
index 00000000000..a5c620504cd
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data/post_users_alias_update.md
@@ -0,0 +1,83 @@
+---
+nav_title: "POST : Mise à jour de l'alias d'utilisateur"
+article_title: "POST : Mise à jour de l'alias d'utilisateur"
+search_tag: Endpoint
+page_order: 2
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Mettre à jour les alias utilisateur."
+---
+{% api %}
+# Mettre à jour l’alias d’utilisateur
+{% apimethod post %}
+/users/alias/update
+{% endapimethod %}
+
+> Utilisez cet endpoint pour mettre à jour les alias utilisateur existants.
+
+Vous pouvez spécifier jusqu’à 50 alias de l’utilisateur par requête.
+
+Mettre à jour d’un alias d’utilisateur nécessite que `alias_label`, `old_alias_name` et `new_alias_name` soient compris dans l’objet de mise à jour d’alias d’utilisateur. Si aucun alias d’utilisateur n’est associé au `alias_label` ni au `old_alias_name`, aucun alias ne sera mis à jour. Si le `alias_label` et le `old_alias_name` sont trouvés, le `old_alias_name` sera mis à jour vers le `new_alias_name`.
+
+{% alert note %}
+Cet endpoint ne garantit pas que la séquence des objets `alias_updates` soit mise à jour.
+{% endalert %}
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#a084b843-b3cd-43f0-bfb1-ef7bada839c5 {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `users.alias.update`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='users alias update' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+  "alias_updates" : (required, array of update user alias object)
+}
+```
+
+### Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+| --------- | --------- | --------- | ----------- |
+| `alias_updates` | Requis | Tableau des objets alias utilisateur mis à jour | Voir l'[objet alias d'utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object/).<br><br> Pour plus d'informations sur `old_alias_name`, `new_alias_name`, et `alias_label`, reportez-vous à la section [Alias de l'utilisateur]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+### Corps de demande d’endpoint avec spécification de l’objet de mise à jour d’alias utilisateur
+
+```json
+{
+  "alias_label" : (required, string),
+  "old_alias_name" : (required, string),
+  "new_alias_name" : (required, string)
+}
+```
+
+## Exemple de demande
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/alias/update' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+  "alias_updates" :[
+    {
+      "alias_label": "example_alias_label",
+      "old_alias_name" : "example_old_alias_name",
+      "new_alias_name" : "example_new_alias_name"
+    }
+  ]
+}'
+```
+
+{% endapi %}
+
diff --git a/_lang/fr_fr/_api/endpoints/user_data/post_users_merge.md b/_lang/fr_fr/_api/endpoints/user_data/post_users_merge.md
new file mode 100644
index 00000000000..d0627746c54
--- /dev/null
+++ b/_lang/fr_fr/_api/endpoints/user_data/post_users_merge.md
@@ -0,0 +1,270 @@
+---
+nav_title: "POST : Fusionner les utilisateurs"
+article_title: "POST : Fusionner les utilisateurs"
+search_tag: Endpoint
+page_order: 6
+layout: api_page
+page_type: reference
+description: "Cet article présente en détail l’endpoint Braze Fusion d’utilisateurs."
+
+---
+{% api %}
+# Fusionner les utilisateurs
+{% apimethod post %}
+/users/merge
+{% endapimethod %}
+
+> Utilisez cet endpoint pour fusionner un utilisateur avec un autre utilisateur. 
+
+Vous pouvez spécifier jusqu’à 50 fusions par requête. Cet endpoint est asynchrone.
+
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#d262b86d-cf84-46e2-b9d0-f882bb7078de {% endapiref %}
+
+## Conditions préalables
+
+Pour utiliser cet endpoint, vous aurez besoin d'une [clé API]({{site.baseurl}}/api/api_key/) avec l’autorisation `users.merge`.
+
+## Limite de débit
+
+{% multi_lang_include rate_limits.md endpoint='users merge' %}
+
+## Corps de la demande
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+```
+
+```json
+{
+  "merge_updates" : (required, array of objects)
+}
+```
+
+## Paramètres de demande
+
+| Paramètre | Requis | Type de données | Description |
+|---|---|---|---|
+| `merge_updates` | Requis | Tableau | Un tableau d’objets. Chaque objet doit contenir un objet `identifier_to_merge` et un objet `identifier_to_keep`, qui doivent chacun référencer un utilisateur par `external_id`, `user_alias`, `phone_number` ou `email`. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+### Comportement de fusion
+
+Le comportement documenté ci-dessous est vrai pour toutes les fonctionnalités de Braze qui *ne sont pas* optimisées par Snowflake. Les fusions d'utilisateurs ne seront pas prises en compte pour l'onglet **Historique des messages**, les extensions de segments, le générateur de requêtes et les actualités.
+
+{% alert important %}
+Cet endpoint ne garantit pas que la séquence des objets `merge_updates` soit mise à jour.
+{% endalert %}
+
+Cet endpoint fusionnera n'importe lequel des champs suivants s'ils ne sont pas trouvés dans l'utilisateur cible :
+
+- Prénom
+- Nom
+- E-mail
+- Genre
+- Date de naissance
+- Numéro de téléphone
+- Fuseau horaire
+- Ville d’origine
+- Pays
+- Langue
+- Informations sur l’appareil
+- Décompte des sessions (la somme des sessions des deux profils)
+- Date de la première session (Braze choisira la date la plus ancienne parmi les deux)
+- Date de la dernière session (Braze choisira la date la plus récente parmi les deux)
+- Attributs personnalisés (les attributs personnalisés existants sur le profil cible sont conservés et incluront les attributs personnalisés qui n'existaient pas sur le profil cible).
+- Données d'événements personnalisés et d'événements d'achat
+- Propriétés de l’événement d’achat et personnalisées pour la segmentation « X fois en Y jours » (où X <= 50 et Y <= 30)
+- Résumé des événements personnalisés pouvant être segmentés
+  - Nombre d’événements (la somme des deux profils)
+  - Événement survenu pour la première fois (Braze choisira la date la plus ancienne parmi les deux)
+  - Événement survenu pour la dernière fois (Braze choisira la date la plus récente parmi les deux)
+- Total des achats intégrés à l’application en centimes (la somme des deux profils)
+- Nombre total d’achats (la somme des deux profils)
+- Date du premier achat (Braze choisira la date la plus ancienne parmi les deux)
+- Date du dernier achat (Braze choisira la date la plus récente parmi les deux)
+- Résumés des applications
+- Champs Last_X_at (Braze mettra à jour les champs si les champs du profil orphelins sont plus récents).
+- Données d'interaction de la campagne (Braze choisira les champs de date les plus récents)
+- Résumés du flux de travail (Braze choisira les champs de date les plus récents)
+- Message et historique d’engagement du message
+
+Les données de session ne seront fusionnées que si l’application existe sur les deux profils utilisateurs.
+
+{% alert note %}
+Lors de la fusion d'utilisateurs, l'utilisation de l'endpoint `/users/merge` fonctionne de la même manière que la [méthode`changeUser()` ](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#changeuser).
+{% endalert %}
+
+#### Comportement personnalisé de la date de l'événement et de la date de l'événement d'achat
+
+Ces champs fusionnés mettront à jour les filtres « pour X événements en Y jours ». Pour les événements d’achat, ces filtres incluent « nombre d’achats en Y jours » et « argent dépensé au cours des Y derniers jours ».
+
+### Fusionner les utilisateurs par e-mail ou par numéro de téléphone
+
+Si un identifiant `email` ou `phone_number` est spécifié, une valeur supplémentaire `prioritization` est requise dans l'identifiant. `prioritization` doit être un tableau spécifiant l'utilisateur à fusionner s'il y a plusieurs utilisateurs trouvés. `prioritization` est un tableau ordonné, ce qui signifie que si plus d'un utilisateur correspond à un ordre de priorité, la fusion n'aura pas lieu.
+
+Les valeurs autorisées pour le tableau sont les suivantes : `identified`, `unidentified`, `most_recently_updated`. `most_recently_updated` signifie que la priorité est accordée à l'utilisateur ayant effectué la dernière mise à jour.
+
+Une seule des options suivantes peut exister à la fois dans le tableau de priorisation :
+- `identified` Il s'agit de donner la priorité à un utilisateur ayant une `external_id`
+- `unidentified` Il s'agit de donner la priorité à un utilisateur qui n'a pas de `external_id`
+
+## Exemple de requêtes
+
+### Demande de base
+
+Il s'agit d'un corps de requête basique pour montrer le modèle de la requête.
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/users/merge' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+{
+  "merge_updates": [
+    {
+      "identifier_to_merge": {
+        "external_id": "old-user1"
+      },
+      "identifier_to_keep": {
+        "external_id": "current-user1"
+      }
+    },
+    {
+      "identifier_to_merge": {
+        "email": "user1@braze.com",
+        "prioritization": ["unidentified", "most_recently_updated"]
+      },
+      "identifier_to_keep":  {
+        "email": "user2@braze.com",
+        "prioritization": ["identified", "most_recently_updated"]
+      }
+    },
+    {
+      "identifier_to_merge": {
+        "user_alias": {
+          "alias_name": "old-user2@example.com",
+          "alias_label": "email"
+        }
+      },
+      "identifier_to_keep": {
+        "user_alias": {
+          "alias_name": "current-user2@example.com",
+          "alias_label": "email"
+        }
+      }
+    }
+  ]
+}'
+```
+
+### Fusionner des utilisateurs non identifiés
+
+`external_id` La demande suivante fusionnerait l'utilisateur non identifié dont l'adresse e-mail est "john.smith@braze.com" avec l'utilisateur dont l'adresse e-mail est " john ". L'utilisation de `most_recently_updated` permet de filtrer la requête pour afficher un seul utilisateur non identifié. Ainsi, s'il y avait deux utilisateurs non identifiés avec cette adresse e-mail, un seul serait fusionné dans l'utilisateur avec `external_id` "john".
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/users/merge' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+{
+  "merge_updates": [
+    {
+      "identifier_to_merge": {
+        "email": "john.smith@braze.com",
+        "prioritization": ["unidentified", "most_recently_updated"]
+      },
+      "identifier_to_keep": {
+        "external_id": "john"
+      }
+    }
+  ]
+}'
+```
+
+### Fusionner un utilisateur non identifié avec un utilisateur identifié
+
+L'exemple suivant fusionne l'utilisateur non identifié dont l'adresse e-mail est "john.smith@braze.com" avec l'utilisateur identifié dont l'adresse e-mail est "john.smith@braze.com". L'utilisation de `most_recently_updated` filtre les requêtes pour afficher un seul utilisateur (un utilisateur non identifié pour `identifier_to_merge` et un utilisateur identifié pour `identifier_to_keep`).
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/users/merge' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+{
+  "merge_updates": [
+    {
+      "identifier_to_merge": {
+        "email": "john.smith@braze.com",
+        "prioritization": ["unidentified", "most_recently_updated"]
+      },
+      "identifier_to_keep": {
+        "email": "john.smith@braze.com",
+        "prioritization": ["identified", "most_recently_updated"]
+      }
+    }
+  ]
+}'
+```
+
+### Fusionner un utilisateur non identifié sans inclure la priorisation most_recently_updated
+
+S'il y a deux utilisateurs non identifiés avec l'adresse e-mail "john.smith@braze.com", cet exemple de demande ne fusionne aucun utilisateur puisqu'il y a deux utilisateurs non identifiés avec cette adresse e-mail. Cette demande ne fonctionne que s'il n'y a qu'un seul utilisateur non identifié dont l'adresse e-mail est "john.smith@braze.com".
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/users/merge' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR_REST_API_KEY' \
+--data-raw '{
+{
+  "merge_updates": [
+    {
+      "identifier_to_merge": {
+        "email": "john.smith@braze.com",
+        "prioritization": ["unidentified"]
+      },
+      "identifier_to_keep": {
+        "external_id": "john"
+      }
+    }
+  ]
+}'
+```
+
+## Réponse
+
+Deux réponses de code de statut existent pour cet endpoint : `202` et `400`.
+
+### Exemple de réponse réussie
+
+Le code de statut `202` pourrait renvoyer le corps de réponse suivant.
+
+```json
+{
+  "message": "success"
+}
+```
+
+### Exemple de réponse échouée
+
+Le code de statut `400` pourrait renvoyer le corps de réponse suivant. Consultez la résolution des problèmes[](#troubleshooting) pour plus d’informations concernant les erreurs que vous pourriez rencontrer.
+
+```json
+{
+  "message": "'merge_updates' must be an array of objects"
+}
+```
+
+## Résolution des problèmes
+
+Le tableau suivant répertorie les messages d’erreur possibles.
+
+| Erreur | Résolution des problèmes |
+| --- |
+| `'merge_updates' must be an array of objects` | Vérifiez que `merge_updates` est un tableau d'objets. |
+| `a single request may not contain more than 50 merge updates` | Vous pouvez spécifier jusqu’à 50 fusions dans une seule requête. |
+| `identifiers must be objects with an 'external_id' property that is a string, 'user_alias' property that is an object, or 'email' property that is a string` | Vérifiez les identifiants dans votre requête. |
+| `'merge_updates' must only have 'identifier_to_merge' and 'identifier_to_keep'` | Vérifiez que `merge_updates` ne contient que les deux objets `identifier_to_merge` et `identifier_to_keep`. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endapi %}
diff --git a/_lang/fr_fr/_api/errors.md b/_lang/fr_fr/_api/errors.md
new file mode 100644
index 00000000000..11115c96403
--- /dev/null
+++ b/_lang/fr_fr/_api/errors.md
@@ -0,0 +1,99 @@
+---
+nav_title: Erreurs et réponses
+article_title: Erreurs et réponses d’API
+description: "Cet article de référence couvre les diverses erreurs et réponses du serveur qui peuvent apparaître lors de l’utilisation de l’API Braze et la façon de les résoudre." 
+page_type: reference
+page_order: 2.3
+
+---
+# Erreurs et réponses d’API
+
+> Cet article de référence couvre les diverses erreurs et réponses du serveur qui peuvent apparaître lors de l’utilisation de l’API Braze et la façon de les résoudre. 
+
+{% raw %}
+
+## Réponses du serveur
+
+Si votre charge utile POST a été acceptée par nos serveurs, les messages réussis seront reçus avec la réponse suivante :
+
+```json
+{
+  "message" : "success"
+}
+```
+
+Notez que la réussite signifie que la charge utile de l’API RESTful a été correctement créée et transmise à notre notification push ou à nos e-mails ou autres services de messagerie. Cela ne signifie pas que les messages ont effectivement été envoyés, car des facteurs supplémentaires peuvent empêcher l'envoi du message (par exemple, un appareil peut être hors ligne, le jeton push peut être rejeté par les serveurs d'Apple, vous pouvez avoir fourni un ID utilisateur inconnu).
+
+Si votre message est réussi, mais que vous avez des erreurs non fatales, vous recevrez la réponse suivante :
+
+```json
+{
+  "message" : "success", "errors" : [<minor error message>]
+}
+```
+
+Dans le cas d’un succès, tout message n’ayant pas été affecté par une erreur du tableau `errors` sera toujours livré. Si votre message contient une erreur fatale, vous recevrez la réponse suivante :
+
+```json
+{
+  "message" : <fatal error message>, "errors" : [<minor error message>]
+}
+```
+
+## Réponses pour les ID d’envoi suivis
+
+Les analyses sont toujours disponibles pour les campagnes. De plus, les analyses sont disponibles pour une instance spécifique de campagne lorsque celle-ci est envoyée en tant que diffusion. Lorsque le suivi est disponible pour une instance spécifique de campagne, vous recevrez la réponse suivante :
+
+```json
+{
+  "message": "success", "send_id" : "example_send_id"
+}
+```
+
+L'ID d'envoi fourni peut être utilisé comme paramètre pour l'endpoint `/send/data_series` afin d'obtenir des analyses/analytiques spécifiques à l'envoi.
+
+## Erreurs
+
+L’élément du code d’état d’une réponse serveur est un numéro à 3 chiffres où le premier chiffre du code définit la classe de réponse.
+
+- Le code d'état de **classe 2XX** (non fatal) indique que **votre demande** a été reçue, comprise et acceptée avec succès.
+- La **classe 4XX** du code de statut (fatal) indique une **erreur du client**. Reportez-vous au tableau des erreurs fatales pour obtenir une liste complète des codes d’erreur et descriptions de la classe 4XX.
+- La **classe 5XX** du code de statut (fatal) indique une **erreur du serveur**. Il y a plusieurs causes possibles, par exemple, le serveur auquel vous essayez d'accéder n'est pas en mesure d'exécuter la requête, le serveur fait l'objet d'une maintenance qui l'empêche d'exécuter la requête, ou le serveur connaît des niveaux élevés de trafic. Dans ce cas, nous vous recommandons de réessayer votre demande avec un délai exponentiel. En cas d'incident ou de panne, Braze n'est pas en mesure de lire à nouveau un appel d’API REST qui a échoué pendant la fenêtre d'incident. Vous devrez réessayer les appels qui ont échoué pendant la fenêtre d'incident.
+
+### Erreurs fatales
+
+Les codes d’état suivants et les messages d’erreur associés seront renvoyés si votre demande rencontre une erreur fatale.
+
+{% endraw %}
+{% alert warning %}
+Tous les codes d’erreur suivants indiquent qu’aucun message ne sera envoyé.
+{% endalert %}
+{% raw %}
+
+| Code d’erreur | Description |
+|---|---|
+| `5XX Internal Server Error` | Réessayer votre demande avec des délais exponentiels.|
+| `400 Bad Request` | Syntaxe incorrecte.|
+| `400 No Recipients` | Il n'y a pas d'ID externe ou d'ID de segmentation, ni de jetons de poussée dans la demande.|
+| `400 Invalid Campaign ID` | Aucune campagne API d'envoi de messages n'a été trouvée pour l'ID de campagne que vous avez fourni.|
+| `400 Message Variant Unspecified` | Vous fournissez un ID de campagne mais aucun ID de variation de message.|
+| `400 Invalid Message Variant` | Vous avez fourni un ID de campagne valide, mais l’ID de modification de message ne correspond pas à l’un des messages de cette campagne.|
+| `400 Mismatched Message Type` | Vous avez fourni une variation de message du mauvais type de message pour au moins un de vos messages.|
+| `400 Invalid Extra Push Payload` | Vous fournissez la clé `extra` pour `apple_push` ou `android_push` mais ce n’est pas un dictionnaire.|
+| `400 Max Input Length Exceeded` | Causé par l'appel de plus de 75 ID externes lors de l'atteinte de l'endpoint `/users/track`.|
+| `400 The max number of external_ids and aliases per request was exceeded` | Causé par l'appel de plus de 50 ID externes.|
+| `400 The max number of ids per request was exceeded` | Causé par l'appel de plus de 50 ID externes.|
+| `400 No message to send` | Aucune charge utile n’est spécifiée pour le message.|
+| `400 Slideup Message Length Exceeded` | Le message Slideup contient plus de 140 caractères.|
+| `400 Apple Push Length Exceeded` | La charge utile JSON est supérieure à 1 912 octets.|
+| `400 Android Push Length Exceeded` | La charge utile JSON est supérieure à 4 000 octets.|
+| `400 Bad Request` | Impossible d’analyser l’horodatage `send_at`.|
+| `400 Bad Request` | Dans votre demande, `in_local_time` est vrai, mais `time` est passé dans le fuseau horaire de votre entreprise.|
+| `401 Unauthorized` | Clé API non valide |
+| `403 Forbidden` | Le plan tarifaire n'est pas pris en charge ou le compte est désactivé.|
+| `403 Access Denied` | La clé API REST que vous utilisez ne dispose pas d'autorisations suffisantes, vérifiez les autorisations de la clé API sous la page **Paramètres.** |
+| `404 Not Found` | URL non valide. |
+| `429 Rate Limited` | Limite de débit dépassée. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% endraw %}
diff --git a/_lang/fr_fr/_api/home.md b/_lang/fr_fr/_api/home.md
new file mode 100644
index 00000000000..ff9a1551676
--- /dev/null
+++ b/_lang/fr_fr/_api/home.md
@@ -0,0 +1,467 @@
+---
+page_order: 0
+nav_title: Accueil
+article_title: Guide de l’API Braze
+layout: api_glossary
+glossary_top_header: "Braze API Guide"
+glossary_top_text: "Braze provides a high-performance REST API to allow you to track users, send messages, export data, and more. This page lists available Braze API endpoints and their uses."
+page_type: glossary
+description: "Cette page d’accueil répertorie les endpoints disponibles dans l’API Braze ainsi que leurs utilisations."
+glossary_tag_name: Endpoint Type
+
+glossary_filter_text: "Select endpoint type to narrow the glossary:"
+
+glossary_mid_text: "Endpoint Search"
+guide_featured_list:
+  - name: Overview API
+    image: /assets/img/braze_icons/annotation-info.svg
+    link: /docs/api/basics/
+  - name: Types d’identifiant API
+    link: /docs/api/identifier_types/
+    image: /assets/img/braze_icons/clipboard-check.svg
+  - name: Objets et filtres
+    link: /docs/api/objects_filters/
+    image: /assets/img/braze_icons/settings-01.svg
+  - name: Erreurs et réponses
+    link: /docs/api/errors/
+    image: /assets/img/braze_icons/list.svg
+  - name: Conservation des données
+    link: /docs/api/data_retention/
+    image: /assets/img/braze_icons/laptop-02.svg
+  - name: Limites de débit
+    link: /docs/api/api_limits/
+    image: /assets/img/braze_icons/hand.svg
+
+# channel to icon/fa or image mapping
+glossary_tags:
+  - name: Campagnes
+  - name: Canvas
+  - name: Catalogues
+  - name: Blocs de contenu
+  - name: Événements personnalisés
+  - name: Liste d’e-mails
+  - name: Modèles d’e-mail
+  - name: Indicateur clé de performance
+  - name: Fil d’actualité
+  - name: Achats
+  - name: Centre de préférences
+  - name: Planifier les messages
+  - name: SCIM
+  - name: Segments
+  - name: Envoyer les messages
+  - name: SMS
+  - name: Groupes d’abonnement
+  - name: Données utilisateur
+  - name: Activité en direct
+  - name: Ingestion de données cloud
+
+glossaries:
+  - name: "<a href='/docs/api/endpoints/user_data/post_user_alias/'>/users/alias/new</a>"
+    description: "Ajouter de nouveaux alias utilisateur pour les utilisateurs identifiés existants, ou pour créer de nouveaux utilisateurs non identifiés."
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/user_data/post_users_alias_update/'>/users/alias/update</a>"
+    description: Mettre à jour les noms d’alias d’utilisateur existants avec les nouveaux noms d’alias d’utilisateur.
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/user_data/post_user_delete/'>/users/delete</a>"
+    description: Supprimer un profil utilisateur en spécifiant un identifiant utilisateur connu.
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/export/user_data/post_users_global_control_group/'>/users/export/global_control_group</a>"
+    description: Exporter tous les utilisateurs d’un Groupe de contrôle global.
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/export/user_data/post_users_identifier/'>/users/export/ids</a>"
+    description: Exporter des données à partir de n’importe quel profil utilisateur en spécifiant un identifiant utilisateur.
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/export/user_data/post_users_segment/'>/users/export/segment</a>"
+    description: Exporter tous les utilisateurs d’un segment.
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/user_data/external_id_migration/post_external_ids_rename/'>/users/external_ids/rename</a>"
+    description: Renommer les ID externes de vos utilisateurs.
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/user_data/external_id_migration/post_external_ids_remove/'>/users/external_ids/remove</a>"
+    description: Supprimer les anciens ID externes obsolètes de vos utilisateurs.
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/user_data/post_user_identify/'>/users/identify</a>"
+    description: Identifier un utilisateur non identifié (alias uniquement).
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/user_data/post_user_track/'>/users/track</a>"
+    description: "Enregistrer des événements personnalisés, des achats et mettre à jour les attributs de profil utilisateur."
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/user_data/post_users_merge/'>/users/merge</a>"
+    description: Fusionner un profil utilisateur avec un autre.
+    tags:
+      - User Data
+  - name: "<a href='/docs/api/endpoints/messaging/send_messages/post_send_triggered_campaigns/'>/campaigns/trigger/send</a>"
+    description: "Envoyez des messages immédiats et ponctuels à des utilisateurs désignés grâce à la réception/distribution déclenchée par l'API. - Envoyer des messages"
+  - name: "<a href='/docs/api/endpoints/messaging/send_messages/post_send_triggered_canvases/'>/canvas/trigger/send</a>"
+    description: "Envoyez des messages canvas par le biais d'une réception/distribution déclenchée par l'API. - Envoyer des messages"
+  - name: "<a href='/docs/api/endpoints/messaging/send_messages/post_send_messages/'>/messages/send</a>"
+    description: "Envoyez des messages immédiats et ponctuels à des utilisateurs désignés via l'API de Braze."
+    tags:
+      - Send Messages
+  - name: "<a href='/docs/api/endpoints/messaging/send_messages/post_create_send_ids/'>/sends/id/create</a>"
+    description: Pour créer des ID d’envoi pouvant être utilisés pour envoyer des messages et suivre leur performance de manière programmatique sans créer une campagne pour chaque envoi.
+    tags:
+      - Send Messages
+  - name: "<a href='/docs/api/endpoints/messaging/send_messages/post_send_transactional_message/'>/transactional/v1/campaigns/{CAMPAIGN_ID}/send</a>"
+    description: Envoyez des messages transactionnels immédiats et ponctuels à un utilisateur désigné.
+    tags:
+      - Send Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/post_schedule_triggered_campaigns/'>/campaigns/trigger/schedule/create</a>"
+    description: "Envoyez des messages de campagne créés dans le tableau de bord par le biais d'une réception/distribution déclenchée par l'API."
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_messages/'>/campaigns/trigger/schedule/delete</a>"
+    description: Annuler des messages de campagne déclenchés par API que vous avez déjà planifiés avant qu’ils ne soient envoyés.
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_campaigns/'>/campaigns/trigger/schedule/update</a>"
+    description: Mettre à jour des campagnes déclenchées par API planifiées créées dans le tableau de bord.
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/post_delete_scheduled_triggered_canvases/'>/canvas/trigger/schedule/delete</a>"
+    description: Annuler un message Canvas que vous avez déjà planifié dans des campagnes déclenchées par API avant qu’il ne soit envoyé.
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/post_schedule_triggered_canvases/'>/canvas/trigger/schedule/create</a>"
+    description: "Planifiez les messages Canvas par le biais d'une réception/distribution déclenchée par l'API."
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/post_update_scheduled_messages/'>/messages/schedule/update</a>"
+    description: Mettre à jour les messages planifiés. Cet endpoint accepte les mises à jour vers le <code>schedule</code> ou <code>messages</code> paramètre ou les deux.
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/post_delete_scheduled_messages/'>/messages/schedule/delete</a>"
+    description: Annuler un message que vous avez déjà planifié avant qu’il ne soit envoyé.
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/post_schedule_messages/'>/messages/schedule/create</a>"
+    description: "Planifiez l'envoi d'une campagne, d'un canvas ou d'un autre message à un moment donné."
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/post_update_scheduled_triggered_canvases/'>/canvas/trigger/schedule/update</a>"
+    description: Mettre à jour des Canvas déclenchés par API planifiés qui ont été créés dans le tableau de bord.
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/schedule_messages/get_messages_scheduled/'>/messages/scheduled_broadcasts</a>"
+    description: Renvoyer une liste JSON d’informations sur les campagnes planifiées et les entrées Canvas entre maintenant et une date désignée <code>end_time</code> spécifié dans la demande.
+    tags:
+      - Schedule Messages
+  - name: "<a href='/docs/api/endpoints/messaging/live_activity/update/'>/messages/live_activity/update</a>"
+    description: Mettre à jour une activité iOS Live.
+    tags:
+      - Live Activity
+  - name: "<a href='/docs/api/endpoints/subscription_groups/post_update_user_subscription_group_status/'>/subscription/status/set</a>"
+    description: Mettre à jour des statuts d’abonnement par lots de 50 utilisateurs maximum sur le tableau de bord de Braze.
+    tags:
+      - Subscription Groups
+  - name: "<a href='/docs/api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2/'>/v2/subscription/status/set</a>"
+    description: Mettre à jour des statuts d’abonnement par lots de 50 utilisateurs maximum sur le tableau de bord de Braze.
+    tags:
+      - Subscription Groups
+  - name: "<a href='/docs/api/endpoints/subscription_groups/get_list_user_subscription_group_status/'>/subscription/status/get</a>"
+    description: Obtenir le statut d’abonnement d’un utilisateur dans un groupe d’abonnement.
+    tags:
+      - Subscription Groups
+  - name: "<a href='/docs/api/endpoints/subscription_groups/get_list_user_subscription_groups/'>/subscription/user/status</a>"
+    description: Répertorier et obtenir les groupes d’abonnement d’un certain utilisateur.
+    tags:
+      - Subscription Groups
+  - name: "<a href='/docs/api/endpoints/email/post_blacklist/'>/email/blacklist</a>"
+    description: Désinscrire un utilisateur des e-mails et le marquer comme rejeté définitivement.
+    tags:
+      - Email List
+  - name: "<a href='/docs/api/endpoints/email/post_remove_hard_bounces/'>/email/bounce/remove</a>"
+    description: Supprimer les adresses e-mail de votre liste de rejets Braze.
+    tags:
+      - Email List
+  - name: "<a href='/docs/api/endpoints/email/post_remove_spam/'>/email/spam/remove</a>"
+    description: Supprimer les adresses e-mail de votre liste de courriers indésirables de Braze.
+    tags:
+      - Email List
+  - name: "<a href='/docs/api/endpoints/email/post_email_subscription_status/'>/email/status</a>"
+    description: Définir l’état de l’abonnement aux e-mails de vos utilisateurs.
+    tags:
+      - Email List
+  - name: "<a href='/docs/api/endpoints/templates/email_templates/post_create_email_template/'>/templates/email/create</a>"
+    description: Créer des modèles d’e-mail sur le tableau de bord de Braze.
+    tags:
+      - Email Templates
+  - name: "<a href='/docs/api/endpoints/templates/email_templates/post_update_email_template/'>/templates/email/update</a>"
+    description: Mettre à jour des modèles d’e-mail sur le tableau de bord de Braze.
+    tags:
+      - Email Templates
+  - name: "<a href='/docs/api/endpoints/email/get_list_hard_bounces/'>/email/hard_bounces</a>"
+    description: "Extraire une liste d’adresses e-mail qui ont rejeté définitivement vos e-mails au cours d'une certaine période."
+    tags:
+      - Email List
+  - name: "<a href='/docs/api/endpoints/email/get_query_unsubscribed_email_addresses/'>/email/unsubscribes</a>"
+    description: Renvoie les adresses mail qui se sont désabonnées entre  <code>start_date</code> to <code>end_date</code>.
+    tags:
+      - Email List
+  - name: "<a href='/docs/api/endpoints/templates/email_templates/get_see_email_template_information/'>/templates/email/info</a>"
+    description: Obtenir des informations sur vos modèles d’e-mail.
+    tags:
+      - Email Templates
+  - name: "<a href='/docs/api/endpoints/templates/email_templates/get_list_email_templates/'>/templates/email/list</a>"
+    description: Obtenir une liste des e-mails disponibles sur votre compte Braze.
+    tags:
+      - Email Templates
+  - name: "<a href='/docs/api/endpoints/export/campaigns/get_campaign_analytics/'>/campaigns/data_series</a>"
+    description: Récupérer une série quotidienne de diverses statistiques pour une campagne au fil du temps.
+    tags:
+      - Campaigns
+  - name: "<a href='/docs/api/endpoints/export/campaigns/get_campaign_details/'>/campaigns/details</a>"
+    description: Récupérer des informations pertinentes d’une campagne donnée.
+    tags:
+      - Campaigns
+  - name: "<a href='/docs/api/endpoints/export/campaigns/get_campaigns/'>/campaigns/list</a>"
+    description: "Exporter une liste de campagnes, comportant pour chacune son nom, s’il s’agit d’une campagne par API, son identifiant API éventuel et les balises qui lui sont associées."
+    tags:
+      - Campaigns
+  - name: "<a href='/docs/api/endpoints/export/campaigns/get_send_analytics/'>/sends/data_series</a>"
+    description: Récupérer une série quotidienne de diverses statistiques pour un suivi. <code>send_id</code>.
+    tags:
+      - Campaigns
+  - name: "<a href='/docs/api/endpoints/export/canvas/get_canvas_analytics/'>/canvas/data_series</a>"
+    description: Exporter les données d’une série de dates pour un Canvas.
+    tags:
+      - Canvas
+  - name: "<a href='/docs/api/endpoints/export/canvas/get_canvas_analytics_summary/'>/canvas/data_summary</a>"
+    description: "Exporter des cumuls de données de série temporelles pour un Canvas, fournissant ainsi un résumé concis des résultats du Canvas."
+    tags:
+      - Canvas
+  - name: "<a href='/docs/api/endpoints/export/canvas/get_canvas_details/'>/canvas/details</a>"
+    description: "Exporter des métadonnées sur un Canvas, telles que le nom, l’heure de création, l’état actuel, etc."
+    tags:
+      - Canvas
+  - name: "<a href='/docs/api/endpoints/export/canvas/get_canvases/'>/canvas/list</a>"
+    description: "Exporter une liste de Canvas, y compris le nom, l’identifiant de l’API Canvas et les balises associées."
+    tags:
+      - Canvas
+  - name: "<a href='/docs/api/endpoints/export/segments/get_segment_analytics/'>/segments/data_series</a>"
+    description: Récupérer une série quotidienne de la taille estimée d’un segment au fil du temps.
+    tags:
+      - Segments
+  - name: "<a href='/docs/api/endpoints/export/segments/get_segment_details/'>/segments/details</a>"
+    description: Récupérer les informations pertinentes sur un segment.
+    tags:
+      - Segments
+  - name: "<a href='/docs/api/endpoints/export/segments/get_segment/'>/segments/list</a>"
+    description: "Exporter une liste de segments, chacun incluant son nom, l’identifiant API du segment et s’il a un suivi des analyses activé."
+    tags:
+      - Segments
+  - name: "<a href='/docs/api/endpoints/export/sessions/get_sessions_analytics/'>/sessions/data_series</a>"
+    description: Récupérer une série du nombre de sessions de votre application sur une période donnée.
+    tags:
+      - Sessions
+  - name: "<a href='/docs/api/endpoints/export/custom_attributes/get_custom_attributes/'>/custom_attributes</a>"
+    description: "Exportez une liste d'attributs personnalisés comprenant le nom, la description, le type de données, la longueur du tableau (le cas échéant), l'état et les tags associés."
+    tags:
+      - Custom Attributes
+  - name: "<a href='/docs/api/endpoints/export/custom_events/get_custom_events_analytics/'>/events/data_series</a>"
+    description: Récupérer une série du nombre d’occurrences d’un événement personnalisé dans votre application sur une période donnée.
+    tags:
+      - Custom Events
+  - name: "<a href='/docs/api/endpoints/export/custom_events/get_custom_events_data/'>/événements</a>"
+    description: "Exportez une liste d'événements personnalisés comprenant le nom, la description, l'état, les tags associés et l'inclusion dans le rapport d'analyse."
+    tags:
+      - Custom Events
+  - name: "<a href='/docs/api/endpoints/export/custom_events/get_custom_events/'>/events/list</a>"
+    description: "Exportez une liste de noms d'événements personnalisés qui ont été enregistrés pour votre appli."
+    tags:
+      - Custom Events
+  - name: "<a href='/docs/api/endpoints/templates/content_blocks_templates/post_create_email_content_block/'>/content_blocks/create</a>"
+    description: Créer un bloc de contenu d’e-mail.
+    tags:
+      - Content Blocks
+  - name: "<a href='/docs/api/endpoints/templates/content_blocks_templates/post_update_content_block/'>/content_blocks/update</a>"
+    description: Mettre à jour un bloc de contenu d’e-mail.
+    tags:
+      - Content Blocks
+  - name: "<a href='/docs/api/endpoints/templates/content_blocks_templates/get_see_email_content_blocks_information/'>/content_blocks/info</a>"
+    description: Appeler les informations de vos blocs de contenu d’e-mail existants.
+    tags:
+      - Content Blocks
+  - name: "<a href='/docs/api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks/'>/content_blocks/list</a>"
+    description: Répertorier les informations existantes de vos blocs de contenu.
+    tags:
+      - Content Blocks
+  - name: "<a href='/docs/api/endpoints/export/kpi/get_kpi_dau_date/'>/kpi/dau/data_series</a>"
+    description: Récupérer une série quotidienne du nombre total d’utilisateurs actifs uniques à chaque date.
+    tags:
+      - KPI
+  - name: "<a href='/docs/api/endpoints/export/kpi/get_kpi_mau_30_days/'>/kpi/mau/data_series</a>"
+    description: Récupérer une série quotidienne du nombre total d’utilisateurs actifs uniques sur une période de 30 jours glissants.
+    tags:
+      - KPI
+  - name: "<a href='/docs/api/endpoints/export/kpi/get_kpi_daily_new_users_date/'>/kpi/new_users/data_series</a>"
+    description: Récupérer une série quotidienne du nombre total de nouveaux utilisateurs à chaque date.
+    tags:
+      - KPI
+  - name: "<a href='/docs/api/endpoints/export/kpi/get_kpi_uninstalls_date/'>/kpi/uninstalls/data_series</a>"
+    description: Récupérer une série quotidienne du nombre total de désinstallations à chaque date.
+    tags:
+      - KPI
+  - name: "<a href='/docs/api/endpoints/export/news_feed/get_news_feed_card_analytics/'>/feed/data_series</a>"
+    description: Récupérer une série quotidienne de statistiques d’engagement pour une carte au fil du temps.
+    tags:
+      - News Feed
+  - name: "<a href='/docs/api/endpoints/export/news_feed/get_news_feed_card_details/'>/feed/details</a>"
+    description: Récupérer les informations pertinentes sur une carte.
+    tags:
+      - News Feed
+  - name: "<a href='/docs/api/endpoints/export/news_feed/get_news_feed_cards/'>/feed/list</a>"
+    description: "Exporter une liste de cartes de fil d’actualité, chacune incluant son nom et son identifiant API de carte."
+    tags:
+      - News Feed
+  - name: "<a href='/docs/api/endpoints/sms/post_remove_invalid_numbers/'>/sms/invalid_phone_numbers/remove</a>"
+    description: "Supprimez les numéros de téléphone \"non valides\" de la liste des numéros non valides dans Braze. Cela peut être utilisé pour revalider les numéros de téléphone après avoir été marqués comme non valides."
+    tags:
+      - SMS
+  - name: "<a href='/docs/api/endpoints/sms/get_query_invalid_numbers/'>/sms/invalid_phone_numbers</a>"
+    description: Extraire une liste des numéros de téléphone considérés comme « non valides » dans un certain délai.
+    tags:
+      - SMS
+  - name: "<a href='/docs/api/endpoints/export/purchases/get_list_product_id/'>/purchases/product_list</a>"
+    description: Retourner des listes paginées des ID de produits.
+    tags:
+      - Purchases
+  - name: "<a href='/docs/api/endpoints/export/purchases/get_number_of_purchases/'>/purchases/quantity_series</a>"
+    description: "Renvoyez le nombre total d'achats effectués dans votre application sur une période donnée."
+    tags:
+      - Purchases
+  - name: "<a href='/docs/api/endpoints/export/purchases/get_revenue_series/'>/purchases/revenue_series</a>"
+    description: Renvoyez le montant total dépensé dans votre application sur une période donnée.
+    tags:
+      - Purchases    
+  - name: "<a href='/docs/api/endpoints/preference_center/get_create_url_preference_center'>/preference_center/v1/{preferenceCenterExternalId}/url/{userId}</a>"
+    description: Créer une URL pour un centre de préférences.
+    tags:
+      - Preference Center
+  - name: "<a href='/docs/api/endpoints/preference_center/get_list_preference_center/'>/preference_center/v1/list</a>"
+    description: Répertorie les centres de préférences disponibles.
+    tags:
+      - Preference Center
+  - name: "<a href='/docs/api/endpoints/preference_center/get_view_details_preference_center'>/preference_center/v1/{preferenceCenterExternalId}</a>"
+    description: "Afficher les détails de vos centres de préférences, y compris la date de leur création et de leurs mises à jour."
+    tags:
+      - Preference Center
+  - name: "<a href='/docs/api/endpoints/preference_center/post_create_preference_center'>/preference_center/v1</a>"
+    description: Créer un centre de préférences pour permettre aux utilisateurs de gérer leurs préférences de notification pour les campagnes par e-mail.
+    tags:
+      - Preference Center
+  - name: "<a href='/docs/api/endpoints/preference_center/put_update_preference_center'>/preference_center/v1/{preferenceCenterExternalId}</a>"
+    description: Mettre à jour un centre de préférences.
+    tags:
+      - Preference Center
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk'>/catalogs/{catalog_name}/items</a>"
+    description: Supprimer plusieurs objets dans votre catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/synchronous/get_catalog_item_details/'>/catalogs/{catalog_name}/items/{item_id}</a>"
+    description: Lister un produit du catalogue et ses détails.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk/'>/catalogs/{catalog_name}/items</a>"
+    description: Éditer plusieurs objets dans votre catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk/'>/catalogs/{catalog_name}/items</a>"
+    description: Créer plusieurs objets dans votre catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_management/synchronous/delete_catalog/'>/catalogs/{catalog_name}</a>"
+    description: Supprimer un catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog/'>/catalogs</a>"
+    description: Créer un catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_management/synchronous/get_list_catalogs/'>/catalogs</a>"
+    description: "Lister les catalogues d'un espace de travail."
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item/'>/catalogs/{catalog_name}/items/{item_id}</a>"
+    description: Créer un produit dans un catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item/'>/catalogs/{catalog_name}/items/{item_id}</a>"
+    description: Éditer un produit dans un catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/synchronous/get_catalog_items_details_bulk/'>/catalogs/{catalog_name}/items</a>"
+    description: Retourner plusieurs produits du catalogue et leur contenu.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/synchronous/delete_catalog_item/'>/catalogs/{catalog_name}/items/{item_id}</a>"
+    description: Supprimer un produit dans un catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item/'>/catalogs/{catalog_name}/items/{item_id}</a>"
+    description: Mettre à jour un produit dans un catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items/'>/catalogs/{catalog_name}/items/</a>"
+    description: Mettre à jour plusieurs produits dans un catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields/'>/catalogs/{catalog_name}/fields/</a>"
+    description: Créez plusieurs champs dans un catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field/'>/catalogs/{catalog_name}/fields/{field_name}</a>"
+    description: "Supprimer un champ d'un catalogue."
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections/'>/catalogs/{catalog_name}/selections</a>"
+    description: Créer une sélection dans un catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection/'>/catalogs/{catalog_name}/selections/{selection_name}</a>"
+    description: Supprimer une sélection de catalogue.
+    tags:
+      - Catalogs
+  - name: "<a href='/docs/post_create_user_account/'>/scim/v2/Users</a>"
+    description: "Créez un nouveau compte utilisateur pour le tableau de bord en indiquant l'e-mail, les noms et prénoms, les autorisations (pour définir les autorisations au niveau de l'entreprise, de l'espace de travail et de l'équipe)."
+    tags:
+      - SCIM
+  - name: "<a href='/docs/get_see_user_account_information/'>/scim/v2/Users/{id}</a>"
+    description: Rechercher un compte utilisateur du tableau de bord existant en spécifiant leur e-mail.
+    tags:
+      - SCIM
+  - name: "<a href='/docs/post_update_existing_user_account/'>/scim/v2/Users/{id}</a>"
+    description: "Mettez à jour un compte utilisateur de tableau de bord existant en spécifiant l'e-mail, les noms et prénoms, les autorisations (pour définir les autorisations au niveau de l'entreprise, de l'espace de travail et de l'équipe)."
+    tags:
+      - SCIM
+  - name: "<a href='/docs/delete_existing_dashboard_user/'>/scim/v2/Users/{id}</a>"
+    description: Supprimer définitivement un utilisateur du tableau de bord existant.
+    tags:
+      - SCIM
+  - name: "<a href='/docs/get_search_existing_dashboard_user_email/'>/scim/v2/Users?filter={userName@example.com}</a>"
+    description: Rechercher un compte utilisateur du tableau de bord existant en spécifiant leur e-mail.
+    tags:
+      - SCIM
+  - name: "<a href='/docs/api/endpoints/cdi/get_integration_list/'>/cdi/integrations</a>"
+    description: Renvoyez une liste des intégrations existantes.
+    tags:
+      - Cloud Data Ingestion
+  - name: "<a href='/docs/api/endpoints/cdi/post_job_sync/'>/cdi/integrations/{integration_id}/sync</a>"
+    description: Déclencher une synchronisation pour une intégration donnée.
+    tags:
+      - Cloud Data Ingestion
+  - name: "<a href='/docs/api/endpoints/cdi/get_job_sync_status/'>/cdi/integrations/{integration_id}/job_sync_status</a>"
+    description: Retourne une liste des états de synchronisation.
+    tags:
+      - Cloud Data Ingestion
+---
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/identifier_types.md b/_lang/fr_fr/_api/identifier_types.md
new file mode 100644
index 00000000000..8e1b15a798a
--- /dev/null
+++ b/_lang/fr_fr/_api/identifier_types.md
@@ -0,0 +1,219 @@
+---
+nav_title: "Types d’identifiant API"
+article_title: Types d’identifiant API
+page_order: 2.2
+toc_headers: h2
+description: "Cet article de référence traite des différents types d'identifiants d'API qui existent dans le tableau de bord de Braze, de l'endroit où vous pouvez les trouver et de leur utilité." 
+page_type: reference
+
+---
+
+# Types d’identifiant API
+
+> Ce guide de référence aborde les différents types d’identifiants API que vous trouverez dans le tableau de bord de Braze, leur but, où vous pouvez les trouver et comment ils sont généralement utilisés. Pour plus d'informations sur les clés API REST ou les clés API de l'espace de travail, reportez-vous à l'[aperçu de l'API.]({{site.baseurl}}/api/api_key/)
+
+Les identifiants suivants peuvent être utilisés pour accéder à votre modèle, Canvas, campagne, segment, envoi ou carte depuis l'API externe de Braze. Tous les messages doivent respecter le codage [UTF-8.][1] 
+
+{% tabs %}
+{% tab ID de l'application %}
+
+## L’identifiant de l’application
+
+L'identifiant de l'application ou `app_id` est un paramètre qui associe l'activité à une application spécifique dans votre espace de travail. Il désigne l'application avec laquelle vous interagissez au sein de l'espace de travail. Par exemple, vous pouvez avoir un `app_id` pour votre application iOS, un `app_id` pour votre application Android et un `app_id` pour votre intégration Web. Chez Braze, il se peut que vous disposiez de plusieurs applications pour la même plateforme sur les différents types de plateformes que Braze prend en charge.
+
+### Où puis-je le trouver ?
+
+Il existe deux façons de localiser votre `app_id`:
+
+1. Allez dans **Paramètres** > **Clés API**. Sous **Identification**, vous pouvez voir toutes les `app_id` qui existent pour vos applications.
+2. Allez dans **Paramètres** > **API et identifiants**. Votre clé API est indiquée à côté du champ **Clé API** dans la section des paramètres.
+
+{% alert note %}
+Si vous utilisez l'[ancienne navigation]({{site.baseurl}}/navigation), ces pages se trouvent à un nouvel emplacement/localisation :<br> \- Les **clés API** sont situées dans la **console de développement** > **Paramètres API**.<br> - **Paramètres de l'application** situés à l'**emplacement/localisation de Gérer les paramètres** > Paramètres
+{% endalert %}
+
+### À quoi cela sert-il ?
+
+Les identifiants d’application chez Braze sont utilisés lors de l’intégration du SDK et pour référencer une application spécifique dans les appels API REST. Avec le `app_id` vous pouvez faire de nombreuses choses comme extraire des données pour un événement personnalisé qui s’est produit pour une application particulière, récupérer les statistiques de désinstallation, les statistiques de nouveaux utilisateurs, les statistiques d’utilisateur actif quotidien et les statistiques de début de session pour une application particulière.
+
+{% alert note %}
+Parfois, vous pouvez être invité à renseigner un `app_id` alors que vous ne travaillez pas avec une application, car il s’agit d’un champ hérité d’une plateforme spécifique. Vous pouvez « omettre » ce champ en incluant une chaîne de caractères comme marque substitutive pour ce paramètre requis.
+{% endalert %}
+
+### Identifiants d’application multiples
+
+Lors de la configuration du SDK, le cas d’usage le plus fréquent avec les identifiants d’application multiples est de séparer ces identifiants entre les variantes de version de débogage et de publication.
+
+Pour passer facilement d'un identifiant d'application à l'autre dans vos builds, nous vous recommandons de créer un fichier `braze.xml` distinct pour chaque [variante de build](https://developer.android.com/studio/build/build-variants.html) concernée. Une variante de version est une combinaison du type de version et de la variété du produit. Remarquez que par défaut, un nouveau projet Android est configuré avec les types de version `debug` et `release`, et aucune variété de produit.
+
+Pour chaque variante de version pertinente, créez un nouveau `braze.xml` pour elle dans `src/<build variant name>/res/values/` :
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<resources>
+<string name="com_braze_api_key">{YOUR_BUILD_VARIANT_API_KEY}</string>
+</resources>
+```
+Lorsque la variante de version est compilée, elle utilisera le nouvel identifiant.
+
+{% endtab %}
+{% tab ID des modèles %}
+
+## Identifiant du modèle
+
+Un identifiant de [modèle]({{site.baseurl}}/api/endpoints/templates/) ou ID de modèle est une clé aléatoire générée par Braze pour un modèle donné au sein du tableau de bord. Les ID de modèle sont uniques pour chaque modèle et peuvent être utilisés pour référencer les modèles via l’API. 
+
+Les modèles sont parfaits si votre entreprise établit des contrats sur vos conceptions HTML pour les campagnes. Une fois les modèles créés, vous disposez maintenant d'un modèle qui n'est pas spécifique à une campagne mais qui peut être appliqué à une série de campagnes comme une newsletter.
+
+### Où puis-je le trouver ?
+Vous pouvez trouver votre ID de modèle de deux manières :
+
+1. Cliquez sur **Modèles**, puis sélectionnez une page modèle et choisissez un modèle préexistant. Si le modèle que vous voulez n’existe pas encore, créez-en un et enregistrez-le. Au bas de la page de modèle individuel, vous trouverez votre identifiant de modèle.<br><br>
+2. Allez dans **Paramètres** > **API et identifiants**. Ici, Braze propose une recherche d'**identifiants d'API supplémentaires** qui vous permet de rechercher des identifiants spécifiques.
+
+{% alert note %}
+Si vous utilisez l'[ancienne navigation]({{site.baseurl}}/navigation), vous pouvez trouver les identifiants API dans la **console de développement** > **Paramètres API**.{% endalert %}
+
+### À quoi cela sert-il ?
+
+- Mettre à jour les modèles sur API
+- Saisir des informations sur un modèle spécifique
+
+<br>
+{% endtab %}
+{% tab Canvas IDs %}
+
+## Identifiant Canvas
+
+Un identifiant de [Canvas]({{site.baseurl}}/user_guide/engagement_tools/canvas/) ou ID Canvas est une clé aléatoire générée par Braze pour un Canvas donné au sein du tableau de bord. Les ID de Canvas sont uniques pour chaque Canvas et peuvent être utilisés pour référencer des Canvas via l’API. 
+
+Notez que si vous disposez d’un Canvas qui comporte des variantes, il existe un ID de Canvas global ainsi que des ID de Canvas pour chaque variante individuelle, imbriqués dans le Canvas principal. 
+
+### Où puis-je le trouver ?
+Vous pouvez trouver votre ID de Canvas dans le tableau de bord. Allez dans **Messagerie** > **Canvas** et sélectionnez un Canvas préexistant. Si le Canvas que vous voulez n’existe pas encore, créez-en un et enregistrez-le. En bas d'une page individuelle de Canvas, cliquez sur **Analyser variantes**. Une fenêtre apparaît avec l’identifiant de l’API de Canvas situé en bas.
+
+{% alert note %}
+Si vous utilisez l'[ancienne navigation]({{site.baseurl}}/navigation), **Canvas** se trouve sous **Engagement.**
+{% endalert %}
+
+### À quoi cela sert-il ?
+- Suivre l’analyse d’un message spécifique
+- Obtenir des statistiques globales de haut niveau sur les performances du Canvas
+- Obtenir des informations sur un Canvas spécifique
+- Avec Currents pour apporter des données au niveau de l'utilisateur pour une approche plus globale de Canvases.
+- Avec la livraison déclenchée par API afin de collecter des statistiques pour les messages transactionnels
+
+<br>
+{% endtab %}
+{% tab ID de campagne %}
+
+## Identifiant de campagne
+
+Un identifiant de [campagne]({{site.baseurl}}/user_guide/engagement_tools/campaigns/) ou ID de campagne est une clé aléatoire générée par Braze pour une campagne donnée dans le tableau de bord. Les ID de campagne sont uniques pour chaque campagne et peuvent être utilisés pour référencer des campagnes via l’API. 
+
+Notez que si vous disposez d’une campagne qui comporte des variantes, il existe un ID de campagne global ainsi que des ID de campagne aux variantes distinctes imbriqués dans la campagne principale. 
+
+### Où puis-je le trouver ?
+Vous pouvez trouver votre ID de campagne de deux manières :
+
+1. Allez dans **Envoi de messages** > **Campagnes** et sélectionnez une campagne préexistante. Si la campagne que vous souhaitez n’existe pas encore, créez-en une et enregistrez-la. Au bas de la page de la campagne individuelle, vous pourrez trouver votre **identifiant API de campagne.**<br><br>
+2. Allez dans **Paramètres** > **API et identifiants**. Ici, Braze propose une recherche d'**identifiants d'API supplémentaires** qui vous permet de rechercher des identifiants spécifiques.
+
+{% alert note %}
+Si vous utilisez l'[ancienne navigation]({{site.baseurl}}/navigation), ces pages se trouvent à un emplacement/localisation différent :<br> - **Campagnes** est sous **Engagement**<br> \- Les **clés API** sont situées dans la **console de développement** > **Paramètres API**.
+{% endalert %}
+
+### À quoi cela sert-il ?
+- Suivre l’analyse d’un message spécifique
+- Obtenir des statistiques globales de haut niveau sur les performances de la campagne
+- Obtenir des informations sur une campagne spécifique
+- Avec Currents pour apporter des données au niveau utilisateur pour bénéficier d’un « tableau général » des campagnes
+- Avec la livraison déclenchée par API afin de collecter des statistiques pour les messages transactionnels
+- Pour [rechercher une campagne spécifique]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/search_campaigns/#search-syntax) sur la page **Campagnes** à l'aide du filtre `api_id:YOUR_API_ID`
+
+<br>
+{% endtab %}
+{% tab ID des segments %}
+
+## Identifiant de segment
+
+Un identifiant de [segment]({{site.baseurl}}/user_guide/engagement_tools/segments/) ou ID de segment est une clé aléatoire générée par Braze pour un segment donné au sein du tableau de bord. Les ID de segment sont uniques pour chaque segment et peuvent être utilisés pour référencer les segments via l’API. 
+
+### Où puis-je le trouver ?
+Vous pouvez trouver votre ID de segment de deux manières :
+
+1. Allez dans **Audience** > **Segments** et sélectionnez un segment préexistant. Si le segment que vous voulez n’existe pas encore, créez-en un et enregistrez-le. Au bas de la page du segment individuel, vous trouverez votre identifiant de segment. <br><br>
+2. Cliquez sur **Paramètres** > \*\***API et identifiants**. Ici, Braze propose une recherche d'**identifiants d'API supplémentaires** qui vous permet de rechercher des identifiants spécifiques.
+
+{% alert note %}
+Si vous utilisez l'[ancienne navigation]({{site.baseurl}}/navigation), ces pages se trouvent à un emplacement/localisation différent :<br> \- Les **segments** sont sous la rubrique **Engagement**<br> \- Les **clés API** sont situées dans la **console de développement** > **Paramètres API**.
+{% endalert %}
+
+### À quoi cela sert-il ?
+- Obtenir des informations sur un segment spécifique
+- Récupérer l’analyse d’un segment spécifique
+- Récupérer le nombre de fois où un événement personnalisé a été enregistré pour un segment particulier
+- Spécifier et envoyer une campagne à un membre d’un segment depuis l’API
+
+{% endtab %}
+{% tab ID de la carte %}
+
+## Identifiant de carte
+
+Un identifiant de carte ou ID de carte est une clé générée aléatoirement générée par Braze pour une carte de fil d’actualité donnée dans le tableau de bord. Les ID des cartes sont uniques à chaque carte de [fil d'actualité]({{site.baseurl}}/user_guide/engagement_tools/news_feed/) et peuvent être utilisés pour référencer les cartes par le biais de l'API. 
+
+{% alert note %}
+Le Fil d’actualité est obsolète. Braze recommande aux clients qui utilisent notre outil de fil d’actualités de passer à notre canal de communication de cartes de contenu : il est plus flexible, plus personnalisable et plus fiable. Consultez le [guide de migration]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/migrating_from_news_feed/) pour en savoir plus.
+{% endalert %}
+
+### Où puis-je le trouver ?
+Vous pouvez trouver votre ID de carte de deux manières :
+
+1. Allez dans **Envoi de messages** > **Fil d'actualité** et sélectionnez un fil d'actualité préexistant. Si le fil d’actualité que vous voulez n’existe pas encore, créez-en un et enregistrez-le. Au bas de la page du fil d’actualité individuel, vous trouverez votre identifiant unique de carte. <br><br>
+2. Allez dans **Paramètres** > **API et identifiants**. Ici, Braze propose une recherche d'**identifiants d'API supplémentaires** qui vous permet de rechercher des identifiants spécifiques.
+
+{% alert note %}
+Si vous utilisez l'[ancienne navigation]({{site.baseurl}}/navigation), ces pages se trouvent à un nouvel emplacement/localisation :<br> \- Le **fil d'actualité** est en cours d'**engagement**<br> \- Les **clés API** sont situées dans la **console de développement** > **Paramètres API**.
+{% endalert %}
+
+### À quoi cela sert-il ?
+- Récupérer les informations pertinentes sur une carte
+- Suivre les événements liés aux cartes de contenu et à l’engagement
+
+<br>
+{% endtab %}
+{% tab Envoyer des ID %}
+
+## Identifiant d’envoi
+
+Un identifiant d'envoi, ou ID d'envoi, est une clé générée par Braze ou créée par vous pour un envoi de message donné, sous laquelle l'analyse/analytique doit être suivie. L'identifiant d'envoi vous permet d'obtenir des analyses/analytiques pour une instance spécifique d'une campagne envoyée via l'[endpoint`/sends/data_series`.]({{site.baseurl}}/api/endpoints/export/campaigns/get_send_analytics/)
+
+### Où puis-je le trouver ?
+Les API et campagnes déclenchées par API qui sont envoyées en tant que diffusion génèrent automatiquement un identifiant d’envoi si un identifiant d’envoi n’est pas fourni. Si vous souhaitez spécifier votre propre identifiant d'envoi, vous devrez d'abord en créer un via l'[endpoint`/sends/id/create`.]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_create_send_ids/) L’identifiant ne peut comporter que des caractères ASCII et ne peut faire plus de 64 caractères. Vous pouvez réutiliser un identifiant d’envoi sur plusieurs envois de la même campagne si vous souhaitez regrouper les analyses de ces envois.
+
+### À quoi cela sert-il ?
+Envoyer et suivre par programme les performances des messages, sans création de campagne pour chaque envoi.
+
+<br>
+{% endtab %}
+{% tab ID des groupes d'abonnement %}
+
+## Identifiant du groupe d'abonnement
+
+Un identifiant de groupe d'abonnement, ou ID de groupe d'abonnement, est une clé générée par Braze pour un groupe d'abonnement donné. Les ID sont uniques à chaque groupe d'abonnement et peuvent être utilisés pour référencer les groupes d'abonnement via l'API.
+
+### Où puis-je le trouver ?
+
+Allez dans **Audience** > **Abonnements** et copiez l'ID à côté du groupe d'abonnement concerné.
+
+### À quoi cela sert-il ?
+
+- Liste des groupes d'abonnement d'un utilisateur
+- Obtenir le statut du groupe d'abonnement d'un utilisateur
+- Mise à jour du statut du groupe d'abonnement d'un utilisateur
+
+{% endtab %}
+{% endtabs %}
+
+[1]: https://en.wikipedia.org/wiki/UTF-8
+[3]: https://developer.android.com/studio/build/build-variants.html
diff --git a/_lang/fr_fr/_api/network_connectivity_issues.md b/_lang/fr_fr/_api/network_connectivity_issues.md
new file mode 100644
index 00000000000..f1c8994ba9b
--- /dev/null
+++ b/_lang/fr_fr/_api/network_connectivity_issues.md
@@ -0,0 +1,36 @@
+---
+nav_title: Problèmes de connectivité réseau d’API
+article_title: Problèmes de connectivité réseau d’API
+page_order: 4
+description: "Cet article de référence aborde les problèmes de connectivité d’API et comment les résoudre."
+page_type: reference
+
+---
+
+# Problèmes de connectivité réseau de l’API
+
+> Cet article de référence aborde les problèmes de connectivité d’API et comment les résoudre.
+
+Les endpoints de l'API de Braze utilisent un réseau de diffusion de contenu qui achemine le trafic vers le POP le plus proche en fonction des informations DNS.  Si vous rencontrez des problèmes de connexion ou remarquez que vous vous connectez à un POP inefficace, assurez-vous d’utiliser les serveurs DNS de votre fournisseur ou les serveurs DNS configurés dans le même centre de données que votre serveur et de disposer des métadonnées appropriées de localisation IP associées à ces derniers.
+
+Nous avons remarqué qu'une poignée de pare-feu tentent de modifier ou de sécuriser le trafic HTTPS/TLS, ce qui interfère avec les connexions aux points d'extrémité de l'API de Braze. Si vos serveurs se trouvent derrière un quelconque pare-feu physique, désactivez toute accélération ou modification HTTPS/TLS effectuée par le pare-feu ou le routeur. En outre, vous pouvez autoriser le trafic sortant vers nos fournisseurs de réseau de diffusion de contenu (Fastly.com) pour voir si cela résout le problème.
+
+Parfois, les configurations d'iptables qui filtrent les paquets SYN/ACK/RST peuvent également causer des problèmes. Si vous utilisez iptables sur votre hôte, vous pouvez également autoriser le trafic sortant vers nos fournisseurs de réseau de diffusion de contenu (Fastly.com) pour voir si cela résout le problème.
+
+Si vous rencontrez toujours des problèmes de réseau lors de la connexion aux endpoints de l'API Braze, fournissez un [test MTR][1] et les résultats de [Fastly Debug][2] pendant que vous rencontrez un problème et soumettez-les avec votre demande d'assistance. Notez que les résultats du test doivent être obtenus à partir d'un serveur qui rencontre des problèmes de connexion aux points d'extrémité de l'API Braze, et non à partir d'une machine de développement. Une capture du réseau (fichier tcpdump ou .pcap) sera également utile si elle peut être obtenue.
+
+Pour plus d’informations sur le MTR, consultez ces ressources en fonction de votre système d’exploitation :
+
+- [GNU/Linux][4]
+- [macOS][5]
+
+## Autoriser la liste des plages d'adresses IP des points d'extrémité de l'API Braze
+
+Pour autoriser les points d'extrémité de l'API Braze à travers votre pare-feu, notre réseau de diffusion de contenu permet d'accéder à la liste des plages d'adresses IP attribuées par le biais d'un vidage JSON. Pour obtenir une liste des plages d'IP de l'API de [Braze][3], reportez-vous à la fois à [la liste des IP publiques de Fastly][3] et à celle [de Cloudflare.][6] Notez que ces adresses IP peuvent changer.
+
+[1]: https://www.privateinternetaccess.com/helpdesk/kb/articles/what-is-an-mtr-test-and-how-do-i-run-one-2
+[2]: http://www.fastly-debug.com/
+[3]: https://api.fastly.com/public-ip-list
+[4]: https://www.digitalocean.com/community/tutorials/how-to-use-traceroute-and-mtr-to-diagnose-network-issues
+[5]: https://formulae.brew.sh/formula/mtr
+[6]: https://api.cloudflare.com/client/v4/ips
diff --git a/_lang/fr_fr/_api/objects_filters.md b/_lang/fr_fr/_api/objects_filters.md
new file mode 100644
index 00000000000..16222b2c731
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters.md
@@ -0,0 +1,35 @@
+---
+nav_title: Objets et filtres
+article_title: Objets et filtres
+page_order: 1.5
+description: "Cette page d’accueil répertorie les objets et filtres d’API Braze utilisés dans vos appels d’API Braze."
+
+---
+
+# Objets et filtres
+
+> Cette page répertorie les objets et filtres d’API Braze utilisés dans vos appels d’API Braze.
+
+## Objets et filtres
+
+- [Objet Propriétés d’entrées de Canvas]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object)
+- [Objet et filtre Audience connectée]({{site.baseurl}}/api/objects_filters/connected_audience/)
+- [Objet Événement]({{site.baseurl}}/api/objects_filters/event_object/)
+- [Objet Achat]({{site.baseurl}}/api/objects_filters/purchase_object/)
+- [Objet Destinataire]({{site.baseurl}}/api/objects_filters/recipient_object/)
+- [Objet Alias d’identification]({{site.baseurl}}/api/objects_filters/aliases_to_identify)
+- [Objet Propriétés du déclencheur]({{site.baseurl}}/api/objects_filters/trigger_properties_object)
+- [Objet Alias utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object)
+- [Objet Attribut utilisateur]({{site.baseurl}}/api/objects_filters/user_attributes_object)
+- [Objet Planification]({{site.baseurl}}/api/objects_filters/schedule_object/)
+
+### Objets Messagerie
+  - [Objet Android]({{site.baseurl}}/api/objects_filters/messaging/android_object/)
+  - [Objet Apple]({{site.baseurl}}/api/objects_filters/messaging/apple_object/)
+  - [Objet Carte de contenu]({{site.baseurl}}/api/objects_filters/messaging/content_cards_object)
+  - [Objet E-mail]({{site.baseurl}}/api/objects_filters/messaging/email_object/)
+  - [Objet Notification push Kindle et FireOS]({{site.baseurl}}/api/objects_filters/messaging/kindle_and_fireos_object)
+  - [Objet SMS]({{site.baseurl}}/api/objects_filters/messaging/sms_object)
+  - [Objet Web]({{site.baseurl}}/api/objects_filters/messaging/web_objects/)
+  - [Objet Webhook]({{site.baseurl}}/api/objects_filters/messaging/webhook_object)
+  - [Objet WhatsApp]({{site.baseurl}}/api/objects_filters/messaging/whats_app_object)
diff --git a/_lang/fr_fr/_api/objects_filters/aliases_to_identify.md b/_lang/fr_fr/_api/objects_filters/aliases_to_identify.md
new file mode 100644
index 00000000000..4a9b931d5e6
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/aliases_to_identify.md
@@ -0,0 +1,36 @@
+---
+nav_title: "Objet Alias d’identification"
+article_title: Objet Alias d’identification de l’API
+page_order: 11
+page_type: reference
+description: "Cet article explique les alias pour identifier la spécification d’objet."
+
+---
+
+# Objet Alias d’identification
+
+Une demande API contenant l’un des champs de l’objet Attributs créera ou mettra à jour un attribut de ce nom avec la valeur donnée sur le profil utilisateur spécifié. 
+
+Utilisez les noms de champs de profil utilisateur Braze (énumérés comme suit ou tout autre répertorié dans la section pour [Braze user profile fields]({{site.baseurl}}/api/objects_filters/user_attributes_object/#braze-user-profile-fields)) pour mettre à jour ces valeurs spéciales sur le profil utilisateur dans le tableau de bord ou ajoutez vos propres données d'attributs personnalisés à l'utilisateur.
+
+## Corps de l’objet
+
+```json
+{
+  "aliases_to_identify" : (required, array of aliases to identify object)
+  [
+    {
+      "external_id" : (required, string) see External user ID,
+      // external_ids for users that do not exist will return a non-fatal error.
+      // See server responses for details.
+      "user_alias" : {
+        "alias_name" : (required, string) see User aliases,
+        "alias_label" : (required, string) see User aliases
+      }
+    }
+  ]
+}
+```
+
+- [ID utilisateur externe]({{site.baseurl}}/api/objects_filters/user_attributes_object/#braze-user-profile-fields)
+- [Alias utilisateurs]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases)
diff --git a/_lang/fr_fr/_api/objects_filters/canvas_entry_properties_object.md b/_lang/fr_fr/_api/objects_filters/canvas_entry_properties_object.md
new file mode 100644
index 00000000000..7b584bcd968
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/canvas_entry_properties_object.md
@@ -0,0 +1,30 @@
+---
+nav_title: "Objet Propriétés d’entrées de Canvas"
+article_title: Objet Propriétés d’entrées de Canvas de l’API
+page_order: 2
+page_type: reference
+tool:
+  - Canvas
+description: "Cet article explique l’objet Propriétés d’entrées de Canvas de Braze."
+
+---
+
+# Objet Propriétés d’entrées de Canvas
+
+> Lors de l'utilisation de l'un des points de terminaison pour déclencher ou planifier un Canvas via l'API, vous pouvez fournir une carte de clés et de valeurs pour personnaliser les messages envoyés par les premières étapes de votre Canvas, dans l'espace de noms `canvas_entry_properties`.
+
+{% alert note %}
+La limite maximale de taille de l’objet Propriétés d’entrées de Canvas est de 50 Ko.
+{% endalert %}
+
+## Corps de l’objet
+
+Ce corps d’objet contient un exemple de demande.
+
+```json
+"canvas_entry_properties": {"product_name" : "shoes", "product_price" : 79.99}
+```
+
+{% raw %}
+Par exemple, une requête avec `"canvas_entry_properties": {"product_name" : "shoes", "product_price" : 79.99}` pourrait inclure le terme « chaussures » à un message en ajoutant ```{{canvas_entry_properties.${product_name}}}``` à la demande.
+{% endraw %}
diff --git a/_lang/fr_fr/_api/objects_filters/connected_audience.md b/_lang/fr_fr/_api/objects_filters/connected_audience.md
new file mode 100644
index 00000000000..98e15a86bef
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/connected_audience.md
@@ -0,0 +1,160 @@
+---
+nav_title: "Objet et filtre Audience connectée"
+article_title: Objet Audience connectée de l’API
+page_order: 3
+page_type: reference
+description: "Cet article explique les différents composants de l’objet Audience connectée et les filtres qui le créent."
+
+---
+
+# Objet Audience connectée
+
+> Un objet Audience connectée est un sélecteur qui identifie l’audience à laquelle envoyer le message. 
+
+Cet objet est composé soit d'un seul filtre d'audience connectée, soit de plusieurs filtres d'audience connectée dans une expression logique utilisant des opérateurs `AND` ou `OR`.
+
+**Exemple de filtre multiple :**
+
+```json
+{
+  "AND":
+    [
+      Connected Audience Filter,
+      {
+        "OR" :
+          [
+            Connected Audience Filter,
+            Connected Audience Filter
+          ]
+      },
+      Connected Audience Filter
+    ]
+}
+```
+
+## Filtres d’audience connectée
+
+L’association de plusieurs filtres d’attributs personnalisés crée un filtre d’audience connectée, qui crée lui-même un filtre d’audience connectée lorsqu’il est combiné avec les opérateurs `AND` et `OR`.
+
+### Filtre d’attribut personnalisé
+
+Ce filtre vous permet de segmenter en fonction de l’attribut personnalisé d’un utilisateur. Ces filtres contiennent jusqu’à trois champs :
+
+```json
+{
+  "custom_attribute":
+    {
+      "custom_attribute_name": (String) the name of the custom attribute to filter on,
+      "comparison": (String) one of the allowed comparisons to make against the provided value,
+      "value": (String, Numeric, Boolean) the value to be compared using the provided comparison
+    }
+}
+```
+
+#### Comparaisons autorisées par type de données
+
+Le type de données de l’attribut personnalisé détermine les comparaisons qui sont valides pour un filtre donné.
+
+| Type d’attribut personnalisé | Comparaisons autorisées |
+| ---------------------| --------------- |
+| Chaîne de caractères | `equals`, `not_equal`, `matches_regex`, `does_not_match_regex`, `exists`, `does_not_exist` |
+| Tableau | `includes_value`, `does_not_include_value`, `exists`, `does_not_exist` |
+| Numérique | `equals`, `not_equal`, `greater_than`, `greater_than_or_equal_to`, `less_than`, `less_than_or_equal_to`, `exists`, `does_not_exist` |
+| Valeur booléenne | `equals`, `does_not_equal`, `exists`, `does_not_exist` |
+| Date | `less_than_x_days_ago`, `greater_than_x_days_ago`, `less_than_x_days_in_the_future`, `greater_than_x_days_in_the_future`, `after`, `before`, `exists`, `does_not_exist` | 
+{: .reset-td-br-1 .reset-td-br-2}
+
+#### Mises en garde dans la comparaison des attributs
+
+| Comparaison | Considérations supplémentaires |
+| --- | --- |
+| `value` | Le `value` n'est pas nécessaire lors de l'utilisation des comparaisons `exists` ou `does_not_exist`. `value` doit être une chaîne datetime ISO 8601 lors de l'utilisation des comparaisons `before` et `after`. |
+|`matches_regex` | Lors de l’utilisation de la comparaison `matches_regex`, la valeur transmise doit être une chaîne de caractères. Pour en savoir plus sur l'utilisation des expressions régulières avec Braze, consultez [Expressions régulières]({{site.baseurl}}/user_guide/engagement_tools/segments/regex/#regex-with-braze) et [Types de données d'attributs personnalisés]({{site.baseurl}}/developer_guide/platform_wide/analytics_overview/#custom-attribute-data-types). |
+{: .reset-td-br-1 .reset-td-br-2}
+
+#### Exemple d’attribut personnalisé
+
+```json
+{
+  "custom_attribute":
+    {
+      "custom_attribute_name": "eye_color",
+      "comparison": "equals",
+      "value": "blue"
+    }
+}
+
+{
+  "custom_attribute":
+  {
+    "custom_attribute_name": "favorite_foods",
+    "comparison": "includes_value",
+    "value": "pizza"
+  }
+}
+
+{
+  "custom_attribute":
+  {
+    "custom_attribute_name": "last_purchase_time",
+    "comparison": "less_than_x_days_ago",
+    "value": 2
+  }
+}
+```
+### Filtre d’abonnement aux notifications push
+
+Ce filtre vous permet de segmenter en fonction du statut d’abonnement aux notifications push d’un utilisateur.
+
+#### Corps du filtre
+
+```json
+{
+  "push_subscription_status":
+  {
+    "comparison": (String) one of the following allowed comparisons,
+    "value": (String) one of the following allowed values
+  }
+}
+```
+
+- **Comparaisons autorisées :** `is`, `is_not`
+- **Valeurs autorisées :** `opted_in`, `subscribed`, `unsubscribed`
+
+### Filtre d’abonnement aux e-mails
+
+Ce filtre vous permet de segmenter en fonction du statut d’abonnement aux e-mails d’un utilisateur.
+
+#### Corps du filtre
+
+```json
+{
+  "email_subscription_status":
+  {
+    "comparison": (String) one of the following allowed comparisons,
+    "value": (String) one of the following allowed values
+  }
+}
+```
+
+- **Comparaisons autorisées :** `is`, `is_not`
+- **Valeurs autorisées :** `opted_in`, `subscribed`, `unsubscribed`
+
+### Dernier filtre d’application utilisé
+
+Ce filtre vous permet de segmenter en fonction du moment où l’utilisateur a utilisé l’application pour la dernière fois. Ces filtres contiennent deux champs :
+
+#### Corps du filtre
+```json
+{
+  "last_used_app":
+  {
+    "comparison": (String) one of the allowed comparisons listed,
+    "value": (String) the value to be compared using the provided comparison
+  }
+}
+```
+
+- **Comparaisons autorisées :** `after`, `before`
+- **Valeurs autorisées :** datetime (chaîne ISO 8601)
+
diff --git a/_lang/fr_fr/_api/objects_filters/event_object.md b/_lang/fr_fr/_api/objects_filters/event_object.md
new file mode 100644
index 00000000000..0c2312bb9a5
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/event_object.md
@@ -0,0 +1,126 @@
+---
+nav_title: "Objet Événement"
+article_title: Objet Événement de l’API
+page_order: 6
+page_type: reference
+description: "Cet article de référence explique l’objet Événement, ce qu’il est et en quoi il est essentiel dans les stratégies de campagne basées sur les événements."
+
+---
+
+# Objet Événement
+
+> Cet article explique les différents composants d’un objet Événement, comment vous pouvez l’utiliser et des exemples dont vous pouvez vous inspirer.
+
+## Qu’est-ce que l’objet Événement ?
+
+Un objet Événement est un objet qui passe par l’API lorsqu’un événement spécifique se produit. Les objets Événements sont hébergés dans un tableau d’événements. Chaque objet Événement du tableau d’événements représente l’occurrence unique d’un événement personnalisé par un utilisateur particulier à la valeur de temps désignée. L’objet Événement comporte plusieurs champs qui vous permettent de le personnaliser en définissant et en utilisant les propriétés de l’événement dans les messages, la collecte de données et la personnalisation.
+
+Vous pouvez vérifier comment configurer des événements personnalisés pour une plateforme spécifique en lisant le guide d'intégration de la plateforme dans le [guide du développeur.][1] Vous trouverez ces informations dans la page **Suivi des événements personnalisés** sous l'onglet **Analyse des** différentes plateformes. Nous en avons associé plusieurs pour vous.
+
+Article sur le suivi des événements personnalisés :
+
+- [Android][2]
+- [iOS][3]
+- [Web][4]
+
+### Corps de l’objet
+
+```json
+{
+  // One of "external_id" or "user_alias" or "braze_id" or "email" is required
+  "external_id" : (optional, string) External user ID,
+  "user_alias" : (optional, User Alias Object) User alias object,
+  "braze_id" : (optional, string) Braze user identifier,
+  "email": (optional, string) User email address,
+  "app_id" : (optional, string) see App Identifier,
+  "name" : (required, string) the name of the event,
+  "time" : (required, datetime as string in ISO 8601 or in `yyyy-MM-dd'T'HH:mm:ss:SSSZ` format),
+  "properties" : (optional, Properties Object) properties of the event
+  // Setting this flag to true will put the API in "Update Only" mode.
+  // When using a "user_alias", "Update Only" mode is always true.
+  "_update_existing_only" : (optional, boolean)
+  // See following notes regarding anonymous push token imports
+}
+```
+
+- [ID utilisateur externe]({{site.baseurl}}/api/basics/#user-ids)
+- [Identifiant d’application]({{site.baseurl}}/api/identifier_types/)
+- [ISO 8601 Time Code Wiki][22]
+
+#### Mettre à jour les profils existants uniquement
+
+Si vous souhaitez mettre à jour uniquement les profils utilisateur existants dans Braze, vous devez passer la clé `_update_existing_only` avec la valeur `true` dans le corps de votre demande. Si cette valeur est omise, Braze créera un nouveau profil utilisateur si `external_id` n’existe pas déjà.
+
+{% alert note %}
+Si vous créez un profil utilisateur alias uniquement via l'endpoint `/users/track`, `_update_existing_only` doit être défini sur `false`. Si cette valeur est omise, le profil alias uniquement ne sera pas créé.
+{% endalert %}
+
+## Objet de propriétés de l’événement
+Les événements et achats personnalisés peuvent avoir des propriétés d’événement. Les valeurs des « Properties (Propriétés) » doivent être un objet dont les clés sont les noms de propriétés et les valeurs sont les valeurs de propriété. Les noms de propriété doivent être des chaînes de caractères non vides de moins de 255 caractères, qui ne commencent pas par un symbole de dollar ($).
+
+Les valeurs de propriété peuvent être l’un des types de données suivants :
+
+| Type de données | Description |
+| --- | --- |
+| Chiffres | Sous forme d'[entiers](https://en.wikipedia.org/wiki/Integer) ou de [float](https://en.wikipedia.org/wiki/Floating-point_arithmetic) |
+| Booléens |  |
+| Datetimes | Formatés sous forme de chaînes de caractères au format [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ou `yyyy-MM-dd'T'HH:mm:ss:SSSZ`. Non pris en charge dans les tableaux. |
+| Chaînes de caractères | 255 caractères ou moins. |
+| Tableaux | Les tableaux ne peuvent pas inclure des dates/horodatages. |
+| Objets | Les objets seront ingérés en tant que chaînes de caractères. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+Les objets de propriété d'événement qui contiennent des valeurs de tableau ou d'objet peuvent avoir une charge utile de propriété d'événement allant jusqu'à 50 Ko.
+
+### Persistance des propriétés de l’événement
+Les propriétés de l’événement sont conçues pour filtrer et personnaliser avec Liquid les messages déclenchés par leurs événements parents. Par défaut, elles ne sont pas persistantes sur le profil utilisateur Braze. Pour utiliser les valeurs des propriétés d'événement dans la segmentation, reportez-vous aux [événements personnalisés][5], qui détaillent les différentes approches de stockage à long terme des valeurs des propriétés d'événement.
+
+#### Demande d’exemple d’événement
+
+```json
+POST https://YOUR_REST_API_URL/users/track
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "events" : [
+    {
+      "external_id" : "user1",
+      "app_id" : "your-app-id",
+      "name" : "watched_trailer",
+      "time" : "2013-07-16T19:20:30+01:00"
+    },
+    {
+      "external_id" : "user1",
+      "app_id" : "your-app-id",
+      "name" : "rented_movie",
+      "time" : "2013-07-16T19:20:45+01:00",
+      "properties": {
+        "movie": "The Sad Egg",
+        "director": "Dan Alexander"
+      }
+    },
+    {
+      "user_alias" : { "alias_name" : "device123", "alias_label" : "my_device_identifier"},
+      "app_id" : "your-app-id",
+      "name" : "watched_trailer",
+      "time" : "2013-07-16T19:20:50+01:00"
+    }
+  ]
+}
+```
+- [ISO 8601 Time Code Wiki][19]
+
+## Objets Événement
+
+À l’aide de l’exemple fourni, nous pouvons voir que quelqu’un a regardé une bande-annonce récemment, puis a loué un film. Bien que nous ne puissions pas accéder à une campagne et segmenter les utilisateurs en fonction de ces propriétés, nous pouvons utiliser ces propriétés stratégiquement en les exploitant sous forme de reçu, pour envoyer un message personnalisé via un canal grâce à Liquid. Par exemple, "Hello **Beth**, Thanks for renting **The Sad Egg** by **Dan Alexander**, here are some recommended movies based on your rental..." (Bonjour **Beth**, Merci d'avoir loué **The Sad Egg** de **Dan Alexander**, voici quelques films recommandés en fonction de votre location).
+
+
+[1]: {{site.baseurl}}/developer_guide/home/
+[2]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/analytics/tracking_custom_events/
+[3]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/tracking_custom_events/
+[4]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/tracking_custom_events/
+[5]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/
+[19]: http://en.wikipedia.org/wiki/ISO_8601 "ISO 8601 Time Code Wiki"
+[21]: {{site.baseurl}}/api/api_key/#the-app-identifier-api-key
+[22]: https://en.wikipedia.org/wiki/ISO_8601 "Code temporel ISO 8601"
+[23]: {{site.baseurl}}/api/basics/#external-user-id-explanation
diff --git a/_lang/fr_fr/_api/objects_filters/messaging.md b/_lang/fr_fr/_api/objects_filters/messaging.md
new file mode 100644
index 00000000000..89fa7ddcbf5
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging.md
@@ -0,0 +1,5 @@
+---
+nav_title: Objets Message
+config_only: true
+noindex: true
+---
diff --git a/_lang/fr_fr/_api/objects_filters/messaging/android_object.md b/_lang/fr_fr/_api/objects_filters/messaging/android_object.md
new file mode 100644
index 00000000000..739b113b323
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging/android_object.md
@@ -0,0 +1,105 @@
+---
+nav_title: "Objets Android"
+article_title: Objet Messagerie Android
+page_order: 0
+page_type: reference
+channel: push
+platform: Android
+description: "Cet article de référence répertorie et explique les différents objets Android utilisés chez Braze."
+
+---
+# Objet Android
+
+> L'objet `android_push` vous permet de définir ou de demander des informations relatives au contenu Android Push et Android Push Alert par le biais de nos [points d'extrémité de messages.]({{site.baseurl}}/api/endpoints/messaging)
+
+## Objet Notification push Android
+
+Vous devez inclure un objet Android push dans `messages` si vous voulez que les utilisateurs que vous avez ciblés reçoivent un push sur leurs appareils Android. Le nombre total d'octets de votre chaîne de caractères `alert` et de votre objet `extra` ne doit pas dépasser 4 000. L’API de messagerie renvoie une erreur si vous dépassez la taille de message autorisée par Google.
+
+```json
+{
+   "alert": (required, string) the notification message,
+   "title": (required, string) the title that appears in the notification drawer,
+   "extra": (optional, object) additional keys and values to be sent in the push,
+   "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under (must be an Android Push Message),
+   "notification_channel_id": (optional, string) the channel ID the notification will be sent with,
+   "priority": (optional, integer) the notification priority value,
+   "send_to_sync": (optional, if set to true we will throw an error if "alert" or "title" is set),
+   "collapse_key": (optional, string) the collapse key for this message,
+   // Specifying "default" in the sound field will play the standard notification sound
+   "sound": (optional, string) the location of a custom notification sound within the app,
+   "custom_uri": (optional, string) a web URL, or Deep Link URI,
+   "summary_text": (optional, string),
+   "time_to_live": (optional, integer (maximum of 2,419,200 seconds)),
+   "notification_id": (optional, integer),
+   "push_icon_image_url": (optional, string) an image URL for the large icon,
+   "accent_color": (optional, integer) accent color to be applied by the standard Style templates when presenting this notification, an RGB integer value,
+   "send_to_most_recent_device_only": (optional, boolean) defaults to false, if set to true, Braze will only send this push to a user's most recently used Android device, rather than all eligible Android devices,
+   "buttons" : (optional, array of Android push action button objects) push action buttons to display
+   "conversation_data" : (optional, Android Conversation Push Object) the data to be displayed through Conversation Push.
+}
+```
+
+Vous pouvez envoyer des notifications « Big Picture » en spécifiant la clé `appboy_image_url` dans l’objet `extra`. La valeur de `appboy_image_url` doit être une URL qui renvoie à l’emplacement où votre image est hébergée. Les images doivent être recadrées à un rapport hauteur/largeur de 2:1 et doivent avoir une taille minimale de 600 x 300 px. Les images utilisées pour les notifications ne s’afficheront que sur les appareils exécutant Jelly Bean (Android 4.1) ou une version supérieure.
+
+### Informations relatives aux paramètres supplémentaires
+
+| Paramètre | Détails |
+| --------- | ------- |
+| `priority` | Ce paramètre accepte les valeurs entre `-2` et `2`, où `-2` représente la priorité « MIN » et `2` représente la priorité « MAX ». `0` est la valeur « PAR DÉFAUT ». <br> <br> Toutes les valeurs envoyées en dehors de cette plage prendront la valeur 0 par défaut. Pour plus d'informations sur le niveau de priorité à utiliser, voir [Priorité des notifications Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/customization/advanced_settings#notification-priority). |
+| `collapse_key` | FCM peut stocker simultanément jusqu’à quatre clés de réduction par appareil. Si vous utilisez plus de quatre clés de réduction, FCM ne donne aucune garantie quant à celles qui seront conservées. Braze utilise l’un de ces éléments par défaut pour les campagnes, assurez-vous donc de ne spécifier que jusqu’à trois clés de réduction supplémentaires pour les messages Android. |
+| `push_icon_image_url` | La valeur du paramètre des grandes icônes doit être une URL qui renvoie à l’emplacement où votre image est hébergée. <br> <br> Les images doivent être recadrées selon un apport hauteur/largeur  1:1 et mesurer au moins 40x40. |
+| `notification_channel` | Si cela n'est pas spécifié, Braze tentera d'envoyer la charge utile de la notification avec l'ID du canal de [repli du tableau de bord][45]. Pour en savoir plus, consultez la section [Canaux de notification][44] et reportez-vous aux étapes de [définition des canaux de notification][43] lors de l'intégration. |
+| `send_to_sync` | Pour plus d'informations sur les messages `send_to_sync`, consultez [les notifications Android silencieuses][28]. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+## Objet Bouton d’action push Android
+
+```json
+{
+  "text": (required, string) the button's text,
+  "action": (optional, string) one of "OPEN_APP", "URI", "DEEP_LINK", or "CLOSE", defaults to "OPEN_APP",
+  "uri": (optional, string) a web URL or Deep Link URI,
+  "use_webview": (optional, boolean) whether to open the web URL inside the app if the action is "URI", defaults to true
+}
+```
+
+## Objet de notification push de conversation pour Android {#android-conversation-push-object}
+
+{% sdk_min_versions android:15.0.0 %}
+
+Les concepts présentés dans ce message correspondent à ceux de la documentation [Android People et Conversations][46] push.
+
+```json
+{
+  "shortcut_id" : (required, string) the sharing shortcut identifier,
+  "reply_person_id" : (required, string) the identifier of the Person this push is replying to,
+  "messages" : (required, array of Android Conversation Push Message Object),
+  "persons" : (required, array of Android Conversation Push Person Object)
+}
+```
+
+### Objet Notification push Android de conversation pour les messages
+
+```json
+{
+  "text" : (required, string) the text of this message,
+  "timestamp" : (required, integer) the unix timestamp of when this message was sent,
+  "person_id" : (required, string) the Person identifier of this message's sender,
+}
+```
+
+### Objet Notification push Android de conversation pour les personnes
+
+```json
+{
+  "id" : (required, string) the identifier of this Person,
+  "name" : (required, string) the display name of this Person
+}
+```
+
+[28]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/silent_push_notifications/#silent-push-notifications
+[44]: {{site.baseurl}}/user_guide/message_building_by_channel/push/notification_channels/
+[43]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/integration/standard_integration/#step-5-define-notification-channels
+[45]: {{site.baseurl}}/user_guide/message_building_by_channel/push/android/notification_channels/#dashboard-fallback-channel
+[46]: https://developer.android.com/guide/topics/ui/conversations
diff --git a/_lang/fr_fr/_api/objects_filters/messaging/apple_object.md b/_lang/fr_fr/_api/objects_filters/messaging/apple_object.md
new file mode 100644
index 00000000000..f8eaf3c1061
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging/apple_object.md
@@ -0,0 +1,100 @@
+---
+nav_title: "Objet Apple"
+article_title: Objet de messagerie Apple
+page_order: 1
+page_type: reference
+channel: push
+platform: iOS
+description: "Cet article de référence répertorie et explique les différents objets Apple utilisés chez Braze."
+
+---
+
+# Objet Notification push Apple
+
+> L'objet `apple_push` vous permet de définir ou de demander des informations relatives au contenu Apple Push et Apple Push Alert par l'intermédiaire de nos [points d'envoi de messages.]({{site.baseurl}}/api/endpoints/messaging)
+
+## Objet Notification push Apple
+
+```json
+{
+   "badge": (optional, int) the badge count after this message,
+   "alert": (required unless content-available is true, string or Apple Push Alert Object) the notification message,
+   // Specifying "default" in the sound field will play the standard notification sound
+   "sound": (optional, string) the location of a custom notification sound within the app,
+   "extra": (optional, object) additional keys and values to be sent,
+   "content-available": (optional, boolean) if set, Braze will add the "content-available" flag to the push payload,
+   "interruption_level": (optional, string: "passive", "active", "time-sensitive", or "critical") specifies the interruption level passed (iOS 15+),
+   "relevance_score": (optional, float) specifies the relevance score between 0.0 and 1.0 used for grouping notification summaries (iOS 15+),
+   "expiry": (optional, ISO 8601 date string) if set, push messages will expire at the specified datetime,
+   "custom_uri": (optional, string) a web URL, or Deep Link URI,
+   "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under (must be an iOS Push Message),
+   "notification_group_thread_id": (optional, string) the notification group thread ID the notification will be sent with,
+   "asset_url": (optional, string) content URL for rich notifications for devices using iOS 10 or higher,
+   "asset_file_type": (required if asset_url is present, string) file type of the asset - one of "aif", "gif", "jpg", "m4a", "mp3", "mp4", "png", or "wav",
+   "collapse_id": (optional, string) To update a notification on the user's device after you've issued it, send another notification with the same collapse ID you used previously
+   "mutable_content": (optional, boolean) if true, Braze will add the mutable-content flag to the payload and set it to 1. The mutable-content flag is automatically set to 1 when sending a rich notification, regardless of the value of this parameter.
+   "send_to_most_recent_device_only": (optional, boolean) defaults to false, if set to true, Braze will only send this push to a user's most recently used iOS device, rather than all eligible iOS devices,
+   "category": (optional, string) the iOS notification category identifier for displaying push action buttons,
+   "buttons" : (optional, array of Apple push action button objects) push action buttons to display
+}
+```
+
+Vous devez inclure un objet Notification push Apple dans `messages` si vous souhaitez que les utilisateurs ciblés reçoivent une notification push sur leurs appareils iOS. Le nombre total d’octets dans votre chaîne de caractères `alert`, objet `extra` et vos autres paramètres facultatifs ne doit pas dépasser 1912. L’API de messagerie renvoie une erreur si vous dépassez la taille de message autorisée par Apple. Les messages incluant les clés `ab` ou `aps` dans l’objet `extra` seront rejetés.
+
+{% alert note %}
+Si vous envoyez l'objet Apple Push dans le cadre d'une ligne/en production/instantanée, veillez à inclure votre chaîne de caractères `sound` dans l'objet `alert`.
+{% endalert %}
+
+### Objet Notification push Apple pour les alertes
+
+Dans la plupart des cas, l’`alert` peut être spécifiée comme une chaîne de caractères dans un objet `apple_push`.
+
+```json
+{
+   "body": (required unless content-available is true in the Apple Push Object, string) the text of the alert message,
+   "title": (optional, string) a short string describing the purpose of the notification, displayed as part of the Apple Watch notification interface,
+   "title_loc_key": (optional, string) the key to a title string in the `Localizable.strings` file for the current localization,
+   "title_loc_args": (optional, array of strings) variable string values to appear in place of the format specifiers in title_loc_key,
+   "action_loc_key": (optional, string) if a string is specified, the system displays an alert that includes the Close and View buttons, the string is used as a key to get a localized string in the current localization to use for the right button's title instead of "View",
+   "loc_key": (optional, string) a key to an alert-message string in a Localizable.strings file for the current localization,
+   "loc_args": (optional, array of strings) variable string values to appear in place of the format specifiers in loc_key,
+   "sound": (optional, string) the location of a custom notification sound within the app (live activities only),
+}
+```
+
+## Objet Boutons d’action de notification push Apple
+
+Vous devez inclure le champ `category` dans l’objet Notification push Apple pour utiliser les boutons d’action push iOS. Inclure le champ `category` affichera tous les boutons d’action push associés. N’ajoutez le champ `buttons` que si vous souhaitez définir en plus les actions de clic individuelles des boutons. Le SDK Braze fournit un ensemble de boutons d’action push par défaut que vous pouvez utiliser et qui sont présentés dans le tableau suivant. Vous pouvez également utiliser vos propres boutons s’ils ont été enregistrés dans votre application.
+
+### Objet Boutons d’action de notification push Apple pour les boutons par défaut de Braze
+
+| Identifiant de catégorie   | Texte du bouton | Identifiant d’action du bouton | Actions autorisées         |
+|-----------------------|-------------|--------------------------|-------------------------|
+| `ab_cat_accept_decline` | Accepter      | `ab_pb_accept`             | OPEN_APP, URI ou DEEP_LINK |
+| `ab_cat_accept_decline` | Refuser     | `ab_pb_decline`            | FERMER                   |
+| `ab_cat_yes_no`         | Oui         | `ab_pb_yes`                | OPEN_APP, URI ou DEEP_LINK |
+| `ab_cat_yes_no`         | Non          | `ab_pb_no`                 | FERMER                   |
+| `ab_cat_confirm_cancel` | Confirmer     | `ab_pb_confirm`            | OPEN_APP, URI ou DEEP_LINK |
+| `ab_cat_confirm_cancel` | Annuler      | `ab_pb_cancel`             | FERMER                   |
+| `ab_cat_more`           | Plus        | `ab_pb_more`               | OPEN_APP, URI ou DEEP_LINK |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+```json
+{
+  "action_id": (required, string) the button's action identifier,
+  "action": (optional, string) one of "OPEN_APP", "URI", "DEEP_LINK", or "CLOSE". Defaults to either "OPEN_APP" or "CLOSE" depending on the button,
+  "uri": (optional, string) a web URL or Deep Link URI,
+  "use_webview": (optional, boolean) whether to open the web URL inside the app if the action is "URI", defaults to true
+}
+```
+
+### Objet Boutons d’action de notification push Apple pour les catégories définies par votre application
+
+```json
+{
+  "action_id": (required, string) the button's action identifier,
+  "action": (required, string) one of "URI" or "DEEP_LINK",
+  "uri": (required, string) a web URL or Deep Link URI,
+  "use_webview": (optional, boolean) whether to open the web URL inside the app if the action is "URI", defaults to true
+}
+```
diff --git a/_lang/fr_fr/_api/objects_filters/messaging/content_cards_object.md b/_lang/fr_fr/_api/objects_filters/messaging/content_cards_object.md
new file mode 100644
index 00000000000..69430e8b5f4
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging/content_cards_object.md
@@ -0,0 +1,38 @@
+---
+nav_title: "Objet Carte de contenu"
+article_title: Objet Messagerie de la carte de contenu
+page_order: 4
+page_type: reference
+channel: content cards
+description: "Cet article de référence explique les différents composants de l’objet Carte de contenu de Braze."
+
+---
+
+# Objet Carte de contenu
+
+> L'objet `content_card` vous permet de créer des cartes de contenu par l'intermédiaire de nos [points d'envoi de messages.]({{site.baseurl}}/api/endpoints/messaging)
+
+```json
+{
+  "type": (required, string) one of "CLASSIC", "CAPTIONED_IMAGE", or "BANNER",
+  "title": (required, string) the card's title,
+  "description": (required, string) the card's description,
+  "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under (must be a Content Card Message),
+  "pinned": (optional, boolean) whether the card is pinned. Defaults to false,
+  "image_url": (optional, string) the card's image URL. Required for "CAPTIONED_IMAGE" and "BANNER",
+  "time_to_live": (optional, integer) the number of seconds before the card expires. You must include either "time_to_live" or "expire_at",
+  "expire_at": (optional, string) ISO 8601 date when the card expires. You must include either "time_to_live" or "expire_at", a maximum expiration time exists of 30 days,
+  "expire_in_local_time": (optional, boolean) if using "expire_at", determines whether the card should expire in users' local time. Defaults to false,
+  "ios_uri": (optional, string) a web URL, or Deep Link URI,
+  "android_uri": (optional, string) a web URL, or Deep Link URI,
+  "web_uri": (optional, string) a web URL, or Deep Link URI,
+  "ios_use_webview": (optional, boolean) whether to open the web URL inside the app, defaults to true,
+  "android_use_webview": (optional, boolean) whether to open the web URL inside the app, defaults to true,
+  "uri_text": (optional, string) the card's link text,
+  "extra": (optional, object) additional keys and values sent with the card,
+}
+```
+
+{% alert important %}
+Actuellement, Braze prend en charge une durée d’expiration maximale de 30 jours.
+{% endalert %}
diff --git a/_lang/fr_fr/_api/objects_filters/messaging/email_object.md b/_lang/fr_fr/_api/objects_filters/messaging/email_object.md
new file mode 100644
index 00000000000..96f9677ffeb
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging/email_object.md
@@ -0,0 +1,98 @@
+---
+nav_title: "Objet E-mail"
+article_title: Objet Messagerie e-mail
+page_order: 5
+page_type: reference
+channel: email
+description: "Cet article de référence explique les différents composants de l’objet E-mail de Braze."
+
+---
+
+# Objet E-mail
+
+> L'objet `email` vous permet de modifier ou de créer des e-mails par l'intermédiaire de nos [points d'envoi de messages.]({{site.baseurl}}/api/endpoints/messaging)
+
+## Objet E-mail
+
+```json
+{
+  "app_id": (required, string), see App Identifier,
+  "subject": (optional, string),
+  "from": (required, valid email address in the format "Display Name <email@address.com>"),
+  "reply_to": (optional, valid email address in the format "email@address.com" - defaults to your workspace's default reply to if not set) - use "NO_REPLY_TO" to set reply-to address to null,
+  "bcc": (optional, one of the BCC addresses defined in your workspace's email settings) if provided and the BCC feature is enabled for your account, this address will get added to your outbound message as a BCC address,
+  "body": (required unless email_template_id is given, valid HTML),
+  "plaintext_body": (optional, valid plaintext, defaults to autogenerating plaintext from "body" when this is not set),
+  "preheader": (optional*, string) recommended length 50-100 characters,
+  "email_template_id": (optional, string) if provided, we will use the subject/body/should_inline_css values from the given email template UNLESS they are specified here, in which case we will override the provided template,
+  "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under,
+  "extras": (optional, valid Key-Value Hash) extra hash - for SendGrid users, this will be passed to SendGrid as Unique Arguments,
+  "headers": (optional, valid Key-Value Hash) hash of custom extensions headers (available for SparkPost and SendGrid),
+  "should_inline_css": (optional, boolean) whether to inline CSS on the body. If not provided, falls back to the default CSS inlining value for the workspace,
+  "attachments": (optional, array) array of JSON objects that define the files you need attached, defined by "file_name" and "url",
+    "file_name": (required, string) the name of the file you want to attach to your email, excluding the extension (for example, ".pdf"). Attach files up to 2 MB. This is required if you use "attachments",
+    "url": (required, string) the corresponding URL of the file you want to attach to your email. The file name's extension will be detected automatically from the URL defined, which should return the appropriate "Content-Type" as a response header. This is required if you use "attachments",
+}
+```
+
+- [Identifiant d’application]({{site.baseurl}}/api/identifier_types/)
+- Pour plus d'informations et de bonnes pratiques sur les accroches, consultez notre article d'aide sur \[email body styling][46].
+
+{% alert warning %}
+Braze recommande d’éviter d’utiliser les liens Google Drive pour les `url` de pièces jointes, car cela peut bloquer les appels de nos serveurs pour obtenir le fichier ce qui empêche l’envoi d’e-mails.
+{% endalert %}
+
+Les types de fichiers joints valides comprennent : `txt`, `csv`, `log`, `css`, `ics`, `jpg`, `jpe`, `jpeg`, `gif`, `png`, `bmp`, `psd`, `tif`, `tiff`, `svg`, `indd`, `ai`, `eps`, `doc`, `docx`, `rtf`, `odt`, `ott`, `pdf`, `pub`, `pages`, `mobi`, `epub`, `mp3`, `m4a`, `m4v`, `wma`, `ogg`, `flac`, `wav`, `aif`, `aifc`, `aiff`, `mp4`, `mov`, `avi`, `mkv`, `mpeg`, `mpg`, `wmv`, `xls`, `xlsx`, `ods`, `numbers`, `odp`, `ppt`, `pptx`, `pps`, `key`, `zip`, `vcf` et `pkpass`.
+
+Un `email_template_id` peut être récupéré au bas des modèles d’e-mail créés avec l’éditeur HTML. Voici un exemple de ce à quoi ressemble cet ID :
+
+![Section Identifiant API d’un modèle d’e-mail HTML][31]
+
+## Exemple d’objet d’e-mail avec pièce jointe
+
+```json
+{
+  "external_user_ids": ["YOUR_EXTERNAL_USER_ID"],
+  "messages":{
+     "email":{
+        "app_id":"YOUR_APP_ID",
+        "attachments":[{
+            "file_name":"YourFileName",
+            "url":"https://exampleurl.com/YourFileName.pdf"
+         }]
+     }
+  }
+}
+```
+
+## Authentification des pièces jointes aux e-mails
+
+{% alert important %}
+L'authentification des pièces jointes aux e-mails dans cet endpoint est actuellement en accès anticipé. Contactez votre gestionnaire de compte Braze si vous souhaitez participer à l’accès anticipé.
+{% endalert %}
+
+1. Naviguez vers **Paramètres** > **Contenu connecté** et cliquez sur **Ajouter un justificatif** pour ajouter vos justificatifs d'authentification.
+2. Entrez un nom, puis ajoutez un nom d'utilisateur et un mot de passe.
+3. Dans l'objet E-mail de l’endpoint `/messages/send`, incluez une propriété `basic_auth_credential` spécifiant le nom de l’identifiant dans les détails de la pièce jointe. Reportez-vous à l'exemple suivant avec le nom d’identifiant `company_basic_auth_credential_name` :
+
+```json
+{
+  "external_user_ids": ["recipient_user_id"],
+  "messages":{
+    "email":{
+      "app_id": "153e8a29-fd6d-4f77-ade7-1a4ca08d457a",
+      "subject": "Basis auth attachement test",
+      "from": "mail <mail@e.company.com>",
+      "body": "my attachment test",
+      "attachments":[
+        { "file_name":"checkout_receipt.pdf",
+        "url":"https://fileserver.company.com/user123-checkout_receipt.pdf",
+        "basic_auth_credential": "company_basic_auth_credential_name" }
+      ]
+    }
+  }
+}
+```
+
+[31]: {% image_buster /assets/img_archive/email_template_id.png %}
+[46]: {{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/guidelines_and_tips/#body-styling
diff --git a/_lang/fr_fr/_api/objects_filters/messaging/kindle_and_fireos_object.md b/_lang/fr_fr/_api/objects_filters/messaging/kindle_and_fireos_object.md
new file mode 100644
index 00000000000..4a47e055d6b
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging/kindle_and_fireos_object.md
@@ -0,0 +1,32 @@
+---
+nav_title: "Objet Notification push Kindle et FireOS"
+article_title: Objet Messagerie de notifications push Kindle et FireOS
+page_order: 7
+page_type: reference
+channel: push
+platform:
+  - Android
+  - FireOS
+description: "Cet article de référence explique les différents composants de l'objet push de Braze Kindle et FireOS."
+
+---
+
+# Objet Notification push Kindle et FireOS
+
+> L'objet `kindle_push` vous permet de modifier ou de créer des notifications push Kindle et FireOS via nos [points d'extrémité de messages.]({{site.baseurl}}/api/endpoints/messaging)
+
+```json
+{
+   "alert": (required, string) the notification message,
+   "title": (required, string) the title that appears in the notification drawer,
+   "extra": (optional, object) additional keys and values to be sent in the push,
+   "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under (must be an Kindle/FireOS Push Message),
+   "priority": (optional, integer) the notification priority value,
+   "collapse_key": (optional, string) the collapse key for this message,
+   // Specifying "default" in the sound field will play the standard notification sound
+   "sound": (optional, string) the location of a custom notification sound within the app,
+   "custom_uri": (optional, string) a web URL, or Deep Link URI
+}
+```
+
+Le paramètre `priority` accepte les valeurs entre `-2` et `2`, où `-2` représente la priorité la plus basse et `2` la priorité la plus élevée. `0` est la valeur par défaut. Toutes les valeurs envoyées en dehors de cette plage d’entiers seront par défaut à `0`.
diff --git a/_lang/fr_fr/_api/objects_filters/messaging/sms_object.md b/_lang/fr_fr/_api/objects_filters/messaging/sms_object.md
new file mode 100644
index 00000000000..80db73ca628
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging/sms_object.md
@@ -0,0 +1,24 @@
+---
+nav_title: "Objet SMS"
+article_title: Objet Messagerie SMS
+page_order: 10
+page_type: reference
+channel: SMS
+description: "Cet article de référence explique les différents composants de l'objet SMS de Braze."
+
+---
+# Objet SMS
+
+> L'objet `sms` vous permet de modifier ou de créer des messages SMS via nos [points d'envoi de messages.]({{site.baseurl}}/api/endpoints/messaging)
+
+```json
+{
+    "subscription_group_id": (required, string) the id of your subscription group,
+    "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under,
+    "body": (required, string),
+    "app_id": (required, string) see App Identifier,
+    "media_items" :(optional, array) use this field to pass an image URL in an MMS to send an image with your message.    
+}
+```
+
+- [Identifiant d’application]({{site.baseurl}}/api/identifier_types/)
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/objects_filters/messaging/web_objects.md b/_lang/fr_fr/_api/objects_filters/messaging/web_objects.md
new file mode 100644
index 00000000000..52f5523750a
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging/web_objects.md
@@ -0,0 +1,43 @@
+---
+nav_title: "Objet Web"
+article_title: Objet Messagerie Web
+page_order: 12
+page_type: reference
+channel: push
+platform: Web
+description: "Cet article de référence répertorie et explique les différents objets Web utilisés chez Braze."
+
+---
+# Objet Notification push Web
+
+> L'objet `web_push` vous permet de définir ou de demander des informations relatives au contenu de web push et d'alertes web push via nos [points d'envoi de messages.]({{site.baseurl}}/api/endpoints/messaging)
+
+## Objet Notification push Web
+
+```json
+{
+   "alert": (required, string) the notification message,
+   "title": (required, string) the title that appears in the notification drawer,
+   "extra": (optional, object) additional keys and values to be sent in the push,
+   "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under (must be an Kindle/FireOS Push Message),
+   "custom_uri": (optional, string) a web URL,
+   "image_url": (optional, string) URL for image to show,
+   "large_image_url": (optional, string) URL for large image, supported on Chrome Windows/Android,
+   "require_interaction": (optional, boolean) whether to require the user to dismiss the notification, supported on Mac Chrome,
+   "time_to_live": (optional, integer (seconds)),
+   "send_to_most_recent_device_only" : (optional, boolean) defaults to false, if set to true, Braze will only send this push to a user's most recently used browser, rather than all eligibles browsers,
+   "buttons" : (optional, array of Web push action button objects) push action buttons to display
+}
+```
+
+La valeur de `image_url` doit être une URL qui renvoie à l’emplacement où votre image est hébergée. Les images doivent être recadrées selon un rapport hauteur/largeur 1:1.
+
+## Objet Bouton d’action push Web
+
+```json
+{
+  "text": (required, string) the button's text,
+  "action": (optional, string) one of "OPEN_APP", "URI", or "CLOSE", defaults to "OPEN_APP",
+  "uri": (optional, string) a web URL
+}
+```
diff --git a/_lang/fr_fr/_api/objects_filters/messaging/webhook_object.md b/_lang/fr_fr/_api/objects_filters/messaging/webhook_object.md
new file mode 100644
index 00000000000..bf06ee11f4a
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging/webhook_object.md
@@ -0,0 +1,26 @@
+---
+nav_title: "Objet Webhook"
+article_title: Objet Messagerie Webhook
+page_order: 13
+page_type: reference
+channel: 
+  - webhook
+description: "Cet article de référence présente l’objet Webhook de Braze."
+
+---
+
+# Objet Webhook
+
+> L'objet `webhook` vous permet de modifier ou de créer des messages webhook via nos [points d'envoi de messages.]({{site.baseurl}}/api/endpoints/messaging)
+
+```json
+{
+  "url": (required, string),
+  "request_method": (required, string) one of "POST", "PUT", "DELETE", or "GET",
+  "request_headers": (optional, Hash) key-value pairs to use as request headers,
+  "body": (optional, string) if you want to include a JSON object, make sure to escape quotes and backslashes,
+  "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under
+}
+```
+
+L’une des bonnes pratiques recommandées par Braze est de fournir une valeur explicite pour `Content-Type` dans le champ `request_headers` afin de garantir un comportement cohérent et prévisible, car les expéditeurs et les serveurs peuvent changer au fil du temps. Si aucune valeur n’est spécifiée pour l’en-tête `Content-Type`, elle sera déduite du corps de la requête.
diff --git a/_lang/fr_fr/_api/objects_filters/messaging/whats_app_object.md b/_lang/fr_fr/_api/objects_filters/messaging/whats_app_object.md
new file mode 100644
index 00000000000..cb3fdfeca06
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/messaging/whats_app_object.md
@@ -0,0 +1,173 @@
+---
+nav_title: "Objet WhatsApp"
+article_title: Objet Envoi de messages WhatsApp
+page_order: 15
+page_type: reference
+channel: WhatsApp
+description: "Cet article de référence explique les différents composants de l’objet Braze WhatsApp."
+
+---
+
+# Objet WhatsApp
+
+> L'objet `whats_app` vous permet de modifier ou de créer des messages WhatsApp via nos [points d'extrémité de messagerie.]({{site.baseurl}}/api/endpoints/messaging)
+
+## Objet WhatsApp
+
+```json
+{
+  "app_id": (required, string) see App Identifier,
+  "subscription_group_id": (required, string) the ID of your subscription group,
+  "message_variation_id": (optional, string) used when providing a campaign_id to specify which message variation this message should be tracked under,
+  "message_type": (required, string) the type of WhatsApp message being sent under the `message` key (template_message | text_response_message | text_image_response_message | quick_reply_response_message),
+  "message": (required, object) message object specifying fields the required fields based on the specified message_type. See Message Types for field specifications.
+}
+```
+
+- [Identifiant d’application]({{site.baseurl}}/api/identifier_types/)
+
+### Types de messages
+
+#### template_message
+
+```json
+{
+  "template_name": (required, string) the WhatsApp template name for the message,
+  "template_language_code": (required, string) the language code of the WhatsApp template for the message,
+  "header_variables": (optional, header variables object) an object to specify header variable values for specified template_name, required if the header has variables; see object specification below,
+  "body_variables": (optional, body variable object) an object to specify body variable values for specified template_name, required if the body has variables; see object specification below,
+  "button_variables": (optional, button variables object) an object to specify button variable values for specified template_name, required if buttons have variables; see object specification below,
+  "header_image_uri" :(optional, string) URI to the header image, if the header is of type IMAGE in specified template_name
+}
+```
+
+##### Objet Variables d'en-tête
+
+L’objet `header_variables` vous permet de spécifier des valeurs pour les variables d’en-tête dans le modèle WhatsApp. Chaque clé est l’index de variable du modèle WhatsApp (indexé à zéro) à remplacer par la valeur spécifiée.
+
+```json
+{
+  "$TEMPLATE_VARIABLE_INDEX_0": "$TEMPLATE_VARIABLE_VALUE_0"
+}
+```
+Actuellement, seuls zéro ou une variable d'en-tête peuvent être spécifiés.
+
+
+###### Exemple
+
+```json
+{
+  "0": "Check it out!"
+}
+```
+
+##### Objet Variables du corps
+
+L’objet `body_variables` vous permet de spécifier des valeurs pour les variables du corps dans le modèle WhatsApp. Chaque clé est l’index de variable du modèle WhatsApp (indexé à zéro) à remplacer par la valeur spécifiée.
+```json
+{
+  "$TEMPLATE_VARIABLE_INDEX_0": "$TEMPLATE_VARIABLE_VALUE_0",
+  "$TEMPLATE_VARIABLE_INDEX_1": "$TEMPLATE_VARIABLE_VALUE_1"
+}
+```
+
+###### Exemple
+
+```json
+{
+  "0": "Check it out!",
+  "1": "It's pretty neat."
+}
+```
+
+##### Objet Variables de bouton
+
+L’objet `button_variables` vous permet de spécifier des valeurs pour les variables du bouton dans le modèle WhatsApp. Chaque clé est l’index de variable du modèle WhatsApp (indexé à zéro) à remplacer par la valeur spécifiée.
+
+```json
+{
+  "$TEMPLATE_VARIABLE_INDEX_1": "$TEMPLATE_VARIABLE_VALUE_1",
+}
+```
+
+Actuellement, une seule variable de bouton peut être spécifiée, à savoir le composant de chemin d’une URL d’appel à l’action. L’index de variable doit correspondre à l’index du bouton d’URL CTA dans le modèle. Par exemple, si votre bouton CTA est le deuxième bouton de votre modèle, utilisez l’index de variable « 1 ».
+
+###### Exemple
+
+```json
+{
+  "1": "/marketing/promotion123"
+}
+```
+
+#### text_response_message
+
+```json
+{
+  "body": (required, string) the body of the message to send,
+  "preview_url": (optional, boolean) whether WhatsApp should render a preview of links included in body
+}
+```
+
+###### Exemple
+
+```json
+{
+  "body": "Check out our new deals at https://braze.com",
+  "preview_url": true
+}
+```
+
+#### text_image_response_message
+
+```json
+{
+  "image_uri": (required, string) the uri of the image to send,
+  "caption": (optional, string) the caption for the image being sent
+}
+```
+
+###### Exemple
+
+```json
+{
+  "image_uri": "https://braze.com/promotion.jpg",
+  "caption": "This won't last for long, check it out!"
+}
+```
+
+#### quick_reply_response_message
+
+```json
+{
+  "body": (required, string) the body of the message to send,
+  "header_image_uri": (optional, string) the URI of the image to send as the message header (only valid if header_text not present),
+  "header_text": (optional, string) the text to send as the message header (only valid if header_image_uri not present),
+  "footer": (optional, string) the footer of the message to send,
+  "buttons": (required, array) array of Button objects. Will render in message based on order in array.
+}
+```
+
+##### Objet bouton
+
+```json
+{
+  "text": (required, string) the text of the button
+}
+```
+
+###### Exemple
+
+```json
+{
+  "body": "Want to keep hearing from us?",
+  "buttons": [
+    {
+      "text": "Yes!"
+    },
+    {
+      "text": "No thanks"
+    }
+  ]
+}
+```
diff --git a/_lang/fr_fr/_api/objects_filters/purchase_object.md b/_lang/fr_fr/_api/objects_filters/purchase_object.md
new file mode 100644
index 00000000000..91f7c2e2067
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/purchase_object.md
@@ -0,0 +1,177 @@
+---
+nav_title: "Objet d’achat"
+article_title: Objet Achat de l’API
+page_order: 8
+page_type: reference
+description: "Cet article de référence explique les différents composants d’un objet Achat, comment l’utiliser correctement et des exemples dont vous pouvez vous inspirer."
+
+---
+
+# Objet Achat
+
+> Cet article explique les différents composants d’un objet Achat, comment l’utiliser correctement, les bonnes pratiques et des exemples dont vous pouvez vous inspirer.
+
+## Qu’est-ce qu’un objet Achat ?
+
+Un objet Achat est un objet qui passe par l’API lorsqu’un achat a été effectué. Chaque objet Achat est situé dans un tableau d’achat, chaque objet représentant un seul achat par un utilisateur particulier à un moment donné. L’objet Achat possède de nombreux champs différents qui permettent au backend de Braze de stocker et d’utiliser ces informations pour la personnalisation et la collecte des données.
+
+### Corps de l’objet
+
+```json
+{
+  // One of "external_id" or "user_alias" or "braze_id" or "email" is required.
+  "external_id" : (optional, string) External user ID,
+  "user_alias" : (optional, User Alias Object) User alias object,
+  "braze_id" : (optional, string) Braze user identifier,
+  "email": (optional, string) User email address,
+  "app_id" : (optional, string) see App Identifier,
+  // See the following product_id naming conventions for clarification.
+  "product_id" : (required, string) identifier for the purchase, for example, Product Name or Product Category,
+  "currency" : (required, string) ISO 4217 Alphabetic Currency Code,
+  //Revenue from a purchase object is calculated as the product of quantity and price.
+  "price" : (required, float) value in the base currency unit (for example, Dollars for USD, Yen for JPY),
+  "quantity" : (optional, integer) the quantity purchased (defaults to 1, must be <= 100 -- currently, Braze treats a quantity _X_ as _X_ separate purchases with quantity 1),
+  "time" : (required, datetime as string in ISO 8601) Time of purchase,
+  // See the following purchase object explanation for clarification.
+  "properties" : (optional, Properties Object) properties of the event,
+  // Setting this flag to true will put the API in "Update Only" mode.
+  // When using a "user_alias", "Update Only" mode is always true.
+  "_update_existing_only" : (optional, boolean)
+}
+```
+
+- [ID utilisateur externe]({{site.baseurl}}/api/basics/#user-ids)
+- [Identifiant d’application]({{site.baseurl}}/api/identifier_types/)
+- [ISO 4217 Code des devises Wiki][20]
+- [ISO 8601 Time Code Wiki][22]
+
+## Identifiant product_id pour l’achat
+
+Dans l'objet Achat, le `product_id` est un identifiant pour l'achat (tel que `Product Name` ou `Product Category`) :
+
+- Braze vous permet de stocker jusqu'à 5 000 `product_id` dans le tableau de bord.
+- Le site `product_id` peut contenir jusqu'à 255 caractères.
+
+### Conventions de nommage des ID de produit
+
+Chez Braze, nous proposons des conventions générales de nommage pour l’objet Achat `product_id`. Lorsque vous choisissez `product_id`, Braze suggère d’utiliser des noms simples tels que le nom du produit ou la catégorie de produit (au lieu des unités de gestion des stocks) dans l’intention de regrouper tous les éléments enregistrés par ce `product_id`.
+
+Cela permet de faciliter l’identification des produits pour la segmentation et le déclenchement.
+
+### Journaliser les achats au niveau de la commande
+
+Si vous souhaitez enregistrer les achats au niveau de la commande plutôt qu'au niveau du produit, vous pouvez utiliser le nom de la commande ou la catégorie de commande comme `product_id` (par exemple `Online Order` ou `Completed Order`).
+
+Par exemple, pour enregistrer des achats au niveau de la commande dans le SDK Web :
+
+```html
+POST https://YOUR_REST_API_URL/users/track
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "purchases" : [
+    {
+      "external_id" : "user1",
+      "app_id" : "11ae5b4b-2445-4440-a04f-bf537764c9ad",
+      "product_id" : "Completed Order",
+      "currency" : "USD",
+      "price" : 219.98,
+      "time" : "2013-07-16T19:20:30+01:00",
+      "properties" : {
+        "products" : [ { "name": "Monitor", "category": "Gaming", "product_amount": 19.99, },
+        { "name": "Gaming Keyboard", "category": "Gaming ", "product_amount": 199.99, }
+        ]
+      }
+    }
+  ]
+}
+```
+
+## Objet Propriétés d’achat
+
+Les événements et achats personnalisés peuvent avoir des propriétés d’événement. Les valeurs des « Properties (Propriétés) » doivent être un objet dont les clés sont les noms de propriétés et les valeurs sont les valeurs de propriété. Les noms de propriété doivent être des chaînes de caractères non vides de moins de 255 caractères, qui ne commencent pas par un symbole de dollar. 
+
+Les valeurs de propriété peuvent être l’un des types de données suivants :
+
+| Type de données | Description |
+| --- | --- |
+| Chiffres | Sous forme d'[entiers](https://en.wikipedia.org/wiki/Integer) ou de [float](https://en.wikipedia.org/wiki/Floating-point_arithmetic) |
+| Booléens |  |
+| Datetimes | Formatés sous forme de chaînes de caractères au format [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) ou `yyyy-MM-dd'T'HH:mm:ss:SSSZ`. Non pris en charge dans les tableaux. |
+| Chaînes de caractères | 255 caractères ou moins. |
+| Tableaux | Les tableaux ne peuvent pas inclure des dates/horodatages. |
+| Objets | Les objets seront ingérés en tant que chaînes de caractères. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+Les objets de propriété d'événement qui contiennent des valeurs de tableau ou d'objet peuvent avoir une charge utile de propriété d'événement allant jusqu'à 50 Ko.
+
+### Propriétés d’achat
+
+Les [propriétés d'achat]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/#purchase-properties) peuvent être utilisées pour déclencher des messages et pour la personnalisation à l'aide de Liquid, ce qui vous permet également de segmenter en fonction de ces propriétés.
+
+### Conventions de nommage des propriétés d’achat
+
+Il est important de noter que cette fonctionnalité est activée **par produit**, et non par achat. Par exemple, si un client possède un grand nombre de produits distincts, mais que chacun d'entre eux possède les mêmes propriétés, la segmentation n'a plus beaucoup de sens.
+
+C’est pourquoi, dans ce cas, nous vous recommandons d’utiliser les noms de produits au « niveau du groupe », plutôt que quelque chose de granulaire lors de la définition des structures de données. Par exemple, une société de vente de billets de train devrait avoir des produits pour "voyage simple", "voyage aller-retour", "multi-villes", et non des transactions spécifiques telles que la "transaction 123" ou la "transaction 046". Par exemple, pour l'événement d'achat "nourriture", il serait préférable que les propriétés soient "gâteau" et "sandwich".
+
+### Exemple d’objet Achat
+```html
+POST https://YOUR_REST_API_URL/users/track
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "purchases" : [
+    {
+      "external_id" : "user1",
+      "app_id" : "11ae5b4b-2445-4440-a04f-bf537764c9ad",
+      "product_id" : "backpack",
+      "currency" : "USD",
+      "price" : 40.00,
+      "time" : "2013-07-16T19:20:30+01:00",
+      "properties" : {
+        "color" : "red",
+        "monogram" : "ABC",
+        "checkout_duration" : 180,
+        "size" : "Large",
+        "brand" : "Backpack Locker"
+      }
+    },
+    {
+      "external_id" : "user1",
+      "app_id" : "11ae5b4b-2445-4440-a04f-bf537764c9ad",
+      "product_id" : "pencil",
+      "currency" : "USD",
+      "price" : 2.00,
+      "time" : "2013-07-17T19:20:20+01:00",
+      "properties" : {
+        "number" : 2,
+        "sharpened" : true
+      }
+    },
+    {
+      "user_alias" : { "alias_name" : "device123", "alias_label" : "my_device_identifier"},
+      "app_id" : "11ae5b4b-2445-4440-a04f-bf537764c9ad",
+      "product_id" : "pen",
+      "currency" : "USD",
+      "price" : 2.50,
+      "time" : "2013-07-17T19:20:20+01:00",
+      "properties" : {
+        "color" : "blue",
+      }
+    }
+  ]
+}
+```
+
+## Objets Achat, objets d’événement et webhooks
+
+À l’aide de l’exemple fourni, nous pouvons voir que quelqu’un a acheté un sac à dos avec les propriétés : couleur, monogramme, durée d’achat, taille et marque. Nous pouvons ensuite créer des segments avec ces propriétés en utilisant les [propriétés d'event d'achat][2] ou envoyer des messages personnalisés par le biais d'un canal à l'aide de Liquid. Par exemple, « Bonjour **Ann F.**, merci d'avoir acheté ce **sac à dos rouge de taille moyenne** pour **40 euros** ! Merci d'avoir acheté chez **Backpack Locker**!"
+
+Si vous souhaitez enregistrer, stocker et suivre les propriétés avec lesquelles segmenter, vous devez les configurer comme attributs personnalisés. Pour ce faire, vous pouvez utiliser les [extensions de segments]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/), qui vous permettent de cibler les utilisateurs en fonction d'un événement personnalisé ou d'un comportement d'achat stocké pendant toute la durée de vie de ce profil utilisateur.
+
+[2]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/#purchase-properties
+[20]: http://en.wikipedia.org/wiki/ISO_4217 "Code devise ISO 4217"
+[21]: {{site.baseurl}}/api/api_key/#the-app-identifier-api-key
+[22]: https://en.wikipedia.org/wiki/ISO_8601 "Code temporel ISO 8601"
+[23]: {{site.baseurl}}/api/basics/#external-user-id-explanation
diff --git a/_lang/fr_fr/_api/objects_filters/recipient_object.md b/_lang/fr_fr/_api/objects_filters/recipient_object.md
new file mode 100644
index 00000000000..2d530f636af
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/recipient_object.md
@@ -0,0 +1,43 @@
+---
+nav_title: "Objet Destinataire"
+article_title: Objet Destinataire de l’API
+page_order: 9
+page_type: reference
+description: "Cet article de référence explique les différents composants de l’objet Destinataire Braze."
+
+---
+
+# Objet Destinataire
+
+> L’objet Destinataire vous permet de demander ou d’écrire des informations dans nos endpoints.
+
+`external_user_id` ou `user_alias` est requis dans cet objet. **Les demandes ne doivent en spécifier qu’un seul des deux.**
+
+L'objet destinataire vous permet de combiner l'[objet alias d'utilisateur]({{site.baseurl}}/api/objects_filters/user_alias_object/), l'[objet propriétés du déclencheur]({{site.baseurl}}/api/objects_filters/trigger_properties_object/) et l'[objet propriétés de l'entrée dans le canvas.]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/)
+
+## Corps de l’objet
+
+```json
+[{
+  "user_alias": (optional, User Alias Object) User alias of user to receive message,
+  "external_user_id": (optional, string) see External user ID,
+  "trigger_properties": (optional, object) personalization key-value pairs for this user when sending a campaign or message; see Trigger Properties,
+  "canvas_entry_properties": (optional, object) personalization key-value pairs for this user when triggering a Canvas; see Canvas Entry Properties
+}]
+```
+
+- [Alias utilisateurs]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases)
+- [ID utilisateur externe]({{site.baseurl}}/api/objects_filters/user_attributes_object/#braze-user-profile-fields)
+
+## Déduplication d’objet Destinataire
+
+Lorsque vous effectuez un appel d’API avec l’objet Destinataire, **s’il existe un destinataire dupliqué ciblant la même adresse (par ex. e-mail, notification push), l’utilisateur sera dédupliqué**, ce qui signifie que les utilisateurs identiques seront supprimés. Il n’en restera qu’un. 
+
+Par exemple, si le même `external_user_id` est utilisé, un seul message sera reçu. Envisagez de faire plusieurs appels à l'API si vous avez besoin d'une solution de contournement pour ce comportement.
+
+```json
+{"campaign_id":"#####","recipients":[
+{"external_user_id":"userid1","trigger_properties":{"name":"Beth Test 1"}},
+{"external_user_id":"userid1","trigger_properties":{"name":"Beth Test 2"}} 
+]}
+```
\ No newline at end of file
diff --git a/_lang/fr_fr/_api/objects_filters/schedule_object.md b/_lang/fr_fr/_api/objects_filters/schedule_object.md
new file mode 100644
index 00000000000..65d3d326ac6
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/schedule_object.md
@@ -0,0 +1,46 @@
+---
+nav_title: "Objet Planification"
+article_title: Objet Planification API
+page_order: 12
+page_type: reference
+description: "Cet article de référence répertorie et explique l’objet Planification différent utilisé chez Braze."
+
+---
+
+# Objet Planification
+
+> Les paramètres des points de terminaison de la campagne et de la création de la planification Canvas reflètent ceux du point de terminaison d'envoi et ajoutent le paramètre `schedule`, qui vous permet de spécifier le moment où vous souhaitez que les utilisateurs ciblés reçoivent votre message. Si vous incluez uniquement le paramètre `time` dans l’objet `schedule`, tous vos utilisateurs recevront des messages à ce moment-là.
+
+Si vous définissez `in_local_time` sur `true`, vous obtiendrez une réponse d’erreur si le paramètre Time est passé dans tous les fuseaux horaires. Si vous attribuez la valeur "true" à `at_optimal_time`, vos utilisateurs recevront le message à la date désignée et à l'heure optimale (quelle que soit l'heure que vous avez indiquée). Lorsque vous utilisez l'envoi de l'heure locale ou optimale, n'indiquez pas les désignateurs de fuseaux horaires dans la valeur du paramètre de temps (par exemple, utilisez `"2015-02-20T13:14:47"` au lieu de `"2015-02-20T13:14:47-05:00"`).
+
+La réponse vous fournira un `schedule_id` que vous devez enregistrer au cas où vous auriez ultérieurement besoin d’annuler ou de mettre à jour le message que vous planifiez :
+
+## Corps de l’objet
+
+Insérez cet objet si nécessaire pour planifier vos messages.
+
+```json
+"schedule": {
+  "time": (required, datetime as ISO 8601 string) time to send the message in UTC,
+  "in_local_time": (optional, bool),
+  "at_optimal_time": (optional, bool),
+}
+```
+
+## Réponse de l’ID de planification
+
+Vous recevrez un `schedule_id` pour le message planifié que vous avez créé.
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "schedule_id" : (required, string) identifier for the scheduled message that was created
+}
+```
+
+Si vous utilisez l'API pour des appels de serveur à serveur, il se peut que vous deviez ajouter à votre liste blanche l’URL d’API appropriée si vous travaillez derrière un pare-feu.
+
+Les réponses des endpoints de planification des messages incluront le `dispatch_id` du message pour y faire référence lors de l’envoi. Le `dispatch_id` est l’identifiant de la transmission du message (ID unique pour chaque « dispatch » envoyé par Braze).
+
+[33]: {{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_timing/
diff --git a/_lang/fr_fr/_api/objects_filters/trigger_properties_object.md b/_lang/fr_fr/_api/objects_filters/trigger_properties_object.md
new file mode 100644
index 00000000000..846fbb30894
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/trigger_properties_object.md
@@ -0,0 +1,40 @@
+---
+nav_title: "Objet Propriétés du déclencheur"
+article_title: Objet Propriétés du déclencheur de l’API
+page_order: 11
+page_type: reference
+description: "Cet article de référence explique les différents composants de l’objet Propriétés du déclencheur."
+tool: Campaigns
+
+---
+
+# Objet Propriétés du déclencheur
+
+> Lorsque vous utilisez l’un des endpoints pour envoyer une campagne avec une livraison déclenchée par API, vous pouvez fournir un mappage de clés et des valeurs pour personnaliser votre message.
+
+Si vous faites une demande API qui contient un objet dans `trigger_properties`, les valeurs de cet objet peuvent alors être référencées dans votre modèle de message sous l’espace de nom `api_trigger_properties`. Par exemple, une demande contenant les éléments suivants pourrait ajouter le mot `"shoes"` à un message en ajoutant {% raw %}`{{api_trigger_properties.${product_name}}}`{% endraw %}.
+
+{% alert note %}
+L'objet `trigger_properties` et la syntaxe {% raw %}`api_trigger_properties.${product_name}`{% endraw %} ne sont pris en charge que dans les campagnes. Pour personnaliser les messages avec des clés et des valeurs à partir d’une requête de déclenchement par l’API pour Canvas, utilisez l’[objet de propriétés d’entrées de Canvas]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/). La taille maximale de l'objet `trigger_properties` est de 50 ko.
+{% endalert %}
+
+## Corps de l’objet
+
+```json
+{
+  "trigger_properties" : {
+    "product_name" : "shoes",
+    "product_price" : 79.99,
+    "details" : {
+      "color" : "red",
+      "size" : {
+        "numerical" : 10,
+        "country" : "US"
+      }
+    },
+    "related_skus": ["123", "456", "789"]
+  }
+}
+```
+
+
diff --git a/_lang/fr_fr/_api/objects_filters/user_alias_object.md b/_lang/fr_fr/_api/objects_filters/user_alias_object.md
new file mode 100644
index 00000000000..64776fe1b6f
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/user_alias_object.md
@@ -0,0 +1,26 @@
+---
+nav_title: "Objet alias utilisateur"
+article_title: Objet Alias utilisateur API
+page_order: 11
+page_type: reference
+description: "Cet article de référence explique les différents composants de l’objet Alias utilisateur."
+
+---
+
+# Objet Alias utilisateur
+
+> Un alias sert d’identifiant utilisateur unique alternatif. En utilisant un objet alias utilisateur, vous pouvez définir un identifiant cohérent pour les analyses qui suivra un utilisateur donné avant et après qu'il se soit connecté à une application mobile ou à un site web. Vous pouvez également utiliser cet objet pour ajouter les identifiants utilisés par un fournisseur tiers à vos utilisateurs Braze afin de concilier plus facilement vos données en externe.
+
+L’objet Alias utilisateur se compose de deux parties : un `alias_name` pour l’identifiant lui-même et un `alias_label` indiquant le type d’alias. Les utilisateurs peuvent avoir plusieurs alias avec différentes étiquettes, mais seulement un `alias_name` par `alias_label`.
+
+Cet objet est fréquemment utilisé dans tous nos endpoints, et souvent dans d’autres objets.
+
+## Corps de l’objet
+```json
+{
+  "user_alias" : {
+    "alias_name" : (required, string),
+    "alias_label" : (required, string)
+  }
+}
+```
diff --git a/_lang/fr_fr/_api/objects_filters/user_attributes_object.md b/_lang/fr_fr/_api/objects_filters/user_attributes_object.md
new file mode 100644
index 00000000000..7024e686f56
--- /dev/null
+++ b/_lang/fr_fr/_api/objects_filters/user_attributes_object.md
@@ -0,0 +1,178 @@
+---
+nav_title: "Objet Attributs d’utilisateur"
+article_title: Objet Attributs d’utilisateur de l’API
+page_order: 11
+page_type: reference
+description: "Cet article de référence explique les différents composants de l’objet Attributs d’utilisateur."
+
+---
+
+# Objet Attributs d’utilisateur
+
+> Une demande API contenant l’un des champs de l’objet Attributs créera ou mettra à jour un attribut de ce nom avec la valeur donnée sur le profil utilisateur spécifié. 
+
+Utilisez les noms des champs du profil utilisateur de Braze (énumérés ci-dessous ou dans la section relative aux [champs du profil utilisateur de Braze][27]) pour mettre à jour ces valeurs spéciales sur le profil utilisateur dans le tableau de bord ou pour ajouter vos propres données d'attribut personnalisé à l'utilisateur.
+
+## Corps de l’objet
+
+```json
+{
+  // One of "external_id" or "user_alias" or "braze_id" or "email" is required
+  "external_id" : (optional, string) see external user ID,
+  "user_alias" : (optional, User alias object),
+  "braze_id" : (optional, string) Braze user identifier,
+  "email": (optional, string) User email address,
+  // Setting this flag to true will put the API in "Update Only" mode.
+  // When using a "user_alias", "Update Only" defaults to true.
+  "_update_existing_only" : (optional, boolean),
+  // See note regarding anonymous push token imports
+  "push_token_import" : (optional, boolean),
+  // Braze User Profile Fields
+  "first_name" : "Jon",
+  "email" : "bob@example.com",
+  // Custom Attributes
+  "my_custom_attribute" : value,
+  "my_custom_attribute_2" : {"inc" : int_value},
+  "my_array_custom_attribute":[ "Value1", "Value2" ],
+  // Adding a new value to an array custom attribute
+  "my_array_custom_attribute" : { "add" : ["Value3"] },
+  // Removing a value from an array custom attribute
+  "my_array_custom_attribute" : { "remove" : [ "Value1" ]},
+}
+```
+
+- [ID utilisateur externe]({{site.baseurl}}/api/objects_filters/user_attributes_object/#braze-user-profile-fields)
+- [Alias utilisateurs]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#user-aliases)
+
+Pour supprimer un attribut de profil, définissez-le sur `null`. Certains champs, tels que `external_id` et `user_alias`, ne peuvent pas être supprimés après avoir été ajoutés à un profil utilisateur.
+
+#### Mettre à jour les profils existants uniquement
+
+Si vous souhaitez mettre à jour uniquement les profils utilisateur existants dans Braze, vous devez passer la clé `_update_existing_only` avec la valeur `true` dans le corps de votre demande. Si cette valeur est omise, Braze créera un nouveau profil utilisateur si `external_id` n’existe pas déjà.
+
+{% alert note %}
+Si vous créez un profil utilisateur alias uniquement via l'endpoint `/users/track`, `_update_existing_only` doit être défini sur `false`. Si cette valeur est omise, le profil alias uniquement ne sera pas créé.
+{% endalert %}
+
+#### Importation de jetons de notification push
+
+Avant d’importer des jetons de notification push à Braze, vérifiez si cela est nécessaire. Lorsque les SDK de Braze sont mis en place, ils gèrent automatiquement les jetons de poussée sans qu'il soit nécessaire de les télécharger via l'API.
+
+Si vous devez les télécharger via l'API, vous pouvez le faire pour des utilisateurs identifiés ou anonymes. Cela signifie que soit un `external_id` doit être présent, soit les utilisateurs anonymes doivent avoir l’indicateur `push_token_import` défini sur `true`. 
+
+{% alert note %}
+Lors de l’importation de jetons de notification push provenant d’autres systèmes, un `external_id` n’est pas toujours disponible. Pour maintenir la communication avec ces utilisateurs pendant votre transition vers Braze, vous pouvez importer les jetons existants pour les utilisateurs anonymes sans fournir `external_id`, en spécifiant `push_token_import` comme `true`.
+{% endalert %}
+
+Lorsque vous indiquez `push_token_import` comme `true` :
+
+* `external_id` et `braze_id` **ne** doivent **pas** être spécifiés
+* L'objet d'attribut **doit** contenir un jeton de poussée.
+* Si le jeton existe déjà dans Braze, la demande est ignorée ; sinon, Braze créera un profil utilisateur temporaire et anonyme pour chaque jeton pour vous permettre de continuer à envoyer des messages à ces personnes
+
+Après l’importation, lorsque chaque utilisateur lance la version compatible Braze de votre application, Braze déplace automatiquement leur jeton de notification push importé vers leur profil utilisateur Braze et efface le profil temporaire.
+
+Braze vérifiera une fois par mois s’il existe des profils anonymes avec l’indicateur `push_token_import` qui n’ont pas de jeton de notification push. Si le profil anonyme n’a plus de jeton de notification push, nous le supprimerons. Cependant, si le profil anonyme a toujours un jeton de notification push, indiquant que l’utilisateur ne s’est pas encore connecté à l’appareil avec le jeton de notification push, nous ne ferons rien.
+
+Pour plus d'informations, consultez [Migration des jetons Push][3].
+
+#### Types de données des attributs personnalisés
+
+Les types de données suivants peuvent être stockés en tant qu’attribut personnalisé :
+
+| Type de données | Remarques |
+| --- | --- |
+| Tableaux | Les tableaux d’attributs personnalisés sont des ensembles unidimensionnels ; les tableaux multidimensionnels ne sont pas pris en charge. L’ajout d’un élément à un tableau d’attribut personnalisé ajoute l’élément à la fin du tableau, à moins qu’il ne soit déjà présent, auquel cas il passe de sa position actuelle à la fin du tableau.<br><br>Par exemple, si un tableau `['hotdog','hotdog','hotdog','pizza']` a été importé, il apparaîtra dans l’attribut de tableau comme `['hotdog', 'pizza']`, car seules des valeurs uniques sont prises en charge.<br><br>En plus de définir les valeurs d’un tableau en indiquant quelque chose comme `"my_array_custom_attribute":[ "Value1", "Value2" ]`, vous pouvez ajouter des tableaux existants en faisant quelque chose comme `"my_array_custom_attribute" : { "add" : ["Value3"] },` ou supprimer les valeurs d’un tableau en écrivant quelque chose comme `"my_array_custom_attribute" : { "remove" : [ "Value1" ]}`.<br><br>Le nombre maximum d’éléments dans les tableaux d’attributs personnalisés est par défaut de 25, mais peut être augmenté jusqu’à 100 pour un tableau donné. Pour plus d'informations, reportez-vous à la section [Tableaux][6]. |
+| Booléens | `true` ou `false` |
+| Dates | Doit être stocké dans le format [ISO 8601][19] ou dans l'un des formats suivants : <br>- `yyyy-MM-ddTHH:mm:ss:SSSZ` <br>- `yyyy-MM-ddTHH:mm:ss` <br>- `yyyy-MM-dd HH:mm:ss` <br>- `yyyy-MM-dd` <br>- `MM/dd/yyyy` <br>- `ddd MM dd HH:mm:ss.TZD YYYY` <br><br>Notez que le « T » est un indicateur de temps, et non une marque substitutive. Il ne doit pas être modifié ou supprimé. <br><br>Les attributs de temps sans fuseau horaire seront par défaut à minuit UTC (et seront formatés sur le tableau de bord comme l’équivalent de minuit UTC dans le fuseau horaire de la société). <br><br> Les événements avec des horodatages dans le futur seront par défaut à l’heure actuelle. <br><br> Pour les attributs personnalisés réguliers, si l'année est inférieure à 0 ou supérieure à 3 000, Braze stocke ces valeurs sous forme de chaînes de caractères sur l'utilisateur. |
+| Floats |  |
+| Entiers | Les attributs personnalisés entiers peuvent être incrémentés par des nombres entiers positifs ou négatifs en leur attribuant un objet avec le champ "inc" et la valeur par laquelle vous souhaitez les incrémenter. <br><br>Exemple : `"my_custom_attribute_2" : {"inc" : int_value},`|
+| Chaînes de caractères |  |
+{: .reset-td-br-1 .reset-td-br-2}
+
+Pour savoir quand vous devez utiliser un événement personnalisé plutôt qu'un attribut personnalisé, consultez nos documentations respectives sur les [événements]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/) et [attributs personnalisés]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/).
+
+#### Champs Braze User Profile (Profil d’utilisateur Braze) {#braze-user-profile-fields}
+
+{% alert important %}
+Les champs de profil utilisateur suivants sont sensibles à la casse, veillez donc à référencer ces champs en minuscule.
+{% endalert %}
+
+| Champ profil utilisateur | Spécification des types de données |
+| ---| --- |
+| nom_alias | (string) |
+| alias_label | (string) |
+| braze_id | (chaîne de caractères, facultatif) Lorsqu'un profil utilisateur est reconnu par le SDK, un profil utilisateur anonyme est créé avec une adresse `braze_id`. Le `braze_id` est automatiquement attribué par Braze, ne peut pas être modifié et est spécifique à l’appareil de l’utilisateur. | 
+| pays | (chaîne de caractères) Nous exigeons que les codes de pays soient transmis à Braze selon la [norme ISO-3166-1 alpha-2.][17] Notre API s'efforcera de mapper les pays reçus dans différents formats. Par exemple, « Australie » peut correspondre à « AU ». Cependant, si l'entrée ne correspond pas à une [norme ISO-3166-1 alpha-2][17] donnée, la valeur du pays sera définie sur `NULL`. <br><br>La définition de `country` sur un utilisateur par importation d'un CSV ou par API empêchera Braze de capturer automatiquement ces informations via le SDK. |
+| lieu_actuel | (objet) du formulaire {"longitude": -73.991443, "latitude": 40.753824} |
+| date_de_la_première_session | (date à laquelle l’utilisateur s’est servi de l’application pour la première fois) Chaîne de caractères au format ISO 8601 ou dans l’un des formats suivants : <br>- `yyyy-MM-ddTHH:mm:ss:SSSZ` <br>- `yyyy-MM-ddTHH:mm:ss` <br>- `yyyy-MM-dd HH:mm:ss` <br>- `yyyy-MM-dd` <br>- `MM/dd/yyyy` <br>- `ddd MM dd HH:mm:ss.TZD YYYY` |
+| date_de_la_dernière_session | (date à laquelle l’utilisateur s’est servi de l’application pour la dernière fois) Chaîne de caractères au format ISO 8601 ou dans l’un des formats suivants : <br>- `yyyy-MM-ddTHH:mm:ss:SSSZ` <br>- `yyyy-MM-ddTHH:mm:ss` <br>- `yyyy-MM-dd HH:mm:ss` <br>- `yyyy-MM-dd` <br>- `MM/dd/yyyy` <br>- `ddd MM dd HH:mm:ss.TZD YYYY`  |
+| ddn | (date de naissance) Chaîne de caractères au format "AAAA-MM-JJ", par exemple, 1980-12-21. |
+| e-mail | (string) |
+| abonnement aux e-mails | (chaîne de caractères) Les valeurs disponibles sont "opted_in" (explicitement inscrit pour recevoir des messages e-mail), "unsubscribed" (explicitement désinscrit des messages e-mail) et "subscribed" (ni inscrit ni désinscrit).  |
+| email_open_tracking_disabled |(booléen) `true` ou `false` accepté. Définissez ce paramètre sur `true` pour désactiver l'ajout du pixel de suivi des ouvertures dans tous les futurs e-mails envoyés à cet utilisateur.|
+| email_click_tracking_disabled |(booléen) `true` ou `false` accepté. Définissez ce champ sur `true` pour désactiver le suivi des clics pour tous les liens contenus dans un prochain e-mail envoyé à cet utilisateur.|
+| external_id | (string) Un identifiant unique pour un profil utilisateur. Après l'attribution d'un `external_id`, le profil utilisateur est identifié sur l'ensemble des appareils de l'utilisateur. Lors de la première instance d'attribution d'un identifiant externe à un profil utilisateur inconnu, toutes les données du profil utilisateur existant seront migrées vers le nouveau profil utilisateur. |
+| facebook | hachage contenant l’un des `id` (string), `likes` (array of strings), `num_friends` (integer). |
+| Prénom | (string) |
+| genre | (string) « H », « F », « A » (autre), « S/O » (sans objet), « P » (préfère ne pas dire) ou nul (inconnu). |
+| ville | (string) |
+| langue | (chaîne de caractères), nous exigeons que la langue soit transmise à Braze selon la [norme ISO-639-1.][24] Pour connaître les langues prises en charge, consultez notre [liste des langues acceptées][2].<br><br>La définition de `language` sur un utilisateur par importation d'un CSV ou par API empêchera Braze de capturer automatiquement ces informations via le SDK. |
+| Nom | (string) |
+| marked_email_as_spam_at | (chaîne de caractères) Date à laquelle l’e-mail de l’utilisateur a été marqué comme courrier indésirable. Apparaît au format ISO 8601 ou dans l’un des formats suivants : <br>- `yyyy-MM-ddTHH:mm:ss:SSSZ` <br>- `yyyy-MM-ddTHH:mm:ss` <br>- `yyyy-MM-dd HH:mm:ss` <br>- `yyyy-MM-dd` <br>- `MM/dd/yyyy` <br>- `ddd MM dd HH:mm:ss.TZD YYYY` |
+| téléphone | (string) |
+| abonnement aux notifications push | (chaîne) Les valeurs disponibles sont "opted_in" (explicitement enregistré pour recevoir des messages push), "unsubscribed" (explicitement exclu des messages push), et "subscribed" (ni in ni out).  |
+| push_tokens | Tableau d’objets avec `app_id` et la chaîne de caractères `token`. Vous pouvez éventuellement fournir un `device_id` pour l’appareil auquel ce jeton est associé, par exemple, `[{"app_id": App Identifier, "token": "abcd", "device_id": "optional_field_value"}]`. Si aucun `device_id` n’est pas fourni, il sera généré de manière aléatoire. |
+| groupes_d'abonnement| Tableau d'objets avec les chaînes de caractères `subscription_group_id` et `subscription_state`, par exemple, `[{"subscription_group_id" : "subscription_group_identifier", "subscription_state" : "subscribed"}]`. Les valeurs disponibles pour `subscription_state` sont « subscribed » (abonné) et unsubscribed » (désabonné).|
+| fuseau horaire | (chaîne de caractères) Nom du fuseau horaire provenant de la [base de données des fuseaux horaires de l'IANA][26] (par exemple, "America/New_York" ou "Eastern Time (US & Canada)"). Seules les valeurs de fuseau horaire valides seront définies. |
+| twitter | Hash contenant l'un des éléments suivants : `id` (nombre entier), `screen_name` (chaîne de caractères, identifiant X (anciennement Twitter)), `followers_count` (nombre entier), `friends_count` (nombre entier), `statuses_count` (nombre entier). |
+{: .reset-td-br-1 .reset-td-br-2}
+
+Les valeurs linguistiques définies explicitement par le biais de cette API sont prioritaires sur les informations relatives aux paramètres linguistiques que Braze reçoit automatiquement de l'appareil.
+
+####  Demande d’exemple d’attribut utilisateur
+
+Cet exemple contient deux objets Attributs utilisateur parmi les 75 autorisés par appel d’API.
+
+```json
+POST https://YOUR_REST_API_URL/users/track
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "attributes" : [
+    {
+      "external_id" : "user1",
+      "first_name" : "Jon",
+      "has_profile_picture" : true,
+      "dob": "1988-02-14",
+      "music_videos_favorited" : { "add" : [ "calvinharris-summer" ], "remove" : ["nickiminaj-anaconda"] }
+    },
+    {
+      "external_id" : "user2",
+      "first_name" : "Jill",
+      "has_profile_picture" : false,
+      "push_tokens": [{"app_id": "Your App Identifier", "token": "abcd", "device_id": "optional_field_value"}]
+
+    },
+    {
+      "user_alias" : { "alias_name" : "device123", "alias_label" : "my_device_identifier"},
+      "first_name" : "Alice",
+      "has_profile_picture" : false
+    },
+    {
+      "external_id": "user3",
+      "subscription_groups" : [{"subscription_group_id" : "subscription_group_identifier", "subscription_state" : "subscribed"}]
+    }
+  ]
+}
+```
+
+[2]: {{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/language_codes/
+[3]: {{site.baseurl}}/help/help_articles/push/push_token_migration/
+[6]: {{site.baseurl}}/developer_guide/platform_wide/analytics_overview/#arrays
+[15]: {{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/
+[17]: http://en.wikipedia.org/wiki/ISO_3166-1 "Codes ISO-3166-1"
+[19]: http://en.wikipedia.org/wiki/ISO_8601 "ISO 8601 Time Code Wiki"
+[24]: http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes "Codes ISO-639-1"
+[26]: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
+[27]: #braze-user-profile-fields
diff --git a/_lang/fr_fr/_api/postman_collection.md b/_lang/fr_fr/_api/postman_collection.md
new file mode 100644
index 00000000000..a5bbca72175
--- /dev/null
+++ b/_lang/fr_fr/_api/postman_collection.md
@@ -0,0 +1,73 @@
+---
+nav_title: Postman et demandes d’échantillons
+article_title: Postman et demandes d’échantillons
+page_order: 3
+description: "Cet article de référence couvre la collection Braze Postman, ce qu’elle est, comment la configurer et l’utiliser, ainsi que la façon de modifier et d’envoyer des demandes."
+page_type: reference
+
+---
+
+# Postman et demandes d’exemples
+
+> Braze vous permet de générer des exemples de requêtes API pour tous nos endpoints grâce à notre collection Postman. Cet article de référence couvre la collection Braze Postman, ce qu’elle est, comment la configurer et l’utiliser, ainsi que la façon de modifier et d’envoyer des demandes.
+
+## Qu’est-ce que Postman ?
+
+Postman est un outil d’édition visuelle gratuit pour la création et l’analyse des demandes API. Contrairement à d'autres méthodes d'interaction avec les API (par exemple, l'utilisation de cURL), Postman vous permet de modifier facilement les demandes d'API, d'afficher les informations d'en-tête, et bien plus encore. Postman a la possibilité d’enregistrer les collections ou bibliothèques d’échantillons de demandes API prédéfinis. Afin de faciliter la mise en service et l’exécution de nos API REST pour nos clients, nous avons créé une collection avec des exemples prédéfinis pour tous nos endpoints d’API.
+
+Consultez ou téléchargez notre collection Postman en cliquant sur **Exécuter dans Postman** dans notre [documentation Postman](https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#intro) pour commencer.
+
+## Utilisation de la collection Braze Postman
+
+Si vous disposez d'un compte Postman (vous pouvez télécharger les versions macOS, Windows et Linux depuis le [site web de Postman][1]), vous pouvez ouvrir notre documentation Postman dans votre propre application Postman en cliquant sur le bouton orange **Exécuter dans Postman.**  Vous pouvez ensuite [créer un environnement](#setting-up-your-postman-environment), ou utiliser notre environnement API REST de Braze comme modèle, et modifier les requêtes `POST` et `GET` disponibles pour répondre à vos propres besoins.
+
+### Configuration de votre environnement Postman
+
+{% raw %}
+La collection Braze Postman utilise une variable de modèle, `{{instance_url}}`, pour remplacer l’URL d’API REST de votre instance Braze dans les demandes prédéfinies, et la variable `{{api_key}}` de votre clé API. Au lieu de devoir modifier manuellement toutes les demandes de la collection, vous pouvez configurer cette variable dans votre environnement Postman. Vous pouvez sélectionner notre environnement modèle (modèle de l’environnement de l’API REST Braze) dans la liste déroulante, puis remplacer les valeurs de variables par les vôtres, ou créer votre propre environnement.
+{% endraw %}
+
+Pour créer votre propre environnement, procédez comme suit :
+
+1. Dans l'onglet **Espaces de travail**, sélectionnez **Environnements**.
+2. Cliquez sur le bouton **+** plus pour créer un nouvel environnement.
+3. Donnez un nom à cet environnement (par exemple, "Braze API Requests") et ajoutez des clés pour `instance_url` et `api_key` avec des valeurs correspondant à votre \[instance de Braze][7] et à votre \[clé d'API REST de Braze][8].
+4. Cliquez sur **Enregistrer**.
+
+{% alert note %}
+Dans les corps de requête `POST`, la `api_key` doit être comprise entre des guillemets : `"MY-API-KEY-EXAMPLE"`. Dans les URL `GET`, elle ne doit pas l’être. Nous vous avons déjà fourni ce formatage pour les corps de demande `POST`, les URL `GET` et le modèle d’environnement de `YOUR-API-KEY-HERE` dans cette documentation.
+{% endalert %}
+
+![Ajout de variables pour la clé API et l’URL d’instance à l’environnement API REST de Braze dans Postman.][3]
+
+### Utiliser les demandes prédéfinies de la collection
+
+Après avoir configuré votre environnement, vous pouvez utiliser l'une des demandes prédéfinies de la collection comme modèle pour créer de nouvelles demandes d'API. Pour commencer à utiliser l'une des requêtes préconstruites, cliquez dessus dans le menu **Collections** de Postman. Cela ouvrira la demande sous forme de nouvel onglet dans la fenêtre principale de l’application Postman.
+
+En général, il existe deux types de requêtes que les endpoints API de Braze acceptent : `GET` et `POST`. Selon la méthode `HTTP` que l’endpoint utilise, vous devrez modifier la demande prédéfinie différemment.
+
+#### Modifier une demande POST
+
+Lorsque vous modifiez une demande `POST`, ouvrez la demande et accédez à la section **Corps** dans l'éditeur de demande. Pour des raisons de lisibilité, sélectionnez le bouton radio **raw** pour formater le corps de la requête `JSON`.
+
+![Onglet Corps lors de la modification d’une demande POST Suivi de l’utilisateur dans Postman][4]
+
+#### Modifier une demande GET
+
+Lors de la modification d’une demande `GET`, changez les paramètres transmis dans l’URL de demande. Pour ce faire, sélectionnez l'onglet **Params** et modifiez les paires clé-valeur dans les champs qui apparaissent.
+
+![Onglet Paramètres lors de la modification d’une demande GET Demander la liste des adresses e-mail désinscrites dans Postman.][5]
+
+### Envoyer votre demande
+
+Lorsque votre demande d'API est prête, cliquez sur **Envoyer.** La demande est envoyée et les données de réponse s’affichent dans une section sous l’éditeur de demande. À partir de là, vous pouvez afficher les données brutes renvoyées par l'API de Braze, le code de réponse HTTP, le temps de traitement de la demande et les informations d'en-tête.
+
+![Exemples de données de réponse de corps d’une demande POST avec un statut de 201 Créés et un temps de réponse de 269 millisecondes.][6]
+
+[1]: https://www.getpostman.com
+[3]: {% image_buster /assets/img_archive/postman_variable.png %}
+[4]: {% image_buster /assets/img_archive/postman_post.png %}
+[5]: {% image_buster /assets/img_archive/postman_get.png %}
+[6]: {% image_buster /assets/img_archive/postman_response.png %}
+[7]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
+[8]: {{site.baseurl}}/api/api_key/
diff --git a/_lang/fr_fr/_api/use_cases.md b/_lang/fr_fr/_api/use_cases.md
new file mode 100644
index 00000000000..7c2190f6378
--- /dev/null
+++ b/_lang/fr_fr/_api/use_cases.md
@@ -0,0 +1,242 @@
+---
+nav_title: "Cas d'utilisation de l'API"
+article_title: "Cas d'utilisation de l'API"
+description: "Que vous soyez un développeur chevronné ou un marketeur avec des ressources de développement minimales, cet article de référence est conçu pour vous aider à comprendre comment exploiter la puissance de l'API REST de Braze pour accomplir diverses tâches et améliorer votre stratégie d'engagement client."
+page_type: reference
+page_order: 4.8
+---
+
+# cas d'utilisation de l'API
+
+> L'API REST [Braze]({{site.baseurl}}/api/basics/) offre une large gamme de points de terminaison conçus pour aider à gérer et optimiser votre stratégie d'engagement client. Dans cet article, nous explorerons plusieurs cas d'utilisation pour chaque collection de points de terminaison : catalogues, listes et adresses e-mail, exportation, messages, centre de préférences, SMS, groupes d'abonnement, modèles et données utilisateur.<br><br>Chaque section introduit un scénario avec un guide étape par étape, un exemple de code et un résultat attendu. À la fin de cet article, vous comprendrez mieux comment utiliser l'API REST de Braze pour améliorer vos efforts d'engagement client.
+
+## Suppression de plusieurs éléments dans un catalogue
+
+La nouvelle année s’accompagne de nouveaux lancements de produits chez Kitchenerie, une marque de vente au détail spécialisée dans les articles de cuisine. Dans le tableau de bord de Braze, Kitchenerie a mis en place un catalogue pour sa collection de vaisselle. Il est intitulé « Dishware ». Cette nouvelle année signifie également le retrait des produits suivants de sa collection de vaisselle.
+
+* Plain Bisque
+* Porcelaine de perle
+* Pink Shimmer
+
+Pour supprimer ces produits de son catalogue, Kitchenerie peut utiliser le [point de terminaison `/catalogs/{catalog_name}/items`]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/delete_catalog_items_bulk/) afin de transmettre les identifiants des produits.
+
+Voici la demande d'exemple :
+
+```
+curl --location --request DELETE 'https://rest.iad-03.braze.com/catalogs/dishware/items' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+  "items": [
+    {"id": "plainbisque"},
+    {"id": "pearlporcelain"},
+    {"id": "pinkshimmer"}
+  ]
+}'
+```
+
+Après l'envoi de cette charge utile, la réponse suivante confirme que les trois collections ont été supprimées avec succès du catalogue de vaisselle de Kitchenerie.
+
+```json
+{
+  "message": "success"
+}
+```
+
+## Retirer des e-mails de la liste des courriers indésirables de Braze
+
+Chez MovieCanon, une entreprise de services de streaming, l'équipe de développement est responsable de l'audit périodique de ses listes de diffusion pour identifier et conserver les utilisateurs abonnés à ses campagnes par e-mail. Dans le cadre de cet audit, MovieCanon souhaite supprimer cette liste d'e-mails de sa liste de courriers indésirables :
+
+- august.author.example.com
+- betty.benson@example.com
+- charlie.chase@example.com
+- delilah.york@example.com
+- evergreen.rebecca@example.com
+
+Pour accomplir cette tâche, l'équipe de développeurs aura besoin d'une clé API avec l'autorisation `email.spam.remove` pour utiliser l’endpoint `/email/spam/remove`. Cet endpoint supprime les adresses e-mails de la liste des courriers indésirables de Braze et de la liste des courriers indésirables gérée par le fournisseur de messagerie de MovieCanon.
+
+Pour envoyer cette demande, incluez soit une adresse e-mail sous forme de chaîne, soit un tableau de jusqu'à 50 adresses e-mail à modifier. Comme le nombre des e-mails à supprimer est inférieur à 50, MovieCanon peut accomplir cette tâche avec le corps de requête suivant :
+
+```
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+```
+
+```json
+{
+  "email": ["august.author.example.com","betty.benson@example.com","charlie.chase@example.com","delilah.york@example.com","evergreen.rebecca@example.com"]
+}
+```
+
+Après avoir envoyé cette charge utile avec succès, cette réponse confirme que les e-mails ont été retirés de la liste des courriers indésirables de MovieCanon.
+
+```json
+{
+  "message": "success"
+}
+```
+
+## Audit de toutes les toiles
+
+Le système de santé de la vallée de Siege est un réseau hospitalier qui comprend 10 hôpitaux en activité et des centres de recherche avec des milliers de patients. Son équipe marketing souhaite comparer les Canvases envoyés aux patients pour leur rappeler de prendre rendez-vous pour des vaccins contre la grippe au cours des 3 dernières années d'utilisation de Braze. L'équipe marketing de Siege Valley Health souhaite également disposer d'un moyen rapide et efficace de consulter à la fois la liste des canvas et le résumé analytique.
+
+Plongeons dans la façon dont Siege Valley Health peut accomplir ces deux tâches en utilisant une combinaison de points de terminaison plutôt qu'en filtrant via le tableau de bord Braze.
+
+Pour la première tâche d'audit des canvas, utilisez l’[endpoint `/canvas/list`]({{site.baseurl}}/api/endpoints/export/canvas/get_canvases/) pour exporter une liste de canvas qui comprend le nom et les étiquettes. Voici un exemple de demande :
+
+{% details Voici la réponse que l'équipe marketing de Siege Valley Health recevrait. %}
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "canvases" : [
+  	{
+  		"id": "canvas_identifier_1",
+  		"last_edited": "2020-07-10T23:59:59",
+  		"name": "PatientReminder_FluShot_2020",
+  		"tags": {
+        "flu_shots", "patienthealth", "2020"
+      },
+  	},
+  	{
+  		"id": "canvas_identifier_2",
+  		"last_edited": "2020-07-30T23:59:59",
+  		"name": "PatientReminder2_FluShot_2020",
+  		"tags": {
+        "flu_shots", "patienthealth", "reminder", "2020"
+      },
+  	},
+    ... (more Canvases)
+  ],
+  "message": 'success'
+}
+```
+{% enddetails %}
+
+Passons à la tâche suivante. Celle-ci consiste à afficher le résumé analytique du premier canvas de la liste des canvas de Siege Valley Health. Pour ce faire, nous utiliserons l’[endpoint `/canvas/data_summary`]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_analytics_summary/) avec les paramètres de requête suivants :
+
+* `canvas_id`: "canvas_identifier_2"
+* `ending_at` : 2023-07-10T23:59:59
+* `starting_at` : 2020-07-10T23:59:59
+
+Voici une demande d'exemple :
+
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/canvas/data_summary?canvas_id={{canvas_identifier_2}}&ending_at=2023-07-10T23:59:59&starting_at=2020-07-10T23:59:59&length=5&include_variant_breakdown=false&include_step_breakdown=false&include_deleted_step_data=false' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+## Vérifier les campagnes et canvas planifiés à venir
+
+La période la plus chargée de l'année approche à grands pas pour Flash & Thread, une marque de vente au détail de vêtements et de produits de beauté en ligne et en magasin. Son équipe marketing souhaite vérifier les campagnes et les canvas à venir depuis le tableau de bord de Braze avant le 31 mars 2024 à 12 heures. Cette tâche peut être effectuée au moyen de l’[endpoint `/messages/scheduled_broadcasts`]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/get_messages_scheduled/). 
+
+Voici la demande d'exemple :
+
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/messages/scheduled_broadcasts?end_time=2024-03-31T12:00:00' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+Ce point de terminaison renverra la liste des campagnes et des toiles à venir. À partir de là, l'équipe marketing peut confirmer sa liste de messages en se référant au champ `name` pour les campagnes et les Canvases dans la réponse.
+
+## Affichage d'un ancien centre de préférences
+
+PoliterWeekly est un magazine numérique dont les abonnés sont joignables par e-mail. Dans le but de mieux comprendre le parcours utilisateur de ses abonnés, l'équipe marketing souhaite examiner les détails du centre de préférences de PoliterWeekly pour vérifier quand il a été créé et mis à jour pour la dernière fois.
+
+En utilisant l’[endpoint `/preference_center/v1/{preferenceCenterExternalID}`]({{site.baseurl}}/api/endpoints/preference_center/get_view_details_preference_center/), l'équipe marketing n'a qu'à insérer l'ID externe du centre de préférences en tant que paramètre de chemin, ce qui ressemblerait à ceci :
+
+```
+curl --location -g --request GET https://rest.iad-01.braze.com/preference_center/v1/politer_weekly_preference_center_api_id \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+
+{% details Voici la réponse que l'équipe marketing de PoliterWeekly recevrait. %}
+
+```json
+{
+  "name": "PoliterWeekly Notification Preferences",
+  "preference_center_api_id": "user_engage_pref_123",
+  "created_at": "2021-04-03T12:00:00",
+  "updated_at": "2024-08-15T15:00:00",
+  "preference_center_title": "Manage Your PoliterWeekly Notification Preferences",
+  "preference_center_page_html": "<!DOCTYPE html><html><head><title>Your PoliterWeekly Newsletter Preferences</title><style>body { font-family: Arial, sans-serif; margin: 0; padding: 20px; }.container { max-width: 600px; margin: auto; }h1 { color: #333; }.preference { margin-bottom: 20px; }.preference label { font-size: 16px; }.preference input[type=\"checkbox\"] { margin-right: 10px; }.submit-btn { background-color: #007bff; color: white; padding: 10px 20px; border: none; cursor: pointer; }</style></head><body><div class=\"container\"><h1>Manage your notification preferences</h1><p>Select the types of updates you wish to receive from us:</p><form id=\"preferencesForm\"><div class=\"preference\"><label><input type=\"checkbox\" name=\"newsUpdates\" checked> News Updates</label></div><div class=\"preference\"><label><input type=\"checkbox\" name=\"editorialPicks\"> Editorial Picks</label></div><div class=\"preference\"><label><input type=\"checkbox\" name=\"events\"> Events & Webinars</label></div><div class=\"preference\"><label><input type=\"checkbox\" name=\"specialOffers\"> Special Offers & Promotions</label></div><button type=\"submit\" class=\"submit-btn\">Save Preferences</button></form></div><script>document.getElementById('preferencesForm').addEventListener('submit', function(e) {e.preventDefault();alert('Your preferences have been saved!');});</script></body></html>",
+  "confirmation_page_html": "<!DOCTYPE html><html><head><title>PoliterWeekly Preferences Updated</title></head><body><h1>You're good to go!</h1><p>Your preferences have been updated successfully.</p></body></html>",
+  "redirect_page_html": null,
+  "preference_center_options": {
+    "meta-viewport-content": "width=device-width, initial-scale=1"
+  },
+  "state": "active"
+}
+```
+
+À partir de cette réponse, l'équipe marketing peut voir que le centre de préférences a été créé 3 ans avant sa mise à jour la plus récente. Avec ces informations en tête, l'équipe marketing pourrait créer et lancer un nouveau centre de préférences.
+
+{% enddetails %}
+
+## Suppression des numéros de téléphone invalides
+
+Chez CashBlastr, l'objectif principal est de simplifier la façon dont les individus peuvent envoyer et recevoir des paiements rapides. En tant qu'entreprise de services financiers, CashBlastr souhaite maintenir sa liste de numéros de téléphone de ses clients à jour et précise. L'équipe de développeurs a été chargée de supprimer la liste suivante de numéros de téléphone marqués comme « invalides » afin que les messages SMS de l'équipe marketing puissent atteindre les clients appropriés de CashBlastr.
+
+- 12223135467
+- 12183095514
+- 14235662245
+- 14324567892
+
+Pour envoyer une demande avec le [`/sms/invalid_phone_numbers/remove` point de terminaison]({{site.baseurl}}/api/endpoints/sms/post_remove_invalid_numbers/), les numéros de téléphone doivent être dans un tableau de chaînes en [e.164 format](https://en.wikipedia.org/wiki/E.164), avec jusqu'à 50 numéros de téléphone par demande. Comme la liste ne dépasse pas 50 numéros de téléphone, voici un exemple du corps de la requête que l'équipe de développement de CashBlastr enverrait :
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR-REST-API-KEY
+{
+  "phone_numbers": ["12183095514","14255551212"]
+}
+```
+
+Après l'envoi de cette charge utile, la réponse suivante confirme que les numéros de téléphone invalides de CashBlastr ont été supprimés de la liste des invalides de Braze.
+
+```json
+{
+  "message": "success"
+}
+```
+
+## Affichage du statut du groupe d'abonnement d'un utilisateur
+
+SandwichEmperor est une chaîne de restauration rapide aux États-Unis, et son équipe marketing souhaite vérifier les statuts des groupes d'abonnement pour une liste aléatoire de ses utilisateurs pour les SMS. En utilisant le [`/subscription/status/get` point de terminaison]({{site.baseurl}}/api/endpoints/subscription_groups/get_list_user_subscription_group_status/), SandwichEmperor peut accomplir cette tâche pour un utilisateur individuel avec la demande d'exemple suivante :
+
+{% raw %}
+```
+curl --location -g --request GET 'https://rest.iad-01.braze.com/subscription/status/get?subscription_group_id={{subscription_group_id}}&phone=+11232223333' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endraw %}
+
+Ce point de terminaison répertorie également les statuts des groupes d'abonnement d'un utilisateur pour les e-mails et peut être utilisé pour voir le statut des groupes d'abonnement pour plusieurs utilisateurs.
+
+## Vérification d'un modèle HTML pour la messagerie électronique
+
+Chez WorkFriends, un réseau social qui aide à établir des connexions entre les travailleurs de différentes industries, son équipe marketing est responsable de l'envoi de campagnes par e-mail à ses utilisateurs. Ces campagnes incluent souvent des rappels pour des événements locaux, des bulletins hebdomadaires et des points forts de l'activité du profil.
+
+Dans ce scénario, WorkFriends a historiquement utilisé un modèle HTML unique avec son ancienne marque. Dans un effort pour aligner son identité de marque, WorkFriends veut vérifier s'il y a des informations utiles dans ce modèle HTML à exploiter avant de passer à un nouveau modèle.
+
+{% details Voici la réponse que l'équipe WorkFriends recevrait. %}
+
+```json
+Content-Type: application/json
+Authorization: Bearer YOUR_REST_API_KEY
+{
+  "email_template_id": "WorkFriends_Email_Template_ID",
+  "template_name": "Promo template",
+  "description": "Promo template",
+  "subject": "WorkFriends Weekly Newsletter",
+  "preheader": "Another week, another WorkFriends update",
+  "body": "<!DOCTYPE html><html><head><title>WorkFriends Weekly Newsletter</title><style>body {font-family: Arial, sans-serif; color: #333;}.container {padding: 20px;}.header {background-color: #f2f2f2; padding: 10px; text-align: center;}.content {margin-top: 20px;}.footer {margin-top: 20px; font-size: 12px; text-align: center; color: #777;}</style></head><body><div class=\"container\"><div class=\"header\"><h2>WorkFriends Weekly Newsletter</h2></div><div class=\"content\"><p>Hello WorkFriends,</p><p>Welcome to another edition of our weekly newsletter. We've got some exciting updates and promos for you this week!</p><!-- Add more content here --><p>Don't forget to check out our latest promos and updates. Stay connected, stay informed!</p></div><div class=\"footer\"><p>Thank you for being a part of WorkFriends.</p><p>Unsubscribe | Update Preferences</p></div></div></body></html>",
+  "tags": "promo",
+  "created_at": "2020-07-10 13:00:00.000",
+  "updated_at": "2024-02-04 17:00:00.000"
+}
+```
+
+{% enddetails %}
+
+Après avoir examiné ces informations de modèle, WorkFriends peut également utiliser le [`/templates/email/update` point de terminaison]({{site.baseurl}}/api/endpoints/templates/email_templates/post_update_email_template/) pour mettre à jour le modèle d'e-mail via l'API. Le modèle d'email dans le tableau de bord Braze reflétera ces modifications.
diff --git a/_lang/fr_fr/_contributing/content_management.md b/_lang/fr_fr/_contributing/content_management.md
new file mode 100644
index 00000000000..3334baa7fb5
--- /dev/null
+++ b/_lang/fr_fr/_contributing/content_management.md
@@ -0,0 +1,432 @@
+---
+nav_title: Gestion du contenu
+article: Content Management
+description: "Voici un aperçu de la façon dont le contenu est géré sur Braze Docs."
+page_order: 2 
+noindex: true
+---
+
+# A propos de la gestion de contenu
+
+> Voici un aperçu de la façon dont le contenu est géré sur Braze Docs. Pour en savoir plus sur un sujet spécifique, choisis la page thématique dédiée dans la navigation.
+
+## Méthodologie
+
+Braze Docs est géré à l'aide de docs-as-code, une méthode de gestion de la documentation qui reflète le cycle de vie du développement logiciel en utilisant un système de contrôle des versions. Braze Docs utilise le système de contrôle de version Git, qui permet aux contributeurs de travailler sur la même documentation sans écraser le travail des autres. Pour plus d'informations, voir [À propos du contrôle de version et de Git](https://docs.github.com/en/get-started/using-git/about-git#about-version-control-and-git).
+
+![The Braze Docs repository's home page on GitHub.]({% image_buster /assets/img/contributing/github/home_page.png %})
+
+## Générateur de site 
+
+Braze Docs est construit à l'aide de Jekyll, un générateur de site statique populaire qui permet de stocker les fichiers de contenu et les fichiers de conception dans des répertoires distincts, tels que `_docs` pour les fichiers de contenu et `assets` pour les fichiers de conception. Lorsque le site est construit, Jekyll fusionne intelligemment chaque fichier et les stocke sous forme de données XML et HTML dans le répertoire `_site`. Pour plus d'informations, voir [Structure des répertoires de Jekyll](https://jekyllrb.com/docs/structure/).
+
+![The home page for Braze Docs.]({% image_buster /assets/img/contributing/styling_examples/home.png %})
+
+En tant que collaborateur, tu travailleras principalement dans les répertoires suivants.
+
+| Répertoire | Description |
+|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [`_docs`](https://github.com/braze-inc/braze-docs/tree/develop/_docs)         | Contient tout le contenu écrit pour Braze Docs sous forme de fichiers texte rédigés en Markdown. Les fichiers texte sont organisés en répertoires et sous-répertoires reflétant le site docs, par exemple `_api` pour la [section API]({{site.baseurl}}/api/home) et `user_guide` pour la [section User Guide]({{site.baseurl}}/user_guide/introduction). |
+| [`_includes`](https://github.com/braze-inc/braze-docs/tree/develop/_includes) | Contient des fichiers texte (appelés "includes") qui peuvent être réutilisés dans n'importe quel fichier du répertoire `_docs`. Généralement, les inclusions sont des éléments de contenu courts et modulaires qui n'utilisent pas de formatage standard. Les fichiers stockés à cet emplacement sont importants pour la [réutilisation des contenus](#content-reuse).                                            |
+| [`assets`](https://github.com/braze-inc/braze-docs/tree/develop/assets)       | Contient toutes les images de Braze Docs. Tout fichier texte se trouvant dans le répertoire `_docs` ou `_includes` peut être lié à ce répertoire pour afficher une image sur sa page.                                                                                                                                                                         |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% alert tip %}
+Pour une démonstration complète, voir [Générer un aperçu]({{site.baseurl}}/contributing/generating_a_preview/).
+{% endalert %}
+
+## Pages
+
+Chaque page de Braze Docs est rédigée en syntaxe Markdown et stockée sous forme de fichier Markdown à l'aide de l'extension de fichier `.md`. En haut de chaque fichier Markdown, YAML front matter est utilisé pour ajouter des métadonnées cachées pour chaque page.
+
+\`\`\`markdown
+---
+METADATA\_KEY : METADATA\_VALUE
+---
+
+# CONTENU
+\`\`\`
+
+Remplacez les éléments suivants :
+
+| Placeholder | Description |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------|
+| `METADATA_KEY` | La clé représentant un type de métadonnées pris en charge. Pour plus d'informations, voir [Métadonnées]({{site.baseurl}}/contributing/yaml_front_matter/metadata/). |
+| `METADATA_VALUE` | La valeur attribuée à la clé du type de métadonnées. Pour plus d'informations, voir [Métadonnées]({{site.baseurl}}/contributing/yaml_front_matter/metadata/).  |
+| `CONTENT` | Le contenu de la page écrit en syntaxe Markdown.                                                                                           |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% tabs local %}
+{% tab example input %}
+\`\`\`markdown
+---
+nav_title: Contribuer aux documents de Braze
+article: Contribution aux documents de Braze
+description: "Voici ce dont tu as besoin pour commencer à contribuer à Braze Docs !"
+page_order: 0
+search_tag: Contribuer
+---
+
+# Contribution aux documents de Braze
+
+> Merci de contribuer aux documents de Braze ! Tous les mardis et jeudis, nous fusionnons les contributions de la communauté et les déployons sur Braze Docs. Utilise ce guide pour que tes modifications soient fusionnées lors de notre prochain déploiement.
+\`\`\`
+{% endtab %}
+
+{% tab example output %}
+![Example page on Braze Docs.]({% image_buster /assets/img/contributing/styling_examples/page.png %})
+{% endtab %}
+{% endtabs %}
+
+{% alert tip %}
+Pour une présentation complète, voir [Créer une page]({{site.baseurl}}/contributing/content_management/pages/#creating-a-page).
+{% endalert %}
+
+## Images
+
+Les images sont stockées sous forme de fichiers PNG à l'intérieur de `assets/img`. La structure du répertoire `img` n'a pas besoin de correspondre à la structure de Braze Docs ; cependant, il est préférable de regrouper les images apparentées dans des sous-répertoires.
+
+Chaque image peut être liée à une ou plusieurs pages à l'aide de la syntaxe suivante.
+
+{% raw %}
+```markdown
+![ALT_TEXT.]({% image_buster /assets/img/DIRECTORY/IMAGE.png %})
+```
+{% endraw %}
+
+Remplacez les éléments suivants :
+
+| Placeholder | Description |
+|-------------|-------------------------------------------------------------------------------------------------------------------------|
+| `ALT_TEXT` | Le texte alt de l'image. Cela est nécessaire pour s'assurer que Braze Docs est également accessible aux personnes qui utilisent des lecteurs d'écran. |
+| `IMAGE` | Le chemin relatif de ton image à partir du répertoire `img`.                                                      |
+{: .reset-td-br-1 .reset-td-br-2}
+
+Ton image en ligne devrait ressembler à ce qui suit :
+
+{% raw %}
+```markdown
+![The form for creating a new pull request on GitHub.]({% image_buster /assets/img/contributing/getting_started/github_pull_request.png %})
+```
+{% endraw %}
+
+{% alert tip %}
+Pour une démonstration complète, voir [Ajouter une nouvelle image]({{site.baseurl}}/contributing/content_management/images/#adding-a-new-image).
+{% endalert %}
+
+## Sections
+
+Braze Docs est organisé en sections et [sous-sections](#subsections) [principales](#primary-sections).
+
+### Sections primaires
+
+Les principales sections de Braze Docs sont les suivantes :
+
+- [Accueil Braze Docs]({{site.baseurl}})
+- [Guide d’utilisation]({{site.baseurl}}/user_guide/introduction)
+- [Guide du développeur]({{site.baseurl}}/developer_guide/home)
+- [Guide de l’API Braze]({{site.baseurl}}/api/home)
+- [Partenaires technologiques]({{site.baseurl}}/partners/home)
+- [Aide Braze]({{site.baseurl}}/help/home)
+- [Contribution aux documents de Braze]({{site.baseurl}}/contributing/home/)
+
+Outre **Contribuer à Braze Docs**, ces sections principales sont accessibles sur l'en-tête du site à partir de n'importe quelle page de Braze Docs.
+
+![The primary sections as shown on the site header on Braze Docs.]({% image_buster /assets/img/contributing/styling_examples/header.png %})
+
+Chaque section primaire est construite à l'aide des [collections Jekyll](https://jekyllrb.com/docs/collections/), qui permettent de regrouper des contenus connexes pour faciliter la gestion. Garde à l'esprit que si toutes les sections primaires sont des collections, toutes les collections ne sont pas des sections primaires. Tu trouveras la liste complète des collections Braze Docs dans le fichier de configuration Jekyll, `_config.yml`.
+
+```yaml
+collections:
+  home:
+    title: Documentation
+    output: true
+    default_nav_url: ''
+    page_order: 1
+  user_guide:
+    title: User Guide
+    output: true
+    default_nav_url: introduction/
+    page_order: 2
+  developer_guide:
+    title: Developer Guide
+    output: true
+    default_nav_url: home/
+    page_order: 3
+  api:
+    title: API
+    output: true
+    default_nav_url: home/
+    page_order: 4
+  partners:
+    title: Technology Partners
+    output: true
+    default_nav_url: home/
+    page_order: 5
+  help:
+    title: Help
+    output: true
+    default_nav_url: home/
+    page_order: 6
+  contributing:
+    output: true
+    default_nav_url: contributing/
+  hidden: # Hidden pages not directly linked via navigation
+    title: Braze
+    output: true
+    hidden: true
+  docs_pages: # Site specific pages. ie main redirects and search
+    title: Braze
+    output: true
+    hidden: true
+```
+
+Chaque collection répertoriée représente un répertoire au sein du répertoire `_docs`.
+
+```plaintext
+braze-docs
+└── _docs
+    ├── _api
+    ├── _contributing
+    ├── _developer_guide
+    ├── _docs_pages
+    ├── _help
+    ├── _hidden
+    ├── _home
+    ├── _partners
+    └── _user_guide
+```
+
+La page d'accueil de chaque section primaire est un fichier Markdown standard dont la clé `page_order:` est définie sur `0`.
+
+{% tabs local %}
+{% tab example input %}
+\`\`\`markdown
+---
+page_order: 0
+nav_title: Home
+article_title:Guide de l’utilisateur Braze
+layout: user\_guide
+user\_top\_header: Guide de l’utilisateur Braze
+---
+\`\`\`
+{% endtab %}
+
+{% tab example output %}
+![An example landing page on Braze Docs.]({% image_buster /assets/img/contributing/styling_examples/primary_section.png %})
+{% endtab %}
+{% endtabs %}
+
+### Sous-sections
+
+Toutes les sections principales de Braze Docs contiennent une ou plusieurs sous-sections, chacune représentant un élément extensible dans la navigation de gauche.
+
+Contrairement aux sections primaires, les sous-sections peuvent être configurées avec ou sans page de renvoi. Les sous-sections sans pages d'atterrissage sont utiles pour organiser ensemble le contenu connexe tout en minimisant le nombre de pages non utiles dans Braze Docs. Qu'une sous-section soit configurée avec ou sans page de destination, toutes les sous-sections représentent à la fois un répertoire et un fichier Markdown dans le référentiel. Pour un exemple, voir ce qui suit.
+
+```plaintext
+braze-docs
+└── _docs
+    └── _primary_section
+        ├── subsection_a
+        │   ├── page_a.md
+        │   └── page_b.md
+        ├── subsection_b
+        │   ├── page_a.md
+        │   └── page_b.md
+        ├── subsection_a.md # not configured as a landing page
+        └── subsection_b.md # configured as a landing page  
+```
+
+{% alert tip %}
+Pour une présentation complète, voir [Créer une section]({{site.baseurl}}/contributing/content_management/sections/#creating-a-section).
+{% endalert %}
+
+Dans le répertoire `_primary_section`, `subsection_a` n'est pas configuré avec une page d'atterrissage, tandis que `subsection_b` est configuré avec une page d'atterrissage. Dans l'exemple suivant, `subsection_a.md` a pour valeur `config_only:` `true` , ce qui empêche le rendu de cette page en tant que page d'atterrissage.
+
+{% tabs local %}
+{% tab example input %}
+\`\`\`markdown
+---
+nav_title: Sous-section A
+page_order: 0
+config_only: true
+---
+\`\`\`
+{% endtab %}
+
+{% tab example output %}
+![The left-side navigation on Braze Docs, showing an example of an expanded section without a landing page.]({% image_buster /assets/img/contributing/styling_examples/subsection_config_only.png %})
+{% endtab %}
+{% endtabs %}
+
+Cependant, `subsection_b.md` n'utilise pas la clé `config_only:`, et cette page _est_ donc rendue comme une page d'atterrissage.
+
+{% tabs local %}
+{% tab example input %}
+\`\`\`markdown
+---
+nav_title: Sous-section B
+page_order: 0
+---
+\`\`\`
+{% endtab %}
+
+{% tab example output %}
+![The left-side navigation on Braze Docs, showing an example of an expanded section with a landing page.]({% image_buster /assets/img/contributing/styling_examples/subsection_landing_page.png %})
+{% endtab %}
+{% endtabs %}
+
+{% alert note %}
+Bien qu'une sous-section dont l'adresse `config_only:` est définie sur `true` ne soit pas rendue comme une page, le nom du répertoire de la sous-section est toujours utilisé dans les URL des pages de cette sous-section. Pour plus d'informations, voir [URL](#urls).
+{% endalert %}
+
+## Réutilisation du contenu
+
+Jekyll offre la possibilité de réutiliser le contenu écrit dans les documents à l'aide de la balise `include`. Les inclusions se trouvent dans le répertoire `_includes` et peuvent être écrites en syntaxe Markdown ou HTML.
+
+```markdown
+{% raw %}{% multi_lang_include RELATIVE_PATH/FILE %}{% endraw %}
+```
+
+Remplacez les éléments suivants :
+
+| Placeholder | Description |
+|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `RELATIVE_PATH` | (Facultatif) Le chemin d'accès relatif au fichier du répertoire `_includes`. Ceci n'est nécessaire que si tu inclus un fichier provenant d'un répertoire situé à l'intérieur du répertoire `_includes`, tel que `_includes/braze/upgrade_notice.md`. |
+| `FILE` | Le nom du fichier, y compris son extension.                                                                                                                                                                      |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% tabs local %}
+{% tab example input %}
+{% raw %}
+\`\`\`markdown
+# Pages
+
+> Apprends à créer, modifier et supprimer des pages sur Braze Docs.
+
+{% multi_lang_include contributing/prerequisites.md %}
+\`\`\`
+{% endraw %}
+{% endtab %}
+
+{% tab example output %}
+![Content reuse example on Braze Docs.]({% image_buster /assets/img/contributing/styling_examples/includes.png %})
+{% endtab %}
+{% endtabs %}
+
+{% alert tip %}
+Pour une présentation complète, voir [Réutiliser le contenu]({{site.baseurl}}/contributing/content_management/reusing_content).
+{% endalert %}
+
+## Mises en page
+
+Par défaut, Jekyll utilise la mise en page `default.html` dans le répertoire `_layouts` pour construire chaque page sur Braze Docs. Cependant, il est possible d'utiliser différentes mises en page en attribuant la mise en page à la touche `layout:` dans la page d'accueil YAML.
+
+\`\`\`markdown
+---
+layout: LAYOUT\_VALUE
+---
+\`\`\`
+
+Remplace `LAYOUT_VALUE` par le nom du fichier de mise en page et l'extension du fichier est supprimée.
+
+{% tabs local %}
+{% tab example input %}
+**Arbre de fichiers**
+
+```plaintext
+braze-docs
+└── _layouts
+    └── api_page.html
+```
+
+**Métadonnées dans la page**
+
+\`\`\`markdown
+---
+layout: page api
+---
+\`\`\`
+{% endtab %}
+
+{% tab example output %}
+![API glossary layout example on Braze Docs.]({% image_buster /assets/img/contributing/styling_examples/layouts/api_page.png %})
+{% endtab %}
+{% endtabs %}
+
+{% alert tip %}
+Pour plus d'informations, voir [Mise en page]({{site.baseurl}}/contributing/yaml_front_matter/page_layouts).
+{% endalert %}
+
+## URL
+
+Les URL sur Braze Docs correspondent toujours à la structure des répertoires dans le référentiel docs. Dans l'exemple suivant d'arborescence de fichiers, l'URL pour `page_a.md` serait `https://www.braze.com/docs/primary_section/subsection_a/page_a`.
+
+```plaintext
+braze-docs
+└── _docs
+    └── _primary_section
+        └── subsection_a
+            └── page_a.md
+```
+
+Cela inclut les URL des pages situées dans une [sous-section](#subsections) où `config_only:` est défini sur `true`. Même si les sous-sections de `config_only` ne sont pas présentées comme des pages, le nom du répertoire de la sous-section est toujours utilisé pour générer les URL des pages de ce répertoire. Pour un exemple, voir ce qui suit.
+
+```plaintext
+braze-docs
+└── _docs
+    └── _primary_section
+        ├── subsection_a
+        │   ├── page_a.md
+        │   └── page_b.md
+        ├── subsection_b
+        │   ├── page_a.md
+        │   └── page_b.md
+        ├── subsection_a.md # not configured as a landing page
+        └── subsection_b.md # configured as a landing page  
+```
+
+{% tabs local %}
+{% tab subsection a %}
+
+**Exemple de page d'atterrissage**
+
+\`\`\`markdown
+---
+nav_title: Sous-section A
+1\.
+config_only: true
+---
+\`\`\`
+
+Puisque `subsection_a.md` est configuré comme une page d'atterrissage, seuls `page_a.md` et `page_b.md` recevront une URL unique. `subsection_b.md` **ne** recevra aucune URL.
+
+**Exemples d'URL**
+
+```plaintext
+Subsection A URL: N/A
+Page A URL: https://www.braze.com/docs/primary_section/subsection_a/page_a
+Page B URL: https://www.braze.com/docs/primary_section/subsection_a/page_b
+```
+{% endtab %}
+{% tab subsection b %}
+**Exemple de page d'atterrissage**
+
+\`\`\`markdown
+---
+nav_title: Sous-section B
+2\. 
+---
+\`\`\`
+
+Puisque `subsection_b.md` est configuré comme une page d'atterrissage, `page_a.md`, `page_b.md`, et `subsection_b.md` recevront une URL unique.
+
+**Exemples d'URL**
+
+```plaintext
+Subesction B URL: https://www.braze.com/docs/primary_section/subsection_b
+Page A URL: https://www.braze.com/docs/primary_section/subsection_b/page_a
+Page B URL: https://www.braze.com/docs/primary_section/subsection_b/page_b
+```
+{% endtab %}
+{% endtabs %}
diff --git a/_lang/fr_fr/_docs_pages/404.md b/_lang/fr_fr/_docs_pages/404.md
new file mode 100644
index 00000000000..32c9e73c386
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/404.md
@@ -0,0 +1,32 @@
+---
+title: 404
+hidden: true
+hide_nav: true
+permalink: 404.html
+layout: broken_page
+
+broken_image: /docs/assets/img/docs_404.png
+
+broken_text: "Sorry, we can't seem to find the page you're looking for."
+broken_text1: "Désolé, nous n'arrivons pas à trouver la page que vous recherchez."
+broken_text2: "申し訳ありませんが、お探しのページは見つかりませんでした。"
+
+
+recommend_list:
+- name: "Canvas: The Basics"
+  link: /docs/user_guide/engagement_tools/canvas/get_started/the_basics/
+- name: Create a Campaign
+  link: /docs/user_guide/engagement_tools/campaigns/ideas_and_strategies/active_user_campaigns/
+- name: Locations and Geofences
+  link: /docs/user_guide/engagement_tools/locations_and_geofences/
+- name: Personalized Messaging
+  link: /docs/user_guide/personalization_and_dynamic_content/overview/
+- name: Braze REST API
+  link: /docs/developer_guide/rest_api/basics/
+- name: Custom Attributes
+  link: /docs/user_guide/data_and_analytics/custom_data/custom_attributes/
+- name: Custom Events
+  link: /docs/user_guide/data_and_analytics/custom_data/custom_events/
+- name: Create a Segment
+  link: /docs/user_guide/engagement_tools/segments/creating_a_segment//
+---
diff --git a/_lang/fr_fr/_docs_pages/404_api.md b/_lang/fr_fr/_docs_pages/404_api.md
new file mode 100644
index 00000000000..3a0d5da5b75
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/404_api.md
@@ -0,0 +1,30 @@
+---
+title: 404
+hidden: true
+hide_nav: true
+permalink: /api/404.html
+layout: broken_page
+
+broken_image: /docs/assets/img/docs_404.png
+
+broken_text: "API Sorry, we can't seem to find the page you're looking for."
+
+
+recommend_list:
+- name: "Canvas: The Basics"
+  link: /docs/user_guide/engagement_tools/canvas/get_started/the_basics/
+- name: Create a Campaign
+  link: /docs/user_guide/engagement_tools/campaigns/ideas_and_strategies/active_user_campaigns/
+- name: Locations and Geofences
+  link: /docs/user_guide/engagement_tools/locations_and_geofences/
+- name: Personalized Messaging
+  link: /docs/user_guide/personalization_and_dynamic_content/overview/
+- name: Braze REST API
+  link: /docs/developer_guide/rest_api/basics/
+- name: Custom Attributes
+  link: /docs/user_guide/data_and_analytics/custom_data/custom_attributes/
+- name: Custom Events
+  link: /docs/user_guide/data_and_analytics/custom_data/custom_events/
+- name: Create a Segment
+  link: /docs/user_guide/engagement_tools/segments/creating_a_segment//
+---
diff --git a/_lang/fr_fr/_docs_pages/api.md b/_lang/fr_fr/_docs_pages/api.md
new file mode 100644
index 00000000000..25ff228a8a4
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/api.md
@@ -0,0 +1,7 @@
+---
+config_only: true
+noindex: true
+layout: redirect
+redirect_to: /docs/api/home/
+permalink: api/
+---
diff --git a/_lang/fr_fr/_docs_pages/blank.md b/_lang/fr_fr/_docs_pages/blank.md
new file mode 100644
index 00000000000..974d32eed76
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/blank.md
@@ -0,0 +1,5 @@
+---
+noindex: true
+layout: bare
+permalink: blank.html
+---
diff --git a/_lang/fr_fr/_docs_pages/cla.md b/_lang/fr_fr/_docs_pages/cla.md
new file mode 100644
index 00000000000..557ed83c4f1
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/cla.md
@@ -0,0 +1,208 @@
+---
+title: "Braze : Accord de licence contributeur"
+permalink: cla/
+layout: documents
+
+---
+# ACCORD DE LICENCE CONTRIBUTEUR
+
+Le présent Accord de licence contributeur (l’**« Accord »**), en vigueur à compter de la dernière date indiquée sous la signature des parties ci-dessous (la **« Date d’entrée en vigueur »**), est conclu entre Braze, Inc., une société du Delaware dont le siège social est sis 330 W 34th Street, New York, NY 10001 (**« Braze »**), et la partie signant ci-dessous et/ou toute personne ou entité qui exerce les droits d’auteur ou les droits de brevet accordés en vertu du présent Accord, et toute personne ou entité que cette personne ou entité contrôle, c’est-à-dire Vous.
+
+Compte tenu des engagements et accords mutuels contenus dans le présent Accord et d'autres contreparties valables et valables, dont la réception et la suffisance sont reconnues par les présentes, les parties conviennent de ce qui suit à compte de la date d’entrée en vigueur :
+
+1. **Définitions**.<br><br>
+  * **« Code »** désigne le code du logiciel informatique, que ce soit sous une forme pouvant être lue par un humain par l’homme ou exécutable par machine, qui est livré par Vous à Braze en vertu du présent Accord.<br><br>
+  * **« Projet »** désigne tout projet détenu ou géré par Braze dans lequel un logiciel est proposé en vertu d’une licence approuvée par l’[Open Source Initiative (OSI)](www.opensource.org) et la documentation proposée en vertu d’une OSI ou d’une [licence Creative Commons](https://creativecommons.org/licenses).<br><br>
+  * **« Soumettre »** ou **« Soumis »** est l'acte de charger, soumettre, transmettre ou distribuer du contenu pour tout projet (et/ou toute forme de communication électronique, verbale ou écrite envoyée à Braze ou à son conseiller entraînant l’un de ces actes), y compris, mais sans s'y limiter, la communication sur des listes de diffusion électroniques, des systèmes de contrôle de code source et des systèmes de suivi des problèmes gérés par ou au nom de Braze dans le but de discuter et d'améliorer le projet en question.<br><br>
+  * **« Soumission »** désigne le code et tout autre matériel protégé par le droit d'auteur que Vous soumettez en vue de leur inclusion dans, ou dans le but de documenter tout produit ou projet détenu ou géré par Braze, mais à l'exclusion du matériel visiblement marqué, ou autrement désigné par écrit, par vous-même comme n’étant « pas une soumission ».<br><br>
+  * **« Vous »** (ou **« Votre »**) désigne le propriétaire du droit d’auteur ou l’entité juridique autorisée par le propriétaire du droit d’auteur qui conclut le présent Accord avec Braze. Pour les entités juridiques, l’entité effectuant une Soumission et toutes les autres entités qui contrôlent, sont contrôlées par, ou sont sous contrôle commun avec cette entité sont considérées comme un seul « Fournisseur ». Aux fins de la présente définition, le terme « contrôle » désigne (i) la capacité, direct ou indirect, d’imposer la direction ou la gestion de ladite entité, que ce soit par contrat ou autrement, ou (ii) la propriété de 50 % ou plus des actions en circulation, ou (iii) la propriété effective de ladite entité.<br><br>
+
+2. **Votre Soumission.** Vous devez accepter les termes du présent Accord avant de faire une soumission pour un projet. Le présent accord couvre toutes les Soumissions que Vous soumettez, maintenant ou à l'avenir (à l'exception de ce qui est décrit dans la section 4 ci-dessous), pour tout projet. Si une Soumission est apportée avant la signature du présent Accord, cette Soumission déclenchera automatiquement l’acceptation des conditions des présentes.<br><br>
+
+3. **Originalité du travail.** Vous déclarez que chacune de vos Soumissions est entièrement votre travail original. Si Vous souhaitez soumettre des documents qui ne sont pas votre travail original, vous pouvez les soumettre séparément au projet si (a) vous conservez toutes les informations de droit d'auteur et de licence qui se trouvaient dans les documents tels que vous les avez reçus, (b) dans la description accompagnant votre Soumission, vous incluez la phrase « Soumission contenant des éléments d'un tiers », suivi des noms du tiers et de toute licence ou autre restriction dont vous avez connaissance, et (c) Vous suivez toute autre instruction contenue dans les directives écrites du Projet en matière de soumissions.<br><br>
+
+4. **Votre Employeur.** Les références à « employeur » dans le présent Accord incluent votre employeur ou toute autre personne pour laquelle vous agissez en faisant votre soumission, par exemple, en tant que sous-traitant, fournisseur ou agent. Si votre Soumission est faite dans le cadre de votre travail pour votre Employeur, ou si votre Employeur a des droits de propriété intellectuelle sur votre soumission dans le cadre d’un contrat ou de la législation applicable, Vous devez obtenir l’autorisation de votre Employeur pour faire la Soumission avant de signer le présent Accord. Dans ce cas, le terme « Vous » dans le présent Accord fera collectivement référence à vous-même et à l'employeur. Si Vous changez d'employeur à l'avenir et souhaitez soumettre des Soumissions supplémentaires pour votre nouvel employeur, vous acceptez de signer un nouvel accord et d'obtenir l'autorisation de votre nouvel employeur avant de soumettre ces Soumissions.<br><br>
+
+5. **Licences.**<br><br>
+**a. Licence de droit d'auteur.** Vous accordez à Braze, et à ceux qui reçoivent la Soumission directement ou indirectement de Braze, une licence perpétuelle, mondiale, sans frais, non exclusive, libre de droits et irrévocable sur la Soumission pour reproduire, préparer des œuvres dérivées, afficher publiquement, exécuter publiquement et distribuer la Soumission et ces œuvres dérivées, et de sous-licencier tout ou partie des droits susmentionnés à des tiers.<br><br>
+**b. Licence de brevet.** Vous accordez à Braze, et à ceux qui reçoivent les Soumissions applicables de Braze, directement ou indirectement, une licence de brevet perpétuelle, mondiale, non exclusive, sans frais, libre de droits et irrévocable en vertu de Vos revendications de brevet qui sont nécessairement violées par la Soumission applicable ou la combinaison de la Soumission avec le Projet auquel elle a été soumise pour faire, avoir fait, utiliser, proposer de vendre, vendre et importer, ou autrement transférer ou disposer de la Soumission seule ou avec le Projet.<br><br>
+**c. Autres droits réservés.** Chaque partie se réserve tous les droits non expressément accordés dans le présent Accord. Aucune licence ou droit supplémentaire (y compris, sans s'y limiter, toute licence implicite) n'est accordé implicitement par épuisement, estoppel, ou de quelque autre manière que ce soit. Sauf indication spécifique dans le présent Accord, aucun autre brevet, marque de commerce, droit d’auteur ou autre droit de propriété, explicite ou implicite, ne Vous est accordé en vertu du présent Accord, y compris par implication, renonciation ou estoppel.<br><br>
+
+6. **Représentations et garanties.** Vous déclarez que Vous êtes légalement autorisé à accorder les droits, licences et déclarations énoncés dans le présent Accord. Vous déclarez que chacune de vos Soumissions est entièrement votre travail original (sauf ce que vous pouvez avoir communiqué tel que requis dans le cadre de la section 3). Vous déclarez que vous avez obtenu l’autorisation de votre Employeur pour faire la Soumission dans les cas où votre soumission est faite dans le cadre de votre travail pour votre employeur, ou si votre employeur a des droits de propriété intellectuelle sur votre soumission dans le cadre d’un contrat ou de la législation applicable. Si vous signez le présent Accord au nom de votre employeur, vous déclarez et garantissez que vous avez l'autorité nécessaire pour lier l'employeur indiqué aux obligations contenues dans le présent accord. Vous n'êtes pas tenu de fournir une assistance pour votre Soumission, à moins que vous ne choisissiez de le faire. SAUF EXIGENCE PAR LA LÉGISLATION APPLICABLE OU ACCEPTÉE PAR ÉCRIT, ET À L'EXCEPTION DES GARANTIES EXPRESSÉMENT INDIQUÉES DANS LES SECTIONS 3, 4 ET 6, LA SOUMISSION FOURNIE EN VERTU DU PRÉSENT ACCORD EST FOURNIE « EN L’ÉTAT », SANS GARANTIE, EXPRESSE OU IMPLICITE, Y COMPRIS, MAIS SANS S'Y LIMITER, TOUTE GARANTIE OU CONDITION DE QUALITÉ MARCHANDE, OU DE PERTINENCE À DES FINS PARTICULIÈRES.<br><br>
+
+7. **Communication à Braze.** Vous acceptez d'informer Braze par écrit de tout fait ou circonstance dont vous prendrez ultérieurement connaissance et qui rendrait l'une de vos déclarations dans le présent Accord inexacte à quelque égard que ce soit.<br><br>
+
+8. **Informations sur les contributions.** Vous acceptez que les contributions aux projets et les informations sur les contributions puissent être conservées indéfiniment et divulguées publiquement, y compris votre nom et d'autres informations que vous soumettez avec votre soumission.<br><br>
+
+9. **Droit applicable.** Le présent Accord sera régi exclusivement par les lois internes de l'État de New York, sans égard à tout conflit de règle de droit. Les tribunaux d'État et fédéraux situés dans l'État de New York, district de Manhattan, New York City, auront compétence exclusive pour statuer sur tout litige découlant de ou lié au présent Accord. Chaque partie consent à la compétence exclusive de ces tribunaux. Chaque partie renonce également à tout droit à un procès devant jury dans le cadre de toute action ou litige découlant de quelque manière que ce soit du présent accord ou lié à celui-ci. <br><br>
+
+10. **Intégralité de l’Accord/ Cession.** Le présent Accord constitue l'intégralité de l'accord entre les parties concernant votre soumission de tout matériel à tout projet, et remplace tous les accords, propositions ou déclarations antérieurs et contemporains, écrits ou oraux, relatifs à son objet. Cet accord peut être cédé par Braze. <br><br>
+
+Sélectionnez une des options ci-dessous et signez comme indiqué. En signant, vous acceptez et acceptez les termes du présent Accord de Licence Contributeur pour vos Soumissions actuelles et futures à Braze.
+
+
+
+<div id="cla_form_div">
+<form id="cla_form" >
+<input type="radio" name="type" value="personal" id="type_personal" checked="checked" /> <label for="type_personal">Je suis le seul propriétaire des droits de propriété intellectuelle sur mes Soumissions et je ne fais pas de Soumissions dans le cadre de mon travail pour mon employeur. </label><br />
+<input type="radio" name="type" value="employer" id="type_employer" /> <label for="type_employer" >Je fais des Soumissions dans le cadre de mon travail pour mon employeur ou mon employeur a des droits de propriété intellectuelle sur mes soumissions en vertu d'un contrat ou de la législation applicable). J'ai la permission de mon employeur de faire des Soumissions et de conclure cet Accord au nom de mon employeur. En signant ci-dessous, j’accepte que le terme défini « Vous » s’applique à moi-même et à mon employeur. </label><br />
+<br /><br />
+<label for="input_name"> Nom (« Vous ») :</label> <input type="text" value="" name="name" id="input_name" class="form-control" required="required" /> <br />
+<label for="input_signature"> Signature :</label> <input type="text" value="" name="signature" id="input_signature" class="form-control" required="required" /> <br />
+<label for="input_username"> Utilisateur GitHubname:</label> <input type="text" value="" name="username" id="input_username" class="form-control" required="required" /> <br />
+<label for="input_email"> E-mail :</label> <input type="email" value="" name="email" id="input_email" class="form-control" required="required" /> <br />
+<label for="input_address"> Adresse :</label> <input type="text" value="" name="address" id="input_address" class="form-control" /> <br />
+
+<span id="company_span">
+<label for="input_company_name"> Nom de l’entreprise :</label> <input type="text" value="" name="company_name" id="input_company_name" class="form-control" /> <br />
+<label for="input_by"> Par :</label> <input type="text" value="" name="by" id="input_by" class="form-control"  /> <br />
+<label for="input_title">Titre :</label> <input type="text" value="" name="title" id="input_title" class="form-control" /> <br />
+</span>
+<button type="submit" name="Agree" value="Accepter" class="btn btn-black" id="cla_agree" role="button"> Accepter </button>
+</form>
+</div>
+<div id="cla_thankyou" style="display:none;"><div class="row"><div class="col" id="cla_thankyou_msg"></div></div></div>
+
+<style type="text/css">
+#cla_form input[type='radio']{
+  display: inline-block;
+  margin-right: 15px;
+}
+#cla_form label {
+  display: inline;
+}
+
+
+#cla_form input[type='text'],#cla_form input[type='email'] ,#cla_form input[type='date']  {
+  border-bottom: 1px solid #ccc !important;
+  width: 100%;
+}
+#cla_form  label {
+ font-weight: bold;
+}
+
+
+.btn, input[type=submit] {
+  display: inline-block;
+  vertical-align: middle;
+  font: inherit;
+  text-align: center;
+  margin: 0;
+  cursor: pointer;
+  font-size: 14px;
+  font-size: 1rem;
+  line-height: 1.4;
+  font-family: Sailec W00 Bold, Arial, sans-serif;
+  text-transform: uppercase;
+  padding: 1.14286rem 2.85714rem;
+  border-radius: 0;
+  letter-spacing: .10714rem;
+  white-space: normal;
+  border: 2px solid #212123 !important;
+  color: #212123;
+  background-color: transparent;
+  position: relative;
+  z-index: 1;
+  overflow: hidden;
+  transition: color .3s cubic-bezier(.5, 0, .1, 1), border-color .3s cubic-bezier(.5, 0, .1, 1);
+  will-change: color, border-color
+}
+
+@media (min-width:36em) {
+  .btn, input[type=submit] {
+    padding: 1.64286rem 3.92857rem
+  }
+}
+
+.btn:before, input[type=submit]:before {
+  content: "";
+  position: absolute;
+  top: 0;
+  left: 0;
+  z-index: -1;
+  height: 100%;
+  background-color: #212123;
+  transform-origin: top right;
+  width: 100%;
+  transform: translate3d(-101%, 0, 0);
+  transition: transform .3s cubic-bezier(.5, 0, .1, 1);
+  will-change: transform
+}
+
+.btn:focus, .btn:hover, input[type=submit]:focus, input[type=submit]:hover {
+  color: #fff
+}
+
+.btn:focus:before, .btn:hover:before, input[type=submit]:focus:before, input[type=submit]:hover:before {
+  transform: translateZ(0)
+}
+
+.btn-black, input[type=submit] {
+  color: #fff
+}
+
+.btn-black:before, input[type=submit]:before {
+  background-color: #fff
+}
+
+.btn-black:after, input[type=submit]:after {
+  content: "";
+  position: absolute;
+  top: 0;
+  left: 0;
+  z-index: -2;
+  height: 100%;
+  width: 100%;
+  background-color: #212123
+}
+
+.btn-black:focus, .btn-black:hover, input[type=submit]:focus, input[type=submit]:hover {
+  color: #212123
+}
+
+.btn-small {
+  padding: 1.07143rem 1.78571rem !important
+}
+#company_span {
+  display: none;
+}
+</style>
+<script type="text/javascript">
+  $(document).ready(function() {
+    var sub_url = '{{ site.cla_url }}';
+    var sub_key = 'N3cTZyz2ecLrAWfBJOzwJHOv47KD0PBX';
+    $('#cla_form').submit(function(e) {
+      var mform = $(this);
+      e.preventDefault();
+      $('#cla_form_div').hide();
+      var url = sub_url;
+
+      var jqxhr = $.ajax({
+        url: url,
+        method: "POST",
+        data: 'synckey=' + sub_key + '&' + mform.serialize()
+      }).done(function(r) {
+        $('#cla_thankyou').fadeIn("slow");
+        if (r['result'] == 'success') {
+          $('#cla_thankyou_msg').html('<h3>Thanks for agreeing to the CLA.</h3>');
+        }
+        else {
+          $('#cla_thankyou_msg').html('<h3>Sorry an error has occur.</h3>');
+          $('#cla_form_div').fadeIn("slow");
+        }
+      });
+    });
+
+
+    $("input[name='type']").click(function(e) {
+      var $this = $(this);
+      if ($this.val() === 'personal') {
+        $('#company_span').hide();
+      }
+      else {
+        $('#company_span').show();
+      }
+    });
+    $("#type_personal").trigger('click')
+  });
+</script>
diff --git a/_lang/fr_fr/_docs_pages/contributing.md b/_lang/fr_fr/_docs_pages/contributing.md
new file mode 100644
index 00000000000..77571b0cb2f
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/contributing.md
@@ -0,0 +1,7 @@
+---
+config_only: true
+noindex: true
+layout: redirect
+redirect_to: /docs/contributing/home
+permalink: contributing/
+---
\ No newline at end of file
diff --git a/_lang/fr_fr/_docs_pages/developer_guide.md b/_lang/fr_fr/_docs_pages/developer_guide.md
new file mode 100644
index 00000000000..be775ed582e
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/developer_guide.md
@@ -0,0 +1,7 @@
+---
+config_only: true
+noindex: true
+layout: redirect
+redirect_to: /docs/developer_guide/home/
+permalink: developer_guide/
+---
diff --git a/_lang/fr_fr/_docs_pages/help.md b/_lang/fr_fr/_docs_pages/help.md
new file mode 100644
index 00000000000..d6fbdf49f51
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/help.md
@@ -0,0 +1,7 @@
+---
+config_only: true
+noindex: true
+layout: redirect
+redirect_to: /docs/help/home/
+permalink: help/
+---
diff --git a/_lang/fr_fr/_docs_pages/home.md b/_lang/fr_fr/_docs_pages/home.md
new file mode 100644
index 00000000000..c0bd4867a79
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/home.md
@@ -0,0 +1,7 @@
+---
+config_only: true
+noindex: true
+layout: redirect
+redirect_to: /docs/
+permalink: home/
+---
diff --git a/_lang/fr_fr/_docs_pages/index.md b/_lang/fr_fr/_docs_pages/index.md
new file mode 100644
index 00000000000..bfbee64c384
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/index.md
@@ -0,0 +1,80 @@
+---
+permalink: /index.html
+page_order: 1
+hide_toc: true
+hide_nav: true
+hidden: true
+layout: doc_guide
+custom_collection: home
+nav_title: "Documentation"
+description: "Ceci est la page d’accueil du site de la documentation Braze. Vous trouverez ici des liens vers le guide utilisateur, le guide du développeur, le guide de l’API, la documentation sur nos technology partners et des articles d’aide. Vous y trouverez aussi des liens rapides vers des articles populaires et des ressources d’aide."
+
+doc_top_header: "Braze Documentation"
+doc_top_text: ""
+
+braze_learning: Technical terms and concepts explained through a mix of videos, lessons, and interactive exercises.
+
+doc_menu_list:
+  - name: User Guide
+    bg_color: '#3accdd'
+    image: /assets/img/braze_icons/users-01.svg
+    link: /docs/user_guide/introduction/
+    description: "Learn how to use the Braze platform to foster a more impactful customer experience."
+  - name: Developer Guide
+    bg_color: '#f7918e'
+    image: /assets/img/braze_icons/file-code-01.svg
+    link: /docs/developer_guide/home/
+    description: "Integrate and activate your app or site with the Braze SDK."
+  - name: Technology Partners
+    bg_color: '#ff9349'
+    image: /assets/img/braze_icons/settings-02.svg
+    link: /docs/partners/home/
+    description: "Our Technology Partners can help you customize your Braze experience and customer relationships."
+  - name: API Guide
+    bg_color: '#ff9349'
+    image: /assets/img/braze_icons/code-browser.svg
+    link: /docs/api/home/
+    description: "Braze provides a high-performance REST API to allow you to track users, send messages, export data, and more."
+  - name: Help
+    bg_color: '#ff9349'
+    image: /assets/img/braze_icons/info-circle.svg
+    link: /docs/help/home
+    description: "Find articles to help troubleshoot issues you may encounter and learn more about best practices to communicate with your users."
+  - name: Compliance Documentation
+    bg_color: '#ff9349'
+    image: /assets/img/braze_icons/certificate-01.svg
+    link: /docs/compliance_documentation/
+    description: "Compliance documentation outlines specific terms applicable to your purchased product or service."
+
+popular_topic_list:
+  - name: Braze API Dictionary
+    link: /docs/api/home/
+  - name: API Overview
+    link: /docs/api/basics/
+  - name: POST&#58; Track Users Endpoint
+    link: /docs/api/endpoints/user_data/post_user_track/
+  - name: User Import
+    link: /docs/user_guide/data_and_analytics/user_data_collection/user_import/
+  - name: Web SDK Setup
+    link: /docs/developer_guide/platform_integration_guides/web/initial_sdk_setup/
+  - name: Custom Events
+    link: /docs/user_guide/data_and_analytics/custom_data/custom_events/
+  - name: Custom Attributes
+    link: /docs/user_guide/data_and_analytics/custom_data/custom_attributes/
+  - name: Braze Currents
+    link: /docs/user_guide/data_and_analytics/braze_currents
+
+helpful_resources_list:
+  - name: Innovation Statement
+    link: /docs/innovation_statement/
+  - name: Entitlements, Support & Success Services Handbooks
+    link: /docs/handbooks/
+  - name: Data Retention
+    link: /docs/api/data_retention/
+  - name: Data Protection Technical Assistance
+    link: /docs/dp-technical-assistance/
+  - name: Release Notes
+    link: /docs/help/release_notes/
+  - name: Contributing to Braze Docs
+    link: /docs/contributing/home/
+---
diff --git a/_lang/fr_fr/_docs_pages/partners.md b/_lang/fr_fr/_docs_pages/partners.md
new file mode 100644
index 00000000000..d0c482eaa64
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/partners.md
@@ -0,0 +1,7 @@
+---
+config_only: true
+noindex: true
+layout: redirect
+redirect_to: /docs/partners/home/
+permalink: partners/
+---
diff --git a/_lang/fr_fr/_docs_pages/robots.txt b/_lang/fr_fr/_docs_pages/robots.txt
new file mode 100644
index 00000000000..2e96603bcb7
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/robots.txt
@@ -0,0 +1,21 @@
+---
+permalink: /robots.txt
+layout: bare
+---
+User-agent: Baiduspider
+User-agent: 360Spider
+User-agent: Yisouspider
+User-agent: PetalBot
+Disallow: /
+
+User-agent: Bytespider
+Disallow: /
+
+User-agent: Sogou web spider
+Disallow: /
+
+User-agent: Sogou inst spider
+Disallow: /
+
+User-agent: *
+Disallow: /
diff --git a/_lang/fr_fr/_docs_pages/search.md b/_lang/fr_fr/_docs_pages/search.md
new file mode 100644
index 00000000000..989ea43e2f9
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/search.md
@@ -0,0 +1,10 @@
+---
+nav_title: Recherche de Documentation
+hidden: true
+hide_nav: true
+permalink: /search/
+layout: basic
+---
+
+
+{% multi_lang_include search_page.html %}
diff --git a/_lang/fr_fr/_docs_pages/user_guide.md b/_lang/fr_fr/_docs_pages/user_guide.md
new file mode 100644
index 00000000000..47b2450b16b
--- /dev/null
+++ b/_lang/fr_fr/_docs_pages/user_guide.md
@@ -0,0 +1,7 @@
+---
+config_only: true
+noindex: true
+layout: redirect
+redirect_to: /docs/user_guide/introduction/
+permalink: user_guide/
+---
diff --git a/_lang/ja/_developer_guide/platform_integration_guides/android/analytics/tracking_sessions.md b/_lang/ja/_developer_guide/platform_integration_guides/android/analytics/tracking_sessions.md
index 48a7eefc986..e0c79af5eef 100644
--- a/_lang/ja/_developer_guide/platform_integration_guides/android/analytics/tracking_sessions.md
+++ b/_lang/ja/_developer_guide/platform_integration_guides/android/analytics/tracking_sessions.md
@@ -15,7 +15,7 @@ description: "このリファレンス記事では、Android または FireOS 
 
 ## セッションライフサイクル
 
-推奨の \[アクティビティライフサイクルコールバック統合]\[session_tracking_8] を使用して Braze を統合している場合は、アプリのアクティビティごとに `openSession()` と `closeSession()` が自動的に呼び出されます。デフォルトでは、Android のセッションは`openSession()`への最初の呼び出し時に開かれ、アプリがフォアグラウンドから10秒以上離れると閉じられます。`closeSession()`を呼び出しても、すぐにセッションを閉じるわけではないことに注意してください。むしろ、ユーザーが途中で`openSession()`を呼び出さないと (別のアクティビティに移動するなど)、10秒でセッションを閉じます。
+推奨の [アクティビティライフサイクルコールバック統合]\[session_tracking_8] を使用して Braze を統合している場合は、アプリのアクティビティごとに `openSession()` と `closeSession()` が自動的に呼び出されます。デフォルトでは、Android のセッションは`openSession()`への最初の呼び出し時に開かれ、アプリがフォアグラウンドから10秒以上離れると閉じられます。`closeSession()`を呼び出しても、すぐにセッションを閉じるわけではないことに注意してください。むしろ、ユーザーが途中で`openSession()`を呼び出さないと (別のアクティビティに移動するなど)、10秒でセッションを閉じます。
 
 Android セッションは、ホストアプリケーションからの通信がない状態で10秒後にタイムアウトします。つまり、ユーザーがアプリをバックグラウンドにして9秒後に戻ってきた場合、同じセッションが継続されます。なお、ユーザーがアプリをバックグラウンドで起動している間にセッションが終了してしまうと、アプリを再度開くまでそのデータがサーバーにフラッシュされないことがあります。
 
@@ -33,9 +33,9 @@ Android セッションは、ホストアプリケーションからの通信が
 
 ## セッショントラッキングをテストする
 
-ユーザーを介してセッションを検出するには、ダッシュボードでユーザーを見つけ、ユーザープロファイルの \[**アプリの利用状況**] に移動します。セッション指標が想定どおりに増加していることを確認することで、セッショントラッキングが機能していることを確認できます。
+ユーザーを介してセッションを検出するには、ダッシュボードでユーザーを見つけ、ユーザープロファイルの [**アプリの利用状況**] に移動します。セッション指標が想定どおりに増加していることを確認することで、セッショントラッキングが機能していることを確認できます。
 
-![発生したセッション数、アプリが最初に使用された日時、最後に使用された日時を示すユーザープロファイルコンポーネント。]\[session_tracking_7]
+![発生したセッション数、アプリが最初に使用された日時、最後に使用された日時を示すユーザープロファイルコンポーネント。] [session_tracking_7]
 
 ## セッション更新の購読
 
@@ -70,6 +70,6 @@ Braze.getInstance(this).subscribeToSessionUpdates { message ->
 {% endtabs %}
 
 [1]: https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze/-i-braze/subscribe-to-session-updates.html
-\[session_tracking_3]: {{ site.baseurl }}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/#step-2-configure-the-braze-sdk-in-brazexml
-\[session_tracking_7] ： {% image_buster /assets/img_archive/test_session.png %}
-\[session_tracking_8] ： {{ site.baseurl }}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/#step-4-tracking-user-sessions-in-android
+[session_tracking_3]: {{ site.baseurl }}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/#step-2-configure-the-braze-sdk-in-brazexml
+[session_tracking_7] ： {% image_buster /assets/img_archive/test_session.png %}
+[session_tracking_8] ： {{ site.baseurl }}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/#step-4-tracking-user-sessions-in-android
diff --git a/_lang/ja/_developer_guide/platform_integration_guides/android/in-app_messaging/troubleshooting.md b/_lang/ja/_developer_guide/platform_integration_guides/android/in-app_messaging/troubleshooting.md
index c5fc0f9ee0a..bd93c222a85 100644
--- a/_lang/ja/_developer_guide/platform_integration_guides/android/in-app_messaging/troubleshooting.md
+++ b/_lang/ja/_developer_guide/platform_integration_guides/android/in-app_messaging/troubleshooting.md
@@ -27,7 +27,7 @@ channel:
 
 ## 予期したアプリ内メッセージが表示されなかった
 
-ほとんどのアプリ内メッセージの問題は、配信と表示の 2 つの主要なカテゴリに分けることができます。予想されるアプリ内メッセージがデバイスで表示されない原因をトラブルシューティングするには、まず、\[アプリ内メッセージがデバイスに配信された]\[troubleshooting_iams_11] ことを確認してから\[メッセージ表示のトラブルシューティング] \[troubleshooting_iams_12] を行う必要があります。
+ほとんどのアプリ内メッセージの問題は、配信と表示の 2 つの主要なカテゴリに分けることができます。予想されるアプリ内メッセージがデバイスで表示されない原因をトラブルシューティングするには、まず、[アプリ内メッセージがデバイスに配信された][troubleshooting_iams_11] ことを確認してから[メッセージ表示のトラブルシューティング] [troubleshooting_iams_12] を行う必要があります。
 
 ## アプリ内メッセージ配信 {#troubleshooting-in-app-message-delivery}
 
@@ -35,52 +35,52 @@ SDK はセッション開始時に Braze サーバーからアプリ内メッセ
 
 ### メッセージが要求され、返されたかどうかを確認する
 
-1. ダッシュボードの\[test user]\[troubleshooting_iams_1] ] として自分を追加する。
+1. ダッシュボードの[test user][troubleshooting_iams_1] として自分を追加する。
 2. ユーザーを対象としたアプリ内メッセージキャンペーンを設定します。
 3. アプリケーションで新しいセッションが発生することを確認します。
-4. \[イベントユーザーログ]\[troubleshooting_iams_3] を使用して、セッション開始時にデバイスがアプリ内メッセージを要求していることを確認します。テストユーザーのセッション開始イベントに関連付けられた SDK リクエストを見つけます。
-  - トリガーされたアプリ内メッセージをリクエストするためのアプリであれば、\[**レスポンスデータ**] の \[**リクエスト済みレスポンス**] フィールドに `trigger` が表示されます。
-  - アプリが元のアプリ内メッセージをリクエストするためのものだった場合、\[**レスポンスデータ］**] の \[**リクエスト済みレスポンス**] フィールドに `in_app` が表示されます。
-5. \[イベントユーザーログ] \[troubleshooting_iams_3] を使用して、応答データで正しいアプリ内メッセージが返されるかどうかを確認します。<br>![]\[troubleshooting_iams_5]
+4. [イベントユーザーログ][troubleshooting_iams_3] を使用して、セッション開始時にデバイスがアプリ内メッセージを要求していることを確認します。テストユーザーのセッション開始イベントに関連付けられた SDK リクエストを見つけます。
+  - トリガーされたアプリ内メッセージをリクエストするためのアプリであれば、[**レスポンスデータ**] の [**リクエスト済みレスポンス**] フィールドに `trigger` が表示されます。
+  - アプリが元のアプリ内メッセージをリクエストするためのものだった場合、[**レスポンスデータ］**] の [**リクエスト済みレスポンス**] フィールドに `in_app` が表示されます。
+5. [イベントユーザーログ] [troubleshooting_iams_3] を使用して、応答データで正しいアプリ内メッセージが返されるかどうかを確認します。<br>![][troubleshooting_iams_5]
 
 #### リクエストされていないメッセージのトラブルシューティング
 
 アプリ内メッセージがリクエストされていない場合、アプリ内メッセージはセッション開始時にリフレッシュされるため、アプリがセッションを正しくトラッキングしていない可能性があります。また、アプリのセッションタイムアウトセマンティクスに基づいて、アプリが実際にセッションを開始していることを確認してください:
 
-![]\[troubleshooting_iams_10] セッション開始イベントが成功したことを示すイベントユーザーログでSDKリクエストが見つかった。]
+![] [troubleshooting_iams_10] セッション開始イベントが成功したことを示すイベントユーザーログでSDKリクエストが見つかった。
 
 ### メッセージが返されない問題のトラブルシューティング
 
 アプリ内メッセージが返されない場合、キャンペーンターゲティングの問題が発生している可能性があります。
 
 - セグメントにユーザーが含まれていない。
-  - ユーザーの\[\*\*Engagement**]\[troubleshooting_iams_6] ] タブで、**\[Segments]の**下に正しいセグメントが表示されているか確認する。
+  - ユーザーの[**Engagement**] [troubleshooting_iams_6]  タブで、** [Segments]の**下に正しいセグメントが表示されているか確認する。
 - ユーザーが以前にアプリ内メッセージを受け取ったことがあり、再度受け取る資格がなかった。
-  - **キャンペーン作成ツール**の**配信**ステップの \[キャンペーン再適格性設定] \[troubleshooting_iams_7] を確認し、再適格性設定がテスト設定と整合していることを確認します。
+  - **キャンペーン作成ツール**の**配信**ステップの [キャンペーン再適格性設定] [troubleshooting_iams_7] を確認し、再適格性設定がテスト設定と整合していることを確認します。
 - ユーザーがキャンペーンのフリークエンシーキャップに達した。
-  - キャンペーン\[フリークエンシーキャップ設定] \[troubleshooting_iams_8] を確認し、テスト設定と整合していることを確認します。
+  - キャンペーン [フリークエンシーキャップ設定]  [troubleshooting_iams_8] を確認し、テスト設定と整合していることを確認します。
 - キャンペーンにコントロールグループが存在した場合、ユーザーがコントロールグループに分類された可能性があります。
-  - キャンペーンバリアントが \[**制御**] に設定されている受信キャンペーンバリアントフィルターでセグメントを作成し、ユーザーがそのセグメントに分類されたかどうかを確認することで、これが発生したかどうかを確認できます。
+  - キャンペーンバリアントが  [**制御**] に設定されている受信キャンペーンバリアントフィルターでセグメントを作成し、ユーザーがそのセグメントに分類されたかどうかを確認することで、これが発生したかどうかを確認できます。
   - 統合テスト目的でキャンペーンを作成する場合は、コントロールグループの追加をオプトアウトしてください。
 
 ## アプリ内メッセージ表示 {#troubleshooting-in-app-message-display}
 
 アプリがアプリ内メッセージのリクエストと受信に成功しているのに表示されない場合は、デバイス側のロジックによって表示が妨げられている可能性があります。
 
-- トリガーされたアプリ内メッセージは、\[トリガー間の最小時間間隔]]\[troubleshooting_iams_9] (デフォルトは30秒) に基づいてレート制限されます。
+- トリガーされたアプリ内メッセージは、[トリガー間の最小時間間隔] [troubleshooting_iams_9] (デフォルトは30秒) に基づいてレート制限されます。
 - アプリ内メッセージ処理をカスタマイズするようにデリゲートを設定している場合は、デリゲートがアプリ内メッセージ表示に影響していないことを確認してください。
 - 画像のダウンロードに失敗すると、画像付きのアプリ内メッセージが表示されなくなります。`BrazeInAppMessageManager` が正しく登録されていない場合、画像のダウンロードは常に失敗します。画像のダウンロードに失敗していないか、デバイスのログを確認してください。
 - 端末の向きがアプリ内メッセージで指定された向きと一致しなかった場合、アプリ内メッセージは表示されません。デバイスの向きが正しいことを確認してください。
 
-\[troubleshooting_iams_1]: {{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#adding-test-users
-\[troubleshooting_iams_2]:{{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab
-\[troubleshooting_iams_3]:{{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab
-\[troubleshooting_iams_4]: #session-tracking
-\[troubleshooting_iams_5]:  {% image_buster /assets/img_archive/event_user_log_iams.png %}
-\[troubleshooting_iams_6]:{{ site.baseurl }}/user_guide/engagement_tools/segments/using_user_search/#engagement-tab
-\[troubleshooting_iams_7]:{{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/
-\[troubleshooting_iams_8]:{{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping
-\[troubleshooting_iams_9]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers
-\[troubleshooting_iams_10]: {% image_buster /assets/img_archive/event_user_log_session_start.png %}
-\[troubleshooting_iams_11]: #troubleshooting-in-app-message-delivery
-\[troubleshooting_iams_12]: #troubleshooting-in-app-message-display
+[troubleshooting_iams_1]: {{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#adding-test-users
+[troubleshooting_iams_2]:{{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab
+[troubleshooting_iams_3]:{{ site.baseurl }}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab
+[troubleshooting_iams_4]: #session-tracking
+[troubleshooting_iams_5]:  {% image_buster /assets/img_archive/event_user_log_iams.png %}
+[troubleshooting_iams_6]:{{ site.baseurl }}/user_guide/engagement_tools/segments/using_user_search/#engagement-tab
+[troubleshooting_iams_7]:{{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/
+[troubleshooting_iams_8]:{{ site.baseurl }}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping
+[troubleshooting_iams_9]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers
+[troubleshooting_iams_10]: {% image_buster /assets/img_archive/event_user_log_session_start.png %}
+[troubleshooting_iams_11]: #troubleshooting-in-app-message-delivery
+[troubleshooting_iams_12]: #troubleshooting-in-app-message-display
diff --git a/_lang/ja/_developer_guide/platform_integration_guides/android/initial_sdk_setup/accessibility.md b/_lang/ja/_developer_guide/platform_integration_guides/android/initial_sdk_setup/accessibility.md
index 6593bfec931..fff0dd735b0 100644
--- a/_lang/ja/_developer_guide/platform_integration_guides/android/initial_sdk_setup/accessibility.md
+++ b/_lang/ja/_developer_guide/platform_integration_guides/android/initial_sdk_setup/accessibility.md
@@ -18,14 +18,14 @@ description: "この参考記事では、Android または FireOS アプリケ
 Android の読み上げ / 「VoiceOver」で、アプリ内メッセージの表示中にその背後にある内容が読み取られないようにするには、以下の SDK 設定を有効にしてください。
 
 {% tabs %}
-{% tab braze.xml %}
+{% tab Braze XML %}
 
 ```xml
 <bool name="com_braze_device_in_app_message_accessibility_exclusive_mode_enabled">true</bool>
 ```
 
 {% endtab %}
-{% tab KOTLIN %}
+{% tab Kotlin %}
 
 ```kotlin
 val brazeConfigBuilder = BrazeConfig.Builder()
@@ -34,7 +34,7 @@ Braze.configure(this, brazeConfigBuilder.build())
 ```
 
 {% endtab %}
-{% tab JAVA %}
+{% tab Java %}
 
 ```java
 BrazeConfig.Builder brazeConfigBuilder = new BrazeConfig.Builder()
diff --git a/_lang/ja/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/huawei_integration.md b/_lang/ja/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/huawei_integration.md
index 13d5746f3e5..38d55832cbc 100644
--- a/_lang/ja/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/huawei_integration.md
+++ b/_lang/ja/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/huawei_integration.md
@@ -11,34 +11,34 @@ channel:
 
 # Huawei のプッシュ統合
 
-> [Huawei][1] 製の新しいスマートフォンには、プッシュ配信に使用されるサービス、Huawei Mobile Services (HMS) が、Google の Firebase Cloud Messaging (FCM) の代わりに搭載されています。<br><br>このガイドでは、Braze 経由でプッシュを送信し、セグメンテーション、分析、キャンバスなどの既存の Braze 機能をフルに活用できるように Huawei Android 統合を設定する方法について説明します。
+> [Huawei](https://huaweimobileservices.com/) 製の新しいスマートフォンには、プッシュ配信に使用されるサービス、Huawei Mobile Services (HMS) が、Google の Firebase Cloud Messaging (FCM) の代わりに搭載されています。<br><br>このガイドでは、Braze 経由でプッシュを送信し、セグメンテーション、分析、キャンバスなどの既存の Braze 機能をフルに活用できるように Huawei Android 統合を設定する方法について説明します。
 
-## ステップ1:Huawei 開発者アカウントに登録する
+## ステップ 1:Huawei 開発者アカウントに登録する
 
-始める前に、[Huawei 開発者アカウント][2]への登録と設定が必要です。Huawei アカウントで、**\[My Projects] > \[Project Settings] > \[App Information]** に移動し、`App ID` と`App secret` を書き留めます。
+始める前に、[Huawei 開発者アカウント](https://developer.huawei.com/consumer/en/console)への登録と設定が必要です。Huawei アカウントで、**[My Projects] > [Project Settings] > [App Information]** に移動し、`App ID` と`App secret` を書き留めます。
 
-![][3]
+![]({% image_buster /assets/img/huawei/huawei-credentials.png %})
 
-## ステップ2:Braze ダッシュボードで新しい Huawei アプリを作成する
+## ステップ 2: Braze ダッシュボードで新しい Huawei アプリを作成する
 
-Braze ダッシュボードで、\[**設定**] ナビゲーションの下にある \[**アプリ設定**] に移動します。
+Braze ダッシュボードで、[**設定**] ナビゲーションの下にある [**アプリ設定**] に移動します。
 
-\[**\+ アプリ**] をクリックし、名前 (My Huawei App など) を入力し、プラットフォームとして `Android` を選択します。
+[**+ アプリ**] をクリックし、名前 (My Huawei App など) を入力し、プラットフォームとして `Android` を選択します。
 
-![][4]{: style="max-width:60%;"}
+![]({% image_buster /assets/img/huawei/huawei-create-app.png %}){: style="max-width:60%;"}
 
 新しい Braze アプリを作成したら、プッシュ通知設定を見つけて、プッシュプロバイダーとして `Huawei` を選択します。次に、`Huawei Client Secret` と `Huawei App ID` を指定します。
 
-![][12]
+![]({% image_buster /assets/img/huawei/huawei-dashboard-credentials.png %})
 
-## ステップ3:Huawei メッセージング SDK をアプリに統合する
+## ステップ 3: Huawei メッセージング SDK をアプリに統合する
 
-Huawei は、Huawei Messaging Service をアプリケーションに統合する \[Android 統合codelab][13] を提供しています。以下の手順に従って開始してください。
+Huawei は、Huawei Messaging Service をアプリケーションに統合する Android 統合codelab[](https://developer.huawei.com/consumer/en/codelab/HMSPushKit/index.html) を提供しています。以下の手順に従って開始してください。
 
-codelab が完了したら、カスタムの \[Huawei Message Service][14] を作成してプッシュトークンを取得し、メッセージを Braze SDK に転送する必要があります。
+codelab が完了したら、カスタムの [Huawei Message Service[](https://developer.huawei.com/consumer/en/doc/development/HMS-References/push-HmsMessageService-cls) を作成してプッシュトークンを取得し、メッセージを Braze SDK に転送する必要があります。
 
 {% tabs %}
-{% tab JAVA %}
+{% tab Java %}
 
 ```java
 public class CustomPushService extends HmsMessageService {
@@ -59,7 +59,7 @@ public class CustomPushService extends HmsMessageService {
 ```
 
 {% endtab %}
-{% tab KOTLIN %}
+{% tab Kotlin %}
 
 ```kotlin
 class CustomPushService: HmsMessageService() {
@@ -100,19 +100,19 @@ class CustomPushService: HmsMessageService() {
 
 ### 新しいプッシュ通知キャンペーンを作成する
 
-\[**キャンペーン**] ページで、新しいキャンペーンを作成し、メッセージタイプとして \[**プッシュ通知**] を選択します。
+[**キャンペーン**] ページで、新しいキャンペーンを作成し、メッセージタイプとして [**プッシュ通知**] を選択します。
 
-キャンペーンに名前を付けたら、プッシュプラットフォームとして \[**Android プッシュ通知**] を選択します。
+キャンペーンに名前を付けたら、プッシュプラットフォームとして [**Android プッシュ通知**] を選択します。
 
-![利用可能なプッシュ・プラットフォームを表示するキャンペーン作成コンポーザー。][5]
+![使用可能なプッシュプラットフォームを表示するキャンペーン登録コンポーザ。]({% image_buster /assets/img/huawei/huawei-test-push-platforms.png %})
 
 次に、タイトルとメッセージを付けてプッシュキャンペーンを作成します。
 
 ### テストプッシュを送信する
 
-**Test]**タブで、\[`changeUser(USER_ID_STRING)` method][9]]を使ってアプリに設定したユーザーIDを入力し、\[**Send Test]**をクリックしてテストプッシュを送信する。
+**Test]**タブで、\[[]({{site.baseurl}}/developer_guide/platform_integration_guides/android/analytics/setting_user_ids/#assigning-a-user-id) method`changeUser(USER_ID_STRING)`]を使ってアプリに設定したユーザーIDを入力し、[**Send Test]**をクリックしてテストプッシュを送信する。
 
-![キャンペーン作成コンポーザーのテストタブを見ると、ユーザーIDを入力し、「個人ユーザーを追加」フィールドに入力することで、自分自身にテストメッセージを送信できることがわかる。][7]
+![キャンペーン作成コンポーザーのテストタブを見ると、ユーザーIDを入力し、「個人ユーザーを追加」フィールドに入力することで、自分自身にテストメッセージを送信できることがわかる。]({% image_buster /assets/img/huawei/huawei-test-send.png %})
 
 この時点で、Braze から Huawei (HMS) デバイスにテストプッシュ通知が届くはずです。
 
@@ -120,27 +120,13 @@ class CustomPushService: HmsMessageService() {
 
 Braze ダッシュボードの Huawei アプリは Android プッシュプラットフォーム上に構築されているため、すべての Android ユーザー (Firebase Cloud Messaging および Huawei Mobile Services) にプッシュを送信するか、キャンペーンオーディエンスを特定のアプリにセグメント化するかを柔軟に選択できます。
 
-Huawei アプリのみにプッシュを送信するには、\[新しいセグメントを作成][15] して、\[**アプリ**] セクション内で Huawei アプリを選択します。
+Huaweiアプリのみにプッシュを送信するには、[新しいSegment]({{ site.baseurl }}/user_guide/engagement_tools/segments/creating_a_segment/#step-3-choose-your-app-or-platform)を作成し、**Apps**セクションでHuaweiアプリを選択します。
 
-![][8]
+![]({% image_buster /assets/img/huawei/huawei-segmentation.png %})
 
 もちろん、すべての Android プッシュプロバイダーに同じプッシュを送信する場合は、アプリを指定しないことを選択することで、現在のワークスペース内で設定されているすべての Android アプリに送信できます。
 
 ## 分析
 
-キャンペーンが開始されると、キャンペーンの分析または Android プッシュ用に集計されたキャンバスが表示されます。Androidのプッシュ分析と設定の詳細については、\[プッシュユーザーガイド][10] ]を参照のこと。
-
-[1]: https://huaweimobileservices.com/
-[2]: https://developer.huawei.com/consumer/en/console
-[3]: {% image_buster /assets/img/huawei/huawei-credentials.png %}
-[4]: {% image_buster /assets/img/huawei/huawei-create-app.png %}
-[5]: {% image_buster /assets/img/huawei/huawei-test-push-platforms.png %}
-[6]: {% image_buster /assets/img/huawei/huawei-test-push-composer.png %}
-[7]: {% image_buster /assets/img/huawei/huawei-test-send.png %}
-[8]: {% image_buster /assets/img/huawei/huawei-segmentation.png %}
-/developer_ guide/platform_integration_guides/android/analytics/setting_user_ids/#assigning-a-user-id
-[10]: {{site.baseurl}}/user_guide/message_building_by_channel/push/push_reporting/
-[12]: {% image_buster /assets/img/huawei/huawei-dashboard-credentials.png %}
-[13]: https://developer.huawei.com/consumer/en/codelab/HMSPushKit/index.html
-[14]: https://developer.huawei.com/consumer/en/doc/development/HMS-References/push-HmsMessageService-cls
-[15]: {{ site.baseurl }}/user_guide/engagement_tools/segments/creating_a_segment/#step-3-choose-your-app-or-platform
+キャンペーンが開始されると、キャンペーンの分析または Android プッシュ用に集計されたキャンバスが表示されます。Android プッシュアナリティクスと設定の詳細については、[プッシュユーザーガイド]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_reporting/) を参照してください。
+
diff --git a/_lang/ja/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md b/_lang/ja/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md
index 37ac672c669..04e52e39217 100644
--- a/_lang/ja/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md
+++ b/_lang/ja/_developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging.md
@@ -29,9 +29,9 @@ Firebase Cloud Messaging (FCM) API には、1分当たりに600,000リクエス
 
 ![Google Cloud プロジェクトのホームページで「プロジェクトID」が強調表示されています。]({% image_buster /assets/img/android/push_integration/migration/verify-project-id/project-id-gcp.png %})
 
-次に、Firebase Console を開き、<i class="fa-solid fa-gear"></i>\[**設定**] > \[**プロジェクト設定**] を選択します。
+次に、Firebase Console を開き、<i class="fa-solid fa-gear"></i>[**設定**] > [**プロジェクト設定**] を選択します。
 
-![\[設定] メニューが開いた状態の Firebase プロジェクト。]({% image_buster /assets/img/android/push_integration/set_up_automatic_token_registration/select-project-settings.png %})
+![[設定] メニューが開いた状態の Firebase プロジェクト。]({% image_buster /assets/img/android/push_integration/set_up_automatic_token_registration/select-project-settings.png %})
 
 「**一般**」タブで、「**プロジェクトID**」がGoogle Cloudプロジェクトに記載されているものと一致していることを確認します。
 
@@ -41,19 +41,19 @@ Firebase Cloud Messaging (FCM) API には、1分当たりに600,000リクエス
 
 まず、Braze を開き、<i class="fa-solid fa-gear"></i>\[**設定**] > \[**アプリ設定**] を選択します。
 
-![\[アプリ設定] が強調表示された状態で Braze で \[設定] メニューが開いています。]({% image_buster /assets/img/android/push_integration/upload_json_credentials/select-app-settings.png %}){: style="max-width:80%;"}
+![[アプリ設定] が強調表示された状態で Braze で [設定] メニューが開いています。]({% image_buster /assets/img/android/push_integration/upload_json_credentials/select-app-settings.png %}){: style="max-width:80%;"}
 
-Android アプリの \[**プッシュ通知の設定**] で、\[**Firebase Cloud Messaging の送信者 ID**] フィールドの番号を確認します。次にこれを Firebase プロジェクトのものと比較します。
+Android アプリの [**プッシュ通知の設定**] で、[**Firebase Cloud Messaging の送信者 ID**] フィールドの番号を確認します。次にこれを Firebase プロジェクトのものと比較します。
 
 ![「プッシュ通知設定」のフォームです。]({% image_buster /assets/img/android/push_integration/migration/verify-sender-id/verify-sender-id.png %})
 
-次に、Firebase Console を開き、<i class="fa-solid fa-gear"></i>\[**設定**] > \[**プロジェクト設定**] を選択します。
+次に、Firebase Console を開き、<i class="fa-solid fa-gear"></i>[**設定**] > [**プロジェクト設定**] を選択します。
 
-![\[設定] メニューが開いた状態の Firebase プロジェクト。]({% image_buster /assets/img/android/push_integration/set_up_automatic_token_registration/select-project-settings.png %})
+![[設定] メニューが開いた状態の Firebase プロジェクト。]({% image_buster /assets/img/android/push_integration/set_up_automatic_token_registration/select-project-settings.png %})
 
-\[**Cloud Messaging**] を選択します。\[**Cloud Messaging API (レガシー)**] で、**送信者 ID** が Braze ダッシュボードに表示されているものと一致していることを確認します。
+[**Cloud Messaging**] を選択します。[**Cloud Messaging API (レガシー)**] で、**送信者 ID** が Braze ダッシュボードに表示されているものと一致していることを確認します。
 
-![\[送信者 ID] が強調表示されている Firebase プロジェクトの「Cloud Messaging」ページ。]({% image_buster /assets/img/android/push_integration/migration/verify-sender-id/verify-sender-id-firebase.png %})
+![[送信者 ID] が強調表示されている Firebase プロジェクトの「Cloud Messaging」ページ。]({% image_buster /assets/img/android/push_integration/migration/verify-sender-id/verify-sender-id-firebase.png %})
 
 ### ステップ3:Firebase Cloud Messaging API を有効にする
 
@@ -63,25 +63,25 @@ Google Cloud で、Android アプリが使用しているプロジェクトを
 
 ### ステップ4: サービスアカウントを作成する
 
-次に、新しいサービスアカウントを作成し、FCM トークンの登録時に Braze が許可された API 呼び出しを行えるようにします。Google Cloud で、\[**サービスアカウント**] に移動し、プロジェクトを選択します。\[**サービスアカウント**] ページで \[**サービスアカウントの作成**] を選択します。
+次に、新しいサービスアカウントを作成し、FCM トークンの登録時に Braze が許可された API 呼び出しを行えるようにします。Google Cloud で、[**サービスアカウント**] に移動し、プロジェクトを選択します。[**サービスアカウント**] ページで [**サービスアカウントの作成**] を選択します。
 
 ![「サービス アカウントの作成」が強調表示されたプロジェクトのサービス アカウントのホーム ページ。]({% image_buster /assets/img/android/push_integration/create_a_service_account/select-create-service-account.png %})
 
-サービスアカウント名、ID、説明を入力して、\[**作成して続行**] を選択します。
+サービスアカウント名、ID、説明を入力して、[**作成して続行**] を選択します。
 
-![\[サービスアカウントの詳細] のフォーム。]({% image_buster /assets/img/android/push_integration/create_a_service_account/enter-service-account-details.png %})
+![[サービスアカウントの詳細] のフォーム。]({% image_buster /assets/img/android/push_integration/create_a_service_account/enter-service-account-details.png %})
 
-\[**ロール**] フィールドで、ロールのリストから \[**Firebase Cloud Messaging API 管理者**] を見つけて選択します。アクセスをより制限する場合は、`cloudmessaging.messages.create` 権限を持つ[カスタムロール](https://cloud.google.com/iam/docs/creating-custom-roles)を作成し、代わりにリストからそれを選択します。\[**完了**] を選択します。
+[**ロール**] フィールドで、ロールのリストから [**Firebase Cloud Messaging API 管理者**] を見つけて選択します。アクセスをより制限する場合は、`cloudmessaging.messages.create` 権限を持つ[カスタムロール](https://cloud.google.com/iam/docs/creating-custom-roles)を作成し、代わりにリストからそれを選択します。[**完了**] を選択します。
 
 {% alert warning %}
-\[_Firebase Cloud Messaging 管理者_] ではなく、\[_Firebase Cloud Messaging **API** 管理者_] を選択してください。
+[_Firebase Cloud Messaging 管理者_] ではなく、[_Firebase Cloud Messaging **API** 管理者_] を選択してください。
 {% endalert %}
 
-![\[Firebase Cloud Messaging API 管理者] がロールとして選択されている、「このサービスアカウントにプロジェクトへのアクセス権を付与」するためのフォーム。]({% image_buster /assets/img/android/push_integration/create_a_service_account/add-fcm-api-admin.png %})
+![[Firebase Cloud Messaging API 管理者] がロールとして選択されている、「このサービスアカウントにプロジェクトへのアクセス権を付与」するためのフォーム。]({% image_buster /assets/img/android/push_integration/create_a_service_account/add-fcm-api-admin.png %})
 
 ### ステップ5:権限を確認する（オプション）
 
-サービスアカウントが持っている権限を確認するには、Google Cloud を開き、プロジェクトに移動して、\[**IAM**] を選択します。**プリンシパル別に表示** で、**過剰な権限** を選択します。
+サービスアカウントが持っている権限を確認するには、Google Cloud を開き、プロジェクトに移動して、[**IAM**] を選択します。**プリンシパル別に表示** で、**過剰な権限** を選択します。
 
 ![各プリンシパルごとに過剰な権限の数が一覧表示される「原則別表示」タブ。]({% image_buster /assets/img/android/push_integration/create_a_service_account/select-excess-permissions.png %})
 
@@ -91,19 +91,19 @@ Google Cloud で、Android アプリが使用しているプロジェクトを
 
 ### ステップ 6:JSON 認証情報を生成する
 
-次に、FCM サービスアカウントの JSON 認証情報を生成します。Google Cloud IAM & Admin で、\[**サービスアカウント**] に移動し、プロジェクトを選択します。[先ほど作成した](#step-4-create-a-service-account) FCM サービスアカウントを見つけて、<i class="fa-solid fa-ellipsis-vertical"></i>\[**アクション**] > \[**キーの管理**] を選択します。
+次に、FCM サービスアカウントの JSON 認証情報を生成します。Google Cloud IAM & Admin で、[**サービスアカウント**] に移動し、プロジェクトを選択します。[先ほど作成した](#step-4-create-a-service-account) FCM サービスアカウントを見つけて、<i class="fa-solid fa-ellipsis-vertical"></i>[**アクション**] > [**キーの管理**] を選択します。
 
-![\[アクション] メニューが開いた状態の、プロジェクトのサービスアカウントホームページ。]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-manage-keys.png %})
+![[アクション] メニューが開いた状態の、プロジェクトのサービスアカウントホームページ。]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-manage-keys.png %})
 
-\[**キーの追加**] > \[**新しいキーを作成**] を選択します。
+[**キーの追加**] > [**新しいキーを作成**] を選択します。
 
 {% alert note %}
-新しいキーを作成しても、レガシーキーは削除されません。\[**認証情報を元に戻す**] を選択して誤って新しいキーを削除した場合、Braze はバックアップとしてレガシーキーを使用します。
+新しいキーを作成しても、レガシーキーは削除されません。[**認証情報を元に戻す**] を選択して誤って新しいキーを削除した場合、Braze はバックアップとしてレガシーキーを使用します。
 {% endalert %}
 
-![\[キーを追加] メニューが開いた状態の選択されたサービスアカウント。]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-create-new-key.png %})
+![[キーを追加] メニューが開いた状態の選択されたサービスアカウント。]({% image_buster /assets/img/android/push_integration/generate_json_credentials/select-create-new-key.png %})
 
-\[**JSON**] を選択し、\[**作成**] を選択します。FCM プロジェクト ID とは異なる Google Cloud のプロジェクト ID を使用してサービスアカウントを作成した場合は、JSON ファイルで `project_id` に割り当てられた値を手動で更新する必要があります。
+[**JSON**] を選択し、[**作成**] を選択します。FCM プロジェクト ID とは異なる Google Cloud のプロジェクト ID を使用してサービスアカウントを作成した場合は、JSON ファイルで `project_id` に割り当てられた値を手動で更新する必要があります。
 
 キーをどこにダウンロードしたかを覚えておいてください。次のステップで必要になります。
 
@@ -115,13 +115,13 @@ Google Cloud で、Android アプリが使用しているプロジェクトを
 
 ### ステップ 7: JSON の認証情報を Braze にアップロードする
 
-Braze で、<i class="fa-solid fa-gear"></i>\[**設定**] > \[**アプリの設定**] を選択します。
+Braze で、<i class="fa-solid fa-gear"></i>[**設定**] > [**アプリの設定**] を選択します。
 
-![\[アプリ設定] が強調表示された状態で Braze で \[設定] メニューが開いています。]({% image_buster /assets/img/android/push_integration/upload_json_credentials/select-app-settings.png %})
+![\[アプリ設定] が強調表示された状態で Braze で [設定] メニューが開いています。]({% image_buster /assets/img/android/push_integration/upload_json_credentials/select-app-settings.png %})
 
-\[**プッシュ通知の設定**] で \[**JSON ファイルのアップロード**] を選択し、[先ほど生成した](#step-6-generate-json-credentials)ファイルを選択します。完了したら、\[**保存**] を選択します。
+[**プッシュ通知の設定**] で [**JSON ファイルのアップロード**] を選択し、[先ほど生成した](#step-6-generate-json-credentials)ファイルを選択します。完了したら、[**保存**] を選択します。
 
-![\[Firebase Cloud Messaging サーバーキー] フィールドで秘密キーが更新されている \[プッシュ通知設定] のフォーム。]({% image_buster /assets/img/android/push_integration/migration/upload_json_credentials/upload-json-file.png %})
+![[Firebase Cloud Messaging サーバーキー] フィールドで秘密キーが更新されている [プッシュ通知設定] のフォーム。]({% image_buster /assets/img/android/push_integration/migration/upload_json_credentials/upload-json-file.png %})
 
 {% alert warning %}
 秘密キーが漏洩した場合は、セキュリティリスクが生じる可能性があります。キーが Braze にアップロードされたので、[先に生成した](#step-6-generate-json-credentials)ファイルをコンピューターから削除します。
@@ -141,7 +141,7 @@ Braze で、<i class="fa-solid fa-gear"></i>\[**設定**] > \[**アプリの設
 
 いつでも、新しい認証情報を削除し、レガシー認証情報を復元できます。認証情報が復元されるとすぐに、代わりに新しい認証情報を使用してプッシュ通知の送信を始めることができます。
 
-Braze で、<i class="fa-solid fa-gear"></i>\[**設定**] > \[**アプリの設定**] を選択します。**プッシュ通知設定**で、**資格情報を元に戻す**を選択します。
+Braze で、<i class="fa-solid fa-gear"></i>[**設定**] > [**アプリの設定**] を選択します。**プッシュ通知設定**で、**資格情報を元に戻す**を選択します。
 
 {% alert warning %}
 新しい認証情報を削除すると、後で復元することはできません。[新しい認証情報を生成](#step-6-generate-json-credentials)し、もう一度[それらを Braze にアップロード](#step-7-upload-your-json-credentials-to-braze)する必要があります。
diff --git a/_lang/ja/_developer_guide/platform_integration_guides/swift/push_notifications/integration.md b/_lang/ja/_developer_guide/platform_integration_guides/swift/push_notifications/integration.md
index 7ba36eb66ed..22cbf2f1ef7 100644
--- a/_lang/ja/_developer_guide/platform_integration_guides/swift/push_notifications/integration.md
+++ b/_lang/ja/_developer_guide/platform_integration_guides/swift/push_notifications/integration.md
@@ -361,7 +361,7 @@ BRZCancellable *cancellable = [notifications subscribeToUpdatesWithPayloadTypes:
 自動プッシュ統合を使用する場合、Braze によって処理されるリモート通知を受信する唯一の方法は `subscribeToUpdates(_:)` です。`UIAppDelegate` と `UNUserNotificationCenterDelegate` システムメソッドは、通知が Braze によって自動的に処理されるときには呼び出されません。
 {% endalert %}
 
-## {#push-testing} のテスト
+## のテスト {#push-testing}
 
 コマンドラインからアプリ内通知とプッシュ通知をテストする場合は、CURL と \[メッセージング API][29] を介してターミナルから単一の通知を送信できます。次のフィールドをテストケースの正しい値に置き換える必要があります。
 
diff --git a/_lang/ja/_developer_guide/platform_wide/getting_started/platform_overview.md b/_lang/ja/_developer_guide/platform_wide/getting_started/platform_overview.md
index db295187396..6cd593cf32d 100644
--- a/_lang/ja/_developer_guide/platform_wide/getting_started/platform_overview.md
+++ b/_lang/ja/_developer_guide/platform_wide/getting_started/platform_overview.md
@@ -95,9 +95,9 @@ Brazeのダッシュボードは、多くの分析指標やアプリケーショ
 ### カスタマイズ可能なコンポーネント
 
 {% gallery %}
-{{site.baseurl}}/assets/img/getting-started/crawl-example.png<br> すべての Braze コンポーネントは、アクセシブルで、適応性があり、カスタマイズできるように作られています。Braze を使い始めるには、デフォルトの `BrazeUI` コンポーネントを使用し、ブランドのニーズやユースケースに合わせてカスタマイズします。
-{{site.baseurl}}/assets/img/getting-started/walk-example.png<br> デフォルトのオプションを超えるために、カスタムコードを書いて、メッセージチャンネルのルック＆フィールをよりブランドに近いものに更新することができる。これには、コンポーネントのフォントタイプ、フォントサイズ、色の変更も含まれます。マーケティング担当者は、Brazeのダッシュボードで直接、オーディエンス、コンテンツ、クリック行動、有効期限をコントロールできる。
-{{site.baseurl}}/assets/img/getting-started/run-example.png<br> また、完全にカスタムのコンポーネントを作成して、メッセージングの外観、動作、および他のメッセージングチャネルとの連携方法 (プッシュ通知に基づいてコンテンツカードをトリガーするなど) をコントロールすることもできます。Braze には SDK メソッドが用意されており、Braze ダッシュボードでのインプレッション数、クリック数、閉じた回数などのメトリクスを記録できます。各メッセージングチャネルには、これを容易にするための分析記事があります。
+{{site.baseurl}}/assets/img/getting-started/crawl-example.png <br> すべての Braze コンポーネントは、アクセシブルで、適応性があり、カスタマイズできるように作られています。Braze を使い始めるには、デフォルトの `BrazeUI` コンポーネントを使用し、ブランドのニーズやユースケースに合わせてカスタマイズします。
+{{site.baseurl}}/assets/img/getting-started/walk-example.png <br> デフォルトのオプションを超えるために、カスタムコードを書いて、メッセージチャンネルのルック＆フィールをよりブランドに近いものに更新することができる。これには、コンポーネントのフォントタイプ、フォントサイズ、色の変更も含まれます。マーケティング担当者は、Brazeのダッシュボードで直接、オーディエンス、コンテンツ、クリック行動、有効期限をコントロールできる。
+{{site.baseurl}}/assets/img/getting-started/run-example.png <br> また、完全にカスタムのコンポーネントを作成して、メッセージングの外観、動作、および他のメッセージングチャネルとの連携方法 (プッシュ通知に基づいてコンテンツカードをトリガーするなど) をコントロールすることもできます。Braze には SDK メソッドが用意されており、Braze ダッシュボードでのインプレッション数、クリック数、閉じた回数などのメトリクスを記録できます。各メッセージングチャネルには、これを容易にするための分析記事があります。
 {% endgallery %}
 
 <br>
diff --git a/_lang/ja/_help/accessibility.md b/_lang/ja/_help/accessibility.md
index 864bbb8674c..31acf810ccd 100644
--- a/_lang/ja/_help/accessibility.md
+++ b/_lang/ja/_help/accessibility.md
@@ -1,77 +1,77 @@
 ---
-nav_title: アクセシブルなメッセージを作る
-article_title: Brazeでアクセシブルなメッセージを作る
+nav_title: アクセシブルなメッセージを作成する
+article_title: Braze でアクセシブルなメッセージを作成する
 page_order: 3.5
 page_type: reference
 description: "この参考記事では、マーケティング・コンテンツにおいてアクセシビリティを考慮することが重要な理由と、Brazeでアクセシブルなメッセージを作成する方法について説明する。"
 ---
 
-# Brazeでアクセシブルなメッセージを作成する
+# Braze でアクセシブルなメッセージを作成する
 
-> たとえ意図的でなくとも、障害者を排除したマーケティング・コンテンツは、何百万人もの人々があなたのブランドと交流することを妨げる可能性がある。マーケティングにおけるアクセシビリティとは、誰もが簡単にあなたのマーケティングを体験し、あなたのコミュニケーションを受け取り、理解し、あなたの製品やサービス、ブランドに投資したりファンになったりする機会を持てるようにすることである。メッセージングをデザインする際には、どのようにすればすべての顧客がデザインにアクセスできるようになるかを考慮し、特別な時間をかけること。
+> 障がい者を排除したマーケティングコンテンツは、意図しなくても、何百万人もの人々がブランドと関わることを妨げる可能性があります。マーケティングにおけるアクセシビリティとは、誰もがマーケティングを体験し、コミュニケーションを受け取って理解し、製品、サービス、またはブランドに投資したり、ファンになったりする機会を得られることです。メッセージングをデザインする際には、どのようにすればすべての顧客がデザインにアクセスできるようになるかを考慮し、特別な時間をかけること。
 
 ## なぜアクセシビリティが重要なのか
 
-- **ユーザビリティが向上した：**アクセシビリティは、ユーザーがコンテンツとどのように相互作用するかを考えているため、アプリやサイトのユーザビリティについて考えることを促す。つまり、アクセシビリティは、障害者だけでなく、すべてのユーザーのオンライン体験を向上させることが多いということだ。
-- **市場リーチを拡大する：**障害者の世界市場は10億人を超え、その消費力は7兆ドル近くに達する。
-   > 「障害者市場は大きく、世界人口の高齢化とともに拡大している。パープル・ポンドと呼ばれる大規模な障害者市場を抱える英国では、障害者とその家族が毎年少なくとも2490億ポンドを費やしている。米国では、障害者の年間裁量支出は2000億ドルを超えている。世界の障害者市場は7兆ドル近いと推定されている」。<br>*ソース[W3C](https://www.w3.org/WAI/business-case/)*
+- **使いやすさの向上:** アクセシビリティは、ユーザーがコンテンツとどのように相互作用するかを考えているため、アプリやサイトのユーザビリティについて考えることを促す。つまり、アクセシビリティは、障がい者だけでなく、すべてのユーザーのオンラインエクスペリエンスを向上させることが多いです。
+- **市場でのリーチの拡大:** 世界の障がい者市場は10億人を超え、購買力は7兆ドル近くに上ります。
+   > 「障がい者の市場は大きく、世界人口の高齢化に伴い拡大しています。英国では、大きな障がい者市場が「パープルポンド」と呼ばれ、障害者とその家族は毎年少なくとも2,490億ポンドを費やしています。米国では、障がい者の年間裁量支出は2,000億ドルを超えています。障がい者市場の世界的な推定規模は約7兆ドルです。」<br>*ソース[W3C](https://www.w3.org/WAI/business-case/)*
 - **法的リスクを最小限に抑える：**多くの国で、デジタル・アクセシビリティを義務付ける法律がある。
 
 ## 考慮すべき障害分野
 
-*このセクションは、[W3Cから一部引用している：多様な能力と障壁](https://www.w3.org/WAI/people-use-web/abilities-barriers/).*
+*このセクションは、[W3Cから一部引用している：Diverse Abilities and Barriers](https://www.w3.org/WAI/people-use-web/abilities-barriers/)」から一部引用されています。*
 
 ### ビジュアル
 
-視覚障害には、片目または両眼の軽度または中等度の視力喪失から、両眼の視力の大幅な喪失または完全な喪失まで、さまざまなものがある。人によっては、特定の色に対する感受性が低下したり欠如したり、明るい色に対する感受性が亢進したりする。
+視覚障がいは、片目または両目の軽度または中等度の視力喪失から、両目の視力の重度または完全な喪失までさまざまです。特定の色に対する感度が低下したり、完全に失われたりする人もいれば、明るい色に対する感度が高まる人もいます。
 
-あなたのコンテンツとインタラクトするために、これらのユーザーは以下の能力を必要としている：
+このようなユーザーがコンテンツを操作するには、次の機能が必要です。
 
 - 文字や画像を拡大・縮小する
 - フォント、色、スペーシングの設定をカスタマイズする
 - コンテンツの音声合成を聞く（つまり、スクリーンリーダーを使う）
 - ビデオの音声解説を聞く
-- リフレッシュ点字を使って文字を読む
+- リフレッシュ可能な点字を使用したテキストの読み取り
 
 {% alert note %}
-- 世界では、少なくとも22億人が近視または遠視の障害を持っている（[WHO](https://www.who.int/news-room/fact-sheets/detail/blindness-and-visual-impairment)参照）。
-- 男性の約12人に1人、女性の約200人に1人がある程度の色覚異常があり、世界には推定3億人がいる（[NHS](https://www.nhs.uk/conditions/colour-vision-deficiency/)参照）。
+- 世界では、少なくとも22億人が近視または遠視を抱えています （[WHO](https://www.who.int/news-room/fact-sheets/detail/blindness-and-visual-impairment) 参照）。
+- 男性12人に1人、女性200人に1人が何らかの色覚障害を抱えており、世界では3億人と推定されている([NHS](https://www.nhs.uk/conditions/colour-vision-deficiency/)参照)。
 {% endalert %}
 
-### ヒアリング
+### 聴覚
 
-聴覚障害には、片耳または両耳の軽度から中等度の聴覚障害が含まれる。部分的な難聴であっても、オーディオ・コンテンツに関しては問題になることがある。
+聴覚障害には、片耳または両耳の軽度から中程度の聴覚障害が含まれます。部分的な難聴であっても、オーディオ・コンテンツに関しては問題になることがある。
 
-あなたのコンテンツを理解するために、これらのユーザーは頼りにしている：
+コンテンツを理解するために、これらのユーザーは以下に依存します。
 
 - 音声コンテンツのトランスクリプトとキャプション
 - キャプションを表示し、キャプションの文字サイズや色を調整するオプションを提供するメディアプレーヤー
-- オーディオ・コンテンツの停止、一時停止、音量調整のオプション（システム・ボリュームとは独立している）
-- バックグラウンドノイズと明瞭に区別できる高品質なフォアグラウンドオーディオ
+- オーディオコンテンツの停止、一時停止、音量調整のオプション (システム音量から独立)
+- バックグラウンドノイズと明確に区別できる高音質のフォアグラウンドオーディオ
 
 {% alert note %}
-- 標準的な聴力検査によると、米国では12歳以上の8人に1人（13％、3000万人）が両耳に難聴がある。
-- 18歳以上の米国成人の約15％（3750万人）が、何らかの聴覚障害を訴えている（[NIH](https://www.nidcd.nih.gov/health/statistics/quick-statistics-hearing)参照）。
+- 標準的な聴力検査によると、米国では12歳以上の8人に1人 (13%、3,000万人) が両耳の難聴を抱えている
+- 18歳以上のアメリカ人成人の約15％（3,750万人）が、何らかの聴覚障害を報告している （[NIH](https://www.nidcd.nih.gov/health/statistics/quick-statistics-hearing) 参照）。
 {% endalert %}
 
-### フィジカル
+### 身体
 
-身体障害には、筋力低下や筋肉のコントロールや感覚の制限、関節障害、運動を妨げる痛み、手足の欠損などがある。
+身体障がいには、筋力低下や筋肉の制御や感覚の制限、関節障害、動きを妨げる痛み、手足の欠損などが含まれます。
 
-このようなユーザーは、（標準的なキーボードを使用していなくても）機能を有効にするためにキーボードのサポートに依存している。あなたのコンテンツと対話するために、これらのユーザーは必要とする：
+このようなユーザーは、（標準的なキーボードを使用していなくても）機能を有効にするためにキーボードのサポートに依存している。このようなユーザーがコンテンツを操作するには、以下が必要です。
 
-- 大きなクリック可能エリア
+- 大きなクリック可能領域
 - タスクを完了するのに十分な時間
 - 現在のフォーカスを目に見える形で示す
 - ページヘッダーやナビゲーションバーなど、コンテンツのブロックをスキップする仕組み
 
 {% alert note %}
-米国では200万人近くが手足を失った状態で生活している（[切断者連合](https://www.amputee-coalition.org/limb-loss-resource-center/resources-filtered/resources-by-topic/limb-loss-statistics/limb-loss-statistics/#1)参照）。
+米国では、約200万人が肢の喪失を伴う生活を送っている([Amputee Coalition](https://www.amputee-coalition.org/limb-loss-resource-center/resources-filtered/resources-by-topic/limb-loss-statistics/limb-loss-statistics/#1)参照)
 {% endalert %}
 
 ### 認知的
 
-認知障害、学習障害、神経学的障害には、神経多様性や神経学的障害だけでなく、必ずしも神経学的ではない行動障害や精神衛生上の障害も含まれる。神経系のあらゆる部分に影響を及ぼし、聴覚、運動、視覚、会話、情報の理解などに影響を及ぼす。
+認知障がい、学習障がい、神経障がいには、神経多様性や神経障がいのほか、必ずしも神経系とは限らない行動障がいや精神障がいも含まれます。これらは神経系のあらゆる部分に影響を及ぼす可能性があり、人の聞く力、動く力、見る力、話す力、情報を理解する力に影響を与えます。
 
 個々のニーズにもよるが、このようなユーザーが頼りにしている：
 
@@ -79,25 +79,25 @@ description: "この参考記事では、マーケティング・コンテンツ
 - フォーム、ボタン、その他のコンテンツに一貫したラベルを付ける
 - 予測可能なリンクターゲットと全体的な相互作用
 - メニューや検索バーなど、さまざまなナビゲーション方法
-- 点滅、点滅、またはその他の邪魔なコンテンツをオフにする設定
+- 点滅、点滅、または他の方法で気を散らすコンテンツを無効にする設定
 - 画像に支えられたシンプルなテキスト
 
 
 {% alert note %}
 - 米国では5人に1人が学習と注意の問題を抱えている（[LDA](https://ldaamerica.org/lda_today/the-state-of-learning-disabilities-today/#:~:text=LD%20Today,have%20learning%20and%20attention%20issues.)参照）。
-- 世界人口のおよそ10～20％がニューロダイバージェントと考えられている（[デロイトを](https://www2.deloitte.com/us/en/insights/topics/talent/neurodiversity-in-the-workplace.html)参照）。
-- 世界で約100人に1人が自閉症である（[WHO](https://www.who.int/news-room/fact-sheets/detail/autism-spectrum-disorders)参照）。
+- 世界人口のおよそ10～20% が神経多様性を持つと考えられている ([Deloitte](https://www2.deloitte.com/us/en/insights/topics/talent/neurodiversity-in-the-workplace.html) 参照)
+- 世界中で100人に1人の子供が自閉症にかかっています([WHO](https://www.who.int/news-room/fact-sheets/detail/autism-spectrum-disorders)参照)
 {% endalert %}
 
 ## ベストプラクティス
 
 ### コンテンツ
 
-- コンテンツはブランドを保ちつつ、平易な言葉を使う。米国中学1年生レベルの読解力で書く。[ヘミングウェイ・アプリなどの](https://hemingwayapp.com/)リソースを使って、テキストの読解レベルをチェックすることができる。
+- コンテンツはブランドを保ちつつ、平易な言葉を使う。米国中学1年生レベルの読解力で書く。[Hemingway App](https://hemingwayapp.com/)などのリソースを使用して、テキストの読み取りレベルを確認できます。
 - コンテンツを論理的に構成し、見出しが正しい階層に従っていることを確認する。見出しのレベルを飛ばしてはいけない。
-- 長いコンテンツの塊には、中央揃えテキストを避ける。これは、認知障害や学習障害のあるユーザーには読みにくいかもしれない。2行以上に折り返すコンテンツは左寄せにする。
+- コンテンツの長いチャンクには、中央揃えのテキストを使用しない。これは、認知障害や学習障害のあるユーザーには読みにくいかもしれない。2行以上に折り返すコンテンツは左寄せにする。
 - デジタル機器で読みやすいサンセリフフォントを使う。
-- テキストが切り捨てられていないことを確認するため、必ずデバイスに[テストメッセージを送信して]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/sending_test_push_notifications/)コピーをテストすること。もしあなたのメッセージが途切れてしまうと、あなたのコンテンツがユーザーに届かなくなるため、あなたとユーザーの双方に損害を与えることになる。
+- テキストが切り捨てられていないことを確認するため、必ずデバイスに[テストメッセージを送信して]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/sending_test_push_notifications/)コピーをテストすること。メッセージが途切れると、コンテンツがユーザーに届かなくなるため、自分とユーザーの両方に悪影響が及びます。
 
 ### リンク
 
@@ -107,7 +107,7 @@ description: "この参考記事では、マーケティング・コンテンツ
 ボタンのように見え、ボタンのように動作するものが欲しければ、リンクをボタンのようにスタイリングするのではなく、常に実際のボタンを使うようにしよう。リンクとボタンは、一般的なユーザーにとっては「同じように感じる」かもしれない-マウスを使ってリンクやボタンの上にカーソルを置き、マウスでクリックすることができる-しかし、ボタンとリンクでは操作方法が異なる（たとえば、ボタンは<kbd>Space</kbd>キーや<kbd>Enter</kbd>キーを押すことでアクティブにできるが、リンクは<kbd>Enter</kbd>キーでしかアクティブにできない）ため、リンクをボタンのようなスタイルにすると混乱する可能性がある。
 {% endalert %}
 
-リンクがユーザーをどこに連れて行くかを明確に説明するリンクテキストを書く。スクリーン・リーダーのユーザーは、コンテンツに目を通す方法として、リンクからリンクへとスキップすることが多い。ここをクリック」、「もっと見る」、「詳細はクリック」といった表現は、文脈を無視して読むと曖昧になるので避けること。
+リンクがユーザーをどこに連れて行くかを明確に説明するリンクテキストを書く。スクリーンリーダーのユーザーは、コンテンツをざっと読む方法としてリンクからリンクへスキップすることが多いため、リンクテキストが単独で機能することを確認してください。ここをクリック」、「もっと見る」、「詳細はクリック」といった表現は、文脈を無視して読むと曖昧になるので避けること。
 
 たとえば、天気予報を見るためのリンクをどう書くかを考えてみよう。
 
@@ -120,9 +120,9 @@ description: "この参考記事では、マーケティング・コンテンツ
 
 ### ボタン
 
-フォームの送信やカルーセルの再生など、クリック可能なアクションにはボタンを使う。
+フォームの送信やカルーセルの再生など、クリック可能なアクションのボタンを使用します。
 
-リンクテキストと同様に、ユーザーがボタンを押したときに起こるアクションを明確に説明するボタンテキストを書く（例えば、「続きを読む」ではなく「全文を読む」）。ボタンのテキストが長すぎないかテストする。ボタンがすべてのテキストを表示できない場合は、テキストが改行されるのではなく、省略記号で切り捨てられる。
+リンクテキストと同様に、ユーザーがボタンを押したときに起こるアクションを明確に説明するボタンテキストを書く（例えば、「続きを読む」ではなく「全文を読む」）。ボタンのテキストが長すぎないかテストする。ボタンにテキスト全体を表示できない場合は、テキストが新しい行に折り返されるのではなく、省略記号で切り捨てられます。
 
 ### 画像
 
@@ -146,7 +146,7 @@ description: "この参考記事では、マーケティング・コンテンツ
 
 ### カラーコントラスト
 
-十分な色のコントラストを持たせることは、アクセシビリティを向上させる手っ取り早い方法だ。前景色（テキスト）と背景色のコントラスト比は、[WCAG2.1のAAレベル要件に](https://www.w3.org/TR/WCAG/#contrast-minimum)準拠すべきである：
+十分な色のコントラストがあれば、アクセシビリティはすぐに向上します。前景色(文字)とバックグラウンド色のコントラスト比は、[WCAG 2.1 AA レベル要件](https://www.w3.org/TR/WCAG/#contrast-minimum)に準拠する必要があります。
 
 - 通常のテキスト（本文、ボタン、リンクなど）のコントラスト比は4.5:1。
 - 大きなテキスト（ヘッダーを考える）のコントラスト比は3：1である。
@@ -155,21 +155,21 @@ description: "この参考記事では、マーケティング・コンテンツ
 
 ### フォーム
 
-**長いフォームを細かく切り分ける**<br>認知的負荷を軽減するために、長いフォームを小さなセクションに分割する。これはチャンキングと呼ばれ、情報を消費しやすくするために使われる段階的な情報開示パターンである。これはすべてのユーザーにとって有益だが、特に認知障害を持つ人々にとって有用である。
+**長いフォームを細かく切り分ける**<br>認知的負荷を軽減するために、長いフォームを小さなセクションに分割する。これはチャンキングと呼ばれ、情報を消費しやすくするために使われる段階的な情報開示パターンである。これはすべてのユーザーに恩恵をもたらしますが、認知障がいのある人には特に役立ちます。
 
-**ツールチップやその他のホバー・ステートで重要なコンテンツを隠さない**<br>ホバー状態に含まれるコンテンツは、発見しにくく、モバイルフレンドリーではない。また、スクリーン拡大鏡を使用しているユーザーは、ホバーでしか利用できないコンテンツを見るのに苦労するだろう。
+**ツールチップやその他のホバー・ステートで重要なコンテンツを隠さない**<br>ホバー状態に含まれるコンテンツは見つけにくく、モバイルフレンドリーでないため、画面拡大鏡を使用するユーザーはホバー時にのみ表示されるコンテンツを視認するのに苦労します。
 
 **フィールド内の無効な文字のブロックを避ける**<br>フォーム・フィールドに特定の文字タイプが入力できないようにしない。ユーザーが好きなように入力できるようにし、何が間違っているのかエラーメッセージを出す方がいい。キーボード入力をブロックすることは、支援技術ユーザーにとって特に問題となる。彼らは、フォームに正しく入力されたかどうかを判断するために、インライン・バリデーションに大きく依存しているからだ。
 
-**明確なエラーメッセージを書く**<br>良いエラーメッセージは3つの部分で構成されている：何が起こったのか、何が間違っていたのか、どうすれば修正できるのか。エラーメッセージは明確で理解しやすいものでなければならない。簡単な言葉で話すようにする。専門用語は必要ない。
+**明確なエラーメッセージを書く**<br>良いエラーメッセージは3つの部分で構成されている：何が起こったのか、何が間違っていたのか、どうすれば修正できるのか。エラーメッセージは明確で理解しやすいものでなければならない。簡単な言葉で話してみてください。難しい専門用語は必要ありません。
 <br>
 
 ### カスタムHTML
 
 メッセージングにカスタムHTMLを使用している場合：
 
-- [セマンティックHTMLを](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML)使う。これは、ある要素を別の要素のように見せるためにスタイルを設定するのではなく、本来の目的に合った正しいHTML要素を使用することを意味する。ほとんどのHTML要素には、独自のアクセシビリティ・サポートが組み込まれている。
-- コンテンツの言語を識別するために、HTML内にlanguage属性を設定する。スクリーン・リーダーは、各言語の発音や特徴に基づいて、言語ごとに異なるサウンド・ライブラリを使用する。言語が指定されていれば、スクリーン・リーダーは必要に応じて自動的に言語ライブラリを切り替えることができる。以下に例を示します。
+- [セマンティックHTML](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML)を使用します。これは、ある要素を別の要素のように見せるためにスタイルを設定するのではなく、本来の目的に合った正しいHTML要素を使用することを意味する。ほとんどのHTML要素には、独自のアクセシビリティ・サポートが組み込まれている。
+- HTML内の言語属性を設定して、コンテンツが含まれている言語を識別します。スクリーン・リーダーは、各言語の発音や特徴に基づいて、言語ごとに異なるサウンド・ライブラリを使用する。言語が指定されている場合、スクリーンリーダーは必要に応じて言語ライブラリ間で自動的に切り替えることができます。以下に例を示します。
 
 {% raw %}
 ```html
diff --git a/_lang/ja/_help/faqs.md b/_lang/ja/_help/faqs.md
index d6c28380121..880d5775134 100644
--- a/_lang/ja/_help/faqs.md
+++ b/_lang/ja/_help/faqs.md
@@ -24,7 +24,7 @@ guide_featured_list:
   - name: "アプリ内メッセージ FAQ"
     link: /docs/user_guide/message_building_by_channel/in-app_messages/faq/
     image: /assets/img/braze_icons/channel-in-app-messages.svg
-  - name: "ロケーションとジオフェンス FAQ"
+  - name: "場所と地理に関するよくある質問"
     link: /docs/user_guide/engagement_tools/locations_and_geofences/faqs/
     image: /assets/img/braze_icons/marker-pin-01.svg
   - name: "メディアライブラリに関するよくある質問"
@@ -48,13 +48,13 @@ guide_featured_list:
   - name: "APIとCSVエクスポートFAQ"
     link: /docs/user_guide/data_and_analytics/export_braze_data/faqs/
     image: /assets/img/braze_icons/file-download-01.svg
-  - name: "特集フラッグFAQ"
+  - name: "機能フラグFAQ"
     link: /docs/developer_guide/platform_wide/feature_flags/faq/
     image: /assets/img/braze_icons/flag-01.svg
-  - name: "ライブ活動 よくある質問"
+  - name: "ライブ活動FAQ"
     link: /docs/developer_guide/platform_integration_guides/swift/live_activities/faq/
     image: /assets/img/braze_icons/swift.svg
-  - name: "リキッドFAQ"
+  - name: "液体FAQ"
     link: /docs/user_guide/personalization_and_dynamic_content/liquid/faq/
     image: /assets/img/braze_icons/beaker-02.svg
 
diff --git a/_lang/ja/_help/help_articles.md b/_lang/ja/_help/help_articles.md
index 2f2f18c9bf6..b323800763a 100644
--- a/_lang/ja/_help/help_articles.md
+++ b/_lang/ja/_help/help_articles.md
@@ -4,7 +4,7 @@ article_title: ヘルプ記事
 page_order: 1
 layout: dev_guide
 guide_top_header: "ヘルプ記事"
-guide_top_text: "私たちには、問題を解決し、キャンペーンの依存関係を明らかにするのに役立つ多くのヘルプ記事があります。新しいヘルプ記事の提案がある場合は、このヘルプ記事ページまたは他のヘルプ記事ページの下部にフィードバックを残してください。または、<a href='https://www.braze.com/docs/contributing/home'>Braze Contributor Guide</a>にアクセスして、自分で記事を書く方法を学ぶことができます。<br> <br>次の人気トピックから選択するか、ナビゲーションパネルに表示されている他の記事をご覧ください。"
+guide_top_text: "問題を解決し、キャンペーンの依存関係を明らかにするのに役立つ多くのヘルプ記事があります。新しいヘルプ記事の提案がある場合は、このヘルプ記事ページまたは他のヘルプ記事ページの下部にフィードバックを残してください。または、<a href='https://www.braze.com/docs/contributing/home'>Braze Contributor Guide</a>にアクセスして、自分で記事を書く方法を学ぶことができます。<br> <br>次の人気トピックから選択するか、ナビゲーションパネルに表示されている他の記事をご覧ください。"
 
 page_type: landing
 description: "このランディングページは、Brazeを使用する際の問題解決や依存関係の明示に役立つヘルプ記事のホームです。"
diff --git a/_lang/ja/_help/help_articles/account.md b/_lang/ja/_help/help_articles/account.md
index e74ebc9dd31..bfb31b5358c 100644
--- a/_lang/ja/_help/help_articles/account.md
+++ b/_lang/ja/_help/help_articles/account.md
@@ -2,8 +2,8 @@
 nav_title: アカウント
 page_order: 1
 layout: dev_guide
-guide_top_header: "アカウント・ヘルプ"
-guide_top_text: "ユーザー権限を明確にする以下のヘルプ記事をチェックしてほしい。<br><br> Brazeアカウントとダッシュボードの管理に関する詳細情報をお探しですか？<a href='/docs/user_guide/administrative/'>アドミニストレーション・</a>セクションの記事をお読みいただきたい！"
+guide_top_header: "アカウントヘルプ記事"
+guide_top_text: "ユーザー権限を明確にする以下のヘルプ記事をチェックしてほしい。<br><br> Brazeアカウントとダッシュボードの管理に関する詳細情報をお探しですか？<a href='/docs/user_guide/administrative/'>Administration</a>セクションの記事をお読みください!"
 
 page_type: landing
 description: "このランディングページには、Brazeアカウントに関連するヘルプ記事が掲載されている。"
diff --git a/_lang/ja/_help/help_articles/account/locked_out.md b/_lang/ja/_help/help_articles/account/locked_out.md
index d7e0b21f26e..2fe3039ee81 100644
--- a/_lang/ja/_help/help_articles/account/locked_out.md
+++ b/_lang/ja/_help/help_articles/account/locked_out.md
@@ -10,13 +10,13 @@ tool: Dashboard
 
 # アカウントからロックアウトされる
 
-だから、あなたはBrazeアカウントからロックアウトされています-心配することはありません!私たちはあなたが戻るのを手伝うことができます。	
+Braze アカウントからロックアウトされても、心配はいりません。再び入れるようサポートします。	
 
 受信したエラー情報によって、どのようなロックアウトが発生しているかを確認できます。	
 
-- [私のパスワードについてのエラーが表示されます。](#password-error)	
-- [エラーは見ませんが、Brazeはまだ入れません。](#instance-error)	
-- [口座停止のエラーがあります。](#account-suspension)	
+- [パスワードに関するエラーが表示される。](#password-error)	
+- [エラーは表示されないが、Braze に入れない。](#instance-error)	
+- [アカウント停止のエラーが表示される。](#account-suspension)	
 
 ## パスワードエラー
 
@@ -24,7 +24,7 @@ tool: Dashboard
 - 正しい[Braze ダッシュボードインスタンス][1]にログインしていることを確認します。アカウント管理者またはBraze アカウントマネージャーに確認してください。	
 - パスワードの有効期限が切れている可能性があるため、[リセットする必要があります][2]。	
 - [single sign-on][3]サービスを使用する場合は、セットアップが適切に完了したことをアカウント管理者に確認してください。	
-- 企業が複数のBrazeを使用している場合は、間違ったメールを使用してログインしている可能性があります。  	
+- Braze のインスタンスが複数ある場合は、間違ったメールを使用してログインしている可能性があります。  	
 
 疑わしい場合は、常に[パスワードをリセットできます][2]。	
 
@@ -33,13 +33,13 @@ tool: Dashboard
 通常、ログインに使用するマシンと同じマシンを使用している場合、Braze は自動的に正しいインスタンスを検出します。ただし、ログインしていない場合や初めてログインする場合は、次のことを考慮することをお勧めします。	
 
 - 正しい[Braze ダッシュボードインスタンス][1]にログインしていることを確認します。アカウント管理者またはBraze アカウントマネージャーに確認してください。
-- 企業が複数のBrazeを使用している場合は、間違ったメールを使用してログインしている可能性があります。	
+- Braze のインスタンスが複数ある場合は、間違ったメールを使用してログインしている可能性があります。	
 
 ## アカウント停止	
 
-これはあまり頻繁にはアプリしませんが、サスペンドと削除を非常に深刻に考慮しています。このエラーを見つけた場合、最善の策は、自社のBraze管理者、Braze アカウントマネージャー、または[Brazeサポート][support]に連絡することです。
+この状況はあまり頻繁には発生しませんが、アカウントの停止と削除は非常に深刻な問題です。このエラーを見つけた場合、最善の策は、自社のBraze管理者、Braze アカウントマネージャー、または[Brazeサポート][support]に連絡することです。
 
-_2019更新10月19日昨日d_
+_最終更新日2019年10月19日_
 
 [support]: {{site.baseurl}}/support_contact/	
 [1]: {{site.baseurl}}/user_guide/administrative/access_braze/braze_instances/#braze-instances
diff --git a/_lang/ja/_help/help_articles/api.md b/_lang/ja/_help/help_articles/api.md
index 0f939b872f0..81d9d1fbddb 100644
--- a/_lang/ja/_help/help_articles/api.md
+++ b/_lang/ja/_help/help_articles/api.md
@@ -6,13 +6,13 @@ guide_top_header: "APIヘルプ記事"
 guide_top_text: "API がユーザーデータの領域にどのように影響するかについては、次の記事を参照してください。<br><br> Braze REST API の詳細については、<a href='/docs/api/basics/'>API</a> を参照してください。"
 
 page_type: landing
-description: "このランディングページは、Braze API に関連する記事を支援するためのホームページです。"
+description: "このランディングページには Braze API に関連するヘルプ記事がまとめられています。"
 guide_menu_title: ""
 guide_menu_list:
   - name: API を使用したユーザーの削除
     link: /docs/help/help_articles/api/delete_user/
     image: /assets/img/braze_icons/user-minus-01.svg
-  - name: キャンペーンとキャンバスの属性の違い
+  - name: ソース間におけるキャンペーンとキャンバスの属性の違い
     link: /docs/help/help_articles/api/attribute_name_id_across_sources/
     image: /assets/img/braze_icons/info-circle.svg
 
diff --git a/_lang/ja/_help/help_articles/api/attribute_name_id_across_sources.md b/_lang/ja/_help/help_articles/api/attribute_name_id_across_sources.md
index ca0e76b24ca..bbdda063fdb 100644
--- a/_lang/ja/_help/help_articles/api/attribute_name_id_across_sources.md
+++ b/_lang/ja/_help/help_articles/api/attribute_name_id_across_sources.md
@@ -4,27 +4,27 @@ article_title: キャンペーンとキャンバスの属性は、Brazeのソー
 page_order: 1
 
 page_type: reference
-description: "このヘルプでは、Brazeのソース間でキャンペーンとキャンバスの属性名とIDを比較する。"
+description: "このヘルプでは、キャンペーンとキャンバスの属性の名前とID をBrazeの送信元間で比較します。"
 platform: API
 ---
 
 # キャンペーンとキャンバスの属性は、Brazeのソースによってどのように異なるのか？
 
-キャンペーン、キャンバス、キャンバスステップの名前とIDはすべて、Liquid、REST API、Currentsで利用できる。これらの属性は、3つのソースすべてで同じ値にマッピングされるが、名前は異なる場合がある。このページは、この3つのつながりを描くためのものである。
+キャンペーン、キャンバス、キャンバスステップの名前と ID はすべて、Liquid、REST API、Currents で利用できます。これらの属性は、3 つのソースすべてで同じ値にマッピングされますが、名前は異なる場合があります。このページは、3 つの間の接続を描くのに役立ちます。
 
 ## ユースケース
 
 ### Liquid
 
-キャンペーンとキャンバスのアトリビュートは、ダッシュボードのリキッドタグ{% raw %}(`{{campaign.${api_id}}}`){% endraw %} として利用できる。Liquidを使って、これらの属性をメッセージ自体、Connected Contentの呼び出し、またはキーと値のペアとして渡すことができる。これは通常、トラッキングの目的で行われる。
+キャンペーンおよびキャンバス属性s は、ダッシュボード{% raw %} (`{{campaign.${api_id}}}` など){% endraw %} の流動タグs として使用できます。Liquid を使用して、これらの属性s をメッセージそのもの、接続コンテンツ呼び出し、またはキーと値のペアとして渡すことができます。これは通常、トラッキングの目的で行われる。
 
 ### REST API
 
-キャンペーンとキャンバスの属性は、[キャンペーンの詳細をエクスポートするエンドポイント]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/)または[キャンバスの詳細をエクスポートするエンドポイントでも]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/)利用できる。つまり、すべてのキャンバス名とそれに対応するIDのリストだ。
+キャンペーンとキャンバスの属性は、[キャンペーンの詳細をエクスポートするエンドポイント]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/)または[キャンバスの詳細をエクスポートするエンドポイントでも]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/)利用できる。REST API を使用して、m 個のアプリリング(すべてのキャンバス名と対応するID の一覧) を構築できます。
 
 ### Currents
 
-キャンペーンとキャンバスの属性は、カレントの[メッセージ・エンゲージメント・イベントと結びついて]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events)いる。これは、プッシュ送信やEメール開封が、どのキャンペーンやキャンバス・コンポーネントに関連付けられているかを判断するために重要である。
+キャンペーンとキャンバスの属性s は、Currents の[メッセージエンゲージメントイベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events) に関連付けられています。これは、プッシュセンドまたはメール 開封が関連付けられているキャンペーンまたはキャンバスコンポーネントを判断できるようにするために大切です。
 
 ## キャンペーン属性
 
diff --git a/_lang/ja/_help/help_articles/api/delete_user.md b/_lang/ja/_help/help_articles/api/delete_user.md
index 1c6f6f3a8d3..35f3ea60afa 100644
--- a/_lang/ja/_help/help_articles/api/delete_user.md
+++ b/_lang/ja/_help/help_articles/api/delete_user.md
@@ -4,7 +4,7 @@ article_title: API を使用したユーザーの削除
 page_order: 0
 
 page_type: reference
-description: "このヘルプ記事では、Braze REST API を使用してユーザープロファイルを削除することの意味について説明します。"
+description: "このヘルプ記事では、Braze REST API を使用してユーザープロファイルを削除した場合の影響について説明します。"
 tool: Dashboard
 platform: API
 ---
@@ -22,21 +22,21 @@ platform: API
 
 [Braze REST API][1] を使用してユーザーを削除すると、以下の事象が発生します。
 - ユーザープロファイルは匿名化される。
-- [存続期間ユーザーs][2]数は、新たに匿名化されたユーザーsを説明するために更新dとなります。	
-- 匿名化されたユーザーは、集計されたコンバージョンパーセンテージeのタグにカウントされます。匿名ユーザーの場合は、カスタムイベントカウントと購入回数は更新されません。
+- [\[生涯ユーザー数]][2] が更新され、新たに匿名化されたユーザーが考慮されます。	
+- 匿名化されたユーザーは、集計コンバージョン率のタグにカウントされます。匿名ユーザーの場合は、カスタムイベントカウントと購入回数は更新されません。
 
-## 共有メールアドレスを持つマルチプロファイルs
+## メールアドレスを共有する複数のプロファイル
 
 同じメールアドレスを共有する複数のユーザープロファイルを結合するとします。 
 
 これらのユーザープロファイルを結合するには:
 
  1. 重複するメールアドレスを持つユーザーを特定します。 
- 2. 単一のプロファイルのすべての属性s をエクスポートします。 
+ 2. 単一プロファイルの属性をすべてエクスポートします。 
  3. これらの属性s をAPI またはCSV を介してユーザープロファイルに読み込みます。 
- 4. ユーザー s via API を削除します。基本的には、これらの重複ユーザーs と上記のデーターを削除します。
+ 4. API を介してユーザーを削除します。基本的には、これらの重複ユーザーと上記のデータを削除します。
 
-_2023更新9月13日昨日d_
+_最終更新日2023年9月13日_
 
 [1]: {{site.baseurl}}/api/endpoints/user_data/#user-delete-endpoint/
 [2]: {{site.baseurl}}/user_guide/data_and_analytics/analytics/understanding_your_app_usage_data/#lifetime-users
diff --git a/_lang/ja/_help/help_articles/campaigns_and_canvas.md b/_lang/ja/_help/help_articles/campaigns_and_canvas.md
index 77b5ea9d61e..cc0061b714a 100644
--- a/_lang/ja/_help/help_articles/campaigns_and_canvas.md
+++ b/_lang/ja/_help/help_articles/campaigns_and_canvas.md
@@ -1,12 +1,12 @@
 ---
 page_order: 2
-nav_title: キャンペーン&amp;アンプ; キャンバス
+nav_title: キャンペーンとキャンバス
 layout: dev_guide
-guide_top_header: "キャンペーン&amp;アンプ; キャンバスヘルプ記事"
-guide_top_text: "役に立つ情報を探していますか?これ以上見ないでください!キャンバスやキャンペーンのトラブルシューティングに役立つヘルプ記事をご覧ください。<br><br> ユーザー s を使用したエンゲージメントの構築および最適化の詳細については、<a href='/docs/user_guide/engagement_tools/campaigns/'>キャンペーン</a> および<a href='/docs/user_guide/engagement_tools/canvas/'>キャンバス</a> の記事を参照してください。"
+guide_top_header: "キャンペーンとキャンバスのヘルプ記事"
+guide_top_text: "役に立つ情報をお探しですか? これで十分です。キャンバスやキャンペーンのトラブルシューティングに役立つヘルプ記事をご覧ください。<br><br> ユーザーとのエンゲージメントの構築および最適化の詳細については、<a href='/docs/user_guide/engagement_tools/campaigns/'>キャンペーン</a>および<a href='/docs/user_guide/engagement_tools/canvas/'>キャンバス</a>の記事を参照してください。"
 
 page_type: landing
-description: "このランディングページは、キャンペーンまたはキャンバスの一般的な問題に関連する記事を支援するためのホームページです。"
+description: "このランディングページは、キャンペーンやキャンバスの一般的な問題に関連するヘルプ記事のホームです。"
 tool:
 - Campaigns
 - Canvas
@@ -16,22 +16,22 @@ guide_menu_list:
   - name: キャンバス配信の問題
     link: /docs/help/help_articles/campaigns_and_canvas/canvas_not_sending/
     image: /assets/img/braze_icons/send-01.svg
-  - name: 位置情報を確認する
+  - name: 位置データを確認する
     link: /docs/help/help_articles/campaigns_and_canvas/locations_data_in_campaigns/
     image: /assets/img/braze_icons/navigation-pointer-01.svg
-  - name: 大規模な制御グループの処理
+  - name: 大きなコントロールグループを処理する
     link: /docs/help/help_articles/campaigns_and_canvas/more_people_in_control_group/
     image: /assets/img/braze_icons/target-05.svg
-  - name: カスタムイベントプロパティのロギング
+  - name: カスタムイベントプロパティをロギングする
     link: /docs/help/help_articles/campaigns_and_canvas/using_custom_event_properties/
     image: /assets/img/braze_icons/code-02.svg
-  - name: キャンペーンまたはキャンバスの低変換
+  - name: キャンペーンまたはキャンバスの低コンバージョン
     link: /docs/help/help_articles/campaigns_and_canvas/conversions_low/
     image: /assets/img/braze_icons/shopping-cart-03.svg
-  - name: トリガー解除キャンペーンまたはキャンバス
+  - name: 非トリガーキャンペーンまたはキャンバス
     link: /docs/help/help_articles/campaigns_and_canvas/not_triggering/
     image: /assets/img/braze_icons/x-circle.svg
-  - name: イベントログの使用
+  - name: イベントロギングを使用する
     link: /docs/help/help_articles/campaigns_and_canvas/using_event_logging/
     image: /assets/img/braze_icons/list.svg
 
@@ -39,5 +39,5 @@ guide_menu_list:
 ---
 
 {% alert tip %}
-キャンペーンのトラブルシューティングに関する詳細については、問題発生後30日以内にBrazeサポートにお問い合わせください。診断ログは過去30日間しかありません。
+キャンペーンのトラブルシューティングに関して追加のサポートが必要な場合は、問題が発生してから30日以内に Braze サポートにお問い合わせください。これは、診断ログが過去30日分しか保存されていないためです。
 {% endalert %}
\ No newline at end of file
diff --git a/_lang/ja/_help/help_articles/campaigns_and_canvas/canvas_not_sending.md b/_lang/ja/_help/help_articles/campaigns_and_canvas/canvas_not_sending.md
index 2f5f6c2b5e8..bd9d54164e7 100644
--- a/_lang/ja/_help/help_articles/campaigns_and_canvas/canvas_not_sending.md
+++ b/_lang/ja/_help/help_articles/campaigns_and_canvas/canvas_not_sending.md
@@ -9,32 +9,32 @@ tool: Canvas
 
 # キャンバス配信の問題
 
-キャンバスは頑丈で複雑であり、作成する際には時間と注意を払っていることを私たちは知っています。ですから、キャンバスが思い通りに送信されない場合は、キャンバスのスケジュール、エントリのオーディエンス、およびエントリの設定を確認し、[キャンバスの作成]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)手順を見直すことをお勧めします。
+キャンバスは堅牢かつ複雑であり、作成する際には多くの時間と注意を要します。そのため、キャンバスが思いどおりに送信されない場合は、キャンバススケジュール、エントリオーディエンス、およびエントリ設定を確認し、[キャンバスの作成]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)ステップを見直すことをお勧めします。
 
 ## スケジュール
 
-- キャンバスは[スケジュールされた正しく]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#scheduled-delivery)ですか？
-- 正しい日付と時間を選択しましたか？
-- キャンバスを起動してから、[アクションベースの配信]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#action-based-delivery)のために、ユーザーが指定されたアクションを実行しましたか？
+- キャンバスは[正しくスケジュール]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#scheduled-delivery)されていますか?
+- 正しい日付と時間を選択しましたか?
+- キャンバスを起動してから、[アクションベースの配信]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#action-based-delivery)のために、ユーザーが指定されたアクションを実行しましたか?
 
 ## エントリ設定
 
-[エントリ設定]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-2-set-up-your-canvas)は、キャンバスの送信方法を理解するために重要です。キャンバスに入る可能性のある人数を制限しているかどうかを確認してください。
+[エントリ設定]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-2-set-up-your-canvas)は、キャンバスの送信方法を理解するために重要です。キャンバスにエントリする可能性のある人数を制限しているかどうかを確認してください。
 
-ユーザーは、メッセージを受信する資格がなくなった場合、キャンバスを終了することもできます。例えば、キャンバスにプッシュ通知のみが含まれており、ユーザーが最初のステップを受け取った後にプッシュをオプトアウトした場合、そのユーザーはキャンバスからドロップアウトします。[異なるキャンバスのステップ]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components)を使用して代替のユーザー ジャーニーを追加することを検討してください。
+メッセージを受信する資格がなくなったユーザーは、キャンバスを終了することもできます。例えば、キャンバスにプッシュ通知のみが含まれている場合、最初のステップを受信した後にプッシュ通知をオプトアウトしたユーザーはキャンバスから離脱します。[異なるキャンバスステップ]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components)を使用して、代わりのユーザー ジャーニーを追加することを検討してください。
 
 ## オーディエンスをセグメント化する
 
-ターゲットオーディエンスに対して次の質問を考えてみてください:
+ターゲットオーディエンスに関する次の質問を考慮します。
 
-- 正しいSegmentを選択しましたか？
-- セグメントはどのように設定されていますか？
-- セグメントにユーザーが含まれていることを確認しましたか？
-- キャンバスに入るユーザーの数を制限する追加のフィルターを追加しましたか？
-- ユーザーはあなたのバリアントの最初のステップを受け取る資格がありますか？例えば、キャンバスの最初のステップがプッシュ通知である場合、エントリオーディエンスがすべてプッシュ無効であると、ユーザーはメッセージを受信しません。
+- 正しいセグメントを選択しましたか?
+- セグメントはどのように設定されていますか?
+- セグメントにユーザーが含まれていることを確認しましたか?
+- キャンバスにエントリするユーザーの数を制限するフィルターを追加しましたか?
+- ユーザーがバリアントの最初のステップを受信する条件を満たしていますか? 例えば、キャンバスの最初のステップがプッシュ通知で、エントリオーディエンスがすべてプッシュ通知無効である場合、ユーザーはメッセージを受信しません。
 
 {% alert tip %}
-キャンバスのトラブルシューティングに関するさらなる支援が必要な場合は、問題が発生してから30日以内にBrazeサポートに連絡してください。診断ログは過去30日分しか保存されていません。
+キャンバスのトラブルシューティングに関して追加のサポートが必要な場合は、問題が発生してから30日以内に Braze サポートにお問い合わせください。これは、診断ログが過去30日分しか保存されていないためです。
 {% endalert %}
 
 _最終更新日: 2024年6月25日_
\ No newline at end of file
diff --git a/_lang/ja/_help/help_articles/campaigns_and_canvas/conversions_low.md b/_lang/ja/_help/help_articles/campaigns_and_canvas/conversions_low.md
index fa657207d9c..8714af0842e 100644
--- a/_lang/ja/_help/help_articles/campaigns_and_canvas/conversions_low.md
+++ b/_lang/ja/_help/help_articles/campaigns_and_canvas/conversions_low.md
@@ -14,23 +14,23 @@ tool:
 
 コンバージョンは、キャンペーン作成時に定義したメッセージ内でユーザーがアクションを実行したときに発生する。
 
-以前のキャンペーンや期待値と比較すると、コンバージョンが期待したほど高くないかもしれない。コンバージョンは厄介なビジネスだが、私たちのプラットフォームのいくつかのシンプルな機能、すなわちイベントトラッキングとコンバージョン期限に依存している。
+以前のキャンペーンや期待と比較すると、コンバージョンが期待したほど高くならない可能性があります。コンバージョンは扱いにくい数値ですが、イベントトラッキングとコンバージョン期限という、Braze のプラットフォームにおけるいくつかのシンプルな機能に依存しています。
 
 その理由を素早くトラブルシューティングするには、イベントトラッキングとコンバージョンの期限をチェックすることをお勧めする。
 
 ## イベントトラッキング
 
-キャンペーンがセッション開始またはカスタムイベントをトリガーするとき、このイベントまたはセッションがメッセージをトリガーするのに十分な頻度で発生していることを確認したい。[概要][1]（セッションデータ用）または[カスタムイベントページで][2]このデータを確認する：
+キャンペーンがセッション開始またはカスタムイベントをトリガーするとき、このイベントまたはセッションがメッセージをトリガーするのに十分な頻度で発生していることを確認したい。[概要][1](セッション情報の場合)または[カスタムイベント][2]ページでこのデータを確認します。
 
-![カスタム・イベント数の統計があるカスタム・イベント・ページ。][43]
+![カスタムイベント数の統計を含む \[カスタムイベント] ページ。][43]
 
 ## コンバージョンの期限
 
-キャンペーンごとに選択したコンバージョンイベントごとに、\[期限][44] を設定する。これは、コンバージョンがそれぞれのキャンペーンにカウントされるために、そのコンバージョンが発生しなければならない期限を設定していることを意味する。
+キャンペーンごとに選択したコンバージョンイベントごとに、\[期限][44] を設定する。つまり、コンバージョンが各キャンペーンでカウントされるための発生時間の制限を設定します。
 
-キャンペーンの指標を理解するために、\[コンバージョンの計算][45] ]に関する情報を確認しておくこと。キャンバスのユーザー変換については、[キャンバスのFAQを]({{site.baseurl}}/user_guide/engagement_tools/canvas/faqs/#how-are-user-conversions-tracked-in-a-canvas)参照のこと。 
+キャンペーン指標を理解するために、\[コンバージョンの計算][45] に関する情報を確認しておきます。キャンバスのユーザーコンバージョンについては、[キャンバスに関する FAQ]({{site.baseurl}}/user_guide/engagement_tools/canvas/faqs/#how-are-user-conversions-tracked-in-a-canvas) を参照してください。 
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2021年5月6日_
 
diff --git a/_lang/ja/_help/help_articles/campaigns_and_canvas/know_before_send.md b/_lang/ja/_help/help_articles/campaigns_and_canvas/know_before_send.md
index 5fc853ebda0..4820e203cc4 100644
--- a/_lang/ja/_help/help_articles/campaigns_and_canvas/know_before_send.md
+++ b/_lang/ja/_help/help_articles/campaigns_and_canvas/know_before_send.md
@@ -1,96 +1,96 @@
 ---
 nav_title: 送信する前に知っておくべきこと
 article_title: 送信する前に知っておくべきこと
-description: "事前ローンチガイドを訪問した後、コンテンツカード、メール、アプリ内メッセージ、プッシュ、SMSの最終チェックリストまたは「落とし穴」を参照してください。"
+description: "私たちのプレローンチガイドを訪問した後、コンテンツカード、メール、アプリ内メッセージ、プッシュ、SMSについては、この最終的なチェックリストまたは「gotcha」を参照してください。"
 alias: /know_before_send/
 
 ---
 
 # 送信する前に知っておくべきこと: チャンネル
 
-自信を持ってキャンペーンとキャンバスを開始しましょう！コンテンツカード、メール、アプリ内メッセージ、プッシュ、SMSの最終チェックリストまたは「注意点」を参照してください。
+キャンペーンとキャンバスを自信を持って開始しましょう。コンテンツカード、メール、アプリ内メッセージ、プッシュ、SMSの最終チェックリストまたは「注意点」を参照してください。
 
 {% alert note %}
-私たちは送信前に参照するための豊富なリソースリストを提供していますが、各チャネルには個別のニュアンスがあり、製品の進化に伴って成長し続けています。以下にリストされているチェックは役立つ提案であり、送信する前にキャンペーンや大規模な送信を徹底的にテストすることをお勧めします。
+私たちは送信前に参照するための豊富なリソースリストを提供していますが、各チャネルには個別のニュアンスがあり、製品の進化に伴って成長し続けています。以下のチェックを参考にして、キャンペーンと大量の送信を徹底的にテストしてから送信することをお勧めします。
 {% endalert %}
 
 ## 全般的な質問
 
-#### 確認すること
-- [**APIレート制限**](https://braze.com/resources/articles/whats-rate-limiting):ワークスペースでエラーが発生しないように、Braze API [レート制限]({{site.baseurl}}/api/api_limits/) を確認してください。レート制限を増やしたい場合（すでにリクエストをバッチ処理している場合）、顧客成功マネージャーに連絡してください。このプロセスにはリードタイムが必要であることを念頭に置いて、計画を立ててください。
-- [**必要なフリークエンシーキャップのオーバーライド**]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping):いくつかのキャンペーン、例えばトランザクションメッセージなどは、たとえ頻度制限に達していても、常にユーザーに届くようにしたいものです（例えば、配達通知）。特定のキャンペーンがフリークエンシーキャップのルールを上書きするようにしたい場合は、そのキャンペーンの配信をスケジュールする際にBrazeダッシュボードでフリークエンシーキャップをオフに切り替えることで設定できます。
+#### 確認事項
+- [**API レート制限**](https://braze.com/resources/articles/whats-rate-limiting): ワークスペースでエラーが発生しないように、Braze API [レート制限]({{site.baseurl}}/api/api_limits/) を確認してください。レート制限の引き上げを検討している （すでにリクエストをバッチ処理している) 場合は、カスタマーサクセスマネージャーにお問い合わせください。このプロセスにはリードタイムが必要であることを念頭に置いて、計画を立ててください。
+- [**必要なフリークエンシーキャップの無効化**]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping): いくつかのキャンペーン、例えばトランザクションメッセージなどは、たとえ頻度制限に達していても、常にユーザーに届くようにしたいものです（例えば、配達通知）。特定のキャンペーンでフリークエンシーキャップルールを無効にしたい場合は、フリークエンシーキャップをオフに切り替えて、そのキャンペーンの配信をスケジュールするときに Braze ダッシュボードで設定できます。
 
 #### 知っておくべきこと
-- [**グローバルコントロールグループ**]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group#global-control-group):グローバルコントロールグループを使用している場合、ユーザーの一部はキャンペーンやキャンバスを受け取りません。（[除外設定]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/#step-3-assign-exclusion-settings)で例外を作成できます）。これらのユーザーのリストを表示するには、CSVまたは[API]({{site.baseurl}}/api/endpoints/export/user_data/post_users_global_control_group/)経由でエクスポートします。
-- [**キャンバスレート制限**]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#rate-limiting):キャンバスでは、レート制限は個々のステップではなく、キャンバス全体に適用されます。例えば、複数のステップを持つキャンバスに1分あたり10,000メッセージのレート制限を設定した場合でも、最初のステップで制限に達するため、メッセージは10,000に制限されます。
+- [**グローバルコントロールグループ**]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group#global-control-group):グローバルコントロールグループを使用している場合、ユーザーの一部はキャンペーンやキャンバスを受け取りません。（[除外設定]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/#step-3-assign-exclusion-settings)で例外を作成できます）。これらのユーザーの一覧を表示するには、CSV または [API]({{site.baseurl}}/api/endpoints/export/user_data/post_users_global_control_group/) でエクスポートします。
+- [**キャンバスレート制限**]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#rate-limiting): キャンバスでは、レート制限は個々のステップではなく、キャンバス全体に適用されます。例えば、複数のステップを持つキャンバスに1分あたり10,000メッセージのレート制限を設定した場合でも、最初のステップで制限に達するため、メッセージは10,000に制限されます。
 - **フリークエンシーキャップ**: 
   - フリークエンシーキャップのルールはプッシュ、メール、SMS、およびwebhookに適用されますが、アプリ内メッセージとコンテンツカードには適用されません。
-  - グローバルフリークエンシーキャップはユーザーのタイムゾーンに基づいてスケジュールされ、24時間ではなくカレンダーデイによって計算されます。例えば、1日に1回以上キャンペーンを送信しないというフリークエンシーキャップのルールを設定した場合、ユーザーはローカルタイムゾーンで午後11時にメッセージを受信し、1時間後に別のメッセージを受信する資格があります。
+  - グローバルフリークエンシーキャップはユーザーのタイムゾーンに基づいてスケジュールされ、24時間単位ではなく暦日単位で計算されます。例えば、1日に1回以上キャンペーンを送信しないというフリークエンシーキャップのルールを設定した場合、ユーザーはローカルタイムゾーンで午後11時にメッセージを受信し、1時間後に別のメッセージを受信する資格があります。
 
 {% alert tip %}
-キャンバスおよびキャンペーンのトラブルシューティングに関するさらなる支援については、問題が発生してから30日以内にBrazeサポートに連絡してください。診断ログは過去30日分しか保存されていません。
+キャンバスおよびキャンペーンのトラブルシューティングに関する詳細については、過去30日間の診断ログしかないため、問題が発生してから30日間以内にBrazeサポートに連絡してください。
 {% endalert %}
 
 ## メール
 
-#### 確認すること
-- **顧客の同意**:最初のメールを送信する前に、まず顧客の許可を得ることが重要です。[同意とアドレスの収集]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/consent_and_address_collection/)および当社の[Braze許容使用ポリシー](https://www.braze.com/company/legal/aup)についての詳細をご参照ください。
-- **予想されるボリューム**:1日あたり200万通のメールを1つのIPで送信することは、そのボリュームが[適切にウォームアップされている]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/ip_warming#ip-warming)限り、一般的に推奨されます。 
-  - もしこれよりも多くのメールを定期的に送信する予定がある場合、プロバイダーがメールの受信を制限し、ソフトバウンスの増加、配信率の低下、IPの評判の低下を避けるために、複数のIPアドレスをIPプールにまとめて使用することを検討してください。 
-  - 短期間で送信したい場合は、異なるプロバイダーがメールを受け入れる速度を調べて、送信元のIP数を適切に判断することをお勧めします。 
+#### 確認事項
+- **顧客の同意**: 最初のメールを送信する前に、まず顧客の許可を得ることが重要です。[同意とアドレスの収集]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/consent_and_address_collection/)および当社の[Braze許容使用ポリシー](https://www.braze.com/company/legal/aup)についての詳細をご参照ください。
+- **推奨ボリューム**: [適切にウォームアップされている]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/ip_warming#ip-warming)場合、1つのIPに対して1日あたり200万通のメールが一般的な推奨値になります。 
+  - これよりも大量のメールを継続的に送信する予定がある場合は、プロバイダーがメールの受信を制限して大量のソフトバウンスや配信可能性および IP レピュテーションの低下が発生しないよう、複数の IP アドレスを IP プールにバンドルすることを検討してください。 
+  - より短い期間内でのみ送信する予定の場合は、さまざまなプロバイダーがメールを受け入れる速度を調べ、送信元として適切な IP の数を判断することをお勧めします。 
 
 #### 知っておくべきこと
-- **送信量の要因**:IP の送信可能なボリュームを決定する要因には次のものがあります:
+- **送信ボリュームの決定要素**: IP に対応する送信ボリュームを決定する要素には、次のものがあります。
   - メールボックス:大手のメールプロバイダーは、単一のIPから1日に数百万通を処理できる可能性がありますが、地域の小規模なメールボックスプロバイダーやインフラが小規模なプロバイダーは、その量を処理できないかもしれません。
-  - 送信者の評判:送信者がそのボリュームに増加し、各メールボックスまたはドメインでの送信者の評判が十分に強ければ、単一のIPから1日により多くのボリュームを送信できる可能性があります。
-- **ベストプラクティス**:Braze [メールのベストプラクティス]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices)を確認し、配信サービスについて詳しく知りたい場合は、Brazeアカウントチームにお問い合わせください。
+  - 送信者レピュテーション: 送信者が送信ボリュームを増やし、送信先の各メールボックスまたはドメインでの送信者のレピュテーションが十分に高い場合は、単一 IP からの1日あたりの送信ボリュームを増やせる可能性があります。
+- **ベストプラクティス**: Braze の[メールのベストプラクティス]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices)を確認し、配信サービスについて詳しく知りたい場合は Braze アカウントチームにお問い合わせください。
 
 ## プッシュ
 
-#### 確認すること
-- [**オプトイン/サブスクライブおよびプッシュ有効**]({{site.baseurl}}/user_guide/message_building_by_channel/push/users_and_subscriptions/):ユーザーがBrazeからプッシュメッセージを受信するには、サブスクリプションステータスがオプトイン（iOS）またはサブスクライブ（Android）である必要があり、`Push Enabled = True`。Android 13では、プッシュ通知を送信するアプリの管理方法に大きな変更が導入されていることに注意してください。Braze [Android 13 SDK アップグレードガイド]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_13/) は、新しい Android 13 ベータ版がリリースされるたびに更新され続けます。
+#### 確認事項
+- [**Opted-in/subscribed and push enabled**]({{site.baseurl}}/user_guide/message_building_by_channel/push/users_and_subscriptions/):ユーザーが Braze からプッシュメッセージを受信するには、サブスクリプションステータスがオプトイン済み (iOS) またはサブスクリプション登録済み (Android) および `Push Enabled = True` になっている必要があります。Android 13では、ユーザーsがプッシュ通知sを送信するアプリsを管理する方法に大きな変更を導入していることに注意してください。Braze [Android 13 SDK アップグレードガイド]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_13/) は、新しい Android 13 ベータ版がリリースされるたびに更新され続けます。
 
 #### 知っておくべきこと
-- **Web プッシュ**:Braze [Web SDK のセットアップ]({{site.baseurl}}/user_guide/message_building_by_channel/push/web) がある場合は、ユーザーを引き付けるために Web プッシュを利用することを検討してください。Web プッシュは、アプリのプッシュ通知があなたの電話で動作するのと同じ方法で動作します。Web プッシュの作成に関する詳細については、[プッシュ通知の作成]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/#creating-a-push-message)をチェックしてください。
-- **単一のアプリをターゲットにする**:セグメンテーションの[違い]({{site.baseurl}}/developer_guide/platform_wide/app_group_configuration/#targeting-a-singular-app)を確認して、Singularアプリとそのユーザーをターゲットにします。
+- **Web プッシュ**:Braze [Web SDK のセットアップ]({{site.baseurl}}/user_guide/message_building_by_channel/push/web) がある場合は、ユーザーを引き付けるために Web プッシュを利用することを検討してください。Web プッシュは、スマートフォンでのアプリのプッシュ通知と同様に機能します。Web プッシュの作成に関する詳細については、[プッシュ通知の作成]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/#creating-a-push-message)をチェックしてください。
+- **単一アプリのターゲット設定**: 単一アプリとそのユーザーをターゲットに設定するため、[セグメンテーションの違い]({{site.baseurl}}/developer_guide/platform_wide/app_group_configuration/#targeting-a-singular-app)を確認します。
 
 ## SMS
 
-#### 確認すること
-- **割り当てとスループット**:現在アカウントに割り当てられているSMSの割り当て（ショートコード、ロングコードなど）と[それが提供するスループットの量]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup/short_and_long_codes/)を理解して、希望する時間内に送信するのに十分なスループットがあることを確認してください。
-- **SMSコピーからセグメントを見積もる**:[SMS Segment 計算機]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/segments/#things-to-keep-in-mind-as-you-create-your-copy)でSMSコピーをテストします。SMSセグメントの数は、スループット能力を考慮する必要があります。(Audience * SMS segments = Throughput needed).SMS FAQの[超過料金を回避する方法]({{site.baseurl}}/user_guide/message_building_by_channel/sms/faqs/#how-can-i-avoid-overages)を参照してください。
+#### 確認事項
+- **割り当てとスループット**: 現在アカウントに割り当てられているSMSの割り当て（ショートコード、ロングコードなど）と[それが提供するスループットの量]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup/short_and_long_codes/)を理解して、希望する時間内に送信するのに十分なスループットがあることを確認してください。
+- **SMS コピーからのセグメント推定**: [SMS Segment 計算機]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/segments/#things-to-keep-in-mind-as-you-create-your-copy)でSMSコピーをテストします。SMS セグメントの数はスループット能力と合わせて考慮する必要があることに注意してください。(Audience * SMS segments = Throughput needed).SMS FAQの[超過料金を回避する方法]({{site.baseurl}}/user_guide/message_building_by_channel/sms/faqs/#how-can-i-avoid-overages)を参照してください。
 - **SMSの法律と規制**:[SMSの法律、規制、および乱用防止を確認して]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_laws_and_regulations/)、すべての適用法に準拠してSMSサービスを使用していることを確認してください。送信する前に、必ず法律顧問の助言を求めてください。
 
 #### 知っておくべきこと
-- **SMSメッセージのデフォルト設定**:SMSメッセージは通常、送信者プールのショートコードから送信されるようにデフォルト設定されています。
-- **英数字送信者ID**:双方向メッセージングは、英数字の送信者IDを使用すると機能しなくなります。これらは現在、片方向のみです。
-- **米国のスループットが更新されました**:米国では、米国[A2P 10DLC登録](https://support.twilio.com/hc/en-us/articles/1260803225669-Message-throughput-MPS-and-Trust-Scores-for-A2P-10DLC-in-the-US)によりスループットが変更されました。交通渋滞やキャリアの問題など、実際の配信率に影響を与える複数の要因により、送信速度のSLAを契約上保証することはありませんのでご注意ください。
+- **SMS メールデフォルト**: SMSメッセージは通常、送信者プールのショートコードから送信されるようにデフォルト設定されています。
+- **英数字の送信者 ID**: 双方向メッセージングは、英数字の送信者IDを使用すると機能しなくなります。これらは現在、片方向のみです。
+- **米国でのスループット更新**: 米国では、米国[A2P 10DLC登録](https://support.twilio.com/hc/en-us/articles/1260803225669-Message-throughput-MPS-and-Trust-Scores-for-A2P-10DLC-in-the-US)によりスループットが変更されました。トラフィックの輻輳やキャリアの問題など、実際の配信レートに影響を与える可能性がある複数の要因があるため、SLAの送信速度を契約で決定することはありません。
 - **サブスクリプショングループ**:Brazeを通じてSMSキャンペーンを開始するには、サブスクリプショングループを選択する必要があります。また、国際的な[電気通信のコンプライアンスとガイドライン]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_laws_and_regulations/)に従うために、Brazeは選択されたサブスクリプショングループに[登録していない]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/#how-to-check-a-users-sms-subscription-group)ユーザーにSMSを送信することはありません。
 
 ## WhatsApp
 
 #### 知っておくべきこと
 
-- [**ベストプラクティス**]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_best_practices/):WhatsAppのベストプラクティスを確認してください。
+- [**ベストプラクティス**]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_best_practices/):提案されたWhatsAppのベストプラクティスを確認します。
 
 ## コンテンツカードによって促進された
 
-#### 確認すること
-- **コンテンツカード size**:コンテンツカードメッセージフィールドは、次のフィールドのバイトサイズ長を合計して計算した場合、圧縮前のサイズが2 KBに制限されています: タイトル、メッセージ、画像URL、リンクテキスト、リンクURL、およびキーと値のペア。このサイズを超えるメッセージは送信されません。このサイズには画像のサイズではなく、画像URLの長さが含まれます。
-- **送信後のコピーを更新**:カードが送信された後、同じカードのコピーを更新することはできません。[送信済みカードの更新]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/#updating-sent-cards)を参照して、このシナリオにどのように対処するかを理解してください。
+#### 確認事項
+- **コンテンツカードのサイズ**: コンテンツカードのメッセージフィールドは、圧縮前のサイズが2 KB に制限されています。この値は、タイトル、メッセージ、画像 URL、リンクテキスト、リンク URL、キーと値のペアの各フィールドのバイトサイズの長さを加算して計算されます。このサイズを超えるメッセージは送信されません。このサイズには画像のサイズではなく、画像URLの長さが含まれます。
+- **送信後のコピーの更新**:カードが送信された後、同じカードのコピーを更新することはできません。このシナリオへのアプローチ方法については、「[送信されたカードの更新]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/#updating-sent-cards)」を参照してください。
 
 #### 知っておくべきこと
-- **アクティブなコンテンツカードキャンペーンの制限**:アクティブなコンテンツカードキャンペーンは最大500件まで作成できます。このカウントには、[カード作成]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/)オプションのいずれかで送信されたコンテンツカードが含まれます。  
-- [**報告用語**]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/reporting/):総インプレッション数、ユニークインプレッション数、ユニーク受信者などの用語を確認してください。定義が混乱を招くことがあります。
-- **コンテンツカードの更新**:デフォルトでは、Brazeはセッション開始時、フィードの下スワイプ（モバイル）、および最後の更新が1分以上前である場合にカードビューが開かれたときに、コンテンツカードリクエストを同期して更新します。
-- **コンテンツカードのキャッシュ**:コンテンツカードのキャッシュオプションは、当社の[Android/FireOS]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/customization/custom_styling/#customizing-card-rendering-for-android)および[Web](https://js.appboycdn.com/web-sdk/latest/doc/modules/appboy.html#getcachedcontentcards)のドキュメントにあります。 
-- **フリークエンシーキャップ**:フリークエンシーキャップはコンテンツカードには適用されません。
-- **印象**:インプレッションは通常、カードが表示されたときに記録されます。例えば、受信トレイがコンテンツカードでいっぱいの場合、ユーザーが特定のコンテンツカードまでスクロールするまでインプレッションは記録されません。Web、Android、iOSプラットフォームの間にはいくつかのニュアンスがあります。  
+- **アクティブコンテンツカードキャンペーンの制限**: アクティブコンテンツカードキャンペーンの上限は500件です。このカウントには、[カード作成]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/)オプションのいずれかで送信されたコンテンツカードが含まれます。  
+- [**レポート条件**]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/reporting/): 総インプレッション数、ユニークインプレッション数、ユニーク受信者などの用語を確認してください。定義が混乱を招くことがあります。
+- **コンテンツカードの更新**: デフォルトでは、Braze は、セッション開始時、フィードダウンスワイプ時 (モバイル)、および最後の更新が1分以上前の場合はカードビューが開かれたときに、コンテンツ カードリクエストを同期して更新します。
+- **コンテンツカードのキャッシュ**: コンテンツカードのキャッシュオプションは、当社の[Android/FireOS]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/customization/custom_styling/#customizing-card-rendering-for-android)および[Web](https://js.appboycdn.com/web-sdk/latest/doc/modules/appboy.html#getcachedcontentcards)のドキュメントにあります。 
+- **フリークエンシーキャップ**: フリークエンシーキャップは、コンテンツカードには適用されません。
+- **インプレッション**: 印象は一般的にカードが見られたときに記録されます。例えば、受信トレイがコンテンツカードでいっぱいの場合、ユーザーが特定のコンテンツカードまでスクロールするまでインプレッションは記録されません。Web、Android、iOS の各プラットフォームには若干の違いがあります。  
 
 ## アプリ内メッセージ
 
 #### 知っておくべきこと
-- **アプリ内メッセージトリガー**:セッションの開始時に、SDKはすべての対象となるアプリ内メッセージをトリガーとともにデバイスに送信するよう要求します。そのため、セッション中にイベントを実行すると、アプリ内メッセージを迅速かつ確実に受信できます。このため、キャンバス内のカスタムイベントによってアプリ内メッセージをトリガーすることはできません。
-- **送信対インプレッション**:アプリ内メッセージの場合、「送信済み」の概念は他の利用可能なチャネルとは異なります。アプリ内メッセージを見るには、ユーザーがセッションを開始し、対象のオーディエンスに属し、トリガーを実行する必要があります。このため、「インプレッション」を追跡しています。これはより明確です。
+- **アプリ内メッセージトリガー**: セッションの開始時に、SDK は、すべての適格アプリ内メッセージをトリガーとともにデバイスに送信するように要求します。そのため、セッション中にイベントを実行すると、アプリ内メッセージを迅速かつ確実に受信できます。このため、キャンバスのカスタムイベントによってアプリ内メッセージをトリガーすることはできません。
+- **送信済みとインプレッション**: アプリ内メッセージの場合、「送信済み」の概念は他の利用可能なチャネルとは異なります。アプリ内メッセージを表示するには、ユーザーがセッションを開始し、適格オーディエンスに含まれ、トリガーを実行する必要があります。このため、「インプレッション」を追跡しています。これはより明確です。
 - **トリガー**:デフォルトでは、アプリ内メッセージは SDK によって記録されるイベントによってトリガーされます。サーバー送信イベントによってアプリ内メッセージをトリガーしたい場合、[iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/custom_triggering/)および[Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/customization)向けのこれらのガイドを通じてこれを達成することもできます。
-- [**アプリ内メッセージのキャンバス**]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/in-app_messages_in_canvas/#advancement-behavior-options):これらのメッセージは、スケジュールされたメッセージがキャンバスコンポーネントで送信された後、ユーザーがアプリを初めて開いたとき（セッションの開始によってトリガーされます）に表示されます。
+- [**キャンバスのアプリ内メッセージ**]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/in-app_messages_in_canvas/#advancement-behavior-options): キャンバスコンポーネントでスケジュールされたメッセージがユーザーに送信された後、ユーザーが (開始セッションによってトリガーされて) 初めてアプリを開いたときに、これらのメッセージが表示されます。
diff --git a/_lang/ja/_help/help_articles/campaigns_and_canvas/locations_data_in_campaigns.md b/_lang/ja/_help/help_articles/campaigns_and_canvas/locations_data_in_campaigns.md
index 71f5c9294b2..08a6f257656 100644
--- a/_lang/ja/_help/help_articles/campaigns_and_canvas/locations_data_in_campaigns.md
+++ b/_lang/ja/_help/help_articles/campaigns_and_canvas/locations_data_in_campaigns.md
@@ -3,13 +3,13 @@ nav_title: 位置情報をチェックする
 article_title: 位置情報をチェックする
 page_order: 1
 page_type: solution
-description: "このヘルプ記事では、利用可能なロケーションを持つユーザーがいない場合に役立つクイックチェックを紹介する。"
+description: "このヘルプ記事では、利用可能な位置情報があるユーザーが存在しない場合に役立つ簡単なチェックについて説明します。"
 tool: Location
 ---
 
 # 位置情報をチェックする
 
-Brazeは、SDKを通じてユーザーの最新の位置情報をデフォルトで取得する。これは通常、"最近の場所 "が、ユーザーが最も最近アプリを使用した場所であることを意味する。Brazeにバックグラウンドの位置情報を送信すれば、より詳細なデータを入手できるかもしれない。
+Brazeは、SDKを通じてユーザーの最新の位置情報をデフォルトで取得する。これは通常、「最新の位置情報」が、ユーザーがアプリを最後に使用した場所であることを意味します。Braze のバックグラウンド位置情報データを送信する場合は、より詳細なデータを使用できる場合があります。
 
 利用可能なロケーションを持つユーザーがいない場合、2つの簡単なチェックでデータ収集と日付転送を確認することができる。
 
@@ -17,8 +17,8 @@ Brazeは、SDKを通じてユーザーの最新の位置情報をデフォルト
 
 アプリが位置情報を収集していることを確認する：
 
-- iOSの場合、これはユーザージャーニーのある時点で、ユーザがプロンプトを通じて位置情報の共有をオプトインすることを意味する。 
-- アンドロイドの場合、アプリのインストール時に、位置情報の許可を細かく、または粗く要求されることを確認する。
+- iOS の場合、これは、ユーザーがユーザージャーニーのどこかの時点でプロンプトを介して位置情報データの共有を選択することを意味します。 
+- Androidについては、設置時にアプリが細かい場所または粗い場所の許可を要求していることを確認してください。
 
 ユーザーの位置情報がBrazeに送信されているかどうかを確認するには、**Location Available**フィルターを使用する。このフィルターによって、「最新の位置情報」を持つユーザーの割合を見ることができる。
 
@@ -26,12 +26,12 @@ Brazeは、SDKを通じてユーザーの最新の位置情報をデフォルト
 
 ## データ転送
 
-開発者が位置情報をBrazeに渡していることを確認する。通常、位置情報の受け渡しは、ユーザーが許可を与えた後にSDKによって自動的に処理されるが、開発者がBrazeで位置情報のトラッキングを無効にしている可能性がある。位置情報のトラッキングに関する詳細は、以下を参照されたい：
+開発者が位置情報をBrazeに渡していることを確認する。通常、位置データの受け渡しは、ユーザーが権限を付与した後に SDK によって自動的に処理されますが、開発者が Braze での位置情報の追跡を無効にしている可能性があります。位置情報のトラッキングに関する詳細は、以下を参照されたい：
 - \[Android][26]
 - \[iOS][27]
-- \[ウェブ][28]
+- \[Web][28]
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2022年11月16日_
 
diff --git a/_lang/ja/_help/help_articles/campaigns_and_canvas/more_people_in_control_group.md b/_lang/ja/_help/help_articles/campaigns_and_canvas/more_people_in_control_group.md
index 058e98be8ae..f319a12f016 100644
--- a/_lang/ja/_help/help_articles/campaigns_and_canvas/more_people_in_control_group.md
+++ b/_lang/ja/_help/help_articles/campaigns_and_canvas/more_people_in_control_group.md
@@ -4,19 +4,19 @@ article_title: 大規模な対照群を扱う
 page_order: 2
 
 page_type: solution
-description: "このヘルプでは、対照群が予想より大きくなる理由を説明し、これを修正する手順を説明する。"
+description: "このヘルプ記事では、コントロールグループが予想よりも大きくなる可能性がある理由について説明し、これを修正するステップについて説明します。"
 tool: Canvas
 ---
 
-# 大規模な対照群を扱う
+# 大規模コントロールグループの処理
 
-キャンバスを作成する際、次の[例の](#example)ように、オーディエンスがコントロールグループとバリアントグループに均等に分かれることを想定していたかもしれない。その理由と解決方法を説明することができる！
+キャンバスの作成時に、次の[例](#example)のように、オーディエンスがコントロールグループとバリアントグループに均等に分割されると予想したかもしれません。その理由と解決方法を説明することができる！
 
-ユーザーが参加するグループは、ユーザーの設定によって異なる。これは対照群でも変種群でもよい。ユーザーは、\[入力ステップ][1].キャンバスを設定するとき、各バリアントとコントロール・グループに入るユーザーの割合を定義する。
+ユーザーが参加するグループは、ユーザーの設定によって異なる。これは、コントロールグループとバリアントグループのいずれかになります。キャンバスへのユーザーのエントリは、\[エントリステップ][1] で定義されたすべての基準を満たすと実行されます。キャンバスを設定するとき、各バリアントとコントロール・グループに入るユーザーの割合を定義する。
 
-対照群が変種群に比べて大きい場合（これはあなたの意図するところではない）、以下を推奨する：
+コントロールグループが意図せずバリアントグループよりも大きくなった場合は、以下をお勧めします。
 1. エントリーオーディエンスのフィルターを「プッシュ有効」に設定する。
-2. エントリーオーディエンスのフィルターを「オプトインしている、または購読している」に設定する。
+2. エントリオーディエンスフィルターを「オプトイン済みまたはサブスクリプション登録済み」に設定します。
 
 コントロール・グループを使ってキャンバスを作成する場合、エントリー・オーディエンスのすべてのユーザーがキャンバス内のメッセージを受信できるようにする（キャンバスにプッシュ・メッセージや電子メール・メッセージが含まれているなど）。
 
@@ -25,19 +25,19 @@ tool: Canvas
 次のようなシナリオを想像してみよう：
 - キャンバスには単一変異体と対照群がある。
 - バリアントの最初のステップはプッシュ通知だ。
-- 90％のユーザーがバリアント群に、10％のユーザーがコントロール群に選ばれた。
+- ユーザーの90% がバリアント、10% がコントロールグループにエントリするよう選択されました。
 
 ![キャンバスの例][41]
 
-このシナリオでは、キャンバスに入ったユーザーの90％がバリアントに入る。 
+このシナリオでは、キャンバスにエントリするユーザーの90% がバリアントにエントリします。 
 
-アクティブ・ユーザーを見てみると、39.8万人のユーザーがいるにもかかわらず、そのうちの73％しかプッシュを有効にしていないことがわかる：
+アクティブユーザーを振り返ると、含まれる39万8,000ユーザーのうち、プッシュが有効な割合は73% にすぎないことがわかります。
 
-![入場者数][42]
+![エントリオーディエンス][42]
 
-つまり、90％のユーザーがバリアントを入力するように指定したにもかかわらず、それらのユーザー全員が実際にプッシュ通知を受け取れるわけではないということだ。プッシュ通知を受け取ることができないこれらのユーザーは、関係なくバリアントに入る。
+つまり、90％のユーザーがバリアントを入力するように指定したにもかかわらず、それらのユーザー全員が実際にプッシュ通知を受け取れるわけではないということだ。プッシュ通知を受信できないこれらのユーザーも、バリアントにエントリします。
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2020年12月3日_
 
diff --git a/_lang/ja/_help/help_articles/campaigns_and_canvas/not_triggering.md b/_lang/ja/_help/help_articles/campaigns_and_canvas/not_triggering.md
index 7c96f60bf00..3c1aef6eec5 100644
--- a/_lang/ja/_help/help_articles/campaigns_and_canvas/not_triggering.md
+++ b/_lang/ja/_help/help_articles/campaigns_and_canvas/not_triggering.md
@@ -1,10 +1,10 @@
 ---
-nav_title: トリガー解除キャンペーンまたはキャンバス
-article_title: トリガー解除キャンペーンまたはキャンバス
+nav_title: 非トリガーキャンペーンまたはキャンバス
+article_title: 非トリガーキャンペーンまたはキャンバス
 page_order: 5
 
 page_type: solution
-description: "このヘルプでは、期待どおりにトリガーしないキャンペーン s またはキャンバスの問題を解決するためのステップについて説明します。"
+description: "このヘルプ記事では、キャンペーンまたはキャンバスが予期したとおりにトリガーされない問題を解決するステップについて説明します。"
 tool: 
 - Campaigns
 - Canvas
@@ -14,13 +14,13 @@ tool:
 
 期待されるトリガーの振る舞いを得られなかった理由はいくつかあります。最も一般的なエラーのソリューションは、トリガーしているキャンペーンがSegmentで同じトリガー事象を使用しないようにすることです。
 
-## 運動トリガー
+## キャンペーントリガー
 
-セグメントメンバーシップは、トリガー アクションs より先に評価されます。つまり、ユーザーが最初にSegmentに入っていなければ、トリガーを実行してもキャンペーンを受信しません。
+セグメントメンバーシップは、トリガーアクションの前に評価されます。つまり、ユーザーが最初にSegmentに入っていなければ、トリガーを実行してもキャンペーンを受信しません。
 
-キャンペーンがトリガーでカスタムイベントから外れている場合は、このイベントがキャンペーンで使用するSegmentによって事前にフィルターされていないことを確認する必要があります。 
+キャンペーンがカスタムイベントからトリガーされる場合は、このイベントがキャンペーンで使用するセグメントによって事前にフィルタリングされていないことを確認する必要があります。 
 
-たとえば、Segmentにイベント`SessionStart` "使用済みアプリが複数回&quot である場合、キャンペーン トリガーがオフのイベントが`SessionStart` であると、ユーザーはメッセージを受信しますが、最初のセッションのものであるとは限りません。これは、ユーザーがキャンペーンを受信するかどうかを確認する最初のステップ中に、キャンペーンがSegment対象オーディエンスを確認しているためです。 
+例えば、セグメントにイベント `SessionStart` 「アプリを複数回使用した」が含まれており、キャンペーンがトリガーされるイベントが `SessionStart` である場合、ユーザーはメッセージを受信しますが、それが必ずしも最初のセッションのメッセージであるとは限りません。これは、ユーザーがキャンペーンを受信するかどうかを確認する最初のステップ中に、キャンペーンがSegment対象オーディエンスを確認しているためです。 
 
 つまり、オーディエンス フィルターと同じトリガー(変更された属性やカスタムイベントなど)でアクションベースのキャンペーンまたはキャンバスを設定することは避けてください。[競合][2] は、ユーザーがトリガーを実行するときにオーディエンスにない場合に発生することがあります。つまり、キャンペーンを受信したり、キャンバスに入ったりすることはありません。
 
@@ -28,7 +28,7 @@ tool:
 キャンペーンのトラブルシューティングに関する詳細については、問題発生後30日以内にBrazeサポートにお問い合わせください。診断ログは過去30日間しかありません。
 {% endalert %}
 
-_2024更新6月25日昨日_
+_最終更新日: 2024年6月25日_
 
 [1]: {{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/#session-start-event/
 [2]: {{site.baseurl}}/user_guide/engagement_tools/testing/race_conditions/#race-conditions/
\ No newline at end of file
diff --git a/_lang/ja/_help/help_articles/campaigns_and_canvas/using_custom_event_properties.md b/_lang/ja/_help/help_articles/campaigns_and_canvas/using_custom_event_properties.md
index ef26fdb4b68..6991f12dbef 100644
--- a/_lang/ja/_help/help_articles/campaigns_and_canvas/using_custom_event_properties.md
+++ b/_lang/ja/_help/help_articles/campaigns_and_canvas/using_custom_event_properties.md
@@ -1,6 +1,6 @@
 ---
-nav_title: カスタムイベント・プロパティを記録する
-article_title: カスタムイベント・プロパティを記録する
+nav_title: カスタムイベントプロパティのロギング
+article_title: カスタムイベントプロパティのロギング
 page_order: 3
 page_type: solution
 description: "このヘルプ記事では、カスタムイベントが期待通りにログに記録されているかどうかを確認するための3つの重要なチェック方法について説明する。"
@@ -9,17 +9,17 @@ tool:
 - Canvas
 ---
 
-# カスタムイベント・プロパティを記録する
+# カスタムイベントプロパティをロギングする
 
-カスタムイベントが期待通りに記録されているかどうかを確認するには、3つの重要なチェックがある：
+カスタムイベントが想定どおりにロギングされていることを確認するための重要なチェックが3つあります。
 
-* [どのイベントをログに記録するかを設定する](#verify-events)
+* [ロギングされるイベントを設定する](#verify-events)
 * [ログを確認する](#verify-log)
-* [数値を確認する](#verify-values)
+* [値を確認する](#verify-values)
 
 ## カスタムイベントプロパティを確認する
 
-[カスタムイベント・プロパティは][22]、カスタムイベントを記述するメタデータである。カスタムイベントが記録されるたびに、複数のプロパティが記録される可能性がある。
+[カスタムイベントプロパティー][22] は、カスタムイベントs を記述するメタデータです。カスタムイベントがログに記録されるたびに、複数のプロパティーがログに記録されます。
 
 ### イベントを検証する
 
@@ -33,7 +33,7 @@ tool:
 
 イベント・プロパティが正常に追跡されていることを確認するには、**カスタム・イベント・**ページからすべてのイベント・プロパティを見ることができる。
 
-1. **データ設定**＞**カスタム**イベントに移動する。
+1. \[**データ設定**] > \[**カスタムイベント**] に移動します。
 2. リストからカスタムイベントを探す。
 3. イベントの「**プロパティの管理**」をクリックする。これは、イベントに関連するプロパティの名前を表示する。
 
@@ -42,10 +42,10 @@ tool:
 テストユーザーとしてユーザーを追加した後、以下の手順に従って値を検証する： 
 
 1. アプリ内でカスタムイベントを実行する。
-2. データがフラッシュされるまでおよそ10秒待つ。
-3. [イベント・ユーザー・ログを][24]リフレッシュして、カスタム・イベントと、それと一緒に渡されたイベント・プロパティ値を表示する。
+2. データがフラッシュされるまで約10秒待ちます。
+3. [イベントユーザーログ][24]を更新して、渡されたカスタムイベントとイベントプロパティの値を表示します。
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2023年4月10日_
 
diff --git a/_lang/ja/_help/help_articles/campaigns_and_canvas/using_event_logging.md b/_lang/ja/_help/help_articles/campaigns_and_canvas/using_event_logging.md
index c1139ffa616..81a54a42d49 100644
--- a/_lang/ja/_help/help_articles/campaigns_and_canvas/using_event_logging.md
+++ b/_lang/ja/_help/help_articles/campaigns_and_canvas/using_event_logging.md
@@ -3,7 +3,7 @@ nav_title: イベント ログの使用
 article_title: イベント ログの使用
 page_order: 6
 page_type: solution
-description: "この記事では、Braze統合の問題をトラブルシューティングするためにイベントログを使用する方法について説明します。"
+description: "このヘルプ記事では、イベントログを使用してBrazeインテグレーションの問題をトラブルシューティングする方法について説明します。"
 ---
 
 # イベント ログの使用
@@ -16,7 +16,7 @@ Braze統合の問題のトラブルシューティングを支援するために
 
 これは匿名ユーザーを見つけるための素晴らしい方法です。この情報を使用して、Brazeに送信されているデータをテストし、不一致がないか確認することもできます。このビューから、データのデルタがBrazeに送信されているかどうかを確認できます。メールアドレスまたはプッシュトークンがログに記録されるすべてのイベントと共に送信される場合、すべてのデータがBrazeに送信されます。
 
-まだ助けが必要ですか？[サポートチケット]({{site.baseurl}}/braze_support/)を開封する。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日: 2022年11月16日_
 
diff --git a/_lang/ja/_help/help_articles/content_cards.md b/_lang/ja/_help/help_articles/content_cards.md
index e0cb01039c0..8ead44f7eb2 100644
--- a/_lang/ja/_help/help_articles/content_cards.md
+++ b/_lang/ja/_help/help_articles/content_cards.md
@@ -6,7 +6,7 @@ guide_top_header: "コンテンツカードのヘルプ記事"
 guide_top_text: "コンテンツカードのトラブルシューティングについては、次の記事を参照してください。<br><br> <a href='/docs/user_guide/message_building_by_channel/content_cards/'>コンテンツカード</a>セクションで、コンテンツカードをキャンペーンとキャンバスに統合するさまざまな方法について詳しく説明します!"
 
 page_type: landing
-description: "このランディングページは、コンテンツカードに関連する記事を支援するためのホームページです。"
+description: "このランディングページにはコンテンツカードに関連するヘルプ記事がまとめられています。"
 channel: content cards
 noindex: true
 guide_menu_title: ""
diff --git a/_lang/ja/_help/help_articles/content_cards/empty_content_card_feed.md b/_lang/ja/_help/help_articles/content_cards/empty_content_card_feed.md
index bc5f2538231..25ea6b5c51d 100644
--- a/_lang/ja/_help/help_articles/content_cards/empty_content_card_feed.md
+++ b/_lang/ja/_help/help_articles/content_cards/empty_content_card_feed.md
@@ -10,13 +10,13 @@ channel: content cards
 
 # 空のコンテンツ・カード・フィード
 
-スケジュール配信でコンテンツカードキャンペーンを送信する場合、[カード作成で]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/#overview)選択したオプションは、新規ユーザーが最初のセッションでフィードにカードを表示するかどうかに影響する。**カード作成が** **キャンペーン開始時に**設定されている場合、Brazeはキャンペーン送信時にオーディエンスメンバーシップを評価するため、キャンペーン開始後に作成されたユーザーはフィードにコンテンツカードを受信しない。
+スケジュール配信でコンテンツカードキャンペーンを送信する場合、[カード作成で]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/#overview)選択したオプションは、新規ユーザーが最初のセッションでフィードにカードを表示するかどうかに影響する。**Card Creation**が**に設定されている場合、キャンペーン起動時**に、キャンペーン起動後に作成されたユーザーはフィードでコンテンツカードを受信しません。これは、Brazeがオーディエンス
 
-新規ユーザーにカードを受け取らせたい場合は、以下のいずれかを行う：
+新しいユーザーにカードs を受信させたい場合は、以下のいずれかの操作を行います:
 
-- 定期配送キャンペーンを作成し、「**カード作成**」を**「第一印象で**」に設定する。このカードは初回セッション時に渡される。
-- アクション・ベースの配送キャンペーンを行う。選択したアクションを次に実行したときに、このカードを受け取る。
+- 定期配送キャンペーンを作成し、「**カード作成**」を**「第一印象で**」に設定する。このカードは、最初のセッションで提供されます。
+- アクションベースの配信キャンペーンを作成します。このカードは、選択したアクションの次回実行時に提供されます。
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2023年4月17日_
diff --git a/_lang/ja/_help/help_articles/data.md b/_lang/ja/_help/help_articles/data.md
index 886a1fe47fd..72d695fccc1 100644
--- a/_lang/ja/_help/help_articles/data.md
+++ b/_lang/ja/_help/help_articles/data.md
@@ -13,7 +13,7 @@ guide_menu_list:
   - name: カスタム属性またはイベントのデータタイプを変更する
     link: /docs/help/help_articles/data/change_custom_data_type/
     image: /assets/img/braze_icons/table.svg
-  - name: ディスパッチIDの動作
+  - name: ディスパッチ ID の動作
     link: /docs/help/help_articles/data/dispatch_id/
     image: /assets/img/braze_icons/key-01.svg
   - name: ブロックリストと削除の比較
diff --git a/_lang/ja/_help/help_articles/data/blocklisting_deletion.md b/_lang/ja/_help/help_articles/data/blocklisting_deletion.md
index 3e29888b21d..09a10a8130b 100644
--- a/_lang/ja/_help/help_articles/data/blocklisting_deletion.md
+++ b/_lang/ja/_help/help_articles/data/blocklisting_deletion.md
@@ -11,13 +11,13 @@ description: "このヘルプ記事では、属性のブロックリストと削
 
 Brazeにおけるブロックリストと属性の削除の違いを理解するために、それぞれのアクションの結果を確認しよう：
 
-- **ブロックリスト入りだ：**カスタム属性、イベント、または購入がブロックリストに登録されている場合、それらはユーザープロファイルに残るが、その属性に対する新しいリクエストは処理されない。
-- **削除する：**カスタム属性、イベント、購入が削除された場合、データは削除される。しかし、Brazeは、その属性がまだSDK経由で追跡されているか、APIまたはCSV経由でアップロードされている場合は、その属性に対する新しい受信要求を受け入れる。
+- **ブロックリストへの追加:**カスタム属性、イベント、または購入がブロックリストに登録されている場合、それらはユーザープロファイルに残るが、その属性に対する新しいリクエストは処理されない。
+- **削除:**カスタム属性、イベント、購入が削除された場合、データは削除される。ただし、SDK 経由で追跡されているか、API または CSV 経由でアップロードされている場合、Braze はその属性に対する新しい受信リクエストを受け入れます。
 
-## どちらを選ぶべきか？
+## どうすればいいですか？
 
-ブロックリストを達成するために、Brazeはブロックリスト情報を各ユーザーのデバイスに送信しなければならない。また、リストが大きすぎると（100以上の属性、イベント、購入）、アプリの動作が遅くなることがある。 
+ブロックリストに追加するには、Braze がブロックリスト情報を各ユーザーのデバイスに送信する必要があります。これはデータ量の多い処理になるため、回避するのが理想的です。また、一覧が大きすぎる (属性、イベント、または購入が 100 を超える) 場合は、アプリの処理速度が低下し始める可能性があります。 
 
 もうBrazeに属性を送る予定がないのであれば、削除ルートが推奨される。
 
-ルートに関係なく、削除したいカスタム属性、イベント、および購入は、**Manage Workspace**ページに表示されなくなり、セグメントフィルターとして削除される。ユーザーレベルのデータはプロファイルに残る。 
\ No newline at end of file
+ルートに関係なく、削除するカスタム属性、イベント、購入は \[**ワークスペースの管理**] ページに表示されなくなり、セグメントフィルターとして削除されます。ユーザーレベルのデータはプロファイルに残る。 
\ No newline at end of file
diff --git a/_lang/ja/_help/help_articles/data/change_custom_data_type.md b/_lang/ja/_help/help_articles/data/change_custom_data_type.md
index 783d2ab1f3b..ba949736367 100644
--- a/_lang/ja/_help/help_articles/data/change_custom_data_type.md
+++ b/_lang/ja/_help/help_articles/data/change_custom_data_type.md
@@ -20,11 +20,11 @@ description: "このヘルプ記事では、カスタム属性またはカスタ
 カスタム属性またはイベントのデータ型を変更する必要がある場合（例：`time`を`string`に変更する場合）、次の点を考慮してください。
 
 - セグメント、キャンペーン、キャンバス、または変更された属性やイベントを使用する他の場所の関連フィルターは自動的に更新されません。属性を変更する前に、属性をセグメントやフィルターで使用しているキャンペーンやキャンバスを停止し、それらを参照するフィルターから属性を削除する必要があります。
-- ユーザーデータは遡及的に更新されません。データ型の変更前にユーザープロファイルに変更された属性があった場合、その値は依然として古いデータ型のままです。これにより、変更された属性を含むセグメントからユーザーが外れる可能性があります。フィルターは新しいデータタイプを積極的に探しますが、プロファイルが以前のデータタイプを持っている場合、そのユーザーはセグメントから除外されます。これらのユーザーは、適切なセグメントに戻るように更新する必要があります。これを[`users/track`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)で行うことができます。
+- ユーザーデータは遡及的に更新されません。データ型の変更前にユーザープロファイルに変更された属性があった場合、その値は依然として古いデータ型のままです。これにより、変更された属性を含むセグメントからユーザーが外れる可能性があります。フィルターは新しいデータ型をアクティブに検索しますが、プロファイルに以前のデータ型が残っている場合、そのユーザーはSegmentから除外されます。これらのユーザーは、適切なセグメントに戻るように更新する必要があります。これを[`users/track`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)で行うことができます。
 - 新しいデータ型でない場合、新しいデータは受け付けられません。例えば、変更された属性の以前のデータ型を含む`users/track`エンドポイントへのAPI呼び出しは受け付けられません。新しいデータ型を呼び出す必要があります。
 
 {% alert important %}
-自動検出がカスタム属性データ型を更新するのを防ぐ機能は現在、早期アクセス中です。この早期アクセスに参加することに興味がある場合は、顧客成功マネージャーに連絡してください。
+自動検出がカスタム属性データ型を更新するのを防ぐ機能は現在、早期アクセス中です。この初期のアクセスに参加したい場合は、顧客のサクセスマネージャーにお問い合わせください。
 {% endalert %}
 
 _最終更新日: 2024年2月8日_
diff --git a/_lang/ja/_help/help_articles/data/dispatch_id.md b/_lang/ja/_help/help_articles/data/dispatch_id.md
index 15e6e4f0cdd..4acd1387397 100644
--- a/_lang/ja/_help/help_articles/data/dispatch_id.md
+++ b/_lang/ja/_help/help_articles/data/dispatch_id.md
@@ -1,44 +1,44 @@
 ---
-nav_title: ディスパッチIDの動作
-article_title: ディスパッチIDの動作
+nav_title: ディスパッチ ID の動作
+article_title: ディスパッチ ID の動作
 page_order: 0
 
 page_type: solution
-description: "このヘルプ記事では、ディスパッチID の使用法、影響、および制限を含むディスパッチID の動作について説明します。"
+description: "このヘルプ記事では、用途、影響、制限を含むディスパッチ ID の動作について説明します。"
 ---
 
-# ディスパッチIDの動作
+# ディスパッチ ID の動作
 
-`dispatch_id` は、メッセージディスパッチのID - それぞれの"transmission" Brazeから送信される一意のID です。スケジュールされたを送信したユーザは、同じ`dispatch_id` を受け取ります。通常、アクション ベースまたはAPI-トリガーメッセージ s はユーザーごとに一意の`dispatch_id` を受け取りますが、別の近くで送信されたメッセージは、複数のユーザーs 間で同じ`dispatch_id` を共有する場合があります。
+`dispatch_id` はメッセージディスパッチの ID で、Braze から送信される各「送信」に固有の ID です。スケジュールされたメッセージが送信されたユーザーには、同じ `dispatch_id` が割り当てられます。通常、アクションベースメッセージや API トリガーメッセージには、ユーザーごとに一意の`dispatch_id` が割り当てられますが、別のユーザーに近接して送信されたメッセージでは、複数のユーザー間で同じ `dispatch_id` が共有される場合があります。
 
-これにより、2 つの異なる時刻にメッセージが送信された場合、2 つの異なるユーザーが1 つのキャンペーンに対して異なるディスパッチID を持つことになります。これは、多くの場合、API 要求が個別に行われたためです。両方のユーザーs が1 回の送信で同じキャンペーン オーディエンスにあった場合、ディスパッチID は同じになります。
+これにより、2 つの異なる時刻にメッセージが送信された場合、2 つの異なるユーザーが1 つのキャンペーンに対して異なるディスパッチID を持つことになります。これは、多くの場合、API 要求が個別に行われたためです。両方のユーザーが 1 回の送信で同じキャンペーンオーディエンスに含まれていた場合、ディスパッチ ID は同じになります。
 
-## キャンペーン s でのディスパッチID の動作
+## キャンペーンでのディスパッチ ID の動作
 
-スケジュールされたキャンペーンは、同じ`dispatch_id` になります。アクションベースまたはAPI-トリガーのed キャンペーンは、ユーザーごとに一意の`dispatch_id`を取得できます。または、前述のように、近くにあるか、同じAPI 呼び出しで送信された場合、`dispatch_id` は、複数のユーザーで同じになる場合があります。たとえば、スケジュールされた キャンペーン オーディエンス内の2 つのユーザーs は、キャンペーンがスケジュールされたされるたびに同じ`dispatch_id` を持ちます。ただし、API-トリガー ed キャンペーンのオーディエンスの2 つのユーザーs は、別々のAPI 呼び出しで送信され、互いに近接していない場合、別々のディスパッチID を持つことがあります。
+スケジュールされたキャンペーンメッセージの `dispatch_id` は同じになります。アクションベースキャンペーンや API トリガーキャンペーンには、ユーザーごとに一意の`dispatch_id` が割り当てられます。また、前述のように、近接範囲内または同一の API 呼び出しで送信された場合は、複数のユーザーの `dispatch_id` が同じになる場合もあります。例えば、スケジュールされたキャンペーンオーディエンス内の2人のユーザーには、キャンペーンがスケジュールされたされるたびに同じ `dispatch_id` が割り当てられます。ただし、API トリガーキャンペーンのオーディエンスに含まれる2人のユーザーは、別々の API 呼び出しで送信され、互いに近接していない場合、別々のディスパッチ ID が割り当てられることがあります。
 
-Multi チャネル キャンペーン s は、配信種別で説明されているものと同じ動作を持ちます。
+マルチチャネルキャンペーンの動作は、配信タイプの説明と同じになります。
 
 {% alert warning %}
-すべてのキャンバスステップs に対して`dispatch_id` がランダムに生成されます。これは、Braze では、キャンバスステップs が"スケジュールされた" であっても、トリガーのed イベントとして扱われるためです。これにより、ID の生成に不整合が生じる可能性があります。場合によっては、キャンバスコンポーネントは、送信ごとのユーザーごとに一意の`dispatch_id` を持つか、または送信ごとにユーザー間で共有ディスパッチID を持つことがあります。
+Braze は、キャンバスステップが「スケジュール」されている場合でもキャンバスステップをトリガーされたイベントとして扱うため、すべてのキャンバスステップに対して `dispatch_id` がランダムに生成されます。これにより、ID の生成に不整合が生じる可能性があります。キャンバスコンポーネントには各送信でユーザーごとに一意の `dispatch_id` が割り当てられることもあれば、各送信においてユーザー間でディスパッチ ID が共有されることもあります。
 {% endalert %}
 
-## Template dispatch ID をLiquid でメッセージに送信する
+## Liquid でディスパッチ ID をメッセージにテンプレート化する
 
-(URL などで) メッセージ内からのメッセージの配信を追跡する場合は、`dispatch_id` をテンプレートできます。このための書式設定は、[サポートされているパーソナライゼーション タグs]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/) の一覧にあります。
+(URL などで) メッセージ内からのメッセージのディスパッチを追跡する場合は、`dispatch_id` でテンプレート化できます。このための書式設定は、「[サポートされているパーソナライゼーションタグ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/)」の一覧の \[キャンバスの属性] で確認できます。
 
-これは`api_id` と同じように動作します。この場合、`api_id` はキャンペーン作成時には使用できないため、プレースホルダとしてd がテンプレートされ、`dispatch_id_for_unsent_campaign` としてプレビューされます。ID はメッセージが送信される前に生成され、送信時間として含まれます。
+これは、`api_id` と同じように動作します。つまり、`api_id` はキャンペーンの作成時に使用できないため、プレースホルダとしてテンプレート化され、`dispatch_id_for_unsent_campaign` としてプレビューされます。ID はメッセージが送信される前に生成され、送信時間として含まれます。
 
 {% alert warning %}
-アプリ内メッセージ には`dispatch_id` がないため、`dispatch_id_for_unsent_campaign` のリキッドテンプレートはアプリ内メッセージ s では機能しません。
+アプリ内メッセージには `dispatch_id` がないため、`dispatch_id_for_unsent_campaign` の Liquid テンプレート化はアプリ内メッセージでは機能しません。
 {% endalert %}
 
-## メールのディスパッチ識別Currents フィールド
+## メールのディスパッチ ID Currents フィールド
 
-Currents機能を引き続き強化するために、`dispatch_id` は、すべてのコネクタータイプのCurrents メール事象のフィールドでもあります。`dispatch_id` は、Braze プラットフォームから送信される送信またはディスパッチごとに生成される一意のID です。
+Currents の機能を継続的に強化する取り組みの一環として、すべてのコネクタータイプで `dispatch_id` は Currents のメールイベントにおけるフィールドにもなっています。`dispatch_id` は、Braze プラットフォームからの送信 (ディスパッチ) ごとに生成される一意の ID です。
 
-送信されたすべての顧客 s が同じ`dispatch_id` をスケジュールされたしますが、アクション ベースまたはAPI-トリガーメッセージ s を受信した顧客 s は、メッセージごとに一意の`dispatch_id` を取得します。`dispatch_id` フィールドを使用すると、定期的なキャンペーンのどのインスタンスがコンバージョンを担当しているかを識別できるため、より多くのインサイトと、どのタイプのキャンペーンが業務目標の達成に役立っているかを確認できます。
+スケジュール済みのメッセージを受信したすべての顧客に同じ `dispatch_id` が割り当てられますが、アクションベースメッセージや API トリガーメッセージを受信した顧客にはメッセージごとに固有の `dispatch_id` が割り当てられます。`dispatch_id` フィールドを使用すると、定期的なキャンペーンのどのインスタンスがコンバージョンを担当しているかを識別できるため、より多くのインサイトと、どのタイプのキャンペーンが業務目標の達成に役立っているかを確認できます。
 
 `dispatch_id` を[パーソナライゼーション タグ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#supported-personalization-tags)、[メッセージエンゲージメントイベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/)、または[Segment]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment_for_currents/#integration-details)、[Mixpanel]({{site.baseurl}}/partners/insights/behavioral_analytics/mixpanel_for_currents/#email-events)、または[Amplitude]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents/) をCurrentsに使用できます。
 
-_2021更新7月15日昨日d_
+_最終更新日: 2021年7月15日_
diff --git a/_lang/ja/_help/help_articles/docs.md b/_lang/ja/_help/help_articles/docs.md
index bdb96c209f3..1bce23fc08e 100644
--- a/_lang/ja/_help/help_articles/docs.md
+++ b/_lang/ja/_help/help_articles/docs.md
@@ -2,15 +2,15 @@
 page_order: 10
 nav_title: 資料
 layout: dev_guide
-guide_top_header: "ヘルプ記事"
-guide_top_text: "Braze Documentationサイトに関連する追加情報については、以下のリソースをチェックしてほしい。"
+guide_top_header: "ドキュメントのヘルプ記事"
+guide_top_text: "Braze ドキュメントサイトに関連する追加情報については、次のリソースを参照してください。"
 
 page_type: landing
 description: "このランディングページには、オープンソースのドキュメントに貢献する方法など、Brazeドキュメントサイトに関連するリソースが含まれている。"
 noindex: true
 guide_menu_title: ""
 guide_menu_list:
-  - name: Braze Docsに貢献する
+  - name: Braze ドキュメントへの貢献
     link: /docs/help/help_articles/docs/contribution/
     image: /assets/img/braze_icons/edit-05.svg
   - name: スクロールバーの重なり
diff --git a/_lang/ja/_help/help_articles/docs/scroll_bar_overlap.md b/_lang/ja/_help/help_articles/docs/scroll_bar_overlap.md
index f811a3a9b93..a873f43021c 100644
--- a/_lang/ja/_help/help_articles/docs/scroll_bar_overlap.md
+++ b/_lang/ja/_help/help_articles/docs/scroll_bar_overlap.md
@@ -19,15 +19,15 @@ Mac を使用していて、スクロールバーがBraze Docs 内の内容と
 <your-bucket-prefix>/dataexport.<cluster-identifier>.S3.integration.<integration-id>/event_type=<event-type>/date=<date>/<schema-id>/<zone>/dataexport.<cluster-identifier>.S3.integration.<integration-id>+<partition>+<offset>.avro
 ```
 
-スクロールバーがコード ブロックと重なる場合は、**スクロールバーを表示する:**設定を**Always**に変更することをお勧めします(**一般設定s**)。これにより、Docs(コード ブロック s など)の機能が拡張され、スクロールバーが常時表示され、読みにくくなります。
+スクロールバーがコード ブロックと重なる場合は、**スクロールバーを表示する:**設定を**Always**に変更することをお勧めします(**一般設定s**)。この場合、ドキュメントの機能 (コードブロックなど) が拡張され、スクロールバーが常時表示されるため、文字を読みにくくなります。
 
 ![MacOSの一般設定][2]
 
-ここでは、更新d スクロールバーの外観を説明します。
+更新されたスクロールバーは、以下のように表示されます。
 
 ![重複のない固定スクロールバーの例][3]
 
-_2019更新3月27日昨日_
+_最終更新日: 2019年3月27日_
 
 {% comment %}
 問題を引き起こす可能性のある長いコードが1 行ある場合に挿入します。
diff --git a/_lang/ja/_help/help_articles/email.md b/_lang/ja/_help/help_articles/email.md
index 29b1acebe99..9d4e2fcd26f 100644
--- a/_lang/ja/_help/help_articles/email.md
+++ b/_lang/ja/_help/help_articles/email.md
@@ -2,8 +2,8 @@
 page_order: 3
 nav_title: メール
 layout: dev_guide
-guide_top_header: "Eメール・ヘルプ"
-guide_top_text: "メールキャンペーンに関するよくある問題や質問については、以下のヘルプ記事をチェックしよう。<br><br> BrazeでパーソナライズされたEメールメッセージを作成する詳細に興味がある？詳しくは<a href='/docs/user_guide/message_building_by_channel/email/'>Eメールの</a>セクションをご覧いただきたい！"
+guide_top_header: "電子メールヘルプ記事"
+guide_top_text: "メールキャンペーンに関するよくある問題や質問については、以下のヘルプ記事をチェックしよう。<br><br> Braze でのパーソナライズされたメールメッセージの構築に関する詳細に興味がありますか?詳しくは、<a href='/docs/user_guide/message_building_by_channel/email/'>Email</a>セクションをご覧ください!"
 
 page_type: landing
 description: "このランディングページには、よくあるEメールの問題についてのヘルプ記事が掲載されている。"
diff --git a/_lang/ja/_help/help_articles/email/email_bounces.md b/_lang/ja/_help/help_articles/email/email_bounces.md
index c4d57f8bd4a..69aee4c7ba7 100644
--- a/_lang/ja/_help/help_articles/email/email_bounces.md
+++ b/_lang/ja/_help/help_articles/email/email_bounces.md
@@ -3,13 +3,13 @@ nav_title: メールバウンス
 article_title: メールバウンス
 page_order: 0
 page_type: solution
-description: "このヘルプ記事は、ハードバウンスとソフトバウンスの違いを明確にします。"
+description: "このヘルプ記事では、ハードバウンスとソフトバウンスの違いを明確に説明します。"
 channel: email
 ---
 
 # メールバウンス
 
-メール キャンペーンからのメッセージがユーザーのメールの住所から跳ね返った場合、どうしますか?まず、ハードバウンスとソフトバウンスの2 種類のメールバウンスを定義してトラブルシューティングします。 
+メール キャンペーンからのメッセージがユーザーのメールの住所から跳ね返った場合、どうしますか?まず、ハードバウンスとソフトバウンスの2種類のメールバウンスを定義してトラブルシューティングしましょう。 
 
 ## ハードバウンス
 
@@ -17,20 +17,20 @@ channel: email
 
 ## ソフトバウンス
 
-ソフトバウンスは、受信者のメールアドレスが有効な場合、またはメールメッセージが受信者のメールサーバーに到達したが、一時的な問題でメッセージが拒否された場合に発生します。これらの一時的な問題は、次の場合に発生します。
+ソフトバウンスは、受信者のメールアドレスが有効な場合、またはメールメッセージが受信者のメールサーバーに到達したが、一時的な問題でメッセージが拒否された場合に発生します。これらの一時的な問題は、次の状況で発生します。
 - 受信者の受信トレイがいっぱいです
-- 受信者の受信トレイには大きすぎます  
+- 受信者の受信トレイに対してメッセージのサイズが大きすぎます  
 - メールサーバーが停止しました
 
 メールがソフトバウンスを受信した場合、通常は72時間以内に再試行されますが、再試行回数は受信側ごとに異なります。
 
-ソフトバウンスはキャンペーン 分析では追跡されませんが、[メッセージアクティビティログ][3]でソフトバウンスを監視できます。ここでは、ソフトバウンスの理由を確認し、メール キャンペーンの"sends"および"deliveries"の間に起こりうる不一致を理解することもできます。
+ソフトバウンスはキャンペーン分析では追跡されませんが、[メッセージアクティビティログ][3]で監視できます。ここでは、ソフトバウンスの理由を確認し、メールキャンペーンの「送信数」と「配信数」の間で発生しうる不一致を把握することもできます。
 
-メール サブスクリプション s およびキャンペーン s の管理の詳細については、[メール][2] のベストプラクティスを参照してください。
+メール購読とキャンペーンの管理の詳細については、「[メールのベストプラクティス][2]」を参照してください。
 
 それでも助けが必要ですか?[サポートチケット]({{site.baseurl}}/braze_support/)を開きます。
 
-_2024更新5月2日昨日d_
+_最終更新日: 2024年5月2日_
 
 [1]: {{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions
 [2]: {{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices
diff --git a/_lang/ja/_help/help_articles/email/html_looks_strange.md b/_lang/ja/_help/help_articles/email/html_looks_strange.md
index 41dea79659f..d66496f537b 100644
--- a/_lang/ja/_help/help_articles/email/html_looks_strange.md
+++ b/_lang/ja/_help/help_articles/email/html_looks_strange.md
@@ -4,20 +4,20 @@ article_title: テストメールのHTMLレンダリング
 page_order: 2
 
 page_type: solution
-description: "このヘルプでは、テストメールのHTMLレンダリングに関する問題のトラブルシューティング方法を説明する。"
+description: "このヘルプ記事では、テストメールでの HTML レンダリングに関する問題のトラブルシューティング方法について説明します。"
 channel: email
 ---
 
 # テストメールのHTMLレンダリングのトラブルシューティング
 
-[テストメールが][37]おかしいと感じたら、まずHTMLの設定をチェックすることをお勧めする。次に、これらの問題をチェックすることができる：
-* [エクステンションのコンフリクト](#check-conflicts)
+[テストメールが][37]おかしいと感じたら、まずHTMLの設定をチェックすることをお勧めする。次に、次の問題を確認できます。
+* [拡張機能の競合](#check-conflicts)
 * [メールレンダリング](#check-rendering)
-* [CSSのインライン化](#switch-css-inlining)
+* [CSS のインライン化](#switch-css-inlining)
 
 ### エクステンションのコンフリクト
 
-ブラウザの拡張機能によっては、Eメールエディタに問題が生じる場合がある。その一例が、Google Chromeで使用される[Grammarly][38]である）。これらのエクステンションのいずれかを使用しているのであれば、どちらかを選ぶべきである： 
+ブラウザの拡張機能によっては、Eメールエディタに問題が生じる場合がある。その一例が、Google Chromeで使用される[Grammarly][38]である）。これらの拡張機能のいずれかを使用している場合は、次のいずれかを実行する必要があります。 
 - Grammarlyがブラウザ拡張機能としてインストールされていないブラウザでBrazeのメールを編集する
 - Brazeのアカウントマネージャーに連絡し、メールエディタをHTMLのみまたはプレーンテキストに切り替えるよう依頼する。 
 
@@ -32,9 +32,9 @@ channel: email
 
 ### CSSのインライン化
 
-Inbox Visionのプレビューが、Brazeで送信されたものとまだ一致しないことがある。これは、Brazeと他のツールで実行されるCSSインライン化の違いによるものと思われる。このような疑いがある場合は、Brazeのアカウントマネージャーに連絡し、CSSのインライン化をオフにするよう依頼してほしい。
+受信トレイビジョンのプレビューが Braze で送信された内容と一致しないことがあります。これは、Brazeや他の工具によって実行されるCSSインライン展開の違いが原因である可能性があります。このような疑いがある場合は、Brazeのアカウントマネージャーに連絡し、CSSのインライン化をオフにするよう依頼してほしい。
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2021年12月21日_
 
diff --git a/_lang/ja/_help/help_articles/email/open_rates.md b/_lang/ja/_help/help_articles/email/open_rates.md
index 037fe8d74c2..ca79adaf38a 100644
--- a/_lang/ja/_help/help_articles/email/open_rates.md
+++ b/_lang/ja/_help/help_articles/email/open_rates.md
@@ -10,15 +10,15 @@ channel: email
 
 # クリック率の増加に対応する
 
-開封率は、Eメールキャンペーンを追跡するための有益な指標となる。しかし、これらの開封率は、必ずしもメールキャンペーンに対する人々のエンゲージメントを示す正確な指標ではない。定義上、開封イベントは、ユーザーがメールを開封したときに発生し、透明な開封トラッキングピクセルが正常にダウンロードされたことを意味する。 
+開封率は、Eメールキャンペーンを追跡するための有益な指標となる。ただし、これらの開封率は、メールキャンペーンに対する人間のエンゲージメントを必ずしも正確に示す指標ではありません。定義上、開封イベントは、ユーザーがメールを開封したときに発生し、透明な開封トラッキングピクセルが正常にダウンロードされたことを意味する。 
 
-さらに、セキュリティ・スキャンツールの使用は、開封率を上昇させる可能性がある。これらのツールの中には、リンクをクリックしてその正当性を確認することによって、受信した電子メールに悪意のあるコンテンツが含まれていないかスキャンし、ユーザーを保護するものもある。これらのクリックは、しばしば「ボットクリック」または「非人間的相互作用」（NHI）と呼ばれる。 
+さらに、セキュリティスキャンツールを使用すると、開封率が膨張する可能性があります。これらのツールの中には、リンクをクリックしてその正当性を確認することによって、受信した電子メールに悪意のあるコンテンツが含まれていないかスキャンし、ユーザーを保護するものもある。これらのクリックは、しばしば「ボットクリック」または「非人間的相互作用」（NHI）と呼ばれる。 
 
-結局のところ、Eメールが当社のサーバーを離れた後、次に何が起こるかについては限られた可視性しかないが、以下は、結果に影響を与える薬価を管理するための当社の推奨事項である：
+結局のところ、メールがサーバーから送信された後、次に何が起こるかは限定的にしかわかりませんが、結果に影響する NHI を管理するための推奨事項は次のとおりです。
 
-1. これは、どの送信者にも、そしてほとんどすべての受信者にも起こりうることである。クリックは、開封と同様、あなたのメッセージに対する人間のインタラクションを示す完全な信頼できる指標ではない。
-2. 肯定的なエンゲージメントが高いほど、薬価は下がる傾向にあるため、Eメールメッセージングの[ベストプラクティスに]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices)従うことが重要である。これには、ユーザーからメール送信の明確な許可を得ることや、定期的な頻度で、エンゲージメントのない購読者を停止することが含まれる。 
-3. 可能な限り、メールにHTTPSリンクを使用する。NHIは、安全なリンクを使用する送信者にとってはあまり一般的ではない。
-4. 現在、シングルクリックの配信停止プロセスを使用している場合は、通知設定を編集・管理するページにユーザーを誘導する[プリファレンスセンターの]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center/overview)作成を検討する。日本ハムはユーザーをうっかり配信停止にしてしまうことがあるので、これは役に立つ。
+1. この事象は、すべての送信者とほぼすべての受信者に発生する可能性があることに注意してください。クリック数は、開封数と同様に、メッセージに対する人間のインタラクションを示す完全に信頼できる指標ではないため、NHI を防ぐことはできません。
+2. 肯定的なエンゲージメントがの割合が高いほど NHI が低くなる傾向があるため、メールメッセージングの[ベストプラクティス]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices)に従うことが重要です。これには、通常のケイデンスでメールとSunsetting (配信停止)の未調整のサブスクライバーを送信するための明示的な権限をユーザーから取得することも含まれます。 
+3. 可能な限り、メールにHTTPSリンクを使用する。NHI は、安全なリンクを使用する送信者に対してはそれほど一般的に発生しません。
+4. 現在、シングルクリックの配信停止処理を使用している場合は、ページにユーザーs を渡して通知の環境設定を編集および管理する[ユーザー設定センター]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center/overview) を作成することを検討してください。NHI によって誤ってユーザーの登録を解除してしまう可能性があるため、これは有用です。
 5. コンバージョン数、アプリセッション数、サイト訪問数など、メールマーケティングの成功を測るために[他の指標を]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/email_reporting/#email-performance)使うことも検討しよう。
 6. メールキャンペーンに隠しリンクを追加する。このリンクは、白地に白のテキストや句読点など、人間が気づかないようなものだろう。ボットは全てのリンクをクリックする傾向があるため、見えないリンクにクリックイベントを発生させているユーザーは、実際にはNHIの結果であり、オープンやクリックが必ずしもポジティブなエンゲージメントを示しているわけではないと結論づけることができる。
\ No newline at end of file
diff --git a/_lang/ja/_help/help_articles/email/universal_links.md b/_lang/ja/_help/help_articles/email/universal_links.md
index 6d017368c04..cc0daba839e 100644
--- a/_lang/ja/_help/help_articles/email/universal_links.md
+++ b/_lang/ja/_help/help_articles/email/universal_links.md
@@ -13,7 +13,7 @@ AppleユニバーサルリンクとAndroidアプリリンクは、Webコンテ
 
 ## ユニバーサルリンクとアプリリンクの仕組み
 
-ユニバーサルリンク（iOS）とアプリンク（Android）は、ウェブページとアプリ内のコンテンツの両方を指す標準的なWebリンク（`http://mydomain.com`）です。
+ユニバーサルリンク (iOS) とアプリリンク (Android) は、Web ページとアプリ内のコンテンツの両方を指す標準的なウェブリンク (`http://mydomain.com`) です。
 
 ユニバーサルリンクまたはアプリリンクが開かれると、オペレーティングシステムはインストールされているアプリがそのドメインに登録されているかどうかを確認します。アプリが見つかった場合、Webページを読み込むことなくすぐに起動されます。アプリが見つからない場合、Web URLはユーザーのデフォルトのWebブラウザで読み込まれます。これもそれぞれApp StoreまたはGoogle Play Storeにリダイレクトするように設定できます。
 
@@ -24,7 +24,7 @@ AppleユニバーサルリンクとAndroidアプリリンクは、Webコンテ
 |                        | ユニバーサルリンクとアプリリンク                                  | ディープリンク                   |
 | ---------------------- | -------------------------------------------------------------- | ---------------------------- |
 | プラットフォーム互換性 | iOS（バージョン9以降）およびAndroid（バージョン6.0以降）  | さまざまなモバイルOSで使用されます    |
-| 目的                | シームレスにWebとアプリのコンテンツをiOSおよびAndroidデバイスでリンクする | 特定のアプリコンテンツへのリンク |
+| 目的                | iOS および Android デバイスの Web コンテンツとアプリコンテンツをシームレスにリンクする | 特定のアプリコンテンツへのリンク |
 | 機能               | コンテキストに基づいてWebページまたはアプリのコンテンツに誘導します           | 特定のアプリ画面を開きます   |
 | アプリインストール       | アプリがインストールされている場合はアプリを開き、それ以外の場合はWebコンテンツを開きます | アプリのインストールが必要です |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
@@ -33,10 +33,10 @@ AppleユニバーサルリンクとAndroidアプリリンクは、Webコンテ
 
 ユニバーサルリンクとアプリリンクは、メールキャンペーンで最も一般的に使用されます。メールはデスクトップとモバイルの両方のデバイスから開いてクリックすることができます。
 
-いくつかのチャンネルはこれらのリンクではうまく機能しません。例えば、プッシュ通知、アプリ内メッセージ、およびコンテンツカードは、スキームベースのディープリンクを使用する必要があります（`mydomain://`）。
+いくつかのチャンネルはこれらのリンクではうまく機能しません。たとえば、プッシュ通知、アプリ内メッセージ、およびコンテンツカードでは、スキームベースのディープリンク (`mydomain://`) を使用する必要があります。
 
 {% alert note %}
-Androidアプリリンクには、他のWeb URLとは別にドメインからのリンクを処理するためのカスタム`IBrazeDeeplinkHandler`が必要です。他のチャネルではメールではなく、ディープリンクを使用し、リンクの方法を統一する方が簡単かもしれません。
+Android アプリリンクでは、他の Web URL とは別にドメインからのリンクを処理するために、カスタム `IBrazeDeeplinkHandler` ロジックが必要です。他のチャネルではメールではなく、ディープリンクを使用し、リンクの方法を統一する方が簡単かもしれません。
 {% endalert %}
 
 ## 前提条件
@@ -50,7 +50,7 @@ Androidアプリリンクには、他のWeb URLとは別にドメインからの
 
 アプリがユニバーサルリンクまたはアプリリンクをサポートするためには、iOSとAndroidの両方でリンクドメインに特別な権限ファイルをホストする必要があります。このファイルには、どのアプリがそのドメインからのリンクを開封できるか、そしてiOSの場合、これらのアプリが開封できるパスが定義されています。
 
-- **iOS: **Apple アプリ Site Association (AASA) file
+- **iOS: **Apple App Site Association(AASA)ファイル
 - **Android :**デジタル資産リンクファイル
 
 この権限ファイルに加えて、アプリ内で設定されているアプリが開封できるリンクドメインのハードコーディングされた定義があります。
@@ -66,32 +66,32 @@ Androidアプリリンクには、他のWeb URLとは別にドメインからの
 
 これらの手順は、Appleの開発者ドキュメントから適応されています。詳細については、[アプリやウェブサイトがあなたのコンテンツにリンクすることを許可する](https://developer.apple.com/documentation/xcode/allowing-apps-and-websites-to-link-to-your-content?language=objc)を参照してください。
 
-### ステップ 1:アプリの権利を構成する
+### ステップ 1: アプリ資格の設定
 
 {% alert note %}
-[Xcode 13以降](https://developer.apple.com/help/account/reference/provisioning-with-managed-capabilities/)、Xcodeは自動的に権利プロビジョニングを処理できます。おそらく[ステップ 1c](#step-1c)にスキップして、問題が発生した場合はこれらの指示に戻ることができます。
+[Xcode 13 以降](https://developer.apple.com/help/account/reference/provisioning-with-managed-capabilities/)では、Xcode は資格プロビジョニングを自動的に処理できます。おそらく[ステップ 1c](#step-1c)にスキップして、問題が発生した場合はこれらの指示に戻ることができます。
 {% endalert %}
 
-#### ステップ 1a: アプリを登録する {#step-1a}
+#### ステップ 1a: アプリ {#step-1a} の登録
 
 1. developer.apple.comを実行してログインしてください。
 2. **証明書、識別子、プロファイル**をクリックします。
 3. **識別子**をクリックします。
-4. 登録済みのアプリ識別子がまだない場合は、+をクリックして作成してください。
+4. アプリ識別子がまだ登録されていない場合は、+ をクリックして作成します。
    a. **名前**を入力してください。これはあなたが望むものなら何でもかまいません。
-   b. **バンドルID**を入力します。Xcodeプロジェクトの**一般**タブからバンドルIDを見つけることができます。
+   b. **バンドルID**を入力します。適切なビルドターゲットのXコードプロジェクトの**General**タブからバンドルIDを見つけることができます。
 
 #### ステップ 1b: アプリ識別子で関連ドメインをオンにする
 
-1. 既存または新しく作成したアプリ識別子で、**アプリサービス**セクションを見つけます。
-2. **関連ドメイン**を選択します。
+1. 既存または新しく作成したApp Identifier で、**App Services** セクションを見つけます。
+2. \[**関連ドメイン**] を選択します。
 3. \[**保存**] をクリックします。
 
 ![]({% image_buster /assets/img_archive/universal_links_1b.png %}){: style="max-width:75%;"}
 
-#### ステップ 1c:Xcodeプロジェクトで関連ドメインをオンにする {#step-1c}
+#### ステップ1c: Xcodeプロジェクトで関連ドメインをオンにする {#step-1c}
 
-続行する前に、Xcodeプロジェクトで、アプリ識別子を登録したのと同じチームが選択されていることを確認してください。 
+続行する前に、Xcode プロジェクトで、アプリ識別子を登録した場所と同じチームが選択されていることを確認してください。 
 
 1. Xcode で、プロジェクトファイルの**Capabilities**タブに移動します。
 2. **関連ドメイン**をオンにします。
@@ -101,23 +101,23 @@ Androidアプリリンクには、他のWeb URLとは別にドメインからの
 「識別子 'your-app-id' を持つアプリIDは利用できません」というエラーが表示された場合。別の文字列を入力してください", 次のことを行ってください:
 
 1. 選択したチームが正しいことを確認してください。
-2. XcodeプロジェクトのバンドルID（[ステップ1a](#step-1a)）がアプリ識別子の登録に使用されたものと一致することを確認してください。
+2. Xcode プロジェクトのバンドル ID ([ステップ1a](#step-1a)) が、アプリ識別子の登録に使用されたものと一致していることを確認します。
 
-#### ステップ 1d:ドメインの権利を追加
+#### ステップ1d: ドメイン資格の追加
 
-ドメインセクションで、適切なドメインタグを追加します。`applinks:`それを接頭辞にする必要があります。この場合、`applinks:yourdomain.com`を追加したことがわかります。
+\[ドメイン] セクションで、適切なドメインタグを追加します。`applinks:` をプレフィックスとして使用する必要があります。この場合、`applinks:yourdomain.com`を追加したことがわかります。
 
 ![]({% image_buster /assets/img_archive/universal_links_1d.png %})
 
-#### ステップ 1e:ビルド時に権利ファイルが含まれていることを確認してください
+#### ステップ1e: ビルド時に権利ファイルが含まれていることを確認してください
 
-プロジェクトブラウザで、新しい権利ファイルが**ターゲットメンバーシップ**の下に選択されていることを確認してください。
+プロジェクトブラウザで、新しい資格ファイルが \[**ターゲットメンバーシップ**] で選択されていることを確認します。
 
 Xcodeはこれを自動的に処理するはずです。
 
 ### ステップ2:Web サイトをホストするようにAASAファイルを構成する
 
-iOSでネイティブアプリとWebサイトのドメインを関連付けるには、WebサイトにApple App Site Association (AASA)ファイルをホストする必要があります。このファイルは、iOSにドメイン所有権を確認するための安全な方法として機能します。iOS 9以前、開発者は検証なしに任意のURIスキームを登録してアプリを開封することができました。しかし、AASAを使用すると、このプロセスははるかに安全で信頼性が高くなります。
+iOSでネイティブアプリとWebサイトのドメインを関連付けるには、WebサイトにApple App Site Association (AASA)ファイルをホストする必要があります。このファイルは、iOS に対するドメイン所有権を安全に検証する手段となります。iOS 9より前では、開発者は検証なしで任意の URI スキームを登録してアプリを開くことができました。しかし、AASAを使用すると、このプロセスははるかに安全で信頼性が高くなります。
 
 AASAファイルには、アプリのリストと、ユニバーサルリンクとして含めるべきまたは除外するべきドメイン上のURLパスを含むJSONオブジェクトが含まれています。こちらはサンプルのAASAファイルです：
 
@@ -146,7 +146,7 @@ AASAファイルには、アプリのリストと、ユニバーサルリンク
 
 ### ステップ 3:ドメインにAASAファイルをホストする
 
-AASAファイルの準備ができたら、`https://<<yourdomain>>/apple-app-site-association`または`https://<<yourdomain>>/.well-known/apple-app-site-association`のいずれかのドメインでホストできます。
+AASA ファイルの準備ができたら、ドメインで`https://<<yourdomain>>/apple-app-site-association` または`https://<<yourdomain>>/.well-known/apple-app-site-association` のいずれかでAASA ファイルをホストできます。
 
 `apple-app-site-association`ファイルをHTTPS Webサーバーにアップロードします。ファイルをサーバーのルートまたは`.well-known`サブディレクトリに配置できます。ファイル名に`.json`を追加しないでください。
 
@@ -162,17 +162,17 @@ AASAファイルをホスティングする際は、ファイルがこれらの
 
 ### ステップ 4:ユニバーサルリンクを処理するためにアプリを準備する
 
-iOSデバイスでユーザーがユニバーサルリンクをタップすると、デバイスはアプリを起動し、[NSUserActivity](https://developer.apple.com/documentation/foundation/nsuseractivity)オブジェクトを送信します。そのアプリは、どのように起動されたかを判断するために、NSUserActivityオブジェクトを照会できます。
+iOSデバイスでユーザーがユニバーサルリンクをタップすると、デバイスはアプリを起動し、[NSUserActivity](https://developer.apple.com/documentation/foundation/nsuseractivity)オブジェクトを送信します。その後、アプリはNSUserActivity オブジェクトを照会して、起動方法を判断できます。
 
-ユニバーサルリンクをアプリでサポートするには、次の手順を実行します:
+アプリでユニバーサルリンクを使用するには、次のステップを実行します。
 
 1. お使いのアプリがサポートするドメインを指定する権利を追加します。
 2. アプリデリゲートを更新して、NSUserActivityオブジェクトを受け取ったときに適切に応答するようにします。
 
-Xcode で、**関連ドメイン** セクションを **機能** タブで開封し、アプリがサポートする各ドメインのエントリを `applinks:` で始めて追加します。例えば、`applinks:www.mywebsite.com`。
+Xコード では、**Capabilities** タブの**Associated Domains** セクションを開封し、`applinks:` の接頭辞を付けたアプリがサポートするドメインごとにエントリを追加します。たとえば `applinks:www.mywebsite.com` です。
 
 {% alert note %}
-Appleは、このリストを20から30のドメインに制限することを推奨しています。
+Apple は、このリストを20～30のドメインに制限することを推奨しています。
 {% endalert %}
 
 ### ステップ 5: ユニバーサルリンクをテストする
@@ -187,7 +187,7 @@ Appleは、このリストを20から30のドメインに制限することを
 これらの手順は、Android開発者ドキュメントから適応されています。詳細については、[Androidアプリリンクの追加](https://developer.android.com/training/app-links#add-app-links)および[アプリコンテンツへのディープリンクの作成](https://developer.android.com/training/app-links/deep-linking)を参照してください。
 
 {% alert note %}
-Androidアプリリンクには、他のWeb URLとは別にドメインからのリンクを処理するためのカスタム`IBrazeDeeplinkHandler`が必要です。他のチャネルではメールではなく、ディープリンクを使用し、リンクの方法を統一する方が簡単かもしれません。
+Android アプリリンクでは、他の Web URL とは別にドメインからのリンクを処理するために、カスタム `IBrazeDeeplinkHandler` ロジックが必要です。他のチャネルではメールではなく、ディープリンクを使用し、リンクの方法を統一する方が簡単かもしれません。
 {% endalert %}
 
 ### ステップ 1:ディープリンクを作成
@@ -196,11 +196,11 @@ Androidアプリリンクには、他のWeb URLとは別にドメインからの
 
 ### ステップ2:アプリをWebサイトに関連付ける
 
-アプリをWebサイトに関連付ける必要があります。これは、デジタルアセットリンクファイルを作成することで実行できます。このファイルは JSON 形式である必要があり、Web サイトへのリンクを開封できる Android アプリに関する詳細が含まれています。それはあなたのWeb サイトの`.well-known`ディレクトリに配置する必要があります。
+アプリをWebサイトに関連付ける必要があります。そのために、デジタルアセットリンクファイルを作成します。このファイルは JSON 形式である必要があり、Web サイトへのリンクを開封できる Android アプリに関する詳細が含まれています。Web サイトの`.well-known` ディレクトリーに配置する必要があります。
 
 ### ステップ 3:アプリのマニフェストファイルを更新してください
 
-アプリケーション要素内にメタデータ要素を追加するには、`AndroidManifest.xml`ファイルに追加します。メタデータ要素には「asset_statements」の`android:name`属性と、Web サイトのURLを含む文字列配列を持つリソースファイルを指す`android:resource`属性が必要です。
+`AndroidManifest.xml` ファイルで、アプリライケーション要素内にメタデータ要素を追加します。メタデータ要素には、「asset_statements」の `android:name` 属性と、Web サイトの URL が含まれる文字列配列を持つリソースファイルを指す `android:resource` 属性が必要です。
 
 ### ステップ 4:アプリをディープリンクに対応させる準備をする
 
@@ -208,7 +208,7 @@ Androidアプリでは、受信したディープリンクを処理する必要
 
 ### ステップ 5: ディープリンクのテスト
 
-最後に、ディープリンクをテストできます。メッセージングアプリやメールを通じて自分にリンクを送信し、それをクリックします。すべてが正しく設定されていれば、アプリを開封するはずです。
+最後に、ディープリンクをテストできます。メッセージングアプリやメールを通じて自分にリンクを送信し、それをクリックします。すべてが正しく設定されている場合は、アプリが開かれます。
 
 {% endtab %}
 {% endtabs %}
@@ -216,14 +216,14 @@ Androidアプリでは、受信したディープリンクを処理する必要
 ## ユニバーサルリンク、アプリリンク、クリックトラッキング
 
 {% alert note %}
-クリック{トラッキング}リンクは通常、{オンボーディング}の一環として{メール}に設定されます。これは顧客オンボーディング中に完了しなかった場合、アカウントマネージャーに連絡して助けを求めてください。
+クリックトラッキングリンクは通常、メールのオンボーディングの一部として設定されます。これがカスタマーオンボーディング中に完了しなかった場合は、アカウントマネージャーに連絡してサポートを受けてください。
 {% endalert %}
 
 私たちのメール送信パートナーであるSendGridとSparkPostは、クリックトラッキングドメインを使用してすべてのリンクをラップし、BrazeのメールでクリックトラッキングのためのURLパラメータを含めます。
 
 例えば、`https://www.example.com`のようなリンクは`https://links.email.example.com/uni/wf/click?upn=abcdef123456…`のようになります。
 
-メールリンクをクリックトラッキングでユニバーサルリンクまたはアプリリンクとして機能させるには、追加の設定が必要です。アプリが開封できるドメインとして、クリックトラッキングドメイン（`links.email.example.com`）を追加してください。さらに、クリックトラッキングドメインは、AASA (iOS) またはデジタルアセットリンク(Android) ファイルを処理する必要があります。これにより、クリックトラッキング付きのメールリンクがシームレスに機能するようになります。
+メールリンクをクリックトラッキングでユニバーサルリンクまたはアプリリンクとして機能させるには、追加の設定が必要です。クリックトラッキングドメイン (`links.email.example.com`) を、アプリを開くことが許可されているドメインとして必ず追加してください。また、クリックトラッキングドメインは、AASA (iOS) またはデジタルアセットリンク (Android) ファイルを提供する必要があります。これにより、クリックトラッキング付きのメールリンクがシームレスに機能するようになります。
 
 すべてのクリックトラッキングリンクをユニバーサルリンクまたはアプリリンクにしたくない場合は、メール送信パートナーに基づいて、どのリンクをユニバーサルリンクにするかを指定できます。詳細については、次のセクションを参照してください。
 
@@ -245,7 +245,7 @@ AMPメールの場合、この属性はdata-universal="true"である必要が
 ```
 
 {:start="3"}
-3\.アプリがラップされたリンクを適切に処理するように設定されていることを確認してください。SendGrid の記事「[SendGrid のトラッキングリンクの解決](https://docs.sendgrid.com/ui/sending-email/universal-links#resolving-sendgrid-click-tracking-links)」を参照し、お使いのオペレーティングシステムに応じた手順に従ってください。この記事には、[iOS](https://docs.sendgrid.com/ui/sending-email/universal-links#resolving-links-in-ios)および[Android](https://docs.sendgrid.com/ui/sending-email/universal-links#resolving-links-in-android)のサンプルコードが含まれています。
+3\.アプリがラップされたリンクを適切に処理するように設定されていることを確認してください。[SendGrid クリックトラッキングリンクの解決](https://docs.sendgrid.com/ui/sending-email/universal-links#resolving-sendgrid-click-tracking-links)に関する SendGrid の記事を参照し、ご使用のオペレーティングシステムのステップに従ってください。この記事には、[iOS](https://docs.sendgrid.com/ui/sending-email/universal-links#resolving-links-in-ios)および[Android](https://docs.sendgrid.com/ui/sending-email/universal-links#resolving-links-in-android)のサンプルコードが含まれています。
 
 この構成では、URL パスに `/uni/` が含まれるリンクはユニバーサルリンクとして機能し、それ以外のリンクは Web リンクとして機能します。
 
@@ -261,7 +261,7 @@ SparkPostのクリックトラッキングリンクをユニバーサルリン
 <a href=”https://www.example.com” data-msys-sublink="open-in-app">
 ```
 
-次に、アプリがカスタムパスを適切に処理するように設定されていることを確認してください。[SparkPost の記事「ディープリンクで SparkPost のクリック トラッキングを使用する」を参照してください](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve#preferred-solution-using-sparkpost-click-tracking-on-deep-links)。この記事には、[iOS](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve#ios-swift-forwarding-clicks-to-sparkpost)および[Android](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve#forwarding-clicks-from-android-to-sparkpost)のサンプルコードが含まれています。
+次に、アプリがカスタムパスを適切に処理するように設定されていることを確認してください。[SparkPost クリックトラッキングの使用](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve#preferred-solution-using-sparkpost-click-tracking-on-deep-links)に関する SparkPost の記事を参照してください。この記事には、[iOS](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve#ios-swift-forwarding-clicks-to-sparkpost)および[Android](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve#forwarding-clicks-from-android-to-sparkpost)のサンプルコードが含まれています。
 
 ### クリックトラッキングによるユニバーサルリンクのトラブルシューティング
 
@@ -269,16 +269,16 @@ SparkPostのクリックトラッキングリンクをユニバーサルリン
 
 #### リンクファイルの場所を確認する
 
-AASAファイル（iOS）またはデジタルアセットリンクファイル（Android）が正しい場所にあることを確認してください。
+AASA ファイル(iOS) またはデジタルアセットリンクファイル (Android) が正しい場所にあることを確認してください。
 
 - **iOS:** `https://click.tracking.domain/.well-known/apple-app-site-association`
 - **Android:** `https://click.tracking.domain/.well-known/assetlinks.json`
 
-これらのファイルが常に公開されていることを確認することが重要です。アクセスできない場合は、メールのユニバーサルリンクの設定でステップを見逃した可能性があります。
+これらのファイルが常に公開アクセス可能であることを確認することが重要です。アクセスできない場合は、メールのユニバーサルリンクの設定でステップを見逃した可能性があります。
 
 #### ドメイン定義を確認する
 
-ドメインの正しい定義がアプリに開封することを許可されていることを確認してください。
+アプリを開くことが許可されているドメインの定義が正しいことを確認してください。
 
-- **iOS: **Xcodeでアプリの関連ドメインの設定を確認します（[ステップ1c]({{site.baseurl}}/help/help_articles/email/universal_links/?tab=ios#step-1c)）。クリックトラッキングドメインがそのリストに含まれていることを確認してください。
-- **Android :**アプリ情報ページを開封します（アプリアイコンを長押しして、ⓘをクリックします）。アプリ情報メニュー内で、**デフォルトで開封**を見つけてタップします。これは、アプリが開封を許可されているすべての確認済みリンクを表示する画面を表示する必要があります。クリックトラッキングドメインがそのリストに含まれていることを確認してください。
+- **iOS: **アプリ用に Xcode で設定された関連ドメインを確認します ([ステップ1c]({{site.baseurl}}/help/help_articles/email/universal_links/?tab=ios#step-1c))。クリックトラッキングドメインがそのリストに含まれていることを確認してください。
+- **Android :**アプリ情報ページを開封します（アプリアイコンを長押しして、ⓘをクリックします）。アプリ情報メニュー内で、**デフォルトで開封**を見つけてタップします。これにより、アプリを開くことが許可されているすべての検証済みリンクが表示されます。クリックトラッキングドメインがそのリストに含まれていることを確認してください。
diff --git a/_lang/ja/_help/help_articles/in-app_messages.md b/_lang/ja/_help/help_articles/in-app_messages.md
index 8ea7baf6131..2709c668534 100644
--- a/_lang/ja/_help/help_articles/in-app_messages.md
+++ b/_lang/ja/_help/help_articles/in-app_messages.md
@@ -3,15 +3,15 @@ page_order: 4
 nav_title: アプリ内メッセージ
 layout: dev_guide
 guide_top_header: "アプリ内メッセージヘルプ記事"
-guide_top_text: "以下のヘルプ記事では、アプリ内メッセージ s の一般的な問題のトラブルシューティングについて説明します。"
+guide_top_text: "以下のヘルプ記事では、アプリ内メッセージに関する一般的な問題のトラブルシューティングについて説明します。"
 
 page_type: landing
-description: "このランディングページは、アプリ内メッセージ s の一般的な問題に関する記事を支援するためのホームページです。"
+description: "このランディングページには、アプリ内メッセージに関する一般的な問題についてのヘルプ記事が含まれています。"
 channel: in-app messages
 noindex: true
 guide_menu_title: ""
 guide_menu_list:
-  - name: アプリ内メッセージの印象が低い
+  - name: アプリ内メッセージのインプレッション数が少ない
     link: /docs/help/help_articles/in-app_messages/in-app_message_impressions_appear_lower_than_expected/
     image: /assets/img/braze_icons/eye.svg
   - name: アプリ内メッセージが表示されない
diff --git a/_lang/ja/_help/help_articles/in-app_messages/in-app_messages_not_displaying.md b/_lang/ja/_help/help_articles/in-app_messages/in-app_messages_not_displaying.md
index 6ec4033fecf..b399a418ff9 100644
--- a/_lang/ja/_help/help_articles/in-app_messages/in-app_messages_not_displaying.md
+++ b/_lang/ja/_help/help_articles/in-app_messages/in-app_messages_not_displaying.md
@@ -15,7 +15,7 @@ channel: in-app messages
 * [イベントトリガー](#event-triggers)
 * [メッセージインプレッション](#message-impressions)
 * [テスト](#run-tests)
-* [セッション timeout](#session-timeout)
+* [セッションタイムアウト](#session-timeout)
 * [メッセージング間隔](#minimum-interval)
 
 ## イベントトリガー
@@ -26,19 +26,19 @@ channel: in-app messages
 
 ## メッセージのインプレッション
 
-SDK内でのアプリ内メッセージUIや配信メカニズムのカスタマイズには、開発者がアプリ内メッセージのインプレッションを手動でログに記録するために当社のメソッドを利用する必要があるかもしれません。開発者に確認して、アプリ内メッセージのカスタマイズを使用しているかどうかを確認してください。
+SDK 内のアプリ内メッセージ UI または配信メカニズムをカスタマイズするには、開発者が Braze のメソッドを使用してアプリ内メッセージインプレッションを手動でログインする必要がある場合があります。開発者に確認して、アプリ内メッセージのカスタマイズを使用しているかどうかを確認してください。
 
 ## テストを実行する
 
-トリガーイベントが発生しないのか、それともメッセージ自体が表示できないのかを判断することが重要です。テストするには、異なるアクション（例えば、セッション開始や異なるカスタムイベント）を使用してメッセージをトリガーし、それが表示されるかどうかを確認します。これにより、これが潜在的にデータの問題であるかどうかを特定するのに役立ちます。
+トリガーイベントが発生していないか、メッセージ自体を表示できないかを特定することが重要です。テストするには、異なるアクション（例えば、セッション開始や異なるカスタムイベント）を使用してメッセージをトリガーし、それが表示されるかどうかを確認します。これにより、これが潜在的にデータの問題であるかどうかを特定するのに役立ちます。
 
-あるいは、異なる種類のアプリ内メッセージテンプレートや画像のサイズを試してみてください。アプリ内メッセージ][15]の仕様が守られなければなりません。場合によっては、画像が大きすぎると、アプリ内メッセージの表示を妨げることがあります。
+あるいは、異なる種類のアプリ内メッセージテンプレートや画像のサイズを試してみてください。\[アプリ内メッセージの仕様][15] に従う必要があります。場合によっては、画像が大きすぎると、アプリ内メッセージの表示を妨げることがあります。
 
 ## セッションタイムアウト
 
 セッションタイムアウトをカスタマイズしたかどうかを確認してください。デフォルトでは、Brazeはセッションの開始時にサーバーからアプリ内メッセージを取得します。
 
-セッションタイムアウトを延長した場合、対象となるアプリ内メッセージを更新できる期間が延長されます。さらに、キャンペーンがセッション開始時にトリガーされるように設定されている場合、新しいセッションが登録されるために適切な時間が経過していることを確認する必要があります。例えば、セッションタイムアウトは30秒にカスタマイズされているかもしれません。アプリを開封してから30秒以内に閉じた場合、セッション開始時にトリガーされる別のアプリ内メッセージを受信する資格はありません。 
+セッションのタイムアウトが延長されると、対象となるアプリ内メッセージを更新できる期間が延長されます。さらに、キャンペーンがセッション開始時にトリガーされるように設定されている場合、新しいセッションが登録されるために適切な時間が経過していることを確認する必要があります。例えば、セッションタイムアウトは30秒にカスタマイズされているかもしれません。30秒以内にアプリを開くか、閉じた場合、セッション開始時にトリガーされた別のアプリ内メッセージを受信できません。 
 
 次のプラットフォームのセッションタイムアウトのカスタマイズについて詳しく学びましょう:
 * \[iOS][16]
@@ -54,7 +54,7 @@ SDK内でのアプリ内メッセージUIや配信メカニズムのカスタマ
 
 インターバルはカスタマイズ可能ですが、ユーザーへの過剰なメッセージングを避けるために設定されています。
 
-まだ助けが必要ですか？開封 a [support ticket]({{site.baseurl}}/braze_support/).
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2021年7月15日_
 
diff --git a/_lang/ja/_help/help_articles/push.md b/_lang/ja/_help/help_articles/push.md
index 0c6548b73fd..6883842094d 100644
--- a/_lang/ja/_help/help_articles/push.md
+++ b/_lang/ja/_help/help_articles/push.md
@@ -2,8 +2,8 @@
 page_order: 5
 nav_title: プッシュ
 layout: dev_guide
-guide_top_header: "プッシュ・ヘルプ"
-guide_top_text: "プッシュメッセージに関する一般的な問題のトラブルシューティングについては、以下のヘルプ記事を参照のこと。"
+guide_top_header: "プッシュに関するヘルプ記事"
+guide_top_text: "プッシュメッセージに関する一般的な問題のトラブルシューティングのサポートについては、以下のヘルプ記事を確認してください。"
 
 page_type: landing
 description: "このランディング・ページには、プッシュ・メッセージに関する一般的な問題に関するヘルプ記事が掲載されている。"
@@ -14,10 +14,10 @@ guide_menu_list:
   - name: 一般的なプッシュ・エラー・メッセージ
     link: /docs/help/help_articles/push/push_error_codes/
     image: /assets/img/braze_icons/alert-circle.svg
-  - name: プッシュ・イネーブルメントの定義
+  - name: プッシュ有効の定義
     link: /docs/help/help_articles/push/defining_push_enablement/
     image: /assets/img/braze_icons/book-closed.svg
-  - name: プッシュ通知の欠落
+  - name: プッシュ通知を受信しない
     link: /docs/help/help_articles/push/no_push_notification_was_received/
     image: /assets/img/braze_icons/message-x-circle.svg
   - name: プッシュトークンを移行する
@@ -26,7 +26,7 @@ guide_menu_list:
   - name: プッシュ権限をリセットする
     link: /docs/help/help_articles/push/resetting_push_permissions/
     image: /assets/img/braze_icons/check-circle.svg
-  - name: プッシュ配信停止の追跡
+  - name: プッシュの配信停止をトラッキングする
     link: /docs/help/help_articles/push/push_unsubscribes/
     image: /assets/img/braze_icons/users-01.svg
 
diff --git a/_lang/ja/_help/help_articles/push/no_push_notification_was_received.md b/_lang/ja/_help/help_articles/push/no_push_notification_was_received.md
index 0c7fcf71aae..1f1ac738397 100644
--- a/_lang/ja/_help/help_articles/push/no_push_notification_was_received.md
+++ b/_lang/ja/_help/help_articles/push/no_push_notification_was_received.md
@@ -1,27 +1,27 @@
 ---
-nav_title: プッシュ通知の欠落
-article_title: プッシュ通知の欠落
+nav_title: プッシュ通知を受信しない
+article_title: プッシュ通知を受信しない
 page_order: 3
 
 page_type: solution
 description: "このヘルプ記事では、ユーザーがプッシュ通知を受け取らない場合のトラブルシューティング手順を説明する。"
 channel: push
 ---
-# プッシュ通知の欠落
+# プッシュ通知を受信しない
 
-プッシュ通知での配信に課題を感じているか？この問題を解決するために、いくつかのステップを踏むことができる：
+プッシュ通知での配信に課題を感じているか？以下の点を確認してこの問題のトラブルシューティングを行うためのステップがいくつかあります。
 
-* [購読状況をプッシュする](#push-subscription-status)
+* [プッシュ通知のサブスクリプションのステータス](#push-subscription-status)
 * [セグメント](#segment)
-* [プッシュ通知キャップ](#push-notification-caps)
+* [プッシュ通知上限](#push-notification-caps)
 * [レート制限](#rate-limits)
-* [対照群の状況](#control-group-status)
+* [コントロールグループステータス](#control-group-status)
 
-### 購読状況をプッシュする
+### プッシュ通知のサブスクリプションのステータス
 
 **ユーザープロファイル**セクションの[Engagement][1]タブでユーザープロファイルを確認し、テストしているワークスペースのプッシュにアクティブに登録されているかどうかを確認します。複数のアプリに登録している場合は、「**Push Registered For**」フィールドに表示される：
 
-![プッシュ登録][2]
+![登録済みのプッシュ通知][2]
 
 Brazeエクスポートエンドポイントを使用してユーザープロファイルをエクスポートすることもできる：
 - \[識別子によるユーザー][12]
@@ -31,13 +31,13 @@ Brazeエクスポートエンドポイントを使用してユーザープロフ
 
 ### セグメント
 
-テストではなく本番のキャンペーンの場合）ターゲットにしているセグメントに該当することを確認する。**ユーザープロフィールでは**、ユーザーが現在属しているセグメントのリストが表示される。セグメンテーションはリアルタイムで更新されるため、これは常に変化する変数であることを忘れてはならない。
+テストではなく本番のキャンペーンの場合）ターゲットにしているセグメントに該当することを確認する。**ユーザープロフィールでは**、ユーザーが現在属しているセグメントのリストが表示される。セグメンテーションはリアルタイムで更新されるため、これは常に変化する変数であることに注意してください。
 
 ![セグメント一覧][3]
 
 ### プッシュ通知キャップ
 
-グローバル周波数キャップをチェックする。ワークスペースにグローバル頻度上限が設定されており、指定された時間枠のプッシュ通知上限をすでに超えているため、プッシュ通知を受け取れなかった可能性がある。
+グローバル周波数の上限を確認します。ワークスペースにグローバル頻度上限が設定されており、指定された時間枠のプッシュ通知上限をすでに超えているため、プッシュ通知を受け取れなかった可能性がある。
 
 これは、ダッシュボードで\[global frequency capping][4] ]をチェックすることでできる。キャンペーンがフリークエンシー・キャッピング・ルールに従うように設定されている場合、これらの設定によって影響を受けるユーザーが多数存在する。
 
@@ -45,25 +45,25 @@ Brazeエクスポートエンドポイントを使用してユーザープロフ
 
 ### レート制限
 
-キャンペーンやキャンバスにレートリミットを設定している場合、このリミットを超えたためにメッセージの受信から外れてしまう可能性がある。詳しくは\[Rate Limiting][9]]を参照のこと。
+キャンペーンまたはキャンバスにレート制限が設定されている場合、この制限を超過したためにメッセージングを受信できなくなる可能性があります。詳細については、\[レート制限][9] を参照してください。
 
-### 対照群の状況
+### コントロールグループステータス
 
 これが単一チャンネルのキャンペーンや、コントロールグループのあるキャンバスであれば、コントロールグループに属している可能性がある。
 
-  1. バリアント分布][6] 、対照群があるかどうかを確認する。
-  2. もしそうなら、\[キャンペーンコントロールグループ][7] ]のセグメントフィルタリングを作成し、\[セグメント][8] をエクスポートし、あなたのユーザーIDがこのリストにあるかどうかをチェックする。
+  1. \[バリアントの分布][6] をチェックして、コントロールグループがあるかどうかを確認します。
+  2. ある場合は、\[キャンペーンのコントロールグループ内][7] にセグメントフィルターを作成し、\[セグメントをエクスポート][8] して、ユーザー ID がこの一覧に含まれているかどうかを確認します。
 
 ### 有効なプッシュトークン
-プッシュトークンは、送信者が特定のデバイスにプッシュ通知を行うための識別子である。つまり、デバイスが有効なプッシュトークンを持っていなければ、そのデバイスにプッシュ通知を送ることはできない。 
+プッシュトークンは、送信者がプッシュ通知を持つ特定の機器を対象にするために使用する識別子です。つまり、デバイスが有効なプッシュトークンを持っていなければ、そのデバイスにプッシュ通知を送ることはできない。 
 
 ### プッシュ通知タイプ
 
 正しい種類のプッシュ通知を使用しているか確認する。例えば、FireTVをターゲットにしたい場合は、Androidのプッシュ・キャンペーンではなく、Kindleのプッシュ通知を使うことになる。Brazeのワークフローを理解するための詳細については、以下の記事をチェックしてほしい：
-- \[アップルのプッシュ通知][10]
-- \[Firebaseクラウドメッセージング][11]
+- \[Appleプッシュ通知]][10]
+- \[Firebase クラウドメッセージング][11]
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2021年1月21日_
 
diff --git a/_lang/ja/_help/help_articles/push/push_enablement.md b/_lang/ja/_help/help_articles/push/push_enablement.md
index 852be56f1ee..9dfe210fb71 100644
--- a/_lang/ja/_help/help_articles/push/push_enablement.md
+++ b/_lang/ja/_help/help_articles/push/push_enablement.md
@@ -1,25 +1,25 @@
 ---
-nav_title: プッシュ・イネーブルメントの定義
-article_title: プッシュ・イネーブルメントの定義
+nav_title: プッシュ通知有効を定義する
+article_title: プッシュ通知有効を定義する
 page_order: 1
 
 page_type: solution
-description: "このヘルプでは、ユーザーのプッシュ有効化ステータスを説明するために使用される2つの基本用語を定義する。"
+description: "このヘルプ記事では、ユーザーのプッシュ通知有効ステータスを説明するために使用される 2 つの基本用語を定義します。"
 channel: push
 ---
 
-# プッシュ・イネーブルメントの定義
+# プッシュ通知有効を定義する
 
-最初にプッシュ通知を設定する際、どのユーザーがどのようにメッセージを受け取るかを理解することが重要だ。
+プッシュ通知の初回設定時には、どのユーザーがどのようにメッセージを受信するのかを理解することが重要です。
 
-プッシュ有効とは、プッシュトークンが利用可能なユーザーを指す。例えば、これはワークスペース内のアプリのアクティブなプッシュトークンかもしれない。
+プッシュ通知が有効とは、プッシュトークンが利用可能なユーザーを指します。例えば、これはワークスペース内のアプリに対するアクティブなプッシュトークンである可能性があります。
 
-バックグラウンド・プッシュ有効とは、プッシュは有効だが、フォアグラウンド・プッシュ通知を無効にしているユーザーを指す。この場合、Brazeはそのデバイスにユーザーから見える通知を表示できない。しかし、アンインストールの追跡、サイレント・プッシュ通知の有効化、ジオフェンシングのためにバックグラウンド・プッシュを使うことができる。  
+バックグラウンドのプッシュ通知が有効とは、プッシュ通知は有効であるものの、フォアグラウンドプッシュ通知が無効であるユーザーを指します。この場合、Braze はそのデバイスにユーザーから見える通知を表示できません。ただし、アンインストールのトラッキング、サイレントプッシュ通知の有効化、ジオフェンシングのためにバックグラウンドプッシュ通知を使用できます。  
 
-詳しくは、[プッシュ通知についてを][1]ご覧いただきたい。
+詳細については、[プッシュ通知][1]に関する記事をご覧ください。
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+サポートが必要な場合は、[サポートチケット]({{site.baseurl}}/braze_support/)を登録してください。
 
-_最終更新日：2021年1月24日_
+_最終更新日: 2021年1月24日_
 
 [1]: {{site.baseurl}}/user_guide/message_building_by_channel/push/about
\ No newline at end of file
diff --git a/_lang/ja/_help/help_articles/push/push_error_codes.md b/_lang/ja/_help/help_articles/push/push_error_codes.md
index de64b9363cb..605f4a9eccc 100644
--- a/_lang/ja/_help/help_articles/push/push_error_codes.md
+++ b/_lang/ja/_help/help_articles/push/push_error_codes.md
@@ -16,40 +16,40 @@ platform:
 プッシュ・メッセージのよくあるエラーメッセージをチェックしてみよう：
 
 {% tabs %}
-{% tab アンドロイド %} 
-### プッシュが跳ねた：送信者IDの不一致
-`MismatchSenderId` は認証が失敗したことを示します。Firebase Cloud Messaging (FCM)は、送信者IDとFCM APIキーという2つの重要なデータで認証を行う。 いずれも正確性を検証する必要がある。詳細については、この問題に関する[Androidのドキュメントを](https://firebase.google.com/docs/cloud-messaging/http-server-ref#error-codes)参照のこと。
+{% tab Android %} 
+### プッシュバウンス: MismatchSenderId
+`MismatchSenderId` は認証が失敗したことを示します。Firebase クラウドメッセージング (FCM) の認証には、senderID と FCM API キーという2つの重要なデータが使用されます。 これら2つの正確性を検証する必要があります。詳細については、この問題に関する[Androidのドキュメントを](https://firebase.google.com/docs/cloud-messaging/http-server-ref#error-codes)参照のこと。
 
-よくある故障には、以下のようなものがある：
+よくある失敗には、次のものがあります。
 - 不正な[送信者ID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/integration/standard_integration/#step-1-enable-firebase)
 - 別のプッシュサービスに別の送信者IDで登録した場合、多重登録される。
 
-### プッシュが跳ねた：InvalidRegistration
-`InvalidRegistration` プッシュトークンが不正な形である場合に起こりうる。よくある故障には、以下のようなものがある：
-- 人々はBrazeの登録トークンを手動で渡しているが、`getToken()` 。例えば、インスタンスID全体を渡すこともできる。エラーメッセージのトークンは`&#124;ID&#124;1&#124;:[regular token]` のようだ。  
-- 人々は複数のサービスに登録している。現在、プッシュ登録のインテントが古いスタイルで到着することを期待しているため、人々が複数の場所で登録し、他のサービスからのインテントをキャッチした場合、不正なプッシュトークンを取得する可能性がある。
+### プッシュバウンス: InvalidRegistration
+`InvalidRegistration` は、プッシュトークンの形式が正しくない場合に発生します。よくある失敗には、次のものがあります。
+- ユーザはBraze登録トークンを手動で渡していますが、`getToken()` を呼び出さないでください。例えば、インスタンス ID 全体が渡される場合があります。エラーのトークンは`&#124;ID&#124;1&#124;:[regular token]` のようになります。  
+- 複数のサービスに登録しています。現在、プッシュ登録のインテントが古いスタイルで到着することを期待しているため、人々が複数の場所で登録し、他のサービスからのインテントをキャッチした場合、不正なプッシュトークンを取得する可能性がある。
 
-### プッシュが跳ねた：NotRegistered
+### プッシュバウンス: NotRegistered
 `NotRegistered` 通常、アプリがデバイスから削除されたことを意味する（アンインストールの合図など）。これは、複数の登録が行われていて、2回目の登録がBrazeが受け取るプッシュトークンを無効にしている場合にも発生する可能性がある。
 
 {% endtab %}
 {% tab iOS %}
 
-### プッシュが跳ねた：不正なプッシュトークンへの送信エラー
+### プッシュバウンス: 不正なプッシュトークンへの送信エラー
 
 このエラーはいくつかの理由で発生する可能性がある：
-- でプッシュトークンが正しく送信されていない。 `[[Appboy sharedInstance] registerPushToken:]`
-	- **メッセージアクティビティログで**トークンを確認する。一般的には、文字と数字の長い文字列のように見えるはずである。(e.g `6e407a9be8d07f0cdeb9e714733a89445f57a89ec890d63867c482a483506fa6`) そうでない場合は、Brazeのプッシュトークンエラー送信に関わるコードをチェックする。<br><br>
+- 現在、`[[Appboy sharedInstance] registerPushToken:]` でプッシュトークンが正しく送られてこない
+	- **Message Activity Log**のトークンを確認してください。通常は、文字と数字を含む長い文字列のように見えるはずです (e.g `6e407a9be8d07f0cdeb9e714733a89445f57a89ec890d63867c482a483506fa6`)。そうでない場合は、Braze プッシュトークンエラーの送信に関連するコードを確認してください。<br><br>
 - プロビジョニング環境の不一致：
 	- 開発用の証明書で登録し、本番用の証明書で送信しようとすると、このようなエラーが表示される。  
-	- Brazeは、本番環境用のユニバーサル証明書のみをサポートしている。ユニバーサル証明書を使用した開発環境でのプッシュテストは機能しない。 
-	- このレポートは本番ではバウンスを送信するが、開発では送信しない。<br><br>
+	- Braze は、本番環境のユニバーサル証明書のみをサポートしています。ユニバーサル証明書を使用した開発環境でのプッシュテストは機能しない。 
+	- このレポートは、プロダクションではバウンスを送信しますが、開発では送信しません。<br><br>
 - プロビジョニング・プロファイルの不一致：
-	- これは、トークンの取得に使われた証明書とあなたの証明書が一致しない場合に起こりうる。これが疑われる場合、次のステップがある：
+	- この問題は、証明書がトークンの取得に使用された証明書と一致しない場合に発生する可能性があります。これが疑われる場合、次のステップは次のようになります。
 		- Brazeダッシュボードからのプッシュ送信に使用するプッシュ証明書とプロビジョニングプロファイルが正しく設定されていることを確認する。
-		- APNS証明書を再作成し、APNS証明書が`app_id` に設定された後、プロビジョニングプロファイルを再作成する。これによって、より目に見える問題が解決されることもある。
+		- APNS 証明書を再作成し、APNS 証明書が `app_id` に設定された後にプロビジョニングプロファイルを再作成します。これによって、より目に見える問題が解決されることもある。
 
-### プッシュが跳ねた：APNSフィードバックサービスが削除された
+### プッシュバウンス: APNSフィードバックサービスが削除された
 
 これは通常、誰かがアンインストールしたときに起こる。Brazeは毎晩APNSフィードバックサービスに問い合わせ、無効なトークンのリストを取得する。詳細については、Appleの「[Communicating with APNs](https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/CommunicatingwithAPNs.html)」を参照のこと。
 
diff --git a/_lang/ja/_help/help_articles/push/push_token_migration.md b/_lang/ja/_help/help_articles/push/push_token_migration.md
index 0e879b2b518..04ab4a6a503 100644
--- a/_lang/ja/_help/help_articles/push/push_token_migration.md
+++ b/_lang/ja/_help/help_articles/push/push_token_migration.md
@@ -10,37 +10,37 @@ channel: push
 
 # プッシュトークンを移行する
 
-[プッシュトークンは]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_registration/#push-tokens/)、アプリの通知先を指定する一意の匿名識別子である。Brazeは、AndroidのFirebase Cloud Messaging Service（FCM）やiOSのApple Push Notification Service（APN）のようなプッシュサービスプロバイダーと接続し、これらのプロバイダーは、あなたのアプリを識別するユニークなデバイストークンを送信する。Brazeを統合する前に、自社または他のプロバイダー経由でプッシュ通知を送信していた場合、プッシュトークンの移行により、プッシュトークンを登録したユーザーにプッシュ通知を送信し続けることができる。
+[プッシュトークン]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_registration/#push-tokens/) は、アプリの通知の送信先を指定する一意の匿名識別子です。Brazeは、AndroidのFirebase Cloud Messaging Service（FCM）やiOSのApple Push Notification Service（APN）のようなプッシュサービスプロバイダーと接続し、これらのプロバイダーは、あなたのアプリを識別するユニークなデバイストークンを送信する。Brazeを統合する前に、自社または他のプロバイダー経由でプッシュ通知を送信していた場合、プッシュトークンの移行により、プッシュトークンを登録したユーザーにプッシュ通知を送信し続けることができる。
 
 ## SDKによる自動移行
 
 Braze SDKは、過去にプッシュ通知をオプトインしたユーザーのプッシュトークンを、Brazeと統合されたアプリやサイトに初めてサインインした時に自動的に移行する。Braze SDKを統合すれば、APIを使用してプッシュトークンを移行する必要はない。
 
-ただし、プッシュトークンはユーザーがアプリに最初にログインしたときに移行するため、SDK統合後にログインしていないユーザーにはBrazeからプッシュ通知を送信できないことに注意。これらのユーザーと再びエンゲージする方法として、AndroidとiOSのプッシュトークンを手動で移行することを望むかもしれない。
+ただし、プッシュトークンはユーザーがアプリに最初にログインしたときに移行するため、SDK統合後にログインしていないユーザーにはBrazeからプッシュ通知を送信できないことに注意。これらのユーザーを再エンゲージする手段として、Android および iOS プッシュトークンを手動で移行することもできます。
 
 {% alert note %}
-ウェブ・プッシュ・トークンの性質上、トークンは60日ごとに期限切れとなり、リセットされる。その期間内にセッションを持たない者は、アクティブなウェブ・プッシュ・トークンを持たないことになる。Brazeは期限切れのWebプッシュトークンを移行しない。このようなユーザーには、[プッシュ・プライマーを通じて]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/push_primer_messages)再参加してもらう必要がある。
+ウェブプッシュトークンs の性質上、トークンは約60 日間ごとに失効し、再設定されます。その期間内にセッションがないユーザーには、アクティブな Web プッシュトークンがありません。Brazeは期限切れのWebプッシュトークンを移行しない。これらのユーザーは、[プッシュプライマー]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/push_primer_messages)を使用して再エンゲージする必要があります。
 {% endalert %}
 
 ## API経由の手動移行
 
 手動プッシュトークンマイグレーションは、これらの以前に作成されたキーを、APIを通じてBrazeプラットフォームにインポートするプロセスである。
 
-[`users/track` エンドポイントを]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)使用して、iOS (APNs) および Android (FCM) トークンをお客様のプラットフォームにプログラム的に移行する。特定ユーザー（関連する外部IDを持つユーザー）と匿名ユーザー（外部IDを持たないユーザー）の両方を移行できる。
+[`users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) を使用して、iOS (APN s) およびAndroid (FCM) トークンs をプラットフォームにプログラムで移行します。特定ユーザー（関連する外部IDを持つユーザー）と匿名ユーザー（外部IDを持たないユーザー）の両方を移行できる。
 
 プッシュトークン移行時にアプリの`app_id` を指定し、適切なプッシュトークンを適切なアプリに関連付ける。各アプリ（iOS、Androidなど）にはそれぞれ`app_id` 、[API Keys]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/)ページの**Identification**セクションで確認できる。必ず正しいプラットフォームの`app_id` を使用すること。
 
 {% alert important %}
-APIを通じてウェブ・プッシュ・トークンを移行することはできない。これは、ウェブ・プッシュ・トークンが他のプラットフォームと同じスキーマに準拠していないためだ。 
+API を使用してウェブプッシュトークンを移行することはできません。これは、ウェブ・プッシュ・トークンが他のプラットフォームと同じスキーマに準拠していないためだ。 
 
-<br>ウェブ・プッシュ・トークンをプログラムで移行しようとすると、次のようなエラーが表示されることがある： `Received '400: Invalid subscription auth' sending to 'https://fcm.googleapis.com/fcm/send`
+<br>ウェブプッシュトークンをプログラムで移行しようとすると、次のようなエラーが表示されることがあります。 `Received '400: Invalid subscription auth' sending to 'https://fcm.googleapis.com/fcm/send`
 
 <br>
-APIマイグレーションの代替として、SDKを統合し、トークン・ベースが自然に再投入されるようにすることをお勧めする。
+APIマイグレーションの代わりに、SDKを統合し、トークン基盤が自然に再集積できるようにすることをお勧めします。
 {% endalert %}
 
 ### 外部IDが存在する場合は移行する
-特定されたユーザーの場合、`push_token_import` フラグを`false` に設定し（またはパラメータを省略し）、ユーザー`attributes` オブジェクトに`external_id` 、`app_id` 、`token` の値を指定する。 
+識別されたユーザーの場合は、`push_token_import` フラグを`false` に設定 (またはパラメーターを省略) して、`external_id`、`app_id`、`token` の値をユーザー `attributes` オブジェクトで指定します。 
 
 以下に例を示します。
 
@@ -65,7 +65,7 @@ curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
 ```
 
 ### 外部IDが存在しない場合の移行
-他のシステムからプッシュトークンをインポートする場合、`external_id` が利用できるとは限らない。この場合、`push_token_import` フラグを`true` とし、`app_id` と`token` の値を指定する。Brazeは、各トークンについて一時的な匿名ユーザープロフィールを作成し、これらの個人とのメッセージのやり取りを継続できるようにする。トークンがすでにBrazeに存在する場合、リクエストは無視される。
+他のシステムからプッシュトークンをインポートする場合、`external_id` が利用できるとは限らない。この状況では、`push_token_import` フラグを`true` に設定し、`app_id` と`token` の値を指定します。Braze は、トークンごとに一時的な匿名ユーザープロファイルを作成し、これらの個人にメッセージを送信し続けられるようにします。トークンがすでにBrazeに存在する場合、リクエストは無視される。
 
 以下に例を示します。
 
@@ -103,12 +103,12 @@ curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
 
 インポート後、匿名ユーザーがBraze対応バージョンのアプリを起動すると、Brazeは自動的にインポートしたプッシュトークンをBrazeユーザープロファイルに移動し、一時的なプロファイルをクリーンアップする。
 
-Brazeは、プッシュトークンを持っていない`push_token_import` フラグの匿名プロフィールを見つけるために、月に1回チェックする。匿名プロフィールにプッシュトークンがなくなった場合、プロフィールを削除する。しかし、匿名プロファイルがまだプッシュトークンを持っていて、実際のユーザーがまだそのプッシュトークンでデバイスにログインしていないことを示唆している場合は、何もしない。
+Braze は月に1回チェックを実行し、プッシュトークンがない `push_token_import` フラグが設定された匿名プロファイルを見つけます。匿名プロフィールにプッシュトークンがなくなった場合、プロフィールを削除する。しかし、匿名プロファイルがまだプッシュトークンを持っていて、実際のユーザーがまだそのプッシュトークンでデバイスにログインしていないことを示唆している場合は、何もしない。
 
 ## Androidのプッシュトークンをインポートする
 
 {% alert important %}
-iOSアプリには、プッシュを表示するためのフレームワークが1つしかなく、Brazeが必要なプッシュトークンと証明書を持っている限り、プッシュ通知はすぐにレンダリングされるからだ。
+以下の考慮事項は Android アプリにのみ適用されます。iOS アプリでは、プッシュを表示するためのフレームワークがプラットフォームに1つしかないため、これらのステップは必要ありません。また、Braze に必要なプッシュトークンと証明書がある限り、プッシュ通知は即時にレンダリングされます。
 {% endalert %}
 
 Braze SDKの統合が完了する前にAndroidプッシュ通知をユーザーに送信する必要がある場合は、キーと値のペアを使用してプッシュ通知を検証する。 
diff --git a/_lang/ja/_help/help_articles/push/push_unsubscribes.md b/_lang/ja/_help/help_articles/push/push_unsubscribes.md
index c5458b8d7d7..f5b399aa088 100644
--- a/_lang/ja/_help/help_articles/push/push_unsubscribes.md
+++ b/_lang/ja/_help/help_articles/push/push_unsubscribes.md
@@ -1,34 +1,34 @@
 ---
-nav_title: プッシュ・アンサブスクライブのトラッキング
-article_title: プッシュ・アンサブスクライブのトラッキング
+nav_title: プッシュの配信停止をトラッキングする
+article_title: プッシュの配信停止をトラッキングする
 page_type: solution
-description: "このヘルプでは、プッシュ配信停止を追跡するためのヒントをいくつか紹介します。"
+description: "このヘルプでは、プッシュの配信停止をトラッキングするためのヒントをいくつか紹介します。"
 channel: push
 ---
 
-# プッシュ配信停止の追跡
+# プッシュの配信停止をトラッキングする
 
-プッシュ配信停止sは、アップルやグーグルなどのプロバイダからのユーザーのプッシュステータスへの更新に依存します。これらの更新s は、頻度が低く、予測不可能な場合があります。そのため、プッシュ配信停止sはプッシュキャンペーン 分析のメトリクスとして含まれません。 
+プッシュの配信停止は、Apple や Google などのプロバイダーからのユーザーのプッシュステータスに対する更新に依存します。これらの更新は、頻度が低く、予測不可能な場合があります。そのため、プッシュの配信停止は、プッシュキャンペーン分析の指標として含まれません。 
 
-ただし、手動でプッシュ配信停止を"トラッキングすると、通知頻度と内容の関連性に対するユーザーレスポンスに貴重なインサイトを提供することができます。"トラッキングプッシュ配信停止sには、次の2つの方法があります。
+ただし、手動でプッシュの配信停止をトラッキングすると、通知の頻度とコンテンツの関連性に対するユーザー応答に関する重要なインサイトが得られます。プッシュの配信停止のトラッキングには、次の2つのオプションがあります。
 
 ## オプション 1: Segment フィルターsを使用
 
-回避策として、Segmentを作成して、プッシュが有効になっていないユーザーを識別できます。つまり、サブスクライブまたはオプトインされておらず、[フォアグラウンドプッシュトークン]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_registration/#push-tokens)がありません。たとえば、Android アプリ内の配信停止の個数を表示するには、次のSegments の組合せを使用します。 
+回避策として、Segmentを作成して、プッシュが有効になっていないユーザーを識別できます。つまり、サブスクライブまたはオプトインされておらず、[フォアグラウンドプッシュトークン]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_registration/#push-tokens)がありません。例えば、Android アプリで配信停止の数を表示するには、次のセグメントの組み合わせを使用します。 
 
 - `Background or Foreground Push Enabled for App "TEST (Android)" is false`
 - `Has Uninstalled`
 
-![フィルター "Background またはForeground Push Enabled for アプリ"TEST (Android) アプリがfalse で、フィルター "Has Uninstalled"が選択され、2393 の到達可能なユーザーs.]({% image_buster /assets/img/push_unsub_segment_example.png %})が表示されます。
+![TEST (Android) アプリのフィルター \[アプリのバックグラウンドまたはフォアグラウンドプッシュが有効] を含むセグメントビルダーセクションが false で、フィルター \[アンインストールされました] が選択されているため、到達可能な 2,393 ユーザーが表示されています。]({% image_buster /assets/img/push_unsub_segment_example.png %})
 
-セグメンテーション フィルターs はアプリ近接であり、特に日付とキャンペーンに結びつけることはできません。
+セグメンテーションフィルターは概算であり、日付やキャンペーンに具体的に関連付けることはできません。
 
 ## オプション 2: カスタムイベントの使用
 
 {% alert important %}
-サブスクリプション変更のカスタムイベントを記録すると、[データポイント s]({{site.baseurl}}/user_guide/data_and_analytics/data_points#consumption-count) が消費されることに注意してください。または、Segment フィルターs を使用して、プッシュが有効になっていないユーザーを識別し、対象にします。
+サブスクリプション変更のカスタムイベントを記録すると、[データポイント]({{site.baseurl}}/user_guide/data_and_analytics/data_points#consumption-count)が消費されることにご注意ください。または、セグメントフィルターを使用して、プッシュが有効になっていないユーザーを識別し、ターゲットにします。
 {% endalert %}
 
-別の回避策では、このメトリクスを追跡するために、ユーザーのプッシュ有効ステータスが`true` または`false` のいずれであるかに基づいてプッシュ配信停止s のカスタムイベントを作成することもお勧めします。
+別の回避策として、この指標をトラッキングするために、ユーザーのプッシュ有効ステータスが`true` か`false` かに基づいて、プッシュの配信停止のカスタムイベントを作成することもお勧めします。
 
-_2024更新6月13日昨日_
+_最終更新日: 2024年6月13日_
diff --git a/_lang/ja/_help/help_articles/push/reducing_payload_size.md b/_lang/ja/_help/help_articles/push/reducing_payload_size.md
index 69eef21bd8d..b220e4bdb8a 100644
--- a/_lang/ja/_help/help_articles/push/reducing_payload_size.md
+++ b/_lang/ja/_help/help_articles/push/reducing_payload_size.md
@@ -19,9 +19,9 @@ channel: push
 プッシュサービスプロバイダーは、プッシュペイロード全体のバイトサイズを確認することで、プッシュ通知がユーザーに表示できるかどうかを計算します。ペイロードはほとんどのプッシュサービスで**4KB（4,096バイト）**に制限されています。含む：
 
 - Appleプッシュ通知サービス（APNs）
-- AndroidのFirebase Cloudメッセージング（FCM）
+- Android の Firebase Cloud Messaging (FCM)
 - Web プッシュ
-- ファーウェイプッシュ
+- Huawei プッシュ
 
 これらのプッシュサービスは、この制限を超える通知を拒否します。
 
@@ -30,7 +30,7 @@ Brazeは、統合および分析の目的でプッシュペイロードの一部
 プッシュ内の次の要素がプッシュペイロードを構成します：
 
 - コピー、タイトルやメッセージ本文など
-- Liquidパーソナライゼーションの最終レンダー
+- Liquid パーソナライゼーションの最終レンダリング
 - 画像のURL（ただし、画像自体のサイズは含まれません）
 - クリックターゲットのURL
 - ボタン名
@@ -42,5 +42,5 @@ Brazeは、統合および分析の目的でプッシュペイロードの一部
 
 - メッセージを簡潔に保つ。一般的なガイドラインとして、40文字以内で実行可能で有益なものにすることです。
 - 空白と改行をコピーから省略します。
-- Liquidが送信時にどのようにレンダリングされるかを考慮してください。Liquidパーソナライゼーションの最終レンダーはユーザーごとに異なるため、Liquidが含まれている場合、Brazeはプッシュペイロードがサイズ制限を超えるかどうかを判断できません。Liquid が短いメッセージをレンダリングする場合は、大丈夫かもしれません。ただし、Liquidの結果が長いメッセージになる場合、プッシュがペイロードサイズの制限を超える可能性があります。常にプッシュメッセージをユーザーに送信する前に実際のデバイスでテストしてください。
+- Liquid が送信時にどのようにレンダリングされるかを考慮します。Liquidパーソナライゼーションの最終レンダーはユーザーごとに異なるため、Liquidが含まれている場合、Brazeはプッシュペイロードがサイズ制限を超えるかどうかを判断できません。Liquid が短いメッセージをレンダリングする場合は、大丈夫かもしれません。ただし、Liquidの結果が長いメッセージになる場合、プッシュがペイロードサイズの制限を超える可能性があります。常にプッシュメッセージをユーザーに送信する前に実際のデバイスでテストしてください。
 - URL短縮サービスを使用してURLを短縮することを検討してください。
diff --git a/_lang/ja/_help/help_articles/push/resetting_push_permissions.md b/_lang/ja/_help/help_articles/push/resetting_push_permissions.md
index 2b4b517f32e..e090291901a 100644
--- a/_lang/ja/_help/help_articles/push/resetting_push_permissions.md
+++ b/_lang/ja/_help/help_articles/push/resetting_push_permissions.md
@@ -6,14 +6,14 @@ description: "このヘルプ記事では、ブラウザのプッシュ権限と
 channel: push
 ---
 
-# 再設定プッシュ権限
+# プッシュ権限のリセット
 
-ブラウザーでプッシュ通知に問題が発生した場合は、サイトの通知権限を再設定し、サイトの記憶領域を消去する必要があります。ヘルプについては、これらのステップを参照してください。
+ブラウザーでプッシュ通知の問題が発生した場合は、サイトの通知権限をリセットし、サイトのストレージをクリアする必要がある場合があります。サポートが必要な場合は、以下のステップを参照してください。
 
 ## デスクトップのChrome をリセットする
 
 1. Chrome ブラウザのURL の横にある**View Site Information** スライダアイコンをクリックします。
-2. **Notifications**の下で、**Reset permission**をクリックします。
+2. \[**通知**] で、\[**権限をリセット**] をクリックします。
 3. Chrome DevTools を開きます。オペレーティングシステムごとの関連するショートカットは次のとおりです。
 
 <style> 
@@ -24,40 +24,40 @@ table {
 
 | OS      | キーボードショートカット                                                  |
 | ------- | ------------------------------------------------------------------- |
-| マック      | `Fn` + `F12`<br>`Ctrl` + `Shift` + `I` |
+| Mac      | `Fn` + `F12`<br>`Ctrl` + `Shift` + `I` |
 | Windows | `F12`<br>`Ctrl` + `Shift` + `I` |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {:start="4"}
 4\.DevTools で、**Application** タブに移動します。
 5. サイドバーで、**Storage** を選択します。
-6. **サイトデータクリア**をクリックします。
-7. 更新 d 設定 sをアプリするために、再度読み込むするように求められます。**Re 読み込む**を押します。
+6. \[**サイトデータをクリア**] をクリックします。
+7. 更新された設定を適用するために、Chrome でページの再読み込みを求められます。\[**再読み込み**] をクリックします。
 
 プッシュ権限がリセットされます。サイトに新しいタブを開き、試してみてください。
 
-## Android時のクロムの初期化
+## Android で Chrome をリセットする
 
-Android 通知ドロワーに通知が表示されている場合:
+Android 通知ドロワーにサイトからの通知が表示されている場合:
 
 1. プッシュ通知から<i class="fas fa-cog" title="設定s"></i>をタップし、**Site 設定s**を選択します。
 2. **サイト設定s**から**クリア&リセット**をタップします。
 
-開封からの通知がない場合:
+サイトからの通知が開かれていない場合:
 
-1. Androidでクロームを開きます。
+1. Android で Chrome を開きます。
 2. <i class="fas fa-ellipsis-vertical"></i>メニューをタップします。
-3. **Settings**> **Site Settings**> **Notifications**に移動します。
-4. 通知が「&quot」に設定されていることを確認します。送信時に確認する(推奨)"。
-5. リストからサイトを検索します。
-6. エントリを選択し、**クリア&リセット**をタッチします。
+3. \[**設定**] > \[**サイトの設定**] > \[**通知**] に移動します。
+4. 通知が \[送信前に確認する (推奨)] に設定されていることを確認します。
+5. リストでサイトを見つけます。
+6. エントリを選択し、\[**クリアしてリセット**] をタップします。
 
 プッシュ権限がリセットされます。サイトに新しいタブを開き、試してみてください。
 
 ## デスクトップのFirefox をリセットする
 
-1. サイトURL の横にある<i class="fa-solid fa-circle-info" alt="info icon"></i> または<i class="fas fa-lock" alt="lock icon"></i> をクリックします。
-2. **Permissions**で、**Receive 通知 s**の横にある<i class="fa-solid fa-circle-xmark" title="この権限をクリアし、再度"></i>に通知権限をクリアしてください。
+1. サイトURL の横にある <i class="fa-solid fa-circle-info" alt="info icon"></i> または <i class="fas fa-lock" alt="lock icon"></i> をクリックします。
+2. \[**権限**] で、\[**通知を受信**] の横にある \[<i class="fa-solid fa-circle-xmark" title="この権限をクリアして再度確認"></i>] を選択して通知権限をクリアします。
 3. 同じメニューで、**Clear Cookies and Site Data**を選択します。
 4. 選択内容を確認するための画面がアプリされます。**OK**をクリックします。
 
@@ -67,22 +67,22 @@ Android 通知ドロワーに通知が表示されている場合:
 
 Androidのプッシュ権限を再設定するには、この[Mozilla サポート記事](https://support.mozilla.org/en-US/kb/clear-your-browsing-history-and-other-personal-data#w_clear-specific-items-from-your-browser) を参照してください。
 
-## macOS でのSafari のリセット
+## macOS での Safari のリセット
 
 {% alert note %}
-これらのステップはmacOS 専用です。Apple は、Windows ではWeb Push for Safari に対応していません。
+これらのステップは macOS 専用です。Apple は、Windows では Safari の Web プッシュをサポートしていません。
 {% endalert %}
 
 1. Safari を開きます。
 2. Macの[メニューバーから、**Safari**> **設定**> **Webサイト**> **通知**に進みます。
 3. リストからサイトを選択します。
 4. **Remove**を押すと、サイトの通知権限が削除されます。
-5. 次に、**プライバシー**> **Webサイトデータ**に移動します。
+5. 次に、\[**プライバシー**] > \[**Web サイトデータを管理**] に移動します。
 6. リストからサイトを選択します。
 7. **Remove**をクリックするか、すべてのサイトデータを削除するには、**Remove All**をクリックします。
-8. **Done**をクリックします。
+8. \[**完了**] をクリックします。
 
 プッシュ権限がリセットされます。サイトに新しいタブを開き、試してみてください。
 
 
-*2024更新2月12日の昨日d*
\ No newline at end of file
+*最終更新日: 2024年2月12日*
\ No newline at end of file
diff --git a/_lang/ja/_help/help_articles/segments.md b/_lang/ja/_help/help_articles/segments.md
index d865e454190..883a26d7739 100644
--- a/_lang/ja/_help/help_articles/segments.md
+++ b/_lang/ja/_help/help_articles/segments.md
@@ -2,28 +2,28 @@
 page_order: 6
 nav_title: セグメント
 layout: dev_guide
-guide_top_header: "セグメント ヘルプ記事"
-guide_top_text: "セグメンテーションロジックとフィルタリングの問題を明確にするための、いくつかの迅速で有益な記事があります。<br><br> セグメンテーションやBrazeキャンペーンまたはCanvasでの使用方法の詳細については、<a href='/docs/user_guide/engagement_tools/segments'>セグメント</a>セクションをご覧ください。"
+guide_top_header: "セグメントのヘルプ記事"
+guide_top_text: "セグメンテーションロジックとフィルタリングの問題を明確にするための簡潔で有益に記事をいくつかご紹介します。<br><br> Braze キャンペーンまたはキャンバスにおけるセグメンテーションの使用方法の詳細については、「<a href='/docs/user_guide/engagement_tools/segments'>セグメント</a>」セクションをご覧ください。"
 
 page_type: landing
-description: "このランディングページは、セグメントに関する一般的な問題に関するヘルプ記事のホームです。"
+description: "このランディングページには、セグメントに関する一般的な問題についてのヘルプ記事が含まれています。"
 tool: Segments
 noindex: true
 guide_menu_title: ""
 guide_menu_list:
-  - name: フィルターオプションが変更されました
+  - name: フィルターオプションの変更
     link: /docs/help/help_articles/segments/my_filter_options_have_changed/
     image: /assets/img/braze_icons/flag-02.svg
-  - name: セグメントにユーザーがいません
+  - name: セグメントのユーザー数が少ない
     link: /docs/help/help_articles/segments/segment_showing_0_users/
     image: /assets/img/braze_icons/users-01.svg
-  - name: セグメンテーション ロジック
+  - name: セグメンテーションロジック
     link: /docs/help/help_articles/segments/segmentation_logic_with_and_or/
     image: /assets/img/braze_icons/columns-01.svg
-  - name: 正確なテキストを検索
+  - name: 正確なテキストを検索する
     link: /docs/help/help_articles/segments/search_exact_text/
     image: /assets/img/braze_icons/search-refraction.svg
-  - name: 大きなセグメントのエクスポート
+  - name: 大きなセグメントをエクスポートする
     link: /docs/help/help_articles/segments/exporting_large_segments/
     image: /assets/img/braze_icons/file-download-01.svg
 
diff --git a/_lang/ja/_help/help_articles/segments/exporting_large_segments.md b/_lang/ja/_help/help_articles/segments/exporting_large_segments.md
index 1c4ba5e5fa6..620a5363819 100644
--- a/_lang/ja/_help/help_articles/segments/exporting_large_segments.md
+++ b/_lang/ja/_help/help_articles/segments/exporting_large_segments.md
@@ -1,25 +1,25 @@
 ---
-nav_title: 大規模セグメントのエクスポート
-article_title: 大規模セグメントのエクスポート
+nav_title: 大きなセグメントをエクスポートする
+article_title: 大きなセグメントをエクスポートする
 page_order: 4
 
 page_type: solution
-description: "このヘルプ記事では、大規模なユーザー Segmentのエクスポート方法について説明します。"
+description: "このヘルプ記事では、大きなユーザーセグメントのエクスポート方法について説明します。"
 tool: Segments
 ---
 
-# ラージSegmentのエクスポート
+# 大きなセグメントをエクスポートする
 
-大きなユーザー Segmentをエクスポートするには、いくつかの方法があります。Segment s に500,000 ユーザー s 以上が含まれている場合、この大きなSegmentを小さなSegments に分解して、これらのユーザーs をキャプチャし、それぞれの小さなSegments をBraze ダッシュボードからエクスポートできます。 
+大きなユーザーセグメントをエクスポートするには、いくつかの方法があります。含まれるユーザー数が500,000を超える大きなセグメントについては、小さなセグメントに分割してこれらのユーザーをキャプチャし、小さなセグメントをそれぞれ Braze ダッシュボードからエクスポートできます。 
 
-また、[乱数バケット番号]({{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/ab_testing_with_random_buckets/#step-1-segment-your-users-by-the-random-bucket-attribute)を使用してユーザー群を複数のSegments に分割し、エクスポート後に組み合わせることもできます。たとえば、Segmentを2 つのSegments に分割する必要がある場合は、次のフィルターs を使用して分割できます。
-- セグメント1:ランダムバケット番号が5000 未満(0 ～4999 を含む)
-- セグメント2:ランダムバケット番号が4999 を超えています(5000 ～ 9999 を含む)
+また、[ランダムバケット番号]({{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/ab_testing_with_random_buckets/#step-1-segment-your-users-by-the-random-bucket-attribute)を使用してユーザー群を複数のセグメントに分割し、エクスポート後に組み合わせることもできます。例えば、セグメントを2つの異なるセグメントに分割する必要がある場合は、次のフィルターを使用できます。
+- セグメント1: ランダムバケット番号が5000未満 (0 ～ 4999を含む)
+- セグメント2: ランダムバケット番号が5000以上 (5000 ～ 9999を含む)
 
-また、次のエンドポイントs を利用して、指定したSegmentのユーザーデータをエクスポートすることもできます。なお、これらのエンドポイントsはデータリミットの対象となります。
+また、次のエンドポイントを利用して、特定のセグメントのユーザーデータをエクスポートすることもできます。これらのエンドポイントはデータ制限の対象となるのでご注意ください。
 - [`/users/export/segment`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/)
 - [`/users/export/global_control_group`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_global_control_group/)
 
-それでも助けが必要ですか?[サポートチケット]({{site.baseurl}}/braze_support/)を開きます。
+サポートが必要な場合は、[サポートチケット]({{site.baseurl}}/braze_support/)を登録してください。
 
-_2022更新10月24日昨日d_
+_最終更新日2022年10月24日_
diff --git a/_lang/ja/_help/help_articles/segments/my_filter_options_have_changed.md b/_lang/ja/_help/help_articles/segments/my_filter_options_have_changed.md
index b38fd5bfdeb..52b93aac841 100644
--- a/_lang/ja/_help/help_articles/segments/my_filter_options_have_changed.md
+++ b/_lang/ja/_help/help_articles/segments/my_filter_options_have_changed.md
@@ -4,11 +4,11 @@ article_title: フィルターオプションが変更された
 page_order: 0
 
 page_type: solution
-description: "このヘルプでは、カスタム属性のフィルター・オプションが変更された場合の意味について説明する。"
+description: "このヘルプ記事では、カスタム属性のフィルター方法が変更された場合の意味について説明します。"
 tool: Segments
 ---
 
-# フィルター・オプションが変更された
+# フィルタオプションの変更
 
 フィルターオプションは、カスタム属性にBrazeに渡すフォーマット（データ型）に関連している。Brazeがカスタム属性用に認識しているデータ型を確認するには、「**データ設定**」>「**カスタム属性**」に移動する。
 
@@ -16,11 +16,11 @@ tool: Segments
 [古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**カスタム属性**] は \[**設定の管理**] の下にあります。
 {% endalert %}
 
-フィルターオプションが変更された場合は、データが以前とは異なるフォーマット（データ型）でBrazeに渡されていることを示している。さまざまなデータタイプとそのフィルタリングオプションの詳細については、[カスタム属性データタイプを][36]参照のこと。
+フィルターオプションが変更された場合は、データが以前とは異なるフォーマット（データ型）でBrazeに渡されていることを示している。各種データ型とそのフィルター設定オプションの詳細については、[カスタム属性データ型][36]を参照してください。
 
 ダッシュボードでカスタム属性のデータタイプを変更すると、異なるフォーマットでBrazeに送信されたデータは拒否されることに留意してほしい。
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2021年5月5日_
 
diff --git a/_lang/ja/_help/help_articles/segments/search_exact_text.md b/_lang/ja/_help/help_articles/segments/search_exact_text.md
index 0f8897e3ae7..7f57b7cd466 100644
--- a/_lang/ja/_help/help_articles/segments/search_exact_text.md
+++ b/_lang/ja/_help/help_articles/segments/search_exact_text.md
@@ -4,7 +4,7 @@ article_title: 検索フィールドで正確なテキストを検索する
 page_order: 5
 
 page_type: solution
-description: "このヘルプでは、Brazeの検索フィールドで正確なテキストを検索する方法について説明する。"
+description: "このヘルプでは、Braze の検索フィールドで正確なテキストを検索する方法について説明します。"
 tool: Segments
 ---
 
@@ -12,6 +12,6 @@ tool: Segments
 
 Brazeは検索語を含むすべての検索結果を返すので、特定のアイテムを検索すると、検索結果が多すぎることがある。
 
-正確なテキストを検索するには、検索を角括弧で囲む`[ ]`.
+正確なテキストを検索するには、角かっこ `[ ]` で検索語句を囲みます。
 
 例えば、**セグメント**ページで「`[Purchase]` 」を検索すると、「購入」という単語が含まれるセグメントは表示されるが、「購入者」や「購入」は表示されない。
\ No newline at end of file
diff --git a/_lang/ja/_help/help_articles/segments/segment_showing_0_users.md b/_lang/ja/_help/help_articles/segments/segment_showing_0_users.md
index ce63e492431..fcd6dfc6171 100644
--- a/_lang/ja/_help/help_articles/segments/segment_showing_0_users.md
+++ b/_lang/ja/_help/help_articles/segments/segment_showing_0_users.md
@@ -1,40 +1,40 @@
 ---
-nav_title: セグメント内の欠落ユーザー
-article_title: セグメント内の欠落ユーザー
+nav_title: セグメントのユーザー数が少ない
+article_title: セグメントのユーザー数が少ない
 page_order: 1
 
 page_type: solution
-description: "このヘルプ記事では、セグメントに表示されるユーザーがゼロであるにもかかわらず、さらに多くのユーザーが表示されることが予想される場合のトラブルシューティング手順を説明する。"
+description: "このヘルプ記事では、セグメントのユーザ数がゼロと表示されるものの、より多くのユーザーが表示されることが予想される場合のトラブルシューティングステップを説明します。"
 tool: Segments
 ---
 
-# セグメント内の欠落ユーザー
+# セグメントのユーザー数が少ない
 
-`0` 、それ以上のユーザーを見込んでいる場合、2つの解決策が考えられる：
-* [正確な統計量を計算する](#calculate-exact-statistics)
-* [データ転送を確認する](#verify-data-transfer)
+表示されるユーザー数が `0` であるものの、より多くのユーザーを予測していた場合、次の2つの解決策が考えられます。
+* [正確な統計を計算する](#calculate-exact-statistics)
+* [データ転送を検証する](#verify-data-transfer)
 
-## 正確な統計量を計算する
+## 正確な統計を計算する
 
-セグメント統計は推定値を示している可能性がある。推定値は、無作為標本に基づいて算出され、その結果が`+/- 1%` 以内であるという95％の信頼区間がある。ユーザーベースが小さければ小さいほど、セグメントのサイズは概算である可能性が高くなる。**セグメントの詳細**パネルで**正確な統計を計算を**クリックする。これにより、セグメント内の正確なユーザー数が計算される。
+セグメント統計は推定値を示している可能性があります。推定値はランダムなサンプルに基づいて計算され、95% の信頼区間で結果が `+/- 1%` に含まれることを意味します。ユーザー群が小さいほど、セグメントのサイズは推定である可能性が高くなります。**\[セグメントの詳細]** パネルで **\[正確な統計を計算]** をクリックします。これにより、セグメントの正確なユーザー数が計算されます。
 
-![正確な統計を計算するオプションを表示するセグメントの詳細パネル][28]
+![\[正確な統計を計算] オプションが表示される \[セグメントの詳細] パネル][28]
 
 ## データ転送を確認する
 
-フィルタリングしているデータがBrazeに送信されていない可能性がある。どのカスタムイベントがBrazeに送信されているかを確認するには、[カスタムイベントレポートを][1]参照する。
+フィルタリングしているデータが Braze に送信されていない可能性があります。Braze に送信されているカスタムイベントを確認するには、[カスタムイベントレポート][1]を参照してください。
 
-カスタムイベントを特定の日付とアプリとともに選択し、Brazeに実際に転送されているデータを確認する。`0` データがBrazeに送信されていることに気づいたら、次のステップは、Brazeにどのようにイベントを送信しているかを評価することである。
+カスタムイベントを特定の日付およびアプリとともに選択して、Braze に実際に転送されているデータを確認します。`0` データが Braze に送信されていることを確認したら、次のステップでは Braze へのイベントの送信方法を評価します。
 
-![カスタムイベントのカウントをゼロとして表示するグラフ][29]
+![カスタムイベント数がゼロと表示されるグラフ][29]
 
 {% alert important %}
-Brazeダッシュボードに表示されるデータは、Brazeに送信しているものと同じ構文でない場合がある。この2つが正確に一致していることを確認する。
+Braze ダッシュボードに表示されるデータと、Braze に送信しているデータの構文が同じでない可能性があります。これら 2 つが正確に一致していることを確認してください。
 {% endalert %}
 
-まだ助けが必要か？[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+サポートが必要な場合は、[サポートチケット]({{site.baseurl}}/braze_support/)を登録してください。
 
-_最終更新日：2021年1月5日_
+_最終更新日: 2021年1月5日_
 
 [1]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-analytics
 [28]: {% image_buster /assets/img_archive/trouble8.png %}
diff --git a/_lang/ja/_help/help_articles/segments/segmentation_logic_with_and_or.md b/_lang/ja/_help/help_articles/segments/segmentation_logic_with_and_or.md
index db672fbc3ae..b8865d29d7c 100644
--- a/_lang/ja/_help/help_articles/segments/segmentation_logic_with_and_or.md
+++ b/_lang/ja/_help/help_articles/segments/segmentation_logic_with_and_or.md
@@ -14,7 +14,7 @@ tool: Segments
 
 ## ANDおよびOR演算子の理解
 
-`AND`と`OR`の演算子は異なる方法で機能します。セグメント化する際に達成したいことに応じて、各オペレーターを使用できます。 
+`AND`と`OR`の演算子は異なる方法で機能します。オーディエンスをSegmentするときの目的に応じて、それぞれの演算子を使用できます。 
 
 ### AND演算子を使用するタイミング
 
@@ -26,17 +26,17 @@ tool: Segments
 
 `OR` を使用して、条件のセットの中で少なくとも1つの条件を満たすユーザーをターゲットにすることが目的の場合。3つの条件が`OR`で結びついている場合、実際の文が真であるためには、1つ、2つ、またはすべての条件が真である可能性があります。
 
-例えば、バージョン1.0または1.1のアプリを使用しているすべてのユーザーにメッセージを送信したいと想像してください。ユーザーがバージョン1.0およびバージョン1.1にいる場合、それらをターゲットにするために、フィルター`Is 1.0`および`Is 1.1`を`OR`オペレーターと共にSegmentで使用できます。これにより、バージョン1.0または1.1を使用しているすべてのユーザーが対象になります。
+例えば、バージョン1.0または1.1のアプリを使用しているすべてのユーザーにメッセージを送信したいと想像してください。バージョン1.0およびバージョン1.1のユーザーをターゲットにするには、セグメントでフィルター `Is 1.0` および `Is 1.1` を`OR` 演算子とともに使用できます。これにより、バージョン1.0または1.1を使用しているすべてのユーザーが対象になります。
 
-次の例では、米国とカナダの両方のユーザーに有効なプロモーションを考えてみましょう。プロモーションが有効な地域のユーザーのみがプロモーションを受け取るようにしたい。このシナリオでは、次の文を使用してキャンペーンをターゲットにします: `Country is United States OR Country is Canada`。`OR` 演算子を使用すると、キャンペーンはカナダまたはアメリカ合衆国のユーザーにのみ配信されます。
+次の例では、米国とカナダの両方のユーザーに有効なプロモーションを考えてみましょう。プロモーションが有効な地域のユーザーのみがプロモーションを受け取るようにします。このシナリオでは、次の文を使用してキャンペーンをターゲットにします: `Country is United States OR Country is Canada`。`OR` 演算子を使用すると、国がカナダまたは米国のユーザーにのみキャンペーンが送られます。
 
 #### OR演算子を避けるべき場合
 
-ユーザーをターゲットにする状況では、`OR`演算子の使用を避けるべき場合があります。`OR` 演算子は、ユーザーがステートメント内の1つ以上のフィルターの基準を満たす場合にtrueと評価されるステートメントを作成します。例えば、「フーディーズ」に属するが、「非フーディーズ」または「キャンディー愛好家」のいずれにも属さないユーザーのセグメントを作成したい場合、`OR`演算子を使用するとここで機能します。
+ユーザーをターゲットにする状況では、`OR`演算子の使用を避けるべき場合があります。`OR` 演算子は、ユーザーがステートメント内の1つ以上のフィルターの基準を満たす場合にtrueと評価されるステートメントを作成します。たとえば、"foodies"に属するが、"non-foodies"または"candy-lovers"のいずれにも属さないユーザーのSegmentを作成する場合は、`OR`演算子を使用します。
 
 ![][1]
 
-ただし、あなたの目標が「フーディーズ」セグメントに属し、「非フーディーズ」および「キャンディ愛好家」セグメントのいずれにも属さないユーザーをセグメント化することである場合は、`AND` 演算子を使用してください。このようにして、キャンペーンまたはキャンバスを受け取るユーザーは、意図されたセグメント（「フーディーズ」）に属し、同時に他のセグメント（「非フーディーズ」および「キャンディー愛好家」）には属しません。 
+ただし、「foodies」セグメントに属し、「non-foodies」および「candy-lovers」セグメントのいずれにも属さないユーザーをセグメント化することが目的の場合は、`AND` 演算子を使用します。このようにして、キャンペーンまたはキャンバスを受け取るユーザーは、意図されたセグメント（「フーディーズ」）に属し、同時に他のセグメント（「非フーディーズ」および「キャンディー愛好家」）には属しません。 
 
 次の否定的なターゲティング基準は、2つ以上のフィルターが同じ属性を参照している場合、`OR`演算子と一緒に使用しないでください:
 
@@ -48,13 +48,13 @@ tool: Segments
 
 ### 両方の演算子を使用する
 
-次の例では、`AND`と`OR`の両方の演算子を使用します。ここでのターゲットオーディエンスには、ナイキのスニーカーやアディダスのスニーカーを購入し、メール通知を受け取ることに同意したユーザーが含まれます。
+次の例では、`AND`と`OR`の両方の演算子を使用します。ここで、ターゲットオーディエンスには、Nike スニーカーまたは Adidas スニーカーを購入し、メール通知を受信するためにオプトインしたユーザーが含まれます。
 
-![スニーカーショッパーのためのSegmentを作成するには、ユーザーのお気に入りブランドがNikeまたはAdidasであり、メールにオプトインしている必要があります][33]
+![ユーザーの好きなブランドが Nike か Adidas で、メールにオプトインしているスニーカー購入者のセグメントを構築する][33]
 
-もう一つの方法は、セグメントを作成し、フィルターに基づいてそれに該当するユーザー][35]をプレビューすることです。この方法を使用すると、属性、アプリバージョン、またはその他のセグメンテーションが表示されている内容と一致していることを確認できます。
+正しいロジックを構築する別の方法は、Segmentを作成し、フィルターs に基づいてそれに分類される\[ユーザーs][35] をプレビューする] ことです。この方法を使用すると、属性、アプリバージョン、またはその他のセグメンテーションが表示されている内容と一致していることを確認できます。
 
-まだ助けが必要ですか？[サポートチケット]({{site.baseurl}}/braze_support/)を開封する。
+それでもサポートが必要な場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)を登録してください。
 
 _最終更新日：2022年6月3日_
 
diff --git a/_lang/ja/_help/home.md b/_lang/ja/_help/home.md
index 0e404c27922..951607f58db 100644
--- a/_lang/ja/_help/home.md
+++ b/_lang/ja/_help/home.md
@@ -19,13 +19,13 @@ resources_list:
   - name: リリースノート
     link: /docs/help/release_notes/most_recent/
     image: /assets/img/braze_icons/sticker-square.svg
-  - name: ログイン
+  - name: Braze ラーニングログイン
     link: https://learning.braze.com/
     image: /assets/img/braze_icons/user-square.svg
   - name: メディア・リソース
     link: https://www.youtube.com/channel/UCEXVTEWeAHx1OlddOMRTaOg
     image: /assets/img/braze_icons/youtube.svg
-  - name: ブレイズ・サポート
+  - name: Braze支援
     link: /docs/braze_support/
     image: /assets/img/braze_icons/mail-01.svg
 
@@ -34,9 +34,9 @@ popular_topic_list:
     link: /docs/help/help_articles/campaigns_and_canvas/know_before_send/
   - name: プッシュトークンの移行
     link: /docs/help/help_articles/push/push_token_migration/
-  - name: カスタムイベント・プロパティを記録する
+  - name: カスタムイベントプロパティのロギング
     link: /docs/help/help_articles/campaigns_and_canvas/using_custom_event_properties/
-  - name: 派遣ID
+  - name: ディスパッチ ID
     link: /docs/help/help_articles/data/dispatch_id/
   - name: メールバウンス
     link: /docs/help/help_articles/email/email_bounces/
diff --git a/_lang/ja/_help/release_notes.md b/_lang/ja/_help/release_notes.md
index 2a855054b86..4863f4b41ea 100644
--- a/_lang/ja/_help/release_notes.md
+++ b/_lang/ja/_help/release_notes.md
@@ -49,7 +49,7 @@ guide_featured_list:
 
 # 最新のBrazeリリースノート {#most-recent}
 
-> Brazeは、メジャー・プロダクト・リリースに合わせて、製品のアップデート情報を毎月リリースしているが、週ごとに雑多な改良が加えられている。
+> Brazeは、主要な製品リリースに合わせて、月ごとに製品更新の情報を公開しています。ただし、製品は、週ごとにさまざまな改良が加えられて更新です。
 > <br>
 > <br>
 > このセクションに記載されているアップデートの詳細については、アカウント・マネージャーに問い合わせるか、[サポート・チケットを発行する]({{site.baseurl}}/help/support/)。また、[SDK Changelogsで]({{site.baseurl}}/developer_guide/platform_integration_guides/sdk_changelogs/)、毎月のSDKのリリース、アップデート、改良に関する詳細情報を確認することができる。
@@ -58,13 +58,13 @@ guide_featured_list:
 
 ### Braze Docsのアップデート
 
-#### ディアタクシーとブレイズ・ドックス
+#### Diátaxis と Braze Docs
 
-我々は、[Diátaxisと](https://diataxis.fr/)呼ばれるフレームワークを使ってドキュメンテーションの標準化を進めているところだ。ライターやコントリビューターがこの新しいフレームワークに合ったコンテンツを作成できるよう、[各コンテンツタイプのテンプレートを作成]({{site.baseurl}}/contributing/content_types)した。
+私たちは、[Diátaxis](https://diataxis.fr/)と呼ばれる枠組みを使ってドキュメントを標準化しています。ライターやコントリビューターがこの新しいフレームワークに合ったコンテンツを作成できるよう、[各コンテンツタイプのテンプレートを作成]({{site.baseurl}}/contributing/content_types)した。
 
-#### Braze Docs用の新しいプル・リクエスト・テンプレート
+#### Braze Docs の新しいプルリクエストテンプレート
 
-私たちは、[Braze Docsに貢献する]({{site.baseurl}}/contributing/home/)のがより簡単で混乱しないように、プルリクエスト（PR）テンプレートを改善するために時間をかけた。それでもまだ改善の余地があると思うなら、PRを開設するか、[問題を提出する](https://github.com/braze-inc/braze-docs/issues/new?assignees=&labels=enhancement&projects=&template=request_a_feature.md&title=)こと。簡単なことなら何でもいい！
+私たちは、[Braze Docsに貢献する]({{site.baseurl}}/contributing/home/)のがより簡単で混乱しないように、プルリクエスト（PR）テンプレートを改善するために時間をかけた。まだ改善の余地があると思われる場合は、PR を開封するか、[問題を送信](https://github.com/braze-inc/braze-docs/issues/new?assignees=&labels=enhancement&projects=&template=request_a_feature.md&title=)してください。すべてが簡単になります。
  
 ### データの柔軟性
 
@@ -72,61 +72,61 @@ guide_featured_list:
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-を通じてエクスポートする。 [`/custom_attributes`]({{site.baseurl}}/api/endpoints/export/custom_attributes/get_custom_attributes)と [`/events`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events_data)APIエンドポイントは早期アクセスではなくなった。
+[`/custom_attributes`]({{site.baseurl}}/api/endpoints/export/custom_attributes/get_custom_attributes) および[`/events`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events_data) API エンドポイントs によるエクスポートは、初期アクセスではなくなりました。
 
-#### カレントの新しいユーザー権限
+#### ユーザーの新しい Currents 権限
 
-ユーザーに対する新しい権限設定が2つある：**百花繚乱の****積分を表示**し、**百花繚乱の積分を編集**する。ユーザー権限の詳細については[、こちらを]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions)参照のこと。 
+ユーザーには2つの新しい権限設定があります。\[**Currents 統合を表示する**] と \[**Currents 統合を編集する**] です。ユーザー権限の詳細については[、こちらを]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions)参照のこと。 
 
-#### Snowflakeデータ保持ポリシーの更新
+#### Snowflake データリテンションポリシーの更新
  
-8月27日より、2年以上前のすべてのスノーフレーク・セキュア・データ・シェアリング・イベントのデータから、個人を特定できる情報（PII）が削除される。Snowflakeを使用している場合、保持ポリシーが適用される前に、Snowflakeアカウントにコピーを保存することで、環境内の完全なイベントデータを保持することを選択することができる。詳しくは、[Snowflakeのデータ保持を]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention/)参照のこと。
+8月27日より、個人を特定できる情報 (PII) は、作成から2年を超えたすべての Snowflake Secure Data Sharing イベントデータから削除されます。Snowflake を使用する場合、完全なイベントデータを環境に保持するには、リテンションポリシーが適用される前に Snowflake アカウントにコピーを保存します。詳細については、[Snowflakeデータリテンション]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention/)を参照してください。
  
-### 創造性を解き放つ
+### 創造性を引き出す
 
 #### 複数ページのアプリ内メッセージ
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-アプリ内メッセージにページを追加することで、オンボーディングフローやウェルカムジャーニーのような連続したフローでユーザーを誘導することができる。詳しくは、[ドラッグ＆ドロップでアプリ内メッセージを作成するを]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create#multi-page)参照のこと。
+アプリ内メッセージにページを追加することで、オンボーディングフローやウェルカムジャーニーのような連続したフローでユーザーを誘導することができる。詳細については、[ドラッグアンドドロップによるアプリ内メッセージの作成]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create#multi-page)を参照してください。
 
-#### リンク短縮とリキッド
+#### Liquid でのリンク短縮
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[Liquidを使ってURLをパーソナライズ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#enabling-link-shortening)し、SMSメッセージに含まれるURLを自動的に短縮し、クリックスルー率分析を収集する。試すには、[リンク・ショートニングを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/)参照のこと。
+[Liquidを使ってURLをパーソナライズ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#enabling-link-shortening)し、SMSメッセージに含まれるURLを自動的に短縮し、クリックスルー率分析を収集する。試してみるには、[リンク短縮]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/)を参照してください。
 
 #### カタログのAPI例
 
 配列フィールドを使った`/catalogs` エンドポイントの例を追加した。例を見るには、以下をチェックしてほしい：
 
-- [複数のカタログ項目を編集する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk)
-- [複数のカタログ項目を作成する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk)
-- [カタログ項目を更新する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items)
-- [カタログ項目を編集する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item)
-- [カタログ項目を作成する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item)
-- [カタログ項目を更新する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item)
-- [カタログを作成する]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog)
+- [複数のカタログ項目を編集]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk)
+- [複数のカタログ項目を作成]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk)
+- [カタログアイテムを更新]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items)
+- [カタログアイテムを編集]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item)
+- [カタログアイテムを作成]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item)
+- [カタログアイテムを更新]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item)
+- [カタログを作成]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog)
  
-### ロバスト・チャンネル
+### 強力なチャネル
 
 ### 複数のWhatsAppビジネスアカウント
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-各ワークスペースに複数のWhatsApp Businessアカウントとサブスクリプショングループ（および電話番号）を追加できるようになった。詳しくは[WhatsApp Businessアカウントを]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups)ご覧下さい。 
+各ワークスペースに複数のWhatsApp Businessアカウントとサブスクリプショングループ（および電話番号）を追加できるようになった。詳しくは、[複数のWhatsApp取引先]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups)を参照してください。 
 
-#### SMSの地理的許可
+#### SMSの地理的権限
 
 SMS Geographic Permissionsは、SMSメッセージを送信できる国をコントロールすることで、セキュリティを強化し、不正なSMSトラフィックから保護する。SMSメッセージが承認された地域にのみ送信されるように、国の許可リストを指定する方法については、[SMS国の許可リストを設定するを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_geographic_permissions/#configuring-your-sms-country-allowlist)参照のこと。
 
-#### LINEとブレイズ
+#### LINE と Braze
 
 {% multi_lang_include release_type.md release="ベータ" %}
 
-[LINEは](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf)日本で最も人気のあるメッセージングアプリで、月間アクティブユーザー数は9500万人を超える。LINEアカウントとBrazeを統合することで、ゼロおよびファーストパーティの顧客データを活用し、顧客の嗜好、行動、クロスチャネルでのインタラクションに基づいて、適切な顧客に魅力的なLINEメッセージを送ることができる。まずは[LINEを]({{site.baseurl}}/line)ご覧いただきたい。
+[LINE](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf) は、月間アクティブユーザー数が9500万 を超える国内で最も人気のあるメッセージング アプリです。LINE アカウントを Braze と統合することで、ゼロパーティおよびファーストパーティの顧客データを活用し、顧客の嗜好、行動、クロスチャネルのインタラクションに基づいて、適切な顧客に魅力的な LINE メッセージを送信できます。開始するには、[LINE]({{site.baseurl}}/line) を参照してください。
 
-#### Shopifyである：値下げと再入荷
+#### Shopify:値下げ、再入荷商品
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
@@ -137,33 +137,33 @@ Shopifyでは、[値下げや]({{site.baseurl}}/user_guide/personalization_and_d
  
 #### 重複ユーザーのルールベースのマージ
 
-以前は、Brazeで重複ユーザーを個別または一括で検索し、マージすることができた。重複の解決方法を制御するルールを作成し、最も関連性の高いユーザーを残すことができる。詳しくは、[ルールベースのマージを]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users/#rules-based-merging)参照のこと。
+以前は、Braze で重複するユーザーを個別または一括で検索してマージすることができました。これで、重複がどのように解決されるかをコントロールするためのルールを作成できるようになりました。そのため、最も関連性の高いユーザーが保持されます。詳細については、[ルールベースのマージ]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users/#rules-based-merging)を参照してください。
 
 #### AI Liquidアシスタント
 
 {% multi_lang_include release_type.md release="ベータ" %}
 
-Sage AI Liquid AssistantはSage AIを搭載したチャットアシスタントで、メッセージ内容をパーソナライズするために必要なLiquidの生成をサポートする。テンプレートからリキッドを生成し、パーソナライズされたリキッドの提案を受け、セージAIのサポートで既存のリキッドを最適化することができる。AIリキッド・アシスタントは、使用されているリキッドを説明する注釈も提供するので、リキッドへの理解を深め、自分で書けるようになる。
+Sage AI Liquid アシスタントは Sage AI を搭載したチャットアシスタントであり、メッセージコンテンツをパーソナライズするために必要な Liquid を生成する場合に役立ちます。テンプレートからの Liquid の生成、パーソナライズされた Liquid の提案の受け取り、および Sage AI のサポートを使用した既存の Liquid の最適化を実行できます。AI Liquid アシスタントには、使用されている Liquid を説明する注釈も用意されているため、Liquid の理解を深めたり、自作方法を学んだりできます。
 
-まずは、[AIリキッド・アシスタントを]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_liquid)参照のこと。
+開始するには、「[AI Liquid アシスタント]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_liquid)」を参照してください。
  
 ### SDK
  
 #### Android SDKのログ
 
-[Braze Android SDKのロギングドキュメントを]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/additional_customization_and_configuration/#logging)見直し、読みやすく、アプリで使いやすくした。また、各ログレベルの説明も追加した。
+Braze Android SDKの[ログ記録文書を見直したので、あなたのアプリで読みやすく、使いやすいです。また、各ログレベルの説明も追加した。
 
-#### iOS SDKのフォアグラウンド・プッシュ通知
+#### iOS SDKのフォアグラウンドプッシュ通知s
 
-Braze iOS SDKの`subscribeToUpdates` メソッドが、フォアグラウンドプッシュ通知を受信したかどうかを検出できるようになった。詳しくは、[iOSプッシュ通知統合を]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration)参照のこと。
+Braze iOS SDKの `subscribeToUpdates` メソッドで、フォアグラウンドプッシュ通知を受信したかどうかを検出できるようになりました。詳しくは、[iOS プッシュ通知統合]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration)を参照してください。
  
 #### Xamarinのドキュメントを更新する
  
-[バージョン4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/releases/tag/4.0.0)以降、Braze Xamarin SDKはSwift SDKバインディングを使用しているため、コードスニペットと参考資料を更新した。また、読みやすく、理解しやすいようにセクションを再構成した。確認するには、[Xamarinのドキュメントを]({{site.baseurl}}/developer_guide/platform_integration_guides/xamarin/initial_sdk_setup)参照のこと。
+[バージョン4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/releases/tag/4.0.0)以降、Braze Xamarin SDK で Swift SDK バインディングが使用されるため、コードスニペットと参考資料が更新されました。また、読みやすく、理解しやすいようにセクションを再構成した。確認するには、[Xamarin ドキュメント]({{site.baseurl}}/developer_guide/platform_integration_guides/xamarin/initial_sdk_setup)を参照してください。
 
 #### SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
  
 - [Swift SDK 9.3.1](https://github.com/braze-inc/braze-swift-sdk/releases/tag/9.3.1)
 - [Web SDK 5.3.2](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#532)
@@ -184,37 +184,37 @@ Braze Docsが日本語に対応した！
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[`/campaigns/trigger/send` エンド]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns)ポイントが添付ファイルをサポートするようになった（ちょうど`/messages/send` エンドポイントが電子メールの添付ファイルをサポートするように）。 
+[`/campaigns/trigger/send` エンドポイント]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns)で添付ファイルがサポートされるようになりました (`/messages/send` エンドポイントでメールの添付ファイルがサポートされるのと同様)。 
 
 #### データウェアハウスの追加サポート
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-Brazeの[Cloud Data Ingestion（CDI]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/connected_sources)）は、BigQuery、Databricks、Redshift、Snowflakeをサポートするようになった。
+Braze [クラウドデータ取り込み (CDI)]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/connected_sources) で、BigQuery、Databricks、Redshift、Snowflake がサポートされるようになりました。
 
 #### WhatsAppの電話番号移行
 
-WhatsAppビジネスアカウント間でWhatsApp電話番号を移行する。[WhatsAppの電話番号移行について]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration)もっと読む。
+Meta の埋め込みサインアップを使用して、WhatsApp Business アカウント間で WhatsApp の電話番号を移行します。[WhatsApp電話番号マイグレーション]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration)について詳しくお読みください。
  
-### 創造性を解き放つ
+### 創造性を引き出す
 
 #### デバイス別エンゲージメント
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-新レポート「**Engagement by Device**」は、ユーザーがどのデバイスを使ってメールに参加しているのかがわかる。このデータは、モバイル、デスクトップ、タブレット、その他のデバイスの種類を問わず、Eメールのエンゲージメントを追跡する。[レポートとEメールパフォーマンスダッシュボードの]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard)詳細はこちら。
+新レポート「**Engagement by Device**」は、ユーザーがどのデバイスを使ってメールに参加しているのかがわかる。このデータは、モバイル、デスクトップ、タブレット、および他のデバイスタイプのメールエンゲージメントを追跡します。[レポートと電子メールパフォーマンスダッシュボード]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard) について詳しく説明します。
 
 #### キャンバスフローのWhatsAppとSMSリキッドプロパティ
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[キャンバスフローにWhatsAppとSMSリキッドプロパティの]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties)サポートを追加した。アクションパスのステップが "Sent an SMS Inbound Message "または "Sent a WhatsApp Inbound Message "トリガーを含むとき、後続のキャンバスステップはSMSまたはWhatsApp Liquidプロパティを含むことができる。これは、Canvas Flowにおけるイベントプロパティの動作を反映している。こうすることで、メッセージを活用して、ユーザープロファイルや会話メッセージに関するファーストパーティデータを保存し、参照することができる。
+[WhatsAppおよびSMS Liquidプロパティーのサポートがキャンバスフロー]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties)に追加されました。アクションパスステップに \[SMS インバウンドメッセージを送信しました] または \[WhatsApp インバウンドメッセージを送信しました] トリガーが含まれている場合、後続のキャンバスステップに SMS または WhatsApp Liquid プロパティを含めることができるようになりました。これは、キャンバスフローでのイベントプロパティの動作を反映したものです。こうすることで、メッセージを活用して、ユーザープロファイルや会話メッセージに関するファーストパーティデータを保存し、参照することができる。
  
-#### キャンバスに描かれたパーソナライズされた道
+#### 繰り返されるキャンバスのパーソナライズされたパス
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-キャンバスのパーソナライズドパスでは、コンバージョンの可能性に基づいて、個々のユーザーに対してキャンバスのジャーニーの任意のポイントをパーソナライズすることができる。キャンバスにパーソナライズされたパスが追加された。[パーソナライズド・バリアントについて]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths)もっと知る。
+キャンバスのパーソナライズドパスでは、コンバージョンの可能性に基づいて、個々のユーザーに対してキャンバスのジャーニーの任意のポイントをパーソナライズすることができる。定期的なキャンバスでパーソナライズされたパスを使用できるようになりました。詳細については、[Personalized Variants]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths)を参照してください。
 
 #### セグメントのトラブルシューティング
 
@@ -226,13 +226,13 @@ WhatsAppビジネスアカウント間でWhatsApp電話番号を移行する。[
 
 ![]({% image_buster /assets/img/liquid_color_code.png %})
  
-### ロバスト・チャンネル
+### 強力なチャネル
 
-#### SMSの地理的許可
+#### SMS 地理的許可
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-SMSの地理的許可は、あなたがSMSメッセージを送信することができる国の制御を強制することにより、セキュリティを強化し、詐欺的なSMSトラフィックから保護する。管理者は、承認された地域にのみSMSメッセージが送信されるように、国の許可リストを指定できるようになった。詳細については、[SMS地理的許可を]({{site.baseurl}}/sms_geographic_permissions)参照のこと。 
+SMSの地理的許可は、あなたがSMSメッセージを送信することができる国の制御を強制することにより、セキュリティを強化し、詐欺的なSMSトラフィックから保護する。管理者は、承認された地域にのみSMSメッセージが送信されるように、国の許可リストを指定できるようになった。詳細については、[SMS Geographic Permissions]({{site.baseurl}}/sms_geographic_permissions)を参照してください。 
 
 ![最も一般的な国が一番上に表示される "Country allowlist "ドロップダウン。]({% image_buster /assets/img/sms/allowlist_dropdown.png %}){: style="max-width:80%;"}
 
@@ -240,66 +240,66 @@ SMSの地理的許可は、あなたがSMSメッセージを送信すること
 
 オプトアウト監視やトラフィックポンプの推奨など、[Brazeを使ったSMS/MMSのベストプラクティスについて]({{site.baseurl}}/user_guide/message_building_by_channel/sms/best_practices/best_practices)詳しく知る。 
 
-#### プッシュ配信の停止を追跡する
+#### プッシュの配信停止をトラッキングする
 
 プッシュ配信の停止を追跡するためのヒントについては、新しい[ヘルプ記事を]({{site.baseurl}}/help/help_articles/push/push_unsubscribes)チェックしよう。
 
 #### Shopify`checkout.liquid` 非推奨
 
-Shopify`checkout.liquid` のサポートは2024年8月に非推奨となり、2025年8月に終了する。Braze がこの遷移 を処理する方法について詳しく説明します。[ 
+Shopify `checkout.liquid` は、2024年8月に非推奨になり、2025年8月に終了することにご注意ください。この変化に対する Braze の対応については、[こちら]({{site.baseurl}}/help/release_notes/deprecations/shopify_checkout)をご覧ください。 
 
 ### SDKのアップデート
  
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
  
 - [Swift SDK 9.3.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/9.3.0)
-    - 既存のFeature Flag APIは廃止され、将来のバージョンで削除される：
-        - `Braze.FeatureFlag.jsonStringProperty(key:)` は非推奨となった。
-        - `Braze.FeatureFlag.jsonObjectProperty(key:)` は非推奨となり、`Braze.FeatureFlag.jsonProperty(key:)` が採用された。
+    - 将来のバージョンで削除される既存のフィーチャーフラグ API を非推奨にします。
+        - `Braze.FeatureFlag.jsonStringProperty(key:)` は非推奨になりました。
+        - `Braze.FeatureFlag.jsonObjectProperty(key:)` は非推奨になり、`Braze.FeatureFlag.jsonProperty(key:)` に置き換えられした。
 - [Roku SDK 2.2.0](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md)
 - [Braze Expo プラグイン 2.1.2](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
 
 #### tvOSドキュメント
 
-数ヶ月前、[tvOSコンテンツカードと]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/tvos) [アプリ内メッセージングの]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/tvos)記事が誤って非推奨となった。これらのドキュメントは現在、Braze DocsのSwiftセクションで再公開されている。
+数か月前、[tvOS コンテンツカード]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/tvos)と[アプリ内メッセージング]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/tvos)の記事は誤って非推奨になりました。これらのドキュメントは現在、Braze DocsのSwiftセクションで再公開されている。
 
 {% alert note %}
-Braze Docsへの[投稿]({{site.baseurl}}/contributing/home)者は、このサイトが現在Ruby 3.3.0で動作していることに注意する必要がある。必要に応じてRubyのバージョンをアップグレードしてほしい。
+Braze Docs の[貢献者]({{site.baseurl}}/contributing/home)は、サイトが Ruby 3.3.0で実行されるようになったことを確認する必要があります。必要に応じてRubyのバージョンをアップグレードしてほしい。
 {% endalert %}
 
 ## 2024年5月28日リリース
 
 ### ドキュメントサイトの視覚的な更新
 
-ドキュメンテーションのウェブサイトが新しくなったことにお気づきだろうか！私たちは、新しい活気あるブレイズのブランド・アイデンティティを反映させるために、それを刷新した。新ブランドの舞台裏については、[Unveiling Our New Brandをご覧いただきたい：Braze エグゼクティブ・クリエイティブ・ディレクター グレッグ・エルデリとの対話](https://www.braze.com/resources/articles/unveiling-our-new-brand-a-conversation-with-braze-executive-creative-director-greg-erdelyi).
+ドキュメンテーションのウェブサイトが新しくなったことにお気づきだろうか！新しく生き生きとしたBrazeブランドアイデンティティを反映するように改良しました。新ブランドの舞台裏については、[Unveiling Our New Brandをご覧いただきたい：Braze クリエイティブディレクター Greg Erdelyi との会話](https://www.braze.com/resources/articles/unveiling-our-new-brand-a-conversation-with-braze-executive-creative-director-greg-erdelyi)。
 
 ### ポルトガル語とスペイン語をサポート
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-Brazeは現在、ポルトガル語とスペイン語に対応している。Brazeダッシュボードの表示言語を変更するには、[言語設定を]({{site.baseurl}}/user_guide/administrative/access_braze/language/)参照のこと。
+Brazeは現在、ポルトガル語とスペイン語に対応している。Braze ダッシュボード アプリが認識する言語を変更するには、[言語設定s]({{site.baseurl}}/user_guide/administrative/access_braze/language/)を参照してください。
 
-### ロバスト・チャンネル
+### 強力なチャネル
 
 #### 多言語設定
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[多言語設定を]({{site.baseurl}}/multi_language_support/)調整することで、異なる言語や地域のユーザーをターゲットに、1通のメールメッセージの中で異なるメッセージを送ることができる。多言語サポートを編集・管理するには、「多言語設定の管理」ユーザー権限が必要である。メッセージにロケールを追加するには、キャンペーンの編集権限が必要だ。
+[多言語設定を]({{site.baseurl}}/multi_language_support/)調整することで、異なる言語や地域のユーザーをターゲットに、1通のメールメッセージの中で異なるメッセージを送ることができる。多言語サポートを編集および管理するには、「多言語設定を管理」ユーザー権限が必要です。メッセージにロケールを追加するには、キャンペーンの編集権限が必要だ。
 
-#### メッセージレベルのワンクリックリスト配信停止ヘッダー
+#### メッセージレベルのワンクリックリスト-配信停止 ヘッダー
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-list-unsubscribeヘッダーのためのワンクリックunsubscribe[(RFC 8058](https://datatracker.ietf.org/doc/html/rfc8058))は、受信者が電子メールからオプトアウトする簡単な方法を提供する。このヘッダー設定は、メールのメッセージレベルで適用されるように調整できる。この設定の詳細については、[ワークスペースのメール配信停止ヘッダーを]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#email-unsubscribe-header-in-workspaces)参照のこと。
+list-unsubscribe ヘッダーのワンクリック配信停止 ([RFC 8058](https://datatracker.ietf.org/doc/html/rfc8058)) により、受信者がメールから簡単にオプトアウトできます。このヘッダー設定は、メールのメッセージレベルで適用されるように調整できる。この設定の詳細については、「[ワークスペースのメール配信停止ヘッダー]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#email-unsubscribe-header-in-workspaces)」を参照してください。
 
 #### 電子メールのサニタイズについて
 
 Brazeがメールメッセージ内の特定の種類のJavaScriptを検出した場合に発生する処理については、新しい[サニタイズの]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/sanitization)記事を参照。その主な目的は、悪質業者が他のBrazeダッシュボードユーザーのセッションデータにアクセスするのを防ぐことである。
 
-#### コンテンツ・ブロックの包含数
+#### コンテンツブロックの包含カウント
 
-アクティブなキャンペーンまたはキャンバスにコンテンツブロックを追加した後、コンテンツブロックにカーソルを合わせ、<i class="fa fa-eye preview-icon"></i> **プレビューアイコンを**選択すると、コンテンツブロックライブラリから[このコンテンツブロックをプレビューする]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/)ことができる。
+アクティブなキャンペーンまたはキャンバスにコンテンツブロックを追加した後、コンテンツブロックライブラリから[ このコンテンツブロック]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/) をプレビューするには、コンテンツブロックにマウスを合わせて<i class="fa fa-eye preview-icon"></i>**プレビュー** アイコンを選択します。
 
 #### キャンバスのステータス
 
@@ -313,60 +313,60 @@ Brazeのダッシュボードでは、キャンバスがステータスごとに
 
 AIコピーライティングアシスタントが生成するコピーのスタイルを、ブランドの声に合わせてカスタマイズするための[ブランドガイドラインを]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines/)作成し、適用できるようになった。シナリオごとに複数のガイドラインを設定し、常に文脈に合ったトーンになるようにする。
  
-### 新しいブレイズ・パートナーシップ
+### Braze の新しいパートナーシップ
 
-#### アディクテフ - アナリティクス
+#### Adikteev - 分析
 
-Brazeと[Adikteevの]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/adikteev/)統合により、Braze CRMキャンペーン内でAdikteevの解約予測技術を活用し、リスクの高いユーザーセグメントを優先的にターゲットにすることで、ユーザーリテンションを高めることができる。
+Braze と [Adikteev]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/adikteev/) の統合により、Braze CRM キャンペーン内で Adikteev の解約予測技術を活用し、リスクの高いユーザーセグメントを優先的にターゲットにすることで、ユーザーリテンションを高めることができます。
  
-#### セレブラス - 分析
+#### Celebrus - 分析
  
-Brazeと[Celebrusの]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/celebrus)統合は、WebとモバイルアプリのチャネルでBraze SDKとシームレスに統合され、チャネルの活動データをBrazeに取り込むことを容易にする。これには、特定期間におけるデジタル資産全体のビジター・トラフィックに関する包括的な洞察も含まれる。
+Braze と [Celebrus]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/celebrus) の統合により、Web アプリチャネルとモバイルアプリチャネルで Braze SDK とシームレスに統合され、チャネルアクティビティデータを Braze に取り込みやすくなります。これには、特定期間におけるデジタル資産全体のビジター・トラフィックに関する包括的な洞察も含まれる。
  
 #### IAM Studio - メッセージテンプレート
  
-Brazeと[IAM Studioの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/iam_studio/)統合により、カスタマイズ可能なアプリ内メッセージテンプレートをBrazeのアプリ内メッセージに簡単に挿入することができ、画像置換、テキスト変更、ディープリンク設定、カスタム属性、イベント設定を提供する。IAM Studioを使えば、メッセージ作成時間を短縮し、コンテンツプランニングにより多くの時間を割くことができる。
+Brazeと[IAM Studioの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/iam_studio/)統合により、カスタマイズ可能なアプリ内メッセージテンプレートをBrazeのアプリ内メッセージに簡単に挿入することができ、画像置換、テキスト変更、ディープリンク設定、カスタム属性、イベント設定を提供する。IAM Studio を使用すると、メッセージの作成時間を短縮し、コンテンツ計画により多くの時間を費やすことができます。
  
-#### リーガル - インスタント・チャット
+#### Regal - インスタントチャット
 
 Brazeと[Regalを]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/regal/)統合することで、すべての顧客接点において、より一貫性のあるパーソナライズされた体験を生み出すことができる。
 
-#### トレジャーデータ - コーホートインポート
+#### トレジャーデータ - コホートインポート
  
-Brazeと[Treasure Dataの]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/treasuredata/)統合により、Treasure DataからBrazeにユーザーコホートをインポートすることができる。
+Braze と[トレジャーデータ]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/treasuredata/)の統合により、トレジャーデータから Braze にユーザーコホートをインポートし、ウェアハウス内にのみ存在する可能性のあるデータに基づいてターゲットを絞ったキャンペーンを送信できるようになります。
  
 #### Zapier - ワークフローの自動化
  
-Brazeと[Zapierの]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/zapier/)パートナーシップは、Braze APIとBraze webhooksを活用してサードパーティアプリケーションと接続し、さまざまなアクションを自動化する。
+Braze と [Zapier]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/zapier/) のパートナーシップでは、Braze API と Braze Webhook を活用してサードパーティアプリケーションに接続し、さまざまなアクションを自動化します。
 
 ### SDKのアップデート
  
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Android SDK 31.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
 - [Braze Segment Swift プラグイン 3.0.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md#300)
-    - Braze Swift SDKバインディングを更新し、9.2.0+ SemVerのリリースを必要とするようにした。
-        - これにより、Braze SDKの9.2.0から10.0.0までのどのバージョンとも互換性がある。
-        - 潜在的な変更点の詳細については、[7.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#700)、[8.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#800)、[9.0.](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#900)0の変更履歴を参照のこと。
-    - プッシュ通知のサポートには、アプリのライフサイクルのできるだけ早い段階で、アプリケーションの`AppDelegate.application(_:didFinishLaunchingWithOptions:)` メソッドでスタティック・メソッド`BrazeDestination.prepareForDelayedInitialization()` を呼び出す必要がある。
+    - Braze Swift SDK バインディングを更新して、9.2.0+ SemVer 仕様のリリースを必要とするようにします。
+        - これにより、Braze SDK の9.2.0から10.0.0までのあらゆるバージョンとの互換性が確保されます (10.0.0は含まれません)。
+        - 破壊的な変更の可能性に関する詳細については、[7.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#700)、[8.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#800)、および[9.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#900)の変更ログエントリを参照してください。
+    - プッシュ通知のサポートでは、アプリケーションの `AppDelegate.application(_:didFinishLaunchingWithOptions:)` メソッドにおいて、アプリのライフサイクルのできるだけ早い段階で静的メソッド `BrazeDestination.prepareForDelayedInitialization()` を呼び出すことが必要になりました。
 - [Cordova SDK 9.0.0-9.2.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
-    - ネイティブiOSブリッジを[Braze Swift SDK 7.7.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
-- [Expo プラグイン 2.1.1](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md#211)
+    - ネイティブ iOS ブリッジを [Braze Swift SDK 7.7.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
+- [Expo プラグイン2.1.1](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md#211)
 - [Flutter SDK 10.1.0](https://pub.dev/packages/braze_plugin/changelog)
 - [React Native SDK 11.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/11.0.0/CHANGELOG.md)
 - [Swift SDK 9.1.0-9.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#920)
-- ユニティ 6.0.0
-    - ネイティブiOSブリッジを[Braze Swift SDK 7.7.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
-    - ネイティブAndroidブリッジを[Braze Android SDK 29.0.1から30.3.0に](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+- Unity 6.0.0
+    - ネイティブ iOS ブリッジを [Braze Swift SDK 7.7.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
+    - ネイティブ Android ブリッジを [Braze Android SDK 29.0.1から30.3.0に](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
 - [Web SDK 5.3.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - Xamarin SDKバージョン5.0.0
-    - iOSバインディングを[Braze Swift SDK 8.4.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/8.4.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+    - iOSバインディングを [Braze Swift SDK 8.4.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/8.4.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
 
 ## 2024年4月30日リリース
 
 ### プロモーション・コード・リストを作成または更新する権限
 
-2024年4月以降、プロモーションコード一覧を作成・更新するには、「キャンペーン、キャンバス、カード、セグメント、メディアライブラリへのアクセス」権限が必要となる。権限名とその説明の一覧については、「[限定されたチーム・ロールの権限を管理する]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#managing-limited-and-team-role-permissions)」を参照のこと。
+2024年4月以降、プロモーションコード一覧を作成・更新するには、「キャンペーン、キャンバス、カード、セグメント、メディアライブラリへのアクセス」権限が必要となる。権限名とその説明のリストについては、[制限付きおよびチームロール権限の管理]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#managing-limited-and-team-role-permissions)を参照してください。
 
 ### データの柔軟性
 
@@ -374,31 +374,31 @@ Brazeと[Zapierの]({{site.baseurl}}/partners/data_and_infrastructure_agility/wo
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-[ジャストインタイム・プロビジョニングは]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/saml_jit)SAML SSOと連動し、新規ダッシュボード・ユーザーが最初のサインイン時にBrazeアカウントを作成できるようにする。これにより、管理者は新しいダッシュボード・ユーザーのアカウントを手動で作成し、権限を選択し、ワークスペースに割り当て、アカウントを有効にするのを待つ必要がなくなる。
+[ジャストインタイムプロビジョニング]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/saml_jit)は、SAML SSO と連携して、新しいダッシュボードユーザーが初回サインイン時に Braze アカウントを作成できるようにします。これにより、管理者が新しいダッシュボード ユーザーのアカウントを手動で作成し、権限を選択してワークスペースに割り当て、アカウントの有効化を待機する必要がなくなります。
 
-#### パーミッション・セットとロール
+#### 権限セットとロール
 
-[パーミッション・セットを使って]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#permission-sets-and-roles)、特定のサブジェクト領域やアクションに関連するパーミッションを束ねる。これらの権限セットは、異なるワークスペース間で同じアクセスを必要とするダッシュボードユーザーに適用することができる。
+[パーミッション・セットを使って]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#permission-sets-and-roles)、特定のサブジェクト領域やアクションに関連するパーミッションを束ねる。これらの権限セットは、異なるワークスペースにわたって同じアクセス権を必要とするダッシュボードユーザーに適用できます。
 
-#### クラウドデータ収集セグメント
+#### クラウドデータ取り込みセグメント
 
-Braze[Cloud Data Ingestionセグメントを]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/cdi_segments)使用すると、CDI接続を介して利用可能になったデータを使用して、独自のデータウェアハウスに直接問い合わせるSQLを記述し、Braze内でターゲットとなるユーザーグループを作成することができる。
+Braze [クラウドデータ取り込みセグメント]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/cdi_segments)を使用すると、CDI 接続を介して利用可能なデータを使用して独自のデータウェアハウスを直接クエリする SQL を記述し、Braze 内でターゲットにできるユーザーグループを作成できます。
 
-### 創造性を解き放つ
+### 創造性を引き出す
 
 ### クエリビルダーのテンプレート
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-Query Builderのテンプレートを使って、SnowflakeのBrazeデータを使ったレポートを作成できる。[クエリ・ビルダー・テンプレートに]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/)アクセスするには、レポート作成時に**クエリ・テンプレートを**選択する。すべてのテンプレートは過去60日までのデータを表示するが、エディターで直接その値や他の値を編集することができる。
+クエリービルダーテンプレートを使用して、Snowflake から Braze データを使用してレポートを作成できます。[クエリービルダー]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/)テンプレートにアクセスするには、レポートの作成時に**クエリテンプレート**を選択します。すべてのテンプレートは過去60日までのデータを表示するが、エディターで直接その値や他の値を編集することができる。
 
 ### セグメント別パフォーマンスデータ
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-クエリビルダーのレポートテンプレートで、キャンペーン、バリアント、キャンバス、キャンバスステップの[パフォーマンスデータをセグメント別に]({{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/#performance-data-by-segment)分解できる。
+クエリビルダーレポートテンプレートでは、キャンペーン、バリアント、キャンバス、キャンバスステップの[パフォーマンスデータをセグメント別に]({{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/#performance-data-by-segment)分類できます。
 
-### ロバスト・チャンネル
+### 強力なチャネル
 
 #### SMSメッセージの自動リンク短縮
 
@@ -406,36 +406,36 @@ Query Builderのテンプレートを使って、SnowflakeのBrazeデータを
 
 [自動リンク短縮]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/keyword_handling/?tab=manage%20responses#managing-keywords-and-auto-responses)機能を使って、回答中の静的URLを自動的に短縮する。文字数カウンタが更新され、短縮URLの予想される長さが表示されるからだ。
 
-### 新しいブレイズ・パートナーシップ
+### Braze の新しいパートナーシップ
 
-#### Friendbuy - ロイヤリティ
+#### Friendbuy - ロイヤルティ
 
-Brazeと[Friendbuyの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/friendbuy/)統合を活用して、EメールやSMSの機能を拡張し、紹介やロイヤルティプログラムのコミュニケーションを簡単に自動化しよう。Brazeは、Friendbuyを通じて収集したオプトイン済みの電話番号の顧客プロファイルを作成する。
+Brazeと[Friendbuyの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/friendbuy/)統合を活用して、EメールやSMSの機能を拡張し、紹介やロイヤルティプログラムのコミュニケーションを簡単に自動化しよう。Braze では、Friendbuy 経由で収集されたすべてのオプトイン電話番号の顧客プロファイルが生成されます。
 
 ### NiftyImages - ダイナミックコンテンツ
 
-Brazeと[NiftyImagesの]({{site.baseurl}}/partners/message_personalization/dynamic_content/niftyimages/)パートナーシップにより、既存のBrazeパーソナライズタグをNiftyImagesのURLにマッピングすることで、メールキャンペーン用にダイナミックでパーソナライズされた画像を作成することができる。
+Braze と[NiftyImages]({{site.baseurl}}/partners/message_personalization/dynamic_content/niftyimages/) のパートナーシップにより、既存の Braze パーソナライゼーションタグを NiftyImages URL にマッピングすることで、メールキャンペーンのダイナミックでパーソナライズされた画像を作成できます。
 
 ### SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Android SDK 30.4.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
 - [Braze Segment Swift プラグイン 2.4.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md#240)
 - [Flutter SDK 9.0.0](https://pub.dev/packages/braze_plugin/changelog)
-    - ネイティブiOSブリッジを[Braze Swift SDK 7.7.0から8.4.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...8.4.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+    - ネイティブ iOS ブリッジを [Braze Swift SDK 7.7.0から8.4.0](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...8.4.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)に更新します。
         - iOSの最小デプロイメントターゲットは12.0に更新された。
-    - ネイティブAndroidブリッジを[Braze Android SDK 29.0.1から30.3.0に](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+    - ネイティブ Android ブリッジを [Braze Android SDK 29.0.1から30.3.0](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)に更新します。
     - サポートされるDartの最小バージョンは2.15.0である。
 - [React Native SDK 9.2.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
 - [Swift SDK 8.3.0-8.4.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
 - [Swift SDK 9.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
     - BrazeKitのプライバシーマニフェストからデフォルトのプライバシー追跡ドメインを削除する。
-        - Brazeの[データトラッキング機能を]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest/)使用している場合は、アプリレベルのプライバシーマニフェストにトラッキングエンドポイントを手動で追加する必要がある。
-        - 統合ガイダンスについては、更新された[チュートリアルを](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/e1-privacy-tracking)参照のこと。
+        - Braze [データトラッキング機能]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest/)を使用している場合は、トラッキングエンドポイントをアプリレベルのプライバシーマニフェストに手動で追加する必要があります。
+        - 統合の手引きについては、更新d [チュートリアル](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/e1-privacy-tracking)を参照してください。
     - 非推奨の`BrazeDelegate.braze(_:sdkAuthenticationFailedWithError) method in favor of BrazeSDKAuthDelegate.braze(_:sdkAuthenticationFailedWithError)` を削除する。
-        - このメソッドは[リリース5.14.](https://github.com/braze-inc/braze-swift-sdk/releases/tag/5.14.0)0で非推奨となった。
-        - 新しいデリゲート・メソッドへの切り替えに失敗しても、コンパイラー・エラーは発生しない。代わりに、あなたが定義した`BrazeDelegate.braze(_:sdkAuthenticationFailedWithError)` 。
+        - このメソッドは、元は[release 5.14.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/5.14.0) で非推奨になりました。
+        - 新しいデリゲートメソッドへの切り替えるに失敗しても、コンパイラエラーはトリガーされません。代わりに、定義した`BrazeDelegate.braze(_:sdkAuthenticationFailedWithError)` メソッドは単に呼び出されません。
 - [Xamarin SDKバージョン4.0.3](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md#403)
 
 ## 2024年4月2日リリース
@@ -444,11 +444,11 @@ Brazeと[NiftyImagesの]({{site.baseurl}}/partners/message_personalization/dynam
 
 #### 複数のビジネスアカウント
 
-各ワークスペースに複数のWhatsApp Businessアカウントとサブスクリプショングループを追加できる。詳しくは[WhatsApp Businessの複数アカウントと電話]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups/)番号をご覧下さい。
+複数の WhatsApp Business アカウントと購読グループを各ワークスペースに追加できるようになりました。詳細な手順については、「[複数の WhatsApp ビジネスアカウントと電話番号]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups/)」を参照してください。
 
 #### 料金を読む
 
-WhatsAppは、より価値ある体験を創造し、企業のマーケティング会話とのエンゲージメントを最大化するために、インドの消費者を対象に新しいアプローチをテストしている。これには、ある人がある期間にどの企業からもらってくるマーケティングの会話の数を制限し、読まれる可能性の低い少数の会話から始めることも含まれる。詳しくは[メタ・リソースを]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/meta_resources/)参照のこと。
+WhatsApp では、企業のマーケティング会話により、価値の高い体験を創出し、エンゲージメントを最大にする新しい手法のテストが、インドの消費者を対象に開始されました。これには、ある特定の時期に、ある企業から受け取るマーケティングの会話の回数を制限することも含まれます。これは、読まれにくい少数の会話から始まります。詳細については、[メタリソース]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/meta_resources/)を参照してください。
 
 ### データの柔軟性
 
@@ -456,7 +456,7 @@ WhatsAppは、より価値ある体験を創造し、企業のマーケティン
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-Cloud Data Ingestion for S3を使用して、AWSアカウント内の1つまたは複数のS3バケットをBrazeに直接統合できるようになった。新規ファイルが S3 にパブリッシュされると、メッセージが SQS に投稿され、Braze のクラウドデータ取り込みがそれらの新規ファイルを取り込みます。詳細については、[ファイル・ストレージの統合を]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/file_integrations/)参照のこと。
+S3 用のクラウドデータ取り込みを使用して、AWS アカウントの 1 つ以上の S3 バケットを Braze と直接連携できるようになりました。新規ファイルが S3 にパブリッシュされると、メッセージが SQS に投稿され、Braze のクラウドデータ取り込みがそれらの新規ファイルを取り込みます。詳細については、[ファイルストレージの統合]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/file_integrations/)を参照してください。
 
 #### Shopify OAuth
 
@@ -466,47 +466,47 @@ Shopifyは、あらゆる規模の小売ビジネスを開始し、成長させ
 
 #### iOSのプッシュ通知にExpoを使う
 
-Expo with React Nativeを使ってリッチなプッシュ通知とプッシュストーリーをiOSアプリに統合する[手順を追加した]({{site.baseurl}}/developer_guide/platform_integration_guides/react_native/push_notifications/?tab=expo)。
+React Nativeで Expo を使用して、リッチプッシュ通知とプッシュストーリーを iOS アプリに統合するための[手順を追加]({{site.baseurl}}/developer_guide/platform_integration_guides/react_native/push_notifications/?tab=expo)しました。
 
-#### リモート・スタート iOSライブ・アクティビティ
+#### iOS ライブアクティビティのリモート起動
 
-これで、iOS上でライブ・アクティビティをリモート・スタートできるようになった。 [`/messages/live_activity/start`]({{site.baseurl}}/api/endpoints/messaging/live_activity/start/)エンドポイントを使う。完全なウォークスルーは、[ライブ・アクティビティを参照のこと：]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/#step-2-start-the-activity) アクティビティを開始する。
+これで、[`/messages/live_activity/start`]({{site.baseurl}}/api/endpoints/messaging/live_activity/start/) エンドポイントを使用して、iOS でライブアクティビティをリモートで起動できます。詳細な手順については、「[ライブアクティビティ:アクティビティを開始する]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/#step-2-start-the-activity)」を参照してください。
 
 ### AIとMLの自動化
 
-#### 推奨アイテム
+#### 項目の推奨事項
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-Sage AI by Brazeを使えば、最も人気のある商品を計算したり、特定のカタログに対してパーソナライズされたAIレコメンデーションを作成したりすることができる。詳しくは、[アイテムの推奨についてを]({{site.baseurl}}/user_guide/sage_ai/recommendations/about_item_recommendations/)参照のこと。
+Braze による Sage AI を使用すると、最も人気のある製品を計算したり、特定のカタログのパーソナライズされた AI レコメンデーションを作成したりできます。詳細については、[項目の推奨事項について]({{site.baseurl}}/user_guide/sage_ai/recommendations/about_item_recommendations/)を参照してください。
 
 #### アプリ内メッセージの内容をQAする
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-以前は、BrazeのダッシュボードでSage AIを使ってSMSやプッシュ通知のコンテンツの品質保証を行うことができた。[アプリ内メッセージの内容もQA]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_content_qa/)できるようになった。
+以前は、Braze ダッシュボードで Sage AI を使用して SMS およびプッシュ通知コンテンツで品質保証を実行できました。[アプリ内メッセージの内容もQA]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_content_qa/)できるようになった。
 
-### 新しいブレイズ・パートナーシップ
+### Braze の新しいパートナーシップ
 
-#### 国勢調査 - コーホート・インポート
+#### Census - コホートインポート
 
-BrazeからCensusにコホートユーザーを[インポートできるようになりました]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/census/)。これは、SnowflakeやBigQueryのようなクラウドデータウェアハウスをBrazeに接続するデータアクティベーションプラットフォームです。貴社のマーケティングチームは、ファーストパーティデータの力を引き出し、ダイナミックなオーディエンスセグメントを構築し、顧客属性を同期してキャンペーンをパーソナライズし、Braze内のすべてのデータを最新の状態に保つことができる。
+BrazeからCensusにコホートユーザーを[インポートできるようになりました]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/census/)。これは、SnowflakeやBigQueryのようなクラウドデータウェアハウスをBrazeに接続するデータアクティベーションプラットフォームです。マーケティングチームは、ファーストパーティデータの力を解き放ち、ダイナミックなオーディエンスセグメントを構築し、顧客属性を同期してキャンペーンをパーソナライズし、Braze 内の全てのデータを最新の状態に保つことができます。
 
 ### SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
-- [リアクト・ネイティブ 9.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+- [React Native 9.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
   - React Nativeの最小バージョンを0.71.0に更新した。
   - iOSの最低バージョンを12.0に更新した。
-  - iOSバインディングを更新し、Braze Swift SDK 8.1.0を使用するようにした。
-  - Braze Android SDK 30.1.1を使用するようにAndroidバインディングを更新した。
+  - Braze Swift SDK 8.1.0を使用するように iOS バインディングを更新しました。
+  - Braze Android SDK 30.1.1を使用するように Android バインディングを更新しました。
 
 ## 2024年3月5日リリース
 
-### Google EUユーザー同意ポリシー
+### Google EU ユーザー同意ポリシー
 
-グーグルは、2024年3月6日から施行される[デジタル市場法（DMA](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)）の変更に対応するため、[EUユーザー同意ポリシーを](https://www.google.com/about/company/user-consent-policy/)更新している。この新たな変更により、広告主はEEAおよび英国のエンドユーザーに特定の情報を開示し、彼らから必要な同意を得る必要がある。今度の変更の一環として、[Brazeで両方の同意シグナルをカスタム属性として収集する]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)ことができる。Brazeは、これらのカスタム属性のデータをGoogleの適切な同意フィールドに同期する。
+Googleは[EUユーザー同意ポリシー](https://www.google.com/about/company/user-consent-policy/)を[Digital Markets Act (DMA)](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)の変更に応じて更新しています。これは2024年3月6日現在有効です。この新しい変更により、広告主は EEA および英国のエンドユーザーに特定の情報を開示し、必要な同意を得る必要があります。予定されているこの変更の一環として、[Braze で両方の同意シグナルをカスタム属性として収集]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)できるようになります。Brazeは、これらのカスタム属性のデータをGoogleの適切な同意フィールドに同期する。
 
 ### データの柔軟性
 
@@ -514,134 +514,134 @@ BrazeからCensusにコホートユーザーを[インポートできるよう
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-Brazeのダッシュボードで、[重複ユーザーを検索してマージし]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users)、キャンペーンとCanvasの効果を最大化できるようになった。ユーザ・プロフィールを個別にマージすることも、識別子が一致するすべてのプロフィールを最近更新されたユーザ・プロフィールにマージするバルク・マージを実行することもできる。
+Brazeのダッシュボードで、[重複ユーザーを検索してマージし]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users)、キャンペーンとCanvasの効果を最大化できるようになった。ユーザープロファイルを個別にマージすることも、識別子が一致するすべてのプロファイルを最近更新されたユーザープロファイルにマージする一括マージを実行することもできます。
 
 #### アーカイブされたコンテンツを検索する
 
-Brazeダッシュボードで、**アーカイブされたコンテンツを表示するを**選択することで、[検索結果にアーカイブされたコンテンツを]({{site.baseurl}}/user_guide/administrative/access_braze/global_search/#filter-for-archived-content)含めることができるようになった。
+Braze ダッシュボードで、[アーカイブされた内容を検索結果]({{site.baseurl}}/user_guide/administrative/access_braze/global_search/#filter-for-archived-content)に含めるには、**アーカイブされた内容を表示**を選択します。
 
-#### AWS S3とGoogle Cloud Storageのメッセージ・アーカイブをサポートする
+#### AWS S3および Google Cloud Storage のメッセージアーカイブサポート
 
-[メッセージアーカイブを]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/)使用すると、アーカイブやコンプライアンス目的でユーザーに送信したメッセージのコピーをAWS S3バケット、Azure Blob Storageコンテナ、Google Cloud Storageバケットに保存できる。
+[メッセージのアーカイブ]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/)を使用すると、アーカイブやコンプライアンスの目的で、ユーザーに送信したメッセージのコピーを AWS S3バケット、Azure Blob Storage コンテナー、または Google Cloud Storage バケットに保存できます。
 
 #### SQL テーブルリファレンス
 
-クエリ・ビルダーやSQL Segment Extensionsの生成時にクエリ可能なテーブルとカラムを確認するには、[SQLテーブル・リファレンスを]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/sql_segments_tables/)参照する。
+[SQLテーブル参照]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/sql_segments_tables/)にアクセスして、クエリビルダでクエリする、またはSQLセグメント拡張を生成するときに使用できるテーブルと列を確認します。
 
-### 創造性を解き放つ
+### 創造性を引き出す
 
 #### AIコピーライティングのためのトーンコントロール
 
 AIコピーライティングアシスタントで生成されるコピーのスタイルを決定するために、[メッセージトーンを]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/#steps)選択できるようになった。
 
-### ロバスト・チャンネル
+### 強力なチャネル
 
 #### カード作成
 
-Brazeが新しいコンテンツカードキャンペーンとキャンバスのステップでオーディエンスの適格性とパーソナライズを評価するタイミングは、カードが[作成さ]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/)れるタイミングを指定することで選択できる。 
+カードが[作成]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/)されるタイミングを指定することで、Braze が新しいコンテンツカードキャンペーンとキャンバスステップのオーディエンス適格性とパーソナライゼーションを評価するタイミングを選択できます。 
 
 #### ユーザーパスをプレビューする
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-ユーザーが受け取るタイミングやメッセージをプレビューするなど、ユーザーのために作成したキャンバスの旅を体験しよう。これらの[テストは]({{site.baseurl}}/preview_user_paths/)、キャンバスを送信する前に、メッセージが適切なオーディエンスに送信されているかどうかの品質保証として機能する。
+ユーザー用に作成したキャンバスジャーニーを体験しましょう。これには、受信するタイミングやメッセージのプレビューも含まれます。これらの[テスト実行]({{site.baseurl}}/preview_user_paths/)は、キャンバスを送信する前に、メッセージが適切なオーディエンスに送信されているかどうかの品質保証として機能します。
 
 #### クイック・プッシュ・キャンペーン
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-Brazeでプッシュキャンペーンを作成する際、複数のプラットフォームやデバイスを選択し、[クイックプッシュと]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/quick_push/)呼ばれる1回の編集で、すべてのプラットフォーム向けに1つのメッセージを作成することができる。この機能はキャンペーンでのみ利用できる。
+Braze でプッシュキャンペーンを作成する場合、[クイックプッシュ]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/quick_push/) と呼ばれる単一の編集エクスペリエンスで、すべてのプラットフォームs に対して1 つのメッセージを作成する複数のプラットフォームs とデバイスを選択できます。この機能はキャンペーンでのみ利用できる。
 
-#### カスタムリスト-配信停止ヘッダー
+#### カスタムの list-unsubscribe ヘッダー
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-メールメッセージに[カスタムリスト・アンサブスクライブヘッダーを]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#custom-list-unsubscribe-header)追加することで、受信者がオプトアウトできるようになる。この方法で、あなた自身が設定したワンクリック配信停止エンドポイントと、オプションの "mailto: "を追加することができる。ワンクリック配信停止 HTTP が Yahoo および Gmail の一括送信者に対する要件であるため、Braze では、カスタムの list-unsubscribe ヘッダーをサポートするために URL を入力する必要があります。
+[カスタムの list-unsubscribe ヘッダー]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#custom-list-unsubscribe-header)をメールメッセージングに追加すると、受信者がオプトアウトできるようになります。これにより、独自に設定したワンクリック配信停止 エンドポイントとオプションの「mailto:」を追加できます。ワンクリック配信停止 HTTP が Yahoo および Gmail の一括送信者に対する要件であるため、Braze では、カスタムの list-unsubscribe ヘッダーをサポートするために URL を入力する必要があります。
 
-#### アプリ内メッセージ用の複数のページ
+#### アプリ内メッセージの複数ページ
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-[アプリ内メッセージにページを追加する]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/#multi-page)ことで、オンボーディングフローやウェルカムジャーニーのような連続したフローでユーザーを誘導することができる。**Build**タブの**Pages**セクションからページを管理できる。
+[アプリ内メッセージにページを追加する]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/#multi-page)ことで、オンボーディングフローやウェルカムジャーニーのようなシーケンシャルなフローを通じてユーザーをガイドできます。**Build**タブの**Pages**セクションからページを管理できる。
 
 #### 実験パスのランダム化
 
-常に実験パスステップのパス割り当てを[ランダム化する]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step)には、ステップで**実験パスのランダム化されたパス**を選択します。このオプションは、勝者パスまたはパーソナライズされたパスを用いる場合は使用できません。
+実験パスの[パス割り当てステップを常にランダム化]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step)するには、ステップで \[**実験パスのランダムパス**] を選択します。このオプションは、勝者パスまたはパーソナライズされたパスを用いる場合は使用できません。
 
 #### 電子メール・キャプチャ・フォーム
 
-[Eメールキャプチャメッセージを]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form/)使えば、サイトのユーザーに簡単にEメールアドレスの送信を促すことができる。
+[ メールキャプチャメッセージ]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form/) を使用すると、サイトのユーザーにメール住所を送信するように簡単に促すことができます。その後、すべてのメッセージング キャンペーンで使用できるように、ユーザープロファイルで使用できます。
 
 ### SDKのアップデート
  
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [AppboyKit iOS SDK 4.7.0](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.7.0)
-    - これは、2024年3月1日にObjective-C SDKが終了する前の最後のリリースとなる（[Swift SDKの](https://github.com/braze-inc/braze-swift-sdk/)使用が優先されるため）。
+    - これは、2024年3月1日のサポート終了前の Objective-C SDK の最終リリースとなります ([Swift SDK](https://github.com/braze-inc/braze-swift-sdk/) の使用を優先)。
     - SDWebImageの最小必要バージョンを5.8.2から5.18.7に更新した。このバージョンには、[プライバシーに影響を与えるSDK](https://developer.apple.com/support/third-party-SDK-requirements/)リストに表示されるSDWebImageのプライバシーマニフェストが含まれている。
 - [Flutter SDK 8.1.0](https://pub.dev/packages/braze_plugin/changelog)
-- [ユニティ 5.2.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
+- [Unity 5.2.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
 - [React Native SDK 8.4.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.4.0/CHANGELOG.md)
 - [Xamarin SDKバージョン4.0.2](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
 - [Swift SDK 7.7.0-8.0.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#801)
 - [Android SDK 30.1.0-30.2.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
 - [Web SDK 5.1.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - [Cordova SDK 8.0.0-Cordova SDK 8.1.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
-    - ネイティブAndroidブリッジを[Braze Android SDK 27.0.1から30.0.0に](https://github.com/braze-inc/braze-android-sdk/compare/v27.0.0...v30.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
-    - ネイティブiOSブリッジを[Braze Swift SDK 6.6.0から7.6.0に](https://github.com/braze-inc/braze-swift-sdk/compare/6.6.0...7.6.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+    - ネイティブ Android ブリッジを [Braze Android SDK 27.0.1から30.0.0に](https://github.com/braze-inc/braze-android-sdk/compare/v27.0.0...v30.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
+    - ネイティブ iOS ブリッジを [Braze Swift SDK 6.6.0から7.6.0に](https://github.com/braze-inc/braze-swift-sdk/compare/6.6.0...7.6.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
     - `Banner` コンテンツ・カード・タイプの名前を`ImageOnly` に変更した：
-        - `ContentCardTypes.BANNER` への `ContentCardTypes.IMAGE_ONLY`
+        - `ContentCardTypes.BANNER` から `ContentCardTypes.IMAGE_ONLY`
         - Androidでは、プロジェクト内のXMLファイルにコンテンツカードのバナーという単語が含まれている場合、それを`image_only` に置き換える必要がある。
     - `BrazePlugin.getFeatureFlag(id)` は、featureフラグが存在しない場合、`null` を返すようになった。
-    - `BrazePlugin.subscribeToFeatureFlagsUpdates(function)` は、リフレッシュリクエストが成功または失敗で完了したとき、および現在のセッションから以前にキャッシュされたデータがあった場合は最初のサブスクリプションのときにのみトリガーする。
-    - 非推奨のメソッド`registerAppboyPushMessages` を削除した。代わりに`setRegisteredPushToken` 。
+    - `BrazePlugin.subscribeToFeatureFlagsUpdates(function)` は、更新リクエストが成功または失敗して完了したとき、および現在のセッションから過去にキャッシュされたデータがあった場合の初回のサブスクリプション時にのみトリガーされます。
+    - 非推奨のメソッド`registerAppboyPushMessages` を削除しました。代わりに`setRegisteredPushToken` を使用します。
 
 ## 2024年2月6日リリース
 
-### プライバシー・マニフェスト
+### Brazeのプライバシーマニフェスト
 
-Brazeは、宣言されたトラッキングデータを自動的に専用の`-tracking` エンドポイントにリルートする新しい柔軟なAPIとともに、独自のプライバシー・マニフェストをリリースした。詳細については、[Brazeのプライバシー・マニフェストを]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest)参照のこと。
+Brazeは、宣言されたトラッキングデータを自動的に専用の`-tracking` エンドポイントにリルートする新しい柔軟なAPIとともに、独自のプライバシー・マニフェストをリリースした。詳細については、[Brazeプライバシーマニフェスト]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest)を参照してください。
 
-### Google EUユーザー同意ポリシー
+### Google EU ユーザー同意ポリシー
 
-グーグルは、2024年3月6日に施行される[デジタル市場法（DMA](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)）の変更に対応するため、[EUユーザー同意ポリシーを](https://www.google.com/about/company/user-consent-policy/)更新している。この新たな変更により、広告主はEEAおよび英国のエンドユーザーに特定の情報を開示し、彼らから必要な同意を得る必要がある。今度の変更の一環として、[Brazeで両方の同意シグナルをカスタム属性として収集する]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)ことができる。Brazeは、これらのカスタム属性のデータをGoogleの適切な同意フィールドに同期する。
+Google は、2024年3月6日に発効した[デジタル市場法 (DMA)](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html) の変更に対応して、[EU ユーザー同意ポリシー](https://www.google.com/about/company/user-consent-policy/)を更新します。この新しい変更により、広告主は EEA および英国のエンドユーザーに特定の情報を開示し、必要な同意を得る必要があります。予定されているこの変更の一環として、[Braze で両方の同意シグナルをカスタム属性として収集]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)できるようになります。Brazeは、これらのカスタム属性のデータをGoogleの適切な同意フィールドに同期する。
 
 ### データの柔軟性
 
-#### Google Firebase Cloud Messaging (FCM) API
+#### Google Firebase クラウドメッセージング(FCM) API
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[Googleの非推奨Cloud Messaging APIから、完全にサポートされたFirebase Cloud Messaging (FCM) APIに移行]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/)できるようになった。 
+[Google の廃止予定の Cloud Messaging API から、完全にサポートされている Firebase Cloud Messaging (FCM) API への移行]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/)が可能になります。 
 
-#### Braze Cloud Data Ingestion（CDI）エンドポイント
+#### Braze クラウドデータ取り込み (CDI) エンドポイント
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-BrazeのCDIエンドポイントを使用する：
+Braze CDI エンドポイントを使用して、以下を実行します。
 - [既存の統合のリストを返す]({{site.baseurl}}/api/endpoints/cdi/get_integration_list/)。
 - 指定した統合の[過去の同期ステータスのリストを返す]({{site.baseurl}}/api/endpoints/cdi/get_job_sync_status/)。
 - 指定した統合の[同期をトリガーする]({{site.baseurl}}/api/endpoints/cdi/post_job_sync/)。
 
-#### Braze Cloud Data Ingestion (CDI)がDatabricksをサポートする。
+#### Braze クラウドデータ取り込み (CDI) での Databricks のサポート
 
-カタログのBraze CDIサポートが[Databricksソースで]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/sync_catalogs_data/#step-2-integrate-cloud-data-ingestion-with-catalog-data)利用可能になった。
+Braze CDI で、[Databricks ソース]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/sync_catalogs_data/#step-2-integrate-cloud-data-ingestion-with-catalog-data)がカタログのサポートの対象なりました。
 
 #### 手動によるSwift SDKの統合
 
-パッケージマネージャを使用せずに手動でSwift SDKを統合する方法を説明するために、統合ガイドに[手動統合の]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration)記事を追加した。
+[手動統合]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration)記事を統合ガイドに追加し、パッケージマネージャーを使用せずにSwift SDKを手動で統合する方法について説明しました。
 
 #### 非推奨
 
 2024年1月11日、BrazeはWindowsアプリとBaiduアプリからのメッセージ配信とデータ収集を停止した。
 
-### 創造性を解き放つ
+### 創造性を引き出す
 
 #### SQLセグメント拡張の使用例
 
-[SQL Segment Extensionsユースケースライブラリには]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/use_cases)、SQL Segment Extensionsのテスト済みクエリが含まれており、独自のSQLクエリを作成する際のインスピレーションとして利用できる。
+[SQL セグメントエクステンションユースケース]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/use_cases)ライブラリに、独自の SQL クエリの作成時にヒントとして使用できる SQL セグメントエクステンション用のテスト済みクエリが含まれています。
 
-### ロバスト・チャンネル
+### 強力なチャネル
 
 #### カスタム・コード・ブロック
 
@@ -657,67 +657,67 @@ BrazeのCDIエンドポイントを使用する：
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-電子メールメッセージに[BCCアドレスを]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/?tab=bcc%20address#outbound-email-settings)付加することができる。これは、あなたのユーザーが受信したメッセージの同一コピーを、あなたのBCC受信トレイに送信する。これにより、コンプライアンス要件やカスタマーサポートの問題のために、ユーザーに送信したメッセージのコピーを保持することができる。
+電子メールメッセージに[BCCアドレスを]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/?tab=bcc%20address#outbound-email-settings)付加することができる。これにより、ユーザーが受信したメッセージの同じコピーがBCC 受信トレイに送信されます。これにより、コンプライアンス要件やカスタマーサポートの問題のために、ユーザーに送信したメッセージのコピーを保持することができる。
 
 #### ワンクリックでメール配信を停止できるリンク
 
 [list-unsubscribeヘッダーを]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#list-unsubscribe-header)使用すると、メール本文ではなく、メールボックスのUI内に**配信停止**ボタンを表示することで、受信者がマーケティングメールからワンクリックで配信停止できるようになる。
 
-### 新しいブレイズ・パートナーシップ
+### Braze の新しいパートナーシップ
 
-#### Criteo - キャンバス・オーディエンス・シンク
+#### Criteo - キャンバスオーディエンス同期
 
-[CriteoへのBraze Audience Syncを]({{site.baseurl}}/partners/canvas_steps/criteo_audience_sync/)使用することで、ブランドは、自社のBrazeインテグレーションからCriteoの顧客リストにユーザーデータを追加し、行動トリガーやセグメンテーションなどに基づいて広告を配信することができる。ユーザーデータに基づいてBraze Canvasでメッセージ（プッシュ、Eメール、SMS、ウェブフックなど）をトリガーするために通常使用するあらゆる基準を、Criteoの顧客リストでそのユーザーに広告をトリガーするために使用できるようになった。
+[Braze Audience Sync to Criteo]({{site.baseurl}}/partners/canvas_steps/criteo_audience_sync/) を使用すると、ブランドは独自の Braze 統合からのユーザーデータを Criteo の顧客リストに追加して、行動トリガーやセグメンテーションなどに基づいて広告を配信できます。ユーザーデータに基づいて Braze キャンバスでメッセージをトリガーするために通常使用する基準 (プッシュ、メール、SMS、Webhook など) を、Criteo 顧客リスト内の該当ユーザーに対して広告をトリガーするために使用できるようになりました。
 
-#### ムーバブル・インク - ダイナミック・コンテンツ
+#### Movable Ink - ダイナミックコンテンツ
 
-[Movable Ink]({{site.baseurl}}/partners/message_personalization/dynamic_content/movable_ink#movable-ink)Customer Data API統合により、マーケティング担当者はBrazeに保存されている顧客イベントデータを有効化して、Movable Ink内でパーソナライズされたコンテンツを生成することができる。
+[Movable Ink]({{site.baseurl}}/partners/message_personalization/dynamic_content/movable_ink#movable-ink) 顧客データ API の統合により、マーケターは Braze に保存されている顧客イベントデータをアクティブ化して、Movable Ink 内でパーソナライズされたコンテンツを生成できます。
 
-#### スキューバ・アナリティクス - 分析
+#### Scuba Analytics - 分析
 
-[Scuba Analyticsは]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/scuba#scuba-analytics)、高速時系列データ用に設計された、フルスタックの機械学習機能付きデータ・コラボレーション・プラットフォームである。Scubaでは、ユーザー（アクターとも呼ばれる）を選択的にエクスポートし、Brazeプラットフォームにロードすることができる。スクーバでは、カスタムのアクター・プロパティを使って行動傾向を分析し、さまざまなプラットフォームでデータを活性化し、機械学習を使って予測モデリングを行う。
+[Scuba Analyticsは]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/scuba#scuba-analytics)、高速時系列データ用に設計された、フルスタックの機械学習機能付きデータ・コラボレーション・プラットフォームである。Scubaでは、ユーザー（アクターとも呼ばれる）を選択的にエクスポートし、Brazeプラットフォームにロードすることができる。Scuba では、カスタムアクタープロパティを使用して動作トレンドを分析し、さまざまなプラットフォーム間でデータを有効化し、マシンラーニングを使用して予測モデリングを実行します。
 
 ### SDKのアップデート
  
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
  
-- [Expo プラグイン 2.0.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
-    - [Expo SDK 50の要件に従い](https://expo.dev/changelog/2024/01-18-sdk-50)、iOSの最小プラットフォームバージョンを`13.4` 。
-    - このバージョンでは、Expo SDK 50を完全にサポートするために、Braze React Native SDKのバージョン[8.3.0以上が](https://github.com/braze-inc/braze-react-native-sdk/releases/tag/8.3.0)必要である。
+- [Expo プラグイン2.0.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+    - [Expo SDK 50の要件](https://expo.dev/changelog/2024/01-18-sdk-50)に従って、iOSの最低プラットフォームバージョンを`13.4`に上げます。
+    - このバージョンでは、Expo SDK 50を完全にサポートするために、Braze React Native SDK のバージョン[8.3.0以上](https://github.com/braze-inc/braze-react-native-sdk/releases/tag/8.3.0)が必要です。
 - [React Native SDK 8.3.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.3.0/CHANGELOG.md)
 - [Unity SDK 5.1.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
 - [Android SDK 30.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
-    - アプリ内メッセージに使用されるWebViewが更新され、`WebViewAssetLoader` を使用するようになった。
-        - `WebSettings.allowFileAccess` `InAppMessageHtmlBaseView` と`BrazeWebViewActivity` では false に設定されている。
+    - アプリ内メッセージに使用される WebView が、`WebViewAssetLoader`を使用するために更新されました。
+        - `InAppMessageHtmlBaseView` と `BrazeWebViewActivity` で、`WebSettings.allowFileAccess` が False に設定されました。
         - 独自の`InAppMessageWebViewClient` または`InAppMessageHtmlBaseView` を使用している場合は、オリジナルのクラスと比較して、実装が正しくアセットをロードしていることを確認してほしい。
         - カスタム・クラスを使用していない場合は、すべてが以前と同じように機能する。
 - [Braze Swift SDK 6.6.2](https://github.com/braze-inc/braze-swift-sdk/blob/6.6.2/CHANGELOG.md)
 - [Braze Swift SDK 7.6.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0)
 - [Xamarin SDKバージョン3.0.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
-    - NuGetパッケージは、`AppboyPlatformXamariniOSBinding` から次のように名前が変更された。 [`BrazePlatform.BrazeiOSBinding`](https://www.nuget.org/packages/BrazePlatform.BrazeiOSBinding/).
-        - 更新されたパッケージを使用するには、using`AppboyPlatformXamariniOSBinding;` をusing Brazeに置き換える；
-    - このバージョンでは、.NET 6+を使用する必要があり、Xamarinフレームワークを使用するプロジェクトのサポートは削除された。Xamarinのサポート終了前後の[Microsoftのポリシー](https://dotnet.microsoft.com/en-us/platform/support/policy/xamarin)を参照してください。
-    - Androidバインディングを[Braze Android SDK 26.3.2から29.0.1に](https://github.com/braze-inc/braze-android-sdk/compare/v26.3.1...v29.0.1#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+    - NuGet パッケージの名前が`AppboyPlatformXamariniOSBinding` から[`BrazePlatform.BrazeiOSBinding`](https://www.nuget.org/packages/BrazePlatform.BrazeiOSBinding/) に変更されました。
+        - 更新されたパッケージを使用するには、`AppboyPlatformXamariniOSBinding;` を使用するすべてのインスタンスを Braze を使用ように置き換えます。
+    - このバージョンでは、NET 6以降を使用する必要があり、Xamarin フレームワークを使用するプロジェクトのサポートが削除されます。Xamarinのサポート終了前後の[Microsoftのポリシー](https://dotnet.microsoft.com/en-us/platform/support/policy/xamarin)を参照してください。
+    - Android バインドを [Braze Android SDK 26.3.2から29.0.1](https://github.com/braze-inc/braze-android-sdk/compare/v26.3.1...v29.0.1#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)に更新しました。
 - [Xamarin SDK 4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
-    - このバージョンは、[Braze Swift SDKを](https://github.com/braze-inc/braze-swift-sdk/)使用するためにiOSバインディングを更新する。ほとんどのiOSパブリックAPIが変更されたため、使用するAPIの変更については、[移行ガイド](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/appboy-migration-guide/)（Swift）を参照されたい。私たちは、古いパブリックAPIを使い続けるための互換バインディングを提供している。
+    - このバージョンは、[ Braze Swift SDK](https://github.com/braze-inc/braze-swift-sdk/) を使用するためにiOS バインドを更新します。ほとんどのiOSパブリックAPIが変更されたため、使用するAPIの変更については、[移行ガイド](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/appboy-migration-guide/)（Swift）を参照されたい。私たちは、古いパブリックAPIを使い続けるための互換バインディングを提供している。
         - iOSバインディングは現在、複数のモジュールで構成されている：
-            - **BrazeKitだ：**アナリティクスとプッシュ通知のサポートを提供する主なSDKライブラリ（nuget： [Braze.iOS.BrazeKit](https://www.nuget.org/packages/Braze.iOS.BrazeKit)).
-            - BrazeUIである：Brazeが提供するアプリ内メッセージとコンテンツカード用のユーザーインターフェイスライブラリ（nuget： [Braze.iOS.BrazeUI](https://www.nuget.org/packages/Braze.iOS.BrazeUI)).
-            - ブレイズロケーション位置情報解析とジオフェンス監視をサポートする位置情報ライブラリ（nuget： [Braze.iOS.BrazeLocation](https://www.nuget.org/packages/Braze.iOS.BrazeLocation)).
+            - **BrazeKit:**アナリティクスとプッシュ通知のサポートを提供する主なSDKライブラリ（nuget： [Braze.iOS.BrazeKit](https://www.nuget.org/packages/Braze.iOS.BrazeKit)).
+            - BrazeUI:Brazeが提供するアプリ内メッセージとコンテンツカード用のユーザーインターフェイスライブラリ（nuget： [Braze.iOS.BrazeUI](https://www.nuget.org/packages/Braze.iOS.BrazeUI)).
+            - BrazeLocation:位置情報解析とジオフェンス監視をサポートする位置情報ライブラリ（nuget： [Braze.iOS.BrazeLocation](https://www.nuget.org/packages/Braze.iOS.BrazeLocation)).
             - BrazeKitCompat：4.0.0以前のAPIをサポートする互換ライブラリ（nuget： [Braze.iOS.BrazeKitCompat](https://www.nuget.org/packages/Braze.iOS.BrazeKitCompat)).
             - BrazeUICompat：4.0.0以前のUI APIをサポートする互換ライブラリ（nuget： [Braze.iOS.BrazeUICompat](https://www.nuget.org/packages/Braze.iOS.BrazeUICompat)).
         - 新しい統合についてはBrazeiOSMauiSampleAppを、互換モジュールの使用法についてはBrazeiOSMauiCompatSampleAppを参照のこと。
-    - iOSバインディングを[Braze Swift SDK 7.6.0に](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0)更新。
-    - iOSバインディングでは、Xcode 15との互換性のために.NET 7を使用する必要がある。
+    - iOS バインドを[Braze Swift SDK 7.6.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0) に更新しました。
+    - iOS バインドでは、Xcode 15との互換性を確保するために、NET 7を使用する必要があります。
 - [Xamarin SDK 4.0.1](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
 
 ## 2024年1月9日リリース
 
 ### Shopifyとの統合に関するドキュメントを更新
 
-BrazeとShopifyの統合ドキュメントの一部を更新した：
+以下のようなBrazeとShopifyインテグレーションドキュメントのセクションを更新します。
 
-- [Shopifyを使い始める]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/)
+- [Shopify を使い始める]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/)
 - [BrazeでShopifyを設定する]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/)
 - [ShopifyのユーザーID管理]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_user_identity/)
 
@@ -727,31 +727,31 @@ BrazeとShopifyの統合ドキュメントの一部を更新した：
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-カタログを使った[在庫切れ通知と]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications/)キャンバスを組み合わせることで、顧客に商品の在庫切れを通知することができる。顧客が選択したカスタムイベントを実行するたびに、その商品が補充されたときに通知されるように自動的に購読することができる。
+カタログとキャンバスによる[再入荷通知]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications/)を組み合わせて使用​​することで、商品の再入荷時に顧客に通知できます。選択されたカスタムイベントを実行した顧客が、商品の補充時に通知を受け取れるよう自動的に配信登録できます。
 
 #### カタログセグメント
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-[カタログ・セグメントは]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/catalog_segments/)、SQL Segment Extensionsのカタログ・データに基づくユーザーのオーディエンスである。これらのSQLセグメントエクステンションは、セグメントで参照され、キャンペーンやキャンバスでターゲットにすることができる。カタログセグメントは、SQL を使用して、カタログのデータとカスタムイベントまたは購入のデータとを結合します。これを行うには、カタログとカスタムイベントまたは購入に共通の識別子フィールドが必要です。
+[カタログセグメント]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/catalog_segments/)は、SQL セグメントエクステンションのカタログデータに基づくユーザーのオーディエンスです。これらのSQLセグメントエクステンションは、セグメントで参照され、キャンペーンやキャンバスでターゲットにすることができる。カタログセグメントは、SQL を使用して、カタログのデータとカスタムイベントまたは購入のデータとを結合します。これを行うには、カタログとカスタムイベントまたは購入に共通の識別子フィールドが必要です。
 
 #### Firebase Cloud Messaging API への移行
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-Googleの非推奨Cloud Messaging APIから、完全にサポートされたFirebase Cloud Messaging (FCM) APIに[移行する方法を]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/)学ぶ。
+Google の廃止予定の Cloud Messaging API から、完全にサポートされている Firebase Cloud Messaging (FCM) API への[移行方法]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/)について説明します。
 
 ### SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Swift SDK 7.5.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
-    - `BrazeKit` 、`BrazeLocation` 、Brazeのデータ収集ポリシーを説明するプライバシー・マニフェストを追加する。詳細については、プライバシー・マニフェストに関するAppleの[文書を](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests)参照のこと。データ収集の慣行を管理するためのより多くの設定は、将来のリリースで利用可能になる予定である。
+    - `BrazeKit`および`BrazeLocation`のプライバシーマニフェストを追加して、Brazeのデータ収集ポリシーを説明します。詳細については、プライバシー・マニフェストに関するAppleの[文書を](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests)参照のこと。データ収集プラクティスを管理するためのその他の設定は、今後のリリースで利用できるようになります。
     - 7.1.0で導入されたXCFrameworksのコード署名に関する問題を修正した。
 - [Web SDK v5.1.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - [Unity SDK 5.0.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
-    - ネイティブiOSブリッジをBraze Swift SDK 6.1.0から7.4.0に更新。
-        - iOSリポジトリーのリンクは、この[リポジトリーから](https://github.com/braze-inc/braze-swift-sdk-prebuilt-dynamic)ビルド済みのダイナミックXCFrameworksを指すようになった。
-    - ネイティブAndroidブリッジをBraze Android SDK 27.0.1から29.0.1に更新。
+    - ネイティブ iOS ブリッジを Braze Swift SDK 6.1.0から7.4.0に更新しました。
+        - iOS リポジトリリンクが、この[リポジトリ](https://github.com/braze-inc/braze-swift-sdk-prebuilt-dynamic)から事前構築済みのダイナミック XCFramework を指すようになりました。
+    - ネイティブ Android ブリッジを Braze Android SDK 27.0.1から29.0.1に更新しました。
     - `AppboyBinding.GetFeatureFlag(string id)` は、featureフラグが存在しない場合、`null` を返すようになった。
-    - `FEATURE_FLAGS_UPDATED` は、リフレッシュリクエストが成功または失敗で完了したとき、および現在のセッションから以前にキャッシュされたデータがあった場合は最初のサブスクリプションのときにのみトリガーする。
\ No newline at end of file
+    - `FEATURE_FLAGS_UPDATED` は、更新リクエストが成功または失敗して完了したとき、および現在のセッションから過去にキャッシュされたデータがあった場合の初回のサブスクリプション時にのみトリガーされます。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2016/august.md b/_lang/ja/_help/release_notes/2016/august.md
index 416e2a16b87..ffaf5117dea 100644
--- a/_lang/ja/_help/release_notes/2016/august.md
+++ b/_lang/ja/_help/release_notes/2016/august.md
@@ -9,7 +9,7 @@ description: "この記事には2016年8月のリリースノートが含まれ
 # 2016年8月
 
 ## iOS 10リッチプッシュ通知
-iOS 10で顧客にリッチな通知を送ることができるようになった。詳しくは、iOS 10のリッチ通知をサポートするための[アプリの設定]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration/#ios-10-rich-notifications)方法を参照のこと。
+iOS 10でリッチプッシュ通知を顧客に送信できるようになりました。詳しくは、iOS 10のリッチ通知をサポートするための[アプリの設定]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration/#ios-10-rich-notifications)方法を参照のこと。
 
 ## コンバージョンイベントとしてアップグレードアプリを追加
-ユーザーにアプリのアップグレードを促すことは、多くの顧客にとって重要なユースケースである。新しいアプリのバージョンは、より安定しているかもしれないし、収益を上げるチャンスがあるかもしれない。アプリのアップグレードをキャンペーンの[コンバージョンイベントとして]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/conversion_events/#conversion-events)追跡することで、メッセージング活動がどのように目標を達成しているかを簡単に追跡することができる。
+ユーザーにアプリのアップグレードを促すことは、多くのお客様にとって重要なユースケースです。新しいアプリ版の方が安定していたり、収益を牽引するチャンスが多いかもしれない。アプリのアップグレードをキャンペーン[コンバージョンイベント]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/conversion_events/#conversion-events)としてトラッキングすることで、メッセージングの取り組みの目標達成状況を簡単にトラッキングできます。
diff --git a/_lang/ja/_help/release_notes/2016/december.md b/_lang/ja/_help/release_notes/2016/december.md
index 60e3e077954..6d8cb0a7e03 100644
--- a/_lang/ja/_help/release_notes/2016/december.md
+++ b/_lang/ja/_help/release_notes/2016/december.md
@@ -10,11 +10,11 @@ description: "この記事には2016年12月のリリースノートが含まれ
 
 ## メールヘッダー
 
-メール ヘッダー s は、メール ヘッダー s の明示的な設定を送信エンドポイントを介して追加します。Brazeを使用したメールの送信の詳細については、[メールのベストプラクティス][14]を参照してください。
+メールヘッダーにより、送信エンドポイントを介してメールヘッダーの明示的な設定が追加されます。Brazeを使用したメールの送信の詳細については、[メールのベストプラクティス][14]を参照してください。
 
-## キャンバス更新
+## キャンバスの更新
 
-この更新を使用すると、1 つのステップを複数のステップs に接続したり、複数の s を1 つの結合ステップに接続したり、それらの間に接続点を描画したりできます。たとえば、購買を行ったユーザーは、行っていないユーザーとは別の流れをたどるかもしれない。キャンバスの詳細については、[ブランチの作成][15]を参照してください。
+この更新により、1つのステップを複数のステップに接続したり、複数のステップを1つのマージされたステップに接続したり、それらのステップ間に接続ポイントを描画したりできます。例えば、購入を行ったユーザーは、購入を行っていないユーザーとは別のフローに従うことができます。キャンバスの詳細については、[分岐の作成][15]を参照してください。
 
 [14]: {{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/
 [15]: {{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/branching/#branching
diff --git a/_lang/ja/_help/release_notes/2016/july.md b/_lang/ja/_help/release_notes/2016/july.md
index f14a7cf065c..c37667a13ca 100644
--- a/_lang/ja/_help/release_notes/2016/july.md
+++ b/_lang/ja/_help/release_notes/2016/july.md
@@ -8,19 +8,19 @@ description: "この記事には2016年7月のリリースノートが含まれ
 
 # 2016年7月
 
-## エラータイプ別にDeveloper Consoleのエラーログをフィルタリングする
+## エラータイプによる開発者コンソールのエラーログのフィルタリング
 
-このアップグレードにより、Developer Consoleのメッセージエラーログを使用して、Brazeの統合に関する問題のトラブルシューティングが容易になる。これはユーザビリティのアップデートであり、メッセージエラーログをタイプ別にフィルタリングすることができる。
+このアップグレードにより、開発者コンソールのメッセージエラーログを使用して、Braze 統合の問題をトラブルシューティングしやすくなります。これは、ユーザビリティ更新で、メッセージエラーログを種類別にフィルターし、具体的なインテグレーションの問題を簡単に見つけて特定することができます。
 
 ## 最後に送信されたアンインストール追跡プッシュのタイムスタンプを追加した。
 
-Brazeは、顧客のアプリにサイレント・プッシュを送信し、どのデバイスが反応するかを確認することで、アンインストールを検知する。この機能は、アンインストールトラッキングが最後に実行された日時を示すタイムスタンプを控えめに追加する。このタイムスタンプは、アンインストール追跡が設定されている「設定」ページで確認できる。[アンインストール・トラッキングについて]({{site.baseurl}}/user_guide/data_and_analytics/uninstall_tracking/#uninstall-tracking)もっと知る。
+Brazeは、顧客のアプリにサイレント・プッシュを送信し、どのデバイスが反応するかを確認することで、アンインストールを検知する。この機能により、アアンインストール追跡が最後に実行された日時を示す、目立たないタイムスタンプが追加されます。このタイムスタンプは、アンインストール追跡が設定されている「設定」ページで確認できる。詳細については、[トラッキングのアンインストール]({{site.baseurl}}/user_guide/data_and_analytics/uninstall_tracking/#uninstall-tracking)を参照してください。
 
 ![トラッキング・チェックボックスをアンインストールする][6]
 
 ## ウェブフック・テストの機能強化
 
-Brazeからライブウェブフックメッセージをテスト送信できるようになった。テスト・メッセージを送信することで、安全なサンドボックス環境で、メッセージとサーバー・エンドポイントが適切に設定されていることを確認することができる。[ウェブフックについて]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/#creating-a-webhook)もっと知る。
+キャンペーンを本番に設定する前に、Braze からライブ Webhook をテスト送信できるようになりました。テスト・メッセージを送信することで、安全なサンドボックス環境で、メッセージとサーバー・エンドポイントが適切に設定されていることを確認することができる。[webhook]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/#creating-a-webhook) について詳しく説明します。
 
 ## キャンペーン受信者のCSVエクスポートに受信メッセージのバリエーションを追加
 
@@ -28,9 +28,9 @@ Brazeからライブウェブフックメッセージをテスト送信できる
 
 ## インプレッション数のおおよその制限
 
-アプリ内メッセージが一定数のインプレッションを獲得すると、Brazeはユーザーにメッセージを受け取る資格を与えることを停止する。設定 アプリ roximate [インプレッション s]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#setting-a-max-impression-cap) の制限について詳しく説明します。
+アプリ内メッセージが一定数のインプレッションを獲得すると、Brazeはユーザーにメッセージを受け取る資格を与えることを停止する。インプレッションのおおよその制限の設定について詳しくは、[こちら]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#setting-a-max-impression-cap)をご覧ください。
 
-![IAMインプレッションキャップ][11]
+![IAM インプレッション上限][11]
 
 [6]: {% image_buster /assets/img_archive/uninstall_tracking_checkbox.png %}
 [11]: {% image_buster /assets/img_archive/approx_limit_for_IAM.png %}
diff --git a/_lang/ja/_help/release_notes/2016/june.md b/_lang/ja/_help/release_notes/2016/june.md
index 24f99ea04f4..a3f732d7b97 100644
--- a/_lang/ja/_help/release_notes/2016/june.md
+++ b/_lang/ja/_help/release_notes/2016/june.md
@@ -10,19 +10,19 @@ description: "この記事には2016年6月のリリースノートが含まれ
 
 ## 例外イベントを実行するアクションベースのトリガー
 
-例外イベントは、アクションベースのキャンペーンで強力なロジックを作成するために使用される。エンドユーザーがメッセージを受け取らないようにするために使われる。例えば、「ショッピングカートを放棄したユーザーには、チェックアウトしない限りプッシュ通知を送る」というものだ。例外イベントをトリガーにすることで、顧客はカートを放棄した後にチェックアウトしたユーザーに追加のメッセージや注意を向けることができ、シームレスでまとまりのある体験を作り出すことができる。
+例外イベントは、アクションベースのキャンペーンで強力なロジックを作成するために使用される。エンドユーザーがメッセージを受け取らないようにするために使われる。例えば、「ショッピングカートを放棄したユーザーには、チェックアウトしない限りプッシュ通知を送る」というものだ。例外イベントをトリガーすることで、カートを放棄した後にチェックアウトしたユーザーに追加のメッセージを送信するか、注意を向けることができ、シームレスで一貫したエクスペリエンスを生み出すことができます。
 
 ## 「タグ付きキャンペーンからの受信メッセージ」セグメントフィルター
 
-顧客は、すでに使用しているのと同じ「タグ」機能によって、キャンペーンのグループを受信したユーザーを除外できるようになった。
+すでに使用している同じ「タグ」機能によって、キャンペーンのグループを受信したユーザーを除外できるようになりました。
 
 ## 複数のキャンペーンを同時に一時停止・再開する
 
-キャンペーンページから、複数のキャンペーンを同時に一時停止・再開できるようになった。
+キャンペーンページから複数のキャンペーンを同時に一時停止および再開できるようになりました。
 
 ## データAPIエンドポイントをアンインストールする
 
-顧客は、当社のエクスポートAPIからアンインストール追跡データを直接取得できるようになった。詳細については、[エクスポート・エンドポイントを][4]チェックしてほしい。
+エクスポート API からアンインストール追跡データを直接取得できるようになりました。詳細については、[エクスポート・エンドポイントを][4]チェックしてほしい。
 
 ## エラーログの改善
 
diff --git a/_lang/ja/_help/release_notes/2016/november.md b/_lang/ja/_help/release_notes/2016/november.md
index b96b366e3fb..76d30452bf7 100644
--- a/_lang/ja/_help/release_notes/2016/november.md
+++ b/_lang/ja/_help/release_notes/2016/november.md
@@ -3,16 +3,16 @@ nav_title: 11月
 page_order: 2
 noindex: true
 page_type: update
-description: "この記事には2016年11月のリリースノートが含まれている。"
+description: "この記事には、2016年11月のリリースノートが含まれています。"
 ---
 
 # 2016年11月
 
-## コネクテッド・オーディエンス
+## 接続オーディエンス
 
-Connected Audiencesを使えば、Brazeで事前に設定することなく、ユーザーベースのサブセットをターゲットにしたメッセージをその場で送ることができる。例えば、メディアアプリはカスタム属性配列を使って、顧客がお気に入りにしたすべてのカテゴリーやテレビ番組を追跡することができる。Connected Audiencesを使えば、カスタムCMSとBrazeを接続し、新しいエピソードが公開されるたびに、番組をお気に入り登録した人に自動的にプッシュ通知やメールを送ることができる。
+接続オーディエンスを使用すると、Braze で事前設定を行うことなく、ユーザー群のサブセットをターゲットにしたメッセージを即時に送信できます。例えば、メディアアプリは、カスタム属性配列を使用して、顧客がお気に入りに登録したすべてのカテゴリーやテレビ番組をトラッキングできます。接続オーディエンスを使用することで、カスタム CMS と Braze を接続し、新しいエピソードがリリースされるたびに、番組をお気に入りに登録したユーザーに自動的にプッシュ通知やメールを送信できます。
 
-[コネクテッド・オーディエンス・オブジェクトを][12]参照するか、[コネクテッド・オーディエンスに関する][13]ブログをチェックしてほしい。
+「[接続オーディエンスオブジェクト][12]」を参照するか、[接続オーディエンス][13]に関する当社のブログをご確認ください。
 
 [12]: {{site.baseurl}}/api/objects_filters/connected_audience/
 [13]: https://www.braze.com/blog/connected-audiences/
diff --git a/_lang/ja/_help/release_notes/2016/october.md b/_lang/ja/_help/release_notes/2016/october.md
index 8f47024fa1d..8f64f0d2a04 100644
--- a/_lang/ja/_help/release_notes/2016/october.md
+++ b/_lang/ja/_help/release_notes/2016/october.md
@@ -9,18 +9,18 @@ description: "この記事には2016年10月のリリースノートが含まれ
 # 2016年10月
 
 ## 新しいセキュリティー設定s
-Brazeには、パスワードの有効期限ルール、パスワードの長さルール、パスワードの複雑さルール、ダッシュボード IP ログインの許可、2 要素認証などのセキュリティ機能が追加されています。
+パスワードの有効期限のルール、パスワードの長さのルール、パスワードの複雑さのルール、ダッシュボード IP ログイン許可リスト、2 要素認証など、強化されたセキュリティ機能が Braze に追加されました。
 
 > 更新:Braze の**Security Settings** は、**Company Settings** ページからアクセスでき、パスワードの再利用と有効期限の規則も含まれています。
 
 ## インポート後のCSV ダウン読み込む
-Braze ユーザー s は、最近インポートしたユーザーのCSV を読み込むできるようになりました。これにより、システムからのデータ同期の可視性が向上します。詳細については、[CSV importing]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/) を参照してください。
+Braze ユーザーが、最近インポートしたユーザーの CSV を読み込めるようになりました。これにより、システムからのデータ同期の可視性が向上します。CSV インポートについて詳しくは、[こちら]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/)をご覧ください。
 
 ## 記念日フィルター
-[バースデーフィルター]({{site.baseurl}}/user_guide/Engagement_Tools/Segments/Segmentation_Filters/)に加えて、Brazeは記念日フィルターをサポートするようになりました。これにより、ロイヤルティのマイルストーンのカレンダー日に基づいてユーザーの目標を設定したり、通知を補充したりすることができます!この機能にアクセスするには、セグメントページで"カスタム属性とクォートの日付; フィルターを選択します。[フィルター s]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#segmentation-filters) について詳しく説明します。
+[バースデーフィルター]({{site.baseurl}}/user_guide/Engagement_Tools/Segments/Segmentation_Filters/)に加えて、Brazeは記念日フィルターをサポートするようになりました。これにより、ロイヤルティのマイルストーンのカレンダー日に基づいてユーザーの目標を設定したり、通知を補充したりすることができます!この機能にアクセスするには、\[セグメント] ページで \[カスタム属性の日付] フィルターを選択します。フィルターについて詳しくは、[こちら]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#segmentation-filters)をご覧ください。
 
-## 頻度キャップ 更新s
-以前は、フリークエンシーキャップの制約を無視したキャンペーンまたはキャンバスは、依然として度数制限にカウントされます。このビヘイビアを変更したのは、新しいキャンペーンや、周波数上限に従わないキャンバスをデフォルトすることで、それらのビヘイビアにも反映されないようにするためです。これはキャンペーンとキャンバスごとに設定できます。[フリークエンシーキャップ]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#frequency-capping) について詳しく説明します。
+## フリークエンシーキャップの更新
+以前は、フリークエンシーキャップの制限を無視したキャンペーンやキャンバスが、フリークエンシーキャップの対象としてカウントされていました。このビヘイビアを変更したのは、新しいキャンペーンや、周波数上限に従わないキャンバスをデフォルトすることで、それらのビヘイビアにも反映されないようにするためです。これはキャンペーンとキャンバスごとに設定できます。フリークエンシーキャップについて詳しくは、[こちら]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#frequency-capping)をご覧ください。
 
 ## アプリ中の本文のカラープロファイルs
-アプリ内メッセージ s に[color プロファイル s]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/customize/#color-profile) を追加しました。これにより、顧客 s は、Braze で新しいメッセージを作成するときに、オンブランドのカラースキームを再利用できます。
+アプリ内メッセージ用の[カラープロファイル]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/customize/#color-profile)を追加しました。これにより、Braze で新しいメッセージを作成する場合に、ブランド固有の配色を再利用できるようになります。
diff --git a/_lang/ja/_help/release_notes/2016/september.md b/_lang/ja/_help/release_notes/2016/september.md
index f5598fe4b45..6638394182e 100644
--- a/_lang/ja/_help/release_notes/2016/september.md
+++ b/_lang/ja/_help/release_notes/2016/september.md
@@ -12,4 +12,4 @@ description: "この記事は、2016年9月のリリースノートを含んで
 これで、セグメントに加えられた変更の履歴が表示されます。
 
 ## 最後に使用したデバイス
-次の属性では、すべてのプラットフォームでユーザーの最新の機器をテンプレートできます。
+すべてのプラットフォームで、ユーザーの最新のデバイスに対して次の属性をテンプレート化できます。
diff --git a/_lang/ja/_help/release_notes/2017.md b/_lang/ja/_help/release_notes/2017.md
index 8de60a306ef..a02f55d9681 100644
--- a/_lang/ja/_help/release_notes/2017.md
+++ b/_lang/ja/_help/release_notes/2017.md
@@ -3,7 +3,7 @@ page_order: 7
 nav_title: 2017
 layout: dev_guide
 noindex: true
-guide_top_header: "2017年リリースノート"
+guide_top_header: "2017 リリースノート"
 
 page_type: landing
 description: "このセクションでは、2017年のリリースノートを掲載する。"
diff --git a/_lang/ja/_help/release_notes/2017/april.md b/_lang/ja/_help/release_notes/2017/april.md
index 065373e74b4..78d961ef153 100644
--- a/_lang/ja/_help/release_notes/2017/april.md
+++ b/_lang/ja/_help/release_notes/2017/april.md
@@ -10,11 +10,11 @@ description: "この記事には2017年4月のリリースノートが含まれ
 
 ## HTMLブラウザ内メッセージ
 
-カスタムHTMLやEメール・キャプチャ・フォーマットを含む、インタラクティブなインブラウザ・メッセージ・タイプをサポートするようになった。[アプリ内メッセージについて][48]もっと知る。
+カスタム HTML およびメールキャプチャ形式を含むインタラクティブなブラウザ内メッセージタイプがサポートされるようになりました。これにより、どこにいても顧客にリーチできます。[アプリ内メッセージ s][48] について詳しく説明します。
 
 ## 接続されたコンテンツでパーソナライズされたアプリ内メッセージ
 
-アプリ内メッセージのトリガーに{% raw %} {%connected_content%} {% endraw %} ブロックが追加され、API経由でアクセス可能なあらゆる情報をメッセージに直接挿入することで、リッチなパーソナライゼーションを追加できるようになった。これで、プッシュ、Eメール、ウェブフックに加えて、アプリ内でコネクテッド・コンテンツを使うことができる。[コネクテッド・コンテンツについて][34]もっと知る。
+トリガーされたアプリ内メッセージに {% raw %} {%connected_content%} {% endraw %} ブロックを追加しました。これにより、API 経由でアクセス可能な情報をメッセージに直接挿入して、豊富なパーソナライゼーションを追加できます。プッシュ、メール、Webhook に加えて、アプリ内でコネクテッドコンテンツを使用できるようになりました。[Connected Content][34]について詳しく説明します。
 
 ## ニュースフィードカードのナビゲーションを改善
 
@@ -22,25 +22,25 @@ description: "この記事には2017年4月のリリースノートが含まれ
 
 ## iOSリッチ通知のプレビューを改善
 
-iOSのプレビュー通知では、リッチな通知が表示されるようになり、顧客に送信している内容をフォントサイズまで正確に把握できるようになった。[iOSのリッチ通知について][32]もっと知る。
+iOSのプレビュー通知では、リッチな通知が表示されるようになり、顧客に送信している内容をフォントサイズまで正確に把握できるようになった。詳細については、[iOS リッチプッシュ通知][32]を参照してください。
 
 ## プッシュ統計に「Influenced Opens」を追加
 
-Brazeで提供される標準的なキャンペーンとキャンバスの統計リストに「Influenced Opens」が追加され、キャンペーンのInfluenced、Direct、Total Opensの内訳を簡単に知ることができるようになった。[インフルエンス・オープンについて][31]もっと知る。
+「"Influenced Opens"」をBrazeで提供されているスタンダードキャンペーンとキャンバス統計の一覧に追加しました。これにより、「Influenced」、「Direct」、および「Total Opens」のキャンペーンの内訳がわかりやすくなります。詳細については、[誘発された開封数][31]を参照してください。
 
 ## 内部グループへのアップグレード
 
-複数の内部グループを作成し、SDKロギング、REST APIロギング、またはメッセージコンテンツテストのためにグループを使用するかどうかを示すプロパティを割り当てることができるようになった。[イベント・ユーザー・ログについて][30]もっと知る。
+複数の内部グループを作成し、SDKロギング、REST APIロギング、またはメッセージコンテンツテストのためにグループを使用するかどうかを示すプロパティを割り当てることができるようになった。[イベントユーザーログ][30]について詳しく説明します。
 
-> 更新された：内部グループは、[シードメールの送信にも]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/#seed-groups)使用できる。
+> 更新:内部グループを使用して、[シードメールs]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/#seed-groups)を送信することもできます。
 
 ## ウェブURLの新しいオプション
 
-プッシュメッセージ、アプリ内メッセージ、ブラウザ内メッセージ、ニュースフィードカードについて、外部ウェブブラウザでウェブURLを開くオプションが追加された。アプリへのディープリンク」アクションは、HTTP/HTTPSディープリンクにも対応するようになった。BranchやAppleのUniversal Linksのようなパートナーを使う場合は、SDKのカスタマイズが必要になる。[ディープリンクについて][29]もっと知る。
+プッシュメッセージ、アプリ内メッセージ、ブラウザ内メッセージ、ニュースフィードカードについて、外部ウェブブラウザでウェブURLを開くオプションが追加された。「アプリにディープリンクする」アクションと HTTP/HTTPS ディープリンクとの互換性も確保されました。Branch や Apple のユニバーサルリンクなどのパートナーを使用する場合は、SDK のカスタマイズが必要になります。詳細については、[ディープリンク][29]を参照してください。
 
-## 新しい "Performed Conversion "イベント・キャンバス
+## 新しい「コンバージョンを実行」イベントキャンバス
 
-新しい "Performed Conversion "イベントと "In Canvas Control "フィルターを追加し、リターゲティングオプションを改善した。[リターゲティング・フィルターの][28]使い方についてもっと知る。
+新しい「コンバージョンを実行」イベントと「キャンバス内コントロール」フィルターを追加し、リターゲティングを改善しました。[リターゲティングフィルター][28]の使用に関する詳細をご確認ください。
 
 
 
diff --git a/_lang/ja/_help/release_notes/2017/august.md b/_lang/ja/_help/release_notes/2017/august.md
index 6df7a110c31..c2b7a958cf2 100644
--- a/_lang/ja/_help/release_notes/2017/august.md
+++ b/_lang/ja/_help/release_notes/2017/august.md
@@ -8,62 +8,62 @@ description: "この記事には2017年8月のリリースノートが含まれ
 
 # 2017年8月
 
-## アクションボタンを押すためのアップデート
+## プッシュアクションボタンsへのアップデート
 
-REST APIメッセージングエンドポイントに[プッシュアクションボタンの][70]サポートを追加した。
+REST API メッセージングエンドポイントに[プッシュアクションボタン][70]のサポートを追加しました。
 
-## リキッドテンプレートの更新
+## リキッドテンプレーティングへのアップデート
 
 [メッセージのパーソナライズが][69]可能になった：
 - 送信先のデバイス、
-- デバイスID、
-- キャリアだ、
-- IDFAである、
-- モデルだ、
-- OS、そして
+- デバイス ID、
+- 通信事業者、
+- IDFA、
+- モデル、
+- OS、
 - プラットフォーム
 
-## APIトリガー・キャンバス
+## API トリガーキャンバス
 
 キャンペーン用の既存のエンドポイントと一致するAPIエンドポイント（送信、スケジュール、更新、削除）を介して[キャンバスを][68]トリガーできるようになったので、マーケティングの自動化と最適化をさらに進めることができる。
 
-## ウェブ・プッシュ・アクション・ボタン
+## Web プッシュアクションボタンs
 
-Chrome用のウェブSDKにプッシュアクションボタンのサポートが追加され、ユーザーの多忙な生活を簡素化するコンテキストに応じた選択肢を与えることで、エンゲージメントを高めることができる。[プッシュ通知のベストプラクティスを][66]チェックしよう。
+Chrome用のウェブSDKにプッシュアクションボタンのサポートが追加され、ユーザーの多忙な生活を簡素化するコンテキストに応じた選択肢を与えることで、エンゲージメントを高めることができる。[プッシュ通知のベストプラクティス][66]を確認してください。
 
 ## 新しいAPIエンドポイント
 
-新しいAPIエンドポイントを公開した。/email/hard_bouncesは、メールアドレス別または指定された日付範囲のハードバウンスを引き出すことができ、/messages/scheduled_broadcastsは、スケジュールされたキャンペーンとスケジュールされたエントリーのキャンバスが開始される次の時間を引き出すことができる。これらの新しいエンドポイントは、キャンペーンのさらなるカスタマイズと最適化を可能にする。[APIエンドポイントについて][65]もっと知る。
+新しい API エンドポイント /email/hard_bounces を公開しました。これにより、メールアドレスまたは特定の日付範囲でハードバウンスを取得できます。また、/messages/scheduled_broadcasts を使用すると、スケジュールされたキャンペーンとスケジュールされたエントリキャンバスが次に開始される時刻を取得できます。これらの新しいエンドポイントは、キャンペーンのさらなるカスタマイズと最適化を可能にする。詳細については、[API エンドポイントs][65] を参照してください。
 
 ## ジオフェンス
 
-ジオフェンスという新機能が追加され、顧客が定義された地理的エリアに出入りしたときにリアルタイムでメッセージをトリガーすることができるようになり、顧客とのパーソナライズされた適切なコミュニケーションが可能になった。[ロケーション・マーケティングについて][64]もっと知る。
+ジオフェンスという新しい機能を追加しました。これにより、顧客が定義済みの地理的エリアに出入りするときにリアルタイムでメッセージをトリガーし、顧客とのパーソナライズされた関連性の高いコミュニケーションが可能になります。[ロケーション・マーケティングについて][64]もっと知る。
 
 ## Eメールエディターの更新
 
-新しいメールエディタにダイナミックオートコンプリートを追加した。[アカデミーの][63]Eメールのベストプラクティスについてもっと知る。
+新しいメールエディタにダイナミックオートコンプリート機能を追加しました。これにより、Liquid を使用する際に顧客の実際のカスタム属性とイベントをオートコンプリートできるようになり、作業が楽になります。メール のベストプラクティスの詳細については、[Academy][63] を参照してください。
 
 ## 日付フィルターの更新
 
-一度もメッセージを受信したことがない、または一度もやりとりしたことがない顧客をターゲットにできるよう、「一度も」日付フィルタを追加。[フィルターについて][62]もっと知る。
+「まったく該当しない」日付フィルターを追加しました。これにより、メッセージを一度も受信または操作したことのない顧客をターゲットにでき、クリーンな顧客リストを保持して、メールの配信到達性を確保できます。フィルターについて詳しくは、[こちら][62]をご覧ください。
 
 ## キャンバスへの更新
 
-各キャンバスのバリアントの上部にパーセンテージが追加され、どのバリアントがより良いパフォーマンスをしているかが一目でわかるようになった。[キャンバスについて][61]もっと知る。
+各キャンバスのバリアントの上部にパーセンテージが追加され、どのバリアントがより良いパフォーマンスをしているかが一目でわかるようになった。キャンバスについて詳しくは、[こちら][61]をご覧ください。
 
-## インテリジェント・セレクションのキャンバス
+## インテリジェントセレクションを使用したキャンバス
 
-キャンバスにはインテリジェント・セレクションが追加され、より効率的にキャンバスをテストできるようになった。[インテリジェンス・スイートの][60]詳細はこちら。
+キャンバスにインテリジェントセレクションが追加され、キャンバスをより効率的にテストできるようになりました。詳細については、[Intelligence Suite][60] を参照してください。
 
-## 電子メールの表示名を更新
+## メールディスプレイの名前へのアップデート
 
-電子メールの表示名に特殊なUTF-8文字をサポートするようになったので、顧客によりパーソナライズされた電子メールを作成できるようになった。[Eメールのベストプラクティスについて][67]もっと知る。
+電子メールの表示名に特殊なUTF-8文字をサポートするようになったので、顧客によりパーソナライズされた電子メールを作成できるようになった。[メールのベストプラクティス][67]について詳しく説明します。
 
 ## エンゲージメント・レポートCSV集計
 
-キャンペーンやキャンバスの数に関係なく、すべてのキャンペーンとキャンバスの統合データを2つのファイルに分けて受け取ることができる。[エンゲージメント・レポートの][59]詳細はこちら。
+選択されているキャンペーンやキャンバスの数に関係なく、すべてのキャンペーンとすべてのキャンバスの統合データを2つの別々のファイルで受け取ることができるため、必要なときに必要なすべてのデータを入手できるようになりました。[エンゲージメント・レポートの][59]詳細はこちら。
 
-> [2017年9月のリリースノートで]({{site.baseurl}}/help/release_notes/2017/september/)述べたように、特定の期間のデータを集計したり、定期的にエクスポートを実行するようにスケジュールしたりできるようになった。
+> [2017年9月のリリースノート]({{site.baseurl}}/help/release_notes/2017/september/)に記載されているように、特定の期間のデータを集計したり、定期的なエクスポートの実行をスケジュールしたりできるようになりました。
 
 
 [59]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/engagement_reports/
diff --git a/_lang/ja/_help/release_notes/2017/december.md b/_lang/ja/_help/release_notes/2017/december.md
index d8bb7f0b563..c815a0bcaa5 100644
--- a/_lang/ja/_help/release_notes/2017/december.md
+++ b/_lang/ja/_help/release_notes/2017/december.md
@@ -8,4 +8,4 @@ description: "この記事には2017年12月のリリースノートが含まれ
 
 # 2017年12月
 
-今月は更新がない！2018年1月にまたチェックしよう！
+今月は更新がない！2018年1月にもう一度確認してください。
diff --git a/_lang/ja/_help/release_notes/2017/february.md b/_lang/ja/_help/release_notes/2017/february.md
index 2e0ca645151..faadd420a07 100644
--- a/_lang/ja/_help/release_notes/2017/february.md
+++ b/_lang/ja/_help/release_notes/2017/february.md
@@ -8,25 +8,25 @@ description: "この記事には2017年2月のリリースノートが含まれ
 
 # 2017年2月
 
-## 打ち上げ後にキャンバス・ステップを追加する
+## 起動後にキャンバスステップを追加する
 
 これで、[キャンバスステップs][23]を、キャンバスの起動後でも既存のステップs に追加できます。
 
 ## エンゲージメント・レポートの一括CSV
 
-[エンゲージメントレポートで][22]キャンペーンデータをCSVで一括エクスポートできるようになった。キャンバスのデータは、エンゲージメント・レポートからもエクスポートできる。
+[エンゲージメントレポート][22] を使用して、キャンペーンデータCSV を一括してエクスポートできるようになりました。キャンバスデータは、エンゲージメントレポートでもエクスポートできます。
 
 ## 最後に受信したアプリ内メッセージでフィルタリングする
 
-よりパーソナライズされたユーザーターゲティングのために、「最後に受信したアプリ内メッセージ」を時間ベースのフィルターとして使用できるようになった。Brazeのユーザー・ターゲティングの詳細については、[セグメンテーションを][21]参照。
+パーソナライズされた ユーザーターゲットの詳細については、"Last Received In-App Message"を時間ベースのフィルターとして使用できるようになりました。Brazeのユーザー・ターゲティングの詳細については、[セグメンテーションを][21]参照。
 
 ## イベントユーザーログのアップグレード
 
 アップグレードされた[イベント・ユーザー・ログにより][20]、SDKインテグレーションで何が起こっているかを簡単に確認できるようになった。
 
-## ニュースフィードのテンプレート
+## ニュースフィードテンプレート
 
-{% raw %} {{card.${name}}}{% endraw %} と{% raw %}  {{card.${api_id}}}{% endraw %} の2つのニュース・フィード・カード・フィールドが追加された。これらのカードはリキッドのテンプレートに追加できる。[パーソナライズされたメッセージとテンプレートについて][19]詳しく知る。
+{% raw %} {{card.${name}}}{% endraw %} と{% raw %}  {{card.${api_id}}}{% endraw %} の2つのニュース・フィード・カード・フィールドが追加された。これらのカードs は、液体テンプレートに追加できます。[パーソナライズされた メッセージングとテンプレート s][19]について詳しく説明します。
 
 [19]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/personalized_messaging/#personalized-messaging
 [20]: {{site.baseurl}}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab
diff --git a/_lang/ja/_help/release_notes/2017/january.md b/_lang/ja/_help/release_notes/2017/january.md
index 1cc1239d5e3..8b742983beb 100644
--- a/_lang/ja/_help/release_notes/2017/january.md
+++ b/_lang/ja/_help/release_notes/2017/january.md
@@ -9,19 +9,19 @@ description: "この記事には2017年1月のリリースノートが含まれ
 
 ## メール用の新しいコンバージョンイベント
 
-&quot のコンバージョンイベントを指定できるようになりました。開封; メール from キャンペーン" または" clicked メール from キャンペーン."[キャンペーン配信タイプ][16]について詳しく説明します。
+「キャンペーンからメールを開いた」または「キャンペーンからメールをクリックした」のコンバージョンイベントを指定できるようになりました。詳細については、「[キャンペーン配信タイプ][16]」を参照してください。
 
 ## コントロールグループによるCSVエクスポート
 ユーザー キャンペーンのCSV をエクスポートするときに、データにコントロールグループs を含めることができるようになりました。[ダッシュボードデータのエクスポート][17]について詳しく説明します。
 
-## ようこそとダブルオプトインメール
-新しく作成した"Added メール Address" アクション ベースのトリガーを使用すると、ユーザーが最初にメールアドレスを追加したときに、ダブルオプトインまたはウェルカムメールs を送信しやすくなります。[電子メールのベストプラクティス][18]について詳しく説明します。
+## ウェルカムメールとダブルオプトインメール
+新しく作成した「メールアドレスの追加」アクションベーストリガーを使用して、ユーザーが最初にメールアドレスを追加したときに、ダブルオプトインメールまたはウェルカムメールを送信しやすくなりました。[電子メールのベストプラクティス][18]について詳しく説明します。
 
-## List-Unsubscribe Email ヘッダー
-サブスクリプション ステータスが&quot、subscribed/opted in ユーザー s&quot、または&quot、opted in ユーザー s only.&quotのList-Unsubscribe ヘッダーを設定できるようになりました。これにより、"配信停止"リンクが送信者の名前の横にGmailに追加され、配信可能性の評価が向上します。
+## list-unsubscribe メールヘッダー
+購読ステータスが「購読中/オプトイン済みのユーザー」または「オプトイン済みのユーザーのみ」である list-unsubscribe ヘッダーを構成できるようになりました。これにより、Gmail の送信者名の横に「購読解除」リンクが追加され、配信可能性の評価が向上します。
 
 ## ユーザビリティ更新
-ボタンをクリックして、小さい画面のキャンバスヘッダーを最小化したり、Braze のユーザープロファイルのキャンバスとキャンペーンのフルネームの上にマウスポインタを置いたりできます。
+ボタンをクリックして、小さい画面用にキャンバスヘッダーを最小化し、Braze のユーザープロファイルでキャンバスとキャンペーンの完全な名前の上にカーソルを移動できるようになりました。
 
 
 
diff --git a/_lang/ja/_help/release_notes/2017/july.md b/_lang/ja/_help/release_notes/2017/july.md
index 453ae44e425..af7bde04f92 100644
--- a/_lang/ja/_help/release_notes/2017/july.md
+++ b/_lang/ja/_help/release_notes/2017/july.md
@@ -10,19 +10,19 @@ description: "この記事には2017年7月のリリースノートが含まれ
 
 ## Web プッシュにおける大きな画像
 
-Chrome の Windows および Android で Web プッシュの大きな画像のサポートを追加し、リッチで魅力的な顧客体験を作成できるようにしました。[Web プッシュ][58] について詳しく学びましょう。
+Windows および Android の Chrome 用 Web プッシュで大容量画像のサポートを追加して、豊かで魅力的なカスタマーエクスペリエンスを構築できるようにしました。[Web プッシュ][58] について詳しく学びましょう。
 
-## メールフィールドの更新
+## メール フィールドのアップデート
 
-これで、特定の送信元アドレスにメールをロックすることができ、誤ったアドレスを入力することがないようにすることができます。メール作成フォームには、過去6か月間に使用されたアドレスが事前に入力され、プロセスが合理化されます。[メールのベストプラクティス][57]をチェックして、詳細をご確認ください。
+間違ったアドレスを入力しないように、特定の差出人アドレスのセットにメールをロックできるようになりました。メール作成フォームには、過去6か月間に使用されたアドレスが事前に入力され、プロセスが合理化されます。[メールのベストプラクティス][57]をチェックして、詳細をご確認ください。
 
 ## キャンペーン詳細APIの更新
 
-`/campaign/details`エンドポイントは現在、そのメッセージに関する情報を提供しており、APIを使用して件名、HTML本文、送信元アドレス、および返信先フィールドを取得できます。Braze API について[詳しく知る][56]。
+`/campaign/details` エンドポイントが、そのメッセージに関する情報を提供し、API を使用して件名、HTML 本文、差出人アドレス、返信先のフィールドを取得できるようになりました。[ Braze API][56] について詳しく説明します。
 
-## Liquidテンプレートの更新
+## リキッドテンプレーティングの更新
 
-キャンバスとキャンペーンでテンプレートバリアント属性を追加しました。キャンバスでは、バリアントのAPI IDとバリアントの名前の両方をテンプレート化できるようになりました。また、キャンペーンではメッセージの`message_api_id`と`message_name`をテンプレート化できるようになりました。両方のアップデートにより、メッセージングの柔軟性が向上し、パーソナライズされたキャンペーンを構築できるようになります。[パーソナライズされたメッセージング][55] について詳しく学びましょう。
+キャンバスとキャンペーンで、バリアント属性をテンプレート化する機能を追加しました。キャンバスではバリアントの API ID と名前を、キャンペーンではメッセージの `message_api_id` と`message_name` をテンプレート化できるようになりました。両方の更新により、メッセージングの柔軟性が向上し、パーソナライズされたキャンペーンを構築できるようになります。[パーソナライズされたメッセージング][55] について詳しく学びましょう。
 
 ## 新しいHTMLメールエディター
 
@@ -30,11 +30,11 @@ Chrome の Windows および Android で Web プッシュの大きな画像の
 
 ## プレビューの更新
 
-キャンペーンやキャンバスでメッセージプレビューをスクロールすると、画面ウィンドウに従って変更が反映されるのを常に確認できます。プレビューとテストについて[詳しく知る][53]。
+キャンペーンとキャンバスでメッセージプレビューを下にスクロールすると、画面ウィンドウをたどることができ、反映された変更をいつでも確認できます。詳細については、「[プレビューとテスト][53]」を参照してください。
 
-## 新しいSegmentメンバーシップフィルター
+## 新しいセグメントメンバーシップフィルター
 
-[セグメントメンバーシップフィルター][52]を追加し、既存のセグメントのいずれかに基づいてユーザーをターゲットにすることができるようにしました。さらに、「And」と「Or」ロジックの両方をセグメントフィルターで使用する機能、およびセグメントを相互にネストする機能を追加しました。これらの更新により、顧客により正確にカスタマイズされたメッセージを送信できるようになります。 
+[セグメントメンバーシップフィルター][52]を追加しました。これにより、既存セグメントのいずれかのメンバーシップに基づいてユーザーをターゲット設定できます。さらに、「And」と「Or」ロジックの両方をセグメントフィルターで使用する機能、およびセグメントを相互にネストする機能を追加しました。これらの更新により、カスタマイズされたメッセージをより正確に顧客に送信できるようになります。 
 
 ## Androidプレビューに更新
 
diff --git a/_lang/ja/_help/release_notes/2017/june.md b/_lang/ja/_help/release_notes/2017/june.md
index b15830e7b35..936cab9ff9e 100644
--- a/_lang/ja/_help/release_notes/2017/june.md
+++ b/_lang/ja/_help/release_notes/2017/june.md
@@ -8,13 +8,13 @@ description: "この記事には2017年6月のリリースノートが含まれ
 
 # 2017年6月
 
-## 外部APIの更新
+## 外部API への更新
 
 外部APIを更新してAppleプッシュのcollapse_idフィールドをサポートし、顧客に正確にメッセージを送信できるようにしました。[BrazeメッセージングAPI][49]について詳しく学びましょう。
 
-## Web プッシュ通知の更新
+## ウェブプッシュ通知にアップデート
 
-Web プッシュ通知プレビューの更新を追加しました。ドロップダウンと正しい画像の高さのレンダリングを含み、Web プッシュ通知のテストと送信が容易になりました。[Web プッシュ][47] について詳しく学びましょう。
+ドロップダウンや正しい画像高さのレンダリングなど、Web プッシュ通知のプレビューに対する更新が追加され、Web プッシュ通知のテストと送信が容易になりました。[Web プッシュ][47] について詳しく学びましょう。
 
 ## セキュリティ設定の改善
 
@@ -28,7 +28,7 @@ Web プッシュ通知プレビューの更新を追加しました。ドロッ
 
 キャンバスのステップから送信されるメッセージに[テンプレート属性][45]を含める機能を追加し、より効率的に作業できるようにしました。
 
-## ターゲティングの更新
+## ターゲット設定の更新
 
 日付と時刻をフィルタリングする際に、時間単位として時間を選択できるようになり、メッセージをより正確にターゲットすることができます。フィルターについて[詳しく知る][44]。
 
diff --git a/_lang/ja/_help/release_notes/2017/march.md b/_lang/ja/_help/release_notes/2017/march.md
index 1fc42ae1af8..d0689c2e732 100644
--- a/_lang/ja/_help/release_notes/2017/march.md
+++ b/_lang/ja/_help/release_notes/2017/march.md
@@ -10,19 +10,19 @@ description: "この記事には2017年3月のリリースノートが含まれ
 
 ## 新しいリターゲティング・フィルター
 
-私たちは、よりシームレスなリターゲティングオプションを提供するために、新しい "Converted from Canvas "フィルタを追加した。[リターゲティング・フィルターの][27]使い方についてもっと知る。
+私たちは、よりシームレスなリターゲティングオプションを提供するために、新しい "Converted from Canvas "フィルタを追加した。[リターゲティングフィルター][27]の使用に関する詳細をご確認ください。
 
 ## Webhook テンプレート
 
-Webhookメッセージをテンプレートとして保存して簡単に再利用したり、Twilioを使ったSMSやFacebook Messengerのようなチャットボットのようなプラットフォーム用にあらかじめ設定されたテンプレートから始めることができるようになった。[ウェブフックの作成について][26]詳しく知る。
+Webhookメッセージをテンプレートとして保存して簡単に再利用したり、Twilioを使ったSMSやFacebook Messengerのようなチャットボットのようなプラットフォーム用にあらかじめ設定されたテンプレートから始めることができるようになった。[Webhook の作成][26]に関する詳細をご確認ください。
 
 ## エンゲージメント・レポートの複数の電子メール・サポート
 
-[エンゲージメント・レポートを][25]複数のEメールアドレスに送信できるようになった。
+[エンゲージメントレポート][25]を複数のメールアドレスに送信できるようになりました。
 
-## アクション・ベース・デリバリーで時間を指定する
+## アクションベースの配信で時間を指定する
 
-遅延アクションベースのトリガーを使用する場合、遅延後の特定の時間に送信するオプションが追加された。この機能はキャンバスとキャンペーンで利用できる。[アクションベースの配信キャンペーンの][24]送信について詳しく知る。
+遅延アクションベースのトリガーを使用する場合、遅延後の特定の時間に送信するオプションが追加された。この機能はキャンバスとキャンペーンで利用できます。[アクションベースの配信キャンペーンの][24]送信に関する詳細をご確認ください。
 
 
 [24]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/delivery_types/triggered_delivery/
diff --git a/_lang/ja/_help/release_notes/2017/may.md b/_lang/ja/_help/release_notes/2017/may.md
index 1572109d179..dcb54cef2c8 100644
--- a/_lang/ja/_help/release_notes/2017/may.md
+++ b/_lang/ja/_help/release_notes/2017/may.md
@@ -10,35 +10,35 @@ description: "この記事には2017年5月のリリースノートが含まれ
 
 ## 社内グループへのアップデート
 
-内部グループにシードグループ用の新機能を追加し、メールのテストが簡単にできるようになった。ユーザーの一括アップロード、パーソナライズされたユーザーデータを使ったリアルタイムでのテストメール送信、メッセージテンプレートの使用が可能になった。社内グループについての詳細は[こちらを][43]ご覧いただきたい。
+シードグループの内部グループに新しい機能が追加され、メールを簡単にテストできるようになりました。ユーザーの一括アップロード、パーソナライズされたユーザーデータを使ったリアルタイムでのテストメール送信、メッセージテンプレートの使用が可能になった。内部グループ[の詳細についてはこちら][43]を参照してください。
 
-## タグの更新
+## タグsへのアップデート
 
-セグメント・タグをネストして、ダッシュボードを整理できるようになった。[セグメント・タグについて][42]もっと知る。
+セグメントタグをネストして、ダッシュボードをより適切に整理できるようになりました。詳細については、[セグメントタグ][42]を参照してください。
 
 ## アプリ内メッセージの設定を更新
 
-また、アプリ内メッセージの受信拒否を特定の時間帯にカスタマイズできるようになり、顧客に対するメッセージをさらにパーソナライズできるようになった。[アプリ内メッセージの作成について][41]詳しく知る。
+アプリ内メッセージを閉じる時間をカスタマイズできるようになり、顧客へのメッセージングをより詳細にパーソナライズできるようになりました。[アプリ内メッセージs][41]の作成について詳しく説明します。
 
 ## テンプレート・ギャラリーの更新
 
-マーケティングプロセスを効率化するため、Brazeの「**テンプレート＆メディア**」タブにすべての[テンプレートと][40]画像を統合した。**テンプレート＆メディア**」ページにはリンクテンプレートもある。
+マーケティングプロセスを効率化するために、すべての[テンプレート][40]と画像を Braze の \[**テンプレートとメディア**] タブに統合しました。**テンプレート＆メディア**」ページにはリンクテンプレートもある。
 
-## アクションボタンを押す
+## プッシュアクションボタン
 
-プッシュアクションボタンを使って、ユーザーの忙しい生活を簡素化するような文脈に沿った選択肢を与えることで、エンゲージメントを高めることができる。[プッシュ通知の][39]ベストプラクティスについてもっと知る。
+プッシュアクションボタンを使って、ユーザーの忙しい生活を簡素化するような文脈に沿った選択肢を与えることで、エンゲージメントを高めることができる。[プッシュ通知 s][39] のベストプラクティスについて詳しく説明します。
 
 ## リキッド・パーソナライゼーションへの更新
 
-リキッドパーソナライゼーションは、メッセージに顧客データを簡単に挿入できるポップアップで簡素化されている。[リキッド・パーソナライゼーションについて][38]もっと知る。
+Liquid のパーソナライゼーションが簡素化され、ポップアップにより顧客データをメッセージに簡単に挿入できるようになりました。[リキッドパーソナライゼーション][38]について詳しく説明します。
 
 ## ダッシュボードUIの更新
 
-キャンペーン・ターゲティングとセグメント詳細ページのダッシュボードの一番下にある表で、自分に関連する統計だけを見ることができる。[ターゲティングとエンゲージメント・レポートの][37]詳細はこちら。
+今後は、キャンペーンのターゲティングおよびセグメント詳細ページのダッシュボードの下部にある表に、自分に関連する統計情報のみが表示されるようになり、キャンペーンの受信者とその状況をより適切に構築および追跡できるようになります。ターゲティングおよびエンゲージメントレポートについて詳しくは、[こちら][37]をご覧ください。
 
-## IPウォーミングアップのための新しいクォータ・アラート
+## IP ウォームアップの新しいクォータアラート
 
-IPウォーミングアップのスケジュールに応じて、ノルマ達成を知らせるアラートが表示されるようになった。[IP温暖化について][36]もっと知る
+IP ウォームアップスケジュールに応じた割り当てに達したときに通知するアラートが追加され、状況を見落とすことがなくなりました。[IP ウォーミング][36] について詳しく説明します。
 
 ## エンゲージメント・レポートのキャンバス・データ
 
diff --git a/_lang/ja/_help/release_notes/2017/november.md b/_lang/ja/_help/release_notes/2017/november.md
index e78c18aa43e..93ea74ff72d 100644
--- a/_lang/ja/_help/release_notes/2017/november.md
+++ b/_lang/ja/_help/release_notes/2017/november.md
@@ -3,22 +3,22 @@ nav_title: 11月
 page_order: 2
 noindex: true
 page_type: update
-description: "この記事には2017年11月のリリースノートが含まれています。"
+description: "この記事には、2017年11月のリリースノートが含まれています。"
 ---
 
 # 2017年11月
 
 ## Braze 通知設定
 
-Braze [ 通知 Preferences Center][77] を会社設定ページ内で使用すると、Braze からさまざまなアラートを受信するためにチームのユーザーを選択できます。たとえば、週単位の通知 s、キャンペーン s が送信したときの分析 レポート s、プッシュ認証エラー s などです。また、Slack などの別のチャネル[ で通知を表示するようにWebhookを設定することもできます。
+Braze [通知ユーザー設定センター][77]を \[会社の設定] ページ内で使用すると、チームのユーザーが Braze からさまざまなアラートをメールで受信できます。これには週次分析レポート、キャンペーン送信時の通知、プッシュ認証エラーなどが含まれます。また、[Slack など][78]の別のチャネルで通知を表示するように Webhook を設定することもできます。
 
-## 媒体ライブラリーのアップデート
+## メディアライブラリの更新
 
-これで、[media ライブラリー][79] に**Templates & Media** ページからアセットの複数のアセットとフォルダをアップロードしたり、アプリのタグs や複数のアセットの削除などの一括アクションs を実行したりできます。
+**\[テンプレートとメディア]** ページから[メディアライブラリ][79]に複数のアセットやアセットのフォルダをアップロードしたり、タグの適用や複数のアセットの削除などの一括アクションを実行したりできるようになりました。
 
-## キャンバスの最初のステップs のBranchリング
+## キャンバスの最初のステップに対して Branch を作成する
 
-バリアントの最初のステップにブランチを作成できるようになりました。この機能を使用すると、複数のメッセージをバリアントの最初のステップとして送信し、商談を開封してオーディエンスをさらにターゲットにすることができます。
+バリアントの最初のステップに対して Branch を作成できるようになりました。この機能を使用すると、バリアントの最初のステップとして複数のメッセージを送信し、オーディエンスをさらにターゲティングできます。
 
 
 [77]: {{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#notification-preferences
diff --git a/_lang/ja/_help/release_notes/2017/october.md b/_lang/ja/_help/release_notes/2017/october.md
index adc21b86878..6ffd59c51f0 100644
--- a/_lang/ja/_help/release_notes/2017/october.md
+++ b/_lang/ja/_help/release_notes/2017/october.md
@@ -10,17 +10,17 @@ description: "この記事には2017年10月のリリースノートが含まれ
 
 ## プッシュ通知ストーリー
 
-iOSとAndroidで、複数のページを持つ通知を[作成][74]できるようになりました。各ページには、画像、クリック動作、およびオプションのタイトルとサブタイトルが含まれます。この機能には iOS SDK 3.2.1 および Android SDK 2.2.0 が必要です。この新製品にアクセスするには、顧客成功マネージャー、アカウントマネージャーに連絡するか、[サポートチケット][support]を開封してください。
+iOSとAndroidで、複数のページを持つ通知を[作成][74]できるようになりました。各ページには、画像、クリック動作、およびオプションのタイトルとサブタイトルが含まれます。この機能には、iOS SDK 3.2.1と Android SDK 2.2.0が必要です。この新しい製品にアクセスするには、カスタマーサクセスマネージャーまたはアカウントマネージャーに連絡するか、[サポートチケット][support]を登録してください。
 
 ## Currents
 
-[Currents][75] は、データウェアハウス、ビジネスインテリジェンスツール、データ管理プラットフォームなどの技術に直接接続するための、顧客データのリアルタイムで大量のデータ接続セットを表示します。Amazon Redshift、Amplitude、およびデータ管理プラットフォームSegmentとmParticleの統合で起動します。この新製品にアクセスするには、顧客成功マネージャー、アカウントマネージャーに連絡するか、[サポートチケット][support]を開封してください。
+[Currents][75] は、データウェアハウス、ビジネスインテリジェンスツール、データ管理プラットフォームなどのテクノロジーへの事前構築済みの直接接続を使用して、顧客データに関するリアルタイムの大容量データ接続のセットを表示します。これは、Amazon Redshift、Amplitude、およびデータ管理プラットフォーム Segment と mParticle の統合を利用して起動します。この新しい製品にアクセスするには、カスタマーサクセスマネージャーまたはアカウントマネージャーに連絡するか、[サポートチケット][support]を登録してください。
 
 ## Okta シングルサインオン（2017年10月）
 
-企業はOktaを使用してBrazeアクセスをコントロールし、他のBrazeユーザーがOktaの資格情報を使用してログインすることを許可または強制することができます。この新しい製品にアクセスするには、顧客成功マネージャー、アカウントマネージャーに連絡するか、[サポートチケット][support]を開封してください。
+企業は Okta を使用して Braze へのアクセスを制御し、自社の Braze ユーザーが Okta の認証情報を使用してログインすることを許可または強制できます。この新しい製品にアクセスするには、カスタマーサクセスマネージャーまたはアカウントマネージャーに連絡するか、[サポートチケット][support]を登録してください。
 
-> 更新:Oktaへのアクセス方法に関する情報は、私たちの[2018年5月のリリースノート]({{site.baseurl}}/help/release_notes/2017/august/#may-2018)にあります。
+> 更新:Okta へのアクセス方法については、[May 2018 Release Notes]({{site.baseurl}}/help/release_notes/2017/august/#may-2018) を参照してください。
 
 ## 更新されたメールフッターの長さ制限
 
diff --git a/_lang/ja/_help/release_notes/2017/september.md b/_lang/ja/_help/release_notes/2017/september.md
index 00c3ac5fc6d..98db2070fef 100644
--- a/_lang/ja/_help/release_notes/2017/september.md
+++ b/_lang/ja/_help/release_notes/2017/september.md
@@ -10,7 +10,7 @@ description: "この記事には2017年9月のリリースノートが含まれ
 
 ## エンゲージメントレポートの新機能
 
-特定の期間にわたってキャンペーンの指標を集計するために、[エンゲージメントレポート][72]を使用できるようになりました。例えば、四半期の開封総数やキャンペーンまたはキャンバスの全期間のクリック総数をエクスポートできます。あなたがしなければならないのは:
+特定の期間にわたってキャンペーンの指標を集計するために、[エンゲージメントレポート][72]を使用できるようになりました。例えば、四半期の合計開封数や、キャンペーンまたはキャンバスの期間全体の合計クリック数をエクスポートできます。あなたがしなければならないことは:
 - データをエクスポートする期間を選択してください。
 - 定期的に1人以上の受信者に送信されるエンゲージメントレポートをスケジュールし、
 - タグに基づいてキャンペーンとキャンバスをレポートに追加します。
@@ -19,11 +19,11 @@ description: "この記事には2017年9月のリリースノートが含まれ
 
 [ユーザープロファイルページ][73]が更新されました。
 
-## ユーザーのアクションを必要とするWebプッシュ通知
+## 無視するためにユーザーアクションが必要な Web プッシュ通知
 
-Chrome Web プッシュのメッセージ終了動作を設定できるようになり、受信者がメッセージを閉じるためにメッセージと対話する必要があります。この機能には Web SDK バージョン 1.6.13 以上が必要です。
+受信者がメッセージを無視するためにメッセージの操作を必要とするよう、Chrome Web プッシュのメッセージのクローズ動作を設定できるようになりました。この機能を使用するには、Web SDK バージョン1.6.13以降が必要です。
 
-## メールのプリアヘッダー
+## メールプレヘッダーs
 
 Braze内でメールメッセージを作成する際、**送信情報**セクションにプレヘッダーを簡単に挿入できるようになりました。
 
diff --git a/_lang/ja/_help/release_notes/2018/april.md b/_lang/ja/_help/release_notes/2018/april.md
index f78ce6358e2..71d707d2e69 100644
--- a/_lang/ja/_help/release_notes/2018/april.md
+++ b/_lang/ja/_help/release_notes/2018/april.md
@@ -7,21 +7,21 @@ description: "この記事には2018年4月のリリースノートが含まれ
 ---
 # 2018年4月
 
-## webhook更新中
+## Webhook の更新が進行中
 
-5月に、BrazeはWebhookリダイレクトのセキュリティイニシアチブを実施します。今後、Webhook送信者はこれらのリダイレクトに従うことができなくなります。代わりに、リダイレクトは無限リダイレクトループを防ぐためにエラーとして扱われます。Braze はこれが誰にも影響を与えるとは考えていませんが、リダイレクトする webhook がある場合は、そのキャンペーンを再確認して編集することをお勧めします。
+5月に、Braze は Webhook リダイレクトのセキュリティイニシアチブを実施します。今後、Webhook 送信者はこれらのリダイレクトに従うことができなくなります。代わりに、リダイレクトは無限リダイレクトループを防ぐためにエラーとして扱われます。Braze はこれが誰にも影響を与えるとは考えていませんが、リダイレクトする webhook がある場合は、そのキャンペーンを再確認して編集することをお勧めします。
 
 ## CSVストレージが増加しました
 
-BrazeはCSV Xフィルターを更新し、以前の10件ではなく、ユーザーが更新された最新の100件のCSVを含むようにしました。
+Braze は CSV X フィルターを更新し、以前の10件ではなく、ユーザーが更新された最新の100件の CSV を含めるようにしました。
 
-## Androidアプリのデフォルトでアンインストール追跡がオン
+## Android アプリのアンインストール追跡がデフォルトでオン
 
-すべての新しいAndroidアプリの[アンインストール追跡][94]機能はデフォルトで「オン」になります。すべての既存のAndroidアプリでアンインストール追跡がオフになっているものは、今後「オン」に変更されます。Android アンインストール追跡は、もはやデバイスにプッシュを送信せず、他の更新やアクションは必要ありません。
+すべての新しいAndroidアプリの[アンインストール追跡][94]機能はデフォルトで「オン」になります。すべての既存のAndroidアプリでアンインストール追跡がオフになっているものは、今後「オン」に変更されます。Android のアンインストール追跡でデバイスにプッシュが送信されなくなり、ユーザー側で他の更新やアクションを実行する必要もありません。
 
 ## 更新され、改善された検索機能
 
-Brazeは、タグ付けとより優れた検索機能をBrazeに追加し、[カスタムイベントと属性][92]、テンプレートなどを検索する際に、大規模な展開を管理する体験を向上させました。
+Braze は、[カスタムイベントと属性][92]、テンプレートなどを検索しながら、Braze の大規模な展開を管理するエクスペリエンスを向上させるために、タグ付けを追加し、検索機能を改善しました。
 
 ## プッシュ通知ストーリー
 
@@ -32,7 +32,7 @@ Brazeは、タグ付けとより優れた検索機能をBrazeに追加し、[カ
 
 ## 受信トレイビジョン
 
-お客様のプラットフォームに基づいて、[メールをプレビューする][96]ことができます。サムネイルの概要ページまたは、各クライアントのHTMLレンダリングに関する問題の詳細な分析を含む大きなスクリーンショットのリストビューを通じて行うことができます。詳細については、顧客成功マネージャーまたはアカウントマネージャーにお問い合わせください。
+サムネイルの概要ページ、または大きなスクリーンショットと各クライアントの HTML レンダリングに存在する可能性のある問題のより詳細な分析を含むリストビューのいずれかを使用し、顧客のプラットフォームに基づいて[メールをプレビュー][96]できるようになりました。詳細についてはカスタマーサクセスマネージャーまたはアカウントマネージャーにお問い合わせください。
 
 
 [92]: {{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#custom-event-and-attribute-management
diff --git a/_lang/ja/_help/release_notes/2018/august.md b/_lang/ja/_help/release_notes/2018/august.md
index cd35faa5a01..5064710b75b 100644
--- a/_lang/ja/_help/release_notes/2018/august.md
+++ b/_lang/ja/_help/release_notes/2018/august.md
@@ -9,18 +9,18 @@ description: "この記事は、2018年8月のリリースノートを含んで
 
 ## iOS 12 通知群
 
-最近のiOS 12 リリースでは、アプリ版の通知のグループ化(Android 通知チャンネルに似ています) がサポートされています。[Braze では、メッセージ作成画面を使用してこのグループ化機能をiOS で利用できます。]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/#notification-groups)
+最新の iOS 12リリースでは、アプリケーションのグループ化通知 (Android 通知チャネルに似ています) がサポートされています。[Braze では、メッセージ作成画面を使用してこのグループ化機能をiOS で利用できます。]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/#notification-groups)
 
 ## プッシュストーリートリガー中
 
-プッシュストーリースライドのページクリックに基づいてs をリターゲティングする ユーザーできるようになりました。**Campaign**とのインタラクションには、追加のフィルターを使用します。
+プッシュ通知ストーリースライドの特定のページクリックに基づいて、ユーザーをリターゲティングできるようになりました。\[**キャンペーンと対話しました**] の追加フィルターを使用します。
 
 ## 匿名ユーザーからのS3およびAzureデータイベント
 
-Amazon S3 およびMicrosoft Azure にデータをエクスポートするお客様は、匿名ユーザーからのイベントを含めることができます。この機能は、新しく作成されたすべての統合で有効にデフォルトされますが、既存のすべての統合で無効のままになります。ご不明な点がございましたら、アカウントマネージャーまでお問い合わせいただくか、[サポートチケット][support]を開封してください。
+Amazon S3および Microsoft Azure にデータをエクスポートするお客様が、匿名ユーザーからのイベントを含めることができるようになりました。この機能は、新しく作成された統合ではすべてデフォルトでオンになりますが、既存の統合ではすべてオフのままになります。ご不明な点がございましたら、アカウントマネージャーまでお問い合わせいただくか、[サポートチケット][support]を開封してください。
 
-## Mixpanelコホート統合
+## Mixpanel コホートの統合
 
-Braze とMixpanel の両方の顧客が統合できるようになり、[ Mixpanel コホートをSegment フィルター s]({{site.baseurl}}/partners/insights/behavioral_analytics/mixpanel_for_currents/#mixpanel-cohort-import) としてBraze に送信します。1 回限りの手動エクスポートを設定するか、2 時間ごとにダイナミックなエクスポートを設定できます。それぞれの更新 d ユーザーはデータポイントとしてカウントされますが、ミックスパネルは前回の同期以降の変更のみを送信します。
+Braze と Mixpanel の両方のお客様が [Mixpanel コホートを統合し、セグメントフィルターとして Braze に送信]({{site.baseurl}}/partners/insights/behavioral_analytics/mixpanel_for_currents/#mixpanel-cohort-import)できるようになりました。1 回限りの手動エクスポートを設定するか、2 時間ごとにダイナミックなエクスポートを設定できます。更新された各ユーザーはデータポイントとしてカウントされますが、Mixpanel からは前回の同期以降の変更のみが送信されます。
 
 [support]: {{site.baseurl}}/braze_support/
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2018/december.md b/_lang/ja/_help/release_notes/2018/december.md
index d7ebb755c20..b9171395f74 100644
--- a/_lang/ja/_help/release_notes/2018/december.md
+++ b/_lang/ja/_help/release_notes/2018/december.md
@@ -9,7 +9,7 @@ description: "この記事には2018年12月のリリースノートが含まれ
 
 ## コンテンツブロック
 
-[コンテンツ・ブロックは]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/)、再利用可能なクロスチャネルのコンテンツを一元管理することができる。この機能にアクセスするには、Brazeアカウントの**テンプレート＆メディア**セクションの**コンテンツブロックライブラリタブに**入る。 
+[コンテンツブロック]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/)を使用すると、再利用可能なクロスチャネルコンテンツを1か所で管理できます。この機能にアクセスするには、Braze アカウントの**Templates & Media** セクションの**Content Blocks Library** タブに移動します。 
 
 コンテンツブロックを使用すると、次のことができます。
  - コンテンツブロックをヘッダーやフッターとして使用することで、メールキャンペーンに一貫性のあるルック＆フィールを作成できる。
@@ -19,4 +19,4 @@ description: "この記事には2018年12月のリリースノートが含まれ
 
 ## Gmailプロモーションツール
 
-Gmailはモバイルプロモーションタブを更新し、マーケティング担当者が件名やプリヘッダー情報だけでなく、「カード」の注釈でより多くの情報を送信できるようにした。[Gmailプロモーションツールを]({{site.baseurl}}/user_guide/message_building_by_channel/email/gmail_promotions_tab/)使えば、Brazeの製品からカードを作ることができる。
\ No newline at end of file
+Gmail でモバイルの \[プロモーション] タブが更新され、マーケターが件名やプリヘッダー情報だけでなく、「カード」の注釈をを使用してより多くの情報を送信できるようになりました。[Gmailプロモーションツール]({{site.baseurl}}/user_guide/message_building_by_channel/email/gmail_promotions_tab/)で、Brazeは弊社商品からのカード構築をお手伝いします。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2018/february.md b/_lang/ja/_help/release_notes/2018/february.md
index 1c96ba48699..5ffa1de4be2 100644
--- a/_lang/ja/_help/release_notes/2018/february.md
+++ b/_lang/ja/_help/release_notes/2018/february.md
@@ -9,8 +9,8 @@ description: "この記事には2018年2月のリリースノートが含まれ
 
 ## iOSプッシュバッジ数
 
-Brazeのプッシュコンポーザーで[バッジ数を更新][89]できるようになった。
-各プッシュ・メッセージに対して、その通知がトリガーするバッジ・カウントを指定できる。
+Brazeからのプッシュコンポーザー内で[更新バッジ数][89]が可能になりました。
+プッシュメッセージごとに、通知 トリガーするバッジ数を指定できます。
 
 ## メールアドレスを使用してAPI経由でユーザーをエクスポートする
 
@@ -19,7 +19,7 @@ Brazeのプッシュコンポーザーで[バッジ数を更新][89]できるよ
 
 ## メールテンプレートAPI
 
-[API経由でメールテンプレートを][87]作成・更新できるようになった。各テンプレートは、他のAPIコールで参照できる**email_template_idを**持つ。
+[メールテンプレートを API を介して][87]作成および更新できるようになりました。それぞれのテンプレートには、他のAPI 呼び出しで参照できる**メール_テンプレート_id** があります。
 
 ## REST APIキーのパーミッション
 
diff --git a/_lang/ja/_help/release_notes/2018/january.md b/_lang/ja/_help/release_notes/2018/january.md
index e4c661a6d4d..ecb972a2bb3 100644
--- a/_lang/ja/_help/release_notes/2018/january.md
+++ b/_lang/ja/_help/release_notes/2018/january.md
@@ -11,18 +11,18 @@ description: "この記事は、2018年1月のリリースノートを含んで
 
 [ CSS インライン化][84] を個別のメールメッセージに対してオンまたはオフに切り替えるには、** メール設定** を選択します。
 
-## 新Segment フィルターs
+## 新規セグメントフィルター
 
 次のフィルターs を使用してSegments を作成できるようになりました。
-- 受信キャンバスステップ
+- キャンバスステップを受信しました
 - 開いた/クリックしたキャンバスステップ
 - 最後に受信した特定のキャンバスステップ
 
 {% alert update %}
-2019年3月現在、`Received Canvas Step`は`Received Message from Canvas Step`に、`Last Received Specific Canvas Step`は`Last Received Message from Specific Canvas Step`に名称変更されています。
+2019年3月より、`Received Canvas Step` は `Received Message from Canvas Step` に、`Last Received Specific Canvas Step` は `Last Received Message from Specific Canvas Step` に名称変更されています。
 {% endalert %}
 
-## 機器ID を使用したユーザーs のエクスポート
+## デバイス ID を使用してユーザーをエクスポートする
 
 このエンドポイントでは、パラメータとして装置識別子を受け入れるようになりました。これにより、[匿名ユーザープロファイルs][82]をエクスポートできます。
 
diff --git a/_lang/ja/_help/release_notes/2018/july.md b/_lang/ja/_help/release_notes/2018/july.md
index 93ddda79061..3672ac1e816 100644
--- a/_lang/ja/_help/release_notes/2018/july.md
+++ b/_lang/ja/_help/release_notes/2018/july.md
@@ -9,16 +9,16 @@ description: "この記事には2018年7月のリリースノートが含まれ
 
 ## 属性の変更によるトリガー
 
-購読ステータスやカスタム属性の変更など、属性値の変更に基づいてキャンペーンやキャンバスステップをトリガーできるようになった。以前は、リアルタイムでキャンペーンをトリガーするには、BrazeにイベントやAPIトリガーを送信する必要があった。しかし、属性トリガーを使えば、イベントを追加することなく、Brazeから直接トリガーワークフローを設定できる！
+購読ステータスやカスタム属性の変更など、属性値の変更に基づいてキャンペーンとキャンバスステップをトリガーできるようになりました。以前は、リアルタイムでキャンペーンをトリガーするには、BrazeにイベントやAPIトリガーを送信する必要があった。しかし、属性トリガーを使えば、イベントを追加することなく、Brazeから直接トリガーワークフローを設定できる！
 
-この機能はまだすべての顧客で利用できるわけではない。Brazeアカウントでこの機能を有効にすることに興味がある場合は、アカウントマネージャーに連絡すること。
+この機能は、すべてのお客様が使用できるわけではありません。Brazeアカウントでこの機能を有効にすることに興味がある場合は、アカウントマネージャーに連絡すること。
 
 ## キャンバスタイムオプションの追加：現地時間
 
-あなたの会社の現地時間か、あなたのユーザーの現地時間でメッセージを送信するかを選択できるようになった。キャンバスのステップを作成する際、「スケジュール」を選択し、次に「次のステップで」または「次のステップで」を選択するだけだ。そして、"会社時間 "と "ユーザーの現地時間 "を選択できるようになる。
+メッセージの送信で、会社の現地時間またはユーザーの現地時間を選択できるようになりました。キャンバスステップの作成時に、\[スケジュール済み] を選択してから、\[次の] または \[後] を選択します。その後、\[会社時間] と \[ユーザーの現地時間] のいずれかを選択できます。
 
 ## キャンペーンのアラート
 
-Brazeのキャンペーンでは、キャンペーン内の送信数に関するパラメーターを設定できるようになり、送信数が設定した数を下回ったり上回ったりした場合に、キャンペーンに関する通知を受け取ることができるようになった。監視したいキャンペーンをクリックし、最初のブロック「**キャンペーン監視**」を確認する。**Set Up Alertを**クリックし、アラートを設定して保存する！ 
+Brazeのキャンペーンでは、キャンペーン内の送信数に関するパラメーターを設定できるようになり、送信数が設定した数を下回ったり上回ったりした場合に、キャンペーンに関する通知を受け取ることができるようになった。監視したいキャンペーンをクリックし、最初のブロック「**キャンペーン監視**」を確認する。**Set Up Alert**をクリックし、アラートを設定して保存します! 
 
 [キャンペーンアラートについて]({{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/campaign_alerts/#campaign-alerts)もっと知る。
diff --git a/_lang/ja/_help/release_notes/2018/june.md b/_lang/ja/_help/release_notes/2018/june.md
index b3f3ed37a39..967d47f6b50 100644
--- a/_lang/ja/_help/release_notes/2018/june.md
+++ b/_lang/ja/_help/release_notes/2018/june.md
@@ -11,9 +11,9 @@ description: "この記事には2018年6月のリリースノートが含まれ
 
 管理者は、会社内の他のBrazeユーザーが以前のパスワードを再利用する前に使用しなければならない新しい一意のパスワードの最小数を決定できるようになりました。これは、**会社設定**の\[認証ルール][98]パネルから、**セキュリティ設定**タブで制御できます。
 
-## キャンバスのステップのアンインストール追跡
+## キャンバスステップのアンインストール追跡
 
-キャンバスごとのアンインストール手順が統計として追跡および表示されるようになりました。
+キャンバスステップごとのアンインストールが追跡され、統計として表示できるようになりました。
 
 ![キャンバスのアンインストール追跡][1]
 
diff --git a/_lang/ja/_help/release_notes/2018/march.md b/_lang/ja/_help/release_notes/2018/march.md
index ac1e061db0d..ad3cabc3de4 100644
--- a/_lang/ja/_help/release_notes/2018/march.md
+++ b/_lang/ja/_help/release_notes/2018/march.md
@@ -9,7 +9,7 @@ description: "この記事には2018年3月のリリースノートが含まれ
 
 ## リンクテンプレート
 
-これで、エンドパラメータ をアプリする[ テンプレートを作成したり、メール メッセージ内のすべてのリンクにURI をプレエンドすることができます。すべてのリンクにGoogle Analyticsのクエリパラメータを追加したい。頑張れ！
+これで、エンドパラメータ をアプリする[ テンプレートを作成したり、メール メッセージ内のすべてのリンクにURI をプレエンドすることができます。すべてのリンクにGoogle Analyticsのクエリパラメータを追加したい。やってみましょう。
 
 ## 開発ビルド用のユニバーサルAPN証明書
 
diff --git a/_lang/ja/_help/release_notes/2018/may.md b/_lang/ja/_help/release_notes/2018/may.md
index 5120138bdc6..6991b8594e4 100644
--- a/_lang/ja/_help/release_notes/2018/may.md
+++ b/_lang/ja/_help/release_notes/2018/may.md
@@ -9,7 +9,7 @@ description: "この記事には2018年5月のリリースノートが含まれ
 
 ## Oktaシングルサインオンの更新（SSO）
 
-貴社がOktaを使用している場合、Okta管理者はOktaアプリケーションネットワークからBrazeアプリをインストールできる。次に、Okta証明書をBrazeアプリの「会社設定」ページの「セキュリティ設定」タブの適切な場所に置く必要がある。
+貴社がOktaを使用している場合、Okta管理者はOktaアプリケーションネットワークからBrazeアプリをインストールできる。次に、Okta 証明書を Braze アプリの \[会社の設定] ページにおける \[セキュリティ設定] タブの適切な場所に配置する必要があります。
 
 有効化されると、Oktaサインインボタンを使ってBrazeアプリにログインできる。
 
@@ -21,7 +21,7 @@ Brazeは、一般的なメールマーケティングのニーズに対応する
 - ありがとう
 - ニュースレター
 - 注文の確認
-- 発送確認
+- 配送確認
 - 製品
 - イベント
 - インフォメーション
diff --git a/_lang/ja/_help/release_notes/2018/november.md b/_lang/ja/_help/release_notes/2018/november.md
index 422553fe1af..dda6927ab8a 100644
--- a/_lang/ja/_help/release_notes/2018/november.md
+++ b/_lang/ja/_help/release_notes/2018/november.md
@@ -3,16 +3,16 @@ nav_title: 11月
 page_order: 3
 noindex: true
 page_type: update
-description: "この記事は、2018年11月のリリースノートを含んでいます。"
+description: "この記事には、2018年11月のリリースノートが含まれています。"
 ---
 ## 2018年11月
 
-### キャンバスエントリ 設定のウィザード
+### キャンバスエントリ設定ウィザード
 
-キャンバスUI は、タスクの失敗やエラーの発生を防ぐために簡素化されます。これで、**Campaigns**ウィザードのデザインと同様に、キャンバス設定がウィザードに表示されます。詳細については、[キャンバスを作成する]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)でステップを確認してください!
+キャンバスUI は、タスクの失敗やエラーの発生を防ぐために簡素化されます。**\[キャンペーン]** ウィザードのデザインと同様に、キャンバス設定がウィザードに表示されます。詳細については、[キャンバスを作成する]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)でステップを確認してください!
 
-この新機能はもっと欲しいですか？[入力ウィザード](https://learning.braze.com/the-new-canvas-entry-step/264889/scorm/20z5ij5ublxbk)のBrazeラーニングコースをご覧ください!
+この新機能についてより詳しく知りたい場合は、[エントリウィザード](https://learning.braze.com/the-new-canvas-entry-step/264889/scorm/20z5ij5ublxbk)に関する Brazeラーニングコースをご覧ください。
 
-### アプリ中メールモーダル CSS
+### アプリ内メッセージ Web モーダル CSS
 
 [WebモードCSSエディタ]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/create/#web-modal-css)が更新されており、新しい[CSS テンプレート s]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/in_app_message_color_templates/#css-template)でアプリ内メッセージの外観をよりコントロールすることができます。
diff --git a/_lang/ja/_help/release_notes/2018/october.md b/_lang/ja/_help/release_notes/2018/october.md
index 107b2300d8f..af3f9714537 100644
--- a/_lang/ja/_help/release_notes/2018/october.md
+++ b/_lang/ja/_help/release_notes/2018/october.md
@@ -10,10 +10,10 @@ description: "この記事には2018年10月のリリースノートが含まれ
 {% comment %}
   後でこれらを追加してください...
   インテリジェントセレクション コントロールグループ トグル
-  インテリジェントセレクションボックスには、コントロールグループの使用を[オンまたはオフに切り替える]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/multivariate_testing/#including-a-control-group)チェックボックスが追加されました。オンにすると、コントロールグループはオーディエンスサイズの20％になり、インテリジェントセレクション機能がバリアントごとのオーディエンスサイズを最適化するにつれて変化します。
+  インテリジェントセレクションボックスにチェックボックスが追加され、[コントロールグループの使用のオン/オフを切り替える]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/multivariate_testing/#including-a-control-group)ことができるようになりました。オンにすると、コントロールグループはオーディエンスサイズの20% になり、インテリジェントセレクション機能によってバリアントごとのオーディエンスサイズが最適化されると割合が変化します。
   キャンバス エントリ 設定 ウィザード (ベータ)
-  キャンバスUIは、タスクの見逃しやそれに伴うエラーを防ぐために簡素化されます。キャンバスの構成は、特にキャンペーンウィザードのデザインに似たウィザードに表示されるようになります。これは現在、段階的に展開されているため、私たちのドキュメントには反映されていません。すぐにこれについてもっと確認してください！
-  サブスクリプショングループ API (hidden)
+  キャンバスUIは、タスクの見逃しやそれに伴うエラーを防ぐために簡素化されます。\[キャンペーン] ウィザードのデザインと同様に、キャンバス設定がウィザードに表示されます。これは段階的にロールアウトされているため、現時点ではドキュメントに反映されていません。すぐにこれについてもっと確認してください！
+  サブスクリプショングループAPI (非表示)
   Brazeは、新しいGETコールを利用できるようにして、external IDまたはメールアドレスに基づいてリクエストできるようにしました。次に、そのユーザーに関連付けられているすべてのサブスクリプショングループが提供されます。
 {% endcomment %}
 
@@ -21,29 +21,29 @@ description: "この記事には2018年10月のリリースノートが含まれ
 
 **キャンペーン分析**に移動して、オーディエンスの正確な統計を計算できます。フッターの**正確な統計を計算**をクリックすると、**ターゲットユーザー**セクションに正確なオーディエンス統計が表示されます。計算する前にキャンペーンを保存する必要があります（下書きキャンペーンは下書きとして保存されます）。
 
-## Windows 8 廃止
+## Windows 8の非推奨化
 
 Brazeは2018年10月10日をもってWindows 8のサポートを終了しました。
 
 ## パートナーシップハブ
 
-Brazeプラットフォームの**統合**のリスト、統合キー、および手順を見つけることができます。
+Braze プラットフォームの \[**統合**] に、統合キーおよび手順とともに統合のリストが表示されるようになりました。
 
 ## メール分析計算
 
 Brazeは現在、メール送信パートナー（メールサービスプロバイダー (ESP)）のイベントデータを使用して、すべてのメール分析を計算しており、メール分析の精度を大幅に向上させています。このソリューションは、データの完全性を確保するために、オープンソースのデータベースソリューションであるPostgresを利用しています。
 
 {% alert important %}
-ユニークオープンとユニーククリックは、現在、メール送信パートナーによって提供される集計データに依存しています。このリリースで導入された同じインフラを使用して、これらの一意性統計を計算する作業が進行中です。
+ユニーク開封数とユニーククリック数は、現在もメール送信パートナーが提供する集計データに依存しています。このリリースで導入されたものと同じインフラを使用して、これらのユニーク統計を計算する作業が進行中です。
 {% endalert %}
 
-## 作曲者パネルのコントロール
+## 作成画面パネルのコントロール
 
-メッセージ作成画面のコントロールが更新され、アイコンに関連する文言が含まれるようになり、使いやすさとナビゲーションが向上しました。
+メッセージ作成画面のコントロールが、ユーザビリティとナビゲーションを向上させるため、アイコンに関連付けられた用語を含むように更新されました。
 
 ## Currents の Azure
 
-Brazeの顧客は、Currentsを使用して、[Azure]({{site.baseurl}}/partners/braze_currents/data_storage_integrations/partners/microsoft_azure_blob_storage/)を潜在的な統合として見ることができるようになりました。
+Currents を使用する Braze のお客様にとって、[Azure]({{site.baseurl}}/partners/braze_currents/data_storage_integrations/partners/microsoft_azure_blob_storage/) の統合が可能になりました。
 
 ## 入力フィールドの拡張
 
diff --git a/_lang/ja/_help/release_notes/2018/september.md b/_lang/ja/_help/release_notes/2018/september.md
index d90570672ad..ea7d105e64a 100644
--- a/_lang/ja/_help/release_notes/2018/september.md
+++ b/_lang/ja/_help/release_notes/2018/september.md
@@ -9,21 +9,21 @@ description: "この記事には2018年9月のリリースノートが含まれ
 
 ## iOS 12の通知グループ：その他の能力
 
-Brazeを使って[アップルの通知グループ機能に]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/#notification-groups)アクセスできるようになった！サマリー引数およびグループの追加、クリティカルアラートの利用、仮認証ユーザのフィルタリング、ユーザプロファイルの仮認証ステータスの表示ができる。
+Brazeを使って[アップルの通知グループ機能に]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/#notification-groups)アクセスできるようになった！概要引数とグループを追加したり、重要なアラートを利用したり、暫定的に認証済みのユーザーをフィルタリングしたり、ユーザープロファイルで暫定的に認証済みのステータスを表示したりできます。
 
 ## 静かな時間
 
-顧客は、キャンバスの[Quiet Hours]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-5-select-your-send-settings)(メッセージが送信されない時間)を指定できるようになりました。**キャンバスの送信設定で**「静かな時間を有効にする」にチェックを入れるだけだ。次に、ユーザーの現地時間でサイレント時間を選択し、そのサイレント時間内にメッセージがトリガーされた場合の後続のアクションを選択します。
+キャンバスに[サイレント時間]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-5-select-your-send-settings) (メッセージを送信しない時間帯) を指定できるようになりました。**キャンバスの送信設定で**「静かな時間を有効にする」にチェックを入れるだけだ。次に、ユーザーの現地時間でサイレント時間を選択し、そのサイレント時間内にメッセージがトリガーされた場合の後続のアクションを選択します。
 
 キャンペーンでは、「1日のうち特定の時間帯にこのメッセージを送信する」のではなく、「クワイエットタイム」を使用するようになった。
 
 ## 顧客を調整する
 
-[Adjustを]({{site.baseurl}}/partners/advertising_technologies/attribution/adjust/)使用しているBrazeのお客様は、Braze APIキーとBrazeインスタンスURLを確認できるようになり、Adjustプラットフォームで統合に使用できるようになった。
+[Adjust]({{site.baseurl}}/partners/advertising_technologies/attribution/adjust/) を使用している Braze のお客様が、Braze API キーと Braze インスタンス URL を確認できるようになりました。これらは、Adjust プラットフォームで統合に使用できます。
 
 ## セグメントフィルターにない
 
-顧客は、[特定のセグメントに含まれない]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#retargeting)ユーザーからセグメントを作成できるようになった。
+[特定のセグメントに含まれていない]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#retargeting)ユーザーからセグメントを作成できるようになりました。
 
 ## キャンバス受信者のCSVエクスポート
 
@@ -31,12 +31,12 @@ Brazeを使って[アップルの通知グループ機能に]({{site.baseurl}}/u
 
 ## iOS12のセグメントフィルターが暫定的に認可される
 
-指定したアプリのiOS 12で仮承認されたユーザーを見つけることができる[セグメントフィルターが]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#other)追加された。
+特定のアプリのiOS 12 で仮承認されているユーザーを見つけることができる[Segment フィルター]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#other) が追加されました。
 
 ## アプリ内メッセージ画像アップローダー
 
-アプリ内メッセージの画像アップローダーがデザインパネルからメール作成パネルに移動した。
+アプリ内メッセージ用の画像アップローダーがデザインパネルから作成パネルに移動しました。
 
 ## ユーザープロファイルページの読み取り専用パーミッション
 
-このリリース以前は、顧客は[読み取り専用権限で]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#available-limited-and-team-role-permissions)ユーザープロファイルの購読ステータスとメールアドレスを変更することができた。私たちは、`import_user` パーミッションの名前を`import_and_update_user` パーミッションに変更し、購読ステータスとメールアドレスの編集アクセスを制限した。現在、開発者が読み取り専用になりすましたり、このパーミッションを欠いている場合、購読ステータスやメールアドレスを変更することはできない。
+このリリースより前は、[読み取り専用権限]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#available-limited-and-team-role-permissions)を持つユーザープロファイルでサブスクリプションステータスとメールアドレスを変更できました。`import_user` 権限の名前を `import_and_update_user` 権限に変更し、サブスクリプションステータスとメールアドレスの編集アクセスを制限しました。現在、開発者が読み取り専用になりすましたり、このパーミッションを欠いている場合、購読ステータスやメールアドレスを変更することはできない。
diff --git a/_lang/ja/_help/release_notes/2019.md b/_lang/ja/_help/release_notes/2019.md
index c2787237263..e65d2e1aca6 100644
--- a/_lang/ja/_help/release_notes/2019.md
+++ b/_lang/ja/_help/release_notes/2019.md
@@ -3,10 +3,10 @@ page_order: 5
 nav_title: 2019
 layout: dev_guide
 noindex: true
-guide_top_header: "2019年リリースノート"
+guide_top_header: "2019 リリースノート"
 
 page_type: landing
-description: "このセクションでは、2019年のリリースノートを掲載する。"
+description: "このセクションには、2019年版のリリースノートがあります。"
 
 guide_menu_title: ""
 guide_menu_list:
diff --git a/_lang/ja/_help/release_notes/2019/april.md b/_lang/ja/_help/release_notes/2019/april.md
index f996de14bcf..867e8803ff8 100644
--- a/_lang/ja/_help/release_notes/2019/april.md
+++ b/_lang/ja/_help/release_notes/2019/april.md
@@ -8,18 +8,18 @@ description: "この記事には2019年4月のリリースノートが含まれ
 
 # 2019年4月
 
-## 百花繚乱のイベント＆フィールド
+## Currents の新しいイベントとフィールド
 
-セクションのいくつかの修正に加え、新しい \[購読イベント]({{ site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/#subscription-events) )がメッセージ・エンゲージメント・イベント・ページに追加された。 
+セクションの一部修正に加えて、新しい \[サブスクリプションイベント]({{ site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/#subscription-events) が \[メッセージエンゲージメントイベント] ページに追加されました。 
 
-Brazeから[Segment]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment_for_currents/#integration-details)および[mParticle]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents/)にサブスクリプショングループの状態変更データをエクスポートできるようになりました。また、[Mixpanel]({{site.baseurl}}/partners/insights/behavioral_analytics/mixpanel_for_currents)でインストールアトリビューションイベントもエクスポートできます。
+サブスクリプショングループの状態変更データを、Braze から [Segment]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment_for_currents/#integration-details) と [mParticle]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents/)、および [Mixpanel]({{site.baseurl}}/partners/insights/behavioral_analytics/mixpanel_for_currents) のそのイベントとインストールアトリビューションイベントにエクスポートできるようになりました。
 
-さらに、利用可能な[コンバージョンイベントに]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/#conversion-events)プロパティ`canvas_step_id` が追加された。
+また、利用可能な[コンバージョンイベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/#conversion-events)にプロパティ`canvas_step_id`が追加されました。
 
 {% alert important %}
-これらのアップデートを利用するには、Currentsコネクタの設定を編集し、使用したいイベントを有効にする必要がある。ご不明な点があれば、担当のアカウント・マネージャーにお問い合わせいただきたい。
+これらの更新を活用するには、Currents コネクターの設定を編集し、使用するイベントを有効にする必要があります。ご不明な点があれば、担当のアカウント・マネージャーにお問い合わせいただきたい。
 {% endalert %}
 
-## 購読グループのアーカイブ
+## サブスクリプショングループのアーカイブ
 
-[購読グループをアーカイブ]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#archiving-groups)できるようになった！アーカイブされた購読グループは編集できず、セグメントフィルターに表示されなくなる。 メール、キャンペーン、キャンバスでセグメントフィルターとして使用されているグループをアーカイブしようとすると、エラーメッセージが表示され、そのグループの使用をすべて削除するまでアーカイブできない。
+これで[アーカイブサブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#archiving-groups)が可能になりました!アーカイブされたサブスクリプショングループは編集できず、セグメントフィルターに表示されなくなります。 メール、キャンペーン、キャンバスでセグメントフィルターとして使用されているグループをアーカイブしようとすると、エラーメッセージが表示され、そのグループの使用をすべて削除するまでアーカイブできない。
diff --git a/_lang/ja/_help/release_notes/2019/august.md b/_lang/ja/_help/release_notes/2019/august.md
index 91e2c2a26f6..88c5fbfb3f8 100644
--- a/_lang/ja/_help/release_notes/2019/august.md
+++ b/_lang/ja/_help/release_notes/2019/august.md
@@ -3,12 +3,12 @@ nav_title: 8月
 page_order: 5
 noindex: true
 page_type: update
-description: "この記事は、2019年8月のリリースノートを含んでいます。"
+description: "この記事には、2019年8月のリリースノートが含まれています。"
 ---
 
 # 2019年8月
 
-## レポートsの運動内容
+## レポートのキャンペーン詳細
 
 キャンペーン パフォーマンス レポートにはキャンペーンの詳細が表示されるので、レポートの設定中に選択した配信、オーディエンス、またはコンバージョン設定を確認するためにキャンペーンに戻る必要はありません。
 
@@ -19,15 +19,15 @@ description: "この記事は、2019年8月のリリースノートを含んで
 管理できるようになりました([create]({{site.baseurl}}/api/endpoints/email_templates/#create-content-block),[list available]({{site.baseurl}}/api/endpoints/email_templates/#list-available-content-blocks),[get information]({{site.baseurl}}/api/endpoints/email_templates/#see-content-block-information)) メール コンテンツブロックをAPI で管理できます!
 
 {% alert update %}
-この機能は、一時的に限られた可用性で使用されます。詳しくは、Braze アカウントマネージャーにお問い合わせください。
+この機能は一時的に利用が制限されています。詳しくは、Braze アカウントマネージャーにお問い合わせください。
 {% endalert %}
 
 ## カスタムメール 配信停止ランディングページの更新
 
 デフォルトの[カスタムメール 配信停止ページ]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#custom-unsubscribe-landing-page)は更新dで、より洗練された、よりモダンな外観です。
 
-## iOSSDK:ノッチ付き電話サポートの改善
+## iOS SDK:ノッチ付きスマートフォンに対するサポートの改善
 
-"notched" 機器(たとえば、iPhone X、Pixel 3XL) でのアプリ内メッセージ s のサポートを改善しました。フルスクリーンメッセージは、ステータスバーを覆いながら、すべての電話機の画面全体に表示されるように拡張されます。
+「ノッチ付き」デバイス (iPhone X、Pixel 3XL など) でのアプリ内メッセージのサポートが改善されました。フルスクリーンメッセージが、ステータスバーに重なり、あらゆるスマートフォンの画面全体に拡大されるようになりました。
 
-Braze Docsでは、この変更をまだ反映している更新はあまり見られませんが、途中です!
+Braze Docs では、この変更が反映されている更新はあまり見られませんが、間もなく反映される予定です。
diff --git a/_lang/ja/_help/release_notes/2019/december.md b/_lang/ja/_help/release_notes/2019/december.md
index 01804f677f6..8f99be09e8f 100644
--- a/_lang/ja/_help/release_notes/2019/december.md
+++ b/_lang/ja/_help/release_notes/2019/december.md
@@ -7,6 +7,6 @@ description: "この記事には2019年12月のリリースノートが含まれ
 ---
 # 2019年12月
 
-12月のコードフリーズのため、12月のリリースノートはない。 
+12月のコードフリーズにより、12月のリリースノートはありません。 
 
 さらなるアップデートについては、来月のリリースノートをチェックしてほしい。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2019/february.md b/_lang/ja/_help/release_notes/2019/february.md
index 4a4c483922e..f6bf6a8a0a3 100644
--- a/_lang/ja/_help/release_notes/2019/february.md
+++ b/_lang/ja/_help/release_notes/2019/february.md
@@ -3,19 +3,19 @@ nav_title: 2月
 page_order: 11
 noindex: true
 page_type: update
-description: "この記事には2019年2月のリリースノートが含まれている。"
+description: "この記事には、2019年2月のリリースノートが含まれています。"
 ---
 # 2019年2月
 
-## 電子メール購読グループ
+## メールサブスクリプショングループ
 
-[サブスクリプショングループは]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#subscription-groups)、上記の[グローバルサブスクリプションステートから]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/)さらにオーディエンスを絞り込むことができるセグメントフィルタである。これらのグループは、エンドユーザーにより詳細な購読オプションを提示する能力を提供する。
+[サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#subscription-groups)は、上記の[グローバルサブスクリプションの状態]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/)からさらにオーディエンスを絞り込むことができるセグメントフィルタです。これらのグループを使用すると、より詳細なサブスクリプションオプションをエンドユーザーに提示できます。
 
-例えば、複数のカテゴリのメールキャンペーンを配信している場合、[メールプレファレンスセンターを](#email-preference-center)利用することで、1つのページから一括で購読または購読解除を行うことができる。
+例えば、複数のカテゴリのメールキャンペーンを送信する場合は、[メールユーザー設定センター](#email-preference-center)を使用することで、1つのページから一括で配信登録または配信停止するオプションを顧客に登録できます。
 
-[Subscription Group REST APIを]({{site.baseurl}}/developer_guide/rest_api/subscription_group_api/)使用して、Brazeダッシュボード上の**Subscription Group**ページに保存したSubscription Groupをプログラムで管理する。
+[サブスクリプショングループ REST API]({{site.baseurl}}/developer_guide/rest_api/subscription_group_api/) を使用して、Braze ダッシュボードの **\[サブスクリプショングループ]** ページに保存したサブスクリプショングループをプログラムで管理します。
 
-## Eメール・プリファレンス・センター
+## メールユーザー設定センター
 
-[メールプレファレンスセンターは]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#email-preference-center)、どのユーザーが特定のニュースレターグループを受信するかを管理する簡単な方法である。あなたが作成した各購読グループは、プリファレンスセンターのリストに追加される。プリファレンス・センターの名前をクリックすると、インタラクティブなプレビューが表示される。
+[メールユーザー設定センター]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#email-preference-center)は、特定のグループのニュースレターを受信するユーザーを簡単に管理できる手段です。作成した各サブスクリプショングループは、ユーザー設定センターのリストに追加されます。ユーザー設定センターの名前をクリックすると、インタラクティブなプレビューが表示されます。
 
diff --git a/_lang/ja/_help/release_notes/2019/january.md b/_lang/ja/_help/release_notes/2019/january.md
index b5f7f3105a7..ee2f81293ff 100644
--- a/_lang/ja/_help/release_notes/2019/january.md
+++ b/_lang/ja/_help/release_notes/2019/january.md
@@ -9,13 +9,13 @@ description: "この記事には2019年1月のリリースノートが含まれ
 
 新年を迎えました！
 
-## プッシュTTL (TTL)
+## Push time to live (TTL)
 
 アカウント内の**設定の管理**で、[プッシュTTL設定]({{site.baseurl}}/user_guide/administrative/app_settings/push_ttl_settings/)タブをクリックして、デバイスがオフラインの場合に再送を試みる時間の長さを管理します。
 
 ## コネクテッドコンテンツIPホワイトリスト
 
-Brazeは、内部チームによる多数のインフラのアップグレードにより、すべてのクラスターでコネクテッドコンテンツのIPホワイトリスト化を提供できるようになったことを発表できることを嬉しく思います。将来的には、非EUクラスターに追加のIPを追加する予定です。
+Brazeは、内部チームによる多数のインフラのアップグレードにより、すべてのクラスターでコネクテッドコンテンツのIPホワイトリスト化を提供できるようになったことを発表できることを嬉しく思います。今後、EU 以外のクラスターの IP を追加する予定です。
 
 ## キャンバス遅延
 
diff --git a/_lang/ja/_help/release_notes/2019/july.md b/_lang/ja/_help/release_notes/2019/july.md
index ea82cc1b5c1..8e33012983a 100644
--- a/_lang/ja/_help/release_notes/2019/july.md
+++ b/_lang/ja/_help/release_notes/2019/july.md
@@ -3,34 +3,34 @@ nav_title: 7月
 page_order: 6
 noindex: true
 page_type: update
-description: "この記事は、2019年7月のリリースノートを含んでいます。"
+description: "この記事には、2019年7月のリリースノートが含まれています。"
 ---
 
 # 2019年7月
 
 {% alert update %}
-Brazeは今月、2回(その通り-**2回**)の商品発売がありました!最新のリリースが最上位に記録され、前のページ[ がさらにこのページ](#earlier-this-month) から始まります!
+Braze には今月、**2回**の製品リリースサイクルがありました。このページでは、最新のリリースが一番上に記載され、それより前のリリースは[その下に記載されています](#earlier-this-month)。
 {% endalert %}
 
 ## SAML/SSO
 
-[シングルサインオン]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/) (SSO) は、企業がBraze ダッシュボードへのアクセスをコントロールするための安全で集中的な方法を提供します。要するに、1 組の認証情報 s を使用して、Braze を含むさまざまなアプリアプリケーションにアクセスできます。
+[シングルサインオン]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/) (SSO) は、Braze ダッシュボードへのアクセスを制御する安全かつ一元化された方法を企業に提供します。つまり、1 組の認証情報を使用して、Braze を含むさまざまなアプリケーションにアクセスできます。
 
-OAuth 2.0 サポート を使用した[Google サインインに加えて、企業はSecurity Assertion Markup Language (SAML) サポートのSSO を希望しています。これにより、[Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/) および[Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/) を含む大規模なID プロバイダ(IdP) とシームレスに統合できます。これは、最新の業界標準(SAML 2.0) に対応しています。
+[OAuth 2.0 サポートを使用した Google サインイン](https://developers.google.com/identity/protocols/OAuth2)に加えて、企業は Security Assertion Markup Language (SAML) サポートを使用した SSO を希望しています。これにより、[Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/) および[Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/) を含む大規模なID プロバイダ(IdP) とシームレスに統合できます。これは、最新の業界標準(SAML 2.0) に対応しています。
 
-Brazeサポート:
+Braze は以下をサポートしています。
 - [OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/)
 - [Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/)
 - [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/)
 
-## Adjust行事API キー番組
+## イベント API キー表示を調整する
 
-このAPI キーを顧客 s にアクセスできるようにするために、更新 d Adjust のパートナページがあります。
+Adjust のパートナーページを更新し、お客様がこの API キーにアクセスできるようにしました。
 
 ## 新パートナーズ
 
-いくつかの新しいパートナーが私たちのAlloysプログラムに参加し、私たちのDocsに追加されました！こんにちは。
-- [ファイブトラン]({{site.baseurl}}/partners/fivetran/)
+いくつかの新しいパートナーが Alloys プログラムに参加し、ドキュメントに追加されました。新しいパートナーは以下のとおりです。
+- [FiveTran]({{site.baseurl}}/partners/fivetran/)
 - [Talon.One]({{site.baseurl}}/partners/talonone/)
 - [Voucherify]({{site.baseurl}}/partners/voucherify/)
 
@@ -38,7 +38,7 @@ Brazeサポート:
 
 拡張キャンペーンの詳細が、**キャンペーン**ページの。..wait it...**キャンペーン詳細**セクションに表示されます!
 
-## Segment s & amp; Canvas では地雷のみを表示します
+## セグメントとキャンバスで自分のもののみを表示する
 
 "Show Only Mine" **Campaigns**ページのチェックフィルターは、非常に人気があることが証明されています。その結果、キャンバスとセグメントリストにもこのオプションを追加しています!
 
@@ -62,7 +62,7 @@ Braze ユーザープロファイル s とユーザー 検索で表示されて
 
 外部サーバへの接続されたコンテンツコールは、カードが実際に送信されたときにアプリします。カードがユーザによって表示されたときではありません。メールと同様に、ダイナミックなの内容は、実際に表示されるときではなく、送信時に計算され決定されます。
 
-## Null & quot; 返信先" 住所
+## Null "; 返信先" 住所
 
 顧客は、メールメッセージの" 返信先" address に`null` 値を設定できるようになりました。Braze の** メール Settings** ページから、または[API]({{site.baseurl}}/api/endpoints/messaging/#email-object-specification) を使用して設定します。 使用すると、リストされた"From"アドレスに返信が送信されます。 "From"address フィールドを`dan@emailaddress.com`としてパーソナライズできるようになりました。そして、あなたの顧客sは直接Danに返信することができます。
 
diff --git a/_lang/ja/_help/release_notes/2019/june.md b/_lang/ja/_help/release_notes/2019/june.md
index 822f3c519fb..29349f89053 100644
--- a/_lang/ja/_help/release_notes/2019/june.md
+++ b/_lang/ja/_help/release_notes/2019/june.md
@@ -8,12 +8,12 @@ description: "この記事には2019年6月のリリースノートが含まれ
 
 # 2019年6月
 
-## スノーフレーク・パートナーシップ
+## Snowflake提携
 
 BrazeはSnowflakeとのパートナーシップを発表できることを誇りに思う！
 
-Snowflakeは、すべてのデータとすべてのユーザーのために構築されたSQLクラウドデータウェアハウスである。Snowflakeのユニークで特許取得済みのアーキテクチャにより、すべてのデータを簡単に収集し、迅速な分析を可能にし、すべてのユーザーに対してデータ主導型の洞察を導き出すことができる。
+Snowflake は、あらゆるデータ、あらゆるユーザーのために特別に設計された SQL クラウドデータウェアハウスです。Snowflake 独自の特許取得済みアーキテクチャにより、すべてのデータを集約し、迅速な分析を可能にし、すべてのユーザーにデータドリブン型のインサイトを提供することが容易になります。
 
-Brazeは、SnowflakeのData Exchangeを活用することで、存在感を高め、新規顧客を見つけ、拡大を続けるSnowflakeの顧客基盤を通じてリーチを拡大する。
+Brazeは、Snowflake の Data Exchange を活用して、プレゼンスを構築し、新規顧客を見つけ、成長を続ける Snowflake の顧客基盤を通じてリーチを拡大します。
 
-このパートナーシップの詳細については、[こちらか](https://www.braze.com/perspectives/article/snowflake-partner-announcement) [ドキュメントを]({{site.baseurl}}/partners/snowflake/)ご覧いただきたい。
+このパートナーシップについて詳しくは、[こちら](https://www.braze.com/perspectives/article/snowflake-partner-announcement)または [Braze のドキュメント]({{site.baseurl}}/partners/snowflake/)をご覧ください。
diff --git a/_lang/ja/_help/release_notes/2019/march.md b/_lang/ja/_help/release_notes/2019/march.md
index 5e2c2a473c9..31331886ba2 100644
--- a/_lang/ja/_help/release_notes/2019/march.md
+++ b/_lang/ja/_help/release_notes/2019/march.md
@@ -10,14 +10,14 @@ description: "この記事には2019年3月のリリースノートが含まれ
 
 ## アプリ内メッセージ - 第3世代
 
-Brazeは、最新のUXおよびUIのベストプラクティスに準拠するために、アプリ内メッセージの外観と操作性を改善したことを誇りに思います。最新のインアプリメッセージでは、ユーザーがメッセージと対話することが期待できます:
+Brazeは、最新のUXおよびUIのベストプラクティスに準拠するために、アプリ内メッセージの外観と操作性を改善したことを誇りに思います。最新のアプリ内メッセージでは、ユーザーによるメッセージの操作に関して以下の改善が予定されています。
 - より大きなフォントサイズ
 - 洗練された間隔
-- 新しいクローズ`x`資産
+- 新しい閉じる `x` アセット
 - すべてのメッセージタイプに対するレスポンシブな動作が改善され、ビューポートにより適合するようになりました
 - ボタンの境界線を使用して、ボタン間のカスタムコントラストを作成する
 
-私たちの[新しいアプリ内メッセージ]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/overview/)は、ユーザーとのやり取りを良好からアプリ素晴らしいものにします！
+[新しいアプリ内メッセージ]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/overview/)は、ユーザーとのインタラクションを劇的に改善します。
 
 ![全画面表示の動作]({% image_buster /assets/img/full-screen-behavior.gif %}){: style="border:0px;"}
 
@@ -27,14 +27,14 @@ Brazeは、最新のUXおよびUIのベストプラクティスに準拠する
 
 その後、準備完了です！
 
-## コンテンツブロックアーカイブ更新
+## コンテンツブロックアーカイブの更新
 
 これで[コンテンツブロック]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/#archiving-content-blocks)をアーカイブおよびアーカイブ解除できます。
 
-## Inkitパートナーの追加
+## パートナーとしての Inkit の追加
 
 [Inkit]({{site.baseurl}}/partners/inkit/) を事前に設計された Webhook テンプレートとして使用するか、新しい Webhook キャンペーンを作成できます。
 
 ## Google Cloud Storage
 
-[Google Cloud Storage]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/google_cloud_storage_for_currents/) はベータ版ではなくなりました！Brazeは、Google Cloud StorageがBrazeプラットフォーム内の関心のある顧客に利用可能であることを発表できることを誇りに思います。Brazeアカウントの**Technology Partners**に移動し、Google Cloud Storageを検索します。
+[Google Cloud Storage]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/google_cloud_storage_for_currents/) はベータ版ではなくなりました！関心のあるお客様が、Braze プラットフォーム内で Google Cloud Storage をご利用いただけるようになりました。Brazeアカウントの**Technology Partners**に移動し、Google Cloud Storageを検索します。
diff --git a/_lang/ja/_help/release_notes/2019/may.md b/_lang/ja/_help/release_notes/2019/may.md
index 8a53dda01f2..b8b21e5d95a 100644
--- a/_lang/ja/_help/release_notes/2019/may.md
+++ b/_lang/ja/_help/release_notes/2019/may.md
@@ -10,13 +10,13 @@ description: "この記事には2019年5月のリリースノートが含まれ
 
 ## コンテンツカードによって促進された
 
-コンテンツカードは、顧客のアプリおよびWebエクスペリエンス内に表示される永続的なコンテンツです。
+コンテンツカードは、お客様のアプリおよび Web 環境内に表示される永続的なコンテンツです。
 
-コンテンツカードを使用すると、顧客の体験を中断することなく、彼らが愛するアプリ内で高度にターゲットされたダイナミックなリッチコンテンツのストリームを送信できます。または、メールやプッシュ通知などの他のチャネルとコンテンツカードを組み合わせて、一貫したマーケティング戦略を実現できます。
+コンテンツカードを使用すると、顧客のエクスペリエンスを中断することなく、顧客が選択したアプリ内で、高度にターゲットを絞ったリッチコンテンツの動的なストリームを送信できます。または、メールやプッシュ通知などの他のチャネルとコンテンツカードを組み合わせて、一貫したマーケティング戦略を実現できます。
 
 ![コンテンツカードフィード]({% image_buster /assets/img/cc-feed.png %}){: height="50%" width="50%"}
 
-さらに、コンテンツカードは、カードのピン留め、カードの却下、APIベースの配信、カスタムカードの有効期限、カードの分析など、よりパーソナライズされた機能をサポートしています。
+また、コンテンツカードは、カードのピン留め、カードの却下、API ベースの配信、カスタムカードの有効期限、カード分析など、よりパーソナライズされた機能をサポートします。
 
 通知センター、ホームページフィード、プロモーションフィードを作成するために使用します。
 
@@ -25,15 +25,15 @@ description: "この記事には2019年5月のリリースノートが含まれ
 - Android :2.6.0以降
 - Web:2.2.0以降
 
-[コンテンツカードの詳細はこちらをご覧ください！]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/overview/)
+[コンテンツカードについて詳しくはこちら]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/overview/)
 
 {% alert update %}
-コンテンツカードのCurrentsおよびコンテンツカードのAPIドキュメントは今週後半にリリースされます。お楽しみに！
+Currents のコンテンツカードとコンテンツカードの API ドキュメントは、今週後半にリリースされる予定です。お楽しみに！
 {% endalert %}
 
 ## Rokuプラットフォームの追加
 
-Brazeは私たちの機能に新しいチャネルを追加しました！新しいチャネルに拡大することで、視聴行動を理解することでデータを充実させたり、関連するすべてのチャネルで消費者に意味のある体験を提供したりすることができます。
+Brazeは私たちの機能に新しいチャネルを追加しました！新しいチャネルに拡大することで、お客様は表示行動を理解してデータを充実させたり、関連するすべてのチャネルを通じて消費者に有意義な体験を提供したりできるようになります。
 
 Rokuデバイスからデータを[取得して]({{site.baseurl}}/developer_guide/platform_integration_guides/roku/initial_sdk_setup/)、データの強化およびカスタムイベントのトラッキングが可能になりました。
 
@@ -43,29 +43,29 @@ Rokuデバイスからデータを[取得して]({{site.baseurl}}/developer_guid
 
 ## Jampp テクノロジーパートナー ドキュメント
 
-Jamppは、モバイル顧客の獲得とリターゲティングのためのパフォーマンスマーケティングプラットフォームです。それは、消費者が初めて、またはより頻繁に購入するように促す個人的で関連性のある広告を表示することによって、広告主の収益を生み出すために、行動データと予測およびプログラム技術を組み合わせています。
+Jamppは、モバイル顧客の獲得とリターゲティングのためのパフォーマンスマーケティングプラットフォームです。これは、行動データと予測およびプログラム技術を組み合わせて、消費者が初めて購入する、またはより頻繁に購入するように促す個人的な関連性のある広告を表示することで、広告主のための収益を生み出す。
 
-Brazeの顧客は、BrazeのWebhookチャネルを構成してイベントをJamppにストリームすることで、[Jamppと統合]({{site.baseurl}}/partners/advertising_technologies/retargeting/jampp/)できます。その結果、顧客はモバイル広告エコシステム内でJamppを使用してリターゲティングの取り組みにより豊富なデータセットを追加することができます。
+Braze のお客様は、Braze Webhook チャネルを構成してイベントを Jampp にストリーミングすることで、[Jampp と統合]({{site.baseurl}}/partners/advertising_technologies/retargeting/jampp/)できます。その結果、顧客はモバイル広告エコシステム内でJamppを使用してリターゲティングの取り組みにより豊富なデータセットを追加することができます。
 
 ## アプリ内メッセージ用プラットフォームピッカー
 
-アプリ内メッセージの送信先と、それらが構築されるプラットフォームを選択するのが簡単になりました。このステップはキャンペーン作成プロセスで強調されています。
+キャンペーン作成プロセスのこのステップを強調するプラットフォームピッカーを使用することで、アプリ内メッセージの送信先と対象プラットフォームの選択が簡単になりました。
 
-![プラットフォーム Picker][1]
+![プラットフォームピッカー][1]
 
-## ディスパッチID Currents フィールド メール
+## メールのディスパッチ ID Currents フィールド
 
 {% alert update %}
 キャンバスとキャンペーンの間で`dispatch_id`の動作が異なるのは、Brazeがキャンバスステップ（スケジュール可能なエントリステップを除く）を「スケジュールされた」場合でもトリガーイベントとして扱うためです。キャンバスやキャンペーンでの[`dispatch_id`動作]({{site.baseurl}}/help/help_articles/data/dispatch_id/)について詳しく学びましょう。
 
-_更新 noted in August 2019._
+_更新は2019年8月に記録されました。_
 {% endalert %}
 
-私たちのCurrents機能をさらに強化するために、すべてのコネクタタイプにわたるCurrentsメールイベントに`dispatch_id`をフィールドとして追加しています。
+Currents の機能を継続的に強化する取り組みの一環として、すべてのコネクタータイプで Currents のメールイベントにフィールドとして `dispatch_id` を追加します。
 
-`dispatch_id` は、Braze プラットフォームから送信される各送信または配信に対して生成される一意の ID です。
+`dispatch_id` は、Braze プラットフォームからの送信 (ディスパッチ) ごとに生成される一意の ID です。
 
-すべての顧客がスケジュールされたメッセージを受け取ると同じ`dispatch_id`を受け取りますが、アクションベースまたはAPIトリガーのメッセージを受け取る顧客は、メッセージごとに一意の`dispatch_id`を受け取ります。`dispatch_id`フィールドにより、繰り返し行われるキャンペーンのどのインスタンスがコンバージョンの原因であるかを特定できるため、どのタイプのキャンペーンがビジネス目標の達成に役立っているかについての洞察と情報を提供します。
+スケジュール済みのメッセージを受信したすべての顧客に同じ `dispatch_id` が割り当てられますが、アクションベースメッセージや API トリガーメッセージを受信した顧客にはメッセージごとに固有の `dispatch_id` が割り当てられます。`dispatch_id` フィールドを使用すると、定期的なキャンペーンのどのインスタンスがコンバージョンを担当しているかを識別できるため、より多くのインサイトと、どのタイプのキャンペーンが業務目標の達成に役立っているかを確認できます。
 
 ## 「自分のものだけ表示」キャンペーンの並べ替え機能
 
@@ -77,20 +77,20 @@ _更新 noted in August 2019._
 
 `users/delete`エンドポイントを使用して、エイリアスでユーザーを[削除することができます]({{site.baseurl}}/api/endpoints/user_data/#user-delete-request)！
 
-## メールのクリックとオープンのユニークな計算
+## メールクリック数と開封数のユニーク計算
 
-メールのユニーククリックとユニークオープンは、ユーザーごとに7日間の期間でキャプチャされ表示され、各`dispatch_id`ごとにその7日間のウィンドウ内で1カウント増加します。
+メールのユニーククリック数とユニーク開封数が、ユーザーごとに7日間の期間で取得され、表示されるようになりました。この7日間の期間内において、各 `dispatch_id` でカウントが1ずつ増加します。
 
-`dispatch_id`を使用すると、各メッセージの真のユニーク開封またはユニーククリック数を反映する定期的なメッセージが可能になります。顧客は、このデータを簡単に照合できるようになります。現在、`dispatch_id`がCurrentsで利用可能です。
+`dispatch_id` を使用すると、繰り返しメッセージに各メッセージの実際のユニーク開封数またはユニーククリック数を反映させることができます。Currents で `dispatch_id` を利用できるようになったため、このデータを簡単に照合できるようになります。
 
-Mailjetを使用しているユーザーは、以前の一意性の期間が30日以上だったため、これらの数値の急増を目にするでしょう。3週間前にこの変更について知らされているべきでした。 SendGridの顧客は違いを感じないはずです。
+Mailjet も使用しているユーザーは、以前のユニーク時間枠が30日間を超えていたため、これらの数値が急増します。この変更については3週間前にお知らせしておくべきでした。 SendGridの顧客は違いを感じないはずです。
 
 これらの更新された用語は、当社の[レポートメトリクス用語集]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics/)で検索できます。
 
 {% alert update %}
 キャンバスとキャンペーンの間での`dispatch_id`の動作は異なります。なぜなら、Brazeはキャンバスのステップ（スケジュール可能なエントリステップを除く）を「スケジュールされた」場合でもトリガーイベントとして扱うからです。 [キャンバスとキャンペーンにおける[`dispatch_id`の動作]({{site.baseurl}}/help/help_articles/data/dispatch_id/)について詳しくはこちらをご覧ください。]
 
-_更新 noted in August 2019._
+_更新は2019年8月に記録されました。_
 {% endalert %}
 
 
@@ -102,6 +102,6 @@ _更新 noted in August 2019._
 
 最もエンゲージされたチャネルフィルターは、選択されたメッセージングチャネルが「最適な」チャネルであるオーディエンスの一部を選択します。この場合、「ベスト」とは「ユーザーの履歴を考慮した場合、エンゲージメントの可能性が最も高い」という意味です。メール、Web プッシュ、またはモバイルプッシュ（利用可能なモバイルOSやデバイスを含む）をチャネルとして選択できます。
 
-この新しいフィルターを私たちの\[セグメンテーションフィルターライブラリー]({{site.baseurl }}/user_guide/engagement_tools/segments/segmentation_filters/).でチェックしてください
+この新しいフィルターについては \[セグメンテーションフィルターライブラリ]({{site.baseurl }}/user_guide/engagement_tools/segments/segmentation_filters/). で確認してください。
 
 [1]: {% image_buster /assets/img/iam_platforms.gif %}
diff --git a/_lang/ja/_help/release_notes/2019/november.md b/_lang/ja/_help/release_notes/2019/november.md
index 43afc1f6da5..a0cab942b50 100644
--- a/_lang/ja/_help/release_notes/2019/november.md
+++ b/_lang/ja/_help/release_notes/2019/november.md
@@ -8,11 +8,11 @@ description: "この記事には2019年11月のリリースノートが含まれ
 
 # 2019年11月
 
-もっと来るよ！今月後半にまたチェックして、さらに更新情報をお待ちください！
+今後も追加予定です。今月後半にまたチェックして、さらに更新情報をお待ちください！
 
 ## Intelligence Suite
 
-Brazeの[インテリジェンススイート]({{site.baseurl}}/user_guide/intelligence/)は、データに基づく洞察で意思決定を自動化するのに役立ちます。配信時間から多変量テストまで、ブランドはこれらのツールと機能を使用して、スケールで最適化されるダイナミックなクロスチャネルの体験を作成できます。<br> <br> インテリジェンススイートは、3つの主要な機能で構成されています:[インテリジェントタイミング]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_timing/), [インテリジェントチャネル]({{site.baseurl}}/user_guide/intelligence/intelligent_channel/), and [インテリジェントセレクション]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_selection/).
+Brazeの[インテリジェンススイート]({{site.baseurl}}/user_guide/intelligence/)は、データに基づく洞察で意思決定を自動化するのに役立ちます。配信時間から多変量テストまで、ブランドはこれらのツールと機能を使用して、大規模に最適化されるダイナミックなクロスチャネルのエクスペリエンスを構築できます。<br> <br> Intelligence Suite は、[インテリジェントタイミング]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_timing/), [インテリジェントチャネル]({{site.baseurl}}/user_guide/intelligence/intelligent_channel/), and [インテリジェントセレクション]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_selection/).
 
 {% alert note %}
 「インテリジェンススイート」は、以前「最もエンゲージされたチャネル」、「インテリジェントタイミング」、および「多変量およびABテスト」として知られていた機能の改訂およびグループ化です。
@@ -20,7 +20,7 @@ Brazeの[インテリジェンススイート]({{site.baseurl}}/user_guide/intel
 
 ## アプリ内メッセージのダークモードテーマ
 
-iOS 13とAndroid 10の両方が、携帯電話のカラーテーマを「ダークモード」に変更できる設定を導入しました。この機能に合わせて、Brazeは[アプリ内メッセージのダークモード]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/dark-mode/)を導入しました！この機能を使用すると、「ライト」と「ダークテーマ」のアプリ内メッセージを作成できます。デバイスに「ダークモード」が有効になっている場合、メッセージは選択したダークモードテーマを表示します。
+iOS 13とAndroid 10の両方が、携帯電話のカラーテーマを「ダークモード」に変更できる設定を導入しました。この機能に合わせて、Brazeは[アプリ内メッセージのダークモード]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/dark-mode/)を導入しました！この機能を使用すると、「ライト」と「ダークテーマ」のアプリ内メッセージを作成できます。デバイスで「ダークモード」が有効になっている場合、メッセージは選択したダークモードテーマで表示されます。
 
 <img src="{% image_buster /assets/img_archive/iam-dark-mode.gif %}" style="width:100%;max-width:800px;" />
 
diff --git a/_lang/ja/_help/release_notes/2019/october.md b/_lang/ja/_help/release_notes/2019/october.md
index 70e6a040f64..2ac03f8abb3 100644
--- a/_lang/ja/_help/release_notes/2019/october.md
+++ b/_lang/ja/_help/release_notes/2019/october.md
@@ -8,18 +8,18 @@ description: "この記事には2019年10月のリリースノートが含まれ
 
 # 2019年10月
 
-## キャンバスのバリアント分析の改善
+## 改良されたキャンバスバリアント分析
 
-Canvasには、各バリアントのパフォーマンスを見るための新しく改良されたアナリティクスがある。特にコンバージョンイベントや信頼度に関する新しい指標や、セルのコピー、API ID、結果のダウンロード（`.csv` ）といった新機能がある。[改良されたキャンバスのバリアント分析について]({{site.baseurl}}/user_guide/engagement_tools/canvas/get_started/measuring_and_testing_with_canvas_analytics/#performance-breakdown-by-variant)もっと読む。
+「キャンバス」には、バリアントs のそれぞれのパフォーマンスを表示するための分析が新しく改良されています。特にコンバージョンイベントや信頼度に関する新しい指標や、セルのコピー、API ID、結果のダウンロード（`.csv` ）といった新機能がある。改良されたキャンバスバリアント分析について詳しくは、[こちら]({{site.baseurl}}/user_guide/engagement_tools/canvas/get_started/measuring_and_testing_with_canvas_analytics/#performance-breakdown-by-variant)をご覧ください。
 
 ## SMS
 
-Brazeは現在、キャンペーン、キャンバス、[カレントで]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/)SMSを提供している！詳しくは、[セットアップガイドと]({{site.baseurl}}/user_guide/onboarding_with_braze/sms_setup/) [SMS送信ガイドを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/)ご覧いただきたい！
+Brazeは現在、SMSにキャンペーンs、キャンバス、および[currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/)を提供しています!詳しくは、[セットアップガイドと]({{site.baseurl}}/user_guide/onboarding_with_braze/sms_setup/) [SMS送信ガイドを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/)ご覧いただきたい！
 
 ## コンテンツ・ブロックの改善
 
-コンテンツブロックのAPI IDが、ダッシュボードの選択したコンテンツブロックページに表示されるようになった。さらに、コンテンツ・ブロックが使用されている場所を表示する。
+コンテンツブロックの API ID が、ダッシュボードの選択したコンテンツブロックページに表示されます。また、コンテンツブロックが使用されている場所も表示されます。
 
 ## APIによるエイリアスのみのユーザー作成と識別
 
-Attributesオブジェクトの任意のフィールドを持つ[APIリクエストを使用する]({{site.baseurl}}/api/endpoints/user_data/#user-attributes-object-specification)ことができるようになり、指定されたユーザプロファイルに、指定された値を持つその名前の属性を作成または更新する。
+属性オブジェクトに任意のフィールドを持つ [API リクエストを使用]({{site.baseurl}}/api/endpoints/user_data/#user-attributes-object-specification)して、指定されたユーザープロファイル上に、指定された値を持つその名前の属性を作成または更新できるようになりました。
diff --git a/_lang/ja/_help/release_notes/2019/september.md b/_lang/ja/_help/release_notes/2019/september.md
index 4bc8a45fd0f..d1351bd06c8 100644
--- a/_lang/ja/_help/release_notes/2019/september.md
+++ b/_lang/ja/_help/release_notes/2019/september.md
@@ -10,20 +10,20 @@ description: "この記事には2019年9月のリリースノートが含まれ
 
 ## OneLogin内のBrazeアプリ
 
-顧客は、[OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/)内でBrazeを検索して選択するだけで、SPまたはIdP Initiatedログインができるようになる。これは、顧客がOneLogin内にカスタムアプリケーションを追加する必要がないことを意味する。その結果、SAML SSOを立ち上げてから見られるようになった、属性のような特定の設定が事前に入力されるはずである。
+[OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/) 内で Braze を検索し、サービスプロバイダーまたは IdP 開始ログイン用に選択できるようになります。これは、顧客がOneLogin内にカスタムアプリケーションを追加する必要がないことを意味する。その結果、SAML SSO の起動後に表示された属性などの特定の設定が事前入力されます。
 
 ## ロクト・カレンダー・パートナーシップ
 
-[Rokt Calendarは]({{site.baseurl}}/partners/additional_channels/calendar/rokt_calendar/)、Brazeの顧客に、パーソナライズされたマーケティングイニシアティブを調整し、パーソナライズされたコンテンツをエンドユーザーのカレンダーに拡張する機能を提供する。こうして、エンドユーザーにとってよりシームレスな体験となり、顧客のサービスに対する愛着がさらに深まる。顧客は...
+[Rokt Calendarは]({{site.baseurl}}/partners/additional_channels/calendar/rokt_calendar/)、Brazeの顧客に、パーソナライズされたマーケティングイニシアティブを調整し、パーソナライズされたコンテンツをエンドユーザーのカレンダーに拡張する機能を提供する。これにより、エンドユーザーのエクスペリエンスがよりシームレスになり、お客様のサービスのスティッキネスがさらに向上します。以下を実行できるようになります。
 
 - Brazeプラットフォーム経由でカレンダーに招待状を送り、「日付を保存」してコミュニケーションを広げる。
 - イベントの内容が変更された場合、既存の招待を更新する。
 
-## パスキット・パートナーシップ
+## Passkit パートナーシップ
 
-[Passkit]({{site.baseurl}}/partners/additional_channels/mobile_wallet/passkit/)で、Braze 顧客 sは携帯ウォレットへのカスタマーエンゲージメントを拡張することができます。彼らは、Brazeの強力なセグメンテーションを使いながら、財布キャンペーンをパーソナライズし、プッシュやアプリ内メッセージなどのチャネルと並行してオーケストレーションすることができる。
+[Passkit]({{site.baseurl}}/partners/additional_channels/mobile_wallet/passkit/) により、Braze のお客様はカスタマーエンゲージメントをモバイルウォレットに拡張できます。Braze の強力なセグメンテーションを利用しながらウォレットキャンペーンをパーソナライズし、プッシュやアプリ内メッセージなどのチャネルとのオーケストレーションを実現できます。
 
-## メッセージング・エンドポイント経由でディスパッチID値を返す
+## メッセージングエンドポイント経由でのディスパッチ ID 値の返却
 
 メッセージの`dispatch_id` は、以下のメッセージング・エンドポイントのレスポンスに含まれる：
 - [`/campaigns/trigger/send`]({{site.baseurl}}/api/endpoints/messaging/#sending-messages-via-api-triggered-delivery)
@@ -33,11 +33,11 @@ description: "この記事には2019年9月のリリースノートが含まれ
 - [`/canvases/trigger/send`]({{site.baseurl}}/api/endpoints/messaging/#canvas)
 - [`/canvases/trigger/schedule`]({{site.baseurl}}/api/endpoints/messaging/#api-triggered-canvases)
 
-こうすることで、トランザクショナル・メッセージングを利用する顧客は、カレントを介してコールバックをトレースすることができる。
+これにより、トランザクションメッセージングを使用するお客様は、Currents を介してコールバックをトレースできます。
 
 ## キャンバスの変更履歴
 
-自分のアカウントで誰がキャンバスに取り組んでいるのか、もっと詳しく知りたいと思ったことはないだろうか？もう不思議ではない！キャンバスの変更履歴にアクセスできるようになった。
+自分のアカウントで誰がキャンバスに取り組んでいるのか、もっと詳しく知りたいと思ったことはないだろうか？もうその必要はありません。キャンバス変更ログにアクセスできるようになりました。
 
-![Canvas Changelogs]({% image_buster /assets/img/canvas-changelog1.png %})
-![Canvas Changelogs]({% image_buster /assets/img/canvas-changelog2.png %})
+![キャンバス変更ログ]({% image_buster /assets/img/canvas-changelog1.png %})
+![キャンバス変更ログ]({% image_buster /assets/img/canvas-changelog2.png %})
diff --git a/_lang/ja/_help/release_notes/2020.md b/_lang/ja/_help/release_notes/2020.md
index b2480335145..1a3984d81f0 100644
--- a/_lang/ja/_help/release_notes/2020.md
+++ b/_lang/ja/_help/release_notes/2020.md
@@ -3,10 +3,10 @@ page_order: 4
 nav_title: 2020
 layout: dev_guide
 noindex: true
-guide_top_header: "2020年リリースノート"
+guide_top_header: "2020 リリースノート"
 
 page_type: landing
-description: "このセクションでは、2020年のリリースノートを掲載する。"
+description: "このセクションには、2020年版のリリースノートがあります。"
 
 guide_menu_title: ""
 guide_menu_list:
diff --git a/_lang/ja/_help/release_notes/2020/april.md b/_lang/ja/_help/release_notes/2020/april.md
index ed32053bd28..31ca8a85da9 100644
--- a/_lang/ja/_help/release_notes/2020/april.md
+++ b/_lang/ja/_help/release_notes/2020/april.md
@@ -3,33 +3,33 @@ nav_title: 4月
 page_order: 9
 noindex: true
 page_type: update
-description: "この記事は、2020年4月のリリースノートを含んでいます。"
+description: "この記事には、2020年4月のリリースノートが含まれています。"
 ---
 # 2020年4月
 
-## Movable Ink提携
+## Movable Ink のパートナーシップ
 
-Movable Ink は、Braze 顧客 のプッシュ、アプリ内メッセージ、コンテンツカードキャンペーンで、カウントダウンタイマー、ポーリング、スクラッチオフなどのインテリジェントクリエイティブ機能を使用できます。Movable InkとBrazeの力は、より丸みを帯びたアプリをダイナミックな データドリブン型のの伝言に訴え、問題の内容に関するリアルタイムの要素をユーザーに提供する。
+Movable Ink は、プッシュ、アプリ内メッセージ、およびコンテンツカードキャンペーンでカウントダウンタイマー、投票、スクラッチオフなどのインテリジェントクリエイティブ機能を使用するための機能を Braze のお客様に提供します。Movable Ink と Braze は、ダイナミックなデータドリブン型のメッセージに対するより包括的なアプローチを実現し、重要事項に関するリアルタイムのエレメントをユーザーに提供します。
 
-[ Movable Ink]({{site.baseurl}}/partners/channel_extensions/creative_and_personalization/intelligent_creative/movable_ink/) をキャンペーンs に統合します!
+キャンペーンに[ Movable Ink を統合]({{site.baseurl}}/partners/channel_extensions/creative_and_personalization/intelligent_creative/movable_ink/)しましょう。
 
 ## インテリジェントタイミング
 
 キャンペーンのスケジュールを設定する場合、[インテリジェントタイミング]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_timing/)(以前はインテリジェント配信)を使用して、Brazeが個人が参加する可能性が最も高いと判断したときに、それぞれのユーザーにメッセージを配信できます。
 
 この機能の更新内容は次のとおりです。
-- **静音時間の明確化**:Quiet Hours 機能は同じままですが、UI は明確化のために調整されています。
-- **プレビューチャートの追加**:これで、インテリジェント・タイミングを使用して、1 時間ごとにメッセージを受け取るユーザーの数と、最適な時刻を計算するために十分なデータを持っているユーザーの割合を示すグラフを作成できます。
+- **サイレント時間の明確化**:サイレント時間機能に変更はありませんが、UI は明確化のために調整されています。
+- **プレビューチャートの追加**:インテリジェントタイミングを使用して、1日の各時間にメッセージを受信するユーザー数と、最適な時間を計算するのに十分なデータがあるユーザーの割合を確認するためのチャートを生成できるようになりました。
 - **カスタムフォールバックの追加**:最適な時刻を計算するのに十分なエンゲージメント情報がない場合に、ユーザーがメッセージを送信するローカル時刻を選択できるようになりました
 
 ## Facebook オーディエンス輸出
 
-Braze では、Brazeセグメントページからユーザーを手動でエクスポートして、Fac eBook カスタムオーディエンスを作成できます。これは、1 回限りのスタティックオーディエンスエクスポートであり、新しい[Fac eBook ユーザ定義オーディエンスs]({{site.baseurl}}/partners/facebook/) のみを作成します。
+Braze では、Braze セグメントページからユーザーを手動でエクスポートして Facebook カスタムオーディエンスを作成する機能が提供されています。これは1回限りの静的オーディエンスエクスポートであり、新しい [Facebook カスタムオーディエンス]({{site.baseurl}}/partners/facebook/)のみが作成されます。
 
-現在、すべてのクラスターで利用可能な新しいBraze Facebook オーディエンスエクスポートプロセスがあり、シンプルなインテグレーションステップs でプロセスを合理化しています。OAuth リダイレクトURI のホワイトリストを作成して、Fac eBook アプリ設定内でカスタムオーディエンスまたは混乱を送信して統合する必要がなくなりました。
+現在、すべてのクラスターで利用可能な新しいBraze Facebook オーディエンスエクスポートプロセスがあり、シンプルなインテグレーションステップs でプロセスを合理化しています。カスタムオーディエンスを送信するために OAuth リダイレクト URI をホワイトリストに登録したり、統合するために Facebook アプリ設定内で操作したりする必要がなくなります。
 
 {% alert important %}
-現在Fac eBook カスタムオーディエンスを使用しているすべてのクライアントは、これらの新しいステップでBrazeセグメントを再統合する必要があります。
+現在 Facebook カスタムオーディエンスを使用しているすべてのクライアントが、これらの新しいステップを使用して Braze セグメントを再統合する必要があることに注意してください。
 {% endalert%}
 
 
@@ -37,10 +37,10 @@ Braze では、Brazeセグメントページからユーザーを手動でエク
 
 [template/email/list]({{site.baseurl}}/api/endpoints/templates/email_templates/get_list_email_templates/)および[content_ブロック/list]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks/)API エンドポイントsは、新しい`tags`フィールドを含むように更新されました。このフィールドは、現行のブロックまたはメール テンプレートにアプリする任意のタグs を配列として列挙します。
 
-## カスタマイズされた発信元アドレス
+## パーソナライズされた差出人アドレス
 
 メール メッセージをBraze 内で作成するときに、メール構成の**送信情報** セクションでメッセージのFrom Address をパーソナライズできるようになりました。サポートされている任意の[パーソナライゼーション タグs]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/)を使用できます。
 
-![アドレスからカスタマイズ][0]{: style="max-width:80%"}
+![パーソナライズされた差出人アドレス][0]{: style="max-width:80%"}
 
 [0]: {% image_buster /assets/img/personalized-from-name.png %}
diff --git a/_lang/ja/_help/release_notes/2020/august.md b/_lang/ja/_help/release_notes/2020/august.md
index e5ff81725df..14b2f7b9d9c 100644
--- a/_lang/ja/_help/release_notes/2020/august.md
+++ b/_lang/ja/_help/release_notes/2020/august.md
@@ -9,17 +9,17 @@ description: "この記事には、2020年8月のリリースノートが含ま
 
 ## 外部ID移行エンドポイント
 
-Brazeは、2つの新しい外部ID移行エンドポイントをリリースした。これらのエンドポイントにより、顧客はBraze APIを利用することで、ユーザーのBraze外部IDを変更または削除することができる。これらのエンドポイントを活用することで、異なるネーミングスキーマを持つユーザーを、それらのユーザーの履歴データを保持したまま移行することができる。の詳細については、ドキュメントを参照すること。 [`users.external_ids.rename`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_rename/)と [`users.external_ids.remove`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_remove/)エンドポイントについて詳しくは
+Brazeは2つの新しい外部IDマイグレーションエンドポイントsをリリースしました。これらのエンドポイントでは、顧客s がBraze API を使用してユーザーのBraze外部ID の名前を変更または削除できます。これらのエンドポイントを活用することで、異なるネーミングスキーマを持つユーザーを、それらのユーザーの履歴データを保持したまま移行することができる。の詳細については、ドキュメントを参照すること。 [`users.external_ids.rename`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_rename/)と [`users.external_ids.remove`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_remove/)エンドポイントについて詳しくは
 
 ## 解約予測
 
-BrazeのPredictive Suiteは、機械学習を直接あなたの手に届ける。[Predictive Churnを]({{site.baseurl}}/user_guide/predictive_suite/)始め、Brazeプラットフォーム内でシームレスにデータを効果的に活用し、行動することがこれまで以上に簡単になった。これを使えば、特定の顧客ベースの解約リスクを予測するためにカスタマイズされた機械学習モデルを作成し、手遅れになる前に機械学習がリスクがあると判断したユーザーにメッセージを送ることができる。 
+BrazeのPredictive Suiteは、機械学習を直接的に手にします。[Predictive Churn]({{site.baseurl}}/user_guide/predictive_suite/)から始めると、Braze プラットフォーム内のデータシームレスにを効果的に活用し、行動することは、今まで以上に簡単です。これを使えば、特定の顧客ベースの解約リスクを予測するためにカスタマイズされた機械学習モデルを作成し、手遅れになる前に機械学習がリスクがあると判断したユーザーにメッセージを送ることができる。 
 
-この機能のプレビューは、8月上旬に対象となるBraze顧客のダッシュボードに表示される。全機能へのアクセスについては、アカウント・マネージャーに問い合わせること。
+この機能の試聴は、8月初旬に適格なBraze 顧客のダッシュボードsで耳元をアプリします。完全な機能については、アカウントマネージャーにお問い合わせください。
 
-## Currentsのトラッキング・プロパティの更新
+## Currents "トラッキング プロパティーのアップデート
 
-特定のCurrentsメッセージ・エンゲージメント・イベント内に、トラッキング・プロパティ`canvas_variation_name` と`canvas_step_name` が追加された。全リストは、[メッセージ・エンゲージメント・イベント用語集と]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) [カレントのChangelogを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/)チェックしてほしい。
+特定のCurrents電文エンゲージメント事象の中に、"トラッキングプロパティー`canvas_variation_name`と`canvas_step_name`が追加された。全リストは、[メッセージ・エンゲージメント・イベント用語集と]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) [カレントのChangelogを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/)チェックしてほしい。
 
 ## Amazon Personalizeパートナーシップ
 
@@ -27,12 +27,12 @@ Amazon Personalizeは、機械学習を利用して、ウェブサイトやア
 
 ## Vizbeeパートナーシップ
 
-Vizbeeは、家庭内のすべてのスマートフォンとスマートテレビを1つのシームレスなデバイスとして連携させ、優れたユーザー体験を可能にする。Vizbeeは、すべてのCTVデバイス（Roku、FireTV、Samsung TV、LG TVなど）で視聴者を獲得し、エンゲージするために、通知、ディープリンク、電子メールなどの既存のモバイルアプリ・マーケティング・チャンネルを活用するのに役立つ。詳細については、[Vizbeeの]({{site.baseurl}}/partners/channel_extensions/deep_linking/vizbee_for_tv_deeplinking/)ドキュメントをチェックしてほしい。 
+Vizbeeは、家庭内のすべてのスマートフォンとスマートテレビを1つのシームレスなデバイスとして連携させ、優れたユーザー体験を可能にする。Vizbeeは、すべてのCTVデバイス（Roku、FireTV、Samsung TV、LG TVなど）で視聴者を獲得し、エンゲージするために、通知、ディープリンク、電子メールなどの既存のモバイルアプリ・マーケティング・チャンネルを活用するのに役立つ。詳細については、[Vizbee]({{site.baseurl}}/partners/channel_extensions/deep_linking/vizbee_for_tv_deeplinking/) ドキュメントを参照してください。 
 
-## ブルードット・パートナーシップ
+## Bluedot提携
 
-ブルードットは、アプリに正確でわかりやすいジオフェンシングを提供するロケーション・プラットフォームだ。ブルードットのSDKを使用することで、よりスマートなメッセージ、モバイル注文チェックインの自動化、ワークフローの最適化、摩擦のない体験の実現が可能になる。詳しくは、[ブルードットの]({{site.baseurl}}/partners/data_augmentation/contextual_location/bluedot/#bluedot)ドキュメントをご覧いただきたい。 
+Bluedot は、アプリ s のAC キュレートと単純なジオフェンシングを提供する場所プラットフォームです。Bluedot のSDKを使用すると、よりスマートにメッセージを送信し、モバイル注文のチェックインを自動化し、ワークフローを最適化し、摩擦のない体験を作成できます。詳細については、[Bluedot]({{site.baseurl}}/partners/data_augmentation/contextual_location/bluedot/#bluedot) ドキュメントを参照してください。 
 
-## パートナーシップを繰り返す
+## Iterate提携
 
-Iterateは、スマートで使いやすい調査ツールを提供することで、顧客から簡単に学ぶことができる。詳しくは[Iterateの]({{site.baseurl}}/partners/additional_channels/surveys/iterate/)ドキュメントをご覧いただきたい。 
+Iterateは、あなたの顧客から簡単に学ぶことができ、あなたのブランドのように見える、そして感じられるスマートでユーザーに優しい調査道具を提供します。詳細については、[Iterate]({{site.baseurl}}/partners/additional_channels/surveys/iterate/) ドキュメントを参照してください。 
diff --git a/_lang/ja/_help/release_notes/2020/december.md b/_lang/ja/_help/release_notes/2020/december.md
index 2e7d19d5cd4..dae983906bd 100644
--- a/_lang/ja/_help/release_notes/2020/december.md
+++ b/_lang/ja/_help/release_notes/2020/december.md
@@ -7,13 +7,13 @@ description: "この記事には、2020年12月のリリースノートが含ま
 ---
 # 2020年12月
 
-## Currents メッセージング・イベント・プロパティの更新
+## Currents メッセージングのイベントプロパティーのアップデート
 
-Currentsのメールメッセージング・エンゲージメント・イベントに、トラッキング・プロパティ（`ip_pool` ）が追加された。トラッキング・プロパティ`bounce_reason` と`bounce_code` は、`users.messages.email.Bounce` と`users.messages.email.SoftBounce` イベントにも追加された。<br>全リストは、[メッセージ・エンゲージメント・イベント用語集を]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)参照のこと。
+Currents メールメッセージングエンゲージメントイベント内に、トラッキングプロパティ `ip_pool` が追加されました。また、トラッキングプロパティ `bounce_reason` および `bounce_code` が、`users.messages.email.Bounce` および`users.messages.email.SoftBounce` イベントに追加されました。<br>全リストは、[メッセージ・エンゲージメント・イベント用語集を]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)参照のこと。
 
 ## 解約予測に関するFAQ
 
-既存のPredictive Churnのドキュメントに、よくある質問の記事が追加された。これらの潜在的なエラー、タイミングの明確化、データに関する考察の詳細については、[予測解約に関するFAQを]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/prediction_faq/)参照されたい。
+よくある質問の記事が、既存の解約予測ドキュメントに追加されました。これらの潜在的なエラー、タイミングの明確化、データに関する考察の詳細については、[予測解約に関するFAQを]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/prediction_faq/)参照されたい。
 
 ## CSVおよびAPIエクスポートのトラブルシューティング・ドキュメント
 
@@ -21,20 +21,20 @@ Brazeのドキュメントに、よくあるCSVとAPIのエラーについての
 
 ## EduMeパートナーシップ
 
-EduMeはモバイルベースのトレーニングツールで、従業員が成功するために必要な知識を提供する。BrazeのConnected Contentを使って、従業員や顧客がEduMeのレッスンやコースにアクセスできるようにする。生徒はブラウザからシームレスにこのコンテンツにアクセスでき、EduMeのレポート機能を使って、グループまたは個人としての学習進捗状況を確認することができる。詳しくは、[EduMeの]({{site.baseurl}}/partners/channel_extensions/learning/edume/)ドキュメントをご覧いただきたい。
+EduMeはモバイルベースのトレーニングツールで、従業員が成功するために必要な知識を提供する。Braze の Connected Content を使用して、従業員や顧客が EduMe のレッスンやコースにアクセスできるようにします。従業員や顧客はブラウザでシームレスにこのコンテンツにアクセスでき、ユーザーは EduMe レポート機能を使用してグループまたは個人としての進捗状況を追跡できます。詳細については、[EduMe]({{site.baseurl}}/partners/channel_extensions/learning/edume/)ドキュメントを参照してください。
 
-## パイストリームとのパートナーシップ
+## Pypestream パートナーシップ
 
-Pypestreamはフルスタックの会話AIプラットフォームで、特許を取得したオールインワンのクラウド・メッセージングを提供し、ブランドを「常時オン」のデジタル・エンティティに変える。BrazeとPypestreamのパートナーシップにより、ブランドは、最初のアウトリーチから、会話体験へのルーティング、インテリジェントなリターゲティングによるオムニチャネルのフォローアップまで、エンドツーエンドの顧客ライフサイクルをシームレスに編成することができる。詳細については、[Pypestreamの]({{site.baseurl}}/partners/advertising_technologies/attribution/pypestream/)ドキュメントをチェックしてほしい。
+Pypestream はフルスタックの会話型 AI プラットフォームであり、特許取得済みのオールインワン型クラウドメッセージングを提供し、ブランドを「常時稼働」状態のデジタルエンティティに変換します。Braze と Pypestream のパートナーシップにより、最初のアウトリーチから会話エクスぺリエンスへのルーティング、インテリジェントなリターゲティングによるオムニチャネルのフォローアップまで、エンドツーエンドのカスタマーライフサイクルをシームレスに管理できます。詳細については、[Pypestream]({{site.baseurl}}/partners/advertising_technologies/attribution/pypestream/)ドキュメントを参照してください。
 
-## ダイスパッチ・パートナーシップ
+## Dyspatch パートナーシップ
 
-Dyspatchを使えば、直感的なドラッグ＆ドロップ操作で、コードを書くことなく、美しく、レスポンシブで、魅力的なEメールを作成できる。チームと協力してDyspatchでメールを作成・承認し、Brazeにアップロードする！詳しくは[Dyspatchの]({{site.baseurl}}/partners/channel_extensions/creative_and_personalization/email_orchestration/dyspatch/)ドキュメントを参照されたい。
+Dyspatchを使えば、直感的なドラッグ＆ドロップ操作で、コードを書くことなく、美しく、レスポンシブで、魅力的なEメールを作成できる。チームと協力して、Dyspatch 内でメールを作成および承認し、Braze で使用するためにアップロードします。これらの作業は数ステップで完了できます。詳細については、[Dyspatch]({{site.baseurl}}/partners/channel_extensions/creative_and_personalization/email_orchestration/dyspatch/) ドキュメントを参照してください。
 
 ## RudderStackパートナーシップ
 
-RudderStackはオープンソースの顧客データ基盤で、顧客のイベントデータを収集し、好みのデータウェアハウスやBrazeのような数多くの分析プロバイダーにルーティングする。エンタープライズ対応で、イベントデータをその場で処理するための堅牢な変換フレームワークを提供する。詳しくは[RudderStackの]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/#rudderstack)ドキュメントをご覧いただきたい。
+RudderStack は、顧客イベントデータを収集し、希望するデータウェアハウスや Braze などの他の多数の分析プロバイダーにルーティングするための、オープンソースの顧客データインフラです。これはエンタープライズ対応で、イベントデータを即座に処理するための強力な変換フレームワークを提供します。詳細については、[RudderStack]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/#rudderstack)ドキュメントを参照してください。
 
-## ジェビット・パートナーシップ
+## Jebbit パートナーシップ
 
-Jebbitは、ファーストパーティデータを取得するために、ユーザーにとって魅力的な体験を構築できるPaaSだ。JebbitはBrazeと提携しており、JebbitのキャンペーンからユーザーのEメールや属性をユーザーデータとしてリアルタイムでBrazeに渡すことができる。このデータは、パーソナライズされたEメールキャンペーンやトリガーといったマーケティング施策の推進に活用できる。詳しくは、[Jebbitの]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/jebbit/#jebbit)ドキュメントをチェックしてほしい。
+Jebbit は、ユーザーがファーストパーティデータを取得するための魅力的なエクスペリエンスを構築できる PaaS です。JebbitはBrazeと提携しており、JebbitのキャンペーンからユーザーのEメールや属性をユーザーデータとしてリアルタイムでBrazeに渡すことができる。このデータは、パーソナライズされたEメールキャンペーンやトリガーといったマーケティング施策の推進に活用できる。詳細については、[Jebbit]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/jebbit/#jebbit) ドキュメントを参照してください。
diff --git a/_lang/ja/_help/release_notes/2020/february.md b/_lang/ja/_help/release_notes/2020/february.md
index f33d023d459..ef6675b15a5 100644
--- a/_lang/ja/_help/release_notes/2020/february.md
+++ b/_lang/ja/_help/release_notes/2020/february.md
@@ -9,12 +9,12 @@ description: "この記事には2020年2月のリリースノートが含まれ
 
 ## リテンションレポート
 
-Brazeは、キャンペーンの[リテンションレポートを]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/retention_reports/)提供できることを誇りに思う。この機能は、特定のキャンペーンで何らかのメッセージを受け取ったユーザーのリテンションを測定するのに役立つ。リテンションレポートは、ダッシュボード内の**キャンペーン分析**ページで見ることができる。 
+Brazeは、キャンペーンの[リテンションレポートを]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/retention_reports/)提供できることを誇りに思う。この機能は、特定のキャンペーンで何らかのメッセージを受け取ったユーザーのリテンションを測定するのに役立つ。リテンションレポートは、ダッシュボード内の \[**キャンペーン分析**] ページで簡単に見つけることができます。 
 
 ![フルレポート][4]
 
 {% alert important %}
-2020年1月13日現在、この機能はEU地域に展開するクライアントやHIPPAに準拠したクラスタではまだ利用できない。プラットフォーム全体への機能配備を進めながら、これらの地域でもこのレポートを利用できるようにする予定だ。
+2020年1月13日現在、この機能は、EU地域またはHIPPA準拠クラスターに展開されている当社のクライアントではまだ使用できません。プラットフォーム全体への機能配備を進めながら、これらの地域でもこのレポートを利用できるようにする予定だ。
 {% endalert %}
 
 ## 新しいEメール・コンテンツ・ブロックAPIエンドポイント
diff --git a/_lang/ja/_help/release_notes/2020/january.md b/_lang/ja/_help/release_notes/2020/january.md
index 7e9424918de..95207c7b644 100644
--- a/_lang/ja/_help/release_notes/2020/january.md
+++ b/_lang/ja/_help/release_notes/2020/january.md
@@ -7,10 +7,10 @@ description: "この記事には2020年1月のリリースノートが含まれ
 ---
 # 2020年1月
 
-新しい年、新しい10年へようこそ！ 
+お正月と新10年へようこそ！ 
 
 ## SMS機能を追加
 
-Brazeでは、SMSメッセージの頻度]({{ site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/) ) に上限を設定できるようになった。追加された\[セグメントフィルター]({{ site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/) "Last Received SMS")を実装することもできる。
+Braze では、SMS メッセージの頻度を\[cap the frequency]({{ site.baseurl}}/user_guide/エンゲージメント_tools/campaigns/testing_and_more/rate-limiting/) とすることができます。追加された\[セグメントフィルター]({{ site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/) "Last Received SMS")を実装することもできる。
 
 ユーザー設定と動作の詳細については、[SMSキーワード](/docs/user_guide/message_building_by_channel/sms/keywords/)処理を参照のこと。
diff --git a/_lang/ja/_help/release_notes/2020/june.md b/_lang/ja/_help/release_notes/2020/june.md
index 25cb5699370..418ccbf31eb 100644
--- a/_lang/ja/_help/release_notes/2020/june.md
+++ b/_lang/ja/_help/release_notes/2020/june.md
@@ -9,13 +9,13 @@ description: "この記事には2020年6月のリリースノートが含まれ
 
 ## リテンションレポート
 
-リテンションレポートは、[キャンペーン][2]および[キャンバス][1]の範囲リテンションを提供するようになりました。範囲リテンションは、特定の時間間隔で選択されたリテンションイベントを実行するために何人のユーザーが戻ってくるかを測定します。 
+リテンションレポートは、[キャンペーン][2]および[キャンバス][1]の範囲リテンションを提供するようになりました。レンジリテンションは、指定した期間内に、選択したリテンションを実行するユーザーの数を測定します。 
 
-## ユーザー トラック API 更新
+## ユーザトラックAPI 更新
 
-[`users/track`エンドポイント][3]は現在、2020年6月2日以降に作成されたダッシュボード会社に対して、デフォルトのレートとして1分あたり50,000のAPIリクエストを持っています。この日付より前に作成された既存の企業とそのワークスペースは、`users/track`エンドポイントへの無制限のAPIリクエストが引き続き許可されます。
+[`users/track` エンドポイント][3] は、2020年6 月2 日以降に作成されたダッシュボード企業で、1 分あたり50,000 のAPI リクエストのデフォルト率を持っています。この日付より前に作成された既存の企業とそのワークスペースは、`users/track`エンドポイントへの無制限のAPIリクエストが引き続き許可されます。
 
-Brazeは、APIおよびインフラの安定性と信頼性の目標に向けたステップとして、最も頻繁に使用される顧客向けエンドポイントにこのデフォルトを課しています。課せられた制限は非常に自由であり、ダッシュボード企業やその通常の運営に影響を与えることはほとんどありません。この制限の引き上げが必要な場合は、顧客成功マネージャーまたはサポートチームに連絡して引き上げをリクエストしてください。
+Brazeは、APIおよびインフラの安定性と信頼性の目標に向けたステップとして、最も頻繁に使用される顧客向けエンドポイントにこのデフォルトを課しています。この制限は非常に自由であり、ほとんどのダッシュボード企業やその通常業務に影響を与えることはない。この制限を引き上げる必要がある場合は、顧客のサクセスマネージャーまたはサポートチームに連絡し、引き上げをリクエストしてください。
 
 [1]: {{site.baseurl}}/user_guide/engagement_tools/canvas/retention_reports/
 [2]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/retention_reports/
diff --git a/_lang/ja/_help/release_notes/2020/march.md b/_lang/ja/_help/release_notes/2020/march.md
index 55a5ca25a19..b735f4bbd93 100644
--- a/_lang/ja/_help/release_notes/2020/march.md
+++ b/_lang/ja/_help/release_notes/2020/march.md
@@ -9,12 +9,12 @@ description: "この記事には2020年3月のリリースノートが含まれ
 
 ## カスタム属性 フィルタービヘイビア
 
-ダッシュボードは[改善されたフィルターs]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#dates)を持ち、より直感的な振る舞いを含む。
-特定のカスタム属性s フィルターs の動作には、2 つの重要な変更があります。 
+ダッシュボードの[フィルターが改善され]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#dates)、より直感的な動作が追加されました。
+特定のカスタム属性フィルターの動作に2つの重要な変更が加えられました。 
 
-カスタム属性 フィルターの変更はフィルターs に反映されます。 
-- **X** Days Ago 未満
-- Less than **X** Days in the Future
+カスタム属性フィルターの変更がフィルターに反映されます。 
+- 過去 **X** 日間以内
+- 未来 **X** 日間以内
 - 定期的なイベントの日<br>
 
 これらのフィルターs をセグメンテーションで使用する場合は、これらの変更を考慮してSegments を再調整することをお勧めします。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2020/may.md b/_lang/ja/_help/release_notes/2020/may.md
index 309c18872c5..4f47a26e546 100644
--- a/_lang/ja/_help/release_notes/2020/may.md
+++ b/_lang/ja/_help/release_notes/2020/may.md
@@ -17,19 +17,19 @@ Braze API経由でメールアドレスを[ブラックリスト化]({{site.base
 
 ## Braze APIエンドポイントのAPIキー変更
 
-2020年5月より、BrazeはAPIキーの読み取り方法をより安全なものに変更した。APIキーはリクエスト・ヘッダとして渡さなければならない。例は、**API Key Explanationと**同様に、**Example Requestの**下にある個々のエンドポイントのページで見つけることができる。
+2020年5月より、BrazeはAPIキーの読み取り方法をより安全なものに変更した。これで API キーがリクエストヘッダーとして渡されるはずです。\[**リクエスト例**] の下の個々のエンドポイントページや、\[**API キーの説明**] で例を確認できます。
 
-Brazeは、リクエストボディやURLパラメータを通して渡される`api_key` をサポートし続けるが、いずれは廃止される予定である（未定）。**それに応じてAPIコールを更新する。**これらの変更は[Postman](https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#intro)内で更新された。
-{% details APIキーの説明 %}
+Braze は、リクエストボディとURL パラメータに渡される`api_key` を引き続きサポートしますが、最終的にはサンセット(TBD) になります。**API コールを適宜更新します。**これらの変更は[Postman](https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#intro)内で更新された。
+{% details API キーの説明 %}
 {% tabs %}
 {% tab GET Request %}
 この例では、`/email/hard_bounces` エンドポイントを使用している。
 
-**その前だ：リクエスト・ボディのAPIキー**
+**前:リクエスト本文のAPI キー**
 ```
 curl --location --request GET 'https://rest.iad-01.braze.com/email/hard_bounces?api_key={YOUR_REST_API_KEY}&start_date=2019-01-01&end_date=2019-02-01&limit=100&offset=1&email=foo@braze.com' \
 ```
-**今すぐだ：ヘッダーのAPIキー**
+**現在: ヘッダーのAPIキー**
 ```
 curl --location --request GET 'https://rest.iad-01.braze.com/email/hard_bounces?start_date=2019-01-01&end_date=2019-02-01&limit=100&offset=1&email=foo@braze.com' \
 --header 'Authorization: Bearer YOUR-REST-API-KEY'
@@ -38,7 +38,7 @@ curl --location --request GET 'https://rest.iad-01.braze.com/email/hard_bounces?
 {% tab POST Request %}
 この例では、`/user/track` エンドポイントを使用している。
 
-**その前だ：リクエスト・ボディのAPIキー**
+**前:リクエスト本文のAPI キー**
 ```
 curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
 --header 'Content-Type: application/json' \
@@ -55,7 +55,7 @@ curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
     ]
 }'
 ```
-**今すぐだ：ヘッダーのAPIキー**
+**現在: ヘッダーのAPIキー**
 ```
 curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
 --header 'Content-Type: application/json' \
diff --git a/_lang/ja/_help/release_notes/2020/november.md b/_lang/ja/_help/release_notes/2020/november.md
index 985945fba41..d76e81e243c 100644
--- a/_lang/ja/_help/release_notes/2020/november.md
+++ b/_lang/ja/_help/release_notes/2020/november.md
@@ -8,13 +8,13 @@ description: "この記事には2020年11月のリリースノートが含まれ
  
 # 2020年11月
 
-## Tealiumのパートナーシップが開始されました
+## Tealium のパートナーシップが開始
 
-[Tealium]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/#about-tealium) は、サードパーティのソースからモバイル、Web、および代替データを簡単に接続できるデータハブです。Brazeと接続すると、Tealiumはカスタムイベント、ユーザー属性、および購入のデータフローをリアルタイムデータアクションのために可能にします。
+[Tealium]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/#about-tealium) は、サードパーティのソースからモバイル、Web、および代替データを簡単に接続できるデータハブです。Braze に接続すると、Tealium により、カスタムイベント、ユーザー属性、および購入のデータフローがリアルタイムデータアクションで有効になります。
 
 ## Braze プロダクトポータル
 
-[Braze Product Portal]({{site.baseurl}}/user_guide/administrative/access_braze/portal/#product-portal-)には、Braze製品のロードマップとユーザーがアイデアを提出する機会が含まれています。最近リリースされた機能も確認できます。製品ポータルは、**リソース**のBrazeダッシュボードにあります。
+[Braze Product Portal]({{site.baseurl}}/user_guide/administrative/access_braze/portal/#product-portal-)には、Braze製品のロードマップとユーザーがアイデアを提出する機会が含まれています。最近リリースされた機能も確認できます。製品ポータルは、Braze ダッシュボードの \[**リソース**] にあります。
 
 ## iOSコンテンツカード実装ガイド
 
@@ -22,4 +22,4 @@ description: "この記事には2020年11月のリリースノートが含まれ
 
 ## Swift Package Manager
 
-[Swift Package Manager]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overviewswift_package_manager) は、Swift ビルドシステムと統合されており、自動的にダウンロード、コンパイル、リンクの依存関係が生成されます。Swiftパッケージマネージャーを介してiOS SDKをインストールすると、インストールプロセスの大部分が自動化されます。
+[Swift Package Manager]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overviewswift_package_manager) は、Swift ビルドシステムと統合されており、依存関係を自動的にダウンロード、コンパイル、およびリンクします。Swiftパッケージマネージャーを介してiOS SDKをインストールすると、インストールプロセスの大部分が自動化されます。
diff --git a/_lang/ja/_help/release_notes/2020/october.md b/_lang/ja/_help/release_notes/2020/october.md
index 3497ab732f4..dc8c9ce882a 100644
--- a/_lang/ja/_help/release_notes/2020/october.md
+++ b/_lang/ja/_help/release_notes/2020/october.md
@@ -20,22 +20,22 @@ iOS 14アップグレードガイドでは、iOS 14で導入されたBraze関連
 
 ## Android 11アップグレードガイド
 
-Android 11ガイドは、Android 11リリースで導入された関連する変更と、Braze Android SDK統合に必要なアップグレード手順について説明している。ディープリンク、HTMLアプリ内メッセージ、ロケーション許可に関する変更もある。詳しくは[アップグレードガイドを]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_11/)ご覧いただきたい。
+『Android 11 ガイド』では、Android 11 リリースで導入された関連する変更点と、Braze Android SDK インテグレーションに必要なアップグレード ステップs について説明します。ディープリンク、HTMLアプリ内メッセージ、ロケーション許可に関する変更もある。詳しくは[アップグレードガイドを]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_11/)ご覧いただきたい。
 
 ## アトリビューション・パートナー - クリック追跡ガイド
 
-各アトリビューション・パートナーのページに、オプションでクリックトラッキングのドキュメントが追加された。このドキュメントには、キャンペーンでクリックトラッキングを機能させるためのベストプラクティスと実装ガイドラインが含まれている。詳しくは、[アトリビューション・パートナーの]({{site.baseurl}}/partners/advertising_technologies/attribution/)ページをご覧いただきたい。 
+各アトリビューション・パートナーのページに、オプションでクリックトラッキングのドキュメントが追加された。このドキュメントには、キャンペーンでクリックトラッキングを機能させるためのベストプラクティスと実装ガイドラインが含まれている。詳細については、[アトリビューションパートナー]({{site.baseurl}}/partners/advertising_technologies/attribution/)ページをご覧ください。 
 
 ## 新しい説明フィールド
 
-キャンペーンとキャンバスに説明文を追加できるようになった！この新しいフィールドは、既存のキャンペーンまたはキャンバスを作成または編集する際に、キャンペーンまたはキャンバス名フィールドの下に見つけることができる。 
+キャンペーンとキャンバスに説明文を追加できるようになった！この新しいフィールドは、既存のキャンペーンやキャンバスの作成または編集時に、\[キャンペーンまたはキャンバス名] フィールドの下に表示されます。 
 
 ## キャンバスの例外イベント
 
-Canvasesにおける[例外イベントの]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/exception_events/)期待される動作について説明した新しいドキュメントが追加された。 
+キャンバスにおける[例外イベント]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/exception_events/)の予想される動作を説明する新しいドキュメントが追加されました。 
 
 ## ユーザーが更新を削除する
 
-BrazeはAPIに改良を加え、データ削除を要求しているデータ対象者のエンドユーザープロファイルだけでなく、データ対象者の電話番号や電子メールアドレスに関連する購読状態も、顧客が追加の操作をすることなく同時に削除できるようにした。更新されたドキュメントは[ここに]({{site.baseurl}}/help/dp-technical-assistance/#braze-recommendation-2)ある。
+Braze は API を改良し、追加のアクションを実行しなくても、データの削除を要求するデータ主体のエンドユーザープロファイルだけでなく、データ主体の電話番号やメールアドレスに関連付けられたサブスクリプションの状態も同時に削除できるようにしました。更新されたドキュメントは[ここで見つかります]({{site.baseurl}}/help/dp-technical-assistance/#braze-recommendation-2)
 
 [5]: {% image_buster /assets/img/campaign_comparison/campaign_main.png %} 
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2020/september.md b/_lang/ja/_help/release_notes/2020/september.md
index 3ba8c3e5e71..bde3d98262b 100644
--- a/_lang/ja/_help/release_notes/2020/september.md
+++ b/_lang/ja/_help/release_notes/2020/september.md
@@ -3,7 +3,7 @@ nav_title: 9月
 page_order: 4
 noindex: true
 page_type: update
-description: "この記事は、2020年9月のリリースノートを含んでいます。"
+description: "この記事には、2020年9月のリリースノートが含まれています。"
 ---
 
 # 9月
@@ -12,13 +12,13 @@ description: "この記事は、2020年9月のリリースノートを含んで
 
 ファネルレポートは、[キャンペーン]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/campaign_funnel_report/) または[キャンバス]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_funnel_reports) を受信した後に、顧客が実行するジャーニーを分析できる視覚的なレポートを提供します。
 
-## iOS 14 アップグレード
+## iOS 14アップグレードガイド
 
-アップルの新しいiOS 14で発表された変更に伴い、Braze関連の変更やアクションの項目が、iOS SDKの統合に必要なものがいくつかあります。詳細については、この[アップグレードガイド]({{site.baseurl}}/ios_14/)を参照してください。
+Apple の新しい iOS 14で発表された変更に伴い、Braze iOS SDK の統合に必要な Braze 関連の変更とアクション項目がいくつかあります。詳細については、この[アップグレードガイド]({{site.baseurl}}/ios_14/)を参照してください。
 
-## iOS 用IDFA およびIDFV の変更14
+## iOS 14の IDFA および IDFV の変更
 
-iOS 14 では、ユーザー s は"トラッキング をアドインするかどうかを決定し、アプリを訪問するときに、s およびアドネットワークにIDFA を読み取らせる必要があります。そのため、Braze の戦略では、代わりに" 識別子をベンダー" (IDFV など) に使用することで、さまざまな機器間でユーザーを追跡し続けることができます。詳しくは、[iOS 14 アップグレードガイド]({{site.baseurl}}/ios_14/)をご覧ください。
+iOS 14では、ユーザーがアプリにアクセスしたときに広告トラッキングをオプトインして、アプリと広告ネットワークに IDFA の読み取りを許可するかどうかを決定する必要があります。それに応じた Braze の戦略として、代わりに「ベンダーの識別子」 (IDFV など) を使用して、異なるデバイス間でユーザーを継続的に追跡できるようにします。詳しくは、[iOS 14 アップグレードガイド]({{site.baseurl}}/ios_14/)をご覧ください。
 
 ## メール検証
 
@@ -26,14 +26,14 @@ iOS 14 では、ユーザー s は"トラッキング をアドインするか
 
 ## Currentsにおけるランダムバケットユーザー事象
 
-ランダムバケット番号(RBNなど)は、新しいユーザーがワークスペース内に作成されるたびに発生します。このイベントの間、新規ユーザーのそれぞれにランダムなバケット番号が割り当てられます。このバケット番号を使用して、ランダムなユーザーの一様分布セグメントを作成できます。これを使用して、ランダムバケット番号値の範囲をグループ化し、キャンペーンとキャンペーンバリアント間でパフォーマンスを比較します。このイベントが使用可能かどうかを確認するには、Currents[ 顧客行動 イベント用語集]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/) を参照してください。
+ランダムバケット番号 (RBNなど) は、ワークスペース内で新しいユーザーが作成されるたびに生成されます。このイベントの間、新規ユーザーのそれぞれにランダムなバケット番号が割り当てられます。このバケット番号を使用して、ランダムなユーザーの一様分布セグメントを作成できます。これを使用して、ランダムバケット番号値の範囲をグループ化し、キャンペーンとキャンペーンバリアント間でパフォーマンスを比較します。このイベントが使用可能かどうかを確認するには、Currents [顧客行動イベント用語集]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)を参照してください。
 
-## キャンバスコンポーネント - まもなく登場します!
+## キャンバスコンポーネント - 近日提供開始
 
-Braze では、キャンバスの柔軟性と機能性を高めるために、4 つの新しいキャンバスコンポーネントが追加されました。これらの新しいコンポーネントは次のとおりです。[分割ステップ]({{site.baseurl}}/decision_split/)、[遅延ステップ]({{site.baseurl}}/delay_step/)、[メッセージングステップ]({{site.baseurl}}/message_step/)、および[Fac eBook]({{site.baseurl}}/audience_sync_facebook/)へのオーディエンス同期。
-- **キャンバスのディシジョンの分割、遅延、およびメッセージングの手順**<br>ディシジョンスプリットは、ユーザーが定義済みクエリーと一致するかどうかに応じてキャンバスブランチを作成するために使用できます。遅延ステップでは、対応するメッセージを必要とせずに、キャンバスにスタンドアロン遅延を追加できます。メッセージステップでは、キャンバスフロー内の目的の場所にスタンドアロンメッセージを追加できます。
-- **オーディエンスがファクトeBookに同期する**<br>Braze Audience Sync to Fac eBookを使用すると、ブランドは独自のBrazeインテグレーションからFac eBook カスタムオーディエンスに独自のユーザーのデータを追加して、行動トリガーやセグメンテーションなどに基づいた広告を配信できます。通常、メッセージをトリガーするために使用する基準(プッシュ、メール、SMS、Webフックなど)を、ユーザーデータに基づいてBrazeキャンバスで使用できるようになりました。これにより、カスタムオーディエンスを介してFac eBookでそのユーザーに広告をトリガーすることができます。
+Braze は、キャンバスの柔軟性と機能性を向上させるために、4つの新しいキャンバスコンポーネントを追加しました。これらの新しいコンポーネントには[条件分岐ステップ]({{site.baseurl}}/decision_split/)、[遅延ステップ]({{site.baseurl}}/delay_step/)、[メッセージングステップ]({{site.baseurl}}/message_step/)、[FaceBook へのオーディエンス同期]({{site.baseurl}}/audience_sync_facebook/)が含まれます。
+- **キャンバスの条件分岐、遅延、およびメッセージングステップ**<br>条件分岐を使用して、ユーザーが定義済みのクエリと一致するかどうかに基づいてキャンバス Branch を作成できます。遅延ステップでは、対応するメッセージを必要とせずに、キャンバスにスタンドアロン遅延を追加できます。メッセージステップでは、キャンバスフロー内の目的の場所にスタンドアロンメッセージを追加できます。
+- **Facebook へのオーディエンス同期**<br>Braze Facebook へのオーディエンス同期を使用すると、ブランドは独自の Braze 統合からのユーザーデータを Facebook のカスタムオーディエンスに追加して、行動トリガーやセグメンテーションなどに基づいて広告を配信できます。ユーザーデータに基づいて Braze キャンバスでメッセージをトリガーするために通常使用する基準 (プッシュ、メール、SMS、Webhook など) を、カスタムオーディエンスを介して Facebook 内の該当ユーザーに対して広告をトリガーするために使用できるようになりました。
 
 ## SMS インバウンド受信イベント
 
-新しいメッセージング エンゲージメントがCurrentsに追加されました。このイベントは、ユーザーの 1 人が Braze SMS サブスクリプショングループの 1 つの電話番号に SMS を送信したときに発生します。詳細については、Currents [ メッセージングおよびエンゲージメントイベント用語集]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) を参照してください。
+新しいメッセージングエンゲージメントが Currents に追加されました。このイベントは、ユーザーの 1 人が Braze SMS サブスクリプショングループの 1 つの電話番号に SMS を送信したときに発生します。詳細については、Currents [ メッセージングおよびエンゲージメントイベント用語集]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) を参照してください。
diff --git a/_lang/ja/_help/release_notes/2021/april.md b/_lang/ja/_help/release_notes/2021/april.md
index bd8b0c77359..c0ac935ae2a 100644
--- a/_lang/ja/_help/release_notes/2021/april.md
+++ b/_lang/ja/_help/release_notes/2021/april.md
@@ -13,11 +13,11 @@ description: "この記事には2021年4月のリリースノートが含まれ
 
 ## マルチメディアメッセージングサービス（MMS）のVFCサポート
 
-vCards、またはVirtual Contact Files（VCF）として知られるものは、アドレス帳や連絡先帳に簡単にインポートできるビジネス/連絡先情報を送信するための標準化されたファイル形式です。これらのVFCファイルは、[MMS]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/create/)を通じて送信され、Brazeメディアライブラリーに追加できるようになりました。 
+vCard は仮想連絡先ファイル (VCF) とも呼ばれ、アドレス帳や連絡先一覧に簡単にインポートできるビジネス情報や連絡先情報を送信するための標準化されたファイル形式です。これらのVFCファイルは、[MMS]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/create/)を通じて送信され、Brazeメディアライブラリーに追加できるようになりました。 
 
-## ユーザーの削除を更新
+## ユーザー削除の更新
 
-2020年10月に、ユーザーがデータ対象者の電話番号やメールアドレスを削除する方法に[改善]({{site.baseurl}}/help/release_notes/2020/october/)を加えました。 
+2020年10月に、ユーザー削除でデータ主体の電話番号やメールアドレスを処理する方法を[改善]({{site.baseurl}}/help/release_notes/2020/october/)しました。 
 
 ## 新しいBrazeのパートナーシップ
 
@@ -26,16 +26,16 @@ vCards、またはVirtual Contact Files（VCF）として知られるものは
 [AirbridgeとBrazeの統合]({{site.baseurl}}/partners/message_orchestration/attribution/airbridge/)により、すべてのオーガニックおよび非オーガニックのインストールアトリビューションデータをBrazeに渡して、よりパーソナライズされたマーケティングキャンペーンを構築し、ユーザーがどこで獲得されたかを正確に把握することができます。
 ### Kubit - 分析
 
-[Kubit]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/kubit/)は、インスタントな製品インサイトを提供する、ノーコードのセルフサービス分析プラットフォームです。コード不要のBrazeとのシームレスな統合により、ユーザーコホート情報をBrazeにインポートし、特定のコホートをターゲットにしたエンゲージメントキャンペーンを開始できます。さらに、Snowflakeのセキュアデータ共有を使用することで、Brazeの生のキャンペーンおよびインプレッションデータをKubitの製品分析と統合し、これらのキャンペーンの影響をリアルタイムで測定できます。 
+[Kubit]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/kubit/)は、インスタントな製品インサイトを提供する、ノーコードのセルフサービス分析プラットフォームです。コード不要のBrazeとのシームレスな統合により、ユーザーコホート情報をBrazeにインポートし、特定のコホートをターゲットにしたエンゲージメントキャンペーンを開始できます。また、Snowflake Secure Data Sharing を使用することで、Braze の生のキャンペーンおよびインプレッションデータを Kubit の製品分析と統合し、これらのキャンペーンの効果をリアルタイムで測定できます。 
 
 ### Census - 顧客データプラットフォーム
 
-[Census]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/census/) により、顧客成功、営業、マーケティングの各チームが同じページに留まり、開発部門の継続的な支援なしで顧客データを同期させることができます。
+[Census]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/census/) を使用すると、開発部門からの継続的なサポートなしに、顧客データを同期させ、カスタマーサクセス、営業、マーケティングの各チームの認識を一致させることができます。
 
-### トレジャーデータ - 顧客データプラットフォーム
+### トレジャーデータ- カスタマーデータプラットフォーム
 
-[トレジャーデータ]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/) は、データ、インサイト、エンゲージメントを調和させて完璧なユニゾンで機能させることで、関連性のある顧客体験を促進します。実行可能な指標を備えたCXチームは、マーケティング、営業、顧客サービスを含め、支出を効果的に最適化し、全体のカスタマージャーニーにわたってオムニチャネルのインタラクションをパーソナライズできます。 
+[トレジャーデータ]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/)は、データ、インサイト、エンゲージメントを調和させて最適なカスタマーエクスペリエンスを実現します。実行可能な指標を備えたCXチームは、マーケティング、営業、顧客サービスを含め、支出を効果的に最適化し、全体のカスタマージャーニーにわたってオムニチャネルのインタラクションをパーソナライズできます。 
 
-## ジャカード - AB テスト
+## Jacquard - AB テスト
 
 Brazeカスタマーエンゲージメントは、マルチチャネルマーケティングを通じて関係を構築します。[Jacquard]({{site.baseurl}}/partners/data_and_infrastructure_agility/ab_testing/jacquard/)と協力して、Brazeはブランドの言語を大規模に、ブランドの声に合わせてカスタマイズされたチャネル全体に展開できます。Jacquardのディープラーニングエンジンはテストを処理し、結果を監視し、学習した内容に基づいて新しい言語を生成します。 
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2021/august.md b/_lang/ja/_help/release_notes/2021/august.md
index 0ce1d705c3d..da937c7464a 100644
--- a/_lang/ja/_help/release_notes/2021/august.md
+++ b/_lang/ja/_help/release_notes/2021/august.md
@@ -8,9 +8,9 @@ description: "この記事には2021年8月のリリースノートが含まれ
 
 # 2021年8月
 
-## Google オーディエンス Sync
+## Google オーディエンスの同期
 
-Braze [オーディエンス同期をGoogleに]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/)統合により、ブランドはクロスチャネルの顧客ジャーニーの範囲をGoogle検索、Googleショッピング、Gmail、YouTube、およびGoogleディスプレイに拡張できます。ファーストパーティの顧客データを使用して、ダイナミックな行動トリガー、セグメンテーションなどに基づいて安全に広告を配信できます。Braze キャンバスの一部としてメッセージをトリガーするために通常使用する任意の基準（例えば、プッシュ、メール、SMSなど）を使用して、Googleの顧客マッチを介してそのユーザーに広告をトリガーすることができます。
+Braze [オーディエンス同期をGoogleに]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/)統合により、ブランドはクロスチャネルの顧客ジャーニーの範囲をGoogle検索、Googleショッピング、Gmail、YouTube、およびGoogleディスプレイに拡張できます。ファーストパーティの顧客データを使用して、ダイナミックな行動トリガー、セグメンテーションなどに基づいて安全に広告を配信できます。通常、Braze キャンバスの一部としてメッセージ (プッシュ、メール、SMS など) をトリガーするために使用する基準は、Google のカスタマーマッチを介してそのユーザーに広告をトリガーするために使用できます。
 
 ## ベストプラクティスiOS SDK統合ガイド
 
@@ -22,11 +22,11 @@ Braze [オーディエンス同期をGoogleに]({{site.baseurl}}/partners/canvas
 
 ## ドラッグアンドドロップエディタ
 
-Brazeメールを使用すると、新しい[ドラッグアンドドロップ編集体験]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/)を使用して、キャンペーンやキャンバスのいずれかで完全にカスタムおよびパーソナライズされたメールメッセージを作成できます。ユーザーはエディターブロックをメールにドラッグできるようになり、より直感的なカスタマイズが可能になりました。 
+Braze メールでは、新しい[ドラッグ＆ドロップ編集エクスペリエンス]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/)を使用して、キャンペーンとキャンバスのいずれかで完全なカスタムメールメッセージおよびパーソナライズされたメールメッセージを作成できます。ユーザーはエディターブロックをメールにドラッグできるようになり、より直感的なカスタマイズが可能になりました。 
 
 ## ユーザーエイリアスインポート
 
-`external_id`を持っていないユーザーをターゲットにするには、[ユーザーのエイリアスを持つユーザーのリストをインポートする]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#import-with-user-alias)ことができます。エイリアスは、代替の一意のユーザー識別子として機能します。匿名ユーザーにマーケティングしようとしている場合、アカウントを作成していないユーザーに役立ちます。 
+`external_id`を持たないユーザーを対象にするには、[ユーザー別名を持つユーザーの一覧をインポートすることができます]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#import-with-user-alias)エイリアスは、代替の一意のユーザー識別子として機能します。これは、アプリにサインアップしていないか、アカウントを作成していない匿名ユーザーを対象とするマーケティングを行う場合に役立ちます。 
 
 ## iOS 15 アップグレード ガイド
 
@@ -40,9 +40,9 @@ Brazeメールを使用すると、新しい[ドラッグアンドドロップ
 
 A2P 10DLCは、企業が標準的な10桁の長いコード（10DLC）電話番号を介してアプリケーションから人（A2P）タイプのメッセージングを送信できる米国のシステムを指します。10 桁の長いコードは、従来、個人間（P2P）トラフィック用に設計されていたため、企業はスループットの制限とフィルタリングの強化に悩まされていました。このサービスはこれらの問題を軽減し、全体的なメッセージの配信率を向上させ、ブランドがリンクやアクションを含むメッセージを大量に送信できるようにし、消費者を望まないメッセージからさらに保護するのに役立ちます。 
 
-現在、米国のロングコードを持っているお客様、または米国のお客様に送信するために米国のロングコードを使用しているお客様は、10DLCのためにロングコードを登録する必要があります。10DLCの詳細とその必要性について詳しくは、専用の[10DLC記事]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/10dlc/)をご覧ください。
+米国のロングコードを現在所有しているか、米国の顧客に送信するために使用しているすべてのお客様が、10DLC のロングコードを登録する必要があります。10DLCの詳細とその必要性について詳しくは、専用の[10DLC記事]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/10dlc/)をご覧ください。
 
-## 2 要素認証リセット
+## 2要素認証のリセット
 
 2 要素認証を使用してログインに問題が発生しているユーザーは、会社の管理者に連絡して[2 要素認証をリセット]({{site.baseurl}}/user_guide/administrative/app_settings/company_settings/security_settings/#user-authetication-reset)できます。
 
@@ -50,13 +50,13 @@ A2P 10DLCは、企業が標準的な10桁の長いコード（10DLC）電話番
 
 ### Hightouch - ワークフローオートメーション
 
-Brazeと[Hightouch]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/hightouch/)の統合により、データウェアハウスからの最新の顧客データを使用して、Brazeでより良いキャンペーンを構築できます。お客様に関連性があり、タイムリーなやり取りを提供したいと考えており、そのためにはBrazeアカウントのデータが正確で新鮮であることが非常に重要です。データウェアハウスからBrazeに顧客データを自動的に同期することで、データの一貫性を心配する必要がなくなり、世界クラスの顧客体験の構築に集中できます。
+Brazeと[Hightouch]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/hightouch/)の統合により、データウェアハウスからの最新の顧客データを使用して、Brazeでより良いキャンペーンを構築できます。お客様に関連性があり、タイムリーなやり取りを提供したいと考えており、そのためにはBrazeアカウントのデータが正確で新鮮であることが非常に重要です。顧客データをデータウェアハウスから Braze に自動的に同期させることで、データの整合性を心配する必要がなくなり、世界レベルのカスタマーエクスペリエンスの構築に集中して取り組むことができます。
 
 ### Transcend - データプライバシーとコンプライアンス
 
-Brazeと[Transcend]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_privacy/transcend/)のパートナーシップは、数十のデータシステムにわたるデータを調整することで、ユーザーがプライバシーリクエストを自動化するのに役立ちます。最終的に、これはチームがGDPRやCCPAのような規制に準拠するのを助け、個人が自分のデータに関して主導権を握ることができます。
+Brazeと[Transcend]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_privacy/transcend/)のパートナーシップは、数十のデータシステムにわたるデータを調整することで、ユーザーがプライバシーリクエストを自動化するのに役立ちます。最終的に、これはチームが GDPR や CCPA などの規制に準拠するのに役立ち、個人が自分のデータに関して主導権を握ることができます。
 
-### Tinyclues - コホート Import
+### Tinyclues - コホートインポート
 
 [Tinyclues]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/tinyclues/)は、カスタマーエクスペリエンスを損なうことなくキャンペーン数と収益を増加させる機能を提供するオーディエンス構築機能であり、オンラインおよびオフラインのCRMキャンペーンのパフォーマンスを追跡するための分析を提供します。一緒に、BrazeとTinycluesの統合はユーザーにより良いCRM計画と戦略へのパスを提供し、ユーザーがよりターゲティングされたキャンペーンを送信し、新しい製品機会を見つけ、非常にユーザーフレンドリーなUIを使用して収益を向上させることを可能にします。
 
diff --git a/_lang/ja/_help/release_notes/2021/december.md b/_lang/ja/_help/release_notes/2021/december.md
index f750ac62ab0..34efe844956 100644
--- a/_lang/ja/_help/release_notes/2021/december.md
+++ b/_lang/ja/_help/release_notes/2021/december.md
@@ -13,35 +13,35 @@ alias: "/help/release_notes/2022/january/"
 2021年12月より、[セグメント別ユーザー・エクスポート・エンドポイントについて]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/)、以下の変更が適用される：
 
 1. このAPIリクエストの`fields_to_export` フィールドは必須となる。すべてのフィールドをデフォルトにするオプションは削除される。
-2. `custom_events` 、`purchases` 、`campaigns_received` 、`canvases_received` のフィールドには、過去90日間のデータのみが含まれる。
+2. `custom_events`、`purchases`、`campaigns_received`、`canvases_received` のフィールドには、過去90日間のデータのみが含まれます。
 
 ## カレントのメッセージ・エンゲージメント・イベントの新しいプロパティ
 
-一部の[メッセージ・エンゲージメント・イベントに]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)新しいプロパティが追加された。このアップデートは、以下のCurrentsメッセージエンゲージメントイベントと、それらを使用するすべてのパートナーに適用される：
+一部の[メッセージ・エンゲージメント・イベントに]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)新しいプロパティが追加された。この更新は、以下の Currents メッセージエンゲージメントイベントと、それらを使用するすべてのパートナーに適用されます。
 
-- `LINK_ID`,`LINK_ALIAS` を加える：
-  - Eメールクリック（すべての宛先）
-- `USER_AGENT` ：
-  - Eメールオープン
-  - Eメールクリック
+- `LINK_ID`、`LINK_ALIAS` を以下に追加します。
+  - メールクリック(すべての送信先)
+- `USER_AGENT` を以下に追加します。
+  - メール開封
+  - メールのクリック
   - 迷惑メールとしてマークする
-- `MACHINE_OPEN` ：
-  - Eメールオープン
+- `MACHINE_OPEN` を以下に追加します。
+  - メール開封
 
-## 新リキッド名入れタグ
+## 新流動パーソナライゼーション タグ
 
-以下のリキッドタグで、フォアグラウンドプッシュを有効にしているユーザーをターゲットにできるようになった：
+次の Liquid タグを使用して、デバイスでフォアグラウンドプッシュが有効になっているユーザーへのターゲット設定をサポートします。
 
 {% raw %}
 - `{{most_recently_used_device.${foreground_push_enabled}}}`
 - `{{targeted_device.${foreground_push_enabled}}}`
 {% endraw %}
 
-詳しくは、[サポートされるパーソナライズタグを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/)参照のこと。
+詳細については、[サポートされるパーソナライゼーション タグs]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/)を参照してください。
 
 ## ウェブフックについて
 
-Webhookは強力で柔軟なツールだが、少しわかりにくいかもしれない。Webhookとは何なのか、Brazeでどのように使えるのか気になる方は、[Webhookについての]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/understanding_webhooks/)新しい記事をチェックしよう。
+Webhookは強力で柔軟なツールだが、少しわかりにくいかもしれない。どのようなwebhookがあり、どのようにBrazeでそれらを使用できるか気になる場合は、[webhookについて]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/understanding_webhooks/)の新しい記事をご覧ください。
 
 ## Amazon Personalize
 
@@ -49,12 +49,12 @@ Amazon Personalizeは、Amazonの機械学習によるレコメンデーショ
 
 さらに詳しく知りたい方は、[Amazon Personalizeの]({{site.baseurl}}/partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize/)新しい記事を参照し、Amazon Personalizeが提供するユースケース、Amazon Personalizeが扱うデータ、サービスの設定方法、Brazeとの統合方法について理解しよう。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
 ### Yotpo - Eコマース
 
-[Yotpoと]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/yotpo/)Brazeの統合により、Braze内のEメールやその他のコミュニケーションチャンネルで、製品に関する星評価、トップレビュー、視覚的なユーザー生成コンテンツを動的に取得し、表示することができる。また、顧客レベルのロイヤルティデータをEメールやその他のコミュニケーション手段に含めることで、よりパーソナライズされたインタラクションを実現し、売上とロイヤルティを高めることができる。
+[Yotpo]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/yotpo/) と Braze の統合により、Braze 内のメールや他の通信チャネル内で、製品の星の評価、トップレビュー、視覚的なユーザー生成コンテンツを動的に取得して表示できます。また、顧客レベルのロイヤルティデータをメールやその他のコミュニケーション手段に組み込むこで、よりパーソナライズされたインタラクションを実現し、売上とロイヤルティを高めることができます。
 
 ### Zeotap - 顧客データプラットフォーム
 
-[Zeotapと]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/zeotap/)Brazeの統合により、Zeotap顧客セグメントを同期してZeotapユーザーデータをBrazeユーザーアカウントにマッピングすることで、キャンペーンの規模とリーチを拡大することができる。そして、このデータに基づいて行動し、ユーザーにパーソナライズされたターゲット体験を提供することができる。
\ No newline at end of file
+[Zeotap]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/zeotap/) と Braze の統合により、Zeotap の顧客セグメントを同期して Zeotap のユーザーデータを Braze のユーザーアカウントにマッピングすることで、キャンペーンの規模と範囲を拡張できます。そして、このデータに基づいて行動し、ユーザーにパーソナライズされたターゲット体験を提供することができる。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2021/february.md b/_lang/ja/_help/release_notes/2021/february.md
index cdda3db77a7..68e7e39c0cb 100644
--- a/_lang/ja/_help/release_notes/2021/february.md
+++ b/_lang/ja/_help/release_notes/2021/february.md
@@ -9,9 +9,9 @@ description: "この記事には、2021年2月のリリースノートが含ま
 
 ## 迅速なアップデート
 
-2021年3月22日以降、Brazeサービスでは、TLS接続がサーバー名表示（SNI）をサポートする必要がある。これは、上流のコンテンツ配信ネットワークFastlyが、すべてのTLSトラフィックをSNIを必要とするように移行するためである。最新のブラウザ、OS、HTTPS接続プロトコルはすべてSNIをサポートしている。SNIに対応していないデバイスはBrazeに接続できなくなる。当社のトラフィック予測によれば、これはエンドユーザー・デバイスの約0.000001%である。
+2021年3月22日以降、Brazeサービスでは、TLS接続がサーバー名表示（SNI）をサポートする必要がある。これは、上流のコンテンツ配信ネットワークFastlyが、すべてのTLSトラフィックをSNIを必要とするように移行するためである。最新のブラウザ、オペレーティングシステム、およびHTTPS 接続プロトコルはすべてSNI に対応しています。SNIに対応していないデバイスはBrazeに接続できなくなる。当社のトラフィック予測によれば、これはエンドユーザー・デバイスの約0.000001%である。
 
 ## オーディエンスパス
 
-[Canvas Audience Pathsは]({{site.baseurl}}/audience_paths/)、戦略的な優先順位に基づいたユーザーグループ分けによって、大規模なユーザーを直感的にフィルタリングし、セグメント化することができる。この新しいキャンバス・ステップは、過剰なオーディエンス・ベースのフル・ステップを作成する必要性に取って代わり、8つのフル・ステップを1つにまとめることができる！この新しいステップを導入することで、ユーザーターゲティングを簡素化し、キャンバスを不必要なごちゃごちゃ感や複雑さから解放することができる。
+[キャンバスのオーディエンスパス]({{site.baseurl}}/audience_paths/)では、戦略的な優先順位に基づいたユーザーのグループ化を行って、ユーザーを大規模に直感的にフィルタリングしてセグメント化することができます。この新しいキャンバスステップは、過剰なオーディエンスベースのフルステップを作成する必要をなくし、8つのフルステップを1つにまとめることを可能にします。この新しいステップの導入は、不必要に複雑になったキャンバスを整理してユーザーのターゲット設定を簡素化するのに役立ちます。
 
diff --git a/_lang/ja/_help/release_notes/2021/january.md b/_lang/ja/_help/release_notes/2021/january.md
index cf8c8a91378..d6f998060f1 100644
--- a/_lang/ja/_help/release_notes/2021/january.md
+++ b/_lang/ja/_help/release_notes/2021/january.md
@@ -9,25 +9,25 @@ description: "この記事には、2021年1月のリリースノートが含ま
 
 ## キャンバスレポートビルダー
 
-レポートビルダーを使用すると、複数のキャンペーンまたはキャンバスの結果を 1 つのビューで比較できるため、主要な指標に最も影響を与えたエンゲージメント戦略を簡単に判断できます。[キャンバス・レポート・ビルダーについて]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/)もっと読む。
+レポートビルダーを使用すると、複数のキャンペーンまたはキャンバスの結果を 1 つのビューで比較できるため、主要な指標に最も影響を与えたエンゲージメント戦略を簡単に判断できます。[Canvas Report Builder]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/)について詳しく説明します。
 
 ## アプリ内メッセージ iOS実装ガイド
 
-この詳細なガイドでは、サブクラス化を活用して、BrazeのキャンペーンやCanvasに追加するカスタムスライドアップアプリ内メッセージ、カスタムモーダルアプリ内メッセージ、カスタムフルアプリ内メッセージを作成する方法を説明する。必要なコードの検討、我々のチームによって構築された詳細な使用例、付随するコード・スニペットも含まれている。詳しくは[こちらの]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/in-app_messaging/implementation_guide/)ドキュメントをご覧いただきたい。 
+この詳細なガイドでは、サブクラス化を活用して、BrazeのキャンペーンやCanvasに追加するカスタムスライドアップアプリ内メッセージ、カスタムモーダルアプリ内メッセージ、カスタムフルアプリ内メッセージを作成する方法を説明する。必要なコードの検討、我々のチームによって構築された詳細な使用例、付随するコード・スニペットも含まれている。詳しくは、ドキュメント[ここ]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/in-app_messaging/implementation_guide/)をご覧ください。 
 
 ## SMSカスタムキーワードカテゴリとリターゲティングオプション
 
 BrazeはネイティブSMSの機能を拡張し、双方向メッセージングのためのカスタムキーワードの追加、キーワードのカスタムカテゴリー、多言語サポート、キーワードのリターゲティングとフィルタリングオプションなどの機能を追加した。SMSキーワード処理の詳細については、[SMSドキュメントを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/keyword_handling/)参照のこと。 
 
-## プレイアブル・パートナーシップが始動
+## Playable のパートナーシップが開始
 
-BrazeのEメール機能を拡張し、最高のコンテンツ（高品質ビデオ）を最高のオーディエンス（Eメール）に届ける[。]({{site.baseurl}}/partners/playable/)再生可能な動画メールは、受信ボックス内で自動的に再生されるエキサイティングで高品質な動画コンテンツで、クリックスルーとクリック後の指標を高めることができる。 
+Braze のメール機能を拡張し、[Playable]({{site.baseurl}}/partners/playable/) で最高のコンテンツ(高品質動画) を最高のオーディエンス(メール) に提供します。再生可能な動画メールは、受信ボックス内で自動的に再生されるエキサイティングで高品質な動画コンテンツで、クリックスルーとクリック後の指標を高めることができる。 
 
 ## Zendeskとのパートナーシップが始動
 
-[Zendesk Support Suite（ZSS]({{site.baseurl}}/partners/zendesk/)）は、Eメール、ウェブチャット、音声、ソーシャルメッセージングアプリを使ったオムニチャネルサポートを通じて、顧客との自然な会話を可能にする。ZSSはインタラクションの追跡と優先順位付けを通じてカスタマーサポートを評価し、企業が顧客に関する統一された履歴ビューを持つことを可能にする。合理化された発券システムのような強力なツールによって、企業はパーソナライズされたアプローチで顧客に直接働きかけることができる。Brazeは、Zendeskとのサーバー間統合を提供しており、BrazeとZendesk間でサポートチケットデータを同期できるBrazeのウェブフックを利用できる。 
+[Zendesk Support Suite（ZSS]({{site.baseurl}}/partners/zendesk/)）は、Eメール、ウェブチャット、音声、ソーシャルメッセージングアプリを使ったオムニチャネルサポートを通じて、顧客との自然な会話を可能にする。ZSSはインタラクションの追跡と優先順位付けを通じてカスタマーサポートを評価し、企業が顧客に関する統一された履歴ビューを持つことを可能にする。合理化されたチケット発行システムなどの強力なツールにより、企業はパーソナライズされたアプローチで顧客に直接リーチできるようになります。Braze が Zendesk とのサーバー間統合を提供するため、Braze と Zendesk 間でサポートチケットデータを同期できる Braze webhook を利用できます。 
 
-## クラウディン・パートナーシップが始動
+## Crowdin のパートナーシップが開始
 
-[Crowdinは]({{site.baseurl}}/partners/crowdin/)、ローカライゼーション管理のためのクラウドベースのソフトウェアである。BrazeとCrowdinの統合により、メールテンプレートやコンテンツブロックの翻訳が可能に。BrazeアカウントからCrowdinプロジェクトにコンテンツを同期し、Brazeに戻って翻訳を追加できる。
+[Crowdin]({{site.baseurl}}/partners/crowdin/)は、ローカライゼーションマネジメントのためのクラウドベースのソフトウエアです。Braze と Crowdin の統合により、メールテンプレートとコンテンツブロックを翻訳できます。Braze アカウントから Crowdin プロジェクトにコンテンツを同期し、Braze に戻って翻訳を追加できます。
 
diff --git a/_lang/ja/_help/release_notes/2021/july.md b/_lang/ja/_help/release_notes/2021/july.md
index a0271b5d893..527e3a246f0 100644
--- a/_lang/ja/_help/release_notes/2021/july.md
+++ b/_lang/ja/_help/release_notes/2021/july.md
@@ -10,19 +10,19 @@ description: "この記事には2021年7月のリリースノートが含まれ
 
 ## アプリ内の簡単なアンケートメッセージ
 
-[シンプルなアプリ内メッセージテンプレートを使って]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/)、キャンペーン戦略に役立つユーザー属性、洞察、嗜好を収集しよう。例えば、ユーザーにアプリをどのように使いたいかを尋ねたり、個人的な嗜好を詳しく知ったり、特定の機能に対する満足度を尋ねたりすることもできる。このアンケートテンプレートは、モバイルアプリとウェブブラウザの両方に対応している。
+[簡単な調査アプリ内メッセージテンプレート]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/)を使用して、キャンペーン戦略を強化するユーザー属性、インサイト、および好みを収集します。例えば、ユーザーにアプリをどのように使いたいかを尋ねたり、個人的な好みについて詳しく知ったり、特定の機能に対する満足度を質問したりすることができます。このアンケートテンプレートは、モバイルアプリとウェブブラウザの両方に対応している。
 
-## 液体ユースケース・ライブラリ
+## 流動ユースケース ライブラリー
 
-リキッドでその1つのことを行うにはどうすればいいのか？インスピレーションを探している？記念日や誕生日、プラットフォームターゲティングなど、様々なユースケースを集めた[Liquidユースケースライブラリを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases/)チェックしよう。
+Liquid でその1つのことを実行する方法を知りたいですか?インスピレーションが必要なだけですか?記念日や誕生日、プラットフォームターゲティングなど、様々なユースケースを集めた[Liquidユースケースライブラリを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases/)チェックしよう。
 
 ## 電子メール追跡
 
-オープン・ピクセル・トラッキングとクリック・トラッキングをユーザー・プロファイルごとに無効にできるようになった。この柔軟性は、個々のユーザー・プロフィールが追跡されることを望まないことを示すような、地域の個人情報保護法をサポートするのに役立つ。詳しくは、[Eメール・トラッキングの]({{site.baseurl}}/user_guide/data_and_analytics/tracking/email_tracking/)記事をご覧いただきたい。
+開封ピクセル追跡とクリック追跡を、ユーザープロファイルごとに無効にできるようになりました。このような柔軟性があるため、お客様がが各自のユーザープロファイルを追跡対象外と指定したときに地域の個人情報保護法を遵守できます。詳しくは、[Eメール・トラッキングの]({{site.baseurl}}/user_guide/data_and_analytics/tracking/email_tracking/)記事をご覧いただきたい。
 
-## SDKデータ収集オプション
+## SDK によるデータ収集のオプション
 
-柔軟なデータ収集を可能にするBraze SDKの統合方法については、[SDKデータ収集オプションに関する]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/sdk_data_collection/)新しいドキュメントを参照。
+Braze SDK を統合して柔軟なデータ収集を可能にする方法について詳しくは、[SDK データ収集オプション]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/sdk_data_collection/)に関する新しいドキュメントをご覧ください。
 
 ## SSLの概要
 
@@ -30,8 +30,8 @@ BrazeのSSLについての詳細、SSLが重要な理由、SSL証明書の取得
 
 ## AmplitudeユーザープロファイルAPIエンドポイント
 
-AmplitudeのUser Profile APIは、Amplitudeのユーザープロファイルを提供する。これには、ユーザー・プロパティ、計算されたユーザー・プロパティ、ユーザーを含むコホートのコホートIDのリスト、および推奨事項が含まれる。詳しくは[Amplitude User Profile API Endpointsを]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api/)参照のこと。
+Amplitude のユーザープロファイル API はAmplitude ユーザープロファイル に対応しています。これには、ユーザー・プロパティ、計算されたユーザー・プロパティ、ユーザーを含むコホートのコホートIDのリスト、および推奨事項が含まれる。詳細については、[AmplitudeユーザプロファイルAPI エンドポイント]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api/)を参照してください。
 
 ## キャンペーン詳細エンドポイント 
 
-[`/campaigns/details` エンドポイントに]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/)、アプリ内メッセージチャンネル専用の`message` レスポンスが追加された。これに関するドキュメントは[こちらで]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/#messages)見ることができる。
\ No newline at end of file
+[`/campaigns/details` エンドポイントに]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/)、アプリ内メッセージチャンネル専用の`message` レスポンスが追加された。これに関するドキュメントは、[ここで]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/#messages)にあります。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2021/june.md b/_lang/ja/_help/release_notes/2021/june.md
index 5636d84faf7..b6d3f82f2e8 100644
--- a/_lang/ja/_help/release_notes/2021/june.md
+++ b/_lang/ja/_help/release_notes/2021/june.md
@@ -8,37 +8,37 @@ description: "この記事には、2021年6月のリリースノートが含ま
 
 # 2021年6月
 
-## 取引メールキャンペーン
+## トランザクションメールキャンペーン
 
-トランザクションメールとは、送信者と受信者の間で合意されたトランザクションを促進するために送信されるメールである。Brazeの[トランザクションメールキャンペーンは]({{site.baseurl}}/api/api_campaigns/transactional_campaigns)、注文確認、パスワードリセット、請求アラート、その他のビジネスクリティカルな通知など、自動化された非宣伝的なメールメッセージの送信を目的として構築されている。さらに、対応する[トランザクションEメール・エンドポイントが]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_transactional_message/)作成された。トランザクションメールと新しいエンドポイントは、一部のBrazeパッケージでのみ利用できる。 
+トランザクションメールは、送信者と受信者間で合意されたトランザクションを円滑に進めるために送信されます。Brazeの[トランザクションメールキャンペーンは]({{site.baseurl}}/api/api_campaigns/transactional_campaigns)、注文確認、パスワードリセット、請求アラート、その他のビジネスクリティカルな通知など、自動化された非宣伝的なメールメッセージの送信を目的として構築されている。また、対応する[trans アクション al メール エンドポイント]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_transactional_message/)が作成されました。トランザクションメールと新しいエンドポイントは、一部の Braze パッケージのみで使用できます。 
 
 ## イベント・プロパティのネストされたオブジェクトのサポート
 
-Brazeは、カスタムイベントと購入イベントの[ネストされたオブジェクトを]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/nested_object_support/)サポートするようになった。ネストされたオブジェクトによって、カスタム・イベントや購入のプロパティとしてデータの配列を送ることができる。このネストされたデータは、Liquidとドット記法を使用することで、APIトリガーメッセージにパーソナライズされた情報をテンプレート化するために使用することができる。
+Braze で、カスタムイベントおよび購入イベントの[ネストされたオブジェクト]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/nested_object_support/)がサポートされるようになりました。ネストされたオブジェクトによって、カスタム・イベントや購入のプロパティとしてデータの配列を送ることができる。このネストされたデータは、Liquidとドット記法を使用することで、APIトリガーメッセージにパーソナライズされた情報をテンプレート化するために使用することができる。
 
-## 新しいHMACリキッドフィルター
+## 新しい HMAC Liquid フィルター
 
-新しい[`hmac_sha1` と`hmac_sha256` リキッド・エンコーディング・フィルターが]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/)Brazeプラットフォームに追加された。
+新しい[`hmac_sha1`と`hmac_sha256`リキッドエンコードフィルターs]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/)がBraze プラットフォームに追加されました。
 
 ## 購入イベントページ
 
-ブレイズでの購入イベントの詳細について興味がある？詳しくは[購入イベントの]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/)記事をご覧いただきたい。
+Brazeでの買い物の内容は気になりますか？詳しくは[購入イベントの]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/)記事をご覧いただきたい。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
 ### Nexla - ワークフローの自動化
 
-[ネクスラは]({{site.baseurl}}/partners/nexla)ユニファイド・データ・オペレーションのリーダーであり、2021年ガートナー・クールベンダーに選ばれている。Currentsを使ってデータをデータウェアハウスに送信している顧客は、Nexlaを活用してデータを抽出、変換し、他の場所にロードすることで、エコシステム全体でデータに簡単にアクセスできるようになる。Nexlaは、Braze Currentsを使用することで、簡単なポイント＆クリックで、カスタムフォーマットのデータを希望の宛先に配信することができる。 
+[Nexla]({{site.baseurl}}/partners/nexla) は統合データ運用分野のリーダーであり、2021年の Gartner Cool Vender に選出されています。Currents を使用してデータウェアハウスにデータを送信するお客様は、Nexla を活用してそのデータを抽出、変換し、他の場所に読み込むことで、エコシステム全体でデータに簡単にアクセスできるようになります。Nexla により、Braze Currents を使用して、ポイントアンドクリックするだけで、カスタム形式のデータを任意の宛先に配信できます。 
 
 ### Amperity - 顧客データプラットフォーム
 
-[Amperityは]({{site.baseurl}}/partners/amperity/)、包括的な企業向け顧客データプラットフォームであり、ブランドが顧客を知り、戦略的な意思決定を行い、消費者により良いサービスを提供するために常に正しい行動をとることを支援する。Amperityは、CDPとBrazeにまたがる顧客の統一ビューを提供することで、Brazeプラットフォームをサポートし、貴重なAmperityデータをBrazeに送信できるようにする。
+[Amperity]({{site.baseurl}}/partners/amperity/)は、包括的なエンタープライズ顧客データプラットフォームであり、ブランドが自社の顧客を知り、戦略的な意思決定を行い、自社の消費者により良く奉仕するために適切なアクションを一貫して取ることを支援する。Amperity は、顧客データプラットフォームと Braze 全体で顧客の統合ビューを提供し、貴重な Amperity データを Braze に送信できるようにすることで、Braze プラットフォームをサポートします。
 
-### デジオ - アンケート
+### Digioh - アンケート
 
-[Digiohは]({{site.baseurl}}/partners/digioh/)、リストを増やし、ファーストパーティデータを取得し、そのデータをBrazeのキャンペーンに活用することを支援する。ドラッグ＆ドロップのビルダーで、顧客とつながるオンブランドのフォーム、ポップアップ、プリファレンスセンター、ランディングページ、アンケートを簡単に作成できる。
+[Digioh]({{site.baseurl}}/partners/digioh/) は、リストの拡大、ファーストパーティデータの取り込み、Braze キャンペーンでのデータの利用を支援します。ドラッグ＆ドロップビルダーを使用すると、ブランドに合わせたフォーム、ポップアップ、ユーザー設定センター、ランディングページ、顧客とのつながりを築くアンケートなどを簡単に作成できます。
 
-### AppsFlyer Audiences - アトリビューション/アナリティクス
+### AppsFlyer オーディエンス- 属性/分析
 
-[AppsFlyerは]({{site.baseurl}}/partners/message_orchestration/attribution/appsflyer/)モバイルマーケティング分析とアトリビューションプラットフォームであり、マーケティング分析モバイルアトリビューションとディープリンクを通じてアプリの分析と最適化を支援する。[AppsFlyer Audiencesは]({{site.baseurl}}/partners/appsflyer_audiences/)、オーディエンスセグメントを構築し、これらのセグメントを直接Brazeに渡すことで、強力な顧客エンゲージメントキャンペーンを作成することができる。
+[AppsFlyer]({{site.baseurl}}/partners/message_orchestration/attribution/appsflyer/) は、モバイルマーケティングにおける分析やアトリビューションを計測するプラットフォームです。マーケティング分析、モバイルアトリビューション、ディープリンクにより、アプリの分析と最適化を支援します。[AppsFlyer Audiences]({{site.baseurl}}/partners/appsflyer_audiences/) を使用すると、オーディエンスセグメントを構築し、これらのセグメントを直接 Braze に渡して、強力なカスタマーエンゲージメントキャンペーンを作成できます。
 
diff --git a/_lang/ja/_help/release_notes/2021/march.md b/_lang/ja/_help/release_notes/2021/march.md
index 7964719563e..ed73ed35c21 100644
--- a/_lang/ja/_help/release_notes/2021/march.md
+++ b/_lang/ja/_help/release_notes/2021/march.md
@@ -7,14 +7,14 @@ description: "この記事には、2021年3月のリリースノートが含ま
 ---
 # 2021年3月
 
-## セグメント延長
+## セグメント拡張
 
-[Segment Extensionは]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension)、既存のセグメンテーション機能を拡張するもので、過去365日間のカスタムイベントや購買行動に基づいて、より正確なユーザーリストをターゲットにすることができる。これらの拡張子リストが生成されると、セグメントでフィルターとして含めたり除外したりすることができる。Segment Extensionを作成する際、24時間に1回リストを再生成するように指定することもできる。
+[Segment Extensionは]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension)、既存のセグメンテーション機能を拡張するもので、過去365日間のカスタムイベントや購買行動に基づいて、より正確なユーザーリストをターゲットにすることができる。これらのエクステンションリストは、生成後にセグメントにフィルターとして含めるか、除外することができます。セグメントエクステンションを作成するときに、24時間ごとにリストを再生成するように指定することもできます。
 
 ## A2P 10DLC
 
-A2P 10DLCとは、企業が標準的な10桁のロングコード（10DLC）電話番号を使ってアプリケーション・ツー・パーソン（A2P）タイプのメッセージングを送信できる米国のシステムを指す。10桁のロングコードは従来、個人間（P2P）トラフィック用に設計されてきたため、スループットの制限やフィルタリングの強化によってビジネスが制約を受ける原因となっていた。現在ロングコードをお持ちのお客様、またはロングコードをご利用のお客様は、10DLCにロングコードを登録する必要がある。詳しくは[A2P 10DLCの]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup/short_and_long_codes/#application-to-person-10-digit-long-codes-a2p-10dlc)記事を参照されたい。
+A2P 10DLCとは、企業が標準的な10桁のロングコード（10DLC）電話番号を使ってアプリケーション・ツー・パーソン（A2P）タイプのメッセージングを送信できる米国のシステムを指す。10桁のロングコードは従来、個人間（P2P）トラフィック用に設計されてきたため、スループットの制限やフィルタリングの強化によってビジネスが制約を受ける原因となっていた。現在ロングコードをお持ちのお客様、またはロングコードをご利用のお客様は、10DLCにロングコードを登録する必要がある。詳細については、[A2P 10DLC]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup/short_and_long_codes/#application-to-person-10-digit-long-codes-a2p-10dlc) の記事を参照してください。
 
 ## グローバル・コントロール・グループ
 
-[グローバル・コントロール・グループによって]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/)、メッセージング活動の全体的な影響を長期にわたって分析することができる。これらのグループは、メッセージを受け取ったユーザーとそうでないユーザーの行動を比較することで、マーケティングキャンペーンやCanvasesがセッションやカスタムイベントの増加にどのようにつながるかを理解するのに役立つ。 
\ No newline at end of file
+[グローバルコントロールグループ]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/)を使用すると、メッセージング作業の経時的な効果を分析できます。これらのグループは、メッセージを受け取ったユーザーとそうでないユーザーの行動を比較することで、マーケティングキャンペーンやCanvasesがセッションやカスタムイベントの増加にどのようにつながるかを理解するのに役立つ。 
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2021/may.md b/_lang/ja/_help/release_notes/2021/may.md
index b8696d6f5d7..39b047bb80e 100644
--- a/_lang/ja/_help/release_notes/2021/may.md
+++ b/_lang/ja/_help/release_notes/2021/may.md
@@ -12,9 +12,9 @@ description: "この記事には、2021年5月のリリースノートが含ま
 
 このガイドでは、**キャンペーン分析**ページの[コンバージョン相関]({{site.baseurl}}/user_guide/engagement_tools/testing/conversion_correlation/)分析について説明する。この分析では、キャンペーンに設定した成果に対して、どのようなユーザー属性や行動が役立つのか、あるいは不利になるのかを知ることができる。分析の概要、何をチェックするのか、いつチェックできるのか、そしてBrazeがどのように有意性をチェックするのかについて説明する。
 
-## グローバル・コントロール・グループのレポート
+## グローバルコントロールグループレポート
 
-[グローバルコントロールグループレポートの]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/)指標を更新し、長期的なメッセージング活動の全体的な影響を分析しやすくした。主な変更点としては、**ユーザーあたりのイベント**数と**推定グループサイズを**追加し、**増分アップリフトの**計算を調整し、治療グループと対照グループのイベント総数の差を反映させる。
+[Global Control Groups]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/)レポートのメトリクスを更新し、メッセージングの取り組みの全般的な影響をより適切に分析できます。主な変更点には、**ユーザーあたりのイベント数**と**推定グループサイズ**の追加、トリートメントグループとコントロールグループ間の合計イベント数の差異を反映するための**増分上昇**計算の調整が含まれます。
 
 ## レポートの概要
 
@@ -22,15 +22,15 @@ description: "この記事には、2021年5月のリリースノートが含ま
 
 ## 新しいUS-05クラスター
 
-Brazeは新しいUSクラスタ、US-05をサポートしている。詳しくは、ダッシュボードとREST[エンドポイントの]({{site.baseurl}}/api/basics/#endpoints)リストを参照のこと。
+Brazeは新しいUSクラスタ、US-05をサポートしている。詳細については、ダッシュボードとRESTの一覧[エンドポイント]({{site.baseurl}}/api/basics/#endpoints)を参照してください。
 
 ## BrazeのUIアップデート
 
-2021年5月、BrazeはBrazeダッシュボードの以下のラベルと用語を更新した：
+2021年5月、Braze は Braze ダッシュボードで以下のラベルと用語を更新しました。
 
-- アプリの使い方 --> 概要
-- アプリの設定 --> 設定
+- アプリケーションの使用状況--> 概要
+- アプリ設定 --> 設定
 - アプリグループを管理する --> 設定を管理する
-- アプリ内で使ったお金 --> 使ったお金
-- アプリの使用状況（ユーザープロファイル）→セッションの概要
-- ユーザー情報のCSVをインポートして、このApp Groupにユーザーを追加・更新する --> ユーザー情報のCSVをインポートして、ユーザーを追加・更新する
+- アプリに費やした金額 --> 支出した金額
+- アプリの利用状況 (ユーザープロファイル) --> セッションの概要
+- このアプリグループでユーザーを追加または更新するには、CSV 形式のユーザー情報をインポートします --> ユーザーを追加または更新するには、CSV 形式のユーザー情報をインポートします
diff --git a/_lang/ja/_help/release_notes/2021/november.md b/_lang/ja/_help/release_notes/2021/november.md
index 68fc8ddc05e..0d357517167 100644
--- a/_lang/ja/_help/release_notes/2021/november.md
+++ b/_lang/ja/_help/release_notes/2021/november.md
@@ -7,44 +7,44 @@ description: "この記事には、2021年11月のリリースノートが含ま
 ---
 # 2021年11月
 
-## クリック・ツー・オープン率報告指標
-Brazeは、[レポートビルダーで]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/)利用可能な新しいメール指標「クリック・ツー・オープン率」を追加した。この指標は、開封されたメールのうち、クリックされたメールの割合を表している。
+## クリック開封率レポートメトリック
+Brazeは、[レポートビルダーで]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/)利用可能な新しいメール指標「クリック・ツー・オープン率」を追加した。このメトリックは、クリックされた開封メールの割合を表します。
 
-## マシン・オープン レポート指標
+## マシン開封レポートメトリック
 
 キャンバスとキャンペーンアナリティクスのEメールページで、新しいEメール指標「[マシンオープンズ]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/analytics_glossary/#machine-opens)」が利用できるようになった。この指標は、（Appleのサーバーによって開封されたような）人為的ではないメール開封を特定するもので、開封総数のサブセットとして表示される。
 
 ## random_bucket_number Liquid variable
-メッセージのパーソナライズ用に[サポートされているリキッド変数の]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#supported-personalization-tags)リストに、変数`random_bucket_number` が追加された。 
+メッセージパーソナライゼーションの[サポートされている Liquid 変数]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#supported-personalization-tags)のリストに、変数 `random_bucket_number` が追加されました。 
 
 ## iOS 15のリッチプッシュ通知ガイドライン
 新しい[iOSプッシュ通知ガイドラインが]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/rich_notifications/)iOSリッチドキュメントに追加され、通知状態に関する情報とテキスト切り捨て変数の内訳が含まれる。
 
 ## EUでウェブフックとコネクテッド・コンテンツのホワイトリストに登録するIP
-EUでウェブフックとコネクテッド・コンテンツのホワイトリストに追加するIPが、[ウェブフックと]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/) [コネクテッド・コンテンツの]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call/)記事に追加された。これらの新規IPには、`18.157.135.97` 、`3.123.166.46` 、`3.64.27.36` 、`3.65.88.25` 、`3.68.144.188` 、`3.70.107.88` が含まれる。
+EUでウェブフックとコネクテッド・コンテンツのホワイトリストに追加するIPが、[ウェブフックと]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/) [コネクテッド・コンテンツの]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call/)記事に追加された。これらの新しい IP には `18.157.135.97`、`3.123.166.46`、`3.64.27.36`、`3.65.88.25`、`3.68.144.188`、`3.70.107.88` が含まれます。
 
-## 輸出購入エンドポイント
+## 購入エンドポイントをエクスポートする
 Brazeに新しい[エンドポイント（`/purchases/product_list` ）が]({{site.baseurl}}/api/endpoints/export/purchases/get_list_product_id/)追加された。このエンドポイントは、製品IDのページ分割されたリストを返す。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
 ### アドビ - 顧客データプラットフォーム
-Brazeと[Adobeの]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/adobe/#adobe)統合により、ブランドはAdobeデータ（カスタム属性とセグメント）をリアルタイムでBrazeに接続し、マッピングすることができる。そして、ブランドはこのデータに基づいて行動し、ユーザーにパーソナライズされたターゲット体験を提供することができる。 
+Braze と [Adobe]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/adobe/#adobe) の統合により、ブランドはリアルタイムで Braze に接続し、Adobe データ (カスタム属性とセグメント) を Braze にマッピングできます。そうすれば、ブランドはこの情報に基づいて行動し、パーソナライズされたなターゲットを絞った体験をユーザーに提供することができる。 
 
 ### BlueConic - 顧客データプラットフォーム
-[Blueconicにより]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/blueconic/#blueconic)、Brazeのユーザーは、データを永続的な個別プロファイルに統合し、顧客ライフサイクルのオーケストレーション、モデリングと分析、デジタル製品と体験、オーディエンスベースの収益化など、成長に焦点を当てた幅広いイニシアチブをサポートするために、顧客接点とシステム間で同期させることができる。
+[Blueconic]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/blueconic/#blueconic) を使用すると、Braze ユーザーはデータを永続的な個別のプロファイルに統合し、顧客タッチポイントやシステムを横断して同期して、カスタマーライフサイクルオーケストレーション、モデリングと分析、デジタル製品とエクスペリエンス、オーディエンスベースの収益化など、成長に重点を置いた幅広いイニシアチブをサポートできます。
 
 ### 価値がある - ダイナミックなコンテンツ
-Brazeと[Worthyの]({{site.baseurl}}/partners/message_personalization/dynamic_content/worthy/#worthy)統合により、Worthyのドラッグアンドドロップ・ダイナミック・コンテンツ・エディタを使って、パーソナライズされたリッチなアプリ内体験を簡単に作成し、Brazeを通じて配信することができる。
+Braze と [Worthy]({{site.baseurl}}/partners/message_personalization/dynamic_content/worthy/#worthy) の統合により、Worthy のドラッグ＆ドロップダイナミックコンテンツエディターを使用して、パーソナライズされたリッチなアプリ内エクスペリエンスを簡単に作成し、Braze を通じて提供できるようになります。
 
 ### 柔道 - ダイナミックコンテンツ
-[Judoと]({{site.baseurl}}/partners/message_personalization/dynamic_content/judo/#judo)Brazeの統合により、キャンペーンのコンポーネントを上書きし、Judoのエクスペリエンスに置き換えることができる。Brazeのデータは、柔道体験においてパーソナライズされたコンテンツをサポートするために使用されることがある。ユーザーイベントとエクスペリエンスからのデータは、アトリビューションとターゲティングのためにBrazeにフィードバックできる。
+[Judo]({{site.baseurl}}/partners/message_personalization/dynamic_content/judo/#judo)とBrazeインテグレーションを使用すると、Judoのエクスペリエンスでキャンペーンのコンポーネントを上書きして置き換えることができます。Braze のデータは、Judo エクスペリエンスでパーソナライズされたコンテンツをサポートするために使用できます。ユーザーイベントとエクスペリエンスからのデータは、アトリビューションとターゲティングのためにBrazeにフィードバックできる。
 
 ### ライン - メッセージング
-[LINEと]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/line/#line)Brazeの統合により、Brazeのウェブフック、高度なセグメンテーション、パーソナライゼーション、トリガー機能を活用し、[LINE Messaging APIを通じて](https://developers.line.biz/en/docs/messaging-api/overview/)LINEのユーザーにメッセージを送ることができる。
+[LINE]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/line/#line) と Braze の統合により、[Line メッセージング API](https://developers.line.biz/en/docs/messaging-api/overview/) を介し、Braze の Webhook、高度なセグメンテーション、パーソナライゼーション、およびトリガー機能を利用して、Line のユーザーにメッセージを送信できます。
 
-### RevenueCat - ペイメント
-[RevenueCatと]({{site.baseurl}}/partners/data_and_infrastructure_agility/payments/revenuecat/#revenuecat)Brazeの統合により、顧客の購入と購読のライフサイクルイベントをプラットフォーム間で自動的に同期することができる。これにより、無料トライアル中にオプトアウトした顧客にエンゲージしたり、課金に問題がある顧客にリマインダーを送信するなど、顧客の購読ライフサイクルのステージに反応するキャンペーンを構築することができる。
+### RevenueCat - 決済
+[RevenueCat]({{site.baseurl}}/partners/data_and_infrastructure_agility/payments/revenuecat/#revenuecat)とBrazeインテグレーションを使用すると、顧客の購買およびサブスクリプションライフサイクルイベントをプラットフォーム間で自動的に同期できます。これにより、無料トライアル中にオプトアウトした顧客への働きかけや、請求で問題のある顧客へのリマインダーの送信など、顧客のサブスクリプションライフサイクルステージに対応するキャンペーンを作成できます。
 
-### パンチ - 忠誠心
-[Punchhは]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/punchh/#punchh)Brazeと提携し、2つのプラットフォーム間でデータを同期させ、ギフトとロイヤリティを目的としている。Brazeで公開されたデータはセグメンテーションに利用でき、Brazeで設定されたWebhookテンプレートを介してPunchhにユーザーデータを同期することができる。  
\ No newline at end of file
+### Punchh - ロイヤルティ
+[Punchh]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/punchh/#punchh)はBrazeと提携し、プレゼントやロイヤルティのために2つのプラットフォーム間でデータを同期しました。Brazeで公開されたデータはセグメンテーションに利用でき、Brazeで設定されたWebhookテンプレートを介してPunchhにユーザーデータを同期することができる。  
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2021/october.md b/_lang/ja/_help/release_notes/2021/october.md
index 91b2494f0f7..a5db5b86bc9 100644
--- a/_lang/ja/_help/release_notes/2021/october.md
+++ b/_lang/ja/_help/release_notes/2021/october.md
@@ -10,9 +10,9 @@ description: "この記事には、2021年10月のリリースノートが含ま
 
 ## データポイント利用ダッシュボード
 
-**合計データポイント使用量**ダッシュボードを使用して、契約割り当てに関連するデータポイントの使用ペースを追跡する。このダッシュボードには、契約内容、現在の請求サイクル、会社の請求データ、ワークスペースの請求データに関する情報が表示される。詳細については、「[請求]({{site.baseurl}}/user_guide/onboarding_with_braze/subscription_and_usage/#total-data-points-dashboard)」を参照のこと。
+**合計データポイント使用量**ダッシュボードを使用して、契約割り当てに関連するデータポイントの使用ペースを追跡する。このダッシュボードには、契約内容、現在の請求サイクル、会社の請求データ、ワークスペースの請求データに関する情報が表示される。詳細については、「[請求]({{site.baseurl}}/user_guide/onboarding_with_braze/subscription_and_usage/#total-data-points-dashboard)」を参照してください。
 
-## セグメント延長再生に変更
+## セグメントエクステンションの再生成の変更
 
 2022年2月1日以降、未使用の[セグメント・エクステンションについては]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/)、毎日エクステンションを再生成する設定が自動的にオフになる。Braze では、未使用のエクステンションを次の基準を満たすものと定義しています。
 
@@ -36,14 +36,14 @@ description: "この記事には、2021年10月のリリースノートが含ま
 
 このオプショナルで高度な[実装ガイドでは]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/implementation_guide/)、カスタム`FirebaseMessagingService` サブクラスを活用してプッシュ・メッセージを最大限に活用する方法について説明する。Braze チームが作成したカスタムのユースケース、付属のコードスニペット、ロギング分析に関するガイダンスも含まれています。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
 ### アドビ - 顧客データプラットフォーム
 
-Adobe Experience Platform上に構築されたアドビのリアルタイム顧客データプラットフォーム（リアルタイムCDP）は、企業が複数の企業ソースから既知および匿名のデータを収集し、顧客プロファイルを作成するのを支援する。
+Adobe Experience Platform 上に構築された Adob​​e のリアルタイム顧客データプラットフォーム (リアルタイム CDP) は、企業が複数のエンタープライズソースからの既知のデータと匿名データを統合し、すべてのチャネルとデバイスでパーソナライズされた顧客体験をリアルタイムで提供するために使用できる顧客プロファイルを作成するのに役立ちます。
 
-Brazeと[Adobe]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/adobe/)CDPの統合により、ブランドはAdobeデータ（カスタム属性とセグメント）をリアルタイムでBrazeに接続し、マッピングすることができる。ブランドはこのデータに基づいて行動し、パーソナライズされたターゲット体験をユーザーに提供することができる。 
+Brazeと[Adobe]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/adobe/)CDPの統合により、ブランドはAdobeデータ（カスタム属性とセグメント）をリアルタイムでBrazeに接続し、マッピングすることができる。ブランドはこのデータに基づいて行動し、パーソナライズされ、ターゲットに応じた体験をユーザーに提供できます。 
 
 ### Shopify - Eコマース
 
-[Shopifyは]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/)、あらゆる規模の小売ビジネスを開始し、成長させ、販売し、管理するための信頼できるツールを提供する、世界的なコマースのリーディングカンパニーである。BrazeとShopifyの統合により、ブランドはShopifyストアをBrazeとシームレスに接続し、選択したShopifyのウェブフックをBrazeに渡すことができる。Brazeのクロスチャネル戦略とCanvasを活用して、放棄されたチェックアウトのメッセージでユーザーを再ターゲットし、購入を完了するよう促す。
\ No newline at end of file
+[Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/)は、あらゆる規模の小売 (店)事業を始め、成長し、販売し、管理するための信頼できる道具を提供する世界的な大手商業企業です。Braze と Shopify の統合により、ブランドは Shopify ストアを Braze とシームレスに接続し、選択した Shopify Webhook を Braze に渡すことができます。Braze のクロスチャネル戦略とキャンバスを活用して、購入手続き放棄のメッセージングでユーザーをリターゲティングし、顧客に購入を完了するよう促したり、以前の購入に基づいてユーザーをリターゲティングしたりできます。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2021/september.md b/_lang/ja/_help/release_notes/2021/september.md
index fa76d3ec321..7aabf7f3c97 100644
--- a/_lang/ja/_help/release_notes/2021/september.md
+++ b/_lang/ja/_help/release_notes/2021/september.md
@@ -10,30 +10,30 @@ description: "この記事には2021年9月のリリースノートが含まれ
 
 ## iOS 15
 
-### アップル・メールのプライバシー保護 
+### Apple Mail のプライバシー保護 
 
-アップルのMail Privacy Protection（MPP）は、9月中旬にリリースされるiOS 15、iPadOS 15、macOS Monterey、watchOS 8のApple Mailアプリのユーザー向けに提供されるプライバシーアップデートだ。MPPをオプトインしたユーザーは、プロキシサーバーを使用してメールがプリロードされ、画像がキャッシュされ、[開封トラッキングなどの]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#open-tracking-pixel)指標にトラッキングピクセルを活用することができなくなる。MPPの詳細や、メール配信メトリクスの問題、既存のキャンペーンやCanvaseがこれらのメトリクスのトリガーとなる問題については、当社の[ドキュメントを]({{site.baseurl}}/user_guide/message_building_by_channel/email/mpp/)ご覧ください。
+Apple のメールプライバシー保護 (MPP) は、9月中旬にリリースされた iOS 15、iPadOS 15、macOS Monterey、watchOS 8の Apple Mail アプリのユーザーに提供されるプライバシーアップデートです。MPP にオプトインしたユーザーの場合、メールはプロキシサーバーを使用してプリロードされ、画像がキャッシュされ、[開封の追跡]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#open-tracking-pixel)などの指標のトラッキングピクセルをトラッキングできなくなります。MPP およびメール配信可能性メトリクスに関する問題、およびこれらのメトリクスに基づいてトリガーされる既存のキャンペーンとキャンバスに関する問題については、[ドキュメント]({{site.baseurl}}/user_guide/message_building_by_channel/email/mpp/) を参照してください。
 
 ### プッシュ機能
 
-iOS15は、ユーザーが集中力を維持し、一日中頻繁な中断を避けるための新しい通知機能を導入した。[中断レベルや関連性スコアなど]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/notification_options/)、これらの新機能のサポートを提供できることをうれしく思う。
+iOS 15では新しい通知機能が導入され、ユーザーは1日を通して集中力を保ち、頻繁な作業の中断を避けることができます。[中断レベルや関連性スコアなど]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/notification_options/)、これらの新機能のサポートを提供できることをうれしく思う。
 
 ## 連絡先カード
 
-コンタクトカードは、ビジネスや連絡先情報を送信するための標準化されたファイルフォーマットで、アドレス帳や連絡帳に簡単にインポートできる。SMSやMMSメッセージに連絡先カードをアップロードして作成できるようになった。内蔵のコンタクト・カード・ジェネレーターでコンタクト・カードを作成する方法については、[ドキュメントを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/contact_card/)参照されたい。
+連絡先カードは、アドレス帳や連絡先一覧に簡単にインポートできるビジネス情報や連絡先情報を送信するための標準化されたファイル形式です。SMSやMMSメッセージに連絡先カードをアップロードして作成できるようになった。組み込みの連絡先カードジェネレーターで連絡先カードを構築する方法の詳細については、[こちら]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/contact_card/)のドキュメントを参照してください。
 
 ## デフォルト・コンテンツ・カードのカスタマイズ
 
-`ABKContentCardsTableViewController` を拡張してすべての UI 要素とコンテンツカードの動作をカスタマイズすることで、独自のコンテンツカードインターフェイスを作成できます。コンテンツ・カード・フィードのカスタマイズ方法の詳細については、[ドキュメントを]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/customization/customizing_feed/)ご覧いただきたい。 
+`ABKContentCardsTableViewController` を拡張してすべての UI 要素とコンテンツカードの動作をカスタマイズすることで、独自のコンテンツカードインターフェイスを作成できます。コンテンツカードフィードのカスタマイズ方法の詳細については、[ドキュメント]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/customization/customizing_feed/) をご覧ください。 
 
-## APIレート制限
+## API レート制限
 
 [料金制限は]({{site.baseurl}}/api/basics/#api-limits/)2021年9月16日以降に搭乗するすべての顧客に適用される。 
 
 ## AndroidとFireOSの開発者向けガイドを更新
 
-AndroidとFireOSの開発者ガイドは1つの場所に統合された。FireOSの記事は、この[新しいAndroidセクションで]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/fireos/integration/)読むことができる。
+AndroidとFireOSの開発者ガイドは1つの場所に統合された。この[新しいAndroidセクション]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/fireos/integration/) では、専用のFireOS アーティクルを使用できます。
 
 ## ファネルとリテンションレポートの更新
 
-[ファネルレポートと]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_funnel_reports/) [リテンションレポートが]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/retention_reports/)SMSキャンペーンで利用可能になった。
+[ファネルレポート]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_funnel_reports/)と[保持レポート]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/retention_reports/)がSMSキャンペーンで利用可能になりました。
diff --git a/_lang/ja/_help/release_notes/2022.md b/_lang/ja/_help/release_notes/2022.md
index 05b9683600f..011570a4f6a 100644
--- a/_lang/ja/_help/release_notes/2022.md
+++ b/_lang/ja/_help/release_notes/2022.md
@@ -6,7 +6,7 @@ noindex: true
 guide_top_header: "2022 リリースノート"
 
 page_type: landing
-description: "このセクションでは、2022年のリリースノートを掲載する。"
+description: "このセクションには、2022年のリリースノートがあります。"
 
 guide_menu_title: ""
 guide_menu_list:
diff --git a/_lang/ja/_help/release_notes/2022/10_18_22.md b/_lang/ja/_help/release_notes/2022/10_18_22.md
index 8f6c3a2231c..ac9cb4f082d 100644
--- a/_lang/ja/_help/release_notes/2022/10_18_22.md
+++ b/_lang/ja/_help/release_notes/2022/10_18_22.md
@@ -3,55 +3,55 @@ nav_title: 2022年10月18日
 page_order: 1
 noindex: true
 page_type: update
-description: "この記事には、2022年10月18日のリリースノートが含まれている。"
+description: "この記事には、2022年10月18日のリリースノートが含まれています。"
 ---
 
 # 2022年10月18日リリース
 
 ## ユーザープロファイル メッセージング履歴
 
-ユーザープロファイルの \[**メッセージ履歴**] タブには、過去30日間の個々のユーザーの最近のメッセージング関連イベント (約40件) が表示されます。これらのイベントには、ユーザーに送られたメッセージ、ユーザーが受信したメッセージ、ユーザーが処理したメッセージなどが含まれます。詳しくは[ユーザープロファイルを]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/#messaging-history-tab)参照のこと。 
+ユーザープロファイルの \[**メッセージ履歴**] タブには、過去30日間の個々のユーザーの最近のメッセージング関連イベント (約40件) が表示されます。これらのイベントには、ユーザーに送られたメッセージ、ユーザーが受信したメッセージ、ユーザーが処理したメッセージなどが含まれます。詳細については、「[ユーザープロファイル]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/#messaging-history-tab)」を参照してください。 
 
 ## ドラッグ＆ドロップ・エディター用コンテンツ・ブロック
 
 ドラッグ＆ドロップ・エディターでのみ使用される[コンテンツ・ブロックは]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/)、異なるチャンネルで使用されるコンテンツ・ブロックと同様の機能を持つ。様々なメールキャンペーンで参照できる情報を一元管理できる。これには、Eメールのヘッダーやプロモーションの吹き出しなどを、再利用可能な1つの行にまとめることも含まれる。
 
-## Shopifyスクリプトタグ
+## Shopify ScriptTag
 
 [BrazeとShopifyの統合により]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify)、ShopifyストアにScriptTag経由で弊社のWeb SDK統合を埋め込むことができるようになった。ScriptTag経由で当社のWeb SDKを埋め込むと、以下のトラッキングをサポートする：
 - 匿名ユーザー・トラッキングにより、店舗でのゲストの行動を追跡する。
-- Web SDKは、店舗訪問者のセッションデータを追跡できるため、毎月アクティブユーザーを追跡することができる。
+- 月次アクティブユーザートラッキング (Web SDKは店舗訪問者のセッションデータをトラッキングできるため)
 - Shopifyのオンサイト・アクティビティ・ユーザーを収集するオプションがあり、データ・ポイントの消費にカウントされる。
 - Shopifyストアのチャネルとしてブラウザ内メッセージングを有効にするオプション
 
 ## SCIMエンドポイント
 
 自動化されたユーザープロビジョニングを管理するには、以下のBraze SCIMエンドポイントを使用する：
-- [削除する：ダッシュボードのユーザーアカウントを削除する]({{site.baseurl}}/api/endpoints/scim/delete_existing_dashboard_user/)
-- [GETだ：既存のダッシュボード・ユーザー・アカウントを検索する]({{site.baseurl}}/api/endpoints/scim/get_see_user_account_information/)
-- [ポストだ：新しいダッシュボード・ユーザー・アカウントを作成する]({{site.baseurl}}/api/endpoints/scim/post_create_user_account/)
-- [プットする：ダッシュボードのユーザーアカウントを更新する]({{site.baseurl}}/api/endpoints/scim/put_update_existing_user_account/)
+- [DELETE: ダッシュボードのユーザーアカウントを削除する]({{site.baseurl}}/api/endpoints/scim/delete_existing_dashboard_user/)
+- [GET: 既存のダッシュボードユーザーアカウントを検索する]({{site.baseurl}}/api/endpoints/scim/get_see_user_account_information/)
+- [POST: 新しいダッシュボードユーザーアカウントを作成する]({{site.baseurl}}/api/endpoints/scim/post_create_user_account/)
+- [PUT: ダッシュボードのユーザーアカウントを更新する]({{site.baseurl}}/api/endpoints/scim/put_update_existing_user_account/)
 
 ## SMS ファジー・オプトアウト
 
-[ファジー・オプトアウトは]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out#fuzzy-opt-out)、受信SMSメッセージがオプトアウト・キーワードに一致しないが、オプトアウトの意図を示す場合に、それを認識しようとするものである。ファジーオプトアウトが有効で、インバウンドキーワードレスポンスが「ファジー」と判断された場合、Brazeは自動的にユーザーに意思確認を求めるレスポンスを返す。
+[あいまいなオプトアウト]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out#fuzzy-opt-out)は、受信 SMS メッセージがオプトアウトキーワードと一致しないものの、オプトアウトの意図を示している場合に、それを認識しようとします。ファジーオプトアウトが有効で、インバウンドキーワードレスポンスが「ファジー」と判断された場合、Brazeは自動的にユーザーに意思確認を求めるレスポンスを返す。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Android SDK 23.2.0-23.2.1](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2321)
 - [iOS Objective-C SDK 4.5.1](https://github.com/Appboy/appboy-ios-sdk/blob/master/CHANGELOG.md#451)
 - [iOS Swift SDK 5.5.0S-SDK 5.5.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#550)
 - [Cordova SDK 2.31.0](https://github.com/Appboy/appboy-cordova-sdk/blob/master/CHANGELOG.md#2310)
-  - [Braze Android SDK 23.0.](https://github.com/braze-inc/braze-android-sdk/releases/tag/v23.0.1)1に更新。
-- [ユニティ 3.10.0](https://github.com/Appboy/appboy-unity-sdk/blob/master/CHANGELOG.md#3100)
+  - [Braze Android SDK 23.0.1](https://github.com/braze-inc/braze-android-sdk/releases/tag/v23.0.1) に更新されました。
+- [Unity 3.10.0](https://github.com/Appboy/appboy-unity-sdk/blob/master/CHANGELOG.md#3100)
 - [React SDK v1.39.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#1400)
   - ネイティブのAndroid SDKを23.2.0に更新した。
-  - `kotlin_versio`n gradle テンプレート変数の名前を次のように変更した。 `kotlinVersion`
+  - `kotlin_versio`n gradle テンプレート変数の名前が `kotlinVersion` に変更されました。
 - [Flutter SDK 2.6.0](https://pub.dev/packages/braze_plugin/changelog#260)
-  - ネイティブAndroidブリッジは、Braze Android SDK 23.2.0を使用している。
+  - ネイティブ Android ブリッジでは、Braze Android SDK 23.2.0を使用します。
   - ネイティブiOSブリッジは、Braze iOS SDK 4.5.1を使用している。
   - `process(inAppMessage)` はiOSレイヤーでは`processInAppMessage(inAppMessage)` にリネームされる。
-- [セグメント iOS 4.6.0](https://github.com/Appboy/appboy-segment-ios/blob/master/CHANGELOG.md#460)
-  - Braze[iOS SDK 4.5.1+に](https://github.com/Appboy/appboy-ios-sdk/blob/master/CHANGELOG.md#451)アップデート。
+- [Segment iOS 4.6.0](https://github.com/Appboy/appboy-segment-ios/blob/master/CHANGELOG.md#460)
+  - Braze [iOS SDK 4.5.1+](https://github.com/Appboy/appboy-ios-sdk/blob/master/CHANGELOG.md#451) に更新されました。
diff --git a/_lang/ja/_help/release_notes/2022/11_15_22.md b/_lang/ja/_help/release_notes/2022/11_15_22.md
index 35508848dcf..26b547ce608 100644
--- a/_lang/ja/_help/release_notes/2022/11_15_22.md
+++ b/_lang/ja/_help/release_notes/2022/11_15_22.md
@@ -3,18 +3,18 @@ nav_title: 2022年11月15日
 page_order: 0.5
 noindex: true
 page_type: update
-description: "この記事には、2022年11月15日のリリースノートが含まれている。"
+description: "この記事には、2022年11月15日のリリースノートが含まれています。"
 ---
 
 # 2022年11月15日リリース
 
 ## アプリ内メッセージ用の新しいドラッグ＆ドロップ・エディター
 
-新しい[ドラッグ&アンプ;アプリ内メッセージ用ドロップエディターs]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop)で、HTMLを知らなくても完全なカスタムとパーソナライズされた アプリ内メッセージs を作成できます。ドラッグ＆ドロップ・エディターは、今後数ヶ月かけてすべての顧客に展開される。もっと早くアクセスをリクエストしたい場合は、カスタマー・サクセス・マネージャーまでご連絡を。
+新しい[ドラッグ&アンプ;アプリ内メッセージ用ドロップエディターs]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop)で、HTMLを知らなくても完全なカスタムとパーソナライズされた アプリ内メッセージs を作成できます。ドラッグアンプ;ドロップエディターは、今後数ヶ月間、すべての顧客に展開されています。もっと早くアクセスをリクエストしたい場合は、カスタマー・サクセス・マネージャーまでご連絡を。
 
 ## Eメール用ドラッグ＆ドロップ・エディターの更新
 
-### 新しいエディター・ブロック
+### 新しいエディタブロック
 
 メールのドラッグ＆ドロップ・エディターに2つの新しいエディター・ブロックが追加された：[段落ブロックと]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks/#paragraph) [リストブロック]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks/#list)。
 
@@ -24,25 +24,25 @@ description: "この記事には、2022年11月15日のリリースノートが
 
 ### ダークモードのプレビュー
 
-ドラッグ＆ドロップエディターで[メールをプレビュー、テストする]({{site.baseurl}}/user_guide/message_building_by_channel/email/html_editor/creating_an_email_campaign/#step-3b-preview-and-test-your-message)際、**ダークモードプレビューを**オンにして、ダークモードユーザーのメールの見え方を確認できるようになった。
+ドラッグアンドドロップエディタで[ プレビューを実行し、メールのs]({{site.baseurl}}/user_guide/message_building_by_channel/email/html_editor/creating_an_email_campaign/#step-3b-preview-and-test-your-message) をテストすると、**Dark Mode プレビュー** を有効にして、ダークモードユーザーs のメールを確認できます。
 
-## ウイニング・パス』早期アクセス
+## Winning Path earlyアクセス
 
-CanvasのExperiment Pathsの一部として利用できる[Winning Pathを]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/#step-2-turn-on-winning-path-optional)使えば、A/Bテストを自動化できる。Winning Pathをオンにすると、指定された期間の後、後続のユーザーはすべて、最もコンバージョン率の高いパスに送られる。
+Canvas のExperiment Paths の一部として使用できます。[Winning Path]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/#step-2-turn-on-winning-path-optional) では、A/B テストを自動化できます。Winning パス を有効にすると、指定した期間が経過すると、それ以降のすべてのユーザーs が、最も高いコンバージョン速度でパスに送信されます。
 
-この機能は現在早期アクセス段階です。早期アクセスへの参加に興味がある方は、カスタマー・サクセス・マネージャーまでご連絡を。
+この機能は現在早期アクセス段階です。早期参入に興味がある場合は、顧客のサクセスマネージャーに手を伸ばしてください。
 
 ## tvOSのアプリ内メッセージとコンテンツカード
 
-この新しい記事では、Braze Swift SDKを通じて利用可能な[アプリ内メッセージとコンテンツカードをtvOS上で]({{site.baseurl}}/developer_guide/platform_integration_guides/tvos/in-app_messaging)統合する際のニュアンスを取り上げている。
+この新しい記事では、Braze Swift SDKを介して利用可能な、tvOS上の[アプリ内メッセージとコンテンツカードの統合のニュアンスについて説明します。
 
 ## 新しいリキッドの使用例
 
-[Liquidユースケースライブラリに]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases#misc-personalize-content)、顧客の購読状態を利用してメッセージ内のコンテンツをパーソナライズする方法に関する新しいユースケースを追加した。このユースケースでは、特定の購読グループを購読している顧客は、EメールとSMSの両方の購読グループに対する限定メッセージを受け取ることになる。
+メッセージの内容をパーソナライズするために顧客のサブスクリプションステートを使用する方法について、[Liquid ユースケース Library]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases#misc-personalize-content)に新しいユースケースを追加しました。このユースケースでは、特定のサブスクリプショングループをサブスクライブした顧客は、メールとSMS サブスクリプショングループの両方に対して排他的なメッセージを受信します。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。これらのリリースに伴う更新はない。その他のすべてのアップデートは、対応するSDKの変更履歴をチェックすることで確認できる。
+以下のSDKアップデートがリリースされた。これらのリリースでは、壊れた更新はありません。その他のすべてのアップデートは、対応するSDKの変更履歴をチェックすることで確認できる。
 
 - [Android SDK 23.3.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2330)
 - [Web SDK 4.4.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#440)
diff --git a/_lang/ja/_help/release_notes/2022/12_13_22.md b/_lang/ja/_help/release_notes/2022/12_13_22.md
index 9f8fb446578..1f99f61f9d0 100644
--- a/_lang/ja/_help/release_notes/2022/12_13_22.md
+++ b/_lang/ja/_help/release_notes/2022/12_13_22.md
@@ -15,12 +15,12 @@ description: "この記事には2022年12月13日のリリースノートが含
 [Braze API カタログのエンドポイント]({{site.baseurl}}/api/endpoints/catalogs)を使用して、[カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs)およびカタログアイテムの詳細を追加、編集、および管理します。非同期カタログエンドポイントを使用して、カタログに一括変更を加えることができます。
 
 ## メール用ドラッグ＆ドロップエディタのリンクのHTML属性
-ドラッグ＆ドロップエディターの`Image`、`Button`、または`Text`エディターブロック内の任意のURLに[HTML属性を追加]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/#creative-details/)できます。カスタム属性を使用すると、電子メールのHTMLタグに追加情報を簡単に追加できます。これは、メッセージのパーソナライゼーション、セグメンテーション、およびスタイリングに特に役立ちます。 
+メール用のドラッグ＆ドロップエディターで、`Image`、`Button`、または `Text` エディターブロック内の任意の URL に [HTML属性]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/#creative-details/)を追加できるようになりました。カスタム属性を使用すると、電子メールのHTMLタグに追加情報を簡単に追加できます。これは、メッセージのパーソナライゼーション、セグメンテーション、およびスタイリングに特に役立ちます。 
 
 ## ヒートマップの切り替えを表示
 [ヒートマップ表示]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/email_reporting#heatmaps)トグルを使用して、メールキャンペーンの存続期間中のクリックの全体的な頻度と場所を示す**メッセージ分析**の視覚的なビューを表示できるようになりました。将来の参考のために、ヒートマップのコピーをダウンロードすることもできます。
 
-## 更新されたメール設定
+## メール設定の更新
 前の**一般メール設定**セクションは、2つの新しいセクションに分割されました:**送信設定**と**サブスクリプションページとフッター。**詳細については、[メール設定]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#sending-configuration)を確認してください。
 
 ## メディアライブラリー用のAI画像を生成する
@@ -28,11 +28,11 @@ DALL·E 2を使用してメディアライブラリー用の画像を生成で
 
 ## ネストされたカスタム属性の強化
 カスタム属性をネストして使用することで、オブジェクトをカスタム属性の新しいデータ型として送信できます。 
-- [トリガーは階層化カスタム属性オブジェクトが変更されたときに]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/#trigger-nested-custom-attribute-changes)できます。
+- [階層化カスタム属性オブジェクトを変更するタイミングをトリガー]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/#trigger-nested-custom-attribute-changes)できます。
 - また、[カスタム属性オブジェクトとLiquidを使用してメッセージをパーソナライズすることもできます]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/#personalization)。
 
 ## 新しい動画ブロック
-ドラッグ＆ドロップエディターに[動画]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks/#video)の新しいコンテンツブロックが追加されました。
+[Video]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks/#video) の新しいコンテンツブロックが、ドラッグアンプ、Drop Editor for Email に追加されました。
 
 ## ベンダーコレクションのオプション識別子 - SWIFT
 Braze iOS Swift SDK の以前のバージョンでは、IDFV （ベンダーの識別子) フィールドがユーザーのデバイス ID として自動的に収集されました。Swift SDK v5.7.0 以降では、IDFV フィールドをオプションで無効にすることができ、代わりに Braze はランダムな UUID をデバイス ID として設定します。詳細については、「[IDFV の収集]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/)」を参照してください。
@@ -42,14 +42,14 @@ Snowflake Reader Accounts を使用すると、Snowflake アカウントや Snow
 
 詳細については、カスタマーサクセスマネージャーにお問い合わせください。
 
-## 更新されたShopify統合
+## Shopify 連携の更新
 [Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/)の統合により、ShopifyストアからメールおよびSMSのオプトインを収集し、それらをBrazeのサブスクリプショングループに割り当てることができるようになりました。
 
 
 ## 新しいBrazeのパートナーシップ
 
 ### Ada - アンケート
-[Ada]({{site.baseurl}}/partners/message_orchestration/channel_extensions/surveys/ada/)とBrazeの統合により、自動化されたAdaの会話から収集されたデータでユーザープロファイルを拡張できます。Ada チャット中に収集した情報に基づいてカスタムユーザー属性を設定し、Ada 会話の指定されたポイントで Braze にカスタムイベントを記録できます。AdaチャットボットをBrazeに接続することで、消費者がブランドについてどのような質問をするかに基づいて、消費者について詳しく知ることができます。また、積極的に会話を始め、彼らの興味や好みについて詳しく知ることができる質問をすることで、消費者についてさらに理解を深めることができます。
+[Ada]({{site.baseurl}}/partners/message_orchestration/channel_extensions/surveys/ada/)とBrazeの統合により、自動化されたAdaの会話から収集されたデータでユーザープロファイルを拡張できます。Ada チャット中に収集した情報に基づいてカスタムユーザー属性を設定し、Ada 会話中に指定された時点で Braze にカスタムイベントを記録できます。AdaチャットボットをBrazeに接続することで、消費者がブランドについてどのような質問をするかに基づいて、消費者について詳しく知ることができます。また、積極的に会話を始め、彼らの興味や好みについて詳しく知ることができる質問をすることで、消費者についてさらに理解を深めることができます。
 
 ### B.Layer \- メッセージテンプレート
 [B.Layer]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/blayer)とBrazeの統合により、B.Layerアプリ内メッセージビルダーを活用して、ブランドに合ったアプリ内メッセージを作成し、zipファイルまたはインラインHTMLとしてBrazeにエクスポートすることができます。この統合には追加の開発者リソースは必要なく、時間と予算を節約できます。
@@ -57,27 +57,27 @@ Snowflake Reader Accounts を使用すると、Snowflake アカウントや Snow
 ### Contentsquare - 分析
 [Contentsquare]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/contentsquare/)とBrazeの統合により、BrazeのカスタムイベントとしてLive Signals(詐欺、フラストレーション信号など)を送信できます。Contentsquareのエクスペリエンスインサイトを活用して、顧客のデジタルエクスペリエンスとボディランゲージに基づいてメッセージをターゲティングすることで、キャンペーンの関連性とコンバージョン率を向上させましょう。
 
-### ダイナミックなYield - ダイナミックなcontent
-[ダイナミックなYield]({{site.baseurl}}/partners/message_personalization/dynamic_content/dynamic_yield/)とBrazeのパートナーシップにより、ダイナミックなYieldのレコメンデーションおよびセグメンテーションエンジンを活用して、Brazeメッセージに埋め込むことができるエクスペリエンスブロックを作成できます。経験ブロックは次のもので作ることができます:
-- **推奨事項ブロック**:アルゴリズムとフィルタリングを設定して、メールが開かれたときに伝播するユーザーのパーソナライズされたコンテンツをソースします。 
-- **ダイナミックなコンテンツブロック**:異なるプロモーションやメッセージを異なるユーザーにターゲットします。ターゲティングは、アフィニティまたはオーディエンスに基づいて行うことができます。ダイナミックなYieldは、メールが開かれたときにどのパーソナライズされたエクスペリエンスを提供するかを決定します。 
+### Dynamic Yield - Dynamic コンテンツ
+[ダイナミックなYield]({{site.baseurl}}/partners/message_personalization/dynamic_content/dynamic_yield/)とBrazeのパートナーシップにより、ダイナミックなYieldのレコメンデーションおよびセグメンテーションエンジンを活用して、Brazeメッセージに埋め込むことができるエクスペリエンスブロックを作成できます。エクスペリエンスブロックは次のものから作成できます。
+- **レコメンデーションブロック**:メールの開封時に伝播されるソースユーザーのパーソナライズされたコンテンツに、アルゴリズムとフィルターを設定します。 
+- **ダイナミックコンテンツブロック**:異なるプロモーションやメッセージを異なるユーザーにターゲットします。ターゲティングは、アフィニティまたはオーディエンスのいずれかに基づいて行うことができます。ダイナミックなYieldは、メールが開かれたときにどのパーソナライズされたエクスペリエンスを提供するかを決定します。 
 
 ### Octolis - 分析
-[Octolis]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/contentsquare/)とBrazeの統合は、あなたの生データソースとBrazeの間のミドルウェアとして機能し、オンラインとオフラインの両方のさまざまなソースからデータを取得して統合することを可能にします。
+Braze と [Octolis]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/contentsquare/) の統合は、生データソースと Braze 間のミドルウェアとして機能します。これにより、オンラインとオフラインのさまざまなソースからデータを取得して統合できます。
 
-### ジャカード - ABテスト
-[Jacquard React]({{site.baseurl}}/partners/data_and_infrastructure_agility/ab_testing/jacquard/jacquard_react/)は、Jacquard Xによって提供され、Braze Currentsとコネクテッドコンテンツを活用して、webhookを通じて購読者からクリックトラッキング情報を収集します。ジャカードはそれらのイベントをあなたの言語バリアントに結び付け、リアルタイムの言語最適化を行います。
+### Jacquard - AB テスト
+[Jacquard React]({{site.baseurl}}/partners/data_and_infrastructure_agility/ab_testing/jacquard/jacquard_react/)は、Jacquard Xによって提供され、Braze Currentsとコネクテッドコンテンツを活用して、webhookを通じて購読者からクリックトラッキング情報を収集します。Jacquard は、これらのイベントを言語バリアントに関連付けて、リアルタイムで言語を最適化します。
 
 ### Sheetlabs - ダイナミックな content
 [Sheetlabs]({{site.baseurl}}/partners/message_personalization/dynamic_content/sheetlabs/)とBrazeの統合により、[コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/)を活用して、BrazeのマーケティングキャンペーンにSheetlabs APIを含めることができます。これは通常、Googleスプレッドシート（マーケティングチームによって直接更新される）とBrazeのテンプレートの間の橋渡しを提供するために使用されます。これにより、翻訳やより大きなカスタム属性セットなど、Brazeテンプレートでより多くのことを達成できます。
 
 ### Tellius - 分析
-[Tellius]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/tellius/)とBrazeの統合は、ユーザーがBIエンジニアに依存せずにデータを活用し、ダッシュボードを構築し、インサイトを生成して、より良いマーケティングの意思決定を行うことを可能にします。
+[Tellius]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/tellius/) とBraze の統合により、ユーザーは BI エンジニアに頼ることなくデータを活用し、ダッシュボードを構築し、マーケティングの意思決定を改善するためのインサイトを生み出すことができるようになります。
 
 ### ThoughtSpot - 分析
-[ThoughtSpot]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/thoughtspot/)とBrazeの統合は、Brazeユーザーがワークシートとモデルの事前構築テンプレートを使用してユーザー行動分析を加速できるようにするThoughtSpot TMLブロックを活用します。この統合により、ユーザーはBrazeのインタラクションデータを無制限に検索し、実用的な洞察を発見することができます。 
+[ThoughtSpot]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/thoughtspot/)とBrazeの統合は、Brazeユーザーがワークシートとモデルの事前構築テンプレートを使用してユーザー行動分析を加速できるようにするThoughtSpot TMLブロックを活用します。この統合により、ユーザーは Braze のインタラクションデータを無制限に検索し、実用的なインサイトを見つけることができます。 
 
-### ワンダーキンド - 分析
+### Wunderkind - 分析
 [Wunderkind]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/wunderkind/)とBrazeの統合により、パフォーマンスの向上を分析し、より多くの匿名ユーザーを特定することができ、Brazeを介して送信される1対1のメッセージと、Brazeに直接追加される連絡先を大幅に拡大します。
 
 
@@ -89,10 +89,10 @@ Snowflake Reader Accounts を使用すると、Snowflake アカウントや Snow
     - ネイティブiOSブリッジは現在、[新しいBraze SWIFT SDK、バージョン5.6.4](https://github.com/braze-inc/braze-swift-sdk)を使用しています。最小のiOSデプロイメントターゲットは10.0です。
     - 移行中に、次の変更を使用してプロジェクトを更新してください:
         - Brazeを初期化するには、[これらの統合手順に従って構成オブジェクトを作成します](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/a2-configure-braze)。次に、このコードを追加してセットアップを完了します: `let braze = BrazePlugin.initBraze(configuration)`
-        - 依存関係として`SDWebImage`を使用し続けるには、この行をプロジェクトの`/ios/Podfile`に追加します: `pod 'SDWebImage', :modular_headers => true`。次に、[これらのセットアップ手順に従ってください](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/c3-gif-support)。
+        - 依存関係として `SDWebImage` を引き続き使用するには、この行をプロジェクトの`/ios/Podfile`: `pod 'SDWebImage', :modular_headers => true` に追加します。次に、[これらのセットアップ手順に従ってください](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/c3-gif-support)。
         - 他の変更についてのガイダンスについては、アプリ内メッセージやコンテンツカードのデータを受信するなど、サンプル[`AppDelegate.swift`](https://github.com/braze-inc/braze-flutter-sdk/blob/master/example/ios/Runner/AppDelegate.swift)を参照してください。
 - [React Native SDK v1.41.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
 - [Web SDK 4.5.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 
 ### 新しいSDKライブラリー：Segment Kotlin SDK 
-Segmentは、Segment Kotlinと呼ばれる新しいKotlinファーストアプローチでライブラリーを更新しました。Brazeは、この新しいライブラリパラダイムで動作する独自の新しいライブラリーをリリースしました。[初期リリースをGitHubでチェックしてください。](https://github.com/braze-inc/braze-segment-kotlin)
+Segment は、新しい Kotlin ファーストアプローチである Segment Kotlin によってライブラリを更新しました。Braze はこの新しいライブラリパラダイムに対応する独自の新しいライブラリをリリースしました。GitHub で[初期リリースをチェックしてください。](https://github.com/braze-inc/braze-segment-kotlin)
diff --git a/_lang/ja/_help/release_notes/2022/1_11_22.md b/_lang/ja/_help/release_notes/2022/1_11_22.md
index 80892ee4a86..dc4c888a337 100644
--- a/_lang/ja/_help/release_notes/2022/1_11_22.md
+++ b/_lang/ja/_help/release_notes/2022/1_11_22.md
@@ -11,15 +11,15 @@ alias: "/help/release_notes/2022/february/"
 新しい年へようこそ！
 
 ## キャンバス実験パス ステップ
-新しいキャンバス・エクスペリメント・パスステップは、ユーザー・ジャーニーの任意の時点で、複数のキャンバス・パスを互いにテストし、コントロール・グループとテストすることで、パスのパフォーマンスを追跡するのに役立つ。さて、ここで集めたアナリティクスを活用して、どの経路が最も効果的かをさらに判断することができる。[エクスペリメント・パスステップの]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/)作り方については、こちらを参照のこと。
+新しいキャンバス試行パスでは、複数のキャンバスパスを相互にテストしたり、コントロールグループをユーザーの旅行の任意の時点でテストしたりすることで、パス パフォーマンスを追跡しやすくします。これで、ここで収集した分析を活用して、どのパスが最も効果的かをさらに判断できます。[Experiment Paths Step]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/)の作成方法について詳しく説明します。
 
 ## 無効な電話番号を処理する
 あなたは、ユーザーが無効な電話番号を入力した場面に遭遇した。これが解決策だ！Brazeは、これらの無効な電話番号をマークし、これらの電話番号には今後一切連絡を送らない。Brazeが無効な電話番号をどのように処理するかについて詳しく読む[}]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/#handling-invalid-phone-numbers/)。
 
 ## 新しいSMSエンドポイント
 新しい[Braze SMS Endpointsを使って]({{site.baseurl}}/api/endpoints/sms/)無効な電話番号を管理できるようになった！このアップデートの特徴は以下の通りである：
-- [GETだ：Query or list invalid phone numbers endpoint]({{site.baseurl}}/api/endpoints/sms/get_query_invalid_numbers/) Brazeが「無効」とみなす電話番号のリストを返す。
-- [ポストだ：Remove invalid phone numbers endpoint]({{site.baseurl}}/api/endpoints/sms/post_remove_invalid_numbers/) Brazeの無効リストから「無効な」電話番号を削除できる。
+- [GET: クエリーまたは不正な電話番号の一覧エンドポイント]({{site.baseurl}}/api/endpoints/sms/get_query_invalid_numbers/) は、"invalid" と見なされる電話番号の一覧をBrazeで返します。
+- [POST: 不正な電話番号エンドポイント]({{site.baseurl}}/api/endpoints/sms/post_remove_invalid_numbers/) を削除すると、"invalid" 電話番号をBrazeの不正な一覧から削除できます。
 
 ## レート制限
 すべての[Braze Endpoint]({{site.baseurl}}/api/basics/#nav_top_endpoints)記事にAPIレート制限が含まれている。リクエストの種類別に料金制限を簡単に表示できるようになった。レート制限の詳細については、[APIレート制限に関する]({{site.baseurl}}/api/api_limits/)記事を参照のこと。
@@ -28,7 +28,7 @@ alias: "/help/release_notes/2022/february/"
 Brazeに[EU-02 RESTエンドポイントが]({{site.baseurl}}/api/basics/#api-definitions)追加された。
 
 ## Eメールについて
-Eメール・メッセージは、顧客とつながる素晴らしい方法だ。Eメールメッセージをカスタマイズして活用する方法については、[Eメールについての]({{site.baseurl}}/user_guide/message_building_by_channel/email/about/)新しい記事をご覧いただきたい。 
+メールメッセージは、顧客 s との接続に最適な方法です。メールをカスタマイズして活用する方法については、[ メール]({{site.baseurl}}/user_guide/message_building_by_channel/email/about/) に関する新記事をご覧ください。 
 
 ## アプリ内メッセージについて
-アプリ内メッセージは、アプリ内でアクティブなユーザーにリッチコンテンツを配信する。パーソナライズされた挨拶や機能採用のためのアプリ内メッセージを作成することで、アクティブな顧客と簡単にエンゲージすることができる。利点とメッセージの種類については、[アプリ内メッセージについての]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/about/)新しい記事をご覧いただきたい。
\ No newline at end of file
+アプリ内メッセージは、アプリ内でアクティブなユーザーにリッチコンテンツを配信する。パーソナライズされたのあいさつや機能導入のためのアプリ内メッセージsを作成することで、有効な顧客sと簡単に関わることができます。アドバンスタグ es とメッセージタイプについては、[ アプリ内メッセージ s]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/about/) に関する新記事をご覧ください。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2022/2_8_22.md b/_lang/ja/_help/release_notes/2022/2_8_22.md
index 4988a362290..b4193f88397 100644
--- a/_lang/ja/_help/release_notes/2022/2_8_22.md
+++ b/_lang/ja/_help/release_notes/2022/2_8_22.md
@@ -3,7 +3,7 @@ nav_title: 2022年2月8日
 page_order: 10
 noindex: true
 page_type: update
-description: "この記事には2/8/22のリリースノートが含まれている。"
+description: "この記事には2/8/22のリリースノートが含まれています。"
 alias: "/help/release_notes/2022/march/"
 ---
 # 2022年2月8日リリース
@@ -18,10 +18,10 @@ alias: "/help/release_notes/2022/march/"
 
 ## APIエンドポイントリファレンスページ
 
-利用可能なすべてのBrazeエンドポイントのクイック・リファレンス・ページをお探し？[APIエンドポイントのインデックスを]({{site.baseurl}}/api/endpoints/)見る。
+利用可能なすべてのBraze エンドポイントのクイックリファレンスページを探していますか?[API エンドポイントインデックス]({{site.baseurl}}/api/endpoints/)をご覧ください。
 
 ## Transifex v2およびv2.5のAPIは非推奨となる
-2022年4月7日より、[Transifexは]({{site.baseurl}}/partners/message_personalization/localization/transifex/#transifex)APIバージョン2と2.5を廃止し、バージョン3に移行する。この日を過ぎると、v2とv2.5は使用できなくなり、関連するリクエストは失敗する。このパートナーとの統合を利用しているユーザーは、この日までにAPIのバージョンを更新することが求められる。
+2022年4 月7 日以降、[Transifex]({{site.baseurl}}/partners/message_personalization/localization/transifex/#transifex) はAPI バージョン2 と2.5 を廃止し、バージョン3 を使用できるようになります。この日付以降、v2 およびv2.5 は動作しなくなり、関連するリクエストは失敗します。このパートナーとの統合を利用しているユーザーは、この日までにAPIのバージョンを更新することが求められる。
 
 ## 利用可能なカスタム属性データタイプ
-もうすぐだ！カスタム属性のためのオブジェクトとオブジェクト配列データ型のサポートは、2022年春に登場する。
\ No newline at end of file
+もうすぐ!カスタム属性のためのオブジェクトとオブジェクト配列データ型のサポートは、2022年春に登場する。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2022/3_8_22.md b/_lang/ja/_help/release_notes/2022/3_8_22.md
index d97957269be..ca099b19caf 100644
--- a/_lang/ja/_help/release_notes/2022/3_8_22.md
+++ b/_lang/ja/_help/release_notes/2022/3_8_22.md
@@ -17,7 +17,7 @@ Brazeは、Rokuデバイスでユーザーにアプリ内メッセージを送
 
 新しい予測をすぐに構築するために、デフォルトではBrazeのセグメンテーションフィルターのサブセットのみがサポートされています。フルフィルターモードを有効にすると、すべてのセグメンテーションフィルターを有効にできますが、このモードでは予測を構築する際にウィンドウが1つに制限されます。詳細については、次の記事を参照してください。
 
-- [解約予測の作成]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/creating_a_churn_prediction/#full-filter-mode)
+- [チャーン予測の作成]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/creating_a_churn_prediction/#full-filter-mode)
 - [購入予測の作成]({{site.baseurl}}/user_guide/predictive_suite/predictive_purchases/creating_a_purchase_prediction/#full-filter-mode)
 
 ## キーワード応答のリターゲティングオプション
@@ -30,7 +30,7 @@ SMSキャンペーンの分析を表示する際に、特定のキーワード
 
 ## Transifex API 廃止
 
-2022年4月7日現在、Transifexはバージョン3に向けてAPIバージョン2および2.5を廃止しています。この日付以降、v2およびv2.5は運用されなくなり、関連するリクエストは失敗します。Transifex APIを活用している場合は、コネクテッドコンテンツの呼び出しを更新してください。詳細については、[Transifex]({{site.baseurl}}/partners/message_personalization/localization/transifex/)を参照してください。
+2022年4月7日より、Transifexは API バージョン2と2.5を廃止してバージョン3に移行します。この日付以降、v2およびv2.5は運用されなくなり、関連するリクエストは失敗します。Transifex API を利用している場合は、コネクテッドコンテンツ呼び出しを適宜更新してください。詳細については、[Transifex]({{site.baseurl}}/partners/message_personalization/localization/transifex/)を参照してください。
 
 ## 新しいBrazeのパートナーシップ
 
@@ -40,11 +40,11 @@ Brazeと[Toovio]({{site.baseurl}}/partners/data_and_infrastructure_agility/custo
 
 ### Snowplow - 分析
 
-Brazeと[Snowplow]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/snowplow/)の統合により、ユーザーはGoogle Tag Managerのサーバーサイドタグ付けを通じてSnowplowイベントをBrazeに転送できるようになります。Snowplow Braze タグを使用すると、Braze にイベントを送信しながら、追加の柔軟性とコントロールを提供します。
+Brazeと[Snowplow]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/snowplow/)の統合により、ユーザーはGoogle Tag Managerのサーバーサイドタグ付けを通じてSnowplowイベントをBrazeに転送できるようになります。Snowplow Braze タグを使用すると、イベントを Braze に送信しながら、以下によって柔軟性とコントロール性を高めることができます。
 
-- データに対するすべての変換の完全な可視性
-- 洗練を時間とともに進化させる能力
-- すべてのデータは、転送することを選択するまでプライベートクラウドに残ります
+- データ上のすべての変換を完全に可視化する
+- 時間の経過とともに洗練度を高める
+- すべてのデータを転送するまでプライベートクラウドに残す
 - 豊富なタグライブラリと使い慣れたGoogle Tag Manager UIによるセットアップの容易さ
 
 Snowplowの豊富な行動データを活用して、Brazeで強力な顧客中心のインタラクションを促進し、リアルタイムでパーソナライズされたメッセージを配信します。
@@ -55,15 +55,15 @@ Brazeと[Clarisights]({{site.baseurl}}/partners/data_and_infrastructure_agility/
 
 ### Wyng - ダイナミックなコンテンツ
 
-Brazeと[Wyng]({{site.baseurl}}/partners/message_personalization/dynamic_content/wyng/)の統合により、Wyngのエクスペリエンスを活用して、BrazeキャンペーンおよびCanvasでパーソナライゼーションを提供できます。Wyngには、顧客がブランドと共有するデータや好みをコントロールできる顧客好みポータルも含まれています。
+Brazeと[Wyng]({{site.baseurl}}/partners/message_personalization/dynamic_content/wyng/)の統合により、Wyngのエクスペリエンスを活用して、BrazeキャンペーンおよびCanvasでパーソナライゼーションを提供できます。Wyng には顧客設定ポータルも含まれており、ユーザーはブランドと共有するデータや設定を制御できます。
 
 ### Grouparoo - ワークフローオートメーション
 
-Brazeと[Grouparoo]({{site.baseurl}}/help/release_notes/deprecations/grouparoo)の統合により、データをBrazeに送信することで、倉庫に保存されているデータを簡単に運用化できます。自動同期スケジュールを設定すると、最新の情報で顧客とのコミュニケーションを一貫して強化できます。
+Brazeと[Grouparoo]({{site.baseurl}}/help/release_notes/deprecations/grouparoo)の統合により、データをBrazeに送信することで、倉庫に保存されているデータを簡単に運用化できます。自動同期スケジュールを設定すると、最新の情報により顧客とのコミュニケーションを一貫して強化できます。
 
-### レクサー - 顧客データプラットフォーム
+### Lexer - 顧客データプラットフォーム
 
-Brazeと[Lexer]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/lexer/)の統合により、2つのプラットフォーム間でデータを同期できます。Lexerのデータを使用して貴重なBrazeセグメントを作成するか、既存のセグメントをLexerにインポートしてインサイトを解放します。
+Brazeと[Lexer]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/lexer/)の統合により、2つのプラットフォーム間でデータを同期できます。Lexer のデータを使用して有益な Braze セグメントを作成するか、既存のセグメントを Lexer にインポートしてインサイトを引き出します。
 
 ### Knak - メールオーケストレーション
 
diff --git a/_lang/ja/_help/release_notes/2022/4_5_22.md b/_lang/ja/_help/release_notes/2022/4_5_22.md
index cb8f48f1a4e..9bd29b8ba6c 100644
--- a/_lang/ja/_help/release_notes/2022/4_5_22.md
+++ b/_lang/ja/_help/release_notes/2022/4_5_22.md
@@ -10,7 +10,7 @@ alias: "/help/release_notes/2022/may/"
 # 2022年4月5日リリース
 
 ## キャンペーンまたはキャンバスのアトリビューションでフィルタリングする
-特定のSMSキャンペーンやキャンバスステップ、キーワードカテゴリー、タグに返信したユーザーをフィルタリングできるようになった。詳しくは、[SMSリターゲティングを][8]参照のこと。
+特定のSMSキャンペーンやキャンバスステップ、キーワードカテゴリー、タグに返信したユーザーをフィルタリングできるようになった。詳細については、[SMS リターゲティング][8]を参照してください。
 
 ## メールパフォーマンスダッシュボード
 [メールパフォーマンスダッシュボードでは][1]、選択した日付範囲におけるキャンペーンとキャンバスの両方から、メールチャネル全体のパフォーマンス指標を集計して表示することができる。
@@ -22,21 +22,21 @@ Brazeで利用可能な分析ダッシュボードの詳細については、「
 ドラッグ＆ドロップ・エディターに[グローバルなスタイル設定を][3]導入！デフォルトテーマの追加、基本的なテキストスタイルの設定など、メールキャンペーンやキャンバスの見た目を簡単にパーソナライズできるようになった。
 
 ## BrazeからBrazeへのウェブフック
-BrazeからBrazeへのWebhookを使用すると、Webhookを使用してBraze REST APIと通信し、当社のAPIでできることは何でもできる。基本的に、これはBrazeからBrazeへ通信するWebhookである。詳しくは、[Braze to Braze webhooksの][4]記事を参照のこと。
+BrazeからBrazeへのWebhookを使用すると、Webhookを使用してBraze REST APIと通信し、当社のAPIでできることは何でもできる。基本的に、これはBrazeからBrazeに通信するWebhookです。詳細については、「[Braze to Braze Webhooks][4]」の記事を参照してください。
 
 ## 非推奨
 
 ### Windows SDK
-2022年3月24日をもって、[Braze Windows SDKは][6]非推奨となり、Brazeダッシュボードで新しいWindowsアプリを作成することはできない。 
+2022年3月24日より、[Braze Windows SDK][6] は非推奨となっており、Braze ダッシュボードで新しい Windows アプリを作成することはできません。 
 
-### 百度プッシュの統合
-2022年3月24日をもって、[Braze Baidu Push Integrationは][7]非推奨となり、Brazeダッシュボードで新しいBaiduアプリを作成することはできない。 
+### Baiduプッシュ統合
+2022年3月24日より、[Braze Baidu プッシュ統合][7]は非推奨となっており、Braze ダッシュボードで新しいBaidu アプリを作成することはできません。 
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
 ### Tealium for Currents
 
-Brazeと[Tealiumの][5]統合により、2つのシステム間の情報の流れをシームレスにコントロールすることができる。Currentsを使えば、データをTealiumに接続し、成長スタック全体で実行可能にすることもできる。
+Braze と [Tealium][5] の統合により、2つのシステム間の情報フローをシームレスに制御できます。Currents では、データを Tealium に接続し、グローススタック (growth stack) 全体で実用的なデータにすることもできます。
 
 
 [1]: {{site.baseurl}}/user_guide/data_and_analytics/analytics/
diff --git a/_lang/ja/_help/release_notes/2022/5_31_22.md b/_lang/ja/_help/release_notes/2022/5_31_22.md
index 19dcb059a28..48842892474 100644
--- a/_lang/ja/_help/release_notes/2022/5_31_22.md
+++ b/_lang/ja/_help/release_notes/2022/5_31_22.md
@@ -11,11 +11,11 @@ alias: "/help/release_notes/2022/july/"
 
 ## 受信トレイビジョン
 
-Inbox Visionを使えば、ドラッグ＆ドロップで作成したメールキャンペーンが、送信前にすべてのメールクライアントやモバイルプラットフォームで整合性がとれているかをチェックできる。詳しくは[Inbox Visionを]({{site.baseurl}}/user_guide/message_building_by_channel/email/inbox_vision/)ご覧いただきたい。
+Inbox Visionを使えば、ドラッグ＆ドロップで作成したメールキャンペーンが、送信前にすべてのメールクライアントやモバイルプラットフォームで整合性がとれているかをチェックできる。詳しくは、[Inbox Vision]({{site.baseurl}}/user_guide/message_building_by_channel/email/inbox_vision/)を参照してください。
 
 ## HTMLエンジンを更新
 
-ドラッグ＆ドロップ・エディターからHTMLを生成する基礎となるエンジンが最適化され、更新された結果、HTMLファイルの圧縮とレンダリングに関する利点がもたらされた。アップデートの詳細については、[Updated HTML engineを]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/#updated-html-engine/)チェックしてほしい。
+ドラッグ＆ドロップ・エディターからHTMLを生成する基礎となるエンジンが最適化され、更新された結果、HTMLファイルの圧縮とレンダリングに関する利点がもたらされた。更新sについて詳しくは、[更新 d HTML engine]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/#updated-html-engine/)をご覧ください。
 
 ## キーワードカテゴリー別リターゲティングを更新
 
@@ -25,27 +25,27 @@ Inbox Visionを使えば、ドラッグ＆ドロップで作成したメール
 
 [イベント・プロパティ・セグメンテーションによって]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/#event-property-segmentation/)、行われたカスタム・イベントと、それらのイベントに関連するプロパティに基づいて、ユーザをターゲットにすることができる。この機能により、購入イベントとカスタムイベントをセグメント化するときのフィルターオプションが追加されます。
 
-## オーディエンスはグーグルに同期する
+## Google へのオーディエンス同期
 
-Braze Audience Sync to Googleの実装プロセスが簡素化され、Brazeに複数のGoogle Adsアカウントへのアクセスを許可できるようになった。詳しくは、[Audience Sync to Googleを]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/)参照のこと。 
+Braze の Google へのオーディエンス同期の実装プロセスが簡素化され、Braze に複数の Google 広告アカウントへのアクセスを許可できるようになりました。詳細については、「[Google へのオーディエンス同期]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/)」を参照してください。 
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
 ### Amperity - 顧客データプラットフォーム
 
-Brazeと[Amperityの]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/amperity/)統合は、2つのプラットフォーム間で顧客の統一されたビューを提供する。この統合では、Amperityのユーザーリストを作成することで、ユーザーリストを同期し、AmperityのユーザーデータをBrazeのユーザーアカウントにマッピングすることができる。 
+Braze と [Amperity]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/amperity/) の統合により、2 つのプラットフォームにわたる顧客の統合ビューが提供されます。この統合により、Amperity ユーザーリストを作成して、ユーザーリストを同期し、Amperity ユーザーデータを Braze ユーザーアカウントにマッピングできます。 
 
 ### Dynamic 365 Customer Insights - 顧客データプラットフォーム
 
-Brazeと[Dynamics 365 Customer Insightsの]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights/)統合により、キャンペーンやCanvasesで使用する顧客セグメントをBrazeにエクスポートできる。
+Braze と [Dynamics 365 Customer Insights]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights/) の統合により、顧客セグメントを Braze にエクスポートしてキャンペーンやキャンバスで使用できるようになります。
 
-### エクストレイル - ロイヤルティ
+### Extole - ロイヤルティ
 
-Brazeと[Extoleの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/extole/)統合により、Extoleの友達紹介プログラムや成長プログラムから顧客イベントや属性をBrazeに取り込むことができ、顧客獲得、エンゲージメント、ロイヤルティを高める、よりパーソナライズされたマーケティングキャンペーンを作成できるようになる。パーソナライズされた共有コードやリンクなど、Extoleのコンテンツ属性をBrazeのコミュニケーションに動的に取り込むこともできる。
+Braze と [Extole]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/extole/) の統合により、Extole の友人紹介プログラムや成長プログラムからカスタムイベントや属性を Braze に取り込むことができ、顧客の獲得、エンゲージメント、ロイヤルティを高める、よりパーソナライズされたマーケティングキャンペーンを作成できるようになります。パーソナライズされた共有コードやリンクなど、Extoleのコンテンツ属性をBrazeのコミュニケーションに動的に取り込むこともできる。
 
-### ヒープ - コーホートのインポート
+### Heap - コホートインポート
 
-Brazeと[Heapの]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/heap/)統合により、HeapデータをBrazeにインポートし、ユーザーコホートを作成したり、BrazeデータをHeapにエクスポートしてセグメントを作成することができる。
+Braze および[Heap]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/heap/) インテグレーションを使用すると、ヒープデータをBrazeにインポートしたり、ユーザー コホートs を作成したり、BrazeデータをHeap にエクスポートしてSegments を作成したりできます。
 
 ### ハイタッチ - ワークフローの自動化
 
@@ -53,16 +53,16 @@ Brazeと[Hightoughの]({{site.baseurl}}/partners/data_and_infrastructure_agility
 
 ### ピーク - ダイナミックコンテンツ
 
-Brazeと[Peakの]({{site.baseurl}}/partners/message_personalization/dynamic_content/peak/)統合により、顧客の行動やインタラクションに基づいて予測された解約確率や属性をBrazeにインポートし、顧客セグメンテーションやターゲティングに使用することができる。 
+Brazeと[Peak]({{site.baseurl}}/partners/message_personalization/dynamic_content/peak/)積分により、Brazeに顧客行動sとinterアクションsに基づいて予測されたチャーン確率と属性sを取り込み、顧客 セグメンテーションとターゲティングに使用することができます。 
 
 ### Shopify - Eコマース
 
-Brazeと[Shopifyの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/)統合は、放棄されたチェックアウトの遅延、優先商品識別子の設定、および`shopify_paid_order` 、`shopify_partially_fulfilled_order` 、`shopify_fulfilled_order` 、`shopify_cancelled_order` 、`shopify_created_refund` を含むいくつかの新しいShopifyイベントを提供するように拡張された。 
+Braze と [Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/) の統合が拡張され、購入手続き放棄の遅延、優先製品 ID の設定、`shopify_paid_order`、`shopify_partially_fulfilled_order`、`shopify_fulfilled_order`、`shopify_cancelled_order`、`shopify_created_refund` などのいくつかの新しい Shopify イベントが提供されるようになりました。 
 
 ### Survicate - アンケート
 
-Brazeと[Survicateの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/surveys/survicate/)統合により、メールにアンケートリンクを記載したり、アンケートのスニペットを直接埋め込んで回答率を高めることができる。アンケートが完了したら、Survicateに戻ってアンケート回答者の属性と回答を特定し、分析する。
+Braze と [Survicate]({{site.baseurl}}/partners/message_orchestration/channel_extensions/surveys/survicate/) の統合により、回答率の向上のためにメールにアンケートリンクを組み込むか、アンケートスニペットを直接埋め込むことができます。アンケートが完成したら Survicate に戻り、アンケート回答者の属性と回答を特定して分析します。
 
-### Viralsweep - 忠誠心
+### Viralsweep - ロイヤルティ
 
 Brazeと[ViralSweepの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/viralsweep/)統合により、ViralSweepプラットフォーム上で懸賞やコンテストを開催し（EメールやSMSのリストを増やす）、懸賞やコンテストの応募情報をBrazeに送信してキャンペーンやCanvasesで使用することができる。 
diff --git a/_lang/ja/_help/release_notes/2022/5_3_22.md b/_lang/ja/_help/release_notes/2022/5_3_22.md
index c6d76b95329..b967f9e0617 100644
--- a/_lang/ja/_help/release_notes/2022/5_3_22.md
+++ b/_lang/ja/_help/release_notes/2022/5_3_22.md
@@ -19,7 +19,7 @@ alias: "/help/release_notes/2022/june/"
 
 ## AIコピーライティングアシスタント
 
-Braze [AIコピーライティングアシスタント]({{site.baseurl}}/user_guide/intelligence/ai_copywriting#ai-copywriting-assistant)は、簡単な製品名や説明をOpenAIのGPT3コピー生成ツールに渡し、人間のようなマーケティングコピーを生成してメッセージングに使用します。この機能は、Brazeダッシュボードのほとんどのメッセージ作成者にデフォルトで利用できます。
+Braze [AIコピーライティングアシスタント]({{site.baseurl}}/user_guide/intelligence/ai_copywriting#ai-copywriting-assistant)は、簡単な製品名や説明をOpenAIのGPT3コピー生成ツールに渡し、人間のようなマーケティングコピーを生成してメッセージングに使用します。この機能は、Braze ダッシュボード内のほとんどのメッセージ作成画面でデフォルトで使用できます。
 
 ## iOSプッシュ通知ユニットテストガイド
 
@@ -27,19 +27,19 @@ Braze [AIコピーライティングアシスタント]({{site.baseurl}}/user_gu
 
 ## Googleプライバシーアンケート
 
-2022年4月現在、Android開発者はプライバシーとセキュリティの実践を開示するためにGoogle Playの\[データセーフティフォーム][4]を完了する必要があります。[このガイド]({{site.baseurl}}/developer_guide/platform_integration_guides/android/google_play_privacy#google-play-privacy-questionnaire)は、Brazeがアプリデータをどのように処理するかに関する情報を含む新しいフォームの記入方法についての指示を提供します。 
+2022年4月現在、Android 開発者は、プライバシーとセキュリティの方針を開示するために、Google Play の \[データセーフティフォーム][4] に記入する必要があります。[このガイド]({{site.baseurl}}/developer_guide/platform_integration_guides/android/google_play_privacy#google-play-privacy-questionnaire)は、Brazeがアプリデータをどのように処理するかに関する情報を含む新しいフォームの記入方法についての指示を提供します。 
 
 ## RelayState SAML SSO
 
-初回のシングルサインオン設定手順が更新され、`RelayState` API キーの使用が推奨されるようになりました。詳細については、[SAML SSO 設定]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/)および対応する[OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/)、[Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/)、[Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/)の記事を参照してください。 
+シングルサインオンの初期設定手順が、`RelayState` API キーの使用を推奨するよう更新されました。詳細については、[SAML SSO 設定]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/)および対応する[OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/)、[Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/)、[Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/)の記事を参照してください。 
 
 ## Talon.One 統合の更新
 
-私たちの[Talon.One]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/talonone#talonone)パートナーシップ記事には、更新された統合手順、エンドポイント、および例が含まれています。パートナーシップTalon.Oneを活用している場合は、統合を適宜更新することをお勧めします。
+私たちの[Talon.One]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/talonone#talonone)パートナーシップ記事には、更新された統合手順、エンドポイント、および例が含まれています。Talon.One パートナーシップを活用している場合は、それに応じて統合を更新することをお勧めします。
 
-## Braze Web SDK V4 リリース
+## Braze Web SDK V4のリリース
 
-Braze SDKチームはWeb SDK v4をリリースしました。破壊的変更、更新、および追加のリストについては、当社のWeb SDK [changelog](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)をご覧ください。V3からV4にアップグレードする人のために[アップグレードガイド](https://github.com/braze-inc/braze-web-sdk/blob/master/UPGRADE_GUIDE.md)が作成されました。
+Braze SDK チームが Web SDK v4をリリースしました。破壊的変更、更新、および追加のリストについては、当社のWeb SDK [changelog](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)をご覧ください。V3からV4にアップグレードする人のために[アップグレードガイド](https://github.com/braze-inc/braze-web-sdk/blob/master/UPGRADE_GUIDE.md)が作成されました。
 
 ## Grouparoo 廃止
 
diff --git a/_lang/ja/_help/release_notes/2022/6_28_22.md b/_lang/ja/_help/release_notes/2022/6_28_22.md
index c4503d37f1d..1ed502e94d4 100644
--- a/_lang/ja/_help/release_notes/2022/6_28_22.md
+++ b/_lang/ja/_help/release_notes/2022/6_28_22.md
@@ -3,34 +3,34 @@ nav_title: 2022年6月6日
 page_order: 5
 noindex: true
 page_type: update
-description: "この記事には、2022年6月22日のリリースノートが含まれている。"
+description: "この記事には、2023年6月22日のリリースノートが含まれています。"
 alias: "/help/release_notes/2022/august/"
 ---
 
 # 2022年6月6日リリース
 
-## キャンバス・メッセージ・ステップの配信検証
+## キャンバスメッセージステップの配信検証
 
-キャンバスの[メッセージ・ステップで]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/)配信検証をオンにすると、メッセージ送信時に視聴者が配信基準を満たしていることを確認するための追加チェックを行うことができる。この設定は、サイレント時間、インテリジェントタイミング、レート制限のいずれかがアクティブになっている場合に推奨されます。
+キャンバス[メッセージステップ]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/)で配信検証をオンにすると、メッセージ送信時にオーディエンスが配信基準を満たしていることを確認する追加チェックを実行できます。この設定は、サイレント時間、インテリジェントタイミング、レート制限のいずれかがアクティブになっている場合に推奨されます。
 
 ## Android 13 SDK アップグレードガイド
 
-2022年6月8日現在、アンドロイド13は[プラットフォーム安定性マイルストーンに達して](https://developer.android.com/about/versions/13/overview#platform_stability)いる。これは、すべての変更が最終決定されたことを意味し、アプリのユーザーは間もなく自分のデバイスをアップグレードできるようになる。Android 13で導入された関連する変更と、Braze Android SDK統合に必要なアップグレード手順の詳細については、[Android 13 SDKアップグレードガイドを]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_13/)参照。
+2022年6月8日時点で、Android 13は [Platform Stability マイルストーン](https://developer.android.com/about/versions/13/overview#platform_stability)に達しています。つまり、すべての変更が完了しており、アプリユーザーがデバイスを間もなくアップグレードできるようになります。Android 13で導入された関連する変更と、Braze Android SDK の統合に必要なアップグレードステップの詳細については、[Android 13 SDK アップグレードガイド]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_13/)を参照してください。
 
 ## iOS 16 SDK アップグレードガイド
 
-iOS 16 Beta 2（2022年6月22日）の時点で、Braze SDKの統合に影響するiOS 16の機能的な変更はなかった。これは、AppleがiOS 16の新しいベータ版をリリースするにつれて変わる可能性があるため、定期的に[iOS 16 SDK アップグレードガイド]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/ios_16/)を確認することをお勧めします。このガイドでは、iOS 16で導入された関連する変更について説明しています。
+iOS 16 Beta 2 (2022年6月22日) 時点で、Braze SDK の統合に影響する iOS 16の機能的な変更はありませんでした。これは、Apple が iOS 16の新しいベータ版をリリースすると変わる可能性があるため、[iOS 16 SDK アップグレードガイド]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/ios_16/)を定期的に確認することをお勧めします。このガイドでは、iOS 16で導入された関連する変更について説明されています。
 
-## チャンネルガイドを送る前に知っておこう
+## チャネルの送信前に必要な知識ガイド
 
-キャンペーンとキャンバスを自信を持って立ち上げよう！プレローンチ・ガイドを参照した後、コンテンツ・カード、Eメール、アプリ内メッセージ、プッシュ、SMSの最終チェックリストや "gotchas "については、[Know before you send: channelsを]({{site.baseurl}}/help/help_articles/campaigns_and_canvas/know_before_send/)参照されたい。
+キャンペーンとキャンバスを自信を持って開始しましょう。開始前ガイドにアクセスした後、コンテンツカード、メール、アプリ内メッセージ、プッシュ、SMS のチェックまたは「gotcha」の最終リストを確認するには、「[送信前に必要な知識: チャネル]({{site.baseurl}}/help/help_articles/campaigns_and_canvas/know_before_send/)」を参照してください。
 
-## キャンペーンとキャンバスの属性名とIDがソース間でどのように異なるか
+## ソース間におけるキャンペーンとキャンバスの属性の名前および ID の違い
 
-キャンペーン、キャンバス、キャンバスステップの名前とIDはすべて、Liquid、REST API、Currentsで利用できる。これらの属性は、3つのソースすべてで同じ値にマッピングされるが、名前は異なる場合がある。この[新しいヘルプ記事を]({{site.baseurl}}/help/help_articles/api/attribute_name_id_across_sources/)読めば、この3つのつながりを理解することができるだろう。
+キャンペーン、キャンバス、キャンバスステップの名前と ID はすべて、Liquid、REST API、Currents で利用できます。これらの属性は、3つのソースすべてで同じ値にマッピングされますが、名前は異なる場合があります。こちらの[新しいヘルプ記事]({{site.baseurl}}/help/help_articles/api/attribute_name_id_across_sources/)は、これら3つの関係を理解するのに役立ちます。
 
-## Braze 学習
+## Braze ラーニング
 
-[Braze Learning](https://learning.braze.com/)（旧Learning at Braze (LAB)）は、マーケティング担当者、管理者、開発者向けに、Brazeの主要概念と基礎に関するコースを提供している。一部の記事でBraze Learningのロゴに注目し、リンクをクリックするとそのトピックについて詳しく知ることができる。
+[Braze ラーニング](https://learning.braze.com/) （旧 Learning at Braze (LAB)） は、マーケター、管理者、開発者向けに、Braze の主要概念と基礎に関するコースを提供しています。一部の記事には Braze ラーニングのロゴが含まれており、リンクをクリックすると該当トピックについて詳しく知ることができます。
 
-![カスタム属性の記事にあるBraze learningのロゴは、カスタム属性のためのBraze Learningコース]({% image_buster /assets/img_archive/release_notes_brazelearning.png %}) へ行く。
\ No newline at end of file
+![カスタム属性の Braze ラーニングコースにリンクされている、カスタム属性の記事の Braze ラーニングロゴ]({% image_buster /assets/img_archive/release_notes_brazelearning.png %})
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2022/7_26_22.md b/_lang/ja/_help/release_notes/2022/7_26_22.md
index e9a353ce6fc..59117673047 100644
--- a/_lang/ja/_help/release_notes/2022/7_26_22.md
+++ b/_lang/ja/_help/release_notes/2022/7_26_22.md
@@ -3,14 +3,14 @@ nav_title: 2022年7月26日
 page_order: 4
 noindex: true
 page_type: update
-description: "この記事には、2022年7月26日のリリースノートが含まれている。"
+description: "この記事は、7/26/2022のリリースノートを含みます。"
 alias: "/help/release_notes/2022/september/"
 ---
 
 # 2022年7月26日リリース
 
 ## キャンバスフロー
-キャンバス製品の最新バージョン、[キャンバス・フローが]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#editing-a-step)リリースされた。Canvas Flowを使えば、軽量の[Canvasコンポーネント]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components)、[永続的なエントリー・プロパティ]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_persistent_entry_properties/)、[起動後の編集に]({{site.baseurl}}/post-launch_edits)アクセスできる。
+Canvas 製品の最新バージョン[Canvas Flow]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#editing-a-step) がリリースされました。Canvas Flow を使用すると、軽量の[Canvas コンポーネント]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components)、[永続的なエントリプロパティ]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_persistent_entry_properties/)、および[起動後編集]({{site.baseurl}}/post-launch_edits) にアクセスできます。
 
 ![]({% image_buster /assets/img/canvas_flow.png %})
 
@@ -18,34 +18,34 @@ alias: "/help/release_notes/2022/september/"
 [オブジェクトの配列を]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects#array-of-objects)使用して、関連する属性をグループ化する。例えば、1 人のユーザーに属するペットオブジェクト、曲オブジェクト、アカウントオブジェクトをすべて含むグループがあるとします。これらのオブジェクト配列を使用して、Liquid でメッセージングをパーソナライズしたり、オブジェクト内のいずれかの要素が条件に一致する場合にオーディエンスセグメントを作成したりできます。
 
 ## パートナーとの統合を更新
-[Amplitude Recommendと]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_recommend/) [mParticleの]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle/)統合ステップが更新された。これらのパートナーを活用する場合は、そのパートナーのドキュメントを参照し、最新のセットアップに従っていることを確認すること。
+[ Amplitude Recommend]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_recommend/) および[mParticle]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle/) に更新d 積分ステップs が追加されました。これらのパートナーを活用する場合は、そのパートナーのドキュメントを参照し、最新のセットアップに従っていることを確認すること。
 
 ## Shopifyの要件
-- [前提]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/#prerequisites)条件に記載されている必要なユーザー権限が更新された。
-- `price`,`total_price`,`total_discounts`,`amount` プロパティを含むShopify[ペイロードの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/#supported-shopify-events)例が更新され、これらのプロパティが文字列ではなく数字としてフォーマットされるようになった。
+- [前提条件]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/#prerequisites)に記載されている必要なユーザー権限が更新されました。
+- 例`price`、`total_price`、`total_discounts`、`total_discounts`、および`amount` プロパティーを含むShopify{<span=>pay 読み込む s<<span=} は、これらのプロパティーを文字列ではなく数値としてフォーマットするために更新d になっています。
 
 ## 予想アップデート
-解約予測や購入予測の最大期間は14日間から60日間に延長された。
+解約予測sと購買予測sの最長の期間は、14日から60日に増加した。
 
 ## SDKのアップデート
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 - [Web SDK 4.1.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#410)
 - [Cordova SDK 2.30.1](https://github.com/Appboy/appboy-cordova-sdk/blob/master/CHANGELOG.md#2301)
 - [Unity SDK 3.8.1](https://github.com/Appboy/appboy-unity-sdk/blob/master/CHANGELOG.md#381)
 - [Swift SDK 5.0.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#501)
 - [Roku SDK 0.1.2](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md#012)
 - [React Native SDK 1.37.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#1370)
-  - Braze React Native SDKが、デフォルトオブジェクトをESモジュールとしてエクスポートするようになった。現在、`require()` を使用してSDKをインポートしている場合は、標準のESモジュールとしてインポートする必要がある（例えば、"`@braze/react-native-sdk`"からBrazeをインポートする）。
+  - Braze対応ネイティブSDKは、ESモジュールとしてデフォルトオブジェクトをエクスポートします。現在、`require()` を使用してSDKをインポートしている場合は、標準のESモジュールとしてインポートする必要がある（例えば、"`@braze/react-native-sdk`"からBrazeをインポートする）。
 - [Android SDK 22.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2200)
-  - `Appboy.java` は現在、`Braze.kt` 。Kotlinクライアントは、必要に応じてBrazeシングルトンのKotlinプロパティの使用をサポートするようにコードを更新する必要がある。
-    - `Braze.registerPushToken()`/`Braze.getRegisteredPushToken()` が`Braze.setRegisteredPushToken()/Braze.getRegisteredPushToken()` になった。Kotlinを使用している場合は、`Braze.registeredPushToken`.
-    - `Braze.getDeviceId` は現在、Kotlinのための`Braze.deviceId` 。
-    - `Braze.enableMockNetworkAppboyRequestsAndDropEventsMode` は現在、`Braze.enableMockNetworkRequestsAndDropEventsMode()` 。
-    - `Appboy.java` は削除された。例えば、`Appboy.getInstance()` のような通話は、今後`Braze.getInstance()` 。
+  - `Appboy.java` 現在は`Braze.kt` です。Kotlinクライアントは、必要に応じてBrazeシングルトンのKotlinプロパティの使用をサポートするようにコードを更新する必要がある。
+    - `Braze.registerPushToken()`/`Braze.getRegisteredPushToken()` が`Braze.setRegisteredPushToken()/Braze.getRegisteredPushToken()` になりました。Kotlin を使用する場合は、プロパティ`Braze.registeredPushToken` を使用します。
+    - `Braze.getDeviceId` 現在は、Kotlin の`Braze.deviceId` だけです。
+    - `Braze.enableMockNetworkAppboyRequestsAndDropEventsMode` 現在は`Braze.enableMockNetworkRequestsAndDropEventsMode()` です。
+    - `Appboy.java` 削除されました。たとえば、`Appboy.getInstance()` のような呼び出しは、`Braze.getInstance()` を前に進める必要があります。
     - `setCustomAppboyNotificationFactory()` を`setCustomBrazeNotificationFactory()` /`customBrazeNotificationFactory` に置き換えた。
     - `enableMockAppboyNetworkRequestsAndDropEventsMode` を`enableMockNetworkRequestsAndDropEventsMode` に改名した。
   - `com.appboy.IBrazeEndpointProvider` を`com.braze.IBrazeEndpointProvider` に移動した。
   - `com.braze.events.IEventSubscriber` を`com.braze.events.IEventSubscriber` に改名した。
-  - `Appboy.registerAppboyPushMessages()` /`Appboy.getAppboyPushMessageRegistrationId()` を削除した。`getRegisteredPushToken()` /`setRegisteredPushToken()` 。
+  - `Appboy.registerAppboyPushMessages()` / `Appboy.getAppboyPushMessageRegistrationId()` を削除しました。`getRegisteredPushToken()` / `setRegisteredPushToken()`に置き換えられました。
   - `IAppboyNotificationFactory` を`IBrazeNotificationFactory` に置き換えた。
-  - `com.appboy.ui.inappmessage.listeners.IHtmlInAppMessageActionListener` を削除した。代わりに`com.braze.ui.inappmessage.listeners.IHtmlInAppMessageActionListener` 。
+  - `com.appboy.ui.inappmessage.listeners.IHtmlInAppMessageActionListener` が削除されました。代わりに`com.braze.ui.inappmessage.listeners.IHtmlInAppMessageActionListener` を使用します。
diff --git a/_lang/ja/_help/release_notes/2022/8_23_22.md b/_lang/ja/_help/release_notes/2022/8_23_22.md
index 1225411bdfb..43971ab33a6 100644
--- a/_lang/ja/_help/release_notes/2022/8_23_22.md
+++ b/_lang/ja/_help/release_notes/2022/8_23_22.md
@@ -10,15 +10,15 @@ description: "この記事には、2022年8月23日のリリースノートが
 
 ## 開発者ポータル
 
-Brazeを使用している他の開発者とつながり、学び、刺激を受ける。[開発者ポータルを](https://www.braze.com/dev-portal)チェックし、SlackのBraze開発者コミュニティに参加する。
+Brazeを使用している他の開発者とつながり、学び、刺激を受ける。私たちの[開発者ポータル](https://www.braze.com/dev-portal)をチェックして、SlackでBraze 開発者コミュニティーに参加しましょう。
 
 ## メッセージのアーカイブ
 
-[メッセージアーカイブは]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/)、アーカイブやコンプライアンス目的でユーザーに送信されたメッセージのコピーをS3バケットに保存できるアドオン機能だ。
+[Message Archiving]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/) は、アーカイブまたは準拠のために ユーザー に送信されたメッセージのコピーを S3 バケットに保存できるアドオン機能です。
 
 ## キャンバスエントリのプロパティとイベントのプロパティ
 
-名前は似ているが、Canvasエントリー・プロパティとイベント・プロパティは、Canvasワークフロー内で異なる機能を果たす。各プロパティを使用するタイミングや、[Canvasのエントリー・プロパティとイベント・プロパティにおける]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties)動作の違いについて詳しく説明する。
+名前は似ていますが、キャンバスエントリのプロパティとイベントプロパティは、キャンバスワークフロー内では機能が異なります。それぞれのプロパティをいつ使用するか、および[キャンバスのエントリプロパティーとイベントプロパティー]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties) の動作の違いについて詳しく説明します。
 
 ## 追跡リンクエイリアス
 
@@ -26,54 +26,54 @@ Brazeを使用している他の開発者とつながり、学び、刺激を受
 
 ## Liquid 5
 
-Brazeは**ShopifyのLiquid 5を**含むLiquidのサポートを更新した。新しいBrazeユーザーには、Liquid 5が一般的に利用できる。既存のBrazeユーザーにとっては、Liquid 5は早期アクセスである。[リキッド5の新機能について]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid#whats-new-with-liquid-5)もっと知る。
+Braze は、Liquid のサポートを **Shopify の Liquid 5**まで (これを含む) に更新しました。新しい Braze ユーザーについては、Liquid 5は一般的に利用可能です。既存の Braze ユーザーについては、Liquid 5は早期アクセスです。[Liquid 5]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid#whats-new-with-liquid-5)の新機能について詳しく説明します。
 
 ## キャンペーンとキャンバスのベストプラクティス
 
-キャンペーンやキャンバスを成功させるのは複雑なことなので、メッセージを最大限に活用するために知っておくべきベストプラクティスのリストをチェックしよう。
+有効なキャンペーンやキャンバスの作成は複雑な作業になる可能性があるため、メッセージングを最大限に活用するために知っておくべきベストプラクティスの一覧を確認してください。
 
 - [キャンペーンのベストプラクティス]({{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/best_practices/)
 - [キャンバスのベストプラクティス]({{site.baseurl}}/user_guide/engagement_tools/canvas/best_practices/)
 
 ## キャンペーンの検索
 
-API識別子でキャンペーンを検索できることをご存知だろうか？キャンペーンを絞り込んで検索する他の方法については、「[キャンペーンを検索する]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/search_campaigns/)」で詳しく説明する。
+API識別子でキャンペーンを検索できることをご存知だろうか？この方法やその他の方法によるキャンペーンのフィルタリングと検索の詳細については、[キャンペーンの検索]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/search_campaigns/)を参照してください。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
 ### IAM Studio - メッセージテンプレート
 
-Brazeと[IAM Studioの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/iam_studio/)統合により、カスタマイズ可能なアプリ内メッセージテンプレートをBrazeのアプリ内メッセージに簡単に挿入することができ、画像置換、テキスト変更、ディープリンク設定、カスタム属性、イベント設定を提供する。IAM Studioを使えば、メッセージ作成時間を短縮し、コンテンツプランニングにより多くの時間を割くことができる。
+Brazeと[IAM Studioの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/iam_studio/)統合により、カスタマイズ可能なアプリ内メッセージテンプレートをBrazeのアプリ内メッセージに簡単に挿入することができ、画像置換、テキスト変更、ディープリンク設定、カスタム属性、イベント設定を提供する。IAM Studio を使用すると、メッセージの作成時間を短縮し、コンテンツ計画により多くの時間を費やすことができます。
 
 ### actionable.me \- アナリティクス
 
-Brazeと [actionable.me]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/actionableme/)の統合により、Brazeの活用状況をモニターするサービスを展開できる。ツールとプロセスを組み合わせることで、CRMのパフォーマンスを迅速にベンチマークし、新たな機会を特定し、より良いパフォーマンスを実現する方法を提案する。
+Braze と [actionable.me]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/actionableme/) の統合により、Braze の使用状況を監視するためのサービスをデプロイできます。ツールとプロセスを組み合わせることで、CRM のパフォーマンスが迅速にベンチマークされ、新しい機会が特定され、パフォーマンスの向上に関する推奨事項が提供されます。
 
 ### Storyly - コーホートのインポート
 
-Brazeと[Storylyの]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/storyly/)統合により、BrazeのセグメントをStorylyプラットフォームのオーディエンスとして使うことができる。この統合によって、あなたは次のことができる：
+Braze と [Storyly]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/storyly/) の統合により、Braze のセグメントを Storyly プラットフォームのオーディエンスとして使用できるようになります。この統合により、次のことが可能になります。
 
 - 特定のストーリーを持つセグメントをターゲットにする
 - ユーザー属性を使ってストーリー・コンテンツをパーソナライズする
 
 ### Lokalise - ローカライゼーション
 
-Brazeと[Lokaliseの]({{site.baseurl}}/partners/message_personalization/localization/lokalise/)統合は、Connected Contentを活用し、ユーザーの言語設定に基づいてBrazeキャンペーンに翻訳コンテンツを簡単に挿入できる。
+Braze と [Lokalise]({{site.baseurl}}/partners/message_personalization/localization/lokalise/) の統合により、Connected Content を活用し、ユーザーの言語設定に基づいて翻訳されたコンテンツを Braze キャンペーンに簡単に挿入できるようになります。
 
-### Quikly - リターゲティング
+### クイックリターゲティング
 
-Brazeと[Quiklyの]({{site.baseurl}}/partners/message_orchestration/additional_channels/retargeting/quikly/)パートナーシップにより、Brazeのカスタマージャーニー内のイベントでのコンバージョンを加速させることができる。Quiklyは、緊急性心理学を利用し、楽しく、即座に消費者のやる気を起こさせる。例えば、ブランドはQuiklyを使って、EメールやSMSの新規登録者を即座にBrazeに直接取り込んだり、モバイルアプリのダウンロードなど、他の重要なマーケティング目標の動機付けを行うことができる。
+Brazeと[Quikly]({{site.baseurl}}/partners/message_orchestration/additional_channels/retargeting/quikly/)パートナーシップにより、Braze カスタマージャーニー内の行動に対するコンバージョンを加速することができます。Quiklyは、緊急性心理学を利用し、楽しく、即座に消費者のやる気を起こさせる。例えば、ブランドは Quikly を使用して、新しいメールや SMS の購読者を Braze にすぐに直接取り込んだり、モバイルアプリのダウンロードなどの他の重要なマーケティング目標達成を促進したりできます。
 
 ### DataGrail - データプライバシーとコンプライアンス
 
-Brazeと[DataGrailの]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_privacy/datagrail/)統合により、Braze内に収集・保存された消費者データを検出し、DSR（アクセス、削除、販売禁止要求）を迅速に処理することができる。Brazeは、自動化されたデータマッピングによって、消費者データが組織内のどこに存在するかの正確な青写真に追加される。プライバシーフレームワークを維持したり、処理活動の記録（RoPA）を作成したりするための調査やスプレッドシートはもう必要ない。
+Braze と [DataGrail]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_privacy/datagrail/) を統合すると、Braze 内で収集され、保存されている消費者データを検出して、DSR を迅速に処理できます (アクセス、削除、販売しないリクエスト)。自動化されたデータマッピングにより、消費者データが組織内のどこにあるかを正確に把握できるうえに、Braze が追加されるため、プライバシーフレームワークの維持や処理活動の記録 (RoPA) の作成にアンケートやスプレッドシートは不要になります。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Web SDK 4.2.0-4.2.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#421)
 - [iOS 4.5.0](https://github.com/Appboy/appboy-ios-sdk/blob/master/CHANGELOG.md#450)(Objective-C)
 - [iOS Swift 5.1.0-5.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#520)
 - [Android 23.0.0-23.0.1](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2301)
-    - `BaseContentCardView.bindViewHolder()` ジェネリック型の代わりに`Card` 。
+    - `BaseContentCardView.bindViewHolder()` で、汎用タイプの代わりに`Card` が使用されます。
diff --git a/_lang/ja/_help/release_notes/2022/9_20_22.md b/_lang/ja/_help/release_notes/2022/9_20_22.md
index 124f2fe3319..330168bb213 100644
--- a/_lang/ja/_help/release_notes/2022/9_20_22.md
+++ b/_lang/ja/_help/release_notes/2022/9_20_22.md
@@ -15,7 +15,7 @@ description: "この記事には2022年9月20日のリリースノートが含
 ターゲットセグメント内の各ユーザーに最も関与する可能性が高いバリアントを送信するには、[パーソナライズされたバリアント]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign/#optimizations)を使用します。
 
 ## キャンバスのテスト
-キャンバスを作成した後、オーディエンスのサイズやセグメンテーションフィルターの数などの詳細に応じて、起動前に実行したいチェックがいくつかあります。[テストキャンバスの送信]({{site.baseurl}}/user_guide/engagement_tools/canvas/testing_canvases/sending_test_canvases/)のヒントをチェックしてください。
+キャンバスを作成した後、オーディエンスのサイズやセグメンテーションフィルターの数などの詳細に応じて、開始前にいくつかの事項を確認することをお勧めします。[テストキャンバスの送信]({{site.baseurl}}/user_guide/engagement_tools/canvas/testing_canvases/sending_test_canvases/)でヒントを確認してください。
 
 ## Liquid 5
 既存のBrazeユーザー向けに、Liquid 5が一般提供されています。Liquid 5の新機能について[詳しくはこちら]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid#whats-new-with-liquid-5)。
@@ -27,14 +27,14 @@ Brazeと[Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extens
 
 ## SDKの更新
 
-以下のSDKアップデートがリリースされました。以下に重大な更新が記載されています。その他の更新については、対応するSDKの変更ログを確認してください。
+以下のSDKアップデートがリリースされました。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Android SDK 23.1.0–23.12](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
 - [React Native SDK v1.38.0–v1.38.1](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
-	- ネイティブ<sub>Android<}ブリッジを<sub>Braze<}Android<sub>SDK<}23.0.1に更新しました。
+	- ネイティブ Android ブリッジを Braze Android SDK 23.0.1に更新しました。
 	- ネイティブiOSブリッジをBraze iOS SDK 4.5.0に更新しました。
-	- Braze React Native Android SDKは、コンパイルに直接Kotlinを必要とするようになりました。
-- [Braze Expo プラグイン 0.4.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+	- Braze React Native Android SDKでは、コンパイルで Kotlin が直接必要になりました。
+- [Braze Expo プラグイン0.4.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
 	- プロップ`fcmSenderID`の名前を`firebaseCloudMessagingSenderId`に変更しました。
 - [Unity 3.9.0](https://github.com/Appboy/appboy-unity-sdk/blob/master/CHANGELOG.md)
 	- Androidプラグインを更新して、Braze Android SDK 23.1.0を使用しました。
diff --git a/_lang/ja/_help/release_notes/2023.md b/_lang/ja/_help/release_notes/2023.md
index 39b7c62e706..d123e1b56aa 100644
--- a/_lang/ja/_help/release_notes/2023.md
+++ b/_lang/ja/_help/release_notes/2023.md
@@ -3,10 +3,10 @@ page_order: 1
 nav_title: 2023
 layout: dev_guide
 noindex: true
-guide_top_header: "2023 リリースノート"
+guide_top_header: "2023年リリースノート"
 
 page_type: landing
-description: "このセクションには、2023年のリリースノートがあります。"
+description: "このセクションには、2023年のリリースノートが含まれています。"
 
 guide_menu_title: ""
 guide_menu_list:
diff --git a/_lang/ja/_help/release_notes/2023/10_17_23.md b/_lang/ja/_help/release_notes/2023/10_17_23.md
index 2b1dbe26ad2..83f1f4b557d 100644
--- a/_lang/ja/_help/release_notes/2023/10_17_23.md
+++ b/_lang/ja/_help/release_notes/2023/10_17_23.md
@@ -3,37 +3,37 @@ nav_title: 2023年10月17日
 page_order: 2
 noindex: true
 page_type: update
-description: "この記事には10/17/23のリリースノートが含まれている。"
+description: "この記事には、2023年10月17日のリリースノートが含まれています。"
  
 ---
 # 2023年10月17日リリース
 
 ## ワークスペースにコピーする
 
-[ワークスペース全体でキャンペーンをコピーすること]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/copying_to_workspace/)により、別のワークスペース内のキャンペーンのコピーから始めることで、メッセージ作成を迅速に開始できます。このコピーは、編集して開始するまで下書きとして残り、成功したメッセージング戦略を維持し、構築するのに役立ちます。
+[ワークスペース間でキャンペーンをコピー]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/copying_to_workspace/)すると、別のワークスペースにあるキャンペーンのコピーを利用して、メッセージの作成をすぐに開始できます。このコピーは、編集して開始するまで下書きとして残り、成功したメッセージング戦略を維持し、構築するのに役立ちます。
 
 ## Currents のテストコネクター
 
-[テストカレント・コネクターは]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/setting_up_currents/#test-currents-connectors)、既存のコネクターの無料バージョンで、テストやさまざまな行き先を試すために使用できる。Currents のテストは次のとおりです。
+[Currents のテストコネクター]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/setting_up_currents/#test-currents-connectors)は、弊社の既存のコネクターの無料版であり、さまざまな送信先のテストと試行に使用できます。Currents のテストは次のとおりです。
 
-- テストカレントコネクターの数に制限はない。
-- 30日ごとの合計で最大10,000件。このイベントの合計はダッシュボードで 1 時間ごとに更新されます。
+- 作成できる Currents のテストコネクターの数に制限はありません。
+- 30 日間の移動期間あたり、集計するイベントは最大 10,000 件です。このイベントの合計はダッシュボードで 1 時間ごとに更新されます。
 
 ## フィーチャーフラグ
 
-[機能フラグを]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/about/)使用すると、特定のユーザーまたはランダムに選択されたユーザーに対して、リモートで機能を有効または無効にすることができる。重要なのは、追加コードのデプロイやアプリストアのアップデートをすることなく、本番環境で機能をオン・オフできることだ。これにより、安心して新機能を展開することができる。
+[フィーチャーフラグ]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/about/)を使用すると、特定のユーザーまたは選択したユーザーの機能をリモートで有効または無効にすることができます。重要なのは、追加コードのデプロイやアプリストアのアップデートをすることなく、本番環境で機能をオン・オフできることだ。これにより、新しい機能を安全かつ確信を持ってロールアウトできます。
 
 ## 特集フラッグ実験
 
 [機能フラグ実験では]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/experiments/)、コンバージョン率を最適化するためにアプリケーションの変更をA/Bテストできる。マーケティング担当者は、機能フラグを使って、新機能がコンバージョン率にプラスに影響するかマイナスに影響するか、あるいはどの機能フラグのプロパティセットが最も最適かを判断することができる。
 
-## ユーザープロファイルをマージする
+## ユーザープロファイルのマージ
 
 **Search Users（ユーザ検索）**ページで検索した結果、複数のユーザ・プロファイルが返された場合、**Merge duplicates（重複をマージ）**ボタンをクリックして、[ユーザ・プロファイルをマージする]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles#merge-profiles)ことができる。どのユーザープロファイルを保持するかを選択できる。つまり、このプロファイルは保持され、マージされたプロファイルから属性を得ることになる。
 
 ## セグメント別パフォーマンスデータ
 
-クエリビルダーのレポートテンプレートを使って、キャンペーン、キャンバス、バリアント、ステップのセグメント別に[パフォーマンスデータを分解]({{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/#performance-data-by-segment)できるようになった。
+クエリビルダーのレポートテンプレートを使用すると、キャンペーン、キャンバス、バリアント、ステップの[パフォーマンスデータをセグメント別に分類]({{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/#performance-data-by-segment)できます。
 
 ## ユーザープロファイルを更新する
 
@@ -41,40 +41,40 @@ description: "この記事には10/17/23のリリースノートが含まれて
 
 ## SDKのアップデート
  
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
  
-- [Braze Segment Swift プラグイン v2.1.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md)
+- [Braze セグメント Swift プラグイン v2.1.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md)
 - [Web SDK v4.10.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - [Web SDK v5.0.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
     - この [`subscribeToFeatureFlagsUpdates()`](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#subscribetofeatureflagsupdates)コールバックは、リフレッシュの成否にかかわらず、常に呼び出されるようになった。更新の受信に失敗した場合、コールバックは現在キャッシュされている機能フラグで呼び出される。
     - この [`getFeatureFlag()`](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#getfeatureflag)メソッドは、機能フラグが存在しない場合、または機能フラグが無効になっている場合はNULLを返すようになった。
-    - 4.0.4で非推奨となっていた`logContentCardsDisplayed()` メソッドを削除した。
-    - 非推奨の初期化オプション`enableHtmlInAppMessages` を削除した。これは`allowUserSuppliedJavascript` オプションに置き換えるべきである。
-    - 4.9.0で非推奨とされたBannerクラスを削除し、以下のように変更した。 [`ImageOnly`](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.imageonly.html).
-    - `Banner` クラス削除の一環として、`ab-banner` CSS クラス名を削除した。CSSのカスタマイズは、代わりに`ab-image-only` 。
-    - SDKがランタイムエラーを投げなくなった。初期化前にBrazeのメソッドが呼ばれた場合、代わりに警告がコンソールに記録される。
-    - SDKが、カスタムHTMLアプリ内メッセージにデフォルトのBrazeアプリ内メッセージスタイルを追加しなくなった。これらのスタイルは、以前はレガシーなアプリ内メッセージタイプで使用されていた。
+    - 以前4.0.4 で非推奨になった`logContentCardsDisplayed()` メソッドを削除しました。
+    - 非推奨の初期化オプション`enableHtmlInAppMessages` を削除した。代わりに、`allowUserSuppliedJavascript` オプションに置き換える必要があります。
+    - 以前は4.9.0 で非推奨になったBanner クラスを削除しました。[`ImageOnly`](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.imageonly.html) が優先されます。
+    - `Banner` クラス削除の一環として、`ab-banner` CSS クラス名を削除した。CSSのカスタマイズでは、代わりに`ab-image-only` クラスを対象にする必要があります。
+    - SDK がランタイムエラーをどこにもスローしなくなりました。初期化前にBrazeのメソッドが呼ばれた場合、代わりに警告がコンソールに記録される。
+    - SDK で、カスタム HTML アプリ内メッセージにデフォルトの Braze アプリ内メッセージスタイルが追加されなくなりました。これらのスタイルは、以前はレガシーなアプリ内メッセージタイプで使用されていた。
 - [Android SDK 29.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
-    - `BannerImageCard`,`BannerImageCardView`,`BannerImageContentCardView` の名称を`ImageOnlyCard`,`ImageOnlyCardView`,`ImageOnlyContentCardView` に変更した。
-    - バナーカードに使用されていたすべてのスタイルが画像のみのカードに更新された。`banner` の文字があるキーはすべて`image_only` に置き換える。
-    - デバイスのブランド情報が送信されるようになった。これをブロックしたい場合は、データ収集をブロックするを参照のこと。
+    - `BannerImageCard`、`BannerImageCardView`、`BannerImageContentCardView` を `ImageOnlyCard`、`ImageOnlyCardView`、`ImageOnlyContentCardView` に名称変更しました。
+    - バナーカードに使用されていたすべてのスタイルが画像のみのカードに更新された。単語 `banner` を含むキーはすべて、`image_only` に置き換える必要があります。
+    - デバイスのブランド情報が送信されるようになった。これをブロックする場合は、「データ収集のブロック」を参照してください。
 - [Flutter SDK 7.0.0](https://pub.dev/packages/braze_plugin/changelog)
-    - ネイティブAndroidブリッジを[Braze Android SDK 26.1.1から27.0.1に](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2701)更新。
+    - ネイティブ Android ブリッジを [Braze Android SDK 26.1.1から27.0.1](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2701)に更新します。
     - Gradle 8のサポートを追加した。
 - [Swift SDK 7.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
     - `useUUIDAsDeviceId` コンフィギュレーションがデフォルトで有効になった。
-        - 影響の詳細については、「[IDFVの収集-スウィフト]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/swift_idfv/)」を参照のこと。
-    - バナー・コンテンツ・カード・タイプと対応するUI要素は、`ImageOnly` に名称が変更された。すべてのメンバー・メソッドとプロパティは変わらない。
+        - 影響の詳細については、こちらの「[IDFV の収集 - Swift]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/swift_idfv/)」を参照してください。
+    - バナーコンテンツカードタイプと対応するUI 要素の名前が`ImageOnly` に変更されました。すべてのメンバーメソッドおよびプロパティが同じままです。
         - `Braze.ContentCard.Banner` → `Braze.ContentCard.ImageOnly`
         - `BrazeContentCardUI.BannerCell` → `BrazeContentCardUI.ImageOnlyCell`
-    - BrazeUIのテキストレイアウトロジックの一部をリファクタリングし、新しいBraze.ModalTextView 。
+    - リファクターは、BrazeUI の一部のテキストレイアウトロジックを新しいBraze.ModalTextView クラスに変換します。
     - Feature Flagsメソッドの動作が更新された。
-        - `FeatureFlags.featureFlag(id:)` 存在しないIDに対してはnilを返すようになった。
-        - `FeatureFlags.subscribeToUpdates(:)` は、リフレッシュ・リクエストが成功または失敗で完了したときにコールバックをトリガーする。
-            - コールバックはまた、以前にキャッシュされたデータが存在する場合、最初のサブスクリプション時に即座にトリガーされる。
+        - `FeatureFlags.featureFlag(id:)` が、存在しないID に対して nil を返すようになりました。
+        - リフレッシュリクエストが成功または失敗で完了すると、`FeatureFlags.subscribeToUpdates(:)` によってコールバックがトリガーされます。
+            - 以前にキャッシュされたデータが存在する場合、コールバックは最初の購読時にすぐにトリガーされます。
 - [AppboyKit iOS SDK 4.6.0](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.6.0)
     - このリリースにはXcode`14.x` が必要である。
     - iOS 9とiOS 10のサポートを打ち切る。
     - Carthage 経由でインポートする際、時代遅れの`.framework` アセットのサポートを削除し、最新の`.xcframework` アセットを使用するようにした。
         - コマンド`carthage update --use-xcframeworks` を使って、適切なBrazeアセットをインポートする。
-        - `appboy_ios_sdk_full.json` 。 `appboy_ios_sdk.json`
+        - `appboy_ios_sdk_full.json` のサポートを削除し、代わりに `appboy_ios_sdk.json` を使用します。
diff --git a/_lang/ja/_help/release_notes/2023/11_14_23.md b/_lang/ja/_help/release_notes/2023/11_14_23.md
index 890feae76e6..ec74883fd25 100644
--- a/_lang/ja/_help/release_notes/2023/11_14_23.md
+++ b/_lang/ja/_help/release_notes/2023/11_14_23.md
@@ -3,40 +3,40 @@ nav_title: 2023年11月14日
 page_order: 1
 noindex: true
 page_type: update
-description: "この記事には11/14/23のリリースノートが含まれている。"
+description: "この記事には、2023年11月14日のリリースノートが含まれています。"
 ---
 
 # 2023年11月14日リリース
 
 ## Brazeを使い始める
 
-エキサイティングなニュースだ！Brazeの[マーケティング担当]({{site.baseurl}}/user_guide/getting_started)者と[開発者]({{site.baseurl}}/developer_guide/platform_wide/getting_started)向けに特別に作られた2つの入門セクションを紹介する。これらのセクションは、必要なツールやガイダンスを提供し、あなたがBrazeを使い始めるのを助けるように設計されている。飛び込んで探検を始めよう。
+エキサイティングなニュースです。Brazeの[マーケティング担当]({{site.baseurl}}/user_guide/getting_started)者と[開発者]({{site.baseurl}}/developer_guide/platform_wide/getting_started)向けに特別に作られた2つの入門セクションを紹介する。これらの項は、Brazeを使用して地面を走行させるのに役立つように設計されており、必要なすべての道具と手引きを提供します。詳細を確認しましょう。
 
 ## 新しいBrazeのダッシュボード・インスタンス
 
-Brazeは、ダッシュボードとRESTエンドポイント用のさまざまなインスタンスを管理している。新しいダッシュボード・インスタンス`US-07` を追加した。詳細については、[APIの概要を]({{site.baseurl}}/api/basics/)参照のこと。
+Brazeは、ダッシュボードとRESTエンドポイント用のさまざまなインスタンスを管理している。新しいダッシュボード・インスタンス`US-07` を追加した。詳細については、[API の概要]({{site.baseurl}}/api/basics/)を参照してください。
 
-## ロバスト・チャンネル
+## 強力なチャネル
 
 ### アプリ内メッセージ用のカスタムテンプレートをドラッグ＆ドロップで作成できる
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[アプリ内メッセージ用のカスタムテンプレートをドラッグ＆ドロップで]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/)使用できるようになり、ドラッグ＆ドロップエディターでアプリ内メッセージのデザインを開始できる。
+[アプリ内メッセージ用のカスタムドラッグ＆ドロップテンプレート]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/)を使用して、ドラッグ＆ドロップエディターでアプリ内メッセージのデザインを開始できるようになりました。
 
 ### SMSダブルオプトイン
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[SMSダブルオプトインは]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/sms_double_opt_in/)、ユーザーがSMSメッセージを受信する前に、オプトインの意思を明示的に確認することを要求することができる。これによって、SMSに関心を持ちそうなユーザー、またはSMSに関心を持っているユーザーに焦点を合わせることができる。
+[SMS double opt-in]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/sms_double_opt_in/) では、ユーザーが明示的にオプトインインインインテントを確認してからSMS を受信できるようにする必要があります。これによって、SMSに関心を持ちそうなユーザー、またはSMSに関心を持っているユーザーに焦点を合わせることができる。
 
 ### メールレポート用の推定実質開封率
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[推定実開封率は]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/email_reporting#estimated-real-open-rate)、Brazeが独自に作成した分析モデルを使用して、機械開封が存在しないかのようにキャンペーン独自の推定開封率を再構築する。Brazeは、各キャンペーンのクリックデータを使って、実際の人間がメッセージを開封した割合を推測する。これは、アップルのMPPを含む様々なマシン・オープニング・メカニズムを補正するものである。 
+[推定実開封率は]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/email_reporting#estimated-real-open-rate)、Brazeが独自に作成した分析モデルを使用して、機械開封が存在しないかのようにキャンペーン独自の推定開封率を再構築する。Brazeは、各キャンペーンのクリックデータを使って、実際の人間がメッセージを開封した割合を推測する。これにより、Apple の MPP を含むさまざまなマシン開封メカニズムが補われます。 
 
-### キャンバスのためのパーソナライズされた道
+### キャンバス用のパーソナライズされたパス
 
 {% multi_lang_include release_type.md release="ベータ" %}
 
@@ -54,15 +54,15 @@ Brazeは、ダッシュボードとRESTエンドポイント用のさまざま
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-一度に10個までのカスタム属性やイベントをブロックリストにできるようになった。詳細については、[カスタム・イベントと属性]({{site.baseurl}}/user_guide/administrative/app_settings/custom_event_and_attribute_management/)管理を参照のこと。
+一度に最大10個のカスタム属性またはイベントをブロックできるようになりました。詳細については、[カスタムイベントと属性管理]({{site.baseurl}}/user_guide/administrative/app_settings/custom_event_and_attribute_management/)を参照してください。
 
 ### 新しいヘルプ記事ユニバーサルリンクとアプリリンク
 
-アップルのユニバーサルリンクとアンドロイドのアプリリンクは、ウェブコンテンツとモバイルアプリの間のシームレスな移行を提供するために考案された仕組みである。ユニバーサル・リンクはiOSに特有のものだが、Androidアプリ・リンクはAndroidアプリでも同じ役割を果たす。 
+Apple ユニバーサルリンクと Android アプリリンクは、Web コンテンツとモバイルアプリ間のシームレスな移行を実現するために考案されたメカニズムです。ユニバーサル・リンクはiOSに特有のものだが、Androidアプリ・リンクはAndroidアプリでも同じ役割を果たす。 
 
-このトピックについては、[ユニバーサルリンクとアプリリンクの]({{site.baseurl}}/help/help_articles/email/universal_links/)記事で詳しく説明している。
+このトピックの詳細については、専用の[ユニバーサルリンクとアプリケーションリンク]({{site.baseurl}}/help/help_articles/email/universal_links/) の記事を参照してください。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
 ### Olo - チャンネル拡張
 
@@ -70,23 +70,23 @@ Brazeと[Oloの]({{site.baseurl}}/partners/message_orchestration/channel_extensi
 
 ### Typeform - 顧客データプラットフォーム
 
-Brazeと[Typeformの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/surveys/typeform/)統合により、Typeformのレスポンスから収集したデータでBrazeのユーザープロフィールを更新したり、ユーザーのTypeformへのエンゲージメントに基づいてBrazeのメッセージングをトリガーしたり、ユーザーのTypeformのレスポンスに基づいてBrazeのメッセージングをパーソナライズしたりすることができる。
+Braze と [Typeform]({{site.baseurl}}/partners/message_orchestration/channel_extensions/surveys/typeform/) の統合により、Typeform の応答から収集されたデータを使用して Braze のユーザープロファイルを更新したり、Typeform でのユーザーのエンゲージメントに基づいて Braze でメッセージングをトリガーしたり、ユーザーの Typeform 応答に基づいて Braze メッセージをパーソナライズしたりできるようになります。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Web SDK v4.10.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - [Web SDK v5.0.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - [Android SDK 29.0.1](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
 - [Swift SDK 7.1.0-7.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
-    - `Braze.Configuration.DeviceProperty.pushDisplayOptions` は非推奨となった。この値を与えても、もはや効果はない。
+    - `Braze.Configuration.DeviceProperty.pushDisplayOptions` は非推奨になりました。この値を与えても、もはや効果はない。
 - [React Native SDK 8.0.0-8.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
-    - ネイティブAndroidブリッジをBraze Android SDK 27.0.1から29.0.0に更新。
-    - ネイティブiOSブリッジをBraze Swift SDK 6.6.0から7.0.0に更新。
-    - `Banner` コンテンツカードのタイプをImageOnlyに変更する：
-        - `BannerContentCard` への `ImageOnlyContentCard`
-        - `ContentCardTypes.BANNER` への `ContentCardTypes.IMAGE_ONLY`
-    - Androidの場合、プロジェクト内のXMLファイルにコンテンツカードの`banner` という単語が含まれている場合、`image_only` に置き換える必要がある。
+    - ネイティブ Android ブリッジを Braze Android SDK 27.0.1から29.0.0に更新します。
+    - ネイティブ iOS ブリッジを Braze Swift SDK 6.6.0から7.0.0に更新します。
+    - `Banner` コンテンツカードタイプの名前を ImageOnly に変更します。
+        - `BannerContentCard` から `ImageOnlyContentCard`
+        - `ContentCardTypes.BANNER` から `ContentCardTypes.IMAGE_ONLY`
+    - Android では、プロジェクトの XML ファイルにコンテンツカードの単語 `banner` が含まれている場合、`image_only` に置き換える必要があります。
     - `Braze.getFeatureFlag(id)` は、featureフラグが存在しない場合、`null` を返すようになった。
-    - `Braze.Events.FEATURE_FLAGS_UPDATED` は、リフレッシュリクエストが成功または失敗で完了したとき、および現在のセッションから以前にキャッシュされたデータがあった場合は最初のサブスクリプションのときにのみトリガーする。
\ No newline at end of file
+    - `Braze.Events.FEATURE_FLAGS_UPDATED` は、更新リクエストが成功または失敗して完了したとき、および現在のセッションから過去にキャッシュされたデータがあった場合の初回のサブスクリプション時にのみトリガーされます。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2023/12_12_23.md b/_lang/ja/_help/release_notes/2023/12_12_23.md
index ef12f88688f..341f14b477d 100644
--- a/_lang/ja/_help/release_notes/2023/12_12_23.md
+++ b/_lang/ja/_help/release_notes/2023/12_12_23.md
@@ -3,30 +3,30 @@ nav_title: 2023年12月12日
 page_order: 0
 noindex: true
 page_type: update
-description: "この記事には12/12/23のリリースノートが含まれている。"
+description: "この記事には、2023年12月12日のリリースノートが含まれています。"
 ---
 
 # 2023年12月12日リリース
 
-## アンドロイド・プッシュ統合の更新
+## Androidプッシュインテグレーションのアップデート
 
-2023年6月20日、グーグルはAndroidアプリにプッシュ通知を送るためのCloud Messaging APIを廃止した。[標準のAndroidプッシュ統合では](https://www.braze.com/docs/developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration/)、代わりにGoogleのFirebase Cloud Messaging APIの設定方法が表示されるようになった。
+2023年6月20日、Google は Android アプリにプッシュ通知を送信する Cloud Messaging API を非推奨にしました。[Android の標準プッシュ統合](https://www.braze.com/docs/developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration/)では、代わりに Google の Firebase Cloud Messaging API をセットアップする方が示されるようになりました。
 
-GoogleのCloud Messaging APIの減価償却の詳細については、[Firebase FAQを](https://firebase.google.com/support/faq#fcm-23-deprecation)参照のこと。
+Google の Cloud Messaging API の非推奨化に関する詳細については、「[Firebase に関する FAQ](https://firebase.google.com/support/faq#fcm-23-deprecation)」を参照してください。
 
-## ロバスト・チャンネル
+## 強力なチャネル
 
-### WhatsApp レスポンスメッセージ
+### WhatsApp レスポンスメッセージング
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-キャンペーンやキャンバスで[WhatsAppメッセージを作成する]({{site.baseurl}}/whatsapp_response_messaging/)際、24時間以内にユーザーのWhatsAppメッセージに返信するレスポンスメッセージを作成できる。レスポンス・メッセージは、オプトイン・キャンペーンなど、ブランドとユーザーとのインタラクションを促進するキャンバスで特に役立つ。
+[WhatsAppメッセージ]({{site.baseurl}}/whatsapp_response_messaging/)をキャンペーンまたはキャンバスに作成すると、24時間枠内でユーザーのWhatsAppメッセージに返信するレスポンスメッセージを作成できます。レスポンスメッセージングは、オプトインキャンペーンなど、ブランドとユーザー間のやり取りを奨励するキャンバスで特に役立ちます。
 
 ### WhatsAppの周波数上限設定
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-WhatsAppで[回数制限ルールを]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)設定できるようになった。フリークエンシー・キャッピングは、キャンペーンまたはキャンバス・コンポーネントの送信レベルで適用され、**「設定**」＞「**フリークエンシー・キャッピング・ルール**」からワークスペースごとに設定できる。  
+WhatsAppで[回数制限ルールを]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)設定できるようになった。フリークエンシーキャップはキャンペーンまたはキャンバスコンポーネントの送信レベルで適用され、\[**設定**] > \[**フリークエンシーキャップルール**] から各ワークスペースに設定できます。  
 
 ## データの柔軟性
 
@@ -42,50 +42,50 @@ WhatsAppで[回数制限ルールを]({{site.baseurl}}/user_guide/engagement_too
 
 [メールパフォーマンスダッシュボード]({{site.baseurl}}/email_engagement_dashboard/)内に、メールインサイトという新しいタブがあり、2つの新しいレポートが含まれている：
 
-- **メールボックス・プロバイダーによる関与：**メールボックスプロバイダー別のクリック数と開封数を表示する。メールボックス・プロバイダを選択し、特定の受信ドメインをドリルダウンすることができる。
-- **曜日別エンゲージメント**ユーザーがいつメールに関与しているかを示す。
+- **メールボックスプロバイダーによるエンゲージメント:**メールボックスプロバイダー別のクリック数と開封数を表示する。メールボックスプロバイダーを選択し、特定の受信ドメインにドリルダウンできます。
+- **曜日別エンゲージメント**メールに対するユーザーのエンゲージメントが、何曜日に行われているのかを示します。
 
-### 購読グループの時系列グラフを更新する
+### サブスクリプショングループ時系列グラフへのアップデート
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-** サブスクリプション Group Timeseries** グラフで、** サブスクリプション Groups** ページでアプリが取得するグラフに、メールまたは電話番号ごとではなく、ユーザーごとのサブスクリプション数が表示されるようになりました。これは、Brazeがダッシュボードの他の領域で統計を計算する方法と、よりよく一致している。
+\[**購読グループ**] ページに表示される \[**購読グループの時系列**] グラフに、メールアドレスや電話番号ごとではなく、ユーザーごとの購読数が表示されるようになりました。これは、Braze でのダッシュボードの他の領域における統計の計算方法とより合致します。
 
 ## AIとMLの自動化
 
-### AIアイテムの推奨
+### AI によるアイテムのおすすめ
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[AIアイテム・レコメンデーションは]({{site.baseurl}}/ai_item_recommendations)、ディープラーニングに基づく商品レコメンデーションエンジンであり、ユーザーの購買行動の集合を利用して商品を推薦する。AIアイテム・レコメンデーションを使用して、最も人気のある商品を計算したり、特定のカタログ用にパーソナライズされたAIレコメンデーションを作成したりすることができる。レコメンデーションを作成したら、パーソナライゼーションを使用して、それらの商品をメッセージに挿入することができる。
+[AIアイテム推薦]({{site.baseurl}}/ai_item_recommendations)は、集合的なユーザー購買行動を用いてアイテムを推薦するディープラーニングベースの商品レコメンデーションエンジンです。AI によるアイテムのおすすめを使用して、最も人気のある製品を計算したり、特定のカタログに対してパーソナライズされた AI によるおすすめを作成したりできます。おすすめの作成後、パーソナライゼーションを使用してそれらの製品をメッセージに挿入できます。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
-### Zapierを使ったFacebookリード広告 - リード獲得
+### Zapier を介した Facebook リード広告 - リードキャプチャ
 
-[Zapierを介したFacebook Lead Adsの統合により]({{site.baseurl}}/partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier/)、FacebookからBrazeにリードをインポートし、リードが捕捉されたときにカスタムイベントを追跡することができる。
+[Zapier を介した Facebook Lead Ads]({{site.baseurl}}/partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier/) への統合により、Facebook から Braze にリードをインポートし、リードがキャプチャされたときにカスタムイベントを追跡することができます。
 
 ### SmarterSends - メッセージテンプレート
 
-Brazeと[SmarterSendsの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/smartersends/)パートナーシップにより、Brazeのパワーと分散したユーザーが所有するハイパーローカライズされたコンテンツを組み合わせることができ、マーケティングキャンペーンを向上させることができる。
+Braze と[SmarterSends]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/smartersends/) パートナーシップにより、Braze の能力と、分散ユーザーs が所有するハイパーローカライズされたコンテンツを組み合わせて、マーケティング キャンペーンs を向上させることができます。
 
-### Recurly - 支払い
+### Recurly – 決済
 
-[Recurlyと]({{site.baseurl}}/partners/data_and_infrastructure_agility/payments/recurly/)Brazeの統合は、Brazeとのサブスクリプション・データの共有プロセスを簡素化し、顧客との的を絞ったコミュニケーションを可能にする。
+[Recurly]({{site.baseurl}}/partners/data_and_infrastructure_agility/payments/recurly/) と Braze の統合により、Braze との購読データの共有プロセスが簡素化され、顧客とのターゲットを絞ったコミュニケーションが可能になります。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Flutter SDK 8.0.0-8.1.0](https://pub.dev/packages/braze_plugin/changelog)
-  - ネイティブAndroidブリッジをBraze Android SDK 27.0.1から29.0.1に更新。
-  - ネイティブiOSブリッジをBraze Swift SDK 6.6.1から7.2.0に更新。
+  - ネイティブ Android ブリッジを Braze Android SDK 27.0.1から29.0.1に更新します。
+  - ネイティブ iOS ブリッジを Braze Swift SDK 6.6.1から7.2.0に更新します。
   - Feature Flagsメソッドの動作を変更する。
     - `BrazePlugin.getFeatureFlagByID(String id)` は、featureフラグが存在しない場合、`null` を返すようになった。
-    - `BrazePlugin.subscribeToFeatureFlags(void Function(List<BrazeFeatureFlag>) onEvent))` は以下の状況でのみ発動する：
+    - `BrazePlugin.subscribeToFeatureFlags(void Function(List<BrazeFeatureFlag>) onEvent))` は以下の状況でのみトリガーされます。
       - リフレッシュ要求が成功または失敗で完了したとき。
       - 現在のセッションから以前にキャッシュされたデータがある場合、最初のサブスクリプション時に。
-  - Android SDKの最低サポートバージョンは21である。
+  - サポートされているAndroid SDK の最小バージョンは21です。
 - [React Native SDK 8.2.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.2.0/CHANGELOG.md)
 - [Swift SDK 7.3.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
 - [Braze Segment Swift プラグイン 2.2.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md)
diff --git a/_lang/ja/_help/release_notes/2023/1_10_23.md b/_lang/ja/_help/release_notes/2023/1_10_23.md
index ee3904dd8f0..4c28a7ed953 100644
--- a/_lang/ja/_help/release_notes/2023/1_10_23.md
+++ b/_lang/ja/_help/release_notes/2023/1_10_23.md
@@ -8,9 +8,9 @@ description: "この記事には2023年1月10日のリリースノートが含
 
 # 2023年1月10日リリース
 
-## キャンバスフローのユーザー更新コンポーネント
+## キャンバスフローのユーザ更新コンポーネント
 
-[ユーザー更新]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/user_update/)コンポーネントを使用すると、ユーザーの属性、イベント、および購入をJSONコンポーザーで更新できるため、APIキーのような機密情報を含める必要はありません。 
+[ユーザー 更新]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/user_update/) コンポーネントを使用すると、JSON コンポーザーでユーザーの属性、イベント、および購入を更新できるため、API キーなどの機密情報を含める必要はありません。 
 
 ## APIを介して設定サブスクリプショングループ
 
@@ -18,22 +18,22 @@ description: "この記事には2023年1月10日のリリースノートが含
 
 ## コンバージョンダッシュボード早期アクセス
 
-[コンバージョンダッシュボード]({{site.baseurl}}/user_guide/data_and_analytics/analytics/conversions_dashboard/)では、さまざまなアトリビューション方法を使用して、キャンペーン、キャンバス、およびチャネル全体のコンバージョンを分析できます。これらのアトリビューション方法を特定的に追跡できます:
+[コンバージョンダッシュボード]({{site.baseurl}}/user_guide/data_and_analytics/analytics/conversions_dashboard/)では、さまざまなアトリビューション方法を使用して、キャンペーン、キャンバス、およびチャネル全体のコンバージョンを分析できます。具体的には、次のアトリビューション方法を追跡できます。
 
-- **開封変換:**ユーザーがメッセージを開いた後に発生したコンバージョン
-- **クリックコンバージョン:**ユーザーがメッセージをクリックした後に発生したコンバージョン
-- **受信した変換:**ユーザーがメッセージを受信した後に発生した変換
-- **ラストクリックコンバージョン:**ユーザーがメッセージをクリックした後に発生したコンバージョン（メッセージがユーザーが最後にクリックしたものであった場合）（この機能は現在、早期アクセス顧客の一部でテストされています）
+- **オープンコンバージョンs:**ユーザーがメッセージを開いた後に発生したコンバージョン
+- **コンバージョン s:**ユーザーがメッセージをクリックした後に発生したコンバージョン
+- **受信コンバージョンs:**ユーザーがメッセージを受信した後に発生した変換
+- **ラストクリックコンバージョンs:**ユーザーがメッセージをクリックした後に発生したコンバージョン（メッセージがユーザーが最後にクリックしたものであった場合）（この機能は現在、早期アクセス顧客の一部でテストされています）
 
-この機能は現在早期アクセス段階です。早期アクセスに参加することに興味がある場合は、顧客成功マネージャーに連絡してください。
+この機能は現在早期アクセス段階です。早期参入に興味がある場合は、顧客のサクセスマネージャーに手を伸ばしてください。
 
-## Braze Currentsのキャンバス終了イベント
+## Braze Currentsのキャンバス出口イベント
 
-ユーザーがイベントを実行するか、オーディエンスに一致することによって、キャンバスを退出するタイミングを追跡できるようになりました。Currentsイベント用語集の[メッセージエンゲージメントイベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)セクションをご覧ください。
+ユーザーがキャンバスを終了したときに、イベントを実行するか、オーディエンスを一致させることで追跡できるようになりました。Currentsイベント用語集の[メッセージエンゲージメントイベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)セクションをご覧ください。
 
 ## SDKの更新
 
-次のSDKアップデートがリリースされました。以下に重大な更新が記載されています。それ以外の更新については、対応するSDKの変更ログを確認してください。
+次のSDKアップデートがリリースされました。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Web SDK 4.5.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - [AppboyKit iOS SDK 4.5.2](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.5.2)
@@ -41,7 +41,7 @@ description: "この記事には2023年1月10日のリリースノートが含
 	- 同じ名前のモジュールを隠さないように、`BrazeLocation`クラスの名前を`BrazeLocationProvider`に変更します。
 - [Flutter SDK 3.0.1](https://pub.dev/packages/braze_plugin/changelog)
 - [Android SDK 24.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
-	- 位置情報およびジオフェンス機能は、新しいモジュール`com.braze:android-sdk-location`に移動しました。
+	- 場所とジオフェンスの機能は、`com.braze:android-sdk-location` という新しいモジュールに移動しました。
 	- AppboyのクラスとファイルはBrazeに一括移動されました。
 	- コンテンツカードを並べ替えるときに、`DefaultContentCardsUpdateHandler`のデフォルトの動作を最終更新時刻ではなく作成時刻を使用するように変更しました。
-	- 削除されました BrazeUser.setFacebookData() と BrazeUser.setTwitterData()。
+	- BrazeUser.setFacebookData(およびBrazeUser.setTwitterData() が削除されました。
diff --git a/_lang/ja/_help/release_notes/2023/2_7_23.md b/_lang/ja/_help/release_notes/2023/2_7_23.md
index 8abf9607aa1..eac33446418 100644
--- a/_lang/ja/_help/release_notes/2023/2_7_23.md
+++ b/_lang/ja/_help/release_notes/2023/2_7_23.md
@@ -10,22 +10,22 @@ description: "この記事には、2023年2月7日のリリースノートが含
 
 ## アクセシブルなメッセージの構築
 
-たとえ意図的でなくとも、障害者を排除したマーケティング・コンテンツは、何百万人もの人々があなたのブランドと交流することを妨げる可能性がある。マーケティングにおけるアクセシビリティとは、誰もが簡単にあなたのマーケティングを体験し、あなたのコミュニケーションを受け取り、理解し、あなたの製品やサービス、ブランドに投資したりファンになったりする機会を持てるようにすることである。[Brazeでアクセシブルなメッセージを作る]({{site.baseurl}}/help/accessibility#building-accessible-messages-in-braze)」を参照。
+障がい者を排除したマーケティング・コンテンツは、意図せずにさえも、何百万人もの人々があなたのブランドと交流することを防ぐことができる。マーケティングのアクセシビリティとは、誰もがあなたのマーケティングを体験し、あなたのコミュニケーションを受け、理解し、あなたの商品、サービス、ブランドに投資したり、ファンになったりするチャンスを手に入れることを容易にすることです。ガイダンスについては、[Braze]({{site.baseurl}}/help/accessibility#building-accessible-messages-in-braze)でアクセス可能なメッセージの構築を参照してください。
 
 ## クエリー・ビルダー早期アクセス
 
-[クエリビルダーを]({{site.baseurl}}/user_guide/data_and_analytics/query_builder#query-builder
-)使えば、SnowflakeでBrazeのデータを使ってレポートを作成できる。クエリ・ビルダーには、SQLクエリのテンプレートがあらかじめ用意されている。現在のところ、テンプレート化されたクエリーだけが許可されている。カスタムSQLクエリーのサポートは追って行われる。
+[query builder]({{site.baseurl}}/user_guide/data_and_analytics/query_builder#query-builder
+) を使用すると、Snowflake でBraze を使用してレポートs を生成できます。Query Builder には、使用を開始するためのSQL クエリテンプレートs が事前に構築されています。現在のところ、テンプレート化されたクエリーだけが許可されている。カスタムSQLクエリーのサポートは追って行われる。
 
-この機能は現在早期アクセス段階です。早期アクセスへの参加に興味がある方は、カスタマー・サクセス・マネージャーまでご連絡を。
+この機能は現在早期アクセス段階です。早期参入に興味がある場合は、顧客のサクセスマネージャーに手を伸ばしてください。
 
 ## 機能フラッグ・ベータ版
 
-[機能フラグにより]({{site.baseurl}}/developer_guide/platform_wide/feature_flags)、選択したユーザーに対してリモートで機能を有効または無効にすることができる。追加コードのデプロイやアプリストアのアップデートをすることなく、本番環境で機能のオン／オフを切り替えることができる。これにより、安心して新機能を展開することができる。
+[機能フラグ]({{site.baseurl}}/developer_guide/platform_wide/feature_flags)を使用すると、選択したユーザーの機能をリモートで有効または無効にすることができます。追加コードのデプロイやアプリストアのアップデートをすることなく、本番環境で機能のオン／オフを切り替えることができる。これにより、自信を持って新しい機能を安全に展開することができます。
 
-この機能は現在ベータ版である。ベータ版への参加に興味がある方は、カスタマー・サクセス・マネージャーまでご連絡を。
+この機能は現在ベータ版である。ベータへの参加に興味がある場合は、顧客のサクセスマネージャーに手を伸ばしてください。
 
-## 百花繚乱のイベント
+## 新しいCurrents行事
 
 以下のCurrentsイベントが最近リリースされ、[メッセージ・エンゲージメント・イベントと]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events) [顧客行動・ユーザー・イベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events)用語集に追加された：
 
@@ -52,39 +52,39 @@ SMSショートリンククリックイベント：
 
 ## パーソナライズされたバリアント
 
-A/Bテストを送信する際、ユーザーにパーソナライズド・バリアントを送信し、最もエンゲージしやすいバリアントを送信することができる。パーソナライズド・バリアントがどのように選択され、キャンペーンでどのように活用するかについては、[多変量解析を]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/multivariate_analytics/#personalized-variant)参照のこと。 
+A/B テストを送信するときは、ユーザー にパーソナライズされたバリアントを送信し、エンゲージする可能性が最も高いバリアントを送信できます。パーソナライズされたバリアントの選択方法と、それらをキャンペーンsで活用する方法については、[多変量分析]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/multivariate_analytics/#personalized-variant)を参照してください。 
 
 ## SQLセグメント拡張の早期アクセス
 
-[Segment Extensionsを]({{site.baseurl}}/sql_segments/)使用すると、SnowflakeデータのSnowflake SQLクエリを使用してSegment Extensionを生成できる。SQL では、他のセグメンテーション機能では実現できない方法でデータ間の関係を柔軟に記述できるため、新しいセグメントのユースケースを開拓するのに役立ちます。
+[Segment Extensions]({{site.baseurl}}/sql_segments/)を使用すると、SnowflakeのSQLクエリーを使用してセグメント拡張を生成できます。SQL では、他のセグメンテーション機能では実現できない方法でデータ間の関係を柔軟に記述できるため、新しいセグメントのユースケースを開拓するのに役立ちます。
 
-## キャンバス立ち上げ前後のチェックリスト
+## キャンバスの起動前と起動後のチェックリスト
 
-キャンバスを立ち上げる前と後には、チェックすべきいくつかの詳細がある：
-- メッセージングと送信時間を視聴者の好みに合わせる。
+キャンバスを起動する前と後に、次のような詳細情報を確認する必要があります。
+- メッセージングと送信時間がオーディエンスの環境設定と一致することを確認します
 - タイムゾーンやエントリー設定などのバリエーションを考慮する
-- これらのシナリオに基づき、ローンチ後にキャンバスに不一致が生じた場合、キャンバスを見直し、調整する。
+- これらのシナリオに基づいて起動後に不一致が発生した場合は、キャンバスを確認して調整します
 
-この[チェックリストは]({{site.baseurl}}/user_guide/engagement_tools/canvas/ideas_and_strategies/pre_post_launch_checklist#pre-and-post-launch-checklist)、キャンバスの成功に貢献するために、あなたのユースケースに基づいてこれらの領域を微調整するためのガイドとして使用する。 
+この[チェックリスト]({{site.baseurl}}/user_guide/engagement_tools/canvas/ideas_and_strategies/pre_post_launch_checklist#pre-and-post-launch-checklist)を使用して、ユースケースに基づいてこれらの領域を微調整し、キャンバスの成功に役立ててください。 
 
 ## 新しいAPIエンドポイント：ユーザーエイリアスを更新する
 
-既存のユーザーエイリアスを更新するには、[ユーザーエイリアスの更新エンドポイントを]({{site.baseurl}}/api/endpoints/user_data/post_users_alias_update/)使用する。
+存在するユーザー別名を更新するには、[更新 ユーザー別名エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_users_alias_update/)を使用します。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Web SDK 4.6.0-4.6.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#461)
 - [Android SDK 24.1.0-24.2.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2420)
 - [AppboyKit iOS SDK 4.5.3](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.5.3)
 - [Swift SDK 5.9.0-5.9.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#591)
 	- デプロイメントの最小ターゲットをiOS 11.0とtvOS 11.0に引き上げる。
-	- Xcode のバージョンを 14.1 (14B47b) に上げる。
+	- Xコード バージョンを14.1 (14B47b) に上げます。
 - [Flutter SDK 3.1.0](https://pub.dev/packages/braze_plugin/changelog)
-	- ネイティブAndroidブリッジは、Braze Android SDK 24.2.0を使用している。
-	- ネイティブiOSブリッジは、Braze iOS SDK 5.9.0を使用している。
-	- iOSの最小導入目標は11.0だ。
+	- 本来のAndroidブリッジはBraze Android SDK 24.2.0を使用します。
+	- ネイティブiOSブリッジは、Braze iOS SDK 5.9.0を使用します。
+	- iOS のデプロイメントターゲットの最小値は11.0 です。
 - [Cordova SDK 2.33.0](https://github.com/Appboy/appboy-cordova-sdk/blob/2.33.0/CHANGELOG.md#2330)
 	- 新しいBraze Swift SDK (5.8.1)を使用するようにiOSプラグインを移行した。
 	- ニュースフィードUIはiOSではサポートされなくなった。
diff --git a/_lang/ja/_help/release_notes/2023/3_7_23.md b/_lang/ja/_help/release_notes/2023/3_7_23.md
index 5f3b89919fc..88999741f46 100644
--- a/_lang/ja/_help/release_notes/2023/3_7_23.md
+++ b/_lang/ja/_help/release_notes/2023/3_7_23.md
@@ -8,13 +8,13 @@ description: "この記事には2023年3月7日のリリースノートが含ま
 
 # 2023年3月7日リリース
 
-## 元のエクスペリエンスキャンバスの複製サポートを削除
+## 従来のエクスペリエンスのキャンバス複製に対するサポートの中止
 
 2023 年 2 月 28 日以降、従来のキャンバスエクスペリエンスを使用したキャンバスの作成や複製ができなくなりました。Braze では、従来のキャンバスエクスペリエンスを使用しているお客様に、キャンバスフローへの移行をお勧めしています。これは、キャンバスの構築と管理をより良く行う目的で改良された編集エクスペリエンスです。「[キャンバスからキャンバスフローへの複製]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases/)」を参照してください。
 
 ## iOSのライブアクティビティ（早期アクセス）
 
-[ライブアクティビティ]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/)はロック画面に表示される持続的でインタラクティブな通知で、リアルタイムで物事を監視することができます。ロック画面に表示されるため、ライブアクティビティは通知を見逃さないようにします。それらは持続的であるため、ユーザーが電話のロックを解除しなくても最新のコンテンツを表示できます。
+[ライブアクティビティ]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/)はロック画面に表示される持続的でインタラクティブな通知で、リアルタイムで物事を監視することができます。ライブアクティビティはロック画面に表示されるため、通知が見逃されないようにすることができます。それらは持続的であるため、ユーザーが電話のロックを解除しなくても最新のコンテンツを表示できます。
 
 ## コンテンツカードのカード作成
 
@@ -22,8 +22,8 @@ Brazeがオーディエンスの適格性とパーソナライゼーションを
 
 利用可能なオプションは次のとおりです:
 
-- **キャンペーン開始時:**コンテンツカードの以前のデフォルトの動作。Brazeはキャンペーンが開始されるときにオーディエンスの適格性とパーソナライゼーションを計算し、次にカードを作成してユーザーがアプリを開くまでそれを保存します。
-- **最初のインプレッションで:**ユーザーが次にアプリを開いたとき（つまり、新しいセッションを開始したとき）、Brazeはユーザーが利用できるコンテンツカードを決定し、Liquidやコネクテッドコンテンツのようなパーソナライゼーションをテンプレート化し、カードを作成します。
+- **キャンペーン開始時:** コンテンツカードの以前のデフォルトの動作。Brazeはキャンペーンが開始されるときにオーディエンスの適格性とパーソナライゼーションを計算し、次にカードを作成してユーザーがアプリを開くまでそれを保存します。
+- **最初のインプレッション発生時:** ユーザーが次にアプリを開いたとき（つまり、新しいセッションを開始したとき）、Brazeはユーザーが利用できるコンテンツカードを決定し、Liquidやコネクテッドコンテンツのようなパーソナライゼーションをテンプレート化し、カードを作成します。
 
 詳細については、[カード作成]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/)を参照してください。
 
@@ -37,13 +37,13 @@ Brazeがオーディエンスの適格性とパーソナライゼーションを
 
 ## SafariモバイルWebプッシュ
 
-Safari v16.4 はモバイル Web プッシュをサポートしており、これにより iOS および iPadOS でプッシュ通知を使用してモバイルユーザーと再エンゲージすることができます。iOSおよびiPadOSのSafariで[Webプッシュをサポートする方法については、専用ガイドをご覧ください]({{site.baseurl}}/developer_guide/platform_integration_guides/web/push_notifications/safari_mobile_push/)。
+Safari v16.4 はモバイル Web プッシュに対応しており、iOS と iPadOS のプッシュ通知でモバイルユーザーを再度エンゲージできるようになりました。iOSおよびiPadOSのSafariで[Webプッシュをサポートする方法については、専用ガイドをご覧ください]({{site.baseurl}}/developer_guide/platform_integration_guides/web/push_notifications/safari_mobile_push/)。
 
-## ユーザー更新コンポーネント使用例
+## ユーザー更新コンポーネントのユースケース
 
-キャンバスのユーザー更新コンポーネントを使用すると、JSONコンポーザーでユーザーの属性、イベント、および購入を更新できますが、この機能を最大限に活用する方法がわからない場合がありますか？私たちは、いくつかのアイデアを提供するために[3つの例を追加しました]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/user_update/#use-cases)。
+キャンバスのユーザー更新コンポーネントを使用すると、JSON コンポーザーでユーザーの属性、イベント、購入を更新できますが、この機能を最大限に活用する方法がよくわからないのではないでしょうか。私たちは、いくつかのアイデアを提供するために[3つの例を追加しました]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/user_update/#use-cases)。
 
-## ユーザー lookup
+## ユーザルックアップ
 
 この新しい記事では、[ユーザー検索]({{site.baseurl}}/user_guide/engagement_tools/segments/user_lookup)を使用して、コンポーザーから直接特定のユーザーを検索し、フィルターとセグメントが正しく設定されているかどうかをテストする方法について説明します。これは、キャンペーンやキャンバスが期待通りに送信されていない場合のトラブルシューティングにも役立ちます。たとえば、ユーザーが受信すべきメッセージを受信していない場合などです。
 
@@ -55,17 +55,17 @@ Safari v16.4 はモバイル Web プッシュをサポートしており、こ
 
 ## ブロックリストまたはカスタムデータの削除
 
-この記事では、カスタムデータオブジェクトを[ブロックリストまたは削除する]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/blocklist_delete_custom_data/)方法について説明します。
+この新しい記事では、[ブロックリストによるカスタムデータオブジェクトのリタイア方法、またはカスタムデータ]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/blocklist_delete_custom_data/)の削除方法について説明します。
 
-カスタム属性、カスタムイベント、または購入イベントが、データポイントを過剰に消費している、マーケティング戦略に役立たない、またはエラーで記録されたことを特定することがあります。開発チームがアプリや Web サイトのバックエンドからこのデータを削除する作業をしている間、このデータが Braze に送信されないようにするために、カスタムデータオブジェクトを禁止リストに入れておくことができます。
+たまに、カスタム属性、カスタムイベント、購入イベントについて、データポイントの消費量が多いもの、マーケティング戦略に不要になったもの、または誤って記録されたものが見つかることがあります。開発チームがアプリや Web サイトのバックエンドからこのデータを削除する作業をしている間、このデータが Braze に送信されないようにするために、カスタムデータオブジェクトを禁止リストに入れておくことができます。
 
 ## 新しいBrazeのパートナーシップ
 
 ### Sisu Data - ビジネスインテリジェンス
 
-[Sisu Data]({{site.baseurl}}/partners/data_and_infrastructure_agility/business_intelligence/sisu_data/)とBrazeの統合により、すべてのキャンペーンまたはキャンペーンレベルで、メトリクス（例えば、開封率、クリックスルー率、コンバージョン率など）が変化する理由と、最も最適な結果を導く要因を理解することができます。これらのセグメントが特定されると、Brazeユーザーはデータウェアハウスで出力を具体化するか、Sisuから直接Brazeに送信してユーザーをリターゲティングおよび再エンゲージすることができます。
+[Sisu Data]({{site.baseurl}}/partners/data_and_infrastructure_agility/business_intelligence/sisu_data/)とBrazeの統合により、すべてのキャンペーンまたはキャンペーンレベルで、メトリクス（例えば、開封率、クリックスルー率、コンバージョン率など）が変化する理由と、最も最適な結果を導く要因を理解することができます。これらのセグメントが識別されると、Braze ユーザーはデータウェアハウスで出力を具体化したり、Sisu から Braze に直接送信し、ユーザーのリターゲティングおよび再エンゲージメントを実行したりできます。
 
-### Loplat - 文脈に応じた場所
+### Loplat - 状況に即したロケーション
 
 Brazeと[loplat]({{site.baseurl}}/partners/message_personalization/location/loplat/)の統合により、loplatの位置情報サービス（店舗POIおよびカスタムジオフェンス）を使用して、ジオ文脈に応じたマーケティングキャンペーンをトリガーし、オフラインセグメンテーションを使用してカスタムイベントを作成できます。ユーザーがloplat Xで設定したターゲットロケーションを訪れると、キャンペーンおよびロケーション情報が即座にBrazeに送信されます。
 
@@ -74,7 +74,7 @@ Brazeと[loplat]({{site.baseurl}}/partners/message_personalization/location/lopl
 Brazeと[ActionIQ]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/actioniq/)の統合により、ブランドはActionIQデータを直接Brazeに同期およびマッピングでき、顧客データ全体に基づいた卓越した顧客体験の提供を可能にします。統合により、ユーザーは次のことができるようになります:
 
 - ActionIQからBrazeにオーディエンスセグメントまたはカスタム属性を直接マッピングする
-- ActionIQ によってトラッキングされたイベントを Braze にリアルタイムで転送して、パーソナライズされたターゲットキャンペーンをトリガーします。
+- ActionIQによって追跡された事象をBrazeにリアルタイムでトリガー パーソナライズされたおよびターゲットキャンペーンに転送する
 
 ### Komo - ダイナミックなコンテンツ
 
@@ -82,24 +82,24 @@ Brazeと[Komo]({{site.baseurl}}/partners/message_personalization/dynamic_content
 
 - KomoからBrazeにリアルタイムで収集されたファーストパーティおよびゼロパーティのユーザーデータを取り込む
 - アンケート、投票、およびクイズの質問に回答する際に、市場調査およびユーザーの好みのデータを取り込む
-- ユーザーが引き続き関与し、自分自身に関するデータをより多く共有するにつれて、Brazeでユーザープロファイルを段階的に構築します。
+- ユーザーが継続的に関与し、自らに関する情報をより多く共有するにつれ、Brazeにおけるユーザープロファイルを徐々に構築する
 - Brazeを通じて送信されるトランザクションメールの外観と感触を標準化する
 
-### フレーズ - ローカライゼーション
+### Phrase - ローカライゼーション
 
-[Phrase]({{site.baseurl}}/partners/message_personalization/localization/phrase/) とBraze の統合により、Braze インターフェイスを離れることなくメールテンプレートとコンテンツブロックを翻訳できます。BrazeのPhrase TMS統合により、カスタマーエンゲージメントを高め、シームレスなローカライゼーションで新しい市場への成長を促進できます。
+[Phrase]({{site.baseurl}}/partners/message_personalization/localization/phrase/) と Braze の統合により、Braze インターフェイスを離れることなく、メールテンプレートとコンテンツブロックを翻訳できます。Braze 向け Phrase TMS 統合により、シームレスなローカライゼーションでカスタマーエンゲージメントを高め、新しい市場への拡大を促進できます。
 
 ### Nift - ロイヤルティ
 
-Brazeと[Nift]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/nift/)の統合により、カスタマーライフサイクルの重要な瞬間にNiftギフトを含む「感謝」を自動的にトリガーし、ギフトを使用した顧客を特定できます。Niftギフトカードは、Niftのマッチメイキング技術を利用して、コスト効率よく大規模に新規顧客を獲得するブランドが提供する製品やサービスにアクセスするために使用できます。
+Brazeと[Nift]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/nift/)の統合により、カスタマーライフサイクルの重要な瞬間にNiftギフトを含む「感謝」を自動的にトリガーし、ギフトを使用した顧客を特定できます。Nift ギフトカードは、Nift のマッチメイキング技術を利用して、費用対効果の高い大規模で新規顧客を獲得するブランドが提供する製品やサービスにアクセスするために使用できます。
 
 ### Sageflo - メッセージテンプレート
 
-Brazeと[Sageflo]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/sageflo/)の統合により、ローカルチームはマーケティング承認済みのテンプレート、画像、およびオーディエンスセグメントを使用して、API統合を通じて独自のメールを簡単に送信できるようになります。
+Braze と [Sageflo]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/sageflo/) の統合により、ローカルチームは、Braze との API 統合を通じ、マーケティング承認済みのテンプレート、画像、オーディエンスセグメントを使用して独自のメールを簡単に送信できるようになります。
 
 ### Airbyte - ワークフローオートメーション
 
-Brazeと[Airbyte]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/airbyte/)の統合により、すべてのアプリケーションとデータベースを中央のウェアハウスに接続することで、Brazeデータを収集および分析するためのデータパイプラインを作成できます。データが中央倉庫に収集されると、データチームは好みのビジネスインテリジェンスツールを使用してBrazeデータを効果的に探索できます。
+Braze と [Airbyte]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/airbyte/) の統合により、ユーザーはすべてのアプリケーションとデータベースを中央のウェアハウスに接続して、Braze データを収集および分析するためのデータパイプラインを作成できます。中央倉庫でデータが収集されると、データチームは好みのビジネスインテリジェンス手段を使用してBrazeデータを効率的に探索できます。
 
 ### GrowthLoop - ワークフローオートメーション
 
@@ -117,7 +117,7 @@ Brazeと[Mozart Data]({{site.baseurl}}/partners/data_and_infrastructure_agility/
 
 ## SDKの更新
 
-以下のSDKアップデートがリリースされました。以下に重大な更新が記載されています。他のすべての更新は、対応するSDKの変更履歴を確認してください。
+以下のSDKアップデートがリリースされました。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Swift SDK 5.10.0-5.11.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
 - [Web SDK 4.6.2-4.6.3](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
diff --git a/_lang/ja/_help/release_notes/2023/4_4_23.md b/_lang/ja/_help/release_notes/2023/4_4_23.md
index 5ea5d135de6..7178c46c562 100644
--- a/_lang/ja/_help/release_notes/2023/4_4_23.md
+++ b/_lang/ja/_help/release_notes/2023/4_4_23.md
@@ -9,7 +9,7 @@ description: "この記事には、2023年4月4日のリリースノートが含
 # 2023年4月4日リリース
 
 ## ドキュメントのパンくず 
-Braze Docsのサイトでは、各記事の上部にパンくずが表示されるようになった。これらは、ナビゲーションを手助けする別のオプションに過ぎない！
+Braze・ドックスのサイトでは、それぞれのアーティクルの上部にパンくずがあり、サイトのどこにいるのかを見せることができます。これらは、ナビゲーションを支援するもう1つのオプションです。
 
 ![ユーザーガイド > チャネル別メッセージ作成 > アプリ内メッセージ > テンプレート > 簡易アンケートから移動する一連のパンくず][1]{: style="max-width:55%"}
 
@@ -17,30 +17,30 @@ Braze Docsのサイトでは、各記事の上部にパンくずが表示され
 Liquidを通してBrazeのキャンペーンで非ユーザーデータを参照するためにカタログを使うことができる。Brazeでは、CSVをインポートする代わりに、ブラウザで直接カタログを作成できるようになった。詳しくは「[カタログの作成]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog)」を参照のこと。
 
 ## クエリビルダーのカスタムSQL
-クエリビルダーを使えば、SnowflakeでBrazeのデータを使ってレポートを作成できる。[カスタムSQLを使って]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/custom_sql)新たな洞察を引き出すことができる。
+クエリビルダーを使えば、SnowflakeでBrazeのデータを使ってレポートを作成できる。これで、[カスタム SQL を使用]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/custom_sql)して新しいインサイトを引き出すことができます。
 
 {% alert important %}
-SQLエディターは早期アクセス中だ。早期アクセスへの参加に興味がある方は、カスタマー・サクセス・マネージャーまでご連絡を。
+SQLエディターは早期アクセス中だ。早期アクセスへの参加に興味がある場合は、カスタマーサクセスマネージャーにお問い合わせください。
 {% endalert %}
 
-## 特集フラッグFAQ
-[機能フラッグに関するよくある質問に答えて]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/faq)みた。
+## 機能フラグFAQ
+いくつかの[フィーチャーフラグs]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/faq)のよくある質問に答えました。
 
-## 百花繚乱のメッセージ・エキストラ・リキッドタグ
-[`message_extras` Liquidタグを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras)使えば、送信イベントにConnected Contentのダイナミック・データ、カスタム属性（言語、国など）、Canvasエントリー・プロパティをアノテーションすることができる。このLiquidタグは、Currentsの対応する送信イベントにキーと値のペアを追加する。
+## Currents のメッセージエクストラ・Liquid・タグ
+[`message_extras`Liquid タグ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras)を使用すると、Connected Content からのダイナミックなデータ、カスタム属性 (言語、国など)、およびキャンバスエントリのプロパティを使用して、送信イベントに注釈を付けることができます。この Liquid タグにより、Currents 内の対応する送信イベントにキーと値のペアが追加されます。
 
 {% alert important %}
 このLiquidタグは現在、Eメール、SMS、プッシュ送信イベントのためのベータ版である。ベータ版への参加に興味がある場合は、Brazeカスタマー・サクセス・マネージャーに連絡すること。
 {% endalert %}
 
 ## 百花繚乱イベント：users_campaigns_abortとusers_canvas_abort
-百花繚乱の用語集に2つの新しいイベントが追加された：[キャンバス中止メッセージイベントと]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events#canvas-abort-message-events) [キャンペーン中止メッセージイベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events#campaign-abort-message-events)。
+Currents の用語集に2つの新しいイベントが追加されました。[キャンバス中止メッセージイベントと]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events#canvas-abort-message-events) [キャンペーン中止メッセージイベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events#campaign-abort-message-events)。
 
 ## 新しいAPIエンドポイント：カタログ
 カタログ内のアイテムまたは複数のアイテムを更新するには、[Update catalog item]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item/)および[Update catalog items]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items/)エンドポイントを使用する。
 
-## Shopifyヒストリカル・バックフィル
-[Shopifyヒストリカル・バックフィルにより](https://www.braze.com/docs/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_backfill/)、Brazeは、Shopify統合接続前の過去90日間のすべての顧客、注文、購入イベントをインポートすることができる。
+## Shopify 履歴バックフィル
+[Shopify 履歴バックフィル](https://www.braze.com/docs/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_backfill/)を使用すると、Braze で Shopify 統合接続前の過去 90 日間のすべての顧客、注文、購入イベントをインポートできます。
 
 ## WhatsApp
 WhatsAppは世界中で利用されている人気のピアツーピアメッセージングプラットフォームで、会話ベースのメッセージングをビジネス向けに提供している。[WhatsAppメッセージングチャンネルは]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp)、キャンペーン、オプトイン/オプトアウト、クイック返信などを通じて、WhatsAppプラットフォーム上のユーザーに直接エンゲージする方法を提供する。
@@ -48,14 +48,14 @@ WhatsAppは世界中で利用されている人気のピアツーピアメッセ
 ### WhatsApp API オブジェクト
 BrazeのWhatsAppサポートの一環として、`whats_app` オブジェクトを使用すると、[メッセージングエンドポイント]({{site.baseurl}}/api/endpoints/messaging)経由でWhatsAppメッセージを変更または作成できる。完全な仕様については、[`whats_app` オブジェクトのドキュメントを]({{site.baseurl}}/api/objects_filters/messaging/whats_app_object)参照のこと。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
-### メルクーリ - 分析
-Brazeと[Merkuryの]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/merkury)統合により、`MerkuryID` 、Brazeの顧客のサイト訪問者の認識率を高めることができる。
+### Merkury - 分析
+Brazeと[Merkury]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/merkury)統合により、`MerkuryID`を活用して、Braze 顧客sのサイト訪問者認識率を向上させることができます。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Cordova SDK 3.0.0](https://github.com/Appboy/appboy-cordova-sdk/blob/3.0.0/CHANGELOG.md)
 - [Swift SDK 5.11.1-5.13.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
diff --git a/_lang/ja/_help/release_notes/2023/5_2_23.md b/_lang/ja/_help/release_notes/2023/5_2_23.md
index b8ea421ce21..4829bfd1327 100644
--- a/_lang/ja/_help/release_notes/2023/5_2_23.md
+++ b/_lang/ja/_help/release_notes/2023/5_2_23.md
@@ -8,11 +8,11 @@ description: "この記事には2023年5月2日のリリースノートが含ま
 
 # 2023年5月2日リリース
 
-## 再設計されたBraze UI/UX
+## Braze UI/UX の再設計
 
-_2023年5月16日に一般公開_
+_2023年5月16日より一般発売_
 
-新しく再設計されたUI/UXと情報アーキテクチャで、時間を節約し、必要なものを正確に見つけましょう。プラットフォーム全体を迅速にナビゲートし、タスクを完了し、新機能を簡単に発見してください。この移行をあなたとあなたのチームにとってより簡単にするために、何が変わったのか、次に何を期待できるのかを学ぶための専用の[ナビゲーションガイド]({{site.baseurl}}/navigation)をご覧ください。
+新しく再設計されたUI/UXと情報アーキテクチャで、時間を節約し、必要なものを正確に見つけましょう。プラットフォーム内をすばやく移動し、タスクを完了し、新しい機能を簡単に発見できます。この移行をあなたとあなたのチームにとってより簡単にするために、何が変わったのか、次に何を期待できるのかを学ぶための専用の[ナビゲーションガイド]({{site.baseurl}}/navigation)をご覧ください。
 
 ## クエリビルダー
 
@@ -20,18 +20,18 @@ _2023年5月16日に一般公開_
 
 ## キャンバスのバージョン履歴
 
-[バージョン履歴]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/canvas_version_history/)を使用すると、キャンバスの分析およびユーザーのジャーニーを以前のバージョンのキャンバスで表示およびアクセスできます。キャンバスのバージョン履歴を参照することは、キャンバスの変化を記録しておくのに特に役立ちます。
+[バージョン履歴]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/canvas_version_history/)を使用すると、以前のバージョンのキャンバスの分析とユーザージャーニーを表示してアクセスできます。キャンバスのバージョン履歴を参照することは、キャンバスの変化を記録しておくのに特に役立ちます。
 
 ## SQLセグメントの増分リフレッシュ
 
-これで、インクリメンタルリフレッシュを使用する[SQLセグメントエクステンション]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/)を作成できるようになり、過去2日分のデータのみがリフレッシュされます。これはよりコスト効率が高く、セグメントメンバーシップが更新されるたびに使用するSQL Segmentクレジットが少なくて済みます。完全なリフレッシュ拡張とは異なり、増分リフレッシュ拡張を設定してメンバーシップを毎日自動的に再生成することができます。
+これで、インクリメンタルリフレッシュを使用する[SQLセグメントエクステンション]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/)を作成できるようになり、過去2日分のデータのみがリフレッシュされます。これによってコスト効率が向上し、セグメントのメンバーシップが更新されるたびに使用される SQL セグメントクレジットが少なくなります。完全更新エクステンションとは異なり、増分更新エクステンションを設定した場合、メンバーシップを毎日自動的に再生成できます。
 
-## メールの配信可能性センター
+## メールの配信センター
 
-[デリバラビリティセンター]({{site.baseurl}}/user_guide/data_and_analytics/analytics/deliverability_center#deliverability-center)は、送信されたメールに関するデータを追跡し、送信ドメインに関するデータを収集するためにGmailポストマスターツールの使用をサポートすることにより、メールのパフォーマンスに関するより多くのインサイトを提供します。
+[配信センター]({{site.baseurl}}/user_guide/data_and_analytics/analytics/deliverability_center#deliverability-center)は、送信メールのデータを追跡して送信ドメインに関するデータを収集する Google Postmaster Tools をサポートすることにより、メールのパフォーマンスに関してより多くのインサイトを提供します。
 
 {% alert important %}
-デリバラビリティセンターは現在、早期アクセス中です。早期アクセスに参加することに興味がある場合は、Brazeの顧客成功マネージャーに連絡してください。
+配信センターは現在早期アクセス段階です。初期のアクセスに参加したい場合は、Braze 顧客のサクセスマネージャーにお問い合わせください。
 {% endalert %}
 
 ## カタログの制限の更新
@@ -40,21 +40,21 @@ _2023年5月16日に一般公開_
 
 ## 新しいAPIおよびSDKエンドポイントの記事
 
-Braze は、ダッシュボード、SDK、REST エンドポイントのさまざまなインスタンスを管理しており、これを「クラスター」と呼びます。[APIおよびSDKエンドポイント]({{site.baseurl}}/user_guide/administrative/access_braze/sdk_endpoints)を確認して、利用可能なBrazeインスタンスのダッシュボードURL、APIエンドポイント、およびSDKエンドポイントのリストを確認してください。
+Braze は、ダッシュボード、SDK、REST エンドポイントのさまざまなインスタンスを管理しており、これを「クラスター」と呼びます。「[API と SDK のエンドポイント]({{site.baseurl}}/user_guide/administrative/access_braze/sdk_endpoints)」で、ダッシュボード URL、API エンドポイント、および使用可能な Braze インスタンスの SDK エンドポイントを確認してください。
 
-## Liquid FAQ
+## Liquid の FAQ
 
 いくつかの[Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/faq/)のよくある質問に答えました。 
 
 ## iOS SDK 廃止 - SWIFT
 
-BrazeのレガシーiOS SDKは、新しいSWIFT SDKに置き換えられる予定です。これにより、パフォーマンスの向上、新機能、および多くの改善がもたらされます—[新しいドキュメント](https://www.braze.com/docs/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overview)を含む！
+Braze のレガシー iOS SDK は非推奨になり、代わりに新しい Swift SDK が推奨されています。これにより、パフォーマンスの向上、新機能、および多くの改善がもたらされます—[新しいドキュメント](https://www.braze.com/docs/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overview)を含む！
 
 アップグレードをお考えですか？詳細については、[移行ガイド](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/appboy-migration-guide/)をご覧ください。
 
 ## SDKの更新
 
-次のSDKアップデートがリリースされました。以下に重大な更新が記載されています。それ以外の更新については、対応するSDKの変更履歴を確認してください。
+次のSDKアップデートがリリースされました。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [React Native SDK v4.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
 - [Android SDK 25.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
diff --git a/_lang/ja/_help/release_notes/2023/5_30_23.md b/_lang/ja/_help/release_notes/2023/5_30_23.md
index 0be0ac1238a..a749f381ade 100644
--- a/_lang/ja/_help/release_notes/2023/5_30_23.md
+++ b/_lang/ja/_help/release_notes/2023/5_30_23.md
@@ -10,9 +10,9 @@ description: "この記事には2023年5月30日のリリースノートが含
 
 ## 再設計されたBrazeナビゲーション
 
-Brazeナビゲーションを更新して、コンテンツをより迅速かつ効率的に作成およびアクセスできるようにしました。機能は現在、Brazeのマーケターのワークフローに馴染みがあり、関連性のある直感的なカテゴリに整理されています。今後数ヶ月間、古いナビゲーション体験と新しいナビゲーション体験を切り替えることができます。変更内容の詳細については、[Brazeナビゲーション]({{site.baseurl}}/navigation)を参照してください。
+Brazeナビゲーションを更新することで、より迅速かつ効率的にコンテンツを作成し、利用できるようになりました。機能は現在、Brazeのマーケターのワークフローに馴染みがあり、関連性のある直感的なカテゴリに整理されています。今後数か月間は、新旧のナビゲーションエクスペリエンスを切り替えることができます。変更内容の詳細については、[Brazeナビゲーション]({{site.baseurl}}/navigation)を参照してください。
 
-## 新しいCurrentsイベント
+## Currents の新しいイベント
 
 次のWhatsApp Currentsイベントが最近リリースされ、[メッセージエンゲージメントイベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events)の用語集に追加されました:
 
@@ -28,19 +28,19 @@ Brazeナビゲーションを更新して、コンテンツをより迅速かつ
 
 カタログは現在、ブラウザ内編集と[選択]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections)をサポートしています。選択は、キャンペーン内の各ユーザーにメッセージをパーソナライズするために使用できるデータのグループです。[カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalog/)を作成した後、Brazeキャンペーンに選択を組み込むことでこのデータをさらに参照できます。
 
-## Currents と Snowflake Data Sharing message_extras Liquid タグ
+## Currents および Snowflake データ共有の message_extras Liquid タグ
 
-[`message_extras` Liquid タグ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras/)を使用すると、コネクテッドコンテンツ、カタログ、カスタム属性（言語、国など）、キャンバスエントリプロパティ、その他のデータソースからのダイナミックなデータで送信イベントに注釈を付け、追加データをCurrentsまたはSnowflake Data Sharingに送り返すことができます。
+[`message_extras` Liquid タグ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras/)を使用して、Connected Content、カタログ、カスタム属性 (言語、国など)、キャンバスエントリプロパティ、またはその他のデータソースからのダイナミックデータを使用して送信イベントに注釈を付け、追加データを Currents または Snowflake データ共有に送り返すことができます。
 
 ## 新しいBrazeのパートナーシップ
 
 ### Tangerine - ローカライゼーション
 Brazeと[Tangerine]({{site.baseurl}}/partners/message_personalization/location/tangerine/)の統合により、Brazeの生キャンペーンおよびインプレッションデータをSnowflake Secure Data Sharingを通じてStore360に統合できます。ブランドは、これらのキャンペーンが実店舗への訪問や店内エンゲージメントに与える影響を測定できるようになりました。
 
-### Personalize.AI \- ダイナミックなコンテンツ
+### Personalize.AI \- ダイナミックコンテンツ
 Brazeと[Personalize.AI]({{site.baseurl}}/partners/message_personalization/dynamic_content/personalize/)の統合により、データをPersonalize.AIからBrazeプラットフォームにエクスポートして、メッセージのパーソナライゼーションとターゲティングが可能になります。
 
-### リーガル - メッセージング
+### Regal - メッセージング
 [Regal]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/regal/)とBrazeを統合することで、すべての顧客接点にわたってより一貫性のあるパーソナライズされた体験を提供できます。
 - Regalの電話での会話内容に基づいて、Brazeから最適な次のメールまたはプッシュ通知を送信します。
 - 高価値の顧客がBrazeからのマーケティングメールをクリックしたがコンバートしなかった場合、Regalでコールをトリガーします。
@@ -48,16 +48,16 @@ Brazeと[Personalize.AI]({{site.baseurl}}/partners/message_personalization/dynam
 ### Sendbird - メッセージング
 Brazeと[Sendbird]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/sendbird)の統合により、Brazeユーザーは次のことができます:
 - Brazeのセグメンテーションおよびトリガリング機能を利用して、パーソナライズされたアプリ内通知を開始します。
-- Sendbird Notificationsプラットフォームでアプリ内通知を作成し、それをアプリ環境内で配信して、ユーザーエンゲージメントを向上させます。
+- Sendbird Notifications プラットフォームで、アプリ環境内で配信されるカスタマイズされたアプリ内通知を作成し、ユーザーエンゲージメントを強化します。
 
-### Fresh Relevance - ダイナミックな Content
+### Fresh Relevance - ダイナミックコンテンツ
 Brazeと[Fresh Relevance]({{site.baseurl}}/partners/message_personalization/dynamic_content/fresh_relevance/)の統合により、顧客が閲覧した商品や同じカテゴリ内のアイテムに基づいた商品推奨など、トリガーメールにパーソナライズされたコンテンツを含めることができます。価格の下落、在庫の復活、複数段階の閲覧、カート放棄メッセージなど、より高度なトリガーメールキャンペーンを送信できます。
 
 ### Smartling - ローカライゼーション
-Brazeと[Smartling]({{site.baseurl}}/partners/message_personalization/localization/smartling/)の統合により、メールテンプレートとコンテンツブロックを翻訳できます。Smartlingは翻訳中に視覚的なコンテキストを提供することで、エラーを減らし、品質を維持します。
+Braze と [Smartling]({{site.baseurl}}/partners/message_personalization/localization/smartling/) の統合により、メールテンプレートとコンテンツブロックを翻訳できます。Smartling は、翻訳中に視覚的なコンテキストを利用できるようにすることで、エラーを減らし、品質を維持します。
 
 ### SalesWings - 分析
-Brazeと[SalesWings]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/saleswings#saleswings)の統合により、リードスコアリングおよびリードグレーディング機能を使用して、2つのプラットフォーム間でデータを柔軟に同期させ、リードを評価することができます。
+Braze と [SalesWings]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/saleswings#saleswings) の統合により、リードスコアリングとリードグレーディング機能を使用してリードを柔軟に選定できるよう、2つのプラットフォーム間でデータを同期できます。
 
 ### Kognitiv Inspire - ロイヤルティ
 Brazeと[Kognitiv]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/kognitiv/)の統合により、ロイヤルティ戦略を実装および評価し、プログラムの効果を高めるための革新的な機能とカスタマイズされたメンバーコミュニケーションを提供できます。
@@ -70,13 +70,13 @@ Brazeと[OneTrust]({{site.baseurl}}/partners/data_and_infrastructure_agility/dat
 
 ## SDKの更新
 
-以下のSDKアップデートがリリースされました。以下に重大な更新が記載されています。その他の更新については、対応するSDKの変更履歴を確認してください。
+以下のSDKアップデートがリリースされました。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [SWIFT SDK 6.1.0-6.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#620)
 - [Web SDK 4.7.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#471)
 - [React Native SDK 5.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#500)
-	- Braze Swift SDK 5.13.0 から 6.2.0 へのネイティブ iOS ブリッジを更新します。
-	- `setSDKFlavor` と `setMetadata` を削除します。これらはバージョン2.0.0からは無操作でした。
+	- ネイティブ iOS ブリッジを Braze Swift SDK 5.13.0から6.2.0に更新します。
+	- バージョン2.0.0以降 no-ops であった `setSDKFlavor` および `setMetadata` を削除します。
 	- iOSでは、これらのフィールドはSDK初期化時に`Braze.Configuration`オブジェクトを使用して設定する必要があります。
 	- Androidでは、これらのフィールドはbraze.xmlファイルを介して設定する必要があります。
 - [Cordova SDK 4.0.0-5.0.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md#500)
@@ -84,13 +84,13 @@ Brazeと[OneTrust]({{site.baseurl}}/partners/data_and_infrastructure_agility/dat
 		- Appboyのインスタンスの名前をBrazeに変更しました。
 			- プロジェクトが新しい命名規則に適切に移行されるようにするために、プロジェクト内の次のインスタンスに注意して置き換えてください:
 				- プラグインの名前が`cordova-plonugin-appboy`から`cordova-plugin-braze`に変更されました。
-					- Cordova プラグインを実行し、`cordova-plugin-appboy` を削除してから、[README](https://github.com/braze-inc/braze-cordova-sdk/blob/master/README.md) の指示に従ってプラグインを再追加してください。
+					- 必ず Cordova プラグインを実行し、`cordova-plugin-appboy` を削除してから、[README](https://github.com/braze-inc/braze-cordova-sdk/blob/master/README.md) の手順に沿ってプラグインを再追加します。
 				- このGitHubリポジトリはURLhttps://github.com/braze-inc/braze-cordova-sdkに移動されました。
 				- プロジェクトのconfig.xmlファイルで、各構成プロパティキーのcom.appboyのインスタンスをcom.brazeに名前変更します。
 				- JavaScriptクラスインターフェイス`AppboyPlugin`は`BrazePlugin`に名前が変更されました。
 		- Braze Android SDK 25.0.0 に更新されました。
 		- Braze Swift SDK 5.13.0 に更新されました。
-			- この更新は、コンテンツカードのクリックを記録する際にバージョン2.33.0で導入されたiOSの動作を修正します。呼び出し`logContentCardClicked`は、関連付けられたURLフィールドにリダイレクトする代わりに、メトリクスのクリックイベントのみを送信します。
+			- この更新は、コンテンツカードのクリックを記録する際にバージョン2.33.0で導入されたiOSの動作を修正します。`logContentCardClicked` を呼び出すと、クリックイベントを送信して関連する URL フィールドにリダイレクトするのではなく、指標のクリックイベントのみが送信されるようになりました。
 	- **Cordova SDK 5.0.0**
 		- これらのフィーチャーフラグメソッドを更新して、コールバックパラメータの代わりにプロミスを返すようにしました
 			- `getAllFeatureFlags()`
diff --git a/_lang/ja/_help/release_notes/2023/6_27_23.md b/_lang/ja/_help/release_notes/2023/6_27_23.md
index aee9975354a..32996514c32 100644
--- a/_lang/ja/_help/release_notes/2023/6_27_23.md
+++ b/_lang/ja/_help/release_notes/2023/6_27_23.md
@@ -3,47 +3,47 @@ nav_title: 2023年6月27日
 page_order: 6
 noindex: true
 page_type: update
-description: "この記事には、2023年6月27日のリリースノートが含まれている。"
+description: "この記事には、2023年6月27日のリリースノートが含まれています。"
 ---
 
 # 2023年6月27日リリース
 
-## ドラッグ・アンド・ドロップEメール設定センター
+## ドラッグ＆ドロップメールユーザー設定センター
 
-プリファレンスセンターを設定することで、ユーザーがメールメッセージの通知設定を編集・管理するためのワンストップショップが提供される。ドラッグ・アンド・ドロップのエディターで、プリファレンス・センターを作成し、カスタマイズすることができる。詳しくは、[ドラッグ＆ドロップでメールプレファレンスセンターを作成するを]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center/dnd_preference_center/)参照のこと。
+ユーザー設定センターを設定することで、ユーザーがメールメッセージングの通知設定を編集および管理するためのワンストップショップが提供されます。ドラッグ＆ドロップエディターで、ユーザー設定センターを作成およびカスタマイズして、特定のタイプの通信を受信するユーザーの管理に役立てることができます。詳細については、「[ドラッグ＆ドロップでメールユーザー設定センターを作成する]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center/dnd_preference_center/)」を参照してください。
 
 ## キャンバスの下書きを保存する
 
-キャンバスを作成して開始する際に、アクティブなキャンバスを編集して下書きとして保存することもできます。これにより、開始前に変更を試すことができます。大規模な変更が必要なアクティブなキャンバスがある場合は、この機能を使用して、これらの編集用に個別の下書きを作成できます。詳しくは[キャンバスの下書き保存を]({{site.baseurl}}/save_as_draft)参照のこと。
+キャンバスを作成して開始する際に、アクティブなキャンバスを編集して下書きとして保存することもできます。これにより、開始前に変更を試すことができます。大規模な変更が必要なアクティブなキャンバスがある場合は、この機能を使用して、これらの編集用に個別の下書きを作成できます。詳細については、「[キャンバスの下書き保存する]({{site.baseurl}}/save_as_draft)」を参照してください。
 
-## ウイニング・パス、ワンタイム・エントリー
+## ワンタイムエントリの勝者パス
 
-ユーザーが一度しか入力できないキャンバスで[ウィニングパスを]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/winning_path/#one-time-entry)使用する場合、ディレイグループが自動的に含まれるようになった。つまり、実験パスでウイニング・パス（Winning Path）を使用するために、ワンタイムエントリーのキャンバスで回避策を講じる必要がなくなったということである。
+ユーザーのエントリが1回に限定されているキャンバスで[勝者パス]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/winning_path/#one-time-entry)を使用する場合、遅延グループが自動的に含められます。つまり、実験パスで勝者パスを使用するために、ワンタイムエントリのキャンバスで回避策を講じる必要がなくなりました。
 
-## コンテンツカードのレート制限をリフレッシュする
+## コンテンツカードのレート制限を更新する
 
-2023年6月14日以降に加入した顧客については、パフォーマンス低下やエラーを防ぐため、手動で`requestContentCardsRefresh()` 、1端末あたり10分あたり3コールまでがデフォルトの料金制限となる。コンテンツカードのリフレッシュの詳細については、[iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/integration#refreshing-content-cards)、[Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/refreshing_the_feed)、[Webの]({{site.baseurl}}/developer_guide/platform_integration_guides/web/content_cards/refreshing_the_feed)それぞれのドキュメントを参照のこと。
+2023年6月14日以降に登録された顧客については、`requestContentCardsRefresh()` を手動で呼び出すためのデフォルトのレート制限は、パフォーマンスの低下とエラーを防ぐために、デバイスごとに10分あたり3コールです。コンテンツカードの更新の詳細については、[iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/integration#refreshing-content-cards)、[Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/refreshing_the_feed)、[Web]({{site.baseurl}}/developer_guide/platform_integration_guides/web/content_cards/refreshing_the_feed) の各ドキュメントを参照してください。
 
-## オーディエンスがFacebookに同期する
+## Facebook へのオーディエンス同期
 
-[Audience Sync to Facebookを]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync/)使用している場合、2023年7月から、MetaはMeta workアカウントを、この新しいアカウントタイプの採用に関心のある少数の企業に展開していることに留意してほしい。Brazeと統合されたビジネスアカウントをお持ちの場合は、この実装を維持し、アクティブなキャンバスを中断させないために、ビジネスアカウントで[Facebookパートナーページへの]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync#step-1-connect-to-facebook)接続を切断し、再接続することを確認する。
+[Facebook へのオーディエンス同期]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync/)を使用している場合、2023年7月より、Meta は Meta ワークアカウントという新しいアカウントタイプをその導入に関心のある少数の企業向けに展開していることをご確認ください。Braze と統合されたビジネスアカウントをお持ちの場合は、この実装を維持し、アクティブなキャンバスの動作を中断させないために、ビジネスアカウントで [Facebook パートナーページ]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync#step-1-connect-to-facebook)への接続を切断し、再接続してください。
 
-## データブリックのためのクラウド・データ・インジェスト
+## Databricks のクラウドデータ取り込み
 
-Braze Cloud Data Ingestion for Databricksにより、顧客はユーザーデータ（属性、イベント、購入）とユーザー削除をDatabricksからBrazeに直接同期することができる。Brazeに同期されると、このデータはBrazeプラットフォームの他のデータと同様に使用できる。この機能は[クラウド・データ・インジェスト]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/)製品の拡張であり、現在早期アクセス中である。
+Braze の Databricks のクラウドデータ取り込みにより、顧客はユーザーデータ (属性、イベント、購入) とユーザー削除を Databricks から Braze に直接同期できます。Braze に同期されると、このデータを Braze プラットフォームの他のデータと同様に使用できるようになります。この機能は[クラウドデータ取り込み]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/)製品の拡張であり、現在早期アクセス版です。
 
-## プライバシー・ポータル
+## プライバシーポータル
 
-新しい[Brazeプライバシーポータルでは]({{site.baseurl}}/user_guide/privacy_portal)、Brazeがどのように貴社の顧客データを適切に管理し、重要な点として、貴社のビジネスに関連するデータ保護規則を遵守するための対策を講じることができるかについて、有益な情報を提供する。当社は、適用されるデータ保護法および規制を遵守してBrazeサービスを利用する際に役立つ情報および文書へのリンクをまとめた。
+新しい [Braze プライバシーポータル]({{site.baseurl}}/user_guide/privacy_portal)では、Braze がどのようにお客様の顧客データの適切な管理をサポートできるのかに関する有用な情報が提供されます。これにより、お客様のビジネスに関連するデータ保護規則を遵守するための対策を講じることができる点が重要です。当社は、適用されるデータ保護の法律と規制を遵守して Braze サービスを利用するために役立つ情報とドキュメントへのリンクをまとめました。
 
-## SDKのアップデート
+## SDK 更新
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下の SDK 更新がリリースされました。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
-- [Android SDK 26.0.0-26.1.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2610)
-	- {% raw %}`BrazeConfig.setIsHtmlInAppMessageHtmlLinkTargetEnabled()` または`<bool name="com_braze_html_in_app_message_enable_html_link_target">true</bool>` を`braze.xml` に追加することで、HTMLアプリ内メッセージのリンクターゲットの動作を設定できるようになった。デフォルトはenabledである。{% endraw %}
-		- {% raw %}有効にすると、リンクターゲットが設定されたアプリ内メッセージのリンク（例えば、`<a HREF="https://www.braze.com" target="_blank">Please Read</a>` ）は、ブラウザでリンクを開くが、アプリ内メッセージは閉じない。{% endraw %}
-- [Web SDK 4.7.2-4.8.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#480)
+- [Android SDK 26.0.0 ～ 26.1.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2610)
+	- {% raw %}`BrazeConfig.setIsHtmlInAppMessageHtmlLinkTargetEnabled()` から、または `<bool name="com_braze_html_in_app_message_enable_html_link_target">true</bool>` を `braze.xml` に追加することで、HTML アプリ内メッセージのリンクターゲットの動作を設定できるようになりました。これはデフォルトで有効です。{% endraw %}
+		- {% raw %}有効にすると、リンクターゲットが設定されたアプリ内メッセージのリンク （`<a HREF="https://www.braze.com" target="_blank">Please Read</a>` など) がブラウザで開かれますが、アプリ内メッセージは閉じられません。{% endraw %}
+- [Web SDK 4.7.2 ～ 4.8.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#480)
 - [Swift SDK 6.3.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#630)
 - [Unity SDK 4.1.1](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md#411)
 - [React Native SDK 5.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#510)
diff --git a/_lang/ja/_help/release_notes/2023/7_25_23.md b/_lang/ja/_help/release_notes/2023/7_25_23.md
index 394940e263a..80a7a2fd277 100644
--- a/_lang/ja/_help/release_notes/2023/7_25_23.md
+++ b/_lang/ja/_help/release_notes/2023/7_25_23.md
@@ -3,28 +3,28 @@ nav_title: 2023年7月25日
 page_order: 5
 noindex: true
 page_type: update
-description: "この記事には、23年7月25日のリリースノートが含まれている。"
+description: "この記事には、07/25/23のリリースノートが含まれます。"
  
 ---
 # 2023年7月25日リリース
 
 ## キャンバスの承認 
-新しいキャンバス承認ワークフロー設定は、新しいキャンバスを起動する前にレビュープロセスを追加する。この機能はデフォルトではオフになっており、その実装をコントロールできるようになっている。このワークフローを有効にする詳細については、[キャンバスの承認と]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/canvas_approval/)許可を参照すること。
+新しい「キャンバスアプリ」の設定では、新しいキャンバスを起動する前に確認処理が追加されます。この機能はデフォルトで無効になっているため、インプリメンテーションをコントロールできます。このワークフローのアクティベーションについて詳しくは、[キャンバスアプリの権限]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/canvas_approval/) を参照してください。
  
 ## キャンバスの機能フラグ
-フィーチャー・フラグを使えば、ユーザー・ベースの異なるセクションに対してフィーチャーをオフにしたりオンにしたりすることで、新機能に関する仮説を実験し、確認することができる。Canvasの新しい機能フラグ・コンポーネントを使用すると、ユーザーの機能フラグがオンかオフかに基づいて、Canvas内のオーディエンスをセグメント化することができる。さらに、エクスペリメント・パスでは、異なるメッセージやパスを互いにテストし、どれが最も効果的かを判断することで、これらのコンバージョンを最適化することができる。一般的な機能フラグについての情報は、[機能フラグの概要を]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/about/)参照するか、または[Canvasでの機能フラグの使用について]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/feature_flags/)詳しく学ぶ。
+フィーチャー・フラグを使えば、ユーザー・ベースの異なるセクションに対してフィーチャーをオフにしたりオンにしたりすることで、新機能に関する仮説を実験し、確認することができる。「キャンバス」の新しいフィーチャーフラグコンポーネントを使用すると、フィーチャーフラグがユーザーに対して有効か無効かに基づいて、キャンバスでオーディエンスをSegmentできます。さらに、エクスペリメント・パスでは、異なるメッセージやパスを互いにテストし、どれが最も効果的かを判断することで、これらのコンバージョンを最適化することができる。一般的なフィーチャーフラグの詳細については、[フィーチャーフラグ概要]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/about/)を参照するか、キャンバスでフィーチャーフラグsを使用して[の詳細を確認してください。
 
-## セグメントを管理する
+## 「セグメントの管理」の記事
 新しい[Managing Segments（セグメントの管理]({{site.baseurl}}/user_guide/engagement_tools/segments/managing_segments/)）の記事では、セグメントのリストのフィルタリング、セグメントの作成、セグメントの編集など、セグメントを設定するためのアクションについて説明している。
  
-## 行コンポーネント・コンテンツ・ブロック
-行コンポーネントをコンテンツブロックとして保存し、キャンバス内のすべてのメールキャンペーンやメールメッセージで使用できるようになった。ドラッグ・アンド・ドロップによるコンテンツ・ブロックの詳細については、[コンテンツ・ブロックを]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_content_blocks/)参照のこと。
+## 行コンポーネントコンテンツブロック
+行コンポーネントをコンテンツブロックとして保存し、キャンバス内のすべてのメール キャンペーン s およびメール メッセージで使用できるようになりました。ドラッグアンドドロップコンテンツブロックの詳細については、[コンテンツブロック]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_content_blocks/)を参照してください。
 
-## セージAI
-Sage AI by Brazeは、クリエイティビティ、パーソナライゼーション、エンゲージメント戦略の最適化のための参入障壁を下げる、アクセスしやすく使いやすいツールのコレクションを提供する。Sage AIの特徴や機能の詳細については、[ドキュメントを]({{site.baseurl}}/user_guide/sage_ai)参照されたい。
+## BrazeAI<sup>TM</sup>
+BrazeAI<sup>TM</sup> は、エンゲージメント 戦略のクリエイティビティ、パーソナライゼーション、最適化のエントリに対する障壁を低減する、アクセシブルで使いやすい道具の集合を提供します。BrazeAI<sup>TM</sup> の機能については、[ドキュメント]({{site.baseurl}}/user_guide/sage_ai) を参照してください。
 
 ## 電話番号でユーザープロファイルを更新する
-エンドポイントを使う [`/users/track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track)エンドポイントを使うと、電話番号を使ってユーザー・プロフィールを更新できる。 
+[`/users/track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track)エンドポイントを使用して、電話番号を使用してユーザープロファイルを更新できます。 
 
 {% alert important %}
 この機能は現在早期アクセス段階です。早期アクセスへの参加に興味がある方は、Brazeのアカウントマネージャーに連絡を。
@@ -35,14 +35,14 @@ Sage AI by Brazeは、クリエイティビティ、パーソナライゼーシ
 
 ## SDKのアップデート
  
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Android SDK 26.2.0-26.3.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2620) 
 - [Swift SDK 6.3.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#631)
 - [Web SDK 4.8.1-4.8.3](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#481)
 - [Flutter SDK 6.0.0](https://github.com/braze-inc/braze-flutter-sdk/blob/master/CHANGELOG.md#600)
-    - ネイティブAndroidブリッジをBraze Android SDK 25.0.0から26.1.0に更新。
+    - ネイティブAndroid ブリッジをBraze Android SDK 25.0.0 から26.1.0 にアップデートします。
 - [React Native SDK 5.2.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#520)
 - [Roku SDK 1.0.0](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md#100)
-- [ユニティ 4.2.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md#420)
-    - Androidプラグインを更新し、Braze Android SDK 26.2.0を使用するようにした。
\ No newline at end of file
+- [Unity 4.2.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md#420)
+    - Braze Android SDK 26.2.0を使用するようにAndroidプラグインを更新しました。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2023/8_22_23.md b/_lang/ja/_help/release_notes/2023/8_22_23.md
index 76712190fa3..6ade18a16c0 100644
--- a/_lang/ja/_help/release_notes/2023/8_22_23.md
+++ b/_lang/ja/_help/release_notes/2023/8_22_23.md
@@ -10,42 +10,42 @@ description: "この記事には、2023年8月22日のリリースノートが
 
 ## Shopifyカタログ 
 
-Shopifyのカタログを使用すると、ShopifyストアからBrazeのカタログに製品をインポートでき、製品データを取り込むプロセスを自動化してメッセージのパーソナライゼーションを深めることができます。放棄カート、注文確認などを最新の製品詳細と情報で充実させることができます。
+Shopifyのカタログを使用すると、ShopifyストアからBrazeのカタログに製品をインポートでき、製品データを取り込むプロセスを自動化してメッセージのパーソナライゼーションを深めることができます。最新の製品の詳細と情報を使用して、放棄カートや注文確認などを強化できます。
 
 ## メールによるユーザーの統合
 
 [メールでユーザーをマージ]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/#merging-users-by-email)できるようになりました。`/users/merge`エンドポイントを使用します。 
 
 {% alert important %}
-メールによるユーザーのマージと、識別子が一致しない`/users/merge`の使用は現在、早期アクセス中です。早期アクセスへの参加に興味がある場合は、Braze アカウントマネージャーにお問い合わせください。
+メールによるユーザーのマージと、識別子が一致しない`/users/merge` の使用は、現在初期アクセス中です。早期アクセスへの参加に興味がある場合は、Braze アカウントマネージャーにお問い合わせください。
 {% endalert %}
 
 ## WhatsAppのベストプラクティス
 
-WhatsAppメッセージを送信する前に、推奨される[ベストプラクティス]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_best_practices/)を参照して、高い電話品質評価を維持し、ブロックや報告を回避し、ユーザーのオプトインおよびオプトアウトを行うことができます。
+WhatsApp メッセージを送信する前に、推奨される[ベストプラクティス]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_best_practices/)を参照して、電話品質の高評価を維持し、ブロックとレポートを回避し、ユーザーをオプトインおよびオプトアウトできます。
 
 ## ドメイン信頼度
 
-配信可能性センターでは、[ドメインの評判]({{site.baseurl}}/user_guide/data_and_analytics/analytics/deliverability_center#domain-reputation)を表示および監視して、スパムフォルダーにフィルタリングされるのを回避するのに役立てることができます。
+配信センターで、スパムフォルダーへのフィルタリングを回避するため、[ドメインレピュテーション]({{site.baseurl}}/user_guide/data_and_analytics/analytics/deliverability_center#domain-reputation)を表示および監視できるようになりました。
 
 ## カスタマイズガイド 
 
-私たちは、開発者ポータルの再編成を紹介することに興奮しています。現在、[コンテンツカード]({{site.baseurl}}/developer_guide/customization_guides/content_cards)から始まるSDKのカスタマイズオプションは、専用のカスタマイズガイドに統合されています。この変更により、詳細な指示にアクセスしやすくなり、特定のニーズに合わせた体験を簡単にカスタマイズできるようになります。
+Developer Portal が再編成されます。現在、[コンテンツカード]({{site.baseurl}}/developer_guide/customization_guides/content_cards)から始まるSDKのカスタマイズオプションは、専用のカスタマイズガイドに統合されています。この変更により、詳細な指示にアクセスしやすくなり、特定のニーズに合わせた体験を簡単にカスタマイズできるようになります。
 
-## キャンバスでのカード作成
+## Canvas でのカード作成
 
 カードが作成されるときに指定することにより、Brazeが新しいコンテンツカードキャンペーンおよびキャンバスステップのオーディエンス適格性とパーソナライゼーションを評価するタイミングを選択できます。
 
 {% alert important %}
-キャンバスのステップでのカード作成のコントロールは早期アクセスです。早期アクセスに参加したい場合は、Brazeのアカウントマネージャーに連絡してください。
+キャンバスステップにおけるカード作成のコントロールは、早期アクセス段階です。早期アクセスに参加したい場合は、Brazeのアカウントマネージャーに連絡してください。
 {% endalert %}
 
-## ワークスペースへのコピー
+## ワークスペースにコピーする
 
-[キャンペーンをワークスペース間でコピーすること]({{site.baseurl}}/copying_to_workspaces/)により、別のワークスペース内のキャンペーンのコピーからメッセージ作成を開始することで、メッセージ作成を迅速に開始できます。このコピーは、編集して開始するまで下書きとして残り、成功したメッセージング戦略を維持し、構築するのに役立ちます。
+[ワークスペース間でキャンペーンをコピー]({{site.baseurl}}/copying_to_workspaces/)すると、別のワークスペースにあるキャンペーンのコピーを利用して、メッセージの作成をすぐに開始できます。このコピーは、編集して開始するまで下書きとして残り、成功したメッセージング戦略を維持し、構築するのに役立ちます。
 
 {% alert important %}
-キャンペーンのワークスペース間のコピーは現在早期アクセス中です。早期アクセスに参加することに興味がある場合は、Brazeのアカウントマネージャーに連絡してください。
+ワークスペース間でのキャンペーンのコピーは、現在初期アクセス段階です。早期アクセスに参加することに興味がある場合は、Brazeのアカウントマネージャーに連絡してください。
 {% endalert %}
 
 ## 最大限にプッシュ通知
@@ -53,25 +53,25 @@ WhatsAppメッセージを送信する前に、推奨される[ベストプラ
 [Push Max]({{site.baseurl}}/user_guide/message_building_by_channel/push/android/push_max/)は、Androidプッシュ通知を増幅し、トラッキングに失敗したプッシュ通知を追跡し、ユーザーが受信しやすいタイミングで再送信します。Push Max について学び、この機能を使用して Android プッシュ通知の配信可能性を [中国の OEM デバイス]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/chinese_push_deliverability/) に向上させる方法を学びます。
 
 {% alert important %}
-Push Maxは現在アーリーアクセス中です。早期アクセスに参加したい場合は、Brazeのアカウントマネージャーに連絡してください。
+現在、Max(最大)を押すと、初期アクセスになります。早期アクセスに参加したい場合は、Brazeのアカウントマネージャーに連絡してください。
 {% endalert %}
 
 ## SDKの更新
 
-次のSDKアップデートがリリースされました。以下に重大な更新が記載されています。その他の更新については、対応するSDKの変更履歴を確認してください。
+次のSDKアップデートがリリースされました。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Xamarin SDK 2.0.0–2.0.1](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
-    - Androidバインディングを更新して、Braze Android SDK 26.3.2を使用するようにしました
+    - Braze Android SDK 26.3.2を使用するように Android バインドを更新しました。
 - [Flutter SDK 6.0.1](https://pub.dev/packages/braze_plugin/changelog)
-    - ネイティブ{_}Android{_}ブリッジを{_}Braze{_}Android{_}SDK{_}26.1.0{_}から{_}26.1.1{_}に更新しました。
+    - ネイティブ Android ブリッジを Braze Android SDK 26.0.1から26.1.1に更新しました。
 - [Android SDK 27.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
 - [SWIFT SDK 6.5.0–6.6.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
     - HTMLのアプリ内メッセージで、カスタムイベントおよび購入プロパティが常に`1`および`0`の値を`true`および`false`にそれぞれ変換してしまう問題を修正しました。これらのプロパティ値は、HTMLの元の形式を尊重するようになります。
 - [React Native SDK 6.0.0–6.0.2](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
-    - ネイティブAndroidブリッジをBraze Android SDK 26.3.1から26.3.2に更新しました。
+    - ネイティブ Android ブリッジを Braze Android SDK 26.3.1から26.3.2に更新しました。
 - [Cordova SDK 6.0.0-6.0.1](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
-    - ネイティブのAndroidバージョンをBraze Android SDK 26.3.1から26.3.2に更新しました
-- [エクスポプラグイン1.1.2](https://github.com/braze-inc/braze-expo-plugin/blob/1.1.2/CHANGELOG.md)
+    - ネイティブ Android バージョンを Braze Android SDK 26.3.1から26.3.2に更新しました。
+- [Expo プラグイン1.1.2](https://github.com/braze-inc/braze-expo-plugin/blob/1.1.2/CHANGELOG.md)
 - [Unity 4.3.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
 - [Segment Kotlin 1.4.1](https://github.com/braze-inc/braze-segment-kotlin/blob/main/CHANGELOG.md)
 - [Segment-Android 15.0.1](https://github.com/Appboy/appboy-segment-android/blob/master/CHANGELOG.md)
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2023/9_19_23.md b/_lang/ja/_help/release_notes/2023/9_19_23.md
index 6625f6afa79..c50ce5e0017 100644
--- a/_lang/ja/_help/release_notes/2023/9_19_23.md
+++ b/_lang/ja/_help/release_notes/2023/9_19_23.md
@@ -3,114 +3,114 @@ nav_title: 2023年9月19日
 page_order: 3
 noindex: true
 page_type: update
-description: "この記事には、09/19/23のリリースノートが含まれている。"
+description: "この記事には、2023年9月19日のリリースノートが含まれています。"
 ---
 
 # 2023年9月19日リリース
 
-## クラウドデータ取り込みのためのBigQuery
+## クラウドデータ取り込みの BigQuery
 
-サーバーレス・エンタープライズ・データウェアハウスである[BigQueryと](https://cloud.google.com/bigquery)Cloud Data Ingestion統合を作成できるようになった。詳細については、[Cloud Data Integestionの統合を]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/?tab=bigquery)参照のこと。
+サーバーレスエンタープライズデータウェアハウスの [BigQuery](https://cloud.google.com/bigquery) を使用して、クラウドデータ取り込みの統合を作成できるようになりました。詳細については、[クラウドデータ取り込みの統合]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/?tab=bigquery)を参照してください。
 
-## ブレイズデータ変換
+## Braze Data Transformation
 
-[Brazeデータ変換では]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/overview/)、外部プラットフォームからBrazeユーザープロファイルへのデータフローを自動化するためのWebhook統合を構築し、管理することができる。この新しく統合されたユーザーデータにより、さらに洗練されたマーケティングユースケースを強化できます。
+[Braze Data Transformation]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/overview/) を使用すると、Webhook 連携の構築および管理を行って、外部プラットフォームから Braze ユーザープロファイルへのデータフローを自動化できます。この新しく統合されたユーザーデータにより、さらに洗練されたマーケティングユースケースを強化できます。
 
 ## キャンバスのコメント
 
-[Canvasesのコメントは]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_comments/)、マーケティングチームがCanvasesの詳細を確認し、議論し、レビューするための素晴らしい共同スペースとなる。キャンバスを作成する際、同僚から追加のフィードバックが必要な箇所を特定するために、コメントを作成して管理することができます。
+[キャンバスのコメント]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_comments/)は、マーケティングチームがキャンバスの詳細について確認し、議論し、検討するための素晴らしいコラボレーションツールとして利用できます。キャンバスを作成する際、同僚から追加のフィードバックが必要な箇所を特定するために、コメントを作成して管理することができます。
 
 ## 配信センター
 
-[配信可能性センターでは]({{site.baseurl}}/user_guide/data_and_analytics/analytics/deliverability_center)、Gmailポストマスターツールの使用をサポートすることで、送信されたメールのデータを追跡し、送信ドメインに関するデータを収集することで、メールのパフォーマンスに関するより詳細な洞察を提供する。 
+[配信センター]({{site.baseurl}}/user_guide/data_and_analytics/analytics/deliverability_center)は、送信メールのデータを追跡して送信ドメインに関するデータを収集する Google Postmaster Tools をサポートすることにより、メールのパフォーマンスに関してより多くのインサイトを提供します。 
 
-メールの配信到達性はキャンペーン成功の中核です。BrazeダッシュボードのDeliverability Centerを使用すると、IPレピュテーションや配信エラーごとにドメインを表示し、メール配信に関する潜在的な問題を発見してトラブルシューティングすることができる。
+メールの配信到達性はキャンペーン成功の中核です。Braze ダッシュボードの配信センターを使用すると、IP の信頼度または配信エラー別にドメインを表示し、メールの配信到達性に関する潜在的な問題を検出してトラブルシューティングを行うことができます。
 
 ## アプリ内メッセージのドラッグ＆ドロップ・エディター
 
-これらの追加機能は、[アプリ内メッセージのドラッグ＆ドロップ・エディターに]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/)追加された：
+以下の追加機能が、[アプリ内メッセージのドラッグ＆ドロップエディター]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/)に追加されました。
 
 - メッセージを削除しないテキストリンク
-- プッシュ・プライマーを要求するボタン操作
+- プッシュプライマーをリクエストするボタンアクション
 - カスタム・コード・エディター・ブロック
 
 ドラッグ＆ドロップ・エディターで利用可能なすべての機能を利用するには、SDKを推奨SDKバージョンにアップデートすること。
 
 ### カスタムテンプレートを保存する（早期アクセス）
 
-アプリ内メッセージ用のドラッグ＆ドロップエディターでは、早期アクセス参加者は、エディターを終了した後に利用できる**「テンプレートとして保存**」ボタンを使って、カスタムアプリ内メッセージテンプレートを作成・保存できる。テンプレートとして保存する前に、まずキャンペーンを立ち上げるか、下書きとして保存する必要がある。 
+アプリ内メッセージのドラッグ＆ドロップエディターで、早期アクセスの参加者は、\[**テンプレートとして保存**] ボタンを使用してカスタムアプリ内メッセージテンプレートを作成および保存できます。このボタンは、エディターの終了後に使用できます。テンプレートとして保存する前に、まずキャンペーンを立ち上げるか、下書きとして保存する必要がある。 
 
-**Templates**>**In-App Message Templatesで**アプリ内メッセージテンプレートを作成・保存することもできる。
+また、\[**テンプレート**] > \[**アプリ内メッセージテンプレート**] に移動して、アプリ内メッセージテンプレートを作成、保存することもできます。
 
 {% alert important %}
-カスタム・テンプレートを保存する機能は、現在早期アクセスとなっている。早期アクセスへの参加に興味がある方は、Brazeのアカウントマネージャーに連絡を。
+カスタムテンプレートを保存する機能は、現在早期アクセス段階です。早期アクセスへの参加に興味がある方は、Brazeのアカウントマネージャーに連絡を。
 {% endalert %}
 
 ## アプリ内メッセージのダークモードを無効にする
 
-開発者は、ユーザー端末がダークモードをオンにしている場合、アプリ内メッセージがダークモードのスタイルを採用しないようにすることができる。この実装方法については、プラットフォーム別に以下のドキュメントを参照のこと：
+開発者は、ユーザーデバイスのダークモードがオンになっている場合に、アプリ内メッセージがダークモードスタイルを採用しないようにすることができます。この実装方法については、プラットフォーム別に以下のドキュメントを参照のこと：
 
 - [Swift]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/setting_delegates/#disabling-dark-mode)
 - [Objective-C]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/in-app_messaging/customization/handling_in_app_display/#disabling-dark-mode)
 
 ## メッセージ・アーカイブ用の新しいフィールド
 
-[メッセージアーカイブは]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/)、アーカイブやコンプライアンス目的でユーザーに送信されたメッセージのコピーをS3バケットに保存することができる。メッセージが送信されるたびに、S3バケットに配信されるJSONペイロードに以下のフィールドが追加された：
+[メッセージアーカイブ]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/)では、アーカイブまたは準拠のためにユーザーに送信されたメッセージのコピーをS3バケットに保存できます。メッセージが送信されるたびに、S3バケットに配信されるJSONペイロードに以下のフィールドが追加された：
 
 - `user_id`
 - `campaign_name`
 - `canvas_name`
 - `canvas_step_name`
 
-## 新リキッドパーソナライズ・タグ
+## 新流動パーソナライゼーション タグs
 
-アプリ内メッセージでは、Liquid内で以下のアプリ属性を使用できる。値は、アプリがどのSDK APIキーを使ってメッセージングをリクエストするかに基づいている：
+アプリ内メッセージでは、Liquid内で以下のアプリ属性を使用できる。この値は、アプリがメッセージングをリクエストするために使用する SDK API キーに基づきます。
 
 - {% raw %}`{{app.${api_id}}}`{% endraw %}
 - {% raw %}`{{app.${name}}}`{% endraw %}
 
-詳しくは、[パーソナライズタグをサポートしたを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags#targeted-app-information)参照のこと。
+詳細については、[サポートされるパーソナライゼーション タグs]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags#targeted-app-information)を参照してください。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
-### アンタボ・ロイヤリティ・クラウド - チャネル拡張
+### Antavo Loyalty Cloud - チャネル拡張
 
-[Antavoと]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/antavo/)Brazeの統合により、ロイヤルティプログラム関連データを利用してパーソナライズされたキャンペーンを構築し、顧客体験を向上させることができる。これはAntavoからBrazeへの一方向のデータ同期のみである。
+[Antavo]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/antavo/)およびBrazeインテグレーションにより、ロイヤルティプログラム関連のデータを使用してパーソナライズされた キャンペーンsを構築し、カスタマーエクスペリエンスを強化することができます。Antavo では、2 つのプラットフォーム間のロイヤルティデータ同期がサポートされています。これは、Antavo からBraze への一方向データ同期のみです。
 
-### Ketch - 顧客データ・プラットフォーム
+### Ketch - カスタマデータプラットフォーム
 
-Brazeと[Ketchの]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/ketch/)統合により、Ketchプリファレンスセンター内で顧客のコミュニケーションプリファレンスをコントロールし、これらの変更を自動的にBrazeに伝えることができる。
+Braze と [Ketch]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/ketch/) の統合により、Ketch ユーザー設定センター内の顧客のコミュニケーション設定を管理し、これらの変更を自動的に Braze に伝播できます。
 
-### レッドポイント - 顧客データ・プラットフォーム
+### Redpoint - カスタマデータプラットフォーム
 
-レッドポイントは、マーケティング担当者に完全に統合されたキャンペーン・オーケストレーション・プラットフォームを提供するテクノロジー・プラットフォームである。Brazeと[Redpointの]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/redpoint/)統合により、RedpointのCDPデータに基づいてBrazeのセグメントを作成できる。 
+Redpoint は、完全に統合されたキャンペーンオーケストレーションプラットフォームをマーケターに提供するテクノロジープラットフォームです。Braze および[Redpoint]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/redpoint/) インテグレーションを使用すると、RedpointのCDP データに基づいてBraze Segments を作成できます。 
 
-### サイモンデータ - 顧客データプラットフォーム
+### Simon Data - 顧客データプラットフォーム
  
-Brazeと[Simon Dataの]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/simondata/)統合を使用して、洗練されたオーディエンスを作成し、Brazeに同期させ、コードなしでリアルタイムにオーケストレーションを行う。この統合により、Simonのキャンペーン優先順位付けやIDマッチング機能、複雑な集計サポートなどを最大限に活用し、Brazeのキャンペーンをダウンストリームで向上させることができる。
+Braze および[Simon Data]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/simondata/) インテグレーションを使用して、Braze に高度なオーディエンスs を作成し、コードなしでリアルタイムでオーケストレーションできるように同期します。この統合により、Simonのキャンペーン優先順位付けやIDマッチング機能、複雑な集計サポートなどを最大限に活用し、Brazeのキャンペーンをダウンストリームで向上させることができる。
 
-### オファーフィット - ダイナミック・コンテンツ
+### OfferFit - ダイナミックコンテンツ
 
-[OfferFitと]({{site.baseurl}}/partners/message_personalization/dynamic_content/offerfit/)Brazeの統合により、顧客データに基づいて、すべての顧客に適切なメッセージ、チャネル、タイミングを自動的に発見することができる。クロスセル、アップセル、再購入、リテンション、リニューアル、リファーラル、ウィン・バックなどのビジネス目標を持つ特定された既存顧客に対して、キャンペーンを最適化することができる。
+[OfferFit]({{site.baseurl}}/partners/message_personalization/dynamic_content/offerfit/)とBrazeインテグレーションを使用すると、顧客データに基づいてすべての顧客の正しいメッセージ、チャネル、タイミングを自動的に検出できます。ビジネス目標 (クロスセル、アップセル、再購入、リテンション、更新、紹介、ウィンバックなど) を使用して、既存の指定された顧客に合わせてキャンペーンを最適化できます。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Swift SDK 6.6.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#661)
 - [Web SDK 4.9.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#490)
 - [Android SDK 28.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2800)
-    - SDKの最小バージョンを21（ロリポップ）に更新した。
+    - 最小 SDK バージョンを21 (Lollipop) に更新しました。
     - フィーチャー・フラグ機能が変更された。
     - `Braze.getFeatureFlag(id)` は、機能フラグが存在しない場合はNULLを返すようになった。
-    - `Braze.subscribeToFeatureFlagsUpdates()` がコールバックされるのは、リフレッシュ・リクエストが完了したときだけで、最初は、以前にキャッシュされたデータが存在する場合だけである。また、リフレッシュに失敗した場合は、キャッシュされた機能フラグとともに呼び出される。
-        - アプリ起動時に即座にキャッシュ値が欲しい場合は、`Braze.getFeatureFlag(id)` 。
-    - `DefaultInAppMessageViewWrapper.createButtonClickListener()` を`DefaultInAppMessageViewWrapper.createButtonClickListeners()` にリファクタリングした。
+    - リフレッシュリクエストが完了し、以前にキャッシュされたデータが存在する場合にのみ、`Braze.subscribeToFeatureFlagsUpdates()` でコールバックが行われます。また、リフレッシュ失敗時にはキャッシュされたフィーチャーフラグで呼び出されます。
+        - アプリの起動時にキャッシュされた値をすぐに使用する場合は、`Braze.getFeatureFlag(id)` を使用します。
+    - `DefaultInAppMessageViewWrapper.createButtonClickListener()` を`DefaultInAppMessageViewWrapper.createButtonClickListeners()` にリファクタリングしました。
 - [React Native SDK 7.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#700)
-    - ネイティブAndroidブリッジを[Braze Android SDK 26.3.2から27.0.1に](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2701)更新。
+    - ネイティブ Android ブリッジを [Braze Android SDK 26.3.2から27.0.1](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2701)に更新します。
 - [Cordova SDK 7.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2800)
-    - ネイティブAndroidブリッジを[Braze Android SDK 26.3.2から27.0.1に](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2701)更新。
+    - ネイティブ Android ブリッジを [Braze Android SDK 26.3.2から27.0.1](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2701)に更新します。
 - [Roku SDK 2.0.0](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md#200)
-    - `getFeatureFlag` フラグが存在しない場合は無効を返す。
-    - `BrazeTask` 機能フラグのリフレッシュが成功したとき、失敗したときを知るために、`BrazeFeatureFlagsUpdated` 。データ値は常に異なるとは限らない。
+    - フラグが存在しない場合、`getFeatureFlag` は無効を返します。
+    - フィーチャーフラグの更新が成功するか、失敗するかを認識するため、`BrazeTask` で `BrazeFeatureFlagsUpdated` が監視されるようになりました。データ値は常に異なるとは限らない。
 
diff --git a/_lang/ja/_help/release_notes/2024/1_9_24.md b/_lang/ja/_help/release_notes/2024/1_9_24.md
index 6eb8b962873..17030d0e688 100644
--- a/_lang/ja/_help/release_notes/2024/1_9_24.md
+++ b/_lang/ja/_help/release_notes/2024/1_9_24.md
@@ -3,16 +3,16 @@ nav_title: 2024年1月9日
 page_order: 12
 noindex: true
 page_type: update
-description: "この記事には、2024年1月9日のリリースノートが含まれている。"
+description: "この記事には、2024年1月9日のリリースノートが含まれています。"
 ---
 
 # 2024年1月9日リリース
 
 ## Shopifyとの統合に関するドキュメントを更新
 
-BrazeとShopifyの統合ドキュメントの一部を更新した：
+以下のようなBrazeとShopifyインテグレーションドキュメントのセクションを更新します。
 
-- [Shopifyを使い始める]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/)
+- [Shopify を使い始める]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/)
 - [BrazeでShopifyを設定する]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/)
 - [ShopifyのユーザーID管理]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_user_identity/)
 
@@ -22,32 +22,32 @@ BrazeとShopifyの統合ドキュメントの一部を更新した：
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-カタログを使った[在庫切れ通知と]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications/)キャンバスを組み合わせることで、顧客に商品の在庫切れを通知することができる。顧客が選択したカスタムイベントを実行するたびに、その商品が補充されたときに通知されるように自動的に購読することができる。
+カタログとキャンバスによる[再入荷通知]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications/)を組み合わせて使用​​することで、商品の再入荷時に顧客に通知できます。選択されたカスタムイベントを実行した顧客が、商品の補充時に通知を受け取れるよう自動的に配信登録できます。
 
 ### カタログセグメント
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-[カタログ・セグメントは]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/catalog_segments/)、SQL Segment Extensionsのカタログ・データに基づくユーザーのオーディエンスである。これらのSQLセグメントエクステンションは、セグメントで参照され、キャンペーンやキャンバスでターゲットにすることができる。カタログセグメントは、SQL を使用して、カタログのデータとカスタムイベントまたは購入のデータとを結合します。これを行うには、カタログとカスタムイベントまたは購入に共通の識別子フィールドが必要です。
+[カタログセグメント]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/catalog_segments/)は、SQL セグメントエクステンションのカタログデータに基づくユーザーのオーディエンスです。これらのSQLセグメントエクステンションは、セグメントで参照され、キャンペーンやキャンバスでターゲットにすることができる。カタログセグメントは、SQL を使用して、カタログのデータとカスタムイベントまたは購入のデータとを結合します。これを行うには、カタログとカスタムイベントまたは購入に共通の識別子フィールドが必要です。
 
 ### Firebase Cloud Messaging API への移行
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-Googleの非推奨Cloud Messaging APIから、完全にサポートされたFirebase Cloud Messaging (FCM) APIに[移行する方法を]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/)学ぶ。
+Google の廃止予定の Cloud Messaging API から、完全にサポートされている Firebase Cloud Messaging (FCM) API への[移行方法]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/)について説明します。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Swift SDK 7.5.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
-    - `BrazeKit` 、`BrazeLocation` 、Brazeのデータ収集ポリシーを説明するプライバシー・マニフェストを追加する。詳細については、プライバシー・マニフェストに関するAppleの[文書を](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests)参照のこと。データ収集の慣行を管理するためのより多くの設定は、将来のリリースで利用可能になる予定である。
+    - `BrazeKit`および`BrazeLocation`のプライバシーマニフェストを追加して、Brazeのデータ収集ポリシーを説明します。詳細については、プライバシー・マニフェストに関するAppleの[文書を](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests)参照のこと。データ収集プラクティスを管理するためのその他の設定は、今後のリリースで利用できるようになります。
     - 7.1.0で導入されたXCFrameworksのコード署名に関する問題を修正した。
 - [Web SDK v5.1.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - [Unity SDK 5.0.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
-    - ネイティブiOSブリッジをBraze Swift SDK 6.1.0から7.4.0に更新。
-        - iOSリポジトリーのリンクは、この[リポジトリーから](https://github.com/braze-inc/braze-swift-sdk-prebuilt-dynamic)ビルド済みのダイナミックXCFrameworksを指すようになった。
-    - ネイティブAndroidブリッジをBraze Android SDK 27.0.1から29.0.1に更新。
+    - ネイティブ iOS ブリッジを Braze Swift SDK 6.1.0から7.4.0に更新しました。
+        - iOS リポジトリリンクが、この[リポジトリ](https://github.com/braze-inc/braze-swift-sdk-prebuilt-dynamic)から事前構築済みのダイナミック XCFramework を指すようになりました。
+    - ネイティブ Android ブリッジを Braze Android SDK 27.0.1から29.0.1に更新しました。
     - `AppboyBinding.GetFeatureFlag(string id)` は、featureフラグが存在しない場合、`null` を返すようになった。
-    - `FEATURE_FLAGS_UPDATED` は、リフレッシュリクエストが成功または失敗で完了したとき、および現在のセッションから以前にキャッシュされたデータがあった場合は最初のサブスクリプションのときにのみトリガーする。
+    - `FEATURE_FLAGS_UPDATED` は、更新リクエストが成功または失敗して完了したとき、および現在のセッションから過去にキャッシュされたデータがあった場合の初回のサブスクリプション時にのみトリガーされます。
 
diff --git a/_lang/ja/_help/release_notes/2024/2_6_24.md b/_lang/ja/_help/release_notes/2024/2_6_24.md
index 44c87df0cf3..f1dc61d5d32 100644
--- a/_lang/ja/_help/release_notes/2024/2_6_24.md
+++ b/_lang/ja/_help/release_notes/2024/2_6_24.md
@@ -3,55 +3,55 @@ nav_title: 2024年2月6日
 page_order: 11
 noindex: true
 page_type: update
-description: "この記事には、2024年2月6日のリリースノートが含まれている。"
+description: "この記事には2024年6月2日のリリースノートが含まれています。"
 ---
 
 # 2024年2月6日リリース
 
-## プライバシー・マニフェスト
+## Brazeのプライバシーマニフェスト
 
-Brazeは、宣言されたトラッキングデータを自動的に専用の`-tracking` エンドポイントにリルートする新しい柔軟なAPIとともに、独自のプライバシー・マニフェストをリリースした。詳細については、[Brazeのプライバシー・マニフェストを]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest)参照のこと。
+Brazeは、宣言されたトラッキングデータを自動的に専用の`-tracking` エンドポイントにリルートする新しい柔軟なAPIとともに、独自のプライバシー・マニフェストをリリースした。詳細については、[Brazeのプライバシーマニフェスト]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest)を参照してください。
 
-## Google EUユーザー同意ポリシー
+## Google EU ユーザー同意ポリシー
 
-グーグルは、2024年3月6日に施行される[デジタル市場法（DMA](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)）の変更に対応するため、[EUユーザー同意ポリシーを](https://www.google.com/about/company/user-consent-policy/)更新している。この新たな変更により、広告主はEEAおよび英国のエンドユーザーに特定の情報を開示し、彼らから必要な同意を得る必要がある。今度の変更の一環として、[Brazeで両方の同意シグナルをカスタム属性として収集する]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)ことができる。Brazeは、これらのカスタム属性のデータをGoogleの適切な同意フィールドに同期する。
+Google は、2024年3月6日に発効した[デジタル市場法 (DMA)](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html) の変更に対応して、[EU ユーザー同意ポリシー](https://www.google.com/about/company/user-consent-policy/)を更新します。この新しい変更により、広告主は EEA および英国のエンドユーザーに特定の情報を開示し、必要な同意を得る必要があります。予定されているこの変更の一環として、[Braze で両方の同意シグナルをカスタム属性として収集]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)できるようになります。Brazeは、これらのカスタム属性のデータをGoogleの適切な同意フィールドに同期する。
 
 ## データの柔軟性
 
-### Google Firebase Cloud Messaging (FCM) API
+### Google Firebase クラウドメッセージング(FCM) API
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[Googleの非推奨Cloud Messaging APIから、完全にサポートされたFirebase Cloud Messaging (FCM) APIに移行]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/)できるようになった。 
+[Google の廃止予定の Cloud Messaging API から、完全にサポートされている Firebase Cloud Messaging (FCM) API への移行]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/)が可能になります。 
 
-### Braze Cloud Data Ingestion（CDI）エンドポイント
+### Braze クラウドデータ取り込み (CDI) エンドポイント
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-BrazeのCDIエンドポイントを使用する：
+Braze CDI エンドポイントを使用して、以下を実行します。
 - [既存の統合のリストを返す]({{site.baseurl}}/api/endpoints/cdi/get_integration_list/)。
 - 指定した統合の[過去の同期ステータスのリストを返す]({{site.baseurl}}/api/endpoints/cdi/get_job_sync_status/)。
 - 指定した統合の[同期をトリガーする]({{site.baseurl}}/api/endpoints/cdi/post_job_sync/)。
 
-### Braze Cloud Data Ingestion (CDI)がDatabricksをサポートする。
+### Braze クラウドデータ取り込み (CDI) での Databricks のサポート
 
-カタログのBraze CDIサポートが[Databricksソースで]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/sync_catalogs_data/#step-2-integrate-cloud-data-ingestion-with-catalog-data)利用可能になった。
+Braze CDI で、[Databricks ソース]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/sync_catalogs_data/#step-2-integrate-cloud-data-ingestion-with-catalog-data)がカタログのサポートの対象なりました。
 
 ### 手動によるSwift SDKの統合
 
-パッケージマネージャを使用せずに手動でSwift SDKを統合する方法を説明するために、統合ガイドに[手動統合の]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration)記事を追加した。
+[手動統合]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration)記事を統合ガイドに追加し、パッケージマネージャーを使用せずにSwift SDKを手動で統合する方法について説明しました。
 
 ## 非推奨
 
 2024年1月11日、BrazeはWindowsアプリとBaiduアプリからのメッセージ配信とデータ収集を停止した。
 
-## 創造性を解き放つ
+## 創造性を引き出す
 
 ### SQLセグメント拡張の使用例
 
-[SQL Segment Extensionsユースケースライブラリには]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/use_cases)、SQL Segment Extensionsのテスト済みクエリが含まれており、独自のSQLクエリを作成する際のインスピレーションとして利用できる。
+[SQL セグメントエクステンションユースケース]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/use_cases)ライブラリに、独自の SQL クエリの作成時にヒントとして使用できる SQL セグメントエクステンション用のテスト済みクエリが含まれています。
 
-## ロバスト・チャンネル
+## 強力なチャネル
 
 ### カスタム・コード・ブロック
 
@@ -67,56 +67,56 @@ BrazeのCDIエンドポイントを使用する：
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-電子メールメッセージに[BCCアドレスを]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/?tab=bcc%20address#outbound-email-settings)付加することができる。これは、あなたのユーザーが受信したメッセージの同一コピーを、あなたのBCC受信トレイに送信する。これにより、コンプライアンス要件やカスタマーサポートの問題のために、ユーザーに送信したメッセージのコピーを保持することができる。
+電子メールメッセージに[BCCアドレスを]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/?tab=bcc%20address#outbound-email-settings)付加することができる。これにより、ユーザーが受信したメッセージの同じコピーがBCC 受信トレイに送信されます。これにより、コンプライアンス要件やカスタマーサポートの問題のために、ユーザーに送信したメッセージのコピーを保持することができる。
 
 ### ワンクリックでメール配信を停止できるリンク
 
 [list-unsubscribeヘッダーを]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#list-unsubscribe-header)使用すると、メール本文ではなく、メールボックスのUI内に**配信停止**ボタンを表示することで、受信者がマーケティングメールからワンクリックで配信停止できるようになる。
 
-## 新Braze提携
+## Braze の新しいパートナーシップ
 
-### Criteo - キャンバス・オーディエンス・シンク
+### Criteo - キャンバスオーディエンス同期
 
-[CriteoへのBraze Audience Syncを]({{site.baseurl}}/partners/canvas_steps/criteo_audience_sync/)使用することで、ブランドは、自社のBrazeインテグレーションからCriteoの顧客リストにユーザーデータを追加し、行動トリガーやセグメンテーションなどに基づいて広告を配信することができる。ユーザーデータに基づいてBraze Canvasでメッセージ（プッシュ、Eメール、SMS、ウェブフックなど）をトリガーするために通常使用するあらゆる基準を、Criteoの顧客リストでそのユーザーに広告をトリガーするために使用できるようになった。
+[Braze Criteo へのオーディエンス同期]({{site.baseurl}}/partners/canvas_steps/criteo_audience_sync/) を使用すると、ブランドは独自の Braze 統合からのユーザーデータを Criteo の顧客リストに追加して、行動トリガーやセグメンテーションなどに基づいて広告を配信できます。ユーザーデータに基づいて Braze キャンバスでメッセージをトリガーするために通常使用する基準 (プッシュ、メール、SMS、Webhook など) を、Criteo 顧客リスト内の該当ユーザーに対して広告をトリガーするために使用できるようになりました。
 
-### ムーバブル・インク - ダイナミック・コンテンツ
+### Movable Ink - ダイナミックコンテンツ
 
-[Movable Ink]({{site.baseurl}}/partners/message_personalization/dynamic_content/movable_ink#movable-ink)Customer Data API統合により、マーケティング担当者はBrazeに保存されている顧客イベントデータを有効化して、Movable Ink内でパーソナライズされたコンテンツを生成することができる。
+[Movable Ink]({{site.baseurl}}/partners/message_personalization/dynamic_content/movable_ink#movable-ink) 顧客データ API の統合により、マーケターは Braze に保存されている顧客イベントデータをアクティブ化して、Movable Ink 内でパーソナライズされたコンテンツを生成できます。
 
-### スキューバ・アナリティクス - 分析
+### Scuba Analytics - 分析
 
-[Scuba Analyticsは]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/scuba#scuba-analytics)、高速時系列データ用に設計された、フルスタックの機械学習機能付きデータ・コラボレーション・プラットフォームである。Scubaでは、ユーザー（アクターとも呼ばれる）を選択的にエクスポートし、Brazeプラットフォームにロードすることができる。スクーバでは、カスタムのアクター・プロパティを使って行動傾向を分析し、さまざまなプラットフォームでデータを活性化し、機械学習を使って予測モデリングを行う。
+[Scuba Analyticsは]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/scuba#scuba-analytics)、高速時系列データ用に設計された、フルスタックの機械学習機能付きデータ・コラボレーション・プラットフォームである。Scubaでは、ユーザー（アクターとも呼ばれる）を選択的にエクスポートし、Brazeプラットフォームにロードすることができる。Scuba では、カスタムアクタープロパティを使用して動作トレンドを分析し、さまざまなプラットフォーム間でデータを有効化し、マシンラーニングを使用して予測モデリングを実行します。
 
 ## SDKのアップデート
  
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
  
-- [Expo プラグイン 2.0.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
-    - [Expo SDK 50の要件に従い](https://expo.dev/changelog/2024/01-18-sdk-50)、iOSの最小プラットフォームバージョンを`13.4` 。
-    - このバージョンでは、Expo SDK 50を完全にサポートするために、Braze React Native SDKのバージョン[8.3.0以上が](https://github.com/braze-inc/braze-react-native-sdk/releases/tag/8.3.0)必要である。
+- [Expo プラグイン2.0.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+    - [Expo SDK 50の要件](https://expo.dev/changelog/2024/01-18-sdk-50)に従って、iOSの最低プラットフォームバージョンを`13.4`に上げます。
+    - このバージョンでは、Expo SDK 50を完全にサポートするために、Braze React Native SDK のバージョン[8.3.0以上](https://github.com/braze-inc/braze-react-native-sdk/releases/tag/8.3.0)が必要です。
 - [React Native SDK 8.3.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.3.0/CHANGELOG.md)
 - [Unity SDK 5.1.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
 - [Android SDK 30.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
-    - アプリ内メッセージに使用されるWebViewが更新され、`WebViewAssetLoader` を使用するようになった。
-        - `WebSettings.allowFileAccess` `InAppMessageHtmlBaseView` と`BrazeWebViewActivity` では false に設定されている。
+    - アプリ内メッセージに使用される WebView が、`WebViewAssetLoader`を使用するために更新されました。
+        - `InAppMessageHtmlBaseView` と `BrazeWebViewActivity` で、`WebSettings.allowFileAccess` が False に設定されました。
         - 独自の`InAppMessageWebViewClient` または`InAppMessageHtmlBaseView` を使用している場合は、オリジナルのクラスと比較して、実装が正しくアセットをロードしていることを確認してほしい。
         - カスタム・クラスを使用していない場合は、すべてが以前と同じように機能する。
 - [Braze Swift SDK 6.6.2](https://github.com/braze-inc/braze-swift-sdk/blob/6.6.2/CHANGELOG.md)
 - [Braze Swift SDK 7.6.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0)
 - [Xamarin SDKバージョン3.0.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
-    - NuGetパッケージは、`AppboyPlatformXamariniOSBinding` から次のように名前が変更された。 [`BrazePlatform.BrazeiOSBinding`](https://www.nuget.org/packages/BrazePlatform.BrazeiOSBinding/).
-        - 更新されたパッケージを使用するには、using`AppboyPlatformXamariniOSBinding;` をusing Brazeに置き換える；
-    - このバージョンでは、.NET 6+を使用する必要があり、Xamarinフレームワークを使用するプロジェクトのサポートは削除された。[マイクロソフトのポリシー](https://dotnet.microsoft.com/en-us/platform/support/policy/xamarin)のXamarinサポート終了に関する情報をご覧ください。
-    - Androidバインディングを[Braze Android SDK 26.3.2から29.0.1に](https://github.com/braze-inc/braze-android-sdk/compare/v26.3.1...v29.0.1#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+    - NuGet パッケージの名前が`AppboyPlatformXamariniOSBinding` から[`BrazePlatform.BrazeiOSBinding`](https://www.nuget.org/packages/BrazePlatform.BrazeiOSBinding/) に変更されました。
+        - 更新されたパッケージを使用するには、`AppboyPlatformXamariniOSBinding;` を使用するすべてのインスタンスを Braze を使用ように置き換えます。
+    - このバージョンでは、NET 6以降を使用する必要があり、Xamarin フレームワークを使用するプロジェクトのサポートが削除されます。Xamarinのサポート終了前後の[Microsoftのポリシー](https://dotnet.microsoft.com/en-us/platform/support/policy/xamarin)を参照してください。
+    - Android バインドを [Braze Android SDK 26.3.2から29.0.1](https://github.com/braze-inc/braze-android-sdk/compare/v26.3.1...v29.0.1#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)に更新しました。
 - [Xamarin SDK 4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
-    - このバージョンは、[Braze Swift SDKを](https://github.com/braze-inc/braze-swift-sdk/)使用するためにiOSバインディングを更新する。ほとんどのiOSパブリックAPIが変更されたため、使用するAPIの変更については、[移行ガイド](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/appboy-migration-guide/)（Swift）を参照されたい。私たちは、古いパブリックAPIを使い続けるための互換バインディングを提供している。
+    - このバージョンは、[ Braze Swift SDK](https://github.com/braze-inc/braze-swift-sdk/) を使用するためにiOS バインドを更新します。ほとんどのiOSパブリックAPIが変更されたため、使用するAPIの変更については、[移行ガイド](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/appboy-migration-guide/)（Swift）を参照されたい。私たちは、古いパブリックAPIを使い続けるための互換バインディングを提供している。
         - iOSバインディングは現在、複数のモジュールで構成されている：
-            - **BrazeKitだ：**アナリティクスとプッシュ通知のサポートを提供する主なSDKライブラリ（nuget： [Braze.iOS.BrazeKit](https://www.nuget.org/packages/Braze.iOS.BrazeKit)).
-            - BrazeUIである：Brazeが提供するアプリ内メッセージとコンテンツカード用のユーザーインターフェイスライブラリ（nuget： [Braze.iOS.BrazeUI](https://www.nuget.org/packages/Braze.iOS.BrazeUI)).
-            - ブレイズロケーション位置情報解析とジオフェンス監視をサポートする位置情報ライブラリ（nuget： [Braze.iOS.BrazeLocation](https://www.nuget.org/packages/Braze.iOS.BrazeLocation)).
+            - **BrazeKit:**アナリティクスとプッシュ通知のサポートを提供する主なSDKライブラリ（nuget： [Braze.iOS.BrazeKit](https://www.nuget.org/packages/Braze.iOS.BrazeKit)).
+            - BrazeUI:Brazeが提供するアプリ内メッセージとコンテンツカード用のユーザーインターフェイスライブラリ（nuget： [Braze.iOS.BrazeUI](https://www.nuget.org/packages/Braze.iOS.BrazeUI)).
+            - BrazeLocation:位置情報解析とジオフェンス監視をサポートする位置情報ライブラリ（nuget： [Braze.iOS.BrazeLocation](https://www.nuget.org/packages/Braze.iOS.BrazeLocation)).
             - BrazeKitCompat：4.0.0以前のAPIをサポートする互換ライブラリ（nuget： [Braze.iOS.BrazeKitCompat](https://www.nuget.org/packages/Braze.iOS.BrazeKitCompat)).
             - BrazeUICompat：4.0.0以前のUI APIをサポートする互換ライブラリ（nuget： [Braze.iOS.BrazeUICompat](https://www.nuget.org/packages/Braze.iOS.BrazeUICompat)).
         - 新しい統合についてはBrazeiOSMauiSampleAppを、互換モジュールの使用法についてはBrazeiOSMauiCompatSampleAppを参照のこと。
-    - iOSバインディングを[Braze Swift SDK 7.6.0に](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0)更新。
-    - iOSバインディングでは、Xcode 15との互換性のために.NET 7を使用する必要がある。
+    - iOS バインドを[Braze Swift SDK 7.6.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0) に更新しました。
+    - iOS バインドでは、Xcode 15との互換性を確保するために、NET 7を使用する必要があります。
 - [Xamarin SDK 4.0.1](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
diff --git a/_lang/ja/_help/release_notes/2024/3_5_24.md b/_lang/ja/_help/release_notes/2024/3_5_24.md
index ce7d2fd037e..d261c3488d5 100644
--- a/_lang/ja/_help/release_notes/2024/3_5_24.md
+++ b/_lang/ja/_help/release_notes/2024/3_5_24.md
@@ -8,9 +8,9 @@ description: "この記事には2024年3月5日のリリースノートが含ま
 
 # 2024年3月5日発売
 
-## Google EU ユーザー Consent Policy
+## Google EU ユーザー同意ポリシー
 
-Googleは、2024年3月6日から施行される[デジタル市場法（DMA）](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)の変更に対応して、[EUユーザー同意ポリシー](https://www.google.com/about/company/user-consent-policy/)を更新しています。この新しい変更により、広告主はEEAおよび英国のエンドユーザーに特定の情報を開示し、必要な同意を得る必要があります。この今後の変更の一環として、Brazeで両方の同意シグナルをカスタム属性として[収集することができます]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)。Brazeは、これらのカスタム属性からのデータをGoogleの適切な同意フィールドに同期します。
+Googleは、2024年3月6日から施行される[デジタル市場法（DMA）](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)の変更に対応して、[EUユーザー同意ポリシー](https://www.google.com/about/company/user-consent-policy/)を更新しています。この新しい変更により、広告主は EEA および英国のエンドユーザーに特定の情報を開示し、必要な同意を得る必要があります。この今後の変更の一環として、Brazeで両方の同意シグナルをカスタム属性として[収集することができます]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)。Brazeは、これらのカスタム属性からのデータをGoogleの適切な同意フィールドに同期します。
 
 ## データの柔軟性
 
@@ -18,37 +18,37 @@ Googleは、2024年3月6日から施行される[デジタル市場法（DMA）]
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-Brazeのダッシュボードで、キャンペーンとCanvasの効果を最大化するために[重複するユーザーを検索して統合することができます]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users)。ユーザープロファイルを個別にマージするか、一括マージを実行して、識別子が一致するすべてのプロファイルを最新のユーザープロファイルにマージすることができます。
+Braze ダッシュボードで、[重複ユーザーを検索してマージ]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users)し、キャンペーンとキャンバスの効果を最大化できるようになりました。ユーザープロファイルを個別にマージすることも、識別子が一致するすべてのプロファイルを最近更新されたユーザープロファイルにマージする一括マージを実行することもできます。
 
 ### アーカイブされたコンテンツを検索
 
-Brazeのダッシュボードでは、[検索結果にアーカイブされたコンテンツを含めることができます]({{site.baseurl}}/user_guide/administrative/access_braze/global_search/#filter-for-archived-content)。**アーカイブされたコンテンツを表示**を選択してください。
+Braze ダッシュボードで、[アーカイブされた内容を検索結果]({{site.baseurl}}/user_guide/administrative/access_braze/global_search/#filter-for-archived-content)に含めるには、**アーカイブされた内容を表示**を選択します。
 
-### AWS S3およびGoogle Cloud Storageのメッセージアーカイブサポート
+### AWS S3および Google Cloud Storage のメッセージアーカイブサポート
 
-メッセージアーカイブ[を使用して]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/)、ユーザーに送信されたメッセージのコピーを保存し、アーカイブまたはコンプライアンスの目的でAWS S3バケット、Azure Blob Storageコンテナ、またはGoogle Cloud Storageバケットに保存できます。
+[メッセージのアーカイブ]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/)を使用すると、アーカイブやコンプライアンスの目的で、ユーザーに送信したメッセージのコピーを AWS S3バケット、Azure Blob Storage コンテナー、または Google Cloud Storage バケットに保存できます。
 
 ### SQL テーブルリファレンス
 
 [SQL テーブルリファレンス]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/sql_segments_tables/) を訪問して、クエリビルダーでクエリを実行する際や SQL セグメントエクステンションを生成する際に利用可能なテーブルと列を確認してください。
 
-## 創造性の解放
+## 創造性を引き出す
 
 ### AIコピーライティングのトーンコントロール
 
 これで、AIコピーライティングアシスタントで生成されたコピーのスタイルを決定するために[メッセージトーン]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/#steps)を選択できるようになりました。
 
-## 堅牢なチャネル
+## 強力なチャネル
 
 ### カード作成
 
 Brazeがオーディエンスの適格性とパーソナライゼーションを評価するタイミングを選択できます。新しいコンテンツカードキャンペーンおよびキャンバスステップの場合、カードが[作成されたとき]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/)に指定します。 
 
-### プレビュー ユーザー パス
+### ユーザーパスのプレビュー
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-ユーザーのために作成したキャンバスの旅を体験し、受け取るタイミングとメッセージをプレビューします。これらの[テスト実行]({{site.baseurl}}/preview_user_paths/)は、キャンバスを送信する前に、メッセージが正しいオーディエンスに送信されることを保証する品質保証として機能します。
+ユーザー用に作成したキャンバスジャーニーを体験しましょう。これには、受信するタイミングやメッセージのプレビューも含まれます。これらの[テスト実行]({{site.baseurl}}/preview_user_paths/)は、キャンバスを送信する前に、メッセージが適切なオーディエンスに送信されているかどうかの品質保証として機能します。
 
 ### クイックプッシュキャンペーン
 
@@ -56,7 +56,7 @@ Brazeがオーディエンスの適格性とパーソナライゼーションを
 
 Brazeでプッシュキャンペーンを作成する際に、複数のプラットフォームとデバイスを選択して、[クイックプッシュ]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/quick_push/)と呼ばれる単一の編集体験で、すべてのプラットフォームに対して1つのメッセージを作成できます。この機能はキャンペーンでのみ利用可能です。
 
-### カスタムリスト配信停止ヘッダー
+### カスタムの list-unsubscribe ヘッダー
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
@@ -70,7 +70,7 @@ Brazeでプッシュキャンペーンを作成する際に、複数のプラッ
 
 ### 実験パスのパスをランダム化する
 
-常に実験パスステップの[パス割り当てをランダム化する]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step)には、ステップで**実験パスのランダム化されたパス**を選択します。このオプションは、勝者パスまたはパーソナライズされたパスを用いる場合は使用できません。
+実験パスの[パス割り当てステップを常にランダム化]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step)するには、ステップで \[**実験パスのランダムパス**] を選択します。このオプションは、勝者パスまたはパーソナライズされたパスを用いる場合は使用できません。
 
 ### メールキャプチャフォーム
 
@@ -78,10 +78,10 @@ Brazeでプッシュキャンペーンを作成する際に、複数のプラッ
 
 ## SDKの更新
  
-以下のSDKアップデートがリリースされました。以下に重大な更新が記載されています。その他の更新については、対応するSDKの変更ログを確認してください。
+以下のSDKアップデートがリリースされました。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [AppboyKit iOS SDK 4.7.0](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.7.0)
-    - これは、2024年3月1日にサポート終了となる前のObjective-C SDKの最終リリースとなります（[Swift SDK](https://github.com/braze-inc/braze-swift-sdk/)の使用を推奨します）。
+    - これは、2024年3月1日のサポート終了前の Objective-C SDK の最終リリースとなります ([Swift SDK](https://github.com/braze-inc/braze-swift-sdk/) の使用を優先)。
     - SDWebImageの必要最低バージョンを5.8.2から5.18.7に更新します。このバージョンには、[プライバシーに影響を与えるSDKのリスト](https://developer.apple.com/support/third-party-SDK-requirements/)に表示されるSDWebImageのプライバシーマニフェストが含まれています。
 - [Flutter SDK 8.1.0](https://pub.dev/packages/braze_plugin/changelog)
 - [Unity 5.2.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
@@ -91,11 +91,11 @@ Brazeでプッシュキャンペーンを作成する際に、複数のプラッ
 - [Android SDK 30.1.0-30.2.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
 - [Web SDK 5.1.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - [Cordova SDK 8.0.0-Cordova SDK 8.1.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
-    - ネイティブAndroidブリッジを[Braze Android SDK 27.0.1から30.0.0に](https://github.com/braze-inc/braze-android-sdk/compare/v27.0.0...v30.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
-    - ネイティブiOSブリッジを[Braze SWIFT SDK 6.6.0から7.6.0に更新しました](https://github.com/braze-inc/braze-swift-sdk/compare/6.6.0...7.6.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)。
+    - ネイティブ Android ブリッジを [Braze Android SDK 27.0.1から30.0.0に](https://github.com/braze-inc/braze-android-sdk/compare/v27.0.0...v30.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
+    - ネイティブ iOS ブリッジを [Braze Swift SDK 6.6.0から7.6.0に](https://github.com/braze-inc/braze-swift-sdk/compare/6.6.0...7.6.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
     - `Banner` コンテンツカードタイプの名前を`ImageOnly`に変更しました:
-        - `ContentCardTypes.BANNER`から`ContentCardTypes.IMAGE_ONLY`まで
-        - Android では、プロジェクト内の XML ファイルに Content Cards のバナーという単語が含まれている場合は、`image_only` に置き換える必要があります。
-    - `BrazePlugin.getFeatureFlag(id)` は、フィーチャーフラグが存在しない場合、`null` を返します。
-    - `BrazePlugin.subscribeToFeatureFlagsUpdates(function)` は、リフレッシュリクエストが成功または失敗で完了したとき、そして現在のセッションから以前にキャッシュされたデータがあった場合に初回のサブスクリプション時にのみトリガーされます。
+        - `ContentCardTypes.BANNER` から `ContentCardTypes.IMAGE_ONLY`
+        - Android では、プロジェクトのXML ファイルにコンテンツカードの単語バナーが含まれている場合は、`image_only` に置き換える必要があります。
+    - フィーチャーフラグが存在しない場合、`BrazePlugin.getFeatureFlag(id)` は `null` を返します。
+    - `BrazePlugin.subscribeToFeatureFlagsUpdates(function)` は、更新リクエストが成功または失敗して完了したとき、および現在のセッションから過去にキャッシュされたデータがあった場合の初回のサブスクリプション時にのみトリガーされます。
     - 非推奨のメソッド`registerAppboyPushMessages`を削除しました。代わりに`setRegisteredPushToken`を使用してください。
diff --git a/_lang/ja/_help/release_notes/2024/4_2_24.md b/_lang/ja/_help/release_notes/2024/4_2_24.md
index 4854d76ae0a..b48b63d3f9b 100644
--- a/_lang/ja/_help/release_notes/2024/4_2_24.md
+++ b/_lang/ja/_help/release_notes/2024/4_2_24.md
@@ -11,11 +11,11 @@ page_type: reference
 
 ### 複数のビジネスアカウント
 
-これで、複数のWhatsApp 取引先およびサブスクリプショングループs をワークスペースごとに追加できます。完全なウォークスルーについては、[複数のWhatsApp取引先と電話番号]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups/)を参照してください。
+複数の WhatsApp Business アカウントと購読グループを各ワークスペースに追加できるようになりました。詳細な手順については、「[複数の WhatsApp ビジネスアカウントと電話番号]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups/)」を参照してください。
 
 ### 読み取り速度
 
-WhatsAppは、インドの消費者sから始まる新たなアプリ侵入をテストし、より価値ある体験を生み出し、企業のマーケティング対話とのエンゲージメントを最大化しています。これには、ある特定の時期に、ある企業から受け取るマーケティングの会話の回数を制限することも含まれます。これは、読まれにくい少数の会話から始まります。詳細については、[メタリソース]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/meta_resources/)を参照してください。
+WhatsApp では、企業のマーケティング会話により、価値の高い体験を創出し、エンゲージメントを最大にする新しい手法のテストが、インドの消費者を対象に開始されました。これには、ある特定の時期に、ある企業から受け取るマーケティングの会話の回数を制限することも含まれます。これは、読まれにくい少数の会話から始まります。詳細については、[メタリソース]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/meta_resources/)を参照してください。
 
 ## データの柔軟性
 
@@ -23,48 +23,48 @@ WhatsAppは、インドの消費者sから始まる新たなアプリ侵入を
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-S3 のクラウドデータインジェストを使用して、AWS アカウントの 1 つ以上の S3 バケットを Braze に直接統合できるようになりました。新規ファイルが S3 にパブリッシュされると、メッセージが SQS に投稿され、Braze のクラウドデータ取り込みがそれらの新規ファイルを取り込みます。詳細については、[ファイルストレージの統合]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/file_integrations/)を参照してください。
+S3 用のクラウドデータ取り込みを使用して、AWS アカウントの 1 つ以上の S3 バケットを Braze と直接連携できるようになりました。新規ファイルが S3 にパブリッシュされると、メッセージが SQS に投稿され、Braze のクラウドデータ取り込みがそれらの新規ファイルを取り込みます。詳細については、[ファイルストレージの統合]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/file_integrations/)を参照してください。
 
-### Shopifyオー
+### Shopify OAuth
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
 Shopifyは、あらゆる規模の小売 (店)事業を始め、成長し、販売し、管理するための信頼できる道具を提供する世界的な大手商業企業です。Braze のShopifyを設定すると、[ワークスペース]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/) に対してOAuth を有効にできます。
 
-### エキスポをiOS プッシュ通知に使用
+### iOSプッシュ通知に Expo を使用する
 
-私たちは[豊富なプッシュ通知sとプッシュストーリーをReact Nativeでエキスポを使ってiOS アプリに統合するための命令]({{site.baseurl}}/developer_guide/platform_integration_guides/react_native/push_notifications/?tab=expo)を追加しました。
+React Nativeで Expo を使用して、リッチプッシュ通知とプッシュストーリーを iOS アプリに統合するための[手順を追加]({{site.baseurl}}/developer_guide/platform_integration_guides/react_native/push_notifications/?tab=expo)しました。
 
 ### iOS ライブアクティビティのリモート起動
 
-これで、[`/messages/live_activity/start` エンドポイント]({{site.baseurl}}/api/endpoints/messaging/live_activity/start/) を使用して、iOS でライブアクティビティをリモートで起動できます。フルウォークスルーについては、[ライブアクティビティを参照してください。Activity]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/#step-2-start-the-activity) を開始します。
+これで、[`/messages/live_activity/start` エンドポイント]({{site.baseurl}}/api/endpoints/messaging/live_activity/start/) を使用して、iOS でライブアクティビティをリモートで起動できます。詳細な手順については、「[ライブアクティビティ:アクティビティを開始する]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/#step-2-start-the-activity)」を参照してください。
 
-## 人工知能とML オートメーション
+## AI と ML のオートメーション
 
 ### 項目の推奨事項
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-Sage AI by Brazeを使用すると、最も人気のあるプロダクトを計算したり、特定のカタログのパーソナライズされた AI 推奨を作成したりできます。詳細については、[項目の推奨事項について]({{site.baseurl}}/user_guide/sage_ai/recommendations/about_item_recommendations/)を参照してください。
+Braze による Sage AI を使用すると、最も人気のある製品を計算したり、特定のカタログのパーソナライズされた AI レコメンデーションを作成したりできます。詳細については、[項目の推奨事項について]({{site.baseurl}}/user_guide/sage_ai/recommendations/about_item_recommendations/)を参照してください。
 
-### 品質保証アプリ内メッセージ内容
+### アプリ内メッセージコンテンツの QA
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-以前は、Braze ダッシュボードでSage AIを使用して、SMSとプッシュ通知内容の品質保証を実行することができました。これで、[QA アプリ内メッセージ content]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_content_qa/) もできます。
+以前は、Braze ダッシュボードで Sage AI を使用して SMS およびプッシュ通知コンテンツで品質保証を実行できました。[アプリ内メッセージコンテンツの QA]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_content_qa/) も実行できるようになりました。
 
-## 新Braze提携
+## Braze の新しいパートナーシップ
 
 ### Census - コホートインポート
 
-[コホート ユーザーをBrazeからCensus]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/census/)にインポートできるようになりました。これは、SnowflakeやBigQueryなどのクラウドデータウェアハウスをBrazeに接続するデータアクティベーションプラットフォームです。マーケティングチームは、ファーストパーティデータの力を解放してダイナミックな オーディエンス Segmentsを構築し、顧客 属性sを同期してキャンペーンsをパーソナライズし、すべてのデータをBrazeに最新の状態に保つことができます。
+[コホート ユーザーをBrazeからCensus]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/census/)にインポートできるようになりました。これは、SnowflakeやBigQueryなどのクラウドデータウェアハウスをBrazeに接続するデータアクティベーションプラットフォームです。マーケティングチームは、ファーストパーティデータの力を解き放ち、ダイナミックなオーディエンスセグメントを構築し、顧客属性を同期してキャンペーンをパーソナライズし、Braze 内の全てのデータを最新の状態に保つことができます。
 
 ## SDK 更新s
 
-以下のSDK 更新がリリースされました。ブレーク更新s を以下に示します。他のすべての更新s は、対応するSDK変更ログを確認することで見つけることができます。
+以下のSDK 更新がリリースされました。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [React Native 9.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
   - React Native の最小バージョンを0.71.0 に更新しました。
   - 最小iOSバージョンを12.0に更新しました。
-  - Braze スウィフトSDK 8.1.0 を使用するようにiOS バインディングを更新しました。
-  - Braze Android SDK 30.1.1 を使用するようにAndroidバインディングを更新しました。
+  - Braze Swift SDK 8.1.0を使用するように iOS バインディングを更新しました。
+  - Braze Android SDK 30.1.1を使用するように Android バインディングを更新しました。
diff --git a/_lang/ja/_help/release_notes/2024/4_30_24.md b/_lang/ja/_help/release_notes/2024/4_30_24.md
index fb2e0199ea0..a876a62490d 100644
--- a/_lang/ja/_help/release_notes/2024/4_30_24.md
+++ b/_lang/ja/_help/release_notes/2024/4_30_24.md
@@ -9,7 +9,7 @@ page_type: reference
 
 ## プロモーション・コード・リストを作成または更新する権限
 
-2024年4月以降、プロモーションコード一覧を作成・更新するには、「キャンペーン、キャンバス、カード、セグメント、メディアライブラリへのアクセス」権限が必要となる。権限名とその説明の一覧については、「[限定されたチーム・ロールの権限を管理する]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#managing-limited-and-team-role-permissions)」を参照のこと。
+2024年4月以降、プロモーションコード一覧を作成・更新するには、「キャンペーン、キャンバス、カード、セグメント、メディアライブラリへのアクセス」権限が必要となる。権限名とその説明のリストについては、[制限付きおよびチームロール権限の管理]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#managing-limited-and-team-role-permissions)を参照してください。
 
 ## データの柔軟性
 
@@ -17,31 +17,31 @@ page_type: reference
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-[ジャストインタイム・プロビジョニングは]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/saml_jit)SAML SSOと連動し、新規ダッシュボード・ユーザーが最初のサインイン時にBrazeアカウントを作成できるようにする。これにより、管理者は新しいダッシュボード・ユーザーのアカウントを手動で作成し、権限を選択し、ワークスペースに割り当て、アカウントを有効にするのを待つ必要がなくなる。
+[ジャストインタイムプロビジョニング]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/saml_jit)は、SAML SSO と連携して、新しいダッシュボードユーザーが初回サインイン時に Braze アカウントを作成できるようにします。これにより、管理者が新しいダッシュボード ユーザーのアカウントを手動で作成し、権限を選択してワークスペースに割り当て、アカウントの有効化を待機する必要がなくなります。
 
-### パーミッション・セットとロール
+### 権限セットとロール
 
-[パーミッション・セットを使って]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#permission-sets-and-roles)、特定のサブジェクト領域やアクションに関連するパーミッションを束ねる。これらの権限セットは、異なるワークスペース間で同じアクセスを必要とするダッシュボードユーザーに適用することができる。
+[パーミッション・セットを使って]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#permission-sets-and-roles)、特定のサブジェクト領域やアクションに関連するパーミッションを束ねる。これらの権限セットは、異なるワークスペースにわたって同じアクセス権を必要とするダッシュボードユーザーに適用できます。
 
-### クラウドデータ収集セグメント
+### クラウドデータ取り込みセグメント
 
-Braze[Cloud Data Ingestionセグメントを]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/cdi_segments)使用すると、CDI接続を介して利用可能になったデータを使用して、独自のデータウェアハウスに直接問い合わせるSQLを記述し、Braze内でターゲットとなるユーザーグループを作成することができる。
+Braze [クラウドデータ取り込みセグメント]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/cdi_segments)を使用すると、CDI 接続を介して利用可能なデータを使用して独自のデータウェアハウスを直接クエリする SQL を記述し、Braze 内でターゲットにできるユーザーグループを作成できます。
 
-## 創造性を解き放つ
+## 創造性の発揮
 
 ### クエリビルダーのテンプレート
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-Query Builderのテンプレートを使って、SnowflakeのBrazeデータを使ったレポートを作成できる。[クエリ・ビルダー・テンプレートに]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/)アクセスするには、レポート作成時に**クエリ・テンプレートを**選択する。すべてのテンプレートは過去60日までのデータを表示するが、エディターで直接その値や他の値を編集することができる。
+クエリービルダーテンプレートを使用して、Snowflake から Braze データを使用してレポートを作成できます。[クエリービルダー]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/)テンプレートにアクセスするには、レポートの作成時に**クエリテンプレート**を選択します。すべてのテンプレートは過去60日までのデータを表示するが、エディターで直接その値や他の値を編集することができる。
 
 ### セグメント別パフォーマンスデータ
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-クエリビルダーのレポートテンプレートで、キャンペーン、バリアント、キャンバス、キャンバスステップの[パフォーマンスデータをセグメント別に]({{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/#performance-data-by-segment)分解できる。
+クエリビルダーレポートテンプレートでは、キャンペーン、バリアント、キャンバス、キャンバスステップの[パフォーマンスデータをセグメント別に]({{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/#performance-data-by-segment)分類できます。
 
-## ロバスト・チャンネル
+## 強力なチャネル
 
 ### SMSメッセージの自動リンク短縮
 
@@ -49,34 +49,34 @@ Query Builderのテンプレートを使って、SnowflakeのBrazeデータを
 
 [自動リンク短縮]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/keyword_handling/?tab=manage%20responses#managing-keywords-and-auto-responses)機能を使って、回答中の静的URLを自動的に短縮する。文字数カウンタが更新され、短縮URLの予想される長さが表示されるからだ。
 
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
-### Friendbuy - ロイヤリティ
+### Friendbuy - ロイヤルティ
 
-Brazeと[Friendbuyの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/friendbuy/)統合を活用して、EメールやSMSの機能を拡張し、紹介やロイヤルティプログラムのコミュニケーションを簡単に自動化しよう。Brazeは、Friendbuyを通じて収集したオプトイン済みの電話番号の顧客プロファイルを作成する。
+Brazeと[Friendbuyの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/friendbuy/)統合を活用して、EメールやSMSの機能を拡張し、紹介やロイヤルティプログラムのコミュニケーションを簡単に自動化しよう。Braze では、Friendbuy 経由で収集されたすべてのオプトイン電話番号の顧客プロファイルが生成されます。
 
 ### NiftyImages - ダイナミックコンテンツ
 
-Brazeと[NiftyImagesの]({{site.baseurl}}/partners/message_personalization/dynamic_content/niftyimages/)パートナーシップにより、既存のBrazeパーソナライズタグをNiftyImagesのURLにマッピングすることで、メールキャンペーン用にダイナミックでパーソナライズされた画像を作成することができる。
+Braze と[NiftyImages]({{site.baseurl}}/partners/message_personalization/dynamic_content/niftyimages/) のパートナーシップにより、既存の Braze パーソナライゼーションタグを NiftyImages URL にマッピングすることで、メールキャンペーンのダイナミックでパーソナライズされた画像を作成できます。
 
 ## SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Android SDK 30.4.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
 - [Braze Segment Swift プラグイン 2.4.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md#240)
 - [Flutter SDK 9.0.0](https://pub.dev/packages/braze_plugin/changelog)
-    - ネイティブiOSブリッジを[Braze Swift SDK 7.7.0から8.4.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...8.4.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+    - ネイティブ iOS ブリッジを [Braze Swift SDK 7.7.0から8.4.0](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...8.4.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)に更新します。
         - iOSの最小デプロイメントターゲットは12.0に更新された。
-    - ネイティブAndroidブリッジを[Braze Android SDK 29.0.1から30.3.0に](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+    - ネイティブ Android ブリッジを [Braze Android SDK 29.0.1から30.3.0](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)に更新します。
     - サポートされるDartの最小バージョンは2.15.0である。
 - [React Native SDK 9.2.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
 - [Swift SDK 8.3.0-8.4.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
 - [Swift SDK 9.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
     - BrazeKitのプライバシーマニフェストからデフォルトのプライバシー追跡ドメインを削除する。
-        - Brazeの[データトラッキング機能を]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest/)使用している場合は、アプリレベルのプライバシーマニフェストにトラッキングエンドポイントを手動で追加する必要がある。
-        - 統合ガイダンスについては、更新された[チュートリアルを](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/e1-privacy-tracking)参照のこと。
+        - Braze [データトラッキング機能]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest/)を使用している場合は、トラッキングエンドポイントをアプリレベルのプライバシーマニフェストに手動で追加する必要があります。
+        - 統合の手引きについては、更新d [チュートリアル](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/e1-privacy-tracking)を参照してください。
     - 非推奨の`BrazeDelegate.braze(_:sdkAuthenticationFailedWithError) method in favor of BrazeSDKAuthDelegate.braze(_:sdkAuthenticationFailedWithError)` を削除する。
-        - このメソッドは[リリース5.14.](https://github.com/braze-inc/braze-swift-sdk/releases/tag/5.14.0)0で非推奨となった。
-        - 新しいデリゲート・メソッドへの切り替えに失敗しても、コンパイラー・エラーは発生しない。代わりに、あなたが定義した`BrazeDelegate.braze(_:sdkAuthenticationFailedWithError)` 。
+        - このメソッドは、元は[release 5.14.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/5.14.0) で非推奨になりました。
+        - 新しいデリゲートメソッドへの切り替えるに失敗しても、コンパイラエラーはトリガーされません。代わりに、定義した`BrazeDelegate.braze(_:sdkAuthenticationFailedWithError)` メソッドは単に呼び出されません。
 - [Xamarin SDKバージョン4.0.3](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md#403)
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2024/5_28_24.md b/_lang/ja/_help/release_notes/2024/5_28_24.md
index 2eaa63130a1..628b916e3f9 100644
--- a/_lang/ja/_help/release_notes/2024/5_28_24.md
+++ b/_lang/ja/_help/release_notes/2024/5_28_24.md
@@ -9,35 +9,35 @@ page_type: reference
 
 ## ドキュメントサイトの視覚的な更新
 
-ドキュメンテーションのウェブサイトが新しくなったことにお気づきだろうか！私たちは、新しい活気あるブレイズのブランド・アイデンティティを反映させるために、それを刷新した。新ブランドの舞台裏については、[Unveiling Our New Brandをご覧いただきたい：Braze エグゼクティブ・クリエイティブ・ディレクター グレッグ・エルデリとの対話](https://www.braze.com/resources/articles/unveiling-our-new-brand-a-conversation-with-braze-executive-creative-director-greg-erdelyi).
+ドキュメンテーションのウェブサイトが新しくなったことにお気づきだろうか！新しく生き生きとしたBrazeブランドアイデンティティを反映するように改良しました。新ブランドの舞台裏については、[Unveiling Our New Brandをご覧いただきたい：Braze クリエイティブディレクター Greg Erdelyi との会話](https://www.braze.com/resources/articles/unveiling-our-new-brand-a-conversation-with-braze-executive-creative-director-greg-erdelyi)。
 
 ## ポルトガル語とスペイン語をサポート
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-Brazeは現在、ポルトガル語とスペイン語に対応している。Brazeダッシュボードの表示言語を変更するには、[言語設定を]({{site.baseurl}}/user_guide/administrative/access_braze/language/)参照のこと。
+Brazeは現在、ポルトガル語とスペイン語に対応している。Braze ダッシュボード アプリが認識する言語を変更するには、[言語設定s]({{site.baseurl}}/user_guide/administrative/access_braze/language/)を参照してください。
 
-## ロバスト・チャンネル
+## 強力なチャネル
 
 ### 多言語設定
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[多言語設定を]({{site.baseurl}}/multi_language_support/)調整することで、異なる言語や地域のユーザーをターゲットに、1通のメールメッセージの中で異なるメッセージを送ることができる。多言語サポートを編集・管理するには、「多言語設定の管理」ユーザー権限が必要である。メッセージにロケールを追加するには、キャンペーンの編集権限が必要だ。
+[多言語設定を]({{site.baseurl}}/multi_language_support/)調整することで、異なる言語や地域のユーザーをターゲットに、1通のメールメッセージの中で異なるメッセージを送ることができる。多言語サポートを編集および管理するには、「多言語設定を管理」ユーザー権限が必要です。メッセージにロケールを追加するには、キャンペーンの編集権限が必要だ。
 
-### メッセージレベルのワンクリックリスト配信停止ヘッダー
+### メッセージレベルのワンクリックリスト-配信停止 ヘッダー
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-list-unsubscribeヘッダーのためのワンクリックunsubscribe[(RFC 8058](https://datatracker.ietf.org/doc/html/rfc8058))は、受信者が電子メールからオプトアウトする簡単な方法を提供する。このヘッダー設定は、メールのメッセージレベルで適用されるように調整できる。この設定の詳細については、[ワークスペースのメール配信停止ヘッダーを]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#email-unsubscribe-header-in-workspaces)参照のこと。
+list-unsubscribe ヘッダーのワンクリック配信停止 ([RFC 8058](https://datatracker.ietf.org/doc/html/rfc8058)) により、受信者がメールから簡単にオプトアウトできます。このヘッダー設定は、メールのメッセージレベルで適用されるように調整できる。この設定の詳細については、「[ワークスペースのメール配信停止ヘッダー]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#email-unsubscribe-header-in-workspaces)」を参照してください。
 
 ### 電子メールのサニタイズについて
 
 Brazeがメールメッセージ内の特定の種類のJavaScriptを検出した場合に発生する処理については、新しい[サニタイズの]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/sanitization)記事を参照。その主な目的は、悪質業者が他のBrazeダッシュボードユーザーのセッションデータにアクセスするのを防ぐことである。
 
-### コンテンツ・ブロックの包含数
+### コンテンツブロックの包含カウント
 
-アクティブなキャンペーンまたはキャンバスにコンテンツブロックを追加した後、コンテンツブロックにカーソルを合わせ、<i class="fa fa-eye preview-icon"></i> **プレビューアイコンを**選択すると、コンテンツブロックライブラリから[このコンテンツブロックをプレビューする]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/)ことができる。
+アクティブなキャンペーンまたはキャンバスにコンテンツブロックを追加した後、コンテンツブロックライブラリから[ このコンテンツブロック]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/) をプレビューするには、コンテンツブロックにマウスを合わせて<i class="fa fa-eye preview-icon"></i>**プレビュー** アイコンを選択します。
 
 ### キャンバスのステータス
 
@@ -51,51 +51,51 @@ Brazeのダッシュボードでは、キャンバスがステータスごとに
 
 AIコピーライティングアシスタントが生成するコピーのスタイルを、ブランドの声に合わせてカスタマイズするための[ブランドガイドラインを]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines/)作成し、適用できるようになった。シナリオごとに複数のガイドラインを設定し、常に文脈に合ったトーンになるようにする。
  
-## 新しいブレイズ・パートナーシップ
+## Braze の新しいパートナーシップ
 
-### アディクテフ - アナリティクス
+### Adikteev - 分析
 
-Brazeと[Adikteevの]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/adikteev/)統合により、Braze CRMキャンペーン内でAdikteevの解約予測技術を活用し、リスクの高いユーザーセグメントを優先的にターゲットにすることで、ユーザーリテンションを高めることができる。
+Braze と [Adikteev]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/adikteev/) の統合により、Braze CRM キャンペーン内で Adikteev の解約予測技術を活用し、リスクの高いユーザーセグメントを優先的にターゲットにすることで、ユーザーリテンションを高めることができます。
  
-### セレブラス - 分析
+### Celebrus - 分析
  
-Brazeと[Celebrusの]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/celebrus)統合は、WebとモバイルアプリのチャネルでBraze SDKとシームレスに統合され、チャネルの活動データをBrazeに取り込むことを容易にする。これには、特定期間におけるデジタル資産全体のビジター・トラフィックに関する包括的な洞察も含まれる。
+Braze と [Celebrus]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/celebrus) の統合により、Web アプリチャネルとモバイルアプリチャネルで Braze SDK とシームレスに統合され、チャネルアクティビティデータを Braze に取り込みやすくなります。これには、特定期間におけるデジタル資産全体のビジター・トラフィックに関する包括的な洞察も含まれる。
  
 ### IAM Studio - メッセージテンプレート
  
-Brazeと[IAM Studioの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/iam_studio/)統合により、カスタマイズ可能なアプリ内メッセージテンプレートをBrazeのアプリ内メッセージに簡単に挿入することができ、画像置換、テキスト変更、ディープリンク設定、カスタム属性、イベント設定を提供する。IAM Studioを使えば、メッセージ作成時間を短縮し、コンテンツプランニングにより多くの時間を割くことができる。
+Brazeと[IAM Studioの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/iam_studio/)統合により、カスタマイズ可能なアプリ内メッセージテンプレートをBrazeのアプリ内メッセージに簡単に挿入することができ、画像置換、テキスト変更、ディープリンク設定、カスタム属性、イベント設定を提供する。IAM Studio を使用すると、メッセージの作成時間を短縮し、コンテンツ計画により多くの時間を費やすことができます。
  
-### リーガル - インスタント・チャット
+### Regal - インスタントチャット
 
 Brazeと[Regalを]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/regal/)統合することで、すべての顧客接点において、より一貫性のあるパーソナライズされた体験を生み出すことができる。
 
-### トレジャーデータ - コーホートインポート
+### トレジャーデータ - コホートインポート
  
-Brazeと[Treasure Dataの]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/treasuredata/)統合により、Treasure DataからBrazeにユーザーコホートをインポートすることができる。
+Braze と[トレジャーデータ]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/treasuredata/)の統合により、トレジャーデータから Braze にユーザーコホートをインポートし、ウェアハウス内にのみ存在する可能性のあるデータに基づいてターゲットを絞ったキャンペーンを送信できるようになります。
  
 ### Zapier - ワークフローの自動化
  
-Brazeと[Zapierの]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/zapier/)パートナーシップは、Braze APIとBraze webhooksを活用してサードパーティアプリケーションと接続し、さまざまなアクションを自動化する。
+Braze と [Zapier]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/zapier/) のパートナーシップでは、Braze API と Braze Webhook を活用してサードパーティアプリケーションに接続し、さまざまなアクションを自動化します。
 
 ## SDKのアップデート
  
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
 
 - [Android SDK 31.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
 - [Braze Segment Swift プラグイン 3.0.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md#300)
-    - Braze Swift SDKバインディングを更新し、9.2.0+ SemVerのリリースを必要とするようにした。
-        - これにより、Braze SDKの9.2.0から10.0.0までのどのバージョンとも互換性がある。
-        - 潜在的な変更点の詳細については、[7.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#700)、[8.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#800)、[9.0.](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#900)0の変更履歴を参照のこと。
-    - プッシュ通知のサポートには、アプリのライフサイクルのできるだけ早い段階で、アプリケーションの`AppDelegate.application(_:didFinishLaunchingWithOptions:)` メソッドでスタティック・メソッド`BrazeDestination.prepareForDelayedInitialization()` を呼び出す必要がある。
+    - Braze Swift SDK バインディングを更新して、9.2.0+ SemVer 仕様のリリースを必要とするようにします。
+        - これにより、Braze SDK の9.2.0から10.0.0までのあらゆるバージョンとの互換性が確保されます (10.0.0は含まれません)。
+        - 破壊的な変更の可能性に関する詳細については、[7.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#700)、[8.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#800)、および[9.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#900)の変更ログエントリを参照してください。
+    - プッシュ通知のサポートでは、アプリケーションの `AppDelegate.application(_:didFinishLaunchingWithOptions:)` メソッドにおいて、アプリのライフサイクルのできるだけ早い段階で静的メソッド `BrazeDestination.prepareForDelayedInitialization()` を呼び出すことが必要になりました。
 - [Cordova SDK 9.0.0-9.2.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
-    - ネイティブiOSブリッジを[Braze Swift SDK 7.7.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
-- [Expo プラグイン 2.1.1](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md#211)
+    - ネイティブ iOS ブリッジを [Braze Swift SDK 7.7.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
+- [Expo プラグイン2.1.1](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md#211)
 - [Flutter SDK 10.1.0](https://pub.dev/packages/braze_plugin/changelog)
 - [React Native SDK 11.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/11.0.0/CHANGELOG.md)
 - [Swift SDK 9.1.0-9.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#920)
-- ユニティ 6.0.0
-    - ネイティブiOSブリッジを[Braze Swift SDK 7.7.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
-    - ネイティブAndroidブリッジを[Braze Android SDK 29.0.1から30.3.0に](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
+- Unity 6.0.0
+    - ネイティブ iOS ブリッジを [Braze Swift SDK 7.7.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
+    - ネイティブ Android ブリッジを [Braze Android SDK 29.0.1から30.3.0に](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
 - [Web SDK 5.3.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
 - Xamarin SDKバージョン5.0.0
-    - iOSバインディングを[Braze Swift SDK 8.4.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/8.4.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新。
\ No newline at end of file
+    - iOSバインディングを [Braze Swift SDK 8.4.0から9.0.0に](https://github.com/braze-inc/braze-swift-sdk/compare/8.4.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed)更新しました。
\ No newline at end of file
diff --git a/_lang/ja/_help/release_notes/2024/6_25_24.md b/_lang/ja/_help/release_notes/2024/6_25_24.md
index dad7a929396..3830f7ee23c 100644
--- a/_lang/ja/_help/release_notes/2024/6_25_24.md
+++ b/_lang/ja/_help/release_notes/2024/6_25_24.md
@@ -19,37 +19,37 @@ Braze Docsが日本語に対応した！
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[`/campaigns/trigger/send` エンド]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns)ポイントが添付ファイルをサポートするようになった（ちょうど`/messages/send` エンドポイントが電子メールの添付ファイルをサポートするように）。 
+[`/campaigns/trigger/send` エンドポイント]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns)で添付ファイルがサポートされるようになりました (`/messages/send` エンドポイントでメールの添付ファイルがサポートされるのと同様)。 
 
 ### データウェアハウスの追加サポート
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-Brazeの[Cloud Data Ingestion（CDI]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/connected_sources)）は、BigQuery、Databricks、Redshift、Snowflakeをサポートするようになった。
+Braze [クラウドデータ取り込み (CDI)]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/connected_sources) で、BigQuery、Databricks、Redshift、Snowflake がサポートされるようになりました。
 
 ### WhatsAppの電話番号移行
 
-WhatsAppビジネスアカウント間でWhatsApp電話番号を移行する。[WhatsAppの電話番号移行について]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration)もっと読む。
+Meta の埋め込みサインアップを使用して、WhatsApp Business アカウント間で WhatsApp の電話番号を移行します。[WhatsApp電話番号マイグレーション]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration)について詳しくお読みください。
  
-## 創造性を解き放つ
+## 創造性を引き出す
 
 ### デバイス別エンゲージメント
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-新レポート「**Engagement by Device**」は、ユーザーがどのデバイスを使ってメールに参加しているのかがわかる。このデータは、モバイル、デスクトップ、タブレット、その他のデバイスの種類を問わず、Eメールのエンゲージメントを追跡する。[レポートとEメールパフォーマンスダッシュボードの]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard)詳細はこちら。
+新レポート「**Engagement by Device**」は、ユーザーがどのデバイスを使ってメールに参加しているのかがわかる。このデータは、モバイル、デスクトップ、タブレット、および他のデバイスタイプのメールエンゲージメントを追跡します。[レポートと電子メールパフォーマンスダッシュボード]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard) について詳しく説明します。
 
 ### キャンバスフローのWhatsAppとSMSリキッドプロパティ
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[キャンバスフローにWhatsAppとSMSリキッドプロパティの]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties)サポートを追加した。アクションパスのステップが "Sent an SMS Inbound Message "または "Sent a WhatsApp Inbound Message "トリガーを含むとき、後続のキャンバスステップはSMSまたはWhatsApp Liquidプロパティを含むことができる。これは、Canvas Flowにおけるイベントプロパティの動作を反映している。こうすることで、メッセージを活用して、ユーザープロファイルや会話メッセージに関するファーストパーティデータを保存し、参照することができる。
+[WhatsAppおよびSMS Liquidプロパティーのサポートがキャンバスフロー]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties)に追加されました。アクションパスステップに \[SMS インバウンドメッセージを送信しました] または \[WhatsApp インバウンドメッセージを送信しました] トリガーが含まれている場合、後続のキャンバスステップに SMS または WhatsApp Liquid プロパティを含めることができるようになりました。これは、キャンバスフローでのイベントプロパティの動作を反映したものです。こうすることで、メッセージを活用して、ユーザープロファイルや会話メッセージに関するファーストパーティデータを保存し、参照することができる。
  
-### キャンバスに描かれたパーソナライズされた道
+### 繰り返されるキャンバスのパーソナライズされたパス
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-キャンバスのパーソナライズドパスでは、コンバージョンの可能性に基づいて、個々のユーザーに対してキャンバスのジャーニーの任意のポイントをパーソナライズすることができる。キャンバスにパーソナライズされたパスが追加された。[パーソナライズド・バリアントについて]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths)もっと知る。
+キャンバスのパーソナライズドパスでは、コンバージョンの可能性に基づいて、個々のユーザーに対してキャンバスのジャーニーの任意のポイントをパーソナライズすることができる。定期的なキャンバスでパーソナライズされたパスを使用できるようになりました。詳細については、[Personalized Variants]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths)を参照してください。
 
 ### セグメントのトラブルシューティング
 
@@ -61,13 +61,13 @@ WhatsAppビジネスアカウント間でWhatsApp電話番号を移行する。[
 
 ![]({% image_buster /assets/img/liquid_color_code.png %})
  
-## ロバスト・チャンネル
+## 強力なチャネル
 
-### SMSの地理的許可
+### SMS 地理的許可
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
-SMSの地理的許可は、あなたがSMSメッセージを送信することができる国の制御を強制することにより、セキュリティを強化し、詐欺的なSMSトラフィックから保護する。管理者は、承認された地域にのみSMSメッセージが送信されるように、国の許可リストを指定できるようになった。詳細については、[SMS地理的許可を]({{site.baseurl}}/sms_geographic_permissions)参照のこと。 
+SMSの地理的許可は、あなたがSMSメッセージを送信することができる国の制御を強制することにより、セキュリティを強化し、詐欺的なSMSトラフィックから保護する。管理者は、承認された地域にのみSMSメッセージが送信されるように、国の許可リストを指定できるようになった。詳細については、[SMS Geographic Permissions]({{site.baseurl}}/sms_geographic_permissions)を参照してください。 
 
 ![Country allowlist "ドロップダウンリストでは、最も一般的な国が一番上に表示される。][2]{: style="max-width:80%;"}
 
@@ -75,31 +75,31 @@ SMSの地理的許可は、あなたがSMSメッセージを送信すること
 
 オプトアウト監視やトラフィックポンプの推奨など、[Brazeを使ったSMS/MMSのベストプラクティスについて]({{site.baseurl}}/user_guide/message_building_by_channel/sms/best_practices/best_practices)詳しく知る。 
 
-### プッシュ配信の停止を追跡する
+### プッシュの配信停止をトラッキングする
 
 プッシュ配信の停止を追跡するためのヒントについては、新しい[ヘルプ記事を]({{site.baseurl}}/help/help_articles/push/push_unsubscribes)チェックしよう。
 
 ### Shopify`checkout.liquid` 非推奨
 
-Shopify`checkout.liquid` のサポートは2024年8月に非推奨となり、2025年8月に終了する。Braze がこの遷移 を処理する方法について詳しく説明します。[ 
+Shopify `checkout.liquid` は、2024年8月に非推奨になり、2025年8月に終了することにご注意ください。この変化に対する Braze の対応については、[こちら]({{site.baseurl}}/help/release_notes/deprecations/shopify_checkout)をご覧ください。 
 
 ## SDKのアップデート
  
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
  
 - [Swift SDK 9.3.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/9.3.0)
-    - 既存のFeature Flag APIは廃止され、将来のバージョンで削除される：
-        - `Braze.FeatureFlag.jsonStringProperty(key:)` は非推奨となった。
-        - `Braze.FeatureFlag.jsonObjectProperty(key:)` は非推奨となり、`Braze.FeatureFlag.jsonProperty(key:)` が採用された。
+    - 将来のバージョンで削除される既存のフィーチャーフラグ API を非推奨にします。
+        - `Braze.FeatureFlag.jsonStringProperty(key:)` は非推奨になりました。
+        - `Braze.FeatureFlag.jsonObjectProperty(key:)` は非推奨になり、`Braze.FeatureFlag.jsonProperty(key:)` に置き換えられした。
 - [Roku SDK 2.2.0](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md)
 - [Braze Expo プラグイン 2.1.2](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
 
 ### tvOSドキュメント
 
-数ヶ月前、[tvOSコンテンツカードと]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/tvos) [アプリ内メッセージングの]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/tvos)記事が誤って非推奨となった。これらのドキュメントは現在、Braze DocsのSwiftセクションで再公開されている。
+数か月前、[tvOS コンテンツカード]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/tvos)と[アプリ内メッセージング]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/tvos)の記事は誤って非推奨になりました。これらのドキュメントは現在、Braze DocsのSwiftセクションで再公開されている。
 
 {% alert note %}
-Braze Docsへの[投稿]({{site.baseurl}}/contributing/home)者は、このサイトが現在Ruby 3.3.0で動作していることに注意する必要がある。必要に応じてRubyのバージョンをアップグレードしてほしい。
+Braze Docs の[貢献者]({{site.baseurl}}/contributing/home)は、サイトが Ruby 3.3.0で実行されるようになったことを確認する必要があります。必要に応じてRubyのバージョンをアップグレードしてほしい。
 {% endalert %}
 
 [1]: {% image_buster /assets/img/braze-docs-japan.png %}
diff --git a/_lang/ja/_help/release_notes/2024/7_23_24.md b/_lang/ja/_help/release_notes/2024/7_23_24.md
index 4ad57ce2a5d..d707997a466 100644
--- a/_lang/ja/_help/release_notes/2024/7_23_24.md
+++ b/_lang/ja/_help/release_notes/2024/7_23_24.md
@@ -9,13 +9,13 @@ page_type: reference
 
 ## Braze Docsのアップデート
 
-### ディアタクシーとブレイズ・ドックス
+### Diátaxis と Braze Docs
 
-我々は、[Diátaxisと](https://diataxis.fr/)呼ばれるフレームワークを使ってドキュメンテーションの標準化を進めているところだ。ライターやコントリビューターがこの新しいフレームワークに合ったコンテンツを作成できるよう、[各コンテンツタイプのテンプレートを作成]({{site.baseurl}}/contributing/content_types)した。
+私たちは、[Diátaxis](https://diataxis.fr/)と呼ばれる枠組みを使ってドキュメントを標準化しています。ライターやコントリビューターがこの新しいフレームワークに合ったコンテンツを作成できるよう、[各コンテンツタイプのテンプレートを作成]({{site.baseurl}}/contributing/content_types)した。
 
-### Braze Docs用の新しいプル・リクエスト・テンプレート
+### Braze Docs の新しいプルリクエストテンプレート
 
-私たちは、[Braze Docsに貢献する]({{site.baseurl}}/contributing/home/)のがより簡単で混乱しないように、プルリクエスト（PR）テンプレートを改善するために時間をかけた。それでもまだ改善の余地があると思うなら、PRを開設するか、[問題を提出する](https://github.com/braze-inc/braze-docs/issues/new?assignees=&labels=enhancement&projects=&template=request_a_feature.md&title=)こと。簡単なことなら何でもいい！
+私たちは、[Braze Docsに貢献する]({{site.baseurl}}/contributing/home/)のがより簡単で混乱しないように、プルリクエスト（PR）テンプレートを改善するために時間をかけた。まだ改善の余地があると思われる場合は、PR を開封するか、[問題を送信](https://github.com/braze-inc/braze-docs/issues/new?assignees=&labels=enhancement&projects=&template=request_a_feature.md&title=)してください。すべてが簡単になります。
  
 ## データの柔軟性
 
@@ -23,61 +23,61 @@ page_type: reference
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-を通じてエクスポートする。 [`/custom_attributes`]({{site.baseurl}}/api/endpoints/export/custom_attributes/get_custom_attributes)と [`/events`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events_data)APIエンドポイントは早期アクセスではなくなった。
+[`/custom_attributes`]({{site.baseurl}}/api/endpoints/export/custom_attributes/get_custom_attributes) および[`/events`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events_data) API エンドポイントs によるエクスポートは、初期アクセスではなくなりました。
 
-### カレントの新しいユーザー権限
+### ユーザーの新しい Currents 権限
 
-ユーザーに対する新しい権限設定が2つある：**Currents統合を表示**および**Currents統合を編集**。ユーザー権限の詳細については[、こちらを]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions)参照のこと。 
+ユーザーには2つの新しい権限設定があります。\[**Currents 統合を表示する**] と \[**Currents 統合を編集する**] です。ユーザー権限の詳細については[、こちらを]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions)参照のこと。 
 
-### Snowflakeデータ保持ポリシーの更新
+### Snowflake データリテンションポリシーの更新
  
-8月27日より、2年以上前のすべてのスノーフレーク・セキュア・データ・シェアリング・イベントのデータから、個人を特定できる情報（PII）が削除される。Snowflakeを使用している場合、保持ポリシーが適用される前に、Snowflakeアカウントにコピーを保存することで、環境内の完全なイベントデータを保持することを選択することができる。詳しくは、[Snowflakeのデータ保持を]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention/)参照のこと。
+8月27日より、個人を特定できる情報 (PII) は、作成から2年を超えたすべての Snowflake Secure Data Sharing イベントデータから削除されます。Snowflake を使用する場合、完全なイベントデータを環境に保持するには、リテンションポリシーが適用される前に Snowflake アカウントにコピーを保存します。詳細については、[Snowflakeデータリテンション]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention/)を参照してください。
  
-## 創造性を解き放つ
+## 創造性を引き出す
 
 ### 複数ページのアプリ内メッセージ
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-アプリ内メッセージにページを追加することで、オンボーディングフローやウェルカムジャーニーのような連続したフローでユーザーを誘導することができる。詳しくは、[ドラッグ＆ドロップでアプリ内メッセージを作成するを]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create#multi-page)参照のこと。
+アプリ内メッセージにページを追加することで、オンボーディングフローやウェルカムジャーニーのような連続したフローでユーザーを誘導することができる。詳細については、[ドラッグアンドドロップによるアプリ内メッセージの作成]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create#multi-page)を参照してください。
 
-### リンク短縮とリキッド
+### Liquid でのリンク短縮
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-[Liquidを使ってURLをパーソナライズ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#enabling-link-shortening)し、SMSメッセージに含まれるURLを自動的に短縮し、クリックスルー率分析を収集する。試すには、[リンク・ショートニングを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/)参照のこと。
+[Liquidを使ってURLをパーソナライズ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#enabling-link-shortening)し、SMSメッセージに含まれるURLを自動的に短縮し、クリックスルー率分析を収集する。試してみるには、[リンク短縮]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/)を参照してください。
 
 ### カタログのAPI例
 
 配列フィールドを使った`/catalogs` エンドポイントの例を追加した。例を見るには、以下をチェックしてほしい：
 
-- [複数のカタログ項目を編集する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk)
-- [複数のカタログ項目を作成する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk)
-- [カタログ項目を更新する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items)
-- [カタログ項目を編集する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item)
-- [カタログ項目を作成する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item)
-- [カタログ項目を更新する]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item)
-- [カタログを作成する]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog)
+- [複数のカタログ項目を編集]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk)
+- [複数のカタログ項目を作成]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk)
+- [カタログアイテムを更新]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items)
+- [カタログアイテムを編集]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item)
+- [カタログアイテムを作成]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item)
+- [カタログアイテムを更新]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item)
+- [カタログを作成]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog)
  
-## ロバスト・チャンネル
+## 強力なチャネル
 
 ## 複数のWhatsAppビジネスアカウント
 
 {% multi_lang_include release_type.md release="一般的な可用性" %}
 
-各ワークスペースに複数のWhatsApp Businessアカウントとサブスクリプショングループ（および電話番号）を追加できるようになった。詳しくは[WhatsApp Businessアカウントを]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups)ご覧下さい。 
+各ワークスペースに複数のWhatsApp Businessアカウントとサブスクリプショングループ（および電話番号）を追加できるようになった。詳しくは、[複数のWhatsApp取引先]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups)を参照してください。 
 
-### SMSの地理的許可
+### SMSの地理的権限
 
 SMS Geographic Permissionsは、SMSメッセージを送信できる国をコントロールすることで、セキュリティを強化し、不正なSMSトラフィックから保護する。SMSメッセージが承認された地域にのみ送信されるように、国の許可リストを指定する方法については、[SMS国の許可リストを設定するを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_geographic_permissions/#configuring-your-sms-country-allowlist)参照のこと。
 
-### LINEとブレイズ
+### LINE と Braze
 
 {% multi_lang_include release_type.md release="ベータ" %}
 
-[LINEは](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf)日本で最も人気のあるメッセージングアプリで、月間アクティブユーザー数は9500万人を超える。LINEアカウントとBrazeを統合することで、ゼロおよびファーストパーティの顧客データを活用し、顧客の嗜好、行動、クロスチャネルでのインタラクションに基づいて、適切な顧客に魅力的なLINEメッセージを送ることができる。まずは[LINEを]({{site.baseurl}}/line)ご覧いただきたい。
+[LINE](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf) は、月間アクティブユーザー数が9500万 を超える国内で最も人気のあるメッセージング アプリです。LINE アカウントを Braze と統合することで、ゼロパーティおよびファーストパーティの顧客データを活用し、顧客の嗜好、行動、クロスチャネルのインタラクションに基づいて、適切な顧客に魅力的な LINE メッセージを送信できます。開始するには、[LINE]({{site.baseurl}}/line) を参照してください。
 
-### Shopifyである：値下げと再入荷
+### Shopify:値下げ、再入荷商品
 
 {% multi_lang_include release_type.md release="早期アクセス" %}
 
@@ -87,33 +87,33 @@ Shopifyでは、[値下げや]({{site.baseurl}}/user_guide/personalization_and_d
  
 ### 重複ユーザーのルールベースのマージ
 
-以前は、Brazeで重複ユーザーを個別または一括で検索し、マージすることができた。重複の解決方法を制御するルールを作成し、最も関連性の高いユーザーを残すことができる。詳しくは、[ルールベースのマージを]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users/#rules-based-merging)参照のこと。
+以前は、Braze で重複するユーザーを個別または一括で検索してマージすることができました。これで、重複がどのように解決されるかをコントロールするためのルールを作成できるようになりました。そのため、最も関連性の高いユーザーが保持されます。詳細については、[ルールベースのマージ]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users/#rules-based-merging)を参照してください。
 
 ### AI Liquidアシスタント
 
 {% multi_lang_include release_type.md release="ベータ" %}
 
-Sage AI Liquid AssistantはSage AIを搭載したチャットアシスタントで、メッセージ内容をパーソナライズするために必要なLiquidの生成をサポートする。テンプレートからリキッドを生成し、パーソナライズされたリキッドの提案を受け、セージAIのサポートで既存のリキッドを最適化することができる。AIリキッド・アシスタントは、使用されているリキッドを説明する注釈も提供するので、リキッドへの理解を深め、自分で書けるようになる。
+Sage AI Liquid アシスタントは Sage AI を搭載したチャットアシスタントであり、メッセージコンテンツをパーソナライズするために必要な Liquid を生成する場合に役立ちます。テンプレートからの Liquid の生成、パーソナライズされた Liquid の提案の受け取り、および Sage AI のサポートを使用した既存の Liquid の最適化を実行できます。AI Liquid アシスタントには、使用されている Liquid を説明する注釈も用意されているため、Liquid の理解を深めたり、自作方法を学んだりできます。
 
-まずは、[AIリキッド・アシスタントを]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_liquid)参照のこと。
+開始するには、「[AI Liquid アシスタント]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_liquid)」を参照してください。
  
 ## SDK
  
 ### Android SDKのログ
 
-[Braze Android SDKのロギングドキュメントを]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/additional_customization_and_configuration/#logging)見直し、読みやすく、アプリで使いやすくした。また、各ログレベルの説明も追加した。
+Braze Android SDKの[ログ記録文書を見直したので、あなたのアプリで読みやすく、使いやすいです。また、各ログレベルの説明も追加した。
 
-### iOS SDKのフォアグラウンド・プッシュ通知
+### iOS SDKのフォアグラウンドプッシュ通知s
 
-Braze iOS SDKの`subscribeToUpdates` メソッドが、フォアグラウンドプッシュ通知を受信したかどうかを検出できるようになった。詳しくは、[iOSプッシュ通知統合を]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration)参照のこと。
+Braze iOS SDKの `subscribeToUpdates` メソッドで、フォアグラウンドプッシュ通知を受信したかどうかを検出できるようになりました。詳しくは、[iOS プッシュ通知統合]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration)を参照してください。
  
 ### Xamarinのドキュメントを更新する
  
-[バージョン4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/releases/tag/4.0.0)以降、Braze Xamarin SDKはSwift SDKバインディングを使用しているため、コードスニペットと参考資料を更新した。また、読みやすく、理解しやすいようにセクションを再構成した。確認するには、[Xamarinのドキュメントを]({{site.baseurl}}/developer_guide/platform_integration_guides/xamarin/initial_sdk_setup)参照のこと。
+[バージョン4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/releases/tag/4.0.0)以降、Braze Xamarin SDK で Swift SDK バインディングが使用されるため、コードスニペットと参考資料が更新されました。また、読みやすく、理解しやすいようにセクションを再構成した。確認するには、[Xamarin ドキュメント]({{site.baseurl}}/developer_guide/platform_integration_guides/xamarin/initial_sdk_setup)を参照してください。
 
 ### SDKのアップデート
 
-以下のSDKアップデートがリリースされた。その他のアップデートは、対応するSDKの変更履歴を確認することで見つけることができる。
+以下のSDKアップデートがリリースされた。破壊的な更新は下記のとおりです。その他すべての更新は、対応する SDK の変更履歴をご確認ください。
  
 - [Swift SDK 9.3.1](https://github.com/braze-inc/braze-swift-sdk/releases/tag/9.3.1)
 - [Web SDK 5.3.2](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#532)
diff --git a/_lang/ja/_help/release_notes/deprecations.md b/_lang/ja/_help/release_notes/deprecations.md
index 78d09931097..9e8fbf7087d 100644
--- a/_lang/ja/_help/release_notes/deprecations.md
+++ b/_lang/ja/_help/release_notes/deprecations.md
@@ -3,144 +3,144 @@ nav_title: 非推奨
 article_title: 非推奨
 page_order: 9
 page_type: reference
-description: "このページでは、非推奨の記事への参照を含み、非推奨およびサポートされない機能のリストを提供する。"
+description: "このページには、非推奨の記事への参照と、非推奨の機能およびサポート対象外の機能のリストが含まれています。"
 ---
 
 # 非推奨
 
-ブレイズの内部でも外部でも、テクノロジーは常に動いている！そして、私たちはそれについていくためにベストを尽くしている。ここでは、Brazeの起源とその技術、そして私たちが "Before Time"-とにかく今より前...-でどのように人々を支えてきたかを知ることができる。
+テクノロジーは、Braze の内外を問わず常に進化しています。当社は、それに追いつくために最善を尽くしています。ここでは、Brazeの起源とその技術、そして私たちが "Before Time"-とにかく今より前...-でどのように人々を支えてきたかを知ることができる。
 
-もう存在しない統合や機能を検索してここにたどり着いたかもしれない。これは、テクノロジー業界における我々の進歩や動きをお知らせするための試みである。以下のリンクから、非推奨およびサポートされない機能のリストや、非推奨の記事を読むことができる。
+ここでは、存在しなくなった統合や機能の用語を検索してみましょう。これは、テクノロジー業界における当社の進歩と動向について、皆様に常に最新情報を提供することを目的としています。以下のリンクから、非推奨の機能とサポート対象外の機能のリストを確認し、非推奨の記事を読むことができます。
 
 ## 非推奨記事
 
 - [Android用カスタム・プッシュ・ブロードキャスト・レシーバー]({{site.baseurl}}/help/release_notes/deprecations/custom_broadcast_receiver/)
 - [Eclipse SDKのセットアップ]({{site.baseurl}}/help/release_notes/deprecations/eclipse_setup_deprecated/)
-- [TLS 1.0および1.1の廃止]({{site.baseurl}}/help/release_notes/deprecations/tls_deprecation/)
+- [TLS 1.0 および1.1 の非推奨]({{site.baseurl}}/help/release_notes/deprecations/tls_deprecation/)
 - [Twilio webhookの統合]({{site.baseurl}}/help/release_notes/deprecations/twilio/)
-- [Apptimizeパートナーシップ]({{site.baseurl}}/help/release_notes/deprecations/apptimize/)
-- [Grouparooパートナーシップ]({{site.baseurl}}/help/release_notes/deprecations/grouparoo)
+- [Apptimize のパートナーシップ]({{site.baseurl}}/help/release_notes/deprecations/apptimize/)
+- [Grouparoo のパートナーシップ]({{site.baseurl}}/help/release_notes/deprecations/grouparoo)
 - [Shopify`checkout.liquid` 非推奨]({{site.baseurl}}/help/release_notes/deprecations/shopify_checkout/)
 
 ## 非推奨ログ
 
-### ショップファイ `checkout.liquid`
+### Shopify `checkout.liquid`
 
-**支援は撤回された**：2024年8月（第1フェーズ）、2025年8月（第2フェーズ）
+**サポートの撤回**: 2024年8月（第1フェーズ）、2025年8月（第2フェーズ）
 
-Shopify`checkout.liquid` のサポートは2024年8月に非推奨となり、2025年8月に終了する。Shopifyは、より安全で、パフォーマンスが高く、カスタマイズ可能な[Checkout Extensibilityに](https://www.shopify.com/enterprise/blog/checkout-extensibility-winter-editions)移行する予定だ。
+Shopify `checkout.liquid` は、2024年8月に非推奨になり、2025年8月に終了します。Shopifyは、より安全で、パフォーマンスが高く、カスタマイズ可能な[Checkout Extensibilityに](https://www.shopify.com/enterprise/blog/checkout-extensibility-winter-editions)移行する予定だ。
 
 ### Android用カスタム・プッシュ・ブロードキャスト・レシーバー
 
-**支援は撤回された**：2022年10月
+**サポートの終了**: 2022年10月
 
 プッシュ通知にカスタム`BroadcastReceiver` を使用することは廃止された。代わりに [` subscribeToPushNotificationEvents()`](/docs/developer_guide/platform_integration_guides/android/push_notifications/android/customization/custom_event_callback/)で代用する。
 
 ### Grouparooパートナーシップ
 
-**支援は撤回された**：2022年4月
+**サポートの終了**: 2022年4月
 
-Grouparooのサポートは2022年4月をもって終了した。
+Grouparoo のサポートは、2022年4月に終了しました。
 
 ### Braze Windows SDK
 
-**2022年3月24日**だ：Braze Windows SDKは非推奨であり、Brazeダッシュボードで新しいWindowsアプリを作成することはできない。<br>
-**2022年9月15日**である：Windowsアプリに新しいメッセージを送ることはできない。既存のメッセージやデータ収集に影響はない。<br>
-**2024年1月11日**だ：Brazeは、Windowsアプリからのメッセージ配信やデータ収集を行わない。
+**2022年3 月24 日**:Braze Windows SDK は非推奨となり、Braze ダッシュボードで新しい Windows アプリを作成することはできません。<br>
+**2022年9 月15 日**:Windowsアプリに新しいメッセージを送ることはできない。既存のメッセージやデータ収集に影響はない。<br>
+**2024年1 月11 日**:Brazeは、Windowsアプリからのメッセージ配信やデータ収集を行わない。
 
-### 百度プッシュの統合
+### Baiduプッシュ統合
 
-**2022年3月24日**だ：BrazeのBaiduプッシュ統合は非推奨となり、Brazeダッシュボードで新しいBaiduアプリを作成することはできない。<br>
-**2022年9月15日**である：新しいBaiduプッシュメッセージは作成できない。既存のメッセージやデータ収集に影響はない。<br>
-**2024年1月11日**だ：Brazeは今後、Baiduアプリからのメッセージ配信やデータ収集は行わない。
+**2022年3 月24 日**:BrazeのBaiduプッシュ統合は非推奨となり、Brazeダッシュボードで新しいBaiduアプリを作成することはできない。<br>
+**2022年9 月15 日**:新しいBaiduプッシュメッセージは作成できない。既存のメッセージやデータ収集に影響はない。<br>
+**2024年1 月11 日**:Brazeは今後、Baiduアプリからのメッセージ配信やデータ収集は行わない。
 
 ### appboyBridge グローバル変数
 
-**支援は撤回された**：2021年5月<br>
-**に取って代わられた**： `brazeBridge`
+**サポートの終了**: 2021年5月<br>
+**置換**: `brazeBridge`
 
-グローバル変数`appboyBridge` は非推奨となり、`brazeBridge` に置き換えられる。`appboyBridge` は既存の顧客には引き続き機能するが、`appboyBridge` を使用している場合は、`brazeBridge` に移行することを推奨する。
+グローバル変数`appboyBridge` は非推奨となり、`brazeBridge` に置き換えられました。`appboyBridge` は既存のお客様は引き続き使用できますが、`appboyBridge` を使用している場合は `brazeBridge` に移行することをお勧めします。
 
 ### Amazon Momentsパートナーシップ
 
-**支援は撤回された**：2020年6月
+**サポートの終了**: 2020年6月
 
 Amazon Momentsのサポートは2020年6月をもって終了した。Amazon MomentsはAmazon Advertisingに統合され、APIと我々の統合は廃止された。
 
 ### 事実上のパートナーシップ
 
-**支援は撤回された**：2020年6月
+**サポートの終了**: 2020年6月
 
-Factualのサポートは2020年6月をもって終了した。Factualは最近Foursquareに買収され、Braze Platformとの統合はなくなった。
+Factual のサポートは、2020年6月に終了しました。Factualは最近Foursquareに買収され、Braze Platformとの統合はなくなった。
 
 ### Twilio webhookの統合
 
-**支援は撤回された**：2020年1月
+**サポートの終了**: 2020年1月
 
-[Twilio webhook統合の]({{site.baseurl}}/partners/twilio/)サポートは2020年1月31日をもって終了した。BrazeでもSMSサービスにアクセスしたい場合は、[SMSのドキュメントを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/)参照のこと。
+[Twilio Webhookインテグレーション]({{site.baseurl}}/partners/twilio/)の対応は2020年1月31日をもって終了しました。BrazeでもSMSサービスにアクセスしたい場合は、[SMSのドキュメントを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/)参照のこと。
 
 ### Apptimizeパートナーシップ
 
-**支援は撤回された**：2019年8月
+**サポートの終了**: 2019年8月
 
-現在[BrazeでApptimizeを]({{site.baseurl}}/help/release_notes/deprecations/apptimize)使用している場合、サービスの中断は発生しない。BrazeのユーザープロファイルにApptimizeのカスタム属性を設定することはできる。しかし、パートナーとの正式なエスカレーション・サポートは提供されない。
+現在[Braze]({{site.baseurl}}/help/release_notes/deprecations/apptimize)でApptimizeを使用している場合、サービスの中断は発生しません。Apptimize のカスタム属性を Braze のユーザープロファイルに設定することもできます。ただし、パートナーとの正式なエスカレーションサポートは提供されません。
 
 ### アプリ内オリジナルメッセージ
 
-**支援は撤回された：**2019年2月<br>
-**に取って代わられた**：[アプリ内メッセージング]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/creating_an_in-app_message)
+**サポートの終了**: 2019年2月<br>
+**置換**: [アプリ内メッセージング]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/creating_an_in-app_message)
 
 Brazeは、最新のUXとUIのベストプラクティスに準拠するため、アプリ内メッセージのルック＆フィールを改善し、オリジナルのアプリ内メッセージのサポートは終了した。
 
-Brazeは、以下のSDKリリースで、新しいアプリ内メッセージの形に移行した：
-- iOSだ： `2.19.0`
-- アンドロイドだ： `1.13.0`
-- ウェブだ： `1.3.0`
+Braze は、以下の SDK リリースでアプリ内メッセージの新しい形式に移行しました。
+- iOS: `2.19.0`
+- Android: `1.13.0`
+- Web: `1.3.0`
 
-これらのリリース以前は、Brazeは "アプリ内オリジナルメッセージ "をサポートしていた。以前は、新しいリリース以前にアプリ内キャンペーンを実施した顧客には、オリジナルのアプリ内メッセージのサポートが提供されていた。すべてのキャンペーン統計はこの変更の影響を受けず、オリジナルのアプリ内メッセージを送信した人は、**キャンペーン**ページの「**キャンペーンを作成」**ボタンから他のメッセージを送信することができた。
+これらのリリース以前は、Brazeは "アプリ内オリジナルメッセージ "をサポートしていた。これまでは、新しいリリース前にアプリ内キャンペーンを実行したすべてのお客様に対して、元のアプリ内メッセージのサポートが提供されていました。すべてのキャンペーン統計はこの変更の影響を受けず、オリジナルのアプリ内メッセージを送信した人は、**キャンペーン**ページの「**キャンペーンを作成」**ボタンから他のメッセージを送信することができた。
 
 ### フィードバック・ウィジェット
 
-**支援は撤回された**：2019年7月1日
+**サポートの終了**: 2019年7月1日
 
 Braze SDKは、アプリに追加できるフィードバックウィジェットを提供し、ユーザーが`submitfeedback` メソッドを使ってフィードバックを残し、それをDesk.com またはZendeskに渡し、ダッシュボードで管理できるようにした。
 
-### グーグル・クラウド・メッセージング（GCM）
+### Google Cloud Messaging (GCM)
 
-**支援は撤回された**：サポートをブレージングで取り外す：2018年7月、グーグルはサポートを打ち切った：2019年5月29日<br>
-**に取って代わられた**：[Firebase Cloud Messaging (FCM)]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/integration/standard_integration/#step-1-enable-firebase)
+**サポートの終了**: Braze のサポート終了: 2018年7月、Googleによるサポートの削除:2019年5月29日<br>
+**置換**: [Firebase クラウドメッセージング (FCM)]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/integration/standard_integration/#step-1-enable-firebase)
 
-グーグルは2019年5月29日をもって[GCMのサポートを終了](https://developers.googleblog.com/2018/04/time-to-upgrade-from-gcm-to-fcm.html)した。Brazeは2018年7月にAndroid SDKからGCMのサポートを打ち切ったが、これは当社の[Android SDKの変更履歴に](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)記載されている。これは、既存のGCMトークンが引き続き機能し、既存のユーザーにメッセージを送ることができることを意味する。ただし、新しいユーザーにメッセージを送ることはできない。
+Google は、2019年5月29日をもって [GCMのサポートを終了](https://developers.googleblog.com/2018/04/time-to-upgrade-from-gcm-to-fcm.html)しました。Brazeは2018年7月にAndroid SDKからGCMのサポートを打ち切ったが、これは当社の[Android SDKの変更履歴に](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)記載されている。これは、既存のGCMトークンが引き続き機能し、既存のユーザーにメッセージを送ることができることを意味する。ただし、新規ユーザーにメッセージを送ることはできません。
 
 まだ[Firebase Cloud Messaging (FCM)]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/integration/standard_integration/#step-1-enable-firebase)に移行していない顧客は、この変更の影響を受ける可能性がある。
 
-FCMに移行していない場合、GCMプッシュトークンの登録はすべて失敗する。アプリが現在GCMをサポートしている場合、開発チームと協力して[GCMからFirebase Cloud Messaging (FCM)に移行する](https://developers.google.com/cloud-messaging/android/android-migrate-fcm)必要がある。
+FCMに移行していない場合、GCMプッシュトークンの登録はすべて失敗する。アプリが現在GCMをサポートしている場合は、[GCMからFirebase Cloud Messaging (FCM)](https://developers.google.com/cloud-messaging/android/android-migrate-fcm)への移行時に開発チームと連携する必要があります。
 
-### エクリプス
+### Eclipse
 
-**支援は撤回された**：2014-2015<br>
-**に取って代わられた**：[アンドロイドスタジオ]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/#using-android-studio)
+**サポートの終了**: 2014～2015年<br>
+**置換**: [Android Studio]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/#using-android-studio)
 
-Brazeは、GoogleがEclipse Android Developer Tools（ADT）プラグインの[サポートを終了した](http://android-developers.blogspot.com/2015/06/an-update-on-eclipse-android-developer.html)ため、Eclipse IDEのサポートを終了した。 
+Google が Eclipse Android Developer Tools (ADT) プラグインの[サポートを終了](http://android-developers.blogspot.com/2015/06/an-update-on-eclipse-android-developer.html)したため、Braze は Eclipse IDE のサポートを中止しました。 
 
-移行前にEclipseとの統合についてサポートが必要な場合は、[サポートに]({{site.baseurl}}/support_contact/)問い合わせること。
+移行前に Eclipse の統合に関するサポートが必要な場合は、[サポート]({{site.baseurl}}/support_contact/)にお問い合わせください。
 
-### ロー・イベント・ストリーム（RES）
+### Raw Event Stream (RES)
 
-**支援は撤回された**：2018年7月<br>
-**に取って代わられた**：[Currents]({{site.baseurl}}/partners/braze_currents/about/)
+**サポートの終了**: 2018年7月<br>
+**置換**: [Currents]({{site.baseurl}}/partners/braze_currents/about/)
 
-Rawイベントストリームは[Currentsの]({{site.baseurl}}/partners/braze_currents/about/)前身であり、Brazeデータの将来のために廃止された。
+Raw Event Stream は [Currents]({{site.baseurl}}/partners/braze_currents/about/) の前身であり、Braze データの将来に備えて廃止されました。
 
 ### アイドル時のディレイ - GCM機能
 
-**支援は撤回された**：2016年11月
+**サポートの終了**: 2016年11月
 
-Delay While Idleパラメータは、以前は[GCMプッシュオプションの](https://developers.google.com/cloud-messaging/http-server-ref)一部であった。グーグルは2016年11月15日、このオプションのサポートを打ち切った。以前は、**trueに**設定すると、デバイスがアクティブになるまでメッセージを送信しないことを示していた。
+Delay While Idleパラメータは、以前は[GCMプッシュオプション](https://developers.google.com/cloud-messaging/http-server-ref)の一部でした。Googleは2016年11月15日にこのオプションのサポートを撤回した。以前は、**true**に設定した場合、デバイスがアクティブになるまでメッセージを送信しないことを示していました。
 
-### カスタム・エンドポイント
+### カスタムエンドポイント
 
-**支援は撤回された**：2019年12月
+**サポートの終了**: 2019年12月
 
 カスタムエンドポイントの削除。カスタムエンドポイントを持っている場合は、それを使い続けることができるが、Brazeはもうそれを提供しない。
 
diff --git a/_lang/ja/_help/release_notes/deprecations/apptimize.md b/_lang/ja/_help/release_notes/deprecations/apptimize.md
index d04cce0758d..61577f07c31 100644
--- a/_lang/ja/_help/release_notes/deprecations/apptimize.md
+++ b/_lang/ja/_help/release_notes/deprecations/apptimize.md
@@ -3,17 +3,17 @@ nav_title: パートナーシップを評価する
 page_order: 0
 
 page_type: update
-description: "このアーカイブされた記事は、ApptimizeとBrazeの提携を網羅しています。Brazeは、2019年9月現在、Apptimize提携の支援を廃止している。"
+description: "このアーカイブされた記事は、ApptimizeとBrazeの提携を網羅しています。2019年9月より、Braze は Apptimize のパートナーシップに関するサポートを廃止しています。"
 ---
 
-# 評価する
+# Apptimize
 
 {% alert update %}
-Brazeは、2019年9月現在、Apptimize提携の支援を廃止している。
+2019年9月より、Braze は Apptimize のパートナーシップに関するサポートを廃止しています。
 
 <br>
 
-現在、Braze でApptimize を使用している場合、サービスの中断は発生しません。アプリのカスタム属性をBraze ユーザープロファイルsに設定することもできます。ただし、パートナーとの正式なエスカレーションサポートは提供されません。
+現在、Braze で Apptimize を使用している場合、サービスは中断されません。Apptimize のカスタム属性を Braze のユーザープロファイルに設定することもできます。ただし、パートナーとの正式なエスカレーションサポートは提供されません。
 
 <br>
 
@@ -21,59 +21,59 @@ Brazeは、2019年9月現在、Apptimize提携の支援を廃止している。
 {% endalert %}
 
 
-[アプリ timize](https://apptimize.com/)は、携帯アプリのテストと増殖プラットフォームです
-これにより、顧客sはアプリの発生過程を通じて迅速に反復することができる。
+[Apptimize](https://apptimize.com/) は、モバイルアプリのテストおよび拡張プラットフォームです。
+このアプリを使用することで、アプリ開発プロセス全体を通じて反復処理を迅速に進めることができます。
 
-Apptimizeは、Brazeと併用して、成長を補完することができます
-マーケティング / CRM ストラテジとプロダクトUI テストの同期化
-両プラットフォームのデーター
+Apptimize は、Braze と組み合わせて使用できます。
+それにより、成長マーケティングと CRM の戦略を製品 UI テストで補完できます。
+そのために、2つのプラットフォーム間で実験とデータを同期させます。
 
 ## ユースケース
 
-Braze とApptimize を併用すると、両方のプラットフォームを同時に活用できます
-強力なエンドツーエンドの体験の創出:
+Braze と Apptimize を組み合わせて使用することで、両方のプラットフォームを同時に活用できます。
+それにより、強力なエンドツーエンドのエクスペリエンスが生み出されます。
 
 * カスタムプロモーション用のアプリ内およびCRM マーケティングのエクスペリエンスを同期します。
-* Apptimize で新しいオンボーディングエクスペリエンスをテストし、Brazeを使用して新しいフロー全体でユーザーs を育成します。
-* アプリの適切なユーザー メッセージングと並行して、プロダクト機能の設定を同時にテストします。
-* ユーザー s のさまざまなSegmentに合わせて、アプリ体験とアプリの適切なメッセージングを調整します。
+* Apptimize で新しいオンボーディングエクスペリエンスをテストし、Braze を使用して新しいフロー全体でユーザーを育成します。
+* 製品機能の構成と適切なユーザーメッセージングを同時にテストします。
+* ユーザーのさまざまなセグメントに合わせて、アプリ内エクスペリエンスと適切なメッセージングをカスタマイズします。
 
 ## その仕組み
 
-BrazeとApptimizeを統合して、SDKからSDKにデータを渡すことができます。
+Braze と Apptimize を統合して、SDK 間でデータを受け渡すことができます。
 有効なApptimize A/BテストグループをBrazeに同期し、次の操作を実行できます
-プッシュ、メールを使用して、Braze内の特定のアプリ見積もりテストのユーザーsをリターゲティングするします。
-アプリ内メッセージング。
+プッシュ、メール、またはアプリ内メッセージングを使用して、Braze 内の特定の Apptimize
+テストでユーザーをリターゲティングします。
 
 BrazeとApptimizeの方法を示す標本積分コードがあります
-SDK s は、データをパワーカスタムターゲティングに渡し、それに基づくBrazeでセグメンテーションすることができます
-実験データを見積もる。
+Apptimize の実験データに基づいて Braze でカスタムターゲティングとセグメンテーションを強化するために、SDK
+はデータを渡すことができます。
 
 このサンプルインテグレーションでは、ユーザーのBraze ユーザーにカスタム属性s を設定します
 次のApptimize データのプロファイル:
 
-* ユーザーが現在登録されている実証試験の全一覧。
+* ユーザーが現在登録されているすべてのアクティブな実験の一覧。
 * 完成した実験を含め、ユーザーがこれまでに登録したすべての実験の一覧。
-* ユーザーが試験参加の一部と見なしたバリアント。
+* ユーザーが実験に参加しているとみなされたバリアント。
 
-> 特徴フラグは、唯一のバリアントが特徴フラグが有効かどうかである実験と考えられる。機能フラグが消灯している場合は、レポートされません。
+> 特徴フラグは、唯一のバリアントが特徴フラグが有効かどうかである実験と考えられる。フィーチャーフラグがオフの場合は、データがレポートされません。
 
 さらに、このインテグレーションでは、最初のBraze カスタムイベントが記録されます
-実験参加イベントこれは、次の 2 つの方法のいずれかで実行できます。
+(実験の参加イベント)。これは、次の 2 つの方法のいずれかで実行できます。
 
-* カスタムイベントは、実験名、実験ID、バリアント名、およびバリアント ID を示すプロパティデータを使用して生成されます。次に、Brazeのアクションベースの配信キャンペーンとキャンバスを使用して、リアルタイムのトリガーリングでs をリターゲティングする ユーザーできます。これらのプロパティーを使用して、トリガーしたい正確なApptimize Experiment を特定します。
-* 属性配列は、発生したすべての参加のエントリーとともに生成されます。各参加は次のように書式設定されます `experiment_id_EXPERIMENT_ID:variant_id_VARIANT_ID:experiment_name_EXPERIMENT_NAME:variant_name_VARIANT_NAME`
+* 実験名、実験 ID、バリアント名、バリアント ID を示すプロパティデータを使用してカスタムイベントが生成されます。その後、Braze のアクションベースの配信キャンペーンとキャンバスを使用し、リアルタイムトリガーを介してユーザーをリターゲティングできます。これらのプロパティを使用して、トリガーする Apptimize の実験を正確に識別します。
+* 属性配列は、発生したすべての参加のエントリとともに生成されます。それぞれの参加の書式は `experiment_id_EXPERIMENT_ID:variant_id_VARIANT_ID:experiment_name_EXPERIMENT_NAME:variant_name_VARIANT_NAME` になります。
 
 その後、Brazeのアクションベースの配信キャンペーンまたはキャンバスを使用して送信できます
-これらの事象がトリガーされたときにsをリアルタイムでユーザーするためのフォローオンメッセージ。
+(これらのイベントがトリガーされたときに、後続メッセージをユーザーにリアルタイムで送信)。
 
 ## 統合
 
 ### iOS
-アプリと統合するには、次の`Appboy-Apptimize.m` を読み込みます
-`Apptimize-Appboy.h` Xコードプロジェクトにファイルをインポートする `Appboy-Apptimize.h`
-AppDelegate インプリメンテーションにヘッダーし、以下を追加します
-`didFinishLaunchingWithOptions` Appboy とApptimize の両方を初期化した後:
+アプリと統合するには、次の `Appboy-Apptimize.m` および
+`Apptimize-Appboy.h` ファイルを Xcode プロジェクトにインポートして、`Appboy-Apptimize.h`
+ヘッダーを AppDelegate 実装にインポートし、Appboy と Apptimize の両方を初期化した後に以下を
+`didFinishLaunchingWithOptions` に追加します。
 
 ```objc
 [ApptimizeAppboy setupExperimentTracking];
@@ -215,8 +215,8 @@ NSString *const ApptimizeAppboyTestEnrollmentStorageKey = @"ApptimizeAppboyTestE
 
 ### Android
 
-`apptimizeappboy.java` クラスをアプリとメインにインポートする `activity`
-実装では、プライベートメンバー`appboyApptimizeIntegration` を作成します。
+`apptimizeappboy.java` クラスをアプリにインポートして、メインの `activity`
+実装で非公開メンバー `appboyApptimizeIntegration` を作成します。
 
 ```java
 private ApptimizeAppboy appboyApptimizeIntegration;
diff --git a/_lang/ja/_help/release_notes/deprecations/custom_broadcast_receiver.md b/_lang/ja/_help/release_notes/deprecations/custom_broadcast_receiver.md
index f7bdadd181a..b3af89a91e0 100644
--- a/_lang/ja/_help/release_notes/deprecations/custom_broadcast_receiver.md
+++ b/_lang/ja/_help/release_notes/deprecations/custom_broadcast_receiver.md
@@ -1,20 +1,20 @@
 ---
 nav_title: プッシュ・コールバック・ブロードキャスト・レシーバー
-article_title: Android用カスタム・ブロードキャスト・レシーバー・プッシュ・コールバック
-description: "このリファレンス記事では、Androidプッシュ通知用のカスタムBroadcastレシーバーの作成について説明する。"
+article_title: Android のカスタムブロードキャストレシーバープッシュコールバック
+description: "この参考記事では、Android プッシュ通知用のカスタムブロードキャストレシーバーの作成について説明します。"
 ---
 
-# ブロードキャスト・レシーバーによるプッシュ受信、開封、破棄、キーと値のペアのカスタム処理 {#android-push-listener-broadcast-receiver}
+# ブロードキャストレシーバー {#android-push-listener-broadcast-receiver} を介したプッシュの受信、開封、却下、およびキーと値のペアのカスタム処理
 
 {% alert important %}
 プッシュ通知にカスタム`BroadcastReceiver` を使用することは廃止された。代わりに [` subscribeToPushNotificationEvents()`](/docs/developer_guide/platform_integration_guides/android/push_notifications/android/customization/custom_event_callback/)で代用する。
 {% endalert %}
 
-Brazeはまた、プッシュ通知の受信時、開封時、解除時にカスタムインテントをブロードキャストする。このようなシナリオに対して特定のユースケースがある場合（カスタムキーバリューペアをリッスンする必要がある場合や、ディープリンクを独自に処理する必要がある場合など）、カスタム`BroadcastReceiver` を作成して、これらのインテントをリッスンする必要がある。
+また、Braze は、プッシュ通知が受信、開封、または却下されたときにカスタムインテントをブロードキャストします。これらのシナリオに特定のユースケースがある場合 (カスタムのキーと値のペアをリッスンする必要がある場合や、ディープリンクを独自に処理する必要がある場合など)、カスタム `BroadcastReceiver` を作成してこれらのインテントをリッスンする必要があります。
 
 ## ステップ 1:BroadcastReceiverを登録する
 
-カスタム`BroadcastReceiver` を登録し、Brazeのプッシュをリッスンする。 [`AndroidManifest.xml`][71]:
+カスタム`BroadcastReceiver` を登録して、[`AndroidManifest.xml`][71] でBrazeプッシュ開封をリッスンし、インテントを受信します。
 
 ```xml
 <receiver android:name="YOUR-BROADCASTRECEIVER-NAME" android:exported="false" >
@@ -30,12 +30,12 @@ Brazeはまた、プッシュ通知の受信時、開封時、解除時にカス
 
 レシーバーは、Brazeからブロードキャストされたインテントを処理し、それを使ってアクティビティを起動する：
 
-- をサブクラス化すべきである。 [`BroadcastReceiver`][53]`onReceive()`をオーバーライドする必要がある。
-- `onReceive()` メソッドは、Brazeからブロードキャストされるインテントをリッスンしなければならない。
+- これは [`BroadcastReceiver`][53] をサブクラス化し、`onReceive()` をオーバーライドする必要があります。
+- `onReceive()` メソッドは、Braze でインテントブロードキャストをリッスンする必要があります。
   - プッシュ通知が届くと、`NOTIFICATION_RECEIVED` インテントを受信する。
-  - ユーザーがプッシュ通知をクリックすると、`NOTIFICATION_OPENED` インテントを受け取る。
-  - `NOTIFICATION_DELETED` インテントは、プッシュ通知がユーザーによって却下（スワイプして離す）されたときに受信される。
-- これらのケースごとに、カスタムロジックを実行する必要がある。受信機がディープリンクを開く場合は、`braze.xml` で`com_braze_handle_push_deep_links_automatically` を`false` に設定し、自動ディープリンクオープンをオフにしておくこと。
+  - ユーザーがプッシュ通知をクリックすると、`NOTIFICATION_OPENED` インテントが受信されます。
+  - ユーザーがプッシュ通知を却下 （スワイプ） すると、`NOTIFICATION_DELETED` インテントが受信されます。
+- これらのケースごとにカスタムロジックを実行する必要があります。受信者がディープリンクを開封する場合は、`braze.xml` で `com_braze_handle_push_deep_links_automatically` を`false` に設定し、自動ディープリンク開封を無効にしてください。
 
 カスタム・レシーバーの詳細な例については、以下のコード・スニペットを参照のこと：
 
@@ -112,7 +112,7 @@ class CustomBroadcastReceiver : BroadcastReceiver() {
 
 ## ステップ 3:カスタムキーと値のペアにアクセスする
 
-ダッシュボードまたはメッセージングAPIを介して送信されたカスタムKey-Valueペアは、カスタムブロードキャストレシーバーでアクセスできる：
+ダッシュボード またはメッセージング API を介して送信されたカスタムキーと値のペアは、選択した用途に応じてカスタムブロードキャストレシーバでアクセス可能になります。
 
 {% tabs %}
 {% tab JAVA %}
diff --git a/_lang/ja/_help/release_notes/deprecations/eclipse_setup_deprecated.md b/_lang/ja/_help/release_notes/deprecations/eclipse_setup_deprecated.md
index 6760b111eef..2414549ec39 100644
--- a/_lang/ja/_help/release_notes/deprecations/eclipse_setup_deprecated.md
+++ b/_lang/ja/_help/release_notes/deprecations/eclipse_setup_deprecated.md
@@ -9,11 +9,11 @@ description: "このアーカイブ記事では、EclipseでSDKの初期セッ
 # EclipseでSDKを初期セットアップする
 
 {% alert update %}
-[GoogleがEclipse Android Developer Tools Pluginのサポートを終了した](http://android-developers.blogspot.com/2015/06/an-update-on-eclipse-android-developer.html)ため、BrazeはEclipse IDEのサポートを終了した。移行前にEclipseとの統合についてサポートが必要な場合は、[サポートまでEメールで]({{site.baseurl}}/support_contact/)問い合わせを。
+Google が Eclipse Android Developer Tools プラグインの[サポートを終了](http://android-developers.blogspot.com/2015/06/an-update-on-eclipse-android-developer.html)したため、Braze は Eclipse IDE のサポートを中止しました。移行前に Eclipse の統合に関するサポートが必要な場合は、[サポートにメールで]({{site.baseurl}}/support_contact/)お問い合わせください。
 {% endalert %}
 
 ## ステップ 1
-コマンドラインで、[Braze Android GitHub Repositoryを][03]クローンする。
+コマンドラインで、[Braze Android GitHub リポジトリ][03]を複製します。
 
 ```bash
 $ git clone git@github.com:braze-inc/braze-android-sdk.git
@@ -22,53 +22,53 @@ $ git clone git@github.com:braze-inc/braze-android-sdk.git
 ## ステップ 2
 Brazeプロジェクトをローカルのワークスペースにインポートする。
 
-エクリプス』だ：
+Eclipse の場合:
 
-  - ファイル＞インポートに移動する。
+  - \[ファイル] > \[インポート] に移動します。
 
     ![ファイルインポート][04]
-  - Android > Existing Android Code into Workspaceを選択する。
+  - \[Android] > \[ワークスペースに存在する Android コード] を選択します。
 
     ![Androidドインポート][05]
-  - Browse "をクリックする。
+  - \[参照] をクリックします。
 
-    ![ブラウズ][06]
-  - Braze UIプロジェクトフォルダと "copy project into workspace "にチェックを入れ、"Finish "をクリックする。
+    ![参照][06]
+  - Braze UI プロジェクトフォルダーを確認し、「プロジェクトをワークスペースにコピー」して、\[終了] をクリックします。
 
-    ![Android UIプロジェクトを選択する][07]
+    ![Android UI プロジェクトを選択する][07]
 
 ## ステップ 3
 自分のプロジェクトでBrazeを参照する。
-エクリプス』だ：
+Eclipse の場合:
 
   - プロジェクトを右クリックし、"Properties "を選択する。
 
     ![プロパティをクリックする][08]
-  - Android」で、Libraryセクションの「Add...」をクリックし、アプリにライブラリとしてandroid-sdk-uiを追加する。
+  - \[Android] で、\[ライブラリー] セクションの \[追加...]" をクリックし、android-sdk-ui をライブラリーとしてアプリに追加します。
 
-    ![ブレイズ・アッド][09]
+    ![Braze 追加][09]
 
 ## ステップ 4
 依存性エラーを解決し、ビルドターゲットを修正する。
 
 このとき、Brazeのコードでエラーが出るかもしれないが、これは依存関係が入力されておらず、ビルドターゲットが間違っている可能性があるためだ：
 
-   - Braze UIプロジェクトを右クリックし、Properties->Androidを選択し、ビルドターゲットがBrazeの現在のビルドツールバージョンに設定されていることを確認する。
+   - Braze UI プロジェクトを右クリックし、\[プロパティ] -> \[Android] を選択して、ビルドターゲットが Braze の最新ビルドツールバージョンに設定されていることを確認します。
 
-      ![ビルド・ターゲット][10]
-   - Braze UIプロジェクトを右クリックし、Properties->Java Build Path->Add JARs...を選択し、メインアプリケーションの'android-support-v4.jar'をライブラリとして追加する。
+      ![ビルドターゲット][10]
+   - Braze UI プロジェクトを右クリックし、\[プロパティ] -> \[Java ビルドパス] -> \[JAR を追加...] を選択して、メインアプリケーションから「android-support-v4.jar」をライブラリーとして追加します。
 
       ![サポート][11]
 
 ## ステップ5
 
-最後のピースを加える。
+最終ピースを追加します。
 
-  - SDKのバージョンが1.10.0以上の場合、次のように追加する必要がある。
+  - SDK バージョン1.10.0以降の場合は、
   `<service android:name="com.appboy.services.AppboyDataSyncService" />`
-  AndroidManifest.xmlEclipseはマニフェストのマージをサポートしていない。
+  を AndroidManifest.xml に追加する必要があります。Eclipse ではマニフェストマージがサポートされていないためです。
 
-  - SDKバージョン1.7.0以上の場合、ライブラリ・プロジェクトから "assets/fontawesome-webfont.ttf" をアプリケーションにコピーする必要がある。Eclipseはライブラリからassetsフォルダを自動的にインクルードしない。
+  - SDK バージョン1.7.0以降では、「assets/fontawesome-webfont.ttf」をライブラリープロジェクトからアプリケーションにコピーする必要があります。Eclipse には、ライブラリーのアセットフォルダは自動的には含まれません。
 
 [03]: https://github.com/braze-inc/braze-android-sdk "Appboy Android GitHubリポジトリ"
 [04]: {{site.baseurl}}/assets/img_archive/file_import.png
diff --git a/_lang/ja/_help/release_notes/deprecations/grouparoo.md b/_lang/ja/_help/release_notes/deprecations/grouparoo.md
index 60dec67d149..d3607fe4ab3 100644
--- a/_lang/ja/_help/release_notes/deprecations/grouparoo.md
+++ b/_lang/ja/_help/release_notes/deprecations/grouparoo.md
@@ -1,18 +1,18 @@
 ---
-nav_title: グルーパルー
+nav_title: Grouparoo
 page_order: 1
 description: "この記事では、BrazeとGrouparooのパートナーシップについて概説している。GrouparooはオープンソースのリバースETLツールで、データウェアハウスのデータを使ってマーケティング、セールス、サポートの各ツールに簡単にパワーを与えることができる。"
 page_type: update
 
 ---
 
-# グルーパルー
+# Grouparoo
 
 {% alert update %}
-Grouparooのサポートは2022年4月をもって終了した。
+Grouparoo のサポートは、2022年4月に終了しました。
 {% endalert %}
 
-> [Grouparooは][1]オープンソースのリバースETLツールで、倉庫内のデータを使ってマーケティング、セールス、サポートツールを簡単にパワーアップできる。設定はモデル中心のUIで行われるため、技術者でないチームメンバーでも、運用をサポートするためのデータ同期の設定やスケジュールを立てることができる。
+> [Grouparoo][1]は、開封ソースのリバースETLツールで、倉庫内のデータを使用してマーケティング、販売、サポートツールに簡単に電力を供給します。設定はモデル中心のUIで行われるため、技術者でないチームメンバーでも、運用をサポートするためのデータ同期の設定やスケジュールを立てることができる。
 
 BrazeとGrouparooの統合により、倉庫に保存されているデータをBrazeに送信することで、簡単に運用することができる。自動同期のスケジュールを設定すれば、常に最新の情報で顧客とのコミュニケーションを強化できる。
 
@@ -20,7 +20,7 @@ BrazeとGrouparooの統合により、倉庫に保存されているデータを
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| Grouparooのアカウントとプロジェクト | このパートナーシップを利用するには、Grouparooアカウントとプロジェクトが必要である。<br><br>この統合は、Grouparooが提供する無料のコミュニティ版と企業向けソリューションで使用することができる。セットアップはGrouparooコンフィギュレーション・ユーザーインターフェイスで行われる。 |
+| Grouparooのアカウントとプロジェクト | このパートナーシップを利用するには、Grouparooアカウントとプロジェクトが必要である。<br><br>この統合は、Grouparooが提供する無料のコミュニティーエディションおよびエンタープライズソリューションで使用できます。セットアップはGrouparooコンフィギュレーション・ユーザーインターフェイスで行われる。 |
 | Braze REST API キー | ユーザーとトラック権限を持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][1]。エンドポイントは、インスタンスのBraze URLに依存する。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -29,7 +29,7 @@ BrazeとGrouparooの統合により、倉庫に保存されているデータを
 
 ### ステップ 1:GrouparooでBrazeアプリを作成する
 
-Grouparooで**Appsに**移動し、**Brazeを**選択して新しいBrazeアプリを作成する。表示されたモーダルで、Braze APIキーとRESTエンドポイントを入力する。
+Grouparoo で、\[**Apps**] に移動し、\[**Braze**] を選択して新しいBraze アプリを作成します。表示されたモーダルで、Braze APIキーとRESTエンドポイントを入力する。
 
 ![][2]
 
@@ -41,33 +41,33 @@ Grouparooで**Appsに**移動し、**Brazeを**選択して新しいBrazeアプ
 
 #### 同期モードを選択する
 
-Grouparooで、ナビゲーションバーからモデルを選択する。次に、**Destinations**セクションまでスクロールし、**Add new Destinationを**クリックする。
+Grouparooで、ナビゲーションバーからモデルを選択する。次に、**Destinations**セクションまでスクロールし、**Add new Destination**をクリックします。
 
 次に、作成した**Braze**アプリを選択し、保存先に名前を付け、希望の同期モードを以下から選択する：
-- **同期する**：必要に応じてBrazeユーザーを追加、更新、削除する。このオプションは、新規レコード、既存レコードの変更、および削除を検索する。
-- **添加物**だ：必要に応じてBrazeユーザーを追加・更新するが、誰も削除しないこと。このオプションは、Brazeに追加する新規ユーザーと既存のBrazeユーザーの変更を探すが、削除は追跡しない。
-- **豊かにする**：Brazeにすでに存在するユーザーのみをアップデートする。ユーザを追加または削除しない。このオプションは、Brazeの既存ユーザーのみを更新する。
+- **同期**:必要に応じてBrazeユーザーを追加、更新、削除する。このオプションでは、新しいレコード、既存レコードの変更、および削除を検索します。
+- **Additive**: 必要に応じてBrazeユーザーを追加・更新するが、誰も削除しないこと。このオプションは、Brazeに追加する新規ユーザーと既存のBrazeユーザーの変更を探すが、削除は追跡しない。
+- **Enrich**: Brazeにすでに存在するユーザーのみをアップデートする。ユーザを追加または削除しない。このオプションは、Brazeの既存ユーザーのみを更新する。
 
 #### プロパティ・フィールドのマッピング
 
 次に、Grouparooのプロパティ・フィールドをBrazeのプロパティ・フィールドにマッピングする必要がある。 
 
-![プロパティのマッピングフィールドの例。grouparooのuserIDはexternal_idにマップされるように設定される。email、firstName、lastNameは同等の "email"、"first_name"、"last_name "grouparooフィールドとして設定される。][3]{: style="max-width:80%;"}
+![プロパティのマッピングフィールドの例。Grouparoo userID は、external_id にマップするように設定されます。email、firstName、lastName は、対応する「email」、「first_name」、および「last_name」 Grouparoo フィールドとして設定されます。][3]{: style="max-width:80%;"}
 
-Braze`external_id` フィールドがソーステーブルの主キーにマッピングされていることを確認する。残りのフィールドは、ユースケースに応じてマッピングする。
+Braze`external_id` フィールドがソーステーブルの主キーにマッピングされていることを確認する。ユースケースでの必要に応じて、残りのフィールドをマッピングします。
 
-**レコードプロパティセクションを送信する**：データをマップするために利用可能なプリセット・ユーザー・プロファイル・フィールドのリスト。これらのどれでもGrouparooのプロパティから同期させることができる。
+\[**Send Record Properties**] セクション:データのマッピングに使用できるプリセットユーザープロファイルフィールドのリスト。これらのいずれかをGrouparoo プロパティから同期できます。
 
-**オプションのBraze User Profile Fields**セクション：オプションのカスタムBrazeユーザープロファイルフィールドを作成する。**Add New Braze User Profile Fieldを**クリックすると、Brazeにマッピングできるすべての利用可能なプロパティが表示される。新しく作成するフィールドの名前はGrouparooプロパティと同じになるが、名前を変更することができる。
+**Optional Braze User Profile Fields**セクション:オプションのカスタムBrazeユーザープロファイルフィールドを作成する。\[**Add New Braze User Profile Field**] を選択すると、Braze にマッピングできるすべてのプロパティが表示されます。新しく作成するフィールドの名前はGrouparooプロパティと同じになるが、名前を変更することができる。
 
 #### Grouparooグループ
 
-マッピングだけでなく、GrouparooグループをBrazeサブスクリプショングループに追加することもできる。 
+マッピングに加えて、Grouparoo グループを Braze 購読グループに追加することもできます。 
 
 ![Grouparoo宛先設定ウィンドウの "Braze Subscription Groups "で、"High value with recent automotive purchase "Grouparooグループが "High value with recent automotive purchase "Brazeサブスクリプショングループに追加される。][4]{: style="max-width:80%;"}
 
 {% alert important %}
-この統合に関する詳細と最新情報は[Grouparooのドキュメントを](https://www.grouparoo.com/docs/integrations/grouparoo-braze)参照されたい。
+この統合に関する詳細および更新は、[Grouparooのドキュメント](https://www.grouparoo.com/docs/integrations/grouparoo-braze)にあります。
 {% endalert %}
 
 [1]: https://www.grouparoo.com/
diff --git a/_lang/ja/_help/release_notes/deprecations/shopify_checkout.md b/_lang/ja/_help/release_notes/deprecations/shopify_checkout.md
index cb8624e6064..ef0b96d1569 100644
--- a/_lang/ja/_help/release_notes/deprecations/shopify_checkout.md
+++ b/_lang/ja/_help/release_notes/deprecations/shopify_checkout.md
@@ -1,5 +1,5 @@
 ---
-nav_title: Shopify チェックアウト.liquid
+nav_title: Shopify checkout.liquid
 page_order: 7
 description: "この記事では、Shopifyのcheckout.liquidの非推奨について、Shopifyの統合への影響と開発者向けのガイダンスを説明します。"
 page_type: update
@@ -12,40 +12,40 @@ Shopifyはすべてのマーチャントに`checkout.liquid`の非推奨と、
 
 Shopifyは`checkout.liquid`を2段階で廃止します:
 
-1. **[2024年8月13日](#phase-one-august-13-2024):**情報、配送、および支払いページをアップグレードする締め切り。
-2. **[2025年8月28日](#phase-two-august-28-2025):**感謝ページと注文ステータスページをアップグレードする締め切り、スクリプトタグや追加スクリプトを使用するアプリを含みます。
+1. **[2024年8月13日](#phase-one-august-13-2024):**情報、配送、支払いのページをアップグレードする期限。
+2. **[2025年8月28日](#phase-two-august-28-2025):**スクリプトタグと追加スクリプトを使用するアプリを含む、ありがとうページと注文ステータスページをアップグレードする期限。
 
 チェックアウト拡張機能へのアップグレードに関する一般情報については、[Shopifyのアップグレードガイド](https://help.shopify.com/en/manual/checkout-settings/customize-checkout-configurations/checkout-extensibility)を参照してください。
 
-## 統合への影響
+## 連携への影響
 
-BrazeとShopifyの統合は、[Shopify ScriptTags](https://shopify.dev/docs/apps/build/online-store/script-tag-legacy)を使用して、ヘッドレスでないサイトにBraze Web SDKを読み込むために使用されます。2025年の期限前に新しいバージョンの統合を開始し、`checkout.liquid`が完全に廃止される前にすべての顧客をサポートする予定です。 
+BrazeとShopifyの統合は、[Shopify ScriptTags](https://shopify.dev/docs/apps/build/online-store/script-tag-legacy)を使用して、ヘッドレスでないサイトにBraze Web SDKを読み込むために使用されます。`checkout.liquid` が完全に非推奨になる前に、すべてのお客様をサポートするため、2025年の期限前に新しいバージョンの連携を開始する予定です。 
 
-2024年8月13日に予定されている変更について、開発チームによって影響を受けるかどうかを確認するには、以下の詳細を確認してください。
+2024年8月13日に予定されている変更については、以下の詳細を確認して、開発チームの影響を受けるかどうかを確認してください。
 
 ### フェーズ1:2024年8月13日
 
-デフォルトのBrazeとShopifyの統合は、チェックアウト体験内の情報、配送、および支払いページを使用しません。その結果、デフォルトの統合には影響しません。 
+デフォルトのBrazeとShopifyの統合は、チェックアウト体験内の情報、配送、および支払いページを使用しません。そのため、デフォルトインテグレーションは影響を受けません。 
 
 #### Shopify Plus
 
 Shopify Plusの顧客の場合、情報、配送、または支払いページの`checkout.liquid`を変更するカスタムSDKコードスニペットは、この日以降無効になります。例えば、これらのページからイベントを記録するカスタムコードは機能しなくなります。カスタムSDKコードがある場合は、移行のための[開発者ガイダンス](#developer-guidance)をご覧ください。
 
-#### Non-Shopify Plus の日本語訳
+#### 非Shopifyプラス
 
 Shopify Plus以外の顧客の場合、情報、支払い、および配送ページをカスタマイズする必要がある場合は、[Shopify Plusにアップグレードする必要があります](https://help.shopify.com/en/manual/checkout-settings/customize-checkout-configurations/checkout-extensibility#eligibility) その後、[開発者ガイダンス](#developer-guidance)に従ってください。
 
 ### フェーズ2:2025年8月28日
 
-Shopifyは、統合で使用されている[ScriptTags](https://shopify.dev/docs/apps/build/online-store/script-tag-legacy)の`checkout.liquid`ページでのサポートを廃止します。それに応じて、私たちは2025年8月の期限に十分先立ってリリースする予定の新しいバージョンのShopify統合を積極的に構築しています。Braze製品チームからの詳細情報をお待ちください。 
+Shopifyは、統合で使用されている[ScriptTags](https://shopify.dev/docs/apps/build/online-store/script-tag-legacy)の`checkout.liquid`ページでのサポートを廃止します。これを受けて、2025年8月の期限を大幅に前倒ししてリリースする予定の Shopify 連携の新バージョンを積極的に構築しています。Braze製品チームからの詳細情報をお待ちください。 
 
-## 開発者 guidance
+## 開発者ガイダンス
 
 このガイダンスは、`checkout.liquid`の情報、配送、または支払いページにカスタムSDKコードスニペットを追加したShopify Plusの顧客に適用されます。これらのカスタマイズを行っていない場合は、このガイダンスを無視してもかまいません。
 
-`checkout.liquid`では、情報、配送、または支払いページにカスタムSDKコードスニペットを追加できなくなります。代わりに、カスタムSDKコードスニペットをサンキューページまたは注文ステータスページに追加する必要があります。これにより、チェックアウトを完了したユーザーを照合できます。
+`checkout.liquid`では、情報、配送、または支払いページにカスタムSDKコードスニペットを追加できなくなります。代わりに、カスタムSDKコードスニペットをサンキューページまたは注文ステータスページに追加する必要があります。これにより、チェックアウトが完了したユーザーを調整できます。
 1. ありがとうと注文ステータスページでBraze Web SDKを読み込む。
-2. ユーザーからメールを取得します。
+2. ユーザーからメールアドレスを取得します。
 3. `setEmail` を呼び出します。
 
 {% raw %}
@@ -55,6 +55,6 @@ braze.getUser().setEmail(<email address>);
 {% endraw %}
 
 {: start="4"}
-4\.Brazeで、メールのユーザープロファイルをマージします。
+4\.Braze で、ユーザープロファイルをメールアドレスでマージします。
 
 重複するユーザープロファイルが発生した場合は、データを効率化するために[一括マージツール]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users#bulk-merging)を使用できます。 
diff --git a/_lang/ja/_help/release_notes/deprecations/tls_deprecation.md b/_lang/ja/_help/release_notes/deprecations/tls_deprecation.md
index 1c071a529b0..61f3b0a5e82 100644
--- a/_lang/ja/_help/release_notes/deprecations/tls_deprecation.md
+++ b/_lang/ja/_help/release_notes/deprecations/tls_deprecation.md
@@ -8,25 +8,25 @@ description: "この記事では、2018年5月に完了したBrazeのTLS 1.0とT
 # TLS 1.0および1.1の廃止
 
 {% alert update %}
-Brazeは、PCIセキュリティ基準審議会の勧告に従い、TLS 1.0および1.1の両方でトランスポート・レイヤー・セキュリティ（TLS）暗号のサポートを削除した。このサポート廃止は2段階に分けて行われ、2018年5月に完了した。
+Brazeは、PCIセキュリティ基準審議会の勧告に従い、TLS 1.0および1.1の両方でトランスポート・レイヤー・セキュリティ（TLS）暗号のサポートを削除した。このサポートの廃止は2段階で実施され、2018年5月に完了したました。
 {% endalert %} 
 
 ## バックグラウンド
 
 Brazeは、TLS 1.0と1.1の両方において、既知の脆弱なトランスポート・レイヤー・セキュリティ（TLS）暗号を非推奨としている。
 
-この変更は、Brazeのプラットフォームに関する違反や問題に対応するためではなく、クラス最高のセキュリティとデータ基準を維持し、顧客とその顧客を積極的に保護するための予防措置として行われるものである。
+この変更は、Braze のプラットフォームに関連する違反や問題への対応としてではなく、セキュリティとデータに関するクラス最高の標準を維持し、クライアントとその顧客をプロアクティブに保護するための予防措置として行われます。
 
 近年、[POODLE][1]、[Heartbleed][2]、[LOGJAMなど][3]、TLSとその前身であるセキュア・ソケット・レイヤー（SSL）の両方に関連する多くの体系的なセキュリティ問題が、暗号化されたウェブ・トラフィックを脅かし、インターネットの一部をセキュリティ侵害にさらした。他のテクノロジー企業とともに、Brazeは以前から、脆弱な暗号化プロトコルや暗号が発見されると、それを無効にする措置をとってきた。たとえば、2014年にはSSLv3のサポートを解除している。
 
-最近では、PCIセキュリティ基準評議会が2015年4月に[ペイメントカード業界データセキュリティ基準][4]（PCI-DSS）の暗号化関連ガイダンスを発表した。ガイダンスでは、SSL 3.0、TLS 1.0、およびTLS 1.1でサポートされている暗号スイートの一部を、強力な暗号のプロトコルリストから除外し、インターネットユーザーのセキュリティを確保するために、企業がこれらのプロトコルや暗号のサポートを中止することを奨励している。
+最近では、PCIセキュリティ基準評議会が2015年4月に[ペイメントカード業界データセキュリティ基準][4]（PCI-DSS）の暗号化関連ガイダンスを発表した。このガイダンスでは、SSL 3.0、TLS 1.0と、TLS 1.1でサポートされている一部の暗号スイートを強力な暗号のプロトコルリストから除外し、インターネットユーザーのセキュリティを確保するために、企業がこれらのプロトコルや暗号のサポートを中止することを推奨しています。
 
 暗号スイートとは、安全なSSLまたはTLS接続をネゴシエートする際に、暗号化、認証、通信の完全性を提供するアルゴリズムの組み合わせである。ある暗号が破られる可能性があることが発見された場合（現在知られている攻撃があるかどうかにかかわらず）、その暗号には将来の攻撃を可能にする「弱点」があるとみなされる。これらのTLS暗号をPCI DSS準拠要件から除外することで、PCI DSS協議会はサービスプロバイダーに対し、クラス最高の暗号化規格のみをサポートするよう求めている。PCI DSS協議会は、TLS 1.0およびTLS 1.1のサポートを停止する暗号化要件への準拠期限を2018年6月30日に設定している。
 
-## ブレーズの償却プラン
+## Brazeの減価償却計画
 PCI DSS協議会の勧告に準拠するため、Brazeは当社サービスでサポートするTLSの最小バージョンを引き上げる予定である。私たちのコンプライアンス・プランと、それがあなたのブランドとユーザーに与える潜在的な影響について、よりよくご理解いただくために、私たちのプランには主に2つの段階がある：
 
-### 第1段階：2017年10月1日
+### フェーズ1:2017年10月1日
 
 Brazeは、BrazeのWebダッシュボードとREST APIから以下の暗号を使用する機能を削除する：
 
@@ -38,20 +38,20 @@ Brazeは、BrazeのWebダッシュボードとREST APIから以下の暗号を
 - `TLS_RSA_WITH_AES_128_GCM_SHA256`
 - `TLS_RSA_WITH_3DES_EDE_CBC_SHA`
 
-最新のウェブブラウザはすべて、より安全な暗号をサポートしているため、この変更によるBrazeダッシュボードへのアクセスへの影響はない。ただし、10月1日以降にウェブダッシュボードにアクセスした際にSSL暗号化エラーが発生した場合は、ウェブブラウザを最新バージョンにアップグレードするだけで問題を解決できる。
+この変更は、Braze ダッシュボードにアクセスする顧客に影響を与えるものではありません。なぜなら、すべての現代のウェブブラウザは、よりセキュアな暗号に対応しているからです。ただし、10月1日以降にウェブダッシュボードにアクセスした際にSSL暗号化エラーが発生した場合は、ウェブブラウザを最新バージョンにアップグレードするだけで問題を解決できる。
 
-エンジニアリングチームは、BrazeのREST APIを使ったサーバー間通信にこれらの暗号を使用していないことを確認する必要がある。もしそうであれば、BrazeのAPIを使い続けるためには、10月1日より前に、より安全な暗号を使うようにコードを更新する必要がある。しかしながら、脆弱な暗号を使用している可能性のある旧式のモバイル機器へのサポートを維持するため、Brazeは、SDKからデータを受信したAPIS上で、これらの暗号のサポートを継続する。
+開発チームは、Braze の REST API を使用したサーバー間通信にこれらの暗号を使用していないことを確認する必要があります。もしそうであれば、BrazeのAPIを使い続けるためには、10月1日より前に、より安全な暗号を使うようにコードを更新する必要がある。しかしながら、脆弱な暗号を使用している可能性のある旧式のモバイル機器へのサポートを維持するため、Brazeは、SDKからデータを受信したAPIS上で、これらの暗号のサポートを継続する。
 
-### 第2段階だ：2018年5月31日
+### フェーズ2:2018年5月31日
 
-Brazeは、2018年5月31日にすべてのBrazeサービス（Brazeダッシュボード、REST API、およびSDKと通信するAPIを含む）において、TLS 1.0およびTLS 1.1のサポートを無効にする。また、SDKデータを受け取るAPIに関連して、前節に挙げた暗号のサポートも削除する。つまり、Brazeとの間で行われるすべてのTLS 1.0および1.1通信は、この日付をもって当社のネットワークではサポートされなくなるということだ。
+Braze は、2018年5月31日に、Braze ダッシュボード、REST API、および SDK と通信する API を含むすべての Braze サービスで、TLS 1.0と TLS 1.1のサポートを無効にします。また、SDK データを受信するAPI に関連して、前のセクションに記載されている暗号のサポートも無効になります。つまり、Brazeとの間で行われるすべてのTLS 1.0および1.1通信は、この日付をもって当社のネットワークではサポートされなくなるということだ。
 
-この変更の結果、一部の古い、あるいは時代遅れのモバイルデバイス（おそらくAndroidの初期バージョンを実行しているもの）がBrazeとの通信機能を失い、Brazeへのデータ送信やBrazeからのアプリ内メッセージの受信ができなくなる可能性がある。しかし、この変更が影響するのは、ごく少数の機器に限られると予想している。影響を受けたデバイスは、PCI DSS協議会がTLS 1.0およびTLS 1.1暗号の削除日として定めた1カ月後の2018年6月30日には、PCI準拠のウェブサイトやサービスとの通信機能も失うことになる。
+この変更の結果、一部の古い、あるいは時代遅れのモバイルデバイス（おそらくAndroidの初期バージョンを実行しているもの）がBrazeとの通信機能を失い、Brazeへのデータ送信やBrazeからのアプリ内メッセージの受信ができなくなる可能性がある。しかし、この変更はごく少数のデバイスにしか影響しないことが予想される。影響を受けたデバイスは、PCI DSS協議会がTLS 1.0およびTLS 1.1暗号の削除日として定めた1カ月後の2018年6月30日には、PCI準拠のウェブサイトやサービスとの通信機能も失うことになる。
 
 ## 行動計画
-あなたのブランドがBrazeのREST APIを使用している場合、サービスの中断を避けるために、上記のリストまでにBraze sへのすべてのサーバー間コールがTLS 1.2を使用していることを確認するよう、あなたのエンジニアリングチームに相談すること。Java 7など一部のプログラミング言語では、古いバージョンのTLSがデフォルトで使用されているため、エンジニアリング・チームは、アップグレードされた暗号化要件をサポートするためにコードを変更する必要があるかもしれない。
+ブランドで Braze の REST API を利用している場合は、サービスの中断を避けるために、開発チームに相談し、上記の一覧に従って Braze へのすべてのサーバー間呼び出しで TLS 1.2 が使用されるようにしてください。Java 7など一部のプログラミング言語では、古いバージョンのTLSがデフォルトで使用されているため、エンジニアリング・チームは、アップグレードされた暗号化要件をサポートするためにコードを変更する必要があるかもしれない。
 
-アップルは2016年末からTLS 1.2を要求しているため、アップルのデバイスはBrazeの非推奨化の影響を受けない。最近のウェブブラウザも同様であるため、これらの変更がウェブSDKの使用に影響を与えるとは予想していない。ただし、Android 4.4（KitKat）以下を実行するAndroidデバイスは、デフォルトでTLS 1.2を使用しない可能性があるため、2018年5月31日までに、Android統合のいずれかを少なくともBraze SDKバージョン2.0.3（特定のデバイスがそれをサポートできる場合、デフォルトでTLS 1.2を使用する）にアップグレードする措置を講じること。
+アップルは2016年末からTLS 1.2を要求しているため、アップルのデバイスはBrazeの非推奨化の影響を受けない。これは最新の Web ブラウザーでも同様であるため、これらの変更が Web SDK の使用に影響を与えることはないと予想されます。ただし、Android 4.4 (KitKat) 以下が搭載されている Android デバイスでは、デフォルトで TLS 1.2が使用されない可能性があります。そのため、2018年5月31日までに、Android 統合を (特定のデバイスがサポートできる場合はデフォルトで TLS 1.2を使用する) Braze SDK バージョン2.0.3以上にアップグレードするステップを実行してください。
 
 最後に、TLS 1.0とTLS 1.1暗号スイートには既知の弱点があるため、すべてのお客様のセキュリティを保護するために、Brazeが非推奨化計画を早める必要があるような攻撃が将来発生する可能性がある。Brazeは、TLS 1.0および1.1プロトコルに関連するセキュリティの状態および関連する攻撃を監視し、前節で説明したタイムラインを変更するような攻撃が判明した場合は、随時お知らせする。しかし、この潜在的な影響のため、BrazeへのAPIコールがTLS 1.2でセキュアであることを確認し、今後数ヶ月のうちに最新のAndroid SDKへのアップグレードを計画するよう、エンジニアリングチームと協力することを強く推奨する。
 
diff --git a/_lang/ja/_help/release_notes/deprecations/twilio.md b/_lang/ja/_help/release_notes/deprecations/twilio.md
index ae2ec886073..c8cd3aa6b07 100644
--- a/_lang/ja/_help/release_notes/deprecations/twilio.md
+++ b/_lang/ja/_help/release_notes/deprecations/twilio.md
@@ -9,47 +9,47 @@ channel:
   - Webhook
 ---
 
-# トワイリオ
+# Twilio
 
 {% alert warning %}
-なお、Twilio Webhook Integrationのサポートは2020年1月31日に終了する。BrazeでもSMSサービスにアクセスしたい場合は、[SMSのドキュメントを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/)参照のこと。
+Twilio Webhook Integration のサポートは2020年1月31日に廃止されることにご注意ください。BrazeでもSMSサービスにアクセスしたい場合は、[SMSのドキュメントを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/)参照のこと。
 {% endalert %}
 
-この例では、Twilioの[メッセージ送信APIを介して][20]、ユーザーにSMSとMMSを送信するようにBrazeのWebhookチャンネルを設定する。便宜上、Twilioウェブフック・テンプレートがダッシュボードに含まれている。
+この例では、Twilio の[メッセージ送信API][20] を介して、SMS とMMS をユーザーに送信するようにBraze Webhook チャネルを設定します。便宜上、ダッシュボードには Twilio Webhook テンプレートが含まれています。
 
 ## HTTP URL
 
 WebhookのURLはダッシュボードでTwilioから提供される。このURLにはTwilioアカウントID(`TWILIO_ACCOUNT_SID`)が含まれているため、Twilioアカウントに固有のURLとなる。
 
-Twilioの例では、WebhookのURLは`https://api.twilio.com/2010-04-01/Accounts/TWILIO_ACCOUNT_SID/Messages.json` 。このURLは、Twilioコンソールの*Getting Started*セクションに記載されている。
+Twilio の例では、Webhook URL は `https://api.twilio.com/2010-04-01/Accounts/TWILIO_ACCOUNT_SID/Messages.json` です。このURLは、Twilioコンソールの*Getting Started*セクションに記載されている。
 
 ![Twilio_Console][28]
 
-## リクエスト・ボディ
+## リクエスト本文
 
-Twilio APIはリクエストボディがURLエンコードされていることを期待するので、Braze webhook composerでリクエストタイプを`Raw Text` に変更することから始める必要がある。リクエスト本文に必要なパラメータは、*To*、*From*、*Body*である。
+Twilio API では、リクエスト本文が URL エンコードされていると想定しているため、まず Braze Webhook コンポーザーのリクエストタイプを `Raw Text` に変更する必要があります。リクエスト本文に必要なパラメータは、*To*、*From*、*Body*である。
 
 次のスクリーンショットは、各ユーザーの電話番号に "Hello from Braze!"という本文でSMSを送信する場合のリクエストの例である。
 
-- ターゲットとするユーザーのプロフィールには、有効な電話番号が必要だ。
-- Twilioのリクエストフォーマットを満たすには、メッセージ内容に`url_param_escape` Liquidフィルターを使用する。例えば、電話番号`+12125551212` のプラス文字 (`+`) はURLエンコードされたデータでは禁止されており、`%2B12125551212` に変換される。
+- ターゲットオーディエンスのユーザープロファイルごとに、有効な電話番号が必要です。
+- Twilio のリクエスト形式に対応するため、メッセージコンテンツに `url_param_escape` Liquid フィルターを使用します。このフィルターは文字列をエンコードするため、HTML リクエストですべての文字が許可されます。例えば、電話番号 `+12125551212` のプラス文字 (`+`) はURL エンコードデータでは禁止されており、`%2B12125551212` に変換されます。
 
-![ウェブフック・ボディ][29]
+![Webhook 本文][29]
 
-## リクエスト・ヘッダとメソッド
+## リクエストヘッダーとメソッド
 
-Twilioは2つのリクエストヘッダ、リクエストContent-Typeと\[HTTP Basic Authentication][32] ]ヘッダを要求する。ウェブフック・コンポーザーの横にある歯車のアイコンをクリックし、*「新しいペアを追加*」を2回クリックして、それらをウェブフックに追加する。
+Twilio では、リクエストコンテンツタイプと \[HTTP 基本認証][32] ヘッダーの2つのリクエストヘッダーが必要です。ウェブフック・コンポーザーの横にある歯車のアイコンをクリックし、*「新しいペアを追加*」を2回クリックして、それらをウェブフックに追加する。
 
 ヘッダー名 | ヘッダー値
 --- | ---
 コンテンツタイプ | `application/x-www-form-urlencoded`
-認可 | `{% raw %}Basic {{ 'TWILIO_ACCOUNT_SID:TWILIO_AUTH_TOKEN' | base64_encode }}{% endraw %}`
+許可 | `{% raw %}Basic {{ 'TWILIO_ACCOUNT_SID:TWILIO_AUTH_TOKEN' | base64_encode }}{% endraw %}`
 
-`TWILIO_ACCOUNT_SID` と`TWILIO_AUTH_TOKEN` は必ずTwilioダッシュボードの値で置き換えること。最後に、TwilioのAPIエンドポイントはHTTP POSTリクエストを想定しているので、*HTTP Methodの*ドロップダウンでそのオプションを選択する。
+`TWILIO_ACCOUNT_SID` と`TWILIO_AUTH_TOKEN` は、必ず Twilio ダッシュボードの値で置き換えてください。最後に、Twilio のAPI エンドポイントはHTTP POST リクエストを期待しているので、*HTTP Method* のドロップダウンでそのオプションを選択します。
 
-![ウェブフック・メソッド][30]
+![Webhook メソッド][30]
 
-## リクエストをプレビューする
+## リクエストのプレビュー
 
 ウェブフックコンポーザーを使って、ランダムなユーザー、または特定の認証情報を持つユーザーのリクエストをプレビューし、リクエストが適切にレンダリングされていることを確認する。
 
diff --git a/_lang/ja/_help/support.md b/_lang/ja/_help/support.md
index 8c67a0e14ca..016ce20e479 100644
--- a/_lang/ja/_help/support.md
+++ b/_lang/ja/_help/support.md
@@ -1,7 +1,7 @@
 ---
-nav_title: ブレイズ・サポート
+nav_title: Braze支援
 article_title: サポート
-description: "このページでは、Braze製品のフィードバックを提出するためのBrazeサポートポータルを見つけるのに役立つ。このページはBrazeの顧客のみがアクセスできる。"
+description: "このページでは、Braze製品のフィードバックを提出するためのBrazeサポートポータルを見つけるのに役立つ。このページは Braze のお客様のみがアクセスできます。"
 alias: /braze_support/
 page_type: reference
 search_rank: 1
@@ -11,31 +11,31 @@ search_rank: 1
 
 ## サポートポータルにアクセスする
 
-Brazeサポートチームに連絡するには、Brazeダッシュボードに移動する。ダッシュボードで、**Support**>**Get Helpを**選択する。
+Brazeサポートチームに連絡するには、Brazeダッシュボードに移動する。ダッシュボードで、**Support** > **Get Help**を選択します。
 
 ![]({% image_buster /assets/img_archive/get_help.png %})
 
 お客様のBrazeの権限に応じて、また、お客様が指定サポート窓口（プレミアム）である場合、ケースの提出と追跡ができるBrazeサポートポータル、または標準サポートフォームのいずれかに移動する。自分がBrazeのサポート窓口かどうかわからない場合は、御社のBraze管理者、Brazeサクセスマネージャー、またはアカウントオーナーに連絡すること。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、**「ヘルプを見る**」＞「**サポート**」を選択する。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、**ヘルプの取得**> **サポート**を選択します。
 {% endalert %}
 
 ## 開発者コンソールのスクリーンショットを提供する
 
 サポートと連絡を取る際、追加情報を提供するために開発者コンソールにアクセスする必要があるかもしれない：
-- クローム
-  1. ウェブページを右クリックし、**Inspectを**クリックする。
+- Chrome
+  1. Web ページを右クリックし、**Inspect** をクリックします。
   2. 開いたウィンドウで**Console**タブをクリックする。
   3. コンソールタブのスクリーンショットを撮る。<br><br>
-- ファイアフォックス
-  1. ウェブページを右クリックし、**Inspect Elementを**クリックする。
+- Firefox
+  1. Web ページを右クリックし、**Inspect Element** をクリックします。
   2. 開いたウィンドウで**Console**タブをクリックする。
   3. コンソールタブのスクリーンショットを撮る。<br><br>
-- サファリ
-  1. 画面上部のメニューバーから「Safari」を開き、**「環境設定」を**選択する。
-  2. 上部の**Advancedを**クリックし、**Show Develop menu in menu barに**チェックを入れる。その後、ウィンドウを閉じることができる。
-  3. ウェブページを右クリックし、**Inspect Elementを**クリックする。
+- Safari
+  1. 画面上部のメニューバーにあるSafari に移動し、**Preferences** を選択します。
+  2. 上部の \[**詳細**] をクリックし、\[**メニューバーに開発メニューを表示**] の横にあるチェックボックスにチェックを入れます。その後、ウィンドウを終了できます。
+  3. Web ページを右クリックし、**Inspect Element** をクリックします。
   4. 開いたウィンドウで**Console**タブをクリックする。
   5. コンソールタブのスクリーンショットを撮る。
 
@@ -43,24 +43,24 @@ Brazeサポートチームに連絡するには、Brazeダッシュボードに
 
 ### できるだけ多くの情報を提供する
 
-提供できる見識は多ければ多いほどいい。ワークスペース、キャンペーンやセグメントのURL、関連する外部IDなどの詳細を含める。これにより、より効率的に問題を解決することができる。
+提供できるインサイトが増えれば増えるほど、より良いものになる。ワークスペース、キャンペーンやセグメントのURL、関連する外部IDなどの詳細を含める。これにより、問題のトラブルシューティングをより効率的に行うことができます。
 
 ### ユーザーのサンプルを提供する
 
-影響を受けるセグメント全体ではなく、一部のユーザーを共有する。少人数のユーザーを提供することで、調査範囲を絞り込み、調査を迅速に行うことができる。
+影響を受けるセグメント全体ではなく、一部のユーザーを共有する。より少ない数のユーザーを提供することで、範囲を絞り込み、調査を迅速化できます。
 
 ### 期待される行動と実際の行動を明確にする
 
-期待していたことと、実際に起こったことを教えてほしい。これにより、考えられる原因を絞り込むことができる。
+あなたが期待していたことと、実際にアプリが何を成し遂げたかを教えてください。これにより、考えられる原因を絞り込むことができる。
 
 ### 関連画像を添付する
 
-問題を説明するためにスクリーンショットを添付することを検討する。これらの画像を提供することで、問題の理解を大幅に助け、解決プロセスをスピードアップすることができる。
+問題を説明するためにスクリーンショットを添付することを検討する。これらの画像を提供することで、問題に対する理解が深まり、解決プロセスがスピードアップします。
 
 ### 影響を評価する
 
-問題に対処するための適切なリソースを割り当てるために、適切な重大度レベルを選択する。 
+問題に対処するために適切なリソースを割り当てるために、適切な重大度レベルを選択します。 
 
 {% alert important %}
-issueを "Critical "とマークすることは、本番インスタンスがダウンし、Braze内のすべての作業が停止したことを意味する。
+問題を \[重大] としてマークした場合、稼働中のインスタンスがダウンし、Braze 内のすべての機能が停止していることを意味します。
 {% endalert %}
\ No newline at end of file
diff --git a/_lang/ja/_hidden/archive_docs/android_11.md b/_lang/ja/_hidden/archive_docs/android_11.md
index c5f454e5c9b..6a05260833a 100644
--- a/_lang/ja/_hidden/archive_docs/android_11.md
+++ b/_lang/ja/_hidden/archive_docs/android_11.md
@@ -5,48 +5,48 @@ page_order: 9
 platform: 
   - Android
   - FireOS
-description: "このリファレンス記事では、Android 11 SDK 更新について説明し、ディープリンク、互換性SDKなどの変更点を強調します。"
+description: "このリファレンス記事では、Android 11 SDK の更新について説明し、ディープリンク、SDK 互換性などの変更点を取り上げます。"
 hidden: true
 ---
 
 # Android 11 SDK アップグレードの手引き
 
-本書では、Android 11(2020年9 月8 日リリース)で導入された関連する変更点と、Braze Android SDKインテグレーションに必要なアップグレード ステップs について説明します。
+このガイドでは、Android 11 (2020年9月8日リリース) で導入された関連のある変更と、Braze Android SDK 統合に必要なアップグレード手順について説明します。
 
 Android 11の完全なマイグレーションガイドについては、[Android 開発者 ドキュメント](https://developer.android.com/preview/migration)を参照してください。
 
 ## Braze SDK適合性
 
-Braze メッセージング 機能を引き続き使用するには、_target_ Android 11 (API 30) が[ Braze Android SDK v8.1.0+][1] にアップグレードする必要があるすべてのアプリ。
+Android 11 (API 30) を_対象とする_すべてのアプリで Brazeメッセージング機能を引き続き使用するには、[Braze Android SDK v8.1.0以降][1]にアップグレードする必要があります。
 
 {% alert important %}
-Android 11 のAPI の変更により、Braze Android SDK v8.1.0+ にアップグレードしないAndroid 11 をターゲットとするアプリでは、Braze UI コンポーネントからのディープリンクに問題が発生し、カスタムHTML アプリ内メッセージs が正しく表示されません。
+Android 11 の API の変更により、Braze Android SDK v8.1.0以降にアップグレードしていない Android 11向けのアプリでは、Braze UI コンポーネントからのディープリンクで問題が発生し、カスタム HTML アプリ内メッセージが正常に表示されません。
 {% endalert %}
 
 ### ディープリンク
 
-Android 11 以降(API Version 30+)をターゲットとするアプリケーションは、[ Braze Android SDK v8.1.0][1] にアップグレードして、Braze メッセージ内のディープリンクを引き続き使用する必要があります。Android 11 API の変更により、少なくともAndroid SDK v8.1.0 にアップグレードしないアプリ s では、Brazeメッセージ(アプリ内メッセージまたはコンテンツカード) 内の深いリンクに問題が発生します。
+Android 11 以降(API Version 30+)をターゲットとするアプリケーションは、[ Braze Android SDK v8.1.0][1] にアップグレードして、Braze メッセージ内のディープリンクを引き続き使用する必要があります。Android 11の API の変更により、Android SDK v8.1.0以降にアップグレードしないアプリでは、Braze メッセージ (アプリ内メッセージまたはコンテンツカード) 内のディープリンクで問題が発生します。
 
 ### HTML アプリ内メッセージs
 
-Android 11 以降(API バージョン30 以降) をターゲットとするアプリは、カスタムHTML アプリ内メッセージs を引き続き使用するには、Braze Android SDK v8.1.0 にアップグレードする必要があります。Android 11 WebView 設定 s の変更により、[ Braze Android SDK v8.1.0][1] にアップグレードするまで、HTML アプリ内メッセージ s はAndroid 11 ターゲットアプリs に正しく表示されません。 
+Android 11以降 (APIバージョン30以上) を対象にしたアプリは、カスタム HTML のアプリ内メッセージを引き続き使用するには、Braze Android SDK v8.1.0にアップグレードする必要があります。Android 11 WebView の設定が変更されたため、Android 11 対象アプリでは[Braze Android SDK v8.1.0][1] にアップグレードするまで、HTML アプリ内メッセージが適切に表示されません。 
 
-### ロケーション権限
+### 位置情報の許可
 
-ロケーションアクセス許可を使用するアプリケーションは、ロケーションアクセスをリクエストするときに、Androidの[ベストプラクティス](https://developer.android.com/preview/privacy/location#change-details)に従う必要があります。これらの場所更新s では、Brazeインテグレーションを変更する必要はありません。
+ロケーションアクセス許可を使用するアプリケーションは、ロケーションアクセスをリクエストするときに、Androidの[ベストプラクティス](https://developer.android.com/preview/privacy/location#change-details)に従う必要があります。これらの位置情報の更新には、Braze 統合への変更は必要ありません。
 
 ## Android 11の挙動変化
 
-### 許可を1 回許可
+### 1回限りのアクセスを許可する
 
-ユーザは、ロケーションコレクションなどの権限を1 回限りで付与できるようになりました(詳細については、[ Android Docs](https://developer.android.com/preview/privacy/location#one-time-access) を参照してください)。アプリがクローズされた後、またはバックグラウンドで十分な時間が経過すると、その権限は自動的に取り消されます。アプリは、今後必要に応じてこの権限を再要求する必要があります。ロケーション権限を要求するための推奨フローにすでに従うアプリケーションは、1 回限りの権限をサポートします。
+ユーザは、ロケーションコレクションなどの権限を1 回限りで付与できるようになりました(詳細については、[ Android Docs](https://developer.android.com/preview/privacy/location#one-time-access) を参照してください)。アプリが閉じられた後、またはバックグラウンドで十分な時間が経過すると、その権限は自動的に取り消されます。アプリは、今後必要に応じてこの権限を再要求する必要があります。位置情報の許可を要求するための推奨フローにすでに従っているアプリでは、1回限りのアクセス許可がサポートされます。
 
 ![][3]{: height="230px" }
 
-### バックグラウンドロケーション許可
+### バックグラウンドでの位置情報許可
 
-Android 11 は、最初にフォアグラウンドロケーション権限をリクエストするためにアプリ s を必要とします。その後、アプリがバックグラウンドに入った後、バックグラウンドロケーション権限を再度ユーザーに要求する場合があります。
-Geofencesを使用するお客様は、アプリがバックグラウンド場所の権限の収集に関するAndroidの推奨事項に従っていることを確認する必要があります。詳細については、[Android文書](https://developer.android.com/preview/privacy/location#background-location)を参照してください。
+Android 11 では、アプリは最初にフォアグラウンドでの位置情報の許可を要求する必要があり、アプリがバックグラウンドになったら、バックグラウンドでの位置情報の許可をユーザーに再度求めることができます。
+ジオフェンスを使用する顧客は、バックグラウンドでの位置情報の許可の収集に関する Android の推奨事項にアプリが従っていることを確認する必要があります。詳細については、[Android文書](https://developer.android.com/preview/privacy/location#background-location)を参照してください。
 
 [1]: https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#810
 [3]: {% image_buster /assets/img/android/android-11-one-time-permission.svg %}
diff --git a/_lang/ja/_hidden/archive_docs/android_12.md b/_lang/ja/_hidden/archive_docs/android_12.md
index 3d3ce15a1dd..2cba505b10e 100644
--- a/_lang/ja/_hidden/archive_docs/android_12.md
+++ b/_lang/ja/_hidden/archive_docs/android_12.md
@@ -1,6 +1,6 @@
 ---
-nav_title: アンドロイド12アップグレードガイド
-article_title: アンドロイド12アップグレードガイド
+nav_title: Android 12アップグレードガイド
+article_title: Android 12アップグレードガイド
 page_order: 9
 permalink: "/android_12/"
 layout: "dev_guide"
@@ -8,23 +8,23 @@ hidden: true
 platform: 
   - Android
   - FireOS
-description: "このリファレンス記事では、Android 12 SDKのアップデートを取り上げ、ディープリンクやSDKの互換性などの変更点を紹介している。"
+description: "このリファレンス記事では、Android 12 SDK の更新について説明し、ディープリンク、SDK 互換性などの変更点を取り上げます。"
 ---
 
 # Android 12 SDK アップグレードガイド
 
-このガイドでは、Android 12 (2021)で導入された関連する変更と、Braze Android SDK統合に必要なアップグレード手順について説明する。
+このガイドでは、Android 12 (2021) で導入された関連のある変更と、Braze Android SDK 統合に必要なアップグレード手順について説明します。
 
-Android 12への完全な移行ガイドについては、[Android開発者向けドキュメントを](https://developer.android.com/about/versions/12)参照のこと。
+Android 12 の完全な移行ガイドについては、[Android 開発者のドキュメント](https://developer.android.com/about/versions/12)を参照してください。
 
 ## Braze SDKの互換性
 
-Android 12をターゲットとする場合は、[Braze Android SDK v13.1.2+を][1]使用する必要がある。まだアンドロイド12をターゲットにしていない場合は、アップグレードすることをお勧めする。
+Android 12 を対象とする場合は、[Braze Android SDK v 13.1.2以降][1]を使用する必要があります。まだ Android 12 を対象にしていない場合でも、アップグレードをお勧めします。
 
 **Braze Android SDKをアップグレードしないとどうなるか？**
 
-* Androidの[終了システムダイアログの](https://developer.android.com/about/versions/12/behavior-changes-all#close-system-dialogs)変更により、Braze Android SDKの古いバージョンでは、Android 12を実行しているデバイスでプッシュ通知を受信すると警告が記録される。この動作は、アプリがアンドロイド12をターゲットにしていなくても発生する。
-* [コンポーネントのエクスポート](https://developer.android.com/about/versions/12/behavior-changes-12#exported)、[保留中のインテント](https://developer.android.com/about/versions/12/behavior-changes-12#pending-intent-mutability)、および[通知トランポリンの](https://developer.android.com/about/versions/12/behavior-changes-12#notification-trampolines)変更は、アプリをコンパイルする能力に影響を与えたり、Braze SDKの初期化を妨げる可能性がある。この動作は、アンドロイド12をターゲットにしたアプリでのみ発生する。
-* [カスタムプッシュ通知の](https://developer.android.com/about/versions/12/behavior-changes-12#custom-notifications)変更により、新しい[Androidインライン画像プッシュ]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/inline_image_push/)機能のレイアウトが変更された。この動作は、アンドロイド12をターゲットにしたアプリでのみ発生する。
+* Androidの[終了システムダイアログの](https://developer.android.com/about/versions/12/behavior-changes-all#close-system-dialogs)変更により、Braze Android SDKの古いバージョンでは、Android 12を実行しているデバイスでプッシュ通知を受信すると警告が記録される。この動作は、アプリがAndroid 12 を対象にしていない場合でも発生します。
+* [コンポーネントのエクスポート](https://developer.android.com/about/versions/12/behavior-changes-12#exported)、[保留中のインテント](https://developer.android.com/about/versions/12/behavior-changes-12#pending-intent-mutability)、[通知トランポリン](https://developer.android.com/about/versions/12/behavior-changes-12#notification-trampolines)の変更は、アプリをコンパイルする機能に影響を与えたり、Braze SDK の初期化を妨げたりする可能性があります。この動作は、Android 12 を対象とするアプリケーションでのみ発生します。
+* [カスタムプッシュ通知の](https://developer.android.com/about/versions/12/behavior-changes-12#custom-notifications)変更により、新しい[Androidインライン画像プッシュ]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/inline_image_push/)機能のレイアウトが変更された。この動作は、Android 12 を対象とするアプリケーションでのみ発生します。
 
 [1]: https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#1312
diff --git a/_lang/ja/_hidden/archive_docs/baidu_integration.md b/_lang/ja/_hidden/archive_docs/baidu_integration.md
index 3e6fb20e342..7fedfeb7b5c 100644
--- a/_lang/ja/_hidden/archive_docs/baidu_integration.md
+++ b/_lang/ja/_hidden/archive_docs/baidu_integration.md
@@ -1,19 +1,19 @@
 ---
-nav_title: 百度の統合
+nav_title: Baidu の統合
 article_title: バイドゥ・プッシュ通知のAndroidへの統合
 platform: Android
 permalink: /baidu_integration/
-description: "この記事では、百度アンドロイドとの統合をセットアップする方法を紹介する。"
+description: "この記事では、Baidu Android 統合の設定方法について説明します。"
 hidden: true
 ---
-# 百度の統合
+# Baidu の統合
 {% multi_lang_include archive/baidu_deprecation.md %}
 
-Brazeは、\[Baidu Cloud Push][14].Baidu Cloud Push **を使用すると、**Baidu アプリストアを介してアプリを配布する必要がありません。
+Braze は、\[Baidu Cloud Push][14] を使用して Android デバイスにプッシュ通知を送信できます。Baidu Cloud Push を使用すると、Baidu アプリストアを介してアプリを配布する必要が**ありません**。
 
-## ステップ 1:百度のアカウントを作成する
+## ステップ 1:Baidu のアカウントを作成する
 
-百度アカウントを作成するには、[百度ポータルに][7]アクセスし、**登录**（ログイン）をクリックすると、ログインまたは新しいアカウントを作成するためのダイアログが表示される。
+Baidu アカウントを作成するには、\[[Baidu ポータル][7]] にアクセスし、\[**登录**] (ログイン) をクリックすると、ログインまたは新しいアカウントを作成するためのダイアログが表示されます。
 
 ![][33]
 
@@ -21,47 +21,47 @@ Brazeは、\[Baidu Cloud Push][14].Baidu Cloud Push **を使用すると、**Bai
 
 ![][38]{: style="max-width:70%;"}
 
-アカウント作成ページにユーザー名、電話番号、パスワードを入力する。次に、検証コードを受け取るボタンをクリックする。Baiduから認証コードを含むSMSメッセージが届く。最後に使用許諾契約書に同意し、**注册**(アカウント作成)を押して登録します。これらのセットアップ手順に失敗した場合は、この[ログイン記事で](https://www.adchina.io/how-to-open-a-baidu-account-outside-china/)説明されているように、Baiduクラウドログイン経由で登録を試みる。
+アカウント作成ページにユーザー名、電話番号、パスワードを入力する。次に、\[確認コードを受信] ボタンをクリックします。Baiduから認証コードを含むSMSメッセージが届く。最後に、使用許諾契約書に同意し、\[**注册**] (アカウントの作成) をクリックして登録します。これらの設定手順に失敗した場合は、この[ログイン記事](https://www.adchina.io/how-to-open-a-baidu-account-outside-china/)で説明されているように、Baidu Cloud ログイン経由での登録を試します。
 
 ![百度サインアップページ][17]{: style="max-width:80%;"}
 
-## ステップ2:百度の開発者として登録する
+## ステップ2:Baidu の開発者として登録する
 
-次に、百度の開発者として登録しなければならない。まず、\[Baidu developer portal][36] ] にアクセスし、**注册**(create new developer account) を選択して登録を開始する。
+次に、Baidu の開発者として登録する必要があります。まず、\[Baidu developer portal][36] ] にアクセスし、**注册**(create new developer account) を選択して登録を開始する。
 
 ![][37]
 
-登録ページで、アカウントの種類（個人用には个人、ビジネス用には公司）と開発者の種類を選択する（ほとんどの場合、開発者があらかじめ選択されており、正しい）。氏名、略歴、電話番号（カッコ内に国番号を含む）を入力する（例：(1)xxxxxxxxxx）。**发送**验证码（認証コードを送信）をクリックし、次の行に認証コードを入力する。次の2つのフィールド、開発者のウェブサイトと開発者のロゴは任意である。使用許諾契約に同意し、**提交**（submit）をクリックして送信する。これでBaiduの開発者アカウントを取得したことになる。
+登録ページで、アカウントの種類 (個人用には「个人」、ビジネス用には「公司」) と開発者の種類を選択する (開発者があらかじめ選択されており、ほとんどの場合正しい)。氏名、略歴、電話番号（カッコ内に国番号を含む）を入力する（例：(1)xxxxxxxxxx）。\[**发送验证码**] (確認コードを送信) をクリックし、次の行に確認コードを入力します。次の2つのフィールド、開発者のウェブサイトと開発者のロゴは任意である。使用許諾契約に同意し、**提交**（submit）をクリックして送信する。これでBaiduの開発者アカウントを取得したことになる。
 
 ![][13]
 
-## ステップ 3:百度にアプリケーションを登録する
+## ステップ 3:Baidu にアプリケーションを登録する
 
-百度にアプリケーションを登録するには、\[百度プロジェクトポータル][11] ]にアクセスし、**创建**工程（プロジェクトの作成）をクリックする。
+Baidu にアプリケーションを登録するには、\[Baidu プロジェクトポータル][11] にアクセスし、\[**创建工程**] (プロジェクトの作成) をクリックします。
 
 ![][10]
 
-次のページで、アプリケーション名を入力する。次の2つのチェックボックスは、百度の追加サービスを有効にするためのものである。ほとんどの場合、これらは空白のままでよい。
+次のページで、アプリケーション名を入力します。次の2つのチェックボックスは、Baidu の追加サービスを有効にするためのものです。ほとんどの場合、これらは空白のままでよい。
 
 ![][26]
 
-アプリケーションをセットアップすると、APIキーを含むアプリケーションに関する情報を表示するコンソールが表示される。次に、サイドバーの「**云**推送（クラウドプッシュ）」に移動する。次のページで、**推送设置**（プッシュを設定する）をクリックする。
+アプリケーションをセットアップすると、APIキーを含むアプリケーションに関する情報を表示するコンソールが表示される。次に、サイドバーの \[**云推送**] (クラウドプッシュ)」に移動します。次のページで、**推送设置**（プッシュを設定する）をクリックする。
 
 ![][14]
 
 ![][29]
 
-次のページで、アプリのパッケージ名（例えば、`com.braze.sample` ）を入力し、メッセージをキャッシュするかどうか、キャッシュする場合はその期間（時間単位）を指定する。これは、バイドゥに対して、オフラインのユーザーへのメッセージ送信をいつまで継続するかを示すものである。**保存设置**（設定を保存する）をクリックして保存する。
+次のページで、アプリのパッケージ名（例えば、`com.braze.sample` ）を入力し、メッセージをキャッシュするかどうか、キャッシュする場合はその期間（時間単位）を指定する。これは、Baidu に対して、オフラインユーザーにメッセージの送信を試行し続ける時間を示します。**保存设置**（設定を保存する）をクリックして保存する。
 
 ![][39]
 
-## ステップ 4:アプリケーションに百度を追加する
+## ステップ 4:アプリケーションに Baidu を追加する
 
-Baidu push SDK portal][40] ] にアクセスし、最新のBaidu Cloud Push Android SDKをダウンロードする。
+\[Baidu プッシュ SDK ポータル][40] にアクセスし、最新の Baidu Cloud Push Android SDK をダウンロードします。
 
 ![][41]
 
-SDKの中には、プッシュ・サービスのjarとプラットフォーム固有のネイティブ・ライブラリがある。これらをプロジェクトに組み込む。あなたのアプリが、百度が現在サポートしているSDKの最高バージョンをターゲットにしていることを確認する。このドキュメントは、Baidu Cloud push Android SDK バージョン`4.6.2.38` のものである。
+SDK の中には、プッシュサービスの jar とプラットフォーム固有のネイティブライブラリがあります。これらをプロジェクトに組み込む。ご使用のアプリが現在 Baidu でサポートされている最新の SDK バージョンを対象にしていることを確認します。このドキュメントは、Baidu Cloud push Android SDK バージョン`4.6.2.38` を対象としています。
 
 以下の必要なBaiduパーミッションをアプリケーションの`AndroidManifest.xml` に追加する。
 
@@ -76,7 +76,7 @@ SDKの中には、プッシュ・サービスのjarとプラットフォーム
     <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
 ```
 
-Baiduのライブラリには、受信したプッシュ・メッセージを処理するブロードキャスト・レシーバーが含まれている。アプリケーションの`AndroidManifest.xml` 、`<application>` 要素の中で内部百度レシーバーを宣言する。
+Baiduのライブラリには、受信したプッシュ・メッセージを処理するブロードキャスト・レシーバーが含まれている。アプリケーションの `AndroidManifest.xml` 内の `<application>` 要素内で内部 Baidu レシーバーを宣言します。
 
 ```xml
   <!-- 用于接收系统消息以保证 PushService 正常运行 -->
@@ -116,7 +116,7 @@ Baiduのライブラリには、受信したプッシュ・メッセージを処
       </service>
 ```
 
-また、プッシュ・メッセージや通知の着信をリッスンするブロードキャスト・レシーバーも作成する必要がある。アプリケーションの`AndroidManifest.xml` 、`<application>` 要素の中で受信機を宣言する。このレシーバーは、`com.baidu.android.pushservice.PushMessageReceiver` を拡張し、百度プッシュ・サービスからのイベント更新を受け取るメソッドを実装する必要がある。
+また、プッシュメッセージや通知の着信をリッスンするブロードキャストレシーバーも作成する必要があります。アプリケーションの `AndroidManifest.xml`、`<application>` 要素の中でレシーバーを宣言します。このレシーバーは、`com.baidu.android.pushservice.PushMessageReceiver` を拡張し、Baidu プッシュサービスからイベント更新を受け取るメソッドを実装する必要があります。
 
 ```xml
       <receiver android:name=".MyPushMessageReceiver">
@@ -128,13 +128,13 @@ Baiduのライブラリには、受信したプッシュ・メッセージを処
       </receiver>
 ```
 
-メイン・アクティビティの`onCreate()` ・メソッドに、以下の行を追加し、アプリケーションを百度に登録し、受信プッシュ・メッセージのリッスンを開始する。Your-API-Key "をプロジェクトのBaidu API Keyに置き換えてほしい。
+メインアクティビティの `onCreate()` メソッドに次の行を追加します。これにより、アプリケーションが Baidu に登録され、着信プッシュメッセージのリッスンが開始されます。「Your-API-Key」をプロジェクトの Baidu API キーに置き換えてください。
 
 ```
 PushManager.startWork(getApplicationContext(), PushConstants.LOGIN_TYPE_API_KEY, "Your-API-Key");
 ```
 
-最後に、ユーザーをBrazeに登録する必要がある。このステップで作成した百度放送受信機の`onBind()` メソッドで、`Braze.registerAppboyPushMessages(channelId)` を使って`channelId` をBrazeに送信する。
+最後に、ユーザーをBrazeに登録する必要がある。このステップで作成した Baidu ブロードキャストレシーバーの `onBind()` メソッドで、`Braze.registerAppboyPushMessages(channelId)` を使用して `channelId` を Braze に送信します。
 
 {% tabs %}
 {% tab JAVA %}
@@ -153,9 +153,9 @@ Braze.getInstance(context).setRegisteredPushToken(channelId)
 {% endtab %}
 {% endtabs %}
 
-## ステップ 5: プッシュオープンを登録する
+## ステップ 5: プッシュ開封を登録する
 
-Baiduは、JSON形式のプッシュ・メッセージで余分なキー・バリュー・ペアの送信をサポートしている。ブロードキャスト・レシーバーの`public void onNotificationClicked(Context context, String title, String description, String customContentString)` メソッドは、ユーザーが受信プッシュ・メッセージをクリックするたびに呼び出される。パラメータ`customContentString` には、JSON形式のエクストラが含まれる。Brazeからのすべてのメッセージには、以下の2つのキーと値のペアが含まれる：
+Baiduは、JSON形式のプッシュ・メッセージで余分なキー・バリュー・ペアの送信をサポートしている。ブロードキャストレシーバーの `public void onNotificationClicked(Context context, String title, String description, String customContentString)` メソッドは、ユーザーが着信プッシュメッセージをクリックするたびに呼び出されます。パラメータ`customContentString` には、JSON形式のエクストラが含まれる。Brazeからのすべてのメッセージには、以下の2つのキーと値のペアが含まれる：
 
   ```json
   {
@@ -164,7 +164,7 @@ Baiduは、JSON形式のプッシュ・メッセージで余分なキー・バ
   }
   ```
 
-`onNotificationClicked` があなたの Baidu レシーバーに呼び出されるたびに、レシーバーは`customContentString` を含む \[Intent][44] ] をあなたのアプリケーションに送信する必要がある。あなたのアプリケーションは、`customContentString` を使用してBrazeにクリックを記録する。
+`onNotificationClicked` が Baidu レシーバーと呼ばれるたびに、レシーバーは `customContentString` を含むアプリケーションに \[Intent][44] を送信する必要があります。あなたのアプリケーションは、`customContentString` を使用してBrazeにクリックを記録する。
 
 次のサンプルコードは、`customContentString` をBrazeに渡し、クリックのログを取る：
 
@@ -189,7 +189,7 @@ BrazeNotificationUtils.logBaiduNotificationClick(context, customContentString)
 
 ## ステップ 6: エクストラ
 
-Brazeが使用する予約キー以外に、`customContentString` パラメーターには、ユーザー定義のカスタムキーと値のペアがすべて含まれる。キーと値のペアを取り出すには、`customContentString` をJSONObjectでラップし、エキストラを取り出す：
+Braze が使用する予約キー以外に、`customContentString` パラメーターには、ユーザー定義のカスタムのキーと値のペアがすべて含まれています。キーと値のペアを抽出するには、JSONObject で `customContentString` をラップし、エキストラを取得します。
 
 {% tabs %}
 {% tab JAVA %}
@@ -218,9 +218,9 @@ try {
 {% endtab %}
 {% endtabs %}
 
-## ステップ 7:百度キーを設定する
+## ステップ 7:Baidu キーを設定する
 
-BrazeダッシュボードにBaidu API KeyとBaidu Secret Keyを入力する必要がある。どちらのキーも百度のアプリケーション・コンソールから利用できる。
+Braze ダッシュボードに Baidu API キーとBaidu シークレットキーを入力する必要があります。どちらのキーも Baidu のアプリケーションコンソールから利用できます。
 
 **Manage Settings**ページで、Android Chinaアプリを選択し、プッシュ通知セクションにBaidu API KeyとBaidu Secret Keyを入力する。
 
@@ -228,11 +228,11 @@ BrazeダッシュボードにBaidu API KeyとBaidu Secret Keyを入力する必
 
 ## その他のリソース
 
-- [百度ポータル][7]
+- [Baidu ポータル][7]
 - \[百度開発者ポータル][36]
 - \[百度プロジェクトポータル][11]
 - \[百度プッシュSDKポータル][40]
-- \[バイドゥ統合ドキュメント][43]
+- \[Baidu 統合ドキュメント][43]
 
 [7]: https://www.baidu.com/
 [10]: {% image_buster /assets/img_archive/baidu_project.png %}
@@ -240,7 +240,7 @@ BrazeダッシュボードにBaidu API KeyとBaidu Secret Keyを入力する必
 [13]: {% image_buster /assets/img_archive/baidu_dev_reg.png %}
 [14]: {% image_buster /assets/img_archive/baidu_app_console.png %}
 [17]: {% image_buster /assets/img_archive/baidu_signup.png %}
-[19]: {% image_buster /assets/img_archive/baidu_api_key.png %} 「APIKey」である。
+[19]: {% image_buster /assets/img_archive/baidu_api_key.png %} 「APIKey」
 [26]: {% image_buster /assets/img_archive/baidu_app_name.png %}
 [29]: {% image_buster /assets/img_archive/baidu_continue.png %}
 [33]: {% image_buster /assets/img_archive/baidu_portal.png %}
diff --git a/_lang/ja/_hidden/archive_docs/interactive.md b/_lang/ja/_hidden/archive_docs/interactive.md
index 3ddda7bf3a4..16a496d019a 100644
--- a/_lang/ja/_hidden/archive_docs/interactive.md
+++ b/_lang/ja/_hidden/archive_docs/interactive.md
@@ -41,8 +41,8 @@ justify-content: flex-start;
 padding-top: 0px;
 }
   \#main_content #article-main #swagger-ui .auth-container input\[type=text]{
-というボーダーラインがある：1px solid #f4f4f7;
-幅がある：100%;
+境界線:1px solid #f4f4f7;
+幅:100%;
 
 }
 \#main_content #article-main #swagger-ui .opblock-tag-section a {
@@ -80,7 +80,7 @@ width: 100%;
 width: auto !important;
 }
 \#swagger-ui table thead {
-  背景：透明；
+  バックグラウンド：透明；
 
 }
 \#swagger-ui  table thead tr td, #swagger-ui table thead tr th {
diff --git a/_lang/ja/_hidden/archive_docs/previous_in-app_message_generations.md b/_lang/ja/_hidden/archive_docs/previous_in-app_message_generations.md
index 790f6735807..d509c8b121c 100644
--- a/_lang/ja/_hidden/archive_docs/previous_in-app_message_generations.md
+++ b/_lang/ja/_hidden/archive_docs/previous_in-app_message_generations.md
@@ -1,6 +1,6 @@
 ---
 nav_title: 以前の世代
-article_title: 以前のアプリ内メッセージ世代
+article_title: 以前のアプリ内メッセージ生成
 page_order: 20
 page_type: reference
 description: "この記事では、Brazeのアプリ内メッセージに関する以前の情報を確認します。"
@@ -20,7 +20,7 @@ hidden : true
 これにより、アプリ内メッセージに関する以前の情報が確認されます。最新のアプリ内メッセージ生成に関する最新情報については、[アプリ内メッセージ概要ドキュメント]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/)をご覧ください。
 
 {% details 全画面 %}
-これらは最も魅力的ですが、ユーザーの画面全体を覆うため、最も侵入的でもあります。それらは大きくてリッチな画像を表示するのに最適で、重要な新機能や期限切れのプロモーションなど、非常に重要な情報を伝えるのに役立ちます。それらはユーザーエクスペリエンスをより妨げるため、最優先のコンテンツには控えめに使用してください。
+これらは最も魅力的ですが、ユーザーの画面全体を覆うため、最も侵入的でもあります。サイズが大きくリッチな画像を表示するのに適しており、重要な新機能や期限が迫っているプロモーションなど、非常に重要な情報を伝えるのに役立ちます。これらはユーザーエクスペリエンスの混乱を招くため、最優先のコンテンツには控えめに使用してください。
 
 ![全画面メッセージ]({% image_buster /assets/img_archive/braze_fullscreen.png %}){: style="max-width:80%;"}
 
@@ -28,13 +28,13 @@ hidden : true
 
 - ヘッダーと本文のテキスト
 - 大きな画像
-- 2つまでのクリック動作とディープリンクを持つアクションボタン
+- それぞれ異なるクリック動作とディープリンクを備えた、最大2つのコールトゥアクションボタン
 - ヘッダーと本文テキスト、ボタン、バックグラウンドの異なる色
 - キーと値のペア
 
 {% enddetails %}
 {% details  モーダル %}
-これらのメッセージはフルスクリーンメッセージほど侵入的ではありません。ユーザーがアプリのUIの一部を見ることができるからです。それらにはボタンや画像が含まれているため、モーダルメッセージは、よりインタラクティブで視覚的なキャンペーンを望む場合、スライドアップよりも優れたオプションかもしれません。これらは、中程度の優先度のコンテンツ、例えばアプリの更新や緊急でない取引やイベントに最適です。
+これらのメッセージはフルスクリーンメッセージほど侵入的ではありません。ユーザーがアプリのUIの一部を見ることができるからです。モーダルメッセージにはボタンと画像が含まれているため、よりインタラクティブで視覚的なキャンペーンが必要な場合は、スライドアップよりもモーダルメッセージの方が適しています。これらは、アプリの更新や緊急ではない取引やイベントなど、中優先度のコンテンツに最適です。
 
 ![モーダルメッセージ]({% image_buster /assets/img_archive/braze_modal.png %}){: style="max-width:80%;"}
 
@@ -42,7 +42,7 @@ hidden : true
 
 - ヘッダーと本文のテキスト
 - 画像またはカスタマイズ可能なバッジアイコン
-- 2つまでのクリック動作とディープリンクを持つアクションボタン
+- それぞれ異なるクリック動作とディープリンクを備えた、最大2つのコールトゥアクションボタン
 - ヘッダーと本文テキスト、ボタン、バックグラウンドの異なる色
 - キーと値のペア
 
@@ -73,9 +73,9 @@ hidden : true
 {% details メールキャプチャメッセージ %}
 メールキャプチャメッセージを使用すると、サイトのユーザーにメールアドレスの送信を促すことができ、その後、Brazeシステム内で利用可能になり、すべてのメッセージングキャンペーンで使用できます。
 
-![メール capture message]({% image_buster /assets/img_archive/web-email-capture.png %}){: style="max-width:60%;"}
+![メールキャプチャメッセージ]({% image_buster /assets/img_archive/web-email-capture.png %}){: style="max-width:60%;"}
 
->  Web SDKを介してアプリ内メッセージでメールキャプチャを有効にするには、Brazeに`allowUserSuppliedJavascript`初期化オプションを提供する必要があります。例えば、`braze.initialize('YOUR-API_KEY', {allowUserSuppliedJavascript: true})`。これはセキュリティ上の理由です - アプリ内メッセージのHTMLはJavaScriptを実行できるため、サイト管理者がそれらを有効にする必要があります。
+>  Web SDK を介してメールキャプチャアプリ内メッセージを有効にするには、`allowUserSuppliedJavascript` 初期化オプションを Braze に指定する必要があります。例: `braze.initialize('YOUR-API_KEY', {allowUserSuppliedJavascript: true})`。これはセキュリティ上の理由によるもので、HTML のアプリ内メッセージは JavaScript を実行できるため、サイト管理者が有効にする必要があります。
 
 **カスタマイズ可能な機能**
 
@@ -89,17 +89,17 @@ hidden : true
 
 {% details カスタムHTMLメッセージ %}
 
-Brazeのすぐに使えるアプリ内メッセージはさまざまな方法でカスタマイズできますが、HTML、CSS、およびJavaScriptを使用して設計および構築されたメッセージを使用すると、キャンペーンの外観と感触をさらにコントロールできます。いくつかの簡単な構成で、あらゆるニーズに合わせたカスタム機能とブランディングを解放できます。HTMLアプリ内メッセージを使用すると、メッセージの外観と感触をより細かくコントロールでき、HTML5でサポートされているものはすべてBrazeでもサポートされます。
+Brazeのすぐに使えるアプリ内メッセージはさまざまな方法でカスタマイズできますが、HTML、CSS、およびJavaScriptを使用して設計および構築されたメッセージを使用すると、キャンペーンの外観と感触をさらにコントロールできます。いくつかの簡単な構成で、任意のニーズに合わせてカスタム機能とブランディングを解放できます。HTMLアプリ内メッセージを使用すると、メッセージの外観と感触をより細かくコントロールでき、HTML5でサポートされているものはすべてBrazeでもサポートされます。
 
 **JavaScriptブリッジ（appboyBridge）**
 
-HTMLアプリメッセージは、Braze Web SDK への JavaScript "ブリッジ" インターフェイスをサポートしており、ユーザーがリンク付きの要素をクリックしたり、コンテンツに関与したりすると、カスタム Braze アクションをトリガーすることができます。次のJavaScriptメソッドは、BrazeのHTMLアプリ内メッセージでサポートされています:
+HTML アプリ内メッセージは、Braze Web SDK への JavaScript 「ブリッジ」インターフェイスをサポートしているため、ユーザーがリンクを含む要素をクリックしたとき、またはコンテンツを操作したときに、カスタム Braze アクションをトリガーできます。次のJavaScriptメソッドは、BrazeのHTMLアプリ内メッセージでサポートされています:
 
 {% multi_lang_include archive/appboyBridge.md platform="web" %}
 
 さらに、分析トラッキングのために、HTML内の`<a>`または`<button>`要素は、アプリ内メッセージに関連付けられたキャンペーンへの「クリック」アクションを自動的に記録します。「ボタンクリック」を「ボディクリック」の代わりに記録するには、リンクのhrefにクエリ文字列値abButtonIdを指定する（例：`<a href="http://mysite.com?abButtonId=0">click me</a>`）、またはHTML要素にidを指定します（例：`<a id="0" href="http://mysite.com">click me</a>`）。現在受け入れられているボタンIDは「0」と「1」のみです。ボタンIDが0のリンクはダッシュボード上で「ボタン1」として表示され、ボタンIDが1のリンクは「ボタン2」として表示されます。
 
->  Web SDKを通じてHTMLのアプリ内メッセージを有効にするには、Brazeに`allowUserSuppliedJavascript`初期化オプションを提供する必要があります。例えば`braze.initialize('YOUR-API_KEY', {allowUserSuppliedJavascript: true})`。これはセキュリティ上の理由です - アプリ内メッセージのHTMLはJavaScriptを実行できるため、サイト管理者がそれらを有効にする必要があります。
+>  Web SDK を介して HTML アプリ内メッセージを有効にするには、`allowUserSuppliedJavascript` 初期化オプションを Braze に指定する必要があります。例: `braze.initialize('YOUR-API_KEY', {allowUserSuppliedJavascript: true})`。これはセキュリティ上の理由によるもので、HTML のアプリ内メッセージは JavaScript を実行できるため、サイト管理者が有効にする必要があります。
 
 {% enddetails %}
 
@@ -147,12 +147,12 @@ HTMLアプリメッセージは、Braze Web SDK への JavaScript "ブリッジ"
 Braze は、いくつかの理由から画像や HTML アセットの zip ファイルをできるだけ小さく保つことをお勧めします:
 
 - HTMLおよび画像メッセージのペイロードが小さいほど、より速くダウンロードされ、顧客にとってより迅速かつ確実に表示されます。
-- より小さいHTMLおよび画像メッセージのペイロードは、顧客のデータコストも抑えることができます。Brazeのアプリ内メッセージは、セッション開始時にバックグラウンドでダウンロードされるため、選択した任意の基準に基づいてリアルタイムでトリガーされます。その結果、1MBのHTMLインアプリメッセージが10件ある場合、たとえそれらのメッセージをすべてトリガーしなかったとしても、顧客はすべて10MBのデータ料金が発生します。これは時間の経過とともにすぐに加算される可能性がありますが、アプリ内メッセージはキャッシュされ、セッションごとに再ダウンロードされません。
+- HTML と画像メッセージのペイロードを小さくすれば、顧客のデータコストも抑えられます。Brazeのアプリ内メッセージは、セッション開始時にバックグラウンドでダウンロードされるため、選択した任意の基準に基づいてリアルタイムでトリガーされます。その結果、1MBのHTMLインアプリメッセージが10件ある場合、たとえそれらのメッセージをすべてトリガーしなかったとしても、顧客はすべて10MBのデータ料金が発生します。これは、アプリ内メッセージがキャッシュされ、セッションごとに再ダウンロードされない場合でも、時間の経過と共にすぐに増加する可能性があります。
 
 次の戦略は、ファイルサイズを小さく保つのに役立ちます:
 
 - アプリケーションやWebサイトに埋め込まれた参照フォントを使用して、HTMLアセットZIPフォルダーにフォントファイルを含めるのではなく、HTMLアプリ内メッセージをカスタマイズします。
-- HTMLアセットZIPに余分なCSSやJavaScriptが含まれないようにしてください。
+- HTML アセット ZIP に無関係または重複する CSS や JavaScript が含まれないようにしてください。
 - すべての画像に[ImageOptim][25]を使用して、画質を落とさずに可能な限り最小のサイズに圧縮します。
 
 ### iPhone 5 仕様
diff --git a/_lang/ja/_hidden/archive_docs/product_request_example.md b/_lang/ja/_hidden/archive_docs/product_request_example.md
index 3f0d2c9a9b6..71b55d803a4 100644
--- a/_lang/ja/_hidden/archive_docs/product_request_example.md
+++ b/_lang/ja/_hidden/archive_docs/product_request_example.md
@@ -9,7 +9,7 @@ description: "この参考記事では、製品リクエストの例を示して
 
 # 製品リクエスト例
  
-以下は、顧客から提出された良い製品リクエストの例である。要望を明確に定義し、その機能のユースケースを詳細に説明する。 
+ここでは、顧客が提出した良い製品リクエストの例を示します。要望を明確に定義し、その機能のユースケースを詳細に説明する。 
  
 ## スカイスキャナーからのリクエスト例
  
@@ -17,11 +17,11 @@ description: "この参考記事では、製品リクエストの例を示して
 スカイスキャナーは、回数制限の観点から、特定のタグを他のタグよりも優先して表示できるようにしたいと考えている。
  
 ### 具体的なユースケースは何ですか? 
-_キャンペーンやキャンバスへのリンクも、説明文と同様に役立つ。_
+_ここでは、キャンペーンとキャンバスへのリンクが説明と同様に役立ちます_
  
-ユーザーの行動に基づいて、より多くのトリガー・キャンペーンを展開していくので、1日1通を上限としているため、いくつかのメールが互いにテレスコープしてしまい、1日の早い時間に送信予定のメールが午後のメールよりも優先される可能性がある。これは理想的ではない。例えば、ファネルの一番下（リターゲティング）に関するメールは、TOFU（例えばニュースレター）よりも成果を上げる。
+ユーザーの行動に基づいて、より多くのトリガー・キャンペーンを展開していくので、1日1通を上限としているため、いくつかのメールが互いにテレスコープしてしまい、1日の早い時間に送信予定のメールが午後のメールよりも優先される可能性がある。これは理想的ではありません。例えば、ファネルの最下層に関するメール (リターゲティング) は、TOFU (ニュースレターなど) のメールよりも多くの結果をもたらしますので、優先順位を付けられるようにしたいと考えています。
  
-例えば、フリークエンシーキャップは最大1日だが、リダイレクトリターゲティングとタグ付けされたすべてのキャンペーンとキャンバスはP0、すべてのインスパイアはP3、すべての検索リターゲティングはP2、XsellはP1などと定義できるようにしたい。
+例えば、「freq.cap」は最大1日で、リダイレクトリターゲティングでタグ付けされたすべてのキャンペーンとキャンバスを P0、すべてのインスピレーションを P3、検索のすべてのリターゲティングを P2、Xsell を P1 などと定義できるようにしたいと思います。
  
 例を挙げると、タグの優先順位は次のようになる。
  
diff --git a/_lang/ja/_hidden/archive_docs/windows_object.md b/_lang/ja/_hidden/archive_docs/windows_object.md
index 672440a203a..6b2c00dfc05 100644
--- a/_lang/ja/_hidden/archive_docs/windows_object.md
+++ b/_lang/ja/_hidden/archive_docs/windows_object.md
@@ -11,7 +11,7 @@ hidden: true
 ---
 # Windowsオブジェクト仕様
 
-`windows_phone8_push` 、`windows_universal_push` オブジェクトは、[メッセージングエンドポイントを]({{site.baseurl}}/api/endpoints/messaging)経由して、Windows Phone 8 PushおよびWindows Universal Pushコンテンツに関連する情報を定義または要求するために使用される。
+`windows_phone8_push` および `windows_universal_push` オブジェクトは、[メッセージングエンドポイント]({{site.baseurl}}/api/endpoints/messaging)を介して、Windows Phone 8 Push および Windows Universal Push コンテンツに関連する情報を定義または要求するために使用されます。
 
 ## Windows Phone 8のプッシュオブジェクト
 
@@ -28,7 +28,7 @@ hidden: true
 
 ## Windowsユニバーサル・プッシュ・オブジェクト
 
-`push_type` のオプションの詳細については、Windowsユニバーサル[トーストのテンプレートカタログを][32]参照のこと。
+`push_type` のオプションの詳細については、Windows Universal [トーストテンプレートカタログ][32] を参照してください。
 
 ```json
 {
@@ -42,7 +42,7 @@ hidden: true
 }
 ```
 
-[ディープリンクの][38]ための`extra_launch_string` パラメータの使用に関する詳細は、[Windows Universalでのディープリンクを参照のこと。][37]
+[ディープリンク][38]の `extra_launch_string` パラメーターの使用に関する詳細は、[Windows Universal でのディープリンク][37]を参照してください。
 
 [32]: https://msdn.microsoft.com/en-us/library/windows/apps/hh761494.aspx
 [37]: {{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/push_notifications/integration/#step-4-deep-linking-from-push-into-your-app
diff --git a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/location_tracking.md b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/location_tracking.md
index bbd17ff2f4c..ca9b9c50c06 100644
--- a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/location_tracking.md
+++ b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/location_tracking.md
@@ -3,7 +3,7 @@ nav_title: 位置情報の追跡
 article_title: Windows Universalの位置情報の追跡
 platform: Windows Universal
 page_order: 6
-description: "この記事では、Windowsユニバーサルアプリに位置情報の追跡を追加する方法について説明します。"
+description: "このリファレンス記事では、Windows Universal アプリに位置情報の追跡を追加する方法について説明します。"
 tool: Location
 hidden: true
 ---
@@ -11,5 +11,5 @@ hidden: true
 # 位置情報の追跡
 {% multi_lang_include archive/windows_deprecation.md %}
 
-1. `Package.appxmanifest` ファイル内で`location` がチェックされていることを確認します。
-2. 自動位置"トラッキングを無効にするには、`<DisableLocationCollection>false</DisableLocationCollection>` を`true` に設定します(`AppboyConfiguration.xml`)。
+1. `Package.appxmanifest` ファイル内で `location` がオンになっていることを確認します。
+2. 自動位置情報の追跡をオフにするには、`AppboyConfiguration.xml` で `<DisableLocationCollection>false</DisableLocationCollection>` を `true` に設定します。
diff --git a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/logging_custom_events.md b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/logging_custom_events.md
index 899480aaba8..8a11d3e97d8 100644
--- a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/logging_custom_events.md
+++ b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/logging_custom_events.md
@@ -12,7 +12,7 @@ hidden: true
 
 Braze でカスタムイベントを記録することで、アプリの使用パターンに関する詳細を把握し、ダッシュボードでのアクションによってユーザーをセグメント化できます。また、[イベントの命名規則]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/event_naming_conventions/)についてもよく理解しておくことをお勧めします。
 
-すべてのイベントは、`EventLogger` を使用してログに記録されます。これは、IAppboy で公開されるプロパティです。`EventLogger` への参照を取得するには、`Appboy.SharedInstance.EventLogger` を呼び出します。以下の方法で、大切なユーザー アクションs とカスタムイベントs をトラッキングできます。
+すべてのイベントは、`EventLogger` を使用してログに記録されます。これは、IAppboy で公開されるプロパティです。`EventLogger` への参照を取得するには、`Appboy.SharedInstance.EventLogger` を呼び出します。次の方法を使用して、重要なユーザーアクションとカスタムイベントを追跡できます。
 
 ```csharp
 bool LogCustomEvent(string YOUR_EVENT_NAME)
diff --git a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/logging_purchases.md b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/logging_purchases.md
index 5d6c8d0f2b4..4d2b5bb7a80 100644
--- a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/logging_purchases.md
+++ b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/logging_purchases.md
@@ -18,7 +18,7 @@ Braze は複数の通貨での購入に対応しています。米ドル以外
 
 この機能を使用するには、アプリ内購入が正常に完了した後でこのメソッド呼び出しを追加します。
 
-購入履歴は、IAppboyで公開されている`EventLogger` 。`EventLogger` への参照を得るには、`Appboy.SharedInstance.EventLogger` を呼ぶ。
+購入は、`EventLogger` を使用してログに記録されます。これは、IAppboy で公開されているプロパティです。`EventLogger` への参照を取得するには、`Appboy.SharedInstance.EventLogger` を呼び出します。
 
 ```csharp
 bool LogPurchase(string productId, string currencyCode, decimal price)
diff --git a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/setting_custom_attributes.md b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/setting_custom_attributes.md
index aadffa8c799..64f487e4985 100644
--- a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/setting_custom_attributes.md
+++ b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/setting_custom_attributes.md
@@ -12,9 +12,9 @@ hidden: true
 
 Braze には、ユーザーに属性を割り当てるメソッドが用意されています。ダッシュボードでこれらの属性に基づき、ユーザーをフィルターおよびセグメント化できます。
 
-実装する前に、カスタムイベント、カスタム属性、購入イベントによって提供されるセグメンテーションオプションの例を、[ベストプラクティスで][7]確認してほしい。
+実施にあたっては、まずカスタムイベント、カスタム属性、購買イベントが提供するセグメンテーション選択肢の事例を[ベストプラクティス][7]で検討してください。
 
-ユーザー属性は、現在の`IAppboyUser` に割り当てることができる。現在の`IAppboyUser` への参照を得るには、以下をコールする。 `Appboy.SharedInstance.AppboyUser`
+ユーザー属性は、現在の`IAppboyUser` に割り当てることができる。現在の`IAppboyUser` への参照を取得するには、`Appboy.SharedInstance.AppboyUser` を呼び出します。
 
 ## デフォルトユーザー属性の割り当て
 
@@ -37,12 +37,12 @@ Appboy.SharedInstance.AppboyUser.FirstName = "User's First Name"
 
 ## カスタムユーザー属性の割り当て
 
-デフォルトのユーザー属性だけでなく、Brazeではさまざまなデータタイプを使ってカスタム属性を定義することもできる。セグメンテーションのオプションと、それぞれの属性がどのように影響するかについての詳細は、[ベストプラクティスを]({{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/analytics/setting_user_ids/#user-id-integration-best-practices-and-notes)参照のこと。
+デフォルトのユーザー属性だけでなく、Brazeではさまざまなデータタイプを使ってカスタム属性を定義することもできる。セグメンテーションオプションの詳細と、これらの属性のそれぞれがどのように影響するかについては、[ベストプラクティス]({{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/analytics/setting_user_ids/#user-id-integration-best-practices-and-notes)を参照してください。
 
 ### カスタム属性値を設定する
 
 {% tabs %}
-{% tab ブーリアン %}
+{% tab Boolean %}
 ```csharp
 bool SetCustomAttribute(STRING_KEY, BOOL_VALUE);
 ```
@@ -52,18 +52,18 @@ bool SetCustomAttribute(STRING_KEY, BOOL_VALUE);
 bool SetCustomAttribute(STRING_KEY, INT_VALUE);
 ```
 {% endtab %}
-{% tab ダブル/フロート %}
+{% tab Double/Float %}
 ```csharp
 bool SetCustomAttribute(STRING_KEY, DOUBLE_VALUE);
 ```
 Braze では、FLOAT 値と DOUBLE 値がデータベースでまったく同じく処理されます。
 {% endtab %}
-{% tab ストリング %}
+{% tab String %}
 ```csharp
 bool SetCustomAttribute(STRING_KEY, "STRING_VALUE");
 ```
 {% endtab %}
-{% tab ロング %}
+{% tab Long %}
 ```csharp
 bool SetCustomAttribute(STRING_KEY, LONG_VALUE);
 ```
@@ -72,7 +72,7 @@ bool SetCustomAttribute(STRING_KEY, LONG_VALUE);
 ```csharp
 bool SetCustomAttribute(STRING_KEY, "DATE_VALUE");
 ```
->  Brazeに渡される日付は、[ISO 8601][2]形式、e.g `2013-07-16T19:20:30+01:00` 、または`yyyy-MM-dd'T'HH:mm:ss:SSSZ` 形式のいずれかでなければならない。 e.g `2016-12-14T13:32:31.601-0800`
+>  Braze に渡される日付は、[ISO 8601][2] 形式、e.g `2013-07-16T19:20:30+01:00`、または`yyyy-MM-dd'T'HH:mm:ss:SSSZ` 形式のいずれかである必要があります e.g `2016-12-14T13:32:31.601-0800`
 {% endtab %}
 {% tab 配列 %}
 ```csharp
@@ -110,15 +110,15 @@ REST API を使用してユーザー属性を設定することもできます
 
 カスタム属性値の最大長は 255 文字です。これより長い値は切り捨てられます。
 
-## 通知購読ステータスを管理する
+## 通知サブスクリプションのステータスを管理する
 
-ユーザーに購読を設定するために（Eメールまたはプッシュ）、`IAppboyUser` のプロパティとして、以下の購読ステータスを設定することができる。Brazeのサブスクリプションステータスには、メールとプッシュの両方で3つの異なるステータスがある：
+ユーザーにサブスクリプション (メールまたはプッシュ) を設定するには、`IAppboyUser` のプロパティとして、以下のサブスクリプションステータスを設定できます。Braze のサブスクリプションステータスには、メールとプッシュの両方で3つの異なるステータスがあります。
 
-| 購読状況 | 定義 |
+| サブスクリプションのステータス | 定義 |
 | ------------------- | ---------- |
-| `OptedIn` | 加入し、明示的にオプトインした |
-| `Subscribed` | 購読しているが、明示的にオプトインしていない |
-| `UnSubscribed` | 配信停止および/または明示的にオプトアウトした |
+| `OptedIn` | 配信登録済み、かつ明示的にオプトイン済み |
+| `Subscribed` | 購読済み、ただし明示的に選択されていない |
+| `UnSubscribed` | 配信停止済みまたは明示的にオプトアウト済み、あるいはその両方 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 - `EmailNotificationSubscriptionType`
@@ -126,7 +126,7 @@ REST API を使用してユーザー属性を設定することもできます
 - `PushNotificationSubscriptionType`
   - ユーザーは、有効なプッシュ登録時に自動的に`Subscribed` に設定されるが、明示的なオプトイン・プロセスを確立し、ユーザーから明示的な同意を得た時点でこの値を`OptedIn` に設定することを推奨する。
 
->  これらのタイプは`AppboyPlatform.PCL.Models.NotificationSubscriptionType` に該当する。詳しくは[Managing user subscriptionsを][10]参照のこと。
+>  これらのタイプは `AppboyPlatform.PCL.Models.NotificationSubscriptionType` に属します。詳細については、「[ユーザーサブスクリプションの管理][10]」を参照してください。
 
 [1]: {{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/analytics/setting_user_ids/#user-id-integration-best-practices--notes
 [2]: http://en.wikipedia.org/wiki/ISO_8601
diff --git a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/setting_user_ids.md b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/setting_user_ids.md
index cce567681b9..8e1bf688223 100644
--- a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/setting_user_ids.md
+++ b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/setting_user_ids.md
@@ -34,4 +34,4 @@ Appboy.SharedInstance.ChangeUser(YOUR_USER_ID_STRING);
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/user_data/#user-data
 [2]: {{site.baseurl}}/developer_guide/rest_api/messaging/
-[6]: http://developer.android.com/reference/java/util/Locale.html#default_locale "Android Developer Docs - ローカライゼーション"
+[6]: http://developer.android.com/reference/java/util/Locale.html#default_locale "Android 開発者のドキュメント - ローカライゼーション"
diff --git a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/tracking_sessions.md b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/tracking_sessions.md
index dd8e0105124..0ae21dd692f 100644
--- a/_lang/ja/_hidden/archive_docs/windows_universal/analytics/tracking_sessions.md
+++ b/_lang/ja/_hidden/archive_docs/windows_universal/analytics/tracking_sessions.md
@@ -12,17 +12,17 @@ hidden: true
 
 ## セッショントラッキング
 
-Braze SDK レポートは、次のセッションセマンティクスに基づいて、Braze ダッシュボードがユーザー エンゲージメントやユーザーを理解するために必要な他の分析を計算するために使用されるセッションを生成します。これにより、"start セッション"close セッション"Braze ダッシュボード内で表示可能なセッション長と分析数を考慮したデータポイントsがSDKで生成されます。
+Braze SDK は、Braze ダッシュボードで使用されるセッションデータをレポートし、ユーザーエンゲージメントや、ユーザーを理解するために不可欠なその他の分析を計算します。以下のセッションセマンティクスに基づき、SDK は、Braze ダッシュボード内で表示可能なセッションの長さとセッション数を考慮した「セッション開始」と「セッション終了」のデータポイントを生成します。
 
 ### セッションライフサイクル
 
-当社のウィンドウズインテグレーションは、アプリが起動するとセッション 開封を記録し、アプリライセンスが終了するとセッションを記録します。`sessionTimeoutInSeconds` の最小値は 1 秒です。新しいセッションを強制する必要がある場合、ユーザーを変更することで強制が可能になります。
+Windows 統合では、アプリが起動されるとセッションオープンが記録され、アプリケーションが閉じられるとセッションクローズが記録されます。`sessionTimeoutInSeconds` の最小値は 1 秒です。新しいセッションを強制する必要がある場合、ユーザーを変更することで強制が可能になります。
 
 ### セッショントラッキングをテストする
 
-ユーザーでセッションs を検出するには、ダッシュボードでユーザーを見つけ、ユーザープロファイルで"App Usage" に移動します。セッション "トラッキングが機能していることを確認するには、" セッション s" メトリクスが期待どおりに増えることを確認します。
+ユーザーを介してセッションを検出するには、ダッシュボードでユーザーを見つけ、ユーザープロファイルの \[アプリの利用状況] に移動します。セッショントラッキングが機能していることを確認するには、「セッション」メトリクスが期待どおりに増加することを確認します。
 
-![アプリの使用量を25 セッション s として表示するユーザープロファイル。2 時間前に最後に使用され、最初に20 日前に使用された]\[セッション_"トラッキング_7]
+![ユーザープロファイルには、アプリの利用状況が表示されており、25セッション、最後の使用が2時間前、初めての使用が20日前と表示されています。]\[session_tracking_7]
 
 \[session_tracking_1]: {{ site.baseurl }}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overview#customizing-braze-on-startup
 \[session_tracking_3]: {{ site.baseurl }}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/#step-2-configure-the-braze-sdk-in-appboyxml
diff --git a/_lang/ja/_hidden/archive_docs/windows_universal/changelog.md b/_lang/ja/_hidden/archive_docs/windows_universal/changelog.md
index 61bf3c73e3e..727998fca18 100644
--- a/_lang/ja/_hidden/archive_docs/windows_universal/changelog.md
+++ b/_lang/ja/_hidden/archive_docs/windows_universal/changelog.md
@@ -1,6 +1,6 @@
 ---
 nav_title: 変更ログ
-article_title: ウィンドウズユニバーサルSDKの変更
+article_title: Windows Universal SDK の変更ログ
 page_order: 30
 page_type: update
 platform: Windows Universal
@@ -8,6 +8,6 @@ description: "このページには、Braze のWindows ユニバーサルSDK変
 hidden: true
 ---
 
-# ウィンドウズSDKの変更点
+# Windows SDK の変更ログ
 
 {% markdown_embed https://raw.githubusercontent.com/Appboy/appboy-windows-sdk/master/CHANGELOG.md %}
diff --git a/_lang/ja/_hidden/archive_docs/windows_universal/initial_sdk_setup.md b/_lang/ja/_hidden/archive_docs/windows_universal/initial_sdk_setup.md
index b1e77a74b44..af2558705d6 100644
--- a/_lang/ja/_hidden/archive_docs/windows_universal/initial_sdk_setup.md
+++ b/_lang/ja/_hidden/archive_docs/windows_universal/initial_sdk_setup.md
@@ -1,6 +1,6 @@
 ---
 nav_title: SDK の初期セットアップ
-article_title: ウィンドウズユニバーサル用の最初のSDK設定
+article_title: Windows Universal 用の SDK 初期設定
 platform: Windows Universal
 page_order: 0
 description: "このリファレンス記事では、Windows ユニバーサルプラットフォームにBraze SDKを統合するための最初のSDKインテグレーションステップについて説明します。"
@@ -11,23 +11,23 @@ hidden: true
 # SDK の初期統合
 {% multi_lang_include archive/windows_deprecation.md %}
 
-Braze SDKは、分析、セグメンテーション、およびエンゲージメントで使用されるレポート情報へのAPI、および通知s のプッシュおよび受信のためのユーザーs の登録機能を提供します。
+Braze SDK は、分析、セグメンテーション、エンゲージメントで使用される情報をレポートするための API と、プッシュ通知と通知の受信用にユーザーを登録する機能を提供します。
 
->  Windows ユニバーサルSDKは、Xamarin Windows アプリと互換性があります。
+>  Windows Universal SDK は、Xamarin Windows アプリとも互換性があります。
 
 ## ステップ 1:NuGet パッケージマネージャーを使用したSDKのインストール
 
 Windows ユニバーサルSDKは、[NuGet Package Manager][14] を使用してインストールします。NuGet を使用してBraze Windows SDKをインストールするには:
 
 1. プロジェクトファイルを右クリックする
-2. "Manage NuGet Packages&quotをクリックします。
-3. 左側のドロップダウンメニューで、"Online"をクリックします
-4. &quot で検索;NuGet.org" " Appboy"
-5. "AppboyPlatform.Universal.Release"NuGet Package をクリックし、Install をクリックします
+2. \[Manage NuGet Packages (NuGet パッケージの管理)]をクリックします。
+3. 左側のドロップダウンメニューで、\[オンライン] をクリックします
+4. 「NuGet.org」で「Appboy」を検索
+5. \[AppboyPlatform.Universal.Release] NuGet パッケージをクリックし、\[インストール] をクリックします
 
->  Windows Universal Libraryは、Windows 8.1、Windows Phone 8.1、およびUWP アプリのすべてのアプリケーションで使用する必要があります。
+>  Windows Universal ライブラリは、Windows 8.1、Windows Phone 8.1、および UWP のすべてのアプリケーションで使用する必要があります。
 
-## ステップ2:作成と設定 AppboyConfiguration.xml
+## ステップ2:AppboyConfiguration.xml の作成と設定
 
 プロジェクトのルートディレクトリに`AppboyConfiguration.xml` という名前のファイルを作成し、そのファイルに次のコード スニペットを追加します。
 
@@ -38,19 +38,19 @@ Windows ユニバーサルSDKは、[NuGet Package Manager][14] を使用して
     </AppboyConfig>
 ```
 
->  [ API キー s]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) ページにあるAPI キーで`YOUR_API_KEY_HERE` を必ず更新してください。
+>  \[[API キー]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/)] ページにある API キーで `YOUR_API_KEY_HERE` を更新してください。
 
-そのスニペットを追加したら、以下のファイルプロパティを変更してください `AppboyConfiguration.xml`
+そのスニペットを追加したら、以下の `AppboyConfiguration.xml` のファイルプロパティを変更してください。
 
-1. `Build Action` を `Content`
-2. `Copy to Output Directory`を `Copy Always`
+1. `Build Action` を `Content` に設定します
+2. `Copy to Output Directory` を `Copy Always` に設定します
 
-## ステップ 3:設定 package.appxmanifest
+## ステップ 3:package.appxmanifest の設定
 
-"Capabilities タブで、`Internet (Client)` がチェックされていることを確認します。
+\[機能] タブで、`Internet (Client)` がオンになっていることを確認します。
 ![][18]
 
-## ステップ 4:アプリを編集する
+## ステップ 4:アプリクラスの編集
 
 - `App.xaml.cs` ファイルの`usings` に以下を追加します。
 
@@ -72,11 +72,11 @@ Appboy.SharedInstance.OpenSession();
 Appboy.SharedInstance.CloseSession();
 ```
 
-## 基本SDK一体化完了
+## 基本的な SDK 統合の完了
 
-Braze はアプリライセンスからデータを収集するようになりました。[属性 s]({{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/analytics/setting_custom_attributes/)、[events]({{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/analytics/logging_custom_events)、および[purchases]({{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/analytics/logging_purchases)をSDKに記録し、プッシュメッセージングを計測する方法については、次の記事を参照してください。
+これで Braze はアプリケーションからデータを収集するようになるはずです。[属性]({{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/analytics/setting_custom_attributes/)、[イベント]({{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/analytics/logging_custom_events)、および[購入]({{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/analytics/logging_purchases)を SDK に記録する方法と、プッシュメッセージングを実装する方法については、次の記事を参照してください。
 
->  同じアプリでBraze Unity プロジェクトを使用している場合は、Braze の呼び出しを"AppboyPlatform.Universal.Appboy" として完全修飾する必要がある場合があります。
+>  同じアプリで Braze Unity プロジェクトを使用している場合は、Braze への呼び出しを「AppboyPlatform.Universal.Appboy」として完全修飾する必要があります。
 
 [14]: http://www.nuget.org/
 [18]: {% image_buster /assets/img_archive/internet_client.png %}
diff --git a/_lang/ja/_hidden/archive_docs/windows_universal/push_notifications.md b/_lang/ja/_hidden/archive_docs/windows_universal/push_notifications.md
index 7a2fec2608a..53413d46713 100644
--- a/_lang/ja/_hidden/archive_docs/windows_universal/push_notifications.md
+++ b/_lang/ja/_hidden/archive_docs/windows_universal/push_notifications.md
@@ -11,24 +11,24 @@ hidden: true
 # プッシュ通知の統合
 {% multi_lang_include archive/windows_deprecation.md %}
 
-![ユニバーサル・プッシュの例である。][10]{: style="float:right;max-width:40%;margin-left:15px;"}
+![Windows Universal プッシュ通知の例。][10]{: style="float:right;max-width:40%;margin-left:15px;"}
 
 プッシュ通知は、重要なアップデートが発生したときにユーザーの画面に表示されるアプリ外のアラートです。プッシュ通知は、時間的制約があって関連性の高いコンテンツをユーザーに提供したり、ユーザーをアプリに再エンゲージしたりするための効果的な方法です。
 
 その他のベストプラクティスについては、\[ドキュメント][9] ] を参照のこと。
 
-## ステップ 1:プッシュ用にアプリケーションを設定する
+## ステップ 1:プッシュ通知用にアプリケーションを設定する
 
-`Package.appxmanifest` 、以下の設定がされていることを確認する：
+`Package.appxmanifest` ファイルで、次の設定が構成されていることを確認します。
 
 **アプリケーション**タブで、`Toast Capable` が`YES` に設定されていることを確認する。
 
 ## ステップ2:Brazeダッシュボードを設定する
 
-1. [SIDとクライアントシークレットを検索する][4]
+1. [SID とクライアントシークレットを検索する][4]
 2. Brazeダッシュボードの**設定**ページで、SIDとクライアントシークレットを設定に追加する。<br>![][6]
 
-## ステップ3:バックグラウンド・オープン・ロギングの更新
+## ステップ3:バックグラウンド開封ロギングの更新
 
 `OnLaunched` メソッドで、`OpenSession` をコールした後、以下のコード・スニペットを追加する。
 
@@ -47,7 +47,7 @@ Appboy.SharedInstance.PushManager.LogPushNotificationOpened(campaignId);
 - `Appboy.SharedInstance.PushManager.PushReceivedEvent += YourPushReceivedEventHandler;`
 - `Appboy.SharedInstance.PushManager.ToastActivatedEvent += YourToastActivatedEventHandler;`
 
-イベント・ハンドラにはシグネチャが必要だ：
+イベントハンドラには、署名が必要です。
 
 - `void YourPushReceivedEventHandler(PushNotificationChannel sender, AppboyPushNotificationReceivedEventArgs args);`
 - `void YourToastActivatedEventHandler(ToastNotification sender, AppboyToastActivatedEventArgs args);`
@@ -58,23 +58,23 @@ Appboy.SharedInstance.PushManager.LogPushNotificationOpened(campaignId);
 
 ディープリンクは、アプリケーションの外部からユーザーをアプリケーションの特定の画面やページに直接ナビゲートするために使用される。通常これは、オペレーティング・システムにURLスキーム（例えば、myapp://mypage ）を登録し、そのスキームを処理するアプリケーションを登録することによって行われる。OSがその形式のURLを開くように要求されると、アプリケーションに制御が移る。
 
-WNSのディープリンクサポートは、ユーザーをどこに送るかについてのデータでアプリケーションを起動するので、これとは異なる。WNSプッシュが作成されると、プッシュがクリックされアプリケーションが開かれたときに、アプリケーションの`OnLaunched` に渡される起動文字列を含めることができる。私たちはすでに、キャンペーン・トラッキングを行うためにこのローンチ文字列を使用しており、アプリが起動したときに解析され、ユーザーをナビゲートするために使用できる独自のデータを追加する能力をユーザーに与えている。
+WNSのディープリンクサポートは、ユーザーをどこに送るかについてのデータでアプリケーションを起動するので、これとは異なる。WNS プッシュが作成されると、プッシュがクリックされアプリケーションが開かれたときに、アプリケーションの `OnLaunched` に渡される起動文字列を含めることができます。私たちはすでに、キャンペーン・トラッキングを行うためにこのローンチ文字列を使用しており、アプリが起動したときに解析され、ユーザーをナビゲートするために使用できる独自のデータを追加する能力をユーザーに与えている。
 
-ダッシュボードやREST APIで追加の打ち上げ文字列を指定すると、作成する打ち上げ文字列の末尾、キー "abextras="の後に追加される。つまり、ローンチ文字列の例は、`ab_cn_id=_trackingid_abextras=page=settings` のようになる。この場合、ローンチ文字列の追加パラメータに`page=settings` を指定することで、それを解析してユーザーを設定ページにナビゲートすることができる。
+ダッシュボードや REST API で追加の起動文字列を指定すると、作成した起動文字列の末尾、キー「abextras=」の後に追加されます。そのため、起動文字列の例は `ab_cn_id=_trackingid_abextras=page=settings` のようになります。この例では、追加の起動文字列パラメータで `page=settings` を指定しているため、これを解析してユーザーを設定ページに移動できます。
 
 ### パート 2:ダッシュボードを使ったディープリンク
 
-プッシュ通知設定の「追加起動文字列設定」フィールドで、起動文字列に追加する文字列を指定する。
+プッシュ通知設定の \[追加の起動文字列設定] フィールドで、起動文字列に追加する文字列を指定します。
 
 ![][15]
 
 ### パート3：REST APIによるディープリンク
 
-Brazeは、REST APIを通じてディープリンクを送信することもできる。\[Windowsユニバーサルプッシュオブジェクト][13] は、オプションの`extra_launch_string` パラメータを受け付ける。
+Braze では、REST API 経由でディープリンクを送信することもできます。\[Windows Universal プッシュ通知オブジェクト][13] は、オプションの `extra_launch_string` パラメータを受け入れます。
 
 [4]: http://msdn.microsoft.com/en-us/library/windows/apps/hh465407.aspx
 [6]: {% image_buster /assets/img_archive/windows_sid.png %} 「Windows SIDダッシュボード
 [9]: {{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/
 [10]: {% image_buster /assets/img_archive/windows_uni_push_sample.png %}
 [13]: {{site.baseurl}}/api/objects_filters/messaging/windows_objects/
-[15]: {% image_buster /assets/img_archive/windows_deep_link_click_action.png %} 「ディープリンクのクリックアクション
+[15]: {% image_buster /assets/img_archive/windows_deep_link_click_action.png %}「ディープリンククリックアクション」
diff --git a/_lang/ja/_hidden/archived_layouts/api_glossary.md b/_lang/ja/_hidden/archived_layouts/api_glossary.md
index 1abd72fed0a..befd5cb4e77 100644
--- a/_lang/ja/_hidden/archived_layouts/api_glossary.md
+++ b/_lang/ja/_hidden/archived_layouts/api_glossary.md
@@ -56,7 +56,7 @@ Post,Email,Create,Template,REST,API
 
 {% apiref postman %}https://www.getpostman.com/ {% endapiref %}
 
-#### リクエストボディ
+#### リクエスト本文
 ```
 {
   "template_name": "email_template_name",
@@ -68,7 +68,7 @@ Post,Email,Create,Template,REST,API
 
 ```
 
-#### 例の応答
+#### 応答の例
 ```
 {
   "template_name": "email_template_name",
@@ -105,7 +105,7 @@ Post,Email,Create,Template,REST,API
 
 {% apiref postman %}https://www.getpostman.com/ {% endapiref %}
 
-#### リクエストボディ
+#### リクエスト本文
 ```
 GET https://YOUR_REST_API_URL/templates/email/list
 
@@ -120,7 +120,7 @@ GET https://YOUR_REST_API_URL/templates/email/list
 
 ```
 
-#### 例の応答
+#### 応答の例
 ```
 GET https://YOUR_REST_API_URL/templates/email/list
 
@@ -154,7 +154,7 @@ API トリガー配信を使用すると、メッセージの内容を Braze ダ
 
 {% apiref postman %}https://www.getpostman.com/ {% endapiref %}
 
-#### リクエストボディ
+#### リクエスト本文
 ```
 POST https://YOUR_REST_API_URL/campaigns/trigger/send
 Content-Type: application/json
@@ -179,7 +179,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 
 ```
 
-#### 例の応答
+#### 応答の例
 ```
 POST https://YOUR_REST_API_URL/canvas/trigger/send
 Content-Type: application/json
@@ -218,11 +218,11 @@ Authorization: Bearer YOUR-REST-API-KEY
 {% apimethod put %}users/track{% endapimethod %}
 {% apitags %}PUT, キャンペーン, トリガー, 送信{% endapitags %}
 
-このエンドポイントは、カスタムイベント、ユーザー属性、およびユーザーの購入を記録するために使用できます。リクエストごとに最大75の属性、イベント、および購入オブジェクトを含めることができます。つまり、一度に最大75人のユーザーの属性しか投稿できませんが、同じAPI呼び出しで最大75件のイベントと最大75件の購入も提供できます。
+このエンドポイントは、カスタムイベント、ユーザー属性、およびユーザーの購入を記録するために使用できます。リクエストごとに最大75の属性、イベント、購入オブジェクトを含めることができます。つまり、一度に最大75人のユーザーの属性しか投稿できませんが、同じ API 呼び出しで最大75件のイベントと最大75件の購入も提供できます。
 
 {% apiref postman %}https://www.getpostman.com/ {% endapiref %}
 
-#### リクエストボディ
+#### リクエスト本文
 ```
 POST https://YOUR_REST_API_URL/users/track
 Content-Type: application/json
@@ -235,7 +235,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 
 ```
 
-#### 例の応答
+#### 応答の例
 ```
 {
   // One of "external_id" or "user_alias" or "braze_id" is required
@@ -265,26 +265,26 @@ Authorization: Bearer YOUR-REST-API-KEY
 
 | ユーザープロファイル フィールド | データ型仕様 |
 | ---| --- |
-| country | 国コードは\[ISO-3166-1 alpha-2標準][17]でBrazeに渡される必要があります。 |
+| country | (文字列) 国コードは \[ISO-3166-1 alpha-2 規格][17] で Braze に渡す必要があります。 |
 | current_location | (オブジェクト) {"longitude": -73.991443, "latitude": 40.753824} の形式 |
 | date_of_first_session | （ユーザーが初めてアプリを使用した日付）ISO 8601形式または`yyyy-MM-dd'T'HH:mm:ss:SSSZ`形式の文字列。 |
 | date_of_last_session | （ユーザーが最後にアプリを使用した日付）ISO 8601形式または`yyyy-MM-dd'T'HH:mm:ss:SSSZ`形式の文字列。 |
 | dob | （生年月日）「YYYY-MM-DD」の形式の文字列。例えば、1980-12-21。 |
 | email | (string) |
 | email_subscribe | (文字列) 使用できる値は、「opted_in」 (メールメッセージを受信するように明示的に登録)、「unsubscribed」 (メールメッセージの受信を明示的に拒否)、「subscribed」 (明示的に登録も拒否もしていない) です。  |
-| external_id | （文字列）一意のユーザー識別子。 |
+| external_id | (文字列) 一意のユーザー識別子。 |
 | Facebook | `id`（文字列）、`likes`（文字列の配列）、`num_friends`（整数）のいずれかを含むハッシュ。 |
 | first_name | (string) |
 | gender | (文字列) 「M」、「F」、「O」 (その他)、「N」 (該当なし)、「P」 (言いたくない) または「nil」 (不明)。 |
 | home_city | (string) |
-| 画像_url | （文字列）ユーザープロファイルに関連付ける画像のURL。 |
-| language | (string) 言語はISO-639-1標準][24]でBrazeに渡される必要があります。<br>[受け入れられる言語のリスト][1]|
+| image_url | （文字列）ユーザープロファイルに関連付ける画像のURL。 |
+| language | (文字列) 言語は \[ISO-639-1 規格][24] で Braze に渡す必要があります。<br>[受け入れ可能な言語のリスト][1]|
 | last_name | (string) |
 |marked_email_as_spam_at| （文字列）ユーザーのメールがスパムとしてマークされた日付。ISO 8601形式またはyyyy-MM-dd'T'HH:mm:ss:SSSZ形式で表示されます。|
 | phone | (string) |
 | push_subscribe | (文字列) 使用できる値は、「opted_in」 (プッシュメッセージを受信するように明示的に登録)、「unsubscribed」 (プッシュメッセージの受信を明示的に拒否)、「subscribed」 (明示的に登録も拒否もしていない) です。  |
 | push_tokens | オブジェクトの配列は`app_id`と`token`の文字列です。このトークンが関連付けられているデバイスに`device_id`を任意で提供することができます。例えば、`[{"app_id": App Identifier, "token": "abcd", "device_id": "optional_field_value"}]`。提供されない場合は、`device_id`がランダムに生成されます。 |
-| time_zone | IANAタイムゾーンデータベース][26]からのタイムゾーン名（例：「America/New_York」または「Eastern Time (US & Canada)」）。有効なタイムゾーン値のみが設定されます。 |
+| time_zone | (文字列) \[IANA タイムゾーンデータベース][26] (たとえば、「アメリカ/ニューヨーク」または「東部標準時 (アメリカ & カナダ)」) からのタイムゾーン名。有効なタイムゾーン値のみが設定されます。 |
 | ツイッター | `id` (整数)、`screen_name` (文字列、X (旧Twitter) ハンドル)、`followers_count` (整数)、`friends_count` (整数)、`statuses_count` (整数) のいずれかを含むハッシュ。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
diff --git a/_lang/ja/_hidden/archived_layouts/get_endpoint.md b/_lang/ja/_hidden/archived_layouts/get_endpoint.md
index ea4b00b286f..0aa8ffc4d69 100644
--- a/_lang/ja/_hidden/archived_layouts/get_endpoint.md
+++ b/_lang/ja/_hidden/archived_layouts/get_endpoint.md
@@ -6,13 +6,13 @@ page_order: 1
 excerpt_separator: ""
 layout: api_page
 page_type: reference
-description: "この記事では、Get [エンドポイント名] Brazeエンドポイントの使用方法とパラメータについて概説する。"
+description: "この記事では、Get [エンドポイント名] Braze エンドポイントを使用するための使用方法とパラメーターについて説明します。"
 
 noindex: true
 #ATTENTION: remove noindex and this alert from template
 ---
 {% api %}
-# クエリーまたはリスト \[項目エンドポイント "Gets"]
+# クエリまたは List \[項目エンドポイント "Gets"]
 
 {% apimethod get %}
 /sms/invalid_phone_numbers
diff --git a/_lang/ja/_hidden/archived_layouts/glossary.md b/_lang/ja/_hidden/archived_layouts/glossary.md
index 5431b102f7c..62510e3cec0 100644
--- a/_lang/ja/_hidden/archived_layouts/glossary.md
+++ b/_lang/ja/_hidden/archived_layouts/glossary.md
@@ -7,7 +7,7 @@ noindex: true
 
 # レイアウト例：用語集
 
-> 用語集のレイアウトはYAMLである。それにはいくつかのコンポーネントとパラメーターが必要だ。用語集レイアウトは、辞書や特定のカテゴリーのコンテンツなど、ローカライズされた検索可能なコンテンツに適している。
+> 用語集のレイアウトはYAMLである。それにはいくつかのコンポーネントとパラメーターが必要です。用語集レイアウトは、辞書や特定のカテゴリーのコンテンツなど、ローカライズされた検索可能なコンテンツに適している。
 
 ## 必要なコンポーネント
 
@@ -17,26 +17,26 @@ noindex: true
 
 ## 必須パラメータ
 
-|パラメーター | コンテンツ・タイプ | 詳細 |
+|パラメーター | コンテンツタイプ | 詳細 |
 |---|---|---|
-|`page_order`| 数値 | セクション内でページを順番に並べる。この順番は左側のナビゲーションに反映される。 |
+|`page_order`| 数値 | セクション内でページを順番に並べる。この順序は左側のナビゲーションに反映されます。 |
 | `nav-title`| 英数字 | 左側のナビゲーションに表示されるタイトル。 |
 |`layout`| 英数字 - スペースなし | ドキュメントの[レイアウトセクションから](https://github.com/Appboy/braze-docs/tree/develop/_layouts)レイアウトを選択する。 | 
-|`glossary_top_header` | 英数字 | 二重引用符が必要である。タイトルはページ上部に表示される。 |
-|`glossary_top_text`| 文字列、英数字 | 用語集ページについて説明する。これは、検索バーとフィルター（選択した場合）の上に表示される。これは基本的にHTMLで書かれているので、\`\`\`を使うことができる。<br> でラインブレイクを作る。 | 
-|`glossary_tag_name` | 単一単語、英数字 | フィルターに名前をつける。これらは、検索バーの下のチェックボックスや、下のデータに表示される。 | 
-|`glossary_filter_text`| 文字列、英数字 | フィルターについて説明してほしい。通常、指導に使われる。 | 
-|`glossary_tags`| YAMLプラス・コンテンツが増えた。 | 書式は以下の通りである：<br> glossary_tags:<br>  \- という名前だ：コンテンツカードによって促進された <br>  \- という名前だ：メール | 
-| `glossaries`| YAMLプラス・コンテンツが増えた。 | 以下の[用語集パラメータを](#glossaries-parameters)参照のこと。 |
+|`glossary_top_header` | 英数字 | 二重引用符が必要です。タイトルはページ上部に表示される。 |
+|`glossary_top_text`| 文字列、英数字 | 用語集ページについて説明する。これは、検索バーとフィルター（選択した場合）の上に表示される。これは基本的にHTMLで書かれているので、\`\`\`を使うことができる。<br> 改行を作成します。 | 
+|`glossary_tag_name` | 単一単語、英数字 | フィルターに名前をつける。これらは、検索バーの下のチェックボックスや、下のデータに表示されます。 | 
+|`glossary_filter_text`| 文字列、英数字 | フィルターについて説明してほしい。通常、指示に使用します。 | 
+|`glossary_tags`| YAMLプラス・コンテンツが増えた。 | 書式は以下の通りです。<br> glossary_tags:<br>  \- name:コンテンツカードによって促進された <br>  \- name:メール | 
+| `glossaries`| YAMLプラス・コンテンツが増えた。 | 以下の[用語集パラメーター](#glossaries-parameters)を参照してください。 |
 
 ### 用語集 パラメータ
 
-|パラメーター | コンテンツ・タイプ | 詳細 |
+|パラメーター | コンテンツタイプ | 詳細 |
 |---|---|---|
 |`name`| 英数字 | 用語集に名前をつける。| 
 |`description`| 文字列、英数字 | 用語集の項目を説明する。 | 
 |`calculation`| string | (任意) あなたの用語集項目がどのように計算されるかを記述する（通常、データや測定基準を記述するときに使用される）。 | 
-|`tags`| 英数字 | `glossary_tags` の下に`name` として記載されているものと一致するはずである。該当するものをいくつでも挙げること。`All` と書くと、すべてのフィルターにその項目が含まれる。|
+|`tags`| 英数字 | `glossary_tags` の下に`name` として記載されているものと一致するはずである。該当するものをすべて挙げてください。`All` と書くと、すべてのフィルターにその項目が含まれる。|
 
 ## 例
 
diff --git a/_lang/ja/_hidden/archived_layouts/glossary_test_page.md b/_lang/ja/_hidden/archived_layouts/glossary_test_page.md
index 92e29f60dd3..92f22c3240a 100644
--- a/_lang/ja/_hidden/archived_layouts/glossary_test_page.md
+++ b/_lang/ja/_hidden/archived_layouts/glossary_test_page.md
@@ -46,18 +46,18 @@ glossary_filter_text: "Select tags to narrow the glossary:"
 
 # channel to icon/fa or image mapping
 glossary_tags:
-  - name: タグ 1
-  - name: タグ 2
-  - name: タグ 3
+  - name: タグ1
+  - name: タグ2
+  - name: タグ3
 
 glossaries:
-  - name: 用語 1
+  - name: 用語1
     image: /docs/assets/img_archive/weeklyreport.png
     description: 用語1の定義。
     calculation: Calculation / Of Term 1
     tags:
       - All
-  - name: ターム2
+  - name: 用語2
     description: 用語2の定義。
     calculation: (Number of Terms) / (Unique Terms)
     tags:
diff --git a/_lang/ja/_hidden/archived_layouts/help_article_template.md b/_lang/ja/_hidden/archived_layouts/help_article_template.md
index ece9137ec52..f0c41ba4925 100644
--- a/_lang/ja/_hidden/archived_layouts/help_article_template.md
+++ b/_lang/ja/_hidden/archived_layouts/help_article_template.md
@@ -43,11 +43,11 @@ noindex: true
 
 # \[ヘルプ記事名]
 
-> ヘルプ記事テンプレートへようこそ！ここには、自分のヘルプ記事を作成するのに必要なものがすべて揃っている。この最初のセクションでは、記事のトピックを数センテンスで説明する。おそらく、「この記事は、あなたのメッセージが全聴衆に送信されない理由のトラブルシューティングについて説明します」のようなものだろう。
+> ヘルプ記事テンプレートへようこそ！ここには、自分のヘルプ記事を作成するために必要なものがすべて用意されています。この最初のセクションでは、記事のトピックを数文で説明します。おそらく、「この記事では、メッセージがすべてのオーディエンスに送信されない原因のトラブルシューティングについて説明します」などです。
 
 ## 主な問題
 
-このセクションでは、主な問題を分解し、関連する可能性のある副次的な問題を列挙する。また、このスペースを使って、この記事に関連しそうな他のヘルプ記事を参照したり、提案したりすることもできる。根本的な問題を十分に説明した後、読者を問題の答えが見つかる場所に誘導することができる。
+このセクションでは、主な問題を分解し、関連する可能性のある副次的な問題を列挙する。このスペースを使用して、この記事に関連している可能性のある他のヘルプ記事を参照または提案することもできます。根本的な問題を十分に説明した後、読者を問題の答えが見つかる場所に誘導することができる。
 
 あなたのシナリオに最も近い項目をクリックする：
 - [解決策1](#solution-1)
@@ -56,7 +56,7 @@ noindex: true
 
 ## 解決策1
 
-これがトラブルシューティングの核心である。これは最も一般的な問題であり、最も簡単な解決策でもある！
+これがトラブルシューティング記事の要点です。これは最も一般的な問題であり、最も簡単な解決策でもある！
 
 ### ステップ1:これはステップ1の簡単な説明である。
 
@@ -68,11 +68,11 @@ noindex: true
 
 ### ステップ3:ステップの数
 
-必要なだけ入れる。
+必要な数だけ入れます。
 
 ## 解決策2
 
-これがトラブルシューティングの核心である。これはもうひとつの問題であり、解決策でもある！
+これがトラブルシューティング記事の要点です。これはもうひとつの問題であり、解決策でもある！
 
 ### ステップ1:これはステップ1の簡単な説明である。
 
@@ -84,11 +84,11 @@ noindex: true
 
 ### ステップ3:ステップの数
 
-必要なだけ入れる。
+必要な数だけ入れます。
 
 ## 解決策3
 
-これがトラブルシューティングの核心である。これはもうひとつの問題であり、解決策でもある！
+これがトラブルシューティング記事の要点です。これはもうひとつの問題であり、解決策でもある！
 
 ### ステップ1:これはステップ1の簡単な説明である。
 
@@ -100,11 +100,11 @@ noindex: true
 
 ### ステップ3:ステップの数
 
-必要なだけ入れる。
+必要な数だけ入れます。
 
 ## 次のステップ
 
-おめでとうございます！あなたはこのチュートリアル、トラブルシューティング記事、または解決策を完了した！つまり、あなたは持っているべきだということだ：
+おめでとうございます！あなたはこのチュートリアル、トラブルシューティング記事、または解決策を完了した！つまり、次のものが必要です。
 1. あなたが学ぶべきだったこと
 2. 完了したはずのタスク
 3. 今すぐ、あるいは次にやるべきことがある。
@@ -116,7 +116,7 @@ noindex: true
 - [関連記事2](#solution-2)：なぜ役に立つのかを説明する。
 - [関連記事3](#solution-3)：なぜ役に立つのかを説明する。
 
-### まだ迷っているのか？
+### まだ迷っていますか？
 
 この記事が役に立たなかった場合は、フィードバックを残すか、[サポートチケットを][support]開く！
 
diff --git a/_lang/ja/_hidden/archived_layouts/landing_images.md b/_lang/ja/_hidden/archived_layouts/landing_images.md
index 144da8a2e66..5ff06b46307 100644
--- a/_lang/ja/_hidden/archived_layouts/landing_images.md
+++ b/_lang/ja/_hidden/archived_layouts/landing_images.md
@@ -56,7 +56,7 @@ guide_featured_list:
 
 ---
 
-## 余分な
+## エクストラ
 
 必要に応じて、下部に追加のコンテンツを追加できます。必ず下に改行を入れてください。ここに参考資料を追加しないでください。[そのために参照テンプレートを使用してください]({{site.baseurl}}/home/templates/reference/).
 
diff --git a/_lang/ja/_hidden/archived_layouts/landing_multiple.md b/_lang/ja/_hidden/archived_layouts/landing_multiple.md
index 3d194dd64c9..4d36ffccbbb 100644
--- a/_lang/ja/_hidden/archived_layouts/landing_multiple.md
+++ b/_lang/ja/_hidden/archived_layouts/landing_multiple.md
@@ -1,5 +1,5 @@
 ---
-nav_title: MS LP with FA Icons
+nav_title: FA アイコン付き MS LP
 layout: dev_guide
 
 page_order: 1.3
@@ -57,10 +57,10 @@ guide_menu_list:
   - name: 例4
     link: /docs/home/templates/api_glossary/
     image: /assets/img/braze_icons/book-closed.svg
-  - name: 例 5
+  - name: 例5
     link: /docs/home/templates/glossary_test_page/
     image: /assets/img/braze_icons/book-closed.svg
-  - name: 例 6
+  - name: 例6
     link: /docs/home/templates/partner_page_template_video/
     image: /assets/img/braze_icons/heart-hand.svg
 ---
diff --git a/_lang/ja/_hidden/archived_layouts/landing_multiple_images.md b/_lang/ja/_hidden/archived_layouts/landing_multiple_images.md
index 4c4e80c8c67..37bba07a6d2 100644
--- a/_lang/ja/_hidden/archived_layouts/landing_multiple_images.md
+++ b/_lang/ja/_hidden/archived_layouts/landing_multiple_images.md
@@ -1,5 +1,5 @@
 ---
-nav_title: MS LP とイメージ
+nav_title: 画像付きの MS LP
 layout: dev_guide
 
 page_order: 1.4
@@ -40,9 +40,9 @@ noindex: true
 #ATTENTION: remove noindex and this alert from template
 
 guide_top_header: "イメージを使用した複数セクションのランディングページ"
-guide_top_text: "マルチセクションランディングページは、セクション内のページ間を通常トピックで分割する大きなセクションに適しています。このテンプレートでは、'dev_guide' layout YAMLパラメータ('layout: dev_guide')を使用します。これにより、ページの下部に情報を追加できなくなりますが、ボタンの複数のセクションを含めることができます。"
+guide_top_text: "マルチセクションランディングページは、セクション内のページ間を通常トピックで分割する大きなセクションに適しています。この特別なテンプレートは「dev_guide」レイアウト YAML パラメーター ('layout: dev_guide') を使用します。これにより、ページの下部に余分な情報を追加できなくなりますが、ボタンの複数のセクションを持つことができます。"
 
-guide_featured_title: "第一節"
+guide_featured_title: "セクション1"
 guide_featured_list:
   - name: 例 1
     link: /docs/home/templates/landing_single/
diff --git a/_lang/ja/_hidden/archived_layouts/landing_single.md b/_lang/ja/_hidden/archived_layouts/landing_single.md
index b472cc93fff..c6cd5f4e539 100644
--- a/_lang/ja/_hidden/archived_layouts/landing_single.md
+++ b/_lang/ja/_hidden/archived_layouts/landing_single.md
@@ -38,7 +38,7 @@ noindex: true
 #ATTENTION: remove noindex and this alert from template
 
 guide_top_header: "FAアイコンを使ったシングルセクションのランディングページ"
-guide_top_text: "単一セクションのランディングページは、セクション内のページ間の区分がほとんどない、あるいは全くない大きなセクションに最適である。この特別なテンプレートは、「featured」レイアウトのyamlパラメーター（「layout: dev_guide」）を使っている。追加のセクションが必要な場合、'dev_guide' レイアウト YAML パラメータを使用して、マルチセクションランディングページページタイプを使用する。"
+guide_top_text: "単一セクションのランディングページは、セクション内のページ間の区分がほとんどない、あるいは全くない大きなセクションに最適である。この特定のテンプレートは 'featured' layout yaml パラメーター ('layout: dev_guide') を使用します。これにより、ページの下部に追加情報を追加できます。追加のセクションが必要な場合、'dev_guide' レイアウト YAML パラメータを使用して、マルチセクションランディングページページタイプを使用する。"
 
 guide_featured_title: "セクション"
 guide_featured_list:
@@ -54,7 +54,7 @@ guide_featured_list:
 
 ---
 
-## おまけ
+## エクストラ
 
 必要であれば、一番下に追加コンテンツを加えることもできる。必ず下に改行を入れること。ここに参考資料を追加してはいけない。[その際は、参考テンプレートを使おう]({{site.baseurl}}/home/templates/reference/)。
 
diff --git a/_lang/ja/_hidden/archived_layouts/overview.md b/_lang/ja/_hidden/archived_layouts/overview.md
index 397c7c1cb68..c1f61e0d491 100644
--- a/_lang/ja/_hidden/archived_layouts/overview.md
+++ b/_lang/ja/_hidden/archived_layouts/overview.md
@@ -8,7 +8,7 @@ noindex: true
 
 > オーバービュー・レイアウトは、ページの上部に特定のナビゲーション・オプションを設け、ユーザーがボタンをクリックしてページの特定の部分や、まったく別のページに移動できるようにするのに適している。
 
-セレクタ・レイアウトの典型的な例としては、[SDK Changelogs](https://www.braze.com/docs/developer_guide/platform_integration_guides/sdk_changelogs/)ページや[アプリ内メッセージCreative Detailsページが](https://www.braze.com/docs/user_guide/message_building_by_channel/in-app_messages/creative_details/)ある。
+セレクタレイアウトの典型的な例は、[SDK Changelogs](https://www.braze.com/docs/developer_guide/platform_integration_guides/sdk_changelogs/) ページ、または[アプリ内メッセージクリエイティブ詳細ページ](https://www.braze.com/docs/user_guide/message_building_by_channel/in-app_messages/creative_details/)です。
 
 ## 必要なコンポーネント
 
@@ -18,22 +18,22 @@ noindex: true
 
 ## 必須パラメータ
 
-|パラメーター | コンテンツ・タイプ | 詳細 |
+|パラメーター | コンテンツタイプ | 詳細 |
 |---|---|---|
-|`page_order`| 数値 | セクション内でページを順番に並べる。この順番は左側のナビゲーションに反映される。 |
+|`page_order`| 数値 | セクション内でページを順番に並べる。この順序は左側のナビゲーションに反映されます。 |
 | `nav-title`| 英数字 | 左側のナビゲーションに表示されるタイトル。 |
 |`layout`| 英数字 - スペースなし | ドキュメントの[レイアウトセクションから](https://github.com/Appboy/braze-docs/tree/develop/_layouts)レイアウトを選択する。 | 
 |`guide_top_header`|英数字 | ページにタイトルをつける。|
-|`guide_top_text`|英数字 | これはボタンとそのタイトルの真上に表示される。内容によっては引用が必要である。 |
-|`guide_featured_title`| 英数字 | カードにタイトルをつける。これはボタンの真上に配置される。
+|`guide_top_text`|英数字 | ページを説明すると、ボタンとそのタイトルの真上に表示されます。内容によっては引用が必要である。 |
+|`guide_featured_title`| 英数字 | カードにタイトルをつける。ボタンの真上に表示されます。
 |`guide_featured_list`| より多くのYAML、英数字 | 下記の[ガイド掲載フォーマットを](#guide-listing-format)参照のこと。 |
 
 ### ガイド掲載フォーマット
 
-|パラメーター | コンテンツ・タイプ | 詳細 |
+|パラメーター | コンテンツタイプ | 詳細 |
 |---|---|---|
-|`name`| 英数字 | 箱に名前をつける。 |
-| `link`| URLまたはパス | 箱が置かれる場所へのリンク。完全なURL、または（内部リンクの場合は）完全なURLを含むこと。 `/docs...`  |
+|`name`| 英数字 | ボックスに名前を付けます。 |
+| `link`| URLまたはパス | ボックスの移動先へのリンク。完全なURL、または（内部リンクの場合は）完全なURLを含むこと。 `/docs...`  |
 |`image`| パス | 画像の場所へのリンク。 |
 
 フォーマットの例：
diff --git a/_lang/ja/_hidden/archived_layouts/partner_page_template.md b/_lang/ja/_hidden/archived_layouts/partner_page_template.md
index 85ff9274c41..850795c9956 100644
--- a/_lang/ja/_hidden/archived_layouts/partner_page_template.md
+++ b/_lang/ja/_hidden/archived_layouts/partner_page_template.md
@@ -49,7 +49,7 @@ noindex: true
 このセクションでは、パートナーと連携してパートナーのサービスを使用するために必要な条件について説明します。この情報を伝える最良の方法は、「知る必要がある」情報の技術的でない重要な詳細、例えば、あなたの統合が追加のセキュリティチェックやクリアランスの対象となるかどうかなどを、手短に説明する段落を設けることである。次に、この連携の技術的な要件をチャートで説明します。
 
 {% alert important %}
-次の要件は、Braze で必要になる可能性のある一般的な要件です。以下のチャートに記載されている帰属☆タイトル、Origin、リンク、および言い回しを使用することをお勧めします。それぞれの要件が何をするために使われるのかがわかるように、必ず説明を調整すること。
+Braze で必要となる可能性のある一般的な要件を次に示します。次の表に示すように、属性付きのタイトル、Origin、リンク、およびフレーズを使用することをお勧めします。それぞれの要件が何をするために使われるのかがわかるように、必ず説明を調整すること。
 {% endalert %}
 
 | 必要条件 | Origin | アクセス | 説明 |
@@ -60,9 +60,9 @@ noindex: true
 
 ## \[統合の種類] 統合
 
-ここで、統合をステップに分解する。段落が長過ぎないようにしてください。これらは、マーケターと開発者が統合を運用するために使用する技術ドキュメントです。このセクションの唯一の目標は、Brazeユーザーが仕事をこなすのに役立つ説明的な文書を書くことである。セクションタイトルの「統合のタイプ」とは、これがサイド・バイ・サイド統合なのか、サーバー間統合なのか、Out-of-the Boxなのかを示すことを意味する。これにより、このパートナーと連携する方法が複数ある場合に、複数の連携セクションを作成できます。
+ここで、統合をステップに分解する。段落が長過ぎないようにしてください。これらは、マーケターと開発者が統合を運用するために使用する技術ドキュメントです。このセクションの唯一の目標は、Brazeユーザーが仕事をこなすのに役立つ説明的な文書を書くことである。セクションタイトルの「統合のタイプ」とは、これがサイド・バイ・サイド統合なのか、サーバー間統合なのか、Out-of-the Boxなのかを示すことを意味する。これにより、このパートナーと統合する方法が複数ある場合に、複数の統合セクションを持つことができます。
 
-これが Currents の連携である場合、このページを Currents セクションに配置し、Currents 内のそのロケーションにリダイレクトする対応するナビゲーション ページを作成します。
+これが Currents 統合である場合は、このページを Currents セクションに配置し、Currents のその場所にリダイレクトする対応するナビゲーションページを作成する必要があります。
 
 ### ステップ1:これはステップ1の簡単な説明である。
 
@@ -74,11 +74,11 @@ noindex: true
 
 ### ステップ3:ステップの数
 
-メッセージ作成画面に Liquid を挿入する場合などには、統合の使い方の概要を記述します。
+統合の使用方法の概要 - 特に、メッセージ作成画面に Liquid を挿入することを意味する場合。
 
 ## カスタマイズ
 
-これは**オプション**のセクションです。ここでは、2つのパートナー間の統合をカスタマイズする具体的な方法を概説できます。
+これは**オプション**のセクションです。ここでは、2つのパートナー間の統合をカスタマイズするための具体的な方法の概要を説明できます。
 
 ## この統合を使う
 
@@ -90,4 +90,4 @@ noindex: true
 
 ## ユースケース
 
-これはドキュメンテーションの重要な部分となる可能性があります。これはオプションですが、統合の標準的なユースケースや新しいユースケースの概要を記述するのに適しています。これは、リレーションシップの売り込みやアップセルの手段として使用できます。背景情報やアイデアを提示し、また最も重要な点としてこの統合の機能性を視覚化できます。
+これはドキュメンテーションの重要な部分となる可能性があります。これはオプションですが、統合の一般的なユースケースまたは新しいユースケースの概要を説明するのに適しています。これは、リレーションシップを販売またはアップセルする方法として使用できます。コンテキスト、アイデア、そして最も重要なものとして、統合の機能を可視化する方法を提供します。
diff --git a/_lang/ja/_hidden/archived_layouts/partner_page_template_video.md b/_lang/ja/_hidden/archived_layouts/partner_page_template_video.md
index 7879c4a9003..ac65664185c 100644
--- a/_lang/ja/_hidden/archived_layouts/partner_page_template_video.md
+++ b/_lang/ja/_hidden/archived_layouts/partner_page_template_video.md
@@ -51,20 +51,20 @@ noindex: true
 このセクションでは、パートナーと連携してパートナーのサービスを使用するために必要な条件について説明します。この情報を伝える最良の方法は、「知る必要がある」情報の技術的でない重要な詳細、例えば、あなたの統合が追加のセキュリティチェックやクリアランスの対象となるかどうかなどを、手短に説明する段落を設けることである。次に、この連携の技術的な要件をチャートで説明します。
 
 {% alert important %}
-以下の要件は、Brazeが必要とする典型的な要件である。以下の表にあるような、帰属するタイトル、由来、リンク、言い回しを使用することを推奨する。それぞれの要件が何をするために使われるのかがわかるように、必ず説明を調整すること。
+Braze で必要となる可能性のある一般的な要件を次に示します。次の表に示すように、属性付きのタイトル、Origin、リンク、およびフレーズを使用することをお勧めします。それぞれの要件が何をするために使われるのかがわかるように、必ず説明を調整すること。
 {% endalert %}
 
 | 必要条件 | Origin | アクセス | 説明 |
 |---|---|---|---|
 |BrazeワークスペースREST APIキー | Braze プラットフォーム | **設定**>**アプリ設定**ページ | この説明は、ワークスペース REST API キーを使って行う作業を説明するものです。 |
-|Braze APIエンドポイント | Braze プラットフォーム | [リストされたエンドポイント]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)を確認するか、[サポートチケット]({{site.baseurl}}/braze_support/)を登録します。 | 説明保留。 |
+|Braze APIエンドポイント | Braze プラットフォーム | [リストされたエンドポイント]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)を確認するか、[サポートチケット]({{site.baseurl}}/braze_support/)を登録します。 | 説明保留中。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## \[統合の種類] 統合
 
-ここで、統合をステップに分解する。段落が長過ぎないようにしてください。これらは、マーケターと開発者が統合を運用するために使用する技術ドキュメントです。このセクションの唯一の目標は、Brazeユーザーが仕事をこなすのに役立つ説明的な文書を書くことである。セクションタイトルの「統合のタイプ」とは、これがサイド・バイ・サイド統合なのか、サーバー間統合なのか、Out-of-the Boxなのかを示すことを意味する。これにより、このパートナーと統合する方法が複数ある場合、複数の統合セクションを持つことができる。
+ここで、統合をステップに分解する。段落が長過ぎないようにしてください。これらは、マーケターと開発者が統合を運用するために使用する技術ドキュメントです。このセクションの唯一の目標は、Brazeユーザーが仕事をこなすのに役立つ説明的な文書を書くことである。セクションタイトルの「統合のタイプ」とは、これがサイド・バイ・サイド統合なのか、サーバー間統合なのか、Out-of-the Boxなのかを示すことを意味する。これにより、このパートナーと統合する方法が複数ある場合に、複数の統合セクションを持つことができます。
 
-これがカレントの統合である場合、このページはカレントセクションに配置され、カレントのその場所にリダイレクトする対応するナビページが構築されるべきである。
+これが Currents 統合である場合は、このページを Currents セクションに配置し、Currents のその場所にリダイレクトする対応するナビゲーションページを作成する必要があります。
 
 ### ステップ1:これはステップ1の簡単な説明である。
 
@@ -97,18 +97,18 @@ noindex: true
 
 | 可変 | 説明 |
 | -------- | ----------- |
-| ページタイトル | ページのタイトルは何でもいい。これを持っていなければならない。 |
-| 初めての見出し | 大文字で書くことをお勧めする。これもオプションである。 |
+| ページタイトル | ページのタイトルは何でもいい。これを持っていなければなりません。 |
+| 初めての見出し | 大文字で書くことをお勧めする。これはオプションでもあります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 
 ### ステップ3:ステップの数
 
-メッセージコンポーザーにLiquidを挿入する場合は特にそうだ。
+統合の使用方法の概要 - 特に、メッセージ作成画面に Liquid を挿入することを意味する場合。
 
 ## カスタマイズ
 
-これは**オプション**のセクションです。ここでは、2つのパートナー間の統合をカスタマイズする具体的な方法を説明することができる。
+これは**オプション**のセクションです。ここでは、2つのパートナー間の統合をカスタマイズするための具体的な方法の概要を説明できます。
 
 ## この統合を使う
 
@@ -141,11 +141,11 @@ noindex: true
 
 | 可変 | 説明 |
 | -------- | ----------- |
-| ページタイトル | ページのタイトルは何でもいい。これを持っていなければならない。 |
-| 初めての見出し | 大文字で書くことをお勧めする。これもオプションである。 |
+| ページタイトル | ページのタイトルは何でもいい。これを持っていなければなりません。 |
+| 初めての見出し | 大文字で書くことをお勧めする。これはオプションでもあります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 
 ## ユースケース
 
-これはドキュメンテーションの重要な部分となる可能性があります。これは任意であるが、典型的な、あるいは斬新な統合の使用例を概説するのに良い場所である。これは、リレーションシップを売り込んだり、アップセルしたりする方法として使うことができる。コンテキストやアイデアを提供し、最も重要なのは、統合の能力を可視化する方法である。
+これはドキュメンテーションの重要な部分となる可能性があります。これはオプションですが、統合の一般的なユースケースまたは新しいユースケースの概要を説明するのに適しています。これは、リレーションシップを販売またはアップセルする方法として使用できます。コンテキスト、アイデア、そして最も重要なものとして、統合の機能を可視化する方法を提供します。
diff --git a/_lang/ja/_hidden/archived_layouts/post_endpoint.md b/_lang/ja/_hidden/archived_layouts/post_endpoint.md
index c46e9ebf2c5..348dd587479 100644
--- a/_lang/ja/_hidden/archived_layouts/post_endpoint.md
+++ b/_lang/ja/_hidden/archived_layouts/post_endpoint.md
@@ -1,5 +1,5 @@
 ---
-nav_title: "POSTする：[エンドポイント名］"
+nav_title: "POST: [エンドポイント名］"
 article_title: "レイアウト例：POST:ユーザートラック"
 search_tag: Endpoint
 page_order: 4
@@ -31,7 +31,7 @@ This is the description of the endpoint. API descriptions usually start with "Us
 <!-- The rate limit of the endpoint. This pulls from /includes/rate_limits/ and displays specific endpoint limits based on the endpoint provided -->
 {% multi_lang_include rate_limits.md endpoint='default' %}
 
-## リクエスト・ボディ
+## リクエスト本文
 
 <!--This is where you can give more information about your endpoint request body. -->
 
diff --git a/_lang/ja/_hidden/archived_layouts/reference.md b/_lang/ja/_hidden/archived_layouts/reference.md
index 82640bd2533..662878c94da 100644
--- a/_lang/ja/_hidden/archived_layouts/reference.md
+++ b/_lang/ja/_hidden/archived_layouts/reference.md
@@ -47,7 +47,7 @@ noindex: true
 インクルード:
 - この概念の起源(該当する場合)。
 - 必要に応じて、このコンセプトや他の名前に関する外部リソースにリンクします。
-- このコンセプトがどのように使われ、アプリがBrazeに横たわっているか。  
+- このコンセプトが Braze でどのように使われ、適用されているのか。  
 - この概念の利点は何か
 
 
@@ -74,15 +74,15 @@ noindex: true
 </html>
 ```
 
-ユーザー s がコードのサンプリングから調整する必要があるパラメータまたは要素を定義していることを確認します。多くのユーザー s は単にコピーアンドペーストします。
+ユーザーがコードサンプルから調整する必要がある可能性のあるパラメーターまたは要素を定義していることを確認します。多くのユーザーは単にコピーして貼り付けるだけです。
 
 | 変数 | 説明 |
 | -------- | ----------- |
-| ページタイトル | ページには何でもタイトルを付けることができます。これを持っていなければならない。 |
-| 最初の見出し | キャップに入れることをお勧めします。これもオプションです。 |
+| ページタイトル | ページには何でもタイトルを付けることができます。これを持っていなければなりません。 |
+| 最初の見出し | キャップに入れることをお勧めします。これはオプションでもあります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 
 ## この考え方に関するトピックス2
 
-2つ目のトピックが追加された場合は、すぐに最初のコンセプトと区別してください。次に、コンセプトの説明に進みます。ダイアグラムはお気軽にお付けください！
+2番目のトピックが追加された場合は、最初のコンセプトとすぐに区別するようにしてください。次に、コンセプトの説明に進みます。ダイアグラムはお気軽にお付けください！
diff --git a/_lang/ja/_hidden/archived_layouts/reference_video.md b/_lang/ja/_hidden/archived_layouts/reference_video.md
index a3a4e94b388..924c70ad781 100644
--- a/_lang/ja/_hidden/archived_layouts/reference_video.md
+++ b/_lang/ja/_hidden/archived_layouts/reference_video.md
@@ -42,7 +42,7 @@ noindex: true
 
 {% multi_lang_include video.html id="XY5uXoKIvFY" align="right" %}
 
->  このタイプの記事は、コンセプトを説明し、技術的なプロセスや製品の内容（キャンバスのステップ、セグメンテーション、特定のタイプのオブジェクトなど）に関する具体的な情報を含んでいる。もう一つのReferenceテンプレートはGlossary（用語集）である。このフォーマットは、説明が必要な特定のコンセプトがない限り、API用語集やリファレンス文書には使用されない。このページで、[これと](#what-is-x-concept) [これと](#topic-1-regarding-this-concept) [これ](#what-is-x-concept) [以外を](#topic-2-regarding-this-concept)学ぶという概要を必ず説明する。これは[リファレンス文書の良いサンプル](https://guide.meteor.com/code-style.html)だ。これは[非常に技術的な参考文書の](https://www.w3schools.com/html/html_intro.asp)良い例である。
+>  このタイプの記事は、コンセプトを説明し、技術的なプロセスや製品の内容（キャンバスのステップ、セグメンテーション、特定のタイプのオブジェクトなど）に関する具体的な情報を含んでいる。リファレンステンプレートのもう1つのタイプは、用語集です。この形式は、説明が必要な特定の概念がない限り、当社の API 用語集やリファレンスドキュメントでは使用されません。このページで、[これ](#what-is-x-concept)と [これ](#topic-1-regarding-this-concept)と[これ](#topic-2-regarding-this-concept)以外を学ぶという概要を必ず説明する。これは[リファレンス文書の良いサンプル](https://guide.meteor.com/code-style.html)です。これは[非常に技術的な参考ドキュメント](https://www.w3schools.com/html/html_intro.asp)の良い例です。
 >
 > もっと詳しく知りたいならビデオを見てほしい」と必ず伝えること。
 
@@ -50,14 +50,14 @@ noindex: true
 ## Xコンセプトとは
 
 含む：
-- 関連性があれば、このコンセプトの成り立ちを説明する。
+- このコンセプトの起源 (関連する場合)
 - 必要に応じて、このコンセプトや他の名称に関する外部リソースへのリンクを貼る。
-- このコンセプトがブレイズでどのように使われ、応用されているのか。
+- このコンセプトが Braze でどのように使われ、適用されているのか。
 - このコンセプトの利点は何だろうか？
 
 ## トピック1 このコンセプトについて
 
-これは、特定のタイプのキャンバス・ステップがチャンネルとどのように組み合わされて使われるのかなど、このコンセプトの特定の側面を説明するものでなければならない。ワイルドでこの操作を実行する方法の例を確認するには、[このチュートリアルへのリンクを確認してください]()。
+これは、特定のタイプのキャンバス・ステップがチャンネルとどのように組み合わされて使われるのかなど、このコンセプトの特定の側面を説明するものでなければならない。これを実際に行う方法の例を確認したい場合は、[そのチュートリアルへのリンク]()を確認してください。
 
 
 ### コードサンプル
@@ -83,10 +83,10 @@ noindex: true
 
 | 可変 | 説明 |
 | -------- | ----------- |
-| ページタイトル | ページのタイトルは何でもいい。これを持っていなければならない。 |
-| 初めての見出し | 大文字で書くことをお勧めする。これもオプションである。 |
+| ページタイトル | ページのタイトルは何でもいい。これを持っていなければなりません。 |
+| 初めての見出し | 大文字で書くことをお勧めする。これはオプションでもあります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## トピック2 このコンセプトについて
 
-2つ目のトピックを追加する場合は、最初のコンセプトとすぐに区別できるようにすること。それからコンセプトの説明に入る。図を自由に追加してほしい！
+2番目のトピックが追加された場合は、最初のコンセプトとすぐに区別するようにしてください。それからコンセプトの説明に入ります。図は自由に追加してください。
diff --git a/_lang/ja/_hidden/archived_layouts/solution.md b/_lang/ja/_hidden/archived_layouts/solution.md
index 67b74d056bb..8675a5b695e 100644
--- a/_lang/ja/_hidden/archived_layouts/solution.md
+++ b/_lang/ja/_hidden/archived_layouts/solution.md
@@ -40,13 +40,13 @@ noindex: true
 
 # ソリューション記事タイトル
 
-> ソリューションは特別なヘルプ記事です。トラブルシューティングは行われませんが、より技術的な問題を解決するためのオプションを提供します。この導入パラグラフでは、基本的な状況を提起すべきです。ここから、この問題を解決するためのオプションがいくつかあると言えます。
+> ソリューションは特別なヘルプ記事です。トラブルシューティングは行われませんが、より技術的な問題を解決するためのオプションを提供します。この導入パラグラフでは、基本的な状況を仮定する必要があります。ここから、この問題を解決するためのオプションがいくつかあると言えます。
 >
-> [オプション1:こんなことをする](#option-one)
+> [オプション1:これをする](#option-one)
 > <br>
 > [オプション2:他のことをする](#option-two)
 
-## オプション 1: こんなことをする {#option-one}
+## オプション 1: これをする{#option-one}
 
 ここでは、何かを行う方法を説明します。
 
@@ -69,9 +69,9 @@ this is the code snippet you need to do it.
 ## 次のステップ
 
 おめでとうございます！このチュートリアル、トラブルシューティング記事、またはソリューションを完了しました!つまり、次のようになります。
-1. 知っておくべきだったこと、
-2. 完了すべきタスク
-3. あなたが今、あるいは次のことをする準備ができていなければならない。
+1. あなたが学ぶべきだったこと
+2. 完了したはずのタスク
+3. 今すぐ、または次に行う準備ができている必要があること。
 
 ### 関連記事
 
@@ -80,7 +80,7 @@ this is the code snippet you need to do it.
 - [関連条項2](#solution-2):役に立つ理由の説明。
 - [関連記事3](#solution-3):役に立つ理由の説明。
 
-### それでも失われますか?
+### まだ迷っていますか？
 
 この記事が役に立たなかった場合は、フィードバックまたは開封を[サポートチケット][support]のままにしてください!
 
diff --git a/_lang/ja/_hidden/archived_layouts/tutorial.md b/_lang/ja/_hidden/archived_layouts/tutorial.md
index 3a9f61bc67a..d3eead36bc0 100644
--- a/_lang/ja/_hidden/archived_layouts/tutorial.md
+++ b/_lang/ja/_hidden/archived_layouts/tutorial.md
@@ -46,13 +46,13 @@ noindex: true
 
 > この記事では、XYZの実行方法について説明します。このチュートリアルの終わりまでに、A、B、およびCができるようになるはずです！
 
-## ステップ1:最初のことをする
+## ステップ1:最初に行う
 
-これはこのステップで達成することです。これが再現する方法です。
+これが、このステップで実行する内容です。これが再現する方法です。
 
 必要に応じて、[他の参照にリンクしてください]({{site.baseurl}}/home/templates/reference_video/)。
 
-### コード Sample
+### コードサンプル
 
 技術的な概念を説明している場合は、ここに注意し、コードサンプルを示してください。
 
@@ -81,7 +81,7 @@ noindex: true
 
 ## ステップ2:次のことをする
 
-これはこのステップで達成することです。これが再現する方法です。
+これが、このステップで実行する内容です。これが再現する方法です。
 
 このステップを追加のステップに分解する必要がある場合は、次のいずれかを実行できます:
 1. 番号や箇条書きを使用するか、
@@ -90,7 +90,7 @@ noindex: true
 ### これはステップ2の一部でもあります
 
 {% alert important %}
-重要なことが発生したら、ユーザーに必ず伝えてください。最後まで待たないで！あなたのユーザーは一緒に進めていくでしょう - 人々はチュートリアルを始める_前_に指示を読みません。
+重要なことが発生したら、ユーザーに必ず伝えてください。最後まで待たないでください！あなたのユーザーは一緒に進めていくでしょう - 人々はチュートリアルを始める_前_に指示を読みません。
 {% endalert %}
 
 ## ステップ3:最後のことをする
@@ -99,9 +99,9 @@ noindex: true
 
 ## 次のステップ
 
-おめでとうございます！このチュートリアル、トラブルシューティング記事、またはソリューションを完了しました！これは、あなたが持っている必要があることを意味します：
-1. あなたが学ぶべきこと
-2. タスクは完了しているはずです、そして
+おめでとうございます！このチュートリアル、トラブルシューティング記事、またはソリューションを完了しました！つまり、次のものが必要です。
+1. あなたが学ぶべきだったこと
+2. 完了したはずのタスク
 3. 今すぐまたは次に行う準備ができていること。
 
 ### 関連記事
diff --git a/_lang/ja/_hidden/archived_layouts/tutorial_video.md b/_lang/ja/_hidden/archived_layouts/tutorial_video.md
index 42fc2bf003e..353a0c23e4a 100644
--- a/_lang/ja/_hidden/archived_layouts/tutorial_video.md
+++ b/_lang/ja/_hidden/archived_layouts/tutorial_video.md
@@ -41,10 +41,10 @@ noindex: true
 ---
 {% comment %}
 このレイアウトについて
-このレイアウトは、クイックスタートガイド、製品ウォークスルー、トラブルシューティングウォークスルーのためのもので、ビデオ付きである。ビデオは右側に配置され、そのまま固定される。TOCはH2ヘッダーのみを表示するので、H2とすべきステップだけはそのように書くべきであることに注意されたい：
-「ステップ1：ステップが何であれ」だ。
-チュートリアルだ：
-指導コンセプトの一般的なウォークスルー。実践的な知識を含むべきである。ひとつのトピックに集中する（キャンペーンの作り方、キャンバスの作り方など）。特定の課題（特定のユーザーをターゲットにする方法、場所に基づくセグメント化方法など）を解決するために、段階を追って説明するゴールまたはタスク指向の記事。
+このレイアウトは、クイックスタートガイド、製品ウォークスルー、トラブルシューティングウォークスルーのためのもので、ビデオ付きである。動画は右側に配置され、固定されます。TOCはH2ヘッダーのみを表示するので、H2とすべきステップだけはそのように書くべきであることに注意されたい：
+「ステップ1：ステップがどんなものであっても」。
+チュートリアル:
+指導コンセプトの一般的なウォークスルー。実用的な知識を含むべきです。ひとつのトピックに集中する（キャンペーンの作り方、キャンバスの作り方など）。特定の課題（特定のユーザーをターゲットにする方法、場所に基づくセグメント化方法など）を解決するために、段階を追って説明するゴールまたはタスク指向の記事。
 {% endcomment %}
 # このビデオチュートリアルのタイトルの付け方
 
@@ -54,7 +54,7 @@ noindex: true
 
 これがこのステップで達成することだ。その再現方法を紹介しよう。
 
-[必要に応じて他の参考文献にリンクする]({{site.baseurl}}/home/templates/reference_video/)ようにする。
+[必要に応じて、他の参照にリンクしてください]({{site.baseurl}}/home/templates/reference_video/)。
 
 ### コードサンプル
 
@@ -79,8 +79,8 @@ noindex: true
 
 | 可変 | 説明 |
 | -------- | ----------- |
-| ページタイトル | ページのタイトルは何でもいい。これを持っていなければならない。 |
-| 初めての見出し | 大文字で書くことをお勧めする。これもオプションである。 |
+| ページタイトル | ページのタイトルは何でもいい。これを持っていなければなりません。 |
+| 初めての見出し | 大文字で書くことをお勧めする。これはオプションでもあります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 
@@ -89,15 +89,15 @@ noindex: true
 これがこのステップで達成することだ。その再現方法を紹介しよう。
 
 このステップをさらに細分化する必要がある場合は、次のいずれかを実行する：
-1. 数字や箇条書きを使う。
-2. H3ヘッダーを使う。
+1. 数字または箇条書きを使用するか、
+2. H3 ヘッダーを使います。
 
 ### これもステップ2の一部である。
 
 なお、このサブステップは、右側のビデオの下のTOCには表示されない。
 
 {% alert important %}
-重要なことは、その都度ユーザーに伝えるようにしよう。最後まで待つな！ユーザーは、チュートリアルを始める_前に_説明を読まない。
+重要なことは、その都度ユーザーに伝えるようにしよう。最後まで待たないでください！ユーザーは進みながら学ぶことになります。ユーザーはチュートリアルを始める_前に_説明を読みません。
 {% endalert %}
 
 ## ステップ3:最後のことをする
@@ -106,7 +106,7 @@ noindex: true
 
 ## 次のステップ
 
-おめでとうございます！あなたはこのチュートリアル、トラブルシューティング記事、または解決策を完了した！つまり、あなたは持っているべきだということだ：
+おめでとうございます！あなたはこのチュートリアル、トラブルシューティング記事、または解決策を完了した！つまり、次のものが必要です。
 1. あなたが学ぶべきだったこと
 2. 完了したはずのタスク
 3. 今すぐ、あるいは次にやるべきことがある。
@@ -118,7 +118,7 @@ noindex: true
 - [関連記事2](#solution-2)：なぜ役に立つのかを説明する。
 - [関連記事3](#solution-3)：なぜ役に立つのかを説明する。
 
-### まだ迷っているのか？
+### まだ迷っていますか？
 
 この記事が役に立たなかった場合は、フィードバックを残すか、[サポートチケットを][support]開く！
 
diff --git a/_lang/ja/_hidden/archived_layouts/use_case.md b/_lang/ja/_hidden/archived_layouts/use_case.md
index ade74d5844d..c2325a28087 100644
--- a/_lang/ja/_hidden/archived_layouts/use_case.md
+++ b/_lang/ja/_hidden/archived_layouts/use_case.md
@@ -40,9 +40,9 @@ noindex: true
 
 # ユースケース名
 
-> ユースケーステンプレートへようこそ！ここには、Brazeユースケースのウォークスルーを書くために必要なものがすべて揃っている。この最初のセクションでは、ユースケースを数センテンスで説明する。おそらく、「このユースケースは、プッシュやEメールなどを使って、失効したユーザーをどのようにコンテンツに再導入できるかを探るものだ」というようなものだろう。
+> ユースケーステンプレートへようこそ！ここには、Brazeユースケースのウォークスルーを書くために必要なものがすべて揃っている。この最初のセクションでは、ユースケースを数文で説明します。おそらく、「このユースケースでは、プッシュ、メールなどを使用して、失効したユーザーをコンテンツに再導入する方法について説明します」のようなものです。
 >
-> ここでユースケースシナリオを設定する。なぜ誰かがこのページを読みたいと思うのか？読者を「その気にさせる」ために、心をつかむ仮定の話を提示する。おそらく..."サリーの会社（仮定の化粧品会社）は、ユーザーの一部が、メールは開くものの、アプリにはほとんど興味を示していないことに気づく。彼らは何もクリックしないが、それらを開く！サリーは、これらの人々の20％を再びアプリユーザーに変えたいと考えた。
+> ここでユースケースシナリオを設定する。なぜ誰かがこのページを読みたいと思うのか？読者を「その気にさせる」ために、心をつかむ仮定の話を提示する。おそらく...「サリーの会社 (架空の化粧品会社) は、ユーザーの一部が、メールは開くものの、アプリにはほとんど興味を示していないことに気がつきます。何もクリックしないのに、開封するのです!サリーは、これらの人々の20%を再びアプリユーザーに変えたいと考えました。
 >
 > このユースケースの目標は以下の通りである（先のシナリオを分解する）：
 > - 目標1
@@ -51,39 +51,39 @@ noindex: true
 
 ## 推奨される指標
 
-測定について話す時だ！ブレイズ・ユーザーはキャンペーンをどのように評価すべきか？どのようなコンバージョン指標を設定すべきか？以下の表に列挙する。
+測定について話す時です！ブレイズ・ユーザーはキャンペーンをどのように評価すべきか？どのようなコンバージョン指標を設定すべきか？以下の表に列挙する。
 
 | メートル | 説明 | データ型 |
 | ------ | ----------- | --------- |
-| コンバージョン1 | これはコンバージョンだ。理由」があるから測るべきだ。 | ブールである。 |
-| コンバージョン2 | これもまた変換である。理由」があるから測るべきだ。 | ブールである。 |
-| 年齢 | これはユーザー属性である。理由」があるから測るべきだ。 | 整数。 |
+| コンバージョン1 | これはコンバージョンです。「理由」があるので測るべきです。 | ブール値。 |
+| コンバージョン2 | これはまた別のコンバージョンです。「理由」があるので測るべきです。 | ブール値。 |
+| 年齢 | これはユーザー属性である。「理由」があるので測るべきです。 | 整数。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## キャンペーン／キャンバスの作り方
 
-この部分を書くときは、彼らがやるべきことを「戦略」と「ステップ」に分けて書くこと。ステップに次のような名前をつければ、一目瞭然だ。ステップ（i.e., Click this button; click that button）を明示的に書き出さないこと。その代わりに、ユースケースの目標を達成するためのステップを記述することで、指示し導く。
+この部分を書くときは、彼らがやるべきことを「戦略」と「ステップ」に分けて書くこと。ステップに次のような名前をつければ、一目瞭然だ。手順を明示的に記述しないでください (i.e。このボタンをクリックします;そのボタンをクリックします)。その代わりに、ユースケースの目標を達成するためのステップを記述することで、指示し導く。
 
 ### ステップ1:周回遅れのユーザーのためにキャンバスを設定する（オーディエンスへのアドバイス）
 
-オーディエンスについて話すとき、セグメントやフィルターの使い方を指示する必要はない。その代わりに、どのようにオーディエンスをラプシング・ユーザーに絞り込み、他の誰にも行かないようにするか、なぜそれが重要なのかを指導する。例えば、数日間アプリを使用していないユーザーや、メールを開封していないユーザーを選択するといった具合だ。長い間アプリから遠ざかっていて、データポイントの価値がないかもしれない人を除外したい場合は、フィルターを適用することを確認する。"
+オーディエンスについて話すときに、セグメントやフィルターの使用方法について指示する必要はありません。代わりに、オーディエンスを離脱ユーザーに絞り込み、他のユーザーに流れないようにする方法と、それがなぜ重要なのかを説明します。たとえば、「数日間アプリを使用していないユーザーや、メールを開封していないユーザーを選択するなど、いくつかの方法で離脱ユーザーを絞り込むことができます。あまりにも長い間アプリから離れていて、データポイントの価値がないかもしれないユーザーを除外する場合は、必ずフィルターを適用してください」
 
 ### ステップ2:適切なタイミングでメッセージを送る
 
-もしそれが重要なら、いつメッセージを送るかについて話す。そうではないかもしれない！せめて、現地時間で送信することがあることを伝えてほしい。あるいは、この特定の状況をAPIでトリガーする方法や、キャンバスを使用していて、アクションに基づいてステップをトリガーする方が良い場合（メールを開封し、少なくともその後1日はクリックしないなど）も知らせる。
+重要な場合は、メッセージを送信するタイミングについて話します。そうではない可能性もあります！少なくとも、現地時間で送信することができるということを伝えておいてください。あるいは、この特定の状況をAPIでトリガーする方法や、キャンバスを使用していて、アクションに基づいてステップをトリガーする方が良い場合（メールを開封し、少なくともその後1日はクリックしないなど）も知らせる。
 
 ### ステップ3:メッセージを構築する
 
-ここでベストプラクティスについてアドバイスができる。いくつかのことを列挙するだけでも、これをすることを強く勧める。画像も追加したい。
+ここでベストプラクティスについてアドバイスができる。いくつかのことをリストアップするだけだとしても、これを行うことを強くお勧めします。画像も追加します。
 
 ### ステップ 4:その他
 
-もし、キャンバスの中でウェイティング・ステップについて話すなど、追加のステップが必要なら、こことそれ以降のステップでそれを続けるだろう。記事を長くしすぎてはいけない。
+追加ステップを追加する必要がある場合 (キャンバスで待機ステップなどについて説明する場合など) は、ここと以降のステップで続けます。記事を長くしすぎてはいけない。
 
 
 ## 次のステップ
 
-おめでとうございます！あなたはこのチュートリアル、トラブルシューティング記事、または解決策を完了した！つまり、あなたは持っているべきだということだ：
+おめでとうございます！あなたはこのチュートリアル、トラブルシューティング記事、または解決策を完了した！つまり、次のものが必要です。
 1. あなたが学ぶべきだったこと
 2. 完了したはずのタスク
 3. 今すぐ、あるいは次にやるべきことがある。
@@ -91,11 +91,11 @@ noindex: true
 ### 関連記事
 
 記事で取り上げたことについてもっと知りたい人は、チェックしてみてほしい：
-- [関連記事 1](#solution-1)：なぜ役に立つのかを説明する。
+- [関連記事1](#solution-1)：なぜ役に立つのかを説明する。
 - [関連記事2](#solution-2)：なぜ役に立つのかを説明する。
 - [関連記事3](#solution-3)：なぜ役に立つのかを説明する。
 
-### まだ迷っているのか？
+### まだ迷っていますか？
 
 この記事が役に立たなかった場合は、フィードバックを残すか、[サポートチケットを][support]開く！
 
diff --git a/_lang/ja/_hidden/archived_layouts/use_case_video.md b/_lang/ja/_hidden/archived_layouts/use_case_video.md
index 3382c63c0df..8a16464ed18 100644
--- a/_lang/ja/_hidden/archived_layouts/use_case_video.md
+++ b/_lang/ja/_hidden/archived_layouts/use_case_video.md
@@ -1,5 +1,5 @@
 ---
-nav_title: ビデオのユースケース
+nav_title: 動画のユースケース
 
 page_order: 7
 
@@ -42,9 +42,9 @@ noindex: true
 
 {% multi_lang_include video.html id="XY5uXoKIvFY" align="right" %}
 
-> ユースケーステンプレートへようこそ!ここでは、Braze ユースケースのウォークスルーを記述するために必要なすべての情報を確認します。この最初の節では、いくつかの文章でユースケースを説明します。おそらく、&quot のようなものです。このユースケースでは、プッシュ、メールなど" を使用してコンテンツに離脱ユーザーを再導入する方法について説明します。
+> ユースケーステンプレートへようこそ!ここには、Braze のユースケースの説明を書くために必要なものがすべて揃っています。この最初のセクションでは、ユースケースを数文で説明します。おそらく、「このユースケースでは、プッシュ、メールなどを使用して、失効したユーザーをコンテンツに再導入する方法について説明します」のようなものです。
 >
-> ここでは、ユースケースシナリオを設定します。なぜ、誰かがこのページを読みたがるのだろうか。&quot にグリップ仮説を提示します。気分" でリーダを取得します。おそらく・・・"Sallyの会社は、仮のメーキャップ企業であるが、そのユーザーの一部は、メールを開封しているにもかかわらず、アプリ アプリにほとんど関心を示していないことを発見した。何もクリックしないで、開封してしまいます！サリーは、これらの人員の20%を再びアプリ ユーザーS&Quotに転換したいと決めた。
+> ここでは、ユースケースシナリオを設定します。なぜこのページを読みたいのでしょうか?「読者をその気にさせる」ために、魅力的な仮説を提示します。おそらく・・・「サリーの会社 (架空の化粧品会社) は、ユーザーの一部が、メールは開くものの、アプリにはほとんど興味を示していないことに気がつきます。何もクリックしないで、開封してしまいます！サリーは、これらの人々の20%を再びアプリユーザーに変えたいと考えました。
 >
 > このユースケースの目標は次のとおりです(前述のシナリオの内訳)。
 > - 目標1
@@ -54,22 +54,22 @@ noindex: true
 
 ## 推奨されるメトリック
 
-測定についてお話しする時間です！Brazeユーザは、どのようにしてキャンペーンを測定すべきか?どのようなコンバージョン指標を設定すべきか?次の表に示します。
+測定について話す時です！Brazeユーザは、どのようにしてキャンペーンを測定すべきか?どのようなコンバージョン指標を設定すべきか?次の表に示します。
 
 | メトリック | 説明 | データ型 |
 | ------ | ----------- | --------- |
-| 変換1 | これはコンバージョンです。"reasons" のため測定する必要があります。 | ブール値。 |
-| 変換2 | これもコンバージョンです。"reasons" のため測定する必要があります。 | ブール値。 |
-| 年齢 | これはユーザー 属性です。"reasons" のため測定する必要があります。 | 整数。 |
+| 変換1 | これはコンバージョンです。「理由」があるので測るべきです。 | ブール値。 |
+| 変換2 | これはまた別のコンバージョンです。「理由」があるので測るべきです。 | ブール値。 |
+| 年齢 | これはユーザー 属性です。「理由」があるので測るべきです。 | 整数。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## このキャンペーン/キャンバスの作成方法
 
-記事のこの部分を書くときは、戦略とステップによって、何をすべきかを分けてみてください。これは、次のようにステップs を命名することによって明らかにすることができます。ステップを明示的に記述しないでください(i.e.このボタンをクリックします。そのボタンをクリックします)。代わりに、ユースケースの目標を達成するステップを説明し、指導してください。
+記事のこの部分を書くときは、戦略とステップによって、何をすべきかを分けてみてください。次のようにステップに名前を付けることで、これを明確にできます。ステップを明示的に記述しないでください (i.e。このボタンをクリックします; そのボタンをクリックします)。代わりに、ユースケースの目標を達成するステップを説明し、指導してください。
 
-### ステップ1:ラップシングユーザー用にキャンバスを設定する(視聴者にアドバイス)
+### ステップ1:離脱ユーザーのためのキャンバスの設定 (オーディエンスに関するアドバイス)
 
-オーディエンスについて話すときに、セグメントまたはフィルタの使用方法を指導する必要はありません。代わりに、自分のオーディエンスをラップシングユーザに絞り込み、それが他の誰にも行かないようにする方法、そしてそれが大事な理由について、彼らを案内してください。&quotのようなもの;アプリは、いくつかの方法で離脱ユーザーsを絞り込むことができます。たとえば、数日間アプリを使用していないユーザーを選択したり、それが欲しいものであれば開封をメールにしたりします。アプリから遠ざかっている人を除外したい場合は、必ずフィルターをアプリしてください。データポイントのS&Quot に見合う価値がないかもしれません。
+オーディエンスについて話すときに、セグメントやフィルターの使用方法について指示する必要はありません。代わりに、オーディエンスを離脱ユーザーに絞り込み、他のユーザーに流れないようにする方法と、それがなぜ重要なのかを説明します。たとえば、「数日間アプリを使用していないユーザーや、メールを開封していないユーザーを選択するなど、いくつかの方法で離脱ユーザーを絞り込むことができます。あまりにも長い間アプリから離れていて、データポイントの価値がないかもしれないユーザーを除外する場合は、必ずフィルターを適用してください」
 
 
 ### コードサンプル
@@ -91,34 +91,34 @@ noindex: true
 </html>
 ```
 
-ユーザー s がコードのサンプリングから調整する必要があるパラメータまたは要素を定義していることを確認します。多くのユーザー s は単にコピーアンドペーストします。
+ユーザーがコードサンプルから調整する必要がある可能性のあるパラメーターまたは要素を定義していることを確認します。多くのユーザーは単にコピーして貼り付けるだけです。
 
 | 変数 | 説明 |
 | -------- | ----------- |
-| ページタイトル | ページには何でもタイトルを付けることができます。これを持っていなければならない。 |
-| 最初の見出し | キャップに入れることをお勧めします。これもオプションです。 |
+| ページタイトル | ページには何でもタイトルを付けることができます。これを持っていなければなりません。 |
+| 最初の見出し | キャップに入れることをお勧めします。これはオプションでもあります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 
 ### ステップ2:正しい時間にメッセージを送る
 
-もしそれが重要なら、あなたのメッセージをいつ送るかについて話しましょう。そうではないかもしれない!少なくとも現地時間で送ることが物であることを彼らに知らせてください。あるいは、このような特殊な状況をトリガーしてAPIを提供する方法、またはキャンバスを使用している場合でも、アクションに基づいてステップをトリガーする方がよいことを知らせてください(開封がメールを実行し、少なくとも1日以上クリックしないなど)。
+重要な場合は、メッセージを送信するタイミングについて話します。そうではない可能性もあります！少なくとも現地時間で送ることが物であることを彼らに知らせてください。あるいは、このような特殊な状況をトリガーしてAPIを提供する方法、またはキャンバスを使用している場合でも、アクションに基づいてステップをトリガーする方がよいことを知らせてください(開封がメールを実行し、少なくとも1日以上クリックしないなど)。
 
 ### ステップ3:メッセージの作成
 
-ここでは、ベストプラクティスについてアドバイスできます。たとえいくつかのものをリストするだけでも、これをすることを強くお勧めします。また、いくつかの"画像sを追加します。
+ここでは、ベストプラクティスについてアドバイスできます。たとえいくつかのものをリストするだけでも、これをすることを強くお勧めします。画像も追加します。
 
 ### ステップ 4:その他すべて
 
-追加ステップを追加する必要がある場合は、待機ステップs などをキャンバスで話すなど、それをこことそれ以降のステップsで続けます。しかし、あまり長く物を作らないでください - オーディエンスを失いたくないです。
+追加ステップを追加する必要がある場合 (キャンバスで待機ステップなどについて説明する場合など) は、これ以降のステップで続けます。しかし、記事をあまり長くしないでください - オーディエンスを失いたくありません。
 
 
 ## 次のステップ
 
 おめでとうございます！このチュートリアル、トラブルシューティング記事、またはソリューションを完了しました!つまり、次のようになります。
-1. 知っておくべきだったこと、
-2. 完了すべきタスク
-3. あなたが今、あるいは次のことをする準備ができていなければならない。
+1. あなたが学ぶべきだったこと
+2. 完了したはずのタスク
+3. 今すぐ、または次に行う準備ができている必要があること。
 
 ### 関連記事
 
@@ -127,7 +127,7 @@ noindex: true
 - [関連条項2](#solution-2):役に立つ理由の説明。
 - [関連記事3](#solution-3):役に立つ理由の説明。
 
-### それでも失われますか?
+### まだ迷っていますか？
 
 この記事が役に立たなかった場合は、フィードバックまたは開封を[サポートチケット][support]のままにしてください!
 
diff --git a/_lang/ja/_hidden/compliance/sms_channel.md b/_lang/ja/_hidden/compliance/sms_channel.md
index f82de3c7a04..6c6456e8544 100644
--- a/_lang/ja/_hidden/compliance/sms_channel.md
+++ b/_lang/ja/_hidden/compliance/sms_channel.md
@@ -9,11 +9,11 @@ noindex: true
 
 # SMS/MMSサービス（「SMSチャンネル」）のコンプライアンス文書
 
-_改定日1 2024年3月_
+_改定日2024年3月1日_
 
-_(改定日時点で有効、変更される場合がある）_
+_(改定日より有効、変更される場合がある)_
 
-顧客の SMS チャンネルの利用に関しては、以下の追加条項が適用される： 
+顧客による SMS チャネルの使用に関連して、以下の追加条項が適用されます。 
 
 ## 定義
 
@@ -25,18 +25,18 @@ _(改定日時点で有効、変更される場合がある）_
 
 ## 適用される業界標準とベストプラクティス
 
-SMS/MMSメッセージを送信する場合、お客様は、SMS/MMSプロバイダーの許容される使用およびメッセージングポリシー、適用される業界標準およびガイドライン、ならびに該当する場合は、Brazeの[許容される使用ポリシーに](https://www.braze.com/company/legal/aup)詳しく規定されているように、お客様がSMS/MMSメッセージを送信しようとする国の業界規範および適用される通信事業者のガイドラインを遵守しなければならない。 
+SMS/MMS メッセージを送信する場合、顧客は、Braze の[利用規定](https://www.braze.com/company/legal/aup)に詳細が記載されているとおり、SMS/MMS プロバイダーの該当する利用ポリシーおよびメッセージングポリシー、該当する業界標準およびガイドライン、および該当する場合はお客様が SMS/MMS メッセージを送信しようとしている国の業界規範および該当する通信事業者ガイドラインを遵守する必要があります。 
 
 キャリアおよびアグリゲーターを含む、SMS/MMSメッセージの送信に関与する第三者プロバイダーは、その規約または適用法に違反して送信されたSMS/MMSメッセージに基づき、料金または罰則を課す場合がある。お客様は、かかる料金または違約金がお客様に課されるかBrazeに課されるかにかかわらず、お客様がかかる第三者プロバイダーの条件に違反したことに起因する料金および違約金を支払う責任を負うものとする。
 
 ## SMSサブプロセッサー
 
-SMSチャネルの提供において、Brazeは、[www.braze.com](http://www.braze.com/subprocessors)/subprocessorsのサブプロセッサー一覧に含まれるSMS/MMSプロバイダーを利用することができる。
+Braze は、SMS チャネルの提供において、[www.braze.com/subprocessors](http://www.braze.com/subprocessors) のサブプロセッサーのリストに含まれる任意の SMS/MMS プロバイダーを使用することができます。
 
 ## 免責事項
 
-Brazeは、システム容量、メッセージスループット、またはエンドユーザーのデバイスへの実際の配信に関する責任を含め、SMS/MMSメッセージの送信または処理に関与するサードパーティプロバイダ（キャリアおよびアグリゲータを含む）に関して、いかなる表明、保証、責任および補償義務も否認する。 
+Braze は、SMS/MMSメッセージ (キャリアおよびアグリゲーターを含む) の送信または処理に関与するサードパーティプロバイダーに関する表明、保証、責任および補償義務を否認します。これには、システム容量、メッセージスループット、または、エンドユーザーの装置への実際の配信に関連する責任も含まれます。 
 
 ## 一般用語
 
-本契約に基づく顧客の義務の一般性を制限することなく、また、疑義を避けるために、顧客は、本チャネルの使用に関連して、必要なすべての権利、同意、及び権限を取得し、法的に適切なプライバシー通知を提供すること、並びに本チャネルを通じてメッセージを送信し、又は該当する場合にはこれを受信するために法的に必要なすべての同意及び権限を取得することについて、単独で責任を負うものとする。 
\ No newline at end of file
+本契約に基づく顧客の義務の一般性を制限することなく、また、疑義を回避するためにのみ、顧客は、本チャネルの使用に関連して、必要なすべての権利、同意、承認を取得し、本チャネルの使用に関連して法的に適切なプライバシー通知を提供し、本チャネルを通じてメッセージを送信または該当する場合、受信するために法的に必要なすべての同意および承認を取得することについて、単独で責任を負うものとします。 
\ No newline at end of file
diff --git a/_lang/ja/_hidden/compliance/webhook_channel.md b/_lang/ja/_hidden/compliance/webhook_channel.md
index 535a07cc034..6b4b726d69f 100644
--- a/_lang/ja/_hidden/compliance/webhook_channel.md
+++ b/_lang/ja/_hidden/compliance/webhook_channel.md
@@ -11,22 +11,22 @@ noindex: true
 
 _改定日2024年5月22日_
 
-_(改定日時点で有効、変更される場合がある）_
+_(改定日より有効、変更される場合がある)_
 
-顧客によるウェブフック・チャネルの利用に関連して、以下の追加条件が適用される：
+顧客による Webhooks チャネルの使用に関連して、以下の追加条項が適用されます。
 
 ## Webhooksチャンネル利用規約
 
-適用されるチャネルコンプライアンス文書で別途許可されている場合を除く、
-(a) 顧客は、Brazeが同じ結果を得るためのネイティブ機能を提供する場合、Webhookを使用しないものとする。
-(b) お客様は、BrazeがBrazeサービスを通じて当該メッセージを送信するためのネイティブなメカニズムを提供する限りにおいて、第三者プロバイダーのプラットフォームを通じてメッセージの送信をトリガーするためにWebhookを使用しないものとする。
+該当するチャネルコンプライアンスドキュメントで別段の許可がない限り、
+(a) 顧客は、Braze が同じ結果を得るためのネイティブ機能を提供する場合、Webhook を使用しないものとします。
+(b) 顧客は、Braze が Braze サービスを通じて当該メッセージを送信するためのネイティブなメカニズムを提供する限りにおいて、サードパーティプロバイダーのプラットフォームを使用してメッセージの送信をトリガーするために Webhook を使用しないものとします。
 
-Brazeが、お客様の現在のサブスクリプション契約期間中に、Brazeサービスにおいて新規または更新されたメカニズムを一般的に利用可能とした場合、お客様は、新規メカニズムの一般リリース日から6ヶ月後またはお客様のサブスクリプション契約期間の当年度末のいずれか遅い時点において、指定された第三者プラットフォームを通じてメッセージ送信をトリガーするためにWebhookを使用することが禁止されるものとする。
+Braze が、顧客の現在のサブスクリプション契約期間中に、Braze サービスにおいて新規または更新されたメカニズムを一般利用可能とした場合、顧客は、新規メカニズムの一般リリース日から6ヶ月後または顧客のサブスクリプション契約期間の当年度末のいずれか遅い時点において、指定されたサードパーティプラットフォームを通じてメッセージ送信をトリガーするために Webhook を使用することを禁止されるものとします。
 
 ## 免責事項
 
-Brazeは、お客様がWebhookを使用してメッセージの送信またはBrazeサービス外のその他の行為をトリガーすることに関して、一切の責任を負わないものとする。
+Braze は、顧客が Webhook を使用してメッセージの送信または Brazeサービス外のその他のアクションをトリガーすることに関して、一切の責任を負いません。
 
 ## 一般用語
 
-本契約に基づく顧客の義務の一般性を制限することなく、また、疑義を回避するためにのみ、顧客は、本チャネルの使用に関連して、必要なすべての権利、同意及び権限を取得し、法的に適切なプライバシー通知を提供すること、並びに本チャネルを通じてメッセージを送信し、又は該当する場合にはこれを受信するために法的に必要なすべての同意及び権限を取得することについて、単独で責任を負うものとする。
+本契約に基づく顧客の義務の一般性を制限することなく、また、疑義を回避するためにのみ、顧客は、本チャネルの使用に関連して、必要なすべての権利、同意、承認を取得し、本チャネルの使用に関連して法的に適切なプライバシー通知を提供し、本チャネルを通じてメッセージを送信または該当する場合、受信するために法的に必要なすべての同意および承認を取得することについて、単独で責任を負うものとします。
diff --git a/_lang/ja/_hidden/compliance/whatsapp.md b/_lang/ja/_hidden/compliance/whatsapp.md
index 0e4812e5190..925cc199553 100644
--- a/_lang/ja/_hidden/compliance/whatsapp.md
+++ b/_lang/ja/_hidden/compliance/whatsapp.md
@@ -13,15 +13,15 @@ _改訂日:2024年3月1日_
 
 _（改訂日から有効。変更されることがあります）_
 
-顧客のWhatsAppチャネルの使用に関して、以下の追加条件が適用されます: 
+顧客による WhatsApp チャネルの使用に関連して、以下の追加条項が適用されます。 
 
-## 適用されるサードパーティプロバイダーの条件
-顧客は、Braze [WhatsAppセットアップ][1]ページに記載されているように、WhatsApp、LLCおよびそのグループ関連会社によって要求される条件を含む、WhatsAppチャネルに適用されるすべての前提条件、条件、およびポリシーを遵守するものとします。
+## 適用されるサードパーティプロバイダーの条項
+顧客は、Braze [WhatsApp 設定][1]ページに記載されているように、WhatsApp、LLC およびそのグループ関連会社によって要求される条件を含め、WhatsApp チャネルに適用されるすべての前提条件、条項、およびポリシーを遵守するものとします。
 
 ## Webhook 使用例外条件
-顧客は、顧客サポート目的（人間支援チャットの使用例および/またはチャットボットの使用例など）でない限り、WhatsAppチャネルを介してメッセージを送信するためにwebhookをトリガーすることはできません。 
+顧客は、WhatsApp チャネルを介したメッセージの送信をトリガーするために Webhook を使用することはできません。ただし、人間支援型チャットのユースケースやチャットボットのユースケースなど、カスタマーサポートを目的とする場合は除きます。 
 
 ## 一般条件
-疑義を避けるために、契約に基づく顧客の義務の一般性を制限することなく、顧客はこのチャネルの使用に関連して、すべての必要な権利、同意、および認可を取得し、法的に適切なプライバシー通知を提供し、このチャネルを通じてメッセージを送信または受信するために法的に必要なすべての同意および認可を取得する責任を単独で負うものとします。
+本契約に基づく顧客の義務の一般性を制限することなく、また、疑義を回避するため、顧客は、本チャネルの使用に関連して、必要なすべての権利、同意、承認を取得し、本チャネルの使用に関連して法的に適切なプライバシー通知を提供し、本チャネルを通じてメッセージを送信または該当する場合、受信するために法的に必要なすべての同意および承認を取得することについて、単独で責任を負うものとします。
 
 [1]: {{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/
\ No newline at end of file
diff --git a/_lang/ja/_hidden/misc_reference/regex_reference.md b/_lang/ja/_hidden/misc_reference/regex_reference.md
index baa90cfa2dd..eaed7660fac 100644
--- a/_lang/ja/_hidden/misc_reference/regex_reference.md
+++ b/_lang/ja/_hidden/misc_reference/regex_reference.md
@@ -1,10 +1,10 @@
 ---
-nav_title: 正規表現リファレンス・シート
+nav_title: 正規表現リファレンスシート
 permalink: /regex_cheat_sheet/
 hidden: true
 ---
 
-# 正規表現リファレンス・シート
+# 正規表現リファレンスシート
 
 このページは、一般的なトークン、メタ・シーケンス、一般的なトークン、グループ定数などを含む、正規表現のクイック・リファレンス・ガイドとして役立つ。
 
@@ -22,19 +22,19 @@ hidden: true
 | 任意の空白文字 | `\s` |
 | 空白以外の文字 | `\S` |
 | 任意の数字 | `\d` |
-| 数字以外 | `\D` |
+| 数字以外の任意の文字 | `\D` |
 | 任意の単語文字 | `\w` |
 | 単語以外の文字 | `\W` |
-| 同封のキャプチャー | `(...)` |
-| aまたはbのいずれかに一致する | `(a|b)` |
-| のいずれか1つである。 | `a?` |
+| 囲まれた部分をキャプチャーする | `(...)` |
+| a または b のいずれかににマッチする | `(a|b)` |
+| a が0または1つ | `a?` |
 | を0個以上含む。 | `a*` |
-| のうちの1つ以上である。 | `a+` |
-| のちょうど3つである。 | `a{3}` |
-| の3～6の間である。 | `a{3,6}` |
+| a が1つ以上 | `a+` |
+| a がちょうど3つ | `a{3}` |
+| a が3つ～6つの間 | `a{3,6}` |
 | 文字列の先頭 | `^` |
 | 文字列の最後 | `$` |
-| 言葉の境界 | `\n` |
+| 単語境界 | `\n` |
 | 非単語境界 | `\B` |
 {: .reset-td-br-1 .reset-td-br-2}
 {% endtab %}
@@ -46,29 +46,29 @@ hidden: true
 | 1つのデータ・ユニットに一致させる | `\C` |
 | ユニコード改行 | `\R` |
 | 縦の空白文字 | `\v` |
-| の否定 | `\V` |
+| \\v の否定 | `\V` |
 | 水平空白文字 | `\h` |
-| の否定 | `\H` |
-| リセットマッチ | `\K` |
+| \\h の否定 | `\H` |
+| マッチのリセット | `\K` |
 | n番目のサブパターンにマッチする | `\n` |
-| ユニコードのプロパティ X | `\pX` |
-| の否定 | `\PX` |
+| Unicode プロパティ X | `\pX` |
+| \\pX の否定 | `\PX` |
 | Unicodeプロパティまたはスクリプトカテゴリ | `\p{...}` |
-| の否定 | `\P{...}` |
-| 引用；リベラル扱い | `\Q...|E` |
+| \\p の否定 | `\P{...}` |
+| 引用；リベラルとして扱う | `\Q...|E` |
 | サブパターン'name'にマッチする | `\k<name>` | 
 | サブパターン'name'にマッチする | `\k'name'` | 
 | サブパターン'name'にマッチする | `\k{name}` |
 | n番目のサブパターンにマッチする | `\gn` | 
 | n番目のサブパターンにマッチする | `\g{n}` |
-| n番目のキャプチャグループを検索する | `\g<n>` |
-| n番目のキャプチャグループを検索する | `\g'n'` |
+| n番目のキャプチャグループを再帰する | `\g<n>` |
+| n番目のキャプチャグループを再帰する | `\g'n'` |
 | n番目の相対的な前のサブパターンにマッチする | `\g{-n}` |
-| n番目の相対的な次のサブパターンを検索する。 | `\g<+n>` |
-| n番目の相対的な次期送信者にマッチする | `\g'+n'` |
-| 再帰的名前捕捉グループ | `'letter'` |
+| n番目の相対的な次のサブパターンを再帰する | `\g<+n>` |
+| n番目の相対的な次の提出者にマッチする | `\g'+n'` |
+| 再帰的名前キャプチャグループ | `'letter'` |
 | 以前の名前のキャプチャーグループ「letter」と一致する。 | `\g{letter}` |
-| グループ'letter'をキャプチャする名前を再帰検索する | `\g<letter>` |
+| 名前付きキャプチャグループ「letter」を再帰する | `\g<letter>` |
 | ヘックス文字 YY | `\xYY` |
 | ヘックス文字 YYYY | `\x{YYYY}` |
 | 8進文字 ddd | `\ddd` |
@@ -88,9 +88,9 @@ hidden: true
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endtab %}
-{% tab キャラクターのクラス修正 %}
+{% tab 文字クラス修飾子 %}
 
-| キャラクターのクラス修正 |
+| 文字クラス修飾子 |
 | ------------------------- |
 | a、b、cのいずれか1文字 | `[abc]` |
 | a、b、c以外の文字 | `[^abc]` |
@@ -103,7 +103,7 @@ hidden: true
 | スペースまたはタブのみ | `[:blank:]` |
 | 制御文字 | `[:cntrl:]` |
 | 数字 | `[:digit:]` |
-| 目に見える文字（スペースではない） | `[:word:]` |
+| 表示文字 (スペース以外) | `[:word:]` |
 | 小文字 | `[:xdigit:]` |
 | 大文字 | `[:<:]` |
 | 単語文字 | `[:>:]` |
@@ -114,32 +114,32 @@ hidden: true
 | グループ定数 |
 | --------------- |
 | 同封されているものすべてをキャプチャする | `(...)` |
-| aまたはbのいずれかに一致する | `(a|b)` |
+| a または b のいずれかににマッチする | `(a|b)` |
 | 同封されているものをすべて揃える | `(?:...)` |
-| 原子グループ化（非捕捉） | `(?>...)` |
+| アトミックグルーピング (非キャプチャ) | `(?>...)` |
 | サブパターングループ番号が重複している | `(?|...)` |
 | コメント | `(?#...)` |
 | 大文字と小文字を区別しない | `(?i)` |
-| 名前付きキャプチャ・グループ | `(?'name'...)` |
-| 名前付きキャプチャ・グループ | `(?<name>...)` |
-| 名前付きキャプチャ・グループ | `(?P<name>...)` |
+| 名前付きキャプチャグループ | `(?'name'...)` |
+| 名前付きキャプチャグループ | `(?<name>...)` |
+| 名前付きキャプチャグループ | `(?P<name>...)` |
 | インライン修飾子 | `(?imsxXU)` |
 | 条件文 | `(?(1)yes|no)` |
 | 再帰的条件文 | `(?(R#)yes|no)` |
 | 条件文 | `(?(R&name)yes|no)` |
-| ルックアヘッド条件付き | `(?(?=...)yes|no)` |
-| ルックビハインド条件 | `(?(?<=...)yes|no)` |
-| パターン全体を検索する | `(?R)` |
+| 先読み条件 | `(?(?=...)yes|no)` |
+| 後読み条件 | `(?(?<=...)yes|no)` |
+| パターン全体を再帰する | `(?R)` |
 | 最初のサブパターンを再帰する | `(?1)` |
 | 最初の相対サブパターンを検索する | `(?+1)` |
-| サブパターン 'name' を再帰検索する | `(?&name)` |
+| サブパターン「name」を再帰する | `(?&name)` |
 | サブパターン 'name' にマッチする | `(?P=name)` |
-| サブパターン 'name' を再帰検索する | `(?P>name)` |
+| サブパターン「name」を再帰する | `(?P>name)` |
 | 使用前にパターンを定義しておく | `(?(DEFINE)...)` |
-| ポジティブな先読み | `(?=...)` |
-| ネガティブ・ルックアヘッド | `(?!...)` |
-| 前向きな後ろ姿 | `(?<=...)` |
-| ネガティブな後ろ姿 | `(?<!...)` |
+| 肯定的先読み | `(?=...)` |
+| 否定的先読み | `(?!...)` |
+| 肯定的後読み | `(?<=...)` |
+| 否定的後読み | `(?<!...)` |
 | 制御動詞 | `(*ACCEPT)` |
 | 制御動詞 | `(*FAIL)` |
 | 制御動詞 | `(*MARK:NAME)` |
@@ -166,33 +166,33 @@ hidden: true
 | 正規表現エンジン修飾子 | `(*NO_START_OPT)` |
 {: .reset-td-br-1 .reset-td-br-2}
 {% endtab %}
-{% tab 量記号 %}
+{% tab 量指定子 %}
 
-| 量記号 |
+| 量指定子 |
 | ----------- |
-| のいずれか1つである。 | `a?` |
+| a が0または1つ | `a?` |
 | を0個以上含む。 | `a*` |
-| のうちの1つ以上である。 | `a+` |
-| のちょうど3つである。 | `a{3}` |
+| a が1つ以上 | `a+` |
+| a がちょうど3つ | `a{3}` |
 | のうち3つ以上 | `a{3,}` |
-| の3～6の間である。 | `a{3,6}` |
-| 貪欲な量化子 | `a*` |
-| 怠惰な量化子 | `a*?` |
-| quanitiferを所有する。 | `a*+` |
+| a が3つ～6つの間 | `a{3,6}` |
+| 貪欲な量指定子 | `a*` |
+| 怠惰な量指定子 | `a*?` |
+| 所有量指定子 | `a*+` |
 {: .reset-td-br-1 .reset-td-br-2}
 {% endtab %}
 {% tab アンカー %}
 
 | アンカー |
 | ------- |
-| 試合開始 | `\G` |
+| マッチの開始 | `\G` |
 | 文字列の先頭 | `^` |
 | 文字列の最後 | `$` |
 | 文字列の先頭 | `\A` |
 | 文字列の最後 | `\Z` |
 | 文字列の絶対終端 | `\z` |
-| 言葉の境界 | `\b` |
-| 単語以外の境界 | `\B` |
+| 単語境界 | `\b` |
+| 非単語境界 | `\B` |
 {: .reset-td-br-1 .reset-td-br-2}
 {% endtab %}
 
@@ -204,22 +204,22 @@ hidden: true
 | マルチライン | `m` |
 | 大文字と小文字を区別する | `l` |
 | 空白を無視する | `x` |
-| シングルライン | `s` |
+| 単一行 | `s` |
 | ユニコード | `u` |
-| エクステンデッド | `X` |
+| 拡張 | `X` |
 | 欲がない | `U` |
 | アンカー | `A` |
-| グループ名の重複 | `J` |
+| 重複グループ名 | `J` |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endtab %}
-{% tab 代替 %}
+{% tab 置換 %}
 
 | 代替 |
 | ------------ |
-| 完全な試合内容 | `\0` |
-| キャプチャ・グループ1の内容 | `\1 or $1` |
-| キャプチャグループ内のコンテンツ `foo` | `${foo}` |
+| 完全マッチの内容 | `\0` |
+| キャプチャグループ1の内容 | `\1 or $1` |
+| キャプチャグループ`foo` 内のコンテンツ | `${foo}` |
 | 16進数の置換値 | `\x20, \x{06fa}` |
 | タブ | `\t` |
 | キャリッジリターン | `\r` |
diff --git a/_lang/ja/_hidden/misc_reference/scim_api_appendix.md b/_lang/ja/_hidden/misc_reference/scim_api_appendix.md
index 210e2db97aa..3f934ade74f 100644
--- a/_lang/ja/_hidden/misc_reference/scim_api_appendix.md
+++ b/_lang/ja/_hidden/misc_reference/scim_api_appendix.md
@@ -15,7 +15,7 @@ permalink: "/scim_api_appendix/"
 permissionsオブジェクトは、SCIM IDパーミッションを通してユーザーリソースとインターフェースするときに、リクエストとレスポンスの一部に見られるフィールドである。
 
 {% alert note %}
-Brazeでは、アプリグループはワークスペースに改名されたが、このページのキーはまだ古い用語を参照している（例えば、`appGroup` 、`appGroupName` ）。
+Braze では、アプリグループはワークスペースに改名されましたが、このページのキーはまだ古い用語を参照しています (例えば、`appGroup`、`appGroupName`)。
 {% endalert %}
 
 ```
@@ -31,21 +31,21 @@ Brazeでは、アプリグループはワークスペースに改名されたが
 
 | キー | required | データタイプ | 説明 |
 | --- | --- | --- | --- |
-| `companyPermissions` | オプション | 配列 | 文字列の存在は、対応するパーミッションを持つユーザーに対応する[。](#company) |
-| `appGroup` | required | 配列 | [ワークスペース許可オブジェクトの](#workspace-permission-object)配列。 |
+| `companyPermissions` | オプション | 配列 | [会社許可文字列](#company) テーブルからの会社レベルの許可文字列の配列。文字列の存在は、対応する許可を持つユーザに対応します。 |
+| `appGroup` | required | 配列 | [ワークスペース許可オブジェクト](#workspace-permission-object)の配列。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ### ワークスペース許可オブジェクト {#workspace-permission-object}
 
-有効なアプリグループ許可オブジェクトは、以下のキーと値のペアを持つJSONオブジェクトである：
+有効なアプリグループ許可オブジェクトは、以下のキーと値のペアを持つ JSON オブジェクトです。
 
 | キー | required | データタイプ | 説明 |
 | --- | --- | --- | --- |
 | `appGroupName`| オプション | string | ワークスペースの名前。このオブジェクトに含まれるパーミッションがどのワークスペースに対するものかを指定するために使用される。 | 
-| `appGroupId` | `appGroupName` がない場合は必須 | string | ワークスペースを指定する代替方法となる。 |
-| `appGroupPermissionSets` | オプション | 配列 | [ワークスペース権限セットオブジェクトを](#workspace-permissions-set-object)1つ持つ配列。 |
-| `appGroupPermissions` | required | 配列 | [ワークスペース・パーミッション文字列](#workspace-strings)テーブルのワークスペース・レベル・パーミッション文字列の配列で、文字列の存在は、指定されたワークスペースの対応するパーミッションを持つユーザーに対応する。 |
-| `team` | オプション | 配列 | [チーム権限オブジェクトの](#team-permissions-object)配列。 |
+| `appGroupId` | `appGroupName` がない場合は必須 | string | ワークスペースの ID。ワークスペースを指定する別の方法として機能します。 |
+| `appGroupPermissionSets` | オプション | 配列 | 単一の[ワークスペース許可セットオブジェクト](#workspace-permissions-set-object)を持つ配列。 |
+| `appGroupPermissions` | required | 配列 | [ワークスペース許可文字列](#workspace-strings)テーブルからのワークスペースレベルの許可文字列の配列。文字列の存在は、指定されたワークスペースに対する対応する許可を持つユーザーに対応します。 |
+| `team` | オプション | 配列 | [チーム許可オブジェクト](#team-permissions-object)の配列。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ### ワークスペース権限設定オブジェクト {#workspace-permissions-set-object}
@@ -55,7 +55,7 @@ Brazeでは、アプリグループはワークスペースに改名されたが
 | キー | required | データタイプ | 説明 |
 | --- | --- | --- | --- |
 | `appGroupPermissionSetName` | オプション | string | このワークスペースのユーザーに割り当てられているワークスペース権限セットの名前。 |
-| `appGroupPermissionSetID` | `appGroupPermissionSetName` がない場合は必須 | string | このワークスペースのユーザーに割り当てられているワークスペース権限セットを指定する代替方法として機能する。 |
+| `appGroupPermissionSetID` | `appGroupPermissionSetName` がない場合は必須 | string | ワークスペースの ID。このワークスペースに対してユーザーに割り当てられたワークスペース許可セットを指定する代替方法として機能します。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ### チーム許可オブジェクト
@@ -66,14 +66,14 @@ Brazeでは、アプリグループはワークスペースに改名されたが
 | --- | --- | --- | --- |
 | `teamName` | オプション | string | チーム名。このオブジェクト内のパーミッションがどのチームのものかを指定するために使用できる。 |
 | `teamId` | `teamName` がない場合は必須 | string | チームのIDで、チームを指定する代替方法となる。 |
-| `teamPermissions` | required | 配列 | この文字列が存在する場合、そのユーザーは指定された[チームの](#team)対応するパーミッションを持っていることになる。 |
+| `teamPermissions` | required | 配列 | [チーム許可文字列](#team) テーブルからのチームレベルの許可文字列の配列。文字列の存在は、指定されたチームに対する対応する許可を持つユーザーに対応します。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 付録
 
 ### 会社の許可文字列 {#company}
 
-| UIに表示されている | SCIM API 文字列 |
+| UI に表示 | SCIM API 文字列 |
 | --- | --- |
 | 管理者 | `admin` |
 | 会社の設定を管理できる | `manage_company_settings` |
@@ -97,15 +97,15 @@ Brazeでは、アプリグループはワークスペースに改名されたが
 | 利用データを見る | `view_usage_data` |
 | ユーザーデータのインポートと更新 | `import_update_user_data` |
 | 請求の詳細を見る | `view_billing_details` |
-| デブ・コンソールにアクセスする | `dev_console` |
-| コンテンツ・ブロックを立ち上げる | `launch_content_blocks` |
+| 開発コンソールにアクセス | `dev_console` |
+| コンテンツブロックを開始 | `launch_content_blocks` |
 | 外部統合を管理する | `manage_external_integrations` |
 | アプリを管理する | `manage_apps` |
-| チームを管理する | `manage_teams` |
+| チームを管理 | `manage_teams` |
 | イベント、属性、購入を管理する | `manage_events_attributes_purchases` |
 | タグを管理する | `manage_tags` |
-| Eメールの設定を管理する | `manage_email_settings` |
-| 購読グループを管理する | `manage_subscription_groups` |
+| メール設定を管理 | `manage_email_settings` |
+| サブスクリプショングループを管理 | `manage_subscription_groups` |
 | 承認設定を管理する | `manage_approval_settings` |
 | カタログ・ダッシュボードの権限を管理する | `manage_catalogs_dashboard_permission` |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -127,11 +127,11 @@ Brazeでは、アプリグループはワークスペースに改名されたが
 
 ### 部門の文字列
 
-| UIに表示されている | SCIM API 文字列 |
+| UI に表示 | SCIM API 文字列 |
 | --- | --- |
-| 代理店 / 第三者 | `agency` |
+| 代理店 / サードパーティ | `agency` |
 | BI / アナリティクス | `bi` |
-| Cスイート | `c_suite` |
+| 経営幹部 | `c_suite` |
 | エンジニアリング | `engineering` |
 | ファイナンス | `finance` |
 | マーケティング / 編集 | `marketing` |
diff --git a/_lang/ja/_hidden/misc_reference/x-in-y-behavior.md b/_lang/ja/_hidden/misc_reference/x-in-y-behavior.md
index eda88c659cf..a9650c75b96 100644
--- a/_lang/ja/_hidden/misc_reference/x-in-y-behavior.md
+++ b/_lang/ja/_hidden/misc_reference/x-in-y-behavior.md
@@ -7,12 +7,12 @@ permalink: /x-in-y-behavior/
 
 これらのフィルターの動作はほとんど変わらず、以下の特性によって定義される：
 
-- カレンダーの日数（午前0時で終了）を設定して実行する。
+- 暦日数 (午前0時で終了) を設定して実行します。
 - 「日」はUTCで定義されている。
-- 現在のUTCの日は "0 "と定義される。
+- 現在の UTC 日付は「0」と定義されます。
 
 {% details UTCの定義が "1 "から "0 "に変わったのはなぜか？ %}
-ローカルタイムゾーンのスケジューリングでは、ユーザーが24時間セグメント内に留まる必要がある。Y=1日の場合、キャンペーンやキャンバスの対象者を決定する際に、24時間未満のユーザー履歴を評価しているケースがあった。
+ローカルタイムゾーンのスケジューリングでは、ユーザーが24時間セグメント内に留まる必要がある。Y = 1日の場合、キャンペーンやキャンバスの対象者を決定する際に、24時間未満のユーザー履歴を評価しているケースがありました。
 
 この変更は、フィルタをより直感的なものにし、「1日以内」に送信するスケジュールオプションなど、他のカレンダー機能の動作との一貫性を高める。
 {% enddetails %}
@@ -21,16 +21,16 @@ permalink: /x-in-y-behavior/
 
 ## ユースケース
 
-4月16日午後9時から、以下のキャンペーンを実施する。オーディエンスのセグメンテーションは「過去3日間に2回以上購入した」である。
+以下のキャンペーンは4月16日午後9時に送信されます。オーディエンスのセグメンテーションは「過去3日間に2回以上購入した」です。
 
 ![キャンペーンスケジュール][1]
 
-4月16日午後9時（東部標準時）は4月17日午前1時（UTC）となる。
+東部標準時の4月16日午後9時は協定世界時の4月17日午前1時です。
 
 4月17日が「0日目」、4月16日が「1日目」、4月15日が「2日目」、4月14日が「3日目」となる。
 
-4月14日午前12時（UTC）から現在（4月17日午前1時（UTC））までの履歴である。
-これは、ユーザーの履歴の73時間を含むウィンドウに蓄積されることになる。
+協定世界時4月14日午前12時から現在時刻 (協定世界時4月17日午前1時) までの履歴。
+これは、ユーザー履歴の73時間を含むウィンドウに累積されます。
 
 ## カレンダー通り
 
@@ -44,26 +44,26 @@ permalink: /x-in-y-behavior/
 
 ### フリークエンシーキャップ
 
-`Frequency Capping` で "days "または "weeks "を選択すると、カレンダー・デーが使用される。
+暦日数は、`Frequency Capping` で「日」または「週」を選択した場合に使用されます。
 
-- `Every 1 day` は、ユーザーの現地時間における現在の暦日に上限を制限する（現地時間の深夜に終了する）。
-- `Every 2 days` は、上限をユーザーの現地時間における前および現在の暦日に制限する（現在の暦日の現地時間午前0時に終了する）。
+- `Every 1 day` では、キャップはユーザー現地時間の現在の暦日に制限されます (現地時間の午前0時に終了します)。
+- `Every 2 days` では、キャップはユーザーの現地時間の前日と現在の暦日に制限されます (現在の暦日の現地時間午前0時に終了します)。
 
 ### 会社と現地時間
 
-会社のタイムゾーンにおける現在のカレンダーの日が、日としてカウントされる`0` 。
+会社のタイムゾーンの現在の暦日は、日 `0` としてカウントされます。
 
-`Send in 1 Calendar days at 11:05 am company time` または`send in 1 Calendar days at 11:05 am local time` 、それぞれ会社のタイムゾーンまたはローカルのタイムゾーンで、現在のカレンダーの日に`1` 、次に来る会社時間の午前11時5分にメッセージをスケジュールする。
+`Send in 1 Calendar days at 11:05 am company time` または `send in 1 Calendar days at 11:05 am local time` は、それぞれ会社のタイムゾーンまたはローカルタイムゾーンの現在の暦日に `1` 日を追加し、次の会社時間の午前11時05分にメッセージをスケジュールします。
 
-会社時間または現地時間が太平洋時間の場合、ユーザーが4/13の8:00PTにキャンバスステップを入力すると、Brazeはこのキャンバスステップを4/14の11:05am PTにスケジュールする。
+会社時間または現地時間が太平洋時間の場合、ユーザーが太平洋時間4月13日の午後8時にキャンバスステップを入力すると、Braze はこのキャンバスステップを太平洋時間4月14日の午前11時5分にスケジュールします。
 
 ## 前へ X in Y フィルターの動作
 
-Brazeには「X in Yフィルター」と呼ばれるセグメンテーション・フィルターがある。これらのフィルターはそれぞれ、以下の特徴によって定義された同様の機能を持つ：
+Braze には「X in Y フィルター」と呼ばれるセグメンテーションフィルターの特定のカテゴリーがあります。これらのフィルターはそれぞれ、以下の特徴によって定義された同様の機能を持つ：
 
-- カレンダーの日数（午前0時で終了）を設定して実行する。
+- 暦日数 (午前0時で終了) を設定して実行します。
 - 「日」はUTCで定義されている。
-- 現在のUTCの日は "1 "と定義される。
+- 現在の UTC 日付は「0」と定義されます。
 
 
 
diff --git a/_lang/ja/_hidden/other/10dlc_application.md b/_lang/ja/_hidden/other/10dlc_application.md
index f524b34c731..c68fcfd2c7f 100644
--- a/_lang/ja/_hidden/other/10dlc_application.md
+++ b/_lang/ja/_hidden/other/10dlc_application.md
@@ -7,66 +7,66 @@ page_type: reference
 
 # 10DLCアプリケーションに必要な情報
 
-顧客がBrazeから10DLCの登録支援を購入する場合、顧客はBrazeと顧客の間の適用される契約に従って、以下のメールに記載されたすべての情報に対する回答をBrazeに提出する必要があります。
+Braze から購入する顧客は 10DLC の登録に関する支援を受けるために、顧客と Braze の間の適用契約に基づいて合意された、以下のメールで求められたすべての情報に対する回答を Braze に提出する必要があります。
 
 情報には、関連するスクリーンショットや添付ファイルを含めて、[smsapplications@braze.com](mailto:smsapplications@braze.com)に提出する必要があります。10DLCに関する質問がある場合は、[Braze SMS 10DLCガイド]({{site.baseurl}}/assets/pdf/SMS_10DLC_Guide.pdf)を参照するか、Brazeの顧客成功マネージャーにお問い合わせください。
 
 ## 会社情報 (10DLC)
 
-すべての米国のキャリアは、新しいキャンペーンの提出に以下の会社情報を必要とします。
+すべての米国のキャリアは、新しいキャンペーンの送信に以下の会社情報が必要です。
 
 
 | フィールド                                                         | オプション（該当する場合）                                       | 説明                                                  |
 |---------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------|
-| 法的事業名                                           |                                                               | EINに登録されている正確な法的事業名を入力してください。（例えば、BrazeではなくBraze Inc.） |
-| ビジネスタイプ                                                 | {::nomarkdown}<ul><li>株式会社</li><li>協同組合</li><li>有限責任会社</li><li>非営利</li><li>パートナーシップ</li><li>個人事業</li></ul> {:/}|   |
+| 法定事業名称                                           |                                                               | EINに登録されている正確な法的事業名を入力してください。（例えば、BrazeではなくBraze Inc.） |
+| ビジネスタイプ                                                 | {::nomarkdown}<ul><li>株式会社</li><li>協同組合</li><li>有限責任会社</li><li>非営利</li><li>パートナーシップ</li><li>個人事業体</li></ul> {:/}|   |
 | 事業EIN / 税務ID番号                                  |                                                               | あなたのビジネスを識別するために使用される番号。   |
-| 事業登録IDタイプ                                 | {::nomarkdown}<ul><li>アメリカ合衆国:雇用者識別番号 (EIN)</li><li>カナダ：カナダ法人番号（CCN）</li><li>グレートブリテン：会社番号</li><li>オーストラリア：ASIC（ACN）からの会社番号</li><li>インド:法人番号</li><li>VAT番号</li><li>イスラエル:登録番号</li><li>その他</li></ul>{:/}  |                                                              |
+| 事業登録 ID タイプ                                 | {::nomarkdown}<ul><li>アメリカ合衆国:雇用者識別番号 (EIN)</li><li>カナダ：カナダ法人番号（CCN）</li><li>イギリス:会社番号</li><li>オーストラリア：ASIC による会社番号 (ACN)</li><li>インド:法人番号</li><li>VAT番号</li><li>イスラエル:登録番号</li><li>その他</li></ul>{:/}  |                                                              |
 | 事業登録IDタイプで「その他」を選択した場合、事業を識別するために使用する他の登録簿を指定してください。|                                                              | 
-| ビジネス業界                                             | {::nomarkdown}<ul><li>自動車</li><li>農業</li><li>銀行業務</li><li>消費者</li><li>教育</li><li>エレクトロニクス</li><li>エンジニアリング</li><li>エネルギー</li><li>ファストムービング消費者商品</li><li>金融</li><li>フィンテック</li><li>食品・飲料</li><li>政府</li><li>ヘルスケア</li><li>おもてなし</li><li>保険</li><li>宝石</li><li>合法</li><li>製造業</li><li>メディア</li><li>非営利</li><li>石油・ガス</li><li>オンライン</li><li>原材料</li><li>不動産</li><li>宗教</li><li>小売</li><li>テクノロジー</li><li>通信</li><li>交通</li><li>旅行</li></ul>{:/} | |
+| ビジネス業界                                             | {::nomarkdown}<ul><li>自動車</li><li>農業</li><li>銀行業務</li><li>消費者</li><li>教育</li><li>エレクトロニクス</li><li>エンジニアリング</li><li>エネルギー</li><li>日用消費財</li><li>金融</li><li>フィンテック</li><li>食品・飲料</li><li>政府</li><li>ヘルスケア</li><li>ホスピタリティ</li><li>保険</li><li>宝石</li><li>合法</li><li>製造業</li><li>メディア</li><li>非営利</li><li>石油・ガス</li><li>オンライン</li><li>原材料</li><li>不動産</li><li>宗教</li><li>小売</li><li>テクノロジー</li><li>通信</li><li>交通</li><li>旅行</li></ul>{:/} | |
 | Web サイト URL                                                   |                                                               | 提供されたWeb サイトは、登録されたブランドを反映し、アクセス可能である必要があります。 |
-| 事業運営地域（該当するものすべてを選択）        | {::nomarkdown}<ul><li>アフリカ</li><li>アジア</li><li>ヨーロッパ</li><li>ラテンアメリカ</li><li>アメリカ合衆国とカナダ</li></ul>{:/}    |    |
-| 完全な法的事業住所（通り、市区町村、州、郵便番号）        |                                                               | EINまたは登録リストに表示されているとおりに事業所の住所を入力してください。  |
+| 事業運営地域 (該当するものすべてを選択)        | {::nomarkdown}<ul><li>アフリカ</li><li>アジア</li><li>ヨーロッパ</li><li>ラテンアメリカ</li><li>アメリカ合衆国とカナダ</li></ul>{:/}    |    |
+| 正式な法人住所 (番地、市区町村、州、郵便番号)        |                                                               | EIN または登録リストに表示されているとおりに事業所の住所を入力してください。  |
 | 会社の種類                                                  | {::nomarkdown}<ul><li>プライベート</li><li>非営利</li><li>政府</li><li>パブリック</li></ul> {:/}  |     |
 | 公開されている場合は、ティッカーシンボルを提供してください                         |                                                               |                                                              |
-| 認定代表者 #1 - 名前                           |                                                               | Brazeは、ショートコードに関して発生する可能性のある問題の最初の連絡先となります。これは公開されている情報ではなく、キャリアがファイルに保管するためのものです（これと次のフィールドに適用されます）。 |
-| 承認された代表者 #1 - メール                          |                                                               |                                                              |
+| 認定代表者 #1 - 名前                           |                                                               | Brazeは、ショートコードに関して発生する可能性のある問題の最初の連絡先となります。これは公開されている情報ではなく、キャリアがファイルに保管するためのものです（これと次のフィールドに適用されます）。 |
+| 認定代表者 #1 - メール                          |                                                               |                                                              |
 | 認定代表者 #1 - 役職                 |                                                               |                                                              |
 | 認定代表者 #1 - 職位                   |                                                               |                                                              |
 | 認定代表者 #1 - 電話番号                   |                                                               |                                                              |
 | 任意の認定代表者 #2 - 名前                  |                                                               |                                                              |
-| オプションの認定代表者 #2 - メール                 |                                                               |                                                              |
+| 任意の認定代表者 #2 - メール                 |                                                               |                                                              |
 | 任意の認定代表者 #2 - 役職        |                                                               |                                                              |
 | 任意の認定代表者 #2 - 職位          |                                                               |                                                              |
-| オプションの認定代表者 #2 - 電話番号          |                                                               |                                                              |
-| 完全な法的事業住所（通り、市区町村、州、郵便番号）        |                                                               |                                                              |
-| 会社の種類（非公開、非営利、政府、公開（ティッカーシンボルを提供してください）） |                                       |                                                              |
+| 任意の認定代表者 #2 - 電話番号          |                                                               |                                                              |
+| 正式な法人住所 (番地、市区町村、州、郵便番号)        |                                                               |                                                              |
+| 会社のタイプ (民間、非営利、政府、公共 (ティッカーシンボルを入力してください)) |                                       |                                                              |
 | 公開されている場合は、ティッカーシンボルを提供してください                         |                                                               |                                                              |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## SMSキャンペーン情報
 
-各SMSサブスクリプショングループを、独自のA2P 10DLCキャンペーン（ユースケースと呼ばれることもあります）で登録する必要があります。以下の情報を、米国のロングコードを含む各SMSサブスクリプショングループごとに一度提供してください。	
+米国の長いコードを含む各 SMS サブスクリプショングループを、独自の A2P 10DLC キャンペーン (ユースケースと呼ばれることもあります) に登録する必要があります。以下の情報を、米国のロングコードを含む各SMSサブスクリプショングループごとに一度提供してください。	
 
 | フィールド | オプション（該当する場合） | 説明 |
 | ------ | ------------------------ | --------------- |
-| キャンペーンユースケース（最も適したものを選択） | {::nomarkdown}<ul><li>マーケティング</li><li>アカウント通知</li><li>配達通知</li><li>顧客ケア</li><li>セキュリティ警報</li><li>詐欺警告メッセージング</li><li>高等教育</li><li>混合</li><li>投票と投票</li><li>公共サービスのお知らせ</li></ul>{:/} | 注:サブスクリプショングループに「混合」ユースケースを使用する予定がある場合は、事前に重要な詳細について顧客成功マネージャーまたは顧客オンボーディングマネージャーに相談してください。 |
+| キャンペーンユースケース（最も適したものを選択） | {::nomarkdown}<ul><li>マーケティング</li><li>アカウント通知</li><li>配信通知</li><li>顧客ケア</li><li>セキュリティ警報</li><li>詐欺警告メッセージング</li><li>高等教育</li><li>混合</li><li>投票と投票</li><li>公共サービスのお知らせ</li></ul>{:/} | 注:サブスクリプショングループに「混合」ユースケースを使用する予定がある場合は、事前に重要な詳細についてカスタマーサクセスマネージャーまたは顧客オンボーディングマネージャーに相談してください。 |
 | キャンペーン名 | | {::nomarkdown}<p>SMSキャンペーン名は、メッセージング、利用規約、およびユーザーがプログラムにサインアップする場所のどこにでも一貫して表示する必要があります。</p><p>例:</p><ul><li>Braze マーキングアラート</li><li>Brazeアカウント通知</li><li>Braze カートリマインダー</li></ul>{:/} |
-| キャンペーンの説明 | | このキャンペーンは、特別オファー/クーポンやカートリマインダ通知を含むSMSを受信することを希望するユーザーに、マーケティングおよびプロモーションメッセージを送信します。 |
-| 顧客サポートメールアドレス | | エンドユーザーはヘルプとサポートのためにどこでメールで連絡できますか |
+| キャンペーンの説明 | | このキャンペーンでは、SMS の受信をオプトインしたユーザーに、特別オファー/クーポンやカートのリマインダー通知などのマーケティングおよびプロモーションメッセージを送信します。 |
+| 顧客サポートメールアドレス | | エンドユーザーがメール経由でヘルプやサポートを受けられる場所 |
 | 顧客サポート電話番号 | | エンドユーザーはどこで電話でサポートを受けることができますか |
-| SMS 利用規約 URL | | {::nomarkdown}<p>米国A2P 10DLC登録を完了するには、SMS利用規約ページに以下を含める必要があります:</p><ol><li>プログラム（ブランド）名</li><li>Web サイトおよびメッセージフローでの一貫した製品開示</li><li>メッセージの頻度（メッセージフローと一致）</li><li>「メッセージおよびデータ料金が適用される場合があります」という免責事項</li><li>HELP/STOPの指示または顧客ケアの連絡先情報</li></ol><p>このページが公開されていないか、必要な開示情報が欠けている場合、SMS利用規約の下書きと、公開予定日を含むライブウェブページが登録プロセスを完了するために必要です。</p>{:/} |
-| エンドユーザーはどのようにしてあなたのSMSキャンペーンにオプトインしますか？エンドユーザーがあなたのSMSプログラムにオプトインする方法、例えばエンドユーザーがあなたのSMSメッセージを受信するための同意を与える方法を共有してください。複数のオプトイン方法が使用されている場合、それらはすべてここにリストされている必要があります。 | | {::nomarkdown}<p>例:</p><ul><li>エンドユーザーは、XXXXXXXXXXにSTARTとテキストメッセージを送信することでオプトインします。</li><li>エンドユーザーは、Web サイトにアクセスして携帯番号を追加することでオプトインします。それから、SMSを受信することに同意するボックスをチェックします。</li><li>オプトイン方法がまだ有効でない場合。オプトイン方法のモックアップ/スクリーンショットを提供してください。</li></ul>{:/} |
-| オプトインキーワード | | {::nomarkdown}<p>エンドユーザーがこのキャンペーンからSMSを受信し始めるためにキーワードをテキストで送信できる場合、それらのキーワードを提供する必要があります。デフォルトでは、Brazeは次のキーワードを設定します:</p><ul><li>開始</li><li>アンストップ</li><li>はい</li></ul><p>キーワードを追加したい場合はお知らせください。</p> {:/} |
-| オプトイン確認メッセージ | | エンドユーザーにオプトインを確認するために送信される自動返信メッセージを提供する必要があります。オプトインの回答には、ブランド名、定期メッセージキャンペーンへのオプトイン登録の確認、ヘルプの取得方法、およびオプトアウトの方法に関する明確な説明を含める必要があります。（例：Brazeマーケティングアラートにご参加いただきありがとうございます！）メッセージの頻度は異なります。メッセージおよびデータ料金が適用される場合があります。返信 HELP はヘルプ、STOP はオプトアウト。 |
-| オプトアウトキーワード | | {::nomarkdown}<p>エンドユーザーは、このキャンペーンからのメッセージの受信を停止するためにキーワードをテキストで送信できる必要があります。デフォルトでは、Brazeは次のキーワードを設定します:</p><ul>  <li>止まれ</li><li>すべて停止</li><li>配信停止</li><li>キャンセル</li><li>終わり</li><li>終了</li></ul><p>キーワードを追加したい場合はお知らせください。</p>{:/} |
-| オプトアウトメッセージ | | エンドユーザーからオプトアウトキーワードを受け取ると、キャリアはオプトアウトリクエストの受領確認と、今後メッセージが送信されないことの確認を提供する自動生成された応答を期待します。また、これらのオプトアウトメッセージにはブランド名を含めることをお勧めします（例：Braze Marketing Alerts：すべてのメッセージの購読を解除しました。返信 HELP でヘルプを表示します。<br><br>320 文字の最大値|
+| SMS 利用規約 URL | | {::nomarkdown}<p>米国A2P 10DLC の登録を完了するには、SMS 規約ページに以下を含める必要があります:</p><ol><li>プログラム（ブランド）名</li><li>Web サイトおよびメッセージフローでの一貫した製品開示</li><li>メッセージの頻度（メッセージフローと一致）</li><li>「メッセージおよびデータ料金が適用される場合があります」という免責事項</li><li>HELP/STOP の指示または顧客ケアの連絡先情報</li></ol><p>このページが公開されていないか、必要な開示情報が欠けている場合、SMS利用規約の下書きと、公開予定日を含むライブウェブページが登録プロセスを完了するために必要です。</p>{:/} |
+| エンドユーザーはどのようにしてあなたのSMSキャンペーンにオプトインしますか？エンドユーザーが SMS メッセージの受信に同意する方法など、エンドユーザーが SMS プログラムにオプトインする方法を共有してください。複数のオプトイン方法が使用されている場合、それらはすべてここにリストされている必要があります。 | | {::nomarkdown}<p>例:</p><ul><li>エンドユーザーは、XXXXXXXXXX に「START」とテキストを送信することでオプトインします。</li><li>エンドユーザーは、Web サイトにアクセスして携帯番号を追加することでオプトインします。それから、SMSを受信することに同意するボックスをチェックします。</li><li>選択したオプトイン方式がまだ使用可能になっていない場合。オプトイン方法のモックアップ/スクリーンショットを提供してください。</li></ul>{:/} |
+| オプトインキーワード | | {::nomarkdown}<p>エンドユーザーがこのキャンペーンからSMSを受信し始めるためにキーワードをテキストで送信できる場合、それらのキーワードを提供する必要があります。デフォルトでは、Brazeは次のキーワードを設定します:</p><ul><li>開始</li><li>UNSTOP</li><li>はい</li></ul><p>キーワードを追加したい場合はお知らせください。</p> {:/} |
+| オプトイン確認メッセージ | | オプトインを確認するためにエンドユーザーに送信される自動応答メッセージを提供する必要があります。オプトインの回答には、ブランド名、定期メッセージキャンペーンへのオプトイン登録の確認、ヘルプの取得方法、およびオプトアウトの方法に関する明確な説明を含める必要があります。（例：Brazeマーケティングアラートにご参加いただきありがとうございます！）メッセージの頻度はさまざまです。メッセージおよびデータ料金が適用される場合があります。ヘルプを求める場合は「HELP」と返信し、オプトアウトするには「STOP」と返信します。 |
+| オプトアウトキーワード | | {::nomarkdown}<p>エンドユーザーは、このキャンペーンからのメッセージの受信を停止するためにキーワードをテキストで送信できる必要があります。デフォルトでは、Brazeは次のキーワードを設定します:</p><ul>  <li>STOP</li><li>STOPALL</li><li>UNSUBSCRIBE</li><li>キャンセル</li><li>終わり</li><li>終了</li></ul><p>キーワードを追加したい場合はお知らせください。</p>{:/} |
+| オプトアウトメッセージ | | エンドユーザーからオプトアウトキーワードを受け取ると、キャリアはオプトアウトリクエストの受領確認と、今後メッセージが送信されないことの確認を提供する自動生成された応答を期待します。また、これらのオプトアウトメッセージにはブランド名を含めることをお勧めします（例：Braze Marketing Alerts：すべてのメッセージの配信を停止しました。ヘルプの場合は HELP と返信します。)<br><br>最大320文字|
 | ヘルプキーワード | | エンドユーザーは、キーワードをテキストで送信してヘルプを受け取ることができる必要があります。デフォルトで、Brazeは次のキーワードを設定します: -HELP -INFO キーワードを追加したい場合はお知らせください。 |
-| ヘルプメッセージ | | エンドユーザーからオプトアウトキーワードを受け取ると、キャリアは自動生成された応答を期待します。これにはブランド名や追加のサポート連絡先情報が含まれる場合があります（例：Braze マーケティングアラート：）。助けが必要な場合は、555-555-555に電話してください。メッセージとデータの料金がかかる場合があります。メッセージの頻度は異なる場合があります。キャンセルするにはSTOPとテキストしてください。<br><br>320 文字の最大値|
-| サンプルメッセージ1の2 | | 顧客/ブランドの更新:こんにちは、顧客ブランドの更新へようこそ。www.customerwebsite.com で私たちの Web サイトをご覧ください。ヘルプが必要な場合はHELPと入力してください。オプトアウトするにはSTOPと入力してください。 |
-| サンプルメッセージ2の2 | | 顧客/ブランドの更新:月曜日まで全商品が20％オフになる最新のホリデーセールをチェックしてください。www.customerwebsite.com で私たちの Web サイトをご覧ください。ヘルプが必要な場合はHELPと入力してください。オプトアウトするにはSTOPと入力してください。 |
+| ヘルプメッセージ | | エンドユーザーからオプトアウトキーワードを受け取ると、キャリアは自動生成された応答を期待します。これにはブランド名や追加のサポート連絡先情報が含まれる場合があります（例：Braze マーケティングアラート：）。助けが必要な場合は、555-555-555に電話してください。メッセージとデータの料金がかかる場合があります。メッセージの頻度は異なる場合があります。キャンセルするにはSTOPとテキストしてください。<br><br>最大320文字|
+| サンプルメッセージ1/2 | | 顧客/ブランドの更新:こんにちは、顧客ブランドの更新へようこそ。www.customerwebsite.com で私たちの Web サイトをご覧ください。ヘルプが必要な場合はHELPと入力してください。オプトアウトするにはSTOPと入力してください。 |
+| サンプルメッセージ2/2 | | 顧客/ブランドの更新:月曜日まで全商品が20％オフになる最新のホリデーセールをチェックしてください。www.customerwebsite.com で私たちの Web サイトをご覧ください。ヘルプが必要な場合はHELPと入力してください。オプトアウトするにはSTOPと入力してください。 |
 | 推定日量 | | この特定のユースケース/サブスクリプショングループに対して、1日に送信されるメッセージの推定平均数を示してください。例えば、10,000。 |
-| アクションチェックリストの呼び出し | | {::nomarkdown}<p>行動喚起には次のものを含める必要があります：</p><ol><li>製品説明</li><li>メッセージ頻度開示</li><li>利用規約の完全なリンク</li><li>完全なプライバシーポリシーへのリンク</li><li>STOP キーワード instructions</li><li>HELP キーワード instructions</li><li>「メッセージおよびデータ料金」が適用される場合があります。</li></ol> {:/} |
-| アクションの例 | | ![アクションを含むすべての必要な詳細を含む例。]({{site.baseurl}}/assets/img_archive/10dlc_cta_example.png) |
+| コール・トゥ・アクションのチェックリスト | | {::nomarkdown}<p>行動喚起には次のものを含める必要があります：</p><ol><li>製品説明</li><li>メッセージ頻度開示</li><li>利用規約全文へのリンク</li><li>完全なプライバシーポリシーへのリンク</li><li>STOP キーワードの説明</li><li>HELP キーワードの説明</li><li>「メッセージおよびデータ料金」が適用される場合があります。</li></ol> {:/} |
+| アクションの例 | | ![必要な詳細情報をすべて含むコールトゥアクションの例。]({{site.baseurl}}/assets/img_archive/10dlc_cta_example.png) |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
diff --git a/_lang/ja/_hidden/other/airship_migration.md b/_lang/ja/_hidden/other/airship_migration.md
index e822fab2c8b..e5797207066 100644
--- a/_lang/ja/_hidden/other/airship_migration.md
+++ b/_lang/ja/_hidden/other/airship_migration.md
@@ -5,31 +5,31 @@ hidden: true
 page_type: reference
 ---
 
-# AirshipからBraze（iOS）へSDKを移行する
+# Airship から Braze (iOS) へ SDK を移行する
 
-> Brazeでは、全く新しいプラットフォームやSDKに移行するのは大変なことだと理解しているが、以下の移行ガイド、わかりやすいコードレベルの例、Brazeプラットフォームがもたらす印象的な機能セットがあれば、気にすることはないだろう。この記事では、Airshipの主要機能の多くに相当するBrazeと、移行を迅速、簡単、簡単にする "リッピング＆リプレース "SDKコードスニペットを紹介する。
+> Brazeでは、全く新しいプラットフォームやSDKに移行するのは大変なことだと理解しているが、以下の移行ガイド、わかりやすいコードレベルの例、Brazeプラットフォームがもたらす印象的な機能セットがあれば、気にすることはないだろう。この記事では、Airship の多くの主要機能に相当する Braze と、移行をすばやく、簡単に、手間をかけずに行うための "rip-and-replace" SDK コードスニペットについて紹介します。
 
-## コードを超えて
+## コードを超える
 ### トークン管理
 BrazeはアップルのiOS用デバイストークンを使用している。
 
-**| ブレイズの視点**<br>AirshipからBrazeへの移行プロセス（100%Brazeへのハードカットオーバーであろうと、50%Airship 50%Brazeといったきめ細かな移行であろうと）において、顧客がユーザーと継続的にコミュニケーション（プッシュ通知など）できるようにする。|
+| **Braze の観点:**<br>Airship から Braze への移行プロセスでは、顧客がユーザーと継続的に通信 (プッシュ通知など) できるようにします (100% Braze へのハードカットオーバーであろうと、50% Airship 50% Braze などのきめ細かい移行であろうと)。|
 {: .reset-td-br-1}
 
 #### プッシュトークンの移行
 
-[API経由でプッシュトークンを移行する]({{site.baseurl}}/help/help_articles/push/push_token_migration/#migration-via-api)必要がある。リンク先のドキュメントには、具体的な手順とペイロードの例が記載されているが、全体的な流れは以下の通りである：
+[API 経由でプッシュトークンを移行する]({{site.baseurl}}/help/help_articles/push/push_token_migration/#migration-via-api)必要があります。リンク先のドキュメントには、具体的な手順とペイロードの例が記載されているが、全体的な流れは以下の通りである：
 
-1. [`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)経由でトークンをインポートする。大規模なバッチ輸入については、プロセスを迅速化するためのリソースを用意している。詳細はCOMまたはSAに問い合わせること！
+1. [`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)経由でトークンをインポートする。大規模なバッチのインポートについては、プロセスを迅速化するために利用できるリソースがあります。詳細はCOMまたはSAに問い合わせること！
 2. トークンがすでにBrazeに存在する場合は無視され、そうでない場合は匿名プロファイルが生成される。
-3. プッシュ統合の品質保証を行う。[プッシュを設定する]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration/)手順が完了していることを確認する。
+3. プッシュ統合の品質保証を行う。[プッシュを設定する]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration/)手順が完了していることを確認します。
 
 ユーザープロファイルとプッシュトークンが別々の場所に保存されている場合は、プッシュトークンを匿名でインポートし、その後で既存のユーザープロファイルを移行することを推奨する。Braze iOS SDKが統合成功時にトークンの解決を処理するため、これらを一緒にマッピングする必要はない。
 
-- API経由でユーザーを移行することを推奨するが、静的なユーザーリストをインポートする必要がある場合は、CSV経由で行うことができる。push_token」オブジェクトはCSVで指定できないため、**プッシュトークンをCSV経由でインポートすることはできない**。インポート・テンプレートや、ダッシュボードへのデータ・インポートの詳細については、[CSVドキュメントを]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv)参照されたい。
+- API経由でユーザーを移行することを推奨するが、静的なユーザーリストをインポートする必要がある場合は、CSV経由で行うことができる。push_token」オブジェクトはCSVで指定できないため、**プッシュトークンをCSV経由でインポートすることはできない**。インポートテンプレートや、ダッシュボードへのデータのインポートの詳細については、[CSV ドキュメント]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv)を参照してください。
 
 {% alert note %}
-プッシュトークンは、Brazeのダッシュボードでは`subscribed` と表示されるかもしれないが、ユーザーがBraze SDKでセッションを開始すると、`opted-in` に変更される。
+プッシュトークンは、Braze のダッシュボードでは `subscribed` と表示される場合がありますが、ユーザーが Braze SDK でセッションを開始すると、`opted-in` に変わります。
 {% endalert %}
 
 #### 複数のプッシュ・トークン
@@ -37,53 +37,53 @@ BrazeはアップルのiOS用デバイストークンを使用している。
 Brazeでは、ユーザーは複数のプッシュトークン（各デバイスに1つずつ）を持つことができ、有効なプッシュトークンすべてをターゲットにすることで、複数のユーザーデバイスに通知を送ることができる。また、ユーザーの最新のデバイスにのみ送信するようにキャンペーンを設定することも可能である。
 
 ## キャンペーンの構成
-高いレベルで言えば、Brazeはカスタマー・エンゲージメントの分野では実にユニークなツールである。Brazeに移行したキャンペーンは、豊富なカスタマイズオプションと増え続ける機能セットにより、これらのツールの利点を活用するために再計画が必要になることがよくある。
+高いレベルで言えば、Brazeはカスタマー・エンゲージメントの分野では実にユニークなツールである。Braze に移行されたキャンペーンは、豊富なカスタマイズオプションと機能セットの拡大により、これらのツールの利点を活用するために再計画することでメリットが得られることが多く、キャンペーン計画フレームワーク (詳細についてはCOMまたはSAにお問い合わせください) はその目的に特化しています。
 
 ### 構成
 #### プッシュ通知
 Brazeはプッシュのために別々のチャンネルを必要とする（iOS用とAndroid用）。
 
-**| ブレイズの視点**<br>我々は、顧客が譲歩する代わりに、両方の世界のベストを得ることを可能にする。個々のチャネルをフルに活用できることで、マーケティング担当者はより柔軟になり、ユーザー・エクスペリエンスも向上する。これにより、各OSの最新機能を採用することができる。例えば、アンドロイドはiOSより先にリッチ通知をサポートしていた。|
+| **Braze の観点:**<br>お客様が譲歩することなく、両方の利点を享受できるようにします。個々のチャネルをフルに活用できることで、マーケティング担当者はより柔軟になり、ユーザー・エクスペリエンスも向上する。これにより、各OSの最新機能を採用することができる。例えば、アンドロイドはiOSより先にリッチ通知をサポートしていた。|
 {: .reset-td-br-1}
 
-Brazeは、Braze SDKがインストールされたアプリケーションをアップデートしていないユーザーにプッシュ通知を送信することができる。Brazeが有効なプッシュトークンを持っている場合、BrazeはBraze SDKなしでプッシュ通知を送信できる。プッシュメッセージ**分析は、Braze SDKを使用しないビルドでは利用できない**ことに注意することが重要である。
+Braze は、Braze SDK がインストールされたアプリケーションをアップデートしていないユーザーにプッシュ通知を送信することができます。Braze に有効なプッシュトークンがある場合、APN が残りを処理するため、Braze は Braze SDK なしでプッシュ通知を送信できます。プッシュメッセージ**分析は、Braze SDK を使用しないビルドでは利用できない**ことに注意することが重要です。
 
 ##### トークンを共有する
 
-Braze SDKへの移行プロセス中も継続する必要があるライフサイクル固有のキャンペーンの場合、Brazeが有効なプッシュトークンを受け取っていれば、ユーザーはBrazeとAirshipの両方から通知を受け取ることができる。
+Braze SDK への移行プロセス中も継続する必要があるライフサイクル固有のキャンペーンの場合、Braze が有効なプッシュトークンを受け取っていれば、ユーザーは Braze と Airship の両方から通知を受け取ることができます。
 
 #### メッセージセンター
-Airshipのメッセージセンター・キャンペーン機能を置き換えるには、プッシュ通知と[コンテンツ・カードで]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/)構成されるマルチチャンネル・キャンペーンを作成することをお勧めする。コンテンツ・カードをメッセージ・センター形式で使用する方法については、[iOSコンテンツ・カード導入ガイドを]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/implementation_guide/#content-cards-in-a-message-center)参照されたい。
+Airship のメッセージセンターキャンペーン機能を置き換えるには、プッシュ通知と[コンテンツカード]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/)で構成されるマルチチャネルキャンペーンを作成することをお勧めします。コンテンツカードをメッセージセンター形式で使用する方法については、[iOS コンテンツカード導入ガイド]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/implementation_guide/#content-cards-in-a-message-center)を参照してください。
 
 ### セグメンテーション
 Brazeは、顧客に豊かなユーザー体験を提供するために、複数の[セグメンテーション]({{site.baseurl}}/user_guide/engagement_tools/segments/)フィルターを提供している。
 
-**| ブレイズの視点**<br> Brazeのセグメントは完全に動的であるため、ユーザーは定義された条件の変化に応じてセグメントに入ったり出たりする。|
+| **Braze の観点**:<br> Brazeのセグメントは完全に動的であるため、ユーザーは定義された条件の変化に応じてセグメントに入ったり出たりする。|
 {: .reset-td-br-1}
 
 #### ユーザーセグメントの移行
 
-静的な飛行船セグメントをBrazeで直接再現するには、2つの選択肢がある：
+静的な Airship セグメントを Braze で直接再現するには、2つの選択肢があります。
 - **API経由でインポートする - カスタム属性を割り当てる**（推奨）<br>
-[`/users/track` 、エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)経由でユーザーをインポートし、インポートしたユーザーにカスタム属性を割り当てることを推奨する。例えば、`true` に設定されたカスタム属性`Segment_Group_1` を持つユーザーのセグメントを作成することができる。これらのユーザーを後でセグメント化するには、`Segment_Group_1` が`true` である全ユーザーの[セグメントを作成する。]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/)<br><br>
+[`/users/track`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)経由でユーザをインポートし、同時にそのインポートしたユーザーにカスタム属性を割り当てることをお勧めします。例えば、`true` に設定されたカスタム属性 `Segment_Group_1` をそれぞれ持つユーザーのセグメントを作成することができます。これらのユーザーを後でセグメント化するには、`Segment_Group_1` が`true` である全ユーザーの[セグメントを作成する。]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/)<br><br>
 - **CSVユーザーインポートに基づくフィルタリング**<br>
-Brazeには、特定のCSVインポートに含まれるユーザーをフィルタリングするオプションがある。このフィルタリングオプションは、エンゲージメントツールのターゲットユーザーのステップで、"filter users by`Updated/Imported via CSV`" の下にある。
+Braze には、特定の CSV インポートに含まれるユーザーを具体的にフィルターするオプションがあります。このフィルターオプションは、エンゲージメントツールのターゲットユーザーのステップの「ユーザーを `Updated/Imported via CSV` でフィルターする」の下にあります。
 ![CSVインポートフィルター][1]{: style="max-width:90%;border:0;"}
-CSVインポートでは、インポートされる各ユーザーに外部IDが必要であり、**匿名またはエイリアスのみのユーザーを持つセグメントはインポートできないことに**注意すること。インポート・テンプレートや、ダッシュボードへのデータ・インポートの詳細については、[CSVドキュメントを]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv)参照されたい。
+CSV インポートでは、インポートされる各ユーザーに外部 ID が必要であり、**匿名またはエイリアスのみのユーザーを持つセグメントはインポートできない**ことに注意してください。インポートテンプレートや、ダッシュボードへのデータのインポートの詳細については、[CSV ドキュメント]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv)を参照してください。
 
 ## SDKのコード・スニペットをリッピングして置き換える
-移行を簡略化するため、コード内に存在する以下のAirship SDKスニペットを強調表示し、それらを置き換えるために必要な対応するBraze SDKスニペットを提供する。まずは以下のトピックをご覧いただきたい：
+移行を簡単にするために、コード内に存在する次の Airship SDK スニペットを強調表示し、それらを置き換えるために必要な対応する Braze SDK スニペットを提供しています。まずは以下のトピックをご覧いただきたい：
 - [インストール](#installation)
 - [ユーザーIDの取得と設定](#userid)
-- [プッシュ通知を扱う](#pushnotifications)
+- [プッシュ通知を処理する](#pushnotifications)
 - [分析](#analytics)
 - [アプリ内メッセージを処理する](#iammessages)
-- [コンテンツ・カードとメッセージ・センター](#messagecenter)
+- [コンテンツカードとメッセージセンター](#messagecenter)
 
 ### インストール {#installation}
 {% tabs %}
 {% tab Swift %}
-**飛行船**
+**Airship**
 ```swift
 func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) {
 
@@ -121,7 +121,7 @@ func application(_ application: UIApplication, didFinishLaunchingWithOptions lau
 ```
 {% endtab %}
 {% tab Objective-C %}
-**飛行船**
+**Airship**
 ```objc
 - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
 
@@ -166,10 +166,10 @@ func application(_ application: UIApplication, didFinishLaunchingWithOptions lau
 {% endtab %}
 {% endtabs %}
 
-### ユーザーIDの取得と設定 {#userid}
+### ユーザー ID の取得と設定 {#userid}
 {% tabs %}
 {% tab Swift %}
-**飛行船**
+**Airship**
 ```swift
 extension AirshipManager {
   var userId: String? {
@@ -195,7 +195,7 @@ extension AppboyManager {
 ```
 {% endtab %}
 {% tab Objective-C %}
-**飛行船**
+**Airship**
 ```objc
 
 - (NSString *)userId {
@@ -219,10 +219,10 @@ extension AppboyManager {
 {% endtab %}
 {% endtabs %}
 
-### プッシュ通知を扱う {#pushnotifications}
+### プッシュ通知を処理する {#pushnotifications}
 {% tabs %}
 {% tab Swift %}
-**飛行船**
+**Airship**
 ```swift
 extension AirshipManager: UAPushNotificationDelegate {
   func receivedBackgroundNotification(_ notificationContent: UANotificationContent, completionHandler: @escaping (UIBackgroundFetchResult) -> Void) {
@@ -256,7 +256,7 @@ extension AppboyManager {
 ```
 {% endtab %}
 {% tab Objective-C %}
-**飛行船**
+**Airship**
 ```objc
 - (void)receivedBackgroundNotification:(UANotificationContent *)notificationContent completionHandler:(void (^)(UIBackgroundFetchResult))completionHandler {
   completionHandler(UIBackgroundFetchResultNoData);
@@ -299,7 +299,7 @@ didReceiveNotificationResponse:(UNNotificationResponse *)response
 ### 分析 {#analytics}
 {% tabs %}
 {% tab Swift %}
-**飛行船**
+**Airship**
 ```swift
 extension AirshipManager {
   func trackEvent(with name: String, value: NSDecimalNumber? = nil, eventProperties: [String: Any]? = nil) {
@@ -337,7 +337,7 @@ extension AppboyManager {
 ```
 {% endtab %}
 {% tab Objective-C %}
-**飛行船**
+**Airship**
 ```objc
 - (void)trackEventWith:(NSString *)name value:(NSDecimalNumber *)value eventProperties:(NSDictionary *)eventProperties {
   UACustomEvent *event = [[UACustomEvent alloc] init];
@@ -374,7 +374,7 @@ extension AppboyManager {
 ### アプリ内メッセージを処理する {#iammessages}
 {% tabs %}
 {% tab Swift %}
-**飛行船**
+**Airship**
 ```swift
 
 extension AirshipManager: UAInAppMessagingDelegate {
@@ -426,7 +426,7 @@ extension AppboyManager: ABKInAppMessageUIDelegate {
 ```
 {% endtab %}
 {% tab Objective-C %}
-**飛行船**
+**Airship**
 ```objc
 - (UAInAppMessage *)extendMessage:(UAInAppMessage *)message {
 
@@ -477,7 +477,7 @@ extension AppboyManager: ABKInAppMessageUIDelegate {
 ### コンテンツ・カードとメッセージ・センター {#messagecenter}
 {% tabs %}
 {% tab Swift %}
-**飛行船**
+**Airship**
 ```swift
 extension AirshipManager {
   func displayMessageCenter() {
@@ -506,7 +506,7 @@ extension AppboyManager {
 ```
 {% endtab %}
 {% tab Objective-C %}
-**飛行船**
+**Airship**
 ```objc
 - (void)displayMessageCenter {
   [UAMessageCenter shared].defaultUI.title = @"My Message Center";
diff --git a/_lang/ja/_hidden/other/core_endpoints.md b/_lang/ja/_hidden/other/core_endpoints.md
index 9b4d2477cd4..ac4ce12b5e1 100644
--- a/_lang/ja/_hidden/other/core_endpoints.md
+++ b/_lang/ja/_hidden/other/core_endpoints.md
@@ -1,5 +1,5 @@
 ---
-nav_title: コア・エンドポイント
+nav_title: コアエンドポイント
 permalink: "/core_endpoints/"
 hidden: true
 layout: dev_guide
@@ -7,7 +7,7 @@ layout: dev_guide
 
 # Braze Core APIエンドポイント
 
-BrazeのAPIコアエンドポイントは、Brazeアカウントのサービスレベルアグリーメント（SLA）に従って許容されるダウンタイムを持つBrazeのREST APIの特定のエンドポイントである。詳細については、SLAの文書を参照するか、アカウント・マネージャーに問い合わせること。 
+Braze の API コアエンドポイントは、Braze アカウントのサービスレベルアグリーメント (SLA) に従って許容されるダウンタイムを持つ Braze の REST API の特定のエンドポイントです。詳細については、SLA ドキュメントを参照するか、アカウントマネージャーに問い合わせてください。 
 
 核となるエンドポイントは以下の通りである：
 - [`/users/track`][1]
diff --git a/_lang/ja/_hidden/other/credit_ratios.md b/_lang/ja/_hidden/other/credit_ratios.md
index e4c7ef72caf..2cb6eeb1119 100644
--- a/_lang/ja/_hidden/other/credit_ratios.md
+++ b/_lang/ja/_hidden/other/credit_ratios.md
@@ -5,22 +5,22 @@ permalink: "/credits_whatsapp/"
 hidden: true
 ---
 
-# WhatsAppクレジット比率（機密）
+# WhatsApp クレジット比率 (機密)
 
 > **WhatsApp**は、双方向のメッセージングに焦点を当てたチャネルであり、個々のメッセージの数ではなく会話に基づいています。会話は、ビジネスとエンドユーザーの間の24時間のスレッドです。会話内の個々のメッセージの数は、クレジットの使用に影響しません。 
 
 {% alert note %}
-MetaがWhatsAppの価格設定やパッケージを変更した場合、Brazeは合理的な通知の後にクレジット比率をそれに応じて変更する権利を留保します。
+Meta が WhatsApp の価格設定やパッケージを変更した場合、Braze は合理的な通知の後にクレジット比率をそれに応じて変更する権利を留保します。
 {% endalert %}
 
-**認証会話**:企業がワンタイムパスコードでユーザーを認証できるようにし、ログインプロセスの複数のステップ（例えば、アカウントの確認、アカウントの回復、整合性のチャレンジ）で使用する可能性があります。 
-  - 認証の会話はケースバイケースでのみサポートされ、Braze は特定の SLA を保証できません。さらに、BrazeはPIN生成をサポートしていません。
+**認証の会話**:企業がワンタイムパスコードでユーザーを認証できるようにし、ログインプロセスの複数のステップ（例えば、アカウントの確認、アカウントの回復、整合性のチャレンジ）で使用する可能性があります。 
+  - 認証の会話はケースバイケースでのみサポートされ、Braze は特定の SLA を保証できません。また、Brazeは暗証番号の生成に対応していません。
 
-**マーケティング Conversations**:プロモーションやオファー、情報更新、または顧客が応答またはアクションを取るための招待を含めます。 
+**マーケティングの会話**:プロモーションやオファー、情報更新、または顧客が応答またはアクションを取るための招待が含まれます。 
 
-**サービス会話**:エンドユーザーがビジネスにメッセージを送信します。ビジネスがメッセージを返信すると、これにより24時間のウィンドウが開始されます。
+**サービスの会話**:エンドユーザーがビジネスにメッセージを送信します。企業が返信メッセージを送信すると、これにより24時間の期間が開始されます。
 
-**ユーティリティ会話**:進行中の取引に関する特定の合意されたリクエストまたは取引、または顧客への更新を促進し、購入後の通知や定期的な請求書を含みます。
+**ユーティリティの会話**:購入後の通知や定期的な請求明細書など、進行中の取引に関する顧客への特定の合意済みのリクエストまたは取引または更新を促進します。
 
 | 参考文献 | クレジット比率 |
 |------------|--------------|
@@ -31,41 +31,41 @@ MetaがWhatsAppの価格設定やパッケージを変更した場合、Brazeは
 | WhatsApp - ブラジル認証 | 8.5 |
 | WhatsApp - ブラジルマーケティング | 16.5 |
 | WhatsApp - ブラジルサービス | 8 |
-| WhatsApp - ブラジルユーティリティ | 2.1 |
+| WhatsApp - ブラジルのユーティリティ | 2.1 |
 | WhatsApp - チリ認証 | 14 |
 | WhatsApp - チリマーケティング | 23.5 |
 | WhatsApp - チリサービス | 12 |
-| WhatsApp - チリユーティリティ | 5.3 |
+| WhatsApp - チリのユーティリティ | 5.3 |
 | WhatsApp - コロンビア認証 | 2 |
 | WhatsApp - コロンビア マーケティング | 3.5 |
 | WhatsApp - コロンビアサービス | 1.5 |
-| WhatsApp - コロンビアユーティリティ | 0.1 |
+| WhatsApp - コロンビアのユーティリティ | 0.1 |
 | WhatsApp - エジプト認証 | 16.5 |
 | WhatsApp - エジプトマーケティング | 28.5 |
 | WhatsApp - エジプトサービス | 17 |
-| WhatsApp - エジプトユーティリティ | 1.4 |
+| WhatsApp - エジプトのユーティリティ | 1.4 |
 | WhatsApp - フランス認証 | 18.5 |
 | WhatsApp - フランス マーケティング | 38 |
 | WhatsApp - フランスサービス | 23 |
-| WhatsApp - フランスユーティリティ | 8 |
+| WhatsApp - フランスのユーティリティ | 8 |
 | WhatsApp - ドイツ認証 | 20.5 |
 | WhatsApp - ドイツ マーケティング | 36 |
 | WhatsApp - ドイツのサービス | 21.5 |
 | WhatsApp - ドイツのユーティリティ | 14.6 |
 | WhatsApp - インド認証 | 0.4 |
-| インド認証 - 国際 | 7.4 |
+| インド認証- 国際 | 7.4 |
 | WhatsApp - インドマーケティング | 2.5 |
 | WhatsApp - インドサービス | 1 |
-| WhatsApp - インドユーティリティ | 0.4 |
+| WhatsApp - インドのユーティリティ | 0.4 |
 | WhatsApp - インドネシア 認証 | 8 |
-| インドネシア 認証 - 国際 | 36.1 |
+| インドネシア認証- 国際 | 36.1 |
 | WhatsApp - インドネシア マーケティング | 11 |
 | WhatsApp - インドネシアサービス | 5 |
 | WhatsApp - インドネシアユーティリティ | 5.5 |
 | WhatsApp - イスラエル認証 | 4.5 |
 | WhatsApp - イスラエル マーケティング | 9.5 |
 | WhatsApp - イスラエルサービス | 5 |
-| WhatsApp - イスラエルユーティリティ | 1.4 |
+| WhatsApp - イスラエルのユーティリティ | 1.4 |
 | WhatsApp - イタリア認証 | 10 |
 | WhatsApp - イタリアマーケティング | 18.5 |
 | WhatsApp - イタリアサービス | 10 |
@@ -73,11 +73,11 @@ MetaがWhatsAppの価格設定やパッケージを変更した場合、Brazeは
 | WhatsApp - マレーシア認証 | 5 |
 | WhatsApp - マレーシア マーケティング | 23 |
 | WhatsApp - マレーシアサービス | 6 |
-| WhatsApp - マレーシアユーティリティ | 3.7 |
+| WhatsApp - マレーシアのユーティリティ | 3.7 |
 | WhatsApp - メキシコ認証 | 6.5 |
 | WhatsApp - メキシコ マーケティング | 11.5 |
 | WhatsApp - メキシコサービス | 3 |
-| WhatsApp - メキシコユーティリティ | 2.7 |
+| WhatsApp - メキシコのユーティリティ | 2.7 |
 | WhatsApp - オランダ認証 | 19 |
 | WhatsApp - オランダ マーケティング | 42.5 |
 | WhatsApp - オランダのサービス | 23.5 |
@@ -102,16 +102,16 @@ MetaがWhatsAppの価格設定やパッケージを変更した場合、Brazeは
 | WhatsApp - ペルー マーケティング | 18.5 |
 | WhatsApp - ペルーサービス | 5 |
 | WhatsApp - ペルー ユーティリティ | 5.3 |
-| WhatsApp - アフリカの残りの認証 | 4 |
+| WhatsApp - アフリカのその他諸国の認証 | 4 |
 | WhatsApp - アフリカの残りのマーケティング | 6 |
 | WhatsApp - アフリカ地域の残りのサービス | 9.5 |
 | WhatsApp - アフリカの残りのユーティリティ | 1.6 |
-| WhatsApp - アジア太平洋地域の残りの認証 | 11.5 |
+| WhatsApp - アジア太平洋地域のその他の地域の認証 | 11.5 |
 | WhatsApp - アジア太平洋地域の残りのマーケティング | 19.5 |
 | WhatsApp - アジア太平洋地域の残りのサービス | 6 |
 | WhatsApp - アジア太平洋地域の残りのユーティリティ | 4.2 |
 | WhatsApp - 中央および東ヨーロッパの残りの部分 認証 | 15 |
-| WhatsApp - 中央および東ヨーロッパの残りのマーケティング | 23 |
+| WhatsApp - 中東欧地域のその他諸国: マーケティング | 23 |
 | WhatsApp - 中央・東ヨーロッパの残りのサービス | 6.5 |
 | WhatsApp - 中央および東ヨーロッパの残りのユーティリティ | 9.4 |
 | WhatsApp - ラテンアメリカの残りの部分 認証 | 12 |
@@ -125,7 +125,7 @@ MetaがWhatsAppの価格設定やパッケージを変更した場合、Brazeは
 | WhatsApp - 西ヨーロッパの残りの部分 認証 | 10 |
 | WhatsApp - 西ヨーロッパの残りのマーケティング | 15.5 |
 | WhatsApp - 西ヨーロッパの残りのサービス | 10.5 |
-| WhatsApp - 西ヨーロッパの残りのユーティリティ | 8 |
+| WhatsApp - 西欧地域のその他諸国: ユーティリティ | 8 |
 | WhatsApp - ロシア認証 | 11.5 |
 | WhatsApp - ロシア マーケティング | 21.5 |
 | WhatsApp - ロシアサービス | 10.5 |
@@ -145,7 +145,7 @@ MetaがWhatsAppの価格設定やパッケージを変更した場合、Brazeは
 | WhatsApp - トルコ認証 | 2 |
 | WhatsApp - トルコ マーケティング | 3 |
 | WhatsApp - トルコサービス | 1 |
-| WhatsApp - トルコユーティリティ | 1.4 |
+| WhatsApp - トルコのユーティリティ | 1.4 |
 | WhatsApp - アラブ首長国連邦 認証 | 4.5 |
 | WhatsApp - アラブ首長国連邦 マーケティング | 9 |
 | WhatsApp - アラブ首長国連邦サービス | 5 |
@@ -153,28 +153,28 @@ MetaがWhatsAppの価格設定やパッケージを変更した場合、Brazeは
 | WhatsApp - イギリス 認証 | 9.5 |
 | WhatsApp - イギリス マーケティング | 18.5 |
 | WhatsApp - イギリス サービス | 10.5 |
-| WhatsApp - イギリス ユーティリティ | 5.8 |
+| WhatsApp - イギリスのユーティリティ | 5.8 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-## WhatsApp請求地域の内訳
+## WhatsApp 請求地域の内訳
 
-#### 北アメリカ
-アメリカ合衆国、カナダ
+#### 北米
+米国、カナダ
 
-#### アフリカの残りの部分
+#### その他のアフリカ
 アルジェリア、アンゴラ、ベナン、ボツワナ、ブルキナファソ、ブルンジ、カメルーン、チャド、コンゴ、エリトリア、エチオピア、ガボン、ガンビア、ガーナ、ギニアビサウ、コートジボワール、ケニア、レソト、リベリア、リビア、マダガスカル、マラウイ、マリ、モーリタニア、モロッコ、モザンビーク、ナミビア、ニジェール、ルワンダ、セネガル、シエラレオネ、ソマリア、南スーダン、スーダン、スワジランド、タンザニア、トーゴ、チュニジア、ウガンダ、ザンビア
 
-#### アジア太平洋地域の残りの部分
+#### その他のアジア太平洋地域
 アフガニスタン、オーストラリア、バングラデシュ、カンボジア、中国、香港、日本、ラオス、モンゴル、ネパール、ニュージーランド、パプアニューギニア、フィリピン、シンガポール、スリランカ、台湾、タジキスタン、タイ、トルクメニスタン、ウズベキスタン、ベトナム
 
 #### 中東欧地域のその他諸国
-アルバニア、アルメニア、アゼルバイジャン、ベラルーシ、ブルガリア、クロアチア、チェコ共和国、ジョージア、ギリシャ、ハンガリー、ラトビア、リトアニア、マケドニア、モルドバ、ポーランド、ルーマニア、セルビア、スロバキア、スロベニア、ウクライナ
+アルバニア、アルメニア、アゼルバイジャン、ベラルーシ、ブルガリア、クロアチア、チェコ、グルジア、ギリシャ、ハンガリー、ラトビア、リトアニア、マケドニア、モルドバ、ポーランド、ルーマニア、セルビア、スロバキア、スロベニア、ウクライナ
 
-#### ラテンアメリカの残りの地域
+#### その他のラテンアメリカ
 ボリビア、コスタリカ、ドミニカ共和国、エクアドル、エルサルバドル、グアテマラ、ハイチ、ホンジュラス、ジャマイカ、ニカラグア、パナマ、パラグアイ、プエルトリコ、ウルグアイ、ベネズエラ
 
-#### 中東の残りの部分
-バーレーン、イラク、ヨルダン、クウェート、レバノン、オマーン、カタール、イエメン
+#### その他の中東
+バハレーン、イラク、ヨルダン、クウェート、レバノン、オマーン、カタール、イエメン
 
 #### 西欧地域のその他諸国
 オーストリア、ベルギー、デンマーク、フィンランド、アイルランド、ノルウェー、ポルトガル、スウェーデン、スイス
diff --git a/_lang/ja/_hidden/other/devices_and_carriers.md b/_lang/ja/_hidden/other/devices_and_carriers.md
index 47a28af0941..5d1f16de853 100644
--- a/_lang/ja/_hidden/other/devices_and_carriers.md
+++ b/_lang/ja/_hidden/other/devices_and_carriers.md
@@ -1,13 +1,13 @@
 ---
-nav_title: デバイスとキャリア
-article_title: デバイスとキャリア
+nav_title: デバイス＆通信事業者
+article_title: デバイス＆通信事業者
 page_type: reference
 permalink: "/device_and_carriers/"
-description: "このリファレンス記事では、ダッシュボードのデバイスおよびキャリアページにどのような情報が表示されるかを説明します。"
+description: "このリファレンス記事では、ダッシュボードのデバイスおよび通信事業者のページで確認できる情報について説明します。"
 hidden: true
 ---
 
-# デバイスとキャリア
+# デバイス＆通信事業者
 
 <!--This article is hidden because it has been deprecated for most customers. Confirm with Reporting PM before fully removing.-->
 
diff --git a/_lang/ja/_hidden/other/documentation_request.md b/_lang/ja/_hidden/other/documentation_request.md
index 24a813c6f75..fe10ebe9f90 100644
--- a/_lang/ja/_hidden/other/documentation_request.md
+++ b/_lang/ja/_hidden/other/documentation_request.md
@@ -1,5 +1,5 @@
 ---
-nav_title: ドキュメントリクエスト
+nav_title: ドキュメントのリクエスト
 permalink: "/request/"
 hide_nav: true
 layout: basic
@@ -413,7 +413,7 @@ hide_toc: true
     });
   </script>
 
-<div id="braze_internal" ><i class="fa-solid fa-lock"></i> 内部 only.顧客と共有しないでください。</div>
+<div id="braze_internal" ><i class="fa-solid fa-lock"></i> 内部専用。顧客と共有しないでください。</div>
 <div class="container-fluid" id="main-container">
 
       <div id="doc_div">
diff --git a/_lang/ja/_hidden/other/dp-technical-assistance.md b/_lang/ja/_hidden/other/dp-technical-assistance.md
index e84fc92956a..2222d5337e4 100644
--- a/_lang/ja/_hidden/other/dp-technical-assistance.md
+++ b/_lang/ja/_hidden/other/dp-technical-assistance.md
@@ -16,7 +16,7 @@ Warning! Don't make any changes to this document without approval from the legal
 
 EUおよび英国の一般データ保護規則（「GDPR」）、カリフォルニア州消費者プライバシー法（「CCPA」）、医療保険の携行性と説明責任に関する法律（「HIPAA」）など、組織が個人データを使ってできることを規制するさまざまなデータ保護法（「データ保護法」）がある。あなたのビジネスに適用される可能性のある、国、州、業界特有のデータ保護法および規制は他にもある。
 
-これらのデータ保護法は、個人データに対する「プライバシーの権利」を個人に与えている。組織は、プライバシーの権利を行使する個人からの要請を受け、それに応える義務がある。Brazeプラットフォームは、これらのデータ保護法の下で要求される特定の行為を容易にする機能を提供することにより、これらのデータ保護法への準拠を支援することができる。本書は、プライバシー権要求を管理するためにこれらの機能を使用するための技術的な指示を提供する。どのデータ保護法があなたのビジネスに適用されるかを判断し、それを遵守して行動するのはあなた次第である。
+これらのデータ保護法は、個人データに対する「プライバシーの権利」を個人に与えている。組織は、プライバシーの権利を行使する個人からのリクエストを受け、それに応える義務があります。Braze プラットフォームは、これらのデータ保護法の下で要求される特定の行為を容易にする機能を提供することにより、お客様がこれらの法律を遵守するのを支援します。本ドキュメントでは、これらの機能を使用してプライバシー権に関するリクエストを管理するための技術的な手順について説明します。どのデータ保護法がお客様のビジネスに適用されるかを判断し、それを遵守して行動するのはお客様次第です。
 
 ## 法的免責事項
 
@@ -24,74 +24,74 @@ EUおよび英国の一般データ保護規則（「GDPR」）、カリフォ
 
 ## 用語
 
-本書の目的上、個人データへの言及は、個人情報または個人を特定できる情報（「個人データ」）への言及として理解される場合もある。簡略化のため、エンドユーザーの権利を扱う際には、一般的にGDPRの文言に依拠する。GDPRの文言は、他のデータ保護法で定義されている用語や概念と互換性があるか、密接に一致していることが多い。
+本ドキュメントの目的上、個人データへの言及は、個人情報または個人を特定できる情報 (「個人データ」) への言及として理解される場合もあります。簡略化のため、エンドユーザーの権利を扱う際には、一般的にGDPRの文言に依拠する。GDPR の文言は、他のデータ保護法で定義されている用語や概念と互換性があるか、密接に関連していることがよくあります。
 
 ## 基本
 
-ほとんどの個人情報保護法は、個人データの処理に関与する3つの主要な利害関係者（データ主体、データ管理者、データ処理者）を定義している。各グループは、個人データの使用に関して異なる権利と責任を有する：
+ほとんどのプライバシー法は、個人データの処理に関与する主な利害関係者として、データ主体、データ管理者、データ処理者の3つを定義しています。各グループは、個人データの使用に関して異なる権利と責任を有します。
 
 - データ主体とは、データ処理者またはデータ管理者によって個人データが処理される個人を指す。
-- データ管理者とは、個人データの処理の目的および手段を決定する主体をいう。
-- データ処理者とは、データ管理者に代わって、またデータ管理者の指示に従って個人データを処理する事業者である。
+- データ管理者とは、個人データの処理の目的および手段を決定する主体です。
+- データ処理者とは、データ管理者に代わって、データ管理者の指示に基づいて個人データを処理する主体です。
 
-ブレイズ・プラットフォームに関連して：
+Braze プラットフォームに関して:
 
-- データ主体は、例えば、お客様の顧客アプリケーションのエンドユーザー（e.g...、お客様の顧客/クライアント）またはBrazeプラットフォームのお客様のインスタンスのダッシュボードユーザーであるお客様の従業員である。
-- Brazeの顧客であるお客様は、データ主体の個人データをBrazeプラットフォーム内で収集し、処理する方法および理由を決定するデータ管理者である。
+- データ主体は、例えば、お客様の顧客のアプリケーションのエンドユーザー (e.g、お客様の顧客/クライアント) または Braze プラットフォームのインスタンスのダッシュボードユーザーであるお客様の従業員です。
+- Braze の顧客であるお客様は、データ主体の個人データを Braze プラットフォーム内で収集し、処理する方法および理由を決定するデータ管理者です。
 - Brazeは、お客様に代わり、お客様から受領した指示に従い、Brazeプラットフォームにおいて個人データを処理するデータ処理業者である。
 
 上記はGDPRの用語であるが、例えば、CCPAにおける同等の用語は以下の通りである：
 
-- データ主体の「消費者」である。
+- データ主体の「消費者」。
 - データ管理者の「企業」。
-- データ処理業者の「サービスプロバイダー」。
+- データ処理者の「サービスプロバイダー」。
 
 データ主体からの最も一般的なプライバシーの権利に関する要求に関する関連情報、およびBrazeプラットフォームの技術的機能を通じてそれらに対応する方法を以下に示す。
 
 ## 情報を得る権利
 
-知らされる権利には、通常、プライバシー通知を通じて「公正な処理に関する情報」を提供する義務が含まれる。これは、個人データの使用方法に関する透明性の必要性を強調するものである。
+知らされる権利には、通常、プライバシー通知を通じて「公正な処理に関する情報」を提供する義務が含まれる。これは、個人データの使用方法に関する透明性の必要性を強調しています。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
-ほとんどのデータ保護法は、個人データの使用方法に関する透明性の必要性を強調している。これはデータ管理者の責任であり、データ管理者は通常、自社の製品およびサービスのユーザーが容易にアクセスでき、Brazeによる処理をカバーするプライバシー通知を維持する。
+ほとんどのデータ保護法は、個人データの使用方法に関する透明性の必要性を強調しています。これはデータ管理者の責任であり、データ管理者は通常自社の製品やサービスのユーザーが容易にアクセスできるプライバシー通知を維持し、Braze によるデータ処理をカバーしています。
 
 ## アクセス権
 
-データ保護法に基づき、データ対象者は以下を取得する権利を有する：
+データ保護法に基づき、データ主体は以下を取得する権利を有します。
 
-- 個人データが処理されていることを確認すること、
+- 個人データが処理されていることの確認
 - 個人データへのアクセス
 - その他、適用されるデータ保護法の定める補足情報。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
-データ対象者のアクセス要求に応じて機械可読形式でBrazeから個人データを提供するために、お客様は、Brazeの[REST APIに](https://www.braze.com/docs/api/endpoints/export/#user-export)ユーザー識別子（Brazeに提供される`external_id` としてお客様により定義される）および/またはデバイス識別子を使用してAPIコールを行うことにより、エンドユーザープロファイルをエクスポートすることができる。
+データ主体のアクセス要求に応じて機械可読形式で Braze から個人データを提供するために、お客様は、ユーザー識別子 (Braze に提供される `external_id` としてお客様が定義する) および/またはデバイス識別子を使用して Braze の [REST API](https://www.braze.com/docs/api/endpoints/export/#user-export) に API コールを行うことにより、エンドユーザープロファイルをエクスポートできます。
 
 ## 訂正権
 
-個人は、個人データが不正確または不完全である場合、訂正を受ける権利を有する。当該個人データを第三者に開示した場合、可能であれば、当該第三者に訂正の必要性を通知することができる。
+個人は、個人データが不正確または不完全である場合、訂正を受ける権利を有する。当該個人データを第三者に開示した場合、可能であれば、その訂正について知らせる必要性を検討することをお勧めします。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
-データ主体が、お客様またはお客様の代理としてBrazeにより処理されている個人データ内の不正確な情報を修正するよう要求した場合、お客様は、Braze SDKまたはBraze[REST APIを](https://www.braze.com/docs/api/endpoints/user_data/#user-track-endpoint)使用して、かかる個人データを修正することができる。
+データ主体が、お客様またはお客様の代理として Braze により処理されている個人データ内の不正確な情報を修正するよう要求した場合、お客様は、Braze SDK または Braze [REST API](https://www.braze.com/docs/api/endpoints/user_data/#user-track-endpoint) を使用して、かかる個人データを修正することができます。
 
 ## 消去権
 
 消去権は「忘れられる権利」または「削除される権利」とも呼ばれる。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
 #### 標準的な削除 
 
 データ収集を停止した後は、[Brazeのユーザー削除REST APIエンドポイントを](https://www.braze.com/docs/api/endpoints/user_data/post_user_delete/)使用してエンドユーザーを削除することができ、これによりBrazeのサービスから当該エンドユーザーのすべての記録が削除される：
 
 - サービス内にexternal_idを持つエンドユーザーについては、そのIDを使用してエンドユーザーのデータを削除できる。
-- サービス内にexternal_idを持たない匿名のエンドユーザーについては、Braze SDKを使用してエンドユーザーのデバイス識別子を取得し、デバイス識別子を使用してそのデバイスに関連付けられたエンドユーザープロファイルを検索することができる。その後、User Deletion APIを使用して、そのエンドユーザーに関連付けられているプロファイルを削除することができる。
+- サービス内に external_id を持たない匿名のエンドユーザーについては、Braze SDK を使用してエンドユーザーのデバイス識別子を取得し、そのデバイス識別子を使用してそのデバイスに関連付けられたエンドユーザープロファイルを検索できます。その後、ユーザー削除 API を使用して、そのエンドユーザーに関連付けられているプロファイルを削除できます。
 
-Brazeサービスからエンドユーザーを削除すると、提供された`external_id` によって定義されたそのエンドユーザーのBrazeの集中管理されたユーザープロファイルが永久に削除される。これには、Brazeがデフォルトで収集した、またはお客様がBrazeサービスが収集するように設定した構造化プロファイル情報（デバイス情報、国、言語、電子メールアドレスなど）が含まれる。
+Braze サービスからエンドユーザーを削除すると、提供された `external_id` によって定義されたそのエンドユーザーの Braze の集中管理されたユーザープロファイルが永久に削除されます。これには、Brazeがデフォルトで収集した、またはお客様がBrazeサービスが収集するように設定した構造化プロファイル情報（デバイス情報、国、言語、電子メールアドレスなど）が含まれる。
 
-エンドユーザーのプロフィールに関連付けられた電子メールアドレスや電話番号は、別のエンドユーザーのプロフィールに関連付けられる可能性があるため、Brazeによって依然として保存される可能性があることに留意されたい。電子メールアドレスおよび電話番号は、Brazeサービスにおいて一意ではない。つまり、あなたのチームは、複数のユーザープロファイルに同じメールアドレスや電話番号を保存するようにBrazeを設定した可能性がある。あなたのチームがこの方法でBrazeを構成した場合、データ対象者からの削除要求に従うために、特定のデータ対象者を表すすべてのユーザープロファイルを削除する必要がある可能性があり、あなたのチームは、特定のデータ対象者を参照するすべてのユーザープロファイルを削除するために複数のAPIコールを行う必要があることに注意する。
+エンドユーザーのプロフィールに関連付けられた電子メールアドレスや電話番号は、別のエンドユーザーのプロフィールに関連付けられる可能性があるため、Brazeによって依然として保存される可能性があることに留意されたい。電子メールアドレスおよび電話番号は、Brazeサービスにおいて一意ではない。つまり、あなたのチームは、複数のユーザープロファイルに同じメールアドレスや電話番号を保存するようにBrazeを設定した可能性がある。お客様のチームがこの方法で Braze を構成した場合、データ主体からの削除要求に従うために、特定のデータ主体を表すすべてのユーザープロファイルを削除する必要がある可能性があり、お客様のチームは、特定のデータ主体を参照するすべてのユーザープロファイルを削除するために複数の API コールを行う必要があることに注意してください。
 
 #### その他の削除に関する考慮事項
 
@@ -107,12 +107,12 @@ Brazeサービスからエンドユーザーを削除すると、提供された
 <tbody>
   <tr>
     <td>
-        <p>顧客は、イベント・プロパティとメッセージ・エクストラのカスタム・フィールドを作成できる。これらのフィールドは個人データ用ではないため、上記のデフォルト削除プロセスには含まれない。ただし、Brazeを使用して、イベントプロパティやメッセージエクストラを通じて個人データを入力または収集する場合は、User Deletion REST APIエンドポイントによってトリガーされる削除処理にこれらのフィールドも含めるように設定できるため、これらのフィールドに含まれるデータも削除される。</p>
+        <p>顧客は、イベントプロパティとメッセージエクストラのカスタムフィールドを作成できます。これらのフィールドは個人データ用ではないため、これらのフィールドは上記のデフォルトの削除プロセスには含まれません。ただし、Braze を使用して、イベントプロパティやメッセージエクストラを通じて個人データを入力または収集する場合は、ユーザー削除 REST API エンドポイントによってトリガーされる削除処理にこれらのフィールドも含めるように設定できるため、これらのフィールドに含まれるデータも削除されます。</p>
         <p>デフォルト設定は会社レベルで適用されるが、アプリグループ/ワークスペースレベルで、削除処理の実行時に以下のフィールドを削除することを選択できる：</p>
     <ul>
         <li>USERS_BEHAVIORS_CUSTOMEVENTのプロパティ</li>
         <li>USERS_BEHAVIORS_PURCHASE用プロパティ</li>
-        <li>に対するMESSAGE_EXTRASである：</li>
+        <li>以下に対する MESSAGE_EXTRAS</li>
             <ul>
             <li>USERS_MESSAGES_CONTENTCARD</li>
             <li>USERS_MESSAGES_EMAIL_SEND</li>
@@ -123,8 +123,8 @@ Brazeサービスからエンドユーザーを削除すると、提供された
             <li>将来のメッセージ送信イベント</li>
             </ul>
     </ul>
-    <p>この設定は、<b>「会社設定」</b>>「<b>管理者設定</b>」>「<b>セキュリティ設定</b>」からアクセスできる。データの削除設定は、イベントの種類やカテゴリーごとに設定される。これらの設定を変更できるのは、管理者権限を持つユーザーだけである。あるいは、管理者はこれらの権限を他のユーザーに委譲することもできる。</p>
-    <p>イベント・タイプまたはメッセージ・エクストラが削除プロセスに含まれるように設定されている場合、このフィールドのデータは、ユーザ削除REST APIエンドポイントを実行しているユーザに対して今後削除される。さらに、この削除設定を選択すると、次に予定されている削除ジョブで、これらのフィールドのデータが、これらのフィールドを含む既存の匿名化データセットから削除される。削除されたデータフィールドを復元することはできない。</p>
+    <p>この設定は、<b>「会社設定」</b>>「<b>管理者設定</b>」>「<b>セキュリティ設定</b>」からアクセスできる。データの削除設定は、イベントの種類やカテゴリーごとに設定される。これらの設定を変更できるのは、管理者権限を持つユーザーだけです。あるいは、管理者はこれらの権限を他のユーザーに委譲することもできる。</p>
+    <p>イベントタイプまたはメッセージエクストラが削除プロセスに含まれるように設定されている場合、このフィールドのデータは、ユーザ削除 REST API エンドポイントを実行しているユーザに対して今後削除されます。さらに、この削除設定を選択すると、次に予定されている削除ジョブで、これらのフィールドのデータが、これらのフィールドを含む既存の匿名化データセットから削除される。削除されたデータフィールドを復元することはできない。</p>
     </td>
   </tr>
 </tbody>
@@ -132,66 +132,66 @@ Brazeサービスからエンドユーザーを削除すると、提供された
 
 #### 分析
 
-キャンペーンおよびアプリケーションの利用分析の完全性を維持するため、匿名の集計データは、エンドユーザーが削除されても変更されない。例えば、エンドユーザーが削除されても、Brazeはアプリの総セッション数を減らさない。そのようなエンドユーザーがアプリを訪問したときのセッションは、そのアプリの総訪問回数には含まれるが、そのデータは、忘れられたエンドユーザーのプロファイルには一切関連付けられないため、この匿名化され集計されたデータを個々のエンドユーザーに結びつけることはできない。
+キャンペーンおよびアプリケーションの利用分析の完全性を維持するため、匿名の集計データは、エンドユーザーが削除されても変更されません。例えば、エンドユーザーが削除されても、Brazeはアプリの総セッション数を減らさない。そのようなエンドユーザーがアプリを訪問したときのセッションは、そのアプリの総訪問回数には含まれますが、そのデータは、忘れられたエンドユーザーのプロファイルには一切関連付けられないため、この匿名化され集計されたデータを個々のエンドユーザーに結びつけることはできません。
 
-Brazeサービス内の分析は、Brazeのエンドユーザー識別子に関連付けられる。エンドユーザーのプロフィールが削除された後、Brazeユーザー識別子は、Brazeがそれを個々のエンドユーザーに結びつけることができないため、事実上、完全に匿名化された識別子になる。
+Braze サービス内の分析は、Braze エンドユーザー識別子に関連付けられます。エンドユーザーのプロフィールが削除された後、Brazeユーザー識別子は、Brazeがそれを個々のエンドユーザーに結びつけることができないため、事実上、完全に匿名化された識別子になる。
 
 #### 削除が完了したら
 
-一般的に、データ対象者の個人データ消去要求に応じた場合、データ対象者に通知するための合理的な努力をすることが求められる。削除されたエンドユーザーは、後日、貴社のアプリまたはサービスに再登録または再参加する可能性があり、Brazeは、削除されたユーザーまたは忘れられたユーザーとして特定することはできない。Brazeサービスは、お客様に代わって削除されたユーザー識別子または電子メールアドレスのリストを作成することはできない。
+一般的に、データ主体による個人データ消去要求に応じた場合、データ主体に通知するための合理的な努力をすることが求めらます。削除されたエンドユーザーは、後日、貴社のアプリまたはサービスに再登録または再参加する可能性があり、Brazeは、削除されたユーザーまたは忘れられたユーザーとして特定することはできない。Brazeサービスは、お客様に代わって削除されたユーザー識別子または電子メールアドレスのリストを作成することはできない。
 
 ## 処理制限の権利
 
-データ対象者は、特定の状況において、自己の個人データの処理を「ブロック」または抑制する権利を有する場合がある。処理の制限とは、データ主体が異議を唱えた処理を実行しないことを意味する。
+データ主体は、特定の状況において、自己の個人データの処理を「ブロック」または抑制する権利を有する場合があります。処理の制限とは、データ主体が異議を唱えた処理を実行しないことを意味します。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
-Brazeサービスは、個人データの個別カテゴリーの処理制限に対応していない。データ対象者から、そのデータ対象者の個人データの特定のサブセットの処理を制限するよう要請された場合は、[Braze APIを](https://www.braze.com/docs/api/home/)使用して、そのエンドユーザーのプロファイル全体をエクスポートし、Brazeから[削除する](https://www.braze.com/docs/api/endpoints/user_data/#user-delete-endpoint)こと。BrazeのAPIは、エンドユーザーがその個人データの特定のサブセットを処理することを許可した場合に、このデータを再インポートするために使用することができる。さらに、データ対象者に関する追加データの収集を停止するため、エンドユーザーに対し、Braze SDKを使用するアプリケーションのすべてからアンインストールまたはログアウトするよう推奨すること。
+Brazeサービスは、個人データの個別カテゴリーの処理制限に対応していない。データ主体から、そのデータ主体の個人データの特定のサブセットの処理を制限するよう要請された場合は、[Braze API](https://www.braze.com/docs/api/home/) を使用して、そのエンドユーザーのプロファイル全体をエクスポートし、Braze から[削除](https://www.braze.com/docs/api/endpoints/user_data/#user-delete-endpoint)しなければなりません。Braze の API は、後でエンドユーザーがその個人データの特定のサブセットを処理することを許可した場合に、そのデータを再インポートするために使用することができます。さらに、データ主体に関する追加データの収集を停止するため、エンドユーザーに対しBraze SDK を使用するアプリケーションのすべてをアンインストールするかログアウトするように推奨する必要があります。
 
-## データ・ポータビリティの権利
+## データポータビリティの権利
 
-データ・ポータビリティの権利により、データ対象者は、異なるサービス間で自己の個人データを入手し、自己の目的のために再利用することができる。個人データは、構造化され、機械で読み取り可能で、一般的に使用される形式で提供されなければならない。
+データポータビリティの権利により、データ主体は、異なるサービス間で自己の個人データを入手し、自己の目的のために再利用することができます。個人データは、構造化され、機械で読み取り可能で、一般的に使用される形式で提供されなければなりません。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
-アクセス権と同様に、Braze[REST APIを](https://www.braze.com/docs/api/endpoints/export/#user-export)使用してエンドユーザーの個人データをエクスポートし、データ主体の要求に従ってデータ主体に提供することができる。
+アクセス権と同様に、Braze [REST API](https://www.braze.com/docs/api/endpoints/export/#user-export) を使用してエンドユーザーの個人データをエクスポートし、データ主体の要求に従ってデータ主体に提供することができます。
 
 ## 異議申し立ての権利
 
-個人は異議申し立ての権利を有する：
+個人は以下のに対する異議申し立ての権利を有します。
 
 - 正当な利益に基づく処理、または公益のための業務の遂行/公的権限の行使（プロファイリングを含む）；
 - ダイレクトマーケティング（プロファイリングを含む
 - 科学的/歴史的研究および統計の目的で処理すること。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
-Brazeは、[REST APIと](https://www.braze.com/docs/api/home/) [iOS](https://www.braze.com/docs/developer_guide/platform_integration_guides/ios/analytics/setting_custom_attributes/)、[Android](https://www.braze.com/docs/developer_guide/platform_integration_guides/android/analytics/setting_custom_attributes/)、および[Web](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/analytics/setting_custom_attributes/)SDKの両方を介して、SMS、電子メール、またはプッシュ通知からユーザープロファイルを配信停止としてマークする機能を提供する。このようなメッセージの受信についてデータ対象者から異議申し立てを受けた場合、BrazeのAPIを使用して、これらのエンドユーザーの配信を停止することができる。
+Brazeは、[REST APIと](https://www.braze.com/docs/api/home/) [iOS](https://www.braze.com/docs/developer_guide/platform_integration_guides/ios/analytics/setting_custom_attributes/)、[Android](https://www.braze.com/docs/developer_guide/platform_integration_guides/android/analytics/setting_custom_attributes/)、および[Web](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/analytics/setting_custom_attributes/)SDKの両方を介して、SMS、電子メール、またはプッシュ通知からユーザープロファイルを配信停止としてマークする機能を提供する。このようなメッセージの受信についてデータ主体から異議申し立てを受けた場合、Braze API を使用して、これらのエンドユーザーへの配信を停止することができます。
 
-それでも十分でない場合、Brazeによるエンドユーザー個人データの処理を回避するために、「消去権」で規定されているのと同じ方法でエンドユーザープロフィールを削除する必要がある。
+それでも十分でない場合、Braze によるエンドユーザーの個人データの処理を回避するため、「消去する権利」に規定されているのと同じ方法でエンドユーザーのプロファイルを削除する必要があります。
 
 ## 自動意思決定およびプロファイリングに関する権利
 
-データ保護法の中には、特定の状況、特に「法的効果または同様の重要な影響を個人に及ぼす」決定について、自動的な意思決定やプロファイリングを防止する、またはデータ主体がオプトアウトすることを認めているものがある。
+一部のデータ保護法の中には、特定の状況、特に「個人に法的効果又は同様の重大な効果をもたらす」意思決定について、自動化された意思決定又はプロファイリングを防止するか、データ主体がオプトアウトすることを認めているものがあります。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
-Brazeは、データ主体に対して法的または同等の影響を及ぼす自動化されたプロファイリングまたは意思決定行為を行わない。お客様は、お客様自身のBraze Platformの利用が法的またはこれに準ずる影響を及ぼすと考え、これに対する異議申し立てを受けた場合、"消去権 "と同様の方法でユーザープロフィールの削除を選択することができる。
+Braze は、データ主体に法的または同等の影響を及ぼす自動プロファイリングまたは意思決定アクションを実行しません。お客様は、お客様自身のBraze Platformの利用が法的またはこれに準ずる影響を及ぼすと考え、これに対する異議申し立てを受けた場合、"消去権 "と同様の方法でユーザープロフィールの削除を選択することができる。
 
 ## ターゲティング広告
 
-米国の一部の州の個人情報保護法では、データ主体はターゲット広告の目的で個人データを使用することに反対することができる。
+米国の一部の州のプライバシー法では、データ主体は、ターゲット広告目的での個人データの使用に異議を唱えることができます。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
-データ主体に広告をターゲティングする目的でオーディエンスを構築する場合、ターゲティング広告に異議を唱えたデータ主体（例えば、CCPAに基づき「販売または共有しない」権利を行使したカリフォルニア州の消費者）が除外されていることを確認する必要がある。
+データ主体に広告をターゲティングする目的でオーディエンスを構築する場合、ターゲティング広告に異議を唱えたデータ主体 (例えば、CCPA に基づき「販売または共有しない」権利を行使したカリフォルニア州の消費者) が除外されていることを確認する必要があります。
 
-サードパーティプラットフォームと同期するオーディエンスを構築する方法の詳細については、[Audience syncを](https://www.braze.com/docs/partners/canvas_steps)参照のこと。
+サードパーティプラットフォームと同期するオーディエンスを構築する方法の詳細については、[オーディエンスの同期](https://www.braze.com/docs/partners/canvas_steps)を参照してください。
 
 ## 無差別の権利 
 
-データ対象者は、差別なくプライバシー権を行使する権利を有する。
+データ主体は、差別なくプライバシー権を行使する権利を有します。
 
-### ブレイズ推薦
+### Braze の推奨事項
 
-お客様は、Brazeサービスの使用において、プライバシー権を行使したデータ主体を差別しないようにしなければならない。例えば、プライバシーの権利を行使したデータ主体は、オーディエンスにセグメント化されるべきではなく、また差別的なターゲットにされるべきではない。
\ No newline at end of file
+顧客は、Braze のサービスの使用において、プライバシー権を行使したデータ主体を差別しないようにしなければならない。例えば、プライバシー権を行使したデータ主体が、オーディエンスにセグメント化されるべきではなく、また、その他の方法で、彼らを差別するような方法でターゲティングされるべきではないことを推奨します。
\ No newline at end of file
diff --git a/_lang/ja/_hidden/other/ephemeral_custom_events.md b/_lang/ja/_hidden/other/ephemeral_custom_events.md
index a672590f969..78d0c2eca12 100644
--- a/_lang/ja/_hidden/other/ephemeral_custom_events.md
+++ b/_lang/ja/_hidden/other/ephemeral_custom_events.md
@@ -5,11 +5,11 @@ hidden: true
 page_type: reference
 ---
 
-# エフェメラルのカスタムイベント
+# エフェメラルカスタムイベント
 
-- エフェメラルカスタムイベントには、購入イベントまたは開始セッションと終了セッション(Brazeドキュメントに記載)は含まれません。
-- Brazeは、SDKインプリメンテーションごとに最大12の配置/イベント名について、カスタムイベントをデータポイントとしてBrazeに送信および保存しません。
-- エフェメラルイベントソリューションは、Braze のプロダクションiOS およびAndroid SDKs、およびBraze がエフェメラルカスタムイベントソリューションを有効にしたプラットフォームs の将来のBrazeプロダクションSDKs にロールされます。これにより、お客様はこのような本番SDKを使用できるようになり、将来の機能やバグ修正と同期しなくなります。これにより、カスタマーは、他のカスタムプロセスを必要とせずに、将来のSDK 更新s のタグe を実行できるようになります。
+- エフェメラルカスタムイベントには、購入イベントまたは開始セッションと終了セッション (Brazeのドキュメントに記載されている) は含まれません。
+- Braze は、SDK 実装ごとに最大12の配置/イベント名に対して、カスタムイベントを Braze のデータポイントとして送信および保存しません。
+- エフェメラルイベントソリューションは、Braze の本番 iOS および Android SDK、および Braze がエフェメラルカスタムイベントソリューションを有効にしたプラットフォーム用の将来の Braze 本番 SDK に展開されます。これにより、お客様はこのような本番 SDK を使用できるようになり、将来の機能やバグ修正と同期しなくなります。これにより、顧客は、他のカスタムプロセスを必要とせずに、将来の SDK 更新を実行できるようになります。
 <!--
 Keep this doc available on the docs site with the above permalink until 1/21/2026. This feature was built as a one-off page for a customer. Reach out to Rod Amies with questions, if needed.
 -->
diff --git a/_lang/ja/_hidden/other/generations.md b/_lang/ja/_hidden/other/generations.md
index 88acdef02ea..0bf4a5a4b74 100644
--- a/_lang/ja/_hidden/other/generations.md
+++ b/_lang/ja/_hidden/other/generations.md
@@ -1,22 +1,22 @@
 ---
 nav_title: 世代
-article_title: アプリ内メッセージ生成
+article_title: アプリ内メッセージの世代
 hidden: true
 permalink: /iam_generations/ 
 ---
 
-# アプリ中電文の生成
+# アプリ内メッセージの世代
 
-Brazeには現在、3つのアプリ内メッセージsがあります。それぞれに、独自のサポートレベルがあります。アプリ内メッセージ s の最新機能のタグ e を活用するには、最新の[web]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/#upgrading-the-sdk)、iOS、およびAndroid SDK s にアップグレードすることをお勧めします。
+Braze には 3 世代のアプリ内メッセージが用意されています。それぞれに、独自のサポートレベルがあります。アプリ内メッセージの最新機能を活用するには、最新の [web]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/#upgrading-the-sdk)、iOS、Android SDK にアップグレードすることをお勧めします。
 
 このチャートでは、現在使用可能な機能とメッセージタイプ、および各世代で導入されたときを強調表示します。また、このグラフでは、特定の世代でサポートされていないものが明示的に示されています。
 
 | 世代 | 新機能 | サポートされない機能 |
 |---|---|---|
-| **第1世代** | • アプリ トリガー内フルスクリーン、モダル、およびスライドアップメッセージタイプ | カスタムHTMLメッセージ <br> • Webメールキャプチャフォーム <br> • カスタムCSS付きWebモーダル |
+| **第1世代** | • アプリ トリガー内フルスクリーン、モダル、およびスライドアップメッセージタイプ | カスタムHTMLメッセージ <br> • Web メールキャプチャフォーム <br> • カスタムCSS付きWebモーダル |
 | **第2世代** | • テキストの配置コントロール <br> • モーダルの背後にあるオーバーレイ <br> • プレビュー画面のイメージセーフゾーン | ボタンの境界線 |
-| **第3世代** | • ボタンの境界線 <br> • 洗練されたルック&アンプ; すべてのメッセージタイプの感覚 <br> • 世代1、2、3の概念 <br> • 新規クローズXアセット <br> • Webのアクセシビリティの向上 <br> • Notched Devices のサポートが向上しました | (最新のGenerationには常にフル機能がサポートされています!) |
+| **第3世代** | • ボタンの境界線 <br> • すべてのメッセージタイプに対応した洗練されたルックアンドフィール <br> • 第1世代、第2世代、第3世代の概念 <br> • 新しいクローズ X アセット <br> • Web のアクセシビリティの向上 <br> • Notched Devices のサポートが向上しました | (最新のGenerationには常にフル機能がサポートされています!) |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-![世代差]({% image_buster /assets/img/iam-generations-of-modals.png %})
+![世代間の違い]({% image_buster /assets/img/iam-generations-of-modals.png %})
 
diff --git a/_lang/ja/_hidden/other/sms_country_blocklist.md b/_lang/ja/_hidden/other/sms_country_blocklist.md
index 4255b5b60f0..8f45aa39460 100644
--- a/_lang/ja/_hidden/other/sms_country_blocklist.md
+++ b/_lang/ja/_hidden/other/sms_country_blocklist.md
@@ -9,28 +9,28 @@ permalink: /sms_country_blocklist/
 
 SMSトラフィックポンプからお客様を保護するため、Brazeは現在、米国禁輸国およびトラフィックポンプのリスクが高いとされる国のブロックリストを管理している。デフォルトでは、Brazeはこれらの国にSMSを送信しない： 
 
-- 「アフガニスタン
+- 「AF」# アフガニスタン
 - "AO"# アンゴラ
 - "AZ"# アゼルバイジャン
 - 「BD" # バングラデシュ
 - 「BI" # ブルンジ
 - 「CF」#中央アフリカ共和国
 - 「CM" # カメルーン
-- 「キューバ
+- 「CU」# キューバ
 - 「CV" # カーボベルデ
 - 「DZ # アルジェリア
 - "GM "#ガンビア
-- "GT"# グアテマラ
+- 「GT」# グアテマラ
 - 「ID" # インドネシア
 - 「IR" # イラン
 - 「IQ # イラク
-- 「JE" # ジャージー
+- 「JE」# ジャージー
 - 「LY# リビア
-- 「ケニア
-- "KG"# キルギス
-- 「カンボジア
-- 「キリバス
-- "KP"# 北朝鮮
+- 「KE」# ケニア
+- 「KG」# キルギスタン
+- 「KH」# カンボジア
+- 「KI」# キリバス
+- 「KP」# 北朝鮮
 - "LK"# スリランカ
 - 「MA" # モロッコ
 - "ML "#マリ
@@ -40,11 +40,11 @@ SMSトラフィックポンプからお客様を保護するため、Brazeは現
 - "MW"# マラウイ
 - 「NE" # ニジェール
 - 「NF" # ノーフォーク島
-- "NG "#ニジェラ
+- 「NG」# ナイジェリア
 - 「NU" # ニウエ
 - 「OM" # オマーン
-- 「パキスタン
-- 「パレスチナ
+- 「PK」# パキスタン
+- 「PS」# パレスチナ
 - 「SA" # サウジアラビア
 - 「SD スーダン
 - "SI "#スロベニア
@@ -54,13 +54,13 @@ SMSトラフィックポンプからお客様を保護するため、Brazeは現
 - 「SY" # シリア
 - "TG"# トーゴ
 - 「TJ # タジキスタン
-- 「TL # 東ティモール
+- 「TL」# 東ティモール
 - "TN"# チュニジア
 - 「TZ" # タンザニア
-- 「ウクライナ
+- 「UA」# ウクライナ
 - "UZ "#ウズベキスタン
 - 「VN" # ベトナム
 - 「WF" # ウォリス＆フォルトゥナ
-- 「イエメン
+- 「YE」# イエメン
 - 「ZB" # ジンバブエ
 - "ZM "#ザンビア
diff --git a/_lang/ja/_hidden/other/support_contact.md b/_lang/ja/_hidden/other/support_contact.md
index 5b46d902812..7cf8b5d62d1 100644
--- a/_lang/ja/_hidden/other/support_contact.md
+++ b/_lang/ja/_hidden/other/support_contact.md
@@ -1,6 +1,6 @@
 ---
 permalink: /support_contact/
-nav_title: ヘルプ｜ブレイズ
+nav_title: ヘルプ | Braze
 hide_nav: true
 layout: basic
 hide_toc: true
@@ -1332,12 +1332,12 @@ $( document ).ready(function() {
  }
 });
 </script>
-<div id="firefox_warning" style="display:none;">Firefoxユーザーの場合、このサイトを許可リストに入れるか、<a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Privacy/Tracking_Protection?utm_source=mozilla&utm_medium=firefox-console-errors&utm_campaign=default" target="_blank">トラッキング保護設定を</a>チェックする。</div>
+<div id="firefox_warning" style="display:none;">Firefox ユーザーの場合、このサイトを許可リストに入れるか、<a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Privacy/Tracking_Protection?utm_source=mozilla&utm_medium=firefox-console-errors&utm_campaign=default" target="_blank">トラッキング保護設定</a>にチェックを入れてください。そうしないと、チケットが送信されない場合があります。</div>
 
 <div class="container-fluid" id="main-container">
       <div class="row">
           <div class="col" >
-              <h1 class="h1">お困りですか？</h1>
+              <h1 class="h1">お困りの場合</h1>
               <div class="gradient-line"></div>
           </div>
       </div>
diff --git a/_lang/ja/_hidden/other/user_archival.md b/_lang/ja/_hidden/other/user_archival.md
index 7ce34962c82..f99f26bd23d 100644
--- a/_lang/ja/_hidden/other/user_archival.md
+++ b/_lang/ja/_hidden/other/user_archival.md
@@ -9,22 +9,22 @@ description: "この参考記事では、ユーザーアーカイブの定義、
 ---
 # ユーザーアーカイブ
 
-> 毎週日曜日の午前5時30分（米国東部標準時間）に、BrazeはBrazeサービスから非アクティブユーザーと休眠ユーザーを削除するプロセスを実行する。なお、Brazeは、ワークスペースのユーザー数が250,000のしきい値に達しない限り、ユーザーをアーカイブしない。 
+> Braze は毎週日曜日の東部標準時午前5時30分に、非アクティブユーザーと休眠ユーザーを Braze サービスから削除するプロセスを実行します。なお、Brazeは、ワークスペースのユーザー数が250,000のしきい値に達しない限り、ユーザーをアーカイブしない。 
 
-このプロセスは、Brazeがキャンペーンの到達可能なオーディエンスに関する正確な統計を提供することを目的としている。また、[GDPRの][1]2つの重要な概念に従っている：
+このプロセスは、キャンペーンで到達可能なオーディエンスに関する正確な統計を Braze が提供できるようにすることを目的としています。また、[GDPR][1] の2つの主要な概念に従って機能します。
 
-1. 保存制限の原則-処理され保存された個人データは、必要な期間を超えて保存されるべきではない。
+1. 保存制限の原則-処理され保存された個人データは、必要な期間を超えて保存されるべきではありません。
 2. 個人データを処理する正当な事業目的を有すること。
 
-すなわち、処理され保存された個人データは必要以上の期間保存されるべきではなく、個人データは合法的な業務目的のためにのみ処理されるべきである。アーカイブされたユーザーは、GDPRに準拠して配信停止ステータスも削除される。
+すなわち、処理され保存された個人データは必要以上の期間保存されるべきではなく、個人データは合法的な業務目的のためにのみ処理されるべきです。アーカイブされたユーザーは、GDPR に従って配信停止ステータスも削除されます。
 
-{% alert note %} 顧客は、ユーザーが非アクティブか休止状態かを完全にコントロールできる。Braze Canvasは、この機能を自動的に実行する機能を提供しており、非アクティブまたは休止状態のユーザーの一部または全員に対して、この機能を効果的にオフにすることができる。 {% endalert %}
+{% alert note %} 顧客は、ユーザーが非アクティブか休止状態かを完全にコントロールできます。Braze キャンバスにはこれを自動的に行う機能が備わっており、一部またはすべての非アクティブユーザーまたは休眠ユーザーに対してこの機能を効果的にオフにすることができます。 {% endalert %}
 
-## ユーザー・アーカイブ定義
+## ユーザーアーカイブ定義
 
 ### アクティブユーザー
 
-Brazeは、一定期間の「アクティブユーザー」を、モバイルアプリやウェブサイトでセッションを記録したユーザー、更新を受けたユーザー、メッセージを送信したユーザー、メッセージと対話したユーザーと定義している。
+Braze は、モバイルアプリまたはウェブサイトでセッションを記録したユーザー、更新されたユーザー、メッセージが送られたユーザー、メッセージを操作したりしたユーザーを、一定期間の「アクティブユーザー」と定義しています。
 
 新規ユーザーがログインしたときにユーザーを識別するためにユーザーIDを設定した場合、そのユーザーは別のアクティブユーザーとしてカウントされる。API 経由で更新されたユーザーも、更新の期間中はアクティブユーザーとしてカウントされます。
 
@@ -34,33 +34,33 @@ Brazeは、一定期間の「アクティブユーザー」を、モバイルア
 
 ### 非アクティブユーザー
 
-「非アクティブ・ユーザー」とは、連絡が取れず、解約した可能性が高いユーザーのことである。非アクティブ・ユーザーとは、これらの条件をすべて満たすユーザーのことである：
+「非アクティブユーザー」とは、連絡が取れず、解約した可能性が高いユーザーのことである。非アクティブユーザーとは、これらの条件をすべて満たすユーザーのことである：
 
 - メールが受信できない。例えば、電子メールアドレスを持っていなかったり、すべての電子メールリストの配信を停止していたりする。
-- SMSを受信できない。例えば、有効な電話番号を持っていなかったり、すべてのSMS購読グループから登録解除されていたりする。
+- SMS を受信できない。例えば、有効な電話番号を持っていなかったり、すべてのSMS購読グループから登録解除されていたりする。
 - プッシュを受けられない。例えば、アプリをアンインストールしたとか、プッシュ許可を無効にしたとか。
-- WhatsAppメッセージを受信できない。例えば、有効な電話番号を持っていなかったり、全てのWhatsApp購読グループから退会している。
-- 半年以上、ワークスペースでモバイルアプリを使ったり、ウェブサイトを見たりしたことがない。
+- WhatsApp メッセージを受信できない。例えば、有効な電話番号を持っていなかったり、全てのWhatsApp購読グループから退会している。
+- 半年以上、ワークスペースでモバイルアプリを使ったり、Web サイトを閲覧していない。
 - 半年以上、ワークスペースからメッセージを受け取っていない。
 - 半年以上更新されていない。
 
-この場合、これらのユーザーはメッセージを送ることができず、ブランドとエンゲージしていない。これらのユーザーは事実上、解約している。
+この場合、これらのユーザーはメッセージを受け取ることができず、ブランドとのエンゲージメントもありません。これらのユーザーは事実上、解約しています。
 
 ### 休眠ユーザー
 
-「休眠ユーザー」とは、過去12ヶ月間まったく活動をしていないユーザーのことである：
+「休眠ユーザー」とは、過去12ヶ月間まったく活動がなく、次の条件を満たすユーザーを指します。
 
-- 12ヶ月以上、モバイルアプリを使用したり、ワークスペースのウェブサイトを閲覧したことがない。
+- 12ヶ月以上、ワークスペースでモバイルアプリを使ったり、Web サイトを閲覧していない。
 - 12ヶ月以上、ワークスペースからメッセージを受け取っていない。
 - 12ヶ月以上更新されていない。
 
 ## グローバル・コントロール・グループのユーザー
 
-グローバル・コントロール・グループのユーザーは、たとえ非アクティブまたは休眠ユーザーの 定義に合致していたとしても、アーカイブされることはない。 
+グローバル・コントロール・グループのユーザーは、たとえ非アクティブまたは休眠ユーザーの定義に合致していたとしても、アーカイブされることはない。 
 
-### 治療サンプル群
+### 治療サンプルグループ
 
-治療サンプルグループユーザーは、グローバルコントロールグループレポート内のアーカイブから除外される。
+治療サンプルグループのユーザーは、グローバルコントロールグループレポート内のアーカイブから除外されます。
 
 ## テストユーザー
 
@@ -68,12 +68,12 @@ Brazeは、一定期間の「アクティブユーザー」を、モバイルア
 
 ## スパムブロック
 
-Brazeは、500万セッションを超える個々のユーザー（「ダミーユーザー」）をブロックし、SDKイベントをインジェストしなくなった。正当なユーザーにこのようなことが起こった場合は、Brazeの[サポートに]({{site.baseurl}}/braze_support/)チケットを提出すること。
+Braze は、500万を超えるセッションを持つ個々のユーザー (「ダミーユーザー」) をブロックするとともに、それらの SDK イベントは通常、正しくない統合の結果であるため、取り込まれなくなりました。正当なユーザーに対してこの問題が発生した場合は、Braze [サポート]({{site.baseurl}}/braze_support/)にチケットを提出してください。
 
 ダッシュボードのダミーユーザーを見つけるには、以下の手順を実行する：
 
-1. [セグメントを]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/)作成する。
-2. フィルター`Session Count` を選択し、`more than 5,000,000` に設定する。
+1. [セグメント]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/)を作成します。
+2. フィルター `Session Count` を選択し、`more than 5,000,000` に設定します。
 3. CSVでセグメントをエクスポートする。
 
 必要であれば、[`/users/delete` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/)経由でユーザーを削除できる。
@@ -96,9 +96,9 @@ Brazeは、ユーザーアーカイバルポリシーをカスタマイズでき
 
 1. アーカイブ基準を満たし、保持したいユーザーを対象とする。<br><br>
       ![最後にメッセージを受け取ったのが23週間以上前、キャンペーンやキャンバスステップからのメッセージを受け取ったことがない、最後にこれらのアプリを利用したのが23週間以上前、これらのアプリを利用した回数が0回というユーザーを対象とする。][2]<br><br>
-2. 再入国資格を6カ月弱に設定する。<br><br>
-      ![エントリーコントロールでは、再資格をオンとし、再資格ウィンドウを23週に設定した。][3]<br><br>
-3. ユーザ更新ステップを構成して、各プロファイルにイベントを追加する。<br><br>
+2. 再資格付与期間を6か月弱に設定します。<br><br>
+      ![再適格性付与がオンになっており、再適格性付与期間が23週間に設定されているエントリコントロール。][3]<br><br>
+3. ユーザ更新ステップを構成して、各プロファイルにイベントを追加します。<br><br>
       ![ユーザーのプロファイルに "do_not_archive "イベントを追加するユーザー更新ステップ。][4]
 {% details サンプル・ユーザー更新オブジェクト %}
 
diff --git a/_lang/ja/_hidden/other/user_csv_lambda.md b/_lang/ja/_hidden/other/user_csv_lambda.md
index a82e0fcfddf..40b6d051efe 100644
--- a/_lang/ja/_hidden/other/user_csv_lambda.md
+++ b/_lang/ja/_hidden/other/user_csv_lambda.md
@@ -1,30 +1,30 @@
 ---
 nav_title: ユーザー属性CSVラムダプロセス
 permalink: /user_csv_lambda/
-description: "以下の記事では、Track users Brazeエンドポイントを通じてCSVファイルからユーザー属性データを直接BrazeにポストするLambdaプロセスを簡単にデプロイできるサーバーレスアプリケーションを紹介している。"
+description: "以下の記事では、ユーザー追跡 Braze エンドポイントを通じて CSV ファイルからユーザー属性データを直接 Braze にポストする Lambda プロセスを簡単にデプロイできるサーバーレスアプリケーションを紹介しています。"
 hidden: true
 ---
 
 # ユーザー属性CSVをBrazeにインポートする
 
-> 以下の記事では、CSVファイルからユーザー属性データを[Track usersエンドポイントを通じて]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)Brazeに直接ポストするLambdaプロセスを簡単にデプロイできるサーバーレスアプリケーションを紹介している。このアプリケーションの統合は、我々のAmperityパートナーとともにテストされ、[GitHubで](https://github.com/braze-inc/growth-shares-lambda-user-csv-import)見ることができる。
+> 以下の記事では、[ユーザー追跡エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)を通じて CSV ファイルからユーザー属性データを直接 Braze にポストする Lambda プロセスを簡単にデプロイできるサーバーレスアプリケーションを紹介しています。このアプリケーションの統合は、我々の Amperity パートナーによってテストされ、[GitHub](https://github.com/braze-inc/growth-shares-lambda-user-csv-import) で確認できます。
 
-このプロセスは、設定されたAWS S3バケットにCSVファイルをアップロードすると即座に起動する。大きなファイルやアップロードを扱うことができるが、ラムダの時間制限により、関数は10分後に実行を停止する。このプロセスは、ファイルの残りの部分を処理するために、別のラムダ・インスタンスを起動する。ファンクションのタイミングについての詳細は、[推定実行](#estimated-execution-times)時間をチェックしてほしい。
+このプロセスは、設定された AWS S3 バケットに CSV ファイルをアップロードすると即座に起動します。大きなファイルやアップロードを扱うことができますが、Lambda の時間制限により、関数は10分後に実行を停止します。このプロセスは、ファイルの残りの部分を処理するために、別の Lambda インスタンスを起動します。ファンクションのタイミングについての詳細は、[推定実行](#estimated-execution-times)時間をチェックしてほしい。
 
 {% alert important %}
-このアプリケーションは、Brazeの成長部門によって構築され、維持されている。このアプリケーションの制作者に連絡を取りたい場合は、[GitHubのissueを](https://github.com/braze-inc/growth-shares-lambda-user-csv-import/issues)作成し、フィードバックや問題が発生する可能性があることを伝えてほしい。
+このアプリケーションは Braze Growth 部門によって構築および保守されています。このアプリケーションの制作者に連絡を取りたい場合は、発生する可能性のあるフィードバックや問題について、[GitHub issue](https://github.com/braze-inc/growth-shares-lambda-user-csv-import/issues) を作成してください。
 {% endalert %}
 
 #### CSVユーザー属性
 
-更新されるユーザー属性は、以下の`.csv` ：
+更新されるユーザー属性は、次の `.csv` 形式である必要があります。
 
 ```
 external_id,attr_1,...,attr_n
 userID,value_1,...,value_n
 ```
 
-最初の列は更新されるユーザーの外部IDを指定し、次の列は属性名と値を指定しなければならない。指定する属性の数は様々である。処理するCSVファイルがこのフォーマットに従っていない場合、この関数は失敗する。  
+最初の列には更新するユーザーの外部 ID を指定し、次の列には属性名と値を指定する必要があります。指定する属性の数は異なる場合があります。処理するCSVファイルがこのフォーマットに従っていない場合、この関数は失敗する。  
 
 **CSVファイルの例：**
 
@@ -40,19 +40,19 @@ def456,578,Hunter-Hayes
 
 ## 要件
 
-このラムダ関数を成功させるには、以下のものが必要だ：
+この Lambda 関数を正常に実行するには、次のものが必要です。
 - S3とLambdaサービスを利用するための**AWSアカウント**
-- **Braze**サーバーに接続するための**Braze API URL**
+- Braze サーバーに接続するための **Braze API URL**
 - `/users/track` エンドポイントにリクエストを送信できるようにするための**Braze API キー**
 - 更新するユーザーの外部IDと属性を含む**CSVファイル**
 
 {% tabs %}
 {% tab API URL %}
 
-API URL、またはRESTエンドポイントは、Braze APIドキュメントやダッシュボードで確認できる。
+API URL、または REST エンドポイントは、Braze API ドキュメントおよびダッシュボードにあります。
 
-- **APIドキュメント**<br>[APIドキュメントに従って]({{site.baseurl}}/user_guide/administrative/access_braze/braze_instances/#braze-instances)、BrazeインスタンスURLをRESTエンドポイントURLに一致させるだけでよい。例えば、ダッシュボードに`dashboard-01.braze.com/` URLが表示されている場合、RESTエンドポイントは`https://rest.iad-01.braze.com` 。<br><br>
-- **ダッシュボード**<br>**Manage Settings**ページでSDKエンドポイントを探す。RESTエンドポイントを取得するには、`sdk` を`rest` に置き換える。例えば、`sdk.iad-01.braze.com` と表示された場合、APIのURLは次のようになる。 `rest.iad-01.braze.com`
+- **API ドキュメント**<br>[APIドキュメントに従って]({{site.baseurl}}/user_guide/administrative/access_braze/braze_instances/#braze-instances)、BrazeインスタンスURLをRESTエンドポイントURLに一致させるだけでよい。例えば、ダッシュボードに`dashboard-01.braze.com/` URLが表示されている場合、RESTエンドポイントは`https://rest.iad-01.braze.com` 。<br><br>
+- **ダッシュボード**<br>\[**設定の管理**] ページに移動し SDK エンドポイントを見つけます。`sdk` を `rest` に置き換えて、REST エンドポイントを取得します。例えば、`sdk.iad-01.braze.com` と表示された場合、APIのURLは次のようになる。 `rest.iad-01.braze.com`
 
 {% endtab %}
 {% tab APIキー %}
@@ -62,12 +62,12 @@ Brazeサーバーに接続するには、APIキーが必要である。この一
 APIキーを取得するには、**「設定」**>「**APIキー**」を選択する。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、**Developer Console**>**API Settingsで**APIキーを見つけることができる。
+[古いナビゲーション]({{site.baseurl}}/navigation) を使用している場合は、\[**開発者コンソール**] > \[**API 設定**] に API キーがあります。
 {% endalert %}
 
-`/users/track` 、エンドポイントへの投稿を許可するAPIキーが必要となる。APIキーの1つがそのエンドポイントをサポートしていることが分かっていれば、そのキーを使うことができる。 
+`/users/track` エンドポイントに投稿する権限を持つ API キーが必要です。APIキーの1つがそのエンドポイントをサポートしていることが分かっていれば、そのキーを使うことができる。 
 
-新しいものを作成するには、**Create New API Keyを**クリックする。次に、APIキーに名前を付け **users.track**を選択し、**\[Save API Key**]をクリックする。
+新しいものを作成する場合は、\[**新規 API キー作成**] をクリックします。次に、API キーに名前を付け、\[**ユーザーデータ**] エンドポイントグループの下の \[**users.track**] を選択し、\[**API キーの保存**] をクリックします。
 
 {% endtab %}
 {% endtabs %}
@@ -81,32 +81,32 @@ APIキーを取得するには、**「設定」**>「**APIキー**」を選択
 
 #### デプロイする
 
-ユーザー属性CSVファイルの処理を開始するには、処理を代行するサーバーレス・アプリケーションをデプロイする必要がある。このアプリケーションは、デプロイを成功させるために以下のリソースを自動的に作成する：
+ユーザー属性 CSV ファイルの処理を開始するには、処理を自動的に行うサーバーレスアプリケーションをデプロイする必要があります。このアプリケーションは、デプロイを成功させるために以下のリソースを自動的に作成する：
 
 - ラムダ関数
 - Lambdaプロセスが読み込み可能なCSVファイル用のS3バケット_（注意：このLambda関数は、`.csv` 拡張子ファイルの通知のみを受け取る）_
-- S3バケットの作成を許可する役割
+- S3 バケットの作成を許可するロール
 - Lambdaが新しいバケットでS3のアップロードイベントを受け取ることを許可するポリシー
 
-[アプリケーションへの](https://console.aws.amazon.com/lambda/home?region=us-east-1#/create/app?applicationId=arn:aws:serverlessrepo:us-east-1:585170621372:applications/braze-user-attribute-import)直接リンクに従うか、[AWS Serverless Application Repositoryを](https://serverlessrepo.aws.amazon.com/applications)開き、"braze-user-attribute-import "を検索する。なお、このアプリケーションを見るには、`Show apps that create custom IAM roles and resource policies` のチェックボックスをチェックしなければならない。アプリケーションは、ラムダが新しく作成されたS3バケットから読み込むためのポリシーを作成する。
+[アプリケーション](https://console.aws.amazon.com/lambda/home?region=us-east-1#/create/app?applicationId=arn:aws:serverlessrepo:us-east-1:585170621372:applications/braze-user-attribute-import)への直接リンクをたどるか、[AWS Serverless Application Repository](https://serverlessrepo.aws.amazon.com/applications) を開いて「braze-user-attribute-import」を検索します。なお、このアプリケーションを表示するには、`Show apps that create custom IAM roles and resource policies` のチェックボックスをオンにしなければなりません。アプリケーションは、ラムダが新しく作成されたS3バケットから読み込むためのポリシーを作成する。
 
-**Deployを**クリックし、AWSに必要なリソースをすべて作成させる。
+\[**デプロイ**] をクリックし、AWS に必要なリソースをすべて作成させます。
 
-デプロイを観察し、スタック（つまり必要なすべてのリソース）が[CloudFormationに](https://console.aws.amazon.com/cloudformation/)作成されていることを確認できる。serverlessrepo-braze-user-attribute-import」というスタックを見つける。**ステータスが** `CREATE_COMPLETE` に変わったら、その機能は使用可能である。スタックをクリックして**「リソース」を**開き、さまざまなリソースが作成されるのを見ることができる。
+デプロイを監視し、[CloudFormation](https://console.aws.amazon.com/cloudformation/) 内にスタック (つまり、必要なすべてのリソース) が作成されていることを確認できます。serverlessrepo-braze-user-attribute-import」というスタックを見つける。**ステータス**が `CREATE_COMPLETE` に変わったら、その機能は使用可能です。スタックをクリックして**「リソース」を**開き、さまざまなリソースが作成されるのを見ることができる。
 
 以下のリソースが作成された：
 
 - [S3バケット](https://s3.console.aws.amazon.com/s3/)-`braze-user-csv-import-aaa123` という名前のバケット。`aaa123` はランダムに生成された文字列である。
-- [ラムダ関数](https://console.aws.amazon.com/lambda/)\- 以下の名前のラムダ関数である。 `braze-user-attribute-import`
-- [IAM Role](https://console.aws.amazon.com/iam/)-`braze-user-csv-import-BrazeUserCSVImportRole` という名前のポリシーで、ラムダがS3から読み込み、関数の出力をログに記録することを許可する。
+- [Lambda 関数](https://console.aws.amazon.com/lambda/)- `braze-user-attribute-import` という名前の Lambda 関数
+- [IAM ロール](https://console.aws.amazon.com/iam/)\- Lambda が S3 から読み取りを行い、関数出力をログに記録することを許可する `braze-user-csv-import-BrazeUserCSVImportRole` という名前のポリシー
 
-#### 走る
+#### 実行
 
 この機能を実行するには、新しく作成したS3バケットにユーザー属性CSVファイルをドロップする。
 
 ## モニタリングとロギング
 
-関数が正常に実行されていることを確認するには、関数の実行ログを読めばいい。BrazeユーザーCSVインポート機能を開き（コンソールのLambdaリストから選択）、**Monitorに**移動する。ここでは、その関数の実行履歴を見ることができる。出力を読むには、**View logs in CloudWatchを**クリックする。チェックしたいラムダ実行イベントを選択する。
+関数が正常に実行されていることを確認するには、関数の実行ログを読めばいい。Braze ユーザー CSV インポート関数を開き (コンソールの Lambda リストから選択)、\[**Monitor**] に移動します。ここでは、その関数の実行履歴を見ることができる。出力を読み取るには、\[**CloudWatch でログを表示**] をクリックします。チェックしたいラムダ実行イベントを選択する。
 
 ## 推定実行時間
 _2048 MB ラムダ関数_
@@ -120,12 +120,12 @@ _2048 MB ラムダ関数_
 
 ## 既存の関数を更新する
 
-すでにアプリケーションをデプロイしていて、新しいバージョンがリポジトリにある場合は、初めてデプロイするのと同じように、機能を再デプロイすることでアップデートできる。つまり、Braze API KeyとBraze API URLを再度渡す必要がある。アップデートはファンクションコードを上書きするだけだ。S3バケットのような既存のリソースを変更したり削除したりすることはない。
+すでにアプリケーションをデプロイしていて、新しいバージョンがリポジトリにある場合は、初めてデプロイするのと同じように、機能を再デプロイすることでアップデートできる。つまり、Braze API キーと Braze API URL を再度渡す必要があります。アップデートはファンクションコードを上書きするだけだ。S3 バケットなどの他の既存のリソースを変更または削除することはありません。
 
 ## 致命的なエラー
 
-予期せぬエラーによってファイルの処理が続行できなくなった場合、イベントが記録される（「[モニタリングとロギング](#monitoring-and-logging)」のCloudWatchからアクセス可能）。データ・ポイントを保存するために、同じデータを再インポートしないことが重要である。[GitHubリポジトリに](https://github.com/braze-inc/growth-shares-lambda-user-csv-import#fatal-error)その手順がある。
+ファイルのさらなる処理を妨げる予期しないエラーが発生した場合は、プログラムがファイルの処理を停止したポイントから Lambda を再起動するために使用できるイベントがログに記録されます (「[モニタリングとロギング](#monitoring-and-logging)」で説明されている CloudWatch からアクセス可能)。データ・ポイントを保存するために、同じデータを再インポートしないことが重要である。これを行う手順については、[GitHub リポジトリ](https://github.com/braze-inc/growth-shares-lambda-user-csv-import#fatal-error)を参照してください。
 
 {% alert important %}
-[致命的なエラーや](https://github.com/braze-inc/growth-shares-lambda-user-csv-import#fatal-error) [ラムダ設定の](https://github.com/braze-inc/growth-shares-lambda-user-csv-import#lambda-configuration)処理方法については、GitHubリポジトリを参照のこと。
+[致命的なエラー](https://github.com/braze-inc/growth-shares-lambda-user-csv-import#fatal-error)や [Lambda 設定](https://github.com/braze-inc/growth-shares-lambda-user-csv-import#lambda-configuration)の処理方法について詳しくは、GitHub リポジトリを参照してください。
 {% endalert%}
\ No newline at end of file
diff --git a/_lang/ja/_hidden/pricing/braze_go.md b/_lang/ja/_hidden/pricing/braze_go.md
index ad75c18c541..17fd60571fe 100644
--- a/_lang/ja/_hidden/pricing/braze_go.md
+++ b/_lang/ja/_hidden/pricing/braze_go.md
@@ -8,30 +8,30 @@ hide_toc: true
 
 # Braze Go
 
-> Braze・ゴーは、マーケティングチームがどこからでも始めて、どこへでも行けるように、Braze カスタマーエンゲージメント プラットフォームへのアクセスを合理化します。Braze・ゴーは、シンプルかつ効率的に設計されており、特定の新興国向けに設計されています。
+> Braze Go は、お客様のマーケティングチームがどこからでも始めて、どこへでも行けるように、Braze カスタマーエンゲージメントプラットフォームへのアクセスを合理化します。Braze Go は、シンプルで効率的な設計になっており、特定の新興市場に合わせて設計されています。
 
 {% alert important %}
-Braze・ゴーは、一部のマーケットでは利用できません。Braze Go について詳しく知りたい場合は、アカウントマネージャーにお問い合わせください。
+Braze Go は、一部のマーケットでは利用できません。Braze Go について詳しく知りたい場合は、アカウントマネージャーにお問い合わせください。
 {% endalert %}
 
 Braze Go には、Braze と同じ機能がすべて用意されており、以下の機能にフォーカスされた変更が加えられています。 
 
-- 有効なキャンペーン数は最大30 個です。
+- アクティブなキャンペーンは最大30件まで保持できます。
 - アクティブなキャンバスは最大20 個まで設定できます。
-- REST API の総デフォルト レート制限は、1 ワークスペースあたり1 時間あたり50,000 です。
+- REST API のデフォルトレート制限の合計は、ワークスペースあたり1時間あたり50,000です。
     - Braze Go 以外の使用法については、[ REST API limits]({{site.baseurl}}/api/api_limits/#rate-limits-by-request-type) について詳しく説明します。
 - キャンペーンとキャンバス間のアクションデータリテンションは2 か月で、復元は行われません。
-    - Braze Go 以外の使用法については、[ メッセージング inter アクション data availability]({{site.baseurl}}/messaging_interaction_data/) について詳しく説明します。
+    - Braze Go 以外の使用方法については、[メッセージングインタラクションデータの可用性]({{site.baseurl}}/messaging_interaction_data/)に関する詳細を参照してください。
 
 {% alert note %}
 「キャンペーン」と「キャンバス」のアクション間データは、Snowflakeデータとは異なり、何の影響もありません。
 {% endalert %}
 
 - Braze-Braze webhookはサポートされていません。
-- 以下のフィルターs は、タグs に関連するものではありません。
+- タグに関連するフィルターはサポートされていません。特に次のフィルターはサポートされていません。
     - クリックまたは開かれたキャンペーンまたはキャンバス(タグ付き)
     - キャンペーンまたはキャンバスからタグ付きで最後に受信したメッセージ
     - 受信したキャンペーンまたはタグ付きキャンバス
-- また、Brazeは、1年以内に再度実行されなかった1年を超えるイベント、購入、またはその両方を削除する、ユーザープロファイルのイベントおよび購入データのデータリテンションポリシーを実装することもできます。ただし、このデータは、2年間SQLセグメント拡張で引き続き使用できます。
+- Braze は、ユーザープロファイルイベントと購入データのデータリテンションポリシーを実装することもできます。このポリシーでは、1年以上前のイベント、購入、またはその両方が1年間実行されていない場合に削除されます。ただし、このデータは、2年間 SQL セグメントエクステンションで引き続き使用できます。
 
-上記のいずれかの機能が更新 d の場合、これはこの記事に反映され、[リリースノート]({{site.baseurl}}/help/release_notes/#most-recent-braze-release-notes) に記載されます。
\ No newline at end of file
+上記の機能が更新された場合は、この記事に反映され、[リリースノート]({{site.baseurl}}/help/release_notes/#most-recent-braze-release-notes)に記載されます。
\ No newline at end of file
diff --git a/_lang/ja/_hidden/pricing/message_credits_delta_a3sy.md b/_lang/ja/_hidden/pricing/message_credits_delta_a3sy.md
index 4e942366b03..bf9502731d1 100644
--- a/_lang/ja/_hidden/pricing/message_credits_delta_a3sy.md
+++ b/_lang/ja/_hidden/pricing/message_credits_delta_a3sy.md
@@ -6,7 +6,7 @@ noindex: true
 hide_toc: true
 ---
 
-# メッセージクレジット - デルタ（機密）
+# メッセージクレジット - デルタ (社外秘)
 
 > Message Creditsは、Brazeのクロスチャネルのパッケージ構造で、ネイティブSMS、MMS、およびWhatsAppの提供に対応しています。Brazeメッセージングチャネルを利用する際に柔軟で透明性のある体験を提供するために、メッセージクレジットを使用します。このページの表に示されているすべてのチャネルで購入されたクレジットの割り当てを使用できます。
 
@@ -32,7 +32,7 @@ hide_toc: true
 {: .reset-td-br-1 .reset-td-br-2}
 
 
-## メッセージクレジットのクレジット比率表 - デルタ
+## メッセージクレジットのクレジット比率の表 - デルタ
 
 {% details クリックして展開 %}
 <table>
@@ -42,10 +42,10 @@ hide_toc: true
     </colgroup>
     <tr>
         <th><b>Channel</b></th>
-        <th><b>チャネルのクレジット比率</b></th>
-        <th><b>送信先</b></th>
-        <th><b>乗数</b></th>
-        <th class="credits-column"><b>1 回の送信で使用されるクレジット</b></th>
+        <th>**チャネルのクレジット比率**</th>
+        <th>**送信先**</th>
+        <th>**乗数**</th>
+        <th class="credits-column">**1 回の送信で使用されるクレジット**</th>
     </tr>
     <tr>
         <td>SMS - 米国 / カナダ</td>
@@ -1618,7 +1618,7 @@ hide_toc: true
     <tr>
         <td>SMS / MMS - グローバル</td>
         <td>10</td>
-        <td>七面鳥</td>
+        <td>トルコ</td>
         <td>0.77</td>
         <td>7.70</td>
     </tr>
@@ -2395,7 +2395,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>REST of Latin America マーケティング</td>
+        <td>ラテンアメリカ地域のその他諸国 マーケティング</td>
         <td>1.95</td>
         <td>19.50</td>
     </tr>
@@ -2444,7 +2444,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>西ヨーロッパの残りの部分 認証</td>
+        <td>西欧地域のその他諸国 認証</td>
         <td>1.00</td>
         <td>10.00</td>
     </tr>
@@ -2661,7 +2661,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>イギリスUtility</td>
+        <td>イギリスのユーティリティ</td>
         <td>1.05</td>
         <td>5.80</td>
     </tr>
diff --git a/_lang/ja/_hidden/pricing/message_credits_gamma_0dhr.md b/_lang/ja/_hidden/pricing/message_credits_gamma_0dhr.md
index 50e87163615..7c64b177bcb 100644
--- a/_lang/ja/_hidden/pricing/message_credits_gamma_0dhr.md
+++ b/_lang/ja/_hidden/pricing/message_credits_gamma_0dhr.md
@@ -6,16 +6,16 @@ noindex: true
 hide_toc: true
 ---
 
-# メッセージ・クレジット - ガンマ（コンフィデンシャル）
+# メッセージクレジット - ガンマ (社外秘)
 
 > メッセージクレジットは、BrazeのネイティブSMS、MMS、WhatsAppのクロスチャネルパッケージング構造である。メッセージクレジットは、Brazeのメッセージングチャネルを利用する際に、柔軟で透明性の高い体験を提供するために使用する。このページの表に示されているすべてのチャネルで購入されたクレジットの割り当てを使用できます。
 
 {% alert note %}
-チャンネルが異なれば、報道における測定単位も異なる。<br><br>
+レポートの測定単位は、チャネルによって異なります。<br><br>
 <b>WhatsApp:</b>会話<br>
 <b>SMS:</b>セグメント<br>
 <b>MMS:</b>セグメント<br><br>
-つまり、WhatsAppメッセージに使用されたクレジットは会話の開始時に計算され、SMSとMMSメッセージの両方に使用されたクレジットは送信されたセグメントで計算される。
+つまり、WhatsApp メッセージに使用されるクレジットは会話の開始時に計算され、SMS と MMS メッセージの両方に使用されるクレジットは送信されたセグメントで計算されます。
 <br><br>
 最後に、通信事業者料金は別途請求され (後払い)、このメッセージクレジット SKU の一部とは見なされません。
 {% endalert %}
@@ -32,7 +32,7 @@ hide_toc: true
 {: .reset-td-br-1 .reset-td-br-2}
 
 
-## メッセージクレジットのクレジット比率表 - ガンマ
+## メッセージクレジットのクレジット比率の表 - ガンマ
 
 {% details クリックで拡大 %}
 <table>
@@ -42,10 +42,10 @@ hide_toc: true
     </colgroup>
     <tr>
         <th><b>Channel</b></th>
-        <th><b>チャネルのクレジット比率</b></th>
-        <th><b>送信先</b></th>
-        <th><b>乗数</b></th>
-        <th class="credits-column"><b>1 回の送信で使用されるクレジット</b></th>
+        <th>**チャネルのクレジット比率**</th>
+        <th>**送信先**</th>
+        <th>**乗数**</th>
+        <th class="credits-column">**1 回の送信で使用されるクレジット**</th>
     </tr>
     <tbody><tr>
         <td>SMS - 米国 / CA</td>
@@ -1828,7 +1828,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>チリ・サービス</td>
+        <td>チリサービス</td>
         <td>1.20</td>
         <td>12.00</td>
     </tr>
@@ -2010,7 +2010,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>インドネシア・サービス</td>
+        <td>インドネシアサービス</td>
         <td>0.50</td>
         <td>5.00</td>
     </tr>
@@ -2059,7 +2059,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>イタリア・マーケティング</td>
+        <td>イタリアマーケティング</td>
         <td>1.85</td>
         <td>18.50</td>
     </tr>
@@ -2416,7 +2416,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>その他の中東認証</td>
+        <td>その他の中東の認証</td>
         <td>0.45</td>
         <td>4.50</td>
     </tr>
@@ -2542,7 +2542,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>南アフリカ・サービス</td>
+        <td>南アフリカサービス</td>
         <td>0.45</td>
         <td>4.50</td>
     </tr>
@@ -2679,7 +2679,7 @@ SMSメッセージセグメントは、SMS業界がメッセージをカウン
 
 ### MMSセグメント
 
-MMSの場合、メッセージの上限は5MBである（これにはマルチメディアアセットとメッセージ本文のサイズが含まれる）。安全面を考慮し、Brazeではメッセージ本文も含め、マルチメディア資産は600KBを超えないことを推奨している。
+MMS の場合、メッセージの上限は5 MBです (これにはマルチメディアアセットとメッセージ本文のサイズが含まれます)。安全面を考慮し、Brazeではメッセージ本文も含め、マルチメディア資産は600KBを超えないことを推奨している。
 
 ## WhatsAppチャンネルの詳細
 
@@ -2700,7 +2700,7 @@ WhatsAppは双方向のメッセージングに特化したチャンネルであ
 **サービスの会話:**テンプレート化されていないメッセージで応答されるユーザー主導の会話。
 
 {% alert note %}
-マーケティングまたはユーティリティのテンプレートで応答されたユーザー主導の会話は、そのように課金される。
+マーケティングテンプレートまたはユーティリティテンプレートで応答されたユーザーが開始した会話は、そのように課金されます。
 {% endalert %}
 
 ## 請求地域の分類
@@ -2709,7 +2709,7 @@ WhatsAppは双方向のメッセージングに特化したチャンネルであ
 
 米国、カナダ
 
-#### アフリカ
+#### アフリカのその他諸国
 
 アルジェリア、アンゴラ、ベナン、ボツワナ、ブルキナファソ、ブルンジ、カメルーン、チャド、コンゴ、エリトリア、エチオピア、ガボン、ガンビア、ガーナ、ギニアビサウ、コートジボワール、ケニア、レソト、リベリア、リビア、
 マダガスカル、マラウイ、マリ、モーリタニア、モロッコ、モザンビーク、ナミビア、ニジェール、ルワンダ、セネガル、シエラレオネ、ソマリア、南スーダン、スーダン、スワジランド、タンザニア、トーゴ、チュニジア、ウガンダ、ザンビア
diff --git a/_lang/ja/_hidden/pricing/message_credits_lambda_k5gh.md b/_lang/ja/_hidden/pricing/message_credits_lambda_k5gh.md
index a528e08781b..9a129b07981 100644
--- a/_lang/ja/_hidden/pricing/message_credits_lambda_k5gh.md
+++ b/_lang/ja/_hidden/pricing/message_credits_lambda_k5gh.md
@@ -8,14 +8,14 @@ hide_toc: true
 
 # メッセージクレジット - Lambda (機密)
 
-> メッセージクレジットは、当社の本来のSMS、MMS、およびWhatsApp製品のためのBrazeのクロスチャネルのなパッケージング構成です。Braze メッセージング チャネルsの先行タグを受講する際に、メッセージクレジットを活用し、柔軟かつ透明な体験を提供しています。このページの表に示されているすべてのチャネルで購入されたクレジットの割り当てを使用できます。
+> メッセージクレジットは、当社のネイティブな SMS、MMS、WhatsApp 製品のための、Braze のクロスチャネルのパッケージング構造です。メッセージクレジットを使用して、Braze メッセージングチャネルを利用する際に、柔軟で透明性のある体験を提供します。このページの表に示されているすべてのチャネルで購入されたクレジットの割り当てを使用できます。
 
 {% alert note %}
-チャネルs が異なれば、測定単位はレポート ing で異なります。<br><br>
+レポートの測定単位は、チャネルによって異なります。<br><br>
 <b>WhatsApp:</b>会話<br>
 <b>SMS:</b>セグメント<br>
 <b>MMS:</b>セグメント<br><br>
-つまり、WhatsApp メッセージに使用されるクレジットは対話開始時に計算され、SMS とMMS メッセージの両方に使用されるクレジットは送信されるSegmentで計算されます。
+つまり、WhatsApp メッセージに使用されるクレジットは会話の開始時に計算され、SMS と MMS メッセージの両方に使用されるクレジットは送信されたセグメントで計算されます。
 <br><br>
 最後に、通信事業者料金は別途請求され (後払い)、このメッセージクレジット SKU の一部とは見なされません。
 {% endalert %}
@@ -25,14 +25,14 @@ hide_toc: true
 列定義は次のとおりです。
 
 |---------|-------------------------------------------------|
-| **チャネルのクレジット比率** | チャネルごとの基準与信額 |
+| **チャネルのクレジット比率** | 各チャネルのベースラインクレジット量 |
 | **送信先** | Braze プラットフォームから送信されるメッセージの最終送信先の特定の地域、国、またはメッセージの種類 |
 | **乗数** | 特定の送信先の価格設定に応じたチャネルのクレジット比率の係数 |
 | **1 回の送信で使用されるクレジット** | 1 つのメッセージの送信に使用されるメッセージクレジットの正確な数<br> (メッセージあたりのクレジット = チャネルのクレジット比率 x 宛先係数）  |
 {: .reset-td-br-1 .reset-td-br-2}
 
 
-## メッセージクレジットのクレジット率テーブル- Lambda
+## メッセージクレジットのクレジット比率の表 - ラムだ
 
 {% details クリックして展開 %}
 <table>
@@ -42,10 +42,10 @@ hide_toc: true
     </colgroup>
     <tr>
         <th><b>Channel</b></th>
-        <th><b>チャネルのクレジット比率</b></th>
-        <th><b>送信先</b></th>
-        <th><b>乗数</b></th>
-        <th class="credits-column"><b>1 回の送信で使用されるクレジット</b></th>
+        <th>**チャネルのクレジット比率**</th>
+        <th>**送信先**</th>
+        <th>**乗数**</th>
+        <th class="credits-column">**1 回の送信で使用されるクレジット**</th>
     </tr>
     <tr>
         <td>SMS - US/CA</td>
@@ -512,7 +512,7 @@ hide_toc: true
     <tr>
         <td>SMS/MMS - グローバル</td>
         <td>10</td>
-        <td>コンゴDR</td>
+        <td>DR コンゴ</td>
         <td>1.48</td>
         <td>14.80</td>
     </tr>
@@ -610,7 +610,7 @@ hide_toc: true
     <tr>
         <td>SMS/MMS - グローバル</td>
         <td>10</td>
-        <td>フランスのギアナ</td>
+        <td>フランス領ギアナ</td>
         <td>2.01</td>
         <td>20.10</td>
     </tr>
@@ -2332,7 +2332,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>その他のアジアパシフィック認証</td>
+        <td>アジア太平洋地域のその他の地域の認証</td>
         <td>1.15</td>
         <td>11.50</td>
     </tr>
@@ -2416,7 +2416,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>その他の中東認証</td>
+        <td>その他の中東の認証</td>
         <td>0.45</td>
         <td>4.50</td>
     </tr>
@@ -2444,7 +2444,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>その他の西ヨーロッパ認証</td>
+        <td>西欧地域のその他諸国 認証</td>
         <td>1.00</td>
         <td>10.00</td>
     </tr>
@@ -2472,7 +2472,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>ロシア認証</td>
+        <td>ロシアの認証</td>
         <td>1.15</td>
         <td>11.50</td>
     </tr>
@@ -2556,7 +2556,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>スペイン認証</td>
+        <td>スペインの認証</td>
         <td>0.90</td>
         <td>9.00</td>
     </tr>
@@ -2584,7 +2584,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>トルコ認証</td>
+        <td>トルコの認証</td>
         <td>0.20</td>
         <td>2.00</td>
     </tr>
@@ -2675,11 +2675,11 @@ hide_toc: true
 
 ### SMSSegment
 
-SMSメッセージSegmentは、SMS産業がメッセージを数える方法です。メッセージSegmentは、単一のSMS ディスパッチで送信される、定義された文字数(GSM-7 エンコードの場合は160、UCS-2 エンコードの場合は67)までのグループです。GSM-7 エンコードを使用して161 文字のSMS を送信すると、送信されたメッセージSegmentが2 つあることがわかります。複数のメールSegmentを送信すると、追加料金が発生します。
+SMSメッセージSegmentは、SMS産業がメッセージを数える方法です。メッセージSegmentは、単一のSMS ディスパッチで送信される、定義された文字数(GSM-7 エンコードの場合は160、UCS-2 エンコードの場合は67)までのグループです。GSM-7 エンコードを使用して161 文字のSMS を送信すると、送信されたメッセージSegmentが2 つあることがわかります。複数のメッセージセグメントを送信すると、追加料金が発生します。
 
 ### MMSSegment
 
-MMSの場合、メッセージの制限は5MBです(これにはマルチメディアアセットとメッセージ本文のサイズが含まれます)。安全のために、Braze では、マルチメディアアセットには600KB を超えず、メッセージ本文も含めることをお勧めします。
+MMSの場合、メッセージの制限は5MBです(これにはマルチメディアアセットとメッセージ本文のサイズが含まれます)。Braze では、より安全な方法として、メッセージ本文を含めながら、マルチメディア資産が600 KB を超えないようにすることを推奨しています。
 
 ## WhatsApp チャネル内容
 
@@ -2689,7 +2689,7 @@ WhatsAppは、双方向のメッセージングに焦点を当てたチャネル
 
 **マーケティングの会話:**意識の喚起から販売・リターゲティング 顧客の促進まで、幅広い目標を達成できるビジネス主導の対話。たとえば、新商品、新サービス、機能のアナウンス、ターゲットを絞ったプロモーション/オファー、カート放棄のリマインダーなどです。
 
-**ユーティリティの会話:**ユーザー アクション s またはリクエストのフォローアップを可能にするビジネス開始の対話。例としては、オプトインの確認、注文/配送管理 (e.g、配送の最新情報)、アカウントのアップデートやアラート (e.g、支払いリマインダーなど)、フィードバックアンケートなどがあります。
+**ユーティリティの会話:**ユーザーのアクションまたはリクエストのフォローアップを可能にするビジネスが開始した会話。例としては、オプトインの確認、注文/配送管理 (e.g、配送の最新情報)、アカウントのアップデートやアラート (e.g、支払いリマインダーなど)、フィードバックアンケートなどがあります。
 
 **認証の会話:**ワンタイムパスコードでユーザーを認証できます。ログインプロセスの複数ステップ (e.g、アカウント認証、アカウントリカバリー、整合性チェックなど) で使用されます。
 
@@ -2697,10 +2697,10 @@ WhatsAppは、双方向のメッセージングに焦点を当てたチャネル
 認証の会話はケースバイケースでのみサポートされ、Braze は特定の SLA を保証できません。また、Brazeは暗証番号の生成に対応していません。
 {% endalert %}
 
-**サービスの会話:**テンプレート 以外のd メッセージで応答された、ユーザーが開始した会話。
+**サービスの会話:**テンプレート化されていないメッセージで応答された、ユーザーが開始した会話。
 
 {% alert note %}
-マーケティングまたはユーティリティテンプレートで応答されるユーザ起動の対話は、そのように課金されます。
+マーケティングテンプレートまたはユーティリティテンプレートで応答されたユーザーが開始した会話は、そのように課金されます。
 {% endalert %}
 
 ## 請求地域の分類
diff --git a/_lang/ja/_hidden/pricing/message_credits_theta_d9kw.md b/_lang/ja/_hidden/pricing/message_credits_theta_d9kw.md
index d8954b52fe7..abe41c723b7 100644
--- a/_lang/ja/_hidden/pricing/message_credits_theta_d9kw.md
+++ b/_lang/ja/_hidden/pricing/message_credits_theta_d9kw.md
@@ -6,35 +6,35 @@ noindex: true
 hide_toc: true
 ---
 
-# メッセージ・クレジット - シータ（コンフィデンシャル）
+# メッセージクレジット - シータ (社外秘)
 
-> メッセージクレジットは、BrazeのネイティブSMS、MMS、WhatsAppのクロスチャネルパッケージング構造である。メッセージクレジットは、Brazeのメッセージングチャネルを利用する際に、柔軟で透明性の高い体験を提供するために使用する。このページの表に示されているすべてのチャネルで購入されたクレジットの割り当てを使用できます。
+> Message Creditsは、Brazeのクロスチャネルのパッケージ構造で、ネイティブSMS、MMS、およびWhatsAppの提供に対応しています。Brazeメッセージングチャネルを利用する際に柔軟で透明性のある体験を提供するために、メッセージクレジットを使用します。このページの表に示されているすべてのチャネルで購入されたクレジットの割り当てを使用できます。
 
 {% alert note %}
-チャンネルが異なれば、報道における測定単位も異なる。<br><br>
+異なるチャネルは、報告において異なる測定単位を持つでしょう。<br><br>
 <b>WhatsApp:</b>会話<br>
 <b>SMS:</b>セグメント<br>
 <b>MMS:</b>セグメント<br><br>
-つまり、WhatsAppメッセージに使用されたクレジットは会話の開始時に計算され、SMSとMMSメッセージの両方に使用されたクレジットは送信されたセグメントで計算される。
+つまり、WhatsAppメッセージに使用されるクレジットは会話の開始時に計算され、SMSおよびMMSメッセージに使用されるクレジットは送信されたセグメントに基づいて計算されます。
 <br><br>
 最後に、通信事業者料金は別途請求され (後払い)、このメッセージクレジット SKU の一部とは見なされません。
 {% endalert %}
 
 ## 定義
 
-列の定義は以下の通りである：
+列の定義は次のとおりです:
 
 |---------|-------------------------------------------------|
-| **チャネルのクレジット比率** | 各チャンネルのベースライン・クレジット額 |
+| **チャネルのクレジット比率** | 各チャネルのベースラインクレジット額 |
 | **送信先** | Braze プラットフォームから送信されるメッセージの最終送信先の特定の地域、国、またはメッセージの種類 |
 | **乗数** | 特定の送信先の価格設定に応じたチャネルのクレジット比率の係数 |
 | **1 回の送信で使用されるクレジット** | 1 つのメッセージの送信に使用されるメッセージクレジットの正確な数<br> (メッセージあたりのクレジット = チャネルのクレジット比率 x 宛先係数） |
 {: .reset-td-br-1 .reset-td-br-2}
 
 
-## メッセージクレジットのクレジット比率表 - Theta
+## メッセージクレジットのクレジット比率の表 - シータ
 
-{% details クリックで拡大 %}
+{% details クリックして展開 %}
 <table>
     <colgroup>
         <col span="4" style="background-color:background-color:#FFFFFF;">
@@ -42,71 +42,71 @@ hide_toc: true
     </colgroup>
     <tr>
         <th><b>Channel</b></th>
-        <th><b>チャネルのクレジット比率</b></th>
-        <th><b>送信先</b></th>
-        <th><b>乗数</b></th>
-        <th class="credits-column"><b>1 回の送信で使用されるクレジット</b></th>
+        <th>**チャネルのクレジット比率**</th>
+        <th>**送信先**</th>
+        <th>**乗数**</th>
+        <th class="credits-column">**1 回の送信で使用されるクレジット**</th>
     </tr>
     <tbody><tr>
-        <td>SMS - 米国 / CA</td>
+        <td>SMS - 米国 / カナダ</td>
         <td>0.7</td>
-        <td>米国</td>
+        <td>アメリカ合衆国</td>
         <td>1.00</td>
         <td>0.70</td>
     </tr>
     <tr>
-        <td>SMS - 米国 / CA</td>
+        <td>SMS - 米国 / カナダ</td>
         <td>0.7</td>
-        <td>米国 フリーダイヤル</td>
+        <td>アメリカ合衆国のフリーダイヤル</td>
         <td>1.50</td>
         <td>1.05</td>
     </tr>
     <tr>
-        <td>SMS - 米国 / CA</td>
+        <td>SMS - 米国 / カナダ</td>
         <td>0.7</td>
         <td>カナダ</td>
         <td>1.00</td>
         <td>0.70</td>
     </tr>
     <tr>
-        <td>SMS - 米国 / CA</td>
+        <td>SMS - 米国 / カナダ</td>
         <td>0.7</td>
-        <td>カナダ・フリーダイヤル</td>
+        <td>カナダのフリーダイヤル</td>
         <td>1.30</td>
         <td>0.91</td>
     </tr>
     <tr>
-        <td>MMS - 米国 / CA</td>
+        <td>MMS - 米国 / カナダ</td>
         <td>2</td>
-        <td>米国</td>
+        <td>アメリカ合衆国</td>
         <td>1.00</td>
         <td>2.00</td>
     </tr>
     <tr>
-        <td>MMS - 米国 / CA</td>
+        <td>MMS - 米国 / カナダ</td>
         <td>2</td>
-        <td>米国 フリーダイヤル</td>
+        <td>アメリカ合衆国のフリーダイヤル</td>
         <td>2.00</td>
         <td>4.00</td>
     </tr>
     <tr>
-        <td>MMS - 米国 / CA</td>
+        <td>MMS - 米国 / カナダ</td>
         <td>2</td>
-        <td>カナダ ロングコード</td>
+        <td>カナダロングコード</td>
         <td>1.50</td>
         <td>3.00</td>
     </tr>
     <tr>
-        <td>MMS - 米国 / CA</td>
+        <td>MMS - 米国 / カナダ</td>
         <td>2</td>
-        <td>カナダ・ショートコード</td>
+        <td>カナダショートコード</td>
         <td>4.00</td>
         <td>8.00</td>
     </tr>
     <tr>
-        <td>MMS - 米国 / CA</td>
+        <td>MMS - 米国 / カナダ</td>
         <td>2</td>
-        <td>カナダ・フリーダイヤル</td>
+        <td>カナダのフリーダイヤル</td>
         <td>1.30</td>
         <td>2.60</td>
     </tr>
@@ -141,7 +141,7 @@ hide_toc: true
     <tr>
         <td>SMS / MMS - グローバル</td>
         <td>10</td>
-        <td>米領サモア</td>
+        <td>アメリカ領サモア</td>
         <td>4.74</td>
         <td>47.40</td>
     </tr>
@@ -162,7 +162,7 @@ hide_toc: true
     <tr>
         <td>SMS / MMS - グローバル</td>
         <td>10</td>
-        <td>アングィラ</td>
+        <td>アンギラ</td>
         <td>3.33</td>
         <td>33.30</td>
     </tr>
@@ -281,7 +281,7 @@ hide_toc: true
     <tr>
         <td>SMS / MMS - グローバル</td>
         <td>10</td>
-        <td>バーミューダ</td>
+        <td>バミューダ</td>
         <td>2.99</td>
         <td>29.90</td>
     </tr>
@@ -372,7 +372,7 @@ hide_toc: true
     <tr>
         <td>SMS / MMS - グローバル</td>
         <td>10</td>
-        <td>カリブ海 オランダ</td>
+        <td>カリブ海オランダ</td>
         <td>2.17</td>
         <td>21.70</td>
     </tr>
@@ -1828,7 +1828,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>チリ・サービス</td>
+        <td>チリサービス</td>
         <td>1.20</td>
         <td>12.00</td>
     </tr>
@@ -2010,7 +2010,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>インドネシア・サービス</td>
+        <td>インドネシアサービス</td>
         <td>0.50</td>
         <td>5.00</td>
     </tr>
@@ -2059,7 +2059,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>イタリア・マーケティング</td>
+        <td>イタリアマーケティング</td>
         <td>1.85</td>
         <td>18.50</td>
     </tr>
@@ -2416,7 +2416,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>その他の中東認証</td>
+        <td>その他の中東の認証</td>
         <td>0.45</td>
         <td>4.50</td>
     </tr>
@@ -2542,7 +2542,7 @@ hide_toc: true
     <tr>
         <td>WhatsApp</td>
         <td>10</td>
-        <td>南アフリカ・サービス</td>
+        <td>南アフリカサービス</td>
         <td>0.45</td>
         <td>4.50</td>
     </tr>
@@ -2679,7 +2679,7 @@ SMSメッセージセグメントは、SMS業界がメッセージをカウン
 
 ### MMSセグメント
 
-MMSの場合、メッセージの上限は5MBである（これにはマルチメディアアセットとメッセージ本文のサイズが含まれる）。安全面を考慮し、Brazeではメッセージ本文も含め、マルチメディア資産は600KBを超えないことを推奨している。
+MMS の場合、メッセージの上限は5 MBです (これにはマルチメディアアセットとメッセージ本文のサイズが含まれます)。安全面を考慮し、Brazeではメッセージ本文も含め、マルチメディア資産は600KBを超えないことを推奨している。
 
 ## WhatsAppチャンネルの詳細
 
@@ -2700,7 +2700,7 @@ WhatsAppは双方向のメッセージングに特化したチャンネルであ
 **サービスの会話:**テンプレート化されていないメッセージで応答されるユーザー主導の会話。
 
 {% alert note %}
-マーケティングまたはユーティリティのテンプレートで応答されたユーザー主導の会話は、そのように課金される。
+マーケティングテンプレートまたはユーティリティテンプレートで応答されたユーザーが開始した会話は、そのように課金されます。
 {% endalert %}
 
 ## 請求地域の分類
@@ -2709,7 +2709,7 @@ WhatsAppは双方向のメッセージングに特化したチャンネルであ
 
 米国、カナダ
 
-#### アフリカ
+#### アフリカのその他諸国
 
 アルジェリア、アンゴラ、ベナン、ボツワナ、ブルキナファソ、ブルンジ、カメルーン、チャド、コンゴ、エリトリア、エチオピア、ガボン、ガンビア、ガーナ、ギニアビサウ、コートジボワール、ケニア、レソト、リベリア、リビア、
 マダガスカル、マラウイ、マリ、モーリタニア、モロッコ、モザンビーク、ナミビア、ニジェール、ルワンダ、セネガル、シエラレオネ、ソマリア、南スーダン、スーダン、スワジランド、タンザニア、トーゴ、チュニジア、ウガンダ、ザンビア
diff --git a/_lang/ja/_hidden/private_betas/ai_step.md b/_lang/ja/_hidden/private_betas/ai_step.md
index 50953255b63..d9bece957c0 100644
--- a/_lang/ja/_hidden/private_betas/ai_step.md
+++ b/_lang/ja/_hidden/private_betas/ai_step.md
@@ -18,25 +18,25 @@ AIステップは現在ベータ機能として提供されている。このベ
 
 ## AI ステップの作成 {#create-ai-step}
  
-1. キャンバスに新しいステップを追加し、\[**AI ステップ**] を選択します。<br><br>![キャンバスビルダーのAIステップ][1]{: style="max-width: 30%;"}<br><br>
-2. ユーザーのさまざまなアクションにどのように反応するかをAIに指示するプロンプトを作成する。レスポンスには、カスタム属性の更新やメッセージの送信などがある。このプロンプトは、リキッドを使用して、異なるユーザー属性や入力に基づいて異なる応答出力を割り当てることができる。<br><br>同じキャンバス内で将来のメッセージをパーソナライズするために使用できる出力を割り当てるには、特定の名前（たとえば、"メッセージ "と "センチメントスコア"）を持つ変数を保存するプロンプトを作成する。<br><br> ![AIステップの設定で使用されるAIプロンプトのサンプルは、生成されたセンチメントスコアに基づいてパーソナライズされたメッセージを送信する。この例は、「顧客感情の反応」のセクションに記載されている。][2]<br><br>
+1. キャンバスに新しいステップを追加し、\[**AI ステップ**] を選択します。<br><br>![キャンバスビルダーの AI ステップ][1]{: style="max-width: 30%;"}<br><br>
+2. ユーザーのさまざまなアクションにどのように反応するかをAIに指示するプロンプトを作成する。応答としては、カスタム属性の更新やメッセージの送信などがあります。このプロンプトは、Liquid を使用して、異なるユーザー属性や入力に基づいて異なる応答出力を割り当てることができます。<br><br>同じキャンバス内で将来のメッセージをパーソナライズするために使用できる出力を割り当てるには、特定の名前 (たとえば、「メッセージ」と「センチメントスコア」) を持つ変数を保存するプロンプトを作成します。<br><br> ![生成されたセンチメントスコアに基づいてパーソナライズされたメッセージを送信するために AI ステップ設定で使用される AI プロンプトの例。この例は「顧客センチメント応答」セクションの下に記載されています。][2]<br><br>
 3. **プレビュー・**タブを使って、特定のユーザーに対してAIがどのような出力をするかをテストする。<br><br> ![AIステップ設定のプレビュータブに、AIが生成したパーソナライズされたメッセージが表示されている。3つのパラメーター：キャメロンというファーストネーム、シューズという商品名、そして "comfy but my shoe lace already broke "というテキスト。][3]
 
 ## Liquidを使ってAIの出力を参照する
-リキッドロジック`{% raw %}{{ai_step_output.${key_name}}}{% endraw %}` を挿入することで、後のステップでAI出力を参照する。AIステップのプロンプト内で`key_name` 。
+Liquid ロジック `{% raw %}{{ai_step_output.${key_name}}}{% endraw %}` を挿入することで、後のステップで AI 出力を参照します。AI ステップのプロンプト内に `key_name` を設定できます。
 
-例えば、変数 "message "と "sentiment score "を使えば、`{% raw %}{{ai_step_output.${message}}}{% endraw %}` 、同じCanvasの次のメッセージをパーソナライズすることができる。
+たとえば、変数「message」と「sentiment score」を使用する場合、`{% raw %}{{ai_step_output.${message}}}{% endraw %}` を使用して同じキャンバスで後続のメッセージをパーソナライズできます。
 
-また、ユーザー更新キャンバス・ステップを使用して、AIステップの出力をカスタム属性としてログに記録することもできる（例えば、`{% raw %}{{ai_step_output.${sentiment_score}}}{% endraw %}` ）。出力がカスタム属性として保存されていない場合、同じキャンバスの後続ステップ以外の場所では使用できない。
+また、AI ステップの出力を読み取るユーザー更新キャンバスステップを使用して、AI ステップの出力をカスタム属性としてログに記録することもできます (例えば、`{% raw %}{{ai_step_output.${sentiment_score}}}{% endraw %}`)。出力がカスタム属性として保存されていない場合、同じキャンバスの後続ステップ以外の場所では使用できない。
 
 ## AIステップの統計
 
 AIステップは以下のステップレベルのステータスを持つ：
 
 - **次のステップに進む：**キャンバスの次のステップに進んだユーザー数
-- **キャンバスを出た：**あなたのAIステップが最後のステップであったため、キャンバスを終了したユーザーの数
-- **出力は成功した：**AIステップが正常に出力を生成したユーザー数
-- **出力に失敗した：**AIステップが出力に失敗したユーザーの数。この場合でも、ユーザーは後続のステップに進む。
+- **終了済みのキャンバス:**AI ステップが最後のステップであったため、キャンバスを終了したユーザーの数
+- **出力に成功：**AIステップが正常に出力を生成したユーザー数
+- **出力に失敗：**AIステップが出力に失敗したユーザーの数。この場合でも、ユーザーは後続のステップに進む。
 
 ### AIステップのアウトプットを理解する
 
@@ -47,18 +47,18 @@ BrazeがAIステップの出力を破棄し、顧客を次のステップに送
 
 ## AIステップの使用例
 
-### 顧客感情の回答
+### 顧客センチメント応答
 
-[AIステップの作成](#create-ai-step)」の例で示したように、顧客フィードバックから生成されたセンチメント・スコアに基づいて、AIにフォローアップ・メッセージを送信させることができる。
+「[AI ステップの作成](#create-ai-step)」の例で示したように、顧客フィードバックから生成されたセンチメントスコアに基づいて、AI にフォローアップメッセージを送信させることができます。
 - ポジティブなセンチメントスコア - ユーザーにレビューを残すよう求めるプッシュ通知をトリガーする
 - 中程度のセンチメントスコア - 追加のヘルプが必要かをユーザーに尋ねるメールをトリガーする。
-- センチメントスコアが低い - ウェブフックをトリガーし、ユーザーヘルプデスクに通知する。
+- センチメントスコアが低い - ユーザーのヘルプデスクに通知する Webhook をトリガーして、サポート担当者が絶妙なフォローアップを作成できるようにします。
 
 #### AIプロンプトの例
 
-この例は、[AIの作成ステップで](#create-ai-step)使用した。
+この例は、「[AI ステップの作成](#create-ai-step)」で使用しました。
 
-ある顧客が"`{% raw %}{{canvas_entry_properties.${product_name}}}{% endraw %}`"を購入し、"`{% raw %}{{canvas_entry_properties.${text}}}{% endraw %}`"という商品感想を述べた。センチメントスコアを0～100の整数値で作成する。そして、パーソナライズされたメッセージを作成する。これは、"メッセージ "と "センチメント・スコア "という2つの変数を返すはずだ。
+ある顧客が"`{% raw %}{{canvas_entry_properties.${product_name}}}{% endraw %}`"を購入し、"`{% raw %}{{canvas_entry_properties.${text}}}{% endraw %}`"という商品感想を述べた。センチメントスコアを0～100の整数値で作成する。そして、パーソナライズされたメッセージを作成します。これは、「message」と 「sentiment score」という2つの変数を返すはずです。
 
 ### 調査のフォローアップ
 
@@ -68,36 +68,36 @@ BrazeがAIステップの出力を破棄し、顧客を次のステップに送
 
 #### AIプロンプトの例
 
-ユーザーの回答から好きなブランドを特定する。そして、アンケートに答えてくれたユーザーに感謝し、Beauty Expertsも彼らの好きなブランドを愛していることに言及するメッセージを作成する。これは2つの変数、"message "と "favorite brand "を返すはずだ。
+ユーザーの応答からユーザーが好きなブランドを特定する。次に、アンケートに答えてくれたユーザーに感謝し、ビューティーエキスパートも彼らのお気に入りのブランドが好きであることを伝えるメッセージを作成します。これは2つの変数、"message "と "favorite brand "を返すはずだ。
 
-![AIステップ設定のプレビュータブには、「エスティローダーのフェイスクリームが好き」というアンケートの回答パラメータに対して、AIが生成したパーソナライズされたメッセージが表示されている。][4]
+![AI ステップ設定のプレビュータブには、アンケートの回答パラメーター「Estee Lauder フェイスクリームが好きです」に対して AI が生成したパーソナライズされたメッセージが表示されます。これは、ユーザーがアンケートに記入したことに感謝し、フェイスクリームをお勧めするものです。][4]
 
 ### 行動主導の提言
 
-顧客はAIにユーザーの行動を分析し、推薦メッセージを送るよう依頼することができる。 
+顧客は AI に、ユーザーの行動を分析してレコメンデーションメッセージを送信するように指示できます。 
 
-例えば、ユーザーの最近の購入履歴50件を分析するプロンプトを作成し、最もよく購入したカテゴリーを新しいカスタム属性として設定することができる。そして、各ユーザーの好きなカテゴリーにパーソナライズされたおすすめメールを送ることができる。
+たとえば、ユーザーが最近購入した50件を分析し、最もよく購入されるカテゴリーを新しいカスタム属性として設定するプロンプトを作成できます。次に、各ユーザーのお気に入りのカテゴリに対してパーソナライズされたおすすめメールを送信できます。
 
 #### AIプロンプトの例
 
-ある顧客が次の商品を購入した： "`{% raw %}{{custom_attribute.${Products Purchased}}}{% endraw %}`".ユーザーが最も購入した商品カテゴリーを特定する。これは、"最も購入されたカテゴリー "の新しい変数を返すはずである。
+ある顧客が次の商品を購入した： "`{% raw %}{{custom_attribute.${Products Purchased}}}{% endraw %}`".ユーザーが最も購入した商品カテゴリーを特定します。これにより、「最も購入されたカテゴリー」の新しい変数が返されます。
 
 ![AIステップ設定のプレビュータブに、最も購入されたカテゴリのパラメータとしてAIが生成した変数「本」が表示されている。][5]
 
 ## レート制限
 
-1社につき毎分10リクエスト（RPM）の制限がある。つまり、どのAIステップでも、1分間に最大10人のユーザーがそのステップを受けることができ、10人を超えたユーザーは自動的に次のステップに進む。次の分が始まると、ユーザーは再びAIステップを受けることができるが、レート制限を発動した以前のユーザーは再試行されない。
+1社につき毎分10リクエスト (RPM) の制限があります。つまり、どのAIステップでも、1分間に最大10人のユーザーがそのステップを受けることができ、10人を超えたユーザーは自動的に次のステップに進む。次の分が始まると、ユーザーは再び AI ステップを受信できますが、レート制限をトリガーした以前のユーザーは再試行されません。
 
 ## AIステップの制限
 
 - この機能はGPT-3.5を活用している。
-- この機能は、Braze OpenAI APIキーを使用する。自分のOpenAI APIキーは使えない。
-- 1ワークスペースあたり毎分5リクエスト（RPM）、1社あたり10RPMの制限がある。
-- この機能はHIPAAに準拠していないため、個人を特定できる情報（PII）や保護されるべき医療情報（PHI）を送信してはならない。
+- この機能は、Braze OpenAI APIキーを使用する。自身の OpenAI API キーは使えません。
+- ワークスペースごとに1分あたり5要求 (RPM)、会社ごとに10 RPM という制限があります。
+- この機能は HIPAA に準拠していないため、顧客は個人を特定できる情報 (PII) や保護されるべき医療情報 (PHI) を送信してはいけません。
 
 ## データはどのように使用されて、OpenAI に送信されるのですか?
 
-メッセージ内容を分析して作成するために、BrazeはOpenAIのAPI Platformにプロンプトを送信する。BrazeからOpenAIに送信されるクエリはすべて匿名化される。つまり、OpenAIは、ユーザーが提供するメッセージコンテンツに一意に特定できる情報が含まれていない限り、クエリが誰から送信されたかを特定することはできない。[OpenAI の API プラットフォームコミットメント](https://openai.com/policies/api-data-usage-policies)に詳述されているように、Braze 経由で OpenAI の API に送信されたデータは、モデルのトレーニングや改善には使用されず、30日後に削除されます。[使用ポリシー](https://openai.com/policies/usage-policies)など、お客様に関連する OpenAI のポリシーを必ず順守してください。Braze は AI が生成したコンテンツに関していかなる種類の保証も行いません。 
+メッセージ内容を分析して作成するために、BrazeはOpenAIのAPI Platformにプロンプトを送信する。Braze から OpenAI に送信されるすべてのクエリは匿名化されます。つまり、提供するメッセージコンテンツに一意に識別できる情報を含めない限り、OpenAI はクエリの送信元を特定できません。[OpenAI の API プラットフォームコミットメント](https://openai.com/policies/api-data-usage-policies)に詳述されているように、Braze 経由で OpenAI の API に送信されたデータは、モデルのトレーニングや改善には使用されず、30日後に削除されます。[使用ポリシー](https://openai.com/policies/usage-policies)など、お客様に関連する OpenAI のポリシーを必ず順守してください。Braze は AI が生成したコンテンツに関していかなる種類の保証も行いません。 
 
 [1]: {% image_buster /assets/img/ai_step1.png %}
 [2]: {% image_buster /assets/img/ai_step2.png %}
diff --git a/_lang/ja/_hidden/private_betas/api_usage_dashboard.md b/_lang/ja/_hidden/private_betas/api_usage_dashboard.md
index 0ab43cadda3..e3ddc6054e2 100644
--- a/_lang/ja/_hidden/private_betas/api_usage_dashboard.md
+++ b/_lang/ja/_hidden/private_betas/api_usage_dashboard.md
@@ -3,22 +3,22 @@ nav_title: API 使用状況ダッシュボード
 article_title: API 使用状況ダッシュボード
 permalink: "/api_usage/"
 hidden: true
-description: "ここでは、API 使用ダッシュボードの概要について説明します。"
+description: "この記事では、API 使用状況ダッシュボードの概要について説明します。"
 ---
 
-# 原薬使用ダッシュボード
+# API 使用状況ダッシュボード
 
-> API 使用状況ダッシュボードを使用すると、受信REST API トラフィックをBraze に監視し、REST API の使用状況の傾向を把握し、潜在的な問題をトラブルシューティングできます。
+> API 使用状況ダッシュボードを使用すると、Braze で受信した REST API トラフィックを監視し、REST API の使用状況内のトレンドを把握し、潜在的な問題をトラブルシューティングすることができます。
 
-デフォルト ダッシュボードは、過去1 日(24 時間) のワークスペースのすべての受信REST API リクエストのビューです。ユースケースに応じて、ダッシュボード コントロールsをフィルターまたはグループトラフィックに調整し、ダッシュボードのタイムレンジを設定することもできます。
+デフォルトのダッシュボードには、過去1日 (24時間) のワークスペースのすべての受信した REST API リクエストのビューが表示されます。ユースケースに応じて、トラフィックをフィルターまたはグループ化するようにダッシュボードコントロールを調整したり、ダッシュボードの時間範囲を設定したりできます。
 
 ![]({% image_buster /assets/img/api_usage_dashboard/api_usage_dashboard.png %})
 
 ## 要約統計量
 
-- **総リクエスト数:**フィルター s およびコントロール s アプリがダッシュボードに存在する場合、現行のワークスペースに対してBraze に送信されたリクエストの総数。
-- **成功率:**Braze が`2XX` 成功レスポンスを発行した総リクエストのパーセンテージe のタグ。
-- **エラー率:**Braze が`4XX` または`5XX` エラーレスポンスを発行した総リクエストのパーセンテージe のタグ。
+- **リクエスト数の合計**ダッシュボードに適用されているフィルターとコントロールを指定して、現在のワークスペースに対して Braze に送信されたリクエストの合計数。
+- **成功率:**Braze が `2XX` 成功応答を発行したリクエストの合計の割合。
+- **エラー率:**Braze が `4XX` または `5XX` エラー応答を発行したリクエストの合計の割合。
 
 ## ダッシュボードコントロールs
 
@@ -26,24 +26,24 @@ description: "ここでは、API 使用ダッシュボードの概要につい
 
 ### フィルター
 
-フィルター s を適用して、ワークスペースのREST API トラフィックのビューを絞り込みます。使用可能なフィルターは次のとおりです。
+フィルターを適用して、ワークスペースの REST API トラフィックの表示を絞り込みます。使用可能なフィルターは次のとおりです。
 
-- 原薬エンドポイント
+- API エンドポイント
 - API キー
-- レスポンスコード
+- 応答コード
 
 ### グループデータ
 
 さまざまなデータ系列にデータをグループ化して、使用状況のさまざまなパターンを調査します。使用可能なグループ化オプションは次のとおりです。
 
-- レスポンスコードs(デフォルト)
-- 原薬エンドポイント
+- 応答コード (デフォルト)
+- API エンドポイント
 - API キー
 - 成功と失敗のみ
 
 ### 日付
 
-日付フィルターをAdjustすると、必要に応じて、より短いまたは長い時間帯が表示されます。使用可能な日付オプションは次のとおりです。
+必要に応じて、日付フィルターを調整して、表示する時間範囲を増減します。使用可能な日付オプションは次のとおりです。
 
 - 本日(デフォルト)
 - カスタム
@@ -63,6 +63,6 @@ description: "ここでは、API 使用ダッシュボードの概要につい
 
 ## 考慮事項
 
-API 使用状況ダッシュボードには、Braze が受信し、`2XX`、`4XX`、または`5XX` レスポンスを返したすべてのREST API リクエストが含まれます。これには、データ変換出力とクラウドデータ取り込み同期が含まれます。SDK通信およびユーザアップデートステップは、このダッシュボードには含まれていません。
+API 使用状況ダッシュボードには、Braze が受信し、`2XX`、`4XX`、または `5XX` 応答を返したすべての REST API リクエストが含まれます。これには、データ変換出力とクラウドデータ取り込み同期が含まれます。SDK通信およびユーザアップデートステップは、このダッシュボードには含まれていません。
 
-ダッシュボードに表示されるデータは、最近のトラフィックを表示するのに最大15 分の遅延がある場合があります。使用率が高い場合は、ダッシュボードを1 分間に4 回まで更新できます。数分待ってから、ダッシュボードを再度更新する必要があります。
+ダッシュボードに表示されるデータは、最近のトラフィックを表示するのに最大15分の遅延が生じる場合があります。使用率が高い時間帯には、1分間に最大4回ダッシュボードを更新できます。数分待ってから、ダッシュボードを再度更新する必要がある場合があります。
diff --git a/_lang/ja/_hidden/private_betas/campaign_autosave.md b/_lang/ja/_hidden/private_betas/campaign_autosave.md
index 158465a5c1d..2661f766a47 100644
--- a/_lang/ja/_hidden/private_betas/campaign_autosave.md
+++ b/_lang/ja/_hidden/private_betas/campaign_autosave.md
@@ -12,11 +12,11 @@ page_type: reference
 > Brazeでキャンペーンを構築すると、変更が自動的に保存されるようになった。そうすれば、キャンペーンの進捗が保たれていることを確認しながら、安心してキャンペーンの詳細の微調整に集中することができる。
 
 {% alert important %}
-オートセーブは現在ベータ版で、キャンペーンでのみ利用できる。このベータ版への参加に興味がある場合は、カスタマー・サクセス・マネージャーに連絡すること。
+自動保存は現在ベータ版であり、キャンペーンでのみ使用できます。このベータ版への参加に興味がある場合は、カスタマーサクセスマネージャーにお問い合わせください。
 {% endalert %}
 
 {% alert warning %}
-電子メールやアプリ内メッセージなど、フルスクリーンエディタでメッセージを編集する場合、メッセージへの変更が自動保存されない。**Doneを**選択してエディターを終了し、キャンペーンに戻ると、メッセージへの変更は次にオートセーブが発生したときに保存される。用心のため、手動でメッセージを保存することもできる。
+電子メールやアプリ内メッセージなど、フルスクリーンエディタでメッセージを編集する場合、メッセージへの変更が自動保存されない。\[**完了**] を選択してエディターを終了し、キャンペーンに戻ると、次回自動保存が発生したときにメッセージの変更が保存されます。念のため、メッセージを手動で保存することもできます。
 {% endalert %}
 
 ## その仕組み
@@ -25,7 +25,7 @@ page_type: reference
 
 キャンペーンエディターで編集したりタブを切り替えたりすると、キャンペーンは自動的に定期的に保存される。
 
-下書きキャンペーンでもアクティブキャンペーンでも、変更は下書きとして保存される。停止したキャンペーンの場合、変更は保存されるが、キャンペーンは停止したままとなる。
+下書きキャンペーンでもアクティブキャンペーンでも、変更は下書きとして保存されます。停止したキャンペーンの場合、変更は保存されるが、キャンペーンは停止したままとなる。
 
 あなたと他のユーザーがキャンペーンに変更を加えた場合、最初の変更セットが保存される。変更を保存したのが2人目の場合、キャンペーンの最新アップデートを見るにはページを更新する必要がある。
 
diff --git a/_lang/ja/_hidden/private_betas/campaign_drafts.md b/_lang/ja/_hidden/private_betas/campaign_drafts.md
index 65d95b278c8..93f82a09084 100644
--- a/_lang/ja/_hidden/private_betas/campaign_drafts.md
+++ b/_lang/ja/_hidden/private_betas/campaign_drafts.md
@@ -8,13 +8,13 @@ page_type: reference
 
 # キャンペーンの下書きを保存する
 
-> キャンペーンを作成し、ローンチする際に、アクティブなキャンペーンに編集を加え、ドラフトとして保存することもできる。
+> キャンペーンを作成して開始する際に、アクティブなキャンペーンを編集して下書きとして保存することもできます。これにより、開始前に変更を試すことができます。
 
 大規模な変更が必要なキャンペーンがある場合、その編集のためにドラフトを作成することができる。
 
 ![アクティブなキャンペーンの下書きで、アクティブなキャンペーンを表示するオプションがある。][1]
 
-アクティブなキャンペーンでこれらの変更を開始する前に、アクティブなキャンペーン内で下書きを作成し、保存し、品質チェックすることができる。これらの下書きには、下書きの変更がまだ開始されていないため、分析はありません。キャンペーンは一度に1つのドラフトしか持つことができない。
+アクティブなキャンペーン内に下書きを作成して、アクティブなキャンペーンでこれらの変更を開始する前にビルド、保存、品質チェックを行うことができます。これらの下書きには、下書きの変更がまだ開始されていないため、分析はありません。キャンペーンに含められる下書きは、一度に1つまでです。
 
 ドラフトを作成するには、以下のようにする：
 
@@ -22,10 +22,10 @@ page_type: reference
 2. 変更を加える。
 3. キャンペーンフッターにある**「下書きとして保存**」ボタンを選択する。キャンペーンの下書きが存在する間は、アクティブなキャンペーンに編集を加えることはできない。キャンペーンを更新して変更を適用することも、草稿を破棄することもできる。
 
-アクティブなキャンペーンを参照するには、アナリティクスビューからフッターの**「アクティブなキャンペーンを表示**」を選択するか、ドラフトからキャンペーンヘッダーを選択する。アクティブなキャンペーンに戻るには、アナリティクスビューまたはアクティブなキャンペーンビューから**ドラフトを編集を**選択する。
+アクティブなキャンペーンを参照するには、アナリティクスビューからフッターの**「アクティブなキャンペーンを表示**」を選択するか、ドラフトからキャンペーンヘッダーを選択する。アクティブなキャンペーンに戻るには、分析ビューまたはアクティブなキャンペーンビューから \[**下書きを編集**] を選択します。
 
 ### アプリ内メッセージの優先順位付け
 
-アプリ内メッセージの優先順位は、**「厳密な優先順位を設定**」を選択し、他のキャンペーンやキャンバスとの関連で優先順位を指定すると、（ドラフトが起動する前に）即座に更新される。
+アプリ内メッセージの優先度は、\[**厳密な優先度を設定**] を選択し、他のキャンペーンやキャンバスとの関連で優先度を指定すると、(下書きが開始される前に) 即座に更新されます。
 
 [1]: {% image_buster /assets/img/campaign_draft.png %}
\ No newline at end of file
diff --git a/_lang/ja/_hidden/private_betas/canvas_templates.md b/_lang/ja/_hidden/private_betas/canvas_templates.md
index 3ab748a07f3..4c1c2967ce9 100644
--- a/_lang/ja/_hidden/private_betas/canvas_templates.md
+++ b/_lang/ja/_hidden/private_betas/canvas_templates.md
@@ -8,7 +8,7 @@ page_type: reference
 
 # キャンバステンプレートの作成
 
-> このリファレンス記事では、キャンバスのテンプレートを作成および管理する方法について説明します。テンプレート s を使用すると、キャンバス全体の目標に合わせて簡単にカスタマイズできる一貫したフレームワークを作成することで、メッセージングを絞り込むことができます。
+> このリファレンス記事では、キャンバスのテンプレートを作成および管理する方法について説明します。テンプレートを使用すると、キャンバス全体で特定の目標に合わせて簡単にカスタマイズできる一貫したフレームワークを作成することで、メッセージングを絞り込むことができます。
 
 {% alert important %}
 現在、キャンバステンプレートは初期段階にあります。この早期アクセスへ参加することに興味がある場合は、カスタマーサクセスマネージャーにお問い合わせください。
@@ -34,7 +34,7 @@ Braze ダッシュボードで、**メッセージング**> **キャンバス**
 
 ### ステップ 1:キャンバステンプレートエディタに移動する
 
-Braze ダッシュボードで、**Templates**> **Canvas Templates** に移動します。
+Braze ダッシュボードで、\[**テンプレート**] > \[**キャンバステンプレート**] に移動します。
 
 {% alert note %}
 古いナビゲーションを使用している場合は、**Engagement** > **Templates & Media** > **Canvas Templates** の下にこのページがあります。
@@ -44,11 +44,11 @@ Braze ダッシュボードで、**Templates**> **Canvas Templates** に移動
 
 **テンプレート**を作成を選択し、キャンバスの詳細の設定を開始します。まず、キャンバステンプレートに名前を付けることから始めることができます。
 
-![たとえば、「&quot」、「Annual sale Canvas テンプレート&quot」、「&quot」、「Use for annual spring promotion&quot」という名前のキャンバステンプレートがあります。][1]
+![「毎年春のプロモーションに使用」という説明が付いた「年間販売キャンバステンプレート」という名前のキャンバステンプレートの例。][1]
 
 ### ステップ 3:テンプレートのカスタマイズ
 
-次に、[キャンバス]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-2-set-up-your-canvas)を設定してテンプレートをカスタマイズします。ユーザーs がキャンバスに入る時期を決定し、どのユーザーs がこのキャンバスに入るかを決定し、送信設定s を調整し、テンプレートのユーザージャーニーを構築できます。
+次に、[キャンバス]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-2-set-up-your-canvas)を設定してテンプレートをカスタマイズします。ユーザーがいつキャンバスに入るかを決定し、どのユーザがこのキャンバスに入るかを決定し、送信設定を調整し、テンプレートのユーザジャーニーを構築することができます。
 
 ### ステップ 4:テンプレートを保存する
 
@@ -57,14 +57,14 @@ Braze ダッシュボードで、**Templates**> **Canvas Templates** に移動
 ## カンバステンプレートの使用
 
 テンプレートを使用してキャンバスを作成するには、次の2 つの方法があります。
-- **メッセージングから**:**メッセージング**> **Canvas**に進みます。**Create Canvas**ボタンと**Use a Canvas Template**を選択します。
-- **テンプレートから**:** テンプレート s** > ** Canvas テンプレート s** に移動し、目的のテンプレートを見つけます。次に、<i class="fas fa-ellipsis-vertical"></i>メニューの後に**テンプレートを適用**を選択します。これにより、キャンバスコンポーザーにテンプレート アプリが置かれた状態で、新しいキャンバスに移動します。
+- **メッセージングから**:\[**メッセージング**] > \[**キャンバス**] に進みます。**Create Canvas**ボタンと**Use a Canvas Template**を選択します。
+- **テンプレートから**:\[**テンプレート**] > \[**キャンバステンプレート**] に移動し、目的のテンプレートを見つけます。次に、<i class="fas fa-ellipsis-vertical"></i>メニューの後に**テンプレートを適用**を選択します。これにより、キャンバス作成画面にテンプレートが適用された新しいキャンバスが表示されます。
 
 ## キャンバステンプレートの管理
 
 キャンバステンプレートは、実際のキャンバスと同様に複製およびアーカイブできます。キャンバステンプレートを編集するには、テンプレートを選択し、**<i class="fas fa-pencil-alt"></i>編集**を選択します。
 
-ワークスペースの段階で、アクセス権を更新 ユーザーして、キャンバステンプレートの作成、編集、表示、またはアーカイブを許可または制限することができます。これらの権限は、[teams]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/teams) ではまだ使用できません。
+ワークスペースレベルでは、ユーザー権限を更新して、キャンバステンプレートの作成、編集、表示、またはアーカイブのためのアクセスを許可または制限できます。これらの権限は、[teams]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/teams) ではまだ使用できません。
 
 ## よくある質問
 
@@ -74,7 +74,7 @@ Braze ダッシュボードで、**Templates**> **Canvas Templates** に移動
 
 ### Canvas ビルダーの設定s をテンプレートとして保存できますか、それともステップs のみ保存できますか? 
 
-はい。キャンバステンプレート内のキャンバスビルダに設定を保存できます。たとえば、Segment s とフィルター s の組合せを頻繁に使用する予定の場合、これらの**Target Audience** 設定 s をキャンバステンプレートの一部として保存できます。
+はい。キャンバステンプレート内のキャンバスビルダに設定を保存できます。たとえば、セグメントとフィルターの組み合わせを頻繁に使用する場合は、これらの \[**ターゲットオーディエンス**] 設定をキャンバステンプレートの一部として保存できます。
 
 [1]: {% image_buster /assets/img/canvas_template_example.png %}
 [2]: {% image_buster /assets/img/save_canvas_as_template.png %}
\ No newline at end of file
diff --git a/_lang/ja/_hidden/private_betas/csv_events.md b/_lang/ja/_hidden/private_betas/csv_events.md
index d91ecba6db3..ddd6fd3044a 100644
--- a/_lang/ja/_hidden/private_betas/csv_events.md
+++ b/_lang/ja/_hidden/private_betas/csv_events.md
@@ -2,13 +2,13 @@
 nav_title: ユーザーデータとCSVイベントをインポート
 article_title: ユーザーデータとCSVイベントをインポート
 permalink: "/csv_events/"
-description: "この記事では、CSVファイルを使用してユーザーデータをインポートする方法とカスタムイベントをインポートする方法について説明します。"
+description: "このリファレンス記事では、ユーザーデータのインポート方法と CSV ファイルを使用したカスタムイベントのインポート方法について説明します。"
 page_type: reference
 ---
 
 # ユーザーデータのインポート（CSVイベントの早期アクセス）
 
-> Braze には、次のようにユーザーデータをプラットフォームにインポートするさまざまな方法が用意されています。SDK、API、クラウドデータの取り込み、テクノロジーパートナーの統合、およびCSVファイル。この記事では、ユーザーデータのインポート方法について詳しく説明します。[カスタムイベントをCSVファイル経由でインポートする方法（早期アクセス）](#importing-custom-events)も含まれています。
+> Braze には、次のようにユーザーデータをプラットフォームにインポートするさまざまな方法が用意されています。SDK、API、クラウドデータ取り込み、テクノロジーパートナー連携、CSV ファイル。この記事では、ユーザーデータのインポート方法について詳しく説明します。[カスタムイベントをCSVファイル経由でインポートする方法（早期アクセス）](#importing-custom-events)も含まれています。
 
 {% multi_lang_include email-via-sms-warning.md %}
 
@@ -22,19 +22,19 @@ page_type: reference
 
 CSVファイルから**オーディエンス** > **ユーザーのインポート**を通じてユーザープロフィールをアップロードおよび更新できます。
 
-CSVファイルを使用したユーザーデータのインポートは、名やメールなどのユーザー属性の記録および更新に加えて、靴のサイズなどのカスタム属性もサポートしています。CSV をインポートするには、2 つの一意のユーザー識別子のいずれかを指定できます: `external_id` またはユーザーエイリアス。
+CSV ファイルを使用したユーザーデータのインポートは、靴のサイズなどのカスタム属性に加えて、名やメールアドレスなどのユーザー属性の記録と更新をサポートしています。CSV をインポートするには、2 つの一意のユーザー識別子のいずれかを指定できます: `external_id` またはユーザーエイリアス。
 
 {% alert important %}
-ユーザーインポートは、ユーザーのカスタムイベントの記録と更新もサポートしています。ユーザー属性と同様に、`external_id`、`braze_id`、または`user_alias_name`を`user_alias_label`と一緒にインポートできます。詳細については、[カスタムイベントのインポート](#importing-custom-events)を参照してください。
+ユーザーインポートは、ユーザーのカスタムイベントの記録と更新もサポートしています。ユーザー属性と同様に、`external_id`、`braze_id`、または `user_alias_label` 付きの `user_alias_name` を使用してインポートできます。詳細については、[カスタムイベントのインポート](#importing-custom-events)を参照してください。
 {% endalert %}
 
 {% alert note %}
-ユーザーを`external_id`持つユーザーと持たないユーザーの混合でアップロードする場合は、インポートごとにCSVファイルを作成する必要があります。1つのCSVファイルには`external_ids`とユーザーエイリアスの両方を含めることはできません。
+`external_id` を持つユーザーと持たないユーザーが混在する場合、それらのユーザーの種類別に CSV ファイルを作成してアップロードする必要があります。1つのCSVファイルには`external_ids`とユーザーエイリアスの両方を含めることはできません。
 {% endalert %}
 
 ### external ID を使用するインポート
 
-顧客データをインポートする場合、各顧客の一意の識別子 (`external_id` とも呼ばれる) を指定する必要があります。CSVインポートを開始する前に、開発チームからBrazeでユーザーがどのように識別されるかを理解することが重要です。通常、これは内部データベースIDです。これは、モバイルおよびWeb上のBraze SDKによってユーザーがどのように識別されるかと一致する必要があり、各顧客がデバイス間でBraze内に単一のユーザープロファイルを持つように設計されています。Brazeの\[ユーザープロファイルライフサイクル][13]について詳しく読む。
+顧客データをインポートする場合、各顧客の一意の識別子 (`external_id` とも呼ばれる) を指定する必要があります。CSV インポートの開始前に、Braze によるユーザーの識別方法を開発チームから聞いて理解しておくことが重要です。通常、これは内部データベースIDです。これは、モバイルと Web で Braze SDK がユーザーを識別する方法と一致する必要があり、各顧客がデバイスを問わず Braze 内で単一のユーザープロファイルを持つように設計されています。詳細については、Braze の「\[ユーザープロファイルのライフサイクル][13]」を参照してください。
 
 インポートで `external_id` を指定すると、Braze は、同じ `external_id` を持つ既存のユーザーを更新します。`external_id` が見つからない場合は、その external_id を持つ新規ユーザーを作成します。
 
@@ -52,8 +52,8 @@ CSVファイルを使用したユーザーデータのインポートは、名
 
 | user_alias_name | user_alias_label | last_name | email | sample_attribute |
 | --- | --- | --- | --- | --- |
-| 182736485 | my_alt_identifier | スミス | smith@user.com | TRUE |
-| 182736486 | my_alt_identifier | グエン | nguyen@user.com | FALSE |
+| 182736485 | my_alt_identifier | Smith | smith@user.com | TRUE |
+| 182736486 | my_alt_identifier | Nguyen | nguyen@user.com | FALSE |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 インポート時に `user_alias_name` と`user_alias_label` の両方を指定すると、Braze は同じ `user_alias_name` と`user_alias_label` を使用して既存のユーザーを更新します。ユーザーが見つからない場合、Braze はその `user_alias_name` を設定して新規ユーザーを作成します。
@@ -63,11 +63,11 @@ CSVファイルを使用したユーザーデータのインポートは、名
 {% endalert %}
 
 - **ダウンロード:** \[CSV エイリアス属性インポートテンプレート]\[template_alias_attributes]
-- **ダウンロード:** \[CSV エイリアス イベント インポート テンプレート]\[\[template_alias_events]
+- **ダウンロード:** \[CSV エイリアスイベントインポートテンプレート]\[template_alias_events]
 
 ### Braze ID を使用するインポート
 
-内部のBraze ID値を使用してBrazeで既存のユーザープロファイルを更新するには、`external_id`または`user_alias_name`および`user_alias_label`の代わりに、列ヘッダーとして`braze_id`を指定します。
+`external_id` または `user_alias_name` および `user_alias_label` 値の代わりに内部 Braze ID 値を使用して、Braze の既存のユーザープロファイルを更新するには、列のヘッダーとして `braze_id` を指定します。
 
 これは、セグメンテーション内のCSVエクスポートオプションを使用してBrazeからユーザーデータをエクスポートし、既存のユーザーに新しいカスタム属性を追加したい場合に役立ちます。
 
@@ -84,39 +84,39 @@ BrazeダッシュボードからのCSVエクスポートでは、`braze_id`値
 ユーザーのデフォルト属性をインポートするには、**ユーザーのインポート** > **属性** に移動します。デフォルトのユーザー属性は Braze の予約キーです。`first_name`、`email` などがあります。カスタム属性は、お客様のビジネスに合わせてカスタマイズされます。例えば、旅行予約アプリには、`last_destination_searched` というカスタム属性を作成できます。
 
 {% alert important %}
-属性として顧客データをインポートする場合、使用する列ヘッダーはデフォルトのユーザー属性のスペルと大文字小文字が完全に一致している必要があります。一致しない場合、Braze は自動的にそのユーザープロファイルにカスタム属性を作成します。
+顧客データを属性としてインポートするときに、使用する列ヘッダーは、デフォルトのユーザー属性と正確に一致する必要があります (スペル、大文字小文字の区別)。一致しない場合、Braze は自動的にそのユーザープロファイルにカスタム属性を作成します。
 {% endalert %}
 
 #### デフォルトのユーザーデータ列のヘッダー
 
 | ユーザープロファイル フィールド | データ型 | 情報 | 必須 |
 |---|---|---|---|
-| `external_id` | string | 顧客のためのユニークなユーザー識別子。 | はい、[次のメモを見てください](#about-external-ids)。 |
-| `user_alias_name` | string | 匿名ユーザーのユニークなユーザー識別子。別の`external_id`。 | いいえ、[次のメモを参照してください](#about-external-ids)。 |
+| `external_id` | string | 顧客固有のユーザー識別子 | はい。[次の注記](#about-external-ids)を参照してください。 |
+| `user_alias_name` | string | 匿名ユーザーの一意のユーザー識別子。別の`external_id`。 | いいえ、[次のメモを参照してください](#about-external-ids)。 |
 | `user_alias_label` | string | ユーザーのエイリアスをグループ化するための一般的なラベル。 | はい、`user_alias_name`が使用されている場合。 |
-| `first_name` | string | ユーザーが示した名前（例えば、`Jane`）。 | いいえ |
-| `last_name` | string | ユーザーが示した姓（例えば、`Doe`）。 | いいえ |
-| `email` | string | ユーザーが示したメール（例えば、`jane.doe@braze.com`）です。 | いいえ |
+| `first_name` | string | ユーザーが指定したユーザーの名 (例: `Jane`)。 | いいえ |
+| `last_name` | string | ユーザーが指定したユーザーの姓 (例: `Doe`)。 | いいえ |
+| `email` | string | ユーザーが指定したユーザーのメール (例: `jane.doe@braze.com`)。 | いいえ |
 | `country` | string | 国コードは、ISO-3166-1アルファ2標準（例えば、`GB`）でBrazeに渡す必要があります。 | いいえ |
 | `dob` | string | "YYYY-MM-DD"の形式で渡す必要があります（例：`1980-12-21`）。これにより、ユーザーの生年月日がインポートされ、「今日」が誕生日のユーザーをターゲットにすることができます。 | いいえ |
 | `gender` | string | 「M」、「F」、「O」（その他）、「N」（該当なし）、「P」（言いたくない）、またはnil（不明）。 | いいえ |
-| `home_city` | string | ユーザーが示したホーム市区町村（例えば、`London`）。 | いいえ |
-| `language` | string | 言語はISO-639-1標準（例：`en`）でBrazeに渡す必要があります。<br>受け入れ可能な言語のリスト][1]をご参照ください。 | いいえ |
-| `phone` | string | ユーザーが示した電話番号は、`E.164`形式（例えば、`+442071838750`）です。<br> フォーマットのガイダンスについては\[ユーザー電話番号][2]を参照してください。 | いいえ |
+| `home_city` | string | ユーザーが示したユーザーの自宅の市区町村 (例えば、`London`)。 | いいえ |
+| `language` | string | 言語はISO-639-1標準（例：`en`）でBrazeに渡す必要があります。<br>\[受け入れ可能な言語のリスト][1] を参照してください。 | いいえ |
+| `phone` | string | ユーザーが指定した電話番号。`E.164` 形式 (`+442071838750` など)。<br> フォーマットのガイダンスについては\[ユーザー電話番号][2]を参照してください。 | いいえ |
 | `email_open_tracking_disabled` | ブール値 | true または false が受け入れられます。 このユーザーに送信されるすべての将来のメールに開封トラッキングピクセルが追加されないようにするには、trueに設定します。   | いいえ |
 | `email_click_tracking_disabled` | ブール値 | true または false が受け入れられます。 将来のメール内のすべてのリンクに対するクリックトラッキングを無効にするには、trueに設定します。このユーザーに送信されます。 | いいえ |
-| `email_subscribe` | string | 利用可能な値は、`opted_in`（メールメッセージの受信を明示的に登録）、`unsubscribed`（メールメッセージの受信を明示的にオプトアウト）、および`subscribed`（オプトインもオプトアウトもしていない）です。 | いいえ |
-| `push_subscribe` | string | 利用可能な値は`opted_in`（プッシュメッセージを受信するように明示的に登録されている）、`unsubscribed`（プッシュメッセージの受信を明示的にオプトアウトしている）、および`subscribed`（オプトインもオプトアウトもしていない）です。 | いいえ |
+| `email_subscribe` | string | 使用できる値は、`opted_in` (メールメッセージの受信を明示的に登録)、`unsubscribed` (メールメッセージの受信を明示的に拒否)、`subscribed` (明示的に登録も拒否もしていない) です。 | いいえ |
+| `push_subscribe` | string | 使用できる値は、`opted_in` (プッシュメッセージの受信を明示的に登録)、`unsubscribed` (プッシュメッセージの受信を明示的に拒否)、`subscribed` (登録も拒否もしていない) です。 | いいえ |
 | `time_zone` | string | タイムゾーンは、IANAタイムゾーンデータベース（例えば、`America/New_York` または `Eastern Time (US & Canada)`）と同じ形式で Braze に渡す必要があります。  | いいえ |
 | `date_of_first_session`<br><br> `date_of_last_session`| string | 次のISO-8601形式のいずれかで渡される場合があります: {::nomarkdown}<ul> <li> 「YYYY-MM-DD」 </li> <li> 「YYYY-MM-DDTHH:MM:SS+00:00」 </li> <li> 「YYYY-MM-DDTHH:MM:SSZ」 </li> <li> 「YYYY-MM-DDTHH:MM:SS」(2019-11-20T18:38:57 など) </li> </ul> {:/} | いいえ |
 | `subscription_group_id` | string | サブスクリプショングループの`id`。この識別子は、ダッシュボードのサブスクリプショングループページにあります。 | いいえ |
-| `subscription_state` | string | 指定された`subscription_group_id`のサブスクリプショングループのサブスクリプション状態。許可される値は `unsubscribed`（サブスクリプショングループに含まれていない）または `subscribed`（サブスクリプショングループに含まれている）です。 | いいえ、しかし`subscription_group_id`が使用されている場合は強くお勧めします。 |
+| `subscription_state` | string | `subscription_group_id` で指定されたサブスクリプショングループのサブスクリプション状態。許可される値は `unsubscribed`（サブスクリプショングループに含まれていない）または `subscribed`（サブスクリプショングループに含まれている）です。 | いいえ、しかし`subscription_group_id`が使用されている場合は強くお勧めします。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ##### 外部IDについて
 
 `external_id`は必須ではありませんが、**必ず**これらのフィールドのいずれかを含める必要があります: 
-- `external_id`: 顧客のための一意のユーザー識別子、**または**
+- `external_id`: 顧客の一意のユーザー識別子、**または**
 - `braze_id`: 既存のBrazeユーザーのために取得された一意のユーザー識別子、**または**
 - `user_alias_name` と `user_alias_label` :匿名ユーザーの一意のユーザー識別子
 
@@ -141,7 +141,7 @@ BrazeダッシュボードからのCSVエクスポートでは、`braze_id`値
 
 ### サブスクリプショングループのステータスの更新
 
-ユーザーをメールまたはSMSサブスクリプショングループにユーザーインポートを通じて追加できます。これは特にSMSに役立ちます。なぜなら、ユーザーがSMSチャネルでメッセージを受信するには、SMSサブスクリプショングループに登録されている必要があるからです。詳細については、[SMS サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/#subscription-group-mms-enablement)を参照してください。
+ユーザーをメールまたはSMSサブスクリプショングループにユーザーインポートを通じて追加できます。これは特に SMS で便利です。SMS チャネルでメッセージを受信するには、ユーザーが SMS サブスクリプショングループに登録されていなければならないためです。詳細については、[SMS サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/#subscription-group-mms-enablement)を参照してください。
 
 サブスクリプショングループのステータスを更新する場合、CSV に以下の 2 列が必要です。
 
@@ -182,7 +182,7 @@ BrazeダッシュボードからのCSVエクスポートでは、`braze_id`値
 ユーザーインポートでは、1 行につき `subscription_group_id` を 1 つのみ設定できます。異なる行に異なる `subscription_group_id` の値を設定できます。ただし、同じユーザーを複数のサブスクリプショングループに登録する必要がある場合は、複数のインポートを行う必要があります。
 {% endalert %}
 
-### カスタムイベントのインポート（早期アクセス） {#importing-custom-events}
+### カスタムイベントのインポート (早期アクセス） {#importing-custom-events}
 
 {% alert important %}
 カスタムイベントのインポートは現在早期アクセス中です。早期アクセスに参加したい場合は、Brazeのアカウントマネージャーに連絡してください。
@@ -190,7 +190,7 @@ BrazeダッシュボードからのCSVエクスポートでは、`braze_id`値
 
 ユーザーのカスタムイベントをインポートするには、**ユーザーのインポート** > **イベント**に移動します。
 
-カスタムイベントはあなたのビジネスにカスタムされています。例えば、ストリーミングアプリにはrented_movieというカスタムイベントがあるかもしれません。あなたのCSVには次の列ヘッダーが必要です：
+カスタムイベントは、お客様のビジネスに合わせてカスタマイズされます。例えば、ストリーミングアプリにはrented_movieというカスタムイベントがあるかもしれません。あなたのCSVには次の列ヘッダーが必要です：
 
 - 次のいずれか:
   - `external_id`、**または**
@@ -199,30 +199,30 @@ BrazeダッシュボードからのCSVエクスポートでは、`braze_id`値
 - 名前
 - 時刻
 
-カスタムイベントにはイベントプロパティが含まれる場合があります。例えば、カスタムイベントrented_movieには、タイトルとジャンルのプロパティが含まれる場合があります。これらのイベントプロパティには、`<event_name>.properties.<property name>`の列ヘッダーが必要です。例は`rented_movie.properties.title`です。
+カスタムイベントにはイベントプロパティが含まれる場合があります。例えば、カスタムイベントrented_movieには、タイトルとジャンルのプロパティが含まれる場合があります。これらのイベントプロパティには、列ヘッダー`<event_name>.properties.<property name>` が必要です。例は`rented_movie.properties.title`です。
 
 | ユーザープロファイル フィールド                      | データ型 | 情報                                                                                                                                                                                                             | 必須                                                                                        |
 |-----------------------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|
-| `external_id`                           | string    | あなたのユーザーのための一意のユーザー識別子。                                                                                                                                                                                 | はい、`external_id`、`braze_id`、`user_alias_name`のいずれかと`user_alias_label`が必要です。 |
-| `braze_id`                              | string    | あなたのユーザーのために割り当てられたBraze識別子。                                                                                                                                                                              | はい、`external_id`、`braze_id`、`user_alias_name`のいずれかと`user_alias_label`が必要です。 |
-| `user_alias_name`                       | string    | 匿名ユーザーのユニークなユーザー識別子。外部IDの代替案。                                                                                                                                        | はい、`external_id`、`braze_id`、`user_alias_name`のいずれかと`user_alias_label`が必要です。 |
-| `user_alias_label`                      | string    | ユーザーのエイリアスをグループ化するための一般的なラベル。                                                                                                                                                                          | はい、`external_id`、`braze_id`、`user_alias_name`のいずれかと`user_alias_label`が必要です。 |
+| `external_id`                           | string    | あなたのユーザーのための一意のユーザー識別子。                                                                                                                                                                                 | はい、`external_id`、`braze_id`、`user_alias_name` のいずれかと `user_alias_label` が必要です。 |
+| `braze_id`                              | string    | あなたのユーザーのために割り当てられたBraze識別子。                                                                                                                                                                              | はい、`external_id`、`braze_id`、`user_alias_name` のいずれかと `user_alias_label` が必要です。 |
+| `user_alias_name`                       | string    | 匿名ユーザーの一意のユーザー識別子。外部IDの代替案。                                                                                                                                        | はい、`external_id`、`braze_id`、`user_alias_name` のいずれかと `user_alias_label` が必要です。 |
+| `user_alias_label`                      | string    | ユーザーのエイリアスをグループ化するための一般的なラベル。                                                                                                                                                                          | はい、`external_id`、`braze_id`、`user_alias_name` のいずれかと `user_alias_label` が必要です。 |
 | `name`                                  | string    | ユーザーのカスタムイベント。                                                                                                                                                                                           | はい                                                                                             |
 | `time`                                  | string    | イベントの時間。次のISO-8601形式のいずれかで渡される場合があります: {::nomarkdown}<ul> <li> 「YYYY-MM-DD」 </li> <li> 「YYYY-MM-DDTHH:MM:SS+00:00」 </li> <li> 「YYYY-MM-DDTHH:MM:SSZ」 </li> <li> 「YYYY-MM-DDTHH:MM:SS」(2019-11-20T18:38:57 など) </li> </ul> {:/} | はい                                                                                             |
 | `<event name>.properties.<property name>` | 複数  | カスタムイベントに関連付けられたイベントプロパティ。例は`rented_movie.properties.title`です                                                                                                                        | いいえ                                                                                              |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 {% alert note %}
-外部ID自体は必須ではありませんが、次のいずれかのフィールドを含める必要があります:<br>- `external_id`: 顧客固有のユーザー識別子 <br>- `braze_id`: 既存の Braze ユーザーについて取得される一意のユーザー識別子 <br>- `user_alias_name`: 匿名ユーザーの一意のユーザー識別子
+external_id 自体は必須ではありませんが、次のいずれかのフィールドを含める必要があります。<br>- `external_id`: 顧客固有のユーザー識別子 <br>- `braze_id`: 既存の Braze ユーザーについて取得される一意のユーザー識別子 <br>- `user_alias_name`: 匿名ユーザーの一意のユーザー識別子
 {% endalert %}
 
 #### CSVサイズ
 
-Brazeは、500 MBまでのファイルから標準CSV形式のユーザーデータを受け付けます。CSVファイルテンプレートの1つをダウンロードするには、[external IDを使用したインポート](#importing-with-external-id)または[ユーザーエイリアスを使用したインポート](#importing-with-user-alias)を参照してください。
+Braze は、最大500 MB のファイルから標準 CSV 形式のユーザーデータを受け入れます。CSVファイルテンプレートの1つをダウンロードするには、[external IDを使用したインポート](#importing-with-external-id)または[ユーザーエイリアスを使用したインポート](#importing-with-user-alias)を参照してください。
 
 #### データポイントの考慮事項
 
-CSV経由でインポートされた各顧客データは、ユーザープロファイルの既存の値を上書きし、外部IDおよび空白の値を除き、データポイントとしてカウントされます。
+CSV を使用してインポートされた各顧客データは、ユーザープロファイルの既存の値を上書きし、external ID および空白の値を除き、1データポイントとしてカウントされます。
 
 - CSVインポートを介してアップロードされた外部IDは、データポイントを消費しません。外部IDのみをアップロードして既存のBrazeユーザーをSegmentするためにCSVファイルをアップロードする場合、データポイントを消費せずにこれを行うことができます。インポートにユーザーのメールや電話番号などの追加データを追加すると、既存のユーザーデータが上書きされ、データポイントが消費されます。
     - セグメンテーション目的のCSVインポート（唯一のフィールドとして`external_id`、`braze_id`、または`user_alias_name`を使用して行われたインポート）は、データポイントを消費しません。
@@ -236,7 +236,7 @@ CSVインポートまたはAPIを介してユーザーの言語や国を設定
 ## CSV のインポート
 
 CSVファイルをインポートするには:
-1. **オーディエンス** > **ユーザーをインポート**に移動します。 
+1. \[**オーディエンス**] > \[**ユーザーをインポート**] に移動します。 
 2. **ファイルを参照**を選択して、目的のファイルを選択し、**インポートを開始**を選択します。Braze によりファイルがアップロードされ、列ヘッダー、および各列のデータ型がチェックされます。
 
 {% alert important %}
@@ -255,7 +255,7 @@ CSV インポートでは大文字と小文字が区別されます。つまり
 
 インポートプロセスがエラーに遭遇すると、ファイル内の行の総数の横に警告アイコンが表示されます。アイコンにカーソルを合わせると、特定の行が失敗した理由の詳細が表示されます。インポートが完了すると、すべてのデータが既存のプロファイルに追加されるか、新規プロファイルが作成されます。
 
-![CSVファイルのアップロードは、単一の列に混在するデータ型に関するエラーで完了しました][4]{: style="max-width:70%"}
+![CSV のアップロードが完了しましたが、ある列でデータ型が混在しているエラーが発生しました][4]{: style="max-width:70%"}
 
 ### 考慮事項
 
@@ -318,7 +318,7 @@ Braze では、列の各値が同じデータ型である必要があります
 \[events_template]: {% image_buster /assets/download_file/braze-csv-events-import-template.csv %}
 \[template_alias_attributes]: {% image_buster /assets/download_file/braze-user-import-alias-template-csv.xlsx %}
 \[template_alias_events]: {% image_buster /assets/download_file/braze-events-csv-example-user-alias.csv %}
-エラー]:#一般的なエラー
+\[errors]:#common-errors
 [1]: {{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/language_codes/
 [2]: {{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/
 [12]: {{site.baseurl}}/api/endpoints/user_data/post_user_track/
diff --git a/_lang/ja/_hidden/private_betas/dashboard_builder.md b/_lang/ja/_hidden/private_betas/dashboard_builder.md
index b7c4e4627b1..2df91bc188b 100644
--- a/_lang/ja/_hidden/private_betas/dashboard_builder.md
+++ b/_lang/ja/_hidden/private_betas/dashboard_builder.md
@@ -2,66 +2,66 @@
 nav_title: ダッシュボードビルダー
 article_title: ダッシュボードビルダー
 permalink: "/dashboard_builder/"
-description: "このリファレンス記事では、ダッシュボードビルダを使用して、クエリビルダで作成されたレポートを使用してダッシュボードおよびビジュアライゼーションを作成する方法について説明します。"
+description: "このレファレンス記事では、ダッシュボードビルダーを使用して、クエリビルダーで作成されたレポートを使用してダッシュボードとビジュアライゼーションを作成する方法について説明します。"
 page_type: reference
 hidden: true
 ---
 
 # ダッシュボードビルダー
 
-> ダッシュボードビルダを使用して、クエリビルダで作成されたレポートを使用してダッシュボードとビジュアライゼーションを作成します。Query Builderの組み込みSQLクエリテンプレートの使用を開始するか、独自のカスタムSQLクエリを作成して、さらに多くのインサイトをアンロックすることができます。
+> ダッシュボードビルダーを使用して、クエリビルダーで作成されたレポートを使用してダッシュボードとビジュアライゼーションを作成します。Query Builderの組み込みSQLクエリテンプレートの使用を開始するか、独自のカスタムSQLクエリを作成して、さらに多くのインサイトをアンロックすることができます。
 
 Braze では、ラストタッチアトリビューションを使用した収益の解析など、頻繁にユースケースするためのダッシュボード テンプレートs が事前に構築されています。テンプレート ダッシュボードをエディットする機能はまだ使用できません。
 
 {% alert note %}
-Dashboard Builder は現在初期アクセス中です。この早期アクセスへ参加することに興味がある場合は、カスタマーサクセスマネージャーにお問い合わせください。
+ダッシュボードビルダーは現在早期アクセス段階です。この早期アクセスへ参加することに興味がある場合は、カスタマーサクセスマネージャーにお問い合わせください。
 {% endalert %}
 
 ## ダッシュボード テンプレートの実行
 
-1. **Analytics**> **Dashboard Builder**に移動します。ホームページには、ワークスペース内に存在するすべてのダッシュボードが一覧表示され、Braze作成されたテンプレートs が一番上に表示されます。これらは、タイトルに"(Braze)"と表示されます。
+1. **Analytics**> **Dashboard Builder**に移動します。ホームページには、ワークスペース内に存在するすべてのダッシュボードが一覧表示され、Braze作成されたテンプレートs が一番上に表示されます。これらは、タイトルでは「(Braze)」で表されます。
 2. 関心のあるダッシュボードを選択します。
 3. **ダッシュボード**を実行を選択して、そのテンプレートを使用してダッシュボードを生成します。
 
 ### 利用可能なダッシュボード テンプレート
 
-#### 売上- ラストタッチ属性
+#### 売上 - 前回のタッチのアトリビューション
 
-**Revenue - Last Touch Attribution** テンプレートでは、キャンペーンs、キャンバス、およびチャネルs 全体の収益を確認できます。すべての収益データは、アトリビューションウィンドウ中に最後にタッチされたメッセージに属性されます。
+**Revenue - Last Touch Attribution** テンプレートでは、キャンペーンs、キャンバス、およびチャネルs 全体の収益を確認できます。すべての収益データは、アトリビューション期間中に最後にタッチされたメッセージに関連付けられます。
 
-タッチには、`Email Click`、`Content Card Click`、`In-App Message Click`、`SMS Delivery`、`WhatsApp Read`、`Webhook Send`などがあります。
+タッチには、`Email Click`、`Content Card Click`、`In-App Message Click`、`SMS Delivery`、`WhatsApp Read`、`Webhook Send` などがあります。
 
-| メトリクス | 定義 |
+| 指標 | 定義 |
 | --- | --- |
-| ラストタッチ収益合計 | 選択した日付範囲とアトリビューションウィンドウ内のラストタッチイベントを含む、すべてのキャンペーンとキャンバスの収益イベントの合計。 |
-| 購入換算合計 | 対象となるラストタッチイベントを含む、すべてのキャンペーンおよびキャンバスの収益イベントの数。 |
-| 平均変換日数 | すべてのキャンペーンとキャンバスが、対象となるラストタッチイベントを使用してイベントを購入するまでの平均的な期間。 |
-| 受信者あたりの収益 | 適格収益イベントからの収益の合計を、日付範囲内でメッセージを受信した一意のユーザーの数で除算します。 |
-| 独自の購入者 | 修飾された収益事象を持つ一意のユーザーs の数。 |
+| ラストタッチ収益合計 | 選択された日付範囲およびアトリビューション期間内にラストタッチイベントがあるすべてのキャンペーンおよびキャンバスの収益イベントの合計。 |
+| 購入コンバージョンの合計 | 対象となるラストタッチイベントを含む、すべてのキャンペーンおよびキャンバスの収益イベントの数。 |
+| コンバージョンまでの平均日数 | 対象のラストタッチイベントを含むすべてのキャンペーンおよびキャンバス購入イベント間の平均時間。 |
+| 受信者あたりの収益 | 対象収益イベントの収益合計を、日付範囲内にメッセージを受信した一意のユーザー数で割った値。 |
+| 一意の購入者 | 対象収益イベントがある一意のユーザーの数。 |
 | 国別売上高 | 国別にグループ化された、ラストタッチイベントを含むすべてのキャンペーンおよびキャンバスの収益イベントの合計。 |
 | キャンペーン別売上高 | キャンペーン別にグループ化された、すべてのキャンペーンおよびキャンバスの収益イベントと、該当するラストタッチイベントの合計。 |
 | キャンペーンバリアント別売上高 | キャンペーン バリアント別にグループ化された、すべてのキャンペーンおよびキャンバスの収益イベントと、該当するラストタッチイベントの合計。 |
 | キャンバス別売上高 | キャンバス別にグループ化された、すべてのキャンペーンおよびキャンバスの収益イベントの合計と、該当するラストタッチイベントの合計。 |
-| キャンバスバリアント別売上高 | キャンバスバリアント別にグループ化された、すべてのキャンペーンとキャンバスの収益イベントの合計と、対象となるラストタッチイベントの合計。 |
-| 商品1個当たりの購入金額 | 製品ごとにグループ化されたすべての購入のカウント。 |
+| キャンバスバリアント別売上高 | 対象のラストタッチイベントを含むすべてのキャンペーンおよびキャンバス収益イベントの合計 (キャンバスバリアント別にグループ化)。 |
+| 製品あたりの購入数 | 製品別にグループ化されたすべての購入数。 |
 | チャネル別売上収益 | チャネル別にグループ化された、すべてのキャンペーンおよびキャンバスの収益イベントと、該当するラストタッチイベントの合計。 | 
-| 収益の時系列 | すべてのキャンペーンとキャンバスの収益イベントの合計と、UTC で日別にグループ化された、適切なラストタッチイベント。 |
+| 収益の時系列 | 対象のラストタッチイベントを含むすべてのキャンペーンおよびキャンバス収益イベントの合計 (UTC 日付別にグループ化)。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-#### デバイスおよびキャリア
+#### デバイスと通信事業者
 
-| メトリクス | 定義 |
+| 指標 | 定義 |
 | --- | --- |
-| デバイスキャリア | デバイスキャリアごとにグループ化された、プッシュ通知を開封した選択された日付範囲内のユーザーs の数。 |
+| デバイスの通信事業者 | 選択した日付範囲にプッシュ通知を開封したユーザの数 (デバイスの通信事業者別にグループ化)。 |
 | デバイスモデル | デバイスモデル別にグループ化された、プッシュ通知を開封した選択された日付範囲内のユーザーs の数。 |
 | デバイスオペレーティングシステム | プッシュ通知を開封した選択された日付範囲のユーザーの数(機器オペレーティングシステム別にグループ化)。 |
-| デバイス画面サイズ | プッシュ通知を開封した、選択した日付範囲のユーザーs の数を、機器の画面再ソリューション(サイズ)別にグループ化します。 |
+| デバイス画面サイズ | 選択した日付範囲内にプッシュ通知を開封したユーザーの数 (デバイス画面の解像度 (サイズ) 別にグループ化)。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## カスタマイズしたダッシュボードの作成
 
-1. **ダッシュボード**を作成するか、既存のダッシュボードと**編集**を選択します。**\+ Add Tile**を選択します。
-2. **Select Existing Query**を選択し、Query Builderで実行したクエリを選択します。
+1. **ダッシュボード**を作成するか、既存のダッシュボードと**編集**を選択します。\[**\+ タイルを追加**] を選択します。
+2. \[**既存のクエリの選択**] を選択し、クエリビルダーで実行したクエリを選択します。
 3. タイルでのクエリー結果の表示方法を編集するには、鉛筆アイコンを選択してタイトルとグラフの種類を変更します。<br><br>![タイトルとチャートの種類を変更するオプションを含むタイルエディタビュー。][2]{: style="max-width:60%;"}<br><br>
     - **Column**、**Bar**、または**Line**のチャートタイプを選択した場合:
         - X 軸で使用するフィールドをクエリーから選択します。
@@ -69,13 +69,13 @@ Dashboard Builder は現在初期アクセス中です。この早期アクセ
 
 {: start="4"}        
 4\.変更を保存してください。タイルを削除する場合は、ごみ箱アイコンを選択します。削除したタイルは元に戻せず、再作成する必要があります。
-5. 右下隅をドラッグしてタイルサイズをAdjustし、右上隅のハンドルをドラッグしてダッシュボード上のタイル位置をドラッグします。<br><br>![ハンドルでドラッグするタイル。][3]<br><br>
+5. 右下隅をドラッグしてタイルのサイズを調整し、右上隅のハンドルをドラッグしてダッシュボード上のタイルの位置を調整します。<br><br>![タイルがハンドルでドラッグされています。][3]<br><br>
 6. ダッシュボードが完了するまで、タイルを追加します。
-7. **Dashboard**を選択し、**Dashboard**を実行します。ダッシュボードがレポートs の生成を完了するまでに数分かかる場合があります。
+7. \[**ダッシュボードを表示**] を選択し、\[**ダッシュボードを実行**] を選択します。ダッシュボードがレポートの生成を完了するまでに数分かかる場合があります。
 
 ## フィードバックを共有する
 
-顧客のサクセスマネージャーに連絡するか、受け取ったイネーブルメント メールに返信することで、ごフィードバックをお気軽にお伝えください。
+カスタマーサクセスマネージャーに連絡するか、受け取ったイネーブルメントメールに返信して、お気軽にフィードバックをお寄せください。
 
 [1]: {% image_buster /assets/img/chart_type.png %}
 [2]: {% image_buster /assets/img/sample_tile.png %}
diff --git a/_lang/ja/_hidden/private_betas/dnd_content_blocks_preview.md b/_lang/ja/_hidden/private_betas/dnd_content_blocks_preview.md
index 04c8b8f5be9..f0215cfc350 100644
--- a/_lang/ja/_hidden/private_betas/dnd_content_blocks_preview.md
+++ b/_lang/ja/_hidden/private_betas/dnd_content_blocks_preview.md
@@ -1,26 +1,26 @@
 ---
-nav_title: ドラッグ＆ドロップ・エディターのコンテンツ・ブロックをプレビューする
+nav_title: ドラッグ＆ドロップエディターのコンテンツブロックをプレビューする
 permalink: "/preview_dnd_content_blocks/"
 hidden: true
 ---
 
-# ドラッグ＆ドロップ・エディターのコンテンツ・ブロックをプレビューする
+# ドラッグ＆ドロップエディターのコンテンツブロックをプレビューする
 
 [ドラッグ＆ドロップでメールキャンペーン用のコンテンツブロックを]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_content_blocks/)作成したら、ドラッグ＆ドロップエディターでコンテンツブロックのライブラリを表示しよう。
 
 {% alert important %}
-ドラッグ＆ドロップ・エディター・コンテンツ・ブロックのこのプレビュー機能は、現在早期アクセス中である。早期アクセスへの参加に興味がある方は、Brazeのアカウントマネージャーに連絡を。
+ドラッグ＆ドロップエディターコンテンツブロックのこのプレビュー機能は、現在早期アクセス中です。早期アクセスへの参加に興味がある方は、Brazeのアカウントマネージャーに連絡を。
 {% endalert %}
 
-コンテンツブロックをプレビューするには、**コンテンツ**セクション >**デザインとビルドに**進む。**Rows**タブをクリックし、ドロップダウンで**Content Blocksを**選択する。ドラッグ＆ドロップで作成したコンテンツブロックが、メールキャンペーンと同じように表示される。 
+コンテンツブロックをプレビューするには、\[**コンテンツ**] セクション > \[**設計と構築**] に移動します。\[**行**] タブをクリックし、ドロップダウンで \[**コンテンツブロック**] を選択します。ここでは、ドラッグ＆ドロップエディターのコンテンツブロックがメールキャンペーンの場合と同様に表示されます。 
 
 {% alert note %}
-**行」**タブで表示できるのは、ドラッグ＆ドロップ・エディターでのみ使用されるコンテンツ・ブロックのみである。
+\[**行**] タブには、ドラッグ＆ドロップエディターでのみ使用されるコンテンツブロックのみが表示されます。
 {% endalert %}
 
 コンテンツブロックをメールキャンペーンにドラッグ＆ドロップすると、コンテンツブロック内のすべてのコンテンツに変更を加えることができる。コンテンツブロックにリキッドが含まれている場合、**プレビュー＆テスト**セクションにリキッドが表示される。
 
-![ドラッグ＆ドロップ・エディターのコンテンツ・セクションにある「行」タブで、コンテンツ・ブロック・オプションが選択されている。MyDealzとArtNightのメールヘッダーとして使用できる2つのコンテンツブロックプレビューがある。][1]{: style="max-width:50%" }
+![ドラッグ＆ドロップエディターのコンテンツセクションにある「行」タブで、コンテンツブロックオプションが選択されています。MyDealz およびArtNight のメールヘッダーとして使用できる2つのコンテンツブロックプレビューがあります。][1]{: style="max-width:50%" }
 
 
 [1]: {% image_buster /assets/img_archive/dnd_content_block_preview.png %} 
diff --git a/_lang/ja/_hidden/private_betas/email_html_react.md b/_lang/ja/_hidden/private_betas/email_html_react.md
index 56d4ce40224..21a7700bfce 100644
--- a/_lang/ja/_hidden/private_betas/email_html_react.md
+++ b/_lang/ja/_hidden/private_betas/email_html_react.md
@@ -8,7 +8,7 @@ description: "この記事では、更新されたEメール用HTMLエディタ
 
 # Eメール用HTMLエディタを更新
 
-> 更新されたEメール用HTMLエディタは、より優れたコード編集体験を含む一連のUI改善を特徴とする。 
+> 更新されたメール用 HTML エディターでは、コード編集エクスペリエンスの向上など、一連の UI 改善が行われています。 
 
 アップデートされたHTMLエディタでは、エディタ上部のナビゲーションでエディタ（HTML、クラシック、プレーンテキスト、AMP）をシームレスに切り替えることができる。これらのオプションは、以前は古いHTMLエディターのドロップダウンに隠されていた。この更新されたHTMLエディターは、他のメッセージング・チャンネルのエディターでも一貫したエクスペリエンスを実現し、Brazeが将来、これらのエディターに普遍的な改良をより効率的に加えることを可能にする。
 
@@ -18,7 +18,7 @@ description: "この記事では、更新されたEメール用HTMLエディタ
 更新されたHTMLメールエディターで**リンク管理**タブにアクセスするには、[リンクエイリアスを]({{site.baseurl}}/user_guide/message_building_by_channel/email/templates/link_aliasing/)オンにしておく必要がある。リンクエイリアスを有効にするには、アカウントマネージャーに連絡する。
 {% endalert %}
 
-**旧HTMLエディタへの切り替える**をクリックして旧HTMLエディタに切り替えるすることはできますが、旧HTMLエディタは2024年初頭に削除されることに注意してください。
+\[**古い HTML エディターに切り替える**] をクリックして古い HTML エディターに切り替えることはできますが、古い HTML エディターは2024年初頭に削除されることに注意してください。
 
 詳細については、専用の[ HTMLエディタでメール]({{site.baseurl}}/user_guide/message_building_by_channel/email/html_editor) を参照してください。
 
diff --git a/_lang/ja/_hidden/private_betas/field_level_encryption.md b/_lang/ja/_hidden/private_betas/field_level_encryption.md
index 879190ddc4c..6d12c812cc6 100644
--- a/_lang/ja/_hidden/private_betas/field_level_encryption.md
+++ b/_lang/ja/_hidden/private_betas/field_level_encryption.md
@@ -8,7 +8,7 @@ page_type: reference
 
 # フィールドレベル暗号化
 
-> フィールドレベルの暗号化を使用すると、AWS Key Management Service (KMS) でメールアドレスをシームレスに暗号化し、Braze で共有される個人を特定できる情報 (PII) を最小限に抑えることができます。暗号化は機密データを暗号文に置き換えます。これは読み取れない暗号化された情報です。
+> フィールドレベルの暗号化を使用すると、AWS Key Management Service (KMS) を使用してメールアドレスをシームレスに暗号化し、Braze で共有される個人を特定できる情報 (PII) を最小限に抑えることができます。暗号化は機密データを暗号文に置き換えます。これは読み取れない暗号化された情報です。
 
 {% alert important %}
 フィールドレベルの暗号化は現在ベータ機能として利用可能です。このベータ版に参加することに興味がある場合は、Brazeのアカウントマネージャーに連絡してください。
@@ -16,28 +16,28 @@ page_type: reference
 
 ## その仕組み
 
-メールアドレスは、Brazeに追加される前にハッシュ化および暗号化される必要があります。メッセージが送信されると、復号化されたメールアドレスのためにAWS KMSに呼び出しが行われます。次に、ハッシュ化されたメールアドレスが配信およびエンゲージメントイベントのメタデータに挿入され、元のユーザーにリンクされます。これがBrazeがメール分析を追跡する方法です。Brazeは含まれているプレーンテキストのメールアドレスを編集し、ユーザーのプレーンテキストのメールアドレスを保存しません。
+メールアドレスは、Brazeに追加される前にハッシュ化および暗号化される必要があります。メッセージが送信されると、復号化されたメールアドレスに対して AWS KMS への呼び出しが行われます。次に、ハッシュ化されたメールアドレスが配信およびエンゲージメントイベントのメタデータに挿入され、元のユーザーにリンクされます。これがBrazeがメール分析を追跡する方法です。Braze は含まれているプレーンテキストのメールアドレスを編集し、ユーザーのプレーンテキストのメールアドレスを保存しません。
 
 ## 前提条件
 
-フィールドレベルの暗号化を使用するには、メールアドレスをBrazeに送信する前にAWS KMSにアクセスして[暗号化](https://docs.aws.amazon.com/kms/latest/APIReference/API_Encrypt.html)および[ハッシュ化](https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateMac.html)する必要があります。 
+フィールドレベルの暗号化を使用するには、メールアドレスを Braze に送信する**前に**、AWS KMS へアクセスして、メールアドレスを[暗号化](https://docs.aws.amazon.com/kms/latest/APIReference/API_Encrypt.html)および[ハッシュする](https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateMac.html)必要があります。 
 
 次の手順に従って、AWSシークレットキー認証方法を設定します。
 
-1. アクセスキー ID とシークレットアクセスキーを取得するには、[AWS に IAM ユーザーと管理者グループ](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-set-up.html#create-an-admin) を作成し、AWS キーマネジメントサービスの権限ポリシーを設定します。IAMユーザーは[kms:Decrypt](https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt.html)および[kms:GenerateMac](https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateMac.html)の権限を持っている必要があります。詳細については、[AWS KMS の権限](https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)を参照してください。
+1. アクセスキー ID とシークレットアクセスキーを取得するには、AWS Key Management Service のアクセス許可ポリシーを使用して AWS で [IAM ユーザーと管理者グループを作成します](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-set-up.html#create-an-admin)。IAMユーザーは[kms:Decrypt](https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt.html)および[kms:GenerateMac](https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateMac.html)の権限を持っている必要があります。詳細については、[AWS KMS の権限](https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)を参照してください。
 2. **ユーザーのセキュリティ認証情報を表示**を選択して、アクセスキーIDとシークレットアクセスキーを表示します。これらの認証情報をどこかにメモするか、**認証情報をダウンロード**ボタンを選択してください。AWS KMSキーに接続する際にこれらを入力する必要があります。
 3. 次のAWSリージョンでKMSを設定する必要があります:
     - **Braze US クラスター:** `us-east-1`
     - **Braze EU クラスター:** `eu-central-1`
-4. AWS Key Management Serviceで2つのキーを作成し、IAMユーザーがキー使用権限に追加されていることを確認します。
+4. AWS Key Management Service で2つのキーを作成し、IAM ユーザーがキー使用アクセス許可に追加されていることを確認します。
     - **[暗号化/復号化](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html#create-symmetric-cmk):****対称**キータイプを選択し、**暗号化と復号化**キー使用法を選択します。
-    - **[ハッシュ](https://docs.aws.amazon.com/kms/latest/developerguide/hmac-create-key.html):****Symmetric**キータイプと**Generate and Verify MAC**キーの使用を選択します。キー仕様は**HMAC_256**であるべきです。キーを作成した後、HMACキーIDをどこかにメモしておいてください。Brazeに入力する必要があります。
+    - **[ハッシュ](https://docs.aws.amazon.com/kms/latest/developerguide/hmac-create-key.html):**\[**対称**] キータイプと **\[MAC の生成と検証**] キー使用を選択します。キー仕様は**HMAC_256**であるべきです。キーを作成した後、HMAC キー ID をどこかにメモしておいてください。Braze で入力する必要があります。
 
 ![]({% image_buster /assets/img/field_level_encryption_aws_prereq.png %})
 
 ## ステップ 1:AWS KMS キーを接続する
 
-AWS KMS設定には、次の内容を入力してください:
+AWS KMS 設定には、次の内容を入力してください:
 
 - アクセスキーID
 - シークレットアクセスキー
@@ -74,8 +74,8 @@ Brazeでメールアドレスを更新する際は、`email`が含まれてい
 
 - SDKを介してメールアドレスを識別およびキャプチャする
 - アプリ内メッセージメールキャプチャフォーム
-- 受信者ドメインに関するレポート、メールインサイトのメールボックスプロバイダーチャートを含む
-- メールアドレスフィルター正規表現による
+- メールインサイトのメールボックスプロバイダーチャートを含む、受信者ドメインに関するレポート
+- 正規表現によるメールアドレスフィルター
 - オーディエンス同期
 - Shopify統合
 
@@ -93,17 +93,17 @@ Brazeでメールアドレスを更新する際は、`email`が含まれてい
 暗号化は、データを暗号化および復号化することが可能な双方向機能です。同じ平文の値が複数回暗号化された場合、AWSの暗号化アルゴリズム（AES-256-GCM）は異なる暗号化値を生成します。ハッシュ化は、平文が復号できない方法でスクランブルされる一方向関数です。ハッシュ化は毎回同じ値を生成します。これにより、同じメールアドレスを共有する複数のユーザー間でサブスクリプション状態を維持することができます。
 
 ### テスト送信にどのメールアドレスを使用すればよいですか？
-プレーンテキストのメールアドレスはテスト送信でサポートされています。特定のユーザーに対してメールがどのように見えるかを確認するには、次の手順を実行します。
+プレーンテキストのメールアドレスはテスト送信でサポートされています。特定のユーザーに対してメールがどのように表示されるかを確認するには、次の操作を行います。
 
 1. **プレビュー メッセージをユーザーとして選択**.
-2. **テスト送信**で、**現在のプレビューユーザーの属性で受信者の属性を上書き<2>}を選択します。
+2. \[**テスト送信**] で、\[**受信者の属性を現在のプレビューユーザーの属性で上書きする**] を選択します。
 
 {%raw%}
 ### このメールアドレス Liquid `{{${email_address}}}` を Braze に追加するとどうなりますか？
 
 Brazeはメールを送信する際にプレーンテキストのメールアドレスをレンダリングします。プレビューでは、メールの暗号化されたバージョンを表示します。カスタムワンクリックURLでユーザーを参照する場合は、ユーザーのexternal IDを使用することをお勧めします。
 
-`{{${email_address}}}`は現在、ユーザー設定センターおよび配信停止ページではサポートされていません。
+`{{${email_address}}}` は現在、ユーザー設定センターおよび配信停止ページではサポートされていません。
 {%endraw%}
 
 ### Currentsで確認するメールアドレスは何ですか？
diff --git a/_lang/ja/_hidden/private_betas/get_app_group_apps.md b/_lang/ja/_hidden/private_betas/get_app_group_apps.md
index 9e65b877167..61a5fbbd5ca 100644
--- a/_lang/ja/_hidden/private_betas/get_app_group_apps.md
+++ b/_lang/ja/_hidden/private_betas/get_app_group_apps.md
@@ -11,7 +11,7 @@ description: "この記事では、リストワークスペースアプリBraze
 {% api %}
 # ワークスペースアプリをリスト
 {% apimethod get %}
-/アプリ_group/アプリs
+/app_group/apps
 {% endapimethod %}
 
 > このエンドポイントを使用して、ワークスペース内のアプリの名前と一意の識別子（`api_key`）を一覧表示します。 
@@ -24,7 +24,7 @@ description: "この記事では、リストワークスペースアプリBraze
 
 このエンドポイントには、1日（24時間）あたり100リクエストのレート制限があります。
 
-## Request parameters
+## リクエストパラメーター
 
 このリクエストはパラメータを取りません。
 
@@ -58,7 +58,7 @@ Authorization: Bearer YOUR-REST-API-KEY
 | エラー | トラブルシューティング |
 | --- | --- |
 | `401: Unauthorized` | API キーには必要な権限がありません。API キーに`apps.get`の権限があることを確認してください。 |
-| `403: Forbidden` | この会社では機能フリッパーがオンになっていません。アシスタンスについては、顧客成功マネージャーに連絡してください。 |
+| `403: Forbidden` | この会社では機能フリッパーがオンになっていません。サポートが必要な場合は、カスタマーサクセスマネージャーに連絡してください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endapi %}
diff --git a/_lang/ja/_hidden/private_betas/get_campaign_url_info.md b/_lang/ja/_hidden/private_betas/get_campaign_url_info.md
index bab95f08023..03f794f6d9a 100644
--- a/_lang/ja/_hidden/private_betas/get_campaign_url_info.md
+++ b/_lang/ja/_hidden/private_betas/get_campaign_url_info.md
@@ -65,8 +65,8 @@ Authorization: Bearer YOUR-REST-API-KEY
 
 | エラー | トラブルシューティング |
 | --- | --- |
-| `Missing/Invalid Campaign ID` | キャンペーンAPI IDはAPI識別子でなければなりません。エクスポートキャンペーンリストエンドポイント[}を使用するか、ダッシュボードにログインすることでこれを見つけることができます。]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaigns/) |
-| `Missing/Invalid Message Variant ID` | メッセージバリアントAPI IDはAPI識別子でなければなりません。これは、[エクスポートキャンペーンの詳細エンドポイント]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/)を使用するか、ダッシュボードにログインして確認できます。 |
+| `Missing/Invalid Campaign ID` | キャンペーンAPI IDはAPI識別子でなければなりません。これは、[キャンペーンリストのエクスポートエンドポイントを]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaigns/)使うか、ダッシュボードにログインすることで確認できます。 |
+| `Missing/Invalid Message Variant ID` | メッセージバリアントAPI IDはAPI識別子でなければなりません。これは、[キャンペーン詳細のエクスポートエンドポイントを]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/)使うか、ダッシュボードにログインすることで確認できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 
diff --git a/_lang/ja/_hidden/private_betas/get_canvas_url_info.md b/_lang/ja/_hidden/private_betas/get_canvas_url_info.md
index 78338ff1bd8..d8538164091 100644
--- a/_lang/ja/_hidden/private_betas/get_canvas_url_info.md
+++ b/_lang/ja/_hidden/private_betas/get_canvas_url_info.md
@@ -28,8 +28,8 @@ description: "この記事では、CanvasエンドポイントのListリンク
 
 | パラメーター | required | データ型 | 説明 |
 |---|---|---|---|
-| `canvas_step_id` | 必須 | string | [キャンバスステップAPI識別子を]({{site.baseurl}}/api/identifier_types/#canvas-api-identifier)参照のこと。 |
-| `message_variation_id ` | 必須 | string | メッセージバリアントAPI識別子（そのステップのEメールメッセージバリアント用）。これは、**キャンバスの詳細**ページで**バリアントの分析を**クリックすることで見つけることができる。 |
+| `canvas_step_id` | required | string | [キャンバスステップ API 識別子]({{site.baseurl}}/api/identifier_types/#canvas-api-identifier)を参照してください。 |
+| `message_variation_id ` | required | string | メッセージバリアント API 識別子 (そのステップのメールメッセージバリアント用)。これは、\[**キャンバス詳細**] ページで \[**バリアントを分析**] をクリックすることで確認できます。 |
 | `includes_link_id` | オプション | string | 特定のリンク識別子（Brazeによって割り当てられる）または`null` 。これは、特定の`link_id` によって結果をフィルタリングするために使用される。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 }
 
@@ -66,8 +66,8 @@ Authorization: Bearer YOUR-REST-API-KEY
 
 | エラー | トラブルシューティング |
 | --- | --- |
-| `Missing/Invalid Canvas ID` | キャンバスAPI IDはAPI識別子でなければならない。これは、[キャンバス・リストのエクスポート・エンドポイントを]({{site.baseurl}}/api/endpoints/export/canvas/get_canvases/)使うか、ダッシュボードにログインすることで確認できる。 |
-| `Missing/Invalid Message Variant ID` | メッセージバリアントAPI IDはAPI識別子でなければならない。これは、[キャンバスの詳細をエクスポートするエンドポイントを]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/)使用するか、ダッシュボードにログインすることで確認できる。 |
+| `Missing/Invalid Canvas ID` | キャンバス API ID はAPI 識別子でなければなりません。これは、[キャンバスリストのエクスポートエンドポイントを]({{site.baseurl}}/api/endpoints/export/canvas/get_canvases/)使うか、ダッシュボードにログインすることで確認できます。 |
+| `Missing/Invalid Message Variant ID` | メッセージバリアントAPI IDはAPI識別子でなければならない。これは、[キャンバス詳細のエクスポートエンドポイントを]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/)使うか、ダッシュボードにログインすることで確認できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endapi %}
diff --git a/_lang/ja/_hidden/private_betas/idle_campaigns.md b/_lang/ja/_hidden/private_betas/idle_campaigns.md
index 248b76e140e..153227a6006 100644
--- a/_lang/ja/_hidden/private_betas/idle_campaigns.md
+++ b/_lang/ja/_hidden/private_betas/idle_campaigns.md
@@ -9,7 +9,7 @@ hidden: true
 > このリファレンス記事では、キャンペーンとキャンバスのアイドルステータスについて説明し、よくある質問への回答を提供します。
 
 {% alert note %}
-2024年、キャンバスは**アイドル**とマークされ、キャンペーンs と同様に停止します。キャンバスがアイドル状態または停止状態になると、このドキュメントのロジックに従います。
+2024年、キャンバスは**アイドル**とマークされ、キャンペーンと同様に停止します。キャンバスがアイドル状態または停止状態になると、このドキュメントのロジックに従います。
 {% endalert %}
 
 キャンペーンとキャンバスには、しばらくの間、メッセージを送信したり、ユーザーs を入力したりしなかったときに、アイドルステータスが割り当てられます。これらのキャンペーンとキャンバスは、関連付けられた停止日時に自動的に停止します。アイドル状態のキャンペーンやキャンバスをフィルターすると、キャンペーンやキャンバスの一覧を並べ替えたり管理したりできます。
@@ -18,19 +18,19 @@ hidden: true
 
 継続的に、次の基準を満たすアイドルキャンペーンs は停止されます。
  
-- スケジュールされたのワンタイム送信は、送信日を7日間過ぎています
+- スケジュールされた1回限りの送信が、送信日から7日経過しています
 - 終了日があるスケジュールされたまたはアクション ベースのキャンペーンは、終了日を7 日過ぎています
 - 1年間にメールを送信しなかった、終了日のないキャンペーン
 
-終了日のないキャンペーンの場合、メッセージが送信されるか、キャンペーンが更新dの場合、キャンペーンを停止するための1年間のカウントダウンが再設定されます。キャンペーン s が停止すると、Braze は顧客にダッシュボードとメールで通知します。
+終了日のないキャンペーンの場合、メッセージが送信されるか、キャンペーンが更新dの場合、キャンペーンを停止するための1年間のカウントダウンが再設定されます。キャンペーンが停止すると、Braze は顧客にダッシュボードとメールで通知します。
 
-キャンペーンは、デフォルト終了日の後日、および最後に発生したコンバージョン期限の1 日後に停止されます。Winning またはPersonalized Variant の送信はスケジュールされた送信として扱われ、Winning またはPersonalized Variant の送信から7 日後に停止されます。すべてのキャンペーンs は、すべてのBraze ユーザーs について毎日UTC の午前4 時に停止します。
+キャンペーンは、デフォルトの停止日または最後に発生したコンバージョン期限の1日後のいずれか遅い方の日付に停止されます。勝者バリアントまたはパーソナライズされたバリアントの結果である送信は、スケジュールされた送信として扱われ、勝者バリアントまたはパーソナライズされたバリアントが送信されてから7日後に停止されます。すべてのキャンペーンは、すべての Braze ユーザーを対象に、毎日午前4時 (協定世界時) に停止されます。
 
 コンテンツカードは、期限が切れるまで停止せず、上記の基準およびコンバージョン期限規則を遵守します。
 
-アイドルキャンペーンを有効にする方法については、このテーブルを参照してください。
+アイドルキャンペーンを有効にする方法については、この表を参照してください。
 
-| アイドルステータスの理由                                                                              | キャンペーンを有効にする手順                     |
+| アイドル状態の理由                                                                              | キャンペーンを有効にする手順                     |
 |-----------------------------------------------------------------------------------------------------|---------------------------------------------------|
 | スケジュールされた1回送信されるキャンペーンで、送信日の7日間が過ぎています                 | 今後の送信をスケジュールする                            |
 | スケジュールされたベースまたはアクションベースのキャンペーンで、終了日があり、終了日の7 日後のキャンペーン | 終了日の延長                               |
@@ -45,45 +45,45 @@ hidden: true
 - 終了日が指定されたスケジュールされたまたはアクションベースのキャンバスは、終了日を過ぎており、最長で7 日間継続します
 - 終了日のないキャンバスがユーザーに入力されていないか、12 か月以上編集されていないか、その最長継続時間
 
-終了日のないキャンバスの場合、ユーザーが入力されているか、キャンバスが更新d の場合、キャンバスを停止するための1 年間のカウントダウンがリセットされます。キャンバスが停止すると、Brazeは顧客にダッシュボードとメールで通知します。
+終了日のないキャンバスの場合、ユーザーが入力されるか、キャンバスが更新された場合、キャンバスを停止するための1年間のカウントダウンがリセットされます。キャンバスが停止すると、Braze は顧客にダッシュボードとメールで通知します。
 
-キャンバスの[最大継続時間]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)は、ユーザーが特定のキャンバスを完成するのに要する最長時間です。この期間には、コンテンツカードとアプリ内メッセージの有効期限が含まれます。
+キャンバスの[最大時間]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)は、ユーザーが特定のキャンバスを完了するために費やすことができる最長時間です。この期間には、コンテンツカードとアプリ内メッセージの有効期限が含まれます。
 
-アイドル状態のキャンバスをアクティブにする方法については、次の表を参照してください。
+アイドルキャンバスをアクティブに保つ方法については、次の表を参照してください。
 
-| アイドルステータスの理由                                                                                                  | キャンバスをアクティブにする手順                     |
+| アイドル状態の理由                                                                                                  | キャンバスをアクティブにする手順                     |
 |-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|
 | 1 回限りの送信をスケジュールされたするキャンバスで、送信日の7 日後で最長継続時間です                 | 今後の送信をスケジュールする                          |
 | スケジュールされたベースまたはアクションベースで、終了日があり、終了日の7 日後で最長継続時間が経過しているキャンバス | 終了日の延長                             |
-| 1年以内にメッセージを送信しなかった終了日のないキャンバス                                                      | 1 つのメッセージを送信するか、キャンバスに編集を加えます |
+| 1年以内にメッセージを受信しなかった終了日のないキャンバス                                                      | 1 つのメッセージを送信するか、キャンバスに編集を加えます |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## よくある質問
 
-#### このアプリはどのキャンペーンやキャンバスに向いていますか?
+#### これはどのキャンペーンまたはキャンバスに適用されますか?
 
-これにより、すでにリストされている基準を満たしているキャンペーン s とキャンバス、および前に進む基準を満たすキャンペーン s とキャンバスがアプリされます。
+これにより、リストされている基準をすでに満たしているキャンペーンとキャンバス、および今後基準を満たすキャンペーンとキャンバスに適用されます。
 
 #### キャンペーンまたはキャンバスがアイドル状態かどうかは、どのようにすればわかりますか?
 
-アイドルキャンペーンs とキャンバスは、アイドルカテゴリのキャンペーンとキャンバスリストページに表示されます。キャンペーンまたはキャンバスを停止する日が、一覧の列として表示されます。
+アイドル状態のキャンペーンとキャンバスは、\[アイドル] カテゴリーの下のキャンペーンおよびキャンバスリストページに表示されます。キャンペーンまたはキャンバスを停止する日が、一覧の列として表示されます。
 
-#### アイドル状態のキャンペーンまたはキャンバスが更新dの場合、どのアプリが終了しますか?
+#### アイドル状態のキャンペーンまたはキャンバスが更新されると、どうなりますか？
 
-メッセージを送信していないキャンペーン、またはユーザーに入力されていないキャンバスが更新 d の場合、カウントダウンは再設定されます。
+メッセージが送られていないキャンペーン、またはユーザーが入力されていないキャンバスが更新された場合、カウントダウンはリセットされます。
 
-#### 1年以内にメッセージを送っていない(または、1年以内にユーザーに入っていないキャンバス)が、将来終了日を持っているキャンペーンに寄るアプリは?
+#### 1年以内にメッセージが送信されていないキャンペーン (または1年以内にユーザーが入力されていないキャンバス) の終了日が将来の場合はどうなりますか？
 
-このキャンペーンとキャンバスは、終了日から7日後にストップします。
+これらのキャンペーンとキャンバスは、終了日から7日後に停止します。
 
-#### 停止したキャンペーンのSとキャンバスに関するメール 通知を受け取るのは?
+#### 停止したキャンペーンとキャンバスに関するメール通知を受け取るのは誰ですか?
 
-デフォルトでは、管理者権限を持つすべてのユーザーは、キャンペーンとキャンバスの自動停止に関するメール 通知に選択されます。キャンペーンまたはキャンバスの作成者は、停止すると必ず通知されます。ユーザは、**Company Settings**> **通知 Preferences**に移動し、通知**Campaign Automatically Stopped**と通知**Canvas Automatically Stopped**から受信者sを追加または削除することで、メール 通知の環境設定を管理できます。
+デフォルトでは、管理者権限を持つすべてのユーザーは、キャンペーンとキャンバスの自動停止に関するメール通知にオプトインされます。キャンペーンまたはキャンバスの作成者は、停止すると必ず通知されます。ユーザーは、\[**会社設定 (Company Settings)**] > \[**通知設定 (Notification Preferences)**] に移動し、通知 \[**キャンペーンの自動停止 (Campaign Automatically Stopped)**] および通知 \[**キャンバスの自動停止 (Canvas Automatically Stopped)**] から受信者を追加または削除することで、メール通知の設定を管理できます。
 
 #### コンテンツカードの停止はどのように機能しますか?
 
-キャンペーン s のコンテンツカードは、有効期限とアプリの適切なバッファー期限まで停止されません。これらは、バッファー期間の後半(キャンペーンがワンタイム送信であるか、終了日があるか、終了日がないかに対応) と有効期限で停止されます。 
+キャンペーンのコンテンツカードは、有効期限および適切なバッファー期限までは停止されません。これらは、バッファー期間 (キャンペーンが1回限りの送信であるか、終了日があるか、または終了日がないかに対応する) と有効期限のどちらか遅い時間に停止されます。 
 
-たとえば、コンテンツカードが4 月1 日に期限切れになり、ワンタイム送信であり、コンバージョンの期限が10 日である場合、4 月12 日(コンバージョンの期限の10 日後に1 日を加算) に停止されます。コンテンツカードが4月1日に期限切れになり、API-トリガーが期限切れになり、3月15日以降にメッセージを送信していない場合、期限は来年の3月15日となります。
+たとえば、4月1日に期限が切れるコンテンツカードが1回限りの送信で、コンバージョン期限が10日である場合、4月12日 (コンバージョン期限の10日後+1日) に停止されます。4月1日に有効期限が切れるコンテンツカードが API によってトリガーされ、3月15日以降メッセージが送信されていない場合、翌年の3月15日に有効期限が切れます。
 
-キャンバスは、コンテンツカードが停止した後でのみ停止します。つまり、最大継続時間が経過したことを意味します。
\ No newline at end of file
+キャンバスは、コンテンツカードが停止した後、つまり最大継続時間が経過して初めて停止します。
\ No newline at end of file
diff --git a/_lang/ja/_hidden/private_betas/linkedin_audience_sync.md b/_lang/ja/_hidden/private_betas/linkedin_audience_sync.md
index 8b6e910adf1..ea1fe369b01 100644
--- a/_lang/ja/_hidden/private_betas/linkedin_audience_sync.md
+++ b/_lang/ja/_hidden/private_betas/linkedin_audience_sync.md
@@ -1,48 +1,48 @@
 ---
-nav_title: 視聴者がLinkedIn に同期する
-article_title: Canvas Audience とLinkedIn の同期
+nav_title: LinkedIn へのオーディエンス同期
+article_title: キャンバスのオーディエンスと LinkedIn の同期
 permalink: /linkedin_audience_sync/
-description: "このレファレンス記事では、Braze Audience Sync をLinkedIn に使用して、ビヘイビアートリガーs、セグメンテーションなどに基づいてアドバタイズメントを配信する方法について説明します。"
+description: "このリファレンス記事では、Braze Audience Sync を LinkedIn に使用して、行動トリガーやセグメンテーションなどに基づいて広告を配信する方法について説明します。"
 Tool:
   - Canvas
 hidden: true
 ---
 
-# 視聴者がLinkedIn に同期する
+# LinkedIn へのオーディエンス同期
 
-Brazeオーディエンス同期を使用して、ブランドはBrazeインテグレーションのユーザーデータをLinkedIn 顧客一覧に追加して、動作トリガーs、セグメンテーションなどに基づいてアドバタイズメントを配信できます。通常、メッセージのトリガーに使用する基準(プッシュ、メール、SMS、Webhookなど)が、ユーザーデータに基づいてBrazeキャンバスに設定され、LinkedIn 顧客一覧のそのユーザーに広告をトリガーできるようになりました。
+Braze オーディエンス同期を LinkedIn に使用して、ブランドは Braze 統合のユーザーデータを LinkedIn 顧客一覧に追加して、行動トリガー、セグメンテーションなどに基づいて広告を配信できます。ユーザーデータに基づいて Braze キャンバスでメッセージをトリガーするために通常使用する基準 (プッシュ、メール、SMS、Webhook など) を使用して、LinkedIn 顧客リスト内の該当ユーザーに対して広告をトリガーできるようになりました。
 
 **オーディエンス同期の一般的なユースケースには**が含まれます。
 
-- 多重チャネルによる高価値ユーザーをターゲットに、仕入・エンゲージメントを牽引
+- 複数のチャネルを通じて価値の高いユーザーをターゲットにして、購入やエンゲージメントを促進
 - 他のマーケティング チャネルにあまりレスポンシブでないユーザーのリターゲット
-- 自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑圧オーディエンスsの作成
+- すでに自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑制オーディエンスの作成
 
-この機能により、ブランドはLinkedInと共有されている特定のファーストパーティデータをコントロールできます。Brazeでは、ファーストパーティデータを共有できる統合と共有できない統合を最大限に検討します。詳細については、[プライバシーポリシー](https://www.braze.com/privacy)を参照してください。
+この機能により、ブランドはLinkedInと共有されている特定のファーストパーティデータをコントロールできます。Braze では、ファーストパーティデータを共有できる統合と共有できない統合を最大限に考慮しています。詳細については、[プライバシーポリシー](https://www.braze.com/privacy)を参照してください。
 
 {% alert important %}
-Audience Sync to LinkedInは現在ベータ版にある。ベータ版に参加したい場合は、Braze アカウントマネージャーにお問い合わせください。
+LinkedIn へのオーディエンス同期は現在ベータ版です。ベータ版に参加したい場合は、Braze アカウントマネージャーにお問い合わせください。
 {% endalert %}
 
 ## 前提条件
 
-キャンバスでLinkedIn Audience Sync ステップを設定するには、以下のアイテムが作成、完了、または受け入れられていることを確認する必要があります。
+キャンバスで LinkedIn へのオーディエンス同期のステップを設定するには、以下の項目が作成、完了、または受け入れられていることを確認する必要があります。
 
 | 要件 | Origin | 説明 |
 | --- | --- | --- |
-| LinkedInの広告アカウント | [LinkedIn](https://www.linkedin.com/campaignmanager) | ブランドに関連付けられたアクティブなLinkedIn アドアカウント。<br><br>関連するLinkedIn 利用規約を受け入れ、そのアカウントを使用していること、およびLinkedIn 管理者がオーディエンスを管理するための適切な権限をアプリに付与していることを確認してください。 |
-| LinkedIn用語&ポリシー | LinkedIn | LinkedIn Audience Sync の使用に関連するLinkedIn の必要な用語、ポリシー、ガイドライン、およびドキュメントのいずれかに準拠することに同意します。これには、LinkedIn の以下の用語、ポリシー、ガイドライン、およびドキュメントが含まれます。サービス条件、広告契約、データ処理契約、および専門家コミュニティガイドライン。 |
+| LinkedIn の広告アカウント | [LinkedIn](https://www.linkedin.com/campaignmanager) | ブランドに関連付けられたアクティブなLinkedIn アドアカウント。<br><br>そのアカウントにアクセスして使用するための関連する LinkedIn の使用条件に同意していること、および LinkedIn の管理者によってオーディエンスを管理するための適切なアクセス許可が付与されていることを確認してください。 |
+| LinkedIn 利用規約 | LinkedIn | LinkedIn Audience Sync の使用に関連する LinkedIn の必須規約、ポリシー、ガイドラインおよびドキュメントを遵守することに同意するものとします。これには、参照によって組み込まれている LinkedIn の以下の項目を含む規約、ポリシー、ガイドラインおよびドキュメントが含まれます。サービス規約、広告契約、データ処理契約、プロフェッショナルコミュニティガイドライン。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合
 
 ### ステップ1:LinkedIn への接続
 
-Braze ダッシュボードで、**Technology Partners**に移動し、**LinkedIn**を選択します。LinkedIn Audience Export モジュールで、**Connect LinkedIn** をクリックします。
+Braze ダッシュボードで、**Technology Partners**に移動し、**LinkedIn**を選択します。LinkedIn Audience Export モジュールで、\[**LinkedIn に接続**] をクリックします。
 
-![Braze のLinkedIn テクノロジページには、Overview モジュールとLinkedIn Audience Export モジュールとConnected LinkedIn ボタンがあります。][3]{: style="max-width:75%;"}
+![Braze のLinkedIn テクノロジページには、Overview モジュールと LinkedIn Audience Export モジュールと \[接続済みの LinkedIn] ボタンがあります。][3]{: style="max-width:75%;"}
 
-次に、LinkedIn OAuth ページにリダイレクトされ、オーディエンスシンクインテグレーションに関連する権限のBrazeを許可します。**Confirm** を選択すると、Braze にリダイレクトされ、同期するLinkedIn アドアカウントを選択します。 
+次に、LinkedIn OAuth ページにリダイレクトされ、Braze に Audience Sync 統合に関連するアクセス許可を承認します。**Confirm** を選択すると、Braze にリダイレクトされ、同期するLinkedIn アドアカウントを選択します。 
 
 ![][7]{: style="max-width:75%;"}
 
@@ -50,35 +50,35 @@ Braze ダッシュボードで、**Technology Partners**に移動し、**LinkedI
 
 ![][6]{: style="max-width:75%;"}
 
-あなたのLinkedInコネクションは、アプリはBraze ワークスペースの段階にあります。LinkedIn 管理者がLinkedIn アドアカウントからユーザを削除すると、Braze は不正なトークンを検出します。そのため、LinkedIn を使用しているアクティブなキャンバスにはエラーs が表示され、Braze はユーザーs を同期できません。
+LinkedIn 接続は Braze ワークスペースレベルで適用されます。LinkedIn 管理者が LinkedIn 広告アカウントからユーザーを削除した場合、Braze は無効なトークンを検出します。そのため、LinkedIn を使用しているアクティブなキャンバスにはエラーが表示され、Braze はユーザーを同期できません。
 
 ### ステップ2:キャンバスのエントリ条件を設定する
 
-広告追跡のためにオーディエンスsを構築する場合、その好みに基づいて特定のユーザーsを含めるか除外し、[CCPA](https://oag.ca.gov/privacy/ccpa)の下で「売らない、共有しない」権利などのプライバシー法に従うことを希望する場合があります。マーケターは、キャンバスのエントリ基準の範囲内で、ユーザーの適格性に関連するフィルターを実施すべきである。以下に、いくつかのオプションを示します。 
+広告追跡のためにオーディエンスsを構築する場合、その好みに基づいて特定のユーザーsを含めるか除外し、[CCPA](https://oag.ca.gov/privacy/ccpa)の下で「売らない、共有しない」権利などのプライバシー法に従うことを希望する場合があります。マーケターは、キャンバスのエントリ基準の範囲内で、ユーザーの適格性に関する適切なフィルターを実装する必要があります。以下に、いくつかのオプションを示します。 
 
-[iOS IDFAをBraze SDK]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overviewother_sdk_customizations/#optional-idfa-collection)を通して収集した場合、**Ads Tracking Enabled**フィルターを使用することができます。`true` として値を選択すると、ユーザーs が選択されているオーディエンス同期送信先s にのみ送信されます。 
+[iOS IDFAをBraze SDK]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overviewother_sdk_customizations/#optional-idfa-collection)を通して収集した場合、**Ads Tracking Enabled**フィルターを使用することができます。ユーザーがオプトインしたオーディエンス同期の宛先にのみユーザーを送信するには、値を `true` に選択します。 
 
 ![][5]{: style="max-width:75%;"}
 
-`opt-ins`、`opt-outs`、`Do Not Sell Or Share`、または他の関連するカスタム属性s を収集する場合は、キャンバスのエントリ基準にこれらをフィルターとして含める必要があります。
+`opt-ins`、`opt-outs`、`Do Not Sell Or Share`、または他の関連するカスタム属性を収集する場合は、キャンバスのエントリ基準にこれらをフィルターとして含める必要があります。
 
-![エントリ オーディエンスが"opted_in_マーケティング" equals "true" のキャンバス。][4]{: style="max-width:75%;"}
+![エントリオーディエンスが 「opted_in_marketing」のキャンバスは「true」です。][4]{: style="max-width:75%;"}
 
-Braze プラットフォーム内でこれらのデータプロテクション法を遵守する方法の詳細については、[データプロテクションテクニカルサポート]({{site.baseurl}}/dp-technical-assistance/)を参照してください。
+Braze プラットフォーム内でこれらのデータ保護法を遵守する方法の詳細については、[データ保護テクニカルアシスタンス]({{site.baseurl}}/dp-technical-assistance/)を参照してください。
 
 ### ステップ3:LinkedIn を使用したオーディエンス同期ステップの追加
 
-キャンバスにコンポーネントを追加し、「オーディエンス同期」を選択します。コンポーネントエディターを開封するには、**Custom Audience**ボタンを押します。
+キャンバスにコンポーネントを追加し、「オーディエンス同期」を選択します。コンポーネントエディターを開くには、\[**カスタムオーディエンス**] ボタンをクリックします。
 
 ![][2]{: style="max-width:35%;"} ![][1]{: style="max-width:29%;"}
 
 ### ステップ4:同期設定
 
-必要なAudience Sync パートナーとして**LinkedIn** を選択します。
+**LinkedIn** を目的のオーディエンス同期パートナーとして選択します。
 
 ![][9]{: style="max-width:70%;"}
 
-次に、目的のLinkedIn ad アカウントを選択します。**新規または既存のオーディエンス**ドロップダウンから、新規または既存のオーディエンスの名前を入力します。
+次に、目的の LinkedIn ad アカウントを選択します。\[**新規または既存のオーディエンス**] ドロップダウンから、新規または既存のオーディエンスの名前を入力します。
 
 ![][11]
 
@@ -86,104 +86,104 @@ Braze プラットフォーム内でこれらのデータプロテクション
 {% tab 新規オーディエンスの作成 %}
 
 **新規オーディエンスの作成**<br>
-新しいオーディエンスの名前を入力し、**オーディエンス** にユーザを追加を選択し、LinkedIn と同期するフィールドを選択します。この統合では、現在以下をサポートしています。 
+新しいオーディエンスの名前を入力し、\[**オーディエンスにユーザを追加**] を選択し、LinkedIn と同期するフィールドを選択します。この統合では、現在以下をサポートしています。 
 - メール
-- 姓と名
-- Androidガイド
+- 名前と苗字
+- Android GAID
 
 次に、ステップエディタの下部にある**オーディエンス**を作成ボタンをクリックして、オーディエンスを保存します。
 
 ![]({% image_buster /assets/img/linkedin/linkedin10.png %})
 
-オーディエンスが正常に作成された場合、またはこの処理中にエラーが発生した場合は、ステップエディタの上部にユーザが通知されます。ユーザー s は、このオーディエンスを参照して、後でキャンバスジャーニーでユーザーを削除することもできます。これは、オーディエンスが下書きで作成されたためです。
+オーディエンスが正常に作成された場合、またはこの処理中にエラーが発生した場合は、ステップエディタの上部にユーザが通知されます。ユーザーは、このオーディエンスを参照して、後でキャンバスジャーニーでユーザーを削除することもできます。これは、オーディエンスが下書きで作成されたためです。
 
 ![]({% image_buster /assets/img/linkedin/linkedin9.png %})
 
-新しいオーディエンスを使用してキャンバスを起動すると、オーディエンスシンクコンポーネントに入ったときに、Braze はユーザーをほぼリアルタイムで同期します。
+新しいオーディエンスを使用してキャンバスを起動すると、オーディエンス動機コンポーネントに入ったときに、Braze はユーザーをほぼリアルタイムで同期します。
 
 {% endtab %}
 {% tab 既存のオーディエンスとの同期 %}
 
 **既存のオーディエンスとの同期**<br>
-また、Brazeは、これらのオーディエンスが最新であることを確認するために、既存のLinkedIn オーディエンス sにユーザーを追加する機能も提供します。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンスの名前を入力し、**オーディエンスに追加します。**Braze は、オーディエンスシンクコンポーネントに入ると、ほぼリアルタイムでユーザーs を追加します。
+また、Braze は、これらのオーディエンスが最新であることを確認するために、既存のLinkedIn オーディエンスにユーザーを追加する機能も提供します。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンスの名前を入力し、**オーディエンスに追加します。**Braze は、オーディエンス同期コンポーネントに入ると、ほぼリアルタイムでユーザーを追加します。
 
-![カスタムオーディエンスキャンバスステップの展開表示。ここでは、目的の広告アカウントと既存のオーディエンスが選択されます。]({% image_buster /assets/img/linkedin/linkedin17.png %})
+![カスタムオーディエンスキャンバスステップの展開ビュー。ここでは、目的の広告アカウントと既存のオーディエンスが選択されます。]({% image_buster /assets/img/linkedin/linkedin17.png %})
 
 {% endtab %}
 {% endtabs %}
 
 ### ステップ 5: キャンバスの起動
 
-Audience Sync to LinkedIn を設定したら、キャンバスを起動します。新しいオーディエンスが作成され、LinkedIn でこのオーディエンスにオーディエンス同期 を流れるユーザーs ステップが渡されます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーs はユーザーの移動の次回のステップに進みます。
+LinkedInへのオーディエンス同期を設定したら、キャンバスを起動するだけです！新しいオーディエンスが作成され、オーディエンス同期ステップを通過するユーザーは LinkedIn のこのオーディエンスに送られます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーはユーザージャーニーの次のステップに進みます。
 
-LinkedIn のオーディエンスを表示するには、広告アカウントに移動し、ナビゲーションの**Assets** セクションで**オーディエンスs** を選択します。**オーディエンス s**ページから、300人以上の会員に達した後、それぞれのオーディエンスの大きさを見ることができます。
+LinkedIn のオーディエンスを表示するには、広告アカウントに移動し、ナビゲーションの \[**アセット**] セクションで \[**オーディエンス**] を選択します。\[**オーディエンス**] ページでは、300人以上のメンバーに達した後、それぞれのオーディエンスの大きさを見ることができます。
 
-![Linked 指定されたオーディエンスの次のメトリクスを一覧表示します。][8]
+![指定したオーディエンスの以下のメトリクスをリストする LinkedIn ページ。][8]
 
 ## ユーザの同期とレート制限に関する考慮事項
 
-ユーザーがオーディエンス同期ステップに到達すると、BrazeはLinkedInのAPIレート制限を尊重しながら、これらのユーザーをほぼリアルタイムで同期します。実際には、Braze は、これらのユーザーをLinkedIn に送信する前に、5 秒ごとに最大数のユーザーをバッチ処理して処理しようとします。
+ユーザーがオーディエンス同期ステップに到達すると、BrazeはLinkedInのAPIレート制限を尊重しながら、これらのユーザーをほぼリアルタイムで同期します。実際には、Braze は、これらのユーザーをLinkedIn に送信する前に、5秒ごとにできるだけ多くのユーザーをバッチ処理しようとします。
 
-LinkedIn のAPI レート制限では、1 秒あたり10 件のクエリーと1 リクエストあたり100k のユーザーを超えないように設定されています。Braze 顧客がこのレート制限に達した場合、キャンバスをBrazeすると最大13 時間までシンクが再試行されます。同期できない場合、これらのユーザーは「エラーメトリクス」のユーザーに表示されます。
+LinkedIn のAPI レート制限では、1 秒あたり10 件のクエリーと1 リクエストあたり100k のユーザーを超えないように設定されています。Braze の顧客がこのレート制限に達した場合、Braze キャンバスは最大13時間にわたって同期を再試行します。同期できない場合、これらのユーザーは「ユーザーエラーが発生しました」メトリクスの下にリストされます。
 
 ## 分析について
 
-次のテーブルには、オーディエンスシンクコンポーネントからの分析をよりよく理解するためのメトリクスと説明が含まれています。
+次の表には、オーディエンス同期コンポーネントからの分析をよりよく理解するのに役立つメトリクスと説明が含まれています。
 
-| メトリック | 説明 |
+| メトリクス | 説明 |
 | ------ | ----------- | 
-| 入力 | このコンポーネントをLinkedIn に同期するために入力したユーザーの人数。 |
-| 次のステップに進む | 次のコンポーネントがある場合、次のコンポーネントに進んだユーザーの数は?すべてのユーザーs は、これがキャンバスブランチの最後のステップである場合、自動的に進みます。 |
-| ユーザーの同期 | LinkedIn に正常に同期されたユーザーの件数。 |
+| 入力 | LinkedIn と同期するためにこのコンポーネントを入力したユーザーの数。 |
+| 次のステップに進む | 次のコンポーネントがある場合、次のコンポーネントに進んだユーザーの数は?すべてのユーザーは、これがキャンバスブランチの最後のステップである場合、自動的に進みます。 |
+| ユーザーの同期 | LinkedIn に正常に同期されたユーザー数。 |
 | 同期されていないユーザー | 照合するフィールドs がないために同期されていないユーザーの個数。 |
 | 保留中のユーザー | Braze がLinkedIn に同期するために現在処理されているユーザーの数。 |
-| ユーザーのエラー | 約13 時間の再試行後にAPI エラーのためにLinkedIn に同期されなかったユーザーの数。エラーs の潜在的な原因に、不正なLinkedIn トークンが含まれているか、またはオーディエンスがLinkedIn で削除されている可能性があります。 |
-| 廃止されたキャンバス | キャンバスを終了したユーザーの人数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生します。 |
+| エラーが発生したユーザー数 | 約13 時間の再試行後にAPI エラーのためにLinkedIn に同期されなかったユーザーの数。エラーの原因としては、LinkedIn トークンが無効である場合や、LinkedIn でオーディエンスが削除された場合などが考えられます。 |
+| 終了済みのキャンバス | キャンバスを終了したユーザーの人数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert important %}
-バルクフラッシュおよび13 時間の再試行のために、それぞれユーザー s 同期およびユーザー s エラーのメトリクスのレポートが遅延することを覚えておいてください。
+一括フラッシャーと13時間の再試行のために、同期されたユーザーとエラーが発生したユーザーのメトリクスのレポートに遅延が発生することに注意してください。
 {% endalert %}
 
 {% alert important %}
 LinkedIn は、プラットフォーム内のマッチングレートに関する追加のメトリクスを提供します。特定のオーディエンス同期の一致を確認するには、オーディエンス同期ステップメトリクスを選択して、**キャンバスステップ詳細**ページに移動します。
 <br><br>
-パートナーを**LinkedIn**、広告アカウント、およびオーディエンスとして選択し、LinkedInからオーディエンスのサイズとマッチングレートを確認します。
+パートナーを**LinkedIn**、広告アカウント、およびオーディエンスとして選択し、LinkedIn からオーディエンスのサイズとマッチングレートを確認します。
 
 ![]({% image_buster /assets/img/linkedin/linkedin11.png %})
 {% endalert %}
 
 ## トラブルシューティング
 
-{% details オーディエンスの大きさがLinkedInに入るのにどれくらいかかりますか？ %}
-LinkedIn アカウント内のオーディエンスを表示するのに最大48 時間の遅延があります。
+{% details オーディエンスサイズが LinkedIn に反映されるまでにどのくらいの時間がかかりますか？ %}
+LinkedIn アカウント内のオーディエンスを表示するのに最大48時間の遅延があります。
 {% enddetails %}
 
-{% details LinkedInが広告アカウント内に入力するための最低オーディエンス容量はいくらですか? %}
-オーディエンスには、LinkedIn アカウント内のオーディエンス容量を入力するために、少なくとも300 のメンバが含まれている必要があります。
+{% details LinkedIn が広告アカウント内に表示する最小オーディエンスサイズを教えてください。 %}
+「オーディエンスのサイズが LinkedIn アカウントに反映されるためには、少なくとも300人のメンバーを含む必要があります。
 {% enddetails %}
 
 {% details 不正なトークン エラーを受信した場合、次にどうすればよいですか? %}
-LinkedIn パートナーページで、LinkedIn アカウントを切断して再接続できます。LinkedIn 管理者に、同期する広告アカウントに対するアプリの適切な権限があることを確認します。
+LinkedIn パートナーページで、LinkedIn アカウントを切断して再接続できます。同期する広告アカウントに対する適切なアクセス許可があることを LinkedIn 管理者に確認します。
 {% enddetails %}
 
 {% details キャンバスを起動できないのはなぜですか? %}
 LinkedIn アドアカウントが、LinkedIn パートナーページでBraze に正常に接続されたことを確認してください。
-広告アカウントを選択し、新しいオーディエンスの名前を入力し、照合するフィールドs を選択していることを確認します。
+広告アカウントを選択し、新しいオーディエンスの名前を入力し、一致するフィールドを選択したことを確認します。
 {% enddetails %}
 
-{% details ユーザーs をLinkedIn に渡した後、ユーザーs が一致したかどうかを知るにはどうすればよいですか? %}
-- ユーザーs をLinkedIn に渡した後、ユーザーs が一致したかどうかを知るにはどうすればよいですか?
-LinkedIn は、ダッシュボード内のマッチレートに関する情報を提供します。LinkedIn の**Audiences** セクションで確認できます。 
-- さらに、オーディエンス同期ステップのキャンバスステップ詳細ページで、LinkedIn オーディエンスのマッチングレートを確認できます。
+{% details ユーザーを LinkedIn に渡した後、ユーザーが一致したかどうかを知るにはどうすればよいですか？ %}
+- ユーザーを LinkedIn に渡した後、ユーザーが一致したかどうかを知るにはどうすればよいですか？
+LinkedIn は、ダッシュボード内でマッチ率に関する情報を提供します。LinkedIn の \[**オーディエンス**] セクションで確認できます。 
+- さらに、オーディエンス同期ステップのキャンバスステップ詳細ページ内で、LinkedIn オーディエンスのマッチ率を確認できます。
 {% enddetails %} 
 
-{% details LinkedInが支援できるオーディエンス数は? %}
-現在、LinkedIn アドアカウントのオーディエンスの件数に制限はありません。
+{% details LinkedIn がサポート可能なオーディエンス数は? %}
+現在、LinkedIn アドアカウントのオーディエンス数に制限はありません。
 {% enddetails %}
 
-{% details ビルディングステータスでSegmentが詰まっていて、更新 dではないのはなぜですか? %}
-Segmentは、下書きまたは有効なキャンペーンで30日間継続的に使用されない場合、未使用と見なされ、ARCHIVEDに設定されます。このため、Segmentはear & quot;stuck&quot をアプリすることがあります。ARCHIVED Segmentに更新がストリーミングされ、それがビルド状態にプッシュされ、再アーカイブされる直前に、新しい更新が未使用のSegmentにストリーミングされます。
+{% details セグメントが BUILDING ステータスのままで更新されないのはなぜですか? %}
+セグメントは、下書きまたはアクティブなキャンペーンで30日間継続的に使用されない場合、未使用と見なされ、「アーカイブ済」に設定されます。このため、更新がアーカイブ済みセグメントにストリーミングされると、セグメントが BUILDING 状態に「スタック」したように見えることがあります。そのため、BUILDING 状態に追いやられ、再度アーカイブされる直前に、新しい更新が未使用セグメントにストリーミングされます。
 {% enddetails %}
 
 [1]: {% image_buster /assets/img/linkedin/linkedin1.png %}
diff --git a/_lang/ja/_hidden/private_betas/messaging_interaction_data.md b/_lang/ja/_hidden/private_betas/messaging_interaction_data.md
index 2f739e70fdc..5df1f0d9258 100644
--- a/_lang/ja/_hidden/private_betas/messaging_interaction_data.md
+++ b/_lang/ja/_hidden/private_betas/messaging_interaction_data.md
@@ -17,23 +17,23 @@ hidden: true
 2024年初頭から、ここで説明する手順に従ってメッセージングインタラクションデータを利用できるようになります。
 {% endalert %}
 
-### メッセージングインタラクションデータはいつ利用可能になりますか？
+### メッセージングインタラクションデータはいつ利用できますか。
 
-インタラクションデータはいつでも利用可能です。有効なキャンペーンs とキャンバスの場合、アクション間データはリアルタイムでいつでも利用できます。 
+インタラクションデータはいつでも利用可能です。アクティブなキャンペーンやキャンバスの場合、インタラクションデータは常にリアルタイムで利用できます。 
 
-停止したキャンペーンやキャンバスの場合、有効なキャンペーンやキャンバスでアクションデータがリターゲティング フィルターで使用されない限り、3 か月後に有効期限が切れます。期限切れのアクションデータは長期保管庫に移動され、以下に説明する手順を使用して復元しない限り、使用できません。
+停止したキャンペーンとキャンバスの場合、アクティブなキャンペーンまたはキャンバスによるリターゲティングフィルターで使用されない限り、インタラクションデータは3か月後に期限切れになります。期限切れのインタラクションデータは長期ストレージに移動され、次に説明するプロセスを使用して復元しない限り使用できません。
 
-期限切れのインターアクションは削除されず、いつでも復元できます。
+期限切れのインタラクションデータは削除されず、いつでも復元できます。
 
-#### アクション間を利用する機能
+#### インタラクションデータを使用する機能
 
-次の機能では、メッセージングのアクション間データを使用します。
+次の機能はメッセージングインタラクションデータを使用します。
 
-- リターゲティングするするフィルターは、指定したキャンペーンまたはキャンバス上でリターゲティングするします
+- 特定のキャンペーンやキャンバスでリターゲティングを行うリターゲティングフィルター
     - キャンペーンでクリックしたエイリアス
     - キャンバスステップでクリックしたエイリアス
     - クリックされた/開封されたキャンペーン
-    - クリック/オープンステップ
+    - クリックされた/開封されたステップ
     - キャンペーンからコンバージョン済み
     - キャンバスからコンバージョン済み
     - 入力したキャンバスバリエーション
@@ -44,23 +44,23 @@ hidden: true
     - キャンペーンバリアントを受信
     - キャンペーンから受信したメッセージ
     - キャンバスステップからメッセージを受信
-- キャンペーンまたは特定のタグのキャンバスをリターゲティングするリターゲティングのフィルター
+- 特定のタグのキャンペーンまたはキャンバスでリターゲティングを行うリターゲティングフィルター
     - キャンペーンまたはキャンバスからタグ付きで受信したメッセージ
     - クリック/開いたキャンペーンまたはタグ付きキャンバス
     - キャンペーンまたはCanvas With Tagから最後に受信したメッセージ
-- ユーザープロファイルに表示される**キャンペーンの受信**リストと**キャンバスメッセージの受信**リスト
+- ユーザープロファイルの \[**受信したキャンペーン**] リストおよび \[**キャンバスメッセージの受信**] リスト
 - `/users/export` エンドポイント
 - **ユーザデータ** キャンペーン およびキャンバスサマリページでのCSV エクスポート
 
-これらの機能には、期限切れのアクション間データは含まれません。これらの機能の結果に期限切れのアクション間データを含めるには、キャンペーンまたはキャンバスを期限切れのデータで復元します。
+これらの機能の結果には、期限切れのインタラクションデータは含まれません。これらの機能の結果に期限切れのインタラクションデータを含めるには、キャンペーンまたはキャンバスを期限切れのデータで復元します。
 
-#### アクション間を使用しない機能
+#### インタラクションデータを使用しない機能
 
-以下の機能**do not** は、メッセージングのアクション間データを使用します。つまり、これらの機能は、メッセージングのアクション間データの有効期限の影響を受けません。
+次の機能はメッセージングインタラクションデータを使用**しません**。つまり、これらの機能はメッセージングインタラクションデータが期限切れになっても影響を受けません。
 
 - キャンペーンとキャンバスの設定
 - キャンペーンとキャンバスの分析
-- 分析レポート(レポートビルダ、クエリビルダ、およびエンゲージメントレポートなど)
+- 分析レポート (レポートビルダ、クエリビルダ、およびエンゲージメントレポートなど)
 - Currents
 - Snowflakeデータシェア
 - セグメントエクステンション
@@ -85,7 +85,7 @@ hidden: true
     - 最後に閲覧したニュースフィード
     - ニュースフィードの閲覧数
 
-### メッセージインタラクションデータを復元するには？
+### メッセージングインタラクションデータを復元するには？
 
 インタラクションデータを復元するには、次のステップに従います。
 
@@ -94,9 +94,9 @@ hidden: true
 
 ![][1]
 
-アクション間のデータをキャンペーンs ページから復元するには、s キャンペーンを選択し、Restore inter アクションデータボタンをクリックします。
+キャンペーンを選択し、\[インタラクションデータの復元] ボタンをクリックして、キャンペーンページから複数のキャンペーンのインタラクションデータを復元することもできます。
 
-アクション間の復元にかかる時間は異なりますが、ほとんどの場合、この処理は5 ～15 分かかります。復元が完了すると、メールが表示されます。
+インタラクションデータの復元にかかる時間はさまざまですが、ほとんどの場合、このプロセスは5～15分です。復元が完了するとメールが届きます。
 
 #### タグによる復元
 
@@ -110,7 +110,7 @@ hidden: true
 
 #### タグによるリターゲット
 
-タグによってリターゲティングされるリターゲティング フィルターsを使用するキャンペーンは、期限切れから除外されません。タグでリターゲティングされるリターゲティング フィルターs には、次のものがあります。
+タグによってリターゲティングするリターゲティングフィルターを使用するキャンペーンは、期限切れの対象から除外されません。タグによってリターゲティングするリターゲティングフィルターには、次のものがあります。
 
 - キャンペーンまたはキャンバスからタグ付きで受信したメッセージ
 - クリック/開いたキャンペーンまたはタグ付きキャンバス
@@ -118,7 +118,7 @@ hidden: true
 
 ### メッセージングのインターアクション情報は、これまでいつ利用可能だった?
 
-以前は、キャンペーンまたはキャンバスでアクション間データが削除されていました。
+以前は、キャンペーンまたはキャンバスが次の場合、メッセージインタラクションデータは削除されていました。
 - 25 カレンダー月以内にメッセージが送信されなかった場合、および
 - 有効なキャンペーン、キャンバス、またはコンテンツカードのリターゲティングには使用されませんでした。
 
diff --git a/_lang/ja/_hidden/private_betas/multiple_stores.md b/_lang/ja/_hidden/private_betas/multiple_stores.md
index 9cd1eeb1e35..e6113016cc8 100644
--- a/_lang/ja/_hidden/private_betas/multiple_stores.md
+++ b/_lang/ja/_hidden/private_betas/multiple_stores.md
@@ -5,12 +5,12 @@ hidden: true
 layout: dev_guide
 ---
 
-# Shopify多店舗化支援
+# Shopify 複数店舗サポート
 
-> 複数のShopifyストアを単一のワークスペースに接続し、複数のストアをサポートする新しいベータを使用して、すべてのマーケットまたはブランドの顧客を全体的に把握できます。複数のインスタンスにまたがる取り組みを重複することなく、単一のワークスペースでオートメーション番組およびジャーニーを構築し、起動します。 
+> 複数のストアをサポートする新しいベータ版を使用して、複数の Shopify ストアを1つのワークスペースに接続し、すべての市場やブランドにわたる顧客の全体像を把握できます。複数のインスタンス間で作業を重複させることなく、単一のワークスペースでオートメーションプログラムとジャーニーを構築および起動します。 
 
 {% alert important %}
-複数のShopifyストアの対応は、バグを含む可能性があるベータ版で利用できます。この機能は、開発が続行されるにつれて変更される可能性があります。
+複数の Shopify ストアのサポートはベータ版で利用可能ですが、バグが含まれている可能性があります。この機能は、開発が続行されるにつれて変更される可能性があります。
 {% endalert %}
 
 ## 前提条件
@@ -18,40 +18,40 @@ layout: dev_guide
 | 要件 | 説明 |
 | ----------- | ----------- |
 | ストアごとに[メール サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions#create-a-group)を作成 | メール サブスクリプショングループが作成された後、設定フローの「[メールまたはSMS サブスクライバーs]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/#step-5-collect-email-or-sms-subscribers) を収集」ステップの間、指定したストアに指定します。<br><br>これは、ユーザーが準拠のためにどのストアのメールサブスクリプショングループに属しているかを追跡するために必要です。 |
-| Shopify 属性 s を使用したs、キャンペーン s、およびキャンバスのオーディットと更新 Segment | 複数のストアから収集されたカスタム属性s は、ネストされたオブジェクトの形式になります。これは、文字列値としてフォーマットされた、総合的なShopify積分で使用されている現行の構造とは異なります。そのため、複数のストアを接続して「ネストされたカスタム属性」フィルターを使用するか、「カスタム属性の変更」トリガーを更新した後に、すべてのSegments、キャンペーンs、またはキャンバスを新しい形式に更新する必要があります。<br><br>現在、どの属性sも使用していない場合は、これを無視できます。 |
-| オーディットと更新 Shopifyの別名 | 複数のストアを接続した後、`shopify_customer_id` エイリアスは{% raw %}`shopify_customer_id_{{storename}}`{% endraw %} に移行されます。新しい別名を使用するように内部を更新していることを確認します。従来のエイリアス`shopify_customer_id` は廃止されます。現在エイリアスを使用していない場合は、これを無視できます。 |
+| Shopify 属性を使用したセグメント、キャンペーン、キャンバスの監査と更新 | 複数のストアから収集されたカスタム属性s は、ネストされたオブジェクトの形式になります。これは、文字列値としてフォーマットされた、総合的なShopify積分で使用されている現行の構造とは異なります。そのため、複数のストアを接続して「階層化カスタム属性」フィルターを使用するか、「カスタム属性の変更」トリガーイベントを更新した後に、すべてのセグメント、キャンペーン、またはキャンバスを新しい形式に更新する必要があります。<br><br>現在、どの属性sも使用していない場合は、これを無視できます。 |
+| Shopify エイリアスの監査と更新 | 複数のストアを接続した後、`shopify_customer_id` エイリアスは{% raw %}`shopify_customer_id_{{storename}}`{% endraw %} に移行されます。新しいエイリアスを使用するようにすべての内部システムを更新していることを確認します。従来のエイリアス `shopify_customer_id` は廃止されます。現在エイリアスを使用していない場合は、これを無視できます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合
-Braze のマルチストアサポートでは、次のことが可能です。
-- 店舗全体の顧客を360°表示
-- 集約ストアデータを使用して、顧客s のSegments を作成する 
+Braze の複数ストアサポートでは、次のことが可能です。
+- 店舗全体の顧客を360度見渡すことができる
+- 集計ストアデータを使用して顧客のセグメントを作成する 
 - 顧客が別の店舗を移動するときにメッセージングまたはジャーニーを設定する
-- メールやSMSサブスクリプションを複数の店舗で管理する
+- 複数のストア間でメールと SMS のサブスクリプションを管理する
 
 ### 店舗の増設
-1. 最初のストアをインストールしたら、**\+ Connect New Store** オプションを選択します。<br>![][1]{: style="max-width:70%;"}<br><br>
-2. この新しいストアのオンボーディングフローを実行するように求められます。詳しくは、[Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/)のセットアップガイドを参照してください。<br><br>前のストアの設定s は引き継ぐことができますが、オンボーディングの進行に応じて設定s を更新できます。<br><br>
-3. 収集メールまたはSMS サブスクライバー s ステップの場合:
-- ストアごとに適切なメールとSMSサブスクリプションをアプリ収集するには、ストア設定ごとに一意のサブスクリプショングループsを割り当てる必要があります。 
-- ここでは、**do not** enable "Override existing global state for ユーザー s" を有効にすることをお勧めします。これは、複数のストアとやり取りする場合に顧客s をグローバルに配信停止できるためです。<br><br>
+1. 最初のストアをインストールしたら、\[**+新しいストアの接続**] オプションを選択します。<br>![][1]{: style="max-width:70%;"}<br><br>
+2. この新しいストアのオンボーディングフローを実行するように求められます。詳しくは、[Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/)のセットアップガイドを参照してください。<br><br>前のストアの設定は引き継ぐことができますが、オンボーディングの進行に応じて設定を更新できます。<br><br>
+3. メールまたは SMS サブスクライバーの収集ステップの場合:
+- 各ストアのメールおよび SMS サブスクリプションを適切に収集するには、各ストア設定に固有のサブスクリプショングループを割り当てる必要があります。 
+- 「ユーザーの既存のグローバル状態を上書き」を有効に**しない**ことをお勧めします。これは、顧客が複数のストアとやり取りした場合に、グローバルに配信停止される可能性があるためです。<br><br>
 4. 必要な数の店舗に対してこのインストールを繰り返します。<br><br>
-5. 各ストアのインテグレーションを表示し、詳細設定を設定するには、ドロップダウンメニューでストアを選択します。<br>![][2]{: style="max-width:70%;"}
+5. 各ストアの統合を表示し、詳細設定を構成するには、ドロップダウンメニューでストアを選択します。<br>![][2]{: style="max-width:70%;"}
 
 ## Shopify情報
 
 ### Shopify別名
 
-{% raw %}複数のストアを接続すると、すべての受信Shopify ユーザーs には、既存のエイリアス`shopify_customer_id` に加えて、新しいエイリアス`shopify_customer_id_{{storename}}` が追加されます。`shopify_customer_id` はレガシーエイリアスであり、この機能が一般的に使用可能な場合は廃止されることに注意してください。前に進む新しいエイリアスを使用するように移行する必要があります。 {% endraw %}
+{% raw %}複数のストアに接続すると、すべての新しい Shopify ユーザーは、既存のエイリアス `shopify_customer_id` に加えて新しいエイリアス `shopify_customer_id_{{storename}}` を持つことになります。`shopify_customer_id` は従来のエイリアスであり、この機能が一般公開されると非推奨になります。今後は、新しいエイリアスの使用に移行する必要があります。 {% endraw %}
 
 ### Shopify カスタム属性s
 
-複数のストアを接続した後、次の属性s は、ストアごとの値と集計値を含むネストされたオブジェクトとして同期されます。
+複数のストアを接続した後、次の属性は、ストアごとの値と集計値を含む階層化オブジェクトとして同期されます。
 - `shopify_tags`
-- `shopify_order_count` (ヒストリカル・バックフィルでのみ使用可能)
-- `shopify_total_spent` (ヒストリカル・バックフィルでのみ使用可能)
+- `shopify_order_count` (履歴バックフィル経由でのみ使用可能)
+- `shopify_total_spent` (履歴バックフィル経由でのみ使用可能)
 
-カスタムイベント s を使用してSegmentを作成または編集するには、**ネストされたカスタム属性** フィルターを選択し、ネストされた属性を見つけます。オブジェクト内のパスまたはフィールドを特定するには、[Generate Schema]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support#generate-schema)ツールを使用します。ネストされた属性s を選択すると、プラスボタンの付いたフィールドが選択した属性s の横に耳をアプリし、パスを指定します。ネストされた属性s の詳細については、[ネストされたカスタム属性s]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/) を参照してください。
+セグメントの作成または編集時にカスタムイベントを使用するには、\[**階層化カスタム属性**] フィルターを選択し、階層化属性を見つけます。オブジェクト内の特定のパスまたはフィールドを特定するには、\[[スキーマの生成]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support#generate-schema)] ツールを使用します。階層化属性を選択すると、選択した属性の横にプラスボタンの付いたフィールドが表示され、パスを指定できます。階層化属性の詳細については、[階層化カスタム属性]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/) を参照してください。
 
 ![3]{:style="max-width:70%;"}
 
@@ -61,16 +61,16 @@ Braze のマルチストアサポートでは、次のことが可能です。
 
 ### Shopify カスタムイベントs
 
-複数のストアを接続すると、受信Shopify カスタムイベントs に新しいイベントプロパティ`shopify_storefront` が含まれるようになります。[Shopifyデータプロセッシング]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_data_processing#supported-shopify-events)を参照して、このインテグレーションでサポートされるすべてのカスタムイベントを確認してください。このイベントプロパティは、イベントの送信元のShopifyストアドメインを提供します。
+複数のストアを接続すると、新たな Shopifyカスタムイベントに新しいイベントプロパティ `shopify_storefront` が含まれるようになります。[Shopifyデータプロセッシング]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_data_processing#supported-shopify-events)を参照して、このインテグレーションでサポートされるすべてのカスタムイベントを確認してください。このイベントプロパティは、イベントの送信元のShopifyストアドメインを提供します。
 
-### アクションベースの配信またはコンバージョン "トラッキング
+### アクションベースの配信またはコンバージョントラッキング
 
-指定したストアでアクションs を完了するユーザーにトリガー メッセージングするには:
+特定のストアでアクションを完了したユーザーにメッセージングをトリガーするには、以下を実行します。
 
 1. キャンペーンの**Schedule Delivery** ステップに移動します。
 2. トリガーとして**カスタムイベントを実行**を選択します。
 ![5]{:style="max-width:70%;"}
-3. **Shopify_created_order**、**プロパティ フィルターを追加s** チェックボックスなど、トリガーの行動としてShopifyを選択します。
+3. トリガーイベントとして Shopify イベントを選択します (\[**shopify_created_order**]、\[**プロパティフィルターの追加**] チェックボックスなど)。
 ![6]{:style="max-width:70%;"}
 4. **Add Filter**ドロップダウンで**Basic Property**を選択します。
 5. **Shopify_storefront**を選択し、ストアのフルShopify領域を入力します。
@@ -82,7 +82,7 @@ Braze のマルチストアサポートでは、次のことが可能です。
 エイリアス、{% raw %}`shopify_customer_id_{{storefront_domain}}`、`shopify_email`、または`shopify_phone`、{% endraw %} を使用して、ユーザーのShopify 顧客 ID、メールアドレス、または電話番号がすでにBraze内に存在する場合は、既存のユーザープロファイルを更新します。これらの別名がBraze内に存在しない場合は、新しいユーザープロファイルを作成します。ユーザーのデータ(都市など)は、同じユーザーの複数のShopifyストア間で異なることがあります。このような場合、Braze は、最新のアクティビティを持つストアからユーザープロファイルを必ず更新します。 
 
 {% alert warning %}
-Braze は、最新のアクティビティを持つストアからShopify 顧客データを持つユーザープロファイルを更新します。つまり、メール、電話番号、送信側の電話機、市区町村など、任意の属性sは、最新のストアアクティビティで上書きできます。たとえば、ユーザーが2つの別のストアに別の電話番号を持っている場合、Brazeは、最新のアクティビティを持つストアの電話番号でユーザープロファイルを更新します。
+Braze は、最新のアクティビティを持つストアからShopify 顧客データを持つユーザープロファイルを更新します。つまり、メール、電話番号、送信元の電話番号、都市などの属性は、最新のストアアクティビティで上書きできます。たとえば、ユーザーが2つの別のストアに別の電話番号を持っている場合、Brazeは、最新のアクティビティを持つストアの電話番号でユーザープロファイルを更新します。
 {% endalert %}
 
 [1]: {% image_buster /assets/img/multiple_stores.png %}
diff --git a/_lang/ja/_hidden/private_betas/pick_up_where_you_left_off.md b/_lang/ja/_hidden/private_betas/pick_up_where_you_left_off.md
index 5901ea44431..847cd372d8d 100644
--- a/_lang/ja/_hidden/private_betas/pick_up_where_you_left_off.md
+++ b/_lang/ja/_hidden/private_betas/pick_up_where_you_left_off.md
@@ -1,18 +1,18 @@
 ---
-nav_title: オフにした場所でピックアップ
-article_title: オフにした場所でピックアップ
+nav_title: 中断したところから再開
+article_title: 中断したところから再開
 permalink: "/pick_up_where_you_left_off/"
-description: "Brazeで出発した場所をピックアップする方法を学習します。"
+description: "Braze で中断したところから再開する方法を学習します。"
 page_type: reference
 hidden: true
 ---
 
-# 離れた場所をピックアップ
+# 中断したところから再開
 
-Braze ダッシュボード内のどこから離れたかを、最近編集または作成したファイルに簡単に取り込むことができます。このセクションアプリは、Braze ダッシュボードの**Home** ページの上部にあります。
+Braze ダッシュボードでは、最近編集または作成したファイルに簡単にアクセスして、中断したところから再開できます。このセクションは、Braze ダッシュボードの \[**ホーム**] ページの上部に表示されます。
 
 {% alert important %}
-休んだ場所をピックアップするのは、現在初期アクセス中です。この初期のアクセスに参加したい場合は、Braze アカウントマネージャーに連絡してください。
+「中断したところから再開」機能は、現在早期アクセス中です。この初期のアクセスに参加したい場合は、Braze アカウントマネージャーに連絡してください。
 {% endalert %}
 
 ![][1]
@@ -27,7 +27,7 @@ Braze ダッシュボード内のどこから離れたかを、最近編集ま
 
 ### 最近編集したコンテンツにアクセスする
 
-最近編集または作成したキャンペーン、キャンバス、およびSegmentを再訪問することができます。こうすることで、Braze ダッシュボードに戻るたびに、離れた場所を拾うことができます。
+最近編集または作成したキャンペーン、キャンバス、およびSegmentを再訪問することができます。こうすることで、Braze ダッシュボードに戻るたびに、中断したところから再開できます。
 
 ### コンテンツタイプとステータスタグ
 
diff --git a/_lang/ja/_hidden/private_betas/post_duplicate_canvas.md b/_lang/ja/_hidden/private_betas/post_duplicate_canvas.md
index ee54906cef0..4573bd2da56 100644
--- a/_lang/ja/_hidden/private_betas/post_duplicate_canvas.md
+++ b/_lang/ja/_hidden/private_betas/post_duplicate_canvas.md
@@ -4,19 +4,19 @@ layout: api_page
 page_type: reference
 hidden: true
 permalink: /api/endpoints/messaging/duplicate_canvases/
-description: "この記事では、キャンバスの複製エンドポイントについて詳しく説明します。"
+description: "この記事では、「キャンバスの複製」エンドポイントの詳細について説明します。"
 ---
 
 {% api %}
 # API を使用したキャンバスの複製
 {% apimethod post core_endpoint|{1} %}
-/キャンバス/複製
+/canvas/duplicate
 {% endapimethod %}
 
-> このエンドポイントを使用して、キャンバスを複製します。このAPI エンドポイントは、[Braze ダッシュボード][1] のキャンバスの複製に似ています。
+> このエンドポイントを使用して、キャンバスを複製します。この API エンドポイントは、[Braze ダッシュボードでのキャンバスの複製][1]に似ています。
 
 {% alert important %}
-API を使用したキャンバスの複製は、現在初期アクセス中です。早いアクセスに参加したい場合は、Braze アカウントマネージャーに連絡してください。
+API を介したキャンバスの複製は、現在、早期アクセスの段階です。早いアクセスに参加したい場合は、Braze アカウントマネージャーに連絡してください。
 {% endalert %}
 
 ## 前提条件
@@ -25,7 +25,7 @@ API を使用したキャンバスの複製は、現在初期アクセス中で
 
 ## レート制限
 
-このエンドポイントは、1 分あたり100 個のAPI コールに制限されます。
+このエンドポイントは、1分あたり100個のAPIコールに制限されます。
 
 ## 要求本文:
 
@@ -47,15 +47,15 @@ Authorization: Bearer YOUR-REST-API-KEY
 
 | パラメータ | required | データ型 | 説明 |
 | --------- | ---------| --------- | ----------- |
-|`canvas_id`| 必須 | string | [キャンバス識別子]({{site.baseurl}}/api/identifier_types/)を参照してください。 |
-|`name`| 必須 | string | 作成されるキャンバスの名前。 |
+|`canvas_id`| required | string | [キャンバス識別子]({{site.baseurl}}/api/identifier_types/)を参照してください。 |
+|`name`| required | string | 作成されるキャンバスの名前。 |
 |`description`| オプション | string | 結果のキャンバスの記述フィールド。 |
 |`tag_names` | オプション | string | 作成されるキャンバスのタグ。これらは存在するタグs である必要があります。リクエストに新しいタグs を追加すると、元のキャンバスにあったすべてのタグs が上書きされます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 応答
 
-このエンドポイントは`202` ステータス コードを返し、キャンバスの作成は非同期に行われます。[セキュリティイベントダウン読み込む][2]を使用すると、キャンバスがいつ複製され、どのAPI キーによって記録されたかを確認できます。
+このエンドポイントは `202` ステータスコードを返し、キャンバス作成は非同期に行われます。[セキュリティイベントダウン読み込む][2]を使用すると、キャンバスがいつ複製され、どのAPI キーによって記録されたかを確認できます。
 
 [1]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/duplicating_segments_and_campaigns#duplicating-segments-campaigns-and-canvases
 [2]: {{site.baseurl}}/user_guide/administrative/app_settings/company_settings/security_settings/?redirected=true#security-event-download
diff --git a/_lang/ja/_hidden/private_betas/post_user_track_synchronous.md b/_lang/ja/_hidden/private_betas/post_user_track_synchronous.md
index 2b1a0b21738..e21967df1b9 100644
--- a/_lang/ja/_hidden/private_betas/post_user_track_synchronous.md
+++ b/_lang/ja/_hidden/private_betas/post_user_track_synchronous.md
@@ -5,7 +5,7 @@ hidden: true
 permalink: /post_user_track_synchronous/
 layout: api_page
 page_type: reference
-description: "この記事では、同期TrackユーザーBrazeエンドポイントの詳細について概説する。"
+description: "この記事では、「ユーザー同期追跡」Braze エンドポイントの詳細について説明します。"
 
 ---
 {% api %}
@@ -14,7 +14,7 @@ description: "この記事では、同期TrackユーザーBrazeエンドポイ
 /users/track/sync
 {% endapimethod %}
 
-> このエンドポイントを使用して、カスタム・イベントや購入を記録し、ユーザー・プロファイル属性を同期的に更新する。このエンドポイントは、非同期でユーザープロファイルを更新する[`/users/track` エンド]({{site.baseurl}}/api/endpoints/user_data/post_user_track)ポイントと同様の機能を持つ。
+> このエンドポイントを使用して、カスタムイベントと購入を記録し、ユーザープロファイル属性を同期的に更新します。このエンドポイントは、ユーザープロファイルを非同期に更新する [`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track)と同様に機能します。
 
 {% alert important %}
 このエンドポイントは現在ベータ版である。このベータ版への参加に興味がある場合は、Brazeのアカウントマネージャーに連絡すること。
@@ -22,13 +22,13 @@ description: "この記事では、同期TrackユーザーBrazeエンドポイ
 
 ## 同期APIコールと非同期APIコール
 
-非同期呼び出しでは、APIはステータスコード`201` を返し、リクエストが正常に受信、理解、受け入れられたことを示す。しかし、これはあなたの要請が完全に完了したことを意味するものではない。
+非同期呼び出しでは、API はステータスコード `201` を返し、リクエストが正常に受信、理解、受け入れられたことを示します。ただし、これは、リクエストが完全に完了したわけではありません。
 
-同期呼び出しでは、APIはステータスコード`201` を返し、リクエストが正常に受信され、理解され、受け入れられ、完了したことを示す。コールレスポンスには、操作の結果として、選択されたユーザープロファイルの フィールドが表示される。
+同期呼び出しでは、API は、リクエストが正常に受信され、理解され、受け入れられ、完了したことを示すステータスコード `201` を返します。呼び出し応答には、操作の結果として、選択されたユーザープロファイルのフィールドが表示されます。
 
-このエンドポイントは、`/users/track` エンドポイントよりも低いレート制限を持っている（下記の[レート制限を](#rate-limit)参照）。各`/users/track/sync` リクエストは、1つのイベント・オブジェクト、1つのアトリビュート・オブジェ クト**、または**1つの購買オブジェクトのみを含むことができる。このエンドポイントは、同期呼び出しが必要なユーザープロファイル更新のために予約されるべきである。健全な導入のためには、`/users/track/sync` と`/users/track` を併用することをお勧めする。
+このエンドポイントは、`/users/track` エンドポイントよりも低いレート制限を持っている（下記の[レート制限を](#rate-limit)参照）。各 `/users/track/sync` リクエストには、1つのイベントオブジェクト、1つの属性オブジェクト、**また**は1つの購入オブジェクトのみを含めることができます。このエンドポイントは、同期呼び出しが必要なユーザープロファイルの更新用に予約する必要があります。健全な実装のためには、`/users/track/sync` と`/users/track` を併用することをお勧めします。
 
-例えば、同じユーザーに対して短時間に連続してリクエストを送信する場合、非同期の`/users/track` エンドポイントではレースコンディションが発生する可能性があるが、`/users/track/sync` エンドポイントでは、`2XX` レスポンスを受信した後に、それらのリクエストを順番に送信することができる。
+例えば、同じユーザーに対して短時間に連続してリクエストを送信する場合、非同期の `/users/track` エンドポイントでは競合が発生する可能性がありますが、`/users/track/sync` エンドポイントでは、`2XX` レスポンスを受信した後に、それらのリクエストをそれぞれ順番に送信することができます。
 
 ## 前提条件
 
@@ -38,7 +38,7 @@ description: "この記事では、同期TrackユーザーBrazeエンドポイ
 
 ## レート制限
 
-このエンドポイントには、すべての顧客に対して、1分あたり500リクエストという基本速度制限が適用される。`/users/track/sync` 各リクエストは、最大1つのイベントオブジェクト、1つのアトリビュートオブジェクト、または1つの購買オブジェクトを含むことができる。各オブジェクト（イベント、アトリビュート、購入アレイ）は、それぞれ1人のユーザーを更新することができる。
+すべての顧客に対して、このエンドポイントに対して1分あたり500リクエストの基本スピード制限を適用します。各 `/users/track/sync` リクエストには、最大1つのイベントオブジェクト、1つの属性オブジェクト、または1つの購入オブジェクトを含めることができます。それぞれのオブジェクト (イベント、属性、および購入配列) は、それぞれ1つのユーザーを更新できます。
 
 ## 要求本文:
 
@@ -63,9 +63,9 @@ Authorization: Bearer YOUR_REST_API_KEY
 
 | パラメーター | required | データ型 | 説明 |
 | --------- | ---------| --------- | ----------- |
-| `attributes` | オプション | つの属性オブジェクト | [ユーザー 属性  object]({{site.baseurl}}/api/objects_filters/user_attributes_object/)参照 |
+| `attributes` | オプション | つの属性オブジェクト | 「[ユーザー属性オブジェクト]({{site.baseurl}}/api/objects_filters/user_attributes_object/)」を参照 |
 | `events` | オプション | イベントオブジェクト | [イベントオブジェクト]({{site.baseurl}}/api/objects_filters/event_object/)を参照してください |
-| `purchases` | オプション | 購入対象は1つ | [購入オブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/)を参照してください |
+| `purchases` | オプション | 1つの購入オブジェクト | [購入オブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/)を参照してください |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 応答
@@ -74,7 +74,7 @@ Authorization: Bearer YOUR_REST_API_KEY
 
 ### 成功のメッセージ
 
-成功したメッセージは、更新されたユーザー・プロファイル・データに関する情報を含む、以下のレスポンスを返す。
+成功したメッセージは、更新されたユーザープロファイルデータに関する情報を含む、以下のレスポンスを返します。
 
 ```json
 {
@@ -271,13 +271,13 @@ curl --location --request POST 'https://rest.iad-01.braze.com/users/track/sync'
 
 ### 非同期エンドポイントと同期エンドポイントのどちらを使うべきか？
 
-ほとんどのプロファイル更新には、`/users/track` エンドポイントが最も適している。しかし、`/users/track/sync` エンドポイントは、同じユーザーに対する連続したリクエストが急激に発生し、レースコンディションが発生している場合に便利である。
+ほとんどのプロファイル更新では、`/users/track` エンドポイントが最適に機能します。これは、レート制限が高く、柔軟に要求を一括処理できるためです。ただし、`/users/track/sync` エンドポイントは、同じユーザーに対する短時間の連続するリクエストによって競合が発生している場合に便利です。
 
 ### レスポンスタイムは`/users/track` エンドポイントと異なるか？
 
-同期呼び出しでは、APIはリクエストが完了するまで応答を返すのを待つ。その結果、同期リクエストは、非同期リクエストよりも平均して`/users/track` に時間がかかる。リクエストの大半は、数秒以内に返信される。
+同期呼び出しの場合、API はリクエストが完了するまで応答を返すのを待ちます。その結果、同期要求は `/users/track` への非同期要求よりも平均して時間がかかります。大半のリクエストでは、数秒以内にレスポンスが返ってきます。
 
-### 複数のリクエストを同時に送ることは可能か？
+### 複数のリクエストを同時に送信できますか？
 
 リクエストが異なるユーザーに対するものであるか、各リクエストが1人のユーザーに対して異なるアトリビュート、イベント、購入を更新する限りは、そうだ。
 
@@ -285,8 +285,8 @@ curl --location --request POST 'https://rest.iad-01.braze.com/users/track/sync'
 
 ### なぜレスポンスの値が元のリクエストの値と一致しないのか？
 
-リクエストは完了したが、カスタム属性の値が更新されなかった可能性がある。これは、カスタム属性の更新が最大文字数を超える場合、配列の制限を超える場合、またはユーザーがBrazeに存在せず、`_update_existing_only = true` 。
+リクエストは完了したが、カスタム属性の値が更新されなかった可能性がある。これは、カスタム属性の更新が最大文字数を超えている場合、配列の制限を超えている場合、またはユーザーが Braze に存在せず `_update_existing_only = true` がある場合に発生する可能性があります。
 
-このような場合、リクエストは完了したものの、希望する更新が行われなかったことを示す応答として扱う。このような現象が起こる理由を、上記から考えてトラブルシューティングを行う。
+このような場合、リクエストは完了したものの、希望する更新が行われなかったことを示しているものとして応答を処理します。このような現象が起こる理由を、上記から考えてトラブルシューティングを行う。
 
 {% endapi %}
diff --git a/_lang/ja/_hidden/private_betas/shopify_collections_sync.md b/_lang/ja/_hidden/private_betas/shopify_collections_sync.md
index 9677638f91b..34920335d22 100644
--- a/_lang/ja/_hidden/private_betas/shopify_collections_sync.md
+++ b/_lang/ja/_hidden/private_betas/shopify_collections_sync.md
@@ -8,31 +8,31 @@ hidden: true
 
 # Shopifyコレクション同期ベータ版
 
-> Shopifyのコレクション同期では、商品をコレクションにグループ化することができ、顧客はカテゴリー別に商品を見つけることができる。よりシームレスな買い物体験のために、ショップのコレクション内のアイテムをBrazeのメッセージに組み込むことができる。
+> Shopify のコレクション同期では、製品をコレクションにグループ化することができ、顧客はカテゴリー別に商品を見つけることができます。よりシームレスなショッピング体験のために、ショップのコレクション内のアイテムを Braze メッセージングに組み込むことができます。
 
 {% alert important %}
-Shopifyコレクション同期は現在ベータ版である。ベータ版への参加を希望する場合は、Brazeのアカウントマネージャーに連絡すること。
+Shopify コレクション同期は現在ベータ版です。ベータ版への参加を希望する場合は、Brazeのアカウントマネージャーに連絡すること。
 {% endalert %}
 
 ## Shopifyのコレクション同期を設定する
 
-ShopifyストアからBrazeに商品を同期するには、[Shopifyを統合する]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify#setting-up-shopify-in-braze) **商品の同期**ステップで、**Shopifyコレクションを同期**するチェックボックスを選択する。<br><br>![Shopify商品同期のステップ4で、「Shopifyコレクションを同期」チェックボックスを選択する。][1]
+Shopify ストアから Braze に製品を同期するには、[Shopify の統合]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify#setting-up-shopify-in-braze)の \[**製品の同期**] ステップで \[**Shopify コレクションを同期する**] チェックボックスをオンにします。<br><br>![\[Shopify コレクションを同期する] チェックボックスがオンの状態の Shopify 製品同期のステップ4。][1]
 
-商品が同期されると、Shopifyのカタログを見ることで、どの商品がコレクションに関連付けられているかを確認することができる。<br><br>![ベストセラー」と「フロントページ」のコレクションにある商品を示すカタログ・テーブルの行。][2]
+製品が同期されると、Shopify カタログを見ることで、どの製品がコレクションに関連付けられているかを確認することができます。<br><br>![ベストセラー」と「フロントページ」のコレクションにある商品を示すカタログ・テーブルの行。][2]
 
-Shopifyカタログから、**Selections**タブでShopifyコレクションを見ることができる。<br><br>![セレクション」タブには、「ベストセラー」と「フロントページ」という2つのコレクションが表示されている。][3]
+Shopifyカタログから、**Selections**タブでShopifyコレクションを見ることができる。<br><br>![「ベストセラー」と「フロントページという2つのコレクションのリストが表示された \[選択] タブ][3]
 
 ### ベータ版機能
 
-- ブレイズは最大30コレクションをサポートする
-- 現時点では、コレクションのソート順は維持・サポートされていない。今のところ、ソート順は以下に基づいている：
-    - あなたのコレクションに最近追加されたアイテム。
+- Braze は最大30のコレクションをサポート予定
+- 現時点では、コレクションのソート順は維持・サポートされていない。今のところ、ソート順は以下に基づいています。
+    - コレクションに最近追加されたアイテム。
     - 連続シンク中にアイテムが更新される順序。
-    - Shopifyコレクションの選択タブで選択した順序。
+    - Shopify コレクションの選択タブで選択した順序。
 
 ## Shopifyのコレクションを使う
 
-Shopifyのコレクションを使って、[Brazeのセレクションを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)使うのと同じように、キャンペーンの各ユーザーにメッセージをパーソナライズしよう。
+Shopify コレクションを使用して、[Braze セレクション]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)を使用する場合と同様に、キャンペーンの各ユーザーに合わせてメッセージをパーソナライズします。
 
 {% alert warning %}
 ベータ版では、以下のような挙動に注意すること：<br><br>Shopifyコレクションの説明やフィルター設定を更新すると、Shopifyコレクションの同期が壊れてしまう。その結果、Shopifyコレクションは期待通りに機能しなくなる。
@@ -40,23 +40,23 @@ Shopifyのコレクションを使って、[Brazeのセレクションを]({{sit
 
 ### ステップ1:Shopifyコレクションのソート順を設定する
 
-1. Shopifyコレクションの選択タブで**Sort Orderを**選択して、Shopifyコレクションの結果を返す順序を指定する。これにはソート順をランダムにするオプションも含まれている。
-2. **リミット番号の**結果の最大数（最大50）を入力する。
-3. **Update Selectionを**選択する。
+1. Shopify コレクションの \[選択] タブで \[**ソート順**] を選択して、Shopify コレクションの結果が返される順序を指定します。これにはソート順をランダムにするオプションも含まれている。
+2. \[**上限数**] に結果の最大数 (50まで) を入力します。
+3. \[**選択の更新**] を選択します。
 
-![フィルター設定、ソートタイプ、結果制限を選択できる。][4]
+![フィルター設定、ソートタイプ、結果の制限を選択できる \[選択の編集] ページ。][4]
 
 ### ステップ2:キャンペーンでコレクションを使用する
 
 1. キャンペーンを作成し、メッセージコンポーザーで**「+パーソナライズ**」を選択する。
-2. 以下を選択する：<br>**\- カタログ項目を** **パーソナライズの種類に**する<br>\- カタログ名<br>\- アイテム選択方法<br>\- セレクション名（Shopifyコレクション名） <br>\- メッセージに表示する情報
+2. 以下を選択します。<br>- **カタログ項目**を**パーソナライゼーションタイプ**として選択<br>\- カタログ名<br>\- アイテム選択方法<br>\- セレクション名（Shopifyコレクション名） <br>\- メッセージに表示する情報
 
 {: start="3"}
-3\.Liquidのスニペットをコピーして、メッセージに表示したい場所に貼り付ける。
+3\.Liquid スニペットをコピーして、メッセージ内で情報を表示する場所に貼り付けます。
 
-![パーソナライゼーションの追加」セクションには、カタログ、アイテムの選択方法、表示する情報を選択するフィールドがある。][5]{: style="max-width:30%;"}
+![カタログ、項目選択方法、表示する情報を選択するフィールドがある「パーソナライゼーションの追加」セクション。][5]{: style="max-width:30%;"}
 
-#### 選考結果が流動的
+#### セレクション結果内の Liquid
 
 カスタム属性やカスタム・イベントなど、カタログ内の結果を使用すると、選択したユーザーごとに異なる結果が返される可能性がある。
 
diff --git a/_lang/ja/_hidden/private_betas/shopify_user_reconciliation.md b/_lang/ja/_hidden/private_betas/shopify_user_reconciliation.md
index c1bc4d7d06b..50e00cacded 100644
--- a/_lang/ja/_hidden/private_betas/shopify_user_reconciliation.md
+++ b/_lang/ja/_hidden/private_betas/shopify_user_reconciliation.md
@@ -11,21 +11,21 @@ hidden: true
 > Shopifyインテグレーションでは、チェックアウトフローに達したときにユーザーの端末IDと個人情報を照合し、そこでShopify Webhookな事象を実行します。
 
 {% alert note %}
-この機能は現在ベータ版です。興味がある場合は、顧客のサクセスマネージャーまたはアカウントマネージャーにお問い合わせください。
+この機能は現在ベータ版です。興味がある場合は、カスタマーサクセスマネージャーまたはアカウントマネージャーにお問い合わせください。
 {% endalert %}
 
 Shopifyのサインアップとログインフローによるユーザーの調整をサポートするために、チェックアウトフロー以外のShopifyストアにJavaScript 機能を自動的に実装できます。Braze は、以下の例のように、Shopifyストアに`type="email"` を持つフォームが表示されている場合には、自動的に関数を実装します。
 
 ![1]{:style="max-width:60%;"}
 
-この機能が呼び出されると、ウェブ上の匿名ユーザーが、提供されたメールの住所に関連付けられます。今後、当社が使用するShopifyの識別子(ShopifyのカスタマーID、メールアドレス、電話番号など)を参照するすべての行動は、一致があれば同じBraze ユーザーに割り当てられます。
+この関数が呼び出されると、Web 上の匿名ユーザーが指定されたメールアドレスに関連付けられます。今後、当社が使用するShopifyの識別子(ShopifyのカスタマーID、メールアドレス、電話番号など)を参照するすべての行動は、一致があれば同じBraze ユーザーに割り当てられます。
 
 ## 考慮事項
 
 {% alert important %}
-Braze は、顧客のShopify サイトの`type="email"` を含むすべてのフォームに精通していません。これは、機能が、ユーザー照合更新に使用されるべき入力フィールドを見逃したり、間違ったフィールドをピックアップして、間違ったメールアドレス(例えば、照会フォーム)をユーザープロファイルに設定する可能性があることを意味します。
+Braze は、顧客のShopify サイトの`type="email"` を含むすべてのフォームに精通していません。これは、関数がユーザー調整に使用する必要がある入力フィールドを見逃したり、誤ったフィールドを選択してユーザープロファイルに誤ったメールアドレス (たとえば、Referralフォーム) を設定したりする可能性があることを意味します。
 {% endalert %}
 
-Shopify施設でサポートされているすべてのフォームを調査し、このベータソリューションがどのようにしてあなたの要求に効果的に対応できるかを評価することをお勧めします。このベータ機能を利用することで、Shopifyフォームに手動で変更を加えることで、予期しない動作が発生する可能性があることがわかります。
+Shopify サイトでサポートされているすべての形式を調査し、このベータソリューションがお客様の要件にどのように効果的に対応できるかを評価することをお勧めします。このベータ機能を利用することで、Shopifyフォームに手動で変更を加えることで、予期しない動作が発生する可能性があることがわかります。
 
 [1]: {% image_buster /assets/img/shopify_type_email.png %}
diff --git a/_lang/ja/_hidden/private_betas/sms_traffic_pumping_fraud.md b/_lang/ja/_hidden/private_betas/sms_traffic_pumping_fraud.md
index 34f9e2851f1..4ef5c24a9d6 100644
--- a/_lang/ja/_hidden/private_betas/sms_traffic_pumping_fraud.md
+++ b/_lang/ja/_hidden/private_betas/sms_traffic_pumping_fraud.md
@@ -17,22 +17,22 @@ SMSトラフィックポンピングは、SMS分野で増加している脅威
 
 Brazeは現在、米国が禁輸している国およびトラフィックポンピングのリスクが高いとされる国のSMSブロックリストを維持しており、それは[our documentation]({{site.baseurl}}/sms_country_blocklist)で参照できます。これらの国コードを持つ電話番号へのすべての送信試行はブロックされます。
 
-さらに、BrazeはSMS地理的許可リストを導入しており、送信可能な国に対する制御を強化することで、不正行為からさらに保護します。
+さらに、Braze は SMS 地理的許可リストを導入しており、送信可能な国を制限することで、不正行為からの保護を一層強化します。
 
 ### ブランドをSMSポンピング詐欺から守るにはどうすればよいですか？ 
 
 自分を守る方法はいくつかあります。例えば、 
-- **毎日のSMS送信量のスパイクや異常を監視する:**
+- **毎日の SMS 送信量を監視して、スパイクや異常がないか確認します。**
     - 異常に多くのメッセージが送信された場合に上限を設定し通知するために、[キャンペーンの制限とアラート]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/campaign_alerts/)を設定することをお勧めします。
     - メッセージ送信の異常なスパイクは、トラフィックポンピングを示している可能性があります。
     - 意図的なオプトイン促進戦略以外で、短期間に異常に多くのオプトインが発生することは、トラフィックポンピングを示している可能性があります。
 - **オンラインの電話番号キャプチャフォームのセキュリティを向上させる:**
     - Braze [SMSサインアップフォームテンプレート]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/templates/phone_number_capture)は、電話番号の長さと形式を検証するなど、すぐに使えるセキュリティ対策を提供します。ターゲット顧客に合わせた国コードを持つ電話番号のみを収集するようにフォームを設定することもできます。
         - 例えば、米国と英国でのみビジネスを行っている場合、+1および+44の国コードのみを収集するようにフォームを設定します（技術的な詳細は[our documentation]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/templates/phone_number_capture/#step-2-customize-your-phone-number-input-component)で確認できます）。
-    - Web サイトでカスタム電話番号キャプチャを構築する場合、電話番号の長さと形式を検証するルールを設定し、電話番号を収集する前にフォームが完全に完了していることを確認することをお勧めします。必ず<b>開発<b"}または技術チームと協力して、最大限の保護のためにフォーム入力をクライアント側とサーバー側の両方で検証してください。
+    - Web サイトでカスタム電話番号キャプチャを構築する場合、電話番号の長さと形式を検証するルールを設定し、電話番号を収集する前にフォームが完全に完了していることを確認することをお勧めします。開発チームまたは技術チームと連携して、最大限の保護を得るために、クライアント側とサーバー側の両方のフォーム入力を検証してください。
         - さらに、フォームが自動化されたプロセスではなく人間によって送信されることを確認するために、CAPTCHAなどのツールを使用することを検討してください。SMSサインアップフォームにCAPTCHA要件を設けることで、不正なサインアップの数を減らすことができます。
 
-### 私のブランドは米国でビジネスを行っており、米国は私のSMS地理的許可リストに含まれています。私の顧客は米国外に旅行しているときでもSMSメッセージングを受信しますか？ 
+### 私のブランドは米国でビジネスを行っており、米国は私の SMS 地理的許可リストに載っています。私の顧客は米国外に旅行しているときでもSMSメッセージングを受信しますか？ 
 
 はい、お客様が米国の市外局番の電話番号を持っている限り、旅行中でもメッセージを受信できます。 
 
diff --git a/_lang/ja/_hidden/private_betas/template_catalog_item_liquid.md b/_lang/ja/_hidden/private_betas/template_catalog_item_liquid.md
index a1bdeda8eeb..de6647d25e2 100644
--- a/_lang/ja/_hidden/private_betas/template_catalog_item_liquid.md
+++ b/_lang/ja/_hidden/private_betas/template_catalog_item_liquid.md
@@ -9,15 +9,15 @@ hidden: true
 
 # リキッドを含むカタログアイテムのテンプレート化
 
- [Connected Content]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content) と同様に、`:rerender` フラグをLiquid タグに含めて、Liquid コンテンツをレンダリングする必要があります。`:rerender` フラグは1 レベルの深さしかないことに注意してください。つまり、入れ子になったリキッドタグ 呼び出しにはアプリされません。
+ [Connected Content]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content) と同様に、`:rerender` フラグを Liquid タグに含めて、Liquid コンテンツをレンダリングする必要があります。`:rerender` フラグはレベル1の深さしかないことに注意してください。つまり、階層化 Liquid タグ 呼び出しには適用されません。
 
  {% alert important %}
- 「リキッド」を含むカタログ項目のテンプレート化は、初期段階で実行されます。早いアクセスに参加したい場合は、Braze アカウントマネージャーに連絡してください。
+ Liquid を含むカタログアイテムのテンプレート化は、早期アクセス段階です。早いアクセスに参加したい場合は、Braze アカウントマネージャーに連絡してください。
  {% endalert %}
 
-カタログアイテムにユーザープロファイル フィールドs(液体パーソナライゼーション タグ内)が含まれている場合、これらの値は、液体を適切にレンダリングするために、テンプレートの前に、液体を介してメッセージ内で事前に定義する必要があります。`:rerender` フラグが指定されていない場合、Raw Liquid コンテンツがレンダリングされます。
+カタログアイテムにユーザープロファイルフィールド (Liquid パーソナライゼーションタグ内) が含まれている場合は、Liquid を適切にレンダリングするために、テンプレートの前に Liquid を使用してメッセージ内でこれらの値を事前に定義する必要があります。`:rerender` フラグが指定されていない場合、生の Liquid コンテンツがレンダリングされます。
 
-たとえば、"Messages"という名前のカタログに、このリキッドを含むアイテムがあるとします。
+たとえば、「Messages」という名前のカタログに、この Liquid を含むアイテムがあるとします。
 
 ![][15]{: style="max-width:80%;"}<br>
 
diff --git a/_lang/ja/_includes/rate_limits.md b/_lang/ja/_includes/rate_limits.md
new file mode 100644
index 00000000000..5f4d064c532
--- /dev/null
+++ b/_lang/ja/_includes/rate_limits.md
@@ -0,0 +1,186 @@
+
+<!---DEFAULT RATE LIMIT-->
+
+{% if include.endpoint == "デフォルト" %}
+[API レート制限]({{site.baseurl}}/api/api_limits/)で説明されているように、このエンドポイントにはデフォルトの1時間あたり25万リクエストのBraze レート 制限が適用されます。
+
+<!---PUT /scim/v2/Users/YOUR_ID_HERE--->
+{% elsif include.endpoint == "ダッシュボードユーザーの更新" %}
+このエンドポイントには、1日あたり1社あたり5000リクエストのレート制限があります。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/scim/v2/Users/` GET、DELETE、および POST エンドポイントと共有されます。
+
+<!---GET /scim/v2/Users/YOUR_ID_HERE--->
+{% elsif include.endpoint == "ダッシュボードユーザーを検索する" %}
+このエンドポイントには、1日あたり1社あたり5000リクエストのレート制限があります。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/scim/v2/Users/` PUT、GET、DELETE、およびPOST エンドポイントと共有されます。
+
+<!---DELETE /scim/v2/Users/YOUR_ID_HERE--->
+{% elsif include.endpoint == "ダッシュボードーザーを消去する" %}
+このエンドポイントには、1日あたり1社あたり5000リクエストのレート制限があります。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/scim/v2/Users/` PUT、GET、および POST エンドポイントと共有されます。
+
+<!---POST /scim/v2/Users--->
+{% elsif include.endpoint == "ダッシュボードユーザーを作成する" %}
+このエンドポイントには、1日あたり1社あたり5000リクエストのレート制限があります。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/scim/v2/Users/` PUT、GET、および DELETE エンドポイントと共有されます。
+
+<!---GET /scim/v2/Users--->
+{% elsif include.endpoint == "ダッシュボードユーザーメールを調べる" %}
+このエンドポイントには、1日あたり1社あたり5000リクエストのレート制限があります。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/scim/v2/Users/` PUT、GET、DELETE、およびPOST エンドポイントと共有されます。
+
+<!---/users/external_id/rename-->
+<!---/users/external_id/remove-->
+
+{% elsif include.endpoint == "external ID 移行" %}
+[API レート制限]({{site.baseurl}}/api/api_limits/)で説明されているように、このエンドポイントに1分あたり1000リクエストのレート制限を適用します。
+
+<!---/users/track-->
+
+{% elsif include.endpoint == "ユーザー追跡" %}
+すべての顧客に対して、このエンドポイントに対して1分あたり50,000リクエストの基本スピード制限を適用します。`/users/track` の各リクエストには、最大75個のイベントオブジェクト、75個の属性オブジェクト、75個の購買オブジェクトを含めることができます。それぞれのオブジェクト (イベント、属性、および購入配列) は、それぞれ1つのユーザーを更新できます。合計すると、1回の呼び出しで最大225人のユーザーを更新できることになります。さらに、単一のユーザープロファイルを複数のオブジェクトによって更新することもできます。
+
+**月間アクティブユーザー数 - CY 24-25** を購入した顧客には異なる制限が適用されます。これらの制限の詳細については、[月間アクティブユーザー数 - CY 24-25 制限]({{site.baseurl}}/api/endpoints/user_data/post_user_track/#monthly-active-users-cy-24-25)を参照してください。
+
+詳しくは、[API レート制限]({{site.baseurl}}/api/api_limits/)のページを参照してください。制限を引き上げる必要がある場合は、カスタマーサクセスマネージャーに連絡してください。
+
+<!---/users/export/ids-->
+
+{% elsif include.endpoint == "ユーザーエクスポート ID" %}
+2024年8月22日以降に Braze にオンボーディングした場合、このエンドポイントには、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、1分あたり250リクエストのレート制限が適用されます。
+
+<!---/users/delete-->
+
+{% elsif include.endpoint == "ユーザーの消去" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1分あたり20,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/users/alias/new`、`/users/identify`、および `/users/merge` エンドポイントと共有されます。
+
+<!---/users/alias/new-->
+
+{% elsif include.endpoint == "users alias new" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1分あたり20,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/users/delete`、`/users/identify`、`/users/merge`、および `/users/alias/update` エンドポイントと共有されます。
+
+<!---/users/alias/update-->
+
+{% elsif include.endpoint == "users alias update" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1分あたり20,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/users/delete`、`/users/identify`、`/users/merge`、および `/users/alias/new` エンドポイントと共有されます。
+
+<!---/users/alias/update-->
+
+{% elsif include.endpoint == "users alias update" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1分あたり20,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/users/delete`、`/users/identify`、および `/users/merge` エンドポイントと共有されます。
+
+<!---/users/identify-->
+
+{% elsif include.endpoint == "ユーザー ID" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1分あたり20,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/users/delete`、`/users/alias/new`、`/users/merge`、および `/users/alias/update` エンドポイントと共有されます。
+
+<!---/users/merge-->
+
+{% elsif include.endpoint == "ユーザーのマージ" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1分あたり20,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/users/delete`、`/users/alias/new`、`/users/identify`、および `/users/alias/update` エンドポイントと共有されます。
+
+<!---/custom_attributes-->
+
+{% elsif include.endpoint == "custom_属性" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1時間あたり1,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/events`、`/events/list`、および `/purchases/product_list` エンドポイントと共有されます。
+
+<!---/events-->
+
+{% elsif include.endpoint == "イベント" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1時間あたり1,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/custom_attributes`、`/events/list`、および `/purchases/product_list` エンドポイントと共有されます。
+
+<!---/events/list-->
+
+{% elsif include.endpoint == "イベントリスト" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1時間あたり1,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/custom_attributes`、`/events`、および `/purchases/product_list` エンドポイントと共有されます。
+
+<!---/purchases/product_list-->
+
+{% elsif include.endpoint == "購入品リスト" %}
+2021年9月16日以降に Braze にオンボーディングした顧客の場合、このエンドポイントには、1時間あたり1,000リクエストの共有レート制限が適用されます。このレート制限は、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/custom_attributes`、`/events`、および `/events/list` エンドポイントと共有されます。
+
+<!---/messages/send-->
+<!---/campaigns/trigger/send-->
+<!---/canvas/trigger/send-->
+
+{% elsif include.endpoint == "エンドポイントの送信" %}
+リクエストでセグメントまたは接続済みのオーディエンスを指定する際、このエンドポイントには1分あたり250リクエストのレート制限が適用されます。それ以外の場合、`external_id` を指定すると、このエンドポイントは、[API レート制限]({{site.baseurl}}/api/api_limits/) に記載されているように、`/messages/send`、`/campaigns/trigger/send`、および `/canvas/trigger/send` 間で共有される1時間あたり250,000リクエストのデフォルトのレート制限が適用されます。
+
+<!---/transactional/v1/campaigns/{campaign_id}/send -->
+
+{% elsif include.endpoint == "トランザクションメール" %}
+Braze トランザクションメールはレート制限の対象外です。選択したパッケージに応じて、1時間あたりに設定された数のトランザクションメールが SLA によってカバーされます。このレートを超えるリクエストは送信されますが、SLA ではカバーされません。メールの99.9%が1分以内に送信されます。
+
+<!---/sends/id/create-->
+
+{% elsif include.endpoint == "ID 作成を送信する" %}
+このエンドポイントを使用して作成できるカスタム送信識別子の1日の最大数は、特定のワークスペースに対して100です。作成する各 `send_id` および `campaign_id` の組み合わせは、毎日の制限にカウントされます。有効なリクエストのレスポンスヘッダーには、現在のレート制限ステータスが含まれます。詳しくは、[API レート制限]({{site.baseurl}}/api/api_limits/)を参照してください。
+
+<!---/subscription/status/set-->
+{% elsif include.endpoint == "サブスクリプションステータスセット" %}
+このエンドポイントには、[API レート制限]({{site.baseurl}}/api/api_limits/)に記載されているように、`/subscription/status/set` および `/v2/subscription/status/set` エンドポイントで共有される1分あたり5000リクエストのレート制限があります。
+
+<!-- Add this phrase back ", as documented in [API rate limits]({{site.baseurl}}/api/api_limits/)" to CDI endpoints for GA -->
+
+<!---GET /cdi/integrations--->
+{% elsif include.endpoint == "cdi リストの統合" %}
+このエンドポイントには、1分あたり、50リクエストのレート制限があります。
+
+<!---POST /cdi/integrations/{integration_id}/sync--->
+{% elsif include.endpoint == "cdi ジョブの同期" %}
+このエンドポイントには、1分あたり、20リクエストのレート制限があります。
+
+<!---POST /cdi/integrations/{integration_id}/job_sync_status--->
+{% elsif include.endpoint == "cdi ジョブ同期ステータス" %}
+このエンドポイントには、1分あたり、100リクエストというレート制限があります。
+
+{% endif %}
+
+<!---Additional if statement for Messaging endpoints-->
+
+{% if include.category == "メッセージエンドポイント" %}
+
+Braze エンドポイントは[API リクエストのバッチ処理]({{site.baseurl}}/api/api_limits/#batching-api-requests)をサポートしています。メッセージングエンドポイントへの単一のリクエストは、次のいずれかに到達できます。
+
+- それぞれに個別のメッセージパラメーターを持つ、最大50個の特定の `external_ids`
+- `segment_id` で指定される、Braze ダッシュボードで作成された任意のサイズのセグメント
+- リクエストで[接続オーディエンス]({{site.baseurl}}/api/objects_filters/connected_audience/)オブジェクトとして定義されている、任意のサイズのオーディエンスセグメント
+
+{% endif %}
+
+<!---Additional if statement for /messages/send endpoint-->
+
+{% if include.category == "メール送信エンドポイント" %}
+
+Braze エンドポイントは[API リクエストのバッチ処理]({{site.baseurl}}/api/api_limits/#batching-api-requests)をサポートしています。メッセージングエンドポイントへの単一のリクエストは、次のいずれかに到達できます。
+
+- 最大50個の特定の `external_ids`
+- `segment_id` で指定される、Braze ダッシュボードで作成された任意のサイズのセグメント
+- リクエストで[接続オーディエンス]({{site.baseurl}}/api/objects_filters/connected_audience/)オブジェクトとして定義されている、任意のサイズのオーディエンスセグメント
+
+{% endif %}
+
+{% if include.endpoint == "非同期カタログアイテム" %}
+
+このエンドポイントは、[API レート制限]({{site.baseurl}}/api/api_limits/)で説明されているように、すべての非同期カタログアイテムエンドポイント間で1分あたり16,000リクエストの共有レート制限があります。
+
+{% endif %}
+
+{% if include.endpoint == "同期カタログアイテム" %}
+
+このエンドポイントは、[API レート制限]({{site.baseurl}}/api/api_limits/)で説明されているように、すべての同期カタログアイテムエンドポイント間で毎分50リクエストの共有レート制限があります。
+
+{% endif %}
+
+{% if include.endpoint == "同期カタログ" %}
+
+このエンドポイントは、[API レート制限]({{site.baseurl}}/api/api_limits/)で説明されているように、すべての同期カタログエンドポイント間で1分あたり50リクエストの共有レート制限があります。
+
+{% endif %}
+
+{% if include.endpoint == "非同期カタログフィールド" またはエンドポイントを含める == "非同期カタログ選択" %}
+
+このエンドポイントは、[API レート制限]({{site.baseurl}}/api/api_limits/)で説明されているように、すべての非同期カタログフィールドとセレクションエンドポイント間で1分あたり50リクエストの共有レート制限があります。
+
+{% endif %}
+
+{% if include.endpoint == "キャンペーン分析のエクスポート" %}
+
+このエンドポイントには、1分あたり、50,000リクエストというレート制限があります。
+
+{% endif %}
diff --git a/_lang/ja/_partners/canvas_steps.md b/_lang/ja/_partners/canvas_steps.md
index 24e1ccb7db8..03cea203bfd 100644
--- a/_lang/ja/_partners/canvas_steps.md
+++ b/_lang/ja/_partners/canvas_steps.md
@@ -4,8 +4,8 @@ article_title: キャンバスオーディエンスの同期
 page_order: 8
 
 guide_top_header: "キャンバスオーディエンスの同期"
-guide_top_text: "Brazeのオーディエンスシンク機能は、多くのトップソーシャルおよび広告テクノロジーにキャンペーンのリーチを拡大するのに役立つ。このランディングページでは、開発者やマーケティング担当者が、利用可能なキャンバスのシンクパートナーに関するリソースを見つけることができる。"
-description: "このランディングページでは、開発者やマーケティング担当者が、利用可能なキャンバスのシンクパートナーに関するリソースを見つけることができる。"
+guide_top_text: "Braze のオーディエンスの同期機能は、多くのトップソーシャルテクノロジーおよび広告テクノロジーにキャンペーンのリーチを拡大するのに役立ちます。このランディングページでは、開発者やマーケターが、利用可能なキャンバス同期パートナーに関するリソースを見つけることができます。"
+description: "このランディングページでは、開発者やマーケターが、利用可能なキャンバス同期パートナーに関するリソースを見つけることができます。"
 
 layout: dev_guide
 
@@ -23,10 +23,10 @@ guide_menu_list:
   - name: Facebookオーディエンス同期
     link: /docs/partners/canvas_steps/facebook_audience_sync
     image: /assets/img/braze_icons/facebook.svg
-  - name: Google Audience Sync
+  - name: Google オーディエンスの同期
     link: /docs/partners/canvas_steps/google_audience_sync
     image: /assets/img/braze_icons/google.svg
-  - name: Criteoオーディエンス・シンク
+  - name: Criteo オーディエンスの同期
     link: /docs/partners/canvas_steps/criteo_audience_sync
     image: /assets/img/braze_icons/lightning-01.svg
   - name: Pinterestオーディエンス同期
@@ -42,5 +42,5 @@ guide_menu_list:
 ---
 
 {% alert important %}
-Criteo、Pinterest、Snapchat、TikTokへのBraze Audience Syncsは、Audience Sync Pro統合である。これらの統合の詳細については、Brazeのアカウントマネージャーに問い合わせを。
+Braze Audience Sync to Criteo、Braze Audience Sync to Pinterest、Braze Audience Sync to Snapchat、Braze Audience Sync to TikTok は、Audience Sync Pro 統合です。これらの統合の詳細については、Brazeのアカウントマネージャーに問い合わせを。
 {% endalert %}
diff --git a/_lang/ja/_partners/canvas_steps/criteo_audience_sync.md b/_lang/ja/_partners/canvas_steps/criteo_audience_sync.md
index 941b450414f..93743a20ca5 100644
--- a/_lang/ja/_partners/canvas_steps/criteo_audience_sync.md
+++ b/_lang/ja/_partners/canvas_steps/criteo_audience_sync.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Criteo
 article_title: キャンバスのオーディエンスがCriteoに同期する
-description: "この参考記事では、Braze Audience SyncをCriteoに接続して、行動トリガーやセグメンテーションなどに基づいて広告を配信する方法を紹介する。"
+description: "このリファレンス記事では、Braze Audience Sync to Criteo を使用して、行動トリガーやセグメンテーションなどに基づいて広告を配信する方法について説明します。"
 page_order: 4
 alias: "/audience_sync_criteo/"
 
@@ -9,137 +9,137 @@ Tool:
   - Canvas
 ---
 
-# Criteoへのオーディエンス・シンク
+# Audience Sync to Criteo
 
-CriteoへのBraze Audience Syncを使用することで、ブランドは自社のBrazeインテグレーションからCriteoの顧客リストにユーザーデータを追加し、行動トリガーやセグメンテーションなどに基づいて広告を配信することができる。ユーザーデータに基づいてBraze Canvasでメッセージ（プッシュ、Eメール、SMS、ウェブフックなど）をトリガーするために通常使用するあらゆる基準を、Criteoの顧客リストでそのユーザーに広告をトリガーするために使用できるようになった。
+Braze Audience Sync to Criteo を使用すると、ブランドは独自の Braze 統合からのユーザーデータを Criteo の顧客リストに追加して、行動トリガーやセグメンテーションなどに基づいて広告を配信できます。ユーザーデータに基づいて Braze キャンバスでメッセージをトリガーするために通常使用する基準 (プッシュ、メール、SMS、Webhook など) を、Criteo 顧客リスト内の該当ユーザーに対して広告をトリガーするために使用できるようになりました。
 
-**オーディエンス・シンクの一般的な使用例には、以下のようなものがある：**
+**オーディエンス同期の一般的なユースケースには次のものがあります。**
 
 - 購買やエンゲージメントを促進するために、複数のチャネルを通じて価値の高いユーザーをターゲットにする。
-- 他のマーケティング・チャネルで反応が低いユーザーをリターゲティングする
-- 抑制オーディエンスを作成することで、ユーザーがすでにブランドの忠実な消費者である場合に広告を受け取らないようにする。
+- 他のマーケティング チャネルにあまりレスポンシブでないユーザーのリターゲッティング
+- すでに自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑制オーディエンスの作成
 - Lookalikeオーディエンスを作成し、新規ユーザーをより効率的に獲得する
 
-この機能により、ブランドはCriteoと共有される特定のファーストパーティデータをコントロールすることができる。Brazeでは、ファーストパーティデータを共有できる統合とできない統合を最大限に考慮している。詳細については、当社の[プライバシーポリシーを](https://www.braze.com/privacy)参照のこと。
+この機能により、ブランドは Criteo と共有される特定のファーストパーティデータを制御できるようになります。Braze では、ファーストパーティデータを共有できる統合と共有できない統合を最大限に考慮しています。詳細については、当社の[プライバシーポリシー](https://www.braze.com/privacy)をご確認ください。
 
 {% alert important %}
-**オーディエンス・シンク・プロの免責事項**<br>
-Braze Audience Sync to Criteoは、Audience Sync Proとの統合である。この統合の詳細については、Brazeのアカウント・マネージャーに問い合わせを。<br> 
+**Audience Sync Pro 免責条項**<br>
+Braze Audience Sync to Criteo は Audience Sync Pro 統合です。この統合の詳細については、Brazeのアカウント・マネージャーに問い合わせを。<br> 
 {% endalert %}
 
 ## 前提条件 
 
-CriteoへのAudience Syncを設定する前に、以下の項目を作成または完了しておく必要がある。
+キャンバスで Criteo へのオーディエンス同期のステップを設定するには、以下の項目が作成され完了していることを確認する必要があります。
 
-| 必要条件 | 起源 | 説明 |
+| 必要条件 | 提供元 | 説明 |
 | --- | --- | --- |
-| Criteo広告アカウント | [Criteo](https://marketing.criteo.com/) | Criteoの広告アカウントは、あなたのブランドに関連付けられている。<br><br>Criteoの管理者がオーディエンスにアクセスするための適切な権限を付与していることを確認する。 |
-| [Criteo広告ガイドライン](https://www.criteo.com/advertising-guidelines/)<br>そして<br>[Criteoブランド・セーフティ・ガイドライン](https://www.criteo.com/wp-content/uploads/2017/11/Criteo-Brand-Safety-Guidelines-UK-March-2016.pdf) | Criteo | Criteoのアクティブカスタマーとして、Criteoのキャンペーンを開始する前に、Criteoの広告およびブランドセーフティガイドラインを遵守できることを確認する必要がある。 |
+| Criteo広告アカウント | [Criteo](https://marketing.criteo.com/) | ブランドに関連付けられたアクティブな Criteo 広告アカウント。<br><br>Criteo 管理者から、オーディエンスにアクセスするための適切な権限が付与されていることを確認します。 |
+| [Criteo 広告ガイドライン](https://www.criteo.com/advertising-guidelines/)<br>そして<br>[Criteo ブランドセーフティガイドライン](https://www.criteo.com/wp-content/uploads/2017/11/Criteo-Brand-Safety-Guidelines-UK-March-2016.pdf) | Criteo | Criteo のアクティブな顧客として、Criteo キャンペーンを開始する前に、Criteo の広告ガイドラインを遵守できることを確認します。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合 
 
-### ステップ1:Criteoに接続する
+### ステップ1:Criteo に接続する
 
-Brazeのダッシュボードで、**Partner Integrations**>**Technology Partnersと**進み、**Criteoを**選択する。Criteo Audience Exportモジュールで、**Connect Criteoを**クリックする。
+Braze ダッシュボードで \[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Criteo**] を選択します。Criteo Audience Export (Criteo オーディエンスエクスポート) モジュールで、\[**Criteo に接続**] をクリックします。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-![BrazeのCriteoテクノロジーページには、OverviewモジュールとCriteoモジュール（Connected Criteoボタン付き）が含まれている。][5]{: style="max-width:80%;"}
+![Braze の Criteo テクノロジーページ。「概要」モジュール、「Criteo」モジュール、「Criteo に接続」ボタンが表示されている。][5]{: style="max-width:80%;"}
 
-CriteoのoAuthページが表示され、BrazeにAudience Sync統合に関連する権限を付与する。
+次に、Criteo oAuth ページにリダイレクトされ、Braze に Audience Sync 統合に関連するアクセス許可を承認します。
 
-confirmを選択すると、Brazeにリダイレクトされ、同期したいCriteo広告アカウントを選択する。 
+\[confirm] を選択すると、Braze にリダイレクトされます。同期する Criteo 広告アカウントを選択します。 
 
-![Criteoに接続可能な広告アカウントのリスト。][7]{: style="max-width:80%;"}
+![Criteo に接続できる広告アカウントのリスト。][7]{: style="max-width:80%;"}
 
-接続に成功すると、パートナー・ページに戻り、どのアカウントが接続されているかを確認したり、既存のアカウントを切断したりできる。
+接続に成功すると、パートナーページが再び表示され、どのアカウントが接続されているかを表示したり、既存のアカウントを切断したりできます。
 
-![Criteoテクノロジーパートナーのページが更新され、接続に成功した広告アカウントが表示されている。][4]{: style="max-width:80%;"}
+![広告アカウントが接続されたことを示す更新後の Criteo テクノロジーパートナーページ。][4]{: style="max-width:80%;"}
 
-Criteoとの接続は、Brazeワークスペースレベルで適用される。Criteo管理者がCriteo広告アカウントからあなたを削除した場合、Brazeは無効なトークンを検出する。その結果、Criteoを使用しているアクティブなCanvasesにはエラーが表示され、Brazeはユーザーを同期できなくなる。
+Criteoとの接続は、Brazeワークスペースレベルで適用される。Criteo 管理者が Criteo 広告アカウントからユーザーを削除した場合、Braze は無効なトークンを検出します。その結果、Criteoを使用しているアクティブなCanvasesにはエラーが表示され、Brazeはユーザーを同期できなくなる。
 
-### ステップ2:キャンバスのエントリー基準を設定する
+### ステップ2:キャンバスのエントリ基準を設定する
 
-広告トラッキングのオーディエンスを構築する際、ユーザーの嗜好に基づき、また[CCPAに](https://oag.ca.gov/privacy/ccpa)基づく「販売または共有しない」権利などのプライバシー法を遵守するために、特定のユーザーを含めたり除外したりしたい場合がある。マーケティング担当者は、キャンバスのエントリー基準の中で、ユーザーの適格性に関する関連フィルタを実装する必要がある。以下にいくつかの選択肢を挙げる。
+広告追跡のためにオーディエンスを作成する場合、その好みに基づいて特定のユーザーを含めるか除外し、[CCPA](https://oag.ca.gov/privacy/ccpa)の「販売または共有を禁止する」権利などのプライバシー法に従うことを希望する場合があります。マーケターは、キャンバスのエントリ基準の範囲内で、ユーザーの適格性に関する適切なフィルターを実装する必要があります。以下にいくつかの選択肢を挙げる。
 
-[Braze SDKを通じてiOS IDFAを]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/other_sdk_customizations/#optional-idfa-collection)収集した場合、Ads Tracking Enabledフィルターを使用できるようになる。trueを選択すると、ユーザーがオプトインしたAudience Sync送信先にのみユーザーを送信する。
+[Braze SDK で iOS IDFA]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/other_sdk_customizations/#optional-idfa-collection) を収集した場合、\[広告の追跡が有効] フィルターを使用できます。ユーザーがオプトインしたオーディエンス同期の宛先にのみユーザーを送信するには、値を true に選択します。
 
 ![][11]
 
-`opt-ins` 、`opt-outs` 、`Do Not Sell Or Share` 、またはその他の関連するカスタム属性を収集する場合は、フィルタとしてキャンバスの入力条件にこれらを含める必要がある：
+`opt-ins`、`opt-outs`、`Do Not Sell Or Share`、または他の関連するカスタム属性を収集する場合は、キャンバスのエントリ基準にこれらをフィルターとして含める必要があります。
 
 ![][12]
 
-Brazeプラットフォーム内でこれらのデータ保護法を遵守する方法の詳細については、[データ保護テクニカルアシスタンスを]({{site.baseurl}}/dp-technical-assistance/)参照のこと。
+Braze プラットフォーム内でこれらのデータ保護法を遵守する方法の詳細については、[データ保護テクニカルアシスタンス]({{site.baseurl}}/dp-technical-assistance/)を参照してください。
 
 ### ステップ3:Criteoでオーディエンス同期ステップを追加する
 
-キャンバスにコンポーネントを追加し、**Audience Syncを**選択する。
+キャンバスにコンポーネントを追加し、\[**オーディエンスの同期**] を選択します。
 
-![キャンバスフローにCriteo Audienceコンポーネントを追加する前のステップのワークフロー。][9]{: style="max-width:35%;"}![キャンバスフローにCriteo Audienceコンポーネントを追加する前のステップのワークフロー。][10]{: style="max-width:28%;"}
+![キャンバスフローに Criteo オーディエンスコンポーネントを追加するための前のステップのワークフロー。][9]{: style="max-width:35%;"}![キャンバスフローに Criteo オーディエンスコンポーネントを追加するための前のステップのワークフロー。][10]{: style="max-width:28%;"}
 
-### ステップ 4:シンクの設定
+### ステップ 4:同期設定
 
-**Custom Audience**ボタンをクリックして、コンポーネント・エディターを開く。
+\[**カスタムオーディエンス**] ボタンをクリックしてコンポーネントエディターを開きます。
 
-**Criteoを**Audience Syncのパートナーとして選択する。 
+**Criteo** を目的のオーディエンス同期パートナーとして選択します。 
 
 ![][6]
 
-次に、希望のCriteo広告アカウントを選択する。**Choose a New or Existing Audience（新規または既存のオーディエンスを選択**）ドロップダウンで、新規または既存のオーディエンスの名前を入力する。
+次に、目的の Criteo 広告アカウントを選択します。**Choose a New or Existing Audience（新規または既存のオーディエンスを選択**）ドロップダウンで、新規または既存のオーディエンスの名前を入力する。
 
 {% tabs %}
 {% tab 新しいオーディエンスを作る %}
-**新しいオーディエンスを作る**<br>
-新しいオーディエンスの名前を入力し、**Add Users to Audienceを**選択し、Criteoと同期したいフィールドを選択する。次に、ステップエディタの下部にある**Create Audience**ボタンをクリックしてオーディエンスを保存する。
+**新規オーディエンスの作成**<br>
+新しいオーディエンスの名前を入力し、\[**ユーザーをオーディエンスに追加**] を選択し、Criteo と同期するフィールドを選択します。次に、ステップエディタの下部にある**Create Audience**ボタンをクリックしてオーディエンスを保存する。
 
-![カスタムオーディエンスキャンバスステップの拡大図。] （{% image_buster /assets/img/criteo/criteo3.png %} ）。
+![カスタムオーディエンスキャンバスステップの展開ビュー。ここでは目的の広告アカウントが選択され、新しいオーディエンスが作成される。]({% image_buster /assets/img/criteo/criteo3.png %})
 
-オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合、ステップエディタの上部にユーザーに通知される。また、オーディエンスはドラフトモードで作成されたため、ユーザーはキャンバスの旅の後半でユーザーを削除するためにこのオーディエンスを参照することができる。
+オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合、ステップエディタの上部にユーザーに通知される。ユーザーは、後でキャンバスジャーニーでユーザーを削除するためにこのオーディエンスを参照することもできます。これは、オーディエンスが下書きで作成されたためです。
 
 ![キャンバスコンポーネントで新しいオーディエンスが作成された後に表示されるアラート。]({% image_buster /assets/img/criteo/criteo1.png %})
 
-新しいオーディエンスを持つキャンバスを立ち上げると、Brazeは、オーディエンス同期コンポーネントに入ったユーザーをほぼリアルタイムで同期する。
+新しいオーディエンスを使用してキャンバスを起動すると、オーディエンス同期コンポーネントに入る時点で、Braze はユーザーをほぼリアルタイムで同期します。
 {% endtab %}
 {% tab 既存のオーディエンスと同期する %}
-**既存のオーディエンスと同期する**<br>
-Brazeはまた、既存のCriteoオーディエンスにユーザーを追加し、これらのオーディエンスを最新の状態に保つ機能も提供している。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンス名を入力し、**オーディエンスに追加する**。Brazeは、ユーザーがAudience Syncコンポーネントに入ると、ほぼリアルタイムでユーザーを追加する。
+**既存のオーディエンスとの同期**<br>
+また、Braze は、これらのオーディエンスが最新であることを確認するために、既存の Criteo オーディエンスにユーザーを追加する機能も提供します。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンスの名前を入力し、**オーディエンスに追加します。**Braze は、オーディエンス同期コンポーネントに入ると、ほぼリアルタイムでユーザーを追加します。
 
-![カスタムオーディエンスキャンバスステップの拡大図。] （{% image_buster /assets/img/criteo/criteo8.png %} ）。
+![カスタムオーディエンスキャンバスステップの展開ビュー。ここでは、目的の広告アカウントと既存のオーディエンスが選択されている。]({% image_buster /assets/img/criteo/criteo8.png %})
 
 {% endtab %}
 {% endtabs %}
 
 ### ステップ 5: キャンバスを立ち上げる
 
-CriteoにAudience Syncを設定したら、キャンバスを起動する！新しいオーディエンスが作成され、オーディエンス同期ステップを通過したユーザーは、Criteoのこのオーディエンスに渡される。キャンバスに後続のコンポーネントが含まれていれば、ユーザーはユーザー・ジャーニーの次のステップに進むことができる。
+Audience Sync to Criteo を設定したら、キャンバスを起動します。新しいオーディエンスが作成され、オーディエンス同期ステップを通過するユーザーは Criteo のこのオーディエンスに送られます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーはユーザージャーニーの次のステップに進みます。
 
-Criteoでオーディエンスを表示するには、広告マネージャーのアカウントに入り、ナビゲーションの**オーディエンスライブラリーから**セグメントを選択する。**セグメント**ページから、各オーディエンスが～1,000に達した後のサイズを見ることができる。
+Criteo でオーディエンスを表示するには、広告マネージャーアカウントにログインし、ナビゲーションの**Audience Library** から Segments を選択します。**セグメント**ページから、各オーディエンスが～1,000に達した後のサイズを見ることができる。
 
-![観客ライブラリーは、セグメント、ID、ソース、タイプ、サイズ、現在使用中、最終更新を表示する。][0]
+![セグメント、ID、ソース、タイプ、サイズ、現在使用中であるかどうか、および最終更新日時を示すオーディエンスライブラリ。][0]
 
 ## ユーザー同期とレート制限の考慮
 
-ユーザーがAudience Syncのステップに達すると、BrazeはCriteoのAPIレート制限を尊重しながら、ほぼリアルタイムでこれらのユーザーを同期する。これが実際に意味するのは、Brazeは5秒ごとにできるだけ多くのユーザーをバッチ処理してからSnapchatに送るということだ。
+ユーザーがオーディエンス同期ステップに到達すると、Braze は Criteo の API レート制限を尊重しながら、これらのユーザーをほぼリアルタイムで同期します。これが実際に意味するのは、Brazeは5秒ごとにできるだけ多くのユーザーをバッチ処理してからSnapchatに送るということだ。
 
-CriteoのAPIレート制限では、1分間に250リクエストまでとなっている。Brazeの顧客がこのレート制限に達した場合、Braze the Canvasは最大13時間まで同期を再試行する。同期が不可能な場合、これらのユーザーはUsers Erroredメトリックの下にリストされる。 
+Criteo の API レート制限では、1分あたりに250のリクエストを超えないように設定されています。Brazeの顧客がこのレート制限に達した場合、Braze the Canvasは最大13時間まで同期を再試行する。同期が不可能な場合、これらのユーザーはUsers Erroredメトリックの下にリストされる。 
 
 ## アナリティクスを理解する
 
-以下の表は、Audience Syncコンポーネントのアナリティクスをより理解するのに役立つメトリクスとその説明である。
+次の表に、オーディエンス同期コンポーネントからの分析をよりよく理解するのに役立つ指標と説明を示します。
 
-| メートル | 説明 |
+| 指標 | 説明 |
 | --- | --- |
-| 入団 | Criteoに同期されるこのコンポーネントを入力したユーザーの数。 |
-| 次のステップへ進む | 次のコンポーネントがある場合、何人のユーザーが次のコンポーネントに進んだか。これがキャンバスブランチの最後のステップであれば、すべてのユーザーが自動で進む。 |
-| 同期されたユーザー | Criteoとの同期に成功したユーザー数。 |
+| 入力 | Criteo と同期するためにこのコンポーネントに入ったユーザーの数。 |
+| 次のステップへ進む | 次のコンポーネントがある場合、次のコンポーネントに進んだユーザーの数。これがキャンバスブランチの最後のステップである場合、すべてのユーザーは自動的に進みます。 |
+| 同期されたユーザー | Criteo に正常に同期されたユーザー数。 |
 | 同期されていないユーザー | 一致するフィールドがないために同期されていないユーザーの数。 |
 | 保留中のユーザー | BrazeがCriteoに同期するために現在処理しているユーザー数。 |
-| ユーザーエラー | 約13時間の再試行後、APIエラーによりCriteoに同期されなかったユーザー数。エラーの原因としては、無効なCriteoトークンやCriteo上でオーディエンスが削除された場合などが考えられる。 |
-| イグジット・キャンバス | キャンバスを退出したユーザーの数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生する。 |
+| エラーが発生したユーザー数 | 約13時間の再試行後、APIエラーによりCriteoに同期されなかったユーザー数。エラーの原因としては、Criteo トークンが無効である場合や、Criteo でオーディエンスが削除された場合などが考えられます。 |
+| 終了済みのキャンバス | キャンバスを退出したユーザーの数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert important %}
@@ -149,25 +149,25 @@ CriteoのAPIレート制限では、1分間に250リクエストまでとなっ
 ## トラブルシューティング
 
 {% details 無効なトークンエラーが表示された場合、次に何をすればよいか？ %}
-Criteoアカウントは、Criteoパートナーページで簡単に切断・再接続できる。Criteoの管理者に、同期したい広告アカウントに適切な権限があることを確認する。
+Criteo パートナーページで Criteo アカウントの接続を解除してから再接続できます。同期する広告アカウントに対する適切なアクセス許可があることを Criteo 管理者に確認します。
 {% enddetails %}
 
 {% details なぜキャンバスは起動できないのか？ %}
-Criteoパートナーページで、Criteo広告アカウントがBrazeに正常に接続されていることを確認する。
+Criteo パートナーページで、Criteo 広告アカウントが Braze に正常に接続されていることを確認してください。
 
 広告アカウントを選択し、新しいオーディエンスの名前を入力し、一致するフィールドを選択していることを確認する。
 {% enddetails %}
 
-{% details Criteoにユーザーを渡した後、ユーザーがマッチしたかどうかを知るには？ %}
+{% details ユーザーを Criteo に渡した後、ユーザーが一致したかどうかを知るにはどうすればよいですか? %}
 Criteoは、自社のデータ・プライバシー・ポリシーについて、この情報を提供していない。
 {% enddetails %}
 
-{% details Criteoは何人のオーディエンスをサポートできるか？ %}
-現時点では、Criteoアカウント内で1,000人のオーディエンスしか持つことができない。 
+{% details Criteo がサポート可能なオーディエンス数は? %}
+現時点では、Criteo アカウントに含めることができるオーディエンスの数は1,000です。 
 
-この制限に違反した場合、Brazeは新しいオーディエンスを作成できないことを通知する。 
+この制限を超えると、Braze は新しいオーディエンスを作成できないことを通知します。 
 
-Criteo広告アカウントにアクセスし、使用しなくなったオーディエンスを削除する必要がある。
+Criteo の広告アカウントにログインして、使用していないオーディエンスを削除する必要があります。
 {% enddetails %} 
 
 [0]: {% image_buster /assets/img/criteo/criteo.png %}
diff --git a/_lang/ja/_partners/canvas_steps/facebook_audience_sync.md b/_lang/ja/_partners/canvas_steps/facebook_audience_sync.md
index 7179ece3c6d..634d1e6c7b7 100644
--- a/_lang/ja/_partners/canvas_steps/facebook_audience_sync.md
+++ b/_lang/ja/_partners/canvas_steps/facebook_audience_sync.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Facebook
 article_title: キャンバスのオーディエンスがFacebookに同期
-description: "この参考記事では、Braze Audience SyncをFacebookに同期させ、行動トリガーやセグメンテーションなどに基づいて広告を配信する方法を紹介する。"
+description: "このリファレンス記事では、Braze Audience Sync to Facebook を使用して、行動トリガーやセグメンテーションなどに基づいて広告を配信する方法について説明します。"
 page_order: 1
 alias: "/audience_sync_facebook/"
 
@@ -12,76 +12,76 @@ Tool:
 
 # オーディエンスがFacebookに同期する
 
-FacebookへのBraze Audience Syncを使用することで、ブランドは、自社のBrazeインテグレーションからFacebookカスタムオーディエンスに自社のユーザーデータを追加し、行動トリガーやセグメンテーションなどに基づいて広告を配信することを選択できる。ユーザーデータに基づいてBraze Canvasでメッセージ（Push、Email、SMS、Webhookなど）をトリガーするために通常使用する基準はすべて、カスタムオーディエンスを使ってFacebookでそのユーザーに広告をトリガーするために使用できる。
+Braze Audience Sync to Facebook を使用すると、ブランドは独自の Braze 統合からのユーザーデータを Facebook のカスタムオーディエンスに追加して、行動トリガーやセグメンテーションなどに基づいて広告を配信できます。ユーザーデータに基づいて Braze キャンバスでメッセージ (プッシュ、メール、SMS、Webhook など) をトリガーするために通常使用する基準を、カスタムオーディエンスを介して Facebook 内の該当ユーザーに対して広告をトリガーするときに使用できるようになりました。
 
-**カスタムオーディエンスを同期する一般的なユースケースには、以下のようなものが**ある：
+**カスタムオーディエンス同期の一般的なユースケースには次のものがあります。**
 
 - 複数のチャネルを通じて価値の高いユーザーをターゲットにし、購買やエンゲージメントを促進する。
-- 他のマーケティング・チャネルで反応が低いユーザーをリターゲティングする。
-- 抑制オーディエンスを作成することで、ユーザーがすでにブランドの忠実な消費者である場合に広告を受け取らないようにする。
-- より効率的に新規ユーザーを獲得するために、Lookalike Audiencesを作成する。
+- 他のマーケティングチャネルで反応が低いユーザーをリターゲティングする。
+- すでに自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑制オーディエンスを作成する。
+- 新規ユーザーをより効率的に獲得するための類似オーディエンスを作成する。
 
-この機能により、ブランドはフェイスブックと共有される特定のファーストパーティデータをコントロールできるようになる。Brazeでは、ファーストパーティデータを共有できる統合とできない統合を最大限に考慮している。詳細については、当社の[プライバシーポリシーを](https://www.braze.com/privacy)参照のこと。
+この機能により、ブランドは Facebook と共有される特定のファーストパーティデータを制御できるようになります。Braze では、ファーストパーティデータを共有できる統合と共有できない統合を最大限に考慮しています。詳細については、当社の[プライバシーポリシー](https://www.braze.com/privacy)をご確認ください。
 
 ## 前提条件
 
-キャンバスでFacebookオーディエンス・ステップを設定する前に、以下の項目が作成され、完了していることを確認する必要がある。 
+キャンバスで Facebook へのオーディエンス同期のステップを設定するには、以下の項目が作成され完了していることを確認する必要があります。 
 
-| 必要条件 | 起源 | 説明 |
+| 必要条件 | 提供元 | 説明 |
 | ----------- | ------ | ----------- |
-| フェイスブック・ビジネス・マネージャー | [Facebook][1] | ブランドのFacebook資産（広告アカウント、ページ、アプリなど）を一元管理するツール。 |
-| フェイスブック広告アカウント | [Facebook][2] | あなたのブランドのビジネス・マネージャーと結びついた、アクティブなFacebook広告アカウント。<br><br>Facebookビジネスマネージャー管理者が、Brazeで使用する予定のFacebook広告アカウントに対して「キャンペーンの管理」または「広告アカウントの管理」のいずれかの権限を付与していることを確認する。また、広告アカウントの利用規約に同意していることも確認する。 |
+| Facebook Business Manager | [Facebook][1] | ブランドのFacebook資産（広告アカウント、ページ、アプリなど）を一元管理するツール。 |
+| Facebook 広告アカウント | [Facebook][2] | あなたのブランドのビジネス・マネージャーと結びついた、アクティブなFacebook広告アカウント。<br><br>Facebookビジネスマネージャー管理者が、Brazeで使用する予定のFacebook広告アカウントに対して「キャンペーンの管理」または「広告アカウントの管理」のいずれかの権限を付与していることを確認する。また、広告アカウントの利用規約に同意していることも確認してください。 |
 | Facebookカスタムオーディエンス規約 | [Facebook][3] | Brazeで使用する予定のFacebook広告アカウントについて、Facebookのカスタムオーディエンス規約に同意する。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合
 
-### ステップ1:フェイスブックに接続する
+### ステップ1:Facebook に接続する
 
-Brazeのダッシュボードで、**Partner Integrations**>**Technology Partnersと**進み、**Facebookを**選択する。Facebook Audience Exportモジュールで、**Connect Facebookを**クリックする。
+Braze ダッシュボードで \[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Facebook**] を選択します。Facebook Audience Export (Facebook オーディエンスエクスポート) モジュールで、\[**Facebook に接続**] をクリックします。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-![BrazeのFacebookテクノロジーページには、OverviewモジュールとFacebook Audience Exportモジュール、Connected Facebookボタンが含まれている。][4]{: style="max-width:70%;"}
+![Braze の Facebook テクノロジーページ。「概要」モジュール、「Facebook Audience Export」モジュール、「Facebook に接続」ボタンが表示されている。][4]{: style="max-width:70%;"}
 
 Facebook oAuthダイアログウィンドウが表示され、BrazeがFacebook広告アカウントにカスタムオーディエンスを作成することを承認する。
 
-![最初のフェイスブックのダイアログボックスで、"Connect as X"（Xはフェイスブックのユーザー名）と促される。][6]{: style="max-width:30%;"} ![2つ目のFacebookのダイアログボックスは、広告アカウントの広告を管理する許可を求めるものだ。][5]{: style="max-width:40%;"}
+![最初の Facebook ダイアログボックス。\[Connect as X] (X は Facebook ユーザー名) で接続するように促される。][6]{: style="max-width:30%;"} ![広告アカウントの広告を管理する許可を求める2番目の Facebook のダイアログボックス。][5]{: style="max-width:40%;"}
 
 BrazeとFacebookアカウントのリンクが完了したら、Brazeワークスペース内で同期したい広告アカウントを選択できるようになる。 
 
 ![Facebookに接続可能な広告アカウントのリスト。][7]{: style="max-width:70%;"}
 
-接続に成功すると、パートナー・ページに戻り、どのアカウントが接続されているかを確認したり、既存のアカウントを切断したりできる。
+接続に成功すると、パートナーページが再び表示され、どのアカウントが接続されているかを表示したり、既存のアカウントを切断したりできます。
 
-![フェイスブックのテクノロジー・パートナーのページが更新され、広告アカウントの接続に成功したことが示されている。][8]{: style="max-width:70%;"}
+![広告アカウントが接続されたことを示す更新後の Facebook テクノロジーパートナーページ。][8]{: style="max-width:70%;"}
 
-Facebookとの接続は、Brazeのワークスペース・レベルで適用される。Facebookの管理者がFacebookビジネスマネージャーからあなたを削除したり、接続されているFacebookアカウントへのアクセスを削除した場合、Brazeは無効なトークンを検出する。その結果、Facebook Audienceコンポーネントを使用しているアクティブなCanvasesはエラーが表示され、Brazeはユーザーを同期できなくなる。 
+Facebookとの接続は、Brazeのワークスペース・レベルで適用される。Facebookの管理者がFacebookビジネスマネージャーからあなたを削除したり、接続されているFacebookアカウントへのアクセスを削除した場合、Brazeは無効なトークンを検出する。そのため、Facebook オーディエンスコンポーネントを使用しているアクティブなキャンバスにはエラーが表示され、Braze はユーザーを同期できません。 
 
 {% alert important %}
-過去に[広告管理](https://developers.facebook.com/docs/facebook-login/permissions/#reference-ads_management)および[広告管理スタンダード](https://developers.facebook.com/docs/marketing-api/access#standard)アクセスのFacebookアプリレビュープロセスを受けたことがあるお客様のシステムユーザートークンは、Facebookオーディエンスコンポーネントに対して引き続き有効である。Facebookパートナー・ページを通じてFacebookシステム・ユーザートークンを編集したり、取り消したりすることはできない。その代わりに、Facebookアカウントに接続して、Brazeワークスペース内でFacebookシステムユーザートークンを置き換えることができる。 
+これまでに [Ads Management](https://developers.facebook.com/docs/facebook-login/permissions/#reference-ads_management) および [Ads Management Standard Acces](https://developers.facebook.com/docs/marketing-api/access#standard) の Facebookアプリレビュープロセスを受けたことがある顧客のシステムユーザートークンは、Facebook オーディエンスコンポーネントに対して引き続き有効です。Facebookパートナー・ページを通じてFacebookシステム・ユーザートークンを編集したり、取り消したりすることはできない。その代わりに、Facebookアカウントに接続して、Brazeワークスペース内でFacebookシステムユーザートークンを置き換えることができる。 
 
-<br><br>Facebook oAuthの設定は、[セグメントを経由したFacebookのエクスポートにも]({{site.baseurl}}/partners/message_orchestration/additional_channels/retargeting/facebook/#prerequisites)適用される。
+<br><br>Facebook oAuth 設定は、[セグメントを使用した Facebook のエクスポート]({{site.baseurl}}/partners/message_orchestration/additional_channels/retargeting/facebook/#prerequisites)にも適用されます。
 {% endalert %}
 
 ### ステップ2:カスタムオーディエンスの利用規約に同意する
 
-キャンバスを構築する前に、まずFacebookのカスタムオーディエンスの利用規約に同意する必要がある。利用規約は以下のリンクから確認できる：
+キャンバスを作成する前に、まず Facebook カスタムオーディエンスの利用規約に同意する必要があります。利用規約は以下のリンクから確認できる：
 `https://business.facebook.com/ads/manage/customaudiences/tos/?act=<your_ad_account_id>`
 
-### ステップ3:キャンバスフローにFacebookオーディエンスコンポーネントを追加する
+### ステップ3:キャンバスフローで Facebook オーディエンスコンポーネントを追加する
 
-キャンバスにコンポーネントを追加し、**Facebook Audienceを**選択する。
+キャンバスにコンポーネントを追加し、\[**Facebook オーディエンス**] を選択します。
 
 ![][18]{: style="max-width:35%;"} ![][20]{: style="max-width:28%;"}
 
-### ステップ4:シンクの設定
+### ステップ4:同期設定
 
-**Custom Audience**ボタンをクリックして、コンポーネント・エディターを開く。
+\[**カスタムオーディエンス**] ボタンをクリックしてコンポーネントエディターを開きます。
 
-**Facebookを**Audience Syncのパートナーとして選択する。
+**Facebook** を目的のオーディエンス同期パートナーとして選択します。
 
 ![][19]{: style="max-width:80%;"}
 
@@ -89,60 +89,60 @@ Facebookとの接続は、Brazeのワークスペース・レベルで適用さ
 
 {% tabs %}
 {% tab 新しいオーディエンスを作る %}
-**新しいオーディエンスを作る**<br>
-新しいカスタムオーディエンスの名前を入力し、**Add Users to Audienceを**選択し、Facebookと同期したいフィールドを選択する。次に、ステップエディタの下部にある**Create Audience**ボタンをクリックしてオーディエンスを保存する。
+**新規オーディエンスの作成**<br>
+新しいカスタムオーディエンスの名前を入力し、\[**ユーザーをオーディエンスに追加**] を選択し、Facebook と同期するフィールドを選択します。次に、ステップエディタの下部にある**Create Audience**ボタンをクリックしてオーディエンスを保存する。
 
 ![]({% image_buster /assets/img/audience_sync/fb_sync.png %})
 
-次に、ステップエディタの下部にあるCreate Audienceボタンをクリックしてオーディエンスを保存する。オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合、ステップエディタの上部にユーザーに通知される。また、オーディエンスはドラフトモードで作成されたため、ユーザーはキャンバスの旅の後半でユーザーを削除するためにこのオーディエンスを参照することができる。
+次に、ステップエディターの下部にある \[オーディエンスを作成] ボタンをクリックしてオーディエンスを保存します。オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合、ステップエディタの上部にユーザーに通知される。ユーザーは、後でキャンバスジャーニーでユーザーを削除するためにこのオーディエンスを参照することもできます。これは、オーディエンスが下書きで作成されたためです。
 
 ![]({% image_buster /assets/img/audience_sync/fb_sync2.png %})
 
-新しいオーディエンスでキャンバスを立ち上げると、Brazeはキャンバスの立ち上げと同時に新しいカスタムオーディエンスを作成し、その後、オーディエンス同期ステップに入ったユーザーをほぼリアルタイムで同期する。
+新しいオーディエンスを使用してキャンバスを起動すると、Braze はキャンバスの起動時にカスタムオーディエンスを作成し、その後、オーディエンスがオーディエンスの同期ステップに入るたびに、ほぼリアルタイムでユーザーが同期されます。
 
 {% endtab %}
 {% tab 既存のオーディエンスと同期する %}
-**既存のオーディエンスと同期する**<br>
-Brazeはまた、既存のFacebookカスタムオーディエンスからユーザーを追加または削除し、これらのオーディエンスが最新であることを確認する機能も提供している。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンス名を入力し、**オーディエンスに追加**するか、**オーディエンスから削除**するかを選択する。Brazeは、ユーザーがFacebook Audienceのステップに入ると、ほぼリアルタイムでユーザーを追加または削除する。 
+**既存のオーディエンスとの同期**<br>
+Brazeはまた、既存のFacebookカスタムオーディエンスからユーザーを追加または削除し、これらのオーディエンスが最新であることを確認する機能も提供している。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンスの名前を入力し、\[**ユーザーをオーディエンスに追加**] または \[**オーディエンスからユーザーを削除**] のいずれかを選択します。Brazeは、ユーザーがFacebook Audienceのステップに入ると、ほぼリアルタイムでユーザーを追加または削除する。 
 
 ![]({% image_buster /assets/img/audience_sync/fb_sync3.png %})
 
-Facebookは、オーディエンスサイズが低すぎる（通常1,000人未満）場合、カスタムオーディエンスからユーザーを削除することを禁止していることに注意することが重要だ。その結果、Brazeは、オーディエンスが適切なオーディエンスサイズに達するまで、オーディエンスからの削除ステップのユーザーを同期することができない。
+Facebook では、オーディエンスの規模が小さすぎる場合 (通常は1,000未満)、カスタムオーディエンスからユーザーを削除できないことにご注意ください。そのため、オーディエンスが所定のオーディエンス規模に達するまで、Braze ではオーディエンスから削除ステップでユーザーを同期できません。
 
 {% endtab %}
 {% endtabs %}
 
 ### ステップ 5: キャンバスを立ち上げる
 
-Facebook Audienceコンポーネントの設定が完了したら、キャンバスを起動するだけだ！新しいカスタムオーディエンスが作成され、Facebook Audienceコンポーネントを経由して流入したユーザーは、Facebook上のこのカスタムオーディエンスに渡される。キャンバスに後続のコンポーネントが含まれていれば、ユーザーはユーザー・ジャーニーの次のステップに進むことができる。
+Facebook オーディエンスコンポーネントの設定が完了したら、キャンバスを起動できます。新しいカスタムオーディエンスが作成され、Facebook オーディエンスコンポーネントを通過するユーザーは Facebook のこのカスタムオーディエンスに送られます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーはユーザージャーニーの次のステップに進みます。
 
-Facebookオーディエンスマネージャーのカスタムオーディエンスの**履歴**タブには、Brazeからオーディエンスに送られたユーザー数が反映される。ユーザーがステップに再入力すると、再びフェイスブックに送られる。
+Facebookオーディエンスマネージャーのカスタムオーディエンスの**履歴**タブには、Brazeからオーディエンスに送られたユーザー数が反映される。ユーザーがこのステップに再び入ると、Facebook に再度送信されます。
 
-![オーディエンスの詳細と、アクティビティ、アクティビティの詳細、変更されたアイテム、日時の列を含むオーディエンス履歴テーブルを含む、指定されたFacebookオーディエンスの履歴タブ。][9]{: style="max-width:80%;"}
+![オーディエンスの詳細と、特定の Facebook オーディエンスの「履歴」タブ。このタブには、アクティビティ、アクティビティの詳細、変更されたアイテム、および日時の列を含む「オーディエンス履歴」が表示されている。][9]{: style="max-width:80%;"}
 
-## メタ・ワーク・アカウントへの移行
+## Meta ワークアカウントへの移行
 
-2023年7月から、Metaはこの新しいアカウントタイプの採用に関心を持つ少数の企業に対して、Meta workアカウントを展開している。Brazeと統合されたビジネスアカウントをお持ちの場合は、この実装を維持し、アクティブなCanvasを中断させないために、ビジネスアカウントで[Facebookパートナーページへの]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync#step-1-connect-to-facebook)接続を解除し、再接続してください。
+2023年7月より、Meta は Meta ワークアカウントという新しいアカウントタイプを、その導入に関心のある少数の企業向けに展開しています。Braze と統合されたビジネスアカウントをお持ちの場合は、この実装を維持し、アクティブなキャンバスの動作を中断させないために、ビジネスアカウントで [Facebook パートナーページ]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync#step-1-connect-to-facebook)への接続を切断し、再接続してください。
 
 ## ユーザー同期とレート制限の考慮
  
 ユーザーがオーディエンス同期ステップに達すると、Brazeはほぼリアルタイムでこれらのユーザーを同期し、同時にFacebookのMarketing APIレート制限を尊重する。これが実際に意味するのは、BrazeはFacebookにユーザーを送る前に、5秒ごとにできるだけ多くのユーザーをバッチ処理しようとするということだ。 
 
-FacebookのマーケティングAPIのレート制限では、各広告アカウントのAPIリクエストは1時間あたり190kまでとなっている。Brazeの顧客がこのレート制限に達した場合、Braze the Canvasは最大13時間まで同期を再試行する。同期が不可能な場合、これらのユーザーはUsers Erroredメトリックの下にリストされる。
+Facebook の Marketing API のレート制限では、各広告アカウントで1時間あたり19万件のリクエストを超えないように設定されています。Brazeの顧客がこのレート制限に達した場合、Braze the Canvasは最大13時間まで同期を再試行する。同期が不可能な場合、これらのユーザーはUsers Erroredメトリックの下にリストされる。
 
 ## アナリティクスを理解する
 
-以下の表は、Audience Syncコンポーネントのアナリティクスをより理解するのに役立つメトリクスとその説明である。
+次の表に、オーディエンス同期コンポーネントからの分析をよりよく理解するのに役立つ指標と説明を示します。
 
-| メートル | 説明 |
+| 指標 | 説明 |
 | --- | --- |
-| 入団 | Facebookに同期されるこのコンポーネントを入力したユーザーの数。 |
-| 次のステップへ進む | 次のコンポーネントがある場合、何人のユーザーが次のコンポーネントに進んだか。これがキャンバスブランチの最後のステップであれば、すべてのユーザーが自動で進む。 |
+| 入力 | Facebook と同期するためにこのコンポーネントに入ったユーザーの数。 |
+| 次のステップへ進む | 次のコンポーネントがある場合、次のコンポーネントに進んだユーザーの数。これがキャンバスブランチの最後のステップである場合、すべてのユーザーは自動的に進みます。 |
 | 同期されたユーザー | Facebookとの同期に成功したユーザー数。 |
 | 同期されていないユーザー | 一致するフィールドがないために同期されていないユーザーの数。 |
 | 保留中のユーザー | 現在、BrazeがFacebookへの同期処理を行っているユーザー数。 |
-| ユーザーエラー | 約13時間の再試行後、APIエラーのためにFacebookに同期されなかったユーザーの数。エラーの原因としては、無効なFacebookトークンや、Facebook上でカスタムオーディエンスが削除された場合などが考えられる。 |
-| イグジット・キャンバス | キャンバスを退出したユーザーの数。これは、キャンバスの最後のステップがフェイスブックのステップである場合に発生する。 |
+| エラーが発生したユーザー数 | 約13時間の再試行後、APIエラーのためにFacebookに同期されなかったユーザーの数。エラーの原因としては、無効なFacebookトークンや、Facebook上でカスタムオーディエンスが削除された場合などが考えられる。 |
+| 終了済みのキャンバス | キャンバスを退出したユーザーの数。これは、キャンバスの最後のステップが Facebook ステップである場合に発生します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert important %}
@@ -152,46 +152,46 @@ FacebookのマーケティングAPIのレート制限では、各広告アカウ
 ## トラブルシューティング
 
 {% details 無効なトークンエラーが表示された場合、次に何をすればよいか？ %}
-フェイスブックのパートナー・ページで、フェイスブックのアカウントを切断し、再接続するだけだ。Facebookビジネスマネージャー管理者に、同期したい広告アカウントに適切な権限があることを確認する。
+Facebook パートナーページで Facebook アカウントの接続を解除してから再接続できます。同期する広告アカウントに対する適切なアクセス許可があることを Facebook Business Manager 管理者に確認します。
 {% enddetails %}
 
 {% details なぜキャンバスは起動できないのか？ %}
 - システムユーザートークンが認証され、Facebook Business Managerの目的の広告アカウントにアクセスできることを確認する。
 - 広告アカウントを選択し、新しいカスタムオーディエンスの名前を入力し、一致するフィールドを選択していることを確認する。
-- フェイスブックのカスタムオーディエンスが500人に達したかもしれない。キャンバスを使用して新しいカスタムオーディエンスを作成する前に、Facebookオーディエンスマネージャーで不要なオーディエンスを削除しよう。
+- Facebook のカスタムオーディエンス数の上限である500に達した可能性があります。キャンバスを使用して新しいカスタムオーディエンスを作成する前に、Facebook オーディエンスマネージャーで不要なオーディエンスを削除します。
 {% enddetails %}
 
-{% details Facebookにユーザーを渡した後、ユーザーがマッチングしたかどうかを知るには？ %}
+{% details ユーザーを Facebook に渡した後、ユーザーが一致したかどうかを知るにはどうすればよいですか? %}
 フェイスブックはプライバシー保護のため、この情報を提供していない。
 {% enddetails %}
 
 {% details Brazeはバリューベースのカスタムオーディエンスに対応しているか？ %}
-現時点では、バリューベースのカスタムオーディエンスはBrazeではサポートされていない。このようなタイプのカスタムオーディエンスの同期に興味がある場合は、[製品フィードバックを]({{site.baseurl}}/user_guide/administrative/access_braze/portal/)送信してほしい。
+現時点では、バリューベースのカスタムオーディエンスはBrazeではサポートされていない。このようなタイプのカスタムオーディエンスの同期に関心がある場合は、[製品フィードバック]({{site.baseurl}}/user_guide/administrative/access_braze/portal/)をお送りください。
 {% enddetails %}
 
-{% details バリューベースのそっくりさんカスタムオーディエンスの同期に関する問題を解決するには？ %}
+{% details 値に基づく類似カスタムオーディエンスの同期に関する問題を解決するにはどうしたらよいですか? %}
 
-現時点では、価値ベースのそっくりさんカスタムオーディエンスはBrazeでは想定されていない。このオーディエンスに同期しようとすると、オーディエンスの同期ステップでエラーが発生する可能性がある。これを解決するには、以下の手順に従ってほしい：
+現時点では、値ベースの類似カスタムオーディエンスは Braze ではサポートされていません。このオーディエンスに同期しようとすると、オーディエンスの同期ステップでエラーが発生する可能性があります。これを解決するには、次の手順に従います。
 
-1. Facebook広告マネージャのダッシュボードに行き、**オーディエンスを**選択する。
-2. **Create audience**>**Custom audienceを**選択する。
-3. **顧客リストを**選択する。
-4. **Value**列を除いたCSVまたはリストをアップロードする。**Noを**選択し**、顧客価値を含まない顧客リストで続行する**。
-5. カスタムオーディエンスの作成を完了する。
-6. BrazeのFacebook Audience Syncステップを、作成したカスタムオーディエンスで更新する。
+1. Facebook Ad Manager ダッシュボードを開き、\[**Audiences**] を選択します。
+2. \[**Create audience**] > \[**Custom audience**] を選択します。
+3. \[**Customer list**] を選択します。
+4. **Value**列を除いたCSVまたはリストをアップロードする。\[**No, continue with a customer list that doesn't include customer value**] を選択します。
+5. カスタムオーディエンスの作成を完了します。
+6. Braze で、作成したカスタムオーディエンスで Facebook オーディエンスの同期ステップを更新します。
 {% enddetails %}
 
-{% details Facebookのカスタムオーディエンス利用規約に関連するメールを受け取った。これを解決するにはどうすればいいのか？ %}
-FacebookへのAudience Syncを使用するには、これらの利用規約に同意していることを確認する必要がある。 
+{% details Facebookのカスタムオーディエンス利用規約に関連するメールを受け取った。これを解決するにはどうすればよいですか? %}
+Audience Sync to Facebook を使用するには、これらのサービス利用規約に同意していることを確認する必要があります。 
 
-広告アカウントが直接個人のFacebookアカウントに関連付けられている場合は、このリンクに従い、TOSに同意する[： https://www.facebook.com](https://www.facebook.com/ads/manage/customaudiences/tos.php)/[ads/manage/customaudiences/tos.php](https://www.facebook.com/ads/manage/customaudiences/tos.php)
+広告アカウントが直接個人のFacebookアカウントに関連付けられている場合は、このリンクに従い、TOSに同意する：[https://www.facebook.com/ads/manage/customaudiences/tos.php](https://www.facebook.com/ads/manage/customaudiences/tos.php)
 
-広告アカウントが御社のビジネス・マネージャー・アカウントにリンクされている場合は、ビジネス・マネージャー・アカウントからTOSに同意する必要がある：<br>
+広告アカウントが会社のビジネスマネージャーアカウントに関連付けられている場合、次のリンクに従ってそのビジネスマネージャーアカウントからもサービス使用条件に同意する必要があります。<br>
 [https://business.facebook.com/customaudiences/value_based/tos.php?act=ACCOUNT_ID&business_id=BUSINESS_ID](https://business.facebook.com/customaudiences/value_based/tos.php?act=ACCOUNT_ID&business_id=BUSINESS_ID)
 
-Facebookのカスタムオーディエンスの利用規約に同意したら、次のことを行う必要がある：
+Facebook カスタムオーディエンスのサービス使用条件に同意した後、以下を行う必要があります。
 1. Facebookアカウントを一旦切断し、再接続することで、BrazeでFacebookアクセストークンをリフレッシュする。
-2.  キャンバスを編集して更新し、Facebookオーディエンス同期ステップを再度有効にする。
+2.  キャンバスを編集して更新することにより、Facebook オーディエンスの同期ステップを再度有効にします。
 Brazeは、ユーザーがFacebookのオーディエンス・ステップに到達すると、すぐに同期できるようになる。
 {% enddetails %}
 
diff --git a/_lang/ja/_partners/canvas_steps/faq.md b/_lang/ja/_partners/canvas_steps/faq.md
index 964c33b8eb5..7c97fda2dff 100644
--- a/_lang/ja/_partners/canvas_steps/faq.md
+++ b/_lang/ja/_partners/canvas_steps/faq.md
@@ -1,7 +1,7 @@
 ---
 nav_title: よくある質問
-article_title: オーディエンス・シンク FAQ
-description: "この記事では、Audience Syncに関するよくある質問に対する回答を提供する。"
+article_title: オーディエンスの同期に関するよくある質問
+description: "この記事では、オーディエンスの同期に関してよくある質問にお答えします。"
 page_order: 80
 Tool:
   - Canvas
@@ -10,47 +10,47 @@ Tool:
 
 # よくある質問
 
-> この記事では、Audience Syncに関するよくある質問に対する回答を紹介する。
+> この記事では、オーディエンスの同期に関してよくあるいくつかの質問にお答えします。
 
-### Audience Syncパートナー・ダッシュボードにオーディエンスが表示されるまでにどのくらい時間がかかるか？ 
+### オーディエンスの同期パートナーのダッシュボードに、オーディエンスが取り込まれるまでどのくらいの時間がかかりますか? 
 
-視聴者の入力にかかる時間は、特定のパートナーによって異なる。
+オーディエンスの取り込みにかかる時間は、パートナーに応じて異なります。
 
 すべてのネットワークがBrazeからのリクエストを処理し、ユーザーとのマッチングを試みる。このプロセスには通常6～48時間かかる。
 
-具体的な時間範囲は、各Audience Syncパートナーのドキュメント内の「Troubleshooting」セクションで確認できる。 
+オーディエンスの同期の各パートナーのドキュメントでトラブルシューティングセクションを参照し、特定の時間範囲を確認できます。 
 
-### Audience Syncで使用できるファーストパーティデータの種類は？
+### オーディエンスの同期ではどのようなファーストパーティデータを使用できますか?
 
-各パートナーに使用される特定のフィールドは、パートナーの要件によって異なる場合がある。 
+各パートナーに使用される特定のフィールドは、パートナーの要件によって異なることがあります。 
 
-例えば、Facebookにオーディエンス・シンクを設定する場合、Eメール、電話、名前、姓など、さまざまなファーストパーティ・フィールドを使うことができるが、Snapchatの場合は、Eメール、電話、モバイル広告主IDのいずれかしか選択できない。 
+たとえば、Audience Sync to Facebook を設定すると、メール、電話、名、姓などのさまざまなファーストパーティフィールドを使用できますが、Snapchat の場合は、メール、電話番号、またはモバイル広告主 ID のいずれかのみを選択できます。 
 
-同期するために選択できるユーザーフィールドは、Brazeの標準属性とモバイル広告IDに相関していることに注意することが重要である。当社のSDKやAPIを経由して、このデータを適切に渡すようにしなければならない。 
+同期するために選択できるユーザーフィールドは、Brazeの標準属性とモバイル広告IDに相関していることに注意することが重要である。Braze の SDK や API を使用してこのデータを適切に渡すようにする必要があります。 
 
-### 私のデータが各Audience Syncパートナーに送信するために処理されるとき、何が起こるのか？
+### オーディエンスの同期の各パートナーに送信するためにデータが処理されるときには、どのような処理が行われますか?
 
-Audience Syncの送信先として選択したデータは正規化される。各パートナーは、API要件に基づいてデータの正規化について異なる仕様を持っている可能性があるため、詳細については各パートナー固有のエンドポイントを確認してほしい。
+オーディエンスの同期の宛先に送信するデータとして選択されたデータは、正規化されます。各パートナーは、API要件に基づいてデータの正規化について異なる仕様を持っている可能性があるため、詳細については各パートナー固有のエンドポイントを確認してほしい。
 
-さらに、Brazeは、Audience Syncパートナーとユーザーを同期する前に、すべてのデータをハッシュ化し、すべてのPIIがSHA256を使用してハッシュ化されるようにする。
+さらに Brazeは、オーディエンスの同期のパートナーとユーザーを同期する前に、すべてのデータをハッシュ化します。これにより、すべての PII が SHA256 を使用してハッシュ化されます。
 
-### オーディエンス・シンクを作成、管理する際に起こりうる最も一般的なエラーとは？
+### オーディエンスの同期を作成、管理する際に発生する可能性がある最も一般的なエラーは何ですか?
 
 - **無効なトークン**<br>
   - 典型的な原因としては、特定の広告ネットワークにログインするためのパスワードを変更した場合や、認証情報の有効期限が切れた場合などがある。
-  - この問題を解決するには、問題の特定のパートナーページに入り、アカウントを切断して再接続するだけでよい。
-- **観客数が少なすぎる**<br>
-  - このエラーは通常、オーディエンスからユーザーを削除するオーディエンス同期ステップを作成した場合に発生する。視聴者数がゼロに近づくと、ネットワークは視聴者数が少なすぎて配信できないというフラグを立てることができる。 
-  - この問題を解決するには、オーディエンスのサイズが完全に枯渇しないように、定期的にユーザーを追加・削除するオーディエンス同期戦略を検討していることを確認すること。
-- **観客は存在しない**<br>
-  - このエラーは、オーディエンス同期ステップが存在しないオーディエンスを使用しているために発生する。これは、オーディエンスにアクセスするために必要な権限を持っていない場合にも引き起こされる可能性がある。 
-  - この問題を解決するには、オーディエンス同期設定内にアクティブなオーディエンスを追加するか、新しいオーディエンスを作成する。
-- **広告アカウントへのアクセスを試みる**<br>
+  - この問題を解決するには、当該パートナーのページに移動して、アカウントの接続を解除してから再接続します。
+- **オーディエンスのサイズが小さすぎる**<br>
+  - このエラーは通常、オーディエンスからユーザーを削除するオーディエンスの同期ステップを作成した場合に発生します。オーディエンスのサイズがゼロに近づくと、ネットワークにより、オーディエンスのサイズが小さすぎて提供できないというフラグが設定されることがあります。 
+  - この問題を解決するには、オーディエンスのサイズが完全に枯渇することがないように、定期的にユーザーを追加および削除するオーディエンス同期戦略を検討するようにしてください。
+- **オーディエンスが存在しない**<br>
+  - このエラーは、オーディエンスの同期ステップが存在しないオーディエンスを使用しているために発生します。これは、オーディエンスにアクセスするために必要な権限を持っていない場合にも発生することがあります。 
+  - この問題を解決するには、オーディエンスの同期の設定でアクティブなオーディエンスを追加するか、新しいオーディエンスを作成します。
+- **広告アカウントへのアクセスが試行される**<br>
   - このエラーは、選択した広告アカウントおよび/またはオーディエンスの権限がない場合に発生する。
-  - この問題を解決するには、広告アカウントの管理者と協力して、適切なアクセス権とパーミッションを取得してほしい。 
-- **無効な設定**<br>
-  - このエラーは、広告アカウント、オーディエンス、またはユーザーフィールドを含む、特定のオーディエンス同期先をキャンバスで設定していない場合に発生する。 
+  - この問題を解決するには、広告アカウントの管理者と協力して、適切なアクセスと権限を取得します。 
+- **設定が無効**<br>
+  - このエラーは、照合する広告アカウント、オーディエンス、またはユーザーのフィールドを含む、特定のオーディエンスの同期の宛先をキャンバスで設定していない場合に発生します。 
   - この問題を解決するには、起動する前に各パートナーのコンフィギュレーションを完了させる。
-- **利用規約**<br>
-  - Facebookのような一部のAudience Sync配信先では、Audience Sync機能を使用するために、特定の利用規約に同意することが広告ネットワークによって義務付けられている。このエラーは、あなたが適切な条件を承諾していない場合に発生する。 
-  - この問題を解決するには、各パートナーの要求する条件を受け入れていることを確認する。特にフェイス[ブックについては](https://www.braze.com/docs/partners/canvas_steps/facebook_audience_sync/#troubleshooting)、[フェイスブックのトラブルシューティングを](https://www.braze.com/docs/partners/canvas_steps/facebook_audience_sync/#troubleshooting)確認してほしい。 
+- **サービス利用規約**<br>
+  - Facebook などの一部のオーディエンスの同期の宛先では、広告ネットワークにより特定のサービス利用規約に同意することが義務付けられています。このエラーは、該当する利用規約に同意していない場合に発生します。 
+  - この問題を解決するには、各パートナーの要求する条件を受け入れていることを確認する。特に Facebook については、[Facebook のトラブルシューティング](https://www.braze.com/docs/partners/canvas_steps/facebook_audience_sync/#troubleshooting)を確認してください。 
diff --git a/_lang/ja/_partners/canvas_steps/google_audience_sync.md b/_lang/ja/_partners/canvas_steps/google_audience_sync.md
index 6828e9a219b..4b23344a75a 100644
--- a/_lang/ja/_partners/canvas_steps/google_audience_sync.md
+++ b/_lang/ja/_partners/canvas_steps/google_audience_sync.md
@@ -1,5 +1,5 @@
 ---
-nav_title: グーグル
+nav_title: Google
 article_title: キャンバス オーディエンス Googleに同期
 alias: /google_audience_sync/
 description: "このリファレンス記事では、Brazeオーディエンス同期をGoogleに使用して、行動トリガー、セグメンテーションなどに基づいて広告を配信する方法について説明します。"
@@ -12,48 +12,48 @@ page_order: 2
 # オーディエンスをGoogleに同期する
 
 {% alert important %}
-Googleは、2024年3月6日から施行される[デジタル市場法（DMA）](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)の変更に対応して、[EUユーザー同意ポリシー](https://www.google.com/about/company/user-consent-policy/)を更新しています。この新しい変更により、広告主はEEAおよび英国のエンドユーザーに特定の情報を開示し、必要な同意を得る必要があります。次のドキュメントを確認して、詳細を学んでください。
+Googleは、2024年3月6日から施行される[デジタル市場法（DMA）](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)の変更に対応して、[EUユーザー同意ポリシー](https://www.google.com/about/company/user-consent-policy/)を更新しています。この新しい変更により、広告主は EEA および英国のエンドユーザーに特定の情報を開示し、必要な同意を得る必要があります。次のドキュメントを確認して、詳細を学んでください。
 {% endalert %}
 
-Brazeオーディエンス同期をGoogle統合により、ブランドはクロスチャネルの顧客ジャーニーのリーチをGoogle検索、Googleショッピング、Gmail、YouTube、およびGoogleディスプレイに拡張できます。最初のパーティーの顧客データを使用して、ダイナミックな行動トリガー、セグメンテーションなどに基づいて安全に広告を配信できます。Braze キャンバスの一部としてメッセージ（例えば、プッシュ、メール、またはSMS）をトリガーするために通常使用する任意の基準を使用して、Googleの[顧客マッチ](https://support.google.com/google-ads/answer/6379332?hl=en)を介してそのユーザーに広告をトリガーすることができます。
+Braze Audience Sync to Google 統合により、ブランドは、クロスチャネルのカスタマージャーニーの範囲を Google 検索、Google ショッピング、Gmail、YouTube、および Google ディスプレイに拡大できます。ファーストパーティの顧客データを使用して、ダイナミックな行動トリガー、セグメンテーションなどに基づいて安全に広告を配信できます。Braze キャンバスの一部としてメッセージ（例えば、プッシュ、メール、またはSMS）をトリガーするために通常使用する任意の基準を使用して、Googleの[顧客マッチ](https://support.google.com/google-ads/answer/6379332?hl=en)を介してそのユーザーに広告をトリガーすることができます。
 
 {% alert important %}
-2023年5月1日より、Google 広告はターゲティングおよびレポートのために「類似オーディエンス」（「類似オーディエンス」とも呼ばれる）を生成しなくなります。[Google 広告ドキュメント](https://support.google.com/google-ads/answer/12463119?)を参照して詳細を確認してください。
+2023年5月1日以降、Google 広告は、ターゲティングおよびレポート用に「類似オーディエンス」とも呼ばれる類似性の高いオーディエンスを生成しません。[Google 広告ドキュメント](https://support.google.com/google-ads/answer/12463119?)を参照して詳細を確認してください。
 {% endalert %}
 
-カスタムオーディエンスの同期の一般的な使用例には以下が含まれます：
-- 複数のチャネルを介して高価値ユーザーをターゲットにして、購入またはエンゲージメントを促進します。
+**カスタムオーディエンス同期の一般的なユースケースには次のものがあります。**
+- 複数のチャネルを通じて価値の高いユーザーをターゲットにして、購入やエンゲージメントを促進する。
 - 他のマーケティングチャネルに対してレスポンシブでないユーザーをリターゲティングする。
-- ブランドの忠実な消費者である場合に、ユーザーが広告を受け取らないようにするための抑制オーディエンスの作成。
+- すでに自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑制オーディエンスを作成する。
 
 {% alert note %}
-この機能により、ブランドはどの特定のファーストパーティデータをGoogleと共有するかをコントロールできます。Brazeでは、ファーストパーティデータを共有できる統合と共有できない統合が最優先で考慮されます。Brazeのデータプライバシーポリシーの詳細については、[こちら](https://www.braze.com/privacy)をクリックしてください。
+この機能により、ブランドはどの特定のファーストパーティデータをGoogleと共有するかをコントロールできます。Braze では、ファーストパーティデータを共有できる統合と共有できない統合を最大限に考慮しています。Brazeのデータプライバシーポリシーの詳細については、[こちら](https://www.braze.com/privacy)をクリックしてください。
 {% endalert %}
 
 ## 前提条件
 
-キャンバスでGoogle オーディエンスのステップを設定する前に、次の項目が作成され、完了していることを確認する必要があります。
+キャンバスで Google オーディエンスステップを設定する前に、以下の項目が作成、完了していることを確認する必要があります。
 
-| 要件 | Origin | 説明 |
+| 要件 | 提供元 | 説明 |
 | ----------- | ------ | ----------- |
-| Google 広告アカウント | [グーグル](https://support.google.com/google-ads/answer/6366720?hl=en) | あなたのブランドのためのアクティブなGoogle 広告アカウント。<br><br>複数の管理アカウントにオーディエンスを共有したい場合は、オーディエンスを[マネージャーアカウント](https://support.google.com/google-ads/answer/6139186)にアップロードできます。 |
-| Google 広告規約とGoogle 広告ポリシー | [グーグル](https://support.google.com/adspolicy/answer/54818?hl=en) | Braze Audience Syncを使用するにあたり、[Googleの広告利用規約](https://payments.google.com/u/0/paymentsinfofinder?hostOrigin=aHR0cHM6Ly9wYXltZW50cy5nb29nbGUuY29tOjQ0Mw..&sri=-40)および[Googleの広告ポリシー](https://support.google.com/adspolicy/answer/6008942?sjid=15557182366992806023-NC)、該当する場合には[EUユーザー同意ポリシー](https://www.google.com/about/company/user-consent-policy/)を受け入れ、遵守する必要があります。<br><br>Google の新しい EU ユーザー同意ポリシーについて法務チームに相談し、EEA/英国のエンドユーザーに Google 広告のサービスを利用するために適切な同意を得ていることを確認してください。 |
-| Google 顧客 Match | [グーグル](https://support.google.com/google-ads/answer/6299717) |  顧客マッチはすべての広告主に利用できるわけではありません。<br><br>**顧客マッチを使用するには、アカウントに以下が必要です:**<br>• ポリシー遵守の良い歴史<br>• 良好な支払い履歴<br>• Google 広告での少なくとも90日の履歴<br>• 生涯総支出が50,000米ドルを超える。USD以外の通貨で管理されている広告主の場合、支出額はその通貨の月平均コンバージョンレートを使用してUSDに変換されます。<br><br>お客様のアカウントがこれらの基準を満たしていない場合、お客様のアカウントは現在、顧客マッチを使用する資格がありません。<br><br>Google 広告担当者に連絡して、アカウントの顧客マッチの利用可能性について詳しく確認してください。 |
-| Googleの同意シグナル | [グーグル](https://support.google.com/google-ads/answer/14310715) |  EEAのエンドユーザーにGoogleの顧客マッチサービスを使用して広告を配信したい場合、GoogleのEUユーザー同意ポリシーの一環として、次のカスタム属性（ブール値）をBrazeに渡す必要があります。詳細については、[EEAおよび英国のエンドユーザーの同意を収集する](#collecting-consent-for-eea-and-uk-end-users)の下にあります。<br> `$google_ad_user_data`<br> - `$google_ad_personalization` |
+| Google 広告アカウント | [Google](https://support.google.com/google-ads/answer/6366720?hl=en) | あなたのブランドのためのアクティブなGoogle 広告アカウント。<br><br>複数の管理対象アカウントでオーディエンスを共有する場合は、[マネージャーアカウント](https://support.google.com/google-ads/answer/6139186)にオーディエンスをアップロードできます。 |
+| Google 広告規約とGoogle 広告ポリシー | [Google](https://support.google.com/adspolicy/answer/54818?hl=en) | Braze Audience Syncを使用するにあたり、[Googleの広告利用規約](https://payments.google.com/u/0/paymentsinfofinder?hostOrigin=aHR0cHM6Ly9wYXltZW50cy5nb29nbGUuY29tOjQ0Mw..&sri=-40)および[Googleの広告ポリシー](https://support.google.com/adspolicy/answer/6008942?sjid=15557182366992806023-NC)、該当する場合には[EUユーザー同意ポリシー](https://www.google.com/about/company/user-consent-policy/)を受け入れ、遵守する必要があります。<br><br>Google の新しい EU ユーザー同意ポリシーについて法務チームに相談し、EEA/英国のエンドユーザーに Google 広告のサービスを利用するために適切な同意を得ていることを確認してください。 |
+| Google カスタマーマッチ | [Google](https://support.google.com/google-ads/answer/6299717) |  すべての広告主がカスタマーマッチを利用できるわけではありません。<br><br>**カスタマーマッチを使用するには、アカウントが以下の条件を満たしている必要があります。**<br>• これまでポリシーを遵守してきた実績があること<br>• これまで支払いに関して問題が発生していないこと<br>• Google 広告で 90 日以上の利用実績があること<br>• 利用金額が通算5万米ドルを超えていること米ドル以外の通貨でアカウントを管理している広告主の利用金額は、その通貨の月別平均為替レートで米ドルに換算されます。<br><br>アカウントが上記の要件を満たしていない場合、現時点ではそのアカウントではカスタマーマッチを利用できません。<br><br>Google 広告の担当者に連絡して、アカウントでのカスタマーマッチの利用可能性について詳しいガイダンスを受けてください。 |
+| Google の同意シグナル | [Google](https://support.google.com/google-ads/answer/14310715) |  EEAのエンドユーザーにGoogleの顧客マッチサービスを使用して広告を配信したい場合、GoogleのEUユーザー同意ポリシーの一環として、次のカスタム属性（ブール値）をBrazeに渡す必要があります。詳細については、[EEAおよび英国のエンドユーザーの同意を収集する](#collecting-consent-for-eea-and-uk-end-users)の下にあります。<br> `$google_ad_user_data`<br> `$google_ad_personalization` |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-Braze SDKを使用して同意シグナルを収集する場合、次の最低バージョンを満たしていることを確認してください:
+Braze SDK を使用して同意シグナルを収集する場合は、以下の最小バージョン要件を満たしていることを確認します。
 
 {% sdk_min_versions swift:7.6.0 android:1.3.2 web:3.0.0 %}
 
-### EEAおよび英国のエンドユーザーの同意を収集する
+### EEA および英国のエンドユーザーの同意の収集
 
-Google の EU ユーザー同意ポリシーは、広告主が EEA および 英国 のエンドユーザーに対して以下を開示し、同意を得ることを要求しています。
+Google の EU ユーザー同意ポリシーでは、広告主が EEA および英国のエンドユーザーに以下の内容を開示し、その同意を得ることが求められています。
 
-* クッキーやその他のローカルストレージの使用（法的に必要な場合）; そして
+* 法的に義務付けられている場合の Cookie やその他のローカルストレージの使用
 * 広告のパーソナライゼーションのための個人データの収集、共有、および使用。
 
-これは、米国のエンドユーザーやEEAまたは英国以外に所在する他のエンドユーザーには影響しません。Google の新しい EU ユーザー同意ポリシーについて法務チームに相談し、EEA および英国のエンドユーザーに Google 広告のサービスを利用するために適切な同意を収集していることを確認してください。
+これは、米国のエンドユーザーやEEAまたは英国以外に所在する他のエンドユーザーには影響しません。Google の新しい EU ユーザー同意ポリシーについてお客様の法務部門に相談し、EEA および英国のエンドユーザー向けの Google 広告のサービスを使用するために適切な同意を収集していることを確認してください。
 
 2024年3月6日から施行されるデジタル市場法（DMA）の要件に基づき、広告主はGoogleとデータを共有する際に、EEAのエンドユーザー（英国を除く）の同意を得る必要があります。この変更の一環として、次のブール値カスタム属性としてBrazeで両方の同意シグナルを収集できます:
 
@@ -64,18 +64,18 @@ Braze は、これらのカスタム属性からのデータを適切な [Google
 
 #### 同意の取り消しの管理
 
-EEAのエンドユーザーがオーディエンスリストに追加され、その後2つの同意のいずれか（`$google_ad_user_data` または `$google_ad_personalization`）を撤回した場合に、オーディエンスリストを最新の状態に保つために、キャンバスを設定して、オーディエンス同期ステップを使用して既存のオーディエンスリストからユーザーを削除する必要があります。
+EEA のエンドユーザーがオーディエンスリストに追加され、その後2つの同意 (`$google_ad_user_data` または`$google_ad_personalization`) のいずれかを取り消した場合にオーディエンスリストを最新の状態に保つには、オーディエンスの同期ステップを使用して既存のオーディエンスリストからユーザーを削除するようにキャンバスを設定する必要があります。
 
 {% alert note %}
-EEA が以前に両方のシグナルに対して同意を提供していた場合、そのデータはそのリストの有効期限が切れるまで、またはその同意ステータスが Google Audience Sync を介して明示的に更新されるまで、またはその両方が行われるまで、Google の顧客マッチに使用され続けます。
+以前に EEA のエンドユーザーから両方のシグナルへの同意が提出された場合、そのリストの有効期限を経過するか、その同意ステータスが Google オーディエンスの同期により明示的に更新されるか、あるいはこの両方に該当するまで、そのデータが Google のカスタマーマッチに引き続き利用されます。
 {% endalert %}
 
 #### ヒント
 
 * 値をブール型として送信し、文字列型として送信しないでください。
-* 属性名の前にドル記号（$）を付けます。Brazeは、属性名の先頭にドル記号を使用して、これが特別で予約されたキーであることを示します。
+* 属性名の前にドル記号（$）を付けます。Braze は属性名の先頭のドル記号を使用して、これが特殊な予約済みのキーであることを示します。
 * 属性名を小文字で入力してください。
-* 明示的にユーザーを未指定として設定することはできませんが、`null`または`nil`の値、または`true`または`false`でない任意の値を送信すると、Brazeはこのユーザーを`UNSPECIFIED`としてGoogleに渡します。
+* ユーザーを指定なしとして明示的に設定することはできませんが、`null` 値または`nil` 値、あるいは `true` と`false` 以外の値を送信すると、Braze はこのユーザーを `UNSPECIFIED` として Google に渡します。
 * 新しいユーザーが追加または更新され、いずれかの同意属性が指定されていない場合、それらの同意属性が未指定としてマークされてGoogleと同期されます。
 
 必要な同意フィールドと付与されたステータスなしでEEAユーザーを同期しようとすると、Googleはこれを拒否し、このエンドユーザーに広告を配信しません。さらに、EEAユーザーに明示的な同意なしに広告が配信された場合、あなたは責任を負う可能性があり、財政的なリスクにさらされる可能性があります。顧客マッチアップロードパートナー向けのEUユーザー同意ポリシーの詳細については、Googleの[FAQ](https://support.google.com/google-ads/answer/14310715)をご覧ください。 
@@ -84,13 +84,13 @@ EEA が以前に両方のシグナルに対して同意を提供していた場
 
 ### ステップ1:Googleアカウントを接続する
 
-開始するには、**パートナー統合** > **テクノロジーパートナー** > **Google 広告** に移動し、**Google 広告を接続** を選択します。次に、Google 広告アカウントに関連付けられたメールを選択し、Braze に Google 広告アカウントへのアクセスを許可するためのモーダルが表示されます。
+開始するには、**パートナー統合** > **テクノロジーパートナー** > **Google 広告** に移動し、**Google 広告を接続** を選択します。その後モーダルが表示され、Google 広告アカウントに関連付けられているメールを選択し、Google 広告アカウントに Braze アクセスを付与することが促されます。
 
 {% alert note %}
-古いナビゲーションを使用している場合は、統合の下にテクノロジーパートナーを見つけることができます。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-Google 広告アカウントの接続に成功すると、Google 広告パートナーページに戻ります。次に、Brazeワークスペース内でアクセスしたい広告アカウントを選択するように求められます。
+Google 広告アカウントに接続したら、Google 広告パートナーページが再び表示されます。次に、Brazeワークスペース内でアクセスしたい広告アカウントを選択するように求められます。
 
 ![]({% image_buster /assets/img/google_sync/googlesync.gif %}){: style="max-width:85%;"}
 
@@ -100,25 +100,25 @@ Google 広告アカウントの接続に成功すると、Google 広告パート
 ![更新されたGoogle 広告技術ページには、接続された広告アカウントが表示され、アカウントの再同期やモバイル広告IDの追加が可能です。]({% image_buster /assets/img/google_sync/google_sync5.png %}){: style="max-width:75%;"}
 {% endalert %}
 
-### ステップ2:キャンバスフローにGoogle オーディエンスステップを追加
+### ステップ2:キャンバスフローに Google オーディエンスステップを追加する
 
-キャンバスにコンポーネントを追加し、**オーディエンス同期**を選択します。
+キャンバスにコンポーネントを追加し、\[**オーディエンスの同期**] を選択します。
 
 ![][18]{: style="max-width:35%;"} ![][20]{: style="max-width:28%;"}
 
 ### ステップ3:同期設定
 
-**カスタムオーディエンス** ボタンをクリックして、コンポーネントエディタを開封します。
+\[**カスタムオーディエンス**] ボタンをクリックしてコンポーネントエディターを開きます。
 
 希望するオーディエンス同期パートナーとして**Google**を選択します。
 
 ![][19]{: style="max-width:80%;"}
 
-希望するGoogle広告アカウントを選択してください。**新しいまたは既存のオーディエンスを選択**ドロップダウンで、新しいまたは既存のオーディエンスの名前を入力します。 
+希望するGoogle広告アカウントを選択してください。\[**新規または既存のオーディエンスを選択**] ドロップダウンで、新しいオーディエンスまたは既存のオーディエンスの名前を入力します。 
 
 {% tabs %}
-{% tab 新しいオーディエンスを作成する %}
-**新しいオーディエンスを作成**<br>
+{% tab 新規オーディエンスの作成 %}
+**新規オーディエンスの作成**<br>
 新しいカスタムオーディエンスの名前を入力し、**ユーザーをオーディエンスに追加**を選択し、Googleと同期したいフィールドを選択します。Googleと同期するために一致させるフィールドを選択できます:
 
 - メール 
@@ -131,79 +131,79 @@ Google 広告アカウントの接続に成功すると、Google 広告パート
 - モバイル広告ID
   - Braze SDKを通じて[IDFA]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/other_sdk_customizations/#optional-idfa-collection)または[GAID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection#google-advertising-id-android-only)の収集にオプトインする必要があります。
 
-新しいカスタムオーディエンスの名前を入力し、**ユーザーをオーディエンスに追加**を選択し、オーディエンスに送信するファーストパーティのユーザーフィールドデータを選択します。どちらかを選ぶことができます:
+新しいカスタムオーディエンスの名前を入力し、\[**ユーザーをオーディエンスに追加**] を選択し、オーディエンスに送信するファーストパーティユーザーフィールドデータを選択します。次のいずれかを選択できます。
 
-- **顧客 Contact Info**:Brazeに存在する場合、ユーザーのメールまたは電話番号、またはその両方が含まれます
-- **モバイル広告ID**:iOS IDFA または Android GAID のいずれかを選択してください
+- **お客様の連絡先情報**:Brazeに存在する場合、ユーザーのメールまたは電話番号、またはその両方が含まれます
+- **モバイル広告主 ID**:iOS IDFA または Android GAID のいずれかを選択してください
 
 次に、ステップエディタの下部にある**オーディエンスを作成**ボタンをクリックしてオーディエンスを保存します。
 
-![カスタムオーディエンスキャンバスコンポーネントの拡大ビュー。ここで、希望する広告アカウントが選択され、新しいオーディエンスが作成され、「顧客連絡先情報」チェックボックスが選択されます。]({% image_buster /assets/img/audience_sync/g_sync.png %})
+![カスタムオーディエンスキャンバスコンポーネントの展開ビュー。目的の広告アカウントが選択され、新しいオーディエンスが作成され、「お客様の連絡先情報」チェックボックスが選択されている。]({% image_buster /assets/img/audience_sync/g_sync.png %})
 
-ユーザーは、オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合に、ステップエディターの上部で通知されます。ユーザーは、オーディエンスが下書きモードで作成されたため、キャンバスの旅の後でユーザーの削除のためにこのオーディエンスを参照できます。 
+ユーザーは、オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合に、ステップエディターの上部で通知されます。ユーザーは、後でキャンバスジャーニーでユーザーを削除するためにこのオーディエンスを参照することができます。これは、オーディエンスが下書きで作成されたためです。 
 
-![キャンバスコンポーネントで新しいオーディエンスが作成された後に表示されるアラートです。]({% image_buster /assets/img/audience_sync/g_sync3.png %})
+![キャンバスコンポーネントで新しいオーディエンスが作成された後に表示されるアラート。]({% image_buster /assets/img/audience_sync/g_sync3.png %})
 
-新しいオーディエンスでキャンバスを起動すると、Brazeはキャンバスの起動時に新しいカスタムオーディエンスを作成し、その後、ユーザーがGoogle オーディエンスコンポーネントに入るとほぼリアルタイムで同期します。 
+新しいオーディエンスを使用してキャンバスを起動すると、Braze はキャンバスの起動時にカスタムオーディエンスを作成し、その後、オーディエンスが Google オーディエンスの同期ステップに入るたびに、ほぼリアルタイムでユーザーが同期されます。 
 
 {% alert important %}
-Google の顧客マッチ要件によると、顧客リストに顧客の連絡先情報とモバイル広告主 ID を同時に含めることはできません。Google 顧客 Match は次にこの情報を使用して、Google 検索、Google ディスプレイ、YouTube、および Gmail 内でターゲットにできる人を判断します。Google顧客マッチの要件の詳細については、彼らの[ドキュメント](https://support.google.com/google-ads/answer/7474166?hl=en&ref_topic=6296507)を確認してください。
+Google のカスタマーマッチの要件のため、顧客の連絡先情報とモバイル広告主 ID を同じ顧客リストに含めることはできません。Google カスタマーマッチはその後この情報を使用して、Google 検索、Google ディスプレイ、YouTube、Gmail でターゲットにできる人物を決定します。Google顧客マッチの要件の詳細については、彼らの[ドキュメント](https://support.google.com/google-ads/answer/7474166?hl=en&ref_topic=6296507)を確認してください。
 {% endalert %}
 {% endtab %}
 {% tab 既存のオーディエンスと同期する %}
-**既存のオーディエンスと同期する**<br>
-Brazeは、これらのオーディエンスが最新であることを確認するために、既存のGoogle顧客リストからユーザーを追加または削除する機能も提供します。既存のオーディエンスと同期するには、既存のカスタムオーディエンスを選択して同期し、**オーディエンスに追加する**か**オーディエンスから削除する**かを選択します。Brazeは、ユーザーがGoogle オーディエンス ステップに入ると、ほぼリアルタイムでユーザーを追加または削除します。 
+**既存のオーディエンスとの同期**<br>
+Braze では、これらのオーディエンスが最新の状態であるようにするために、既存の Google 顧客リストからユーザーを追加または削除することもできます。既存のオーディエンスと同期するには、同期する既存のカスタムオーディエンスを選択し、\[**ユーザーをオーディエンスに追加**] または \[**オーディエンスからユーザーを削除**] のいずれかを選択します。Brazeは、ユーザーがGoogle オーディエンス ステップに入ると、ほぼリアルタイムでユーザーを追加または削除します。 
 
-Google オーディエンス ステップを構成したら、**完了**を選択します。あなたのGoogleオーディエンスステップには、新しいオーディエンスに関する詳細が含まれます。
+Google オーディエンス ステップを構成したら、**完了**を選択します。Google オーディエンスステップには、新しいオーディエンスに関する詳細情報が含まれます。
 
-![カスタムオーディエンスキャンバスコンポーネントの拡大ビュー。ここで、希望する広告アカウントと既存のオーディエンスが選択され、「オーディエンスにユーザーを追加」ラジオボタンが選択されます。]({% image_buster /assets/img/audience_sync/g_sync2.png %})
+![カスタムオーディエンスキャンバスコンポーネントの展開ビュー。目的の広告アカウントと既存のオーディエンス、および「ユーザーをオーディエンスに追加」ラジオボタンが選択されている。]({% image_buster /assets/img/audience_sync/g_sync2.png %})
 
 {% endtab %}
 {% endtabs %}
 
 ### ステップ4:キャンバスを起動
 
-キャンバス内でユーザーの旅の残りを完了し、次に進みましょう！新しいオーディエンスを作成することを選択した場合、BrazeはGoogle内にオーディエンスを作成し、ユーザーがキャンバスのこのステップに到達すると追加します。既存のオーディエンスにユーザーを追加または削除することを選択した場合、Brazeはユーザーがユーザージャーニーのこのステップに到達したときにユーザーを追加または削除します。
+キャンバス内でユーザージャーニーの残りの部分を完了し、キャンバスを起動します。新しいオーディエンスを作成することを選択した場合、Braze により Google 内にオーディエンスが作成され、キャンバスのこのステップに到達したユーザーが追加されます。既存のオーディエンスにユーザーを追加または削除することを選択した場合、Brazeはユーザーがユーザージャーニーのこのステップに到達したときにユーザーを追加または削除します。
 
-ユーザーは次のコンポーネントに進みます。キャンバスがあれば、キャンバスの最後のステップでユーザーの旅が終了します。 
+その後、キャンバスに次のコンポーネントがある場合は、ユーザーはそのコンポーネントに進みます。ユーザージャーニーの最後のステップである場合は、キャンバスを終了します。 
 
 ## ユーザーの同期とレート制限の考慮事項
 
-ユーザーがオーディエンス同期コンポーネントに到達すると、BrazeはGoogle 広告APIのレート制限を遵守しながら、これらのユーザーをほぼリアルタイムで同期します。これが実際に意味するところは、Brazeが5秒ごとにできるだけ多くのユーザーをバッチ処理し、これらのユーザーをGoogleに送信しようとするということです。 
+ユーザーがオーディエンス同期コンポーネントに到達すると、Braze は Google 広告 API のレート制限を尊重しながら、これらのユーザーをほぼリアルタイムで同期します。これが実際に意味するところは、Brazeが5秒ごとにできるだけ多くのユーザーをバッチ処理し、これらのユーザーをGoogleに送信しようとするということです。 
 
-顧客がGoogle 広告APIのレート制限に近づくと、Googleは再試行の推奨事項に関するフィードバックをBrazeに提供します。Brazeの顧客がレート制限に達した場合、Brazeのキャンバスは同期を最大約13時間再試行します。同期が不可能な場合、これらのユーザーは「ユーザーエラー」メトリックにリストされます。
+顧客が Google 広告 API のレート制限に近づいたら、Google は再試行の推奨事項に関して Braze にフィードバックを提供します。Brazeの顧客がレート制限に達した場合、Brazeのキャンバスは同期を最大約13時間再試行します。同期が不可能な場合、これらのユーザーは「ユーザーエラー」メトリックにリストされます。
 
 ## 分析を理解する 
 
 次の表には、オーディエンス同期ステップからの分析をよりよく理解するための指標と説明が含まれています。
 
-| メートル法 | 説明 |
+| 指標 | 説明 |
 | ------ | ----------- |
-| *入力済み* | このステップに入ったユーザー数をGoogleに同期します。 |
-| *次のステップに進みました* | 次のコンポーネントがある場合、何人のユーザーが次のコンポーネントに進みましたか。すべてのユーザーが自動的に進行します。これがキャンバスBranchの最後のステップである場合、このメトリックは0になります。 |
-| *ユーザーが同期されました* | Google に正常に同期されたユーザーの数。 |
-| *ユーザー Not Synced* | 欠落しているフィールドが一致しないか、同意属性が`false`に設定されているために同期されていないユーザーの数。 |
-| *ユーザーがエラーを起こしました* | エラーのためにGoogleと同期されなかったユーザーの数、約13時間の再試行後。特定のエラー、例えばGoogle 広告APIサービスの中断の場合、キャンバスは同期を最大約13時間再試行します。その時点で同期がまだ不可能な場合、*ユーザー未同期*が入力されます。 |
-| *保留中のユーザー* | 現在、BrazeによってGoogleに同期されているユーザーの数。 |
-| *キャンバスを終了しました* | キャンバスを終了したユーザーの数。これは、キャンバスの最後のステップがGoogleステップである場合に発生します。 |
+| *入力* | Google と同期するためにこのステップに入ったユーザーの数。 |
+| *次のステップに進む* | 次のコンポーネントがある場合、次のコンポーネントに進んだユーザーの数。すべてのユーザーが自動的に進みます。これがキャンバスブランチの最後のステップである場合、この指標は0になります。 |
+| *ユーザーの同期* | Google に正常に同期されたユーザーの数。 |
+| *同期されていないユーザー* | 欠落しているフィールドが一致しないか、同意属性が`false`に設定されているために同期されていないユーザーの数。 |
+| *エラーが発生したユーザー数* | エラーのためにGoogleと同期されなかったユーザーの数、約13時間の再試行後。特定のエラー (Google 広告 API サービスの中断など) が発生すると、キャンバスは最大13時間にわたって同期を再試行します。その時点で同期がまだ不可能な場合、*ユーザー未同期*が入力されます。 |
+| *保留中のユーザー* | Braze が Google と同期するために現在処理されているユーザーの数。 |
+| *終了済みのキャンバス* | キャンバスを終了したユーザーの人数。これは、キャンバスの最後のステップがGoogleステップである場合に発生します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## トラブルシューティング
 
 {% details Google オーディエンス ステップ設定で複数のフィールドを選択して一致させることができないのはなぜですか？ %}
-Google 顧客マッチには、これらのオーディエンスの形式や含まれる顧客情報に関して厳格な要件があります。具体的には、モバイル広告主IDは顧客の連絡先情報（メールや電話番号など）とは別にアップロードする必要があります。詳細については、[Googleの顧客マッチドキュメント](https://support.google.com/google-ads/answer/7659867?hl=en#undefined)を参照してください。
+Google カスタマーマッチには、このようなオーディエンスの形式と含める顧客情報に関して厳しい要件があります。具体的には、モバイル広告主 ID は、顧客の連絡先情報 (メールや電話番号など) とは別にアップロードする必要があります。詳細については、[Googleの顧客マッチドキュメント](https://support.google.com/google-ads/answer/7659867?hl=en#undefined)を参照してください。
 {% enddetails %}
 
-{% details Googleでオーディエンスが同期するのにどれくらい時間がかかりますか？ %}
-Googleにオーディエンスが同期されるまでに6〜12時間かかることがあります。
+{% details オーディエンスが Google に同期されるまでにどのくらいの時間がかかりますか？ %}
+オーディエンスが Googleに同期されるまでには6～12時間かかることがあります。
 {% enddetails %}
 
-{% details オーディエンスを同期しましたが、Googleのオーディエンスサイズがゼロです。 %}
+{% details オーディエンスを同期しましたが、Google のオーディエンスサイズがゼロです。 %}
 プライバシーの目的で、ユーザーリストのサイズはリストに少なくとも**1,000人のメンバー**がいるまでゼロと表示されます。その後、サイズは最も重要な2桁に丸められます。
 {% enddetails %}
 
 {% details オーディエンスをGoogleに同期しましたが、広告が配信されていません。 %}
-オーディエンスに少なくとも**5,000**人のユーザーが含まれていることを確認して、広告が配信され始めるようにしてください。
+広告が確実に配信開始されるようにするため、オーディエンスに少なくとも**5,000**人のユーザーが含まれていることを確認してください。
 {% enddetails %}
 
 {% details 「モバイルアプリIDが削除されました」エラーを解決するにはどうすればよいですか？ %}
diff --git a/_lang/ja/_partners/canvas_steps/overview.md b/_lang/ja/_partners/canvas_steps/overview.md
index 0c86b4ab199..cbb0e88cafc 100644
--- a/_lang/ja/_partners/canvas_steps/overview.md
+++ b/_lang/ja/_partners/canvas_steps/overview.md
@@ -1,87 +1,87 @@
 ---
 nav_title: 概要
 article_title: 概要
-description: "この参考記事では、Braze Audience SyncをFacebookに同期させ、行動トリガーやセグメンテーションなどに基づいて広告を配信する方法を紹介する。"
+description: "このリファレンス記事では、Braze Audience Sync to Facebook を使用して、行動トリガーやセグメンテーションなどに基づいて広告を配信する方法について説明します。"
 page_order: 0
 Tool:
   - Canvas
 
 ---
 
-# 観客同期の概要
+# オーディエンスの同期の概要
 
-> Brazeのオーディエンスシンク機能は、多くのトップソーシャルおよび広告テクノロジーにキャンペーンのリーチを拡大するのに役立つ。[Braze Canvasを通じて]({{site.baseurl}}/user_guide/engagement_tools/canvas)、ブランドはファーストパーティーのユーザーデータを広告エコシステムに動的かつ安全に同期させ、マーケティングと運用の効率化を推進できる。
+> Braze のオーディエンスの同期機能は、多くのトップソーシャルテクノロジーおよび広告テクノロジーにキャンペーンのリーチを拡大するのに役立ちます。[Braze Canvasを通じて]({{site.baseurl}}/user_guide/engagement_tools/canvas)、ブランドはファーストパーティーのユーザーデータを広告エコシステムに動的かつ安全に同期させ、マーケティングと運用の効率化を推進できる。
 
 ## ユースケース
 
-- オウンド・チャネルとペイド・チャネルを通じて価値の高いユーザーをターゲットにし、購買やエンゲージメントの増加を促進する。
-- 新規ユーザーの獲得コストとコンバージョンを最適化するために、価値の高いユーザーのそっくりさんオーディエンスを作成する。
-- 他のマーケティング・チャネルで反応が低いユーザーを広告でリターゲティングする。
-- 抑制オーディエンスを作成することで、ユーザーがすでにブランドの忠実な消費者である場合に広告を受け取らないようにする。
+- 複数の所有チャネルと有料チャネルを通じて価値の高いユーザーをターゲットに設定して、購入やエンゲージメントを促進する。
+- 新規ユーザーの獲得コストとコンバージョンを最適化するために、価値の高いユーザーの類似オーディエンスを作成する。
+- 他のマーケティングチャネルで反応が低いユーザーを広告でリターゲティングする。
+- すでに自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑制オーディエンスを作成する
 
-## フィーチャー・アベイラビリティ
+## 機能の利用について
 
-Brazeの全顧客は、GoogleとFacebookへのオーディエンス・シンクを直ちに利用できるようになる。TikTok、Pinterest、Snapchat、Criteoなど、Audience Syncの追加配信先をアンロックするには、Audience Sync Proを購入する必要がある。詳細については、Brazeのアカウントマネージャーに問い合わせを。
+Braze をご利用のすべてのお客様は、Audience Sync to Google と Audience Sync to Facebookをすぐに利用できます。TikTok、Pinterest、Snapchat、Criteo など、オーディエンスの同期のその他の宛先をロック解除するには、Audience Sync Pro を購入する必要があります。詳細については、Brazeのアカウントマネージャーに問い合わせを。
 
 ## その仕組み
 
-GoogleまたはFacebookへのAudience Syncを使用するには、**Technology Partners**ページでパートナーを検索して広告アカウントを接続する。
+Audience Sync to Google または Audience Sync to Facebook を使用するには、\[**テクノロジー パートナー**] ページでパートナーを探して、広告アカウントを接続します。
 
 ![][3]{: style="max-width:35%;"} ![][4]{: style="max-width:35%;"}
 
-広告アカウントを接続した後、オーディエンス同期ステップでキャンバスを作成できる。
+広告アカウントを接続した後、オーディエンスの同期ステップを使用してキャンバスを作成できます。
 
 ![][22]{: style="max-width:75%;"}
 
-次に、オーディエンスを同期するパートナーを選択する。
+次に、オーディエンスを同期するパートナーを選択します。
 
 ![][19]{: style="max-width:85%;"}
 
-各パートナーについて、Audience Syncステップの一部として以下を設定する必要がある： 
+パートナーごとに、オーディエンスの同期ステップで次の内容を設定する必要があります。 
 - 広告アカウント
 - オーディエンス 
 - ユーザーを追加または削除するアクション 
 - マッチするフィールド 
 
-Brazeは、ユーザーがキャンバス内のオーディエンス同期ステップに入るとすぐに同期することを覚えておいてほしい。 
+キャンバス内でユーザーがオーディエンスの同期ステップに入るとすぐに、Braze によりユーザーが同期されることに注意してください。 
 
-Audience Syncの送信先ごとに、送信可能なフィールドに対するパートナーの要件が異なる場合がある。詳細については、特定のパートナーの文書を参照のこと。 
+オーディエンスの同期の宛先ごとに、パートナーの送信可能なフィールドに関する要件が異なる場合があります。詳細については、特定のパートナーのドキュメントを参照してください。 
 
-### オーディエンス・シンク・プロ
+### Audience Sync Pro
 
-TikTok、Pinterest、Snapchat、またはCriteoを含むAudience Sync Proパートナーを使用するには、**テクノロジーパートナーページの** **Audience Sync Pro**セクションで、Audience Sync Proの購入割り当てに基づいてパートナーを選択できるようになる。
+TikTok、Pinterest、Snapchat、Criteo などのAudience Sync Pro パートナーを使用するには、\[**テクノロジーパートナー**] ページの \[**Audience Sync Pro**] セクションで Audience Sync Pro の購入割り当てに基づいてパートナーを選択できます。
 
 ![][5]{: style="max-width:75%;"}
 
-まず、Select Partnersを選択して、使用するパートナーを選択する。Audience Sync Proを購入するごとに、ダッシュボード内の各ワークスペースで利用できるAudience Sync Proの目的地が3つ割り当てられる。
+最初に \[パートナーを選択] を選択して、使用するパートナーを選択します。Audience Sync Pro を購入すると、1回の購入につ3つの Audience Sync Pro 宛先が割り当てられます。これは、ダッシュボードの各ワークスペース内で使用可能になります。
 
 ![][6]{: style="max-width:65%;"}
 
-Audience Sync Proの配信先を選択したら、パートナータイルをクリックして選択したパートナーの広告アカウントに接続する。
+Audience Sync Pro 宛先を選択したら、パートナータイルをクリックして、選択したパートナーの広告アカウントを接続します。
 
 ![][7]{: style="max-width:70%;"}
 
 ![][9]{: style="max-width:70%;"}
 
-最後に、このAudience Sync Proの目的地を使って、Canvasにオーディエンス・シンクのステップを作成する。
+最後に、この Audience Sync Pro 宛先を使用して、キャンバスでオーディエンスの同期ステップを作成します。
 
-## データ・プライバシーへの配慮
+## データプライバシーに関する考慮事項
 
 {% alert important %}
-本書は、法的助言を提供することを意図したものではなく、また法的助言を提供するものとして依拠することもできない。オーディエンス・シンクの使用は、特定の法的要件に従う。あなたが適用されるすべての法律を遵守して使用していることを確認するために、あなたの法律顧問の助言を求めるべきである。
+本書は、法的助言を提供することを意図したものではなく、また法的助言を提供するものとして依拠することもできない。オーディエンスの同期の使用には、特定の法的要件が適用されます。あなたが適用されるすべての法律を遵守して使用していることを確認するために、あなたの法律顧問の助言を求めるべきである。
 {% endalert %}
 
-広告トラッキングのオーディエンスを構築する際、ユーザーの嗜好に基づき、また[CCPAに](https://oag.ca.gov/privacy/ccpa)基づく「販売または共有しない」権利などのプライバシー法を遵守するために、特定のユーザーを含めたり除外したりしたい場合がある。マーケティング担当者は、キャンバスのエントリー基準の中で、ユーザーの適格性に関する関連フィルタを実装する必要がある。以下にいくつかの選択肢を挙げる。
+広告トラッキングのオーディエンスを構築する際、ユーザーの嗜好に基づき、また[CCPAに](https://oag.ca.gov/privacy/ccpa)基づく「販売または共有しない」権利などのプライバシー法を遵守するために、特定のユーザーを含めたり除外したりしたい場合がある。マーケターは、キャンバスのエントリ基準の範囲内で、ユーザーの適格性に関する適切なフィルターを実装する必要があります。以下にいくつかの選択肢を挙げる。
 
-[Braze SDKを通じてiOS IDFAを]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/other_sdk_customizations/#optional-idfa-collection)収集した場合、"Ads Tracking Enabled "フィルターを使用できるようになる。ユーザーがオプトインしたAudience Sync送信先にのみユーザーを送信する場合は、`true` 。
+[Braze SDK で iOS IDFA]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/other_sdk_customizations/#optional-idfa-collection) を収集した場合、\[広告の追跡が有効] フィルターを使用できます。ユーザーがオプトインしたオーディエンス同期の宛先にのみユーザーを送信するには、値を `true` に選択します。
 
 ![][2]
 
-`opt-ins` 、`opt-outs` 、`Do Not Sell Or Share` 、またはその他の関連するカスタム属性を収集する場合は、フィルタとしてキャンバスの入力条件にこれらを含める必要がある：
+`opt-ins`、`opt-outs`、`Do Not Sell Or Share`、または他の関連するカスタム属性を収集する場合は、キャンバスのエントリ基準にこれらをフィルターとして含める必要があります。
 
 ![エントリーのオーディエンスが "opted_in_marketing "のキャンバスは、"true "に等しい。][1]
 
-Brazeプラットフォーム内でこれらのデータ保護法を遵守する方法の詳細については、[データ保護テクニカルアシスタンスを]({{site.baseurl}}/dp-technical-assistance/)参照のこと。
+Braze プラットフォーム内でこれらのデータ保護法を遵守する方法の詳細については、[データ保護テクニカルアシスタンス]({{site.baseurl}}/dp-technical-assistance/)を参照してください。
 
 [1]: {% image_buster /assets/img/audience_sync/audience_sync.png %}
 [2]: {% image_buster /assets/img/audience_sync/audience_sync2.png %}
diff --git a/_lang/ja/_partners/canvas_steps/pinterest_audience_sync.md b/_lang/ja/_partners/canvas_steps/pinterest_audience_sync.md
index 7fecb5de00a..82bf2e4a5d5 100644
--- a/_lang/ja/_partners/canvas_steps/pinterest_audience_sync.md
+++ b/_lang/ja/_partners/canvas_steps/pinterest_audience_sync.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Pinterest
-article_title: Canvas Audience がPinterest に同期する
-description: "このレファレンス記事では、Braze オーディエンスシンクをPinterestに使用し、行動トリガーs、セグメンテーションなどに基づいてアドバタイズメントを配信する方法について説明します。"
+article_title: キャンバスのオーディエンスと Pinterest の同期
+description: "このリファレンス記事では、Braze Audience Sync to Pinterest を使用して、行動トリガーやセグメンテーションなどに基づいて広告を配信する方法について説明します。"
 page_order: 3
 alias: "/audience_sync_pinterest/"
 
@@ -10,47 +10,47 @@ Tool:
 
 ---
 
-# 視聴者がPinterest に同期する
+# Audience Sync to Pinterest
 
-PinterestへのBrazeオーディエンス同期を使用すると、ブランドは、独自のBrazeインテグレーションからPinterestオーディエンスへのユーザーデータを追加して、行動トリガーs、セグメンテーションなどに基づいた広告を配信することができます。通常は、Pinterest オーディエンスで広告をトリガーするために使用する条件(プッシュ、メール、SMS、Webhookなど)を、Brazeキャンバスでユーザーデータに基づいて使用できます。これにより、Pinterest オーディエンスでそのユーザーに広告をトリガーできます。
+Braze Audience Sync to Pinterest を使用すると、ブランドは独自の Braze 統合からのユーザーデータを Pinterest オーディエンスに追加して、行動トリガーやセグメンテーションなどに基づいて広告を配信できます。ユーザーデータに基づいて Braze キャンバスでメッセージ (プッシュ、メール、SMS、Webhook など) をトリガーするために通常使用する基準を、Pinterest オーディエンス内の該当ユーザーに対して広告をトリガーするときに使用できるようになりました。
 
 **オーディエンス同期の一般的なユースケースは次のとおりです。**
 
-- 多重チャネルによる高価値ユーザーをターゲットに、仕入・エンゲージメントを牽引
+- 複数のチャネルを通じて価値の高いユーザーをターゲットにして、購入やエンゲージメントを促進する
 - 他のマーケティング チャネルにあまりレスポンシブでないユーザーのリターゲット
-- 自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑圧オーディエンスsの作成
-- 新たなユーザーをより効率的に獲得するためのアクタライクなオーディエンスの創出
+- すでに自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑制オーディエンスを作成する
+- 新規ユーザーをより効率的に獲得するための類似行動オーディエンスを作成する
 
-この機能により、ブランドはPinterestと共有する特定のファーストパーティデータをコントロールできます。Brazeでは、ファーストパーティデータを共有できる統合と共有できない統合を最大限に検討します。詳細については、[プライバシーポリシー](https://www.braze.com/privacy)を参照してください。
+この機能により、ブランドはPinterestと共有する特定のファーストパーティデータをコントロールできます。Braze では、ファーストパーティデータを共有できる統合と共有できない統合を最大限に考慮しています。詳細については、[プライバシーポリシー](https://www.braze.com/privacy)を参照してください。
 
 {% alert important %}
-**Audience Sync Pro免責条項**<br>
-Braze オーディエンスシンクとPinterest はAudience Sync Proなインテグレーションです。この統合の詳細については、Braze アカウントマネージャーにお問い合わせください。
+**Audience Sync Pro 免責条項**<br>
+Braze Audience Sync to Pinterest は Audience Sync Pro 統合です。この統合の詳細については、Braze アカウントマネージャーにお問い合わせください。
 {% endalert %}
 
 ## 前提条件 
-キャンバスでPinterest Audience Step を設定するには、以下の項目が作成され、完了し、受け入れられていることを確認する必要があります。
+キャンバスで Pinterest オーディエンスステップを設定する前に、以下の項目が作成、完了、または受け入れられていることを確認する必要があります。
 
-| 要件 | Origin | 説明 |
+| 要件 | 提供元 | 説明 |
 | --- | --- | --- |
 | Pinterestビジネスハブ | [Pinterest](https://www.pinterest.com/business/hub/) | ブランドのPinterestアセット(広告アカウント、ページ、アプリなど)を管理するための集中管理ツールです。 |
-| Pinterestの広告アカウント | [Pinterest](https://ads.pinterest.com/) | ブランドのPinterest Business Hub に関連付けられたアクティブなPinterest アドアカウント。<br><br>Pinterest Business Hub 管理者が、Braze で使用するPinterest アドアカウントに管理者権限を付与していることを確認します。 |
-| Pinterest用語&ポリシー | Pinterest | Pinterest Audience Syncの使用に関連するPinterestの必要な条件、ポリシー、ガイドライン、およびドキュメントを順守することに同意します。これには、Pinterest Audience Syncに組み込まれている用語、ポリシー、ガイドライン、およびドキュメントが含まれます。これには、サービス利用規約、ビジネス利用規約、プライバシーポリシー、開発者およびAPI利用規約、アドデータ利用規約、アドバタイジングガイドライン、アドバタイジングサービス契約、コミュニティガイドライン、およびブランドガイドラインが含まれます。 |
+| Pinterestの広告アカウント | [Pinterest](https://ads.pinterest.com/) | ブランドの Pinterest Business Hub に関連付けられているアクティブな Pinterest 広告アカウント。<br><br>Pinterest Business Hub 管理者が、Braze で使用する Pinterest 広告アカウントの管理者権限をユーザーに付与していることを確認します。 |
+| Pinterest 利用規約 | Pinterest | Pinterest Audience Sync の利用に関連するPinterest のすべての必須条件、ポリシー、ガイドライン、ドキュメントを遵守することに同意するものとします。これには、引用により組み込まれるすべての条件、ポリシー、ガイドライン、および文書 (利用規約、ビジネス利用規約、プライバシーポリシー、開発者および API 利用規約、広告データ利用規約、広告ガイドライン、広告サービス契約、コミュニティガイドライン、ブランドガイドラインなどを含む) が含まれます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合 
 
 ### ステップ1:Pinterest に接続する
 
-Braze ダッシュボードで、**Partner Integrations**> **Technology Partners**に移動し、**Pinterest**を選択します。Pinterest Audience エクスポートモジュールで、**Connect Pinterest** をクリックします。
+Braze ダッシュボードで、**Partner Integrations**> **Technology Partners**に移動し、**Pinterest**を選択します。Pinterest Audience Export (Pinterest オーディエンスエクスポート) モジュールで、\[**Pinterest に接続**] をクリックします。
 
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation) を使用している場合、**Technology Partners** は**Integrations** にあります。
 {% endalert %}
 
-![Braze のPinterest テクノロジページ。オーバービューモジュールとPinterest Audience Sync モジュールとConnected Pinterest ボタンが含まれています。][1]{: style="max-width:80%;"}
+![Braze の Pinterest テクノロジーページ。「概要」モジュール、「Pinterest Audience Sync」モジュール、「Pinterest に接続」ボタンが表示されている。][1]{: style="max-width:80%;"}
 
-その後、Pinterest OAuth ページにリダイレクトされ、アドアカウントマネジメントとオーディエンスマネジメントのBrazeを許可します。
+その後、広告アカウント管理とオーディエンス管理を Braze に許可する \[Pinterest OAuth] ページにリダイレクトされます。
 
 確認を選択すると、Braze にリダイレクトされ、同期したいPinterest 広告アカウントが選択されます。 
 
@@ -58,21 +58,21 @@ Braze ダッシュボードで、**Partner Integrations**> **Technology Partners
 
 接続に成功すると、パートナーページに戻ります。このページでは、接続されているアカウントを表示したり、既存のアカウントを切断したりできます。
 
-![更新 d 版のPinterest テクノロジーパートナー s ページで、アドアカウントが正常に接続されたことを示します。][3]{: style="max-width:80%;"}
+![広告アカウントが接続されたことを示す更新後の Pinterest テクノロジーパートナーページ。][3]{: style="max-width:80%;"}
 
-Pinterest のコネクションは、アプリはBraze ワークスペースの位置にあります。Pinterest 管理者がPinterest Business Hub からユーザを削除したり、接続されているPinterest アカウントにアクセスしたりすると、Braze は不正なトークンを検出します。そのため、Pinterest Audience コンポーネントを使用しているアクティブなキャンバスにはエラー s が表示され、Braze はユーザー s を同期できません。
+Pinterest 接続は Braze ワークスペースレベルで適用されます。Pinterest 管理者が Pinterest Business Hub からユーザーを削除したり、接続されている Pinterest アカウントにアクセスしたりすると、Braze は無効なトークンを検出します。その結果、Pinterest オーディエンスコンポーネントを使用しているアクティブなキャンバスにはエラーが表示され、Braze はユーザーを同期できません。
 
 ### ステップ2:Pinterest を使用したオーディエンス同期ステップの追加
 
-キャンバスにコンポーネントを追加し、**Audience Sync** を選択します。
+キャンバスにコンポーネントを追加し、\[**オーディエンスの同期**] を選択します。
 
 ![][18]{: style="max-width:35%;"} ![][20]{: style="max-width:28%;"}
 
 ### ステップ3:同期設定
 
-コンポーネントエディターを開封するには、**Custom Audience**ボタンを押します。
+\[**カスタムオーディエンス**] ボタンをクリックしてコンポーネントエディターを開きます。
 
-希望するAudience Sync パートナーとして**Pinterest** を選択します。
+**Pinterest** を目的のオーディエンス同期パートナーとして選択します。
 
 ![][19]{: style="max-width:80%;"}
 
@@ -82,74 +82,74 @@ Pinterest のコネクションは、アプリはBraze ワークスペースの
 {% tab 新規オーディエンスの作成 %}
 
 **新規オーディエンスの作成**<br>
-新しいオーディエンスの名前を入力し、**オーディエンスにユーザを追加**を選択し、Pinterest と同期するフィールドを選択します。次に、ステップエディタの下部にある**オーディエンス**を作成ボタンをクリックして、オーディエンスを保存します。
+新しいオーディエンスの名前を入力し、\[**ユーザーをオーディエンスに追加**] を選択し、Pinterest と同期するフィールドを選択します。次に、ステップエディタの下部にある**オーディエンス**を作成ボタンをクリックして、オーディエンスを保存します。
 
-![カスタムオーディエンスキャンバスステップの展開表示。ここでは、目的のアドアカウントが選択され、新しいオーディエンスが作成されます。]({% image_buster /assets/img/audience_sync/pinterest_sync.png %})
+![カスタムオーディエンスキャンバスステップの展開ビュー。ここでは目的の広告アカウントが選択され、新しいオーディエンスが作成される。]({% image_buster /assets/img/audience_sync/pinterest_sync.png %})
 
-オーディエンスが正常に作成された場合、またはこの処理中にエラーが発生した場合は、ステップエディタの上部にユーザが通知されます。ユーザー s は、このオーディエンスを参照して、後でキャンバスジャーニーでユーザーを削除することもできます。これは、オーディエンスが下書きで作成されたためです。
+オーディエンスが正常に作成された場合、またはこの処理中にエラーが発生した場合は、ステップエディタの上部にユーザが通知されます。ユーザーは、後でキャンバスジャーニーでユーザーを削除するためにこのオーディエンスを参照することもできます。これは、オーディエンスが下書きで作成されたためです。
 
-![新しいオーディエンスがキャンバスコンポーネントに作成された後にアプリが認識されるという警告。]({% image_buster /assets/img/audience_sync/pinterest_sync3.png %})
+![キャンバスコンポーネントで新しいオーディエンスが作成された後に表示されるアラート。]({% image_buster /assets/img/audience_sync/pinterest_sync3.png %})
 
-新しいオーディエンスでキャンバスを起動すると、Braze はユーザーをほぼリアルタイムで同期し、オーディエンス同期ステップに入ります。
+新しいオーディエンスを使用してキャンバスを起動すると、ユーザーがオーディエンス同期ステップに入る時点で、Braze はユーザーをほぼリアルタイムで同期します。
 {% endtab %}
 {% tab 既存のオーディエンスとの同期 %}
 **既存のオーディエンスとの同期**<br>
-Braze では、既存のPinterest オーディエンスs にユーザーを追加して、これらのオーディエンスs が最新であることを確認することもできます。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンスの名前を入力し、オーディエンスに追加します。Braze は、オーディエンス・シンク・ステップに入ると、ほぼリアルタイムでユーザーs を追加します。
+また、Braze は、これらのオーディエンスが最新であることを確認するために、既存の Pinterest オーディエンスにユーザーを追加する機能も提供します。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンスの名前を入力し、オーディエンスに追加します。ユーザーがオーディエンス同期ステップに入る時点で、Braze はほぼリアルタイムでユーザーを追加します。
 
-![カスタムオーディエンスキャンバスステップの展開表示。ここでは、希望する広告アカウントと既設オーディエンスが選択されます。]({% image_buster /assets/img/audience_sync/pinterest_sync2.png %})
+![カスタムオーディエンスキャンバスステップの展開ビュー。ここでは、目的の広告アカウントと既存のオーディエンスが選択されている。]({% image_buster /assets/img/audience_sync/pinterest_sync2.png %})
 
 {% endtab %}
 {% endtabs %}
 
 ### ステップ4:キャンバスの起動
 
-Audience Sync to Pinterest を設定したら、キャンバスを起動します。新しいオーディエンスが作成され、Pinterest でオーディエンスシンクステップを流れるユーザーがこのオーディエンスに渡されます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーs はユーザーの移動の次回のステップに進みます。
+Audience Sync to Pinterest を設定したら、キャンバスを起動します。新しいオーディエンスが作成され、オーディエンス同期ステップを通過するユーザーは Pinterest のこのオーディエンスに送られます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーはユーザージャーニーの次のステップに進みます。
 
-Pinterest でオーディエンスを表示するには、広告マネージャーアカウントを入力し、「広告」ドロップダウンから「オーディエンス」を選択します。オーディエンス画面から、～100に達した後のオーディエンスの大きさが確認できます。
+Pinterest でオーディエンスを表示するには、広告マネージャーアカウントを入力し、\[Ads] ドロップダウンから \[Audience] を選択します。\[Audience] ページで、各オーディエンスが100に達した後のオーディエンスのサイズを確認できます。
 
-![オーディエンスの名前、オーディエンス ID、オーディエンスの種類、オーディエンスの大きさを含む、指定されたPinterest オーディエンスの詳細。][11]
+![オーディエンスの名前、オーディエンス ID、オーディエンスの種類、オーディエンスのサイズを含む、指定された Pinterest オーディエンスのオーディエンス詳細。][11]
 
 ## ユーザの同期とレート制限に関する考慮事項
 
-ユーザーがオーディエンス同期ステップに到達すると、Brazeはこれらのユーザーをほぼリアルタイムで同期し、PinterestのマーケティングAPIレート制限を尊重します。実際には、Braze は5 秒ごとにユーザーをバッチ処理してから、これらのユーザーをPinterest に送信します。
+ユーザーがオーディエンス同期ステップに到達すると、Brazeはこれらのユーザーをほぼリアルタイムで同期し、PinterestのマーケティングAPIレート制限を尊重します。実際には Braze は、これらのユーザーを Pinterest に送信する前に、5秒ごとにできるだけ多くのユーザーをバッチ処理しようとします。
 
-PinterestのセグメントAPI レート制限では、1ユーザーあたり1秒あたり7つのクエリーと、1リクエストあたり1900ユーザーのクエリーを使用できません。Braze 顧客がこのレート制限に達した場合、キャンバスをBrazeすると最大13 時間までシンクが再試行されます。同期できない場合、これらのユーザーは「エラーメトリクス」のユーザーに表示されます。
+Pinterest の Segment API レート制限では、1秒あたり7件のクエリと、リクエストあたり1,900のユーザーを超えないように設定されています。Braze のお客様がこのレート制限に達した場合、Braze キャンバスは最大13時間にわたって同期を再試行します。同期できない場合、これらのユーザーは \[エラーが発生したユーザー数] 指標の下にリストされます。
 
 ## 分析について
 
-次のテーブルには、オーディエンスシンクコンポーネントからの分析をよりよく理解するためのメトリクスと説明が含まれています。
+次の表に、オーディエンス同期コンポーネントからの分析をよりよく理解するのに役立つ指標と説明を示します。
 
 | メトリック | 説明 |
 | --- | --- |
-| 入力 | このコンポーネントをPinterest に同期するために入力したユーザーの人数。 |
-| 次のステップに進む | 次のコンポーネントがある場合、次のコンポーネントに進んだユーザーの数は?すべてのユーザーs は、これがキャンバスブランチの最後のステップである場合、自動的に進みます。 |
+| 入力 | Pinterest と同期するためにこのコンポーネントに入ったユーザーの数。 |
+| 次のステップに進む | 次のコンポーネントがある場合、次のコンポーネントに進んだユーザーの数は?これがキャンバスブランチの最後のステップである場合、すべてのユーザーは自動的に進みます。 |
 | ユーザーの同期 | Pinterest に正常に同期されたユーザーの人数。 |
 | 同期されていないユーザー | 照合するフィールドs がないために同期されていないユーザーの個数。 |
 | 保留中のユーザー | Braze がPinterest に同期するために現在処理されているユーザーの個数。 |
-| ユーザーのエラー | 約13 時間の再試行後にAPI エラーのためにPinterest に同期されなかったユーザーの数。エラーs の潜在的な原因に、不正なPinterest トークンが含まれているか、Pinterest でオーディエンスが削除されている可能性があります。 |
-| 廃止されたキャンバス | キャンバスを終了したユーザーの人数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生します。 |
+| エラーが発生したユーザー数 | 約13 時間の再試行後にAPI エラーのためにPinterest に同期されなかったユーザーの数。エラーの原因としては、Pinterest トークンが無効である場合や、Pinterest でオーディエンスが削除された場合などが考えられます。 |
+| 終了済みのキャンバス | キャンバスを終了したユーザーの人数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert important %}
-バルクフラッシュおよび13 時間の再試行のために、同期されたユーザー s およびエラーのメトリクスのレポートが遅延することを覚えておいてください。
+一括フラッシャーと13時間の再試行のために、同期されたユーザーとエラーが発生したユーザーの指標のレポートに遅延が発生することに注意してください。
 {% endalert %}   
 
 ## トラブルシューティング
 {% details 不正なトークン エラーを受信した場合、次にどうすればよいですか? %}
-Pinterest パートナーページでPinterest アカウントを切断して再接続するだけです。Pinterest Business Hub 管理者が、同期する広告アカウントに対するアプリの適切な権限を持っていることを確認します。
+Pinterest パートナーページでPinterest アカウントを切断して再接続するだけです。同期する広告アカウントに対する適切なアクセス許可があることを Pinterest Business Hub 管理者に確認します。
 {% enddetails %}
 
 {% details キャンバスを起動できないのはなぜですか? %}
-Pinterest アカウントがPinterest パートナーページのBraze に正常に接続されていることを確認します。
+Pinterest パートナーページで Pinterest アカウントが Braze に正常に接続されていることを確認してください。
 広告アカウントを選択し、新しいオーディエンスの名前を入力し、照合するフィールドを選択していることを確認します
 {% enddetails %}
 
-{% details ユーザー s をPinterest に渡した後、ユーザーが一致したかどうかを知るにはどうすればよいですか? %}
+{% details ユーザーを Pinterest に渡した後、ユーザーが一致したかどうかを知るにはどうすればよいですか? %}
 Pinterest は、独自のデータプライバシーポリシーにこの情報を提供しません。
 {% enddetails %}
 
-{% details 私のオーディエンスsがPinterestに入るのにどれくらいかかりますか？ %}
-オーディエンスの大きさは、PinterestのAds Managerのオーディエンスページで24～48時間で更新します。
+{% details オーディエンスが Pinterest に反映されるまでにどのくらいの時間がかかりますか? %}
+オーディエンスのサイズは、Pinterest の広告マネージャーの \[オーディエンス] ページで24～48時間以内に更新されます。
 {% enddetails %}
 
 [1]: {% image_buster /assets/img/pinterest/pinterest1.png %}
diff --git a/_lang/ja/_partners/canvas_steps/snapchat_audience_sync.md b/_lang/ja/_partners/canvas_steps/snapchat_audience_sync.md
index 28162277b7e..0cfb9d6ffb8 100644
--- a/_lang/ja/_partners/canvas_steps/snapchat_audience_sync.md
+++ b/_lang/ja/_partners/canvas_steps/snapchat_audience_sync.md
@@ -1,5 +1,5 @@
 ---
-nav_title: スナップチャット
+nav_title: Snapchat
 article_title: キャンバス オーディエンス Snapchatに同期
 description: "このリファレンス記事では、Brazeオーディエンス同期をSnapchatに使用して、行動トリガー、セグメンテーションなどに基づいて広告を配信する方法について説明します。"
 page_order: 4
@@ -12,31 +12,31 @@ Tool:
 
 # オーディエンスをSnapchatに同期
 
-Brazeオーディエンス同期をSnapchatに使用することで、ブランドはBraze統合からのユーザーデータをSnapchatの顧客リストに追加し、行動トリガー、セグメンテーションなどに基づいて広告を配信できます。Braze キャンバスでユーザーデータに基づいてメッセージ（プッシュ、メール、SMS、Webhookなど）をトリガーするために通常使用する任意の基準を使用して、Snapchatの顧客リスト内のそのユーザーに広告をトリガーできるようになりました。
+Brazeオーディエンス同期をSnapchatに使用することで、ブランドはBraze統合からのユーザーデータをSnapchatの顧客リストに追加し、行動トリガー、セグメンテーションなどに基づいて広告を配信できます。ユーザーデータに基づいて Braze キャンバスでメッセージ (プッシュ、メール、SMS、Webhook など) をトリガーするために通常使用する基準を、Snapchat 顧客リスト内の該当ユーザーに対して広告をトリガーするときに使用できるようになりました。
 
 **オーディエンス同期の一般的な使用例には次のものがあります:**
 
 - 複数のチャネルを通じて高価値ユーザーをターゲティングし、購入またはエンゲージメントを促進する
 - 他のマーケティングチャネルに対してレスポンシブでないユーザーをリターゲティングする
-- 抑制オーディエンスを作成して、すでにあなたのブランドの忠実な消費者であるユーザーが広告を受け取らないようにする
-- 新しいユーザーをより効率的に獲得するための類似オーディエンスの作成
+- すでに自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑制オーディエンスを作成する
+- 新規ユーザーをより効率的に獲得するための類似オーディエンスを作成する
 
-この機能により、ユーザーは特定のファーストパーティデータがSnapchatと共有されるかどうかをコントロールできます。Brazeでは、ファーストパーティデータを共有できる統合と共有できない統合が最優先で考慮されます。詳細については、当社の[プライバシーポリシー](https://www.braze.com/privacy)を参照してください。
+この機能により、ユーザーは特定のファーストパーティデータがSnapchatと共有されるかどうかをコントロールできます。Braze では、ファーストパーティデータを共有できる統合と共有できない統合を最大限に考慮しています。詳細については、当社の[プライバシーポリシー](https://www.braze.com/privacy)を参照してください。
 
 {% alert important %}
-**Audience Sync Pro 免責事項**<br>
-BrazeオーディエンスSync to SnapchatはAudience Sync Proの統合です。この統合の詳細については、Brazeアカウントマネージャーにお問い合わせください。
+**Audience Sync Pro 免責条項**<br>
+Braze Audience Sync to Snapchat はAudience Sync Pro 統合です。この統合の詳細については、Brazeアカウントマネージャーにお問い合わせください。
 {% endalert %}
 
 ## 前提条件 
 
-キャンバスでSnapchatオーディエンスステップを設定する前に、次の項目が作成、完了、および/または受け入れられていることを確認する必要があります。
+キャンバスで Snapchat オーディエンスステップを設定する前に、以下の項目が作成、完了、または受け入れられていることを確認する必要があります。
 
-| 要件 | Origin | 説明 |
+| 要件 | 提供元 | 説明 |
 | --- | --- | --- |
-| Snapchatビジネスマネージャー | スナップチャット | ブランドのSnapchatアセット（広告アカウント、ページ、アプリなど）を管理するための集中化されたツール。 |
-| Snapchat広告アカウント | スナップチャット | ブランドのSnapchatビジネスマネージャーに紐づけられたアクティブなSnapchat広告アカウント。<br><br>Snapchat Business マネージャーの管理者が、Brazeで使用する予定のSnapchat広告アカウントに対する管理者権限を付与していることを確認してください。 |
-| Snapchatの利用規約とポリシー | [スナップチャット](https://www.snap.com/en-US/policies) | Snapchat Audience Syncの使用に関連するSnapchatの必要な条件、ポリシー、ガイドライン、およびドキュメント、ならびにそれに組み込まれている条件、ポリシー、ガイドライン、およびドキュメントに従うことに同意します。これには、利用規約、ビジネス利用規約、開発者利用規約、オーディエンスマッチ、広告ポリシー、商業コンテンツポリシー、コミュニティガイドライン、およびサプライヤー責任が含まれる場合があります。 |
+| Snapchatビジネスマネージャー | Snapchat | ブランドのSnapchatアセット（広告アカウント、ページ、アプリなど）を管理するための集中化されたツール。 |
+| Snapchat広告アカウント | Snapchat | ブランドのSnapchatビジネスマネージャーに紐づけられたアクティブなSnapchat広告アカウント。<br><br>Snapchat Business マネージャーの管理者が、Brazeで使用する予定のSnapchat広告アカウントに対する管理者権限を付与していることを確認してください。 |
+| Snapchatの利用規約とポリシー | [Snapchat](https://www.snap.com/en-US/policies) | Snapchat Audience Sync Snapchat のすべての必須条件、ポリシー、ガイドライン、ドキュメントを遵守することに同意するものとします。これには、引用により組み込まれるすべての条件、ポリシー、ガイドライン、および文書 (利用規約、ビジネス利用規約、開発者規約、オーディエンスマッチ、広告ポリシー、商用コンテンツポリシー、サプライヤー責任などを含む) が含まれます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合 
@@ -46,103 +46,103 @@ BrazeオーディエンスSync to SnapchatはAudience Sync Proの統合です。
 Brazeのダッシュボードで、**パートナー統合** > **テクノロジーパートナー** に移動し、**Snapchat** を選択します。Snapchatオーディエンスエクスポートモジュールで、**Snapchatに接続**をクリックします。
 
 {% alert note %}
-古いナビゲーションを使用している場合は、統合の下にテクノロジーパートナーを見つけることができます。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-![BrazeのSnapchatテクノロジーページには、概要モジュールとSnapchatオーディエンス同期モジュールが含まれており、接続されたSnapchatボタンがあります。][1]{: style="max-width:80%;"}
+![Braze の Snapchat テクノロジーページ。「概要」モジュール、「Snapchat Audience Sync」モジュール、「Snapchat に接続」ボタンが表示されている。][1]{: style="max-width:80%;"}
 
-次に、SnapchatのOAuthページにリダイレクトされ、オーディエンス同期統合に関連する権限のためにBrazeを承認します。
+次に、Snapchat OAuth ページにリダイレクトされ、Braze に Audience Sync 統合に関連するアクセス許可を承認します。
 
 確認を選択すると、Brazeに戻り、同期するSnapchat広告アカウントを選択します。 
 
 ![Snapchatに接続できる利用可能な広告アカウントのリストです。][2]{: style="max-width:80%;"}
 
-接続に成功すると、パートナーページに戻り、どのアカウントが接続されているかを確認し、既存のアカウントを切断することができます。
+接続に成功すると、パートナーページに戻り、どのアカウントが接続されているかを表示したり、既存のアカウントを切断したりできます。
 
-![Snapchatテクノロジーパートナーページの更新バージョンが表示され、接続に成功した広告アカウントが表示されます。][3]{: style="max-width:80%;"}
+![広告アカウントが接続されたことを示す更新後の Snapchat テクノロジーパートナーページ。][3]{: style="max-width:80%;"}
 
 あなたのSnapchat接続はBrazeワークスペースレベルで適用されます。Snapchatの管理者がSnapchat Business Managerまたは接続されたSnapchat広告アカウントへのアクセスからあなたを削除した場合、Brazeは無効なトークンを検出します。その結果、Snapchatを使用しているアクティブなキャンバスにエラーが表示され、Brazeはユーザーを同期できなくなります。
 
-### ステップ2:スナップチャットでオーディエンス同期ステップを追加
+### ステップ2:Snapchat でオーディエンスの同期ステップを追加する
 
-キャンバスにコンポーネントを追加し、**オーディエンス同期**を選択します。
+キャンバスにコンポーネントを追加し、\[**オーディエンスの同期**] を選択します。
 
 ![][18]{: style="max-width:35%;"} ![][20]{: style="max-width:28%;"}
 
 ### ステップ3:同期セットアップ
 
-**カスタムオーディエンス** ボタンをクリックして、コンポーネントエディタを開封します。
+\[**カスタムオーディエンス**] ボタンをクリックしてコンポーネントエディターを開きます。
 
 **TikTok** を希望するオーディエンス同期パートナーとして選択します。
 
 ![][19]{: style="max-width:80%;"}
 
-次に、希望するSnapchat広告アカウントを選択します。**新規または既存のオーディエンスを選択**ドロップダウンで、新規または既存のオーディエンスの名前を入力します。
+次に、希望するSnapchat広告アカウントを選択します。\[**新規または既存のオーディエンスを選択**] ドロップダウンで、新しいオーディエンスまたは既存のオーディエンスの名前を入力します。
 
 {% tabs %}
-{% tab 新しいオーディエンスを作成する %}
+{% tab 新規オーディエンスの作成 %}
 
-**新しいオーディエンスを作成**<br>
+**新規オーディエンスの作成**<br>
 新しいオーディエンスの名前を入力し、**オーディエンスにユーザーを追加**を選択し、Snapchatと同期したいフィールドを選択します。次に、ステップエディタの下部にある**オーディエンスを作成**ボタンをクリックしてオーディエンスを保存します。
 
-![カスタムオーディエンスキャンバスステップの拡大ビュー。ここで、希望する広告アカウントが選択され、新しいオーディエンスが作成されます。]({% image_buster /assets/img/audience_sync/snapchat3.png %})
+![カスタムオーディエンスキャンバスステップの展開ビュー。ここで、希望する広告アカウントが選択され、新しいオーディエンスが作成されます。]({% image_buster /assets/img/audience_sync/snapchat3.png %})
 
-ユーザーは、オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合に、ステップエディターの上部で通知されます。ユーザーは、オーディエンスが下書きモードで作成されたため、キャンバスの旅の後でこのオーディエンスをユーザー削除のために参照することもできます。
+ユーザーは、オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合に、ステップエディターの上部で通知されます。ユーザーは、後でキャンバスジャーニーでユーザーを削除するためにこのオーディエンスを参照することもできます。これは、オーディエンスが下書きで作成されたためです。
 
-![キャンバスコンポーネントで新しいオーディエンスが作成された後に表示されるアラートです。]({% image_buster /assets/img/audience_sync/snapchat2.png %})
+![キャンバスコンポーネントで新しいオーディエンスが作成された後に表示されるアラート。]({% image_buster /assets/img/audience_sync/snapchat2.png %})
 
-新しいオーディエンスでキャンバスを起動すると、Brazeはオーディエンス同期コンポーネントに入るときにユーザーをほぼリアルタイムで同期します。
+新しいオーディエンスを使用してキャンバスを起動すると、オーディエンス同期コンポーネントに入る時点で、Braze はユーザーをほぼリアルタイムで同期します。
 
 {% endtab %}
 {% tab 既存のオーディエンスと同期する %}
-**既存のオーディエンスと同期する**<br>
-Brazeは、これらのオーディエンスが最新であることを確認するために、ユーザーを既存のSnapchatオーディエンスに追加する機能も提供します。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンス名を入力し、**オーディエンスに追加**。Brazeは、ユーザーがオーディエンス同期コンポーネントに入ると、ほぼリアルタイムでユーザーを追加します。
+**既存のオーディエンスとの同期**<br>
+また、Braze は、これらのオーディエンスが最新であることを確認するために、既存の Snapchat オーディエンスにユーザーを追加する機能も提供します。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンスの名前を入力し、**オーディエンスに追加します。**Braze は、オーディエンス同期コンポーネントに入ると、ほぼリアルタイムでユーザーを追加します。
 
-![カスタムオーディエンスキャンバスステップの拡大ビュー。ここで、希望する広告アカウントと既存のオーディエンスが選択されます。]({% image_buster /assets/img/audience_sync/snapchat.png %})
+![カスタムオーディエンスキャンバスステップの展開ビュー。ここで、希望する広告アカウントと既存のオーディエンスが選択されます。]({% image_buster /assets/img/audience_sync/snapchat.png %})
 
 {% endtab %}
 {% endtabs %}
 
 ### ステップ4:キャンバスを起動
 
-オーディエンス同期をSnapchatに設定したら、キャンバスを起動しましょう！新しいオーディエンスが作成され、Audience Syncステップを通過するユーザーはこのオーディエンスにSnapchatで渡されます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーはユーザー ジャーニーの次のステップに進みます。
+オーディエンス同期をSnapchatに設定したら、キャンバスを起動しましょう！新しいオーディエンスが作成され、オーディエンス同期ステップを通過するユーザーは Snapchat のこのオーディエンスに送られます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーはユーザージャーニーの次のステップに進みます。
 
-Snapchatでオーディエンスを表示するには、広告マネージャーアカウントにログインし、ナビゲーションのアセットセクションから**オーディエンス**を選択します。オーディエンスページから、各オーディエンスのサイズが約1,000に達した後のサイズを確認できます。
+Snapchatでオーディエンスを表示するには、広告マネージャーアカウントにログインし、ナビゲーションのアセットセクションから**オーディエンス**を選択します。\[**Audience**] ページで、各オーディエンスが1,000に達した後のオーディエンスのサイズを確認できます。
 
-![オーディエンスの詳細には、オーディエンス名、オーディエンスタイプ、オーディエンスサイズ、およびオーディエンスの保持日数が含まれます。][9]
+![オーディエンスの名前、オーディエンスの種類、オーディエンスのサイズ、オーディエンスのリテンション (日単位) を含む、指定された Snapchat オーディエンスのオーディエンス詳細。][9]
 
 ## ユーザーの同期とレート制限の考慮事項
 
 ユーザーがオーディエンス同期ステップに到達すると、BrazeはSnapchatのAPIレート制限を尊重しながら、これらのユーザーをほぼリアルタイムで同期します。実際には、Brazeはできるだけ多くのユーザーを5秒ごとにバッチ処理し、これらのユーザーをSnapchatに送信しようとします。
 
-SnapchatのAPIレート制限は、1秒あたり10件以下のクエリと1リクエストあたり100,000人のユーザーを規定しています。Brazeの顧客がこのレート制限に達した場合、Brazeのキャンバスは最大約13時間同期を再試行します。同期が不可能な場合、これらのユーザーは「ユーザーエラー」メトリックにリストされます。
+Snapchat の API レート制限では、1秒あたり10件のクエリと、リクエストあたり100,000のユーザーを超えないように設定されています。Brazeの顧客がこのレート制限に達した場合、Brazeのキャンバスは最大約13時間同期を再試行します。同期が不可能な場合、これらのユーザーは「ユーザーエラー」メトリックにリストされます。
 
 ### 分析の理解
 
-次の表には、Audience Syncコンポーネントからの分析をよりよく理解するための指標と説明が含まれています。
+次の表に、オーディエンス同期コンポーネントからの分析をよりよく理解するのに役立つ指標と説明を示します。
 
-| メートル法 | 説明 |
+| 指標 | 説明 |
 | --- | --- |
-| 入力済み | このコンポーネントに入力したユーザー数をSnapchatに同期します。 |
-| 次のステップに進みました | 次のコンポーネントがある場合、何人のユーザーが進みましたか？すべてのユーザーは、これがキャンバスブランチの最後のステップである場合、自動的に進みます。 |
+| 入力済み | Snapchat と同期するためにこのコンポーネントに入ったユーザーの数。 |
+| 次のステップに進みました | 次のコンポーネントがある場合、次のコンポーネントに進んだユーザーの数は?これがキャンバスブランチの最後のステップである場合、すべてのユーザーは自動的に進みます。 |
 | ユーザーが同期されました | Snapchatに正常に同期されたユーザーの数。 |
 | 同期されていないユーザー | 一致するフィールドが不足しているために同期されていないユーザーの数。 |
-| 保留中のユーザー | 現在、BrazeによってSnapchatに同期されているユーザーの数。 |
-| ユーザーがエラーを起こしました | APIエラーのため、約13時間のリトライ後にSnapchatに同期されなかったユーザーの数。エラーの潜在的な原因には、無効なSnapchatトークンや、Snapchatでオーディエンスが削除された場合が含まれます。 |
-| キャンバスを終了しました | キャンバスを終了したユーザーの数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生します。 |
+| 保留中のユーザー | Braze が Snapchat と同期するために現在処理されているユーザーの数。 |
+| エラーが発生したユーザー数 | APIエラーのため、約13時間のリトライ後にSnapchatに同期されなかったユーザーの数。エラーの潜在的な原因には、無効なSnapchatトークンや、Snapchatでオーディエンスが削除された場合が含まれます。 |
+| 終了済みのキャンバス | キャンバスを終了したユーザーの人数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert important %}
-同期されたユーザーとエラーメトリックの報告には、バルクフラッシャーとそれぞれ13時間のリトライのために遅延が発生することを覚えておいてください。
+一括フラッシャーと13時間の再試行のために、同期されたユーザーとエラーが発生したユーザーの指標のレポートに遅延が発生することに注意してください。
 {% endalert %}   
 
 ## トラブルシューティング
 
-{% details 無効なトークンエラーを受け取った場合、次に何をすべきですか？ %}
-SnapchatパートナーページでSnapchatアカウントを切断して再接続できます。Snapchat Business マネージャーの管理者に、同期したい広告アカウントに対する適切な権限があることを確認してください。
+{% details 無効なトークンエラーが発生した場合には次に何をすべきですか？ %}
+SnapchatパートナーページでSnapchatアカウントを切断して再接続できます。同期する広告アカウントに対する適切なアクセス許可があることを Snapchat Business Manager 管理者に確認します。
 {% enddetails %}
 
-{% details なぜ私のキャンバスは起動できないのですか？ %}
+{% details キャンバスを起動できないのはなぜですか? %}
 SnapchatパートナーページでSnapchat広告アカウントがBrazeに正常に接続されるようにしてください。広告アカウントを選択し、新しいオーディエンスの名前を入力し、一致するフィールドを選択したことを確認してください。
 {% enddetails %}
 
@@ -150,10 +150,10 @@ SnapchatパートナーページでSnapchat広告アカウントがBrazeに正
 Snapchatは、データプライバシーポリシーに関するこの情報を提供していません。
 {% enddetails %}
 
-{% details Snapchatはどれくらいのオーディエンスをサポートできますか？ %}
-現時点では、Snapchatアカウント内に1,000人のオーディエンスしか持つことができません。
-この制限を超えると、Brazeは新しいオーディエンスを作成できないことを通知します。
-Snapchat広告アカウントにログインして、使用していないオーディエンスを削除する必要があります。
+{% details Snapchat がサポート可能なオーディエンス数は? %}
+現時点では、Snapchat アカウントに含めることができるオーディエンスの数は1,000です。
+この制限を超えると、Braze は新しいオーディエンスを作成できないことを通知します。
+Snapchat の広告アカウントにログインして、使用していないオーディエンスを削除する必要があります。
 {% enddetails %}
 
 [1]: {% image_buster /assets/img/snapchat/snapchat1.png %}
diff --git a/_lang/ja/_partners/canvas_steps/tiktok_audience_sync.md b/_lang/ja/_partners/canvas_steps/tiktok_audience_sync.md
index df0eef3b8cf..117c63ea1b5 100644
--- a/_lang/ja/_partners/canvas_steps/tiktok_audience_sync.md
+++ b/_lang/ja/_partners/canvas_steps/tiktok_audience_sync.md
@@ -11,31 +11,31 @@ page_order: 5
 
 # オーディエンス同期先はTikTok
 
-ブランドは、Braze Audience Syncを使用してTikTokにユーザーデータを追加し、行動トリガー、セグメンテーションなどに基づいて広告を配信することができます。Braze キャンバスでメッセージ（プッシュ、メール、SMS、Webhookなど）をトリガーするために通常使用する任意の基準。 
+Braze Audience Sync to TikTok を使用すると、ブランドは独自の Braze 統合からのユーザーデータを TikTok オーディエンスに追加して、行動トリガーやセグメンテーションなどに基づいて広告を配信できます。Braze キャンバスでメッセージ (プッシュ、メールSMS、Webhook など) をトリガーするために通常使用する基準です。 
 
-**オーディエンス同期の一般的な使用例には**:
+**オーディエンス同期の一般的なユースケースには次のものがあります。**
 
 - 複数のチャネルを通じて高価値ユーザーをターゲットにして、購入やエンゲージメントを促進する
 - 他のマーケティングチャネルに対してレスポンシブでないユーザーをリターゲティングする
-- 抑制オーディエンスを作成して、すでにブランドの忠実な消費者であるユーザーが広告を受け取らないようにする
+- すでに自社ブランドの忠実な消費者であるユーザーが広告を受け取ることを防ぐための抑制オーディエンスを作成する
 - 新しいユーザーをより効率的に獲得するためのActalikeオーディエンスの作成
 
-この機能により、ブランドは特定のファーストパーティデータがTikTokと共有されるかどうかをコントロールできます。Brazeでは、ファーストパーティデータを共有できる統合と共有できない統合が最優先で考慮されます。詳細については、私たちの[プライバシーポリシー](https://www.braze.com/privacy)を参照してください。
+この機能により、ブランドは特定のファーストパーティデータがTikTokと共有されるかどうかをコントロールできます。Braze では、ファーストパーティデータを共有できる統合と共有できない統合を最大限に考慮しています。詳細については、私たちの[プライバシーポリシー](https://www.braze.com/privacy)を参照してください。
 
 {% alert important %}
-**Audience Sync Pro 免責事項**<br>
-BrazeオーディエンスSync to TikTokはAudience Sync Proの統合です。この統合の詳細については、Brazeアカウントマネージャーにお問い合わせください。
+**Audience Sync Pro 免責条項**<br>
+Braze Audience Sync to TikTok は Audience Sync Pro 統合です。この統合の詳細については、Brazeアカウントマネージャーにお問い合わせください。
 {% endalert %}
 
 ## 前提条件
 
 キャンバスでTikTokオーディエンスステップを設定する前に、次の項目が作成、完了、および/または受け入れられていることを確認する必要があります。
 
-| 要件 | Origin | 説明 |
+| 要件 | 提供元 | 説明 |
 | ----------- | ------ | ----------- |
-| TikTok for Business Centerアカウント | [ティックトック](https://business.tiktok.com/) | ブランドのTikTokアセット（広告アカウント、ページ、アプリなど）を管理するための集中型ツール。 |
-| TikTok広告アカウント | [ティックトック](https://ads.tiktok.com/) | ブランドのビジネスセンターアカウントに紐づけられたアクティブなTikTok広告アカウント。<br><br>TikTokビジネスセンターマネージャーの管理者が、Brazeで使用する予定のTikTok広告アカウントに対する管理者権限を付与していることを確認してください。 |
-| TikToKの利用規約とポリシー | [ティックトック](https://ads.tiktok.com/i18n/official/policy/terms) | Pinterestオーディエンス同期の使用に関連するTikTokの必要な条件、ポリシー、ガイドライン、およびドキュメント、ならびにそれに組み込まれている条件、ポリシー、ガイドライン、およびドキュメント（商業利用規約、広告利用規約、プライバシーポリシー、カスタムオーディエンス利用規約、開発者利用規約、開発者データ共有契約、広告ポリシー、ブランドガイドライン、コミュニティガイドラインを含む）に同意すること。 |
+| TikTok for Business Center アカウント | [TikTok](https://business.tiktok.com/) | ブランドのTikTokアセット（広告アカウント、ページ、アプリなど）を管理するための集中型ツール。 |
+| TikTok広告アカウント | [TikTok](https://ads.tiktok.com/) | ブランドのビジネスセンターアカウントに紐づけられたアクティブなTikTok広告アカウント。<br><br>TikTokビジネスセンターマネージャーの管理者が、Brazeで使用する予定のTikTok広告アカウントに対する管理者権限を付与していることを確認してください。 |
+| TikToKの利用規約とポリシー | [TikTok](https://ads.tiktok.com/i18n/official/policy/terms) | Pinterestオーディエンス同期の使用に関連するTikTokの必要な条件、ポリシー、ガイドライン、およびドキュメント、ならびにそれに組み込まれている条件、ポリシー、ガイドライン、およびドキュメント（商業利用規約、広告利用規約、プライバシーポリシー、カスタムオーディエンス利用規約、開発者利用規約、開発者データ共有契約、広告ポリシー、ブランドガイドライン、コミュニティガイドラインを含む）に同意すること。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合 
@@ -45,7 +45,7 @@ BrazeオーディエンスSync to TikTokはAudience Sync Proの統合です。
 Brazeのダッシュボードで、**Partner Integrations** > **Technology Partners** に移動し、**TikTok** を選択します。TikTokオーディエンスエクスポートモジュールで、**Connect TikTok**をクリックします。
 
 {% alert note %}
-古いナビゲーションを使用している場合は、統合の下にテクノロジーパートナーを見つけることができます。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
 ![BrazeのTikTokテクノロジーページには、概要モジュールと接続されたTikTokボタンを備えたTikTokオーディエンスエクスポートモジュールが含まれています。][1]{: style="max-width:75%;"}
@@ -54,94 +54,94 @@ Brazeのダッシュボードで、**Partner Integrations** > **Technology Partn
 
 ![][2]{: style="max-width:75%;"}
 
-接続に成功すると、パートナーページに戻ります。ここでは、接続されているアカウントを表示し、既存のアカウントの接続を解除できます。
+接続に成功すると、パートナーページに戻ります。ここでは、接続されているアカウントを表示したり、既存のアカウントの接続を解除したりできます。
 
 ![][3]{: style="max-width:75%;"}
 
-お客様のTikTok接続はBrazeアプリグループレベルで適用されます。TikTokの管理者がTikTokビジネスセンターまたは接続されたTikTokアカウントへのアクセスを削除した場合、Brazeは無効なトークンを検出します。その結果、アクティブなキャンバスでTikTokオーディエンスコンポーネントを使用している場合、エラーが表示され、Brazeはユーザーを同期できなくなります。
+お客様のTikTok接続はBrazeアプリグループレベルで適用されます。TikTokの管理者がTikTokビジネスセンターまたは接続されたTikTokアカウントへのアクセスを削除した場合、Brazeは無効なトークンを検出します。その結果、TikTok オーディエンスコンポーネントを使用しているアクティブなキャンバスにはエラーが表示され、Braze はユーザーを同期できません。
 
-### ステップ2:キャンバスフローにTikTokオーディエンスコンポーネントを追加
+### ステップ2:キャンバスフローで TikTok オーディエンスコンポーネントを追加する
 
-キャンバスにコンポーネントを追加し、**オーディエンス同期**を選択します。 
+キャンバスにコンポーネントを追加し、\[**オーディエンスの同期**] を選択します。 
 
 ![][18]{: style="max-width:35%;"} ![][20]{: style="max-width:28%;"}
 
 ### ステップ3:同期セットアップ
 
-**カスタムオーディエンス** ボタンをクリックして、コンポーネントエディタを開封します。
+\[**カスタムオーディエンス**] ボタンをクリックしてコンポーネントエディターを開きます。
 
 **TikTok** を希望するオーディエンス同期パートナーとして選択します。
 
 ![][19]{: style="max-width:80%;"}
 
-次に、目的のTikTok広告アカウントを選択します。**新規または既存のオーディエンスを選択**ドロップダウンで、新規または既存のオーディエンスの名前を入力します。
+次に、目的のTikTok広告アカウントを選択します。\[**新規または既存のオーディエンスを選択**] ドロップダウンで、新しいオーディエンスまたは既存のオーディエンスの名前を入力します。
 
 ![][11]
 
 {% tabs %}
-{% tab 新しいオーディエンスを作成する %}
+{% tab 新規オーディエンスの作成 %}
 
-**新しいオーディエンスを作成する**<br>
+**新規オーディエンスの作成**<br>
 新しいオーディエンスの名前を入力し、**オーディエンスにユーザーを追加**を選択し、TikTokと同期したいフィールドを選択します。次に、ステップエディタの下部にある**オーディエンスを作成**ボタンをクリックしてオーディエンスを保存します。
 
 ![]({% image_buster /assets/img/audience_sync/tiktok3.png %})
 
-ユーザーは、オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合、ステップエディターの上部で通知されます。ユーザーは、キャンバスの旅の後でユーザーを削除するために、このオーディエンスを参照することもできます。なぜなら、オーディエンスは下書きモードで作成されたからです。
+ユーザーは、オーディエンスが正常に作成された場合、またはこのプロセス中にエラーが発生した場合、ステップエディターの上部で通知されます。ユーザーは、後でキャンバスジャーニーでユーザーを削除するためにこのオーディエンスを参照することもできます。これは、オーディエンスが下書きで作成されたためです。
 
 ![]({% image_buster /assets/img/audience_sync/tiktok2.png %})
 
-キャンバスを新しいオーディエンスで開始すると、Brazeはオーディエンスステップに入るときにユーザーをほぼリアルタイムで同期します。
+新しいオーディエンスを使用してキャンバスを起動すると、ユーザーがオーディエンスステップに入る時点で、Braze はユーザーをほぼリアルタイムで同期します。
 
 {% endtab %}
 {% tab 既存のオーディエンスと同期する %}
 
-**既存のオーディエンスと同期する**<br>
-Brazeは、これらのオーディエンスが最新であることを確認するために、ユーザーを既存のTikTokオーディエンスに追加する機能も提供しています。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンス名を入力し、**オーディエンスに追加**。Brazeは、ユーザーがTikTokオーディエンスステップに入ると、ほぼリアルタイムでユーザーを追加します。
+**既存のオーディエンスとの同期**<br>
+Brazeは、これらのオーディエンスが最新であることを確認するために、ユーザーを既存のTikTokオーディエンスに追加する機能も提供しています。既存のオーディエンスと同期するには、ドロップダウンに既存のオーディエンスの名前を入力し、**オーディエンスに追加します。**Brazeは、ユーザーがTikTokオーディエンスステップに入ると、ほぼリアルタイムでユーザーを追加します。
 
-![カスタムオーディエンスキャンバスステップの拡大ビュー。ここで、希望する広告アカウントと既存のオーディエンスが選択されます。]({% image_buster /assets/img/audience_sync/tiktok.png %})
+![カスタムオーディエンスキャンバスステップの展開ビュー。ここで、希望する広告アカウントと既存のオーディエンスが選択されます。]({% image_buster /assets/img/audience_sync/tiktok.png %})
 
 {% endtab %}
 {% endtabs %}
 
 ### ステップ4:キャンバスを起動
-TikTokオーディエンスコンポーネントを構成したら、キャンバスを起動するだけです！新しいオーディエンスが作成され、TikTokオーディエンスコンポーネントを通過するユーザーは、このオーディエンスにTikTokで渡されます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーはユーザー ジャーニーの次のステップに進みます。
+TikTokオーディエンスコンポーネントを構成したら、キャンバスを起動するだけです！新しいオーディエンスが作成され、オーディエンス同期ステップを通過するユーザーは TikTok のこのオーディエンスに送られます。キャンバスに後続のコンポーネントが含まれている場合、ユーザーはユーザージャーニーの次のステップに進みます。
 
-TikTokでオーディエンスを表示するには、**広告マネージャーアカウント**にログインし、**アセット**のドロップダウンから**オーディエンス**を選択します。オーディエンスページから、各オーディエンスのサイズが約1,000に達した後のサイズを確認できます。
+TikTokでオーディエンスを表示するには、**広告マネージャーアカウント**にログインし、**アセット**のドロップダウンから**オーディエンス**を選択します。\[**Audience**] ページで、各オーディエンスが1,000に達した後のオーディエンスのサイズを確認できます。
 
-![TikTokページには、指定されたオーディエンスのための以下の指標がリストされています。][5]
+![指定したオーディエンスの以下の指標をリストする TikTok ページ。][5]
 
 ## ユーザーの同期とレート制限の考慮事項
 
 ユーザーがオーディエンス同期ステップに到達すると、BrazeはTikTokのマーケティングAPIのレート制限を尊重しながら、これらのユーザーをほぼリアルタイムで同期します。これは、Brazeが5秒ごとにできるだけ多くのユーザーをバッチ処理し、これらのユーザーをTikTokに送信することを意味します。
 
-TikTokのSegment APIレート制限は、1秒あたり50クエリ以下、1リクエストあたり10,000ユーザー以下とされています。Brazeの顧客がこのレート制限に達した場合、キャンバスは最大約13時間同期を再試行します。同期が不可能な場合、これらのユーザーはエラーが発生したユーザーメトリックに一覧表示されます。
+TikTok の Segment API レート制限では、1秒あたり50件のクエリと1リクエストあたり1万のユーザーを超えないように設定されています。Braze のお客様がこのレート制限に達した場合、キャンバスは最大13時間にわたって同期を再試行します。同期が不可能な場合、これらのユーザーはエラーが発生したユーザーメトリックに一覧表示されます。
 
 ## 分析の理解
 
-次の表には、Audience Syncコンポーネントからの分析をよりよく理解するための指標と説明が含まれています。
+次の表に、オーディエンス同期コンポーネントからの分析をよりよく理解するのに役立つ指標と説明を示します。
 
-| メートル法 | 説明 |
+| 指標 | 説明 |
 | ------ | ----------- |
-| 入力済み | このコンポーネントに入力したユーザーの数をTikTokに同期します。 |
-| 次のステップに進みました | 次のコンポーネントに進んだユーザーの数（存在する場合）。すべてのユーザーは、これがキャンバスブランチの最後のステップである場合、自動的に進みます。 |
+| 入力済み | TikTok と同期するためにこのコンポーネントに入ったユーザーの数。 |
+| 次のステップに進みました | 次のコンポーネントに進んだユーザーの数 (存在する場合)。これがキャンバスブランチの最後のステップである場合、すべてのユーザーは自動的に進みます。 |
 | ユーザーが同期されました | TikTokに正常に同期されたユーザーの数。このことは、TikTokで一致したユーザーと同じではないことに注意してください。 |
 | 同期されていないユーザー | 一致するフィールドが不足しているため、同期されていないユーザーの数。 |
-| 保留中のユーザー | 現在、BrazeによってTikTokに同期されているユーザーの数。 |
-| ユーザーがエラーを起こしました | 約13時間のリトライ後、APIエラーのためにTikTokに同期されなかったユーザーの数。エラーの潜在的な原因には、無効なTikTokトークンや、TikTokでオーディエンスが削除された場合が含まれます。 |
-| キャンバスを終了しました | キャンバスを終了したユーザーの数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生します。 |
+| 保留中のユーザー | Braze がTikTok と同期するために現在処理されているユーザーの数。 |
+| エラーが発生したユーザー数 | 約13時間のリトライ後、APIエラーのためにTikTokに同期されなかったユーザーの数。エラーの潜在的な原因には、無効なTikTokトークンや、TikTokでオーディエンスが削除された場合が含まれます。 |
+| 終了済みのキャンバス | キャンバスを終了したユーザーの人数。これは、キャンバスの最後のステップがオーディエンス同期コンポーネントである場合に発生します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert important %}
-ユーザーの同期とエラーメトリクスの報告には、バルクフラッシャーとそれぞれ13時間のリトライのために遅延が発生することを覚えておいてください。
+一括フラッシャーと13時間の再試行のために、同期されたユーザーとエラーが発生したユーザーの指標のレポートに遅延が発生することに注意してください。
 {% endalert %}
 
 ## トラブルシューティング
 
-{% details 無効なトークンエラーを受け取った場合、次に何をすべきですか？ %}
+{% details 無効なトークンエラーが発生した場合には次に何をすべきですか？ %}
 TikTokパートナーページでTikTokアカウントを切断して再接続できます。TikTokビジネスセンターの管理者に、同期したい広告アカウントに対する適切な権限があることを確認してください。
 {% enddetails %}
 
-{% details なぜ私のキャンバスは起動できないのですか？ %}
+{% details キャンバスを起動できないのはなぜですか? %}
 TikTokパートナーページでTikTokアカウントをBrazeに正常に接続してください。
 広告アカウントを選択し、新しいオーディエンスの名前を入力し、一致するフィールドを選択したことを確認してください。
 {% enddetails %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility.md b/_lang/ja/_partners/data_and_infrastructure_agility.md
index 89d23979ea9..c55e325f0c4 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility.md
@@ -4,7 +4,7 @@ article_title: データ＆インフラ・アジリティ・パートナー
 page_order: 5
 
 page_type: landing
-description: "このページでは、異なるツールやプロバイダー間でデータの送信、保存、その他の調整を可能にするBrazeパートナー（Alloys）をリストアップしている。"
+description: "このページには、さまざまなツールやプロバイダー間でデータを送信、保存、調整できるようにする Braze パートナー (Alloys) が一覧表示されています。"
 layout: partner_page
 search_tag: Partner
 
@@ -19,15 +19,15 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/zapier/
 - name: Zendesk
   url: /docs/partners/data_and_infrastructure_agility/support/zendesk/
-- name: パイプストリーム
+- name: Pypestream
   url: /docs/partners/data_and_infrastructure_agility/support/pypestream/
 - name: Amazon S3
   url: /docs/partners/data_and_infrastructure_agility/cloud_storage/amazon_s3/
 - name: Google Cloud Storage
   url: /docs/partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents/
-- name: マイクロソフト・アジュール
+- name: Microsoft Azure
   url: /docs/partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents/
-- name: アプテリジェント
+- name: Apteligent
   url: /docs/partners/data_and_infrastructure_agility/crash_analytics/apteligent/
 - name: Snowflake
   url: /docs/partners/data_and_infrastructure_agility/data_warehouses/snowflake/
@@ -35,9 +35,9 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/analytics/amplitude_for_currents/
 - name: Mixpanel
   url: /docs/partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents/
-- name: ルッカー
+- name: Looker
   url: /docs/partners/data_and_infrastructure_agility/analytics/looker/
-- name: クビット
+- name: Kubit
   url: /docs/partners/data_and_infrastructure_agility/analytics/kubit/
 - name: セグメント
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/segment/
@@ -53,86 +53,86 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/
 - name: NPAW
   url: /docs/partners/data_and_infrastructure_agility/analytics/npaw/
-- name: ジャカード
+- name: Jacquard
   url: /docs/partners/data_and_infrastructure_agility/ab_testing/jacquard/
-- name: ネクスラ
+- name: Nexla
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/nexla/
 - name: アンペア
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/amperity/
 - name: Hightouch
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/hightouch/
-- name: テニクル
+- name: Tinyclues
   url: /docs/partners/data_and_infrastructure_agility/cohort_import/tinyclues/
-- name: 超越する
+- name: Transcend
   url: /docs/partners/data_and_infrastructure_agility/data_privacy/transcend/
-- name: レベニューキャット
+- name: RevenueCat
   url: /docs/partners/data_and_infrastructure_agility/payments/revenuecat/
-- name: ブルーコニック
+- name: BlueConic
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/blueconic/
 - name: Adobe
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/adobe/
 - name: Zeotap
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/zeotap/
-- name: トゥービオ
+- name: Toovio
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/toovio/
-- name: レクサー
+- name: Lexer
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/lexer/
-- name: 除雪車
+- name: Snowplow
   url: /docs/partners/data_and_infrastructure_agility/analytics/snowplow/
-- name: クラリサイト
+- name: Clarisights
   url: /docs/partners/data_and_infrastructure_agility/analytics/clarisights/
 - name: Microsoft Dynamics 365
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights/
 - name: Heap
   url: /docs/partners/data_and_infrastructure_agility/cohort_import/heap/
-- name: アクショナブル・ドット・ミー
+- name: actionable.me
   url: /docs/partners/data_and_infrastructure_agility/analytics/actionableme/
-- name: ストーリー
+- name: Storyly
   url: /docs/partners/data_and_infrastructure_agility/cohort_import/storyly/
-- name: データ・グレイル
+- name: DataGrail
   url: /docs/partners/data_and_infrastructure_agility/data_privacy/datagrail/  
-- name: オクトリス
+- name: Octolis
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/octolis/
-- name: 思想スポット
+- name: ThoughtSpot
   url: /docs/partners/data_and_infrastructure_agility/analytics/thoughtspot/
-- name: ワンダーウィンド
+- name: Wunderkind
   url: /docs/partners/data_and_infrastructure_agility/analytics/wunderkind/
-- name: テリウス
+- name: Tellius
   url: /docs/partners/data_and_infrastructure_agility/analytics/tellius/
-- name: コンテンツスクエア
+- name: Contentsquare
   url: /docs/partners/data_and_infrastructure_agility/analytics/contentsquare/
-- name: シス
+- name: Sisu
   url: /docs/partners/data_and_infrastructure_agility/business_intelligence/sisu_data/
-- name: アクションIQ
+- name: ActionIQ
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/actioniq/
 - name: Airbyte
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/airbyte/
 - name: GrowthLoop
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/growthloop/
-- name: モーツァルト・データ
+- name: Mozart Data
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/mozart_data/
-- name: マーキュリー
+- name: Merkury
   url: /docs/partners/data_and_infrastructure_agility/analytics/merkury/
 - name: SalesWings
   url: /docs/partners/data_and_infrastructure_agility/analytics/saleswings/
-- name: ワントラスト
+- name: OneTrust
   url: /docs/partners/data_and_infrastructure_agility/data_privacy/onetrust/
 - name: Redpoint
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/redpoint/
-- name: サイモン・データ
+- name: Simon Data
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/simondata/
 - name: Ketch
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/ketch/
 - name: Lytics
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/lytics/
-- name: リカーリー
+- name: Recurly
   url: /docs/partners/data_and_infrastructure_agility/payments/recurly/
-- name: スキューバ
+- name: Scuba
   url: /docs/partners/data_and_infrastructure_agility/analytics/scuba/
-- name: メタ・ルーター
+- name: MetaRouter
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/metarouter/
 - name: トレジャーデータ
   url: /docs/partners/data_and_infrastructure_agility/cohort_import/treasuredata/
-- name: ライブランプ
+- name: LiveRamp
   url: /docs/partners/data_and_infrastructure_agility/advertising/liveramp/
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/ab_testing.md b/_lang/ja/_partners/data_and_infrastructure_agility/ab_testing.md
index 1e8b66c84ea..2edf414b18e 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/ab_testing.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/ab_testing.md
@@ -1,6 +1,6 @@
 ---
 nav_title: A/B テスト
-article_title: A/Bテスト・パートナー
+article_title: AB テストのパートナー
 layout: partner_page
 page_order: 0
 
@@ -14,7 +14,7 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "A/B Testing"
 
 valid_partner_list:
-- name: ジャカード
+- name: Jacquard
   url: /docs/partners/data_and_infrastructure_agility/ab_testing/jacquard/
 
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/ab_testing/jacquard.md b/_lang/ja/_partners/data_and_infrastructure_agility/ab_testing/jacquard.md
index 2702317cc17..693d18f5a2b 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/ab_testing/jacquard.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/ab_testing/jacquard.md
@@ -1,53 +1,53 @@
 ---
-nav_title: ジャカード
-article_title: ジャカード
+nav_title: Jacquard
+article_title: Jacquard
 page_order: 1
-description: "この参考記事では、Braze CurrentsとConnected Contentを活用し、Webhookを通じて購読者からクリックトラッキング情報を収集する、BrazeとJacquard Dynamic Optimisationのパートナーシップについて概説している。Jacquardは、これらのイベントをあなたの言語バリアントに結びつけ、リアルタイムで言語を最適化する。"
+description: "この参考記事では、Braze CurrentsとConnected Contentを活用し、Webhookを通じて購読者からクリックトラッキング情報を収集する、BrazeとJacquard Dynamic Optimisationのパートナーシップについて概説している。Jacquard は、これらのイベントを言語バリアントに関連付けて、リアルタイムで言語を最適化します。"
 page_type: partner
 search_tag: Partner
 ---
 
-# ジャカード・ダイナミック最適化
+# Jacquard のダイナミック最適化
 
-> [ジャカードは][1]、人工知能、計算言語学、顧客中心主義の精神を結集し、ブランド・ボイスに合わせてカスタマイズされたブランド・ランゲージを、大規模に、チャネルに展開することを支援する。
+> [Jacquard][1] は、人工知能、計算言語学、そして顧客中心の精神を融合し、ブランドボイスに合わせてカスタマイズされたチャネルにわたり、ブランドのメッセージを大規模に展開できるようにします。
 
-Jacquard Xを利用したDynamic Optimisationは、Braze CurrentsとConnected Contentを活用し、ウェブフックを通じて購読者からクリックトラッキング情報を収集する。Jacquardは、これらのイベントをあなたの言語バリアントに結びつけ、リアルタイムで言語を最適化する。 
+Jacquard Xを利用したDynamic Optimisationは、Braze CurrentsとConnected Contentを活用し、ウェブフックを通じて購読者からクリックトラッキング情報を収集する。Jacquard は、これらのイベントを言語バリアントに関連付けて、リアルタイムで言語を最適化します。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| ジャカード・アカウント | このパートナーシップを利用するには、[ジャカードのアカウントが][1]必要である。 |
-| ジャカード・コネクト・サーバー・トークン | Jacquard言語にアクセスするためのBrazeキャンペーンのパスワードとなる長い文字列。<br><br>まだ提供されていない場合は、ジャカードのカスタマー・サクセス・マネージャーにリクエストすることができる。 |
-| Currents | Currentsにデータをエクスポートするには、アカウントに[Braze Currentsを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents)設定する必要がある。 |
+| Jacquard アカウント | このパートナーシップを活用するには、[Jacquard アカウント][1]が必要です。 |
+| Jacquard 接続サーバートークン | Jacquard 言語にアクセスするための、Braze キャンペーンのパスワードとして機能する長い文字列。<br><br>このトークンがまだ提供されていない場合は、Jacquard カスタマーサクセスマネージャーにリクエストできます。 |
+| Currents | Currents にデータを再度エクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ 1:Jacquard Amazon S3の認証情報をリクエストする
 
-クリック・トラッキング・イベントをBrazeから受け取るには、Jacquardが専用のAmazon S3バケットをセットアップする必要がある。このプロセスを開始するには、ジャカードのカスタマー・サクセス・マネージャーに連絡すること。バケットが作成されると、Currentを作成するための固有の認証情報が提供される。 
+クリック・トラッキング・イベントをBrazeから受け取るには、Jacquardが専用のAmazon S3バケットをセットアップする必要がある。このプロセスを開始するには、Jacquard カスタマーサクセスマネージャーに連絡してください。バケットが作成されると、Current を作成するための一意の認証情報が提供されます。 
 
-### ステップ2:電流を作る
+### ステップ2:Current を作成する
 
-1. Brazeで、**Currents > Create New Current > Amazon S3 Data Exportを**選択する。 
-2. 次に、カレントの名前を付け、連絡先のEメールを入力する。
-3. 認証情報ボックスに、Jacquard AWSのアクセスキーIDとシークレットアクセスキーを追加する。次に、AWS S3バケット名として "frasee-braze-currents-exports "を追加する。 
-4. 最後に、Jacquardカスタマー・サクセス・マネージャーから受け取ったAWS S3バケット・フォルダを追加する。それはおそらくあなたの会社名だろう。
-5. **General Settings "**の "Include events from anonymous users "にチェックを入れ、**"Manage Engagement Events "**の "Email Click "にチェックを入れる。
-6. 終了したら、**Launch Currentを**選択する。
+1. Braze で、**\[Currents] > \[新しい Currents を作成] > \[Amazon S3 データのエクスポート]** を選択します。 
+2. 次に Current に名前を付け、連絡先メールを入力します。
+3. 認証情報ボックスに、Jacquard AWS アクセスキー ID とシークレットアクセスキーを追加します。次に、AWS S3バケット名として "frasee-braze-currents-exports "を追加する。 
+4. 最後に、Jacquard カスタマーサクセスマネージャーから受け取った AWS S3バケットフォルダーを追加します。これはお客様の社名である可能性があります。
+5. \[**一般設定**] の \[匿名ユーザーのイベントを含める] ボックスをオンにし、\[**エンゲージイベントの管理**] で \[メールクリック] をオンにします。
+6. 終了したら、\[**Currents を起動**] を選択します。
 
 ### ステップ 3:個人を特定できる情報（PII）の削除を要請すること。
 
-次に、Brazeのアカウントチームに連絡し、個人を特定できる情報がJacquardに送信されないようにする。
+次に、Braze アカウントチームに連絡し、個人を特定できる情報が Jacquard に送信されないようにします。
 
-デフォルトでは、カレントは電子メールや住所などの特定のPII属性を含む。JacquardはPIIを受け取ることはできないし、受け取ることもないので、Jacquardに渡されるすべてのイベントデータについてこれをオフにするよう、Brazeのアカウントチームにリクエストすることが重要である。
+デフォルトでは、Current にはメールや住所などの特定の PII 属性が含まれます。JacquardはPIIを受け取ることはできないし、受け取ることもないので、Jacquardに渡されるすべてのイベントデータについてこれをオフにするよう、Brazeのアカウントチームにリクエストすることが重要である。
 
-### ステップ 4:ジャカードXのコード・スニペット 
+### ステップ 4:Jacquard X コードスニペット 
 
-必要なコード・スニペットについては、Jacquardアカウント・チームに問い合わせること。
+必要なコードスニペットについては、Jacquard アカウントチームにお問い合わせください。
 
-これらのスニペットは[コネクテッドコンテンツを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content)活用し、メールに配置された後、言語とトラッキングピクセルを動的に取り込み、Jacquard Xを使ってリアルタイムで言語を最適化できる。
+これらのスニペットは[コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content)を利用しており、メールに配置されると、言語とトラッキングピクセルをダイナミックに取得します。これにより、Jacquard は Jacquard X を使用してリアルタイムで言語を最適化できます。
 
 
 [1]: https://www.jacquard.com/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/advertising.md b/_lang/ja/_partners/data_and_infrastructure_agility/advertising.md
index 9406a860abd..1a869aee757 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/advertising.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/advertising.md
@@ -5,7 +5,7 @@ page_order: 1
 config_only: true
 
 page_type: landing
-description: "このランディングページには、さまざまな広告技術を提供するブレイズのパートナー（合金）が掲載されている。"
+description: "このランディングページには、さまざまな広告テクノロジーを提供する Braze パートナー (Alloys) が一覧表示されています。"
 
 layout: partner_page
 search_tag: Partner
@@ -15,6 +15,6 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Advertising"
 
 valid_partner_list:
-- name: ライブランプ
+- name: LiveRamp
   url: /docs/partners/data_and_infrastructure_agility/advertising/liveramp/
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/advertising/liveramp.md b/_lang/ja/_partners/data_and_infrastructure_agility/advertising/liveramp.md
index fa1c69a32e3..7ad6fe5e6bd 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/advertising/liveramp.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/advertising/liveramp.md
@@ -1,7 +1,7 @@
 ---
-nav_title: ライブランプ
-article_title: ライブランプ
-description: "LiveRamp、Snowflake、Brazeの接続方法を学ぶことで、高度にパーソナライズされた関連性の高いマーケティングキャンペーンを作成できる。"
+nav_title: LiveRamp
+article_title: LiveRamp
+description: "LiveRamp、Snowflake、および Braze を接続する方法について説明します。この方法を理解することで、高度にパーソナライズされた関連性のあるマーケティングキャンペーンを作成できます。"
 alias: /partners/liveramp/
 page_type: partner
 search_tag: Partner
@@ -9,84 +9,84 @@ search_tag: Partner
 
 # LiveRamp、Snowflake、Brazeを接続する
 
-> LiveRamp、Snowflake、Brazeを接続する方法を学ぶことで、洞察までの時間を短縮し、データのサイロ化を解消し、顧客エンゲージメントを最適化することで、高度にパーソナライズされた関連性の高いマーケティングキャンペーンを作成できる。この統合は、実用的な個人ベースのインサイトを提供し、より良いオーディエンスのセグメンテーションとタイムリーなキャンペーンのために消費者とのタッチポイントを統合することにより、データ駆動型マーケティングを強化する。また、Snowflakeが提供するベンチマークを活用し、業界標準に照らし合わせてマーケティング戦略を洗練させることができる。
+> LiveRamp、Snowflake、Brazeを接続する方法を学ぶことで、洞察までの時間を短縮し、データのサイロ化を解消し、顧客エンゲージメントを最適化することで、高度にパーソナライズされた関連性の高いマーケティングキャンペーンを作成できる。この統合により、実用的な個人ベースのインサイトが提供され、消費者のタッチポイントが集約され、より適切なオーディエンスセグメンテーションとタイムリーなキャンペーンが可能になり、データドリブン型のマーケティングが強化されます。また、Snowflakeが提供するベンチマークを活用し、業界標準に照らし合わせてマーケティング戦略を洗練させることができる。
 
 {% alert important %}
-Snowflakeの[Secure Data Sharesは](https://docs.snowflake.com/en/user-guide/data-sharing-intro)、LiveRamp、Snowflake、Braze間でデータを転送しない。データはスノーフレークのサービスとメタデータストアを通じてのみ共有されるため、データはコピーされず、追加のストレージ料金も発生しない。共有データへのアクセスは、Snowflakeアカウントのアクセス制御を使用して制御・管理される。
+Snowflake の[セキュアデータシェアリング](https://docs.snowflake.com/en/user-guide/data-sharing-intro)では、LiveRamp、Snowflake、および Braze 間でデータが転送されません。データは、Snowflake のサービスおよびメタデータストアでのみ共有されます。つまり、データはコピーされず、追加のストレージ料金は発生しません。共有データへのアクセスは、Snowflake アカウントのアクセスコントロールを使用して制御および管理されます。
 {% endalert %}
 
 ## ユースケース
 
-- **データの最小化：**LiveRampのActivationアプリは、SnowflakeのSecure Data Share機能を使って、インスタンスから直接テーブルを効率的に読み取る。Snowflakeから下流のパートナーにデータを提供するまで、データは移動しない。
-- **安全な1st Party Activation：**上記のIdentity Resolutionアプリケーションを使用することで、LiveRampのActivationアプリケーションは、Snowflakeインスタンス内のRampIDベースのテーブルのみを使用するため、PIIが壁を離れることはない。
-- **生きる時間を早める：**お客様の環境で直接RampIDにデータを解決することにより、LiveRampのより伝統的なファイルベースのアプローチを使用する場合の数日と比較して、エンドデスティネーションへの配信は数時間以内に行うことができる。これにより、キャンペーンのパフォーマンスをタイムリーに最適化する能力が大幅に向上する。
-- **経営上の節約：**上記と同様に、スノーフレークのセキュアなデータ共有機能を使用することで、LiveRampや最終目的地への直接のファイル送信を調整する場合と比較して、顧客は時間とコストを節約することができる。
+- **データの最小化::**LiveRamp のアクティベーションアプリでは、Snowflake のセキュアデータシェア機能を使用して、インスタンスから直接テーブルを効率的に読み取ります。ダウンストリームパートナーに配信する時点までは、Snowflake からデータは移動されません。
+- **安全なファーストパーティのアクティベーション:**前述の ID 解決アプリケーションを使用することで、LiveRamp のアクティベーションアプリケーションはSnowflake インスタンスの RampID ベースのテーブルのみを使用します。このため、PII が外部へ流出することがありません。
+- **有効期間の促進:**お客様の環境でデータを直接 RampID に解決することで、最終宛先への配信が数時間内に行われます。これに対し、LiveRamp の従来のファイルベースの方法では、このような配信が行われるまでに数日間かかっていました。これにより、キャンペーンのパフォーマンスをタイムリーに最適化できる能力が大幅に向上します。
+- **運用コストの節約:**上記と同様に、ファイルの LiveRamp への出力またはその他の最終宛先への直接出力を調整することに比べ、Snowflake のセキュアデータシェアリング機能を使用することでお客様の時間と費用を節約できます。
 
 ## 前提条件
 
 | 前提条件       | 説明                                                                                                                                                                                     |
 |-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Snowflake アカウント | 管理者レベルの権限を持つSnowflakeアカウントが必要だ。                                                                                                                                      |
-| ライブランプ・アカウント  | Snowflake内で必要なLiveRampアプリケーションについては、LiveRampアカウント・チームまたは[snowflake@liveramp.com](mailto:snowflake@liveramp.com)まで連絡を。                              |
+| LiveRamp アカウント  | LiveRamp アカウントチームまたは [snowflake@liveramp.com](mailto:snowflake@liveramp.com) に連絡して、Snowflake 内で必要な LiveRamp アプリケーションについて話し合います。                              |
 {: .reset-td-br-1 .reset-td-br-2 }
 
 ## 統合をセットアップする
 
-### ステップ 1:ブレイズにデータ共有を依頼する
+### ステップ 1:Braze からのデータ共有を依頼する
 
-まず、Brazeアカウントマネージャーまたはカスタマーサクセスマネージャーに連絡して、Brazeアカウント用のSnowflake Data Share Connectorを購入する。データ共有をリクエストすると、Brazeは、共有が購入されたワークスペースから共有をプロビジョニングする。共有がプロビジョニングされると、すべてのデータは受信データ共有の形でSnowflakeインスタンス内からすぐにアクセスできるようになる。共有がインスタンスに表示されたら、共有からデータベースを作成し、テーブルを見たり問い合わせたりできるようにする。
+まず、Brazeアカウントマネージャーまたはカスタマーサクセスマネージャーに連絡して、Brazeアカウント用のSnowflake Data Share Connectorを購入する。データ共有を依頼すると、Braze は共有が購入されたワークスペースから共有をプロビジョニングします。共有がプロビジョニングされると、すべてのデータは Snowflake インスタンス内から受信データ共有の形式ですぐにアクセス可能になります。共有がインスタンスに表示されたら、共有からデータベースを作成し、テーブルを見たり問い合わせたりできるようにする。
 
-完全なウォークスルーは、[BrazeとのSnowflake統合ガイドを]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/)参照のこと。
+完全なウォークスルーについては、[Braze と Snowflake の統合ガイド]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/)を参照してください。
 
 ### ステップ2:SnowflakeでLiveRampアプリをセットアップする 
 
-翻訳とID解決の機能は、LiveRamp Identity Resolution and Translationネイティブアプリを通してSnowflake内で利用できる。
+翻訳機能と ID 解決機能は、Snowflake 内で LiveRamp Identity Resolution and Translation ネイティブアプリを通じて利用可能です。このアプリにより、アカウントに共有が作成され、ご利用の Snowflake 環境から参照データセットをクエリするためのビューが開かれます。
 
-ネイティブアプリをセットアップするには、LiveRampのドキュメントにある以下のステップに従う：[SnowflakeでLiveRampネイティブアプリをセットアップ](https://docs.liveramp.com/identity/en/set-up-the-liveramp-native-app-in-snowflake.html)する。終わったら、次のステップに進む。
+このネイティブアプリを設定するには、LiveRamp のドキュメント[Snowflake での LiveRamp ネイティブアプリの設定](https://docs.liveramp.com/identity/en/set-up-the-liveramp-native-app-in-snowflake.html)に記載されている手順に従います。終わったら、次のステップに進む。
 
 ### ステップ 3:データテーブルを作成する
 
 {% alert warning %}
-PIIベースのテーブルを準備する前に、ジョブ中に実行される[LiveRampのプライバシーフィルターを](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html)理解し、入力テーブルの属性カラム（非識別子）にユニークすぎる値が含まれていないことを確認する。これは、消費者のプライバシーを維持し、再識別を避けるために重要である。
+PII ベースのテーブルを準備する前に、ジョブで実行される [LiveRamp のプライバシーフィルター](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html)を理解し、入力テーブルの属性列 (識別子以外) に非常に独特な値が含まれていないことを確認してください。これは、消費者のプライバシーを維持し、再識別を避けるために重要である。
 {% endalert %}
 
-次に、LiveRampネイティブアプリに対して呼び出される、[必要なフォーマットの](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html)データテーブルを作成する。以下のカテゴリーを参照し、どの識別子が解決の対象となるかを判断する：
+次に、LiveRamp ネイティブアプリに対して呼び出されるデータテーブルを[必要な形式t](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html)で作成します。以下のカテゴリーを参照し、どの識別子が解決の対象となるかを判断する：
 
 | 識別子の種類 | 説明  |
 |-----------------|--------------|
-| 完全なPII        | 個人を特定できる情報（PII）には、ユーザーの氏名、住所、電子メール、電話番号などが含まれる。**注:**すべての識別子がすべての記録に必要なわけではない。 |
-| Eメールのみ      | `alex-lee@email.com` のようなユーザーのメールアドレス。 |
+| 完全な PII        | 個人を特定できる情報（PII）には、ユーザーの氏名、住所、電子メール、電話番号などが含まれる。**注:**すべての識別子がすべての記録に必要なわけではない。 |
+| Eメールのみ      | ユーザーのメールアドレス (`alex-lee@email.com` など)。 |
 | デバイス          | これには、サードパーティのクッキー、モバイル広告ID（MAID）、コネクテッドTV ID（CTV ID）、およびRampID（Household RampIDに解決される）が含まれる。 |
-| CIDについて            | これらは、プラットフォーム・パートナーからの識別子、またはLiveRampと同期したIDであり、社内の顧客IDなどである。 |
+| CID            | これらは、プラットフォームパートナーまたは LiveRamp との ID 同期からの識別子です (内部顧客 ID など)。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 #### ブレイズ識別子
 
-Brazeのイベントログには、LiveRampネイティブアプリ内で使用できる識別子が含まれている。各イベントタイプで使用可能な識別子の全リストは、[Braze Event Schemas and Identifiersを](https://www.braze.com/docs/assets/download_file/data-sharing-raw-table-schemas.txt)ダウンロードする。
+Brazeのイベントログには、LiveRampネイティブアプリ内で使用できる識別子が含まれている。各イベントタイプで使用可能な識別子の完全なリストについては、[Braze イベントのスキーマと識別子](https://www.braze.com/docs/assets/download_file/data-sharing-raw-table-schemas.txt)をダウンロードしてください。
 
 | 識別子の種類 | 説明  |
 |-----------------|--------------|
-| `AD_ID` | `ios_idfa`,`google_ad_id`,`roku_ad_id` のような広告IDは、特定のイベントタイプ内でキャプチャされ、LiveRampのDevice Resolutionサービスと組み合わせて使用することができる。デフォルトでは、Advertising IDは収集されないが、[Brazeのドキュメントに従って](https://www.braze.com/docs/user_guide/data_and_analytics/user_data_collection/sdk_data_collection/#data-not-collected-by-default)トラッキングを有効にすることができる。 |
-| `EMAIL_ADDRESS`   | LiveRampのEメールのみによる解決サービスと併用できるEメールアドレス |
-| `TO_PHONE_NUMBER` | 電話番号は、LiveRampのPII Resolutionサービスと組み合わせて使用することができる。 |
-| `EXTERNAL_USER_ID` | ユーザーに関連付けられた外部IDで、LiveRampのDevice Resolutionサービス（CID）と組み合わせて使用できる。 |
+| `AD_ID` | `ios_idfa`、`google_ad_id`、`roku_ad_id` などの広告 ID は、特定のイベントタイプ内でキャプチャされ、LiveRamp のデバイス解決サービスと組み合わせて使用できます。デフォルトでは広告 ID は収集されませんが、[Braze のドキュメント](https://www.braze.com/docs/user_guide/data_and_analytics/user_data_collection/sdk_data_collection/#data-not-collected-by-default)に従って追跡を有効にできます。 |
+| `EMAIL_ADDRESS`   | LiveRamp のメール専用解決サービスと併用できるメールアドレス |
+| `TO_PHONE_NUMBER` | LiveRamp の ＰＩＩ 解決サービスと併用できる電話番号 |
+| `EXTERNAL_USER_ID` | ユーザーに関連付けられた external ID。この ID は LiveRamp の Device Resolution サービスと併用できます (CID)。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert important %}
-LiveRampのアプリケーション内でクライアントまたはブランド固有のカスタム識別子を使用するには、[LiveRampとのID同期が](https://docs.liveramp.com/identity/en/getting-started-with-liveramp-identity.html)必要である。
+LiveRamp のアプリケーション内でクライアントまたはブランド固有のカスタム識別子を使用するには、[LiveRamp との ID 同期](https://docs.liveramp.com/identity/en/getting-started-with-liveramp-identity.html)が必要です。
 {% endalert %}
 
 ### ステップ 4:変数を設定する
 
-次に、アプリで提供される実行ステップのワークシートで、ジョブの変数を設定する。これには、ターゲット・データベース、関連テーブル（入力データ、メトリクス、ロギング）、出力テーブル名の定義などの詳細が含まれる。完全なウォークスルーは、[LiveRampを参照のこと：](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html#specify-the-variables-43-150727) 変数を指定する。
+次に、アプリに用意されている Execution Step ワークシートでジョブの変数を設定します。これには、ターゲット・データベース、関連テーブル（入力データ、メトリクス、ロギング）、出力テーブル名の定義などの詳細が含まれる。完全なウォークスルーは、[LiveRampを参照のこと：変数 ](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html#specify-the-variables-43-150727) を指定します。
 
 ### ステップ 5: PII解決のためのメタデータテーブルを作成する
 
-変数が設定できたので、PII解決のためのメタデータテーブルを作成する。これは、関係する識別子のカテゴリーに基づいて実行される特定のジョブタイプの詳細を示す。完全なウォークスルーは、[LiveRampを参照のこと：メタデータ・テーブルの作成](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html#create-the-metadata-table-43).
+変数が設定できたので、PII解決のためのメタデータテーブルを作成する。これは、関係する識別子のカテゴリーに基づいて実行される特定のジョブタイプの詳細を示す。完全なウォークスルーは、[LiveRampを参照のこと：メタデータテーブル ](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html#create-the-metadata-table-43) を作成します。
 
 ### ステップ 6: ID解決操作を実行する
 
-最後に、ID解決操作を実行する。完全なウォークスルーは、[LiveRampを参照のこと：アイデンティティ解決操作を実行する](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html#perform-the-identity-resolution-operation).
+最後に、ID解決操作を実行する。完全なウォークスルーは、[LiveRampを参照のこと：ID 解決操作を実行します](https://docs.liveramp.com/identity/en/perform-identity-resolution-in-snowflake.html#perform-the-identity-resolution-operation)。
 
 {% tabs ローカル %}
 {% tab 入力例 %}
@@ -112,7 +112,7 @@ $output_table_name
 
 ### 次のステップ
 
-データがRampIDの専用エンコーディングに仮名化されたことで、RampIDベースのテーブルをライブランプのマネージド・アクティベーション・アプリケーションと共有することができ、主要な広告プラットフォーム・パートナーへの合理的なフルフィルメントが可能になる。アクティベーション・アプリケーションには、セグメンテーションを追加したり、下流のデスティネーション・パートナーを選択／設定するための、ビジネス・ユーザー・フレンドリーなインターフェイスが含まれている。アプリケーションの詳細については、LiveRampのアカウントチームまたは[snowflake@liveramp.com](mailto:snowflake@liveramp.com) までお問い合わせいただきたい。
+データが RampID の専用エンコードに仮名化されたので、RampID ベースのテーブルを LiveRamp のマネージドアクティベーションアプリケーションと共有して、主要な広告プラットフォームパートナーに対して効率的なフルフィルメントを実現することができます。アクティベーションアプリケーションには、追加のセグメンテーションと、ダウンストリーム宛先パートナーを選択/設定するための、ビジネスユーザーにとって使いやすいインターフェイスが含まれています。このアプリケーションの詳細については、LiveRamp アカウントチームまたは [snowflake@liveramp.com](mailto:snowflake@liveramp.com) までお問い合わせください。
 
 ## トラブルシューティング
 
@@ -120,17 +120,17 @@ $output_table_name
 より具体的な問題や質問がある場合は、[martech@liveramp.com](mailto:martech@liveramp.com) まで連絡を。
 {% endalert %}
 
-### 雪片地域
+### Snowflake のリージョン
 
-現在、このアプリケーションは、米国を拠点とする以下の地域でのみ利用できる：
+現在、このアプリケーションは次の米国のリージョンでのみ使用できます。
 
   - aws-us-east-1：POA18931
   - aws-us-west-2：FAA28932
   - azure-east-us-2：BL60425
 
-### プライバシーとコラムの価値
+### プライバシーと列値
 
-このプロセスでは、一意な値があるかどうか、行ごとにすべての列値の組み合わせを評価する。特定のカラム値の組み合わせが3回以下しか出現しない場合、それらのカラム値を含む行はマッチせず、出力テーブルには返されない。同様に、プライバシーを確保するために、LiveRampサービスはカラム値の組み合わせの一意性を評価し、ファイルの行の5％以上がまれな組み合わせのためにマッチ不可能になった場合、ジョブは失敗する。
+このプロセスでは、一意な値があるかどうか、行ごとにすべての列値の組み合わせを評価する。特定のカラム値の組み合わせが3回以下しか出現しない場合、それらのカラム値を含む行はマッチせず、出力テーブルには返されない。同様に、プライバシーを確保するために、LiveRamp サービスは列値の組み合わせの一意性を評価します。これにより、稀な組み合わせが原因でファイルの行の5 % 以上が照合不可能になった場合にはジョブが失敗するようになります。
 
 ### 過去のデータ
 
@@ -138,12 +138,12 @@ Snowflakeの過去データは2019年4月まで遡るが、2019年8月以前の
 
 ### スピード、パフォーマンス、コスト
 
-クエリーのスピードとコストは、使用する倉庫のサイズに依存する。ウェアハウスのサイズを選択する際には、データアクセスのニーズを考慮すること。
+クエリの速度とコストは、使用するウェアハウスのサイズによって異なります。ウェアハウスのサイズを選択するときには、データアクセスの必要性を考慮してください。
 
 ### Braze Benchmarks
 
 ベンチマークでは、Snowflake Data Exchangeで直接利用できる業界標準と自社の指標を比較することができる。
 
-### ブレーク対ブレークブレークしない変更
+### 破壊的変更と非破壊的変更
 
-統合に影響を及ぼす可能性のある変化に注意すること。画期的な変更には、アナウンスと移行期間が設けられる。
+統合に影響を及ぼす可能性のある変化に注意すること。破壊的な変更の前に発表と移行期間を設けます。
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics.md
index 78fb188bcc8..93b460e48ae 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics.md
@@ -24,24 +24,24 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/analytics/kubit/
 - name: NPAW
   url: /docs/partners/data_and_infrastructure_agility/analytics/npaw/
-- name: スノープラウ
+- name: Snowplow
   url: /docs/partners/data_and_infrastructure_agility/analytics/snowplow/
-- name: クラリサイト
+- name: Clarisights
   url: /docs/partners/data_and_infrastructure_agility/analytics/clarisights/
-- name: アクショナブル.me
+- name: actionable.me
   url: /docs/partners/data_and_infrastructure_agility/analytics/actionableme/
 - name: ThoughtSpot
   url: /docs/partners/data_and_infrastructure_agility/analytics/thoughtspot/
-- name: 神童
+- name: Wunderkind
   url: /docs/partners/data_and_infrastructure_agility/analytics/wunderkind/
-- name: テルス
+- name: Tellius
   url: /docs/partners/data_and_infrastructure_agility/analytics/tellius/
-- name: コンテンツスクエア
+- name: Contentsquare
   url: /docs/partners/data_and_infrastructure_agility/analytics/contentsquare/
-- name: マーキュリー
+- name: Merkury
   url: /docs/partners/data_and_infrastructure_agility/analytics/merkury/
 - name: SalesWings
   url: /docs/partners/data_and_infrastructure_agility/analytics/saleswings/
-- name: スキューバ
+- name: Scuba
   url: /docs/partners/data_and_infrastructure_agility/analytics/scuba/
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/actionableme.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/actionableme.md
index 7b88d7df031..02d4b148374 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/actionableme.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/actionableme.md
@@ -1,7 +1,7 @@
 ---
-nav_title: アクショナブル・ドット・ミー
-article_title: アクショナブル・ドット・ミー
-description: "この参考記事では、Brazeと独自のソフトウェアおよびプロセスであるactionable.meとのパートナーシップについて概説している。"
+nav_title: actionable.me
+article_title: actionable.me
+description: "このリファレンス記事では、Braze と actionable.me のパートナーシップについて説明します。actionable.me は、Braze への投資を今すぐ最大限に引き出すことができる専用ソフトウェアおよびプロセスです。"
 alias: /partners/actionableme/
 page_type: partner
 search_tag: Partner
@@ -10,26 +10,26 @@ search_tag: Partner
 
 # actionable.me
 
-> [actionable.me][2]データおよびCRMエージェンシーであるMassive Rocketのチームによって構築された、CRMプログラムを実行するための標準化され、自動化されたアプローチであり、Brazeの顧客が迅速、一貫性、予測可能な価値を得られるように設計されたツールとプロセスを提供する。 
+> [actionable.me][2] は、データおよび CRM エージェンシーである Massive Rocket のチームによって開発された、CRM プログラムを実行するための標準化および自動化されたアプローチです。Braze のお客様に、迅速かつ一貫性があり予測可能な方法で価値を実現するためのツールとプロセスを提供します。 
 
-Brazeとactionable.me の統合により、Brazeの活用状況をモニターするサービスを展開することができる。ツールとプロセスを組み合わせることで、CRMのパフォーマンスを迅速にベンチマークし、新たな機会を特定し、より良いパフォーマンスを実現する方法を提案する。
+Braze と actionable.me の統合により、Braze の使用状況を監視するためのサービスをデプロイできます。ツールとプロセスを組み合わせることで、CRM のパフォーマンスが迅速にベンチマークされ、新しい機会が特定され、パフォーマンスの向上に関する推奨事項が提供されます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | --- | --- |
-| actionable.me アカウント | このパートナーシップを利用するには、actionable.me のアカウントが必要である。 |
+| actionable.me アカウント | このパートナーシップを活用するには、actionable.me アカウントが必要です。 |
 | Braze REST API キー | 次のセクションに記載されている権限を持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][1]。エンドポイントは、インスタンスのBraze URLに依存する。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-Brazeとactionable.me を統合するには、actionable.me プラットフォームを設定し、Braze APIキーをBrazeで作成し、actionable.me ダッシュボードで設定する必要がある。
+Braze とactionable.me を統合するには、actionable.me プラットフォームを設定し、Braze API キーを Braze で作成して actionable.me ダッシュボードで設定する必要があります。
 
 ### ステップ 1:BrazeのAPIキーを作成する
 
-Brazeで、**Settings**>**API Keysに**移動する。**Create New API Keyを**選択し、以下のパーミッションが追加されていることを確認する：
+Braze で \[**設定**] > \[**API キー**] の順に移動します。\[**新しい API キーを作成**] を選択し、次の権限が追加されていることを確認します。
 
 - `campaigns.list`
 - `campaigns.data_series`
@@ -49,18 +49,18 @@ Brazeで、**Settings**>**API Keysに**移動する。**Create New API Keyを**
 - `kpi.uninstalls.data_series`
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、**Developer Console**>**API Settingsから**APIキーを作成できる。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**開発者コンソール**] > \[**API 設定**] から API キーを作成できます。
 {% endalert %}
 
 ### ステップ2:actionable.me チームに情報を提供する
 
-統合を完了するには、REST APIキーと[RESTエンドポイントURLを][1] actionable.me オペレーション・チームに提供する必要がある。actionable.me が接続を確立し、セットアップ完了後に連絡を取り、インサイトの共有を開始する。
+統合を完了するには、REST API キーと [REST エンドポイント URL][1] を actionable.me オペレーションチームに提供する必要があります。その後 actionable.me が接続を確立し、設定完了後に連絡を取り、インサイトの共有を開始します。
 
 ![actionable.me 運営チームが設定するactionable.me 「プラットフォームの追加」ページ。][5]
 
 ## トラブルシューティング
 
-actionable.me またはMassive Rocketチームまでご連絡を。[massiverocket.com][3]
+その他のサポートについては、actionable.me またはMassive Rocket チーム ([info@massiverocket.com][3]) にお問い合わせください。
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
 [2]: https://actionable.me
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/adikteev.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/adikteev.md
index c34e046ea7f..d0cdf78c59d 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/adikteev.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/adikteev.md
@@ -1,6 +1,6 @@
 ---
-nav_title: アディクテフ
-article_title: アディクテフ解約予測
+nav_title: Adikteev
+article_title: Adikteev 解約予測
 description: "この参考記事では、Brazeと、解約予測とフルサービスのアプリリターゲティングを組み合わせたユーザーリテンションエンジンであるAdikteevの提携について概説している。"
 alias: /partners/adikteev/
 page_type: partner
@@ -8,33 +8,33 @@ search_tag: Partner
 
 ---
 
-# アディクテフ解約予測
+# Adikteev 解約予測
 
-> [Adikteevは](https://www.adikteev.com/churn-prediction)、解約予測とフルサービスのアプリリターゲティングを組み合わせたユーザーリテンションエンジンである。
+> [Adikteev](https://www.adikteev.com/churn-prediction) は、解約予測とサービス全般を取り扱うアプリリターゲティングを組み合わせたユーザーリテンションエンジンです。
 
-BrazeとAdikteevの統合により、Braze CRMキャンペーン内でAdikteevの解約予測技術を活用し、リスクの高いユーザーセグメントを優先的にターゲットにすることで、ユーザーリテンションを高めることができる。
+Braze と Adikteev の統合により、Braze CRM キャンペーン内で Adikteev の解約予測技術を活用し、リスクの高いユーザーセグメントを優先的にターゲットにすることで、ユーザーリテンションを高めることができます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | --- | --- |
-| アディクテフのアカウント | このパートナーシップを利用するには、アディクティーフのアカウントが必要だ。 |
-| Braze REST API キー | パーミッションを持つBraze REST APIキー`users.track` 。<br><br> これは、Brazeダッシュボードの**「設定**」>「**APIと識別子**」から作成できる。 |
+| Adikteev アカウント | このパートナーシップを活用するには、Adikteev アカウントが必要です。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定**」>「**APIと識別子**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)。エンドポイントは、インスタンスのBraze URLに依存する。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
 {% tabs %}
-{% tab 観客のフィルタリング %}
-解約リスクに基づいて視聴者セグメントを絞り込む。<br> アディクテフから送信されるカスタム属性の名前と値は設定可能である。
+{% tab オーディエンスフィルタリング %}
+解約リスクに基づいてオーディエンスセグメントを絞り込みます。<br> Adikteev により送信されるカスタム属性の名前と値は設定可能です。
 
-![] （{% image_buster /assets/img/adikteev/audience.png %} ）。
+![Adikteev により送信されるカスタム属性をオーディエンスセグメントフィルターとして使用する例。]({% image_buster /assets/img/adikteev/audience.png %})
 {% endtab %}
 {% tab メッセージ・ターゲティング %}
 受信者の解約リスクに基づいてBrazeメッセージングキャンペーンをカスタマイズ。
 
-![] （{% image_buster /assets/img/adikteev/campaign.png %} ）。
+![Adikteev により送信されるカスタム属性をキャンペーンターゲティングフィルターとして使用する例。]({% image_buster /assets/img/adikteev/campaign.png %})
 {% endtab %}
 {% endtabs %}
 
@@ -42,29 +42,29 @@ BrazeとAdikteevの統合により、Braze CRMキャンペーン内でAdikteev
 
 ### ステップ1:アプリのイベントストリームを共有する
 
-アプリ利用者の解約予測を開始するには、Adikteevがモバイル測定プラットフォームからイベントのポストバックをオンにする必要がある。[アディクティーフのサポートサイトの](https://help.adikteev.com/hc/en-us/sections/8185123408914-Data-stream-activation)ガイドラインに従って設定する。
+アプリオーディエンスの解約予測を開始するには、Adikteev でモバイル計測プラットフォームからのイベントのポストバックをオンにする必要があります。これは、[Adikteev サポート Web サイト](https://help.adikteev.com/hc/en-us/sections/8185123408914-Data-stream-activation)のガイドラインに従って設定してください。
 
 ### ステップ2:Braze REST APIキーを作成する
 
-Brazeで、**Settings**>**APIs and Identifiersに**移動する。**Create New API Keyを**選択し、任意のAPI Key Nameを入力し、以下のパーミッションが追加されていることを確認する：
+Braze で \[**設定**] > \[**API と識別子**] に移動します。\[**新しい API キーを作成**] を選択して使用する API キー名を入力し、次の権限が追加されていることを確認します。
 
 - `users.track`
 
-### ステップ3:アディクテフ・チームに情報を提供する
+### ステップ3:Adikteev チームに情報を提供する
 
-統合を完了するには、REST APIキーとRESTエンドポイントURLをAdikteevアカウントマネージャーに提供する必要がある。Adikteevは接続を確立し、セットアップ完了後、統合を確認するためにあなたに連絡する。
+統合を完了するには、REST API キーと REST エンドポイント URL を Adikteev アカウントマネージャーに提供する必要があります。Adikteevは接続を確立し、セットアップ完了後、統合を確認するためにあなたに連絡する。
 
 ## バッチ処理とレート制限
 
-`user.track` エンドポイントは、ユーザーの詳細を更新するために使用される。エンドポイントのレート制限、リクエストのバッチ処理、リクエストの詳細については、[APIのドキュメントを]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)参照のこと。
+`user.track` エンドポイントは、ユーザーの詳細を更新するために使用されます。エンドポイントのレート制限、リクエストのバッチ処理、リクエストの詳細については、[API のドキュメント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)を参照してください。
 
 {% alert tip %}
-APIコールは、全体的なAPIコールの回数を減らすために、変更されたデータを更新するためだけに行うべきであることを覚えておいてほしい。言い換えれば、解約セグメントが変更されたユーザーだけを更新する。
+API 呼び出しの総数を削減するため、変更されたデータを更新する目的でのみ API 呼び出しを実行すべきであることを覚えておいてください。つまり、解約セグメントが変更されたユーザーだけを更新してください。
 {% endalert %}
 
 ## ユーザーとデバイスの識別子
 
-Brazeのユーザープロファイルは、あらゆるタイプのユーザーまたはデバイス識別子に関連付けることができる。Adikteevの場合、解約セグメント情報を正しく送信するために、MMPとBrazeのユーザープロファイルの間で共通の識別子を見つける必要がある。
+Braze のユーザープロファイルは、任意のタイプのユーザーまたはデバイス識別子に関連付けることができます。使用できるオプションのリストは、データ収集を Braze とどのように統合したかに応じて異なります。Adikteev では、解約セグメント情報を正しく送信するために、MMP と Braze のユーザープロファイルの間で共通の識別子を見つける必要があります。
 
 ## データの保持と削除
 
@@ -72,11 +72,11 @@ Brazeのユーザープロファイルは、あらゆるタイプのユーザー
 
 プロファイル属性を削除するには、`null` に設定する。
 
-## リクエスト・ペイロード
+## リクエストペイロード
 
-アディクテフからブレイズに送られるペイロードはカスタマイズ可能で、顧客のニーズに合わせて設定できる。これには、使用される識別子、カスタム属性の名前、AdikteevがBrazeで新しいユーザーを作成できるか、既存のユーザーを更新するだけかを設定することが含まれる。
+Adikteev から Braze に送信されるペイロードはカスタマイズ可能であり、顧客のニーズに合わせて設定できます。これには、使用する識別子、カスタム属性の名前、Adikteev が Braze で新しいユーザーを作成できるかまたは既存のユーザーを更新するだけかを設定することが含まれます。
 
 
 ## サポートとトラブルシューティング
 
-統合に関するご質問や、ユースケースに関するサポートについては、Adikteevのアカウントマネージャーにお問い合わせいただきたい。
+統合に関するご質問や、ユースケースに関するサポートについては、Adikteev アカウントマネージャーにお問い合わせください。
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude.md
index d5b3ad34e8f..2edf5581c74 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude.md
@@ -4,20 +4,20 @@ noindex: true
 alias: /partners/data_and_infrastructure_agility/analytics/amplitude_for_currents/
 layout: dev_guide
 guide_top_header: "Amplitude"
-guide_top_text: "Amplitudeは、強固な商品と行動分析を通じて成長を牽引することができます。強力なターゲティングを知らせるために、ユーザー Segmentの間でどのような行動や形質が一般的であるかを徹底的に把握する。"
-description: "このランディングページには、AmplitudeのCurrents、「Amplitudeのおすすめ」、「Amplitudeと接続されたコンテンツ」を活用する方法など、あらゆるものが掲載されています。"
+guide_top_text: "Amplitude は、堅牢な製品分析と行動分析により、企業の成長を支援しています。ユーザーセグメントに共通する行動や特徴を徹底的に把握し、強力なターゲティングを可能にします。"
+description: "このランディングページは、Amplitude for Currents や Amplitude Recommend の情報、また Amplitude とコネクテッドコンテンツを活用する方法など、Amplitude に関するあらゆる情報のホームページです。"
 
 guide_featured_list:
-- name: Amplitudeコホートインポート
+- name: Amplitude コホートインポート
   link: /docs/partners/data_and_infrastructure_agility/cohort_import/amplitude/
   image: /assets/img/braze_icons/users-01.svg
 - name: Amplitude for Currents
   link: /docs/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents/
   image: /assets/img/braze_icons/building-01.svg
-- name: Amplitudeの推奨
+- name: Amplitude Recommend
   link: /docs/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences/
   image: /assets/img/braze_icons/lightbulb-02.svg
-- name: Amplitudeと接続内容
+- name: Amplitude とコネクテッドコンテンツ
   link: /docs/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api/
   image: /assets/img/braze_icons/user-circle.svg
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences.md
index b9a23739389..9c45350b201 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences.md
@@ -10,60 +10,60 @@ search_tag: Partner
 
 ---
 
-# [![ブレイズ・ラーニングのコース]](https://learning.braze.com/amplitude-integration-with-braze)([{% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/amplitude-integration-with-braze){: style="float:right;width:120px;border:0;" class="noimgborder"}振幅
+# [![Braze ラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/amplitude-integration-with-braze){: style="float:right;width:120px;border:0;" class="noimgborder"}Amplitude
 
-> [Amplitudeは](https://amplitude.com/)製品分析とビジネスインテリジェンスのプラットフォームである。
+> [Amplitude](https://amplitude.com/) は製品分析およびビジネスインテリジェンスプラットフォームです。
 
-BrazeとAmplitudeの双方向統合により、[AmplitudeのCohorts]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/amplitude/)、ユーザー特性、イベントをBrazeに[インポート]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/amplitude/)し、将来のキャンペーンやCanvasesでユーザーをターゲットにできるセグメントを作成できる。また、Braze Currentsを活用して[、BrazeのイベントをAmplitudeにエクスポート]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents/#data-export-integration)し、製品やマーケティングデータの詳細な分析を行うこともできる。
+Braze と Amplitude の双方向統合により、[Amplitude コホート]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/amplitude/)、ユーザー特性、およびイベントを Braze にインポートし、将来のキャンペーンやキャンバスでユーザーをターゲッティングできるセグメントを作成ができます。また、Braze Currents を利用して [Braze イベントを Amplitude にエクスポートし]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents/#data-export-integration)、製品データやマーケティングデータの詳細な分析を行うこともできます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| 振幅アカウント | このパートナーシップを利用するには、[Amplitudeアカウントが](https://amplitude.com/)必要である。 |
-| Currents | データをAmplitudeにエクスポートするには、アカウントに[Braze Currentsを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents)設定する必要がある。 |
+| Amplitude アカウント | このパートナーシップを活用するには、[Amplitude アカウント](https://amplitude.com/)が必要です。 |
+| Currents | Amplitude にデータを再度エクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2} 
 
 ## 統合を選択する 
 
-AmplitudeとBrazeは2つの異なる統合方法を提供している。以下のドキュメントを読んで、どの方法があなたのニーズに合うか判断してほしい：
+AmplitudeとBrazeは2つの異なる統合方法を提供している。次のドキュメントを参照して、ニーズに適した方法を判断します。
 
-- ブレイズ・イベント・ストリーミングAmplitudeの生のイベントデータをそのままBrazeに転送できる統合。
-- [コホート輸入]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/amplitude/)：AmplitudeのコホートをBrazeに転送できる統合。
+- Braze イベントストリーミング:Amplitudeの生のイベントデータをそのままBrazeに転送できる統合。
+- [コホートインポート]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/amplitude/):Amplitude のコホートを Braze に転送できる統合。
 
-## ブレイズ・イベント・ストリーミング
+## Braze イベントストリーミング
 
 ### 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
 | Braze REST API キー | すべての権限を持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント | \[あなたのRESTエンドポイントURL][1].エンドポイントは、インスタンスのBraze URLに依存する。 |
-| Brazeアプリの識別子 | Amplitudeイベントを受け取るアプリの識別子。これは、**Braze Dashboard > Developer Console > Settingsで**確認できる。 |
+| Braze RESTエンドポイント | \[REST エンドポイント URL][1]。エンドポイントは、インスタンスのBraze URLに依存する。 |
+| Brazeアプリの識別子 | Amplitudeイベントを受け取るアプリの識別子。これは、**Braze ダッシュボード > \[開発者コンソール] > \[設定]** で確認できます。 |
 
 ### 振幅の設定
 
-1. Amplitudeで**Data Destinationsに**移動し、"Braze - Event Stream "を検索する。
-2. シンク名を入力し、**Create Syncを**クリックする。
-3. **編集]**をクリックし、Braze REST APIエンドポイント、REST APIキー、およびBrazeアプリ識別子を入力する。
+1. Amplitude で \[**Data Destinations**] に移動し、\[Braze - Event Stream] を探します。
+2. 同期名を入力し、\[**Create Sync**] をクリックします。
+3. \[**Edit**] をクリックし、Braze REST API エンドポイント、REST API キー、および Braze アプリ識別子を入力します。
 4. イベント送信フィルターを使用して、送信するイベントを選択する。すべてのイベントを送信することもできるが、Amplitudeでは最も重要なイベントを選択することを推奨している。 
 5. 完了したら、デスティネーションを有効にして保存する。 
 
-この統合の詳細については、[Braze Event Streamingを](https://www.docs.developers.amplitude.com/data/destinations/braze/)参照のこと。
+この統合の詳細については、「[Braze イベントストリーミング](https://www.docs.developers.amplitude.com/data/destinations/braze/)」を参照してください。
 
 ## ユーザーの特性と計算を同期させる
 
-Audienceを使用して、ユーザーのプロパティと計算をカスタム属性としてBrazeに送信する。過去90日間にアクティブであったユーザのユーザ・プロパティまたは計算されたプロパティを同期することができる。
+Audience を使用して、ユーザープロパティと計算をカスタム属性として Braze に送信します。過去90日間でアクティブであったユーザーのユーザープロパティまたは計算プロパティを同期できます。
 
 ユーザーのプロパティや計算が更新されると、Amplitudeは、そのユーザーのプロパティや計算と同じ名前のBrazeのカスタム属性を更新する。
 
 ユーザー形質と計算の同期は、Braze内にまだ存在しないユーザーIDに対して新しいユーザーを作成する。計算とユーザーの特徴は、ユーザーIDを使用してのみ同期できる。
 
-[プロパティ、レコメンデーション、コホートをサードパーティのデスティネーションに同期する](https://help.amplitude.com/hc/en-us/articles/360060055531)方法については、Amplitudeのドキュメントを参照のこと。
+[プロパティ、レコメンデーション、コホートをサードパーティの宛先に同期する](https://help.amplitude.com/hc/en-us/articles/360060055531)方法の詳細については、Amplitudeのドキュメントを参照してください。
 
 #### ユーザー・プロパティと計算を同期させる方法
 
-Amplitude Audiencesで、**Syncs > Create Syncを**選択する。
+Amplitude Audiences で、**\[Syncs] > \[Create Sync]** を選択します。
 
 ![]({% image_buster /assets/img/amplitude11.png %})
 
@@ -72,22 +72,22 @@ Amplitude Audiencesで、**Syncs > Create Syncを**選択する。
 {% tabs %}
 {% tab ユーザー・プロパティを同期する %}
 
-**User Propertyを**選択し、同期するユーザ・プロパティを選択する。
+\[**User Propertを**] を選択し、同期するユーザープロパティを選択します。
 
 ![]({% image_buster /assets/img/amplitude7.png %})
 
-次に、ユーザ・プロパティの同期先を選択する。
+次に、ユーザープロパティを同期する宛先を選択します。
 
 ![]({% image_buster /assets/img/amplitude8.png %})
 
 最後に、同期の頻度を決める。
 
-![] （{% image_buster /assets/img/amplitude9.png %} ）。
+![ケイデンスを One-time Sync または Scheduled Sync として定義する。]({% image_buster /assets/img/amplitude9.png %})
 
 {% endtab %}
 {% tab 同期計算 %}
 
-**計算を**選択し、同期させたい計算を選択する。
+\[**Computetion**] を選択し、同期する計算を選択します。
 
 ![]({% image_buster /assets/img/amplitude10.png %})
 
@@ -97,11 +97,11 @@ Amplitude Audiencesで、**Syncs > Create Syncを**選択する。
 
 最後に、同期の頻度を決める。
 
-![] （{% image_buster /assets/img/amplitude9.png %} ）。
+![ケイデンスを One-time Sync または Scheduled Sync として定義する。]({% image_buster /assets/img/amplitude9.png %})
 
 {% endtab %}
 {% endtabs %}
 
 ## AmplitudeユーザープロファイルAPIエンドポイント
 
-Connected Contentで使用できる一般的なAmplitude APIエンドポイントを確認するには、専用の[Amplitude APIドキュメントを]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api/)参照のこと。
+コネクテッドコンテンツで使用できる一般的な Amplitude API エンドポイントのいくつかを確認するには、専用の [Amplitude API ドキュメント]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api/)を参照してください。
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents.md
index 4c4e3daed4d..57a3728abd2 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents.md
@@ -9,26 +9,26 @@ search_tag: Partner
 
 ---
 
-# [![Braze Learning course]](https://learning.braze.com/amplitude-integration-with-braze)([{% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/amplitude-integration-with-braze){: style="float:right;width:120px;border:0;" class="noimgborder"}電流に対する振幅
+# [![Braze ラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/amplitude-integration-with-braze){: style="float:right;width:120px;border:0;" class="noimgborder"}Amplitude for Currents
 
-> [Amplitudeは](https://amplitude.com/)製品分析とビジネスインテリジェンスのプラットフォームである。
+> [Amplitude](https://amplitude.com/) は製品分析およびビジネスインテリジェンスプラットフォームです。
 
-BrazeとAmplitudeの双方向統合により、[AmplitudeのCohorts]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences/)、ユーザー特性、イベントをBrazeに[同期させる]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences/)ことができる。また、Braze Currentsを活用して[BrazeのイベントをAmplitudeにエクスポート](#data-export-integration)し、製品やマーケティングデータの詳細な分析を行うこともできる。
+Braze と Amplitude の双方向統合により、[ Amplitude コホート]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences/)、ユーザー特性、およびイベントを Braze に同期し、また Braze Currents を使用して [Amplitude に Braze イベントをエクスポートして](#data-export-integration)、製品データとマーケティングデータのより深い分析を実行できます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| 振幅アカウント | このパートナーシップを利用するには、[Amplitudeアカウントが](https://amplitude.com/)必要である。 |
-| Currents | データをAmplitudeにエクスポートするには、アカウントに[Braze Currentsを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents)設定する必要がある。 |
+| Amplitude アカウント | このパートナーシップを活用するには、[Amplitude アカウント](https://amplitude.com/)が必要です。 |
+| Currents | Amplitude にデータを再度エクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2} 
 
 ## データ・エクスポートの統合
 
-BrazeからAmplitudeにエクスポートできるイベントとイベントプロパティの完全なリストは、以下のセクションにある。Amplitudeに送信されるすべてのイベントには、AmplitudeのユーザーIDとしてユーザーの`external_user_id` 。ブレーズ特有のイベント・プロパティは、Amplitudeに送られるデータの`event_properties` ・キーの下に送られる。
+BrazeからAmplitudeにエクスポートできるイベントとイベントプロパティの完全なリストは、以下のセクションにある。Amplitude に送信されるすべてのイベントには、ユーザーの`external_user_id` が Amplitude ユーザー ID として含まれます。Braze 固有のイベントプロパティは、Amplitude に送信されるデータの`event_properties` キーで送信されます。
 
 {% alert important %}
-この機能を使うには、AmplitudeのユーザーIDとBrazeの外部IDが一致していなければならない。
+この機能を使用するには、Amplitude のユーザー IDが Braze の external ID に一致している必要があります。
 {% endalert %}
 
 Brazeがイベントデータを送信するのは、`external_user_id` を設定したユーザーか、`device_id` を設定した匿名ユーザーのみである。匿名ユーザーの場合は、SDKでAmplitudeのデバイスIDとBrazeのデバイスIDを同期させる必要がある。以下に例を示します。
@@ -37,50 +37,50 @@ Brazeがイベントデータを送信するのは、`external_user_id` を設
 amplitude.setDeviceId(Appboy.getInstance(context).getDeviceId();)
 ```
 
-Amplitudeには2種類のイベントをエクスポートできる：[メッセージ](#supported-currents-events)送信に直接関連するBrazeイベント、およびプラットフォームを通じて追跡されるセッション、カスタムイベント、購入などのその他のアプリまたはウェブサイトのアクティビティを含む[顧客行動イベントから](#supported-currents-events)構成される[メッセージエンゲージメントイベント](#supported-currents-events)。すべてのレギュラー・イベントのプレフィックスは`[Appboy]` で、すべてのカスタム・イベントのプレフィックスは`[Appboy] [Custom Event]` である。カスタム・イベントと購入イベントのプロパティには、それぞれ`[Custom event property]` と`[Purchase property]` というプレフィックスが付く。
+Amplitudeには2種類のイベントをエクスポートできる：[メッセージエンゲージメントイベント](#supported-currents-events) (メッセージ送信に直接関連する Braze イベントで構成される) と、[顧客行動イベント](#supported-currents-events) (セッション、カスタムイベント、プラットフォーム経由で追跡された購入などのその他のアプリまたは Web サイトアクティビティを含む) です。すべての標準的なイベントには `[Appboy]` が接頭辞として付加され、すべてのカスタムイベントには `[Appboy] [Custom Event]` が付加されます。カスタムイベントプロパティの接頭辞は `[Custom event property]`、購入イベントプロパティの接頭辞は `[Purchase property]` です。
 
-名前が付けられBrazeにインポートされたすべてのコホートには、`[Amplitude]` が先頭に、`cohort_id` が末尾に付けられる。つまり、`cohort_id` "abcd1234 "を持つ "TEST_COHORT "という名前のコホートは、Brazeフィルターでは`[Amplitude] TEST_COHORT: abcd1234` というタイトルになる。
+名前が付けられ Braze にインポートされるすべてのコホートには、接頭辞として `[Amplitude]` が、接尾辞として`cohort_id` が付加されます。これは、`cohort_id` が「abcd1234」で名前が「TEST_COHORT」のコホートが、Braze フィルターでは `[Amplitude] TEST_COHORT: abcd1234` というタイトルになることを意味します。
 
 その他のイベントの種類にアクセスする必要がある場合は、アカウントマネージャーに問い合わせるか、[サポートチケット][support]を開いてください。
 
-### ステップ1:Brazeで振幅統合を設定する 
+### ステップ1:Braze で Amplitude 統合を設定する 
 
 Amplitudeで、AmplitudeエクスポートAPIキーを探す。
 
 {% alert warning %}
-Amplitude API Keyを最新の状態に保つ。コネクタの認証情報が期限切れになると、コネクタはイベントの送信を停止する。この状態が**48時間**以上続くと、コネクタのイベントは削除され、データは永久に失われる。
+Amplitude API Keyを最新の状態に保つ。コネクターの認証情報が期限切れになると、コネクターはイベントの送信を停止します。この状態が**48時間**以上続くと、コネクタのイベントは削除され、データは永久に失われる。
 {% endalert %}
 
-### ステップ2:ブレイズ電流を作る
+### ステップ2:Braze Current を作成する
 
-Brazeで、**Current > + Create Current > Create Amplitude Exportに**移動する。リストにあるフィールドに、統合名、連絡先のEメール、AmplitudeエクスポートAPIキー、およびAmplitudeリージョンを入力する。次に、追跡したいイベントを選択する。利用可能なイベントのリストが提供される。最後に、**Launch Currentを**クリックする。
+Braze で **\[Currents] > \[+ Currents を作成] > \[Amplitude エクスポートを作成]** に移動します。統合名、連絡先メール、Amplitude エクスポート API キー、および Amplitude リージョンを、リストされているフィールドに入力します。次に、追跡したいイベントを選択する。利用可能なイベントのリストが提供される。最後に \[**Currents を起動**] をクリックします。
 
 {% alert note %}
-Braze CurrentsからAmplitudeに送信されたイベントは、Amplitudeのイベントボリュームクォータにカウントされる。
+Braze Currents から Amplitude に送信されたイベントは、Amplitude イベントボリューム割り当ての対象となります。
 {% endalert %}
 
-![ブレイズ振幅電流のページ。このページには、インテグレーション名、コンタクトEメール、APIキー、米国地域のフィールドがある。Currentsページの下半分には、送信可能なCurrentsイベントがリストアップされている。]({% image_buster /assets/img/amplitude4.png %})
+![Braze Amplitude Currents ページ。このページには、統合名、連絡先メール、APIキー、US リージョンのフィールドがある。Currents ページの下半分には、送信可能なCurrents イベントが表示されている。]({% image_buster /assets/img/amplitude4.png %})
 
-{% tab 備考 %}
-詳しくはAmplitudeの[統合ドキュメントを](https://amplitude.zendesk.com/hc/en-us/articles/115000217351-Appboy-Amplitude-Integration#how-to-set-up-and-use-the-integration)チェックしてほしい。
+{% tab 注 %}
+詳細については、Amplitude の[統合に関するドキュメント](https://amplitude.zendesk.com/hc/en-us/articles/115000217351-Appboy-Amplitude-Integration#how-to-set-up-and-use-the-integration)を参照してください。
 {% endtab %}
 
 ## レート制限
 
-電流はAmplitudeのHTTP APIに接続するが、このAPIには[、](https://developers.amplitude.com/docs/http-api-v2#upload-limit)1デバイスあたり30イベント/秒という[レート制限と](https://developers.amplitude.com/docs/http-api-v2#upload-limit)、1デバイスあたり500Kイベント/日という文書化されていない制限がある。これらのしきい値を超えた場合、AmplitudeはCurrentsを通じて記録されたイベントをスロットルする。インテグレーション内のデバイスがこのレート制限を超えると、すべてのデバイスからのイベントがAmplitudeに表示されるタイミングが遅れることがある。
+電流はAmplitudeのHTTP APIに接続するが、このAPIには、1デバイスあたり30イベント/秒という[レート制限と](https://developers.amplitude.com/docs/http-api-v2#upload-limit)、1デバイスあたり500Kイベント/日という文書化されていない制限がある。これらのしきい値を超えた場合、Amplitude はCurrents を通じて記録されるイベントを調整します。インテグレーション内のデバイスがこのレート制限を超えると、すべてのデバイスからのイベントがAmplitudeに表示されるタイミングが遅れることがある。
 
-デバイスは、通常であれば、30イベント/秒または500Kイベント/日を超えて報告すべきではなく、このようなイベントパターンは、誤設定された統合によってのみ発生するはずである。このような遅延を回避するには、SDKインテグレーションが、SDKインテグレーション・インストラクションで指定されているように、通常の速度でイベントをレポートすることを確認し、1つのデバイスに対して多くのイベントを生成する自動テストの実行を控えること。
+通常の状況では、デバイスが報告するレポートの数は、30イベント/秒または50万イベント/日を超えてはなりません。このようなイベントパターンは、設定の誤りがある場合にのみ発生します。このような遅延を回避するには、SDKインテグレーションが、SDKインテグレーション・インストラクションで指定されているように、通常の速度でイベントをレポートすることを確認し、1つのデバイスに対して多くのイベントを生成する自動テストの実行を控えること。
 
-## 百花繚乱イベントをサポート
+## サポートされている Currents イベント
 
-Brazeは、Currentsの[ユーザー行動]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)および[メッセージエンゲージメントイベントの]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)用語集に記載されている以下のデータをAmplitudeにエクスポートすることをサポートしている：
+Braze では、Currents の[ユーザーの行動]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)および[メッセージエンゲージメント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)イベント用語集にある次のデータを Amplitude にエクスポートすることがサポートされています。
 
 ### 行動
-- カスタムイベントだ： `users.behaviors.CustomEvent`
-- 帰属をインストールする： `users.behaviors.InstallAttribution`
+- カスタムイベント: `users.behaviors.CustomEvent`
+- インストールアトリビューション: `users.behaviors.InstallAttribution`
 - 場所はここだ： `users.behaviors.Location`
-- 購入する： `users.behaviors.Purchase`
-- アンインストールする： `users.behaviors.Uninstall`
+- 購入: `users.behaviors.Purchase`
+- アンインストール: `users.behaviors.Uninstall`
 - アプリ（初回セッション、セッション終了、セッション開始）
   - `users.behaviors.app.FirstSession`
   - `users.behaviors.app.SessionEnd`
@@ -89,18 +89,18 @@ Brazeは、Currentsの[ユーザー行動]({{site.baseurl}}/user_guide/data_and_
 - サブスクリプション・グループ（状態変更）： `users.behaviors.subscriptiongroup.StateChange`
   
 ### キャンペーン
-- 中止する： `users_campaigns_abort`
-- コンバージョンだ： `users.campaigns.Conversion`
-- エンローリンコントロール `users.campaigns.EnrollInControl`
+- 中止: `users_campaigns_abort`
+- コンバージョン: `users.campaigns.Conversion`
+- EnrollinControl: `users.campaigns.EnrollInControl`
   
 ### キャンバス
-- 中止する： `users_canvas_abort`
-- コンバージョンだ： `users.canvas.Conversion`
-- エントリーする： `users.canvas.Entry`
-- 退場（マッチした観客、行われたイベント）
+- 中止: `users_canvas_abort`
+- コンバージョン: `users.canvas.Conversion`
+- エントリ:: `users.canvas.Entry`
+- 離脱 (オーディエンス照合、実行済みのイベント)
   - `users.canvas.exit.MatchedAudience`
   - `users.canvas.exit.PerformedEvent`
-- 実験ステップ（コンバージョン、スプリット・エントリー）
+- 実験ステップ (コンバージョン、分割エントリ)
   - `users.canvas.experimentstep.Conversion`
   - `users.canvas.experimentstep.SplitEntry`
 
@@ -111,7 +111,7 @@ Brazeは、Currentsの[ユーザー行動]({{site.baseurl}}/user_guide/data_and_
   - `users.messages.contentcard.Dismiss`
   - `users.messages.contentcard.Impression`
   - `users.messages.contentcard.Send`
-- 電子メール（中止、バウンス、クリック、配信、マークアスパム、開封、送信、ソフトバウンス、購読解除）
+- メール (中止、バウンス、クリック、配信、スパムとしてマーク、開封、送信、ソフトバウンス、配信停止)
 - アプリ内メッセージ（中止、クリック、インプレッション）
   - `users.messages.inappmessage.Abort`
   - `users.messages.inappmessage.Click`
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api.md
index 5e0d0b25b65..1caf6f2a338 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api.md
@@ -1,17 +1,17 @@
 ---
-nav_title: 振幅とコネクテッド・コンテンツ
-article_title: 振幅とコネクテッド・コンテンツ
+nav_title: Amplitude とコネクテッドコンテンツ
+article_title: Amplitude とコネクテッドコンテンツ
 page_order: 0
 alias: /partners/amplitude_api_endpoints/
 page_type: partner
-description: "AmplitudeのUser Profile APIは、Amplitudeのユーザープロファイルを提供する。これには、ユーザー・プロパティ、計算されたユーザー・プロパティ、ユーザーを含むコホートのコホートIDのリスト、および推奨事項が含まれる。"
+description: "Amplitude の User Profile API は、Amplitude ユーザープロファイルを提供します。これには、ユーザー・プロパティ、計算されたユーザー・プロパティ、ユーザーを含むコホートのコホートIDのリスト、および推奨事項が含まれる。"
 search_tag: Partner
 
 ---
 
-# 振幅とコネクテッド・コンテンツ
+# Amplitude とコネクテッドコンテンツ
 
-> AmplitudeのユーザープロファイルAPIは、Amplitudeのユーザープロファイルを提供する。これには、ユーザー・プロパティ、計算されたユーザー・プロパティ、ユーザーを含むコホートのコホートIDのリスト、および推奨事項が含まれる。以下は、Connected Contentで使用できる一般的なAmplitude APIエンドポイントのリストである。
+> AmplitudeのユーザープロファイルAPIは、Amplitudeのユーザープロファイルを提供する。これには、ユーザー・プロパティ、計算されたユーザー・プロパティ、ユーザーを含むコホートのコホートIDのリスト、および推奨事項が含まれる。コネクテッドコンテンツで使用できる一般的なAmplitude API エンドポイントのリストを以下に示します。
 
 ## エンドポイントパラメーター
 
@@ -21,28 +21,28 @@ search_tag: Partner
 | --------- | -------- | ----------- |
 | `user_id` | オプション | 問い合わせるユーザーID（外部データベースID）。`device_id` が設定されていない場合は必須。 |
 | `device_id` | オプション | 問い合わせるデバイスID（匿名ID）。`user_id` が設定されていない場合は必須。 |
-| `get_recs` | オプション<br>(デフォルトはfalse）。 | このユーザーの推薦結果を返す。 |
-| `rec_id` | オプション | `get_recs` が true の場合は必須。`rec_ids` 、カンマで区切ることで複数の推薦文を取得することができる。 |
-| `rec_type` | オプション | デフォルトの実験的コントロール設定を上書きし、`rec_type=model` はモデル化された推奨を返し、`rec_type=random` はランダムな推奨を返す。将来的には他の選択肢も存在するかもしれない。 |
-| `get_amp_props` | オプション<br>(デフォルトはfalse）。 | このユーザーの、計算を含まないユーザー・プロパティの完全なセットを返す。 |
-| `get_cohort_ids` | オプション<br>(デフォルトはfalse）。 | このユーザーが所属するコホートIDのうち、追跡するよう設定されているすべてのコホートIDのリストを返す。デフォルトでは、どのコホートのユーザーについても、コホート・メンバーシップは追跡されない。 |
-| `get_computations` | オプション<br>(デフォルトはfalse）。 | このユーザーに対して有効になっているすべての計算のリストを返す。 |
+| `get_recs` | オプション<br>(デフォルトは false)。 | このユーザーの推薦結果を返す。 |
+| `rec_id` | オプション | 取得するレコメンデーション。`get_recs`が true の場合は必須です。複数のレコメンデーションを取得するには、`rec_ids` をカンマで区切って指定します。 |
+| `rec_type` | オプション | デフォルトの実験的コントロール設定を上書きします。`rec_type=model` はモデル化されたレコメンデーションを返し、`rec_type=random` はランダムなレコメンデーションを返します。将来的にはその他のオプションが導入される可能性があります。 |
+| `get_amp_props` | オプション<br>(デフォルトは false)。 | このユーザーの、計算を含まないユーザー・プロパティの完全なセットを返す。 |
+| `get_cohort_ids` | オプション<br>(デフォルトは false)。 | このユーザーが所属するコホートIDのうち、追跡するよう設定されているすべてのコホートIDのリストを返す。デフォルトでは、すべてのコホートのユーザーのコホートメンバーシップが追跡されません。 |
+| `get_computations` | オプション<br>(デフォルトは false)。 | このユーザーに対して有効になっているすべての計算のリストを返す。 |
 | `comp_id` | オプション | このユーザーで有効になっている可能性のある計算を1つ返す。存在しない場合はヌル値を返す。`get_computations` がtrueの場合、この値を含むすべての値がフェッチされる（アーカイブまたは削除されていない限り）。|
 {: .reset-td-br-1 .reset-td-br-2}
 
-以下の表は、アンプリチュードのレスポンスで最も一般的に期待されるパラメータを網羅している。
+Amplitude の応答で最もよく使用される可能性があるパラメーターを次の表に示します。
 
 | 応答パラメーター | 説明 |
 | ------------------ | ----------- |
-| `rec_id` | という推薦状が要求された。 |
-| `child_rec_id` | より詳細なレコメンデーションIDは、モデルのパフォーマンスを向上させるための内部実験の一環として、アンプリチュードがバックエンドで使用する可能性がある。ほとんどの場合、これは`rec_id` と同じである。 |
+| `rec_id` | 要求されたレコメンデーション ID。 |
+| `child_rec_id` | Amplitude がモデルパフォーマンス向上のための内部実験の一部としてバックエンドで使用する可能性がある、より詳細なレコメンデーション ID。ほとんどの場合、これは `rec_id` と同じです。 |
 | `items` | このユーザーへの推薦リスト。 |
-| `is_control` | このユーザーがコントロール・グループの一員であればtrue。 |
+| `is_control` | このユーザーがコントロールグループに属している場合は true。 |
 | `recommendation_source` | この推薦文を作成するために使用されたモデルの名前 |
 | `last_updated` | この推薦文が最後に生成され、同期されたときのタイムスタンプ。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-## 共通の振幅エンドポイント
+## 一般的な Amplitude エンドポイント
 
 ### 推薦してもらう
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/celebrus.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/celebrus.md
index 0ea67dc9ee5..5e3774243e9 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/celebrus.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/celebrus.md
@@ -1,32 +1,32 @@
 ---
-nav_title: セレブラス
-article_title: セレブラスの統合
-description: "ブレイズとセレブラスの統合"
+nav_title: Celebrus
+article_title: Celebrus 統合
+description: "Braze と Celebrus の統合。"
 ---
 
-# セレブラス
+# Celebrus
 
-> Celebrusは、WebおよびモバイルアプリのチャネルでBraze SDKとシームレスに統合し、チャネルのアクティビティデータをBrazeに取り込むことを容易にする。これには、特定期間におけるデジタル資産全体のビジター・トラフィックに関する包括的な洞察も含まれる。<br><br>さらに、セレブラスは顧客一人ひとりの豊富なプロフィールデータを取得し、Brazeと同期させることができる。これにより、包括的で正確かつ詳細なファーストパーティデータに基づき、効果的なBrazeアナリティクスとコミュニケーション戦略を策定することができる。この能力は、セレブラスの機械学習主導型シグナルによってさらに強化され、大掛かりなタグ付けをすることなく、手間をかけずにデータを取り込むことができる。堅牢なファーストパーティ・アイデンティティ・グラフがあれば、すべてのデータに即座にアクセスでき、すぐに利用できるようになる。 
+> Celebrus は Web アプリチャネルとモバイルアプリチャネルで Braze SDK とシームレスに統合され、チャネルアクティビティデータを Braze に取り込みやすくなります。これには、特定期間におけるデジタル資産全体のビジター・トラフィックに関する包括的な洞察も含まれる。<br><br>さらに Celebrus は、個々の顧客の豊富なプロファイルデータを取得し、Braze と同期できます。これにより、包括的で正確かつ詳細なファーストパーティデータに基づき、効果的なBrazeアナリティクスとコミュニケーション戦略を策定することができる。この機能は Celebrus の機械学習を活用したシグナルによりさらに強化されます。これにより、大規模なタグ付け作業を必要とせずに、簡単にデータを取り込むことができます。堅牢なファーストパーティの ID グラフを導入することで、すべてのデータに即座にアクセスしてすぐに使用できるようになります。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| セレブルスアカウント | このパートナーシップを利用するには、セレブラスのアカウントが必要である。 |
-| データウェアハウス（オプション） | Brazeカスタム属性用のCelebrusコネクタを使用する場合は、Braze Cloud Data Ingestion (CDI)統合がサポートするデータウェアハウスを用意し、BrazeダッシュボードでCDIを設定する必要がある。 |
-| Braze SDKの構成設定（オプション） | Braze SDK用のCelebrusコネクタを使用する場合は、SDKエンドポイントとSDK API Keyを渡す必要がある。 |
+| Celebrus アカウント | このパートナーシップを活用するには、Celebrus アカウントが必要です。 |
+| データウェアハウス（オプション） | Celebrus コネクターを Braze のカスタム属性に使用する場合は、Braze クラウドデータ取り込み (CDI) 統合でサポートされるデータウェアハウスが必要です。また、Braze ダッシュボードで CDI を設定する必要があります。 |
+| Braze SDKの構成設定（オプション） | Braze SDK に Celebrus コネクターを使用する場合は、SDK エンドポイントと SDK API キーを渡す必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 実装
-Celebrusの実装をインストールした後、Braze用のCelebrusコネクタを使用してCelebrusデータをBrazeに統合する。BrazeのCelebrus統合には、Braze SDKとBrazeカスタム属性の2つの要素がある。Brazeの使い方や必要なユースケースに応じて、どちらか一方を導入することも、両方を導入することもできる。
+Celebrusの実装をインストールした後、Braze用のCelebrusコネクタを使用してCelebrusデータをBrazeに統合する。Braze の Celebrus 統合には、Braze SDK とBraze のカスタム属性という2つの要素があります。Braze の使い方と必要なユースケースに応じて、いずれかまたは両方をデプロイできます。
 
-WebチャンネルにBraze SDKがまだ実装されていない場合は、Celebrusを使用してBraze SDKをデプロイすることができる。Celebrusは、WebページにBraze SDKを追加し、Celebrusアイデンティティグラフを使用してWeb訪問者にBrazeアイデンティティを設定する。顧客属性は、CDI（Cloud Data Ingestion）経由でBrazeと同期できる。これには、Braze CDIがサポートするデータウェアハウスと、BrazeでのCDIの設定が必要である。
+Web チャネルに Braze SDK がまだ実装されていない場合は、Celebrus を使用して Braze SDK をデプロイできます。Celebrusは、WebページにBraze SDKを追加し、Celebrusアイデンティティグラフを使用してWeb訪問者にBrazeアイデンティティを設定する。顧客の属性は、クラウドデータ取り込み (CDI) を使用して Braze と同期できます。このためには、Braze CDI によってサポートされるデータウェアハウスと、Braze での CDI の設定が必要です。
 
 ### Braze SDK用Celebrusコネクタ
 
-BrazeSDK用Celebrusコネクタは、Brazeのハイレベルなウェブおよびモバイルアプリのチャネルデータを提供する。Braze SDKでは、Celebrus IDグラフのCelebrus`System Identity` がBraze統合の識別子として使用される。その他の識別子は、Braze Custom Attributes Celebrusコネクタを介してカスタム属性を同期するためにサポートされている。
+BrazeSDK用Celebrusコネクタは、Brazeのハイレベルなウェブおよびモバイルアプリのチャネルデータを提供する。Braze SDK では、Celebrus ID グラフの Celebrus `System Identity` が Braze 統合の識別子として使用されます。その他の識別子は、Braze Custom Attributes Celebrus コネクターを介してカスタム属性を同期するためにサポートされています。
 
-コネクターは、あなたのチャンネルにBraze SDKをデプロイして構成するので、Braze SDKデータストリームでいくつかの設定を構成し、これら3つの設定の値を提供する必要がある：
+このコネクターによりチャネルに Braze SDK がデプロイされ、設定されます。このため、Braze SDK データストリームでいくつかの設定を行い、次の3つの設定の値を指定する必要があります。
 
 ```
     response.addParameter("sdk_endpoint", "sdk.xxxxxx.braze.com");
@@ -35,26 +35,26 @@ BrazeSDK用Celebrusコネクタは、Brazeのハイレベルなウェブおよ
 ```
 
 {% alert important %}
-Braze SDK用のCelebrusコネクタは、ユーザーを識別するためにBraze SDKを挿入して初期化し、CelebrusのIdentity Graphに識別子を追加する。このコネクタは、ユーザープロファイルにデータを記録したり、他のBraze SDKメソッドをトリガーしたりしない。<br><br>[Braze SDK]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/)経由でデータを記録したり、Braze SDKがサポートする他の機能を利用したりするために、コードベース内で必要なメソッドを直接呼び出すことができる。
+Braze SDK 用の Celebrus コネクターは、ユーザーを識別し、識別子を Celebrus の ID グラフに追加するために Braze SDK を挿入および初期化します。このコネクタは、ユーザープロファイルにデータを記録したり、他のBraze SDKメソッドをトリガーしたりしない。<br><br>[Braze SDK]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/)経由でデータを記録したり、Braze SDKがサポートする他の機能を利用したりするために、コードベース内で必要なメソッドを直接呼び出すことができる。
 {% endalert%}
 
 ### Brazeカスタム属性用Celebrusコネクター
 
-#### ステップ1:Celebrusで接続の詳細を設定する 
+#### ステップ1:Celebrus で接続の詳細を設定する 
 
-Brazeカスタム属性用のCelebrusコネクタは、Brazeが期待する方法で事前にフォーマットされたカスタム属性を中間データベースに送信する。Celebrusでは、使用しているデータベースの種類（SnowflakeやRedshiftなど）によって異なるデータベースの接続詳細を設定する。 
+Braze カスタム属性用の Celebrus コネクターは、カスタム属性を中間データベースに送信します。このときカスタム属性は、Braze での受け取り形式で事前に形式設定されています。Celebrusでは、使用しているデータベースの種類（SnowflakeやRedshiftなど）によって異なるデータベースの接続詳細を設定する。 
 
-#### ステップ2:Brazeダッシュボードでクラウドデータ取り込みを設定する
+#### ステップ2:Braze ダッシュボードでクラウドデータ取り込みを設定する
 
-この統合はBraze Cloud Data Ingestionを使用している。[データウェアハウスの統合の]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/)説明に従って、使用しているウェアハウスのタイプに応じて、[クラウドデータインジェスト]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/overview/)設定をセットアップして構成する。 
+この統合では、Braze のクラウドデータ取り込みを使用します。「[データウェアハウスの統合]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/)」の手順に従って、使用するウェアハウスのタイプに応じて[クラウドデータ取り込みの設定]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/overview/)を行います。 
 
-#### ステップ3:セレブラスからブレイズにデータを同期する
+#### ステップ3:Celebrus から Braze にデータを同期する
 
-Celebrusは、電子メール、電話、`external_id`、ユーザーエイリアスなどの一意の識別子を取得し、個人に割り当て、CDIを介してBrazeに送信する。これにより、同じ個人のデータをBrazeに同期させることができる。
+Celebrus は、メール、電話、`external_id` またはユーザーエイリアスなどの一意の識別子をキャプチャし、個別に割り当て、CDI を使用して Braze に送信します。これにより、同一の個人に関するデータを Braze と同期できます。
 
-セレブラスは、定義された識別子を使用して、セレブラス・プロファイル・ビルダーで定義された顧客属性を送信するが、属性値が変更された場合にのみ送信する。属性名はCelebrusプロファイル・ビルダーで定義されたものになるので、Brazeの属性はCelebrusプロファイルの属性と同じになる。これらは、Brazeの命名規則に合わせて調整する必要があるかもしれない。例えば、Brazeの[標準的な属性の命名規則に]({{site.baseurl}}/api/objects_filters/user_attributes_object/)従う。  
+Celebrus は、属性値が変更された場合にのみ、定義されている識別子を使用して、Celebrus プロファイルビルダーで定義された顧客属性を送信します。属性名は、Celebrus プロファイルビルダーで定義されているとおりになるため、Braze の属性は、Celebrus プロファイルの属性をミラーリングすることになります。これらの属性がBraze の命名規則に準拠するように、調整が必要となることがあります。たとえば、Braze の[標準属性命名規則]({{site.baseurl}}/api/objects_filters/user_attributes_object/) に準拠します。  
 
 {% alert important %}
-今のところ、このリリースはイベントと購入には対応していない。<br><br> この統合では、属性を文字列値として送信するため、一部の属性はリストになる（シグナルなど）。今のところ、リストを配列に変換することはできない。ネストされた属性はない。
+現時点では、このリリースではイベントと購入はサポートされていません。<br><br> この統合では、属性を文字列値として送信するため、一部の属性はリストになる（シグナルなど）。今のところ、リストを配列に変換することはできない。ネストされた属性はない。
 {% endalert%}
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/clarisights.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/clarisights.md
index 489e803c55a..1a23adf0ca5 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/clarisights.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/clarisights.md
@@ -1,24 +1,24 @@
 ---
-nav_title: クラリサイト
-article_title: クラリサイト
-description: "この参考記事では、Brazeとセルフサービス型パフォーマンスマーケティングレポーティングプラットフォームであるClarisightsの提携について概説している。BrazeのキャンペーンとCanvasesからデータをインポートすることで、パフォーマンスマーケティングとCRM/リテンションマーケティングの統一されたレポーティングインターフェースを実現することができる。"
+nav_title: Clarisights
+article_title: Clarisights
+description: "このリファレンス記事では、Braze と Clarisights のパートナーシップについて説明します。Clarisights は、セルフサービスのパフォーマンスマーケティングレポートプラットフォームであり、Braze キャンペーンとキャンバスからデータをインポートできます。これは、パフォーマンスと CRM/リテンションマーケティングの統合レポートインターフェイスを実現するのに役立ちます。"
 alias: /partners/Clarisights/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# クラリサイト
+# Clarisights
 
-> [Clarisightsは][2]、データ主導型企業向けのセルフサービス型パフォーマンス・マーケティング・レポート・プラットフォームである。マーケティング、分析、アトリビューション・ソースからのすべてのデータを自動的に統合、処理、視覚化する。
+> [Clarisightsは][2]、データ主導型企業向けのセルフサービス型パフォーマンス・マーケティング・レポート・プラットフォームである。マーケティング、分析、およびアトリビューションのソースからのすべてのデータを自動的に統合、処理、および視覚化します。
 
-BrazeとClarisightsの統合により、BrazeのキャンペーンとCanvasesからデータをインポートし、パフォーマンスとCRM/リテンションマーケティングの統一されたレポーティングインターフェースを実現できる。
+Braze と Clarisights の統合により、Braze キャンペーンとキャンバスからデータをインポートできます。これは、パフォーマンスおよびCRM/リテンションマーケティングの統合レポートインターフェイスを実現するのに役立ちます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| クラリスツアカウント | このパートナーシップを利用するには、Clarisightsワークスペースが必要である。 |
+| Clarisights アカウント | このパートナーシップを利用するには、Clarisightsワークスペースが必要である。 |
 | Braze REST API キー | 以下の権限を持つBraze REST APIキー： <br> - `campaigns.list`<br>  - `campaigns.details`<br> - `campaigns.data_series`<br> - `canvas.details`<br> - `canvas.list`<br>  - `canvas.data_series`<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][1]。エンドポイントは、インスタンスのBraze URLに依存する。 |
 | Brazeワークスペース名 | Braze APIキーに関連付けられたワークスペースの名前。この名前は、Clarisights上のワークスペース統合を識別するために使用される。 |
@@ -29,12 +29,12 @@ BrazeとClarisightsの統合により、BrazeのキャンペーンとCanvasesか
 BrazeとClarisightsの統合により、ユーザーはさまざまなビジュアライゼーションやテーブルを作成し、作成したキャンペーンから洞察を得ることができる。人気のある使用例は以下の通りである：
 
 {% tabs %}
-{% tab より良い視界 %}
+{% tab 可視化の向上 %}
 キャンペーン全体とキャンバスのパフォーマンスの可視性を高める。
 
-![クラリサイト・プラットフォームにおけるより良い実行可能性の例を示すグラフィック。このグラフィックには、キャンペーンとキャンバスの開封、クリック、送信、コンバージョンなどの統計が含まれる。]({{site.baseurl}}/assets/img/clarisights/overall_view.png)
+![Clarisights プラットフォームでの向上した可視化の例。このグラフィックには、キャンペーンとキャンバスの開封、クリック、送信、コンバージョンなどの統計が含まれる。]({{site.baseurl}}/assets/img/clarisights/overall_view.png)
 {% endtab %}
-{% tab きめ細かいレポート %}
+{% tab 詳細なレポート %}
 キャンペーンとキャンバスの詳細なレポート。
 
 ![送信チャネル別の送信全体」や「コンバージョン率」のような詳細なレポートを示すグラフィック。]({{site.baseurl}}/assets/img/clarisights/unified_dashboard.png)
@@ -48,20 +48,20 @@ CMOとCXOのための統一ダッシュボード。
 
 ## 統合
 
-BrazeデータをClarisightsに同期するには、Brazeコネクタを構築し、Brazeワークスペースを接続する必要がある。
+Braze データを Clarisights に同期するには、Braze コネクターを作成して Braze ワークスペースを接続する必要があります。
 
-1. Clarisightsで、**Integrations**ページに移動し、**Braze**コネクターを見つけ、**\+ Connectを**選択する。<br>![Clarisights統合マーケットプレイスから利用可能なコネクタのリスト。][6]<br><br>
-2. 次に、統合フローを使って、ClarisightsアカウントをBrazeに接続する。これは、Braze REST APIキー、Brazeワークスペース名、およびBraze RESTエンドポイントを提供することによって行うことができる。<br>![ClarisightsプラットフォームのBrazeワークスペースコネクター。このページには、Brazeワークスペース名、Braze REST APIキー、Braze RESTエンドポイントのフィールドがある。][7]<br><br>統合が成功する前は、ユーザーは同じページに接続されたワークスペースを見ることができる。<br>![Braze Accounts "の中に、接続されているワークスペースのリストがある。][9]<br><br>
+1. Clarisights で \[**Integrations**] ページに移動し、**Braze** コネクターを見つけ、\[**\+ Connect**] を選択します。<br>![Clarisights の統合のマーケットプレイスから入手できるコネクターのリスト。][6]<br><br>
+2. 次に、統合フローを使って、ClarisightsアカウントをBrazeに接続する。これを行うには、Braze REST API キー、Braze ワークスペース名、Braze REST エンドポイントを指定します。<br>![ClarisightsプラットフォームのBrazeワークスペースコネクター。このページには、Braze ワークスペース名、Braze REST API キー、および Braze REST エンドポイントのフィールドが表示されている。][7]<br><br>統合が成功する前は、ユーザーは同じページに接続されたワークスペースを見ることができる。<br>![「Braze Accounts」に、接続されたワークスペースのリストが表示されている。][9]<br><br>
 
 ## この統合を使う
 
-BrazeをClarisightsレポートのデータソースとして含めるには、**Create New Reportに**移動する。レポートに名前を付け、表示されるプロンプトでデータソースとして**Brazeを**選択する。また、レポートに含めるメトリクスとディメンションを選択することもできる。完了したら、**Create Reportを**選択する。 
+Clarisights レポートにデータソースとして Braze を含めるには、\[**Create New Report**]に移動します。レポートに名前を付け、表示されるプロンプトでデータソースとして \[**Braze**] を選択します。また、レポートに含めるメトリクスとディメンションを選択することもできる。完了したら、\[**Create Report**] を選択します。 
 
-Brazeからのデータは、次に予定されているデータインポートの時点から流れ始める。クラリスタイツのカスタマーサクセスマネージャーに連絡し、長期間のバックフィルを依頼する。 
+Braze のデータは、予定されている次回のデータインポートの時点から流入し始めます。Clarisights のカスタマーサクセスマネージャーに連絡して、長期のバックフィルを依頼します。 
 
-![Clarisightのレポート設定で、名前とデータソースのフィールドが表示される。この例では、データソースとして "Braze "が選択されている。][8]
+![Clarisightのレポート設定で、名前とデータソースのフィールドが表示される。この例では「Braze」がデータソースとして選択されている。][8]
 
-利用可能な[メトリクスとディメンション][10]、または[レポート作成の][11]詳細については、Clarisightsを参照のこと。
+利用可能な[指標とディメンション][10]または[レポート作成][11]の詳細については、Clarisights にアクセスしてください。
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
 [2]: https://clarisights.com
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/contentsquare.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/contentsquare.md
index 8548841d523..f6dcdcf4d56 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/contentsquare.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/contentsquare.md
@@ -1,6 +1,6 @@
 ---
-nav_title: コンテンツスクエア
-article_title: コンテンツスクエア
+nav_title: Contentsquare
+article_title: Contentsquare
 description: "この参考記事では、BrazeとContentsquareの提携について概説している。Contentsquareは、デジタル体験分析プラットフォームであり、顧客のデジタル体験に基づいてメッセージをターゲティングすることで、キャンペーンの関連性とコンバージョン率を向上させることができる。"
 alias: /partners/contentsquare/
 page_type: partner
@@ -8,9 +8,9 @@ search_tag: Partner
 
 ---
 
-# コンテンツスクエア
+# Contentsquare
 
-> [Contentsquareは](https://contentsquare.com/)、前例のない顧客体験の理解を可能にするデジタル体験分析プラットフォームである。
+> [Contentsquare](https://contentsquare.com/) は、カスタマーエクスペリエンスを今までにない方法で理解できるようにするデジタルエクスペリエンス分析プラットフォームです。
 
 BrazeとContentsquareの統合により、Brazeのカスタムイベントとしてライブシグナル（不正行為、フラストレーションシグナルなど）を送信することができる。Contentsquareのエクスペリエンスインサイトを活用し、顧客のデジタルエクスペリエンスとボディランゲージに基づいてメッセージをターゲティングすることで、キャンペーンの関連性とコンバージョン率を向上させる。
 
@@ -18,36 +18,36 @@ BrazeとContentsquareの統合により、Brazeのカスタムイベントとし
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| コンテンツクエアアカウント | このパートナーシップを利用するには、Contentsquareのアカウントが必要だ。 |
+| Contentsquare アカウント | このパートナーシップを活用するには、Contentsquare アカウントが必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
 BrazeとContentsquareの一般的な使用例には、以下のようなものがある：
-- Braze内の顧客経験データを表面化することで、顧客の意図に基づいてメッセージを高度にパーソナライズする。
-- 顧客のデジタル行動、躊躇、フラストレーション、意図に基づいてリターゲティングを行う。
-- Contentsquareの中で悪い経験を特定し、ターゲットを絞ったメッセージとリテンション・オファーで顧客を回復させる。
+- Braze 内でカスタマーエクスペリエンスデータを表面化することで、顧客の意図に基づいてメッセージをハイパーパーパーパーソナライズする。
+- 顧客のデジタル行動、躊躇、不満、意図に基づいて顧客をリターゲティングする。
+- Contentsquare 内で不十分なエクスペリエンスを特定し、ターゲットを絞ったメッセージとリテンションオファーで顧客を取り戻す。
 - 適切なタイミングと場所で、より適切で共感的なメッセージを送ることで、リスクのある顧客を回復させる。
 
 ## 統合
 
-ContentsquareをBrazeに統合するには、Contentsquare統合カタログから「Live Signals」統合のインストールをリクエストする必要がある：
+Contentsquare を Braze に統合するには、Contentsquare 統合カタログからの「Live Signals」のインストールをリクエストする必要があります。
 
-1. Contentsquareで、**設定**メニューの**Consoleを**クリックする。これにより、現在取り組んでいるプロジェクトにリダイレクトされる。 
+1. Contentsquare で \[**Settings**] メニューの \[**Console**] をクリックします。これにより、現在取り組んでいるプロジェクトにリダイレクトされる。 
 2. **Projects**ページで、**Integrations**タブに行き、**\+ Add integration**ボタンをクリックする。
-3. 統合カタログで、**Live Signals**統合を見つけ、**Addを**クリックする。Contentsquareチームは、Brazeにライブシグナルを送信するためのコードスニペットを設定するために連絡を取る。
-4. Contentsquareがあなたの統合を処理する。インジケーターのテキストは、統合完了後に更新される。
+3. 統合カタログで **Live Signals** 統合を見つけ、\[**Add**] をクリックします。その後 Contentsquare チームが、ライブシグナルを Braze に送信するようにコードスニペットを設定することを依頼します。
+4. Contentsquare により統合が処理されます。インジケーターのテキストは、統合完了後に更新される。
 
 詳細については、「[Contentsquareの統合をリクエストする](https://uxanalyser.zendesk.com/hc/en-gb/articles/4405613239186)」を参照のこと。
 
 ## この統合を使う
 
-統合が完了すると、Contentsquareのカスタムイベントがキャンペーンやキャンバスで使用できるようになる。どのイベントがBrazeに送信されているかは、**Data Settings**>**Custom Eventsから**確認できる。
+統合が完了すると、Contentsquareのカスタムイベントがキャンペーンやキャンバスで使用できるようになる。\[**Data Settings**] > \[**Custom Events**] から、どのイベントが Braze に送信されているかを確認できます。
 
 {% alert note %}
 [古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合、このページは**Manage Settings**>**Custom Events** にある。
 {% endalert %}
 
-![BrazeカスタムイベントタブのContentsquareライブシグナルデータ][1]
+![Braze の \[カスタムイベント] タブのContentsquare ライブシグナルデータ][1]
 
 [1]: {% image_buster /assets/img/contentsquare_custom_events.png %} 
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/datadog.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/datadog.md
index 4d3b805825d..e6c6c199a31 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/datadog.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/datadog.md
@@ -11,32 +11,32 @@ search_tag: Partner
 
 # Datadog
 
-> [Datadogは](https://www.datadoghq.com/)、クラウドスケールのアプリケーションのための観測可能なサービスで、SaaSベースのデータ分析プラットフォームを通じて、サーバー、データベース、ツール、サービスの監視を提供する。
+> [Datadog](https://www.datadoghq.com/) は、クラウド規模のアプリケーション向けオブザーバビリティサービスであり、SaaS ベースのデータ分析プラットフォームでサーバー、データベース、ツール、およびサービスを監視する機能を提供します。
 
-BrazeとDatadogの統合により、顧客はDatadogでBrazeのデータを収集し、当社が送信するデータに対してアラートを作成することができる。例えば、毎週のニュースレター・キャンペーンで送信されるメッセージの量が異常に少なかったり、通常は1日に数通しか送信しないキャンバス・ステップが数千通を送信し始めたりした場合に、モニターを設定してアラートを出す。 
+Braze と Datadog の統合により、お客様は Datadog で Braze データを収集し、送信するデータに関するアラートを作成できます。例えば、毎週のニュースレター・キャンペーンで送信されるメッセージの量が異常に少なかったり、通常は1日に数通しか送信しないキャンバス・ステップが数千通を送信し始めたりした場合に、モニターを設定してアラートを出す。 
 
 ## 前提条件 
 
 | 必要条件 | 説明 |
 |---|---|
-| Datadogアカウント | このパートナーシップを利用するには、Datadogアカウントが必要である。 |
+| Datadogアカウント | このパートナーシップを活用するには、Datadog アカウントが必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:Datadogのキーを生成する
 
-Datadogでは、[APIキーを](https://docs.datadoghq.com/account_management/api-app-keys/#api-keys)作成する必要がある。APIキーを追加するには、「**Organization Settings（組織設定）」>「** **API Keys（APIキー）」>「** **New Key（新規キー）**」の順に移動する。
+Datadog で [API キー](https://docs.datadoghq.com/account_management/api-app-keys/#api-keys)を作成する必要があります。APIキーを追加するには、「**Organization Settings（組織設定）」>「** **API Keys（APIキー）」>「** **New Key（新規キー）**」の順に移動する。
 
-### ステップ2:ブレーズにキーを追加する
+### ステップ2:Braze にキーを追加する
 
-Brazeのダッシュボードで、**Partner Integrations**>**Technology Partnersと**進み、**Datadogを**検索する。Datadog パートナーページで、Datadog API キーを入力する。これで、BrazeがDatadogにデータを送信するための接続が作成される。
+Braze ダッシュボードで \[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Datadog**] を探します。Datadog パートナーページで Datadog API キーを指定します。これで、Braze がDatadog にデータを送信するための接続が作成されます。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-## ブレイズのイベント
+## Braze のイベント
 
 接続が統合されると、Brazeは以下のイベントをDatadogに送信する：
 
@@ -49,7 +49,7 @@ Brazeのダッシュボードで、**Partner Integrations**>**Technology Partner
 - `campaign_id` /`campaign_name` (利用可能な場合)
 - `canvas_id` /`canvas_name` /`canvas_step_id` /`canvas_step_name` (利用可能な場合)
 
-これらのイベントとタグは、Datadog**Metrics Explorer**ページで監視できる。これらのメトリクスは、DataDogに[ディストリビューションとして](https://docs.datadoghq.com/metrics/distributions/)記録される。Brazeは、メトリクスの性質とDataDogの集計およびロールアップの不正確さを考慮し、送信中に発生する可能性のある断続的なネットワークエラーやその他のDataDog APIエラーを再試行しない。つまり、これらの数値は、BrazeのダッシュボードやCurrentsで表示される数値とは若干異なる可能性がある。
+これらのイベントとタグは、Datadog**Metrics Explorer**ページで監視できる。これらのメトリクスは、DataDogに[ディストリビューションとして](https://docs.datadoghq.com/metrics/distributions/)記録される。指標の性質と、DataDog の集約とロールアップの不正確さを考慮して、Braze では、送信中に発生する可能性のある断続的なネットワークエラーやその他の DataDog API エラーの場合は再試行されません。つまり、これら指標の数値が、Braze ダッシュボードや Currents で表示される数値とは若干異なる可能性があります。
 
 ![][1]
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/heap.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/heap.md
index 0da53656b07..681cbacf84f 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/heap.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/heap.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Heap
 article_title: "ヒープ解析"
-description: "このリファレンス記事では、Braze Currents を使用してヒープでエンゲージメントのイベントを自動的に分析する方法について説明します。ヒープは、デジタルインサイトs プラットフォームで、Brazeにヒープデータをインポートし、ユーザー コホートs を作成し、BrazeデータをヒープにエクスポートしてSegments を作成することができます。"
+description: "このリファレンス記事では、Braze Currents を使用して Heap でエンゲージメントイベントを自動的に分析する方法について説明します。Heap はデジタルインサイトプラットフォームであり、Braze への Heap データのインポート、ユーザー コホートの作成、セグメント作成のための Heap への Braze データのエクスポートを行うことができます。"
 page_type: partner
 search_tag: Partner
 
@@ -10,7 +10,7 @@ search_tag: Partner
 
 # ヒープ分析
 
-> 解析のためにBrazeからヒープにエンゲージメント事象を自動的に送信する方法について述べた。ヒープと他の機能の統合については、[ヒープコホートs]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/heap/#data-import-integration)をBrazeに同期するなど、メインの[ヒープ記事]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/heap/)を参照してください。
+> この記事では、解析のために Braze から Heap にエンゲージメントイベントを自動送信する方法について説明します。Heap と他の機能 (Braze との [Heap コホートの同期]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/heap/#data-import-integration) など) の統合について詳しくは、メインの[Heap の記事]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/heap/)を参照してください。
 
 ## データエクスポート統合
 
@@ -18,14 +18,14 @@ Braze Currentsを使用して、Brazeからヒープにエンゲージメント
 
 ### ステップ1:ヒープ認証情報の取得
 
-このインテグレーションを設定するには、ヒープアカウントマネージャーから取得できるWebhook エンドポイント URL が必要です。
+この統合を設定するには、Webhook エンドポイント URL が必要です。この URL は、Heap アカウントマネージャーから取得できます。
 
-### ステップ2:Braze Currentsの設定
+### ステップ2:Braze Currents を設定する
 
-Braze で、**Partner Integrations**> **Data Export** に移動し、**Create New Current** をクリックし、**Heap Export** を選択します。 
+Braze で \[**パートナー連携**] > \[**データのエクスポート**] に移動し、\[**新しい Currents を作成**] をクリックし、\[**ヒープのエクスポート**] を選択します。 
 
 {% alert note %}
-[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、**Currents**の下に**統合**があります。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**Currents**] は \[**統合**] にあります。
 {% endalert %}
 
 エクスポートに名前を付け、**Current Details** ページに進みます。この画面では、エンドポイントとオプションのベアラトークン(提供されている場合)を入力します。
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/kubit.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/kubit.md
index 8368f2f949e..85f3ad97496 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/kubit.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/kubit.md
@@ -1,18 +1,18 @@
 ---
-nav_title: クビット
-article_title: クビット
-description: "この参考記事では、BrazeとKubitのパートナーシップについて概説している。Kubitは、コード不要のセルフサービス分析プラットフォームで、製品に関する洞察を即座に提供し、Kubitのユーザーコホートをインポートして、Brazeのメッセージングでターゲットを絞ることができる。"
+nav_title: Kubit
+article_title: Kubit
+description: "このリファレンス記事では、Braze と Kubit のパートナーシップについて説明します。Kubit は、製品インサイトを提供するノーコードのセルフサービス分析プラットフォームであり、Kubit ユーザーコホートをインポートして、Braze メッセージングでそれらのコホートをターゲットにできます。"
 alias: /partners/kubit/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# クビット
+# Kubit
 
-> [Kubitは](https://kubit.ai/)コード不要のセルフサービス分析プラットフォームで、製品に関する洞察を即座に提供する。 
+> [Kubit](https://kubit.ai/) はノーコードのセルフサービス分析プラットフォームであり、製品インサイトを瞬時に提供できます。 
 
-BrazeとKubitの統合により、[Kubitユーザーコホートをインポート]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/kubit/)し、Brazeメッセージングでターゲットにすることができる。さらに、[Snowflakeのセキュアなデータ共有を]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/)使用することで、Brazeの生のキャンペーンデータとインプレッションデータをKubitの製品アナリティクスと統合し、これらのキャンペーンの効果をリアルタイムで測定することができる。このアプローチは、エンジニアリングの努力を必要とすることなく、ユーザーのライフサイクル全体に対する洞察を提供する。
+BrazeとKubitの統合により、[Kubitユーザーコホートをインポート]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/kubit/)し、Brazeメッセージングでターゲットにすることができる。また、[Snowflake セキュアデータシェアリング]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/)を使用することで、Braze の生のキャンペーンおよびインプレッションデータを Kubit の製品分析と統合し、これらのキャンペーンの効果をリアルタイムで測定できます。このアプローチは、エンジニアリングの努力を必要とすることなく、ユーザーのライフサイクル全体に対する洞察を提供する。
 
 ## 前提条件
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/looker.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/looker.md
index a17fd598c27..67f7b1d320e 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/looker.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/looker.md
@@ -1,6 +1,6 @@
 ---
-nav_title: ルッカー
-article_title: ルッカー
+nav_title: Looker
+article_title: Looker
 alias: /partners/looker/
 description: "この参考記事では、Brazeとビジネス・インテリジェンスおよびビッグデータ分析プラットフォームであるLookerのパートナーシップについて概説している。"
 page_type: partner
@@ -8,38 +8,38 @@ search_tag: Partner
 
 ---
 
-# [![Braze Learning course]](https://learning.braze.com/looker-integration-with-braze/)([{% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/looker-integration-with-braze/){: style="float:right;width:120px;border:0;" class="noimgborder"}Looker
+# [![Braze ラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/looker-integration-with-braze/){: style="float:right;width:120px;border:0;" class="noimgborder"}Looker
 
-> ビジネスインテリジェンスとビッグデータ分析プラットフォームである[Lookerは](https://looker.com/)、リアルタイムのビジネス分析をシームレスに探索、分析、共有することを可能にする。
+> ビジネスインテリジェンスとビッグデータ分析のプラットフォームである [Looker](https://looker.com/) は、リアルタイムのビジネス分析の探索、分析、共有をシームレスに行えるようにしています。
 
-BrazeとLookerの統合により、BrazeユーザーはREST APIを介してファーストパーティの[Looker Blocksと](#looker-blocks) [Looker Actionsの](#looker-actions)ユーザーフラグを活用することができる。これらのフラグを立てたユーザーをセグメントに追加し、将来のBrazeキャンペーンやCanvasの[ターゲットにする](#segment-users)ことができる。BrazeでLookerを使用するには、Braze[カレントを使用して][6]Brazeデータを[データウェアハウスに][6]送信し、BrazeのLooker Blocksを使用してLookerでBrazeデータを素早くモデル化、視覚化することを推奨する。
+Braze と Looker の統合により、Braze をご利用のお客様は REST API を介してファーストパーティの [Looker Blocks](#looker-blocks) と [Looker Actions](#looker-actions) ユーザーフラグを利用できます。これらのフラグを立てたユーザーをセグメントに追加し、将来のBrazeキャンペーンやCanvasの[ターゲットにする](#segment-users)ことができる。Braze と Looker を使用するには、[Braze Currents を使用してデータウェアハウスに][6] Braze データを送信してから、Braze の Looker Blocks を使用して Looker で Braze データを迅速にモデル化して視覚化することを推奨します。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-|ルッカーアカウント | このパートナーシップを利用するには、[Lookerアカウントが](https://looker.com/)必要である。 |
+|Looker アカウント | このパートナーシップを活用するには、[Looker アカウント](https://looker.com/)が必要です。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに][1]依存する。 |
+| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは[インスタンスの Braze URL][1] に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 #### 制限事項
 
 - このプロセスは、ピボットされていないデータに対してのみ機能する。
 - APIは一度に最大100,000行を処理する。
-- 重複や非ユーザーのため、最終的なユーザーフラグのカウントは低くなる可能性がある。
+- ユーザーの最終的なフラグの数は、重複や非ユーザーが原因で少なくなる可能性があります。
 
 ## 統合
 
-### ルッカーブロック
+### Looker Blocks
 
-当社のLooker Blocksは、Brazeの顧客が[Currentsを通じて][5]提供する詳細なデータのビューに素早くアクセスするのに役立つ。Brazeのブロックは、Currentsデータ用にあらかじめ作成されたビジュアライゼーションとモデリングを提供するため、Brazeの顧客は、リテンションなどの分析パターンの実装、メッセージ配信性の評価、ユーザー行動のより詳細な調査などを簡単に行うことができる。
+Looker Blocks により、Braze のお客様は [Currents][5] で当社から提供される詳細なデータのビューに素早くアクセスできるようになります。Braze のブロックは、Currents データ用に事前に作成されている視覚化とモデリング機能を提供します。これにより、Braze のお客様は、リテンションなどの分析パターンを容易に実装し、メッセージの配信可能性を評価し、ユーザーの行動をより細かく確認することなどができるようになります。
 
 Looker Blocksを実装するには、GitHubコードのREADMEファイルの指示に従う。
 - [メッセージ・エンゲージメント分析ブロック README][2]
 - [ユーザー行動分析ブロック README][3]
 
-どちらの統合も、[最初のBrazeとの統合][4]、およびBrazeとLooker互換の[データウェアハウスとの][7]統合が、必要なデータを取り込み、送信するように適切に設定されていることを前提としている。
+どちらの統合も、[初回の Braze 統合][4]と、Looker 互換の[データウェアハウス][7]と Braze の統合が、必要なデータを取り込んで送信するように適切に設定されていることを前提としています。
 
 
 {% alert important %}
@@ -54,27 +54,27 @@ Brazeは[Snowflakeを](https://www.snowflake.com/)データウェアハウスと
 
 | ブロック | 説明 |
 |---|---|
-| メッセージ・エンゲージメント分析ブロック | このブロックには、プッシュ、Eメール、アプリ内メッセージ、ウェブフック、ニュースフィード、コンバージョン、キャンバスエントリー、キャンペーンコントロールグループの登録イベントに関するデータが含まれる。<br><br>この[Looker Blockの](https://looker.com/platform/blocks/source/message-engagement-analytics-by-braze?latest&utm_campaign=7012R000000fxfC&utm_source=other&utm_medium=email&utm_content=brazedirectreferral&utm_term=braze_direct)詳細については、[GitHubのコードを](https://github.com/llooker/braze_message_engagement_block)チェックしてほしい。 |
-| ユーザー行動分析ブロック | このブロックには、カスタムイベント、購入、セッション、ロケーションイベント、アンインストールに関するデータが含まれる。<br><br>この[Looker Blockの](https://looker.com/platform/blocks/source/user-behavior-analytics-by-braze?latest&utm_campaign=7012R000000fxfC&utm_source=other&utm_medium=email&utm_content=brazedirectreferral&utm_term=braze_direct)詳細については、[GitHubのコードを](https://github.com/llooker/braze_retention_block)チェックしてほしい。 |
+| メッセージ・エンゲージメント分析ブロック | このブロックには、プッシュ、Eメール、アプリ内メッセージ、ウェブフック、ニュースフィード、コンバージョン、キャンバスエントリー、キャンペーンコントロールグループの登録イベントに関するデータが含まれる。<br><br>この [Looker ブロック](https://looker.com/platform/blocks/source/message-engagement-analytics-by-braze?latest&utm_campaign=7012R000000fxfC&utm_source=other&utm_medium=email&utm_content=brazedirectreferral&utm_term=braze_direct)の詳細については、[GitHub のコード](https://github.com/llooker/braze_message_engagement_block)をご確認ください。 |
+| ユーザー行動分析ブロック | このブロックには、カスタムイベント、購入、セッション、ロケーションイベント、アンインストールに関するデータが含まれる。<br><br>この [Looker ブロック](https://looker.com/platform/blocks/source/user-behavior-analytics-by-braze?latest&utm_campaign=7012R000000fxfC&utm_source=other&utm_medium=email&utm_content=brazedirectreferral&utm_term=braze_direct)の詳細については、[GitHub のコード](https://github.com/llooker/braze_retention_block)をご確認ください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-### ルッカーのアクション
+### Looker Actions
 
-Looker Actionsを使用すると、Looker LookからREST APIエンドポイント経由でBraze内のユーザーにフラグを立てることができる。アクションでは、ディメンジョンに`braze_id` というタグが付けられる必要がある。アクションは、フラグを立てた値をユーザーのカスタム属性（`looker_export` ）に追加する。
+Looker Actions を使用すると、Looker Look から REST API エンドポイントを介して Braze 内のユーザーにフラグを設定することができます。アクションを使用するには、ディメンションに `braze_id` というタグが付けられている必要があります。アクションは、フラグを立てた値をユーザーのカスタム属性（`looker_export` ）に追加する。
 
 {% alert important %}
 フラグが立つのは既存のユーザーだけだ。Brazeでデータにフラグを立てる場合、ピボット・ルックは使用できない。
 {% endalert %}
 
-#### ステップ1:ブレイズ・ルッカーのアクションをセットする
+#### ステップ1:Braze Looker アクションを設定する
 
-Braze REST APIキーとRESTエンドポイントを使用して、Braze Looker Actionを設定する。
+Braze REST API キーと REST エンドポイントを使用して、Braze Looker アクションを設定します。
 
-![Looker Brazeの設定ページ。ここには、Braze APIキーとBraze REST APIエンドポイントのフィールドがある。][12]
+![Looker Brazeの設定ページ。Braze API キーと Braze REST API エンドポイントのフィールドがある。][12]
 
 #### ステップ2:Looker Developをセットアップする
 
-Looker Develop 内で、適切なビューを選択する。dimensionsタグに`braze_id` 、変更をコミットする。
+Looker Develop 内で、適切なビューを選択する。ディメンションタグに `braze_id` を追加し、変更をコミットします。
 この`braze_id` タグは、どのフィールドがユニークキーであるかを決定するために使用される。
 
 ```json
@@ -86,38 +86,38 @@ dimension: external_id {
 }
 ```
 
-**必ず変更をコミットすること。Looker Actionはプロダクションの設定でのみ機能する。**
+**必ず変更をコミットすること。Looker アクションは本番環境の設定でのみ機能します。**
 
 #### ステップ3:タグにユーザー属性を設定する
 
-オプションで、`braze[]` タグを使って、属性名を括弧で囲んで設定することもできる。例えば、カスタム属性`user_segment` を送信したい場合、タグは`braze[user_segment]` となる。
+オプションで、`braze[]` タグを使用し、属性名を括弧で囲んで属性を設定することもできます。たとえば、カスタム属性 `user_segment` を送信する場合、タグは `braze[user_segment]` になります。
 
 以下の制限に注意：
-- 属性は、**ルック内のフィールドとして含まれている**場合にのみ送信される。
-- サポートされるタイプは`Strings` 、`Boolean` 、`Numbers` 、`Dates` である。
+- 属性は、**Look 内のフィールドとして含まれている**場合にのみ送信されます。
+- サポートされているタイプは`Strings`、`Boolean`、`Numbers`、`Dates` です。
 - 属性名は大文字と小文字を区別する。
 - 標準[ユーザープロファイル]({{site.baseurl}}/api/endpoints/user_data/#braze-user-profile-fields)名と完全に一致する限り、標準属性も設定できる。
-- 完全なタグは引用符で囲む。例えば、`tags: ["braze[first_name]"]` 。他のタグを割り当てることもできるが、無視される。
-- 追加情報は[GitHubで](https://github.com/looker/actions/tree/master/src/actions/braze)見ることができる。
+- 完全なタグは引用符で囲む。例: `tags: ["braze[first_name]"]`。他のタグを割り当てることもできるが、無視される。
+- 追加情報は [GitHub](https://github.com/looker/actions/tree/master/src/actions/braze) で確認できます。
 
-#### ステップ 4:ルッカーのアクションを送信する
+#### ステップ 4:Looker アクションを送信する
 
-1. `braze_id` ディメンジョンを選択したルック内で、右上の設定ギア (<i class="fas fa-cog"></i> ) をクリックし、**Send.**.. を選択する**。**
-2. カスタムブレイズアクションを選択する。
-3. **Unique Keyの**下に、Brazeアカウントのプライマリユーザーマッピングキー（`external_id` または`braze_id` ）を入力する。
-4. エクスポートに名前をつける。指定がない場合は、`LOOKER_EXPORT` 。
-5. **Advanced Options（詳細オプション）**」で、**「Results in Table（テーブル内の結果**）」または「**All Results（すべての結果）**」を選択し、「**Send（送信）**」を選択する。<br><br>![][13]<br><br>エクスポートが正しく送信されていれば、`LOOKER_EXPORT` 、アクションで入力した値がカスタム属性としてユーザーのプロファイルに表示されるはずだ。<br><br>![][14]
+1. `braze_id` ディメンションが選択されている Look 内で、右上の設定の歯車 (<i class="fas fa-cog"></i>) をクリックし、[**Send...**] を選択します。
+2. カスタム Braze アクションを選択します。
+3. \[**Unique Keｙ**] で Braze アカウントのプライマリユーザーマッピングキー (`external_id` または`braze_id`) を入力します。
+4. エクスポートに名前をつける。指定されない場合は `LOOKER_EXPORT` が使用されます。
+5. **Advanced Options（詳細オプション）**」で、**「Results in Table（テーブル内の結果**）」または「**All Results（すべての結果）**」を選択し、「**Send（送信）**」を選択する。<br><br>![][13]<br><br>エクスポートが正しく送信された場合、`LOOKER_EXPORT` は、アクションに入力された値を含むカスタム属性としてユーザーのプロファイルに表示されます。<br><br>![][14]
 
-##### 送信APIの例
+##### 送信 API の例
 
-以下は発信APIコールの例で、[`/users/track/` エンドポイントに][10]送られる。
+以下に、[`/users/track/` エンドポイント][10]に送信される送信 API 呼び出しの例を示します。
 
 ###### ヘッダー
 ```
 Authorization: Bearer [API_KEY]
 ```
 
-###### ボディ
+###### 本文
 ```json
 {
    "attributes" : [
@@ -141,24 +141,24 @@ Authorization: Bearer [API_KEY]
 }
 ```
 
-### Brazeのセグメントユーザー {#segment-users}
+### Braze でユーザーをセグメント化する {#segment-users}
 
-Brazeで、これらのフラグを付けたユーザーのセグメントを作成するには、**Engagementの** **Segmentsに**移動し、セグメントに名前を付け、フィルターとして**Looker_Exportを**選択する。次に、"includes value "オプションを使い、Lookerで割り当てたカスタム属性フラグを指定する。
+Braze で、これらのフラグが設定されたユーザーのセグメントを作成するには、\[**エンゲージメント**] の下の \[**セグメント**] に移動し、セグメントに名前を付け、フィルターとして \[**Looker_Export**] を選択します。次に、"includes value "オプションを使い、Lookerで割り当てたカスタム属性フラグを指定する。
 
-![Brazeセグメントビルダーで、フィルター "looker_export "を "includes_value "と "Looker "に設定する。][15]
+![Braze セグメントビルダーで、フィルター \[looker_export] に \[includes_value] と \[Looker] が設定されている。][15]
 
 一度保存すれば、キャンバスやキャンペーン作成時に、ユーザーをターゲティングするステップでこのセグメントを参照することができる。
 
 ## トラブルシューティング
-Lookerアクションに問題がある場合、テストユーザーを\[internal groups][16] ] に追加し、以下を確認する：
+Looker アクションに問題がある場合、テストユーザーを\[内部グループ][16]に追加し、以下を確認します。
 
 * APIキーには`users.track` の権限がある。
-* 正しいRESTエンドポイントは、`https://rest.iad-01.braze.com` のように入力する。
-* `braze_id` タグがディメンジョン・ビューに設定される。
-* クエリには、Id ディメンジョンまたは属性が列として含まれている。
+* 正しい REST エンドポイントが入力されている (例: `https://rest.iad-01.braze.com`)。
+* ディメンションビューで `braze_id` タグが設定されている。
+* クエリには、Id ディメンションまたは属性が列として含まれている。
 * ルッカーの結果はピボットされない。
-* ユニークキーは正しく選択されている。通常、`external_id` 。
-* `braze_id` `braze_id` ディメンジョン内の`braze_id` は、Braze APIの`id` フィールドであることを示すために使用される。ほとんどの場合、送信時`external_id` が主キーとなる。
+* ユニークキーは正しく選択されている。通常は `external_id` です。
+* ディメンションの `braze_id` は API の `braze_id` とは異なる。ディメンションの `braze_id` は、Braze API の `id` フィールドであることを示すために使用されます。ほとんどの場合、送信時には `external_id` がプライマリキーとなります。
 * `external_id` ユーザーはBrazeプラットフォームに存在する。
 * `looker_export` フィールドは`Braze Platform > Settings > Manage Settings > Custom Attributes` の下に`Automatically Detect` として設定されている。
 * 変更はプロダクションにコミットされる。Looker Actionは本番環境でも機能する。
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/merkury.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/merkury.md
index 305ea70d275..2963d7ec07c 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/merkury.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/merkury.md
@@ -1,58 +1,58 @@
 ---
-nav_title: マーキュリー
-article_title: マーキュリー
+nav_title: Merkury
+article_title: Merkury
 description: "この参考記事では、Brazeとアプリ向けエンタープライズIDプラットフォームであるMerkuryのパートナーシップについて概説している。Brazeの顧客は、`MerkuryID`を活用してサイト訪問者の認識率を高めることができる。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# マーキュリー
+# Merkury
 
-> [Merkuryは](https://merkury.merkleinc.com/)Merkleのエンタープライズ・アイデンティティ・プラットフォームであり、ファーストパーティのCookieレス・アイデンティティ機能を通じて、ブランドが消費者とのエンゲージメント、エクスペリエンス、収益を最大化できるよう支援する。`MerkuryID` は、ブランドの既知・未知の顧客や見込み客の記録、サイトやアプリの訪問履歴、消費者データを単一の永続的な個人IDに統合する。
+> [Merkury](https://merkury.merkleinc.com/) は、Merkle のエンタープライズアイデンティティプラットフォームです。ファーストパーティ Cookie レスアイデンティティ機能により、ブランドが消費者とのやり取り、エクスペリエンス、収益を最大化できるように支援します。`MerkuryID` は、ブランドの既知および未知の顧客と見込み客のレコード、サイトやアプリの訪問履歴、および消費者データを、1つの永続的な個人 ID に統合します。
 
-BrazeとMerkuryの統合により、`MerkuryID` 、Brazeの顧客のサイト訪問者の認識率を高めることができる。ブランドのEメール購読者である訪問者を認識すると、MerkuryはBrazeのプロフィールを更新し、購読者のEメールアドレスを含める。`MerkuryID` の認識能力の向上は、エンゲージメントとパーソナライゼーションの機会を改善し、サイト放棄メールの送信量と関連収益を即座に増加させる。 
+Braze と Merkury の統合により、`MerkuryID` を活用して、Braze のお客様のサイト訪問者認識率を向上させることができます。Merkury はブランドのメールサブスクライバーである訪問者を認識すると、Braze プロファイルを更新し、サブスクライバーのメールアドレスをプロファイルに含めます。`MerkuryID` の認識機能の向上により、エンゲージメントとパーソナライゼーションの機会が拡大し、送信されるサイト放棄メールの量と関連収益がすぐに増加します。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | --- | --- |
-| メルクルアカウント | このパートナーシップを利用するには、メルクルのアカウントが必要である。 |
-| メルクル・クライアントID | Merkleの担当者からクライアントIDを取得する。 |
-| マーキュリータグ | MerkleのMerkuryタグをウェブサイトに設置する。 |
-| Braze RESTおよびSDKエンドポイント | RESTまたはSDKのエンドポイントURL。エンドポイントは、[インスタンスのBraze URLに]({{site.baseurl}}/api/basics/#endpoints)依存する。 |
-| Braze REST API キー | `users.track, users.export.ids, users.export.segment, and segments.list` 権限を持つ Braze REST API キー。<br><br>これは、**Braze Dashboard > Developer Console > REST API Key > Create New API Keyで**作成できる。 |
+| Merkle アカウント | このパートナーシップを活用するには、Merkle アカウントが必要です。 |
+| Merkleクライアント ID | Merkle の担当者からクライアント ID を取得します。 |
+| マーキュリータグ | Merkle の Merkury タグを Web サイトに配置します。 |
+| Braze RESTおよびSDKエンドポイント | RESTまたはSDKのエンドポイントURL。エンドポイントはインスタンスの [Braze URL]({{site.baseurl}}/api/basics/#endpoints) に応じて異なります。 |
+| Braze REST API キー | `users.track, users.export.ids, users.export.segment, and segments.list` 権限を持つ Braze REST API キー。<br><br>これは **Brazeダッシュボード > \[開発者コンソール] > \[REST API キー] > \[新しい API キーを作成]** で作成できます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 {% alert important %}
-BrazeへのMerkury IDコネクタのリクエストは、Braze APIレート制限仕様内で動作する。ご不明な点があれば、BrazeまたはMerkleのアカウントマネージャーにお問い合わせいただきたい。<br><br>Merkuryは資格のあるセッションの最後に少なくとも1つのリクエストを送る。
+Braze への Merkury アイデンティティコネクターのリクエストは、Braze API レート制限仕様の範囲内で動作します。ご質問がある場合は、Braze または Merkle アカウントマネージャーにお問い合わせください。<br><br>Merkuryは、適格なセッションの終了時に少なくとも1つのリクエストを送信します。
 {% endalert %}
 
-## サイド・バイ・サイドのSDK統合
+## サイドバイサイドの SDK 統合
 
-MerkleのクライアントサイドMerkuryタグを使用してBrazeデバイスをキャプチャし、識別のためにMerkury IDコネクタエンドポイントに転送する。
+Merkle のクライアントサイド Merkury タグを使用して Braze デバイスをキャプチャし、識別のためにMerkury ID コネクターエンドポイントに転送します。
 
 ### ステップ1:BrazeウェブSDKタグを設定する
 
-この統合を使用するには、ウェブサイトに[Braze Web SDKを]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/#install-gtm)デプロイする必要がある。
+この統合を使用するには、Web サイトに[Braze Web SDK]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/#install-gtm) を導入している必要があります。
 
-### ステップ2:MerkleのMerkuryタグを展開する
+### ステップ2:Merkle の Merkury タグを導入する
 
-Merkuryタグをウェブサイトに配置する。これにより、あなたのウェブサイトでMerkury IDコネクターが利用できるようになる。メルクルアカウントマネージャーより、詳細なガイドが提供される。
+Merkuryタグをウェブサイトに配置する。これにより、Merkury アイデンティティコネクターが Web サイトで使用できるようになります。Merkle アカウントマネージャーから、手順を含む詳細なガイドが提供されます。
 
 ### ステップ3:カスタム属性を作成する
 
-以下のフィールドはMerkury Identity Connectorによって入力されるため、Brazeで[カスタム属性として]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes#custom-attributes)作成する必要がある。
+以下のフィールドは Merkury アイデンティティコネクターによって入力され、Braze で[カスタム属性]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes#custom-attributes) として作成する必要があるものです。
 
 | 属性名 | データタイプ | 説明 |
 | --- | --- | --- |
-| `hmid` | String | メルクルのメルクリーID |
-| `confidence_score` | 数値 | メルクリーがどの程度自信を持って識別できたか（1～8、低いほど良い） |
+| `hmid` | String | Merkle の Merkury ID |
+| `confidence_score` | 数値 | Merkury がどの程度の信頼度で識別できたか (1～8、小さいほど良い) |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-### ステップ4:MerkleにユーザーEメールユニバースを提供する
+### ステップ4:Merkle にユーザーメールユニバースを提供する
 
-Merkleは、許可されたメールユニバースのセグメンテーションエクスポートを推奨している。これは、アクティブな許容ユーザーの日次エクスポートでフォローアップできる。
+Merkle では、許容されるメールユニバースのセグメンテーションエクスポートが推奨されています。これは、アクティブな許容ユーザーの日次エクスポートでフォローアップできる。
 
 以下のフィールドは必須である：
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents.md
index 71205549003..4c38f4cb8f9 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents.md
@@ -2,7 +2,7 @@
 nav_title: Mixpanel
 article_title: Mixpanel
 alias: /partners/mixpanel_for_currents/
-description: "このリファレンス記事では、Braze と業務分析 プラットフォームであるMixpanel との提携の概要を説明します。これにより、Mixpanel コホートをBraze に読み込んで、将来のBraze キャンペーンs またはキャンバスでユーザーs をターゲットにするために使用できるBraze Segments を作成できます。"
+description: "このリファレンス記事では、Braze と Mixpanel のパートナーシップについて説明します。Mixpanel はビジネス分析プラットフォームであり、Mixpanel コホートを Braze にインポートして Braze セグメントを作成できます。作成したセグメントは、今後の Braze キャンペーンやキャンバスでユーザーをターゲットにするために使用できます。"
 page_type: partner
 search_tag: Partner
 tool: Currents
@@ -11,51 +11,51 @@ tool: Currents
  
 # [![Brazeラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/mixpanel-integration-with-braze/339085/scorm/2u7y2e6qrldh2){: style="float:right;width:120px;border:0;" class="noimgborder"}Mixpanel
 
-> [Mixpanel](https://mixpanel.com/) は、Mixpanel から他のプラットフォームs にイベントをエクスポートして、より深い解析を実行できるビジネス分析 プラットフォームです。収集されたデータは、カスタムレポートs を構築し、ユーザー エンゲージメントとリテンションを測定するために使用できます。
+> [Mixpanel](https://mixpanel.com/) はビジネス分析プラットフォームであり、Mixpanel から他のプラットフォームにイベントをエクスポートして、より深い解析を実行できます。収集されたデータは、カスタムレポートの作成やユーザーエンゲージメントとリテンションの測定に使用できます。
 
-Braze とMixpanel を統合すると、[Mixpanel コホートをBraze]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/mixpanel/) にインポートして、将来のBraze キャンペーンs またはキャンバスでユーザーs をターゲットにするために使用できるBraze Segments を作成できます。また、[ へのBraze Currentsを活用して、Brazeの行動をMixpanel](#data-export-integration) にエクスポートし、コンバージョンのs、リテンション、および商品の使用状況をより深く分析することもできます。 
+Braze と Mixpanel の統合により、[Mixpanel コホートを Brazeにインポートして]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/mixpanel/) Braze セグメントを作成できます。このセグメントは、今後の Braze キャンペーンやキャンバスでユーザーをターゲットにするために使用できます。Braze Currents を利用して [Braze イベントを Mixpanel にエクスポート](#data-export-integration)し、コンバージョン、リテンション、製品使用率に関する詳細な分析を促進することもできます。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| Mixpanelアカウント | この提携の前倒しタグを行うには、[Mixpanelアカウント](https://mixpanel.com/)が必要です。 |
-| Currents | データをMixpanel に書き戻すには、アカウントに[Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
+| Mixpanelアカウント | このパートナーシップを活用するには、[Mixpanel アカウント](https://mixpanel.com/)が必要です。 |
+| Currents | Mixpanel にデータを再度エクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2} 
 
 ## データエクスポート統合
 
-Braze からミックスパネルにエクスポートできるイベントの一覧は、以下のとおりです。Mixpanel に送信されるすべてのイベントには、ユーザーの`external_user_id` がMixpanel の識別ID として含まれます。このとき、Braze は`external_user_id` が設定されていないユーザーs のイベントデータを送信しません。
+Braze から Mixpanel にエクスポートできるすべてのイベントを以下に示します。Mixpanel に送信されるすべてのイベントには、ユーザーの`external_user_id` が Mixpanel Distict ID として含まれます。このとき、Braze は`external_user_id` が設定されていないユーザーs のイベントデータを送信しません。
 
-ミックスパネルには2 種類のイベントを書き出すことができます。[メッセージエンゲージメントイベント](#supported-currents-events) メッセージ送信に直接的に関連するBrazeイベント、および[カスタマービヘイビアイベント](#supported-currents-events) には、セッション s、カスタムイベント、およびプラットフォーム経由で追跡された購買などの他のアプリやWeb サイトアクティビティが含まれます。すべてのカスタムイベントs には、`[Braze Custom Event]` が接頭辞として付加されます。カスタムイベントプロパティと購入イベントプロパティのプレフィックスは、それぞれ`[Custom event property]` と`[Purchase property]` です。
+Mixpanel にエクスポートできるイベントは2種類あります。[メッセージエンゲージメントイベント](#supported-currents-events) (メッセージ送信に直接関連する Braze イベントで構成される) と、[顧客行動イベント](#supported-currents-events) (セッション、カスタムイベント、プラットフォーム経由で追跡された購入などのその他のアプリまたは Web サイトアクティビティを含む) です。すべてのカスタムイベントには、接頭辞として `[Braze Custom Event]` が付いています。カスタムイベントプロパティの接頭辞は `[Custom event property]`、購入イベントプロパティの接頭辞は `[Purchase property]` です。
 
 その他のイベントの種類にアクセスする必要がある場合は、アカウントマネージャーに問い合わせるか、[サポートチケット][support]を開いてください。
 
-### ステップ1:ミックスパネル認証情報を取得
+### ステップ1:Mixpanel 認証情報を取得する
 
-ミックスパネルダッシュボードで、新規または既存のプロジェクトの**プロジェクト設定**を選択します。ここにMixpanel API シークレットとMixpanel トークンがあります。これらの認証情報は、次回のステップでCurrentsコネクションを作成するために使用されます。 
+Mixpanel ダッシュボードで、新規または既存のプロジェクトの \[**Project Settings**] をクリックします。ここにMixpanel API シークレットとMixpanel トークンがあります。これらの認証情報は、次のステップで Currents 接続を作成するために使用します。 
 
-### ステップ2:Braze電流の作成
+### ステップ2:Braze Current を作成する
 
-Braze で、\*\*Currents > **\+ Create Current** > **Create Mixpanel Export** に移動します。一覧表示されているフィールドで、インテグレーションの名前、連絡先メール、Mixpanel API シークレット、およびMixpanel トークンを指定します。次に、追跡するイベントを選択します。使用可能なイベントのリストが表示されます。最後に、**Launch Current**をクリックします。
+Braze で \*\*\[Currents] > \[**\+ Currents を作成**] > \[**Mixpanel エクスポートを作成**] に移動します。表示されているフィールドに、統合名、連絡先メール、Mixpanel API シークレット、Mixpanel トークンを入力します。次に、追跡するイベントを選択します。使用可能なイベントのリストが表示されます。最後に \[**Currents を起動**] をクリックします。
 
-![BrazeミックスパネルのCurrents画面。このページには、インテグレーションの名前、連絡先メール、APIシークレット、およびMixpanelエクスポートトークンのフィールドが含まれます。Currents画面の下半分には、送信可能なCurrentsが表示されます。]({% image_buster /assets/img_archive/mixpanel4.png %}){: style="max-width:80%;"}
+![Braze Mixpanel Currents ページ。このページには、インテグレーションの名前、連絡先メール、APIシークレット、およびMixpanelエクスポートトークンのフィールドが含まれます。Currents ページの下半分には、送信可能なCurrents イベントが表示されている。]({% image_buster /assets/img_archive/mixpanel4.png %}){: style="max-width:80%;"}
 
 {% tab 注 %}
-詳細については、Mixpanel の[integration docs](https://help.mixpanel.com/hc/en-us/articles/360001243663) を参照してください。
+詳細については、Mixpanel の[統合に関するドキュメント](https://help.mixpanel.com/hc/en-us/articles/360001243663)を参照してください。
 {% endtab %}
 
-## 対応Currents
+## サポートされている Currents イベント
 
-Braze は、Currents [ ユーザーの動作]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/) および [ メッセージエンゲージメント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) イベント用語集の Mixpanel へのエクスポートをサポートしています。
+Braze では、Currents の[ユーザーの行動]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)および[メッセージエンゲージメント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)イベント用語集にある次のデータを Mixpanel にエクスポートすることがサポートされています。
 
 ### 行動
 - カスタムイベント: `users.behaviors.CustomEvent`
-- インストール属性: `users.behaviors.InstallAttribution`
+- インストールアトリビューション: `users.behaviors.InstallAttribution`
 - 場所: `users.behaviors.Location`
 - 購入: `users.behaviors.Purchase`
 - アンインストール: `users.behaviors.Uninstall`
-- アプリ(最初のセッション、セッションエンド、セッションスタート)
+- アプリ (初回セッション、セッション終了、セッション開始)
   - `users.behaviors.app.FirstSession`
   - `users.behaviors.app.SessionEnd`
   - `users.behaviors.app.SessionStart`
@@ -64,17 +64,17 @@ Braze は、Currents [ ユーザーの動作]({{site.baseurl}}/user_guide/data_a
   
 ### キャンペーン
 - 中止: `users_campaigns_abort`
-- 変換: `users.campaigns.Conversion`
-- 登録制御: `users.campaigns.EnrollInControl`
+- コンバージョン: `users.campaigns.Conversion`
+- EnrollinControl: `users.campaigns.EnrollInControl`
   
 ### キャンバス
 - 中止: `users_canvas_abort`
-- 変換: `users.canvas.Conversion`
-- 入力: `users.canvas.Entry`
-- 終了(一致したオーディエンス、実行されたイベント)
+- コンバージョン: `users.canvas.Conversion`
+- エントリ:: `users.canvas.Entry`
+- 離脱 (オーディエンス照合、実行済みのイベント)
   - `users.canvas.exit.MatchedAudience`
   - `users.canvas.exit.PerformedEvent`
-- 試験手順(コンバージョン、分割エントリ)
+- 実験ステップ (コンバージョン、分割エントリ)
   - `users.canvas.experimentstep.Conversion`
   - `users.canvas.experimentstep.SplitEntry`
 
@@ -85,7 +85,7 @@ Braze は、Currents [ ユーザーの動作]({{site.baseurl}}/user_guide/data_a
   - `users.messages.contentcard.Dismiss`
   - `users.messages.contentcard.Impression`
   - `users.messages.contentcard.Send`
-- メール(中止、バウンス、クリック、配信、マークスパム、開封、送信、ソフトバウンス、配信停止)
+- メール (中止、バウンス、クリック、配信、スパムとしてマーク、開封、送信、ソフトバウンス、配信停止)
   - `users.messages.email.Abort`
   - `users.messages.email.Bounce`
   - `users.messages.email.Click`
@@ -95,17 +95,17 @@ Braze は、Currents [ ユーザーの動作]({{site.baseurl}}/user_guide/data_a
   - `users.messages.email.Send`
   - `users.messages.email.SoftBounce`
   - `users.messages.email.Unsubscribe`
-- アプリ中(中止、押下、インプレッション)
+- アプリ内メッセージ (中止、クリック、インプレッション)
   - `users.messages.inappmessage.Abort`
   - `users.messages.inappmessage.Click`
   - `users.messages.inappmessage.Impression`
-- プッシュ通知(中止、跳ね返り、iOS フォアグラウンド、開封、送信)
+- プッシュ通知 (中止、バウンス、iOSforeground、開封、送信)
   - `users.messages.pushnotification.Abort`
   - `users.messages.pushnotification.Bounce`
   - `users.messages.pushnotification.IosForeground`
   - `users.messages.pushnotification.Open`
   - `users.messages.pushnotification.Send`
-- SMS(アボート、キャリア送信、配信、配信失敗、インバウンド受信、拒否、送信、ショートリンククリック)
+- SMS (中止、通信事業者の送信、配信、配信失敗、インバウンド受信、拒否、送信、ショートリンククリック)
   - `users.messages.sms.Abort`
   - `users.messages.sms.Delivery`
   - `users.messages.sms.DeliveryFailure`
@@ -116,7 +116,7 @@ Braze は、Currents [ ユーザーの動作]({{site.baseurl}}/user_guide/data_a
 - Webフック(中止、送信)
   - `users.messages.webhook.Abort`
   - `users.messages.webhook.Send`
-- WhatsApp(アボート、配信、障害、受信、読み取り、送信)
+- WhatsApp (中止、配信、障害、インバウンド受信、読み取り、送信)
   - `users.messages.whatsapp.Abort`
   - `users.messages.whatsapp.Delivery`
   - `users.messages.whatsapp.Failure`
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/npaw.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/npaw.md
index 4df5b9c1331..f3fc6474031 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/npaw.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/npaw.md
@@ -11,15 +11,15 @@ hidden: true
 
 # NPAW
 
-> [NPAW](https://nicepeopleatwork.com/)は、_素敵な勤務者_としても知られており、アクション可能なインサイトをオンラインメディアプロフェッショナルに提供するインテリジェントなデータ分析 プラットフォームです。NPAWのYOUBORAツールスイートにより、Braze 顧客は予測的で堅牢なAIを活用して、顧客行動をより深く理解し、プラットフォームS間のエンゲージメントを促進できるようになりました。
+> [NPAW](https://nicepeopleatwork.com/)は、_素敵な勤務者_としても知られており、アクション可能なインサイトをオンラインメディアプロフェッショナルに提供するインテリジェントなデータ分析 プラットフォームです。NPAW の YOUBORA ツールスイートにより、Braze をご利用のお客様は予測的で強力な AI を活用して顧客行動をより深く理解し、プラットフォーム間のエンゲージメントを促進できるようになります。
 
 # 前提条件
 
-| 要件   |Origin| 説明 |
+| 要件   |提供元| 説明 |
 | --------------|------|-------------|
-| YOUBORA APIキー |[YOUBORAの設定](https://youbora.nicepeopleatwork.com/users/login)|ユーザー登録時に生成されるAPI キーで、**設定** に配置できます。 |
-| ID |[Braze設定](https://dashboard.braze.com/sign_in) | YOUBORAでは、***Braze ID***、***外部ユーザID***、または***ユーザID***のいずれかを選択できます。 |
-| エンドポイント |[Braze設定](https://dashboard.braze.com/sign_in)| Braze ダッシュボードで設定可能な完全にカスタマイズ可能なURL エンドポイント。 |
+| YOUBORA APIキー |[YOUBORA の設定](https://youbora.nicepeopleatwork.com/users/login)|ユーザー登録時に生成されるAPI キーで、**設定** に配置できます。 |
+| ID |[Braze の設定](https://dashboard.braze.com/sign_in) | YOUBORA では、***Braze ID***、***外部ユーザー ID***、または***ユーザー ID*** のいずれかを使ってソフトウェアを Braze にリンクできます。 |
+| エンドポイント |[Braze の設定](https://dashboard.braze.com/sign_in)| Braze ダッシュボードで設定可能な完全にカスタマイズ可能なURL エンドポイント。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 # 分析の統合
@@ -37,10 +37,10 @@ Integration(統合)ページにアクセスしたら、スクロールダウン
 
 ![NPAW 統合]({% image_buster /assets/img/npaw_integration.png %})
 
-役得欄から集めたアプリの適切な情報を詳しく記入してください。
-* **Connector Name** は、将来この統合を参照するために使用される**英数字** 文字列です。この値は、****の文字と数字のみが含まれている限り、任意の値に設定できます。
+前提条件のセクションで確認した適切な情報を使用して詳細を入力します。
+* \[**Connector Name**] は、将来この統合を参照するために使用される**英数字**の文字列です。この値は、文字と数字**のみ**が含まれている限り、任意の値に設定できます。
 * **ユーザID**は、あなたのYOUBORAソフトとあなたのBrazeアカウントを結びつけるために以前に選ばれたIDです。たとえば、**Braze ID**でリンクを実行する場合は、ドロップダウンから**Braze ID**を選択して、適切なフィールドに値を割り当てます。
-* **API Key** は、**API** セクションの**Settings** にあるYOUBORA ツールスイートAPI Key です。
+* \[**API Key**] は、\[**API**] セクションの \[**Settings**] にある YOUBORA ツールスイートの API キーです。
 * **エンドポイント** は、以前にBraze ダッシュボード内で設定したカスタマイズ可能なURL エンドポイントです。
 
 すべてのフィールドが入力されたら、**Connect**ボタンをクリックしてコネクションを確立し、変更を保存します。
@@ -49,8 +49,8 @@ Integration(統合)ページにアクセスしたら、スクロールダウン
 
 Braze との統合の設定が完了したら、**Users** 製品に移動し、**Sample Manager** を**セクションマネージャ** 内で選択します。
 
-**Sample Manger**内にサンプルを作成した後、右側のトリプルドットアイコンをクリックすると、サンプル内のすべてのユーザーsをBrazeに送信できます。
+**Sample Manger** でサンプルを作成した後、右側の3つのドットのアイコンをクリックすると、サンプル内のすべてのユーザーを Braze に送信できます。
 
-![NPAW 標本マネージャー]({% image_buster /assets/img/npaw_sample_manager.png %})
+![NPAW Sample Manger]({% image_buster /assets/img/npaw_sample_manager.png %})
 
-これで、ユーザーsをBrazeに送った後、アクションを取ってキャンペーンsをユーザー Segmentsに集中させ、sを再びアクティブユーザーしたり、あなたの最も忠実なsやアクションにどんなユーザー Segmentでも連絡を取ることができます!
+ユーザーを Braze に送信したら、アクションを実行し、ユーザーセグメントへのキャンペーンに集中して取り組み、非アクティブなユーザーの再獲得、最も忠実なユーザーへのコンタクトなど、あらゆるユーザーセグメントに対するアクションを実行できます。
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/saleswings.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/saleswings.md
index d058f874c81..26296f29438 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/saleswings.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/saleswings.md
@@ -10,61 +10,61 @@ search_tag: Partner
 
 # SalesWings
 
-> [セールスウィングスは][1]、マーケティングチームと営業チームのために構築されたB2B SaaSリードプロファイリングアドオンであり、リードスコアリングとグレーディング、営業インサイトとアラート、マーケティングアライメント、B2Bアトリビューションレポートを通じて、リードとアカウントの資格認定を管理し、セールスフォースCRMとの緊密な統合を支援する。
+> [SalesWings][1] は、マーケティングチームとセールスチームを対象に構築された B2B SaaS リードプロファイリングアドオンです。Salesforce CRM と緊密に連携しており、リードスコアリングとリードグレーディング、セールスインサイトとセールスアラート、マーケティングとの連携、B2B アトリビューションレポートにより、リードとアカウントの適格性を管理するのに役立ちます。
 
-セールスウィングスによって、マーケティングチームとマーケティング・オペレーション・マネージャーは、営業チームのためにリードとアカウントを限定することができる。さらに、SalesWingsはBrazeとともに、リードのカスタマージャーニーとBrazeのマーケティングキャンペーンのエンゲージメントデータを営業担当者に提示することができる。
+SalesWings では、マーケティングチームとマーケティングオペレーションマネージャーが、営業チームのためにリードとアカウントの適格性を評価します。これは、営業とマーケティングの連携と効率化に不可欠です。さらに SalesWings と Braze の統合により、リードのカスタマージャーニーと、Braze マーケティングキャンペーンエンゲージメントを営業担当者に提示できるため、知識に基づく会話を通じてリードクオリフィケーション率を高めることができます。
 
 ## 前提条件
  
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| セールスウィングスアカウント | このパートナーシップを利用するには、[セールスウィングスの][1]アカウントが必要である。 |
+| SalesWings アカウント | このパートナーシップを活用するには、[SalesWings アカウント][1]が必要です。 |
 | Braze REST API キー | `users.export.ids` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][2]。エンドポイントは、インスタンスのBraze URLに依存する。 |
-| Segment.com アカウント（オプション） | Segment.com ユーザーであれば、リードのプロファイリングのために、すべてのリードのエンゲージメントとプロファイルデータを送信し、Segment.com を介してイベントを特定することができる。 |
+| Segment.com アカウント (オプション) | Segment.com をご利用の場合は、リードプロファイリングのために、すべてのリードエンゲージメントおよびプロファイルデータを送信し、Segment.com でイベントを特定することができます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
 {% tabs %}
-{% tab リード・スコアリング %}
+{% tab リードスコアリング %}
 
-SalesWingsは、[最先端のリードスコアリングと](https://www.saleswingsapp.com/braze-lead-scoring-and-sales-insights?utm_source=braze&utm_campaign=technicaldocs)リードグレーディング[機能により、](https://www.saleswingsapp.com/braze-lead-scoring-and-sales-insights?utm_source=braze&utm_campaign=technicaldocs)Brazeの顧客に[、リード、コンタクト、およびアカウントを認定する柔軟な方法を](https://www.saleswingsapp.com/braze-lead-scoring-and-sales-insights?utm_source=braze&utm_campaign=technicaldocs)提供する。すべてのリード認定データは、Salesforce CRMや、リード、コンタクト、アカウント、オポチュニティを管理しレポートしたいその他のシステムにネイティブにプッシュされる。
+SalesWings は、最先端のリードグレーディング機能と[リードスコアリング機能により、リード、取引先責任者、アカウントを選別する柔軟な方法](https://www.saleswingsapp.com/braze-lead-scoring-and-sales-insights?utm_source=braze&utm_campaign=technicaldocs)を Braze のお客様に提供します。すべてのリードクオリフィケーションデータは、Salesforce CRM や、リード、取引先責任者、アカウント、商談を管理および報告するその他のシステムにネイティブにプッシュされます。
 
-![セールスウィングス]({% image_buster /assets/img/saleswings/example_lead_scoring_builder_braze_lead_scoring.png %}) におけるシンプルなクリック・ノットコード・リードスコアリングモデルの例
+![SalesWings のシンプルな click-not-code のリードスコアリングモデルの例]({% image_buster /assets/img/saleswings/example_lead_scoring_builder_braze_lead_scoring.png %})
 
-_セールスウィングスにおけるシンプルなクリック・ノットコード・リードスコアリングモデルの例_
+_SalesWings のシンプルな click-not-code リードスコアリングモデルの例_
 {% endtab %}
 {% tab 営業とマーケティングの連携 %}
-SalesWingsは、マーケティングチームがマーケティングで適格とされたリードを追跡し、選別し、営業チームに引き渡すことを可能にする。SalesWingsのデータはすべてSalesforceにネイティブにプッシュされ、既存のプロセスを微調整したり、リスト、レポート、フローなどを使って新しいプロセスを作成したりするのに活用できる。
+SalesWings では、マーケティングチームがマーケティング対象として適格なリードを追跡、選別し、営業チームに受け渡すことができます。SalesWingsのデータはすべてSalesforceにネイティブにプッシュされ、既存のプロセスを微調整したり、リスト、レポート、フローなどを使って新しいプロセスを作成したりするのに活用できる。
 
-![SalesWings リードスコアリングが、Salesforce]({% image_buster /assets/img/saleswings/prioritized_lead_or_contact_list_braze_lead_scoring.png %}) 内で、リードまたはコンタクトのリストに優先順位をつける例
+![SalesWings リードスコアリングにより、Salesforce 内部でネイティブに一連のリードまたは取引先担当者を優先順位付けする方法の例]({% image_buster /assets/img/saleswings/prioritized_lead_or_contact_list_braze_lead_scoring.png %})
 
-_SalesWingsのリードスコアリングが、Salesforce内でリードやコンタクトのリストに優先順位をつける例_
+_SalesWings リードスコアリングにより、Salesforce 内部でネイティブに一連のリードまたは取引先担当者を優先順位付けする方法の例_
 
-![SalesWingsのリードスコアリングがSalesforce]({% image_buster /assets/img/saleswings/prioritized_account_list_braze_lead_scoring.png %}) 内のアカウントリストに優先順位をつける例
+![SalesWings リードスコアリングにより、Salesforce 内部でネイティブに一連のアカウントを優先順位付けする方法の例]({% image_buster /assets/img/saleswings/prioritized_account_list_braze_lead_scoring.png %})
 
-_SalesWingsのリードスコアリングがSalesforceのアカウントリストに優先順位をつける例_
+_SalesWings リードスコアリングにより、Salesforce 内部でネイティブに一連のアカウントを優先順位付けする方法の例_
 {% endtab %}
-{% tab リードとアカウントの格付け %}
-SalesWingsによって、Brazeの顧客は、プロファイルデータ（通常はCRMデータ）に基づいてリードとアカウントを限定することができる。これは「リードグレーディング」、「フィットスコアリング」、「ファームグラフィックスコアリング」とも呼ばれる。Brazeの顧客は、属性データを直接SalesWingsに送信することができ、SalesWingsは、Salesforce CRMの標準またはカスタムオブジェクトのデータとレコードを読み取り、全体的なプロファイルのスコアリングを行うことができる。
+{% tab リードとアカウントのグレーディング %}
+SalesWings では、Braze のお客様がプロファイルデータ (通常は CRM データ) に基づいてリードとアカウントを選別できます。これは「リードグレーディング」、「フィットスコアリング」、「ファームグラフィックスコアリング」とも呼ばれる。Braze のお客様は、属性データを直接 SalesWings に送信できます。SalesWings は、全体的なプロファイルスコアリングのために Salesforce CRM の標準オブジェクトまたはカスタムオブジェクトのデータとレコードを読み取ることができます。
 {% endtab %}
 {% tab 営業担当者のためのセールスインサイト %}
-SalesWingsは、リード、コンタクト、アカウントに関する営業インサイトを営業担当者に表示することができる（Marketo Sales Insightsの代替）。基本的には、ブレイズとウェブのエンゲージメント・データを営業チームに見せることができる。インサイトはSalesforce CRMにネイティブに組み込まれ、他のCRMやシステムにプッシュしたり、Brazeの電子メールを介して「セールスアラート」として送信することができる。
+SalesWings では、リード、取引先担当者、アカウントに関するセールスインサイトを営業担当者に対して表示できます (Marketo Sales Insights の代替)。基本的には、Braze および Web エンゲージメントデータを営業チームに対して表示できます。インサイトは Salesforce CRM にネイティブに組み込まれ、他の CRM やシステムにプッシュするか、Braze のメールで「セールスアラート」として送信することができます。
 
-![Salesforce 内の営業担当者向けの Sales Insights ビューの例（他の CRM システムでも利用可能）]({% image_buster /assets/img/saleswings/marketo_sales_insights_alternative_for_braze.png %})
+![Salesforce 内の営業担当者向けのセールスインサイトビューの例 (他の CRM システムでも利用可能)]({% image_buster /assets/img/saleswings/marketo_sales_insights_alternative_for_braze.png %})
 
 _Salesforce内の営業担当者向けセールスインサイトビューの例（他のCRMシステムでも利用可能）_
 {% endtab %}
 {% tab セールスアラート %}
-SalesWingsは、EメールとSlackのネイティブアラートを提供し、営業チームが日次、週次、月次のEメールレポートを取得するためにアクセスできるSalesforceのレポート購読を設定することができる。さらに、Zapierとの統合により、セールスウィングスのリードクオリフィケーションデータに基づいた追加ワークフローを構築することができる。
+SalesWings は、ネイティブメールと Slack アラートを提供します。Salesforce でレポートサブスクリプションを設定することで、営業チームがこのサブスクリプションを使用して日次、週次、月次のメールレポートを取得できます。さらに Zapier との統合により、SalesWings のリードクオリフィケーションデータに基づいた追加ワークフローを作成できます。
 
 ![Slackチャンネルによるセールスアラートの例]({% image_buster /assets/img/saleswings/smart_watch_alerts.png %})
 
 _Slackチャンネルを使ったセールスアラートの例_
 {% endtab %}
 {% tab Salesforce CRMのレポーティング %}
-SalesWingsとSalesforceの統合により、WebエンゲージメントデータとBrazeキャンペーンのエンゲージメントに基づいて、リード、コンタクト、アカウント、オポチュニティに関する自動化されたレポートを作成できる。例えば、特定のEメールキャンペーンをクリックした人、アプリやウェブサイトで特定のアクションを行った人など、ホットリードのリストを営業チームに見せることができる。
+SalesWings と Salesforce の統合により、Web エンゲージメントデータと Braze キャンペーンエンゲージメントに基づいて、リード、取引先担当者、アカウント、商談に関する自動レポートを作成できます。例えば、特定のEメールキャンペーンをクリックした人、アプリやウェブサイトで特定のアクションを行った人など、ホットリードのリストを営業チームに見せることができる。
 
 ![Salesforce内のBrazeのEメールとマーケティング・エンゲージメントにリンクしたダッシュボードの例で、Brazeのキャンペーンが販売結果と成果に与える影響を見る]({% image_buster /assets/img/saleswings/saleswings_email_campaign_attribution_dashboard.png %})
 
@@ -74,54 +74,54 @@ _Salesforce内のBrazeのEメールとマーケティングエンゲージメン
 
 ## 統合
 
-### ステップ1:セールスウィングスのアカウントと設定
+### ステップ1:SalesWings アカウントと設定
 
-フレンドリーなセールスウィングス・チームとの[デモを予約して][4]、セールスウィングスについてもっと知ろう。
+SalesWings について詳しく知るために、フレンドリーな SalesWings チームとの[デモをスケジュール][4]します。
 
 ### ステップ2:ウェブサイトやアプリに行動トラッキングを設置する
 
-現在、SalesWingsでリードスコアリングとセールスインサイトのために行動データを収集するには2つの方法がある：
-* [セールスウィングスのトラッキングJavaScriptを][5]、リードを追跡・特定したいウェブサイトやアプリに[導入する][5]。
-* セールスウィングスとの統合により、行動リードアクティビティデータ（およびリードプロファイルデータ）を送信する。 Segment.com
+現在、SalesWings でリードスコアリングとセールスインサイトのために行動データを収集するには、次の2種類の方法があります。
+* リードを追跡して特定したい Web サイトやアプリに、[SalesWings トラッキング JavaScriptを導入する][5]
+* SalesWings とSegment.com の統合を介して行動リードアクティビティデータ (およびリードプロファイルデータ) を送信する。
 
 ### ステップ 3:SalesWingsとBrazeを接続する
 
-[**セールスウィングスの設定**ページを][6]開き、**Braze Integration**セクションを展開する。
+[\[**SalesWings Settings**] ページ][6]に移動し、\[**Braze Integration**] セクションを展開します。
 
-![SalesWings SettingsページのBraze Integrationセクション。][7]
+![\[SalesWings Settings] ページの \[Braze Integration] セクション。][7]
 
 新しく作成したキーの**Identifier**列の値をコピーし、SalesWings**Braze Integration**セクションの**Braze APIキー**フィールドにペーストする。
 
-API and SDK endpoints article][8]]で説明されているように、Braze APIエンドポイントを追加し、**Braze APIエンドポイントフィールドに**入力する。**REST Endpoint**列の値をコピーし、SalesWings**Braze Integration**セクションの**Braze API endpoint**フィールドに入力する。
+\[API と SDK のエンドポイントの記事][8]での説明に従って Braze API エンドポイントを追加し、\[**Braze API endpoint**] フィールドにこのエンドポイントを入力します。**REST Endpoint**列の値をコピーし、SalesWings**Braze Integration**セクションの**Braze API endpoint**フィールドに入力する。
 
-その後、セールスウィングス設定の**Save Changesを**クリックする。
+次に、SalesWings 設定で \[**Save Changes**] をクリックします。
 
 ### ステップ4:Braze、CRMとの統合など、SalesWingsのリードスコアリングを設定する
 
-セールスウィングスのサービスチームに相談すれば、[ウェブサイトを][1]通じたフルオンボーディングサポートを受けることができる。
+[Web サイト][1]での完全なオンボーディングサポートについては、SalesWings のサービスチームにお問い合わせください。
 
 ## この統合を使う 
 
-リードスコアリングとセールスインサイトの作成をトリガーするために、セールスウィングスはウェブサイトやアプリでユーザーを特定する必要がある。これは以下のような形で起こりうる：
+リードスコアリングとセールスインサイトの作成をトリガーするために、SalesWings は Web サイトまたはアプリでユーザーを識別する必要があります。これは次の方法で行われます。
 
-- **フォームを提出する：**ユーザーがウェブフォームを送信すると、セールスウィングスは自動的にすべてのウェブフォームタイプ（ログイン、ダウンロード、お問い合わせなど）を識別し、ユーザーがフォームを送信した際のアイデンティティを解決する。 
+- **フォームの送信:**ユーザーが Web フォームを送信すると、SalesWings はすべての Webフォームタイプ (ログイン、ダウンロード、お問い合わせなど) を自動的に識別し、フォームの送信時にユーザーの身元を特定します。 
 - **Braze IDまたは外部IDを持つURLクリック：**ユーザーがBrazeのマーケティングアクション（通常、Eメールクリック、バナークリックなど）をクリックし、SalesWingsでトラッキングしているページに誘導する。
 - **GmailとOutlookのプラグイン（オプション）による販売メールのトラッキング：**営業担当者にEメール追跡プラグインを導入すれば、追跡可能なリンクを送信することで、ユーザーの完全なウェブサイト追跡が可能になる。
-- **Segment.com イベントを特定する（オプション）：**Segment.com ユーザーであれば、Segment.com の統合でユーザーのIDを解決することもできる。
+- **Segment.com 識別イベント (オプション)**Segment.com ユーザーの場合は、Segment.com 統合でユーザーの身元を特定することもできます。
 
 ### URLクリックからユーザーを特定する
 
 追跡可能なURL（例えば、EメールブラストやURL付きバナー）をクリックしたユーザーを自動的に特定することができる。URLを追跡可能にするには、リンクの末尾にパラメータとIDを追加して、Eメール、バナー、SMSでウェブサイトのURLを修正する2つの方法がある。
 
-1. `?braze_id=` 、その後に続く。 {% raw %}`{{${braze_id}}}`{% endraw %} 
+1. `?braze_id=` と {% raw %}`{{${braze_id}}}`{% endraw %} をこの順序で付加する 
   - **リンクの例** {% raw %}`https://www.your-website.com?braze_id={{${braze_id}}}`{% endraw %}<br><br>
 
-2. `?br_user_id=` 、その後に続く。 {% raw %}`{{${user_id}}}`{% endraw %}
+2. `?br_user_id=` と {% raw %}`{{${user_id}}}`{% endraw %} をこの順序で付加する
   - **リンクの例** {% raw %}`https://www.client-website.com?br_user_id={{${user_id}}}`{% endraw %}
 
-`braze_id` 変数には、Brazeが生成したユーザーの識別子が設定され、常に利用可能である。変数`br_user_id` は、システム内のユーザー識別子に設定されるため、特定のシナリオ（Braze SDKで作成された匿名ユーザーの場合など）では欠落する可能性がある。リンクに`braze_id` と`br_user_id` の両方が使用されている場合、セールスウィングスは`braze_id` パラメータのみを考慮する。
+`braze_id` 変数には、Braze により生成されたユーザーの識別子が設定されます。この変数はいつでも使用できます。`br_user_id` 変数には、システム内のユーザーの識別子が設定されます。この変数は、特定の状況 (Braze SDK により作成された匿名ユーザーなど) では使用されない可能性があります。リンクに `braze_id` と `br_user_id` の両方が使用されている場合、SalesWings は`braze_id` パラメーターのみを考慮します。
 
-コンフィギュレーションとさらなるトラブルシューティングについては、[セールスウィングスのサービスチームまで][1]お問い合わせください。
+設定とトラブルシューティングの詳細については、[SalesWings サービスチーム][1]に連絡して、オンボーディングサポートを受けてください。
 
 [1]: https://www.saleswingsapp.com/?utm_source=braze&utm_campaign=technicaldocs
 [2]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/scuba.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/scuba.md
index 31bb5855105..9a27a2babc1 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/scuba.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/scuba.md
@@ -1,7 +1,7 @@
 ---
 nav_title: スクーバ
 article_title: Scuba Analytics
-description: "このスキューバおよびBrazeテクニカルリファレンスでは、Brazeセグメントを使用してスキューバのリアルタイムデータインサイトを有効にする方法について説明します。"
+description: "この Scuba と Braze のテクニカルリファレンスでは、Braze Segments を使用して Scuba のリアルタイムデータインサイトをアクティブにする方法を説明します。"
 alias: /partners/scuba/
 page_type: partner
 search_tag: Partner
@@ -9,22 +9,22 @@ search_tag: Partner
 
 # Scuba Analytics
 
->[Scuba Analytics][1] は、高速時系列データ用に設計された、機械学習能力のあるフルスタックのデータ連携プラットフォームです。スクーバでは、ユーザーs(アクターとも呼ばれます)を選択的にエクスポートし、Braze プラットフォームに読み込むできます。Scuba では、カスタムアクタープロパティを使用して動作トレンドを分析し、さまざまなプラットフォーム間でデータを有効化し、マシンラーニングを使用して予測モデリングを実行します。
+>[Scuba Analytics][1] は、高速時系列データ向けに設計された、機械学習を採用したフルスタックのデータコラボレーションプラットフォームです。Scuba では、ユーザー (アクターとも呼ばれます) を選択的にエクスポートし、Braze プラットフォームにそれらのユーザーを読み込むことができます。Scuba では、カスタムアクタープロパティを使用して動作トレンドを分析し、さまざまなプラットフォーム間でデータを有効化し、マシンラーニングを使用して予測モデリングを実行します。
 
 ## 前提条件
 
-Braze でScuba Analytics を使用するには、以下が必要です。
+Braze で Scuba Analytics を使用するには、以下が必要です。
 
 - `users.track` 権限を持つ[Braze REST API キー]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/#rest-api-keys)。
-- `https://{scuba_hostname}/api/create_token` エンドポイントから取得できるScuba API トークン。
+- `https://{scuba_hostname}/api/create_token` エンドポイントから取得できる Scuba API トークン。
 
-## Brazeへのスキューバデータの読み込むアップ
+## Braze への Scuba データのアップロード
 
 {% alert important %}
-以下の要求はcurl を使用します。API リクエストの管理を向上させるには、Postman などのAPI クライアントを使用することをお勧めします。
+以下の要求はcurl を使用します。API リクエストの管理を改善するには、Postman などの API クライアントを使用することをお勧めします。
 {% endalert %}
 
-Braze にScuba データをアップロードするには、`https://scuba.pliant.io/a/scuba-connectors/prod/braze-activation` に対して`application/json` content-type を使用してPOST リクエストを行います。
+Braze に Scuba データをアップロードするには、`https://scuba.pliant.io/a/scuba-connectors/prod/braze-activation` に対して `application/json` content-type を使用して POST リクエストを行います。
 
 ```bash
 curl -X POST "https://scuba.pliant.io/a/scuba-connectors/prod/braze-activation" \
@@ -46,30 +46,30 @@ curl -X POST "https://scuba.pliant.io/a/scuba-connectors/prod/braze-activation"
 
 | placeholder             | 説明                                                                                                                                                                                     |
 |-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `BRAZE_API_ENDPOINT`    | カレントBrazeインスタンスのBraze REST エンドポイント URL。詳細については、[休止API キーs]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/#rest-api-keys)を参照してください。 |
+| `BRAZE_API_ENDPOINT`    | 現在の Braze インスタンスの Braze REST エンドポイント URL。詳細については、「[REST API キー]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/#rest-api-keys)」を参照してください。 |
 | `BRAZE_API_KEY`         | `users.track` 権限を持つBraze REST API キー。                                                                                                                                      |
 | `HOSTNAME`              | 現在のScuba インスタンスのホスト名。                                                                                                                                                    |
-| `SCUBA_API_TOKEN`       | スキューバAPI トークン。                                                                                                                                                                           |
-| `TABLE_NAME`            | データセットが属するテーブル。詳細については、[用語集を参照してください。データセットテーブル][3]。                                                                                                      |
-| `ACTOR_PROPERTY_NAME`   | データセットが属するアクタプロパティ。この名前に一致するデータのみが返されます。詳細については、[用語集を参照してください。アクタプロパティ][4]。                                             |
+| `SCUBA_API_TOKEN`       | Scuba API トークン。                                                                                                                                                                           |
+| `TABLE_NAME`            | データセットが属するテーブル。詳細については、[用語集:データセットテーブル][3]。                                                                                                      |
+| `ACTOR_PROPERTY_NAME`   | データセットが属するアクタプロパティ。この名前に一致するデータのみが返されます。詳細については、[用語集:アクタープロパティ ][4]。                                             |
 | `ACTOR_PROPERTY_FILTER` | アクタープロパティのオーディエンス検索フィルター。                                                                                                                                             |
-| `ACTOR_ID`              | データセットが属するアクタプロパティのID。このID は、Braze の`external_id` に一致します。詳細については、[用語集を参照してください。アクタ][5]。                                              |
-| `PERIOD_START`          | BQL 互換の日付としての開始期間。詳細については、[BQL構文および使用法][6]を参照してください。                                                                                                 |
-| `PERIOD_END`            | BQL 互換の日付としての終了期間。詳細については、[BQL構文および使用法][6]を参照してください。                                                                                                   |
-| `RECORD_LIMIT`          | **オプション**:返されるレコードの最大数。`scuba_record_limit` が省略された場合、Scuba は最大100 レコードを返します。これを変更するには、負でない数値を`scuba_record_limit` に割り当てます。    |
+| `ACTOR_ID`              | データセットが属するアクタプロパティのID。この ID は、Braze の`external_id` に一致します。詳細については、[用語集を参照してください。Actor][5].を参照してください。                                              |
+| `PERIOD_START`          | BQL 互換の日付としての期間開始日。詳細については、[BQL構文および使用法][6]を参照してください。                                                                                                 |
+| `PERIOD_END`            | BQL 互換の日付としての期間終了日。詳細については、[BQL構文および使用法][6]を参照してください。                                                                                                   |
+| `RECORD_LIMIT`          | **オプション**:返されるレコードの最大数。`scuba_record_limit` が省略された場合、Scuba は最大100件のレコードを返します。これを変更するには、負でない数値を `scuba_record_limit` に割り当てます。    |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ### デフォルト動作
 
-デフォルトでは、`update_existing_only` は`false` に設定されています。これにより、Braze内の既存のレコードが更新され、存在しないレコードの新規レコードが作成されます。Scuba が新しいレコードを作成しないようにするには、`update_existing_only` を`true` に設定します。
+デフォルトでは、`update_existing_only` は`false` に設定されています。これにより、Braze内の既存のレコードが更新され、存在しないレコードの新規レコードが作成されます。Scuba が新しいレコードを作成しないようにするには、`update_existing_only` を `true` に設定します。
 
-### レートリミット
+### レート制限
 
-スキューバアプリは、このエンドポイントに対して1分間にレート制限50,000件のリクエストが存在します。
+Scuba は、1分あたり50,000件のリクエストのレート制限をこのエンドポイントに適用します。
 
-## スキューバのビヘイビアーデータを使用したSegmentの作成
+## Scuba の行動データを使用したセグメントの作成
 
-[ データ](#uploading-your-scuba-data-to-braze) をアップロードすると、Scuba のビヘイビアーデータを使用してBraze でユーザー Segmentを作成できます。
+[データをアップロード](#uploading-your-scuba-data-to-braze)したら、Scuba の行動データを使用して Braze でユーザーセグメントを作成できます。
 
 ### ステップ1:新しいSegmentの作成
 
@@ -77,11 +77,11 @@ Braze で、**Audience** > **Segments** に移動し、**Segmentの作成** を
 
 ![Braze での新しいSegmentの作成。][501]
 
-### ステップ2:スクーバ属性を探して選択する
+### ステップ2:Scuba 属性を探して選択する
 
 **Segment Details** > **Filters**で、**Custom Attributes**を選択します。
 
-![「セグメント詳細」で「カスタム属性」フィルターを選択します。][502]
+![\[セグメントの詳細] での「カスタム属性」フィルターの選択。][502]
 
 **検索カスタム属性s**を選択し、前回のPOSTリクエストで使用したアクタープロパティの名前を選択します。
 
@@ -89,9 +89,9 @@ Braze で、**Audience** > **Segments** に移動し、**Segmentの作成** を
 
 ### ステップ3:属性の設定
 
-アクタープロパティの名前の隣に、演算子と数値(アプリであればライセンス可能)を選択します。これらの値は、Scuba で定義したアクタープロパティによって決定されます。完了したら、\[**保存**] を選択します。
+アクタープロパティ名の横で、演算子と値を選択します (該当する場合)。これらの値は、Scuba で定義したアクタープロパティによって決定されます。完了したら、\[**保存**] を選択します。
 
-![選択した操作と値の選択 ][504]
+![選択されているプロパティ名に対する演算子と値の選択。][504]
 
 [1]: https://scuba.io
 [3]: https://docs.scuba.io/glossary/dataset-table
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/snowplow.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/snowplow.md
index e9ea45b315f..33f18f2b89d 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/snowplow.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/snowplow.md
@@ -1,6 +1,6 @@
 ---
-nav_title: スノープラウ
-article_title: スノープラウ
+nav_title: Snowplow
+article_title: Snowplow
 description: "このリファレンス記事では、BrazeとSnowplowのパートナーシップについて説明します。Snowplowはオープンソースのデータ収集プラットフォームであり、Google Tag Managerのサーバーサイドタグ付けを通じてSnowplowイベントをBrazeに転送することができます。"
 alias: /partners/snowplow/
 page_type: partner
@@ -8,14 +8,14 @@ search_tag: Partner
 
 ---
 
-# スノープラウ
+# Snowplow
 
-> [Snowplow][1]は、リッチで高品質、低遅延のデータ収集のためのスケーラブルなオープンソースプラットフォームです。それは、企業ビジネスのために高品質で完全な行動データを収集するように設計されています。
+> [Snowplow][1] は、豊富で高品質、低レイテンシーのデータ収集のためのスケーラブルなオープンソースプラットフォームです。エンタープライズビジネスのための高品質で完全な行動データを収集するように設計されています。
 
-BrazeとSnowplowの統合により、ユーザーはGoogle Tag Managerのサーバーサイドタグ付けを通じてSnowplowイベントをBrazeに転送できるようになります。Snowplow Brazeタグを使用すると、Brazeにイベントを送信しながら、追加の柔軟性とコントロールを提供できます:
-- データに対するすべての変換の完全な可視性
-- 洗練を時間とともに進化させる能力
-- すべてのデータは、転送することを選択するまでプライベートクラウドに残ります。
+Braze と Snowplow の統合により、ユーザーは Google Tag Manager のサーバーサイドタグ設定を使用して Snowplow のイベントを Braze に転送できます。Snowplow Braze タグを使用すると、イベントを Braze に送信しながら、以下によって柔軟性とコントロール性を高めることができます。
+- データ上のすべての変換を完全に可視化する
+- 時間の経過とともに洗練度を高める
+- すべてのデータを転送するまでプライベートクラウドに残す
 - 豊富なタグライブラリと使い慣れたGoogle Tag Manager UIによるセットアップの容易さ
 
 Snowplowの豊富な行動データを活用して、Brazeで強力な顧客中心のインタラクションを促進し、リアルタイムでパーソナライズされたメッセージを配信します。
@@ -24,7 +24,7 @@ Snowplowの豊富な行動データを活用して、Brazeで強力な顧客中
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| スノープラウパイプライン | スノープロウパイプラインは稼働している必要があります。 |
+| Snowplow パイプライン | Snowplowパイプラインが稼働している必要があります。 |
 | Google Tag Managerサーバーサイド | GTM-SSをデプロイし、[GTM-SS用のSnowplowクライアント][2]をセットアップする必要があります。 |
 | Braze REST API キー | `users.track`の権限を持つBraze REST APIキー。<br><br> これはBrazeのダッシュボードで**設定** > **APIキー**から作成できます。 |
 | Braze REST エンドポイント | [あなたのRESTエンドポイントURL][3]。あなたのエンドポイントは、インスタンスのBraze URLに依存します。 |
@@ -33,7 +33,7 @@ Snowplowの豊富な行動データを活用して、Brazeで強力な顧客中
 ## ユースケース
 
 ### パーソナライズされた、アクションベースの配信
-Snowplowがデフォルトで収集する多数のリッチイベントのいずれかを使用するか、カスタムイベントを定義して、ビジネスにとって意味のある、さらに詳細な顧客ジャーニーを形成します。Snowplowの豊富な行動データを活用して顧客ファネルを設計し、マーケティングおよび製品チームの価値を引き出し、Brazeを通じてコンバージョンと製品使用を最大化するのに役立てます。
+Snowplow がデフォルトで収集する多数のリッチなイベントのいずれかを使用するか、カスタムイベントを定義して、ビジネスに適したより細かなカスタマージャーニーを形成します。Snowplowの豊富な行動データを活用して顧客ファネルを設計し、マーケティングおよび製品チームの価値を引き出し、Brazeを通じてコンバージョンと製品使用を最大化するのに役立てます。
 
 ### ダイナミックなセグメンテーション
 Snowplowの高品質な行動データに基づいてBrazeでダイナミックなオーディエンスを作成する:ユーザーが製品、アプリ、またはWebサイトでアクションを実行すると、Snowplowが収集するリアルタイムの行動データを活用して、Brazeの関連セグメントにユーザーを自動的に追加または削除できます。
@@ -51,9 +51,9 @@ Snowplowの高品質な行動データに基づいてBrazeでダイナミック
 
 #### タグ マネージャー ギャラリー
 
-近日公開！このタグはGTMギャラリーに含まれる承認待ちです。
+近日公開予定です。このタグを GTM ギャラリーに追加するための承認が保留中です。
 
-### ステップ2:Braze タグ setup
+### ステップ2:Braze タグの設定
 
 テンプレートをインストールしたら、BrazeタグをGTM-SSコンテナに追加します。
 
@@ -64,7 +64,7 @@ Snowplowの高品質な行動データに基づいてBrazeでダイナミック
 
 ## カスタマイズ
 
-### 必須タグパラメータ
+### 必須タグパラメーター
 
 次の表は、Brazeタグのセットアップに含める必要があるタグパラメータを一覧にしたものです。
 
@@ -82,8 +82,8 @@ Snowplowの高品質な行動データに基づいてBrazeでダイナミック
 | マッピングオプション | 説明 |
 | --------- | ----------- |
 | 自己記述イベントを含める | デフォルトでオンになっています。Snowplowの自己記述イベントデータがBrazeに送信されるイベントのプロパティオブジェクトに含まれるかどうかを示します。 |
-| スノープラウイベントコンテキストルール | BrazeタグがSnowplowイベントに関連付けられたコンテキストエンティティをどのように使用するかについて説明します。 |
-| 配列からエンティティを抽出する場合、単一の要素 | スノープロウエンティティは常に配列にあり、同じエンティティが複数イベントにアタッチされることがあります。このオプションは、配列に単一の要素しか含まれていない場合、その単一の要素を選択します。 |
+| Snowplow イベントコンテキストルール | BrazeタグがSnowplowイベントに関連付けられたコンテキストエンティティをどのように使用するかについて説明します。 |
+| 配列からエンティティを抽出する場合、単一の要素 | 複数の同一エンティティを1つのイベントにアタッチできるため、Snowplow エンティティは常に配列に格納されます。このオプションは、配列に単一の要素しか含まれていない場合、その単一の要素を選択します。 |
 | イベントオブジェクトにすべてのエンティティを含める | デフォルトでオンになっています。Brazeイベントのプロパティオブジェクト内のイベントに含まれるすべてのエンティティを含みます。このオプションを無効にして、個々のエンティティを選択して含めます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -96,7 +96,7 @@ Snowplowの高品質な行動データに基づいてBrazeでダイナミック
 | イベントプロパティルール | 説明 |
 | --------- | ----------- |
 | 共通イベントプロパティを含める | デフォルトで有効になっているこのオプションは、Brazeイベントのプロパティに[共通イベント定義][6]のイベントプロパティを自動的に含めるかどうかを設定します。 |
-| 追加のユーザー プロパティおよびイベント プロパティ マッピング ルール | クライアントイベントからプロパティキーと、マッピングしたいプロパティオブジェクトのキーを指定します（または、マッピングされたキーを空白のままにして同じ名前を保持します）。ここでキー`x-sp-tp2.p`パス表記を使用できます（例えば、`x-sp-tp2.p`はSnowplowイベントプラットフォーム、`x-sp-contexts.com_snowplowanalytics_snowplow_web_page_1.0.id`はSnowplowイベントページビューID（配列インデックス0）を示します。または、代替クライアントを使用する場合は非Snowplowプロパティを選択します）。<br><br>イベントプロパティマッピングルールはBrazeイベントプロパティオブジェクトに入力されます。|
+| 追加のユーザー プロパティおよびイベント プロパティ マッピング ルール | クライアントイベントからプロパティキーと、マッピングしたいプロパティオブジェクトのキーを指定します（または、マッピングされたキーを空白のままにして同じ名前を保持します）。ここではキーパス表記を使用できます (たとえば Snowplow イベントプラットフォームの場合は `x-sp-tp2.p`、Snowplow イベントページビュー ID (配列インデックス 0) の場合は `x-sp-contexts.com_snowplowanalytics_snowplow_web_page_1.0.id`、代替クライアントを使用する場合は Snowplow 以外のプロパティを選択します)。<br><br>イベントプロパティマッピングルールはBrazeイベントプロパティオブジェクトに入力されます。|
 | 一般的なユーザーのプロパティを含める| デフォルトで有効になっているこのオプションは、Brazeユーザー属性オブジェクトに共通イベント定義からの`user_data`プロパティを含めるかどうかを設定します。|
 | イベント時間プロパティ | このオプションを使用すると、イベント時間（ISO-8601形式）を入力するためのクライアントイベントプロパティを指定するか、空のままにして現在の時間（デフォルトの動作）を使用できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -106,7 +106,7 @@ Snowplowの高品質な行動データに基づいてBrazeでダイナミック
 Snowplowエンティティマッピングテーブルを使用すると、エンティティをBrazeで異なる名前に再マッピングし、イベントプロパティやユーザー属性オブジェクトに含めることができます。 
 
 エンティティは2つの異なる形式で指定できます:
-- メジャーバージョンの一致: `x-sp-contexts_com_snowplowanalytics_snowplow_web_page_1` ここで `com_snowplowanalytics_snowplow` はイベントベンダー、`web_page` はスキーマ名、`1` はメジャーバージョン番号です。`x-sp-` は必要に応じて省略することもできます。
+- メジャーバージョン一致: `x-sp-contexts_com_snowplowanalytics_snowplow_web_page_1`。ここで、`com_snowplowanalytics_snowplow` はイベントベンダー、`web_page` はスキーマ名、`1` はメジャーバージョン番号です。`x-sp-` は必要に応じて省略できます。
 - 完全なスキーマ一致: `iglu:com.snowplowanalytics.snowplow/webPage/jsonschema/1-0-0`
 <br><br>
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/tellius.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/tellius.md
index 177beac9c01..01893cd9f94 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/tellius.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/tellius.md
@@ -1,47 +1,47 @@
 ---
-nav_title: テリウス
-article_title: テリウス
+nav_title: Tellius
+article_title: Tellius
 alias: /partners/Tellius/
-description: "この参考記事では、Brazeと意思決定インテリジェンスおよび拡張分析プラットフォームであるTelliusの提携について概説している。これにより、BIエンジニアに頼ることなくデータを活用し、ダッシュボードを構築してインサイトを生成し、より良いマーケティングの意思決定を行うことができる。"
+description: "このリファレンス記事では、Braze と Tellius のパートナーシップについて説明します。Tellius は、意思決定インテリジェンスおよび拡張分析のプラットフォームであり、BI エンジニアに依存せずにデータを活用してダッシュボードを構築し、マーケティングに関してより的確な決定を行うためのインサイトを生成することができます。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# テリウス
+# Tellius
 
-> 意思決定インテリジェンスと拡張分析プラットフォームである[テリウスは](https://www.tellius.com/)、自然言語検索を使ってデータの疑問に答え、AI主導のガイド付き洞察で「なぜ」を深く理解することを可能にする。
+> [Tellius](https://www.tellius.com/) は意思決定インテリジェンスと拡張分析のプラットフォームであり、自然言語検索を使用してデータに関する質問に答え、AI を活用したガイド付きインサイトで「なぜ」を理解するためにさらに深く掘り下げることができるようにします。
 
-BrazeとTelliusの統合により、ユーザーはBIエンジニアに頼ることなくデータを活用し、ダッシュボードを構築し、より良いマーケティングの意思決定を行うための洞察を得ることができる。この統合には、BrazeのデータがSnowflakeに保存されている必要があり、Telliusはそこに直接接続し、ライブモード統合でクエリをプッシュダウンできる。
+Braze と Tellius の統合により、ユーザーは BI エンジニアに依存せずにデータを活用し、ダッシュボードを構築し、マーケティングに関してより的確な決定を行うためのインサイトを生成することができます。この統合には、BrazeのデータがSnowflakeに保存されている必要があり、Telliusはそこに直接接続し、ライブモード統合でクエリをプッシュダウンできる。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| テリウス口座 | この提携を利用するにはテリウス・アカウントが必要である。[無料トライアルで](https://www.tellius.com/free-trial/)テリアスの旅を始めよう|
-| スノーフレーク・データ共有プログラム | 現在Snowflakeをご利用のお客様は、BrazeのデータをSnowflakeインスタンスに取り込むためのSnowflakeデータ共有プログラムについて、Brazeの担当者に問い合わせる。|
-| 雪印メグミルクのアカウント | Snowflakeをご利用でないお客様は、お客様のBrazeデータにアクセスするためのSnowflake Readerアカウントのプロビジョニングについて、Brazeの担当者にお問い合わせください。|
+| Tellius アカウント | このパートナーシップを活用するには、Tellius アカウントが必要です。[無料トライアル](https://www.tellius.com/free-trial/)で Tellius を利用してみることができます。|
+| Snowflake データシェアリングプログラム | 現在Snowflakeをご利用のお客様は、BrazeのデータをSnowflakeインスタンスに取り込むためのSnowflakeデータ共有プログラムについて、Brazeの担当者に問い合わせる。|
+| Snowflake Reader アカウント | Snowflakeをご利用でないお客様は、お客様のBrazeデータにアクセスするためのSnowflake Readerアカウントのプロビジョニングについて、Brazeの担当者にお問い合わせください。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### ステップ1:スノーフレークを通じてブレイズにアクセスする
+### ステップ1:Snowflake から Braze へのアクセスを取得する
 
-Brazeはきめ細かい顧客データをSnowflakeに保存している。BrazeのSnowflakeデータ共有プログラムまたはSnowflakeリーダーアカウントを取得することで、Brazeのデータを活用してインサイトを生成することができる。 
+Brazeはきめ細かい顧客データをSnowflakeに保存している。Braze データを利用して、Braze Snowflake データシェアリングプログラムを使用するかまたは Snowflake Reader アカウントを取得してインサイトを生成できます。 
 
-[スノーフレークの統合に従って]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/)セットアップを行う。 
+「[Snowflake 統合]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/)」に従って設定を行います。 
 
 ### ステップ2:SnowflakeでTelliusとBrazeのデータを接続する
 
-以下のいずれかの方法で、TelliusをSnowflakeのBrazeデータに接続する：
+次のいずれかの方法で、Tellius を Snowflake の Braze データに接続します。
 
-- 直接アクセスできる：データをTelliusに読み込むには、[データセットを読み込む](https://help.tellius.com/article/jn6o59d5gk-load-datasets)のステップに従う。
-- OAuthアクセス：SnowflakeへのOAuthアクセスについては、[OAuth認証の](https://help.tellius.com/article/11517w63b6-oauth-authentication-for-snowflake)ステップに従う。
+- 直接アクセス:Tellius にデータを読み込むため、[データセットの読み込み](https://help.tellius.com/article/jn6o59d5gk-load-datasets)の手順に従います。
+- OAuthアクセス：Snowflake への OAuth アクセスの場合は、[OAuth 認証](https://help.tellius.com/article/11517w63b6-oauth-authentication-for-snowflake)の手順に従います。
 
 ### ステップ3:読み込んだデータからTelliusでビジネス・ビューを作成する
 
-自然言語検索と自動化されたインサイトを使い始めるには、[ビジネスビューを](https://help.tellius.com/article/hy9yvh5tom-create-business-view)作成し、Snowflake接続からデータセットを選択する。
+自然言語検索と自動化されたインサイトを利用するには、[ビジネスビュー](https://help.tellius.com/article/hy9yvh5tom-create-business-view)を作成し、Snowflake 接続からデータセットを選択します。
 
 ### ステップ4:Telliusを使ってデータの価値を最大限に引き出す
 
-テリウスでは、プラットフォームの機能を順を追って説明するガイド付きインターフェイスがある。その他の質問やウォークスルーについては、[ナレッジベースを](https://help.tellius.com/)参照されたい。
\ No newline at end of file
+Tellius には、プラットフォームの機能のウォークスルーを実行するガイド付きインターフェイスがあります。その他の質問とウォークスルーについては、Tellius の[ナレッジベース](https://help.tellius.com/)を参照してください。
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/thoughtspot.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/thoughtspot.md
index 0ccff116fe7..57c32e11cd1 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/thoughtspot.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/thoughtspot.md
@@ -1,36 +1,36 @@
 ---
-nav_title: 思想スポット
-article_title: 思想スポット
-description: "この参考記事では、BrazeとThoughtSpotのパートナーシップについて概説している。ThoughtSpotは次世代分析プラットフォームで、ユーザーはBrazeのインタラクションデータを無制限に検索し、実用的な洞察を見出すことができる。"
+nav_title: ThoughtSpot
+article_title: ThoughtSpot
+description: "このリファレンス記事では、Braze と ThoughtSpot のパートナーシップについて説明します。ThoughtSpot は次世代の分析プラットフォームであり、ユーザーが Braze のインタラクションデータ全体を無制限に検索し、実用的なインサイトを見つけることができます。"
 alias: /partners/thoughtspot/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# 思想スポット
+# ThoughtSpot
 
-> ThoughtSpotはモダン・アナリティクス・クラウドであり、モダン・データスタックにライブ・アナリティクスを提供する次世代アナリティクス・プラットフォームである。
+> ThoughtSpot は、最新のデータスタックにライブ分析を提供し、同僚、パートナー、顧客がデータを実用的なインサイトに変えられるようにする次世代の分析プラットフォームです。
 
-BrazeとThoughtSpotの統合は、ThoughtSpot TML Blocksを活用し、Brazeユーザーがワークシートやモデルの構築済みテンプレートを使ってユーザー行動分析を加速できるようにする。この統合により、ユーザーはBrazeのインタラクションデータを無制限に検索し、実用的な洞察を発見することができる。 
+BrazeとThoughtSpotの統合は、ThoughtSpot TML Blocksを活用し、Brazeユーザーがワークシートやモデルの構築済みテンプレートを使ってユーザー行動分析を加速できるようにする。この統合により、ユーザーは Braze のインタラクションデータを無制限に検索し、実用的なインサイトを見つけることができます。 
 
 ## 前提条件
 
-BrazeでThoughtSpotを使い始めるには、ThoughtSpotがライブクエリを行う前に、データをクラウドデータウェアハウスに送る必要がある。
+Braze で ThoughtSpot の使用を開始するには、ThoughtSpot がデータに対してライブクエリを実行できるようにするために、そのデータをクラウドデータウェアハウスに送信する必要があります。
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| ThoughtSpotアカウント | このパートナーシップを利用するにはThoughtSpotのアカウントが必要である。 |
-| クラウド・データウェアハウス| Brazeのデータは、Braze Currentsを使用してクラウドデータウェアハウスに保存される。 |
+| ThoughtSpotアカウント | このパートナーシップを利用するには ThoughtSpot アカウントが必要です。 |
+| クラウドデータウェアハウス| Braze のデータは、Braze Currents を使用してクラウドデータウェアハウスに保存されます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## TMLブロック
 
-Brazeのユーザーは、すべてのデジタル交流データに簡単にアクセスし、検索することができる。当社のテンプレートにより、ユーザーはあらかじめ組み込まれたビジュアライゼーションやワークシートを使って、分析を素早くセットアップすることができる。検索、ドリルダウン、spotIQでウェブサイトの獲得とユーザー行動を分析する。
+Braze のユーザーは、すべてのデジタルインタラクションデータに簡単にアクセスし、データを検索することができます。当社のテンプレートにより、ユーザーはあらかじめ組み込まれたビジュアライゼーションやワークシートを使って、分析を素早くセットアップすることができる。検索、ドリルダウン、spotIQでウェブサイトの獲得とユーザー行動を分析する。
 
 ## 統合
 
-### ステップ1:ThoughtSpotに接続する 
+### ステップ1:ThoughtSpot に接続する 
 
 ThoughtSpotインスタンスにログインし、Braze Currentsを使ってBrazeから持ってきた各テーブルへのEmbrace接続を作成する。
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/wunderkind.md b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/wunderkind.md
index 6abf4422e24..274f4687152 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/analytics/wunderkind.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/analytics/wunderkind.md
@@ -1,32 +1,32 @@
 ---
-nav_title: ワンダーウィンド
-article_title: ワンダーウィンド
-description: "この参考記事では、BrazeとWunderkindのパートナーシップについて概説している。これにより、パフォーマンスの上昇を分析し、より多くの匿名ユーザーを特定し、Braze経由で送信される1:1メッセージとBrazeに直接追加される連絡先を大幅に拡大することができる。"
+nav_title: Wunderkind
+article_title: Wunderkind
+description: "このリファレンス記事では、Braze と Wunderkind のパートナーシップについて説明します。これにより、パフォーマンスの向上を分析し、より多くの匿名ユーザーを特定することができ、Brazeを介して送信される1対1のメッセージと、Brazeに直接追加される連絡先を大幅に拡大します。"
 alias: /partners/wunderkind/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# ワンダーウィンド
+# Wunderkind
 
-> [Wunderkindは](https://www.wunderkind.co)、高パフォーマンスの1対1メール送信によってeコマースの収益を拡大するプラットフォームである。WunderkindのIdentificationテクノロジーを使えば、ブランドはデバイスを問わず、より多くの匿名ユーザーを、実用的なメールアドレスまで認識することができる。平均して、Wunderkindは識別の割合をウェブサイトトラフィックの3～5%から～40～60%に拡大している。
+> [Wunderkind](https://www.wunderkind.co) は、パフォーマンスの高い1対1メールの送信により、e コマースの収益を拡大するプラットフォームです。Wunderkind の識別技術により、ブランドは、実用的なメールアドレスに至るまで、デバイス間でより多くの匿名ユーザーを認識することができます。平均して、Wunderkindは識別の割合をウェブサイトトラフィックの3～5%から～40～60%に拡大している。
 
-BrazeとWunderkindの統合により、パフォーマンスの上昇を分析し、より多くの匿名ユーザーを特定し、Braze経由で送信された1対1のメッセージやBrazeに直接追加された連絡先を大幅に拡大することができる。
+Braze と Wunderkind の統合により、パフォーマンスの向上を分析し、より多くの匿名ユーザーを特定することができ、Brazeを介して送信される1対1のメッセージと、Brazeに直接追加される連絡先を大幅に拡大します。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| ワンダーウィンド口座 | このパートナーシップを利用するには、Wunderkindのアカウントが必要だ。 |
+| Wunderkind アカウント | このパートナーシップを活用するには、Wunderkind アカウントが必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-WunderKindチームに連絡し、統合のセットアップを手伝ってもらう。WunderkindがAPIを通じて電子メールのデプロイメントと購読ステータスを送信できるように、Braze ESPまたはAPIの認証情報の提供を求められる。 
+WunderKindチームに連絡し、統合のセットアップを手伝ってもらう。Wunderkind が API を介して メールのデプロイとサブスクリプションステータスを送信できるようにするために、Braze ESP または API の認証情報を指定するよう求められます。 
 
-一度接続すれば、ワンダーカインドはそうする：
-- 予備テストを実施し、安定した接続を確認し、Wunderkind側からESPにメールが配信できることを確認する。 
+接続が完了すると、Wunderkind により次の操作が行われます。
+- 安定した接続であることと、メールが Wunderkind 側から メールサービスプロバイダー (ESP) にデプロイできることを確認するために、予備テストを実行します。 
 - レンダリングされたメールを送信できるように、Braze UI内でシリーズの各パートごとに個別のキャンペーンを作成する。
 - 適切なAPIエンドポイントを使用して、レンダリングされたEメールコンテンツをBrazeを通じてリアルタイムに送信するための統合を開発する。
-- テスト環境において、電子メールが正しく通過し、データが想定通りにBrazeに流れることを確認するために、広範な品質保証を実施する。
\ No newline at end of file
+- テスト環境で広範な品質保証を実施して、メールが正しく通過し、データが予期したとおりに Braze に流れることを確認します。
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/business_intelligence.md b/_lang/ja/_partners/data_and_infrastructure_agility/business_intelligence.md
index c11199abd42..b57e7f7990a 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/business_intelligence.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/business_intelligence.md
@@ -5,7 +5,7 @@ page_order: 3
 
 page_type: landing
 search_tag: Partner
-description: "このランディングページには、ビジネスインテリジェンス製品との統合を可能にするBrazeパートナー（合金）が掲載されている。"
+description: "このランディングページには、ビジネスインテリジェンス製品を統合できる Braze パートナー (Alloys) が一覧表示されています。"
 
 layout: partner_page
 partner_api: "https://www.braze.com/api/v1/partners"
@@ -14,7 +14,7 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Business Intelligence"
 
 valid_partner_list:
-- name: シス
+- name: Sisu
   url: /docs/partners/data_and_infrastructure_agility/business_intelligence/sisu_data/
   
 ---
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/business_intelligence/sisu_data.md b/_lang/ja/_partners/data_and_infrastructure_agility/business_intelligence/sisu_data.md
index adb543773b2..b3e7ed76169 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/business_intelligence/sisu_data.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/business_intelligence/sisu_data.md
@@ -1,70 +1,70 @@
 ---
-nav_title: シス・データ
-article_title: シス・データ
+nav_title: Sisu Data
+article_title: Sisu Data
 description: "この参考記事では、Brazeとクラウド・デシジョン・インテリジェンスのリーダーであるSisu Data社との提携について概説している。この提携により、すべてのキャンペーン、またはキャンペーン・レベルで、なぜメトリクスが変化しているのか、何が最も最適な結果をもたらすのかを理解することができる。"
 alias: /partners/sisudata
 page_type: partner
 search_tag: Partner
 ---
 
-# シス・データ
+# Sisu Data
 
-> [Sisu Dataは][2]、機械学習を使用して測定基準のパフォーマンスを自動的に分解し、迅速かつ包括的で実用的な洞察を提供するクラウド・デシジョン・インテリジェンスのリーダーである。
+> [Sisu Data][2] はクラウド意思決定インテリジェンス分野の大手企業であり、機械学習を使用して指標パフォーマンスを自動的に分解し、迅速で包括的で実用的なインサイトを提供します。
 
-Sisu DataとBrazeの統合により、すべてのキャンペーン、またはキャンペーンレベルで、指標（例えば、開封率、クリック率、コンバージョン率など）が変化している理由と、何が最も最適な結果をもたらすのかを理解することができる。これらのセグメントを特定した後、Brazeユーザーは、データウェアハウスでアウトプットを具体化したり、SisuからBrazeに直接送信して、ユーザーのリターゲティングやリエンゲージメントを行うことができる。
+Sisu DataとBrazeの統合により、すべてのキャンペーン、またはキャンペーンレベルで、指標（例えば、開封率、クリック率、コンバージョン率など）が変化している理由と、何が最も最適な結果をもたらすのかを理解することができる。これらのセグメントが識別されると、Braze ユーザーはデータウェアハウスで出力を具体化したり、Sisu から Braze に直接送信し、ユーザーのリターゲティングおよび再エンゲージメントを実行したりできます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| シス・アカウント | このパートナーシップを利用するには、[シスの][3]アカウントが必要である。 |
-| クラウド倉庫 | この統合は、Brazeのデータがクラウドウェアハウス（例えば、SnowflakeやBigQuery）に保存されていることを前提としている。この統合プロセスを効率化するには、[Currentsを][4]経由してBrazeのネイティブ機能を利用することをお勧めする。 |
+| Sisu アカウント | このパートナーシップを活用するには、[Sisu][3] アカウントが必要です。 |
+| クラウド倉庫 | この統合は、Brazeのデータがクラウドウェアハウス（例えば、SnowflakeやBigQuery）に保存されていることを前提としている。この統合プロセスを効率化するには、[Currents][4] を介して Braze のネイティブ機能を使用することをお勧めします。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:データセットを準備する
 
-データセットは、シスに分析させたいKPIを示す必要がある。例えば、コンバージョン率が週をまたいで低下した理由をよりよく理解したいのであれば、リーチレコードは週ごとのコンバージョンを表すべきである。データセットの列は、コンバージョン率が下がる可能性のある理由でなければならない。
+データセットは、Sisu で分析する KPI を示している必要があります。例えば、コンバージョン率が週をまたいで低下した理由をよりよく理解したいのであれば、リーチレコードは週ごとのコンバージョンを表すべきである。データセットの列は、コンバージョン率が下がる可能性のある理由でなければならない。
 
 ### ステップ2:メトリックを作成する  
 
-データセットが準備できたら、集約されたカラムを参照するメトリックを作成する必要がある。1つのデータセットが複数のメトリクスを提供することができるため、ユーザーは、デフォルトですべての分析に含まれるべき、または含まれるべきではないディメンションのセットをキュレートすることもできる。なお、ユーザーはいつでも分析レベルでキュレーションを続けることができる。
+データセットが準備できたら、集約されたカラムを参照するメトリックを作成する必要がある。1つのデータセットが複数のメトリクスを提供することができるため、ユーザーは、デフォルトですべての分析に含まれるべき、または含まれるべきではないディメンションのセットをキュレートすることもできる。ユーザーは常に分析レベルでキュレーションを続けることができることに注意してください。
 
 ![][6]
 
 ### ステップ3:分析を行う  
 
-ユーザーがSisuで作成できる分析は、ユースケースによって異なる。最も一般的な分析のひとつは、どのセグメントが最も変化したかを理解するための期間分析である。ユーザーは、相対的な期間を選択することによって、日次、週次、月次、またはカスタム期間のいずれを分析するかを決定することができる。
+ユーザーがSisuで作成できる分析は、ユースケースによって異なる。最も一般的な分析の1つは、最も大きく変化したセグメントを理解するための前期比分析です。ユーザーは、相対的な期間を選択することによって、日次、週次、月次、またはカスタム期間のいずれを分析するかを決定することができる。
 
-例えば、ユーザーは特定の広告グループとエンゲージメントチャネルの前月比コンバージョン率分析を作成し、上位のポジティブおよびネガティブなドライバーを理解することができる。
+たとえば、ユーザーは特定の広告グループとエンゲージメントチャネルの前月比コンバージョン率分析を作成し、上位のプラス要因とマイナス要因を理解できます。
 
 {% tabs %}
-{% tab トップ・ポジティブ・ドライバー %}
+{% tab 上位のプラス要因 %}
 
 ![]({% image_buster /assets/img/sisudata/kda_result_positive.png %})
 
 {% endtab %}
-{% tab マイナスドライバーのトップ %}
+{% tab 上位のマイナス要因 %}
 
 ![]({% image_buster /assets/img/sisudata/kda_result_negative.png %})
 
 {% endtab %}
 {% endtabs %}
 
-ここから、参加させたいコホートを絞り込んだり、キャンペーンを変更したりすることができる。例えば、シスは、火曜日に送信されるプッシュ通知や大量に送信されるメールがコンバージョン率に深刻な影響を与えることを自動的に特定した。
+ここから、使用するコホートを絞り込んだり、キャンペーンを変更したりできます。たとえば Sisu では、毎週火曜日に送信されるプッシュ通知と、大量に送信されるメールが、コンバージョン率に深刻な影響を与えることが自動的に特定されます。
 
 ![][9]
 
 ### ステップ4:結果をデータウェアハウスに書き戻す
 
-ユーザーは、\[SisuのAPI][10] ]を使用してSisuから結果を抽出し、データウェアハウスでセグメントを具体化することができる。Snowflakeの顧客は、[Cloud Data Ingestionを介して][5]Brazeでこれらのセグメントを有効化できる。
+ユーザーは \[Sisu の API][10] を使用して Sisu から結果を抽出し、データウェアハウス内のセグメントを具体化できます。Snowflake をご利用のお客様は、[クラウドデータ取り込み][5]を使用して Brazeでこれらのセグメントをアクティブにすることができます。
 
-その他のデータウェアハウスについては、既存のアクティベーション・ソリューションを活用するか、シスに問い合わせることができる。
+その他のデータウェアハウスの場合は、既存のアクティベーションソリューションを利用するか、Sisu に連絡して支援を要請できます。
 
 ## サポート
 
-この統合に関するご質問は、partners@sisudata.com までご連絡いただきたい。
+この統合についてのご質問は、Sisu (partners@sisudata.com) にお問い合わせください。
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
 [2]: https://sisudata.com/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage.md b/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage.md
index baf5727391e..8bebdc5efec 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage.md
@@ -18,7 +18,7 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/cloud_storage/amazon_s3/
 - name: Google Cloud Storage
   url: /docs/partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents/
-- name: マイクロソフト Azure
+- name: Microsoft Azure
   url: /docs/partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents/
   
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/amazon_s3.md b/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/amazon_s3.md
index 9f686cf31f0..0968d880c87 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/amazon_s3.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/amazon_s3.md
@@ -12,14 +12,14 @@ search_tag: Partner
 
 > [Amazon S3](https://aws.amazon.com/s3/)は、Amazon Web Servicesが提供する高度にスケーラブルなストレージシステムです。
 
-Braze と Amazon S3 の統合では、[Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) を使用して S3 インスタンスにBrazeデータを送信し、他のプラットフォームs、ツール、および場所に接続するまでデータを保存できます。ダッシュボードデータエクスポートを使用して統合することもできます。AWS S3インテグレーションを始めるには、このページの指示に従ってください。
+Braze と Amazon S3 の統合では、[Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) を使用して S3 インスタンスにBrazeデータを送信し、他のプラットフォームs、ツール、および場所に接続するまでデータを保存できます。ダッシュボードデータエクスポートを使用して統合することもできます。このページの手順に従って AWS S3統合を開始します。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| Amazon S3 アカウント | Amazon S3 アカウントは、このパートナーシップの前進タグe を考慮する必要があります。 |
-| 専用 S3 バケット | Amazon S3 と統合するには、アプリ用の S3 バケットを作成する必要があります。<br><br>すでに S3 バケットがある場合は、権限を制限できるように、Braze専用の新しいバケットを作成することをお勧めします。新しいバケットを作成する方法については、次の手順を参照してください。 |
+| Amazon S3 アカウント | このパートナーシップを活用するには、Amazon S3アカウントが必要です。 |
+| 専用 S3 バケット | Amazon S3 と統合するには、アプリ用の S3 バケットを作成する必要があります。<br><br>すでに S3バケットがある場合は、Braze 専用の新しいバケットを作成することをお勧めします。これにより、権限を制限できるようになります。新しいバケットを作成する方法については、次の手順を参照してください。 |
 | Currents | データを Amazon S3 にエクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -29,33 +29,33 @@ Braze と Amazon S3 の統合では、[Currents]({{site.baseurl}}/user_guide/dat
 
 ## 統合
 
-Braze には、[Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) と、すべてのダッシュボードデータエクスポート(CSV エクスポート、エンゲージメント レポートなど) に対して、Amazon S3-one で2 つの異なるインテグレーションストラテジがあります。どちらの統合も、2 つの認証/許可方法をサポートしています。
+Braze には、[Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) と、すべてのダッシュボードデータエクスポート(CSV エクスポート、エンゲージメント レポートなど) に対して、Amazon S3-one で2 つの異なるインテグレーションストラテジがあります。どちらの統合も、2つの認証/許可方法をサポートしています。
 
-- [AWSシークレットアクセスキー方式](#aws-secret-key-auth-method)
+- [AWS シークレットアクセスキー方式](#aws-secret-key-auth-method)
 - [AWSロールARNメソッド](#aws-role-arn-auth-method)
 
 ## AWSシークレットキー認証方式
 
 この認証メソッドは、シークレットキーとアクセスキー ID を生成し、Brazeがバケットにデータを書き込むためにAWSアカウントのユーザーとして認証できるようにします。
 
-### ステップ1:ユーザーの作成 {#secret-key-1}
+### ステップ1:ユーザーを作成する {#secret-key-1}
 
-アクセスキーID とシークレットアクセスキーを取得するには、[ IAM ユーザーと管理者グループをAWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started_create-admin-group.html) に作成する必要があります。
+アクセスキー ID とシークレットアクセスキーを取得するには、[AWS で IAM ユーザーと管理者グループを作成](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started_create-admin-group.html)する必要があります。
 
 ### ステップ2:認証情報を取得する {#secret-key-2}
 
-新しいユーザーを作成した後、**ユーザーセキュリティクレデンシャルを表示**をクリックして、アクセスキーIDとシークレットアクセスキーを表示します。次に、これらの認証情報をどこかにメモするか、**Down 読み込む 認証情報 s**ボタンをクリックします。後でBraze ダッシュボードに入力する必要があります。
+新しいユーザーを作成した後、**ユーザーセキュリティクレデンシャルを表示**をクリックして、アクセスキーIDとシークレットアクセスキーを表示します。これらの認証情報は後で Braze ダッシュボードに入力する必要があるため、どこかにメモしておくか、\[**Download Credentials**] ボタンをクリックします。
 
 ![][11]
 
-### ステップ3:ポリシーの作成 {#secret-key-3}
+### ステップ3:ポリシーを作成する {#secret-key-3}
 
 **Policies > Get Started > Create Policy** に移動して、ユーザーの権限を追加します。次に、**Create Your Own Policy**を選択します。これにより、制限された権限が付与されるため、Brazeは指定されたバケットにのみアクセスできます。 
 
 ![][12]
 
 {% alert note %}
-"Currents"および"Dashboard Data Export"には、さまざまなポリシーが必要です。
+「Currents」と「ダッシュボードデータのエクスポート」では必要なポリシーが異なります。
 {% endalert %}
 
 任意のポリシー名を指定し、**Policy Document**に以下のコードスニペットを入力します。`INSERTBUCKETNAME` は必ずバケット名に置き換えてください。これらの権限がないと、インテグレーションは認証情報チェックに失敗し、作成されません。
@@ -101,13 +101,13 @@ Braze には、[Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/b
 {% endtab %}
 {% endtabs %}
 
-### ステップ4:ポリシーのアタッチ {#secret-key-4}
+### ステップ4:ポリシーをアタッチする {#secret-key-4}
 
-新しいポリシーを作成したら、**ユーザー s** に移動し、指定したユーザーを選択します。**Permissions**タブで、**Attach Policy**をクリックし、作成した新しいポリシーを選択します。これで、AWS 認証情報 s をBraze アカウントに関連付ける準備ができました。
+新しいポリシーを作成したら、**ユーザー s** に移動し、指定したユーザーを選択します。**Permissions**タブで、**Attach Policy**をクリックし、作成した新しいポリシーを選択します。これで、AWS 認証情報を Braze アカウントにリンクする準備が整いました。
 
 ![][13]
 
-### ステップ 5: BrazeをAWSに関連付ける {#secret-key-5}
+### ステップ 5: Brazeを AWS にリンクする {#secret-key-5}
 
 {% tabs %}
 {% tab Braze Currents %}
@@ -115,7 +115,7 @@ Braze には、[Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/b
 Braze で、**Partner Integrations** > **データエクスポート** に移動します。
 
 {% alert note %}
-[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、**Currents**の下に**統合**があります。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**Currents**] は \[**統合**] にあります。
 {% endalert %}
 
 次に、**Create Current**をクリックし、**Amazon S3 Data Export**を選択します。
@@ -130,12 +130,12 @@ AWSのアクセスキーID とシークレットアクセスキーを最新の
 
 必要に応じて、次のカスタマイズを追加することもできます。
 
-- **フォルダパス:**デフォルトは`currents` です。このフォルダーが存在しない場合、Braze によって自動的に作成されます。 
+- **フォルダーのパス:**デフォルトは `currents` です。このフォルダーが存在しない場合、Braze によって自動的に作成されます。 
 - **サーバ側の保管時のAES-256 暗号化:**デフォルトはオフで、`x-amz-server-side-encryption` ヘッダーが含まれます。
 
 **Launch Current**をクリックして続行します。
 
-認証情報が正常に検証されたかどうかを知らせる通知が表示されます。AWS S3がBraze Currents用に設定されます。
+認証情報が正常に検証されたかどうかを示す通知が表示されます。これで、AWS S3が Braze Currents 用に設定されているはずです。
 
 {% endtab %}
 {% tab ダッシュボードデータのエクスポート %}
@@ -146,15 +146,15 @@ Brazeで、**Partner Integrations** > **Technology Partners** に移動し、**A
 [古いナビゲーション]({{site.baseurl}}/navigation) を使用している場合、**Technology Partners** は**Integrations** にあります。
 {% endalert %}
 
-AWS 認証情報ページで、** AWS シークレットアクセスキー** ラジオボタンが選択されていることを確認し、AWS アクセスID、AWS シークレットアクセスキー、およびAWS S3 バケット名を指定されたフィールドs に入力します。シークレットキーを入力するときは、まず**テスト認証情報s**をクリックして認証情報が機能することを確認し、成功したら**保存**をクリックします。
+AWS 認証情報ページで \[**AWS シークレットアクセスキー**] ラジオボタンが選択されていることを確認してから、AWS アクセス ID、AWS シークレットアクセスキー、AWS S3 バケット名をそれぞれ所定のフィールドに入力します。シークレットキーを入力するときは、まず**テスト認証情報s**をクリックして認証情報が機能することを確認し、成功したら**保存**をクリックします。
 
 ![]({{site.baseurl}}/assets/img/s3_tech_partners.png)
 
 {% alert tip %}
-新しい認証情報 s を取得するには、ユーザーに移動し、**Security 認証情報 s** タブの**Create Access Key** をAWS コンソール内でクリックします。
+新しい認証情報はいつでも取得できます。取得するには、ユーザーに移動して、AWS Console 内の \[**Security Credentials**] タブの \[**Create Access Key**] をクリックします。
 {% endalert %}
 
-認証情報が正常に検証されたかどうかを知らせる通知が表示されます。これで、AWS S3がBrazeの口座に統合されます。
+認証情報が正常に検証されたかどうかを示す通知が表示されます。これで、AWS S3が Braze アカウントに統合されているはずです。
 
 {% endtab %}
 {% endtabs %}
@@ -163,14 +163,14 @@ AWS 認証情報ページで、** AWS シークレットアクセスキー** ラ
 
 この認証メソッドは、BrazeのAmazonアカウントがバケットにデータを書き込むために作成したロールのメンバーとして認証できるようにするロールAmazonリソースネーム(ARN)を生成します。
 
-### ステップ1:ポリシーの作成 {#role-arn-1}
+### ステップ1:ポリシーを作成する {#role-arn-1}
 
 まず、アカウント管理者として AWS 管理コンソールにサインインします。AWS コンソールの IAM セクションに移動し、ナビゲーションバーで **Policies** をクリックし、**ポリシーの作成** をクリックします。
 
 ![]({{site.baseurl}}/assets/img/create_policy_1_list.png)
 
 {% alert note %}
-"Currents"および"Dashboard Data Export"には、さまざまなポリシーが必要です。
+「Currents」と「ダッシュボードデータのエクスポート」では必要なポリシーが異なります。
 {% endalert %}
 
 \[**JSON**] タブを開き、\[**ポリシードキュメント**] セクションに以下のコードスニペットを入力します。`INSERTBUCKETNAME` は必ずバケット名に置き換えてください。終了したら、**Review Policy**をクリックします。
@@ -226,25 +226,25 @@ AWS 認証情報ページで、** AWS シークレットアクセスキー** ラ
 
 ![]({{site.baseurl}}/assets/img/create_policy_4_created.png)
 
-### ステップ2:ロールの作成 {#role-arn-2}
+### ステップ2:ロールを作成する {#role-arn-2}
 
 コンソールの同じIAM セクションで、**Roles > Create Role** をクリックします。
 
 ![]({{site.baseurl}}/assets/img/create_role_1_list.png)
 
-Braze アカウントからBraze アカウントID と外部ID を取得します。
-- **Currents**:Braze で、**Partner Integrations** > **Data Export** に移動します。次に、**Create Current**をクリックし、**Amazon S3 Data Export**を選択します。ここには、ロールの作成に必要な識別子s があります。
+Braze アカウントから Braze アカウント ID と external ID を取得します。
+- **Currents**:Braze で、**Partner Integrations** > **データエクスポート** に移動します。次に、**Create Current**をクリックし、**Amazon S3 Data Export**を選択します。ここには、ロールの作成に必要な識別子s があります。
 - **ダッシュボードデータエクスポート**:Brazeで、**Partner Integrations** > **Technology Partners** に移動し、**Amazon S3** をクリックします。ここには、ロールの作成に必要な識別子s があります。
 
 {% alert note %}
-[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、これらのページは別の場所にあります。<br>- **Currents** は**積分**> **Currents** にあります。<br>- **Technology Partners**は**Integrations**の下にあります。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、これらのページは別の場所にあります。<br>- **Currents** は**積分**> **Currents** にあります。<br>\- \[**テクノロジーパートナー**] は \[**統合**] の下にあります。
 {% endalert %}
 
-AWSコンソールに戻り、信頼できるエンティティセレクタタイプとして**Another AWS Account** を選択します。BrazeのアカウントID を入力し、**外部ID を要求** をオンにして、Brazeの外部ID を入力します。完了したら、**Next**をクリックします。
+AWS Console に戻り、信頼できるエンティティセレクターのタイプとして \[**Another AWS Account**] を選択します。BrazeのアカウントID を入力し、**外部ID を要求** をオンにして、Brazeの外部ID を入力します。完了したら、**Next**をクリックします。
 
 ![S3 の \[ロールの作成] ページ。このページには、ロール名、ロールの説明、信頼できるエンティティ、ポリシー、および権限境界のフィールドがあります。]({{site.baseurl}}/assets/img/create_role_2_another.png)
 
-### ステップ3:ポリシーのアタッチ {#role-arn-3}
+### ステップ3:ポリシーをアタッチする {#role-arn-3}
 
 次に、以前に作成したポリシーをロールにアタッチします。検索バーでポリシーを検索し、ポリシーの横にチェックマークを付けて添付します。完了したら、**Next**をクリックします。
 
@@ -252,11 +252,11 @@ AWSコンソールに戻り、信頼できるエンティティセレクタタ
 
 ロールに名前と説明を付け、\[**ロールの作成**] をクリックします。
 
-![ロールの ARN]({{site.baseurl}}/assets/img/create_role_4_name.png)
+![ロールの ARN]({{site.baseurl}}/assets/img/create_role_3_attach.png)
 
 これで、新しく作成したロールがリストに表示されます。
 
-### ステップ4:Braze AWSとの連携 {#role-arn-4}
+### ステップ4:Braze AWS にリンクする {#role-arn-4}
 
 AWS コンソールで、新しく作成したロールを一覧で見つけます。名前を選択すると、そのロールの詳細が開封されます。
 
@@ -271,23 +271,23 @@ Braze アカウントに戻り、提供されたフィールドにロールARN 
 {% tabs %}
 {% tab Braze Currents %}
 
-Braze で、**Integrations** の**Currents** ページに移動します。次に、**Create Current**をクリックし、**Amazon S3 Data Export**を選択します。
+Braze で、\[**統合**] の \[**Currents**] ページに移動します。次に、**Create Current**をクリックし、**Amazon S3 Data Export**を選択します。
 
 ![]({{site.baseurl}}/assets/img/currents-role-arn.png)
 
-現在の名前を入力します。次に、**Credentials** セクションで、**AWS Role ARN** ラジオボタンが選択されていることを確認し、指定されたフィールドs にロールARN とAWS S3 バケットの名前を入力します。
+Current の名前を指定します。次に、\[**認証情報**] セクションで \[**AWS ロール ARN**] ラジオボタンが選択されていることを確認し、ロール ARN と AWS S3バケット名を所定のフィールドに入力します。
 
 必要に応じて、次のカスタマイズを追加することもできます。
 
-- フォルダパス(デフォルト s to `currents`)
-- サーバ側の保管時のAES-256 暗号化(デフォルト s to OFF) - `x-amz-server-side-encryption` ヘッダーを含みます
+- フォルダーのパス (デフォルトは`currents`)
+- サーバーサイド、保管時 AES-256 暗号化 (デフォルトはオフ) -`x-amz-server-side-encryption`ヘッダーを組み込みます。
 
 **Launch Current**をクリックして続行します。
 
-認証情報が正常に検証されたかどうかを知らせる通知が表示されます。AWS S3がBraze Currents用に設定されます。
+認証情報が正常に検証されたかどうかを示す通知が表示されます。これで、AWS S3が Braze Currents 用に設定されているはずです。
 
 {% alert important %}
-"S3 認証情報が不正な" エラーを受け取った場合、これはAWS でロールを作成した後に統合が早すぎるためである可能性があります。しばらくしてからもう一度やり直してください。
+「S3の認証情報が無効です」というエラーが発生した場合、これは AWS でロールを作成した後に行われた統合が早すぎたことが原因である可能性があります。しばらくしてからもう一度やり直してください。
 {% endalert %}
 
 {% endtab %}
@@ -297,27 +297,27 @@ Braze で、**Technology Partners** ページの**Integrations** に移動し、
 
 ![]({{site.baseurl}}/assets/img/data-export-role-arn.png)
 
-** AWS Credentials** ページで、** AWS Role ARN** ラジオボタンが選択されていることを確認し、指定されたフィールドs にロールARN とAWS S3 バケットの名前を入力します。最初に**テスト認証情報s**をクリックして、認証情報が正しく動作することを確認し、成功したら**保存**をクリックします。
+\[**認証情報**] ページで \[**AWS ロール ARN**] ラジオボタンが選択されていることを確認し、ロール ARN と AWS S3バケット名を所定のフィールドに入力します。最初に**テスト認証情報s**をクリックして、認証情報が正しく動作することを確認し、成功したら**保存**をクリックします。
 
 {% alert tip %}
-新しい認証情報 s を取得するには、ユーザーに移動し、**Security 認証情報 s** タブの**Create Access Key** をAWS コンソール内でクリックします。
+新しい認証情報はいつでも取得できます。取得するには、ユーザーに移動して、AWS Console内の \[**Security Credentials**] タブの \[**Create Access Key**] をクリックします。
 {% endalert %}
 
-認証情報が正常に検証されたかどうかを知らせる通知が表示されます。これで、AWS S3がBrazeの口座に統合されます。
+認証情報が正常に検証されたかどうかを示す通知が表示されます。これで、AWS S3が Braze アカウントに統合されているはずです。
 
 {% endtab %}
 {% endtabs %}
 
-## 書き出しビヘイビア
+## エクスポートの動作
 
-クラウドデータストレージソリューションを統合し、API、ダッシュボード レポートs、またはCSV レポートs をエクスポートしようとしているユーザは、次の処理を実行します。
+クラウドデータストレージソリューションを統合しており、API、ダッシュボードレポート、または CSV レポートをエクスポートする場合、次のような状況が発生します。
 
 - すべてのAPI エクスポートでは、レスポンスボディにダウン読み込むURL が返されず、データストレージを介して取得する必要があります。
-- すべてのダッシュボード レポート s およびCSV レポートs は、ダウン読み込むのためにユーザー s メールに送信され(ストレージ権限は必要ありません)、データストレージにバックアップされます。 
+- すべてのダッシュボードレポートと CSV レポートは、ダウンロード用のメールでユーザーに送信され (保存権限は不要です)、Data Storage にバックアップされます。 
 
-## 複数のコネクタ
+## 複数のコネクター
 
-S3 バケットに送信する複数の Currents コネクターを作成する場合は、同じ認証情報 s を使用できますが、それぞれに別のフォルダーパスを指定する必要があります。これらは、同じワークスペース内で作成することも、複数のワークスペース内で分割して作成することもできます。また、統合ごとに1 つのポリシーを作成するか、両方の統合をカバーする1 つのポリシーを作成することもできます。 
+S3 バケットに送信する Currents コネクターを複数作成する場合は、同じ認証情報を使用できますが、それぞれに異なるパスを指定する必要があります。これらは、同じワークスペース内で作成することも、複数のワークスペース内で分割して作成することもできます。また、統合ごとに1つのポリシーを作成するか、両方の統合に対応する1つのポリシーを作成することもできます。 
 
 Currentsとデータエクスポートの両方に同じ S3 バケットを使用する場合は、統合ごとに異なる権限が必要なため、2 つの個別のポリシーを作成する必要があります。
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents.md b/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents.md
index 6797030cae5..38b9b12d598 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents.md
@@ -2,7 +2,7 @@
 nav_title: Google Cloud Storage
 article_title: Google Cloud Storage
 alias: /partners/google_cloud_storage_for_currents/
-description: "この参考記事では、Brazeと、非構造化データ用の大規模スケーラブルなオブジェクトストレージであるGoogle Cloud Storageとの提携について概説している。"
+description: "このリファレンス記事では、Braze と Google Cloud Storage のパートナーシップについて説明します。Google Cloud Storage は、非構造化データのための大規模拡張可能オブジェクトストレージです。"
 page_type: partner
 tool: Currents
 search_tag: Partner
@@ -11,45 +11,45 @@ search_tag: Partner
 
 # Google Cloud Storage
 
-> [Google Cloud Storageは](https://cloud.google.com/storage/)、Googleがクラウドコンピューティング製品群の一部として提供する、非構造化データ用の大規模スケーラブルなオブジェクトストレージである。
+> [Google Cloud Storage](https://cloud.google.com/storage/) は、Google が Cloud Computing 製品群の一部として提供する、非構造化データのための大規模拡張可能オブジェクトストレージソリューションです。
 
-BrazeとGoogle Cloud Storageの統合により、CurrentsのデータをGoogle Cloud Storageにストリーミングできる。後でETLプロセス（Extract、Transform、Load）を使って、Google BigQueryのような他の場所にデータを転送することができる。
+Braze と Google Cloud Storage の統合により、Currents データを Google Cloud Storage にストリーミングできます。その後、ETL プロセス (抽出、変換、読み込み) を使用して、データを Google BigQuery などの他の場所に転送できます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| グーグル・クラウド・ストレージのアカウント | このパートナーシップを利用するには、グーグル・クラウド・ストレージのアカウントが必要だ。 |
-| Currents | データをGoogle Cloud Storageにエクスポートするには、アカウントに[Braze Currentsを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents)設定する必要がある。 |
+| Google Cloud Storage アカウント | このパートナーシップを活用するには、Google Cloud Storage アカウントが必要です。 |
+| Currents | Google Cloud Storage にデータを再度エクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-Google Cloud Storageと統合するには、Brazeが書き込み先のストレージバケット(`storage.buckets.get`)に関する情報を取得し、そのバケット(`storage.objects.create`)内にオブジェクトを作成できるように、適切な認証情報を設定する必要がある。 
+Google Cloud Storage と統合するには、Braze が書き込み先のストレージバケット (`storage.buckets.get`) に関する情報を取得し、そのバケット (`storage.objects.create`) 内にオブジェクトを作成できるように、適切な認証情報を設定する必要があります。 
 
-これは、Currents統合で使用する秘密鍵を生成するロールとサービスアカウントを作成する手順を説明する、以下の手順を使用して行うことができる。
+これを行うには次の手順に従います。この手順では、Currents 統合で使用する秘密キーを生成するロールとサービスアカウントを作成する手順を説明します。
 
 ### ステップ1:役割を作成する
 
-Google Cloud Platform Consoleで、**IAM & admin**>**Roles**>**\+ Create Roleと**進み、新しいロールを作成する。
+\[**IAM & admin**] > \[**Roles**] > \[**\+ Create Role**] に移動して、Google Cloud Platform Console に新しいロールを作成します。
 
 ![][2]
 
-次に、ロールに名前を付け、**"+Add Permissions**"を選択し、以下を追加する：`storage.buckets.get` `storage.objects.create` と`storage.objects.get` を追加する。次に、**Createを**選択する。
+次に、ロールに名前を付け、\[**+Add Permissions**] を選択し、`storage.buckets.get`、`storage.objects.create`、`storage.objects.get` を追加します。次に \[**Create**] を選択します。
 
-オプションで、`storage.objects.delete` パーミッションを追加して、Brazeが不完全なファイルをクリーンアップできるようにする。まれに、Google Cloudが接続を早期に終了し、Brazeが不完全なファイルをGoogle Cloud Storageに書き込むことがある。通常の場合、Brazeは再試行し、正しいデータで新しいファイルを作成し、古いファイルはGoogle Cloud Storageに残す。
+必要に応じて `storage.objects.delete` 権限を追加して、Braze が不完全なファイルをクリーンアップできるようにします。まれに Google Cloud が接続を早期に終了し、Braze が Google Cloud Storage に不完全なファイルを書き込むことがあります。通常の状況では、Braze は再試行し、正しいデータを含む新しいファイルを作成しますが、古いファイルは Google Cloud Storage に残ります。
 
 ![][3]
 
 ### ステップ2:サービスアカウントを作成する
 
-Google Cloud Platform Consoleで**IAM & admin**>**Service Accountsに**移動し、**Create Service Accountを**選択して新しいサービスアカウントを作成する。
+\[**IAM & admin**] > \[**Service Accounts**] に移動し、\[**Create Service Account**] を選択して、Google Cloud Platform Console で新しいサービスアカウントを作成します。
 
 ![][4]
 
 次に、サービスアカウントに名前を付け、新しく作成したカスタムロールへのアクセス権を付与する。
 
-![Google Cloud Platformのcreate servicesページで、"Select a Role "フィールドにロールの名前を入力する。][5]
+![Google Cloud Platform のサービス作成ページで、「Select a Role」フィールドにロールの名前を入力する。][5]
 
 #### キーを作成する
 
@@ -57,29 +57,29 @@ Google Cloud Platform Consoleで**IAM & admin**>**Service Accountsに**移動し
 
 ![][6]
 
-### ステップ3:ブレイズで電流を設定する
+### ステップ3:Braze で Currents を設定する
 
-Brazeで、**Currents**>**\+ Create Current**>**Google Cloud Storage Data Exportに**移動し、統合名と連絡先のEメールを入力する。
+Braze で \[**Currents**] > \[**\+ Current を作成**] > \[**Google Cloud Storage データのエクスポート**] に移動し、統合名と連絡先メールを入力します。
 
-次に、**GCS JSON Credentialsに**JSON秘密鍵をアップロードし、CGSバケット名とGCSプレフィックス（オプション）を入力する。 
+次に \[**GCS JSON 認証情報**] で JSON 秘密キーをアップロードし、GCS バケット名と GCS 接頭辞 (オプション) を指定します。 
 
 {% alert important %}
-コネクタの認証情報が期限切れになると、コネクタはイベントの送信を停止する。この状態が**48時間**以上続くと、コネクタのイベントは削除され、データは永久に失われる。
+認証情報ファイルを最新の状態に維持することが重要です。コネクターの認証情報の有効期限が切れると、コネクターはイベントの送信を停止します。この状態が**48時間**以上続くと、コネクタのイベントは削除され、データは永久に失われる。
 {% endalert %}
 
-![BrazeのGoogle Cloud Storage Currentsページ。このページには、インテグレーション名、コンタクトEメール、GCS JSONクレデンシャル、GCSバケット名、プレフィックスのフィールドがある。][7]
+![Braze の「Google Cloud Storage Currents」ページ。このページには、統合名、連絡先メール、GCS JSON 認証情報、GCS バケット名、接頭辞のフィールドがある。][7]
 
-最後に、ページの一番下までスクロールし、エクスポートしたいメッセージ・エンゲージメント・イベントまたは顧客行動イベントを選択する。完了したら、カレントを起動する。
+最後に、ページの一番下までスクロールし、エクスポートしたいメッセージ・エンゲージメント・イベントまたは顧客行動イベントを選択する。完了したら、Current を起動します。
 
-### ステップ4:グーグル・クラウド・ストレージ（GCS）のエクスポートを設定する
+### ステップ4:Google Cloud Storage (GCS) エクスポートを設定する
 
-Google Cloud Storage（GCS）エクスポートを設定するには、**Technology Partners**>**Google Cloud Storageに**進み、GCS認証情報を入力し、**Make this default data export destinationを**選択する。
+Google Cloud Storage (GCS) エクスポートを設定するには、\[**Technology Partners**] > \[**Google Cloud Storage**] に移動し、GCS 認証情報を入力し、\[**Make this the default data export destination**] を選択します。
 
 {% alert tip %}
-**GCS JSON クレデンシャルは**、[Google Cloud ドキュメントの](https://cloud.google.com/iam/docs/keys-create-delete)手順に従って生成される。必ず、生成されたJSON値全体を入力すること。
+**GCS JSON 認証情報**は、[Google Cloud ドキュメント](https://cloud.google.com/iam/docs/keys-create-delete) の手順に従って生成されます。必ず、生成されたJSON値全体を入力すること。
 {% endalert %}
 
-![BrazeダッシュボードのGoogle Cloud Storageページ。][8]{: style="max-width:70%;"}
+![Braze ダッシュボードの「Google Cloud Storage」ページ。][8]{: style="max-width:70%;"}
 
 対応するGoogle Cloud IAMサービスアカウントには、以下の権限が必要である（これは、Brazeの**Google Cloud Storage**ページで**Test Credentials**ボタンを選択することで確認できる）：
 - `storage.objects.create`
@@ -87,14 +87,14 @@ Google Cloud Storage（GCS）エクスポートを設定するには、**Technol
 - `storage.objects.get`
 - `storage.objects.list`
 
-エクスポートされたファイルの構成と内容は、AWS S3、Microsoft Azure、Google Cloud Storageの統合間で同一である。
+エクスポートされたファイルの構成と内容は、AWS S3、Microsoft Azure、および Google Cloud Storage の各統合で同一です。
 
-## 輸出行動
+## エクスポートの動作
 
-クラウド・データ・ストレージ・ソリューションを統合し、API、ダッシュボード・レポート、またはCSVレポートをエクスポートしようとしているユーザーには、次のような問題が発生する：
+クラウドデータストレージソリューションを統合しており、API、ダッシュボードレポート、または CSV レポートをエクスポートする場合、次のような状況が発生します。
 
-- すべてのAPIエクスポートは、レスポンスボディにダウンロードURLを返さず、データストレージを通じて取得する必要がある。
-- すべてのダッシュボード・レポートとCSVレポートは、ダウンロード用にユーザーのEメールに送信され（ストレージのパーミッションは不要）、データ・ストレージにバックアップされる。 
+- すべての API エクスポートでは、応答本文でダウンロード URL が返されないため、データストレージから取得する必要があります。
+- すべてのダッシュボードレポートと CSV レポートは、ダウンロード用のメールでユーザーに送信され (保存権限は不要です)、Data Storage にバックアップされます。 
 
 [2]: {% image_buster /assets/img/gcs1.png %}
 [3]: {% image_buster /assets/img/gcs2.png %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents.md b/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents.md
index d7a274b54ff..014b7d73912 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents.md
@@ -2,7 +2,7 @@
 nav_title: Microsoft Azure Blob Storage
 article_title: Microsoft Azure Blob Storage
 alias: /partners/microsoft_azure_blob_storage_for_currents/
-description: "この参考記事では、Braze Currentsと、非構造化データ用の大規模スケーラブルなオブジェクトストレージであるMicrosoft Azure Blog Storageとのパートナーシップについて概説している。"
+description: "このリファレンス記事では、Braze Currents と Microsoft Azure Blog Storage のパートナーシップについて説明します。Microsoft Azure Blog Storage は、非構造化データのための大規模拡張可能オブジェクトストレージです。"
 page_type: partner
 tool: Currents
 search_tag: Partner
@@ -11,35 +11,35 @@ search_tag: Partner
 
 # Microsoft Azure Blob Storage
 
-> [Microsoft Azure Blob Storageは](https://azure.microsoft.com/en-us/services/storage/blobs/)、マイクロソフトがAzure製品群の一部として提供する、非構造化データ用の大規模スケーラブルなオブジェクトストレージである。
+> [Microsoft Azure Blob Storage](https://azure.microsoft.com/en-us/services/storage/blobs/) は、Microsoft が Azure 製品群の一部として提供する、非構造化データのための大規模拡張可能オブジェクトストレージです。
 
-BrazeとMicrosoft Azure Blob Storageの統合により、データをAzureにエクスポートし、Currentsデータをストリーミングすることができる。その後、ETLプロセス（Extract、Transform、Load）を使ってデータを他の場所に転送することができる。
+Braze と Microsoft Azure Blob Storage の統合により、データを Azure にエクスポートし、Currents データをストリーミングすることができます。その後、ETL プロセス (抽出、変換、読み込み) を使用してデータを他の場所に転送できます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| Microsoft AzureとAzureストレージアカウント | このパートナーシップを利用するには、Microsoft AzureとAzureストレージのアカウントが必要だ。 |
-| Currents | Currentsにデータをエクスポートするには、アカウントに[Braze Currentsを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents)設定する必要がある。 |
+| Microsoft AzureとAzureストレージアカウント | このパートナーシップを利用するには、Microsoft Azure と Azure ストレージアカウントが必要です。 |
+| Currents | Currents にデータをエクスポートするには、アカウントに対して [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定しておく必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-Microsoft Azure Blob Storageと統合するには、BrazeがデータをAzureにエクスポートバックするか、Currentsデータをストリーミングできるように、ストレージアカウントと接続文字列が必要である。
+Microsoft Azure Blob Storage と統合するには、Braze がデータを Azure にエクスポートするか、Currents データをストリーミングするためのストレージアカウントと接続文字列を用意しておく必要があります。
 
 ### ステップ1:ストレージアカウントを作成する
 
-Microsoft Azureで、サイドバーの**Storage Accountsに**移動し、**\+ Addを**クリックして新しいストレージアカウントを作成する。次に、ストレージアカウント名を指定する。その他のデフォルト設定は更新する必要はない。最後に、**レビュー＋作成を**選択する。 
+Microsoft Azure で、サイドバーの \[**Storage Accounts**] に移動し、\[**\+ Add**] をクリックして新しいストレージアカウントを作成します。次に、ストレージアカウント名を指定する。その他のデフォルト設定は更新する必要はない。最後に \[**Review + create**] を選択します。 
 
-すでにストレージアカウントをお持ちの場合でも、Brazeのデータ専用に新規作成することをお勧めする。
+すでにストレージアカウントをお持ちの場合でも、Braze データ専用にストレージアカウントを新規作成することをお勧めします。
 
 ![]({% image_buster /assets/img/azure-currents-step-1.png %})
 
 ### ステップ2:接続文字列を取得する
 
-ストレージアカウントがデプロイされたら、ストレージアカウントから**Access Keys**メニューに移動し、接続文字列をメモする。
+ストレージアカウントが準備できたら、ストレージアカウントから \[**Access Keys**] メニューに移動し、接続文字列を書きとめておきます。
 
-マイクロソフトは2つのアクセスキーを提供し、一方のキーを使って接続を維持しながら、もう一方のキーを再生成する。必要なのはどちらか一方の接続文字列だけだ。
+Microsoft は2つのアクセスキーを提供しています。1つのキーを再生成する際に、もう1つのキーを使用して接続を維持します。必要なのはどちらか一方の接続文字列だけだ。
 
 {% alert note %}
 Brazeはキーではなく、このメニューの接続文字列を使用する。
@@ -47,7 +47,7 @@ Brazeはキーではなく、このメニューの接続文字列を使用する
 
 ![]({% image_buster /assets/img/azure-currents-step-2.png %})
 
-### ステップ 3:ブロブ・サービス・コンテナを作成する
+### ステップ 3:Blob サービスコンテナーを作成する
 
 ストレージアカウントの**Blob Service**セクションにある**Blobs**メニューに移動する。先ほど作成したストレージアカウント内にBlobサービスコンテナを作成する。 
 
@@ -55,40 +55,40 @@ Blobサービスコンテナの名前を指定する。その他のデフォル
 
 ![]({% image_buster /assets/img/azure-currents-step-3.png %})
 
-### ステップ 4:電流を設定する
+### ステップ 4:Currents を設定する
 
-Brazeで、**Currents > + Create Current > Azure Blob Data Exportに**移動し、統合名と連絡先のEメールを入力する。
+Brazeで **\[Currents] > \[+ Current を作成] > \[Azure Blob データエクスポート]** に移動し、統合名と連絡先のメールを入力します。
 
-次に、接続文字列、コンテナ名、BlobStorage接頭辞（オプション）を指定する。
+次に、接続文字列、コンテナー名、BlobStorage 接頭辞 (オプション) を指定します。
 
-![BrazeのMicrosoft Azure Blob storage Currentsページ。このページには、統合名、連絡先Eメール、接続文字列、コンテナ名、接頭辞のフィールドがある。]({% image_buster /assets/img/maz.png %})
+![Braze の Microsoft Azure Blob ストレージ Currents のページ。このページには、統合名、連絡先メール、接続文字列、コンテナー名、接頭辞のフィールドがある。]({% image_buster /assets/img/maz.png %})
 
-最後に、ページの一番下までスクロールし、エクスポートしたいメッセージ・エンゲージメント・イベントまたは顧客行動イベントを選択する。完了したら、カレントを起動する。
+最後に、ページの一番下までスクロールし、エクスポートしたいメッセージ・エンゲージメント・イベントまたは顧客行動イベントを選択する。完了したら、Current を起動します。
 
 ### ステップ 5: Azureデータエクスポートを設定する
 
-以下は、クレデンシャルを設定するものである：
+次の目的で使用する認証情報を設定する手順を以下で説明します。
 1. APIを通じてセグメントをエクスポートする
 2. CSVエクスポート（キャンペーン、セグメント、キャンバスのユーザーデータをダッシュボード経由でエクスポートする）
 3. エンゲージメントレポート
 
-Brazeで、**Partner Integrations**>**Technology Partners**>**Microsoft Azureに**移動し、接続文字列、Azureストレージコンテナ名、Azureストレージ接頭辞を入力する。
+Braze で \[**パートナー連携**] >\[**テクノロジーパートナー**] > \[**Microsoft Azure**] に移動し、接続文字列、Azure ストレージコンテナー名、Azure ストレージ接頭辞を入力します。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-次に、**Make this the default data export destination（これをデフォルトのデータ・エクスポート先にする**）ボックスがチェックされていることを確認する。完了したら、統合を保存する。
+次に、\[**これをデフォルトのデータエクスポート先にする**] ボックスがオンになっていることを確認します。これにより、エクスポートしたデータが確実に Azure に送信されます。完了したら、統合を保存する。
 
-![BrazeのMicrosoft Azureデータエクスポートページ。このページには、接続文字列、コンテナ名、プレフィックスのフィールドがある。]({% image_buster /assets/img/azure_data_export.png %})
+![BrazeのMicrosoft Azureデータエクスポートページ。このページには、接続文字列、コンテナー名、接頭辞のフィールドがある。]({% image_buster /assets/img/azure_data_export.png %})
 
 {% alert important %}
-コネクターの認証情報が期限切れになると、コネクターはイベントの送信を停止する。この状態が**48時間**以上続くと、コネクタのイベントは削除され、データは永久に失われる。
+接続文字列を最新の状態に維持することが重要です。コネクターの認証情報の有効期限が切れると、コネクターはイベントの送信を停止します。この状態が**48時間**以上続くと、コネクタのイベントは削除され、データは永久に失われる。
 {% endalert %}
 
-## 輸出行動
+## エクスポートの動作
 
-クラウド・データ・ストレージ・ソリューションを統合し、API、ダッシュボード・レポート、またはCSVレポートをエクスポートしようとしているユーザーには、次のような問題が発生する：
+クラウドデータストレージソリューションを統合しており、API、ダッシュボードレポート、または CSV レポートをエクスポートする場合、次のような状況が発生します。
 
-- すべてのAPIエクスポートは、レスポンスボディにダウンロードURLを返さず、データストレージを通じて取得する必要がある。
+- すべての API エクスポートでは、応答本文でダウンロード URL が返されないため、データストレージから取得する必要があります。
 - すべてのダッシュボード・レポートとCSVレポートは、ダウンロード用にユーザーのEメールに送信され（ストレージのパーミッションは不要）、データストレージにバックアップされる。 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import.md
index be90b4ca2ab..b9e646e9396 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import.md
@@ -1,12 +1,12 @@
 ---
-nav_title: コホート・インポート
-article_title: コーホート・インポート・パートナー
+nav_title: コホートインポート
+article_title: コホートインポートのパートナー
 layout: partner_page
 page_order: 2
 
 page_type: landing
 search_tag: Partner
-description: "このランディング・ページには、ブレイズに共同輸入を提供するブレイズ・パートナー（合金）が掲載されている。"
+description: "このランディングページには、Blaze へのコホートインポート機能を提供する Braze パートナー (Alloys) が一覧表示されています。"
 
 partner_api: "https://www.braze.com/api/v1/partners"
 partner_path: "https://www.braze.com/product/alloys/partners/"
@@ -14,7 +14,7 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Cohort Import"
 
 valid_partner_list:
-- name: クビット
+- name: Kubit
   url: /docs/partners/data_and_infrastructure_agility/analytics/kubit/
 - name: Mixpanel
   url: /docs/partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents/
@@ -22,7 +22,7 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/analytics/amplitude_for_currents/
 - name: AppsFlyer
   url: /docs/partners/message_orchestration/attribution/appsflyer/  
-- name: テニクル
+- name: Tinyclues
   url: /docs/partners/data_and_infrastructure_agility/cohort_import/tinyclues/
 - name: Hightouch
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/hightouch/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/amplitude.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/amplitude.md
index d785df428f6..ff2b2cb16e4 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/amplitude.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/amplitude.md
@@ -1,18 +1,18 @@
 ---
 nav_title: Amplitude
-article_title: Amplitudeコホートインポート
-description: "このリファレンス記事では、Amplitude、プロダクト分析、およびビジネスインテリジェンス プラットフォームのコホートインポート機能について概説します。"
+article_title: Amplitude コホートインポート
+description: "このリファレンス記事では、Amplitude のコホートインポート機能について説明します。Amplitude は、プロダクト分析およびビジネスインテリジェンスのプラットフォームです。"
 page_type: partner
 search_tag: Partner
 ---
 
-# Amplitude コホート輸入
+# Amplitude コホートインポート
 
 > ここでは、[Amplitude](https://amplitude.com/)からBrazeへのユーザー コホートの読み込み方法について説明します。Amplitudeと他の機能の統合の詳細については、主な[Amplitudeの記事]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_audiences/)を参照してください。
 
 ## データインポート統合
 
-設定したすべてのインテグレーションは、取引先のデータポイント量にカウントされます。
+設定するすべての統合は、アカウントのデータポイントボリュームの対象となります。
 
 ### ステップ1:Braze データインポートキーを取得する
 
@@ -26,27 +26,27 @@ Brazeで、**Partner Integrations** > **Technology Partners** に移動し、**A
 
 ### ステップ2:Amplitude でのBrazeインテグレーションの設定
 
-Amplitudeで、**Sources & Destinations**> **\[project name]**> **Destinations**> **Braze** に移動します。アプリが表示されるプロンプトで、BrazeデータインポートキーとREST エンドポイントを入力し、**Save** をクリックします。
+Amplitude で \[**Sources & Destinations**] > \[**project name]**] > \[**Destinations**] > \[**Braze**] に移動します。表示されるプロンプトで Braze データインポートキーと REST エンドポイントを指定し、\[**Save**] をクリックします。
 
 ![]({% image_buster /assets/img/amplitude.png %})
 
 ### ステップ 3:Amplitude コホートをBrazeにエクスポートする
 
-まず、ユーザーs をAmplitude からBraze にエクスポートするには、エクスポートするユーザーの[コホート](https://help.amplitude.com/hc/en-us/articles/231881448-Behavioral-Cohorts) を作成します。Amplitudeは、次の識別子sを使用してコホートsをBrazeに同期できます。
+まず、Amplitude から Braze にユーザーをエクスポートするため、エクスポートするユーザーの[コホート](https://help.amplitude.com/hc/en-us/articles/231881448-Behavioral-Cohorts)を作成します。Amplitude は、以下の識別子を使用してコホートを Braze に同期できます。
 - ユーザー別名
-- デバイスID
+- デバイス ID
 - ユーザーID(外部ID)
 
 コホートを作成したら、**Sync to...**を押して、これらのユーザーsをBrazeにエクスポートします。
 
 #### 同期ケイデンスの定義
 
-コホート同期は、1 回の同期、毎日または毎時のスケジュールされた、または毎分s を更新するリアルタイムに設定できます。[データポイント s]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points/) を消費することに留意しながら、ビジネスニーズに合った選択肢を選択してください。
+コホート同期は、1回限りの同期、毎日または毎時間のスケジュールされた同期、1分ごとに更新されるリアルタイム同期として設定できます。[データポイント]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points/)の消費も考慮して、ビジネスニーズに適したオプションを選択してください。
 
-### ステップ4:Brazeの事業ユーザー
+### ステップ4:Braze でユーザーをセグメント化する
 
-Braze で、これらのSegmentのユーザーを作成するには、**Segment s** に移動して**Engagement** に移動し、Segmentに名前を付け、フィルターとして** Amplitude Cohorts** を選択します。次に、"includes"オプションを使用し、Amplitude で作成したコホートを選択します。 
+Braze でこれらのユーザーのセグメントを作成するには、\[**エンゲージメント**] の下の \[**セグメント**] に移動し、セグメントに名前を付け、フィルターとして \[**Amplitude コホート**] を選択します。次に、"includes"オプションを使用し、Amplitude で作成したコホートを選択します。 
 
-![Braze Segment ビルダーでは、フィルター"Amplitude_コホート s" は" includes_value" および" Amplitude コホート test".]({% image_buster /assets/img/amplitude2.png %}) に設定されています。
+![Braze セグメントビルダーでフィルター「amplitude_cohorts」が「includes_value」と「Amplitude cohort test」に設定されている。]({% image_buster /assets/img/amplitude2.png %})
 
-保存後、このSegmentは、ターゲットユーザーのs ステップでキャンバスまたはキャンペーンの作成時に参照できます。
\ No newline at end of file
+保存したら、ユーザーのターゲット設定のステップでキャンバスまたはキャンペーンを作成するときに、このセグメントを参照できます。
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/appsflyer_audiences.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/appsflyer_audiences.md
index 32e9fa695bb..7197dcf55ca 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/appsflyer_audiences.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/appsflyer_audiences.md
@@ -1,23 +1,23 @@
 ---
-nav_title: AppsFlyerの利用者
-article_title: AppsFlyerの利用者
+nav_title: AppsFlyer Audiences
+article_title: AppsFlyer Audiences
 alias: /partners/appsflyer_audiences/
-description: "このリファレンス記事では、Braze とAppsFlyer オーディエンス s 間のパートナーシップについて説明します。これは、AppsFlyer プラットフォームの機能で、オーディエンス Segment s を効率的に構築し、パートナーネットワークに接続することができます。"
+description: "このリファレンス記事では、Braze と AppsFlyer Audiences のパートナーシップについて説明します。AppsFlyer Audiences は、オーディエンスセグメントを効率的に作成してパートナーネットワークに接続できる AppsFlyer プラットフォームの機能です。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# AppsFlyerの利用者
+# AppsFlyer Audiences
 
-> ここでは、[AppsFlyer Audiences][2]統合を使用して、AppsFlyerからBrazeにユーザー コホートを読み込む方法について説明します。AppsFlyerとその他の機能(携帯アトリビューションなど)の統合の詳細については、メインの[AppsFlyerの記事][3]を参照してください。
+> この記事では、[AppsFlyer Audiences][2] 統合を使用して AppsFlyer から Braze にユーザーコホートをインポートする方法について説明します。AppsFlyerとその他の機能(携帯アトリビューションなど)の統合の詳細については、メインの[AppsFlyerの記事][3]を参照してください。
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| AppsFlyerアカウント | AppsFlyerアカウントは、この提携の事前タグeを考慮する必要があります。 |
-| iOSやAndroid アプリ | この統合は、iOS とAndroid アプリ s をサポートします。お使いのプラットフォームによっては、アプリのライセンスにコードの抜粋が必要な場合があります。これらの要件の詳細は、インテグレーションプロセスの第1ステップに記載されています。 |
+| AppsFlyerアカウント | このパートナーシップを活用するには、AppsFlyer アカウントが必要です。 |
+| iOSやAndroid アプリ | この統合では、iOS アプリと Android アプリがサポートされています。ご使用のプラットフォームによっては、アプリケーションでコードスニペットが必要な場合があります。これらの要件の詳細については、統合プロセスのステップ1を参照してください。 |
 | AppsFlyer SDK | 必要なBraze SDKに加えて、[AppsFlyer SDK](https://support.appsflyer.com/hc/en-us/articles/207032126-SDK-integration-overview)をインストールする必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -25,7 +25,7 @@ search_tag: Partner
 
 ### ステップ1:AppsFlyer SDKの設定
 
-この統合を使用するには、AppsFlyer SDKの`setPartnerData()` 関数を使用して、ユーザーのBraze外部ID をAppsFlyer に渡す必要があります。
+この統合を使用するには、AppsFlyer SDK の`setPartnerData()` 関数を使用して、ユーザーの Braze external ID をAppsFlyer に渡す必要があります。
 
 #### Android 
 ```java
@@ -50,22 +50,22 @@ Brazeで、**Partner Integrations** > **Technology Partners** に移動し、**A
 [古いナビゲーション]({{site.baseurl}}/navigation) を使用している場合、**Technology Partners** は**Integrations** にあります。
 {% endalert %}
 
-ここでは、REST エンドポイントが見つかり、Brazeデータインポートキーが生成されます。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。データインポートキーとREST エンドポイントは、AppsFlyerのダッシュボードでポストバックアップを設定するときに次回のステップで使用されます。<br><br>![AppsFlyerテクノロジページの"Data Import Using Cohort Import"ボックスデータインポートキーとREST エンドポイントが表示されます。][5]{: style="max-width:90%;"}
+ここでは、REST エンドポイントが見つかり、Brazeデータインポートキーが生成されます。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。データインポートキーとREST エンドポイントは、AppsFlyerのダッシュボードでポストバックアップを設定するときに次回のステップで使用されます。<br><br>![AppsFlyer テクノロジーページの「コホートインポートを使用したデータインポート」ボックス。このボックスには、データインポートキーと REST エンドポイントが表示されている。][5]{: style="max-width:90%;"}
 
 ### ステップ3:AppsFlyer オーディエンスでのBraze コネクションの設定
 
 1. [AppsFlyer Audiences][4]で、**Connections**タブに移動し、**Add partner connection**をクリックします。
 2. パートナーとしてBraze を選択し、コネクションに名前を付けます。
 3. データインポートキーとBraze REST エンドポイントを入力します。
-4. 接続を保存すると、新規または既存のオーディエンスにリンクできるようになります。
+4. 接続を保存します。保存した接続は、新しいオーディエンスまたは既存のオーディエンスにリンクできます。
 
-![AppsFlyer オーディエンスは、プラットフォームパートナ接続設定ページを表示します。"画像sの下部には、Brazeの外部IDがチェックされていることが表示されます。][6]{: style="max-width:80%;"}
+![AppsFlyer Audiences プラットフォームのパートナー接続設定ページ。画像下部で「Braze external ID」ボックスがオンになっている。][6]{: style="max-width:80%;"}
 
 ### ステップ 4:Braze でのAppsFlyer オーディエンスコホートの使用
 
 AppsFlyer オーディエンスがアップロードされてBrazeされると、**AppsFlyer Cohorts**フィルターを選択して、BrazeでSegmentsを定義するときにフィルターとして使用できます。
 
-![ユーザ属性s フィルター "AppsFlyer Cohorts"選択。][7]
+![ユーザー属性フィルター「AppsFlyer Cohorts」アが選択されている。][7]
 
 [1]: https://www.appsflyer.com/
 [2]: https://www.appsflyer.com/product/audiences/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/census.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/census.md
index 8b7517638c3..e3a7a8042e3 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/census.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/census.md
@@ -1,37 +1,37 @@
 ---
 nav_title: Census
-article_title: Census コホート インポート
+article_title: Census のコホートインポート
 description: "このリファレンス記事は、クラウドウェアハウスのデータを使用してターゲットユーザーセグメントを動的に作成できるデータ統合プラットフォームであるCensusのコホートインポート機能を概説しています。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# Census コホート インポート
+# Census のコホートインポート
 
-> この記事では、ユーザーコホートを[Census][1]からBrazeにインポートする方法について説明します。詳細については、メインの[Censusの記事]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/census/)を参照してください。
+> この記事では、ユーザーコホートを[Census][1]からBrazeにインポートする方法について説明します。詳細については、[Census のメイン記事]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/census/)を参照してください。
 
 ## コホートインポート統合
 
 ### ステップ1:Brazeサービス接続を作成する
 
-CensusプラットフォームでCensusを統合するには、**Connections**タブに移動し、**New Destination**を選択して新しいBrazeサービス接続を作成します。
+Census プラットフォームで Census を統合するには、\[**Connections**] タブに移動し、\[**New Destination**] を選択して新しい Braze サービス接続を作成します。
 
 表示されるプロンプトで、この接続に名前を付け、BrazeエンドポイントURL、Braze REST APIキー、およびデータインポートキーを提供します。データインポートキーはコホートを同期するために必要であり、**パートナー統合** > **テクノロジーパートナー** > **Census**に移動することでBrazeで見つけることができます。
 
 ![][8]{: style="max-width:60%;"}
 
-### ステップ2:Census同期を作成する
+### ステップ2:Census 同期を作成する
 
 Brazeに顧客を同期するには、同期を構築する必要があります。ここでは、データを同期する場所と、2つのプラットフォーム間でフィールドをどのようにマッピングするかを定義します。
 
 1. **同期** タブに移動し、**新しい同期** を選択します。<br><br> 
-2. 作曲者で、データウェアハウスからソースデータモデルを選択します。<br><br>
-3. モデルが同期される場所を設定します。**Braze**を送信先として選択し、**ユーザー & コホート**を同期するオブジェクトとして選択します。<br>![「送信先を選択」プロンプトで、「Braze」が接続として選択され、さまざまなオブジェクトが一覧表示されます。][10]{: style="max-width:80%;"}<br><br>
+2. コンポーザーで、データウェアハウスからソースデータモデルを選択します。<br><br>
+3. モデルが同期される場所を設定します。**Braze**を送信先として選択し、**ユーザー & コホート**を同期するオブジェクトとして選択します。<br>![\[Select a Destination] プロンプトで接続として「Braze」が選択されており、さまざまなオプションが一覧表示されている。][10]{: style="max-width:80%;"}<br><br>
 4. **ソース列**を選択して、コホートに追加するユーザーを識別し、**外部ユーザーID**を**識別子タイプ**として選択します。<br><br>
-5. **コホート名** ドロップダウンで、コホートを選択するか、コホートを作成するか、ソース列を選択してコホート名を入力します。<br><br>
+5. \[**Cohort Name**] ドロップダウンでコホートを選択するか、コホートを作成するか、またはソース列を選択してコホート名を取り込みます。<br><br>
 6. **ソースデータからレコードが削除されたとき**のドロップダウンを使用して、ソースデータセットから削除されたときにユーザーに何が起こるかを選択します。例えば、**何もしない**や**コホートから一致するレコードを削除する**などです。<br><br>
-7. 最後に、Censusデータフィールドを同等のBrazeフィールドにマッピングします。<br>![Censusマッピング][11]{: style="max-width:80%;"}<br><br>
+7. 最後に、Census データフィールドを対応する Braze フィールドにマッピングします。<br>![Censusマッピング][11]{: style="max-width:80%;"}<br><br>
 8. 詳細を確認して同期を作成します。 
 
 これで同期を実行できます！
@@ -41,7 +41,7 @@ Brazeに顧客を同期するには、同期を構築する必要があります
 同期後、Brazeセグメントを作成し、Censusコホートフィルターを追加して、将来のBrazeキャンペーンやCanvasでそのユーザーをターゲットにすることができます。 
 
 {% alert note %}
-CensusとBrazeの統合を使用する場合、Censusは各同期でBrazeにデルタ（変更データ）のみを送信します。
+Census と Braze の統合を使用する場合、Census は Braze との同期のたびに差分 (変更データ) のみを送信します。
 {% endalert %}
 
 [1]: https://www.getcensus.com/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/heap.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/heap.md
index 8913397dbc3..f1b186eb23b 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/heap.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/heap.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Heap
 article_title: Heap
-description: "このリファレンス記事では、BrazeとデジタルインサイトプラットフォームであるHeapとの統合について詳述しています。これにより、HeapデータをBrazeにインポートし、ユーザーコホートを作成することができるほか、BrazeデータをHeapにエクスポートしてセグメントを作成することもできます。"
+description: "このリファレンス記事では、Braze と Heap の統合について詳しく説明します。Heap はデジタルインサイトプラットフォームであり、Heap データを Braze にインポートしたり、ユーザーコホートを作成したり、Braze データを Heap にエクスポートしてセグメントを作成したりできます。"
 alias: /partners/heap/
 page_type: partner
 search_tag: Partner
@@ -10,16 +10,16 @@ search_tag: Partner
 
 # Heap
 
-> [Heap](https://heap.io/)、デジタルインサイトプラットフォームは、ビジネスに最も影響を与えるデジタルエクスペリエンスの機会に焦点を当て、摩擦を排除し、顧客を喜ばせ、収益を加速させます。
+> [Heap](https://heap.io/) はデジタルインサイトプラットフォームであり、デジタルエクスペリエンスにおいてビジネスに最も大きく影響する機会に集中して取り組むことができるようにし、フリクションを解消し、顧客を楽しませ、収益創出を加速させます。
 
-BrazeとHeapの統合により、[HeapデータをBrazeにインポート](#data-import-integration)し、ユーザーコホートを作成することや、[BrazeデータをHeapにエクスポート]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/heap/)してセグメントを作成することができます。
+Braze と Heap の統合により、[Heap データをBraze にインポート](#data-import-integration)し、ユーザーコホートを作成し、[Braze データを Heap にエクスポート]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/heap/)してセグメントを作成することができます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| ヒープアカウント | このパートナーシップを利用するには、[Heap](https://heap.io/about)アカウントが必要です。 |
-| Braze データインポートキー | これは、**パートナー統合** > **テクノロジーパートナー** からBrazeダッシュボードにキャプチャして、**Heap** を選択できます。 |
+| Heap アカウント | このパートナーシップを利用するには、[Heap](https://heap.io/about)アカウントが必要です。 |
+| Braze データインポートキー | これは、Braze ダッシュボードの \[**パートナー連携**] > \[**テクノロジーパートナー**] からキャプチャされます。その後 \[**Heap**] を選択します。 |
 | Braze REST エンドポイント | [あなたのRESTエンドポイントURL][1]。あなたのエンドポイントは、インスタンスのBraze URLに依存します。 |
 | Braze Currents | BrazeからHeapにデータをエクスポートするには、アカウントで[Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents)を有効にする必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -27,35 +27,35 @@ BrazeとHeapの統合により、[HeapデータをBrazeにインポート](#data
 ## ユースケース
 - 放棄されたファネルを再度利用するユーザーを再エンゲージする:ユーザーが購入またはサブスクリプションのファネルを放棄したときに、再エンゲージメントメッセージングをトリガーします。
 - 試用体験をパーソナライズする：トライアル体験における摩擦点を特定し、トライアル中にユーザーを再エンゲージするための適切なタイミングでリマインダーを送信し、価値を見出す手助けをします。
-- 発表とオファーに対するエンゲージメントを高める：ターゲットプロモーション、更新、および新しいサービスの発表を関連するオーディエンスに向けて行います。
+- 発表とオファーに対するエンゲージメントを高める：プロモーション、アップデート、および新しいサービス発表のターゲットを、関連性のあるオーディエンスに設定します。
 
 ## データインポート統合
 
-HeapとBrazeの統合を使用して、Heapで定義されたコホートをBrazeに自動的に同期します。
+Heap と Braze の統合を使用して、Heap で定義されたコホートを Braze に自動的に同期します。
 
 ### ステップ1:Brazeデータインポートキーを取得する
 
-Brazeで、**パートナー統合** > **テクノロジーパートナー** に移動し、**Heap** を選択します。 
+Brazeで \[**パートナー連携**] >\[**テクノロジーパートナー**] に移動し、\[**Heap**] を選択します。 
 
 {% alert note %}
-古いナビゲーションを使用している場合は、統合の下にテクノロジーパートナーを見つけることができます。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-このページでは、データインポートキーとRESTエンドポイントを見つけることができます。これらの値の両方に注意し、それらをHeapのアカウントマネージャーに提供して、統合の設定を完了してください。
+このページでは、データインポートキーとRESTエンドポイントを見つけることができます。統合の設定を完了するため、これらの両方の値をメモして Heap アカウントマネージャーに提出します。
 
 ![][3]{: style="max-width:90%;"}
 
 ### ステップ2:Brazeでインポートされたユーザーをセグメント化する
 
-Brazeで、**Segment**に移動し、HeapコホートSegmentに名前を付け、フィルターとして**Heapコホート**を選択します。ここから、含めたいHeapコホートを選択できます。HeapのコホートSegmentが作成された後、キャンペーンやキャンバスを作成する際にオーディエンスフィルターとして選択できます。
+Braze で \[**セグメント**] に移動し、Heap コホートセグメントに名前を付け、フィルターとして \[**セグメントコホート**] を選択します。ここから、どの Heap コホートを含めるかを選択できます。Heap のコホートセグメントを作成したら、キャンペーンまたはキャンバスを作成するときにこのセグメントをオーディエンスフィルターとして選択できます。
 
-![BrazeのSegmentビルダーでは、ユーザー属性フィルター「Heapコホート」が「含む」と「Heapテストコホート」に設定されています。][2]{: style="max-width:90%;"}
+![Braze セグメントビルダーで、ユーザー属性フィルター「Heap cohort」が「次を含む」と「Heap Test Cohort」に設定されている。][2]{: style="max-width:90%;"}
 
 ### この統合を使用する
 
-Heap Segment を使用するには、Braze キャンペーンまたはキャンバスを作成し、ターゲットオーディエンスとしてセグメントを選択します。
+Heap セグメントを使用するには、Braze キャンペーンまたはキャンバスを作成し、ターゲットオーディエンスとしてセグメントを選択します。
 
-![Brazeのキャンペーンビルダーのターゲティングステップで、「セグメントによるターゲットユーザー」フィルターが「Heapコホート」に設定されています。][4]{: style="max-width:90%;"}
+![Braze キャンペーンビルダーのターゲティングステップで、\[セグメントを基準にユーザーをターゲットに設定] フィルターが「Heap cohort」に設定されている。][4]{: style="max-width:90%;"}
 
 ## 統合の詳細
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/hightouch.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/hightouch.md
index fbcd8427ca3..bc3aa51134f 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/hightouch.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/hightouch.md
@@ -1,14 +1,14 @@
 ---
 nav_title: Hightouch
 article_title: Hightouch Cohort Import
-description: "このリファレンス記事では、Hightouch のコホートインポート機能について説明します。これは、ウェアハウスからビジネスツールに顧客データを同期するためのプラットフォームです。"
+description: "このリファレンス記事では、Hightouch のkコホートインポート機能について説明します。Hightouch は、ウェアハウスの顧客データをカスタムツールと同期するプラットフォームです。"
 page_type: partner
 search_tag: Partner
 
 ---
-# Hightouch コホート輸入
+# Hightouch コホートインポート
 
-> ここでは、[Hightouch][1] からユーザー コホートs をBrazeに読み込む方法について説明します。これにより、ウェアハウスにのみ存在するデータに基づいてターゲットキャンペーンs を送信できます。Hightouchと他の機能の統合の詳細については、主な[Hightouchの記事]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch/)を参照してください。
+> この記事では、[Hightouch][1] から Braze にユーザーコホートをインポートする方法について説明します。これにより、ウェアハウス内にのみ存在する可能性のあるデータに基づいてターゲットを絞ったキャンペーンを送信できるようになります。Hightouchと他の機能の統合の詳細については、主な[Hightouchの記事]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch/)を参照してください。
 
 ## データインポート統合
 
@@ -21,17 +21,17 @@ Brazeで、**Partner Integrations** > **Technology Partners** に移動し、**H
 
 ここでは、REST エンドポイントが見つかり、Brazeデータインポートキーが生成されます。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。<br><br>![][6]{: style="max-width:90%;"} 
 
-### ステップ2:Hightouch でのBraze コホートs の宛先としての追加
+### ステップ2:Hightouch で Braze コホートを宛先として追加する
 Hightouch ワークスペースの**Destination**ページに移動し、**Brazeコホート**を検索し、**Continue**をクリックします。そこから、REST エンドポイントとデータインポートキーを取り出し、**Continue**をクリックします。<br><br>![][7]{: style="max-width:90%;"}
 
 ### ステップ3:モデル(またはオーディエンス)をBrazeコホートに同期する
-Hightouch では、作成した[モデル](https://hightouch.io/docs/getting-started/create-your-first-sync/#create-a-model) または[オーディエンス](https://hightouch.io/docs/audiences/usage/) を使用して、新しい同期を作成します。次に、前のステップで作成したBrazeコホート送信先を選択します。最後に、「Brazeコホート」送信先設定で、照合する識別子を選択し、新しいBrazeコホートをHightouchで作成するか、既存のコホートを更新するかを決定します。<br><br>![][8]{: style="max-width:90%;"}
+Hightouch では、作成した[モデル](https://hightouch.io/docs/getting-started/create-your-first-sync/#create-a-model) または[オーディエンス](https://hightouch.io/docs/audiences/usage/) を使用して、新しい同期を作成します。次に、前のステップで作成した Braze コホート宛先を選択します。最後に Braze コホート宛先設定で、照合する識別子を選択し、Hightouch で新しい Braze コホートを作成するか、既存のコホートを更新するかを決定します。<br><br>![][8]{: style="max-width:90%;"}
 
-### ステップ4:Hightouch ユーザ定義オーディエンスからのBraze Segmentの作成
-Braze で、**Segment s** に移動し、新しいSegmentを作成し、フィルターとして** Hightouch Cohorts** を選択します。ここから、含めるHightouch コホートを選択できます。Hightouch コホート Segmentが作成されたら、キャンペーンまたはキャンバスを作成するときにオーディエンス フィルターとして選択できます。<br><br>![][9]{: style="max-width:90%;"}
+### ステップ4:Hightouch カスタムオーディエンスから Braze セグメントを作成する
+Braze で \[**セグメント**] に移動し、新しいセグメントを作成し、フィルターとして \[**Hightouch コホート**] を選択します。ここから、どの Hightouch コホートを含めるかを選択できます。Hightouch のコホートセグメントを作成したら、キャンペーンまたはキャンバスを作成するときにこのセグメントをオーディエンスフィルターとして選択できます。<br><br>![][9]{: style="max-width:90%;"}
 
 ### この統合の使用
-Hightouch Segmentを使用するには、Braze キャンペーンまたはキャンバスを作成し、対象オーディエンスとしてSegmentを選択します。<br><br>![][10]{: style="max-width:90%;"}
+Hightouch セグメントを使用するには、Braze キャンペーンまたはキャンバスを作成し、ターゲットオーディエンスとしてセグメントを選択します。<br><br>![][10]{: style="max-width:90%;"}
 
 [1]: https://hightouch.io
 [6]: {% image_buster /assets/img/hightouch/data_import_key.png %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/kubit.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/kubit.md
index fa060497473..218af7696ed 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/kubit.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/kubit.md
@@ -1,53 +1,53 @@
 ---
-nav_title: クビット
-article_title: クビット・コホート・インポート
+nav_title: Kubit
+article_title: Kubit コホートインポート
 description: "このリファレンス記事では、Kubitのコホートインポート機能について概説している。Kubitはコード不要のセルフサービス分析プラットフォームで、即座に製品インサイトを提供し、KubitユーザーコホートをインポートしてBrazeメッセージングでターゲットにすることができる。"
 page_type: partner
 search_tag: Partner
 ---
 
-# クビット共同輸入
+# Kubit コホートインポート
 
-> この記事では、[Kubitから](https://kubit.ai/)Brazeにユーザーコホートをインポートする方法を説明する。Kubitとその他の機能の統合についての詳細は、[Kubitの]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/kubit/)メイン[記事を]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/kubit/)参照のこと。
+> この記事では、[Kubitから](https://kubit.ai/)Brazeにユーザーコホートをインポートする方法を説明する。Kubit とその他の機能の統合についての詳細は、[Kubitのメイン記事]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/kubit/)を参照してください。
 
 ## データ・インポートの統合
 
 ### ステップ1:Brazeデータインポートキーを取得する
 
-Brazeで、**Partner Integrations**>**Technology Partnersに**移動し、**Kubitを**選択する。ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。 
+Brazeで \[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Kubit**] を選択します。ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。 
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-一度生成された鍵は、新規に作成することも、既存のものを無効にすることもできる。データ・インポート・キーとRESTエンドポイントは、Kubitのダッシュボードでポストバックを設定する際に、次のステップで使用される。
+生成されたら、新しいキーを作成するか、既存のキーを無効にできます。Kubit のダッシュボードでポストバックを設定する場合、次のステップでデータインポートキーと REST エンドポイントが使用されます。
 
-![]({% image_buster /assets/img/kubit/kubit.png %}){: style="max-width:90%;"}
+![Braze の Kubit テクノロジーパートナーページ.]({% image_buster /assets/img/kubit/kubit.png %}){: style="max-width:90%;"}
 
 ### ステップ2:KubitでBrazeを設定する
 
-BrazeデータインポートキーとBraze RESTエンドポイントをKubitサポート窓口に提供する。統合の設定は彼らが行い、統合が開始されたら知らせてくれる。  
+Kubit サポート担当者に、Braze データインポートキーと Braze REST エンドポイントを提供します。統合の設定は彼らが行い、統合が開始されたら知らせてくれる。  
 
-### ステップ3:インポート・コーホートをブレイズへ
+### ステップ3:Braze にコホートをインポートする
 
 #### Kubitでコホートを作成する
-Kubitで[コホートを作成](https://www.kubit.ai/doc/fundamentals#cohort)し、ターゲットユーザーの条件を定義する。<br><br>![]({% image_buster /assets/img/kubit/create_cohort.png %}){: style="max-width:80%;"}
+Kubit で[コホートを作成](https://www.kubit.ai/doc/fundamentals#cohort)し、ターゲットユーザの条件を定義します。<br><br>![]({% image_buster /assets/img/kubit/create_cohort.png %}){: style="max-width:80%;"}
 
 #### ユーザーをBrazeにインポートする
-コホートを保存したら、BrazeにインポートしてBrazeセグメントで使用することができる。これらのセグメントは、ターゲットを絞ったEメールやプッシュキャンペーン、キャンバスの作成に利用できる。
+コホートを保存したら、そのコホートを Braze にインポートして、Braze セグメントで使用できます。これらのセグメントは、ターゲットを絞ったEメールやプッシュキャンペーン、キャンバスの作成に利用できる。
 
-これを行うには、既存のコホートに移動し、**「Cohort Control**」で「**Import to Braze**」を選択する。
+これを行うには、既存のコホートに移動し、\[**Cohort Control**] で \[**Import to Braze**] を選択します。
 
 ![]({% image_buster /assets/img/kubit/import_to_braze.png %}){: style="max-width:80%;"}
 
-次に、希望するインポート・ケイデンスを選択する。ワンタイムインポートでは、一度だけインポートすることができる。スケジュールインポートでは、毎日、毎週、毎月、特定の時間にインポートすることができる。各コホートは、1つのライブ・インポート・スケジュールしか持つことができない。 
+次に、使用するインポートケイデンスを選択します。\[One-Time Import] では、今すぐ1回インポートできます。\[Scheduled Import] では、毎日、毎週、または毎月の特定の時点にインポートできます。各コホートに設定できるライブインポートスケジュールは1つだけであることに注意してください。 
 
 ![]({% image_buster /assets/img/kubit/import_schedule.png %}){: style="max-width:40%;"}
 
-#### 輸入状況を確認する
-インポートが完了すると、インポートスケジュールで指定された受信者にEメール通知が送信される。Kubitの**Scheduleで**コホートのインポート状況を確認することもできる。スケジュール履歴には、すべてのインポート実行時間、結果、Brazeにインポートされたコホート内のユーザー総数が表示される。<br><br>![]({% image_buster /assets/img/kubit/import_history.png %})<br><br>そのインポートスケジュールの**Import to Braze**アイコンをクリックすることで、手動でインポートをトリガーすることができる。
+#### インポートステータスを確認する
+インポートが完了すると、インポートスケジュールで指定された受信者にEメール通知が送信される。また、Kubit の \[**Schedule**] でコホートのインp－トステータスを確認することもできます。スケジュール履歴には、すべてのインポート実行時間、結果、Brazeにインポートされたコホート内のユーザー総数が表示される。<br><br>![]({% image_buster /assets/img/kubit/import_history.png %})<br><br>そのインポートスケジュールの**Import to Braze**アイコンをクリックすることで、手動でインポートをトリガーすることができる。
 
 ### ステップ4:KubitコホートでBrazeセグメントを作成する
-Brazeにコホートをインポートした後、それらをフィルターとして使用してBrazeセグメントを作成し、BrazeキャンペーンやCanvasに含めることができる。[Brazeセグメントの作成方法の]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/#step-4-add-filters-to-your-segment)詳細については、セグメントのドキュメントを参照。
+Braze にコホートをインポートしたら、それらのコホートをフィルターとして使用して、Braze セグメントを作成し、Braze キャンペーンまたはキャンバスに含めることができます。[Braze セグメントの作成方法]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/#step-4-add-filters-to-your-segment)の詳細については、セグメントのドキュメントを参照してください。
 
-![Brazeセグメントビルダーでは、ユーザー属性「Kubit cohorts」が「includes_value」に設定され、利用可能なコホートのリストが表示される。]({% image_buster /assets/img/kubit/segment_with_kubit_cohorts.png %}){: style="max-width:70%;"}
\ No newline at end of file
+![Braze セグメントビルダーで、ユーザー属性「Kubit コホート」が「includes_value」に設定されており、使用可能なコホートのリストが表示されている。]({% image_buster /assets/img/kubit/segment_with_kubit_cohorts.png %}){: style="max-width:70%;"}
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/mixpanel.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/mixpanel.md
index 3d9aca1a87c..835d5f24d2e 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/mixpanel.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/mixpanel.md
@@ -1,49 +1,49 @@
 ---
 nav_title: Mixpanel
-article_title: ミックスパネルのコホート・インポート
-description: "このリファレンス記事では、ビジネス分析プラットフォームであるMixpanelのコホートインポート機能について概説しています。MixpanelのコホートをBrazeにインポートしてBrazeセグメントを作成し、将来のBrazeキャンペーンやCanvasでユーザーをターゲットにするために使用することができます。"
+article_title: Mixpanel コホートインポート
+description: "このリファレンス記事では、Mixpanel のコホートインポート機能について説明します。Mixpanel はビジネス分析プラットフォームであり、Mixpanel コホートを Braze にインポートして Braze セグメントを作成できます。作成したセグメントは、今後の Braze キャンペーンやキャンバスでユーザーをターゲットにするために使用できます。"
 page_type: partner
 search_tag: Partner
 ---
 
-# ミックスパネルのコホート・インポート
+# Mixpanel コホートインポート
 
-> この記事では、[Mixpanelから](https://mixpanel.com/)Brazeにユーザーコホートをインポートする方法について説明する。Mixpanelとその他の機能の統合に関する詳細は、[Mixpanelの]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents/)メイン[記事を]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents/)参照のこと。
+> この記事では、[Mixpanelから](https://mixpanel.com/)Brazeにユーザーコホートをインポートする方法について説明する。Mixpanel とその他の機能の統合についての詳細は、[Mixpanel のメイン記事]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/mixpanel_for_currents/)を参照してください。
 
 ## データ・インポートの統合
 
-あなたが設定した統合は、あなたのアカウントのデータポイント数にカウントされる。
+設定するすべての統合は、アカウントのデータポイントボリュームの対象となります。
 
 {% alert important %}
-Mixpanelのデータ保持ポリシーに従い、2010年1月1日以前に送信されたイベントはインポート時に削除される。
+Mixpanel のデータリテンションポリシーに従い、2010年1月1日より前に送信されたイベントは、インポート中に削除されます。
 {% endalert %}
 
 ### ステップ1:Brazeデータインポートキーを取得する
 
-Brazeで、**Partner Integrations**>**Technology Partnersに**移動し、**Mixpanelを**選択する。ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。 
+Brazeで \[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Mixpanel**] を選択します。ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。 
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-一度生成された鍵は、新規に作成することも、既存のものを無効にすることもできる。データインポートキーとRESTエンドポイントは、Mixpanelのダッシュボードでポストバックを設定する際に次のステップで使用される。<br><br>![]({% image_buster /assets/img_archive/currents-mixpanel-edit.png %})
+生成されたら、新しいキーを作成するか、既存のキーを無効にできます。データインポートキーとRESTエンドポイントは、Mixpanelのダッシュボードでポストバックを設定する際に次のステップで使用される。<br><br>![]({% image_buster /assets/img_archive/currents-mixpanel-edit.png %})
 
 ### ステップ2:MixpanelでBrazeとの統合をセットアップする
 
-Mixpanelで、**Data Management > Integrationsに**移動する**。**次に、Brazeの統合タブを選択し、**Connectを**クリックする。表示されるプロンプトで、BrazeデータインポートキーとRESTエンドポイントを入力し、**Continueを**クリックする。
+Mixpanel で **\[Data Management] > \[Integrations]** に移動します。次に Braze 統合のタブを選択し、\[**Connect**] をクリックします。表示されるプロンプトで Braze データインポートキーと REST エンドポイントを指定し、\[**Continue**] をクリックします。
 
 ![]({% image_buster /assets/img_archive/mixpanel2.png %}){: style="max-width:50%;"}
 
 ### ステップ 3:MixpanelのコホートをBrazeにエクスポートする
 
-Mixpanelで、**Data Management > Cohortsに**移動する。Brazeに送信するコホートを選択し、**Brazeにエクスポートを**選択する。最後に、ワンタイムシンクまたはダイナミックシンクを選択する。ダイナミック同期を選択すると、Brazeコホートが15分ごとに同期され、Mixpanelのユーザーと一致する。 
+Mixpanel で **\[Data Management] > \[Cohorts]** に移動します。Braze に送信するコホートを選択し、\[**Export to Braze**] を選択します。最後に、ワンタイムシンクまたはダイナミックシンクを選択する。動的同期を選択すると、Braze コホートが15分ごとに同期され、Mixpanel のユーザーと照合されます。 
 
 ![]({% image_buster /assets/img_archive/mixpanel3.png %}){: style="max-width:50%;"}
 
 ### ステップ 4:Brazeのセグメントユーザー
 
-Brazeで、これらのユーザーのセグメントを作成するには、**Engagementの**下の**Segmentsに**移動し、セグメントに名前を付け、フィルターとして**Mixpanel_Cohortsを**選択する。次に、「includes」オプションを使い、Mixpanelで作成したコホートを選択する。 
+Braze でこれらのユーザーのセグメントを作成するには、\[**エンゲージメント**] の下の \[**セグメント**] に移動し、セグメントに名前を付け、フィルターとして \[**Mixpanel_Cohorts**] を選択します。次に、「includes」オプションを使い、Mixpanelで作成したコホートを選択する。 
 
-![Brazeセグメントビルダーで、ユーザー属性フィルター「Mixpanel cohorts」が「includes」と「Braze cohort」に設定されている。]({% image_buster /assets/img_archive/mixpanel1.png %})
+![Braze セグメントビルダーで、ユーザー属性フィルター「Mixpanel cohort」が「次を含む」と「Braze cohort」に設定されている。]{% image_buster /assets/img_archive/mixpanel1.png %}
 
 保存後、キャンバスまたはキャンペーン作成時に、ユーザーをターゲティングするステップでこのセグメントを参照できる。
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/tinyclues.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/tinyclues.md
index 3778b36b607..39c33e65340 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/tinyclues.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/tinyclues.md
@@ -1,6 +1,6 @@
 ---
-nav_title: テニクル
-article_title: テニクル
+nav_title: Tinyclues
+article_title: Tinyclues
 alias: /partners/tinyclues/
 description: "この参考記事では、BrazeとTinycluesのパートナーシップについて概説している。Tinycluesは、オーディエンス構築機能を提供し、よりターゲティングされたキャンペーンへの送信、新しい製品機会の発見、驚くほどユーザーフレンドリーなUIを使用した収益の向上を支援する。"
 page_type: partner
@@ -8,9 +8,9 @@ search_tag: Partner
 
 ---
 
-# テニクル
+# Tinyclues
 
-> [Tinycluesは](https://www.tinyclues.com/)、顧客体験を損なうことなくキャンペーン数と収益を増加させる機能と、オンラインとオフラインの両方でCRMキャンペーンのパフォーマンスを追跡する分析機能を提供するオーディエンス構築機能である。
+> [Tinyclues](https://www.tinyclues.com/) はオーディエンス構築機能であり、オンラインとオフラインの両方で CRM キャンペーンのパフォーマンスを追跡するために、カスタマーエクスペリエンスと分析に悪影響を及ぼすことなく、キャンペーン数と収益を増加できます。
 
 BrazeとTinycluesの統合は、より良いCRMプランニングと戦略への道をユーザーに提供し、ユーザーはよりターゲットを絞ったキャンペーンを送信し、新しい製品機会を見つけ、信じられないほどユーザーフレンドリーなUIを使用して収益を向上させることができる。
 
@@ -27,21 +27,21 @@ BrazeとTinycluesを統合するには、Tinycluesプラットフォームを設
 
 ### ステップ1:Brazeデータインポートキーを取得する
 
-Brazeで、**Partner Integrations**>**Technology Partnersに**移動し、**Tinycluesを**選択する。 
+Braze で \[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Tinyclues**] を選択します。 
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。鍵の生成後、新しい鍵を作成したり、既存の鍵を無効にしたりすることができる。<br><br>![][6]{: style="max-width:90%;"} 
+ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。<br><br>![][6]{: style="max-width:90%;"} 
 
 統合を完了するには、データインポートキーとRESTエンドポイントをTinycluesデータオペレーションチームに提供する必要がある。その後、Tinycluesが接続を確立し、セットアップ完了後に連絡を取る。
 
 ### ステップ2:Tinycluesプラットフォームからキャンペーンをエクスポートする
 
-Brazeで使用するTinycluesユーザーのコホートを作成するには、まずTinycluesプラットフォームからエクスポートする必要がある。
+Braze で使用する Tinyclues ユーザーのコホートを作成するには、まず Tinyclues プラットフォームからエクスポートする必要があります。
 
-Tinycluesで、エクスポートしたいキャンペーンを選択し、**キャンペーンのエクスポートを**クリックする。エクスポートすると、オーディエンスは自動的にBrazeアカウントにアップロードされる。
+Tinyclues でエクスポートするキャンペーンを選択し、\[**Export Campaigns**] をクリックします。エクスポートすると、オーディエンスは自動的にBrazeアカウントにアップロードされる。
 
 ![][1]
 
@@ -50,23 +50,23 @@ Tinycluesで、エクスポートしたいキャンペーンを選択し、**キ
 Brazeで「**セグメント**」に移動し、Tinycluesコホートセグメントに名前を付け、フィルターとして**Tinycluesコホートを**選択する。ここから、どのTinycluesコホートを含めるかを選択できる。Tinycluesコホートセグメントを作成した後、キャンペーンやキャンバスを作成する際に、オーディエンスフィルターとして選択することができる。
 
 ![][3]{: style="max-width:90%;"}<br><br>
-![Brazeセグメントビルダーで、ユーザー属性フィルター「Tinyclues cohort」が「includes」と「Primary cohort」に設定されている。][4]{: style="max-width:90%;"}
+![Braze セグメントビルダーで、ユーザー属性フィルター「Tinyclues cohort」が「次を含む」と「Primary cohort」に設定されている。][4]{: style="max-width:90%;"}
 
-コーホートの所在がわからず困っている？[トラブルシューティングの](#troubleshooting)セクションを参照してほしい。 
+コーホートの所在がわからず困っている？「[トラブルシューティング](#troubleshooting)」セクションでガイダンスをご確認ください。 
 
 ## この統合を使う
 
 Tinycluesセグメントを使用するには、Brazeキャンペーンまたはキャンバスを作成し、ターゲットオーディエンスとしてセグメントを選択する。 
 
-![ターゲティングステップのBrazeキャンペーンビルダーで、"Target users by segment "フィルターが "Tinyclues cohort "に設定されている。][5]{: style="max-width:90%;"}
+![Braze キャンペーンビルダーのターゲティングステップで、\[セグメントを基準にユーザーをターゲットに設定] フィルターが「Tinyclues cohort」に設定されている。][5]{: style="max-width:90%;"}
 
 ## トラブルシューティング
 
-リスト内で適切なコホートを見つけるのに苦労している？Tinycluesでキャンペーンの詳細を表示し、**Export File Nameを**チェックして名前を確認する。
+リスト内で適切なコホートを見つけるのに苦労している？Tinyclues でキャンペーンの詳細を表示し、\[**Export File Name**] をオンにして名前を確認します。
 
-![キャンペーン詳細ページの下部には、あなたのコホート名が表示される。][2]{: style="max-width:30%;"}
+![キャンペーン詳細ページの下部にコホート名が表示されている。][2]{: style="max-width:30%;"}
 
-視聴者の検索にまだ問題があるのか？その他のサポートについては、[Tinycluesチームに](mailto:support@tinyclues.com)問い合わせを。
+これでもオーディエンスの取得で問題が解決しない場合は、その他のサポートについては、[Tinycluesチームに](mailto:support@tinyclues.com)問い合わせを。
 
 [1]: {% image_buster /assets/img/tinyclues/tinyclues_1.png %}
 [2]: {% image_buster /assets/img/tinyclues/tinyclues_2.png %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md
index 113237ab29f..61defa38db0 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md
@@ -1,27 +1,27 @@
 ---
 nav_title: トレジャーデータ
-article_title: トレジャーデータ コホート インポート
-description: "このリファレンス記事は、トレジャーデータのコホートインポート機能について説明しています。"
+article_title: トレジャーデータのコホートインポート
+description: "このリファレンス記事では、トレジャーデータのコホートインポート機能について説明します。"
 page_type: partner
 search_tag: Partner
 
 ---
-# トレジャーデータコホートインポート
+# トレジャーデータのコホートインポート
 
 > この記事では、トレジャーデータからBrazeにユーザーコホートをインポートする方法について説明します。これにより、倉庫にしか存在しないデータに基づいてターゲットキャンペーンを送信できるようになります。
 
 {% alert important %}
-この機能は現在ベータ版です。詳細については、トレジャーデータおよびBrazeの担当者にお問い合わせください。
+この機能は現在ベータ版です。詳細については、トレジャーデータおよび Braze の担当者にお問い合わせください。
 {% endalert %}
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| トレジャーデータアカウント | このパートナーシップを利用するには、[トレジャーデータ](https://www.treasuredata.com/)アカウントが必要です。 |
-| Braze データインポートキー | これは、**パートナー統合** > **テクノロジーパートナー** からBrazeダッシュボードでキャプチャでき、その後**Heap**を選択します。 |
+| トレジャーデータのアカウント | このパートナーシップを利用するには、[トレジャーデータ](https://www.treasuredata.com/)のアカウントが必要です。 |
+| Braze データインポートキー | これは、Braze ダッシュボードの \[**パートナー連携**] > \[**テクノロジーパートナー**] からキャプチャされます。その後 \[**Heap**] を選択します。 |
 | Braze REST エンドポイント | [あなたのRESTエンドポイントURL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)。お客様のエンドポイントは、お客様のインスタンスのBraze URLに依存します。 |
-| トレジャーデータの静的IPアドレス | トレジャーデータの静的IPアドレスは、この統合のリンクのアクセス ポイントおよびソースです。静的IPアドレスを決定するには、トレジャーデータのカスタマーサクセス担当者またはトレジャーデータの技術サポートに連絡してください。 |
+| トレジャーデータの静的IPアドレス | トレジャーデータの静的 IP アドレスは、この統合のリンクのアクセスポイントおよびソースです。静的 IP アドレスを確認するには、トレジャーデータのカスタマーサクセス担当者またはトレジャーデータの技術サポートにご連絡ください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## データインポート統合
@@ -32,17 +32,17 @@ Brazeで、**Partner Integrations** > **Technology Partners** に移動し、**
 
 ### ステップ2:データ接続を作成する
 
-トレジャーデータ内でデータ接続を作成する前に、認証が必要です。まず、**インテグレーションハブ**を選択し、次に**カタログ**を選択します。
+トレジャーデータ内でデータ接続を作成する前に、認証が必要になります。まず、**インテグレーションハブ**を選択し、次に**カタログ**を選択します。
 
-![トレジャーデータ インテグレーションズ ハブ カタログ]({% image_buster /assets/img/treasure_data/cohort/cohort1.png %}) 
+![トレジャーデータの「Integrations Hub」と「Catalog」]({% image_buster /assets/img/treasure_data/cohort/cohort1.png %}) 
 
 **カタログ**でBraze統合を検索し、アイコンにカーソルを合わせて**認証の作成**を選択します。資格情報を入力し、認証に名前を付けて、**完了**を選択します。
 
-![トレジャーデータ インテグレーションズ ハブ カタログ]({% image_buster /assets/img/treasure_data/cohort/cohort2.png %}) 
+![トレジャーデータの「Integrations Hub」と「Catalog」]({% image_buster /assets/img/treasure_data/cohort/cohort2.png %}) 
 
 ### ステップ 3:コホートオーディエンスを定義する
 
-オーディエンススタジオ**Audience Studio**またはデータワークベンチ**Data Workbench**でクエリを実行することによって、Brazeにコホートを同期します。
+**Audience Studio** でのアクティベーション、または **Data Workbench** でクエリを実行して、コホートを Braze に同期します。
 
 {% alert important %}
 Braze内に既に存在するユーザーのみがコホートに追加または削除されます。コホートインポートはBrazeに新しいユーザーを作成しません。
@@ -53,22 +53,22 @@ Braze内に既に存在するユーザーのみがコホートに追加または
 #### ステップ 3.1:クエリを定義する
 
 {% alert note %}
-クエリ列は正確な列名とデータ型で指定する必要があります。クエリ列には、少なくとも次の列のいずれかが含まれている必要があります: `user_ids`、`device_ids`、またはBrazeエイリアス列がUIの構成と一致します。Braze内に存在するユーザーのプロファイルのみがコホートに追加されます。コホートインポートでは、新しいユーザープロファイルは作成されません。
+クエリ列は正確な列名とデータ型で指定する必要があります。クエリの列には、`user_ids`、`device_ids`、または UI の設定と一致する Braze エイリアス列のうち、1つ以上の列が含まれている必要があります。Braze内に存在するユーザーのプロファイルのみがコホートに追加されます。コホートインポートでは、新しいユーザープロファイルは作成されません。
 {% endalert %}
 
 1. **データワークベンチ** > **クエリ** に移動します。
 2. **新しいクエリ**を選択します。
 3. クエリを実行して結果セットを検証します。
 
-![トレジャーデータ インテグレーションズ ハブ カタログ]({% image_buster /assets/img/treasure_data/cohort/cohort3.png %})
+![トレジャーデータの「Integrations Hub」と「Catalog」]({% image_buster /assets/img/treasure_data/cohort/cohort3.png %})
 
 ##### ユースケース:識別子によるコホートの同期
 
 {% subtabs local %}
 {% subtab Syncing External IDs %}
-こちらはトレジャーデータの例のテーブルです：
+次にトレジャーデータのテーブルの例を示します。
 
-| external_id |	email	| デバイスID |
+| external_id |	email	| device_ids |
 | ----------- | ----------- | ----------- |
 | `TDCohort1`	| `TDCohort1@gmail.com`	| `1a2b3c` |
 | `TDCohort2`	| `TDCohort2@gmail.com`	| `4d5f6g` |
@@ -79,7 +79,7 @@ Braze内に既に存在するユーザーのみがコホートに追加または
 列名は`user_ids`である必要があります。そうでないと同期が失敗します。
 {% endalert %}
 
-コホートをexternal IDを使用して同期するには、次のクエリを実行します:
+external ID を使用してコホートを同期するには、次のクエリを実行します。
 
 ```sql
 SELECT
@@ -97,9 +97,9 @@ FROM
 {% endsubtab %}
 
 {% subtab Syncing User Aliases %}
-こちらはトレジャーデータの例のテーブルです：
+次にトレジャーデータのテーブルの例を示します。
 
-| external_id |	email	| デバイスID |
+| external_id |	email	| device_ids |
 | ----------- | ----------- | ----------- |
 | `TDCohort1`	| `TDCohort1@gmail.com`	| `1a2b3c` |
 | `TDCohort2`	| `TDCohort2@gmail.com`	| `4d5f6g` |
@@ -124,9 +124,9 @@ FROM
 {% endsubtab %}
 
 {% subtab Syncing Device IDs %}
-こちらはトレジャーデータの例のテーブルです：
+次にトレジャーデータのテーブルの例を示します。
 
-| external_id |	email	| デバイスID |
+| external_id |	email	| device_ids |
 | ----------- | ----------- | ----------- |
 | `TDCohort1`	| `TDCohort1@gmail.com`	| `1a2b3c` |
 | `TDCohort2`	| `TDCohort2@gmail.com`	| `4d5f6g` |
@@ -157,16 +157,16 @@ FROM
 
 #### ステップ 3.2:結果のエクスポートターゲットを指定します
 
-クエリが構築されたら、**結果をエクスポート**を選択します。既存の認証を選択するか、最後の手順で作成した認証を選択するか、新しい認証を作成して出力に使用できます。 
+クエリが構築されたら、**結果をエクスポート**を選択します。既存の認証 (前回の手順で作成した認証など) を選択するか、または出力に使用する新しい認証を作成できます。 
 
-![トレジャーデータ インテグレーションズ ハブ カタログ]({% image_buster /assets/img/treasure_data/cohort/cohort5.png %}) 
+![トレジャーデータの「Integrations Hub」と「Catalog」]({% image_buster /assets/img/treasure_data/cohort/cohort5.png %}) 
 
 
 | エクスポート結果マッピング |	説明	| 
 | ----------- | ----------- |
 | コホートID	| これは、Brazeに送信されるバックエンドのコホート識別子です。 	|
 | コホート名（任意）	| これは、Brazeのセグメンテーションツール内のコホートフィルターに表示される名前です。これが設定されていない場合、`Cohort ID`は`Cohort Name`として使用されます。	|
-| 操作	| クエリがBrazeのコホートからプロファイルを追加または削除するかどうかを判断するために使用されます。	| 
+| Operation	| クエリがBrazeのコホートからプロファイルを追加または削除するかどうかを判断するために使用されます。	| 
 | 別名（オプション） | 定義されている場合、クエリ内の対応する列の名前は`alias_label`として送信され、列内の各行の値は`alias_name`として送信されます。	| 
 | スレッド数 | 同時API呼び出しの数。 |
 
@@ -174,7 +174,7 @@ FROM
 
 #### ステップ 3.3:クエリを実行する
 
-クエリを名前で保存して実行するか、クエリを実行するだけです。クエリが正常に完了すると、クエリ結果は自動的にBrazeにエクスポートされます。
+クエリに名前を付けて保存して実行するか、またはクエリを実行します。クエリが正常に完了すると、クエリ結果は自動的にBrazeにエクスポートされます。
 
 {% endtab %}
 {% tab オーディエンス スタジオ %}
@@ -182,9 +182,9 @@ FROM
 
 新しいSegmentを作成するか、既存のSegmentを選択して、コホートとしてBrazeに同期します。セグメント内で、**アクティベーションを作成**を選択します。
 
-#### ステップ 3.2:アクティベーションの詳細を記入してください
+#### ステップ 3.2:アクティベーションの詳細を入力する
 
-![トレジャーデータインテグレーションのアクティベーション詳細]({% image_buster /assets/img/treasure_data/cohort/cohort7.png %}) 
+![トレジャーデータ統合のアクティベーションの詳細]({% image_buster /assets/img/treasure_data/cohort/cohort7.png %}) 
 
 | アクティベーション詳細設定 |	説明	| 
 | ----------- | ----------- |
@@ -193,7 +193,7 @@ FROM
 | 認証	| ステップ2で作成されたBrazeコホート認証を選択します。	| 
 | コホートID	| これは、Brazeに送信されるバックエンドのコホート識別子です。 	|
 | コホート名（任意）	| これは、Brazeのセグメンテーションツール内のコホートフィルターに表示される名前です。これが設定されていない場合、`Cohort ID`は`Cohort Name`として使用されます。	|
-| 操作	| クエリがBrazeのコホートからプロファイルを追加または削除するかどうかを判断するために使用されます。	| 
+| Operation	| クエリがBrazeのコホートからプロファイルを追加または削除するかどうかを判断するために使用されます。	| 
 | 別名（オプション） | 定義されている場合、クエリ内の対応する列の名前は`alias_label`として送信され、列内の各行の値は`alias_name`として送信されます。	| 
 | スレッド数 | 同時API呼び出しの数。 |
 
@@ -204,7 +204,7 @@ FROM
 | アクティベーション出力マッピング |	説明	| 
 | ----------- | ----------- |
 | 属性カラム	| セグメントデータベースから列を特定し、プロファイルをBrazeコホートに同期する際に識別子としてマッピングされるようにします。	|
-| 文字列ビルダー| Braze統合には文字列ビルダーは必要ありません。	|
+| String Builder| Braze統合には文字列ビルダーは必要ありません。	|
 
 {% alert important %}
  - `device_id`を識別子として使用する場合、**出力列名**は`device_ids`と名付ける必要があります。
@@ -218,12 +218,12 @@ FROM
 
 希望する同期スケジュールを定義し、アクティベーションを保存します。
 
-![トレジャーデータ インテグレーションの有効化スケジュール]({% image_buster /assets/img/treasure_data/cohort/cohort8.png %})
+![トレジャーデータ統合のアクティベーションのスケジュール]({% image_buster /assets/img/treasure_data/cohort/cohort8.png %})
 {% endtab %}
 {% endtabs %}
 
-### ステップ 4:トレジャーデータエクスポートからBrazeセグメントを作成する
+### ステップ 4:Treasure Data Export から Braze セグメントを作成する
 
-Brazeで、**Segment**に移動し、新しいセグメントを作成して、フィルターとして**トレジャーデータコホート**を選択します。ここから、含めたいトレジャーデータのコホートを選択できます。トレジャーデータコホートSegmentが作成された後、キャンペーンやキャンバスを作成する際にオーディエンスフィルターとして選択できます。
+Brazeで、**Segment**に移動し、新しいセグメントを作成して、フィルターとして**トレジャーデータコホート**を選択します。ここから、どのトレジャーデータコホートを含めるかを選択できます。トレジャーデータのコホートセグメントを作成したら、キャンペーンまたはキャンバスを作成するときにこのセグメントをオーディエンスフィルターとして選択できます。
 
-![トレジャーデータ インテグレーションズ ハブ カタログ]({% image_buster /assets/img/treasure_data/cohort/cohort4.png %}) 
+![トレジャーデータの「Integrations Hub」と「Catalog」]({% image_buster /assets/img/treasure_data/cohort/cohort4.png %}) 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/crash_analytics.md b/_lang/ja/_partners/data_and_infrastructure_agility/crash_analytics.md
index b279f83272d..3de6a1d6084 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/crash_analytics.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/crash_analytics.md
@@ -6,7 +6,7 @@ page_order: 4
 
 page_type: landing
 search_tag: Partner
-description: "このランディングページには、アプリケーションからのクラッシュデータの解析を可能にするBrazeパートナー（合金）がリストアップされている。"
+description: "このランディングページには、アプリケーションのクラッシュデータを分析できるようにする Braze パートナー (Alloys) が一覧表示されています。"
 
 partner_api: "https://www.braze.com/api/v1/partners"
 partner_path: "https://www.braze.com/product/alloys/partners/"
@@ -15,7 +15,7 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Crash Analytics"
 
 valid_partner_list:
-- name: アプテリジェント
+- name: Apteligent
   url: /docs/partners/data_and_infrastructure_agility/crash_analytics/apteligent/
 
 ---
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/crash_analytics/apteligent.md b/_lang/ja/_partners/data_and_infrastructure_agility/crash_analytics/apteligent.md
index 30deaa61024..da94915355e 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/crash_analytics/apteligent.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/crash_analytics/apteligent.md
@@ -1,16 +1,16 @@
 ---
-nav_title: アプテリジェント
-article_title: アプテリジェント
+nav_title: Apteligent
+article_title: Apteligent
 alias: /partners/apteligent/
-description: "この参考記事では、BrazeとApteligentのパートナーシップについて概説している。Apteligentは、クラッシュ報告の詳細を提供するモバイル・アプリケーションで、重要なデータを既存のBrazeソリューションに記録することができる。"
+description: "このリファレンス記事では、Braze と Apteligent のパートナーシップについて説明します。Apteligent は、詳細なクラッシュレポートを作成するモバイルアプリケーションであり、重要なデータを既存の Braze ソリューションに記録できるようにします。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# アプテリジェント
+# Apteligent
 
-> [Apteligentは](https://www.vmware.com/products/workspace-one/intelligence-consumer-apps.html)モバイル・アプリケーション・パフォーマンス・プラットフォームで、開発者やプロダクト・マネージャーにツールと洞察を提供している。 
+> [Apteligent](https://www.vmware.com/products/workspace-one/intelligence-consumer-apps.html) は、開発者と製品マネージャーにツールとインサイトを提供するモバイルアプリケーションパフォーマンスプラットフォームです。 
 
 BrazeとApteligentの統合は、詳細なiOSクラッシュレポートを提供し、重要なデータを既存のBrazeソリューションに記録するだけでなく、アプリケーションのクラッシュを経験したユーザーをセグメント化し、理解し、エンゲージすることを可能にする。
 
@@ -18,7 +18,7 @@ BrazeとApteligentの統合は、詳細なiOSクラッシュレポートを提
 
 | 必要条件 | 説明 |
 |---|---|
-| テストドライブアカウント | このパートナーシップを利用するには、テストドライブのアカウントが必要だ。 |
+| TestDrive アカウント | このパートナーシップを活用するには、TestDrive アカウントが必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert warning %}
@@ -29,7 +29,7 @@ BrazeとApteligentの統合は、詳細なiOSクラッシュレポートを提
 
 ### ステップ1:オブザーバーを登録する
 
-まず、オブザーバーを登録しなければならない。これは、Apteligentを初期化する前に行っておくこと。
+最初にオブザーバーを登録する必要があります。Apteligent を初期化する前に、この登録が完了していることを確認してください。
 
 ```objc
 [[NSNotificationCenter defaultCenter] addObserver:self
@@ -38,11 +38,11 @@ BrazeとApteligentの統合は、詳細なiOSクラッシュレポートを提
                                            object:nil];
 ```
 
-### ステップ2:カスタム・クラッシュ解析を記録する
+### ステップ2:カスタムクラッシュ分析を記録する
 
-Apteligent SDKは、クラッシュが発生した後、ユーザーがアプリケーションをロードすると通知を発する。通知には、クラッシュの名称、理由、発生日が記載される。
+Apteligent SDK は、クラッシュが発生した後、ユーザーがアプリケーションをロードしたときに通知を発行します。通知には、クラッシュの名前、理由、発生日が含まれます。
 
-通知を受信したら、カスタムクラッシュイベントを記録し、Apteligentのクラッシュレポート分析でユーザー属性を更新する：
+通知を受け取ったら、カスタムクラッシュイベントをログに記録し、Apteligent のクラッシュレポート分析を使用してユーザー属性を更新します。
 
 ```objc
 - (void)crashDidOccur:(NSNotification*)notification {
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform.md
index b390807d160..0f08c218e15 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform.md
@@ -1,6 +1,6 @@
 ---
-nav_title: 顧客データ・プラットフォーム
-article_title: 顧客データ・プラットフォーム・パートナー
+nav_title: 顧客データプラットフォーム
+article_title: 顧客データプラットフォームのパートナー
 page_order: 5
 
 page_type: landing
@@ -28,25 +28,25 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/
 - name: アンペア
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/amperity/
-- name: レベニューキャット
+- name: RevenueCat
   url: /docs/partners/data_and_infrastructure_agility/payments/revenuecat/
-- name: ブルーコニック
+- name: BlueConic
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/blueconic/
 - name: Zeotap
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/zeotap/
-- name: トゥービオ
+- name: Toovio
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/toovio/
-- name: レクサー
+- name: Lexer
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/lexer/
 - name: Microsoft Dynamics 365
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights/
-- name: オクトリス
+- name: Octolis
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/octolis/
-- name: アクションIQ
+- name: ActionIQ
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/actioniq/
 - name: Redpoint
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/redpoint/
-- name: サイモン・データ
+- name: Simon Data
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/simondata/
 - name: Ketch
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/ketch/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/actioniq.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/actioniq.md
index c549ed135d2..17e2340c207 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/actioniq.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/actioniq.md
@@ -1,32 +1,32 @@
 ---
-nav_title: アクションIQ
-article_title: アクションIQ
+nav_title: ActionIQ
+article_title: ActionIQ
 description: "この参考記事では、BrazeとActionIQの統合について取り上げている。ActionIQは、マーケティング担当者、アナリスト、技術者のための企業向け顧客データ・プラットフォームである。この統合により、ブランドはActionIQのデータをBrazeに直接同期し、マッピングすることができる。"
 alias: /partners/actioniq/
 page_type: partner
 search_tag: ActionIQ
 ---
 
-# アクションIQ
+# ActionIQ
 
-> [ActionIQは][2]カスタマー・エクスペリエンスの混沌に秩序をもたらす。ActionIQカスタマー・エクスペリエンス（CX）ハブは、すべてのチームが顧客データに直接、しかしコントロールされたセルフサービスでアクセスできるようにし、オーディエンスを発見し、規模に応じたエクスペリエンスをオーケストレーションする。
+> [ActionIQ][2]は、混沌としたカスタマーエクスペリエンスに秩序をもたらします。ActionIQ Customer Experience (CX) Hub では、すべてのチームが、直接かつ制御されたセルフサービスで顧客データにアクセスできます。これにより、オーディエンスを発見し、エクスペリエンスを大規模にオーケストレーションできます。
 
-BrazeとActionIQの統合により、ブランドはActionIQデータを直接Brazeと同期させ、マッピングすることができる。この統合により、ユーザーは以下のことが可能になる：
+Braze と ActionIQ の統合により、ブランドは ActionIQ データを直接 Braze に同期してマッピングできます。これにより、幅広い顧客データ全体に基づく卓越したカスタマーエクスペリエンスを提供できるようになります。この統合により、ユーザーは以下のことが可能になる：
 - ActionIQから直接、オーディエンスセグメントやカスタム属性をBrazeにマッピングする
-- ActionIQがトラッキングしたイベントをリアルタイムでBrazeに転送し、パーソナライズされたターゲットキャンペーンをトリガーする。
+- ActionIQ で追跡されたイベントをリアルタイムで Braze に転送し、パーソナライズされ、ターゲットを絞ったキャンペーンをトリガーする
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
 | ActionIQアカウント | この統合を利用するには、ActionIQアカウントが必要である。 |
-| Braze REST API キー | `users.track` および`user.export.ids` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
+| Braze REST API キー | `users.track` および `user.export.ids` の権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][1]。エンドポイントは、インスタンスのBraze URLに依存する。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### 観客数
+### オーディエンスのメンバーシップ
 
 この統合は、Brazeのプロファイルがセグメントに属しているかどうかを示すカスタム属性を作成することによって、ActionIQのオーディエンスメンバーシップをBrazeと同期させるために使用される。各ActionIQオーディエンスは、固有のブーリアン・カスタム属性に対応している。
 
@@ -36,9 +36,9 @@ BrazeとActionIQの統合により、ブランドはActionIQデータを直接Br
 
 #### 要件
 
-ActionIQで、REST APIキーとBraze RESTエンドポイントを提供して、Braze接続をセットアップする。 
+ActionIQ で、REST API キーと Braze REST エンドポイントを指定して、Braze 接続を設定します。 
 
-Brazeプラットフォームのコンシューマーにマッチさせるには、アクティベーション設定に以下の識別子を含める必要がある：
+Braze プラットフォームで消費者と一致するためには、アクティベーション設定に次の識別子が含まれている必要があります。
 - `braze_id`
 - `external_id`
 
@@ -56,7 +56,7 @@ ActionIQプラットフォームは、ストリーミング・インジェスト
 - イベント名
 - 消費者識別子（`braze_id` または`external_id` ）。
 - タイムスタンプ
-- イベント・プロパティは、エクスポート設定で追加された属性によって設定される。
+- イベントプロパティ (エクスポート設定で追加の属性により取り込まれる)
 
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe.md
index ac41153de55..702d71164f4 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe.md
@@ -5,9 +5,9 @@ page_type: partner
 search_tag: Partner
 layout: dev_guide
 guide_top_header: "Adobe"
-guide_top_text: "Adobe Experience Platform上に構築されたアドビのリアルタイム顧客データプラットフォームは、企業が複数の企業ソースから既知および匿名のデータを集めて顧客プロファイルを作成するのを支援する。これらのプロファイルは、リアルタイムですべてのチャネルとデバイスにパーソナライズされた体験を提供するために使用することができる。"
+guide_top_text: "Adobe Experience Platform 上に構築されている Adobe のリアルタイム顧客データプラットフォームにより、企業は複数のエンタープライズソースからの既知の匿名データをまとめて、カスタマープロファイルを作成できます。その後、これらのプロファイルを使用して、パーソナライズされたエクスペリエンスをすべてのチャネルおよびデバイスでリアルタイムで提供できます。"
 
-description: "このランディングページには、アドビの統合方法やイベント転送エクステンションの使用方法など、アドビに関するあらゆる情報が掲載されている。"
+description: "このランディングページは、Adobe を統合してイベント転送拡張機能を使用する方法など、Adobe に関するあらゆる情報のホームページです。"
 
 guide_featured_list:
 - name: Adobe
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe.md
index a46f654d8c6..4984140712e 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/adobe.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Adobe
 article_title: Adobe
-description: "このリファレンス記事では、Braze と顧客データプラットフォーム であるAdobe との提携について説明します。これにより、ブランドは、Adobe データ(カスタム属性 s およびSegment s) をリアルタイムでBrazeに接続し、マップできます。そうすれば、ブランドはこの情報に基づいて行動し、パーソナライズされたなターゲットを絞った体験をユーザーに提供することができる。"
+description: "このリファレンス記事では、Braze と Adobe のパートナーシップについて説明します。Adobe は顧客データプラットフォームであり、ブランドはリアルタイムで Braze に接続し、Adobe データ (カスタム属性とセグメント) を Braze にマッピングできます。そうすれば、ブランドはこの情報に基づいて行動し、パーソナライズされたなターゲットを絞った体験をユーザーに提供することができる。"
 page_type: partner
 page_order: 1
 search_tag: Partner
@@ -10,34 +10,34 @@ search_tag: Partner
 
 # Adobe
 
-> Adobe Experience プラットフォームに基づいて構築されたAdobeのリアルタイム顧客データプラットフォームは、企業が複数のエンタープライズソースからの既知の匿名データをまとめて顧客 プロファイルを作成するのに役立ちます。これらのプロファイルを使用すると、すべてのチャネルおよび機器にリアルタイムでパーソナライズされた体験を提供できます。
+> Adobe Experience プラットフォームに基づいて構築されたAdobeのリアルタイム顧客データプラットフォームは、企業が複数のエンタープライズソースからの既知の匿名データをまとめて顧客 プロファイルを作成するのに役立ちます。その後、これらのプロファイルを使用して、パーソナライズされたエクスペリエンスをすべてのチャネルおよびデバイスでリアルタイムで提供できます。
 
-Braze とAdobe CDP インテグレーションを使用すると、ブランドはAdobe データ(カスタム属性 s およびSegment s) をリアルタイムでBrazeに接続してマッピングできます。そうすれば、ブランドはこの情報に基づいて行動し、パーソナライズされたなターゲットを絞った体験をユーザーに提供することができる。Adobeでは、統合は直感的です。Adobe [identity](https://experienceleague.adobe.com/docs/experience-platform/identity/namespaces.html?lang=en) を使用して、Brazeの外部ID にマッピングし、Braze プラットフォームに送信するだけです。送信されるすべてのデータは、新しい`AdobeExperiencePlatformSegments` 属性を介してBrazeでアクセスできます。
+Braze とAdobe CDP の統合により、ブランドはリアルタイムで Braze に接続し、Adobe データ (カスタム属性とセグメント) を Braze にマッピングできます。そうすれば、ブランドはこの情報に基づいて行動し、パーソナライズされたなターゲットを絞った体験をユーザーに提供することができる。Adobeでは、統合は直感的です。Adobe の任意の [ID](https://experienceleague.adobe.com/docs/experience-platform/identity/namespaces.html?lang=en) を Braze の external ID にマッピングし、Braze プラットフォームに送信するだけです。Braze では、新しい `AdobeExperiencePlatformSegments` 属性を使用して、送信されるすべてのデータにアクセスできます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| Adobeアカウント | この提携の事前タグを行うには、[Adobeアカウント](https://account.adobe.com/)が必要です。 |
-| Braze REST API キー | `users.track` 権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
+| Adobeアカウント | このパートナーシップを活用するには、[Adobe アカウント](https://account.adobe.com/)が必要です。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
 | Brazeインスタンス | Brazeインスタンスは、Braze オンボーディング マネージャーから取得するか、[API 概要ページ]({{site.baseurl}}/api/basics/#endpoints) にあります。 |
-| Braze REST エンドポイント | REST エンドポイントのURL。エンドポイントは、インスタンス の[ Braze URL によって異なります。 |
+| Braze REST エンドポイント | REST エンドポイントのURL。エンドポイントはインスタンスの [Braze URL]({{site.baseurl}}/api/basics/#endpoints) に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert important %}
-追加のカスタム属性s を送信すると、データポイント使用量が増えることに注意してください。この潜在的なデータポイント上昇をより良く理解するために、あなたの顧客サクセスマネージャーと話すことをお勧めします。
+追加のカスタム属性s を送信すると、データポイント使用量が増えることに注意してください。このデータポイントの増加の可能性をよりよく理解するために、お客様のカスタマーサクセスマネージャーと話すことをお勧めします。
 {% endalert %}
 
 ## 統合
 
-### ステップ1:Braze 送信先の設定
+### ステップ1:Braze 宛先を設定する
 
 Adobe **Settings**ページで、**Destinations**を**Collections**から選択します。そこから、**Braze**タイルを見つけ、**Configure**を選択します。 
 
 ![][1]
 
 {% alert note %}
-Braze との接続がすでに存在する場合は、送信先 カードに**Activate** が表示されます。activateとconfigureの違いについては、Adobe 送信先 ワークスペース [ドキュメント](https://experienceleague.adobe.com/docs/experience-platform/rtcdp/destinations/destinations-interface/destinations-workspace.html?lang=en#catalog)のカタログを参照してください。
+Braze との接続がすでに存在する場合は、送信先 カードに**Activate** が表示されます。\[Activate] と \[Configure] の違いの詳細については、Adobe 宛先ワークスペースの[ドキュメント](https://experienceleague.adobe.com/docs/experience-platform/rtcdp/destinations/destinations-interface/destinations-workspace.html?lang=en#catalog)の「カタログ」セクションを参照してください。
 {% endalert %}
 
 ### ステップ2:Braze トークンの提供
@@ -49,38 +49,38 @@ Braze との接続がすでに存在する場合は、送信先 カードに**Ac
 ### ステップ3:認証
 
 次に、**Authentication**ステップで、Brazeコネクションの詳細を入力する必要があります。
-- **名前**:今後この送信先を認識したい名前を入力します。
-- **宛先**:この送信先の識別に役立つ説明を入力します。
+- **Name**:今後この宛先を認識するために使用する名前を入力します。
+- **Destination**:この宛先を特定するのに役立つ説明を入力します。
 - **エンドポイントインスタンス**:Braze エンドポイントを入力します。
-- **販売ユースケース**:マーケティングユースケースは、データを送信先にエクスポートする目的を示します。Adobe定義のマーケティング ユースケースから選択するか、独自のマーケティング ユースケースを作成できます。Adobe マーケティング ユースケース sの詳細については、Adobe Experience Platformの[データガバナンスを参照してください。
+- **マーケティングユースケース**:マーケティングユースケースは、データを送信先にエクスポートする目的を示します。Adobe定義のマーケティング ユースケースから選択するか、独自のマーケティング ユースケースを作成できます。Adobe マーケティングユースケースの詳細については、[Adobe Experience Platform のデータガバナンス](https://experienceleague.adobe.com/docs/experience-platform/rtcdp/privacy/data-governance-overview.html?lang=en#destinations)を参照してください。
 
 ![][4]{: style="max-width:60%;"}
 
-### ステップ4:送信先の作成
-**送信先の作成**を押します。送信先が作成されました。**Save & Exit** をクリックしてSegment s 以降を有効にするか、**Next** をクリックしてワークフローを続行し、Segment s を選択して有効にします。 
+### ステップ4:宛先を作成する
+\[**Create destination**.] をクリックします。これで宛先が作成されました。\[**Save & Exit**] をクリックしてセグメントを後からアクティブにするか、\[**Next**] をクリックしてワークフローを続行し、アクティブにするセグメントを選択します。 
 
 ### ステップ 5: Segmentの有効化
-Braze 送信先にs をアプリすることで、Adobe リアルタイムCDP にあるデータを有効にします。
+Adobe Real-Time CDP で使用しているデータをアクティブにするには、セグメントを Braze 宛先にマッピングします。
 
-次の一覧では、Segmentを有効にするために必要な全般的なステップを示します。Adobe Segment s とSegmentアクティベーションワークフローの詳細なガイダンスについては、[Adobe](https://experienceleague.adobe.com/docs/experience-platform/destinations/ui/activate-destinations.html?lang=en#prerequisites) をご覧ください。
+次の一覧では、Segmentを有効にするために必要な全般的なステップを示します。Adobe のセグメントとセグメントアクティベーションワークフローの詳細なガイダンスについては、[Adobe](https://experienceleague.adobe.com/docs/experience-platform/destinations/ui/activate-destinations.html?lang=en#prerequisites) を参照してください。
 
-1. Braze 送信先を選択して有効にします。
-2. アプリライセンス可能Segmentsを選択します。
+1. Braze 宛先を選択してアクティブ化します。
+2. 該当するセグメントを選択します。
 4. エクスポートするSegmentごとにスケジュールとファイル名を設定します。
 5. Brazeに送信する属性sを選択します。
-6. アクティベーションを確認して確認します。
+6. アクティベーションを確認します。
 
-### ステップ 6: 照射野mのアプリ値
+### ステップ 6: フィールドマッピング
 
-Adobe Experience Platform からBraze にオーディエンスを正しく送信するには、フィールド m アプリ の実行ステップを完了する必要があります。Mアプリingは、Adobe Experienceデータモデルフィールドsと対応するBraze プラットフォーム フィールドsの間にリンクを作成します。
+Adobe Experience Platform から Braze にオーディエンスデータを正しく送信するには、フィールドマッピングステップを完了する必要があります。マッピングにより、Adobe Experience データモデルのフィールドと対応する Braze プラットフォームのフィールドの間にリンクが作成されます。
 
-1. m アプリ ing ステップで、**新しいm アプリを追加**を選択します。<br>![][5]{: style="max-width:50%;"}<br><br>
-2. ソースフィールド部分で、空のフィールドの横にある矢印ボタンをクリックすると、ソースフィールドの選択ウィンドウが開封されます。<br>![][6]<br><br>
-3. このウィンドウでは、Adobe 属性 s を選択してBraze 属性s にマップする必要があります。<br>![][7]{: style="max-width:70%;"}<br><br>次に、ID ネームスペースを選択する必要があります。この項目は、プラットフォーム ID ネームスペースをBraze ネームスペースにマップするために使用されます。<br>![][8]{: style="max-width:80%;"}<br> 入力フィールドを選択し、****を選択します。<br><br>
-4. 対象フィールドで、フィールドの横にあるmアプリのアイコンを選択します。<br>![][9]{: style="max-width:90%;"}<br><br>
-5. ターゲットフィールドの選択ウィンドウで、ターゲットフィールドs の3つのカテゴリから選択できます。<br><br>• **アイデンティティ名前空間を選択**:このオプションを使用して、プラットフォームアイデンティティネームスペースをBrazeアイデンティティネームスペースにマップします。<br>• **カスタム属性を選択s**:このオプションを使用して、Adobe XDM 属性s をBraze アカウントで定義したカスタムBraze 属性s にマップします。<br><br>![][10]{: style="max-width:60%;"}<br><br>**また、XDM 属性の名前をBrazeに変更することもできます。**たとえば、`lastname` XDM 属性をカスタム`Last_Name` 属性にBrazeでm アプリすると、`Last_Name` 属性がまだ存在しない場合はBraze で作成され、`lastname` XDM 属性がマップされます。<br><br> 目的のフィールドsを選択し、**Select**をクリックします。<br><br>
-6. これで、一覧にフィールドm アプリが表示されます。<br>![][11]<br><br>
-7. さらにm個のアプリを追加するには、必要に応じてステップ1～6を繰り返します。 
+1. マッピングステップで \[**Add new mapping**] をクリックします。<br>![][5]{: style="max-width:50%;"}<br><br>
+2. ソースフィールドセクションで、空のフィールドの横にある矢印ボタンをクリックします。これにより、ソースフィールド選択ウィンドウが表示されます。<br>![][6]<br><br>
+3. このウィンドウでは、Braze の属性にマッピングするAdobe の属性を選択する必要があります。<br>![][7]{: style="max-width:70%;"}<br><br>次に、ID ネームスペースを選択する必要があります。この項目は、プラットフォーム ID ネームスペースをBraze ネームスペースにマップするために使用されます。<br>![][8]{: style="max-width:80%;"}<br> ソースフィールドを選択し、\[**Select**] をクリックします。<br><br>
+4. ターゲットフィールドセクションで、フィールドの横にあるマッピングアイコンをクリックします。<br>![][9]{: style="max-width:90%;"}<br><br>
+5. ターゲットフィールド選択ウィンドウでは、ターゲットフィールドの3つのカテゴリから選択できます。<br><br>• **Select identity namespace**:Platform の ID 名前空間を Braze の ID 名前空間にマッピングするには、このオプションを使用します。<br>• **Select custom attributes**:Adobe XDM 属性を、Braze アカウントで定義したカスタム Braze 属性にマッピングするには、このオプションを使用します。<br><br>![][10]{: style="max-width:60%;"}<br><br>**このオプションを使用して、既存の XDM 属性の名前を Braze で変更することもできます。**たとえば、XDM 属性 `lastname` を Braze のカスタム属性 `Last_Name` にマッピングすると、Braze に属性 `Last_Name` がまだ存在しない場合はこの属性が作成され、XDM 属性 `lastname` がそれにマッピングされます。<br><br> 目的のフィールドsを選択し、**Select**をクリックします。<br><br>
+6. これで、フィールドマッピングがリストに表示されます。<br>![][11]<br><br>
+7. マッピングをさらに追加するには、必要に応じて手順1～6を繰り返します。 
 
 ## ユースケース
 
@@ -89,18 +89,18 @@ Adobe Experience Platform からBraze にオーディエンスを正しく送信
 |     | XDM プロファイルスキーマ | Brazeインスタンス |
 | --- | ------------------ | -------------- |
 | 属性 | - `person.name.firstname`<br>- `person.name.lastname`<br>- `mobilePhone.number`| - `FirstName`<br>- `LastName`<br>- `PhoneNumber`|
-| ID | - `Email`<br>\- Google Ad ID (`GAID`)<br>\- Apple ID Advertisers 用(`IDFA`) | - `external_id` |
+| ID | - `Email`<br>\- Google 広告 ID (`GAID`)<br>\- Apple ID Advertisers 用(`IDFA`) | - `external_id` |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-正しいm アプリ ing は次のようになります。
+正しいマッピングは次のようになります。
 
-![デスティネーションm アプリ:IdentityMap:IDFA m がIdentityMap:external_id にアプリしたIdentityMap:external_id:GAID m アプリがIdentityMap:external_id、IdentityMap:email m アプリがIdentityMap:external_id、xdm:mobilePhone.number m アプリがカスタム属性:電話番号、xdm:person.name.lastName m カスタム属性:FirstName に設定されたAtrribute:LastName、xdm:<meta id="4"][12]
+![宛先マッピング:IdentityMap:IDFA が IdentityMap:external_id に、IdentityMap:GAID が IdentityMap:external_id に、IdentityMap:Email が IdentityMap:external_id に、xdm:mobilePhone.number が CustomAttribute:PhoneNumber に、xdm:person.name.lastName が CustomAtrribute:LastName に、xdm:person.name.firstName が CustomAttribute:FirstName にマッピングされている][12]
 
 ## エクスポートされたデータ
-Braze に正常にエクスポートされたかどうかを確認するには、Braze アカウントを確認します。Adobe Experience Platform Segmentは、`AdobeExperiencePlatformSegments`属性でBrazeにエクスポートされます。
+データが正常に Braze にエクスポートされたかどうかを確認するには、Braze アカウントをチェックします。Adobe Experience Platform Segmentは、`AdobeExperiencePlatformSegments`属性でBrazeにエクスポートされます。
 
 ## データの使用とガバナンス
-すべてのAdobe Experience Platform 送信先は、データの処理時にデータ使用ポリシーに準拠しています。Adobe Experience Platform によるデータガバナンスの実施方法の詳細については、[リアルタイムCDP](https://experienceleague.adobe.com/docs/experience-platform/rtcdp/privacy/data-governance-overview.html?lang=en)のデータガバナンスを参照してください。 
+データの処理時に、Adobe Experience Platform のすべての宛先はデータ使用ポリシーに準拠します。Adobe Experience Platform によるデータガバナンスの実施方法の詳細については、[Real-Time CDP のデータガバナンス](https://experienceleague.adobe.com/docs/experience-platform/rtcdp/privacy/data-governance-overview.html?lang=en)を参照してください。 
 
 [1]: {% image_buster /assets/img/adobe/braze-destination-configure.png %}
 [3]: {% image_buster /assets/img/adobe/braze-destination-account.png %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/event_forwarding_extension.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/event_forwarding_extension.md
index 6b5ab0dfddf..0d8d508c08f 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/event_forwarding_extension.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/adobe/event_forwarding_extension.md
@@ -1,53 +1,53 @@
 ---
-nav_title: イベント転送拡張
+nav_title: イベント転送拡張機能
 article_title: Adobe
-description: "このリファレンス記事では、Adobe Experience Platform Edge Networkでキャプチャされたデータを活用し、サーバーサイドイベントの形式でBrazeに送信することを可能にするBrazeイベントフォワード拡張機能について説明します。"
+description: "このリファレンス記事では、Adobe Experience Platform Edge Network でキャプチャされたデータを利用して、サーバー側のイベントの形式でデータを Braze に送信できる Braze イベント転送拡張機能について説明します。"
 page_type: partner
 page_order: 2
 search_tag: Partner
 
 ---
 
-# トラックイベントAPIイベント転送拡張
+# Track Events API イベント転送拡張機能
 
-> Braze Track Events API [イベント転送](https://experienceleague.adobe.com/docs/experience-platform/tags/event-forwarding/overview.html?lang=en)拡張機能を使用すると、Adobe Experience Platform Edge Networkでキャプチャされたデータを活用し、[`/users/track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track) APIを使用してサーバーサイドイベントの形式でBrazeに送信できます。
+> Braze Track Events API の[イベント転送](https://experienceleague.adobe.com/docs/experience-platform/tags/event-forwarding/overview.html?lang=en)拡張機能を使用すると、Adobe Experience Platform Edge Network でキャプチャされたデータを利用して、[`/users/track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track) API を使用してサーバーサイドのイベントの形式でデータを Braze に送信できます。
 
 このドキュメントは、拡張機能の使用例、イベント転送ライブラリへのインストール方法、およびイベント転送[ルール](https://experienceleague.adobe.com/docs/experience-platform/tags/ui/rules.html?lang=en)でその機能を使用する方法について説明しています。
 
 {% alert note %}
-Brazeに属性を送信すると、Brazeのデータポイント消費が増加する可能性があります。送信する前にBrazeアカウントマネージャーに相談してください。Brazeのドキュメントの[課金対象データポイント]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points/#billable-data-points)についての詳細をご参照ください。
+Brazeに属性を送信すると、Brazeのデータポイント消費が増加する可能性があります。属性を送信する前に Braze アカウントマネージャーにお問い合わせください。Brazeのドキュメントの[課金対象データポイント]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points/#billable-data-points)についての詳細をご参照ください。
 {% endalert %}
 
 ## ユースケース
 
-この拡張機能は、Brazeのエッジネットワークからのデータを使用して、顧客分析およびターゲティング機能を活用する必要があります。
+この拡張機能は、顧客分析およびターゲティング機能を利用するために、Braze で Edge Network からのデータを使用する必要があります。
 
-例えば、小売組織がマルチチャネルの存在感（Web サイトとモバイル）を持ち、Web サイトとモバイルプラットフォームからイベントデータとして取引または会話の入力をキャプチャしていると考えてみましょう。 
+たとえば、マルチチャネルプレゼンス (Web サイトとモバイル) で展開しており、Web サイトプラットフォームとモバイルプラットフォームからトランザクション入力と会話入力をイベントデータとして取得している小売組織について考えてみます。 
 
-さまざまな[タグ](https://experienceleague.adobe.com/docs/experience-platform/tags/home.html?lang=en)ルールを使用して、このデータはリアルタイムでエッジネットワークに送信されます。ここから、Braze イベント転送拡張機能は、サーバー側から Braze に関連するイベントを自動的に送信します。
+さまざまな[タグ](https://experienceleague.adobe.com/docs/experience-platform/tags/home.html?lang=en)ルールを使用して、このデータはリアルタイムでエッジネットワークに送信されます。ここから Braze イベント転送拡張機能により、関連するイベントがサーバーサイドから Braze へ自動的に送信されます。
 
 ## レート制限
 
 | API | レート制限 |
 | --- | --- |
-| ユーザー トラック | 1分あたり50,000リクエスト。<br><br>詳細については、[ユーザー トラック API ドキュメント]({{site.baseurl}}/api/endpoints/user_data/post_user_track#rate-limit)を参照してください。
+| ユーザー トラック | 1分あたり50,000件のリクエスト。<br><br>詳細については、[User Track API のドキュメント]({{site.baseurl}}/api/endpoints/user_data/post_user_track#rate-limit)を参照してください。
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:必要な構成の詳細を収集する
 
-Edge NetworkをBrazeに接続するには、次のものが必要です:
+Edge Network を Braze に接続するには、次のものが必要です。
 
-| キータイプ | 説明 |
+| キーのタイプ | 説明 |
 | --- | --- |
 | Brazeインスタンス | Brazeインスタンスは、Brazeオンボーディングマネージャーから取得するか、[API概要ページ]({{site.baseurl}}/api/basics/#endpoints)で見つけることができます。 |
 | Braze REST API キー | すべての権限を持つBraze REST APIキー。<br><br> これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。|
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-### ステップ2:秘密を作成する
+### ステップ2:シークレットを作成する
 
-新しい[イベント転送シークレット](https://experienceleague.adobe.com/docs/experience-platform/tags/event-forwarding/secrets.html?lang=en)を作成し、値を[Braze API キー](https://experienceleague.adobe.com/docs/experience-platform/tags/extensions/server/braze/overview.html?lang=en#configuration-details)に設定します。これは、値を安全に保ちながらアカウントへの接続を認証するために使用されます。
+新しい[イベント転送シークレット](https://experienceleague.adobe.com/docs/experience-platform/tags/event-forwarding/secrets.html?lang=en)を作成し、値を[Braze API キー](https://experienceleague.adobe.com/docs/experience-platform/tags/extensions/server/braze/overview.html?lang=en#configuration-details)に設定します。これは、アカウントへの接続を認証し、値を安全に保護するために使用されます。
 
 ### ステップ3:Braze拡張機能をインストールして構成する
 
@@ -62,13 +62,13 @@ Edge NetworkをBrazeに接続するには、次のものが必要です:
 ![][1]
 
 {% tabs ローカル %}
-{% tab ユーザー Identification %}
+{% tab ユーザー識別 %}
 
 | 入力 | 説明 |
 | --- | --- |
 | 外部ユーザ ID | 長く、ランダムで、よく分散されたUUIDまたはGUID。ユーザーIDの名前を付ける別の方法を選択する場合、それらも長く、ランダムで、よく分散されている必要があります。[推奨されるユーザー ID の命名規則]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/setting_user_ids#suggested-user-id-naming-convention)について詳しく学びます。 |
 | Braze ユーザー ID | Braze ユーザー 識別子。 |
-| ユーザーエイリアス | エイリアスは、代替の一意のユーザー識別子として機能します。エイリアスを使用して、コアユーザーIDとは異なる次元でユーザーを識別します。<br><br>ユーザーエイリアスオブジェクトは2つの部分で構成されています: 識別子自体の`alias_name`とエイリアスの種類を示す`alias_label`。ユーザーは異なるラベルで複数のエイリアスを持つことができますが、`alias_name`ごとに`alias_label`つだけです。 |
+| ユーザーエイリアス | エイリアスは、代替の一意のユーザー識別子として機能します。エイリアスを使用して、コアユーザーIDとは異なる次元でユーザーを識別します。<br><br>ユーザーエイリアスオブジェクトは2つの部分で構成されています: 識別子自体の`alias_name`とエイリアスの種類を示す`alias_label`。ユーザーは、異なるラベルを持つ複数のエイリアスを持つことができますが、`alias_name` は `alias_label` ごとに1つしか持つことができません。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
@@ -82,7 +82,7 @@ Edge NetworkをBrazeに接続するには、次のものが必要です:
 | --- | --- | --- |
 | イベント名 | イベントの名前。 | はい |
 | イベント時間 | ISO 8601または`yyyy-MM-dd'T'HH:mm:ss:SSSZ`形式の日付時刻文字列。 | はい |
-| アプリ識別子 | アプリ識別子または`app_id`は、ワークスペース内の特定のアプリとアクティビティを関連付けるパラメーターです。それは、ワークスペース内のどのアプリと対話しているかを指定します。 | いいえ |
+| アプリ識別子 | アプリ識別子または`app_id`は、ワークスペース内の特定のアプリとアクティビティを関連付けるパラメーターです。これにより、ワークスペース内のどのアプリと対話するかが指定されます。 | いいえ |
 | イベントプロパティ | イベントのカスタムプロパティを含むJSONオブジェクト。 | いいえ |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -101,14 +101,14 @@ Edge NetworkをBrazeに接続するには、次のものが必要です:
 | 姓 | ユーザーの姓。 |
 | 電話 | ユーザーの電話番号。 |
 | メール | ユーザーのメールアドレス。 |
-| 性別 | 次の文字列のいずれか:「M」、「F」、「O」（その他）、「N」（該当なし）、「P」（言いたくない）。 |
+| 性別 | 次の文字列のいずれか:「M」、「F」、「O」(その他)、「N」(該当なし)、「P」(開示しない)。 |
 | 市区町村 | ユーザーの市区町村。 |
 | 国 | ユーザーの国は、[ISO-3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)形式の文字列です。 |
 | 言語 | ユーザーの言語は[ISO-639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes)形式の文字列です。 |
 | 生年月日 | 文字列形式のユーザーの生年月日（例：1980-12-21）。 |
-| タイムゾーン | タイムゾーン名は、[IANA Time Zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)データベースから取得します（例：'America/New_York' または 'Eastern Time (US & Canada)'）。 |
+| タイムゾーン | [IANA タイムゾーンデータベース](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)からのタイムゾーン名 (たとえば、「America/New_York」または「東部標準時 (アメリカおよびカナダ)」)。 |
 | Facebook | `id`（文字列）、`likes`（文字列の配列）、`num_friends`（整数）のいずれかを含むハッシュ。 |
-| ツイッター | id（整数）、`screen_name`（文字列、X（旧Twitter）ハンドル）、`followers_count`（整数）、`friends_count`（整数）、`statuses_count`（整数）を含むハッシュ。 |
+| Twitter | `screen_name` (整数)、`followers_count` (文字列、X (旧 Twitter) ハンドル)、`friends_count` (整数)、`statuses_count` (整数) のいずれかを含むハッシュ。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
@@ -125,13 +125,13 @@ Edge NetworkをBrazeに接続するには、次のものが必要です:
 ![][3]
 
 {% tabs ローカル %}
-{% tab ユーザー Identification %}
+{% tab ユーザー識別 %}
 
 | 入力 | 説明 |
 | --- | --- |
 | 外部ユーザ ID | 長く、ランダムで、よく分散されたUUIDまたはGUID。ユーザーIDの名前を付ける別の方法を選択する場合、それらも長く、ランダムで、よく分散されている必要があります。[推奨されるユーザー ID の命名規則]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/setting_user_ids#suggested-user-id-naming-convention)について詳しく学びます。 |
 | Braze ユーザー ID | Braze ユーザー 識別子。 |
-| ユーザーエイリアス | エイリアスは、代替の一意のユーザー識別子として機能します。エイリアスを使用して、コアユーザーIDとは異なる次元でユーザーを識別します。<br><br>ユーザーエイリアスオブジェクトは2つの部分で構成されています: 識別子自体の`alias_name`とエイリアスの種類を示す`alias_label`。ユーザーは異なるラベルで複数のエイリアスを持つことができますが、`alias_name`ごとに`alias_label`つだけです。 |
+| ユーザーエイリアス | エイリアスは、代替の一意のユーザー識別子として機能します。エイリアスを使用して、コアユーザーIDとは異なる次元でユーザーを識別します。<br><br>ユーザーエイリアスオブジェクトは2つの部分で構成されています: 識別子自体の`alias_name`とエイリアスの種類を示す`alias_label`。ユーザーは、異なるラベルを持つ複数のエイリアスを持つことができますが、`alias_name` は `alias_label` ごとに1つしか持つことができません。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
@@ -144,20 +144,20 @@ Edge NetworkをBrazeに接続するには、次のものが必要です:
 | 入力 | 説明 | 必須 |
 | --- | --- | --- |
 | 製品ID | 購入のための識別子。（例えば、製品名や製品カテゴリ） | はい |
-| 購入時間 | ISO 8601または`yyyy-MM-dd'T'HH:mm:ss:SSSZ`形式の日付時刻文字列。 | はい |
+| 購入時刻 | ISO 8601 または `yyyy-MM-dd'T'HH:mm:ss:SSSZ` 形式の日時 (文字列)。 | はい |
 | 通貨 | [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) アルファベット通貨コード形式の文字列としての通貨。 | はい |
 | 価格 | 物の価格。 | はい |
-| 数量 | 購入数量。提供されていない場合、デフォルト値は1になります。最大値は100未満でなければなりません。 | いいえ |
-| アプリ識別子 | アプリ識別子または`app_id`は、ワークスペース内の特定のアプリとアクティビティを関連付けるパラメーターです。それは、ワークスペース内のどのアプリと対話しているかを指定します。 | いいえ |
+| 数量 | 購入数量。提供されていない場合、デフォルト値は1になります。最大値は100未満にする必要があります。 | いいえ |
+| アプリ識別子 | アプリ識別子または`app_id`は、ワークスペース内の特定のアプリとアクティビティを関連付けるパラメーターです。これにより、ワークスペース内のどのアプリと対話するかが指定されます。 | いいえ |
 | 購入プロパティ | 購入のカスタムプロパティを含むJSONオブジェクト。 | いいえ |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 {% alert note %}
-**購入イベントの送信**アクションには、`Product ID`、`Purchase Time`、`Currency`、および`Price`のみを指定する必要がありますが、購入プロパティフィールドにできるだけ多くの情報を含める必要があります。詳細については[購入オブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/)を参照してください。
+**Send Purchase Event** アクションには、`Product ID`、`Purchase Time`、`Currency`、および `Price` のみを指定する必要がありますが、購入プロパティフィールドにできるだけ多くの情報を含める必要があります。詳細については[購入オブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/)を参照してください。
 {% endalert %}
 
 {% endtab %}
-{% tab ユーザー Attributes %}
+{% tab ユーザー属性 %}
 
 構成ビュー内の各イベントに属性を送信するかどうかを選択できます。
 
@@ -169,14 +169,14 @@ Edge NetworkをBrazeに接続するには、次のものが必要です:
 | 姓 | ユーザーの姓。 |
 | 電話 | ユーザーの電話番号。 |
 | メール | ユーザーのメールアドレス。 |
-| 性別 | 次の文字列のいずれか:「M」、「F」、「O」（その他）、「N」（該当なし）、「P」（言いたくない）。 |
+| 性別 | 次の文字列のいずれか:「M」、「F」、「O」(その他)、「N」(該当なし)、「P」(開示しない)。 |
 | 市区町村 | ユーザーの市区町村。 |
 | 国 | ユーザーの国は、[ISO-3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)形式の文字列です。 |
 | 言語 | ユーザーの言語は[ISO-639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes)形式の文字列です。 |
 | 生年月日 | 文字列形式のユーザーの生年月日（例：1980-12-21）。 |
-| タイムゾーン | タイムゾーン名は、[IANA Time Zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)データベースから取得します（例：'America/New_York' または 'Eastern Time (US & Canada)'）。 |
+| タイムゾーン | [IANA タイムゾーンデータベース](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)からのタイムゾーン名 (たとえば、「America/New_York」または「東部標準時 (アメリカおよびカナダ)」)。 |
 | Facebook | `id`（文字列）、`likes`（文字列の配列）、`num_friends`（整数）のいずれかを含むハッシュ。 |
-| ツイッター | id（整数）、`screen_name`（文字列、X（旧Twitter）ハンドル）、`followers_count`（整数）、`friends_count`（整数）、`statuses_count`（整数）を含むハッシュ。 |
+| Twitter | `screen_name` (整数)、`followers_count` (文字列、X (旧 Twitter) ハンドル)、`friends_count` (整数)、`statuses_count` (整数) のいずれかを含むハッシュ。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/amperity.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/amperity.md
index 7d347d9f5ca..b492e3d8556 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/amperity.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/amperity.md
@@ -10,37 +10,37 @@ search_tag: Partner
 
 # アンペア
 
-> [Amperityは](https://amperity.com/)、包括的な企業向け顧客データプラットフォームであり、ブランドが顧客を知り、戦略的な意思決定を行い、消費者により良いサービスを提供するために常に正しい行動をとることを支援する。Amperityは、データ管理の統合、分析、洞察、活性化にわたるインテリジェントな機能を提供する。
+> [Amperity](https://amperity.com/) は、包括的な企業向け顧客データプラットフォームであり、ブランドが顧客を理解し、戦略的な意思決定を行い、消費者により良いサービスを提供するために常に適切な措置を取れるよう支援します。Amperity は、データ管理の統合、分析、インサイト、およびアクティベーションにおけるインテリジェントな機能を提供します。
 
 {% multi_lang_include video.html id="06G0lxaSjgk" align="right" %}
 
-BrazeとAmperityの統合は、2つのプラットフォーム間で顧客の統一されたビューを提供する。この統合により、以下のことが可能になる：
-- **顧客プロファイルを同期する**：ユーザーデータとカスタム属性をAmperityからBrazeにマッピングする。 
-- **オーディエンスを作成し、送信する**：アクティブな顧客のリストと関連するカスタム属性をBrazeに返すセグメントを構築し、Brazeに送信する。
-- **データの更新を管理する**：カスタム属性の更新をBrazeに送信する頻度を制御する。
-- **データを統一する**：Amperityがサポートする様々なプラットフォームとBrazeでデータを統合する。
+Braze と Amperity の統合により、2つのプラットフォームにわたる顧客の統合ビューが提供されます。この統合により、以下のことが可能になる：
+- **顧客プロファイルを同期する**:ユーザーデータとカスタム属性をAmperityからBrazeにマッピングする。 
+- **オーディエンスを作成、送信する**:アクティブな顧客とこれらの顧客に関連付けられているカスタム属性のリストを Braze に返すセグメントを作成して、Braze に送信します。
+- **データの更新を管理する**:カスタム属性の更新をBrazeに送信する頻度を制御する。
+- **データを統合する**:Amperityがサポートする様々なプラットフォームとBrazeでデータを統合する。
 - **BrazeのデータをAmazon S3に同期する**：Braze Currentsを使用して、Brazeキャンペーンからのエンゲージメントデータを統合し、Apache AvroフォーマットでAmazon S3にデータを同期できる。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| アンペリティ口座 | このパートナーシップを利用するには、[Amperityアカウントが](https://amperity.com/request-a-demo)必要である。 |
-| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br> これは、Brazeダッシュボードの**Developer Console**>**Rest API Key**>**Create New API Keyで**作成できる。 |
-| ブレイズインスタンス | あなたのBrazeインスタンスは、あなたのBrazeオンボーディングマネージャーから取得するか、[API概要ページで]({{site.baseurl}}/api/basics#endpoints)見つけることができる。 |
+| Amperity アカウント | このパートナーシップを活用するには、[Amperity アカウント](https://amperity.com/request-a-demo)が必要です。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br> これは Braze ダッシュボードの \[**開発者コンソール**] > \[**REST API キー**] > \[**新しい API キーを作成**] で作成できます。 |
+| ブレイズインスタンス | Braze インスタンスは Braze オンボーディングマネージャーから入手できます。また、[API 概要ページ]({{site.baseurl}}/api/basics#endpoints)でも確認できます。 |
 | Braze RESTエンドポイント | あなたのBrazeエンドポイントURL。エンドポイントはBrazeインスタンスに依存する。 |
-| 電流コネクタ（オプション） | S3カレントのコネクターだ。 |
+| Currents コネクター (オプション) | S3 Currents コネクター。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## データマッピング
 
-標準属性とカスタム属性の両方をAmperityからBrazeに送信できるため、Amperityを通じて様々なソースからのデータでBrazeの顧客プロファイルを充実させることができる。送信できる特定の属性は、AmperityシステムのデータとBrazeで設定した属性によって異なる。
+標準属性とカスタム属性の両方を Amperity から Braze に送信できます。これにより、Amperity からさまざまなソースのデータを使用して、Braze の顧客プロファイルを強化できます。送信できる属性は、Amperity システムのデータと、Braze で設定した属性によって異なります。
 
 これらの属性については、以下をお読みいただきたい。
 
 ### 標準属性 
 
-[プロフィール属性は]({{site.baseurl}}/api/objects_filters/user_attributes_object#braze-user-profile-fields)、あなたの顧客がどのような人であるかを説明する。それらはしばしば、顧客のアイデンティティと関連付けられる：
+[プロファイル属性]({{site.baseurl}}/api/objects_filters/user_attributes_object#braze-user-profile-fields)は、顧客が誰であるかを示します。これらは多くの場合、次のような顧客の身元情報に関連付けられています。
 - 名前
 - 生年月日
 - メールアドレス
@@ -48,17 +48,17 @@ BrazeとAmperityの統合は、2つのプラットフォーム間で顧客の統
 
 ### カスタム属性 
 
-Brazeの[カスタム属性は]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/)、あなたのブランドによって決定されるフィールドである。Brazeにすでに存在するカスタム属性をAmperityで管理したい場合は、Amperityから送信される出力を、Brazeワークスペースにすでにある名前に合わせる。これには以下のようなものが含まれる：
+Braze の[カスタム属性]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/)は、ブランドが決定するフィールドです。Brazeにすでに存在するカスタム属性をAmperityで管理したい場合は、Amperityから送信される出力を、Brazeワークスペースにすでにある名前に合わせる。これには次のものが含まれます。
 - 購入履歴
-- ロイヤリティ・ステータス
-- バリュー層
+- ロイヤルティステータス
+- 価値階層
 - 最近のエンゲージメント・データ
 
 AmperityからBrazeに送信されるカスタム属性の名前を確認する。Amperityは、一致する名前がないときはいつでもカスタム属性を追加する。
 
-カスタム属性は、Braze内で一致する`external_id` または`braze_id` を持つユーザーに対してのみ更新される。
+Braze 内で一致する `external_id` または`braze_id` を持つユーザーのカスタム属性のみが更新されます。
 
-### 観客数
+### Amperity オーディエンス
 
 AmperityからBrazeに同期されたオーディエンスは、カスタム属性としてユーザープロファイルに記録される。これらは、Brazeでそれらのユーザーをターゲットにするために使用できる。
 
@@ -66,77 +66,77 @@ AmperityからBrazeに同期されたオーディエンスは、カスタム属
 
 ![l12m_frequency" や "l12m_monetary" などのカスタム属性のドロップダウンリスト。][2]{: style="max-width:40%;"}
 
-### データタイプ
+### データ型
 
 サポートされているデータタイプは以下の通りである：
 - ブール値
 - 日付
-- 日付
-- 10進数
+- 日時
+- 小数
 - フロート
 - 整数
 - String
-- Varchar
+- 可変長文字列
 
-使用されるデータ型は属性の性質によって異なる。例えば、Eメールアドレスは文字列、顧客の年齢は整数かもしれない。
+使用されるデータ型は属性の性質によって異なる。たとえば、メールアドレスは文字列で、顧客の年齢は整数です。
 
 ### 属性の重複
 
-デフォルトのユーザープロファイルフィールドと重複するカスタム属性の送信は避ける。例えば、生年月日は、Brazeの標準属性と一致するように、"dob "という名前のユーザープロファイルのフィールドとしてBrazeに送られるべきである。birthday"、"Birthdate"、またはその他の文字列として送信された場合、カスタム属性が作成され、"dob "フィールドの値は更新されない。
+デフォルトのユーザープロファイルフィールドと重複するカスタム属性の送信は避ける。たとえば、Braze の標準属性に一致するように、誕生日を「dob」という名前のユーザープロファイルフィールドとして Braze に送信する必要があるとします。birthday"、"Birthdate"、またはその他の文字列として送信された場合、カスタム属性が作成され、"dob "フィールドの値は更新されない。
 
 ### データポイント
 
-Amperityは、Brazeへのシンクの間に何が変更されたのか、全体的なセンドのステータスを追跡している。Amperityは、前回の同期以降に変更されたリストメンバーシップとその他の選択された属性のみをBrazeに送信する。  
+Amperity は、Braze との同期間に行われた変更と、送信のステータスを追跡します。Amperityは、前回の同期以降に変更されたリストメンバーシップとその他の選択された属性のみをBrazeに送信する。  
 
 ## 統合
 
 ### ステップ1:Brazeの設定の詳細をキャプチャする
 
-1. Brazeワークスペース用のBraze REST APIキーを作成し、**User Dataの**下に`users.track` 。`users.track` エンドポイントは、Amperityのオーディエンスをカスタム属性としてBrazeに同期する。
+1. \[**User Data**] で、`users.track` 権限を持つ Braze ワークスペースの Braze REST APIキーを作成します。`users.track` エンドポイントは、Amperity オーディエンスをカスタム属性として Braze に同期します。
 2. Brazeインスタンスの[REST APIエンドポイントを]({{site.baseurl}}/api/basics#endpoints)決定する。例えば、BrazeのURLが`https://dashboard-03.braze.com` 、REST APIのエンドポイントが`https://rest.iad-03.braze.com` 、インスタンスが "US-03 "の場合。
-3. AmperityからBrazeに送信される[ユーザープロファイルフィールドと]({{site.baseurl}}/api/objects_filters/user_attributes_object#braze-user-profile-fields) [カスタム属性の]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/)リストを決定する。
+3. Amperity から Braze に送信できる一連の[ユーザープロファイルフィールド]({{site.baseurl}}/api/objects_filters/user_attributes_object#braze-user-profile-fields)と[カスタム属性]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/)を決定します。
 
-### ステップ2:Brazeをデスティネーション-DataGrid Operatorとして設定する。
+### ステップ2:Braze を宛先として設定する - DataGrid オペレーター
 
-#### ステップ 2a: 顧客プロファイル・テーブルを構築する
+#### ステップ 2a: 顧客プロファイルテーブルを作成する
 
-AmperityのCustomer 360データベース内に "Braze Customer Attributes "という新しいテーブルを作成する。このテーブルには、ブランドがAmperityから管理したいBrazeのすべての属性（Brazeが要求するデフォルトのユーザープロファイルのフィールドとカスタム属性の両方を含む）を含める必要がある。[Amperityのドキュメントに](https://docs.amperity.com/datagrid/destination_braze.html#customer-profiles-table)示されているように、SQLを使ってこのテーブルの構造を定義する。
+Amperity の Customer 360 データベース内に、「Braze Customer Attributes」という名前の新しいテーブルを作成します。このテーブルには、ブランドが Amperity で管理するすべての Braze 属性が含まれている必要があります。これには、Braze が必要とするデフォルトのユーザープロファイルフィールドとカスタム属性の両方が含まれます。[Amperity ドキュメント](https://docs.amperity.com/datagrid/destination_braze.html#customer-profiles-table)に示されているように、SQL を使用してこのテーブルの構造を定義します。
 
 #### ステップ 2b: テーブルに名前を付け、検証し、保存する
 
 テーブル名を "Braze Customer Attributes "とし、保存する。テーブルが**セグメントエディター**およびキャンペーン内の**属性編集**エディターにアクセス可能であることを確認する。
 
-#### ステップ 2c: ブラゼを目的地に追加する
+#### ステップ 2c: Braze を宛先として追加する
 
-Amperityプラットフォームで、**Destinations**タブに移動する。新しい目的地を追加するオプションを探す。利用可能なオプションから、**Brazeを**選択する。
+Amperity プラットフォームで \[**Destinations**] タブに移動します。新しい目的地を追加するオプションを探す。利用可能なオプションから \[**Braze**] を選択します。
 
-![New Destinationセクションの名前は "Braze API"、説明は "Send audience attributes to Braze."、プラグインは "Braze"。][3]{: style="max-width:60%;"}
+![名前が「Braze API」、説明が「Send audience attributes to Braze」、プラグインが「Braze」である「New Destination」セクション。][3]{: style="max-width:60%;"}
 
-#### ステップ 2d: デスティネーションの詳細を設定する
+#### ステップ 2d: 宛先の詳細を設定する
 
-**Brazeの**設定で、[Amperityのドキュメントに](https://docs.amperity.com/datagrid/destination_braze.html#add-destination)示されているように、Brazeの認証情報とデスティネーション設定を提供する。最後のステップで収集した構成の詳細を入力し、Braze識別子を定義する。マッチング可能な識別子は以下の通りである：
+[Amperityのドキュメント](https://docs.amperity.com/datagrid/destination_braze.html#add-destination)に示されているように、\[**Braze settings**] で Braze の認証情報と宛先設定を指定します。最後のステップで収集した構成の詳細を入力し、Braze識別子を定義する。マッチング可能な識別子は以下の通りである：
 - `braze_id`:自動的に割り当てられるBrazeの識別子で、Brazeで作成されたときに特定のユーザーに関連付けられ、変更できない。
 - `external_id`:顧客が割り当てた識別子で、通常はUUIDである。 
 
-![インスタンスが "US-03"、ユーザー識別子が "external_id"、セグメント名が空白、S3バケットが "amperity-training-abc123"、S3フォルダが "braze-attributes "のBraze Settingsセクション。][4]{: style="max-width:60%;"}
+![インスタンスが「US-03」、ユーザー ID が「external_id」、セグメント名が空白、S3 バケットが「amperity-training-abc123」、S3 フォルダーが「braze-attributes」である「Braze Settings」セクション。][4]{: style="max-width:60%;"}
 
-#### ステップ2e：データ・テンプレートを追加する
+#### ステップ2e:データ・テンプレートを追加する
 
-**Destinations**タブで、Brazeデスティネーションのメニューを開き、**Add data templateを**選択する。テンプレートの名前と説明（例えば、"Braze "と "Send custom attributes to Braze"）を入力し、ビジネスユーザーのアクセスを確認し、すべての構成設定をチェックする。 
+\[**Destinations**] タブで Braze 宛先のメニューを開き、\[**Add data template**] を選択します。テンプレートの名前と説明（例えば、"Braze "と "Send custom attributes to Braze"）を入力し、ビジネスユーザーのアクセスを確認し、すべての構成設定をチェックする。 
 
 必要な設定がデスティネーションの一部として構成されていない場合は、データテンプレートの一部として構成する。データ・テンプレートを保存する。
 
-![Data Template Nameセクションに "Braze Audience Attributes "という名前と "Send audience attributes to Braze "という説明がある。][5]{: style="max-width:60%;"}
+![名前が「Braze Audience Attributes」で説明が「Send audience attributes to Braze」である「Data Template Name」セクション。][5]{: style="max-width:60%;"}
 
-#### ステップ2f：設定を保存する 
+#### ステップ2f:設定を保存する 
 
-必要事項を記入したら、設定を保存する。Brazeがデスティネーションとして設定されたので、Amp360とAmpIQのユーザーはBrazeにデータを同期できる。
+必要な情報を入力したら、この設定を保存します。Braze が宛先として設定されたので、Amp360 と AmpIQ のユーザーはデータを Braze に同期できます。
 
 ### ステップ3:データをBrazeに同期させる
 
-AmperityのテナントでBrazeが有効になっていることを確認する。そうでない場合は、DataGridオペレーターまたはAmperityの担当者に問い合わせること。
+AmperityのテナントでBrazeが有効になっていることを確認する。有効になっていない場合は、DataGrid オペレーターまたは Amperity の担当者に支援を依頼してください。
 
-次に、貴社に該当するAmp360またはAmpIQの同期手順に従う。
+次に、該当する Amp360 または AmpIQ の同期手順に従います。
 
 #### 同期オプション 1：Amp360経由でBrazeにクエリー結果を送信する
 
@@ -150,33 +150,33 @@ Amperityのクエリー機能に移動し、目的の顧客データセットを
 
 1. **Orchestration**セクションに行き、新しいオーケストレーションを追加するオプションをクリックする。 
 2. オーケストレーションが何をすべきかを指定する。これには通常、実行されるべきSQLクエリと、その結果の送信先を指定することが含まれる。この場合、アクティブな顧客のリストを生成するために作成したSQLクエリーを選択し、結果の送信先としてBrazeを指定する。
-3. オーケストレーションをいつ、どのくらいの頻度で実行するかを定義する。例えば、毎日特定の時間にオーケストレーションを実行する。
+3. オーケストレーションをいつ、どのくらいの頻度で実行するかを定義する。たとえば、毎日特定の時間にオーケストレーションを実行できます。
 4. オーケストレーションを好みに設定したら保存する。Amperityのオーケストレーションリストに追加される。
 5. オーケストレーションをテストして、期待通りに動作することを確認する。手動でオーケストレーションをトリガーし、Brazeで結果をチェックすることでこれを行うことができる。
 
 ##### ステップ3:オーケストレーションを実行する 
 
-オーケストレーションを実行してクエリを実行し、結果をBrazeに送信する。これは手動で行うことも、オーケストレーション設定で設定したスケジュールで行うこともできる。
+オーケストレーションを実行してクエリを実行し、結果をBrazeに送信する。これは手動で行うことも、オーケストレーション設定で設定したスケジュールで行うこともできます。
 
-#### 同期オプション 2：AmpIQ経由でブレイズにオーディエンスを送る
+#### 同期オプション 2：AmpIQ を介して Braze にオーディエンスを送信する
 
-AmpIQユーザーは、SQL以外のインターフェイスを使ってAmperityでセグメントを作成し、Brazeのような下流のデスティネーションに同期させることができる。ユーザーは送信先を選択し、各送信先に送信する属性のリストを設定することができる。
+AmpIQユーザーは、SQL以外のインターフェイスを使ってAmperityでセグメントを作成し、Brazeのような下流のデスティネーションに同期させることができる。ユーザーは宛先を選択し、各宛先に送信する属性のリストを設定できます。
 
 ##### ステップ1:Amperityでセグメントを作成する 
 
-Amperityで顧客のリストを返すセグメントを作成する。このセグメントは、Brazeで更新したいカスタム属性に関連付けられていなければならない。
+Amperityで顧客のリストを返すセグメントを作成する。このセグメントは、Braze で更新するカスタム属性に関連付けられている必要があります。
 
 {% alert note %}
-Brazeに送信したいさまざまなセグメントタイプの例については、Amperityのドキュメントをチェックしてほしい。
+Amperity のドキュメントで、Braze に送信できるさまざまなセグメントタイプの例を確認してください。
 {% endalert %}
 
 ##### ステップ2:Amperityでキャンペーンを構築する
 
 1. **キャンペーン・**セクションに行き、新しいキャンペーンを作成するオプションをクリックする。
 2. 特に複数のキャンペーンを行っている場合は、後でキャンペーンを識別するのに役立つ、説明的でユニークな名前を付ける。
-3. このキャンペーンでターゲットにしたい顧客セグメントを選択する。これは先ほど作成したセグメントでなければならない。<br>![ターゲティングから除外するセグメントのドロップダウンフィールド。][6]{: style="max-width:50%;"}<br><br>
-4. キャンペーンの一部として送信したいデータを選択する。これには、さまざまな顧客属性が含まれる。![キャンペーン属性の編集]モーダルでは、宛先と顧客属性を選択できる。 ][7]{: style="max-width:90%;"}<br><br>
-5. キャンペーンデータの送信先として**Brazeを**選択する。
+3. このキャンペーンでターゲットにする顧客のセグメントを選択します。これは先ほど作成したセグメントです。<br>![ターゲティングから除外するセグメントのドロップダウンフィールド。][6]{: style="max-width:50%;"}<br><br>
+4. キャンペーンの一部として送信したいデータを選択する。これにはさまざまな顧客属性が含まれる可能性があります。![「Edit Campaign Attributes」モーダルでは、宛先とカスタマー属性を選択できる。][7]{: style="max-width:90%;"}<br><br>
+5. キャンペーンデータの送信先として \[**Braze**] を選択します。
 6. いつ、どれくらいの頻度でキャンペーンを実施するかを選択する。これは1回限りのイベントでも、定期的なスケジュールでも構わない。
 7. キャンペーンを保存してテストを実行し、期待通りに機能することを確認する。
 
@@ -185,7 +185,7 @@ Brazeに送信したいさまざまなセグメントタイプの例について
 Brazeにセグメントを送信するためにキャンペーンを実行する。これは手動で行うことも、キャンペーン設定で設定したスケジュールに基づいて行うこともできる。
 
 
-### ブレージング電流でアンペリティを使う
+### Amperity と Braze Currents を組み合わせて使用する
 Braze CurrentsのデータをAmperityに送信する：
 1. Amazon S3バケットにデータを送信するために[Braze Currentをセットアップ]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/setting_up_currents/)する。
 2. [そのAmazon S3バケットからApache Avroファイルを読み込む](https://docs.amperity.com/datagrid/source_amazon_s3.html)ようにAmperityを設定する。
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/blueconic.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/blueconic.md
index ba291740001..e7c421d7bf0 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/blueconic.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/blueconic.md
@@ -1,16 +1,16 @@
 ---
-nav_title: ブルーコニック
-article_title: ブルーコニック
-description: "この参考記事では、Brazeとピュアプレイの大手顧客データプラットフォームであるBlueConicのパートナーシップについて概説しており、永続的な個々のプロファイル間でデータを統一し、Amazon Web ServicesのS3サーバー経由でインポート目標のために2つのシステム間で同期することができる。"
+nav_title: BlueConic
+article_title: BlueConic
+description: "このリファレンス記事では、Braze と BlueConic のパートナーシップについて説明します。BlueConic は、業界をリードするピュアプレイ顧客データプラットフォームであり、永続的な個々のプロファイル間でデータを統合し、Amazon Web Services S3 サーバーを介してインポート目標のために2つのシステム間でデータを同期することができます。"
 alias: /partners/blueconic/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# ブルーコニック
+# BlueConic
 
-> [BlueConicは][1]、ピュアプレイ顧客データプラットフォームのリーディングカンパニーであり、企業のファーストパーティデータを異種システムから解放し、いつでもどこでも必要なときにアクセスできるようにすることで、顧客との関係を変革し、ビジネスの成長を促進する。 
+> [BlueConic][1] は業界をリードするピュアプレイ顧客データプラットフォームであり、異種システムから企業のファーストパーティデータを解放し、顧客との関係を変えビジネスの成長を促進するために必要であれば、いつでもどこからでもこのデータにアクセスできるようにします。 
 
 BrazeとBlueConicの統合により、ユーザーは永続的な個々のプロファイル間でデータを統一し、Amazon Web ServicesのS3サーバーを経由してインポート目標のために2つのシステム間で同期することができる。想定される目標には、成長に焦点を当てた取り組み、顧客ライフサイクルのオーケストレーション、モデリングと分析、デジタル製品と体験、視聴者ベースの収益化などが含まれる。この統合は、スケジュールされたバッチインポートとエクスポートの両方をサポートしている。 
 
@@ -22,21 +22,21 @@ BrazeとBlueConicの統合により、ユーザーは永続的な個々のプロ
 
 | 必要条件 | 説明 |
 | --- | --- |
-| ブルーコニックのアカウント | このパートナーシップを利用するには、[ブルーコニックのアカウントが][1]必要である。プラグインにアクセスするには、BlueConicアカウント内で[接続を表示および編集][4]するためのアクセス権が必要である。 |
-| Braze REST API キー | `users.track` 、`users.export.segment` 、`campaigns.list` 、`campaigns.details` 、`segments.lists` 、`segments.details` のパーミッションを持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに][2]依存する。 |
+| BlueConic アカウント | このパートナーシップを活用するには、[BlueConic アカウント][1]が必要です。プラグインにアクセスするには、BlueConicアカウント内で[接続を表示および編集][4]するためのアクセス権が必要である。 |
+| Braze REST API キー | `users.track`、`users.export.segment`、`campaigns.list`、`campaigns.details`、`segments.lists`、`segments.details` の権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
+| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL][2] に応じて異なります。 |
 | S3認証 | データのエクスポートとインポートには、Amazon Web Services（S3）サーバーへのアクセスが必要だ。 |
-| アクセスキーID<br>秘密のアクセス・キー | アクセスキーIDとシークレットアクセスキーによって、インポートやエクスポートを行うS3サーバーを認証することができる。 |
-| AWSバケット | プラグイン内でS3に接続する必要がある。認証後、利用可能なバケツがドロップダウンメニューに表示される。ここには、インポートまたはエクスポートされるファイルが保存される。 |
+| アクセスキーID<br>シークレットアクセスキー | アクセスキー ID とシークレットアクセスキーを使用して、インポートとエクスポートのために S3 サーバーを認証できます。 |
+| AWSバケット | プラグイン内で S3 に接続する必要があります。認証後に、利用可能なバケットがドロップダウンメニューに表示されます。ここには、インポートまたはエクスポートされるファイルが保存される。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 ## 統合
 
-### ステップ1:ブレイズコネクションを作る
+### ステップ1:Braze 接続を作成する
 
-BlueConicのナビゲーション・バーで**「Connections」を**選択し、「**Add Connection」を**選択する。表示されたプロンプトで**Brazeを**検索し、**Braze connectionを**選択する。 
+BlueConic のナビゲーションバーで \[**Connections**] を選択し、次に \[**Add Connection**] を選択します。表示されるプロンプトで、**Braze** を検索し、\[**Braze connection**] を選択します。 
 
-グレーのシェブロンアイコンをクリックして、接続で使用可能なメタデータフィールドを展開または折りたたむ。これらのフィールドでは、この接続をお気に入りに登録したり、接続に名前をつけたり、ラベルを追加したり、説明を含めたり、接続が[実行されたり実行されなかったりした][5]場合にEメールで通知を受け取るかどうかを選択したりすることができる。 
+グレーの山形記号アイコンをクリックして、接続の使用可能なメタデータフィールドを展開または折りたたみます。これらのフィールドでは、お気に入りへのこの接続の追加、接続の名前の指定、ラベルの追加、説明の追加、および接続が[実行されているか、実行できていないか][5]に関するメール通知を受信するかどうかの選択を行うことができます。 
 
 設定を保存する。
 
@@ -44,37 +44,37 @@ BlueConicのナビゲーション・バーで**「Connections」を**選択し
 
 BlueConicとBraze間の接続を設定するには、接続を認証するためにBrazeのアカウント認証情報とAmazon Web Services（S3）のアカウント情報を追加する必要がある。 
 
-1. BlueConicでは、左パネルの**Setup**セクションで**Set up and runを**選択する。<br><br>
+1. BlueConic の左パネルの \[**Set up**] セクションで \[**Set up and run**] を選択します。<br><br>
 2. 開いたBraze認証ページで、Braze REST APIエンドポイントとBraze APIキーを入力する。<br>
 ![]({% image_buster /assets/img/blueconic/braze2.png %}){: style="max-width:80%;"}<br><br>
-3. S3 setup and authenticationセクションで、これらの認証情報を入力する：Amazon Web Services（S3）のアクセスキーID、シークレットアクセスキー、S3バケット。これらは、BrazeとAmazon S3の統合を設定するときに設定した[のと同じ認証情報]({{site.baseurl}}/partners/data_and_infrastructure_agility/cloud_storage/amazon_s3/)である必要がある。設定を保存する。<br>![]({% image_buster /assets/img/blueconic/braze3.png %}){: style="max-width:80%;"}
+3. S3 の設定と認証のセクションで、次の認証情報を入力します。Amazon Web Services（S3）のアクセスキーID、シークレットアクセスキー、S3バケット。これらは、BrazeとAmazon S3の統合を設定するときに設定した[のと同じ認証情報]({{site.baseurl}}/partners/data_and_infrastructure_agility/cloud_storage/amazon_s3/)である必要がある。設定を保存する。<br>![]({% image_buster /assets/img/blueconic/braze3.png %}){: style="max-width:80%;"}
 
 ### ステップ 3:インポートゴールまたはエクスポートゴールを作成する（インポートマッピング）
 
 認証が完了したら、少なくとも1つのインポートまたはエクスポートゴールを作成し、接続をオンにし、接続をスケジュールまたは実行する必要がある。
 
 {% tabs %}
-{% tab 輸入 %}
+{% tab インポート %}
 
-1. 左のパネルで**Import data into BlueConicを**選択し、Brazeのデータ設定ページを開く。<br><br>
-2. Brazeのデータの場所を選択する。ここで、Brazeのオーディエンスを選択することで、インポートするデータの場所をBlueConicに伝えることができる。<br>![BlueConic Brazeの視聴者を「BlueConicテストユーザー」に設定した。]({% image_buster /assets/img/blueconic/braze4.png %}){: style="max-width:80%;"}<br><br>
-3. 次に、BrazeとBlueConicの間で識別子をマッピングする。<br>![Brazeのフィールド「外部ID」は、BlueConicの「Braze外部ID」フィールドにマッピングするように設定されている。]({% image_buster /assets/img/blueconic/braze5.png %}){: style="max-width:80%;"}<br><br> 2つのシステム間で顧客データをリンクさせるには、1つ以上の顧客識別子を入力する。<br>既存のBlueConicプロファイルに一致しないデータについて、BlueConicが新しいプロファイルを作成することを許可するには、**「作成を許可...」**チェックボックスを使用する。<br><br>
+1. 左パネルで \[**Import data into BlueConic**] を選択し、Braze データ設定ページを開きます。<br><br>
+2. Brazeのデータの場所を選択する。ここで、Brazeのオーディエンスを選択することで、インポートするデータの場所をBlueConicに伝えることができる。<br>![「Blue Conic Test Users」に設定されている BlueConic Braze オーディエンス。]({% image_buster /assets/img/blueconic/braze4.png %}){: style="max-width:80%;"}<br><br>
+3. 次に、BrazeとBlueConicの間で識別子をマッピングする。<br>![Braze のフィールド「external ID」が、BlueConic の「Braze external ID」フィールドにマッピングするように設定されている。]({% image_buster /assets/img/blueconic/braze5.png %}){: style="max-width:80%;"}<br><br> 2つのシステム間で顧客データをリンクさせるには、1つ以上の顧客識別子を入力します。<br>既存のBlueConicプロファイルに一致しないデータについて、BlueConicが新しいプロファイルを作成することを許可するには、**「作成を許可...」**チェックボックスを使用する。<br><br>
 4. 次に、エクスポートするBlueConicのデータフィールドをBrazeのフィールドに合わせる。ドロップダウンフィールドを使用して、左側のBlueConicプロファイル識別子またはプロファイルプロパティのいずれかを選択し、対応するBrazeプロファイル識別子を選択する。次に、ドロップダウンメニューを使用して、インポートしたコンテンツを既存の値に追加する方法を指定する：追加、合計、プロファイル・プロパティが空の場合のみ設定、またはクリアに設定（Brazeフィールドが空の場合）。<br>![]({% image_buster /assets/img/blueconic/braze6.png %}){: style="max-width:80%;"}<br><br>**Add Mapping**ボタンを使って、必要に応じてマッピング行を追加作成する。**Add remaining fields**オプションで複数のマッピング行を追加できる。BlueConicは残りのBrazeフィールドを検出し、BlueConicプロファイル・プロパティと照合する。インポートのマージ戦略（set、add、sum、set if empty、clear）を設定し、BlueConicプロファイル・プロパティの名前にカスタム接頭辞を指定できる。<br><br>
 5. 最後に、**Run the connectionを**選択して接続を開始する。接続のスケジューリングと実行については、[BlueConicを](https://support.blueconic.com/hc/en-us/articles/205957522-Scheduling-Connections)ご覧いただきたい。
 {% endtab %}
-{% tab 輸出 %}
+{% tab エクスポート %}
 
-1. 左のパネルで**Export data to Brazeを**選択し、BlueConicからBrazeへのデータエクスポートを設定する。<br><br>
-2. エクスポートするBlueConicセグメントを選択する。このセグメントで、Brazeの識別子が一致するプロファイルだけがエクスポートされる。<br>![ブルーコニックの2万プロファイルのセグメント。]({% image_buster /assets/img/blueconic/braze8.png %}){: style="max-width:80%;"}<br><br>
-3. 次に、BlueConicプロファイルとBrazeフィールド間の識別子をリンクさせる。オプションで、一致するレコードがない場合、BlueConicに新しいレコードを作成させることもできる。<br>![Brazeのフィールド「外部ID」は、BlueConicの「Braze外部ID」フィールドにマッピングするように設定されている。]({% image_buster /assets/img/blueconic/braze7.png %}){: style="max-width:80%;"}<br><br>
-4. 次に、エクスポートするBlueConicのデータフィールドをBrazeのフィールドに合わせる。BlueConicのアイコンからドロップダウンメニューを使って、エクスポートしたい[情報の](https://support.blueconic.com/hc/en-us/articles/4405501836955-Braze-Connection#creating-export-goals)種類を選択する。利用可能な情報には、プロファイルプロパティ、BlueConicプロファイル識別子、関連セグメント、閲覧されたすべてのインタラクション、パーミッションレベル、静的テキスト値が含まれる。<br>![]({% image_buster /assets/img/blueconic/braze6.png %}){: style="max-width:80%;"}<br><br>
-5. 最後に、**Run the connectionを**クリックして接続を開始する。接続のスケジューリングと実行については、[BlueConicを](https://support.blueconic.com/hc/en-us/articles/205957522-Scheduling-Connections)ご覧いただきたい。
+1. 左パネルで \[**Export data to Braze**] を選択し、BlueConic から Braze へのデータエクスポートを設定します。<br><br>
+2. エクスポートするBlueConicセグメントを選択する。このセグメントで、Braze で一致する識別子を持つプロファイルのみがエクスポートされます。<br>![2万件のプロファイルからなる BlueConic セグメント。]({% image_buster /assets/img/blueconic/braze8.png %}){: style="max-width:80%;"}<br><br>
+3. 次に、BlueConicプロファイルとBrazeフィールド間の識別子をリンクさせる。オプションで、一致するレコードがない場合、BlueConicに新しいレコードを作成させることもできる。<br>![Braze のフィールド「external ID」が、BlueConic の「Braze external ID」フィールドにマッピングするように設定されている。]({% image_buster /assets/img/blueconic/braze7.png %}){: style="max-width:80%;"}<br><br>
+4. 次に、エクスポートするBlueConicのデータフィールドをBrazeのフィールドに合わせる。BlueConic アイコンのドロップダウンメニューを使用して、エクスポートする[情報](https://support.blueconic.com/hc/en-us/articles/4405501836955-Braze-Connection#creating-export-goals)のタイプを選択します。利用可能な情報には、プロファイルプロパティ、BlueConicプロファイル識別子、関連セグメント、閲覧されたすべてのインタラクション、パーミッションレベル、静的テキスト値が含まれる。<br>![]({% image_buster /assets/img/blueconic/braze6.png %}){: style="max-width:80%;"}<br><br>
+5. 最後に \[**Run the connection**] をクリックして接続を開始します。接続のスケジューリングと実行については、[BlueConicを](https://support.blueconic.com/hc/en-us/articles/205957522-Scheduling-Connections)ご覧いただきたい。
 {% endtab %}
 {% endtabs %}
 
 ## ステップ4:接続をオンに切り替える
 
-Braze接続のタイトルの横にあるトグルを使って、接続のオンとオフを切り替える。スケジュールされた時間帯に実行するには、接続がオンになっていなければならない。 
+Braze接続のタイトルの横にあるトグルを使って、接続のオンとオフを切り替える。スケジュールされた時間に実行するには、接続がオンになっている必要があります。 
 
 [1]: https://www.blueconic.com/
 [2]: https://portal.aws.amazon.com/billing/signup#/start
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights.md
index 63cc90429a3..965429d1e6b 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights.md
@@ -1,23 +1,23 @@
 ---
-nav_title: Dynamics 365カスタマーインサイト
-article_title: Dynamics 365カスタマーインサイト
-description: "この参考記事では、BrazeとDynamics 365 Customer Insights（主要な企業顧客データプラットフォーム）のパートナーシップについて概説している。"
+nav_title: Dynamics 365 Customer Insights
+article_title: Dynamics 365 Customer Insights
+description: "このリファレンス記事では、Braze と Dynamics 365 Customer Insights のパートナーシップについて説明します。Dynamics 365 Customer Insights は業界をリードするエンタープライズ顧客データプラットフォームであり、顧客セグメントをキャンペーンまたはキャンバスで使用するために Braze にエクスポートできます。"
 alias: /partners/dynamics_365_customer_insights/
 page_type: partner
 search_tag: Partner
 ---
 
-# Dynamics 365カスタマーインサイト
+# Dynamics 365 Customer Insights
  
 > [Dynamics 365 Customer Insightsは](https://dynamics.microsoft.com/en-gb/ai/customer-insights/)、顧客の360度ビューでパーソナライズされたカスタマーエクスペリエンスを提供する、エンタープライズ向けの主要な顧客データプラットフォームである。
 
-BrazeとDynamics 365 Customer Insightsの統合により、キャンペーンやCanvasesで使用する顧客セグメントをBrazeにエクスポートできる。
+Braze と Dynamics 365 Customer Insights の統合により、顧客セグメントを Braze にエクスポートしてキャンペーンやキャンバスで使用できるようになります。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| Dynamics 365 Customer Insightsアカウント | このパートナーシップを利用するには、[Dynamics 365 Customer Insights](https://dynamics.microsoft.com/en-gb/ai/customer-insights/)アカウントが必要である。必要なプラグインにアクセスするには、Dynamics 365 Customer Insightsアカウント内で接続を表示および編集するための管理者としてのアクセス権が必要である。 |
+| Dynamics 365 Customer Insights アカウント | このパートナーシップを活用するには、[Dynamics 365 Customer Insights](https://dynamics.microsoft.com/en-gb/ai/customer-insights/) アカウントが必要です。必要なプラグインにアクセスするために Dynamics 365 Customer Insights アカウント内で接続を表示および編集するには、管理者としてアクセスする必要があります。 |
 | Braze REST API キー | すべての権限が付与されたBraze REST APIキーが必要である。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -25,36 +25,36 @@ BrazeとDynamics 365 Customer Insightsの統合により、キャンペーンや
 
 ### ステップ1:Brazeの接続を設定する
 
-Customer Insightsで、**Admin > Connectionsに**移動する。次に、**Add connectionsを**選択し、**Brazeを**選択して接続を設定する。 
+Customer Insights で **\[Admin] > \[Connections]** に移動します。次に、\[**Add connections**] を選択し、\[**Braze**] を選択して接続を設定します。 
 
 1. **表示名]**フィールドで、接続にわかりやすい名前を付ける。 
-2. この接続を使用できる人を選択する。このフィールドを空白にすると、デフォルトはAdministratorsになる。詳細については、[投稿者がエクスポートに接続を使用できるようにするを](https://docs.microsoft.com/en-us/dynamics365/customer-insights/connections#allow-contributors-to-use-a-connection-for-exports)参照のこと。
+2. この接続を使用できる人を選択する。このフィールドを空白にすると、デフォルトはAdministratorsになる。詳細については、[共同作成者がエクスポートに接続を使用できるようにする](https://docs.microsoft.com/en-us/dynamics365/customer-insights/connections#allow-contributors-to-use-a-connection-for-exports)を参照してください。
 3. サインインを続けるには、Braze APIキーを入力する。
-4. データおよびプライバシーの遵守を確認することに**同意するを**選択する。
-5. **Connectを**選択し、Brazeとの接続を初期化する。
-6. **Add yourself as export userを**選択し、Customer Insightsの認証情報を入力する。
-7. **Saveを**選択して接続を完了する。 
+4. \[**I agree**] を選択して、データとプライバシーの遵守を確認します。
+5. \[**Connect**] を選択して、Braze への接続を初期化します。
+6. \[**Add yourself as export user**] を選択し、Customer Insights の認証情報を入力します。
+7. \[**Save**] を選択して接続を完了します。 
 
 ### ステップ2:エクスポートを設定する
 
 このタイプの接続にアクセスできる場合は、このエクスポートを設定できる。詳細については、「[輸出の概要](https://docs.microsoft.com/en-us/dynamics365/customer-insights/export-destinations#set-up-a-new-export)」を参照のこと。
 
-1. Customer Insightsで、**Data > Exportsに**進む。新しいエクスポートを作成するには、**Add destinationを**選択する。
+1. Customer Insights で **\[Data] > \[Exports]** に移動します。新しいエクスポートを作成するには、\[**Add destination**] を選択します。
 2. **Connection for export**フィールドで、Brazeセクションの接続を選択する。このセクション名が表示されない場合は、このタイプの接続はない。 
 3. RESTエンドポイントを次の形式でホスト名フィールドに入力する：`rest.iad-03.braze.com`.
-4. **Data matching**セクションの**Email**フィールドで、顧客のEメールアドレスを表すフィールドを選択する。次に、**Customer ID**フィールドで、顧客のBraze IDを表すフィールドを選択する。また、マッチング・データ用に、追加のオプション・フィールドを選択することもできる。 
-5. 最後に**Saveを**選択する。 
+4. **Data matching**セクションの**Email**フィールドで、顧客のEメールアドレスを表すフィールドを選択する。次に、**Customer ID**フィールドで、顧客のBraze IDを表すフィールドを選択する。また、データを照合するための追加のオプションフィールドを選択することもできます。 
+5. 最後に \[**Save**] を選択します。 
 
-エクスポートを保存しても、すぐにエクスポートが実行されるわけではない。このエクスポートは、[スケジュールされた更新](https://docs.microsoft.com/en-us/dynamics365/customer-insights/system#schedule-tab)ごとに実行される。[オンデマンドでデータをエクスポートする](https://docs.microsoft.com/en-us/dynamics365/customer-insights/export-destinations#run-exports-on-demand)こともできる。 
+エクスポートを保存しても、すぐにエクスポートが実行されるわけではない。このエクスポートは、[スケジュールされた更新](https://docs.microsoft.com/en-us/dynamics365/customer-insights/system#schedule-tab)ごとに実行される。[オンデマンドでデータをエクスポートする](https://docs.microsoft.com/en-us/dynamics365/customer-insights/export-destinations#run-exports-on-demand)こともできます。 
 
 ### この統合を使う
 
-セグメントがBrazeに正常にエクスポートされると、Dynamics 365 Customer Insightsのセグメントと同じ名前で、ユーザープロファイルのカスタム属性として見つけることができる。 
+Braze に正常にエクスポートされたセグメントは、Dynamics 365 Customer Insights にあるセグメントと同名のユーザープロファイルのカスタム属性として確認できます。 
 
 これらのユーザーのセグメントを作成するには、Brazeの「**セグメント**」に移動し、新しいセグメントを作成し、フィルターとして**「カスタム属性**」を選択する。ここから、Dynamics 365のカスタム属性を選択できる。セグメントを作成した後、キャンペーンまたはキャンバスを作成する際に、オーディエンスフィルターとして選択することができる。
 
 {% alert note %}
-この統合の詳細については、マイクロソフトのBraze[統合の記事を](https://docs.microsoft.com/en-us/dynamics365/customer-insights/export-braze)参照のこと。
+この統合の詳細については、Microsoft の [Braze 統合の記事](https://docs.microsoft.com/en-us/dynamics365/customer-insights/export-braze)を参照してください。
 {% endalert %}
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/ketch.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/ketch.md
index a3e79b48629..071d6ef0d88 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/ketch.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/ketch.md
@@ -1,7 +1,7 @@
 ---
 title: Ketch
 nav_title: Ketch
-description: "この参考記事では、ブレイズとケッチの統合について取り上げている。Ketchは、簡素化されたプライバシー・オペレーションと、完全でダイナミックなデータ・コントロール、そしてインテリジェンスを提供する。"
+description: "このリファレンス記事では、Braze とKetch の統合について説明します。Ketchは、簡素化されたプライバシー運用、完全でダイナミックなデータ制御、インテリジェンスを提供します。"
 alias: /partners/ketch
 page_type: partner
 search_tag: Ketch
@@ -9,9 +9,9 @@ search_tag: Ketch
 
 # Ketch
 
-> [ケッチは](https://www.ketch.com)、企業がデータの責任ある管理者となることを可能にする。Ketchは、簡素化されたプライバシー・オペレーションと、完全でダイナミックなデータ・コントロールとインテリジェンスを提供する。 
+> [Ketch ](https://www.ketch.com)は、企業がそのデータの責任者となることを可能にします。Ketchは、簡素化されたプライバシー処理、完全でダイナミックなデータ制御、インテリジェンスを提供します。 
 
-BrazeとKetchの統合により、Ketchプリファレンスセンター内で顧客のコミュニケーションプリファレンスをコントロールし、これらの変更を自動的にBrazeに反映させることができる。 
+Braze と Ketch の統合により、Ketch ユーザー設定センター内の顧客のコミュニケーション設定を管理し、これらの変更を自動的に Braze に伝播できます。 
 
 {% alert note %}
 購読グループの作成に関するガイダンスをお探しですか？<a href='/docs/user_guide/message_building_by_channel/sms/sms_subscription_group//'>SMS購読グループと</a> <a href='/docs/user_guide/message_building_by_channel/email/managing_user_subscriptions/'>Eメール購読</a>グループの記事をチェックする。
@@ -21,41 +21,41 @@ BrazeとKetchの統合により、Ketchプリファレンスセンター内で
 
 | 要件 | 説明 |
 |---|---|
-| ケッチアカウント | この統合を有効にするには、管理者権限を持つ[Ketch](https://www.ketch.com)アカウントが必要である。 |
-| BrazeのAPIキー | `users.track` 、`subscription.status.get` 、`subscription.status.set` 、`users.delete` 、`users.alias.new` 、`users.export.ids` 、`email.unsubscribe` 、`email.blacklist` のパーミッションを持つBraze REST APIキー。<br><br> これは、Brazeのダッシュボード**（Developer Console**>**REST API Key**>**Create New API Key**）で作成できる。 |
+| Ketch アカウント | この統合を有効にするには、管理者権限を持つ[Ketch](https://www.ketch.com)アカウントが必要である。 |
+| BrazeのAPIキー | `users.track`、`subscription.status.get`、`subscription.status.set`、`users.delete`、`users.alias.new`、`users.export.ids`、`email.unsubscribe`、`email.blacklist` の権限を持つ Braze REST API キー。<br><br> これは Brazeダッシュボード (\[**開発者コンソール**] > \[**REST API キー**] > \[**新しい API キーを作成**]) で作成できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:Brazeの接続をセットアップする
 
-1. [ケッチ・インスタンスで](https://app.ketch.com)、**データ・**システムに移動し、**ブレイズを**選択する。次に、**New Connectionを**クリックする。
-2. Braze接続に識別可能な名前を付け、APIベースの処理でこの接続を参照するために使用する。その接続にはコードも作成される。このコードは、すべての接続で一意でなければならない。
-3. ユーザーのIDマッピングを確認する。デフォルトでは、Ketchはユーザーの電子メールアドレス、またはBrazeの`external_id` 。
+1. [Ketch インスタンス](https://app.ketch.com)で \[**Data Systems**] に移動し、\[**Braze**] を選択します。次に \[**New Connection**] をクリックします。
+2. Braze接続に識別可能な名前を付け、APIベースの処理でこの接続を参照するために使用する。この接続のためのコードも作成されることに注意してください。このコードは、すべての接続において一意である必要があります。
+3. ユーザーのIDマッピングを確認する。デフォルトでは、Ketch はユーザーのメールアドレスまたは Braze の`external_id` によってユーザー ID をマッピングします。
 4. Braze APIキーを追加し、APIエンドポイントを指定する。この[APIエンドポイントは](https://www.braze.com/docs/api/basics/#endpoints)、あなたの組織が使用しているBrazeインスタンスに基づいていることに注意すること。
 
-### ステップ2:購読設定を行う
+### ステップ2:サブスクリプション設定を構成する
 
-1. **ポリシー・センター＞サブスクリプションに**進む。**Policy Center（ポリシーセンター）**」に「Subscriptions（購読）」タブが表示されない場合は、マーケティング・プリファレンス・センターにアクセスできることを確認し、製品のこの部分にアクセスするための正しいアカウント権限を持っていることを確認する。
-2. **新しい購読を作成**] をクリックして、新しいトピックを作成する。各サブスクリプションには名前とコードがある。
-3. 購読トピックを送信するチャンネルを追加する。各チャンネルは、ユーザーのマーケティング・プレファレンス・センターに表示される。また、ケッチ・プリファレンス・センターに特定のオプトインやオプトアウトのシグナルをどのようにオーケストレーションさせたいかの詳細を追加することもできる。
+1. **\[Policy Center] > \[Subscriptions]** に移動します。**Policy Center（ポリシーセンター）**」に「Subscriptions（購読）」タブが表示されない場合は、マーケティング・プリファレンス・センターにアクセスできることを確認し、製品のこの部分にアクセスするための正しいアカウント権限を持っていることを確認する。
+2. \[**Create New Subscription**] をクリックして新しいトピックを作成します。各サブスクリプションには名前とコードがある。
+3. 購読トピックを送信するチャンネルを追加する。各チャネルは、ユーザーのマーケティングユーザー設定センターに表示されます。また、Ketch ユーザー設定センターで特定のオプトインシグナルまたはオプトアウトシグナルを調整する方法の詳細を追加することもできます。
 4. オプトインおよびオプトアウト信号の編成に使用するBraze接続を選択する。
-5. Ketchユーザー設定を送信したい購読グループのBraze`subscription_group_id` を入力する。
+5. Ketch ユーザー設定を送信するサブスクリプショングループの Braze `subscription_group_id` を入力します。
 
 ![Brazeサブスクリプション・グループID。][1]
 
 {% alert note %}
-ユーザーのオプトインとオプトアウトのシグナルを収集し、組織化するためには、IDが適切に設定されていなければならない。Ketchは、この統合のために、ユーザー・プレファレンス・シグナルをオーケストレーションする識別子として電子メールを設定することを推奨している。
+ユーザーのオプトインとオプトアウトのシグナルを収集し、組織化するためには、IDが適切に設定されていなければならない。Ketch では、この統合向けににユーザー設定シグナルを調整するために、識別子としてメールを設定することをお勧めしています。
 {% endalert %}
 
 
 ### ステップ3:アイデンティティを設定する
 
-ユーザーがマーケティング・プリファレンス・センターを見ることができるのは、Ketchがそのユーザーのマーケティング・プリファレンス・アイデンティティを確認できたときだけである。もしKetchがユーザーのIDを適切に捕捉できない場合、Ketchはユーザーのプリファレンスを管理できないので、マーケティング・プリファレンス・ページはそのユーザーに表示されない。
+ユーザーは、Ketch がそのユーザーのマーケティングユーザー設定 ID を確認できる場合にのみ、マーケティングユーザー設定センターを表示できます。Ketch がユーザーの ID を適切にキャプチャできない場合、Ketch はそのユーザーのユーザー設定を管理できないため、そのユーザーに対してマーケティングユーザー設定ページは表示されません。
 
-1. マーケティング・プリファレンス・アイデンティティを構成するには、Ketch の**「Settings」**ページに移動し、「**Identity space**」をクリックする。新しい ID スペースを作成するか、既存の ID スペースを編集して、その ID スペースをマ ーケティング優先 ID として割り当てる必要がある。敷地内に配置されたケッチ・タグが、そのIDスペースを適切に捉えていることを確認する。
-2. **エクスペリエンス・サーバー**]、\[**プロパティ**] の順に選択し、目的のプロパティを編集する。そのプロパティのデータレイヤーで、カスタム・アイデンティティ・スペースを有効にする。次に、このサイトでマーケティング嗜好のアイデンティティをどのように取得するかを設定する。
-3. アイデンティティ・スペースを設定したら、Ketchタグが配置されたウェブサイト上でプリファレンス・センターを開き、プリファレンス・センターが表示されるかどうかをテストする。
+1. マーケティングユーザー設定 ID を設定するには、Ketch の \[**Settings**] ページに移動し、\[**Identity space**] をクリックします。新しいアイデンティティスペースを作成するか、既存のアイデンティティスペースを編集して、そのアイデンティティスペースをマーケティングユーザー設定 ID として割り当てる必要があります。プロパティに導入されている Ketch タグが、そのアイデンティティスペースを適切にキャプチャしていることを確認します。
+2. **エクスペリエンス・サーバー**]、\[**プロパティ**] の順に選択し、目的のプロパティを編集する。そのプロパティのデータレイヤーで、カスタムアイデンティティスペースを有効にします。次に、このサイトでマーケティングユーザー設定 ID をキャプチャする方法を設定します。
+3. アイデンティティスペースを設定したら、Ketch タグが導入されている Web サイトのユーザー設定センターを開いて、ユーザー設定センターが表示されるかどうかをテストします。
 
 
 [1]: {% image_buster /assets/img/ketch/ketch1.png %}
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/lexer.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/lexer.md
index 96fba0db258..50995d2285d 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/lexer.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/lexer.md
@@ -1,74 +1,74 @@
 ---
-nav_title: レクサー
-article_title: レクサー
-description: "この参考記事では、BrazeとLexerの提携について概説している。Lexerは、顧客データをマーケティング担当者の手に委ね、売上を促進する体験を喚起する顧客データ・プラットフォームである。"
+nav_title: Lexer
+article_title: Lexer
+description: "このリファレンス記事では、Braze と Lexer のパートナーシップについて説明します。Lexer はマーケターが顧客データを使用して、売上を伸ばすエクスペリエンスを生み出すことができる顧客データプラットフォームです。"
 alias: /partners/lexer/
 page_type: partner
 search_tag: Partner
 ---
 
-# レクサー
+# Lexer
 
-> \[小売業向けに構築された顧客データプラットフォームであるLexer][6] は、堅牢なデータエンリッチメントと最も直感的なツールおよび専門家の助言を組み合わせることで、ブランドが顧客体験を向上させ、売上の増加を促進するのを支援する。
+> \[Lexer][6] は小売業向けに構築された顧客データプラットフォームであり、堅牢なデータ強化機能と最も直感的なツールおよび専門家によるアドバイスを組み合わせて、ブランドが改善されたカスタマーエクスペリエンスによりインクリメンタルセールスを伸ばすことができるようにします。
 
-BrazeとLexerの統合により、2つのプラットフォーム間でデータを同期することができる。Lexerのデータを使用して価値あるBrazeセグメントを作成するか、既存のセグメントをLexerにインポートしてインサイトを引き出す。 
+Braze と Lexer の統合により、この2つのプラットフォーム間でデータを同期できます。Lexer のデータを使用して有益な Braze セグメントを作成するか、既存のセグメントを Lexer にインポートしてインサイトを引き出します。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| パートナーアカウント | このパートナーシップを利用するには、Lexerアカウントが必要である。 |
-| Braze REST API キー | `users.track` 権限（`user.delete` を除く）と`segment.list` 権限を持つ Braze REST API キー。Lexerがより多くのBrazeオブジェクトをサポートするようになると、パーミッション・セットは変更される可能性がある。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
+| パートナーアカウント | このパートナーシップを活用するには、Lexer アカウントが必要です。 |
+| Braze REST API キー | `users.track` 権限 (`user.delete` を除く) と`segment.list` 権限を持つ Braze REST API キー。Lexer でサポートされる Braze オブジェクトの増加に伴い、権限セットが変わる可能性があります。このため、この時点でより多くの権限を付与するか、これらの権限を今後更新する計画を立てることができます。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL]({{site.baseurl}}/api/basics/#endpoints)。エンドポイントは、インスタンスのBraze URLに依存する。 |
-| Amazon AWS S3バケットと認証情報 | 統合を開始する前に、Lexerハブに接続されているAWS S3バケットのアクセス認証情報が必要である（これは、あなたが作成したバケットでも、Lexerがあなたのために作成し管理するバケットでもよい）。この要件に関するガイダンスについては、[Lexerを](https://learn.lexer.io/docs/amazon-s3)参照のこと。 |
+| Amazon AWS S3バケットと認証情報 | 統合を開始する前に、Lexer ハブに接続されている AWS S3 バケット (お客様が作成したバケットまたはLexer がお客様のために作成して管理しているバケット) のアクセス認証情報が必要です。この要件に関するガイダンスについては、[Lexerを](https://learn.lexer.io/docs/amazon-s3)参照のこと。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-Lexerで、**Manage > Integrationに**移動し、**Braze**タイルを選択し、**Integrate Brazeを**クリックする。以下の情報を提供する：
+Lexerで **\[Manage] > \[Integration]** に移動し、\[**Braze**] タイルを選択し、\[**Integrate Braze**] をクリックします。次の情報を入力します。
 - **Braze RESTエンドポイント**
 - **Braze REST API キー**
-- **AWSクレデンシャル**
-  - **AWS S3バケット名**
+- **AWS 認証情報**
+  - **AWS S3 バケット名**
   - **AWS S3 \[バケットリージョン][4]**
-  - **AWS S3バケットのパス**：このパスは、\[S3バケットをBraze][5] に接続する]際に指定したパスと一致する必要がある。Brazeに何も指定しなかった場合は空白にする。
-  - **AWS S3のシークレットアクセスキー**：アクセスキーの作成]に関する情報はアマゾンを参照のこと][3] 。
-- **ブレイズの輸出セグメントID**：Lexerにエクスポートしたいすべてのユーザーを含む、Brazeで作成したセグメントのID。Lexerにエクスポートしたくないユーザーがいる場合は、Brazeで作成したセグメントから除外することができる。セグメント識別子を見つけるには、Brazeで目的のセグメントをクリックし、**セグメントAPI識別子を**見つける。
+  - **AWS S3バケットのパス**：このパスは、\[S3バケットを Braze に接続する][5]ときに指定したパスと一致している必要があります。Brazeに何も指定しなかった場合は空白にする。
+  - **AWS S3シークレットアクセスキー**:アクセスキーの作成]に関する情報はアマゾンを参照のこと][3] 。
+- **Braze エクスポートセグメント ID**:Lexerにエクスポートしたいすべてのユーザーを含む、Brazeで作成したセグメントのID。Lexerにエクスポートしたくないユーザーがいる場合は、Brazeで作成したセグメントから除外することができる。セグメント識別子を確認するには、Braze で目的のセグメントをクリックし、\[**セグメント API 識別子**] を見つけます。
 
 ![][1]
 
-### AWS S3のオプションを選択する（Lexer管理または自己管理）
-BrazeをLexerハブに接続するには、Lexerが管理するバケットを使用するのが望ましい。Lexerは、Brazeの設定に必要な1回限りの詳細を提供する。
+### AWS S3 オプションを選択する (Lexer マネージドまたはセルフマネージド)
+Braze を Lexer ハブに接続する方法として、Lexer マネージド バケットを使用する方法が推奨されます。これにより、必要な設定作業が減ります。Lexer は、Braze の設定に必要な1回限りの詳細情報を提供します。
 
 すでにS3バケットをBrazeに接続し、他の目的で使用している場合は、代わりに、前述の手順に従って、Lexerにこの自己管理バケットへのアクセスを提供する必要がある。
 
-この統合は、既存のAPIトークンとシークレットをLexerに提供し、Lexerがあなたに代わってこれらのエクスポートを行うことで機能する。また、これらの認証情報とS3の設定を使用して、BrazeのデータをLexerにインポートし、両プラットフォームのデータを自動的に同期する。
+この統合は、既存のAPIトークンとシークレットをLexerに提供し、Lexerがあなたに代わってこれらのエクスポートを行うことで機能する。また、これらの認証情報と S3設定を使用して Braze データが Lexer にインポートされ、両方のプラットフォームのデータが自動的に同期されます。
 
-## セグメントをブレイズに送る
+## Braze にセグメントを送信する
 
 ### ステップ1:アクティベーションを行う
 
-Lexer ActivateはBrazeプロファイルを自動的に更新し、顧客のセグメントへの出入りに応じて属性を追加または削除する。
+Lexer Activate により Braze プロファイルが自動的に更新され、セグメントへの顧客の出入りに応じて属性が追加または削除されます。
 
-1. Lexerの\[**Lexer Activations**]で**\[ACTIVATE NEW AUDIENCE]**をクリックする。
+1. Lexer の \[**Lexer Activations**] で \[**ACTIVATE NEW AUDIENCE**] をクリックします。
 2. このキャンペーンに適切なBrazeのアクティベーションを選択する。
 3. セグメントを追加する。
-4. オーディエンス名を更新する。これがBrazeでの属性値となる。
-5. これがBrazeで更新するカスタム属性だ。[Lexerサポートに](support@lexer.io)連絡してアップデートする。
-6. 適切なリストアクションをチェックする。
+4. オーディエンス名を更新します。これは Braze での属性値となります。
+5. これがBrazeで更新するカスタム属性だ。更新のため [Lexer サポート](support@lexer.io)に連絡します。
+6. 適切なリストアクションを確認します。ほとんどの場合、リストを維持します。
 7. 規約を確認し、**「SEND AUDIENCE**」をクリックする。
 
 ![][7]
 
 ### ステップ2:アクティベーションを確認する
 
-Activateでアクティベーションが送信されたことが確認されると、Brazeで記録が更新され始める。Lexerから確認メールが届くまで、Brazeのプロフィールは完全に更新されない。
+Activate でアクティベーションが送信されたことが確認されると、Braze でレコードの更新が開始されます。Lexer から確認メールが届くまで、Braze のプロファイルは完全には更新されません。
 
-### ステップ3:ブレイズ・セグメントを作成する
+### ステップ3:Braze セグメントを作成する
 
-Brazeでは、Lexerのオーディエンス名が`lexer_audience` カスタム属性の値になっていることがわかる。Brazeには、1つの属性につき100個の値という制限がある。
+Brazeでは、Lexer のオーディエンス名が `lexer_audience` カスタム属性の値になっています。Braze では、属性あたりの値の数は100に制限されています。
 
-セグメントを作成するには、「**セグメント > + セグメントの作成**」と進み、フィルターとして**「カスタム属性**」を選択する。次に、属性として`lexer_audience` 、オーディエンス名としてLexerを選択する。完了したら、オーディエンスを**保存する**。
+セグメントを作成するには、「**セグメント > + セグメントの作成**」と進み、フィルターとして**「カスタム属性**」を選択する。次に、属性として `lexer_audience` を選択し、目的の Lexer オーディエンス名を選択します。完了したら、オーディエンスを**保存**します。
 
 この新しく作成したセグメントを、今後のBrazeのキャンペーンやキャンバスに追加して、これらのエンドユーザーをターゲットにすることができる。
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/lytics.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/lytics.md
index 97629239896..e10785ec655 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/lytics.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/lytics.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Lytics
 article_title: Lytics
-description: "この参考記事は、BrazeとLyticsの統合をカバーしている。Lyticsは、マーケティング担当者、アナリスト、技術者のための企業向け顧客データプラットフォームである。この統合により、ブランドはLyticsのデータをBrazeに直接同期し、マッピングすることができる。"
+description: "このリファレンス記事では、Braze と Lytics の統合について説明します。Lytics は、マーケター、アナリスト、技術者向けのエンタープライズ顧客データプラットフォームです。この統合により、ブランドは Lytics のデータを Braze に直接同期およびマッピングできます。"
 alias: /partners/lytics/
 page_type: partner
 search_tag: Partner
@@ -9,45 +9,45 @@ search_tag: Partner
 
 # Lytics
 
-> [Lyticsは][1]、顧客中心の次世代ビジネスに選ばれる顧客データプラットフォーム（CDP）である。Lytics Decision Engine、Conductor、Cloud Connectの各ソリューションは、マーケティング担当者とデータチームに、プライバシーに準拠した方法で、アイデンティティ解決、オーケストレーション、キャンペーン最適化をリアルタイムで実行する機会を提供する。
+> [Lytics][1] は、顧客中心の次世代ビジネスに最適な顧客データプラットフォーム (CDP) です。Lytics Decision Engine、Conductor、Cloud Connectの各ソリューションは、マーケティング担当者とデータチームに、プライバシーに準拠した方法で、アイデンティティ解決、オーケストレーション、キャンペーン最適化をリアルタイムで実行する機会を提供する。
 
-BrazeとLyticsの統合は、顧客の統一されたビューを提供し、強力なパーソナライゼーションを可能にし、次善のアクションオーケストレーションと決定を用いて最適化されたキャンペーンを推進する。
+Braze と Lytics の統合により、顧客を一元的に把握できるため、強力なパーソナライゼーションが可能になり、ネクストベストアクションオーケストレーションと意思決定を使用して最適化されたキャンペーンを推進できます。
 
-この統合により、ブランドは以下のことが可能になる：
+この統合により、ブランドは以下のことができるようになります。
 
-- Lyticsから直接Brazeにオーディエンスをエクスポートする
+- Lytics から直接 Braze にオーディエンスをエクスポートする
 - BrazeのキャンペーンやCanvasesのイベントをリアルタイムでLyticsに送信し、パーソナライズされたキャンペーンやリッチなユーザープロファイルを構築する。
 
 ## ユースケース
 
-BrazeをLyticsに接続して、電子メール、SMS、プッシュのアクティビティを[インポート](#importing-data-from-braze-to-lytics)し、Lyticsのユーザープロファイルを充実させる。BrazeとLyticsを一緒に使えば、Lyticsのクロスチャネル、行動主導型オーディエンスを[エクスポートして](#integration)、ファーストパーティデータを使って高度にパーソナライズされたBrazeカスタマージャーニーを構築することもできる。
+Braze を Lytics に接続して、メール、SMS、プッシュアクティビティを[インポート](#importing-data-from-braze-to-lytics)し、Lytics のユーザープロファイルを充実させます。Braze と Lytics を併用することで、Lytics のクロスチャネル、行動主導型のオーディエンスを[エクスポート](#integration)し、ファーストパーティデータを使用して高度にパーソナライズされた Braze カスタマージャーニーを構築することもできます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| Lyticsアカウント | この統合を利用するには、Lyticsのアカウントが必要である。 |
+| Lyticsアカウント | この統合を活用するには、Lytics アカウントが必要です。 |
 | Lyticsアカウント番号 | ウェブフックのエンドポイントURLを設定するには、Lyticsのアカウント番号が必要である。 |
 | Lytics APIトークン | データマネージャー権限を持つLytics REST APIトークン。<br><br> これは、Lyticsダッシュボード内の**「アカウント設定コンソール**」＞「**アクセストークン**」＞「**新しいトークンの作成**」から作成できる。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| ブレイズインスタンス | [ブレイズのインスタンス]({{site.baseurl}}/user_guide/administrative/access_braze/sdk_endpoints)だ。不明な場合は、Brazeのオンボーディング・マネージャーに問い合わせること。 |
+| ブレイズインスタンス | お客様の [Braze インスタンス]({{site.baseurl}}/user_guide/administrative/access_braze/sdk_endpoints)。不明な場合は、Brazeのオンボーディング・マネージャーに問い合わせること。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 このセクションでは、LyticsのデータをBrazeにエクスポートする方法を説明する。
 
-### ステップ1:認可を作成する
+### ステップ1:認証を作成する
 
-Lyticsで、ナビゲーションバーの**データ・**コンソール内の**認可**ダッシュボードに移動する。**Create New Authorizationを**選択し、**Brazeを**検索して選択する。
+Lyticsで、ナビゲーションバーの \[**Data**] コンソール内の \[**Authorization**] ダッシュボードに移動します。\[**Create New Authorization**] を選択し、**Braze** を検索して選択します。
 
-表示される**Configure Authorization**プロンプトで、ラベルと説明を入力し、REST APIキーとBrazeインスタンスを入力する。終了したら**Completeを**選択する。
+表示される**Configure Authorization**プロンプトで、ラベルと説明を入力し、REST APIキーとBrazeインスタンスを入力する。完了したら \[**Complete**] を選択します。
 
 ![][2]{: style="max-width:80%;"}
 
 ### ステップ2:新しい仕事を作る
 
-Lyticsで、ナビゲーションバーの**データ**コンソール内の**ジョブダッシュボードに**移動する。**Create New Jobを**選択し、**Brazeを**検索して選択する。 表示される**Select Job Type**プロンプトで、**Export Audienceを**選択する。
+Lytics で、ナビゲーションバーの \[**Data**] コンソール内の\[**Jobs**] ダッシュボードに移動します。\[**Create New Job**] を選択し、**Braze** を検索して選択します。 表示される \[**Select Job Type**] プロンプトで \[**Export Audience**] を選択します。
 
 ![][3]{: style="max-width:80%;"}
 
@@ -57,21 +57,21 @@ Lyticsで、ナビゲーションバーの**データ**コンソール内の**
 
 ### ステップ3:ジョブを設定する
 
-**Configure Job**プロンプト内で、ラベルとオプションの説明を入力する。次に、**Braze External User ID Field**入力から、Braze外部ユーザーID（`braze_id` ）を含むLyticsのフィールドを選択する。次のステップが最も重要で、Brazeにエクスポートするオーディエンスを選択する。
+**Configure Job**プロンプト内で、ラベルとオプションの説明を入力する。次に \[**Braze External User ID Field**] の入力から、Braze 外部ユーザー ID (`braze_id`) を含む Lytics のフィールドを選択します。次は最も重要なステップです。Braze にエクスポートするオーディエンスを選択します。
 
 ![][5]{: style="max-width:80%;"}
 
-最後に、"**Existing Users**"チェックボックスで好ましいオプションを選択する。このボックスにチェックを入れたままにしておくと、選択したLyticsオーディエンスにすでに存在しているユーザーを追加する。チェックを外すと、ワークフロー開始後にオーディエンスに入室または退室するときのみ、ユーザーがBrazeにエクスポートされる。
+最後に、"**Existing Users**"チェックボックスで好ましいオプションを選択する。このボックスをオンのままにすると、選択した Lytics オーディエンスにすでに存在しているユーザーが追加されます。オフにすると、ワークフロー開始後にオーディエンスに追加される時点またはオーディエンスから外される時点でのみ、ユーザーが Braze にエクスポートされます。
 
 {% alert note %}
-このボックスをチェックすることで、選択したオーディエンスのすべての既存ユーザーがBrazeにプッシュされる。この結果、最初の同期では、視聴者1人につきユーザー1人分のデータポイントが発生することになる。
+このボックスをチェックすることで、選択したオーディエンスのすべての既存ユーザーがBrazeにプッシュされる。これにより、最初の同期ではユーザーごと、オーディエンスごとにデータポイントが発生します。
 {% endalert %}
 
-**完了**したら**Completeを**クリックしてエクスポートを開始し、保存する。
+完了したら \[**完了**] をクリックしてエクスポートを開始し、保存します。
 
 ![][6]{: style="max-width:80%;"}
 
-エクスポートジョブが設定されると、Lyticsはネイティブ統合を通じて、選択されたオーディエンスをBrazeに送信する。以下は、Brazeに送信されたオーディエンスのJSON構造を示すサンプルオーディエンスである。
+エクスポートジョブの設定が完了したら、Lytics はネイティブ統合を介して、選択されたオーディエンスを Braze に送信します。以下は、Braze に送信されるオーディエンスの JSON 構造を示すサンプルオーディエンスです。
 
 ```json
 {
@@ -99,30 +99,30 @@ Lyticsで、ナビゲーションバーの**データ**コンソール内の**
 }
 ```
 
-オーディエンスエクスポートに含まれる、Brazeにまだ存在しない`external_id` 、Brazeに新しいユーザーが作成される。 
+オーディエンスのエクスポートに含まれ、Braze にまだ存在していない `external_id` に対し、Braze で新しいユーザーが作成されます。 
 
 ## BrazeからLyticsにデータをインポートする
 
-BrazeからLyticsへのオーディエンスデータのインポートは、以下の方法で行うことができる：
+Braze から Lytics へのオーディエンスデータのインポートは、以下の方法で行うことができます。
 
-- [ウェブフックを使う](#using-webhooks)
+- [Webhook を使用する](#using-webhooks)
 - [CSVファイルから](#from-a-csv-file)
 
 ### ウェブフックを使う
 
 #### ステップ1:Lytics API トークンを作成する
 
-左下にあるLyticsアカウントメニューに移動し、アカウント名を選択し、ドロップダウンメニューから**Access Tokensを**選択する。次に、**Create API Tokenを**選択する。
+アカウント名を選択して左下にある Lytics Account Menu に移動し、ドロップダウンメニューから \[**Access Tokens**] を選択します。次に \[**Create API Token**] を選択します。
 
 ![][7]{: style="max-width:80%;"}
 
-名前、オプションの説明、トークンの有効期限を入力する。次に、**Data Managerの**スコープをAPI Permissionsに切り替え、**Generate Tokenを**クリックする。トークンをコピーし、安全な場所に保管する。
+名前、オプションの説明、トークンの有効期限を入力する。次に API 権限の \[**Data Manager**] スコープをオンに切り替え、\[**Generate Token**] をクリックします。トークンをコピーし、安全な場所に保管する。
 
 ![][8]{: style="max-width:80%;"}
 
 #### ステップ2:LyticsのウェブフックURLを設定する
 
-Lytics webhook URLは、BrazeからLytics APIにメッセージを送信するためにBrazeによって使用される。このメッセージは、Lyticsでキャンペーンをパーソナライズしたり、Lyticsの顧客プロファイルを充実させたりするために使用できる。以下の2つのパラメータは、LyticsウェブフックURL内に追加する必要がある：
+Lytics Webhook URL は、Braze から Lytics API にメッセージを送信するために Braze によって使用されます。このメッセージは、Lytics でキャンペーンをパーソナライズする場合や、Lytics の顧客プロファイルを充実させる場合に使用できます。以下の2つのパラメータは、LyticsウェブフックURL内に追加する必要がある：
 
 - Lyticsアカウント番号
 - Lytics APIトークン
@@ -133,13 +133,13 @@ Lytics webhook URLは、BrazeからLytics APIにメッセージを送信する
 https://api.lytics.io/c/<ACCOUNT-NUMBER>/braze_users?key=<LYTICS-API-TOKEN>
 ```
 
-`<ACCOUNT-NUMBER>` をあなたのアカウント番号に、`<LYTICS-API-TOKEN>` をあなたの Lytics API トークンに置き換える。
+`<ACCOUNT-NUMBER>` をアカウント番号に置き換え、`<LYTICS-API-TOKEN>` を Lytics API トークンに置き換えます。
 
 #### ステップ3:BrazeでWebhookを作成する 
 
-Brazeで、新しい[Webhookキャンペーンを]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/)作成する。**Webhook URL**フィールドにLyticsのWebhook URLを追加する。
+Braze で新しい [Webhook キャンペーン]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/)を作成します。**Webhook URL**フィールドにLyticsのWebhook URLを追加する。
 
-リクエストタイプ（HTTP`POST` メソッド）を定義し、残りのウェブフックの詳細を設定したら、ウェブフックのテストとデプロイの準備は完了だ。以下は、BrazeでWebhookを設定した後のPOSTリクエスト本文のサンプルである：
+リクエストタイプ (HTTP `POST` メソッド) を定義し、残りの Webhook の詳細を設定したら、Webhook をテストおよびデプロイできます。以下は、BrazeでWebhookを設定した後のPOSTリクエスト本文のサンプルである：
 
 ```json
 {
@@ -162,11 +162,11 @@ Brazeで、新しい[Webhookキャンペーンを]({{site.baseurl}}/user_guide/m
 
 このセクションでは、BrazeのユーザーデータをセグメントからLyticsにインポートする方法を説明する。
 
-#### ステップ1:認可を作成する
+#### ステップ1:認証を作成する
 
-Lyticsで、ナビゲーションバーの**データ・**コンソール内の**認可**ダッシュボードに移動する。**Create New Authorizationを**選択し、**Custom Integrationsを**検索して選択する。
+Lyticsで、ナビゲーションバーの \[**Data**] コンソール内の \[**Authorization**] ダッシュボードに移動します。\[**Create New Authorization**] を選択し、\[**Custom Integrations**] を検索して選択します。
 
-ビジネス要件とセキュリティ要件に基づいて、SFTP認証の優先タイプを選択する。SFTP経由でLyticsにファイルをインポートする場合、以下の認証タイプがサポートされている：
+ビジネス要件とセキュリティ要件に基づいて、使用する SFTP 認証タイプを選択します。SFTP経由でLyticsにファイルをインポートする場合、以下の認証タイプがサポートされている：
 
 - クライアントSFTPサーバー認証
 - PGP秘密鍵によるクライアントSFTPサーバー認証
@@ -176,21 +176,21 @@ Lyticsで、ナビゲーションバーの**データ・**コンソール内の*
 
 ![][9]{: style="max-width:80%;"}
 
-表示された**Configure Authorization**プロンプトで、ラベルと説明を入力し、残りの構成要件を完了する。完了したら**Completeを**クリックする。
+表示された**Configure Authorization**プロンプトで、ラベルと説明を入力し、残りの構成要件を完了する。完了したら \[**Complete**] をクリックします。
 
 #### ステップ2:セグメントデータをCSVにエクスポートする
 
-Brazeで、**Audience**>**Segmentsに**移動する。エクスポートしたいセグメントを探し、以下を選択する。 <i class="fas fa-gear" aria-label="設定"></i>を選択し、次に**CSV Export User Dataを**選択する。セグメントで最大50万ユーザーをエクスポートできる。詳しくは、[セグメントデータをCSVにエクスポートするを]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/segment_data_to_csv)参照のこと。
+Braze で \[**オーディエンス**] > \[**セグメント**] に移動します。エクスポートするセグメントを見つけ、\[<i class="fas fa-gear" aria-label="設定"></i>] を選択し、次に \[**ユーザーデータを CSV 形式でエクスポート**] を選択します。1つのセグメントで最大50万ユーザーをエクスポートできます。詳細については、「[CSV へのセグメントデータのエクスポート]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/segment_data_to_csv)」を参照してください。
 
 #### ステップ3:CSVインポートジョブを設定する
 
-Lyticsで、ナビゲーションバーの**データ**コンソール内の**ジョブダッシュボードに**移動する。**Create New Jobを**選択し、**Custom Integrationsを**検索して選択する。
+Lytics で、ナビゲーションバーの \[**Data**] コンソール内の\[**Jobs**] ダッシュボードに移動します。\[**Create New Job**] を選択し、\[**Custom Integrations**] を検索して選択します。
 
-次に、ジョブ・タイプを選択する。BrazeのCSVファイルをLyticsにインポートするには、ジョブタイプとして**CSVインポートを**選択する。
+次にジョブタイプを選択します。Braze の CSV ファイルを Lytics にインポートするには、ジョブタイプとして \[**Import CSV**] を選択します。
 
 ![][10]{: style="max-width:80%;"}
 
-最後に、仕事のラベルと任意の説明を入力し、その他の必要な詳細を設定する。**Completeを**クリックしてジョブを開始し、保存する。
+最後に、仕事のラベルと任意の説明を入力し、その他の必要な詳細を設定する。\[**Complete**] をクリックして、ジョブを開始し、保存します。
 
 [1]: https://www.lytics.com/
 [2]: {% image_buster /assets/img/lytics/braze_authorization.png %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle.md
index 288f841bd1e..a954df2f52f 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle.md
@@ -2,7 +2,7 @@
 nav_title: mParticle
 article_title: mParticle
 alias: /partners/mparticle/
-description: "この記事は、BrazeとmParticleのパートナーシップについて説明しています。mParticleは、マーケティングスタック内のソース間で情報を収集およびルーティングする顧客データプラットフォームです。"
+description: "このリファレンス記事では、Braze と mParticle のパートナーシップについて説明します。mParticle は、マーケティングスタックのソース間で情報を収集してルーティングする顧客データプラットフォームです。"
 page_type: partner
 search_tag: Partner
 
@@ -12,34 +12,34 @@ search_tag: Partner
 
 {% multi_lang_include video.html id="Njhqwd36gZM" align="right" %}
 
-> mParticleの顧客データプラットフォームは、データを活用する力を高めます。洗練されたマーケターは、mParticleを使用して成長スタック全体にわたるデータを調整し、重要なカスタマージャーニーの瞬間に勝利することを可能にします。
+> mParticle の顧客データプラットフォームは、データの有効活用を支援しています。熟練したマーケターは、mParticle で成長スタック全体のデータのオーケストレーションを行い、カスタマージャーニーの重要なタイミングで適切な行動を取ることができます。
 
 BrazeとmParticleの統合により、2つのシステム間の情報の流れをシームレスにコントロールできます。
-- mParticleのオーディエンスをBrazeに同期して、Brazeのキャンペーンとキャンバスのセグメンテーションを行います。
-- 2つのプラットフォーム間でデータを共有する。これはmParticleキット統合とサーバー間統合を通じて行うことができます。
-- [mParticleを通じてBrazeユーザーのインタラクションをCurrentsに送信]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents/)し、成長スタック全体でアクション可能にします。 
+- Braze キャンペーンとキャンバスのセグメンテーションのために、mParticle のオーディエンスを Braze に同期する。
+- 2つのプラットフォーム間でデータを共有する。これは mParticl eキット統合とサーバー間統合によって可能になります。
+- [Currents を介して mParticle に Braze ユーザーインタラクションを送信し]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents/)、グローススタック全体で実行可能にする。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
 | mParticle アカウント | このパートナーシップを利用するには、[mParticleアカウント](https://app.mparticle.com/login)が必要です。 |
-| Brazeインスタンス | Brazeインスタンスは[API概要ページ]({{site.baseurl}}/api/basics/#endpoints)にあります。例えば：米国-01、米国-02、など。 |
-| Brazeアプリ識別子キー | あなたのアプリ識別子キー。<br><br>これは、**Braze ダッシュボード > 設定の管理 > API キー**内にあります。 |
+| Brazeインスタンス | Brazeインスタンスは[API概要ページ]({{site.baseurl}}/api/basics/#endpoints)にあります。例えば：US-01、US-02 など) |
+| Brazeアプリ識別子キー | アプリ識別子キー。<br><br>これは、**Braze ダッシュボード > 設定の管理 > API キー**内にあります。 |
 | ワークスペース REST APIキー | （サーバー間）Braze REST APIキー<br><br>これは、**Braze ダッシュボード > 開発者コンソール > API 設定 > API キー**内で作成できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### 観客
+### オーディエンス
 
-BrazeとmParticleのパートナーシップを利用して、統合を構成し、mParticleのオーディエンスを直接Brazeにインポートしてリターゲティングを行い、1つのシステムから別のシステムへのデータの完全なループを作成します。設定した任意の統合は、アカウントのデータポイント量にカウントされます。
+BrazeとmParticleのパートナーシップを利用して、統合を構成し、mParticleのオーディエンスを直接Brazeにインポートしてリターゲティングを行い、1つのシステムから別のシステムへのデータの完全なループを作成します。設定するすべての統合は、アカウントのデータポイントボリュームの対象となります。
 
-#### 転送オーディエンス
+#### オーディエンスの転送
 
 mParticleは、コホートメンバーシップ属性を設定するための3つの方法を提供しており、「[Send Segments As](#send_settings)」構成設定によって制御されます。次のセクションを参照して、各オプションの処理を行ってください。
 
-- [シングルストリング属性](#string)
+- [単一文字列属性](#string)
 - [シングル配列属性](#array)
 - [セグメントごとに1つの属性](#per-segment)
 - [単一の配列属性と単一の文字列属性の両方](#both-1)
@@ -56,24 +56,24 @@ mParticleは、`SegmentMembership`という単一のカスタム属性を作成
 これはmParticleのデフォルトオプションですが、ほとんどのBrazeユーザーはBrazeでセグメントを作成する際のフィルタリング体験のために[単一配列属性](#array)を使用することを選択します。
 
 {% alert important %}
-このソリューションは、オーディエンスが数人以上いる場合にはお勧めできません。カスタム属性は最大255文字まで可能なので、この方法では数十または数百のオーディエンスをユーザープロファイルに保存することはできません。ユーザーごとに多くのコホートがある場合は、「1属性ごとに1Segment」の構成を強くお勧めします。
+この方法は、オーディエンスが数人よりも多い場合にはお勧めできません。カスタム属性の最大文字数は255文字であるため、この方法では数十または数百のオーディエンスを1つのユーザープロファイルに保存することはできません。ユーザーごとに多くのコホートがある場合は、「1属性ごとに1Segment」の構成を強くお勧めします。
 {% endalert %}
 
-![mParticle Segment メンバーシップ][6]
+![mParticle セグメントのメンバーシップ][6]
 
 ##### 単一配列属性 {#array}
 
 mParticleは、各ユーザーに対してBrazeに単一のカスタム配列属性を作成し、それを`SegmentMembershipArray`と呼びます。この属性の値は、ユーザーに一致するmParticleオーディエンスIDの配列です。
 
-例えば、ユーザーが3つのmParticleオーディエンス（オーディエンスIDが「13053」、「13052」、「13051」）のメンバーである場合、`SegmentMembershipArray` — `includes value` — `13051`のフィルターを使用して、それらのオーディエンスのいずれかに一致するユーザーをセグメント化できます。
+たとえば、ユーザーが「13053」、「13052」、および「13051」というオーディエンス ID を持つ3つのmParticleオーディエンスのメンバーである場合、それらのオーディエンスの1つに一致するユーザーを、フィルター `SegmentMembershipArray` — `includes value` — `13051`でセグメント化できます。
 
 {% alert note %}
-Braze 配列属性の最大長は 25 です。ユーザーが25以上のオーディエンスのメンバーである場合、Brazeによってメンバーシップ情報が切り捨てられます。これを回避するには、Brazeの担当者に連絡して、最大配列長のしきい値を増やしてください。
+Braze 配列属性の最大長は 25 です。ユーザーがメンバーとなっているオーディエンスが25を超える場合には、Braze によってメンバーシップ情報が切り捨てられます。これを回避するには、Brazeの担当者に連絡して、最大配列長のしきい値を増やしてください。
 {% endalert %}
 
 ##### セグメント{#per-segment}ごとに1つの属性
 
-mParticleは、ユーザーが属する各オーディエンスに対してブール値のカスタム属性を作成します。例えば、mParticleのオーディエンスが「Possible Parisians」と呼ばれる場合、これらのユーザーを`In Possible Parisians` - `equals` - `true`のフィルターでSegmentできます。
+mParticleは、ユーザーが属する各オーディエンスに対してブール値のカスタム属性を作成します。たとえば、「Possible Parisians」という mParticle オーディエンスの場合、フィルター `In Possible Parisians` - `equals` - `true` でこれらのユーザーをセグメント化できます。
 
 ![mParticleカスタム属性][7]
 
@@ -83,17 +83,17 @@ mParticleは、単一の配列属性と単一の文字列属性の両方で説
 
 ##### 単一の配列属性とセグメントごとの1つの属性{#both-2}
 
-mParticleは、単一の配列属性とセグメントごとの1つの属性の両方で説明されているように属性を送信します。
+mParticle は、単一配列属性とセグメントごとに1つの属性の両方によって記述されている属性を送信します。
 
 ##### 単一の文字列属性とセグメントごとの1つの属性{#both-3}
 
 mParticleは、単一の文字列属性とセグメントごとの1つの属性の両方で説明されているように属性を送信します。
 
-##### 単一の配列属性、単一の文字列属性、およびセグメント{#multi}ごとの1つの属性
+##### 単一配列属性、単一文字列属性、およびセグメントごとの1つの属性 {#multi}
 
 mParticleは、単一の配列属性、単一の文字列属性、およびセグメントごとの1つの属性として記述されている属性を送信します。
 
-#### ステップ1:mParticleでオーディエンスを作成する {#send_settings}
+#### ステップ1:mParticle でオーディエンスを作成する {#send_settings}
 
 mParticleでオーディエンスを作成するには:
 
@@ -105,31 +105,31 @@ mParticleでオーディエンスを作成するには:
 | API キー                  | Brazeのダッシュボードの**設定** > **APIキー**にあります。<br><br>古いナビゲーションを使用している場合は、**開発者コンソール** > **API設定**でAPIキーを見つけることができます。 |
 | API キー オペレーティングシステム | どのオペレーティングシステムがあなたのBraze APIキーに対応しているかを選択してください。この選択は、オーディエンス更新で転送されるプッシュトークンの種類を制限します。                          |
 | セグメントとして送信         | Brazeにオーディエンスを送信する方法。詳細については、セクション[Forwarding audiences](#forwarding-audiences)を参照してください。                                                          |
-| ワークスペース REST APIキー   | Braze REST APIキー with full permissions.これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。                                                        |
-| 外部アイデンティティタイプ   | mParticleのユーザーIDタイプを外部IDとしてBrazeに転送します。これをデフォルト値のままにしておくことをお勧めします、顧客ID。                                          |
-| メールアイデンティティタイプ      | mParticleのユーザーIDタイプをメールとしてBrazeに転送します。                                                                                                            |
+| ワークスペース REST APIキー   | すべての権限を持つ Braze REST API キー。これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。                                                        |
+| External identity type   | external ID として Braze に転送する mParticle のユーザー ID タイプ。これはデフォルト値の Customer ID のままにすることをお勧めします。                                          |
+| Email identity type      | メールとして Braze に転送する mParticle のユーザー ID タイプ。                                                                                                            |
 | Brazeインスタンス           | どのクラスターにBrazeデータを転送するか指定します。                                                                                                                   |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {:start="3"}
-3\.最後に**オーディエンス**を保存します。
+3\.最後にオーディエンスを**保存**します。
 
-数分以内にBrazeにオーディエンスの同期が開始されるはずです。オーディエンスメンバーシップは、`external_ids`（つまり、匿名ユーザーではない）を持つユーザーに対してのみ更新されます。Braze mParticleオーディエンスの作成に関する詳細は、mParticleの[設定](https://docs.mparticle.com/integrations/braze/audience/#configuration-settings)に関するドキュメントを参照してください。
+数分以内にオーディエンスが Braze に同期されることが示されます。オーディエンスのメンバーシップは、`external_ids` が設定されているユーザー （つまり匿名ユーザーではないユーザー） に対してのみ更新されます。Braze mParticle オーディエンスの作成の詳細については、mParticle の[構成設定](https://docs.mparticle.com/integrations/braze/audience/#configuration-settings)に関するドキュメントを参照してください。
 
-#### ステップ2:Brazeでセグメントユーザー
+#### ステップ2:Braze でユーザーをセグメント化する
 
 Braze でこれらのユーザーのセグメントを作成するには、**Segments** の **エンゲージメント** に移動し、セグメントに名前を付けます。次のものは、**セグメントを送信する**ために選択したオプションに応じた2つのセグメントの例です。各オプションの詳細については、[転送オーディエンス](#forwarding-audiences.)を参照してください。
 
-- **単一の配列属性:**`SegmentMembershipArray`をフィルターとして選択します。次に、「値を含む」オプションを使用して、希望するオーディエンスIDを入力します。 ![mParticle Segment フィルター「SegmentMembershipArray」を「値を含む」として設定し、オーディエンスIDを入力します。][11]<br><br>
+- **単一配列属性:**`SegmentMembershipArray`をフィルターとして選択します。次に、\[値を含む] オプションを使用して目的のオーディエンス ID を入力します。![「値を含む」とオーディエンス ID が設定されている mParticle セグメントフィルター「SegmentMembershipArray」。][11]<br><br>
 - **セグメントごとに1つの属性:**カスタム属性をフィルターとして選択します。次に、「等しい」オプションを使用し、適切なロジックを選択します。![mParticle Segment フィルター「in possible parisians」を「等しい」と「true」に設定します。][8]
 
 保存すると、キャンバスやキャンペーンの作成時にターゲットユーザーのステップでこのSegmentを参照できます。
 
 #### 接続の無効化と削除
 
-mParticleはBraze内のセグメントを直接管理しないため、対応するmParticleオーディエンス接続が削除または無効化された場合でも、セグメントは削除されません。このような場合、mParticleはBrazeのオーディエンスユーザー属性を更新せず、各ユーザーからオーディエンスを削除しません。
+mParticleはBraze内のセグメントを直接管理しないため、対応するmParticleオーディエンス接続が削除または無効化された場合でも、セグメントは削除されません。この場合、mParticle は各ユーザーからオーディエンスを除去するために Braze でオーディエンスユーザー属性を更新しません。
 
-Brazeユーザーからオーディエンスを削除するには、オーディエンスを削除する前にオーディエンスフィルターを調整してオーディエンスサイズを0にします。オーディエンスの計算が完了して0人のユーザーが返された後、オーディエンスを削除します。次に、オーディエンスメンバーシップは、単一の属性オプションの場合は`false`に更新され、または配列形式からオーディエンスIDが削除されます。
+削除前に Braze ユーザーからオーディエンスを除去するには、オーディエンスフィルターを調整してオーディエンスのサイズを強制的に0にしてから、オーディエンスを削除します。オーディエンスの計算が完了して0人のユーザーが返された後に、オーディエンスを削除します。次に、単一属性オプションの場合は Braze でオーディエンスのメンバーシップが `false` に更新されるか、配列形式からオーディエンス ID が削除されます。
 
 ## データマッピング
 
@@ -139,13 +139,13 @@ Brazeユーザーからオーディエンスを削除するには、オーディ
 
 ### Brazeの出力設定を構成する
 
-mParticleで、**セットアップ > 出力 > 出力の追加**に移動し、**Braze**を選択してBrazeキットの構成を開封します。**保存** 完了したら。
+mParticleで、**セットアップ > 出力 > 出力の追加**に移動し、**Braze**を選択してBrazeキットの構成を開封します。完了したら**保存**します。
 
 | 設定名 | 説明 |
 | ------------ | ----------- |
 | Brazeアプリ識別子キー | Brazeアプリ識別子キーは、**設定** > **APIキー**のBrazeダッシュボードで見つけることができます。APIキーは各プラットフォーム（iOS、Android、Web）で異なることに注意してください。 |
-| 外部アイデンティティタイプ | mParticleのユーザーIDタイプを外部IDとしてBrazeに転送します。これをデフォルト値のままにしておくことをお勧めします、顧客ID |
-| メールアイデンティティタイプ | mParticleのユーザーIDタイプをメールとしてBrazeに転送します。これをデフォルト値のままにしておくことをお勧めします、メール、 |
+| External identity type | external ID として Braze に転送する mParticle のユーザー ID タイプ。これはデフォルト値の Customer ID のままにすることをお勧めします。 |
+| Email identity type | メールとして Braze に転送する mParticle のユーザー ID タイプ。これはデフォルト値の Email のままにすることをお勧めします。 |
 | Brazeインスタンス | Brazeデータが転送されるクラスター。これは、ダッシュボードがあるクラスターと同じである必要があります。 |
 | イベントストリーム転送を有効にする | （サーバー間）有効にすると、すべてのイベントがリアルタイムで転送されます。そうでない場合、すべてのイベントが一括で転送されます。イベントストリーム転送を有効にする場合、Braze に渡すデータが[レート制限]({{site.baseurl}}/api/basics/#api-limits)を尊重することを確認してください。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -154,11 +154,11 @@ mParticleで、**セットアップ > 出力 > 出力の追加**に移動し、*
 
 ### 組み込みキットの統合
 
-mParticleとBraze SDKは、埋め込みキット統合を通じてアプリケーションに存在します。ただし、直接のBraze統合とは異なり、mParticleはBraze SDKメソッドの大部分を呼び出すことを担当します。mParticleのメソッドを使用してユーザーデータを追跡すると、自動的にBrazeのSDKメソッドにマッピングされます。 
+mParticle と Braze SDK は、埋め込みキット統合によってアプリケーションに表示されます。ただし、直接の Braze 統合とは異なり、mParticle が Braze SDK のメソッドのほとんどの呼び出しを処理します。mParticleのメソッドを使用してユーザーデータを追跡すると、自動的にBrazeのSDKメソッドにマッピングされます。 
 
 これらのmParticleのSDKの[Android](https://github.com/mparticle-integrations/mparticle-android-integration-appboy)、[iOS](https://github.com/mparticle-integrations/mparticle-apple-integration-appboy)、[Web](https://github.com/Appboy/integration-appboy)のマッピングはオープンソースであり、[mParticleのGitHubページ](https://github.com/mparticle-integrations)で見つけることができます。 
 
-埋め込みキットSDKの統合により、フル機能スイート（プッシュ、アプリ内メッセージ、およびすべての関連するメッセージ分析トラッキング）を活用できます。
+埋め込みキット SDK 統合により、Braze のフルスイート機能 (プッシュ、アプリ内メッセージ、および関連するすべてのメッセージ分析トラッキング) を利用できます。
 
 {% alert note %}
 コンテンツカードとカスタムアプリ内メッセージの統合には、Braze SDKメソッドを直接呼び出します。
@@ -166,21 +166,21 @@ mParticleとBraze SDKは、埋め込みキット統合を通じてアプリケ
 
 #### ステップ1:mParticle SDKを統合する
 
-プラットフォームのニーズに基づいて、適切なmParticle SDKをアプリに統合します。
+プラットフォームのニーズに基づいて、適切な mParticle SDK をアプリに統合します。
 
-* [Android 用 mParticle](https://docs.mparticle.com/developers/sdk/android/getting-started/)
-* [iOS用mParticle](https://docs.mparticle.com/developers/sdk/ios/getting-started/)
-* [Web用mParticle](https://docs.mparticle.com/developers/sdk/web/getting-started/)
+* [mParticle for Android](https://docs.mparticle.com/developers/sdk/android/getting-started/)
+* [mParticle for iOS](https://docs.mparticle.com/developers/sdk/ios/getting-started/)
+* [mParticle for Web](https://docs.mparticle.com/developers/sdk/web/getting-started/)
 
-#### ステップ2:mParticleのBrazeイベントキット統合を完了する
+#### ステップ2:mParticle の Braze イベントキット統合を完了する
 
 このmParticle統合のためにBraze SDKをWebサイトやアプリに直接含める必要はありませんが、アプリからBrazeにデータを転送するために次のmParticle Appboy Kitをインストールする必要があります。
 
-mParticleの[Brazeイベントキット統合ガイド](https://docs.mparticle.com/integrations/braze/event/#kit-integration)は、メッセージングのニーズ（プッシュ、位置情報の追跡など）に基づいて、カスタムmParticleとBrazeの調整手順を案内します。
+mParticle の[Braze イベントキット統合ガイド](https://docs.mparticle.com/integrations/braze/event/#kit-integration)は、メッセージングのニーズ (プッシュ、位置情報の追跡など) に基づくカスタムの mParticle および Braze 調整手順を説明します。
 
-#### ステップ3:Braze出力の接続設定
+#### ステップ3:Braze 出力の接続の設定
 
-mParticleで、**接続 > 接続 > \[希望するプラットフォーム] > 出力を接続**して、Brazeを出力として追加します。**保存** 完了したら。
+mParticle で **\[Connections] > \[Connect] > \[\[目的のプラットフォーム]] > \[Connect Output]** に移動し、出力として Braze を追加します。完了したら**保存**します。
 
 ![][3]
 
@@ -188,19 +188,19 @@ mParticleで、**接続 > 接続 > \[希望するプラットフォーム] > 出
 
 ### サーバーAPI統合
 
-mParticleのサーバーサイドSDK（例えば、Ruby、Pythonなど）を使用している場合、バックエンドデータをBrazeにルーティングするためのアドオンです。このサーバー間統合をBrazeで設定するには、[mParticleのドキュメント](https://docs.mparticle.com/guides/platform-guide/connections/)に従ってください。
+mParticleのサーバーサイドSDK（例えば、Ruby、Pythonなど）を使用している場合、バックエンドデータをBrazeにルーティングするためのアドオンです。Braze でこのサーバー間統合を設定するには、[mParticle のドキュメント](https://docs.mparticle.com/guides/platform-guide/connections/)の説明に従ってください。
 
 {% alert important %}
-サーバー間統合は、アプリ内メッセージング、コンテンツカード、プッシュ通知などのBraze UI機能をサポートしていません。この方法では利用できないデバイスレベルのフィールドなど、自動的にキャプチャされたデータも存在します。 
+サーバー間統合では、アプリ内メッセージング、コンテンツカード、プッシュ通知などの Braze UI 機能はサポートされていません。この方法では利用できないデバイスレベルのフィールドなど、自動的にキャプチャされたデータも存在します。 
 
 これらの機能を使用したい場合は、並列統合を検討してください。
 
 サーバー側のデータをBrazeに転送するには、`external_id`を含める必要があります。匿名ユーザーは転送されません。
 {% endalert %}
 
-#### Braze出力の接続設定
+#### Braze 出力の接続の設定
 
-mParticleで、**接続 > 接続 > \[希望するプラットフォーム] > 出力を接続**して、Brazeを出力として追加します。**保存** 完了したら。 
+mParticle で **\[Connections] > \[Connect] > \[\[目的のプラットフォーム]] > \[Connect Output]** に移動し、出力として Braze を追加します。完了したら**保存**します。 
 
 ![][4]
 
@@ -216,7 +216,7 @@ mParticleで、**接続 > 接続 > \[希望するプラットフォーム] > 出
 - [カスタム属性]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/)は文字列、数値、ブール値、日付オブジェクト、および配列をサポートしますが、オブジェクトやネストされたオブジェクトはサポートしません。 
 
 {% alert note %}
-Brazeは`Time`タイプのカスタム属性で0年以前または3000年以降のタイムスタンプをサポートしていません。BrazeはmParticleによって送信されたこれらの値を取り込みますが、その値は文字列として保存されます。
+Braze は `Time` タイプのカスタム属性で0年以前または3000年以降のタイムスタンプをサポートしていません。Braze は、これらの値が mParticle によって送信されると値を取り込みますが、値は文字列として保存されます。
 {% endalert %}
 
 #### データマッピング
@@ -224,48 +224,48 @@ Brazeは`Time`タイプのカスタム属性で0年以前または3000年以降
 | mParticle データ タイプ | Brazeデータ型 | 説明 |
 | ------------------- | --------------- | ----------- |
 | ユーザー属性（予約済み） | 標準属性項目 | 例えば、mParticleの`$FirstName`予約ユーザー属性キーは、Brazeの`first_name`標準属性項目フィールドにマッピングされます。 |
-| ユーザー属性（その他） | カスタム属性 | mParticle に渡される予約済みユーザー属性キーの範囲外のユーザー属性は、Braze にカスタム属性として記録されます。<br><br>ユーザー属性は文字列、数値、ブール値、日付、および配列をサポートしますが、オブジェクトやネストされたオブジェクトはサポートしません。 |
+| ユーザー属性（その他） | カスタム属性 | mParticle に渡されたユーザー属性が、予約済みのユーザー属性キーの範囲外にある場合、そのユーザー属性はカスタム属性として Braze に記録されます。<br><br>ユーザー属性は文字列、数値、ブール値、日付、および配列をサポートしますが、オブジェクトやネストされたオブジェクトはサポートしません。 |
 | カスタムイベント | カスタムイベント | mParticleカスタムイベントはBrazeによってカスタムイベントとして認識されます。イベント属性はカスタムイベントプロパティとして転送されます。<br><br>イベントプロパティとしてBrazeに渡されるイベント属性は、文字列、数値、ブール値、または日付オブジェクトをサポートしますが、配列やネストされたオブジェクトはサポートしません。 |
-| 購入コマースイベント | 購入イベント | 購入コマースイベントはBraze購入イベントにマッピングされます。<br><br>バンドルコマースイベントデータの設定値を切り替えて、注文レベルまたは製品レベルで購入を記録します。例えば、`false`、2つのユニークな製品、プロモーション、またはインプレッションを含む単一の受信イベントは、少なくとも2つの送信Brazeイベントをもたらします。設定を`true`にすると、ネストされた製品、プロモーション、またはインプレッションの配列を持つ単一の送信イベントが生成されます。<br><br>追加のコマースフィールドのログに関する詳細については、[mParticleのドキュメント](https://docs.mparticle.com/integrations/braze/event/#purchase-events)を参照してください。<br><br>「バンドルコマースイベントデータ」を`false`として設定する場合、製品属性は購入イベントプロパティとしてBrazeに渡され、文字列、数値、ブール値、または日付オブジェクトがサポートされますが、配列やネストされたオブジェクトはサポートされません。|
-| 他のすべての商取引イベント | カスタムイベント | 他のすべての商取引イベントはカスタムイベントにマッピングされます。<br><br>バンドルコマースイベントデータの設定値を切り替えて、注文レベルまたは製品レベルで購入を記録します。例えば、`false`、2つのユニークな製品、プロモーション、またはインプレッションを含む単一の受信イベントは、少なくとも2つの送信Brazeイベントをもたらします。設定を`true`にすると、ネストされた製品、プロモーション、またはインプレッションの配列を持つ単一の送信イベントが生成されます。<br><br>特定のデフォルトコマース値に加えて、製品属性はBrazeイベントプロパティとして記録されます。追加のコマースフィールドのログ記録に関する詳細については、[mParticleのドキュメント](https://docs.mparticle.com/integrations/braze/event/#other-commerce-events)を参照してください。<br><br>「バンドルコマースイベントデータ」を`false`製品属性としてBrazeにイベントプロパティとして渡す場合、文字列、数値、ブール値、または日付オブジェクトをサポートしますが、配列やネストされたオブジェクトはサポートしません。 |
+| 購入コマースイベント | 購入イベント | 購入コマースイベントは Braze の購入イベントにマッピングされます。<br><br>バンドルコマースイベントデータの設定値を切り替えて、注文レベルまたは製品レベルで購入を記録します。たとえば `false` の場合、2つの一意の製品、プロモーション、またはインプレッションを含む1つの受信イベントでは、少なくとも2つの送信 Braze イベントが生成されます。`true` に設定すると、ネストされた製品、プロモーション、またはインプレッションの配列を含む1つの送信イベントが生成されます。<br><br>ログに記録される追加のコマースフィールドの詳細については、[mParticle のドキュメント](https://docs.mparticle.com/integrations/braze/event/#purchase-events)を参照してください。<br><br>「バンドルコマースイベントデータ」を `false` として設定する場合、購入イベントプロパティとして Braze に渡される製品属性では、文字列、数値、ブール値、または日付オブジェクトがサポートされますが、配列やネストされたオブジェクトはサポートされません。|
+| その他のすべてのコマースイベント | カスタムイベント | 他のすべての商取引イベントはカスタムイベントにマッピングされます。<br><br>バンドルコマースイベントデータの設定値を切り替えて、注文レベルまたは製品レベルで購入を記録します。たとえば `false` の場合、2つの一意の製品、プロモーション、またはインプレッションを含む1つの受信イベントでは、少なくとも2つの送信 Braze イベントが生成されます。`true` に設定すると、ネストされた製品、プロモーション、またはインプレッションの配列を含む1つの送信イベントが生成されます。<br><br>特定のデフォルトコマース値に加えて、製品属性が Braze イベントプロパティとして記録されます。ログに記録される追加のコマースフィールドの詳細については、[mParticle のドキュメント](https://docs.mparticle.com/integrations/braze/event/#other-commerce-events)を参照してください。<br><br>「バンドルコマースイベントデータ」を `false` として設定する場合、イベントプロパティとして Braze に渡される製品属性では、文字列、数値、ブール値、または日付オブジェクトがサポートされますが、配列やネストされたオブジェクトはサポートされません。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 #### ユーザーアイデンティティマッピング
-各mParticle出力について、`external_id`としてBrazeに送信する外部IDタイプを選択できます。デフォルト値は顧客IDですが、`MPID`などの別のIDをBrazeに`external_id`として送信するようにマッピングすることもできます。識別子以外の顧客IDを選択すると、Brazeに送信されるデータに影響を与える可能性があることに注意してください。 
+各mParticle出力について、`external_id`としてBrazeに送信する外部IDタイプを選択できます。デフォルト値は顧客IDですが、`MPID`などの別のIDをBrazeに`external_id`として送信するようにマッピングすることもできます。顧客 ID 以外の識別子を選択すると、Braze でのデータの送信方法に影響する場合があることに注意してください。 
 
 例えば、MPIDをBraze `external_id`にマッピングすると、次のような効果があります:
 - MPIDが割り当てられるタイミングの性質上、すべてのユーザーはセッション開始時に`external_id`が割り当てられます。
-- Currentsのセットアップには、MPIDと`external_id`の間でデータ型が異なるため、追加のマッピングが必要な場合があります。
+- MPID と `external_id` のデータ型が異なるため、Currents の設定で追加のマッピングが必要になる場合があります。
 
-### 消去要求の転送（データ主体の要求）
+### 消去要求 (データ主体の要求) の転送
 
-Brazeにデータ主体リクエスト出力を設定して、消去リクエストをBrazeに転送します。消去リクエストをBrazeに転送するには、[mParticleのドキュメント](https://docs.mparticle.com/integrations/braze/forwarding-dsr/)に従ってください。
+Braze へ消去要求を転送するには、Braze へのデータ主体要求出力を設定します。消去要求を Braze に転送するには、[mParticle のドキュメント](https://docs.mparticle.com/integrations/braze/forwarding-dsr/)の説明に従います。
 
 ## 潜在的なデータポイントの超過
 
 ### 強化されたユーザー属性
 
-#### ユーザー属性/アイデンティティの有効化（サーバー間のみ）{#enriched}
+#### ユーザー属性/識別子の強化を有効にする (サーバー間のみ) {#enriched}
 
 mParticle接続設定では、Brazeは**拡張ユーザー属性を含める**をオフにすることを推奨します。有効にすると、mParticleは、既存のプロファイルから利用可能なすべてのユーザー属性（標準属性、カスタム属性、計算された属性など）を各ログイベントでBrazeに転送します。これにより、mParticleが各呼び出しで同じ変更されていない属性をBrazeに送信するため、データポイントの消費が多くなります。
 
-例えば、ユーザーが最初のセッション中に名、姓、電話番号を追加し、後で同じ情報に加えてメールを追加してニュースレターにサインアップする場合、ニュースレターのサインアップイベントがトリガーされます。
+たとえば、ユーザーが最初のセッションで名、姓、電話番号を追加し、その後、同じ情報とメールを追加してニュースレターに登録すると、ニュースレター登録イベントがトリガーされるとします。
 - オンにすると（デフォルト）、FIVEつのデータポイントが発生します。（サインアップイベント、メールアドレス、名、姓、電話番号）
 - オフにすると、2つのデータポイント（サインアップイベントとメールアドレス）が発生します
 
 {% alert note %}
-この設定をオフにすると、データの変更をチェックしません。ただし、統合が元のインバウンドバッチで受信されなかったか、イベントの属性として明示的に設定されていないユーザーのプロファイル上のすべてのユーザー属性を送信するのを防ぎます。依然としてデルタのみがBrazeに渡されることを確認することが重要です。
+この設定をオフにすると、データの変更はチェックされません。ただし、統合が元のインバウンドバッチで受信されなかったか、イベントの属性として明示的に設定されていないユーザーのプロファイル上のすべてのユーザー属性を送信するのを防ぎます。差分のみが Braze に渡されることを確認することが重要です。
 {% endalert %}
 
 #### 強化されたユーザー属性をオフにすることの考慮事項
 
 **リッチユーザー属性を含める**をオフにする際に注意すべき点がいくつかあります:
-1. サーバー間統合はmParticleイベントAPIを使用してイベントをBrazeに送信します。各リクエストはイベントによってトリガーされます。ユーザー属性が変更されたとき、例えばメールアドレスの更新など、特定のイベントに関連付けられていない場合（例えば、プロファイル更新カスタムイベント）、新しい値はユーザーによってトリガーされた次のイベントのペイロード内の「強化された属性」としてBrazeのような出力にのみ渡されます。**Include Enriched User Attributes**がオフになっている場合、この新しい属性値は特定のイベントに関連付けられていないため、Brazeに渡されません。
-  - これを解決するために、更新された特定のユーザー属性のみをBrazeに送信する「ユーザー属性更新」イベントを別途作成することをお勧めします。このアプローチでは、「ユーザー属性更新」イベントの追加のデータポイントを記録していますが、機能が有効になっているすべての呼び出しでユーザー属性をすべて送信するよりも、データポイントの消費は大幅に少なくなります。
+1. サーバー間統合はmParticleイベントAPIを使用してイベントをBrazeに送信します。各リクエストはイベントによってトリガーされます。メールアドレスの更新など、ユーザー属性が変更されても、そのユーザー属性が特定のイベント (プロファイル更新カスタムイベントなど) に関連付けられていない場合、新しい値は、ユーザーによってトリガーされる次のイベントのペイロードで「強化属性」として Braze などの出力に渡されるだけです。**Include Enriched User Attributes**がオフになっている場合、この新しい属性値は特定のイベントに関連付けられていないため、Brazeに渡されません。
+  - これを解決するために、更新された特定のユーザー属性のみをBrazeに送信する「ユーザー属性更新」イベントを別途作成することをお勧めします。この方法では、「ユーザー属性更新」イベントの追加データポイントは記録されますが、データポイントの消費は、この機能が有効になっておりすべての呼び出しですべてのユーザー属性が送信される場合よりもはるかに少なくなることに注意してください。
 2. 計算された属性は、強化されたユーザー属性としてBrazeに渡されるため、「強化されたユーザー属性」がオフになると、これらはもはやBrazeに渡されません。「強化されたユーザー属性」がオフになっている場合、すべての属性をプッシュすることなく、[計算された属性フィード](https://docs.mparticle.com/guides/platform-guide/calculated-attributes/using-calculated-attributes/#forward-calculated-attributes-in-the-calculated-attributes-feed)がBrazeに計算された属性を転送するのに役立ちます。計算された属性が変更されると、フィードはBrazeに下流の更新を送信します。 
 
 ### Brazeに不要または重複するデータを送信する
-Brazeは、値が変更されていない場合でも、属性がBrazeに渡されるたびにデータポイントをカウントします。このため、BrazeはBraze内でアクションを実行するために必要なデータのみを転送し、属性のデルタのみが渡されることを確認することを推奨します。
+Brazeは、値が変更されていない場合でも、属性がBrazeに渡されるたびにデータポイントをカウントします。このため、Braze 内でアクションを実行するために必要なデータのみを転送し、属性の差分のみが渡されるようにすることが推奨されます。
 
 [1]: https://dashboard.braze.com/app_settings/developer_console
 [2]: {% image_buster /assets/img_archive/dashboard_keys_locations.png %}
@@ -277,4 +277,4 @@ Brazeは、値が変更されていない場合でも、属性がBrazeに渡さ
 [9]: {% image_buster /assets/img_archive/mparticle4.png %}
 [10]: {% image_buster /assets/img_archive/configure_settings.png %}
 [11]: {% image_buster /assets/img_archive/mparticle5.png %}
-[5]: \#組み込みキット統合
+[5]: \#embedded-kit-integration
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents.md
index 7f5cf1593e4..04cdc5778fb 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents.md
@@ -1,6 +1,6 @@
 ---
-nav_title: 電流用m粒子
-article_title: 電流用m粒子
+nav_title: mParticle と Currents
+article_title: mParticle と Currents
 alias: /partners/mparticle_for_currents/
 description: "この参考記事では、Braze Currentsと、マーケティング・スタック内のソース間で情報を収集し、ルーティングする顧客データ・プラットフォームであるmParticleとのパートナーシップについて概説している。"
 page_type: partner
@@ -9,71 +9,71 @@ search_tag: Partner
 
 ---
 
-# 電流用m粒子
+# mParticle と Currents
 
-> [mParticleは](https://www.mparticle.com)、複数のソースから情報を収集し、マーケティング・スタックの他のさまざまな場所にルーティングする顧客データ・プラットフォームである。
+> [mParticle](https://www.mparticle.com) は、複数のソースから情報を収集し、マーケティングスタックの他のさまざまな場所に情報をルーティングする顧客データプラットフォームです。
 
-BrazeとmParticleの統合により、2つのシステム間の情報の流れをシームレスに制御できる。Currentsを使えば、データをmParticleに接続し、成長スタック全体で実行可能にすることもできる。 
+BrazeとmParticleの統合により、2つのシステム間の情報の流れをシームレスに制御できる。Currents では、データを mParticle に接続し、グローススタック全体で実用的なデータにすることもできます。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| mパーティクルアカウント | このパートナーシップを利用するには、[mParticleのアカウントが](https://app.mparticle.com/login)必要である。 |
-| Currents | データをmParticleにエクスポートするには、アカウントに[Braze Currentsを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents)設定する必要がある。 |
-| mParticleサーバーからサーバーへのキー<br><br>mParticleサーバー間の秘密 | これらは、mParticleのダッシュボードに移動し、mParticleがiOS、Android、およびWebプラットフォーム用のBraze相互作用データを受信できるようにするために[必要なフィードを](#step-1-create-feeds)作成することで取得できる。|
+| mParticle アカウント | このパートナーシップを活用するには、[mParticle アカウント](https://app.mparticle.com/login)が必要です。 |
+| Currents | mParticle にデータを再度エクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
+| mParticleサーバーからサーバーへのキー<br><br>mParticle サーバー間シークレット | これらを取得するには、mParticle ダッシュボードに移動し、mParticle が iOS、Android、および Web プラットフォームの Braze インタラクションデータを受信できるようにするために[必要なフィード](#step-1-create-feeds)を作成します。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:フィードを作成する
 
-mParticleの管理者アカウントから、**「設定」>「入力**」に移動する。mParticle**ディレクトリで** **Brazeを**見つけ、フィード統合を追加する。
+mParticle 管理者アカウントから、**\[Setup] > \[Inputs]** に移動します。mParticle**Directory** で **Braze** を見つけ、フィード統合を追加します。
 
-Brazeのフィード統合は、iOS、Android、Web、Unboundの4つのフィードに対応している。バインドされていないフィードは、プラットフォームに接続されていない電子メールなどのイベントに使用できる。各メイン・プラットフォーム・フィードの入力を作成する必要がある。**Setup > Inputsの** **Feed Configurations**タブで追加入力を作成できる。
+Braze フィード統合は、iOS、Android、Web、Unbound の4つのフィードをサポートしています。バインドされていないフィードは、プラットフォームに接続されていない電子メールなどのイベントに使用できる。メインプラットフォームフィードごとに入力を作成する必要があります。\[**Feed Configurations**] タブの **\[Setup] > \[Input]** から追加の入力を作成できます。
 
 ![][1]
 
-各フィードについて、**「Act as Platform**」で、一致するプラットフォームをリストから選択する。**act-as**フィードを選択するオプションが表示されない場合、データは結合されていないものとして扱われるが、データウェアハウスの出力に転送することは可能である。
+フィードごとに、\[**Act as Platform**] で対応するプラットフォームをリストから選択します。**act-as**フィードを選択するオプションが表示されない場合、データは結合されていないものとして扱われるが、データウェアハウスの出力に転送することは可能である。
 
-![最初の統合ダイアログボックスが表示され、設定名を入力し、フィードのステータスを決定し、動作するプラットフォームを選択するよう促される。][2]{: style="max-width:40%;"} ![サーバー間キーとサーバー間シークレットを示す2つ目の統合ダイアログボックス。][3]{: style="max-width:37%;"}
+![設定名を入力し、フィードのステータスを決定し、act as platform を選択することを求める最初の統合ダイアログボックス。][2]{: style="max-width:40%;"} ![サーバー間キーとサーバー間シークレットを示す2つ目の統合ダイアログボックス。][3]{: style="max-width:37%;"}
 
-各入力を作成すると、mParticleはキーとシークレットを提供する。これらのクレデンシャルをコピーし、各クレデンシャルのペアがどのフィードのものであるかをメモしておくこと。
+各入力を作成すると、mParticleはキーとシークレットを提供する。これらの認証情報をコピーし、各認証情報のペアがどのフィードのものであるかをメモしておいてください。
 
-### ステップ2:電流を作る
+### ステップ2:Current を作成する
 
-Brazeで、**Current > + Create Current > Create mParticle Exportに**移動する。統合名、連絡先メールアドレス、各プラットフォームのmParticle APIキーとmParticleシークレットキーを入力する。次に、追跡したいイベントを選択する。利用可能なイベントのリストが提供される。最後に、**Launch Currentを**クリックする。
+Braze で **\[Currents] > \[+ Currents を作成] > \[mParticle エクスポートを作成]** に移動します。統合名、連絡先メールアドレス、各プラットフォームの mParticle API キーと mParticle シークレットキーを入力します。次に、追跡したいイベントを選択する。利用可能なイベントのリストが提供される。最後に \[**Currents を起動**] をクリックします。
 
-![BrazeのmParticle Currentsページ。] （{% image_buster /assets/img_archive/currents-mparticle-edit.png %} ）。
+![BrazeのmParticle Currentsページ。統合名、連絡先メール、API キー、シークレットキーのフィールドがある。]({% image_buster /assets/img_archive/currents-mparticle-edit.png %})
 
 {% alert important %}
-mParticle API KeyとmParticle Secret Keyを最新の状態に保つことが重要で、コネクタの認証情報が期限切れになると、コネクタはイベントの送信を停止する。この状態のまま **48 時間**を超えると、コネクターのイベントがドロップし、データが永久に喪失します。
+mParticle API キーと mParticle シークレットキーを最新の状態に維持することが重要です。コネクターの認証情報の有効期限が切れると、コネクターはイベントの送信を停止します。この状態のまま **48 時間**を超えると、コネクターのイベントがドロップし、データが永久に喪失します。
 {% endalert %}
 
-mParticleに送信されるすべてのイベントには、`customerid` としてユーザーの`external_user_id` が含まれる。現時点では、Brazeは、`external_user_id` を設定していないユーザーのイベントデータを送信しない。mParticleの`external_user_id` 、デフォルトの`customerid` 以外のIDにマッピングしたい場合は、Braze CSMに連絡すること。 
+mParticleに送信されるすべてのイベントには、ユーザーの `external_user_id` が `customerid` として含まれます。現時点では、Brazeは、`external_user_id` を設定していないユーザーのイベントデータを送信しない。mParticle で、デフォルトの `customerid` ではない別の ID に `external_user_id` をマッピングする場合は、Braze カスタマーサクセスマネージャーにお問い合わせください。 
 
-## 百花繚乱イベントをサポート
+## サポートされている Currents イベント
 
 Brazeは、Currentsの[ユーザー行動]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)および[メッセージエンゲージメントイベントの]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)用語集に記載されている以下のデータをmParticleにエクスポートすることをサポートしている：
 
 ### 行動
-- アンインストールする： `users.behaviors.Uninstall`
+- アンインストール: `users.behaviors.Uninstall`
 - サブスクリプション（グローバルな状態変更）： `users.behaviors.subscription.GlobalStateChange`
 - サブスクリプション・グループ（状態変更）： `users.behaviors.subscriptiongroup.StateChange`
   
 ### キャンペーン
-- 中止する： `users_campaigns_abort`
-- コンバージョンだ： `users.campaigns.Conversion`
-- エンローリンコントロール `users.campaigns.EnrollInControl`
+- 中止: `users_campaigns_abort`
+- コンバージョン: `users.campaigns.Conversion`
+- EnrollinControl: `users.campaigns.EnrollInControl`
   
 ### キャンバス
-- 中止する： `users_canvas_abort`
-- コンバージョンだ： `users.canvas.Conversion`
-- エントリーする： `users.canvas.Entry`
-- 退場（マッチした観客、行われたイベント）
+- 中止: `users_canvas_abort`
+- コンバージョン: `users.canvas.Conversion`
+- エントリ:: `users.canvas.Entry`
+- 離脱 (オーディエンス照合、実行済みのイベント)
   - `users.canvas.exit.MatchedAudience`
   - `users.canvas.exit.PerformedEvent`
-- 実験ステップ（コンバージョン、スプリット・エントリー）
+- 実験ステップ (コンバージョン、分割エントリ)
   - `users.canvas.experimentstep.Conversion`
   - `users.canvas.experimentstep.SplitEntry`
 
@@ -84,12 +84,12 @@ Brazeは、Currentsの[ユーザー行動]({{site.baseurl}}/user_guide/data_and_
   - `users.messages.contentcard.Dismiss`
   - `users.messages.contentcard.Impression`
   - `users.messages.contentcard.Send`
-- 電子メール（中止、バウンス、クリック、配信、マークアスパム、開封、送信、ソフトバウンス、購読解除）
+- メール (中止、バウンス、クリック、配信、スパムとしてマーク、開封、送信、ソフトバウンス、配信停止)
 - アプリ内メッセージ（中止、クリック、インプレッション）
   - `users.messages.inappmessage.Abort`
   - `users.messages.inappmessage.Click`
   - `users.messages.inappmessage.Impression`
-- プッシュ通知（中止、バウンス、開封、送信）
+- プッシュ通知 (中止、バウンス、開封、送信)
   - `users.messages.pushnotification.Abort`
   - `users.messages.pushnotification.Bounce`
   - `users.messages.pushnotification.Open`
@@ -114,7 +114,7 @@ Brazeは、Currentsの[ユーザー行動]({{site.baseurl}}/user_guide/data_and_
   - `users.messages.whatsapp.Send`
 
 
-mParticleの統合についての詳細は、[こちらの](http://docs.mparticle.com/integrations/braze/feed)ドキュメントを参照されたい。
+mParticle 統合の詳細については、[こちらのドキュメント](http://docs.mparticle.com/integrations/braze/feed)を参照してください。
 
 [1]: {% image_buster /assets/img/braze-feed-inputs.png %}
 [2]: {% image_buster /assets/img/braze-feed-act1.png %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mparticle.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mparticle.md
index 8c8f29a6187..6abf5412ba0 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mparticle.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/mparticle.md
@@ -3,13 +3,13 @@ nav_title: mParticle
 noindex: true
 layout: dev_guide
 guide_top_header: "mParticle"
-guide_top_text: "mParticleの顧客データプラットフォームは、データを活用する力を高めます。洗練されたマーケターは、mParticleを使用して成長スタック全体にわたるデータを調整し、カスタマージャーニーの重要な瞬間で勝利を収めることができます。"
-description: "このランディングページは、統合ガイダンスやmParticle for Currentsを含む、mParticleに関するすべてのもののホームです。"
+guide_top_text: "mParticle の顧客データプラットフォームは、データの有効活用を支援しています。熟練したマーケターは、mParticle で成長スタック全体のデータのオーケストレーションを行い、カスタマージャーニーの重要なタイミングで適切な行動を取ることができます。"
+description: "このランディングページは、統合ガイダンスや mParticle と Currents など、mParticle に関するあらゆる情報のホームページです。"
 guide_featured_list:
 - name: mParticle
   link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/mparticle/mparticle
   image: /assets/img/braze_icons/user-circle.svg
-- name: mParticle for Currents
+- name: mParticle と Currents
   link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/mparticle/mparticle_for_currents/
   image: /assets/img/braze_icons/building-01.svg
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/octolis.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/octolis.md
index bcc90b03b1b..65fc4a86c6f 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/octolis.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/octolis.md
@@ -1,18 +1,18 @@
 ---
-nav_title: オクトリス
-article_title: オクトリス
-description: "このリファレンス記事では、Braze と、データをBraze に統合できるデータアクティベーションプラットフォームであるOctolis の連携について説明します。"
+nav_title: Octolis
+article_title: Octolis
+description: "このリファレンス記事では、Braze と Octolis のパートナーシップについて説明します。Octolisはデータアクティベーションプラットフォームであり、データを Braze に統合できます。"
 alias: /partners/octolis/
 page_type: partner
 search_tag: Octolis
 
 ---
 
-# オクトリス
+# Octolis
 
 > [Octolis][0]は、強力なデータアクティベーションプラットフォーム(またはヘッドレスCDP)です。Octolisは、自分が所有するデータベースの上に座って、ビジネスツールでデータを統合、準備、スコア化、同期するための簡単な方法です。
 
-Braze とOctolis の統合は、未加工のデータソースとBraze間のミドルウェアとして機能し、オンラインとオフラインのさまざまなソースからデータを取得して統合することができます。
+Braze と Octolis の統合は、生データソースと Braze 間のミドルウェアとして機能します。これにより、オンラインとオフラインのさまざまなソースからデータを取得して統合できます。
 1. エスホップ、CRM、POSシステムなどの情報源からのデータを統一し、統合する。
 2. 正規化とスコア化
 3. 計算されたフィールドsと事象のBrazeへのリアルタイム同期
@@ -23,74 +23,74 @@ Braze とOctolis の統合は、未加工のデータソースとBraze間のミ
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| Octolisアカウント | この提携の前進タグeをとるには、オクトーリスの勘定が必要である。 |
+| Octolisアカウント | このパートナーシップを活用するには、Octolis アカウントが必要です。 |
 | Braze REST API キー | [**users.track**][1] 権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
-| Braze REST エンドポイント | [Your REST エンドポイント URL][2].エンドポイントは、インスタンスのBraze URL によって異なります。 |
-| Braze アプリボタン | アプリ 識別子ボタン。これは、** Braze Dashboard > Manage Settings > API Key** にあります。 |
+| Braze REST エンドポイント | [REST エンドポイント URL][2]。エンドポイントはインスタンスの Braze URL に応じて異なります。 |
+| Brazeアプリキー | アプリ識別子キー。これは、**Braze ダッシュボード > \[設定の管理] > \[API キー]** で確認できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-インテグレーションを開始する前に、コネクション、ソース、オーディエンスs、シンクに関する以下の節を参照してください。
+統合を開始する前に、接続、ソース、オーディエンス、および同期に関する以下のセクションを参照してください。
 
 詳細については、Octolis [Getting started][4]セクションを参照してください。
 
 ### ステップ1:Octolisをデータソースに接続する
 
-Braze に送信するには、少なくとも1 つの[オーディエンス][5] が作成されていることを確認する必要があります。オーディエンスは、いくつかのデータソースsを結合し、それらを調製ステップsにアプリし、計算されたフィールドsを加算します。
+Braze にデータを送信するには、少なくとも1つの[オーディエンス][5]を作成しておく必要があります。オーディエンスは、いくつかのデータソースsを結合し、それらを調製ステップsにアプリし、計算されたフィールドsを加算します。
 
-これらのオーディエンスsは、いくつかのデータソースsに基づいて構築する必要があります。ソースには、次のいずれかを指定できます。
+これらのオーディエンスは、さまざまなデータソースに基づいて作成する必要があります。ソースとして次のいずれかを使用できます。
 - Salesforce オブジェクト(取引先責任者、取引先など)
 - Zendesk オブジェクト(チケット)
 - SFTP 内のファイル(一部の連絡先を含むCSVファイル、イベントを含むJSON ファイルなど)
 - データベースのテーブル/ビュー。
-- システムの1 つが、webhookまたはAPI 呼び出しを介してレコードを送信します。
+- いずれかのシステムから、Webhook や API 呼び出しを通じてレコードが送信されます。
 
-### ステップ2:Brazeを送信先として追加する
+### ステップ2:Braze を宛先として追加する
 
-次に、Braze を新しい送信先として設定するには、メインスクリーン内のカレント送信先の上部で**\+ Add more** を選択し、利用可能なビジネスツールから**Braze** を選択します。
+次に、Braze を新しい宛先として設定するには、メイン画面の現在の宛先の上にある \[**\+ Add more**] を選択し、利用可能なビジネスツールから \[**Braze**] を選択します。
 
 ![][9]
 
 選択したら、以下を入力します。
 
 - Braze API キー:これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。
-- 時間ウィンドウ:オクトリスは与えられた時期にレート制限をアプリします。
-- リクエストボリューム:この期間内に実行できるリクエストの数。
-- カスタム属性s:ここで、Braze に送信する新しいフィールドs、その形式(文字列、整数、浮動小数点数)、およびsync に必要な** を指定します(いずれかを同期に必須にする場合)。
+- 時間ウィンドウ:Octolis は特定の期間にわたってレート制限を適用します。
+- Request volume:この期間内に実行できるリクエストの数。
+- カスタム属性s:ここで、Braze に送信する新しいフィールドs、その形式(文字列、整数、浮動小数点数)、および**sync に必要な**を指定します(いずれかを同期に必須にする場合)。
 
 ![][10]
 
-設定が完了すると、Braze は新しい送信先としてイヤーをホームスクリーンにアプリします。
+設定が完了すると、ホーム画面で新しい宛先として Braze が表示されます。
 
 ### ステップ3:新しい同期の作成
 
-メニューから**Syncs**をクリックし、右上の**Add sync**を選択します。以前に作成したオーディエンスから選択するオーディエンスを選択します。
-次に、送信先として**Braze**を選択し、データを送信するエンティティを選択します。
+メニューから**Syncs**をクリックし、右上の**Add sync**を選択します。以前に作成したオーディエンスから、使用するオーディエンスを選択します。
+次に、宛先として \[**Braze**] を選択し、データ宛先エンティティを選択します。
 
 ![][11]
 
-### ステップ4:出力設定設定s
+### ステップ4:出力設定を行う
 
-デフォルトでは、Braze は送信するすべての属性s を作成しますが、同期するフィールドs の一覧を文書化する必要があります。
+デフォルトでは、送信するすべての属性が Braze により作成されますが、同期するフィールドのリストを文書に記録しておく必要があります。
 
 ![][12]{: style="max-width:75%;"}
 
-設定 s フィールド s の具体的な定義を次に示します。
+設定フィールドの具体的な定義を次に示します。
 
 | フィールド | 説明 |
 | --- | --- |
-| オーディエンスの同期先はどこですか? | レコードを作成または更新するBrazeのエンティティ。 |
+| Where do you want to sync the audience to? | レコードを作成または更新するBrazeのエンティティ。 |
 | レコードを識別するために使用されるフィールドは? | フィールドは、レコードがすでにBrazeに存在する場合、Octolis を使用してレコードを識別します。 |
-| どのくらいの頻度で各レコードを送信しますか? | デフォルトでは、シンクはすべての統合(API、データベース、FTP)に対してインクリメンタルになります。つまり、最後の更新以降の新しい値のみが更新d になります。必要に応じて、定期的にテーブル全体を送信することもできます。開始時に、Octolisは完全なテーブルを送信します。 |
-| 同期するフィールドはどれですか? | オクトリスはs m アプリ ing をBraze フィールドする。使用可能なすべてのフィールドの一覧が、ドロップダウンメニューの耳にアプリします。計算フィールドをBrazeに送信するには、まず、Brazeエンティティ内に対応する列を作成したことを確認する必要があります。 |
-| オーディエンスをいつ同期しますか? | Brazeへの送信方法:手動、リアルタイム、またはプログラム  |
-| レコードが…のときに同期 | 作成:オプトインの場合、Brazeテーブルがマスタのままであることが大切です。フィールドが更新dのときに同期をトリガーしないようにします。<br><br>更新:一方、名 フィールドの場合は、顧客が新しいエントリを提供するたびに、Brazeテーブルのフィールドに更新できるようにする必要があります。 |
+| How often do you want to send each record? | デフォルトでは、すべての統合 (API、データベース、FTP) で同期は増分同期になります。つまり、最後の更新以降の新しい値のみが更新d になります。必要に応じて、定期的にテーブル全体を送信することもできます。開始時に、Octolisは完全なテーブルを送信します。 |
+| 同期するフィールドはどれですか? | Octolis と Braze のフィールドのマッピングです。使用可能なすべてのフィールドの一覧が、ドロップダウンメニューの耳にアプリします。計算フィールドをBrazeに送信するには、まず、Brazeエンティティ内に対応する列を作成したことを確認する必要があります。 |
+| オーディエンスをいつ同期しますか? | Braze へのデータの送信方法: 手動、リアルタイム、またはプログラムによる送信のいずれかです。  |
+| Sync when record is... | 作成:オプトインの場合、Braze テーブルがマスターのままであることが重要です。フィールドの更新時に Octolis が同期をトリガーしないようにします。<br><br>更新:一方で、たとえば名前フィールドの場合、顧客が新しいエントリを入力するたびに Braze テーブルのフィールドを更新できるようにすることがあります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-## マルチキー重複排除
+## 複数キーの重複排除
 
-重複排除は、複数のソース、特にオンラインおよびオフラインからのデータを調整する場合の重要な課題です。Octolisの高度なno-コードモジュールを使用すると、[deduplication][3]に複数のキーを使用できます。このモジュールは各マスターテーブルで使用できます。つまり、各エンティティにロジックを適合させることができます。
+重複排除は、複数のソース、特にオンラインおよびオフラインのソースのデータを照合する場合に大きな課題となります。Octolis の高度なノーコードモジュールにより、[重複排除][3]に複数のキーを使用できます。このモジュールは各マスターテーブルで使用できます。つまり、各エンティティにロジックを適合させることができます。
 
 [0]: http://octolis.com
 [1]: {{site.baseurl}}/api/endpoints/user_data/post_user_track/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/redpoint.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/redpoint.md
index e2a7112b9d2..5f4e44e3580 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/redpoint.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/redpoint.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Redpoint
 article_title: Redpoint 
-description: "BrazeインテグレーションへのRedpointにより、ファーストパーティデータを使用してBraze ユーザープロファイルをオンボードし、拡張することができます。"
+description: "Redpoint と Braze の統合により、ファーストパーティデータを使用して Braze ユーザープロファイルを登録および拡充できます。"
 alias: /partners/redpoint/
 page_type: partner
 search_tag: Redpoint
@@ -9,26 +9,26 @@ search_tag: Redpoint
 
 # Redpoint
 
-> [Redpoint][2] は、マーケター s に完全に統合されたキャンペーン オーケストレーション プラットフォームを提供するテクノロジプラットフォームです。Redpoint のセグメンテーション、スケジュール、およびオートメーション機能を活用して、CDP データがBraze にインポートされる方法と時期をコントロールします。
+> [Redpoint][2] は、完全に統合されたキャンペーンオーケストレーションプラットフォームをマーケターに提供するテクノロジープラットフォームです。Redpoint のセグメンテーション、スケジュール、およびオートメーション機能を活用して、CDP データが Braze にインポートされる方法とタイミングをコントロールします。
 
-BrazeとRedpointインテグレーションを使用すると、RedpointのCDPデータに基づいてBraze Segmentsを作成できます。Redpoint には、Braze にデータを渡すための2 つの方法があります。 
+Braze と Redpoint の統合により、Redpoint CDP データに基づいて Braze セグメントを作成できます。Redpoint には、データを Braze に渡すための2種類のモードがあります。 
 
-1. **Braze Onboarding and Upsert** モード:"Upserts" RedpointからBrazeへのユーザープロファイル。これは、変更されたユーザーレコードをオンボーディングまたは更新するために使用されることを意図しています。 
-2. ** Braze 追加** モード:そのユーザーがBrazeにすでに存在する場合は、ユーザープロファイルをアップデートします。 
+1. **Braze Onboarding and Upsert** モード:"Upserts" RedpointからBrazeへのユーザープロファイル。これは、データが変更されたときに、ユーザーレコードを登録または更新するために使用されるものです。 
+2. **Braze Append** モード:そのユーザーがBrazeにすでに存在する場合は、ユーザープロファイルをアップデートします。 
 
-エクスポートテンプレートと送信チャネルを設定します。
+モードごとにエクスポートテンプレートとアウトバウンドチャネルを設定します。
 
 {% alert note %}
-"Upsert"は単語"更新"と"insert."の組合せです。データベーステーブルに新しいレコードが存在しない場合は、そのレコードをデータベーステーブルに挿入するか、存在する場合はレコードを更新する場合に使用されます。基本的に、upsert は、特定のレコードがデータベースに存在するかどうかを確認します。レコードが存在する場合は更新d、存在しない場合は新しいレコードが挿入されます。
+"Upsert"は単語"更新"と"insert."の組合せです。データベーステーブルに新しいレコードが存在しない場合は、そのレコードをデータベーステーブルに挿入するか、存在する場合はレコードを更新する場合に使用されます。基本的に、upsert は、特定のレコードがデータベースに存在するかどうかを確認します。レコードが存在する場合はレコードが更新され、存在しない場合は新しいレコードが挿入されます。
 {% endalert %}
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| Braze REST API キー | `users.track` 権限を持つBraze REST API キー。<br><br>これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
-| Braze REST エンドポイント | [Your REST エンドポイント URL][1].エンドポイントは、インスタンスのBraze URL によって異なります。 |
-| Redpoint データマネジメントアーティファクト | Brazeインテグレーションは、Redpoint データマネジメントアーティファクトの集合によってサポートされます。[ Redpoint サポート][3] に連絡して、Redpoint データマネジメントのアーティファクトをリクエストします。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br>これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
+| Braze REST エンドポイント | [REST エンドポイント URL][1]。エンドポイントはインスタンスの Braze URL に応じて異なります。 |
+| Redpoint Data Management アーティファクト | Braze 統合は、一連の Redpoint Data Management アーティファクトによりサポートされています。ご使用の Redpoint Data Management バージョンに対応したアーティファクトをリクエストするには、[Redpoint Support][3] にお問い合わせください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
@@ -42,10 +42,10 @@ BrazeとRedpointインテグレーションを使用すると、RedpointのCDP
 | フィールド               | 説明                                                                                                       |
 | ------------------- | ----------------------------------------------------------------------------------------------------------------- |
 | `rpi_cdp_attributes` | Redpoint CDP プロファイル 属性の対象                                                                                  |
-| `rpi_audience_outputs`| ユーザーがRedpoint 送信デリバリーBraze チャネルで実行されるオーディエンスアウトプットタグs の配列         |
-| `rpi_offers`         | Redpoint 送信デリバリーBraze チャネルでユーザーがターゲットとなるオファータグの配列                   |
-| `rpi_contact_ids`    | ユーザーがRedpoint 送信デリバリーBraze チャネルで実行されるオファー履歴の連絡先ID の配列     |
-| `rpi_channel_exec_ids`| Redpoint 送信デリバリーBraze チャネルの実行でユーザーのターゲットとなるチャネル実行ID の配列       |
+| `rpi_audience_outputs`| Redpoint Outbound Delivery Braze チャネルの実行でこのユーザーがターゲットとなるオーディエンス出力タグの配列         |
+| `rpi_offers`         | Redpoint Outbound Delivery Braze チャネルの実行でこのユーザーがターゲットとなるオファータグの配列                   |
+| `rpi_contact_ids`    | Redpoint Outbound Delivery Braze チャネルの実行でこのユーザーがターゲットとなるオファー履歴連絡先 ID の配列     |
+| `rpi_channel_exec_ids`| Redpoint Outbound Delivery Braze チャネルの実行でこのユーザーがターゲットとなるチャネル実行 ID の配列       |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ![][4]{: style="max-width:75%;"}
@@ -54,9 +54,9 @@ BrazeとRedpointインテグレーションを使用すると、RedpointのCDP
 
 ### ステップ1:テンプレートの設定
 
-#### ステップ 1a: Braze オンボーディングおよびアップサートテンプレートの作成
+#### ステップ 1a: Braze Onboarding and Upsert テンプレートを作成する
 
-Redpointインターアクション(RPI) で、新しいエクスポートテンプレートを作成し、** Braze Onboarding and Upsert** という名前を付けます。このテンプレートでは、Redpoint CDP とBraze ユーザープロファイル の間のコアm アプリを定義し、Braze のユーザープロファイルs に追加する追加のカスタム属性s も定義します。
+Redpointインターアクション(RPI) で、新しいエクスポートテンプレートを作成し、** Braze Onboarding and Upsert** という名前を付けます。このテンプレートでは、Redpoint CDP と Braze ユーザープロファイルの間のコアマッピングと、Braze でユーザープロファイルに追加するカスタム属性を定義します。
 
 Redpoint CDP 属性sを**属性**列にドラッグアンドドロップします。それぞれの**ヘッダー行値**を対応するBraze\[ユーザー 属性][17]]に設定します。 
 
@@ -65,27 +65,27 @@ Redpoint CDP 属性sを**属性**列にドラッグアンドドロップしま
 | Redpointアトリビュート | ヘッダ行値 |
 |--------------------|------------------|
 | PID                | `external_id`    |
-| フィッスト名          | `first_name`     |
+| Fist Name          | `first_name`     |
 | 姓          | `last_name`      |
-| プライマリメール      | `email`          |
+| Primary Email      | `email`          |
 | 主要国    | `country`        |
 | DOB                | `dob`            |
 | 性別             | `gender`         |
-| プライマリ市区町村       | `home_city`      |
-| プライマリ電話機      | `phone`          |
+| Primary City       | `home_city`      |
+| Primary Phone      | `phone`          |
 {: .reset-td-br-1 .reset-td-br-2}
 
-**Offer History**テーブルの**Offer Name**属性を追加します。最後に、Braze にマージするカスタムRedpoint 属性を追加します。たとえば、次のオンボーディングとアップサートのテンプレートでは、学歴、収入、および配偶者のステータスを追加属性としています。
+\[**Offer History**] テーブルの \[**Offer Name**] 属性を追加します。最後に、Braze にマージするカスタム Redpoint 属性を追加します。たとえば、Education、Income、および Marital Status が属性として追加されている Onboarding and Upsert テンプレートを以下に示します。
 
 ![][7]{: style="max-width:75%;"}
 
 #### ステップ 1b: Braze追加テンプレートの作成
 
-**Braze アプリ end** という名前のアプリ end-only オペレーションの2 番目のエクスポートテンプレートを作成します。
+追加専用操作のための2つ目のエクスポートテンプレートを **Braze Append** という名前で作成します。
 
 このテンプレートには2 つの属性s のみを設定します。**PID**の場合は、**Header Row Value**を`external_id`に設定します。**Output Name**の場合、**Header Row**を`output_name`に設定します。
 
-![`external_id` のエクスポートテンプレートの例と属性s を出力します。][8]{: style="max-width:75%;"}
+![`external_id` および Output Name 属性を含むエクスポートテンプレートの例。][8]{: style="max-width:75%;"}
 
 #### ステップ1c:日付形式の設定
 
@@ -93,27 +93,27 @@ Redpoint CDP 属性sを**属性**列にドラッグアンドドロップしま
 
 ![日付形式がyyyy-MM-dd に設定されているオプションタブ。][16]{: style="max-width:75%;"}
 
-### ステップ2:送信チャネルの作成s
+### ステップ2:アウトバウンドチャネルを作成する
 
-RPIで、2つの新しいチャネルsを作成します。両方のチャネルsを**Outbound Delivery**に設定します。1 つのチャネル** Braze Onboarding and Upsert** と、もう1 つの** Braze Append** に名前を付けます。
+RPI で2つの新しいチャネルを作成します。両方のチャネルを \[**Outbound Delivery**] に設定します。1つのチャネルに **Braze Onboarding and Upsert** という名前を付け、もう1つのチャネルに **Braze Append** という名前を付けます。
 
 ![][9]{: style="max-width:75%;"}
 
 {% alert note %}
-CDPレコードを最初にオンボーディングしてBrazeした後、最初のオンボーディングの同期以降に変更されたレコードのみを選択するように、Braze オンボーディングおよびアップサートチャネルを使用する後続のRedpointインターアクションワークフローが設計されているかどうかを確認します。
+Braze への CDP レコードの最初の登録後に、Braze Onboarding and Upsert チャネルを使用する後続の Redpoint Interaction ワークフローが、最初の登録同期以降に変更されたレコードのみを選択するように設計されているかどうかを確認します。
 {% endalert %}
 
 ### ステップ3:チャネルの設定s
 
 #### ステップ3a:テンプレートおよびエクスポートパス形式の設定
 
-チャネル s **Configuration** 画面の**General** タブに移動します。エクスポートテンプレートをそれぞれのチャネルに設定します。 
+チャネルの \[**Configuration**] 画面の \[**General**] タブに移動します。エクスポートテンプレートをそれぞれのチャネルに設定します。 
 
-次に、共有ネットワーク、ファイル転送プロトコル、または外部コンテンツプロバイダーの場所を指す両方のチャネルで、Redpoint Inter アクション とRedpoint データマネジメントの両方がアクセスできる**エクスポートパス形式** を定義します。 
+次に、Redpoint Interaction と Redpoint Data Management の両方がアクセスできる外部コンテンツプロバイダーの場所、ファイル転送プロトコル、または共有ネットワークを指す両方のチャネルで、**エクスポートパス形式**を定義します。 
 
 ![][10]{: style="max-width:75%;"}
 
-両方のチャネルs のエクスポートディレクトリ形式は同一であり、`\\[Channel]\\[Offer]\\[Workflow ID]` で終わる必要があります。
+両方のチャネルのエクスポートディレクトリ形式は同一であり、`\\[Channel]\\[Offer]\\[Workflow ID]` で終わる必要があります。
 
 ![][11]{: style="max-width:50%;"}
 
@@ -121,40 +121,40 @@ CDPレコードを最初にオンボーディングしてBrazeした後、最初
 
 Channels **Configuration** 画面の**Post Execution** タブに移動します。 
 
-チャネル実行後に**実行後**にチェックを入れ、サービスURLを呼び出します。Redpoint データマネジメントウェブサービスURL を入力します。このエントリは、オンボーディングと追加チャネルの両方で同じになります。
+チャネル実行後に**実行後**にチェックを入れ、サービスURLを呼び出します。Redpoint Data Management Web サービスの URL を入力します。このエントリは、Onboarding チャネルと Append チャネルの両方で同一です。
 
 ![][14]{: style="max-width:75%;"}
 
-### ステップ4:RedpointデータマネジメントでのBrazeコンポーネントの設定 
+### ステップ4:Redpoint Data Management で Braze コンポーネントを設定する 
 
-BrazeインテグレーションをサポートするRedpointデータマネジメント(RPDM)アーティファクトを含むアーカイブには、必要なコンポーネントを設定するための詳細な手順を含むREADME が含まれています。統合を設定するときは、次の詳細に留意してください。 
+Braze 統合をサポートするための Redpoint Data Management (RPDM) アーティファクトを含むアーカイブには、必要なコンポーネントの詳しい設定手順が記載された README が含まれています。統合を設定するときには以下の点に留意してください。 
 
-#### ステップ4a:Braze REST エンドポイントおよび基本RPI出力ディレクトリーを使用してRPIをBraze オートメーションにアップデートする 
+#### ステップ4a:Braze REST エンドポイントとベース RPI 出力ディレクトリで RPI to Braze オートメーションを更新する 
 
-Braze関連のアーティファクトをRedpoint データマネジメントにインポートした後、**AUTO_Process_RPI_to_Braze** という名前のオートメーションを開封し、次の2 つのオートメーション変数を環境の値で更新します。
+Braze 関連のアーティファクトを Redpoint Data Management にインポートした後で、**AUTO_Process_RPI_to_Braze** という名前のオートメーションを開き、次の2つのオートメーション変数をご使用の環境に対応した値で更新します。
 
 * **BRAZE_API_URL**:Braze REST エンドポイント
-* **BASE_OUTPUT_DIRECTORY**:Redpoint Inter アクション とRedpoint Data Management 間の共有出力ディレクトリー
+* **BASE_OUTPUT_DIRECTORY**:Redpoint Interaction と Redpoint Data Management 間の共有出力ディレクトリ
 
 ![][5]{: style="max-width:40%;"}
 
-#### ステップ4b:Braze アプリエンドプロジェクトへのRPI のアップデート 
+#### ステップ4b:RPI to Braze append プロジェクトを更新する 
 
-**PROJ_RPI_to_Braze_アプリ end**という名前のRedpointデータマネジメントプロジェクトには、Brazeの`rpi_cdp_attributes`カスタム属性オブジェクトの送信配信エクスポートファイルスキーマとmアプリが含まれています。 
+**PROJ_RPI_to_Braze_Append** という名前のRedpoint Data Management プロジェクトには、Braze の`rpi_cdp_attributes` カスタム属性オブジェクトのアウトバウンド配信エクスポートファイルスキーマとマッピングが含まれています。 
 
-**RPI という名前のファイル入力スキーマとドキュメントインジェクタツールを、エクスポートファイルテンプレートで定義された追加のカスタムCDP 属性でBraze ドキュメントインジェクタ** に更新します。次に、学歴、収入、配偶者のステータスに関する追加のm アプリを示します。
+ファイル入力スキーマとドキュメント挿入ツール **RPI to Braze Document Injector** を、エクスポートファイルテンプレートに定義されている追加のカスタム CDP 属性で更新します。次の例に、education、income、marital_status の追加マッピングを示します。
 
 ![][6]{: style="max-width:40%;"}
 
 ## 統合の使用
 
-送信配信Braze チャネルは、Redpoint Inter アクション ワークフローで活用できるようになりました。RPI での選択ルールとオーディエンスの作成、および関連付けられたワークフロースケジュールs とトリガーs の構築については、標準的な方法に従ってください。 
+Outbound Delivery Braze チャネルを Redpoint Interaction ワークフロー内で利用できるようになりました。RPI での選択ルールとオーディエンスの作成、および関連付けられたワークフロースケジュールs とトリガーs の構築については、標準的な方法に従ってください。 
 
-RPI オーディエンス出力をBraze に同期するには、送信配信オファーを作成し、** Braze Onboarding and Upsert** または** Braze Append** チャネルのいずれかに関連付けます。これは、インテントがBrazeで新規レコードを作成またはマージするかどうか、またはレコードがBrazeにすでに存在する場合はエンドキャンペーンデータのみをアプリするかどうかによって異なります。
+RPI Audience 出力を Braze に同期するには、アウトバウンド配信オファーを作成し、**Braze Onboarding and Upsert** チャネルまたは**Braze Append** チャネルのいずれかに関連付けます。これは、その目的が、Braze で新規レコードを作成またはマージすること、またはレコードが Braze に既に存在する場合にのみキャンペーンデータを追加することのいずれであるかによって異なります。
 
 ![][13]{: style="max-width:80%;"}
 
-ワークフローがRPI で正常に実行されると、RPI からのオーケストレーション およびCDP データソースd を使用して、Braze でSegments を作成できるようになります。
+ワークフローが RPI で正常に実行されると、RPI から取得したオーケストレーションおよび CDP データを使用して、Braze でセグメントを作成できるようになります。
 
 ![][12]{: style="max-width:80%;"}
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack.md
index f2c96c08017..01362acd978 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack.md
@@ -4,16 +4,16 @@ noindex: true
 alias: /partners/RudderStack/
 layout: dev_guide
 guide_top_header: "RudderStack"
-guide_top_text: "RudderStackは、データエンジニアがリッチな顧客データを使って組織のあらゆる部分に力を与えることを簡単にする。RudderStackを使えば、パイプラインの配管やセキュリティ、ボリュームによる突然のコスト上昇を心配することなく、自社のデータウェアハウスを完全な機能を備えた顧客データに変えることができる。Eメールから製品分析まで、あらゆる種類のツールにデータを送信することで、マーケティング、営業、製品チームを強化する。"
+guide_top_text: "RudderStack は、データエンジニアが豊富な顧客データを組織のあらゆる部分に簡単に活用することを可能にします。RudderStack を使うことで自社のデータウェアハウスを、機能を完備した顧客データプラットフォームに転換でき、パイプラインの整備、セキュリティ、ボリューム増によるコストの急上昇を気にする必要はありません。Eメールから製品分析まで、あらゆる種類のツールにデータを送信することで、マーケティング、営業、製品チームを強化する。"
 
-description: "このランディングページは、RudderStackとRudderStack for Currentsの統合方法など、RudderStackのすべてを紹介する。"
+description: "このランディングページは、RudderStack とRudderStack for Currents の統合方法など、RudderStack に関するあらゆる情報のホームページです。"
 
 
 guide_featured_list:
 - name: RudderStack
   link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack
   image: /assets/img/braze_icons/user-circle.svg
-- name: 電流用ラダースタック
+- name: RudderStack と Currents
   link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents/
   image: /assets/img/braze_icons/building-01.svg
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack.md
index e53775aba19..b5b528044b6 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack.md
@@ -9,19 +9,19 @@ search_tag: Partner
 
 # RudderStack
 
-> \[RudderStack][1] は、顧客のイベントデータを収集し、好みのデータウェアハウスやBrazeのような数多くの分析プロバイダーにルーティングするためのオープンソースの顧客データ基盤である。エンタープライズ対応で、イベントデータをその場で処理するための堅牢な変換フレームワークを提供する。
+> \[RudderStack][1] は、顧客イベントデータを収集し、希望するデータウェアハウスや Braze などの他の多数の分析プロバイダーにルーティングするための、オープンソースの顧客データインフラです。これはエンタープライズ対応で、イベントデータを即座に処理するための強力な変換フレームワークを提供します。
 
-BrazeとRudderStackの統合は、Android、iOS、WebアプリケーションのためのネイティブSDK統合と、バックエンドサービスからのサーバー間統合を提供する。
+Braze と RudderStack の統合により、Android、iOS、および Web アプリケーションのネイティブ SDK 統合と、バックエンドサービスからのサーバー間統合が提供されます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | --- | --- |
-| RudderStackアカウント | このパートナーシップを利用するには、[RudderStackのアカウントが](https://app.rudderstack.com/)必要である。 |
-| 設定されたソース | ソース][3] は基本的に、ウェブサイト、モバイルアプリ、バックエンドサーバーなど、RudderStackに送信されるあらゆるデータのオリジンである。RudderStackでBrazeをデスティネーションとして設定する前に、ソースを設定する必要がある。 |
-| Braze REST API キー | `users.track` 、`users.identify` 、`users.delete` 、`users.alias.new` の権限を持つBraze REST APIキー。<br><br>これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
+| RudderStackアカウント | このパートナーシップを活用するには、[RudderStack アカウント](https://app.rudderstack.com/)が必要です。 |
+| 設定済みのソース | \[ソース][3]は基本的に、Web サイト、モバイルアプリ、バックエンドサーバーなど、RudderStack に送信されるあらゆるデータの提供元です。RudderStack で Braze を宛先として設定する前に、ソースを設定する必要があります。 |
+| Braze REST API キー | `users.track`、`users.identify`、`users.delete`、`users.alias.new` の権限を持つ Braze REST API キー。<br><br>これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Brazeアプリのキー | Brazeダッシュボードでアプリキーを取得するには、**「設定」**>「**アプリ設定**」>「**識別**」と進み、アプリ名を見つける。関連する識別子文字列を保存する。
-| データセンター | データセンターはBrazeのダッシュボード\[instance][15].  |
+| データセンター | データセンターは、Braze ダッシュボード\[インスタンス][15]]に対応しています。  |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 統合
@@ -30,81 +30,81 @@ BrazeとRudderStackの統合は、Android、iOS、Webアプリケーションの
 
 Brazeへのデータ送信を開始するには、まずRudderStackアプリにソースが設定されていることを確認する必要がある。データソースの設定方法については、\[RudderStack][22] ] を参照のこと。
 
-### ステップ2:目的地を設定する
+### ステップ2:宛先を設定する
 
-データソースがセットアップされたので、RudderStackのダッシュボードで、**Destinationsの**下にある**ADD DESTINATIONを**選択する。利用可能な宛先リストから**Brazeを**選択し、**Nextを**クリックする。
+データソースが設定されたので、RudderStack ダッシュボードで、\[**Destinations**] の下にある \[**ADD DESTINATION**] を選択します。使用可能な宛先のリストから \[**Braze**] を選択し、\[**Next**] をクリックします。
 
-Brazeデスティネーションで、アプリキー、Braze REST APIキー、データクラスタ、およびネイティブSDKオプション（デバイスモードのみ）を指定する。ネイティブSDKオプションをオンにすると、BrazeネイティブSDKを使用してイベントを送信する。 
+Brazeデスティネーションで、アプリキー、Braze REST APIキー、データクラスタ、およびネイティブSDKオプション（デバイスモードのみ）を指定する。ネイティブ SDK オプションをオンにすると、Braze ネイティブ SDK を使用してイベントが送信されます。 
 
 ![][0]{: style="max-width:70%;margin-bottom:15px;border:none;"}
 
 ### ステップ3:統合のタイプを選ぶ
 
-RudderStackのWebおよびネイティブクライアントサイドライブラリをBrazeと統合するには、以下のいずれかの方法を選択する：
+次のいずれかの方法を使用して、RudderStack の Web ライブラリとネイティブクライアント側ライブラリを Braze と統合できます。
 
-- [サイド・バイ・サイド/デバイス・モード](#device-mode)**:**RudderStackは、クライアント（ブラウザまたはモバイルアプリケーション）から直接Brazeにイベントデータを送信する。
-- [サーバー間/クラウドモード](#cloud-mode)**:**Braze SDKはイベントデータを直接RudderStackに送り、それを変換してBrazeにルーティングする。
+- [サイドバイサイド/デバイスモード](#device-mode)**:**RudderStackは、クライアント（ブラウザまたはモバイルアプリケーション）から直接Brazeにイベントデータを送信する。
+- [サーバー間/クラウドモード](#cloud-mode)**:**Braze SDK はイベントデータを RudderStack に直接送信します。イベントデータは変換され、Braze にルーティングされます。
 - [ハイブリッドモード](#hybrid-mode)**:**ハイブリッドモードを使用して、iOSとAndroidの自動生成イベントとユーザー生成イベントを、単一の接続を使用してBrazeに送信する。
 
 {% alert note %}
-RudderStackの[接続モードと](https://www.rudderstack.com/docs/destinations/rudderstack-connection-modes/)それぞれの利点について詳しく知る。
+RudderStack の[接続モード](https://www.rudderstack.com/docs/destinations/rudderstack-connection-modes/)と、それぞれの利点について詳しく説明します。
 {% endalert %}
 
-#### サイド・バイ・サイドの統合（デバイス・モード） {#device-mode}
+#### サイドバイサイド統合 (デバイスモード) {#device-mode}
 
-このモードでは、ウェブサイトまたはモバイルアプリに設定したBraze SDKを使用して、イベントをBrazeに送信できる。
+このモードでは、Web サイトまたはモバイルアプリで設定した Braze SDK を使用して、イベントを Braze に送信できます。
 
-BrazeのGitHubリポジトリで、[サポートされる方法の](#supported-methods)説明に従って、お使いのプラットフォーム用のRudderStack SDKへのマッピングを設定する：
+「[サポートされているメソッド](#supported-methods)」で説明するように、Braze の GitHub リポジトリでご使用のプラットフォームに対応した RudderStack SDK へのマッピングを設定します。
 
-- \[アンドロイド]\[アンドロイド]
+- \[Android]\[android]
 - \[iOS]\[ios]
-- \[スウィフト]\[スウィフト]
+- \[Swift]\[swift]
 - \[Web]\[web]
-- \[リアクト・ネイティブ]\[react]
-- \[フラッター]\[flutter]
+- \[React Native]\[react]
+- \[Flutter]\[flutter]
 
-デバイスモードの統合を完了するには、[プロジェクトにBrazeを追加](https://rudderstack.com/docs/destinations/marketing/braze/#adding-device-mode-integration)するためのRudderStackの詳しい説明を参照する。
+デバイスモードの統合を完了するには、Rudderstack の[プロジェクトに Brazeを追加する](https://rudderstack.com/docs/destinations/marketing/braze/#adding-device-mode-integration)詳しい手順を参照してください。
 
 #### サーバー間統合（クラウドモード） {#cloud-mode}
 
-このモードでは、SDKはイベントデータを直接RudderStackサーバーに送信する。そして、RudderStackはこのデータを変換し、目的の目的地にルーティングする。この変換は、RudderStackのtransformerモジュールを使ってRudderStackのバックエンドで行われる。
+このモードでは、SDKはイベントデータを直接RudderStackサーバーに送信する。そして、RudderStackはこのデータを変換し、目的の目的地にルーティングする。この変換は、RudderStack のトランスフォーマーモジュールを使用して RudderStack バックエンドで実行されます。
 
-統合を有効にするには、[サポートされるメソッドで](#supported-methods)説明されているように、RudderStackのメソッドをBrazeにマッピングする必要がある。
+統合を有効にするには、[サポートされているメソッド](#supported-methods)で説明されているように、RudderStack メソッドを Braze にマッピングする必要があります。
 
 {% alert note %}
-RudderStackのサーバーサイドSDK（Java、Python、Node.js 、Go、Ruby）は、クラウドモードのみをサポートしている。これは、サーバー側のSDKがRudderStackのバックエンドで動作し、ブレーズ固有のSDKをロードできないためだ。
+RudderStackのサーバーサイドSDK（Java、Python、Node.js 、Go、Ruby）は、クラウドモードのみをサポートしている。これは、サーバー側の SDK が RudderStack バックエンドで動作し、Braze 固有のSDK を読み込むことができないためです。
 {% endalert %}
 
 {% alert important %}
-サーバー間の統合は、プッシュ通知やアプリ内メッセージングなどのBraze UI機能をサポートしていない。しかし、これらの機能は、デバイスモードの統合によってサポートされる。
+サーバー間の統合は、プッシュ通知やアプリ内メッセージングなどのBraze UI機能をサポートしていない。ただし、これらの機能はデバイスモード統合によってサポートされます。
 {% endalert %}
 
-#### ハイブリッド・モード {#hybrid-mode}
+#### ハイブリッドモード {#hybrid-mode}
 
 ハイブリッドモードを使用して、iOSとAndroidのソースからすべてのイベントをBrazeに送信する。 
 
-Brazeにイベントを送信するためにハイブリッドモードを選択した場合、RudderStack：
+ハイブリッドモードで Braze にイベントを送信することを選択した場合、RudderStack により次の操作が行われます。
 1. Braze SDKを初期化する。
 2. ユーザーが生成したすべてのイベント（identify、track、page、screen、group）をクラウドモードからのみBrazeに送信し、デバイスモードからの送信をブロックする。
 3. 自動生成イベント（アプリ内メッセージ、Braze SDKを必要とするプッシュ通知）をデバイスモード経由で送信する。
 
-[ハイブリッドモードでイベントを送信](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#send-events-in-hybrid-mode)するには、ソースをBrazeデスティネーションに接続する際にハイブリッドモードオプションを使用する。次に、Brazeインテグレーションをプロジェクトに追加する。
+[ハイブリッドモードでイベントを送信する](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#send-events-in-hybrid-mode)には、ソースを Braze の宛先に接続している状態でハイブリッドモードオプションを使用します。次に、Brazeインテグレーションをプロジェクトに追加する。
 
 ## ステップ4:追加設定を行う
 
 初期設定完了後、Brazeでデータを正しく受信するために以下の設定を行う：
 
-- **グループ通話でサブスクリプショングループを有効にする**：グループイベントで購読グループのステータスを送信するには、この設定を有効にする。詳しくは[グループを](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#group)参照のこと。
-- **カスタム属性を使用する**：Brazeの[ネストされたカスタム属性]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects/)機能を使用してセグメントを作成し、カスタム属性オブジェクトを使用してメッセージをパーソナライズする場合は、この設定を有効にする。詳細については、[ネストされたカスタム属性としてユーザー特性を送信するを](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#send-user-traits-as-nested-custom-attributes)参照のこと。
-- **匿名ユーザーのイベントを追跡**する：この設定を有効にすると、匿名のユーザーの活動が追跡され、その情報がBrazeに送信される。
+- **グループ通話でサブスクリプショングループを有効にする**：グループイベントでサブスクリプショングループのステータスを送信するには、この設定を有効にします。詳細については、[Group](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#group) を参照してください。
+- **Use Custom Attributes Operation**:Brazeの[ネストされたカスタム属性]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects/)機能を使用してセグメントを作成し、カスタム属性オブジェクトを使用してメッセージをパーソナライズする場合は、この設定を有効にする。詳細については、[ネストされたカスタム属性としてユーザー特性を送信するを](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#send-user-traits-as-nested-custom-attributes)参照のこと。
+- **Track events for anonymous users**:この設定を有効にすると、匿名のユーザーの活動が追跡され、その情報がBrazeに送信される。
 
 ### デバイスモード設定
 
 以下の設定は、[デバイスモード](https://www.rudderstack.com/docs/destinations/rudderstack-connection-modes/#device-mode)経由でBrazeにイベントを送信する場合にのみ適用される：
 
-- **クライアント側のイベントフィルタリング**：この設定により、Brazeに流れるイベントをブロックするか、許可するかを指定できる。この設定の詳細については、[クライアント側イベントフィルタリングを](https://www.rudderstack.com/docs/sources/event-streams/sdks/event-filtering/)参照のこと。
-- **形質を重複させない**：この設定を有効にすると、コール内のユーザー形質が重複排除される。 [`identify`](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#identify)を呼び出す。
-- **Brazeのログを表示する**：この設定は、[JavaScript SDKを](https://www.rudderstack.com/docs/sources/event-streams/sdks/rudderstack-javascript-sdk/)ソースとして使用する場合にのみ適用される。Brazeのログをユーザーに表示するには、これを有効にする。
+- **クライアント側のイベントフィルタリング**：この設定により、Brazeに流れるイベントをブロックするか、許可するかを指定できる。この設定の詳細については、[クライアント側のイベントフィルタリング](https://www.rudderstack.com/docs/sources/event-streams/sdks/event-filtering/)を参照してください。
+- **Deduplicate Traits**:この設定を有効にすると、[`identify`](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#identify) 呼び出しでユーザー特性の重複が排除されます。
+- **Show Braze logs**:この設定は、[JavaScript SDKを](https://www.rudderstack.com/docs/sources/event-streams/sdks/rudderstack-javascript-sdk/)ソースとして使用する場合にのみ適用される。Brazeのログをユーザーに表示するには、これを有効にする。
 - **OneTrustクッキーカテゴリー**：この設定により、[OneTrust](https://www.rudderstack.com/docs/sources/event-streams/sdks/onetrust/javascript/)クッキーの同意グループをBrazeに関連付けることができる。
 
 ## サポートされている方法
@@ -112,55 +112,55 @@ Brazeにイベントを送信するためにハイブリッドモードを選択
 Brazeは、RudderStackメソッドのidentify、track、screen、page、group、aliasをサポートしている。
 
 {% tabs %}
-{% tab 特定する %}
+{% tab Identify %}
 
 RudderStack[`identify` メソッドは](https://rudderstack.com/docs/destinations/marketing/braze/#identify)、ユーザーとそのアクションを関連付ける。RudderStackは、一意のユーザーIDと、名前、電子メール、IPアドレスなど、そのユーザーに関連するオプションの特徴をキャプチャする。
 
-**特定コールのデルタ管理**<br>
-デバイスモード経由でBrazeにイベントを送信する場合、`identify` コールを重複排除することでコストを節約できる。そのためには、ダッシュボードのDeduplicate Traits設定を有効にする。そしてRudderStackは、変更または修正された属性（trait）のみをBrazeに送信する。
+**identify 呼び出しの差分管理**<br>
+デバイスモードで Braze にイベントを送信する場合、`identify` 呼び出しを重複排除することでコストを節減できます。そのためには、\[Deduplicate Traits] ダッシュボード設定を有効にします。その後、RudderStack は変更された属性 (特性) のみを Braze に送信します。
 
-**ユーザーを削除する**<br>
-RudderStack[Data Regulation APIの](https://www.rudderstack.com/docs/api/data-regulation-api/) [Suppression with Deleteレギュレーションを](https://www.rudderstack.com/docs/api/data-regulation-api/#adding-a-suppression-with-delete-regulation)使用して、Brazeでユーザーを削除できる。
+**ユーザーの削除**<br>
+RudderStack [Data Regulation API](https://www.rudderstack.com/docs/api/data-regulation-api/) の[抑制と削除の規則 (Suppression with Delete regulation)](https://www.rudderstack.com/docs/api/data-regulation-api/#adding-a-suppression-with-delete-regulation) を使用して、Braze のユーザーを削除できます。
 
 {% endtab %}
-{% tab トラック %}
+{% tab Track %}
 
 RudderStackの[`track` メソッドは](https://rudderstack.com/docs/destinations/marketing/braze/#track)、すべてのユーザー・アクティビティと、それらのアクティビティに関連するプロパティをキャプチャする。
 
-**注文完了**<br>
-RudderStack Ecommerce API][20] を使用して、`Order Completed` という名前のイベントの track メソッドを呼び出すと、RudderStack はそのイベントにリストされている商品を [`purchases`][21].
+**Order completed**<br>
+\[RudderStack Ecommerce API][20] を使用して `Order Completed` という名前のイベントに対して track メソッドを呼び出すと、RudderStack はそのイベントにリストされている製品を [`purchases`][21] として Braze に送信します。
 
 {% endtab %}
 {% tab スクリーン %}
 
-RudderStackの[`screen` メソッドでは](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#screen)、ユーザーのモバイル画面表示を、表示画面に関する追加情報とともに記録することができる。
+RudderStack の [`screen` メソッド](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#screen)を使用して、ユーザーのモバイル画面ビューを、表示されている画面に関する追加情報とともに記録できます。
 
 {% endtab %}
 {% tab ページ %}
 
-RudderStackの[`page` ](https://rudderstack.com/docs/destinations/marketing/braze/#page)、ウェブサイトのページビューを記録することができる。また、そのページに関するその他の関連情報もキャプチャする。
+RudderStack の [`page` メソッド](https://rudderstack.com/docs/destinations/marketing/braze/#page) を使用して、Web サイトのページビューを記録できます。また、そのページに関するその他の関連情報もキャプチャされます。
 
 {% endtab %}
-{% tab グループ %}
+{% tab Group %}
 
 RudderStackの[`group` メソッドでは](https://rudderstack.com/docs/destinations/marketing/braze/#group)、ユーザーをグループに関連付けることができる。
 
-**購読グループのステータス**<br>
-サブスクリプショングループのステータスを更新するには、RudderStackダッシュボードの "Enable subscription groups in group call "設定を有効にし、グループコールでサブスクリプショングループのステータスを送信する。
+**サブスクリプショングループのステータス**<br>
+サブスクリプショングループのステータスを更新するには、RudderStack ダッシュボードの \[Enable subscription groups in group call] 設定を有効にし、グループ呼び出しでサブスクリプショングループのステータスを送信します。
 
 {% endtab %}
 {% tab 別名 %}
 
-RudderStackの[`alias` メソッドでは](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#alias)、既知のユーザーの異なるIDをマージすることができる。RudderStackは、クラウドモードでのみBrazeのエイリアス呼び出しをサポートしていることに注意。
+RudderStack の [`alias` メソッド](https://www.rudderstack.com/docs/destinations/streaming-destinations/braze/#alias) を使用して、既知のユーザーの複数の ID をマージできます。RudderStack は、クラウドモードでのみ Braze のエイリアス呼び出しをサポートしていることに注意してください。
 
 {% endtab %}
 {% endtabs %}
 
 ## ユーザー特性をネストされたカスタム属性として送信する
 
-ユーザー特性をネストされたカスタム属性としてBrazeに送信し、それに対して追加、更新、削除操作を実行できる。そのためには、RudderStackでBrazeデスティネーションを設定する際に、"Use Custom Attributes Operation dashboard "設定を有効にする。この機能はクラウドモードでのみ利用できる。
+ユーザー特性をネストされたカスタム属性としてBrazeに送信し、それに対して追加、更新、削除操作を実行できる。これを行うには、Braze の宛先を設定するときに Rudderstack で \[Use Custom Attributes Operation dashboard] 設定を有効にします。この機能はクラウドモードでのみ利用できる。
 
-`identify` 、ネストされたカスタム・アトリビュートとして、以下のフォーマットでユーザーの特徴を送ることができる：
+次の形式で `identify` イベントでユーザー特性を階層化カスタム属性として送信できます。
 ```javascript
 rudderanalytics.identify("1hKOmRA4GRlm", {
   "cars": {
@@ -203,7 +203,7 @@ rudderanalytics.identify("1hKOmRA4GRlm", {
 })
 ```
 
-`track` 、`page` 、`screen` のコールでカスタムユーザー属性としてユーザー特性を送信するには、`traits` をイベントのコンテキストフィールドとして渡す：
+`track`、`page`、または`screen` 呼び出しでユーザー特性をカスタムユーザ属性として送信するには、イベントのコンテキストフィールドとして `traits` を渡します。
 ```javascript
 rudderanalytics.track("Product Viewed", {
     revenue: 8.99,
@@ -253,7 +253,7 @@ rudderanalytics.track("Product Viewed", {
 ```
 
 {% alert note %}
-更新と削除の操作では、`identifier` が必須キーとなる。add、update、remove操作が入れ子配列に存在しない場合、RudderStackはデフォルトでcreate操作を使用してプロパティを作成する。ネストされたカスタム属性の送信に関する詳細は、[オブジェクトの]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects/)配列を参照のこと。
+更新と削除の操作では、`identifier` が必須キーとなる。add、update、remove操作が入れ子配列に存在しない場合、RudderStackはデフォルトでcreate操作を使用してプロパティを作成する。階層化カスタム属性の送信の詳細については、「[オブジェクト配列]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects/)」を参照してください。
 {% endalert %}
 
 [0]: {% image_buster /assets/img/RudderStack/braze_settings.png %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents.md
index 43fd6724e19..f7c3fc5fef1 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack_for_currents.md
@@ -1,48 +1,48 @@
 ---
-nav_title: Currents用ラダースタック
-article_title: Currents用ラダースタック
-description: "本稿では、Android、iOS、およびウェブアプリのライセンスにシームレスなBrazeインテグレーションを提供する開封ソース顧客データ インフラであるBraze CurrentsとRudderStackの提携について概説します。"
+nav_title: RudderStack と Currents
+article_title: RudderStack と Currents
+description: "この記事では、Braze Currents と RudderStack のパートナーシップについて説明します。RudderStack は、Android、iOS、および Web アプリケーション向けのシームレスな Braze 統合を提供するオープンソースの顧客データインフラストラクチャです。"
 page_type: partner
 tool: Currents
 search_tag: Partner
 
 ---
 
-# Currents用ラダースタック
+# RudderStack と Currents
 
-> [RudderStack](https://www.rudderstack.com/) では、クラウドデータウェアハウスを真理の中心的な源泉として活用することで、スタック全体で顧客データを収集、変換、アクティブ化することができます。ここでは、Braze Currents とRudderStack 間のコネクションの設定方法について説明します。
+> [RudderStack](https://www.rudderstack.com/) では、スタック全体で顧客データを収集、変換、アクティブ化し、クラウドデータウェアハウスを一元的な信頼できる情報源として活用することができます。この記事では、Braze Currents と RudderStack 間の接続を設定する方法の概要を説明します。
 
-Braze とRudderStack の統合により、BrazeイベントをRudderStack にエクスポートするBraze Currentsを活用して、より深い分析を促進できます。
+Braze と RudderStack の統合により、Braze Currents を利用して Braze イベントを RudderStack にエクスポートし、より深い分析を促進できます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | --- | --- |
-| RudderStackアカウント | この提携の前倒しタグを行うには、[RudderStackアカウント](https://app.rudderstack.com/login)が必要です。 |
-| Braze 送信先 | RudderStack では、[ Brazeを送信先]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack/#integration) として設定することをお勧めします。 |
-| Currents | RudderStack にデータをエクスポートするには、アカウントに[Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
+| RudderStackアカウント | このパートナーシップを活用するには、[RudderStack アカウント](https://app.rudderstack.com/login)が必要です。 |
+| Braze 宛先 | RudderStack で [Braze を宛先として設定する]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/rudderstack/#integration)ことをお勧めします。 |
+| Currents | RudderStack にデータを再度エクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:RudderStack 内でのBrazeのデータソースの作成
 
-まず、RudderStack ウェブアプリでBraze送信元を作成する必要があります。データソースの作成手順は、[RudderStack](https://www.rudderstack.com/docs/sources/event-streams/cloud-apps/braze-currents/) サイトにあります。
+まず、RudderStack Web アプリで Braze ソースを作成する必要があります。データソースの作成手順は、[RudderStack](https://www.rudderstack.com/docs/sources/event-streams/cloud-apps/braze-currents/) サイトにあります。
 
-完了すると、書き込みキーを含むWebhook URL が提供されます。これは、次回のステップで使用する必要があります。WebhookのURLは、Braze元の**Settings**タブにあります。
+この作業が完了すると、Rudderstack から Webhook URL が提供されます。この URL に含まれている書き込みキーは、次のステップで使用する必要があります。WebhookのURLは、Braze元の**Settings**タブにあります。
 
 ### ステップ2:現在の作成
 
-Braze で、**Currents > + Create Current > RudderStack Export** に移動します。統合名、連絡先メール、RudderStack Webhook URL (キーフィールドに表示されます)、およびRudderStack リージョンを指定します。 
+Braze で **\[Currents] > \[+ Currents を作成] > \[RudderStack のエクスポート]** に移動します。統合名、連絡先メール、RudderStack Webhook URL (キーフィールドに表示されます)、およびRudderStack リージョンを指定します。 
 
 ### ステップ3:イベントのエクスポート
 
 次に、書き出すイベントを選択します。最後に、**Launch Current**をクリックします。
 
-RudderStack に送信されるすべてのイベントには、ユーザーの`external_user_id` が含まれます。このとき、Braze は`external_user_id` が設定されていないユーザーに対して、イベントデータをRudderStack に送信しません。
+RudderStack に送信されるすべてのイベントには、ユーザーの`external_user_id` が含まれます。この時点では Braze は、`external_user_id` が設定されていないユーザーのイベントデータを RudderStack に送信しません。
 
 ## 統合の詳細
 
-Braze は、[ Currentsイベント用語集]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents) にリストされているすべてのデータのRudderStack へのエクスポートをサポートしています。
+Braze は、[Currents のイベント用語集]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents)に記載されているすべてのデータを RudderStack にエクスポートする操作をサポートしています。
 
-エクスポートされたデータの給与読み込む構成は、カスタムHTTP コネクターの給与読み込む構成と同じです。カスタムHTTP コネクターの[サンプルリポジトリーで表示できます](https://github.com/Appboy/currents-examples/tree/master/sample-data/Custom%20HTTP/users/behaviors)。
\ No newline at end of file
+エクスポートされたデータのペイロードの構造は、カスタム HTTP コネクターのペイロード構造と同じです。これは、[カスタム HTTP コネクターのサンプルリポジトリ](https://github.com/Appboy/currents-examples/tree/master/sample-data/Custom%20HTTP/users/behaviors)で確認できます。
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment.md
index eba6c74bc33..d5b31e44afc 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment.md
@@ -3,14 +3,14 @@ nav_title: セグメント
 layout: dev_guide
 search_rank: 9
 guide_top_header: "セグメント"
-guide_top_text: "セグメントは、企業が顧客を第一に考えるための顧客データ・インフラを提供している。Segmentを使えば、ファーストパーティーの顧客データを収集、統合し、Eメール、ウェブ、広告、POS、モバイルなど200以上のツールに接続することができる。Segmentを使えば、ユーザーの共通理解を達成し、自社のデータを活性化して、パーソナライズされた顧客第一の体験を生み出すことができる。"
-description: "このランディング・ページは、顧客データ・プラットフォームであるSegmentに関連するすべてのことを扱っている。"
+guide_top_text: "セグメントは、企業が顧客を第一に考えるための顧客データ・インフラを提供している。Segment の活用により、ファーストパーティの顧客データを収集、一元化でき、メール、Web、広告、POS、モバイルを含め、200以上のツールに接続できます。Segment の活用により、ユーザーの共通の理解を得て自社データを有効化し、パーソナライズされたカスタマーファーストの体験を提供できます。"
+description: "このランディングページは、顧客データプラットフォームである Segment に関するあらゆる情報のホームページです。"
 
 guide_featured_list:
 - name: セグメント
   link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/
   image: /assets/img/braze_icons/user-circle.svg
-- name: セグメント・エンゲージ
+- name: Segment Engage
   link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage/
   image: /assets/img/braze_icons/users-01.svg
 - name: 電流セグメント
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment.md
index d1e6e0a9919..0be262fd93e 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment.md
@@ -13,78 +13,78 @@ search_tag: Partner
 
 {% multi_lang_include video.html id="RfOHfZ34hYM" align="right" %}
 
-> [Segmentは][5]、顧客データの収集、クリーニング、活性化を支援する顧客データ・プラットフォームである。 
+> [Segment][5] は、顧客データの収集、クリーンアップ、およびアクティブ化を支援する顧客データプラットフォームです。 
 
-BrazeとSegmentの統合により、ユーザーを追跡し、様々なユーザー分析プロバイダーにデータをルーティングすることができる。セグメントを使えば、次のことができる：
-- BrazeキャンペーンとCanvasセグメンテーションで使用するために、[Segment Engageを]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage/)Brazeに同期する。
-- [2つのプラットフォーム間でデータをインポートする](#integration-options)。お客様のAndroid、iOS、およびWebアプリケーション用のサイドバイサイドSDKインテグレーションと、BrazeのREST APIにデータを同期するためのサーバー間インテグレーションを提供する。
+Braze と Segment の統合により、ユーザーを追跡し、さまざまなユーザー分析プロバイダーにデータを転送できます。Segment では次の操作を行うことができます。
+- Braze キャンペーンとキャンバスセグメンテーションで使用するために、[Segment Engage]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage/)を Braze に同期する。
+- [2つのプラットフォームの間でデータをインポートする](#integration-options)。お客様のAndroid、iOS、およびWebアプリケーション用のサイドバイサイドSDKインテグレーションと、BrazeのREST APIにデータを同期するためのサーバー間インテグレーションを提供する。
 - [カレントを介してデータをセグメントに接続する]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_for_currents/)。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| セグメント・アカウント | このパートナーシップを利用するには、[セグメントアカウントが](https://app.segment.com/login)必要である。 |
-| インストールされたソースとセグメント・ソース・[ライブラリ](https://segment.com/docs/sources/) | モバイルアプリ、ウェブサイト、バックエンドサーバーなど、Segmentに送信されるあらゆるデータの送信元。<br><br>ライブラリをアプリ、サイト、サーバーにインストールしてからでないと、`Source > Destination` 。 |
+| Segment アカウント | このパートナーシップを活用するには、[Segment アカウント](https://app.segment.com/login)が必要です。 |
+| インストールされたソースと Segment ソースの[ライブラリ](https://segment.com/docs/sources/) | モバイルアプリ、Web サイト、バックエンドサーバーなど、Segment に送信されるデータの提供元。<br><br>適切な `Source > Destination` フローを設定できるようにするには、ライブラリをアプリ、サイト、サーバーにインストールしておく必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-BrazeとSegmentを統合するには、[選択した統合タイプ](#integration-options)（接続モード）に従って、[Brazeを接続先に](#connection-settings)設定する必要がある。Brazeの新規顧客であれば、[セグメントリプレイを使って](#segment-replays)過去のデータをBrazeにリレーすることができる。次に、BrazeとSegment間のスムーズなデータフローを確保するために、[マッピングを](#methods)設定し、[統合をテスト](#step-4-test-your-integration)しなければならない。
+BrazeとSegmentを統合するには、[選択した統合タイプ](#integration-options)（接続モード）に従って、[Brazeを接続先に](#connection-settings)設定する必要がある。Brazeの新規顧客であれば、[セグメントリプレイを使って](#segment-replays)過去のデータをBrazeにリレーすることができる。次に、Braze と Segment 間のスムーズなデータフローを確保するために、[マッピング](#methods)を設定し、[統合をテスト](#step-4-test-your-integration)する必要があります。
 
-### ステップ1:ブレイズの目的地を作る {#connection-settings}
+### ステップ1:Braze 宛先を作成する {#connection-settings}
 
-ソースの設定に成功したら、各ソース（iOS、Android、ウェブなど）の[デスティネーションとして](https://segment.com/docs/destinations/)Brazeを設定する必要がある。接続設定を使用して、BrazeとSegment間のデータフローをカスタマイズする多くのオプションがある。
+ソースの設定が完了したら、各ソース (iOS、Android、Web など) の[宛先](https://segment.com/docs/destinations/)として Braze を設定する必要があります。接続設定を使用して、BrazeとSegment間のデータフローをカスタマイズする多くのオプションがある。
 
-### ステップ2:接続先フレームワークと接続タイプを選択する {#integration-options}
+### ステップ2:宛先フレームワークと接続タイプを選択する {#integration-options}
 
-Segmentで、**Destinations > Braze > Configure Braze > Select your Source > Setupと**進む。
+Segmentで、**\[Destinations] > \[Braze] > \[Configure Braze] > \[Select your Source] > \[Setup]** の順に移動します。
 
-![ソースの設定ページ。このページでは、デスティネーション・フレームワークを「アクション」または「クラシック」のいずれかに設定し、接続モードを「クラウドモード」または「デバイスモード」のいずれかに設定する。][42]
+![ソースの設定ページ。このページでは、宛先フレームワークを \[Actions] または \[Classic] のいずれかに設定し、接続モードを \[Cloud mode] または \[Device mode] のいずれかに設定します。][42]
 
-Segmentのウェブソース（Analytics.js ）およびネイティブクライアントサイドライブラリは、サイドバイサイド（デバイスモード）統合またはサーバー間（クラウドモード）統合のいずれかを使用して、Brazeと統合できる。
+Segment のWeb ソース (Analytics.js) およびネイティブクライアントサイドライブラリは、サイドバイサイド (デバイスモード) 統合またはサーバー間 (クラウドモード) 統合のいずれかを使用して、Braze と統合できます。
 
-接続モードの選択は、宛先が設定されているソースのタイプによって決定される。
+選択する接続モードは、宛先が設定されているソースのタイプによって決まります。
 
 | 統合 | 詳細 |
 | ----------- | ------- |
-| [サイド・バイ・サイド<br>(デバイスモード)](#side-by-side-sdk-integration) |SegmentのSDKを使用して、イベントをBrazeのネイティブコールに変換し、サーバー間の統合よりも深い機能とBrazeのより包括的な使い方にアクセスできるようにする。<br><br>Segmentは、すべてのBrazeメソッド（例えば、Content Cards）をサポートしているわけではない。対応するマッピングを通してマッピングされていないBrazeメソッドを使用するには、コードベースにネイティブのBrazeコードを追加してメソッドを呼び出す必要がある。 |
-| [サーバー間<br>(クラウドモード）](#server-to-server-integration) | SegmentからBraze REST APIエンドポイントにデータを転送する。<br><br>アプリ内メッセージ、コンテンツカード、プッシュ通知などのBraze UI機能には対応していない。また、この方法では利用できない、デバイスレベルのフィールドのような、自動的に取り込まれるデータも存在する。<br><br>これらの機能を使いたい場合は、サイド・バイ・サイドの統合を検討しよう。|
+| [サイドバイサイド<br>(デバイスモード)](#side-by-side-sdk-integration) |Segment の SDK を使用して、イベントを Braze のネイティブ呼び出し変換します。これにより、サーバー間統合よりも高度な機能にアクセスでき、Braze をより包括的に使用できるようになります。<br><br>Segmentは、すべてのBrazeメソッド（例えば、Content Cards）をサポートしているわけではない。対応するマッピングを通してマッピングされていないBrazeメソッドを使用するには、コードベースにネイティブのBrazeコードを追加してメソッドを呼び出す必要がある。 |
+| [サーバー間<br>(クラウドモード)](#server-to-server-integration) | SegmentからBraze REST APIエンドポイントにデータを転送する。<br><br>アプリ内メッセージ、コンテンツカード、プッシュ通知などのBraze UI機能には対応していない。また、この方法では利用できないデバイスレベルのフィールドなど、自動的に取得されるデータも存在します。<br><br>これらの機能を使いたい場合は、サイド・バイ・サイドの統合を検討しよう。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
 2つの統合オプション（接続モード）について、それぞれの利点を含め、詳しくは[セグメントを](https://segment.com/docs/destinations/#connection-modes)ご覧いただきたい。
 {% endalert %}
 
-#### サイド・バイ・サイドのSDK統合
+#### サイドバイサイドの SDK 統合
 
-デバイスモードとも呼ばれるこの統合は、SegmentのSDKと[メソッドを](#methods)Braze SDKにマッピングし、プッシュ、アプリ内メッセージング、その他のBrazeネイティブのメソッドなど、当社のSDKが提供するすべての機能へのアクセスを可能にする。 
+デバイスモードとも呼ばれるこの統合では、Segment の SDK と[メソッド](#methods)が Braze SDK にマッピングされます。これにより、Braze の SDK が提供するすべての機能 (プッシュ、アプリ内メッセージング、その他の Braze ネイティブのメソッドなど) にアクセスできるようになります。 
 
 {% alert note %}
-Segmentのデバイスモードを使用する場合、Braze SDKを直接統合する必要はない。Segmentのデバイスモード先としてBrazeを追加する場合、Segment SDKはBraze SDKを初期化し、関連するマッピングされたBrazeメソッドを呼び出す。
+Segment のデバイスモードを使用する場合、Braze SDK を直接統合する必要はありません。Segment のデバイスモードの宛先として Braze を追加する場合、Segment SDK は Braze SDK を初期化し、関連するマッピングされた Braze メソッドを呼び出します。
 {% endalert %}
 
-デバイスモード接続を使用する場合、Braze SDKをネイティブに統合するのと同様に、Braze SDKは、すべてのユーザーに`device_id` とバックエンド識別子、`braze_id` を割り当てる。これによりBrazeは、`userId` の代わりにこれらの識別子を照合することで、デバイスからの匿名アクティビティをキャプチャすることができる。 
+デバイスモード接続を使用する場合、Braze SDK をネイティブに統合する場合と同様に、Braze SDK はすべてのユーザーに `device_id` とバックエンド識別子 `braze_id` を割り当てます。これにより Braze は、`userId` の代わりにこれらの識別子を照合することで、デバイスからの匿名アクティビティを取得できます。 
 
 {% tabs ローカル %}
-{% tab アンドロイド %}
+{% tab Android %}
 
 {% alert important %}
 Androidデバイスモード統合のソースコードは、Brazeによって保守されており、新しいBraze SDKのリリースを反映して定期的に更新される。
 
 <br>
-使用するBraze SDKは、使用するSegment SDKによって異なる：
+使用する Braze SDKは、使用する Segment SDK によって異なります。
 
-| セグメントSDK｜ブレイズSDK
+| | Segment SDK | Braze SDK |
 | - | ----------- | --------- |
-\|[Analytics-Kotlin｜Braze Segment Kotlin](https://github.com/braze-inc/braze-segment-kotlin)｜優先｜[分析-Kotlin](https://github.com/segmentio/analytics-kotlin)｜[ブレイズ・セグメント・コトリン](https://github.com/braze-inc/braze-segment-kotlin)
-| レガシー｜[アナリティクス-アンドロイド](https://github.com/segmentio/analytics-android)｜[Braze Segment Android](https://github.com/braze-inc/braze-segment-android)｜[ブレイズ・セグメント・アンドロイド](https://github.com/braze-inc/braze-segment-android)
+| 優先 | [Analytics-Kotlin](https://github.com/segmentio/analytics-kotlin) | [Braze Segment Kotlin](https://github.com/braze-inc/braze-segment-kotlin) |
+| レガシー｜[Analytics-Android](https://github.com/segmentio/analytics-android)｜[Braze Segment Android](https://github.com/braze-inc/braze-segment-android)｜
 {: .reset-td-br-1 .reset-td-br-2}
 
 
 {% endalert %}
 
-AndroidソースのデバイスモードデスティネーションとしてBrazeを設定するには、デスティネーションフレームワークとして**Classicを**選択し、**Saveを**クリックする。 
+Android ソースのデバイスモードの宛先として Braze を設定するには、宛先フレームワークとして \[**Classic**] を選択し、\[**Save**] をクリックします。 
 
 ![]({% image_buster /assets/img/segment/android.png %})
 
@@ -99,16 +99,16 @@ AndroidソースのデバイスモードデスティネーションとしてBraz
 iOSデバイスモード統合のソースコードは、Brazeによって保守されており、新しいBraze SDKのリリースを反映して定期的に更新される。
 
 <br>
-使用するBraze SDKは、使用するSegment SDKによって異なる：
+使用する Braze SDKは、使用する Segment SDK によって異なります。
 
-| セグメントSDK｜ブレイズSDK
+| | Segment SDK | Braze SDK |
 | - | ----------- | --------- |
-| プリファード｜[アナリティクス・スイフト](https://github.com/segmentio/analytics-swift)｜[ブレイズ・セグメント・スイフト](https://github.com/braze-inc/braze-segment-swift)
-| レガシー｜[アナリティクスiOS](https://github.com/segmentio/analytics-ios)｜[Braze Segment iOS](https://github.com/Appboy/appboy-segment-ios)｜[ブレイズ・セグメントiOS](https://github.com/Appboy/appboy-segment-ios)
+| 優先 | [Analytics-Swift](https://github.com/segmentio/analytics-swift) | [Braze Segment Swift](https://github.com/braze-inc/braze-segment-swift) |
+| レガシー｜[Analytics-iOS](https://github.com/segmentio/analytics-ios)｜[Braze Segment iOS](https://github.com/Appboy/appboy-segment-ios)｜
 {: .reset-td-br-1 .reset-td-br-2}
 {% endalert %}
 
-BrazeをiOSソースのデバイスモードデスティネーションとして設定するには、デスティネーションフレームワークとして**Classicを**選択し、**Saveを**クリックする。 
+iOS ソースのデバイスモードの宛先として Braze を設定するには、宛先フレームワークとして \[**Classic**] を選択し、\[**Save**] をクリックします。 
 
 ![]({% image_buster /assets/img/segment/ios.png %})
 
@@ -121,136 +121,136 @@ BrazeをiOSソースのデバイスモードデスティネーションとして
 
 Segmentの新しいBraze Web Mode (Actions)フレームワークは、BrazeをWebソースのデバイスモードデスティネーションとして設定するのに推奨される。 
 
-セットアップUIで、接続先フレームワークとして**Actionsを**、接続モードとして**Device Modeを**選択する。
+Setup UI で、宛先フレームワークとして \[**Actions**] を選択し、接続モードとして \[**Device Mode**] を選択します。
 
 ![]({% image_buster /assets/img/segment/website.png %})
 
 {% endtab %}
-{% tab リアクト・ネイティブ %}
-[React Native Brazeプラグインの](https://github.com/segmentio/analytics-react-native/tree/master/packages/plugins/plugin-braze)ソースコードはSegmentによって管理されており、新しいBraze SDKのリリースを反映するために定期的に更新される。
+{% tab React Native %}
+[React Native Braze プラグイン](https://github.com/segmentio/analytics-react-native/tree/master/packages/plugins/plugin-braze)のソースコードは Segment によって管理されており、新しい Braze SDK リリースを反映するために定期的に更新されます。
 
-React NativeセグメントソースをBrazeに接続する場合、オペレーティングシステムごとにソースとデスティネーションを設定する必要がある。例えば、iOSのデスティネーションとAndroidのデスティネーションを設定する。 
+React Native Segment ソースを Braze に接続する場合は、オペレーティングシステムごとにソースと宛先を設定する必要があります。たとえば、iOS の宛先と Android の宛先を設定します。 
 
 アプリのコードベース内で、各アプリに関連付けられたそれぞれのソース書き込みキーを使用して、デバイスタイプ別にSegment SDKを条件付きで初期化する。
 
 デバイスからプッシュトークンが登録され、Brazeに送信されると、SDKの初期化時に使用されたアプリ識別子に関連付けられる。デバイスタイプの条件付き初期化は、Brazeに送信されるプッシュトークンが関連アプリに関連付けられていることを確認するのに役立つ。
 
 {% alert important %}
-React Nativeアプリがすべてのデバイスで同じBrazeアプリ識別子でBrazeを初期化する場合、すべてのReact NativeユーザーはBrazeでAndroidまたはiOSユーザーとみなされ、すべてのプッシュトークンはそのオペレーティングシステムに関連付けられる。
+React Native アプリがすべてのデバイスで同じ Braze アプリ識別子を使用して Braze を初期化する場合、すべての React Native ユーザーは Braze で Android ユーザーまたは iOS ユーザーとみなされ、すべてのプッシュトークンはそのオペレーティングシステムに関連付けられます。
 {% endalert %}
 
-Brazeを各ソースのデバイスモードデスティネーションとして設定するには、デスティネーションフレームワークとして**Classicを**選択し、**Saveを**クリックする。
+各ソースのデバイスモードの宛先として Braze を設定するには、宛先フレームワークとして \[**Classic**] を選択し、\[**Save**] をクリックします。
 
 {% endtab %}
 {% endtabs %}
 
-#### サーバー間の統合
+#### サーバー間統合
 
 クラウドモードとも呼ばれるこの統合は、SegmentからBrazeのREST APIにデータを転送する。Segmentの新しい[Brazeクラウドモード（Actions）](https://segment.com/docs/connections/destinations/catalog/braze-cloud-mode-actions/)フレームワークを使って、どのソースにもクラウドモードのデスティネーションを設定する。 
 
-サイド・バイ・サイドの統合とは異なり、サーバー間統合は、アプリ内メッセージング、コンテンツカード、自動プッシュトークン登録といったBrazeのUI機能をサポートしていない。また、クラウドモードでは利用できない[自動取得]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/#user-data-collection)データ（匿名ユーザーやデバイスレベルのフィールドなど）も存在する。
+サイドバイサイド統合とは異なり、サーバー間統合では、アプリ内メッセージング、コンテンツカード、自動プッシュトークン登録といった Brazeの UI 機能がサポートされていません。また、クラウドモードでは利用できない[自動取得]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/#user-data-collection)データ（匿名ユーザーやデバイスレベルのフィールドなど）も存在する。
 
 このデータとこれらの機能を使用したい場合は、サイド・バイ・サイド（デバイスモード）SDK統合の使用を検討すること。
 
-[Braze Cloud Mode（Actions）デスティネーションの](https://github.com/segmentio/action-destinations/tree/main/packages/destination-actions/src/destinations/braze)ソースコードはSegmentによって管理されている。
+[Braze Cloud Mode (Actions) destination](https://github.com/segmentio/action-destinations/tree/main/packages/destination-actions/src/destinations/braze) のソースコードは Segment によって管理されています。
 
 ### ステップ3:設定
 
-目的地の設定を定義する。すべての設定がすべてのデスティネーションタイプに適用されるわけではない。
+宛先の設定を定義します。すべての設定がすべての宛先タイプに適用されるわけではありません。
 
 {% tabs ローカル %}
-{% tab モバイル・デバイス・モード %}
+{% tab Mobile Device-Mode %}
 
 | セッティング | 説明 |
 | ------- | ----------- |
-| アプリ識別子 | 特定のアプリを参照するためのアプリ識別子。これは、Brazeダッシュボードの「**Manage Settings**」で確認できる。 | 
+| アプリ識別子 | 特定のアプリを参照するためのアプリ識別子。これは、Braze ダッシュボードの \[**設定の管理**] で確認できます。 | 
 | カスタムAPIエンドポイント<br>(SDKエンドポイント） | インスタンスに対応するBraze SDKエンドポイント（`sdk.iad-01.braze.com` など） | 
-| 終点領域 | あなたのBrazeインスタンス（US 01、US 02、EU 01など） | 
-| アプリ内の自動メッセージ登録を有効にする | アプリ内メッセージを手動で登録したい場合は、これを無効にする。 |
+| Endpoint region | あなたのBrazeインスタンス（US 01、US 02、EU 01など） | 
+| Enable automatic in-app message registration | アプリ内メッセージを手動で登録したい場合は、これを無効にする。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endtab %}
-{% tab ウェブ・デバイス・モード %}
+{% tab Web Device-Mode %}
 
 | セッティング | 説明 |
 | ------- | ----------- |
-| アプリ識別子 | 特定のアプリを参照するためのアプリ識別子。これは、Brazeダッシュボードの「**Manage Settings**」で確認できる。 | 
+| アプリ識別子 | 特定のアプリを参照するためのアプリ識別子。これは、Braze ダッシュボードの \[**設定の管理**] で確認できます。 | 
 | カスタムAPIエンドポイント<br>(SDKエンドポイント） | インスタンスに対応するBraze SDKエンドポイント（`sdk.iad-01.braze.com` など） | 
-| サファリウェブサイトのプッシュID | Safariプッシュをサポートしている場合、Safariプッシュ証明書を作成する際にAppleに提供したWebサイトプッシュID（`web` で始まる、たとえば、`web.com.example.domain` ）をこのオプションに指定する必要がある。 |
+| Safari website push ID | Safariプッシュをサポートしている場合、Safariプッシュ証明書を作成する際にAppleに提供したWebサイトプッシュID（`web` で始まる、たとえば、`web.com.example.domain` ）をこのオプションに指定する必要がある。 |
 | Braze Web SDKバージョン | 使用したいBraze Web SDKのバージョン |
-| アプリ内メッセージを自動送信する | デフォルトでは、ユーザーが受信可能なアプリ内メッセージはすべて、自動的にユーザーに配信される。アプリ内メッセージを手動で表示したい場合は、これを無効にする。 |
-| 素晴らしいフォントを読み込まない | Brazeはアプリ内のメッセージアイコンにFont Awesomeを使用している。デフォルトでは、Brazeは自動的にFontAwesome CDNからFontAwesomeを読み込む。この動作を無効にするには（例えば、あなたのサイトが FontAwesome のカスタマイズ版を使用しているため）、このオプションを`TRUE` に設定する。これを行う場合、FontAwesomeがあなたのサイトにロードされていることを確認する責任があることに注意すること - そうでない場合、アプリ内メッセージが正しくレンダリングされない可能性がある。 |
-| HTMLアプリ内メッセージを有効にする | このオプションを有効にすると、BrazeダッシュボードユーザーがHTMLアプリ内メッセージを使用できるようになる。 | 
-| アプリ内のメッセージを新しいタブで開く | デフォルトでは、アプリ内のメッセージクリックからのリンクは、メッセージごとにダッシュボードで指定された現在のタブまたは新しいタブに読み込まれる。このオプションを`TRUE` に設定すると、アプリ内メッセージのクリックによるすべてのリンクが新しいタブまたはウィンドウで強制的に開かれる。 |
-| アプリ内メッセージzインデックス | Brazeのデフォルトのz-indexを上書きするには、このオプションに値を指定する。 | 
-| 明示的なアプリ内メッセージの解除を要求する | デフォルトでは、アプリ内メッセージが表示されている場合、エスケープボタンを押すか、ページのグレーアウトした背景をクリックすると、メッセージが表示されなくなる。このオプションをtrueに設定すると、この動作を防ぎ、メッセージを解除するために明示的なボタンクリックを要求する。 |
-| トリガーアクションの最小間隔（秒 | デフォルトは30である。<br>デフォルトでは、トリガーアクションは、最後のトリガーアクションから少なくとも30秒が経過した場合にのみ発火する。このコンフィギュレーション・オプションに値を指定すると、デフォルトを独自の値で上書きすることができる。ユーザーへのスパム通知を避けるため、この値を10より小さくすることは推奨しない。|
-| サービス従業員の所在地 | デフォルトでは、Webプッシュ通知のためにユーザーを登録するとき、Brazeは、Webサーバーのルートディレクトリの`/service-worker.js` にある必要なサービスワーカーファイルを探す。サーバー上の別のパスでサービスワーカーをホストしたい場合、このオプションにファイルへの絶対パスを指定する。(例えば、`/mycustompath/my-worker.js`)。ここで値を設定すると、サイト上でのプッシュ通知の範囲が制限されることに注意。例えば、上記の例では、サービスワーカーファイルは`/mycustompath/` ディレクトリ内にあるため、`requestPushPermission` は`http://yoursite.com/mycustompath/` で始まるウェブページからのみ呼び出すことができる。 |
-| プッシュトークンのメンテナンスを無効にする | デフォルトでは、すでにウェブプッシュ許可を与えているユーザーは、配信可能性を確保するために、新しいセッションで自動的にBrazeバックエンドとプッシュトークンを同期する。この動作を無効にするには、このオプションを`FALSE` に設定する。 |
-| サービス・ワーカーを外部で管理する | 登録し、ライフサイクルを制御する独自のサービスワーカーがある場合、このオプションを`TRUE` に設定すると、Braze SDKはサービスワーカーを登録または登録解除しない。このオプションを`TRUE` に設定した場合、プッシュが正しく機能するためには、`requestPushPermission` を呼び出す前に自分でサービスワーカーを登録し、`self.importScripts('https://js.appboycdn.com/web-sdk-develop/4.1/service-worker.js');` を使うか、そのファイルの内容を直接含めるかして、Brazeのサービスワーカーコードが含まれていることを確認する必要がある。このオプションが`TRUE` の場合、`serviceWorkerLocation` オプションは無関係であり、無視される。 |
-| コンテンツ・セキュリティ・ノンス | このオプションに値を指定すると、Braze SDKは、SDKによって作成されたすべての`<script>` および`<style>` 要素にnonceを追加する。これにより、Braze SDKは、あなたのウェブサイトのコンテンツセキュリティポリシーと連動することができる。このnonceの設定に加えて、FontAwesomeの読み込みを許可する必要があるかもしれない。これは、コンテンツセキュリティポリシーのallowlistに`use.fontawesome.com` を追加するか、`doNotLoadFontAwesome` オプションを使用して手動で読み込むことでできる。 |
-| クローラーの活動を許可する | デフォルトでは、Braze Web SDKは、ユーザーエージェント文字列に基づいて、Googleなどの既知のスパイダーやウェブクローラーからのアクティビティを無視する。これはデータポイントを節約し、分析をより正確にし、ページランクを向上させる可能性がある。ただし、Brazeにこれらのクローラーからの活動を記録させたい場合は、このオプションを`TRUE` 。 |
-| ロギングを有効にする | デフォルトでロギングを有効にするには、`TRUE` に設定する。この場合、BrazeはJavaScriptコンソールにログを記録する。ページを本番環境にリリースする前に、これを削除するか、`setLogger` で代替のロガーを提供すべきである。 |
+| アプリ内メッセージを自動送信する | デフォルトでは、ユーザーが受信できるすべてのアプリ内メッセージは、自動的にユーザーに配信されます。アプリ内メッセージを手動で表示したい場合は、これを無効にする。 |
+| Do not load font awesome | Brazeはアプリ内のメッセージアイコンにFont Awesomeを使用している。デフォルトでは、Brazeは自動的にFontAwesome CDNからFontAwesomeを読み込む。この動作を無効にするには（例えば、あなたのサイトが FontAwesome のカスタマイズ版を使用しているため）、このオプションを`TRUE` に設定する。これを行う場合、FontAwesomeがあなたのサイトにロードされていることを確認する責任があることに注意すること - そうでない場合、アプリ内メッセージが正しくレンダリングされない可能性がある。 |
+| HTMLアプリ内メッセージを有効にする | このオプションを有効にすると、Braze ダッシュボードのユーザーが HTML アプリ内メッセージを使用できるようになります。 | 
+| アプリ内のメッセージを新しいタブで開く | デフォルトでは、アプリ内メッセージでクリックしたリンクは、現在のタブまたは新しいタブに読み込まれます。どちらのタブになるかは、ダッシュボードでメッセージごとに指定されています。このオプションを`TRUE` に設定すると、アプリ内メッセージのクリックによるすべてのリンクが新しいタブまたはウィンドウで強制的に開かれる。 |
+| アプリ内メッセージzインデックス | Braze のデフォルトの z-index をオーバーライドするには、このオプションに値を指定します。 | 
+| Require explicit in-app message dismissal | デフォルトでは、アプリ内メッセージが表示されている場合、エスケープボタンを押すか、ページのグレーアウトした背景をクリックすると、メッセージが表示されなくなる。このオプションをtrueに設定すると、この動作を防ぎ、メッセージを解除するために明示的なボタンクリックを要求する。 |
+| トリガーアクションの最小間隔（秒 | デフォルトは30です。<br>デフォルトでは、トリガーアクションは、前回のトリガーアクションから30秒以上が経過した場合にのみ実行されます。デフォルトを各自の値でオーバーライドするには、この設定オプションに値を指定します。ユーザーへのスパム通知を避けるため、この値を10より小さくすることは推奨しない。|
+| サービス従業員の所在地 | デフォルトでは、Webプッシュ通知のためにユーザーを登録するとき、Brazeは、Webサーバーのルートディレクトリの`/service-worker.js` にある必要なサービスワーカーファイルを探す。サーバー上の別のパスでサービスワーカーをホストする場合は、このオプションにファイルの絶対パスを指定します (例: `/mycustompath/my-worker.js`)。ここで値を設定すると、サイトでのプッシュ通知の範囲が制限されることに注意してください。たとえば上記の例では、サービスワーカーファイルは `/mycustompath/` ディレクトリ内にあるため、`requestPushPermission` は`http://yoursite.com/mycustompath/` で始まる Web ページからのみ呼び出すことができます。 |
+| プッシュトークンのメンテナンスを無効にする | デフォルトでは、確実に配信されるようにするため、すでに Web プッシュ通知の権限が付与されているユーザーが、新しいセッションでプッシュトークンを Braze バックグラウンドと自動的に同期します。この動作を無効にするには、このオプションを`FALSE` に設定する。 |
+| Manage service worker externally | 登録し、ライフサイクルを制御する独自のサービスワーカーがある場合、このオプションを`TRUE` に設定すると、Braze SDKはサービスワーカーを登録または登録解除しない。このオプションを `TRUE` に設定した場合、プッシュが正しく機能するためには、`requestPushPermission` を呼び出す前に自分自身でサービスワーカーを登録し、`self.importScripts('https://js.appboycdn.com/web-sdk-develop/4.1/service-worker.js');` を使用するかまたはそのファイルのコンテンツを直接インクルードすることで、Braze のサービスワーカーコードが含まれているようにする必要があります。このオプションが`TRUE` の場合、`serviceWorkerLocation` オプションは無関係であり、無視される。 |
+| Content security nonce | このオプションに値を指定すると、Braze SDK によって作成されたすべての `<script>` 要素と`<style>` 要素に nonce が追加されます。これにより Braze SDK は、Web サイトのコンテンツセキュリティポリシーを処理できるようになります。この nonce の設定に加えて、FontAwesome の読み込みを許可する必要があります。このためには、コンテンツセキュリティポリシー許可リストに `use.fontawesome.com` を追加するか、または `doNotLoadFontAwesome` オプションを使用して手動で読み込みます。 |
+| クローラーの活動を許可する | デフォルトでは、Braze Web SDK はエージェント文字列に基づいて、Google などの既知のスパイダーや Web クローラーからのアクティビティを無視します。これによりデータポイントを節約でき、分析がより正確になり、またページランクが向上する可能性があります。ただし、Braze にこれらのクローラーからのアクティビティを記録させる場合には、このオプションを `TRUE` に設定します。 |
+| ロギングを有効にする | デフォルトでロギングを有効にするには、`TRUE` に設定します。これにより Braze は、すべてのユーザーに対して表示される JavaScript コンソールにログを記録することに注意してください。ページを本番環境にリリースする前にこれを削除するか、`setLogger` で代替ロガーを指定する必要があります。 |
 | ニュースフィードのカードを新しいタブで開く（新しいタブでカードを開く） | デフォルトでは、カード・オブジェクトからのリンクは現在のタブまたはウィンドウに読み込まれる。カードからのリンクを新しいタブまたはウィンドウで開くようにするには、このオプションを`TRUE` に設定する。<br><br>**注:**ニュースフィードは非推奨になります。Braze では、News Feed ツールを使用するお客様は、コンテンツカードメッセージングチャネルに移動することを推奨しています。これは、より柔軟でカスタマイズ可能で、信頼性が高いチャネルです。詳しくは[マイグレーションガイド]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/migrating_from_news_feed/)をご覧ください。 |
-| ユーザー提供のJavaScriptを許可する | デフォルトでは、Braze Web SDKは、Brazeダッシュボードユーザーがサイト上でJavaScriptを実行できるように、ユーザーが提供するJavaScriptクリックアクションを許可しない。Brazeダッシュボードのユーザーが悪意のないJavaScriptクリックアクションを記述することを信頼することを示すには、このプロパティを`TRUE` に設定する。`enableHtmlInAppMessages` が`TRUE` の場合、このオプションも`TRUE` に設定される。 |
-| アプリ版| このオプションに値を指定すると、Brazeに送信されたユーザーイベントは、指定したバージョンに関連付けられ、ユーザーセグメンテーションに使用できる。 |
-| セッションタイムアウト（秒 | デフォルトは30である。<br>デフォルトでは、セッションは30分間操作がないとタイムアウトする。このコンフィギュレーション・オプションに値を指定すると、デフォルトを独自の値で上書きすることができる。 | 
-| デバイス・プロパティ allowlist | デフォルトでは、Braze SDKは自動的にすべてのデバイスプロパティを検出し、`DeviceProperties` で収集する。この動作をオーバーライドするには、`DeviceProperties` の配列を指定する。いくつかのプロパティがないと一部の機能が正しく機能しないことがあるので注意してください。たとえば、ローカルタイムゾーンの配信はタイムゾーンなしでは機能しません。 |
-| ローカライゼーション | デフォルトでは、SDKが生成したユーザー可視メッセージはすべて、ユーザーのブラウザ言語で表示される。その動作をオーバーライドして特定の言語を強制するには、このオプションに値を指定する。このオプションの値はISO 639-1言語コードでなければならない。 |
-| クッキーなし | デフォルトでは、Braze SDKは少量のデータ（ユーザーID、セッションID）をクッキーに保存する。これは、Brazeがサイトの異なるサブドメイン間でユーザーとセッションを認識できるようにするためである。これが問題になる場合は、このオプションに`TRUE` 。クッキーの保存を無効にし、ユーザーとセッションの識別をHTML 5のlocalStorageに完全に依存する。 |
-| すべてのページを追跡する | **クラシック・デスティネーション・ウェブ・デバイス・モード（メンテナンス）のみ**<br><br>Segmentでは、この設定を[マッピングで有効に](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping)できるWeb Actionsフレームワークへの移行を推奨している。<br><br>これにより、すべての[ページ呼び出しが](https://segment.com/docs/spec/page/)"Loaded/Viewed a Page "イベントとしてBrazeに送られる。 |
-| 指定されたページのみを追跡する | **クラシック・デスティネーション・ウェブ・デバイス・モード（メンテナンス）のみ**<br><br>Segmentでは、この設定を[マッピングで有効に](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping)できるWeb Actionsフレームワークへの移行を推奨している。<br><br>これでBrazeには、名前に関連づけられたページ・コールだけが送られる。 |
-| 収益がある場合、購入を記録する | **クラシック・デスティネーション・ウェブ・デバイス・モード（メンテナンス）のみ**<br><br>Segmentでは、この設定を[マッピングで有効に](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping)できるWeb Actionsフレームワークへの移行を推奨している。<br><br>このオプションを有効にすると、収益プロパティを持つすべてのTrackコールが購入イベントをトリガーする。 | 
-| 既知のユーザーのみを追跡する | **クラシック・デスティネーション・ウェブ・デバイス・モード（メンテナンス）のみ**<br><br>Segmentでは、マッピングによってこの設定を有効にできるWeb Actions Frameworkへの移行を推奨している。<br><br>この新しい設定を有効にすると、有効な`userId` まで、`window.appboy.initialize` の呼び出しを遅らせる。 | 
+| ユーザー提供のJavaScriptを許可する | デフォルトでは、Braze Web SDK は、ユーザー提供の JavaScript クリックアクションを許可しません。これは、このアクションにより、Braze ダッシュボードのユーザーがサイトで JavaScript を実行できるようになるためです。Brazeダッシュボードのユーザーが悪意のないJavaScriptクリックアクションを記述することを信頼することを示すには、このプロパティを`TRUE` に設定する。`enableHtmlInAppMessages` が`TRUE` の場合、このオプションも`TRUE` に設定されます。 |
+| App version| このオプションに値を指定すると、Brazeに送信されたユーザーイベントは、指定したバージョンに関連付けられ、ユーザーセグメンテーションに使用できる。 |
+| セッションタイムアウト（秒 | デフォルトは30です。<br>デフォルトでは、セッションは30分間操作がないとタイムアウトする。デフォルトを各自の値でオーバーライドするには、この設定オプションに値を指定します。 | 
+| Device property allowlist | デフォルトでは、Braze SDK は `DeviceProperties` のすべてのデバイスプロパティを自動的に検出して収集します。この動作をオーバーライドするには、`DeviceProperties` の配列を指定する。いくつかのプロパティがないと一部の機能が正しく機能しないことがあるので注意してください。たとえば、ローカルタイムゾーンの配信はタイムゾーンなしでは機能しません。 |
+| ローカライゼーション | デフォルトでは、SDK により生成されたユーザーに対して表示されるメッセージはすべて、ユーザーのブラウザーで設定されている言語で表示されます。その動作をオーバーライドして特定の言語を強制するには、このオプションに値を指定する。このオプションの値は ISO 639-1言語コードでなければなりません。 |
+| クッキーなし | デフォルトでは、Braze SDKは少量のデータ（ユーザーID、セッションID）をクッキーに保存する。これは、Brazeがサイトの異なるサブドメイン間でユーザーとセッションを認識できるようにするためである。これで問題が発生する場合は、このオプションに `TRUE` を渡して Cookie の保存を無効にし、HTML 5 localStorage のみを使用してユーザーとセッションを識別します。 |
+| すべてのページを追跡する | **Classic Destination Web Device-Mode (メンテナンス) のみ**<br><br>Segment は、この設定を Web Actions フレームワーク宛先に移行することを推奨しています。Web Actions フレームワーク宛先では、この設定を[マッピングによって有効にできます](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping)。<br><br>これにより、すべての[ページ呼び出し](https://segment.com/docs/spec/page/)が "Loaded/Viewed a Page "イベントとして Braze に送信されます。 |
+| 指定されたページのみを追跡する | **Classic Destination Web Device-Mode (メンテナンス) のみ**<br><br>Segment は、この設定を Web Actions フレームワーク宛先に移行することを推奨しています。Web Actions フレームワーク宛先では、この設定を[マッピングによって有効にできます](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping)。<br><br>これにより、ページ呼び出しとそれに関連付けられている名前のみが Braze に送信されます。 |
+| Log purchase when revenue is present | **Classic Destination Web Device-Mode (メンテナンス) のみ**<br><br>Segment は、この設定を Web Actions フレームワーク宛先に移行することを推奨しています。Web Actions フレームワーク宛先では、この設定を[マッピングによって有効にできます](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping)。<br><br>このオプションを有効にすると、収益プロパティを持つすべてのTrackコールが購入イベントをトリガーする。 | 
+| 既知のユーザーのみを追跡する | **Classic Destination Web Device-Mode (メンテナンス) のみ**<br><br>Segment は、この設定を Web Actions フレームワーク宛先に移行することを推奨しています。Web Actions フレームワーク宛先では、この設定をマッピングによって有効にできます。<br><br>有効にすると、この新しい設定により、有効な`userId` が存在するまで `window.appboy.initialize` の呼び出しが遅延します。 | 
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endtab %}
-{% tab クラウドモード %}
+{% tab Cloud-Mode %}
 
 | セッティング | 説明 |
 | ------- | ----------- |
-| アプリ識別子 | 特定のアプリを参照するためのアプリ識別子。これは、Brazeダッシュボードの「**Manage Settings**」で確認できる。 | 
+| アプリ識別子 | 特定のアプリを参照するためのアプリ識別子。これは、Braze ダッシュボードの \[**設定の管理**] で確認できます。 | 
 | REST APIキー | これは、Brazeダッシュボードの**「設定」**>「**APIキー**」で確認できる。 | 
 | カスタムREST APIエンドポイント | インスタンスに対応するBraze RESTエンドポイント（rest.iad-01.braze.com など）。 | 
-| 既存ユーザーのみを更新する | **クラシック・デスティネーション クラウドモード（メンテナンス）のみ**<br><br>セグメントでは、[マッピングによって](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping)この設定を[有効に](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping)できるCloud Actions Frameworkデスティネーションへの移行を推奨している。<br><br>既存のユーザーのみを更新するかどうかを決定する。 |
+| 既存ユーザーのみを更新する | **Classic Destination Cloud-Mode (メンテナンス) のみ**<br><br>Segment は、この設定を Cloud Actions フレームワーク宛先に移行することを推奨しています。Cloud Actions フレームワーク宛先では、この設定を[マッピングによって有効にできます](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#braze-web-settings-mapping)。<br><br>既存のユーザーのみを更新するかどうかを決定する。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endtab %}
 {% endtabs %}
 
-### ステップ4:地図メソッド {#methods}
+### ステップ4:メソッドをマッピングする {#methods}
 
-Brazeは、[Page](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#page)メソッド、[Identify](https://segment.com/docs/spec/identify/)メソッド、[Track](https://segment.com/docs/spec/track/)Segmentメソッドをサポートしている。これらの方法で使用される識別子の種類は、データがサーバー間（クラウドモード）で送信されるのか、サイドバイサイド（デバイスモード）で送信されるのかによって異なる。Braze Web Mode ActionsとCloud Mode Actionsの宛先では、[セグメントエイリアス通話の](https://segment.com/docs/connections/spec/alias/)マッピングを設定することもできる。 
+Brazeは、[Page](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#page)メソッド、[Identify](https://segment.com/docs/spec/identify/)メソッド、[Track](https://segment.com/docs/spec/track/)Segmentメソッドをサポートしている。これらのメソッドで使用される識別子の種類は、データがサーバー間統合 (cloud-mode) で送信されるのか、サイドバイサイド (device-mode) で送信されるのかによって異なります。Braze Web Mode Actions 宛先と Cloud Mode Actions 宛先では、[Segment エイリアス呼び出し](https://segment.com/docs/connections/spec/alias/)のマッピングを設定することもできます。 
 
 {% alert note %}
-ユーザーエイリアスは、Brazeクラウドモード（Actions）デスティネーションの識別子としてサポートされているが、Segmentのエイリアス呼び出しは、Brazeユーザーエイリアスとは直接関係ないことに注意すべきである。
+ユーザーエイリアスは、Braze Cloud Mode (Actions) 宛先の識別子としてサポートされていますが、Segment のエイリアス呼び出しは、Braze ユーザーエイリアスとは直接関係ないことに注意してください。
 {% endalert %}
 
-| 識別子タイプ | サポート先 |
+| 識別子タイプ | サポートされている宛先 |
 | --------------- | --------------------- |
 | `userId` (`external_id`) | すべて |
-| 匿名ユーザー | デバイス・モードの目的地 |
-| ユーザーエイリアス | クラウドモードの目的地 |
+| 匿名ユーザー | Device mode の宛先 |
+| ユーザーエイリアス | Cloud mode の宛先 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-クラウドモード（Actions）デスティネーションには、[エイリアスの作成（Create Alias）アクションが](https://segment.com/docs/connections/destinations/catalog/actions-braze-cloud/#create-alias)あり、エイリアスのみのユーザーを作成したり、既存の`external_id` プロファイルにエイリアスを追加したりするのに使用できる。[ユーザーの識別（Identify User）アクションは](https://segment.com/docs/connections/destinations/catalog/actions-braze-cloud/#identify-user)、エイリアスの作成（Create Alias）アクションと並行して使用することができ、そのユーザーが使用可能になった後、エイリアスのみのユーザーを`external_id` 。 
+Cloud Mode (Actions) 宛先にある [Create Alias アクション](https://segment.com/docs/connections/destinations/catalog/actions-braze-cloud/#create-alias)を使用して、エイリアスのみのユーザーを作成したり、既存の `external_id` プロファイルにエイリアスを追加したりできます。[ユーザーの識別（Identify User）アクションは](https://segment.com/docs/connections/destinations/catalog/actions-braze-cloud/#identify-user)、エイリアスの作成（Create Alias）アクションと並行して使用することができ、そのユーザーが使用可能になった後、エイリアスのみのユーザーを`external_id` 。 
 
-回避策を考え、`braze_id` 、クラウドモードで匿名のユーザーデータを送信することも可能だ。そのため、すべてのSegment APIコールにユーザーの`braze_id` を手動で含める必要がある。この回避策の設定方法については、[Segmentのドキュメントを](https://segment.com/docs/connections/destinations/catalog/braze/#capture-the-braze_id-of-anonymous-users)参照されたい。
+回避策を考案し`braze_id` を使用して cloud-mode で匿名ユーザーのデータを送信することもできます。そのため、すべてのSegment APIコールにユーザーの`braze_id` を手動で含める必要がある。この回避策の設定方法については、[Segmentのドキュメントを](https://segment.com/docs/connections/destinations/catalog/braze/#capture-the-braze_id-of-anonymous-users)参照されたい。
 
-Brazeに送信される宛先データは、クラウドモードアクション内でバッチ処理できる。バッチサイズの上限は75イベントであり、これらのバッチはフラッシュされる前に30秒間蓄積される。リクエストのバッチ処理はアクションごとに行われる。例えば、Identify Calls（属性）はリクエストにバッチされ、Track Calls（カスタムイベント）は2番目のリクエストにバッチされる。SegmentからBrazeに送信されるリクエストの数を減らすことができるため、Brazeはこの機能を有効にすることを推奨している。その結果、デスティネーションがBrazeのレート制限にヒットし、リクエストをリトライするリスクを減らすことができる。 
+Braze に送信される宛先データは、Cloud Mode Actions 内でバッチ処理できます。バッチサイズの上限は75イベントであり、これらのバッチはフラッシュされる前に30秒間蓄積される。リクエストのバッチ処理はアクションごとに実行されます。たとえば、Identify Calls (属性) が1つのリクエストでバッチ処理され、Track Calls (カスタムイベント) が2番目のリクエストでバッチ処理されます。SegmentからBrazeに送信されるリクエストの数を減らすことができるため、Brazeはこの機能を有効にすることを推奨している。その結果、宛先が Braze のレート制限に達してリクエストを再試行するリスクが減少します。 
 
-Braze Destination >**Mappingsに**移動して、アクションのバッチ処理をオンにできる。そこから、マッピングの右側にある3つの点のアイコンをクリックし、**マッピングの編集を**選択する。**Select mappings**セクションの一番下までスクロールし、**Batch Data to Brazeが** **Yesに**設定されていることを確認する。
+\[Braze Destination] > \[**Mappings**] に移動して、アクションのバッチ処理をオンにできます。そこから、マッピングの右側にある3つのドットのアイコンをクリックし、\[**Edit Mapping**] を選択します。**Select mappings**セクションの一番下までスクロールし、**Batch Data to Brazeが** **Yesに**設定されていることを確認する。
 
 
 {% tabs ローカル %}
-{% tab 特定する %}
+{% tab Identify %}
 #### 特定する
 
 [Identify](https://segment.com/docs/spec/identify/)コールは、ユーザーをその行動に結びつけ、そのユーザーに関する属性を記録することができる。 
 
 特定のセグメント特殊特性は、Brazeの標準的な属性プロファイルフィールドにマッピングされる：
 
-| 特別セグメントの特徴 | ブレージング標準属性 |
+| Segment の特別な特性 | Braze の標準属性項目 |
 | ------------- | ----------- |
 | `userId` | `external_id` |
 | `firstName` | `first_name` |
@@ -262,16 +262,16 @@ Braze Destination >**Mappingsに**移動して、アクションのバッチ処
 | `gender` | `gender` |
 {: .reset-td-br-1 .reset-td-br-2}
 
-`email_subscribe` 、`push_subscribe` などの予約済みBrazeプロファイルフィールドは、Brazeのこれらのフィールドの命名規則を使用し、identifyコール内でtraitとして渡すことで送信できる。
+`email_subscribe` や `push_subscribe` などのその他の予約済み Braze プロファイルフィールドを送信するには、これらのフィールドに Braze 命名規則を使用して、identify 呼び出しでこれらを特性として渡します。
 
-##### 購読グループにユーザーを追加する
+##### サブスクリプショングループにユーザーを追加する
 
 traits パラメータの以下のフィールドを使用して、指定されたサブスクリプショングループからユーザーをサブスクライブまたはアンサブスクライブすることもできる。
 
-`braze_subscription_groups` という予約済みのBrazeプロファイル・フィールドを使用し、オブジェクトの配列と関連付けることができる。配列の各オブジェクトは、2つの予約キーを持っていなければならない：
+`braze_subscription_groups` という予約済みの Braze プロファイルフィールドを使用します。このフィールドは、オブジェクト配列に関連付けることができます。配列の各オブジェクトに2つの予約キーが含まれている必要があります。
 
-1. `subscription_group_state`:ユーザーが特定のサブスクリプショングループに`"subscribed"` 、または`"unsubscribed"` 。
-2. `subscription_group_id`:サブスクリプショングループの一意の ID を表す。このIDは、Brazeダッシュボードの「**Subscription Group Management**」で確認できる。
+1. `subscription_group_state`:特定のサブスクリプショングループに対してユーザーが `"subscribed"` または`"unsubscribed"` のいずれであるかを示します。
+2. `subscription_group_id`:サブスクリプショングループの一意の ID を表す。この ID は、Braze ダッシュボードの \[**サブスクリプショングループ管理**] で確認できます。
 
 {% subtabs %}
 {% subtab Swift %}
@@ -342,43 +342,43 @@ analytics.identify(
 
 その他の特徴はすべて[カスタム属性として]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/)記録される。
 
-| セグメント方式 | ろう付け法 | 例 |
+| Segment での方法 | Braze での方法 | 例 |
 |---|---|---|
-| ユーザーIDで識別する | 外部IDを設定する | セグメントだ：  `analytics.identify("dawei");`<br>ブレイズだ： `Braze.changeUser("dawei")` |
-| 控えめな特徴を識別する | ユーザー属性を設定する | セグメントだ： `analytics.identify({email: "dawei@braze.com"});`<br> ブレイズだ： `Braze.getUser().setEmail("dawei@braze.com");`
-| カスタム特性で識別する | カスタム属性を設定する | セグメントだ： `analytics.identify({fav_cartoon: "Naruto"});`<br>ブレイズ：`Braze.getUser().setCustomAttribute("fav_cartoon": "Naruto")` ；
-| ユーザーIDと特徴を識別する | セグメントだ：外部IDと属性を設定する | 先の方法を組み合わせる。 |
+| ユーザーIDで識別する | 外部IDを設定する | Segment:  `analytics.identify("dawei");`<br>Braze: `Braze.changeUser("dawei")` |
+| 予約済み特性で識別する | ユーザー属性を設定する | Segment: `analytics.identify({email: "dawei@braze.com"});`<br> Braze: `Braze.getUser().setEmail("dawei@braze.com");`
+| カスタム特性で識別する | カスタム属性を設定する | Segment: `analytics.identify({fav_cartoon: "Naruto"});`<br>Braze: `Braze.getUser().setCustomAttribute("fav_cartoon": "Naruto")`;
+| ユーザー ID と特性で識別する | Segment:external ID と属性を設定する | 先の方法を組み合わせる。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-[Web Mode Actionsと](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#update-user-profile) [Cloud Mode Actionsの](https://segment.com/docs/connections/destinations/catalog/braze-cloud-mode-actions/#update-user-profile)宛先では、Update User Profile Actionを使って上記のマッピングを設定できる。
+[Web Mode Actions](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#update-user-profile) 宛先と [Cloud Mode Actions](https://segment.com/docs/connections/destinations/catalog/braze-cloud-mode-actions/#update-user-profile) 宛先では、Update User Profile Action を使用して前述のマッピングを設定できます。
 
 {% alert important %}
-ユーザー属性データを渡すときは、前回の更新以降に変更された属性の値のみを渡すようにする。こうすることで、不必要にデータポイントを消費することがなくなる。クライアント側のソースについては、Segmentのオープンソースの[ミドルウェアツールを](https://github.com/segmentio/segment-braze-mobile-middleware)使用して、統合を最適化し、Segmentからの重複した`identify()` 呼び出しをデバウンスすることで、データポイントの使用量を制限する。 
+ユーザー属性データを渡すときは、前回の更新以降に変更された属性の値のみを渡すようにする。こうすることで、データポイントを不必要に消費することがなくなります。クライアントサイドのソースについては、Segment のオープンソース [Middleware](https://github.com/segmentio/segment-braze-mobile-middleware) ツール使用して統合を最適化し、Segment からの重複した `identify()` 呼び出しをデバウンスすることで、データポイント使用量を制限します。 
 
 {% endalert %}
 {% endtab %}
 
-{% tab トラック %}
-#### トラック
+{% tab Track %}
+#### Track
 
 あなたがイベントを追跡するとき、私たちは提供された名前を使用して[カスタムイベントとして]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-events)そのイベントを記録する。 
 
 トラックコールのプロパティオブジェクト内で送信されたメタデータは、関連イベントのカスタムイベントプロパティとしてBrazeに記録される。すべての[カスタムイベントプロパティデータタイプが](https://www.braze.com/docs/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-properties)サポートされている。
 
-[Web Mode Actionsと](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#track-event) [Cloud Mode Actionsの](https://segment.com/docs/connections/destinations/catalog/braze-cloud-mode-actions/#track-event)デスティネーションでは、Track Event Actionを使って上記のマッピングを設定できる。
+[Web Mode Actions](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#track-event) 宛先と [Cloud Mode Actions](https://segment.com/docs/connections/destinations/catalog/braze-cloud-mode-actions/#track-event) 宛先では、Track Event Action を使用して前述のマッピングを設定できます。
 
-| セグメント方式 | ろう付け法 | 例 |
+| Segment での方法 | Braze での方法 | 例 |
 |---|---|---|
-| [トラック](https://segment.com/docs/spec/track/) | [カスタムイベントとして]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-events)記録される。 | セグメントだ： `analytics.track("played_game");`<br>ブレイズだ： `Braze.logCustomEvent("played_game");`|
-| [物件を追跡する](https://segment.com/docs/spec/track/) | [イベントプロパティとして]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-properties)記録される。 | セグメントだ： `analytics.track("played_game", {name: "BotW", weapon: "boomerang"});`<br>ブレイズだ： `Braze.logCustomEvent("played_game", { "name": "BotW", "weapon": "boomerang"});` |
-| [製品で追跡する](https://segment.com/docs/spec/track/) | [購入イベントとして]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/logging_purchases/)記録される。 | セグメントだ： `analytics.track("Order Completed", {products: [product_id: "ab12", price: 19]});`<br>ブレイズだ： `Braze.logPurchase("ab12", 19);` |
+| [追跡](https://segment.com/docs/spec/track/) | [カスタムイベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-events)として記録される | Segment: `analytics.track("played_game");`<br>Braze: `Braze.logCustomEvent("played_game");`|
+| [プロパティを使用した追跡](https://segment.com/docs/spec/track/) | [イベントプロパティ]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-properties)として記録される | Segment: `analytics.track("played_game", {name: "BotW", weapon: "boomerang"});`<br>Braze: `Braze.logCustomEvent("played_game", { "name": "BotW", "weapon": "boomerang"});` |
+| [製品を使用した追跡](https://segment.com/docs/spec/track/) | [購入イベント]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/logging_purchases/)として記録される。 | Segment: `analytics.track("Order Completed", {products: [product_id: "ab12", price: 19]});`<br>Braze: `Braze.logPurchase("ab12", 19);` |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ##### 注文完了 {#order-completed}
 
-Segmentの[EコマースAPIに](https://segment.com/docs/spec/ecommerce/v2/)記載されているフォーマットを使用して、`Order Completed` という名前でイベントをトラッキングすると、あなたが[購入として]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/exporting_revenue_data/#revenue-data)リストアップした商品が記録される。
+Segment の [Ecommerce API](https://segment.com/docs/spec/ecommerce/v2/) で説明されている形式を使用して、`Order Completed` という名前のイベントを追跡すると、リストした製品が[購入]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/exporting_revenue_data/#revenue-data)として記録されます。
 
-[Web Mode Actionsと](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#track-purchase) [Cloud Mode Actionsの](https://segment.com/docs/connections/destinations/catalog/braze-cloud-mode-actions/#track-purchase)宛先では、Track Purchase Actionでデフォルトのマッピングをカスタマイズできる。
+[Web Mode Actions](https://segment.com/docs/connections/destinations/catalog/braze-web-device-mode-actions/#track-purchase) 宛先と [Cloud Mode Actions](https://segment.com/docs/connections/destinations/catalog/braze-cloud-mode-actions/#track-purchase) 宛先では、Track Purchase Action でデフォルトのマッピングをカスタマイズできます。
 
 {% endtab %}
 
@@ -387,7 +387,7 @@ Segmentの[EコマースAPIに](https://segment.com/docs/spec/ecommerce/v2/)記
 
 [Page](https://segment.com/docs/spec/page/)コールは、ユーザーがあなたのウェブサイトのページを見るたびに、ページに関するオプションのプロパティとともに記録することができる。
 
-このイベントタイプは、Web Mode ActionsとCloud Actionsのデスティネーションでトリガーとして使用し、カスタムイベントをBrazeに記録することができる。
+このイベントタイプを、Web Mode Actions 宛先と Cloud Actions 宛先でトリガーとして使用して、カスタムイベントを Braze に記録することができます。
 {% endtab %}
 
 {% endtabs %}
@@ -396,60 +396,60 @@ Segmentの[EコマースAPIに](https://segment.com/docs/spec/ecommerce/v2/)記
 
 サイドバイサイド（デバイスモード）統合を使用する場合、[概要][27]メトリクス（ライフタイムセッション、MAU、DAU、スティッキネス、デイリーセッション、MAUあたりのデイリーセッション）を使用して、BrazeがSegmentからデータを受信していることを確認できる。
 
-[カスタムイベントや][22] [収益][28]ページ、または[セグメントを作成する][23]ことでデータを見ることができる。ダッシュボードの**カスタム・イベント**・ページでは、カスタム・イベントのカウントを時系列で見ることができる。サーバー間（クラウドモード）統合を使用している場合、MAUとDAU統計を含む[計算式を][24]使用することはできないことに注意。
+[カスタムイベント][22]ページまたは[収益][28]ページでデータを確認するか、または[セグメントを作成する][23]ことでデータを確認できます。ダッシュボードの**カスタム・イベント**・ページでは、カスタム・イベントのカウントを時系列で見ることができる。サーバー間（クラウドモード）統合を使用している場合、MAUとDAU統計を含む[計算式を][24]使用することはできないことに注意。
 
-Brazeに購入データを送信している場合（[ステップ](#methods)3の**Track**タブで注文完了を参照）、[収益][28]ページで特定の期間の収益や購入に関するデータ、またはアプリの総収益を確認できる。
+Braze に購入データを送信する場合 ([ステップ3](#methods) の「**Track**」タブの「Ｏｒｄｅｒ Completed」を参照)、[収益][28]ページで特定の期間の収益や購入に関するデータ、またはアプリの総収益を確認できます。
 
 [セグメントを作成すること][26]で、カスタムイベントと属性データに基づいてユーザーをフィルタリングすることができる。
 
 {% alert important %}
-サーバー間統合（クラウドモード）を使用している場合、自動的に収集されたセッションデータ（「最初に使用したアプリ」や「最後に使用したアプリ」など）に関連するフィルターは機能しない。SegmentとBrazeの統合でこれらを使用したい場合は、サイドバイサイド統合（デバイスモード）を使用する。
+サーバー間統合 (cloud-mode) を使用する場合、自動的に収集されたセッションデータに関連するフィルター (「最初に使用したアプリ」や「最後に使用したアプリ」など) は機能しません。Segment とBraze の統合でこれらを使用する場合は、サイドバイサイド統合 (デバイスモード) を使用してください。
 {% endalert %}
 
 ## ユーザーの削除と抑制 
 
-ユーザーを削除または抑制する必要がある場合は、[Segmentのユーザー削除](https://segment.com/docs/privacy/user-deletion-and-suppression/#which-destinations-can-i-send-deletion-requests-to) **機能が**Braze[`/users/delete` エンドポイントに]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/)マッピングされて**いる**ことに注意。これらの削除の検証には最大30日かかる可能性があることに注意してほしい。
+ユーザーを削除または抑制する必要がある場合は、[Segment のユーザー削除機能](https://segment.com/docs/privacy/user-deletion-and-suppression/#which-destinations-can-i-send-deletion-requests-to)**が** Braze [`/users/delete` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/)にマッピングされていることに注意してください。これらの削除の検証には最大30日かかる可能性があることに注意してほしい。
 
-BrazeとSegmentの間で共通のユーザー識別子を選択する必要がある（`external_id` のように）。Segmentで削除リクエストを開始すると、Segmentダッシュボードの削除リクエストタブでステータスを確認できる。
+(`external_id` と同様に) Braze と Segment の間で共通のユーザー識別子を選択する必要があります。Segment で削除リクエストを開始した後は、Segment ダッシュボードの削除リクエストのタブでステータスを確認できます。
 
-## セグメント・リプレイ
+## Segment のリプレイ機能
 
-セグメントは顧客に対して、すべての履歴データを新しいテクノロジー・パートナーに「再生」するサービスを提供している。関連するすべての履歴データをインポートしたいBrazeの新規顧客は、Segmentを通じてインポートできる。もし興味があれば、セグメント担当者に相談してほしい。
+Segment は、新しいテクノロジーパートナーに対してすべての履歴データを「再生」するサービスをクライアントに提供しています。関連するすべての履歴データをインポートすることを望む Braze の新しいお客様は、Segment を介してインポートできます。この機能に興味がある場合は Segment の担当者にお問い合わせください。
 
 Segmentが当社の[`/users/track` エンドポイントに]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)接続し、ユーザーに代わってBrazeにユーザーデータをインポートする。
 
 {% alert important %}
-クラウドモード・アクションの宛先でサポートされているすべての識別子は、セグメント・リプレイの一部としてサポートされている。
+Cloud Mode Actions 宛先でサポートされているすべての識別子は、Segment のリプレイの一部としてサポートされています。
 {% endalert %}
 
 ## ベストプラクティス
 
 {% details データ超過を避けるために使用例を見直す。 %}
 
-セグメントは**、**クライアントが送信するデータエレメントの数を制限**しない**。セグメントを使えば、すべてのイベントをBrazeに送ることも、どのイベントを送るかを決めることもできる。Segmentを使ってすべてのイベントを送信するのではなく、マーケティングチームや編集チームとユースケースを検討し、データオーバーを避けるためにBrazeに送信するイベントを決定することをお勧めする。
+Segment では、クライアントが送信できるデータエレメントの数は制限**されていません**。セグメントを使えば、すべてのイベントをBrazeに送ることも、どのイベントを送るかを決めることもできる。Segmentを使ってすべてのイベントを送信するのではなく、マーケティングチームや編集チームとユースケースを検討し、データオーバーを避けるためにBrazeに送信するイベントを決定することをお勧めする。
 
 {% enddetails %}
 
 {% details モバイルデバイスモード宛先設定のカスタムAPIエンドポイントとカスタムREST APIエンドポイントの違いを理解する。 %}
 
-| ブレイズ用語 | セグメントに相当する |
+| ブレイズ用語 | Segment で対応する用語 |
 | ----------------- | ------------------ |
 | Braze SDKエンドポイント | カスタムAPIエンドポイント |
 | Braze RESTエンドポイント | カスタムREST APIエンドポイント |
 {: .reset-td-br-1 .reset-td-br-2}
 
-あなたのBraze APIエンドポイント（Segmentでは「カスタムAPIエンドポイント」と呼ばれる）は、BrazeがあなたのSDKのために設定するSDKエンドポイントである（例えば、`sdk.iad-03.braze.com` ）。あなたのBraze REST APIエンドポイント（Segmentでは「カスタムREST APIエンドポイント」と呼ばれる）は、REST APIエンドポイント（例えば、`https://rest.iad-03.braze.com` ）である。
+Braze API エンドポイント (Segment では「Custom API Ednpoint」と呼ばれます) は、SDK のために Braze により設定される SDK エンドポイントです (例: `sdk.iad-03.braze.com`)。Braze REST API エンドポイント (Segment では「Custom REST API Endpoint」と呼ばれます) は、REST API エンドポイントです (例: `https://rest.iad-03.braze.com`)。
 {% enddetails %}
 
 {% details カスタムAPIエンドポイントがモバイルデバイスモードの宛先設定に正しく入力されていることを確認する。 %}
 
-| ブレイズ用語 | セグメントに相当する |
+| ブレイズ用語 | Segment で対応する用語 |
 | ----------------- | ------------------ |
 | Braze SDKエンドポイント | カスタムAPIエンドポイント |
 | Braze RESTエンドポイント | カスタムREST APIエンドポイント |
 {: .reset-td-br-1 .reset-td-br-2}
 
-Braze SDKのエンドポイントを正しく入力するために、適切なフォーマットに従わなければならない。あなたのBraze SDKエンドポイントは、`https://` (例えば、`sdk.iad-03.braze.com`)を含んではならない。そうでなければ、Braze統合は壊れる。これは、Segmentが自動的にエンドポイントの先頭に`https://` を付けるためで、その結果、Brazeは無効なエンドポイント`https://https://sdk.iad-03.braze.com` で初期化される。
+Braze SDK のエンドポイントを正しく入力するには、適切な形式に従う必要があります。Braze SDK エンドポイントには `https://` を含めないでください (例: `sdk.iad-03.braze.com`)。このようにしないと、Braze 統合が機能しなくなります。これは、Segment によりエンドポイントの先頭に `https://` が自動的に付加され、その結果、Braze は無効なエンドポイント `https://https://sdk.iad-03.braze.com` で初期化されことになるためです。
 
 {% enddetails %}
 
@@ -458,29 +458,29 @@ Braze SDKのエンドポイントを正しく入力するために、適切な
 データが期待通りに通過しないシナリオ：
 
 1. 階層化カスタム属性
-  - [ネストされたカスタム属性は]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/)、技術的にはSegmentを通してBrazeに送信できるが、**ペイロード全体が**毎回送信される。これにより、ペイロードが送信されるたびに、ネストされたオブジェクトに渡されたキーごとに[データポイントが]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/#data-points)発生する。<br><br> ペイロードの送信時にデータポイントのサブセットのみを使用するには、Segmentが持つカスタム[宛先関数](https://segment.com/docs/connections/functions/destination-functions/)機能を使用することができる。Segmentプラットフォームのこの機能により、下流へのデータ送信方法をカスタマイズすることができる。
+  - [ネストされたカスタム属性は]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/)、技術的にはSegmentを通してBrazeに送信できるが、**ペイロード全体が**毎回送信される。これにより、ペイロードが送信されるたびに、ネストされたオブジェクトに渡されたキーごとに[データポイントが]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/#data-points)発生する。<br><br> ペイロードの送信時にデータポイントのサブセットのみを使用するには、Segment のカスタム[宛先関数](https://segment.com/docs/connections/functions/destination-functions/)機能を使用できます。Segment プラットフォームのこの機能により、ダウンストリームの宛先へのデータの送信方法をカスタマイズできます。
 
   {% alert note %}
-  カスタムデスティネーション機能はセグメント内で制御され、外部で設定された機能に対するBrazeの洞察力は限られている。
+  カスタム宛先関数は Segment 内で管理されるため、Braze では外部で設定されているこの関数に関する情報は限られています。
   {% endalert %}
 
 {: start="2"}
-2\.匿名データをサーバー間で受け渡す。
-  - 顧客は、Segmentのサーバー間ライブラリを使用して、匿名データを他のシステムに流すことができる。サーバー間（クラウドモード）統合で、`external_id` のないユーザーをBrazeに送る方法については、マップ方法のセクションを参照のこと。
+2\.サーバー間で匿名データを受け渡す。
+  - 顧客は、Segment のサーバー間ライブラリを使用して、匿名データを他のシステムに渡すことができます。サーバー間 (cloud-mode) 統合を介して `external_id` を持たないユーザーを Braze に送信する方法については、「メソッドをマッピングする」セクションを参照してください。
 
 {% enddetails %}
 
 {% details Brazeの初期化をカスタマイズする。 %}
 
-Brazeのカスタマイズには、プッシュ、アプリ内メッセージ、コンテンツカード、初期化など、いくつかの方法がある。サイドバイサイドの統合でも、Brazeとの直接統合と同様に、プッシュ、アプリ内メッセージ、コンテンツカードをカスタマイズできる。
+Brazeのカスタマイズには、プッシュ、アプリ内メッセージ、コンテンツカード、初期化など、いくつかの方法がある。サイドバイサイド統合では、Braze の直接統合と同様に、プッシュ、アプリ内メッセージ、コンテンツカードをカスタマイズできます。
 
-しかし、Braze SDKを統合する際のカスタマイズや初期化設定の指定は困難であり、場合によっては不可能なこともある。これは、Segmentの初期化時にBraze SDKが初期化されるためである。
+ただし Braze SDK の統合時にカスタマイズを行うこと、または初期化設定を指定することは難しく、場合によっては不可能なことがあります。これは、Segment の初期化時に Segment により Braze SDK が初期化されるためです。
 
 {% enddetails %}
 
-{% details ブレーズにデルタを送る。 %}
+{% details Braze に差分を送信する。 %}
 
-ユーザー属性データを渡すときは、前回の更新以降に変更された属性の値のみを渡すようにする。こうすることで、不必要にデータポイントを消費することがなくなる。クライアント側のソースについては、Segmentのオープンソースの[ミドルウェアツールを](https://github.com/segmentio/segment-braze-mobile-middleware)使用して、統合を最適化し、Segmentからの重複した`identify()` 呼び出しをデバウンスすることで、データポイントの使用量を制限する。 
+ユーザー属性データを渡すときは、前回の更新以降に変更された属性の値のみを渡すようにする。こうすることで、データポイントを不必要に消費することがなくなります。クライアントサイドのソースについては、Segment のオープンソース [Middleware](https://github.com/segmentio/segment-braze-mobile-middleware) ツール使用して統合を最適化し、Segment からの重複した `identify()` 呼び出しをデバウンスすることで、データポイント使用量を制限します。 
 
 {% enddetails %}
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage.md
index e0f5599e5ec..679abd2a0b3 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_engage.md
@@ -1,6 +1,6 @@
 ---
-nav_title: セグメント・エンゲージ
-article_title: セグメント・エンゲージ
+nav_title: Segment Engage
+article_title: Segment Engage
 page_order: 3
 alias: /partners/segment_personas/
 alias: /partners/segment_engage/
@@ -12,9 +12,9 @@ search_tag: Partner
 
 ---
 
-# セグメント・エンゲージ
+# Segment Engage
 
-> [Segmentは](https://segment.com)、顧客データの収集、クリーニング、活性化を支援する顧客データ・プラットフォームである。この参考記事では、[BrazeとSegment Engageの](https://segment.com/docs/destinations/braze/#Engage)接続の概要を説明するとともに、適切な導入と利用のための要件とプロセスについて述べる。
+> [Segment](https://segment.com) は、顧客データの収集、クリーンアップ、およびアクティブ化を支援する顧客データプラットフォームです。このリファレンス記事では、[Braze と Segment Engage](https://segment.com/docs/destinations/braze/#Engage) の接続について概説し、適切な実装と利用のための要件とプロセスを説明します。
 
 BrazeとSegmentの統合により、Segmentに組み込まれたオーディエンス・ビルダーである[Engageを使って](https://segment.com/docs/engage/)、様々なソースから収集したデータを基にユーザーのセグメントを作成することができる。これらのオーディエンスは、コホートとしてBrazeに同期されるか、[カスタム属性や]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/) [カスタムイベントを通じて]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-events)ユーザープロファイルに示され、キャンペーンやキャンバスリターゲティングで使用するBrazeセグメントを作成するために使用できる。
 
@@ -22,99 +22,99 @@ BrazeとSegmentの統合により、Segmentに組み込まれたオーディエ
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| セグメント・アカウント | このパートナーシップを利用するには、[セグメントアカウントが](https://app.segment.com/login)必要である。 |
-| ブレイズクラウドの目的地 | Segmentとの統合で、[Brazeを配信先として設定]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings/)済みであること。<br><br>これには、[接続]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings)設定で正しいBrazeデータセンターとREST APIキーを提供することが含まれる。 |
-| Brazeデータインポートキー | EngageオーディエンスをコホートとしてBrazeに同期するには、データインポートキーを生成する必要がある。<br><br>Brazeのカスタマーサクセスマネージャーに連絡して、この機能にアクセスしよう。 |
+| Segment アカウント | このパートナーシップを活用するには、[Segment アカウント](https://app.segment.com/login)が必要です。 |
+| Braze Cloud の宛先 | Segment 統合で [Braze を宛先として設定]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings/)している必要があります。<br><br>これには、[接続]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings)設定で正しいBrazeデータセンターとREST APIキーを提供することが含まれる。 |
+| Brazeデータインポートキー | Engage オーディエンスをコホートとして Braze に同期するには、データインポートキーを生成する必要があります。<br><br>コホートのインポート機能は早期アクセスの段階であるため、この機能を利用するには Braze のカスタマーサクセスマネージャーにお問い合わせください。 |
 
 {: .reset-td-br-1 .reset-td-br-2}
 
-## コホート 目的地 統合
+## コホート宛先の統合
 
-### ステップ1:エンゲージ・オーディエンスを作る
-1. Segmentで、Engageの**Audiences**タブに移動し、**Newを**クリックする。
-2. 観客を作る。ページ上部の稲妻は、観客がリアルタイムで更新しているかどうかを示す。
-3. 次に、目的地としてブレーズを選択する。
-4. **Review & Createを**クリックしてオーディエンスをプレビューする。デフォルトでは、Segmentはすべての履歴データを照会し、計算された特性と観客の現在値を設定する。このデータを省略するには、**ヒストリカル・バックフィルの**チェックを外す。
+### ステップ1:Engage オーディエンスを作成する
+1. Segment で、Engage の \[**Audiences**] タブに移動し、\[**New**] をクリックします。
+2. オーディエンスを作成します。ページ上部の稲妻は、オーディエンスがリアルタイムで更新されているかどうかを示します。
+3. 次に、宛先として Braze を選択します。
+4. \[**Review & Create**] をクリックしてオーディエンスをプレビューします。デフォルトでは、Segment は計算済み特性とオーディエンスの現在の値を設定するため、すべての履歴データをクエリします。このデータを省略するには、\[**Historical Backfill**] をオフにします。
 
-### ステップ2:コホート・データ・インポート・キーをキャプチャする
+### ステップ2:コホートデータインポートキーをキャプチャする
 
-Brazeで、**Partner Integrations**>**Technology Partnersに**移動し、**Segmentを**選択する。
+Brazeで、\[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Segment**] を選択します。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。鍵の生成後、新しい鍵を作成したり、既存の鍵を無効にしたりすることができる。
+ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。
 
-### ステップ3:ブレイズ・コホーツの目的地をつなぐ
-[Segmentの指示に従って](https://segment.com/docs/connections/destinations/catalog/actions-braze-cohorts/#getting-started)Cohorts Destinationを設定し、EngageオーディエンスをコホートとしてBrazeに同期する。
+### ステップ3:Braze コホートの宛先を接続する
+Cohorts Destination の設定に関する[Segment の手順](https://segment.com/docs/connections/destinations/catalog/actions-braze-cohorts/#getting-started)に従って、Engage オーディエンスをコホートとして Braze に同期します。
 
 ### ステップ4:EngageのオーディエンスからBrazeセグメントを作成する。
-Brazeで**Segmentsに**移動し、新しいセグメントを作成し、フィルターとして**Segment Cohortsを**選択する。ここから、どのセグメントのコホートを含めるかを選択できる。セグメントコホートセグメントを作成した後、キャンペーンまたはキャンバスを作成する際に、オーディエンスフィルターとして選択することができる。
+Braze で \[**セグメント**] に移動し、新しいセグメントを作成し、フィルターとして \[**セグメントコホート**] を選択します。ここから、どの Segment コホートを含めるかを選択できます。セグメントコホートセグメントを作成した後、キャンペーンまたはキャンバスを作成する際に、オーディエンスフィルターとして選択することができる。
 
 ![][1]
 
 ## クラウドモードの統合
 
-### ステップ1:セグメントで計算された特性または聴衆を作成する
+### ステップ1:Segment の計算済み特性またはオーディエンスを作成する
 
-1. Segmentで、**Engageの** **Computed Traits**または**Audiences**タブに移動し、**Newを**クリックする。
-2. 競合の特徴やオーディエンスを作る。ページの上隅にある稲妻は、計算がリアルタイムで更新されているかどうかを示す。
-3. 次に、目的地として**ブレーズを**選択する。 
-4. **Review & Createを**クリックしてオーディエンスをプレビューする。デフォルトでは、Segmentはすべての履歴データを照会し、計算された特性と観客の現在値を設定する。このデータを省略するには、**ヒストリカル・バックフィルの**チェックを外す。
+1. Segmentで、\[**Engage**] の \[**Computed Traits**] タブまたは \[**Audiences**] タブに移動し、\[**New**] をクリックします。
+2. 計算済み特性またはオーディエンスを作成します。ページの上隅にある稲妻は、計算がリアルタイムで更新されているかどうかを示す。
+3. 次に、宛先として **Braze** を選択します。 
+4. \[**Review & Create**] をクリックしてオーディエンスをプレビューします。デフォルトでは、Segment は計算済み特性とオーディエンスの現在の値を設定するため、すべての履歴データをクエリします。このデータを省略するには、\[**Historical Backfill**] をオフにします。
 5. 計算された特性または視聴者設定で、Brazeへのデータ送信方法に基づいて接続設定を調整する。
 
 #### 計算された特徴とオーディエンス
 
 [計算された特性や](https://segment.com/docs/engage/audiences/computed-traits/) [オーディエンスは](https://segment.com/docs/Engage/audiences/)、カスタム属性やカスタムイベントとしてBrazeに送ることができる。
-- `identify` 、カスタム属性としてBrazeに表示される。
-- `track` 、カスタムイベントとしてBrazeに表示される。
+- `identify` 呼び出しを使用して送信された特性とオーディエンスは、Braze ではカスタム属性として表示されます。
+- `track` 呼び出しを使用して送信された特性とオーディエンスは、Braze ではカスタムイベントとして表示されます。
 
 計算された形質をBrazeのデスティネーションに接続する際に、どちらの方法を使うか（あるいは両方を使うか）を選択できる。
 
 {% tabs %}
-{% tab 特定する %}
+{% tab Identify %}
 
-Brazeでカスタム属性を作成するために、計算された形質とオーディエンスを`identify` 呼び出しとしてBrazeに送ることができる。 
+Braze でカスタム属性を作成するために、計算済み特性とオーディエンスを `identify` 呼び出しとして Braze に送信できます。 
 
-例えば、"Last Product Viewed Item"（最後に見た商品）に対してEngageが計算した特質がある場合、ユーザーのBrazeプロフィールの**Custom Attributes（カスタム属性**）に`last_product_viewed_item` 。これがエンゲージオーディエンスであった場合、**カスタム属性の**下に`true` として設定されたオーディエンスが表示される。
+例えば、"Last Product Viewed Item"（最後に見た商品）に対してEngageが計算した特質がある場合、ユーザーのBrazeプロフィールの**Custom Attributes（カスタム属性**）に`last_product_viewed_item` 。これが Engage のオーディエンスであった場合、\[**カスタム属性**] の下に `true` として設定されたオーディエンスが表示されます。
 
-| 計算された形質 | 観客 |
+| 計算済み特性 | オーディエンス |
 | -------------- | --------- |
-| ![ユーザー・プロフィール内のカスタム属性セクションに、"last_product_viewed_item" が "Sweater" としてリストされている。]({% image_buster /assets/img/segment/last_viewed-id-braze.png %}) | ![] （{% image_buster /assets/img/segment/dormant-identify-braze.png %} ）。 |
+| ![ユーザープロファイル内のカスタム属性セクションに、「last_product_viewed_item」 が「Sweater」としてリストされている。]({% image_buster /assets/img/segment/last_viewed-id-braze.png %}) | ![ユーザープロファイル内のカスタム属性セクションに、「dormant_shopper」が「tru」としてリストされている。]({% image_buster /assets/img/segment/dormant-identify-braze.png %}) |
 
 {% endtab %}
-{% tab トラック %}
+{% tab Track %}
 
-計算された特性やオーディエンスを`track` 呼び出しとしてBrazeに送信し、Brazeでカスタムイベントを作成することができる。 
+Braze でカスタムイベントを作成するために、計算済み特性とオーディエンスを `track` 呼び出しとして Braze に送信できます。 
 
 前の例の続きで、もしユーザーが "Last Product Viewed Item "の計算された特徴を持っている場合、それはユーザーのBrazeプロフィールに`Trait Computed` 、対応するカウントと最新のタイムスタンプと共に**Custom Eventsの**下に表示される。これがEngageオーディエンスであった場合、オーディエンス、カウント、および最新のタイムスタンプは、`true` として設定された**カスタム属性の**下に表示される。
 
-| 計算された形質 | 観客 |
+| 計算済み特性 | オーディエンス |
 | -------------- | --------- |
-| ![ユーザープロファイル内のカスタムイベントセクションには、"Trait Computed "が "1 "回表示され、最後に表示されたのは "20時間前 "である。]({% image_buster /assets/img/segment/last_viewed-track-braze.png %}) | ![ユーザー・プロフィール内のカスタム属性セクションには、"観客動員数 "の "1 "時間が表示され、最終時間は "3月9日午前1時45分 "である。]({% image_buster /assets/img/segment/dormant-track-braze.png %}) |
+| ![ユーザープロファイル内のカスタムイベントセクションに、「Trait Computed」「1」回、「Last time」として「20 hours ago」が表示されている。]({% image_buster /assets/img/segment/last_viewed-track-braze.png %}) | ![ユーザープロファイル内のカスタム属性セクションに、「Audience Entered」、「1」回、Last time」として「March 9 at 1:45 am」が表示されている。]({% image_buster /assets/img/segment/dormant-track-braze.png %}) |
 
 {% endtab %}
 {% endtabs %}
 
 ### ステップ2:Brazeのセグメントユーザー
 
-Brazeで、これらのユーザーのセグメントを作成するには、**Engagementの**下の**Segmentsに**移動し、新しいセグメントを作成し、セグメントに名前を付ける。次に、どのコールを使用したかによる：
-- **特定する**：フィルターとして**カスタム属性を**選択し、カスタム属性を探す。次に、"matches regex "オプション（特徴）または "equals "オプション（観客）を使い、適切な変数を入力する。
-- **トラック**フィルターとして**カスタムイベントを**選択し、カスタムイベントを探す。次に、"more than"、"less than"、"justly "のオプションを使い、希望の値を入れる。これは、セグメントをどのように定義したいかによる。
+Braze でこれらのユーザーのセグメントを作成するには、\[**エンゲージメント**] の下の \[**セグメント**] に移動し、新しいセグメントを作成し、セグメントに名前を付けます。次に、使用した呼び出しに基づいて作業を行います。
+- **Identify**:フィルターとして**カスタム属性を**選択し、カスタム属性を探す。次に、"matches regex "オプション（特徴）または "equals "オプション（観客）を使い、適切な変数を入力する。
+- **Track**:フィルターとして**カスタムイベントを**選択し、カスタムイベントを探す。次に、\[より大きい]、\[より小さい]、\[完全一致] オプションのいずれかを使用して必要な値を挿入します。これは、セグメントをどのように定義したいかによる。
 
 一度保存すれば、キャンバスやキャンペーン作成時に、ユーザーをターゲティングするステップでこのセグメントを参照することができる。
 
 ## 同期時間
 
-BrazeからSegment Engageへの接続のデフォルト設定は`Realtime` 、ペルソナをリアルタイム同期から除外するフィルターがいくつかある。これには、メッセージ送信時のオーディエンスのサイズを制限する時間ベースのフィルターも含まれる。
+Braze から Segment Engage への接続のデフォルト設定は `Realtime` ですが、ペルソナがリアルタイム同期を実行できないようにするいくつかのフィルターがあります。これには、メッセージ送信時のオーディエンスのサイズを制限する時間ベースのフィルターが含まれます。
 
-## セグメント・デバッガのテスト
+## Segment デバッガーのテスト
 
-セグメントのダッシュボードには「デバッガー」機能があり、「ソース」からのデータが期待通りに「デスティネーション」に転送されているかどうかをテストすることができる。
+Segment のダッシュボードにある「Debugger」機能により、顧客は「ソース」からのデータが予期されているとおりに「宛先」に転送されているかどうかをテストできます。
 
-この機能は、Braze[`/users/track` エンドポイントに]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)接続する。つまり、識別されたユーザー（BrazeユーザープロファイルのユーザーIDをすでに持っているユーザー）にのみ使用できる。
+この機能は Braze [`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)に接続します。つまり、この機能は識別されたユーザー (Braze ユーザープロファイルのユーザー ID がすでに設定されているユーザー) のみに使用できます。
 
-これはサイドバイサイドのBrazeとの統合には使えない。正しいBraze REST API情報が入力されていない場合、サーバーデータは通過しない。
+これはサイドバイサイドの Braze 統合では機能しません。正しい Braze REST API 情報が入力されていない場合、サーバーデータは転送されません。
 
 [1]: {% image_buster /assets/img/segment/segment3.png %}
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_for_currents.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_for_currents.md
index feb86dfb33b..017effeb56b 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_for_currents.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/segment/segment_for_currents.md
@@ -1,6 +1,6 @@
 ---
-nav_title: Currents事業
-article_title: Currents事業
+nav_title: Segment と Currents
+article_title: Segment と Currents
 page_order: 2
 alias: /partners/segment_for_currents/
 description: "このリファレンス記事では、Braze Currentsとセグメント間の連携について概説します。この顧客データプラットフォームは、マーケティングスタック内の送信元間で情報を収集し、ルーティングします。"
@@ -10,49 +10,49 @@ search_tag: Partner
 
 ---
 
-# Currents事業  
+# Segment と Currents  
 
 > [Segment](https://segment.com) は、顧客データの収集、クリーンアップ、およびアクティブ化を支援する顧客データプラットフォームです。本参考文献では、Braze Currentsとセグメントの関係を概観し、適切な実施と使用のための要求事項と手順を説明する。
 
-Brazeとセグメントインテグレーションを使用すると、Brazeの行動をセグメントにエクスポートするBraze Currentsを活用して、より深い分析をコンバージョンs、リテンション、および商品の使用状況に組み込むことができます。 
+Braze と Segments の統合により、Braze Currents を利用して Braze イベントを Segment にエクスポートし、コンバージョン、リテンション、製品使用率に関する詳細な分析を促進することもできます。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| セグメント勘定 | この提携の前倒しタグを行うには、[セグメントアカウント](https://app.segment.com/login)が必要です。 |
-| Braze 送信先 | セグメントインテグレーションでは、すでに[Brazeを送信先]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings/)として設定しておく必要があります。<br><br>これには、[接続設定s]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings)に正しいBrazeデータセンターとREST API キーを提供することも含まれます。 |
-| Currents | データをセグメントにエクスポートするには、アカウントに[Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents)を設定する必要があります。 |
+| Segment アカウント | このパートナーシップを活用するには、[Segment アカウント](https://app.segment.com/login)が必要です。 |
+| Braze 宛先 | セグメントインテグレーションでは、すでに[Brazeを送信先]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings/)として設定しておく必要があります。<br><br>これには、[接続設定s]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment/segment/#connection-settings)に正しいBrazeデータセンターとREST API キーを提供することも含まれます。 |
+| Currents | Segment にデータを再度エクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:セグメント書き込みキーの取得
 
-セグメントダッシュボードで、セグメントソースを選択します。次に、**Settings > API キー s** に移動します。ここには、**Segment Write Key** があります。
+Segment ダッシュボードで、Segment ソースを選択します。** \[設定] > \[API キー]** に移動します。ここで **Segment Write Key** を確認します。
 
 {% alert warning %}
-セグメント書き込みキーを最新の状態に保つことが重要です。コネクターの認証情報が期限切れになると、コネクターはイベントの送信を中止します。これが **48 時間** 以上続く場合、コネクタのイベントはドロップされ、データは永続的に失われます。
+Segment Write Key を最新の状態に保つことが重要です。コネクターの認証情報が期限切れになると、コネクターはイベントの送信を中止します。これが **48 時間** 以上続く場合、コネクタのイベントはドロップされ、データは永続的に失われます。
 {% endalert %}
 
 ### ステップ2:新しいCurrentsコネクターを作成する
 
 1. Braze で、**Partner Integrations** > **データエクスポート** に移動します。
-2. **\+ Create New Current** > **Segment Data Export**をクリックします。
-3. 次に、インテグレーションの名前、連絡先メール、セグメント書き込みキー、およびセグメント領域を指定します。
+2. \[**\+ 新しい Currents を作成**] > \[**セグメントデータのエクスポート**] をクリックします。
+3. 次に、統合名、連絡先メール、Segment Write Key、および Segment リージョンを指定します。
 
-![BrazeのセグメントCurrentsページです。ここには、インテグレーションの名前、連絡先メール、Segmentリージョン、およびAPI キーのフィールドs があります。][3]
+![Braze の Segment Currents ページ。統合名、連絡先メール、Segment リージョン、API キーのフィールドがある。][3]
 
 ### ステップ3:メールエンゲージメントをエクスポートする
 
-次に、エクスポートしたいエンゲージメントを選択します。リストされている次のエクスポートイベントおよびプロパティテーブルを参照してください。セグメントに送信されるすべてのイベントには、ユーザーの`external_user_id` が`userId` として含まれます。このとき、Braze は`external_user_id` が設定されていないユーザーs に対してイベントデータを送信しません。
+次に、エクスポートするメッセージエンゲージメントイベントを選択します。リストされている次のエクスポートイベントおよびプロパティテーブルを参照してください。セグメントに送信されるすべてのイベントには、ユーザーの`external_user_id` が`userId` として含まれます。このとき、Braze は`external_user_id` が設定されていないユーザーs に対してイベントデータを送信しません。
 
-![BrazeのセグメントCurrentsページで使用可能なすべてのメッセージエンゲージメントイベントのリスト。][2]
+![Braze の Segment Currents ページの利用可能なすべてのメッセージエンゲージイベントのリスト。][2]
 
-最後に、**Launch Current**を選択します。
+最後に \[**Currents を起動**] を選択します。
 
 {% alert warning %}
-同じCurrentsコネクターを複数作成する場合(たとえば、2 つのメッセージエンゲージメントイベントコネクター)、それらは別々のワークスペースにする必要があります。Braze セグメントCurrentsインテグレーションでは、1 つのワークスペース内のさまざまなアプリs によってイベントを分離できないため、これを実行しないと、不必要なデータのデデューピングとデータの損失が発生します。
+同じCurrentsコネクターを複数作成する場合(たとえば、2 つのメッセージエンゲージメントイベントコネクター)、それらは別々のワークスペースにする必要があります。Braze Segment Currents の統合では、1つのワークスペース内で異なるアプリケーションごとにイベントを分離することはできないため、そのようにできない場合、不必要なデータの重複排除やデータの損失が発生します。
 {% endalert %}
 
 詳細については、セグメント [ドキュメント](https://segment.com/docs/connections/sources/catalog/cloud-apps/braze/) を参照してください。
@@ -61,7 +61,7 @@ Brazeとセグメントインテグレーションを使用すると、Brazeの
 
 {% multi_lang_include updating_currents.md %}
 
-## 対応Currents
+## サポートされている Currents イベント
 
 Braze は、Currents [ユーザー動作]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/) および [メッセージエンゲージメント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) イベント用語集にリストされている以下のデータのセグメントへのエクスポートをサポートしています。
  
@@ -72,17 +72,17 @@ Braze は、Currents [ユーザー動作]({{site.baseurl}}/user_guide/data_and_a
   
 ### キャンペーン
 - 中止: `users_campaigns_abort`
-- 変換: `users.campaigns.Conversion`
-- 登録制御: `users.campaigns.EnrollInControl`
+- コンバージョン: `users.campaigns.Conversion`
+- EnrollinControl: `users.campaigns.EnrollInControl`
   
 ### キャンバス
 - 中止: `users_canvas_abort`
-- 変換: `users.canvas.Conversion`
-- 入力: `users.canvas.Entry`
-- 終了(一致したオーディエンス、実行されたイベント)
+- コンバージョン: `users.canvas.Conversion`
+- エントリ:: `users.canvas.Entry`
+- 離脱 (オーディエンス照合、実行済みのイベント)
   - `users.canvas.exit.MatchedAudience`
   - `users.canvas.exit.PerformedEvent`
-- 試験手順(コンバージョン、分割エントリ)
+- 実験ステップ (コンバージョン、分割エントリ)
   - `users.canvas.experimentstep.Conversion`
   - `users.canvas.experimentstep.SplitEntry`
 
@@ -93,7 +93,7 @@ Braze は、Currents [ユーザー動作]({{site.baseurl}}/user_guide/data_and_a
   - `users.messages.contentcard.Dismiss`
   - `users.messages.contentcard.Impression`
   - `users.messages.contentcard.Send`
-- メール(中止、バウンス、クリック、配信、マークスパム、開封、送信、ソフトバウンス、配信停止)
+- メール (中止、バウンス、クリック、配信、スパムとしてマーク、開封、送信、ソフトバウンス、配信停止)
   - `users.messages.email.Abort`
   - `users.messages.email.Bounce`
   - `users.messages.email.Click`
@@ -103,17 +103,17 @@ Braze は、Currents [ユーザー動作]({{site.baseurl}}/user_guide/data_and_a
   - `users.messages.email.Send`
   - `users.messages.email.SoftBounce`
   - `users.messages.email.Unsubscribe`
-- アプリ中(中止、押下、インプレッション)
+- アプリ内メッセージ (中止、クリック、インプレッション)
   - `users.messages.inappmessage.Abort`
   - `users.messages.inappmessage.Click`
   - `users.messages.inappmessage.Impression`
-- プッシュ通知(中止、跳ね返り、iOS フォアグラウンド、開封、送信)
+- プッシュ通知 (中止、バウンス、iOSforeground、開封、送信)
   - `users.messages.pushnotification.Abort`
   - `users.messages.pushnotification.Bounce`
   - `users.messages.pushnotification.IosForeground`
   - `users.messages.pushnotification.Open`
   - `users.messages.pushnotification.Send`
-- SMS(アボート、キャリア送信、配信、配信失敗、インバウンド受信、拒否、送信、ショートリンククリック)
+- SMS (中止、通信事業者の送信、配信、配信失敗、インバウンド受信、拒否、送信、ショートリンククリック)
   - `users.messages.sms.Abort`
   - `users.messages.sms.Delivery`
   - `users.messages.sms.DeliveryFailure`
@@ -124,7 +124,7 @@ Braze は、Currents [ユーザー動作]({{site.baseurl}}/user_guide/data_and_a
 - Webフック(中止、送信)
   - `users.messages.webhook.Abort`
   - `users.messages.webhook.Send`
-- WhatsApp(アボート、配信、障害、受信、読み取り、送信)
+- WhatsApp (中止、配信、障害、インバウンド受信、読み取り、送信)
   - `users.messages.whatsapp.Abort`
   - `users.messages.whatsapp.Delivery`
   - `users.messages.whatsapp.Failure`
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/simondata.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/simondata.md
index 38dc263d196..2bd5cd96ce6 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/simondata.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/simondata.md
@@ -1,37 +1,37 @@
 ---
-nav_title: サイモン・データ
-article_title: サイモン・データ
-description: "BrazeとSimon Dataの統合を利用して、洗練されたオーディエンスを作成し、オーケストレーションのためにBrazeに同期させる。"
+nav_title: Simon Data
+article_title: Simon Data
+description: "Braze と Simon Data の統合を使用して、高度なオーディエンスを作成し、オーケストレーションのためにリアルタイムでコードを使用せずに Braze に同期します。"
 alias: /partners/simon_data/
 page_type: partner
 search_tag: Partner
 ---
 
-# サイモン・データ
+# Simon Data
 
-> [サイモン・][1]データは、マーケティング担当者に親しみやすく、データチームから信頼されている顧客データプラットフォーム（CDP）である。サイモンは、データウェアハウスをマーケティングの強みに変えることで、ビジネス成果と優れた顧客体験を促進する。
+> [Simon Data][1] は、マーケターにとって使いやすく、データチームの信頼を得ている顧客データプラットフォーム (ＣＤＰ) です。Simon は、データウェアハウスをマーケティングの強みに変えることで、ビジネスの実績を向上し、カスタマーエクスペリエンスを促進します。
 
-BrazeとSimon Dataの統合を利用して、洗練されたオーディエンスを作成し、オーケストレーションのためにBrazeに同期させる。この統合により、Simonのキャンペーン優先順位付け、Identityマッチング機能、複雑な集計サポートなどを最大限に活用し、Brazeのキャンペーンをダウンストリームで向上させることができる。
+Braze と Simon Data の統合を使用して、高度なオーディエンスを作成し、オーケストレーションのためにリアルタイムでコードを使用せずに Braze に同期します。この統合により、Simonのキャンペーン優先順位付け、Identityマッチング機能、複雑な集計サポートなどを最大限に活用し、Brazeのキャンペーンをダウンストリームで向上させることができる。
 
 ## 前提条件
 
-開始するには、Simon Dataアカウント内でBrazeアカウントを認証する必要がある。
+開始するには、Simon Data アカウント内で Braze アカウントを認証する必要があります。
 
 | 必要条件         | 説明                                                                                                                                                               |
 | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| サイモン・データ          | Simon DataからBraze統合を利用するには、既存のSimon Dataアカウントが必要である。                                                                    |
-| Braze REST API キー  | `users.track`,`campaigns.trigger.schedule.create`,`campaigns.trigger.send` のパーミッションを持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
+| Simon Data          | Simon Data 内から Braze 統合を利用するには、既存の Simon Dataアカウントが必要です。                                                                    |
+| Braze REST API キー  | `users.track`,`campaigns.trigger.schedule.create`,および `campaigns.trigger.send` の権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | BrazeダッシュボードURL | [RESTエンドポイントのURL][3]。エンドポイントは、インスタンスのBraze URLに依存する。                                                                                |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
-- ブレイズ・キャンバスまたはEメールをトリガーする  
-- セグメント・プロパティを渡し、維持する
-- シンク特性とコンタクト・プロパティ
+- Braze キャンバスまたはメールをトリガーする  
+- セグメントプロパティを受け渡し、維持する
+- 特性と連絡先プロパティを同期する
 
 {% alert note %}  
-SimonとBrazeの統合を使用する場合、Simonは各同期でBrazeにデルタのみを送信するため、無関係なデータのコストを避けることができる。詳しくは[Sync TraitsとContact Propertiesを](#sync-traits-and-contact-properties)参照のこと。
+SimonとBrazeの統合を使用する場合、Simonは各同期でBrazeにデルタのみを送信するため、無関係なデータのコストを避けることができる。詳しくは、「[特性とコンタクトプロパティを同期する](#sync-traits-and-contact-properties)」を参照してください。
 {% endalert %}
 
 ## 統合
@@ -40,46 +40,46 @@ SimonとBrazeの統合を使用する場合、Simonは各同期でBrazeにデル
 
 Brazeとの統合を使用するには、まずSimonでBrazeアカウントを認証する：
 
-1. 左のナビゲーションから**Integrationsを**クリックし、Brazeまでスクロールする。
-2. Braze[REST APIキーと][2] [ダッシュボードのURLを][3]入力する。
-3. **Save Changesを**クリックする。
+1. 左側のナビゲーションで \[**Integrations**] をクリックし、\[Braze] までスクロールします。
+2. Braze の [REST API キー][2]と[ダッシュボードのURL][3] を入力します。
+3. \[**SAVE CHANGES**] クリックします。
 
 接続に成功すると、ウィンドウに「**Connected**」と表示される。
 
-![サイモンデータの統合画面][8]{: style="max-width:70%"}
+![Simon Data の統合画面][8]{: style="max-width:70%"}
 
-### サイモンのフローやジャーニーにブレイズのアクションを追加する
+### Simon でフローまたはジャーニーに Braze アクションを追加する
 
-SimonでBrazeアカウントを認証した後、Brazeのアクションを[Flowsと][4] [Journeysに][5]追加できる。
+Simon で Braze アカウントを認証したら、Braze のアクションを[フロー][4]と[ジャーニー][5]に追加できます。
 
-つのアクションが用意されている：
+3つのアクションがあります。
 
-- **サイモンのセグメント属性を同期させる**：セグメントの詳細をBrazeの新規または既存のカスタム属性と同期させる。
-- **ブレイズ・キャンバスを発動させる**：サイモンのセグメントデータを活用したBraze Canvasをトリガーする。
-- **ブレイズのキャンペーンを送る**：サイモンからBrazeキャンペーン全体を立ち上げる。
+- **Sync Simon segment attribute**:セグメントの詳細をBrazeの新規または既存のカスタム属性と同期させる。
+- **Trigger a Braze Canvas**:Simon のセグメントデータを利用する Braze キャンバスをトリガーします。
+- **Send a Braze campaign**:Simon から Braze キャンペーン全体を開始します。
 
-![サイモンデータで利用可能なBrazeアクションのリストをドロップダウンで表示する。][9]{: style="max-width:60%"}
+![Simon Data で利用可能な Braze アクションのリストを示すドロップダウン。][9]{: style="max-width:60%"}
 
 一部のアクションは、特定のフロータイプまたはジャーニーでのみ利用できる。詳細は以下を参照のこと。 [docs.simondata.com][6].
 
-### 特性とコンタクトのプロパティを同期する
+### 特性と連絡先プロパティを同期する
 
-データ消費を最小限に抑えるために、セグメント内のすべての顧客のすべてのフィールドを更新するのではなく、デフォルトで同期する特定の特徴を選択することができる。
+データの消費を最小限に抑えるために、セグメント内のすべての顧客のすべてのフィールドを更新するのではなく、デフォルトで同期する特定の特性を選択できます。
 
 {% alert note %}
-取引同期を開始するには、[サイモン・サポート・センターで](https://docs.simondata.com/docs/support-center)リクエストを送信する。次のステップに進めるようになったら、アカウント・マネージャーから連絡がある。
+特性の同期を開始するには、[Simon Support Center](https://docs.simondata.com/docs/support-center) でリクエストを送信します。次のステップに進めるようになったら、アカウント・マネージャーから連絡がある。
 {% endalert %}
 
-アカウント・マネージャーによってContact Traitsが有効化された後：
+アカウントマネージャーによって連絡先特性がアクティブ化された後に、次の手順に沿って操作します。
 
-1. Simonで、左ナビゲーションの**Admin Centerを**展開し、**Sync Contact Traitsを**選択する。
-2. **ブレイズを**選ぶ。コンタクト・プロパティはここに表示され、データセットごとにネストされている。
+1. Simon で、左側のナビゲーションの \[**Admin Centerを**] を展開し、\[**Sync Contact Traits**] を選択します。
+2. \[**Braze**] を選択します。連絡先プロパティはここに表示され、データセットごとにネストされます。
 3. SimonとBrazeの統合を使用する際に同期させたいフィールドを選択する：
-   1. **形質の数は**、そのデータセットで選択可能な形質の数を示す。すべてを選択することも、行を展開して個々のフィールドを選択することもできる。
+   1. \[**Number of traits**] は、そのデータセットで選択可能な特性の数を示します。すべてを選択することも、行を展開して個々のフィールドを選択することもできる。
    2. フィールド名がBrazeに到着したときに異なる表示にしたい場合は、**Downstream nameを**編集する。
-   3. サイモンから初めてBrazeと統合する場合は、「**Backfill all contacts**」をクリックする。すべてのデータが完全に同期していることを確認するために、フローやジャーニーで初めてアクションを使用するときに、Brazeにすべてのデータポイントを送信する。その後の同期では、この画面で選んだ特徴だけがBrazeに送られる。これにより、必要なデータに対してのみ課金されるようになる。
+   3. Simon から Braze と初めて統合する場合は、\[**Backfill all contacts**] をクリックします。フローまたはジャーニーで初めてアクションを使用するときに、すべてのデータが完全に同期されるようにするため、バックフィルにより Braze にすべてのデータポイントが送信されます。その後の同期では、この画面で選択した特性のみが Braze に送信されます。これにより、必要なデータに対してのみ課金されるようになります。
 
-![サイモン・データで同期特性を選択する。][10]
+![Simon Dataでの同期する特性の選択。][10]
 
 
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium.md
index 19d1a5d4242..97e1787abda 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium.md
@@ -3,8 +3,8 @@ nav_title: Tealium
 noindex: true
 layout: dev_guide
 guide_top_header: "Tealium"
-guide_top_text: "ウェブ、モバイル、オフライン、IoTデバイスにまたがるTealiumは、顧客データを結びつけ、ブランドが顧客とつながる手助けをする。Tealiumのターンキー統合エコシステムは、1,200を超えるクライアントサイドおよびサーバーサイドのベンダーとテクノロジーをサポートしており、ブランドはリアルタイムで統一された顧客データ基盤を構築することができる。"
-description: "このランディングページには、統合ガイダンス、Tealium AudienceStream、Tealium for Currentsなど、Tealiumに関するあらゆる情報が掲載されている。"
+guide_top_text: "Tealium は、Web、モバイル、オフライン、IoT デバイスにわたる顧客データを接続し、企業が顧客とつながれることを支援しています。すぐに使える Tealium の統合エコシステムでは、1,200社以上のクライアントサイドおよびサーバーサイドベンダーやテクノロジーに対応し、ブランドはリアルタイムで統一顧客データのインフラを構築できます。"
+description: "このランディングページは、統合ガイダンス、Tealium AudienceStream、Tealium と Currents など、Tealium に関するあらゆる情報のホームページです。"
 
 guide_featured_list:
 - name: Tealium
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium.md
index 0fe183cda51..9c03dd5e29c 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium.md
@@ -11,84 +11,84 @@ search_tag: Partner
 
 # Tealium
 
-> [Tealium](https://tealium.com/) は、EventStream、AudienceStream、およびiQ Tag Management で構成されるユニバーサルデータハブおよび顧客データプラットフォームで、サードパーティのソースからモバイル、ウェブ、および代替データを接続できます。Tealium と Braze を接続すると、カスタムイベント s、ユーザー 属性、および購入のデータフローが可能になり、リアルタイムでデータを操作できるようになります。
+> [Tealium](https://tealium.com/) は、EventStream、AudienceStream、および iQ Tag Management で構成されるユニバーサルデータハブおよびカスタマーデータプラットフォームであり、サードパーティのソースのモバイルデータ、Web データ、および代替データを接続できます。Tealium を Braze と接続することで、カスタムイベント、ユーザー属性、購入のデータフローが実現し、リアルタイムでデータを操作できるようになります。
 
-![さまざまなTealiumプロダクトとBraze プラットフォームを組み合わせてリアルタイムでクロスチャネルの キャンペーンs を有効にする方法を示すTealium図です。][22]{: style="border:0;"}
+![さまざまな Tealium 製品と Braze プラットフォームがどのように連携してクロスチャネルキャンペーンをリアルタイムでアクティブにするかを示す Teralium の概要図。][22]{: style="border:0;"}
 
 BrazeとTealiumインテグレーションを使用すると、ユーザーを追跡し、さまざまなユーザー 分析プロバイダーにデータをルーティングできます。Tealiumでは次の操作ができます。
-- Tealium オーディエンス s を[オーディエンスStream]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream/) と同期し、Braze キャンペーンとキャンバスのパーソナライズまたはSegments の構築に使用するためにBrazeします。
-- [プラットフォーム間のデータインポート](#choose-your-integration-type)。Braze は、Android、iOS、およびWeb アプリの各アプリケーションに[並列](#side-by-side-sdk-integration)SDKインテグレーションと、イベントデータにレポートできる任意のプラットフォーム内で使用できる[server-to-server](#server-to-server-integration)インテグレーションの両方を提供します。<br><br>
+- [AudienceStream]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream/)で Tealium オーディエンスを Braze に同期し、Braze キャンペーンとキャンバスのパーソナライズ、またはセグメントの作成に使用できるようにします。
+- [プラットフォーム間でデータをインポートします](#choose-your-integration-type)。Braze は、Android、iOS、およびWeb アプリの各アプリケーションに[並列](#side-by-side-sdk-integration)SDKインテグレーションと、イベントデータにレポートできる任意のプラットフォーム内で使用できる[server-to-server](#server-to-server-integration)インテグレーションの両方を提供します。<br><br>
 
 {% tabs %}
 {% tab EventStream %}
-Tealium EventStream は、データセンターに配置されるデータ収集およびAPI ハブです。EventStream は、セットアップとインストールから、受信ユーザーデータの識別、検証、および拡張まで、データサプライチェーン全体を処理します。EventStream は、イベントフィードs およびコネクターでリアルタイムのアクションを実行します。以下は、[EventStream](https://docs.tealium.com/server-side/getting-started/eventstream-api-hub/introduction/)を構成する機能です。
-- データソース(設置とデータ収集)
+Tealium EventStream は、データの中央に位置するデータ収集および API ハブです。EventStream は、セットアップとインストールから、受信ユーザーデータの識別、検証、および拡張まで、データサプライチェーン全体を処理します。EventStream は、イベントフィードとコネクターを使用してリアルタイムアクションを実行します。以下は、[EventStream](https://docs.tealium.com/server-side/getting-started/eventstream-api-hub/introduction/)を構成する機能です。
+- データソース (インストールおよびデータ収集)
 - ライブイベント(リアルタイムデータ検査)
 - イベント仕様と属性s(データレイヤー要件と検証)
-- イベントフィードs (フィルターのイベントタイプ)
+- イベントフィード (フィルタリングされたイベントタイプ)
 - イベントコネクター(API ハブアクションs)
 
 {% endtab %}
-{% tab オーディエンスストリーム %}
+{% tab AudienceStream %}
 
-Tealium AudienceStreamはオムニチャネル 顧客 セグメンテーションでリアルタイムのアクションエンジンです。AudienceStream は、EventStream に流れるデータを取得し、ブランドとの顧客のエンゲージメントの最も大切な属性を表すビジタープロファイルs を作成します。設定ステップについては、[AudienceStream]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream/)を参照してください。
+Tealium AudienceStreamはオムニチャネル 顧客 セグメンテーションでリアルタイムのアクションエンジンです。AudienceStream は EventStream に流入するデータを取得し、ブランドのカスタマーエンゲージメントの最も重要な属性を表す訪問者プロファイルを作成します。設定ステップについては、[AudienceStream]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream/)を参照してください。
 
 {% endtab %}
 {% tab iQタグ管理 %}
-Tealium iQ では、トリガー コードをアプリ s で使用することができます。これには、Tealium iQ タグマネジメントユーザーインターフェイスのタグを使用します。このタグでは、モバイルおよびウェブプラットフォームs からイベントデータを収集、コントロール、配信します。これにより、アプリs にBraze固有のコードを追加することなく、ネイティブのBraze インプリメンテーションを設定できます。ユーザは、iQ タグ管理またはJSON 設定ファイルを介してモバイルリモートコマンドを統合することができます(推奨Tealium アプリ到達)。Braze Web SDKを使用するユーザは、Web iQ タグを使用して統合する必要があります。
+Tealium iQ では、Tealium iQ Tag Management UI でタグを使用してアプリでコードをトリガーできます。このタグにより、モバイルおよび Web プラットフォームからイベントデータが収集、制御、および配信されます。これにより、アプリケーションに Braze 固有のコードを追加することなく、ネイティブの Braze 実装を設定できます。ユーザーは、iQ Tag Management または JSON 設定ファイルを使用してモバイルリモートコマンドを統合できます (Tealium アプローチが推奨されます)。Braze Web SDK を使用するユーザーは、Web iQ タグを使用して統合を行う必要があります。
 
 各メソッドの長所と短所について詳しくは、以下の[ Tealium iQ タグ マネージャー](#mobile-remote-commands) を参照してください。
 {% endtab %}
 {% endtabs %}
 
 {% alert important %}
-Tealium は、バッチコネクタと非バッチコネクタの両方のアクションを提供します。ユースケースにとってリアルタイムのリクエストが大切で、BrazeのAPI レート制限スペックを打つ心配がない場合は、非バッチコネクターを使用する必要があります。不明な点がある場合は、Brazeサポートまたは顧客のサクセスマネージャーにお問い合わせください。<br><br>
+Tealium は、バッチと非バッチの両方のコネクターアクションを提供します。非バッチコネクターは、リアルタイムリクエストがユースケースにとって重要であり、Braze の API レート制限指定に達する懸念がない場合にのみ使用してください。不明な点がある場合は、Brazeサポートまたは顧客のサクセスマネージャーにお問い合わせください。<br><br>
 
 バッチ・コネクターの場合、要求は、以下のいずれかのしきい値が満たされるまでキューに入れられます。<br><br>
 - 最大リクエスト数:75
-- 最も古いリクエストからの最大時間:10分
+- 最も古いリクエストからの最大経過時間:10分
 - 要求の最大サイズ1 MB
 
-Tealium では、同意イベント(サブスクリプション環境設定)またはユーザー削除イベントはデフォルトで一括処理されません。
+Tealium は、デフォルトでは同意イベント (サブスクリプション設定) またはユーザー削除イベントをバッチ処理しません。
 {% endalert %}
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| Tealium勘定 | この提携を進めるには、サーバーおよび/またはクライアントサイドアクセスを持つ[Tealiumアカウント](https://my.tealiumiq.com/)が必要です。 | 
-| インストール元とTealium元[ライブラリ](https://docs.tealium.com/platforms/) | モバイルアプリs、Web サイトs、バックエンドサーバなど、Tealiumに送信されるデータの送信元。<br><br>Tealiumコネクターを正しく設定するには、ライブラリーをアプリ、現場、またはサーバーにインストールする必要があります。 |
-| Braze RESTとSDKエンドポイント | RESTまたはSDKエンドポイント。エンドポイントは、インスタンス の[ Braze URL によって異なります。 |
-| Braze アプリ 識別子鍵(横並びのみ) | アプリ 識別子ボタン。<br><br>これは、** Braze Dashboard > Manage Settings > API Key** にあります。 |
-| コードバージョン(並列のみ) | SDK 版に対応し、major.minor 形式である必要があります(3.0.1 ではなく3.2 など)。コード版は、3.0以上にしてください。 |
-| REST API キー(サーバ間のみ) | `users.track` および`users.delete` 権限を持つBraze REST API キー。<br><br>これは、** Braze Dashboard > Developer Console > REST API Key > Create New API Key** 内で作成できます。|
+| Tealium アカウント | この提携を進めるには、サーバーおよび/またはクライアントサイドアクセスを持つ[Tealiumアカウント](https://my.tealiumiq.com/)が必要です。 | 
+| インストールされたソースと Tealium ソースの[ライブラリ](https://docs.tealium.com/platforms/) | モバイルアプリ、Web サイト、バックエンドサーバーなど、Tealium に送信されるデータの提供元。<br><br>適切な Tealium コネクターを設定できるようにするには、ライブラリをアプリ、サイト、サーバーにインストールしておく必要があります。 |
+| Braze RESTとSDKエンドポイント | REST または SDK エンドポイントの URL。エンドポイントはインスタンスの [Braze URL]({{site.baseurl}}/api/basics/#endpoints) に応じて異なります。 |
+| Braze アプリ 識別子鍵(横並びのみ) | アプリ識別子キー。<br><br>これは、**Braze ダッシュボード > \[設定の管理] > \[API キー]** で確認できます。 |
+| コードバージョン(並列のみ) | SDK バージョンに対応し、major.minor 形式である必要があります (3.0.1ではなく3.2など)。コードバージョンは3.0以上である必要があります。 |
+| REST API キー(サーバ間のみ) | `users.track` および`users.delete` 権限を持つBraze REST API キー。<br><br>これは **Brazeダッシュボード > \[開発者コンソール] > \[REST API キー] > \[新しい API キーを作成]** で作成できます。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合タイプを選択する
 
 | 統合 | 詳細 |
 | ----------- | ------- |
-| [横並び](#side-by-side-sdk-integration) | Tealium のSDKを使用して、イベントをBrazeのネイティブコールに変換し、サーバー間の統合よりも深い機能とBrazeの包括的な使用を可能にします。<br><br>Brazeのリモートコマンドを使用する場合は、TealiumがすべてのBraze方法(コンテンツカードなど)に対応しているわけではないことに注意してください。対応するリモートコマンドでアプリされていないBrazeメソッドを使用するには、ネイティブBraze コードをコードベースに追加してメソッドを呼び出す必要があります。|
-| [サーバ間](#server-to-server-integration) | Tealium からBraze のREST API エンドポイントに転送します。<br><br>アプリ メッセージング内、コンテンツカード、プッシュ通知などのBrazeのユーザーインターフェイス機能には対応していません。また、このメソッドでは使用できない、デバイスレベルのフィールドs などの自動的にキャプチャされるデータもあります。<br><br>これらの機能を使用する場合は、並列統合を検討してください。|
+| [サイドバイサイド](#side-by-side-sdk-integration) | Tealium の SDK を使用して、イベントを Braze のネイティブ呼び出し変換します。これにより、サーバー間統合よりも高度な機能にアクセスでき、Braze をより包括的に使用できるようになります。<br><br>Brazeのリモートコマンドを使用する場合は、TealiumがすべてのBraze方法(コンテンツカードなど)に対応しているわけではないことに注意してください。対応するリモートコマンドにマッピングされていない Braze メソッドを使用するには、ネイティブ Braze コードをコードベースに追加してメソッドを呼び出す必要があります。|
+| [サーバー間](#server-to-server-integration) | Tealium からBraze のREST API エンドポイントにデータを転送します。<br><br>アプリ メッセージング内、コンテンツカード、プッシュ通知などのBrazeのユーザーインターフェイス機能には対応していません。また、この方法では利用できないデバイスレベルのフィールドなど、自動的に取得されるデータも存在します。<br><br>これらの機能を使用する場合は、並列統合を検討してください。|
 {: .reset-td-br-1 .reset-td-br-2}
 
-## サイドバイサイドSDKインテグレーション
+## サイドバイサイドの SDK 統合
 
 ### リモートコマンド
 
-リモートコマンドは、Tealium iOS およびAndroid ライブラリの機能であり、Braze Server からBraze へTealium SDKからの呼び出しを可能にします。Braze リモートコマンドモジュールは、必要なBrazeライブラリを自動的にインストールして構築し、すべてのメッセージレンダリングと分析 "トラッキングを処理します。Braze モバイルリモートコマンドを使用するには、アプリs にインストールされているTealium ライブラリが必要です。
+リモートコマンドは、Tealium iOS および Android ライブラリの機能であり、Tealium SDK から Braze サーバーを介して Braze への呼び出しを実行できるようにします。Braze リモートコマンドモジュールは、必要な Braze ライブラリを自動的にインストールおよびビルドし、すべてのメッセージレンダリングと分析トラッキングを処理します。Braze モバイルリモートコマンドを使用するには、アプリs にインストールされているTealium ライブラリが必要です。
 
 Tealium には、モバイルリモートコマンドを統合する2 つの方法があります。統合タイプ間で機能が失われることはなく、基礎となるネイティブコードは同じです。
 
-| モバイルリモートコマンド方式 | 利点 | 連結 |
+| モバイルリモートコマンド方式 | 長所 | 短所 |
 | --- | --- | --- |
-| **リモート指令タグ** | Tealium iQ UI を使用して、リモートコマンドに送信されるm アプリの内容やデータを簡単に変更できます。<br><br>これにより、アプリがすでにアプリストアに入った後、クライアントがアプリを更新する必要なく、追加のデータまたはイベントをサードパーティSDKに送信できます。 | アプリのタグマネジメントモジュールは、非表示のWeb ビューに依存してJavaScript を処理します。 |
-| **JSON構成ファイル**<br>([推奨](https://docs.tealium.com/platforms/remote-commands/integrations/braze/#how-it-works)) | JSONメソッドを使用すると、アプリで非表示のWebビューを使用する必要がなくなり、メモリー使用量が大幅に削減されます。<br><br>JSON ファイルは、顧客のアプリ内でリモートまたはローカルにホストできます。 | 現時点では、これを管理するUIがないため、少し手間がかかります。<br><br>注:Tealiumは、この問題を解決し、iQタグマネジメントバージョンと同じレベルの柔軟性をJSONリモートコマンドにもたらすマネジメントUIの追加に取り組んでいます |
+| **リモートコマンドタグ** | Tealium iQ UI を使用して、リモートコマンドに送信されるデータとマッピングを簡単に変更できます。<br><br>これにより、アプリがすでにアプリストアに入った後、クライアントがアプリを更新する必要なく、追加のデータまたはイベントをサードパーティSDKに送信できます。 | アプリのタグマネジメントモジュールは、非表示のWeb ビューに依存してJavaScript を処理します。 |
+| **JSON構成ファイル**<br>([推奨](https://docs.tealium.com/platforms/remote-commands/integrations/braze/#how-it-works)) | JSONメソッドを使用すると、アプリで非表示のWebビューを使用する必要がなくなり、メモリー使用量が大幅に削減されます。<br><br>JSON ファイルは、顧客のアプリ内でリモートまたはローカルにホストできます。 | 現時点では、これを管理するUIがないため、少し手間がかかります。<br><br>注:Tealium は、この問題を解決し、iQ Tag Management バージョンと同じレベルの柔軟性を JSON リモートコマンドに取り入れる Management UIの追加に取り組んでいます |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-Braze モバイルリモートコマンドデータm アプリ ings を使用して、デフォルト ユーザー 属性s とカスタム属性s を設定し、購買とカスタムイベントs を追跡します。対応するBraze方法については、次の表を参照してください。
+Braze モバイルリモートコマンドのデータマッピングを使用して、デフォルトのユーザー属性とカスタム属性を設定し、購入とカスタムイベントを追跡します。対応するBraze方法については、次の表を参照してください。
 
-| リモートコマンド | Braze法 |
+| リモートコマンド | Braze のメソッド |
 | -------------- | ------------ |
 | appendcustomarrayattribute | addToCustomAttributeArrayWithKey()|
 | emailnotification | setEmailNotificationSubscriptionType() |
@@ -109,23 +109,23 @@ Braze モバイルリモートコマンドデータm アプリ ings を使用し
 
 Braze モバイルリモートコマンドの設定方法の詳細と、サポートされている方法の概要については、Tealium 開発者 ドキュメントを参照してください。
 - [リモートコマンド](https://docs.tealium.com/platforms/remote-commands/integrations/braze/#json-template)
-- [リモート指令タグ](https://docs.tealium.com/client-side-tags/braze-mobile-remote-command-tag/)
+- [リモートコマンドタグ](https://docs.tealium.com/client-side-tags/braze-mobile-remote-command-tag/)
 
 {% alert important %}
-Brazeのモバイルリモートコマンドは、すべてのBraze方法やメッセージング チャネル(コンテンツカードなど)に対応しているわけではありません。対応するリモートコマンドでアプリされていないBrazeメソッドを使用するには、ネイティブBraze コードをコードベースに追加して、そのメソッドを直接的に呼び出す必要があります。
+Braze モバイルリモートコマンドは、すべての Braze メソッドとメッセージングチャネルをサポートしているわけではありません (コンテンツカードなど)。対応するリモートコマンドにマッピングされていない Braze メソッドを使用するには、ネイティブ Braze コードをコードベースに追加してメソッドを直接呼び出す必要があります。
 {% endalert%}
 
 ### Braze Web SDK タグ
 
-Braze Web SDKタグを使用して、BrazeのWeb SDKをWeb サイトにデプロイします。[ Tealium iQ タグ Management](https://docs.tealium.com/client-side-tags/braze-web-sdk-tag/) では、顧客 s がビジターのアクティビティを追跡するタグとしてBrazeをTealium ダッシュボード内に追加できます。通常、タグは、オンライン広告、メール マーケティング、およびサイトパーソナライゼーションの有効性を理解するためにマーケターs によって使用されます。
+Braze Web SDK タグを使用して、Braze の Web SDK を Web サイトにデプロイします。[Tealium iQ Tag Management](https://docs.tealium.com/client-side-tags/braze-web-sdk-tag/) により、顧客は訪問者のアクティビティを追跡するために Tealium ダッシュボード内でタグとして Braze を追加できます。タグは一般的に、オンライン広告、メールマーケティング、およびサイトのパーソナライゼーションの効果を理解する目的でマーケターにより使用されます。
 
-1. Tealium で、**iQ > Tags > + Add Tag > Braze Web SDK** に移動します。
-2. Tag Configuration ダイアログボックスで、API Key (Braze アプリ 識別子鍵)、Base URL (Braze SDKエンドポイント)、および[Braze Web SDK コードバージョン](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md) を入力します。また、ログを有効にして、デバッグ目的で Web Console に情報を記録することもできます。
-3. [ 読み込む Rules](https://docs.tealium.com/iq-tag-management/load-rules/about/) ダイアログボックスで、" All Pages&quot を読み込むするか、**Create Rule** を選択して、いつ、どこでこのタグのインスタンスをサイトに読み込むするかを決定します。
-4. **[Data Mアプリings](https://docs.tealium.com/iq-tag-management/data-mappings/about/)**ダイアログボックスで、**Create Mアプリings**を選択してTealiumデータをBrazeにマッピングします。Braze Web SDK タグの送信先は、タグの**Data Mアプリing**タブに組み込まれています。[以下のテーブル](https://docs.tealium.com/client-side-tags/braze-web-sdk-tag/)は、使用可能な送信先カテゴリを一覧表示し、それぞれの送信先の名前を説明します。
-5. **Finish**を選択します。
+1. Tealium で **\[iQ] > \[Tags] > \[+ Add Tag] > \[Braze Web SDK]** に移動します。
+2. \[Tag Configuration] ダイアログボックスで、API キー (Braze アプリ識別子キー)、ベース URL (Braze SDK エンドポイント)、および[Braze Web SDK コードバージョン](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md) を入力します。また、ロギングを有効にして、デバッグ目的で Web コンソールに情報を記録することもできます。
+3. \[[Load Rules](https://docs.tealium.com/iq-tag-management/load-rules/about/)] ダイアログボックスで \[Load on All Pages] を選択するか、または \[**Create Rule**] を選択して、サイトでこのタグのインスタンスをいつどこに読み込むかを決定します。
+4. **[Data Mアプリings](https://docs.tealium.com/iq-tag-management/data-mappings/about/)**ダイアログボックスで、**Create Mアプリings**を選択してTealiumデータをBrazeにマッピングします。Braze Web SDK タグの宛先変数は、タグの \[**Data Mapping**] タブに組み込まれています。[これらの表](https://docs.tealium.com/client-side-tags/braze-web-sdk-tag/)に、使用可能な宛先カテゴリと、それぞれの宛先名の説明が示されています。
+5. \[**Finish**] を選択します。
 
-### サイドバイサイドの統合リソース
+### サイドバイサイド統合のリソース
 
 - iOS リモートコマンド:[Tealium ドキュメント](https://docs.tealium.com/platforms/remote-commands/integrations/braze/),[Tealium GitHub リポジトリ](https://github.com/Tealium/tealium-ios-braze-remote-command)
 - Androidリモートコマンド:[Tealium ドキュメント](https://docs.tealium.com/platforms/remote-commands/integrations/braze/),[Tealium GitHub リポジトリ](https://github.com/Tealium/tealium-android-braze-remote-command)
@@ -133,55 +133,55 @@ Braze Web SDKタグを使用して、BrazeのWeb SDKをWeb サイトにデプロ
 
 ## サーバー間統合
 
-このインテグレーションでは、Tealium からBraze REST にデータが転送されます。
+この統合により、Tealium から Braze REST API にデータが転送されます。
 
-サーバー間統合では、アプリ メッセージング、コンテンツカード、またはプッシュ通知などのBraze UI 機能は使用できません。また、このメソッドでは使用できない、自動的にキャプチャされるデータ(デバイスレベルのフィールドなど) もあります。
+サーバー間統合では、アプリ内メッセージング、コンテンツカード、プッシュ通知などの Braze UI 機能はサポートされていません。また、このメソッドでは使用できない、自動的にキャプチャされるデータ(デバイスレベルのフィールドなど) もあります。
 
 このデータとこれらの機能を使用する場合は、[並列]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium/#side-by-side-sdk-integration)SDKインテグレーションを検討してください。
 
 ### ステップ1:ソースの設定
 
-Tealiumでは、まずコネクターの有効なデータソースを設定する必要があります。
-1. **Server-Side** のTealiumのサイドバーから、**Sources > Data Sources > + Add Data Source** に移動します。
-2. 使用可能なカテゴリ内で目的のプラットフォームを見つけ、送信元に名前を付けます。これは必須のフィールドです。<br>![][6]{: style="max-width:80%;margin-left:15px;margin-bottom:15px;"}
-3. **Event Specifications**オプションから、含める[イベント仕様](https://docs.tealium.com/server-side/event-specifications/about/)を選択します。イベントの指定は、イベントの名前とインストールで追跡するために必要な属性を特定するのに役立ちます。これらの指定は、アプリ受信事象に依存します。<br>![][7]{: style="max-width:80%;margin-left:15px;margin-bottom:15px;"}<br>あなたにとって最も価値のあるデータと、あなたのユースケースにとって最もアプリ適切と思われる仕様について、少し時間をかけて考えてみましょう。\[カスタムイベント仕様][19]も利用可能です。]<br>
-4. 次に、**Get Code**ステップに進みます。ここに記載されている基本コードと行動"トラッキング コードは、インストールガイドとして機能します。これらの指示を共有したい場合は、提供されたPDF を読み込むします。**Save & Continue**を選択します。<br>
-5. 保存したソースを表示したり、イベントスペックを追加または削除したりできます。<br>![][18]{: style="max-width:80%;margin-left:15px;margin-bottom:15px;"}<br>詳細なデータソースビューから、次のアクションを実行できます。
+Tealium では最初に、コネクターの取得元となる有効なデータソースを設定する必要があります。
+1. Tealium のサイドバーの \[**Server-Side**] から **\[Sources] > \[Data Sources] > \[+ Add Data Source]** に移動します。
+2. 使用可能なカテゴリ内で目的のプラットフォームを見つけ、ソースに名前を付けます。これは必須フィールドです。<br>![][6]{: style="max-width:80%;margin-left:15px;margin-bottom:15px;"}
+3. **Event Specifications**オプションから、含める[イベント仕様](https://docs.tealium.com/server-side/event-specifications/about/)を選択します。イベント仕様は、インストールで追跡するイベント名と必須属性を特定するのに役立ちます。これらの仕様は受信イベントに適用されます。<br>![][7]{: style="max-width:80%;margin-left:15px;margin-bottom:15px;"}<br>時間をとって、お客様にとって最も価値のあるデータと、ユースケースに最も適切であると思われる仕様について検討します。\[カスタムイベント仕様][19]も利用可能です。<br>
+4. 次に、**Get Code**ステップに進みます。ここで提供されるベースコードとイベント追跡コードは、インストールガイドとして機能します。これらの指示を共有したい場合は、提供されたPDF を読み込むします。完了したら \[**Save & Continue**] を選択します。<br>
+5. これで、保存したソースを表示し、イベント仕様を追加または削除することができます。<br>![][18]{: style="max-width:80%;margin-left:15px;margin-bottom:15px;"}<br>詳細なデータソースビューから、次のアクションを実行できます。
 - データソース鍵の表示と複製
-- インストール手順の表示
+- インストール手順を表示する
 - **Get Code**ページに戻る
 - イベント仕様の追加または削除
 - イベント仕様に関連するライブイベントを表示するために移動します
-- さらに・・・<br>
-6. 最後に、ページの上部にある**Save / Publish**を選択します。送信元を公開しないと、Braze コネクターの設定時に見つかりません。
+- その他<br>
+6. 最後に、ページの上部にある**Save / Publish**を選択します。ソースを公開しないと、Braze コネクターの設定時にソースを見つけることができません。
 
-データソースの設定と編集の詳細については、[データソース s](https://docs.tealium.com/server-side/data-sources/about-data-sources/)を参照してください。
+データソースの設定と編集の詳細な手順については、[データソース](https://docs.tealium.com/server-side/data-sources/about-data-sources/)を参照してください。
 
-### ステップ2:イベント・コネクターの作成
+### ステップ2:イベントコネクターを作成する
 
-コネクターは、Tealiumと、データ通信に使用される別のベンダーとの間のインテグレーションです。これらのコネクターには、パートナーがサポートするAPI を表すアクションが含まれています。 
+コネクターとは、Tealium と他のベンダーの間でデータを伝送するために使用される統合です。これらのコネクターには、パートナーがサポートするAPI を表すアクションが含まれています。 
 
-1. **Server-Side** のTealiumのサイドバーから、**EventStream > Event Connectors** に移動します。
-2. 青色の**\+ Add Connector** ボタンを選択して、コネクター市場を調べます。アプリが耳にする新しいダイアログボックスで、スポットライト検索を使用して**Braze** コネクターを見つけます。
-3. このコネクターを追加するには、**Braze**コネクタータイルを選択します。クリックすると、接続の概要と、必要な情報、サポートされるアクション、および設定手順の一覧が表示されます。構成は、送信元、構成、およびアクションの3 つのステップで構成されます。
+1. Tealium のサイドバーの \[**Server-Side**] から **\[EventStream] > \[Event Connectors]** に移動します。
+2. 青色の \[**＋Add Connector**] ボタンを選択して、コネクターマーケットプレースを参照します。アプリが耳にする新しいダイアログボックスで、スポットライト検索を使用して**Braze** コネクターを見つけます。
+3. このコネクターを追加するには、**Braze**コネクタータイルを選択します。クリックすると、接続の概要と、必要な情報、サポートされるアクション、および設定手順の一覧が表示されます。この設定は、ソース、設定、アクションの3つのステップで構成されています。
 
 #### ソース
 
-ソースが設定されたら、**EventStream > Event Connectors > + Add Connector > Braze** のBraze コネクターページに戻ります。 
+ソースの設定が完了したら、**\[EventStream] > \[Event Connectors] > \[+ Add Connector] > \[Braze]** の Braze コネクタページに戻ります。 
 
 開封が作成したデータソースを選択し、**Event Feed**で**All Events**または特定のイベント仕様を選択して、変更された値のみをBrazeに送信する推奨パスを選択します。**Continue**をクリックします。
 
 #### 構成
 
-次に、ページの下部で**Add Connector** を選択します。コネクターに名前を付け、Braze API エンドポイントとBraze REST API キーを指定します。
+次に、ページの下部で**Add Connector** を選択します。コネクターに名前を付け、Braze エンドポイントと Braze REST API キーを指定します。
 
 ![][15]{: style="max-width:70%;"}
 
-以前にコネクタを作成した場合は、オプションとして、使用可能なコネクタリストから既存のコネクタを使用し、必要に応じて鉛筆アイコンで修正するか、ごみ箱アイコンで削除できます。 
+以前にコネクターを作成したことがある場合は、利用可能なコネクターのリストにある既存のコネクターを使用し、鉛筆アイコンでニーズに合わせて変更するか、ゴミ箱アイコンでコネクターを削除することができます。 
 
 #### アクション (Action)
 
-次に、コネクター・アクションに名前を付け、構成するmアプリに従って送信するアクションの種類を選択します。ここでは、Braze 属性s、行動、および購入をTealium 属性、行動、および購入の名前にマッピングします。
+次に、コネクターアクションに名前を付け、設定するマッピングに従ってデータを送信するアクションタイプを選択します。ここでは、Braze の属性、イベント、および購入をTealium の属性、イベント、および購入名にマッピングします。
 
 {% alert important %}
 提供されるすべてのフィールドが必要なわけではありません。
@@ -190,33 +190,33 @@ Tealiumでは、まずコネクターの有効なデータソースを設定す
 {% endalert %}
 
 {% tabs ローカル %}
-{% tab トラックユーザー(バッチおよび非バッチ) %}
+{% tab Track User (Batch および Non-Batch) %}
 
-このアクションでは、1つのアクションでユーザー、行動、購買属性をすべて追跡できます。
+このアクションを使用すると、ユーザー、イベント、購入属性をすべて1回のアクションで追跡できます。
 
 | パラメータ | 説明 |
 | ---------- | ----------- |
-| ユーザー ID | このフィールドを使用して、Tealium ユーザー ID フィールドを同等のBrazeにマップします。1 つ以上のユーザー ID 属性をマップします。複数のID が指定されている場合、最初の非ブランク値は、次の優先順位に基づいて選択されます。外部ID、Braze ID、別名、および別名ラベル。<br><br>\- プッシュトークンs をインポートする場合は、外部ID とBraze ID を指定しないでください。<br>\- ユーザー別名を指定する場合は、別名と別名を設定する必要があります。<br><br>詳細については、Braze[`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) を参照してください。 |
-| ユーザ属性 | Braze のユーザープロファイル フィールドネームを使用してBraze ダッシュボードに更新 ユーザープロファイルするか、独自のカスタム[ユーザー 属性]({{site.baseurl}}/api/objects_filters/user_attributes_object/) をユーザープロファイルs に追加します。<br><br>\- デフォルトでは、新しいユーザーs は存在しない場合に作成されます。<br>\- 設定では、** 更新 Existing Only** to `true` で、存在するユーザーs のみが更新d になり、新しいユーザーは作成されません。<br>\- Tealium 属性が空の場合は、NULL に変換され、Braze ユーザープロファイルから削除されます。ヌル値をBrazeに送信してユーザー 属性を削除しない場合は、エンリッチメントを使用する必要があります。 |
-| ユーザー 属性の変更s | このフィールドを使用して、特定のユーザー 属性を増減します<br><br>\- 整数属性s は正または負の整数でインクリメントできます。<br>\- 配列属性s は、既存の配列に数値を追加または削除することで修正できます。 |
-| イベント | イベントは、タイムスタンプでの特定のユーザーによるカスタムイベントの単一オカレンスを表します。このフィールドを使用して、Braze[event object]({{site.baseurl}}/api/objects_filters/event_object/) のようなイベント属性s を追跡およびマップします。<br><br>\- イベント属性`Name` は、m アプリの各イベントに必要です。<br>\- イベント属性`Time` は、明示的にm がアプリしない限り、自動的に現在に設定されます。<br>\- デフォルトでは、新しいイベントは存在しない場合に作成されます。設定では、`Update Existing Only` から`true` までは、既存のイベントのみが更新d になり、新しいイベントは作成されません。<br>\- 配列型属性s をマップして、複数のイベントを追加します。配列型の属性s は等しい長さでなければなりません。<br>\- 単一の属性s を使用し、それぞれの事象にアプリを置くことができます。 |
-| 事象テンプレート | ボディデータで参照するイベントテンプレートを指定します。テンプレートを使用してデータを変換してから、Brazeに送信できます。詳細については、Tealiumの[テンプレートガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/)を参照してください。 |
-| 事象テンプレート | データインプットとして事象テンプレートを提供する。詳細については、Tealiumの[テンプレート変数ガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/template-variables/)を参照してください。 |
-| 購入 | このフィールドを使用して、Braze[purchase object]({{site.baseurl}}/api/objects_filters/purchase_object/) のようにユーザーの購買属性s を追跡およびマップします。<br><br>\- 購入属性s `Product ID`、`Currency`、および`Price` は、購入するm アプリごとに必要です。<br>\- 購入属性`Time` は、明示的にm がアプリされない限り、自動的に現在に設定されます。<br>\- デフォルトでは、新規購入は存在しない場合に作成されます。設定では、`Update Existing Only` から`true` までは、既購入分のみが更新 d となり、新規購入分は作成されません。<br>\- 配列型属性s をマップして、複数の購入アイテムを追加します。配列型の属性s は等しい長さでなければなりません。<br>\- 1つの数値属性sを使うことができ、それぞれの項目にアプリします。|
-| 購買テンプレート | テンプレートを使用して、Brazeに送信する前にデータを変換できます。<br>\- ネストされたオブジェクトサポートが必要な場合は、購入テンプレートを定義します。<br>\- 購入テンプレートが定義されている場合、アクションの購入セクションで設定された設定は無視されます。<br>\- 詳細については、Tealiumの[テンプレートガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/)を参照してください。|
+| ユーザー ID | このフィールドを使用して、Tealium のユーザー ID フィールドを Braze の対応するフィールドにマッピングします。1 つ以上のユーザー ID 属性をマップします。複数のID が指定されている場合、最初の非ブランク値は、次の優先順位に基づいて選択されます。External ID、Braze ID、エイリアス名、エイリアスラベル。<br><br>\- プッシュトークンs をインポートする場合は、外部ID とBraze ID を指定しないでください。<br>\- ユーザーエイリアスを指定する場合、エイリアス名とエイリアスラベルの両方を設定する必要があります。<br><br>詳細については、Braze[`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) を参照してください。 |
+| ユーザ属性 | Braze の既存のユーザープロファイルのフィールド名を使用して、Braze ダッシュボードのユーザープロファイル値を更新するか、独自のカスタム[ユーザー属性]({{site.baseurl}}/api/objects_filters/user_attributes_object/)データをユーザープロファイルに追加します。<br><br>\- デフォルトでは、新規ユーザーが存在しない場合は作成されます。<br>\- 設定では、** 更新 Existing Only** to `true` で、存在するユーザーs のみが更新d になり、新しいユーザーは作成されません。<br>\- Tealium 属性が空の場合、その属性は NULL に変換され、Braze ユーザープロファイルから削除されます。ユーザー属性を削除する目的で Braze に NULL 値を送信すべきでない場合は、エンリッチメントを使用してください。 |
+| Modify user attributes | このフィールドを使用して、特定のユーザー 属性を増減します<br><br>\- 整数属性は、正の整数または負の整数でインクリメントできます。<br>\- 配列属性s は、既存の配列に数値を追加または削除することで修正できます。 |
+| イベント | イベントは、タイムスタンプの時点で特定のユーザーによりカスタムイベントが1回発生したことを表します。このフィールドは、Braze [イベントオブジェクト]({{site.baseurl}}/api/objects_filters/event_object/)の属性と同様にイベント属性を追跡、マッピングする場合に使用します。<br><br>\- イベント属性 `Name` は、マッピングされたすべてのイベントで必要です。<br>\- イベント属性 `Time` は、明示的にマッピングされていない限り、自動的に現時点の時刻に設定されます。<br>\- デフォルトでは、新しいイベントは存在しない場合に作成されます。`Update Existing Only` を`true` に設定すると、既存のイベントのみが更新され、新規のイベントは作成されません。<br>\- 配列型属性s をマップして、複数のイベントを追加します。配列型の属性s は等しい長さでなければなりません。<br>\- 単一値属性を使用できます。単一値属性は各イベントに適用できます。 |
+| Event template | ボディデータで参照するイベントテンプレートを指定します。テンプレートを使用してデータを変換してから、Brazeに送信できます。詳細については、Tealiumの[テンプレートガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/)を参照してください。 |
+| Event template variable | イベントテンプレート変数をデータ入力として指定します。詳細については、Tealiumの[テンプレート変数ガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/template-variables/)を参照してください。 |
+| 購入 | このフィールドは、Braze [購入オブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/)の属性と同様に購入属性を追跡、マッピングする場合に使用します。<br><br>\- 購入属性 `Product ID`、`Currency`、`Price` は、マッピングされたすべての購入に必要です。<br>\- 購入属性 `Time` は、明示的にマッピングされていない限り、自動的に現時点の時刻に設定されます。<br>\- デフォルトでは、新規購入が存在しない場合は作成されます。`Update Existing Only` を`true` に設定すると、既存の購入のみが更新され、新規購入は作成されません。<br>\- 配列型属性s をマップして、複数の購入アイテムを追加します。配列型の属性s は等しい長さでなければなりません。<br>\- 単一値属性を使用できます。単一値属性は各アイテムに適用されます。|
+| 購買テンプレート | テンプレートを使用して、Brazeに送信する前にデータを変換できます。<br>\- ネストされたオブジェクトサポートが必要な場合は、購入テンプレートを定義します。<br>\- 購入テンプレートを定義すると、アクションの購入セクションで設定された設定は無視されます。<br>\- 詳細については、Tealiumの[テンプレートガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/)を参照してください。|
 | 購買テンプレート変数 | 商品テンプレートの項目を入力します。詳細については、Tealiumの[テンプレート変数ガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/template-variables/)を参照してください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ![]({% image_buster /assets/img/tealium/track_user_example.png %})
 
 {% endtab %}
-{% tab ユーザーの削除(非バッチ) %}
+{% tab Delete User (Non-Batch) %}
 
-このアクションでは、Braze ダッシュボードからユーザーs を消去できます。
+このアクションでは、Braze ダッシュボードからユーザーを削除できます。
 
 | パラメータ | 説明 |
 | ---------- | ----------- |
-| ユーザー ID | このフィールドを使用して、TealiumのユーザID フィールドをBraze同等のものにマップします。<br><br>\- 1 つ以上のユーザー ID 属性をマップします。複数のID が指定されている場合、最初の非ブランク値は、次の優先順位に基づいて選択されます。外部ID、Braze ID、別名、および別名ラベル。<br>\- ユーザー別名を指定する場合は、別名と別名ラベルの両方を設定する必要があります。<br><br>詳細については、Braze[`/users/delete` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/) を参照してください。 |
+| ユーザー ID | このフィールドを使用して、Tealium のユーザー ID フィールドを Braze の対応するフィールドにマッピングします。<br><br>\- 1 つ以上のユーザー ID 属性をマップします。複数のID が指定されている場合、最初の非ブランク値は、次の優先順位に基づいて選択されます。External ID、Braze ID、エイリアス名、エイリアスラベル。<br>\- ユーザーエイリアスを指定する場合、エイリアス名とエイリアスラベルの両方を設定する必要があります。<br><br>詳細については、Braze[`/users/delete` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/) を参照してください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ![]({% image_buster /assets/img/tealium/track_user_delete.png %})
@@ -228,21 +228,21 @@ Tealiumでは、まずコネクターの有効なデータソースを設定す
 
 **Continue**を選択します。
 
-コネクターがTealiumのホームページのコネクターの一覧に表示されるようになりました。<br>![][13]{: style="max-width:80%;"}
+コネクターが Tealium ホームページのコネクターリストに表示されます。<br>![][13]{: style="max-width:80%;"}
 
-終了したら、必ず**Save / Publish**コネクタを使用してください。設定したアクションは、トリガーコネクションが満たされると起動します。 
+終了したら、必ず**Save / Publish**コネクタを使用してください。設定したアクションは、トリガー接続が満たされたときに実行されます。 
 
-### ステップ3:Tealiumコネクターのテスト
+### ステップ3:Tealium コネクターをテストする
 
-コネクタが起動して実行されたら、正しく動作することをテストする必要があります。これを検証する最も簡単な方法は、Tealium**トレースツール**を使用することです。トレースの使用を開始するには、Tealium ツールブラウザ拡張を追加したことを確認します。
+コネクターが稼動したら、正常に動作していることを確認するため、コネクターをテストする必要があります。これを検証する最も簡単な方法は、Tealium**トレースツール**を使用することです。Trace の使用を開始するには、Tealium Tools ブラウザー拡張機能が追加されていることを確認します。
 
-1. 新しいトレースを開始するには、**Server-Side** オプションの下のサイドバーで**Trace** を選択します。**Start**をクリックし、Trace ID をキャプチャします。
-2. ブラウザ拡張を開き、AudienceStream Trace にTrace ID を入力します。
+1. 新しいトレースを開始するには、サイドバーの \[**Server-Side**] のオプションから \[**Trace**] を選択します。\[**Start**] をクリックし、トレース ID をキャプチャします。
+2. ブラウザー拡張機能を開き、AudienceStream Trace にトレース ID を入力します。
 3. リアルタイムログを調べます。
-4. **アクション s Triggered** エントリをクリックして、検証するアクションを確認します。
+4. 展開する **Actions Triggered** エントリをクリックして、検証するアクションを確認します。
 5. 検証するアクションを探して、ログステータスを表示します。 
 
-Tealium のトレースツールの実装に関する詳細な手順については、Tealium の\[トレースドキュメント][21] を参照してください。
+Tealium の Trace ツールの詳しい実装手順については、Tealium の \[Trace ドキュメント][21]を参照してください。
 
 ## 統合デモ
 
@@ -252,19 +252,19 @@ Tealium のトレースツールの実装に関する詳細な手順について
 
 ## 潜在データポイント 超過料金s
 
-Tealium を介してBrazeを統合するときに、誤ってデータ超過料金s を操作する可能性がある主な方法は3 つあります。
+Tealium から Braze を統合するときに、誤ってデータ超過料金が生じる主な状況が3つあります。
 
 #### 重複データの送信- Brazeの属性の差分のみを送信します
-Tealium は、ユーザー 属性s のBrazeの差分を送信しません。たとえば、EventStream アクションでユーザーの名、メール、および携帯電話番号を追跡している場合、アクションがトリガーされると、Tealium は3 つの属性すべてをBraze に送信します。Tealiumは、変更されたものや更新されたものを探し、その情報のみを送信しません。<br><br> 
-**解決策**:<br>バックエンドを確認して、属性が変更されているかどうかを評価し、変更されている場合は、Tealium の関連メソッドを呼び出してユーザープロファイルを更新できます。**これは、Brazeを直接的に統合するユーザーが通常行うことである。**<br>**または**<br> 自分のバージョンのユーザープロファイルをバックエンドに保存せず、属性が変更されたかどうかを判断できない場合は、AudienceStream を使用できます
-[エンリッチメントを作成](https://docs.tealium.com/server-side/attributes/manage-enrichments/add-enrichment/) 値が変更されたときにのみユーザー 属性s を送信します。[エンリッチメントルール](https://docs.tealium.com/server-side-connectors/braze-connector/)に関するTealiumのドキュメントを参照してください。
+Tealium はユーザー属性の Braze 差分を送信しません。たとえば、EventStream アクションでユーザーの名、メール、および携帯電話番号を追跡している場合、このアクションがトリガーされると、Tealium は3つの属性すべてを Braze に送信します。Tealium は、変更された内容や更新された内容を探してその情報のみを送信することはありません。<br><br> 
+**解決策**:<br>バックエンドを確認して、属性が変更されているかどうかを評価し、変更されている場合は、Tealium の関連メソッドを呼び出してユーザープロファイルを更新できます。**これは、Braze を直接統合するユーザーが通常行う作業です。**<br>**または**<br> 自分自身のユーザープロファイルをバックエンドに保存しておらず、属性が変更されたかどうかを判断できない場合は、AudienceStream を使用して
+[エンリッチメントを作成](https://docs.tealium.com/server-side/attributes/manage-enrichments/add-enrichment/) 値が変更されたときにのみユーザー 属性s を送信します。[エンリッチメントルール](https://docs.tealium.com/server-side-connectors/braze-connector/)に関する Tealium のドキュメントを参照してください。
 
 #### 無関係なデータの送信またはデータの不必要な上書き
-同じイベントフィードをターゲットとする複数のEventStreams がある場合、そのコネクタ で有効になっているすべてのアクションは、1 つのアクションがトリガーされるたびに自動的に起動されます。**これにより、Brazeでデータが上書きされ、不必要なデータポイントを消費することもあります。**<br><br>
-**解決策**:<br>それぞれのアクションを追跡するために、個別のイベント指定またはフィードを設定します。<br>**または**<br> Tealium ダッシュボードのトグルを使用して、起動しないアクション(またはコネクター)を無効にします。
+同じイベントフィードをターゲットとする複数の EventStream がある場合、1つのアクションがトリガーされるたびに、**そのコネクターで有効になっているすべてのアクション**が自動的に起動します。**その結果、Braze でデータが上書きされ、不要なデータポイントが消費される可能性があります。**<br><br>
+**解決策**:<br>それぞれのアクションを追跡するために、個別のイベント指定またはフィードを設定します。<br>**または**<br> Tealium ダッシュボードのトグルを使用して、起動しないアクション (またはコネクター) を無効にします。
 
 #### Brazeの初期化が早すぎる
-Braze Web SDK タグ を使用してTealium と統合すると、MAU が大幅に増えることがあります。**Braze がページ読み込むで初期化されている場合、Web ユーザーが初めてWeb サイトに移動するたびに、Braze によって匿名プロファイルが作成されます。**ユーザーが"Signed In"または"Watched Video"など、いくつかのアクションを完了したときにのみ、MAU数を減らすためにユーザーの挙動を追跡することを望む人もいるかもしれません。<br><br>
+Braze Web SDK タグを使用して Tealium と統合するユーザーの場合、MAU が大幅に増加する可能性があります。**Braze がページ読み込むで初期化されている場合、Web ユーザーが初めてWeb サイトに移動するたびに、Braze によって匿名プロファイルが作成されます。**ユーザーが"Signed In"または"Watched Video"など、いくつかのアクションを完了したときにのみ、MAU数を減らすためにユーザーの挙動を追跡することを望む人もいるかもしれません。<br><br>
 **解決策**:<br>[ 読み込む規則](https://docs.tealium.com/iq-tag-management/load-rules/about/) を設定して、タグ 読み込むがいつどこにあるかを正確に判断します。 
 
 [1]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream.md
index b8484ed3f6c..93f0f536d98 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_audience_stream.md
@@ -3,7 +3,7 @@ nav_title: Tealium AudienceStream
 article_title: Tealium AudienceStream
 page_order: 2
 alias: /partners/tealium_audience_stream/
-description: "この参考記事では、モバイル、ウェブ、代替データを他のサードパーティ・ソースに接続できるユニバーサル・データ・ハブであるBrazeとTealiumのパートナーシップについて概説している。"
+description: "このリファレンス記事では、Braze と Tealium のパートナーシップについて説明します。Tealium は、モバイルデータ、Web データ、代替データを他のサードパーティソースに接続できるユニバーサルデータハブです。"
 page_type: partner
 search_tag: Partner
 
@@ -11,12 +11,12 @@ search_tag: Partner
 
 # Tealium AudienceStream
 
-> Tealium[AudienceStreamは](https://docs.tealium.com/server-side/getting-started/audiencestream-cdp/introduction/)、オムニチャネルの顧客セグメンテーションとリアルタイムアクションエンジンである。AudienceStreamは、EventStreamに流れ込むデータを取り込み、顧客のブランドに対するエンゲージメントの最も重要な属性を表す訪問者プロファイルを作成する。 
+> Tealium [AudienceStream](https://docs.tealium.com/server-side/getting-started/audiencestream-cdp/introduction/) は、オムニチャネルの顧客セグメンテーションおよびリアルタイムアクションエンジンです。AudienceStream は EventStream に流入するデータを取得し、ブランドのカスタマーエンゲージメントの最も重要な属性を表す訪問者プロファイルを作成します。 
 
-BrazeとTealiumの統合は、AudienceStreamの訪問者プロファイルを活用している。共有された行動は、オーディエンスと呼ばれる共通の特徴を持つ訪問者のセットを作成するために、これらのプロファイルをセグメント化する。これらのオーディエンスは、コネクターを通じてリアルタイムでマーケティング・テクノロジー・スタックに燃料を供給することができる。 
+Brazeと Tealium の統合には、AudienceStream の訪問者プロファイルが利用されています。共有された行動は、オーディエンスと呼ばれる共通の特徴を持つ訪問者のセットを作成するために、これらのプロファイルをセグメント化する。これらのオーディエンスは、コネクターを介してリアルタイムでマーケティングテクノロジースタックにデータを提供できます。 
 
 {% alert important %}
-TealiumのAudienceStreamsとEventStreamsは、バッチと非バッチの両方のコネクターアクションを提供する。非バッチコネクターは、リアルタイムリクエストがユースケースにとって重要で、BrazeのAPIレート制限仕様にヒットする懸念がない場合に使用すべきである。ご質問がある場合は、Braze[サポート]({{site.baseurl}}/braze_support/)またはカスタマーサクセスマネージャーにお問い合わせください。
+TealiumのAudienceStreamsとEventStreamsは、バッチと非バッチの両方のコネクターアクションを提供する。非バッチコネクターは、リアルタイムリクエストがユースケースにとって重要であり、Braze の API レート制限指定に達する懸念がない場合にのみ使用してください。ご質問がある場合は、Braze [サポート]({{site.baseurl}}/braze_support/)またはカスタマーサクセスマネージャーにお問い合わせください。
 {% endalert %}
 
 ## 前提条件
@@ -24,8 +24,8 @@ TealiumのAudienceStreamsとEventStreamsは、バッチと非バッチの両方
 | 名前 | 説明 |
 | ---- | ----------- |
 | Tealiumアカウント | サーバー側にアクセスできる[Tealiumアカウントが](https://my.tealiumiq.com/)必要である。このパートナーシップを活用するために、クライアント側のインテグレーションも利用することをお勧めする。 |
-| REST APIキー | `users.track`,`users.delete`,`subscription.status.set` のパーミッションを持つBraze REST APIキー。<br><br>これは、**Brazeのダッシュボード > Developer Console > REST API Key > Create New API Keyで**作成できる。|
-| \[Braze RESTエンドポイント][6] | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに]({{site.baseurl}}/api/basics/#endpoints)依存する。 |
+| REST APIキー | `users.track`,`users.delete`,および `subscription.status.set` の権限を持つ Braze REST API キー。<br><br>これは **Brazeダッシュボード > \[開発者コンソール] > \[REST API キー] > \[新しい API キーを作成]** で作成できます|
+| \[Braze RESTエンドポイント][6] | RESTエンドポイントのURL。エンドポイントは[インスタンスの Braze URL]({{site.baseurl}}/api/basics/#endpoints) に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
@@ -34,108 +34,108 @@ TealiumのAudienceStreamsとEventStreamsは、バッチと非バッチの両方
 
 #### 属性を理解する
 
-AudienceStreamを使う最初のステップは、属性を作成することだ。属性は、訪問者の習慣、好み、行動、ブランドとの関わりを表す重要な特徴を定義することができる。 
+AudienceStreamを使う最初のステップは、属性を作成することだ。属性を使用して、訪問者の習慣、好み、アクション、ブランドへのエンゲージメントを表す重要な特性を定義できます。 
 
-**属性を訪問する**：Visit属性は、ユーザーの現在の訪問（またはセッション）に関連する。これらの属性に保存されたデータは、訪問期間中持続する。訪問属性の例をいくつか挙げる：
-- 訪問期間（人）
+**訪問属性**:Visit属性は、ユーザーの現在の訪問（またはセッション）に関連する。これらの属性に保存されたデータは、訪問期間中持続する。訪問属性の例をいくつか挙げる：
+- Visit Duration (数値)
 - 現在のブラウザ (文字列)
-- 現在のデバイス (文字列)
+- Current Device (文字列)
 - ページビュー数（数）
 
-**ビジター属性**：ビジター属性は現在のユーザーに関連する。これらのアトリビュートに保存されたデータは、ユーザーの生涯にわたって持続する。ビジター属性の例としては、以下のようなものがある： 
-- 生涯受注額（数字）
-- 名 (文字列)
+**訪問者属性**:ビジター属性は現在のユーザーに関連する。これらの属性に保存されるデータは、ユーザーの存続期間全体にわたって持続します。訪問者属性の例としては、以下のものがあります。 
+- Lifetime Order Value (数値)
+- First Name (文字列)
 - 生年月日（日付）
-- 買取ブランド（集計）
+- Purchases Brands (集計)
 
 利用可能なデータタイプの全リストは[Tealiumを][1]参照のこと。
 
-##### 属性の強化
+##### 属性エンリッチメント
 
-必要な属性を特定したら、それを[エンリッチメント](https://docs.tealium.com/server-side/getting-started/audiencestream-cdp/attributes-enrichments/)（属性の値をいつ、どのように更新するかを決定するビジネスルール）で構成することができる。それぞれのデータ型は、属性の値を操作するための独自のエンリッチメントの選択を提供する。これは "WHEN "設定と関連している。各訪問者および訪問者の属性に対して、以下のオプションが利用可能である：
+必要な属性を特定したら、それを[エンリッチメント](https://docs.tealium.com/server-side/getting-started/audiencestream-cdp/attributes-enrichments/)（属性の値をいつ、どのように更新するかを決定するビジネスルール）で構成することができる。それぞれのデータ型は、属性の値を操作するための独自のエンリッチメントの選択を提供する。これは "WHEN "設定と関連している。各訪問属性および訪問者属性で利用可能なオプションを以下に示します。
 
 - 新規訪問者：訪問者があなたのサイトに初めて来たときに発生する。
 - 新規訪問：ビジターが新規に訪問した際に発生する。
-- エニー・イベント：どのイベントでも発生する。
-- Visit Ended：訪問が終了したときに発生する。
+- Any Event: 任意のイベントで発生します。
+- Visit Ended: 訪問が終了したときに発生します。
 
-また、ルールと呼ばれるカスタム条件を作成し、エンリッチメントが発生するタイミングを決定することもできる。
+また、エンリッチメントが発生するタイミングを決定するカスタム条件 (ルール) を作成することもできます。
 
 #### バッジ
 
-バッジは、貴重な行動パターンを表す特別なビジター属性である。バッジは、訪問者のエンリッチメントのロジックに基づいて割り当てられたり、外されたりする。このロジックは通常、訪問者セグメントを捕捉するために複数の条件を組み合わせたり、特定の値に達したときのしきい値を設定したりする。
+バッジは、価値の高い行動パターンを表す特別な訪問者属性です。バッジは、訪問者のエンリッチメントのロジックに基づいて割り当てられたり、外されたりする。このロジックは通常、訪問者セグメントを捕捉するために複数の条件を組み合わせたり、特定の値に達したときのしきい値を設定したりする。
 
 #### 属性とバッジの例
 
 {% tabs ローカル %}
 {% tab 属性 %}
 
-すべての完了した注文（購入イベント）に対して、顧客が費やした累積金額（`order_total` ）を計算するビジター属性 "Lifetime Order Value "を作成する。Tealiumアカウントでライフタイムオーダーバリューを設定するには、以下の指示に従う：
+すべての完了した注文 (購入イベント) での顧客の累積支出額 (`order_total`) を計算する訪問者属性「Lifetime Order Value」を作成します。Tealium アカウントで生涯注文額を設定するには、次の手順に従います。
 
-1. **AudienceStream > Visitor/Visit Attributesに**移動し、**Add Attributeを**クリックする。
-2. スコープを**ビジターとして**選択し、**Continueを**クリックする。
-3. データ型「**Number」を**選択し、「**Continue**」をクリックする。
-4. 属性名 "Lifetime Order Value "を入力する。
-5. **Add Enrichmentを**クリックし、**Increment NumberまたはDecrement Numberを**選択する。
+1. **\[AudienceStream] > \[Visitor/Visit Attributes]** に移動して \[**Add Attribute**] をクリックします。
+2. スコープとして \[**Visitor**] を選択して \[**Continue**] をクリックします。
+3. データ型として \[**Number**] を選択して \[**Continue**] をクリックします。
+4. 属性名として「Lifetime Order Value」を入力します。
+5. \[**Add Enrichmentを**] をクリックし、\[**Increment or Decrement Number**] を選択します。
 6. インクリメントする値を含む属性を選択する（`order_total` ）。
-7. WHEN "を "Any Event "に設定したまま、**"Create a New Rule**"をクリックする。
+7. \[WHEN] は \[Any Event] のままにしておき、\[**Create a New Rule**] をクリックします。
 8. 購入イベントがいつ発生したかを識別するルールを作成する。
-9. **Saveを**クリックし、**Finishを**クリックする。
+9. \[**Save**] をクリックし、\[**Finish**] をクリッします。
 
-これで、すべての顧客は生涯注文価値属性を持つことになる。
+これで、すべての顧客に生涯注文額属性が関連付けられます。
 
 {% endtab %}
 {% tab バッジ %}
 
-バッジを作成することで、ユーザーが共有する特定の属性によってユーザーを分類し、ターゲットを絞ることができる。次の例では、"Lifetime Order Value "が$500以上のユーザーに対してVIPバッジを作成する。
+バッジを作成することで、ユーザーが共有する特定の属性によってユーザーを分類し、ターゲットを絞ることができる。次の例では、「Lifetime Order Value」が$500を超えるユーザーに対して VIP バッジを作成します。
 
-1. **AudienceStream > Visitor/Visit Attributesに**移動し、**Add Attributeを**クリックする。
-2. スコープを**ビジターとして**選択し、**Continueを**クリックする。
-3. データ・タイプ**Badgeを**選択し、**Continueを**クリックする。
+1. **\[AudienceStream] > \[Visitor/Visit Attributes]** に移動して \[**Add Attribute**] をクリックします。
+2. スコープとして \[**Visitor**] を選択して \[**Continue**] をクリックします。
+3. データ型として \[**Badge**] を選択して \[**Continue**] をクリックします。
 4. バッジの名前「VIP」を入力する。
-5. **Add Enrichmentを**クリックし、**Assign Badgeを**選択する。
+5. \[**Add Enrichment**] をクリックし、\[**Assign Badge**] を選択します。
 6. WHEN "は "Any Event "のままにしておく。
-7. **Create Rule（ルールの作成）を**選択して、バッジ割り当てのルールを作成する。このルールにタイトルを割り当て、前回作成した属性を使用して、ルールを「...属性 "Lifetime Order Value greater than 500 "を持つ」と設定する。
-8. **Saveを**クリックし、**Finishを**クリックする。
+7. \[**Create Rule**] を選択して、バッジ割り当てのルールを作成します。このルールにタイトルを割り当て、前回作成した属性を使用して、ルールを「...属性 "Lifetime Order Value greater than 500 "を持つ」と設定する。
+8. \[**Save**] をクリックし、\[**Finish**] をクリックします。
 
 {% endtab %}
 {% endtabs %}
 
-### ステップ2:観客を作る
+### ステップ2:オーディエンスを作成する
 
-Tealiumのホームページから、サイドバーナビゲーションで**AudienceStreamの**下にある**Audiencesを**選択する。ここでは、共通の属性を持つユーザーのオーディエンスを作成することができる。このオーディエンスへのユーザの入室または退室は、次のステップで設定するコネクタアクションのトリガとなり、この情報をBrazeのユーザプロファイルに渡す。 
+Tealium のホームページから、サイドバーナビゲーションの \[**AudienceStream**] の \[**Audiences**] を選択します。ここでは、共通の属性を持つユーザーのオーディエンスを作成できます。このオーディエンスへのユーザーの出入りが、次のステップで設定する Connector Action のトリガーとなり、この情報が Braze のユーザープロファイルに渡されます。 
 
-まず、オーディエンスに名前を付け、あなたが作ろうとしているオーディエンスのタイプにはどのような属性が当てはまるかを考える。例えば、VIPユーザーのオーディエンスを作成するには、**VIPバッジを持って**いる訪問者のオーディエンスを作成することができる。
+まず、オーディエンスに名前を付けてから、作成するオーディエンスのタイプに適用する属性を検討します。たとえば VIP ユーザーのオーディエンスを作成するには、**VIP バッジ**を持つ訪問者のオーディエンスを作成することができます。
 
-終了したら、必ずオーディエンスを**保存／公開**すること。
+終了したら、オーディエンスを必ず**保存 / 公開**してください。
 
 ### ステップ3:イベントコネクターを作成する
 
-コネクターとは、Tealiumと他のベンダーの間でデータを伝送するために使用される統合のことである。これらのコネクターには、パートナーがサポートするAPIを表すアクションが含まれている。 
+コネクターとは、Tealium と他のベンダーの間でデータを伝送するために使用される統合です。これらのコネクターには、パートナーがサポートするAPIを表すアクションが含まれている。 
 
-1. Tealiumのサイドバーの**Server-Sideから**、**AudienceStream > Audience Connectorsに**移動する。
-2. 青い**＋Add Connector**ボタンを選択し、コネクタ市場を調べる。表示された新しいダイアログボックスで、スポットライト検索を使って**Braze**コネクタを探す。
-3. このコネクタを追加するには、**Braze**コネクタタイルをクリックする。クリックすると、接続の概要と、必要な情報、サポートされているアクション、設定手順のリストが表示される。コンフィギュレーションは、ソース、コンフィギュレーション、アクションの3つのステップで構成される。
+1. Tealium のサイドバーの \[**Server-Side**] から **\[AudienceStream] > \[Audience Connectors]** に移動します。
+2. 青色の \[**＋Add Connector**] ボタンを選択して、コネクターマーケットプレースを参照します。表示された新しいダイアログボックスで、スポットライト検索を使って**Braze**コネクタを探す。
+3. このコネクタを追加するには、**Braze**コネクタタイルをクリックする。クリックすると、接続の概要と、必要な情報、サポートされているアクション、設定手順のリストが表示される。この設定は、ソース、設定、アクションの3つのステップで構成されています。
 
 #### ソース
 
-表示される**Source**ダイアログで、前のステップで作成したオーディエンスと、状況に適していると思われるトリガーを選択する。また、このアクションがトリガーされる頻度をコントロールするために、頻度キャップを切り替えることもできる。 
+表示される**Source**ダイアログで、前のステップで作成したオーディエンスと、状況に適していると思われるトリガーを選択する。また、このアクションのトリガーの頻度を制御するためにフリークエンシーキャップをオンに切り替えることもできます。 
 
 ![]({% image_buster /assets/img/tealium/create_source.png %}){: style="max-width:90%;"}
 
 #### 構成
 
-次に、**設定**ダイアログが表示される。ページ下部の**Add Connectorを**選択する。コネクタに名前を付け、Braze APIエンドポイントとBraze REST APIキーをここに入力する。
+次に、**設定**ダイアログが表示される。ページ下部の \[**Add Connector**] を選択します。コネクタに名前を付け、Braze APIエンドポイントとBraze REST APIキーをここに入力する。
 
 ![]({% image_buster /assets/img/tealium/create_configuration.png %}){: style="max-width:70%;"}
 
-以前にコネクタを作成したことがある場合は、利用可能なコネクタリストから既存のコネクタを使用し、鉛筆アイコンでニーズに合うように修正するか、ゴミ箱アイコンで削除することもできる。 
+以前にコネクターを作成したことがある場合は、利用可能なコネクターのリストにある既存のコネクターを使用し、鉛筆アイコンでニーズに合わせて変更するか、ゴミ箱アイコンでコネクターを削除することができます。 
 
-このオーディエンスをリンクするコネクタを作成または選択したら、Doneをクリックして続行する。
+このオーディエンスをリンクするコネクターを作成または選択したら、\[Done] をクリックして続行します。
 
 #### アクション (Action)
 
-次に、コネクターアクションに名前を付け、設定したマッピングに従ってデータを送信するアクションタイプを選択する。ここでは、Brazeの属性をTealiumの属性名にマッピングする。どのアクションタイプを選択するかによって、Tealiumが要求するフィールドはさまざまに選択される。以下は、これらのフィールドの例と説明である。
+次に、コネクターアクションに名前を付け、設定したマッピングに従ってデータを送信するアクションタイプを選択する。ここでは、Brazeの属性をTealiumの属性名にマッピングする。選択するアクションタイプに応じて、Tealium で必要となるフィールドは異なります。以下は、これらのフィールドの例と説明である。
 
 {% alert important %}
 すべての項目が必須というわけではない。
@@ -144,46 +144,46 @@ Tealiumのホームページから、サイドバーナビゲーションで**Au
 {% endalert %}
 
 {% tabs ローカル %}
-{% tab ユーザーを追跡する（バッチと非バッチ） %}
+{% tab Track User (Batch および Non-Batch) %}
 
-このアクションでは、ユーザー、イベント、購入の属性を1つのアクションですべて追跡できる。Track UserアクションはAudienceStreamとEventStreamの両方で同じだが、TealiumはAudienceStreamアクションでユーザー属性のマッピングを設定し、EventStreamアクションでイベントと購入のマッピングを設定することを推奨する。
+このアクションでは、ユーザー、イベント、購入の属性を1つのアクションですべて追跡できる。Track User アクションは AudienceStream と EventStream の両方で同じですが、Tealium はAudienceStream アクションでユーザー属性のマッピングを設定し、EventStream アクションでイベントと購入のマッピングを設定することを推奨しています。
 
 | パラメーター | 説明 |
 | ---------- | ----------- |
-| ユーザー ID | このフィールドを使用して、TealiumユーザーIDフィールドとBrazeユーザーIDフィールドを対応させる。1つ以上のユーザーID属性をマップする。複数のIDが指定された場合、以下の優先順位に基づいて、空白でない最初の値が選ばれる：外部ID、ブレイズID、エイリアス名、エイリアスラベル。<br><br>\- プッシュトークンをインポートする場合、外部IDとBraze IDを指定すべきではない。<br>\- ユーザーエイリアスを指定する場合は、エイリアス名とエイリアスラベルを設定する必要がある。<br><br>詳しくは、Braze[`/users/track` のエンド]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)ポイントをチェックしてほしい。 |
-| ユーザー属性 | Brazeの既存のユーザープロファイルのフィールド名を使用して、Brazeダッシュボードのユーザープロファイル値を更新するか、独自のカスタム[ユーザー属性]({{site.baseurl}}/api/objects_filters/user_attributes_object/)データをユーザープロファイルに追加する。<br><br>\- デフォルトでは、ユーザーが存在しない場合、新しいユーザーが作成される。<br>-**Update Existing Onlyを** `true` に設定すると、既存のユーザーのみが更新され、新規ユーザーは作成されない。<br>\- Tealium属性が空の場合、NULLに変換され、Brazeユーザープロファイルから削除される。ユーザー属性を削除するためにBrazeにNULL値を送信すべきでない場合は、エンリッチメントを使用すべきである。 |
-| ユーザー属性を変更する | このフィールドを使用して、特定のユーザー属性をインクリメントまたはデクリメントする。<br><br>\- 整数属性は、正の整数または負の整数でインクリメントすることができる。<br>\- 配列の属性は、既存の配列に値を追加したり削除したりすることで変更できる。 |
-| イベント | イベントは、タイムスタンプにおける、特定のユーザーによるカスタムイベントの単一発生を表す。このフィールドを使用して、Braze[イベントオブジェクトに]({{site.baseurl}}/api/objects_filters/event_object/)あるようなイベント属性を追跡し、マッピングする。<br><br>\- イベント属性`Name` は、マッピングされたイベントごとに必要である。<br>\- イベント属性`Time` は、明示的にマッピングされない限り、自動的にnowに設定される。<br>\- デフォルトでは、イベントが存在しない場合、新しいイベントが作成される。`Update Existing Only` を`true` に設定すると、既存のイベントのみが更新され、新しいイベントは作成されない。<br>\- 配列タイプの属性をマップして、複数のイベントを追加する。配列型の属性は同じ長さでなければならない。<br>\- 単一値属性を使用し、各イベントに適用することができる。 |
-| イベントテンプレート | ボディデータで参照されるイベントテンプレートを提供する。Brazeにデータを送る前に、テンプレートを使ってデータを変換することができる。詳しくはTealiumの[テンプレートガイドを](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/)参照のこと。 |
-| イベントテンプレート変数 | イベントテンプレート変数をデータ入力として提供する。詳しくはTealiumの[テンプレート変数ガイドを](https://docs.tealium.com/server-side/connectors/webhook-connectors/template-variables/)参照のこと。 |
-| 購入 | このフィールドを使用して、Brazeの[購買オブジェクトに]({{site.baseurl}}/api/objects_filters/purchase_object/)あるようなユーザーの購買属性を追跡し、マッピングする。<br><br>-`Product ID` 、`Currency` 、`Price` の購買属性は、マッピングされた購買ごとに必要である。<br>\- 購買属性`Time` は、明示的にマッピングされない限り、自動的にnowに設定される。<br>\- デフォルトでは、新規購入が存在しない場合、新規購入が作成される。`Update Existing Only` を`true` に設定すると、既存の購入のみが更新され、新しい購入は作成されない。<br>\- 複数の購入項目を追加するために、配列タイプの属性をマップする。配列型の属性は同じ長さでなければならない。<br>\- 単一値属性を使用することができ、各項目に適用される。|
-| テンプレート購入 | テンプレートは、Brazeに送信する前にデータを変換するために使用できる。<br>\- ネストされたオブジェクトのサポートが必要な場合は、購入テンプレートを定義する。<br>\- 購入テンプレートが定義されると、アクションの購入セクションで設定されたコンフィギュレーションは無視される。<br>\- 詳しくはTealiumの[テンプレートガイドを](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/)参照のこと。|
-| 購入テンプレート変数 | 製品テンプレートの変数をデータ入力として提供する。詳しくはTealiumの[テンプレート変数ガイドを](https://docs.tealium.com/server-side/connectors/webhook-connectors/template-variables/)参照のこと。 |
+| ユーザー ID | このフィールドを使用して、TealiumユーザーIDフィールドとBrazeユーザーIDフィールドを対応させる。1つ以上のユーザーID属性をマップする。複数のIDが指定された場合、以下の優先順位に基づいて、空白でない最初の値が選ばれる：External ID、Braze ID、エイリアス名、エイリアスラベル。<br><br>\- プッシュトークンをインポートする場合、外部IDとBraze IDを指定すべきではない。<br>\- ユーザーエイリアスを指定する場合は、エイリアス名とエイリアスラベルを設定する必要がある。<br><br>詳細については、Braze [`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)をご確認ください。 |
+| ユーザー属性 | Brazeの既存のユーザープロファイルのフィールド名を使用して、Brazeダッシュボードのユーザープロファイル値を更新するか、独自のカスタム[ユーザー属性]({{site.baseurl}}/api/objects_filters/user_attributes_object/)データをユーザープロファイルに追加する。<br><br>\- デフォルトでは、ユーザーが存在しない場合、新しいユーザーが作成される。<br>\- \[**Update Existing Only**] を `true` に設定すると、既存のユーザーのみが更新され、新規ユーザーは作成されません。<br>\- Tealium 属性が空の場合、その属性は NULL に変換され、Braze ユーザープロファイルから削除されます。ユーザー属性を削除する目的で Braze に NULL 値を送信すべきでない場合は、エンリッチメントを使用してください。 |
+| ユーザー属性を変更する | このフィールドを使用して、特定のユーザー属性をインクリメントまたはデクリメントする。<br><br>\- 整数属性は、正の整数または負の整数でインクリメントできます。<br>\- 配列の属性は、既存の配列に値を追加したり削除したりすることで変更できる。 |
+| イベント | イベントは、タイムスタンプにおける、特定のユーザーによるカスタムイベントの単一発生を表す。このフィールドは、Braze [イベントオブジェクト]({{site.baseurl}}/api/objects_filters/event_object/)の属性と同様にイベント属性を追跡、マッピングする場合に使用します。<br><br>\- イベント属性 `Name` は、マッピングされたすべてのイベントで必要です。<br>\- イベント属性 `Time` は、明示的にマッピングされていない限り、自動的に現時点の時刻に設定されます。<br>\- デフォルトでは、イベントが存在しない場合、新しいイベントが作成される。`Update Existing Only` を`true` に設定すると、既存のイベントのみが更新され、新しいイベントは作成されない。<br>\- 配列タイプの属性をマップして、複数のイベントを追加する。配列型の属性は同じ長さでなければならない。<br>\- 単一値属性を使用できます。単一値属性は各イベントに適用できます。 |
+| イベントテンプレート | ボディデータで参照されるイベントテンプレートを提供する。Brazeにデータを送る前に、テンプレートを使ってデータを変換することができる。詳細については、Tealium の[テンプレートガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/)を参照してください。 |
+| イベントテンプレート変数 | イベントテンプレート変数をデータ入力として提供する。詳細については、Tealium の[テンプレート変数ガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/template-variables/)を参照してください。 |
+| 購入 | このフィールドは、Braze [購入オブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/)の属性と同様に購入属性を追跡、マッピングする場合に使用します。<br><br>\- 購入属性 `Product ID`、`Currency`、`Price` は、マッピングされたすべての購入に必要です。<br>\- 購入属性 `Time` は、明示的にマッピングされていない限り、自動的に現時点の時刻に設定されます。<br>\- デフォルトでは、新規購入が存在しない場合は作成されます。`Update Existing Only` を`true` に設定すると、既存の購入のみが更新され、新規購入は作成されません。<br>\- 複数の購入項目を追加するために、配列タイプの属性をマップする。配列型の属性は同じ長さでなければならない。<br>\- 単一値属性を使用することができ、各項目に適用される。|
+| テンプレート購入 | テンプレートは、Brazeに送信する前にデータを変換するために使用できる。<br>\- ネストされたオブジェクトのサポートが必要な場合は、購入テンプレートを定義する。<br>\- 購入テンプレートが定義されると、アクションの購入セクションで設定されたコンフィギュレーションは無視される。<br>詳細については、Tealium の[テンプレートガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/trimou-templating-engine/)を参照してください。|
+| 購入テンプレート変数 | 製品テンプレートの変数をデータ入力として提供する。詳細については、Tealium の[テンプレート変数ガイド](https://docs.tealium.com/server-side/connectors/webhook-connectors/template-variables/)を参照してください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ![]({% image_buster /assets/img/tealium/track_user_example2.png %}){: style="max-width:90%"}
 
 {% endtab %}
-{% tab ユーザーを削除する（非バッチ） %}
+{% tab Delete User (Non-Batch) %}
 
-Brazeダッシュボードからユーザーを削除する。
+このアクションでは、Braze ダッシュボードからユーザーを削除できます。
 
 | パラメーター | 説明 |
 | ---------- | ----------- |
-| ユーザー ID | このフィールドを使用して、TealiumユーザーIDフィールドとBrazeユーザーIDフィールドを対応させる。<br><br>\- 1つ以上のユーザーID属性をマップする。複数のIDが指定された場合、以下の優先順位に基づいて、空白でない最初の値が選ばれる：外部ID、ブレイズID、エイリアス名、エイリアスラベル。<br>\- ユーザーエイリアスを指定する場合、エイリアス名とエイリアスラベルの両方を設定する必要がある。<br><br>詳細については、Braze[`/users/delete` のエンド]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/)ポイントを参照のこと。 |
+| ユーザー ID | このフィールドを使用して、TealiumユーザーIDフィールドとBrazeユーザーIDフィールドを対応させる。<br><br>\- 1つ以上のユーザーID属性をマップする。複数のIDが指定された場合、以下の優先順位に基づいて、空白でない最初の値が選ばれる：External ID、Braze ID、エイリアス名、エイリアスラベル。<br>\- ユーザーエイリアスを指定する場合、エイリアス名とエイリアスラベルの両方を設定する必要があります。<br><br>詳しくは、Braze [`/users/delete` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/)を参照してください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ![]({% image_buster /assets/img/tealium/track_user_delete2.png %}){: style="max-width:90%"}
 
 {% endtab %}
-{% tab ユーザーサブスクリプショングループのステータスを更新する（非バッチ） %}
+{% tab Update User Subscription Group Status (Non-Batch) %}
 この操作により、Braze SMSまたはEメール購読グループからユーザーを追加または削除することができる。
 
 | パラメーター | 説明 |
 | ---------- | ----------- |
-| グループ・タイプ | このフィールドを使用して、SMS購読グループかEメール購読グループかを示す。 |
+| Group type | このフィールドを使用して、SMS購読グループかEメール購読グループかを示す。 |
 | 更新タイプ | このアクションを購読解除または購読イベントにマッピングする 
-| 属性 | \- サブスクリプション・グループID（必須）：前のフィールドでマップされたグループタイプに関連するサブスクリプショングループのID。<br>\- 外部ID：ユーザーの外部ID。<br><br>電子メール・グループ特有のものである：<br>\- EメールユーザーのEメールアドレス。<br>**外部IDが定義されていない場合は、Eメールが必要となる。**<br><br>SMSグループ固有である：<br>\- 電話だ：E.164 。例えば、+14155552671である。<br>**外部IDが定義されていない場合、電話が必要となる。** |
+| 属性 | \- Subscription group ID (required):前のフィールドでマップされたグループタイプに関連するサブスクリプショングループのID。<br>\- 外部ID：ユーザーの外部ID。<br><br>メールグループ固有:<br>\- Email:ユーザーのEメールアドレス。<br>**external ID が定義されていない場合はメールが必須です。**<br><br>SMS グループ固有:<br>\- Phone:E.164 形式の電話番号。 +14155552671 などです。<br>**external ID が定義されていない場合は電話番号が必須です。** |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ![]({% image_buster /assets/img/tealium/update_subscription.png %}){: style="max-width:90%"}
@@ -191,27 +191,27 @@ Brazeダッシュボードからユーザーを削除する。
 {% endtab %}
 {% endtabs %}
 
-**仕上げを**選択する。
+\[**Finish**] を選択します。
 
 #### まとめ
 
-作成したコネクタの概要を表示する。選択したオプションを変更したい場合は、「**Back**」を選択して編集するか、「**Finish」を**選択して完了する。
+作成したコネクタの概要を表示する。選択したオプションを変更する場合は、\[**Back**] を選択して編集するか、\[**Finish**] を選択して完了します。
 
-コネクタがTealiumホームページのコネクタ一覧に表示される。
+コネクターが Tealium ホームページのコネクターリストに表示されます。
 
-終了したら、必ずコネクタを保存するかパブリッシュすること。設定したアクションは、トリガーの接続が満たされたときに実行される。 
+終了したら、必ずコネクタを保存するかパブリッシュすること。設定したアクションは、トリガー接続が満たされたときに実行されます。 
 
-### ステップ4:Tealiumコネクタをテストする
+### ステップ4:Tealium コネクターをテストする
 
-コネクターが稼動したら、正常に動作しているかテストする必要がある。これをテストする最も簡単な方法は、Tealium**Trace Toolを**使うことである。Traceを使い始めるには、Tealium Toolsブラウザ拡張機能を追加していることを確認する。
+コネクターが稼動したら、正常に動作していることを確認するため、コネクターをテストする必要があります。最も簡単なテスト方法は、Tealium **Trace ツール**を使用する方法です。Traceを使い始めるには、Tealium Toolsブラウザ拡張機能を追加していることを確認する。
 
-1. 新しいトレースを開始するには、サイドバーの**サーバーサイドオプションから** **トレースを**選択する。**Startを**クリックし、トレースIDをキャプチャする。
-2. ブラウザ拡張機能を開き、AudienceStream TraceにトレースIDを入力する。
+1. 新しいトレースを開始するには、サイドバーの \[**Server-Side**] のオプションから \[**Trace**] を選択します。\[**Start**] をクリックし、トレース ID をキャプチャします。
+2. ブラウザー拡張機能を開き、AudienceStream Trace にトレース ID を入力します。
 3. リアルタイムのログを調べる。
 4. **Actions Triggered（トリガーされたアクション）」の**エントリーをクリックして展開し、検証したいアクションをチェックする。
 5. 検証したいアクションを探し、ログのステータスを見る。 
 
-TealiumのTraceツールの実装方法については、Tealiumの\[Trace documentation][21] ]を参照すること。
+Tealium の Trace ツールの詳しい実装手順については、Tealium の \[Trace ドキュメント][21]を参照してください。
 
 ## 統合デモ
 
@@ -219,21 +219,21 @@ TealiumのTraceツールの実装方法については、Tealiumの\[Trace docum
   <iframe width="560" height="315" src="https://drive.google.com/file/d/1m2JI4vdFt3fDePBdVvVcQWEjbC82ApGA/preview" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 </div>
 
-## データ・ポイント超過の可能性
+## データポイントの超過料金発生の可能性
 
 Tealiumを通じてBrazeを統合する際に、誤ってデータ超過に見舞われる可能性のある主な方法は3つある：
 
 #### 重複したデータを送信する - 属性のBraze差分のみを送信する
-Tealiumはユーザー属性のBrazeデルタを送信しない。例えば、ユーザーのファーストネーム、Eメール、携帯電話番号を追跡するEventStreamアクションがある場合、Tealiumはアクションがトリガーされるたびに、3つの属性すべてをBrazeに送信する。Tealiumは、何が変更されたか、更新されたかを探し、その情報のみを送信することはない。<br><br> 
-**解決策**だ：<br>バックエンドをチェックして属性が変更されたかどうかを評価し、変更された場合はTealiumの関連メソッドを呼び出してユーザープロファイルを更新することができる。**これは、Brazeを直接統合するユーザーが通常行うことである。**<br>**または**<br> バックエンドにユーザープロファイルの独自のバージョンを保存しておらず、属性が変更されたかどうかが分からない場合は、AudienceStreamを使用し、値が変更された場合にのみユーザー属性を送信する[エンリッチメントを作成](https://docs.tealium.com/server-side/attributes/manage-enrichments/add-enrichment/)することができる。 
+Tealiumはユーザー属性のBrazeデルタを送信しない。例えば、ユーザーのファーストネーム、Eメール、携帯電話番号を追跡するEventStreamアクションがある場合、Tealiumはアクションがトリガーされるたびに、3つの属性すべてをBrazeに送信する。Tealium は、変更された内容や更新された内容を探してその情報のみを送信することはありません。<br><br> 
+**解決策**:<br>バックエンドをチェックして属性が変更されたかどうかを評価し、変更された場合はTealiumの関連メソッドを呼び出してユーザープロファイルを更新することができる。**これは、Braze を直接統合するユーザーが通常行う作業です。**<br>**または**<br> 自分自身のユーザープロファイルをバックエンドに保存しておらず、属性が変更されたかどうかを判断できない場合は、AudienceStream を使用して[リッチメントを作成し](https://docs.tealium.com/server-side/attributes/manage-enrichments/add-enrichment/)、値が変更された場合にのみユーザー属性を送信するようにできます。 
 
 #### 無関係なデータを送信したり、不必要にデータを上書きしたりする。
-同じイベントフィードをターゲットとする複数のEventStreamがある場合、1つのアクションがトリガーされると、**そのコネクタで有効になっているすべてのアクションが**自動的に起動する**。**<br><br>
-**解決策**だ：<br>各アクションを追跡するために、個別のイベント仕様またはフィードを設定する。<br>**または**<br> Tealiumダッシュボードのトグルを使って、起動したくないアクション（またはコネクタ）を無効にする。
+同じイベントフィードをターゲットとする複数の EventStream がある場合、1つのアクションがトリガーされるたびに、**そのコネクターで有効になっているすべてのアクション**が自動的に起動します。**その結果、Braze でデータが上書きされる可能性があります。**<br><br>
+**解決策**:<br>各アクションを追跡するために、個別のイベント仕様またはフィードを設定する。<br>**または**<br> Tealium ダッシュボードのトグルを使用して、起動しないアクション (またはコネクター) を無効にします。
 
 #### Brazeの初期化が早すぎる
-Braze Web SDKタグを使用してTealiumと統合するユーザーは、MAUが劇的に増加する可能性がある。**Brazeがページ読み込み時に初期化される場合、Brazeは、ウェブユーザーが初めてウェブサイトに移動するたびに匿名プロファイルを作成する。**MAUカウントを下げるために、ユーザーが「サインイン」や「ビデオ視聴」など、何らかのアクションを完了した時だけ、ユーザーの行動をトラッキングしたいと考える人もいるだろう。<br><br>
-**解決策**だ：<br>[ロードルールを](https://docs.tealium.com/iq-tag-management/load-rules/about/)設定し、タグがサイト上でロードされるタイミングと場所を正確に決定する。
+Braze Web SDK タグを使用して Tealium と統合するユーザーの場合、MAU が大幅に増加する可能性があります。**Brazeがページ読み込み時に初期化される場合、Brazeは、ウェブユーザーが初めてウェブサイトに移動するたびに匿名プロファイルを作成する。**MAUカウントを下げるために、ユーザーが「サインイン」や「ビデオ視聴」など、何らかのアクションを完了した時だけ、ユーザーの行動をトラッキングしたいと考える人もいるだろう。<br><br>
+**解決策**:<br>タグがサイトで読み込まれるタイミングと位置を正確に決定する[読み込みルール](https://docs.tealium.com/iq-tag-management/load-rules/about/)を設定します。
 
 [1]: https://docs.tealium.com/server-side/attributes/about/
 [15]: {% image_buster /assets/img/tealium/create_configuration.png %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents.md
index 4eaa80fcae3..9c5f8787138 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents.md
@@ -12,37 +12,37 @@ search_tag: Partner
 
 # Tealium for Currents
 
-> [Tealiumは](https://www.tealium.com)、複数のソースから情報を収集し、マーケティング・スタックの他のさまざまな場所にルーティングする顧客データ・プラットフォームである。
+> [Tealium](https://www.tealium.com) は、複数のソースから情報を収集し、マーケティングスタックの他のさまざまな場所に情報をルーティングする顧客データプラットフォームです。
 
-BrazeとTealiumの統合により、2つのシステム間の情報の流れをシームレスにコントロールすることができる。Currentsを使えば、データをTealiumに接続し、成長スタック全体で実行可能にすることもできる。 
+BrazeとTealiumの統合により、2つのシステム間の情報の流れをシームレスにコントロールすることができる。Currents では、データを Tealium に接続し、グローススタック全体で実用的なデータにすることもできます。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| Tealium EventStream or Tealium AudienceStream | このパートナーシップを利用するには、[Tealiumアカウントが](https://my.tealiumiq.com/)必要である。 |
-| Currents | データをTealiumにエクスポートするには、アカウントに[Braze Currentsを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents)設定する必要がある。 |
-| ティーリウムURL | これらは、Tealiumのダッシュボードに移動し、インジェストURLをコピーすることで入手できる。|
+| Tealium EventStream or Tealium AudienceStream | このパートナーシップを活用するには、[Tealium アカウント](https://my.tealiumiq.com/)が必要です。 |
+| Currents | Tealium にデータを再度エクスポートするには、アカウントに [Braze Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/#access-currents) を設定する必要があります。 |
+| Tealium URL | これは、Tealium のダッシュボードに移動し、取り込み URL をコピーすることで取得できます。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:Tealium内にBraze用のデータソースを作成する。
 
-データソースの作成方法は、[Tealiumの](https://docs.tealium.com/server-side/data-sources/webhooks/braze-currents/)サイトに掲載されている。完了すると、TealiumはコピーするデータソースURLを提供するので、次のステップでそれを使用する。
+データソースを作成する手順は、[Tealium](https://docs.tealium.com/server-side/data-sources/webhooks/braze-currents/) サイトにあります。完了すると、Tealium からデータソース URL が提供されます。この URL をコピーして、次のステップで使用します。
 
-### ステップ2:電流を作る
+### ステップ2:Current を作成する
 
-Brazeで、**Current > + Create Current > Tealium Exportに**移動する。統合名、連絡先Eメール、Tealium URLを記入する。次に、利用可能なイベントのリストから追跡したいものを選択する。最後に、**Launch Currentを**クリックする。
+Braze で **\[Currents] > \[+ Currents を作成] > \[Tealium のエクスポート]** に移動します。統合名、連絡先メール、および Tealium URL を指定します。次に、利用可能なイベントのリストから追跡するイベントを選択します。最後に \[**Currents を起動**] をクリックします。
 
-Tealiumに送信されるすべてのイベントには、ユーザーの`external_user_id` 。現時点では、Brazeは、`external_user_id` を設定していないユーザーのイベントデータをTealiumに送信しない。
+Tealium に送信されるすべてのイベントには、ユーザーの `external_user_id` が含まれます。現時点では、Brazeは、`external_user_id` を設定していないユーザーのイベントデータをTealiumに送信しない。
 
 {% alert important %}
-TealiumのURLを常に最新の状態に保つことが重要だ。コネクタのURLが正しくない場合、Brazeはイベントを送信できない。この状態が**48時間**以上続くと、コネクタのイベントは削除され、データは永久に失われる。
+Tealium URL を最新の状態に保つことが重要です。コネクタのURLが正しくない場合、Brazeはイベントを送信できない。この状態が**48時間**以上続くと、コネクタのイベントは削除され、データは永久に失われる。
 {% endalert %}
 
 ## 統合の詳細
 
-Brazeは、[Currentsイベント用語集に]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents)記載されているすべてのデータ（[メッセージエンゲージメントイベントと]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) [顧客行動]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)イベントの両方のすべてのプロパティを含む）のTealiumへのエクスポートをサポートしている。
+Braze では、「[Currents イベント用語集]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents)」にリストされているすべてのデータ ([メッセージエンゲージメント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)イベントおよび[顧客行動]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)イベントのすべてのプロパティを含む) を Tealium にエクスポートできます。
 
-エクスポートされたデータのペイロード構造は、カスタムHTTPコネクターのペイロード構造と同じで、[カスタムHTTPコネクターのサンプルリポジトリで](https://github.com/Appboy/currents-examples/tree/master/sample-data/Custom%20HTTP/users/behaviors)見ることができる。
\ No newline at end of file
+エクスポートされたデータのペイロードの構造は、カスタム HTTP コネクターのペイロード構造と同じです。これは、[カスタム HTTP コネクターのサンプルリポジトリ](https://github.com/Appboy/currents-examples/tree/master/sample-data/Custom%20HTTP/users/behaviors)で確認できます。
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/toovio.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/toovio.md
index 02cda4eb0e3..69fad4c2869 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/toovio.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/toovio.md
@@ -1,43 +1,43 @@
 ---
-nav_title: トゥービオ
-article_title: トゥービオ
-description: "この参考記事では、Brazeとデータ・アズ・ア・サービス企業であるToovio社との提携について概説している。Toovio社は、実用的なデータを発見し、最も重要な要素を使用して、事前に定義された目標に基づき、段階的に成果を上げることを支援する。"
+nav_title: Toovio
+article_title: Toovio
+description: "このリファレンス記事では、Braze と Toovio のパートナーシップについて説明します。Toovio は、実用的なデータを検出し、最も重要な要素を使用して事前に定義されている目標に基づき段階的に成果を上げることができるようにする data-as-a-service 企業です。"
 alias: /partners/toovio/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# トゥービオ
+# Toovio
 
-> [Toovioは](https://toovio.com/)、人工知能を搭載したデータ・アズ・ア・サービス企業であり、実用的なデータを発見し、最も重要な要素を使用して、事前に定義された目標に基づき、段階的に成果を上げることができる。
+> [Toovio](https://toovio.com/) は、人工知能を採用している data-as-a-service企業であり、実用的なデータを検出し、最も重要な要素を使用して事前に定義されている目標に基づき段階的に成果を上げることを支援します。
 
-BrazeとToovioのパートナーシップは、ほぼリアルタイムのメッセージ・トリガー、パフォーマンスを向上させるツール、Toovioの高度なキャンペーン測定ツールへのアクセスを提供する。
+Braze と Toovio のパートナーシップにより、ほぼリアルタイムでのメッセージトリガー、増分パフォーマンスを促進するツール、Toovio の高度なキャンペーン測定ツールが利用可能になります。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| トゥービオアカウント | このパートナーシップを利用するには、トゥービオのアカウントが必要だ。 |
+| Toovio アカウント | このパートナーシップを活用するには、Toovio アカウントが必要です。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze Currents | Braze Currentsにより、Brazeクライアントは、Brazeプラットフォームの外部で処理するために、イベントまたは行動データをBrazeデータパートナー（AWS S3、Google Cloud Storage、またはMicrosoft Azure Blob Storage）にストリーミングすることができる。 |
+| Braze Currents | Braze Currents により、Brazeクライアントは、Brazeプラットフォーム外部での処理のためにイベントまたは行動データを Braze データパートナー (AWS S3、Google Cloud Storage、または Microsoft Azure Blob Storage) にストリーミングできます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-以下の統合により、Toovioは特定の顧客をターゲットとしたトリガーを生成し、ほぼリアルタイムでコミュニケーションをとることができる。Toovioが決定したトリガーは、Braze[`/users/track` エンドポイントを][3]経由してBrazeに送信される。
+以下の統合により、Toovio は特定の顧客をターゲットとしたトリガーを生成し、ほぼリアルタイムで通信できます。Toovio により決定されたトリガーは、Braze [`/users/track`エンドポイント][3]を経由して Braze に送信されます。
 
 ### ステップ1:データパートナーを定義する
 
 カレントのフィードのドロップ先をToovioと共有する必要がある。これにより、Toovioはユーザーのイベントおよび行動データにアクセスし、処理することができる。
 
-### ステップ2:トリガー・キャンペーンを設定する
+### ステップ2:トリガーキャンペーンを設定する
 
-Toovioがターゲットとする顧客イベントに基づいて、Braze[APIトリガーキャンペーンを][4]作成する。さらに、キャンペーンのトリガーとなるターゲットユーザーの属性と値を定義する必要がある。
+Toovio がターゲットとする顧客イベントに基づいて、Braze [API トリガーキャンペーン][4]を作成します。さらに、キャンペーンのトリガーとなるターゲットユーザーの属性と値を定義する必要がある。
 
 ### ステップ3:Tovioアカウントを設定する
 
-Toovioの[info@toovio.com](mailto:info@toovio.com?subject=New%20Customer%20Request)まで、件名を「新規顧客リクエスト」とし、アカウントを開設する。トゥービオは顧客と協力して、トリガーと基礎となるモデルを設定する。
+アカウントを設定するには、「New Customer Request」という件名のメールで Toovio ([info@toovio.com](mailto:info@toovio.com?subject=New%20Customer%20Request)) にご連絡ください。Toovio はクライアントと協力して、トリガーおよび基盤となるモデルを設定します。
 
 [1]: {{site.baseurl}}/user_guide/data_and_analytics/braze_currents/
 [2]: {{site.baseurl}}/api/api_key/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data.md
index 39746b5a400..390662daa40 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data.md
@@ -3,8 +3,8 @@ nav_title: トレジャーデータ
 noindex: true
 layout: dev_guide
 guide_top_header: "トレジャーデータ"
-guide_top_text: "トレジャーデータは、顧客データ、インサイト、エンゲージメントを完璧に調和させることで、適切な顧客体験を促進するエンタープライズ顧客データプラットフォーム（CDP）である。これらの実用的な指標を武器に、マーケティング、セールス、カスタマーサービスを含むCXチームは、効果的に支出を最適化し、カスタマージャーニー全体にわたってオムニチャネル・インタラクションをパーソナライズすることができる。"
-description: "このランディング・ページでは、統合ガイダンスやTreasure Data for Currentsなど、Treasure Dataに関するあらゆる情報を提供している。"
+guide_top_text: "トレジャーデータは、エンタープライズ顧客データプラットフォーム (CDP) です。顧客データ、インサイト、エンゲージメントを調和させて最適なカスタマーエクスペリエンスを実現しています。これらの実用的な指標を武器に、マーケティング、セールス、カスタマーサービスを含むCXチームは、効果的に支出を最適化し、カスタマージャーニー全体にわたってオムニチャネル・インタラクションをパーソナライズすることができる。"
+description: "このランディングページは、統合ガイダンスやトレジャーデータと Currents など、トレジャーデータに関するあらゆる情報のホームページです。"
 
 guide_featured_list:
 - name: トレジャーデータ
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data.md
index 85c8ff5a351..7edfaf29a12 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data.md
@@ -1,7 +1,7 @@
 ---
 nav_title: トレジャーデータ
 article_title: トレジャーデータ
-description: "この記事では、Brazeとトレジャーデータのパートナーシップについて説明します。トレジャーデータは、企業向けの顧客データプラットフォームで、ジョブの結果を直接Brazeに書き込むことができます。"
+description: "このリファレンス記事では、Braze とトレジャーデータのパートナーシップについて説明します。トレジャーデータはエンタープライズ顧客データプラットフォームであり、Braze に直接ジョブの結果を書き込むことができます。"
 alias: /partners/treasure_data/
 page_type: partner
 search_tag: Partner
@@ -10,31 +10,31 @@ search_tag: Partner
 
 # トレジャーデータ
 
-> \[トレジャーデータ][4]は、複数のソースから情報を収集し、マーケティングスタック内のさまざまな場所にルーティングする顧客データプラットフォーム（CDP）です。
+> \[トレジャーデータ][4]は、複数のソースから情報を収集し、マーケティングスタックの他のさまざまな場所に情報をルーティングする顧客データプラットフォーム (CDP) です。
 
-Brazeとトレジャーデータの統合により、トレジャーデータからBrazeに直接ジョブ結果を書き込むことができ、次のことが可能になります:
-* **外部IDをマップする**:CRMシステムからBrazeユーザーアカウントにIDをマッピングします。 
+Braze とトレジャーデータの統合により、トレジャーデータのジョブ結果を Braze に直接書き込むことができます。
+* **external ID をマッピングする**:CRMシステムからBrazeユーザーアカウントにIDをマッピングします。 
 * **オプトアウトを管理する**:エンドユーザーが参加しないことを選択して同意を更新する場合。
-* **あなたのイベント、購入、またはカスタムプロファイル属性のトラッキングをアップロード**。この情報は、キャンペーンのユーザーエクスペリエンスを向上させる正確な顧客セグメントの構築に役立ちます。
+* **イベント、購入、またはカスタムプロファイル属性のトラッキングをアップロードする**。この情報は、正確な顧客セグメントの作成に役立ちます。正確な顧客セグメントにより、キャンペーンのユーザーエクスペリエンスが向上します。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | --- | --- |
-| トレジャーデータアカウント | このパートナーシップを利用するには、[トレジャーデータアカウント](https://www.treasuredata.com/custom-demo/)が必要です。 |
+| トレジャーデータのアカウント | このパートナーシップを活用するには、[トレジャーデータのアカウント](https://www.treasuredata.com/custom-demo/)が必要です。 |
 | Braze REST API キー | `users.track`、`users.delete`、`users.alias.new`、`users.identify`の権限を持つBraze REST APIキー。<br><br>これはBrazeのダッシュボードで**設定** > **APIキー**から作成できます。 |
-| Braze REST エンドポイント  | あなたのRESTエンドポイントURL。エンドポイントは、インスタンスのBraze URL][1]に依存します。 |
+| Braze REST エンドポイント  | あなたのRESTエンドポイントURL。エンドポイントは\[インスタンスの Braze URL][1] に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 ## ユースケース
 
-トレジャーデータから統合された顧客プロファイルをBrazeに同期して、ターゲットセグメントを構築できます。トレジャーデータは、ファーストパーティCookieデータ、モバイルID、CRMのようなサードパーティシステムなど、多くのものをサポートしています。
+ターゲットセグメントを編成するために、統合された顧客プロファイルをトレジャーデータから Braze に同期できます。トレジャーデータは、ファーストパーティの Cookie データ、モバイル ID、CRM などのサードパーティシステムなどをサポートしています。
 
 ## 統合
 
 ### ステップ1:新しい接続を作成する
 
-トレジャーデータで、**カタログ**の**インテグレーションハブ**に移動し、**Braze**を検索して選択します。 
+トレジャーデータで、\[**Catalog**] の下にある \[**Integrations Hub**] に移動し、\[**Braze**] を検索して選択します。 
 
 **新しい認証**プロンプトが表示されたら、接続に名前を付け、Braze REST APIキーとRESTエンドポイントを提供します。完了したら**完了**を選択します。
 
@@ -45,7 +45,7 @@ Brazeとトレジャーデータの統合により、トレジャーデータか
 トレジャーデータで、**クエリ**の下にある**データワークベンチ**に移動し、データをエクスポートしたいクエリを選択します。このクエリを実行して結果セットを検証します。
 
 {% alert note %}
-HIVEを使用してクエリを作成するユーザーの場合、HIVEではアンダースコアで始まる列またはテーブルをバッククォートで囲む必要があります。例えば、`_merge_objects`。
+HIVEを使用してクエリを作成するユーザーの場合、HIVEではアンダースコアで始まる列またはテーブルをバッククォートで囲む必要があります。たとえば `_merge_objects` です。
 {% endalert %}
 
 次に、**結果をエクスポート**を選択し、既存の統合認証を選択します。
@@ -54,7 +54,7 @@ HIVEを使用してクエリを作成するユーザーの場合、HIVEではア
 
 次の[カスタマイズセクション](#customization)に概説されているように、追加のエクスポート結果パラメータを定義します。エクスポート統合コンテンツで、統合パラメータを確認してください。
 
-![「結果のエクスポート」ページ。このページには、「モード」、「トラックレコードタイプ」、および「事前フォーマットされたフィールド」のフィールドがあります。この例では、「ユーザー-トラック」と「カスタムイベント」がそれぞれこれらのフィールドに設定されています。][3]{: style="max-width:80%;"}
+![「Export Results」ページ。このページには、「Mode」、「Traffic Record Type」、および「Pre-formatted Fields」フィールドがある。この例では、それぞれのフィールドに「User-Track」と「Custome Event」が設定されている。][3]{: style="max-width:80%;"}
 
 最後に、**完了**を選択し、クエリを実行して、データがBrazeに移動したことを確認します。
 
@@ -64,10 +64,10 @@ HIVEを使用してクエリを作成するユーザーの場合、HIVEではア
 
 | パラメータ                 | 値 | 説明 |
 |---------------------------|---|---|
-| `mode`                    | ユーザー - New Alias<br>ユーザー - 識別<br>ユーザー - トラック<br>ユーザー - 削除 | コネクターモード |
+| `mode`                    | User - New Alias<br>ユーザー - 識別<br>ユーザー - トラック<br>ユーザー - 削除 | コネクターモード |
 | `pre_formatted_fields`    | String | 配列またはJSON列に使用してフォーマットを保持します。 |
-| `track_record_type`       | カスタムイベント<br>購入<br>ユーザープロファイル属性| **ユーザー - トラック**モードのレコードタイプ |
-| `skip_on_invalid_records` | ブール値 | 有効にした場合、続行してJSON列の無効なレコードを無視します。<br> さもなければ、仕事は止まります。 |
+| `track_record_type`       | カスタムイベント<br>購入<br>ユーザープロファイル属性| **User - Track** モードのレコードタイプ |
+| `skip_on_invalid_records` | ブール値 | 有効にした場合、続行してJSON列の無効なレコードを無視します。<br> それ以外の場合は、ジョブが停止します。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 {% alert note %}
@@ -76,7 +76,7 @@ HIVEを使用してクエリを作成するユーザーの場合、HIVEではア
 
 ## Webhook
 
-トレジャーデータのユーザーは、パブリックREST APIを通じてデータを取り込むことができます。トレジャーデータを使用して、データにカスタムwebhookを作成できます。詳細については、[トレジャーデータ][6]をご覧ください。
+トレジャーデータのユーザーは、パブリック REST API を介してデータを取り込むことができます。トレジャーデータを使用して、データにカスタム Webhook を作成できます。詳細については、[トレジャーデータ][6]を参照してください。
 
 [6]: https://docs.treasuredata.com/display/public/PD/Postback+API
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data_for_currents.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data_for_currents.md
index ee0a142a690..67b5dcd3b07 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data_for_currents.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/treasure_data_for_currents.md
@@ -13,9 +13,9 @@ search_tag: Partner
 # Treasure Data for Currents
 
 
-> [Treasure Dataは][1]顧客データプラットフォーム（CDP）であり、複数のソースから情報を収集し、マーケティングスタックの様々な場所にルーティングする。
+> [トレジャーデータ][1]は、複数のソースから情報を収集し、マーケティングスタックの他のさまざまな場所に情報をルーティングする顧客データプラットフォーム (CDP) です。
 
-BrazeとTreasure Dataの統合により、2つのシステム間の情報の流れをシームレスにコントロールすることができる。Currentsを使えば、データをTreasure Dataに接続し、成長スタック全体で実行可能なものにすることもできる。
+Braze とトレジャーデータの統合により、2 つのシステム間の情報の流れをシームレスに制御できます。Currents では、データをトレジャーデータに接続し、グローススタック全体で実用的なデータにすることもできます。
 
 
 ## 前提条件
@@ -23,40 +23,40 @@ BrazeとTreasure Dataの統合により、2つのシステム間の情報の流
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| Treasure Data | このパートナーシップを利用するには、[トレジャーデータのアカウントが][0]必要である。 |
-| Currents | データをTreasure Dataにエクスポートするには、アカウントに[Braze Currentsを][2]設定する必要がある。 |
-| トレジャーデータURL | これは、Treasure Dataのダッシュボードに移動し、取り込みURLをコピーすることで取得できる。|
+| Treasure Data | このパートナーシップを活用するには、[トレジャーデータのアカウント][0]が必要です。 |
+| Currents | トレジャーデータにデータを再度エクスポートするには、アカウントに [Braze Currents][2] を設定する必要があります。 |
+| トレジャーデータ URL | これは、トレジャーデータのダッシュボードに移動し、取り込み URL をコピーすることで取得できます。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 
 ## 統合
 
 
-Treasure Dataとの接続には、Postback APIを使用することを推奨する。この方法はデフォルトのコネクターを必要とせず、プッシュ方式でデータを受け取ることができる。1つのデータ・バッチで送信されるすべてのイベントは、JSON配列の1行の1フィールド内にあり、必要なデータを取得するために解析する必要がある。
+トレジャーデータとの接続には、Postback API を使用することをお勧めします。この方法はデフォルトのコネクターを必要とせず、プッシュ方式でデータを受け取ることができる。1つのデータバッチで送信されるすべてのイベントは、JSON 配列の1つの行の1つのフィールド内にあり、必要なデータを取得するために解析する必要があります。
 
 
 {% alert important %}
-現在のところ、イベントコレクターによるTreasure Dataへの取り込みはリアルタイムではなく、5分ほどかかることがある。
+現時点では、イベントコレクターを介したトレジャーデータへの取り込みはリアルタイムでは行われず、最大5分かかることがあります。
 {% endalert %}
 
 
-### ステップ1:BrazeでTreasure Data Postback APIをセットアップする
+### ステップ1:Braze を使用してトレジャーデータの Postback API を設定する
 
 
-Postback APIの作成方法は、[Treasure Dataの][3]ウェブサイトに掲載されている。Brazeは、event-collectorを介した取り込みを除き、更新されたイベントをリアルタイムでTreasure Dataに直接送信する。完了すると、Treasure Dataは次のステップで使用するためにコピーするデータソースURLを提供する。
+Postback API の作成方法については、[トレジャーデータ][3]の Web サイトを参照してください。Braze は、イベントコレクターによる取り込みを除き、更新されたイベントをリアルタイムでトレジャーデータに直接送信します。完了すると、トレジャーデータからデータソース URL が提供されます。この URL をコピーして、次のステップで使用します。
 
 
-### ステップ2:電流を作る
+### ステップ2:Current を作成する
 
 
-Brazeで、**Current**>**\+ Create Current**>**Treasure Data Exportに**移動する。統合名、連絡先Eメール、Treasure Data URLを入力する。次に、利用可能なイベントのリストから追跡したいものを選択し、**「Launch Current**」をクリックする。
+Braze で \[**Currents**] > \[**\+ Current を作成**] > \[**トレジャーデータのエクスポート**] に移動します。統合名、連絡先メール、およびトレジャーデータ URL を指定します。次に、利用可能なイベントのリストから追跡したいものを選択し、**「Launch Current**」をクリックする。
 
 
-Treasure Data に送信されるすべてのイベントには、ユーザーの`external_user_id` が含まれる。現時点では、Brazeは、`external_user_id` を設定していないユーザーのイベントデータをTreasure Dataに送信しない。
+トレジャーデータに送信されるすべてのイベントには、ユーザーの `external_user_id` が含まれます。この時点では Braze は、`external_user_id` が設定されていないユーザーのイベントデータをトレジャーデータに送信しません。
 
 
 {% alert important %}
-トレジャーデータのURLを常に最新の状態に保つ。コネクタのURLが正しくない場合、Brazeはイベントを送信できない。この状態が48時間以上続くと、コネクタのイベントは削除され、データは永久に失われる。
+トレジャーデータ URL を最新の状態に保ちます。コネクタのURLが正しくない場合、Brazeはイベントを送信できない。この状態が48時間以上続くと、コネクタのイベントは削除され、データは永久に失われる。
 {% endalert %}
 
 
@@ -93,9 +93,9 @@ Treasure Data に送信されるすべてのイベントには、ユーザーの
 ## 統合の詳細
 
 
-Brazeは、[Currentsイベント用語集に]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents)記載されているすべてのデータ（[メッセージエンゲージメントイベントと]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) [顧客行動]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)イベントの両方のすべてのプロパティを含む）のTreasure Dataへのエクスポートをサポートしている。
+Braze では、「[Currents イベント用語集]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents)」にリストされているすべてのデータ ([メッセージエンゲージメント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)イベントおよび[顧客行動]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)イベントのすべてのプロパティを含む) をトレジャーデータにエクスポートできます。
 
-エクスポートされたデータのペイロード構造は、カスタムHTTPコネクターのペイロード構造と同じで、[カスタムHTTPコネクターのサンプルリポジトリで](https://github.com/Appboy/currents-examples/tree/master/sample-data/Custom%20HTTP/users/behaviors)見ることができる。
+エクスポートされたデータのペイロードの構造は、カスタム HTTP コネクターのペイロード構造と同じです。これは、[カスタム HTTP コネクターのサンプルリポジトリ](https://github.com/Appboy/currents-examples/tree/master/sample-data/Custom%20HTTP/users/behaviors)で確認できます。
 
 
 [0]: https://console.treasuredata.com/users/sign_in
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap.md
index ddc3b71aae1..dcf46bded29 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap.md
@@ -5,15 +5,15 @@ page_type: partner
 search_tag: Partner
 layout: dev_guide
 guide_top_header: "Zeotap"
-guide_top_text: "Zeotapは次世代の顧客データ・プラットフォームだ。ブランドは、顧客のプライバシーとコンプライアンスを前面に押し出しながら、クッキーのない未来において顧客データを統合し、強化し、活性化することができる。"
+guide_top_text: "Zeotap は次世代の顧客データプラットフォームです。Cookie のない未来において、ブランドは顧客のプライバシーとコンプライアンスを最重視しながら、顧客データを統合し、強化し、アクティブ化することができます。"
 
-description: "このランディングページには、Zeotapの統合方法やZeotap Symphonyの使用方法など、Zeotapのすべてが掲載されている。"
+description: "このランディングページは、Zeotap を統合する方法と Zeotap Symphony を使用する方法など、Zeotap に関するあらゆる情報のホームページです。"
 
 guide_featured_list:
 - name: Zeotap
   link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/zeotap/zeotap/
   image: /assets/img/braze_icons/user-circle.svg
-- name: ゼオタップ交響曲
+- name: Zeotap Symphony
   link: /docs/partners/data_and_infrastructure_agility/customer_data_platform/zeotap/symphony/
   image: /assets/img/braze_icons/building-01.svg
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/symphony.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/symphony.md
index bc3e4cfbf5c..9622f2865ae 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/symphony.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/symphony.md
@@ -1,29 +1,29 @@
 ---
-nav_title: ゼオタップ交響曲
-description: "この参考記事では、Brazeと、アイデンティティの解決、洞察、エンリッチメントを提供する次世代顧客データプラットフォームZeotapのパートナーシップについて概説している。"
+nav_title: Zeotap Symphony
+description: "このリファレンス記事では、Braze と Zeotap のパートナーシップについて説明します。Zeotap は、アイデンティティ解決、インサイト、データ強化を提供する次世代顧客データプラットフォームです。"
 page_type: partner
 search_tag: Partner
 page_order: 2 
 ---
 
-# ゾイタップ・シンフォニー
+# Zoetap Symphony
 
 BrazeとZoetap Symphonyの統合により、リアルタイムのオーケストレーションを作成し、電子メールやプッシュ通知キャンペーンを実行することができる。
 
-- Zeotapで姓と名を送信し、それに基づいてユーザーがBrazeでパーソナライズされたメールを送信できる。
+- ユーザーが Braze からパーソナライズされたメールを送信できるかどうかに基づいて、Zeotap から姓と名を送信します。
 - Zeotapを通じてカスタムイベントまたは購入イベントをリアルタイムで送信し、ユーザーはそれに基づいてBraze内でキャンペーントリガーを作成し、顧客をターゲットにすることができる。
 
 {% alert note %}
-Eメールマーケティングキャンペーンを作成するには、生のEメールをZeotapカタログの`Email Raw` 。
+メールマーケティングキャンペーンを作成するには、生のメールを Zeotap Catalogue の `Email Raw` にマッピングして、これらのメールを登録します。
 {% endalert %}
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| クライアント名 | Brazeアカウントのクライアント名。Brazeコンソールに移動して見つけることができる。 |
+| クライアント名 | これは、Braze アカウントのクライアント名です。これを確認するには、Braze コンソールに移動します。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| インスタンス | あなたのBrazeインスタンスは、あなたのBrazeオンボーディングマネージャーから取得するか、[API概要ページで]({{site.baseurl}}/api/basics/#endpoints)見つけることができる。 |
+| インスタンス | Braze インスタンスは Braze オンボーディングマネージャーから入手できます。また、[API 概要ページ]({{site.baseurl}}/api/basics/#endpoints)でも確認できます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 ## 統合
@@ -31,20 +31,20 @@ Eメールマーケティングキャンペーンを作成するには、生のE
 このセクションでは、Brazeと統合できる2つの方法について説明する：
 
 ### 方法1
-この方法では、以下の作業を行う必要がある：
+この方法では、次の作業を行う必要があります。
 1. ウェブサイトやアプリにBraze SDKを統合する。
-2. BrazeをSymphonyを通じてZeotapと統合する。
+2. Symphony を介して Braze を Zeotap と統合します。
 
-- `User traits` は、**Data To Send**タブの各Brazeフィールドにマッピングされなければならない。`Event` と`Purchase` のアトリビュートを対応させると、Braze内でイベントが重複することになる。
-- Braze SDKのセットアップ中に設定した`User ID` に`External ID` をマップする。
+- `User traits` は、[**Data To Send**] タブの各 Braze フィールドにマッピングされている必要があります。`Event` と`Purchase` のアトリビュートを対応させると、Braze内でイベントが重複することになる。
+- Braze SDK の設定時に設定した`User ID` に `External ID` をマッピングします。
 
 統合が正常に設定されると、Symphonyを通じてBrazeに送信されるカスタム属性に基づいて、Eメールやプッシュ通知キャンペーンを作成できる。
 
 ### 方法2
-この方法では、シンフォニーを通してBrazeとZeotapを統合することができる。
+この方法では、Symphony を介して Braze とZeotap を統合できます。
 
 - この方法では、アプリ内メッセージ、ニュースフィード、コンテンツカード、プッシュ通知などのBraze UI機能はサポートされない。
-- ZeotapはZeotap Catalogueで利用可能な`hashed email` を`External ID` にマッピングすることを推奨する。
+- Zeotap では、Zeotap Catalogue で利用可能な `hashed email` を `External ID` にマッピングすることを推奨しています。
 
 統合が正常に設定されると、Symphonyを通じてBrazeに送信されたカスタム属性に基づいてのみ、メールキャンペーンを作成できるようになる。
 
@@ -53,62 +53,62 @@ Eメールマーケティングキャンペーンを作成するには、生のE
 データはZeotapから[ユーザートラック](https://www.braze.com/docs/api/endpoints/user_data/post_user_track/)APIを使ってBrazeに流れる。データの流れをまとめると以下のようになる：
 
 1. Zeotapはユーザープロファイル属性、カスタム属性、カスタムイベント、購入フィールドを送信する。
-2. **送信するデータ**」タブで、関連するすべてのZeotapカタログフィールドをBrazeフィールドにマッピングする。
+2. 関連するすべての Zeotap Catalogue フィールドを、\[**Data To Send**] タブの Braze フィールドにマッピングします。
 3. そのデータはBrazeにアップロードされる。
 
 各属性の詳細は、「[送信するデータ](#data-to-send-tab)」セクションで確認できる。
 
 ## 目的地の設定
 
-Symphonyでユーザーにフィルタを適用したり条件を追加した後、Brazeの**Send to Destinationsで**それらを有効にすることができる。新しいウィンドウが開き、目的地を設定できる。**利用可能な目的地の**リストから既存の目的地を使用するか、新しい目的地を作成することができる。
+Symphony でユーザーにフィルターを適用した後、またはユーザーの条件を追加した後は、\[**Send to Destinations**] で、Braze のユーザーをアクティブ化できます。新しいウィンドウが開き、宛先を設定できます。\[**Available Destination**] リストにある既存の宛先を使用するか、新規の宛先を作成できます。
 
-#### 新しい目的地を追加する
-新しい宛先を追加するには、以下の手順を実行する：
-1. **Add New Destinationを**クリックする。
-2. **ブレーズを**検索する。
-3. **クライアント名**、**APIキー**、**インスタンスを**追加し、保存先を指定する。
+#### 新しい宛先を追加する
+新しい宛先を追加するには、次の手順を実行します。
+1. \[**Add New Destination**] をクリックします。
+2. **Braze** を検索します。
+3. \[**Client Name**]、\[**API Key**]、および \[**Instance**] を追加し、宛先を保存します。
 
 デスティネーションが作成され、「**Available Destinations（利用可能なデスティネーション）**」で利用できるようになる。
 
 #### ワークフローレベルの入力を追加する
-デスティネーションを作成したら、次にワークフローレベルのインプットを追加しなければならない。
+宛先を作成したら、次に以下に示すようにワークフローレベルの入力を追加する必要があります。
 1. 検索機能を使って、利用可能な目的地のリストから目的地を選ぶ。
 2. **Client Name（クライアント名）**、**API Key（APIキー）**、**Instance（インスタンス**）フィールドは、宛先作成時に入力した値に基づいて自動的に入力される。
-3. このワークフローノードに作成したい**オーディエンス名を**入力する。これは**カスタム属性として**Brazeに送られる。
-4. **送信するデータ**」タブで、カタログから宛先へのマッピングを完了する。マッピングの詳細については、下記を参照されたい。
+3. このワークフローノードに対して作成する**オーディエンス名**を入力します。これは**カスタム属性**として Braze に送信されます。
+4. \[**Data To Send**] タグでカタログから宛先へのマッピングを完了します。マッピングの詳細については、下記を参照されたい。
 
-#### 送信データタブ
-**Data To Send**タブで、ZeotapカタログフィールドをBrazeに送信可能なBrazeフィールドにマッピングする。マッピングは以下のいずれかの方法で行うことができる：
-- **静的マッピング**\- ZeotapがEメール、電話、姓、名などの関連するBrazeフィールドに自動的にマッピングするフィールドがある。<br>
-- **ドロップダウン選択**\- Zeotapで取り込まれた関連フィールドを、ドロップダウンメニューで提供されるBrazeフィールドにマッピングする。<br>![言語、都市、誕生日など、Zeotapに設定されたさまざまなユーザー特性。][3]{: style="max-width:70%;"}<br>
+#### \[Data to send] タブ
+\[**Data To Send**] タブでは、Zeotap Catalogue のフィールドを、Braze に送信できる Braze のフィールドにマッピングできます。マッピングは以下のいずれかの方法で行うことができる：
+- **静的マッピング** \- Zeotap により関連する Braze フィールドに自動的にマッピングされるフィールドがあります (メール、電話番号、名前、性など)。<br>
+- **ドロップダウン選択** \- Zeotap に取り込まれた関連フィールドを、ドロップダウンメニューに示されている Braze フィールドにマッピングします。<br>![言語、都市、誕生日など、Zeotapに設定されたさまざまなユーザー特性。][3]{: style="max-width:70%;"}<br>
 - **カスタムデータ入力**-関連するZeotapフィールドにマッピングされたカスタムデータを追加し、Brazeに送信する。<br>![Zeotapのユーザー特性として「loyalty_points」を選択する。][4]{: style="max-width:70%;"}
 
 ## サポートされている属性
-このセクションでは、すべてのブレイズフィールドの詳細を見ることができる。
+このセクションでは、すべての Braze フィールドの詳細を確認できます。
 
-| ブレイズ・フィールド | マッピング・タイプ | 説明 |
+| Braze フィールド | マッピングタイプ | 説明 |
 | --- | --- | --- |
-| external ID | ドロップダウン選択 | これは、デバイスやプラットフォームを超えてユーザーを追跡するためにBrazeが定義した永続的な`User ID` 。`User ID` を`External ID` にマップすることを推奨する。そうしないと、Zeotapはユーザーエイリアスとして電子メールを送信する可能性がある。<br><br>ゼオタップは、ゼオタップ・カタログで利用可能な`hashed email` を`External ID` にマッピングすることを推奨する。|
-| メール | 静的マッピング | これはゼオタップ・カタログの`Email Raw` 。 |
-| 電話 | 静的マッピング | これはゼオタップ・カタログの`Mobile Raw` 。<br><br>\- Brazeは`E.164` フォーマットの電話番号を受け付ける。ゼオタップは変身を行わない。従って、所定のフォーマットで電話番号を入力する必要がある。詳しくは、[ユーザーの電話番号を](https://www.braze.com/docs/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/)参照のこと。 |
-| 名 | 静的マッピング | これはゼオタップ・カタログの`First Name` 。 |
-| 姓 | 静的マッピング | これはゼオタップ・カタログの`Last Name` 。 |
-| 性別 | 静的マッピング | これはゼオタップ・カタログの`Gender` 。 |
-| カスタムイベント名 | 静的マッピング | これはゼオタップ・カタログの`Event Name` 。<br><br>Brazeでカスタムイベントをキャプチャするには、カスタムイベント名とカスタムイベントタイムスタンプの両方をマッピングする必要がある。どちらかがマッピングされていないと、カスタムイベントは処理できない。詳しくは[イベント・オブジェクトを](https://www.braze.com/docs/api/objects_filters/event_object#what-is-the-event-object)参照のこと。 |
-| カスタム・イベントのタイムスタンプ | 静的マッピング | これはゼオタップ・カタログの`Event Timestamp` 。<br><br>Brazeでカスタムイベントをキャプチャするには、カスタムイベント名とカスタムイベントタイムスタンプの両方をマッピングする必要がある。どちらかがマッピングされていないと、カスタムイベントは処理できない。詳しくは[イベント・オブジェクトを](https://www.braze.com/docs/api/objects_filters/event_object#what-is-the-event-object)参照のこと。 |
-| メール購読 | ドロップダウン選択 | `Email Marketing Preference` 、そのフィールドにマッピングする。<br><br>ゼオタップは以下の3つの値を送信する：<br>-`opted_in` - ユーザーが明示的にEメールマーケティング希望に登録したことを示す。<br>-`unsubscribed` - ユーザーが明示的にEメールメッセージをオプトアウトしたことを示す。<br>-`subscribed` - ユーザーがオプトインもオプトアウトもしていないことを示す。 |
-| プッシュサブスクライブ | ドロップダウン選択 | `Push Marketing Preference` 、そのフィールドにマッピングする。<br><br>ゼオタップは以下の3つの値を送信する：<br>-`opted_in` - ユーザーが明示的にプッシュ・マーケティング選好に登録したことを示す。<br>-`unsubscribed` - ユーザーが明示的にプッシュメッセージをオプトアウトしたことを示す。<br>-`subscribed` - ユーザーがオプトインもオプトアウトもしていないことを示す。 |
-| メール開封トラッキングを有効にする | ドロップダウン選択 | 該当する`Marketing Preference` フィールドをマッピングする。<br><br>trueに設定すると、今後このユーザーに送信されるすべてのEメールに開封トラッキングピクセルを追加できるようになる。 |
+| external ID | ドロップダウン選択 | これは、デバイスやプラットフォームを超えてユーザーを追跡するためにBrazeが定義した永続的な`User ID` 。`User ID` を`External ID` にマップすることを推奨する。そうしないと、Zeotapはユーザーエイリアスとして電子メールを送信する可能性がある。<br><br>Zeotap では、Zeotap Catalogue で利用可能な `hashed email` を `External ID` にマッピングすることを推奨しています。|
+| メール | 静的マッピング | これは、Zeotap Catalogueの`Email Raw` にマッピングされます。 |
+| 電話 | 静的マッピング | これは、Zeotap Catalogueの`Mobile Raw` にマッピングされます。<br><br>\- Brazeは`E.164` フォーマットの電話番号を受け付ける。Zeotap は変換を実行しません。このため、電話番号を所定の形式で取り込む必要があります。詳細については、「[ユーザーの電話番号](https://www.braze.com/docs/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/)」を参照してください。 |
+| 名 | 静的マッピング | これは、Zeotap Catalogueの`First Name` にマッピングされます。 |
+| 姓 | 静的マッピング | これは、Zeotap Catalogueの`Last Name` にマッピングされます。 |
+| 性別 | 静的マッピング | これは、Zeotap Catalogueの`Gender` にマッピングされます。 |
+| カスタムイベント名 | 静的マッピング | これは、Zeotap Catalogueの`Event Name` にマッピングされます。<br><br>Braze でカスタムイベントをキャプチャするため、カスタムイベント名とカスタムイベントタイムスタンプをマッピングする必要があります。どちらかがマッピングされていないと、カスタムイベントは処理できない。詳細については、「[イベントオブジェクト](https://www.braze.com/docs/api/objects_filters/event_object#what-is-the-event-object)」を参照してください。 |
+| カスタムイベントタイムスタンプ | 静的マッピング | これは、Zeotap Catalogueの`Event Timestamp` にマッピングされます。<br><br>Braze でカスタムイベントをキャプチャするため、カスタムイベント名とカスタムイベントタイムスタンプをマッピングする必要があります。どちらかがマッピングされていないと、カスタムイベントは処理できない。詳細については、「[イベントオブジェクト](https://www.braze.com/docs/api/objects_filters/event_object#what-is-the-event-object)」を参照してください。 |
+| メール購読 | ドロップダウン選択 | `Email Marketing Preference` フィールドを登録してそれにマッピングします。<br><br>Zeotap は次の3つの値を送信します。<br>• `opted_in` - ユーザーがメールマーケティング設定を明示的に登録していることを示します。<br>• `unsubscribed` - ユーザーがメールメッセージを明示的にオプトアウトしたことを示します。<br>• `subscribed` - ユーザーがオプトインもオプトアウトもしていないことを示します。 |
+| プッシュサブスクライブ | ドロップダウン選択 | `Push Marketing Preference` フィールドを登録してそれにマッピングします。<br><br>Zeotap は次の3つの値を送信します。<br>• `opted_in` - ユーザーがプッシュマーケティング設定を明示的に登録していることを示します。<br>• `unsubscribed` - ユーザーがプッシュメッセージを明示的にオプトアウトしたことを示します。<br>• `subscribed` - ユーザーがオプトインもオプトアウトもしていないことを示します。 |
+| メール開封追跡が有効 | ドロップダウン選択 | 該当する`Marketing Preference` フィールドをマッピングする。<br><br>trueに設定すると、今後このユーザーに送信されるすべてのEメールに開封トラッキングピクセルを追加できるようになる。 |
 | 電子メールのクリック追跡を有効にする | ドロップダウン選択 | 該当する`Marketing Preference` フィールドをマッピングする。<br><br>trueに設定すると、このユーザーに今後送信されるすべてのメール内のすべてのリンクのクリックトラッキングを有効にする。 |
-| プロダクトID | ドロップダウン選択 | \- 購入アクションの識別子`(Product Name/Product Category)`.詳しくは、[購入先を](https://www.braze.com/docs/api/objects_filters/purchase_object/)参照のこと。<br>\- 該当する属性をZeotapカタログに搭載し、マッピングする。<br><br>`Product ID`Brazeで購入イベントをキャプチャするためには、`Currency` 、`Price` を必ずマッピングする必要がある。この3つのどれかが欠けると、購入イベントは成立しない。詳しくは、[購入対象を](https://www.braze.com/docs/api/objects_filters/purchase_object/#purchase-object)参照のこと。 |
-| 通貨 | ドロップダウン選択 | \- 購入アクションの通貨属性。<br>\- 対応フォーマットは`ISO 4217 Alphabetic Currency Code` である。<br>\- 正しくフォーマットされた通貨データをゼオタップ・カタログに搭載し、マップを作成する。<br><br>`Product ID`Brazeで購入イベントをキャプチャするためには、`Currency` 、`Price` を必ずマッピングする必要がある。この3つのどれかが欠けると、購入イベントは成立しない。 |
-| 価格 | ドロップダウン選択 | \- 購入アクションの価格属性。<br>\- 該当する属性をZeotapカタログに搭載し、マッピングする。<br><br>`Product ID`Brazeで購入イベントをキャプチャするためには、`Currency` 、`Price` を必ずマッピングする必要がある。この3つのどれかが欠けると、購入イベントは成立しない。 |
-| 数量 | ドロップダウン選択 | \- 購入アクションの数量属性。<br>\- 該当する属性をZeotapカタログに搭載し、マッピングする。 |
-| 国 | ドロップダウン選択 | オンボーディングする`Country` カタログ・フィールドにマッピングする。 |
-| 市区町村 | ドロップダウン選択 | オンボーディングする`City` カタログ・フィールドにマッピングする。 |
-| 言語 | ドロップダウン選択 | \- 使用可能なフォーマットは、`ISO-639-1` 標準（例：en）である。<br>\- 正しくフォーマットされた言語を搭載し、それにマップする。 |
-| 生年月日 | ドロップダウン選択 | `Date of Birth` フィールドにマッピングする。 |
-| カスタム属性 | カスタム・データ入力 | 任意のユーザー属性をカスタムデータ入力にマップし、それをBrazeに送信する。 |
+| プロダクトID | ドロップダウン選択 | • 購入アクションの ID `(Product Name/Product Category)`。詳細については、「[購入オブジェクト](https://www.braze.com/docs/api/objects_filters/purchase_object/)」を参照してください。<br>• 関連する属性を Zeotap Catalogue に登録してそれにマッピングします。<br><br>Braze で購入イベントをキャプチャするには、`Product ID`、`Currency`、および`Price` を必ずマッピングする必要があります。この3つのいずれかが欠落している場合、購入イベントは成立しません。詳細については、「[購入オブジェクト](https://www.braze.com/docs/api/objects_filters/purchase_object/#purchase-object)」を参照してください。 |
+| 通貨 | ドロップダウン選択 | \- 購入アクションの通貨属性。<br>\- サポートされているフォーマットは`ISO 4217 Alphabetic Currency Code` です。<br>\- 正しい形式の通貨データを Zeotap Catalogue に登録してそれにマッピングします。<br><br>Braze で購入イベントをキャプチャするには、`Product ID`、`Currency`、および`Price` を必ずマッピングする必要があります。この3つのいずれかが欠落している場合、購入イベントは成立しません。 |
+| 価格 | ドロップダウン選択 | \- 購入アクションの価格属性。<br>• 関連する属性を Zeotap Catalogue に登録してそれにマッピングします。<br><br>Braze で購入イベントをキャプチャするには、`Product ID`、`Currency`、および`Price` を必ずマッピングする必要があります。この3つのいずれかが欠落している場合、購入イベントは成立しません。 |
+| 数量 | ドロップダウン選択 | \- 購入アクションの数量属性。<br>• 関連する属性を Zeotap Catalogue に登録してそれにマッピングします。 |
+| 国 | ドロップダウン選択 | 登録する`Country` Catalogue フィールドにマッピングします。 |
+| 市区町村 | ドロップダウン選択 | 登録する`City` Catalogue フィールドにマッピングします。 |
+| 言語 | ドロップダウン選択 | \- 使用可能なフォーマットは、`ISO-639-1` 標準（例：en）である。<br>• 正しい形式の言語を登録してそれにマッピングします。 |
+| 生年月日 | ドロップダウン選択 | 登録する`Date of Birth` フィールドにマッピングします。 |
+| カスタム属性 | カスタムデータ入力 | 任意のユーザー属性をカスタムデータ入力にマップし、それをBrazeに送信する。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 ## Brazeコンソールでデータを見る
@@ -117,11 +117,11 @@ Symphonyでユーザーにフィルタを適用したり条件を追加した後
 
 ![][2]
 
-Brazeのユーザー・ダッシュボードのさまざまなセクションには、さまざまな属性がある。
+各種属性は、Braze 内のユーザーダッシュボードのさまざまなセクションに表示されます。
 - **Profile**タブにはユーザー属性が含まれる。
 - **カスタム属性**タブには、ユーザーが定義したカスタム属性が含まれる。
-- **カスタム・イベント・**タブには、ユーザーが定義したカスタム・イベントが含まれる。
-- **Purchases "**タブには、ユーザーが一定期間に購入したものが含まれる。
+- \[**カスタムイベント**] タブには、ユーザーが定義したカスタムイベントが表示されます。
+- \[**購入**] タブには、ユーザーが一定期間内に購入したものが表示されます。
 
 ## キャンペーン作成
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/zeotap.md b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/zeotap.md
index 619a9e3b211..b8aa46a10a6 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/zeotap.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/customer_data_platform/zeotap/zeotap.md
@@ -1,6 +1,6 @@
 ---
 nav_title: Zeotap
-description: "この参考記事では、Brazeと、アイデンティティの解決、洞察、エンリッチメントを提供する次世代顧客データプラットフォームZeotapのパートナーシップについて概説している。"
+description: "このリファレンス記事では、Braze と Zeotap のパートナーシップについて説明します。Zeotap は、アイデンティティ解決、インサイト、データ強化を提供する次世代顧客データプラットフォームです。"
 page_type: partner
 search_tag: Partner
 page_order: 1
@@ -8,7 +8,7 @@ page_order: 1
 
 # Zeotap
 
-> [Zeotapは](https://zeotap.com/)、アイデンティティの解決、洞察、データの充実を提供することで、モバイル利用者の発見と理解を支援する次世代顧客データ・プラットフォームである。
+> [Zeotap](https://zeotap.com/) は、アイデンティティ解決、インサイト、データ強化を提供して、モバイルオーディエンスを発見、理解できるようにする次世代の顧客データプラットフォームです。
 
 ZeotapとBrazeの統合により、Zeotapの顧客セグメントを同期してユーザーデータをBrazeのユーザーアカウントにマッピングすることで、キャンペーンの規模とリーチを拡大することができる。そして、このデータに基づいて行動し、ユーザーにパーソナライズされたターゲット体験を提供することができる。
 
@@ -16,47 +16,47 @@ ZeotapとBrazeの統合により、Zeotapの顧客セグメントを同期して
 
 | 必要条件 | 説明 |
 | --- | --- |
-|ゼオタップアカウント | このパートナーシップを利用するには、[Zeotapアカウントが](https://zeotap.com/)必要である。 |
+|Zeotap アカウント | このパートナーシップを活用するには、[Zeotap アカウント](https://zeotap.com/)が必要です。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは、\[インスタンスのBraze URL][1] に依存する。 |
+| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは\[インスタンスの Braze URL][1] に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 ## 統合
 
-### ステップ1:Zeotapデスティネーションを作成する
+### ステップ1:Zeotap の宛先を作成する
 
 1. Zeotap Unityプラットフォームから**DESTINATIONS**アプリケーションに移動する。
 2. **すべてのチャンネル**」で「**Braze**」を選択する。
-3. 表示されるプロンプトで、宛先に名前を付け、Brazeアカウントに関連付けられたクライアント名とBraze REST APIキーを入力する。
+3. 表示されるプロンプトで、宛先に名前を付け、Braze アカウントに関連付けられたクライアント名と Braze REST API キーを指定します。
 4. 最後に、ドロップダウンからBraze RESTエンドポイントインスタンスを選択し、保存先を指定する。<br><br>![][1]
 
 ### ステップ2:Zeotapセグメントを作成して目的地にリンクする 
  
 1. Zeotap Unityプラットフォームから**CONNECT**アプリケーションに移動する。
 2. セグメントを作成し、ステップ1で作成したBrazeデスティネーションを選択する。
-3. サポートされている出力識別子を選択する：MAID、SHA256にハッシュ化した電子メールアドレス、またはBrazeが認識する任意の1P顧客識別子（Brazeアカウントにカスタム識別子を使用したい場合は、アカウントで有効にできるようにZeotapに連絡すること）。Brazeの統合に使用できる出力識別子は1つだけである。これらの識別子は、Braze SDKデータ収集時に設定された外部IDと同じでなければならない。
+3. サポートされている出力識別子を選択する：MAID、SHA256 にハッシュされたメールアドレス、または Braze で認識される1P 顧客識別子 (Braze アカウントにカスタム識別子を使用する場合は、アカウントに対して有効にできるように、Zeotap に連絡してください)。Brazeの統合に使用できる出力識別子は1つだけである。これらの識別子は、Braze SDK データを収集するときに設定された external ID と同じである必要があります。
 4. セグメントを保存する。
 
 ![][2]
 
 {% alert note %}
-表示される識別子は、セグメントで使用可能で、Brazeがサポートしているものである。
+表示される識別子はセグメントで使用でき、Braze でサポートされています。
 {% endalert %}
 
 ### ステップ3:ブレイズセグメントを作成する
 
 Zeotapでセグメントの作成、プッシュ、処理に成功すると、BrazeダッシュボードにZeotapユーザーが表示される。BrazeダッシュボードでユーザーIDからユーザーを検索できる。 
 
-![Brazeのユーザープロファイル。"Custom attributes "の下に、セグメント1から4までが "true "と表示されている。][4]
+![「カスタム属性」の下でセグメント1から4が「true」としてリストされている Braze ユーザープロファイル。][4]
 
-ユーザーが Zeotap セグメントの一部である場合、セグメント名はユーザー プロファイルのカスタム属性としてブーリアン値`true` とともに表示される。Brazeセグメントを作成する際に必要になるので、カスタム属性名をメモしておくこと。 
+ユーザーが Zeotap セグメントの一部である場合、セグメント名は、ブール値 `true` が設定されているユーザープロファイルのカスタム属性として表示されます。Brazeセグメントを作成する際に必要になるので、カスタム属性名をメモしておくこと。 
 
-次に、このセグメントをBraze内で作成し、定義する必要がある：
-1. Brazeダッシュボードから、**セグメントを**選択し、**セグメントを作成する**。
+次に、Braze 内でこのセグメントを作成して定義する必要があります。
+1. Braze ダッシュボードから \[**セグメント**] を選択し、次に \[**セグメントを作成**] を選択します。
 2. 次に、セグメントに名前を付け、Zeotapで作成したカスタム属性セグメントを選択する。
 3. 変更を保存する。 
 
-![Brazeのセグメントビルダーでは、インポートされたセグメントがカスタム属性として設定されている。][3]
+![Braze セグメントビルダーでインポートされたセグメントがカスタム属性として設定されていることがわかる。][3]
 
 この新しく作成したセグメントを、今後のBrazeのキャンペーンやキャンバスに追加して、これらのエンドユーザーをターゲットにすることができる。 
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy.md
index 5b7b7ba1372..0bc5b7f4052 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy.md
@@ -16,8 +16,8 @@ partner_top_header: "Data Privacy & Compliance"
 valid_partner_list:
 - name: Transcend
   url: /docs/partners/data_and_infrastructure_agility/data_privacy/transcend/
-- name: データグレイル
+- name: DataGrail
   url: /docs/partners/data_and_infrastructure_agility/data_privacy/datagrail/
-- name: ワントラスト
+- name: OneTrust
   url: /docs/partners/data_and_infrastructure_agility/data_privacy/onetrust/
 ---
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md
index 8b4df17a03d..be97215fec8 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/datagrail.md
@@ -1,37 +1,37 @@
 ---
-nav_title: データ・グレイル
-article_title: データ・グレイル
-description: "この参考記事では、Brazeとプライバシー管理プラットフォームであるDataGrailのパートナーシップについて概説しており、Braze内で収集・保存された消費者データを検出してDSRを迅速に処理することができる。"
+nav_title: DataGrail
+article_title: DataGrail
+description: "このリファレンス記事では、Braze と DataGrail のパートナーシップについて説明します。DataGrail はプライバシー管理プラットフォームであり、Braze 内で収集され、保存されている消費者データを検出してDSR を迅速に処理できます。"
 alias: /partners/datagrail/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# データ・グレイル
+# DataGrail
 
-> プライバシー管理プラットフォームである[DataGrailは](https://www.datagrail.io/)、消費者の信頼を築き、リスクの高いビジネスを排除するのに役立つ。継続的なシステム検知と自動化されたデータ対象者要求（DSR）の履行により、DataGrailはプライバシープログラムを強化し、GDPR、CCPA、CPRAのような進化するプライバシー法や規制へのコンプライアンスをサポートする。 
+> [DataGrail](https://www.datagrail.io/) は、消費者の信頼を得て、リスクの高いビジネスを排除するうえで役立つプライバシー管理プラットフォームです。DataGrail は、継続的なシステム検出と自動化されたデータ主体要求 (DSR) の履行により、プライバシープログラムを推進し、GDPR、CCPA、CPRA などの変遷するプライバシー関連の法律や規制に準拠できるように支援します。 
 
-BrazeとDataGrailの統合により、Braze内に収集・保存された消費者データを検出し、DSR（アクセス、削除、販売禁止要求）を迅速に処理することができる。Brazeは、自動化されたデータマッピングによって、消費者データが組織内のどこに存在するかの正確な青写真に追加される。プライバシーフレームワークを維持したり、処理活動の記録（RoPA）を作成したりするための調査やスプレッドシートはもう必要ない。 
+BrazeとDataGrailの統合により、Braze内に収集・保存された消費者データを検出し、DSR（アクセス、削除、販売禁止要求）を迅速に処理することができる。自動化されたデータマッピングにより、消費者データが組織内のどこにあるかを正確に把握できるうえに、Braze が追加されるため、プライバシーフレームワークの維持や処理活動の記録 (RoPA) の作成にアンケートやスプレッドシートは不要になります。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| DataGrailアカウント | このパートナーシップを利用するには、DataGrailアカウントが必要である。<br>統合に関する問題や質問があれば、管理者に連絡するか、support@datagrail.io 。 |
-| BrazeのAPIキー | `events.list` 、`users.export.ids` 、`users.delete` 、`users.track` の権限を持つBraze REST APIキー。<br><br>これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| ブレイズインスタンス | あなたのBrazeインスタンスは、あなたのBrazeオンボーディングマネージャーから取得するか、[API概要ページで]({{site.baseurl}}/api/basics/#endpoints)見つけることができる。 |
+| DataGrailアカウント | このパートナーシップを活用するには、DataGrail アカウントが必要です。<br>統合に関する問題や質問がある場合は、システム管理者にお問い合わせいただくか、または support@datagrail.io までメールでお問い合わせください。 |
+| BrazeのAPIキー | `events.list`、`users.export.ids`、`users.delete`、`users.track` の権限を持つ Braze REST API キー。<br><br>これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
+| ブレイズインスタンス | Braze インスタンスは Braze オンボーディングマネージャーから入手できます。また、[API 概要ページ]({{site.baseurl}}/api/basics/#endpoints)でも確認できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-DataGrailポータルにログインし、Brazeの統合ページで**Connectを**クリックする。次に、インスタンスとBraze API Keyを入力し、**Connect Brazeを**クリックする。
+DataGrail ポータルにログインし、Braze の統合ページで \[**Connect**] をクリックします。次にインスタンスと Braze API キーを入力し、\[**Connect Braze**] をクリックします。
 
 統合するBrazeアカウントが追加された場合：
-1. Brazeの統合ページで**Edit Connectionを**クリックする。
-2. ドロップダウンから、**+Add New Connectionを**選択する。
+1. Braze の統合ページで \[**Edit Connection**] をクリックします。
+2. ドロップダウンから \[**+Add New Connection**] を選択します。
 3. **Connection Name（接続名**）の下に、この別個のアカウントを識別するための新しい名前を入力する（例：Braze Training Account）。
 4. この新しいアカウント用に、別のBrazeインスタンスとAPIキーを入力する。
-5. **コネクトを**クリックする。
+5. \[**Connect**] をクリックします。
 
-統合に関する問題や質問があれば、DataGrail（support@datagrail.io ）までEメールで問い合わせを。
+統合に関する問題やご質問がある場合は、DataGrail (support@datagrail.io) までメールでお問い合わせください。
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/onetrust.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/onetrust.md
index 8d4bfb3012c..ef7c26ba247 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/onetrust.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/onetrust.md
@@ -1,23 +1,23 @@
 ---
-nav_title: ワントラスト
-article_title: ワントラスト
-description: "このリファレンス記事では、データプライバシーおよびセキュリティソフトウェアプロバイダであるBraze とOneTrust の連携について説明します。これにより、OneTrust ワークフロービルダを使用して製品のセキュリティワークフローを作成できます。"
+nav_title: OneTrust
+article_title: OneTrust
+description: "このリファレンス記事では、Braze と OneTrust のパートナーシップについて説明します。OneTrust は、データプライバシーおよびセキュリティソフトウェアのプロバイダーであり、お客様は OneTrust ワークフロービルダーを使用して自社製品のセキュリティワークフローを作成できます。"
 alias: /partners/onetrust/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# ワントラスト
+# OneTrust
 
-> [OneTrust](https://www.onetrust.com/) はプライバシーとセキュリティーのソフトプロバイダーで、信頼性の状況、強力なインサイトs を活用するためのアクション、競合からの高揚を維持するためのオートメーションをよりよく理解するために必要な可視性を提供します。 
+> [OneTrust](https://www.onetrust.com/) は、プライバシーおよびセキュリティソフトウェアのプロバイダーであり、信頼の状況、強力なインサイトを活用するためのアクション、そして競争で常に優位に立つためのオートメーションをより詳しく理解するために必要な可視化機能を提供します。 
 
 Braze とOneTrust の統合により、OneTrust ワークフロービルダーを使用してプロダクトのセキュリティワークフローを作成できます。
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| ワン信託口 | [OneTrust](https://www.onetrust.com/)は、この提携の前進タグeを考慮します。 |
+| OneTrust アカウント | このパートナーシップを活用するには、[OneTrust](https://www.onetrust.com/) アカウントが必要です。 |
 | Braze API キー | OneTrust アクションが使用するエンドポイントに必要な権限を持つBraze REST API キー。<br><br>これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
 | Brazeインスタンス | Brazeインスタンスは、Braze オンボーディング マネージャーから取得するか、[API 概要ページ]({{site.baseurl}}/api/basics/#endpoints) にあります。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -26,43 +26,43 @@ Braze とOneTrust の統合により、OneTrust ワークフロービルダー
 
 次の統合では、ユーザー同意更新ワークフローとユーザー削除ワークフローを作成するためのガイダンスを提供します。追加でサポートされるBraze エンドポイントの詳細については、[サポートされる他のアクションs](#Other-supported-actions)を参照してください。
 
-### ワントラストへのBraze 認証情報の追加
+### OneTrust に Braze 認証情報を追加する
 
 OneTrust **Integrations** メニューで、**Credentials**> **Add New** ボタンに移動して、**Select System** 画面を表示します。ここで、**Braze**を見つけ、**Next**ボタンをクリックします。
 
-**Credential Details**画面のプロンプトに従って、次の情報を入力します。完了したら、認証情報を保存します。
+\[**Enter Credential Details**] 画面のプロンプトに従って、次の情報を入力します。完了したら、認証情報を保存します。
   - 認証情報名
   - コネクタータイプを**Webアプリ**に設定します。
   - ホスト名: `<your-braze-instance-url>`
-  - **リクエストヘッダ**:
-    - **認証**:ベアラ
+  - **リクエストヘッダー**:
+    - **Authorization**:Bearer
     - **Content-Type**: application/json
   - トークン: `<your-braze-api-key>`
 
-### Brazeを系として追加する
+### Braze をシステムとして追加する
 
 #### ステップ1:ワークフローの作成
 
 {% tabs %}
-{% tab ユーザ同意更新 %}
-1. OneTrust 統合メニューで、**Gallery** > **Braze** > **Add** に移動して新しいワークフローを作成します。![]({% image_buster /assets/img/onetrust/onetrust.png %})<br><br>
-2. ワークフローモーダルに名前と通知 メールを入力します。**Create**ボタンをクリックします。作成時に、Workflow Builder に移動します。Brazeワークフローには、削除リクエストの処理に使用できるAPI コールとアクションがシードされます。<br><br>
+{% tab ユーザー同意の更新 %}
+1. OneTrust 統合メニューで \[**Gallery**] > \[**Braze**] > \[**Add**] に移動し、新しいワークフローを作成します。![]({% image_buster /assets/img/onetrust/onetrust.png %})<br><br>
+2. ワークフローモーダルに名前と通知 メールを入力します。**Create**ボタンをクリックします。作成時に Workflow Builder が表示されます。Brazeワークフローには、削除リクエストの処理に使用できるAPI コールとアクションがシードされます。<br><br>
 3. Workflow Builder で、ワークフローでトリガーするアクションを選択します。<br>![]({% image_buster /assets/img/onetrust/onetrust2.png %})
 
 {% endtab %}
 {% tab ユーザー削除 %}
 
-1. OneTrust 統合メニューで、**Gallery** > **Braze** > **Add** に移動して新しいワークフローを作成します。![]({% image_buster /assets/img/onetrust/onetrust.png %})<br><br>
-2. ワークフローモーダルに名前と通知 メールを入力します。**Create**ボタンをクリックします。作成時に、Workflow Builder に移動します。Brazeワークフローには、削除リクエストの処理に使用できるAPI コールとアクションがシードされます。<br><br>
+1. OneTrust 統合メニューで \[**Gallery**] > \[**Braze**] > \[**Add**] に移動し、新しいワークフローを作成します。![]({% image_buster /assets/img/onetrust/onetrust.png %})<br><br>
+2. ワークフローモーダルに名前と通知 メールを入力します。**Create**ボタンをクリックします。作成時に Workflow Builder が表示されます。Brazeワークフローには、削除リクエストの処理に使用できるAPI コールとアクションがシードされます。<br><br>
 3. Workflow Builder で、ワークフローでトリガーするアクションを選択します。<br>![]({% image_buster /assets/img/onetrust/onetrust8.png %})
 {% endtab %}
 {% endtabs %}
 
 #### ステップ2:アクションの選択
 {% tabs %}
-{% tab ユーザ同意更新 %}
+{% tab ユーザー同意の更新 %}
 
-1. 完了したら、**Done**をクリックし、**Add Action**を選択します。選択するアクションは、更新のプリファレンスの種類dと希望するエンドポイントによって異なります。
+1. 完了したら、**Done**をクリックし、**Add Action**を選択します。選択するアクションは、更新される設定のタイプと使用するエンドポイントによって異なることに注意してください。
 - ユーザーのグローバルサブスクリプション設定を更新するには、**POST ユーザートラック-属性s**アクションを選択します。
 - ユーザーのサブスクリプショングループ設定を更新するには、**POST ユーザー Track - Attributes**アクションまたは**POST Set ユーザー s サブスクリプショングループ Status**アクションを選択します。<br>![]({% image_buster /assets/img/onetrust/onetrust4.png %})<br><br>
 2. 目的のアクションを選択し、以前に作成したBraze 認証情報s を選択して、**Next** をクリックします。<br>![]({% image_buster /assets/img/onetrust/onetrust5.png %})
@@ -79,14 +79,14 @@ OneTrust **Integrations** メニューで、**Credentials**> **Add New** ボタ
 {% endtabs %}
 #### ステップ3:更新リクエストボディ
 {% tabs %}
-{% tab ユーザ同意更新 %}
+{% tab ユーザー同意の更新 %}
 
-1. 本文をアップデートして、必要なすべてのダイナミックなを含めます。アクションの本体が[`/users/track` エンドポイント](https://www.braze.com/docs/api/endpoints/user_data/post_user_track/) と[`/subscription/status/set` エンドポイント](https://www.braze.com/docs/api/endpoints/subscription_groups/post_update_user_subscription_group_status/) に一致することを確認します。
+1. 本文を更新して、必要なすべてのダイナミック値を含めます。アクションの本体が[`/users/track` エンドポイント](https://www.braze.com/docs/api/endpoints/user_data/post_user_track/) と[`/subscription/status/set` エンドポイント](https://www.braze.com/docs/api/endpoints/subscription_groups/post_update_user_subscription_group_status/) に一致することを確認します。
 2. 組織のニーズを満たすように、追加のパラメータまたは条件付きロジックを使用してワークフローをカスタマイズします。
 3. 編集が終了したら、**Finish**をクリックし、次に**Activate**をクリックしてワークフローを有効にします。
 
 {% alert note %}
-OneTrust ワークフローを使用してBraze でプリファレンスを更新 サブスクリプショングループする場合、`subscription_group_id` は、サブスクリプショングループの作成時にBraze によって設定されたID と一致する必要があります。サブスクリプショングループの`subscription_group_id` にアクセスするには、Braze ダッシュボードの**サブスクリプショングループ** ページに移動します。
+OneTrust ワークフローを使用して Braze でサブスクリプショングループの設定を更新する場合、`subscription_group_id` は、サブスクリプショングループの作成時に Braze により設定された ID と一致している必要があります。サブスクリプショングループの`subscription_group_id` にアクセスするには、Braze ダッシュボードの**サブスクリプショングループ** ページに移動します。
 {% endalert %}
 
 ![]({% image_buster /assets/img/onetrust/onetrust6.png %})
@@ -94,13 +94,13 @@ OneTrust ワークフローを使用してBraze でプリファレンスを更
 {% endtab %}
 {% tab ユーザー削除 %}
 
-1. 本文をアップデートして、必要なすべてのダイナミックなを含めます。アクションの本体が[`/users/delete`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/)と一致することを確認します。
+1. 本文を更新して、必要なすべてのダイナミック値を含めます。アクションの本体が[`/users/delete`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_delete/)と一致することを確認します。
 2. 編集が終了したら、**Finish**、**Activate**を選択してワークフローを有効にします。
 
 ![]({% image_buster /assets/img/onetrust/onetrust10.png %})
 
-#### データサブジェクト要求ワークフローの更新
-1. **Privacy Rights Automation**メニューで、**Workflows**を選択します。 
+#### データ主体の要求ワークフローを更新する
+1. \[**Privacy Rights Automation**] メニューで \[**Workflows**] を選択します。 
 2. Brazeインテグレーションで更新するワークフローを選択します。 
 3. **編集**ボタンを選択して編集を有効にします。
 4. 次に、ワークフローステップを選択してBrazeインテグレーションを追加し、**接続の追加**をクリックします。
@@ -109,13 +109,13 @@ OneTrust ワークフローを使用してBraze でプリファレンスを更
 {% endtab %}
 {% endtabs %}
 
-## 他の対応アクション
+## サポートされるその他のアクション
 
 **POST ユーザートラック- 属性**、**POST ユーザー設定サブスクリプショングループステータス**、および**POST ユーザー削除** アクションs に加えて、Braze は、カスタムワークフローを作成し、既存のワークフロー内でサブタスクとして使用できる他のエンドポイントをサポートします。 
 
 サポートされているアクションの一覧を表示するには
 1. OneTrust で、**Integrations** メニューから**Systems** をクリックします。 
-2. **Braze**系を選択します。
+2. **Braze** システムを選択します。
 3. **Actions** タブに移動します。
 
 ![][7]
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/transcend.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/transcend.md
index f124a3b64e2..2dd32d1957f 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/transcend.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_privacy/transcend.md
@@ -1,56 +1,56 @@
 ---
-nav_title: 超越する
-article_title: 超越する
-description: "この参考記事では、Brazeとデータプライバシー・インフラストラクチャ・プラットフォームであるTranscendのパートナーシップについて概説している。"
+nav_title: Transcend
+article_title: Transcend
+description: "このリファレンス記事では、Braze と Transcend のパートナーシップについて説明します。Transcend はデータプライバシーインフラストラクチャプラットフォームであり、Braze のユーザーがデータ主体要求を自動的に履行できるようにします。"
 alias: /partners/transcend/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# 超越する
+# Transcend
 
-> トランセンドは、データ・プライバシー・インフラストラクチャー企業であり、企業がユーザーに自分のデータをコントロールさせることを容易にし、企業内のすべてのデータ・システムとベンダーにまたがるデータ主体の要求を自動的に満たす。 
+> Transcend はデータプライバシーインフラストラクチャ企業であり、企業のユーザーがデータを簡単に管理できるようにし、すべてのデータシステムおよびベンダーに対するデータ主体要求を社内での自動的に履行します。 
 
-BrazeとTranscendのパートナーシップは、ユーザーが数十のデータシステムにわたってデータをオーケストレーションすることによってプライバシー要求を自動化し、チームがGDPRやCCPAのような規制に準拠するのを支援する。トランセンドは、`privacy.\<company\>.com` でホストされているコントロールパネル（プライバシーセンター）をエンドユーザーに提供し、ユーザーはそこでプライバシー設定を管理したり、データをエクスポートしたり、削除したりすることができる。 
+BrazeとTranscendのパートナーシップは、ユーザーが数十のデータシステムにわたってデータをオーケストレーションすることによってプライバシー要求を自動化し、チームがGDPRやCCPAのような規制に準拠するのを支援する。Transcend はエンドユーザーに対し、`privacy.\<company\>.com` でホストされるコントロールパネルまたはプライバシーセンターを提供します。このコントロールパネルまたはプライバシーセンターでは、ユーザーが各自のプライバシー設定の管理、データのエクスポート、データの削除を行うことができます。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| トランセンドアカウント | このパートナーシップを利用するには、管理者権限を持つ[トランセンドの](https://app.transcend.io/)アカウントが必要である。 |
+| Transcend アカウント | このパートナーシップを利用するには、管理者権限を持つ[Transcend](https://app.transcend.io/) アカウントが必要です。 |
 | BrazeのAPIキー | `users.delete, users.alias.new, users.export.ids, email.unsubscribe,`および`email.blacklist` 権限を持つ Braze REST API キー。<br><br>これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-トランセンドは、データプライバシー規制に従って、Brazeプラットフォームでプログラム的にユーザーにアクセスし、消去し、コミュニケーションからオプトアウトすることを可能にする。
+Transcend では、Braze プラットフォームでコミュニケーションへのアクセス、消去、ユーザーのオプトアウトを、データプライバシー規制に従ってプログラムで実行できるようにします。
 
 ### ステップ1:Brazeとの統合をセットアップする
-まずは[トランセンドに](https://app.transcend.io/login)ログインしよう。
-1. **データマップ＞データサイロの追加＞Brazeと**進み、**接続**ボタンを選択する。<br><br>
+開始するには、[Transcend](https://app.transcend.io/login) にログインします。
+1. **\[Data Map] > \[Add Data Silo] > \[Braze]** に移動し、\[**Connect**] ボタンを選択します。<br><br>
 2. アカウントがプロビジョニングされると、対応するURLのいずれかにログインする：`https://dashboard-01.braze.com` `https://dashboard-02.braze.com, ..., https://dashboard-01.braze.eu` 。<br> 以下の[表を使って]({{site.baseurl}}/api/basics/#endpoints)、ダッシュボードのURLからどのサブドメインを含めるべきかを考えよう。<br><br>
-3. 接続したら、**トランセンド・プライバシー・センター・タブに**移動する。ここで、Brazeのデータをあなたのデータプラクティスにマッピングする必要がある。これを行うには、適切な命名規則（たとえば、"Mailing Lists or User Profile"）で、新しいカテゴリと新しいデータコレクションを作成する。完了したら、**Publishを**押す。<br><br>
-4. データマップに戻り、Brazeデータサイロをクリックする。**Manage Datapoints（データポイントの管理**）を展開して、前のステップで作成したコ レクション・ラベル（カテゴリ）をドロップダウンから選択する。また、どのデータ・ポイントに対してどのデータ・アクション（例えば、アクセスや消去）を有効にするかを選択することもできる。<br><br>
-5. 次に、Brazeのデータサイロに入ったまま、**Manage Identifiersを**展開する。有効にしたい識別子のボックスにチェックを入れる。例えば、トランセンドに電子メールアドレスでユーザーを検索させたい場合、電子メールアドレス識別子を有効にするボックスにチェックを入れる。
+3. 接続したら、Transcend の \[**Privacy Center**] タブに移動します。ここで、Brazeのデータをあなたのデータプラクティスにマッピングする必要がある。これを行うには、適切な命名規則で新しいカテゴリと新しいデータコレクションを作成します (（「Mailing Lists or User Profile」など)。完了したら、\[**Publish**] をクリックします。<br><br>
+4. Data Map に戻り、Braze データサイロをクリックします。**Manage Datapoints（データポイントの管理**）を展開して、前のステップで作成したコ レクション・ラベル（カテゴリ）をドロップダウンから選択する。また、どのデータポイントに対してどのデータアクション (アクセスや消去など) を有効にするかを選択することもできます。<br><br>
+5. 次に、Braze データサイロが表示された状態で、\[**Manage Identifiers**] を展開します。有効にしたい識別子のボックスにチェックを入れる。たとえば、Transcend でユーザーをメールアドレスで検索する場合は、このチェックボックスをオンにしてメールアドレス識別子を有効にします。
 
 {% alert note %}
-識別子が正しく有効になっていない場合、トランセンドは特定のユーザーのリクエストを処理できないことがある。
+識別子が適切に有効化されていない場合、Transcend は特定のユーザーのリクエストを処理できないことがあります。
 {% endalert %}
 
-### ステップ2:テスト依頼
-トランセンドは、エンドユーザーからのリクエストを処理し始める前に、データマップ全体でリクエストをテストすることを推奨している。
-1. トランセンドの**プライバシーセンターに**行き、**プライバシーセンターを見るを**クリックする。<br><br>
-2. **プライバシーセンターから**、「**コントロールする**」をクリックし、「**自分のデータをダウンロードする**」をクリックする。リクエストを送信する前に、Eメールを入力するか、ログインして認証する。<br><br>
-3. トランセンドからのメッセージをメールで確認する。リクエストを確認するために、確認リンクをクリックするよう求められる。<br><br>
-4. 次に、**管理者**ダッシュボードに戻って、**受信リクエスト**タブに移動し、リクエストを選択する。ここにリクエストが表示されない場合は、トランセンドの[support@transcend.io](mailto:support@transcend.io)まで連絡を。<br><br>
-5. リクエストをクリックしたら、**Data Silos**タブに移動し、**Brazeを**選択する。返されたデータを検査し、確認する。<br><br>
+### ステップ2:要求をテストする
+Transcend は、エンドユーザーからの要求の処理を開始する前に、Data Map 全体で要求をテストすることを推奨しています。
+1. Transcend で \[**Privacy Center**] に移動し、\[**View your Privacy Center**] をクリックします。<br><br>
+2. **プライバシーセンターから**、「**コントロールする**」をクリックし、「**自分のデータをダウンロードする**」をクリックする。要求を送信する前に、自分自身を認証するためにメールを入力するか、ログインします。<br><br>
+3. メールで Transcend からのメッセージを確認します。リクエストを確認するために、確認リンクをクリックするよう求められる。<br><br>
+4. 次に、**管理者**ダッシュボードに戻って、**受信リクエスト**タブに移動し、リクエストを選択する。ここに要求が表示されない場合は、Transcend ([support@transcend.io](mailto:support@transcend.io)) までお問い合わせください。<br><br>
+5. 要求をクリックしたら、\[**Data Silos**] タブに移動し、\[**Braze**] を選択します。返されたデータを検査し、確認する。<br><br>
 6. 最後に、**「レポート**」タブに移動し、「**承認して送信**」をクリックする。申請時に提出したEメールアドレスに報告書が届くはずだ。
 
-## ブレージングを外す
-トランセンドデータマップからBrazeデータサイロを削除する：
-1. **データマップに**移動し、**Brazeを**クリックする。<br><br>
-2. 画面下部で、**Remove Brazeを**展開し、**Remove Siloを**クリックする。サイロを削除するかどうかを確認するプロンプトが表示される。**Okを**クリックする。<br><br>
-3. データ・マップに戻り、サイロが削除されたことを確認する。
+## Braze 統合を削除する
+Transcend Data Mapから Braze データサイロを削除するには、次の手順に従います。
+1. **Data Map** に移動し、\[**Braze**] をクリックします。<br><br>
+2. 画面の下部で \[**Remove Braze**] を展開し、\[**Remove Silo**] をクリックします。サイロを削除するかどうかを確認するプロンプトが表示される。\[**OK**] をクリックします。<br><br>
+3. Data Map に戻り、サイロが削除されたことを確認します。
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses.md
index 880eabee43e..3393ad0f926 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses.md
@@ -1,10 +1,10 @@
 ---
 nav_title: データウェアハウス
-article_title: データウェアハウスパートナー
+article_title: データウェアハウスのパートナー
 page_order: 7
 
 page_type: landing
-description: "このランディングページには、メッセージング キャンペーン s からデータを使用できるようにするために役立つBrazeパートナ(Alloys) が一覧表示されます。"
+description: "このランディングページには、メッセージングキャンペーンのデータを利用可能にできるように支援する Braze パートナー (Alloys) が一覧表示されています。"
 
 layout: partner_page
 search_tag: Partner
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake.md
index be310c64a89..57a6ff0bdd6 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake.md
@@ -2,7 +2,7 @@
 nav_title: Snowflake
 article_title: Snowflake
 alias: /partners/snowflake/
-description: "このリファレンス記事は、Braze と Snowflake のパートナーシップについて概説しています。Snowflake は、すべてのデータとユーザーのために特別に構築された SQL クラウド データウェアハウスです。"
+description: "このリファレンス記事では、Braze と Snowflake のパートナーシップについて説明します。Snowflake は専用 SQL クラウドデータウェアハウスであり、お客様のすべてのデータとユーザーに対応しています。"
 page_type: partner
 search_tag: Partner
 
@@ -10,33 +10,33 @@ search_tag: Partner
 
 # [![Brazeラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/snowflake-secure-data-sharing-via-braze/){: style="float:right;width:120px;border:0;" class="noimgborder"}Snowflake
 
-> [Snowflake](https://docs.snowflake.net/manuals/user-guide/intro-key-concepts.html) は、Software-as-a-Service (SaaS) として提供される目的別 SQL クラウド データウェアハウスです。Snowflakeは、従来のデータウェアハウス製品よりも高速で使いやすく、はるかに柔軟なデータウェアハウスを提供します。Snowflakeのユニークで特許取得済みのアーキテクチャにより、すべてのデータを集約し、迅速な分析を可能にし、すべてのユーザーにデータドリブン型のインサイトを提供することが容易になります。
+> [Snowflake](https://docs.snowflake.net/manuals/user-guide/intro-key-concepts.html) は、Software-as-a-Service (SaaS) として提供される専用 SQL クラウドデータウェアハウスです。Snowflake のデータウェアハウスは、従来のデータウェアハウス製品よりも高速で使いやすく、極めて高い柔軟性を備えています。Snowflake 独自の特許取得済みアーキテクチャにより、すべてのデータを集約し、迅速な分析を可能にし、すべてのユーザーにデータドリブンのインサイトを提供することが容易になります。
 
-パーソナライズされたおよび関連性のあるマーケティングキャンペーンには、その瞬間のデータへのアクセスが必要です。だからこそBrazeはSnowflakeと提携してデータ共有を開始しました。この共同提供により、マーケターはこれまでになく迅速にカスタマーエンゲージメントおよびキャンペーンデータの可能性を引き出すことができます。
+パーソナライズされたおよび関連性のあるマーケティングキャンペーンには、その瞬間のデータへのアクセスが必要です。だからこそBrazeはSnowflakeと提携してデータ共有を開始しました。この共同の取り組みにより、マーケターはこれまでになく迅速にカスタマーエンゲージメントとびキャンペーンデータの可能性を引き出すことができます。
 
 [BrazeとSnowflakeの統合](https://www.braze.com/perspectives/article/snowflake-partner-announcement)は、Snowflakeのデータ交換を活用してプレゼンスを構築し、新しい顧客を見つけ、増え続けるSnowflakeの顧客基盤を通じてリーチを拡大します。
 
 {% alert tip %}
-**SnowflakeアカウントがなくてもSnowflakeレベルのデータにアクセスできることに興味がありますか？**<br>[Snowflake Reader Accounts]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/how_braze_uses_currents/#snowflake-reader-accounts)をチェックしてください。Reader Accounts では、Braze がお客様のデータを作成してアカウントと共有し、またログインしてデータにアクセスするための認証情報を用意します。これにより、すべてのデータ共有と使用量請求は  Braze が完全に処理することになります。
+**Snowflake アカウントがなくても Snowflake レベルのデータにアクセスできるとしたらどうでしょうか?**<br>「[Snowflake Reader アカウント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/how_braze_uses_currents/#snowflake-reader-accounts)」をご覧ください。Reader Accounts では、Braze がお客様のデータを作成してアカウントと共有し、またログインしてデータにアクセスするための認証情報を用意します。これにより、すべてのデータ共有と使用量請求は  Braze が完全に処理することになります。
 {% endalert %}
 
 ## データ共有とは何ですか？
 
-Snowflakeの[Secure Data Sharing](https://docs.snowflake.net/manuals/user-guide/data-sharing-intro.html)機能により、BrazeはSnowflakeポータル上のデータへの安全なアクセスを提供し、通常のデータ提供者との関係に伴うワークフローの摩擦や遅延、失敗点、不必要なコストを心配することなく利用できます。データ共有は、次の統合を通じて、または[Snowflake Reader Accounts]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/how_braze_uses_currents/#snowflake-reader-accounts)を通じて設定できます。
+Snowflakeの[Secure Data Sharing](https://docs.snowflake.net/manuals/user-guide/data-sharing-intro.html)機能により、BrazeはSnowflakeポータル上のデータへの安全なアクセスを提供し、通常のデータ提供者との関係に伴うワークフローの摩擦や遅延、失敗点、不必要なコストを心配することなく利用できます。データ共有は、次の統合または [Snowflake Reader アカウント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/how_braze_uses_currents/#snowflake-reader-accounts)で設定できます。
 
-- **洞察までの時間を短縮する**<br>ETLプロセスの構築に数週間かかることにさよならを言いましょう。BrazeとSnowflakeのユニークなアーキテクチャにより、すべてのカスタマーエンゲージメントおよびキャンペーンデータは、データレイクに到着した瞬間から即座にアクセス可能でクエリ可能になります。データはコピーまたは移動されないため、最も関連性が高く最新の情報に基づいて顧客体験を提供できます。
-- **データサイロ化を解消する**<br>チャネルやプラットフォーム全体で顧客の全体像を把握する。データ共有により、Brazeのカスタマーエンゲージメントデータを他のすべてのSnowflakeデータと結合することがこれまでになく簡単になり、単一の信頼できる情報源全体でより豊かな洞察を生み出します。
-- **あなたのエンゲージメントがどのように積み重なるかを確認してください**<br>Brazeベンチマークを使用して、カスタマーエンゲージメント戦略を最適化します。このインタラクティブツールは、BrazeとSnowflakeによって提供されており、ブランドのエンゲージメントデータをチャネル、業界、デバイスプラットフォーム全体のベンチマークと比較することができます。
+- **洞察までの時間を短縮する**<br>ETLプロセスの構築に数週間かかることにさよならを言いましょう。Braze と Snowflake の独自のアーキテクチャにより、すべてのカスタマーエンゲージメントとキャンペーンデータは、データレイクに到着した時点からすぐにアクセスおよびクエリ可能になります。データのコピーと移動は行われないので、最も関連性が高い最新の情報のみに基づいて顧客体験を提供できます。
+- **データのサイロ化を解消する**<br>チャネルやプラットフォーム全体で顧客の全体像を把握する。データ共有により、Braze のカスタマーエンゲージメントデータを他のすべての Snowflake データと結合することがこれまで以上に容易になり、唯一の信頼できる情報源全体でより豊富なインサイトが作成されます。
+- **お客様のエンゲージメントの状況を確認する**<br>Brazeベンチマークを使用して、カスタマーエンゲージメント戦略を最適化します。このインタラクティブツールは、BrazeとSnowflakeによって提供されており、ブランドのエンゲージメントデータをチャネル、業界、デバイスプラットフォーム全体のベンチマークと比較することができます。
 
-データ共有では、実際のデータはアカウント間でコピーまたは転送されません。すべての共有は、Snowflakeのユニークなサービス層とメタデータストアを通じて行われます。これは重要な概念です。なぜなら、共有データは消費者アカウントにストレージを占有せず、したがって消費者の月間データストレージ料金に寄与しないからです。消費者への唯一の請求は、共有データをクエリするために使用されるコンピューティングリソース（仮想ウェアハウスなど）に対してです。
+データ共有では、実際のデータはアカウント間でコピーまたは転送されません。すべての共有は Snowflake 独自のサービスレイヤーとメタデータストアを介して行われます。共有データは消費者アカウントのストレージを一切使用しないため、これは重要な意味を持ちます。したがって、消費者の毎月のデータストレージ料金には影響しません。消費者に請求されるのは、共有データをクエリするために使用されるコンピューティングリソース (仮想ウェアハウスなど) **のみ**です。
 
-さらに、Snowflake の組み込みロールと権限機能を使用して、Braze から共有されたデータへのアクセスを、Snowflake アカウントおよびその中のデータに既に設定されているアクセス制御を使用して制御および管理できます。アクセスは、あなた自身のデータと同じ方法で制限および監視できます。
+さらに、Snowflake の組み込みの役割と権限の機能を使用すると、Snowflake アカウントとアカウント内のデータに対してすでに適用されているアクセス制御を使用して、Braze から共有されるデータへのアクセスを制御および管理できます。アクセスは、あなた自身のデータと同じ方法で制限および監視できます。
 
 [セキュアデータ共有の紹介](https://docs.snowflake.net/manuals/user-guide/data-sharing-intro.html#how-does-secure-data-sharing-work)をチェックして、Snowflakeのデータ共有の仕組みについて詳しく読んでください。
 
 ## 前提条件
 
-この統合に興味がある場合は、Brazeアカウントまたは顧客成功マネージャーに連絡し、Snowflakeとのセキュアデータ共有に関するBrazeデータ戦略サービスに相談するよう依頼してください。これによりBrazeの内部で歯車が回り始め、すぐにビューが設定されます！
+この統合について興味をお持ちの場合は、Snowflake とのセキュアデータ共有に関して Brazeデータ戦略サービスと相談するため、Braze アカウントまたはカスタマーサクセスマネージャーにご連絡ください。これにより Braze 内での手続きが開始され、お客様のビューが速やかに準備されます。
 
 | 要件 | 説明 |
 | ----------- | ----------- |
@@ -48,9 +48,9 @@ Snowflakeの[Secure Data Sharing](https://docs.snowflake.net/manuals/user-guide/
 Brazeアカウントでセキュアデータ共有を設定するには、次の手順に従ってください。
 
 1. Brazeダッシュボードの**パートナー統合** > **データ共有**に移動します。
-2. Snowflakeアカウントの詳細を入力してください。送信先アカウントで`SELECT CURRENT_ACCOUNT()`を実行することにより、SnowflakeアカウントIDを見つけることができます。
-3. クラウドプロバイダーとリージョンを指定してください。
-4. **「データ共有の作成」を選択**。
+2. Snowflakeアカウントの詳細を入力してください。Snowflake アカウント ID を確認するには、宛先アカウントで `SELECT CURRENT_ACCOUNT()` を実行します。
+3. CRR 共有をご利用の場合は、クラウドプロバイダーとリージョンを指定してください。
+4. \[**データ共有を作成**] を選択します。
 
 数分以内に、データ共有がSnowflakeインスタンスに表示されるはずです。共有からデータベースを作成して、テーブルを表示およびクエリできるようにします。データ共有を見るには、アカウント管理者である必要があることに注意してください。
 
@@ -60,20 +60,20 @@ Brazeアカウントでセキュアデータ共有を設定するには、次の
 
 ## 使用と視覚化
 
-データ共有がプロビジョニングされると、受信データ共有からデータベースを作成する必要があります。これにより、共有されたすべてのテーブルがSnowflakeインスタンスに表示され、インスタンスに保存されている他のデータと同様にクエリ可能になります。ただし、共有データは読み取り専用であり、照会のみ可能で、変更や削除は一切できません。
+データ共有のプロビジョニングが完了したら、受信するデータ共有からデータベースを作成する必要があります。これにより、共有されているすべてのテーブルが Snowflake インスタンスに表示され、インスタンスに保存されている他のデータと同様にクエリ可能になります。ただし共有データは読み取り専用であり、クエリのみ可能で、変更や削除は一切できないことにご注意ください。
 
-Currentsと同様に、Snowflake Secure Data Sharingを使用して次のことができます:
+Currents と同様に、Snowflake セキュアデータシェアリングを使用して次のことができます:。
 - 複雑なレポートを作成する
 - アトリビューション モデリングを実行する
 - 自社内での安全な共有
 - 生のイベントまたはユーザーデータをCRM（Salesforceなど）にマッピングする
 - さらに
 
-生のテーブルスキーマをここからダウンロードしてください。]\[schemas]
+\[生テーブルスキーマをここからダウンロードしてください。]\[schemas]
 
 ### ユーザー ID スキーマ
 
-ユーザーIDの命名規則に関するBrazeとSnowflakeの違いに注意してください。
+次に示す Braze と Snowflake でのユーザー ID の命名規則の違いに注意してください。
 
 | Brazeスキーマ | スノーフレークスキーマ | 説明 |
 | ----------- | ----------- | ----------- |
@@ -83,47 +83,47 @@ Currentsと同様に、Snowflake Secure Data Sharingを使用して次のこと
 
 ## 重要な情報と制限
 
-### 非互換変更と互換変更
+### 破壊的な変更と非破壊的な変更
 
 #### 非破壊的な変更
-非破壊的な変更はいつでも発生する可能性があり、一般的に追加の機能を提供します。非破壊的変更の例：
+非破壊的な変更はいつでも発生する可能性があり、一般的に追加の機能を提供します。非破壊的な変更の例には次のものがあります。
 - 新しいテーブルまたはビューの追加
 - 既存のテーブルまたはビューに列を追加する
 
 {% alert important %}
-新しい列は非破壊と見なされるため、Braze は `SELECT *` クエリを使用する代わりに、各クエリで関心のある列を明示的に列挙することを強くお勧めします。あるいは、列を明示的に名前付けするビューを作成し、それらのビューを直接テーブルの代わりにクエリすることを検討するかもしれません。
+新しい列の追加は非破壊的な変更と見なされるため、Braze では `SELECT *` クエリを使用する代わりに、各クエリで関心のある列を明示的に列挙することを強くお勧めします。あるいは、列を明示的に名前付けするビューを作成し、それらのビューを直接テーブルの代わりにクエリすることを検討するかもしれません。
 {% endalert %}
 
 #### 破壊的な変更
-可能な場合、破壊的変更は発表と移行期間を伴います。破壊的変更の例には次のようなものがあります:
+可能な場合には、破壊的な変更の前に通知を行い、移行期間を設けます。破壊的変更の例には次のようなものがあります:
 - テーブルまたはビューの削除
 - 既存のテーブルまたはビューから列を削除する
 - 既存の列の型またはnull許容性を変更する
 
-### Snowflakeリージョン
-Brazeは現在、すべてのユーザーレベルのデータをSnowflake AWS US East-1およびEU-Central（フランクフルト）リージョンにホストしています。これらの地域外のユーザーに対して、Braze は、Snowflake インフラストラクチャを任意の AWS、Azure、または GCP リージョンにホストしている共同顧客へのデータ共有を提供できます。
+### Snowflake のリージョン
+Braze は現在、すべてのユーザーレベルのデータを Snowflake AWS US East-1 および EU-Centra (フランクフルト) リージョンでホストしています。これらのリージョン外のユーザーの場合、Braze は、Snowflake インフラストラクチャを AWS、Azure、または GCP リージョンでホストしている共同の顧客にデータ共有を提供できます。
 
 ### データリテンション
 
 #### リテンションポリシー
-2年以上前のデータはすべてアーカイブされ、長期保存に移されます。アーカイブプロセスの一環として、すべてのイベントは匿名化され、個人を特定できる情報 (PII) の機密フィールドはすべて削除されます（これには、`properties` のようなオプションの PII フィールドも含まれます）。アーカイブされたデータには依然として`user_id`フィールドが含まれており、すべてのイベントデータにわたるユーザーごとの分析が可能です。
+2年以上前のデータはすべてアーカイブされ、長期保存に移されます。アーカイブプロセスの一環として、すべてのイベントは匿名化され、個人を特定できる情報 (PII) が含まれる機密フィールドはすべて削除されます (これには、`properties` のようなオプションの PII フィールドも含まれます)。アーカイブされたデータには依然として`user_id`フィールドが含まれており、すべてのイベントデータにわたるユーザーごとの分析が可能です。
 
 対応する`USERS_*_SHARED`ビューで各イベントの直近2年間のデータを照会できます。さらに、各イベントには、匿名化されたデータと非匿名化されたデータの両方を返すためにクエリを実行できる`USERS_*_SHARED_ALL`ビューが用意されています。
 
 #### 歴史的なデータ
-Snowflake における歴史的イベントデータのアーカイブは、2019年4月に遡ります。BrazeがSnowflakeにデータを保存し始めた最初の数ヶ月間に、製品の変更が行われ、そのデータの一部がわずかに異なって見えたり、いくつかのフィールドにnull値が含まれている可能性があります（この時点ではすべての利用可能なフィールドにデータを渡していなかったため）。2019年8月以前のデータを含む結果は、予想と少し異なる可能性があると考えるのが最善です。
+Snowflake では、2019年4月までの履歴イベントデータがアーカイブされています。BrazeがSnowflakeにデータを保存し始めた最初の数ヶ月間に、製品の変更が行われ、そのデータの一部がわずかに異なって見えたり、いくつかのフィールドにnull値が含まれている可能性があります（この時点ではすべての利用可能なフィールドにデータを渡していなかったため）。2019年8月以前のデータを含む結果は、予期される結果と多少異なる可能性があると想定しておくことが最適です。
 
 ### 一般データ保護規則（GDPR）準拠
-ほぼすべてのイベントレコードBrazeには、ユーザーの個人を特定できる情報（PII）を表すいくつかのフィールドが含まれています。一部のイベントには、メールアドレス、電話番号、デバイスID、言語、性別、および位置情報が含まれる場合があります。ユーザーの削除依頼がBrazeに送信された場合、これらのユーザーに属するイベントのPIIフィールドを無効化します。この方法では、イベントの歴史的記録を削除することはありませんが、今ではイベントが特定の個人に結びつけられることは決してありません。
+Braze に保管されているほぼすべてのイベントレコードには、ユーザーの個人を特定できる情報 (PII) を表すいくつかのフィールドが含まれています。一部のイベントには、メールアドレス、電話番号、デバイスID、言語、性別、および位置情報が含まれる場合があります。ユーザーの削除依頼がBrazeに送信された場合、これらのユーザーに属するイベントのPIIフィールドを無効化します。この方法では、イベントの履歴レコードは削除されませんが、イベントが特定の個人に結び付けられることは一切ありません。
 
 ### スピード、パフォーマンス、クエリのコスト
-クエリを実行するために使用するウェアハウスのサイズによって、データ上で実行されるクエリの速度、パフォーマンス、およびコストが決まります。場合によっては、分析のためにアクセスしているデータ量によって、クエリを成功させるためにより大きなウェアハウスサイズを使用する必要があるかもしれません。Snowflakeには、[ウェアハウスの概要](https://docs.snowflake.net/manuals/user-guide/warehouses-overview.html)や[ウェアハウスの考慮事項](https://docs.snowflake.net/manuals/user-guide/warehouses-considerations.html)など、どのサイズを使用するかを最適に判断する方法に関する優れたリソースが用意されています。
+データに対して実行されるクエリの速度、パフォーマンス、およびコストは、データのクエリに使用するウェアハウスのサイズによって決まります。場合によっては、分析のためにアクセスしているデータ量によって、クエリを成功させるためにより大きなウェアハウスサイズを使用する必要があるかもしれません。Snowflakeには、[ウェアハウスの概要](https://docs.snowflake.net/manuals/user-guide/warehouses-overview.html)や[ウェアハウスの考慮事項](https://docs.snowflake.net/manuals/user-guide/warehouses-considerations.html)など、どのサイズを使用するかを最適に判断する方法に関する優れたリソースが用意されています。
 
 ## Braze Benchmarks
 
-ベンチマーク、[Brazeによって構築されたデータツール](https://www.braze.com/perspectives/benchmarks)は、Brazeの見込み客と顧客が自社の指標をBrazeの業界ベンチマークと比較することで、業界のトッププレーヤーとどのように比較されるかを確認できるようにします。
+Benchmarks は [Braze によって構築されたデータツール](https://www.braze.com/perspectives/benchmarks)であり、Braze の見込み客と顧客は Benchmarks を使用して自社の指標を Braze の業界ベンチマークと比較して、業界上位の企業との比較を確認できます。
 
-初期産業には以下が含まれます：
+初期設定の業界には以下のものがあります。
 - 配達サービス
 - e コマース
 - 教育
@@ -144,4 +144,4 @@ Snowflake における歴史的イベントデータのアーカイブは、2019
 
 [SQ]: {{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/sample_queries/
 [ETL]: {{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/etl_pipline_setup/
-スキーマ]: {% image_buster /assets/download_file/data-sharing-raw-table-schemas.txt %}
+\[schemas]: {% image_buster /assets/download_file/data-sharing-raw-table-schemas.txt %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention.md
index 51c2bb65c3e..a359afd8c2f 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention.md
@@ -1,15 +1,15 @@
 ---
 nav_title: "データ保持"
-article_title: スノーフレークのデータ保持
+article_title: Snowflake データリテンション
 page_order: 3
 description: "このページでは、Brazeのリテンションポリシーが適用されている場合に、フルイベントデータを保持する方法について説明する。"
 page_type: partner
 search_tag: Partner
 ---
 
-# スノーフレークのデータ保持
+# Snowflake データリテンション
 
-> Brazeは、2年以上前のすべてのイベントデータから個人を特定できる情報（PII）を削除し、匿名化する。Snowflakeデータ共有を使用する場合、保持ポリシーが適用される前に、Snowflakeアカウントにコピーを保存することで、完全なイベントデータを環境に保持することを選択することができる。
+> Braze は、2年以上経過しているすべてのイベントデータを匿名化、つまり個人を特定できる情報 (PII) を削除します。Snowflake データシェアリングを使用する場合、完全なイベントデータをご使用の環境に保持するには、リテンションポリシーが適用される前に Snowflake アカウントにコピーを保存します。
 
 このページでは、匿名化されていないデータを保持する2つの方法を紹介する： 
 
@@ -17,7 +17,7 @@ search_tag: Partner
 - ステージにデータをアンロードする
 
 {% alert warning %}
-Brazeは、[データ保護テクニカルアシスタンスに]({{site.baseurl}}/dp-technical-assistance/)記載されているとおり、Brazeから削除されたユーザーのイベントデータを自動的に匿名化する。共有データベースの外部にコピーされたデータは、Brazeがもはや管理していないため、このプロセスには含まれない。
+「[データ保護技術支援]({{site.baseurl}}/dp-technical-assistance/)」で説明されているように、Braze は、Braze から削除されたユーザーのイベントデータを自動的に匿名化します。共有データベースの外部にコピーされたデータは、Brazeがもはや管理していないため、このプロセスには含まれない。
 {% endalert %}
 
 ## すべてのデータを別のSnowflakeデータベースにコピーする
@@ -123,12 +123,12 @@ $$;
 {% endraw %}
 
 {: start="2"}
-2\.Snowflakeアカウントで以下のコマンドのいずれかを実行し、プロシージャを実行する。
+2\.Snowflake アカウントで以下のコマンドのいずれかを実行して、プロシージャーを実行します。
 
 {% tabs %}
 {% tab デフォルト %}
 
-デフォルトでは、すべての`USERS_*` イベントタイプについて、2年以上前のデータをバックアップする。 
+デフォルトでは、すべての `USERS_*` イベントタイプについて、2年以上経過しているデータがバックアップされます。 
 
 {% raw %}
 ```sql
@@ -141,7 +141,7 @@ CALL COPY_BRAZE_SHARE('SOURCE_DB', 'SOURCE_SCHEMA', 'DEST_DB', 'DEST_SCHEMA')
 {% endtab %}
 {% tab フィルター付き %}
 
-バックアップする年齢データを選択するためにフィルタを指定し、選択したイベント・テーブルのみをバックアップするためにテーブル名フィルタを指定する。 
+バックアップ対象の古いデータを選択するフィルターを指定し、選択されるイベントテーブルのみをバックアップするためのテーブル名フィルターを指定します。 
 
 {% raw %}
 ```sql
@@ -155,14 +155,14 @@ CALL COPY_BRAZE_SHARE('SOURCE_DB', 'SOURCE_SCHEMA', 'DEST_DB', 'DEST_SCHEMA', DA
 {% endtabs %}
 
 {% alert note %}
-このプロシージャは最新の`SF_CREATED_AT` をチェックし、それより新しいデータのみをバックアップするため、プロシージャを繰り返し実行しても重複レコードは作成されない。
+このプロシージャーは最新の `SF_CREATED_AT` をチェックし、それより新しいデータのみをバックアップするので、このプロシージャーを繰り返し実行しても、重複するレコードは作成されません。
 {% endalert %}
 
 ## ステージにデータをアンロードする
 
 共有`BRAZE_RAW_EVENTS` スキーマからステージにデータをアンロードすることで、匿名化されていないデータを保持することができる。そのためには、以下の手順に従ってほしい：
 
-1. `UNLOAD_BRAZE_SHARE` 、Brazeが共有する全データを指定したステージにコピーするための手続きを作成する。
+1. プロシージャー `UNLOAD_BRAZE_SHARE` を作成します。これは、Braze が共有するすべてのデータを、指定したステージにコピーする場合に使用されるプロシージャーです。
 
 {% raw %}
 ```sql
@@ -235,12 +235,12 @@ $$;
 {% endraw %}
 
 {: start="2"}
-2\.以下のいずれかのコマンドを実行し、プロシージャを実行する。 
+2\.以下のコマンドのいずれかを実行して、プロシージャーを実行します。 
 
 {% tabs %}
 {% tab デフォルト %}
 
-デフォルトでは、`USERS_` 接頭辞を持つすべてのテーブルをコピーする。
+デフォルトでは、`USERS_` 接頭辞を持つすべてのテーブルがコピーされます。
 
 {% raw %}
 ```sql
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/etl_pipline_setup.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/etl_pipline_setup.md
index 539012621ae..0d67860bb82 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/etl_pipline_setup.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/etl_pipline_setup.md
@@ -2,7 +2,7 @@
 nav_title: "ETLイベントパイプラインの設定"
 article_title: Snowflake ETLイベントパイプラインの設定
 page_order: 2
-description: "このパートナページでは、独自のクエリを設定するときに参照する電子メールクリッククエリのセットアップ例を提供します。"
+description: "このパートナーページではメールクリッククエリの設定例を示します。これは、独自のクエリを設定するときに参照します。"
 page_type: partner
 search_tag: Partner
 
@@ -10,13 +10,13 @@ search_tag: Partner
 
 # ETLイベントパイプラインの設定
 
-> このパートナページでは、独自のクエリーを設定するときに参照するメールクリッククエリーのサンプルセットアップを提供します。
+> このパートナーページではメールクリッククエリの設定例を示します。これは、独自のクエリを設定するときに参照します。
 
-このメールクリッククエリーを使用すると、インターアクションs とBraze キャンペーンs およびキャンバス内の固有のメールs を分析できます。
+このメールクリッククエリを使用して、Braze キャンペーンおよびキャンバス内の特定のメールでのインタラクションを分析できます。
 
 ## このクエリを設定する
 
-`BRAZE` のデータベースを作成し、`BRAZE_CURRENTS;` に存在しない場合はデータベースを作成します。
+`BRAZE` のデータベースを作成し、次に `BRAZE_CURRENTS;` のデータベースが存在しない場合はそのデータベースを作成します。
 
 ```sql
 use schema BRAZE_CURRENTS.public;
@@ -96,7 +96,7 @@ show pipes;
 
 ## このクエリの例を使用して、さらに実行します
 
-前述のコマンドの出力から `notification_channel` をコピーし、S3 バケット通知s を設定するときに使用します。
+前述のコマンドの出力から `notification_channel` をコピーし、S3 バケット通知を設定するときに使用します。
 
 指定された以下のパイプ名について、S3 からSnowflake に手動で同期します。
 ```sql
@@ -105,7 +105,7 @@ ALTER PIPE
   refresh ;
 ```
 
-配管ステータスを確認します。これにより、S3 からSnowflake にメッセージがいつ転送されたかが表示されます。
+S3 から Snowflake にメッセージが転送されたタイミングを示すパイプステータスを確認します。
 ```sql
 SELECT
   SYSTEM$PIPE_STATUS(
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/faqs.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/faqs.md
index ca4d6a2b22e..7679a5c31d3 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/faqs.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/faqs.md
@@ -1,6 +1,6 @@
 ---
 nav_title: よくある質問
-article_title: スノーフレーク・データ共有FAQ
+article_title: Snowflake データシェアリングに関するよくある質問
 page_order: 4
 page_type: FAQ
 description: "この記事では、Snowflakeのデータ共有に関するよくある質問に答える。"
@@ -9,22 +9,22 @@ description: "この記事では、Snowflakeのデータ共有に関するよく
 
 # よくある質問
 
-### スノーフレークのデータ共有によってPIIデータを難読化することは可能か？
-今のところ、それはサポートされていない。
+### Snowflake データシェアリングを介して PII データを難読化することは可能ですか?
+現時点ではこの機能はサポートされていません。
 
 ### 同じ地域のデータ共有が必要なのか、地域をまたぐデータ共有が必要なのか？
 以下のシナリオでは、同じ地域のデータ共有を使用する：
-- SnowflakeアカウントはUS-EAST-1（AWS）にあり、Brazeダッシュボードのリージョンは米国にある。
-- スノーフレークのリージョンはEU-CENTRAL-1にあり、ブレイズダッシュボードのリージョンはEUにある。
+- Snowflake アカウントは US-EAST-1 (AWS) にあり、Braze ダッシュボードのリージョンは米国内にある。
+- Snowflake アカウントは EU-CENTRAL-1 にあり、Braze ダッシュボードのリージョンは EU 内にある。
 
-そうでなければ、地域間のデータ共有を利用する。 
+それ以外の場合はクロスリージョンのデータ共有を使用します。 
 
-### 新しいSnowflakeアカウントに変更した場合、データ共有はどうすればいいのか？
-古いSnowflakeアカウントに関連付けられている古いデータ共有を削除し、新しいアカウント用に新しい共有を作成することができる。過去のデータはすべて新しいシェアで利用できる。 
+### 新しい Snowflake アカウントに切り替える場合、自分のデータ共有をどのように扱えばよいですか?
+古い Snowflake アカウントに関連付けられている古いデータ共有を削除してから、新しいアカウント用に新しい共有を作成できます。履歴データはすべて新しい共有で利用可能になります。 
 
 ### 自分のデータシェアにデータが表示されないのはなぜか？
-データ共有の作成時に間違ったSnowflakeアカウントIDを使用した可能性がある。データ共有ダッシュボードのアカウントIDは、Snowflakeアカウントからの`CURRENT_ACCOUNT()` の出力と一致しなければならない。
+データ共有の作成時に間違ったSnowflakeアカウントIDを使用した可能性がある。データ共有ダッシュボードのアカウント ID が、Snowflake アカウントの `CURRENT_ACCOUNT()`の 出力と一致している必要があります。
 
-あなたのシェアが地域をまたぐ場合、データはすぐには入手できないかもしれない。データ量にもよるが、データがあなたの地域に同期されるまで数時間かかることもある。
+共有がリージョンをまたいでいる場合、データがすぐに利用可能にならない可能性があります。データの量によっては、リージョンとのデータ同期に数時間かかることがあります。
 
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/sample_queries.md b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/sample_queries.md
index 6dc33502b9b..2f3559d41b7 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/sample_queries.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/data_warehouses/snowflake/sample_queries.md
@@ -10,14 +10,14 @@ search_tag: Partner
 
 # サンプルクエリ
 
-> このパートナーページでは、クエリを設定する際に参照するためのいくつかのサンプルクエリを提供しています。
+> このパートナーページでは、クエリを設定する際に参照するための考えられるユースケースのサンプルクエリを紹介します。
 
 {% tabs %}
-{% tab 時間でフィルター%}
+{% tab 時間でのフィルタリング%}
 
 一般的なクエリは、時間でイベントをフィルターすることです。
 
-発生時刻でそれらをフィルターできます。イベントテーブルは`time`によってクラスタリングされるため、`time`によるフィルタリングが最適です:
+発生時刻でイベントをフィルタリングできます。イベントテーブルは`time`によってクラスタリングされるため、`time`によるフィルタリングが最適です:
 ```sql
 -- find custom events that occurred after 04/15/2019 @ 7:02pm (UTC) i.e., timestamp=1555354920
 SELECT *
@@ -25,7 +25,7 @@ FROM users_behaviors_customevent_shared
 WHERE time > 1555354920
 LIMIT 10;
 ```
-また、`sf_created_at`を使用して、Snowflakeデータウェアハウスに保存された時刻でイベントをフィルターすることもできます。`sf_created_at`と`time`は同じではありませんが、通常は近いので、このクエリは同様のパフォーマンス特性を持つはずです。
+また、`sf_created_at` を使用して、イベントが Snowflake データウェアハウスで永続化された時刻に基づいてイベントをフィルタリングすることもできます。`sf_created_at` と `time` は同じではありませんが通常は類似しているため、このクエリは同様のパフォーマンス特性を持ちます。
 ```sql
 -- find custom events that arrived in Snowflake after time 04/15/2019 @ 7:02pm (UTC)
 SELECT *
@@ -56,7 +56,7 @@ qualify row_number() over (partition by event.id ORDER BY ccs.time DESC) = 1;
 - Snowflakeの[window](https://docs.snowflake.com/en/sql-reference/functions-analytic.html)機能がここで使用されています。
 - 左結合により、キャンペーンに関連しないイベントも含まれるようになります。
 - イベントに`campaign_id`が表示されるがキャンペーン名が表示されない場合、キャンペーンがデータ共有が製品として存在する前の名前で作成された可能性があります。
-- 同様のクエリを使用して、`CHANGELOGS_CANVAS_SHARED`テーブルと結合することでキャンバス名を確認できます。
+- 代わりに `CHANGELOGS_CANVAS_SHARED` テーブルと結合することで、同様のクエリを使用してキャンバス名を確認できます。
 
 キャンペーンとキャンバスの両方の名前を表示したい場合は、次のサブクエリを使用する必要があるかもしれません:
 ```sql
@@ -75,7 +75,7 @@ qualify row_number() over (partition by campaign_join.event_id ORDER BY canvas.t
 {% endtab %}
 {% tab プッシュファネル %}
 
-このプッシュファネルクエリを使用して、プッシュ送信の生データを集計し、配信の生データを通じて、開封の生データを通じて集計できます。このクエリは、各生データが通常別々のテーブルを持つため、すべてのテーブルがどのように結合されるべきかを示しています。
+このプッシュファネルクエリを使用して、プッシュ送信の生イベントデータ、配信の生イベントデータ、開封の生イベントデータの順に集約できます。通常、生イベントごとに個別のテーブルがあるため、このクエリはすべてのテーブルを結合する方法を示します。
 
 ```sql
 
@@ -102,10 +102,10 @@ LIMIT 500;
 ```
 
 {% endtab %}
-{% tab メール Cadence %}
-この日々のメールメッセージングのケイデンスクエリを使用して、ユーザーが受信するメール間の時間を分析できます。
+{% tab メールケイデンス %}
+日次メールメッセージングケイデンスクエリを使用して、ユーザーのメール受信間隔の時間を分析できます。
 
-例えば、ユーザーが1日に2通のメールを受信した場合、それは`0 "days since last received"`に該当します。もし彼らが月曜日に1通のメールを受け取り、火曜日に1通のメールを受け取った場合、彼らは`1 "days since last received"`コホートに入るでしょう。
+例えば、ユーザーが1日に2通のメールを受信した場合、それは`0 "days since last received"`に該当します。月曜日と火曜日にそれぞれメールを1通ずつ受信したユーザーは、`1 "days since last received"` コホートに分類されます。
 
 ```sql
 WITH email_messaging_cadence AS (WITH deliveries AS
@@ -145,14 +145,14 @@ ORDER BY 1
 LIMIT 500;
 ```
 {% endtab %}
-{% tab ユニークメールクリック数 %}
+{% tab ユニークなメールクリック数 %}
 
-指定された時間枠内で一意のメールクリックを分析するために、この一意のメールクリッククエリを使用できます。これを計算するアルゴリズムは次のとおりです:
-  1. キー（`app_group_id`、`message_variation_id`、`dispatch_id`、`email_address`）でイベントを分割します。
+このユニークなメールクリック数のクエリを使用して、指定された時間枠内でのユニークなメールクリックを分析できます。これを計算するアルゴリズムは次のとおりです:
+  1. キー (`app_group_id`、`message_variation_id`、`dispatch_id`、`email_address`) でイベントを分割します。
   2. 各パーティション内で、イベントを時間順に並べ、最初のイベントは常に一意のイベントです。
-  3. その後のすべてのイベントについて、それが前のイベントから7日以上経過して発生した場合、ユニークなイベントと見なされます。
+  3. 後続のすべてのイベントでは、前のイベントから7日以上経過して発生したイベントは、ユニークなイベントと見なされます。
   
-これを達成するために、Snowflakeの[ウィンドウ関数](https://docs.snowflake.com/en/sql-reference/functions-analytic.html)を使用できます。次のクエリは、過去365日間のすべてのメールクリックを示し、`is_unique`列でどのイベントがユニークであるかを示します。
+これを達成するために、Snowflake の[ウィンドウ関数](https://docs.snowflake.com/en/sql-reference/functions-analytic.html)を使用できます。次のクエリは、過去365日間のすべてのメールクリックを示し、`is_unique` 列にどのイベントがユニークであるかを示します。
   
 ```sql
 SELECT id, app_group_id, message_variation_api_id, dispatch_id, email_address, time,
@@ -179,7 +179,7 @@ WHERE
   AND time > DATE_PART('EPOCH_SECOND', TO_TIMESTAMP(CURRENT_TIMESTAMP())) - 365*24*3600
 QUALIFY is_unique = true;
 ```
-メールアドレスごとにグループ化されたユニークなイベント数をさらに確認するには:
+メールアドレスごとにグループ化されたユニークイベントの数をさらに表示するには、:次のようにします。
 ```sql
 WITH unique_events AS(
   SELECT id, app_group_id, message_variation_api_id, dispatch_id, email_address, time,
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/leads_capture.md b/_lang/ja/_partners/data_and_infrastructure_agility/leads_capture.md
index 7c41efafc5e..64c255b026c 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/leads_capture.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/leads_capture.md
@@ -1,6 +1,6 @@
 ---
 nav_title: リードの獲得
-article_title: リード・キャプチャー・パートナー
+article_title: リード獲得のパートナー
 page_order: 7.5
 
 page_type: landing
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier.md b/_lang/ja/_partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier.md
index 52d32318733..1bf6089e4b1 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier.md
@@ -1,7 +1,7 @@
 ---
 nav_title: ZapierによるFaceBookのリード広告
 article_title: ZapierによるFaceBookのリード広告
-description: "このレファレンス記事では、BrazeとFac eBookリード広告の統合をZapierを介して概説し、Fac eBookからBrazeへのリードデータの転送を自動化し、リアルタイムのエンゲージメントとパーソナライズされたのフォローアップアクションsを可能にします。"
+description: "このリファレンス記事では、Zapierを介した Braze と Facebook リード獲得広告との統合による Facebook から Brazeへのリードデータの転送の自動化について説明します。これにより、リアルタイムのエンゲージメントとパーソナライズされたフォローアップアクションが可能になります。"
 alias: /partners/facebook_via_zapier/
 page_type: partner
 search_tag: Partner
@@ -10,47 +10,47 @@ search_tag: Partner
 
 # ZapierインテグレーションによるFaceBookのリード広告
 
-> Fac eBook リードアドインテグレーションでは、<a href="https://zapier.com/" target="_blank">Zapier</a> を使用して、リードをFac eBookからBraze に読み込んで、リードがキャプチャされたときにカスタムイベントを追跡できます。 
+> <a href="https://zapier.com/" target="_blank">Zapier</a> を介した Facebook リード獲得広告への統合により、Facebook から Braze にリードをインポートし、リードがキャプチャされたときにカスタムイベントを追跡することができます。 
 
-Fac eBookリード広告は、企業がFac eBookで直接的にリード情報を収集できる広告形式です。これらの広告は、リード生成プロセスを簡単かつシームレスにするように設計されています。ZapierインテグレーションとBrazeを活用することで、Fac eBookからBrazeへのリードデータの転送を自動化し、リアルタイムのエンゲージメントとパーソナライズされたのフォローアップアクションを可能にします。 
+Facebook Lead Ads は、企業が Facebook で直接リード情報を収集できる広告フォーマットです。リード獲得広告は、リード生成プロセスを簡単かつシームレスにするように設計されています。Zapier 統合と Braze を利用することで、Facebook から Braze へのリードデータの転送を自動化でき、リアルタイムのエンゲージメントとパーソナライズされたフォローアップアクションが可能になります。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| Zapier勘定 | この提携の前進タグeを考慮するには、Zapierな考慮が必要である。この統合では、<a href="https://zapier.com/app/pricing/" target="_blank">プレミアムZapier アプリs</a>を使用する必要があるため、Zapierプランがプレミアムアプリsにアクセスできることを確認します。 |
-| <a href="https://www.facebook.com/business/help/540596413257598?id=735435806665862/" target="_blank">Fac eBook リードアクセス</a> | Fac eBook リードアクセスは、Braze で使用する予定の広告アカウントごとに必要です。 |
-| <a href="https://www.facebook.com/business/help/1710077379203657?id=180505742745347" target="_blank">ファックeBook事業部長</a> | この統合の一環として、Fac eBookビジネスマネージャを使用して、ブランドのFac eBookアセット(広告アカウント、ページ、アプリなど)を管理します。 |
-| <a href="https://www.facebook.com/business/help/195296697183682?id=829106167281625/" target="_blank">FaceBookの広告アカウント</a> | あなたのブランドの事業マネージャーと結びついた、有効なFaceBookの広告アカウントが必要になります。<br><br>「&quot」、「Ad accounts&quot の管理」、「Braze」で使用する予定の広告アカウントごとの権限、および広告アカウントの条件を承諾していることを確認します。 |
-| <a href="https://www.facebook.com/business/help/183277585892925?id=420299598837059/" target="_blank">ファクスeBook画面</a> | 自社の事業マネージャーに合わせて、能動的なFac eBookページが必要となる。<br><br>Braze で使用するFac eBook ページごとに、"Manage Pages" 権限があることを確認します。 |
+| Zapierアカウント | このパートナーシップを活用するには、Zapier アカウントが必要です。この統合には、<a href="https://zapier.com/app/pricing/" target="_blank">プレミアム Zapier アプリ</a>を使用する必要があります。そのため、ご利用の Zapier プランでプレミアムアプリを使用できることを確認してください。 |
+| <a href="https://www.facebook.com/business/help/540596413257598?id=735435806665862/" target="_blank">Facebook リードアクセス</a> | Braze で使用する予定の各広告アカウンには、Facebook リードアクセスが必要です。 |
+| <a href="https://www.facebook.com/business/help/1710077379203657?id=180505742745347" target="_blank">Facebook Business Manager</a> | この統合の一環として、Facebook Business Manager を使用します。Facebook Business Manager は、ブランドの Facebook アセット (広告アカウント、ページ、アプリなど) を管理するための一元的なツールです。 |
+| <a href="https://www.facebook.com/business/help/195296697183682?id=829106167281625/" target="_blank">Facebook 広告アカウント</a> | あなたのブランドの事業マネージャーと結びついた、有効なFaceBookの広告アカウントが必要になります。<br><br>Braze で使用する予定の各広告アカウントに対する「Manage ad accounts」権限を持っており、広告アカウントの利用規約に同意していることを確認します。 |
+| <a href="https://www.facebook.com/business/help/183277585892925?id=420299598837059/" target="_blank">Facebook ページ</a> | 自社のブランドのビジネスマネージャーに関連付けられているアクティブな Facebook ページが必要になります。<br><br>Braze で使用する Facebook ページごとに、「Manage Pages」権限があることを確認します。 |
 | Braze REST エンドポイント | [ REST エンドポイント URL][1] を確認してください。API エンドポイントは、Brazeインスタンスのダッシュボード URL と一致します。<br><br> たとえば、ダッシュボード URL が`https://dashboard-03.braze.com` の場合、エンドポイントは`dashboard-03` になります。 |
-| Braze REST API キー | `users.track` 権限を持つBraze REST API キーがあることを確認します。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キーがあることを確認します。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:インスタントフォームでリード広告キャンペーンを作成する
 
-Fac eBook Ads Manager から、<a href="https://www.facebook.com/business/help/397336587121938?id=735435806665862&helpref=uf_permalink" target="_blank">Fac eBook リードキャンペーンとFac eBook リードアドフォーム</a> を作成します。
+Facebook 広告マネージャから、<a href="https://www.facebook.com/business/help/397336587121938?id=735435806665862&helpref=uf_permalink" target="_blank">Facebook リードキャンペーンと Facebook リード獲得広告フォーム</a>を作成します。
 
-[`/users/track`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)へのリクエスト時に、メールの住所または電話番号を使用して、ユーザープロファイルを更新または作成できます。このため、リード広告フォームに****メール**または**phone**の**連絡先フィールド**を含めてください。名または姓を収集する場合は、フルネームではなくフォームで別々に収集します。
+[`/users/track`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)へのリクエスト時に、メールの住所または電話番号を使用して、ユーザープロファイルを更新または作成できます。このため、リード広告フォームに**メール**または**phone**の**連絡先フィールド**を含めてください。名または姓を収集する場合は、フルネームではなくフォームで別々に収集します。
 
-### ステップ2:Fac eBook をZapier に接続する 
+### ステップ2:Facebook アカウントを Zapier に接続する 
 
 #### ステップ 2a: Zapierで接続方法を選択する
 
-Zapierで、**アプリ s** に移動し、使用可能なFac eBook アプリ s を検索します。**Fac eBook リード広告**または**Fac eBook リード広告(ビジネス管理者向け)**を選択します。
+Zapier で \[**Apps**] に移動して利用可能なFacebook アプリを検索します。\[**Facebook Lead Ads**] または \[**Facebook Lead Ads (for Business admins)**] のいずれかを選択します。
 
-Fac eBook アカウントを Zapier に接続する方法の詳細については、以下を参照してください。
+Facebook アカウントを Zapier に接続するこの2つの方法の詳細については、以下を参照してください。
 
-- <a href="https://help.zapier.com/hc/en-us/articles/8496123584781-How-to-get-started-with-Facebook-Lead-Ads-for-Business-Admins-on-Zapier#h_01HC9VZFZG0GR2KRYM5EQJN329" target="_blank">Fac eBook リードアド(企業管理者向け)</a>
-- <a href="https://help.zapier.com/hc/en-us/articles/8496061306253#h_01HC9VMZ2XP0017AR6SE7S30JG" target="_blank">ファック・eBookのリード広告</a>
+- <a href="https://help.zapier.com/hc/en-us/articles/8496123584781-How-to-get-started-with-Facebook-Lead-Ads-for-Business-Admins-on-Zapier#h_01HC9VZFZG0GR2KRYM5EQJN329" target="_blank">Facebook Lead Ads (for Business Admins)</a>
+- <a href="https://help.zapier.com/hc/en-us/articles/8496061306253#h_01HC9VMZ2XP0017AR6SE7S30JG" target="_blank">Facebook Lead Ads</a>
 
 ![][2]{: style="max-width:80%;"}
 
-#### ステップ 2b: Fac eBook Business Manager へのZapierの追加
+#### ステップ 2b: Facebook Business Manager でリードアクセスに Zapier を追加する
 
-Fac eBook ビジネスマネージャの左側のメニューで、**Integrations** > **Leads Access** に移動します。Fac eBook ページを選択し、**CRM s** をクリックします。CRMタブで、**CRMs**を割り当て、**Zapier**を追加します。
+Facebook Business Manager で、左側のメニューの \[**Integrations**] > \[**Leads Access**] に移動します。Facebook ページを選択し、\[**CRMs**] をクリックします。\[CRM] タブで、\[**Assign CRMs**] を選択し、\[**Zapier**] を追加します。
 
 ![][3]{: style="max-width:80%;"}
 
@@ -60,7 +60,7 @@ CRMインテグレーションとしてZapierを割り当てるステップに
 
 #### ステップ3a:トリガーの作成 
 
-Fac eBook アカウントを接続したら、Zap の作成に進むことができます。**Trigger**の場合は、ステップ 2 からお好みの**Fac eBook リードアド**または**Fac eBook リードアド(ビジネス管理者向け)**を選択します。 
+Facebook アカウントを接続したら、Zap の作成に進むことができます。**トリガー**の場合は、ステップ2での選択に基づいて、\[**Facebook Lead Ads**] または \[**Facebook Lead Ads (for Business Admins)**] を選択します。 
 
 ![][4]{: style="max-width:80%;"}
 
@@ -68,11 +68,11 @@ Fac eBook アカウントを接続したら、Zap の作成に進むことがで
 
 ![][5]{: style="max-width:80%;"}
 
-Fac eBookを選択し、**Continue**を選択します。 
+Facebook アカウントを選択し、\[**Continue**] を選択します。 
 
 ![][6]{: style="max-width:80%;"}
 
-以前に作成したFac eBook ページとインスタントフォームを選択し、**Continue** を選択します。
+以前に作成した Facebook ページとインスタントフォームを選択し、\[**Continue**] を選択します。
 
 ![][7]{: style="max-width:80%;"}
 
@@ -84,7 +84,7 @@ Fac eBookを選択し、**Continue**を選択します。
 
 ![][8]{: style="max-width:80%;"}
 
-最後に、フィールド s を有料読み込むに挿入して、カスタムリクエストを設定します。次のコード スニペットは、サンプルの給与読み込むを示しています。 
+最後に、ペイロードにフィールドを挿入してカスタムリクエストを設定します。次のコードスニペットは、ペイロードの例を示しています。 
 
 ```
 {
@@ -122,21 +122,21 @@ Fac eBookを選択し、**Continue**を選択します。
 
 Webhookを設定した後、**Continue とtest** を選択します。テストが成功した場合は、Zap を公開できます。
 
-### ステップ4:Fac eBook リードアドザップのテスト
+### ステップ4:Facebook Lead Ads Zap をテストする
 
-このエンドツーエンドのをテストするには、Fac eBook 開発者コンソールでFac のリードアドテストツールを使用します。詳細については、<a href="https://developers.facebook.com/docs/marketing-api/guides/lead-ads/testing-troubleshooting/" target="_blank">テストとトラブルシューティング</a>を参照してください。
+このエンドツーエンドをテストするには、Facebook Developer Console で Facebook の Leads Ads Testing Tool を使用します。詳細については、<a href="https://developers.facebook.com/docs/marketing-api/guides/lead-ads/testing-troubleshooting/" target="_blank">テストとトラブルシューティング</a>を参照してください。
 
 ## ユーザー識別管理
 
-このインテグレーションでは、[`/users/track`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/#example-request-for-updating-a-user-profile-by-phone-number)をメールしてFaceBookリードを属性できます。
+この統合により、[`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/#example-request-for-updating-a-user-profile-by-phone-number)からのメールに基づいて Facebook リードを紐づけることができます。
 
-* メールが既存のユーザープロファイルと一致した場合、Braze はFac eBook リードデータでプロファイルを更新します。
-* 同じメールを持つ複数のユーザープロファイルs がある場合、Braze は更新s の外部ID を持つ最後の更新d プロファイルに優先順位を付けます。
-* 外部ID が存在しない場合、Braze は、一致するメールを持つ最新の更新d プロファイルを優先します。
-* 指定されたプロファイルがメールと共に存在しない場合、Brazeは新しいプロファイルを作成し、新しい別名ユーザープロファイルが作成されます。新しく作成された別名ユーザープロファイルs を識別するには、[`/users/identify`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/) を使用します。
+* メールが既存の1つのユーザープロファイルと一致する場合、Braze は Facebook リードデータを使用してそのプロファイルを更新します。
+* 同じメールが設定されているユーザープロファイルが複数ある場合、Braze は更新時に、external ID を持つ最新の更新済みプロファイルを優先します。
+* external ID が存在しない場合、Braze は、一致するメールを持つ最新の更新済みプロファイルを優先します。
+* 指定されたメールを持つプロファイルが存在しない場合、Braze は新しいプロファイルを作成し、新しいエイリアスユーザープロファイルが作成されます。新しく作成された別名ユーザープロファイルs を識別するには、[`/users/identify`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/) を使用します。
 
 {% alert note %}
-これらのフィールドが利用可能で、インテグレーションに使用したいプライマリ識別子がある場合は、Brazeへのリクエストの一部として電話番号または外部ID を使用することもできます。これを行うには、[`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) に示すように、リクエストの支払い読み込むを変更します。
+これらのフィールドが利用可能で、インテグレーションに使用したいプライマリ識別子がある場合は、Brazeへのリクエストの一部として電話番号または外部ID を使用することもできます。これを行うには、[`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)に示すようにリクエストペイロードを変更します。
 {% endalert %}
 
 ## トラブルシューティング
@@ -145,28 +145,28 @@ Webhookを設定した後、**Continue とtest** を選択します。テスト
 この統合を使用するには、プレミアムアプリs をサポートする<a href="https://zapier.com/app/pricing/" target="_blank">Zapierプラン</a> が必要です。
 {% enddetails %}
 
-{% details ファクスeBookがBrazeに同期しないのはなぜですか? %}
-1. ファックeBookページ、広告アカウント、およびリードアクセスに管理者がアクセスできることを確認します。次に、Zapier でアカウントを再接続します。
-2. Fac eBook で作成したインスタントフォームが、トリガーステップで選択したフォームにマッピングされていることを確認します。 
-3. **Fac eBook Business Manager**> **Integrations**> **Lead Access**に移動して、リードアクセスにZapierを割り当てたことを確認します。
+{% details Facebook リードが Braze に同期されないのはなぜですか? %}
+1. 管理者が Facebook ページ、広告アカウント、リードアクセスにアクセスできることを確認します。次に、Zapier でアカウントを再接続します。
+2. Facebook で作成したインスタントフォームが、トリガーステップで選択したフォームにマッピングされていることを確認します。 
+3. \[**Facebook Business Manager**] > \[**Integrations**] > \[**Lead Access**] に移動して、Zapier を Leads Access に割り当てていることを確認します。
 {% enddetails %}
 
-{% details なぜ同じメールの重複ユーザープロファイルsを見ているのですか? %}
+{% details 同じメールが設定されている重複ユーザープロファイルが表示されるのはなぜですか? %}
 [ユーザープロファイルライフサイクル]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle#user-profile-lifecycle) に基づいて、Braze でユーザープロファイルs を作成および管理する独自の方法があります。
 
-内部の処理に応じて、またBraze 内で顧客 s を作成するトリガーを作成しているときに、統合によって作成されるユーザープロファイルの競合と、システムからユーザーが作成されるときに、重複するユーザープロファイル s が発生することがあります。[マージユーザープロファイルs]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/)をBrazeで使用できます。
+内部プロセスによっては、Braze 内での顧客の作成をトリガーするときに、統合によって作成されるユーザープロファイルの競合状態と、ユーザーがシステムから作成された時点に応じて、重複するユーザープロファイルが発生することがあります。Braze では[ユーザープロファイルをマージできます]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/)。
 {% enddetails %}
 
-{% details Zapier口座を持っていません。Fac eBookのリード広告webhookをBrazeにトリガーするにはどうすればよいですか? %}
-Zapier を使用せず、Zapier を使用する予定がない場合は、Fac eBook からBraze にインテグレーションを構築できます。詳細については、<a href="https://developers.facebook.com/docs/marketing-api/guides/lead-ads/" target="_blank">リード広告ドキュメント</a>を参照してください。
+{% details Zapier アカウントを持っていません。Facebook Lead Ads Webhook を Braze にトリガーするにはどうすればよいですか? %}
+Zapier を使用しておらず、Zapier を使用する予定がない場合は、Facebook から Braze への直接の統合を構築できます。詳細については、<a href="https://developers.facebook.com/docs/marketing-api/guides/lead-ads/" target="_blank">リード獲得広告のドキュメント</a>を参照してください。
 
-Fac eBookからリードを取得するには、<a href="https://developers.facebook.com/docs/marketing-api/guides/lead-ads/retrieving#webhooks" target="_blank">webhook</a> を使用します。ファクトeBookのwebhookを始めるには、<a href="https://developers.facebook.com/docs/graph-api/webhooks/getting-started" target="_blank">webhook ドキュメント</a>を参照してください。
+Facebook からリードを取得するには、<a href="https://developers.facebook.com/docs/marketing-api/guides/lead-ads/retrieving#webhooks" target="_blank">Webhook</a> を使用します。Facebook で Webhook の使用を開始するには、<a href="https://developers.facebook.com/docs/graph-api/webhooks/getting-started" target="_blank">Webhook のドキュメント</a> を参照してください。
 
-Fac eBook でwebhook URL を確立したら、チームと協力して、[`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) にデータを転送する最適なパスを決定します。Zapier アプリ ローチと同様に、`users/track` エンドポイントを通じて、メール によって[ リクエストを行うことをお勧めします。
+Facebook で Webhook URL を確立したら、チームと協力して、[`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)にデータを転送するための最適なパスを決定します。Zapier アプローチと同様に、`users/track` エンドポイントから [メールによるリクエスト]({{site.baseurl}}/api/endpoints/user_data/post_user_track#example-request-for-updating-a-user-profile-by-phone-number)を実行することをお勧めします。
 {% enddetails %}
 
 {% alert tip %}
-トラブルシューティングのヒントについては、Zapierの<a href="https://help.zapier.com/hc/en-us/articles/8495982030861-Common-Problems-with-Facebook-Lead-Ads#h_01HC9V6Y652KQYYY96YG99T423" target="_blank">Fac eBookのトラブルシューティングガイド</a>を参照してください。
+トラブルシューティングのヒントについては、Zapierの<a href="https://help.zapier.com/hc/en-us/articles/8495982030861-Common-Problems-with-Facebook-Lead-Ads#h_01HC9V6Y652KQYYY96YG99T423" target="_blank">Facebook リードのトラブルシューティングガイド</a>を参照してください。
 {% endalert %}
 
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/payments.md b/_lang/ja/_partners/data_and_infrastructure_agility/payments.md
index c93582f0f74..fc649932f97 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/payments.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/payments.md
@@ -1,6 +1,6 @@
 ---
 nav_title: 決済
-article_title: 支払パートナー
+article_title: 決済のパートナー
 layout: partner_page
 page_order: 8
 
@@ -14,8 +14,8 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Payment Infrastructure"
 
 valid_partner_list:
-- name: レベニューキャット
+- name: RevenueCat
   url: /docs/partners/data_and_infrastructure_agility/payments/revenuecat/
-- name: リカーリー
+- name: Recurly
   url: /docs/partners/data_and_infrastructure_agility/payments/recurly/
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/payments/recurly.md b/_lang/ja/_partners/data_and_infrastructure_agility/payments/recurly.md
index 0b57c97e40f..74c685d2eb4 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/payments/recurly.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/payments/recurly.md
@@ -1,30 +1,30 @@
 ---
-nav_title: リカーリー
-article_title: リカーリー
-description: "Recurlyは、サブスクリプションおよび請求プラットフォームのリーダーであり、サブスクリプションと定期収益を成長させようとする直接消費者ブランド向けです。"
+nav_title: Recurly
+article_title: Recurly
+description: "Recurly は、業界をリードするサブスクリプションおよび請求プラットフォームであり、サブスクリプションと定期収益の拡大を求める Direct-to-Consumer ブランド向けのサブスクリプション管理および課金プラットフォームです。"
 alias: /partners/recurly/
 page_type: partner
 search_tag: partner
 ---
 
-# リカーリー
+# Recurly
 
-> [Recurly](https://recurly.com/)はサブスクリプション管理および請求プラットフォームです。Recurly統合プラットフォームは、サブスクリプションライフサイクルのオートメーションを簡素化し、チームが新しいプラン、オファー、プロモーションのテストから、支払い方法、統合、インサイトの管理まで、サブスクライバーの体験を管理および最適化できるようにします。
+> [Recurly](https://recurly.com/)はサブスクリプション管理および請求プラットフォームです。Recurly 統合プラットフォームは、サブスクリプションライフサイクルのオートメーションを簡素化し、チームがサブスクライバーの体験 (新しいプラン、オファー、プロモーションのテストから、決済方法、統合、インサイトの管理まで) を管理および最適化できるようにします。
 
-RecurlyとBrazeの統合により、サブスクリプションデータをBrazeと共有するプロセスが簡素化され、顧客とのターゲットコミュニケーションが可能になります。
+Recurly と Braze の統合により、サブスクリプションデータを Braze と共有するプロセスが簡素化され、顧客とのターゲットを絞ったコミュニケーションが可能になります。
 
-- BrazeでRecurlyのサブスクリプションライフサイクルイベント（例えば、サブスクリプションの更新、一時停止、またはキャンセル）を活用して、パーソナライズされたキャンペーンやコミュニケーションをトリガーします。
-- Recurlyのサブスクリプションデータ（例えば、サブスクリプションプラン、アドオン、またはステータス）を活用して、Brazeユーザー、セグメント、およびキャンバスを作成および管理し、コホート固有のキャンペーンおよびコミュニケーションを実行します。
+- Braze で Recurly のサブスクリプションライフサイクルイベント (サブスクリプションの更新、一時停止、またはキャンセルなど) を活用して、パーソナライズされたキャンペーンやコミュニケーションをトリガーします。
+- Recurly のサブスクリプションデータ (サブスクリプションプラン、アドオン、ステータスなど) を活用して、Braze ユーザー、セグメント、およびキャンバスを作成、管理し、コホート固有のキャンペーンおよびコミュニケーションを実施します。
 - Recurlyデータを直接Brazeに送信し、追加のメッセージングユースケースを可能にし、開発のオーバーヘッドコストを削減します。
 
-BrazeとRecurlyの使用に関する追加の詳細は、[Recurly Docs](https://docs.recurly.com/docs/braze-integration)で見つけることができます。
+Braze と Recurly の使用に関する追加の詳細については、[Recurly のドキュメント](https://docs.recurly.com/docs/braze-integration)で確認できます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| Recurlyアカウント | このパートナーシップを活用するには、Brazeフィーチャーフラグが有効になっているエリート[Recurly](https://recurly.com/)サブスクリプションプランが必要です。Recurlyプラットフォームでのクレジット請求書の有効化も必要です。|
-| Braze REST API キー | `users.track`の権限を持つBraze REST APIキー。<br><br> これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。Recurlyは`users.track`エンドポイントのみを使用するため、この権限のみを持つRecurly専用キーをプロビジョニングすることをお勧めします。 |
+| Recurly アカウント | このパートナーシップを活用するには、Brazeフィーチャーフラグが有効になっているエリート[Recurly](https://recurly.com/)サブスクリプションプランが必要です。Recurly プラットフォームでクレジット請求書を有効化する必要もあります。|
+| Braze REST API キー | `users.track`の権限を持つBraze REST APIキー。<br><br> これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。Recurly は `users.track` エンドポイントのみを使用するため、この権限のみで Recurly 専用キーをプロビジョニングすることをお勧めします。 |
 | Braze REST エンドポイント | [あなたのRESTエンドポイントURL][1].お客様のエンドポイントは、お客様のインスタンスのBraze URLに依存します。 |
 
 ## 統合
@@ -33,11 +33,11 @@ BrazeとRecurlyの使用に関する追加の詳細は、[Recurly Docs](https://
 
 ### RecurlyをBrazeに接続
 
-1. Recurlyで、**Integrations** > **Braze** に移動します。RecurlyのBraze統合設定ページに初めて移動すると、インターフェイスが両方のシステムを接続するように促します。
+1. Recurly で \[**Integrations**] > \[**Braze**] に移動します。Recurly の Braze統合設定ページに初めて移動すると、2 つのシステムを接続するように促されます。
 
-2. 次の資格情報を提供してください:
+2. 以下の認証情報を指定します。
 
-- **インスタンスURL:**プロビジョニングされたインスタンスのBraze RESTエンドポイント。
+- **Instance URL:**プロビジョニングされたインスタンスのBraze RESTエンドポイント。
 - **API キー (識別子):**RecurlyがBrazeにリクエストを送信する際に使用するBraze REST APIキー。
 
 BrazeインスタンスのURLをコピーすることを忘れないでください。例えば、あなたのURLは次のようになります: 
@@ -57,34 +57,34 @@ Recurlyはアカウントの`account_code`をBrazeの`external_id`として使
 
 ### カスタムイベント
 
-効果的なカスタマーエンゲージメントのためには、Recurlyによってトリガーされたイベントを受信するためにBrazeで[カスタムイベントを設定する][2]必要があります。Recurlyの各イベントを含めて、徹底したデータ統合を行うようにしてください。これらのイベントは、[Braze 分析][3]内でも追跡できます。一度設定すると、これらのカスタムイベントを使用してユーザーをセグメント化したり、メッセージングをパーソナライズしたりできます。 
+カスタマーエンゲージメントを効果的に行うには、Recurly によってトリガーされるイベントを受信すrるために、Braze で[カスタムイベントを設定][2]する必要があります。データ統合を徹底するために、Recurly の各イベントを含めるようにしてください。これらのイベントは、[Braze 分析][3]内でも追跡できます。一度設定すると、これらのカスタムイベントを使用してユーザーをセグメント化したり、メッセージングをパーソナライズしたりできます。 
 
-| Braze カスタムイベント| リカーリーイベント |
+| Braze カスタムイベント| Recurly イベント |
 | ----------- | ----------- |
-| Recurly新規サブスクリプション              | サブスクリプションが作成されたときにトリガーされます                            |
-| Recurly更新サブスクリプション          | サブスクリプションが更新されるとトリガーされます                                |
-| リカーリー更新サブスクリプション          | サブスクリプションの属性が変更されたときにトリガーされます（プランの変更、価格の変更、または数量の変更） |
-| Recurlyキャンセルされたサブスクリプション         | サブスクリプションがキャンセルされたときにトリガーされます                           |
-| Recurly再活性化サブスクリプション      | キャンセルされたサブスクリプションが再アクティブ化されたときにトリガーされます               |
-| Recurly一時停止中のサブスクリプション           | サブスクリプションが一時停止に設定されたときにトリガーされます                   |
-| Recurlyはサブスクリプションを再開しました          | サブスクリプションが再開されたときにトリガーされます                              |
-| リカーリーサブスクリプションの有効期限が切れました          | サブスクリプションの有効期限が切れたときにトリガーされます                               |
-| リカーリーの請求書が作成されました               | 請求書が作成されたときにトリガーされます                                |
-| リカーリーの支払いが成功しました            | 請求書が正常に回収されたときにトリガーされます                 |
-| リカーリーの返金が発行されました                 | 返金が発行されたときにトリガーされます                                   |
-| リカーリーの定期支払いが失敗しました      | サブスクリプションの更新のための請求書が失敗したときにトリガーされます          |
+| Recurly 新規サブスクリプション              | サブスクリプションが作成されたときにトリガーされます                            |
+| Recurly サブスクリプション更新          | サブスクリプションが更新されるとトリガーされます                                |
+| Recurly サブスクリプション変更          | サブスクリプションの属性が変更されたときにトリガーされます（プランの変更、価格の変更、または数量の変更） |
+| Recurly サブスクリプションキャンセル         | サブスクリプションがキャンセルされたときにトリガーされます                           |
+| Recurly サブスクリプション再有効化      | キャンセルされたサブスクリプションが再アクティブ化されたときにトリガーされます               |
+| Recurly サブスクリプション一時停止           | サブスクリプションが一時停止に設定されたときにトリガーされます                   |
+| Recurly サブスクリプション再開          | サブスクリプションが再開されたときにトリガーされます                              |
+| Recurly サブスクリプション期限切れ          | サブスクリプションの有効期限が切れたときにトリガーされます                               |
+| Recurly 請求書作成               | 請求書が作成されたときにトリガーされます                                |
+| Recurly 決済成功            | 請求書が正常に回収されたときにトリガーされます                 |
+| Recurly 返金                 | 返金が行われたときにトリガーされます                                   |
+| Recurly 定期払い失敗      | サブスクリプション更新のための請求書が失敗したときにトリガーされます          |
 
 ### バッチ処理とレート制限
 
-RecurlyはBrazeの`/users/track`エンドポイントを使用しているため、統合は1分あたり50,000リクエストの標準的なBrazeレート制限の対象となります。
+Recurly は Braze `/users/track` エンドポイントを使用しているため、この統合は標準的な Braze レート制限 (1分あたり50,000件のリクエスト) の対象となります。
 
-Recurlyは、特定のサブスクリプションライフサイクルイベントを単一のAPI呼び出しとしてBrazeにバッチ処理し、呼び出し回数を減らします。
+Recurly は、特定のサブスクリプションライフサイクルイベントを Braze に対する単一の API 呼び出しとしてバッチ処理し、呼び出し回数を削減します。
 
 - 複数のサブスクリプションの同時作成はバッチ処理され、単一のリクエストとしてBrazeに送信されます。
 - アカウントの複数のサブスクリプションが同時に更新されると、それらの更新はすべて1つのリクエストにまとめられます。
-- 同じモデルのサブスクリプションライフサイクルイベントは単一のリクエストとして送信されます。支払いのある新しく作成された請求書の例では、`Recurly Invoice Created` と `Recurly Successful Payment` の両方のカスタムイベントを含む単一のAPIリクエストが送信されます。
+- 同じモデルのサブスクリプションライフサイクルイベントは単一のリクエストとして送信されます。新しく作成された請求書と支払いの例では、`Recurly Invoice Created` および `Recurly Successful Payment` の両方のカスタムイベントを含む単一の API リクエストが送信されます。
 
-バッチは一度に最大75件のイベントのグループでBrazeに送信されます。例えば、100件のサブスクリプションが一度に作成された場合、RecurlyはBrazeに対して2回のAPIリクエストを行います。詳細については、[バッチ処理ユーザートラックリクエスト][4]を参照してください。
+バッチは一度に最大75個のイベントのグループで Braze に送信されます。例えば、100件のサブスクリプションが一度に作成された場合、RecurlyはBrazeに対して2回のAPIリクエストを行います。詳細については、[バッチ処理ユーザートラックリクエスト][4]を参照してください。
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
 [2]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/payments/revenuecat.md b/_lang/ja/_partners/data_and_infrastructure_agility/payments/revenuecat.md
index 6dd08e73911..594165b53fe 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/payments/revenuecat.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/payments/revenuecat.md
@@ -1,48 +1,48 @@
 ---
-nav_title: レベニューキャット
-article_title: レベニューキャット
-description: "RevenueCatとBrazeの統合により、顧客の購入と購読のライフサイクルイベントをプラットフォーム間で自動的に同期することができる。これにより、無料トライアル中にオプトアウトした顧客にエンゲージしたり、課金に問題がある顧客にリマインダーを送信するなど、顧客の購読ライフサイクルのステージに反応するキャンペーンを構築することができる。"
+nav_title: RevenueCat
+article_title: RevenueCat
+description: "RevenueCat と Braze の統合により、顧客の購入およびサブスクリプションのライフサイクルイベントをプラットフォーム間で自動的に同期できます。これにより、無料トライアル中にオプトアウトした顧客への働きかけや、請求で問題のある顧客へのリマインダーの送信など、顧客のサブスクリプションライフサイクルステージに対応するキャンペーンを作成できます。"
 alias: /partners/revenuecat/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# レベニューキャット
+# RevenueCat
 
-> [RevenueCatは](https://www.revenuecat.com/)、iOS、アンドロイド、ウェブにまたがるサブスクリプションのステータスを一元的に把握することができる。RevenueCatを使えば、クロスプラットフォームのアプリ内課金の構築、商品と購読者の管理、データ分析が可能で、サーバーコードは不要だ。
+> [RevenueCat](https://www.revenuecat.com/) は、iOS、Android、および Web におけるサブスクリプションステータスの信頼できる唯一の情報源です。新しいアプリを作成する場合でも、すでに数百万のサブスクライバーがいる場合でも、RevenueCat を使用すれば、サーバーコードなしでクロスプラットフォームのアプリ内購入を構築し、製品とサブスクライバーを管理し、データを分析することができます。
 
-RevenueCatとBrazeの統合により、顧客の購入と購読のライフサイクルイベントをプラットフォーム間で自動的に同期することができる。これにより、無料トライアル中にオプトアウトした顧客にエンゲージしたり、課金に問題がある顧客にリマインダーを送信するなど、顧客の購読ライフサイクルのステージに反応するキャンペーンを構築することができる。
+RevenueCat と Braze の統合により、顧客の購入およびサブスクリプションのライフサイクルイベントをプラットフォーム間で自動的に同期できます。これにより、無料トライアル中にオプトアウトした顧客への働きかけや、請求で問題のある顧客へのリマインダーの送信など、顧客のサブスクリプションライフサイクルステージに対応するキャンペーンを作成できます。
 
 ## 前提条件
 
-最低限、RevenueCatとBrazeを接続するには、RevenueCatダッシュボードから統合を有効にする必要がある。Braze SDKを使用している場合、RevenueCatとBraze SDKを一緒に使用することで、両方のシステムで同じ顧客識別子が使用されていることを確認し、統合を強化することができる。
+RevenueCat と Braze を接続するには、少なくとも RevenueCat ダッシュボードから統合を有効にしておく必要があります。Braze SDK を使用している場合は、RevenueCat SDK と Braze SDK を一緒に使用して、両方のシステムで同じ顧客識別子が使用されるようにすることで、統合を強化できます。
 
 | 必要条件 | 説明 |
 |---|---|
-| RevenueCatアカウントとアプリ | このパートナーシップを利用するには、\[RevenueCatアカウント][9] ]が必要である。また、RevenueCatアプリが設定されている必要がある。 |
-| RevenueCat SDK | 必要なBraze SDKに加えて、RevenueCatにユーザーエイリアスを提供するために、\[RevenueCat SDK][8] ] をインストールすることを推奨する。 |
-| ブレイズインスタンス | あなたのBrazeインスタンスは、あなたのBrazeオンボーディングマネージャーから取得するか、[API概要ページで]({{site.baseurl}}/api/basics/#endpoints)見つけることができる。<br><br>RevenueCatは、Brazeインスタンスが正しいBraze RESTエンドポイントにサーバーサイドから送信することを要求する。 |
+| RevenueCatアカウントとアプリ | このパートナーシップを活用するには、\[RevenueCat アカウント][9]が必要です。また、RevenueCat アプリが設定されている必要があります。 |
+| RevenueCat SDK | 必要な Braze SDK に加えて \[RevenueCat SDK][8] をインストールして、RevenueCat にユーザーエイリアスを提供することをお勧めします。 |
+| ブレイズインスタンス | Braze インスタンスは Braze オンボーディングマネージャーから入手できます。また、[API 概要ページ]({{site.baseurl}}/api/basics/#endpoints)でも確認できます。<br><br>RevenueCat では、Braze インスタンスが正しいBraze REST エンドポイントにサーバーサイドを送信する必要があります。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze test REST APIキー（オプション） | テスト用APIキーは、テスト用と本番用で別々のBrazeインスタンスにリクエストを送信したい場合に使用できる。 |
+| Braze test REST APIキー（オプション） | テスト API キーは、テスト購入と本番購入のリクエストを個別の Braze インスタンスに送信する場合に、テスト購入および本番購入に使用できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース 
 
-- 顧客が無料トライアルを開始すると、プレミアム機能を強調するオンボーディングキャンペーンをトリガーする。
-- 課金問題」イベントを受信した際に、課金情報を更新するリマインダーを送信する。
-- 顧客が無料トライアルをキャンセルした後、フィードバック調査を送る。 
+- 顧客が無料トライアルを開始するときにプレミアム機能を強調するオンボーディングキャンペーンをトリガーする。
+- 「Billing Issue」イベントを受信したときに請求情報を更新するためにリマインダーを送信する。
+- 顧客が無料トライアルをキャンセルした後で、フィードバックアンケートを送信する。 
 
 ## 統合
 
 ### ステップ1:BrazeのユーザーIDを設定する
 
-Braze SDKでは、BrazeのユーザーIDとRevenueCatアプリのユーザーIDを一致させることで、BrazeとRevenueCatから送信されるイベントを同じユーザーに同期させることができる。
+Braze SDK では、RevenueCat アプリのユーザー ID に一致するように Braze ユーザーID を設定できます。これにより、Braze と RevenueCat から送信されるイベントを同じユーザーに同期できます。
 
-RevenueCat と同じアプリユーザーIDでBraze SDKを設定するか、Braze SDK`.changeUser()` メソッドを使用する。
+RevenueCat と同じアプリユーザー ID で Braze SDK を設定するか、Braze SDK `.changeUser()` メソッドを使用します。
 
 {% tabs ローカル %}
-{% tab 速い %}
+{% tab swift %}
 ```swift
 // Configure Purchases SDK
 Purchases.configure(withAPIKey: "public_sdk_key", appUserID: "my_app_user_id")
@@ -55,7 +55,7 @@ Purchases.shared.setAttributes(["$brazeAliasName" : "name",
                              "$brazeAliasLabel" : "label"])
 ```
 {% endtab %}
-{% tab オブジェクティブシー %}
+{% tab objective-c %}
 ```objc
 // Configure Purchases SDK
 [RCPurchases configureWithAPIKey:@"public_sdk_key" appUserID:@"my_app_user_id"];
@@ -70,7 +70,7 @@ Purchases.shared.setAttributes(["$brazeAliasName" : "name",
 }];
 ```
 {% endtab %}
-{% tab ジャワ %}
+{% tab java %}
 ```java
 // Configure Purchases SDK
 Purchases.configure(this, "public_sdk_key", "my_app_user_id");
@@ -90,7 +90,7 @@ Purchases.getSharedInstance().setAttributes(attributes);
 
 #### ユーザーエイリアスオブジェクトをBrazeに送信する（オプション） 
 
-RevenueCatアプリのユーザーIDとは別の一意のユーザー識別子を送信したい場合は、RevenueCatのサブスクライバー属性として以下のデータをユーザーに更新する。
+RevenueCat アプリのユーザー ID とは異なる代替の一意のユーザー識別子を送信する場合は、RevenueCat サブスクライバー属性として次のデータでユーザーを更新します。
 
 | キー | 説明 |
 |---|---|
@@ -98,22 +98,22 @@ RevenueCatアプリのユーザーIDとは別の一意のユーザー識別子
 | `$brazeAliasLabel` | [ユーザーエイリアスオブジェクトの][2]Braze`alias_label`  |
 {: .reset-td-br-1 .reset-td-br-2}
 
-両方の属性は、[ユーザーエイリアスオブジェクトが][2]イベントデータと一緒に送信されるために必要である。これらのプロパティは、他の \[RevenueCat サブスクライバー属性]][4] と同様に、手動で設定することができる。コード・スニペットの例をステップ1に示す。
+どちらの属性も、[ユーザーエイリアスオブジェクト][2]をイベントデータとともに送信するために必要です。これらのプロパティは、他の \[RevenueCat サブスクライバー属性][4]と同様に、手動で設定できます。コード・スニペットの例をステップ1に示す。
 
-### ステップ2:RevenueCatのイベントをBrazeに送信する
+### ステップ2:RevenueCat イベントを Braze に送信する
 
-RevenueCat purchases SDKとBraze SDKが同じユーザーIDになるように設定したら、RevenueCatダッシュボードから統合をオンにしてイベント名を設定することができる。
+RevenueCat が同じユーザー ID を持つようにRevenueCat purchases SDK と Braze SDK を設定したら、RevenueCat ダッシュボードで統合を有効にしてイベント名を設定できます。
 
-1. RevenueCatダッシュボードのプロジェクトに移動し、左メニューの**Integrations**カードを見つける。選択**＋新規作成する**。
-2. 次に、利用可能な統合から**Brazeを**選択し、BrazeインスタンスとBraze REST APIキーを追加する。 
-3. RevenueCatが送信するイベント名を入力するか、デフォルトのイベント名を選択する。利用可能なイベントの詳細は、[ステップ](#configure-event-names)3で確認できる。
-4. RevenueCatに売上高（アプリストアカット後）を報告させるか、売上高（総売上高）を報告させるかを選択する。
+1. RevenueCat ダッシュボードでプロジェクトに移動し、左側のメニューで \[**Integrations**] カードを見つけます。\[**\+ New**] を選択します。
+2. 次に、利用可能な統合から \[**Braze**] を選択し、Braze インスタンスと Braze REST API キーを追加します。 
+3. RevenueCatが送信するイベント名を入力するか、デフォルトのイベント名を選択する。利用可能なイベントの詳細については、[ステップ3](#configure-event-names)を参照してください。
+4. RevenueCat で売上 (アプリストアの取り分差し引き後) または収益 (総売上高) を報告するかどうかを選択します。
 
-![Brazeインスタンス、APIキー識別子、サンドボックス識別子のフィールドを持つRevenueCatのBraze設定。][3]
+![Braze インスタンス、API キー識別子、およびサンドボックス識別子のフィールドを含む RevenueCat での Braze 設定。][3]
 
 ### ステップ3:イベント名を設定する {#configure-event-names}
 
-RevenueCatが送信するイベント名を入力するか、**Use Default Event Namesを**選択してデフォルトのイベント名から選択する。RevenueCatが送信をサポートしているイベントは、以下の表の通りである。
+RevenueCat が送信するイベント名を入力するか、\[**Use Default Event Names**] を選択してデフォルトのイベント名から選択します。RevenueCatが送信をサポートしているイベントは、以下の表の通りである。
 
 | イベント | 説明 |
 |---|---|
@@ -121,24 +121,24 @@ RevenueCatが送信するイベント名を入力するか、**Use Default Event
 | トライアル開始 | 自動更新のサブスクリプション製品の無料トライアルの開始。 |
 | トライアル転換 | 自動更新のサブスクリプション商品が、無料トライアルから通常の有料期間に変更された場合。 |
 | 試験中止 | 無料トライアル期間中に、ユーザーが自動更新のサブスクリプション製品の更新をオフにした場合。 |
-| リニューアル | 自動更新のサブスクリプション商品が更新された場合、またはユーザーがサブスクリプションの失効後に自動更新のサブスクリプション商品を再購入した場合。 |
+| 更新 | 自動更新サブスクリプション製品が更新された場合、またはユーザーがサブスクリプション期限の経過後に自動更新サブスクリプション製品を再購入した場合。 |
 | キャンセル | 通常の有料期間中に、ユーザーが自動更新のサブスクリプション製品の更新をオフにした場合。 |
-| 非購読購入 | 自動更新の定期購読ではない製品を購入すること。 |
+| Non Subscription Purchase | 自動更新サブスクリプションではない製品の購入。 |
 | 有効期限 | サブスクリプションの期限が切れる。 |
-| 課金問題 | ユーザーへのチャージに問題があった場合。 |
+| 課金問題 | ユーザーへの請求時に問題が発生した場合。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 収益を含むイベントの場合、RevenueCatは、トライアルコンバージョンや更新などのイベントとともに、この金額を自動的にBrazeに記録する。
 
 ## この統合を使う
 
-RevenueCatでBrazeの設定を行った後、イベントは自動的にRevenueCatからBrazeに流れ始める。
+RevenueCat で Braze の設定が完了したら、イベントが RevenueCat から Braze に自動的に流れ始めます。お客様による操作は不要です。
 
 ## カスタマイズ
 
 ### テスト用のサンドボックスAPIキーを追加する
 
-Braze REST APIキーを1つだけRevenueCatに提供すると、本番イベントのみが送信される。サンドボックステストのイベントも送信したい場合は、\[別のBraze REST APIキー][11] を作成し、RevenueCatのBraze設定に追加する。
+RevenueCat に1つの Braze REST API キーのみを指定すると、本番イベントのみが送信されます。サンドボックステストイベントも送信する場合は、\[別の Braze REST API キー][11]を作成し、RevenueCat の Braze 設定に追加します。
 
 [2]: {{site.baseurl}}/api/objects_filters/user_alias_object/
 [3]: {% image_buster /assets/img/revenuecat/braze_settings_in_revenuecat.png %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/support.md b/_lang/ja/_partners/data_and_infrastructure_agility/support.md
index d44426314f7..728f8993947 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/support.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/support.md
@@ -4,7 +4,7 @@ article_title: サポートパートナー
 page_order: 9
 
 page_type: landing
-description: "このランディングページには、Brazeを顧客サポートスイートと統合できるBrazeパートナ(Alloys) が一覧表示されます。"
+description: "このランディングページには、Braze と顧客サポートスイートを統合できる Braze パートナー (Alloys) が一覧表示されています。"
 
 layout: partner_page
 search_tag: Partner
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/support/pypestream.md b/_lang/ja/_partners/data_and_infrastructure_agility/support/pypestream.md
index cf0ef33251b..e09ec23190a 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/support/pypestream.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/support/pypestream.md
@@ -1,6 +1,6 @@
 ---
-nav_title: パイプストリーム
-article_title: パイプストリーム
+nav_title: Pypestream
+article_title: Pypestream
 description: "この参考記事では、ブランドとのデジタル・エンゲージメントを強化できるフルスタックの会話AIプラットフォームであるBrazeとPypestreamのパートナーシップについて概説している。"
 alias: /partners/pypestream/
 page_type: partner
@@ -8,39 +8,39 @@ search_tag: Partner
 
 ---
 
-# パイプストリーム
+# Pypestream
 
-> [Pypestreamは](https://www.pypestream.com)フルスタックの会話AIプラットフォームで、特許を取得したオールインワンのクラウド・メッセージングを提供し、ブランドを「常時オン」のデジタル・エンティティに変える。Pypestreamを利用することで、ブランドは、没入感のあるユーザー体験、高度なNLU機能、バックエンドシステムとのリアルタイム統合を活用しながら、すべての顧客とオムニチャネルの会話を大規模に行うことができる。
+> [Pypestream](https://www.pypestream.com) はフルスタックの会話型 AI プラットフォームであり、特許取得済みのオールインワン型のクラウドメッセージングを提供し、ブランドを「常時稼働」状態のデジタルエンティティに変換します。Pypestream によりブランドは、没入型のユーザーエクスペリエンス、高度な NLU 機能、バックエンドシステムへのリアルタイム統合を利用し、大規模なオムニチャネルの会話に参加できるようになります。
 
-BrazeとPypestreamの統合により、最初のアウトリーチから、会話体験へのルーティング、インテリジェントなリターゲティングによるオムニチャネルのフォローアップまで、エンドツーエンドの顧客ライフサイクルをシームレスに編成することができる。 
+Braze と Pypestream の統合により、最初のアウトリーチから、会話エクスぺリエンスへのルーティング、インテリジェントなリターゲティングによるオムニチャネルのフォローアップまで、エンドツーエンドのカスタマーライフサイクルをシームレスに調整できます。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| Pypestreamアカウント | このパートナーシップを利用するには、[Pypestreamのアカウントが](https://www.pypestream.com/contact-us/)必要である。<br><br>契約後は、Pypestreamチームが専用環境のセットアップを支援し、Brazeと統合する会話AIソリューションの構築を開始する。 |
+| Pypestreamアカウント | このパートナーシップを活用するには、[Pypestream アカウント](https://www.pypestream.com/contact-us/)が必要です。<br><br>サブスクライブ後は、Pypestream チームが、Braze と統合する会話型 AI ソリューションの構築を開始するための専用の環境の設定を支援します。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに]({{site.baseurl}}/api/basics/)依存する。 |
+| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL]({{site.baseurl}}/api/basics/) に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
-BrazeとPypestreamのパートナーシップは、Canvasesで以下のような一般的なユースケースを実現するために使用することができる：
-* **インテリジェントなリターゲティング**：Pypestreamを通じて収集された豊富なデータポイントを活用することで、ブランドとの会話エンゲージメントの後にBraze Canvasでユーザーをリターゲティングしよう。
-* **ダイナミック・ターゲティング**だ：特定のコホートやセグメントに基づいて既存顧客や見込み客にアプローチし、Pypestreamを通じてカスタマイズされた会話体験を提供する。
-* **コンテクスチュアルな顧客インサイト**：エンドユーザー（既存または見込み客）がウェブサイトにアクセスした後、Pypestream Event Listenerから取り込んだウェブページタグと、Brazeに保存されている顧客データを組み合わせることで、完全にパーソナライズされた、文脈に沿った会話型インタラクションを提供することができる。
+Braze と Pypestream の連携により、キャンバスで以下のような一般的なユースケースを実現できます。
+* **インテリジェントなリターゲティング**：Pypestream で収集されたリッチなデータポイントをすべて活用して、ユーザーがブランドとの会話を終えた後に Braze キャンバスでユーザーをリターゲティングします。
+* **ダイナミックターゲット設定**：特定のコホートやセグメントに基づいて既存の顧客や見込み客にアプローチし、Pypestream でカスタマイズされた会話エクスペリエンスを提供します。
+* **状況に即した顧客インサイト**:エンドユーザー (既存の顧客または見込み客) が Web サイトでやり取りをした後で、Pypestream Event Listener から取り込んだ Web ページタグと、Braze に保存されている顧客データを組み合わせることで、完全にパーソナライズされ、コンテキストに即した会話型インタラクションを提供できます。
 
 ## 統合
 
-Pypestreamはサーバーレスの統合レイヤーを活用し、様々なプラットフォームへのカスタム統合を行う。このレイヤーは、構築される会話フローのデータ要件をサポートするために、サービスやシステムとのインターフェースに使用される。アクション・ノード統合と呼ばれるこれらの統合は、通常Pythonで書かれ、Pypestreamプラットフォームを使ってデプロイされる。アクションノードがインスタンス化されると、Braze APIのどのエンドポイントにも柔軟に統合できるようになり、結果をさまざまな方法で評価できるようになる。 
+Pypestreamはサーバーレスの統合レイヤーを活用し、様々なプラットフォームへのカスタム統合を行う。このレイヤーは、構築される会話フローのデータ要件をサポートするために、サービスやシステムとのインターフェースに使用される。これらの統合は、アクションノード統合と呼ばれ、通常、Python で記述され、Pypestream プラットフォームを使用してデプロイされます。アクションノードがインスタンス化されると、Braze APIのどのエンドポイントにも柔軟に統合できるようになり、結果をさまざまな方法で評価できるようになる。 
 
 {% alert note %}
-Pypestreamアクションノードの概要と設定手順については、こちらの[Pypestreamの記事を](https://pypestream.atlassian.net/servicedesk/customer/kb/view/669352070)参照のこと。このドキュメントにアクセスするには、Pypestreamの顧客である必要がある。
+Pypestream アクションノードの概要と設定手順については、この [Pypestream の記事](https://pypestream.atlassian.net/servicedesk/customer/kb/view/669352070)を参照してください。このドキュメントにアクセスするには、Pypestream の顧客である必要があります。
 {% endalert %}
 
 ### ステップ1:エンドポイントの設定を行う
 
-Braze RESTエンドポイントURLやBraze APIキーなどの主要な設定値は、ソリューションの`app.py` ファイルに設定する： 
+Raze REST エンドポイント URL や Braze API キーなどの主要な設定値は、ソリューションの `app.py` ファイルで設定する必要があります。 
 
 ```
 import os
@@ -156,28 +156,28 @@ class BrazeExample:
 Braze REST APIと統合する最後のステップでは、前のステップで開発したアクションノードを使用するように、Pypestreamの[Design Studio](https://platform.pypestream.com/design-studio/)内でフローを設定する。 
 
 {% alert note %}
-Design Studioでモードを設定する方法の概要については、[Pypestreamの記事を](https://pypestream.atlassian.net/servicedesk/customer/kb/view/669352070)参照のこと。このドキュメントにアクセスするには、Pypestreamの顧客である必要がある。
+Design Studio でモードを設定する方法の概要については、[Pypestream の記事](https://pypestream.atlassian.net/servicedesk/customer/kb/view/669352070)を参照してください。このドキュメントにアクセスするには、Pypestream の顧客である必要があります。
 {% endalert %}
 
 ## 統合のユースケース
 
-前提条件が満たされ、アクションノード構造が作成されると、開発者は、Braze APIエンドポイントと対話する際に、空白のキャンバスで作業できるようになる。この例では、アクションノードをBraze[`/user/track` のエンドポイントに]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)統合するために必要な手順を示す[。具体的には]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)、Pypestreamの会話フローに入る特定のユーザーを追跡するためのユーザープロファイルを作成する。
+前提条件が満たされ、アクションノード構造が作成されると、開発者はブランクのキャンバスを使用して、Braze API エンドポイントとのインタラクションを開始します。この例は、アクションノードを Braze [`/user/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)に統合するために必要な手順を示します。具体的には、Pypestream 会話フローに入る特定のユーザーを追跡するためにユーザープロファイルを作成します。
 
 ### ステップ1:会話の中でユーザーからデータを収集する
 
-ユーザーがPypestreamのセッションに入ると、収集されるデータの詳細は、その時点でのユースケースに完全に依存する。Brazeでユーザープロフィールを作成するには、会話で必要なフィールドを収集する必要がある。
-目的のエンドポイントが必要とするものである。
+ユーザーが Pypestream セッションに入ると、収集されるデータの詳細は、その時点でのユースケースに完全に依存します。Brazeでユーザープロフィールを作成するには、会話で必要なフィールドを収集する必要がある。
+目的のエンドポイントに必要な
 
-例えば、Braze`/user/track` エンドポイントの会話中に、ソリューションがユーザーから以下の情報を収集したとする： 
+たとえば、ソリューションが Braze `/user/track` エンドポイントの会話中にユーザーから次の情報を収集するとします。 
 
 * 名
 * 姓
 * メールアドレス
 * 生年月日
-* 居住都市
+* 居住地の市町村
 * オペレーティング・システム
 
-このデータはBrazeプラットフォームに送られ、このユーザーのエンゲージメントを追跡し、将来的にリターゲティングできる可能性がある。一般的なアプリケーションを見るには、[ユースケース・リストを](#use-cases)チェックしよう。
+将来的にこのユーザーをリターゲティングできる機能により、このユーザーのエンゲージメントを追跡するために、このデータを Braze プラットフォームに送信できます。一般的なアプリケーションを見るには、[ユースケース・リストを](#use-cases)チェックしよう。
 
 ### ステップ2:アクションノード構造体にデータを入力する
 
@@ -276,4 +276,4 @@ class BrazeExample:
 
 ### ステップ3:アクションノードの成功/失敗時にリダイレクトするようにソリューションフローを更新する。
 
-最後に、各ソリューションの設計では、アクション・ノードAPI呼び出しが成功したかどうかに基づいて、ユーザーをノードにルーティングすることができる。アクションノードがエラーメッセージを受け取った場合、エンドユーザーは注意深く対処しなければならない。 
+最後に、各ソリューションの設計では、アクション・ノードAPI呼び出しが成功したかどうかに基づいて、ユーザーをノードにルーティングすることができる。アクションノードがエラーメッセージを受信した場合、エンドユーザーを慎重に処理する必要があります。 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/support/zendesk.md b/_lang/ja/_partners/data_and_infrastructure_agility/support/zendesk.md
index 73ffbacc5ca..ddf1c25f490 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/support/zendesk.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/support/zendesk.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Zendesk
 article_title: Zendesk
-description: "この参考記事では、Brazeと人気のサポートスイートであるZendeskのパートナーシップについて概説しており、2つのプラットフォーム間でサポートデータを同期できるBrazeのウェブフックを利用できる。"
+description: "このリファレンス記事では、Braze と Zendesk のパートナーシップについて説明します。Zendesk は人気の高いサポートスイートであり、この2つのプラットフォーム間でサポートデータを同期できる Braze Webhook を利用できます。"
 alias: /partners/zendesk/
 page_type: partner
 search_tag: Partner
@@ -10,18 +10,18 @@ search_tag: Partner
 
 # Zendesk
 
-> [Zendesk Support Suite](https://www.zendesk.com/support-suite/)（ZSS）は、Eメール、ウェブチャット、音声、ソーシャルメッセージングアプリを使ったオムニチャネルサポートを通じて、顧客との自然な会話を可能にする。Zendeskは、相互作用の追跡と優先順位付けを重視する合理化された発券システムを提供し、企業は顧客に関する統一された履歴ビューを持つことができる。
+> [Zendesk Support Suite](https://www.zendesk.com/support-suite/)（ZSS）は、Eメール、ウェブチャット、音声、ソーシャルメッセージングアプリを使ったオムニチャネルサポートを通じて、顧客との自然な会話を可能にする。Zendesk は対応の追跡と優先順位付けを重視する効率的なチケット発行システムを提供し、企業が顧客の履歴を一元的に把握できるようにしています。
 
-BrazeとZendeskのサーバー間統合を利用することができる： 
+Braze とZendesk のサーバー間統合により、以下を利用できます。 
 - BrazeのWebhookを使用して、BrazeのユーザージャーニーでのメッセージエンゲージメントによるZendeskでのサポートチケット作成を自動化する。例えば、統合の実装とテストに成功した後、Brazeは、アプリ内のメッセージ "Enjoying our App?" に否定的な回答をしたユーザーからサポートチケットを作成し、サポートチームが顧客をフォローアップできるようにする。
-- ZendeskのWebhookにより、ZendeskのアクティビティによってBrazeのユーザープロファイルを更新するような双方向のユースケースをサポートする。例えば、チケットが解決した後、Brazeのユーザープロファイルにイベントを記録する。
+- Zendesk でのアクティビティによる Braze でのユーザープロファイルの更新など、双方向ユースケースをサポートするための Zendesk Webhook。例えば、チケットが解決した後、Brazeのユーザープロファイルにイベントを記録する。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| Zendeskアカウント | このパートナーシップを利用するには、[Zendeskの管理者アカウントが](https://`<your-zendesk-instance>`.zendesk.com/agent/admin)必要である。 |
-| Zendesk APIトークン | BrazeからZendeskチケットエンドポイントにリクエストを送信するには、Zendesk[APIトーク][2]ンが必要である。 |
+| Zendeskアカウント | このパートナーシップを活用するには、[Zendesk 管理者アカウント](https://`<your-zendesk-instance>`.zendesk.com/agent/admin)が必要です。 |
+| Zendesk APIトークン | Braze から Zendesk チケットエンドポイントにリクエストを送信するには、Zendesk [API トークン][2]が必要です。 |
 | 共通識別子（推奨） | BrazeとZendesk間で[共通の識別子を](#common-identifier)使用することを推奨する。 |
 | BrazeのAPIキー | ZendeskからBrazeエンドポイントにリクエストを送信するには、Braze APIキーが必要である。使用するAPIキーが、Zendesk webhookが使用するBrazeエンドポイントに対して正しい権限を持っていることを確認する。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -32,29 +32,29 @@ BrazeとZendeskのサーバー間統合を利用することができる：
 
 ウェブフックを作成する：
 
-- **キャンペーン**Brazeダッシュボードの**Campaigns**ページに行く。**Create Campaignを**クリックし、**Webhookを**選択する。
-- **キャンバス:**新規または既存のキャンバスから、キャンバスビルダーでフルステップまたはメッセージステップを作成する。次に、**Messagesを**クリックし、メッセージ・オプションから**Webhookを**選択する。
+- **キャンペーン:**Brazeダッシュボードの**Campaigns**ページに行く。\[**キャンペーンを作成**] をクリックし、\[**Webhook**] を選択します。
+- **キャンバス:**新しいキャンバスまたは既存のキャンバスから、キャンバスビルダーでフルステップまたはメッセージステップを作成します。次に、\[**メッセージ**] をクリックし、メッセージオプションから \[**Webhook**] を選択します。
 
 Webhookに以下のフィールドを入力する：
-- **ウェブフックのURL**： `<your-zendesk-instance>.zendesk.com/api/v2/tickets.json`
-- **リクエスト・ボディ**Raw Text
+- **Webhook URL**: `<your-zendesk-instance>.zendesk.com/api/v2/tickets.json`
+- **リクエスト本文**:Raw Text
 
-その他のユースケースは、\[Zendesk support APIs][4], Webhook URL の末尾の`/api/v2/` エンドポイントを適宜変更する。
+その他のユースケースは、\[Zendesk support API][4] を使用して対処できます。これにより、Webhook URL の末尾の `/api/v2/` エンドポイントが変更されます。
 
-#### リクエスト・ヘッダとメソッド
+#### リクエストヘッダーとメソッド
 
-Zendesk は HTTP ヘッダによる認証と HTTP メソッドを要求する。**設定]**タブで、<email_address> を Zendesk 管理者のメールアドレスに、<api_token> を Zendesk API トークンに置き換える。
+Zendesk には、認証用の HTTP ヘッダーと HTTP メソッドが必要です。**設定]**タブで、<email_address> を Zendesk 管理者のメールアドレスに、<api_token> を Zendesk API トークンに置き換える。
 
 - **HTTPメソッド**：POST
-- **ヘッダーを要求する**：
-  - **認可する**：ベーシック {% raw %} `{{ '<email_address>/token:<api_token>' | base64_encode }}` {% endraw %}
+- **リクエストヘッダー**:
+  - **Authorization**:ベーシック {% raw %} `{{ '<email_address>/token:<api_token>' | base64_encode }}` {% endraw %}
   - **Content-Type**: application/json
 
 ![][3]{: style="max-width:70%;"}
 
 #### Request body
 
-Webhookペイロードで、タイプ、サブジェクト、ステータスなどのチケットの詳細を定義する。チケットの詳細は、\[Zendesk ticket API][6].以下の例を参考に、ペイロードを構成し、希望するフィールドを入力する。
+Webhookペイロードで、タイプ、サブジェクト、ステータスなどのチケットの詳細を定義する。チケットの詳細は拡張可能であり、\[Zendesk ticket API][6] に基づいてカスタマイズされます。以下の例を参考に、ペイロードを構成し、希望するフィールドを入力する。
 
 {% raw %}
 ```json
@@ -90,23 +90,23 @@ Webhookペイロードで、タイプ、サブジェクト、ステータスな
 
 ## 共通識別子
 
-BrazeとZendeskで共通の識別子がある場合は、これを`requester_id` 。これは、2組のユーザーを統一するのに役立つだろう。また、そうでない場合は、名前、Eメールアドレス、電話番号などの識別属性を渡すことを推奨する。
+Braze と Zendesk の間に共通の識別子がある場合は、それを `requester_id` として使用することをお勧めします。これにより、2つのユーザーセットを統一できます。それ以外の場合は、名前、メールアドレス、電話番号などの一連の識別属性を渡すことをお勧めします。
 
 ## ZendeskとBrazeの統合
 
 ### ステップ1:ウェブフックを作成する
 
-1. [Admin Centerで](https://support.zendesk.com/hc/en-us/articles/4581766374554#topic_hfg_dyz_1hb)、サイドバーの**Apps and integrationsを**クリックし、**Webhooks > Webhooksを**選択する。<br><br>
-2. **Create webhookを**クリックする。<br><br>
-3. **Trigger**または**Automationを**選択し、**Nextを**クリックする。<br>![][9]{: style="max-width:70%;"}<br><br>
-4. ウェブフックに以下の情報を記入する：
+1. [Admin Center](https://support.zendesk.com/hc/en-us/articles/4581766374554#topic_hfg_dyz_1hb) で、サイドバーにある \[**Apps and integrations**] クリックし、**\[Webhooks] > \[Webhooks]** を選択します。<br><br>
+2. \[**Create webhook**] をクリックします。<br><br>
+3. \[**Trigger**] または \[**Automation**] を選択し、\[**Next**] をクリックします。<br>![][9]{: style="max-width:70%;"}<br><br>
+4. Webhook に以下の情報を指定します。
 - ウェブフックの名前と説明を入力する。
 - Webhookが使用するBrazeエンドポイントURLを入力する。{% raw %}この例では`https://{{instance_url}}/users/track` を使用する。{% endraw %}
 - ウェブフックのリクエスト・メソッドとしてPOSTを選択し、リクエスト・フォーマットをJSONに設定する。
-- Webhookのベアラートークン認証方法を選択し、[Braze APIキーを](https://www.braze.com/docs/api/basics/#creating-and-managing-rest-api-keys)入力する。
-  - 使用するAPIキーが、Webhookが使用するBrazeエンドポイントに対して[正しい権限を持って](https://www.braze.com/docs/api/basics/#rest-api-key-permissions)いることを確認する。<br><br>
+- Webhook にベアラートークン認証方式を選択し、[Braze API キー](https://www.braze.com/docs/api/basics/#creating-and-managing-rest-api-keys)を入力します。
+  - 使用する API キーに、Webhook が使用する Braze エンドポイントに対して[正しい権限](https://www.braze.com/docs/api/basics/#rest-api-key-permissions)があることを確認します。<br><br>
 5. (推奨）ウェブフックが正しく動作しているかテストする。<br><br>
-6. トリガーとオートメーションのウェブフックについては、セットアップを終了する前に、ウェブフックをトリガーまたはオートメーションに接続する必要がある。Webhookのトリガーを作成する例については、次のステップを参照のこと。トリガーが作成されたら、このページに戻り、**Finish setupを**クリックする。
+6. トリガーとオートメーションのウェブフックについては、セットアップを終了する前に、ウェブフックをトリガーまたはオートメーションに接続する必要がある。Webhookのトリガーを作成する例については、次のステップを参照のこと。トリガーが作成されたら、このページに戻り、\[**Finish setup**] をクリックします。
 
 ### ステップ2:トリガーまたはオートメーションを作成する
 
@@ -114,14 +114,14 @@ BrazeとZendeskで共通の識別子がある場合は、これを`requester_id`
 
 以下の例では、サポートケースのステータスが "Solved"（解決済み）または "Closed"（クローズ済み）に変更されたときに、Webhookを呼び出すトリガーを使用している。 
 
-1. **Admin Centerで**、サイドバーの**Objects and rulesを**クリックし、**Business rules > Triggersを**選択する。<br><br>
-2. **Add triggerを**クリックする。<br><br>
+1. **Admin Center** で、サイドバーにある \[**Objects and rules**] をクリックし、**\[Business rules] > \[Triggers]** を選択します。<br><br>
+2. \[**Add trigger**] をクリックします。<br><br>
 3. トリガーに名前を付け、カテゴリーを選択する。<br><br>
-4. **Add conditionを**クリックして、ウェブフックをトリガーする条件を設定する。例えば、「ステータスのカテゴリーがクローズに変更されました」や「ステータスのカテゴリーが解決済みに変更されました」などである。![][8]{: style="max-width:70%;"}<br><br>
-5. **Add actionを**クリックし、**Notify active webhookを**選択し、前のステップで作成したwebhookをドロップダウンから選択する。<br><br>
+4. \[**Add condition**] をクリックして、Webhook をトリガーする条件を設定します。たとえば、「Status category changed to closed」や「Status category changed to solved」などです。![][8]{: style="max-width:70%;"}<br><br>
+5. \[**Add action**] をクリックし、\[**Notify active webhook**] を選択し、前のステップで作成した Webhook をドロップダウンから選択します。<br><br>
 6. Brazeのエンドポイントに適合するようにJSON本体を定義し、Zendeskの変数プレースホルダを使用して、関連するフィールドに動的に入力する。<br>![][10]{: style="max-width:70%;"}<br><br>
 7. \[**作成**] をクリックします。<br><br>
-8. Webhookに戻り、**Finish setupを**クリックする。
+8. Webhook に戻り、\[**Finish setup**] をクリックします。
 
 [1]: {{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/
 [2]: https://support.zendesk.com/hc/en-us/articles/226022787-Generating-a-new-API-token-\
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation.md
index c89180c26b1..b63f006286c 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation.md
@@ -18,7 +18,7 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/fivetran/
 - name: Zapier
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/zapier/
-- name: ネクスラ
+- name: Nexla
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/nexla/
 - name: Hightouch
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/hightouch/
@@ -28,8 +28,8 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/airbyte/
 - name: GrowthLoop
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/growthloop/
-- name: モーツァルト・データ
+- name: Mozart Data
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/mozart_data/
-- name: メタ・ルーター
+- name: MetaRouter
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/metarouter/
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/airbyte.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/airbyte.md
index 20bcb7b7c79..1db1e4adcd9 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/airbyte.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/airbyte.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Airbyte
 article_title: Airbyte
-description: "この参考記事では、BrazeとAirbyteの統合について取り上げている。Airbyteはオープンソースのデータ統合エンジンで、データウェアハウス、レイク、データベース内のデータを統合し、AirbyteからBrazeにリアルタイムイベントを転送するのに役立つ。"
+description: "この参考記事では、BrazeとAirbyteの統合について取り上げている。Airbyte はデータウェアハウス、データレイク、データベースにデータを統合するのに役立つオープンソースのデータ統合エンジンであり、Airbyte から Braze にリアルタイムのイベントが転送されます。"
 alias: /partners/airbyte/
 page_type: partner
 search_tag: Airbyte
@@ -10,32 +10,32 @@ search_tag: Airbyte
 
 # Airbyte
 
-> [Airbyteは](https://airbyte.com/)オープンソースのデータ統合エンジンで、データウェアハウス、レイク、データベース内のデータの統合を支援する。
+> [Airbyte](https://airbyte.com/) は、データウェアハウス、データレイク、データベースにデータを統合するのに役立つオープンソースのデータ統合エンジンです。
 
-BrazeとAirbyteの統合により、ユーザーはデータパイプラインを作成し、すべてのアプリケーションとデータベースを中央倉庫に接続することで、Brazeのデータを収集・分析することができる。セントラルウェアハウスにデータが収集された後、データチームは好みのビジネスインテリジェンスツールを使ってBrazeのデータを効率的に探索することができる。
+BrazeとAirbyteの統合により、ユーザーはデータパイプラインを作成し、すべてのアプリケーションとデータベースを中央倉庫に接続することで、Brazeのデータを収集・分析することができる。中央ウェアハウスにデータが収集されると、データチームは好きなビジネスインテリジェンスツールを使って、Braze のデータを効率的に調査できます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| エアバイトクラウドアカウント | この統合を利用するには、[Airbyte Cloud](https://cloud.airbyte.io/workspaces)アカウントが必要である。 |
+| Airbyte Cloud アカウント | この統合を利用するには、[Airbyte Cloud](https://cloud.airbyte.io/workspaces)アカウントが必要である。 |
 | Braze REST API キー | すべての権限を持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント | \[あなたのRESTエンドポイントURL][1].エンドポイントは、インスタンスのBraze URLに依存する。 |
+| Braze RESTエンドポイント | \[REST エンドポイント URL][1]。エンドポイントは、インスタンスのBraze URLに依存する。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-1. Airbyte Cloudアカウントで、**Sources > + New Source > Set up Sourceに**移動する。
-2. ソース名に "Braze "と入力し、ソースのドロップダウンから**Brazeを**選択する。
-3. エンドポイントURL、Braze REST APIキー、開始日を入力する。**ソースの設定を**クリックする。
+1. Airbyte Cloud アカウントで **\[Sources] > \[+ New Source] > \[Set up the Source]** に移動します。
+2. ソース名として「Braze」を入力し、ソースのドロップダウンから \[**Braze**] を選択します。
+3. エンドポイント URL、Braze REST API キー、および開始日を指定します。\[**Set up Source**] をクリックします。
 
 ### 対応する同期モード
 
-AirbyteのBrazeソースコネクターは、以下の[シンクモードを](https://docs.airbyte.com/cloud/core-concepts#connection-sync-modes)サポートしている：
+Airbyte の Braze ソースコネクターは、以下の[同期モード](https://docs.airbyte.com/cloud/core-concepts#connection-sync-modes)をサポートしています。
 - **フル・リフレッシュ｜上書き**：ソースからすべてのレコードを同期し、デスティネーションのデータを上書きして置き換える。
-- **インクリメンタル同期｜アペンド**：ソースから新しいレコードを同期し、データを削除せずにデスティネーションに追加する。
+- **Incremental Sync | Append**:ソースから新しいレコードを同期し、データを削除せずに宛先に追加する。
 
-### 対応ストリーム
+### サポートされるストリーム
 
 - [`campaigns`](https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#f3b0b3ef-04fb-4a31-8570-e6ad88dacb18)
 - [`campaigns_analytics`](https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#c07b5ebd-0246-471e-b154-416d63ae28a1)
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/census.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/census.md
index 87763e9a198..3c3970b969d 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/census.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/census.md
@@ -10,53 +10,53 @@ search_tag: Partner
 
 # 国勢調査
 
-> [Censusは][1]、SnowflakeやBigQueryのようなクラウドデータウェアハウスをBrazeに接続するデータ活性化プラットフォームである。マーケティングチームは、ファーストパーティデータの力を解き放ち、ダイナミックなオーディエンスセグメントを構築し、顧客属性を同期してキャンペーンをパーソナライズし、Braze内のすべてのデータを最新の状態に保つことができる。CSVのアップロードやエンジニアの好意は必要ない。
+> [Census][1] は、Snowflake や BigQuery のようなクラウドデータウェアハウスを Braze に接続するデータアクティベーションプラットフォームです。マーケティングチームは、ファーストパーティデータの力を解き放ち、ダイナミックなオーディエンスセグメントを構築し、顧客属性を同期してキャンペーンをパーソナライズし、Braze内のすべてのデータを最新の状態に保つことができる。信頼できる実用的なデータで、これまで以上に簡単に行動を起こすことができます。CSV のアップロードやエンジニアの助力は必要ありません。
 
-BrazeとCensusの統合により、オーディエンスや製品データをBrazeに動的にインポートし、パーソナライズされたキャンペーンを送ることができる。例えば、Brazeで「CLV > 1000のニュースレター購読者」のコホートを作成し、価値の高い顧客をターゲットにしたり、「過去30日間にアクティブだったユーザー」のコホートを作成し、次期ベータ機能をテストする特定のユーザーをターゲットにすることができる。
+Braze と Census の統合により、オーディエンスや製品データを Braze にダイナミックにインポートし、パーソナライズされたキャンペーンを送信できます。例えば、Brazeで「CLV > 1000のニュースレター購読者」のコホートを作成し、価値の高い顧客をターゲットにしたり、「過去30日間にアクティブだったユーザー」のコホートを作成し、次期ベータ機能をテストする特定のユーザーをターゲットにすることができる。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | --- | --- |
-| 国勢調査アカウント | このパートナーシップを利用するには、[国勢調査のアカウントが][1]必要である。 |
-| Braze REST API キー | すべてのユーザーデータ権限（`users.delete` を除く）と`segments.list` 権限を持つ Braze REST API キー。Censusがより多くのBrazeオブジェクトのサポートを追加するにつれて、パーミッションのセットは変更される可能性がある。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに][2]依存する。 |
-| データウェアハウスとデータモデル | 統合を開始する前に、Censusでデータウェアハウスをセットアップし、Brazeと同期させたいデータのサブセットのモデルを定義しておく必要がある。利用可能なデータソースのリストとモデル作成に関するガイダンスについては、[国勢調査のドキュメントを](https://docs.getcensus.com/destinations/braze)参照のこと。 |
+| Census アカウント | このパートナーシップを活用するには、[Census アカウント][1]が必要です。 |
+| Braze REST API キー | すべてのユーザーデータ権限 (`users.delete` を除く) と `segments.list` 権限を持つ Braze REST API キー。Census でサポートされる Braze オブジェクトの増加に伴い、権限セットが変わる可能性があります。このため、この時点でより多くの権限を付与するか、これらの権限を今後更新する計画を立てることができます。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
+| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL][2] に応じて異なります。 |
+| データウェアハウスとデータモデル | 統合を開始する前に、Censusでデータウェアハウスをセットアップし、Brazeと同期させたいデータのサブセットのモデルを定義しておく必要がある。利用可能なデータソースのリストとモデル作成に関するガイダンスについては、[Census のドキュメント](https://docs.getcensus.com/destinations/braze)を参照してください。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 ## 統合
 
 ### ステップ1:Brazeサービス接続を作成する
 
-CensusプラットフォームでCensusを統合するには、**Connections**タブに移動し、**New Destinationを**選択して新しいBrazeサービス接続を作成する。
+Census プラットフォームで Census を統合するには、\[**Connections**] タブに移動し、\[**New Destination**] を選択して新しい Braze サービス接続を作成します。
 
-表示されるプロンプトで、この接続に名前を付け、BrazeエンドポイントURLとBraze REST APIキー（オプションで、コホートを同期するためのデータインポートキー）を入力する。
+表示されるプロンプトで、この接続に名前を付け、Braze エンドポイント URL と Braze REST API キー (オプションで、コホートを同期するためのデータインポートキー) を入力します。
 
 ![][8]{: style="max-width:60%;"}
 
 ### ステップ2:国勢調査の同期を作成する
 
-顧客をBrazeに同期させるには、同期を構築する必要がある。ここで、データを同期する場所と、2つのプラットフォーム間でどのようにフィールドをマッピングするかを定義する。
+顧客を Braze に同期するには、同期を作成する必要があります。ここで、データを同期する場所と、2つのプラットフォーム間でどのようにフィールドをマッピングするかを定義する。
 
-1. **Syncs**タブに移動し、**New Syncを**選択する。<br><br> 
-2. コンポーザーで、データウェアハウスからソース・データモデルを選択する。<br><br>
-3. モデルの同期先を設定する。同期先として**Brazeを**選択し、[サポートするオブジェクトタイプを](#supported-objects)選択する。<br>![Select a Destination "プロンプトでは、接続先として "Braze "が選択され、様々なオブジェクトがリストアップされる。][10]{: style="max-width:80%;"}<br><br>
-4. 適用したい同期ルールを選択する**（UpdateまたはCreateが**最も一般的な選択だが、データの削除など、より高度なルールを選択することもできる）。<br><br>
-5. 次に、レコードマッチングのために、Brazeオブジェクトをモデルフィールドに[マッピング](#supported-objects)するシンクキーを選択する。<br>![Select a Sync Key "プロンプトで、Brazeの "External User ID "がソースの "user_id "に一致する。][9]{: style="max-width:80%;"}<br><br>
-6. 最後に、国勢調査のデータフィールドを同等のBrazeフィールドにマッピングする。<br>![国勢調査マッピング][11]{: style="max-width:80%;"}<br><br>
+1. \[**Syncs**] タブに移動し、\[**New Sync**] を選択します。<br><br> 
+2. コンポーザーで、データウェアハウスからソースデータモデルを選択します。<br><br>
+3. モデルの同期先を設定する。宛先として \[**Braze**] を選択し、同期する[サポートされているオブジェクトタイプ](#supported-objects)を選択します。<br>![\[Select a Destination] プロンプトで接続として「Braze」が選択されており、さまざまなオプションが一覧表示されている。][10]{: style="max-width:80%;"}<br><br>
+4. 適用する同期ルールを選択します (\[**Update or Create**] が最も一般的な選択肢ですが、データの削除を処理するためのより詳細なルールを選択することもできます)。<br><br>
+5. 次に、レコードマッチングのために、Brazeオブジェクトをモデルフィールドに[マッピング](#supported-objects)するシンクキーを選択する。<br>![「Select a Sync Key」プロンプトで Braze の「External User ID」がソースの「user_id」に一致している。][9]{: style="max-width:80%;"}<br><br>
+6. 最後に、Census データフィールドを対応する Braze フィールドにマッピングします。<br>![Census でのマッピング][11]{: style="max-width:80%;"}<br><br>
 7. 詳細を確認し、シンクを作成する。 
 
 同期が実行されると、Brazeにユーザーデータが表示される。今後のBrazeキャンペーンやCanvasにBrazeセグメントを作成・追加して、これらのユーザーをターゲットにできるようになった。 
 
 {% alert note %}
-CensusとBrazeの統合を使用する場合、Censusは、各同期のデルタ（変更データ）のみをBrazeに送信する。
+Census と Braze の統合を使用する場合、Census は Braze との同期のたびに差分 (変更データ) のみを送信します。
 {% endalert %}
 
-## サポート対象
+## サポートされるオブジェクト
 
 Censusは現在、以下のBrazeオブジェクトの同期をサポートしている：
 
-| オブジェクト名 | シンクの動作 |
+| オブジェクト名 | 同期の動作 |
 | --- | --- |
 | ユーザー | 更新、作成、ミラー、削除 |
 | コホート | 更新、作成、ミラー | 
@@ -66,8 +66,8 @@ Censusは現在、以下のBrazeオブジェクトの同期をサポートして
 {: .reset-td-br-1 .reset-td-br-2}
 
 さらに、CensusはBrazeへの[構造化データの](https://docs.getcensus.com/destinations/braze#supported-objects)送信もサポートしている： 
-- ユーザーがトークンをプッシュする：プッシュトークンを送信するには、データを2-3の値を持つオブジェクトの配列として構造化する必要がある：`app_id` `token` 、そしてオプションで`device_id` 。
-- カスタム属性を入れ子にする：オブジェクトと配列の両方がサポートされている。2022年4月現在、この機能はまだ早期アクセスである。アクセスするには、Brazeのアカウントマネージャーに連絡する必要があるかもしれない。
+- ユーザープッシュトークン:プッシュトークンを送信するには、データを2-3の値を持つオブジェクトの配列として構造化する必要がある：`app_id` `token` 、そしてオプションで`device_id` 。
+- 階層化カスタム属性:オブジェクトと配列の両方がサポートされている。2022年4月現在、この機能はまだ早期アクセス段階です。アクセスするには、Brazeのアカウントマネージャーに連絡する必要があるかもしれない。
 
 [1]: https://www.getcensus.com/
 [2]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md
index 6329a3d8e95..25a3a965aad 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md
@@ -11,32 +11,32 @@ tool: Currents
 
 # Fivetran
 
-> [Fivetran](https://fivetran.com/) は、アナリストに焦点を当てた製品と完全に管理されたパイプラインにより、クラウドウェアハウスにクエリ可能なデータを提供することで、データに基づいた意思決定を可能にする世界的に認知されたブランドです。
+> [Fivetran](https://fivetran.com/) は世界的に認知されたブランドであり、アナリストに焦点を当てた製品と完全に管理されたパイプラインにより、クエリ可能なデータをクラウドウェアハウスに配信してデータに基づく意思決定を可能にします。
 
-BrazeとFivetranの統合により、すべてのアプリケーションとデータベースを中央のウェアハウスに接続することで、Brazeデータを収集および分析するためのメンテナンス不要のパイプラインを作成できます。データが中央倉庫に収集された後、データチームは好みのビジネスインテリジェンスツールを使用してBrazeデータを効果的に探索できます。 
+Braze とFivetran の統合により、ユーザーはメンテナンス不要のパイプラインを作成できます。このパイプラインにより、すべてのアプリケーションとデータベースを中央のウェアハウスに接続することで、Braze データを収集、分析できます。中央ウェアハウスにデータが収集されると、データチームは好きなビジネスインテリジェンスツールを使って、Braze のデータを効率的に調査できます。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
 | Fivetranアカウント | このパートナーシップを利用するには、[Fivetran](https://fivetran.com/login?next=%2Fdashboard)アカウントが必要です。 |
-| Braze REST API キー | 次の権限を持つBraze REST APIキー:<br>- users.export.ids<br>- users.export.segment<br>- email.unsubscribe<br>email.ハードバウンス<br>messages.スケジュール放送<br>- campaigns.list<br>- campaigns.details<br>- canvas.list<br>- canvas.details<br>- segments.list<br>- segments.details<br>purchases.製品リスト<br>- events.list<br>- feed.list<br>- feed.details<br>- templates.email.info<br>- templates.email.list<br>- subscription.status.get<br>- subscription.groups.get<br><br> これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。 |
+| Braze REST API キー | 次の権限を持つBraze REST APIキー:<br>- users.export.ids<br>- users.export.segment<br>- email.unsubscribe<br>- email.hard_bounces<br>- messages.schedule_broadcasts<br>- campaigns.list<br>- campaigns.details<br>- canvas.list<br>- canvas.details<br>- segments.list<br>- segments.details<br>- purchases.product_list<br>- events.list<br>- feed.list<br>- feed.details<br>- templates.email.info<br>- templates.email.list<br>- subscription.status.get<br>- subscription.groups.get<br><br> これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。 |
 | Braze REST エンドポイント  | あなたのRESTエンドポイントURL。エンドポイントは、[BrazeインスタンスのURL][1]によって異なります。 |
 | Braze Currents | [Braze Currents](https://www.braze.com/product/data-agility-management/currents/) は Amazon S3 または Google Cloud Storage のいずれかに接続する必要があります。 |
-| Amazon S3 または Google Cloud Storage | この統合には、Amazon S3 または Google Cloud Storage へのアクセスが必要です。 |
+| Amazon S3 または Google Cloud Storage | この統合では、1つの Amazon S3または Google Cloud Storage にアクセスできる必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2} 
 
 ## 統合
 
 次のCurrents統合は、[Amazon S3](#setting-up-braze-currents-for-s3)および[Google Cloud Storage](#setting-up-braze-currents-for-google-cloud-storage)の両方でサポートされています。
 
-### S3のためのBraze Currentsの設定
+### S3 向けの Braze Currents の設定
 
-#### ステップ1:外部ID {#step-one} を見つけてください
+#### ステップ1:external ID を確認する {#step-one}
 
-[Fivetran ダッシュボード](https://fivetran.com/dashboard)で、**\+ Connector**をクリックし、**Braze**コネクタを選択してセットアップフォームを起動します。次に、**Amazon S3**を選択します。ここに提供されたexternal IDに注意してください。FivetranがあなたのS3バケットにアクセスできるようにするために必要です。 
+[Fivetran ダッシュボード](https://fivetran.com/dashboard)で、**\+ Connector**をクリックし、**Braze**コネクタを選択してセットアップフォームを起動します。次に、**Amazon S3**を選択します。ここに示されている external ID に注意してください。これは、Fivetran が S3 バケットにアクセスできるようにするために必要です。 
 
-![FivetranのセットアップBrazeコネクタフォーム。このステップに必要なexternal IDフィールドは、ページの中央にある薄い灰色のボックスにあります。]({% image_buster /assets/img/fivetran_braze_setupform_as3.png %})
+![Fivetran の Braze コネクター設定フォーム。このステップに必要なexternal IDフィールドは、ページの中央にある薄い灰色のボックスにあります。]({% image_buster /assets/img/fivetran_braze_setupform_as3.png %})
 
 #### ステップ2:指定されたS3バケットへのアクセス権をFivetranに与える
 
@@ -74,7 +74,7 @@ BrazeとFivetranの統合により、すべてのアプリケーションとデ
 ```
 {% endraw %}
 
-最後に、**ポリシーを確認**をクリックし、ポリシーに一意の名前と説明を付けます。「ポリシーの作成」をクリックしてポリシーを作成します。 
+最後に、**ポリシーを確認**をクリックし、ポリシーに一意の名前と説明を付けます。\[**Create Policy**] をクリックしてポリシーを作成します。 
 
 ![]({% image_buster /assets/img/fivetran_iam_policy_meta.png %})
 
@@ -84,30 +84,30 @@ AWS で、**ロール** に移動し、**新しいロールを作成** を選択
 
 ![]({% image_buster /assets/img/fivetran_iam_new_role.png %})
 
-**別のAWSアカウント**を選択し、FivetranアカウントID`834469178297`を提供します。必ず**Require external ID**チェックボックスを確認してください。ここでは、ステップ1で見つかったexternal IDを提供します。
+\[**Another AWS Account**] を選択し、FivetranアカウントID `834469178297` を入力します。必ず**Require external ID**チェックボックスを確認してください。ここでは、ステップ1で見つかったexternal IDを提供します。
 
 ![]({% image_buster /assets/img/fivetran_another_aws_account.png %})
 
-次に、**次をクリックします。権限**を選択して、作成したポリシーを選択します。
+次に、\[**Next:権限**を選択して、作成したポリシーを選択します。
 
 ![]({% image_buster /assets/img/fivetran_as3_select_policy.png %})
 
-クリック **次へ:レビュー**、新しい役割に名前を付けます（例えば、Fivetran）、そして**役割を作成**をクリックします。ロールが作成された後、それをクリックして表示されるロールARNをメモします。
+\[**Next:Review**] をクリックして、新しいロールに名前を付け (Fivetran など)、\[**Create Role**] をクリックします。ロールが作成された後、それをクリックして表示されるロールARNをメモします。
 
 ![ロールに記載されているAmazon S3 ARNです。]({% image_buster /assets/img/fivetran_iam_role_arn.png %})
 
 {% alert note %}
-Fivetran用に指定するロールARNの権限を指定できます。このロールに選択的な権限を与えることで、Fivetranは権限を持つもののみを同期できるようになります。
+Fivetran に指定するロール ARN の権限を指定できます。このロールに選択的な権限を付与すると、Fivetran は、参照する権限を持つもののみを同期できます。
 {% endalert %}
 
-#### ステップ3:Fivetranコネクタを完了する
+#### ステップ3:Fivetran コネクターの設定を完了する
 
-Fivetranで、**\+ Connector**をクリックし、**Braze**コネクタを選択してセットアップフォームを起動します。フォーム内で、指定されたフィールドに適切な値を入力してください:
-- `Destination schema`:ユニークなスキーマ名。
+Fivetranで \[**+Connector**]をクリックし、**Braze** コネクターを選択して設定フォームを起動します。フォーム内で、指定されたフィールドに適切な値を入力してください:
+- `Destination schema`:一意のスキーマ名。
 - `API URL`:あなたのBraze REST APIエンドポイント。
 - `API Key`:あなたのBraze REST APIキー。 
 - `External ID`:Currentsセットアップ手順の[ステップ2](#step-two)で設定されたexternal ID。このIDは固定値です。
-- `Bucket`:Brazeアカウントで見つかりました。**統合 > Currents > \[あなたのCurrent名] > バケット名**に移動します。
+- `Bucket`:これは、**\[Integration] > \[Currents] > \[Your Currents name]> \[Bucket Name]** に移動して、Braze アカウントで確認できます。
 - `Role ARN`:現在のセットアップ手順の[ステップ1](#step-one)にロールARNが見つかります。
 
 {% alert important %}
@@ -116,31 +116,31 @@ Fivetranで、**\+ Connector**をクリックし、**Braze**コネクタを選
 
 最後に、**保存してテスト**をクリックすると、FivetranがBrazeアカウントのデータと同期して残りの作業を行います！
 
-### Google Cloud StorageのBraze Currentsの設定
+### Google Cloud Storage 向けの Braze Currents の設定
 
-#### ステップ1:Google Cloud Storage {#step-one2} から Fivetran メールを取得する
+#### ステップ1:Google Cloud Storage から Fivetran メールアドレスを取得する {#step-one2}
 
 [Fivetranダッシュボード](https://fivetran.com/dashboard)で、**\+ Connector**をクリックし、**Braze**コネクタを選択してセットアップフォームを起動します。次に、**Google Cloud Storage**を選択します。表示されるメールアドレスに注意してください。
 
-![FivetranのセットアップBrazeコネクタフォーム。このステップに必要なメールフィールドは、ページの中央にある薄い灰色のボックスにあります。]({% image_buster /assets/img/fivetran_braze_setupform_gcs.png %})
+![Fivetran の Braze コネクター設定フォーム。このステップに必要なメールフィールドは、ページの中央にある薄い灰色のボックスにあります。]({% image_buster /assets/img/fivetran_braze_setupform_gcs.png %})
 
 #### ステップ2:バケットアクセスを許可する
 
 [Google Storage Console](https://console.cloud.google.com/storage/browser) に移動し、Braze Currents で設定したバケットを選択して、**バケットの権限を編集** をクリックします。
 
-![Googleストレージコンソールで利用可能なバケット。バケットを見つけて、縦の3点シンボルをクリックして、バケットの権限を編集できるドロップダウンを開きます。]({% image_buster /assets/img/fivetran_edit_bucket_permissions_gcs.png %})
+![Google Storage Console で利用可能なバケット。バケットを見つけて、縦の3点シンボルをクリックして、バケットの権限を編集できるドロップダウンを開きます。]({% image_buster /assets/img/fivetran_edit_bucket_permissions_gcs.png %})
 
-次に、`Storage Object Viewer`に[ステップ1](#step-one2)のメールへのアクセス権を付与し、メールをメンバーとして追加します。バケット名をメモしておいてください。次のステップでFivetranを設定する必要があります。
+次に、[ステップ1](#step-one2)のメールアドレスに `Storage Object Viewer` アクセス権を付与するため、メールアドレスをメンバーとして追加します。バケット名をメモしておいてください。次のステップで Fivetran を設定するときに必要となります。
 
 ![]({% image_buster /assets/img/fivetran_add_members_gcs.png %})
 
-#### ステップ 3:Fivetranコネクタを完了する
+#### ステップ 3:Fivetran コネクターの設定を完了する
 
-Fivetranで、**\+ Connector**をクリックし、**Braze**コネクタを選択してセットアップフォームを起動します。フォーム内で、指定されたフィールドに適切な値を入力してください:
-- `Destination schema`:ユニークなスキーマ名。
+Fivetranで \[**+Connector**]をクリックし、**Braze** コネクターを選択して設定フォームを起動します。フォーム内で、指定されたフィールドに適切な値を入力してください:
+- `Destination schema`:一意のスキーマ名。
 - `API URL`:あなたのBraze REST APIエンドポイント。
 - `API Key`:あなたのBraze REST APIキー。 
-- `Bucket Name`:Brazeアカウントで見つかりました。**統合 > Currents > \[あなたのCurrent名] > バケット名**に移動します。
+- `Bucket Name`:これは、**\[Integration] > \[Currents] > \[Your Currents name]> \[Bucket Name]** に移動して、Braze アカウントで確認できます。
 - `Folder`:Brazeアカウントで、**Integration > Currents > \[Your Current name] > Prefix**に移動して見つけることができます。
 
 {% alert important %}
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/growthloop.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/growthloop.md
index e62a02b4d82..361c537036c 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/growthloop.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/growthloop.md
@@ -10,22 +10,22 @@ search_tag: Partner
 
 # GrowthLoop
 
-> [GrowthLoopは](https://growthloop.com/)、マーケティングチームが顧客データをクラウドデータウェアハウスからBrazeやその他のチャネルに有効化するのを支援する。クラウドデータウェアハウスからマーケティングプログラムを自動化、拡張、測定し、データを一元管理する。
+> [GrowthLoop](https://growthloop.com/) は、クラウドデータウェアハウスから Braze やその他のチャネルへの顧客データを活性化するマーケティング チームを支援します。クラウドデータウェアハウスからマーケティングプログラムを自動化、スケーリング、測定し、データを一元管理します。
 
-BrazeとGrowthLoopの統合により、データウェアハウスから直接顧客データをセグメント化し、Brazeに送信することができる。顧客セグメンテーションとアクティベーションのためのマーケティング活動を合理化し、Brazeに送られたターゲットキャンペーンのセグメンテーション、ローンチ、テスト、結果測定にかかる時間を短縮する。
+Braze と GrowthLoop の統合により、データウェアハウスから直接顧客データをセグメント化して Braze に送信できます。これにより、ユーザーは Braze の豊富な機能セットを、信頼できる唯一の情報源とともに最適化できます。顧客セグメンテーションとアクティベーションのためのマーケティング活動を合理化し、Brazeに送られたターゲットキャンペーンのセグメンテーション、ローンチ、テスト、結果測定にかかる時間を短縮する。
 
 ## 前提条件 
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| GrowthLoop グロースアカウントまたはエンタープライズアカウント | このパートナーシップを利用するには、GrowthLoopのアカウントが必要である。 |
+| GrowthLoop の growth アカウントまたは enterprise アカウント | このパートナーシップを利用するには、GrowthLoopのアカウントが必要である。 |
 | Braze Rest APIキー | すべての権限を持つBraze REST APIキー。<br><br>これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに][2]依存する。|
+| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL][2] に応じて異なります。|
 {: .reset-td-br-1 .reset-td-br-2} 
 
 ## ユースケース
 
-データウェアハウスからBrazeに顧客リストを送信し、Eメールやプッシュ通知キャンペーンをワンクリックでターゲティング。
+データウェアハウスから Braze に顧客リストを送信し、ワンクリックでメールキャンペーンやプッシュ通知キャンペーンのターゲット設定を行い、常に同期を維持できます。
 
 - サインアップアクティベーションに基づくEメール - サインアップフローから外れたユーザーをアクティブユーザーに変えるためにEメールを送る。
 - あらゆるユーザーの行動に基づいたメール - "カートに入れる "など、ユーザーの行動に基づいてメールを送信する。
@@ -35,28 +35,28 @@ BrazeとGrowthLoopの統合により、データウェアハウスから直接
 
 ### GrowthLoopでBraze接続を設定する
 
-GrowthLoop の Segmentation Platform にサインインしたら、左サイドバーの**Destinations**タブを開き、右上の**New Destination**をクリックする。
+GrowthLoop の Segmentation Platform にサインインしたら、左サイドバーの \[**Destinations**] タブを開き、右上の \[**New Destination**] をクリックします。
 
-Brazeが見つかるまでスクロールし、**Add Brazeを**クリックする。
+Braze が見つかるまでスクロールし、\[**Add Braze**] をクリックします。
 
 宛先への接続を設定するポップアップが表示される。
 
-- **デスティネーション名である**：これが、今後アプリ内で目的地がどのように命名され、どのように参照されるかである。
-- **同期周波数**：GrowthLoopがオーディエンスをBrazeにエクスポートする頻度をコントロールする。
-- **APIキー**：要件で作成したAPIキーに必要な権限を付与する。
-- **APIのURL**：要件で定義されているURL
+- **Destination name**:これは宛先に指定される名前であり、今後アプリでこの宛先はこの名前で参照されます。
+- **同期周波数**：\[Daily] または \[Hourly] を選択します。これにより、GrowthLoop がオーディエンスを Braze にエクスポートする頻度が制御されます。
+- **APIキー**：要件で作成した、必要な権限を持つ API キー。
+- **API URL**:要件で定義されているURL
 
-**Createを**クリックすると、最初のオーディエンスをBrazeにエクスポートできる！GrowthLoopでオーディエンスを作成するには、[Create an Audienceを](https://www.growthloop.com/help-center-articles/create-an-audience)参照のこと。
+\[**Create**] をクリックします。これで最初のオーディエンスを Braze にエクスポートできます。GrowthLoop でオーディエンスを作成するには、[オーディエンスの作成](https://www.growthloop.com/help-center-articles/create-an-audience)を参照してください。
 
-### ポストの輸出
+### エクスポート後の作業
 
-顧客リストがエクスポートされると、15分毎にGrowthLoopが顧客リストの更新版を生成し、Brazeに送信する。
+顧客リストがエクスポートされたら、GrowthLoop が15分ごとに最新の顧客リストを生成して Braze に送信します。
 
-同時に、GrowthLoopは、もはや適格でないユーザーをオーディエンスから削除し、新たに適格なユーザーをオーディエンスに追加する。 
+同時に GrowthLoop は、条件を満たさなくなったユーザーをオーディエンスから削除し、新たに条件を満たしているユーザーをオーディエンスに追加します。 
 
-Brazeはユーザーをマッチングし、GrowthLoopのオーディエンスの一員であることを示すフラグを作成する。
+Braze はユーザーを照合し、ユーザーが GrowthLoop のオーディエンスに含まれていることを示すフラグを作成します。
 
-Brazeでキャンペーンを作成する際、GrowthLoopのオーディエンスから顧客を選択することができる。 
+Braze でキャンペーンを作成するときに、その GrowthLoop オーディエンスから顧客を選択できます。 
 
 ## トラブルシューティング
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch.md
index 0c79fc9e40b..b5cfe76e3df 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch.md
@@ -3,7 +3,7 @@ nav_title: Hightouch
 alias: /partners/hightouch/
 layout: dev_guide
 guide_top_header: "Hightouch"
-guide_top_text: "ハイタッチはデータウェアハウスの上に置かれ、ユーザーが望むあらゆるエンドツールにデータを移動できるようにする。"
+guide_top_text: "Hightouch はデータウェアハウスの上に設置され、ユーザーが望むあらゆるエンドツールへのデータの移動を可能にします。"
 description: "このランディングページは、統合ガイダンスやHightouchパーソナライゼーションAPIの概要など、Hightouchに関するあらゆる情報が掲載されている。"
 
 guide_featured_list:
@@ -13,7 +13,7 @@ guide_featured_list:
 - name: Hightouch Cohort Import
   link: /docs/partners/data_and_infrastructure_agility/cohort_import/hightouch/
   image: /assets/img/braze_icons/users-01.svg
-- name: ハイタッチ・パーソナライゼーションAPI
+- name: Hightouch Personalization API
   link: /docs/partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch_personalization_api/
   image: /assets/img/braze_icons/building-01.svg
 ---
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch.md
index 03ca7a180f1..556370fc69b 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Hightouch
 article_title: Hightouch
-description: "この参考記事では、BrazeとHightouchのパートナーシップについて概説している。Hightouchは、顧客データを倉庫からビジネスツールに同期させるプラットフォームである。"
+description: "このリファレンス記事では、Braze と Hightouchのパートナーシップについて説明します。Hightouch は、ウェアハウスの顧客データをカスタムツールと同期するプラットフォームです。"
 page_type: partner
 search_tag: Partner
 
@@ -9,9 +9,9 @@ search_tag: Partner
 
 # Hightouch
 
-> [Hightouchは][1]、最新のデータ統合プラットフォームであり、倉庫やデータレイクから任意のアプリケーションに顧客、製品、または独自のデータを同期させることができる。
+> [Hightouch][1] は最新のデータ統合プラットフォームであり、IT チームやエンジニアリングチームの支援を必要とせずに、ウェアハウスやデータレイクからお客様が選択したアプリに、顧客データ、製品データ、または独自のデータを同期できます。
 
-BrazeとHightouchの統合により、データウェアハウスからの最新の顧客データを使って、Braze上でより良いキャンペーンを構築することができる。顧客データを自動的にBrazeに同期させることで、データの整合性を心配する必要がなくなり、ワールドクラスの顧客体験の構築に集中することができる。 
+Braze と Hightouch の統合により、データウェアハウスの最新の顧客データを使用して、Braze でより優れたキャンペーンを作成できます。顧客データを Braze に自動的に同期させることで、データの整合性を心配する必要がなくなり、世界レベルのカスタマーエクスペリエンスの構築に集中して取り組むことができます。 
 
 この統合により、[ユーザーコホートをBrazeにインポート]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/hightouch/)し、倉庫にしか存在しないデータに基づいてターゲットを絞ったキャンペーンを送信することもできる。
 
@@ -19,49 +19,49 @@ BrazeとHightouchの統合により、データウェアハウスからの最新
 
 | 必要条件 | 説明 |
 |---|---|
-| ハイタッチアカウント | このパートナーシップを利用するには、ハイタッチ・アカウントが必要である。
-| Braze REST API キー | `users.track` および`users.export.ids` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに][2]依存する。<br><br>Hightouchは、Brazeインスタンスのクラスタ名を要求する。例えば、Brazeのエンドポイントが`https://rest.iad-01.braze.com` の場合、必要なのは`iad-01` だけである。|
+| Hightouch アカウント | このパートナーシップを活用するには、Hightouch アカウントが必要です。
+| Braze REST API キー | `users.track` および `users.export.ids` の権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
+| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL][2] に応じて異なります。<br><br>Hightouch には、Braze インスタンスが配置されているクラスターの名前が必要です。例えば、Brazeのエンドポイントが`https://rest.iad-01.braze.com` の場合、必要なのは`iad-01` だけである。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
 * ユーザーとアカウントに関するデータをBrazeに同期し、超パーソナライズされたキャンペーンを構築する。
-* Brazeセグメントをウェアハウスからの新鮮なデータで自動的に更新する。
+* Braze セグメントをウェアハウスからの最新データで自動的に更新する。
 * 他の顧客接点からのデータをBrazeに取り込むことで、より良い体験を提供する。
 * ユーザーのコホートをBrazeにインポートし、ターゲットを絞ったキャンペーンやキャンバスを送信できる。 
 
 ## 統合
 
-### ステップ1:ハイタッチ・ブレイズの目的地を作る
+### ステップ1:Hightouch Braze 宛先を作成する
 
-1. ハイタッチ・プラットフォームの**宛先**セクションで、**宛先の追加を**クリックする。
+1. Hightouch プラットフォームの \[**Destinations**] セクションで \[**Add destination**] をクリックします。
 2. 利用可能な目的地のリストから**Brazeを**選択する。
-3. Braze RESTエンドポイント（"https://rest. "を除く）とBraze REST API Keyを入力する。<br><br>![][3]
+3. Braze REST エンドポイント (「https://rest」を除く) と Braze REST API キーを指定します。<br><br>![][3]
 
 ### ステップ2:オブジェクトとイベントの同期
 
-ハイタッチは、ユーザー・オブジェクトとイベントの両方への同期をサポートしている。
+Hightouch では、ユーザーオブジェクトとイベントの両方の同期がサポートされています。
 
-| 目的地 | 説明 | 対応モード |
+| 目的地 | 説明 | サポートされているモード |
 |---|---|---|
-| オブジェクト | 同期先のユーザーや組織などのオブジェクトにレコードを同期する。| アップサートまたはアップデート |
-| イベント | これは多くの場合、トラック・コールの形式である。 | サーキット・イベントまたはサーキット購入 |
+| オブジェクト | 宛先のユーザーや組織などのオブジェクトにレコードを同期します。| アップサートまたはアップデート |
+| イベント | レコードをイベントとして宛先に同期します。これは多くの場合、トラックコールの形式です。 | イベントまたは購入の追跡 |
 
 {% alert note %}
-同期がBrazeのデータポイント消費にどのように影響するかについての詳細は、[Hightouchを](https://hightouch.com/docs/destinations/braze#syncing-and-data-point-consumption)参照のこと。
+同期が Braze データポイントの消費に与える影響の詳細については、[Hightouch](https://hightouch.com/docs/destinations/braze#syncing-and-data-point-consumption)を参照してください。
 {% endalert %}
 
 #### Brazeオブジェクトを同期する
 
-Hightouchオブジェクト（ユーザーフィールド）を同等のBrazeデフォルトまたはカスタムフィールドに同期できる。また、レコードマッチングを実行して、2つのプラットフォーム間でデータを統一することもできる。
+Hightouchオブジェクト（ユーザーフィールド）を同等のBrazeデフォルトまたはカスタムフィールドに同期できる。2つのプラットフォーム間でデータを統合するためにレコードマッチングを実行することもできます。
 
 #### Brazeのイベントを同期する
 
-ハイタッチでは、イベントや購買データを追跡し、Brazeと同期させることができる。Hightouchでは、トラッキングデータの設定や存在しないユーザー動作の定義など、同期動作に影響を与えるいくつかのオプションを設定できる。
+Hightouch では、イベントデータと購入データを追跡し、これらのデータを Braze に同期できます。Hightouchでは、トラッキングデータの設定や存在しないユーザー動作の定義など、同期動作に影響を与えるいくつかのオプションを設定できる。
 
 {% alert important %}
-オブジェクトとイベントの同期に関する詳しい説明は、[Hightouchのドキュメントを](https://hightouch.io/docs/destinations/braze/)参照されたい。
+オブジェクトとイベントの同期に関する詳細な手順については、[Hightouch のドキュメント](https://hightouch.io/docs/destinations/braze/)を参照してください。
 {% endalert %}
 
 
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch_personalization_api.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch_personalization_api.md
index 4d711180a41..e1a53b610c2 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch_personalization_api.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/hightouch/hightouch_personalization_api.md
@@ -1,20 +1,20 @@
 ---
-nav_title: ハイタッチ・パーソナライゼーションAPI
-article_title: ハイタッチ・パーソナライゼーションAPI
-description: "この参考記事では、BrazeとHightouchのPersonalization APIとの統合について概説している。Personalization APIは、クラウドデータウェアハウス内の任意のデータセットに基づく低遅延データAPIをホスティングするマネージドサービスである。このリファレンス記事では、Hightouch Personalization APIが解決するユースケース、使用するデータ、設定方法、Brazeとの統合方法について説明する。"
+nav_title: Hightouch Personalization API
+article_title: Hightouch Personalization API
+description: "このリファレンス記事では、Braze と Hightouch の Personalization API の統合について説明します。この API は、クラウドデータウェアハウス内のデータセットに基づいて低レイテンシーのデータ API をホストするためのマネージドサービスです。このリファレンス記事では、Hightouch Personalization APIが解決するユースケース、使用するデータ、設定方法、Brazeとの統合方法について説明する。"
 page_type: partner
 search_tag: Partner
 ---
 
-# ハイタッチ・パーソナライゼーションAPI
+# Hightouch Personalization API
 
-> Hightouchの[パーソナライゼーションAPIは](https://hightouch.com/docs/destinations/personalization-api)、クラウドデータウェアハウス内の任意のデータセットに基づく低遅延データAPIをホストできるマネージドサービスである。
+> Hightouch の [Personalization API](https://hightouch.com/docs/destinations/personalization-api) は、クラウドデータウェアハウスのデータセットに基づいて低レイテンシーのデータAPI をホストできるようにするマネージドサービスです。
 
 ![][3]
 
-BrazeとHightouchの統合により、[Braze Connected Contentで](https://www.braze.com/docs/user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call/)APIを使用し、送信時にキャンペーンやCanvasに最新の顧客データやオブジェクトデータを取り込むことができる。
+Braze と Hightouch の統合により、[Braze コネクテッドコンテンツ](https://www.braze.com/docs/user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call/)とこの API を使用して、送信時に最新の顧客またはオブジェクトのデータをキャンペーンまたはキャンバスに取り込むことができます。
 
-HightouchのPersonalization APIは、Braze設定内で使用するRESTエンドポイントを提供する。具体的には、BrazeのConnected Contentオファリングを使用して、Personalization APIにGETリクエストを行い、特定の識別子に関連するすべての情報を取得することができる。このAPIによって公開されるデータは、顧客、製品、またはその他のオブジェクトデータを表すことができる。 
+Hightouch の Personalization API は、Braze の設定で使用する REST エンドポイントを提供します。具体的には、Braze のコネクテッドコンテンツを使用して Personalization API に対する GET リクエストを実行し、特定の識別子に関連するすべての情報を取得できます。この API によって公開されるデータは、顧客、製品、またはその他のオブジェクトデータを表す場合があります。 
 
 ![][2]
 
@@ -22,10 +22,10 @@ HightouchのPersonalization APIは、Braze設定内で使用するRESTエンド
 
 | 必要条件| 説明|
 | ---| ---| 
-| パーソナライゼーションAPIを有効にした[Hightouchアカウント](https://app.hightouch.com/login) | このパートナーシップを利用するには、[ハイタッチ・ビジネス・ティア・アカウントが](https://hightouch.com/pricing)必要である。|
-| 定義されたユースケース | APIをセットアップする前に、この統合のユースケースを決定しなければならない。一般的な使用例については、以下のリストを参照のこと。 |
-| クラウドデータウェアハウスまたはその他のソースに保存されているデータ | ハイタッチは[25以上のデータソースと](https://hightouch.com/integrations)統合する |
-| ハイタッチAPIキー | これは、**ハイタッチ＞設定＞APIキー＞APIキーの追加で**作成できる。 |
+| パーソナライゼーションAPIを有効にした[Hightouchアカウント](https://app.hightouch.com/login) | このパートナーシップを活用するには、[Business Tier アカウント](https://hightouch.com/pricing)が必要です。|
+| 定義されたユースケース | API を設定する前に、この統合のユースケースを決定しておく必要があります。一般的な使用例については、以下のリストを参照のこと。 |
+| クラウドデータウェアハウスなどのソースに保存されているデータ | Hightouch は、[25以上のデータソース](https://hightouch.com/integrations)と統合しています。 |
+| ハイタッチAPIキー | これは、**\[Hightouch] > \[Settings] > \[API keys] > \[Add API key]** 内で作成できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% tabs %}
@@ -36,17 +36,17 @@ HightouchのPersonalization APIは、Braze設定内で使用するRESTエンド
 始める前に、パーソナライゼーションAPIをどのように使いたいかを正確に計画しておくと便利だ。
 
 一般的な使用例には以下のようなものがある：
-- メールテンプレート、キャンペーン、アプリ内エクスペリエンスにパーソナライズされたおすすめ**商品を**埋め込むことを効率化する。
-- マーケティング・タッチポイントをダイナミックな商品レコメンデーションで充実さ**せる**ことで、**パーソナライズされたマーケティング・キャンペーンを強力に推進する**。
+- メールテンプレート、キャンペーン、アプリ内エクスペリエンスへのパーソナライズされた製品レコメンデーションの埋め込むみを効率化する**製品レコメンデーション**
+- ダイナミックな製品レコメンデーションでマーケティングタッチポイントを充実させることで**パーソナライズされたマーケティングキャンペーンを強化する**
 - 例えば、カスタマイズされた検索結果、コホートベースの価格設定、メッセージング、おすすめ記事、最寄りの店舗など、**アプリ内またはウェブでパーソナライゼーションを提供する**。
-- **財務データや医療データに基づく推薦-財務**データには厳しい要件があり、ハイタッチは[厳格なデータ・セキュリティ・ポリシーによって](https://hightouch.com/docs/security/overview#compliance)これを満たしている。Hightouchを使用すると、セグメンテーション基準で使用される基本的な属性を公開することなく、財務データや医療データに基づいて顧客セグメントを作成することができる。
+- **財務データまたは医療データに基づくレコメンデーション** \- 財務データに厳しい要件があり、Hightouch はその[厳格なデータセキュリティポリシー](https://hightouch.com/docs/security/overview#compliance)によってこれらの要件を満たします。Hightouch を使用すると、セグメンテーション基準で使用される基本的な属性を公開せずに、財務データまたは医療データに基づいて顧客セグメントを作成できます。
 
 {% endtab %}
 {% tab データセット %}
 
 ### データセット
 
-パーソナライゼーションAPIは、ウェアハウス内の選択されたデータのキャッシュとして機能するため、レコメンデーションデータはすでにそこに保存されているはずだ。必要であれば、ハイタッチを使ってテンプレートに従って変形させることができる。この種のデータには以下が含まれる：
+パーソナライゼーションAPIは、ウェアハウス内の選択されたデータのキャッシュとして機能するため、レコメンデーションデータはすでにそこに保存されているはずだ。必要に応じて、Hightouch を使用してテンプレートに従って変換できます。この種のデータには以下が含まれる：
 - 地理的地域、年齢、その他の人口統計学的情報などのユーザー・メタデータ
 - 過去の購入、ページビュー、クリックなどのユーザーアクションやイベント。
 
@@ -55,50 +55,50 @@ HightouchのPersonalization APIは、Braze設定内で使用するRESTエンド
 
 ## 統合
 
-### ステップ1:データソースをハイタッチに接続する
+### ステップ1:データソースを Hightouch に接続する
 
-[ハイタッチ・ソースは](https://hightouch.com/docs/getting-started/concepts#sources)、組織のビジネス・データが存在する場所である。この場合、ユーザーデータが保存されている場所であればどこでもいい。
-1. ハイタッチで、「**ソースの概要」＞「ソースの追加**」と進む。ソースとしてデータウェアハウスを選択する。<br><br>
+[ハイタッチ・ソースは](https://hightouch.com/docs/getting-started/concepts#sources)、組織のビジネス・データが存在する場所である。この場合、ユーザーデータが保存されている場所はどこでもかまいません。
+1. ハイタッチで、「**ソースの概要」＞「ソースの追加**」と進む。ソースとしてデータウェアハウスを選択します。<br><br>
 2. 関連する認証情報を入力する。これらはソースによって異なる。 
 
-詳細については、関連するソース・[ドキュメントを](https://hightouch.com/docs)参照のこと。
+詳細については、関連するソースの[ドキュメント](https://hightouch.com/docs)を参照してください。
 
 ### ステップ2:モデルデータ
 
 ハイタッチ・モデルは、ソースからどのようなデータを引き出すかを定義する。新しいモデルをセットアップするには、以下の手順に従う：
 
-1. ハイタッチでは [**モデルの概要**](https://app.hightouch.com/models)**> モデルを追加**]を選択し、先ほど接続したソースを選択する。<br><br>
-2. 次に、[モデリング方法を](https://hightouch.com/docs/models/creating-models)選択する。すべての情報を1つのテーブルにまとめる必要があるので、ビジュアル・テーブル・セレクタを使って定義することができる。あるいは、必要なカラムだけを含むSQLを書いたり、既存のdbtモデル、ルッカー・ルック、シグマ・ワークブックに頼ることもできる。<br><br>
-3. 続行する前に、モデルをプレビューして、興味のあるデータを照会していることを確認する。デフォルトでは、Brazeはプレビューを最初の100レコードに制限している。データを確認したら、**Continueを**クリックする。<br><br>
+1. Hightouch で \[[**Models overview**](https://app.hightouch.com/models)] > \[**Add model**] に移動し、接続したソースを選択します。<br><br>
+2. 次に[モデリング方法](https://hightouch.com/docs/models/creating-models)を選択します。すべての情報を1つのテーブルにまとめる必要があるので、ビジュアル・テーブル・セレクタを使って定義することができる。あるいは、必要なカラムだけを含むSQLを書いたり、既存のdbtモデル、ルッカー・ルック、シグマ・ワークブックに頼ることもできる。<br><br>
+3. 続行する前に、モデルをプレビューして、興味のあるデータを照会していることを確認する。デフォルトでは、Brazeはプレビューを最初の100レコードに制限している。データを検証したら、\[**Continue**] をクリックします。<br><br>
 4. 例えば、"User recommendations "のように、モデルに名前をつける。<br><br>
-5. 最後に、主キーを選択し、**Finishを**クリックする。主キーは一意な識別子を持つカラムでなければならない。これは、パーソナライゼーションAPIを呼び出して特定のユーザーのおすすめを取得するために使用するフィールドでもある。
+5. 最後に主キーを選択し、\[**Finish**] をクリックします。主キーは、一意の識別子を持つ列である必要があります。これは、特定のユーザーのレコメンデーションを取得するために Personalization API を呼び出すときに使用するフィールドでもあります。
 
 ### ステップ3:パーソナライゼーションAPIを設定する
 
-リクエストを受け取るためにAPIを準備するには、2つのステップがある：
+API でリクエストを受信するための準備は、次の2つのステップからなります。
 - お客様のインフラに最も近い地域でパーソナライゼーションAPIを有効にする
 - Hightouchが管理するキャッシュで実体化されるべきモデルを定義するためにシンクを作成する。
 
 以下の指示に従って、両方を完了させる：
 
 1. ハイタッチでは [**目的地**](https://app.hightouch.com/destinations)を選択し、あなたのために作成されたHightouchパーソナライゼーションAPIを選択する。この宛先が有効になっていない場合は、[ハイタッチ・サポートに](mailto:friends@hightouch.com)連絡すること。<br><br>
-2. 次に、適切な地域を選択する。インフラに最も近い地域を選択することで、応答時間を短縮することができる。お住まいのインフラに近い地域が表示されない場合は、[ハイタッチ・サポートまで](mailto:friends@hightouch.com)ご連絡を。<br><br>
-3. [**シンクの**概要ページに](https://app.hightouch.com/syncs)移動し、**シンクを追加**ボタンをクリックする。次に、該当するモデルと、以前に設定した保存先を選択する。<br><br> 
-4. 英数字のコレクション名を入力する。コレクションは概念的にはデータベースのテーブルに似ている。それぞれ、顧客や請求書など、特定のデータ型を表す必要がある。コレクション名は英数字でなければならず、Personalization APIエンドポイントの一部となる。<br><br>
-5. 次に、モデルのどのカラムをレコード検索のプライマリー・インデックスとして使用するかを指定する。このフィールドは、コレクション内の各レコードを一意に識別する必要があり、多くの場合、モデルの主キーと同じである。パーソナライゼーションAPIは、複数のインデックスの検索をサポートする。例えば、`user_id` 、`anonymous_id` 、`email_address` を使って顧客プロファイルを検索したい。複数のインデックスを有効にするには、[ハイタッチ・サポートに](mailto:friends@hightouch.com)連絡すること。<br><br>
+2. 次に、適切な地域を選択する。インフラに最も近い地域を選択することで、応答時間を短縮することができる。インフラストラクチャに近いリージョンが表示されない場合は、[Hightouch サポート](mailto:friends@hightouch.com)にお問い合わせください。<br><br>
+3. [\[**Syncs**] 概要ページ](https://app.hightouch.com/syncs)に進み、\[**Add sync**] ボタンをクリックします。次に、該当するモデルと、以前に設定した宛先を選択します。<br><br> 
+4. 英数字のコレクション名を入力します。コレクションは概念的にはデータベースのテーブルに似ている。各コレクションは特定のデータタイプ (顧客や請求書など) を表します。コレクション名には英数字のみを使用する必要があります。コレクション名は、Personalization API エンドポイントの一部になります。<br><br>
+5. 次に、モデルのどの列をレコード検索の一次インデックスとして使用するかを指定します。このフィールドは、コレクション内の各レコードを一意に識別する必要があり、多くの場合、モデルの主キーと同じである。パーソナライゼーションAPIは、複数のインデックスの検索をサポートする。たとえば、`user_id`、`anonymous_id`、または `email_address` を使用して顧客プロファイルを取得できます。複数のインデックスを有効にする場合は、[Hightouch サポート](mailto:friends@hightouch.com)にご連絡ください。<br><br>
 6. フィールドマッパーを使用して、APIレスポンスペイロードに含まれるべきモデルのカラムを指定する。これらのフィールドの名前を変更し、リキッドテンプレート言語を使用して変換を適用するために高度なマッパーを使用することができる。<br><br>
-7. ユースケースに適した[削除動作を](https://www.hightouch.com/docs/destinations/personalization-api#delete-behavior)選択する。<br><br>
-8. 最後に、「**続ける**」をクリックし、[同期スケジュールを](https://hightouch.com/docs/syncs/schedule-sync-ui)選択する。
+7. ユースケースに適した[削除動作](https://www.hightouch.com/docs/destinations/personalization-api#delete-behavior)を選択します。<br><br>
+8. 最後に \[**Continue**] をクリックし、[同期スケジュール](https://hightouch.com/docs/syncs/schedule-sync-ui)を選択します。
 
-Hightouchは、ウェアハウスのデータを管理データベースに同期し、パーソナライゼーションAPIを介して公開する。
+Hightouch は、ウェアハウス内のデータをマネージドデータベースに同期し、Personalization API を介して公開します。
 
 ### ステップ4:Braze Connected Contentを通じてパーソナライゼーションAPIを呼び出す
 
 パーソナライゼーションAPIインスタンスを設定したら、それをBraze Connected Contentのエンドポイントとして使用できる。 
 
-APIは`https://personalization.{region}.hightouch.com` 、例えば`https://personalization.us-west-2.hightouch.com` からアクセスできる。 
+API は、`https://personalization.{region}.hightouch.com` でアクセスできます (例: `https://personalization.us-west-2.hightouch.com`)。 
 
-情報はこのエンドポイント`/v1/collections/:collection_name/records/:index_key/:index_value` を使って入手できる。
+情報はエンドポイント `/v1/collections/:collection_name/records/:index_key/:index_value` を使用して取得できます。
 
 例えば、キャンペーンやキャンバスにこのスニペットを入れることができる：
 
@@ -163,18 +163,18 @@ APIは`https://personalization.{region}.hightouch.com` 、例えば`https://pers
 }
 ```
 
-次のリキッド参照は、この例のデータを返すだろう：
+以下の Liquid リファレンスは、この例のデータを戻します。
 
-| 液体テンプレート | 返却例 |
+| 液体テンプレート | 戻されるデータの例 |
 | --- | --- |
-| {% raw %}`{{artists.recommendations.concerts[0].artist}}`{% endraw %}| エイフェックス・ツイン |
+| {% raw %}`{{artists.recommendations.concerts[0].artist}}`{% endraw %}| Aphex Twin |
 | {% raw %}`{{artists.recommendations.concerts[0].location}}`{% endraw %}| カリフォルニア州サンフランシスコ |
-| {% raw %}`{{artists.recommendations.upcoming_album_release.title}}`{% endraw %}| ユニバーサル・ランゲージ |
+| {% raw %}`{{artists.recommendations.upcoming_album_release.title}}`{% endraw %}| Universal Language |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## トラブルシューティング
 
-質問がある場合は、[ハイタッチ・サポートに](mailto:friends@hightouch.com)問い合わせること。
+ご質問がある場合は、[Hightouch サポート](mailto:friends@hightouch.com)までお問い合わせください。
 
 [1]: {% image_buster /assets/img/hightouch/cohort5.png %}
 [2]: {% image_buster /assets/img/hightouch/cohort6.png %}  
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/metarouter.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/metarouter.md
index 690561f56ac..b408a441cba 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/metarouter.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/metarouter.md
@@ -1,29 +1,29 @@
 ---
-nav_title: メタ・ルーター
-article_title: メタ・ルーター
-description: "MetaRouterでBrazeの顧客データ管理を向上させよう。この高性能なサーバーサイド・タグ管理ソリューションは、MetaRouterがホストするプライベートクラウド上でも、独自のインフラ上でも、シームレスな展開オプションで最大限のコンプライアンスとコントロールを提供する。"
+nav_title: MetaRouter
+article_title: MetaRouter
+description: "MetaRouter を使用して、Braze で顧客データ管理を強化します。この高性能なサーバーサイドタグ管理ソリューションは、MetaRouter がホストするプライベートクラウドでもお客様のインフラストラクチャでも、シームレスな導入オプションによって最大限のコンプライアンスと制御を提供します。"
 alias: /partners/MetaRouter/
 page_type: partner
 search_tag: Partner
 ---
 
-# メタ・ルーター
+# MetaRouter
 
-> [MetaRouterは](https://www.metarouter.io/)、強力なサーバーサイドのタグ管理プラットフォームとしてシームレスに統合することで、Brazeの体験を向上させる。Brazeは、最大30%までエンリッチされた信頼性の高いファーストパーティデータの収集から、パーソナライズされたジャーニーのためのリアルタイムのイベントストリームの活性化まで、Braze内で完全なカスタマーデータジャーニーをオーケストレーションすることを可能にする。さらに、MetaRouterは、Brazeタグやその他のサードパーティタグを不要にすることで実装を合理化し、Brazeに流入するデータをパラメータごとに細かく制御できるようにする。
+> [MetaRouter](https://www.metarouter.io/) は、強力なサーバーサイドタグ管理プラットフォームとしてシームレスに統合して、Braze エクスペリエンスを向上させます。これにより、最大30 %強化される信頼性の高いファーストパーティデータ収集から、パーソナライズされたジャーニーのリアルタイムのイベントストリームアクティベーションまで、Braze 内で完全な顧客データジャーニーをオーケストレーションできます。さらに ＭetaRouter は、Braze タグやその他のサードパーティタグの必要性を解消することで実装を合理化し、Braze へのデータ流入をより細かくパラメーター単位で制御できるようにします。
 
 ## サポートされている機能
 
 - リトライを組み込むこともできる。
-- リクエストはバッチされる。
+- リクエストはバッチ処理されます。
 - レート制限の問題はリトライで処理される。
-- 外部IDとPIIに対応している。MetaRouterは、匿名IDと、クライアントが望むあらゆる個人情報（電子メール、電話番号、名前）を渡す。
+- 外部IDとPIIに対応している。MetaRouter は、クライアントが必要とする匿名 ID と PII (メール、電話番号、名前) を渡します。
 - Brazeの購入データやカスタムイベントデータを送信できる。
   - イベント・プロパティがサポートされている。
   - ネストされたイベント・プロパティはサポートされていない。
 
 ## 前提条件
 
-始める前に、以下のものが必要だ：
+開始する前に、次のものが必要になります。
 
 | 必要条件           | 説明                                                                                                                                          |
 |-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
@@ -33,7 +33,7 @@ search_tag: Partner
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、**Developer Console**>**API Settingsで**APIキーを作成できる。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**開発者コンソール**] > \[**API 設定**] で API キーを作成できます。
 {% endalert %}
 
 ## MetaRouterをセットアップする
@@ -42,7 +42,7 @@ Brazeとの統合用にMetaRouterをセットアップする：
 
 1. MetaRouterに行き、新しいクラスタを作成する。
 2. 追跡したいイベントを選択する。
-3. MetaRouter SDKをインストールし、イベントをウェブサイトに統合する。
+3. MetaRouter SDK をインストールし、Web サイトにイベントを統合します。
 4. クラスターをウェブサイトのUIに接続する。
 5. 新しいパイプラインを作る。
 6. ウェブサイトがMetaRouterにイベントを送信していることを確認する。
@@ -51,12 +51,12 @@ Brazeとの統合用にMetaRouterをセットアップする：
 
 ### ステップ1:Brazeとの統合を追加する
 
-Enterprise MetaRouterで、**Integrations**>**New Integration**>**Brazeの**順に選択し、統合名を付ける。次にインスタンスURLとAPIキーを入力し、**Apply Changesを**選択する。
+Enterprise MetaRouter で \[**Integrations**] > \[**New Integration**] > \[**Braze**] を選択し、統合に名前を付けます。次に、インスタンスの URL と API キーを入力し、\[**Apply Changes**] を選択します。
 
-![]({% image_buster /assets/img/metarouter/img1.png %}){: style="max-width:50%;"}
+![MetaRouter で Braze を統合として追加する。]({% image_buster /assets/img/metarouter/img1.png %}){: style="max-width:50%;"}
 
 ### ステップ2:イベントマッピングを追加する
 
-各ID出力にイベントマッピングを追加し、Brazeに送信したいイベントを設定する。終了したら、**Save as New Revisionを**選択する。
+各ID出力にイベントマッピングを追加し、Brazeに送信したいイベントを設定する。終了したら、\[**Save as New Revision**] を選択します。
 
-![]({% image_buster /assets/img/metarouter/img2.png %}) 各アイデンティティ出力のイベントマッピングを追加する。
+![ID 出力ごとにイベントマッピングを追加する。]({% image_buster /assets/img/metarouter/img2.png %})
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/mozart_data.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/mozart_data.md
index 775e1192d56..d05fb1f59de 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/mozart_data.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/mozart_data.md
@@ -1,20 +1,20 @@
 ---
-nav_title: モーツァルト・データ
-article_title: モーツァルト・データ
-description: "この参考記事では、Brazeとオールインワンのモダン・データ・プラットフォームであるMozart Dataの提携について概説しており、Fivetranを使用してSnowflakeへのデータのインポート、トランスフォームの作成、データの結合などを行うことができる。"
+nav_title: Mozart Data
+article_title: Mozart Data
+description: "このリファレンス記事では、Braze と Mozart Data のパートナーシップについて説明します。Mozart Data はオールインワンの最新のデータプラットプラットフォームであり、Fivetran を使用して Snowflake へのデータのインポート、トランスフォームの作成、データの結合などを行うことができます。"
 alias: /partners/mozartdata/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# モーツァルト・データ
+# Mozart Data
 
 {% multi_lang_include video.html id="HU6dSOClcQ0" align="right" %}
 
-> [Mozart Dataは](https://mozartdata.com/)、Fivetran、Portable、Snowflakeを搭載したオールインワンの最新データ・プラットフォームである。
+> [Mozart Data](https://mozartdata.com/) は、Fivetran、Portable、Snowflake を利用するオールインワンの最新データプラットフォームです。
 
-BrazeとMozart Dataの統合により、以下のことが可能になる：
+Braze と Mozart Data の統合により、以下のことが可能になります。
 - Fivetranを使ってBrazeのデータをSnowflakeにインポートする
 - Brazeのデータと他のアプリケーションのデータを組み合わせてトランスフォームを作成し、ユーザーの行動を効果的に分析する。
 - SnowflakeからBrazeにデータをインポートし、新たな顧客エンゲージメントの機会を創出する。
@@ -37,43 +37,43 @@ table td {
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| モーツァルト・データ・アカウント | このパートナーシップを利用するには、モーツァルト・データのアカウントが必要である。[登録はこちらから。](https://app.mozartdata.com/signup)|
-| Snowflake アカウント<br>オプション 1: 新規アカウント | Mozart Dataのアカウント作成プロセスで**Create a New Snowflake Accountを**選択すると、Mozart Dataがお客様のために新しいSnowflakeアカウントをプロビジョニングする。 |
-| Snowflake アカウント<br>オプション 2: 既存口座 | 組織がすでにSnowflakeアカウントを持っている場合は、Mozart Data Connectedオプションを使うことができる。<br><br>既存の**Snowflake**アカウントに接続するには、**Already Have a Snowflake Account**オプションを選択する。このオプションを実行するには、アカウントレベルの権限を持つユーザーが[以下のステップに従わなければ](https://help.mozartdata.com/docs/setting-up-data-warehouse#existingsnowflakeaccount)ならない。 |
+| Mozart Data アカウント | このパートナーシップを活用するには、Mozart Data アカウントが必要です。[こちらからご登録ください。](https://app.mozartdata.com/signup)|
+| Snowflake アカウント<br>オプション 1: 新規アカウント | Mozart Data のアカウント作成プロセスで \[**Create a New Snowflake Account**] を選択すると、Mozart Data により新しい Snowflake アカウントがプロビジョニングされます。 |
+| Snowflake アカウント<br>オプション 2: 既存口座 | 組織がすでに Snowflake アカウントを所有している場合は、Mozart Data Connected オプションを使用できます。<br><br>既存のSnowflakeアカウントに接続するには、**Already Have a Snowflake Account**オプションを選択する。このオプションを使用する場合は、アカウントレベルの権限を持つユーザーが[以下の手順に従って操作する](https://help.mozartdata.com/docs/setting-up-data-warehouse#existingsnowflakeaccount)必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-この統合は、[BrazeからMozart Dataへの](#syncing-data-from-braze-to-mozart-data)データ同期と、[Mozart DataからBrazeへの](#syncing-data-from-mozart-data-to-braze)データ同期の両方でサポートされている。
+この統合は、[Braze から Mozart Data への](#syncing-data-from-braze-to-mozart-data)データ同期と [Mozart Data から Braze への](#syncing-data-from-mozart-data-to-braze)データ同期の両方でサポートされています。
 
 ### BrazeからMozart Dataにデータを同期する
 
-#### ステップ1:ブレイズコネクターをセットアップする
+#### ステップ1:Braze コネクターを設定する
 
-1. Mozart Dataで、**Connectorsに**進み、**Add Connectorを**クリックする。
-2. Braze」を検索し、コネクターカードを選択する。
+1. Mozart Data で \[**Connectors**] に移動し、\[**Add Connector**] をクリックします。
+2. 「Braze」を検索し、コネクターカードを選択します。
 3. Brazeから同期されたすべてのデータが保存される保存先スキーマ名を入力する。デフォルトのスキーマ名`braze` を使用することを推奨する。
-4. **Add Connectorを**クリックする。
+4. \[**Add Connector**] をクリックします。
 
-#### ステップ2:Fivetranコネクタフォームに記入する
+#### ステップ2:Fivetran コネクターフォームに情報を入力します。
 
-Fivetranコネクタのページにリダイレクトされる。このページで、所定の欄に記入する。次に、**Continue**>**Save & Testを**クリックし、Fivetranコネクタを完成させる。
+Fivetran コネクターページにリダイレクトされます。このページで所定のフィールドに入力します。次に \[**Continue**] > \[**Save & Test**] をクリックし、Fivetran コネクターを完成させます。
 
-Fivetranは、BrazeアカウントからSnowflakeデータウェアハウスへのデータの同期を開始する。コネクタの同期が完了した後、Mozart Dataからクエリデータにアクセスできる。 
+Fivetran が、Braze アカウントから Snowflake データウェアハウスへのデータの同期を開始します。コネクターの同期が完了したら、Mozart Data からクエリデータにアクセスできます。 
 
 ### Mozart DataからBrazeにデータを同期する
 
 #### ステップ1:Snowflakeデータウェアハウスをセットアップする
 
-[Cloud Data Ingestionの]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/?tab=snowflake)手順に従って、Snowflakeインターフェースからテーブル、ユーザー、権限を設定する。このステップには、管理者レベルのSnowflakeアクセスが必要であることに注意。
+「[クラウドデータ取り込み]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/?tab=snowflake)」の手順に従って、Snowflake インターフェイスからテーブル、ユーザー、権限を設定します。このステップには、管理者レベルのSnowflakeアクセスが必要であることに注意。
 
 #### ステップ2:BrazeでSnowflakeとの統合をセットアップする
 
-Snowflake warehouseを設定した後、Mozart Dataで**Integration**ページに行き、**Brazeを**選択する。ここで、Brazeに提供するために必要なクレデンシャルを見つける。
+Snowflake ウェアハウスの設定後に、Mozart Data の \[**Integration**] ページで \[**Braze**] を選択します。ここで、Braze に提供する必要がある認証情報を確認します。
 
 ![]({% image_buster /assets/img/mozartdata/mozartdata-braze-integrationpage.png %}){: style="max-width:80%;"}
 
-次に、Brazeにサインインした状態で、**Integrations > Technology Partners > Snowflakeと**進み、統合プロセスを開始する。Mozart Dataから認証情報をコピーし、Snowflake Dataのインポートページに追加する。**Set up sync detailsを**クリックし、Snowflakeアカウントとソーステーブル情報を入力する。 
+次に、Braze にサインインした状態で **\[統合] > \[テクノロジーパートナー] > \[Snowflake]** に移動し、統合プロセスを開始します。Mozart Data から認証情報をコピーし、Snowflake Data のインポートページに追加します。\[**同期の詳細を設定**] をクリックし、Snowflake アカウントとソーステーブルの情報を入力します。 
 
 ![]({% image_buster /assets/img/mozartdata/mozartdata-braze-snowflakecredentials.png %}){: style="max-width:80%;"}
 
@@ -82,9 +82,9 @@ Snowflake warehouseを設定した後、Mozart Dataで**Integration**ページ
 ![]({% image_buster /assets/img/mozartdata/mozartdata-braze-importsync.png %}){: style="max-width:80%;"}
 
 #### ステップ 3:Braze ユーザーへの公開キーの追加
-この時点で、Snowflakeに戻ってセットアップを完了する必要がある。Brazeのダッシュボードに表示される公開鍵を、BrazeがSnowflakeに接続するために作成したユーザーに追加する。
+この時点で、Snowflake に戻って設定を完了する必要があります。Brazeのダッシュボードに表示される公開鍵を、BrazeがSnowflakeに接続するために作成したユーザーに追加する。
 
-その方法の詳細については、[Snowflake のドキュメント](https://docs.snowflake.com/en/user-guide/key-pair-auth.html)を参照してください。鍵のローテーションを行いたい場合は、Mozart Dataが新しい鍵ペアを生成し、新しい公開鍵を提供する。
+その方法の詳細については、[Snowflake のドキュメント](https://docs.snowflake.com/en/user-guide/key-pair-auth.html)を参照してください。任意の時点でのキーのローテーションを行う場合、Mozart Data は新規のキーペアを生成して、新規の公開キーを提供できます。
 
 ```json
 ALTER USER BRAZE_INGESTION_USER SET rsa_public_key='Braze12345...';
@@ -92,7 +92,7 @@ ALTER USER BRAZE_INGESTION_USER SET rsa_public_key='Braze12345...';
 
 #### ステップ 4:テスト接続
 
-ユーザーが公開鍵で更新されたら、Brazeダッシュボードに戻り、**Test connectionを**クリックする。成功すると、データのプレビューが表示されます。何らかの理由で接続に失敗した場合、トラブルシューティングに役立つエラーメッセージが表示される。
+ユーザーが公開キーで更新されたら、Braze ダッシュボードに戻って、\[**テスト接続**] をクリックします。成功すると、データのプレビューが表示されます。何らかの理由で接続に失敗した場合、トラブルシューティングに役立つエラーメッセージが表示される。
 
 ![]({% image_buster /assets/img/mozartdata/mozartdata-braze-testsyncpublickey.png %}){: style="max-width:80%;"}
 
@@ -102,16 +102,16 @@ ALTER USER BRAZE_INGESTION_USER SET rsa_public_key='Braze12345...';
 
 ## この統合を使う
 
-### Mozart DataのユーザーとしてBrazeのデータにアクセスする方法
-Mozart Dataアカウントの作成に成功すると、Mozart DataからSnowflakeデータウェアハウスに同期されたBrazeデータにアクセスできるようになる。
+### Mozart Data のユーザーとして Braze のデータにアクセスする方法
+Mozart Data アカウントが作成されたら、Mozart Data から Snowflake データウェアハウスに同期された Braze データにアクセスできます。
 
 #### トランスフォーム
-Mozart Dataは、ユーザーがビューやテーブルを作成するためのSQL変換レイヤーを提供している。ユーザーレベルのディメンションテーブル（たとえば、`dim_users` ）を作成し、各ユーザーの製品使用データ、取引履歴、Brazeメッセージとのエンゲージメント活動を要約することができる。 
+Mozart Dataは、ユーザーがビューやテーブルを作成するためのSQL変換レイヤーを提供している。各ユーザーの製品使用データ、取引履歴、エンゲージメントアクティビティを Braze メッセージとともに要約するユーザーレベルのディメンションテーブル (`dim_users` など) を作成できます。 
 
 #### 分析
-Brazeから同期された変換モデルまたは生データを使用して、Brazeメッセージに対するユーザーのエンゲージメントを分析できる。さらに、Brazeのデータを他のアプリケーションのデータと組み合わせて、ユーザーとBrazeのメッセージとのやり取りから得た洞察が、ユーザーについて持っている他のデータとどのように関連しているかを分析することもできる。例えば、デモグラフィック情報、ショッピング履歴、製品の使用状況、カスタマーサービスへの関与などである。 
+Brazeから同期された変換モデルまたは生データを使用して、Brazeメッセージに対するユーザーのエンゲージメントを分析できる。さらに、Braze データを他のアプリケーションのデータと組み合わせて、Braze メッセージに対するユーザーのインタラクションから得たインサイトが、ユーザーに関して所有している他のデータとどのように関連しているかを分析できます。たとえば、顧客のデモグラフィック情報、ショッピング履歴、製品の使用状況、カスタマーサービスエンゲージメントなどです。 
 
 これは、ユーザーのリテンションを向上させるためのエンゲージメント戦略について、より多くの情報に基づいた決定を下すのに役立つ。これはすべて、クエリーツールを使ってMozart Dataのインターフェイス内で行うことができ、結果をGoogleシートやCSVにエクスポートしてプレゼンテーションに備えることができる。
 
 #### ビジネスインテリジェンス（BI）
-自分の洞察を可視化し、他のチームメンバーと共有する準備はできているか？Mozart Dataは、ほとんどすべてのBIツールと統合できる。BIツールをまだ持っていない場合は、Mozart Dataに連絡して無料のMetabaseアカウントをセットアップしてほしい。 
\ No newline at end of file
+自分の洞察を可視化し、他のチームメンバーと共有する準備はできているか？Mozart Data は、ほぼすべての BI ツールと統合されています。BI ツールをまだ所有していない場合は、Mozart Data に連絡して無料の Metabase アカウントの設定を依頼してください。 
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/nexla.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/nexla.md
index 5293e2bee5a..f39e60eb9bf 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/nexla.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/nexla.md
@@ -1,63 +1,63 @@
 ---
-nav_title: ネクスラ
-article_title: ネクスラ
-description: "この参考記事では、BrazeとNexlaのパートナーシップについて概説している。Nexlaは統合データ運用プラットフォームであり、Braze Currentsのユーザーはデータレイクデータを抽出、変換し、カスタムフォーマットで他の場所にロードすることができる。"
+nav_title: Nexla
+article_title: Nexla
+description: "このリファレンス記事では、Braze と Nexla のパートナーシップについて説明します。Nexla は統合データ運用プラットフォームであり、Braze Currents をご利用のお客様はデータレイクデータを抽出、変換し、カスタムフォーマットで他の場所にデータを読み込むことができます。"
 alias: /partners/nexla/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# ネクスラ
+# Nexla
 
-> [ネクスラは](https://www.nexla.com)ユニファイド・データ・オペレーションのリーダーであり、2021年ガートナー・クールベンダーに選ばれている。Nexlaプラットフォームは、誰でも簡単にスケーラブルなデータフローを作成することができ、ビジネスチームとデータチームに摩擦のないガバメントされたデータオペレーション、より良いコラボレーション、俊敏性を提供する。データを扱うチームは、あらゆるユースケースに対応したデータの統合、変換、プロビジョニング、監視を、ノー／ローコードで統一されたエクスペリエンスで行うことができる。 
+> [Nexla](https://www.nexla.com) は統合データ運用分野のリーダーであり、2021年の Gartner Cool Vender に選出されています。Nexla プラットフォームでは、誰でも簡単にスケーラブルなデータフローを作成でき、ビジネスチームとデータチームにフリクションのない制御されたデータ運用、コラボレーションの向上、アジリティをもたらします。データを扱うチームは、ノーコード / ローコードの統一されたエクスペリエンスで、あらゆるユースケースのデータを統合、変換、プロビジョニング、監視することができます。 
 
-BrazeとNexlaの統合により、[Currentsを]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/setting_up_currents/)使用している顧客は、Nexlaを活用してデータレイクデータをカスタムフォーマットで他の場所に抽出、変換、ロードできるようになり、エコシステム全体でデータに簡単にアクセスできるようになる。
+Braze と Nexla の統合により、[Currents]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/setting_up_currents/) を利用しているお客様は、Nexla を活用してデータレイクデータを抽出、変換し、カスタムフォーマットで他の場所に読み込むことができ、エコシステム全体でデータに簡単にアクセスできるようになります。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| ネクスラアカウント | このパートナーシップを利用するには、\[ネクスラアカウント][2] ]が必要である。 |
+| Nexla アカウント | このパートナーシップを活用するには、\[Nexla アカウント][2]が必要です。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは、\[インスタンスのBraze URL][1] に依存する。 |
+| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは\[インスタンスの Braze URL][1] に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
-Nexlaのデータ・アズ・ア・プロダクトである[Nexsetsは](https://nexla.zendesk.com/hc/en-us/articles/360052999674-Dataset-Information)、メタデータを気にすることなく、あらゆるフォーマットのデータを簡単に扱うことができる。Brazeとの間のデータフローをNexlaで設定する場合、コード不要のツールで簡単に数分で利用できる。データフローを宛先に設定した後、Nexlaはフローを監視し、任意のデータ量に拡張する。
+Nexla の Data as a Product (製品としてのデータ) である [Nexset](https://nexla.zendesk.com/hc/en-us/articles/360052999674-Dataset-Information) により、メタデータを気にすることなく、あらゆるフォーマットのデータを簡単に扱うことができます。Brazeとの間のデータフローをNexlaで設定する場合、コード不要のツールで簡単に数分で利用できる。データフローが宛先に設定された後で、Nexla はフローを監視し、任意のデータ量にスケーリングします。
 
 ## 統合
 
-### ステップ1:ネクスラアカウントを作成する
+### ステップ1:Nexla アカウントを作成する
 
-まだネクスラのアカウントをお持ちでない方は、ネクスラの[ウェブサイトから](https://www.nexla.com)無料デモとトライアルを申し込むことができる。次に [www.dataops.nexla.io](https://www.dataops.nexla.io)にログオンし、新しい認証情報でサインオンする。
+まだ Nexla アカウントをお持ちでない方は、Nexla の [Web サイト](https://www.nexla.com)から無料デモとトライアルを申し込むことができます。次に [www.dataops.nexla.io](https://www.dataops.nexla.io)にログオンし、新しい認証情報でサインオンする。
 
 ### ステップ2:ソースを追加する
 
 #### Brazeをデータソースとする場合
 1. Nexlaプラットフォームで、左ツールバーの「**フロー」>「新規フローの作成**」を選択する。
-2. **Create New Sourceを**クリックし、Brazeコネクタを選択し、**Nextを**クリックする。 
-3. **Add a New Credentialを**選択し、クレデンシャルに名前を付け、Braze APIキーとRESTエンドポイントを追加して、**Save**する。
-4. 最後に、データを選択し、**Saveを**クリックする。 
+2. \[**Create New Source**] をクリックし、Braze コネクターを選択し、\[**Next**] をクリックします。 
+3. \[**Add a New Credential**] を選択し、認証情報に名前を付け、Braze API キーと REST エンドポイントを追加して、\[**Save**] をクリックします。
+4. 最後にデータを選択して \[**Save**] をクリックします。 
 
-Nexlaは、ソースのデータを検索し、変換またはデスティネーションに送信するための[Nexsetを](https://nexla.zendesk.com/hc/en-us/articles/360052999674-Dataset-Information)生成する。
+Nexla はソースでデータを検索し、変換または宛先への送信のために [Nexset](https://nexla.zendesk.com/hc/en-us/articles/360052999674-Dataset-Information) を生成します。
 
-#### ブレーズが目的地なら
+#### Braze が宛先の場合
 
-[Nexlaへのソースの接続については](https://nexla.zendesk.com/hc/en-us/sections/115001685927-Create-a-Data-Source)、Nexlaのドキュメントを参照のこと。
+[Nexla へのソースの接続](https://nexla.zendesk.com/hc/en-us/sections/115001685927-Create-a-Data-Source)については、Nexlaのドキュメントを参照してください。
 
 ### ステップ3:トランスフォーム（オプション）
 
-データに対してカスタム[変換を](https://nexla.zendesk.com/hc/en-us/sections/115001686007-Transformations)実行したい場合、またはNexlaのビルド済みコネクタを使用したい場合は、データセットの**変換**ボタンをクリックして変換ビルダーに入る。Transform Builderの使用方法は、[Nexlaのドキュメントに](https://nexla.zendesk.com/hc/en-us/articles/360000590468-How-to-Transform-your-Data)記載されている。
+データに対してカスタム[変換を](https://nexla.zendesk.com/hc/en-us/sections/115001686007-Transformations)実行したい場合、またはNexlaのビルド済みコネクタを使用したい場合は、データセットの**変換**ボタンをクリックして変換ビルダーに入る。Transform Builder の使用に関するガイダンスは[Nexla のドキュメント](https://nexla.zendesk.com/hc/en-us/articles/360000590468-How-to-Transform-your-Data)にあります。
 
 ### ステップ4:宛先に送信する
 
-デスティネーションにデータを送信するには、データセット上の「**デスティネーションに送信**」矢印をクリックし、Nexlaのデスティネーションコネクター、またはソースが異なる場合はBrazeのいずれかを選択する。認証情報を入力し、宛先オプションを設定し、**Saveを**クリックする。データは即座に、あなたが指定したフォーマットで、あなたが選んだ宛先に流れ始める。
+宛先にデータを送信するには、データセットの \[**宛先**] 矢印をクリックし、Nexla の宛先コネクターまたは Braze (ソースが異なる場合) を選択します。認証情報を入力し、宛先オプションを設定し、\[**Save**] をクリックします。データは即座に、あなたが指定したフォーマットで、あなたが選んだ宛先に流れ始める。
 
 ## この統合を使う
 
-一度フローがセットアップされれば、あとは何も必要ない。Nexlaはソースデータの変更に対応し、新しいデータへのスケーリングを行い、スキーマの変更やトリアージのためのエラーを通知する。トランスフォーム、ソース、デスティネーションを変更したい場合は、これらのオプションをクリックして変更すれば、Nexlaは即座にフローを更新する。
+一度フローがセットアップされれば、あとは何も必要ない。Nexla はソースデータの変更をすべて処理し、新しいデータへのスケーリングを行い、トリアージのためにスキーマの変更やエラーを通知します。変換、ソース、または宛先を変更する場合は、これらのオプションをクリックして変更を行います。Nexla によりフローが即時に更新されます。
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)
 [2]: https://www.nexla.com/get-demo
\ No newline at end of file
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/zapier.md b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/zapier.md
index 2187ba29b35..46bd54432a6 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/zapier.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/workflow_automation/zapier.md
@@ -9,52 +9,52 @@ search_tag: Partner
 ---
 # Zapierとの統合
 
-> [Zapierは][1]自動化ウェブツールで、ウェブアプリ間でデータを共有し、その情報を使ってアクションを自動化することができる。 
+> [Zapier][1] は、Web アプリ間でデータを共有し、その情報を使用してアクションを自動化できるオートメーション Web ツールです。 
 
-BrazeとZapierのパートナーシップは、Braze APIとBraze[webhooksを][3]活用して、Google Workplace、Slack、Salesforce、WordPressなどのサードパーティアプリケーションと接続し、さまざまなアクションを自動化する。
+Braze と Zapier のパートナーシップでは、Braze API と Braze [Webhook][3] を活用してサードパーティアプリケーション (Google Workplace、Slack、Salesforce、WordPress など) に接続し、さまざまなアクションを自動化できます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| Zapierアカウント | このパートナーシップを利用するには、Zapierアカウントが必要だ。 |
-| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに][0]依存する。 |
+| Zapierアカウント | このパートナーシップを活用するには、Zapier アカウントが必要です。 |
+| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL][0] に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-以下のZapierの例では、POST webhookを使ってWordPressからBrazeに情報を送信する。この情報をもとに、ブレイズ・キャンバスを作成することができる。
+以下のZapierの例では、POST webhookを使ってWordPressからBrazeに情報を送信する。この情報を使用して Braze キャンバスを作成することができます。
 
 ### ステップ1:Zapierトリガーを作成する
 
-Zapierの用語を使えば、"ザップ "とはアプリやサービスをつなぐ自動化されたワークフローのことだ。どのようなザップでも、最初の部分はトリガーを指定することだ。ザップが有効になると、トリガーが検出されるたびにZapierが自動的にそれぞれのアクションを実行する。
+Zapierの用語を使えば、"ザップ "とはアプリやサービスをつなぐ自動化されたワークフローのことだ。どのようなザップでも、最初の部分はトリガーを指定することだ。zap が有効になると、トリガーが検出されるたびにZapier によって対応するアクションが自動的に実行されます。
 
 WordPressの例を使って、Zapierプラットフォームで、WordPressの新しい投稿が追加されたときにトリガーされるようにzapを設定し、**Post Statusと** **Post Typeとして** **Publishedと** **Postsを**選択する。 
 
-![Zapierプラットフォームで、zapの中で、トリガーを "新しいコメント"、"任意のウェブフック"、"新しい投稿 "のいずれかに選択する。この例では、"new post "が選択されている。 ] \[5]
+![Zapierプラットフォームで、zap 内でトリガーとして「new comment」、「any webhook」、「new post」のいずれかを選択する。この例では「new post」が選択されている。] \[5]
 
-![Zapierプラットフォームで、ザップ内で、希望の投稿ステータスと投稿タイプを選択してトリガーを設定する。この例では、"Published "と "Posts "が選択されている。] \[6]
+![Zapier プラットフォームで、zap 内で目的の post status と post type を選択してトリガーを設定する。この例では「Publishedと「Posts」が選択されている。] \[6]
 
 ### ステップ2:アクションウェブフックを追加する
 
-次に、ザップアクションを定義する。ザップが有効になり、トリガーが検出されると、自動的にアクションが発生する。
+次に zap アクションを定義します。zap が有効になり、トリガーが検出されると、アクションが自動的に発生します。
 
-この例の続きで、BrazeのエンドポイントにJSONとしてPOSTリクエストを送りたい。これは、**Appsの**下にある**Webhooks**オプションを選択することで行うことができる。
+この例の続きで、BrazeのエンドポイントにJSONとしてPOSTリクエストを送りたい。これを行うには、\[**Apps**] の下にある \[**Webhooks**] オプションを選択します。
 
 ![][7]
 
 ### ステップ3:Braze POSTをセットアップする
 
-Webhookを設定する際は、以下の設定を使用し、Webhook URLにBraze RESTエンドポイントを指定する。完了したら、**Publishを**選択する。
+Webhook を設定するときに、次の設定を使用して Webhook URL に Braze REST エンドポイントを指定します。完了したら \[**Publish**] を選択します。
 
 - **方法**：POST
-- **ウェブフックのURL**： `https://rest.iad-01.braze.com/canvas/trigger/send`
-- **データのパススルー**False
-- **アンフラッテン**だ：いいえ
-- **ヘッダーをリクエストする**：
+- **Webhook URL**: `https://rest.iad-01.braze.com/canvas/trigger/send`
+- **Data Pass-Though**:False
+- **Unflatten**:いいえ
+- **リクエストヘッダー**:
   - **Content-Type**: application/json
-  - **認可する**：Bearer YOUR-API-KEY
-- **データ**だ： 
+  - **Authorization**:Bearer YOUR-API-KEY
+- **Data**: 
 
 ```json
 {
@@ -75,7 +75,7 @@ Webhookを設定する際は、以下の設定を使用し、Webhook URLにBraze
 
 ### ステップ4:Brazeのキャンペーンを作成する
 
-ザップの設定が完了したら、リキッドフォーマットを使ってメッセージに情報を表示することで、BrazeのキャンペーンやキャンバスをWordPressのデータでカスタマイズすることができる。
+zap の設定が完了したら、Liquid フォーマットを使用してメッセージの情報を表示することで、WordPress データを使用して Braze キャンペーンまたはキャンバスをカスタマイズできます。
 
 [0]: {{site.baseurl}}/api/basics/#api-definitions
 [1]: https://zapier.com/
diff --git a/_lang/ja/_partners/data_and_infrastructure_agility/wrapper_sdks.md b/_lang/ja/_partners/data_and_infrastructure_agility/wrapper_sdks.md
index 35644295b7d..486314310d7 100644
--- a/_lang/ja/_partners/data_and_infrastructure_agility/wrapper_sdks.md
+++ b/_lang/ja/_partners/data_and_infrastructure_agility/wrapper_sdks.md
@@ -3,7 +3,7 @@ nav_title: Wrapper SDKs
 article_title: Wrapper SDKs
 page_order: 200
 
-description: "以下のラッパーSDKは、開発者が複数のプラットフォームでアプリを開発する際に役立つ。"
+description: "以下のラッパー SDK は、複数のプラットフォームにわたるアプリケーション開発で開発者を支援するために使用できます。"
 page_type: partner
 platform: 
   - cordova
@@ -14,22 +14,22 @@ platform:
 layout: dev_guide
  
 guide_top_header: "Wrapper SDKs"
-guide_top_text: "以下のラッパーSDKは、開発者が複数のプラットフォームでアプリを開発する際に役立つ。"
+guide_top_text: "以下のラッパー SDK は、複数のプラットフォームにわたるアプリケーション開発で開発者を支援するために使用できます。"
 
 guide_featured_list:
-  - name: コルドバ Android
+  - name: Cordova Android
     link: /docs/developer_guide/platform_integration_guides/cordova/initial_sdk_setup/android/
     image: /assets/img/cordova.png
-  - name: コルドバ iOS
+  - name: Cordova iOS
     link: /docs/developer_guide/platform_integration_guides/cordova/initial_sdk_setup/ios/
     image: /assets/img/cordova.png
   - name: React Native
     link: /docs/developer_guide/platform_integration_guides/react_native/react_sdk_setup/
     image: /assets/img/reactnative_icon.png
-  - name: ユニティ アンドロイド
+  - name: Unity Android
     link: /docs/developer_guide/platform_integration_guides/unity/sdk_integration/android/
     image: /assets/img/unity.png
-  - name: ユニティ iOS
+  - name: Unity iOS
     link: /docs/developer_guide/platform_integration_guides/unity/sdk_integration/ios/
     image: /assets/img/unity.png
   - name: Xamarin
diff --git a/_lang/ja/_partners/home.md b/_lang/ja/_partners/home.md
index a647f8fac4f..3d3d19f4e81 100644
--- a/_lang/ja/_partners/home.md
+++ b/_lang/ja/_partners/home.md
@@ -10,7 +10,7 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 
 partner_top_header: "Technology Partners"
 partner_top_text: "Welcome to our list of Alloys (our allies - our best buds - our partners)! Use it to explore the technical documentation that will help implement Technology Partners into your Braze SDK. <br> <br>  If you're looking for information on joining our Firebrands, a community of movers and shakers using Braze to modernize their customer experience and marketing, check out our information page <a href='https://brazefirebrands.splashthat.com/'>here</a>."
-description: "このランディングページにはすべてのBrazeパートナーが含まれています。技術パートナーを Braze SDK に実装するのに役立つ技術ドキュメントを探索するために使用します。"
+description: "このランディングページにはすべてのBrazeパートナーが含まれています。テクノロジーパートナーを Braze SDK に実装する際に役立つ技術ドキュメントを探すときにご利用ください。"
 
 valid_partner_list:
 - name: Jampp
@@ -43,7 +43,7 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier/
 - name: Kochava
   url: /docs/partners/message_orchestration/attribution/kochava/
-- name: 単数
+- name: Singular
   url: /docs/partners/message_orchestration/attribution/singular/
 - name: Vizbee
   url: /docs/partners/message_orchestration/attribution/vizbee_for_tv_deeplinking/
@@ -73,7 +73,7 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/zapier/
 - name: Zendesk
   url: /docs/partners/data_and_infrastructure_agility/support/zendesk/
-- name: パイプストリーム
+- name: Pypestream
   url: /docs/partners/data_and_infrastructure_agility/support/pypestream/
 - name: Amazon S3
   url: /docs/partners/data_and_infrastructure_agility/cloud_storage/amazon_s3/
@@ -131,13 +131,13 @@ valid_partner_list:
   url: /docs/partners/message_personalization/location/bluedot/
 - name: NPAW
   url: /docs/partners/data_and_infrastructure_agility/analytics/npaw/
-- name: ジャカード
+- name: Jacquard
   url: /docs/partners/data_and_infrastructure_agility/ab_testing/jacquard/
 - name: optilyz
   url: /docs/partners/message_orchestration/additional_channels/direct_mail/optilyz/
 - name: Digioh
   url: /docs/partners/message_orchestration/channel_extensions/surveys/digioh/
-- name: ネクスラ
+- name: Nexla
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/nexla/
 - name: Amperity
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/amperity/
@@ -147,11 +147,11 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/cohort_import/tinyclues/
 - name: Transcend
   url: /docs/partners/data_and_infrastructure_agility/data_privacy/transcend/
-- name: レベニューキャット
+- name: RevenueCat
   url: /docs/partners/data_and_infrastructure_agility/payments/revenuecat/
 - name: Punchh
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/punchh/
-- name: ブルーコニック
+- name: BlueConic
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/blueconic/
 - name: LINE
   url: /docs/partners/message_orchestration/additional_channels/messaging/line/  
@@ -163,19 +163,19 @@ valid_partner_list:
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/adobe/
 - name: Worthy
   url: /docs/partners/message_personalization/dynamic_content/worthy/
-- name: ヨトポ
+- name: Yotpo
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/yotpo/
 - name: Zeotap
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/zeotap/
-- name: トーヴィオ
+- name: Toovio
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/toovio/
-- name: 字句解析器
+- name: Lexer
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/lexer/
-- name: スノープラウ
+- name: Snowplow
   url: /docs/partners/data_and_infrastructure_agility/analytics/snowplow/
-- name: クラリサイト
+- name: Clarisights
   url: /docs/partners/data_and_infrastructure_agility/analytics/clarisights/
-- name: サーヴィケイト
+- name: Survicate
   url: /docs/partners/message_orchestration/channel_extensions/surveys/survicate/
 - name: Wyng
   url: /docs/partners/message_personalization/dynamic_content/wyng/
@@ -185,69 +185,69 @@ valid_partner_list:
   url: /docs/partners/message_personalization/dynamic_content/peak/
 - name: Personalize.AI
   url: /docs/partners/message_personalization/dynamic_content/personalize/
-- name: クナック
+- name: Knak
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/knak/
 - name: WSC Sports
   url: /docs/partners/message_personalization/dynamic_content/wsc_sports/
-- name: エクストール
+- name: Extole
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/extole/
-- name: バイラルスイープ
+- name: ViralSweep
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/viralsweep/
-- name: マイクロソフト ダイナミクス 365
+- name: Microsoft Dynamics 365
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights/
 - name: Heap
   url: /docs/partners/data_and_infrastructure_agility/cohort_import/heap/  
 - name: Quikly
   url: /docs/partners/message_orchestration/additional_channels/retargeting/quikly/
-- name: アクショナブル・ミー
+- name: actionable.me
   url: /docs/partners/data_and_infrastructure_agility/analytics/actionableme/
-- name: IAMスタジオ（NNT）
+- name: IAM Studio (NNT)
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/iam_studio/
-- name: ストーリーリー
+- name: Storyly
   url: /docs/partners/data_and_infrastructure_agility/cohort_import/storyly/
 - name: Lokalise
   url: /docs/partners/message_personalization/localization/lokalise/
-- name: データグレイル
+- name: DataGrail
   url: /docs/partners/data_and_infrastructure_agility/data_privacy/datagrail/
 - name: Dynamic Yield
   url: /docs/partners/message_personalization/dynamic_content/dynamic_yield/
-- name: オクトリス
+- name: Octolis
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/octolis/
 - name: Ada
   url: /docs/partners/message_orchestration/channel_extensions/surveys/ada/
-- name: ソートスポット
+- name: ThoughtSpot
   url: /docs/partners/data_and_infrastructure_agility/analytics/thoughtspot/
-- name: 神童
+- name: Wunderkind
   url: /docs/partners/data_and_infrastructure_agility/analytics/wunderkind/
-- name: B.レイヤー
+- name: B.Layer
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/blayer/
-- name: テルス
+- name: Tellius
   url: /docs/partners/data_and_infrastructure_agility/analytics/tellius/
 - name: Sheetlabs
   url: /docs/partners/message_personalization/dynamic_content/sheetlabs/
-- name: コンテンツスクエア
+- name: Contentsquare
   url: /docs/partners/data_and_infrastructure_agility/analytics/contentsquare/
-- name: シス
+- name: Sisu
   url: /docs/partners/data_and_infrastructure_agility/business_intelligence/sisu_data/
-- name: アクションIQ
+- name: ActionIQ
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/actioniq/
 - name: Airbyte
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/airbyte/
 - name: GrowthLoop
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/growthloop/
-- name: モーツァルトデータ
+- name: Mozart Data
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/mozart_data/
 - name: loplat
   url: /docs/partners/message_personalization/location/loplat/
-- name: セージフロー
+- name: Sageflo
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/sageflo/
-- name: ニフト
+- name: Nift
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/nift/
 - name: Komo
   url: /docs/partners/message_personalization/dynamic_content/komo/
 - name: Phrase
   url: /docs/partners/message_personalization/localization/phrase/
-- name: マーキュリー
+- name: Merkury
   url: /docs/partners/data_and_infrastructure_agility/analytics/merkury/
 - name: WhatsApp
   url: /docs/user_guide/message_building_by_channel/whatsapp/
@@ -263,7 +263,7 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/kognitiv/
 - name: SalesWings
   url: /docs/partners/data_and_infrastructure_agility/analytics/saleswings/
-- name: ワントラスト
+- name: OneTrust
   url: /docs/partners/data_and_infrastructure_agility/data_privacy/onetrust/
 - name: Tangerine
   url: /docs/partners/message_personalization/location/tangerine/
@@ -271,36 +271,36 @@ valid_partner_list:
   url: /docs/partners/message_personalization/dynamic_content/stylitics/
 - name: Redpoint
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/redpoint/  
-- name: サイモンデータ
+- name: Simon Data
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/simondata/
 - name: Ketch
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/ketch/
-- name: アンタヴォ
+- name: Antavo
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/antavo/
 - name: Lytics
   url: /docs/partners/data_and_infrastructure_agility/customer_data_platform/lytics/
-- name: オロ
+- name: Olo
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/olo/
-- name: リカーリー
+- name: Recurly
   url: /docs/partners/data_and_infrastructure_agility/payments/recurly/
 - name: SmarterSends
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/smartersends/
-- name: タイプフォーム
+- name: Typeform
   url: /docs/partners/message_orchestration/channel_extensions/surveys/typeform/
-- name: スキューバ
+- name: Scuba
   url: /docs/partners/data_and_infrastructure_agility/analytics/scuba/
-- name: セレブルス
+- name: Celebrus
   url: /docs/partners/data_and_infrastructure_agility/analytics/celebrus/
 - name: Friendbuy
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/friendbuy/
-- name: アルパコ
+- name: Alpaco
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/alpaco/
 - name: NiftyImages
   url: /docs/partners/message_personalization/dynamic_content/niftyimages
-- name: メタルーター
+- name: MetaRouter
   url: /docs/partners/data_and_infrastructure_agility/workflow_automation/metarouter/
 - name: トレジャーデータ
   url: /docs/partners/data_and_infrastructure_agility/cohort_import/treasuredata/
-- name: ライブランプ
+- name: LiveRamp
   url: /docs/partners/data_and_infrastructure_agility/advertising/liveramp/
 ---
diff --git a/_lang/ja/_partners/isv_partners.md b/_lang/ja/_partners/isv_partners.md
index 627815fbe15..0087fc915d2 100644
--- a/_lang/ja/_partners/isv_partners.md
+++ b/_lang/ja/_partners/isv_partners.md
@@ -5,7 +5,7 @@ page_order: 9
 hidden: true
 
 guide_top_header: "ISVパートナー"
-guide_top_text: "以下の記事は、Alloys ISVパートナーがBrazeプラットフォームとの市場統合を開発する際に参照するために提供されています。対応するパートナー連携ドキュメントを参照して開始してください！"
+guide_top_text: "以下の記事は、当社の Alloys ISV パートナーに、Braze プラットフォームでマーケット統合を開発する際のリファレンスとして提供されています。対応するパートナー連携ドキュメントを参照して開始してください！"
 
 guide_featured_title: "パートナー ドキュメント"
 guide_featured_list:
@@ -15,7 +15,7 @@ guide_featured_list:
 - name: コホートインポート統合
   link: /docs/partners/isv_partners/cohort_import
   image: /assets/img/braze_icons/users-01.svg
-- name: Currentsインテグレーション
+- name: Currents 統合
   link: /docs/partners/isv_partners/currents_integration
   image: /assets/img/braze_icons/waves.svg
 - name: Snowflakeデータ共有
diff --git a/_lang/ja/_partners/isv_partners/api_partner.md b/_lang/ja/_partners/isv_partners/api_partner.md
index 22632d6596d..98f7f066fb2 100644
--- a/_lang/ja/_partners/isv_partners/api_partner.md
+++ b/_lang/ja/_partners/isv_partners/api_partner.md
@@ -6,9 +6,9 @@ hidden: true
 
 # APIパートナーとの統合
 
-Alloys ISVパートナーは、API Requestsの`partner` フィールドにパートナー名を追加する必要があり、Brazeはパートナーからの受信リクエストなどAPIパートナーの利用状況を追跡できる。実装を開発する際には、以下の[/users/track]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)エンドポイント構造を参照すること。
+Alloys ISV パートナーは、API リクエストの `partner` フィールドにパートナー名を追加する必要があります。これにより、Braze はパートナーからの受信リクエストなどの API パートナーの使用状況を追跡できます。実装を開発する際には、以下の[/users/track]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)エンドポイント構造を参照すること。
 
-## パートナー・リクエスト本体
+## パートナーリクエスト本文
 
 ```
 Content-Type: application/json
diff --git a/_lang/ja/_partners/isv_partners/best_practices.md b/_lang/ja/_partners/isv_partners/best_practices.md
index 88b76189ef5..ca7a6bd222d 100644
--- a/_lang/ja/_partners/isv_partners/best_practices.md
+++ b/_lang/ja/_partners/isv_partners/best_practices.md
@@ -7,7 +7,7 @@ hidden: true
 
 ## データ収集
 
-Brazeのデータ収集方法について詳しく知る：
+Braze でのデータの収集方法について詳しくは、以下を参照してください。
 - [SDK によるデータ収集]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/sdk_data_collection/)
 - [データ収集のベストプラクティス]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/best_practices/)
 - [ユーザープロファイルのライフサイクル]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/)
@@ -16,20 +16,20 @@ Brazeのデータ収集方法について詳しく知る：
 
 - `braze_id`:Brazeが割り当てた識別子で、変更不可能であり、当社のデータベース内で作成されたときに特定のユーザーと関連付けられる。
 - `external_id`:顧客が割り当てた識別子で、通常はUUIDである。ユーザーを一意に識別できる場合、`external_id` を割り当てることを推奨する。ユーザーが特定された後、匿名に戻すことはできない。
-- `user_alias`:`external_id` が割り当てられる前に、IDによってユーザーを参照する手段として、顧客が割り当てることができる一意の代替識別子。ユーザーエイリアスは、Brazeの[ユーザー識別]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/)エンドポイントを介して利用可能になったときに、後で他のエイリアスまたは`external_id` 。
-    - [User identify]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/)エンドポイント内では、`merge_behavior` フィールドを使用して、ユーザーエイリアスプロファイルのどのデータを既知のユーザープロファイルに永続させるかを指定することができる。
-    - ユーザーエイリアスを送信可能なプロファイルとするためには、プロファイルの標準属性としてEメールおよび/または電話を含める必要があることに注意すること。
-- `device_id`:自動的に生成される、機器固有の識別子。ユーザープロファイルには、いくつかの`device_ids` 。例えば、職場のコンピューター、自宅のコンピューター、タブレット、iOSアプリでアカウントにログインしているユーザーは、自分のプロフィールに4つの`device_ids` 。
+- `user_alias`:`external_id` が割り当てられる前に、ID によってユーザーを参照する手段として、顧客が割り当てることができる一意の代替識別子。ユーザーエイリアスは、後で Braze の[ユーザー識別]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/)エンドポイントで使用できるようになった時点で、他のエイリアスまたは `external_id` とマージできます。
+    - [ユーザー識別]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/)エンドポイント内では、`merge_behavior` フィールドを使用して、ユーザーエイリアスプロファイルのどのデータを既知のユーザープロファイルで永続化するかを指定できます。
+    - ユーザーエイリアスを送信可能なプロファイルにするには、メールまたは電話番号あるいはこの両方をプロファイルに標準属性として含める必要があることに注意してください。
+- `device_id`:自動的に生成される、機器固有の識別子。ユーザープロファイルには、複数の`device_ids` を関連付けることができます。たとえば、仕事用コンピューター、ホームコンピューター、タブレット、および iOS アプリでアカウントにログインしたユーザーは、プロファイルに4つの `device_ids` が関連付けられます。
 - Eメールアドレスと電話番号
-    - Brazeのtrack user endpointの識別子としてサポートされている。 
-    - リクエストの識別子としてメールアドレスや電話番号を使用する場合、3つの結果が考えられる：
+    - Braze のユーザー追跡エンドポイントで識別子としてサポートされます。 
+    - リクエスト内でメールアドレスまたは電話番号を識別子として使用する場合、3つの結果が考えられます。
         1. このメールアドレス/電話番号を持つユーザーがBraze内に存在しない場合、メールアドレスのみ/電話番号のみのユーザープロファイルが作成され、リクエスト内のデータがプロファイルに追加される。
-        2. このEメール/電話番号のプロフィールがBraze内にすでに存在する場合、リクエスト内で送信されたデータが含まれるように更新される。
-        3. このEメール／電話番号で複数のプロフィールがあるユースケースでは、最も新しく更新されたプロフィールが優先される。
-    - Eメールのみ/電話のみのユーザープロファイルが存在し、同じEメール/電話の識別プロファイルが作成された場合（同じEメールアドレスと外部IDを持つ別のプロファイルなど）、Brazeは2つ目のプロファイルを作成することに注意。それ以降の更新は、外部IDを持つプロファイルに送られる。
+        2. このメール/電話番号を含むプロファイルが Braze 内にすでに存在する場合、リクエストで送信されたすべてのデータが含まれるようにこのプロファイルが更新される。
+        3. このメール/電話番号を含むプロファイルが複数あるユースケースでは、最後に更新されたプロファイルが優先される。
+    - メールのみ/電話番号のみのユーザープロファイルが存在し、同じメール/電話番号を含む識別プロファイルが作成された場合 (同じメールアドレスと external ID を持つ別のプロファイルなど)、Braze では2つ目のプロファイルが作成されることに注意してください。それ以降の更新は、外部IDを持つプロファイルに送られる。
         - 2つのプロファイルは、Braze[/merge/users]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/)エンドポイントを使用してマージできる。
 
-## 匿名ユーザーを扱う
+## 匿名ユーザーの取り扱い
 
 `external_id` にアクセスすることなく、Brazeでユーザープロファイルを作成または更新する必要があるユースケースの場合、電子メールアドレスや電話番号などの別の識別子をBraze[Export user by identifier]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)エンドポイントに渡すことで、そのユーザーのプロファイルがBraze内に存在するかどうかを判断することができる。 
 
@@ -40,15 +40,15 @@ Brazeのデータ収集方法について詳しく知る：
 }
 ```
 
-Braze内にそのメールアドレスまたは電話番号を持つユーザーが存在する場合、そのユーザーのプロフィールが返される。そうでなければ、空の "users "配列が返される。エクスポート・エンドポイントを使用して、その電子メール・アドレスを持つユーザーがすでに存在するかどうかを判断する利点は、匿名ユーザー・プロファイルがそのユーザーに関連付けられているかどうかを判断できるようになることである。例えば、SDK経由で作成された匿名プロファイル（`braze_id` ）や、以前に作成されたユーザーエイリアスプロファイルなどである。 
+Braze内にそのメールアドレスまたは電話番号を持つユーザーが存在する場合、そのユーザーのプロフィールが返される。そうでなければ、空の "users "配列が返される。エクスポート・エンドポイントを使用して、その電子メール・アドレスを持つユーザーがすでに存在するかどうかを判断する利点は、匿名ユーザー・プロファイルがそのユーザーに関連付けられているかどうかを判断できるようになることである。たとえば、SDK で作成された匿名プロファイル (`braze_id` を含むプロファイル) や、以前に作成されたユーザーエイリアスプロファイルなどです。 
 
-リクエストがユーザープロファイルを返さない場合、ユーザーエイリアスを作成するか、電子メールのみのユーザーを作成するかを選択できる：
+リクエストがユーザープロファイルを返さない場合は、ユーザーエイリアスを作成するか、メールのみのユーザーを作成するかを選択できます。
 
 ### ユーザーエイリアス
 
-ユーザートラックエンドポイントを使用して、エイリアス名として選択した識別子を使用して、ユーザエイリアスを作成する。新しいユーザー・エイリアスが定義されている属性、イベント、または購入オブジェクト内に`false` として`_update_existing_only` を含めることで、エイリアス プロファイルを作成し、そのプロファイルに属性、イベント、および購入を同時に追加することができる。 
+ユーザートラックエンドポイントを使用して、エイリアス名として選択した識別子を使用して、ユーザエイリアスを作成する。新しいユーザーエイリアスが定義されている属性、イベント、または購入オブジェクトに `_update_existing_only` を `false` として含めることで、エイリアスプロファイルを作成し、そのプロファイルに属性、イベント、購入を同時に追加できます。 
 
-ユーザーエイリアスを送信可能なプロファイルとするためには、以下のように、`email` フィールドに電子メールアドレスを含める必要がある。
+ユーザーエイリアスを送信可能なプロファイルにするには、以下に示すように、`email` フィールドにメールアドレスを含める必要があります。
 
 ```json
 {
@@ -69,9 +69,9 @@ Braze内にそのメールアドレスまたは電話番号を持つユーザー
 }
 ```
 
-このユーザーエイリアスを後で特定し、[Identify users]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/)エンドポイントを通じて`external_id` 。 
+後でこのユーザーエイリアスが[ユーザー識別]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/)エンドポイントで使用可能になったときに、このユーザーエイリアスを特定して `external_id` にマージできます。 
 
-### Eメールのみのユーザーを作成する
+### メールのみのユーザーの作成
 
 ユーザートラックエンドポイントの識別子として電子メールアドレスを使用する。 
 
@@ -92,100 +92,100 @@ Braze内にそのメールアドレスまたは電話番号を持つユーザー
 }
 ```
 {% alert important %}
-この機能は現在、早期アクセスとなっている。
+この機能は現在早期アクセス段階です。
 {% endalert %}
 
 ## ユーザープロファイルにデータを同期する
 
 [ユーザートラック]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)
-- これは、ユーザープロファイルへの属性の記録など、Brazeでユーザーを作成および更新できる一般にアクセス可能なエンドポイントである。このエンドポイントには、ワークスペース・レベルで適用される毎分50,000リクエストのレート制限がある。
-- このエンドポイントを使用する場合は、パートナーのドキュメントに示されているように、`partner` キーを含める。
+- これは、ユーザープロファイルへの属性の記録など、Brazeでユーザーを作成および更新できる一般にアクセス可能なエンドポイントである。このエンドポイントには、1分あたり50,000件のリクエストというレート制限がワークスペースレベルで適用されています。
+- このエンドポイントを使用する場合は、パートナーのドキュメントに記載されているように、`partner` キーを含めます。
 
 [クラウドデータ取り込み]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/cloud_ingestion/overview/#what-is-cloud-data-ingestion)
-- ユーザートラックエンドポイントと同様に、データはCloud Data Ingestionを通じてユーザプロファイルに同期することができる。このツールを使用する場合、同期させたいデータウェアハウスのテーブルやビューを設定し、希望のBrazeワークスペースに接続することで、属性、イベント、購入がプロファイルに記録される。
+- ユーザートラックエンドポイントと同様に、クラウドデータ取り込みを介してデータをユーザープロファイルに同期できます。このツールを使用する場合、目的の Braze ワークスペースに同期するデータウェアハウスのテーブルまたはビューを設定して接続することで、属性、イベント、および購入がプロファイルに記録されます。
 
 [データポイント]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points#data-points)
 - Brazeのデータポイント消費モデルでは、値が変更されたかどうかにかかわらず、ユーザープロファイルへの「書き込み」ごとにデータポイントが発生する。このため、変更のあった属性のみをBrazeに送信することを推奨する。 
 
-## ユーザーのオーディエンスをBrazeに送る
+## Braze へのユーザーオーディエンスの送信
 
-[コーホート・インポート・シンク・パートナーのドキュメント]({{site.baseurl}}/partners/isv_partners/cohort_import/)<br>
-- ユーザーのオーディエンスは、BrazeのコホートインポートAPIエンドポイントを使用して、コホートとしてBrazeに同期できる。これらのオーディエンスは、ユーザー属性としてユーザー・プロファイルに保存されるのではなく、当社のセグメンテーション・ツール内のパートナー・ブランドのフィルターを通じて、このコホートを構築し、ターゲットを絞ることができる。これにより、顧客は特定のユーザー・セグメントを見つけやすくなり、ターゲットを絞りやすくなる。
-- コホート・インポートのエンドポイントは公開されておらず、各パートナーに固有のものである。このため、コホートエンドポイントへの同期は、顧客のワークスペースのレート制限にカウントされない。 
+[コホートインポート同期パートナーのドキュメント]({{site.baseurl}}/partners/isv_partners/cohort_import/)<br>
+- ユーザーオーディエンスは、Braze のコホートインポート API エンドポイントを使用して、コホートとして Braze に同期できます。これらのオーディエンスをユーザー属性としてユーザープロファイルに保存するのではなく、お客様がBraze のセグメンテーションツール内のパートナーブランドフィルターを使用して、このコホートを作成し、ターゲットに設定できます。これにより、顧客が特定のユーザーセグメントを見つけてターゲットに設定することが容易になります。
+- コホートインポートエンドポイントはパブリックではなく、各パートナーに固有です。このため、コホートエンドポイントへの同期は、顧客のワークスペースのレート制限にカウントされない。 
 
 [ユーザートラック]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)<br>
-- これは、一般にアクセス可能なエンドポイントであり、ユーザー属性を通じて特定のオーディエンスのユーザーを示すことで、Brazeでユーザーを作成するためにすぐに使用できる。このエンドポイントとコホート・インポート・エンドポイントの主な違いは、このエンドポイントを使用して送信されたオーディエンスはユーザー・プロファイルに保存されるのに対し、コホート・インポート・エンドポイントはセグメンテーション・ツールにフィラーとして表示されることである。このエンドポイントには、ワークスペース・レベルで適用される毎分50,000リクエストのレート制限がある。
-- このエンドポイントを使用する際は、[パートナーのドキュメントに]({{site.baseurl}}/partners/isv_partners/api_partner)示されているように、`partner` キーを含めていることを確認すること。
+- これは、一般にアクセス可能なエンドポイントであり、ユーザー属性を通じて特定のオーディエンスのユーザーを示すことで、Brazeでユーザーを作成するためにすぐに使用できる。このエンドポイントとコホートインポートエンドポイントの主な違いは、このエンドポイントを使用して送信されたオーディエンスはユーザープロファイルに保存されるのに対し、コホートインポートエンドポイントではセグメンテーションツールでフィラーとして表示されることです。このエンドポイントには、1分あたり50,000件のリクエストというレート制限がワークスペースレベルで適用されています。
+- このエンドポイントを使用する場合は、パートナーの[ドキュメント]({{site.baseurl}}/partners/isv_partners/api_partner)に記載されているように、`partner` キーを必ず含めてください。
 
 [データポイント]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points#data-points)<br>
 - Brazeのデータポイント消費モデルでは、値が変更されたかどうかにかかわらず、ユーザープロファイルへの「書き込み」ごとにデータポイントが発生する。
-- データポイントは、コホートインポートとユーザートラックのエンドポイントの両方で発生する。
+- データポイントは、コホートインポートエンドポイントとユーザートラックエンドポイントの両方で発生します。
 
 ## パートナーへのエンゲージメント分析ストリーミング
 
 ### Currents
 
-Currentsは、Brazeのほぼリアルタイムのメッセージエンゲージメント分析ストリーミングツールである。これは、顧客のワークスペースから送信されたキャンペーンとキャンバスのすべての送信、配信、開封、クリックなどに関するユーザーレベルのデータをストリーミングする。注意すべき点がいくつかある：カレントの価格は顧客向けのコネクターごとに設定されているため、新規のカレント・パートナーはすべてEAプロセスを経なければならない。カスタムブランドのUIを構築し、コネクタを一般に公開する前に、パートナーはEAの一部として5社の顧客を持つようお願いしている。 
-- [パートナーの文書]({{site.baseurl}}/partners/isv_partners/currents_integration/)
-- [メッセージ・エンゲージメント・イベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events)\- Currentsコネクタを購入したすべての顧客は、これらのイベントにアクセスできる。
-- [ユーザー行動イベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events)\- Currentコネクタを購入するすべての顧客が、これらのイベントを含む「すべてのイベント」コネクタを購入するとは限らない。 
+Currents は、Braze のほぼリアルタイムのメッセージエンゲージメント分析ストリーミングツールです。これにより、お客様のワークスペースから送信されたキャンペーンおよびキャンバスのすべての送信、配信、開封、クリックなどに関するユーザーレベルのデータがストリーミングされます。いくつかの注意点があります。Currents の価格は、お客様のコネクターあたりの価格であるため、すべての新しい Currents パートナーは EA プロセスを実施する必要があります。カスタムブランドのUIを構築し、コネクタを一般に公開する前に、パートナーはEAの一部として5社の顧客を持つようお願いしている。 
+- [パートナーのドキュメント]({{site.baseurl}}/partners/isv_partners/currents_integration/)
+- [メッセージエンゲージメントイベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events) \- Currents コネクターを購入したすべてのお客様はこのイベントにアクセスできます。
+- [ユーザー行動イベント]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events)\- Current コネクターを購入したすべてのお客様が、このイベントが含まれている「すべてのイベント」コネクターを購入するとは限りません。 
 
-### スノーフレーク・データ・シェア
+### Snowflake データシェア
 
-Snowflake Data Shareコネクタを購入した顧客は、メッセージのエンゲージメントとユーザー行動の両方のイベントに自動的にアクセスできるようになる。Snowflake Data Shareがパートナー統合として使用される場合、Brazeが顧客に代わってパートナーのSnowflakeインスタンスに共有をプロビジョニングする。注意点として、リージョンをまたいだデータ共有は、顧客にとってより高い価格設定となるため、Snowflakeとの統合を希望するパートナーには、`US-EAST-1` および/または `EU-CENTRAL-1`
-- [パートナーの文書]({{site.baseurl}}/partners/isv_partners/currents_integration/)
+Snowflake データシェアコネクターを購入したお客様は、メッセージエンゲージメントイベントとユーザー行動イベントの両方に自動的にアクセスできるようになります。Snowflake データシェアがパートナー連携として使用されている場合、Braze はお客様に代わってパートナーの Snowflake インスタンスに共有をプロビジョニングします。クロスリージョンのデータ共有はお客様にとって価格が高いポイントであるため、Snowflake との統合を希望するパートナーに対し、`US-EAST-1` および/または`EU-CENTRAL-1` にアカウントが必要であるというガイダンスを依頼します。
+- [パートナーのドキュメント]({{site.baseurl}}/partners/isv_partners/currents_integration/)
 
 ## キャンペーンとキャンバスの構築とトリガー
 
 ### Brazeでアセットを作成する
-Brazeは、顧客やパートナーが顧客のワークスペース内でメールテンプレートやコンテンツブロックを作成/更新できるようにするエンドポイントを多数提供している。これらのテンプレートとコンテンツブロックは、顧客のBrazeキャンペーンとキャンバス全体で使用することができる。
+Brazeは、顧客やパートナーが顧客のワークスペース内でメールテンプレートやコンテンツブロックを作成/更新できるようにするエンドポイントを多数提供している。これらのテンプレートとコンテンツブロックは、お客様の Braze キャンペーンおよびキャンバス全体で使用できます。
 - メールテンプレート
-    - [テンプレート・エンドポイントを作成する]({{site.baseurl}}/api/endpoints/templates/email_templates/post_create_email_template/)
+    - [テンプレートエンドポイントを作成する]({{site.baseurl}}/api/endpoints/templates/email_templates/post_create_email_template/)
     - [テンプレートのエンドポイントを更新する]({{site.baseurl}}/api/endpoints/templates/email_templates/post_update_email_template/#rate-limit)
 - [コンテンツブロック]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks#content-blocks) 
-    - [コンテンツ・ブロック・エンドポイントを作成する]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/post_create_email_content_block/)
-    - [コンテンツ・ブロックのエンドポイントを更新する]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/post_update_content_block/)
+    - [コンテンツブロックエンドポイントを作成する]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/post_create_email_content_block/)
+    - [コンテンツブロックエンドポイントを更新する]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/post_update_content_block/)
 
-### APIトリガー・キャンペーンとキャンバス
+### API によりトリガーされるキャンペーンとキャンバス
 
-顧客はAPIトリガーでキャンペーンやキャンバスを設定できる。これらのキャンペーンをトリガーするためのAPIリクエストは、APIトリガープロパティとオーディエンスまたは受信者パラメータを渡すことによって、キャンペーンをさらにパーソナライズおよびセグメント化するために使用することができる。 
-- [API経由でキャンペーンをトリガーする]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns/#request-body)
+顧客はキャンペーンやキャンバスが API によりトリガーされるように設定できます。これらのキャンペーンをトリガーする API リクエストを使用して、API トリガープロパティとオーディエンスパラメーターまたは受信者パラメーターを渡すことで、キャンペーンをさらにパーソナライズおよびセグメント化できます。 
+- [API を使用したキャンペーンのトリガー]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns/#request-body)
     - キャンペーンとは、個々のEメールのような単発のメッセージのことである。
-- [API経由でキャンバスをトリガーする]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/#request-body)
-    - Canvasは、マーケターが複数のメッセージとステップを持つキャンペーンを作成し、まとまったジャーニーを形成できる統一されたインターフェイスである。キャンバスをトリガーすると、キャンバスフローにユーザーを入力することになり、キャンバスの条件に合わなくなるまで、メッセージングを受け取り続けることになる。 
+- [API を使用したキャンバスのトリガー]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/#request-body)
+    - キャンバスは、マーケターが複数のメッセージとステップでキャンペーンを作成し、一貫性のあるジャーニーを形成するための統合インターフェイスです。キャンバスをトリガーすると、キャンバスフローにユーザーを入力することになり、キャンバスの条件に合わなくなるまで、メッセージングを受け取り続けることになる。 
 - [APIトリガープロパティ/キャンバスエントリープロパティ]({{site.baseurl}}/api/objects_filters/trigger_properties_object) 
     - 送信時にメッセージに動的に入力できるデータ。
 
 ### APIキャンペーン
-APIキャンペーン（上記で言及したAPIトリガーキャンペーンとは異なる）を作成する場合、Brazeダッシュボードは`campaign_id` を生成するためにのみ使用される。キャンペーンメッセージ自体はAPIリクエストの中で定義される。 
-- [APIキャンペーンをすぐに送信する]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_messages/)
-- [APIキャンペーンをスケジュールする]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_schedule_messages/)
+API キャンペーン (上記の API によりトリガーされるキャンペーンとは異なります) を作成する場合、Braze ダッシュボードは `campaign_id` を生成するためにのみ使用されます。これによりお客様はキャンペーンレポートのために分析を追跡できます。キャンペーンメッセージ自体はAPIリクエストの中で定義される。 
+- [API キャンペーンをすぐに送信する]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_messages/)
+- [API キャンペーンをスケジュールする]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_schedule_messages/)
 
 ### IDを送信する
-Brazeのエンドポイントを使用して送信IDを生成し、送信ごとにキャンペーン分析を分解するために使用できる。例えば、`campaign_id` （APIキャンペーン）をロケーションごとに作成した場合、送信ごとに送信IDを生成し、特定のロケーションに対して異なるメッセージングがどの程度うまく機能しているかを追跡することができる。 
+Brazeのエンドポイントを使用して送信IDを生成し、送信ごとにキャンペーン分析を分解するために使用できる。たとえば、ロケーションごとに `campaign_id` (API キャンペーン) が作成されている場合、送信ごとに送信 ID を生成して、特定のロケーションに対して異なるメッセージングがどの程度適切に実行されているかを追跡できます。 
 - [IDを送信する]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_create_send_ids/)
 
 ## コネクテッドコンテンツ
 
-コネクテッド・コンテンツは、送信時に指定されたエンドポイントにAPIリクエストを行い、レスポンスで返された内容をメッセージに入力するために、どのチャネル・タイプでも使用できる。
+コネクテッドコンテンツを任意のチャネルタイプ内で使用して、送信時に指定されたエンドポイントに対して API リクエストを実行し、応答で返された内容をメッセージに取り込むことができます。
 
-Connected Contentsの多機能性により、Brazeにはない、あるいはBrazeにはないコンテンツを挿入するために、多くの顧客がこの機能を利用している。一般的な使用例としては、以下のようなものがある：
+コネクテッドコンテンツはその汎用性から、多くのお客様が Braze で存続しないまたは存続できないコンテンツを挿入するために使用する機能になりました。一般的な使用例としては、以下のようなものがある：
 - ブログや記事の内容をメッセージにテンプレート化する
-- 推奨コンテンツ
+- コンテンツレコメンデーション
 - 製品メタデータ
-- ローカリゼーションと翻訳
+- ローカライゼーションと翻訳
 
-注意しなければならないことがある：
-- BrazeはAPIコールには課金せず、データポイントの割り当てにはカウントしない。
-- コネクテッド・コンテンツの回答には1MBの制限がある。
+以下の点に注意してください。
+- Braze は API 呼び出しについて課金せず、データポイント割り当てにはカウントされません。
+- コネクテッドコンテンツ応答には1 MB の制限があります。
 - コネクテッド・コンテンツの呼び出しは、メッセージの送信時に行われるが、アプリ内メッセージは例外で、メッセージの閲覧時にこの呼び出しが行われる。
-- コネクテッド・コンテンツの呼び出しは、redirects.Braze 、パフォーマンス上の理由からサーバーの応答時間が2秒未満であることを要求している。サーバーの応答に2秒以上かかる場合、コンテンツは挿入されない。
-- Brazeのシステムは、受信者ごとに同じConnected Content APIコールを複数回行う場合がある。なぜなら、Brazeは、メッセージペイロードをレンダリングするためにConnected Content APIをコールする必要があるかもしれないし、メッセージペイロードは、検証、再試行ロジック、その他の内部的な目的のために、受信者ごとに複数回レンダリングされる可能性があるからだ。 
+- コネクテッドコンテンツ呼び出しが redirects.Braze に従っていない場合、パフォーマンス上の理由からサーバー応答時間が2秒未満でなければなりません。サーバーの応答時間が2秒よりも長い場合、コンテンツが挿入されません。
+- Braze は、各受信者に複数回、同じコネクテッドコンテンツ API 呼び出しを行うことができます。これは、状況によっては Braze がメッセージペイロードを表示するためにコネクテッドコンテンツ API 呼び出しを行う必要があり、メッセージペイロードは、検証、再試行ロジック、またはその他の内部目的のために、受信者ごとに複数回レンダリングされることがあるためです。 
 
 コネクテッド・コンテンツの詳細については、以下の記事を参照されたい：
-- [コネクテッド・コンテンツに電話をかける][1]
-- [接続されたコンテンツを中止する][2]
-- [コネクテッド・コンテンツの再試行][3]
+- [コネクテッドコンテンツ呼び出しを実行する][1]
+- [コネクテッドコンテンツを中止する][2]
+- [コネクテッドコンテンツの再試行][3]
 
 [1]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call/
 [2]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/aborting_connected_content
diff --git a/_lang/ja/_partners/isv_partners/cohort_import.md b/_lang/ja/_partners/isv_partners/cohort_import.md
index 471b33e3bb7..e4731c70de3 100644
--- a/_lang/ja/_partners/isv_partners/cohort_import.md
+++ b/_lang/ja/_partners/isv_partners/cohort_import.md
@@ -4,15 +4,15 @@ alias: /cohort_import/
 hidden: true
 ---
 
-# パートナーコホートインポートインテグレーション
+# パートナーコホートインポート統合
 
-> パートナーコホートインポートインテグレーション機能を使用すると、パートナーとBrazeを統合して、パートナーのアプリライセンス内で生成されたユーザーをコホートで送信できます。
+> パートナーコホートインポート統合機能により、パートナーは Braze と統合して、パートナーのアプリケーション内で生成されたユーザーのコホートを送信できます。
 
 ## クラスタURL
 
 Brazeは、米国と欧州のさまざまなクラスターでアプリライケーションを開催しています。インポートエンドポイントのURL は、クライアントの企業インスタンスがホストされているクラスターによって異なります。
 
-| インスタンス | RESTエンドポイント |
+| インスタンス | REST エンドポイント |
 | ----- | ------------------------------- |
 | US-01 | `https://rest.iad-01.braze.com` |
 | US-02 | `https://rest.iad-02.braze.com` |
@@ -28,37 +28,37 @@ Brazeは、米国と欧州のさまざまなクラスターでアプリライケ
 
 ## エンドポイントURL
 
-最上位のURL はクラスタ固有であるだけでなく、それぞれのエンドポイントもパートナー固有です。たとえば、US01 クラスタにインポートする場合、URL の形式は`https://rest.iad-01.braze.com/partners/[partner_name]/…` となります。ここで、`[partner_name]` は通常、パートナーのビジネスの名前です。それぞれのエンドポイントの詳細については、次の項で説明します。
+最上位のURL はクラスタ固有であるだけでなく、それぞれのエンドポイントもパートナー固有です。たとえば、US01 クラスタにインポートする場合、URL の形式は`https://rest.iad-01.braze.com/partners/[partner_name]/…` となります。ここで、`[partner_name]` は通常、パートナーのビジネスの名前です。それぞれのエンドポイントの詳細については、以降のセクションで説明します。
 
 ## 認証
 
-コホートをBrazeに読み込むには、2つの認証鍵が必要です。
+Braze にコホートデータをインポートするには、2つの認証キーが必要です。
 
-### 提携API キー
+### パートナー API キー
 
-Partner API Key は、統合パートナーを識別し、インポートに有効なものとしてリクエストを認証します。このキーは、`partner_api_key` フィールドのリクエストの本文に含まれている必要があります。
+パートナー API キーにより、統合パートナーが識別され、リクエストがインポートに対して有効であると認証されます。このキーは、`partner_api_key` フィールドのリクエストの本文に含まれている必要があります。
 
-パートナーのアプリライセンスでインテグレーションを設定する場合は、クライアントにBrazeクラスターを指定してもらう必要があります。これにより、インテグレーションは、データのインポート時に使用するクラスターURL とパートナーAPI キーを認識できるようになります。
+パートナーのアプリケーションで統合を設定する場合は、クライアントに対し、クライアントの Braze クラスターを指定するように依頼してください。これにより、データのインポート時に使用するクラスター URL とパートナーAPI キーを統合で認識できるようになります。
 
-Brazeは、パートナーが統合開発を開始する前に、パートナーAPIキーをパートナーに提供します。一般的に、すべてのUSクラスターに有効な単一のキーと、EUクラスターに有効な別のキーを提供します。
+パートナーが統合開発を開始する前に、Braze からパートナー API キーがパートナーに提供されます。一般的に、すべての US クラスターで有効な1つのキーと、EU クラスターで有効なもう1つのキーが提供されます。
 
 ### クライアントデータインポートキー
 
 クライアントデータインポートキーは、コホートをインポートするクライアント ワークスペースを識別します。このキーは、`client_secret` フィールドのリクエストの本文に含まれている必要があります。
 
-この鍵は、パートナの統合設定s のクライアントのダッシュボードで生成されます。提携先のアプリライセンスでインテグレーションを設定する場合は、クライアントにデータインポートキーを指定してもらう必要があります。これにより、インテグレーションでデータを送信するクライアントとワークスペースがわかります。
+このキーは、クライアントのダッシュボードのパートナーの統合設定で生成されます。パートナーのアプリケーションで統合を設定する場合、クライアントにデータインポートキーを指定するように依頼する必要があります。これにより、データを送信するクライアントとワークスペースを統合で認識できるようになります。
 
-## 原薬エンドポイント規格
+## API エンドポイントの仕様
 
-### コホートネームエンドポイント
+### コホート名エンドポイント
 
-コホートの名前エンドポイントを使用して、そのID に基づいてコホートの名前を指定できます。このエンドポイントは、コホートが最初にBraze にエクスポートされたとき、またはBraze がすでに認識しているコホートの名前が変更されたときに呼び出されます。
+コホート名エンドポイントを使用して、その ID に基づいてコホートの名前を指定できます。このエンドポイントは、コホートが最初に Braze にエクスポートされたとき、または Braze がすでに認識しているコホートの名前が変更されたときに呼び出されます。
 
 | フィールド | タイプ | 必須 | メモ |
 | ----- | ---- | -------- | ----- |
-| `partner_api_key` | String | はい | パートナー固有のAPI キー。パートナーからBrazeへのすべてのリクエストで使用されます。このキーはクラスタ固有です([パートナーAPI キー](#partner-api-key)を参照)。そのため、パートナは、どのコホートs が書き込まれるクラスターかを知る必要があります。 |
+| `partner_api_key` | String | はい | パートナー固有のAPI キー。パートナーからBrazeへのすべてのリクエストで使用されます。このキーはクラスター固有であるため (「[パートナー API キー](#partner-api-key)」を参照)、パートナーはコホートの書き込み先クラスターを把握している必要があります。 |
 | `client_secret` | String | はい | コホートが属するクライアントのデータインポートキー。 |
-| `cohort_id` | String | はい | コホートのID。この識別子は、指定したクライアントに対して一意である必要があります。 |
+| `cohort_id` | String | はい | コホートの識別子。この識別子は、指定したクライアントに対して一意である必要があります。 |
 | `name` | String | はい | コホートのクライアント指定の名前 |
 | `created_at` | String | はい | ISO-8601 形式のタイムスタンプ |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
@@ -78,14 +78,14 @@ Brazeは、パートナーが統合開発を開始する前に、パートナー
 
 ### ユーザコホート エンドポイント
 
-ユーザー コホート エンドポイントでは、特定のコホートに追加または削除されたユーザーを指定できます。このエンドポイントは、コホートのリフレッシュ時に呼び出す必要があります。コホートに新規に入力したか、最後の更新以降にコホートを離れたユーザーのみがBraze に送信されます。
+ユーザー コホート エンドポイントでは、特定のコホートに追加または削除されたユーザーを指定できます。このエンドポイントは、コホートの更新時に呼び出す必要があります。コホートに新規に入ったユーザー、または最後の更新以降にコホートを離れたユーザーのみが Braze に送信されます。
 
 | フィールド | タイプ | 必須 | メモ |
 | ----- | ---- | -------- | ----- |
-| `partner_api_key` | String | はい | パートナー固有のAPI キー。パートナーからBrazeへのすべてのリクエストで使用されます。このキーはクラスタ固有であるため([パートナーAPI キー](#partner-api-key)を参照)、インテグレーションでは、どのコホートs が書き込まれるクラスターかを知る必要があります。 |
+| `partner_api_key` | String | はい | パートナー固有のAPI キー。パートナーからBrazeへのすべてのリクエストで使用されます。このキーはクラスター固有であるため (「[パートナー API キー](#partner-api-key)」を参照)、統合がコホートの書き込み先クラスターを認識している必要があります。 |
 | `client_secret` | String | はい | コホートが属するクライアントのデータインポートキー。 |
-| `cohort_id` | String | はい | コホートのID。識別子は指定されたクライアントに対して一意である必要があります。 |
-| `cohort_changes` | オブジェクト配列 | はい | オブジェクトには2 つのフィールドs を指定できます。1 つ、`user_ids` は必須であり、`external_ids`、`device_ids`、および`aliases` の配列にすることができます。各エレメントは、コホート内のステータスが変更されたユーザーのID です。2 番目のフィールド`should_remove` は、オプションのブール値で、このオブジェクトのユーザーs を追加する代わりにコホートから削除する必要があるかどうかを示します。デフォルトが偽です。最初に、ユーザーの外部ユーザー ID と一致しないIDを無視します。つまり、匿名ユーザーはコホートに追加または削除できません。1 つのリクエスト内のユーザー IDs の合計の最大長は1000 です。たとえば、識別されたユーザーのデバイスID を渡した場合、そのユーザーは追加または削除されません。識別されたユーザーには外部ID を使用する必要があります。 |
+| `cohort_id` | String | はい | コホートの識別子。識別子は指定されたクライアントに対して一意である必要があります。 |
+| `cohort_changes` | オブジェクト配列 | はい | オブジェクトには2つのフィールドを含めることができます。1番目の `user_ids` は必須であり、`external_ids`、`device_ids`、および`aliases` の配列にすることができます。各エレメントは、コホート内のステータスが変更されたユーザーのID です。2番目のフィールド `should_remove` は、オプションのブール値で、このオブジェクトのユーザーをコホートへの追加ではなく、コホートから削除するかどうかを示します。デフォルトは false です。最初に、ユーザーの外部ユーザー ID と一致しないIDを無視します。つまり、匿名ユーザーはコホートに追加または削除できません。1 つのリクエスト内のユーザー IDs の合計の最大長は1000 です。たとえば、識別されたユーザーのデバイス ID を渡した場合、そのユーザーは追加または削除されません。識別されたユーザーには外部ID を使用する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 #### リクエスト例:
@@ -104,11 +104,11 @@ Brazeは、パートナーが統合開発を開始する前に、パートナー
 
 ## レート制限
 
-ユーザー コホート エンドポイント内のリクエストごとに1000 ユーザー ID s の上限を除き、これらのエンドポイントs は特にレート制限 ed ではありません。
+ユーザーコホートエンドポイントでのリクエストあたり最大1000のユーザー ID という制限を除き、これらのエンドポイントでは特にレート制限はありません。
 
 ## コホートフィルター
 
-Braze は、パートナーコホート内にある場合、ダッシュボード ユーザーがターゲットオーディエンスにユーザーs を含めるか除外することを許可するフィルターを追加します。フィルターには、そのクライアントのBrazeが認識しているすべてのコホートの名前のドロップダウンリストが表示されます。このフィルターは、提携企業とBrazeがこの統合で提携することに同意したクライアントのみが見ることができます。
+Braze は、ユーザーがパートナーコホートに含まれている場合に、ダッシュボードユーザーがターゲットオーディエンスにそれらのユーザーを含めるかまたは除外することができるようにするフィルターを追加する予定です。フィルターには、そのクライアントのBrazeが認識しているすべてのコホートの名前のドロップダウンリストが表示されます。このフィルターは、パートナーと Braze がこの統合で連携することに同意しているクライアントにのみ表示されます。
 
 ## トラブルシューティング
 
@@ -118,11 +118,11 @@ Braze は、パートナーコホート内にある場合、ダッシュボー
 | ----- | ---- |
 | `401` | 不正なパートナーAPI キー |
 |  | 不正なクライアントシークレット |
-|  | クライアントシークレットでパートナーがクライアントに対して有効になっていません:**<クライアントシークレット>** |
-| `400` | `cohort_id` 有効な文字列である必要があります |
-|  | `cohort_changes` は、`user_ids` および/または`device_ids` m アプリが文字列の配列、または`aliases` オブジェクトを持つオブジェクトの配列である必要があります |
-|  | リクエストごとに許可されるのは、1000 `user_ids`、`device_ids`、および`aliases` のみです |
-|  | `name` 空でない文字列でなければなりません |
+|  | クライアントシークレット **<client secret>** が設定されているクライアントでパートナーが有効になっていません |
+| `400` | `cohort_id` は有効な文字列でなければなりません |
+|  | `cohort_changes` は、キー `user_ids` および/または `device_ids` を持ち、文字列の配列にマッピングされているオブジェクトの配列であるか、または `aliases` オブジェクトである必要があります |
+|  | リクエストあたりの許可されている `user_ids`、`device_ids`、および`aliases` の数は1000個です。 |
+|  | `name` は、空ではない文字列にする必要があります。 |
 |  | `created_at` は、[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)文字列として有効な時刻である必要があります |
 {: .reset-td-br-1 .reset-td-br-2}
 
diff --git a/_lang/ja/_partners/isv_partners/currents_integration.md b/_lang/ja/_partners/isv_partners/currents_integration.md
index 8543ca73028..71e879ab34d 100644
--- a/_lang/ja/_partners/isv_partners/currents_integration.md
+++ b/_lang/ja/_partners/isv_partners/currents_integration.md
@@ -1,10 +1,10 @@
 ---
-nav_title: カスタム電流コネクタ
+nav_title: カスタム Currents コネクター
 alias: /currents_connector/
 hidden: true
 ---
 
-# パートナー・カスタム・カレンツ・コネクター
+# パートナーのカスタム Currents コネクター
 
 ## シリアライズとデータ形式
 
@@ -120,7 +120,7 @@ events "をキーとするトップレベルのJSONオブジェクトが存在
 }
 ```
 
-### キャンバス関連イベント
+### キャンバスに関連付けられているイベント
 
 以下は、キャンバスに関連付けられた場合に表示される、様々なイベントのイベントペイロードの例である：
 
@@ -313,15 +313,15 @@ events "をキーとするトップレベルのJSONオブジェクトが存在
 
 ## 認証
 
-必要な場合、認証は、[RFC 6750で](https://tools.ietf.org/html/rfc6750#section-2.1)規定されているように、`Bearer` 認証スキームを介して、HTTP`Authorization` ヘッダーにトークンを渡すことで実行される。`Authorization` ヘッダーを使用することで、[RFC 7235に](https://tools.ietf.org/html/rfc7235)準拠したカスタム（Braze独自の）のキーと値のペアの認証スキーム（たとえば、AWSのカスタム認証スキームがどのように機能するか）に切り替えることができるからだ。
+必要に応じて、[RFC 6750](https://tools.ietf.org/html/rfc6750#section-2.1) で指定されているように、`Bearer` 認可スキームを介して HTTP `Authorization` ヘッダーにトークンを渡すことで認証が実行されます。また、これには今後実装する可能性があるあらゆるカスタム認証スキームとの上位互換性が自動的に備わっています。これは、`Authorization` ヘッダーを使用することで、今後 [RFC 7235](https://tools.ietf.org/html/rfc7235)に準拠したカスタム (Braze 独自の) キー値ペアの認証スキーム (たとえば、AWS のカスタム認証スキームの仕組みなど) を使用することにした場合に、その認証スキームに切り替えることができるためです。
 
-RFC 6750に従い、トークンは少なくとも1文字のBase64エンコードされた値となる。(もちろん、パートナーや顧客が信じられないほど弱いトークンを選ぶ可能性がないことを知るために、私たちはパートナーや顧客を吟味しなければならないが)。RFC6750の特筆すべき奇妙な点は、トークンに通常のBase64文字に加えて次の文字を含めることができることである：'-'、'.'、'_'、'~'。トークンの正確な内容は、私たちのどのシステムにとってもまったく違いがないため、パートナーがトークンにこれらの文字を含めるかどうかを気にすることはない。
+RFC 6750に従い、トークンは1文字以上からなるBase64エンコード値になります。(もちろん、パートナーや顧客が信じられないほど弱いトークンを選ぶことがないようにするために、パートナーや顧客を精査する必要があります。)RFC 6750の特筆すべき点は、通常のBase64文字に加えて、トークンに「-」、「。」、「_」、および「~」を使用できることです。トークンの正確な内容は、どのシステムにおいても違いはないので、パートナーがトークンにこれらの文字を使用するかどうかについて懸念することはありません。
 
-RFC 6750に従い、ヘッダーは以下のフォーマットで構築される：
+RFC 6750に従い、ヘッダーは以下の形式で構成されます。
 
 `"Authorization: Bearer " + <token>`
 
-例えば、APIトークンが`0p3n5354m3==` の場合、Authorizationヘッダーは以下のようになる：
+たとえば API トークンが `0p3n5354m3==` の場合、Authorization ヘッダーは次のようになります。
 
 `Authorization: Bearer 0p3n5354m3==`
 
@@ -331,33 +331,33 @@ RFC 6750に従い、ヘッダーは以下のフォーマットで構築される
 
 `Braze-Currents-Version: 1`
 
-リクエストのペイロードやセマンティクスに重大な後方互換性のない変更を加えない限り、バージョンは常に1になる。この数字が増えることはあまりないだろう。 
+リクエストのペイロードやセマンティクスに重大な後方互換性のない変更を加えない限り、バージョンは常に1になる。この数値を頻繁に増加することは想定されていません。 
 
 個々のイベントは、既存のAvroスキーマと同じ進化ルールに従う。つまり、すべてのイベントのフィールドは、以下のルールを含む、 Avro の後方互換性の定義に従って、以前のバージョンのイベント ペイロードとの後方互換性が保証される：
 
 - 特定のイベントフィールドは、常に同じデータ型を持つことが保証される。
-- 時間の経過とともにペイロードに追加される新しいフィールドは、すべての当事者によってオプションとみなされなければならない。
+- 時間の経過とともにペイロードに追加される新しいフィールドは、すべての関係者がオプションと見なす必要があります。
 - 必須項目が削除されることはない。
-  - 何が "必須 "とみなされるかは、おそらくAvroスキーマから自動生成されるドキュメントによって指定されるだろう。そのためには、Avroスキーマのフィールドにメタデータを付与し、そのメタデータを読み込んでドキュメントを生成する特別なスクリプトが必要になる。
+  - 「必須」のフィールドは、一元的な信頼できる情報源として、Arvo スキーマから自動生成するドキュメントで指定されます。このためには、メタデータを使用して Avro スキーマフィールドに注釈付けし、そのメタデータを読み取ってドキュメントを生成できる特殊なスクリプトが必要になります。
 
-## エラー処理と再試行メカニズム
+## エラー処理と再試行のメカニズム
 
 エラーの場合、Brazeは受け取ったHTTPリターンコードに基づいてリクエストをキューに入れ、再試行する。以下にリストされていないHTTPエラーコードは、HTTP 5XXエラーとして扱われる。
 
 {% alert important %}
-もし我々のリトライ・メカニズムが24時間以上エンドポイントへのイベント配信に失敗した場合、データ損失が発生する。
+再試行メカニズムが24時間以上イベントをエンドポイントに配信できない場合、データが失われます。
 {% endalert %}
 
-以下のHTTPステータスコードが、コネクター・クライアントによって認識される：
+以下の HTTP ステータスコードがコネクタークライアントによって認識されます。
 - **2XX**\- 成功
   - イベントデータは再送されない。<br><br>
 - **5XX**\- サーバーサイドエラー
-  - イベントデータは、ジッターを伴う指数バックオフパターンで再送される。24時間以内にデータが正常に送信されなければ、そのデータは削除される。<br><br>
+  - イベントデータは、ジッターを伴う指数バックオフパターンで再送される。24時間以内にデータが正常に送信されなかった場合、データは破棄されます。<br><br>
 - **400**\- クライアント側のエラー
-  - 我々のコネクタは、何らかの形で少なくとも1つの不正なイベントを送信した。この場合、イベントデータはサイズ1のバッチに分割され、再送信される。これらのsize-1バッチの中で、追加のHTTP 400レスポンスを受け取ったイベントは、永久にドロップされる。パートナーや顧客は、このような現象が発生したことを発見した場合、私たちに知らせるよう奨励されるべきである。<br><br>
+  - コネクターから1つ以上の不正な形式のイベントが送信されました。この場合、イベントデータはサイズ1のバッチに分割され、再送信される。追加の HTTP 400応答を受け取るサイズ1のバッチ内のイベントはすべて、完全に破棄されます。パートナーや顧客は、このような現象が発生したことを発見した場合、私たちに知らせるよう奨励されるべきである。<br><br>
 - **401**（許可されていない）、**403**（禁止）、**404**
-  - コネクタが無効な認証情報で構成された。コネクタタスクは送信を停止し、"Failed "とマークされる。イベントデータは、2分から5分の遅延後に再送信される（これは、コネクト・タスク・リスターターによって処理される）。この問題が48時間以内に顧客によって解決されない場合、イベントデータは削除される。<br><br>
-- **413**\- ペイロードが大きすぎる
+  - コネクタが無効な認証情報で構成された。コネクタータスクは送信を停止し、「Failed」としてマークされます。イベントデータは、2分～5分の遅延の後に再送信されます (これは Connect Task Restarter (コネクトタスク再起動機能) によって処理されます)。この問題が48時間以内に顧客によって解決されない場合、イベントデータは破棄されます。<br><br>
+- **413** — Payload Too Large
   - イベントデータは小さなバッチに分割され、再送信される。<br><br>
-- **429**\- リクエストが多すぎる
-  - レート制限を示す。イベントデータは、ジッターを伴う指数バックオフパターンで再送される。24時間以内にデータが正常に送信されなければ、そのデータは削除される。
\ No newline at end of file
+- **429** — Too Many Requests
+  - レート制限を示す。イベントデータは、ジッターを伴う指数バックオフパターンで再送される。24時間以内にデータが正常に送信されなかった場合、データは破棄されます。
\ No newline at end of file
diff --git a/_lang/ja/_partners/isv_partners/data_transformation.md b/_lang/ja/_partners/isv_partners/data_transformation.md
index 9b2b5b320b1..1445ed9ed51 100644
--- a/_lang/ja/_partners/isv_partners/data_transformation.md
+++ b/_lang/ja/_partners/isv_partners/data_transformation.md
@@ -3,22 +3,22 @@ nav_title: データ変換
 hidden: true
 ---
 
-# Braze データ変換
+# Braze Data Transformation
 
 > Braze [データ変換]({{site.baseurl}}/data_transformation/)は、パートナープラットフォームからのWebhookを取り込み、顧客がそのWebhookのペイロードをBrazeユーザープロファイル上の属性、イベント、購入などの目的のユーザーデータに変換するためのマッピングを定義できるようにします。
 
-## データ変換に基づく統合はどのように見えるか
+## Data Transformation に基づく統合の仕組み
 
-データ変換機能に基づくパートナー連携は、パブリックドキュメントを通じて顧客と共有される変換コードテンプレートである可能性があります。
+Data Transformation 機能に基づくパートナー連携は、公開ドキュメントを通じて顧客と共有される変換コードテンプレートである可能性があります。
 
-相互の顧客にとって、それは次のように見えるでしょう:
+共通のお客様にとっては、次のようになります。
 
 1. 彼らはあなたのプラットフォームにログインし、webhookを設定します。
-2. 彼らはBrazeチームと協力してBrazeデータ変換にアクセスし、Brazeダッシュボード内で新しい変換を作成します。
+2. Braze チームと連携して Braze Data Transformation にアクセスし、Braze ダッシュボード内に新しい変換を作成します。
 3. 変換によって生成されたURLがコピーされます。
 4. Brazeに戻って、コピーした変換URLにテストWebhookを送信します。
 5. Brazeでは、変換コードテンプレートをコピーして貼り付けます。
-6. それらは変革を可能にします。
+6. 変換を有効にします。
 7. 有効にすると、Brazeユーザー検索ツールを使用して、Webhookに基づいてユーザープロファイルが更新されていることを確認し、必要に応じて変換コードを編集できます。
 
 {% alert tip %}
diff --git a/_lang/ja/_partners/isv_partners/snowflake_datasharing.md b/_lang/ja/_partners/isv_partners/snowflake_datasharing.md
index f1426108248..3a21e2c4bd3 100644
--- a/_lang/ja/_partners/isv_partners/snowflake_datasharing.md
+++ b/_lang/ja/_partners/isv_partners/snowflake_datasharing.md
@@ -1,13 +1,13 @@
 ---
-nav_title: スノーフレーク・データ共有
+nav_title: Snowflake データシェアリング
 hidden: true
 ---
 
-# スノーフレーク・データ共有の統合
+# Snowflake データシェアリング統合
 
 > Snowflake Data Shareが統合方法として使用される場合、Brazeが顧客に代わってSnowflakeインスタンスに共有をプロビジョニングする。この共有には、すべてのメッセージのエンゲージメントとユーザー行動のイベントが自動的に含まれる。
 
-シェアは、顧客がSnowflake Data Shareの権利を購入した後、顧客ごとにプロビジョニングされる。顧客がデータ共有を要求すると、Brazeは顧客のワークスペースに共有を追加し、顧客はセルフサービスUIを使って関連するパートナーのSnowflakeアカウントデータを追加できる。
+顧客が Snowflake データシェア資格を購入した後、シェアは顧客ごとにプロビジョニングされます。顧客がデータ共有を要求すると、Brazeは顧客のワークスペースに共有を追加し、顧客はセルフサービスUIを使って関連するパートナーのSnowflakeアカウントデータを追加できる。
 
 ![]({% image_buster /assets/img/snowflake.png %})
 
@@ -15,10 +15,10 @@ hidden: true
 
 ![]({% image_buster /assets/img/snowflake2.png %})
 
-Snowflakeインスタンス内では、リージョンごとに1つのシェアが表示される。各テーブルには、`app_group_id` というカラムがあり、これが事実上、Brazeのテナントキーとなっている。同じリージョン内のシェアに新しい顧客が追加されると、既存のテーブル内に異なる`app_group_ids` として表示される。
+Snowflakeインスタンス内では、リージョンごとに1つのシェアが表示される。各テーブルには `app_group_id` という列があり、これは実質的な Braze のテナントキーです。新しい顧客が同じリージョン内のシェアに追加されると、この顧客は既存のテーブル内では異なる `app_group_ids` として表示されます。
 
 {% alert important %}
-Brazeは現在、すべてのユーザーレベルのデータをSnowflake AWSのUS East-1とEU-Central（フランクフルト）リージョンでホストしている。Brazeは地域を越えて共有することができるが、`US-EAST-1` および/または`EU-CENTRAL-1` と共有するのが顧客にとって最も費用対効果が高い。
+Braze は現在、すべてのユーザーレベルのデータを Snowflake AWS US East-1 および EU-Centra (フランクフルト) リージョンでホストしています。Braze はクロスリージョンで共有できますが、`US-EAST-1` および/または `EU-CENTRAL-1` と共有すると、これは顧客にとって最もコスト効率が高くなります。
 {% endalert %}
 
 {% alert tip %}
@@ -27,27 +27,27 @@ Brazeは現在、すべてのユーザーレベルのデータをSnowflake AWS
 
 ## 重複イベントを処理する
 
-重複は予想されるが、すべてのイベントはIDカラムという一意の識別子を持っている。重複は`select distinct(id)` で削除できる。
+重複は予想されるが、すべてのイベントはIDカラムという一意の識別子を持っている。`select distinct(id)` を実行すると重複を解消できます。
 
-## 壊れる変更と壊れない変更
+## 破壊的な変更と非破壊的な変更
 
 ### 非破壊的な変更
 
-壊れることのない変更はいつでも可能であり、一般的に追加機能を提供する。壊れない変更の例：
+非破壊的な変更はいつでも発生する可能性があり、一般的に追加の機能を提供します。非破壊的な変更の例には次のものがあります。
 - 新しいテーブルまたはビューを追加する
 - 既存のテーブルやビューにカラムを追加する
 
 {% alert important %}
-新しいカラムは非破壊とみなされるため、Brazeでは、`SELECT *` クエリを使用する代わりに、各クエリで対象カラムを明示的にリストすることを強く推奨している。あるいは、カラム名を明示したビューを作成し、テーブルに直接問い合わせるのではなく、ビューに問い合わせることもできる。
+新しい列の追加は非破壊的な変更と見なされるため、Braze では `SELECT *` クエリを使用する代わりに、各クエリで関心のある列を明示的に列挙することを強くお勧めします。または、列に明示的に名前を付けるビューを作成してから、テーブルではなくそれらのビューを直接クエリすることもできます。
 {% endalert %}
 
 ### 破壊的な変更
 
-可能な限り、変更にはアナウンスと移行期間を設ける。変更点の例としては、以下のようなものがある：
+可能な場合には、破壊的な変更の前に通知を行い、移行期間を設けます。破壊的な変更の例には次のものがあります。
 - テーブルまたはビューを削除する
 - 既存のテーブルやビューからカラムを削除する
 - 既存のカラムのタイプまたはヌル可能性を変更する
 
-## 一般データ保護規則（GDPR）への対応
+## 一般データ保護規則 (GDPR) への準拠
 
 Brazeが保存するほぼすべてのイベント記録には、ユーザーの個人を特定できる情報（PII）を表すフィールドがいくつか含まれている。いくつかのイベントには、電子メールアドレス、電話番号、デバイスID、言語、性別、位置情報が含まれることがある。ユーザーの忘れ去り要求がBrazeに提出された場合、Brazeは、そのユーザーに属するイベントのPIIフィールドを無効にする。こうすることで、その出来事の歴史的記録を削除することはないが、その出来事を特定の個人に結びつけることはできなくなる。
diff --git a/_lang/ja/_partners/message_orchestration.md b/_lang/ja/_partners/message_orchestration.md
index 07a6ea21e2a..c8552e88d71 100644
--- a/_lang/ja/_partners/message_orchestration.md
+++ b/_lang/ja/_partners/message_orchestration.md
@@ -14,9 +14,9 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Message Orchestration"
 
 valid_partner_list:
-- name: アルパコ
+- name: Alpaco
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/alpaco/
-- name: アンタヴォ
+- name: Antavo
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/antavo/
 - name: Jampp
   url: /docs/partners/message_orchestration/additional_channels/retargeting/jampp/
@@ -42,7 +42,7 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/attribution/branch/branch_for_deeplinking/
 - name: Kochava
   url: /docs/partners/message_orchestration/attribution/kochava/
-- name: 単数
+- name: Singular
   url: /docs/partners/message_orchestration/attribution/singular/
 - name: Vizbee
   url: /docs/partners/message_orchestration/attribution/vizbee_for_tv_deeplinking/
@@ -76,27 +76,27 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/additional_channels/messaging/line/  
 - name: Shopify
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/shopify/
-- name: ヨトポ
+- name: Yotpo
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/yotpo/
-- name: クナック
+- name: Knak
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/knak/
-- name: エクストール
+- name: Extole
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/extole/
-- name: バイラルスイープ
+- name: ViralSweep
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/viralsweep/
-- name: サーヴィケイト
+- name: Survicate
   url: /docs/partners/message_orchestration/channel_extensions/surveys/survicate/
 - name: Quikly
   url: /docs/partners/message_orchestration/additional_channels/retargeting/quikly/
-- name: IAMスタジオ（NNT）
+- name: IAM Studio (NNT)
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/iam_studio/
 - name: Ada
   url: /docs/partners/message_orchestration/channel_extensions/surveys/ada/
-- name: B.層 
+- name: B.Layer 
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/blayer/
-- name: セージフロー
+- name: Sageflo
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/sageflo/
-- name: ニフト
+- name: Nift
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/nift/
 - name: Sendbird
   url: /docs/partners/message_orchestration/additional_channels/messaging/sendbird/  
@@ -104,9 +104,9 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/additional_channels/messaging/regal/
 - name: Kognitiv
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/kognitiv/
-- name: オロ
+- name: Olo
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/olo/
-- name: タイプフォーム
+- name: Typeform
   url: /docs/partners/message_orchestration/channel_extensions/surveys/typeform/
 - name: Friendbuy
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/friendbuy/
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels.md b/_lang/ja/_partners/message_orchestration/additional_channels.md
index cf7511b05e9..7a3f78fcf32 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels.md
@@ -20,7 +20,7 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/additional_channels/retargeting/remerge/
 - name: Facebook
   url: /docs/partners/message_orchestration/additional_channels/retargeting/facebook/
-- name: パスキー
+- name: Passkit
   url: /docs/partners/message_orchestration/additional_channels/mobile_wallet/passkit/
 - name: Inkit
   url: /docs/partners/message_orchestration/additional_channels/direct_mail/inkit/
@@ -36,7 +36,7 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/additional_channels/messaging/line/  
 - name: Quikly
   url: /docs/partners/message_orchestration/additional_channels/retargeting/quikly/
-- name: センドバード
+- name: Sendbird
   url: /docs/partners/message_orchestration/additional_channels/messaging/sendbird/      
 - name: Regal
   url: /docs/partners/message_orchestration/additional_channels/messaging/regal/    
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/calendar/rokt_calendar.md b/_lang/ja/_partners/message_orchestration/additional_channels/calendar/rokt_calendar.md
index baf809cfc6a..eb6e90ffb4c 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/calendar/rokt_calendar.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/calendar/rokt_calendar.md
@@ -1,6 +1,6 @@
 ---
-nav_title: ロクト・カレンダー
-article_title: ロクト・カレンダー
+nav_title: Rokt Calendar
+article_title: Rokt Calendar
 alias: /partners/rokt_calendar/
 description: "この参考記事では、BrazeとRokt Calendarの提携について概説している。Rokt Calendarは、ダイナミックなカレンダー・マーケティング・テクノロジーで、ブランドはカレンダー・イベントや通知の形で、1:1のイベントやプロモーション・コミュニケーションをプッシュすることができる。"
 page_type: partner
@@ -8,65 +8,65 @@ search_tag: Partner
 
 ---
 
-# ロクト・カレンダー
+# Rokt Calendar
 
-> [Rokt Calendarは](https://www.rokt.com/rokt-calendar/)、1:1イベントやプロモーション・コミュニケーションをカレンダーイベントや通知の形でプッシュすることを可能にするダイナミック・カレンダー・マーケティング・テクノロジーである。
+> [Rokt Calendar](https://www.rokt.com/rokt-calendar/) は、ブランドがカレンダーイベントや通知の形式で1:1イベントやプロモーションコミュニケーションをプッシュできるようにするダイナミックなカレンダーマーケティングテクノロジーです。
 
-BrazeとRokt Calendarの統合により、Rokt Calendarの購読者とそのデータは、Brazeのウェブフックを介してBrazeにプッシュされる。そして、このデータをBraze Canvasesのジャーニーターゲティングとオーディエンスセグメンテーションに使用することができる。 
+Braze と Rokt Calendar の統合により、Rokt Calendar のサブスクライバーとそのデータを Braze Webhook 経由で Braze にプッシュできます。その後、Braze キャンバスでこのデータを使用して、以下のカスタム [Rokt Calendar 属性](#audience-segmentation)を使用したジャーニーターゲティングとオーディエンスセグメンテーションを行うことができます。 
 
 ## 前提条件
 
 | 必要条件  | 説明 |
 | ------------ | ----------- |
-| 六連カレンダーのアカウント | このパートナーシップを利用するには、クライアント専用のRokt Calendarアカウントが必要である。[sales-calendar@rokt.com](mailto:sales-calendar@rokt.com)に連絡して、アカウント・マネージャーと話す。  |
-| ロクト・カレンダーの設定 | Roktカレンダーのアカウントマネージャーが、あなたのニーズに合わせて、以下のような設定を含む、最適なカレンダーを設定する：<br>\- マージフラグ<br>\- 加入者IDフォールバックフラグ<br>\- 必要であれば、電子メールのキャプチャ |
+| Rokt Calendar アカウント | このパートナーシップを利用するには、クライアント専用のRokt Calendarアカウントが必要である。[sales-calendar@rokt.com](mailto:sales-calendar@rokt.com)に連絡して、アカウント・マネージャーと話す。  |
+| Rokt Calendar の設定 | Roktカレンダーのアカウントマネージャーが、あなたのニーズに合わせて、以下のような設定を含む、最適なカレンダーを設定する：<br>\- マージフラグ<br>\- 加入者IDフォールバックフラグ<br>\- 必要であれば、電子メールのキャプチャ |
 | Rokt Calendar OAuth認証情報 | Roktカレンダーのアカウントマネージャーから提供されるこのキーで、BrazeとRoktカレンダーのアカウントを接続することができる。<br><br>これは、Brazeダッシュボードの**「設定**」>「**接続コンテンツ**」で作成できる。 |
-| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。このキーをRokt Calendarのアカウントマネージャーに提供する必要がある。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| [Braze RESTエンドポイント]({{site.baseurl}}/api/basics/#endpoints) | RESTエンドポイントのURL。エンドポイントは、インスタンスのBraze URLに依存する。 |
-| 外部加入者ID | これは、Roktカレンダーの購読プロセスで、カレンダーの購読者とBrazeユーザーを照合するために使用される識別子である。これは六連カレンダーに渡すものだ。|
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。このキーを Rokt Calendar アカウントマネージャーに提供する必要があります。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
+| [Braze REST エンドポイント]({{site.baseurl}}/api/basics/#endpoints) | RESTエンドポイントのURL。エンドポイントは、インスタンスのBraze URLに依存する。 |
+| 外部サブスクライバー ID | これは、Rokt Calendar サブスクリプションプロセスがカレンダーサブスクライバーと Braze ユーザーを照合するために使用する ID です。これを Rokt Calendar に渡します。|
 {: .reset-td-br-1 .reset-td-br-2}
 
-## オーディエンス・セグメンテーション {#audience-segmentation}
+## オーディエンスセグメンテーション {#audience-segmentation}
 
-Rokt Calendarが新規ユーザーを作成するとき、または既存の購読者とBrazeユーザーをマッチさせるとき、Rokt Calendarは、Braze内でフィルタリングできる以下のカスタム購読属性を送信する：
+Rokt Calendar での新規ユーザーの作成時、またはサブスクライバーと Braze ユーザーの照合時に、Rokt Calendar から、Braze 内でフィルタリングできる次のカスタムサブスクリプション属性が送信されます。
 
 | カスタム属性  | 定義       | 例          |
 | ----------------  | ---------------- | ---------------- |
-| `rokt:account_code` | 六連カレンダーのアカウントコード | `brazetest/f5733866ade2` そして `brazetest/ff10919f1078` |
-| `rokt:account_id` |六連カレンダーのアカウントID | `d0ce4299-7d6c-4888-bfd8-c7e867a0fa6c/f5733866ade2` |
-| `rokt:account_name` | ロクト・カレンダーのアカウント名 | `Braze Test/f5733866ade2` |
-| `rokt:calendar_code` | ロクト・カレンダー・カレンダーのコード | `test-calendar-1/f5733866ade2` |
-| `rokt:calendar_id` | 六連カレンダーのカレンダーID | `9a9007c7-f5a4-e811-b13c-06424c4f2724/f5733866ade2` |
-| `rokt:calendar_title` | 六連カレンダーのカレンダータイトル | `Test Calendar 1/f5733866ade2` |
+| `rokt:account_code` | Rokt Calendar アカウントのコード | `brazetest/f5733866ade2` と `brazetest/ff10919f1078` |
+| `rokt:account_id` |Rokt Calendar アカウントの ID | `d0ce4299-7d6c-4888-bfd8-c7e867a0fa6c/f5733866ade2` |
+| `rokt:account_name` | Rokt Calendar アカウントの名前 | `Braze Test/f5733866ade2` |
+| `rokt:calendar_code` | Rokt Calendar カレンダーのコード | `test-calendar-1/f5733866ade2` |
+| `rokt:calendar_id` | Rokt Calendar カレンダーの ID | `9a9007c7-f5a4-e811-b13c-06424c4f2724/f5733866ade2` |
+| `rokt:calendar_title` | Rokt Calendar カレンダーのタイトル | `Test Calendar 1/f5733866ade2` |
 | `rokt:country_code` | 作成されたサブスクリプションに関連する国コード | `AU/f5733866ade2` |
 | `rokt:device_name` | 作成されたサブスクリプションに関連するデバイスタイプ | `Desktop/f5733866ade2` |
 | `rokt:geo_country` | 作成されたサブスクリプションに関連する原産国 | `Australia/f5733866ade2` |
 | `rokt:optIn1` | ユーザーが、作成されたサブスクリプションに関連する2つのオプトインのうち、最初のオプトインにオプトインした場合 | `True/f5733866ade2` |
-| `rokt:optIn2` | ユーザーが、作成された購読に関連する2つのオプトインのうち2つ目にオプトインした場合 | `True/f5733866ade2` |
+| `rokt:optIn2` | ユーザーが、作成されたサブスクリプションに関連する2つのオプトインのうち2番目にオプトインした場合 | `True/f5733866ade2` |
 | `rokt:source` | 作成されたサブスクリプションのソース | `brazetest.Rokt Calendarapp.com/f5733866ade2` |
-| `rokt:subscriber_email` | 購読手続き中にユーザーが入力したEメールアドレス | `test@email.com/f5733866ade2` |
+| `rokt:subscriber_email` | サブスクリプションプロセス中にユーザーが入力したメールアドレス | `test@email.com/f5733866ade2` |
 | `rokt:subscription_id` | 作成されたサブスクリプションに関連する、一意な識別子としてのサブスクリプションID。 | `06423672-b6ba-4536-aa36-70788a7a0a36` |
 | `rokt:subscription_method` | 作成されたサブスクリプションに関連するサブスクリプションメソッド（webcal/Google）。 | `WebCal/f5733866ade2` |
 | `rokt:tags` | 作成された購読に関連して使用されたカレンダータグ。 | `Test Calendar 1/All Teams/f5733866ade2 and Test Calendar 1/TeamI//f5733866ade2` |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-Roktカレンダーはまた、ユーザーがRoktカレンダーに登録するとすぐに、`subscribe` カスタムイベントをトリガーする。
+また、Rokt Calendar は、ユーザーが Rokt Calendar をサブスクライブするとすぐに `subscribe` カスタムイベントをトリガーします。このカレンダーは、Braze セグメンテーションで使用することも、キャンペーンまたはキャンバスコンポーネントのトリガーとして使用することもできます。
 
 ## 統合
 
-### ステップ1:カレンダー購読者のオーディエンスを構築する
+### ステップ1:カレンダーサブスクライバーのオーディエンスを作成する
 
-Canvasからカレンダー・イベントを送信するには、まずRoktカレンダーを設定し、ユーザーを登録する必要がある。そのためには、カレンダーを購読する場所と方法をユーザーに知らせる必要がある。ロクト・カレンダーでは、以下のことを推奨している：
+キャンバスからカレンダーイベントを送信するには、まずすでにサブスクライブしているユーザーを使用して Rokt Calendar を設定する必要があります。そのためには、カレンダーをサブスクライブする場所と方法をユーザーに通知します。Rokt Calendar では以下のことが推奨されています。
 
 #### サブスクリプションの統合ポイントを提供する
-カレンダー購読者のオーディエンスを作るには、ユーザーが移動して購読できる先を提供する必要がある。サブスクリプション統合ポイントの例としては、以下のようなものがある：
+カレンダーサブスクライバーのオーディエンスを作成するには、ユーザーが移動してサブスクライブできる場所を提供する必要があります。サブスクリプション統合ポイントの例としては、以下のようなものがある：
   - ウェブサイトにカレンダーボタンを追加する
   - メールやSMSにカレンダーリンクを追加する 
   - カレンダーボタンをアプリに追加する
   - ソーシャルメディアにカレンダーのリンクを追加する
 
 #### カレンダーを宣伝する
-購読者のオーディエンスを作るには、購読方法を知ってもらうために、オーディエンスにカレンダーを宣伝する必要がある。カレンダープロモーションの例としては、以下のようなものがある：
+サブスクライバーからなるオーディエンスを作成するには、サブスクライブ方法がわかるように、オーディエンスにカレンダーをプロモーションする必要があります。カレンダープロモーションの例としては、以下のようなものがある：
   - ソーシャルメディアへの投稿
   - Eメールニュースレターと最新情報
   - ブログ記事
@@ -74,10 +74,10 @@ Canvasからカレンダー・イベントを送信するには、まずRoktカ
 
 ### ステップ2:BrazeでRokt CalendarのWebhookを作成する
 
-Brazeでは、WebhookキャンペーンやCanvas内のWebhookを設定することができる：
+Braze では、次のいずれかを行うために Webhook キャンペーンまたはキャンバス内の Webhook を設定できます。
 
-- 新しいパーソナライズされたイベントを送信する：購読者のカレンダーのセグメントに新しいイベントを追加できるようにする。
-- パーソナライズされたイベントを更新する：購読者のカレンダーにある既存のイベントを更新できるようにする。
+- 新しいパーソナライズされたイベントを送信する：サブスクライバーのカレンダーのセグメントに新しいイベントを追加できるようにします。
+- パーソナライズされたイベントを更新する：サブスクライバーのカレンダーにある既存のイベントを更新できるようにします。
 
 今後のキャンペーンやCanvasで使用するRokt Calendarウェブフックテンプレートを作成するには、Brazeプラットフォームの**「テンプレート**」>「**ウェブフックテンプレート**」に移動する。 
 
@@ -90,24 +90,24 @@ Brazeでは、WebhookキャンペーンやCanvas内のWebhookを設定するこ
 {% tabs %}
 {% tab 新しいイベントを送信する %}
 Rokt Calendarウェブフック・テンプレートを選択すると、以下のように表示される：
-- **ウェブフックのURL**： {% raw %}`{% assign accountCode = {{custom_attribute.${rokt:account_code}}}[0] | split: '/' | first %}https://api.roktcalendar.com/v1/subscriptionevent/{{accountCode}}`{% endraw %}
-- **リクエスト・ボディ**Raw Text
+- **Webhook URL**: {% raw %}`{% assign accountCode = {{custom_attribute.${rokt:account_code}}}[0] | split: '/' | first %}https://api.roktcalendar.com/v1/subscriptionevent/{{accountCode}}`{% endraw %}
+- **リクエスト本文**:Raw Text
 {% endtab %}
 {% tab 既存のイベントを更新する %}
 Rokt Calendarウェブフック・テンプレートを選択すると、以下のように表示される：
-- **ウェブフックのURL**： {% raw %}`{% assign accountCode = {{custom_attribute.${rokt:account_code}}}[0] | split: '/' | first %}https://api.roktcalendar.com/v1/subscriptionevent/{{accountCode}}/update`{% endraw %}
-- **リクエスト・ボディ**Raw Text
+- **Webhook URL**: {% raw %}`{% assign accountCode = {{custom_attribute.${rokt:account_code}}}[0] | split: '/' | first %}https://api.roktcalendar.com/v1/subscriptionevent/{{accountCode}}/update`{% endraw %}
+- **リクエスト本文**:Raw Text
 {% endtab %}
 {% endtabs %}
 
 #### リクエストヘッダと方法
 
-Rokt Calendarは、認証のために、Rokt Calendar Connected Contentクレデンシャル名を含む`HTTP Header` 。以下はすでにキーと値のペアとしてテンプレート内に含まれているが、**「設定」**タブでは、`<Rokt-Calendar-API>` を`Manage Settings > Connected Content > Credential` にあるクレデンシャル名に置き換える必要がある。
+Rokt Calendar では、認証のために Rokt Calendar コネクテッドコンテンツの認証情報名を含む `HTTP Header` が必要です。以下はすでにキーと値のペアとしてテンプレート内に含まれているが、**「設定」**タブでは、`<Rokt-Calendar-API>` を`Manage Settings > Connected Content > Credential` にあるクレデンシャル名に置き換える必要がある。
 
 {% raw %}
 - **HTTPメソッド**：POST
-- **ヘッダーをリクエストする**：
-  - **認可する**：ベアラー `{% connected_content https://api.roktcalendar.com/oauth2/token :method post :basic_auth <Rokt-Calendar-API> :body grant_type=client_credentials :save token :retry %}{{token.access_token}}`
+- **リクエストヘッダー**:
+  - **Authorization**:ベアラー `{% connected_content https://api.roktcalendar.com/oauth2/token :method post :basic_auth <Rokt-Calendar-API> :body grant_type=client_credentials :save token :retry %}{{token.access_token}}`
   - **Content-Type**: application/json
 {% endraw %}
 
@@ -169,19 +169,19 @@ Rokt Calendarは、認証のために、Rokt Calendar Connected Contentクレデ
 ```
 {% endraw %}
 {% endtab %}
-{% tab イベント詳細 %}
+{% tab イベントの詳細 %}
 以下のフィールドには、イベント・レベルでカスタマイズできる情報が含まれている。
 
 | フィールド             | 定義       | 例          |
 | ----------------  | ---------------- | ---------------- |
 | `eventId`<br>**\*必須** | 追加または更新されるイベントの一意な識別子。 | `Event_00001`
-| `eventTitle`<br>**\*必須** | カレンダーに表示されるイベントのタイトル | サマーセール2019
+| `eventTitle`<br>**\*必須** | カレンダーに表示されるイベントのタイトル | Summer Sale 2019
 | `eventDescr` | カレンダーに表示されるイベントの説明文 | セール期間は3日間で、このリンク（`www.mybusiness.com/sale` ）をクリックするとオファーが表示される。 |
 | `eventLocation` | カレンダーに表示されるイベントの場所。これはしばしば、eventTitleを補完する2番目の行動喚起として使用されることに注意。 | 50％オフのイベントを開く |
 | `eventStart`<br>**\*必須**  | カレンダーに表示されるイベントの開始日時 | `2019-02-21T15:00:00` |
 | `eventEnd`<br>**\*必須**  | カレンダーに表示されるイベントの開始日時 | `2019-02-21T16:00:00` |
-| `eventTz`<br>**\*必須**  | カレンダーに表示されるイベントのタイムゾーンを指定する。 | `Eastern Standard Time` |
-| `notifyBefore`<br>**\*必須**  | カレンダーに表示されるイベントのリマインダー時間。 | `15` |
+| `eventTz`<br>**\*必須**  | カレンダーに表示されるイベントのタイムゾーン。適用可能なタイムゾーンのリストは[こちら](https://roktcalendar-api.readme.io/docs/timezones)で確認できます。 | `Eastern Standard Time` |
+| `notifyBefore`<br>**\*必須**  | カレンダーに表示されるイベントのリマインダー時刻。これは分単位で表されます。 | `15` |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 {% endtab %}
 {% endtabs %}
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/inkit.md b/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/inkit.md
index 403874a7197..f42c99558bd 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/inkit.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/inkit.md
@@ -10,25 +10,25 @@ search_tag: Partner
 
 # Inkit
 
-> [Inkitと][1]Brazeは、デジタルでもダイレクトメールでも、企業が安全に文書を作成・配布できるようにする。
+> [Inkit][1] と Braze により、デジタルでもダイレクトメールでも、企業が安全に文書を作成して配布することができます。
 
-BrazeとInkitの統合により、BrazeのWebhookを使って文書を生成し、Brazeユーザーに直接郵送することができる。
+Braze と Inkit の統合により、文書を生成し、Braze Webhook を使用して Braze ユーザーに直接メールで送信できます。
 
 ## 前提条件
 
 |必要条件| 説明|
 | ---| ---|
-|Inkitアカウント | このパートナーシップを利用するには、[Inkitアカウントが](https://www.inkit.com/)必要である。 |
-| InkitのAPIキー<br><br>`<INKIT_API_TOKEN>` | このキーは、[Inkitダッシュボードの](https://app.inkit.io/#/account/integrations) **開発**タブにあり、BrazeとInkitのアカウントを接続することができる。|
-| InkitテンプレートID<br><br>`<INKIT_TEMPLATE_ID>` | テンプレートを作成した後、**テンプレート**タブからテンプレートIDをコピーしてBrazeのテンプレートで使用することができる。<br><br>例えば、Inkit環境にテンプレートID:`tmpl_3bDScFl9cwr3OAVR1RSdEC` で`invoice_template` というテンプレートを作成する。
-| HTTPヘッダー | HTTPヘッダーは、BrazeからInkitに送信するAPIリクエストの一部である。その中に、Inkit APIへの呼び出しを認証および承認するためのInkit APIキーを含める。 |
+|Inkitアカウント | このパートナーシップを活用するには、[Inkit アカウント](https://www.inkit.com/)が必要です。 |
+| Inkit API キー<br><br>`<INKIT_API_TOKEN>` | このキーは [Inkit Dashboard](https://app.inkit.io/#/account/integrations) の \[**Development**] タブにあります。このキーにより Braze アカウントと Inkit アカウントを接続できるようになります。|
+| Inkitテンプレート ID<br><br>`<INKIT_TEMPLATE_ID>` | テンプレートを作成した後、**テンプレート**タブからテンプレートIDをコピーしてBrazeのテンプレートで使用することができる。<br><br>たとえば、Inkit 環境にテンプレート ID: `tmpl_3bDScFl9cwr3OAVR1RSdEC` で `invoice_template` というテンプレートを作成できます。
+| HTTPヘッダー | HTTPヘッダーは、BrazeからInkitに送信するAPIリクエストの一部である。この中には、Inkit API の呼び出しを認証および許可するための Inkit API キーが含まれます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 統合
 
-### ステップ1:Inkitテンプレートを作成する
+### ステップ1:Inkit テンプレートを作成する
 
-Inkitプラットフォーム上で、Brazeキャンペーンで使用するテンプレートをHTML、Word、PowerPoint、ExcelまたはPDFで作成する。詳しくは[Inkitのドキュメントを](https://docs.inkit.com/docs/create-a-template)参照されたい。
+Inkitプラットフォーム上で、Brazeキャンペーンで使用するテンプレートをHTML、Word、PowerPoint、ExcelまたはPDFで作成する。詳細については、[Inkit のドキュメント](https://docs.inkit.com/docs/create-a-template)を参照してください。
 
 ### ステップ2:BrazeのWebhookテンプレートを作成する
 
@@ -40,30 +40,30 @@ Inkitプラットフォーム上で、Brazeキャンペーンで使用するテ
 
 単発のInkitウェブフックキャンペーンを作成したい場合、または既存のテンプレートを使用したい場合は、新しいキャンペーンを作成する際にBrazeの**ウェブフックを**選択する。
 
-![Templates & MediaセクションのWebhook Templatesタブにある、利用可能なデザイン済みWebhookテンプレートのセレクション。][7]
+![「Templates & Media」セクションの「Webhook Templates」タブにある、一連の利用可能な事前設計済み Webhook テンプレート。][7]
 
 Inkitウェブフック・テンプレートを選択すると、以下のように表示される：
-- **ウェブフックのURL**：空白
-- **リクエスト・ボディ**Raw Text
+- **Webhook URL**:空白
+- **リクエスト本文**:Raw Text
 
-Webhook URLフィールドで、InkitのWebhook URLを[作成](https://docs.inkit.com/docs/set-up-a-webhook-to-an-event)し、入力する必要がある。
+\[Webhook URL] フィールドで、Inkit Webhook URL を[作成](https://docs.inkit.com/docs/set-up-a-webhook-to-an-event)して入力する必要があります。
 
-![Braze webhook builderのcomposeタブに表示されるリクエストボディコードとwebhook URL。][5]
+![Braze Webhook ビルダー作成タブに表示されているリクエスト本文のコードと Webhook URL。][5]
 
 #### リクエストヘッダと方法
 
-Inkitは、認証のために、Base 64でエンコードされたInkit APIキーを含む、`HTTP Header` 。以下はすでにキーと値のペアとしてテンプレート内に含まれているが、**「設定」**タブでは、`<INKIT_API_TOKEN>` をあなたのInkit APIキーに置き換える必要がある。
+Inkit の認証には、Base64 でエンコードされた Inkit API キーを含む `HTTP Header` が必要です。以下の内容はすでにキーと値のペアとしてテンプレートに含まれていますが、\[**設定**] タブで `<INKIT_API_TOKEN>` を Inkit API キーに置き換える必要があります。
 
 {% raw %}
 - **HTTPメソッド**：POST
-- **ヘッダーをリクエストする**：
-  - **認可する**：ベーシック `{{ '<INKIT_API_TOKEN>' | base64_encode }}`
+- **リクエストヘッダー**:
+  - **Authorization**:Basic `{{ '<INKIT_API_TOKEN>' | base64_encode }}`
   - **Content-Type**: application/json
 {% endraw %}
 
 #### Request body
 
-リキッドが以下の必須フィールドとオプションフィールドに関連する適切なカスタム属性と一致していることを確認する。また、どのリクエストにもカスタムデータフィールドを追加することができる。
+Liquid が、以下の必須フィールドとオプションフィールドに関連付けられている適切なカスタム属性を照合することを確認します。また、どのリクエストにもカスタムデータフィールドを追加できます。
 
 ```json
 {% raw %}{
@@ -86,7 +86,7 @@ Inkitは、認証のために、Base 64でエンコードされたInkit APIキ
 
 ### ステップ3:リクエストをプレビューする
 
-Brazeタグに該当するテキストは自動的にハイライトされる。`street`このWebhookを送信するには、`unit` 、`state` 、`zip` を[カスタム属性として][3]設定する必要がある。
+生のテキストが適切な Braze タグである場合、このテキストが自動的に強調表示されます。この Webhook を送信するには、`street`、`unit`、`state`、`zip` が[カスタム属性][3]として設定されている必要があります。
 
 **Preview**パネルでリクエストをプレビューするか、**Test**タブに移動して、ランダムなユーザー、既存のユーザーを選択するか、ウェブフックをテストするために自分でカスタマイズする。
 
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/lob.md b/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/lob.md
index 5e1dfbf14a6..db107e5d542 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/lob.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/lob.md
@@ -1,6 +1,6 @@
 ---
-nav_title: ロブ
-article_title: ロブ 
+nav_title: Lob
+article_title: Lob 
 alias: /partners/lob/
 description: "この参考記事では、BrazeとLob.comの提携について概説している。Lob.comを利用すれば、手紙やはがき、小切手などのダイレクトメールを郵送することができる。"
 page_type: partner
@@ -8,29 +8,29 @@ search_tag: Partner
 
 ---
 
-# ロブ
+# Lob
 
 > \[Lob.com][38] は、ユーザーにダイレクトメールを送ることができるオンラインサービスである。
 
-BrazeとLobの統合は、BrazeのウェブフックとLobのAPIを活用して、手紙、はがき、小切手などのメールをメールで送信する。  
+Braze と Lob の統合では、Braze Webhook と Lob API を使用して、手紙、ポストカード、小切手などを郵送します。  
 
 ## 前提条件
 
 |必要条件| 説明|
 | ---| ---|
-|ロブアカウント | このパートナーシップを利用するには、ロブ・アカウントが必要である。 |
-| ロブAPIキー | LobのAPIキーは、Lobダッシュボードのあなたの名前の下の設定セクションにある。 |
+|Lob アカウント | このパートナーシップを活用するには、Lob アカウントが必要です。 |
+| Lob API キー | Lob API キーは、Lob ダッシュボードのお客様の名前の下にある設定セクションで確認できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
 ### ステップ1:Lobエンドポイントを選択する
 
-WebhookでリクエストするHTTP URLは、Lobにできるアクションごとに異なる。以下の例では、postcards APIエンドポイント`https://api.lob.com/v1/postcards` を使っている。完全なエンドポイントリスト][39] ] にアクセスして、ユースケースに適したエンドポイントを選択する。 
+Webhook で要求する HTTP URL は、Lob に対して実行できるアクションごとに異なります。以下の例では、postcards APIエンドポイント`https://api.lob.com/v1/postcards` を使っている。\[すべてのエンドポイントのリスト][39]にアクセスして、ユースケースに適したエンドポイントを選択します。 
 
 | APIエンドポイント | 利用可能なエンドポイント |
 | ------------ | ------------------- |
-| https://api.lob.com/ | /v1/アドレス<br>/v1/addresses/{id}<br>/v1/ベリファイ<br>/v1/ポストカード<br>/v1/postcards/{id}<br>/v1/文字<br>/v1/letter/{id}<br>/v1/チェック<br>/v1/checks/{id}である。<br>/v1/bank_accounts<br>/v1/bank_accounts/{id}<br>/v1/bank_accounts/{id}/verify<br>/v1/エリア<br>/v1/areas/{id}である。<br>/v1/ルート/{zip_code}。<br>/v1/ルート<br>/v1/国<br>/v1/ステート|
+| https://api.lob.com/ | /v1/addresses<br>/v1/addresses/{id}<br>/v1/verify<br>/v1/postcards<br>/v1/postcards/{id}<br>/v1/letter<br>/v1/letter/{id}<br>/v1/checks<br>/v1/checks/{id}<br>/v1/bank_accounts<br>/v1/bank_accounts/{id}<br>/v1/bank_accounts/{id}/verify<br>/v1/areas<br>/v1/areas/{id}<br>/v1/routes/{zip_code}<br>/v1/routes<br>/v1/countries<br>/v1/states|
 {: .reset-td-br-1 .reset-td-br-2}
 
 ### ステップ2:BrazeのWebhookテンプレートを作成する
@@ -44,23 +44,23 @@ WebhookでリクエストするHTTP URLは、Lobにできるアクションご
 単発のLob Webhookキャンペーンを作成したい場合、または既存のテンプレートを使用したい場合は、新しいキャンペーンを作成する際にBrazeで**Webhookを**選択する。
 
 新しいWebhookテンプレートで、以下のフィールドに記入する：
-- **ウェブフックのURL**： `<LOB_API_ENDPOINT>`
-- **リクエスト・ボディ**Raw Text
+- **Webhook URL**: `<LOB_API_ENDPOINT>`
+- **リクエスト本文**:Raw Text
 
 #### リクエストヘッダと方法
 
-Lobは認可のためのHTTPヘッダーとHTTPメソッドを必要とする。以下はすでにキーと値のペアとしてテンプレート内に含まれているが、**Settings**タブでは、`<LOB_API_KEY>` をあなたのLob APIキーに置き換える必要がある。このキーは、キーの直後に": "を含み、64進数でエンコードされていなければならない。 
+Lob には、認証用の HTTP ヘッダーと HTTP メソッドが必要です。以下の内容はすでにキーと値のペアとしてテンプレートに含まれていますが、\[**設定**] タブで `<LOB_API_KEY>` をご使用の Lob API キーに置き換える必要があります。このキーの直後に「:」が付加されており、またこのキーは64進数でエンコードされている必要があります。 
 
 - **HTTPメソッド**：POST
-- **ヘッダーを要求する**：
-  - **認可する**：ベーシック `{{'<LOB_API_KEY>:' | base64_encode}}`
+- **リクエストヘッダー**:
+  - **Authorization**:Basic `{{'<LOB_API_KEY>:' | base64_encode}}`
   - **Content-Type**: application/json
 
-![Braze webhook builderのcomposeタブに表示されるリクエストボディコードとwebhook URL。][35]
+![Braze Webhook ビルダー作成タブに表示されているリクエスト本文のコードと Webhook URL。][35]
 
 #### Request body
 
-以下は、Lob postcardsエンドポイントのリクエストボディの例である。このリクエストボディは、Brazeの基本Lobテンプレートで提供されているが、他のエンドポイントを使用したい場合は、それに応じてLiquidフィールドを調整する必要がある。
+Lob ポストカードエンドポイントのリクエスト本文の例を次に示します。このリクエスト本文は Braze の 基本 Lobテンプレートで提供されますが、他のエンドポイントを使用する場合は、それに応じて Liquid フィールドを調整する必要があります。
 
 ```json
 {% raw %}"description": "Demo Postcard",
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/optilyz.md b/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/optilyz.md
index 83d5336bf73..7e726538003 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/optilyz.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/direct_mail/optilyz.md
@@ -10,7 +10,7 @@ search_tag: Partner
 
 # optilyz
 
-> [optilyzは][1]、より顧客中心の、持続可能で収益性の高いダイレクトメールキャンペーンの実施を可能にするダイレクトメール自動化プラットフォームである。 
+> [optilyz][1] はダイレクトメールオートメーションプラットフォームです。顧客中心型で持続可能かつ収益性の高いダイレクトメールキャンペーンを実施できます。 
 
 optilyzとBrazeのウェブフック統合を使用して、手紙、はがき、セルフメーラーなどのダイレクトメールを顧客に送信する。
 
@@ -18,21 +18,21 @@ optilyzとBrazeのウェブフック統合を使用して、手紙、はがき
 
 | 必要条件 | 説明 |
 |---|---|
-|optilyzアカウント | このパートナーシップを利用するには、optilyzアカウントが必要である。 |
-| optilyz APIキー<br><br>`<OPTILYZ_API_KEY>`| optilyzカスタマーサクセスマネージャーがoptilyz APIキーを提供する。<br><br>このAPIキーでBrazeとoptilyzのアカウントを接続できる。 |
-| optilyzオートメーションID<br><br>`<OPTILYZ_AUTOMATION_ID>` | オートメーションIDは、ページヘッダーのボックスに記載されている。<br><br>optilyzにログインすると、データを送信したいオートメーションに移動することができる。<br>まずオートメーションを作動させなければならない。 |
+|optilyzアカウント | このパートナーシップを活用するには、optilyz アカウントが必要です。 |
+| optilyz APIキー<br><br>`<OPTILYZ_API_KEY>`| optilyz API キーは optilyz カスタマーサクセスマネージャーから提供されます。<br><br>このAPIキーでBrazeとoptilyzのアカウントを接続できる。 |
+| optilyzオートメーションID<br><br>`<OPTILYZ_AUTOMATION_ID>` | オートメーションIDは、ページヘッダーのボックスに記載されている。<br><br>optilyz にログインしたら、データの送信先のオートメーションに移動できます。<br>最初にオートメーションをアクティブにする必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## ユースケース
 
-ダイレクトメールをデジタル・チャネルのように運用することは、大量発送から脱却し、カスタマージャーニーの一部として活用することを意味する。ダイレクトメールの現代的なアプローチの利点は以下の通りである：
+ダイレクトメールをデジタルチャネルのように運用することは、大量の郵送から脱却し、チャネルを (デジタル) カスタマージャーニーの一部として活用することを意味します。最新のダイレクトメールアプローチの利点は、次のとおりです。
 - 関連性の向上、ユースケースの追加、A/Bテストの容易化、クロスチャネル効果によるコンバージョン率の向上
 - 自動化とエンド・ツー・エンド・ソリューションによる労力の削減
 - フレーム契約とコストの透明性によるコスト削減
 
 ## 統合
 
-optilyzと統合するには、[optilyz APIを][2]使用して受信者データをBrazeのウェブフックに送信する。
+optilyz と統合するには、[optilyz API][2] を使用して受信者データを Braze Webhook に送信します。
 
 ### ステップ1:BrazeのWebhookテンプレートを作成する
 
@@ -42,28 +42,28 @@ optilyzと統合するには、[optilyz APIを][2]使用して受信者データ
 [古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**Engagement（エンゲージメント）**」＞「**Templates & Media（テンプレート＆メディア**）」＞「**Webhook Templates（ウェブフック・テンプレート**）」と進む。
 {% endalert %}
 
-単発のoptilyzウェブフックキャンペーンを作成したい場合、または既存のテンプレートを使用したい場合は、新しいキャンペーンを作成する際にBrazeで**ウェブフックを**選択する。
+1回限りの optilyz Webhook キャンペーンを作成するか、既存のテンプレートを使用する場合は、新しいキャンペーンを作成する際に Braze で **Webhook** を選択します。
 
 新しいWebhookテンプレートで、以下のフィールドに記入する：
-- **ウェブフックのURL**：WebhookのURLは顧客ごとに異なり、オプティリズのカスタマーサクセスマネージャーが提供する。
-- **リクエスト・ボディ**Raw Text
+- **Webhook URL**:Webhook URL はお客様ごとに異なり、optilyz のカスタマーサクセスマネージャーから提供されます。
+- **リクエスト本文**:Raw Text
 
 #### リクエストヘッダと方法
 
-optilyzはまた、認可のためのHTTPヘッダーとHTTPメソッドを必要とする。以下はすでにキーと値のペアとしてテンプレート内に含まれているが、**設定**タブでは、`<OPTILYZ_API_KEY>` をあなたの optilyz API キーに置き換える必要がある。このキーは、キーの直後に": "を含み、64進数でエンコードされていなければならない。 
+optilyz には、認証用の HTTP ヘッダーと HTTP メソッドが必要です。以下の内容はすでにキーと値のペアとしてテンプレートに含まれていますが、\[**設定**] タブで `<OPTILYZ_API_KEY>` を optilyz API キーに置き換える必要があります。このキーの直後に「:」が付加されており、またこのキーは64進数でエンコードされている必要があります。 
 
 - **HTTPメソッド**：POST
-- **ヘッダーを要求する**：
-  - **認可する**： {% raw %} `{{ '<OPTILYZ_API_KEY>:' | base64_encode }}` {% endraw %}
+- **リクエストヘッダー**:
+  - **Authorization**: {% raw %} `{{ '<OPTILYZ_API_KEY>:' | base64_encode }}` {% endraw %}
   - **Content-Type**: application/json
 
 ![Braze webhookビルダーに表示されるリクエストヘッダーとHTTPメソッド。][6]{: style="max-width:50%"}
 
 #### Request body
 
-以下のリクエストボディでは、任意のLiquidパーソナライゼーションタグを使用し、optilyzの[APIドキュメントに従って][2]カスタムリクエストテンプレートを構築することができる。
+次のリクエスト本文では、任意の Liquid パーソナライゼーションタグを使用して、optilyz の [API ドキュメント][2]に従ってカスタムリクエストテンプレートを作成できます。
 
-`variation` フィールドはオプションで、オートメーション内部のどのデザインを使用するかを定義することができる。バリエーションが省略された場合、optilyzは定義されたバリエーションの1つをランダムに割り当てる。
+`variation` フィールドはオプションであり、オートメーション内部のどのデザインを使用するかを定義できます。バリエーションが省略された場合、optilyzは定義されたバリエーションの1つをランダムに割り当てる。
 
 {% raw %}
 ```json
@@ -84,7 +84,7 @@ optilyzはまた、認可のためのHTTPヘッダーとHTTPメソッドを必
 ```
 {% endraw %}
 
-![Braze webhook builderのcomposeタブに表示されるリクエストボディコードとwebhook URLのイメージ。][5]
+![Braze Webhook ビルダー作成タブに表示さているリクエスト本文のコードと Webhook URL の画像。][5]
 
 ### ステップ2:リクエストをプレビューする
 
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat.md b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat.md
index 366dc3f636c..3eb33cf88c4 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat.md
@@ -14,11 +14,11 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Instant Chat"
 
 valid_partner_list:
-- name: メッセンジャー
+- name: Messenger
   url: /docs/partners/message_orchestration/additional_channels/instant_chat/messenger/
 - name: LINE
   url: /docs/partners/message_orchestration/additional_channels/messaging/line/  
-- name: センドバード
+- name: Sendbird
   url: /docs/partners/message_orchestration/additional_channels/messaging/sendbird/  
 - name: Regal
   url: /docs/partners/message_orchestration/additional_channels/messaging/regal/  
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/front.md b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/front.md
index 6ef9c9f83a5..369b23fb126 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/front.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/front.md
@@ -1,6 +1,6 @@
 ---
-nav_title: フロント
-article_title: フロント
+nav_title: Front
+article_title: Front
 description: "BrazeとFrontを統合する方法を学びます"
 alias: /partners/front/
 page_type: partner
@@ -8,13 +8,13 @@ search_tag: Partner
 
 ---
 
-# フロント
+# Front
 
-> Frontの統合により、各プラットフォームからBrazeデータ変換およびwebhookを活用して、双方向の会話型SMSパイプラインを設定できます。
+> Front の統合により、各プラットフォームから Braze Data Transformation および Webhook を活用して双方向の会話型 SMS パイプラインを設定できます。
 
-Frontからの受信Webhookには、ライブエージェントが送信したメッセージを含むペイロードが含まれます。リクエストは、Brazeのエンドポイントで受け入れられる前に再フォーマットする必要があります。フロントデータ変換テンプレートはペイロードを再フォーマットし、**送信SMS送信,**というタイトルのユーザープロファイルにカスタムイベントを書き込み、メッセージ本文をイベントプロパティとして渡します。
+Front からの受信 Webhook には、ライブエージェントが送信したメッセージを含むペイロードが含まれています。リクエストは、Braze のエンドポイントで受け入れられる前に再フォーマットする必要があります。Front Data Transformation テンプレートによりペイロードが再フォーマットされ、カスタムイベントが、イベントプロパティとして渡されるメッセージ本文とともに **Outbound SMS Sent** というタイトルのユーザープロファイルに書き込まれます。
 
-新しい変換をBrazeで設定する前に、[データ変換]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/overview/)ドキュメントの各層のサポートマトリックスを確認することをお勧めします。私たちの無料およびプロのティアは、月ごとのアクティブな変換と受信リクエストの数が異なります。現在のプランがあなたのユースケースをサポートできるか確認してください。
+Braze で新し変換を設定する前に、[データ変換]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/overview/)ドキュメントの各ティアのサポートマトリックスを確認することをお勧めします。私たちの無料およびプロのティアは、月ごとのアクティブな変換と受信リクエストの数が異なります。現在のプランがあなたのユースケースをサポートできるか確認してください。
 
 ## 前提条件
 
@@ -22,16 +22,16 @@ Frontからの受信Webhookには、ライブエージェントが送信した
 
 | 前提条件             | 説明                                                               |
 |---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|
-| フロントアカウント            | このパートナーシップを利用するには、フロントアカウントが必要です。|
-| Braze データ変換 Webhook URL | [Brazeデータ変換]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/overview/)は、Frontからの受信Webhookを再フォーマットして、Brazeの/users/trackエンドポイントで受け入れられるようにします。|
-| フロントREST APIキー         | FrontのREST APIキーを使用して、BrazeからFrontへのアウトバウンドWebhookリクエストを行います。 |
+| Front アカウント            | このパートナーシップを利用するには、フロントアカウントが必要です。|
+| Braze Data Transformation Webhook URL | [Braze Data Transformation]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/overview/) は、Frontからの受信 Webhook を再フォーマットして、Brazeの /users/track エンドポイントで受け入れられるようにします。|
+| フロントREST APIキー         | Front REST API キーを使用して、Braze から Front へのアウトバウンド Webhook リクエストを行います。 |
 
 ## ユースケース
 
 - Brazeの自動SMSメッセージングを使用してリード生成プロセスを合理化し、ユーザーの好みを特定し、ライブ販売エージェントがフォローアップして販売を完了できるようにします。
-- 放棄されたショッピングカートを持つ顧客を再エンゲージし、自動化されたSMS応答とライブチャットサポートを通じて販売コンバージョンを促進します。
+- 自動 SMS 応答とライブチャットサポートによりセールスコンバージョンを促進することで、ショッピングカートを放棄した顧客を再獲得します。
 
-## フロントの統合
+## Front の統合
 
 ### ステップ1:データ変換を作成する
 
@@ -39,7 +39,7 @@ Frontからの受信Webhookには、ライブエージェントが送信した
 
 1. Braze で、**データ設定** > **データ変換** に移動し、**変換の作成** を選択します。
 2. 「**編集体験**」で「**最初からやり直す**」を選択します。
-3. **送信先**で、**POSTを選択します。ユーザー**を追跡します。
+3. **送信先**で、**POSTを選択します。ユーザー ** を追跡します。
 4. 次の変換テンプレートをコピーして貼り付け、次にエンドポイントを保存してアクティブ化します。
     {% raw %}
     ```liquid
@@ -72,7 +72,7 @@ Frontからの受信Webhookには、ライブエージェントが送信した
     ```
     {% endraw %}
 
-    あなたの変換は次のようにする必要があります:
+    変換は次のようになります。
 
     ![データ変換の例。]({% image_buster /assets/img/front/data_transformation.png %})
 
@@ -82,7 +82,7 @@ Frontからの受信Webhookには、ライブエージェントが送信した
 
 ### ステップ2:アウトバウンドSMSキャンペーンを作成する
 
-次に、Frontからのwebhookをリッスンし、顧客へのカスタムSMS応答を行うSMSキャンペーンを作成します。
+次に、Front からの Webhook をリッスンする SMS キャンペーンと、顧客に対するカスタム SMS 応答を作成します。
 
 #### ステップ 2.1:メッセージを作成する
 
@@ -94,33 +94,33 @@ Frontからの受信Webhookには、ライブエージェントが送信した
 ```
 {% endraw %}
 
-あなたのメッセージは次のようになります:
+メッセージは次のようになります。
 
 ![Liquidコードを使用した例のメッセージです。]({% image_buster /assets/img/front/sms_to_braze.png %}){: style="max-width:80%;"}
 
-#### 2.2 スケジュール the delivery
+#### 2.2 配信をスケジュールする
 
 配信タイプには**アクションベースの配信**を選択し、カスタムイベントトリガーには**送信済みSMS**を選択します。
 
-![「スケジュール配信」ページです。]({% image_buster /assets/img/front/custom_event_trigger.png %})
+![\[Schedule Delivery] ページ。]({% image_buster /assets/img/front/custom_event_trigger.png %})
 
 {% alert note %}
 このカスタムイベントは、ユーザーのプロファイルに書き込むデータ変換です。エージェントメッセージはこのイベントのイベントプロパティとして保存されます。
 {% endalert %}
 
-最後に、**配信コントロール**で再適格性を有効にします。
+最後に、\[**配信コントロール**] で再適格性を有効にします。
 
-![「配信コントロール」で再適格性が有効になりました。]({% image_buster /assets/img/front/braze_reeligibility.png %})
+![\[配信コントロール] で有効になっている再適格性。]({% image_buster /assets/img/front/braze_reeligibility.png %})
 
 ### ステップ 3:カスタムチャネルを作成する
 
 Frontのダッシュボードで、**設定** > **チャネル** > **チャネルを追加** に移動し、**カスタムチャネル** を選択して、新しいBrazeチャネルの名前を入力します。
 
-![FrontダッシュボードのBraze用カスタムチャネル]({% image_buster /assets/img/front/front_custom_channel.png %})
+![Front ダッシュボードの Braze 用カスタムチャネル]({% image_buster /assets/img/front/front_custom_channel.png %})
 
 ### ステップ 4:設定を構成する
 
-アウトバウンドAPIエンドポイントフィールドに、以前に作成したデータ変換Webhook URL [を入力します](#step-1-set-up-a-data-transformation-in-braze)。すべてのライブエージェントからの新しいBrazeチャネルの送信メッセージはここに送信されます。このチャネルは、SMSメッセージを転送するためのエンドポイントURLも提供します。Brazeはこれを**受信URL**フィールドに転送します。
+アウトバウンド API エンドポイントフィールドに、[以前に作成した](#step-1-set-up-a-data-transformation-in-braze) Data Transformation Webhook URL を入力します。すべてのライブエージェントからの新しいBrazeチャネルの送信メッセージはここに送信されます。このチャネルは、SMSメッセージを転送するためのエンドポイントURLも提供します。Brazeはこれを**受信URL**フィールドに転送します。
 
 このURLをメモしておいてください。後で必要になります。
 
@@ -128,12 +128,12 @@ Frontのダッシュボードで、**設定** > **チャネル** > **チャネ
 
 ### ステップ 5: インバウンドSMS転送の設定
 
-次に、Brazeで2つの新しいWebhookキャンペーンを作成し、顧客からの受信SMSをFrontの受信トレイに転送できるようにします。
+次に、Brazeで2つの新しいWebhook キャンペーンを作成します。これにより、顧客からのインバウンド SMS を Front の受信トレイに転送できます。
 
 |数値|目的|
 |---|---|
-|Webhook キャンペーン 1|ライブチャットの会話が要求されていることをフロントに知らせます。|
-|Webhook キャンペーン 2|顧客から受信したすべての会話型SMS応答をFrontの受信トレイに転送します。|
+|Webhook キャンペーン 1|ライブチャットの会話が要求されていることを Front に通知します。|
+|Webhook キャンペーン 2|顧客からインバウンドで送信されたすべての会話型 SMS 応答を Front の受信トレイに転送します。|
 {: .reset-td-br-1 .reset-td-br-2 }
 
 #### ステップ 5.1:SMSキーワードカテゴリを作成する
@@ -144,7 +144,7 @@ Brazeのダッシュボードで、**オーディエンス**に移動し、**SMS
 |---|---|
 |キーワードカテゴリ|キーワードカテゴリの名前、例えば`FrontSMS1`。|
 |キーワード|あなたのカスタムキーワード、例えば`TIMETOMOW`。一般的な言葉を避けて、誤ってトリガーされないようにしてください。念頭に置いてください、キーワードは大文字と小文字を区別しないので、`lawn`は`LAWN`と一致します。|
-|返信メッセージ|キーワードが検出されたときに送信されるメッセージ。例えば、「造園業者がすぐに連絡します。」|
+|返信メッセージ|キーワードが検出されたときに送信されるメッセージ。たとえば「A landscaper will reach out to you shortly」などです。|
 {: .reset-td-br-1 .reset-td-br-2 }
 
 ![Brazeの例としてのSMSキーワードカテゴリ]({% image_buster /assets/img/front/front_keyword.png %}){: style="max-width:65%;"}
@@ -153,7 +153,7 @@ Brazeのダッシュボードで、**オーディエンス**に移動し、**SMS
 
 Brazeのダッシュボードで、以前に作成したURL[を使用して最初のWebhookキャンペーンを作成します](#step-3-configure-the-settings-for-your-new-custom-braze-channel)。
 
-![Brazeで作成する最初のWebhookキャンペーンの例です。]({% image_buster /assets/img/front/sms_to_front.png %}){: style="max-width:65%;"}
+![Braze で作成する最初の Webhook キャンペーンの例。]({% image_buster /assets/img/front/sms_to_front.png %}){: style="max-width:65%;"}
 
 次の内容をリクエストボディに追加してください:
 
@@ -182,19 +182,19 @@ Brazeのダッシュボードで、以前に作成したURL[を使用して最
 
 #### ステップ 5.3:最初の配達をスケジュールする
 
-**スケジュール配信**のために、**アクションベースの配信**を選択し、次にトリガータイプとして**SMS受信メッセージの送信**を選択します。また、以前に[設定した](#step-51-create-an-sms-keyword-category)SMSサブスクリプショングループとキーワードカテゴリを追加します。
+**スケジュール配信**のために、**アクションベースの配信**を選択し、次にトリガータイプとして**SMS受信メッセージの送信**を選択します。また、[以前に設定した](#step-51-create-an-sms-keyword-category) SMS サブスクリプショングループとキーワードカテゴリを追加します。
 
 ![最初のWebhookキャンペーンの「スケジュール配信」ページ。]({% image_buster /assets/img/front/front_actionbased_keyword.png %})
 
-**配信コントロール**で、再適格性を有効にします。
+\[**配信コントロール**] で再適格性を有効にします。
 
-![「配信コントロール」で再選択された最初のWebhookキャンペーンの再適格性。]({% image_buster /assets/img/front/braze_reeligibility.png %})
+![最初の Webhook キャンペーンの \[配信コントロール]で再適格性が選択されている。]({% image_buster /assets/img/front/braze_reeligibility.png %})
 
 #### ステップ 5.4:2番目のWebhookキャンペーンを作成する
 
-2番目のWebhookキャンペーンが最初のものと一致するため、[最初のものを複製して名前を変更することができます]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/duplicating_segments_and_campaigns/#duplicating-segments-or-campaigns)。今すぐに行うことができます。
+2番目のWebhookキャンペーンが最初のものと一致するため、[最初のものを複製して名前を変更することができます]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/duplicating_segments_and_campaigns/#duplicating-segments-or-campaigns)。これは今すぐ実行できます。
 
-#### ステップ 5.5:スケジュール第2回目の配達
+#### ステップ 5.5:2 回目の配信をスケジュールする
 
 **スケジュール配信**のために、**アクションベースのトリガー**と**SMSサブスクリプショングループ**を[最初の配信](#step-53-schedule-the-first-delivery)と同じに設定します。しかし、**キーワードカテゴリ**の場合は、**その他**を選択してください。
 
@@ -202,7 +202,7 @@ Brazeのダッシュボードで、以前に作成したURL[を使用して最
 
 #### ステップ 5.6:オーディエンスフィルターを追加
 
-あなたのWebhookキャンペーンは、顧客からの受信SMS応答を転送できるようになりました。ライブチャット用のメッセージのみが転送されるようにSMSの応答をフィルタリングするには、**特定のキャンペーンからの最後に受信したメッセージ**セグメンテーションフィルターを**ターゲットオーディエンスステップ**に追加します。
+これで、Webhook キャンペーンが顧客からのインバウンド SMS応答を転送できるようになりました。ライブチャット用のメッセージのみが転送されるようにSMSの応答をフィルタリングするには、**特定のキャンペーンからの最後に受信したメッセージ**セグメンテーションフィルターを**ターゲットオーディエンスステップ**に追加します。
 
 ![特定のキャンペーンから最後に受信したメッセージが選択されたオーディエンスフィルター。]({% image_buster /assets/img/front/front_segment_last_received_message.png %}){: style="max-width:65%;"}
 
@@ -210,7 +210,7 @@ Brazeのダッシュボードで、以前に作成したURL[を使用して最
 
 1. **キャンペーン**のために、以前作成したSMSキャンペーン[を選択します](#step-2-create-an-outbound-sms-campaign)。
 2. **オペレーター**の場合、**未満**を選択します。
-3. **時間枠**については、顧客からの応答がない場合にチャットが開封されたままになる時間の長さを選択してください。
+3. \[**時間枠**] については、顧客からの応答がない状態でチャットを開いたままにしておく期間を選択します。
 
 ![選択したオーディエンスフィルターの設定。]({% image_buster /assets/img/front/front_target_audience.png %})
 
@@ -218,12 +218,12 @@ Brazeのダッシュボードで、以前に作成したURL[を使用して最
 
 ### 課金セグメント
 
-- BrazeでのSMSメッセージはメッセージSegmentごとに課金されます。セグメントを定義するものと、これらのメッセージがどのように分割されるかを理解することは、メッセージの請求方法を理解する上で重要です。詳細については、当社の[ドキュメント]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/segments)をご覧ください。
-- エージェントの応答が長いと、請求可能なセグメントが増えます。
+- BrazeでのSMSメッセージはメッセージSegmentごとに課金されます。何がセグメントを定義し、どのようにメッセージが分割されるかを理解することは、メッセージの請求方法を理解するうえで重要です。詳細については、当社の[ドキュメント]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/segments)をご覧ください。
+- エージェントの応答が長いと、請求対象セグメントの消費が増加します。
 
-### データポイント消費
+### データポイントの消費
 
-現在、この統合では、ライブエージェントがFrontからSMSを送信するたびに、カスタムイベントをユーザープロファイルに書き込む必要があります。これは数回のメッセージで終わるような短いやり取りに適しているかもしれませんが、会話が長くなるにつれてデータポイントの影響も大きくなります。データポイントは、Braze に記録された各カスタムイベントごとに消費されます。
+現在、この統合では、ライブエージェントが Front から SMS を送信するたびに、ユーザープロファイルにカスタムイベントを書き込む必要があります。これは数回のメッセージで終わるような短いやり取りに適しているかもしれませんが、会話が長くなるにつれてデータポイントの影響も大きくなります。データポイントは、Braze に記録された各カスタムイベントごとに消費されます。
 
 ### SMSメッセージにリンクを含める
 
@@ -235,4 +235,4 @@ Brazeから送信されたSMSメッセージでは、Frontの画像ファイル
 
 ### オプトアウト 
 
-会話メッセージには、「停止」などのあいまいなオプトアウトとして認識される可能性のある言葉が含まれるリスクが高くなります。
+会話型メッセージでは、あいまいなオプトアウトとして認識される可能性のある言葉 (「stop」など) が含まれるリスクが高くなります。
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/line.md b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/line.md
index ea3ee9d63fa..631d834808d 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/line.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/line.md
@@ -10,21 +10,21 @@ search_tag: Partner
 
 # LINE
 
-> [LINE](https://line.me/en/) は、世界中で最も人気のあるインスタントメッセージング プラットフォームs の1 つで、数億の月間アクティブユーザーs によって使用されます。このプラットフォームを通じて、ブランドは豊かで双方向のメッセージングで顧客と関わることができる。
+> [LINE](https://line.me/en/) は、世界中で最も人気があるインスタントメッセージングプラットフォームの1つであり、1か月あたりのアクティブユーザー数は数億にのぼります。このプラットフォームを通じて、ブランドは豊かで双方向のメッセージングで顧客と関わることができる。
 
 Braze とLINE の統合により、Braze webhook、高度なセグメンテーション、パーソナライゼーション、およびトリガー機能を活用して、[LINE メッセージング API](https://developers.line.biz/en/docs/messaging-api/overview/) を通じてLINE でユーザーにメッセージを送信できます。
 
 ## 前提条件
 
-ブランドがユーザーの同意を得ていれば、プロモーションと非プロモーションの両方のメッセージングがSをユーザーすることができます。ユーザーs に送信するには、次の2 つの条件のいずれかを満たす必要があります。
-- LINEオフィシャルアカウントを友人として追加したユーザー
+LINE では、ブランドがユーザーの同意を得ている限り、プロモーションメッセージングと非プロモーションメッセージングの両方が可能です。ユーザーにメッセージを送信するには、次の2つの条件のいずれかを満たしている必要があります。
+- お客様の LINE 公式アカウントを友だちとして追加したユーザー
 - LINEオフィシャルアカウントを友達として追加していないが、LINEオフィシャルアカウントにメッセージを送信したユーザー(LINEオフィシャルアカウントにブロックを行ったユーザーを除く)。
 <br><br>
 
 | 要件 | 説明 |
 | ----------- | ----------- | 
-| LINE ビジネスアカウント | この提携の前倒しタグを行うには、LINE [公式ビジネスアカウント](https://www.linebiz.com/jp-en/)が必要です。<br><br>LINE メッセージを送信すると、すべてのメッセージがLINE の公式アカウントに関連付けられ、アカウント名とページがユーザーに表示されます。|
-| メッセージングAPI チャネル | メッセージング API をLINE [公式アカウントマネージャー](https://developers.line.biz/en/docs/messaging-api/getting-started/#using-oa-manager) で使用可能にすると、メッセージング API チャネルが作成されます。これは、顧客 s との通信に使用するチャネルです。 |
+| LINE ビジネスアカウント | このパートナーシップを活用するには、LINE の[公式ビジネスアカウント](https://www.linebiz.com/jp-en/)が必要です。<br><br>LINE メッセージを送信すると、すべてのメッセージがLINE の公式アカウントに関連付けられ、アカウント名とページがユーザーに表示されます。|
+| メッセージングAPI チャネル | メッセージング API をLINE [公式アカウントマネージャー](https://developers.line.biz/en/docs/messaging-api/getting-started/#using-oa-manager) で使用可能にすると、メッセージング API チャネルが作成されます。これは、顧客とのコミュニケーションに使用するチャネルになります。 |
 | チャンネル接続トークンs |[チャネルアクセストークン](https://developers.line.biz/en/docs/messaging-api/channel-access-tokens/)を使用すると、LINEオフィシャルアカウントを友達として追加したユーザーにメッセージを送信できます。このトークンは、**LINE 開発者コンソール** の**メッセージAPI** タブにあります。
 | LINE ユーザー ID | LINEでメッセージを送信するには、ユーザーのLINE ID(このIDはユーザーのユーザーの名前とは異なります)が必要になります。<br><br>ユーザーがLINEオフィシャルアカウントを友達として追加すると、LINEのユーザーのAPIを介してユーザーのLINE IDにアクセスできます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
@@ -33,11 +33,11 @@ Braze とLINE の統合により、Braze webhook、高度なセグメンテー
 
 ### ステップ1:顧客 LINE ID の収集
 
-LINEでメッセージを送信するには、ユーザーのLINE IDを収集して、ユーザーを識別し、一貫して対話する必要があります。LINE ID は、ユーザーのLINE ユーザーの名前とは異なります。LINE ID はLINE によって生成され、LINE のAPI と対話するときに使用できます。
+LINE でメッセージを送信するには、ユーザーを識別し、一貫したやり取りを行うためにユーザーの LINE ID を収集する必要があります。LINE ID は、ユーザーのLINE ユーザーの名前とは異なります。LINE ID は LINE によって生成され、LINE の API とのやり取りで使用できます。
 
-LINE ID は、LINE [User ID API](https://developers.line.biz/en/reference/messaging-api/#get-follower-ids) を使用して取得できます。このエンドポイントは、LINE official account に友達であるか、アカウントにメッセージを送信し、ブロックしていないすべてのユーザーのLINE ID のリストを返します。 
+LINE ID は、LINE [User ID API](https://developers.line.biz/en/reference/messaging-api/#get-follower-ids) を使用して取得できます。このエンドポイントは、お客様の LINE 公式アカウントを友だちとして追加したユーザー、またはお客様の LINE アカウントにメッセージを送信しておりお客様をブロックしていないユーザー全員の LINE ID のリストを返します。 
 
-エンドポイント `https://api.line.me/v2/bot/followers/ids` に対してGET リクエストを行うと、次のようになります。
+エンドポイント `https://api.line.me/v2/bot/followers/ids` に対して GET リクエストを行うと、次の結果が得られます。
 ```json
 {
    "userIds":[
@@ -52,30 +52,30 @@ LINE ID の一覧を取得したら、`line_id` カスタム属性としてBraze
 
 ### ステップ2:IDをカスタム属性としてBrazeに送信
 
-これを調整して開発者s と共有し、`line_id` を[カスタム属性 s]({{site.baseurl}}/user_guide/Data_and_Analytics/Custom_Data/Custom_Attributes/#custom-attributes) としてBraze に送信します。
+Braze に `line_id` を[カスタム属性]({{site.baseurl}}/user_guide/Data_and_Analytics/Custom_Data/Custom_Attributes/#custom-attributes)として送信するために、開発者とこれを調整して共有します。
 
 ### ステップ3:チャネルのアクセストークンをコンテンツブロックとして設定します。
 
-Braze で、**Templates &Media >Content Blocks Library > + Create Content Block** に移動し、Braze[Content Block]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/#content-blocks) を作成します。このコンテンツブロックの名前は`LINE_Channel_AccessToken` です。 
+Braze で **\[テンプレートとメディア] > \[コンテンツブロックライブラリ] > \[+ コンテンツブロックを作成]** に移動し、Braze [コンテンツブロック]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/#content-blocks)を作成します。このコンテンツブロックの名前は`LINE_Channel_AccessToken` です。 
 
 次に、コンテンツブロックボディにチャネルのアクセストークンを貼り付けて保存します。
 
-![コンテンツブロックの"画像で、コンテンツブロックの名前、リキッドタグ、および検閲されたチャネルアクセストークンが表示されます。][2]
+![コンテンツブロック名、Liquid タグ、検閲済みチャネルアクセストークンが表示されているコンテンツブロック。][2]
 
 コンテンツブロック内のチャネル接続トークンを設定すると、LINE Webhook テンプレートを使用してユーザーsにメッセージを送信できるようになります。
 
 ### ステップ4:Webhook テンプレートを選択
 
-**テンプレート s** > **Webhook テンプレート s** に移動し、次のLINE Messenger Webhook テンプレートs のいずれかを選択します。
+\[**テンプレート**] > \[**Webhook テンプレート**] に移動し、以下の LINE Messenger Webhookテンプレートのいずれかを選択します。
 
-![使用可能な符号付きWebhook テンプレートs.]({% image_buster /assets/img_archive/line_templates.png %})の選択{: style="border:0px;"}
+![使用可能な事前に設計されている Webhook テンプレート。]({% image_buster /assets/img_archive/line_templates.png %}){: style="border:0px;"}
 
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation) を使用している場合は、**Engagement**> **Templates &Media**> **Webフックテンプレート** に移動します。
 {% endalert %}
 
 {% tabs %}
-{% tab ラインテキスト %}
+{% tab LINE テキスト %}
 LINE [text](https://developers.line.biz/en/docs/messaging-api/message-types/#text-messages)Webhook テンプレートを使用すると、絵文字に対応したテキストベースのメッセージを送信できます。
 
 ![テキストメッセージがプラットフォーム上でどのように見えるかを示す2 つのサンプルを含む行メッセージング UI。]({% image_buster /assets/img_archive/line_text_type.png %}){: style="max-width:70%;border:0px;"}
@@ -83,29 +83,29 @@ LINE [text](https://developers.line.biz/en/docs/messaging-api/message-types/#tex
 {% tab ラインステッカー %}
 LINE [ステッカー](https://developers.line.biz/en/docs/messaging-api/message-types/#sticker-messages)テンプレートでステッカーメッセージを送信できます。ステッカーを使用すると、ボットアプリをより表現力豊かにし、ユーザーに魅力的にすることができます。 
 
-ステッカーを送信するには、ステッカーのパッケージID とステッカーID をメッセージオブジェクトに含めます。Messaging API で送信できるステッカー のリスト[ を参照してください。
+ステッカーを送信するには、ステッカーのパッケージID とステッカーID をメッセージオブジェクトに含めます。Messaging API で送信できる[スタンプのリスト](https://developers.line.biz/en/docs/messaging-api/sticker-list/)を参照してください。
 
-![この行は、ステッカーメッセージがどのように見えるかをいくつか例示したUI をメッセージングします。これらの例には、クマを祝うこと、親指をあげるウサギ、黄色いアヒル]({% image_buster /assets/img_archive/line_sticker_type.png %})が含まれる。{: style="max-width:70%;border:0px;"}
+![複数のスタンプメッセージの表示例を示す LINE メッセージング ＵＩ。これらの例は、祝うクマ、親指を立てるウサギ、黄色いアヒルである。]({% image_buster /assets/img_archive/line_sticker_type.png %}){: style="max-width:70%;border:0px;"}
 {% endtab %}
-{% tab LINE画像 %}
-LINE ["画像](https://developers.line.biz/en/docs/messaging-api/message-types/#image-messages)テンプレートを使用すると、"画像sをLINE ユーザーsに送信できます。
+{% tab LINE 画像 %}
+LINE の[画像](https://developers.line.biz/en/docs/messaging-api/message-types/#image-messages)テンプレートを使用すると、LINE ユーザーに画像を送信できます。
 
-"画像を送信するには、元の"画像のURL とメッセージオブジェクトの小さいプレビュー "画像を含めます。プレビュー "画像はチャットに表示され、フル"画像は"画像がアプリになったときに開封されます。URL は、TLS 1.2 以降のHTTPS を使用する必要があります。
+画像を送信するには、元の画像の URL と小さなプレビュー画像の URL をメッセージオブジェクトに組み込みます。プレビュー画像はチャットに表示され、フル画像は画像をタップしたときに表示されます。URL には、HTTPS over TLS 1.2 以降を使用する必要があります。
 
-!["画像 がプラットフォーム上でどのように表示されるかを示す行メッセージング。]({% image_buster /assets/img_archive/line_image_type.png %})
+![プラットフォームでの画像メッセージの表示例を示す LINE メッセージング UI。]({% image_buster /assets/img_archive/line_image_type.png %})
 {% endtab %}
-{% tab ラインカローセル %}
-LINE [carousel](https://developers.line.biz/en/docs/messaging-api/message-types/#carousel-template)テンプレートを使用すると、ユーザー sが循環できる複数の列オブジェクトを含むメッセージを送信できます。ボタンを持つことに加えて、ユーザーが"画像、タイトル、またはテキストエリアのどこかをたたいたときに実行される単一のアクションを列オブジェクトごとに指定することもできます。
+{% tab LINE カルーセル %}
+LINE [carousel](https://developers.line.biz/en/docs/messaging-api/message-types/#carousel-template)テンプレートを使用すると、ユーザー sが循環できる複数の列オブジェクトを含むメッセージを送信できます。ボタンを組み込むだけでなく、各カラムオブジェクトで、ユーザーが画像エリア、タイトルエリア、テキストエリアの中のどこかをタップすると実行される1つのアクションを指定することもできます。
 
-![カルーセルメッセージを示す行メッセージングユーザーインターフェイス。このメッセージには、"画像、説明、予約ボタン、コールボタンを含む切り替え可能なコンテンツボックスが含まれています。]({% image_buster /assets/img_archive/line_carousel_type.png %}){: style="max-width:70%;border:0px;"}
+![カルーセルメッセージを示す LINE メッセージング UI。このメッセージのスワイプ可能なコンテンツボックスには、画像、説明、\[Reserve] ボタン、\[Call] ボタンが含まれている。]({% image_buster /assets/img_archive/line_carousel_type.png %}){: style="max-width:70%;border:0px;"}
 {% endtab %}
 {% endtabs %}
 
 ### ステップ 5: Webhook テンプレートのセットアップ
 
-Webhook テンプレートで、テンプレートの名前を入力し、必要に応じてチームとタグs を追加します。次に、選択したLINE テンプレートの種類に応じて、メッセージ、ステッカーID、または"画像を入力します。
+Webhook テンプレートで、テンプレートの名前を入力し、必要に応じてチームとタグs を追加します。次に、選択した LINE テンプレートの種類に応じて、メッセージ、スタンプ ID、または画像を入力します。
 
-カスタム属性`LINE ID` は、メッセージ本文の`To:` フィールドのテンプレートd である必要があります。そうでない場合は、LINE ID をカスタム属性として含めます。これを行うには、**Request Body**ボックスの隅にある青と白の+ボタンを使用します。
+カスタム属性 `LINE ID` は、メッセージ本文の `To:` フィールドでテンプレート化されている必要があります。そうでない場合は、LINE ID をカスタム属性として含めます。これを行うには、**Request Body**ボックスの隅にある青と白の+ボタンを使用します。
 
 #### Webフックのプレビューとテスト
 
@@ -117,11 +117,11 @@ Webhookを確認してから送信してください。LINE ID がBraze に保
 
 ## この統合の使用
 
-設定が完了したら、このインテグレーションを使用してLINE ユーザー s を対象にします。まず、\[`LINE ID` がカスタム属性として存在するすべてのユーザーs に対してSegment][62] を作成し、[分析 "トラッキング][61] をオンにして、Messenger サブスクリプションレートを経時的に追跡します。 
+設定が完了したら、このインテグレーションを使用してLINE ユーザー s を対象にします。まず、`LINE ID` がカスタム属性として設定されているすべてのユーザーの[セグメントを作成し][62]、[分析トラッキング][61]をオンにして Messenger サブスクリプション率を経時的に追跡します。 
 
-![セグメントフィルター"line_id"を"に設定すると空白"ではありません。][63]
+![「is not blank」に設定されてるセグメントフィルター「line_id」。][63]
 
-Messenger サブスクライバーs に固有のSegmentを作成しない場合は、エラーs を回避するために、`LINE ID` のフィルターを必ず含めてください。
+Messenger サブスクライバー向けの特定のセグメントを作成しない場合は、エラーを避けるために、既存の `LINE ID` のフィルターを必ず含めてください。
 
 他のセグメンテーションを使用して、他のキャンペーンと同様に、LINE キャンペーン s および残りのキャンペーン作成処理を対象にすることもできます。
 
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/messenger.md b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/messenger.md
index fec82ec3baa..3cb777edc81 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/messenger.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/messenger.md
@@ -2,7 +2,7 @@
 nav_title: Messenger
 article_title: Facebook Messenger
 alias: /partners/messenger/
-description: "この参考文献は、Brazeと、世界中で最も人気のあるインスタントメッセージング プラットフォームの1つであるファック・eBook Messengerとの提携について概説している。"
+description: "このリファレンス記事では、Braze と Facebook Messenger のパートナーシップについて説明します。Facebook Messenger は、世界で最も人気があるインスタントメッセージプラットフォームの1つです。"
 page_type: partner
 search_tag: Partner
 
@@ -10,42 +10,42 @@ search_tag: Partner
 
 # Facebook Messenger
 
-> [Fac eBook Messenger](https://developers.facebook.com/docs/messenger-platform/)は、世界中で最も人気のあるインスタントメッセージング プラットフォームの1つで、月間10億近くのアクティブユーザーで使用されています。このプラットフォームを通じて、ブランドは魅力的なチャットボットを作り出し、彼らの顧客と知的かつ自動的にやり取りすることができる。
+> [Facebook Messenger](https://developers.facebook.com/docs/messenger-platform/) は、世界で最も人気があるインスタントメッセージングプラットフォームの1つで、1か月あたりのアクティブユーザー数は10億にのぼります。ブランドはこのプラットフォームで、顧客とインテリジェントかつ自動的にやり取りするための魅力的なチャットボットを作成します。
 
-Braze およびFac eBook インテグレーションは、Braze webhook、セグメンテーション、およびパーソナライゼーション、およびトリガー リング機能を活用して、Messenger プラットフォームAPI を介してFac eBook Messengerでユーザーに通知します。カスタムFac eBook Messenger Webhook テンプレートは、**テンプレート s**> **Webhook テンプレート s** のプラットフォームに含まれています。
+Braze とFacebook の統合では、Messenger Platform API を介して Facebook Messenger のユーザーにメッセージを送信するために、Braze Webhook、セグメンテーション、パーソナライゼーション、トリガー機能が利用されます。カスタム Facebook Messenger Webhook テンプレートは、Braze プラットフォームの \[**テンプレート**] > \[**Webhook テンプレート**] にあります。
 
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation) を使用している場合は、**Engagement**> **Templates &Media**> **Webフックテンプレート** に移動します。
 {% endalert %}
 
-Fac eBook Messenger プラットフォームは、"既存のトランスアクションを促進したり、他の顧客支援アクションを提供したり、人から要求された内容を配信したりする非プロモーションメッセージを意図しています。詳しくは、[Fac eBookのプラットフォームガイドライン](https://developers.facebook.com/docs/messenger-platform)および[許容ユースケースの例s](https://developers.facebook.com/docs/messenger-platform/app-review#examples_acceptable)を参照してください。
+Facebook Messenger プラットフォームは、「既存の取引を促進し、他の顧客サポートアクションを提供し、個人が要求したコンテンツを配信する非プロモーションメッセージ」を対象としています。詳細については、[Facebook のプラットフォームガイドライン](https://developers.facebook.com/docs/messenger-platform)と[許容可能なユースケースの例](https://developers.facebook.com/docs/messenger-platform/app-review#examples_acceptable)を参照してください。
 
 ## 前提条件
 
 統合を進める前に、以下を確認します。
-- ファクスeBookでは、Messenger プラットフォームを使用してマーケティングを送信することはできません。 
-- ユーザーの明示的な権限が必要になります。 
+- Facebook では、マーケティングメッセージの送信に Messenger プラットフォームを使用することを許可していません。 
+- お客様のページからのメッセージに対するユーザーの明示的な許可が必要になります。 
 - FaceBook アプリのテストユーザーではないユーザーにメッセージを送信するには、アプリがFaceBookの[アプリレビュー](https://developers.facebook.com/docs/messenger-platform/app-review)に合格する必要があります。<br><br>
 
-| 要件| Origin| アクセス| 説明|
+| 要件| 提供元| アクセス| 説明|
 | ---| ---| ---|
-| ファクスeBook Messenger画面| Facebook| [https://<メタID="2" />/pages/create](https://www.facebook.com/pages/create) | Fac eBook ページがボットのID として使用されます。アプリとチャットすると、ページネームとプロファイルピクチャが表示されます。|
-| ファックeBook Messenger アプリ| Facebook| [https://developers.facebook.com/アプリs](https://developers.facebook.com/apps) | Fac eBook アプリには、アクセストークンs を含むMessengerボットの設定s が含まれています。
-| アプリボット審査・アプリ評価 | Facebook | [https://developers.facebook.com/docs/messenger-platform/app-review](https://developers.facebook.com/docs/messenger-platform/app-review) | ボットを公開する準備ができたら、Fac eBook に送信して確認し、承認をアプリする必要があります。この審査の過程で、皆様のMessengerボットが、私たちの方針と機能を期待どおりに遵守し、Messengerの全員が利用できるようにすることができます。 |
-| ページスコープID (PSID) | Facebook | [https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messages](https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messages) | ファクスeBook Messengerで送信するには、ユーザーのPSIDが必要です。ユーザーがMessenger を介してアプリと通信すると、Fac eBook によってPSID が作成されます。このPSID は、ストリングカスタム属性としてBraze に送信できます。
-| ページアクセストークン | Facebook | [https://developers.facebook.com/docs/messenger-platform/getting-started/app-setup#page_access_token](https://developers.facebook.com/docs/messenger-platform/getting-started/app-setup#page_access_token) | これらのアクセストークンs は、ユーザー アクセストークンs に似ていますが、ファックページに属するデータの読み取り、書き込み、または変更を行う権限 API を提供する点が異なります。ページアクセストークンを取得するには、ユーザーアクセストークンを取得し、`manage_pagespermission`を要求する必要があります。ユーザーアクセストークンを取得したら、グラフAPI を使用してページアクセストークンを取得します。|
+| Facebook Messenger ページ| Facebook| [https://www.facebook.com/pages/create](https://www.facebook.com/pages/create) | Facebook ページがボットの ID として使用されます。アプリとチャットすると、ページ名とプロファイル画像が表示されます。|
+| Facebook Messenger アプリ| Facebook| [https://developers.facebook.com/apps](https://developers.facebook.com/apps) | Facebook アプリには、アクセストークンなどの Messenger ボットの設定が含まれています。
+| アプリボットの審査と承認 | Facebook | [https://developers.facebook.com/docs/messenger-platform/app-review](https://developers.facebook.com/docs/messenger-platform/app-review) | ボットを公開する準備ができたら、審査と承認を受けるために Facebook に提出する必要があります。す。この審査の過程で、皆様のMessengerボットが、私たちの方針と機能を期待どおりに遵守し、Messengerの全員が利用できるようにすることができます。 |
+| ページスコープ ID (PSID) | Facebook | [https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messages](https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messages) | Facebook Messenger でメッセージを送信するには、ユーザー PSID が必要です。ユーザーが Messenger を介してアプリとやり取りするときに、Facebook によって PSID が作成されます。このPSID は、ストリングカスタム属性としてBraze に送信できます。
+| ページアクセストークン | Facebook | [https://developers.facebook.com/docs/messenger-platform/getting-started/app-setup#page_access_token](https://developers.facebook.com/docs/messenger-platform/getting-started/app-setup#page_access_token) | これらのアクセストークンは、Facebook Page に属するデータの読み取り、書き込み、変更を行う API に権限を付与することを除き、ユーザーアクセストークンと似ています。ページアクセストークンを取得するには、ユーザーアクセストークンを取得し、`manage_pagespermission` を要求する必要があります。ユーザーアクセストークンを取得したら、Graph API を使用してページアクセストークンを取得できます。|
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 統合
 
-BrazeファクトeBook Messenger Webhookの設定方法を以下に示します。
+以下に、Braze Facebook Messenger Webhook の設定方法を示します。
 ボットのセットアップに追加のヘルプが必要な場合は、[ Braze GitHub リポジトリ](https://github.com/Appboy/appboy-fb-messenger-bot) に完全なMessengerボットチュートリアルとサンプルコードがあります。
 
 ### ステップ1:PSID を収集する
 
-Fac eBook Messengerでメッセージを送信するには、ユーザーのページ固有ID (PSID) を収集して、ユーザーを識別し、一貫して対話する必要があります。PSID は、ユーザーのファクスeBookID とは異なります。Fac eBook は、顧客を表示したり、顧客を表示したりするたびに、この識別子を作成します。
+Facebook Messenger でメッセージを送信するには、ユーザーを識別し、一貫したやり取りを行うためにユーザーのページ固有の ID (PSID) を収集する必要があります。PSID はユーザーの Facebook ID とは異なります。顧客にメッセージを送信する場合または顧客からメッセージが送信される場合は常に、Facebook によりこの ID が作成されます。
 
-PSID は、さまざまな[エントリポイント](https://developers.facebook.com/docs/messenger-platform/discovery) Fac eBook のいずれかを使用して見つけることができます。ユーザーがアプリにメッセージを送ったり、ボタンをアプリしたり、メッセージを送信したりといった対話のアクションを受け取った後は、そのPSIDが`sender.id`プロパティのWebhookの行動に含まれるため、ボットはアクションを受けた人を識別できます。
+PSID は、Facebook が提供するさまざまな[エントリポイント](https://developers.facebook.com/docs/messenger-platform/discovery)の1つを使用して確認できます。ユーザーがアプリにメッセージを送ったり、ボタンをアプリしたり、メッセージを送信したりといった対話のアクションを受け取った後は、そのPSIDが`sender.id`プロパティのWebhookの行動に含まれるため、ボットはアクションを受けた人を識別できます。
 
 ```
 {
@@ -77,7 +77,7 @@ PSID を受信していると確信したら、これを開発者と調整して
 **Templates & Media**から**Webフックテンプレート**に進み、**FaceBook Messenger Webフックテンプレート**を選択します。
 
 1. テンプレートの名前を入力し、必要に応じてチームとタグs を追加します。
-2. メッセージを入力するか、[Fac eBook](https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messages)で利用可能なメッセージテンプレートを選択します。また、[type](https://developers.facebook.com/docs/messenger-platform/send-messages#message_types)または[タグ](https://developers.facebook.com/docs/messenger-platform/send-messages/message-tags)を選択することもできます。
+2. メッセージを入力するか、[Facebook で利用可能なメッセージテンプレート](https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/messages)からメッセージテンプレートを選択します。また、[タイプ](https://developers.facebook.com/docs/messenger-platform/send-messages#message_types)や[タグ](https://developers.facebook.com/docs/messenger-platform/send-messages/message-tags)を選択することもできます。
 3. カスタム属性としてPSID を含めます。これを行うには、**Request Body**ボックスの隅にある、青と白の**+**ボタンを使用します。
 3. `FACEBOOK_PAGE_ACCESS_TOKEN` をトークンに置き換えて、Webhook URL にページアクセストークンを追加します。
 
@@ -85,19 +85,19 @@ PSID を受信していると確信したら、これを開発者と調整して
 
 Webhookを確認してから送信してください。Messenger ID がBraze に保存されていることを確認し(または、それを見つけてカスタマイズしたユーザーとしてテストする)、プレビューを使用してテストメッセージを送信します。
 
-![Fac eBook Messenger Webhook テンプレートのTest タブでは、現存するユーザーに送信することでメッセージをプレビューできます。][60]
+![Facebook Messenger Webhook テンプレートの「Test」タブ。既存のユーザーにメッセージを送信することでそのメッセージをプレビューできる。][60]
 
 メッセージが正常に受信された場合は、配信設定s を設定できます。
 
 ## この統合の使用
 
-設定が完了したら、このインテグレーションを使用してFac eBook Messenger ユーザー s を対象にします。ユーザー の電話番号を使用してメッセージを送信しておらず、繰り返しMessengerメッセージを送信する予定がない場合は、\[Messenger ID が存在するすべてのユーザーにSegment][62] を作成し、\[分析 "トラッキング][61]] をオンにして、Messenger サブスクリプションレートを経時的に追跡する必要があります。 
+設定が完了したら、この統合を使用して Facebook Messenger ユーザーをターゲットにします。ユーザーの電話番号を使用してメッセージを送信しておらず、Messenger メッセージを繰り返し送信する予定がある場合は、Messenger ID がカスタム属性として存在するすべてのユーザーに対して\[セグメントを作成][62]し、\[分析の追跡][61]をオンにして、Messenger のサブスクリプション率を経時的に追跡する必要があります。 
 
-![セグメントフィルター"messenger_id"を"に設定すると空白"ではありません。][63]
+![セグメントフィルター「messenger_id」が「is not blank」に設定されている。][63]
 
-Messenger サブスクライバーs に固有のSegmentを作成しない場合は、エラーs を回避するために、Messenger ID のフィルターを必ず含めてください。
+Messenger サブスクライバー向けの特定のセグメントを作成しない場合は、エラーを避けるために、既存の Messenger ID のフィルターを必ず含めてください。
 
-他のセグメンテーションを使用して、他のキャンペーンと同様に、Messenger キャンペーンs、および残りのキャンペーン作成処理をターゲットにすることもできます。
+他のセグメンテーションを使用して Messenger キャンペーンをターゲットにし、他のキャンペーンと同様にそれ以降のキャンペーン作成プロセスを実行することもできます。
 
 [60]: {% image_buster /assets/img_archive/fbm-test.png %}
 [61]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/regal.md b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/regal.md
index 077f100ae31..4512c21d0c4 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/regal.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/regal.md
@@ -10,32 +10,32 @@ search_tag: Partner
 
 # Regal
 
-> \[Regal.io][6] は、より多くの会話を促進し、成長目標をより早く達成するために構築された電話およびSMSの販売ソリューションです。
+> \[Regal.io][6] は、より多くの会話を促進するために構築された電話および SMS セールスソリューションです。これにより、成長目標をより短期間で達成できるようになります。
 
-RegalとBrazeを統合することで、すべての顧客接点にわたってより一貫性のあるパーソナライズされた体験を提供できます。
-- Regalの電話での会話内容に基づいて、Brazeから次に最適なメールまたはプッシュ通知を送信します。
-- 高価値の顧客がBrazeからのマーケティングメールをクリックしたがコンバージョンしなかった場合、Regalでを呼び出します。
+Regal と Braze の統合により、すべての顧客タッチポイントでより一貫性がありパーソナライズされたエクスペリエンスを作成できます。
+- Regal での電話による会話の内容に基づいて、Braze から適切なネクストベストのメールまたはプッシュ通知を送信します。
+- 価値の高い顧客が Braze からのマーケティングメールをクリックスルーしたがコンバージョンに至らなかった場合に、Regal でコールをトリガーします。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| リーガルアカウント | このパートナーシップを利用するには、リーガルアカウントが必要です。 |
-| リーガル API キー | RegalのAPIキーを使用すると、BrazeからRegalにイベントを送信できます。<br><br>メール [support@regal.io](mailto:support@regal.io) にこのキーを取得するためにメールしてください。 |
-| Braze データ変換 | データ変換は現在アーリーアクセス中です。早期アクセスに参加することに興味がある場合は、Brazeの顧客成功マネージャーに連絡してください。これはリーガルからデータを受け取るために必要です。 |
+| Regal アカウント | このパートナーシップを活用するには、Regal アカウントが必要です。 |
+| リーガル API キー | RegalのAPIキーを使用すると、BrazeからRegalにイベントを送信できます。<br><br>このキーを取得するには、[support@regal.io](mailto:support@regal.io) までメールでご連絡ください。 |
+| Braze Data Transformation | Data Transformation は現在早期アクセス段階です。早期アクセスへの参加に興味がある場合は、Braze カスタマーサクセスマネージャーにお問い合わせください。これは、Regal からデータを受信するために必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-## 統合：BrazeからRegalにデータを送信する
+## 統合:BrazeからRegalにデータを送信する
 
-次のセクションでは、Brazeをソースとして使用し、Braze キャンバスまたはキャンペーンwebhookを使用して顧客プロファイルおよびイベントデータをRegalに送信する方法について説明します。
+次のセクションでは、Braze キャンバスまたはキャンペーン Webhook を使用して顧客プロファイルとイベントデータを Regal に送信するためのソースとして Braze を使用する方法について説明します。
 
 ### ステップ1:Regalで新しい連絡先を作成する
 
-新しい連絡先がBrazeで作成されるたびに、Regalでの通話やテキストメッセージに利用できるようにするために、キャンバスまたはキャンペーンを作成し、Regalにwebhookを送信します。 
+Braze で作成される新しい連絡先を Regal でのコールやテキストに利用できるようにするには、Braze でこのような連絡先が作成されるたびに Webhook で Regal に通知するキャンバスまたはキャンペーンを作成します。 
 
 1. 「Regalの新しい連絡先を作成」と題されたキャンバスまたはキャンペーンを作成し、エントリタイプとして**アクションベース**を選択します。
 
-2. トリガーロジックを**カスタムイベント**として、電話番号を持つ連絡先が作成されたときに発生するイベントを選択します。リーガルは、電話フィールドに設定されていることを確認するための追加フィルターを追加することも推奨しています。
+2. トリガーロジックを**カスタムイベント**として、電話番号を持つ連絡先が作成されたときに発生するイベントを選択します。Regal では、電話番号が確実に設定されるようにするため、電話番号フィールドにフィルターを追加することも推奨されています。
 
 3. 新しいWebhookテンプレートに、次のフィールドに記入してください:
    - **Webhook URL**: <https://events.regalvoice.com/events>
@@ -43,17 +43,17 @@ RegalとBrazeを統合することで、すべての顧客接点にわたって
 
 #### リクエストヘッダーとメソッド
 
-Regal.io には認証のためのHTTPヘッダーとHTTPメソッドも必要です。次の内容は、**設定**タブのキーと値のペアとして既にテンプレートに含まれています:
+Regal.io には、認証用の HTTP ヘッダーと HTTP メソッドが必要です。次の内容は、**設定**タブのキーと値のペアとして既にテンプレートに含まれています:
 {% raw %}
 - **HTTPメソッド**:POST
 - **リクエストヘッダー**:
-    - **認可**: `{{<REGAL_API_KEY>}}`
+    - **Authorization**: `{{<REGAL_API_KEY>}}`
     - **Content-Type**: application/json
 {% endraw %}
 
 #### Request body
 
-以下の唯一の必須フィールドは`traits.phone`プロパティです。残りはオプションです。しかし、`optIn`を含める場合は、`optIn.channel`と`optIn.subscribed`を含める必要があります。
+以下の唯一の必須フィールドは`traits.phone`プロパティです。残りはオプションです。ただし `optIn` を含める場合は、`optIn.channel` と `optIn.subscribed` を含める必要があります。
 
 ```json
 {
@@ -82,13 +82,13 @@ Regal.io には認証のためのHTTPヘッダーとHTTPメソッドも必要で
 }
 ```
 
-上記のペイロードの例は、すべての連絡先が音声およびSMSのオプトインを受け入れたことを前提としています。それが真実でない場合は、上記から`optIn`プロパティを削除し、`optIn`が収集されたときにRegalで連絡先を更新するための別のキャンバスまたはキャンペーンを設定できます。
+上記のペイロードの例は、すべての連絡先が音声と SMS のオプトインに同意していることを前提としています。これに該当しない場合は、上記の `optIn` プロパティを削除し、`optIn` が収集されたときに Regal で連絡先を更新する別のキャンバスまたはキャンペーンを設定できます。
 
 ### ステップ2:オプトイン情報を更新 
 
-お客様のアプリのユーザーエクスペリエンスのさまざまな部分でオプトインおよびオプトアウトが発生する可能性がある場合、ユーザーがオプトインまたはオプトアウトするたびにRegalを更新することが重要です。以下は、Regalに最新のオプトイン情報を送信するための推奨キャンバスです。これはBrazeプロファイルフィールドとして保存することを前提としていますが、そうでない場合、トリガーはユーザーがオプトインまたは購読解除することを表すBrazeアカウントのイベントでもかまいません。（以下の例は電話のオプトイン用ですが、キャンバスまたはキャンペーンを設定して、SMSオプトインを別々に収集することもできます）。
+お客様のアプリのユーザーエクスペリエンスのさまざまな部分でオプトインおよびオプトアウトが発生する可能性がある場合、ユーザーがオプトインまたはオプトアウトするたびにRegalを更新することが重要です。以下は、Regalに最新のオプトイン情報を送信するための推奨キャンバスです。これを Braze プロファイルのフィールドとして保存することを前提としていますが、保存されていない場合、トリガーは、Braze アカウントでユーザーがオプトインまたはサブスクリプション解除したことを表すイベントと同じくらい容易です。（以下の例は電話のオプトイン用ですが、キャンバスまたはキャンペーンを設定して、SMSオプトインを別々に収集することもできます）。
 
-1. 新しいキャンバスまたはキャンペーンを「Send Opt In or Out to Regal」というタイトルで作成します。
+1. 新しいキャンバスまたはキャンペーンを作成して「Send Opt In or Out to Regal」というタイトルを付けます。
 
 2. 次のトリガーオプションのいずれかを選択し、ユーザーのオプトインステータスを表すフィールドを選択します。オプトインまたはオプトアウトを表すイベントをBrazeに送信する場合は、そのイベントをトリガーとして使用してください。
     - ユーザープロファイルフィールド更新済み
@@ -101,11 +101,11 @@ Regal.io には認証のためのHTTPヘッダーとHTTPメソッドも必要で
 
 #### リクエストヘッダーとメソッド
 
-Regal.io には認証のためのHTTPヘッダーとHTTPメソッドも必要です。次の内容は、テンプレート内にキーと値のペアとして既に含まれていますが、**設定**タブにあります:
+Regal.io には、認証用の HTTP ヘッダーと HTTP メソッドが必要です。次の内容は、テンプレート内にキーと値のペアとして既に含まれていますが、**設定**タブにあります:
 {% raw %}
 - **HTTPメソッド**:POST
 - **リクエストヘッダー**:
-    - **認可**: `{{<REGAL_API_KEY>}}`
+    - **Authorization**: `{{<REGAL_API_KEY>}}`
     - **Content-Type**: application/json
 {% endraw %}
 
@@ -137,11 +137,11 @@ Regal.io には認証のためのHTTPヘッダーとHTTPメソッドも必要で
 
 ### ステップ3:カスタムイベントを送信
 
-最後に、キャンバスまたはキャンペーンを設定して、Regalに送信したい主要なイベントごとに設定します。Regalは、SMSや通話をトリガーするために重要なイベント（サインアップや購入フローの各ステップでのイベントなど）や、Regalキャンペーンから連絡先が外れるための終了基準として使用されるイベントを送信することを推奨します。
+最後に、Regal を送信するキーイベントごとにキャンバスまたはキャンペーンを設定します。Regal では、Regal で SMS および通話をトリガーするうえで重要なすべてのイベント (登録フローまたは購入フローの各ステップでのイベントなど) を送信することが推奨されています。このようにしない場合、それは連絡先が Regal キャンペーンの対象外となる終了基準として使用されます。
 
 例えば、以下はユーザーがアプリケーションの最初のステップを完了したときにRegalにイベントを送信するためのワークフローです。
 
-1. 新しいキャンバスまたは「アプリケーション送信ステップ1完了イベントをRegalに送信」と題されたキャンペーンを作成します。
+1. 新しいキャンバスまたはキャンペーンを作成して、「Send Application Step 1 Completed Event to Regal」というタイトルを付けます。
 
 2. トリガーノードのロジックを**カスタムイベント**として、Regalに送信したいイベント名を選択します。例えば、「アプリケーションステップ1完了」などです。
 
@@ -151,11 +151,11 @@ Regal.io には認証のためのHTTPヘッダーとHTTPメソッドも必要で
 
 #### リクエストヘッダーとメソッド
 
-Regal.io には認証のためのHTTPヘッダーとHTTPメソッドも必要です。次の内容は、テンプレート内にキーと値のペアとして既に含まれていますが、**設定**タブにあります:
+Regal.io には、認証用の HTTP ヘッダーと HTTP メソッドが必要です。次の内容は、テンプレート内にキーと値のペアとして既に含まれていますが、**設定**タブにあります:
 {% raw %}
 - **HTTPメソッド**:POST
 - **リクエストヘッダー**:
-    - **認可**: `{{<REGAL_API_KEY>}}`
+    - **Authorization**: `{{<REGAL_API_KEY>}}`
     - **Content-Type**: application/json
 {% endraw %}
 
@@ -187,25 +187,25 @@ Regal.io には認証のためのHTTPヘッダーとHTTPメソッドも必要で
 
 #### 最新の連絡先属性
 
-必要ではありませんが、Regalは、重要なイベントが利用可能になった時点で最新の連絡先属性にアクセスできるようにするために、イベントワークフローのイベントペイロードに重要なユーザープロファイルデータフィールドも送信することをお勧めします。
+これは必須ではありませんが、Regal では、キーイベントが利用可能になった時点で Regal が最新の連絡先属性にアクセスできるようにするために、イベントワークフローのイベントペイロードの主要なユーザープロファイルデータを送信することが推奨されています。
 
 {% alert note %}
-ご質問がある場合や、これらのキャンバスやキャンペーンの設定方法についての詳細は、support@regal.ioにお問い合わせください。
+Regal に送信する重要なイベント、またはこれらのキャンバスとキャンペーンの設定方法についてご質問がある場合は、support@regal.io にお問い合わせください。
 {% endalert %}
 
-## 統合：RegalからBrazeにデータを送信する
+## 統合:RegalからBrazeにデータを送信する
 
-このセクションでは、`SMS.sent`や`call.completed`などのRegalレポートイベントをBrazeに取り込み、Brazeプロファイルに表示され、Brazeのセグメンテーションツール、キャンバス、およびキャンペーンで利用できるようにする方法について説明します。この統合は、Regal Reporting webhook と Braze データ変換を使用してデータフローを自動化します。
+このセクションでは、`SMS.sent`や`call.completed`などのRegalレポートイベントをBrazeに取り込み、Brazeプロファイルに表示され、Brazeのセグメンテーションツール、キャンバス、およびキャンペーンで利用できるようにする方法について説明します。この統合では、Regal Reporting Webhook と Braze Data Transformation を使用してデータフローを自動化します。
 
-### ステップ1:Brazeでデータ変換を作成する
+### ステップ1:Braze で Data Transformation を作成する
 
 {% alert important %}
-データ変換は現在アーリーアクセス中です。早期アクセスに参加することに興味がある場合は、Brazeの顧客成功マネージャーに連絡してください。
+Data Transformation は現在早期アクセス段階です。早期アクセスへの参加に興味がある場合は、Braze カスタマーサクセスマネージャーにお問い合わせください。
 {% endalert %}
 
 Brazeは、Brazeに送信する予定のRegal Webhookごとに変換を作成することをお勧めします。 
 
-データ変換を作成するには:
+Data Transformation を作成するには、次のようにします。
 1. Braze ダッシュボードの**Transformations**ページに移動します。
 2. 変換に名前を付けて、**変換を作成**をクリックします。
 3. 変換のリストから、<i class="fa-solid fa-ellipsis-vertical" title="アクションを表示"></i>をクリックし、**Webhook URLをコピー**を選択します。
@@ -219,40 +219,40 @@ Brazeは、Brazeに送信する予定のRegal Webhookごとに変換を作成す
 
 2. 「**レポートWebhook**」セクションで、「**Webhookを作成**」をクリックします。
 
-3. Webhookエンドポイント入力に、関連するデータ変換のためのBrazeデータ変換Webhook URLを追加します。
+3. Webhook エンドポイント入力で、関連付けられたData Transformation の Braze Data Transformation Webhook URL を追加します。
 
 ![][5]{: style="max-width:60%;"}
 
 #### エンドポイントの更新
 エンドポイントを編集すると、キャッシュが更新されて新しいエンドポイントにイベントが送信されるまでに最大で5分かかることがあります。
 #### 再試行
-現在、これらのイベントに再試行はありません。応答が5秒以内に受信されない場合、イベントは破棄され、再試行されません。リーガルは将来のリリースでリトライを追加する予定です。
+現在、これらのイベントに再試行はありません。応答が5秒以内に受信されない場合、イベントは破棄され、再試行されません。Regal は今後のリリースで再試行を追加する予定です。
 #### イベント
-Regalの\[Reporting webhookガイド][7]には、公開されているReportingイベントの完全なリストが含まれています。そこでは、プロパティの定義やサンプルペイロードも見ることができます。
+Regalの \[Reporting Webhooks ガイド][7]には、公開する Reporting イベントの完全なリストが含まれています。そこでは、プロパティの定義やサンプルペイロードも見ることができます。
 
-### ステップ3:RegalイベントをBrazeイベントに変換する
+### ステップ3:Regal イベントを Braze イベントに変換する
 
-Brazeの[データ変換]({{site.baseurl}}/data_transformation)機能を使用すると、受信したRegalイベントをBrazeに属性、イベント、または購入として追加するために必要な形式にマッピングできます。
+Braze の [Data Transformation]({{site.baseurl}}/data_transformation) 機能を使用すると、受信した Regal イベントを、Braze で属性、イベント、または購入として追加するのに必要な形式にマッピングできます。
 
-1. データ変換に名前を付けてください。イベントWebhookごとにデータ変換を設定することをお勧めします。
+1. Data Transformation に名前を付けてください。イベント Webhook ごとに Data Transformation を設定することをお勧めします。
 
-2. 接続をテストするには、Regal Agent Desktopから携帯電話に発信し、会話の概要フォームを送信してcall.completedイベントを作成します。
+2. 接続をテストするには、Regal Agent Desktop から携帯電話への発信コールを作成し、Conversation Summary フォームを送信して call.completed イベントを作成します。
 
-3. どの識別子を使用してRegalの連絡先をBrazeのプロファイルにマッピングするかを決定します。Regalイベントで利用可能な識別子には以下が含まれます：
+3. Regal の連絡先を Braze プロファイルにマッピングするために使用する識別子を決定します。Regalイベントで利用可能な識別子には以下が含まれます：
    - `userId` - イベントにのみ設定されますが、この識別子を以前に連絡先に送信した場合に限ります
    - `traits.phone`
    - `traits.email` - イベントにのみ設定されますが、この識別子を以前に連絡先に送信した場合に限ります
 
 #### Braze対応の識別子
-- Brazeは識別子として電話番号をサポートしていません。識別子として使用するには、電話番号をBrazeのユーザーエイリアス][8]として設定できます。
-- Brazeデータ変換を使用する場合、メールアドレスを識別子として使用できます。メールアドレスがBraze内のプロファイルとして存在する場合、既存のプロファイルが更新されます。メールアドレスがBraze内にまだ存在しない場合、メール専用のプロファイルが作成されます。
+- Brazeは識別子として電話番号をサポートしていません。これを識別子として使用するには、Braze で電話番号を\[ユーザーエイリアス][8]として設定できます。
+- Braze Data Transformation を使用する場合、メールアドレスを識別子として使用できます。メールアドレスがBraze内のプロファイルとして存在する場合、既存のプロファイルが更新されます。メールアドレスがBraze内にまだ存在しない場合、メール専用のプロファイルが作成されます。
 
 ## ユースケース
 
 {% tabs %}
-{% tab トリガー メール %}
+{% tab メールをトリガーする %}
 
-**Brazeからのメールをトリガーするのは、Regalのコールディスポジションに基づいています**
+**Regal でのコール処理に基づいて、Braze からメールをトリガーする**
 
 以下は、Regalの`call.completed`イベントのサンプルペイロードです。 
 
@@ -348,11 +348,11 @@ return brazecall;
 ```
 
 {% endtab %}
-{% tab プロファイル属性を更新 %}
+{% tab プロファイル属性を更新する %}
 
-**Brazeで`contact.attribute.edited`イベントに基づいてプロファイル属性を更新する**
+**Regalからの `contact.attribute.edited` イベントに基づいて、Braze のプロファイル属性を更新する**
 
-以下は、Regalの`contact.attribute.edited`イベントのサンプルペイロードです。このイベントは、エージェントの1人が会話で新しいことを学び、連絡先のプロファイルの属性を更新するたびに発生します。
+以下は、Regalの`contact.attribute.edited`イベントのサンプルペイロードです。このイベントは、いずれかのエージェントが会話で新しい情報を得て、連絡先のプロファイルの属性を更新するたびにトリガーされます。
 
 ```json
 {
@@ -412,9 +412,9 @@ return brazecall;
 ```
 
 {% endtab %}
-{% tab 実験を同期させてください %}
+{% tab 実験の同期を維持する %}
 
-**BrazeとRegalで実験を同期させるには、`contact.experiment.assigned`イベントを使用します**
+**`contact.experiment.assigned` イベントを使用して Braze と Regal で実験をの同期を維持する**
 
 以下は、Regalの`contact.experiment.assigned`イベントのサンプルペイロードです。
 
@@ -475,9 +475,9 @@ return brazecall;
 
 ```
 {% endtab %}
-{% tab 配信停止 a contact %}
+{% tab 連絡先のサブスクリプションを解除する %}
 
-**配信停止 a contact in Braze based on a `contact.unsubscribed` from Regal**
+**Regal の `contact.unsubscribed` に基づいて、Braze で連絡先のサブスクリプションを解除する**
 
 以下は、Regalの`contact.unsubscribed`イベントのサンプルペイロードです。
 
@@ -503,7 +503,7 @@ return brazecall;
 }
 ```
 
-以下は、Brazeで連絡先の配信停止を行うサンプルデータ変換です。
+Braze の連絡先のサブスクリプションを解除するサンプル Data Transformation を以下に示します。
 
 ```
 // This is an example template you can use as a starting point. Feel free to delete this entirely to start from scratch or to delete specific components as you see fit.
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md
index c31f09e72d3..04f5ec05a95 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md
@@ -1,69 +1,69 @@
 ---
-nav_title: センドバード
-article_title: センドバード
-description: "このレファレンス記事では、Brazeとセンドバードの提携について概説します。センドバードは、ユーザーSがセンドバードプラットフォームでインアプリ 通知を受信できる先導的なアプリ メッセージング ソリューションです。"
+nav_title: Sendbird
+article_title: Sendbird
+description: "このリファレンス記事では、Braze と Sendbird のパートナーシップについて説明します。Sendbird は、業界をリードするアプリ内メッセージソリューションであり、ユーザーが Sendbird プラットフォームでアプリ内通知を受信できるようにします。"
 alias: /partners/sendbird/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# センドバード
+# Sendbird
 
-> [Sendbird][4]通知はマーケターを提供し、プロダクトマネージャーは、永続的な双方向の一方向メッセージで顧客のs-アプリと通信するための強力な新しいチャネルを提供します。これらの伝言は、どのような通信にも使用でき、プロモーションおよびトランスアクションの目的で最も一般的に使用されます。
+> [Sendbird][4] Notifications は、マーケターと製品マネージャーに、アプリ内で持続的でインタラクティブな一方向メッセージにより顧客とコミュニケーションできる強力な新しいチャネルを提供します。これらのメッセージはあらゆるコミュニケーションに利用できますが、プロモーションやトランザクションの目的で最も一般的に利用されています。
 
-Braze とセンドバードのインテグレーションでは、Braze ユーザー s は次の操作を実行できます。
-* Brazeのセグメンテーションとトリガー機能を活用して、アプリ 通知内のパーソナライズされたを開始します。
-* センドバード・通知のプラットフォームでアプリ 通知に合わせたSを作成し、アプリ内で配信し、ユーザー エンゲージメントを強化します。
+Braze と Sendbird の統合により、Braze のユーザーは次の操作を実行できます。
+* Braze のセグメンテーション機能とトリガー機能を使用して、パーソナライズされたアプリ内通知を開始します。
+* Sendbird Notifications プラットフォームで、アプリ環境内で配信されるカスタマイズされたアプリ内通知を作成し、ユーザーエンゲージメントを強化します。
 
-Brazeとセンドバード・通知の共同能力を活用することで、企業はカスタマーエンゲージメントを高め、効果的なアプリ 通知戦略を通じてコンバージョン率を高めることができる。
+Braze と Sendbird Notifications による共同の機能を利用することで、企業は効果的なアプリ内通知戦略によって顧客エンゲージメントを高め、コンバージョン率を向上させることができます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| センドバードのアカウント | センドバードの勘定は、この提携の前進タグeを考慮することが要求される。 |
-| センドバードUIKit | Sendbird UIKit を[iOS][2] または[Android][3] アプリにインストールしておく必要があります。 |
-| Braze REST API キー | `users.track` 権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
-| Braze REST エンドポイント | [Your REST エンドポイント URL][1].エンドポイントは、インスタンスのBraze URL によって異なります。 |
+| Sendbird アカウント | このパートナーシップを活用するには、Sendbird アカウントが必要です。 |
+| Sendbird UIKit | Sendbird UIKit を[iOS][2] または[Android][3] アプリにインストールしておく必要があります。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
+| Braze REST エンドポイント | [REST エンドポイント URL][1]。エンドポイントはインスタンスの Braze URL に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
 ![][13]
 
-Braze とSendbird Notification の統合により、カスタマーエンゲージメントを向上させ、優れたユーザーエクスペリエンスを提供するさまざまなユースケースが提供されます。
+Braze と Sendbird Notifications の統合により、顧客エンゲージメントを高め、優れたユーザーエクスペリエンスを提供するさまざまなユースケースが提供されます。
 
 - **マーケティング**:閲覧履歴やこれまでの購買履歴に基づく独占的な割引など、ユーザーの好みに合わせたパーソナライズされたなプロモーションや推薦で、ターゲットを絞ったキャンペーンを強化する。
-- **トランスアクションal**:発注ステータス、出荷内容、納期の見積もりなどの通知を含む、発注、納品、請求、支払いに関するリアルタイム更新を通じて、顧客通信を向上させる。
+- **トランザクション**:注文、配送、請求、支払いに関する最新情報 (注文状況、配送の詳細、予定配送時の通知など) をリアルタイムで提供して、顧客とのコミュニケーションを向上させます。
 
 ## 統合
 
 ### ステップ1:通知 テンプレートの作成
 
-[Sendbird テンプレート s][7] を使用すると、パーソナライズされた in-アプリ 通知 s をビルドしてチャネルごとに複数のs を使用して送信できます。テンプレートは、コードを書き込むことなく、センドバードダッシュボードで作成およびカスタマイズできます。
+[Sendbird テンプレート][7]により、複数のテンプレートを作成して各チャネルに使用することで、パーソナライズされたアプリ内通知を送信できます。テンプレートは Sendbird Dashboard で作成およびカスタマイズできます。この際、コーディングは不要です。
 
 ![][10]
 
-### ステップ2:センドバードダッシュボードでBrazeインテグレーションを設定する
+### ステップ2:Sendbird ダッシュボードで Braze 統合を設定する
 
-**Sendbird Dashboard**から、アプリのライケーションを選択し、**Notifications > Integrations**に移動し、**Add**を**Braze**セクションでクリックします。ここでは、Braze REST API キーとBraze REST エンドポイントが必要です。
+**Sendbird Dashboard**から、アプリのライケーションを選択し、**Notifications > Integrations**に移動し、**Add**を**Braze**セクションでクリックします。ここでは、Braze REST API キーと Braze REST エンドポイントが必要です。
 
 すべてのフィールドs を入力したら、**Save** をクリックして統合を完了し、統合エンドポイントs およびAPI トークンにアクセスします。
 
-### ステップ3:Sendbird 通知ビルダーのインストール
+### ステップ3:Sendbird Notification Builder をインストールする
 
-次に[Sendbird Notification Builder][6]をインストールする必要があります。このGoogle Chrome 拡張機能を使用すると、Braze ダッシュボードでSendbird 経由でカスタマイズした通知を送信できます。
+次に[Sendbird Notification Builder][6]をインストールする必要があります。この Google Chrome 拡張機能を使用すると、Braze ダッシュボードでカスタマイズした通知を Sendbird に送信できます。
 
 ![][12]
 
-#### センドバードの認証情報を拡張子に追加する
+#### 拡張機能に Sendbird 認証情報を追加する
 
-拡張機能がインストールされたら、ブラウザのツールバーのSendbirdアイコンをクリックし、**Settings**を選択します。ここでは、**Sendbird Notification Builder**にあるアプリ IDとAPI トークンを提供します。
+拡張機能がインストールされたら、ブラウザのツールバーのSendbirdアイコンをクリックし、**Settings**を選択します。ここでは、**Sendbird Notification Builder** にあるアプリ ID とAPI トークンを指定します。
 
-### ステップ4:センドバードのユーザー IDをBraze ユーザー IDにマップ
+### ステップ4:Sendbird のユーザー ID を Braze のユーザー ID にマッピングする
 
-Sendbird ユーザー IDは、使用するインテグレーションの[カスタム属性][5] としてBraze ユーザープロファイルに追加する必要があります。[ ユーザー import][8] ページから、CSVファイル s を使用してs をアップロードおよび更新 ユーザープロファイルできます。または、Braze ユーザー IDをセンドバードユーザー IDとして使用することもできます。
+Sendbird ユーザー IDは、使用するインテグレーションの[カスタム属性][5] としてBraze ユーザープロファイルに追加する必要があります。\[[User import][8]] ページから、CSV ファイルを使用してユーザープロファイルをアップロードおよび更新できます。あるいは Braze のユーザー ID を Sendbird のユーザー ID として使用できます。
 
 ### ステップ 5: Webhook テンプレートのセットアップ
 
@@ -72,10 +72,10 @@ Brazeでは、**Templates & Media**から**Webフックテンプレート**に
 {% raw %}
 1. テンプレートの名前を入力し、必要に応じてチームとタグを追加します。
 2. リアルタイムまたはバッチエンドポイントをSendbird ダッシュボードから**WebフックURL** にコピーします。
-3. **Receiver** フィールドで、<i class="fas fa-plus"></i> アイコンをクリックし、ユーザー 属性m アプリ ed をSendbird ユーザー IDに挿入します。
-    - `{{ '{{' }}custom_attribute.${sendbird_id}}}` カスタム属性`sendbird_id` をSendbird ユーザー IDとして使用している場合。
-    - `{{ '{{' }}${user_id}}}` Braze ユーザー ID をセンドバードユーザー IDとして使用している場合。
-4. **Settings**タブで、`SENDBIRD_API_TOKEN` をSendbird ダッシュボードの通知 s API トークンに置き換えます。
+3. \[**Receiver**] フィールドで <i class="fas fa-plus"></i>アイコンをクリックし、Sendbird のユーザー ID にマッピングされているユーザー属性を挿入します。
+    - カスタム属性 `sendbird_id` を Sendbird ユーザー ID として使用している場合は `{{ '{{' }}custom_attribute.${sendbird_id}}}`。
+    - Braze ユーザー ID を Sendbird ユーザー ID として使用している場合は `{{ '{{' }}${user_id}}}`。
+4. \[**設定**] タブで、`SENDBIRD_API_TOKEN` を Sendbird ダッシュボードの通知 API トークンに置き換えます。
 5. テンプレートを保存します。
 {% endraw %}
 
@@ -84,29 +84,29 @@ Brazeでは、**Templates & Media**から**Webフックテンプレート**に
 ### キャンペーン
 
 1. Braze ダッシュボードの**Campaigns**ページで、**Create Campaign**> **Webフック**をクリックします。
-2. 上記で作成したWebhook テンプレートを選択します。キャンペーン s には一括処理エンドポイントを使用することを強くお勧めします。
-3. **Compose**タブでテンプレートを編集してカスタマイズします。
+2. 上記で作成したWebhook テンプレートを選択します。キャンペーンにバッチエンドポイントを使用することを強くお勧めします。
+3. \[**作成**] タブでテンプレートの変数を編集して、テンプレートをカスタマイズします。
 
 ### Canvas
 
 1. 新規または既存のキャンバスから、**Message** コンポーネントを追加します。 
-2. コンポーネントを開き、**メッセージングチャネル**から**Webフック**を選択します。
+2. コンポーネントを開き、\[**メッセージングチャネル**] から \[**Webhook**] を選択します。
 3. 上記で作成したWebhook テンプレートを選択します。キャンバスのリアルタイムエンドポイントを使用することを強くお勧めします。
-4. **Compose**タブでテンプレートを編集してカスタマイズします。
+4. \[**作成**] タブでテンプレートの変数を編集して、テンプレートをカスタマイズします。
 
 ## カスタマイズ
 
-### 配信と開封 ステータスの追跡
+### 配信ステータスと開封ステータスを追跡する
 
 通知の配信および開封 ステータスの行動をキャンペーンのコンバージョンメトリクスと統合するには、Braze ダッシュボードにカスタムイベントを追加します。
 
-1. Braze ダッシュボードから、**Settings > Manage Settings > Custom Events** に移動し、**\+ Add Custom Event** をクリックします。
+1. Braze ダッシュボードから **\[設定] > \[設定の管理] > \[カスタムイベント]** に移動し、\[**\+ カスタムイベントを追加**] をクリックします。
 2. カスタムイベントを作成したら、**プロパティの管理**をクリックし、プロパティの種類として"ステータス"を選択し、"String"を選択します。
-3. キャンペーン s またはキャンバスで通知を作成する場合は、**イベント名** フィールドにカスタムイベントの名前を入力します。
+3. キャンペーンまたはキャンバスで通知を作成する場合は、\[**イベント名**] フィールドにカスタムイベントの名前を入力します。
 
-このカスタムイベントは、通知ごと、メッセージが送信されたとき、およびユーザー 開封がメッセージを送信したときに、2回トリガーされます。
+このカスタムイベントは、通知ごとに2回 (メッセージが送信された時点と、ユーザーがメッセージを開封した時点) トリガーされます。
 - メッセージが送信されると、カスタムイベントが`SENT` ステータスでトリガーされます。
-- メッセージが読み込まれると、カスタムイベントはトリガー`READ` ステータスで表示されます。
+- メッセージが読まれると、カスタムイベントが `READ` ステータスでトリガーされます。
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
 [2]: https://sendbird.com/docs/notifications/v1/uikit/ios/install-uikit
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/mobile_wallet/passkit.md b/_lang/ja/_partners/message_orchestration/additional_channels/mobile_wallet/passkit.md
index b5964b65fcf..c54ec9f528b 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/mobile_wallet/passkit.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/mobile_wallet/passkit.md
@@ -1,72 +1,72 @@
 ---
-nav_title: パスキット
-article_title: パスキット
+nav_title: PassKit
+article_title: PassKit
 alias: /partners/passkit/
-description: "この参考記事では、ブレイズとパスキットのパートナーシップについて概説している。この提携により、アップルウォレットとグーグルペイを顧客体験に統合することで、モバイル・リーチを拡大することができる。"
+description: "このリファレンス記事では、Brazeと Passkit のパートナーシップについて説明します。このパートナーシップにより、Apple ウォレットと Google Pay のパスをカスタマーエクスペリエンスに統合してモバイルリーチを拡大できます。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# パスキット
+# PassKit
 
-> PassKitは、Apple WalletやGoogle Payのパスを顧客体験に統合することで、モバイル・リーチを拡大することを可能にする。デジタルクーポン、ポイントカード、会員カード、チケットなどの作成、管理、配布、パフォーマンス分析が簡単にできる。
+> PassKit は Apple ウォレットと Google Pay のパスをカスタマーエクスペリエンスに統合するモバイルリーチの拡大を支援しています。デジタルクーポン、ロイヤルティカード、会員カード、チケットなどの作成、管理、配布、パフォーマンス分析を簡単に行うことができ、顧客は他のアプリを使用する必要がなくなります。
 
-BrazeとPassKitの統合により、Apple WalletとGoogle Payのカスタムパスを即座に配信することで、オンラインキャンペーンのエンゲージメントを高め、測定することができる。その後、利用状況を分析し、顧客のモバイル・ウォレットに位置情報ベースのメッセージやパーソナライズされた動的な更新をトリガーすることで、店舗でのトラフィックを増やすためのリアルタイム調整を行うことができる。 
+Braze と PassKit の統合により、Apple ウォレットと Google Pay のカスタムパスを即時に配信して、オンラインキャンペーンのエンゲージメントを高め、このエンゲージメントを測定できます。その後、利用状況を分析し、リアルタイムに調整することで、顧客のモバイルウォレットに位置情報に基づくメッセージやパーソナライズされたダイナミックな最新情報を送信し、ストア内のトラフィックを増加させることができます。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| PassKitアカウント | PassKitアカウントとPassKitアカウントマネージャーが必要である。 |
-| `userDefinedID` | PassKitとBrazeの間でユーザーへのカスタムイベントやカスタム属性を適切に更新するには、Brazeの外部IDを`userDefinedID` 。この`userDefinedID` 、PassKitエンドポイントにAPIコールを行う際に使用される。 |
+| PassKitアカウント | PassKit アカウントと PassKit アカウントマネージャーが必要です。 |
+| `userDefinedID` | PassKit と Braze の間でユーザーに対しカスタムイベントとカスタム属性を適切に更新するには、Braze external ID を`userDefinedID` として設定する必要があります。この`userDefinedID` は、PassKit エンドポイントに対する API 呼び出しの実行時に使用されます。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは、\[インスタンスのBraze URL][6] に依存する。 |
+| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは\[インスタンスの Braze URL][6] に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合
 
-顧客のモバイルウォレット体験をさらに豊かにするために、PassKitダッシュボードから、Brazeの\[`/users/track` エンドポイント][7]]を通じてBrazeにデータを渡すことができる。 
+顧客のモバイルウォレット体験をさらに充実させるために、PassKit ダッシュボード内から Brazeの \[`/users/track` エンドポイント][7]を介してデータを Braze に渡すことを選択できます。 
 
-PassKitから共有されるデータの例には以下が含まれる：
-- **パスの作成**：顧客がパスのリンクをクリックし、最初にパスが表示されたとき。
-- **パスのインストール**：顧客がウォレットアプリにパスを追加し、保存**する**。
-- **パスの更新**：パスが更新されたとき。
-- **パスの削除**：顧客がウォレットアプリからパスを削除した場合。
+PassKit から共有するデータの例を以下に示します。
+- **Pass created**: 顧客がパスリンクをクリックして、パスが最初に表示される時点。
+- **Pass installs**: 顧客がパスを追加し、自分のウォレットアプリに保存する時点。
+- **Pass updates**: パスが更新される時点。
+- **Pass delete**: 顧客がウォレットアプリからパスを削除する時点。
 
 データがBrazeに渡されると、オーディエンスを構築し、Liquidでコンテンツをパーソナライズし、これらのアクションが実行された後にキャンペーンやCanvasesをトリガーすることができる。
 
-## パスキットとブレイズを接続する
+## Passkit を Braze に接続する
 
-PassKitからデータを渡すには、Brazeの外部IDをPassKitの`externalId` 。
+PassKit からデータを渡すには、Braze external ID を PassKit の`externalId` として設定していることを確認します。
 
-1. **設定**内のPassKit passプロジェクトまたはプログラムの**Integrationsで**、**Braze**タブの**Connectを**クリックする。<br>![PassKitプラットフォームのBraze統合タイル。][5]{: style="max-width:80%"}<br><br>
-2. Braze APIキー、エンドポイントURLを入力し、コネクタの名前を入力する。<br><br>
-3. **Enable Integration（統合を有効にする**）をトグルし、Brazeでメッセージをトリガーまたはパーソナライズしたいイベントを選択する。<br>![PassKit Braze統合タイルが拡張され、APIキー、エンドポイントURL、統合名、有効化設定、会員設定、パス設定を受け付ける。][4]{: style="max-width:70%"}
+1. PassKit パスプロジェクトまたはプログラムの \[**Settings**] の \[**Integrations**] で、\[**Braze**] タブの \[**Connect**] をクリックします。<br>![PassKitプラットフォームのBraze統合タイル。][5]{: style="max-width:80%"}<br><br>
+2. Braze API キーとエンドポイント URL を入力し、コネクターの名前を入力します。<br><br>
+3. **Enable Integration（統合を有効にする**）をトグルし、Brazeでメッセージをトリガーまたはパーソナライズしたいイベントを選択する。<br>![API キー、エンドポイント URL、統合名、有効化設定、メンバーシップ設定、およびパス設定を受け入れるために展開されている PassKit Braze 統合タイル。][4]{: style="max-width:70%"}
 
-## スマートパスリンクを使ってパスを作成する
+## SmartPass リンクを使用してパスを作成する
 
-Braze内では、スマートパスリンクを設定し、顧客がAndroidまたはiOSのいずれかにパスをインストールするための固有のURLを生成することができる。そのためには、Brazeコンテンツブロックから呼び出せる暗号化されたSmartPassデータペイロードを定義する必要がある。この\[コンテンツ・ブロック][9] ]は、将来のパスやクーポンに再利用できる。以下は、統合の際に使用される：
+Braze では、SmartPass リンクを設定して、顧客が Android またはiOS にパスをインストールするための一意のURL を生成するようにできます。そのためには、Brazeコンテンツブロックから呼び出せる暗号化されたSmartPassデータペイロードを定義する必要がある。この\[コンテンツブロック][9]は、今後のパスやクーポンに再利用できます。以下は、統合の際に使用される：
 
-- **PassKitのURL**：PassKitのURLは、PassKitプログラムに固有のURLである。<br>各プログラムには固有のURLがあり、PassKitプログラムまたはプロジェクトの「**Distribution」**タブで見つけることができる。(例えば、https://pub1.pskt.io/c/ww0jir ）<br><br>
-- **PassKitの秘密**だ：URLと一緒に、このプログラムのPassKit Keyも手元に用意しておく必要がある。<br>これはPassKitのURLと同じページに記載されている。<br><br>
-- **プログラム（またはプロジェクト）ID**：スマートパスのURLを作成するには、PassKitプログラムIDが必要となる。<br>プロジェクトやプログラムの**"Settings "**タブにある。
+- **PassKit URL**:PassKit URL は、PassKit プログラムの一意のURL です。<br>各プログラムには固有のURLがあり、PassKitプログラムまたはプロジェクトの「**Distribution」**タブで見つけることができる。(例えば、https://pub1.pskt.io/c/ww0jir ）<br><br>
+- **PassKit シークレット**:URL に加えて、このプログラムの PassKit キーが必要です。<br>これは PassKit URL と同じページで確認できます。<br><br>
+- **プログラム (またはプロジェクト) ID**:SmartPass URL を作成するには、PassKit プログラム IDが必要です。<br>プロジェクトやプログラムの**"Settings "**タブにある。
 
 暗号化されたスマートパス・リンクの作成に関する詳細は、こちらの\[PassKitの記事][8] 。
 
-### ステップ1:パスデータのペイロードを定義する {#passkit-integrations}
+### ステップ1:パスデータペイロードを定義する {#passkit-integrations}
 
-まず、クーポンやメンバーのペイロードを定義しなければならない。 
+まず、クーポンまたはメンバーのペイロードを定義する必要があります。 
 
-ペイロードに含めることができるコンポーネントは多岐にわたるが、ここでは2つの重要なコンポーネントを紹介する：
+ペイロードにはさまざまな構成要素を含めることができますが、ここでは2つの重要な構成要素を示します。
 
-| コンポーネント | 必須 | タイプ | 説明 |
+| 構成要素 | 必須 | タイプ | 説明 |
 | --------- | -------- | ---- | ----------- |
-|`person.externalId` | 必須 | String | Brazeの外部IDとして設定され、PassKitからBrazeへのコールバックが機能するために重要であり、Brazeユーザーは1つのキャンペーンで複数のオファーのクーポンを持つことができる。ユニークなものとして施行されていない。 |
-| `members.member.externalId` | オプション | String | Brazeの外部IDとして設定し、外部IDを使用して会員パスを更新することができる。このフィールドを設定することで、会員プログラム内でユーザーが一意であることが強制される。|
+|`person.externalId` | 必須 | String | Brazeの外部IDとして設定され、PassKitからBrazeへのコールバックが機能するために重要であり、Brazeユーザーは1つのキャンペーンで複数のオファーのクーポンを持つことができる。一意であることは必須ではありません。 |
+| `members.member.externalId` | オプション | String | Braze external ID として設定します。external ID を使用してメンバーシップパスを更新できます。このフィールドを設定することで、メンバーシッププログラム内でユーザーが一意になります。|
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
-利用可能なフィールドの完全なリストとそのタイプ、役に立つ説明については、\[PassKit GitHub documentation][10] を見てほしい。
+使用可能なすべてのフィールドとそのタイプ、役立つ説明については、\[PassKit GitHub のドキュメント][10]を参照してください。
 
 #### ペイロードの例
 {% raw %}
@@ -84,17 +84,17 @@ Braze内では、スマートパスリンクを設定し、顧客がAndroidま
 
 ### ステップ2:未定義のペイロード変数を作成し、エンコードする
 
-Brazeダッシュボードの**Templates**>**Content Blocksに**移動して、新しいコンテンツブロックを作成し、名前を付ける。
+Braze ダッシュボード内の \[**テンプレート**] > \[**コンテンツブロック**] に移動して、新しいコンテンツブロックを作成し、名前を付けます。
 
 {% alert note %}
 [旧式のナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**エンゲージメント**」＞「**テンプレート＆メディア**」＞「**コンテンツ・ブロック・ライブラリ**」と進む。
 {% endalert %}
 
-**コンテンツ・ブロックの作成**」を選択して開始する。
+\[**コンテンツブロックを作成**] を選択して開始します。
 
-次に、**コンテンツブロックのリキッドタグを**定義しなければならない。このコンテンツブロックを保存した後、このリキッドタグはメッセージを作成するときに参照できる。この例では、リキッドタグを{% raw %}`{{content_blocks.${passKit_SmartPass_url}}}`{% endraw %} として割り当てている。 
+次に、**コンテンツブロックの Liquid タグ**を定義します。このコンテンツブロックを保存したら、メッセージを作成するときにこの Liquid タグを参照できます。この例では、リキッドタグを{% raw %}`{{content_blocks.${passKit_SmartPass_url}}}`{% endraw %} として割り当てている。 
 
-このコンテンツ・ブロック内では、ペイロードを直接含めず、{% raw %}`{{passData}}`{% endraw %} 変数で参照する。コンテンツ・ブロックに追加しなければならない最初のコード・スニペットは、{% raw %}`{{passData}}`{% endraw %} 変数の Base64 エンコードをキャプチャする。
+このコンテンツブロック内では、ペイロードを直接含めませんが、{% raw %}`{{passData}}`{% endraw %} 変数でペイロードを参照します。コンテンツ・ブロックに追加しなければならない最初のコード・スニペットは、{% raw %}`{{passData}}`{% endraw %} 変数の Base64 エンコードをキャプチャする。
 {% raw %}
 ```liquid
 {% capture base64JsonPayload %}{{passDatapassData|base64_encode}}{% endcapture %}
@@ -112,7 +112,7 @@ Brazeダッシュボードの**Templates**>**Content Blocksに**移動して、
 ```
 {% endraw %}
 
-次に、このハッシュと`Project Secret` を使って署名を生成する必要がある。これは、3つ目のコード・スニペットを含めることで可能になる：
+次に、このハッシュと `Project Secret` を使用して署名を生成する必要があります。これは、3つ目のコード・スニペットを含めることで可能になる：
 {% raw %}
 ```liquid
 {% capture sig %}{{url | hmac_sha1: "Project_Secret"}}{% endcapture %}
@@ -128,14 +128,14 @@ Brazeダッシュボードの**Templates**>**Content Blocksに**移動して、
 
 ### ステップ4:URLを印刷する
 
-最後に、最終的なURLを呼び出し、メッセージ内にスマートパスのURLが表示されるようにする。
+最後に、最終的な URL を呼び出すことを確認します。これにより、メッセージ内に SmartPass URL が出力されます。
 {% raw %}
 ```liquid
 {{longURL}}
 ```
 {% endraw %}
 
-この時点で、あなたは次のようなコンテンツ・ブロックを作成したことになる：
+この時点で、以下のようなコンテンツブロックが作成されます。
 
 {% raw %}
 ```liquid
@@ -151,44 +151,44 @@ Brazeダッシュボードの**Templates**>**Content Blocksに**移動して、
 ```
 {% endraw %}
 
-この例では、インストール元をBrazeとこのキャンペーンまで追跡するためにUTMパラメータが追加されている。
+この例では、これらのインストールのソースを Braze とこのキャンペーンまで追跡するために、UTM パラメーターが追加されています。
 
 {% alert tip %}
-ページを離れる前に、コンテンツ・ブロックを保存することを忘れないこと。
+ページを離れる前に、コンテンツブロックを必ず保存してください。
 {% endalert %}
 
 ### ステップ 5: すべてをまとめる
 
-このコンテンツ・ブロックは、一度作成されれば、今後も再利用することができる。 
+このコンテンツブロックが作成されたら、今後再利用できます。 
 
 コンテンツ・ブロックの例では、2つの変数が未定義のままになっていることにお気づきだろうか。<br> 
-{% raw %}`{{passData}}`{% endraw %} [- ステップ](#passkit-integrations)1で定義したJSONパス・データのペイロード<br>
-{% raw %}`{{projectUrl}}`{% endraw %} - Passkitプロジェクトのディストリビューション・タブにある、プロジェクトまたはプログラムのURL。
+{% raw %}`{{passData}}`{% endraw %} - [ステップ1](#passkit-integrations)で定義した JSON パスデータのペイロード<br>
+{% raw %}`{{projectUrl}}`{% endraw %} - Passkit プロジェクトの配布タブにあるプロジェクトまたはプログラムの URL。
 
-この決定は意図的なものであり、コンテンツ・ブロックの再利用性をサポートするものである。これらの変数は参照されるだけで、コンテンツ・ブロック内で作成されるわけではないので、コンテンツ・ブロックを作り直すことなく、これらの変数を変更することができる。 
+これは意図的な決定であり、コンテンツブロックの再利用性がサポートされます。これらの変数は参照されるだけで、コンテンツ・ブロック内で作成されるわけではないので、コンテンツ・ブロックを作り直すことなく、これらの変数を変更することができる。 
 
-例えば、ロイヤリティ・プログラムの初期ポイントを増やすために、紹介オファーを変更したいかもしれないし、二次的なメンバー・カードやクーポンを作りたいかもしれない。これらのシナリオでは、異なるPasskit`projectURLs` 、または異なるパスペイロードが必要となり、Brazeでキャンペーンごとに定義することになる。  
+たとえば、紹介オファーを変更して、ロイヤルティプログラムに初回ポイントを追加したり、セカンダリメンバーカードやクーポンを作成したりすることがあります。これらのシナリオでは必要な Passkit `projectURLs` またはパスペイロードが異なる可能性があります。これらは Braze でキャンペーンごとに定義します。  
 
 #### メッセージ本文を作成する
 
-この2つの変数をメッセージ・ボディに取り込み、コンテンツ・ブロックを呼び出す。
-[ステップ](#passkit-integrations)1で最小化したJSONペイロードをキャプチャする：
+この2つの変数をメッセージ本文に取り込んでから、コンテンツブロックを呼び出すことができます。
+[ステップ1](#passkit-integrations)のミニファイ化された JSON ペイロードをキャプチャします。
 
-**プロジェクトのURLを割り当てる**
+**プロジェクト URL を割り当てる**
 {% raw %}
 ```liquid
 {% assign projectUrl = "https://pub1.pskt.io/c/ww0jir" %}
 ```
 {% endraw %}
 
-**JSONをキャプチャする**
+**JSON をキャプチャする**
 {% raw %}
 ```liquid
 {% capture passData %}{"members.member.externalId": "{{${user_id}}}","members.member.points": "100","members.tier.name": "current_customer","person.displayName": "{{${first_name}}} {{${last_name}}}","person.externalId": "{{${user_id}}}","universal.expiryDate": "{{ "now" | date: "%s" | plus: 31622400 | date: "%FT%TZ" }}"}{% endcapture %}
 ```
 {% endraw %}
 
-**先ほど作成したコンテンツ・ブロックを参照する**
+**先ほど作成したコンテンツブロックを参照する**
 {% raw %}
 ```liquid
 {{content_block.${passkit_SmartPass_url}}}
@@ -196,19 +196,19 @@ Brazeダッシュボードの**Templates**>**Content Blocksに**移動して、
 {% endraw %}
 
 メッセージ本文は次のようなものだ：
-![キャプチャされたJSONとコンテンツ・ブロック・リファレンスが表示されたコンテンツ・ブロック・メッセージ・コンポーザーの画像。][1]{: style="max-width:70%"}
+![キャプチャされた JSON およびコンテンツブロック参照を含むコンテンツブロックメッセージ作成画面。][1]{: style="max-width:70%"}
 
 サンプルの出力URLは以下の通りだ：
-![ランダムに生成された文字と数字の長い文字列を含む出力URL。][2]{: style="max-width:70%"}
+![ランダムに生成された文字と数字からなる長い文字列を含む出力 URL。][2]{: style="max-width:70%"}
 
-出力URLは長くなる。その理由は、パスデータがすべて含まれており、データの完全性とURL変更による改ざんを確実にするために、クラス最高のセキュリティが組み込まれているからだ。SMSを使ってこのURLを配布する場合は、\[bit.ly][3].これは、bit.ly エンドポイントへのコネクテッド・コンテンツ・コールを通じて行うことができる。
+出力URLは長くなる。その理由は、パスデータがすべて含まれており、データの完全性とURL変更による改ざんを確実にするために、クラス最高のセキュリティが組み込まれているからだ。SMS を使用してこのURL を配布する場合は、\[bit.ly][3] のようなリンク短縮プロセスで実行することができます。これは、bit.ly エンドポイントへのコネクテッドコンテンツ呼び出しを使用して行うことができます。
 
-## PassKitウェブフックを使用してパスを更新する
+## PassKit Webhook を使用してパスを更新する
 
-Brazeでは、WebhookキャンペーンやCanvas内のWebhookを設定して、ユーザーの行動に基づいて既存のパスを更新することができる。便利なPassKitエンドポイントについては、以下のリンクをチェックしてほしい。 
+Brazeでは、WebhookキャンペーンやCanvas内のWebhookを設定して、ユーザーの行動に基づいて既存のパスを更新することができる。有用な PassKit エンドポイントについては、次のリンクを参照してください。 
 - \[メンバープロジェクト][12]
-- \[クーポン企画][13]
-- \[フライト・プロジェクト][14]
+- \[クーポンプロジェクト][13]
+- \[フライトプロジェクト][14]
 
 ### ペイロードパラメーター
 
@@ -216,9 +216,9 @@ Brazeでは、WebhookキャンペーンやCanvas内のWebhookを設定して、
 
 | データ | タイプ | 説明 |
 | ---- | ---- | ----------- |
-| `externalId` | String | 一意の顧客識別子（会員番号など）を使用する既存のシステムとの互換性を提供するために、パスレコードに一意のIDを追加できるようにする。このエンドポイントを使えば、パスIDの代わりに`userDefinedId` 、`campaignName` 。この値はキャンペーン内で一意でなければならず、設定後は変更できない。<br><br>Brazeとの統合には、Brazeの外部IDを使用することをお勧めする： {% raw %}`{{${user_id}}}`{% endraw %} |
-| `campaignId` (クーポン） <br><br> `programId` (会員制） | String | PassKitで作成したキャンペーンまたはプログラムテンプレートのID。これを見つけるには、PassKitパス・プロジェクトの**Settings**タブに向かう。 |
-| `expiryDate` | IO8601 datetime | パスの有効期限。有効期限を過ぎると、パスは自動的に無効となる（`isVoided` を参照）。この値はテンプレートとキャンペーン終了日の値を上書きする。 |
+| `externalId` | String | 一意の顧客識別子 (メンバーシップ番号など) を使用する既存のシステムとの互換性を得るために、パスレコードに一意の ID を追加できるようにします。このエンドポイントを使用して、パス ID ではなく `userDefinedId` と `campaignName` でパスデータを取得できます。この値はキャンペーン内で一意でなければならず、設定後は変更できない。<br><br>Braze 統合では、Braze external ID {% raw %}`{{${user_id}}}`{% endraw %} を使用することをお勧めします。 |
+| `campaignId` (クーポン) <br><br> `programId` (メンバーシップ) | String | PassKitで作成したキャンペーンまたはプログラムテンプレートのID。これを確認するには、PassKit パスプロジェクトの \[**Settings**] タブに移動します。 |
+| `expiryDate` | ISO8601 日時 | パスの有効期限。この有効期限を過ぎると、パスは自動的に無効になります (`isVoided` を参照)。この値はテンプレートとキャンペーン終了日の値を上書きする。 |
 | `status` | String | `REDEEMED` や`UNREDEEMED` など、クーポンの現在のステータス。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
@@ -227,17 +227,17 @@ Brazeでは、WebhookキャンペーンやCanvas内のWebhookを設定して、
 今後のキャンペーンやCanvasで使用するPassKitウェブフックテンプレートを作成するには、Brazeダッシュボードの「**テンプレート＆メディア」**セクションに移動する。単発のPassKitウェブフックキャンペーンを作成する場合、または既存のテンプレートを使用する場合は、新しいキャンペーンを作成する際にBrazeで**ウェブフックを**選択する。
 
 PassKitウェブフック・テンプレートを選択すると、以下のように表示される：
-- **ウェブフックのURL**： `https://api-pub1.passkit.io/coupon/singleUse/coupon`
-- **リクエスト・ボディ**Raw Text
+- **Webhook URL**: `https://api-pub1.passkit.io/coupon/singleUse/coupon`
+- **リクエスト本文**:Raw Text
 
 #### リクエストヘッダと方法
 
-PassKitの認証には、Base64でエンコードされたPassKit APIキーを含む`HTTP Header` 。以下はすでにキーと値のペアとしてテンプレートに含まれているが、**Settings**タブでは、`<PASSKIT_LONG_LIVED_TOKEN>` をあなたのPassKitトークンに置き換える必要がある。トークンを取得するには、PassKitプロジェクト/プログラムに移動し、**「設定」>「統合」>「Long Lived Token**」の順に移動する。
+PassKit の認証には、Base64 でエンコードされた PassKit API キーを含む `HTTP Header` が必要です。以下はすでにキーと値のペアとしてテンプレートに含まれているが、**Settings**タブでは、`<PASSKIT_LONG_LIVED_TOKEN>` をあなたのPassKitトークンに置き換える必要がある。トークンを取得するには、PassKit プロジェクト/プログラムに移動し、**\[Settings] > \[Integrations] > \[Long Lived Token]** に移動します。
 
 {% raw %}
-- **HTTPメソッド**：プット
-- **ヘッダーをリクエストする**：
-  - **認可する**：ベアラー `<PASSKIT_LONG_LIVED_TOKEN>`
+- **HTTPメソッド**：PUT:
+- **リクエストヘッダー**:
+  - **Authorization**:ベアラー `<PASSKIT_LONG_LIVED_TOKEN>`
   - **Content-Type**: application/json
 {% endraw %}
 
@@ -263,11 +263,11 @@ Webhookをセットアップするには、リクエストボディに新しい
 ページを離れる前にテンプレートを保存することを忘れないこと！<br>更新されたWebhookテンプレートは、新しい[Webhookキャンペーンを]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/)作成するときに、**保存されたWebhookテンプレート**リストで見つけることができる。
 {% endalert %}
 
-## コネクテッド・コンテンツでパスの詳細を取得する
+## コネクテッドコンテンツからパスの詳細を取得する
 
-パスの作成と更新に加え、Brazeの\[Connected Content][15] ] を介してユーザーのパスメタデータを取得し、メッセージングキャンペーンにパーソナライズされたパスの詳細を組み込むこともできる。
+パスの作成と更新に加えて、Braze の\[コネクテッドコンテンツ][15]を介してユーザーのパスメタデータを取得し、メッセージングキャンペーン内にパーソナライズされたパスの詳細を組み込むこともできます。
 
-**PassKitコネクテッド・コンテンツ・コール**
+**PassKit コネクテッドコンテンツ呼び出し**
 
 {% raw %}
 ```liquid
@@ -277,7 +277,7 @@ Webhookをセットアップするには、リクエストボディに新しい
 ```
 {% endraw %}
 
-**液体の回答例**
+**Liquid の応答の例**
 
 {% tabs local %}
 {% tab {{passes.redemptionDetails}} %}
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting.md b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting.md
index 4b7c8e857d8..eb0e2433050 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting.md
@@ -1,10 +1,10 @@
 ---
 nav_title: リターゲティング
-article_title: リターゲティング・パートナー
+article_title: リターゲティングのパートナー
 page_order: 2
 
 page_type: landing
-description: "このランディングページには、Brazeのパートナー（合金）のリストがあり、これらのパートナーからの知識に基づいてリターゲティングメッセージを送ることができる。"
+description: "このランディングページには、各パートナーの知識に基づいてメッセージングのリターゲティングができるようにする Braze パートナー (Alloys) が一覧表示されています。"
 
 layout: partner_page
 search_tag: Partner
@@ -14,9 +14,9 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Retargeting"
 
 valid_partner_list:
-- name: ジャムップ
+- name: Jampp
   url: /docs/partners/message_orchestration/additional_channels/retargeting/jampp/
-- name: リマージ
+- name: Remerge
   url: /docs/partners/message_orchestration/additional_channels/retargeting/remerge/
 - name: Facebook
   url: /docs/partners/message_orchestration/additional_channels/retargeting/facebook/
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/facebook.md b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/facebook.md
index 8533cec74c2..9cd9dac8756 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/facebook.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/facebook.md
@@ -10,12 +10,12 @@ search_tag: Partner
 
 # Facebookオーディエンス・エクスポート
 
-> BrazeとFacebookの統合により、手動でBrazeのセグメントをFacebookにエクスポートし、Facebookカスタムオーディエンスを作成することができる。これは1回限りの静的オーディエンスエクスポートであり、新しいFacebookカスタムオーディエンスのみを作成する。
+> BrazeとFacebookの統合により、手動でBrazeのセグメントをFacebookにエクスポートし、Facebookカスタムオーディエンスを作成することができる。これは1回限りの静的オーディエンスエクスポートであり、新しい Facebook カスタムオーディエンスのみが作成されます。
 
 Facebookカスタムオーディエンスをエクスポートする一般的なユースケースには、以下のようなものがある：
 - ライフサイクル内の特定のポイントでユーザーをリターゲティングする
 - 除外ターゲットリストの作成
-- [Lookalikeオーディエンスを][4]作成し、新規ユーザーをより効率的に獲得する
+- 新規ユーザーをより効率的に獲得するための[類似オーディエンス][4]を作成する
 <br><br>
 
 {% alert note %}
@@ -24,42 +24,42 @@ Facebookオーディエンス・エクスポートは、**ユーザー・アク
 {% endalert %}
 
 {% alert note %}
-ベータ版のメタ・ワーク・アカウントのテストに参加している場合は、アカウントを[フェイスブックのパートナー・]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync#step-1-connect-to-facebook)ページに切断し、再接続することを確認すること。
+ベータ版の Meta ワークアカウントのテストに参加している場合は、アカウントを接続解除してから[Facebook パートナーページ]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync#step-1-connect-to-facebook)に再接続してください。
 {% endalert %}
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| [フェイスブック・ビジネス・マネージャー][1] | ブランドのFacebook資産（広告アカウント、ページ、アプリなど）を一元管理するツール。 |
-| [フェイスブック広告アカウント][2] | Brazeカスタムオーディエンスで使用したい、ブランドのビジネスマネージャーに紐づくアクティブなFacebook広告アカウント。<br><br>Facebookビジネスマネージャー管理者が、Brazeで使用する予定のFacebook広告アカウントの管理者権限を付与していること、および広告アカウントの利用規約に同意していることを確認する。そうしないと、Braze内でFacebook広告アカウントにアクセスできなくなる。 |
-| [Facebookカスタムオーディエンス規約][3]| Brazeで使用する予定のFacebook広告アカウントについて、Facebookのカスタムオーディエンス規約に同意すること。|
+| [Facebook Business Manager][1] | ブランドのFacebook資産（広告アカウント、ページ、アプリなど）を一元管理するツール。 |
+| [Facebook 広告アカウント][2] | Brazeカスタムオーディエンスで使用したい、ブランドのビジネスマネージャーに紐づくアクティブなFacebook広告アカウント。<br><br>Facebookビジネスマネージャー管理者が、Brazeで使用する予定のFacebook広告アカウントの管理者権限を付与していること、および広告アカウントの利用規約に同意していることを確認する。そうしないと、Braze内でFacebook広告アカウントにアクセスできなくなる。 |
+| [Facebook カスタムオーディエンス利用規約][3]| Brazeで使用する予定のFacebook広告アカウントについて、Facebookのカスタムオーディエンス規約に同意すること。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### ステップ1:フェイスブックに接続する
+### ステップ1:Facebook に接続する
 
-1. Brazeのダッシュボードで、**Partner Integrations**>**Technology Partnersと**進み、**Facebookを**選択する。 
+1. Braze ダッシュボードで \[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Facebook**] を選択します。 
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
 {: start="2"}
-2\.Facebook Audience Exportモジュールで、**Connect Facebookを**クリックする。<br><br>![BrazeプラットフォームのFacebookテクノロジーパートナーのページ。][6]{: style="max-width:70%;"}
+2\.Facebook Audience Export (Facebook オーディエンスエクスポート) モジュールで、\[**Facebook に接続**] をクリックします。<br><br>![BrazeプラットフォームのFacebookテクノロジーパートナーのページ。][6]{: style="max-width:70%;"}
 
 {: start="3"}
-3\.Facebook oAuthダイアログウィンドウで、BrazeがFacebook広告アカウントにカスタムオーディエンスを作成することを承認する。<br><br>![最初のフェイスブックのダイアログボックスで、"Connect as X"（Xはフェイスブックのユーザー名）と促される。][8]{: style="max-width:30%;"} ![広告アカウントの広告を管理する許可を求める2つ目のFacebookのダイアログボックス。][7]{: style="max-width:40%;"}
+3\.Facebook oAuthダイアログウィンドウで、BrazeがFacebook広告アカウントにカスタムオーディエンスを作成することを承認する。<br><br>![最初の Facebook ダイアログボックス。\[Connect as X] (X は Facebook ユーザー名) で接続するように促される。][8]{: style="max-width:30%;"} ![広告アカウントの広告を管理する許可を求める2つ目のFacebookのダイアログボックス。][7]{: style="max-width:40%;"}
 
 {: start="4"}
-4\.BrazeがFacebookアカウントとリンクされたら、Brazeワークスペース内で同期したい広告アカウントを選択する。<br><br>![Facebookに接続可能な広告アカウントのリスト。][9]{: style="max-width:70%;"}<br><br> 接続後、パートナーページに戻り、どのアカウントが接続されているかを確認したり、既存のアカウントを切断したりできる。<br><br> ![フェイスブックのテクノロジー・パートナーのページが更新され、広告アカウントの接続に成功したことが示されている。][10]{: style="max-width:70%;"}<br>
-<br> Facebookとの接続は、Brazeのワークスペース・レベルで適用される。Facebook管理者があなたをFacebookビジネスマネージャーから削除したり、接続しているFacebookアカウントへのアクセスを削除した場合、Brazeは無効なトークンを検出する。その結果、Facebookオーディエンスステップを使用しているアクティブなCanvasesはエラーが表示され、Brazeはユーザーを同期できなくなる。 
+4\.BrazeがFacebookアカウントとリンクされたら、Brazeワークスペース内で同期したい広告アカウントを選択する。<br><br>![Facebookに接続可能な広告アカウントのリスト。][9]{: style="max-width:70%;"}<br><br> 接続後にパートナーページが再び表示され、どのアカウントが接続されているかを確認したり、既存のアカウントを切断したりできます。<br><br> ![広告アカウントが接続されたことを示す更新後の Facebook テクノロジーパートナーページ。][10]{: style="max-width:70%;"}<br>
+<br> Facebookとの接続は、Brazeのワークスペース・レベルで適用される。Facebook管理者があなたをFacebookビジネスマネージャーから削除したり、接続しているFacebookアカウントへのアクセスを削除した場合、Brazeは無効なトークンを検出する。そのため、Facebook オーディエンスステップを使用しているアクティブなキャンバスにはエラーが表示され、Braze はユーザーを同期できません。 
 
 {% alert important %}
-過去に[広告管理](https://developers.facebook.com/docs/facebook-login/permissions/#reference-ads_management)および[広告管理スタンダード](https://developers.facebook.com/docs/marketing-api/access#standard)アクセスのFacebookアプリ審査プロセスを受けたことがあるお客様については、システムユーザートークンはFacebookオーディエンスステップでも有効である。Facebookのパートナー・ページを通じて、Facebookシステムのユーザートークンを編集したり、取り消したりすることはできない。Brazeワークスペース内でFacebookシステムユーザートークンを置き換えるために、Facebookアカウントを接続することができる。 
+これまでに [Ads Management](https://developers.facebook.com/docs/facebook-login/permissions/#reference-ads_management) および [Ads Management Standard Access](https://developers.facebook.com/docs/marketing-api/access#standard) の Facebook アプリレビュープロセスを受けたことがある顧客のシステムユーザートークンは、Facebook オーディエンスコンポーネントに対して引き続き有効です。Facebookのパートナー・ページを通じて、Facebookシステムのユーザートークンを編集したり、取り消したりすることはできない。代わりに Facebook アカウントを接続して、Braze ワークスペース内の Facebook システムユーザートークンを置き換えることができます。 
 
-<br><br>新しいFacebook oAuth設定は、[セグメントを介したFacebookのエクスポートにも]({{site.baseurl}}/partners/message_orchestration/additional_channels/retargeting/facebook/#prerequisites)適用される。
+<br><br>新しい Facebook oAuth 設定は、[セグメントを使用した Facebook のエクスポート]({{site.baseurl}}/partners/message_orchestration/additional_channels/retargeting/facebook/#prerequisites)にも適用されます。
 {% endalert %}
 
 ### ステップ2:Facebookにユーザーをエクスポートする
@@ -67,10 +67,10 @@ Facebookオーディエンス・エクスポートは、**ユーザー・アク
 Brazeでは、Facebookオーディエンスのエクスポートは、**セグメント**ページからアクセスできる。 
 
 1. **セグメント**ページで、エクスポートしたいセグメントの横にある歯車をクリックする。
-2. **Facebookオーディエンスとしてエクスポートを**クリックする。<br><br>![ブレイズのセグメント一覧。最初のセグメントでは、設定記号が選択され、「Facebookオーディエンスとしてエクスポート」ボタンが表示される。][11]
+2. \[**Facebook オーディエンスとしてエクスポート**] をクリックします。<br><br>![Braze セグメントのリスト。最初のセグメントでは設定シンボルが選択されており、「Facebook オーディエンスとしてエクスポート」ボタンが表示されている。][11]
 
 {: start="3"}
-3\.まだBraze内でFacebookを有効化していない場合は、ダッシュボードのFacebook Technology Partnersページに行くよう促される。**テクノロジー・パートナー**＞**Facebookを通じて**Facebookをすでに有効化している場合は、エクスポートするユーザー・フィールドを選択できるようになり、Facebook広告アカウントを選択するドロップダウンが表示される。<br><br> エクスポートできるユーザーフィールドは3つある：  
+3\.Braze 内で Facebook をまだアクティブにしていない場合は、ダッシュボードで Facebook テクノロジーパートナーページに移動するように促されます。すでに \[**テクノロジーパートナー**] > \[**Facebook**] で Facebook をアクティブにしている場合は、エクスポートするユーザーフィールドを選択でき、Facebook の広告アカウントを選択するドロップダウンが表示されます。<br><br> エクスポートできるユーザーフィールドは3つある：  
 - メール
 - デバイス IDFA
 - 電話番号
@@ -80,32 +80,32 @@ Brazeでは、Facebookオーディエンスのエクスポートは、**セグ
 {% endalert %}
 
 {: start="4"}
-4\.ユーザー・フィールドを選択したら、**Exportを**クリックする。CSVエクスポートと同様に、Facebookへのセグメントのエクスポートが完了すると、Eメールが届く。
-5. Facebook Ads Manager][13] でカスタムオーディエンスを表示する。
+4\.ユーザーフィールドを選択したら \[**エクスポート**] をクリックします。CSVエクスポートと同様に、Facebookへのセグメントのエクスポートが完了すると、Eメールが届く。
+5. \[Facebook 広告マネージャ][13]でカスタムオーディエンスを表示します。
 
 {% alert important %}
-ユーザーのプライバシー保護のため、フェイスブックは閲覧を許可していない：
+ユーザーのプライバシー上の理由により、Facebook では以下の内容を表示できません。
 
-- カスタムオーディエンスに正常に追加された正確なユーザー。[詳細はこちら。](https://www.facebook.com/business/help/112061095610075)
-- カスタム・オーディエンスのサイズ。[詳細はこちら。](https://marketingland.com/exclusive-facebook-will-no-longer-show-audience-reach-estimates-for-custom-audiences-after-vulnerability-detected-236923)
+- カスタムオーディエンスに正常に追加された正確なユーザー。[詳細をご覧ください。](https://www.facebook.com/business/help/112061095610075)
+- カスタムオーディエンスのサイズ。[詳細をご覧ください。](https://marketingland.com/exclusive-facebook-will-no-longer-show-audience-reach-estimates-for-custom-audiences-after-vulnerability-detected-236923)
 {% endalert %}
 
 #### オーディエンスのエクスポートを設定する
 
-Facebookオーディエンスを構築する際、ユーザーの嗜好に基づき、また[CCPAに](https://oag.ca.gov/privacy/ccpa)基づく「販売または共有しない」権利などのプライバシー法を遵守するために、特定のユーザーを含めたり除外したりしたい場合がある。マーケティング担当者は、キャンバスのエントリー基準の中で、ユーザーの適格性に関する関連フィルタを実装する必要がある。以下にいくつかの選択肢を挙げる。 
+Facebookオーディエンスを構築する際、ユーザーの嗜好に基づき、また[CCPAに](https://oag.ca.gov/privacy/ccpa)基づく「販売または共有しない」権利などのプライバシー法を遵守するために、特定のユーザーを含めたり除外したりしたい場合がある。マーケターは、キャンバスのエントリ基準の範囲内で、ユーザーの適格性に関する適切なフィルターを実装する必要があります。以下にいくつかの選択肢を挙げる。 
 
-- [Braze SDKを通じてiOS IDFAを]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/other_sdk_customizations/#optional-idfa-collection)収集した場合、**Ads Tracking Enabled**フィルターを使用できるようになる。ユーザーがオプトインしたAudience Sync送信先にのみユーザーを送信する場合は、`true` 。 
+- [Braze SDKを通じてiOS IDFAを]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/other_sdk_customizations/#optional-idfa-collection)収集した場合、**Ads Tracking Enabled**フィルターを使用できるようになる。ユーザーがオプトインしたオーディエンス同期の宛先にのみユーザーを送信するには、値を `true` に選択します。 
 
 ![][16]{: style="max-width:75%;"}
 
-- オプトイン、オプトアウト、`Do Not Sell Or Share` 、またはその他の関連するカスタム属性を収集する場合は、キャンバスの入力条件にフィルターとして含める必要がある： 
+- オプトイン、オプトアウト、`Do Not Sell Or Share`、または他の関連するカスタム属性を収集する場合は、キャンバスのエントリ基準にこれらをフィルターとして含める必要があります。 
 
 ![エントリーのオーディエンスが "opted_in_marketing "のキャンバスは、"true "に等しい。][15]{: style="max-width:75%;"}
 
 
-#### そっくりさんオーディエンス
+#### 類似オーディエンス
 
-セグメントをFacebookオーディエンスとしてエクスポートすることに成功したら、Facebook[Lookalike Audiencesを使って][4]さらにグループを作成することができる。この機能は、選択したオーディエンスのデモグラフィック、興味、その他の属性を調べ、同様の属性を持つ人々からなる新しいオーディエンスを作成する。
+Facebook オーディエンスとしてセグメントをエクスポートしたら、Facebook [類似オーディエンス][4]を使用して追加のグループを作成できます。この機能は、選択したオーディエンスのデモグラフィック、興味、その他の属性を調べ、類似する属性を持つ新しいオーディエンスを作成します。
 
 [1]: https://www.facebook.com/business/help/113163272211510?id=180505742745347
 [2]: https://www.facebook.com/business/help/910137316041095?id=420299598837059
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/jampp.md b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/jampp.md
index 56c235453ae..ba7668177e0 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/jampp.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/jampp.md
@@ -2,7 +2,7 @@
 nav_title: Jampp
 article_title: Jampp
 alias: /partners/jampp/
-description: "ここでは、携帯顧客sの取得・リターゲティングに使用されるパフォーマンスマーケティング プラットフォームであるBrazeとJamppの提携について概説します。"
+description: "このリファレンス記事では、Braze と Jampp のパートナーシップについて説明します。Jampp は、モバイルの顧客の獲得とリターゲティングに利用されるパフォーマンスマーケティングプラットフォームです。"
 page_type: partner
 search_tag: Partner
 
@@ -10,26 +10,26 @@ search_tag: Partner
 
 # Jampp
 
-> [Jampp](https://www.jampp.com/)は、携帯顧客sの取得およびリターゲティングに使用するパフォーマンスマーケティング プラットフォームです。Jamppは、行動データと予測テクノロジーおよびプログラムテクノロジーを組み合わせて、消費者が初めて購入するか、それよりも頻繁に購入するきっかけとなる個人的な関連性のある広告を表示することで、広告主の収益を生み出します。
+> [Jampp](https://www.jampp.com/) はモバイルの顧客の獲得とリターゲティングに利用されるパフォーマンスマーケティングプラットフォームです。Jampp は、行動データと予測技術やプログラム技術を組み合わせて、消費者に対して初めての購入やより頻繁な購入を促すパーソナルで関連性の高い広告を表示することで、広告主の収益を創出します。
 
-Braze とJampp インテグレーションを使用すると、Braze ユーザー s がJampp にBraze Webhookを介してイベントを同期できます。そのため、顧客 s は、モバイル広告エコシステム内のリターゲティングイニシアチブに、より豊富なデータセットを追加できます。
+Braze と Jampp の統合により、Braze ユーザーは Braze Webhook イベントを使用してイベントを Jampp に同期できます。その結果、お客様はモバイル広告エコシステム内で、より豊富なデータセットを各自のリターゲティングイニシアチブに追加できます。
 
-広告でsをリターゲティングする 顧客したい場合の例:
+広告で顧客をリターゲティングする状況の例を以下に示します。
 - 顧客のメールまたはプッシュサブスクリプションのステートが変化したとき。
 - 顧客とBraze メッセージング キャンペーンとの相互作用の仕方。
-- 顧客がトリガー特定のジオフェンスを受け取った場合。
+- 顧客が特定のジオフェンスをトリガーした場合。
 
 ## 前提条件
 
-この統合は、iOS とAndroid アプリ s をサポートします。
+この統合では、iOS アプリと Android アプリがサポートされています。
 
 | 要件 | 説明 |
 |---|---|
-| Jampp勘定 | この提携の前倒しタグを行うには、[Jamppアカウント](https://www.jampp.com/)が必要です。 |
-| Android アプリ番号 | Android用の一意のBraze アプリライケーション識別子("com.example"など)。 |
-| iOS アプリ識別 | iOS 用の一意のBraze アプリライセンス識別子("012345678" など)。 |
-| Braze SDKでのIDFA 収集の有効化 | IDFA 収集はBraze SDK内でオプションであり、デフォルトで無効になっています。 | 
-| カスタム属性によるグーグル広告IDの収集 | Google 広告ID コレクションは顧客 s のオプションであり、\[カスタム属性][5] として収集できます。
+| Jampp アカウント | このパートナーシップを活用するには、[Jampp アカウント](https://www.jampp.com/)が必要です。 |
+| Android アプリ ID | Android用の一意のBraze アプリライケーション識別子("com.example"など)。 |
+| iOS アプリ ID | iOS 用の Braze アプリケーション識別子 (「012345678」など)。 |
+| Braze SDKでのIDFA 収集の有効化 | IDFA 収集は Braze SDK 内ではオプションであり、デフォルトでは無効になっています。 | 
+| カスタム属性によるグーグル広告IDの収集 | Google 広告 ID の収集は顧客向けのオプションであり、\[カスタム属性][5]]として収集できます。
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合
@@ -44,9 +44,9 @@ Braze とJampp インテグレーションを使用すると、Braze ユーザ
 
 一度だけJampp Webhook キャンペーンしたい場合や、既設のテンプレートを使用したい場合は、新規キャンペーン作成時にBrazeで**Webhook**を選択してください。
 
-新しいWebフックテンプレートで、次のフィールドs を入力します。
+新しい Webhook テンプレートで、次のフィールドに入力します。
 - **リクエスト本文**:Raw Text
-- **WebフックURL**:
+- **Webhook URL**:
 {% raw %}
 ```liquid
 {% assign event_name = 'your_jampp_event_name' %}
@@ -63,15 +63,15 @@ http://tracking.jampp.com/event?kind={{event_name}}&rnd={{rnd}}&app={% if {{most
 ```
 {% endraw %}
 
-Webhook では、次の操作を実行する必要があります。
-- イベント名を設定します。この名前はあなたのJampp ダッシュボードの耳元をアプリします。
-- Android("com.example"など)およびiOS("012345678"など)のアプリ固有のアプリライセンス識別子を渡します。
-- グーグル広告IDとして"トラッキングしているアプリの適切なカスタム属性に[Liquid][1]を挿入します。この例では、Google の広告ID は`aaid` としてリストされていますが、開発者 s が設定したカスタム属性の名前に置き換える必要があります。
+Webhook URL で次の操作を行う必要があります。
+- イベント名を設定します。この名前は Jampp ダッシュボードに表示されます。
+- Android と iOS のアプリの一意のアプリケーション識別子 (Android:「com.example」、iOS:「012345678」など) を渡します。
+- Google 広告 ID として追跡している適切なカスタム属性の [Liquid][1] を挿入します。この例では、Google 広告 ID が `aaid` としてリストされていますが、これを開発者が設定したカスタム属性名に置き換える必要があります。
 
 ![Braze Webhook ビルダーに表示されるWebhookのURL およびメッセージプレビュー。][2]
 
 {% alert important %}
-Braze は自動的にIDFA/AAID を収集しないため、これらの値を自分で保存する必要があります。この情報を収集するには、ユーザーの同意を必要とする場合があることに注意してください。
+Braze ではデバイス IDFA/AAID を自動的に収集しないため、これらの値を各自で保存する必要があります。このデータを収集するには、ユーザーの同意を必要とする場合があることに注意してください。
 {% endalert %}
 
 #### リクエストヘッダーとメソッド
@@ -90,7 +90,7 @@ Jampp WebhookにはHTTP メソッドとリクエストヘッダーが必要で
 
 ### ステップ2:リクエストのプレビュー
 
-リクエストがさまざまなユーザーに対して適切にレンダリングされていることを確認するために、メッセージをプレビューします。Android とiOS ユーザー s の両方のテストリクエストをプレビューして送信することをお勧めします。リクエストが成功した場合、API は`HTTP 204` で応答します。
+リクエストがさまざまなユーザーに対して適切にレンダリングされていることを確認するために、メッセージをプレビューします。Android と iOS の両方のユーザーを対象としたテストリクエストをプレビューして送信することをお勧めします。リクエストが成功した場合、API は`HTTP 204` で応答します。
 
 {% alert important %}
 テンプレートを保存してから退場してください！<br>更新されたWebhook テンプレートs は、新しい[Webhook キャンペーン]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/) を作成するときに**保存されたWebhook テンプレートs** 一覧にあります。
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/quikly.md b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/quikly.md
index f0ccfe04375..94c520a2e78 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/quikly.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/quikly.md
@@ -12,13 +12,13 @@ search_tag: Partner
 
 > [Quikly][1]、緊急性マーケティングプラットフォームは、心理学を活用して消費者を動機付け、ブランドが主要なマーケティングイニシアチブに対する反応を即座に高めることができます。
 
-BrazeとQuiklyのパートナーシップにより、Brazeのカスタマージャーニー内のイベントでコンバージョンを加速させることができます。Quiklyは、緊急性の心理学を利用して、消費者を楽しく、そして即座に動機付けることでこれを実現します。例えば、ブランドはQuiklyを使用して、新しいメールおよびSMSの購読者を直接Brazeに追加したり、モバイルアプリのダウンロードなどの他の重要なマーケティング目標を促進したりすることができます。
+BrazeとQuiklyのパートナーシップにより、Brazeのカスタマージャーニー内のイベントでコンバージョンを加速させることができます。Quiklyは、緊急性の心理学を利用して、消費者を楽しく、そして即座に動機付けることでこれを実現します。たとえば、ブランドが Quikly を使用して、新しいメールや SMS サブスクライバーを Braze にすぐに直接取り込んだり、モバイルアプリのダウンロードなどの他の重要なマーケティング目標達成を促進したりできます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| クイックリーアカウント | このパートナーシップを利用するには、[Quikly][1]ブランドパートナーアカウントが必要です。 |
+| Quikly アカウント | このパートナーシップを利用するには、[Quikly][1]ブランドパートナーアカウントが必要です。 |
 | Braze REST API キー | `users.track`の権限を持つBraze REST APIキー。<br><br> これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。 |
 | Braze REST エンドポイント | [あなたのRESTエンドポイントURL][2].お客様のエンドポイントは、お客様のインスタンスのBraze URLに依存します。 |
 | Quikly APIキー（オプション） | クライアントの成功マネージャーによって提供されたQuikly APIキー（Webhookのみ）。 |
@@ -26,24 +26,24 @@ BrazeとQuiklyのパートナーシップにより、Brazeのカスタマージ
 
 ## ユースケース
 
-QuiklyはブランドがメールまたはSMSの取得を加速し、購読者がBraze内で直接ファーストパーティデータを提供するように動機付けることを可能にします。また、Brazeを使用して、休眠顧客を再活性化し、そのオーディエンスを保持するためのQuiklyアクティベーションをターゲットにすることもできます。さらに、マーケティング担当者は、この統合を使用して、特定のカスタマージャーニーイベントに独自の報酬構造でインセンティブを与えることができます。 
+ブランドは Quikly を使用して、メールまたは SMS サブスクライバーの獲得を加速し、サブスクライバーが Braze 内で直接ファーストパーティデータを提供するように促すことができます。また Braze を使用して、Quikly アクティベーションで離脱した顧客をターゲットにすることもできます。これにより、そのオーディエンスが再アクティブ化され、維持されます。さらに、マーケティング担当者は、この統合を使用して、特定のカスタマージャーニーイベントに独自の報酬構造でインセンティブを与えることができます。 
 
 以下に例を示します。
- - 数日間にわたって期待感とエンゲージメントを高め、消費者が[Quikly Hype][3]でエキサイティングな報酬を獲得するチャンスにオプトインするようにします。ファーストパーティデータは自動的にBrazeにプッシュされます。
- - 新しいメールおよびSMS購読者の獲得を加速するために、消費者の反応速度、他者とのランク、ランダム、または時間や数量がなくなる前に基づいたユニークなリアルタイムオファーを使用して、[Quikly Swap][4]を使用します。
- - webhookを使用して、カスタマージャーニーの特定のステップをユニークな報酬構造で動機付けします。
+ - 消費者が [Quikly Hype][3] でエキサイティングなリワードを獲得できるチャンスのためにオプトインすると、期待とエンゲージメントが日に日に高まります。ファーストパーティデータは自動的にBrazeにプッシュされます。
+ - [Quikly Swap][4] を使用して、消費者の反応の速さ、ランダムな他者との比較ランキングに基づく独自のリアルタイムオファーで、時間や数量がなくなる前に、新しいメールまたは SMS サブスクライバーの獲得を促進します。
+ - Webhook を使用した独自のリワード構造で、カスタマージャーニーの特定のステップを促します。
  - Quiklyアクティベーションに参加すると、ユーザーのプロファイルにカスタム属性やイベントが適用されます。
 
 ## 統合
 
-以下に示すのは、メール取得、SMS取得、カスタム属性、およびwebhookの4つの異なる統合です。選択する統合は、Quiklyのアクティベーションとユースケースに依存します。
+以下に示すのは、メール取得、SMS取得、カスタム属性、およびwebhookの4つの異なる統合です。選択する統合は、Quikly のアクティベーションとユースケースに応じて異なります。
 
 {% tabs %}
-{% tab メール Acquisition %}
+{% tab メール獲得 %}
 
 ### メール取得
 
-Quiklyのアクティベーションが顧客のメールアドレスやプロファイルデータを収集する場合、唯一必要なステップはQuiklyにREST APIキーとエンドポイントを提供することです。Quiklyは、ブランドアカウントを設定してこのデータをBrazeに渡します。追加のユーザー属性を含めたい場合は、APIクレデンシャルをQuiklyに提供する際にこれを言及してください。
+Quiklyのアクティベーションが顧客のメールアドレスやプロファイルデータを収集する場合、唯一必要なステップはQuiklyにREST APIキーとエンドポイントを提供することです。Quiklyは、ブランドアカウントを設定してこのデータをBrazeに渡します。追加のユーザー属性を含めたい場合は、API 認証情報を Quikly に提供するときにこのことに言及してください。
 
 ここに、Quiklyがこのワークフローを実行する方法の概要を示します。
 1. Quiklyのアクティベーションに参加すると、Quiklyは指定された`email_address`を持つユーザーが存在するかどうかを確認するために[エクスポートAPI]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)を使用してユーザー検索をスケジュールします。
@@ -53,7 +53,7 @@ Quiklyのアクティベーションが顧客のメールアドレスやプロ
     - 必要に応じて、Quiklyはユーザーがアクティベーションに参加したことを示すために、ユーザーのプロファイルにカスタム属性を記録できます。
   - ユーザーが存在しない場合:
     - QuiklyはBrazeの[`/users/track`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)を介してエイリアスのみのプロファイルを作成し、ユーザーのメールをユーザーエイリアスとして設定して、将来そのユーザーを参照します（ユーザーにはexternal IDがないため）。
-    - 必要に応じて、Quiklyはカスタムイベントをログに記録して、このプロファイルがQuiklyアクティベーションに参加したことを示すことができます。
+    - 必要に応じて、Quikly はカスタムイベントをログに記録して、このプロファイルが Quikly アクティベーションに参加したことを示すことができます。
 
 {% details /users/track request %}
 
@@ -80,23 +80,23 @@ Authorization: Bearer YOUR-REST-API-KEY
 {% enddetails %}
 
 {% endtab %}
-{% tab SMS取得 %}
+{% tab SMS 獲得 %}
 
-### SMS購読
+### SMS サブスクリプション
 
-Quiklyのアクティベーションは、顧客から直接携帯電話番号を収集し、新しいSMSサブスクリプションを開始することができます。この統合を有効にするには、Quiklyクライアント成功マネージャーに`subscription_group_id`を提供してください。サブスクリプショングループの`subscription_group_id`にアクセスするには、**サブスクリプショングループ**ページに移動します。
+Quikly アクティベーションは、顧客から直接携帯電話番号を収集して新しい SMS サブスクリプションを開始できます。この統合を有効にするには、Quikly クライアントのサクセスマネージャーに `subscription_group_id` を提供してください。サブスクリプショングループの`subscription_group_id`にアクセスするには、**サブスクリプショングループ**ページに移動します。
 
-Quiklyは顧客の電話番号を使用してサブスクリプションの検索を行い、SMSサブスクリプションが既に存在する場合は自動的にアクティベーションでクレジットします。それ以外の場合は、新しいサブスクリプションが開始され、サブスクリプションのステータスが確認された後、顧客にクレジットが付与されます。
+Quikly は顧客の電話番号を使用してサブスクリプション検索を実行し、SMS サブスクリプションが既に存在する場合はアクティベーションで自動的にクレジットを付与します。それ以外の場合は、新しいサブスクリプションが開始され、サブスクリプションのステータスが確認された後、顧客にクレジットが付与されます。
 
-顧客がQuiklyを介して携帯番号と同意を提供する際の完全なワークフローは次のとおりです:
-1. Quiklyは、[サブスクリプショングループステータス]({{site.baseurl}}/api/endpoints/subscription_groups/get_list_user_subscription_group_status/)を使用してサブスクリプション検索を実行し、指定された`phone`が`subscription_group_id`にサブスクライブされているかどうかを確認します。サブスクリプションが存在する場合、Quiklyアクティベーションでユーザーにクレジットを付与します。さらなるアクションは必要ありません。
+顧客が Quikly で携帯電話番号と同意を提供する際の全体的なワークフローは次のとおりです:
+1. Quiklyは、[サブスクリプショングループステータス]({{site.baseurl}}/api/endpoints/subscription_groups/get_list_user_subscription_group_status/)を使用してサブスクリプション検索を実行し、指定された`phone`が`subscription_group_id`にサブスクライブされているかどうかを確認します。サブスクリプションが存在する場合、Quikly アクティベーションでユーザーにクレジットを付与します。さらなるアクションは必要ありません。
 2. Quiklyは、[識別子エンドポイントによるユーザープロファイルのエクスポート]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)を使用してユーザー検索を実行し、指定された`email_address`でユーザープロファイルが存在するかどうかを確認します。ユーザーが存在しない場合、Braze の [`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) を介してエイリアスのみのプロファイルを作成し、ユーザーのメールをユーザーエイリアスとして設定して、将来そのユーザーを参照できるようにします（ユーザーには external ID がないため）。
-3. [ユーザーのサブスクリプショングループステータスエンドポイントを使用してサブスクリプションステータスを更新]({{site.baseurl}}/api/endpoints/subscription_groups/post_update_user_subscription_group_status/)。
+3. [ユーザーのサブスクリプショングループステータスの更新エンドポイント]({{site.baseurl}}/api/endpoints/subscription_groups/post_update_user_subscription_group_status/)を使用してサブスクリプションのステータスを更新します。
 
-既存のダブルオプトインSMSサブスクリプションワークフローをサポートするために、Quiklyは上記のワークフローの代わりにカスタムイベントをBrazeに送信できます。その場合、サブスクリプションステータスを直接更新するのではなく、[カスタムイベントがダブルオプトインプロセスをトリガーし]({{site.baseurl}}/user_guide/message_building_by_channel/sms/non_native/double_opt_in/)、サブスクリプションステータスが定期的に監視され、ユーザーが完全にオプトインしたことを確認してからQuiklyアクティベーションでクレジットされます。
+既存のダブルオプトインSMSサブスクリプションワークフローをサポートするために、Quiklyは上記のワークフローの代わりにカスタムイベントをBrazeに送信できます。この場合、サブスクリプションステータスを直接更新するのではなく、[カスタムイベントによってダブルオプトインプロセスがトリガーされ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/non_native/double_opt_in/)、サブスクリプションステータスが定期的に監視され、ユーザーが完全にオプトインしたことを確認してから Quikly アクティベーションが実行されます。
 
 {% alert important %}
-Brazeは、新しいユーザーを`/users/track`エンドポイント経由で作成する際に、ユーザーを関連するサブスクリプショングループに追加する前に、ユーザープロファイルを完全に作成するための時間を確保するために約2分の遅延を設けることを推奨します。
+Braze は、`/users/track` エンドポイントを使用して新しいユーザーを作成する場合、Braze がユーザープロファイルを完全に作成できる時間を確保するために、関連するサブスクリプショングループにユーザーを追加するまでに約2分の遅延が必要であることをアドバイスしています。
 {% endalert %}
 
 {% details Detailed /subscription/status/set request %}
@@ -122,12 +122,12 @@ Authorization: Bearer YOUR-REST-API-KEY
 {% tab カスタム属性 %}
 ### カスタム属性
 
-Braze の実装によっては、Quikly アクティベーション内のイベントを Braze を通じてカスケードさせ、さらに処理することを検討する場合があります。例えば、Quiklyアクティベーションで達成されたレベルやインセンティブに基づいてカスタム属性をユーザーに適用し、アプリを開封したりWebサイトにログインしたときに関連するコンテンツカードを表示することができます。Quiklyは、これらの統合を実装するために直接協力します。
+Braze の実装によっては、Quikly アクティベーション内のイベントを Braze を通じてカスケードさせ、さらに処理することを検討する場合があります。たとえば、Quikly アクティベーションで達成したレベルやインセンティブに基づいてカスタムユーザー属性を適用し、アプリを開いたときや Web サイトにログインしたときに関連するコンテンツカードを表示することができます。これらの統合を実装するために Quikly がお客様と直接協力します。
 
 {% endtab %}
 {% tab webhook %}
 ### Webhook
-特定のイベントに対するインセンティブをトリガーするためにwebhookを使用してカスタマージャーニーを進めます。例えば、ユーザーがアプリにログインしたとき、プッシュ通知をオンにしたとき、またはストアロケーターを使用したときにBrazeイベントがある場合、特定のQuiklyアクティベーションの設定に基づいて、そのユーザーにカスタムオファーをトリガーするWebhookを使用できます。例として、アクション（例えば、アプリにログインする）を行った最初のX人のユーザーにカスタムオファーを提供する、または時間が経過するにつれて価値が減少するオファーを提供して即時の反応を促す戦術が含まれます。
+Webhook を使用して、カスタマージャーニーの特定のイベントに対するインセンティブをトリガーします。たとえば、ユーザーがアプリにログインしたとき、プッシュ通知をオンにしたとき、またはストアロケーターを使用したときの Braze イベントがある場合、Webhook を使用して、特定のQuikly アクティベーションの設定に基づき、そのユーザーへのカスタムオファーをトリガーできます。たとえば、カスタムオファーでアクション (アプリへのログインなど) を実行するユーザーのうち、最初の X 人にリワードを与える、または即座の応答を促すために、時間の経過に伴い価値が減少するオファーを提供するなどの戦術があります。
 
 ### BrazeでQuiklyのWebhookを作成する
 
@@ -145,11 +145,11 @@ Braze の実装によっては、Quikly アクティベーション内のイベ
 
 #### リクエストヘッダーとメソッド
 
-Quiklyには認証のための`HTTP Header`が必要です。
+Quikly では認証に `HTTP Header` が必要です。
 
 - **HTTPメソッド**:POST
 - **リクエストヘッダー**:
-  - **認可**:ベアラー \[PARTNER_AUTHORIZATION_HEADER]
+  - **Authorization**:ベアラー \[PARTNER_AUTHORIZATION_HEADER]
   - **Content-Type**: application/json
 
 #### Request body
@@ -163,7 +163,7 @@ Quiklyには認証のための`HTTP Header`が必要です。
 ```
 {% endraw %}
 
-### プレビューあなたのリクエスト
+### リクエストをプレビューする
 
 **プレビュー** パネルでリクエストをプレビューするか、`Test` タブに移動して、ランダムなユーザー、既存のユーザーを選択するか、Webhookをテストするために独自のユーザーをカスタマイズできます。
 
diff --git a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/remerge.md b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/remerge.md
index 7c4ac06eefb..27618bd0771 100644
--- a/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/remerge.md
+++ b/_lang/ja/_partners/message_orchestration/additional_channels/retargeting/remerge.md
@@ -1,25 +1,25 @@
 ---
-nav_title: リマージ
-article_title: リマージ
+nav_title: Remerge
+article_title: Remerge
 alias: /partners/remerge/
-description: "この参考記事では、BrazeとRemergeのパートナーシップについて概説している。Remergeは、大規模なリターゲティングのための専用アプリで、アプリのオーディエンスを効率的にセグメントし、ユーザーをリターゲティングするためのツールを提供する。"
+description: "このリファレンス記事では、Braze と Remerge のパートナーシップについて説明します。Remerge は、大規模なリターゲティングのための専用アプリであり、アプリのオーディエンスを効率的にセグメント化し、ユーザーをリターゲティングするツールを備えています。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# リマージ
+# Remerge
 
-> [Remergeは](https://www.remerge.io/)、アプリのオーディエンスを効率的にセグメント化し、ユーザーをリターゲティングするためのツールを提供し、大規模なアプリのリターゲティングのために構築されている。
+> [Remerge](https://www.remerge.io/) は、大規模なリターゲティングのための専用アプリであり、アプリのオーディエンスを効率的にセグメント化し、ユーザーをリターゲティングするツールを備えています。
 
-BrazeとRemergeの統合は、Webhookイベントを通じてRemergeにユーザーデータを送信し、モバイルデマンドサイドプラットフォームを通じてユーザーのリターゲティングを支援することで、強固でクロスチャネルのライフサイクルマーケティングキャンペーンの開発を支援する。
+Braze と Remerge の統合により、ユーザーデータを Webhook イベント経由で Remerge に送信し、モバイルデマンドサイドプラットフォームでユーザーのリターゲティングを支援することで、堅牢なクロスチャネルのライフサイクルマーケティングキャンペーンを開発できます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| アカウントをリマージする | このパートナーシップを利用するには、リマージ・アカウントが必要である。 |
-| ウェブフック・キーをリマージする | このキーはRemergeが提供する。 |
+| Remerge アカウント | このパートナーシップを活用するには、Remerge アカウントが必要です。 |
+| Remerge Webhook キー | このキーは Remerge から提供されます。 |
 | AndroidアプリID | Android用Brazeアプリケーション固有の識別子（「com.example 」など）。 |
 | iOSアプリID | iOS用のお客様固有のBrazeアプリケーション識別子（"012345678 "など）。 |
 | Braze SDKでIDFAコレクションを有効にする | IDFAコレクションはBraze SDK内ではオプションであり、デフォルトでは無効になっている。 | 
@@ -29,7 +29,7 @@ BrazeとRemergeの統合は、Webhookイベントを通じてRemergeにユーザ
 
 ### ステップ1:BrazeのWebhookテンプレートを作成する
 
-将来のキャンペーンやCanvas用にRemergeウェブフックテンプレートを作成するには、Brazeプラットフォームの**テンプレート**>**ウェブフックテンプレートに**移動する。 
+今後のキャンペーンまたはキャンバス用の Remerge Ｗebhook テンプレートを作成するには、Braze プラットフォームの \[**テンプレート**] > \[**Webhook テンプレート**] に移動します。 
 
 {% alert note %}
 [古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**Engagement（エンゲージメント）**」＞「**Templates & Media（テンプレート＆メディア**）」＞「**Webhook Templates（ウェブフック・テンプレート**）」と進む。
@@ -38,8 +38,8 @@ BrazeとRemergeの統合は、Webhookイベントを通じてRemergeにユーザ
 単発のRemergeウェブフックキャンペーンを作成したい場合、または既存のテンプレートを使用したい場合は、新しいキャンペーンを作成する際にBrazeの**ウェブフックを**選択する。
 
 新しいWebhookテンプレートで、以下のフィールドに記入する：
-- **リクエスト・ボディ**Raw Text
-- **ウェブフックのURL**：
+- **リクエスト本文**:Raw Text
+- **Webhook URL**:
 {% raw %}
 ```liquid
 {% assign event_name = 'your_remerge_event_name' %} 
@@ -56,16 +56,16 @@ https://remerge.events/event?partner=braze&app_id=\{% if most_recently_used_devi
 ```
 {% endraw %}
 
-ウェブフックのURLには、次のように記述する：
+Webhook URL で次の操作を行う必要があります。
 - `https://remerge.events/event` APIを使ってウェブフック・イベントを送信する。
-- イベント名を設定する。この名前はダッシュボードに表示される。 [remerge.io][65]ダッシュボードに表示される。
-- リマージには、Android用（"com.example"など）とiOS用（"012345678 "など）のアプリ固有のアプリケーション識別子を渡す。
-- Remergeがこれを提供する。
+- イベント名を設定する。この名前は [remerge.io][65] ダッシュボードに表示されます。
+- Android と iOS のアプリの一意のアプリケーション識別子 (Android:「com.example」、iOS:「012345678」など) を Remergeに渡します。
+- キーを定義します。これは Remerge から提供されます。
 
 ![Brazeウェブフックビルダーに表示されるウェブフックURLとメッセージプレビュー。][67]
 
 {% alert important %}
-BrazeはデバイスのIDFA/AAIDを自動的に収集しないので、これらの値を自分で保存する必要がある。このデータを収集するには、ユーザーの同意が必要な場合があることに注意すること。
+BrazeはデバイスのIDFA/AAIDを自動的に収集しないので、これらの値を自分で保存する必要がある。このデータを収集するには、ユーザーの同意を必要とする場合があることに注意してください。
 {% endalert %}
 
 #### リクエストヘッダと方法
@@ -73,7 +73,7 @@ BrazeはデバイスのIDFA/AAIDを自動的に収集しないので、これら
 RemergeウェブフックはHTTPメソッドとリクエストヘッダを必要とする。
 
 - **HTTPメソッド**：GET
-- **ヘッダーを要求する**：
+- **リクエストヘッダー**:
   - **Content-Type**: application/json
 
 ![リクエストヘッダ、HTTPメソッド、メッセージプレビューがBraze webhookビルダーに表示される。][68]
diff --git a/_lang/ja/_partners/message_orchestration/attribution.md b/_lang/ja/_partners/message_orchestration/attribution.md
index d74c78d093c..e3f1e86d555 100644
--- a/_lang/ja/_partners/message_orchestration/attribution.md
+++ b/_lang/ja/_partners/message_orchestration/attribution.md
@@ -22,7 +22,7 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/attribution/branch/branch_for_deeplinking/
 - name: Kochava
   url: /docs/partners/message_orchestration/attribution/kochava/
-- name: 単数
+- name: Singular
   url: /docs/partners/message_orchestration/attribution/singular/
 - name: Vizbee
   url: /docs/partners/message_orchestration/attribution/vizbee_for_tv_deeplinking/
diff --git a/_lang/ja/_partners/message_orchestration/attribution/adjust.md b/_lang/ja/_partners/message_orchestration/attribution/adjust.md
index 254484c9876..e11550f784e 100644
--- a/_lang/ja/_partners/message_orchestration/attribution/adjust.md
+++ b/_lang/ja/_partners/message_orchestration/attribution/adjust.md
@@ -10,7 +10,7 @@ search_tag: Partner
 
 # 調整する
 
-> [Adjustは](https://www.adjust.com/)、広告ソースのアトリビューションと高度なアナリティクスを組み合わせ、ビジネスインテリジェンスの包括的なイメージを提供するモバイルアトリビューションとアナリティクスの企業である。
+> [Adjust](https://www.adjust.com/) は、モバイルアトリビューションおよび分析を扱う企業です。広告ソースのアトリビューションと高度な分析を組み合わせ、総合的なビジネスインテリジェンスを提供しています。
 
 BrazeとAdjustの統合により、オーガニックインストール以外のアトリビューションデータをインポートし、ライフサイクルキャンペーン内でよりインテリジェントにセグメント化できる。
 
@@ -18,9 +18,9 @@ BrazeとAdjustの統合により、オーガニックインストール以外の
 
 | 必要条件 | 説明 |
 |---|---|
-| 口座を調整する | このパートナーシップを利用するにはアジャスト・アカウントが必要だ。 |
-| iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。これらの要件の詳細は、統合プロセスのステップ1に記載されている。 |
-| SDKを調整する | 必要なBraze SDKに加えて、[Adjust SDKを](https://docs.adjust.com/en/getting-started/#integrate-the-adjust-sdk)インストールする必要がある。 |
+| Adjust アカウント | このパートナーシップを活用するには、Adjust アカウントが必要です。 |
+| iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。これらの要件の詳細については、統合プロセスのステップ1を参照してください。 |
+| SDKを調整する | 必要な Braze SDK に加えて、[Adjust SDK](https://docs.adjust.com/en/getting-started/#integrate-the-adjust-sdk) をインストールする必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
@@ -29,7 +29,7 @@ BrazeとAdjustの統合により、オーガニックインストール以外の
 
 #### Android
 
-Androidアプリをお持ちの場合は、Adjustに固有のBrazeデバイスIDを渡す必要がある。このIDはAdjust SDKの`addSessionPartnerParameter()` 。でSDKを初期化する前に、以下のコード・スニペットをインクルードする必要がある。 `Adjust.onCreate.`
+Androidアプリをお持ちの場合は、Adjustに固有のBrazeデバイスIDを渡す必要がある。この ID は、Adjust SDK の`addSessionPartnerParameter()`メソッドで設定できます。`Adjust.onCreate.` で SDK を初期化する前に、次のコードスニペットを含める必要があります。
 
 ```
 Adjust.addSessionPartnerParameter("braze_device_id", Braze.getInstance(getApplicationContext()).getDeviceId()););
@@ -52,52 +52,52 @@ If set to `true`, you must implement the iOS device ID mapping for Swift in orde
 
 iOSアプリがあれば、IDFVはAdjustによって収集され、Brazeに送信される。このIDは、Brazeで一意のデバイスIDにマッピングされる。
 
-[iOS14アップグレードガイドに]({{site.baseurl}}/android_12/)記載されているように、BrazeでIDFAを収集している場合、BrazeはオプトインしたユーザーのIDFA値を引き続き保存する。そうでない場合、IDFVはユーザーをマップするための予備識別子として使用される。
+[iOS14アップグレードガイドに]({{site.baseurl}}/android_12/)記載されているように、BrazeでIDFAを収集している場合、BrazeはオプトインしたユーザーのIDFA値を引き続き保存する。このようにしないと、ユーザーをマッピングするためのフォールバック識別子として IDFV が使用されます。
 
 {% endtab %}
-{% tab スウィフト %}
+{% tab Swift %}
 
-iOSアプリの場合、`useUUIDAsDeviceId` フィールドを`false` に設定することで、IDFVを収集することができる。設定されていない場合、iOSのアトリビューションはAdjustからBrazeに正確にマッピングされない可能性が高い。詳細については、「[IDFV の収集]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/)」を参照してください。
+iOSアプリを使用している場合は、`useUUIDAsDeviceId` フィールドを`false` に設定することで、IDFV を収集することを選択できます。設定されていない場合、iOSのアトリビューションはAdjustからBrazeに正確にマッピングされない可能性が高い。詳細については、「[IDFV の収集]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/)」を参照してください。
 
 {% endtab %}
 {% endtabs %}
 
 {% alert note %}
-AdjustからBrazeにインストール後のイベントを送信する予定がある場合は、次のことが必要になる：<br><br>1) Adjust SDKのセッションおよびイベントパラメータに`external_id` 。収益イベント転送のためには、`product_id` をイベントのパラメータとして設定する必要もある。イベント転送のためのパートナーパラメータの定義については、[Adjustのドキュメントを](https://github.com/adjust/sdks)参照のこと。<br><br>2) Adjustに入力する新しいAPIキーを生成する。これは、BrazeダッシュボードのAdjust partnerページにある**Generate API Key**ボタンを選択することで行うことができる。
+AdjustからBrazeにインストール後のイベントを送信する予定がある場合は、次のことが必要になる：<br><br>1) Adjust SDK 内でセッションおよびイベントパラメーターとして `external_id` を必ず追加します。収益イベント転送では、イベントのパラメーターとして `product_id` も設定する必要があります。イベント転送のためのパートナーパラメーターの定義の詳細については、[Adjust のドキュメント](https://github.com/adjust/sdks)を参照してください。<br><br>2) Adjust に入力する新しい API キーを生成します。これを行うには、Braze ダッシュボードの Adjust パートナーページにある \[**API キーを生成**] ボタンを選択します。
 {% endalert %}
 
 ### ステップ2:Brazeデータインポートキーを取得する
 
-Brazeで、**Integrations**>**Technology Partnersに**移動し、**Adjustを**選択する。 
+Brazeで \[**統合**] > \[**テクノロジーパートナー**] に移動し、\[**Adjust**] を選択します。 
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。鍵の生成後、新しい鍵を作成したり、既存の鍵を無効にしたりすることができる。データインポートキーとRESTエンドポイントは、Adjustのダッシュボードでポストバックを設定する際に次のステップで使用される。<br><br>![この画像は、Adjustテクノロジーページにある「Data Import for Install Attribution」ボックスを示している。このボックスには、データ・インポート・キーとRESTエンドポイントが表示される。][1]{: style="max-width:90%;"}
+ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。データインポートキーとRESTエンドポイントは、Adjustのダッシュボードでポストバックを設定する際に次のステップで使用される。<br><br>![Adjust テクノロジーページにある「インストールアトリビューションのデータインポート」ボックス。このボックスには、データインポートキーと REST エンドポイントが表示されている。][1]{: style="max-width:90%;"}
 
-### ステップ3:アジャストでブレイズを設定する
+### ステップ3:Adjust で Braze を設定する
 
-1. Adjustのダッシュボードで、**App Settingsに**移動し、**Partner Setupに**移動し、**Add Partnersに**移動する。
-2. **Braze（旧Appboy）を**選択し、データインポートキーとBraze RESTエンドポイントを指定する。
-3. **保存して閉じる**」をクリックする。
+1. Adjust のダッシュボードで \[**App Settings**]、\[**Partner Setup**]、\[**Add Partners**] の順に移動します。
+2. \[**Braze (formerly Appboy)**] を選択し、データインポートキーと Braze REST エンドポイントを入力します。
+3. \[**Save & Close**] をクリックします。
 
 ### ステップ4:統合を確認する
 
-BrazeがAdjustからアトリビューションデータを受信すると、BrazeのAdjustテクノロジーパートナーページのステータス接続インジケーターが "Not Connected "から "Connected "に変わる。最後に成功したリクエストのタイムスタンプも含まれる。 
+Braze が Adjust からアトリビューションデータを受信すると、Braze の Adjust テクノロジーパートナーページのステータス接続インジケーターが \[接続されていません] から \[接続済み] に変わります。最後に成功したリクエストのタイムスタンプも含まれる。 
 
-これは、帰属するインストールに関するデータを受け取るまでは起こらないことに注意してほしい。Adjustのポストバックから除外されるべきオーガニックインストールは、我々のAPIによって無視され、接続が成功したかどうかを判断する際にカウントされない。
+これは、紐づけられるインストールに関するデータを受け取るまでは発生しないことに注意してください。Adjust のポストバックから除外する必要があるオーガニックインストールは、Braze の API では無視され、接続の確立が成功したかどうかを判断する際に考慮されません。
 
 ## 利用可能なデータフィールド
 
-提案されたとおりにインテグレーションを設定すると、BrazeはAdjustのデータを次の表のようにセグメントフィルターにマッピングする。
+提案されたとおりに統合を設定すると、次の表に示すように、Braze により Adjust のデータがセグメントフィルターにマッピングされます。
 
-| データフィールドを調整する | ブレージングセグメントフィルター |
+| データフィールドを調整する | Braze セグメントフィルター |
 | --- | --- |
-| `{network_name}` | 帰属元 |
-| `{campaign_name}` | 帰属キャンペーン |
-| `{adgroup_name}` | 帰属アドグループ |
-| `{creative_name}` | 帰属広告 |
+| `{network_name}` | 紐づけられるソース |
+| `{campaign_name}` | 紐づけられるキャンペーン |
+| `{adgroup_name}` | 紐づけられる広告グループ |
+| `{creative_name}` | 紐づけられる広告 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## FacebookとX（旧Twitter）のアトリビューションデータ
@@ -106,13 +106,13 @@ FacebookおよびX（旧Twitter）キャンペーンのアトリビューショ
 
 ## BrazeでクリックトラッキングURLを調整する（オプション）
 
-Brazeのキャンペーンでクリック追跡リンクを使用すると、どのキャンペーンがアプリのインストールやリエンゲージメントを促進しているかを簡単に確認できる。その結果、マーケティング活動をより効果的に測定できるようになり、ROIを最大化するためにどこにリソースを投資すべきか、データに基づいた意思決定ができるようになる。
+Brazeのキャンペーンでクリック追跡リンクを使用すると、どのキャンペーンがアプリのインストールやリエンゲージメントを促進しているかを簡単に確認できる。その結果、マーケティング活動をより効果的に測定できるようになり、ROI を最大化するためにどこにリソースを投資すべきかについて、データに基づいた意思決定ができるようになります。
 
 クリックトラッキング・リンクの調整を始めるには、[ドキュメントを](https://help.adjust.com/tracking/attribution/tracker-urls)参照すること。BrazeのキャンペーンにAdjustクリックトラッキングリンクを直接挿入することができる。Adjustは、[確率的アトリビューション手法を使って](https://www.adjust.com/blog/attribution-compatible-with-ios14/)、リンクをクリックしたユーザーをアトリビュートする。Brazeキャンペーンからのアトリビューションの精度を高めるために、Adjustトラッキングリンクにデバイス識別子を付加することをお勧めする。これにより、リンクをクリックしたユーザーの属性が決定的になる。
 
 {% tabs ローカル %}
-{% tab アンドロイド %}
-Androidの場合、Brazeは[Google Advertising ID収集（GAID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection)）にオプトインすることができる。GAIDはAdjust SDKとの統合によってネイティブに収集される。以下のリキッドロジックを利用することで、GAIDをAdjustクリックトラッキングリンクに含めることができる：
+{% tab Android %}
+Android の場合、Braze ではお客様が [Google 広告 ID (GAID) 収集]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection)にオプトインできます。GAID はまた、Adjust SDK 統合によってネイティブに収集されます。以下のリキッドロジックを利用することで、GAIDをAdjustクリックトラッキングリンクに含めることができる：
 {% raw %}
 ```
 {% if most_recently_used_device.${platform} == 'android' %}
@@ -136,7 +136,7 @@ idfv={{most_recently_used_device.${id}}}
 {% endtabs %}
 
 {% alert note %}
-**この推奨は純粋にオプションである。**<br>
+**この推奨事項の適用は完全に任意です。**<br>
 現在、クリックトラッキングのリンクにIDFVやGAIDなどのデバイス識別子を使用していない場合、または今後使用する予定がない場合でも、Adjustは確率的モデリングによってこれらのクリックを識別することができる。
 {% endalert %}
 
diff --git a/_lang/ja/_partners/message_orchestration/attribution/airbridge.md b/_lang/ja/_partners/message_orchestration/attribution/airbridge.md
index b66b220eb74..5072d5717b3 100644
--- a/_lang/ja/_partners/message_orchestration/attribution/airbridge.md
+++ b/_lang/ja/_partners/message_orchestration/attribution/airbridge.md
@@ -1,16 +1,16 @@
 ---
-nav_title: エアブリッジ
-article_title: エアブリッジ
+nav_title: Airbridge
+article_title: Airbridge
 alias: /partners/airbridge/
-description: "この参考記事では、ピープルベースのアトリビューションとインクリメンタル測定を提供し、デバイス、ID、プラットフォームを横断して真のマーケティング効果を測定するBrazeとAirbridgeのパートナーシップについて概説している。"
+description: "このリファレンス記事では、Braze と Airbridge のパートナーシップについて説明します。Airbridge は、デバイス、ID、プラットフォームにわたり真のマーケティング効果を測定するためのピープルベースドアトリビューションとインクリメンタル測定を提供します。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# エアブリッジ
+# Airbridge
 
-> [エアブリッジは](https://www.airbridge.io/)、モバイル・アトリビューション、インクリメンタリスト測定、マーケティング・ミックス・モデリングを通じて、真の成長源を発見するのに役立つ統合モバイル測定プラットフォームである。
+> [Airbridge](https://www.airbridge.io/) は、モバイル属性、インクリメンタルリスト測定、マーケティングミックスモデリングを通じて、真の成長の源泉を発見できる統一モバイル測定プラットフォームです。
 
 BrazeとAirbridgeの統合により、パーソナライズされたマーケティングキャンペーンを構築するために、AirbridgeからBrazeにオーガニックインストール以外のアトリビューションデータを渡すことができる。
 
@@ -18,23 +18,23 @@ BrazeとAirbridgeの統合により、パーソナライズされたマーケテ
 
 | 必要条件 | 説明 |
 |---|---|
-| エアブリッジアカウント | このパートナーシップを利用するには、エアブリッジのアカウントが必要である。 |
+| Airbridge アカウント | このパートナーシップを活用するには、Airbridge アカウントが必要です。 |
 | iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。 |
-| エアブリッジSDK | 必要なBraze SDKに加えて、Airbridge[Android](https://help.airbridge.io/en/developers/android-sdk)または[iOS](https://help.airbridge.io/en/developers/ios-sdk)SDKをインストールする必要がある。 |
+| Airbridge SDK | 必要なBraze SDKに加えて、Airbridge[Android](https://help.airbridge.io/en/developers/android-sdk)または[iOS](https://help.airbridge.io/en/developers/ios-sdk)SDKをインストールする必要がある。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### ステップ1:マップ・デバイスID
+### ステップ1:デバイス ID をマッピングする
 
-サーバー間の統合は、以下のコード・スニペットをアプリに含めることで有効になる。
+サーバー間統合を有効にするには、アプリに次のコードスニペットを組み込みます。
 
 #### Android
 
 Androidアプリをお持ちの場合は、一意のBrazeデバイスIDをAirbridgeに渡す必要がある。
 
 {% tabs %}
-{% tab アンドロイド %}
+{% tab Android %}
 {% subtabs %}
 {% subtab Java %}
 
@@ -85,7 +85,7 @@ override fun onCreate() {
 
 #### iOS
 
-iOSアプリの場合、useUUIDAsDeviceIdフィールドをfalseに設定することで、IDFVを収集することができる。設定されていない場合、iOSのアトリビューションはAirbridgeからBrazeに正確にマッピングされない可能性が高い。詳しくは「IDFVの収集」を参照のこと。
+iOSアプリの場合、useUUIDAsDeviceIdフィールドをfalseに設定することで、IDFVを収集することができる。設定されていない場合、iOSのアトリビューションはAirbridgeからBrazeに正確にマッピングされない可能性が高い。詳細については、「IDFV の収集」を参照してください。
 
 {% tabs %}
 {% tab iOS %}
@@ -130,7 +130,7 @@ didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
 #### React Native
 
 {% tabs %}
-{% tab タイプスクリプト %}
+{% tab TypeScript %}
 
 ```typescript
 Braze.getInstallTrackingId(function (error, brazeID) {
@@ -145,7 +145,7 @@ Braze.getInstallTrackingId(function (error, brazeID) {
 #### Cordova
 
 {% tabs %}
-{% tab タイプスクリプト %}
+{% tab TypeScript %}
 
 ```typescript
 AppboyPlugin.getDeviceId(function (brazeID) {
@@ -160,7 +160,7 @@ AppboyPlugin.getDeviceId(function (brazeID) {
 #### Flutter
 
 {% tabs %}
-{% tab タイプスクリプト %}
+{% tab TypeScript %}
 
 ```typescript
 BrazePlugin.getInstallTrackingId().then((brazeID) {
@@ -188,64 +188,64 @@ AirbridgeUnity.StartTracking()
 
 ### ステップ2:Brazeデータインポートキーを取得する
 
-Brazeで、**Partner Integrations**>**Technology Partnersに**移動し、**Airbridgeを**選択する。
+Brazeで \[**パートナー連携**] >\[**テクノロジーパートナー**] に移動し、\[**Airbridge**] を選択します。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。鍵の生成後、新しい鍵を作成したり、既存の鍵を無効にしたりすることができる。データインポートキーとRESTエンドポイントは、エアブリッジのダッシュボードでポストバックを設定する際に、次のステップで使用される。
+ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。Airbridge のダッシュボードでポストバックを設定する場合、次のステップでデータインポートキーと REST エンドポイントが使用されます。
 
 ![][1]
 
-### ステップ3:エアブリッジのダッシュボードでBrazeを設定する
+### ステップ3:Airbridge のダッシュボードで Braze を設定する
 
-1. Airbridgeで、左サイドバーの**Integrations > Third-party Integrationsに**移動し、**Brazeを**選択する。
+1. Airbridgeで、左サイドバーの **\[Integrations] > \[Third-party Integrations]** に移動し、\[**Braze**] を選択します。
 2. Brazeのダッシュボードで見つけたデータインポートキーとRESTエンドポイントを提供する。
-3. イベントの種類（Install EventまたはInstall & Deeplink Open Event）を選択し、保存する。
+3. イベントタイプ (\[Install Event] または \[Install & Deeplink Open Event]) を選択し、保存します。
 
 {% alert note %}
 ディープリンクオープンイベントにつながったキャンペーンのアトリビューションデータは、デバイスレベルで更新される。例えば、2人のユーザーが1つのデバイスを使用し、1人のユーザーがディープリンクを開くイベントを行った場合、このイベントのアトリビューションデータはもう1人のユーザーのデータにも反映される。
 {% endalert %}
 
-詳しい説明は[エアブリッジを](https://help.airbridge.io/en/guides/braze)参照のこと。
+詳細な手順については、[Airbridge](https://help.airbridge.io/en/guides/braze)を参照してください。
 
 ### ステップ4:統合を確認する
 
-BrazeがAirbridgeからアトリビューションデータを受信すると、BrazeのAirbridgeテクノロジーパートナーページのステータス接続インジケータが、"Not Connected "から "Connected "に変わる。最後に成功したリクエストのタイムスタンプも含まれる。
+Braze が Airbridge からアトリビューションデータを受信すると、Braze の Airbridge テクノロジーパートナーページのステータス接続インジケーターが \[接続されていません] から \[接続済み] に変わります。最後に成功したリクエストのタイムスタンプも含まれる。
 
-これは、帰属するインストールに関するデータを受け取るまでは起こらないことに注意してほしい。エアブリッジのポストバックから除外されるべきオーガニックインストールは、APIによって無視され、接続が成功したかどうかを判断する際にカウントされない。
+これは、紐づけられるインストールに関するデータを受け取るまでは発生しないことに注意してください。Airbridge のポストバックから除外する必要があるオーガニックインストールは、Braze の API では無視され、接続の確立が成功したかどうかを判断する際に考慮されません。
 
 ## 利用可能なデータフィールド
 
-Airbridgeは、以下のデータフィールド表に記載されている4種類のアトリビューションデータをBrazeに送信することができる。このデータはエアブリッジのダッシュボードで見ることができ、ユーザーインストールのアトリビューションとフィルタリングに使用される。
+Airbridge は、次のデータフィールドチャートにリストされている4種類のアトリビューションデータを Braze に送信できます。このデータは Airbridge ダッシュボードで確認でき、ユーザーのインストールアトリビューションおよびフィルタリングに使用されます。
 
 提案されたとおりに統合を設定すると、Brazeはインストールデータをセグメントフィルターにマッピングする。
 
-| エアブリッジのデータフィールド | ブレージングセグメントフィルター | 説明 |
+| Airbridge のデータフィールド | Braze セグメントフィルター | 説明 |
 | -------------------- | ---------------------| ---- |
-| `Channel` | 帰属ソースをインストールする | インストールまたはディープリンクが開かれたチャンネルは、以下のチャンネルに帰属する。 |
+| `Channel` | 帰属ソースをインストールする | インストールまたはディープリンクオープンが紐づけられるチャネル |
 | `Campaign` | アトリビューション・キャンペーンをインストールする | インストールまたはディープリンクのオープンが帰属するキャンペーン |
 | `Ad Group` | アトリビューション広告グループをインストールする | インストールまたはディープリンクのオープンが帰属する広告グループ |
 | `Ad Creative` | アトリビューション広告をインストールする | インストールまたはディープリンクが開かれた広告クリエイティブは、以下のものに起因する。 |
 
-ユーザーベースは、BrazeダッシュボードのInstall Attributionフィルタを使用して、アトリビューションデータによってセグメントすることができる。
+ユーザー群は、Braze ダッシュボードで インストールアトリビューションのフィルターを使用して、アトリビューションデータによってセグメント化できます。
 
 ![][2]
 
-## メタビジネス属性データ
+## Meta Business アトリビューションデータ
 
-Meta Businessキャンペーンのアトリビューションデータは、当社のパートナーを通じて入手することはできない。このメディアソースは、パートナーに帰属データを第三者と共有することを許可していないため、パートナーはそのデータをBrazeに送信することができない。
+Meta Businessキャンペーンのアトリビューションデータは、当社のパートナーから入手することはできません。このメディアソースは、パートナーにアトリビューションデータを第三者と共有することを許可していないため、パートナーはそのデータを Braze に送信できません。
 
-## BrazeのAirbridgeクリックトラッキングURL（オプション）
+## Braze での Airbridge クリックトラッキング URL (オプション)
 
-Brazeのキャンペーンでクリック追跡リンクを使用すると、どのキャンペーンがアプリのインストールやリエンゲージメントを促進しているかを簡単に確認できる。その結果、マーケティング活動をより効果的に測定できるようになり、ROIを最大化するためにどこにリソースを投資すべきか、データに基づいた意思決定ができるようになる。
+Brazeのキャンペーンでクリック追跡リンクを使用すると、どのキャンペーンがアプリのインストールやリエンゲージメントを促進しているかを簡単に確認できる。その結果、マーケティング活動をより効果的に測定できるようになり、ROI を最大化するためにどこにリソースを投資すべきかについて、データに基づいた意思決定ができるようになります。
 
-エアブリッジのクリック・トラッキング・リンクを利用するには、[エアブリッジを](https://help.airbridge.io/en/guides/creating-a-new-tracking-link)ご覧いただきたい。セットアップが完了したら、エアブリッジのクリックトラッキングリンクをBrazeのキャンペーンに直接挿入することができる。その後、エアブリッジは[確率論的なアトリビューション手法を使って](https://help.airbridge.io/en/guides/identity-matching)、リンクをクリックしたユーザーをアトリビュートする。Brazeキャンペーンからのアトリビューションの精度を高めるために、Airbridgeトラッキングリンクにデバイス識別子を付加することをお勧めする。これにより、リンクをクリックしたユーザーの属性が決定的になる。
+Airbridge のクリックトラッキングリンクの使用を開始するには、[Airbridge](https://help.airbridge.io/en/guides/creating-a-new-tracking-link) にアクセスします。セットアップが完了したら、エアブリッジのクリックトラッキングリンクをBrazeのキャンペーンに直接挿入することができる。その後、Airbridge は[確率的アトリビューション手法](https://help.airbridge.io/en/guides/identity-matching)を使用して、リンクをクリックしたユーザーを紐づけます。Brazeキャンペーンからのアトリビューションの精度を高めるために、Airbridgeトラッキングリンクにデバイス識別子を付加することをお勧めする。これにより、リンクをクリックしたユーザーの属性が決定的になる。
 
 {% tabs %}
-{% tab アンドロイド %}
-Androidの場合、Brazeは[Google Advertising ID収集（GAID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)）にオプトインすることができる。GAIDはまた、エアブリッジSDKの統合によってネイティブに収集される。以下のリキッドロジックを利用することで、エアブリッジのクリックトラッキングリンクにGAIDを含めることができる：
+{% tab Android %}
+Android の場合、Braze ではお客様が [Google 広告 ID (GAID) 収集]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)にオプトインできます。GAID はまた、Airbridge SDK統合によってネイティブに収集されます。以下のリキッドロジックを利用することで、エアブリッジのクリックトラッキングリンクにGAIDを含めることができる：
 {% raw %}
 ```
 {% if most_recently_used_device.${platform} == 'android' %}
@@ -269,8 +269,8 @@ idfv={{most_recently_used_device.${id}}}
 {% endtabs %}
 
 {% alert note %}
-**この推奨は純粋にオプションである。**<br>
-現在、クリックトラッキングのリンクにIDFVやGAIDなどのデバイス識別子を使用していない場合、または今後使用する予定がない場合でも、エアブリッジは確率的モデリングによってこれらのクリックを識別することができる。
+**この推奨事項の適用は完全に任意です。**<br>
+現在、クリックトラッキングリンクで IDFV やGAID などのデバイス識別子を使用していない場合、または今後使用する予定がない場合でも、Airbridge は確率的モデリングによってこれらのクリックを紐づけることができます。
 {% endalert %}
 
 [1]: {% image_buster /assets/img/airbridge/airbridge_integration_step_1.png %}
diff --git a/_lang/ja/_partners/message_orchestration/attribution/appsflyer/appsflyer.md b/_lang/ja/_partners/message_orchestration/attribution/appsflyer/appsflyer.md
index d71f24c098f..b80348b3230 100644
--- a/_lang/ja/_partners/message_orchestration/attribution/appsflyer/appsflyer.md
+++ b/_lang/ja/_partners/message_orchestration/attribution/appsflyer/appsflyer.md
@@ -23,21 +23,21 @@ BrazeとAppsFlyerの統合により、AppsFlyerのモバイルインストール
 | 必要条件 | 説明 |
 |---|---|
 | AppsFlyerアカウント | このパートナーシップを利用するには、AppsFlyerアカウントが必要である。 |
-| iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。これらの要件の詳細は、統合プロセスのステップ1に記載されている。 |
-| AppsFlyer SDK | 必要なBraze SDKに加えて、[AppsFlyer SDKを](https://dev.appsflyer.com/hc/docs/getting-started)インストールする必要がある。
-| Eメールドメインのセットアップ完了 | Brazeのオンボーディング時に、[IPとドメインのセットアップステップを]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/setting_up_ips_and_domains/)完了していること。 |
-| SSL証明書 | [SSL証明書が]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/ssl#acquiring-an-ssl-certificate)設定されていなければならない。 |
+| iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。これらの要件の詳細については、統合プロセスのステップ1を参照してください。 |
+| AppsFlyer SDK | 必要な Braze SDK に加えて、[AppsFlyer SDK](https://dev.appsflyer.com/hc/docs/getting-started) をインストールする必要があります。
+| Eメールドメインのセットアップ完了 | Braze オンボーディング時にメールを設定するには、[IP とドメインの設定ステップ]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/setting_up_ips_and_domains/)を完了している必要があります。 |
+| SSL証明書 | [SSL 証明書]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/ssl#acquiring-an-ssl-certificate) を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### ステップ1:マップ・デバイスID
+### ステップ1:デバイス ID をマッピングする
 
 #### Android
 
 Androidアプリをお持ちの場合、AppsFlyerに固有のBrazeデバイスIDを渡す必要がある。 
 
-Braze SDKが起動した後、AppsFlyer SDKの初期化コードの前。詳細はAppsFlyer[Android SDKインテグレーションガイドを](https://dev.appsflyer.com/hc/docs/integrate-android-sdk#initializing-the-android-sdk)参照のこと。
+次のコード行が正しい位置に挿入されていることを確認します。これは、Braze SDK の起動と AppsFlyer SDK の初期化コードの間です。詳細については、AppsFlyer の [Android SDK 統合ガイド](https://dev.appsflyer.com/hc/docs/integrate-android-sdk#initializing-the-android-sdk)を参照してください。
 
 ```java
 HashMap<String, Object> customData = new HashMap<String,Object>();
@@ -49,12 +49,12 @@ AppsFlyerLib.setAdditionalData(customData);
 #### iOS
 
 {% alert important %}
-2023年2月以前は、AppsFlyerのアトリビューション統合は、iOSアトリビューションデータを照合するための主要な識別子としてIDFVを使用していた。Objective-Cを使用しているBrazeの顧客が、インストール時にBraze`device_id` を取得し、AppsFlyerに送信する必要はない。
+2023年2月以前は、AppsFlyerのアトリビューション統合は、iOSアトリビューションデータを照合するための主要な識別子としてIDFVを使用していた。Objective-C を使用している Braze のお客様は、サービスが中断されることはないため、インストール時に Braze `device_id` を取得してAppsFlyer に送信する必要はありません。
 {% endalert%}
 
-Swift SDK v5.7.0+を使用している場合、相互識別子としてIDFVを引き続き使用したい場合は、`useUUIDAsDeviceId` フィールドが`false` に設定されていることを確認し、統合が中断されないようにする必要がある。 
+Swift SDK v5.7.0+ を使用しているお客様は、相互識別子として IDFV を引き続き使用するには、`useUUIDAsDeviceId` フィールドが `false` に設定されていることを確認する必要があります。これにより、統合が中断されることがなくなります。 
 
-`true` に設定した場合、BrazeがiOSアトリビュートと適切に一致するように、アプリインストール時にAppsFlyerにBraze`device_id` を渡すために、Swift用のiOSデバイスIDマッピングを実装する必要がある。
+`true` に設定している場合、Brazeが iOS アトリビューションを適切に照合できるように、アプリのインストール時に AppsFlye に Braze`device_id` を渡すために、Swift用の iOS デバイス ID マッピングを実装する必要があります。
 
 {% tabs ローカル %}
 {% tab Objective-C %}
@@ -72,7 +72,7 @@ Braze *braze = [[Braze alloc] initWithConfiguration:configurations];
 ```
 
 {% endtab %}
-{% tab スウィフト %}
+{% tab Swift %}
 
 ##### スイフト完了ハンドラ
 ```swift
@@ -111,48 +111,48 @@ AppsFlyer.setAdditionalData(customData);
 
 ### ステップ2:Brazeデータインポートキーを取得する
 
-Brazeで、**Partner Integrations**>**Technology Partnersに**移動し、**AppsFlyerを**選択する。 
+Brazeで \[**パートナー連携**] >\[**テクノロジーパートナー**] に移動し、\[**AppsFlyer**] を選択します。 
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。鍵の生成後、新しい鍵を作成したり、既存の鍵を無効にしたりすることができる。データインポートキーとRESTエンドポイントは、AppsFlyerのダッシュボードでポストバックを設定する際に、次のステップで使用される。<br><br>![AppsFlyer Technologyページで利用可能な「Data Import for Install Attribution」ボックス。このボックスに含まれるのは、データ・インポート・キーとRESTエンドポイントである。][4]{: style="max-width:70%;"}
+ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。データインポートキーとRESTエンドポイントは、AppsFlyerのダッシュボードでポストバックを設定する際に、次のステップで使用される。<br><br>![AppsFlyer テクノロジーページで利用可能な「インストールアトリビューションのデータインポート」ボックス。このボックスには、データインポートキーと REST エンドポイントが表示されている。][4]{: style="max-width:70%;"}
 
 ### ステップ3:AppsFlyerのダッシュボードでBrazeを設定する
 
-1. AppsFlyerで、左バーの**Integrated Partners**ページに移動する。次に**Brazeを**検索し、Brazeのロゴをクリックして設定ウィンドウを開く。
-2. **Integration "**タブで**"Activate Partner "**を選択する。
+1. AppsFlyer で、左側のバーの \[**Integrated Partners**] ページに移動します。次に **Braze** を検索し、Braze のロゴをクリックして設定ウィンドウを開きます。
+2. \[**Integration**] タブで \[**Activate Partner**] をオンにします。
 3. Brazeのダッシュボードで見つけたデータインポートキーとRESTエンドポイントを提供する。 
-4. **Advanced Privacyを**オフに切り替え、設定を保存する。
+4. \[**Advanced Privacy**] をオフに切り替え、設定を保存します。
 
-これらの手順に関する追加情報は、\[AppsFlyer's documentation][16] に掲載されている。
+これらの手順に関する追加情報は、\[AppsFlyer のドキュメント][16]に掲載されています。
 
 ### ステップ 4:統合を確認する
 
 BrazeがAppsFlyerからアトリビューションデータを受信すると、BrazeのAppsFlyerテクノロジーパートナーページのステータス接続インジケータが「未接続」から「接続済み」に変わる。最後に成功したリクエストのタイムスタンプも含まれる。 
 
-これは、帰属するインストールに関するデータを受け取るまでは起こらないことに注意してほしい。AppsFlyerのポストバックから除外されるべきオーガニックインストールは、APIによって無視され、接続が正常に確立されたかどうかを判断する際にカウントされない。
+これは、紐づけられるインストールに関するデータを受け取るまでは発生しないことに注意してください。AppsFlyerのポストバックから除外されるべきオーガニックインストールは、APIによって無視され、接続が正常に確立されたかどうかを判断する際にカウントされない。
 
-### ステップ 5: ユーザー属性データを見る
+### ステップ 5: ユーザーアトリビューションデータを確認する
 
 #### 利用可能なデータフィールド
 
 提案されたとおりに統合を構成したと仮定すると、Brazeはすべての非オーガニックインストールデータをセグメントフィルターにマッピングする。
 
-| AppsFlyer データフィールド | ブレージングセグメントフィルター |
+| AppsFlyer データフィールド | Braze セグメントフィルター |
 | -------------------- | --------------------- |
-| `media_source` | 帰属元 |
-| `campaign` | 帰属キャンペーン |
-| `af_adset` | 帰属アドグループ |
-| `af_ad` | 帰属広告 |
+| `media_source` | 紐づけられるソース |
+| `campaign` | 紐づけられるキャンペーン |
+| `af_adset` | 紐づけられる広告グループ |
+| `af_ad` | 紐づけられる広告 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-ユーザーベースは、BrazeダッシュボードのInstall Attributionフィルタを使用して、アトリビューションデータによってセグメントすることができる。
+ユーザー群は、Braze ダッシュボードで インストールアトリビューションのフィルターを使用して、アトリビューションデータによってセグメント化できます。
 
-![フィルターは4種類ある。1つ目は、"Install Attribution Source is network_val_0 "である。2つ目は、"Install Attribution Source is campaign_val_0 "である。3つ目は「アトリビューション・ソースのインストールはadgroup_val_0」である。4つ目は、「表示ソースをcreative_val_0に設定する」である。リストされたフィルターの横に、これらの属性ソースがどのようにユーザープロファイルに追加されるかを見ることができる。ユーザー情報ページの "Install Attribution "ボックスでは、Install Sourceはnetwork_val_0、campaignはcampaign_val_0などと表示される。][2]
+![4つのフィルターがある。1つ目は「Install Attribution Source is network_val_0」である。2つ目は「Install Attribution Source is campaign_val_0」である。3つ目は「Install Attribution Source is adgroup_val_0」である。4つ目は、「表示ソースをcreative_val_0に設定する」である。表示されているフィルターの横に、これらのアトリビューションソースがユーザープロファイルにどのように追加されるかが示されている。ユーザー情報ページの「インストールアトリビューション」ボックスで、インストールソースとしてnetwork_val_0、キャンペーンとしてcampaign_val_0が表示されている。][2]
 
-さらに、特定のユーザーのアトリビューションデータは、Brazeダッシュボードの各ユーザーのプロフィールで見ることができる。
+さらに、特定のユーザーのアトリビューションデータは、Braze ダッシュボードの各ユーザーのプロファイルで利用可能です。
 
 {% alert note %}
 FacebookおよびX（旧Twitter）キャンペーンのアトリビューションデータは、パートナーを通じて入手することはできない。これらのメディアソースは、そのパートナーが帰属データを第三者と共有することを許可していないため、当社のパートナーがそのデータをBrazeに送信することはできない。
@@ -160,25 +160,25 @@ FacebookおよびX（旧Twitter）キャンペーンのアトリビューショ
 
 ## AppsFlyerとメールサービスプロバイダを統合してディープリンクを実現する
 
-AppsFlyerは、メールサービスプロバイダ（ESP）としてSendGridとSparkPostの両方と統合し、ディープリンクとクリックトラッキングをサポートする。以下の手順に従って、選択したESPと統合する。
+AppsFlyerは、メールサービスプロバイダ（ESP）としてSendGridとSparkPostの両方と統合し、ディープリンクとクリックトラッキングをサポートする。次の手順に従って、使用するメールサービスプロバイダー (ESP) と統合します。
 
 {% alert tip %}
-ディープリンク（アプリやウェブサイト内の特定のページや場所にユーザーを誘導するリンク）は、ユーザーに合わせてカスタマイズされたユーザー体験を作り出すために使用される。広く使用されている一方で、ユーザーデータの収集に使用されるもう一つの重要な機能であるクリックトラッキングでEメールによるディープリンクを使用する場合、問題が発生する可能性がある。これらの問題は、ESPがディープリンクをクリックを記録するドメインでラップし、元のリンクを壊してしまうことに起因する。そのため、ディープリンクをサポートするには、追加の設定が必要になる。AppsFlyerをSendGridまたはSparkPostと統合することで、これらの問題を回避できる。このトピックについては、[ユニバーサルリンクとアプリリンクで]({{site.baseurl}}/help/help_articles/email/universal_links/)詳しく説明している。
+ディープリンク（アプリやウェブサイト内の特定のページや場所にユーザーを誘導するリンク）は、ユーザーに合わせてカスタマイズされたユーザー体験を作り出すために使用される。広く使用されている一方で、ユーザーデータの収集に使用されるもう一つの重要な機能であるクリックトラッキングでEメールによるディープリンクを使用する場合、問題が発生する可能性がある。これらの問題は、ESPがディープリンクをクリックを記録するドメインでラップし、元のリンクを壊してしまうことに起因する。そのため、ディープリンクをサポートするには、追加の設定が必要になる。AppsFlyerをSendGridまたはSparkPostと統合することで、これらの問題を回避できる。このトピックの詳細については、「[ユニバーサルリンクとアプリリンク]({{site.baseurl}}/help/help_articles/email/universal_links/)」を参照してください。
 {% endalert %}
 
 ### ステップ1:AppsFlyerでOneLinkを設定する
 
 1. AppsFlyerで、メールキャンペーン用のOneLinkテンプレートを選択する。テンプレートがユニバーサルリンク（iOS）またはアプリリンク（Android）をサポートしていることを確認する。 
-2. OneLinkでディープリンクをサポートするようにアプリを設定する。OneLinkをサポートするアプリの設定の詳細については、[AppsFlyerのドキュメントを](https://dev.appsflyer.com/hc/docs/dl_work_flow#initial-setup)参照のこと。
+2. OneLink でディープリンクをサポートするようにアプリを設定します。OneLinkをサポートするアプリの設定の詳細については、[AppsFlyerのドキュメントを](https://dev.appsflyer.com/hc/docs/dl_work_flow#initial-setup)参照のこと。
 
-### ステップ2:ユニバーサルリンクとApp Linksをサポートするようにアプリを設定する
+### ステップ2:ユニバーサルリンクとアプリリンクをサポートするようにアプリを設定する
 
 ユニバーサルリンク（iOS）またはアプリリンク（Android）は、クリックすると指定されたアプリを開くことがデバイスのオペレーティングシステムによって許可されている。
 
-ユニバーサルリンクとApp Linksをサポートするには、以下の手順を実行する。
+ユニバーサルリンクとアプリリンクをサポートするには、次の手順を実行します。
 
 {% tabs ローカル %}
-{% tab センドグリッド %}
+{% tab SendGrid %}
 {% subtabs %}
 {% subtab iOS %}
 Apple App Site Association (AASA)のファイルホスティングを設定し、Eメールでユニバーサルリンクを有効にする。
@@ -187,36 +187,36 @@ Apple App Site Association (AASA)のファイルホスティングを設定し
     * ユニバーサルリンクでOneLinkを設定している場合、OneLinkに関連付けられたAASAファイルがすでにあるかもしれない。AASAファイルを入手するには、以下を実行する：
         * OneLinkテンプレートのOneLinkサブドメインをコピーする。テンプレートがユニバーサルリンクをサポートしていることを確認する。
         * それを以下のURLのプレースホルダーの代わりに貼り付ける： `<OneLinkSubdomain>.onelink.me/.well-known/apple-app-site-association`
-        * AASAファイルをダウンロードするには、OneLinkのURLをブラウザのアドレスバーに貼り付け、**Enter**キーを押す。ファイルはあなたのコンピューターにダウンロードされ、テキストエディタを使ってその内容を開いて見ることができる。
+        * AASAファイルをダウンロードするには、OneLinkのURLをブラウザのアドレスバーに貼り付け、**Enter**キーを押す。ファイルがコンピューターにダウンロードされます。任意のテキストエディターを使用してこのファイルを開き、その内容を表示できます。
     * [アップルのユニバーサルリンクに関するガイドでは](https://developer.apple.com/documentation/xcode/allowing_apps_and_websites_to_link_to_your_content)、AASAファイルの作成方法が説明されている。
-2. AASAファイルをクリック録音ドメインサーバーにホストする。ファイルは`click.example.com/.well-known/apple-app-site-association` というパスにホストされていなければならない。 
+2. クリックレコーディングドメインサーバーで AASA ファイルをホストします。ファイルが `click.example.com/.well-known/apple-app-site-association` というパスでホストされている必要があります。 
 
-[SendGrid](https://docs.sendgrid.com/ui/sending-email/universal-links)用のAASAファイルを設定し、AASAファイルをホストするCDNサービスを設定する方法については、[SendGridのドキュメントを](https://docs.sendgrid.com/ui/sending-email/universal-links)参照のこと。
+SendGrid 用に AASA ファイルを設定し、AASA ファイルをホストするように CDN サービスを設定する方法については、[SendGrid ドキュメント](https://docs.sendgrid.com/ui/sending-email/universal-links) を参照してください。
 
 {% alert important %}
 いったんAASAファイルがホストされると、OneLinkコンフィギュレーションを変更（修正または交換）する場合は、新しいAASAファイルを生成する必要がある。
 {% endalert %}
 {% endsubtab %}
 {% subtab Android %}
-デジタルアセットリンクファイルのホスティングを設定し、メール内のアプリリンクを有効にする。
+デジタルアセットリンクファイルのホスティングを設定して、メールでアプリケーションリンクを有効にします。
 
-1. 以下のいずれかの方法でデジタルアセットリンクファイルを入手する：
-    * アプリリンクでOneLinkをセットアップしている場合、OneLinkに関連付けられているデジタルアセットリンクファイルがすでにあるかもしれない。このファイルを入手するには、以下のようにする：
+1. 以下のいずれかの方法でデジタルアセットリンクファイルを入手します。
+    * アプリリンクで OneLink を設定している場合は、OneLink に関連付けられているデジタルアセットリンクファイルがすでに存在している可能性があります。このファイルを入手するには、以下のようにする：
         * OneLinkテンプレートのOneLinkサブドメインをコピーする。テンプレートがApp Linksをサポートしていることを確認する。
-        * OneLinkのURLの最後に`/.well-known/assetlinks.json` 。
-        * デジタルアセットリンクファイルをダウンロードするには、OneLinkのURLをブラウザのアドレスバーに貼り付け、**Enter**キーを押す。例えば、`https://<OneLinkSubdomain>.onelink.me/.well-known/assetlinks.json` 。ファイルはあなたのコンピューターにダウンロードされ、テキストエディタを使ってその内容を開いて見ることができる。
-    * [AndroidのApp Linksガイドでは](https://developer.android.com/studio/write/app-link-indexing)、Digital Asset Linksファイルの作成方法を説明している。
-2. デジタルアセットリンクファイルをクリックレコーディングドメインサーバーにホストする。ファイルは`click.example.com/.well-known/apple-app-site-association` というパスにホストされていなければならない。
+        * OneLink URL の末尾に`/.well-known/assetlinks.json` を追加します。
+        * デジタルアセットリンクファイルをダウンロードするには、OneLinkのURLをブラウザのアドレスバーに貼り付け、**Enter**キーを押す。たとえば `https://<OneLinkSubdomain>.onelink.me/.well-known/assetlinks.json` です。ファイルがコンピューターにダウンロードされます。任意のテキストエディターを使用してこのファイルを開き、その内容を表示できます。
+    * [Android のアプリリンクのガイド](https://developer.android.com/studio/write/app-link-indexing)で、デジタルアセットリンクファイルの作成方法が説明されています。
+2. クリックレコーディングドメインサーバーでデジタルアセットリンクファイルをホストします。ファイルが `click.example.com/.well-known/apple-app-site-association` というパスでホストされている必要があります。
 
-[SendGrid](https://docs.sendgrid.com/ui/sending-email/universal-links)用のDigital Asset Linksファイルの設定方法と、Digital Asset LinksファイルをホストするCDNサービスの設定方法については、[SendGridのドキュメントを](https://docs.sendgrid.com/ui/sending-email/universal-links)参照のこと。
+SendGrid 用にデジタルアセットリンクファイルを設定し、デジタルアセットリンクファイルをホストするように CDN サービスを設定する方法については、[SendGrid ドキュメント](https://docs.sendgrid.com/ui/sending-email/universal-links) を参照してください。
 
 {% alert important %}
-デジタルアセットリンクファイルがホスティングされると、OneLinkコンフィギュレーションを変更（修正または交換）する場合は、新しいファイルを生成する必要がある。
+デジタルアセットリンクファイルがホストされたら、OneLink 設定を変更 (修正または置換) するには、新しいファイルを生成する必要があります。
 {% endalert %}
 {% endsubtab %}
 {% endsubtabs %}
 {% endtab %}
-{% tab スパークポスト %}
+{% tab SparkPost %}
 {% subtabs %}
 {% subtab iOS %}
 #### ステップ 2a: AASAファイルのホスティングを設定する
@@ -226,42 +226,42 @@ Apple App Site Association (AASA)のファイルホスティングを設定し
     * ユニバーサルリンクでOneLinkを設定している場合、OneLinkに関連付けられたAASAファイルがすでにあるかもしれない。AASAファイルを入手するには、以下を実行する：
         * OneLinkテンプレートのOneLinkサブドメインをコピーする。テンプレートがユニバーサルリンクをサポートしていることを確認する。
         * それを以下のURLのプレースホルダーの代わりに貼り付ける： `<OneLinkSubdomain>.onelink.me/.well-known/apple-app-site-association`
-        * AASAファイルをダウンロードするには、OneLinkのURLをブラウザのアドレスバーに貼り付け、**Enter**キーを押す。ファイルはあなたのコンピューターにダウンロードされ、テキストエディタを使ってその内容を開いて見ることができる。
+        * AASAファイルをダウンロードするには、OneLinkのURLをブラウザのアドレスバーに貼り付け、**Enter**キーを押す。ファイルがコンピューターにダウンロードされます。任意のテキストエディターを使用してこのファイルを開き、その内容を表示できます。
     * [アップルのユニバーサルリンクに関するガイドでは](https://developer.apple.com/documentation/xcode/allowing_apps_and_websites_to_link_to_your_content)、AASAファイルの作成方法が説明されている。
-2. AASAファイルをクリック録音ドメインサーバーにホストする。ファイルは`click.example.com/.well-known/apple-app-site-association` というパスにホストされていなければならない。 
+2. クリックレコーディングドメインサーバーで AASA ファイルをホストします。ファイルが `click.example.com/.well-known/apple-app-site-association` というパスでホストされている必要があります。 
 
-[SparkPost](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve)用のAASAファイルを設定し、カスタムリンクサブパスを設定する方法については、[SparkPostのドキュメントを](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve)参照のこと。
+SparkPost 用の AASA ファイルを設定し、カスタムリンクサブパスを設定する方法については、[SparkPost のドキュメント](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve)を参照してください。
 
 {% alert important %}
 いったんAASAファイルがホストされると、OneLinkコンフィギュレーションを変更（修正または交換）する場合は、新しいAASAファイルを生成する必要がある。
 {% endalert %}
 
 #### ステップ 2b: クリック追跡ドメインをAASAファイルホストにリダイレクトする
-[電子メールの設定]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/setting_up_ips_and_domains/)中に、DNSサーバーにCNAMEレコードを作成した。Brazeでクリックトラッキングドメインを確認した後、以下の手順を実行する。 
+[電子メールの設定]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/setting_up_ips_and_domains/)中に、DNSサーバーにCNAMEレコードを作成した。Braze でクリックトラッキングドメインを確認した後で、次の手順を実行します。 
 
 1. サブドメインをSparkPostドメインにリダイレクトするCNAMEレコードを削除する。
 2. 上記で削除したレコードの代わりに、クリック追跡ドメインをアプリのAASAファイルをホストしているCDNにリダイレクトするCNAMEレコードを作成する。
 {% endsubtab %}
 {% subtab Android %}
-#### ステップ 2a: デジタルアセットリンクのファイルホスティングを設定する
-デジタルアセットリンクファイルのホスティングを設定し、メール内のアプリリンクを有効にする。
+#### ステップ 2a: デジタルアセットリンクファイルのホスティングを設定する
+デジタルアセットリンクファイルのホスティングを設定して、メールでアプリケーションリンクを有効にします。
 
-1. 以下のいずれかの方法でデジタルアセットリンクファイルを入手する：
-    * アプリリンクでOneLinkをセットアップしている場合、OneLinkに関連付けられているデジタルアセットリンクファイルがすでにあるかもしれない。このファイルを入手するには、以下のようにする：
+1. 以下のいずれかの方法でデジタルアセットリンクファイルを入手します。
+    * アプリリンクで OneLink を設定している場合は、OneLink に関連付けられているデジタルアセットリンクファイルがすでに存在している可能性があります。このファイルを入手するには、以下のようにする：
         * OneLinkテンプレートのOneLinkサブドメインをコピーする。テンプレートがApp Linksをサポートしていることを確認する。
-        * OneLinkのURLの最後に`/.well-known/assetlinks.json` 。
-        * デジタルアセットリンクファイルをダウンロードするには、OneLinkのURLをブラウザのアドレスバーに貼り付け、**Enter**キーを押す。例えば、`https://<OneLinkSubdomain>.onelink.me/.well-known/assetlinks.json` 。ファイルはあなたのコンピューターにダウンロードされ、テキストエディタを使ってその内容を開いて見ることができる。
-    * [AndroidのApp Linksガイドでは](https://developer.android.com/studio/write/app-link-indexing)、Digital Asset Linksファイルの作成方法を説明している。
-2. デジタルアセットリンクファイルをクリックレコーディングドメインサーバーにホストする。ファイルは`click.example.com/.well-known/apple-app-site-association` というパスにホストされていなければならない。
+        * OneLink URL の末尾に`/.well-known/assetlinks.json` を追加します。
+        * デジタルアセットリンクファイルをダウンロードするには、OneLinkのURLをブラウザのアドレスバーに貼り付け、**Enter**キーを押す。たとえば `https://<OneLinkSubdomain>.onelink.me/.well-known/assetlinks.json` です。ファイルがコンピューターにダウンロードされます。任意のテキストエディターを使用してこのファイルを開き、その内容を表示できます。
+    * [Android のアプリリンクのガイド](https://developer.android.com/studio/write/app-link-indexing)で、デジタルアセットリンクファイルの作成方法が説明されています。
+2. クリックレコーディングドメインサーバーでデジタルアセットリンクファイルをホストします。ファイルが `click.example.com/.well-known/apple-app-site-association` というパスでホストされている必要があります。
 
-[SparkPost](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve)用のDigital Asset Linksファイルを設定し、カスタムリンクサブパスを設定する方法については、[SparkPostのドキュメントを](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve)参照のこと。
+SendGrid 用にデジタルアセットリンクファイルを設定し、カスタムリンクサブパスを設定する方法については、[SparkPost のドキュメント](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve)を参照してください。
 
 {% alert important %}
-デジタルアセットリンクファイルがホスティングされると、OneLinkコンフィギュレーションを変更（修正または交換）する場合は、新しいファイルを生成する必要がある。
+デジタルアセットリンクファイルがホストされたら、OneLink 設定を変更 (修正または置換) するには、新しいファイルを生成する必要があります。
 {% endalert %}
 
 #### ステップ 2b: クリックトラッキングドメインをデジタルアセットリンクファイルホストにリダイレクトする
-[電子メールの設定]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/setting_up_ips_and_domains/)中に、DNSサーバーにCNAMEレコードを作成した。Brazeでクリックトラッキングドメインを確認した後、以下の手順を実行する。 
+[電子メールの設定]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/setting_up_ips_and_domains/)中に、DNSサーバーにCNAMEレコードを作成した。Braze でクリックトラッキングドメインを確認した後で、次の手順を実行します。 
 
 1. サブドメインをSparkPostドメインにリダイレクトするCNAMEレコードを削除する。
 2. 上記で削除したレコードの代わりに、アプリのDigital Asset LinksファイルをホストしているCDNにクリック追跡ドメインをリダイレクトするCNAMEレコードを作成する。
@@ -274,29 +274,29 @@ Apple App Site Association (AASA)のファイルホスティングを設定し
 ### ステップ3:ディープリンクをサポートするようにAppsFlyer SDKを設定する
 
 {% tabs ローカル %}
-{% tab センドグリッド %}
+{% tab SendGrid %}
 {% subtabs %}
 {% subtab iOS %}
-#### ステップ3a：AASAファイルをサポートするようにSDKを設定する。
-クリック録音ドメインでAASAファイルをホストした後、AASAファイルをサポートするようにAppsFlyer SDKを設定する。
+#### ステップ3a:AASAファイルをサポートするようにSDKを設定する。
+クリックレコーディングドメインで AASA ファイルをホストした後で、AASA ファイルをサポートするように AppsFlyer SDK を設定します。
 
 1. Xcodeでプロジェクトを選択する。
-2. **能力を**選択する**。**
-3. **関連ドメインを**オンにする**。**
-4. **を**クリックし、クリックするドメインを入力する。例えば、`applinks:click.example.com` 。
-ユニバーサルリンクがクリックされると、アプリが開かれ、SDKが起動する。アプリがクリックドメインの背後にあるOneLinkを抽出し、ディープリンクを解決できるようにするには、以下を実行する：
+2. \[**Capabilities**] を選択します。
+3. \[**Associated Domains.**] をオンにします。
+4. \[**+**] をクリックし、クリックドメインを入力します。たとえば `applinks:click.example.com` です。
+ユニバーサルリンクがクリックされると、アプリが開き、SDK が開始されます。アプリがクリックドメインの背後にあるOneLinkを抽出し、ディープリンクを解決できるようにするには、以下を実行する：
 
-#### ステップ3b：ディープリンクのデータを扱う
-1. SDK APIにクリック記録ドメインを提供する [`resolveDeepLinkURLs`](https://dev.appsflyer.com/hc/docs/ios-sdk-reference-appsflyerlib#resolvedeeplinkurls).このAPIはSDKの初期化の前にコールされる必要がある。 `AppsFlyerLib.shared().resolveDeepLinkURLs = ["click.example.com","spgo.io"]`
-2. APIを使用する [`onAppOpenAttribution`](https://dev.appsflyer.com/hc/docs/ios-sdk-reference-appsflyerlibdelegate#onappopenattribution)APIを使用して、ディープリンク・パラメータを取得し、ディープリンク・データを処理する。
+#### ステップ3b:ディープリンクのデータを扱う
+1. SDK API [`resolveDeepLinkURLs`](https://dev.appsflyer.com/hc/docs/ios-sdk-reference-appsflyerlib#resolvedeeplinkurls) にクリックレコーディングドメインを指定します。このAPIはSDKの初期化の前にコールされる必要がある。 `AppsFlyerLib.shared().resolveDeepLinkURLs = ["click.example.com","spgo.io"]`
+2. ディープリンクパラメーターを取得し、ディープリンクデータを処理するには、[`onAppOpenAttribution`](https://dev.appsflyer.com/hc/docs/ios-sdk-reference-appsflyerlibdelegate#onappopenattribution) API を使用します。
 
 {% endsubtab %}
 {% subtab Android %}
-#### ステップ3a：デジタルアセットリンクファイルをサポートするようにSDKを設定する。
+#### ステップ3a:デジタルアセットリンクファイルをサポートするようにSDK を設定する
 
-前のステップでデジタルアセットリンクファイルをクリック録音ドメインにホストしたら、そのファイルをサポートするようにSDKを設定する。
+前の手順でクリックレコーディングドメインでデジタルアセットリンクファイルをホストした後で、ファイルをサポートするように SDK を設定します。
 
-Androidマニフェストで、ディープリンクしたいアクティビティのアクティビティタグに、クリックドメインホストと接頭辞を追加する。
+Android マニフェストで、ディープリンクのリンク先にするアクティビティのアクティビティタグに、クリックドメインホストと任意の接頭辞を追加します。
 
 ```xml
 <activity android:name=".DeepLinkActivity">
@@ -313,34 +313,34 @@ Androidマニフェストで、ディープリンクしたいアクティビテ
   </activity>
 ```
 
-#### ステップ3b：ディープリンクのデータを扱う
-アプリリンクをクリックすると、アプリが開かれ、SDKが起動する。 アプリがクリックドメインの背後にあるOneLinkを抽出し、ディープリンクを解決できるようにするには、SDKメソッドでクリックドメインをリストする。 [`setResolveDeepLinkURLs`](https://support.appsflyer.com/hc/en-us/articles/4408735106193#resolve-wrapped-deep-link-urls).このプロパティはSDK初期化の前に設定する必要がある。`AppsFlyerLib.getInstance().setResolveDeepLinkURLs("clickdomain.com", "myclickdomain.com", "anotherclickdomain.com");`
+#### ステップ3b:ディープリンクのデータを扱う
+アプリリンクがクリックされると、アプリが開き、SDK が開始されます。 アプリがクリックドメインの背後にある OneLink を抽出し、ディープリンクを解決できるようにするには、SDK メソッド [`setResolveDeepLinkURLs`](https://support.appsflyer.com/hc/en-us/articles/4408735106193#resolve-wrapped-deep-link-urls) にクリックドメインをリストします。このプロパティはSDK初期化の前に設定する必要がある。`AppsFlyerLib.getInstance().setResolveDeepLinkURLs("clickdomain.com", "myclickdomain.com", "anotherclickdomain.com");`
 {% endsubtab %}
 {% endsubtabs %}
 {% endtab %}
-{% tab スパークポスト %}
+{% tab SparkPost %}
 {% subtabs %}
 {% subtab iOS %}
-#### ステップ3a：AASAファイルをサポートするようにSDKを設定する。
-クリック録音ドメインでAASAファイルをホストした後、AASAファイルをサポートするようにSDKを設定する。
+#### ステップ3a:AASAファイルをサポートするようにSDKを設定する。
+クリックレコーディングドメインで AASA ファイルをホストした後で、AASA ファイルをサポートするように SDK を設定します。
 
 1. Xcodeでプロジェクトを選択する。
-2. **能力を**選択する**。**
-3. **関連ドメインを**オンにする**。**
-4. **を**クリックし、クリックするドメインを入力する。例えば、`applinks:click.example.com` 。
-
-#### ステップ3b：ディープリンクのデータを扱う
-ユニバーサルリンクがクリックされると、アプリが開かれ、SDKが起動する。SDKがクリックドメインの背後にあるOneLinkを抽出できるようにするには、以下を実行する：
-1. SDKプロパティにクリックドメインをリストする  [`resolveDeepLinkURLs`](https://dev.appsflyer.com/hc/docs/ios-sdk-reference-appsflyerlib#resolvedeeplinkurls).SDK初期化の前にこのプロパティを必ず設定すること。
-2. リスト <em>spgo.io</em>がリストされたドメインの1つであることを確認する。SparkPostはこのドメインを所有しており、リダイレクトフローの一部となっている。 `AppsFlyerLib.shared().resolveDeepLinkURLs = ["click.example.com","spgo.io"]`
-3. APIを使用する [`onAppOpenAttribution`](https://dev.appsflyer.com/hc/docs/ios-sdk-reference-appsflyerlibdelegate#onappopenattribution)APIを使用して、ディープリンク・パラメータを取得し、ディープリンク・データを処理する。
+2. \[**Capabilities**] を選択します。
+3. \[**Associated Domains.**] をオンにします。
+4. \[**+**] をクリックし、クリックドメインを入力します。たとえば `applinks:click.example.com` です。
+
+#### ステップ3b:ディープリンクのデータを扱う
+ユニバーサルリンクがクリックされると、アプリが開き、SDK が開始されます。クリックドメインの背後にある OneLink を SDK が抽出できるようにするには、次の手順を実行します。
+1. SDK プロパティ [`resolveDeepLinkURLs`](https://dev.appsflyer.com/hc/docs/ios-sdk-reference-appsflyerlib#resolvedeeplinkurls) にクリックドメインをリストします。SDK初期化の前にこのプロパティを必ず設定すること。
+2. リスト <em>spgo.io</em> が、リストしたドメインの1つであることを確認します。SparkPost はこのドメインを所有しており、これはリダイレクトフローの一部です。`AppsFlyerLib.shared().resolveDeepLinkURLs = ["click.example.com","spgo.io"]`
+3. ディープリンクパラメーターを取得し、ディープリンクデータを処理するには、[`onAppOpenAttribution`](https://dev.appsflyer.com/hc/docs/ios-sdk-reference-appsflyerlibdelegate#onappopenattribution) API を使用します。
 {% endsubtab %}
 {% subtab Android %}
-#### ステップ3a：デジタルアセットリンクファイルをサポートするようにSDKを設定する。
+#### ステップ3a:デジタルアセットリンクファイルをサポートするようにSDK を設定する
 
-前のステップでデジタルアセットリンクファイルをクリック録音ドメインにホストしたら、そのファイルをサポートするようにSDKを設定する。
+前の手順でクリックレコーディングドメインでデジタルアセットリンクファイルをホストした後で、ファイルをサポートするように SDK を設定します。
 
-Androidマニフェストで、ディープリンクしたいアクティビティのアクティビティタグに、クリックドメインホストと接頭辞を追加する。
+Android マニフェストで、ディープリンクのリンク先にするアクティビティのアクティビティタグに、クリックドメインホストと任意の接頭辞を追加します。
 
 ```xml
 <activity android:name=".DeepLinkActivity">
@@ -357,27 +357,27 @@ Androidマニフェストで、ディープリンクしたいアクティビテ
   </activity>
 ```
 
-#### ステップ3b：アプリリンクのデータを扱う
-アプリリンクをクリックすると、アプリが開かれ、SDKが起動する。アプリがクリックドメインの背後にあるOneLinkを抽出し、ディープリンクを解決できるようにするには、以下を実行する：
+#### ステップ3b:アプリリンクのデータを処理する
+アプリリンクがクリックされると、アプリが開き、SDK が開始されます。アプリがクリックドメインの背後にあるOneLinkを抽出し、ディープリンクを解決できるようにするには、以下を実行する：
 
-1. SDKメソッドのクリックドメインをリストする [`setResolveDeepLinkURLs`](https://support.appsflyer.com/hc/en-us/articles/4408735106193#resolve-wrapped-deep-link-urls).このプロパティはSDK初期化の前に設定する必要がある。
-2. リスト *spgo.io*がリストされたドメインの1つであることを確認する。SparkPostはこのドメインを所有しており、リダイレクトフローの一部となっている。 `AppsFlyerLib.getInstance().setResolveDeepLinkURLs("clickdomain.com", "myclickdomain.com", "spgo.io");`
+1. SDK メソッド [`setResolveDeepLinkURLs`](https://support.appsflyer.com/hc/en-us/articles/4408735106193#resolve-wrapped-deep-link-urls) にクリックドメインをリストします。このプロパティはSDK初期化の前に設定する必要がある。
+2. リスト *spgo.io* が、リストしたドメインの1つであることを確認します。SparkPost はこのドメインを所有しており、これはリダイレクトフローの一部です。`AppsFlyerLib.getInstance().setResolveDeepLinkURLs("clickdomain.com", "myclickdomain.com", "spgo.io");`
 {% endsubtab %}
 {% endsubtabs %}
 {% endtab %}
 {% endtabs %}
 
-統合ステップが完了したら、OneLinkを使ってディープリンクを送信することで、品質保証とトラブルシューティングを行うことができる。OneLinkの使い方の詳細については、[AppsFlyerのドキュメントを](https://support.appsflyer.com/hc/en-us/articles/360001437497-Integrating-AppsFlyer-and-Braze#step-3-sending-your-first-email::2ffdb79a)参照のこと。
+統合手順が完了したら、OneLink を使用してディープリンクを送信することで、品質保証とトラブルシューティングを実行できます。OneLinkの使い方の詳細については、[AppsFlyerのドキュメントを](https://support.appsflyer.com/hc/en-us/articles/360001437497-Integrating-AppsFlyer-and-Braze#step-3-sending-your-first-email::2ffdb79a)参照のこと。
 
 ### BrazeのAppsFlyerクリックトラッキングURL（オプション）
 
-AppsFlyerの[OneLinkアトリビューションリンクは](https://support.AppsFlyer.com/hc/en-us/articles/360001294118)、Brazeのキャンペーンでプッシュ、Eメールなどで使用できる。これにより、BrazeのキャンペーンからインストールやリエンゲージメントのアトリビューションデータをAppsFlyerに送り返すことができる。その結果、マーケティング活動をより効果的に測定し、データに基づいた意思決定を行うことができるようになる。
+プッシュやメールなどの Braze キャンペーンで AppsFlyer の[OneLink アトリビューションリンク](https://support.AppsFlyer.com/hc/en-us/articles/360001294118) を使用できます。これにより、BrazeのキャンペーンからインストールやリエンゲージメントのアトリビューションデータをAppsFlyerに送り返すことができる。その結果、マーケティング活動をより効果的に測定し、データに基づいた意思決定を行うことができるようになる。
 
 AppsFlyerでOneLinkトラッキングURLを作成し、Brazeキャンペーンに直接挿入するだけでよい。その後、AppsFlyerは[確率的アトリビューション手法を](https://support.AppsFlyer.com/hc/en-us/articles/207447053-Attribution-model-explained#probabilistic-modeling)使用して、リンクをクリックしたユーザーをアトリビュートする。Brazeキャンペーンからの帰属の精度を高めるために、AppsFlyerのトラッキングリンクにデバイス識別子を付加することを推奨する。これにより、リンクをクリックしたユーザーの属性が決定的になる。
 
 {% tabs ローカル %}
-{% tab アンドロイド %}
-Androidの場合、Brazeは[Google Advertising ID収集（GAID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)）にオプトインすることができる。GAIDはまた、AppsFlyer SDKの統合によってネイティブに収集される。以下のリキッドロジックを利用することで、AppsFlyerのクリックトラッキングリンクにGAIDを含めることができる：
+{% tab Android %}
+Android の場合、Braze ではお客様が [Google 広告 ID (GAID) 収集]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)にオプトインできます。GAID はまた、AppsFlyer SDK統合によってネイティブに収集されます。以下のリキッドロジックを利用することで、AppsFlyerのクリックトラッキングリンクにGAIDを含めることができる：
 {% raw %}
 ```
 {% if most_recently_used_device.${platform} == 'android' %}
diff --git a/_lang/ja/_partners/message_orchestration/attribution/branch.md b/_lang/ja/_partners/message_orchestration/attribution/branch.md
index bfac74ae5d7..56ef86ce3a2 100644
--- a/_lang/ja/_partners/message_orchestration/attribution/branch.md
+++ b/_lang/ja/_partners/message_orchestration/attribution/branch.md
@@ -1,5 +1,5 @@
 ---
-nav_title: 支店
+nav_title: Branch
 config_only: true
 noindex: true
 layout: blank_config
diff --git a/_lang/ja/_partners/message_orchestration/attribution/branch/branch_for_attribution.md b/_lang/ja/_partners/message_orchestration/attribution/branch/branch_for_attribution.md
index 868bcea8521..5ea4251f14b 100644
--- a/_lang/ja/_partners/message_orchestration/attribution/branch/branch_for_attribution.md
+++ b/_lang/ja/_partners/message_orchestration/attribution/branch/branch_for_attribution.md
@@ -1,6 +1,6 @@
 ---
-nav_title: 帰属ブランチ
-article_title: 帰属ブランチ
+nav_title: Branch (アトリビューション)
+article_title: Branch (アトリビューション)
 alias: /partners/branch_for_attribution/
 description: "この参考記事では、あらゆるデバイス、チャネル、プラットフォームでの獲得、エンゲージメント、測定を支援するモバイルリンクプラットフォームであるBrazeとBranchのパートナーシップについて概説している。"
 page_type: partner
@@ -8,21 +8,21 @@ search_tag: Partner
 
 ---
 
-# 帰属のためのブランチ {#branch}
+# Branch (アトリビューション) {#branch}
 
 {% multi_lang_include video.html id="PwGKqfwV-Ss" align="right" %}
 
-> モバイルリンクプラットフォームである[Branchは](https://docs.branch.io/pages/integrations/braze/)、すべてのユーザータッチポイントを総合的に把握することで、あらゆるデバイス、チャネル、プラットフォームでの獲得、エンゲージメント、測定を支援する。
+> [Branch](https://docs.branch.io/pages/integrations/braze/) はあらゆるデバイス、チャネル、プラットフォームでの獲得、エンゲージメント、測定を支援するモバイルリンクプラットフォームで、すべてのユーザータッチポイントの一元的なビューを提供しています。
 
-BrazeとBranchの統合は、ユーザーがいつ、どこで獲得されたかを正確に理解し、強固なアトリビューションと[ディープリンクを通じて]({{site.baseurl}}/partners/channel_extensions/deep_linking/branch_for_deeplinking/)、ユーザーのジャーニーをパーソナライズする方法を理解するのに役立つ。
+Branch と Braze の統合では、堅牢なアトリビューションと[ディープリンク]({{site.baseurl}}/partners/channel_extensions/deep_linking/branch_for_deeplinking/)により、ユーザーがいつ、どこで獲得されたかを正確に把握し、ユーザーのジャーニーをパーソナライズできるようになります。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| 支店口座 | このパートナーシップを利用するには、支店口座が必要である。 |
-| iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。これらの要件の詳細は、統合プロセスのステップ1に記載されている。 |
-| ブランチSDK | 必要なBraze SDKに加えて、[Branch SDKを](https://help.branch.io/developers-hub/docs/native-sdks-overview)インストールする必要がある。 |
+| Branch アカウント | このパートナーシップを活用するには、Branch アカウントが必要です。 |
+| iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。これらの要件の詳細については、統合プロセスのステップ1を参照してください。 |
+| ブランチSDK | 必要な Braze SDK に加えて、[Branch SDK](https://help.branch.io/developers-hub/docs/native-sdks-overview) をインストールする必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
@@ -31,15 +31,15 @@ BrazeとBranchの統合は、ユーザーがいつ、どこで獲得されたか
 
 #### Android 
 
-Androidアプリの場合、Branchに固有のBrazeデバイスIDを渡す必要がある。このIDは、Branch SDKの`setRequestMetadataKey()` 。`initSession` を呼び出す前に、以下のコード・スニペットをインクルードする必要がある。また、Branch SDKでリクエストメタデータを設定する前に、Braze SDKを初期化する必要がある。
+Android アプリを使用している場合は、Braze のデバイス ID を Branch に渡す必要があります。この ID は、Branch SDK の `setRequestMetadataKey()` メソッドで設定できます。`initSession`を呼び出す前に、次のコードスニペットを含める必要があります。また、Branch SDK でリクエストメタデータを設定する前に、Braze SDK を初期化する必要があります。
 
 {% tabs ローカル %}
-{% tab ジャワ %}
+{% tab Java %}
 ```java
 Branch.getInstance().setRequestMetadata("$braze_install_id", Braze.getInstance(context).deviceId); 
 ```
 {% endtab %}
-{% tab コトリン %}
+{% tab Kotlin %}
 ```kotlin
 Branch.getInstance().setRequestMetadata("$braze_install_id", Braze.getInstance(context).deviceId)
 ```
@@ -49,12 +49,12 @@ Branch.getInstance().setRequestMetadata("$braze_install_id", Braze.getInstance(c
 #### iOS
 
 {% alert important %}
-2023年2月以前は、Branchのアトリビューション統合は、iOSのアトリビューションデータを照合するための主要な識別子としてIDFVを使用していた。Objective-Cを使用しているBrazeの顧客が、インストール時にBraze`device_id` を取得し、Branchに送信する必要はない。
+2023年2月までは、Branch アトリビューション統合は、iOS アトリビューションデータを照合するための主な識別子として IDFV を使用していました。Objective-C を使用している Braze のお客様は、サービスが中断されることはないため、インストール時に Braze`device_id` を取得して Branch に送信する必要はありません。
 {% endalert%}
 
-Swift SDK v5.7.0+を使用している場合、相互識別子としてIDFVを引き続き使用したい場合は、`useUUIDAsDeviceId` フィールドが`false` に設定されていることを確認する必要があるため、統合が中断されることはない。 
+Swift SDK v5.7.0+ を使用しているお客様は、相互識別子として IDFV を引き続き使用するには、`useUUIDAsDeviceId` フィールドが `false` に設定されていることを確認する必要があります。これにより、統合が中断されることがなくなります。 
 
-`true` に設定した場合、BrazeがiOSアトリビュートに適切に一致するように、アプリインストール時にBranchにBraze`device_id` を渡すために、Swift用のiOSデバイスIDマッピングを実装する必要がある。
+`true` に設定している場合、Brazeが iOS アトリビューションを適切に照合できるように、アプリのインストール時に Branch に Braze`device_id` を渡すために、Swift用の iOS デバイス ID マッピングを実装する必要があります。
 
 {% tabs ローカル %}
 {% tab Objective-C %}
@@ -65,7 +65,7 @@ Swift SDK v5.7.0+を使用している場合、相互識別子としてIDFVを
 }];
 ```
 {% endtab %}
-{% tab スウィフト %}
+{% tab Swift %}
 
 ```swift
 braze.deviceId { deviceId in
@@ -79,40 +79,40 @@ braze.deviceId { deviceId in
 
 ### ステップ2:Brazeデータインポートキーを取得する
 
-Brazeで、**Partner Integrations**>**Technology Partnersに**移動し、**Branchを**選択する。 
+Brazeで、\[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Branch**] を選択します。 
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。鍵の生成後、新しい鍵を作成したり、既存の鍵を無効にしたりすることができる。データインポートキーとRESTエンドポイントは、Branchのダッシュボードでポストバックを設定するときに、次のステップで使用される。<br><br>![この画像は、ブランチ・テクノロジー・ページにある "Data Import for Install Attribution "ボックスを示している。このボックスには、データ・インポート・キーとRESTエンドポイントが表示される。][4]{: style="max-width:90%;"}
+ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。Branch のダッシュボードでポストバックを設定する場合、次のステップでデータインポートキーと REST エンドポイントが使用されます。<br><br>![Branch テクノロジーページにある「インストールアトリビューションのデータインポート」ボックス。このボックスには、データインポートキーと REST エンドポイントが表示されている。][4]{: style="max-width:90%;"}
 
 ### ステップ3:データフィードを設定する
 
-1. ブランチの**エクスポートセクションで**、**データフィードを**クリックする。
-2. **Data Feeds Manager**ページで、ページ上部の**Data Integrations**タブをクリックする。 
-3. 利用可能なデータパートナーのリストからBrazeを選択する。 
-4. Brazeのエクスポートページで、Brazeのダッシュボードで見つけたデータインポートキーとRESTエンドポイントを入力し、**Enableを**クリックする。
+1. Branch の \[**Exports**] セクションで \[**Data Feeds**] をクリックします。
+2. \[**Data Feeds Manager**] ページ上部にある \[**Data Integrations**] タブをクリックします。 
+3. 利用可能なデータパートナーのリストから Braze を選択します。 
+4. Braze のエクスポートページで、Braze のダッシュボードで確認したデータインポートキーと REST エンドポイントを入力し、\[**Enable**] をクリックします。
 
 ### ステップ4:統合を確認する
 
-BrazeがBranchからアトリビューションデータを受信すると、BrazeのBranchテクノロジーパートナーページのステータス接続インジケータが "Not Connected "から "Connected "に変わる。最後に成功したリクエストのタイムスタンプも含まれる。 
+Braze が Branch からアトリビューションデータを受信すると、Braze の Branch テクノロジーパートナーページのステータス接続インジケーターが \[接続されていません] から \[接続済み] に変わります。最後に成功したリクエストのタイムスタンプも含まれる。 
 
-これは、帰属するインストールに関するデータを受け取るまでは起こらないことに注意してほしい。Branchのポストバックから除外されるべきオーガニックインストールは、APIによって無視され、成功した接続が確立されたかどうかを判断する際にカウントされない。
+これは、紐づけられるインストールに関するデータを受け取るまでは発生しないことに注意してください。Branch のポストバックから除外する必要があるオーガニックインストールは、Braze の API では無視され、接続の確立が成功したかどうかを判断する際に考慮されません。
 
 ## FacebookとX（旧Twitter）のアトリビューションデータ
 
 FacebookおよびX（旧Twitter）キャンペーンのアトリビューションデータは、パートナーを通じて入手することはできない。これらのメディアソースは、そのパートナーが帰属データを第三者と共有することを許可していないため、当社のパートナーがそのデータをBrazeに送信することはできない。
 
-## BrazeのクリックトラッキングURLのブランチ（オプション）
+## Braze での Branch クリックトラッキング URL (オプション)
 
-Brazeのキャンペーンでクリック追跡リンクを使用すると、どのキャンペーンがアプリのインストールやリエンゲージメントを促進しているかを簡単に確認できる。その結果、マーケティング活動をより効果的に測定できるようになり、ROIを最大化するためにどこにリソースを投資すべきか、データに基づいた意思決定ができるようになる。
+Brazeのキャンペーンでクリック追跡リンクを使用すると、どのキャンペーンがアプリのインストールやリエンゲージメントを促進しているかを簡単に確認できる。その結果、マーケティング活動をより効果的に測定できるようになり、ROI を最大化するためにどこにリソースを投資すべきかについて、データに基づいた意思決定ができるようになります。
 
-Branchのクリック・トラッキング・リンクを使い始めるには、その[ドキュメントを](https://help.branch.io/using-branch/docs/ad-links)参照のこと。BrazeのキャンペーンにBranchのクリックトラッキングリンクを直接挿入することができる。ブランチは、リンクをクリックしたユーザーを[帰属](https://help.branch.io/using-branch/docs/branch-attribution-logic-settings)さ[せる](https://help.branch.io/using-branch/docs/branch-attribution-logic-settings)ために[、確率的帰属手法を](https://help.branch.io/using-branch/docs/branch-attribution-logic-settings)使用する。Brazeキャンペーンからの帰属の精度を高めるために、Branchトラッキングリンクにデバイス識別子を付加することをお勧めする。これにより、リンクをクリックしたユーザーの属性が決定的になる。
+Branch のクリックトラッキングリンクを使用するには、Branchの[ドキュメント](https://help.branch.io/using-branch/docs/ad-links)を参照してください。Braze のキャンペーンに Branch のクリックトラッキングリンクを直接挿入できます。その後 Branch は、リンクをクリックしたユーザーを紐づけるため、Branch の[確率的アトリビューション手法](https://help.branch.io/using-branch/docs/branch-attribution-logic-settings)を使用します。Braze キャンペーンのアトリビューションの精度向上のために、Branch トラッキングリンクにデバイス識別子を付加することをお勧めします。これにより、リンクをクリックしたユーザーの属性が決定的になる。
 
 {% tabs ローカル %}
-{% tab アンドロイド %}
-Androidの場合、Brazeは[Google Advertising ID収集（GAID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)）にオプトインすることができる。GAIDはまた、Branch SDKの統合によってネイティブに収集される。以下のリキッドロジックを利用することで、ブランチのクリックトラッキングリンクにGAIDを含めることができる：
+{% tab Android %}
+Android の場合、Braze ではお客様が [Google 広告 ID (GAID) 収集]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)にオプトインできます。GAID はまた、Branch SDK 統合によってネイティブに収集されます。以下の Liquid ロジックを利用して、Branch のクリックトラッキングリンクに GAID を組み込むことができます。
 {% raw %}
 ```
 {% if most_recently_used_device.${platform} == 'android' %}
@@ -123,7 +123,7 @@ user_data_aaid={{most_recently_used_device.${google_ad_id}}}
 {% endtab %}
 
 {% tab iOS %}
-iOSの場合、BrazeとBranchの両方が、SDKの統合を通じてネイティブにIDFVを自動的に収集する。これはデバイス識別子として使用できる。以下のリキッドロジックを利用することで、ブランチのクリックトラッキングリンクにIDFVを含めることができる：
+iOSの場合、BrazeとBranchの両方が、SDKの統合を通じてネイティブにIDFVを自動的に収集する。これはデバイス識別子として使用できる。以下の Liquid ロジックを利用して、Branch のクリックトラッキングリンクに IDFV を組み込むことができます。
 
 {% raw %}
 ```
@@ -136,9 +136,9 @@ user_data_idfv={{most_recently_used_device.${id}}}
 {% endtabs %}
 
 {% alert note %}
-**この推奨は純粋にオプションである。**<br>
+**この推奨事項の適用は完全に任意です。**<br>
 現在、クリック追跡リンクにIDFVやGAIDなどのデバイス識別子を使用していない場合、または今後使用する予定がない場合でも、ブランチは確率的モデリングによってこれらのクリックを識別することができる。
 {% endalert %}
 
-[22]: https://docs.branch.io/pages/exports/ua-webhooks/ "ブランチ・ウェブフック"
+[22]: https://docs.branch.io/pages/exports/ua-webhooks/ "Branch Webhook"
 [4]: {% image_buster /assets/img/attribution/branch.png %}
diff --git a/_lang/ja/_partners/message_orchestration/attribution/branch/branch_for_deeplinking.md b/_lang/ja/_partners/message_orchestration/attribution/branch/branch_for_deeplinking.md
index 9a5ffffdff6..dc13cbef148 100644
--- a/_lang/ja/_partners/message_orchestration/attribution/branch/branch_for_deeplinking.md
+++ b/_lang/ja/_partners/message_orchestration/attribution/branch/branch_for_deeplinking.md
@@ -1,40 +1,40 @@
 ---
-nav_title: ディープリンクのためのブランチ
-article_title: ディープリンクのためのブランチ
+nav_title: Branch (ディープリンク)
+article_title: Branch (ディープリンク)
 alias: /partners/branch_for_deeplinking/
 page_type: partner
-description: "この参考記事では、BrazeとBranchのパートナーシップと、ディープリンクの実践をサポートするための利用方法について説明している。"
+description: "このリファレンス記事では、Braze と Branch のパートナーシップと、これを利用してディープリンクをサポートする方法について説明します。"
 search_tag: Partner
 
 ---
 
-# ディープリンク用ブランチ {#branch}
+# Branch (ディープリンク) {#branch}
 
 {% multi_lang_include video.html id="PwGKqfwV-Ss" align="right" %}
 
-> モバイルリンクプラットフォームである[Branchは][1]、すべてのユーザータッチポイントを総合的に把握することで、あらゆるデバイス、チャネル、プラットフォームでの獲得、エンゲージメント、測定を支援する。
+> [Branch][1] はあらゆるデバイス、チャネル、プラットフォームでの獲得、エンゲージメント、測定を支援するモバイルリンクプラットフォームで、すべてのユーザータッチポイントの一元的なビューを提供しています。
 
-BrazeとBranchの統合により、ユーザージャーニーの開始を適切に[属性化]({{site.baseurl}}/partners/advertising_technologies/attribution/branch_for_attribution/)し、ディープリンクを通じて目的の場所へとつなげることができるため、顧客により良い体験を提供することができる。
+Braze とBranch の統合により、ユーザージャーニー開始を適切に[紐づける]({{site.baseurl}}/partners/advertising_technologies/attribution/branch_for_attribution/)ことができるようにして、より優れたエクスペリエンスを顧客に提供し、ディープリンクを使用して目的のロケーションに顧客を接続できます。
 
-通話リンク(`href=tel:`)を含む場合、
+コールリンク (`href=tel:`) を含む場合、
 
 ## 統合
 
-[BranchのSDK統合ガイドに従って](https://help.branch.io/developers-hub/docs/native-sdks-overview)、Branch統合を立ち上げ、実行する。その他の使用例については以下を参照のこと。
+[Branch の SDK 統合ガイド](https://help.branch.io/developers-hub/docs/native-sdks-overview)に従って、Branch と Braze の統合を稼働させます。その他の使用例については以下を参照のこと。
 
 ### iOSユニバーサルリンクをサポートする
 
 BrazeからiOSユニバーサルリンクをディープリンクとして送信できるようにする：
 
-1. [ユニバーサルリンクの][3]設定については、Branchのドキュメントに従うこと。
-2. アプリ内からユニバーサルリンクをルーティングするために [`BrazeDelegate`][4]メソッド[braze(_:shouldOpenURL:)を][5]実装し、アプリ内から[ユニバーサルリンクをルーティング][6]する。
+1. [ユニバーサルリンク][3]の設定については、Branch のドキュメントの説明に従ってください。
+2. アプリ内から[ユニバーサルリンクをルーティング][6]するには、Braze SDK 統合に [`BrazeDelegate`][4] メソッド [braze(_:shouldOpenURL:)][5] を実装します。
 
 ### 電子メールでのディープリンク
 
-[ユニバーサルリンクとアプリリンクに関する]({{site.baseurl}}/help/help_articles/email/universal_links/)ドキュメントを参照する。
-または、[Brazeを通して](https://docs.branch.io/pages/integrations/braze/)送信されたメールからのディープリンクを設定するための[Branchのドキュメントを](https://docs.branch.io/pages/integrations/braze/)参照のこと。
+[ユニバーサルリンクとアプリリンク]({{site.baseurl}}/help/help_articles/email/universal_links/)に関するドキュメントを参照するか、
+[Branch のドキュメント](https://docs.branch.io/pages/integrations/braze/)を参照して、Braze 経由で送信されるメールからのディープリンクを設定します。
 
-iOS用Gmailアプリでは、ユーザーがアプリに通話許可を与えない限り、電話番号へのリンク（`href` に`tel` を付加）はサポートされていない。
+ユーザーがアプリにコール権限を付与しない限り、iOS 用の Gmail アプリでは電話番号へのリンク (`tel` を`href` に付加) はサポートされません。
 
 ESPによっては、クリックトラッキングされたユニバーサルリンクをサポートするために追加のカスタマイズが必要になる場合がある。この情報については、専用の記事で紹介している。詳しくは以下の文献を参照されたい：
 
diff --git a/_lang/ja/_partners/message_orchestration/attribution/kochava.md b/_lang/ja/_partners/message_orchestration/attribution/kochava.md
index bbeb672e058..f08bea05e3a 100644
--- a/_lang/ja/_partners/message_orchestration/attribution/kochava.md
+++ b/_lang/ja/_partners/message_orchestration/attribution/kochava.md
@@ -2,7 +2,7 @@
 nav_title: Kochava
 article_title: Kochava
 alias: /partners/kochava/
-description: "このリファレンス記事では、Braze と Kochava の提携について説明しています。Kochava はモバイルアトリビューションプラットフォームで、アトリビューションと分析のインサイトを提供し、データを活用して成長を促進します。"
+description: "このリファレンス記事では、Braze と Kochava のパートナーシップについて説明します。Kochava は、アトリビューションおよび分析インサイトを提供して、成長のためのデータの活用を支援するモバイルアトリビューションプラットフォームです。"
 page_type: partner
 search_tag: Partner
 
@@ -10,7 +10,7 @@ search_tag: Partner
 
 # Kochava
 
-> Kochavaは、成長のためにデータを活用するためのモバイルアトリビューションと分析を提供します。Kochavaオーディエンスプラットフォームは、アプリキャンペーンの計画、ターゲティング、アクティベーション、測定、および最適化を可能にします。
+> Kochava は、モバイルアトリビューションと分析を提供し、データを活用した成長を支援しています。Kochava Audience Platform では、アプリキャンペーンの計画、ターゲット、アクティベーション、測定、最適化を実施できます。
 
 BrazeとKochavaの統合により、アトリビューションデータをBrazeに送信することで、インストール、アプリ内アクティビティなどを促進するキャンペーンをよりよく理解し、キャンペーンの全体的な理解を深めることができます。
 
@@ -18,8 +18,8 @@ BrazeとKochavaの統合により、アトリビューションデータをBraze
 
 | 要件 | 説明 |
 |---|---|
-| Kochavaアカウント | このパートナーシップを利用するには、Kochavaアカウントが必要です。 |
-| iOSまたはAndroidアプリ | この統合はiOSおよびAndroidアプリをサポートしています。プラットフォームによっては、アプリケーションにコードスニペットが必要な場合があります。これらの要件の詳細は、統合プロセスのステップ1にあります。 |
+| Kochavaアカウント | このパートナーシップを活用するには、Kochava アカウントが必要です。 |
+| iOSまたはAndroidアプリ | この統合はiOSおよびAndroidアプリをサポートしています。プラットフォームによっては、アプリケーションにコードスニペットが必要な場合があります。これらの要件の詳細については、統合プロセスのステップ1を参照してください。 |
 | Kochava SDK | 必須のBraze SDKに加えて、[Kochava SDK](https://support.kochava.com/sdk-integration/)をインストールする必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -29,7 +29,7 @@ BrazeとKochavaの統合により、アトリビューションデータをBraze
 
 #### Android
 
-[Android](https://support.kochava.com/sdk-integration/sdk-kochavatracker-android/class-tracker?scrollto=marker_3) SDKは、セッション開始時にBraze IDとしてGUIDを生成します。これは、Brazeがデータを正しいユーザープロファイルに照合できるようにするために、Kochava `IdentityLink` メソッドに渡すことをお勧めする識別子です。Braze IDは次の方法で取得できます:
+[Android](https://support.kochava.com/sdk-integration/sdk-kochavatracker-android/class-tracker?scrollto=marker_3) SDKは、セッション開始時にBraze IDとしてGUIDを生成します。この識別子を Kochava `IdentityLink` メソッドに渡すことが推奨されます。これにより、Braze はデータを正しいユーザープロファイルと照合することができます。Braze IDは次の方法で取得できます:
 
 ```java
 Apppboy.getInstance(context).getDeviceId();
@@ -38,12 +38,12 @@ Apppboy.getInstance(context).getDeviceId();
 #### iOS
 
 {% alert important %}
-2023年2月以前、当社のKochavaアトリビューション統合は、iOSアトリビューションデータを照合するための主要な識別子としてIDFVを使用していました。Brazeの顧客がサービスの中断がないため、インストール時にBraze`device_id`を取得してKochavaに送信する必要はありません。
+2023年2月までは、Kochava アトリビューション統合は、iOS アトリビューションデータを照合するための主な識別子として IDFV を使用していました。Objective-C を使用している Braze のお客様は、サービスが中断されることはないため、インストール時に Braze `device_id` を取得して Kochava に送信する必要はありません。
 {% endalert%}
 
-Swift SDK v5.7.0+を使用している方は、相互識別子としてIDFVを使用し続けたい場合、`useUUIDAsDeviceId`フィールドが`false`に設定されていることを確認して、統合が中断されないようにする必要があります。`true`に設定されている場合、アプリインストール時にBraze `device_id`をKochavaに渡すために、SwiftのiOSデバイスIDマッピングを実装する必要があります。これにより、BrazeはiOSのアトリビューションを適切に一致させることができます。
+Swift SDK v5.7.0+ を使用しているお客様は、相互識別子として IDFV を引き続き使用するには、`useUUIDAsDeviceId` フィールドが `false` に設定されていることを確認する必要があります。これにより、統合が中断されることがなくなります。`true` に設定している場合、Brazeが iOS アトリビューションを適切に照合できるように、アプリのインストール時にKochava に Braze `device_id` を渡すために、Swift用の iOS デバイス ID マッピングを実装する必要があります。
 
-Brazeには2つのAPIがあり、1つは完了ハンドラを使用し、もう1つは新しいSWIFTの並行処理サポートを使用して同じ値を生成します。次のコードスニペットをKochavaの[iOS SDK](https://support.kochava.com/sdk-integration/ios-sdk-integration/)の指示に従って修正する必要があることに注意してください。追加のヘルプが必要な場合は、Kochavaサポートに連絡してください。
+Braze には、同じ値を生成する2つのAPI があります。1つは完了ハンドラを使用し、もう1つは新しいSwift 同時実行サポートを使用します。次のコードスニペットをKochavaの[iOS SDK](https://support.kochava.com/sdk-integration/ios-sdk-integration/)の指示に従って修正する必要があることに注意してください。追加のヘルプが必要な場合は、Kochavaサポートに連絡してください。
 
 ##### 完了ハンドラ
 ```
@@ -61,20 +61,20 @@ let deviceId = await AppDelegate.braze?.deviceId()
 Brazeで、**Partner Integrations** > **Technology Partners** に移動し、**Kochava** を選択します。 
 
 {% alert note %}
-古いナビゲーションを使用している場合は、統合の下にテクノロジーパートナーを見つけることができます。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
 ここでは、RESTエンドポイントを見つけて、Brazeデータインポートキーを生成します。キーが生成された後、新しいキーを作成するか、既存のキーを無効にすることができます。データインポートキーとRESTエンドポイントは、Kochavaのダッシュボードでポストバックを設定する次のステップで使用されます。<br><br>![この画像は、Kochavaテクノロジーページにある「インストールアトリビューションのためのデータインポート」ボックスを示しています。このボックスには、データインポートキーとRESTエンドポイントが表示されます。][4]{: style="max-width:90%;"}
 
 ### ステップ3:Kochavaからのポストバックを設定する
 
-[ポストバックを追加する][18] Kochava ダッシュボードで。Brazeのダッシュボードで見つけたデータインポートキーとRESTエンドポイントを求められます。
+Kochava ダッシュボードに[ポストバックを追加します][18]。Brazeのダッシュボードで見つけたデータインポートキーとRESTエンドポイントを求められます。
 
 ### ステップ4:統合を確認する
 
-BrazeがKochavaからアトリビューションデータを受信すると、BrazeのKochavaテクノロジーパートナーページのステータス接続インジケーターが「未接続」から「接続済み」に変わります。最後の成功したリクエストのタイムスタンプも含まれます。 
+Braze が Kochava からアトリビューションデータを受信すると、Braze の Kochava テクノロジーパートナーページのステータス接続インジケーターが \[接続されていません] から \[接続済み] に変わります。最後の成功したリクエストのタイムスタンプも含まれます。 
 
-このことは、帰属されたインストールに関するデータを受け取るまで発生しないことに注意してください。オーガニックインストールはKochavaポストバックから除外する必要があり、当社のAPIによって無視され、接続が成功したかどうかを判断する際にはカウントされません。
+これは、紐づけられるインストールに関するデータを受け取るまでは発生しないことに注意してください。オーガニックインストールはKochavaポストバックから除外する必要があり、当社のAPIによって無視され、接続が成功したかどうかを判断する際にはカウントされません。
 
 ## FacebookとX（旧Twitter）のアトリビューションデータ
 
@@ -82,13 +82,13 @@ FacebookおよびX（旧Twitter）キャンペーンのアトリビューショ
 
 ## BrazeでのKochavaクリックトラッキングURL（オプション）
 
-Brazeキャンペーンでクリックトラッキングリンクを使用すると、どのキャンペーンがアプリのインストールと再エンゲージメントを促進しているかを簡単に確認できます。その結果、マーケティング活動をより効果的に測定し、最大のROIを得るためにどこにリソースを投資するかについてデータドリブン型の意思決定を行うことができるようになります。
+Brazeキャンペーンでクリックトラッキングリンクを使用すると、どのキャンペーンがアプリのインストールと再エンゲージメントを促進しているかを簡単に確認できます。その結果、マーケティング活動をより効果的に測定できるようになり、ROI を最大化するためにどこにリソースを投資すべきかについて、データに基づいた意思決定ができるようになります。
 
 Kochavaのクリックトラッキングリンクを開始するには、[ドキュメント](https://support.kochava.com/reference-information/attribution-overview/)をご覧ください。BrazeキャンペーンにKochavaクリックトラッキングリンクを直接挿入できます。Kochavaはその後、[確率的アトリビューション方法論](https://www.kochava.com/getting-prepared-for-ios-14/)を使用して、リンクをクリックしたユーザーを属性します。Brazeキャンペーンからのアトリビューションの精度を向上させるために、Kochavaトラッキングリンクにデバイス識別子を追加することをお勧めします。これにより、リンクをクリックしたユーザーを決定論的に属性付けします。
 
 {% tabs ローカル %}
 {% tab Android %}
-Androidの場合、Brazeを使用すると、顧客は[Google広告IDコレクション（GAID）]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)にオプトインできます。GAIDは、Kochava SDK統合を通じてネイティブに収集されます。次のLiquidロジックを利用して、KochavaクリックトラッキングリンクにGAIDを含めることができます:
+Androidの場合、Brazeを使用すると、顧客は[Google広告IDコレクション（GAID）]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)にオプトインできます。GAID はまた、Kochava SDK統合によってネイティブに収集されます。次のLiquidロジックを利用して、KochavaクリックトラッキングリンクにGAIDを含めることができます:
 {% raw %}
 ```
 {% if most_recently_used_device.${platform} == 'android' %}
@@ -117,7 +117,7 @@ idfv={{most_recently_used_device.${id}}}
 {% endalert %}
 
 
-[18]: https://support.kochava.com/campaign-management/create-a-kochava-certified-postback "Kochavaポストバック"
+[18]: https://support.kochava.com/campaign-management/create-a-kochava-certified-postback "Kochava ポストバック"
 [29]: https://support.kochava.com/sdk-integration/sdk-kochavatracker-android/class-tracker?scrollto=marker_3
 [30]: https://support.kochava.com/sdk-integration/windows-and-xbox-one-sdk-integration?scrollto=marker_8
 [4]: {% image_buster /assets/img/attribution/kochava.png %}
diff --git a/_lang/ja/_partners/message_orchestration/attribution/singular.md b/_lang/ja/_partners/message_orchestration/attribution/singular.md
index 35fcec49a44..bda82a81c1f 100644
--- a/_lang/ja/_partners/message_orchestration/attribution/singular.md
+++ b/_lang/ja/_partners/message_orchestration/attribution/singular.md
@@ -2,7 +2,7 @@
 nav_title: 単数形
 article_title: 単数形
 alias: /partners/singular/
-description: "この参考記事では、BrazeとSingularのパートナーシップについて概説している。Singularは、統合マーケティング分析プラットフォームで、有料インストーラのアトリビューションデータをインポートすることができる。"
+description: "このリファレンス記事では、Braze と Singular のパートナーシップについて説明します。Singular は、有料インストールアトリビューションデータをインポートできる統合マーケティング分析プラットフォームです。"
 page_type: partner
 search_tag: Partner
 
@@ -18,9 +18,9 @@ BrazeとSingularの統合により、有料インストーラのアトリビュ
 
 | 必要条件 | 説明 |
 |---|---|
-| 単一アカウント | このパートナーシップを利用するには、Singularアカウントが必要である。 |
-| iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。これらの要件の詳細は、統合プロセスのステップ1に記載されている。 |
-| シンギュラーSDK | 必要なBraze SDKに加えて、[Singular SDKを](https://support.singular.net/hc/en-us/articles/360037640172-Getting-Started-with-the-Singular-SDK-S2S)インストールする必要がある。 |
+| Singular アカウント | このパートナーシップを活用するには、Singular アカウントが必要です。 |
+| iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。これらの要件の詳細については、統合プロセスのステップ1を参照してください。 |
+| シンギュラーSDK | 必要な Braze SDK に加えて、[Singular SDK](https://support.singular.net/hc/en-us/articles/360037640172-Getting-Started-with-the-Singular-SDK-S2S) をインストールする必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
@@ -39,12 +39,12 @@ SingularConfig config = new SingularConfig("SDK KEY", "SDK SECRET")
 #### iOS
 
 {% alert important %}
-2023年2月以前は、当社のSingularアトリビューション統合は、iOSアトリビューションデータを照合するための主要識別子としてIDFVを使用していた。Objective-Cを使用しているBrazeの顧客が、インストール時にBraze`device_id` を取得し、Singularに送信する必要はない。
+2023年2月までは、Singular アトリビューション統合は、iOS アトリビューションデータを照合するための主な識別子として IDFV を使用していました。Objective-C を使用している Braze のお客様は、サービスが中断されることはないため、インストール時に Braze `device_id` を取得して Singular に送信する必要はありません。
 {% endalert%}
 
-Swift SDK v5.7.0+を使用している場合、相互識別子としてIDFVを引き続き使用したい場合は、`useUUIDAsDeviceId` フィールドが`false` に設定されていることを確認する必要があるため、統合が中断されることはない。 
+Swift SDK v5.7.0+ を使用しているお客様は、相互識別子として IDFV を引き続き使用するには、`useUUIDAsDeviceId` フィールドが `false` に設定されていることを確認する必要があります。これにより、統合が中断されることがなくなります。 
 
-`true` に設定した場合、BrazeがiOSアトリビュートに適切に一致するように、アプリインストール時にSingularにBraze`device_id` を渡すために、Swift用にiOSデバイスIDマッピングを実装する必要がある。
+`true` に設定している場合、Brazeが iOS アトリビューションを適切に照合できるように、アプリのインストール時に Singular に Braze`device_id` を渡すために、Swift用の iOS デバイス ID マッピングを実装する必要があります。
 
 {% tabs ローカル %}
 {% tab Objective-C %}
@@ -70,21 +70,21 @@ config.setGlobalProperty("brazeDeviceId", withValue: brazeDeviceId, overrideExis
 
 ### ステップ2:Brazeデータインポートキーを取得する
 
-Brazeで、**Partner Integrations**>**Technology Partnersと**進み、**Singularを**選択する。 
+Brazeで、\[**パートナー連携**] > \[**テクノロジーパートナー**] に移動し、\[**Singular**] を選択します。 
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。鍵の生成後、新しい鍵を作成したり、既存の鍵を無効にしたりすることができる。 
+ここで、RESTエンドポイントを見つけ、Brazeデータインポートキーを生成する。キーが生成されたら、新しいキーを作成するか、既存のキーを無効にできます。 
 
-統合を完了するには、データインポートキーとRESTエンドポイントをSingularアカウントマネージャーに提供する必要がある。<br><br>![この画像は、Singularテクノロジーのページにある「Data Import for Install Attribution」ボックスを示している。このボックスには、データ・インポート・キーとRESTエンドポイントが表示される。][4]{: style="max-width:90%;"}
+統合を完了するには、データインポートキーとRESTエンドポイントをSingularアカウントマネージャーに提供する必要がある。<br><br>![Singular テクノロジーページにある「インストールアトリビューションのデータインポート」ボックス。このボックスには、データインポートキーと REST エンドポイントが表示されている。][4]{: style="max-width:90%;"}
 
 ### ステップ3:統合を確認する
 
-BrazeがSingularからアトリビューションデータを受信すると、BrazeのSingularテクノロジーパートナーページのステータス接続インジケーターが、"Not Connected "から "Connected "に変わる。最後に成功したリクエストのタイムスタンプも含まれる。 
+Braze が Singular からアトリビューションデータを受信すると、Braze の Singular テクノロジーパートナーページのステータス接続インジケーターが \[接続されていません] から \[接続済み] に変わります。最後に成功したリクエストのタイムスタンプも含まれる。 
 
-これは、帰属するインストールに関するデータを受け取るまでは起こらないことに注意してほしい。Singularのポストバックから除外されるべきオーガニック・インストールは、APIによって無視され、接続が成功したかどうかを判断する際にカウントされない。
+これは、紐づけられるインストールに関するデータを受け取るまでは発生しないことに注意してください。Singular のポストバックから除外する必要があるオーガニックインストールは、Braze の API では無視され、接続の確立が成功したかどうかを判断する際に考慮されません。
 
 ## FacebookとX（旧Twitter）のアトリビューションデータ
 
@@ -92,13 +92,13 @@ FacebookおよびX（旧Twitter）キャンペーンのアトリビューショ
 
 ## Brazeの単一クリックトラッキングURL（オプション）
 
-Brazeのキャンペーンでクリック追跡リンクを使用すると、どのキャンペーンがアプリのインストールやリエンゲージメントを促進しているかを簡単に確認できる。その結果、マーケティング活動をより効果的に測定できるようになり、ROIを最大化するためにどこにリソースを投資すべきか、データに基づいた意思決定ができるようになる。
+Brazeのキャンペーンでクリック追跡リンクを使用すると、どのキャンペーンがアプリのインストールやリエンゲージメントを促進しているかを簡単に確認できる。その結果、マーケティング活動をより効果的に測定できるようになり、ROI を最大化するためにどこにリソースを投資すべきかについて、データに基づいた意思決定ができるようになります。
 
 Singularクリック・トラッキング・リンクを使い始めるには、[ドキュメントを](https://support.singular.net/hc/en-us/articles/360030934212-Singular-Links-FAQ?navigation_side_bar=true)参照すること。SingularのクリックトラッキングリンクをBrazeのキャンペーンに直接挿入することができる。その後、Singularは[確率的アトリビューション手法を用いて](https://support.singular.net/hc/en-us/articles/115000526963-Understanding-Singular-Mobile-App-Attribution?navigation_side_bar=true)、リンクをクリックしたユーザーをアトリビュートする。Brazeキャンペーンからの帰属の精度を高めるために、Singularトラッキングリンクにデバイス識別子を付加することをお勧めする。これにより、リンクをクリックしたユーザーの属性が決定的になる。
 
 {% tabs ローカル %}
-{% tab アンドロイド %}
-Androidの場合、Brazeは[Google Advertising ID収集（GAID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)）にオプトインすることができる。GAIDはまた、Singular SDKの統合によってネイティブに収集される。以下のLiquidロジックを利用することで、SingularクリックトラッキングリンクにGAIDを含めることができる：
+{% tab Android %}
+Android の場合、Braze ではお客様が [Google 広告 ID (GAID) 収集]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/optional_gaid_collection/#optional-google-advertising-id)にオプトインできます。GAID はまた、Singular SDK統合によってネイティブに収集されます。以下のLiquidロジックを利用することで、SingularクリックトラッキングリンクにGAIDを含めることができる：
 {% raw %}
 ```
 {% if most_recently_used_device.${platform} == 'android' %}
@@ -122,7 +122,7 @@ idfv={{most_recently_used_device.${id}}}
 {% endtabs %}
 
 {% alert note %}
-**この推奨は純粋にオプションである。**<br>
+**この推奨事項の適用は完全に任意です。**<br>
 現在、クリックトラッキングのリンクにIDFVやGAIDのようなデバイス識別子を使用していない場合、または今後使用する予定がない場合でも、Singularは確率的モデリングによってこれらのクリックを識別することができる。
 {% endalert %}
 
diff --git a/_lang/ja/_partners/message_orchestration/attribution/vizbee_for_tv_deeplinking.md b/_lang/ja/_partners/message_orchestration/attribution/vizbee_for_tv_deeplinking.md
index fa4cef98234..69d3bf12cab 100644
--- a/_lang/ja/_partners/message_orchestration/attribution/vizbee_for_tv_deeplinking.md
+++ b/_lang/ja/_partners/message_orchestration/attribution/vizbee_for_tv_deeplinking.md
@@ -1,36 +1,36 @@
 ---
-nav_title: ヴィズビー
-article_title: TVディープリンクのためのVizbee
+nav_title: Vizbee
+article_title: Vizbee (TV ディープリンク)
 alias: /partners/vizbee_for_tv_deeplinking/
 page_type: partner
-description: "この参考記事では、BrazeとVizbeeのパートナーシップと、TVディープリンクをサポートするための使用方法について説明している。"
+description: "このリファレンス記事では、Braze と Vizbee のパートナーシップと、これを利用して TV ディープリンクをサポートする方法について説明します。"
 search_tag: Partner
 
 ---
 # Vizbee {#vizbee}
 
-> [Vizbeeは][1]、家庭内のすべてのスマートフォンとスマートテレビを1つのシームレスなデバイスとして連携させ、優れたユーザー体験を可能にする。Vizbeeは、通知、ディープリンク、Eメールなどの既存のモバイルアプリ・マーケティング・チャネルを活用し、すべてのコネクテッドTV（CTV）デバイス（Roku、FireTV、Samsung TV、LG TVなど）で視聴者をシームレスに獲得し、エンゲージすることができる。
+> [Vizbee][1] は、ご家庭のすべてのスマートフォンとスマートテレビを1つのシームレスなデバイスとして連携させ、優れたユーザーエクスペリエンスを実現します。Vizbeeは、通知、ディープリンク、Eメールなどの既存のモバイルアプリ・マーケティング・チャネルを活用し、すべてのコネクテッドTV（CTV）デバイス（Roku、FireTV、Samsung TV、LG TVなど）で視聴者をシームレスに獲得し、エンゲージすることができる。
 
-BrazeとVizbeeの統合により、単一のコンソールを使用して、モバイルとCTVデバイスの両方のストリーミングアプリで視聴者を獲得し、維持するためのマーケティングキャンペーンをスケジュールすることができる。この統合によって、あなたは次のことができる：
-- ターゲットユーザーにモバイル通知をスケジュールし、タップすると、モバイルアプリの視聴につながったり、近くのストリーミングデバイスやテレビでの再生をシームレスに呼び出したりできる。
+Braze と Vizbee の統合により、モバイルデバイスと CTV デバイスの両方でストリーミングアプリの視聴者を獲得、維持するためのマーケティングキャンペーンを、1つのコンソールでスケジュールできます。この統合により、次のことが可能になります。
+- ターゲットユーザーへのモバイル通知をスケジュールする。このモバイル通知では、タップ操作でモバイルアプリで視聴できたり、近くにあるストリーミングデバイスやテレビでの再生をシームレスに実行できたりします。
 - ターゲットユーザーへのEメールマーケティングキャンペーンをスケジュールし、タップすると、CTVアプリの自動インストールや、RokuやFireTVなどのCTVデバイスへのサインインが可能になる。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| Vizbeeアカウント | このパートナーシップを利用するには、[Vizbee][1]アカウントが必要である。Vizbeeにアプリを登録し、Vizbee IDを割り当てる必要がある。 |
+| Vizbeeアカウント | このパートナーシップを利用するには、[Vizbee][1]アカウントが必要である。Vizbee でアプリを登録し、Vizbee ID を割り当てる必要があります。 |
 | iOSまたはAndroidアプリ | この統合はiOSとAndroidアプリをサポートしている。プラットフォームによっては、アプリケーションにコード・スニペットが必要になるかもしれない。 |
-| Vizbee SDK | 必要なBraze SDKに加えて、Vizbee SDKをインストールする必要がある。 |
+| Vizbee SDK | 必要な Braze SDK に加えて、Vizbee SDK をインストールする必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-Vizbeeの[SDK統合ガイドに従って][2]、VizbeeとBrazeの統合を立ち上げ、実行する。ここでは、モバイルからテレビへのディープリンク、テレビアプリのインストール、視聴率アトリビューションに関するガイダンスを見ることができる。 
+Vizbee の [SDK 統合ガイド][2]に従って、Vizbee と Braze の統合を稼働させます。ここでは、モバイルからテレビへのディープリンク、テレビアプリのインストール、視聴率アトリビューションに関するガイダンスを見ることができる。 
 
-### インストール・レポートとアトリビューション・レポートを見る {#vizbee-tv-app-installs-viewership-attribution}
+### インストールおよびアトリビューションレポートの表示 {#vizbee-tv-app-installs-viewership-attribution}
 
-また、VizbeeとBrazeは、モバイルとCTVデバイスにまたがるキャンペーンの総合的なパフォーマンスを表示することもできる。Vizbee SDKはBraze SDKにカスタムイベントを送信し、Brazeダッシュボードからキャンペーンレポートで確認できる。
+また、VizbeeとBrazeは、モバイルとCTVデバイスにまたがるキャンペーンの総合的なパフォーマンスを表示することもできる。Vizbee SDK はカスタムイベントを Braze SDK に送信します。カスタムイベントは、Braze ダッシュボードからキャンペーンレポートで確認できます。
 
 [1]: https://vizbee.tv/
 [2]: https://console.vizbee.tv/app/vzb1765003429/develop/guides/ios-continuity
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions.md b/_lang/ja/_partners/message_orchestration/channel_extensions.md
index 8aa82b614d6..dcd3c5b82b4 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions.md
@@ -14,55 +14,55 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Channel Extensions"
 
 valid_partner_list:
-- name: アルパコ
+- name: Alpaco
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/alpaco/
-- name: アンタボ
+- name: Antavo
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/antavo/
 - name: Dyspatch.io
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/dyspatch/
-- name: ステンソール
+- name: Stensul
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/stensul/
 - name: Stripo
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/stripo/
-- name: Eメール用タクシー
+- name: Taxi for Email
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/taxi_for_email/
 - name: Talon.One
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/talonone/
-- name: バウチャリファイ
+- name: Voucherify
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/voucherify/
 - name: Jebbit
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/jebbit/
 - name: 繰り返す
   url: /docs/partners/message_orchestration/channel_extensions/surveys/iterate/
-- name: デジオー
+- name: Digioh
   url: /docs/partners/message_orchestration/channel_extensions/surveys/digioh/
 - name: Punchh
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/punchh/
-- name: ショップファイ
+- name: Shopify
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/shopify/
-- name: ヨットポ
+- name: Yotpo
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/yotpo/
-- name: ナック
+- name: Knak
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/knak/
-- name: エクストール
+- name: Extole
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/extole/
 - name: ViralSweep
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/viralsweep/
-- name: サバイケート
+- name: Survicate
   url: /docs/partners/message_orchestration/channel_extensions/surveys/survicate/
-- name: IAMスタジオ（NNT）
+- name: IAM Studio (NNT)
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/iam_studio/
 - name: Ada
   url: /docs/partners/message_orchestration/channel_extensions/surveys/ada/
-- name: B.レイヤー 
+- name: B.Layer 
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/blayer/
-- name: サゲフロ
+- name: Sageflo
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/sageflo/
-- name: ギフト
+- name: Nift
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/nift/
-- name: コグニティブ
+- name: Kognitiv
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/kognitiv/
-- name: タイプフォーム
+- name: Typeform
   url: /docs/partners/message_orchestration/channel_extensions/surveys/typeform/
 - name: Friendbuy
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/friendbuy/
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce.md
index edb8567677d..0eddf8aa513 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce.md
@@ -4,7 +4,7 @@ article_title: eコマースパートナー
 page_order: 9
 
 page_type: landing
-description: "このランディングページには、Eコマースプラットフォームと統合できるBrazeパートナ(Alloys) が一覧表示されます。"
+description: "このランディングページには、e コマースプラットプラットフォームを統合できる Braze パートナー (Alloys) が一覧表示されています。"
 
 layout: partner_page
 search_tag: Partner
@@ -16,8 +16,8 @@ partner_top_header: "Ecommerce"
 valid_partner_list:
 - name: Shopify
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/shopify/
-- name: オロ
+- name: Olo
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/olo/
-- name: ヨットポ
+- name: Yotpo
   url: /docs/partners/message_orchestration/channel_extensions/ecommerce/yotpo/
 ---
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/olo.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/olo.md
index 9a3427616ca..55caff4e4be 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/olo.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/olo.md
@@ -1,15 +1,15 @@
 ---
-nav_title: オロ
-article_title: オロ
+nav_title: Olo
+article_title: Olo
 description: "この記事では、Brazeと、あらゆるタッチポイントでホスピタリティを実現するレストラン向けオープンSaaSプラットフォームのリーディングカンパニーであるOlo社との提携について概説する。"
 alias: /partners/olo/
 page_type: partner
 search_tag: Partner
 ---
 
-# オロ
+# Olo
 
-> [Oloは][1]、あらゆるタッチポイントでホスピタリティを実現する、レストラン向けの主要なオープンSaaSプラットフォームである。
+> [Olo][1] は、あらゆるタッチポイントでの応対を可能にする飲食店向けの大手オープン SaaS プラットフォームです。
 
 OloとBrazeを統合することで、それが可能になる：
 
@@ -20,51 +20,51 @@ OloとBrazeを統合することで、それが可能になる：
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| オロ口座 | このパートナーシップを利用するには、ウェブフックにアクセスできるOloアカウントが必要である。Oloダッシュボード内の[セルフサービスWebhooksツールで](https://olosupport.zendesk.com/hc/en-us/articles/360061153692-Self-Service-Webhooks)Webhookサブスクリプションを設定する。 |
-| ブレイズデータ変換 | Oloからデータを受け取るには、[データ変換URLが]({{site.baseurl}}/data_transformation/)必要である。 |
+| Olo アカウント | このパートナーシップを利用するには、ウェブフックにアクセスできるOloアカウントが必要である。Oloダッシュボード内の[セルフサービスWebhooksツールで](https://olosupport.zendesk.com/hc/en-us/articles/360061153692-Self-Service-Webhooks)Webhookサブスクリプションを設定する。 |
+| Braze Data Transformation | Olo からデータを受信するには、[Data Transformation URL]({{site.baseurl}}/data_transformation/) が必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 Webhookとは、OloがBrazeにユーザーとそのアクションに関するイベントドリブンな情報を送信する方法であり、Order Placed（注文の発注）、Guest Opt In（ゲストのオプトイン）、Order Picked Up（注文の受け取り）などのイベントを含む。Olo Webhookは、一般的にアクションが実行されてから数秒以内にBrazeにイベントを配信する。
 
 ## 免責事項
 
-Oloでは、承認されたブランドごとに1環境につき1つのウェブフックに制限され、すべて同じ**宛先**URLに送信される。異なるブランドは異なるURLを持つことができるが、同じブランドのイベントはURLを共有しなければならない。Brazeでは、これはOloで使用するための変身を1つしか作れないことを意味する。
+Oloでは、承認されたブランドごとに1環境につき1つのウェブフックに制限され、すべて同じ**宛先**URLに送信される。異なるブランドは異なるURLを持つことができるが、同じブランドのイベントはURLを共有しなければならない。これは Braze では、Olo で使用するために作成できる変換が1つだけであることを意味します。
 
 この1つの変換で複数のOloイベントを処理するには、各ウェブフックの`X-Olo-Event-Type` ヘッダーを探す。このヘッダーによって、異なるOloイベントを条件付きで処理することができる。
 
 ## 統合
 
-### ステップ1:Oloのテストイベントを受け入れるようにBrazeデータ変換をセットアップする。 {#step-1}
+### ステップ1:Olo のテストイベントを受け入れるように Braze Data Transformation を設定する {#step-1}
 
 {% multi_lang_include create_transformation.md location="default" %}
 
 ### ステップ2:Oloウェブフックを設定する
 
-Oloダッシュボード内の[セルフサービスウェブフックツールを][2]使用して、データ変換に送信するウェブフックを設定する。
+Olo ダッシュボード内の[セルフサービス Webhooks ツール][2]を使用して、Data Transformation に送信する Webhook を設定します。
 
 1. Brazeに送信するイベントを選択する
-2. **宛先URLを**設定する。これは[ステップ](#step-1)1で作成したデータ変換URLになる。
+2. **宛先 URL** を設定します。これは、[ステップ1](#step-1)で作成された Data Transformation URL です。
 
 {% alert note %}
-`OAuth` と`X-Olo-Signature` ヘッダー共有秘密は変換に必要ない。
+`OAuth` と `X-Olo-Signature` ヘッダー共有シークレットは、変換には必要ありません。
 {% endalert %}
 
 {:start="3"}
-3\.[Test Eventを][3]Data Transformationに送信して、Webhookが正しく設定されていることを確認する。テストイベントを送信できるのは、[Developer Tools 権限を][4]持つ Olo Dashboard ユーザのみである。
+3\.[テストイベント][3]を Data Transformation に送信して、Webhook が正しく設定されていることを確認します。テストイベントを送信できるのは、[Developer Tools 権限を][4]持つ Olo Dashboard ユーザのみである。
 
-Olo は、Olo ウェブフック設定プロセスを完了する前に、Test Event ウェブフックからの成功応答を必要とする。
+Olo では、Olo Webhook 設定プロセスを完了する前に、テストイベント Webhook からの正常な応答が必要です。
 
 ### ステップ3:選んだOloイベントを受け入れる変換コードを書く
 
 このステップでは、ソース・プラットフォームから送信されるウェブフック・ペイロードを、JavaScriptオブジェクトの戻り値に変換する。
 
 1. データ変換 URL に、サポートする予定の Olo イベントのサンプルイベントペイロードを添えてリクエストを送信する。リクエストの書式については、[リクエストボディの書式を](#request-body-format)参照のこと。
-2. Data Transformationをリフレッシュし、**Webhook Detailsに**サンプルのイベントペイロードが表示されていることを確認する。
-3. データ変換コードを更新して、選択したOloイベントをサポートする。
-4. **Validateを**クリックすると、コードの出力のプレビューが返され、それが受け入れ可能な`/users/track` リクエストかどうかがチェックされる。
-5. データ変換を保存して有効にする。
+2. Data Transformation を更新し、\[**Webhook の詳細**] にサンプルイベントペイロードが表示されていることを確認します。
+3. 選択した Olo イベントをサポートするように Data Transformation コードを更新します。
+4. \[**検証**] をクリックして、コード出力のプレビューを返し、受け入れられる `/users/track` リクエストであるかどうかを確認します。
+5. Data Transformation を保存して有効化します。
 
-#### リクエスト・ボディのフォーマット
+#### リクエスト本文の形式
 
 この戻り値は、Brazeの `/users/track` リクエストの本文フォーマットに準拠しなければなりません。
 
@@ -78,11 +78,11 @@ Olo は、Olo ウェブフック設定プロセスを完了する前に、Test E
 
 ## Oloウェブフックのデータ変換の例
 
-このセクションには、出発点として使用できるテンプレートの例が含まれている。ゼロから始めるのも、特定のコンポーネントを削除するのも自由だ。
+このセクションには、出発点として使用できるテンプレートの例が含まれている。ゼロから作成するか、必要に応じて特定のコンポーネントを削除することができます。
 
-各テンプレートでは、`/users/track` リクエストを構築するために、`brazecall` という変数を定義している。
+各テンプレートでは、`/users/track` リクエストを作成するための変数 `brazecall` がコードにより定義されます。
 
-`/users/track `リクエストが`brazecall` に割り当てられた後、出力を作成するために明示的に`brazecall` を返す。
+`/users/track ` リクエストが `brazecall` に割り当てられた後、明示的に `brazecall` を返して出力を作成します。
 
 ### 単一イベント変換
 
@@ -143,9 +143,9 @@ return brazecall;
 
 ## マルチイベント変換
 
-Olo は、各 webhook の`X-Olo-Event-Type` ヘッダー内にイベントタイプを送信する。単一の変換内で複数の Olo webhook イベントをサポートするには、条件付きロジックを使用して、このヘッダー型の値に基づいて webhook ペイロードを変換する。  
+Olo は、各Webhookの `X-Olo-Event-Type` ヘッダーにイベントタイプを入れて送信します。単一の変換内で複数の Olo webhook イベントをサポートするには、条件付きロジックを使用して、このヘッダー型の値に基づいて webhook ペイロードを変換する。  
 
-以下の変換例では、JavaScriptは`UserSignedUp` と`OrderPlaced` のイベントに対して特定のペイロードを作成している。さらに、`else` の条件は、`UserSignedUp` と`OrderPlaced` のX-Olo-Event-TypeヘッダーのないBrazeに送られたOloイベントのペイロードを処理する。
+以下の変換例では、JavaScriptは`UserSignedUp` と`OrderPlaced` のイベントに対して特定のペイロードを作成している。さらに `else` 条件により、`UserSignedUp` および `OrderPlaced` の X-Olo-Event-Type ヘッダーなしで Braze に送信されたすべての Olo イベントのペイロードが処理されます。
 
 ```javascript
 // captures the value within the X-Olo-Event-Type header for use in the conditional logic
@@ -242,19 +242,19 @@ return brazecall;
 
 ### ステップ 4:Oloウェブフックを公開する
 
-BrazeでData Transformationを有効化したら、Oloダッシュボード内の[セルフサービスwebhooksツールを使って][2]webhookを公開する。ウェブフックがパブリッシュされると、データ変換はOloウェブフックのイベントメッセージを受信し始める。
+Braze で Data Transformation を有効化したら、Olo ダッシュボード内の[セルフサービス Webhook ツール][2]を使用して Webhook を公開します。Webhook が公開されると、Data Transformation はOlo Webhook イベントメッセージの受信を開始します。
 
 ## 知っておくべきこと
 
-### リトライ
+### 再試行
 
-Oloは、HTTPレスポンスステータスコードが`429 - Too Many Requests` 、または`5xx` （ゲートウェイのタイムアウトやサーバーエラーなど）の範囲になったWebhookコールを、リクエストをドロップする前に、24時間以内に50回まで再試行する。
+Olo は、HTTP 応答ステータスコードが`429 - Too Many Requests`、または`5xx` 範囲内のコード （ゲートウェイのタイムアウトやサーバーエラーなどに起因する） である場合、リクエストをドロップするまで、24時間以内に50回までWebhook 呼び出しを再試行します。
 
-### 少なくとも1回の配達
+### 1回以上の配信
 
-ウェブフック呼び出しの結果、HTTPレスポンスステータスコードが`429 - Too Many Requests` 、または`5xx` （ゲートウェイのタイムアウトやサーバーエラーなど）の範囲になった場合、Oloは24時間以内に50回までメッセージを再試行してからあきらめる。
+Webhook 呼び出しの結果、HTTP 応答ステータスコードが`429 - Too Many Requests` または`5xx` 範囲内のコード (ゲートウェイのタイムアウトやサーバーのエラーなどに起因する) である場合、Olo は24時間以内に最大50回メッセージを再試行してから、処理をあきらめます。
 
-したがって、Webhookはサブスクライバーによって複数回受信される可能性がある。`X-Olo-Message-Id` ヘッダーをチェックすることで、重複を無視するのは購読者次第である。
+したがって、Webhookはサブスクライバーによって複数回受信される可能性がある。サブスクライバーは、`X-Olo-Message-Id` ヘッダーを確認して重複を無視するかどうかを決定します。
 
 
 [1]: https://www.olo.com/
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify.md
index ed60980eefc..56656e22d08 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify.md
@@ -1,15 +1,15 @@
 ---
-nav_title: ショップファイ
-article_title: ショップファイ
+nav_title: Shopify
+article_title: Shopify
 alias: /shopify/
 alias: /partners/shopify/
 layout: dev_guide
 noindex: true
-guide_top_header: "ショップファイ"
+guide_top_header: "Shopify"
 guide_top_text: "Shopifyは、あらゆる規模の小売ビジネスを開始し、成長させ、マーケティングし、管理するための信頼できるツールを提供する、世界有数のコマース企業である。Shopifyは、信頼性のために設計されたプラットフォームとサービスによって、すべての人にとってより良い商取引を実現し、あらゆる消費者により良いショッピング体験を提供する。"
 description: "このランディングページには、Shopifyの概要、Shopifyの設定、Shopifyのデータ処理など、Shopifyに関するあらゆることが掲載されている。"
 
-guide_featured_title: "特集記事"
+guide_featured_title: "注目の記事"
 guide_featured_list:
 - name: Shopifyの概要
   link: /docs/shopify_overview/
@@ -23,7 +23,7 @@ guide_featured_list:
 - name: BrazeのShopifyデータ
   link: /docs/shopify_data/
   image: /assets/img/braze_icons/settings-01.svg
-- name: Shopifyヒストリカル・バックフィル
+- name: Shopify 履歴バックフィル
   link: /docs/shopify_historical_backfill/
   image: /assets/img/braze_icons/database-01.svg
 - name: Shopify商品同期
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify.md
index 4a9ccc19d4b..42cdda2c02a 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify.md
@@ -1,7 +1,7 @@
 ---
 nav_title: はじめに
 article_title: "Shopifyを使い始める"
-description: "この参考記事では、ShopifyウェブサイトにBraze Web SDKを実装する方法を概説している。"
+description: "このリファレンス記事では、Shopify Web サイトにBraze Web SDK を実装する方法について説明します。"
 page_type: partner
 search_tag: Partner
 alias: /getting_started_shopify/
@@ -10,7 +10,7 @@ page_order: 1
 
 # Shopifyを使い始める
 
-> この記事では、ShopifyウェブサイトにBraze Web SDKを実装する方法を概説する。実装後、[Shopifyと]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify)Brazeの統合設定を完了する方法については、[Shopifyを設定するを]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify)参照のこと。
+> この記事では、ShopifyウェブサイトにBraze Web SDKを実装する方法を概説する。実装が完了したら、「[Shopify の設定]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify)」を参照して、Braze と Shopify の統合を設定する方法を確認してください。
 
 ## 統合セットアップ・チェックリスト
 
@@ -20,37 +20,37 @@ page_order: 1
 
 ## ShopifyウェブサイトにWeb SDKを実装する {#implement-web-sdk}
 
-[Braze Web SDKは]({{site.baseurl}}/user_guide/onboarding_with_braze/web_sdk/)、Shopifyストアの顧客の行動を追跡するための強力なツールである。Web SDKを使用すると、Webまたはモバイルブラウザからセッションデータを収集し、ユーザーを識別し、ユーザーの行動データを記録することができる。また、インブラウザ・メッセージのようなネイティブ・メッセージング・チャンネルのロックを解除することもできる。
+[Braze Web SDK]({{site.baseurl}}/user_guide/onboarding_with_braze/web_sdk/) は、Shopify ストアの顧客の行動を追跡するために使用される強力なツールです。Web SDK を使用すると、セッションデータを収集し、ユーザーを識別し、Web ブラウザーまたはモバイルブラウザーからユーザーの動作データを記録できます。また、ブラウザー内メッセージのようなネイティブメッセージングチャネルを利用することもできます。
 
 Shopifyとの統合は、デフォルトで堅牢な機能を提供しているが、[Shopifyとの統合でサポートされていないイベントの]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_data_in_braze/)オンサイトトラッキングを追加したり、[コンテンツカードの]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards)ようなチャネルを追加したりするユースケースがある場合は、Web SDKをShopifyサイトに直接実装する必要があることを覚えておいてほしい。
 
-統合のオンボーディングを開始する前に、Web SDKを実装するためにどのようなパスを取るかについて、チームと以下を確認してほしい。
+統合のオンボーディングを開始する前に、Web SDKを実装するための方法について、チームと以下の点を確認してください。
 
 ### サポートされている機能
 
 |アイコン| 定義 
 |-------------|-------------
-|<i aria-hidden="true" class="fas fa-check" title="サポート"></i><span class="sr-only">対応</span> | サポート
+|<i aria-hidden="true" class="fas fa-check" title="サポート"></i><span class="sr-only">対応</span> | サポートされている
 |<i aria-hidden="true" class="fas fa-times" title="未対応"></i><span class="sr-only">対応</span> | サポートされていない
 {: .reset-td-br-1 .reset-td-br-2} 
 
-| 特徴 | Shopify ScriptTag経由のWeb SDK | ウェブSDKとの直接統合 theme.liquid | Shopify Hydrogenを介したWeb SDKの直接統合
+| 特徴 | Shopify ScriptTag経由のWeb SDK | theme.liquid による Web SDK 直接統合 | Shopify Hydrogenを介したWeb SDKの直接統合
 |-------------|-------------|-------------|------------
-| デフォルトの現場追跡      | <i class="fas fa-check" title="サポート"></i> | <i class="fas fa-times" title="サポートされていない"></i> | <i class="fas fa-times" title="サポートされていない"></i>          
-| キャプチャーフォームのユーザー照合（低いエンジニアリングリフトが必要）   | <i class="fas fa-check" title="サポート"></i> | <i class="fas fa-check" title="サポート"></i> | <i class="fas fa-times" title="サポートされていない"></i> 
-| チェックアウト・ユーザーの照合     | <i class="fas fa-check" title="サポート"></i>  | <i class="fas fa-times" title="サポートされていない"></i>   | <i class="fas fa-times" title="サポートされていない"></i>                                        
-| 製品を見た<br> 製品クリック<br> 放置されたカート   | <i class="fas fa-check" title="サポート"></i> |<i class="fas fa-check" title="サポート"></i> | <i class="fas fa-times" title="サポートされていない"></i> 
-| 放棄されたチェックアウト<br> オーダー作成<br> ブレイズ購入<br> 注文は支払われた<br> 部分的に履行された注文<br> 履行された注文<br> 注文のキャンセル<br> 払い戻し<br> 顧客の作成と更新 | <i class="fas fa-check" title="サポート"></i> | <i class="fas fa-check" title="サポート"></i> | <i class="fas fa-check" title="サポート"></i>
-| 歴史的埋め戻し | <i class="fas fa-check" title="サポート"></i>  | <i class="fas fa-check" title="サポート"></i>  | <i class="fas fa-check" title="サポート"></i>  
-| カタログ同期  |<i class="fas fa-check" title="サポート"></i> |<i class="fas fa-check" title="サポート"></i>  |<i class="fas fa-check" title="サポート"></i>
-| EメールとSMSの購読者収集    | <i class="fas fa-check" title="サポート"></i>| <i class="fas fa-check" title="サポート"></i>  | <i class="fas fa-check" title="サポート"></i>     
-| デフォルトのアプリ内メッセージのサポート   | <i class="fas fa-check" title="サポート"></i>  | <i class="fas fa-check" title="サポート"></i>  | <i class="fas fa-times" title="サポートされていない"></i>     
+| デフォルトのオンサイトトラッキング      | <i class="fas fa-check" title="サポートされている"></i> | <i class="fas fa-times" title="サポートされていない"></i> | <i class="fas fa-times" title="サポートされていない"></i>          
+| キャプチャフォームのユーザーの照合 (必要なエンジニアリング作業は少ない)   | <i class="fas fa-check" title="サポートされている"></i> | <i class="fas fa-check" title="サポートされている"></i> | <i class="fas fa-times" title="サポートされていない"></i> 
+| チェックアウトユーザーの照合     | <i class="fas fa-check" title="サポートされている"></i>  | <i class="fas fa-times" title="サポートされていない"></i>   | <i class="fas fa-times" title="サポートされていない"></i>                                        
+| 製品の閲覧<br> 製品クリック<br> カート放棄   | <i class="fas fa-check" title="サポートされている"></i> |<i class="fas fa-check" title="サポートされている"></i> | <i class="fas fa-times" title="サポートされていない"></i> 
+| 購入手続き放棄<br> 注文の作成<br> Braze 購入<br> 注文の支払い<br> 部分的に履行された注文<br> フルフィルメントが完了した注文<br> 注文のキャンセル<br> 払い戻しの作成<br> 顧客の作成と更新 | <i class="fas fa-check" title="サポートされている"></i> | <i class="fas fa-check" title="サポートされている"></i> | <i class="fas fa-check" title="サポートされている"></i>
+| 歴史的埋め戻し | <i class="fas fa-check" title="サポートされている"></i>  | <i class="fas fa-check" title="サポートされている"></i>  | <i class="fas fa-check" title="サポートされている"></i>  
+| カタログ同期  |<i class="fas fa-check" title="サポートされている"></i> |<i class="fas fa-check" title="サポートされている"></i>  |<i class="fas fa-check" title="サポートされている"></i>
+| メールおよび SMS サブスクライバーの収集    | <i class="fas fa-check" title="サポートされている"></i>| <i class="fas fa-check" title="サポートされている"></i>  | <i class="fas fa-check" title="サポートされている"></i>     
+| デフォルトのアプリ内メッセージのサポート   | <i class="fas fa-check" title="サポートされている"></i>  | <i class="fas fa-check" title="サポートされている"></i>  | <i class="fas fa-times" title="サポートされていない"></i>     
 | デフォルトのコンテンツカードをサポート   | <i class="fas fa-times" title="サポートされていない"></i> | <i class="fas fa-times" title="サポートされていない"></i> | <i class="fas fa-times" title="サポートされていない"></i>   
-| デフォルトのウェブ・プッシュ対応     | <i class="fas fa-times" title="サポートされていない"></i> | <i class="fas fa-times" title="サポートされていない"></i> | <i class="fas fa-times" title="サポートされていない"></i>
+| デフォルトのWeb プッシュのサポート     | <i class="fas fa-times" title="サポートされていない"></i> | <i class="fas fa-times" title="サポートされていない"></i> | <i class="fas fa-times" title="サポートされていない"></i>
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}    
 
 {% tabs %}
-{% tab Shopifyスクリプトタグ %}
+{% tab Shopify ScriptTag %}
 
 ### Shopify ScriptTagでBraze Web SDKを実装する
 
@@ -59,12 +59,12 @@ Shopifyとの統合は、デフォルトで堅牢な機能を提供している
 Brazeをすぐに使い始めたい場合は、BrazeがBraze Web SDK用の定義済みスクリプトをShopifyストアサイトに直接ロードするオプションがある。
 
 {% alert important %}
-この統合方法のためのBraze Web SDKの事前定義スクリプトはカスタマイズできない。
+この統合方法では、あらかじめ定義されているBraze Web SDK のスクリプトはカスタマイズできません。
 {% endalert %}
 
 #### Shopifyとの統合の仕組み
 
-Shopifyサイトがロードされると、Shopifyはスクリプトタグをページにロードする必要があるかどうかをチェックする。このプロセスの間、Braze Web SDKスクリプトは、ストアのページまたはチェックアウトの注文状況ページに読み込まれる。 
+Shopifyサイトがロードされると、Shopifyはスクリプトタグをページにロードする必要があるかどうかをチェックする。処理中に、Braze Web SDK スクリプトがストアのページまたはチェックアウトの注文ステータスページに読み込まれます。 
 
 また、Shopify ScriptTagやアプリ内メッセージングをチャネルとして必要とする商品閲覧、商品クリック、カート放棄イベントを選択した場合は、事前に定義されたスクリプトを追加する。  
 
@@ -76,23 +76,23 @@ Shopifyセットアップコンポーザーから、アスタリスク(\*)で示
 
 #### Shopifyのメールキャプチャフォームとユーザー照合 
 
-キャプチャー・フォームは、顧客のライフサイクルの初期段階で、特定可能な顧客情報を取得し、下流のメッセージングやエンゲージメントに役立てる。 
+キャプチャフォームにより、顧客のライフサイクルの早期段階で、ダウンストリームのメッセージングとエンゲージメントのために特定可能な顧客情報が取得されます。 
 
-Web SDK は、`device_id` を使用することにより、Shopify の現場での行動と匿名ユーザーを追跡する。BrazeのShopify ScriptTagインテグレーションは、ニュースレター登録などのShopifyのメール取り込みフォームからのメールを、ユーザーの`device_id` 。
+Web SDK は `device_id` を使用して、Shopify のオンサイト行動と匿名ユーザーを追跡します。BrazeのShopify ScriptTagインテグレーションは、ニュースレター登録などのShopifyのメール取り込みフォームからのメールを、ユーザーの`device_id` 。
 
 典型的なメール・キャプチャ・フォームには以下のようなものがある： 
 - 電子メール・キャプチャ・フォーム 
 - ニュースレター登録フォーム
 
-ユーザーのEメールと`device_id` を照合する方法は2つある： 
+ユーザーのメールと `device_id` を照合するには、次の2つの方法があります。 
 - Braze自動メールキャプチャスクリプトを使用する 
 - `setEmail` または`setPhoneNumber` メソッドを呼び出す
 
-##### Eメールや電話でのサインアップを獲得する
+##### メールや電話での登録のキャプチャ
 
 Brazeを使えば、[Eメールや]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form/#step-1-create-an-in-app-message-campaign) [SMS、WhatsAppの]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/templates/phone_number_capture)登録フォームを使って、Web SDKやアプリ内メッセージを活用できる。 
 
-ShopifyのEメールや電話番号のキャプチャ、またはサードパーティのキャプチャフォームを使用する場合は、Braze Web SDKで追跡されるユーザーに直接設定することができる。例えば、顧客のEメールアドレスを取得した場合、それをユーザー・プロフィールに次のように設定することができる：
+ShopifyのEメールや電話番号のキャプチャ、またはサードパーティのキャプチャフォームを使用する場合は、Braze Web SDKで追跡されるユーザーに直接設定することができる。たとえば、顧客のメールアドレスを取得した場合、そのメールアドレスを顧客のユーザープロファイルに次のように設定できます。
 
 {% raw %}
 ```javascript
@@ -102,10 +102,10 @@ braze.getUser().setEmail(<email address>);
 
 これらの値の設定の詳細については、以下のJavascriptリソースを参照のこと：
 
-- ユーザーの[Eメールを](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemail)設定する
-- ユーザーの[電話番号を](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setphonenumber)設定する
+- ユーザーの[メール](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemail)を設定する
+- ユーザーの[電話番号](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setphonenumber)を設定する
 
-Eメールや電話番号を収集する際に、このようにユーザーの購読状態を設定することもできる：
+次のように、ユーザーのメールまたは電話番号を収集するときに、ユーザーのサブスクリプションの状態を設定することもできます。
 
 {% raw %}
 ```javascript
@@ -115,10 +115,10 @@ braze.getUser().setEmailNotificationSubscriptionType(braze.User.NotificationSubs
 
 これらの値の設定の詳細については、以下のJavascriptリソースを参照のこと：
 
-- ユーザーの[電子メール通知購読タイプを](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemailnotificationsubscriptiontype)設定する
-- ユーザーを[購読グループに](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#addtosubscriptiongroup)追加する
+- ユーザーの[メール通知サブスクリプションタイプ](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemailnotificationsubscriptiontype)を設定する
+- [サブスクリプショングループ](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#addtosubscriptiongroup)にユーザーを追加する
 
-**第三者キャプチャ・フォームの実装例**
+**サードパーティキャプチャフォームの実装例**
 
 1. `theme.liquid` で、以下のスニペットを`head tag` にコピーする：
 
@@ -141,24 +141,24 @@ braze.getUser().setEmailNotificationSubscriptionType(braze.User.NotificationSubs
 {% endraw %}
 
 {: start="2"}
-2\.まず、スクリプトが最初にロードされるように、`setInterval` 。
-3\.`{FORM_ID}` 、キャプチャしたいフォームの要素IDに置き換える。
-(ContactFooter "など）。
+2\.まず、スクリプトが最初に読み込まれるようにするため、`setInterval` を呼び出します。
+3\.`{FORM_ID}` を、キャプチャするフォームの要素 ID に置き換えます
+(「ContactFooter」など)。
 4\.`{INPUT_EMAIL_ID}` 、フォーム内のEメール入力フィールドの要素IDに置き換える。
-5. フォームが送信されると、スクリプトは電子メールの入力値で`setEmail` 。
-6. スクリプトがロードされた後、`clearInterval` 。
+5. フォームが送信されると、スクリプトはメール入力値を使用して `setEmail` を呼び出します。
+6. スクリプトが読み込まれたら、スクリプトの読み込みが1回だけであるようにするため、`clearInterval` を呼び出します。
 
 {% alert note %}
 現時点では、BrazeのメールキャプチャフォームはShopifyの顧客を作成しない。その結果、顧客がチェックアウトを通過するか、アカウントを作成するまで、Shopifyのユーザープロファイルが関連付けられていないBrazeのユーザープロファイルを持つことができる。
 {% endalert %}
 
-#### 導入後に期待されること
+#### 実装後に予期されること
 
 **Braze Web SDKの初期化**
 
 Web SDKはセッション開始時に初期化される。Brazeは、Shopifyの顧客ID、Eメール、電話番号などの他の識別子がShopifyストアのゲスト訪問者から容易に入手できない可能性があるため、匿名ユーザーデータを追跡するために`device_id` を収集する必要がある。
 
-また、`device_id` 、チェックアウト後に顧客がより多くの特定可能な情報（電子メールアドレスや電話番号など）を提供した場合、匿名ユーザープロファイルとユーザーデータを照合するために使用される。
+また、チェックアウトプロセス後に顧客からさらに識別可能な情報 (メールアドレスや電話番号など) が提供されるため、ユーザーデータを匿名ユーザープロファイルと照合するために `device_id` が使用されます。
 
 **Braze Web SDKバージョン**
 
@@ -166,7 +166,7 @@ Shopify ScriptTag統合によるBraze Web SDKの現在のバージョンはv4.2
 
 **1 か月あたりのアクティブユーザー数 (MAU)**
 
-Web SDKはShopifyの顧客やゲストのセッションを追跡する。その結果、これはBrazeダッシュボードのレポート内でMAUとして計上され、MAU割り当ての対象となる。匿名ユーザーもMAUにカウントされることに注意することが重要だ。モバイルデバイスの場合、匿名ユーザーはデバイスによって決まります。Web ユーザーの場合、匿名ユーザーはブラウザーのキャッシュによって決まります。
+Web SDKはShopifyの顧客やゲストのセッションを追跡する。その結果、これは Braze ダッシュボードのレポート内で MAU にカウントされ、MAU 割り当ての対象となります。匿名ユーザーも MAU にカウントされることに注意してください。モバイルデバイスの場合、匿名ユーザーはデバイスによって決まります。Web ユーザーの場合、匿名ユーザーはブラウザーのキャッシュによって決まります。
 
 {% endtab %}
 
@@ -174,41 +174,41 @@ Web SDKはShopifyの顧客やゲストのセッションを追跡する。その
 
 ### WebSDKをShopifyサイトに直接実装する theme.liquid
 
-Brazeは、Web SDKを実装するための複数の方法を提供している：
+Braze には、Web SDK を実装する方法が複数あります。
 - Web SDKをShopify`theme.liquid` ファイルに直接追加する。
 - Google Tag Manager 
 
 すでにShopifyストアにWeb SDKをインストールしている場合でも、オンボーディングプロセス内でShopify ScriptTagのセットアップを進めることができる。 
 
-インストールプロセス中、BrazeはWeb SDKのインスタンスがShopifyストアですでに利用可能かどうかをチェックする。既存の実装がある場合、BrazeはWeb SDKを有効にするための定義済みスクリプトを読み込まない。その後、必要なスクリプトを追加して、選択したイベントをトラッキングできるようにしたり、ブラウザ内のメッセージングを有効にしたりする。
+インストールプロセス中、BrazeはWeb SDKのインスタンスがShopifyストアですでに利用可能かどうかをチェックする。既存の実装がある場合、Braze はWeb SDK を有効にするために事前定義スクリプトを読み取りません。その後、必要なスクリプトを追加して、選択したイベントをトラッキングできるようにしたり、ブラウザ内のメッセージングを有効にしたりする。
 
 #### 有効化する方法
 
-手動でWeb SDKを実装するには、[初期SDKセットアップを]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/)参照のこと。Google Tag Manager経由でWeb SDKを実装するには、[Google Tag Manager for Webを]({{site.baseurl}}/developer_guide/platform_integration_guides/web/google_tag_manager#google-tag-manager)参照のこと。 
+Web SDK を手動で実装するには、「[SDK の初期セットアップ]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/)」を参照してください。Google Tag Manager を使用して Web SDK を実装するには、「[Google Tag Manager for Web]({{site.baseurl}}/developer_guide/platform_integration_guides/web/google_tag_manager#google-tag-manager)」を参照してください。 
 
-どちらの実装パスでも、Web SDKインテグレーションに以下が含まれていることを確認すること： 
-- Web SDKのバージョンはv4.0+である。
+どちらの実装方法でも、Web SDK 統合に以下が含まれているか、または Shopify 統合がサポートされない予定であることを確認します。 
+- Web SDKバージョン v4.0+
 - セッション開始時にWeb SDKが初期化される
 
 #### Shopifyのメールキャプチャフォームとユーザー照合 
 
-キャプチャー・フォームは、顧客のライフサイクルの初期段階で、特定可能な顧客情報を取得し、下流のメッセージングやエンゲージメントに役立てる。 
+キャプチャフォームにより、顧客のライフサイクルの早期段階で、ダウンストリームのメッセージングとエンゲージメントのために特定可能な顧客情報が取得されます。 
 
-Web SDK は、`device_id` を使用することにより、Shopify の現場での行動と匿名ユーザーを追跡する。BrazeのShopify ScriptTagインテグレーションは、ニュースレター登録などのShopifyのメール取り込みフォームからのメールを、ユーザーの`device_id` 。
+Web SDK は `device_id` を使用して、Shopify のオンサイト行動と匿名ユーザーを追跡します。BrazeのShopify ScriptTagインテグレーションは、ニュースレター登録などのShopifyのメール取り込みフォームからのメールを、ユーザーの`device_id` 。
 
 典型的なメール・キャプチャ・フォームには以下のようなものがある： 
 - 電子メール・キャプチャ・フォーム 
 - ニュースレター登録フォーム
 
-ユーザーのEメールと`device_id` を照合する方法は2つある： 
+ユーザーのメールと `device_id` を照合するには、次の2つの方法があります。 
 - Braze自動メールキャプチャスクリプトを使用する 
 - `setEmail` または`setPhoneNumber` メソッドを呼び出す
 
-##### Eメールや電話でのサインアップを獲得する
+##### メールや電話での登録のキャプチャ
 
 Brazeを使えば、[Eメールや]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form/#step-1-create-an-in-app-message-campaign) [SMS、WhatsAppの]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/templates/phone_number_capture)登録フォームを使って、Web SDKやアプリ内メッセージを活用できる。 
 
-Shopifyの電子メールや電話番号のキャプチャ、またはサードパーティのキャプチャフォームを使用する場合は、Braze Web SDKで追跡されるユーザーオブジェクトに直接設定することができる。例えば、顧客のEメールアドレスを取得した場合、それをユーザー・プロフィールに次のように設定することができる：
+Shopifyの電子メールや電話番号のキャプチャ、またはサードパーティのキャプチャフォームを使用する場合は、Braze Web SDKで追跡されるユーザーオブジェクトに直接設定することができる。たとえば、顧客のメールアドレスを取得した場合、そのメールアドレスを顧客のユーザープロファイルに次のように設定できます。
 
 {% raw %}
 ```javascript
@@ -218,10 +218,10 @@ braze.getUser().setEmail(<email address>);
 
 これらの値の設定の詳細については、以下のJavascriptリソースを参照のこと：
 
-- ユーザーの[Eメールを](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemail)設定する
-- ユーザーの[電話番号を](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setphonenumber)設定する
+- ユーザーの[メール](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemail)を設定する
+- ユーザーの[電話番号](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setphonenumber)を設定する
 
-また、このようにEメールや電話番号を収集しながら、ユーザーの購読状態を設定することもできる：
+次のように、ユーザーのメールまたは電話番号を収集するときに、ユーザーのサブスクリプションの状態を設定することもできます。
 
 {% raw %}
 ```javascript
@@ -231,10 +231,10 @@ braze.getUser().setEmailNotificationSubscriptionType(braze.User.NotificationSubs
 
 これらの値の設定の詳細については、以下のJavascriptリソースを参照のこと：
 
-- ユーザーの[電子メール通知購読タイプを](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemailnotificationsubscriptiontype)設定する
-- ユーザーを[購読グループに](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#addtosubscriptiongroup)追加する
+- ユーザーの[メール通知サブスクリプションタイプ](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemailnotificationsubscriptiontype)を設定する
+- [サブスクリプショングループ](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#addtosubscriptiongroup)にユーザーを追加する
 
-**第三者キャプチャ・フォームの実装例**
+**サードパーティキャプチャフォームの実装例**
 
 1. `theme.liquid` で、以下のスニペットを`head tag` にコピーする：
 
@@ -257,46 +257,46 @@ braze.getUser().setEmailNotificationSubscriptionType(braze.User.NotificationSubs
 {% endraw %}
 
 {: start="2"}
-2\.まず、スクリプトが最初にロードされるように、`setInterval` 。
-3\.`{FORM_ID}` 、キャプチャしたいフォームの要素IDに置き換える。
-(ContactFooter "など）。
+2\.まず、スクリプトが最初に読み込まれるようにするため、`setInterval` を呼び出します。
+3\.`{FORM_ID}` を、キャプチャするフォームの要素 ID に置き換えます
+(「ContactFooter」など)。
 4\.`{INPUT_EMAIL_ID}` 、フォーム内のEメール入力フィールドの要素IDに置き換える。
-5. フォームが送信されると、スクリプトは電子メールの入力値で`setEmail` 。
-6. スクリプトがロードされた後、`clearInterval` 。
+5. フォームが送信されると、スクリプトはメール入力値を使用して `setEmail` を呼び出します。
+6. スクリプトが読み込まれたら、スクリプトの読み込みが1回だけであるようにするため、`clearInterval` を呼び出します。
 
 {% alert note %}
 現時点では、BrazeのメールキャプチャフォームはShopifyの顧客を作成しない。その結果、顧客がチェックアウトを通過するか、アカウントを作成するまで、Shopifyのユーザープロファイルが関連付けられていないBrazeのユーザープロファイルを持つことができる。
 {% endalert %}
 
-#### 統合後に期待されること
+#### 統合後に予期されること
 
 **Braze Web SDKの初期化**
 
 Web SDKはセッション開始時に初期化される。Brazeは、Shopifyの顧客ID、Eメール、電話番号などの他の識別子がShopifyストアのゲスト訪問者から容易に入手できない可能性があるため、匿名ユーザーデータを追跡するために`device_id` を収集する必要がある。
 
-また、`device_id` は、顧客がチェックアウト・プロセスの間やその後に、より多くの特定可能な情報（Eメールや電話番号など）を提供する際に、匿名ユーザー・プロフィールとユーザー・データを照合するためにも使用される。
+また、チェックアウトプロセス中およびこのプロセスの後に顧客からさらに識別可能な情報 (メールアドレスや電話番号など) が提供されるため、ユーザーデータを匿名ユーザープロファイルと照合するために `device_id` が使用されます。
 
 **Braze Web SDKバージョン**
 
-Braze Web SDKの現在のバージョンはv4.0以上であること。
+Braze Web SDK の現在のバージョンは v4.0 以上である必要があります。
 
 **1 か月あたりのアクティブユーザー数 (MAU)**
 
-Web SDKはShopifyの顧客やゲストのセッションを追跡する。その結果、これはBrazeダッシュボードのレポート内でMAUとして計上され、MAU割り当ての対象となる。匿名ユーザーもMAUにカウントされることに注意することが重要だ。モバイルデバイスの場合、匿名ユーザーはデバイスによって決まります。Web ユーザーの場合、匿名ユーザーはブラウザーのキャッシュによって決まります。
+Web SDKはShopifyの顧客やゲストのセッションを追跡する。その結果、これは Braze ダッシュボードのレポート内で MAU にカウントされ、MAU 割り当ての対象となります。匿名ユーザーも MAU にカウントされることに注意してください。モバイルデバイスの場合、匿名ユーザーはデバイスによって決まります。Web ユーザーの場合、匿名ユーザーはブラウザーのキャッシュによって決まります。
 
 {% endtab %}
-{% tab ヘッドレスShopifyサイト %}
+{% tab ヘッドレス Shopify サイト %}
 
-### ヘッドレスShopifyサイトに直接Web SDKを実装する {#headless-site}
+### Web SDK をヘッドレス Shopify サイトに直接実装する {#headless-site}
 
-BrazeのShopify ScriptTagインテグレーションは、Shopifyのヘッドレスサイトとは互換性がない。その結果、閲覧された商品、クリックされた商品、放棄されたカートのイベントをデフォルトでサポートしたり、あらかじめ定義されたスクリプトを使ってアプリ内メッセージを有効にしたりすることはできない。 
+Braze Shopify ScriptTag 統合には、ヘッドレス Shopify サイトとの互換性があません。その結果、閲覧された商品、クリックされた商品、放棄されたカートのイベントをデフォルトでサポートしたり、あらかじめ定義されたスクリプトを使ってアプリ内メッセージを有効にしたりすることはできない。 
 
 #### 有効化する方法
 
-Web SDKを直接ヘッドレスShopifyサイトに統合するには、[Inital SDK Setup for Webを]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/)参照のこと。
+Web SDK をヘッドレス Shopify サイトに直接統合するには、「[ウェブ用SDKの初期セットアップ]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/)」を参照してください。
 
-Web SDKの統合に以下が含まれていることを確認する： 
-- Web SDKのバージョンはv4.0以上でなければならない。
+Web SDK 統合に以下が含まれていることを確認します。 
+- Web SDK バージョンは v4.0+ である必要があります。
 - セッション開始時にWeb SDKが初期化される
 
 #### ユーザー照合のためにShopifyフォームを設定する
@@ -304,31 +304,31 @@ Web SDKの統合に以下が含まれていることを確認する：
 Eコマースブランドは、Shopifyのサイト上で、Eメールキャプチャフォームのように、チェックアウトの前に顧客から識別可能な情報を取得するエクスペリエンスを持っている可能性が高い。
 
 Web SDK は、Shopify のサイト上での行動と匿名ユーザーを`device_id` で追跡する。メールアドレスが匿名ユーザープロフィールに追加されていることを確認するには、ニュースレターまたはメール収集フォームのいずれかに以下を追加する： 
-- [セットEメール](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemail) 
+- [setEmail](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#setemail) 
   - Eメール・キャプチャやニュースレターの登録
-- [エイリアスを追加する](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#addalias) 
+- [addAlias](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.user.html#addalias) 
   - "alias_label": "shopify_email" 
   - "alias_name": "example@email.com"
 
 ユーザーがアカウントに登録またはログインする際、外部IDで[ユーザー・プロファイルを識別]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#identified-user-profiles)したい場合がある。ユーザーが登録しログインした後、[changeUser](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#changeuser)メソッドを追加し、ユーザーがアカウントを作成したりログインした場合に外部IDを割り当てる。 
 
 {% alert note %}
-ユーザー・プロファイルに一時的なエイリアスを設定すれば、[users/mergeエンドポイント・エンドポイントへの]({{site.baseurl}}/api/endpoints/user_data/post_users_merge)リクエストを進め、後の時点でユーザーを特定することができる。
+ユーザープロファイルに一時エイリアスを設定した場合は、[users/merge エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_users_merge)へのリクエストを実行して、後でユーザーを識別できます。
 {% endalert %}
 
-#### チェックアウトのユーザー照合を設定する {#headless-checkout}
+#### チェックアウトユーザーの照合を設定する {#headless-checkout}
 
 放棄されたチェックアウトイベントを有効にすると、BrazeはShopifyのチェックアウト/作成ウェブフックを受信する。Brazeは、メールアドレス、電話番号、またはShopifyの顧客IDのいずれかによって、既存のユーザープロファイルとのマッチングを試みる。一致するプロファイルがない場合、Brazeはエイリアスのプロファイルを作成する。 
 
 Shopifyウェブフックによって作成されたShopifyエイリアスユーザープロファイルと現場で追跡されたユーザプロファイルがマージされることを確認するには、以下の手順で[`/users/merge` エンドポイントを]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/)使用することができる。 
 
 {% alert tip %}
-SDKまたは`theme.liquid` ファイル上で行われるAPIコールによってカスタムイベントをログに記録し、`users/merge` エンドポイントへのリクエストを含むキャンバスをトリガーすることができる。これらの方法の概要は以下の通りである。
+`users/merge` エンドポイントへのリクエストを含むキャンバスをトリガーするために、`theme.liquid` ファイルに対して行われる SDK または API 呼び出しでカスタムイベントをログに記録できます。これらの方法については以下で説明します。
 {% endalert %}
 
 顧客がShopifyサイトを訪問すると、すぐに匿名ユーザーが作成される。このユーザーには自動的にBraze`device_id` が割り当てられる。 
 
-1. 新規セッション時に、サイト訪問者に一意の[ユーザーエイリアスを]({{site.baseurl}}/api/objects_filters/user_alias_object#user-alias-object-specification)ランダムに割り当てる。
+1. 新しいセッションで、サイト訪問者に一意の[ユーザーエイリアス]({{site.baseurl}}/api/objects_filters/user_alias_object#user-alias-object-specification)をランダムに割り当てます。
 
 2. ユーザーがサイト上でアクションを実行すると、[カスタム・イベントとして]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/tracking_custom_events)ログに記録するか、[ユーザー属性をキャプチャする]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/setting_custom_attributes/)。ユーザーがチェックアウトに進み、ShopifyのフォームにEメールを入力すると、Shopifyの顧客IDが作成される。Brazeは、Shopifyのウェブフックを処理し、Eメール、電話、Shopifyのエイリアスが既存のユーザーと一致しない場合は、新しいユーザープロファイルを作成する。
 
@@ -347,7 +347,7 @@ SDKまたは`theme.liquid` ファイル上で行われるAPIコールによっ
 {% subtab API approach %}
 
 {: start="3"}
-3\.ユーザープロファイルの重複を防ぐには、Braze`device_id` を含むユーザープロファイルとShopifyエイリアスプロファイルを含むユーザープロファイルをマージする必要がある。遅延を設定し、`do_not_merge` 属性でユーザーを更新し、[`/users/merge` エンドポイントに]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/)リクエストを行う API トリガーキャンバスを作成できる。また、`merge_user` のようなカスタム・イベントを記録して、キャンバスをトリガーすることもできる。 
+3\.ユーザープロファイルの重複を防ぐには、Braze`device_id` を含むユーザープロファイルとShopifyエイリアスプロファイルを含むユーザープロファイルをマージする必要がある。遅延を設定し、`do_not_merge` 属性を使用してユーザーを更新し、[`/users/merge` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/) へのリクエストを行う API トリガーキャンバスを作成できます。また、`merge_user` のようなカスタム・イベントを記録して、キャンバスをトリガーすることもできる。 
 
 
 {% endsubtab %}
@@ -360,16 +360,16 @@ SDKまたは`theme.liquid` ファイル上で行われるAPIコールによっ
 {% endsubtabs %}
 
 {: start="4"}
-4\.キャンバスの入力条件では、未確認のユーザー・プロファイルのみを対象とする。つまり、外部IDを持たず、`do_not_merge` 。<br><br>![`do_not_merge` 、キャンバスコンポーザーの「エントリー観客」ステップをフィルターとして使用する。]({% image_buster /assets/img/Shopify/shop_usermerge_canvas_entrycriteria.png %})
+4\.キャンバスのエントリ条件で、識別されていないユーザープロファイルのみをターゲットにします。つまり、external ID がなく、`do_not_merge` は真ではありません。<br><br>![Canvas 作成画面で `do_not_merge` をフィルターとして使用している「エントリオーディエンス」ステップ。]({% image_buster /assets/img/Shopify/shop_usermerge_canvas_entrycriteria.png %})
 
 {: start="5"}
-5. キャンバスの入力条件を設定したら、キャンバスフローを作成する。キャンバスの最初のステップを**Delay**ステップにして、処理中に起こりうるレースコンディションを防ぐ。<br><br>![] （{% image_buster /assets/img/Shopify/shop_usermerge_canvas_delay.png %} ）。
+5. キャンバスの入力条件を設定したら、キャンバスフローを作成する。キャンバスの最初のステップを**Delay**ステップにして、処理中に起こりうるレースコンディションを防ぐ。<br><br>![キャンバス作成画面の「遅延」ステップ。]({% image_buster /assets/img/Shopify/shop_usermerge_canvas_delay.png %})
 
 {: start="6"}
-6. これらのユーザーは次のステップでマージされるため、`do_not_merge` カスタム属性を "true "に更新する**ユーザー更新**ステップを作成できる。<br><br>![キャンバスのコンポーザーで、`do_not_merge` を属性として選択したユーザーによる更新ステップ。]({% image_buster /assets/img/Shopify/shop_usermerge_canvas_userupdate.png %})
+6. これらのユーザーは次のステップでマージされるため、\[**ユーザー更新**] ステップを作成して、`do_not_merge` カスタム属性を「true」に更新できます。<br><br>![`do_not_merge` が属性として選択されているキャンバス作成画面の「ユーザー更新」ステップ。]({% image_buster /assets/img/Shopify/shop_usermerge_canvas_userupdate.png %})
 
 {: start="7"}
-7. 次に、ウェブフックを使って**メッセージ・**ステップを作成する。<br><br>![Webhookメッセージングチャンネルを持つキャンバスコンポーザーのメッセージステップ。]({% image_buster /assets/img/Shopify/shop_usermerge_canvas_webhook.png %}) 
+7. 次に、ウェブフックを使って**メッセージ・**ステップを作成する。<br><br>![Webhook メッセージングチャネルが使用されているキャンバス作成画面の「メッセージ」ステップ。]({% image_buster /assets/img/Shopify/shop_usermerge_canvas_webhook.png %}) 
 
 {% raw %}
 ```javascript
@@ -395,7 +395,7 @@ SDKまたは`theme.liquid` ファイル上で行われるAPIコールによっ
 {% endraw %}
 
 {% alert tip %}
-`merge_users` の動作については、[POSTを参照のこと：ユーザーをマージする]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/#merge_updates-behavior).
+`merge_users` の動作については、[POSTを参照のこと：ユーザーをマージする]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/#merge_updates-behavior)」を参照してください。
 {% endalert %}
 
 {: start="8"}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify.md
index 19f11a55250..70b3c354d63 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify.md
@@ -11,11 +11,11 @@ page_order: 2
 
 # Braze でのShopifyのセットアップ
 
-> BrazeとのShopifyインテグレーションの設定を終了する方法について概説した。[ Braze Web SDK]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#implement-web-sdk) をShopify Web サイトに実装した後は、次の手順に従います。
+> この記事では、Shopify と Braze の統合を設定する方法を説明します。[ Braze Web SDK]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#implement-web-sdk) をShopify Web サイトに実装した後は、次の手順に従います。
 
 ## BrazeでのShopifyインテグレーションの設定
 
-### ステップ1:Shopifyストアを接続する
+### ステップ1:Shopify ストアを接続する
 
 Braze で、**Partner Integrations**> **Technology Partners** に移動し、"Shopify" を検索します。
 
@@ -48,25 +48,25 @@ Braze アプリをインストールした後、Braze にリダイレクトさ
 ![]({% image_buster /assets/img/Shopify/begin_setup.png %}){: style="max-width:70%"}
 
 {% alert note %}
-この時点では、1 つのワークスペースにつき 1 つのストアのみ接続できます。複数のShopifyストアをワークスペースに接続したい場合は、マルチストアベータのShopifyについて詳しくは、顧客のサクセスマネージャーにお問い合わせください。
+この時点では、ワークスペースあたり1つのストアだけを接続できます。複数のShopifyストアをワークスペースに接続したい場合は、マルチストアベータのShopifyについて詳しくは、顧客のサクセスマネージャーにお問い合わせください。
 {% endalert %}
 
 ### ステップ2:イベントと履歴バックフィルの選択
 
-Shopifyストアを接続した後、手順2に進み、統合の一部として含めるイベントを選択します。少なくとも1つのイベントを選択する必要があります。
+Shopify ストアを接続したら、ステップ2に進み、統合の一部として含めるイベントを選択します。少なくとも1つのイベントを選択する必要があります。
 
 ![]({% image_buster /assets/img/Shopify/shopify_step_2_events.png %}){: style="max-width:70%"}
 
-**Product Viewed**、**Product Clicked**、または**Abandoned Cart**イベントを選択すると、"トラッキングのBraze Web SDKが必要になります。Braze Web SDKを[ Shopify ScriptTag]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=shopify%20scripttag#supported-features) またはShopifyのサイト[`theme.liquid`]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=theme.liquid#supported-features) のいずれかで実装すると、Braze は自動的に"トラッキング スクリプトと読み込むをサイトに生成します。[ヘッドレスShopifyサイト]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#implement-web-sdk)にWeb SDKを実装する場合は、これらのイベントの"トラッキングを手動で有効にする必要があります。 
+\[**製品の表示**]、\[**製品のクリック**]、または \[**カート放棄**] イベントを選択する場合、トラッキングのために Braze Web SDKが必要になります。[Shopify ScriptTag]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=shopify%20scripttag#supported-features) を使用して Braze Web SDK を実装するか、または Shopify サイト [`theme.liquid`]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=theme.liquid#supported-features) に直接実装すると、Braze によりトラッキングスクリプトが自動的に生成され、サイトに読み込まれます。Web SDK を[ヘッドレス Shopifyサイト]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#implement-web-sdk)に実装する場合は、これらのイベントのトラッキングを手動でオンにする必要があります。 
 
 #### 履歴データのバックフィル(オプション)
 
-オプションで、インストール前の過去90 日間の購入のバックフィルを有効にすることができます。以前の顧客と購買データを自動的に同期することで、すぐにターゲットを設定し、顧客s に参加することができます。詳細については、Shopify履歴バックフィルを確認してください。
+必要に応じて、インストール前の過去90日間の購入のバックフィルを有効にできます。過去の顧客データと購入データを自動的に同期することで、顧客のターゲティングや顧客とのエンゲージメントをすぐに開始できます。詳細については、Shopify 履歴バックフィルを確認してください。
 
 ![]({% image_buster /assets/img/Shopify/shop_setup_4.png %}){: style="max-width:70%"}
 
 {% alert warning %}
-オーダー作成イベントおよびBraze購入イベントをインポートするには、**Order Created**および**Braze購入イベント**を選択し、統合の一部として含める必要があります。
+バックフィルで注文作成イベントと Braze 購入イベントをインポートするには、\[**注文作成イベント**] と \[**Braze 購入イベント**] を選択し、統合の一部として含める必要があります。
 {% endalert %}
 
 ### ステップ3:サブスクライバーの収集(オプション)
@@ -75,19 +75,19 @@ Shopifyインテグレーションを使用すると、Shopifyストアからメ
 
 ![]({% image_buster /assets/img/Shopify/shopify_step_3_email.png %}){: style="max-width:70%"}
 
-### ステップ 4:Shopifyプロダクトシンクの設定(オプション)
+### ステップ 4:Shopify 製品の同期を設定する (オプション)
 
-オプションで、ShopifyストアからBraze カタログに製品をほぼリアルタイムで同期することができます。これにより、メッセージをより深くパーソナライゼーションできるように製品データを取り込むプロセスが自動化されます。詳しくは、[Shopify product syncs]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs/) を参照してください。
+必要に応じて、Shopify ストアから Braze カタログに製品をほぼリアルタイムで同期できます。これにより、メッセージのより細かなパーソナライゼーションのために製品データを取り込むプロセスが自動化されます。詳しくは、[Shopify product syncs]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs/) を参照してください。
 
 ![]({% image_buster /assets/img/Shopify/shopify_step_4_catalog.png %}){: style="max-width:70%"}
 
 ### ステップ 5: ブラウザ内メッセージングを有効にする 
 
-オプションで、この機能を有効にすることで、Shopifyストアの追加チャネルをブラウザー内で使用することができます。これにより、スライドアップ、モーダル、フルスクリーン、シンプルなアンケート、カスタムHTMLなどの基本的なメッセージタイプを使用できます。
+必要に応じて、この機能を有効にすることで、Shopify ストアの追加チャネルをブラウザー内メッセージで使用することができます。これにより、スライドアップ、モーダル、フルスクリーン、シンプルなアンケート、カスタムHTMLなどの基本的なメッセージタイプを使用できます。
 
 ![]({% image_buster /assets/img/Shopify/shopify_step_5_channels.png %}){: style="max-width:70%"}
 
-ブラウザ内メッセージを有効にする場合は、Braze Web SDKを"トラッキング用に実装する必要があります。[ Shopify ScriptTag]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=shopify%20scripttag#supported-features) またはShopifyのサイト[`theme.liquid`]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=theme.liquid#supported-features) のいずれかでBraze Web SDKを実装すると、Braze は基本的なブラウザ内メッセージ実装スクリプトを自動的にサイトに生成します。[ヘッドレスShopifyサイト]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#implement-web-sdk)にWeb SDKを実装する場合、またはブラウザ内メッセージにカスタマイズを追加する場合は、[開発者ガイド](/developer_guide/platform_integration_guides/web/in-app_messaging/integration/)を使用して、手動でブラウザ内メッセージをサイトに追加する必要があります。 
+ブラウザー内メッセージを有効にする場合は、トラッキングのために Braze Web SDKを実装する必要があります。[Shopify ScriptTag]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=shopify%20scripttag#supported-features) を使用して Braze Web SDK を実装するか、または Shopify サイト [`theme.liquid`]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=theme.liquid#supported-features)に直接実装すると、Braze により基本的なブラウザー内メッセージ実装スクリプトが自動的に生成され、サイトに読み込まれます。[ヘッドレスShopifyサイト]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#implement-web-sdk)にWeb SDKを実装する場合、またはブラウザ内メッセージにカスタマイズを追加する場合は、[開発者ガイド](/developer_guide/platform_integration_guides/web/in-app_messaging/integration/)を使用して、手動でブラウザ内メッセージをサイトに追加する必要があります。 
 
 ### ステップ 6: 設定完了
 
@@ -95,23 +95,23 @@ Shopifyインテグレーションを使用すると、Shopifyストアからメ
 
 ![]({% image_buster /assets/img/Shopify/finish_setup.png %}){: style="max-width:70%"}
 
-そうです!「Connection Pending」ステータスが「Connected」に更新され、接続が確立されたときのタイムスタンプが表示されます。また、それぞれのShopify機能が正常に有効になっているかどうかも確認します。 
+以上で操作完了です。\[接続保留中] ステータスが \[接続済み] に更新され、接続が確立された日時のタイムスタンプが表示されます。また、それぞれのShopify機能が正常に有効になっているかどうかも確認します。 
 
 ![]({% image_buster /assets/img/Shopify/shopify_connected_store.png %}){: style="max-width:70%"}
 
-### 詳細設定(オプション) 
+### 高度な設定 (オプション) 
 
 #### 放棄カート or カート放棄のアップデートとチェックアウトの遅延
 
-デフォルトでは、Braze は`shopify_abandoned_checkout` および`shopify_abandoned_cart` イベントを1 時間非アクティブにトリガーする遅延を自動的に設定します。Shopifyパートナページでドロップダウンを選択し、**Abandoned Cart Delay**と**Abandoned Checkout Delay**を5分～24時間の範囲で設定できます。
+デフォルトでは、Braze は `shopify_abandoned_checkout` および`shopify_abandoned_cart` イベントのトリガーの遅延時間を、(何も操作が行われなかった) 1時間に自動的に設定します。\[**カート放棄の遅延**] と \[**チェックアウト放棄遅延**] は、イベントごとに5分から最大24時間までの範囲で設定できます。設定するには、Shopify パートナーページでドロップダウンから時間を選択してから、\[**遅延を設定**] を選択します。
 
 ![]({% image_buster /assets/img/Shopify/shop_setup_advanced_abandonment.png %}){: style="max-width:30%"}
 
 #### 希望のプロダクト識別子を設定する
 
-Brazeの購入イベントをShopifyインテグレーション設定に含めた場合、Brazeは、ShopifyのProduct IDをBrazeの購入イベント内で使用する`product_id`としてデフォルトで設定します。これは、Y日間に購入した商品をフィルターする場合や、リキッドを使用してメールの内容をカスタマイズする場合に使用されます。
+Braze 購入イベントを Shopify 統合設定に含めた場合、Braze では、Shopify 製品 ID が、Braze 購入イベント内で使用する `product_id` としてデフォルトで設定されます。これは、Y 日間内に購入した製品をフィルタリングする場合や、Liquid を使用してメッセージのコンテンツをパーソナライズする場合に使用されます。
 
-ShopifyのプロダクトIDの代わりに、SKUまたはプロダクトタイトルをShopifyから設定することもできます。
+Shopify 製品 ID の代わりに、SKU または製品タイトルを Shopify から設定することもできます。
 
 ![]({% image_buster /assets/img/Shopify/shop_setup_advanced_productid.png %}){: style="max-width:30%"}
 
@@ -123,41 +123,41 @@ ShopifyのプロダクトIDの代わりに、SKUまたはプロダクトタイ
  - BrazeがShopifyと通信しているとき
 
 
-アプリ のインストールが1 時間保留中の場合、Braze はインストールに失敗し、セットアップを再試行するように求められます。<br><br>
+アプリのインストールが1時間にわたり保留されている場合、Braze はインストールに失敗し、設定を再試行するように求められます。<br><br>
 ![Shopify]({% image_buster /assets/img/Shopify/shopify_integration8.png %}){: style="max-width:70%;"}
 {% enddetails %}
 
 
 {% details Shopify アプリのインストールが失敗した理由 %}
 次のいずれかの理由で、インストールが失敗した可能性があります。
- - BrazeがShopifyに到達できなかった
+ - Braze が Shopify にアクセスできなかった
  - Brazeがリクエストの処理に失敗しました
  - Shopify接続トークンが不正です
  - Braze Shopify アプリがShopifyの管理ページから削除された
 
 
-この h アプリが表示された場合は、**Retry Setup**を選択し、インストール処理を再開することができます。<br><br>
+その場合は、\[**設定を再試行**] を選択して、インストールプロセスをやり直すことができます。<br><br>
 ![Shopify]({% image_buster /assets/img/Shopify/shopify_integration16.png %}){: style="max-width:70%;"}
 {% enddetails %}
 
 
-{% details ShopifyストアからBraze アプリライセンスをアンインストールするにはどうすればよいですか? %}
+{% details Shopify ストアから Braze アプリライセンスをアンインストールするにはどうすればよいですか? %}
 
 ShopifyストアからBrazeをアンインストールするには、次の2 つの方法があります。
 
-1. Shopifyパートナページで、**Disconnect**を選択します。<br><br> !["Disconnect Integration" セクション。disconnect.] ({% image_buster /assets/img/Shopify/disconnect_integration.png %}) へのリンクがあります。{: style="max-width:70%;"}
+1. Shopifyパートナページで、**Disconnect**を選択します。<br><br> ![接続解除のリンクが表示されている「統合の接続を解除」セクション。]({% image_buster /assets/img/Shopify/disconnect_integration.png %}){: style="max-width:70%;"}
 
-2. **Apps**にあるShopifyの管理者ページに移動します。その後、Braze アプリのライケーションを削除することができます。<br><br> ![Braze アプリ.]({% image_buster /assets/img/Shopify/shopify_integration12.png %})を削除するかどうかを確認するモーダル{: style="max-width:70%;"}
+2. **Apps**にあるShopifyの管理者ページに移動します。その後、Braze アプリケーションを削除するオプションが表示されます。<br><br> ![Braze アプリの削除操作の確認を求めるモーダル。]({% image_buster /assets/img/Shopify/shopify_integration12.png %}){: style="max-width:70%;"}
 {% enddetails %}
 
-{% details 私はユーザーの和解に苦労している。その理由は何でしょうか。 %}
+{% details ユーザー照合がうまくできません。その理由は何でしょうか? %}
 
-ユーザー調整に必要な支援の種類は、Web SDKの実装方法によって決まります。詳細については、[Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/)の使用開始を参照してください。 
+ユーザー照合に必要なサポートの種類は、Web SDK の実装方法によって異なります。詳細については、[Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/)の使用開始を参照してください。 
 
-- Shopifyのヘッドレスサイトにいる場合は、[ヘッドレス実装]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=headless%20shopify%20site#supported-features)をチェックして、チェックアウトユーザーの調整が有効になっていることを確認します。
-- 同じメールまたは電話番号の重複するユーザープロファイルs が発生した場合は、次のBrazeを使用して、重複を1 つのプロファイルにマージできます。 
+- Shopify ヘッドレスサイトでは、[ヘッドレス実装]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=headless%20shopify%20site#supported-features)をチェックして、チェックアウトユーザーの照合が有効になっていることを確認します。
+- 同じメールや電話番号のユーザープロファイルが重複している場合、以下の Braze ツールを使用して、重複するプロファイルを1つのプロファイルに統合できます。 
     - [`users/merge`]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/) エンドポイント
     - [一括マージ]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users#bulk-merging)
-- スクリプトタグインテグレーションを使用し、Shopifyストアで"Buy Now"カートをスキップするオプションが提供されている場合、Shopify でスクリプトタグs が`device_id` を取得してカートをスキップするユーザーにイベントをマップできないため、Braze はユーザーs の調整に苦労する可能性があります。
+- ScriptTag 統合を使用しており、Shopify ストアでカートをスキップする 「Buy Now」オプションが提供されている場合、Shopify ではカートをスキップしたユーザーにイベントをマッピングするための `device_id` をスクリプトタグが取得できないため、Braze ではユーザーの照合が難しいことがあります。
 
 {% enddetails %}
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_backfill.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_backfill.md
index a377f7a1339..a6e247d12fd 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_backfill.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_backfill.md
@@ -1,6 +1,6 @@
 ---
-nav_title: "Shopifyヒストリカル・バックフィル"
-article_title: "Shopifyヒストリカル・バックフィル"
+nav_title: "Shopify 履歴バックフィル"
+article_title: "Shopify 履歴バックフィル"
 alias: "/shopify_historical_backfill/"
 description: "この参考記事では、Shopifyのヒストリカル・バックフィルを設定する方法について、リスクやサポートされるデータを含めて概説している。"
 page_type: partner
@@ -8,86 +8,86 @@ search_tag: Partner
 page_order: 1
 ---
 
-# Shopifyヒストリカル・バックフィル 
+# Shopify 履歴バックフィル 
 
-> Shopifyのヒストリカル・バックフィル機能により、ブランドは自動化されたシームレスな方法で顧客と購買データを同期することができる。 
+> Shopify の履歴バックフィル機能により、ブランドは自動化されたシームレスな方法で顧客と購入データを同期できます。このため、最も価値が高いセグメントの1つである購入者にすぐに働きかけることができます。 
 
-この埋め戻しの一環として、Brazeは、Shopify統合接続前の過去90日間のすべての顧客、注文、購入イベントをインポートする。この機能は、次のセクションで説明する意味を考えると、アクティブなメッセージを走らせていない新しい顧客にとって理想的であることに注意してほしい。この機能もデータポイントの使用量にカウントされる。
+この埋め戻しの一環として、Brazeは、Shopify統合接続前の過去90日間のすべての顧客、注文、購入イベントをインポートする。この機能は、次のセクションで説明する内容を踏まえたると、アクティブなメッセージが実行されていない新しい顧客にとって理想的です。この機能もデータポイントの使用量にカウントされる。
 
 ## リスク
 
-この機能は、過去のデータとイベントをインポートし、影響を受けたキャンペーンやキャンバスに対して、ユーザーが無関係なメッセージを受け取ったり、不適切なメッセージを受け取ったりするような、意図しない結果を招く可能性がある。以下のトリガーイベントを使用しているキャンペーンとキャンバスは、この機能が同期しているShopifyのデータを使用している場合、影響を受ける可能性がある：
+この機能は、意図しない結果を引き起こした可能性があるイベントと履歴データをインポートします。このような意図しない結果には、影響を受けたキャンペーンやキャンバスに関して無関係でタイミングが適切ではないメッセージをユーザーが受信したことなどがあります。以下のトリガーイベントを使用しているキャンペーンとキャンバスは、この機能が同期しているShopifyのデータを使用している場合、影響を受ける可能性がある：
 - カスタム属性の値を変更する
 - 変換イベントを実行する
 - キャンペーンの例外イベントを実行する
-- 購読ステータスを更新する
+- サブスクリプションのステータスを更新
 - サブスクリプション・グループのステータスを更新する
 - メールアドレスを追加する
-- 購入する
+- 購入*
 - カスタムイベント\*を実行する
 
 {% alert important %}
 Shopifyのヒストリカル・バックフィルのデータを使って、現在アクティブなキャンペーンとキャンバスに、上記のイベントを引き起こす可能性のあるメッセージがないか監査することをお勧めする。 
 
-- Make Purchase "と "Perform Custom Event "については、ShopifyストアがBrazeに接続された後、[開始時間の期間を]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery/?redirected=true#step-4-assign-duration)任意の日時に更新することができる。この新しい開始時刻以前の過去のイベントは、いかなるメッセージもトリガーされない。 
+- 「購入」と「カスタムイベントを実行」の場合、[期間の開始時刻]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery/?redirected=true#step-4-assign-duration)を、Braze で Shopify ストアが接続された後の任意の日時に更新できます。この新しい開始時刻より前に発生した過去のイベントは、メッセージをトリガーしません。 
 - 上記以外のイベントについては、バックフィルを有効にする前に[一時的に停止させる]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/change_your_campaign_after_launch/#stopping-your-campaign)ことで、メッセージが送信されないことを保証することができる。
 {% endalert %}
 
-## Shopifyヒストリカル・バックフィルを設定する
+## Shopify 履歴バックフィルの設定
 
 ### 前提条件
 
-バックフィルをオンにする前に、以下のイベントを有効にしておく必要がある：
+次のイベントは、バックフィルをオンにする前に有効にしておく必要があります。有効にしないと、データはインポートされません。
 
 - `shopify_created_order`
-- ブレイズ購入イベント 
+- Braze 購入イベント 
 
 上記のイベントは、Shopifyのセットアップ中に、[イベント選択]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/#event-selection)時に有効にすることができる。
 
 {% alert important %}
-バックフィル機能を有効にできるのは、統合の中で一度だけである。
+バックフィル機能は、統合で一度だけアクティブにできます。
 {% endalert %}
 
-### ステップ1:Shopifyのバックフィル・プロセスを開始する
+### ステップ1:Shopify バックフィルプロセスを開始する
 
-Shopifyのパートナーページで、**Start Data Backfillを**選択する。Shopifyの既存顧客については、データの埋め戻しを開始する前に、Brazeが過去の注文イベントをすべて収集できるよう、アクセスを再承認する必要がある。
+Shopifyパートナーページで \[**データバックフィルの開始**] を選択します。既存の Shopify 顧客の場合、データのバックフィルを開始する前に、Braze が過去のすべての注文イベントを収集できるようにアクセスを再認証する必要があります。
 
 ![][3]{: style="max-width:75%;"}
 
 ### ステップ2:Shopifyデータの埋め戻しをトグルする
 
-次に、セットアップ・コンポーザーがポップアップし、オプションで過去のShopifyデータのバックフィルを有効にすることができる。この埋め戻しの一環として、BrazeはデフォルトでShopify統合前の過去90日間の以下のShopifyデータのみを同期する：
-- オーダー作成イベント
-- ブレイズ購入イベント
+次に、設定コンポーザーがポップアップ表示され、Shopify 履歴データのバックフィルを有効にすることができます。この埋め戻しの一環として、BrazeはデフォルトでShopify統合前の過去90日間の以下のShopifyデータのみを同期する：
+- 注文作成イベント
+- Braze 購入イベント
 - 顧客データ
 
 具体的にどのような顧客データが埋め戻されているかを見るには、[サポートされているShopifyの顧客データ](#supported-shopify-customer-data)セクションを見ることができる。
 
 {% alert note %}
-この機能は、バックフィル中に作成された新規ユーザーのEメールとSMSの購読状態のみを同期する。これは、ユーザーの現在のステータスを上書きしないように、Brazeの既存ユーザーの購読ステータスを同期しない。<br><br>現在の動作に関するフィードバックがある場合は、**ダッシュボードの**「**リソース**」にある「**製品ロードマップ」**（[更新されたナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、**「コミュニティ**」>「**製品ロードマップ**」を選択）に記載されている製品ポータルから提出する。
+この機能は、バックフィル中に作成された新規ユーザーのメールおよび SMS サブスクリプションの状態のみを同期します。ユーザーの現在のステータスをオーバーライドしないようにするため、Braze の既存のユーザーのサブスクリプション状態は同期されません。<br><br>現行の動作に関するフィードバックがある場合は、製品ポータルから送信してください。これは \[**ダッシュボード**] の \[**リソース**] に \[**製品ロードマップ**] とリストされています ([新しくなったナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**コミュニティ**] > \[**製品ロードマップ**] を選択してください)。
 {% endalert %}
 
-**次へ」を**クリックすると、バックフィルが有効になり、過去のデータの同期が開始される。ヒストリカル・バックフィルは**一度しか**完了できないので、データの同期が完了した後、このインポートを再度実行することはできない。
+\[**次へ**] をクリックすると、バックフィルがアクティブになり、過去のデータの同期が開始されます。履歴バックフィルは**一度**だけ実行できます。このため、データの同期終了後にこのインポートをもう一度実行することはできません。
 
 ![][1]{: style="max-width:75%;"}
 
 ### ステップ3:埋め戻し作業中
 
-ダッシュボードに通知が届き、ステータスが「進行中」と表示され、埋め戻しが開始されたことがわかる。バックフィルが完了するまでにかかる時間は、BrazeがShopifyから同期する必要がある顧客や注文の数によって異なることに注意してほしい。この間は、このページから離れ、埋め戻しが完了したことを知らせるダッシュボードの通知やEメールを待つことができる。
+ダッシュボード通知を受け取り、ステータスが \[進行中] と表示されたら、バックフィルが開始しています。バックフィルが完了するまでにかかる時間は、BrazeがShopifyから同期する必要がある顧客や注文の数によって異なることに注意してほしい。この間、このページから離れて、バックフィル完了を通知するダッシュボード通知またはメールが届くまで待つことができます。
 
 ![][2]{: style="max-width:75%;"}
 
 ### ステップ4:埋め戻しが完了した
-Shopifyのバックフィルが完了すると、ダッシュボード通知とメールが届く。また、Shopifyのパートナーページでは、ヒストリカル・バックフィルのステータスが "Complete "に更新される。
+Shopify のバックフィルが完了すると、ダッシュボード通知とメールを受け取ります。Shopify パートナーページで \[履歴バックフィル] の下のステータスが \[完了] に更新されます。
 
-## Shopifyの顧客データをサポート
+## サポートされている Shopify 顧客データ
 
 ### Shopifyカスタム属性
 
 | 属性名 | 説明 |
 | --- | --- |
-| `shopify_order_count` | このカスタム属性は、この顧客がShopifyで完了した注文の合計に対応する。これは、このプロセスの一環としてバックフィルされたユーザーに対してのみ有効である。 |
-| `shopify_total_spent` | このカスタム属性は、この顧客がShopifyで使用した合計金額に対応する。これは、このプロセスの一環としてバックフィルされたユーザーに対してのみ有効である。 |
+| `shopify_order_count` | このカスタム属性は、この顧客がShopifyで完了した注文の合計に対応する。これは、このプロセスの一部としてバックフィルされたユーザーの場合にのみ使用できます。 |
+| `shopify_total_spent` | このカスタム属性は、この顧客が Shopify で支払った総額に対応します。これは、このプロセスの一部としてバックフィルされたユーザーの場合にのみ使用できます。 |
 | `shopify_tags` | この属性は、Shopifyの管理者が設定した[顧客タグに](https://help.shopify.com/en/manual/shopify-admin/productivity-tools/using-tags#tag-types)対応する。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 }
 
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs.md
index 1009a5ffc2a..6b73e141a1b 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs.md
@@ -1,18 +1,18 @@
 ---
-nav_title: Shopifyプロダクトシンク
-article_title: Shopifyプロダクトシンク
+nav_title: Shopify 製品の同期
+article_title: Shopify 製品の同期
 alias: /shopify_catalogs/
 page_order: 2
-description: "このリファレンス記事では、Shopify からBraze カタログ s に商品をインポートする方法について説明します。"
+description: "このリファレンス記事では、Shopify から Braze カタログに製品をインポートする方法について説明します。"
 ---
 
-# Shopifyプロダクトシンク 
+# Shopify 製品の同期 
 
-> Shopify ストアからBraze [カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs) に製品を同期することで、より深いパーソナライゼーションのために製品データを取り込む方法を自動化できます。 
+> Shopify ストアの製品を Braze [カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs)に同期し、製品データの取り込み方法を自動化して、メッセージのパーソナライゼーションを強化できます。 
 
-Shopify カタログ s は、Shopifyストア内のプロダクトを編集および変更すると、ほぼリアルタイムで更新します。最新の商品詳細とインフォメーションで、放棄カート or カート放棄、オーダーコンファメーションなどを充実させることができます。
+Shopify ストア内の製品に編集や変更を加えると、Shopify カタログがほぼリアルタイムで更新されます。最新の製品詳細や情報を使用して、カート放棄や注文確認などを強化できます。
 
-## Shopifyプロダクトシンクのセットアップ {#setting-up}
+## Shopify 製品の同期を設定する {#setting-up}
 
 Shopifyストアがすでにインストールされている場合でも、以下の手順に従って商品を同期できます。 
 
@@ -20,9 +20,9 @@ Shopifyストアがすでにインストールされている場合でも、以
 
 ShopifyのインストールフローまたはShopifyパートナページで、製品をBraze カタログに同期できます。 
 
-![" Shopify Variant ID" as " as the " Catalog product 識別子" で設定された処理の手順3。][1]{: style="max-width:70%;"}
+![設定プロセスのステップ3。「カタログの製品の識別子」に「Shopify バリアント ID」が設定されている。][1]{: style="max-width:70%;"}
 
-Braze カタログに同期されたプロダクトは、[ カタログ制限]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/#limits) に影響します。
+Braze カタログに同期された製品は、[カタログ制限]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/#limits)の対象になります。
 
 ### ステップ2:プロダクト識別子の選択
 
@@ -30,29 +30,29 @@ Braze カタログに同期されたプロダクトは、[ カタログ制限]({
 - ShopifyバリアントID
 - SKU
 
-選択するプロダクト識別子のID とヘッダーは、文字、数字、ハイフン、アンダースコアのみを含めることができます。プロダクト識別子がこの形式に従わない場合、Braze はカタログの同期からフィルターされます。
+選択するプロダクト識別子の ID とヘッダーの値には、文字、数字、ハイフン、アンダースコアのみを使用できます。プロダクト識別子がこの形式に従っていない場合、Braze はカタログの同期からその識別子を除外します。
 
-これは、Braze カタログのリファレンスに使用する主な識別子です。 
+これは、Braze カタログ情報を参照するときに使用する主要な識別子です。 
 
 {% alert note %}
 カタログ ID としてSKU を選択する場合は、ストア内のすべての製品とバリアントにSKU が設定されており、それらが一意であることを確認してください。 
-- アイテムにSKU がない場合、Braze はそのアイテムをカタログに同期できません。 
+- アイテムに SKU が設定されていない場合、Braze はその製品をカタログに同期できません。 
 - 同じSKU を持つ複数の製品がある場合、予期しない動作が発生したり、重複したSKU によって意図せずに製品情報が上書きされる可能性があります。
 {% endalert %}
 
 ### ステップ3:同期中
 
-ダッシュボード 通知が表示され、ステータスに「実行中」と表示され、最初の同期が開始されていることを示します。シンクが完了するまでの時間は、プロダクト数とバリアントのBrazeがShopifyからシンクオーバーする必要があるかによって異なります。この間、このページから離れて、ダッシュボード 通知またはメールが完了したときに通知するまで待機できます。
+ダッシュボード 通知が表示され、ステータスに「実行中」と表示され、最初の同期が開始されていることを示します。同期の完了にかかる時間は、Braze が Shopify から同期する必要がある製品やバリアントの数によって異なることに注意してください。この間、このページから離れて、同期完了を通知するダッシュボード通知またはメールが届くまで待つことができます。
 
-最初の同期が[カタログ制限]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/#limits)を超えた場合、Brazeはこれ以上のプロダクトの同期を中止します。時間の経過とともに新しい製品が追加されたために同期が成功した後に制限を超えた場合、同期はアクティブではなくなります。いずれの場合も、Shopifyからの商品更新はBrazeに反映されなくなります。アカウントマネージャーに連絡して、階層のアップグレードを検討してください。 
+最初の同期が[カタログ制限]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/#limits)を超えた場合、Brazeはこれ以上のプロダクトの同期を中止します。時間の経過とともに新しい製品が追加されたために同期が成功した後に制限を超えた場合、同期はアクティブではなくなります。いずれの場合も、Shopifyからの商品更新はBrazeに反映されなくなります。ティアのアップグレードを検討する場合はアカウントマネージャーにご連絡ください。 
 
 ### ステップ4:同期完了
 
-同期が成功すると、ダッシュボード 通知とメールが表示されます。Shopifyパートナページでは、Shopify カタログ s の「同期とクォート;」にステータスも更新されます。Shopifyパートナページでカタログの名前をクリックすると、商品を表示できます。
+同期が成功するとダッシュボード通知とメールが届きます。Shopify パートナーページでも、Shopify カタログの下のステータスが \[Syncing] に更新されます。Shopify パートナページでカタログの名前をクリックすると、製品を表示できます。
 
 カタログデータを利用してメッセージをパーソナライズする方法の詳細については、[カタログの追加ユースケースs]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/#additional-use-cases)を参照してください。
 
-#### 対応Shopify カタログ
+#### サポートされている Shopify カタログデータ
 
 {% alert note %}
 `product_handle` および`product_url` にアクセスして使用するには、Shopify カタログを切断してから再接続します。
@@ -81,12 +81,12 @@ Braze カタログに同期されたプロダクトは、[ カタログ制限]({
 - `sku`
 
 {% alert warning %}
-Shopify カタログを任意の方法で変更すると、意図せずにリアルタイムのプロダクト同期に干渉する可能性があります。Shopify カタログは、Shopifyによって上書きされる可能性があるため、編集しないでください。代わりに、Shopifyで必要なプロダクト更新を作成します。<br><br>Shopify カタログを削除するには、「Shopify」を選択し、「シンク」をオフにします。カタログ s ページのShopify カタログをそのまま消去しないでください。
+Shopify カタログを任意の方法で変更すると、意図せずにリアルタイムのプロダクト同期に干渉する可能性があります。Shopify カタログは、Shopifyによって上書きされる可能性があるため、編集しないでください。代わりに、Shopify インスタンスで必要な製品更新を行います。<br><br>Shopify カタログを削除するには、Shopify ページに移動し、同期を非アクティブにします。カタログページで Shopify カタログを直接削除しないでください。
 {% endalert %}
 
-## バック・イン・ストック、株価下落ユースケース 
+## 再入荷と値下げのユースケース 
 
-バックアップインストック通知s を設定するには、ステップs [ここで]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications#back-in-stock-notifications) を実行します。
+再入荷通知を設定するには、[こちら]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications#back-in-stock-notifications)の手順に従ってください。
 
 価格低下通知s を設定するには、ステップs [ここで]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/price_drop_notifications) を実行します。
 
@@ -95,20 +95,20 @@ Shopifyインテグレーションでは、ユースケースごとにユーザ
 
 ## カタログ番号を変更する
 
-Shopify カタログのプロダクト識別子を変更するには、シンクを無効にする必要があります。まず、このShopify カタログデーターを使用して送信を停止したことを確認します。Shopify カタログのイニシャルシンクを再実行し、[product sync](#setting-up) ステップ s に従って目的のプロダクト識別子を選択します。
+Shopify カタログのプロダクト識別子を変更するには、シンクを無効にする必要があります。まず、この Shopify カタログデータを使用するすべての送信を停止したことを確認します。Shopify カタログの初回同期を再実行し、[製品の同期](#setting-up)の手順に従って目的の製品識別子を選択します。
 
-## 製品の同期を無効にする {#deactivate}
+## 製品の同期の非アクティブ化 {#deactivate}
 
-Shopifyプロダクトシンク機能を無効にすると、カタログとプロダクト全体が削除されます。これは、このカタログからのプロダクトデータをアクティブに使用している可能性がある送信にも影響します。更新 d または一時停止した送信が無効になっていることを確認します。これにより、メッセージングが欠落した商品情報を送信する可能性があります。カタログ s ページのShopify カタログをそのまま消去しないでください。
+Shopify 製品の同期機能を非アクティブにすると、カタログと製品がすべて削除されます。この操作は、このカタログの製品データをアクティブに使用している可能性があるすべての送信に影響する可能性もあります。非アクティブ化する前に、これらの送信を更新または一時停止していることを確認してください。非アクティブ化により、製品の詳細がメッセージ送信に含まれなくなる可能性があります。カタログページで Shopify カタログを直接削除しないでください。
 
 ## トラブルシューティング
-Shopifyプロダクトの同期がエラーに実行される場合、次のエラーが原因である可能性があります。問題を修正し、同期を解決する方法については、次の手順に従ってください。
+Shopify 製品の同期でエラーが発生した場合は、次のいずれかのエラーが原因である可能性があります。問題を修正し、同期を解決する方法については、次の手順に従ってください。
 
 | エラー | 理由 | ソリューション |
 | --- | --- | --- |
-| サーバーエラー | これは、プロダクトを同期しようとしたときに、Shopify側にサーバーエラーがある場合に発生します。 | [sync](#deactivate)を無効にし、製品のインベントリ全体を再同期します。 |
-| 重複SKU | これは、カタログアイテムID としてSKU を使用し、同じSKU の製品がある場合に発生します。カタログアイテムID は一意である必要があるため、すべての製品に一意のSKU が必要です。 | Shopify で製品とバリアントの一覧をすべて監査して、重複するSKU がないことを確認します。SKU が重複している場合は、Shopifyストアアカウントでのみ一意のSKU になるように更新します。これが修正された後、[sync](#deactivate) を非アクティブ化し、製品のインベントリ全体を再同期します。 |
-| カタログ制限を超過 | これは、カタログ制限を超えた場合に発生します。Brazeは、ストレージの可用性がなくなるため、同期を終了したり、同期を有効にしておくことができません。 | この問題には2 つのソリューションがあります。<br><br>1\.カタログの制限を増やすために、アカウントマネージャーにリーチして階層をアップグレードします。<br><br>2\.次のいずれかを削除して、ストレージ領域を解放します。<br>\- 他のカタログsからのカタログアイテム<br>\- 他のカタログ<br>\- 作成された選択<br><br> いずれかのソリューションs を使用した後、同期を無効にしてから再同期する必要があります。 |
+| サーバーエラー | これは、プロダクトを同期しようとしたときに、Shopify側にサーバーエラーがある場合に発生します。 | [同期を非アクティブにし](#deactivate)、製品の在庫全体を再同期します。 |
+| 重複する SKU | これは、カタログアイテム ID としてSKU を使用している場合に、複数の製品に同じ SKU が設定されていると発生します。カタログアイテム ID は一意でなければならないため、すべての製品に一意の SKU が必要です。 | Shopify で製品とバリアントの一覧をすべて監査して、重複するSKU がないことを確認します。SKU が重複している場合は、Shopifyストアアカウントでのみ一意のSKU になるように更新します。これが修正された後、[sync](#deactivate) を非アクティブ化し、製品のインベントリ全体を再同期します。 |
+| カタログ制限の超過 | これは、カタログ制限を超えた場合に発生します。Braze は、利用可能なストレージがないために、同期を終了することや、同期をアクティブな状態で維持することができなくなります。 | この問題には2 つのソリューションがあります。<br><br>1\.アカウントマネージャーに連絡して、ティアをアップグレードしてカタログ制限を引き上げます。<br><br>2\.次のいずれかを削除して、ストレージ領域を解放します。<br>\- 他のカタログsからのカタログアイテム<br>\- 他のカタログ<br>\- 作成されたセレクション<br><br> いずれの解決策を取った場合でも、同期を非アクティブにしてから再同期を実行する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 [1]: {% image_buster /assets/img/Shopify/sync_products_step1.png %}
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_user_identity.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_user_identity.md
index 7c194035113..6e25c0cda4b 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_user_identity.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_user_identity.md
@@ -1,6 +1,6 @@
 ---
-nav_title: Shopify ユーザアイデンティティマネジメント
-article_title: "Shopify ユーザアイデンティティマネジメント"
+nav_title: Shopify ユーザーアイデンティティ管理
+article_title: "Shopify ユーザーアイデンティティ管理"
 description: "このリファレンス記事では、Shopify ユーザー アイデンティティマネジメント機能の概要について説明します。"
 page_type: partner
 search_tag: Partner
@@ -10,32 +10,32 @@ page_order: 3
 
 # Shopify ユーザー識別マネジメント
 
-> Braze は、オンサイトの動作やインテグレーションの一部として設定したShopify webhookを聴くことで、Shopify 顧客 s からシグナルを受信します。ヘッドレスでないShopifyサイトの場合、Brazeはチェックアウトページからユーザーを調整するのを支援します。ヘッドレスShopify拠点については、[チェックアウト]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#headless-checkout)からユーザーを調整する方法に関する当社の統合ガイダンスを参照してください。
+> Braze は、Shopify の顧客からのシグナルを受信します。これは、顧客のオンサイトでの行動から受信するか、または統合の一部として設定した Shopify Webhook をリッスンすることで受信します。ヘッドレスではない Shopify サイトの場合、Braze はチェックアウトページからのユーザー照合を支援します。ヘッドレス Shopify サイトについては、[チェックアウトからユーザーを照合する]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#headless-checkout)方法に関する当社の統合ガイダンスを参照してください。
 
 ## ユーザープロファイルのキャプチャ 
 
-### Shopify ユーザー "トラッキング
+### Shopify ユーザー追跡
 
-ストア訪問者がゲスト(つまり匿名) の場合、Braze はこれらの特定の顧客のセッションs の`device_id` をキャプチャします。[Web SDKの実装中にShopifyフォームのユーザー調整を設定すると、顧客がフォームに入力するたびに、顧客 メールsが匿名ユーザープロファイルに追加されます。 
+ストア訪問者がゲスト(つまり匿名) の場合、Braze はこれらの特定の顧客のセッションs の`device_id` をキャプチャします。[Web SDK の実装]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#implement-web-sdk)時に Shopify フォームにユーザー照合を設定すると、顧客がフォームに情報を入力するたびに、顧客のメールが匿名ユーザープロファイルに追加されます。 
 
 店舗訪問者がメールをShopifyニュースレターやメールキャプチャーフォームに入力すると、BrazeはShopify Webhookを受け取り、ユーザープロファイルを作成します。Braze は、このユーザープロファイルをWeb SDKによって追跡される匿名ユーザープロファイルとマージし、ユーザープロファイルのユーザー別名としてShopify 顧客 ID を割り当てます。 
 
 顧客がチェックアウトに進み、電話番号などの他の識別可能な情報を提供するにつれて、BrazeはShopify webhookから関連するユーザーデータを取得し、`device_id`で匿名ユーザーとマージする必要があります。
 - Shopify ScriptTag、ヘッドレスでないShopify サイト、またはGoogle Tag Manager を使用してWeb SDKを実装した場合、Braze はチェックアウトページからのユーザーデータと匿名ユーザープロファイルからのセッションデータが、割り当てられたShopify 顧客 ID でユーザー別名プロファイルにマージされることを自動的に確認します。
-- Web SDKをShopifyヘッドレスサイトに実装した場合は、チェックアウトページ内で送信されたユーザーデータがアプリ適切に、Web SDKまたはAPIのいずれかを介して正しいユーザープロファイルに割り当てられていることを確認する必要があります。詳細については、[Web SDKをヘッドレスShopifyサイト]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#headless-site)に直接実装してください。
+- Shopify ヘッドレスサイトに Web SDK を実装している場合は、チェックアウトページ内で送信されたユーザーデータが、Web SDK または API のいずれかを介して適切なユーザープロファイルに適切に割り当てられていることを確認する必要があります。詳細については、[Web SDK をヘッドレス Shopify サイトに直接実装する]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#headless-site)を参照してください。
 
-顧客がチェックアウト処理を続行すると、Brazeは、入力されたメール住所、電話番号、またはShopify 顧客 IDが存在するユーザープロファイルと一致するかどうかを確認します。一致がある場合、Braze はShopify ユーザーデータをそのプロファイルに同期します。
+顧客がチェックアウトプロセスを続行すると、Braze は、顧客が入力したメールアドレス、電話番号、または Shopify 顧客 IDが、存在するユーザープロファイルと一致するかどうかを確認します。一致がある場合、Braze はShopify ユーザーデータをそのプロファイルに同期します。
 
 メールの住所または電話番号が複数の識別されたユーザープロファイルs に関連付けられている場合、Braze はShopifyデータを最新のアクティビティを持つプロファイルに同期します。
 
 Brazeがメールの住所または電話番号と一致するものを見つけられない場合、サポートされているShopify情報を使用して新しいユーザープロファイルが作成されます。
 
-### Shopify 顧客 s がBraze と同期する場合
+### Shopify の顧客が Braze と同期される場合
 
-Shopifyストアでキャプチャされたリード、サインアップ、およびアカウント登録の既存のユーザープロファイルをBraze 更新するか、新しいものを作成します。Shopifyなどで、以下のメソッドからユーザープロファイルを収集できます。
+Braze は、Shopify ストアでキャプチャされたリード、サインアップ、およびアカウント登録の既存のユーザープロファイルを更新するか、または新しいユーザープロファイルを作成します。Shopify では次の方法でユーザープロファイルデータを収集できます。
 - 顧客がアカウントを作成する
 - お客様のメール住所または電話番号がShopifyキャプチャフォームで収集される
-- お客様メールの住所は、ニュースレターフォームから収集されます
+- 顧客のメールアドレスがニュースレターフォームから収集される
 - お客様のメール先や電話番号は、EcomSendなどのShopifyに接続されたサードパーティ製の機器で収集されます
 
 Brazeは、まず、顧客のメール住所または電話番号を使用して、サポートされているShopifyデータを既存のユーザープロファイルにマッピングしようとします。 
@@ -45,10 +45,10 @@ Brazeは、まず、顧客のメール住所または電話番号を使用して
 ## ユーザプロファイルのマージ 
 
 {% alert note %}
-デフォルト Shopifyインテグレーションは、匿名ユーザープロファイルとShopify別名プロファイルのマージを支援するツールを提供します。ヘッドレスShopifyサイトへの統合を実装する場合は、[ヘッドレスShopifyサイトにWeb SDKを直接的に実装して]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=headless%20shopify%20site#supported-features)を確認し、ユーザーが適切に調整されていることを確認します。<br><br> 重複するユーザープロファイルs が発生した場合は、[バルクマージツール]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users/#bulk-merging/) を使用して、データの効率化を支援できます。
+デフォルトの Shopify 統合では、匿名ユーザープロファイルと Shopify エイリアスプロファイルのマージを支援するツールが提供されます。ヘッドレス Shopify サイトにこの統合を実装する場合は、「[Web SDK をヘッドレス Shopify サイトに直接実装する]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/?tab=headless%20shopify%20site#supported-features)」を確認し、ユーザーが適切に照合されていることを確認します。<br><br> 重複するユーザープロファイルs が発生した場合は、[バルクマージツール]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users/#bulk-merging/) を使用して、データの効率化を支援できます。
 {% endalert %}
 
-Brazeは、次のいずれかと一致するものが見つかった場合に、匿名ユーザープロファイルのフィールドを識別されたユーザープロファイルにマージします。
+Braze は、次のいずれかの一致が見つかった場合に、匿名ユーザープロファイルのフィールドを、特定されたユーザープロファイルにマージします。
 - Shopify 顧客番号
 - メール
 - 電話番号
@@ -70,7 +70,7 @@ Braze は、匿名ユーザープロファイルの以下のフィールドを
 - プッシュトークン
 - メッセージ履歴
 - 匿名ユーザープロファイルまたは識別されたユーザープロファイルで検出された以下のフィールド(カスタムイベント、購入イベントカウント、最初の日付と最後の日付のタイムスタンプなど)
-    - これらのマージされたフィールドs は、「Y 日間のX イベント」フィルターs を更新します。購入イベントの場合、これらのフィルターには、「Y 日の購入数」と「Y 日の最後に消費した金額」が含まれます。
+    - マージされたフィールドにより、\[Y 日間の X 回のイベント] のフィルターが更新されます。購入イベントの場合、これらのフィルターには、「Y 日の購入数」と「Y 日の最後に消費した金額」が含まれます。
 
 {% alert important %}
 セッションデータは、マージプロセスの一部としてまだサポートされていません。
@@ -78,36 +78,36 @@ Braze は、匿名ユーザープロファイルの以下のフィールドを
 
 ## Shopify サブスクライバーの同期
 
-Shopify設定処理中、Braze は柔軟なコントロールを提供して、顧客 メールアドレスとSMS オプトイン状態をBraze ユーザープロファイルs のサブスクリプショングループs およびサブスクリプション 状態に同期します。 
+Shopify の設定プロセスでは、Braze は顧客のメールアドレスと SMS オプトイン状態を Braze ユーザープロファイルのサブスクリプショングループおよびサブスクリプション状態と同期するための柔軟なコントロールを提供します。 
 
-### メールやショートサブスクライバーを収集する
+### メールサブスクライバーまたは SMS サブスクライバーの収集
 
-Shopify ストアをBraze に設定する際に、Shopify からBraze にメールとSMS サブスクライバーを同期することができます。 
+Shopify ストアをBraze に設定する際に、Shopify からBraze にメールサブスクライバーと SMS サブスクライバーを同期することができます。 
 
-#### メール サブスクライバーの収集
+#### メールサブスクライバーを収集する
 
-メール サブスクライバー収集を有効にするには、Shopify設定で機能を有効にします。Shopify メール サブスクライバーs など、少なくとも1 つのBraze[サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions#subscription-groups) を割り当てることをお勧めします。Braze は、指定されたサブスクリプショングループs にメール サブスクライバーs を追加し、メッセージを送信するときにオーディエンスターゲットに含まれるようにします。 
+メールサブスクライバー収集を有効にするには、Shopify 設定内でこの機能を有効にします。Shopify メール サブスクライバーs など、少なくとも1 つのBraze[サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions#subscription-groups) を割り当てることをお勧めします。Braze は、メールサブスクライバーを指定のサブスクリプショングループに追加します。これにより、メッセージの送信時にメールサブスクライバーがオーディエンスターゲティングに含まれるようになります。 
 
 ![]({% image_buster /assets/img/Shopify/collect_email.png %})
 
-有効にすると、Braze は更新 s をShopify メール サブスクライバー s と更新 s をリアルタイムでメール サブスクリプションステートに同期します。上書きオプションを有効にしない場合、Shopify 顧客s はShopifyストアに関連付けられたサブスクリプショングループからサブスクライブまたは配信停止d のいずれかになります。
+有効にすると、Braze は Shopify メールサブスクライバーに対する更新と、メールサブスクリプションの状態に対する更新をリアルタイムで同期します。オーバーライドオプションを有効にしない場合、Shopify の顧客は、Shopify ストアに関連付けられているサブスクリプショングループにサブスクリプション登録されるか、またはサブスクリプショングループからサブスクリプション解除されます。
 
-上書きオプションを有効にすると、Braze はユーザープロファイルの大域サブスクリプションステートを更新します。つまり、顧客s が配信停止 d としてShopifyでマークされている場合、Braze は配信停止 d としてサブスクリプション ステートをユーザープロファイル上でマークし、使用可能なすべてのメール サブスクリプショングループs からユーザープロファイルします。そのため、メールからグローバル配信停止dのユーザーにはメッセージは送信されません。
+上書きオプションを有効にすると、Braze はユーザープロファイルの大域サブスクリプションステートを更新します。つまり、顧客が Shopify でサブスクリプション登録済みとしてマークされている場合、Braze はユーザープロファイルでグローバルサブスクリプション状態をサブスクリプション解除済みとしてマークし、利用可能なすべてのメールサブスクリプショングループから顧客をサブスクリプション解除します。そのため、メールからグローバルサブスクリプション解除されたユーザーにはメッセージは送信されません。
 
-#### SMSサブスクライバーを収集する
+#### SMS サブスクライバーを収集する
 
-Shopify から SMS サブスクライバー s を収集するには、[SMS サブスクリプショングループ s]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/) を [SMS セットアップ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup) の一部として作成する必要があります。 
+Shopify から SMS サブスクライバーを収集するには、[SMS 設定]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup)で [SMS サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/)を作成する必要があります。 
 
-ShopifyのSMS サブスクライバーを収集する準備ができたら、Shopify設定画面でSMS サブスクライバー収集を有効にします。適切にSMSをアプリして送信できるように、少なくとも1つのSMS サブスクリプショングループを選択する必要があります。 
+ShopifyのSMS サブスクライバーを収集する準備ができたら、Shopify設定画面でSMS サブスクライバー収集を有効にします。適切なターゲティングを行い SMS メッセージを送信できるようにするために、少なくとも1つの SMS サブスクリプショングループを選択する必要があります。 
 
 ![]({% image_buster /assets/img/Shopify/collect_sms.png %})
 
-有効にすると、Braze は更新をShopify SMS サブスクライバーとそのSMS サブスクリプションステートにリアルタイムで同期します。上書きオプションを有効にしない場合、Shopify 顧客s はShopifyストアに関連付けられたサブスクリプショングループからサブスクライブまたは配信停止d のいずれかになります。
+有効にすると、Braze は更新をShopify SMS サブスクライバーとそのSMS サブスクリプションステートにリアルタイムで同期します。オーバーライドオプションを有効にしない場合、Shopify の顧客は、Shopify ストアに関連付けられているサブスクリプショングループにサブスクリプション登録されるか、またはサブスクリプショングループからサブスクリプション解除されます。
 
-SMS サブスクライバーにはグローバルサブスクリプションステートがないため、オーバーライドオプションを使用するときに考慮する必要はありません。ユーザーは、配信停止dまたはSMS サブスクリプショングループへのサブスクライブのみが可能です。
+SMS サブスクライバーにはグローバルサブスクリプション状態がないため、オーバーライドオプションを使用するときにこれらの状態を考慮する必要はありません。SMS サブスクリプショングループに対するユーザーのサブスクリプション解除またはサブスクリプション登録のみが可能です。
 
 #### レガシーカスタム属性
 
-レガシーShopify 顧客s には、`shopify_accepts_marketing` および`shopify_sms_consent` カスタム属性s を介してメール およびSMS サブスクライバーs を収集する従来のメソッドがある場合があります。上の設定s を上書きを有効にして保存すると、Braze はユーザープロファイルs のカスタム属性s を削除し、それぞれのメール サブスクリプショングループとSMS サブスクリプショングループにこれらの値を同期します。
+Shopify を以前から利用している顧客は、カスタム属性 `shopify_accepts_marketing` と`shopify_sms_consent` を使用してメールサブスクライバーと SMS サブスクライバーを収集する従来の方法を使用している可能性があります。上の設定s を上書きを有効にして保存すると、Braze はユーザープロファイルs のカスタム属性s を削除し、それぞれのメール サブスクリプショングループとSMS サブスクリプショングループにこれらの値を同期します。
 
-既存のキャンペーン s またはキャンバスがこれらのレガシーカスタム属性s を使用している場合は、それらの属性s を削除し、キャンペーンs またはキャンバスがアプリの適切なサブスクリプションステート、グループ、またはその両方を使用していることを確認します。
+既存のキャンペーンまたはキャンバスでこれらのレガシーカスタム属性を使用している場合は、それらの属性を削除し、キャンペーンまたはキャンバスが適切なサブスクリプション状態またはサブスクリプショングループ、あるいはこの両方を使用していることを確認します。
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_overview.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_overview.md
index 32511e2e949..5da7f796abb 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_overview.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_overview.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Shopify概要
 article_title: "Shopify概要"
-description: "このリファレンス記事では、BrazeとShopifyの提携について説明しています。Shopifyはグローバルなコマース企業であり、ShopifyストアをBrazeとシームレスに接続して、選択したShopifyのwebhookをBrazeに渡すことができます。Brazeクロスチャネルの戦略とキャンバスを活用して、顧客が購入を完了するよう促したり、以前の購入に基づいてユーザーをリターゲティングする。"
+description: "このリファレンス記事では、Braze と Shopify のパートナーシップについて説明します。Shopify はグローバルなコマース企業であり、Shopify ストアを Brazeとシームレスに接続して、選択した Shopify Webhook を Braze に渡すことができます。Braze クロスチャネル戦略とキャンバスを活用して、顧客が購入を完了するように促し、購入履歴に基づいてユーザーをリターゲティングできます。"
 page_type: partner
 search_tag: Partner
 alias: "/shopify_overview/"
@@ -10,14 +10,14 @@ page_order: 0
 
 # Shopify概要
 
-> [Shopify](https://www.shopify.com/) は、あらゆる規模の小売 (店) ビジネスを開始、成長、マーケティング、および管理するための信頼できるツールを提供する、世界をリードするコマース企業です。Shopifyは、信頼性の高いプラットフォームとサービスを提供し、世界中の消費者により良いショッピング体験を提供することで、すべての人にとって商取引をより良くします。
+> [Shopify](https://www.shopify.com/) は、あらゆる規模の小売 (店) ビジネスの開始、拡大、マーケティング、および管理のための信頼できるツールを提供する、世界をリードするコマース企業です。Shopifyは、信頼性の高いプラットフォームとサービスを提供し、世界中の消費者により良いショッピング体験を提供することで、すべての人にとって商取引をより良くします。
 
-ShopifyとBrazeの統合により、Shopifyストアを接続してShopifyデータをシームレスにBrazeに渡すことができます。Brazeでクロスチャネルの戦略とキャンバスを活用して、新しいリードを引き付けたり、新しい顧客にメッセージを送ったり、放棄されたチェックアウトメッセージングでユーザーをリターゲティングして購入を完了するよう促すことができます。
+ShopifyとBrazeの統合により、Shopifyストアを接続してShopifyデータをシームレスにBrazeに渡すことができます。Brazeでクロスチャネルの戦略とキャンバスを活用して、新しいリードの獲得、新しい顧客へのメッセージの送信、ユーザーに購入の完了を促す購入手続き放棄対応メッセージによるユーザーのリターゲティングを行うことができます。
 
 ## サポートされている機能
 
 - Braze Web SDKを介してオンサイトの行動と匿名ユーザーを追跡する
-- Braze Web SDKを介してShopifyの顧客をBrazeに同期および照合するのを支援する
+- Braze Web SDK を使用して Braze で Shopify 顧客の同期と照合を支援する
 - Shopifyの顧客データを同期する
 - ShopifyのメールおよびSMSサブスクライバーのオプトインサブスクリプション状態を収集する
 - 過去のShopify購入データをバックフィルする 
@@ -26,13 +26,13 @@ ShopifyとBrazeの統合により、Shopifyストアを接続してShopifyデー
 
 ## サポートされているユースケース 
 
-- パス-to-purchase campaigns and キャンバス ユーザー journeys, including: 
+- 次を含む購入経路キャンペーンとキャンバスユーザージャーニー: 
   - ブラウズ放棄 
-  - 放棄カート 
-  - 放棄されたチェックアウト 
-- 購入後のキャンペーンとキャンバスユーザーの旅程を含む:
+  - カート放棄 
+  - 購入手続き放棄 
+- 次を含む購入後のキャンペーンとキャンバスユーザージャーニー:
   - 注文確認 
-  - 実現の更新 
+  - フルフィルメントの更新 
   - 注文のキャンセル 
   - 注文の払い戻し
 - 製品の推奨
@@ -43,12 +43,12 @@ ShopifyとBrazeの統合により、Shopifyストアを接続してShopifyデー
 
 | 要件 | 説明 |
 | --- | --- |
-| Shopifyストア | アクティブな[Shopify](https://www.shopify.com/)ストアがあります。<br><br>ワークスペースごとに1つのShopifyストアを接続できます。複数のストアを1つのワークスペースに接続することに興味がある場合は、Shopifyの複数ストアベータ版に参加するために顧客成功マネージャーに連絡してください。 |
-| Shopify ユーザー permissions | あなたは、Shopifyストアに対して次のいずれかの権限を持っています:{::nomarkdown}<ul><li>店主</li><li>スタッフ</li><li>すべての一般およびオンラインストアの設定に加え、次の追加の管理者権限を持つメンバー:<ul><li>注文</li><li><b>製品</b>の下にあるビュー</li><li>顧客</li><li>設定を管理する</li><li>スタッフや協力者が開発したアプリを表示</li><li>アプリとチャンネルの管理とインストール</li></ul></li></ul>{:/} |
+| Shopify ストア | アクティブな[Shopify](https://www.shopify.com/)ストアがあります。<br><br>ワークスペースごとに1つのShopifyストアを接続できます。複数のストアを1つのワークスペースに接続することに興味がある場合は、Shopify Multiple Stores ベータ版への参加についてカスタマーサクセスマネージャーにご連絡ください。 |
+| Shopify のユーザー権限 | Shopify ストアに対して次のいずれかの権限を持ちます。{::nomarkdown}<ul><li>店主</li><li>スタッフ</li><li>すべての一般設定およびオンラインストア設定と、次の管理者権限を持つメンバー:<ul><li>Orders</li><li><b>製品</b>の下にあるビュー</li><li>顧客</li><li>設定を管理する</li><li>スタッフや協力者が開発したアプリを表示</li><li>アプリとチャンネルの管理とインストール</li></ul></li></ul>{:/} |
 | Braze Web SDK 実装 | オンサイトの行動と匿名ユーザーを追跡するには、デフォルトのShopify統合または手動でBraze Web SDKを実装する必要があります。<br><br>詳細な実装オプションについては、[ShopifyサイトでのWeb SDKの実装]({{site.baseurl}}//partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/#implement-web-sdk)を参照してください。 |
 | イベントプロパティセグメンテーションが有効になりました | Shopifyイベントプロパティをセグメント化できることを確認するには、顧客成功マネージャーまたは[Brazeサポート]({{site.baseurl}}/braze_support/)と連携して、Brazeダッシュボードでイベントプロパティのセグメンテーションがオンになっていることを確認してください。 |
 {: .reset-td-br-1 .reset-td-br-2 }
 
-## 一般データ保護規則（GDPR）
+## 一般データ保護規則 (GDPR)
 
-Brazeのサービスに顧客またはその代理として提供された個人データに関して、Brazeはデータ処理者であり、当社の顧客はデータ管理者です。したがって、Brazeはそのような個人データを当社の顧客の指示に従ってのみ処理し、該当する場合には、データ主体からの要求を顧客に通知します。データ管理者として、私たちの顧客はデータ主体の要求に直接対応します。BrazeプラットフォームのShopify統合の一環として、Brazeは自動的に[ShopifyのGDPR webhook](https://shopify.dev/tutorials/add-gdpr-webhooks-to-your-app)を受信します。ただし、Brazeの顧客は、[Braze SDKs]({{site.baseurl}}/developer_guide/home/)または[REST APIs]({{site.baseurl}}/api/endpoints/user_data/#user-track-endpoint)を使用して、Shopifyの顧客からのデータ主体要求に応答する責任を最終的に負います。これは、当社の[GDPRコンプライアンス]({{site.baseurl}}/help/dp-technical-assistance/)ポリシーに従ったものです。
+Braze のサービスにお客様またはお客様の代理により提供される個人データに関して、Braze はデータ処理者であり、Braze のお客様はデータ管理者です。したがって、Braze はそのような個人データを当社のお客様の指示のみに従って処理し、該当する場合には、データ主体の要求をお客様に通知します。当社のお客様はデータ管理者としてデータ主体の要求に直接対応します。BrazeプラットフォームのShopify統合の一環として、Brazeは自動的に[ShopifyのGDPR webhook](https://shopify.dev/tutorials/add-gdpr-webhooks-to-your-app)を受信します。ただし、Brazeの顧客は、[Braze SDKs]({{site.baseurl}}/developer_guide/home/)または[REST APIs]({{site.baseurl}}/api/endpoints/user_data/#user-track-endpoint)を使用して、Shopifyの顧客からのデータ主体要求に応答する責任を最終的に負います。これは、当社の[GDPRコンプライアンス]({{site.baseurl}}/help/dp-technical-assistance/)ポリシーに従ったものです。
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/shopify_data_in_braze.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/shopify_data_in_braze.md
index bd60e2c7f1e..c4072a0f9e7 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/shopify_data_in_braze.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/shopify_data_in_braze.md
@@ -28,9 +28,9 @@ page_order: 1
 | バリアブル｜リキッド・テンプレーティング
 | --- | --- |
 | アイテムID｜`{{event_properties.${id}}}` ｜
-| アイテムタイトル｜`{{event_properties.${title}}}` ｜
-| 商品価格｜`{{event_properties.${price}}}` ｜
-| アイテムベンダー｜`{{event_properties.${vendor}}}` ｜
+| アイテムタイトル  | `{{event_properties.${title}}}` |
+| アイテム価格 | `{{event_properties.${price}}}` |
+| アイテムベンダー | `{{event_properties.${vendor}}}` |
 | アイテム画像｜`{{event_properties.${images}}}` ｜
 
 
@@ -47,9 +47,9 @@ page_order: 1
 | バリアブル｜リキッド・テンプレーティング
 | --- | --- |
 | アイテムID｜`{{event_properties.${id}}}` ｜
-| アイテムタイトル｜`{{event_properties.${title}}}` ｜
-| 商品価格｜`{{event_properties.${price}}}` ｜
-| アイテムベンダー｜`{{event_properties.${vendor}}}` ｜
+| アイテムタイトル  | `{{event_properties.${title}}}` |
+| アイテム価格 | `{{event_properties.${price}}}` |
+| アイテムベンダー | `{{event_properties.${vendor}}}` |
 | アイテム画像｜`{{event_properties.${images}}}` ｜
 {% endraw %}
 {% endsubtab %}
@@ -64,13 +64,13 @@ page_order: 1
 | バリアブル｜リキッド・テンプレーティング
 | --- | --- |
 | アイテムID｜`{{event_properties.${line_items}[0].product_id}}` ｜
-| アイテム数量｜`{{event_properties.${line_items}[0].quantity}}` ｜
+| アイテム数量 | `{{event_properties.${line_items}[0].quantity}}` |
 | アイテムSKU｜`{{event_properties.${line_items}[0].sku}}` ｜
-| アイテムタイトル｜`{{event_properties.${line_items}[0].title}}` ｜
-| アイテムベンダー｜`{{event_properties.${line_items}[0].vendor}}` ｜
-| 項目プロパティ｜`{{event_properties.${line_items}[0].properties}}` ｜
-| 商品価格｜`{{event_properties.${line_items}[0].price}}` ｜
-| バリアントID｜`{{event_properties.${line_items}[0].variant_id}}` ｜
+| アイテムタイトル | `{{event_properties.${line_items}[0].title}}` |
+| アイテムベンダー | `{{event_properties.${line_items}[0].vendor}}` |
+| アイテムプロパティ | `{{event_properties.${line_items}[0].properties}}` |
+| アイテム価格 | `{{event_properties.${line_items}[0].price}}` |
+| バリアント ID | `{{event_properties.${line_items}[0].variant_id}}` |
 {% endraw %}
 {% endsubtab %}
 
@@ -83,22 +83,22 @@ page_order: 1
 {% raw %}
 | バリアブル｜リキッド・テンプレーティング
 | --- | --- |
-| チェックアウトID｜`{{event_properties.${checkout_id}}}` ｜
+| チェックアウト ID | `{{event_properties.${checkout_id}}}` |
 | 放棄されたカートのURL｜`{{event_properties.${abandoned_checkout_url}}}` ｜
 | 割引コード｜`{{event_properties.${discount_code}}}` ｜
 | 価格｜総額｜`{{event_properties.${total_price}}}` ｜
 | 割引額｜`{{event_properties.${applied_discount}[0].amount}}` ｜
-| 割引タイトル｜`{{event_properties.${applied_discount}[0].title}}` ｜
+| 割引タイトル | `{{event_properties.${applied_discount}[0].title}}` |
 | 割引内容｜`{{event_properties.${applied_discount}[0].description}}` ｜
 | アイテムID｜`{{event_properties.${line_items}[0].product_id}}` ｜
-| アイテム数量｜`{{event_properties.${line_items}[0].quantity}}` ｜
+| アイテム数量 | `{{event_properties.${line_items}[0].quantity}}` |
 | アイテムSKU｜`{{event_properties.${line_items}[0].sku}}` ｜
-| アイテムタイトル｜`{{event_properties.${line_items}[0].title}}` ｜
-| アイテムベンダー｜`{{event_properties.${line_items}[0].vendor}}` ｜
-| 項目プロパティ｜`{{event_properties.${line_items}[0].properties}}` ｜
-| 商品価格｜`{{event_properties.${line_items}[0].price}}` ｜
-| バリアントID｜`{{event_properties.${line_items}[0].variant_id}}` ｜
-| バリアント・タイトル｜`{{event_properties.${line_items}[0].variant_title}}` ｜
+| アイテムタイトル | `{{event_properties.${line_items}[0].title}}` |
+| アイテムベンダー | `{{event_properties.${line_items}[0].vendor}}` |
+| アイテムプロパティ | `{{event_properties.${line_items}[0].properties}}` |
+| アイテム価格 | `{{event_properties.${line_items}[0].price}}` |
+| バリアント ID | `{{event_properties.${line_items}[0].variant_id}}` |
+| バリアントタイトル |`{{event_properties.${line_items}[0].variant_title}}` |
 {% endraw %}
 {% endsubtab %}
 
@@ -113,7 +113,7 @@ page_order: 1
 | バリアブル｜リキッド・テンプレーティング
 | --- | --- |
 | オーダーID｜`{{event_properties.${order_id}}}` ｜
-| ステータス確認｜`{{event_properties.${confirmed}}}` ｜
+| 確認ステータス | `{{event_properties.${confirmed}}}` |
 | 注文状況URL｜`{{event_properties.${order_status_url}}}` ｜
 | 注文番号｜`{{event_properties.${order_number}}}` ｜
 | キャンセルされたタイムスタンプ |`{{event_properties.${cancelled_at}}}` |
@@ -122,20 +122,20 @@ page_order: 1
 | タグ: | `{{event_properties.${tags}}}` |
 | 割引コード｜`{{event_properties.${discount_codes}}}` 
 | アイテムID｜`{{event_properties.${line_items}[0].product_id}}` ｜
-| アイテム数量｜`{{event_properties.${line_items}[0].quantity}}` ｜
+| アイテム数量 | `{{event_properties.${line_items}[0].quantity}}` |
 | アイテムSKU｜`{{event_properties.${line_items}[0].sku}}` ｜
-| アイテムタイトル｜`{{event_properties.${line_items}[0].title}}` ｜
-| アイテムベンダー｜`{{event_properties.${line_items}[0].vendor}}` ｜
-| 項目プロパティ｜`{{event_properties.${line_items}[0].properties}}` ｜
-| 商品価格｜`{{event_properties.${line_items}[0].price}}` ｜
-| バリアントID｜`{{event_properties.${line_items}[0].variant_id}}` ｜
-| バリアント・タイトル｜`{{event_properties.${line_items}[0].variant_title}}` ｜
-| 配送タイトル |`{{event_properties.${shipping}[0].title}}` 
+| アイテムタイトル | `{{event_properties.${line_items}[0].title}}` |
+| アイテムベンダー | `{{event_properties.${line_items}[0].vendor}}` |
+| アイテムプロパティ | `{{event_properties.${line_items}[0].properties}}` |
+| アイテム価格 | `{{event_properties.${line_items}[0].price}}` |
+| バリアント ID | `{{event_properties.${line_items}[0].variant_id}}` |
+| バリアントタイトル |`{{event_properties.${line_items}[0].variant_title}}` |
+| 配送タイトル | `{{event_properties.${shipping}[0].title}}` |
 | 価格｜送料｜`{{event_properties.${shipping}[0].price}}` 
 |Shopify ストア | `{{event_properties.${shopify_storefront}}}`|
-| フルフィルメント・ステータス｜`{{event_properties.${fulfillment_status}}}` ｜
-| 参照サイト｜`{{event_properties.${referring_site}}}` ｜
-| ペイメントゲートウェイ名｜`{{event_properties.${payment_gateway_names}}}` ｜
+| フルフィルメントステータス | `{{event_properties.${fulfillment_status}}}` |
+| 参照元サイト | `{{event_properties.${referring_site}}}` |
+| 決済ゲートウェイ名｜`{{event_properties.${payment_gateway_names}}}` ｜
 | 発送先住所1行目｜`{{event_properties.${shipping_address[0].address1}}}` ｜
 | 発送先住所 2行目｜`{{event_properties.${shipping_address[0].address2}}}` ｜
 | 配送先住所 都市名`{{event_properties.${shipping_address[0].city}}}` 
@@ -144,7 +144,7 @@ page_order: 1
 | 発送先住所 姓｜`{{event_properties.${shipping_address[0].last_name}}}` ｜
 | 発送先住所 都道府県`{{event_properties.${shipping_address[0].province}}}` 
 | 発送先住所 郵便番号`{{event_properties.${shipping_address[0].zip}}}` 
-| 請求書送付先住所1番｜`{{event_properties.${billing_address[0].address1}}}` ｜請求書送付先住所2番｜ ｜ ｜ 
+| 請求先住所行1 | `{{event_properties.${billing_address[0].address1}}}` |
 | 請求書送付先住所2行目｜`{{event_properties.${billing_address[0].address2}}}` ｜
 | 請求書送付先住所 都市名`{{event_properties.${billing_address[0].city}}}` 
 | 請求先住所 国名`{{event_properties.${billing_address[0].country}}}` 
@@ -160,18 +160,18 @@ page_order: 1
 
 
 **イベント**:購入<br>
-**タイプ**：[ブレイズ購入イベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/)
+**タイプ**：[Braze 購入イベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/)
 
 
 {% raw %}
 | バリアブル｜リキッド・テンプレーティング
 | --- | --- |
 | アイテムSKU｜`{{event_properties.${line_items}[0].sku}}` ｜
-| アイテムタイトル｜`{{event_properties.${line_items}[0].title}}` ｜
-| アイテムベンダー｜`{{event_properties.${line_items}[0].vendor}}` ｜
-| 項目プロパティ｜`{{event_properties.${line_items}[0].properties}}` ｜
-| バリアントID｜`{{event_properties.${line_items}[0].variant_id}}` ｜
-| バリアント・タイトル｜`{{event_properties.${line_items}[0].variant_title}}` ｜
+| アイテムタイトル  | `{{event_properties.${line_items}[0].title}}` |
+| アイテムベンダー | `{{event_properties.${line_items}[0].vendor}}` |
+| アイテムプロパティ | `{{event_properties.${line_items}[0].properties}}` |
+| バリアント ID | `{{event_properties.${line_items}[0].variant_id}}` |
+| バリアントタイトル |`{{event_properties.${line_items}[0].variant_title}}` |
 {% endraw %}
 
 
@@ -185,7 +185,7 @@ page_order: 1
 | バリアブル｜リキッド・テンプレーティング
 | --- | --- |
 | オーダーID｜`{{event_properties.${order_id}}}` ｜
-| ステータス確認｜`{{event_properties.${confirmed}}}` ｜
+| 確認ステータス | `{{event_properties.${confirmed}}}` |
 | 注文状況URL｜`{{event_properties.${order_status_url}}}` ｜
 | 注文番号｜`{{event_properties.${order_number}}}` ｜
 | キャンセルされたタイムスタンプ |`{{event_properties.${cancelled_at}}}` |
@@ -194,16 +194,16 @@ page_order: 1
 | タグ: | `{{event_properties.${tags}}}` |
 | 割引コード｜`{{event_properties.${discount_codes}}}` 
 | アイテムID｜`{{event_properties.${line_items}[0].product_id}}` ｜
-| アイテム数量｜`{{event_properties.${line_items}[0].quantity}}` ｜
+| アイテム数量 | `{{event_properties.${line_items}[0].quantity}}` |
 | アイテムSKU｜`{{event_properties.${line_items}[0].sku}}` ｜
-| アイテムタイトル｜`{{event_properties.${line_items}[0].title}}` ｜
-| アイテムベンダー｜`{{event_properties.${line_items}[0].vendor}}` ｜
-| 項目プロパティ｜`{{event_properties.${line_items}[0].properties}}` ｜
-| 商品価格｜`{{event_properties.${line_items}[0].price}}` ｜
-| 配送タイトル |`{{event_properties.${shipping}[0].title}}` 
+| アイテムタイトル | `{{event_properties.${line_items}[0].title}}` |
+| アイテムベンダー | `{{event_properties.${line_items}[0].vendor}}` |
+| アイテムプロパティ | `{{event_properties.${line_items}[0].properties}}` |
+| アイテム価格 | `{{event_properties.${line_items}[0].price}}` |
+| 配送タイトル | `{{event_properties.${shipping}[0].title}}` |
 | 価格｜送料｜`{{event_properties.${shipping}[0].price}}` 
-| バリアントID｜`{{event_properties.${line_items}[0].variant_id}}` ｜
-| バリアント・タイトル｜`{{event_properties.${line_items}[0].variant_title}}` ｜
+| バリアント ID | `{{event_properties.${line_items}[0].variant_id}}` |
+| バリアントタイトル |`{{event_properties.${line_items}[0].variant_title}}` |
 {% endraw %}
 {% endsubtab %}
 
@@ -219,40 +219,40 @@ page_order: 1
 | オーダーID｜`{{event_properties.${order_id}}}` ｜
 | 価格｜総額｜`{{event_properties.${total_price}}}` ｜
 | 割引総額｜`{{event_properties.${total_discounts}}}` ｜
-| ステータス確認｜`{{event_properties.${confirmed}}}` ｜
+| 確認ステータス | `{{event_properties.${confirmed}}}` |
 | 注文状況URL｜`{{event_properties.${order_status_url}}}` ｜
 | 注文番号｜`{{event_properties.${order_number}}}` ｜
 | キャンセルされたタイムスタンプ |`{{event_properties.${cancelled_at}}}` |
 | クローズド・タイムスタンプ｜`{{event_properties.${closed_at}}}` ｜
 | アイテムID｜`{{event_properties.${line_items}[0].product_id}}` ｜
-| アイテム数量｜`{{event_properties.${line_items}[0].quantity}}` ｜
+| アイテム数量 | `{{event_properties.${line_items}[0].quantity}}` |
 | アイテムSKU｜`{{event_properties.${line_items}[0].sku}}` ｜
-| アイテムタイトル｜`{{event_properties.${line_items}[0].title}}` ｜
-| アイテムベンダー｜`{{event_properties.${line_items}[0].vendor}}` ｜
+| アイテムタイトル | `{{event_properties.${line_items}[0].title}}` |
+| アイテムベンダー | `{{event_properties.${line_items}[0].vendor}}` |
 | アイテム名｜`{{event_properties.${line_items}[0].name}}` ｜
-| 項目プロパティ｜`{{event_properties.${line_items}[0].properties}}` ｜
-| 商品価格｜`{{event_properties.${line_items}[0].price}}` ｜
-| 配送タイトル |`{{event_properties.${shipping}[0].title}}` 
+| アイテムプロパティ | `{{event_properties.${line_items}[0].properties}}` |
+| アイテム価格 | `{{event_properties.${line_items}[0].price}}` |
+| 配送タイトル | `{{event_properties.${shipping}[0].title}}` |
 | 価格｜送料｜`{{event_properties.${shipping}[0].price}}` 
-| フルフィルメント・ステータス｜`{{event_properties.${fulfillment_status}}}` ｜
-| フルフィルメント 出荷状況｜`{{event_properties.${fulfillments}[0].shipment_status}}` ｜
-| フルフィルメント・ステータス｜`{{event_properties.${fulfillments}[0].status}}` ｜
+| フルフィルメントステータス | `{{event_properties.${fulfillment_status}}}` |
+| フルフィルメント出荷ステータス | `{{event_properties.${fulfillments}[0].shipment_status}}` |
+| フルフィルメントステータス | `{{event_properties.${fulfillments}[0].status}}` |
 \|`{{event_properties.${fulfillments}[0].tracking_company}}` ｜フルフィルメント・トラッキング・カンパニー｜Fulfillment Tracking Company｜フルフィルメント・トラッキング・カンパニー
 | フルフィルメント追跡番号｜`{{event_properties.${fulfillments}[0].tracking_number}}` ｜
 | フルフィルメント追跡番号｜`{{event_properties.${fulfillments}[0].tracking_numbers}}` ｜
 | フルフィルメント・トラッキングURL｜`{{event_properties.${fulfillments}[0].tracking_url}}` ｜
 | フルフィルメント・トラッキングURL｜`{{event_properties.${fulfillments}[0].tracking_urls}}` ｜
-| フルフィルメント・ステータス｜`{{event_properties.${fulfillments}[0].line_items[0].fulfillment_status}}` ｜
-| フルフィルメント名 |`{{event_properties.${fulfillments}[0].line_items[0].name}}` |
+| フルフィルメントステータス | `{{event_properties.${fulfillments}[0].line_items[0].fulfillment_status}}` |
+| フルフィルメント名 | `{{event_properties.${fulfillments}[0].line_items[0].name}}` |
 | フルフィルメント価格｜`{{event_properties.${fulfillments}[0].line_items[0].price}}` ｜
 | フルフィルメント・プロダクトID｜`{{event_properties.${fulfillments}[0].line_items[0].product_id}}` ｜
-| フルフィルメント数量｜`{{event_properties.${fulfillments}[0].line_items[0].quantity}}` ｜
-| フルフィルメント発送｜`{{event_properties.${fulfillments}[0].line_items[0].requires_shipping}}` 
+| フルフィルメント数量 | `{{event_properties.${fulfillments}[0].line_items[0].quantity}}` |
+| フルフィルメント配送 | `{{event_properties.${fulfillments}[0].line_items[0].requires_shipping}}` |
 | フルフィルメント SKU｜`{{event_properties.${fulfillments}[0].line_items[0].sku}}` 
-| フルフィルメント・タイトル｜`{{event_properties.${fulfillments}[0].line_items[0].title}}` ｜
-| フルフィルメント・ベンダー｜`{{event_properties.${fulfillments}[0].line_items[0].vendor` ｜
+| フルフィルメントタイトル| `{{event_properties.${fulfillments}[0].line_items[0].title}}` |
+| フルフィルメントベンダー | `{{event_properties.${fulfillments}[0].line_items[0].vendor` |
 | バリアントID｜`{{event_properties.${line_items}[0].variant_id}}` ｜
-| バリアント・タイトル｜`{{event_properties.${line_items}[0].variant_title}}` ｜
+| バリアントタイトル |`{{event_properties.${line_items}[0].variant_title}}` |
 {% endraw %}
 {% endsubtab %}
 
@@ -268,40 +268,40 @@ page_order: 1
 | オーダーID｜`{{event_properties.${order_id}}}` ｜
 | 価格｜総額｜`{{event_properties.${total_price}}}` ｜
 | 割引総額｜`{{event_properties.${total_discounts}}}` ｜
-| ステータス確認｜`{{event_properties.${confirmed}}}` ｜
+| 確認ステータス | `{{event_properties.${confirmed}}}` |
 | 注文状況URL｜`{{event_properties.${order_status_url}}}` ｜
 | 注文番号｜`{{event_properties.${order_number}}}` ｜
 | キャンセルされたタイムスタンプ |`{{event_properties.${cancelled_at}}}` |
 | クローズド・タイムスタンプ｜`{{event_properties.${closed_at}}}` ｜
 | アイテムID｜`{{event_properties.${line_items}[0].product_id}}` ｜
-| アイテム数量｜`{{event_properties.${line_items}[0].quantity}}` ｜
+| アイテム数量 | `{{event_properties.${line_items}[0].quantity}}` |
 | アイテムSKU｜`{{event_properties.${line_items}[0].sku}}` ｜
-| アイテムタイトル｜`{{event_properties.${line_items}[0].title}}` ｜
-| アイテムベンダー｜`{{event_properties.${line_items}[0].vendor}}` ｜
+| アイテムタイトル | `{{event_properties.${line_items}[0].title}}` |
+| アイテムベンダー | `{{event_properties.${line_items}[0].vendor}}` |
 | アイテム名｜`{{event_properties.${line_items}[0].name}}` ｜
-| 項目プロパティ｜`{{event_properties.${line_items}[0].properties}}` ｜
-| 商品価格｜`{{event_properties.${line_items}[0].price}}` ｜
-| 配送タイトル |`{{event_properties.${shipping}[0].title}}` 
+| アイテムプロパティ | `{{event_properties.${line_items}[0].properties}}` |
+| アイテム価格 | `{{event_properties.${line_items}[0].price}}` |
+| 配送タイトル | `{{event_properties.${shipping}[0].title}}` |
 | 価格｜送料｜`{{event_properties.${shipping}[0].price}}` 
-| フルフィルメント・ステータス｜`{{event_properties.${fulfillment_status}}}` ｜
-| フルフィルメント 出荷状況｜`{{event_properties.${fulfillments}[0].shipment_status}}` ｜
+| フルフィルメントステータス | `{{event_properties.${fulfillment_status}}}` |
+| フルフィルメント出荷ステータス | `{{event_properties.${fulfillments}[0].shipment_status}}` |
 | ステータス| `{{event_properties.${fulfillments}[0].status}}` |
 \|`{{event_properties.${fulfillments}[0].Fulfillment tracking_company}}` ｜フルフィルメント・トラッキング・カンパニー｜Fulfillment Tracking Company｜フルフィルメント・トラッキング・カンパニー
 | フルフィルメント追跡番号｜`{{event_properties.${fulfillments}[0].Fulfillment tracking_number}}` ｜
 | フルフィルメント追跡番号｜`{{event_properties.${fulfillments}[0].Fulfillment tracking_numbers}}` ｜
 | フルフィルメント・トラッキングURL｜`{{event_properties.${fulfillments}[0].Fulfillment tracking_url}}` ｜
 | フルフィルメント・トラッキングURL｜`{{event_properties.${fulfillments}[0].Fulfillment tracking_urls}}` ｜
-| フルフィルメント・ステータス｜`{{event_properties.${fulfillments}[0].line_items[0].fulfillment_status}}` ｜
-| フルフィルメント名 |`{{event_properties.${fulfillments}[0].line_items[0].name}}` |
+| フルフィルメントステータス | `{{event_properties.${fulfillments}[0].line_items[0].fulfillment_status}}` |
+| フルフィルメント名 | `{{event_properties.${fulfillments}[0].line_items[0].name}}` |
 | フルフィルメント価格｜`{{event_properties.${fulfillments}[0].line_items[0].price}}` ｜
 | フルフィルメント・プロダクトID｜`{{event_properties.${fulfillments}[0].line_items[0].product_id}}` ｜
-| フルフィルメント数量｜`{{event_properties.${fulfillments}[0].line_items[0].quantity}}` ｜
-| フルフィルメント発送｜`{{event_properties.${fulfillments}[0].line_items[0].requires_shipping}}` 
+| フルフィルメント数量 | `{{event_properties.${fulfillments}[0].line_items[0].quantity}}` |
+| フルフィルメント配送 | `{{event_properties.${fulfillments}[0].line_items[0].requires_shipping}}` |
 | フルフィルメント SKU｜`{{event_properties.${fulfillments}[0].line_items[0].sku}}` 
-| フルフィルメント・タイトル｜`{{event_properties.${fulfillments}[0].line_items[0].title}}` ｜
-| フルフィルメント・ベンダー｜`{{event_properties.${fulfillments}[0].line_items[0].vendor` ｜
+| フルフィルメントタイトル| `{{event_properties.${fulfillments}[0].line_items[0].title}}` |
+| フルフィルメントベンダー | `{{event_properties.${fulfillments}[0].line_items[0].vendor` |
 | バリアントID｜`{{event_properties.${line_items}[0].variant_id}}` ｜
-| バリアント・タイトル｜`{{event_properties.${line_items}[0].variant_title}}` ｜
+| バリアントタイトル |`{{event_properties.${line_items}[0].variant_title}}` |
 {% endraw %}
 {% endsubtab %}
 
@@ -323,20 +323,20 @@ page_order: 1
 | キャンセルされたタイムスタンプ |`{{event_properties.${cancelled_at}}}` |
 | タグ: | `{{event_properties.${tags}}}` |
 | 割引コード｜`{{event_properties.${discount_codes}}}` 
-| フルフィルメント・ステータス｜`{{event_properties.${fulfillment_status}}}` ｜
-| フルフィルメンツ｜`{{event_properties.${fulfillments}}}` ｜
+| フルフィルメントステータス | `{{event_properties.${fulfillment_status}}}` |
+| フルフィルメント | `{{event_properties.${fulfillments}}}` |
 | アイテムID｜`{{event_properties.${line_items}[0].product_id}}` ｜
-| アイテム数量｜`{{event_properties.${line_items}[0].quantity}}` ｜
+| アイテム数量 | `{{event_properties.${line_items}[0].quantity}}` |
 | アイテムSKU｜`{{event_properties.${line_items}[0].sku}}` ｜
-| アイテムタイトル｜`{{event_properties.${line_items}[0].title}}` ｜
-| アイテムベンダー｜`{{event_properties.${line_items}[0].vendor}}` ｜
+| アイテムタイトル | `{{event_properties.${line_items}[0].title}}` |
+| アイテムベンダー | `{{event_properties.${line_items}[0].vendor}}` |
 | アイテム名｜`{{event_properties.${line_items}[0].name}}` ｜
-| 項目プロパティ｜`{{event_properties.${line_items}[0].properties}}` ｜
-| フルフィルメント・ステータス｜`{{event_properties.${line_items}[0].fulfillment_status}}` ｜
-| 配送タイトル |`{{event_properties.${shipping}[0].title}}` 
+| アイテムプロパティ | `{{event_properties.${line_items}[0].properties}}` |
+| フルフィルメントステータス | `{{event_properties.${line_items}[0].fulfillment_status}}` |
+| 配送タイトル | `{{event_properties.${shipping}[0].title}}` |
 | 価格｜送料｜`{{event_properties.${shipping}[0].price}}` 
 | バリアントID｜`{{event_properties.${line_items}[0].variant_id}}` ｜
-| バリアント・タイトル｜`{{event_properties.${line_items}[0].variant_title}}` ｜
+| バリアントタイトル |`{{event_properties.${line_items}[0].variant_title}}` |
 {% endraw %}
 {% endsubtab %}
 
@@ -349,17 +349,17 @@ page_order: 1
 | バリアブル｜リキッド・テンプレーティング
 | --- | --- |
 | オーダーID｜`{{event_properties.${order_id}}}` ｜
-| オーダーノート｜`{event_properties.${note}}}` ｜
+| 注文メモ | `{event_properties.${note}}}` |
 | アイテムID｜`{{event_properties.${line_items}[0].product_id}}` ｜
-| アイテム数量｜`{{event_properties.${line_items}[0].quantity}}` ｜
+| アイテム数量 | `{{event_properties.${line_items}[0].quantity}}` |
 | アイテムSKU｜`{{event_properties.${line_items}[0].sku}}` ｜
-| アイテムタイトル｜`{{event_properties.${line_items}[0].title}}` ｜
-| アイテムベンダー｜`{{event_properties.${line_items}[0].vendor}}` ｜
+| アイテムタイトル | `{{event_properties.${line_items}[0].title}}` |
+| アイテムベンダー | `{{event_properties.${line_items}[0].vendor}}` |
 | アイテム名｜`{{event_properties.${line_items}[0].name}}` ｜
-| 項目プロパティ｜`{{event_properties.${line_items}[0].properties}}` ｜
-| 商品価格｜`{{event_properties.${line_items}[0].price}}` ｜
+| アイテムプロパティ | `{{event_properties.${line_items}[0].properties}}` |
+| アイテム価格 | `{{event_properties.${line_items}[0].price}}` |
 | バリアントID｜`{{event_properties.${line_items}[0].variant_id}}` ｜
-| バリアント・タイトル｜`{{event_properties.${line_items}[0].variant_title}}` ｜
+| バリアントタイトル |`{{event_properties.${line_items}[0].variant_title}}` |
 {% endraw %}
 {% endsubtab %}
 {% endsubtabs %}
@@ -793,24 +793,24 @@ page_order: 1
 ## サポートされているShopifyカスタム属性
 {% tabs ローカル %}
 {% tab Shopifyカスタム属性 %}
-| 属性名
+| 属性名 | 説明 |
 | --- | --- |
-\|`shopify_tags` | ショップオーナーが顧客に付けたタグ。カンマで区切られた値の文字列としてフォーマットされる。顧客は最大250個のタグを持つことができる。各タグは255文字まで。|
-\|`shopify_total_spent` | 顧客が注文履歴の中で使った金額の合計。|
+\|`shopify_tags` | ショップオーナーが顧客に付けたタグ。カンマで区切られた値の文字列としてフォーマットされる。顧客には最大250個のタグを付けることができます。各タグの最大文字数は255文字です。 |
+| `shopify_total_spent` | 注文履歴全体で顧客が支払った総額。 |
 ｜`shopify_order_count` ｜この顧客に関連する注文数。テストオーダーとアーカイブオーダーはカウントされない。|
 \|`shopify_last_order_id` | 顧客の最後の注文のID。|
-\|`shopify_last_order_name` | 顧客の最後の注文の名前。これは、注文リソースの`name` フィールドに直接関係する。|
+\|`shopify_last_order_name` | 顧客の最後の注文の名前。これは、注文リソースの `name` フィールドに直接関係しています。 |
 \|`shopify_zipcode` ｜顧客のデフォルト住所の郵便番号。|
-｜`shopify_province` ｜デフォルトの住所から顧客の都道府県を指定する。|
+| `shopify_province` | 顧客のデフォルトの住所の都道府県。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ### Liquid のパーソナライゼーション
 
-Shopifyカスタム属性にリキッドパーソナライゼーションを追加するには、**+パーソナライゼーションを**選択する。次に、パーソナライズのタイプとして**カスタム属性を**選択する。
+Shopify カスタム属性に Liquid パーソナライゼーションを追加するには、\[**\+ パーソナライゼーション**] を選択します。次に、\[パーソナライゼーションタイプ] として \[**カスタム属性**] を選択します。
 
 ![パーソナライズの追加」セクションの「属性」ドロップダウンが拡張された。]({% image_buster /assets/img/Shopify/add_personalization_2.png %}){: style="max-width:40%;"}
 
-カスタム属性を選択したら、デフォルト値を入力し、リキッドのスニペットをメッセージにコピーする。
+カスタム属性を選択したら、デフォルト値を入力して Liquid スニペットをメッセージにコピーします。
 
 ![リキッドのスニペットをメッセージに貼り付ける。]({% image_buster /assets/img/Shopify/copy_liquid_snippet.png %})
 
@@ -866,36 +866,36 @@ Shopifyカスタム属性にリキッドパーソナライゼーションを追
 - 国
 
 {% alert note %}
-Brazeは、サポートされているShopifyカスタム属性とBraze標準属性を更新するのは、既存のユーザープロファイルとデータに違いがある場合のみである。例えば、Shopifyの受信データにBobという名字が含まれており、BobがBrazeのユーザープロフィールの名字としてすでに存在する場合、Brazeは更新をトリガーせず、データポイントを請求しない。
+Brazeは、サポートされているShopifyカスタム属性とBraze標準属性を更新するのは、既存のユーザープロファイルとデータに違いがある場合のみである。たとえば、インバウンド Shopify データに Bob という名前が含まれており、Bob が Braze のユーザープロファイルに名前としてすでに存在している場合、Braze では更新はトリガーされず、データポイントにつ課金されません。
 {% endalert %}
 
 ## セグメンテーション
 
-Shopifyのイベントは、Segmentationの[既存のカスタムフィルターで]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/)フィルタリングできる。 
+Shopify のイベントは、セグメンテーションのすべての[既存のカスタムフィルター]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/)を使用してフィルタリングできます。 
 
 ![Shopify_Test セグメントの詳細ページ。カスタムイベント "shopify_checkouts_abandon" のフィルターがハイライトされている。][12]{: style="max-width:80%;"}
 
-さらに、Brazeの購入幅フィルターを使用して、ユーザーのセグメントを作成することもできる：
-- 最初／最後の購入
-- 特定のアプリの最初／最後の購入
-- 過去30日以内に購入した商品
-- 購入した商品の数
+さらに、Braze のさまざまな購入フィルターを利用して、次の条件に基づいてユーザーセグメントを作成することもできます。
+- 最初の購入 / 最後の購入
+- 特定のアプリの最初の購入 / 最後の購入
+- 過去30日以内に購入した製品
+- 購入した製品の数
 
 ![2020年10月17日以降に初めて購入したユーザーを対象としたセグメンテーションフィルター。][13]
 
 ![セグメンテーション・フィルターとして特定の製品IDを検索する。][14]
 
 {% alert note %}
-カスタムイベントプロパティでセグメント化する場合は、カスタマーサクセスマネージャーまたはBraze[サポートと]({{site.baseurl}}/braze_support/)協力して、セグメンテーションとLiquidで使用したいすべての関連イベントプロパティのフィルタリングを有効にしてください。
+カスタムイベントプロパティでセグメント化する場合は、カスタマーサクセスマネージャーまたは Braze[サポート]({{site.baseurl}}/braze_support/)と協力して、セグメンテーションと Liquid で使用するすべての関連イベントプロパティのフィルタリングを有効にしてください。
 {% endalert %} 
 
 ## キャンペーンとキャンバスのトリガー 
 
-BrazeのShopifyカスタムイベントを使えば、他の[カスタムイベントと]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-storage)同じようにCanvasesやキャンペーンをトリガーすることができる。例えば、Shopify`shopify_checkouts_abandon` イベントをトリガーとしたアクションベースのキャンバスを作成することができる。 
+Braze の Shopify カスタムイベントを使用することで、他の[カスタムイベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-storage)と同様にキャンバスやキャンペーンをトリガーできます。たとえば、キャンバスのエントリ基準内で Shopify `shopify_checkouts_abandon` イベントをトリガーするアクションベースのキャンバスを作成できます。 
 
 ![カスタムイベント "shopify_checkouts_abandon "を実行したユーザーを入力するアクションベースのキャンバス。][5]
 
-カスタムイベントプロパティのネストされたオブジェクトサポートにより、顧客はネストされたイベントプロパティを使用してキャンペーンやキャンバスをトリガーできるようになった。以下は、`shopify_created_order` カスタムイベントから特定の商品を使用してキャンペーンをトリガーする例である。`list_items[].product_id` 、商品リストのインデックスを作成し、商品IDにアクセスする。
+カスタムイベントプロパティのネストされたオブジェクトサポートにより、顧客はネストされたイベントプロパティを使用してキャンペーンやキャンバスをトリガーできるようになった。以下は、`shopify_created_order` カスタムイベントから特定の商品を使用してキャンペーンをトリガーする例である。`list_items[].product_id` を使用してアイテムリストのインデックスを作成し、製品 ID にアクセスするようにしてください。
 
 ![カスタムイベント "shopify_created_order "を実行し、ネストされたプロパティ "product_id "が特定の数字と等しいユーザーに送信するアクションベースのキャンペーン。][26]
 
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/use_cases.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/use_cases.md
index 497c371404f..5201d1ce75d 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/use_cases.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/shopify/using_shopify/use_cases.md
@@ -24,81 +24,81 @@ page_order: 2
 {% tab 返金 %}
 **Shopify返金イベント** - `shopify_created_refund`
 
-利用者には、一部または全部の払い戻しが行われた。このキャンペーンは、注文が正常に返金されたことをユーザーに知らせます。
+ユーザーに一部または全額が返金されました。このキャンペーンは、注文が正常に返金されたことをユーザーに知らせます。
 
 ![カスタムイベント"shopify_created_refund".]({% image_buster /assets/img/Shopify/refund.png %})を実行するユーザーに入力するアクションベースのキャンペーン{: style="max-width:45%;"}
 
 **メッセージングの例**
 
-![メールに&quot と書かれています; ご注文は返金されています、ご注文にアプリの指摘がなかったことをお詫びします。返金は成功裏にお送りいたしました。ファンドがステートメント&クォートで耳をアプリするまで、3～5営業日お待ちください; " View Account" button.]({% image_buster /assets/img/Shopify/refund2.png %}){: style="max-width:80%;border:0;"}
+![テキスト「Your order has been refunded, Sorry that you were disappointed with your order.返金は成功裏にお送りいたしました。Please wait 3-5 business days for the funds to appear in your statement」と「View Account」ボタンが表示されているメール。]({% image_buster /assets/img/Shopify/refund2.png %}){: style="max-width:80%;border:0;"}
 {% endtab %}
 {% tab キャンセル %}
 **Shopify キャンセル換算イベント** - `shopify_cancelled_order`
 
-ユーザは、フルフィルメント前に注文をキャンセルすることができました。このキャンペーンにより、ユーザーは自分の購買が正常にキャンセルされたことを認識できます。 
+ユーザーはフルフィルメント前に注文をキャンセルできました。このキャンペーンにより、ユーザーは自分の購買が正常にキャンセルされたことを認識できます。 
 
 ![カスタムイベント"shopify_キャンセル led_order".]({% image_buster /assets/img/Shopify/cancellation.png %}) を実行するユーザーに入力するアクションベースのキャンペーン{: style="max-width:45%;"}
 
 **メッセージングの例**
 
-![メールに&quot と書かれています;ご注文はキャンセルされています、ご覧になれて申し訳ありません!ご注文のキャンセルに成功しました。ファンドがステートメント&クォートで耳をアプリするまで、3～5営業日お待ちください; " View Account" button.]({% image_buster /assets/img/Shopify/cancellation2.png %}){: style="max-width:80%;border:0;"}
+![メールに&quot と書かれています;ご注文はキャンセルされています、ご覧になれて申し訳ありません!We've successfully canceled your order.Please wait 3-5 business days for the funds to appear in your statement」と「View Account」ボタンが表示されているメール。]({% image_buster /assets/img/Shopify/cancellation2.png %}){: style="max-width:80%;border:0;"}
 
 {% endtab %}
-{% tab 受注完了 %}
-**Shopifyが満たされたイベント** - `shopify_fulfilled_order`
+{% tab フルフィルメントが完了した注文 %}
+**Shopify フルフィルメント完了イベント** - `shopify_fulfilled_order`
 
-ユーザーの注文のすべての品目が正常に実行されました。このキャンペーンは、ユーザーに、注文全体が履行されたことを知らせます。
+ユーザーの注文のすべての品目が正常にフルフィルメントされました。このキャンペーンは、ユーザーに、注文全体が履行されたことを知らせます。
 
 ![カスタムイベント"shopify_fulfilled_order".]({% image_buster /assets/img/Shopify/fulfilled.png %})を実行するユーザーに入力するアクションベースのキャンペーン{: style="max-width:45%;"}
 
 **メッセージングの例**
 
-![テキスト&quot を含むテキストメッセージ;ご注文は完了しました!カートに入っている商品は全て届きました！あなたの口座に入り、領収書を確認してください。フィードバック."]({% image_buster /assets/img/Shopify/fulfilled2.png %})を終了するためのボーナスポイント{: style="max-width:40%;border:0;"}
+![テキスト「Your order's been fulfilled!カートに入っている商品は全て届きました！Please go into your account and confirm receipt.Bonus points for leaving feedback.」が表示されているテキストメッセージ。]({% image_buster /assets/img/Shopify/fulfilled2.png %}){: style="max-width:40%;border:0;"}
 
 {% endtab %}
-{% tab 一部受注完了 %}
-**Shopify部分的に満たされたイベント** - `shopify_partially_fulfilled_order`
+{% tab 部分的にフルフィルメントされた注文 %}
+**Shopify 部分的フルフィルメントイベント** - `shopify_partially_fulfilled_order`
 
-ユーザーの注文の一部の品目が正常に実行されました。このキャンペーンにより、ユーザー s は注文全体の一部が履行されたことを知ることができます。
+ユーザーの注文の一部の品目が正常にフルフィルメントされました。このキャンペーンは、注文全体の一部がフルフィルメントされたことをユーザーに知らせます。
 
 ![カスタムイベント"shopify_partially_fulfilled_order".]({% image_buster /assets/img/Shopify/partially_fulfilled.png %})を実行するユーザーに入るアクションベースのキャンペーン{: style="max-width:45%;"}
 
 **メッセージングの例**
 
-![テキスト&quotを含むテキストメッセージ;ご注文の一部が完了しました!ご注文いただいた商品の一部をお届けし、残りはお待ちしております！配送が完全に完了したら、別のアラートを送信します。"]({% image_buster /assets/img/Shopify/partially_fulfilled2.png %}){: style="max-width:40%;border:0;"}
+![テキスト「Your order's been partially fulfilled!ご注文いただいた商品の一部をお届けし、残りはお待ちしております！配送が完全に完了したら、別のアラートを送信します。"]({% image_buster /assets/img/Shopify/partially_fulfilled2.png %}){: style="max-width:40%;border:0;"}
 
 {% endtab %}
-{% tab 有料オーダー %}
-**Shopify有料オーダーイベント** - `shopify_paid_order`
+{% tab 支払い済みの注文 %}
+**Shopify 支払い済みの注文イベント** - `shopify_paid_order`
 
-ユーザは注文に対して支払いを行い、注文ステータスは支払い済みに変更されます。このキャンペーンでは、ユーザーに、クレジットカードの支払いがキャプチャされたか、手動での支払いがあった場合に注文が支払い済みとしてマークされたことを通知します。
+ユーザーが注文に対して支払いを行い、注文ステータスが支払い済みに変わります。このキャンペーンでは、ユーザーに、クレジットカードの支払いがキャプチャされたか、手動での支払いがあった場合に注文が支払い済みとしてマークされたことを通知します。
 
 ![カスタムイベント"shopify_paid_order".]({% image_buster /assets/img/Shopify/paid.png %})を実行するユーザーに入力するアクションベースのキャンペーン{: style="max-width:45%;"}
 
 **メッセージングの例**
 
-![テキスト &quot を含むメール;お支払いを受け取りました!あなたの注文はWoohooで支払われました!私たちが支払いを処理し、あなたの商品を準備するために、1～2営業日待ってください。その後、出荷します!" a "View Account" button.]({% image_buster /assets/img/Shopify/paid2.png %}){: style="max-width:80%;border:0;"}
+![テキスト「We've received your Payment!あなたの注文はWoohooで支払われました!私たちが支払いを処理し、あなたの商品を準備するために、1～2営業日待ってください。Then we'll ship it out!」と「View Account」ボタンが表示されているメール。]({% image_buster /assets/img/Shopify/paid2.png %}){: style="max-width:80%;border:0;"}
 
 {% endtab %}
 {% endtabs  %}
 ### Canvases
 
 {% tabs ローカル %}
-{% tab 放棄されたチェックアウトキャンバス %}
+{% tab 購入手続き放棄キャンバス %}
 
-**放棄されたチェックアウトキャンバス**
+**購入手続き放棄キャンバス**
 
-ユーザはチェックアウトフローを破棄し、出発までにトランスアクションを完了できません。このキャンバスでは、トランスアクションを終了していないユーザーに自動リマインダーを送信して、チェックアウトフローに戻すことができます。
+ユーザーが購入手続きフローを放棄し、離れる前に取引を完了できませんでした。このキャンバスでは、取引を完了していないユーザーを購入手続きフローに呼び戻すために、このようなユーザーに自動リマインダーを送信できます。
 
-アクションベースのエントリ `shopify_abandoned_checkout`<br>
+アクションベースのエントリイベント: `shopify_abandoned_checkout`<br>
 例外イベント: `shopify_created_order` または購入
 
 ![]({% image_buster /assets/img/Shopify/abandoned_checkout_canvas.gif %})
 
 {% endtab %}
-{% tab 購入後のキャンバス %}
+{% tab 購入後処理キャンバス %}
 
-**購入後のキャンバス**
+**購入後処理キャンバス**
 
 ユーザーが購入を成功させ、自分の購入がどのように気に入ったかを知りたいと思うようになりました。このキャンバスでは、フォローアップメッセージをユーザーに送信してフィードバックを収集できます。 
 
@@ -109,15 +109,15 @@ page_order: 2
 {% endtab %}
 {% endtabs %}
 
-## 詳細
+## 上級者
 
-プラットフォームに慣れると、より複雑なユースケースs を設定できます。
+プラットフォームに慣れたら、より複雑なユースケースを設定できます。
 
 ### キャンペーン
 
 {% tabs ローカル %}
 {% tab ユーザーの推奨事項 %}
-**ユーザーの推奨事項**
+**ユーザーレコメンデーション**
 ![]({% image_buster /assets/img/Shopify/product_view.png %}){: style="max-width:30%;border:0;float:right;"}
 
 ユーザーはアイテムをクリックまたは表示しましたが、購入しませんでした。このキャンペーンは、同じまたは類似のアイテム(接続されたコンテンツで推奨)を持つユーザーにフォローアップメッセージを送信し、ユーザーにそのうちの1つを購入するように促します。
@@ -138,22 +138,22 @@ page_order: 2
 
 **返金ウィンバックキャンバス**
 
-利用者には、一部または全部の払い戻しが行われた。このキャンバスはフォローアップメッセージを送信して、ユーザーが再び購買するようにします。
+ユーザーに一部または全額が返金されました。このキャンバスは、フォローアップメッセージを送信して、ユーザーが再び購入するように働きかけます。
 
-アクションベースのエントリ `shopify_created_refund`<br>
+アクションベースのエントリイベント: `shopify_created_refund`<br>
 例外イベント: `shopify_created_order` または購入
 
 ![]({% image_buster /assets/img/Shopify/winback_canvas_refund.gif %})
 
 
 {% endtab %}
-{% tab ウィンバック・キャンセル・レイション・キャンバス %}
+{% tab ウィンバックキャンセルキャンバス %}
 
-**ウィンバック・キャンセル・レイション・キャンバス**
+**ウィンバックキャンセルキャンバス**
 
-ユーザは、フルフィルメント前に注文をキャンセルすることができました。このキャンバスはフォローアップメッセージを送信して、ユーザーが再び購買するようにします。
+ユーザーはフルフィルメント前に注文をキャンセルできました。このキャンバスは、フォローアップメッセージを送信して、ユーザーが再び購入するように働きかけます。
 
-アクションベースのエントリ `shopify_cancelled_order`<br>
+アクションベースのエントリイベント: `shopify_cancelled_order`<br>
 例外イベント: `shopify_created_order` または購入
 
 ![]({% image_buster /assets/img/Shopify/winback_canvas_cancel.gif %})
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/yotpo.md b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/yotpo.md
index cd2a2e8ed46..d72d4a414b5 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/yotpo.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/ecommerce/yotpo.md
@@ -1,37 +1,37 @@
 ---
-nav_title: ヨットポ
-article_title: ヨットポ
+nav_title: Yotpo
+article_title: Yotpo
 alias: /partners/yotpo/
 description: "この参考記事では、BrazeとYotpoのパートナーシップについて概説している。Yotpoはeコマース・マーケティング・プラットフォームのリーディングカンパニーで、何千もの先進的なブランドが消費者直販の成長を加速させるのを支援している。"
 page_type: partner
 search_tag: Partner
 ---
 
-# ヨットポ
+# Yotpo
 
-> 大手eコマース・マーケティング・プラットフォームの[Yotpoは](https://www.yotpo.com/)、何千もの先進的なブランドが消費者直販の成長を加速させるのを支援している。Yotpoのシングルプラットフォームアプローチは、レビュー、ロイヤルティ、SMSマーケティングなどのデータ主導型ソリューションを統合し、ブランドがよりスマートでコンバージョンの高い顧客体験を創造できるようにする。
+> [Yotpo](https://www.yotpo.com/) は大手 e コマースマーケティングプラットフォームであり、何千もの先進的なブランドが消費者直販の成長を加速できるよう支援しています。Yotpoのシングルプラットフォームアプローチは、レビュー、ロイヤルティ、SMSマーケティングなどのデータ主導型ソリューションを統合し、ブランドがよりスマートでコンバージョンの高い顧客体験を創造できるようにする。
 
-BrazeとYotpoの統合により、Braze内のEメールやその他のコミュニケーションチャンネルで、商品に関する星評価、トップレビュー、視覚的なユーザー生成コンテンツ（UGC）を動的に取得し、表示することができる。また、顧客レベルのロイヤルティデータをEメールやその他のコミュニケーション手段に含めることで、よりパーソナライズされたインタラクションを実現し、売上とロイヤルティを高めることができる。
+BrazeとYotpoの統合により、Braze内のEメールやその他のコミュニケーションチャンネルで、商品に関する星評価、トップレビュー、視覚的なユーザー生成コンテンツ（UGC）を動的に取得し、表示することができる。また、顧客レベルのロイヤルティデータをメールやその他のコミュニケーション手段に組み込むことで、よりパーソナライズされたインタラクションを実現し、売上とロイヤルティを高めることができます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
 | Yotpoアカウント | このパートナーシップを利用するには、Yotpoアカウントが必要である。 |
-| YotpoレビューAPIキー | このAPIは、Connected Contentのコード・スニペット内に実装される。<br><br>詳細については、[Yotpoアプリのキーとシークレットキーの見つけ](https://support.yotpo.com/en/article/finding-your-yotpo-app-key-and-secret-key)方を参照のこと。 |
-| YotpoロイヤリティAPIキー | このAPIキーとGUIDは、Connected Contentのコード・スニペット内に実装される。<br><br>詳細については、[ロイヤリティ＆リファーラルAPIキーとGUIDを見つけるを](https://support.yotpo.com/en/article/finding-your-loyalty-referrals-api-key-and-guid)参照のこと。|
+| YotpoレビューAPIキー | この API は、コネクテッドコンテンツのコードスニペット内に実装されます。<br><br>詳細については、[Yotpo アプリのキーとシークレットキーの確認方法](https://support.yotpo.com/en/article/finding-your-yotpo-app-key-and-secret-key)を参照してください |
+| YotpoロイヤリティAPIキー | この API キーと GUID は、コネクテッドコンテンツのコードスニペット内に実装されます。<br><br>詳細については、[Loyalty & Referrals API キーと GUID の確認方法](https://support.yotpo.com/en/article/finding-your-loyalty-referrals-api-key-and-guid)を参照してください。|
 {: .reset-td-br-1 .reset-td-br-2}
 
-続行する前に、YotpoのプロダクトIDが、Brazeから動的に引き出される`product_id` と同じであることを確認する。これは統合が機能するためには必須である。 
+続行する前に、YotpoのプロダクトIDが、Brazeから動的に引き出される`product_id` と同じであることを確認する。これは統合が機能するために必須の作業です。 
 
 自分のYotpoプロダクトIDを見つけるには、以下のステップを実行する：
 
-1. あなたの店のウェブサイトにアクセスする。
+1. ストア Web サイトに移動します。
 2. 製品ページを開く。
-3. 右クリックして**Inspectを**選択する。
-4. <kbd>Control</kbd>+<kbd>F</kbd>キーを押し、コード内の`yotpo-main` を検索する。`data-product ID` 変数とその値は、Yotpo divに表示される。
+3. 右クリックして \[**Inspect**] を選択します。
+4. <kbd>Control</kbd>+<kbd>F</kbd>キーを押し、コード内の`yotpo-main` を検索する。`data-product ID` 変数とその値が Yotpo div に表示されます。
 
-![yotpo-mainを検査して検索し、data-product ID変数を見つける。][1]
+![調査して yotpo-main を探し、data-product ID 変数を確認する。][1]
 
 ## 統合
 
@@ -40,11 +40,11 @@ YotpoとBrazeを統合するには、以下のステップを実行する：
 1. Brazeのダッシュボードに行く。
 2. **キャンペーン]**ページで\[**キャンペーンを作成]**をクリックし、\[**Eメール]**を選択する。
 3. 好みのテンプレートを選択する。
-4. **Eメール本文の編集を**クリックし、ユースケースに応じた[コネクテッド・コンテンツ・スニペットを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/)追加する：
-    - [商品の星評価とレビュー数を表示する](#star-review-count)
+4. \[**メール本文を編集**] をクリックし、ユースケースに応じた [コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/)のスニペットを追加します。
+    - [製品の星評価とレビュー件数を表示する](#star-review-count)
     - [製品の最近の5つ星レビューを表示する](#five-star-review)
-    - [製品別にビジュアルUGCを表示する](#visual-ugc)
-    - [顧客のポイント残高をEメールに表示する](#loyalty-balance)
+    - [製品別にビジュアル UGC を表示する](#visual-ugc)
+    - [顧客のロイヤルティポイント残高をメールに表示する](#loyalty-balance)
 
 ### 商品の星評価とレビュー数を表示する {#star-review-count}
 
@@ -65,7 +65,7 @@ The average rating for this product is:
 ```
 {% endraw %}
 
-`<YOTPO-API-KEY>` をあなたのYotpoレビューAPIキーに置き換える。`product_id` 、Brazeから動的に引き出される。統合が機能するためには、Brazeの`product_id` 、YotpoのプロダクトID（通常はeコマースの親プロダクトID）と一致する必要がある。
+`<YOTPO-API-KEY>` をあなたのYotpoレビューAPIキーに置き換える。`product_id` が Braze から動的に取得されます。統合が機能するためには、Braze の`product_id` が Yotpo の製品 ID (通常は e コマース親製品 ID) と一致している必要があります。
 
 ![YOTPO-API-KEYをあなたのYotpo Reviews APIキーに置き換える。][2]
 
@@ -88,7 +88,7 @@ Recent 5 Star Review for this product:
 ```
 {% endraw %}
 
-`<YOTPO-API-KEY>` をあなたのYotpoレビューAPIキーに置き換える。`product_id` 、Brazeから動的に引き出される。統合が機能するためには、Brazeの`product_id` 、YotpoのプロダクトID（通常はeコマースの親プロダクトID）と一致する必要がある。
+`<YOTPO-API-KEY>` をあなたのYotpoレビューAPIキーに置き換える。`product_id` が Braze から動的に取得されます。統合が機能するためには、Braze の`product_id` が Yotpo の製品 ID (通常は e コマース親製品 ID) と一致している必要があります。
 
 メールエディターのスニペットはこんな感じになる：
 
@@ -96,7 +96,7 @@ Recent 5 Star Review for this product:
 
 ### 製品別にビジュアルUGCを表示する {#visual-ugc}
 
-このスニペットを使って、タグ付けされ公開されたYotpoの画像を取得し、ストック画像の代わりに、または追加のギャラリーとしてメールに追加する：
+次のスニペットを使用して、タグ付けされ公開された Yotpo 画像を取得し、ストック画像の代わりに、または追加のギャラリーとしてメールに追加します。
 
 {% raw %}
 ```liquid
@@ -117,15 +117,15 @@ Image return NULL
 ```
 {% endraw %}
 
-`<YOTPO-API-KEY>` をあなたのYotpoレビューAPIキーに置き換える。`product_id` 、Brazeから動的に引き出される。統合が機能するためには、Brazeの`product_id` 、YotpoのプロダクトID（通常はeコマースの親プロダクトID）と一致する必要がある。
+`<YOTPO-API-KEY>` をあなたのYotpoレビューAPIキーに置き換える。`product_id` が Braze から動的に取得されます。統合が機能するためには、Braze の`product_id` が Yotpo の製品 ID (通常は e コマース親製品 ID) と一致している必要があります。
 
-スニペットは次のようになる：
+スニペットは次のようになります。
 
 ![Yotpoで公開された画像のスニペットを表示するEメールエディタの例][4]
 
-### 顧客のポイント残高をEメールに表示する {#loyalty-balance}
+### 顧客のロイヤルティポイント残高をメールに表示する{#loyalty-balance}
 
-このスニペットを使って、顧客のポイント残高を取得し、Eメールメッセージに使用する：
+次のスニペットを使用して、顧客のロイヤルティポイント残高を取得してメールメッセージに使用します。
 
 {% raw %}
 ```liquid
@@ -147,15 +147,15 @@ Only {{publication.vip_tier_upgrade_requirements.points_needed}} more points to
 ```
 {% endraw %}
 
-`<YOTPO-LOYALTY-GUID>` と`<YOTPO-LOYALTY-API-KEY>` をあなたのYotpoロイヤリティ認証情報に置き換える。`email_address` 、Brazeから動的に引き出される。統合が機能するためには、EメールはEメールを受信する顧客のEメールアドレスでなければならない。
+`<YOTPO-LOYALTY-GUID>` と`<YOTPO-LOYALTY-API-KEY>` をあなたのYotpoロイヤリティ認証情報に置き換える。`email_address` が Braze から動的に取得されます。この統合が機能するためには、メールのアドレスが、このメールを受信する顧客のメールアドレスでなければなりません。
 
-スニペットは次のようになる：
+スニペットは次のようになります。
 
 ![顧客ロイヤルティ残高のスニペットを表示するEメールエディターの例][5]
 
 ## よくある質問 {#faq}
 
-#### もし5つ星のレビューがなかったら？
+#### 5つ星レビューがない場合
 
 5つ星のレビューがない場合（エンドポイントのレスポンスが5つ星のレビューに対してNULLを返した場合など）、コンテンツは表示されない。
 
@@ -165,7 +165,7 @@ Only {{publication.vip_tier_upgrade_requirements.points_needed}} more points to
 
 #### ルック＆フィールをカスタマイズしたり、Yotpoから他のデータフィールドを引き出すことは可能か？
 
-はい、できます。その他のデータ・ポイントやカスタマイズ・オプションについては、[APIコールを行うを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call/)参照のこと。そのためには、フロントエンド開発者の支援が必要かもしれない。
+はい、できます。その他のデータポイントやカスタマイズオプションについては、「[API 呼び出し]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call/)」を参照してください。そのためには、フロントエンド開発者の支援が必要かもしれない。
 
 {% alert note %}
 Yotpoはこのガイドに記載されている以上のカスタム要件には対応していない。
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates.md
index 7248f088cf8..2afa329783d 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates.md
@@ -4,7 +4,7 @@ article_title: メッセージ・テンプレート・パートナー
 page_order: 2
 
 page_type: landing
-description: "このランディングページは、Brazeのパートナー（合金）をリストアップしている。"
+description: "このランディングページには、統合によってメッセージテンプレートを利用できるようにする Braze パートナー(Alloys) が一覧表示されています。"
 
 layout: partner_page
 search_tag: Partner
@@ -14,23 +14,23 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Message Templates"
 
 valid_partner_list:
-- name: アルパコ
+- name: Alpaco
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/alpaco/
 - name: Dyspatch.io
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/dyspatch/
-- name: ステンソール
+- name: Stensul
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/stensul/
 - name: Stripo
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/stripo/
-- name: Eメール用タクシー
+- name: Taxi for Email
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/taxi_for_email/
-- name: ナック
+- name: Knak
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/knak/
-- name: IAMスタジオ（NNT）
+- name: IAM Studio (NNT)
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/iam_studio/
-- name: B.レイヤー 
+- name: B.Layer 
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/blayer/
-- name: サゲフロ
+- name: Sageflo
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/sageflo/
 - name: SmarterSends
   url: /docs/partners/message_orchestration/channel_extensions/email_templates/smartersends/
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/alpaco.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/alpaco.md
index b2a1b4a82db..707c3a99a59 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/alpaco.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/alpaco.md
@@ -1,62 +1,62 @@
 ---
-nav_title: アルパコ
-article_title: アルパコ
+nav_title: Alpaco
+article_title: Alpaco
 alias: /partners/Alpaco
-description: "BrazeとAlpacoの統合は、Alpacoの構文を活用して、データ駆動型のEメールテンプレートを作成し、Brazeにエクスポートする。"
+description: "Braze と Alpaco の統合では、Alpaco の構文を使用して、データドリブン型のメールテンプレートを作成して Braze にエクスポートします。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# アルパコ
+# Alpaco
 
-> [アルパコは](https://alpaco.email/)オンラインEメールマーケティングツールで、ドラッグ＆ドロップのEメールエディターにより、デザインとアウトプットを新しいレベルでコントロールできる。BrazeとAlpacoの統合により、オンブランドでデータドリブンなEメールをBrazeにエクスポートできる。 
+> [Alpaco](https://alpaco.email/) は、ドラッグ＆ドロップメールエディターを備えたオンラインメールマーケティングツールであり、デザインと出力をこれまでにない方法でコントロールできます。Braze と Alpaco の統合では、データドリブン型でブランドらしさのあるメールテンプレートを作成して Braze にエクスポートできます。 
 
 {% alert note %}
-アルパコは[リキッド](https://shopify.github.io/liquid/)変数を[フル](https://shopify.github.io/liquid/)サポートしており、Brazeコンフィギュレーションで使用されているリキッド変数もフルサポートしている。
+Alpaco は[完全な Liquid](https://shopify.github.io/liquid/) 変数をサポートしています。このため、Braze 設定で使用されるすべての Liquid 変数を完全にサポートしています。
 {% endalert %}
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ------------| ----------- |
-| アルパコアカウント | このパートナーシップを利用するには、アルパコのアカウントが必要だ。 |
+| Alpaco アカウント | このパートナーシップを活用するには、Alpaco アカウントが必要です。 |
 | Braze REST API キー | 完全な**テンプレート**権限を持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| クラスターインスタンス | Braze[クラスタインスタンスは]({{site.baseurl}}/api/basics/#endpoints)、BrazeダッシュボードとRESTエンドポイントに合わせる。<br><br> 例えば、ダッシュボードのURLが`https://dashboard-03.braze.com` の場合、エンドポイントは`dashboard-03` となる。  |
+| クラスターインスタンス | Braze [クラスターインスタンス]({{site.baseurl}}/api/basics/#endpoints)は、Braze ダッシュボードと REST エンドポイントに対応しています。<br><br> 例えば、ダッシュボードのURLが`https://dashboard-03.braze.com` の場合、エンドポイントは`dashboard-03` となる。  |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合
 
-Braze REST APIキーとクラスタインスタンスをアルパコのカスタマーサクセスチームに提供する。その後、チームが初期統合をセットアップする。
+Braze REST API キーとクラスターインスタンスを Alpaco カスタマーサクセスチームに提供します。その後、このチームが初期統合を設定できます。
 
 {% alert note %}
 これは1回限りのセットアップであり、今後のエクスポートは自動的にこのAPIキーを使用する。
 {% endalert %}
 
-## アルパコのEメールをBrazeにエクスポートする
+## Alpaco のメールを Braze にエクスポートする
 
-### ステップ1:アルパコでメールテンプレートを作成する
+### ステップ1:Alpaco でメールテンプレートを作成する
 
-アルパコ・プラットフォームでは、さまざまな設定やオプションを使って、ブランド・アイデンティティを表現するテンプレートを作成することができる。テンプレートに満足したら**Saveを**選択する。
+Alpaco プラットフォームでは、さまざまな設定やオプションを使用して、ブランドアイデンティティを表現するテンプレートを作成できます。テンプレートに満足したら \[**Save**] を選択します。
 
-![アルパコクリエイト テンプレート]({% image_buster /assets/img/alpaco/alpaco_1.png %})
+![Alpaco でのテンプレートの作成]({% image_buster /assets/img/alpaco/alpaco_1.png %})
 
 ### ステップ2:電子メールを作成する
 
-テンプレートが作成されたら、ロビーに移動し、テンプレートを使ってメールを作成する。**Reviewを**選択し、すべてが正しく見えることを確認する。
+テンプレートが作成されたら、ロビーに移動し、テンプレートを使ってメールを作成する。\[**Review**] を選択して、すべてが適切に表示されていることを確認します。
 
-![アルパコクリエイト]({% image_buster /assets/img/alpaco/alpaco_2.png %})
+![Alpaco でのメールの作成]({% image_buster /assets/img/alpaco/alpaco_2.png %})
 
 ### ステップ 3:Eメールを見直し、Brazeにエクスポートする
 
-**エクスポートを**選択し、Brazeインテグレーションを選択してEメールテンプレートをBrazeにエクスポートする。 
+\[**Export**] を選択し、Braze 統合を選択して、メールテンプレートを Braze にエクスポートします。 
 
-メールテンプレートを変更したい場合は、Alpacoで変更し、再度Brazeにエクスポートする。これでBrazeのメールがあなたの変更で更新される。
+メールテンプレートに変更を加える場合は、Alpaco でそれらの変更を行ってから、メールテンプレートを再び Braze にエクスポートします。これでBrazeのメールがあなたの変更で更新される。
 
-![アルパコ・エクスポート Eメール]({% image_buster /assets/img/alpaco/alpaco_3.png %})
+![Alpaco メールのエクスポート]({% image_buster /assets/img/alpaco/alpaco_3.png %})
 
 ## BrazeでAlpacoのEメールテンプレートを使う
 
-Brazeダッシュボードの**Templates & Media > Email Templatesから**、アップロードしたアルパコメールを探す。このテンプレートを使って、ブランドやデータに基づいたメールをユーザーに送ることができる。
+Braze ダッシュボードで **\[テンプレートとメディア] > \[メールテンプレート]** に移動して、アップロードした Alpaco メールを見つけます。このテンプレートを使用して、ブランドらしさのあるデータドリブン型のメールをユーザーに送信できます。
 
 [1]: {{site.baseurl}}/user_guide/message_building_by_channel/email/creating_an_email_template/
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/blayer.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/blayer.md
index ce92fc1bacb..49503c22321 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/blayer.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/blayer.md
@@ -1,7 +1,7 @@
 ---
-nav_title: B.レイヤー
-article_title: B.レイヤー
-description: "この参考記事では、Brazeとアプリ内メッセージビルダーであるB.Layerのパートナーシップについて概説している。"
+nav_title: B.Layer
+article_title: B.Layer
+description: "このリファレンス記事では、Braze と B.Layer のパートナーシップについて説明します。B.Layer はアプリ内メッセージビルダーであり、カスタム設計のアプリ内メッセージをコーディングなしで簡単、迅速に作成するために使用できます。"
 alias: /partners/blayer-inapps/
 page_type: partner
 search_tag: Partner
@@ -12,7 +12,7 @@ search_tag: Partner
 
 > [B.Layer](https://blayer.phiture.com) はPhitureのアプリ内メッセージビルダーで、モバイルアプリのCRMチームがコーディングなしで、シンプルかつ迅速にカスタムデザインのアプリ内メッセージを作成できるように支援する。 
 
-BrazeとB.Layer の統合により、B.Layer アプリ内メッセージビルダーを活用し、ZIPファイルまたはインラインHTMLとしてBrazeにエクスポート可能なオンブランドのアプリ内メッセージを構築することができる。この統合は、追加の開発者リソースを必要としないため、時間と予算を節約できる。
+Braze と B.Layer の統合により、B.Layer アプリ内メッセージビルダーを利用して、ブランドらしさのあるアプリ内メッセージを作成できます。このメッセージは、zip ファイルまたはインライン HTML として Braze にエクスポートできます。この統合には追加の開発者リソースが不要であるため、時間と予算を節約できます。
 
 ![][2]
 
@@ -20,14 +20,14 @@ BrazeとB.Layer の統合により、B.Layer アプリ内メッセージビル
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| B.Layer アカウント | A [B.Layer](https://blayer.phiture.com)このパートナーシップを利用するには、アカウントが必要である。 |
+| B.Layer アカウント | このパートナーシップを活用するには、[B.Layer](https://blayer.phiture.com) アカウントが必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
-B.Layer 、商品推薦スライダー、マルチスクリーンオンボーディングやアンケート、NPS、Eメールキャプチャ、スペシャルオファーなど、構築や実験の機会は無限にある。
+B.Layer では、製品レコメンデーションスライダー、マルチスクリーンオンボーディングまたはアンケート、NPS、メールキャプチャ、特別オファーなど、構築して試してみる機会が無限にあります。
 
-Lifesum、Blinkist、OnX Huntなどのブランドと協力し、余分なリソースを使わずにユーザー体験を向上させる手助けをしている。また、APSアワード2022のアプリ・イノベーション部門の最終選考にも残っている。
+Lifesum、Blinkist、OnX Hunt などの多数のブランドと協力し、追加のリソースを必要とせずにユーザーエクスペリエンスを改善できるように支援しています。また、APSアワード2022のアプリ・イノベーション部門の最終選考にも残っている。
 
 ## 統合
 
@@ -35,14 +35,14 @@ Lifesum、Blinkist、OnX Huntなどのブランドと協力し、余分なリソ
 
 #### ブランドカラーとフォントを設定する
 
-B.Layer で、ページ上部のハンバーガーメニューから、**ブランドアセット > ブランドアセットを追加を**クリックする。ここで、ブランドカラーとフォントを割り当てることができる。
-これで準備万端だ。これでアプリ内メッセージのデザインを始めることができる。
+B.Layer で、ページ上部のハンバーガーメニューから、**\[Brand assets] > \[add your brand assets]** をクリックします。ここで、ブランドカラーとフォントを割り当てることができる。
+これで準備万端だ。これでアプリ内メッセージのデザインを開始できます。
 
 ![][4]
 
 #### アプリ内メッセージをデザインする
 
-アプリ内メッセージをデザインするには、1つのアプリ内メッセージを選択する。次に、メッセージをスタイリングし、必要なコンポーネントを追加する。各コンポーネントは調整可能だ。
+アプリ内メッセージをデザインするには、アプリ内メッセージを1つ選択します。次に、メッセージをスタイリングし、必要なコンポーネントを追加する。各コンポーネントを調整できます。
 
 ![][5]
 
@@ -56,9 +56,9 @@ Brazeで、カスタムコードのアプリ内メッセージを作成する。
 
 ![][6]
 
-## ボタン・トラッキング
+## ボタントラッキング
 
-B.Layer を使えば、ボタン操作やテキスト入力をBraze属性として記録できる。それはエディター内でできる。よく知られている例は、NPS調査である。
+B.Layer を使えば、ボタン操作やテキスト入力をBraze属性として記録できる。この作業はエディター内で行うことができます。代表的な例として NPS アンケートがあります。
 
 B.Layer は、入力したリンク（例えば、`?button=0` ）に追加されたBrazeボタンのトラッキングを使用する。こうすることで、キャンペーンのアナリティクス部分でボタンのクリックを確認することができる。
 
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/dyspatch.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/dyspatch.md
index 83ff3050548..a25ee2c6c3b 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/dyspatch.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/dyspatch.md
@@ -10,15 +10,15 @@ search_tag: Partner
 
 # Dyspatch
 
-> [Dyspatch][1] は、コードを書く必要なく、美しく、レスポンシブで魅力的なメールs を作成するために使用される直感的なドラッグアンドドロップメールビルダーを提供します。あなたのチームとコラボレーションして、Dyspatch 内でメール s を作成してアプリし、それを数ステップ後にBraze にエクスポートしましょう! 
+> [Dyspatch][1] は、コードを書く必要なく、美しく、レスポンシブで魅力的なメールs を作成するために使用される直感的なドラッグアンドドロップメールビルダーを提供します。チームと協力して、Dyspatch 内でメールを作成して承認し、それらのメールを Braze にエクスポートします。この作業は短い手順で完了できます。 
 
-DyspatchとBrazeの統合により、BrazeにDyspatch メール テンプレートをエクスポートすることで、メール作成ライフサイクルを簡素化できます。
+Dyspatch と Braze の統合により、Dyspatch メールテンプレートを直接 Braze にエクスポートすることで、メール作成ライフサイクルを簡素化できます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| Dyspatch勘定 | [ [ownerまたはadmin role][4]を持つ[Dyspatchアカウント][3]は、この提携の進捗タグeを取るために必要です。 |
+| Dyspatch アカウント | このパートナーシップを利用するには、[所有者権限または管理者権限][4]を持つ[Dyspatch アカウント][3]が必要です。 |
 | Braze REST API キー | 完全な**テンプレート**権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
@@ -28,7 +28,7 @@ BrazeとDyspatchインテグレーションを使用すると、Brazeのメデ
 
 ### ステップ1:Brazeインテグレーションの作成
 
-Dyspatch 管理ポータルで、ユーザー名ドロップダウンメニューを開封し、**Integrations** を選択します。新しいインテグレーションを作成し、**Braze**を選択して、Braze API キーを入力します。
+Dyspatch 管理ポータルでユーザー名のドロップダウンメニューを開き、\[**Integrations**] を選択します。新しいインテグレーションを作成し、**Braze**を選択して、Braze API キーを入力します。
 
 **エクスポートのローカライズ**フィールドで、ローカライゼーションの管理方法を選択できます。このフィールドを使用すると、[メール テンプレートs][6]をローカライズし、Brazeにエクスポートしてメールs パーソナライズされたを言語またはロケールで簡単に送信できます。 
 
@@ -38,17 +38,17 @@ Dyspatch 管理ポータルで、ユーザー名ドロップダウンメニュ
 
 Dyspatch でメールを完了した後、テンプレートをBraze に送信するには、公開されたメール テンプレートを表示し、**Down読み込む/Export** をクリックしてから、**Export to Integration** をクリックします。
 
-テンプレートを手動でアップロードする場合は、公開メール テンプレートを表示し、**Down 読み込む/Export** をクリックしてから、**Down 読み込む HTML** をクリックします。次に、テンプレートをアップロードするには、Brazeアカウントの** s & Media > Email テンプレート s** セクションで、**From File** を選択します。
+テンプレートを手動でアップロードする場合は、公開メール テンプレートを表示し、**Down 読み込む/Export** をクリックしてから、**Down 読み込む HTML** をクリックします。次に、Braze アカウントの **\[テンプレートとメディア] > \[メールテンプレート]** セクションで \[**元のファイル**] を選択して、テンプレートをアップロードします。
 
 ![Dyspatchエクスポートテンプレート]({% image_buster /assets/img/dyspatch/dyspatch_export.gif %})
 
 {% alert important %}
-BrazeのDyspatch メール テンプレートの**Sending Info**で**インラインCSS**を選択しないでください。Dyspatch は、メールs が堅牢で、レスポンシブで、送信の準備ができていることを確認することで、これを処理します。
+BrazeのDyspatch メール テンプレートの**Sending Info**で**インラインCSS**を選択しないでください。Dyspatch は、メールが堅牢でレスポンシブであり、送信できる状態であることを確認して、これに対応します。
 {% endalert %}
 
 ### 使用
 
-Braze アカウントの ** テンプレート s& Media > E メールテンプレート s** セクションで、アップロードのDyspatch テンプレートを見つけます。これで、このメール テンプレートを使用してメールを顧客 s に送信できるようになりました。
+アップロードした Dyspatch テンプレートを、Braze アカウントの**\[テンプレートとメディア] > \[メールテンプレート]** セクションで確認します。これで、このメールテンプレートを使用して、顧客に魅力的なメールメッセージを送信できます。
 
 [1]: https://www.dyspatch.io
 [2]: https://dashboard.braze.com/sign_in
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/iam_studio.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/iam_studio.md
index 329be6e3f47..8070f086de4 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/iam_studio.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/iam_studio.md
@@ -1,7 +1,7 @@
 ---
 nav_title: IAMスタジオ
 article_title: IAMスタジオ
-description: "このリファレンス記事では、Braze とIAM Studio の連携について説明します。これは、メッセージパーソナライゼーション プラットフォームで、Braze を使用してパーソナライズされたを作成し、豊富なアプリ体験を提供することができます。"
+description: "このリファレンス記事では、Braze と IAM Studio のパートナーシップについて説明します。IAM Studio は、パーソナライズされたリッチなアプリ内エクスペリエンスを作成し、Braze を通じてそのエクスペリエンスを提供できるメッセージパーソナライゼーションプラットフォームです。"
 alias: /partners/iam_studio/
 page_type: partner
 search_tag: Partner
@@ -10,15 +10,15 @@ search_tag: Partner
 
 # IAMスタジオ
 
-> [IAM Studio](https://www.inappmessage.com) はno-コード メッセージパーソナライゼーション プラットフォームで、豊富なアプリ体験を作成し、Brazeを通じて配信できます。
+> [IAM Studio](https://www.inappmessage.com) は、カスタマイズされたリッチなアプリ内エクスペリエンスを作成し、Braze を通じてそのエクスペリエンスを提供できる、ノーコードのメッセージパーソナライゼーションプラットフォームです。
 
-Braze とIAM Studio の統合により、カスタマイズ可能なアプリ内メッセージ テンプレートs をBraze アプリ内メッセージに簡単に挿入でき、"画像置換、テキストモディフィケーション、ディープリンク設定s、カスタム属性s、およびイベント設定s を提供できます。IAM Studio を使用すると、メッセージのプロダクション時間を短縮し、コンテンツプランニングにより多くの時間を割くことができます。 
+Braze と IAM Studio の統合により、カスタマイズ可能なアプリ内メッセージテンプレートを Braze アプリ内メッセージに簡単に挿入できます。これにより、画像の置き換え、テキストの変更、ディープリンク設定、カスタム属性、イベント設定が提供されます。IAM Studio を使用すると、メッセージの作成時間を短縮し、コンテンツ計画により多くの時間を費やすことができます。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| IAM Studioアカウント | この提携の事前タグを行うには、[IAM Studioアカウント](https://www.inappmessage.com/register)が必要です。 |
+| IAM Studioアカウント | このパートナーシップを活用するには、[IAM Studio アカウント](https://www.inappmessage.com/register)が必要です。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## ユースケース
@@ -34,32 +34,32 @@ Braze とIAM Studio の統合により、カスタマイズ可能なアプリ内
 
 アプリ内メッセージ テンプレートギャラリーから使用するアプリ内メッセージ テンプレートを選択します
 
-![IAM Studio テンプレートギャラリーには、"carousel slide モーダル", "simple icon モーダル", "モーダル full "画像"など、さまざまなテンプレートが表示されます。][1]
+![IAM Studio テンプレートギャラリーに「carousel slide modal」、「carousel slide modal」、「simple icon modal」、「modal full image」など、さまざまなテンプレートが表示されている。][1]
 
 ### ステップ2:テンプレートのカスタマイズ
 
-まず、内容の"画像、文字、ボタンをカスタマイズします。"画像とボタンは必ず**Deeplink**を接続してください。
+まず、コンテンツの画像、テキスト、ボタンをカスタマイズします。"画像とボタンは必ず**Deeplink**を接続してください。
 
 {% tabs ローカル %}
-{% tab イメージ %}
-!["画像をカスタマイズするためのオプションを示すIAM Studio UI。これらの選択肢には、"画像、半径、および"画像が含まれます。]({% image_buster /assets/img/iam_studio/iam_customize_image.png %})
+{% tab 画像 %}
+![画像をカスタマイズするオプションが表示されている IAM Studio のUI。オプションには、画像、画像半径、淡色表示の画像がある。]({% image_buster /assets/img/iam_studio/iam_customize_image.png %})
 {% endtab %}
 {% tab テキスト %}
 ![メッセージのタイトルと字幕をカスタマイズするオプションを示すIAM Studio UI。これらのオプションには、テキスト、書式設定、およびフォントが含まれます。]({% image_buster /assets/img/iam_studio/iam_customize_text.png %})
 {% endtab %}
 {% tab ボタン %}
-![IAM Studio のUI には、メイン、左右のボタンをカスタマイズするオプションが表示されます。これらのオプションには、色、ディープリンク、テキスト、およびフォーマットが含まれます。]({% image_buster /assets/img/iam_studio/iam_customize_button.png %})
+![メインの左および右ボタンをカスタマイズするオプションが表示されている IAM Studio の UI。これらのオプションには、色、ディープリンク、テキスト、およびフォーマットが含まれます。]({% image_buster /assets/img/iam_studio/iam_customize_button.png %})
 {% endtab %}
 {% endtabs %}
 
-次に、カスタムフォントを追加し、リキッドタグs を使用してパーソナライズされた アプリ内メッセージを作成します。ログと"トラッキングを有効にするには、**ログデータを選択し、ユーザーの動作を追跡します**。
+次にカスタムフォントを追加し、Liquid タグを使用して、パーソナライズされたアプリ内メッセージを作成します。ログとトラッキングを有効にするには、\[**Log data and track user behavior**] を選択します。
 
 {% tabs ローカル %}
 {% tab フォント %}
-![IAM Studio のUI に、Liquid を追加するオプションが表示されます。これらの選択肢には、パーソナライズされた設定が含まれます。]({% image_buster /assets/img/iam_studio/iam_custom_font.png %})
+![Liquid を追加するオプションが表示されている IAM Studio のUI。これらの選択肢には、パーソナライズされた設定が含まれます。]({% image_buster /assets/img/iam_studio/iam_custom_font.png %})
 {% endtab %}
-{% tab 液体 %}
-![IAM Studio のUI には、イベント/属性のログ記録をカスタマイズするためのオプションが表示されます。これらのオプションには、ユーザー動作ログが含まれます。]({% image_buster /assets/img/iam_studio/iam_liquid.png %})
+{% tab Liquid %}
+![イベント/属性のロギングをカスタマイズするオプションが表示されている IAM Studio のUI。これらのオプションには、ユーザー動作ログが含まれます。]({% image_buster /assets/img/iam_studio/iam_liquid.png %})
 {% endtab %}
 {% tab ロギングとトラッキング %}
 ![フォントをカスタマイズするオプションを示すIAM Studio UI。これらのオプションには、ユーザーがフォントスタイルをカスタマイズできることが含まれます。]({% image_buster /assets/img/iam_studio/iam_tracking_logging.png  %})
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/knak.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/knak.md
index 56c3595c847..3147e45d354 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/knak.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/knak.md
@@ -1,6 +1,6 @@
 ---
-nav_title: ナック
-article_title: ナック
+nav_title: Knak
+article_title: Knak
 alias: /partners/knak/
 description: "この参考記事では、Brazeとキャンペーン作成プラットフォームであるKnakのパートナーシップについて概説している。Knakは、数日または数週間ではなく、数分または数時間で完全なレスポンシブメールを作成し、すぐに使えるBrazeテンプレートとしてエクスポートすることを可能にする。"
 page_type: partner
@@ -8,9 +8,9 @@ search_tag: Knak
 
 ---
 
-# ナック
+# Knak
 
-> [Knakは][1]、企業のマーケティングチームが社内で使用するために構築された初のキャンペーン作成プラットフォームである。ドラッグ・アンド・ドロップのプラットフォームは、コーディングや外部の手を借りることなく、誰でも数分で美しく、ブランドのあるEメールやランディングページを作成することができる。
+> [Knak][1] は、企業のマーケティングチームが社内で使用するために構築された、初のキャンペーン作成プラットフォームです。ドラッグ・アンド・ドロップのプラットフォームは、コーディングや外部の手を借りることなく、誰でも数分で美しく、ブランドのあるEメールやランディングページを作成することができる。
 
 BrazeとKnakの統合により、何日も何週間もかかることなく、数分から数時間で完全なレスポンシブメールを作成し、すぐに使えるBrazeテンプレートとしてエクスポートできる。Knakは、Brazeで管理するキャンペーンのメール作成をレベルアップしたいマーケティング担当者のために作られたもので、外部エージェンシーやハンドコーディングを必要としない。 
 
@@ -18,43 +18,43 @@ BrazeとKnakの統合により、何日も何週間もかかることなく、
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| クナックアカウント | このパートナーシップを利用するには、Knakアカウントが必要だ。 |
+| Knak アカウント | このパートナーシップを活用するには、Knak アカウントが必要です。 |
 | Braze REST API キー | 完全な**テンプレート**権限を持つBraze REST APIキー。<br><br>これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][2]。エンドポイントは、インスタンスのBraze URLに依存する。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
-Knakは、メール作成のレベルアップを望むマーケティング担当者のために開発された。こんな人には最適だ：
+Knak は、コーディングや外部からの支援を必要とせずに、メール作成をレベルアップしたいマーケターを対象に構築されました。こんな人には最適だ：
 - 現在、Eメールにシンプルなテンプレートを使用しているが、さらにレベルアップしたい
-- Braze用のEメールを外部の代理店や開発者に依存する
+- Braze のメールの作成を外部の組織や開発者に頼っている。
 - アセット制作のクリエイティブ・コントロールを取り戻し、市場投入までの時間を大幅に短縮したい。
 
 ## 統合
 
 ### ステップ1:統合を設定する
 
-Knakで、**Integrations > Platforms > + Add New Integrationに**移動する。
+Knak で **\[Integrations] > \[Platforms] > \[+ Add New Integration]** に移動します。
 
-![統合ボタンを追加する][5]
+![統合追加のボタン][5]
 
-次に、**Braze**プラットフォームを選択し、Braze APIキーとRESTエンドポイントを提供する。**Create New Integrationを**クリックして統合を完了する。 
+次に、**Braze**プラットフォームを選択し、Braze APIキーとRESTエンドポイントを提供する。\[**Create New Integration**] をクリックして統合を完了します。 
 
 ![新しい統合を作成する][6]
 
 ### ステップ2:Knakテンプレートを同期する
 
-Knakで、Brazeに同期したいEメールを探し、**Publish**、**Syncの**順に選択する。
+Knak で、Braze に同期するメールを見つけて \[**Publish**] を選択し、次に \[**Sync**] を選択します。
 
-![クナック統合 1][8]
+![Knak 統合1][8]
 
-次に、Eメール名を確認し、**同期を**クリックする。
+次にメール名を確認し、\[**Sync**] をクリックします。
 
-![クナック統合2][9]
+![Knak 統合2][9]
 
 ## 統合を利用する
 
-アップロードしたKnakのメールは、Brazeの**Engagement > Templates & Mediaで**確認できる。美しく、ブランドらしく、完全なレスポンシブである。唯一の限界は、あなた自身の創造力だ！
+アップロードした Knak メールは、Braze の**\[エンゲージメント] > \[テンプレートとメディア]** にあります。見た目がよく、ブランドらしく、完全にレスポンシブです。クリエイティビティを存分に発揮してください。
 
 [1]: https://knak.com/
 [2]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/sageflo.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/sageflo.md
index bc8e097a227..b3279c9667d 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/sageflo.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/sageflo.md
@@ -1,5 +1,5 @@
 ---
-nav_title: サゲフロ
+nav_title: Sageflo
 article_title: Sageflo Radiate
 description: "この参考記事では、BrazeとSagefloのパートナーシップについて概説している。Sagefloは分散型マーケティングツールで、BrazeとのAPI統合により、マーケティングで承認されたテンプレート、画像、オーディエンスセグメントを使用して、チームが独自のメールを簡単に送信できるようにする。"
 alias: /partners/sageflo/
@@ -10,15 +10,15 @@ search_tag: Partner
 
 # Sageflo Radiate
 
-> [Sageflo Radiateは](https://sageflo.com/radiate)分散型マーケティングツールで、BrazeとのAPI統合により、マーケティングが承認したテンプレート、画像、視聴者セグメントを使用して、ローカルチームが簡単に独自の電子メールを送信できるようになる。
+> [Sageflo Radiate](https://sageflo.com/radiate) は分散型マーケティングツールであり、Braze との API 統合により、ローカルチームがマーケティングで承認されたテンプレート、画像、およびオーディエンスセグメントを使用して独自のメールを簡単に送信できるようになります。
 
-オーディエンスのセグメンテーション、フリークエンシーガバナンス、ダイナミックコンテンツなど、Brazeの洗練された機能を活用しながら、ローカルチームがより賢くマーケティングを行うために必要なツールを提供する。 
+ローカルチームは、よりスマートなマーケティングの実施に必要なツールを利用でき、またブランドのガードレールを組み込む一方で Braze の高度な機能 (オーディエンスのセグメンテーション、頻度の制御、ダイナミックコンテンツなど) を活用できます。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| サゲフロ・ラジエイトのアカウント | このパートナーシップを利用するには、Sageflo Radiateアカウントが必要である。 |
+| Sageflo Radiate アカウント | このパートナーシップを活用するには、Sageflo Radiate アカウントが必要です。 |
 | Braze REST API キー | 完全な`templates` および`campaigns` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][1]。APIエンドポイントは、BrazeインスタンスのダッシュボードURLと一致する。<br><br> 例えば、ダッシュボードのURLが`https://dashboard-03.braze.com` の場合、エンドポイントは`dashboard-03` となる。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -28,15 +28,15 @@ search_tag: Partner
 Radiateは、Brazeを通じてローカルオーディエンスにEメールを送信する権限を分散チームに与えることで、マーケティング活動の規模を拡大したいと考えているフランチャイズや小売業に最適である。
 
 * 分散しているチームでも簡単にマーケティングEメールやSMSを送信できるようにする
-* 地域社会を重視した顧客とのつながりを築く
+* 地域に密着した顧客とのつながりを構築する
 * 内蔵ガードレールでブランドの一貫性を保つ
 * 国内マーケティングチームの負担を軽減する
 
 ## 統合
 
-Sagefloのアカウント・チームが統合の設定を担当する。BrazeのAPI認証情報を提供してもらい、Sagefloが御社のマーケティングチームと協力して、特定の場所や支店の視聴者セグメントを設定する。 
+Sageflo アカウントチームが統合の設定作業を主導します。Braze API の認証情報を入力するよう求められます。Sageflo はマーケティングチームと協力して、特定のロケーションとブランチのオーディエンスセグメントを設定します。 
 
-一旦接続されると、セージフロはそうする：
+接続が完了すると、Sageflo は次の作業を行います。
 
 * Radiate環境とBrazeへの接続をセットアップする。
 * Brazeでロケーションベースのオーディエンス・セグメントを設定する
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/smartersends.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/smartersends.md
index 83c7c3ddcca..75d8c000477 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/smartersends.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/smartersends.md
@@ -11,31 +11,31 @@ search_tag: Partner
 
 > [SmarterSendsは][2]、企業が作成、スケジュール、展開できるマーケティング・キャンペーンでパーソナライゼーションを推進し、使用するコンテンツやデータをコントロールしながら、ブランドや法的コンプライアンスを強化する。 
 
-BrazeとSmarterSendsのパートナーシップにより、Brazeのパワーと分散したユーザーが所有するハイパーローカライズされたコンテンツを組み合わせることができ、マーケティングキャンペーンを向上させることができる。
+Braze と SmarterSends のパートナーシップにより、Braze の機能と、分散ユーザーが所有するハイパーローカライズされたコンテンツを組み合わせて、マーケティングキャンペーンを強化できます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | --- | --- |
-| SmarterSendsアカウント | このパートナーシップを利用するには、[SmarterSendsのアカウントが][2]必要である。 |
+| SmarterSendsアカウント | このパートナーシップを活用するには、[SmarterSends アカウント][2]が必要です。 |
 | Braze REST API キー | これらの権限を持つBraze REST APIキー： {::nomarkdown}<ul><li><code>users.track</code></li><li><code>users.export.ids</code></li><li><code>messages.schedule.create</code></li><li><code>messages.schedule.update</code></li> <li><code>messages.schedule.delete</code></li><li><code>sends.id.create</code></li><li><code>segments.list</code></li><li><code>segments.data_series</code></li><li><code>segments.details</code></li><li><code>sends.data_series</code></li></ul>{:/} これは、Brazeダッシュボードの**「設定**」>「**APIキー**」から作成できる。さらなるセキュリティのために、SmarterSendsのIPアドレス（インスタンスで利用可能）を許可リストに入れる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][1]。エンドポイントは、インスタンスのBraze URLに依存する。 |
-| Braze APIキャンペーンID | [Braze APIキャンペーンIDは]({{site.baseurl}}/api/api_campaigns/)、SmarterSendsを通じて送信されるすべてのキャンペーンの一意の識別子である。これはBrazeダッシュボードの**Messaging**>**Campaignsで**作成できる。 |
+| Braze APIキャンペーンID | [Braze API キャンペーン ID]({{site.baseurl}}/api/api_campaigns/) は、SmarterSends を介して送信されるすべてのキャンペーンの一意の識別子です。これは Braze ダッシュボードの \[**メッセージング**] > \[**キャンペーン**] で作成できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、**Developer Console**>**API Settingsで**APIキーを作成できる。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**開発者コンソール**] > \[**API 設定**] で API キーを作成できます。
 {% endalert %}
 
 ## ユースケース
 
-BrazeとSmarterSendsの統合により、複数のチャネルや場所にまたがるマーケティングキャンペーンを作成・実行することで、分散型マーケティングを活用することができる。これらの利点には以下が含まれる：
+BrazeとSmarterSendsの統合により、複数のチャネルや場所にまたがるマーケティングキャンペーンを作成・実行することで、分散型マーケティングを活用することができる。これには次のようなメリットがあります。
 
-1. **リーチの拡大：**複数のチャネルや場所を利用することで、より幅広いオーディエンスにリーチし、さまざまな場所にいる顧客をターゲットにすることで、ブランドの露出を増やす。
-2. **ターゲットを絞ったメッセージング：**顧客とのより効果的なコミュニケーションとエンゲージメントを実現するため、地域のオーディエンスに響くよう、チャネルや場所を超えてメッセージングを調整する。 
-3. **ブランドの一貫性が向上した：**ブランドメッセージとイメージをすべてのチャネルと場所で統一することは、強力で認知度の高いブランドを構築するために重要である。
-4. **より優れた洞察力**さまざまなチャネルや場所からデータを収集し、顧客の行動や嗜好に関する貴重な洞察を提供することで、地域レベルでもグローバルレベルでも、マーケティング戦略や戦術を洗練させることができる。
-5. **効率が向上した：**異なるチャネルやロケーションの強みを活用することで、望ましいマーケティング目標を達成しつつ、より効率的にリソースを活用することができる。 
+1. **リーチの拡大:**複数のチャネルや場所を利用することで、より幅広いオーディエンスにリーチし、さまざまな場所にいる顧客をターゲットにすることで、ブランドの露出を増やす。
+2. **ターゲットを絞ったメッセージング:**顧客とのより効果的なコミュニケーションとエンゲージメントを実現するため、地域のオーディエンスに響くよう、チャネルや場所を超えてメッセージングを調整する。 
+3. **ブランドの一貫性の向上:**ブランドのメッセージとイメージをすべてのチャネルと場所で統一します。これは、強力で認識しやすいブランドを構築するうえで重要です。
+4. **より優れたインサイト:**さまざまなチャネルや場所からデータを収集し、顧客の行動や嗜好に関する貴重なインサイトを提供します。このインサイトは、ローカルレベルとグローバルレベルの両方でマーケティング戦略や戦術を洗練させるために利用できます。
+5. **効率性の向上:**異なるチャネルや場所の強みを活用します。その結果、マーケティング目標を達成し、リソースをより効率的に活用できるようになります。 
 
 ## 統合
 
@@ -55,24 +55,24 @@ BrazeとSmarterSendsの統合により、複数のチャネルや場所にまた
 - `segments.details`
 - `sends.data_series`
 4. SmarterSendsのIPアドレスを**Whislist IPs**セクションに追加する。
-5. **Save API Keyを**クリックする。
+5. \[**API キーを保存**] をクリックします。
 6. SmarterSendsの**Braze Email Service Provider**設定に、適切なパーミッションを持つAPIキーをコピー＆ペーストする。
 
 ### ステップ2:アプリケーションIDを作成またはコピーする
 
-1. Brazeのワークスペースで、**Settings**>**App Settingsに**進む。 
-2. 新しいアプリケーションをセットアップするか、ワークスペース内の既存のアプリケーションのアプリケーションIDを使用する。アプリケーションIDが**APIキーと**表示されていることに注意。 
+1. Braze ワークスペースで、\[**設定**] > \[**アプリ設定**] に移動します。 
+2. 新しいアプリケーションをセットアップするか、ワークスペース内の既存のアプリケーションのアプリケーションIDを使用する。アプリケーション ID に **API キー**というラベルが付いていることに注意してください。 
 3. このIDをコピーしてSmarterSendsの**App ID**フィールドに貼り付ける。
 
 ### ステップ3:APIキャンペーンを作成する
 
 APIキャンペーンは、Braze内のすべてのSmarterSendsメールのメトリクスを追跡し、SmarterSendsがこれらのAPIベースのキャンペーンをトリガーできるようにする。
 
-1. Brazeで[APIキャンペーンを作成]({{site.baseurl}}/api/api_campaigns/#create-a-new-campaign)する。
+1. Braze で [API キャンペーンを作成]({{site.baseurl}}/api/api_campaigns/#create-a-new-campaign)します。
 2. **Select Message Channel**」の下にある「**Email**」をクリックし、メトリクスのトラッキングを開始するメッセージング・チャンネルを追加する。
 3. 次に、BrazeのキャンペーンIDをSmarterSendsの**キャンペーンID**フィールドにコピー＆ペーストする。 
 4. BrazeのメッセージバリエーションIDをSmarterSendsの**メッセージバリエーションID**フィールドにコピー＆ペーストする。SmarterSendsでグループごとにメッセージIDを作成しない場合、これがデフォルトのメッセージIDとなる。
-5. SmarterSendsで作成したグループごとに、BrazeのAPIキャンペーンにメッセージのバリアントを追加する。次に、メッセージバリアントIDをSmarterSendsのグループのメッセージバリアントIDにコピーする。
+5. SmarterSendsで作成したグループごとに、BrazeのAPIキャンペーンにメッセージのバリアントを追加する。次に、SmarterSends でこのメッセージバリアント ID をグループのメッセージバリアント ID にコピーします。
 
 {% alert tip %}
 SmarterSendsで作成したグループごとにメッセージバリアントIDを作成し、Brazeのワークスペースで各グループの送信のメトリクスを個別に表示する。これは、Brazeでレポートを作成する際に、グループ間の傾向を特定するのに役立つ。
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/stensul.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/stensul.md
index d182cf6a07b..430a20dc855 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/stensul.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/stensul.md
@@ -2,7 +2,7 @@
 nav_title: Stensul
 article_title: Stensul
 alias: /partners/stensul
-description: "このリファレンス記事では、Braze とStensul の連携について概説します。これは、チャネル s 間でモバイルレスポンシブ メール テンプレートを簡単に作成できるエンタープライズメール プラットフォームです。"
+description: "このリファレンス記事では、Braze と Stensul のパートナーシップについて説明します。Stensul は、チャネル間でモバイル対応メールテンプレートを簡単に作成できるエンタープライズメールプラットフォームです。"
 page_type: partner
 search_tag: Partner
 
@@ -10,44 +10,44 @@ search_tag: Partner
 
 # Stensul
 
-> [Stensul](https://stensul.com/) は、メール マーケター s がStensul で簡単にモバイルレスポンシブのオンブランドメールを構築できるようにします。その後、リアルタイムでBraze に送信し、キャンペーンを作成します。
+> [Stensul](https://stensul.com/) では、メールマーケターがキャンペーン作成のためにリアルタイムで Braze にメールをダウンストリーム送信する前に、ブランドらしさのあるモバイル対応のメールを簡単に作成できます。
 
-BrazeとStensulインテグレーションを使用すると、Braze内でHTML形式のStensul メールsをエクスポートし、テンプレートsとしてアップロードできます。
+Braze と Stensul の統合により、HTML 形式の Stensul メールをエクスポートし、Braze 内でテンプレートとしてアップロードできます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ------------| ----------- |
-| Stensul勘定 | この提携の前進タグeを考慮するには、Stensulな考慮が必要である。 |
+| Stensul アカウント | このパートナーシップを活用するには、Stensul アカウントが必要です。 |
 | Braze REST API キー | 完全な**テンプレート**権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
-| クラスタインスタンス | Braze[cluster instance]({{site.baseurl}}/api/basics/#endpoints) は、Braze ダッシュボードとREST エンドポイントに合わせます。  |
+| クラスタインスタンス | Braze [クラスターインスタンス]({{site.baseurl}}/api/basics/#endpoints)は、Braze ダッシュボードと REST エンドポイントに対応しています。  |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合
 
-Braze REST API キーとクラスターインスタンスをStensul カスタマーサクセスチームに提供します。チームは、最初の統合を設定します。
+Braze REST API キーとクラスターインスタンスをStensul カスタマーサクセスチームに提供します。その後、このチームが初期統合を設定できます。
 
 {% alert important %}
 これは1 回限りの設定であり、今後のエクスポートではこのAPI キーが自動的に使用されます。
 {% endalert %}
 
-### ステップ1:Stensul メールの作成
+### ステップ1:Stensul メールを作成する
 
-Stensul プラットフォームにStensul メールを作成し、**Complete**を押します。
+Stensul プラットフォームで Stensul メールを作成し、\[**Complete**] をクリックします。
 
-![Stensul保存オプション]({% image_buster /assets/img_archive/stensul_save_options.png %})
+![Stensul の保存オプション]({% image_buster /assets/img_archive/stensul_save_options.png %})
 
 ### ステップ2:Brazeへのテンプレートのエクスポート
-アプリが完了ページで耳にする新しいダイアログで、<サービスプロバイダー an id="1">Up 読み込む to メールサービスプロバイダー (ESP)</サービスプロバイダー an> を選択します。
+完了ページに表示される新しいダイアログで、\[**Upload to ESP**] を選択します。
 
-![Stensulアップ読み込むオプション]({% image_buster /assets/img_archive/stensul_upload_options.png %})
+![Stensul のアップロードオプション]({% image_buster /assets/img_archive/stensul_upload_options.png %})
 
-次に、メールの ** テンプレート name**、**subject**、および **preヘッダー** を入力し、**Up読み込む** を選択します。アプリに応じて、アップロードが成功したかどうかの確認と、以前のアップロードの履歴が表示されます。
+次に、メールの ** テンプレート name**、**subject**、および **preヘッダー** を入力し、**Up読み込む** を選択します。アップロードが成功したことを示す確認と、該当する場合はファイルの過去のアップロード履歴が表示されます。
 
-![Stensulアップ読み込む成功]({% image_buster /assets/img_archive/stensul_upload_success.png %})
+![Stensul アップロード成功]({% image_buster /assets/img_archive/stensul_upload_success.png %})
 
 ## 使用
 
-Braze アカウントの ** テンプレート s& Media > E メールテンプレート s** セクションで、アップロードのStensul テンプレートを見つけます。これで、このメール テンプレートを使用してメールを顧客 s に送信できるようになりました。
+アップロードした Stensul テンプレートを、Braze アカウントの**\[テンプレートとメディア] > \[メールテンプレート]** セクションで確認します。これで、このメールテンプレートを使用して、顧客に魅力的なメールメッセージを送信できます。
 
 [1]: {{site.baseurl}}/user_guide/message_building_by_channel/email/creating_an_email_template/
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/stripo.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/stripo.md
index 41c98ad24bb..b28b803067e 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/stripo.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/stripo.md
@@ -18,26 +18,26 @@ BrazeとStripoの統合により、カスタマイズしたStripoメールをエ
 
 | 必要条件 | 説明 |
 | ------------| ----------- |
-| ストリップアカウント | このパートナーシップを利用するには、Stripoアカウントが必要である。 |
+| Stripo アカウント | このパートナーシップを利用するには、Stripoアカウントが必要である。 |
 | Braze REST API キー | 完全な**テンプレート**権限を持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| クラスターインスタンス | Braze[クラスタインスタンスは]({{site.baseurl}}/api/basics/#endpoints)、BrazeダッシュボードとRESTエンドポイントに合わせる。  |
+| クラスターインスタンス | Braze [クラスターインスタンス]({{site.baseurl}}/api/basics/#endpoints)は、Braze ダッシュボードと REST エンドポイントに対応しています。  |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 統合
 
 ### ステップ1:StripoのEメールを作成する
 
-StripoプラットフォームでStripoメールを作成し、**エクスポートを**クリックする。 
+Stripo プラットフォームで Stripo メールを作成し、\[**Export**] をクリックします。 
 
-![ストリポ・エクスポート]({% image_buster /assets/img_archive/stripo_export.png %})
+![Stripo エクスポート]({% image_buster /assets/img_archive/stripo_export.png %})
 
 ### ステップ2:テンプレートをBrazeにエクスポートする
 
-表示されるダイアログで、輸出方法として**Brazeを**選択する。 
+表示されるダイアログで、エクスポート方法として \[**Braze**] を選択します。 
 
-次に、**アカウント名**（ワークスペース名など）、**APIキー**、**クラスタ・インスタンスを**入力する。
+次に、**アカウント名** (ワークスペース名など)、**API キー**、**クラスタインスタンス**を入力します。
 
-![ストリポ・フォーム]({% image_buster /assets/img_archive/stripo_form.png %})
+![Stripo Form]({% image_buster /assets/img_archive/stripo_form.png %})
 
 {% alert important %}
 これは1回限りのセットアップであり、今後のエクスポートは自動的にこのAPIキーを利用することになる。
@@ -45,6 +45,6 @@ StripoプラットフォームでStripoメールを作成し、**エクスポー
 
 ## 使用
 
-アップロードしたStripoテンプレートをBrazeアカウントの**Templates & Media > Email Templates**セクションから探す。このテンプレートを使って、顧客に魅力的なメールを送ることができる！
+アップロードしたStripoテンプレートをBrazeアカウントの**Templates & Media > Email Templates**セクションから探す。これで、このメールテンプレートを使用して、顧客に魅力的なメールメッセージを送信できます。
 
 [1]: {{site.baseurl}}/user_guide/message_building_by_channel/email/creating_an_email_template/
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/taxi_for_email.md b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/taxi_for_email.md
index 40caf115810..9605b7f44be 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/taxi_for_email.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/email_templates/taxi_for_email.md
@@ -1,16 +1,16 @@
 ---
-nav_title: Eメール用タクシー
-article_title: Eメール用タクシー
+nav_title: Taxi for Email
+article_title: Taxi for Email
 alias: /partners/taxi_for_email
-description: "ここでは、Braze 顧客がドラッグアンドドロップインターフェイスとシンプルでパワフルなシンタックスを使用してインテリジェントなメール テンプレートを作成できるオンラインメール マーケティングツールである、メールのためのBrazeとタクシーの提携について概説します。"
+description: "このリファレンス記事では、Braze と Taxi for Email のパートナーシップについて説明します。Taxi for Email は、Braze のお客様がドラッグアンドドロップインターフェイスとシンプルで強力な構文を使用してインテリジェントなメールテンプレートを作成できるオンラインメールマーケティングツールです。"
 page_type: partner
 search_tag: Partner
 
 ---
 
-# Eメール用タクシー
+# Taxi for Email
 
-> [メール用タクシー](http://taxiforemail.com/)は、直感的なドラッグアンドドロップビジュアルメールエディタを提供するオンラインメール マーケティングツールです。タクシーは、チームがメール キャンペーンsで簡単にコラボレーションすることを奨励し、コピーライターや編集者がメールsを構築するために必要な情報や情報をコードなく入手できるようにします。
+> [メール用タクシー](http://taxiforemail.com/)は、直感的なドラッグアンドドロップビジュアルメールエディタを提供するオンラインメール マーケティングツールです。Taxi は、チームがメールキャンペーンで容易にコラボレーションできるようにし、コピーライターや編集者が、メールを作成するために必要なリソースとアクセスを、すべてコードなしで利用できるようにします。
 
 Brazeとタクシーの融合は、タクシーのシンプルでパワフルなシンタックスを活用して、Brazeにインテリジェントなメール テンプレートを作成してエクスポートします。 
 
@@ -18,7 +18,7 @@ Brazeとタクシーの融合は、タクシーのシンプルでパワフルな
 
 | 要件 | 説明 |
 | ------------| ----------- |
-| Eメールアカウントのタクシー | この提携の前進タグeをとるためには、電子メールのためのタクシーが必要である。 |
+| Taxi for Email アカウント | このパートナーシップを活用するには、Taxi for Email アカウントが必要です。 |
 | Braze REST API キー | 完全な**テンプレート**権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
 | Braze エンドポイント | [あなたのBraze エンドポイント]({{site.baseurl}}/api/basics/#endpoints)はあなたのBraze ダッシュボード URLに合わせます。<br><br> たとえば、ダッシュボード URL が`https://dashboard-03.braze.com` の場合、エンドポイントは`dashboard-03` になります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
@@ -27,7 +27,7 @@ Brazeとタクシーの融合は、タクシーのシンプルでパワフルな
 
 ### ステップ1:タクシーメール テンプレートの作成
 
-タクシープラットフォームにタクシーテンプレートを作成します。テンプレートが作成されたら、<サービスプロバイダー an id="1">組織設定</サービスプロバイダーan> に移動し、<サービスプロバイダー an id="2">メールサービスプロバイダー (ESP) Connectors</サービスプロバイダー an> タブを選択します。
+Taxi プラットフォームで Taxi テンプレートを作成します。テンプレートが作成されたら、\[**Organization Settings**] に移動して \[**ESP Connectors**] タブを選択します。
 
 ### ステップ2:Brazeコネクターの作成
 
@@ -35,10 +35,10 @@ Brazeとタクシーの融合は、タクシーのシンプルでパワフルな
 2. **Braze**を押して、Brazeコネクターの設定を変更します。
 3. Braze エンドポイントとBraze API キーを入力します。
 
-コネクターフィールドは、正しい権限が与えられた後にカラーを変更します。このフィールドが変わらない場合は、フィールドがリストされている条件に合っていることを確認します。
+正しい権限を含む詳細が指定された後に、コネクターフィールドの色が変わります。このフィールドが変わらない場合は、フィールドがリストされている条件に合っていることを確認します。
 
 ## 使用
 
-アップロード Taxi テンプレートを、Braze アカウントの** テンプレート s & amp; Media > E メールテンプレートs** セクションで見つけます。これで、このメール テンプレートを使用してメールを顧客 s に送信できるようになりました。
+Braze アカウントの **\[テンプレートとメディア] > \[メールテンプレート]** セクションで、アップロードされた Taxi テンプレートを確認します。これで、このメールテンプレートを使用して、顧客に魅力的なメールメッセージを送信できます。
 
 [1]: {{site.baseurl}}/user_guide/message_building_by_channel/email/creating_an_email_template/
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty.md
index dd79ae76069..01784637540 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty.md
@@ -1,6 +1,6 @@
 ---
 nav_title: ロイヤルティ
-article_title: ロイヤルティパートナーズ
+article_title: ロイヤルティのパートナー
 page_order: 3
 
 page_type: landing
@@ -14,7 +14,7 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Loyalty"
 
 valid_partner_list:
-- name: アンタボ
+- name: Antavo
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/antavo/
 - name: Talon.One
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/talonone/
@@ -24,11 +24,11 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/jebbit/
 - name: Punchh
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/punchh/
-- name: エクソール
+- name: Extole
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/extole/
 - name: ViralSweep
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/viralsweep/  
-- name: ニフト
+- name: Nift
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/nift/
 - name: Kognitiv
   url: /docs/partners/message_orchestration/channel_extensions/loyalty/kognitiv/
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/antavo.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/antavo.md
index 43241537495..9c03a190c95 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/antavo.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/antavo.md
@@ -1,43 +1,43 @@
 ---
-nav_title: アンタボ
-article_title: アンタボ・ロイヤリティ・クラウド
-description: "この参考記事では、BrazeとAntavoのパートナーシップについて概説している。"
+nav_title: Antavo
+article_title: Antavo Loyalty Cloud
+description: "このリファレンス記事では、Braze と Antavo のパートナーシップについて説明します。Antavo は、特典付きの購入からさらに進んだ次世代ロイヤルティプログラムです。"
 alias: /partners/antavo/
 page_type: partner
 search_tag: Partner
 ---
 
-# アンタボ・ロイヤリティ・クラウド
+# Antavo Loyalty Cloud
 
 > [Antavo](https://antavo.com/)社は、包括的なロイヤリティ・プログラムを構築し、ブランド愛を育み、顧客の行動を変える、エンタープライズ・グレードのSaaS型ロイヤリティ・テクノロジー・プロバイダーである。
 
-AntavoとBrazeの統合により、ロイヤルティプログラム関連データを利用してパーソナライズされたキャンペーンを構築し、顧客体験を向上させることができる。これはAntavoからBrazeへの一方向のデータ同期のみである。この統合は、`external_id` Brazeフィールドをサポートしている。このフィールドは、Antavoがロイヤルティ会員IDを同期するフィールドである。
+AntavoとBrazeの統合により、ロイヤルティプログラム関連データを利用してパーソナライズされたキャンペーンを構築し、顧客体験を向上させることができる。Antavo では、2つのプラットフォーム間のロイヤルティデータ同期 (Antavo から Braze への一方向データ同期のみ) がサポートされています。この統合は、`external_id` Brazeフィールドをサポートしている。このフィールドは、Antavoがロイヤルティ会員IDを同期するフィールドである。
 
 ## 前提条件
 
-| 必要条件          | 説明                                                                                                                                                                   |
+| 要件          | 説明                                                                                                                                                                   |
 | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------  |
-| アンタボアカウント       | このパートナーシップを利用するには、Brazeとの統合を有効にした[Antavo](https://antavo.com/)アカウントが必要である。                                                |
-| Braze REST API キー   | `users.track` 権限を持つ Braze REST API キー。<br><br>Brazeダッシュボードで新しいAPIキーを作成するには、**Settings**>**API Keysに**進み、**Create New API Keyを**クリックする。  |
+| Antavo アカウント       | このパートナーシップを利用するには、Brazeとの統合を有効にした[Antavo](https://antavo.com/)アカウントが必要である。                                                |
+| Braze REST API キー   | `users.track` 権限を持つ Braze REST API キー。<br><br>Braze ダッシュボードで新しい API キーを作成するには、\[**設定**] >\[**API キー**] に移動し、\[**新しい API キーを作成**] をクリックします。  |
 | Braze RESTエンドポイント  | [RESTエンドポイントのURL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)。エンドポイントは、インスタンスのBraze URLに依存する。                |
-| Brazeアプリの識別子 | アプリの識別子が鍵だ。<br><br>Brazeダッシュボードでこのキーを見つけるには、**設定** **>APIキーと**進み、**識別**セクションを見つける。 |
+| Brazeアプリの識別子 | アプリ識別子キー。<br><br>Braze ダッシュボードでこのキーを確認するには、\[**設定**] > \[**API キー**] に進み、\[**識別**] セクションを確認します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### ステップ1:アンタヴォでブレーズをつなぐ
+### ステップ1:Antavo で Braze に接続する
 
-Antavoで、**Modules**>**Brazeに**進み、**Configureを**クリックする。AntavoのBraze統合設定ページに最初に移動すると、2つのシステムを接続するようインターフェイスが促す。
+Antavo で \[**Modules**] > \[**Braze**] に移動し、\[**Configure**] をクリックします。Antavo の Braze 統合設定ページに初めて移動すると、2つのシステムを接続するように促されます。
 
-以下の証明書を提出すること：
+以下の認証情報を指定します。
 
-- **インスタンスのURL：**プロビジョニング先のインスタンスのBraze RESTエンドポイント。
+- **Instance URL:**プロビジョニング先のインスタンスのBraze RESTエンドポイント。
 - **APIトークン（識別子）：**AntavoがBrazeにリクエストを送信する際に使用するBraze REST APIキー。
-- **アプリ識別子：**Brazeアプリの識別子。
+- **App Identifier:**Brazeアプリの識別子。
 
-認証情報を入力したら、**Connectを**クリックする。
+認証情報を入力したら、\[**Connect**] をクリックします。
 
-![インスタンスURL、APIトークン、アプリ識別子でAntavoのBraze画面を接続する。][1]
+![「Instance URL」、「API Token」、「App Identifier」が表示されている Antavo の「Connect Braze」画面。][1]
 
 ### ステップ2:フィールドマッピングを設定する
 
@@ -45,9 +45,9 @@ Antavoで、**Modules**>**Brazeに**進み、**Configureを**クリックする
 
 Antavoでフィールドマッピングを設定する：
 
-1. **Add new field** <i class="fas fa-plus" alt=""></i> をクリックする。
-2. ドロップダウンフィールドを使用して、Brazeに同期させたいAntavo**Loyaltyフィールドを**選択する。
-3. データを入力するBrazeのカスタム属性に相当する**リモートフィールドを**入力する。  
+1. \[**Add new field**] をクリックします<i class="fas fa-plus" alt=""></i>。
+2. ドロップダウンフィールドを使用して、Braze に同期する Antavo の**ロイヤルティフィールド**を選択します。
+3. データの取り込み先となる Braze の対応するカスタム属性を表す**リモートフィールド**を入力します。  
 
 {% alert note %}
 カスタム属性のリストは、Brazeの「**データ設定**」＞「**カスタム属性**」で確認できる。入力したフィールドがBrazeで定義されていない場合、最初の同期で新しいフィールドが自動的に生成される。
@@ -55,12 +55,12 @@ Antavoでフィールドマッピングを設定する：
 
 {:start="4"}
 4\.フィールドの組み合わせを追加するには、ステップ1〜3を繰り返す。
-5. 同期データのリストからフィールドを削除するには <i class="fa-solid fa-rectangle-xmark" title="をクリックする。"></i>をクリックする。
+5. 同期されるデータのリストからフィールドを削除するには、行の終わりにある <i class="fa-solid fa-rectangle-xmark" title="Delete"></i> をクリックします。
 6. \[**保存**] をクリックします。
 
 Antavoで設定されたフィールドのいずれかの値が変更されると、その単一の値の同期がトリガーされるだけでなく、フィールドマッピングに追加されたすべてのフィールドがリクエストに含まれる。
 
-![AntavoのSync Fieldsページ。][2]
+![Antavo の「Sync Fields」ページ。][2]
 
 {% alert important %}
 データポイントの消費を最小限に抑えるため、Braze内でアクションを起こすフィールドのみをマッピングすることを推奨する。
@@ -68,27 +68,27 @@ Antavoで設定されたフィールドのいずれかの値が変更される
 
 #### サポートされるデータ型
 
-つまり、数値（整数、浮動小数点）、文字列、配列、ブーリアン、オブジェクト、オブジェクトの配列、日付[で]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#custom-attribute-storage)ある。
+この統合では、Braze のすべてのカスタム属性[データ型]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#custom-attribute-storage) (数値 (整数、浮動小数点)、文字列、配列、ブール値、オブジェクト、オブジェクト配列、日付) がサポートされています。
 
-![さまざまなカスタム属性を示すブレイズのプロフィール。][3]
+![さまざまなカスタム属性を示す Braze プロファイル。][3]
 
 データフィールドは、設定されたフィールドマッピングに基づいて入力される。
 
 ## トリガー
 
-フィールドマッピングの設定に加え、Antavoの[ワークフローツールに](https://antavo.atlassian.net/wiki/spaces/AUM/pages/581402629)組み込まれた機能により、統合はさらなる機能を提供する。すべてのBrazeカスタム属性[データタイプと]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#custom-attribute-storage) [カスタムイベントプロパティデータタイプは]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events#expected-format)、ワークフローを通しても同期できる。
+フィールドマッピングの設定に加え、Antavoの[ワークフローツールに](https://antavo.atlassian.net/wiki/spaces/AUM/pages/581402629)組み込まれた機能により、統合はさらなる機能を提供する。すべての Braze カスタム属性[データ型]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#custom-attribute-storage) とカスタムイベントプロパティ[データ型]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events#expected-format)も、ワークフローを介して同期できます。
 
-### ロイヤルティ・データを時々同期させる
+### ロイヤルティデータを随時同期する
 
-データがAntavoのロイヤリティフィールドに格納されていない場合、またはデータがマップされたフィールドリストに追加されていない場合は、このオプションを使用する。要求されたデータの同期は、設定されたワークフロー基準が満たされたときにトリガーされる。
+データがAntavoのロイヤリティフィールドに格納されていない場合、またはデータがマップされたフィールドリストに追加されていない場合は、このオプションを使用する。要求されたデータの同期は、設定されたワークフロー条件が満たされたときにトリガーされます。
 
-ステップ・バイ・ステップ・ガイドで、[前回の購入に関連するロイヤリティ・データの](https://antavo.atlassian.net/wiki/spaces/AUM/pages/812056598/Braze#Use-case----Sync-data-related-to-the-customer%E2%80%99s-last-purchase)同期を設定する方法を学ぶ。
+[最後の購入に関連するロイヤルティデータ](https://antavo.atlassian.net/wiki/spaces/AUM/pages/812056598/Braze#Use-case----Sync-data-related-to-the-customer%E2%80%99s-last-purchase)の同期を設定する方法については、ステップバイステップガイドを参照してください。
 
 ### ロイヤリティ・プログラムのイベントを同期させる
 
-Antavoから同期されたイベントを使用して、アクションベースのBraze Canvasesにロイヤルティ会員を入力する。この統合は、Brazeにカスタムイベントとして表示されるあらゆるAntavoイベント（購入イベントを含む）を同期することができる。
+Antavo から同期されたイベントを使用して、アクションベースの Braze キャンバスにロイヤルティメンバーを入力します。この統合は、Brazeにカスタムイベントとして表示されるあらゆるAntavoイベント（購入イベントを含む）を同期することができる。
 
-ステップ・バイ・ステップ・ガイドで、[ロイヤリティ・プログラム入会イベントの](https://antavo.atlassian.net/wiki/spaces/AUM/pages/812056598/Braze#Use-case----Welcome-to-the-loyalty-program!)同期と、[ロイヤリティ・プログラム特典獲得イベントの](https://antavo.atlassian.net/wiki/spaces/AUM/pages/812056598/Braze#Use-case----Welcome-to-the-loyalty-program!)同期の設定方法を学ぶ。
+[ロイヤルティプログラム登録イベント](https://antavo.atlassian.net/wiki/spaces/AUM/pages/812056598/Braze#Use-case----Welcome-to-the-loyalty-program!)の同期および[ロイヤルティプログラム特典獲得イベント](https://antavo.atlassian.net/wiki/spaces/AUM/pages/812056598/Braze#Use-case----Welcome-to-the-loyalty-program!)の同期の設定方法については、ステップバイステップガイドを参照してください。
 
 [1]: {% image_buster /assets/img/antavo/connect_braze.png %}
 [2]: {% image_buster /assets/img/antavo/data_field_mapping.png %}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/extole.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/extole.md
index f01a172ad0b..48f8fe7f457 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/extole.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/extole.md
@@ -1,83 +1,83 @@
 ---
-nav_title: エクストール
-article_title: エクストール
-description: "この記事では、Brazeとリファラルマーケティング企業のExtole社とのパートナーシップについて概説している。"
+nav_title: Extole
+article_title: Extole
+description: "この記事では、Braze Extole のパートナーシップにつて説明します。Extole はリファラルマーケティング企業であり、友人紹介プログラムと成長プログラムから顧客イベントと属性を取り込むことができるようにします。"
 alias: /partners/extole/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# エクストール
+# Extole
 
 > SaaS企業である[Extole](https://www.extole.com/)社は、友達紹介マーケティングの業界リーダーであり、顧客獲得を増やすための効果的な紹介マーケティング・プログラムの作成と最適化を支援している。
 
-BrazeとExtoleの統合により、Extoleの友達紹介プログラムや成長プログラムから顧客イベントや属性をBrazeに取り込むことができ、顧客獲得、エンゲージメント、ロイヤルティを高める、よりパーソナライズされたマーケティングキャンペーンを作成できるようになる。パーソナライズされた共有コードやリンクなど、Extoleのコンテンツ属性をBrazeのコミュニケーションに動的に取り込むこともできる。
+Braze と Extole の統合により、Extole の友人紹介プログラムや成長プログラムから顧客イベントや属性を Braze に取り込むことができ、顧客の獲得、エンゲージメント、ロイヤルティを高める、よりパーソナライズされたマーケティングキャンペーンを作成できるようになります。パーソナライズされた共有コードやリンクなど、Extoleのコンテンツ属性をBrazeのコミュニケーションに動的に取り込むこともできる。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| エクストール口座 | このパートナーシップを利用するには、Extoleアカウントが必要である。 |
+| Extole アカウント | このパートナーシップを活用するには、Extole アカウントが必要です。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。これは、Brazeダッシュボードの**「設定**」>「**APIキー**」から作成できる。 |
 | Braze API URL | あなたのBraze API URLは、あなたの[Brazeインスタンスに]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)固有である。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
-以下の使用例では、ExtoleとBrazeの統合を活用する方法をいくつか紹介している。Extoleのインプリメンテーション・マネージャーやカスタマー・サクセス・マネージャーと協力して、貴社固有のニーズに合ったオプションを開発する。
+以下の使用例では、ExtoleとBrazeの統合を活用する方法をいくつか紹介している。Extole の実装マネージャーおよびカスタマーサクセスマネージャーと協力して、お客様の自社固有のニーズに対応するオプションを開発します。
 
 - 紹介プログラムやエンゲージメントプログラムのカスタムイベントを活用して、BrazeのキャンペーンやCanvasをトリガーする。
 - Extoleを使用したプログラムのデータを使用して、カスタムセグメント、ダッシュボード、レポートを作成する。
-- Brazeでユーザーを自動的にマーケティングリストに登録または解除する
+- Braze でユーザーをマーケティングリストに自動的に登録または登録解除する
 
 ## 統合
 
-以下のステップを完了し、統合を素早く立ち上げ、実行する。Extoleのインプリメンテーション・マネージャーとカスタマー・サクセス・マネージャーがこのプロセスをサポートし、あらゆる質問にお答えする。
+統合を迅速に起動して実行するには、次の手順を実行します。Extole の実装およびカスタマーサクセスマネージャーがこのプロセスを支援し、ご質問に回答します。
 
 ### Brazeアカウントに接続する
 
 1. My Extoleアカウントの[パートナー](https://my.extole.com/partners)ページでBrazeインテグレーションを選択する。
-2. Brazeインテグレーションで、**Installを**選択してExtoleとBrazeの接続を開始する。
-3. Braze REST APIキーから必要事項を入力する。 
+2. Braze 統合で \[**インストール**] を選択し、Extole と Braze の接続を開始します。
+3. Braze REST API キーをはじめとする必須フィールドを入力します。 
 4. Braze API URLを入力する。このURLは、Brazeアカウントがどのインスタンスにプロビジョニングされているかによって異なる。
-5. Brazeに送信したいExtoleイベントを追加する。デフォルト・イベント、イベント・プロパティ、ユーザー属性は、[Extole Eventsの](https://dev.extole.com/docs/braze#extole-program-events)表に記載されている。
-6. `FULFILLED` の状態以外に、Brazeに送りたい報酬の状態を追加する。利用可能な報酬状態の説明については、[Extole Rewardsの表を](https://dev.extole.com/docs/braze#extole-rewards)参照のこと。
-7. Braze外部IDキーマッピングを選択する。これが、ExtoleがBrazeでユーザー・プロフィールを更新する方法だ。Brazeの外部IDキーをExtoleの`email_address` 、または`partner_user_id` 。より安全なので、`email_address` の代わりに`external_id` を使用することをお勧めする。
+5. Brazeに送信したいExtoleイベントを追加する。デフォルトのイベント、イベントプロパティ、およびユーザー属性は、[Extole イベントの表](https://dev.extole.com/docs/braze#extole-program-events)で説明されています。
+6. `FULFILLED` 状態以外に、Braze に送信するリワードの状態を追加します。利用可能なリワードの状態の説明については、[Extole リワードの表](https://dev.extole.com/docs/braze#extole-rewards)を参照してください。
+7. Braze外部IDキーマッピングを選択する。これが、ExtoleがBrazeでユーザー・プロフィールを更新する方法だ。Braze の external ID キーを Extole のユーザーの`email_address` または`partner_user_id` にマッピングできます。より安全なので、`email_address` の代わりに`external_id` を使用することをお勧めする。
 8. 設定を保存して接続を完了する。これで、ExtoleのイベントがBrazeのアカウントに流れるようになった。
 
-### エクストレイル・プログラムのイベント
+### Extole プログラムイベント
 
-以下は、ExtoleがBrazeに送信するデフォルトのイベント、イベントプロパティ、ユーザー属性である。Extoleのインプリメンテーション・マネージャーまたはカスタマー・サクセス・マネージャーに連絡して、Extoleイベントを特定し、統合に追加する。
+以下は、ExtoleがBrazeに送信するデフォルトのイベント、イベントプロパティ、ユーザー属性である。追加する Extole イベントを特定して統合に追加するには、Extole 実装またはカスタムサクセスマネージャーにご連絡ください。
 
 | イベント | 説明 | イベントプロパティ | ユーザー属性 |
 | ----------- | ----------- | ----------- | ----------- |
-| `extole_created_share_link` | 参加者は、Extole Share ExperienceにEメールを入力して、共有リンクを作成する。 | イベント名  <br>開催時間  <br>パートナー（エクストール）  <br>ファネル（支持者または友人）  <br>プログラム | <br>external ID <br>メール  <br>リンクを共有する |
-| `extole_shared` | 参加者が自分の紹介リンクを友人にシェアする。 | イベント名  <br>開催時間  <br>パートナー（エクストール）  <br>external ID  <br>ファネル（支持者または友人）  <br>プログラム  <br>シェアチャンネル | メール <br>名 <br>姓 |
-| `outcome` - 結果は、プログラムのコンフィギュレーション（`extole_shipped` や`extole_converted` など）に基づいてダイナミックに変化する。| 参加者が、プログラムに設定された望ましい成果イベントに転換または完了した。 | プログラムごとのダイナミック | メール <br>名 <br>姓 |
+| `extole_created_share_link` | 参加者は、Extole Share Experience にメールを入力して、共有リンクを作成します。 | イベント名  <br>イベント時間  <br>パートナー (Extole)  <br>ファンネル (アドボケイトまたは友人)  <br>プログラム | <br>external ID <br>メール  <br>リンクを共有する |
+| `extole_shared` | 参加者が自分の紹介リンクを友人にシェアする。 | イベント名  <br>イベント時間  <br>パートナー (Extole)  <br>external ID  <br>ファンネル (アドボケイトまたは友人)  <br>プログラム  <br>シェアチャンネル | メール <br>名 <br>姓 |
+| `outcome` - 結果は、プログラムのコンフィギュレーション（`extole_shipped` や`extole_converted` など）に基づいてダイナミックに変化する。| 参加者が、プログラムに設定されている目的の成果イベントをコンバージョンまたは完了た。 | プログラムごとのダイナミック | メール <br>名 <br>姓 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
-### エクストレイルの購読状態
+### Extole のサブスクリプション状態
 
 | サブスクリプションの状態 | 説明 | イベントプロパティ | ユーザー属性 |
 | ----------- | ----------- | ----------- | ----------- |
-| `subscribed` | 参加者がマーケティングメッセージの受信をオプトインした。 | 該当なし | メール  <br>リストタイプ  <br>external ID  <br>メール購読（オプトイン） |
-| `unsubscribed` | 参加者がExtoleからの電子メールによる連絡の受信を拒否した。| メール  <br>external ID  <br>購読状態（購読解除）  <br>購読グループID  | リストタイプ |
+| `subscribed` | 参加者がマーケティングメッセージの受信をオプトインした。 | 該当なし | メール  <br>リストのタイプ  <br>external ID  <br>メール購読 (オプトイン) |
+| `unsubscribed` | 参加者が Extole メールコミュニケーションの受信をオプトアウトした。| メール  <br>external ID  <br>サブスクリプション状態 (サブスクリプション解除)  <br>サブスクリプショングループ ID  | リストのタイプ |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
-### エクストレイルの報酬
+### Extrail のリワード
 
-デフォルトでは、Extoleは`FULFILLED` 状態の報酬イベントをBrazeに送信するので、BrazeキャンペーンまたはCanvasを介して報酬通知をトリガーできる。その他の報酬状態については、以下の表を参照のこと。
+デフォルトでは、Extoleは `FULFILLED` 状態のリワードイベントを Braze に送信します。このため、Braze キャンペーンまたはキャンバスを通じてリワード通知をトリガーできます。その他のリワード状態については、以下の表を参照してください。
 
-| 報酬国 | 説明 | イベントプロパティ | ユーザー属性 |
+| リワード状態 | 説明 | イベントプロパティ | ユーザー属性 |
 | ----------- | ----------- | ----------- | ----------- |
-| `FULFILLED` | デフォルトの状態である。報酬は、Extole報酬サプライヤーによって価値（クーポンやギフトカードなど）が割り当てられている。 | メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
-| `EARNED` | 報酬が作成され、その人物に関連付けられた。 | メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
-| `SENT` | 報酬は達成され、電子メールまたはデバイスで受取人に送信された。 | メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
-| `REDEEMED` | 報酬は、Extoleに送信されたコンバージョンまたは償還イベントで証明されるように、受領者によって使用された。| メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
-| `FAILED` | 問題が発生したため、報酬の発行または送付ができず、注意が必要である。 | メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
-| `CANCELED` | 報酬は無効化され、インベントリに戻る。 | メール <br>額面  <br>額面タイプ  | メール <br>名  <br>姓 |
-| `REVOKED` | 達成された報酬は無効となった。例えば、Extole社はサプライヤーにギフトカードを要求したが、そのカードが誤って送られてきたと判断した。サプライヤーが報酬の取り消しを支持した場合、Extoleは資金の払い戻しを要求し、報酬は無効となる。 | メール <br>額面   <br>額面タイプ  | メール <br>名  <br>姓 |
+| `FULFILLED` | デフォルトの状態。リワードには、Extole リワードサプライヤーによって価値 (クーポンやギフトカードなど)が割り当てられています。 | メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
+| `EARNED` | リワードが作成され、人物に関連付けられています。 | メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
+| `SENT` | リワードが履行され、受領者にメールまたはデバイスで送信されました。 | メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
+| `REDEEMED` | リワードは、Extole に送信されたコンバージョンイベントまたは引き換えイベントで証明されているように受領者によって使用されています。| メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
+| `FAILED` | 問題が発生したため、リワードを発行または送付できませんでした。注意する必要があります。 | メール <br>額面  <br>クーポンコード  <br>額面タイプ  | メール <br>名  <br>姓 |
+| `CANCELED` | リワードは無効化されました。インベントリに戻されます。 | メール <br>額面  <br>額面タイプ  | メール <br>名  <br>姓 |
+| `REVOKED` | 履行されたリワードが無効化されました。たとえば、Extole がサプライヤーギフトカードを依頼したが、カードが誤って送付されたと判断した場合などです。サプライヤーがリワードの取り消しに対応している場合、Extole は資金の払い戻しを依頼し、リワードは無効になります。 | メール <br>額面   <br>額面タイプ  | メール <br>名  <br>姓 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 
@@ -85,8 +85,8 @@ BrazeとExtoleの統合により、Extoleの友達紹介プログラムや成長
 
 ### Brazeでユーザーを検索し、作成する
 
-Extoleが外部ID（ユーザーID）を持っていない新規メールやSMS購読などの特定のユースケースでは、ExtoleはBraze[Export user profile by identifierエンドポイントを]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)使用してユーザーの識別子をチェックできる。ユーザーがBrazeに存在する場合、Extoleはプロフィール属性を追加・更新する。リクエストがユーザープロファイルを返さない場合、Extoleは`/users/track` エンドポイントを使用して、ユーザーのメールアドレスをエイリアス名とするユーザーエイリアスを作成する。
+Extole に external ID (ユーザー ID) がない新しいメールや SMS サブスクリプションなどの特定のユースケースでは、Extole は Braze の[識別子によるユーザープロファイルのエクスポートのエンドポイント]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)を使用して、ユーザーの ID を確認できます。ユーザーがBrazeに存在する場合、Extoleはプロフィール属性を追加・更新する。リクエストがユーザープロファイルを返さない場合、Extoleは`/users/track` エンドポイントを使用して、ユーザーのメールアドレスをエイリアス名とするユーザーエイリアスを作成する。
 
 ## この統合を使う
 
-アカウントを接続すると、何もしなくても自動的にExtoleからBrazeにイベントが流れ始める。Brazeに送信されるイベントのライブビューは、Extoleのトラブルシューティング用Outbound Webhook Centerで見ることができる。 
+アカウントを接続すると、何もしなくても自動的にExtoleからBrazeにイベントが流れ始める。Braze に送信されるイベントのライブビューは、Extole の Outbound Webhook Center でトラブルシューティングのために参照できます。 
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/friendbuy.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/friendbuy.md
index 024b6a90aa6..d9d475556f8 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/friendbuy.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/friendbuy.md
@@ -10,57 +10,57 @@ search_tag: Partner
 
 # Friendbuy
 
-> FriendbuyとBrazeの統合により、EメールやSMSの機能を拡張し、紹介やロイヤルティプログラムのコミュニケーションを簡単に自動化することができる。Brazeは、Friendbuyを通じて収集したオプトイン済みの電話番号の顧客プロファイルを作成する。
+> FriendbuyとBrazeの統合により、EメールやSMSの機能を拡張し、紹介やロイヤルティプログラムのコミュニケーションを簡単に自動化することができる。Braze では、Friendbuy 経由で収集されたすべてのオプトイン電話番号の顧客プロファイルが生成されます。
 
 ## 前提条件
 
-始める前に、以下のものが必要だ：
+開始する前に、次のものが必要になります。
 
 | 前提条件          | 説明                                                                                                                              |
 |-----------------------|------------------------------------------------------------------------------------------------------------------------------------------|
-| Friendbuyアカウント   | このパートナーシップを利用するには、[Friendbuyアカウントが][1]必要だ。                                                              |
+| Friendbuyアカウント   | このパートナーシップを活用するには、[Friendbuy アカウント][1]が必要です。                                                              |
 | Braze REST API キー  | `users.track` 権限を持つ Braze REST API キー。これは、Brazeダッシュボードの**「設定**」>「**APIキー**」から作成できる。        |
-| Braze RESTエンドポイント | [RESTエンドポイントURLは]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)、BrazeインスタンスのURLに依存する。 |
+| Braze RESTエンドポイント | [REST エンドポイント URL]({{site.baseurl}}/developer_guide/rest_api/basics/#endpoints)。これは Braze インスタンスの URL に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、**Developer Console**>**API Settingsで**APIキーを作成できる。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**開発者コンソール**] > \[**API 設定**] で API キーを作成できます。
 {% endalert %}
 
-## フレンドバイの統合
+## Friendbuy の統合
 
-[Friendbuyで][1] **Developer Center**>**Integrationsを**選択し、Brazeインテグレーションカードで**Add integrationを**選択する。
+[Friendbuy][1] で \[**Developer Center**] > \[**Integrations**] に移動し、Braze 統合カードで \[**Add integration**] を選択します。
 
-![フレンドバイのブレイズ統合カード。][100]{: style="max-width:75%;"}
+![Friendbuy の Braze 統合カード。][100]{: style="max-width:75%;"}
 
-フォームにRESTエンドポイントとAPIキーを入力し、**Install Integrationを**選択する。
+フォームに REST エンドポイントと API キーを入力し、\[**Install Integration**] を選択します。
 
-![Friendbuyの統合フォーム。][101]{: style="max-width:55%;"}
+![Friendbuy 統合フォーム。][101]{: style="max-width:55%;"}
 
-[Friendbuyアカウントに][1]戻り、ページを更新する。統合が成功すれば、以下のようなメッセージが表示される：
+[Friendbuy アカウント][1]に戻り、ページを更新します。統合が成功すれば、以下のようなメッセージが表示される：
 
-![統合をインストールした][102]{: style="max-width:55%;"}
+![統合がインストールされた][102]{: style="max-width:55%;"}
 
 ### カスタム属性
 
 | カスタム属性名            | 定義                                                                                                                                         | データ型 |
 |----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
-| **フレンドバイ紹介状況**    | 紹介者は「*Advocate」*、被紹介者は「*Referred Friend*」に分類される。                                                          | String    |
-| **フレンドバイカスタマー名**      | 顧客が紹介ウィジェットから情報を送信する際に入力した名前                                                                 | String    |
-| **フレンドバイ紹介リンク**      | アドボケイトのために生成された個人紹介リンク（PURL）。例えば、こうだ、 https://fbuy.io/EzcW                                                       | String    |
-| **フレンドシップ最終購入日** | アドボケイトが最後に共有チャネルを通じてフレンドと共有した日時。アドボケイトがまだシェアしていない場合、プロパティは表示されない。 | 時刻      |
-| **フレンド購入キャンペーンID**        | アドボケートのために生成された個人紹介リンクに関連するキャンペーンID                                                               | String    |
+| **Friendbuy Referral Status**    | 紹介者は *Advocate*、被紹介者は *Referred Friend* に分類されます。                                                          | String    |
+| **Friendbuy Customer Name**      | 顧客が紹介ウィジェットから情報を送信する際に入力した名前                                                                 | String    |
+| **Friendbuy Referral Link**      | Advocate に対して生成されるパーソナル紹介リンク (PURL)。例: https://fbuy.io/EzcW                                                       | String    |
+| **Friendbuy Date of Last Share** | 共有チャネルを通じて最後に Advocate が Friend と共有した時点の日時。Advocate がまだ共有していない場合、このプロパティはて表示されません。 | 時刻      |
+| **Friendbuy Campaign ID**        | アドボケートのために生成された個人紹介リンクに関連するキャンペーンID                                                               | String    |
 | **フレンドバイキャンペーン名**      | アドボケートのために生成された個人紹介リンクに関連するキャンペーン名                                                             | String    |
-| **Friendbuy クーポンコード**        | 顧客に配布された最新の紹介クーポンコード。注：表示されるコードは1つだけである。                                            | string    |
-| **フレンドバイクーポン**       | 顧客に配布された最新のクーポンコードの通貨価値。                                                                     | 数値    |
-| **Friendbuyクーポンステータス**      | 顧客に配布された最新のクーポンコードのステータス。注：ステータスは「分配」または「償還」となる。                            | string    |
-| **Friendbuyクーポン**    | 顧客に配布された最新のクーポンコードに関連する通貨コード（USD、CADなど）またはパーセント（%）。                             | String    |
+| **Friendbuy クーポンコード**        | 顧客に配布された最新の紹介クーポンコード。注：表示されるコードは1つだけです。                                            | String    |
+| **Friendbuy Coupon Value**       | 顧客に配布された最新のクーポンコードの通貨価値。                                                                     | 数値    |
+| **Friendbuy Coupon Status**      | 顧客に配布された最新のクーポンコードのステータス。注：ステータスは「distributed」または「redeemed」です。                            | String    |
+| **Friendbuy Coupon Currency**    | 顧客に配布された最新のクーポンコードに関連する通貨コード（USD、CADなど）またはパーセント（%）。                             | String    |
 | **FriendbuyクーポンキャンペーンID** | 顧客のために生成されたクーポンコードに関連するキャンペーンID。                                                                          | String    |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## デフォルトの動作
 
-顧客データがBrazeに送信される前に、顧客は紹介ウィジェットを通じて以下のボックスの1つ以上にチェックを入れてオプトインする必要がある：
+顧客データを Braze に送信する前に、顧客は紹介ウィジェットで以下の1つ以上のボックスをオンにして、オプトインする必要があります。
 
 ![紹介ウィジェット][103]
 
@@ -72,10 +72,10 @@ Friendbuyは国際標準規格(E.164)を採用し、実在する電話番号を
 
 | チェックボックスが選択されている | 動作                                                        |
 |-------------------|-----------------------------------------------------------------|
-| Eメールのみ        | Brazeに送信されるのは顧客のEメールアドレスのみである。             |
-| 電話のみ        | 顧客の電話番号だけがブレイズに送られる。              |
-| どちらでもない           | 顧客データがBrazeに送信されることはない。                              |
-| どちらも              | 顧客の電子メールアドレスと電話番号がブレイズに送信される。 |
+| Eメールのみ        | 顧客のメールアドレスだけが Braze に送信されます。             |
+| 電話のみ        | 顧客の電話番号だけが Braze に送信されます。              |
+| Neither           | 顧客データがBrazeに送信されることはない。                              |
+| どちらも              | 顧客のメールアドレスと電話番号が Braze に送信されます。 |
 
 [1]: https://retailer.friendbuy.io/
 [100]: {% image_buster /assets/img/friendbuy/choosing_braze.png %}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/jebbit.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/jebbit.md
index e4a391c58bf..a7820f59f2d 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/jebbit.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/jebbit.md
@@ -10,31 +10,31 @@ search_tag: Partner
 
 # Jebbit
 
-> [Jebbitは](https://www.jebbit.com/)、ファーストパーティデータを取得するための魅力的なユーザー体験を構築できるPaaSだ。
+> [Jebbit](https://www.jebbit.com/) は、ユーザーがファーストパーティデータを取得するための魅力的なエクスペリエンスを構築できる PaaS です。
 
-BrazeとJebbitの統合により、JebbitキャンペーンのユーザーEメールや属性をユーザーデータとしてリアルタイムでBrazeに渡すことができる。このデータは、パーソナライズされたEメールキャンペーンやトリガーのようなマーケティングイニシアティブを推進するために使用することができる。 
+Braze と Jebbit の統合により、Jebbit キャンペーンのユーザーメールと属性をユーザーデータとして Blaze にリアルタイムで渡すことができます。その後、パーソナライズされたメールキャンペーンやトリガーなどのマーケティングイニシアチブを推進するためにこのデータを利用できます。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-|Jebbitアカウント | このパートナーシップを利用するには、Jebbitアカウントが必要である。 |
+|Jebbitアカウント | このパートナーシップを活用するには、Jebbit アカウントが必要です。 |
 | Braze REST API キー | すべてのユーザーデータ権限を持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-|Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントは、[インスタンスの]({{site.baseurl}}/api/basics/#endpoints)Braze URLに依存する。 |
+|Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL]({{site.baseurl}}/api/basics/#endpoints) に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-Jebbitとの統合を依頼する際、厳しい納期が必要であれば伝えること。さらに、Brazeに渡したいJebbitエクスペリエンスの属性がマッピングされていることを確認する。
+Jebbitとの統合を依頼する際、厳しい納期が必要であれば伝えること。さらに、Braze に渡す属性が Jebbit エクスペリエンスにマッピングされていることを確認します。
 
 ### ステップ1:API認証情報を提供する
 
 API認証情報をテキストファイルでDropboxファイルリクエスト経由でJebbitに提供する。
-以下の[Dropbox URLを](https://www.dropbox.com/request/RqKQHkJHXw1cFBKbXpZx)使用してファイルを提出する。
+以下の [Dropbox URL](https://www.dropbox.com/request/RqKQHkJHXw1cFBKbXpZx) を使用してファイルを送信します。
 
-### ステップ2:テストの提出を確認する
+### ステップ2:テスト送信を確認する
 
-統合を担当するJebbitエンジニアが、JebbitからBrazeへのテスト送信をプッシュするので、Braze環境でデータがどのように見えるかを確認できる。これが統合を活性化させる最終ステップである。Jebbitのデータがセットアップされたので、それを使ってマーケティングイニシアティブを推進しよう。
+統合を担当するJebbitエンジニアが、JebbitからBrazeへのテスト送信をプッシュするので、Braze環境でデータがどのように見えるかを確認できる。これは、統合アクティブ化の最後の手順です。Jebbitのデータがセットアップされたので、それを使ってマーケティングイニシアティブを推進しよう。
 
 {% alert note %}
 Jebbitで設定した属性IDが、Brazeでの属性フィールド名の表示方法となる。
@@ -45,4 +45,4 @@ Jebbitで設定した属性IDが、Brazeでの属性フィールド名の表示
 現在、[ユーザーデータの]({{site.baseurl}}/api/endpoints/user_data/)エンドポイントを特別にサポートしているが、異なるエンドポイントへのリクエストもサポート可能だ。
 属性フィールド名も好みに応じてカスタマイズできる。
 
-BrazeにJebbitの属性を追加したい場合は、Jebbitアカウントで新しい属性をマッピングする。その属性のデータを収集すると、Brazeにその属性が自動的に表示される。
+Braze で Jebbit から追加の属性が必要な場合は、Jebbit アカウントで新しい属性をマッピングします。その属性のデータを収集すると、Brazeにその属性が自動的に表示される。
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/kognitiv.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/kognitiv.md
index 79abbaa3fe8..76850d079e0 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/kognitiv.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/kognitiv.md
@@ -1,50 +1,50 @@
 ---
-nav_title: コグニティブ・インスパイア
-article_title: コグニティブ・インスパイア
-description: "コグニティブ・インスパイアは、ロイヤリティ戦略の実施と評価を可能にするロイヤリティ・テクノロジー・システムであり、革新的な機能と会員に合わせたコミュニケーションを提供し、プログラムの効果を高める。"
+nav_title: Kognitiv Inspire
+article_title: Kognitiv Inspire
+description: "Kognitiv Inspire は、お客様が各自のロイヤルティ戦略を実装、評価できるようにし、プログラムの有効性を高めるための革新的な機能とカスタマイズされたメンバーコミュニケーションを提供するロイヤルティテクノロジーシステムです。"
 alias: /partners/kognitiv/
 page_type: partner
 search_tag: Partner
 ---
 
-# コグニティブ・インスパイア
+# Kognitiv Inspire
 
-> [Kognitiv Inspireは][1]ロイヤリティ・テクノロジー・システムであり、顧客エンゲージメントを増幅し、支出を増大させ、忠実な行動を称える結果重視のロイヤリティ・プログラムを通じて、比類ない顧客体験を引き出す手助けをする。
+> [Kognitiv Inspire][1] はロイヤルティテクノロジーシステムであり、カスタマーエンゲージメントを強化し、顧客の支出を増やし、ロイヤルティの高い行動を称賛する、結果に基づくロイヤルティプログラムによって、比類のない顧客体験を実現できるように支援します。
 
-BrazeとKognitivの統合により、ロイヤリティ戦略の実施と評価が可能になり、革新的な機能と会員に合わせたコミュニケーションを提供し、プログラムの効果を高めることができる。
+Braze と Kognitiv の統合により、ロイヤルティ戦略を実装、評価できるようになり、プログラムの有効性を高めるための革新的な機能とカスタマイズされたメンバーコミュニケーションが提供されます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| コグニティブアカウント | このパートナーシップを利用するには、[コグニティブの][1]アカウントが必要である。 |
+| コグニティブアカウント | このパートナーシップを活用するには、[Kognitiv][1] アカウントが必要です。 |
 | Kognitiv APIキー | Kognitiv REST API キー。これは**API Security Tokens**ページで作成できる。 |
-| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントは、[インスタンスの]({{site.baseurl}}/api/basics/#endpoints)Braze URLに依存する。 |
+| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL]({{site.baseurl}}/api/basics/#endpoints) に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
-- **パーソナライズされたロイヤリティ・プログラムの登録**：シームレスなプログラム登録と、会員が希望するチャネルを通じて配信されるカスタマイズされたウェルカム通知で、会員のロイヤリティ・ジャーニーを促進する。
-- **報酬発行と婚約通知**：各メンバーのマイルストーンを祝うリワードや通知を発行することで、ロイヤリティの火花を絶やさないようにする。
-- **戦略的な会員の階層化とセグメンテーション**：ブランド固有のニーズに合わせて、支出、エンゲージメント、単純または複雑なビジネス・ルールに基づいて会員を階層化およびセグメント化することで、よりパーソナライズされたエンゲージメントを可能にする。
-- **昇格資格をリアルタイムで通知**する：限定プロモーションの参加資格を即座に通知することで、各会員に特別感を与える。
+- **パーソナライズされたロイヤルティプログラムの登録**:シームレスなプログラム登録と、会員が希望するチャネルを通じて配信されるカスタマイズされたウェルカム通知で、会員のロイヤルティジャーニーを促進します。
+- **リワードの発行とエンゲージメント通知**:会員のマイルストーンを祝うリワードの発行や通知により、ロイヤルティを維持します。
+- **戦略的な会員の階層化とセグメンテーション**:ブランド固有のニーズに合わせて、支出、エンゲージメント、単純または複雑なビジネス・ルールに基づいて会員を階層化およびセグメント化することで、よりパーソナライズされたエンゲージメントを可能にする。
+- **リアルタイムでのプロモーション参加資格の通知**:限定プロモーションの参加資格を即時に通知することで、各会員に特別感を与えます。
 
 ## 統合
 
 KognitivのWebhookを使って、ロイヤルティイベント発生時にBrazeにリクエストを送る。以下の例では、KognitivとBrazeを使用して報酬を発行し、KognitivユーザーをBrazeに登録し、ウェルカムメールを送信する方法を説明する。
 
 {% raw %}
-### ブレイズ発行報酬
+### Braze によるリワードの発行
 
-次のコグニティブの例では、会員に報奨金を発行している。Kognitiv Inspireは、その報酬発行イベントをカスタムイベントとしてBrazeにウェブフック経由で伝える。報酬を伝えるフォローアップメールを送信するには、そのカスタムイベントをトリガーとするキャンペーンまたはキャンバスを作成する。
+次の Kognitiv の例では、会員リワードを発行します。Kognitiv Inspire はそのリワード発行イベントを、Webhook を使用して Braze にカスタムイベントとして伝えます。報酬を伝えるフォローアップメールを送信するには、そのカスタムイベントをトリガーとするキャンペーンまたはキャンバスを作成する。
 
-**ウェブフックのURL**：`<braze-api-rest-endpoint>`
-**リクエスト・ボディ** `Raw Text`
+**Webhook URL**:`<braze-api-rest-endpoint>`
+**リクエスト本文**: `Raw Text`
 
 - **HTTPメソッド**：POST
-- **ヘッダーを要求する**：
-  - **認可する**：ベアラー `<Kognitiv-api-key>`
-  - **コンテンツタイプ**application/json
+- **リクエストヘッダー**:
+  - **Authorization**:ベアラー `<Kognitiv-api-key>`
+  - **Content-Type** application/json
 
 #### Request body
 
@@ -66,15 +66,15 @@ KognitivのWebhookを使って、ロイヤルティイベント発生時にBraze
 
 ### ユーザーを作成し、ウェルカムメールを送信する
 
-以下の Kognitiv の例では、KLS への登録時に Braze に新規ユーザーを作成している。このユーザーのウェルカムメールをスケジュールするには、特定のカスタム属性に基づいてトリガーするキャンペーンまたはキャンバスをBrazeで作成する。
+次の Kognitiv の例では、新規ユーザーが KLS に登録すると、Braze に新規ユーザーが作成されます。このユーザーのウェルカムメールをスケジュールするには、特定のカスタム属性に基づいてトリガーするキャンペーンまたはキャンバスをBrazeで作成する。
 
-**ウェブフックのURL**： `<braze-api-rest-endpoint>`<br>
-**リクエスト・ボディ** `Raw Text`
+**Webhook URL**: `<braze-api-rest-endpoint>`<br>
+**リクエスト本文**: `Raw Text`
 
 - **HTTPメソッド**：POST
-- **ヘッダーを要求する**：
-  - **認可する**：ベアラー `<Kognitiv-api-key>`
-  - **コンテンツタイプ**application/json
+- **リクエストヘッダー**:
+  - **Authorization**:ベアラー `<Kognitiv-api-key>`
+  - **Content-Type** application/json
 
 #### Request body
 
@@ -104,26 +104,26 @@ KognitivのWebhookを使って、ロイヤルティイベント発生時にBraze
 
 ## Kognitiv Inspireのドキュメントと統合機能
 
-BrazeをKognitiv Inspireと統合すると、Kognitivの広範なAPIポートフォリオ、最先端のウェブフック機能、シームレスな一括転送のための堅牢なデータのインポートおよびエクスポート機能にアクセスできるようになる。Kognitiv Inspireの機能と統合機能の詳細については、Kognitiv[リソースガイドを][2]参照するか、ガイド付きデモを希望する場合は同社に連絡する。
+Braze を Kognitiv Inspire と統合すると、Kognitiv の広範な API ポートフォリオ、最先端の Webhook 機能、およびシームレスな一括転送のための堅牢なデータインポートおよびエクスポート機能を利用できるようになります。Kognitiv Inspire の機能と統合機能の詳細については、Kognitiv[リソースガイド][2]を参照するか、Kognitive に連絡してガイド付きデモを依頼してください。
 
 ### エンドポイント
 
-**REST APIの認可**
-- 米国地域である： `https://app.kognitivloyalty.com/Auth/connect/token`
-- CA/EMEA地域： `https://ca.kognitivloyalty.com/Auth/connect/token`
-- APAC地域： `https://aus.kognitivloyalty.com/Auth/connect/token`
+**REST API 認証**
+- US 地域: `https://app.kognitivloyalty.com/Auth/connect/token`
+- CA/EMEA 地域: `https://ca.kognitivloyalty.com/Auth/connect/token`
+- APAC 地域： `https://aus.kognitivloyalty.com/Auth/connect/token`
 
-**REST API（ベースURL）**
-- 米国地域である： `https://app.kognitivloyalty.com/api`
-- CA/EMEA地域： `https://ca.kognitivloyalty.com/api`
-- APAC地域： `https://aus.kognitivloyalty.com/api`
+**REST API (ベース URL)**
+- US 地域: `https://app.kognitivloyalty.com/api`
+- CA/EMEA 地域: `https://ca.kognitivloyalty.com/api`
+- APAC 地域： `https://aus.kognitivloyalty.com/api`
 
 **ウェブサービスのエンドポイント（ベースURL）**
-- 米国地域である： `https://app.kognitivloyalty.com/WS`
-- CA/EMEA地域： `https://ca.kognitivloyalty.com/WS`
-- APAC地域： `https://aus.kognitivloyalty.com/WS`
+- US 地域: `https://app.kognitivloyalty.com/WS`
+- CA/EMEA 地域: `https://ca.kognitivloyalty.com/WS`
+- APAC 地域： `https://aus.kognitivloyalty.com/WS`
 
-アクセストークンおよびSFTPエンドポイントの設定に関する詳細については、Kognitivにデモを問い合わせること。
+アクセストークンと SFTP エンドポイントの設定に関する詳細については、Kognitiv にデモを依頼してください。
 
 [1]: http://kognitiv.com
 [2]: https://info.kognitivloyalty.com
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/nift.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/nift.md
index 04c33b7f965..fec749e5dc8 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/nift.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/nift.md
@@ -1,31 +1,31 @@
 ---
-nav_title: ニフト
-article_title: ニフト
-description: "この参考文献では、企業が顧客を獲得し、関与し、維持するのを助ける2つの側面から成るプラットフォームであるBrazeとニフトの提携について概説する。"
+nav_title: Nift
+article_title: Nift
+description: "このリファレンス記事では、Braze と Nift のパートナーシップについて説明します。Nift は、企業が顧客を獲得し、関与し、維持するのを支援する双方向プラットフォームです。"
 alias: /partners/nift/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# ニフト
+# Nift
 
-> [Nift](https://gonift.com/)は、企業が顧客を獲得し、エンゲージし、維持するのを助ける。両面プラットフォームは、提携企業がニッツギフトカードsで顧客に感謝するのを助ける。顧客sのおかげで、生涯価値が高まり、増分収益を生み出す。
+> [Nift](https://gonift.com/) は、企業が顧客を獲得し、関与し、維持するのを支援します。この双方向プラットフォームでは、パートナーが Nift ギフトカードで顧客への感謝を示すことができます。顧客に感謝を示すことで、顧客生涯価値が高まり、収益が増加します。
 
-Braze とNift の統合により、自動的にトリガー " thank-yous" カスタマーライフサイクルの主要な瞬間にNift ギフトが含まれ、どの顧客が自分のギフトを使用したかを特定することができます。ニフト・ギフト・カードは、ニフトのマッチメーキング・テクノロジーに依存しているブランドが提供する商品やサービスを利用して、コスト効率の良い新しい顧客を獲得することができます。
+Braze と Nift の統合により、カスタマーライフサイクルにおいて重要なタイミングで Nift ギフトを含む「お礼 (thank-yous)」を自動的にトリガーし、どの顧客がギフトを使用したかを特定できます。Nift ギフトカードは、Nift のマッチメイキング技術を利用して、費用対効果の高い大規模で新規顧客を獲得するブランドが提供する製品やサービスにアクセスするために使用できます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| ニフト口座 | この提携の前進タグeを考慮するためには、ニフトの勘定が必要である。 |
+| Nift アカウント | このパートナーシップを活用するには、Nift アカウントが必要です。 |
 | Braze REST API キー | すべてのユーザーデータ権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
 | Braze REST エンドポイント | REST エンドポイントのURL。エンドポイントは、[インスタンス]({{site.baseurl}}/api/basics/#endpoints)のBraze URLによって異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### ステップ1:ニフトのBrazeに接続する
+### ステップ1:Nift で Braze に接続する
 
 [Nift ダッシュボード][2]にアクセスし、**Accounts**> **Integrations**> **Braze**に移動し、**Connect**をクリックします。
 
@@ -33,17 +33,17 @@ Braze とNift の統合により、自動的にトリガー " thank-yous" カス
 
 **Brazeアカウント**ページをリンクするには、Braze REST API キーを入力し、[インスタンス]({{site.baseurl}}/api/basics/#endpoints)のBraze URLに応じてBraze エンドポイントを選択します。
 
-顧客 s に送信される参照リンクの顧客 ID パラメータ名を変更できます。ニフトはこれを使って、あなたの顧客sが私たちのブランドの1つからプレゼントを選んだときに、Brazeで処理されたものとして印付けます。
+顧客に送信される紹介リンクの顧客 ID パラメーター名を変更できます。Ｎｉｆｔ は、顧客が Braze のブランドのギフトを選択している場合に、顧客を Braze で処理済みとしてマークします。
 
-**Link Account**をクリックします。
+\[**Link Account**] をクリックします。
 
-!["Nift サービスインテグレーションページで、ユーザーにBraze API キーとBraze ダッシュボードのURL を入力します。][5]
+!["ユーザーに Braze API キーと Braze ダッシュボード URL の入力を求める Nift サービス統合ページ。][5]
 
 ## 統合の使用
 
 インテグレーションを使用するには、メッセージングでリファラルリンクを配布します。顧客が紹介リンクを使用し、当社のブランドの1つからギフトを選択すると、ニフトはそれらをBrazeで処理されたものとしてマークします。
 
-Braze との統合後、Nift は次の情報を含む顧客 Brazeレコードにイベントを自動的にプッシュします。
+Braze との統合後、Nift は以下のデータを含む既存の顧客の Braze レコードにイベントを自動的にプッシュします。
 
 - イベント名: `nift_processed`
 - 時間:顧客がプレゼントを選択/使用した時刻
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh.md
index ba55ae0512e..55c1fa4cc47 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh.md
@@ -11,7 +11,7 @@ guide_featured_list:
 - name: Punchh
   link: /docs/partners/message_orchestration/channel_extensions/loyalty/punchh/punchh/
   image: /assets/img/braze_icons/bank-note-02.svg
-- name: ダイナミック・コード生成
+- name: 動的コード生成
   link: /docs/partners/message_orchestration/channel_extensions/loyalty/punchh/code_generation/
   image: /assets/img/braze_icons/code-square-01.svg
 
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh/code_generation.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh/code_generation.md
index 10b5b7bd6a1..61a7dc36823 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh/code_generation.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh/code_generation.md
@@ -1,6 +1,6 @@
 ---
-nav_title: ダイナミック・コード生成
-article_title: パンチ・ダイナミック・コード生成
+nav_title: 動的コード生成
+article_title: Punchh 動的コード生成
 page_order: 2
 description: "このリファレンス記事では、BrazeにおけるPunchh動的コード生成の使い方を概説している。"
 page_type: partner
@@ -25,18 +25,18 @@ Punchhクーポン・フレームワークとBrazeを使えば、以下のよう
     - 動的クーポン生成トークン：これは、暗号化のためにシステムが生成したセキュリティ・トークンである。
     - 動的クーポン生成URL：このURLは、ビジネスの要求に応じて、リンクまたは画像としてメールに埋め込まれる。
 
-![]({% image_buster /assets/img/punchh/punchh8.png %}){: style="max-width:60%;"}
+![Punchh でクーポンキャンペーンを作成するためのフォーム。]({% image_buster /assets/img/punchh/punchh8.png %}){: style="max-width:60%;"}
 
 ### ステップ2:署名を生成し、URLを構築する
 
 JWT.IO ライブラリは、JSONウェブトークンをデコード、検証、生成する。これは、2つの当事者間でクレームを安全に表現するための、オープンで業界標準のRFC 7519方式である。 
 
-ゲストとクーポンの一意性を確保するために、以下の`ClaimType` ：
+次の`ClaimType` の名前を使用して、ゲストとクーポンの一意性を確保できます。
 
-- `campaign_id`これはシステムが生成したパンチキャンペーンIDを表す。
-- `email`ユーザーのメールアドレスを表す。 
-- `first_name`ユーザーのファーストネームをキャプチャする。 
-- `last_name`ユーザーの姓をキャプチャする。
+- `campaign_id`: システム生成の Punchh キャンペーン ID を表します。
+- `email`: ユーザーのメールアドレスを表します。 
+- `first_name`:ユーザーの名を取得します。 
+- `last_name`: ユーザーの姓を取得します。
 
 Punchhのダイナミック・クーポン・コードAPIを使用するには、JWTトークンを構築する必要がある。Brazeダッシュボードの使用したいチャンネルのメッセージ本文に、以下のLiquidテンプレートを追加する：
 
@@ -80,9 +80,9 @@ Punchhのダイナミック・クーポン・コードAPIを使用するには
 
 ### ステップ3:クーポンコードをメッセージ本文に追加する
 
-#### パンチ・ウェブページへのリンク
+#### Punchh Web ページへのリンク
 
-Puncchがホストするウェブページにリンクするには、[先ほど作成した](#step-1-create-a-coupon-campaign-in-punchh)動的生成URLに`{% raw %}{{jwt}}{% endraw %}` 。リンクは以下のようなものであるべきだ： 
+Puncch がホストする Web ページにリンクするには、[以前に作成した](#step-1-create-a-coupon-campaign-in-punchh)動的生成 URLに `{% raw %}{{jwt}}{% endraw %}` を追加します。リンクは以下のようなものであるべきだ： 
 
 {% raw %}
 ```
@@ -96,7 +96,7 @@ https://fakebrandz.punchh.com/request_coupons/7xY3bL9jRfZ1pA6mc8qD2eS4vT5wX?sign
 
 #### JSON経由でコードをプレーンテキストとして抽出する
 
-JSONレスポンスを返すには、[先ほど作成した](#step-1-create-a-coupon-campaign-in-punchh)動的生成URLに`{% raw %}{{jwt}}{% endraw %}` 、URL文字列のトークンの後に`.json` 。リンクは以下のようなものであるべきだ：
+JSON 応答を返すには、[以前に作成した](#step-1-create-a-coupon-campaign-in-punchh)動的生成 URL に`{% raw %}{{jwt}}{% endraw %}` を追加し、URL 文字列のトークンの後に `.json` を追加します。リンクは以下のようなものであるべきだ：
 
 {% raw %}
 ```liquid
@@ -117,8 +117,8 @@ https://fakebrandz.punchh.com/request_coupons/7xY3bL9jRfZ1pA6mc8qD2eS4vT5wX.json
 
 クーポンコードを画像内にリンクする：
 
-1. [先ほど作成した](#step-1-create-a-coupon-campaign-in-punchh)動的生成URLに`{% raw %}{{jwt}}{% endraw %}` を追加する。
-2. URL文字列のトークンの後に`.png` 。
+1. [以前に作成した](#step-1-create-a-coupon-campaign-in-punchh)動的生成 URL に `{% raw %}{{jwt}}{% endraw %}` を追します。
+2. URL 文字列のトークンの後に`.png` を追加します。
 3. リンクをHTML{% raw %}`<img>`{% endraw %} タグに埋め込む。
 
 {% tabs ローカル %}
@@ -139,11 +139,11 @@ https://fakebrandz.punchh.com/request_coupons/7xY3bL9jRfZ1pA6mc8qD2eS4vT5wX.json
 
 | エラーコード | エラーメッセージ | 説明 |
 | --- | --- | --- |
-| `coupon_code_expired` | このプロモーションコードの有効期限は切れている | コードは設定された有効期限後に使用される。 |
+| `coupon_code_expired` | このプロモーションコードの有効期限は切れている | このコードが、設定された有効期限日よりも後に使用されています。 |
 | `coupon_code_success` | おめでとう、プロモコードは正常に適用された。 | コードは正常に使用されている。 |
 | `coupon_code_error` | 有効なプロモーションコードを入力する | 使用されたコードは無効である。 |
-| `coupon_code_type_error` | クーポンの種類が正しくない。このクーポンは`%{coupon_type}` でのみ利用できる。 | POSで使用するはずのコードをモバイルアプリで使用すると、このエラーが発生する。 |
-| `usage_exceeded` | 本クーポンコードのキャンペーンは終了した。次回はぜひ挑戦してほしい。 | コードの使用量が、使用を許可されたユーザー数を超えている。例えば、ダッシュボードのコンフィギュレーションが3,000人のユーザーによるコードの使用を許可しており、ユーザー数が3,000人を超えた場合、このエラーが発生する。 |
-| `usage_exceeded_by_guest` | このプロモコードはすでに処理されている。 | ユーザーによるコードの使用は、ユーザーが使用できる回数を超えている。例えば、ダッシュボードの設定では、1つのコードをユーザーが3回使用することができる。それ以上使用すると、このエラーが発生する。 |
+| `coupon_code_type_error` | Incorrect coupon type.このクーポンは`%{coupon_type}` でのみ利用できる。 | POSで使用するはずのコードをモバイルアプリで使用すると、このエラーが発生する。 |
+| `usage_exceeded` | 本クーポンコードのキャンペーンは終了した。Please try next time. | コードの使用量が、使用を許可されたユーザー数を超えている。例えば、ダッシュボードのコンフィギュレーションが3,000人のユーザーによるコードの使用を許可しており、ユーザー数が3,000人を超えた場合、このエラーが発生する。 |
+| `usage_exceeded_by_guest` | このプロモコードはすでに処理されている。 | ユーザーによるコードの使用は、ユーザーが使用できる回数を超えている。たとえば、ダッシュボード設定ではユーザーが1つのコードを3回使用できます。それ以上使用すると、このエラーが発生します。 |
 | `already_used_by_other_guest` | このプロモコードはすでに他のゲストが使用している。 | 別のユーザーがすでにこのコードを使用している。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh/punchh.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh/punchh.md
index 16d60935c7c..81b68412544 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh/punchh.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/punchh/punchh.md
@@ -2,7 +2,7 @@
 nav_title: Punchh
 article_title: Punchh
 page_order: 1
-description: "このリファレンス記事では、ロイヤルティとエンゲージメント プラットフォームであるBraze とパンチの提携について概説します。これにより、2 つのプラットフォームs 間でデータを同期できます。Braze で公開されたデーターはセグメンテーションに使用でき、Braze で設定されたWebhook テンプレートを使ってユーザーデータをパンチに戻すことができます。"
+description: "このリファレンス記事では、Braze と Punchh のパートナーシップについて説明します。Punchh はロイヤルティとエンゲージメントのプラットフォームであり、2つのプラットフォーム間でデータを同期できるようになります。Braze で公開されたデータはセグメンテーションに使用でき、Braze で設定された Webhook テンプレートを使用してユーザーデータを Punchh に同期できます。"
 page_type: partner
 search_tag: Partner
 
@@ -12,66 +12,66 @@ search_tag: Partner
 
 > [Punchh](https://punchh.com/)は、ブランドが店内でもデジタルでもオムニチャネル 顧客 ロイヤルティプログラムを配信できる、業界をリードするロイヤルティとエンゲージメント プラットフォームです。 
 
-Braze とパンチインテグレーションでは、2 つのプラットフォームs 間でギフトやロイヤルティのためにデータを同期できます。Braze で公開されたデーターはセグメンテーションに使用でき、ユーザーデータをBraze webhook でパンチに戻すことができます。
+Braze と Punchh の統合により、2つのプラットフォーム間でギフティングやロイヤルティの目的でデータを同期できます。Braze で公開されたデータはセグメンテーションに使用でき、Braze Webhook を介してユーザーデータを再び Punchh に同期できます。
 
 ## メリットは何でしょうか。
 
-- パンチからBrazeへのロイヤルティをリアルタイムで取り込みます。 
-- Brazeからの強力なオーディエンス情報を活用し、意味のあるダイナミックな クロスチャネルの体験(アプリ、モバイル、ウェブ、メール、SMS)を提供する
-  - 顧客 sはsを開封 メールしましたか?顧客は店の近くでアプリを開封しましたか？
-- Brazeで送信されるアクション間のメールのルックアンドフィールを標準化します。
-- A/B テストと最適化を可能にするジャーニーを作成します。
+- Punchh から Braze にロイヤルティデータをリアルタイムで取り込む。 
+- Braze の強力なオーディエンス情報を利用してレイヤー化し、有意義でダイナミックなクロスチャネルエクスペリエンス (アプリ、モバイル、Web、メール、SMS) を提供する。
+  - 顧客がメールを開封しましたか?顧客が店舗の周辺でアプリを開きましたか?
+- Braze で送信されるトランザクションメールのルックアンドフィールを標準化する。
+- その過程で AB テストと最適化を可能にするジャーニーを作成する。
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| パンチアカウント | この提携の前進タグeを考慮するには、積極的なパンチの勘定が必要である。 |
-| Braze REST API キー | `users.track` 権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
-| Braze REST エンドポイント | \[Your REST エンドポイント URL][6].エンドポイントは、インスタンスのBraze URL によって異なります。 |
+| Punchh アカウント | このパートナーシップを活用するには、アクティブなPunchh アカウントが必要です。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
+| Braze REST エンドポイント | \[REST エンドポイント URL][6]。エンドポイントはインスタンスの Braze URL に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-## 他に何を知るべきですか？
+## その他の留意点
 
 #### 統合前
 
-- Brazeインテグレーションを使用する場合、パンチに1つ、Brazeに2つのキャンペーンsが必要です。たとえば、オファーが添付されたキャンペーンを送信すると、ギフトキャンペーンはパンチ内で設定され、通知はBrazeから送信できます。
-- ゲストはパンチとBrazeにすでに存在するはずです。パンチはまだロイヤルティ客でない顧客をフィルターするだろう。
+- Braze 統合を使用する場合、Punchh と Braze それぞれに1つずつ、2つのキャンペーンが必要です。たとえば、オファーが添付されているキャンペーンを送信する場合、ギフティングキャンペーンは Punchh 内で設定され、通知は Braze から送信できます。
+- ゲストは Punchh と Braze にすでに存在している必要があります。Punchh では、まだロイヤルティゲストではない顧客はすべて除外されます。
 
 #### 注意すべき重要事項
 
-- パンチはデフォルト ユーザー 属性sのBrazeへの送信を無効にする機能を追加したので、顧客はデータポイント 超過料金sを発生させません。これは、アダプターのセットアップ中に構成されます。
+- Punchh では、Braze にデフォルトのユーザー属性を送信する動作を無効にできる機能が追加されています。これにより、顧客に対してデータポイントの超過料金が発生することがありません。これは、アダプターのセットアップ中に構成されます。
 - キャンペーンが実行されるたびにID が変更されるため、定期的なキャンペーンでカスタムSegments を使用する場合は、キャンペーン ID の代わりにキャンペーンの名前を使用する必要があります。
-- パンチギフトキャンペーンで使用できる通信チャネルには、リッチメッセージ、プッシュ通知s、SMS、メールがあります。
-- ユーザー s がBraze からパンチカスタムSegmentに送信された後は、削除できません。既存のカスタムSegmentに追加できるのは、新しいゲストのみです。既存のPunchhカスタムSegmentからゲストを削除する必要がある場合は、新しいPunchhカスタムSegmentにユーザーを送信するために、新しいWebhook キャンペーンをBrazeで作成する必要があります。
+- 各 Punchh ギフティングキャンペーンで使用できるコミュニケーションチャネルには、リッチメッセージ、プッシュ通信、SMS、メールがあります。
+- Braze から Punchh カスタムセグメントに送信されたユーザーは、削除できません。既存のカスタムセグメントには新規ゲストのみを追加できます。既存のPunchhカスタムSegmentからゲストを削除する必要がある場合は、新しいPunchhカスタムSegmentにユーザーを送信するために、新しいWebhook キャンペーンをBrazeで作成する必要があります。
 
 ## 統合
 
-Punchh には、以下のPunchh API エンドポイントを使用して外部ID をPunchh プラットフォームに追加するために、Braze 顧客 s で使用できるいくつかのエンドポイントが用意されています。外部ID を追加したら、Punchh でアダプターを作成し、Braze 認証情報を入力して、同期したい行動を選択します。次に、パンチSegment ID を取得し、それを使用してパンチWebhookを作成し、キャンバスの旅行で同期をトリガー 顧客できます。
+Punchh は、Braze の顧客が利用できる複数のエンドポイントを提供します。これは、次の Punchh API エンドポイントを使用して Punchh プラットフォームに external ID を追加するのに役立ちます。外部ID を追加したら、Punchh でアダプターを作成し、Braze 認証情報を入力して、同期したい行動を選択します。次に、Punchh セグメントID を使用して、キャンバスジャーニーで顧客同期をトリガーする Punchh Webhook を作成できます。
 
-Punchh `user_id` はカスタム属性"punchh_ユーザー_id" としてBraze ユーザープロファイルに追加する必要があることに注意してください。同様に、Braze で使用されている`external_id` は、Punchh ユーザープロファイルの`external_source_id` フィールドとして含める必要があります。 
+Punchh `user_id` は、使用する統合のカスタム属性「punchh_user_id」として Braze ユーザープロファイルに追加する必要があることに注意してください。同様に、Braze で使用されている`external_id` は、Punchh ユーザープロファイルに`external_source_id` フィールドとして含める必要があります。 
 
-### ステップ1:外部ID 取り込みエンドポイントの設定s
+### ステップ1:external ID 取り込みエンドポイントを設定する
 
-Braze の外部ID は、新規および既設のパンチユーザーs の次のエンドポイントs を使用して追加できます。
+Braze の external ID は、新規および既存の Punchh ユーザーの次のエンドポイントを使用して追加できます。
 
 {% alert important %}
-`external_source` および`external_source_id` フィールドは、Punchh に対して一意であり、存在するプロファイルs に関連付けられていない必要があります。
+`external_source` および`external_source_id` フィールドの値は、Punchh に対して一意であり、また既存のプロファイルに関連付けられていてはなりません。
 {% endalert %}
 
-1. 新型パンチユーザー<br>
-`external_source` および`external_source_id` フィールドs を使用して、Punchh サインアップエンドポイントでPunchh に新しいユーザーs を作成します。パンチ機能を使用すると、次のいずれかのサインアップエンドポイントs を使用して、external ID全体をユーザープロファイルで送信できます。
-- [モバイルサインアップAPI](https://developers.punchh.com/docs/dev-portal-mobile/2e67abf6f8e12-sign-up-register)
-- [SSO サインアップAPI](https://developers.punchh.com/docs/dev-portal-online-ordering/58f18dfdd2a3d-signup-with-email-and-password)<br><br>
-2. 従来のパンチユーザー <br>
-既設パンチユーザーs の`external_source_id` をアップデートします。パンチ機能を使用すると、ユーザー API 更新 エンドポイントを介してexternal ID全体をプロファイルに追加できます。 
-- [モバイルユーザーの更新](https://developers.punchh.com/docs/dev-portal-mobile/c9b928e35a6f3-update-user-profile)
-- [SSO ユーザー更新](https://developers.punchh.com/docs/dev-portal-online-ordering/eef4eef6c97a0-update-user-information)
-- [ダッシュボードユーザーの更新](https://developers.punchh.com/docs/dev-portal-platform-functions/6351feaf591aa-update-a-user)
+1. 新規 Punchh ユーザー<br>
+`external_source` および`external_source_id` フィールドs を使用して、Punchh サインアップエンドポイントでPunchh に新しいユーザーs を作成します。Punchh では、外部識別子をユーザープロファイルとともに次のいずれかの登録エンドポイントを介して送信できます。
+- [Mobile Signup API](https://developers.punchh.com/docs/dev-portal-mobile/2e67abf6f8e12-sign-up-register)
+- [SSO Signup API](https://developers.punchh.com/docs/dev-portal-online-ordering/58f18dfdd2a3d-signup-with-email-and-password)<br><br>
+2. 既存の Punchh ユーザー <br>
+既存の Punchh ユーザーの`external_source_id` を更新します。Punchh では、ユーザーAPI 更新エンドポイントを介して外部識別子をプロファイルに追加できます。 
+- [Mobile User Update](https://developers.punchh.com/docs/dev-portal-mobile/c9b928e35a6f3-update-user-profile)
+- [SSO User Update](https://developers.punchh.com/docs/dev-portal-online-ordering/eef4eef6c97a0-update-user-information)
+- [Dashboard User Update](https://developers.punchh.com/docs/dev-portal-platform-functions/6351feaf591aa-update-a-user)
 <br><br>
 {% tabs ローカル %}
-{% tab ユーザーサインアップAPI の例 %}
-このサンプルでは、サインアップ時にユーザープロファイルを持つexternal ID全体を送信できます。これは、`external_source` を"顧客_id" および`external_source_id` を"111111111111111111" として文字列データ型として送信することによって行われます。
+{% tab ユーザー登録 API の例 %}
+この例では、登録時にユーザープロファイルを使用して外部識別子を送信できます。このために、`external_source` を「customer_id」として、`external_source_id` を文字列データ型の「111111111111111111」として送信します。
 
 ```json
 curl --location --request POST 'https://server_name_goes_here.punchh.com/api2/mobile/users' \
@@ -97,8 +97,8 @@ curl --location --request POST 'https://server_name_goes_here.punchh.com/api2/mo
 }'
 ```
 {% endtab %}
-{% tab ユーザ更新の事例 %}
-このサンプルでは、ユーザープロファイルを使用して全体を更新 external IDできます。これは、`external_source` を"顧客_id" および`external_source_id` を"111111111111111111" として文字列データ型として送信することによって行われます。
+{% tab ユーザー更新 API の例 %}
+この例では、ユーザープロファイルを使用して外部識別子を更新できます。このために、`external_source` を「customer_id」として、`external_source_id` を文字列データ型の「111111111111111111」として送信します。
 
 ```json
 curl --location --request PUT 'https://server_name_goes_here.punchh.com/api2/mobile/users' \
@@ -119,48 +119,48 @@ curl --location --request PUT 'https://server_name_goes_here.punchh.com/api2/mob
 {% endtabs %}
 
 {% alert note %}
-**プラットフォーム設定:**Punchh でexternal ID全体を有効にするには、Punchh ダッシュボードから**Cockpit**> **ダッシュボード**> **外部ユーザ識別子** に移動します。
+**プラットフォーム設定:**Punchh で外部識別子を有効にするには、Punchh ダッシュボードから \[**Cockpit**] > \[**Dashboard**] > \[**External User Identifier**] に移動します。
 {% endalert %}
 
-### ステップ2:パンチでのBrazeアダプターの設定
+### ステップ2:Punchh で Braze アダプターを設定する
 
-#### 同期可能なイベント {#available-events-to-sync}
+#### 同期できるイベント {#available-events-to-sync}
 
-1. **ゲスト:**サインアップ、ゲストプロファイルへの更新、非アクティブ化または削除時にトリガされます
-2. **ロイヤリティチェックイン:**ロイヤルティのトランスアクションでトリガーされるか、レシートからバーコードをスキャンして獲得します
-3. **ギフトチェックイン:**キャンペーンから贈られた点をトリガー
-4. **償還:**パンチクーポンを除く報酬償還の場合にトリガーされます。これは、発行と償還を含むクーポンイベントとして別々に送信されるためです
-5. **報酬:**報酬がキャンペーンs、活動、点から報酬sへのコンバージョン、または管理者ギフトから贈られたことをきっかけにした
-6. **トランスアクション通知:**パンチシステム内のユーザーのtrans アクション al アクティビティでトリガーされます(たとえば、ポイントの有効期限)。
-7. **マーケティング通知:**ユーザー s の関連付けられたSegmentに対して、パンチでのさまざまなキャンペーン設定に基づいてトリガーされます
+1. **Guest:**登録、ゲストプロファイルの更新、非アクティブ化、または削除時にトリガーされます。
+2. **Loyalty Check-in:**ロイヤルティトランザクションまたはレシートのバーコードスキャンによる獲得に対してトリガーされます。
+3. **Gift Check-in:**キャンペーンで与えられたポイントに対してトリガーされます。
+4. **Redemption:**パンチクーポンを除く報酬償還の場合にトリガーされます。これは、発行と償還を含むクーポンイベントとして別々に送信されるためです
+5. **Rewards:**キャンペーン、アクティビティ、ポイントからリワードへの変換、または管理ギフティングで与えられたリワードからトリガーされます。
+6. **Transaction Notifications:**Punchh システム内でのユーザーのトランザクションアクティビティに対してトリガーされます (ポイントの有効期限など)。
+7. **マーケティング通知:**関連付けられているユーザーセグメントの Punchh での各種キャンペーン設定に基づいてトリガーされます。
 
 {% alert note %}
-参考パンチドキュメントでは、これらの利用可能なイベントのサンプル有料読み込むがどのように見えるかを確認できます。
+これらの利用可能なイベントのサンプルペイロードの内容については、Punchh のドキュメントを参照してください。
 {% endalert %}
 
-このアダプターをセットアップするには、パンチインプリメンテーション・マネージャーを使用します。
+Punchh 実装マネージャーと協力して、このアダプターを設定します。
 
-Brazeとパンチインテグレーションを設定するには、以下の手順に従います。
+Braze と Punchh の統合を設定するには、次の手順を実行します。
 
-1. パンチダッシュボードで、**コックピット**> **ダッシュボード**> **主な機能**> **Webフック管理を有効にし、**Webフック管理を有効にします**。<br><br>
-2. 次に、**Settings**> **Webフックマネージャ**> **Configurations**> **Show Adapters Tab**に移動してアダプタを有効にし、**Show Adapters Tab**で切り替えます。<br><br>
+1. パンチダッシュボードで、**コックピット**> **ダッシュボード**> **主な機能**> **Webフック管理を有効**にし、**Webフック管理を有効**にします。<br><br>
+2. 次に、\[**Settings**] > \[**Webhooks Manager**] > \[**Configurations**] > \[**Show Adapters Tab**] に移動してアダプターを有効にし、\[**Show Adapters Tab**] をオンに切り替えます。<br><br>
 3. **Webフックマネージャ**の**設定**タブに移動し、**アダプタ**タブを選択し、**アダプタの作成**をクリックします。<br><br>![][1]<br><br>
 4. アダプターの名前、説明、および管理メールを入力します。アダプターとして **Braze** を選択し、Braze REST API エンドポイントとBraze API キーを入力します。<br><br>
-5. 次に、有効にするイベントを選択します。これらのイベントのリストは、[Available events to sync](#available-events-to-sync)にあります。<br><br>![][3]<br><br>
+5. 次に、有効にするイベントを選択します。これらのイベントのリストは「[同期できるイベント ](#available-events-to-sync)」にあります。<br><br>![][3]<br><br>
 6. **Submit**を押してWebhookを有効にします。
 
-## Braze でのパンチWebhookの作成
+## Braze で Punchh Webhook を作成する
 
-Braze は、ユーザー s をパンチSegmentに、パンチカスタムSegments を使用するwebhookを介して追加できます。
+Braze は、Punchh カスタムセグメントを使用してWebhook 経由でユーザーを Punchh セグメントに追加できます。
 
-1. Punchh でカスタムSegmentを作成し、Punchh Segment ダッシュボード URL に存在する`custom_segment_id` を以下のように書き留めます。古典的またはβSegmentビルダーの両方を使用できます。ただし、classic は最終的に非推奨になるため、ベータは推奨されています。<br><br>パンチプラットフォームで、**ゲスト**> **セグメント**> **カスタムリスト**> **新規カスタムリスト** に移動します。<br><br>![][8]<br><br>
+1. Punchh でカスタムセグメントを作成し、以下に示す Punchh セグメントダッシュボード URL に含まれている`custom_segment_id` をメモします。従来のセグメントビルダーまたはベータセグメントビルダーの両方を使用できます。ただし、classic は最終的に非推奨になるため、ベータは推奨されています。<br><br>Punchh プラットフォームで \[**Guest**] > \[**Segment**] > \[**Custom List**] > \[**New Custom List**] に移動します。<br><br>![][8]<br><br>
 
 2. Braze でWebhook キャンペーンを作成するには、Punchh エンドポイントを使用して、ユーザーをカスタムSegmentにWebhook URL として追加します。ここでは、URL からプルされた`custom_segment_id` と`user_id` をキーと値のペアとして指定できます。<br><br>![][4]<br><br>
 
 3. このWebhookは、単数キャンペーンとして、またはキャンバス内のステップとして設定できます。または、この特殊なパンチSegmentにユーザーs を追加するWebhookが複数のキャンペーンs またはキャンバスで使用される場合は、[テンプレート]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/webhook_template#creating-a-webhook-template) として設定できます。<br><br>
-Webhook内の`user_id` キーは、パンチユーザー IDにマップされます。この識別子は、Braze で作成されたすべてのwebhookに追加して、ユーザーs をパンチカスタムSegmentに追加する必要があります。`punch_user_id` カスタム属性は、[Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/using_liquid/#pre-formatted-variables) を使用して、`user_id` キーの値としてダイナミックな入力できます。`punchh_user_id` カスタム属性は、青色の"plus" アイコンを使用して挿入できます。アイコンは、任意のテンプレートd テキストフィールドの右上にあります。<br><br>![][10]{: style="max-width:65%;"}<br><br>![][11]{: style="max-width:65%;"}<br><br>
+Webhook 内の `user_id` キーは、Punchh ユーザー ID にマッピングされます。ユーザーを Punchh カスタムセグメントに追加するには、Braze で作成されたすべての Webhook にこの ID を追加するする必要があります。`punch_user_id` カスタム属性は、[Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/using_liquid/#pre-formatted-variables) を使用して、`user_id` キーの値としてダイナミックな入力できます。`punchh_user_id` カスタム属性変数を挿入するには、任意のテンプレートテキストフィールドの右上にある青色の「プラス」アイコンを使用します。<br><br>![][10]{: style="max-width:65%;"}<br><br>![][11]{: style="max-width:65%;"}<br><br>
 
-4. Webhookが保存されたら、以下に示すようにユーザーs を同期するために使用できます。たとえば、このBraze Webhook キャンペーンを起動すると、136 人のゲストが「パンチ」カスタムSegmentに追加されます。<br><br>![Brazeとパンチインテグレーションによって保存されたWebhookを使用してユーザーsを同期するサンプル。][7]
+4. Webhook が保存されたら、以下に示すように、ユーザーの同期にこの Webhook を使用できます。たとえば、このBraze Webhook キャンペーンを起動すると、136 人のゲストが「パンチ」カスタムSegmentに追加されます。<br><br>![Braze とPunchh の統合 に伴い、保存された Webhook を使用してユーザーを同期する例。][7]
 
 Brazeでのwebhookの使用方法の詳細については、[Webhookの作成]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/)を参照してください。 
 
@@ -170,17 +170,17 @@ Brazeでのwebhookの使用方法の詳細については、[Webhookの作成]({
 
 #### トリガー
 
-報酬イベントやゲストイベントなど、パンチイベントがBrazeに送信するBraze メッセージング トリガーのユースケースは、[アクション ベースのキャンペーンs]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery#action-based-delivery) または該当するパンチイベントによってトリガーされるキャンバスとして作成できます。
+Braze に送信される Punchh イベント (リワードイベントやゲストイベントなど) によりトリガーされる Braze メッセージングのユースケースは、[アクションベースのキャンペーン]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery#action-based-delivery)、または該当する Punchh イベントによってトリガーされるキャンバスとして作成できます。
 
-トリガーを追加すると、Braze で作成された行動の一覧がプルアップされます。キャンペーンまたはキャンバスをトリガーし、イベントを記録したユーザーに送信するイベントを選択します。
+トリガーを追加すると、Braze で作成されたイベントのリストが取得されます。キャンペーンまたはキャンバスをトリガーし、イベントを記録したユーザーに送信するイベントを選択します。
 
 ![][12]
 
-プロパティー・フィルターs を追加して、トリガーの実行イベントをさらにフィルターできます。たとえば、メッセージは、顧客 トリガーが"checkins_gift"event の場合にのみトリガーされます。この場合、アプリのroved イベントプロパティは`true` です。これは、すべてのユースケースにアプリ使用できるわけではないオプション機能です。 
+トリガーイベントをさらに絞り込むには、プロパティフィルターを追加できます。たとえば、承認済みイベントプロパティが `true` である「checkins_gift」イベントを顧客がトリガーした場合にのみ、メッセージをトリガーします。これはオプションの機能であり、すべてのユースケースに適用できるわけではありません。 
 
 #### セグメンテーション
 
-多くの場合、パンチイベントによってトリガーされているBraze キャンペーン s とキャンバスは"すべてのユーザー s" オーディエンスに設定できます。これは、これらのイベントをトリガーするユーザー s のセグメンテーションがパンチ内で決定されるためです。ただし、顧客 は、イベントによってBraze メッセージング トリガーを受け取るユーザーs のオーディエンスをさらに絞り込むために、キャンバスコンポーザーの**Target オーディエンス s** セクションまたは**Entry オーディエンス** にフィルターs とSegments を追加します。 
+多くの場合、Punchh イベントによってトリガーされる Braze キャンペーンとキャンバスには、「すべてのユーザー」オーディエンスを設定できます。これは、これらのイベントをトリガーするユーザーのセグメンテーションがが Punchh 内で決定するためです。ただし、イベントによってトリガーされる Braze メッセージを受信するユーザーからなるオーディエンスをさらに絞り込む場合は、キャンペーン作成画面の \[**ターゲットオーディエンス**] セクションまたはキャンバス作成画面の \[**エントリオーディエンス**] で、フィルターとセグメントを追加します。 
 
 ### ユースケース
 
@@ -188,127 +188,127 @@ Brazeでのwebhookの使用方法の詳細については、[Webhookの作成]({
 {% tab サインアップ %}
 #### 登録キャンペーン
 
-オファーが添付されているサインアップキャンペーンのBraze設定を使用する場合、Punchh内でサインアップギフトキャンペーンを設定し、Brazeでウェルカムメッセージを設定する必要があります。 
+オファーが添付されている登録キャンペーンに Braze 設定を使用する場合、Punchh 内で登録ギフティングキャンペーンを設定し、Braze でウェルカムメッセージを設定する必要があります。 
 
-Punchh はサインアップキャンペーンに実行遅延を追加することを推奨します。そのため、Braze はゲストイベントに基づいてウェルカムメッセージを最初にトリガーできます。ユーザーに贈られたことを知らせるフォローアップメッセージを送りたい場合は、報酬の出来事に基づいてトリガーすることができます。
+Punchh はサインアップキャンペーンに実行遅延を追加することを推奨します。そのため、Braze はゲストイベントに基づいてウェルカムメッセージを最初にトリガーできます。ギフトが贈られたことをユーザーに通知するフォローアップメッセージを送信する場合は、リワードイベントに基づいてこれをトリガーできます。
 
-サインアップキャンペーンでは、すべてのサインアップをSegmentに使用できるため、カスタムBraze Segmentは必要ありません。
+登録キャンペーンの場合、セグメントに「All signed up」を使用できるので、カスタム Braze セグメントは必要ありません。
 
-必要なパンチ構成:
+必要な Punchh 設定:
 - キャンペーン:サインアップ 
-- セグメント情報:登録済み
-- 報酬:顧客選択
+- セグメント:登録済み
+- リワード:顧客が選択
 必要なイベント:
-- 報奨イベント
+- リワードイベント
 - ゲストイベント
 考慮事項:
 - 実行遅延は、ゲストが5 ～10 分の遅延を追加することをお勧めします
 
-![ユーザー Segmentがパンチで設定され、ゲストがロイヤルティプログラムにサインアップします。この後、ゲストイベント(トリガー の場合) がed になり、Braze メッセージング キャンペーンがトリガーed になります。次に、パンチ・サインアップ・ギフト・キャンペーンは、10分後にトリガーされ、報酬・イベントとオプションのフォローアップ・メッセージがトリガーされます。]({% image_buster /assets/img/punchh/usecase3.png %})
+![ユーザーセグメントが Punchh で設定され、ゲストがロイヤルティプログラムに登録されます。この後、ゲストイベント (トリガーされる場合) とBraze メッセージングキャンペーンがトリガーされます。次に、10分後に Punchh 登録ギフティングキャンペーンがトリガーされ、リワードイベントとオプションのフォローアップメッセージがトリガーされます。]({% image_buster /assets/img/punchh/usecase3.png %})
 
 {% endtab %}
 {% tab マスオファー %}
 #### マスオファーキャンペーン
 
-プレゼントに大量のオファーキャンペーンを使用する場合、パンチとBrazeのメッセージング キャンペーン内で大量のオファーキャンペーンを設定する必要があります。
+ギフティングにマスオファーキャンペーンを使用する場合、マスオファーキャンペーンは Punchh 内で設定し、メッセージングキャンペーンは Braze で設定する必要があります。
 
-Braze Segmentをキャンペーンに利用したり、Brazeから通信を送信したりする場合は、パンチキャンペーンに[カスタムパンチSegment]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/punchh/#step-3-create-punchh-webhook-in-braze)が必要になります。 
+Braze セグメントをキャンペーンに利用する場合や、Punchh プラットフォームでゲストにギフトを送る前に Braze からコミュニケーションを送信する場合には、Punchh ギフティングキャンペーンに[カスタム Punchh セグメント]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/punchh/#step-3-create-punchh-webhook-in-braze)が必要になります。 
 
-Brazeでこのオファーを受信するユーザーsのSegmentを作成することは、パンチ内で使用できない属性を使用する場合にのみ推奨されます。それ以外の場合は、Punchh セグメンテーションを使用できます。Braze メッセージング キャンペーンは、ユーザーが報酬(Punchh によってトリガーされる報酬事象)を受け取ることによって、アクションベースのキャンペーン トリガーとして作成されます。
+Braze でこのオファーを受け取るユーザーのセグメントを作成することは、Punchh 内で使用できない属性を使用する場合にのみ推奨されます。それ以外の場合は、Punchh セグメンテーションを使用できます。Braze メッセージング キャンペーンは、ユーザーが報酬(Punchh によってトリガーされる報酬事象)を受け取ることによって、アクションベースのキャンペーン トリガーとして作成されます。
 
-必要なパンチ構成:
+必要な Punchh 設定:
 - キャンペーン:マスオファー
-- セグメント情報:カスタムリストまたは顧客の選択肢
-- 報酬:顧客選択
+- セグメント:カスタムリストまたは顧客が選択
+- リワード:顧客が選択
 
-**セグメンテーションとギフトにパンチ、メッセージングにBrazeを使用:**<br>
-たとえば、$2 off 報酬は、パンチ内で設定可能なSegmentに送信され、メッセージングはBraze 経由で送信されます。<br>
-![ユーザー Segmentはパンチで設定でき、ユーザー sはパンチマスオファーキャンペーンを通じてプレゼントを受け取ります。次に、報酬事象がトリガーされ、次にBraze メッセージング キャンペーンがトリガーされます。]({% image_buster /assets/img/punchh/usecase6.png %}){: style="max-width:80%;"}
+**セグメンテーションとギフティングに Punchh を使用し、メッセージングに Braze を使用する:**<br>
+たとえば、2ドル割引リワードが、Punchh 内で設定可能なセグメントに送信され、メッセージングは Braze で送信されます。<br>
+![ユーザーセグメントは Punchh で設定可能であり、ユーザーは Punchh マスオファーキャンペーンでギフトを受け取ります。次に、リワードイベントがトリガーされ、その後 Braze メッセージングキャンペーンががトリガーされます。]({% image_buster /assets/img/punchh/usecase6.png %}){: style="max-width:80%;"}
 
-**ギフトにBraze セグメンテーションとメッセージング、パンチを使用する:**<br>
+**ギフティングに Braze セグメンテーションおよびメッセージングと Punchh を使用する:**<br>
 たとえば、パンチでは利用できない属性 s を持つSegmentに送信される$2 off 報酬 とメッセージング です。<br>
-![ユーザー SegmentはBrazeで設定でき、その後、BrazeからBraze Segmentにメッセージを送信できます。次に、ユーザーsは、パンチカスタムSegmentに、Segmentとユーザー IDを備えたBraze Webhookを通して送られる。その後、ユーザーはパンチマスオファーキャンペーンで特注のSegmentでプレゼントを受け取ります。この後の報酬事象はトリガー ed.]({% image_buster /assets/img/punchh/usecase5.png %}){: style="max-width:80%;"}
+![ユーザーセグメントは Braze で設定でき、メッセージは Braze間セグメントから送信できます。次に、ユーザーはセグメントとユーザー ID を使用して Braze Webhook から Punchh カスタムセグメントに送信されます。その後、ユーザーはカスタムセグメントが設定された Punchh マスオファーキャンペーンでギフトを受け取ります。この後、リワードイベントがトリガーされます。]({% image_buster /assets/img/punchh/usecase5.png %}){: style="max-width:80%;"}
 
-**ギフトまたはメッセージング、またはその両方にBraze セグメンテーションとパンチを使用する:**<br>
-たとえば、$2 off 報酬は、Punchh で使用できない属性 s を持つSegmentに送信されますが、メッセージングは必要ありません。または、メッセージングはPunchh 経由で送信できます(すべてのゲストがPunchh に存在する必要があることに注意してください)。<br>
-![ユーザー SegmentはBraze で設定でき、ユーザーs はSegment とユーザー ID のBraze Webhookを介してパンチカスタムSegmentに送信されます。その後、ユーザーはパンチマスオファーキャンペーンで特注のSegmentでプレゼントを受け取ります。この後の報酬事象はトリガー ed.]({% image_buster /assets/img/punchh/usecase4.png %})
+**ギフティングとメッセージングのいずれかまたは両方に、Braze セグメンテーションおよびメッセージングと Punchh を使用する:**<br>
+たとえば、Punchh では使用できない属性を持つセグメントに2ドル割引リワードが送信されますが、メッセージングが不要であるか、メッセージングを Punchh から送信できます (すべてのゲストが Punchh に存在している必要があることに注意してください)。<br>
+![ユーザーセグメントは Braze で設定でき、ユーザーはセグメントとユーザー ID を使用して Braze Webhook を介してPunchh カスタムセグメントに送信されます。その後、ユーザーはカスタムセグメントが設定された Punchh マスオファーキャンペーンでギフトを受け取ります。この後、リワードイベントがトリガーされます。]({% image_buster /assets/img/punchh/usecase4.png %})
 
 {% endtab %}
 {% tab 定期的なマスオファー %}
 #### 定期的なマスオファーキャンペーン
 
-定期的なマスオファーキャンペーンをギフトに使用する場合は、パンチ内にマスオファーキャンペーンを設定し、Brazeにメッセージング キャンペーンを設定する必要があります。顧客がBraze セグメンテーションを使用する場合は、パンチカスタムSegmentが必要になります(パンチ内で属性を使用できない場合のみ推奨)。それ以外の場合は、パンチセグメンテーションを使用でき、Braze メッセージング キャンペーンは報酬の事象に基づいてトリガーされます。
+定期的なマスオファーキャンペーンをギフティングに使用する場合は、Punchh 内でマスオファーキャンペーンを設定し、Braze でメッセージング キャンペーンを設定する必要があります。顧客が Braze セグメンテーションを使用する場合は、Punchh カスタムセグメントが必要です (Punchh 内で属性を使用できない場合のみ推奨)。それ以外の場合は、Punchh セグメンテーションを使用できます。Braze メッセージング キャンペーンはリワードイベントに基づいてトリガーされます。
 
-必要なパンチ構成:
+必要な Punchh 設定:
 - キャンペーン:定期的なマスオファー
-- セグメント情報:カスタムリストまたは顧客の選択肢
-- 報酬:顧客選択
+- セグメント:カスタムリストまたは顧客が選択
+- リワード:顧客が選択
 考慮事項:
-- キャンペーンID とキャンペーンの名前は、イベントのイベントプロパティとしてBraze に送信されます。キャンペーンを受信するオーディエンスをさらにフィルターするためにBrazeでパンチキャンペーン 識別子を使用する場合は、キャンペーンID が毎日変更されるため、キャンペーンの名前を使用する必要があります。
+- キャンペーンID とキャンペーンの名前は、イベントのイベントプロパティとしてBraze に送信されます。キャンペーンを受け取るオーディエンスをさらに絞り込むために Braze で Punchh キャンペーン識別子を使用する場合、キャンペーン ID は毎日変更されるため、キャンペーン名を使用する必要があります。
 
 {% endtab %}
-{% tab 通知によるチェックイン後のオファー %}
+{% tab 通知を使用するチェックイン後オファー %}
 #### 通知との事後チェックインオファーキャンペーン
 
-チェックイン後のオファーキャンペーンを利用する場合、Brazeはプレゼントに関する通知を送付し、ゲストがチェックインを行うと、パンチ後のチェックインキャンペーンからプレゼントされます。したがって、チェックイン後のオファーキャンペーンは、パンチとBrazeのメッセージング キャンペーン内で設定する必要があります(キャンペーンを顧客に通知する場合)。
+チェックイン後オファーキャンペーンを利用する場合、Braze はギフティングに関する通知を送信します。ゲストがチェックインすると、Punchh のチェックイン後オファーキャンペーンからギフトが送られます。したがって、チェックイン後オファーキャンペーンは Punchh 内で設定し、メッセージングキャンペーンは Braze 内で設定する必要があります (顧客にキャンペーンについて通知する場合)。
 
-必要なパンチ構成:
+必要な Punchh 設定:
 - キャンペーン:チェックイン後のオファー
-- セグメント情報:カスタムリスト
-- 報酬:顧客選択
+- セグメント:カスタムリスト
+- リワード:顧客が選択
 
-例えば、今週末に来訪することを客に知らせるメールは、パンチでは利用できない属性sのあるSegmentをダブルポイントする。Brazeからの適格なチェックインとオプションのメッセージングの後に、パンチがこのSegment点をプレゼントします。 
+たとえば、この週末に訪問するゲストに対し、Punchh では使用できない属性を持つセグメントに対するポイントが2倍になることを通知するメールなどです。対象となるチェックインの完了後に、このセグメントにポイントが与えられ、Braze からオプションのメッセージが送信されます。 
 
-![ユーザー SegmentはBrazeで設定され、メッセージはチェックイン後のBrazeのキャンペーンから送信されます。次に、該当するユーザーsが、パンチカスタムSegmentに、Segmentとユーザー IDのBraze Webhookを介して送信されます。最後に、カスタムSegmentの修飾ユーザーは、チェックイン後のキャンペーン]({% image_buster /assets/img/punchh/update7.png %}) を通じてギフトとオプションメッセージをチェックインして受け取ります。
+![ユーザー SegmentはBrazeで設定され、メッセージはチェックイン後のBrazeのキャンペーンから送信されます。次に、対象のユーザーは、セグメントとユーザー ID を使用して Braze Webhook を介して Punchh カスタムセグメントに送信されます。最後に、カスタムセグメント内の対象のユーザーがチェックインし、チェックイン後オファーキャンペーンでギフトを受け取り、オプションのメッセージを受信します。]({% image_buster /assets/img/punchh/update7.png %})
 
 {% endtab %}
-{% tab 通知のない事後チェックインオファー %}
-#### チェックイン後のオファーキャンペーン(通知なし)
+{% tab 通知を使用しないチェックイン後オファー %}
+#### 通知を使用しないチェックイン後オファーキャンペーン
 
-キャンペーンは、最初に顧客に通知しないチェックイン後のオファーキャンペーンを使用する場合、ギフト(オプションメッセージング)を付与し、Braze内の通知をトリガーします。したがって、チェックイン後のオファーキャンペーンはPunchh 内で設定する必要がありますが、カスタムリストは必要ありません。代わりに、パンチ内で希望するSegmentを選択することができます。 
+最初に顧客に通知を送信しないチェックイン後オファーキャンペーンを使用する場合、このキャンペーンはギフトを与え (オプションのメッセージング) Braze 内で通知をトリガーします。したがって、チェックイン後のオファーキャンペーンはPunchh 内で設定する必要がありますが、カスタムリストは必要ありません。代わりに、Punchh 内で使用するセグメントを選択できます。 
 
-必要なパンチ構成:
+必要な Punchh 設定:
 - キャンペーン:チェックイン後のオファー
-- セグメント情報:顧客選択
-- 報酬:顧客選択
+- セグメント:顧客が選択
+- リワード:顧客が選択
 
-例えば、パンチで利用可能なSegmentに、驚きと喜びのBraze キャンペーンが送られ、来客の来訪に感謝し、次回の訪問から2ドルで報酬する。
+たとえば、Punchh で使用可能なセグメントに、顧客に対し訪問を感謝し、次回の訪問で2ドル割引を提供する予告なしのサプライズ Braze キャンペーンが送信されます。
 
-![該当するユーザー Segmentはパンチ内で設定でき、該当するユーザーがチェックインし、パンチ後チェックインキャンペーンを通じてギフトを受け取ります。この後、報酬事象がトリガーされ、ゲストにBraze.]({% image_buster /assets/img/punchh/usecase2.png %})から送信された報酬を通知するリコールメッセージが送信されます。
+![該当するユーザー Segmentはパンチ内で設定でき、該当するユーザーがチェックインし、パンチ後チェックインキャンペーンを通じてギフトを受け取ります。この後、リワードイベントがトリガーされ、Braze から送信されたリワードをゲストに通知する呼び戻しメッセージが送信されます。]({% image_buster /assets/img/punchh/usecase2.png %})
 
 {% endtab %}
 {% tab 記念日 %}
 #### 記念日キャンペーン 
 
-記念日キャンペーンをご利用の際は、まずパンチキャンペーンから記念日のユーザーをプレゼントします。このギフト(報酬行事)は、ギフトのユーザーを通知するBraze内のメッセージング キャンペーンをトリガーします。そのため、カスタムリストは必要ありません。代わりに、パンチ内のSegmentと記念日の設定を選択することができます。
+記念日キャンペーンを利用すると、最初に Punchh キャンペーンから記念日のギフトがユーザーに贈られます。このギフティング (リワードイベント) により、ユーザーにギフトが与えられたことを通知するメッセージングキャンペーンが Braze 内でトリガーされます。そのため、カスタムリストは必要ありません。代わりに、Punchh 内でセグメントと記念日設定を選択できます。
 
-必要なパンチ構成:
+必要な Punchh 設定:
 - キャンペーン:記念日キャンペーン
-- セグメント情報:顧客選択
-- 報酬:顧客選択
+- セグメント:顧客が選択
+- リワード:顧客が選択
 考慮事項:
-- 登録プレゼント月
-- 存続期間(誕生日報酬はどのくらい有効ですか?)
-- 経常キャンペーン、必要スケジュール 
+- 登録月のギフティング
+- 存続期間 (誕生日リワードが有効である期間の長さは?)
+- 定期的なキャンペーン、スケジュールが必要 
 
-![オプションのSegmentはパンチ内で作成でき、該当するユーザーはパンチ・アニバーサリー・キャンペーンを通じて報酬を受信します。この後、報酬事象がトリガーされ、ゲストにBraze.]({% image_buster /assets/img/punchh/usecase1.png %})から送信された報酬を通知するリコールメッセージが送信されます。
+![オプションのセグメントは Punchh 内で作成でき、対象のユーザーは Punchh 記念日キャンペーンからリワードを受け取ります。この後、リワードイベントがトリガーされ、Braze から送信されたリワードをゲストに通知する呼び戻しメッセージが送信されます。]({% image_buster /assets/img/punchh/usecase1.png %})
 
 {% endtab %}
-{% tab リコール %}
+{% tab 呼び戻し %}
 #### 回収キャンペーン
 
-非アクティブに基づいてユーザーs をターゲットにする場合は、リコールキャンペーンを使用できます。顧客はパンチ内にSegmentとキャンペーンを作成できますが、メッセージングにはBrazeを使用します。
+休眠状態に基づいてユーザーをターゲット設定するときには、呼び戻しキャンペーンを使用できます。顧客は Punchh 内でセグメントとキャンペーンを作成できますが、メッセージングには Braze を使用できます。
 
 Braze で作成されたセグメンテーションを使用する場合は、非アクティブに基づいた[カスタムPunchh Segment]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/punchh/#step-3-create-punchh-webhook-in-braze) を定期的な一括オファーキャンペーンにアタッチできます。
 
-必要なパンチ構成:
+必要な Punchh 設定:
 - キャンペーン:回収キャンペーン
-- セグメント情報:顧客選択
-- 報酬:顧客選択
+- セグメント:顧客が選択
+- リワード:顧客が選択
 考慮事項:
 - キャンペーンはスケジュールで実行されます
 
-![オプションのSegmentはパンチ内で作成でき、該当するユーザーはパンチリコールキャンペーンを介して報酬を受信します。この後、報酬事象がトリガーされ、ゲストにBraze.]({% image_buster /assets/img/punchh/usecase.png %})から送信された報酬を通知するリコールメッセージが送信されます。
+![オプションのSegmentはパンチ内で作成でき、該当するユーザーはパンチリコールキャンペーンを介して報酬を受信します。その後、リワードイベントがトリガーされ、Braze から送られたリワードをゲストに通知する呼び戻しメッセージが送信されます。.]({% image_buster /assets/img/punchh/usecase.png %})
 
 {% endtab %}
 {% endtabs %}
@@ -320,7 +320,7 @@ Braze で作成されたセグメンテーションを使用する場合は、
 [4]: {% image_buster /assets/img/punchh/punchh4.png %}
 [5]: {% image_buster /assets/img/punchh/punchh5.png %}
 [7]: {% image_buster /assets/img/punchh/punchh6.png %}
-[6]: {{site.baseurl}}/api/basics?redirected=true#エンドポイントs
+[6]: {{site.baseurl}}/api/basics?redirected=true#endpoints
 [8]: {% image_buster /assets/img/punchh/update1.png %}
 [9]: {% image_buster /assets/img/punchh/update2.png %}
 [10]: {% image_buster /assets/img/punchh/update3.png %}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/talonone.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/talonone.md
index 9ba9041489d..54b8b29b50c 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/talonone.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/talonone.md
@@ -19,7 +19,7 @@ BrazeとTalon.Oneの統合により、Talon.Oneによって生成されたコー
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-|Talon.One アカウント | このパートナーシップを利用するにはTalon.Oneアカウントが必要です。 |
+|Talon.One アカウント | このパートナーシップを活用するには、Talon.One アカウントが必要です。 |
 |Talon.One API キー | Talon.One で、**設定** > **開発者設定** の下に、統合のための Braze サードパーティ API キーを作成します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -30,10 +30,10 @@ Talon.One **_には_** 1分あたり2,500メッセージの最大レート制限
 ## 統合
 
 1. [Talon.Oneドキュメント](https://docs.talon.one/docs/dev/technology-partners/braze)にアクセスして、統合の設定方法、Talon.One APIクーポンエンドポイントの使用方法、およびBrazeメッセージに必要なコネクテッドコンテンツテンプレートの場所についてのガイダンスを確認してください。
-2. 他の機能Talon.One、ロイヤルティポイントや紹介などを利用するには、次の記事をご覧ください:
-  - [ロイヤルティポイントをBrazeに追加](https://docs.talon.one/docs/dev/technology-partners/braze/adding-loyalty-points-braze)
-  - [ロイヤルティの台帳をBrazeで取得する](https://docs.talon.one/docs/dev/technology-partners/braze/receiving-loyalty-ledger-braze)
-  - [Brazeを通じてクーポンを作成する](https://docs.talon.one/docs/dev/technology-partners/braze/creating-coupons-braze)
-  - [Brazeを介して紹介を作成する](https://docs.talon.one/docs/dev/technology-partners/braze/creating-referrals-braze)
-  - [Brazeを使用して誕生日プロモーションを作成する](https://docs.talon.one/docs/dev/technology-partners/braze/bday-promotion-braze)
+2. Talon.One が提供するその他の機能 (ロイヤルティポイントや紹介) を利用するには、次の記事を参照してください。
+  - [ロイヤルティポイントを Braze に追加する](https://docs.talon.one/docs/dev/technology-partners/braze/adding-loyalty-points-braze)
+  - [Braze でロイヤルティ元帳を取得する](https://docs.talon.one/docs/dev/technology-partners/braze/receiving-loyalty-ledger-braze)
+  - [Braze を介してクーポンを作成する](https://docs.talon.one/docs/dev/technology-partners/braze/creating-coupons-braze)
+  - [Braze を介して紹介を作成する](https://docs.talon.one/docs/dev/technology-partners/braze/creating-referrals-braze)
+  - [Brazeを介して誕生日プロモーションを作成する](https://docs.talon.one/docs/dev/technology-partners/braze/bday-promotion-braze)
 
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/viralsweep.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/viralsweep.md
index 3e2b763f400..42e2a88750b 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/viralsweep.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/viralsweep.md
@@ -12,13 +12,13 @@ search_tag: Partner
 
 > [ViralSweep](https://viralsweep.com)は、懸賞、コンテスト、インスタントウィン、ウェイトリスト、紹介プロモーションなどのデジタルマーケティングプロモーションを、ブランドが構築、実行、管理できるようにするソフトウエアサービスです。 
 
-Braze とViralSweep のインテグレーションでは、ViralSweep プラットフォームで懸賞やコンテストを開催し(メールとSMS リストを拡大)、懸賞やコンテストエントリをBraze に送信してキャンペーンやキャンバスで使用できます。 
+Braze と ViralSweep の統合により、ViralSweep プラットフォームで懸賞とコンテストを開催し (メールと SMS のリストが増加します)、キャンペーンまたはキャンバスで使用できるように懸賞とコンテストへの参加情報を Braze に送信できます。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| ViralSweepアカウント | 事業計画を活用したViralSweep勘定は、この提携の前倒しタグeをとることが求められる。 |
+| ViralSweep アカウント | このパートナーシップを活用するためには、ビジネスプランを利用している ViralSweep アカウントが必要です。 |
 | Braze REST API キー | すべてのユーザーデータおよびメール権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
 |Braze REST エンドポイント | REST エンドポイントのURL。エンドポイントは、[インスタンス]({{site.baseurl}}/api/basics/#endpoints)のBraze URLによって異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -31,45 +31,45 @@ ViralSweep で、**Integrations > Email & SMS > Add Service** に移動し、**B
 
 ![][1]
 
-### ステップ2 :Braze認証情報の追加
+### ステップ2 :Braze 認証情報を追加する
 
-統合設定ウィンドウで、Braze REST API キーとREST エンドポイントを指定します。指定するエンドポイントに`https://` が含まれていないことを確認します(`dashboard-03.braze.com` など)。 
+統合設定ウィンドウで、Braze REST API キーと REST エンドポイントを指定します。指定するエンドポイントに`https://` が含まれていないことを確認します(`dashboard-03.braze.com` など)。 
 
-![ViralSweep サービスインテグレーションページで、ユーザーにBraze API キーとBraze ダッシュボードのURL を入力します。][2]{: style="max-width:40%;"}
+![ユーザーに Braze API キーと Braze ダッシュボード URL の入力を求める ViralSweep サービス統合ページ。][2]{: style="max-width:40%;"}
 
-**Connect**をクリックします。
+\[**Connect**] をクリックします。
 
-### ステップ3 :Braze認証情報の追加
-あなたはつながっています!プロモーションがBrazeに接続され、ViralSweepによって収集されたすべてのエントリーが自動的にBrazeに送信されます。
+### ステップ3 :Braze 認証情報を追加する
+接続が完了しました。プロモーションがBrazeに接続され、ViralSweepによって収集されたすべてのエントリーが自動的にBrazeに送信されます。
 
 ## よくある質問
 
-### ヴィラルスイープがBrazeに渡したフィールドは?
+### ViralSweep から Braze にはどのフィールドが渡されますか?
 - 名
 - 姓
 - メールアドレス
 - 住所
-- アドレス2
+- Address 2
 - 市区町村
 - 状態
-- ジップ
+- Zip
 - 国
 - 生年月日
 - 電話
 - プロモーションID
-- 照会リンク
+- Referral link
 - 追跡キャンペーンの名前
 
-### ViralSweepは更新 サブスクライバーしますか?
-そうです。プロモーションを実行し、ViralSweep が誰かをBraze に渡した場合、将来別のプロモーションを実行し、同じ人物が入力すると、その人物の情報は自動的にBraze で更新d になります(新しい情報が提供されている場合)。主に紹介URLは、入力したプロモーションごとに最新のURLが付いた更新dとなり、プロモーションID フィールドには入力したすべてのプロモーションのIDが含まれます。
+### ViralSweep ではサブスクライバーが更新されますか?
+そうです。プロモーションを実行し、ViralSweep が誰かをBraze に渡した場合、将来別のプロモーションを実行し、同じ人物が入力すると、その人物の情報は自動的にBraze で更新d になります(新しい情報が提供されている場合)。主に、紹介 URL は、入力するプロモーションごとに最新の URL で更新され、プロモーション ID フィールドにはこれまでに入力したすべてのプロモーションの ID が含まれます。
 
 ## トラブルシューティング
 
 Brazeに接続していて、アカウントに追加されていない場合は、次のような理由が考えられます。
 
-- **メールはBrazeにすでに存在します**<br>
+- **メールがすでに Braze に存在している**<br>
 プロモーションに入力されたメールの住所は、すでにあなたのBrazeアカウントに登録されている可能性があるため、再度追加されることはありません。その連絡先に新しい情報が提供された場合にのみ更新 d となります。<br><br>
-- **ViralSweepに入力済みのメール**<br>
+- **メールがすでに ViralSweep に入力されている**<br>
 プロモーションに入力されたメールの住所はすでに入力されているため、再度Brazeに渡されることはありません。プロモーションにすでに参加した後にBrazeインテグレーションを設定すると、このアプリが表示されます。
 
 [1]: {% image_buster /assets/img/viralsweep/connect.gif %}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify.md
index af5e7938ec9..e378d887b4d 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify.md
@@ -1,16 +1,16 @@
 ---
-nav_title: バウチャリファイ
+nav_title: Voucherify
 noindex: true
 alias: /partners/voucherify/
 layout: dev_guide
-guide_top_header: "バウチャリファイ"
+guide_top_header: "Voucherify"
 guide_top_text: "Voucherifyは、パーソナライズされたクーポン、ギフトカード、ロイヤルティカード、紹介コードなどを、ユーザーがBrazeアカウントを通じて自動的に送信できるオールインワンのプロモーション・プラットフォームであり、あらゆるステップで利用状況やキャンペーンの成長を追跡できる。"
-description: "このランディングページでは、Voucherifyの統合方法、Connected Contentを使ったデータの取得方法、カスタム属性を使った配布方法、Voucherifyとプロモーションコードのリストなど、Voucherifyに関するあらゆることを紹介している。"
+description: "このランディングページは、統合方法、コネクテッドコンテンツを使用したデータの取得方法、カスタム属性を使用したディストリビューション、Voucherifyおよびプロモーションコードリストなど、Voucherify に関するあらゆる情報のホームページです。"
 guide_featured_list:
-- name: バウチャリファイ
+- name: Voucherify
   link: /docs/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify/
   image: /assets/img/braze_icons/percent-02.svg
-- name: コネクテッド・コンテンツを通じてデータを取得する
+- name: コネクテッドコンテンツを使用したデータの取得
   link: /docs/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content/
   image: /assets/img/braze_icons/link-05.svg
 - name: カスタム属性を持つディストリビューション
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify.md
index 6c035a0e298..2823cb4111c 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify.md
@@ -1,6 +1,6 @@
 ---
-nav_title: バウチャリファイ
-article_title: バウチャリファイ
+nav_title: Voucherify
+article_title: Voucherify
 page_order: 1
 alias: /partners/voucherify/voucherify/
 description: "この参考記事では、BrazeとVoucherifyの提携について概説している。Voucherifyは、パーソナライズされたクーポン、ギフトカード、ロイヤルティカード、紹介コードなどを、ユーザーがBrazeのアカウントを通じて自動的に送信できるオールインワンのプロモーションプラットフォームで、あらゆるステップで利用状況やキャンペーンの成長を追跡できる。"
@@ -9,15 +9,15 @@ search_tag: Partner
 
 ---
 
-# バウチャリファイ
+# Voucherify
 
-> [Voucherifyは](https://www.voucherify.io/)、パーソナライズされたキャンペーンとロイヤリティ・プログラムを可能にするオールインワンのプロモーション・プラットフォームで、ユーザーのエンゲージメントとリテンションを促進する。 
+> [Voucherifyは](https://www.voucherify.io/)、パーソナライズされたキャンペーンとロイヤルティプログラムを可能にするオールインワンのプロモーションプラットフォームであり、ユーザーのエンゲージメントとリテンションを促進します。 
 
 <iframe src="https://player.vimeo.com/video/745340934?h=17ceae8c3c" width="640" height="360" frameborder="0" allow="autoplay; fullscreen; picture-in-picture" allowfullscreen></iframe>
 
-BrazeとVoucherifyの統合により、ユニークなコードを送信することで、プロモーションキャンペーンを拡大することができる：
+Braze と Voucherify の統合により、以下の機能を使用して独自のコードを送信することで、プロモーションキャンペーンを拡大できます。
 
-- [コネクテッド・コンテンツ]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content)Braze Connected Contentを通じてBrazeキャンペーンにユニークなコードを追加する。この機能を使えば、Voucherifyの割引クーポン、ギフトカードキャンペーン、ポイントカード、紹介コードを使うことができる。
+- [コネクテッドコンテンツ]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content):Braze コネクテッドコンテンツで Braze キャンペーンに独自のコードを追加します。この機能を使えば、Voucherifyの割引クーポン、ギフトカードキャンペーン、ポイントカード、紹介コードを使うことができる。
 - [カスタム属性]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes)：カスタム属性により、Voucherify独自のクーポン、ギフトカード、ロイヤルティカード、紹介コードをBrazeのユーザープロファイルに割り当てることができる。その結果、メールキャンペーンで添付コードや属性を送信し、ユーザーと共有することができる。
 - [プロモーションコード一覧]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_using_braze_promotion_codes_list)：Voucherifyが生成したプロモーションコードを使い、Brazeにアップロードする。
 
@@ -31,7 +31,7 @@ BrazeとVoucherifyの統合により、ユニークなコードを送信する
 
 ## 統合
 
-Voucherifyの統合に関する追加リソースについては、以下の記事を参照されたい：
-- [Braze Connected Contentでデータを取得する]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content)
+Voucherify 統合に関するその他のリソースについては、次の記事を参照してください。
+- [Braze コネクテッドコンテンツ を使用したデータの取得]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content)
 - [Brazeのカスタム属性を使ったディストリビューション]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes)
 - [Brazeのプロモーションコードを使用する]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_using_braze_promotion_codes_list)
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes.md
index f6d88ee85ac..2db1f3dd300 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes.md
@@ -1,22 +1,22 @@
 ---
 nav_title: カスタム属性を持つディストリビューション
-article_title: Voucherifyを使用したカスタム属性の配布
+article_title: Voucherify でカスタム属性を使用するディストリビューション
 page_order: 3
 alias: /partners/voucherify/custom_attributes/
-description: "このリファレンス記事は、BrazeとVoucherifyの統合について説明しています。Brazeの統合により、BrazeメッセージでVoucherifyコードを送信できます。"
+description: "このリファレンス記事では、Braze と Voucherify の統合について説明しています。Brazeの統合により、BrazeメッセージでVoucherifyコードを送信できます。"
 page_type: partner
 search_tag: Partner
 ---
 
 # カスタム属性を持つディストリビューション
 
-> Brazeの統合により、BrazeメッセージでVoucherifyコードを送信できます。このリファレンス記事では、Brazeのカスタム属性をVoucherifyの配信で使用する方法について説明します。
+> Brazeの統合により、BrazeメッセージでVoucherifyコードを送信できます。このリファレンス記事では、Voucherify ディストリビューションで Braze のカスタム属性を使用する方法について説明します。
 
 {% alert tip %}
-Voucherifyの配布でBrazeのカスタム属性を使用する前に、BrazeユーザーをVoucherifyのダッシュボードに追加する必要があります。Brazeコネクテッドコンテンツを使用して、ユーザーを同期したり、CSVやAPIを通じて顧客をインポートしたりできます。[Voucherify](https://support.voucherify.io/article/67-how-to-import-my-customers) について詳しく知るには、こちらをご覧ください。
+Voucherify ディストリビューションで Braze のカスタム属性を使用する前に、Braze ユーザーを Voucherify ダッシュボードに追加する必要があります。Braze コネクテッドコンテンツを使用して、ユーザーを同期したり、CSV や API を使用して顧客をインポートしたりできます。[Voucherify](https://support.voucherify.io/article/67-how-to-import-my-customers) について詳しく知るには、こちらをご覧ください。
 {% endalert %}
 
-Braze のカスタム属性を使用すると、ユーザープロファイルのカスタム属性に Voucherify コードを割り当てることができます。ユニークなクーポン、ギフトカード、ロイヤルティカード、および紹介コードを使用できます。まず、VoucherifyをBrazeに接続し、Voucherifyで配布を作成し、最後にBrazeでカスタム属性スニペットをメッセージテンプレートに含めたキャンペーンを作成します。
+Braze のカスタム属性を使用すると、ユーザープロファイルのカスタム属性に Voucherify コードを割り当てることができます。ユニークなクーポン、ギフトカード、ロイヤルティカード、および紹介コードを使用できます。まず Voucherify を Braze に接続し、Voucherify でディストリビューションを作成し、最後に Braze でメッセージテンプレートのカスタム属性スニペットを使用したキャンペーンを作成します。
 
 ## ステップ1:BrazeにVoucherifyアカウントを接続する
 
@@ -36,7 +36,7 @@ Braze のカスタム属性を使用すると、ユーザープロファイル
 
 接続されると、Brazeのユーザープロファイルのカスタム属性にコードを割り当てる新しいVoucherify [配布](https://support.voucherify.io/article/19-how-does-the-distribution-manager-work)を開始できます。後で、受け取った属性をコードと一緒にBrazeキャンペーンで使用できます。
 
-配布を設定する前に、BrazeユーザーをVoucherifyダッシュボードに追加する必要があります。[Voucherify](https://support.voucherify.io/article/67-how-to-import-my-customers) について詳しく知るには、訪問してください。
+ディストリビューションを設定する前に、Braze ユーザーを Voucherify ダッシュボードに追加する必要があります。[Voucherify](https://support.voucherify.io/article/67-how-to-import-my-customers) について詳しく知るには、こちらをご覧ください。
 
 ![]({% image_buster /assets/img/voucherify/voucherify_custom_attributes_distribution.png %})
 
@@ -45,20 +45,20 @@ Braze にコードを配布するには、2 つのモードを使用できます
 - **マニュアルモード**
 - ユーザーがアクションを実行したときにコードの配信をトリガーする**自動化されたワークフロー**を定義します。
 
-手動モードと自動モードの両方で、Voucherifyは固有のコードをその属性とともに送信し、それらをユーザープロファイルのBrazeカスタム属性に割り当てます。
+手動モードと自動モードの両方で、Voucherify は固有のコードをその属性とともに送信し、それらをユーザープロファイルの Braze カスタム属性に割り当てます。
 
 ![カスタム属性にフィールドをマッピングする]({% image_buster /assets/img/voucherify/voucherify_custom_attributes_fields_mapping.png %})
 
 {% tabs %}
-{% tab 手動配布 %}
+{% tab マニュアルディストリビューション %}
 
-マニュアルモードは、選択されたオーディエンスにコードを割り当てる一度限りのアクションです。ダッシュボードの**配布**に移動し、プラスで配布マネージャーを実行し、**手動メッセージ**を選択します。
+マニュアルモードは、選択されたオーディエンスにコードを割り当てる一度限りのアクションです。ダッシュボードの \[**Distribution**] に移動し、プラス記号を使ってディストリビューションマネージャーを実行し、\[**Manual Message**] を選択します。
 
-1.  あなたの配布物に名前を付けてください。
+1.  ディストリビューションに名前を付けます。
 
     ![]({% image_buster /assets/img/voucherify/voucherify_custom_attributes_name_distribution.png %}){: style="max-width:90%;margin-top:15px;margin-bottom:15px;"}<br>  
     
-    ユニークなコードのソースとなるキャンペーン**(1)**を選択し、ユーザーのセグメントまたは単一の顧客を受信者として選択します**(2)**。[Voucherify](https://support.voucherify.io/article/51-customer-segments) にアクセスして顧客セグメントの詳細をご覧ください。  
+    ユニークなコードのソースとなるキャンペーン**(1)**を選択し、ユーザーのセグメントまたは単一の顧客を受信者として選択します**(2)**。顧客セグメントの詳細については、[Voucherify](https://support.voucherify.io/article/51-customer-segments) にアクセスしてください。  
     
     ![]({% image_buster /assets/img/voucherify/voucherify_custom_attributes_name_distribution_choose_segment.png %}){: style="max-width:90%;margin-top:15px;margin-bottom:15px;"}  
 
@@ -72,24 +72,24 @@ Braze にコードを配布するには、2 つのモードを使用できます
     
 4.  完了すると、分布の概要を確認できます。**保存して送信**をクリックして、コードをBrazeのユーザープロファイルに配信します。  
 
-_すべての手動配信は10分遅れで送信されることに注意してください。_
+_すべてのマニュアルディストリビューションは10分遅れで送信されることに注意してください。_
 
 {% endtab %}
 {% tab 自動ワークフロー %}
 
 Voucherifyは、次のトリガーに応じてBrazeにコードを自動的にプッシュできます:
 
-- **顧客 entered/left specific Voucherify Segment**
-- **コードの発行に成功しました** – コードがキャンペーンから顧客に発行（割り当て）されたときに送信されるメッセージです。
-- **注文ステータスが変更されました**（注文が作成されました、注文が更新されました、注文が支払われました、注文がキャンセルされました）
-- **ギフトクレジットが追加されました** – メッセージは、ギフトカードクレジットが顧客のカードに追加されたときに送信されます。
+- **Customer entered/left specific Voucherify segment**
+- **Successful code publish** – Voucherify でキャンペーンのコードが顧客に発行された (割り当てられた) ときに送信されるメッセージです。
+- **Order status changed** (order created、order updated、order has been paid、order canceled)
+- **Gift credits added** – このメッセージは、ギフトカードクレジットが顧客のカードに追加されたときに送信されます。
 - **ロイヤルティポイントが追加されました** – ロイヤルティポイントが顧客のプロファイルに追加されたときに送信されるメッセージです。
-- **バウチャーが引き換えられました** – このメッセージは、バウチャーを正常に引き換えた顧客に送信されます。
-- **バウチャーの償還のロールバック** – メッセージは償還が正常にロールバックされた顧客に送信されます。
-- **報酬引き換え** – メッセージは顧客がロイヤルティまたは紹介報酬を引き換えるときに送信されます。
-- **カスタムイベントが顧客に対して記録されました** \- このメッセージは、Voucherifyが特定のカスタムイベントを記録したときにトリガーされます。
+- **Voucher redeemed** – このメッセージは、バウチャーの引き換えが正常に完了した顧客に送信されます。
+- **Voucher redemption rollback** – このメッセージは引き換えが正常にロールバックされた顧客に送信されます。
+- **Reward redemption** – このメッセージは、顧客がロイヤルティまたは紹介報酬を引き換えるときに送信されます。
+- **Custom event was logged for a customer** \- このメッセージは、Voucherify が特定のカスタムイベントを記録したときにトリガーされます。
 
-BrazeとVoucherifyを使用して自動ワークフローを設定するには、[配布チュートリアルを参照してください](https://support.voucherify.io/article/19-how-does-the-distribution-manager-work)。
+Braze と Voucherify を使用して自動ワークフローを設定するには、[ディストリビューションチュートリアルを参照してください](https://support.voucherify.io/article/19-how-does-the-distribution-manager-work)。
 
 {% endtab %}
 {% endtabs %}
@@ -100,7 +100,7 @@ BrazeとVoucherifyを使用して自動ワークフローを設定するには
 
 カスタム属性がBrazeの顧客のカスタム属性にコードと共に追加されると、それをキャンペーンで使用できます。
 
-メッセージ本文を編集し、Voucherifyディストリビューションで定義されたカスタム属性を追加します。{% raw %}`{{custom_attribute.${custom_attribute_with_code}}}`{% endraw %}を配置して、ユニークなコードを表示します。
+メッセージ本文を編集し、Voucherifyディストリビューションで定義されたカスタム属性を追加します。一意のコードを表示するため、{% raw %}`{{custom_attribute.${custom_attribute_with_code}}}`{% endraw %} を配置します。
 
 ![]({% image_buster /assets/img/voucherify/voucherify_custom_attributes_email_body.png %}){: style="max-width:75%;"}
 
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content.md
index 2e7661c1d29..cf6f64335f7 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_fetching_data_through_braze_connected_content.md
@@ -1,16 +1,16 @@
 ---
-nav_title: コネクテッドコンテンツを通じてデータを取得する
-article_title: Voucherifyを使用してコネクテッドコンテンツを通じてデータを取得する
+nav_title: コネクテッドコンテンツを使用したデータの取得
+article_title: コネクテッドコンテンツと Voucherify を使用したデータの取得
 page_order: 2
 alias: /partners/voucherify/connected_content/
-description: "このリファレンス記事では、Brazeコネクテッドコンテンツを通じてVoucherify APIからデータを取得し、特定のBrazeセグメントにメッセージを送信する方法について説明します。"
+description: "このリファレンス記事では、Braze コネクテッドコンテンツを使用して Voucherify API からデータを取得し、特定の Braze セグメントにメッセージを送信する方法について説明します。"
 page_type: partner
 search_tag: Partner
 ---
 
-# コネクテッドコンテンツを通じてデータを取得する
+# コネクテッドコンテンツを使用したデータの取得
 
-> Brazeのコネクテッドコンテンツを使用すると、Voucherify APIからデータを取得し、特定のBrazeセグメントにメッセージを送信できます。このリファレンス記事では、コネクテッドコンテンツスクリプトを設定して、Voucherifyクーポンを発行し、新しい紹介者を招待し、ロイヤルティカードの残高を取得する方法などを紹介します。
+> Braze コネクテッドコンテンツを使用して、Voucherify API からデータを取得し、特定の Braze セグメントにメッセージを送信できます。このリファレンス記事では、Voucherify クーポンの発行、新しい紹介者の招待、ロイヤルティカードの残高の取得などのために、コネクテッドコンテンツスクリプトを設定する方法などを紹介します。
 
 スクリプトの基本スキーマは次のようになります:
 {% raw %}
@@ -29,16 +29,16 @@ search_tag: Partner
 ```
 {% endraw %}
 
-Voucherify の [GitHub リポジトリ](https://github.com/voucherifyio/braze-connected-content) を訪れて、コネクテッドコンテンツ スクリプトの例を確認してください。
+Voucherify の [GitHub リポジトリ](https://github.com/voucherifyio/braze-connected-content)にアクセスして、コネクテッドコンテンツスクリプトの例を参照してください。
 
 ## セキュリティ設定
 
-次の設定を毎回設定しないと、コネクテッドコンテンツメッセージがトリガーされるたびに、少なくとも2回はVoucherify APIを呼び出します。これらの設定により、Brazeに請求されるAPIコールの数が減り、メッセージ配信を妨げる可能性のあるハードブロッキングAPI制限に達するリスクが軽減されます。
+以下の設定が行われてない場合、コネクテッドコンテンツメッセージがトリガーされるたびに、Voucherify API が2回以上呼び出されます。これらの設定により、Brazeに請求されるAPIコールの数が減り、メッセージ配信を妨げる可能性のあるハードブロッキングAPI制限に達するリスクが軽減されます。
 
 {% tabs %}
-{% tab レートリミッター %}
+{% tab レート制限 %}
 
-**レートリミッター**
+**レート制限**
 
 Braze によって送信されるメッセージの数を1分あたり[制限する]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#delivery-speed-rate-limiting)ようにしてください。これにより、キャンペーンからの過剰なトラフィックに対して、BrazeおよびVoucherifyのAPIの両方が保護されます。キャンペーンの設定中にユーザーをターゲットにする場合、送信率を1分あたり500メッセージに制限してください。
 
@@ -47,9 +47,9 @@ Braze によって送信されるメッセージの数を1分あたり[制限す
 {% endtab %}
 {% tab キャッシュ %}
 
-**POSTコールにおけるキャッシュ**
+**POST 呼び出しでのキャッシュ**
 
-コネクテッドコンテンツの呼び出しは、デフォルトではHTTP POST経由でキャッシュされず、公開された各コードごとに2つのAPIリクエストが行われます。この動作はAPIの制限に負担をかける可能性があります。キャッシングメカニズムにより、バウチャーの公開ごとに1回のAPIコールに制限できます。 
+HTTP POST を使用して実行されるコネクテッドコンテンツ呼び出しは、デフォルトではキャッシュを行わず、発行済みのコードごとに2つの API リクエストを行います。この動作はAPIの制限に負担をかける可能性があります。このキャッシュメカニズムでは、バウチャー発行ごとに1回の API 呼び出しに制限できます。 
 
 {% alert important %}
 このチュートリアルにおけるコネクテッドコンテンツのすべての例には、BrazeによってトリガーされるAPIコールの数を減らすためにデフォルトのキャッシングが含まれています。
@@ -57,28 +57,28 @@ Braze によって送信されるメッセージの数を1分あたり[制限す
 
 POST呼び出しにキャッシュを追加するには:
 
-1. {% raw %}`:cache_max_age`{% endraw %}属性を追加します。デフォルトでは、キャッシュの期間は5分です。秒単位で期間をカスタマイズできます。5分から4時間の間に設定できます。例: {% raw %}`:cache_max_age 3600`{% endraw %} は1時間キャッシュされます。
-2. 送信先エンドポイントクエリパラメータにキャッシュキー{% raw %}`cache_id={{cache_id}}`{% endraw %}を提供して、Brazeが一意の公開を識別できるようにします。まず、変数を定義してから、一意のクエリ文字列をエンドポイントに追加します。これにより、各出版物が{% raw %}`source_id`{% endraw %}によって区別されます。
+1. {% raw %}`:cache_max_age`{% endraw %}属性を追加します。デフォルトでは、キャッシュ期間は5分です。秒単位で期間をカスタマイズできます。5分から4時間の間で設定できます。例: {% raw %}`:cache_max_age 3600`{% endraw %} の場合キャッシュ期間は1時間です。
+2. 宛先エンドポイントクエリパラメーターにキャッシュキー {% raw %}`cache_id={{cache_id}}`{% endraw %} を指定します。これにより、Braze が一意のコード発行を識別できるようになります。最初に変数を定義してから、エンドポイントに一意のクエリ文字列を付加します。これにより、各コード発行が {% raw %}`source_id`{% endraw %} によって区別されます。
 
 ![]({% image_buster /assets/img/voucherify/voucherify_cc_cache.png %})
 
-_結果に注意してください:_BrazeはURLに基づいてAPIコールをキャッシュします。クエリパラメータとして使用される一意の文字列はVoucherifyによって無視されますが、Brazeの異なるAPIリクエストを区別し、各一意の試行を個別にキャッシュすることができます。そのクエリパラメータがないと、すべての顧客はキャッシュ期間中に同じクーポンコードを受け取ります。
+_結果に注意してください。_BrazeはURLに基づいてAPIコールをキャッシュします。クエリパラメーターとして使用される一意の文字列は Voucherify では無視されますが、この文字列により Braze の異なる API リクエストが区別され、一意の試行を個別にキャッシュすることができるようになります。そのクエリパラメータがないと、すべての顧客はキャッシュ期間中に同じクーポンコードを受け取ります。
 
 {% endtab %}
 {% tab リトライ属性 %}
 
-**リトライ属性**
+**retry 属性**
 
-コネクテッドコンテンツはVoucherifyの応答を検証しないため、コネクテッドコンテンツスクリプトに[retry]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/connected_content_retries)属性を追加することをお勧めします。コネクテッドコンテンツのロジックは、メッセージを中止する前に5回再試行しようとします（レートリミッターを尊重します）。この方法は、Voucherifyからデータを取得するのに少し時間がかかる場合に、コードの公開が失敗するケースを防ぐのに役立ちます。
+コネクテッドコンテンツは Voucherify 応答を検証しないため、コネクテッドコンテンツスクリプトに [retry]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/connected_content_retries) 属性を追加することを推奨します。コネクテッドコンテンツのロジックは、メッセージを中断する前に5回再試行します (これはレート制限に準拠します)。この方法は、Voucherifyからデータを取得するのに少し時間がかかる場合に、コードの公開が失敗するケースを防ぐのに役立ちます。
 
 {% raw %}`:retry`{% endraw %}を使用しない場合、Voucherifyから返される応答に関係なく、Brazeは配信を送信しようとします。これにより、公開されたコードなしでメールが生成される可能性があります。
 
 ![]({% image_buster /assets/img/voucherify/voucherify_cc_retry.png %})
 
 {% endtab %}
-{% tab ユニークな出版物 %}
+{% tab 一意のコード発行 %}
 
-**顧客ごとのユニークな出版物**
+**顧客ごとの一意のコード発行**
 
 スクリプト本文の{% raw %}`source_id`{% endraw %}パラメータは、各顧客が単一のBrazeキャンペーンで一意のコードを1つだけ受け取ることができるようにします。その結果、たとえBrazeが意図せずリクエストを複数回行ったとしても、各ユーザーは最初のメッセージで彼/彼女に公開されたのと同じ一意のコードを受け取ります。
 
@@ -88,16 +88,16 @@ _結果に注意してください:_BrazeはURLに基づいてAPIコールをキ
 
 | 構成 | 効果 |
 | ------------- | ------ |
-| {% raw %}`{{campaign.${dispatch_id}}}`{% endraw %} | 単一の送信内の顧客は同じ出版物を使用します。 |
-| {% raw %}`{{campaign.${api_id}}}`{% endraw %} | すべての顧客は単一のキャンペーン内で同じ出版物を使用します。 |
-| {% raw %}`{{${user_id}}}`{% endraw %} または {% raw %}`{{${braze_id}}}`{% endraw %} | すべての顧客がどのキャンペーンが送信されても同じ出版物を使用することを確認します（{% raw %}`${user_id}`{% endraw %}は{% raw %}`external_id`{% endraw %}であり、{% raw %}`${braze_id}`{% endraw %}は内部IDです）。 |
-| {% raw %}`{{campaign.${dispatch_id}}}`{% endraw %} と {% raw %}`{{campaign.${user_id}}}`{% endraw %} | 単一の送信内の各顧客は同じ一意の出版物を使用します。 |
+| {% raw %}`{{campaign.${dispatch_id}}}`{% endraw %} | 1回の送信内の顧客は同じコード発行を使用します。 |
+| {% raw %}`{{campaign.${api_id}}}`{% endraw %} | 1つのキャンペーン内のすべての顧客は同じコード発行を使用します。 |
+| {% raw %}`{{${user_id}}}`{% endraw %} または {% raw %}`{{${braze_id}}}`{% endraw %} | どのキャンペーンが送信されてもすべての顧客が同じコード発行を使用することを確認します ({% raw %}`external_id`{% endraw %}である {% raw %}`${user_id}`{% endraw %}と、内部 ID である {% raw %}`${braze_id}`{% endraw %} を使用できます)。 |
+| {% raw %}`{{campaign.${dispatch_id}}}`{% endraw %} と {% raw %}`{{campaign.${user_id}}}`{% endraw %} | 1つの送信内の各顧客は、同じ一意のコード発行を使用します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endtab %}
-{% tab 一度参加 %}
+{% tab 1回のみの参加 %}
 
-**一度参加**
+**1回のみの参加**
 
 Voucherifyキャンペーンに制限がある場合_顧客は一度しか参加できません_、スクリプト本文から公開ソースIDを削除してください。Voucherifyは、同じ顧客に送信される各Brazeメッセージが最初に公開されたのと同じコードを配信することを確認します。
 
@@ -134,12 +134,12 @@ Voucherifyキャンペーンに制限がある場合_顧客は一度しか参加
 
 ## ユースケース
 
-以下のすべてのユースケースでは、Voucherifyの公開ソースIDとBrazeのキャッシュおよびリトライパラメータを使用して、Brazeキャンペーンによって呼び出されるAPIコールを制限することに留意してください。次の結果について知っておく必要があります:
+以下のすべてのユースケースでは、Voucherify の発行ソース ID と Braze のキャッシュおよび再試行パラメーターを使用して、Braze キャンペーンによって呼び出される API 呼び出しを制限していることに留意してください。次に示す影響に注意する必要があります。
 
 - 同じ顧客に異なるコードを単一のBrazeキャンペーンで公開および送信することはできません。
 - Voucherifyキャンペーンで_一度だけ参加機能_を使用する場合は、上記の一度だけ参加タブに記載されているように、コネクテッドコンテンツ本文から`source_id`を削除する必要があります。
 
-Voucherify の [GitHub リポジトリ](https://github.com/voucherifyio/braze-connected-content) を訪れて、コネクテッドコンテンツ スクリプトの例を確認してください。
+Voucherify の [GitHub リポジトリ](https://github.com/voucherifyio/braze-connected-content)にアクセスして、コネクテッドコンテンツスクリプトの例を参照してください。
 
 ### 公開してユニークなクーポンコードを送信する
 
@@ -173,7 +173,7 @@ Voucherify の [GitHub リポジトリ](https://github.com/voucherifyio/braze-co
 
 ### 新しい紹介者を招待する
 
-顧客に紹介プログラムに参加してもらうには、その人に紹介コードを割り当てる必要があります。コネクテッドコンテンツは前の例と同じままです。このコネクテッドコンテンツスクリプトを使用すると、選択したBrazeユーザーにユニークな紹介コードを公開して送信できます。各ユーザーは、他のユーザーと共有して新しい紹介を得るための紹介コードを1つだけ受け取ります。 
+顧客に紹介プログラムに参加してもらうには、その人に紹介コードを割り当てる必要があります。コネクテッドコンテンツは前の例と同じです。このコネクテッドコンテンツスクリプトを使用すると、選択したBrazeユーザーにユニークな紹介コードを公開して送信できます。各ユーザーは、他のユーザーと共有して新しい紹介者を獲得するための紹介コードを1つだけ受け取ります。 
 
 {% raw %}
 
@@ -201,7 +201,7 @@ Voucherify の [GitHub リポジトリ](https://github.com/voucherifyio/braze-co
 
 {% endraw %}
 
-### ロイヤルティカード残高を取得
+### ロイヤルティカード残高を取得する
 
 ここに、カスタム属性として事前にBrazeに送信されたロイヤルティカードコードに基づいて現在のロイヤルティ残高を取得するコネクテッドコンテンツスクリプトのユースケースがあります。このスクリプトを使用する前に、ロイヤルティカードコードをBrazeユーザープロファイルにカスタム属性として保存する必要があることに注意してください。
 
@@ -295,7 +295,7 @@ Voucherify の [GitHub リポジトリ](https://github.com/voucherifyio/braze-co
     
     {% endraw %}
 
-その結果、顧客は次のメールを受け取ります:  
+その結果、顧客に次のメールが送信されます。  
 
 ![]({% image_buster /assets/img/voucherify/voucherify_cc_custom_code_email.png %})
 
@@ -362,7 +362,7 @@ Voucherify の [GitHub リポジトリ](https://github.com/voucherifyio/braze-co
     ```
     {% endraw %}
     
-    | 共有クラスタ   | Brazeコネクテッドコンテンツのエンドポイント          |
+    | 共有クラスタ   | Braze コネクテッドコンテンツのエンドポイント          |
     | ---------------- | --------------------------------------------- |
     | ヨーロッパ（デフォルト） | https://api.voucherify.io/v1/publications     |
     | アメリカ合衆国    | https://us1.api.voucherify.io/v1/publications |
@@ -416,15 +416,15 @@ Voucherify API からの応答は、{% raw %}`:save`{% endraw %} パラメータ
 ```
 {% endraw %}
 
-これにより、Voucherifyの応答からデータを取得してBrazeメッセージに表示できます。
+これにより、Voucherify 応答からデータを取得して Braze メッセージに表示できます。
 
 スニペットを作成して、公開されたコード、ロイヤルティカードの残高、有効期限、およびVoucherify APIからのJSON形式のレスポンスに含まれるその他のパラメーターを表示できます。
 
 例えば、メッセージテンプレートに公開されたコードを表示するには、バウチャーオブジェクトからユニークなコードを取得するスニペットを作成する必要があります。
 
-コネクテッドコンテンツ script:
+コネクテッドコンテンツスクリプト:
 
-![コネクテッドコンテンツスクリプトは、コネクテッドコンテンツ呼び出しの最後にVoucherifyの応答を保存することを示しています]({% image_buster /assets/img/voucherify/voucherify_cc_save_parameter.png %})
+![コネクテッドコンテンツ呼び出しの最後に Voucherify 応答を保存することを示しているコネクテッドコンテンツスクリプト]({% image_buster /assets/img/voucherify/voucherify_cc_save_parameter.png %})
 
 Brazeメッセージテンプレートのスニペット:
 
@@ -436,9 +436,9 @@ Brazeメッセージテンプレートのスニペット:
 
 {% endraw %}
 
-その結果、各顧客はプロファイルに自動的に割り当てられたユニークなコードを含むメッセージを受け取ります。ユーザーがコードを受け取るたびに、それはVoucherifyのプロファイルに公開されます。
+その結果、それぞれの顧客は各自のプロファイルに自動的に割り当てられた一意のコードを含むメッセージを受け取ります。ユーザーがコードを受け取るたびに、そのコードは Voucherify のプロファイルに発行されます。
 
-ロイヤルティカードの残高をVoucherify APIから取得して表示するには、次のスニペットを作成する必要があります:
+ロイヤルティカードの残高を Voucherify API から取得して表示するには、次のスニペットを作成する必要があります。
 
 {% raw %}
 
@@ -448,7 +448,7 @@ Brazeメッセージテンプレートのスニペット:
 
 {% endraw %}
 
-メンバーがコネクテッドコンテンツスクリプトの{% raw %}`:save`{% endraw %}パラメータの値である場合。
+ここで member は、コネクテッドコンテンツスクリプトの {% raw %}`:save`{% endraw %}パラメーターの値です。
 
 {% raw %}
 
@@ -458,12 +458,12 @@ Brazeメッセージテンプレートのスニペット:
 
 {% endraw %}
 
-プレビュー
+「プレビューモード」に完全に依存せず、いくつかのテストメッセージを送信して、すべてが正常に動作していることを確認することを強くお勧めします。
 
-### ステップ3:レートリミッターを設定する
+### ステップ3:レート制限を設定する
 
 キャンペーンターゲットを設定する際は、高度な設定を使用して、1分あたりに送信されるメッセージの数を制限します。
 
 ![]({% image_buster /assets/img/voucherify/voucherify_cc_limiter.png %})
 
-Brazeの[ドキュメント]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#delivery-speed-rate-limiting)でレートリミッターとフリークエンシーキャップについて詳しく読む。
+レート制限とフリークエンシーキャップについて詳しくは、Braze の[ドキュメント]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#delivery-speed-rate-limiting)でご確認ください。
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_using_braze_promotion_codes_list.md b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_using_braze_promotion_codes_list.md
index 354038b5cc1..a2178eab8d7 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_using_braze_promotion_codes_list.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_using_braze_promotion_codes_list.md
@@ -1,6 +1,6 @@
 ---
 nav_title: Voucherify推進規程一覧
-article_title: Voucherify・Braze推進規程一覧
+article_title: Voucherify と Braze のプロモーションコードリスト
 page_order: 4
 alias: /partners/voucherify/promotion/
 description: "このリファレンス記事では、Brazeプロモーションコードの抜粋を使用してVoucherify コードsを共有する方法について説明します。"
@@ -10,7 +10,7 @@ search_tag: Partner
 
 # Voucherify・Braze推進コード一覧
 
-> 接続されたコンテンツおよびカスタム属性s に加えて、Braze プロモコードs スニペットを使用してVoucherify コードs を共有できます。まず、コードsをVoucherifyからエクスポートし、コードsをBrazeにインポートし、プロモーションリストからメール コードの抜粋コードを追加します。 
+> 接続されたコンテンツおよびカスタム属性s に加えて、Braze プロモコードs スニペットを使用してVoucherify コードs を共有できます。最初に Voucherify からコードをエクスポートしてから Braze にコードをインポートし、プロモーションリストからコードを取得するメールコードスニペットを追加します。 
 
 ## ステップ1:Voucherifyからの一意のコードのエクスポート
 
@@ -18,9 +18,9 @@ Voucherify で、Voucherify キャンペーンに移動します。次に、**CS
 
 ![]({% image_buster /assets/img/voucherify/voucherify_promotion_export_codes.png %}){: style="margin-top:15px;"}
 
-## ステップ2:昇格コード一覧の作成
+## ステップ2:プロモーションコードリストを作成する
 
-**Data Settings**> **Promotion Codes**に移動し、**Promotion Code List**をクリックします。
+\[**Data Settings**] > \[**Promotion Codes**] に移動し、\[**Promotion Code List**] をクリックします。
 
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation) を使用している場合は、**プロモーションコード** の下に**Integrations** があります。
@@ -40,11 +40,11 @@ Voucherify キャンペーンの名前を使用して、一覧に名前を付け
 
 ## ステップ 3:上読み込む CSVファイル
 
-Voucherify コード s でCSVファイルを読み込むします。
+Voucherify コードを含む CSV ファイルをアップロードします。
 
 ![]({% image_buster /assets/img/voucherify/voucherify_promotion_import_codes.png %})
 
-一覧にコードs(列ヘッダーではない)のみが含まれていることを確認し、**スタートアップ読み込む**を押します。インポートが完了したら、**Save List**をクリックしてリストの詳細を確認します。
+リストにコードのみが含まれていること (列ヘッダーは含まれていないこと) を確認し、\[**Start Upload**] をクリックします。インポートが完了したら、**Save List**をクリックしてリストの詳細を確認します。
 
 ![]({% image_buster /assets/img/voucherify/voucherify_promotion_upload_csv.png %}){: style="max-width:50%;"}
 
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys.md b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys.md
index 0b92e0cb0e0..4abd1329af5 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys.md
@@ -1,6 +1,6 @@
 ---
 nav_title: アンケート
-article_title: 調査パートナー
+article_title: 調査/アンケートのパートナー
 page_order: 9
 
 page_type: landing
@@ -18,10 +18,10 @@ valid_partner_list:
   url: /docs/partners/message_orchestration/channel_extensions/surveys/iterate/
 - name: Digioh
   url: /docs/partners/message_orchestration/channel_extensions/surveys/digioh/
-- name: サーヴィケイト
+- name: Survicate
   url: /docs/partners/message_orchestration/channel_extensions/surveys/survicate/
 - name: Ada
   url: /docs/partners/message_orchestration/channel_extensions/surveys/ada/
-- name: タイプフォーム
+- name: Typeform
   url: /docs/partners/message_orchestration/channel_extensions/surveys/typeform/
 ---
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/ada.md b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/ada.md
index 0bcd4afc846..9923c7eccbe 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/ada.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/ada.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Ada
 article_title: Ada
-description: "この参考記事では、顧客とのやり取りを自動化し、パーソナライズするAIを搭載したプラットフォームであるBrazeとAdaのパートナーシップについて概説している。この統合により、自動化されたエイダとの会話から収集したデータでユーザー・プロフィールを補強することができる。"
+description: "この参考記事では、顧客とのやり取りを自動化し、パーソナライズするAIを搭載したプラットフォームであるBrazeとAdaのパートナーシップについて概説している。この統合により、自動化された Ada の会話から収集されたデータを使用してユーザープロファイルを拡張できます。"
 alias: /partners/ada/
 page_type: partner
 search_tag: Partner
@@ -10,15 +10,15 @@ search_tag: Partner
 
 # Ada
 
-> [Adaは](https://ada.cx)、会話型AIを使って顧客体験を自動化し、パーソナライズするブランド・インタラクション・プラットフォームだ。Adaを使用して、ユーザーデータに基づいてメッセージングを調整し、キャンペーンをセグメント化し、会話を測定・分析して新たな機会を発見し、顧客とのチャットから得た洞察を使用してユーザープロファイルを充実させる。  
+> [Ada](https://ada.cx)は、対話型 AI を使ってカスタマーエクスペリエンスを自動化およびパーソナライズするブランドインタラクションプラットフォームです。Adaを使用して、ユーザーデータに基づいてメッセージングを調整し、キャンペーンをセグメント化し、会話を測定・分析して新たな機会を発見し、顧客とのチャットから得た洞察を使用してユーザープロファイルを充実させる。  
 
-BrazeとAdaの統合により、自動化されたAdaの会話から収集したデータでユーザープロフィールを補強することができる。Adaチャット中に収集した情報に基づいてカスタムユーザー属性を設定し、Ada会話中の指定ポイントでBrazeにカスタムイベントを記録することができる。エイダ・チャットボットをBrazeに接続することで、消費者がブランドについてどのような質問をしているのか、あるいは消費者と積極的に会話を始めることで、消費者の興味や嗜好についてより深く知ることができる。
+Braze と Ada の統合により、自動化された Ada の会話から収集されたデータを使用してユーザープロファイルを拡張できます。Ada でのチャット中に収集した情報に基づいてカスタムユーザー属性を設定し、Ada での会話中に指定された時点で Braze にカスタムイベントを記録できます。Ada のチャットボットを Braze に接続すると、顧客が尋ねたブランドに関する質問に基づいて、あるいは顧客との会話を積極的に開始し、顧客の関心や好みを深く理解するための質問をすることで、顧客をより詳しく把握できます。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| エイダアカウント | このパートナーシップを利用するには、BrazeとAnswer Utilitiesのアプリケーションを有効にした[Ada](https://ada.cx)アカウントが必要である。 |
+| Ada アカウント | このパートナーシップを利用するには、BrazeとAnswer Utilitiesのアプリケーションを有効にした[Ada](https://ada.cx)アカウントが必要である。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][1]。エンドポイントは、インスタンスのBraze URLに依存する。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -26,63 +26,63 @@ BrazeとAdaの統合により、自動化されたAdaの会話から収集した
 ## ユースケース
 
 BrazeとAdaの統合の一般的な使用例には次のようなものがある：
-- Brazeのカスタムイベントとして、消費者とAdaボットのさまざまなやりとりを追跡する。これにより、どの顧客がAdaのプロアクティブキャンペーンに参加したのか、サポートエージェントに引き渡されたのか、特定の質問をしたのか、特定のアクションを完了したのかを知ることができる。
-- 消費者に興味、嗜好、人口統計などを尋ねる。カスタム属性を使用して、この新しい情報でBrazeのプロフィールを自動的に更新する。
+- 消費者が Ada ボットとの間で行ったさまざまなインタラクションを Braze でカスタムイベントとして追跡する。これにより、Ada でプロアクティブなキャンペーンに参加した顧客、サポートエージェントに引き継がれた顧客、特定の質問をした顧客、特定のアクションを完了した顧客を把握できます。
+- 消費者に各自の関心、好み、デモグラフィックなどを尋ねる。カスタム属性を使用して、この新しい情報で Braze のプロファイルを自動的に更新します。
 
 ## 統合
 
-BrazeとAdaを統合するには、まずAdaダッシュボードでBrazeアプリケーションを設定し、Adaチームと協力してAda埋め込みスクリプトにユーザーIDメタ変数を設定する必要がある。次に、Brazeに情報を送り返したい場所（イベントかアトリビュート）に、Brazeブロックをアンサーエディタにドラッグする。
+Braze と Ada を統合するには、まず Ada ダッシュボードで Braze アプリケーションを設定し、Ada チームと協力して Ada 埋め込みスクリプトにユーザー ID メタ変数を設定する必要があります。次に、Brazeに情報を送り返したい場所（イベントかアトリビュート）に、Brazeブロックをアンサーエディタにドラッグする。
 
 ### ステップ1:AdaでBrazeアプリをセットアップする
 
-Adaのダッシュボードで、**Settings > Integrations > Handoff Integrationsと**進む。
+Ada ダッシュボードで **\[Settings] > \[Integrations] > \[Handoff Integrations]** の順に進みます。
 
 Brazeの横にある「**Connect**」をクリックし、以下の情報を入力する：
 - **RESTエンドポイント**：Braze RESTエンドポイントのURLを入力する。 
 - **APIキー**：Braze REST APIキーを入力する。 
-- **アプリID**：Adaチャッターを関連付けたいアプリIDを入力する。
+- **App ID**: Ada チャット機能に関連付けるアプリ ID を入力します。
 
 ### ステップ2:BrazeからAdaに識別子を渡す
 
-正しいユーザーを更新していることを確認するには、Adaチームに連絡する必要がある。Adaチームは、Brazeから識別子を受け取るためにAdaの埋め込みスクリプトに必要な修正を加える手助けをすることができる。この統合は外部IDを受け取るように設計されているが、ユーザーエイリアスなど他の識別子を渡すことも可能だ。 
+正しいユーザーを確実に更新するためには、Ada チームに連絡する必要があります。Ada チームは、Braze から識別子を受け取るために Ada 埋め込みスクリプトに必要な修正を行う作業を支援します。この統合は external ID を受け取るように設計されていますが、ユーザーエイリアスなど他の識別子が受け渡されることがあります。 
 
-### ステップ3:ブレイズ・ブロックを該当するアンサーにドロップする。
+### ステップ3:Braze ブロックを該当する Answer にドロップします。
 
-Brazeブロックを使用するには、ブロックドロワーから適切なAnswerにドラッグし、アクションを選択する。ブレイズ・ブロックでは、2つのアクションができる：
-* トラックイベント
+Braze ブロックを使用するには、ブロックをブロックドロワーから適切な Answer にドラッグし、アクションを選択します。Braze ブロックでは次の2つのアクションを実行できます。
+* イベントの追跡
 * 属性を更新する
 
 {% tabs ローカル %}
-{% tab 走行会 %}
+{% tab イベントの追跡 %}
 
-#### 回答 ユーティリティ・ブロック
+#### \[Answer Utilities] ブロック
 
-1. ブロック・ドロワーからアンサー・ユーティリティーズ・ブロックを、ブレイズ・ブロックの真上にドラッグする。 
+1. ブロックドロワーから \[Answer Utilities] ブロックを Braze ブロックの真上にドラッグします。 
 2. **Format Date**アクションを選択し、**Date**フィールドに`today` 。
-3. **出力形式」**フィールドに「`iso` 」と入力する。**レスポンスを変数として保存**」で、`iso_time` という**書式付き日付の**変数を作成する。
+3. \[**Output Format**] フィールドに「`iso`」と入力します。\[**Save Response As Variable**] で `iso_time` という名前の**形式付き日付**の変数を作成します。
 
-![アンサー・ユーティリティ・ブロックには、前文で説明したようにフィールドが設定される。]({% image_buster /assets/img/ada/ada-braze-2.png %})
+![前述のテキストで説明されているようにフィールドが入力されている Answer Utilities ブロック。]({% image_buster /assets/img/ada/ada-braze-2.png %})
 
-#### ブレーズ・ブロック
+#### Braze ブロック
 
 **4\.**Brazeブロックの**External ID**フィールドに、前のステップでAdaが設定した`external_id` メタ変数を入力する。<br>
 **5\.****Event Name**フィールドに、追跡したいBrazeのイベント名を入力する。<br>
-**6\.****Time of Event**フィールドに、Answer Utilitiesブロックで作成した変数`iso_time` を入力する。<br>
+**6\.**\[**Time of Event**] フィールドに、\[Answer Utilities] ブロックで作成した変数 `iso_time` を入力します。<br>
 **7\.**Brazeへのイベント投稿中に問題が発生した場合に表示されるフォールバックアンサーを選択する。
 
-![] （{% image_buster /assets/img/ada/ada-braze-3.png %} ）。
+![前述のテキストで説明されているようにフィールドが入力されている Braze ブロック。]({% image_buster /assets/img/ada/ada-braze-3.png %})
 
 {% endtab %}
-{% tab 更新属性 %}
+{% tab 属性の更新 %}
 
-#### ブレーズ・ブロック
+#### Braze ブロック
 
-1. Brazeブロックの**External ID**フィールドに、前のステップでAdaが設定した`external_id` メタ変数を入力する。 
+1. Brazeブロックの`External ID`external_id`フィールドに、前のステップでAdaが設定した`external_id` メタ変数を入力する。 
 2. **Attribute Name（属性名**）フィールドに、追跡したいBraze属性の名前を入力する。 
 3. **属性値**フィールドに、設定したい値を入力する。テキスト、変数、またはテキストと変数の組み合わせである。 
 4. Brazeへの属性の投稿中に問題が発生した場合に表示されるフォールバックアンサーを選択する。
 
-![] （{% image_buster /assets/img/ada/ada-braze-4.png %} ）。
+![前述のテキストで説明されているようにフィールドが入力されている Braze ブロック。]({% image_buster /assets/img/ada/ada-braze-4.png %})
 
 {% endtab %}
 {% endtabs %}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/digioh.md b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/digioh.md
index 0aa91c47ca7..f5ca86f610b 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/digioh.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/digioh.md
@@ -1,43 +1,43 @@
 ---
-nav_title: デジオー
-article_title: デジオー
-description: "この参考記事では、BrazeとDigiohのパートナーシップについて概説している。Digiohは、Brazeのキャンペーンを通じて真のエンゲージメントを促進するポップアップ、フォーム、アンケート、コミュニケーションプレファレンスセンターを簡単に作成できるアンケートプラットフォームである。"
+nav_title: Digioh
+article_title: Digioh
+description: "このリファレンス記事では、Braze と Digioh のパートナーシップについて説明します。Digioh は、Braze のキャンペーンを通じて真のエンゲージメントを促進するポップアップ、フォーム、アンケート、およにコミュニケーションユーザー設定センターを簡単に作成できるアンケートプラットフォームです。"
 alias: /partners/digioh/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# デジオー
+# Digioh
 
-> [Digiohは](https://www.digioh.com/)、リストを増やし、ファーストパーティデータを取得し、そのデータをBrazeのキャンペーンに活用することを支援する。
+> [Digioh](https://www.digioh.com/) は、リストの拡大、ファーストパーティデータの取り込み、Braze キャンペーンでのデータの利用を支援します。
 
-BrazeとDigiohの統合により、柔軟なドラッグ＆ドロップビルダーを使用して、顧客とつながるオンブランドのフォーム、ポップアップ、パフォーマンスセンター、ランディングページ、アンケートを作成することができる。Digiohは、統合セットアップを支援し、あなたのために最初のキャンペーンを構築し、設計し、起動する。
+Braze と Digioh の統合により、柔軟性の高いドラッグ＆ドロップビルダーを使用して、顧客とつながるためのブランドらしさのあるフォーム、ポップアップ、パフォーマンスセンター、ランディングページ、アンケートを作成できます。Digioh は、統合の設定を支援し、最初のキャンペーンを作成、設計、開始できるようにします。
 
-!["Digiohで柔軟な電子メールとコミュニケーションのプリファレンスセンターを作る"][5]{: style="border:0"}
+![「Digioh で柔軟製の高いメールとコミュニケーションのユーザー設定センターを作成する」][5]{: style="border:0"}
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-|デジオーアカウント | このパートナーシップを利用するには、[デジオのアカウントが](https://www.digioh.com/)必要である。 |
+|Digioh アカウント | このパートナーシップを活用するには、[Digioh アカウント](https://www.digioh.com/)が必要です。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze API`/users/track/` エンドポイント | あなたのRESTエンドポイントのURLに、`/users/track/` の詳細が付加されている。エンドポイントは、\[インスタンスのBraze URL][6] に依存する。<br><br>例えば、REST API のエンドポイントが`https://rest.iad-01.braze.com` の場合、`/users/track/` のエンドポイントは`https://rest.iad-01.braze.com/users/track/` となる。 |
+| Braze API`/users/track/` エンドポイント | `/users/track/` の詳細が付加された REST エンドポイント URL。エンドポイントは\[インスタンスの Braze URL][6] に応じて異なります。<br><br>たとえば、REST API エンドポイントが `https://rest.iad-01.braze.com` の場合、`/users/track/` エンドポイントは `https://rest.iad-01.braze.com/users/track/` になります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 統合 
 
-Digiohを統合するには、まずBrazeコネクタを設定する必要がある。完了したら、ライトボックス（ウィジェット）に統合を適用する必要がある。統合の基本についてもっと読むには、[Digiohを](https://help.digioh.com/knowledgebase/digioh-integration-basics/)ご覧いただきたい。
+Digioh を統合するには、まず Braze コネクターを設定する必要があります。完了したら、ライトボックス（ウィジェット）に統合を適用する必要がある。[Digioh](https://help.digioh.com/knowledgebase/digioh-integration-basics/) にアクセスして、統合の基礎についてお読みください。
 
-### ステップ1:デジオーの統合を作成する 
+### ステップ1:Digioh 統合を作成する 
 
-Digiohで、**Integrations**タブをクリックし、**New Integration**ボタンをクリックする。**Integration（統合）**ドロップダウンから**Brazeを**選択し、統合に名前を付ける。 
+Digioh で \[**Integration**] タブをクリックし、次に\[**New Integration**] ボタンをクリックします。\[**Integration**] ドロップダウンから \[**Braze**] を選択し、統合に名前を付けます。 
 
 !["ドロップダウンから正しい統合を選択する"][2]{: style="max-width:50%;"}
 
-次に、Braze REST APIキーとBraze API`/users/track/` エンドポイントを入力する。 
+次に、Braze REST API キーとBraze API `/users/track/` エンドポイントを入力します。 
 
-最後に、マップフィールドセクションを使って、Eメールと名前以外のカスタムフィールドをマッピングする。次のコード・スニペットは、ペイロードの例を示している。完了したら、**Create Integrationを**選択する。
+最後に、マップフィールドセクションを使って、Eメールと名前以外のカスタムフィールドをマッピングする。次のコード・スニペットは、ペイロードの例を示している。完了したら、\[**Create Integration**] を選択します。
 
 ```json
 {
@@ -50,18 +50,18 @@ Digiohで、**Integrations**タブをクリックし、**New Integration**ボタ
 }
 ```
 
-### ステップ2:デジオのライトボックスを作成する
+### ステップ2:Digioh ライトボックスを作成する
 
-デジオの[デザインエディターを使って](https://help.digioh.com/knowledgebase/digioh-platform-training-videos-video-series-getting-started-with-digioh/)ライトボックス（ウィジェット）を作る。<br>
-デザインエディターを活用する方法のギャラリーを見ることに興味がある？デジオの[テーマギャラリーを](https://www.digioh.com/theme-gallery)見る。
+Digioh [デザインエディター](https://help.digioh.com/knowledgebase/digioh-platform-training-videos-video-series-getting-started-with-digioh/)を使用してライトボックス (ウィジェット) を作成します。<br>
+デザインエディターを活用する方法のギャラリーを見ることに興味がある？Digioh の[テーマギャラリー](https://www.digioh.com/theme-gallery)をご覧ください。
 
 ### ステップ3:統合を適用する
 
-この統合をDigioh[ライト](https://help.digioh.com/knowledgebase/digioh-platform-training-videos-video-series-getting-started-with-digioh/)ボックスに適用するには、**Boxes**ページに移動し、**Integrations**列の**Add**または**Edit**リンクを選択する。これはエディターの**Integration**セクションからも追加できる。
+この統合を Digioh [ライトボックス](https://help.digioh.com/knowledgebase/digioh-platform-training-videos-video-series-getting-started-with-digioh/)に適用するには、\[**Boxes**] ページに移動し、\[**Integrations**] カラムの \[**Add**] または \[**Edit**] リンクを選択します。これはエディターの**Integration**セクションからも追加できる。
 
 ![「統合をライトボックスに追加する][3]{: style="max-width:90%"}
 
-ここで、**Add Integrationを**選択し、希望のインテグレーションを選択し、**Save**する。DigiohはリアルタイムでBrazeにリードを渡す。
+ここで \[**Add Integration**] を選択し、目的の統合を選択して \[**Save**] をクリックします。Digioh は、キャプチャしたリードをリアルタイムで Braze に渡します。
 
 [2]: {% image_buster /assets/img/digioh/2.png %}
 [3]: {% image_buster /assets/img/digioh/3.png %}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/iterate.md b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/iterate.md
index 98980b8d026..ad562db1f34 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/iterate.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/iterate.md
@@ -10,24 +10,24 @@ search_tag: Partner
 
 # 繰り返す
 
-> [Iterateは](https://iteratehq.com)、スマートで使いやすいリサーチツールを提供し、あなたのブランドと同じような感覚で、簡単に顧客から学ぶことができる。
+> [Iterate](https://iteratehq.com) は、スマートで使いやすく、ブランドに合わせてルックアンドフィールをカスタマイズしたリサーチツールを提供し、顧客から簡単に学べるようにしています。
 
-IterateとBrazeの統合により、製品やキャンペーン内でIterateアンケートをネイティブかつシームレスに配信することができる。アンケートの回答は、Brazeのカスタムユーザー属性として記録することができるため、ユーザーの全体像を把握したり、強力な新しいオーディエンスやセグメントを作成したりすることができる。
+Iterate と Braze の統合により、製品またはキャンペーン内でネイティブかつシームレスに Iterate アンケートを配信できます。アンケートの回答は、Braze でカスタムユーザー属性として記録できます。これにより、ユーザーの全体像を把握し、強力な新しいオーディエンスやセグメントを作成することができます。
 
-アプリやウェブサイトにBraze SDKをインストールすれば、Brazeで利用可能なセグメンテーションやターゲティングツールを使用して、任意のトリガーやカスタムセグメントに基づいて、オーディエンスの特定の部分にアプリ内メッセージでアンケートを配信することができる。Iterateのアンケートは、Eメールキャンペーンに直接埋め込むことも、プッシュ型やその他のキャンペーンタイプにリンクとして含めることもできる。
+アプリやウェブサイトにBraze SDKをインストールすれば、Brazeで利用可能なセグメンテーションやターゲティングツールを使用して、任意のトリガーやカスタムセグメントに基づいて、オーディエンスの特定の部分にアプリ内メッセージでアンケートを配信することができる。Iterate のアンケートは、メールキャンペーンに直接埋め込むことも、プッシュやその他のキャンペーンタイプにリンクとして組み込むこともできます。
 
 ## 前提条件
 
-| 必要条件 | 起源 |
+| 必要条件 | 提供元 |
 |---|---|
-|アカウントを繰り返す | このパートナーシップを利用するには、[イテレートのアカウントが](https://iteratehq.com)必要である。 |
-| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。Brazeのアプリ内メッセージでアンケートを送信するには、`kpi.mau.data_series` のパーミッションも必要だ。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。|
-| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに][6]依存する。 |
+|Iterate アカウント | このパートナーシップを活用するには、[Iterate アカウント](https://iteratehq.com)が必要です。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。Braze アプリ内メッセージでアンケートを送信するには、`kpi.mau.data_series` 権限も必要です。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。|
+| Braze RESTエンドポイント  | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL][6] に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## ユースケース
 
-Iterateを使えば、ほとんどあらゆる種類のデータを収集することができる。個人情報（名前、年齢、Eメール）、パフォーマンスデータ（NPS、顧客満足度、星評価）、好み（好みのデバイス、好みのコミュニケーション頻度）、性格（好きな本、犬、猫）など多岐にわたる。どのようなデータを集めたいか、どのようなオーディエンスを作りたいかは、すべてあなた次第だ。
+Iterate を使用すると、ほぼすべてのタイプのデータを収集できます。個人情報（名前、年齢、Eメール）、パフォーマンスデータ（NPS、顧客満足度、星評価）、好み（好みのデバイス、好みのコミュニケーション頻度）、性格（好きな本、犬、猫）など多岐にわたる。質問の内容、収集するデータ、作成するオーディエンスはすべてお客様が決定します。
 
 ## 統合
 
@@ -41,48 +41,48 @@ Iterateアカウントにログインし、**会社設定**ページでBraze RES
 
 アンケートを作成する前に、イテレート設定の**アプリ内メッセージアンケートを有効にする**トグルをオンにする。
 
-次に、イテレートで新しいアンケートを作成し、関連するアンケートの質問を追加する。適切であれば、アンケートの前にプロンプトメッセージを表示することもできる。アンケートの種類として、**Brazeアプリ内メッセージで送信を**選択する。
+次に、Iterate で新しいアンケートを作成し、関連するアンケートの質問を追加します。適切であれば、アンケートの前にプロンプトメッセージを表示することもできる。アンケートのタイプとして \[**Send via Braze In-App Message**] を選択します。
 
-アンケートが完了したら、**「公開」**タブで「**コピー**」の下にあるコードスニペットをコピー**し、埋め込みコードを貼り付ける**。
+アンケートが完了したら、**「公開」**タブで「**コピー」の下にあるコードスニペットをコピーし、埋め込みコードを貼り付ける**。
 
 #### ステップ2:アンケートを共有する
 
-Brazeで、新しいアプリ内メッセージングキャンペーンを作成し、メッセージングタイプとして**カスタムコードを**選択し、コードスニペットをメッセージに貼り付ける。次に、on-clickメッセージの動作として、**Wait for User to Dismissを**選択する。
+Brazeで、新しいアプリ内メッセージングキャンペーンを作成し、メッセージングタイプとして**カスタムコードを**選択し、コードスニペットをメッセージに貼り付ける。次に、クリック時のメッセージ動作として \[**Wait for User to Dismiss**] を選択します。
 
-他のアプリ内メッセージングキャンペーンと同様にキャンペーンの設定を続け、配信方法を選択し、オーディエンスをターゲットにする。
+他のアプリ内メッセージングキャンペーンと同様にキャンペーンの設定を続け、配信方法を選択し、オーディエンスをターゲットに設定します。
 
 ### Eメールまたはプッシュでアンケートを配信する
 
 #### ステップ1:アンケートを作成する
 
-イテレートで新しいメールまたはリンクアンケートを作成し、関連するアンケートの質問を追加する。質問を作成し、デザインをカスタマイズしたら、**アンケートを送信 > 統合 > Braze** を選択する。
+Iterate で新しいメールアンケートまたはリンクアンケートを作成し、関連するアンケートの質問を追加します。質問を作成し、デザインをカスタマイズしたら、**アンケートを送信 > 統合 > Braze** を選択する。
 
-すると、Brazeに応答を送信するための設定オプションが表示される。アンケートの回答をBrazeに送信できるように統合をオンにする。 
+すると、Brazeに応答を送信するための設定オプションが表示される。アンケートの回答を Braze に送信できるようにするため、統合をオンにします。 
 
 #### ステップ2:アンケートを共有する
 
-アンケートは2つの方法で共有できる：最初の質問をメッセージに埋め込むか、Iterateプラットフォーム上のアンケートへの直接リンクを含める。
+アンケートは2通りの方法で共有できます。これは、最初の質問をメッセージに埋め込む方法と、Iterate プラットフォーム上のアンケートへの直接リンクを含める方法です。
 
-![リンク・オプションを繰り返す][2]
+![Iterate のリンクオプション][2]
 
 - **コードを埋め込む**
   - **アンケートの送信]**タブの Braze 統合セクションの**\[メール埋め込みコード**] にあるコードスニペットをコピーする。BrazeメールのHTMLに、アンケートの冒頭を表示するコードを挿入する。 
-  - アンケートの質問のレンダリングが難しい場合、または正しくフォーマットされていないように見える場合は、メッセージコンポーザーの**\[送信情報]**タブで \[**インライン CSS] の**チェックを外す必要がある。
-- **リンクを貼る**
-  - **アンケートの送信**タブの Braze 統合セクションの**アンケートリンクの**下にあるリンクをコピーする。なお、リンク{% raw %}`?user_braze_id={{${braze_id}}}`{% endraw %} に含まれるリキッドは、送信時に各ユーザーごとに自動的に置き換えられる。
+  - アンケートの質問の表示に問題がある場合、またはアンケートの形式が正しくない場合は、メッセージ作成画面の \[**Sending Info**] タブに移動して \[**Inline CSS**] をオフにします。
+- **リンクを組み込む**
+  - \[**Send survey**] タブの Braze 統合セクションで \[**Survey Link**] の下にあるリンクをコピーします。リンク {% raw %}`?user_braze_id={{${braze_id}}}`{% endraw %} に含まれる Liquid は、送信時にユーザーごとに自動的に置き換えられることに注意してください。
 
-### 次のステップに進む：フォローアップ・キャンペーンを構築する
+### 次のステップに進む：フォローアップキャンペーンを作成する
 
-ユーザーが反応すると、彼らのプロフィールにリアルタイムでデータが入力されるのがわかる。このデータは、ユーザーをセグメント化し、パーソナライズされたフォローアップ・キャンペーンを送信するために使用することができる。例えば、"Do you enjoy our products? "という質問を送信した場合、"Yes "または "No "と回答したカスタムユーザー属性`Do you enjoy our products?` を持つユーザーのセグメントを作成し、これらのユーザーをターゲットにすることができる。
+ユーザーが反応すると、彼らのプロフィールにリアルタイムでデータが入力されるのがわかる。このデータは、ユーザーをセグメント化し、パーソナライズされたフォローアップキャンペーンを送信するために使用できます。例えば、"Do you enjoy our products? "という質問を送信した場合、"Yes "または "No "と回答したカスタムユーザー属性`Do you enjoy our products?` を持つユーザーのセグメントを作成し、これらのユーザーをターゲットにすることができる。
 
-## カスタムイベント
+## Braze カスタムイベント
 
-ユーザーがアンケートの質問に答えると、IterateはBraze内で`survey-question-response` というカスタムイベントをトリガーする。カスタムイベントは、任意の数とタイプのフォローアップキャンペーンをトリガーすることができる。
+ユーザーがアンケートの質問に回答すると、Iterate は Braze 内で `survey-question-response` という名前のカスタムイベントをトリガーします。カスタムイベントでは、トリガーできるフォローアップキャンペーンの数とタイプに制限はありません。
 
 ## ユーザー属性名をカスタマイズする
 
-デフォルトでは、質問に作成されるユーザー属性はプロンプトと同じである。
-場合によっては、これをカスタマイズすることもできる。これを行うには、**アンケートの作成**ステップで**ユーザー属性名のカスタマイズドロップダウンを**クリックし、任意のカスタム名を入力する。
+デフォルトでは、質問に対して作成されたユーザー属性はプロンプトと同じです。
+場合によっては、これをカスタマイズすることもできる。そのためには、\[**Create your Survey**] ステップの \[**Customize user attribute names**] ドロップダウンをクリックし、使用するカスタム名を入力します。
 
 [6]: {{site.baseurl}}/api/basics?redirected=true#endpoints
 [2]: {% image_buster /assets/img/iterate.png %}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/survicate.md b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/survicate.md
index bba55a00fde..84bde40186a 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/survicate.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/survicate.md
@@ -1,6 +1,6 @@
 ---
-nav_title: サーヴィケイト
-article_title: サーヴィケイト
+nav_title: Survicate
+article_title: Survicate
 description: "この参考記事は、BrazeとSurvicateのパートナーシップについて概説しています。SurvicateはNPSおよび顧客フィードバック調査ソフトウェアであり、ファネルのすべての段階でユーザーの洞察を継続的に得るのに役立ちます。"
 alias: /partners/survicate/
 
@@ -9,19 +9,19 @@ search_tag: Partner
 
 ---
 
-# サーヴィケイト
+# Survicate
 
-![Brazeのメールに埋め込まれたHTML調査（最初の質問）の例です。][2]{: style="float:right;max-width:40%;border:0; margin-left:8px;"}
+![Braze のメールで埋め込み HTML アンケート (最初の質問) がどのように表示されるかを示す例。][2]{: style="float:right;max-width:40%;border:0; margin-left:8px;"}
 
 > [Survicate][1]は、NPSおよび顧客フィードバック調査ソフトウェアであり、ファネルのすべての段階でユーザーの洞察を継続的に得るのに役立ちます。 
 
-BrazeとSurvicateの統合により、メールに調査リンクを含めたり、調査スニペットを直接埋め込んだりして、回答率を向上させることができます。アンケートが完了したら、Survicateに戻って、調査回答者の属性と回答を特定して分析します。
+Braze と Survicate の統合により、回答率の向上のためにメールにアンケートリンクを組み込むか、アンケートスニペットを直接埋め込むことができます。アンケートが完成したら Survicate に戻り、アンケート回答者の属性と回答を特定して分析します。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| サーベイケートアカウント | このパートナーシップを利用するには、Survicateアカウントが必要です。 |
+| Survicate アカウント | このパートナーシップを利用するには、Survicateアカウントが必要です。 |
 
 ## ユースケース
 
@@ -35,25 +35,25 @@ Survicateは、よりスマートな意思決定を行い、より良いカス
 
 Survicateを使用すると、技術的なスキルがなくても数分でBraze内でフィードバックを収集し始めることができます。
 
-### ステップ1:Survicateで調査を作成する
+### ステップ1:Survicate でアンケートを作成する
 
-Survicateアカウントにログインし、**新しい調査を作成**ボタンをクリックします。**メールまたは共有可能なリンク調査**のタイプを選択し、ゼロから調査を設計するか、100以上のすぐに使用できる調査テンプレートから選択してください。
+Survicate アカウントにログインし、\[**Create new survey**] ボタンをクリックします。**メールまたは共有可能なリンク調査**のタイプを選択し、ゼロから調査を設計するか、100以上のすぐに使用できる調査テンプレートから選択してください。
 
-### ステップ2:Brazeに調査を接続する
+### ステップ2:Braze にアンケートを接続する
 
-調査の準備ができたら、調査作成者の**設定**タブに移動し、**回答者を識別する**フィールドのツールのドロップダウンリストから**Braze**を選択します。これで、回答者に連絡先を尋ねる必要はありません。
+アンケートの準備ができたら、アンケート作成画面の \[**Configure**] タブに移動し、\[**Identify respondents with**] フィールドの下のツールのドロップダウンリストから \[**Braze**] を選択します。これで、回答者に連絡先の詳細を尋ねる必要がなくなります。
 
 ![][3]{: style="max-width:70%;" }
 
-### ステップ3:調査を共有する
+### ステップ3:アンケートを共有する
 
-**共有**タブに移動し、調査の配置オプションを選択します。Brazeでボタンやハイパーリンクの下に隠すことができる直接リンクを取得するか、HTMLコードを使用してメールの本文に最初の質問を埋め込むことができます。
+\[**Share**] タブに移動し、アンケート配置オプションを選択します。ダイレクトリンク (後で Braze でボタンやハイパーリンクの下に隠すことができる) を取得するか、HTML コードを使用してメール本文に最初の質問を埋め込むことができます。
 
 ![][4]{: style="max-width:70%;" }
 
-### ステップ4:Brazeでメールキャンペーンに調査を追加します
+### ステップ4:Braze でメールキャンペーンにアンケートを追加する
 
-Brazeで、調査のリンクまたはHTMLコードをメールキャンペーンのコンテンツに追加します。お客様への調査を開始し、Survicateで結果を分析しましょう！
+Braze で、アンケートのリンクまたは HTML コードをメールキャンペーンのコンテンツに追加します。顧客へのアンケート調査を開始し、Survicate で結果を分析します。
 
 [1]: https://survicate.com/
 [2]:  {% image_buster /assets/img/survicate/survicate_asset_1.png %}
diff --git a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/typeform.md b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/typeform.md
index db0be7a0989..4b6db5c4a3a 100644
--- a/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/typeform.md
+++ b/_lang/ja/_partners/message_orchestration/channel_extensions/surveys/typeform.md
@@ -1,19 +1,19 @@
 ---
-nav_title: タイプフォーム
-article_title: タイプフォーム
+nav_title: Typeform
+article_title: Typeform
 description: "この記事では、データやフィードバックなどを収集するための使いやすいツールであるBrazeとTypeformのパートナーシップについて概説する。"
 alias: /partners/typeform/
 page_type: partner
 search_tag: Partner
 ---
 
-# タイプフォーム
+# Typeform
 
 > [Typeformは](https://www.typeform.com/)、データやフィードバックなどを収集するための使いやすいツールだ。
 
 BrazeとTypeformを統合することで、以下のことが可能になる：
 
-- BrazeのユーザープロフィールをTypeformの回答から収集したデータで更新する
+- Typeform 応答から収集したデータで Braze のユーザープロファイルを更新する
 - ユーザーのタイプフォームへの関与に基づいて、Brazeでメッセージングをトリガーする
 - ユーザーのTypeformの回答に基づいてBrazeのメッセージをパーソナライズする
 
@@ -21,25 +21,25 @@ BrazeとTypeformを統合することで、以下のことが可能になる：
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| Typeformアカウント | このパートナーシップを利用するには、ウェブフックにアクセスできるTypeformアカウントが必要である。 |
-| ブレイズデータ変換 | Typeformからデータを受け取るには、[データ変換URLが]({{site.baseurl}}/data_transformation/)必要である。 |
+| Typeform アカウント | このパートナーシップを利用するには、ウェブフックにアクセスできるTypeformアカウントが必要である。 |
+| Braze Data Transformation | Typeform からデータを受信するには、[Data Transformation URL]({{site.baseurl}}/data_transformation/) が必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### ステップ1:Typeformのウェブフックを受け入れるようにBrazeのデータ変換を設定する {#step-1}
+### ステップ1:Typeformの Webhook を受け入れるように Braze Data Transformation を設定する {#step-1}
 
 {% multi_lang_include create_transformation.md location="typeform" %}
 
 ### ステップ2:Typeformのウェブフックを設定する
 
-[TypeformのWebhookドキュメントの](https://www.typeform.com/help/a/webhooks-360029573471/)手順に従って、Webhookをセットアップする。
+[Typeform の Webhook ドキュメント](https://www.typeform.com/help/a/webhooks-360029573471/)の手順に従って Webhook を設定します。
 
-ステップ4では、**Destination URLとして**Data Transformation webhook URLを追加する。
+ステップ4で **Destination URL** として Data Transformation Webhook URL を追加します。
 
 ![]({% image_buster /assets/img/typeform/typeform_add_webhook.png %}){: style="max-width:50%" }
 
-**View deliveriesを**クリックし、**Send test requestを**クリックして、データ変換にテストイベントを送信する。
+\[**View deliveries**] をクリックし、\[**Send test request**] をクリックして、Data Transformation にテストイベントを送信します。
 
 ![]({% image_buster /assets/img/typeform/typeform_test_request.png %})
 
@@ -47,14 +47,14 @@ BrazeとTypeformを統合することで、以下のことが可能になる：
 
 このステップでは、Typeformから送信されるWebhookペイロードをJavaScriptオブジェクトの戻り値に変換する。
 
-1. Data Transformationを更新し、**Webhook Detailsに**Typeformのテストペイロードが表示されていることを確認する。
-2. 選択したTypeformイベントをサポートするようにデータ変換コードを更新する。
-3. **Validateを**クリックすると、コードの出力のプレビューが返され、それが受け入れ可能な`/users/track` リクエストかどうかがチェックされる。
-4. データ変換を保存して有効にする。
+1. Data Transformation を更新し、\[**Webhook の詳細**] に Typeform テストペイロードが表示されていることを確認します。
+2. 選択した Typeform イベントをサポートするように Data Transformation コードを更新します。
+3. \[**検証**] をクリックして、コード出力のプレビューを返し、受け入れられる `/users/track` リクエストであるかどうかを確認します。
+4. Data Transformation を保存して有効化します。
 
 ![]({% image_buster /assets/img/typeform/typeform_test_result.png %})
 
-#### リクエスト・ボディのフォーマット
+#### リクエスト本文の形式
 
 この戻り値は、Brazeの `/users/track` リクエストの本文フォーマットに準拠しなければなりません。
 
@@ -324,11 +324,11 @@ Content-Type: application/json
 
 ## データ変換のユースケース
 
-以下は、[TypeformのWebhookペイロードのサンプルを使って](#example-typeform-webhook-payload)作成したテンプレートの例である。これらのテンプレートは出発点として使用できる。ゼロから始めることも、適当に特定のコンポーネントを削除することもできる。
+以下に、[Typeform の Webhook ペイロードのサンプル](#example-typeform-webhook-payload)を使用して作成したテンプレートの例を示します。これらのテンプレートは出発点として使用できる。ゼロから作成するか、必要に応じて特定のコンポーネントを削除することができます。
 
-これらのテンプレート例では、Brazeプロファイルにカスタムイベントをロギングしている。Typeformのタイトルはカスタムイベント名として渡され、Typeformの結果はイベントプロパティとして渡される。これらのテンプレート例では、TypeformのCalendly、File Upload、Paymentの質問タイプは考慮されていない。
+これらのテンプレート例では、Brazeプロファイルにカスタムイベントをロギングしている。Typeform のタイトルはカスタムイベント名として渡され、Typeform の結果はイベントプロパティとして渡されます。これらのテンプレートの例では、Typeform の質問タイプ Calendly、File Upload、Payment は考慮されていません。
 
-### ユースケース:識別子としての電子メール
+### ユースケース:識別子としてのメール
 
 このテンプレートの例では、メールアドレス（タイプフォーム内のメールアドレスの質問から取得）を識別子として使用している。
 
@@ -472,9 +472,9 @@ return brazecall;
 
 ### ユースケース:隠しフィールドに渡された識別子を使用する
 
-TypeformのHidden Fieldsを使えば、Typeformのレスポンスで情報を渡すことなく、TypeformのウェブフックのペイロードでユーザーのIDなどのデータを渡すことができる。
+Typeform の隠しフィールドを使用して、Typeform の応答でこの情報を渡さずに、Typeform の Webhook ペイロードでユーザーの ID などのデータを渡すことができます。
 
-このテンプレート例では、"user_id "隠しフィールドを使用し、これを`external_id` として`/users/track` リクエストペイロードに渡している。ここでは "user_id "を使用しているが、フィールドは必要に応じて変更することができる。
+このテンプレートの例では、「user_id」隠しフィールドを使用し、これを`external_id` として`/users/track` リクエストペイロードに渡しています。ここでは "user_id "を使用しているが、フィールドは必要に応じて変更することができる。
 
 {% tabs ローカル %}
 {% tab インプット %}
@@ -612,7 +612,7 @@ return brazecall;
 
 ### ステップ4:TypeformのWebhookを公開する
 
-データ変換を書いたら、**Validateを**クリックして、データ変換コードが正しくフォーマットされ、期待通りに動作することを確認する。その後、データ変換を保存してアクティブにする。
+Data Transformation の作成が完了したら、\[**検証**] をクリックして、Data Transformation コードが正しくフォーマットされており、期待通りに動作することを確認します。その後、Data Transformation を保存してアクティブ化します。
 
 有効化されると、カスタムイベントデータはユーザーがフォームに入力した際にユーザーのプロフィールに記録される。
 
@@ -620,4 +620,4 @@ return brazecall;
 
 ## モニタリングとトラブルシューティング
 
-[トランスフォーメーションの]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/creating_a_transformation/#step-5-monitor-your-transformation)モニタリングとトラブルシューティングの詳細については、[トランスフォーメーションのモニタリングの]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/creating_a_transformation/#step-5-monitor-your-transformation)セクションを参照のこと。
\ No newline at end of file
+変換のトラブルシューティングと監視については、「[変換の監視]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/creating_a_transformation/#step-5-monitor-your-transformation)」セクションを参照してください。
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_orchestration/learning.md b/_lang/ja/_partners/message_orchestration/learning.md
index 01a187c8817..a6bc6e8f50d 100644
--- a/_lang/ja/_partners/message_orchestration/learning.md
+++ b/_lang/ja/_partners/message_orchestration/learning.md
@@ -1,6 +1,6 @@
 ---
 nav_title: 学習
-article_title: ラーニング・パートナー
+article_title: 学習のパートナー
 page_order: 8
 
 page_type: landing
@@ -14,7 +14,7 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Learning"
 
 valid_partner_list:
-- name: エデュミー
+- name: EduMe
   url: /docs/partners/message_orchestration/learning/edume/
 
 ---
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_orchestration/learning/edume.md b/_lang/ja/_partners/message_orchestration/learning/edume.md
index 4ccb6e05c81..1a12fbb10fc 100644
--- a/_lang/ja/_partners/message_orchestration/learning/edume.md
+++ b/_lang/ja/_partners/message_orchestration/learning/edume.md
@@ -1,34 +1,34 @@
 ---
-nav_title: エデュメ
-article_title: エデュメ
-description: "このリファレンス記事では、Brazeと、モバイルベースのトレーニングリングツールであるeduMeとの提携について概説します。これにより、Brazeコネクテッドコンテンツを活用して、ユーザーがあなたのBraze キャンペーンの中のeduMe講座やレッスンを利用できるようになります。"
+nav_title: eduMe
+article_title: eduMe
+description: "このリファレンス記事では、Braze と eduMe のパートナーシップについて説明します。eduMe はモバイルベースのトレーニングツールであり、Braze コネクテッドコンテンツを利用して、ユーザーが Braze キャンペーンで eduMe のコースやレッスンにアクセスできるようにします。"
 alias: /partners/edume/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# エデュメ
+# eduMe
 
-> [eduMe](https://edume.com) は、モバイルベースのトレーニングリングツールで、必要なときに、成功するために必要な知識を、どこにいても、従業員に提供します。 
+> [eduMe](https://edume.com)はモバイルベースのトレーニングツールであり、従業員はどこからでも必要なときに、成功するために必要な知識を習得できます。 
 
-Braze とeduMe の統合は、Braze [Connected Content]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/#about-connected-content) を活用して、ユーザーがあなたのBraze キャンペーン s のeduMe コースとレッスンを利用できるようにします。個々のプログレスとグループプログレスは、eduMe レポートの機能を通じて追跡できます。
+Braze と eduMe の統合では、Braze [コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/#about-connected-content)を利用して、ユーザーが Braze キャンペーンで eduMe のコースやレッスンにアクセスできるようにします。個人とグループの進捗状況は、eduMe レポート機能で追跡できます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| eduMeアカウント | この提携の前進タグeを考慮するためには、eduMeの勘定が必要である。 |
-| エデュメAPI キー | API キーは、eduMe 顧客の成功連絡先にリクエストする必要があります。この鍵は、Braze接続内容呼び出しで使用されます。 |
-| eduMeリンク署名シークレット | 組織のリンクサインシークレットを設定するには、eduMe で顧客成功コンタクトをリクエストする必要があります。このシークレットは、接続コンテンツでシームレスなリンクを有効にするために使用されます。この秘密は何もする必要はありません。 |
-| eduMeグループとコンテンツID | これらの識別子は、接続コンテンツコールの設定に必要です。これらの識別子の入手方法については、eduMe 顧客の担当者までお問い合わせください。 |
+| eduMeアカウント | このパートナーシップを活用するには、eduMe アカウントが必要です。 |
+| eduMe API キー | eduMe のカスタマーサクセス担当者に API キーを依頼する必要があります。このキーは、Braze コネクテッドコンテンツ呼び出しで使用します。 |
+| eduMeリンク署名シークレット | eduMe のカスタマーサクセス担当者に組織のリンク署名シークレットの設定を依頼する必要があります。このシークレットは、接続コンテンツでシームレスなリンクを有効にするために使用されます。このシークレットにより、特に何らかの操作を行う必要がなくなります。 |
+| eduMeグループとコンテンツID | これらの識別子は、コネクテッドコンテンツ呼び出しを設定する際に必要です。これらの識別子の入手については、eduMe カスタマーサービス担当者までお問い合わせください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### 接続コンテンツコールの作成
+### コネクテッドコンテンツ呼び出しを作成する
 
-コース、レッスン、またはeNPS 調査をユーザーに利用できるようにし、eduMe の内部 ユーザー IDに対する進行状況を追跡するには、次の例に示すAPI 呼び出しに従います。
+ユーザーがコース、レッスン、eNPS アンケートを利用できるようにし、eduMe で内部ユーザー ID を使用してユーザーの進捗状況を追跡するには、次の例に示す API 呼び出しに従います。
 
 {% raw %}
 ```
@@ -46,10 +46,10 @@ Access your onboarding course at:
 {% endraw %}
 
 1. `YOUR-EDUME-API-KEY` をeduMe API キーに置き換えます。<br><br>
-2. `EDUME-CONTENT-LINK-AND-CONTENT-ID` を、対応するコンテンツリンク文字列とモジュール、レッスン、または調査 識別子に置き換えます。これらの識別子s は、あなたのeduMe アカウントにあります。
+2. `EDUME-CONTENT-LINK-AND-CONTENT-ID` を、対応するコンテンツリンク文字列とモジュール、レッスン、または調査 識別子に置き換えます。これらの識別子は、eduMe アカウントで確認できます。
   - コース: `getCourseLink?moduleId=12087`
-  - 教訓: `getLessonLink?lessonId=25805`
-  - eNPS調査: `getSurveyLink?surveyId=654`<br><br>
+  - レッスン: `getLessonLink?lessonId=25805`
+  - eNPS アンケート: `getSurveyLink?surveyId=654`<br><br>
 3. このリンクを通じてeduMeに到着したユーザーは、選択したeduMeチームまたはグループに追加されます。`groupId` を関連するチームID またはeduMe グループID に置き換えます。通常、チームID を使用しますが、登録が必要なコースはグループID を使用する必要があります<br><br>
-4. `externalUserId` フィールドをマップするアプリの適切なフィールドを含めます。コネクテッドコンテンツ呼び出しの例では、`driver_id` を使用しますが、フィールドは異なっている可能性があります。このID はeduMe レポート s で利用でき、システムと関連付けることができます。<br><br>
-5. 最後に、必要に応じてメッセージをカスタマイズしてテストします。少なくとも1つのテストメッセージを送信し、eduMeコンテンツにアクセスし、レッスンまたはコースを完了し、eduMe 分析が記録されていることを確認することをお勧めします。 
+4. `externalUserId` フィールドのマッピング先として適切なフィールドを含めます。コネクテッドコンテンツ呼び出しの例では、`driver_id` を使用しますが、フィールドは異なっている可能性があります。このID は eduMe レポートで利用可能になり、システムと相関付けることができるようになります。<br><br>
+5. 最後に、必要に応じてメッセージをカスタマイズしてテストします。少なくとも1つのテストメッセージを送信し、eduMe コンテンツにアクセスし、レッスンまたはコースを修了し、eduMe 分析が記録されていることを確認することをお勧めします。 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize.md b/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize.md
index 6b6f8153e86..fe44d6f19b9 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize.md
@@ -3,7 +3,7 @@ nav_title: Amazon Personalize
 noindex: true
 layout: dev_guide
 guide_top_header: "Amazon Personalize"
-guide_top_text: "Amazon Personalize を使用すると、機械学習の経験がない開発者が、高度なパーソナライゼーション機能をアプリのアプリケーションに簡単に構築できます。パーソナライズでは、アプリライセンスからのアクティビティストリームと、推奨するアイテムのインベントリを提供し、パーソナライズはデータを処理して、データにカスタマイズされたパーソナライゼーションモデルをトレーニングします。"
+guide_top_text: "Amazon Personalize を使用すると、機械学習の経験がない開発者が、高度なパーソナライゼーション機能をアプリのアプリケーションに簡単に構築できます。Personalize では、アプリケーションからアクティビティストリームを提供し、さらにおすすめアイテムのインベントリーを提供すると、Personalize でデータが処理され、データに合わせてカスタマイズされたパーソナライゼーションモデルの学習が行われます。"
 description: "このランディングページには、インテグレーションの指示やワークショップの案内など、Amazon Personalizeなすべてのものが掲載されています。"
 page_order: 0
 guide_featured_list:
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize.md b/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize.md
index 8cf33468da4..cbc7a0b017b 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize.md
@@ -2,7 +2,7 @@
 nav_title: Amazon Personalize
 article_title: Amazon Personalize
 alias: /partners/amazon_personalize/
-description: "このリファレンス記事では、BrazeとAmazon Personalizeのリファレンスアーキテクチャと統合について概説している。このリファレンス記事は、Amazon Personalizeが提供するユースケース、Amazon Personalizeが扱うデータ、サービスの設定方法、Brazeとの統合方法を理解するのに役立つ。"
+description: "このリファレンス記事では、Braze と Amazon Personalize のリファレンスアーキテクチャと、これらの統合について説明します。このリファレンス記事は、Amazon Personalizeが提供するユースケース、Amazon Personalizeが扱うデータ、サービスの設定方法、Brazeとの統合方法を理解するのに役立つ。"
 page_type: partner
 search_tag: Partner
 ---
@@ -21,7 +21,7 @@ Amazon Personalizeは、機械学習とあなたが定義したアルゴリズ
 
 | 必要条件| 説明|
 | ---| ---| 
-| アマゾン ウェブ サービス アカウント | このパートナーシップを利用するには、AWSアカウントが必要だ。AWSアカウントを取得したら、Amazon Personalizeコンソール、AWSコマンドラインインターフェイス（AWS CLI）、またはAWS SDKを通じてAmazon Personalizeにアクセスできる。 |
+| Amazon Web Service アカウント | このパートナーシップを利用するには、AWSアカウントが必要だ。AWS アカウントを取得したら、Amazon Personalize コンソール、AWS Command Line Interface (AWS CLI)、または AWS SDK を使用して Amazon Personalize にアクセスできます。 |
 | 定義されたユースケース | モデルを作成する前に、この統合のユースケースを決定しなければならない。一般的な使用例については、以下のリストを参照のこと。 |
 | データセット | アマゾンのパーソナライズ・レコメンデーション・モデルは、インタラクション、ユーザー、アイテムの3つの異なるタイプのデータセットを必要とする。各データセットの要件については、以下の詳細を参照のこと。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
@@ -46,16 +46,16 @@ Amazon Personalizeは、機械学習とあなたが定義したアルゴリズ
 Amazon Personalizeのレコメンデーション・モデルを使い始めるには、3種類のデータセットが必要だ：
 
 - 相互作用
-  - ユーザーとアイテムの過去のやりとりを保存する
-  - `USER_ID` 、`ITEM_ID` 、`EVENT_TYPE` 、`TIMESTAMP` の値が必要で、オプションでイベントに関するメタデータを受け付ける。
+  - ユーザーとアイテムの間のインタラクションの履歴を保存します
+  - `USER_ID`、`ITEM_ID`、`EVENT_TYPE`、`TIMESTAMP` の値が必要です。オプションでイベントに関するメタデータを受け入れます
 - ユーザー
   - ユーザーに関するメタデータを保存する
-  - `USER_ID` の値と、性別、年齢、ロイヤリティ会員などの少なくとも1つのメタデータフィールド（文字列または数値）が必要である。
+  - `USER_ID` の値と、性別、年齢、ロイヤルティメンバーシップなどのメタデータフィールド (文字列または数値) のうち1つ以上が必要です
 - アイテム
   - アイテムに関するメタデータを保存する
-  - `ITEM_ID` 、アイテムを説明する少なくとも1つのメタデータフィールド（テキスト、カテゴリー、数値）が必要である。
+  - `ITEM_ID` と、アイテムを記述する1つのメタデータフィールド (テキスト、カテゴリ、または数値) が必要です
 
-ユーザー推薦レシピでは、少なくとも25人のユニークなユーザーからの少なくとも1000ポイントのインタラクションデータを含むインタラクションデータセットを提供しなければならない。これらのデータセットは、S3に保存されたCSVファイルを使って一括アップロードすることも、APIを使って段階的にアップロードすることもできる。
+ユーザーレコメンデーションレシピの場合、25人以上の一意のユーザー (各ユーザーに2つ以上のインタラクションがある) からの1000ポイント以上のインタラクションデータを含むインタラクションデータセットを提供する必要があります。これらのデータセットは、S3に保存されたCSVファイルを使って一括アップロードすることも、APIを使って段階的にアップロードすることもできる。
 
 {% endtab %}
 {% endtabs %}
@@ -64,14 +64,14 @@ Amazon Personalizeのレコメンデーション・モデルを使い始める
 
 ### ステップ1:トレーニング
 
-データセットがインポートされたら、ソリューションを作成することができる。ソリューションは、Amazon Personalizeの[レシピ](https://docs.aws.amazon.com/personalize/latest/dg/working-with-predefined-recipes.html)（アルゴリズム）の1つを使用してモデルをトレーニングする。今回は、`USER_PERSONALIZATION` 。ソリューションをトレーニングすることで、ソリューション・バージョン（トレーニング済みモデル）が作成され、モデルのパフォーマンス・メトリクスに基づいて評価することができる。
+データセットがインポートされたら、ソリューションを作成することができる。ソリューションは、Amazon Personalizeの[レシピ](https://docs.aws.amazon.com/personalize/latest/dg/working-with-predefined-recipes.html)（アルゴリズム）の1つを使用してモデルをトレーニングする。Braze の場合 `USER_PERSONALIZATION` レシピを使用します。ソリューションをトレーニングすることで、ソリューション・バージョン（トレーニング済みモデル）が作成され、モデルのパフォーマンス・メトリクスに基づいて評価することができる。
 
 Amazon Personalizeでは、モデルがトレーニングに使用するハイパーパラメーターを調整することができる。以下に例を示します。
 - Amazon Personalizeコンソールにある "User history length percentile "パラメーターで、トレーニングに含めるユーザー履歴のパーセンタイルを調整できる：<br><br>![最小最大ユーザープロファイル設定][3]
-  - `min_user_history_length_percentile`履歴の長さが非常に短いユーザーを除外することで、人気のあるアイテムを除外し、より深い基本パターンに基づいたレコメンデーションを構築することができる。
-  - `max_user_history_length_percentile`非常に長い履歴長でトレーニングする場合に考慮するユーザーの割合を調整する。
+  - `min_user_history_length_percentile`: 履歴の長さが非常に短い一定割合のユーザーを除外します。これは、人気の高いアイテムを排除し、より深い基盤となるパターンに基づいてレコメンデーションを作成する際に役立ちます。
+  - `max_user_history_length_percentile`: トレーニングの際に考慮すべきである、履歴の長さが非常に長いユーザーの割合を調整します。
 
-隠れ次元の数は、複雑なデータセットに対してより複雑なパターンを検出するのに役立つ。一方、時間バックプロパゲーション技術（BPTT）は、価値の高い行動をもたらした一連の出来事が起こった後、初期の出来事に対する報酬を調整する。
+隠れ次元の数は、複雑なデータセットのより複雑なパターンを検出するのに役立ちます。一方、通時的誤差逆伝搬法 (BPTT) は、一連のイベントが発生し、その結果価値の高い行動がもたらされた後で、早期のイベントに対するリワードを調整します。
 
 さらに、Amazon Personalizeは、異なる値を持つ複数のバージョンのソリューションを同時に実行することで、ハイパーパラメータの自動チューニングを提供する。チューニングを使用するには、ソリューションの作成時に「**HPO を実行**」をオンにする。
 
@@ -82,29 +82,29 @@ Amazon Personalizeでは、モデルがトレーニングに使用するハイ
 - **割引累積利得を正規化する：**項目の推奨順序を実際の項目リストと比較し、各項目にリスト内の位置に対応する重みを与える。
 - **精度@k：**適切に推奨された項目の量を、推奨された全項目の量で割ったもの。`k` は項目の数である。
 - **平均相互ランク：**最初の、最も高いランクの推薦に焦点を当て、最初にマッチした推薦が表示される前に、推薦されたアイテムがいくつ表示されたかを計算する。
-- **カバレッジ：**データセット内のユニークなアイテムの総数に対する、ユニークな推奨アイテムの割合
+- **Coverage:** データセット内の一意のアイテムの総数に対する、一意の推奨されるアイテムの割合
 
-## 推薦を受ける
+## レコメンデーションの取得
 
-満足のいくソリューション・バージョンを作成したら、次はその推奨事項を使用する番だ。推薦状にアクセスするには2つの方法がある：
+満足のいくソリューション・バージョンを作成したら、次はその推奨事項を使用する番だ。レコメンデーションにアクセスするには、次の2つの方法があります。
 
-1. リアルタイム・キャンペーン<br>キャンペーンとは、定義された最小トランザクション・スループットを持つ、展開されたソリューション・バージョンのことである。トランザクションとは、レコメンデーション出力を得るための1回のAPIコールであり、TPS（1秒あたりのトランザクション数）として定義され、最小値は1である。負荷が増加した場合、キャンペーンはリソースをスケールさせるが、最小値を下回ることはない。コンソール、AWS CLI、またはコード内のAWS SDKを通してレコメンデーションを照会できる。<br><br>
-2. バッチジョブ<br>バッチジョブはS3バケットにレコメンデーションをエクスポートする。このジョブは、レコメンデーションをエクスポートしたいユーザーIDのリストを含むJSONファイルを入力とする。そして、正しいパーミッションと出力先を指定したら、ジョブを実行する準備が整った。実行時間は、データセットのサイズと推奨リストの長さに依存する。
+1. リアルタイム・キャンペーン<br>キャンペーンとは、定義された最小トランザクション・スループットを持つ、展開されたソリューション・バージョンのことである。トランザクションとは、レコメンデーション出力を得るための1回の API 呼び出しです。TPS (1秒あたりのトランザクション数) として定義され、最小値は1です。負荷が増加した場合、キャンペーンはリソースをスケーリングしますが、最小値を下回ることはありません。コンソール、AWS CLI、またはコードでの AWS SDK で、レコメンデーションをクエリできます。<br><br>
+2. バッチジョブ<br>バッチジョブはS3バケットにレコメンデーションをエクスポートする。このジョブは、レコメンデーションをエクスポートするユーザー ID のリストを含む JSON ファイルを入力として取ります。正しい権限と出力先を指定したら、ジョブを実行できます。実行時間は、データセットのサイズと推奨リストの長さに依存する。
 
 ### フィルター
 
-フィルターによって、アイテムのID、イベントタイプ、またはメタデータに基づいてアイテムを除外することで、レコメンデーション出力を調整することができる。また、年齢やロイヤリティ・メンバーシップのステータスなど、メタデータに基づいてユーザーをフィルタリングすることもできる。フィルターがあれば、ユーザーがすでに接したことのあるアイテムを推薦するのを防ぐことができる。
+フィルターによって、アイテムのID、イベントタイプ、またはメタデータに基づいてアイテムを除外することで、レコメンデーション出力を調整することができる。また、年齢やロイヤリティ・メンバーシップのステータスなど、メタデータに基づいてユーザーをフィルタリングすることもできる。フィルターは、ユーザーがすでにやり取りしたアイテムが推奨されることを防ぐ場合に役立ちます。
 
 ## 結果をBrazeと統合する
 
 作成したモデルとレコメンデーションキャンペーンがあれば、コンテンツカードとコネクテッドコンテンツを使って、ユーザーに対してBrazeキャンペーンを実施する準備が整う。
-Brazeキャンペーンを実行する前に、APIを通じてこれらのレコメンデーションを提供できるサービスを作成する必要がある。[ワークショップの記事のステップ3に従って][1]、AWSサービスを使ってサービスをデプロイすることができる。レコメンデーションを提供する独自の独立したバックエンド・サービスを展開することもできる。
+Brazeキャンペーンを実行する前に、APIを通じてこれらのレコメンデーションを提供できるサービスを作成する必要がある。[ワークショップ記事のステップ3][1]に従って、AWS サービスを使用してサービスをデプロイできます。レコメンデーションを提供する独自の独立したバックエンドサービスをデプロイすることもできます。
 
-### コンテンツ・カード・キャンペーンの使用例
+### コンテンツカードキャンペーンのユースケース
 
-リストの最初の推奨アイテムでコンテンツ・カード・キャンペーンを実施してみよう。<br><br>
-以下の例では、以下のクエリーを実行する。
-`GET http://<service-endpoint.com>/recommendations?user_id=user123` エンドポイントに`user_id` パラメータを渡すと、推奨アイテムのリストを返す：
+リストの最初の推奨アイテムを使用してコンテンツカードキャンペーンを実行してみます。<br><br>
+次の例では、
+`user_id` パラメーターを指定した `GET http://<service-endpoint.com>/recommendations?user_id=user123` エンドポイントをクエリします。これにより、推奨アイテムのリストが返されます。
 
 ```json
 [
@@ -126,7 +126,7 @@ Brazeキャンペーンを実行する前に、APIを通じてこれらのレコ
 ]
 ```
 
-Brazeダッシュボードで、新しい[コンテンツカードキャンペーンを]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/)作成する。メッセージ・テキスト・フィールドに、APIに問い合わせ、レスポンスを`recommendations` 変数に保存するConnected Content Liquidブロックを作成する：
+Braze ダッシュボードで、新しい[コンテンツカードキャンペーン]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/)を作成します。メッセージ・テキスト・フィールドに、APIに問い合わせ、レスポンスを`recommendations` 変数に保存するConnected Content Liquidブロックを作成する：
 
 {% raw %}
 
@@ -134,7 +134,7 @@ Brazeダッシュボードで、新しい[コンテンツカードキャンペ
 {% connected_content https:/<service-endpoint.com>/recommendations?user_id={{${user_id}}} :save recommendations %}
 ```
 
-そして、結果として得られる配列の最初の項目を参照し、その内容をユーザーに表示することができる：
+その後、結果として得られる配列の最初のアイテムを参照し、その内容をユーザーに対して表示できます。
 
 ```liquid
 This seems like a great fit for you:
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize/workshop.md b/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize/workshop.md
index bbd7c4cc747..8ffce678a36 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize/workshop.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/amazon_personalize/workshop.md
@@ -9,9 +9,9 @@ search_tag: Partner
 
 # Amazon Personalize workshop
 
-> このリファレンス記事では、Amazon Personalize を設定し、Connected Content を使用してBraze に統合する手順について説明します。これは、s をデプロイしてトレーニング Amazon Personalize ソリューションし、それらをBraze メール キャンペーンに統合するために必要なすべてのステップについて説明する実践的なワークショップを使用して行われます。
+> このリファレンス記事では、コネクテッドコンテンツを使用して Amazon Personalize を設定し、Braze 環境に統合するプロセスについて説明します。これは、s をデプロイしてトレーニング Amazon Personalize ソリューションし、それらをBraze メール キャンペーンに統合するために必要なすべてのステップについて説明する実践的なワークショップを使用して行われます。
 
-以下のサンプルは、Retail Demo Store と呼ばれる完全に機能するサンプルe コマースサイトにデプロイされます。このチュートリアルのリソースとコードは、[ AWS Samples Retail Demo Store](https://github.com/aws-samples/retail-demo-store/) に公開されています。このリファレンスアーキテクチャインプリメンテーションをアウトラインとして使用して、独自の環境にAmazon Personalizeをインプリメントできます。
+以下の例は、Retail Demo Store という名前の完全に機能するサンプル e コマースサイトで展開されています。このチュートリアルのリソースとコードは、[ AWS Samples Retail Demo Store](https://github.com/aws-samples/retail-demo-store/) に公開されています。このリファレンスアーキテクチャインプリメンテーションをアウトラインとして使用して、独自の環境にAmazon Personalizeをインプリメントできます。
 
 ## 要件
 
@@ -19,58 +19,58 @@ search_tag: Partner
 
 ## 統合アーキテクチャ
 
-ユーザー s にパーソナライズされたを送信するBrazeを設定するには、まず、例としてRetail Demo Store アーキテクチャを使用して、一般的なe コマース Web サイトに必要な関連コンポーネントを確認します。
+パーソナライズされたメッセージをユーザーに送信するように Braze を設定する前に、Retail Demo Store アーキテクチャを例に、一般的な e コマース Web サイトに必要な関連コンポーネントを確認します。
 
-![さまざまなコンポーネントが互いにどのように相互作用するかを示すBraze パーソナライゼーションアーキテクチャを分解する"画像。]({% image_buster /assets/img/amazon_personalize/braze-personalize-arch.png %}){: style="max-width:70%" }
+![さまざまなコンポーネントの相互作用を示すBraze パーソナライゼーションアーキテクチャの分解図。]({% image_buster /assets/img/amazon_personalize/braze-personalize-arch.png %}){: style="max-width:70%" }
 
 1. リテールデモストアのWeb UI では、AWS Amplify JavaScript ライブラリーを使用して、トレーニングリングイベントをAmazon Personalize に送信します。
-2. Braze キャンペーン ユーザーレコードは、グローバルストアユーザーから更新されます。
-3. Braze キャンペーンの実行時に、接続コンテンツテンプレートを使用して、パーソナライズから推奨事項を取得し、対象ユーザーのメール テンプレートを入力します。
+2. Braze キャンペーンユーザーレコードは、Global Store User サービスから更新されます。
+3. Braze キャンペーンの実行時に、コネクテッドコンテンツテンプレートを使用して、Personalize からレコメンデーションを取得し、ターゲットユーザーのメールテンプレートを入力します。
 4. 推奨機種のトレーニングにも、商品カタログをご利用いただけます。
 
-Braze は、ユーザープロファイルs の振る舞いまたは属性s に基づいてメールs をユーザーs に送信します。この情報は、ユーザーsを特定し、ユーザープロファイルsを構築するのに役立ち、いつメッセージまたはメールを送信するかを決定するのに役立ちます。
+Braze は、ユーザープロファイルの行動または属性に基づいてユーザーにメールを送信します。このデータは、ユーザーを識別し、ユーザープロファイルを作成して、メッセージまたはメールを送信するタイミングかを決定するのに役立ちます。
 
-このイベントデータフローは、Amazon Personalize に送信される動作イベントデータと並行してh をアプリします。このワークショップでは、デモストアはAmplifyを使用してパーソナライズにイベントを送信します。このデータは、推奨モデルをトレーニングするために使用されます。このモデルは、Braze キャンペーンの実行時にコンテンツをパーソナライズしてユーザーにするためのBraze接続コンテンツ呼び出しで使用できます。
+このイベントデータフローは、Amazon Personalize に送信される行動イベントデータと並行して発生します。このワークショップでは、デモストアで Amplify を使用して Personalize にイベントを送信します。このデータは、レコメンデーションモデルのトレーニングに使用されます。その後レコメンデーションモデルは、Braze キャンペーンの実行時にユーザーに対してコンテンツをパーソナライズするための Braze コネクテッドコンテンツ呼び出しで使用できます。
 
-Braze接続コンテンツは、AWSで実行されているレコメンドサービスを介して、これらのレコメンドを取得できます。Retail Demo Store ワークショップには、推奨サービス展開の例が表示されます。独自のインフラのデプロイシナリオでは、同様のサービスをデプロイして、独自のカタログサービスから項目を取得する必要があります。
+Braze コネクテッドコンテンツは、AWS で実行されているレコメンデーションサービスからこれらのレコメンドを取得できます。Retail Demo Store ワークショップでは、レコメンデーションサービスの導入の例が示されます。独自のインフラのデプロイシナリオでは、同様のサービスをデプロイして、独自のカタログサービスから項目を取得する必要があります。
 
 ## リファレンスアーキテクチャワークショップのセットアップ
 
-### ステップ1:AWS アカウントに小売デモストアをデプロイする
+### ステップ1:AWS アカウントに Retail Demo Store をデプロイする
 
-![使用可能なAWSリージョンの"画像。][2]{: style="float:right;max-width:40%;margin-top:15px;margin-bottom:10px;"}
+![使用可能な AWS リージョン。][2]{: style="float:right;max-width:40%;margin-top:15px;margin-bottom:10px;"}
 
-次のテーブルでは、**AWS Region**を選択し、**Launch Stack**を選択します。このリストは、プロジェクトをデプロイできるすべての可能なリージョンを示すものではなく、Retail Demo Store でデプロイするために現在設定されているリージョンのみを表しています。
+次の表で \[**AWS Region**] を選択し、\[**Launch Stack**] を選択します。このリストは、プロジェクトをデプロイできるすべてのリージョンを示すものではなく、Retail Demo Store のデプロイのために現在設定されているリージョンのみを示しています。
 
-テンプレートのすべてのデフォルトパラメータを受け入れます。すべてのプロジェクトリソースのデプロイには、25 ～30 分かかります。
+テンプレートのすべてのデフォルトパラメータを受け入れます。すべてのプロジェクトリソースのデプロイには25～30分かかります。
 
 ### ステップ2:ビルドAmazon Personalize キャンペーン
 
-パーソナライズされたのプロダクト推奨事項を提供するには、まずマシンラーニングモデルをトレーニングし、Amazon Personalizeから推奨事項を得るための推論エンドポイントを提供する必要があります。ステップ 1 にデプロイされたCloudFormation テンプレートには、詳細なステップごとの手順を持つJupyter 以外のeBookを提供するAmazon SageMaker not eBook インスタンスが含まれています。
+パーソナライズされたのプロダクト推奨事項を提供するには、まずマシンラーニングモデルをトレーニングし、Amazon Personalizeから推奨事項を得るための推論エンドポイントを提供する必要があります。ステップ1でデプロイされた CloudFormation テンプレートには、詳細な手順を含む Jupyter ノートブックを提供する Amazon SageMaker ノートブックインスタンスが含まれています。
 
 1. ステップ 1 でAWS CloudFormation テンプレートをデプロイしたAWS アカウントにサインインします。
-2. Amazon SageMaker コンソールで、**Not eBook instances** を選択します。
-3. **RetailDemoStore** not eBook インスタンスが表示されない場合は、ステップ 1 でプロジェクトをデプロイしたリージョンと同じリージョンにいることを確認します。
-4. 非eBook インスタンスにアクセスするには、**Open Jupyter** または**Open JupyterLab** を選択します。
-5. Jupyter ウェブインターフェイスにnot eBook インスタンスの読み込むed がある場合は、`workshop/1-Personalization/1.1-Personalize.ipynb` not eBookを選択します。eBookでないサブディレクトリを表示するには、`workshop` フォルダーを選択する必要があります。
-6. `1.1-Personalize` がeBook 開封でない場合は、それぞれのセルを実行してワークショップをステップします。Jupyter ツールバーから**Run** を選択して、セル内のコードを順番に実行できます。未eBookの完了には、約2時間のアプリがかかります。
+2. Amazon SageMaker コンソールで \[**Notebook instances**] を選択します。
+3. **RetailDemoStore** ノートブックインスタンスが表示されない場合は、ステップ1でプロジェクトをデプロイしたリージョンと同じリージョンにいることを確認してください。
+4. ノートブックインスタンスにアクセスするには、\[**Open Jupyter**] または \[**Open JupyterLab**] を選択します。
+5. Jupyter Web インターフェイスがノートブックインスタンスに読み込まれたら、`workshop/1-Personalization/1.1-Personalize.ipynb` ノートブックを選択します。ノートブックのサブディレクトリを表示するには、`workshop` フォルダーを選択する必要があります。
+6. `1.1-Personalize` ノートブックが開いている場合は、各セルを実行してワークショップを順に実行します。Jupyter ツールバーから**Run** を選択して、セル内のコードを順番に実行できます。ノートブックが完了するまでには約2時間かかります。
 
-### ステップ3:Brazeからパーソナライズされた メールを送信
+### ステップ3:Braze からパーソナライズされたメールを送信する
 
-Amazon Personalize ソリューション s とキャンペーン s を使用すると、小売デモストアのインスタンスがメール キャンペーンに推奨事項を提供する準備が整います。ステップ 1 では、デモWeb アプリライセンスとすべての関連サービスをデプロイしました。これには、ステップ 2 でデプロイしたAmazon Personalize キャンペーンを使用するConnected Content を介してメール キャンペーン s をBraze と統合するために必要なレコメンドサービスが含まれます。
+Amazon Personalize ソリューションとキャンペーンを導入することで、Retail Demo Store のインスタンスがメールキャンペーンにレコメンデーションを提供できるようになります。ステップ1では、デモ Web アプリケーションとすべての関連サービスをデプロイしました。これには、コネクテッドコンテンツを介して Braze とメールキャンペーンを統合するために必要なレコメンデーションサービスが含まれています。これは、ステップ2でデプロイした Amazon Personalize キャンペーンを使用します。
 
 ステップ 2のパーソナライゼーションワークショップと同様に、次のBraze メッセージングワークショップでは、設定を使用してBrazeとAmazon Personalizeインテグレーションを設定します。
 
 1. ステップ 1 でAWS CloudFormation テンプレートをデプロイしたAWS アカウントにサインインします。
-2. Amazon SageMaker コンソールで、**Not eBook Instances**を選択します。
-3. **RetailDemoStore** not eBook インスタンスが表示されない場合は、プロジェクトをデプロイしたのと同じAWS リージョンにいることを確認します。
-4. 非eBook インスタンスにアクセスするには、**Open Jupyter** または**Open JupyterLab** を選択します。
-5. Jupyter ウェブインターフェイスにnot eBook インスタンスの読み込むed がある場合は、`workshop/4-Messaging/4.2-Braze.ipynb` not eBookを選択します。eBookでないサブディレクトリを表示するには、`workshop` フォルダーを選択する必要があります。
-6. `4.2-Braze` がeBook 開封でない場合は、それぞれのセルを実行してワークショップをステップします。Jupyter ツールバーから**Run** を選択して、セル内のコードを順番に実行できます。未eBookは、完了までに約1時間のアプリがかかります。
+2. Amazon SageMaker コンソールで \[**Notebook instances**] を選択します。
+3. **RetailDemoStore** ノートブックインスタンスが表示されない場合は、ステップ1でプロジェクトをデプロイした AWS リージョンと同じリージョンにいることを確認してください。
+4. ノートブックインスタンスにアクセスするには、\[**Open Jupyter**] または \[**Open JupyterLab**] を選択します。
+5. Jupyter Web インターフェイスがノートブックインスタンスに読み込まれたら、`workshop/4-Messaging/4.2-Braze.ipynb` ノートブックを選択します。ノートブックのサブディレクトリを表示するには、`workshop` フォルダーを選択する必要があります。
+6. `4.2-Braze` ノートブックが開いている場合は、各セルを実行してワークショップを順に実行します。Jupyter ツールバーから**Run** を選択して、セル内のコードを順番に実行できます。ノートブックが完了するまでには約1時間かかります。
 
 ### ステップ4:リソースのクリーンアップ
 
-将来の課金を回避するには、ステップ 1 で作成したAWS CloudFormation スタックを削除して作成したRetail Demo Store プロジェクトのAWS リソースを削除します。
+今後料金が発生しないようにするため、作成した Retail Demo Store プロジェクトの AWS リソースを削除します。このためには、ステップ1で作成した AWS CloudFormation スタックを削除します。
 
 [1]: {% image_buster /assets/img/amazon_personalize/braze-personalize-arch.png %}
 [2]: {% image_buster /assets/img/amazon_personalize/region.png %}
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/certona.md b/_lang/ja/_partners/message_personalization/dynamic_content/certona.md
index 1b6736daedd..50f0bc4d5f2 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/certona.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/certona.md
@@ -2,7 +2,7 @@
 nav_title: Certona
 article_title: Certona
 alias: /partners/certona/
-description: "この参考記事では、顧客ライフサイクル全体にわたってパーソナライゼーションを提供するリアルタイム・オムニチャネル・パーソナライゼーション・ソリューションであるBrazeとCertonaのパートナーシップについて概説している。CertonaをBrazeのConnected Contentパートナーと併用することで、マルチチャネルキャンペーンにコンテンツ推薦を簡単に挿入できる。"
+description: "この参考記事では、顧客ライフサイクル全体にわたってパーソナライゼーションを提供するリアルタイム・オムニチャネル・パーソナライゼーション・ソリューションであるBrazeとCertonaのパートナーシップについて概説している。Certona と Braze のコネクテッドコンテンツパートナーを使用すると、マルチチャネルキャンペーン間でコンテンツのレコメンデーションを簡単に挿入できます。"
 page_type: partner
 search_tag: Partner
 
@@ -10,36 +10,36 @@ search_tag: Partner
 
 # Certona
 
-> Certonaのプラットフォームは、顧客ライフサイクル全体にわたってパーソナライゼーションを推進する。高度にパーソナライズされたEメールキャンペーンから、機械学習による製品推奨まで、Certonaはパーソナライゼーションの力を確実に活用する。
+> Certona のプラットフォームでは、カスタマーライフサイクル全体でパーソナライゼーションが推進されます。高度にパーソナライズされたEメールキャンペーンから、機械学習による製品推奨まで、Certonaはパーソナライゼーションの力を確実に活用する。
 
-BrazeとCertonaの統合は、コネクテッド・コンテンツを通じて、BrazeのキャンペーンとCanvasesでCertonaの機械学習による製品推奨を活用する。
+Braze と Certona の統合では、コネクテッドコンテンツを介して Certona の機械学習製品のレコメンデーションが Braze キャンペーンとキャンバスで利用されます。
 
 ## 前提条件
 
 | 必要条件| 説明|
 | ---| ---|
-| [セルトナアカウント](https://manage.certona.com/) | このパートナーシップを利用するには、セルトナ・アカウントが必要である。 |
+| [Certona アカウント](https://manage.certona.com/) | このパートナーシップを活用するには、Certona アカウントが必要です。 |
 | [Certona REST APIエンドポイント](https://manage.certona.com/) | このエンドポイントは、Brazeキャンペーンメッセージで直接使用され、ユーザーIDに基づいて推奨コンテンツを引き出す。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-Certona の REST API を使用して、パーソナライズされたコンテンツをメッセージに挿入する。これは、以下のConnected Contentテンプレートを、Certona REST APIエンドポイントとともに、Brazeメッセージコンポーザーに追加することで行うことができる。
+Certona の REST API を使用して、パーソナライズされたコンテンツをメッセージに挿入する。これを行うには、Certona REST API エンドポイントとともに、次のコネクテッドコンテンツテンプレートを Braze メッセージ作成画面に追加します。
 
 {% raw %}
 ```liquid
 {% connected_content {CERTONA_REST_API_KEY} :save recommendations %}
 ```
 
-次に、関連するテキストや画像など、呼び出したいコンテンツを定義する。例えば、`{{recommendations.CertonaObject.RecommendedItems[0].Items[0].name}}` 。
+次に、関連するテキストや画像など、呼び出したいコンテンツを定義する。たとえば `{{recommendations.CertonaObject.RecommendedItems[0].Items[0].name}}` です。
 
 {% endraw %}
 
-![サートナに関連するコネクテッド・コンテンツがメッセージ本文に含まれるプッシュ・キャンペーンのイメージ。][1]
+![メッセージ本文に含まれる Certona 関連のコネクテッドコンテンツを使用したプッシュキャンペーン。][1]
 
-このメッセージをコンポーザー本体に入れたら、コネクテッド・コンテンツの呼び出しをプレビューし、正しい情報が表示されていることを確認する。
+このメッセージを作成画面に追加したら、コネクテッドコンテンツの呼び出しをプレビューし、正しい情報が表示されていることを確認します。
 
-![Test "タブを示す画像は、送信前にメッセージを徹底的にテストすることをユーザーに促している。][2]
+![送信前にメッセージを完全にテストするようにユーザーに促す \[Test] タブ。][2]
 
 [1]: {% image_buster /assets/img/certona.png %}
 [2]: {% image_buster /assets/img/certona2.png %}
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/dynamic_yield.md b/_lang/ja/_partners/message_personalization/dynamic_content/dynamic_yield.md
index bf424ec9ede..577febccd98 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/dynamic_yield.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/dynamic_yield.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Dynamic Yield
 article_title: Dynamic Yield
-description: "この参考記事では、ブレイズとダイナミック・イールドのパートナーシップについて概説している。この提携により、Dynamic Yieldのレコメンデーションとセグメンテーション・エンジンを活用して、Brazeメッセージに埋め込むことができるエクスペリエンス・ブロックを作成することができる。"
+description: "このリファレンス記事では、Braze と Dynamic Yieldのパートナーシップについて説明します。この提携により、Dynamic Yieldのレコメンデーションとセグメンテーション・エンジンを活用して、Brazeメッセージに埋め込むことができるエクスペリエンス・ブロックを作成することができる。"
 alias: /partners/dynamic_yield/
 page_type: partner
 search_tag: Partner
@@ -12,15 +12,15 @@ search_tag: Partner
 
 > Mastercardの子会社である[Dynamic Yieldは](https://www.dynamicyield.com/)、パーソナライズされ、最適化され、同期化されたデジタル顧客体験を提供できるよう、さまざまな業種の企業を支援している。Dynamic Yieldの[Experience OSにより](http://www.dynamicyield.com/experience-os)、マーケティング担当者、プロダクトマネージャー、開発者、デジタルチームは、コンテンツ、製品、オファーを各顧客にアルゴリズムでマッチングさせ、収益と顧客ロイヤルティを加速させることができる。
 
-BrazeとDynamic Yieldのパートナーシップにより、Dynamic Yieldのレコメンデーションとセグメンテーションエンジンを活用して、Brazeメッセージに埋め込むことができるエクスペリエンスブロックを作成することができる。エクスペリエンス・ブロックの材質は様々である：
-- **推薦ブロック**アルゴリズムとフィルタリングを設定し、ユーザーのパーソナライズされたコンテンツを配信する。 
-- **ダイナミック・コンテンツ・ブロック**：ユーザーごとに異なるプロモーションやメッセージをターゲットにする。ターゲティングは、親和性または聴衆のいずれかに基づくことができる。Dynamic Yieldは、メールが開封されたときに、どのパーソナライズされた体験を提供するかを決定する。 
+Braze と Dynamic Yield のパートナーシップにより、Dynamic Yield のレコメンデーションとセグメンテーションエンジンを利用して、Braze メッセージに埋め込むことができるエクスペリエンスブロックを作成できます。エクスペリエンスブロックは以下のブロックで構成できます。
+- **レコメンデーションブロック**:メールの開封時に伝播されるユーザーのパーソナライズ済みコンテンツを提供するためのアルゴリズムとフィルターを設定します。 
+- **ダイナミックコンテンツブロック**:ユーザーごとに異なるプロモーションやメッセージをターゲットにする。ターゲティングは、アフィニティまたはオーディエンスのいずれかに基づいて行うことができます。Dynamic Yield は、メールの開封時にどのパーソナライズ済みエクスペリエンスを提供するかを決定します。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| ダイナミック・イールド口座 | このパートナーシップを利用するには、[ダイナミック・イールド](https://adm.dynamicyield.com/users/sign_in#/r/dashboard)口座が必要である。 |
+| Dynamic Yield アカウント | このパートナーシップを利用するには、[ダイナミック・イールド](https://adm.dynamicyield.com/users/sign_in#/r/dashboard)口座が必要である。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
@@ -33,38 +33,38 @@ BrazeとDynamic Yieldのパートナーシップにより、Dynamic Yieldのレ
 
 ### ステップ2:メッセージの下書きをする
 
-次の画像は、ビルダーでゼロからEメールを作成したものである。<br>![][6]
+次の画像は、ビルダーでゼロから作成するメールを示しています。<br>![][6]
 
 1. 見出しエリアにキャンペーン名、メモ、キャンペーンのラベルを入力する。<br><br>
-2. 経験ブロックを挿入する。これらのブロックには次のようなものがある：
-  - [推薦する](#configure-a-recommendations-block)：完全にパーソナライズされたレコメンデーションをユーザーに提供するウィジェット。
-  - [ダイナミックなコンテンツ](#configure-a-dynamic-content-block)：さまざまなプロモーションやメッセージを、さまざまなオーディエンスに向けて発信する。<br><br>
+2. エクスペリエンスブロックを挿入します。エクスペリエンスブロックには、次のものがあります。
+  - [レコメンデーション](#configure-a-recommendations-block):完全にパーソナライズされたレコメンデーションをユーザーに提供するウィジェット。
+  - [ダイナミックコンテンツ](#configure-a-dynamic-content-block):さまざまなプロモーションやメッセージを、さまざまなオーディエンスに向けて発信する。<br><br>
 3. 設定を更新する：
   - URLパラメータを使用して、アナリティクスソフトウェアでクリックを追跡する（オプション）。必要に応じて、デフォルトの表示にパラメータを追加する。
-  - 属性ウィンドウを7日間（デフォルト）または1日のいずれかを選択する。<br><br>
-4. 保存して終了する。コードが生成される前であれば、いつでもEメールのすべての要素を編集することができる。コードが生成された後、[コードに影響を与えない](https://support.dynamicyield.com/hc/en-us/articles/4404013832465-Experience-Email#h_01FAZPXB6MH094J1MWS5N86FXH)ものであれば何でも編集できる。
+  - アトリビュート期間として7日間 (デフォルト) または1日を選択します。<br><br>
+4. 保存して終了する。コードが生成される前であればいつでも、メールのすべての要素を編集できます。コードが生成された後、[コードに影響を与えない](https://support.dynamicyield.com/hc/en-us/articles/4404013832465-Experience-Email#h_01FAZPXB6MH094J1MWS5N86FXH)ものであれば何でも編集できる。
 
 ### レコメンデーション・ブロックを設定する
 
-レコメンデーション・ブロックでは、アルゴリズムやフィルタリングを設定し、メールが開封された際にユーザーにパーソナライズされたコンテンツを配信することができる。 
+レコメンデーションブロックでは、メールの開封時に伝播されるユーザーのパーソナライズ済みコンテンツを提供するためのアルゴリズムとフィルターを設定できます。 
 
 1. 編集ペインからレコメンデーションブロックをメール本文にドラッグする。<br><br>
 2. 希望するアルゴリズム（人気度、ユーザー親和性、類似度など）を選択する。選択されたアルゴリズムに応じて、追加のオプションが表示される： 
   - レコメンデーションが人気に基づいている場合、閲覧者が開いた異なるメールから同じレコメンデーションが提供されるのを避けるために、結果をシャッフルすることができる。
-  - 類似性のような他のアルゴリズムは、文脈に依存して、あなたが含める項目を選択することを必要とする推薦を提供する。これらの項目は、ビルダーで追加することもできるし、[埋め込みコードにマージタグを追加して](https://support.dynamicyield.com/hc/en-us/articles/4404013832465-Experience-Email#advanced)ダイナミックにすることもできる。<br><br>
-3. ユーザーがすでに購入した商品を除外して、これらの商品を勧めないようにすることができる。<br><br>
-4. [カスタムファイラーのルールを](https://support.dynamicyield.com/hc/en-us/articles/4404013832465-Experience-Email#h_01FAZP4ZWZX1JJ2SH61MB3HVXD)追加して、特定の製品をスロットに固定したり、製品プロパティによって製品を含めたり除外したりすることができる。例えば、コードが5ドル以下の商品は表示しないとか、ショートパンツカテゴリーの商品だけを表示する。<br><br>
-5. 最後に、推薦ブロックのデザインを設定する。これを行うには、アイテム・テンプレートを選択し、表示するアイテムの数と行数を設定する。 
+  - 類似性のような他のアルゴリズムは、文脈に依存して、あなたが含める項目を選択することを必要とする推薦を提供する。これらのアイテムをビルダーで追加するか、[埋め込みコードにマージタグを追加して](https://support.dynamicyield.com/hc/en-us/articles/4404013832465-Experience-Email#advanced)ダイナミックにすることもできます。たとえば、類似するアイテムを配送確認メールに追加する場合などです。<br><br>
+3. ユーザーがすでに購入している製品を除外して、これらの製品をレコメンドしないようにできます。<br><br>
+4. [カスタムファイラールール](https://support.dynamicyield.com/hc/en-us/articles/4404013832465-Experience-Email#h_01FAZP4ZWZX1JJ2SH61MB3HVXD)を追加して、特定の製品をスロットに固定したり、製品プロパティに基づいて製品を含めたり除外したりすることができます。例えば、コードが5ドル以下の商品は表示しないとか、ショートパンツカテゴリーの商品だけを表示する。<br><br>
+5. 最後に、推薦ブロックのデザインを設定する。これを行うには、アイテムテンプレートを選択し、表示するアイテムの数と行数を設定します。 
 
-### ダイナミック・コンテンツ・ブロックを設定する
-ダイナミック・コンテンツを使用して、ユーザーごとに異なるプロモーションやメッセージをターゲットにする。ターゲティングは、親和性または聴衆のいずれかに基づくことができる。Dynamic Yieldは、メールが開封されたときに、どのパーソナライズされた体験を提供するかを決定する。 
+### ダイナミックコンテンツブロックを設定する
+ダイナミック・コンテンツを使用して、ユーザーごとに異なるプロモーションやメッセージをターゲットにする。ターゲティングは、アフィニティまたはオーディエンスのいずれかに基づいて行うことができます。Dynamic Yield は、メールの開封時にどのパーソナライズ済みエクスペリエンスを提供するかを決定します。 
 
 1. ダイナミックコンテンツブロックを編集ペインからメール本文にドラッグする。<br><br> 
-2. 最初のバリエーションのテンプレートを選択する。デザイン変数とコンテンツ変数を定義できるようになった。完了したらバリエーションを保存する。<br>![][4]<br><br> 
+2. 最初のバリエーションのテンプレートを選択する。デザイン変数とコンテンツ変数を定義できるようになった。完了したらバリエーションを保存します。<br>![][4]<br><br> 
 3. ダイナミックコンテンツペインでオーディエンスを設定する。<br>![][5]<br><br> 
 4. 別のバリエーションを追加して、別の特定のオーディエンスやすべてのユーザーをターゲットにする。必要に応じて繰り返す。<br><br> 
 5. 上下の矢印を使って、バリエーションの優先順位を設定する。<br><br> 
-6. 優先順位は、ユーザーが複数のエクスペリエンスに適格である場合に、どのバリエーションを提供するかを決定する。
+6. 優先順位により、ユーザーが複数のエクスペリエンスの対象である場合に、どのバリエーションを提供するかが決定します。
 
 ### ステップ3:EメールをBrazeに統合する
 
@@ -73,7 +73,7 @@ BrazeとDynamic Yieldのパートナーシップにより、Dynamic Yieldのレ
 1. エクスペリエンス メールの一覧ページで、\[ESP 統合] アイコンをクリックする。<br><br> 
 2. ユーザーのCUIDとEメールIDを挿入するBrazeの関連トークンを入力する。<br>![][3]
   
-Eメールに満足したら、次はBrazeに埋め込むためのコードを生成する。
+メールに満足したら、次に Braze に埋め込むコードを生成します。
 1. **エクスペリエンス・メール**］で［**コードを生成**］をクリックする。<br><br> 
 2. 次に、「**クリップボードにコピー**」をクリックする。<br>![][1]<br><br> 
 3. コードをBrazeのメールキャンペーンに貼り付け、メールキャンペーンのデザイン、テスト、公開を続ける。
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/fresh_relevance.md b/_lang/ja/_partners/message_personalization/dynamic_content/fresh_relevance.md
index e46c9784735..0fa698c8a5c 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/fresh_relevance.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/fresh_relevance.md
@@ -10,20 +10,20 @@ search_tag: Partner
 
 # Fresh Relevance
 
-> [Fresh Relevance][1]は、コマース主導のビジネスが簡単にカスタマイズされたクロスチャネルの体験を作成できるようにする多用途のパーソナライゼーションソリューションです。プラットフォームは時間を節約し、技術スタックと統合し、ITチームに依存せずに、Webサイト、アプリ、メール、SMS、広告全体でコンバージョンを向上させるパーソナライズされた顧客体験を提供する力を与えます。
+> [Fresh Relevance][1]は、コマース主導のビジネスが簡単にカスタマイズされたクロスチャネルの体験を作成できるようにする多用途のパーソナライゼーションソリューションです。このプラットフォームは、時間を節約し、技術スタックと統合し、IT チームに頼ることなく、Web サイト、アプリ、メール、SMS、広告全体でコンバージョンを高めるパーソナライズされたカスタマーエクスペリエンスを提供できるようにします。
 
 BrazeとFresh Relevanceの統合により、次のことが可能になります:
 * 高度なトリガー付きメールキャンペーンを送信します。例えば、価格の下落、在庫の復活、複数段階の閲覧、またはカート放棄メッセージなどです。
 * トリガーされたメールにパーソナライズされたコンテンツを含めます。例えば、顧客が閲覧した商品や同じカテゴリ内のアイテムに基づいた商品推薦などです。
 * AI駆動の推奨事項、カウントダウンタイマー、リアルタイムの天気予報、ソーシャルメディアフィードなどを使用して、バルクメールキャンペーンをパーソナライズします。
-* データキャプチャポップアップを通じて収集された新しい連絡先でメールデータベースを成長させます。
+* データキャプチャポップアップで収集された新しい連絡先をメールデータベースに追加してこのデータベースを拡大します。
 * Braze メールリンクから到着した Web サイト訪問者を特定します。
 
 ## 前提条件
 
 | 要件 | 説明 |
 |-------------| ----------- |
-| Fresh Relevanceアカウント  | このパートナーシップを利用するには、Fresh Relevanceアカウントが必要です。 |
+| Fresh Relevance アカウント  | このパートナーシップを活用するには、Fresh Relevance アカウントが必要です。 |
 | Braze REST API キー | 以下に記載されているエンドポイントに十分な権限を持つBraze REST APIキー。<br><br> これはBrazeのダッシュボードで**設定** > **APIキー**から作成できます。 |
 | Braze REST エンドポイント | [あなたのRESTエンドポイントURL][3]。お客様のエンドポイントは、お客様のインスタンスのBraze URLに依存します。 |
 | Braze キャンペーン ID | 送信に使用したいデフォルトのBrazeキャンペーン。 |
@@ -31,11 +31,11 @@ BrazeとFresh Relevanceの統合により、次のことが可能になります
 
 ## 統合
 
-Fresh Relevanceで統合を設定するには、**メッセージングチャネル**でBrazeチャネルを作成し、必要に応じて適切なFresh Relevanceトリガーやコンテンツでチャネルを使用する必要があります。 
+Fresh Relevance で統合を設定するには、\[**Messaging Channels**] でBraze チャネルを作成し、必要に応じて適切な Fresh Relevance トリガーまたはコンテンツでこのチャネルを使用する必要があります。 
 
 ステップバイステップの手順については、Fresh Relevanceにログインして、彼らの[ドキュメント][2]に従ってください。
 
-Fresh Relevanceシステムは、提供されたAPIキーを使用してBrazeと通信します。完全な統合では、次のBraze APIエンドポイントを使用します:
+Fresh Relevance システムは、提供された API キーを使用して Braze と通信します。完全な統合では、次のBraze APIエンドポイントを使用します:
 
 * [`/users/alias/new`][4]
 * [`/users/track`][5]
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/judo.md b/_lang/ja/_partners/message_personalization/dynamic_content/judo.md
index 46ff62ae1ae..3e97f93a07f 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/judo.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/judo.md
@@ -10,57 +10,57 @@ search_tag: Partner
 
 # Judo
 
-> [Judoは](https://judo.app)サーバー駆動型のUIプラットフォームで、パブリッシャーがアプリを更新することなく、リッチで魅力的なアプリ内ユーザー体験を効率的に提供できるようにする。
+> [Judo](https://judo.app) はサーバー駆動型 UI プラットフォームであり、パブリッシャーがアプリを更新せずに、リッチで魅力的なアプリ内ユーザーエクスペリエンスを効率的に提供できるようにします。
 
-BrazeとJudoの統合は、キャンペーンやCanvasにオーダーメイドの体験を提供する。Brazeのキャンペーンでは、シンプルなテンプレート化されたランディングページ体験の代わりに、複数のスクリーン、モーダル、動画、カスタムフォント、ダークモードやアクセシビリティなどのサポート設定からなるコンテンツを組み込むことができる。Brazeのデータは、柔道エクスペリエンスでパーソナライズされたコンテンツをサポートするためにも使用されることがある。ユーザーイベントとエクスペリエンスからのデータは、アトリビューションとターゲティングのためにBrazeにフィードバックできる。
+Braze と Judo の統合により、キャンペーンとキャンバスで特別にカスタマイズされたエクスペリエンスが実現します。Braze キャンペーンには、シンプルなテンプレート化されたランディングページエクスペリエンスの代わりに、複数の画面、モーダル、動画、カスタムフォント、サポート設定 (コードを使わず作成され、アプリ更新なしでデプロイされるアクセシビリティ機能やダークモードなど) からなるコンテンツを組み込むことができます。Judo エクスペリエンスでパーソナライズされたコンテンツをサポートするために、Braze のデータを使用することもできます。ユーザーイベントとエクスペリエンスからのデータは、アトリビューションとターゲティングのためにBrazeにフィードバックできる。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| 柔道アカウント | このパートナーシップを利用するには、[柔道](https://www.judo.app/)アカウントが必要である。 |
-| 柔道SDK | 柔道SDKは、[iOS](https://github.com/judoapp/judo-ios/)および/または[Android](https://github.com/judoapp/judo-android)アプリに統合されなければならない。 |
+| 柔道アカウント | このパートナーシップを活用するには、[Judo](https://www.judo.app/) アカウントが必要です。 |
+| 柔道SDK | Judo SDK は、[iOS](https://github.com/judoapp/judo-ios/) アプリおよび/または[Android](https://github.com/judoapp/judo-android) アプリに統合する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
-**オンボーディングで**ある：Judoを使用するアプリパブリッシャーは、リッチでネイティブなオンボーディング体験を構築し、展開する。これらの体験は、Brazeを介して調整されたパーソナライズされたクロスチャネル・オンボーディング・ジャーニーの1つの要素となる。様々なアプリ内フローの有効性をテストするために、アプリを更新することなく、パーソナライズされたエクスペリエンスを素早く更新することができる。
+**オンボーディング**:Judo を使用するアプリパブリッシャーは、リッチでネイティブなオンボーディングエクスペリエンスを構築、デプロイします。これらのエクスペリエンスを、Braze により調整されるパーソナライズされたクロスチャネルオンボーディングの要素として利用できます。さまざまなアプリフローの有効性をテストするために、エクスペリエンスをパーソナライズし、アプリの更新を使用せずに迅速に更新できます。
 
-**コンバージョンだ**：アプリパブリッシャーは、Brazeのデータを使用して、パーソナライズされたリッチなアプリ内体験を作成し、Judoの統合フックを使用して、アプリ内購入、有料購読、またはコンテキスト・マーチャンダイジングを促進することができる。これらのエクスペリエンスへのアクセスは、Brazeで作成されたエンゲージメント・マーケティング・キャンペーンがトリガーとなる。
+**コンバージョン**:アプリパブリッシャーは Braze のデータを使用して、パーソナライズされたリッチなアプリ内エクスペリエンスを作成し、Judo の統合フックを使用して、アプリ内購入、有料サブスクリプション、またはコンテキストに基づくマーチャンダイジングを促進することができます。これらのエクスペリエンスへのアクセスは、Braze で作成されたエンゲージメントマーケティングキャンペーンによってトリガーできます。
 
-**イベント駆動型コンテンツ**：スポーツやエンターテインメントにおける柔道の主な用途は、イベントのプレビュー、プロモーション、総括のためのリッチな体験の構築である。この能力は、季節的なコンテンツやニュース主導のコンテンツなど、他の業種にも幅広く応用できる。イベントをタイムリーに宣伝したり強調したりするメッセージングをリッチなアプリ内体験にリンクさせることで、パブリッシャーは文脈に即したエンゲージメントを促進することができる。
+**イベント駆動型コンテンツ**：スポーツやエンターテインメント分野では、Judo は主として、イベントのプレビュー、プロモーション、要約のためのリッチなエクスペリエンスを構築する目的で使用されています。この機能は、他の業種でも季節的なコンテンツやニュースに基づくコンテンツに幅広く応用できます。イベントをタイムリーに宣伝またはハイライトするメッセージングをリッチなアプリ内エクスペリエンスにリンクできるため、パブリッシャーは状況に即して対応することで、エンゲージメントを促進できます。
 
-## サイド・バイ・サイドのSDK統合
+## サイドバイサイドの SDK 統合
 
 Judoは、モバイルアプリにJudoとBraze SDKを並べて統合するために必要な作業の一部を自動化する追加ライブラリを提供している。 
 
-### ステップ1:柔道整復師の統合ライブラリをインストールする
+### ステップ1:Judo Braze 統合ライブラリをインストールする
 
-アプリにJudo-Braze統合ライブラリをインストールしてセットアップする。これで自動的にイベント・トラッキングが有効になる。
+アプリにJudo-Braze統合ライブラリをインストールしてセットアップする。これにより、イベント追跡が自動的に有効になります。
 
 - [iOSのインストール
-指示](https://github.com/judoapp/judo-braze-ios/wiki#installation)
-- [アンドロイドのインストール
-instructions](https://github.com/judoapp/judo-braze-android/wiki#installation).
+手順](https://github.com/judoapp/judo-braze-ios/wiki#installation)
+- [Android のインストール
+手順](https://github.com/judoapp/judo-braze-android/wiki#installation)。
 
-### ステップ2:アプリ内メッセージを設定する
+### ステップ2:アプリ内メッセージングを設定する
 
-このステップでは、iOSとAndroid用のカスタム`ABKInAppMessageControllerDelegate` 、`IInAppMessageManagerListener` 。
+このステップでは、iOS および Android 用のカスタム `ABKInAppMessageControllerDelegate` および`IInAppMessageManagerListener` 実装を作成します。
 
 各統合ライブラリに同梱されているアプリ内メッセージ設定ドキュメントを参照のこと：
 
 - [iOSアプリ内メッセージ
 セットアップ](https://github.com/judoapp/judo-braze-ios/wiki#in-app-messaging-setup)
 - [Androidアプリ内メッセージ
-セットアップ](https://github.com/judoapp/judo-braze-android/wiki#in-app-messaging-setup).
+の設定](https://github.com/judoapp/judo-braze-android/wiki#in-app-messaging-setup)。.
 
 ## この統合を使う
 
-アプリ側の統合が完了したら、Judo Experience向けにテストBrazeアプリ内メッセージキャンペーンを実行してテストし、期待通りに実行されることを確認することができる。
+アプリ側の統合が完了したら、Judo エクスペリエンスの Braze アプリ内メッセージキャンペーンを実行してこの統合をテストし、期待どおりに実行されていることを確認できます。
 
 ### ステップ1:カスタムコードのアプリ内メッセージキャンペーンを作成する
 
-Brazeプラットフォームから、**カスタムコードの**メッセージタイプでBrazeアプリ内メッセージキャンペーンを作成する。次に、カスタムタイプとして**HTMLアップロードを**選択する。このコンテンツはユーザーには表示されない。
+Brazeプラットフォームから、**カスタムコードの**メッセージタイプでBrazeアプリ内メッセージキャンペーンを作成する。次に、カスタムタイプとして \[**HTML Upload**] を選択します。メッセージのコンテンツに、ベースのアプリ内メッセージングのフィールドが取り込まれていることを確認してください。このコンテンツはユーザーには表示されません。
 
 ![カスタムコード」メッセージタイプを選択したときのダッシュボードのイメージ。][2]
 
@@ -74,13 +74,13 @@ JudoがこれをJudoエクスペリエンスに書き換えて置き換えるの
 ![キャンペーンの作成ステップに追加されたフォーム検証コードを示す画像。][3]
 
 ### ステップ2:柔道のキーと値のペアを設定する
-![この画像は、この統合に必要な1つのキーと値のペアを示している。「キー」は「柔道経験」で、「値」はあなたの柔道リンクである。][4]{: style="float:right;max-width:50%;margin-left:15px;"}
+![この統合に必要な１つのキー値ペアを示す。「キー」は「judo-experience」、「値」は Judo リンクである。][4]{: style="float:right;max-width:50%;margin-left:15px;"}
 
-キャンペーンに[カスタムキーバリューペアを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/key_value_pairs/)設定する。キーは`judo-experience` 。ここに表示したい柔道体験のURLを記入する。Judo-Braze統合ライブラリーは、ハンドラーでこのキーと値のペアを検出し、標準のBrazeアプリ内メッセージUIの代わりにJudo Experienceを注入するために使用する。
+キャンペーンに[カスタムキーバリューペアを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/key_value_pairs/)設定する。キーは`judo-experience` 。ここに表示したい柔道体験のURLを記入する。その後、Judo-Braze 統合ライブラリはハンドラーでこのキー値ペアを検出し、このペアを使用して Judo エクスペリエンスを標準 Braze アプリ内メッセージ UI の代わりに挿入します。
 <br><br>
 ### ステップ3:キャンペーンを終える
 
-最後に、キャンペーンのトリガーを設定し、**配信と** **ターゲットユーザーの**セクションでセグメントを介してユーザーを選択し、キャンペーンを完了する。Brazeアプリ内メッセージのさまざまな構成要素については、アプリ内メッセージの[記事を]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/create/)参照。
+最後に、キャンペーンを完了し、キャンペーンのトリガーを設定し、\[**配信**] セクションと \[**ターゲットユーザー**] セクションで Segments からユーザーを選択します。Brazeアプリ内メッセージのさまざまな構成要素については、アプリ内メッセージの[記事を]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/create/)参照。
 
 
 [2]: {% image_buster /assets/img/judo/braze-campaign-select-custom-type.png %}
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/komo.md b/_lang/ja/_partners/message_personalization/dynamic_content/komo.md
index 0d3867ee7f9..38999874d61 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/komo.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/komo.md
@@ -10,37 +10,37 @@ search_tag: Partner
 
 # Komo
 
-> Komo][7]は、ゲーミフィケーション、インタラクティブコンテンツ、コンペティション、賞品、ロイヤルティを専門とするカスタマーエンゲージメントプラットフォームです。
+> \[Komo][7] は、ゲーミフィケーション、インタラクティブコンテンツ、試合、賞品、ロイヤルティに特化したカスタマーエンゲージメントプラットフォームです。
 
-BrazeとKomoの統合により、Komoエンゲージメントハブを通じてファーストパーティおよびゼロパーティデータを収集できます。これらのハブは、インタラクティブなコンテンツとゲーミフィケーション機能を提供するダイナミックなマイクロサイトです。これらのハブから収集されたユーザーデータは、Braze APIに送信されます。
+Braze と Komo の統合により、Komo Engagment Hub を通じてファーストパーティデータとゼロパーティデータを収集できます。これらのハブは、インタラクティブなコンテンツとゲーミフィケーション機能を提供するダイナミックなマイクロサイトです。これらのハブから収集されたユーザーデータは、Braze APIに送信されます。
 
 - KomoからBrazeにリアルタイムで収集されたファーストパーティおよびゼロパーティのユーザーデータを取り込む
 - アンケート、投票、クイズの質問に回答する際に、市場調査およびユーザーの好みのデータを取り込みます。
-- ユーザーが引き続き関与し、自分自身に関するデータをさらに共有するにつれて、Brazeでユーザープロファイルを段階的に構築します。
+- ユーザーが引き続きエンゲージし、ユーザー自身に関するデータをさらに共有するにつれて、Braze でユーザープロファイルを徐々に作成します。
 - Brazeを通じて送信されるトランザクションメールの外観と感触を標準化する
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| コモアカウント | このパートナーシップを利用するには、アクティブなKomoアカウントが必要です。\[Komo][7] を訪れて、今すぐトライアルを開始してください。 |
+| Komo アカウント | このパートナーシップを利用するには、アクティブなKomoアカウントが必要です。\[Komo][7] を訪れて、今すぐトライアルを開始してください。 |
 | Braze REST API キー | `users.track`の権限を持つBraze REST APIキー。<br><br> これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。 |
-| Braze REST エンドポイント | [あなたのRESTエンドポイントURL][1]お使いのエンドポイントは、インスタンスのBraze URLに依存します。<br><br>例えば、それは次のように見えるはずです：https://rest.iad-03.braze.com |
+| Braze REST エンドポイント | [REST エンドポイント URL][1]。お使いのエンドポイントは、インスタンスのBraze URLに依存します。<br><br>たとえば、https://rest.iad-03.braze.com のようになります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## ユースケース
 
 {% tabs ローカル %}
-{% tab データキャプチャ（フォーム送信） %}
+{% tab データキャプチャ (フォーム送信) %}
 
-ユーザーがKomoでカスタマイズ可能なデータキャプチャフォームを送信すると、Braze統合でマッピングされたKomoフィールドは`/users/track/` APIコールを介してBrazeに渡されます。
+ユーザーが Komo でカスタマイズ可能なデータキャプチャフォームを送信すると、Braze 統合でマッピングされている Komo のフィールドが、`/users/track/` API 呼び出しを介して Braze に渡されます。
 
-データキャプチャフォームは、カードの開始時または終了時に存在します。
+データキャプチャフォームは、カードの開始時または終了時のいずれかに存在します。
 
 {% endtab %}
 {% tab 市場調査（近日公開） %}
 
-近日中に、Komoはユーザーがクイズの質問、投票、性格診断、スワイパーなどに回答したときに収集された市場調査データを通過させる機能を追加します。このデータにより、フォーム送信で取得したデータを超えて、ユーザーのプロファイルを強化することができます。
+Komo は近々、ユーザーがクイズの質問、投票、性格診断、スワイパーなどに回答したときにキャプチャされる市場調査データをパススルーする機能を追加する予定です。このデータにより、フォーム送信でキャプチャしたデータを超えて、ユーザーのプロファイルを強化することができます。
 
 {% endtab %}
 {% endtabs %}
@@ -49,7 +49,7 @@ BrazeとKomoの統合により、Komoエンゲージメントハブを通じて
 
 ### ステップ1:Komoエンゲージメントハブとカードを公開する
 
-Komoエンゲージメントハブを公開するには、データキャプチャフォームを含む少なくとも1枚のカードが必要です。公開されると、ユーザーエクスペリエンスをエンドツーエンドでテストし、統合が正しく機能していることを確認できます。
+データキャプチャフォームを含む1つ以上のカードでKomo Engagement Hub を公開する必要があります。公開されると、ユーザーエクスペリエンスをエンドツーエンドでテストし、統合が正しく機能していることを確認できます。
 
 ![][2]
 
@@ -63,7 +63,7 @@ Komoでは、**ハブ設定**タブに移動し、**統合**セクションを
 
 #### ユーザーのマッピングを構成する
 
-最初に設定する必要があるのは、KomoでキャプチャされたユーザーをBraze内のユーザーにどのようにマッピングするかです。Komo内のフィールドで`braze_id`または`external_id`をキャプチャしている場合は、適切なキーを選択できます。それ以外の場合は、最も一般的なオプションを選択します。これは、メールまたは電話のユーザーエイリアスになります。
+最初に設定する必要があるのは、Komo でキャプチャされたユーザーを Braze 内のユーザーにどのようにマッピングするかです。Komo 内のフィールドで `braze_id` または `external_id` をキャプチャする場合は、適切なキーを選択できます。それ以外の場合は、最も一般的なオプションを選択します。これは、メールまたは電話のユーザーエイリアスになります。
 
 ![][5]{: style="max-width:65%;"}
 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/liftigniter.md b/_lang/ja/_partners/message_personalization/dynamic_content/liftigniter.md
index d9e193c9566..68bd32d8abe 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/liftigniter.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/liftigniter.md
@@ -1,8 +1,8 @@
 ---
-nav_title: リフトアイグナイタ
-article_title: リフトアイグナイタ
+nav_title: LiftIgniter
+article_title: LiftIgniter
 alias: /partners/liftigniter/
-description: "この参考文献では、企業がカスタマーエクスペリエンスを変革するのに役立つ、主要なパーソナライゼーション プラットフォームであるBrazeとリフトイグナイタの提携について概説する。"
+description: "このリファレンス記事では、Braze と LiftIgniter のパートナーシップについて説明します。LiftIgniter は、業界をリードするパーソナライゼーションプラットフォームであり、企業によるカスタマーエクスペリエンスの変革を支援しています。"
 page_type: partner
 search_tag: Partner
 
@@ -10,7 +10,7 @@ search_tag: Partner
 
 # Liftigniter
 
-> リフトイグナイタは主要なパーソナライゼーション プラットフォームであり、企業があらゆるタッチポイントにわたるリアルタイムのパーソナライゼーションを通じてカスタマーエクスペリエンスを変革するのに役立っています。
+> LiftIgniter は、業界をリードするパーソナライゼーションプラットフォームです。企業があらゆるタッチポイントでリアルタイムのパーソナライゼーションを行えるようにすることで、カスタマーエクスペリエンスの変革を支援しています。
 
 LiftIgniterとBrazeインテグレーションは、Connected Contentを活用して、新聞記事、衣料品、他の小売 (店)アイテムや動画など、面白い話題をお勧めすることができます。
 
@@ -18,28 +18,28 @@ LiftIgniterとBrazeインテグレーションは、Connected Contentを活用
 
 | 要件| 説明|
 | ---| ---|
-| LiftIgniterアカウント | この提携の前倒しタグを行うには、[LiftIgniterアカウント](https://console.liftigniter.com/login)が必要です。 |
-| LiftIgniter APIの統合 | ここから推奨を引き出すには、[LiftIgniter をサイトまたはアプリに統合する必要があります。 |
+| LiftIgniterアカウント | このパートナーシップを活用するには、[LiftIgniter アカウント](https://console.liftigniter.com/login)が必要です。 |
+| LiftIgniter APIの統合 | ここからレコメンデーションを取得できるようにするには、LiftIgniter をサイトまたはアプリに[統合](https://support.liftigniter.com/support/solutions/articles/30000024667-api-integration-overview)する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 統合
 
-[LiftIgniterのREST API](https://documenter.getpostman.com/view/2166502/liftigniter/7TFGvSV#9bdf75da-edd6-45ec-9c28-a0edefad1389)を使用して、パーソナライズされた内容をメッセージに挿入します。LiftIgniterアカウントとLiftIgniterがアプリに統合されたら、次のテンプレートをメッセージ作成画面に追加して、必要に応じて情報を置き換えてメッセージにコンテンツを呼び出します(`x-api-key`、`theapikey`など)。
+[LiftIgniterのREST API](https://documenter.getpostman.com/view/2166502/liftigniter/7TFGvSV#9bdf75da-edd6-45ec-9c28-a0edefad1389)を使用して、パーソナライズされた内容をメッセージに挿入します。LiftIgniter アカウントと LiftIgniter がアプリに統合されたら、次のテンプレートをメッセージ作成画面に追加して、必要に応じて情報を置き換えて (`x-api-key`、`theapikey` など)、メッセージにコンテンツを呼び出します。
 
 {% raw %}
 ```
 {% connected_content https://query.petametrics.com/v3/lkdk9usg5av95fvs/userId/model :method post :headers {"x-api-key": "theapikey"} :body "UseActivity"=false :content_type application/json :save json %}
 ```
 
-次に、メッセージを記述し、JSON で呼び出すコンテンツを定義します。たとえば、`{{json.items[0].title}}` です。
+次に、メッセージを記述し、JSON で呼び出すコンテンツを定義します。たとえば `{{json.items[0].title}}` です。
 
 {% endraw %}
 
-![LiftIgniter固有の接続内容コールを含むプッシュキャンペーンを示す"画像。"画像 フィールドには、接続内容ロジックも追加されています。][1]
+![LiftIgniter 固有のコネクテッドコンテンツ呼び出しを含むプッシュキャンペーン。画像フィールドにはコネクテッドコンテンツロジックも追加されている。][1]
 
-このメッセージを作曲者本文に入力すると、メッセージをプレビューできます。以下に示すように、"画像s をプルインすることもできます。
+このメッセージを作成画面の本文に入力すると、メッセージをプレビューできます。以下に示すように、画像を取得することもできます。
 
-![送信後に表示されるメッセージのプレビュー "画像。][2]
+![送信後に表示されるメッセージのプレビュー画像。][2]
 
 [1]: {% image_buster /assets/img/liftigniter.png %}
 [2]: {% image_buster /assets/img/liftigniter2.png %}
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink.md b/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink.md
index 46afd078738..11ae186d4d3 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink.md
@@ -2,7 +2,7 @@
 title: "Movable Ink"
 article_title: Movable Ink
 alias: "/partners/movable_ink/"
-description: "このリファレンス記事は、BrazeとMovable Inkのパートナーシップについて概説しています。これは、デジタルマーケティング担当者に顧客を動かす魅力的でユニークなビジュアル体験を作成する方法を提供するクラウドベースのソフトウェアプラットフォームです。"
+description: "このリファレンス記事では、Braze と Movable Ink のパートナーシップについて説明します。Movable Ink は、顧客に印象づける説得力のある独特なビジュアルエクスペリエンスを作成できるデジタルマーケターに提供するクラウドベースのソフトウェアプラットフォームです。"
 page_type: partner
 search_tag: Partner
 
@@ -10,121 +10,122 @@ search_tag: Partner
 
 # Movable Ink
 
-> [Movable Ink](https://www.movableink.com/) は、デジタルマーケティング担当者に顧客を動かす魅力的でユニークなビジュアル体験を作成する方法を提供するクラウドベースのソフトウェアプラットフォームです。Movable Inkプラットフォームは、キャンペーンに簡単に挿入できる貴重なカスタマイズオプションを提供します。 
+> [Movable Ink](https://www.movableink.com/) は、顧客に印象づける説得力のある独特なビジュアルエクスペリエンスを作成できる手段をデジタルマーケターに提供するクラウドベースのソフトウェアプラットフォームです。Movable Ink プラットフォームは、キャンペーンに簡単に挿入できる有用なカスタマイズオプションを提供します。 
 
-Movable Ink のインテリジェントクリエイティブ機能（投票、カウントダウンタイマー、スクラッチオフなど）を活用して、私たちのクリエイティブ能力を拡大します。Movable InkとBrazeの統合により、ダイナミックなデータドリブン型のメッセージに対するより包括的なアプローチが可能になり、ユーザーにとって重要な事柄に関するリアルタイムの要素が提供されます。
+ポーリング、カウントダウンタイマー、スクラッチオフなど、Movable Ink の Intelligent Creative 機能を利用して Braze のクリエイティブ機能を拡大します。Movable Ink と Braze の統合により、動的なデータドリブン型メッセージへのよりバランスの取れたアプローチを可能にし、重要な事柄に関するリアルタイムの要素をユーザーに提供します。
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| Movable Inkアカウント | このパートナーシップを利用するには、Movable Inkアカウントが必要です。 |
-| データソース | データソースをMovable Inkに接続する必要があります。これは、CSV、Web サイトのインポート、またはAPIを通じて行うことができます。BrazeとMovable Inkの間でデータを統一する識別子（例えば、`external_id`）を渡すようにしてください。
+| Movable Ink アカウント | このパートナーシップを活用するには、Movable Ink アカウントが必要です。 |
+| データソース | データソースを Movable Ink に接続する必要があります。これは、CSV、Web サイトインポート、または API を使用して実行できます。Braze と Movable Ink の間で統一 ID (`external_id` など) を使用してデータを渡していることを確認します。
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
-- パーソナライズされた月次または年末のまとめ。
-- 最後に知られている行動に基づいて、メール、プッシュ、またはリッチ通知の画像を動的にパーソナライズします。<br>
-	例えば： 
-	- APIからデータを取得してイベントのスケジュールを動的に作成するためにリッチプッシュメッセージを使用します。 
-	- カウントダウンタイマー機能を使用して、大規模なセールが近づいていることをユーザーに通知します（例えば、ブラックフライデー、バレンタインデー、ホリデーセールなど）。
-	- プロモコードを配布する楽しくインタラクティブな方法としてスクラッチオフ機能を使用してください。
 
-## サポートされているMovable Ink機能
+- パーソナライズされた月ごとの要約または年末の要約。
+- 直近の既知の動作に基づいて、メール、プッシュ、またはリッチプッシュ通知に使用される画像をダイナミックにパーソナライズします。<br>
+	以下に例を示します。 
+	- リッチプッシュメッセージを使用して、API からデータを取得してイベントのスケジュールを動的に作成します。 
+	- 大規模なセール (ブラックフライデー、バレンタインデー、祝日セールなど) が近づいているときに、カウントダウンタイマーを使用してユーザーに通知します。
+	- プロモーションコードを配信する楽しくインタラクティブな方法として、Scratch Off 機能を使用します。
 
-インテリジェントクリエイティブには、Brazeユーザーが活用できる多くの提供があります。次のリストは、サポートされている機能を示しています。 
+## サポートされている Movable Ink の機能
 
-| Movable Ink機能 | 特徴 | リッチプッシュ通知 | アプリ内メッセージング / コンテンツカード / メール | 詳細 |
+Intelligent Creative には、Braze のユーザーが利用できる多くのサービスがあります。次のリストに、サポートされている機能を示します。 
+
+| Movable Ink の機能 | 機能 | リッチプッシュ通知 | アプリ内メッセージ/コンテンツカード/メール | 詳細 |
 | ---------------------- |---| ---------------------- | -------------------------------- | ------- |
-| クリエイティブオプティマイザー | A/Bコンテンツを表示 | ✗ | ✔ | |
-|| 最適化する | ✗ | ✔* | \* Branchのディープリンクソリューションを使用する必要があります |
-| ターゲティングルール | 日付 | ✔* | ✔ | サポートされていますが、推奨されません。プッシュ通知は受信時にキャッシュされ、更新されません。 |
-|| 曜日 | ✔* | ✔ | サポートされていますが、推奨されません。プッシュ通知は受信時にキャッシュされ、更新されません。 |
-|| 時刻 | ✔* | ✔ | サポートされていますが、推奨されません。プッシュ通知は受信時にキャッシュされ、更新されません。 |
-| ストーリー/行動活動 | | ✔* | ✔* | \* Braze に使用される一意のユーザー識別子は、メールサービスプロバイダー (ESP) の識別子にリンクされている必要があります |
-| アプリ内のディープリンク | | ✔* | ✔* | \* お客様にスムーズな体験を提供するために、確立されたディープリンクソリューションをBranch経由で使用するか、Movable Inkのクライアントエクスペリエンスチームによる検証済みのソリューションを使用してください。 |
-| アプリ | カウントダウンタイマー | ✔* | ✔ | サポートされていますが、推奨されません。プッシュ通知は受信時にキャッシュされ、更新されません。 |
-|| 世論調査 | ✗ | ✔* | \* 投票後、アプリをモバイルランディングページにします |
-|| スクラッチオフ | ✔* | ✔* | クリックすると、スクラッチオフ体験のためにアプリを離れます |
-|| 動画 | ✔* | ✔* | アニメーションGIFのみ,<br>Androidの場合、Brazeは実装において[GIFサポート][GIFサポート]を必要とします。 |
+| クリエイティブ・オプティマイザー | A/B コンテンツの表示 | ✗ | ✔ | |
+|| 最適化 | ✗ | ✔* | \* Branch のディープリンクソリューションを使用する必要がある |
+| ターゲティングルール | 日付 | ✔* | ✔ | \* プッシュ通知は受信時にキャッシュされ、更新されないため、サポートされますが推奨されません |
+|| 曜日 | ✔* | ✔ | \* プッシュ通知は受信時にキャッシュされ、更新されないため、サポートされますが推奨されません |
+|| 時刻 | ✔* | ✔ | \* プッシュ通知は受信時にキャッシュされ、更新されないため、サポートされますが推奨されません |
+| ストーリー/行動アクティビティ | | ✔* | ✔* | \* Brazeに使用される一意のユーザー識別子を、メールサービスプロバイダー (ESP) にリンクする必要がある |
+| アプリ内のディープリンク | | ✔* | ✔* | \* 顧客に効率化されたエクスペリエンスを提供するには、Branch で確立されたディープリンクソリューションを使用するか、Movable Ink のクライアントエクスペリエンスチェンジチームによる検証済みソリューションを使用します。 |
+| アプリ | カウントダウンタイマ | ✔* | ✔ | \* プッシュ通知は受信時にキャッシュされ、更新されないため、サポートされますが推奨されません |
+|| ポーリング | ✗ | ✔* | \* 投票後、アプリを移動式ランディングページに残す |
+|| スクラッチオフ | ✔* | ✔* | \* クリックすると、スクラッチオフエクスペリエンスのためにアプリが終了する |
+|| 動画 | ✔* | ✔* | \* アニメーションGIF のみ。<br>Android の場合、Braze は実装で \[GIF サポート]\[GIF サポート]を必要とする |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 統合
 
-### ステップ1:Movable Inkのデータソースを作成する
+### ステップ1:Movable Inkのデータソースの作成
 
-顧客は、CSV、Web サイトインポート、またはAPI統合のいずれかであるデータソースを作成する必要があります。
+顧客は、CSV、Web サイトのインポート、または API統合のいずれかのデータソースを作成する必要があります。
 
-![表示されるさまざまなデータソースオプション:CSV アップロード、Web サイト、または API 統合。]({% image_buster /assets/img/movable_ink/movable_ink1.png %})
+![表示されるさまざまなデータソースオプション:CSV アップロード、Web サイト、またはAPI 統合。]({% image_buster /assets/img/movable_ink/movable_ink1.png %})
 
-{% tabs ローカル %}
+{% tabs local %}
 {% tab CSVデータソース %}
-- **CSVデータソース**:各行には少なくとも1つのSegment列と1つのコンテンツ列が必要です。CSVファイルがアップロードされたら、どの列をコンテンツのターゲットに使用するかを選択します。 [例のCSVファイル]({% image_buster /assets/download_file/movable_ink_CSV.csv %})
+- **CSV データソース**:各行には、少なくとも1つのSegment列と1つの内容列が必要です。CSV がアップロードされたら、コンテンツのターゲットを設定するために使用する列を選択します。\[例: CSV ファイル]({% image_buster /assets/download_file/movable_ink_CSV.csv %})
 
-![「CSV」をデータソースとして選択する際に表示されるフィールド。]({% image_buster /assets/img/movable_ink/movable_ink2.png %})
+![「CSV」をデータソースとして選択すると表示されるフィールド。]({% image_buster /assets/img/movable_ink/movable_ink2.png %})
 {% endtab %}
-{% tab Web サイト データソース %}
-- **Web サイト データソース**:各行には少なくとも1つのSegment列と1つのコンテンツ列が必要です。CSVをアップロードした後、どの列をコンテンツのターゲットに使用するかを選択します。
-  - このプロセスの中で、次のことをマッピングする必要があります:
-    - どのフィールドがセグメントとして使用されますか
-    - クリエイティブ内で動的にパーソナライズされたデータフィールドとして使用したいフィールドはどれですか（例：ユーザー属性や名、姓、市区町村など）。
+{% tab Web サイトデータソース %}
+- **Web サイトデータソース**:各行には、少なくとも1つのSegment列と1つの内容列が必要です。CSV がアップロードされたら、コンテンツのターゲットを設定するために使用する列を選択します。
+  - このプロセスでは、以下をマップする必要があります。
+    - セグメントとして使用されるフィールドs
+    - クリエイティブでダイナミックにパーソナライズできるデータフィールドとして使用するフィールド (例:ユーザー属性、姓、名、市区町村などのカスタム属性)。
 
-![「データソース」として「Web サイト」を選択したときに表示されるフィールド。]({% image_buster /assets/img/movable_ink/movable_ink3.png %})
+![「Website」をデータソースとして選択すると表示されるフィールド。]({% image_buster /assets/img/movable_ink/movable_ink3.png %})
 {% endtab %}
-{% tab API統合 %}
-- **API統合**:会社のAPIを使用して、API応答から直接コンテンツを提供します。
+{% tab API 統合 %}
+- **API 統合**:自社の API を使用して、API レスポンスから直接ココンテンツを供給します。
 
-![データソースとして「API統合」を選択したときに表示されるフィールド]({% image_buster /assets/img/movable_ink/movable_ink4.png %})
+![「API Integration」をデータソースとして選択すると表示されるフィールド。]({% image_buster /assets/img/movable_ink/movable_ink4.png %})
 {% endtab %}
 {% endtabs %}
 
-### ステップ2:Movable Inkプラットフォームでキャンペーンを作成する
+### ステップ2:Movable Ink プラットフォームでのキャンペーンの作成
 
-Movable Inkのホーム画面から、キャンペーンを作成します。HTML、画像からのメール、またはプッシュ、アプリ内メッセージ、コンテンツカード（推奨）を含む任意のチャネルで使用できるブロックから選択できます。
-また、ブロックを通じて利用できるさまざまなコンテンツオプションを確認することをお勧めします。
+Movable Inkのホームスクリーンから、キャンペーンを作成します。HTML からのメールの開始、画像からのメールの開始、または任意のチャネルで使用できるブロックの作成 (プッシュ、アプリ内メッセージ、コンテンツカード(推奨) など) のいずれかを選択できます。
+また、ブロックを通じて利用できるさまざまなコンテンツオプションを確認することもお勧めします。
 
-![新しいMovable Inkキャンペーンを作成する際のMovable Inkプラットフォームの{画像}です。]({% image_buster /assets/img/movable_ink/movable_ink5.png %}){: style="max-width:70%"}
+![新しい Movable Ink キャンペーンを作成するときの Movable Ink プラットフォーム。]({% image_buster /assets/img/movable_ink/movable_ink5.png %}){: style="max-width:70%"}
 
-Movable Inkには、テキスト、画像などの要素をドラッグ＆ドロップできる簡単なエディターがあります。データソースを入力した場合、データプロパティを使用して動的に画像を生成できます。さらに、キャンペーンが送信され、ユーザーがパーソナライゼーションの基準に合わない場合、このフロー内でユーザーのためにフォールバックを作成することもできます。
+Movable Inkには、テキストや画像などの要素をドラッグアンドドロップできる簡単なエディターがあります。データソースを入力した場合は、データプロパティを使用して画像をダイナミックに生成できます。また、このフロー内に、ユーザーs のフォールバックs を作成することもできます。これは、キャンペーンが送信され、ユーザーがパーソナライゼーション基準内に収まらない場合です。
 
-![Movable Inkブロックエディタは、さまざまなカスタマイズ可能な要素を表示します。]({% image_buster /assets/img/movable_ink/create_campaign2.png %})
+![さまざまなカスタマイズ可能な要素を表示するMovable Ink ブロックエディタ。]({% image_buster /assets/img/movable_ink/create_campaign2.png %})
 
-キャンペーンを終了する前に、ダイナミックな画像をプレビューし、クエリパラメータをテストして、画像が表示されるときの見た目を確認してください。完了すると、ダイナミックなURLが生成され、それをBrazeに挿入できます！
+キャンペーンを終了する前に、ダイナミックな画像をプレビューし、クエリパラメーターを試してビューで画像がどのように表示されるかを確認してください。完了すると、ダイナミックな URLが生成され、Brazeに挿入できるようになります。
 
-Movable Inkプラットフォームの使用方法の詳細については、[Movable Inkサポートセンター][サポート]を参照してください。
+Movable Ink プラットフォームの使用方法の詳細については、\[Movable Ink サポートセンター]\[サポートを参照してください。]
 
-### ステップ 3:Movable Ink コンテンツ URL を取得
+### ステップ 3:Movable Ink コンテンツ URL を取得する
 
-BrazeメッセージにMovable Inkコンテンツを含めるには、Movable Inkが提供したソースURLを見つける必要があります。 
+Movable Ink のコンテンツを Braze メッセージに含めるには、Movable Ink から提供されたソース URL を確認する必要があります。 
 
-ソースURLを取得するには、Movable Inkダッシュボードでコンテンツを設定し、そこからコンテンツを完成させてエクスポートする必要があります。「完了」ページで、クリエイティブタグからソースURL（`img src`）をコピーします。
+ソース URL を取得するには、Movable Ink ダッシュボードでコンテンツを設定し、完了してコンテンツをエクスポートする必要があります。**Finish**ページで、ソースURL(`img src`)をクリエイティブタグからコピーします。
 
-![Movable Inkキャンペーンを完了した後に表示されるページで、ここにコンテンツURLが表示されます。]({% image_buster /assets/img/movable_ink/obtain_url.png %}){: style="max-width:80%;"}
+![Movable Ink キャンペーンが完成した後に表示されるページにコンテンツ URLが表示される。]({% image_buster /assets/img/movable_ink/obtain_url.png %}){: style="max-width:80%;"}
 
-次に、Brazeプラットフォームで、適切なフィールドにURLを貼り付けます。ステップ4に、メッセージングチャネルに適したフィールドが見つかります。最後に、マージタグ（{% raw %}```&mi_u=%%email%%```{% endraw %}など）を対応するLiquid変数（{% raw %}```&mi_u={{${email_address}}}```{% endraw %}など）に置き換えます。
+次に Braze プラットフォームで、URL を該当するフィールドに貼り付けます。メッセージングチャネルに適したフィールドは、4ステップに記載されています。最後に、マージタグ ({% raw %}```&mi_u=%%email%%```{% endraw %} など) を対応するLiquid 変数 ({% raw %}```&mi_u={{${email_address}}}```{% endraw %} など) に置き換えます。
 
-### ステップ4:Brazeエクスペリエンス
+### ステップ4:Braze体験
 
-{% tabs ローカル %}
+{% tabs local %}
 {% tab メール %}
-Brazeプラットフォームで、クリエイティブタグをメール本文に貼り付けます。![]({% image_buster /assets/img/movable_ink/web2.png %}){: style="max-width:90%"}<br><br>
+Braze プラットフォームで、クリエイティブなタグをメール本文に貼り付けます。![]({% image_buster /assets/img/movable_ink/web2.png %}){: style="max-width:90%"}<br><br>
 
 {% endtab %}
 {% tab プッシュ通知 %}
 
-1. Brazeプラットフォーム内で:
-	- Androidプッシュ:**プッシュアイコン画像**と**拡張通知画像**フィールドにURLを貼り付けます。<br>![]({% image_buster /assets/img/movable_ink/android.png %}){: style="max-width:60%"}<br><br>
-	- iOSプッシュ:**メディア**リンクフィールドにURLを貼り付け、使用しているファイル形式を示します。<br>![]({% image_buster /assets/img/movable_ink/ios.png %}){: style="max-width:60%"}<br><br>
-	- Web プッシュ:URLを**プッシュアイコン画像**および**大きな通知画像**フィールドに貼り付けます。<br>![]({% image_buster /assets/img/movable_ink/web.png %}){: style="max-width:60%"}<br><br>
-2. 画像がキャッシュされないようにするには、メッセージ内のURLの前に空のLiquidタグを付けます:<br>{% raw %}```{% if true %}{% endif %}https://movable-ink-image-url-goes-here```{% endraw %}
+1. Braze プラットフォームの場合:
+	- Android プッシュ:**プッシュアイコン画像**と**拡張通知画像**フィールドにURLを貼り付けます。<br>![]({% image_buster /assets/img/movable_ink/android.png %}){: style="max-width:60%"}<br><br>
+	- iOS プッシュ**Media**リンクフィールドにURLを貼り付け、使用しているファイル形式を示します。<br>![]({% image_buster /assets/img/movable_ink/ios.png %}){: style="max-width:60%"}<br><br>
+	- Web プッシュURL を \[**プッシュ通知アイコンの画像**] と \[**大きな通知画像**] フィールドに貼り付けます。<br>![]({% image_buster /assets/img/movable_ink/web.png %}){: style="max-width:60%"}<br><br>
+2. 画像がキャッシュされないようにするため、メッセージの URL の先頭に空の Liquid タグを追加します。<br>{% raw %}```{% if true %}{% endif %}https://movable-ink-image-url-goes-here```{% endraw %}
 
 {% endtab %}
-{% tab アプリ内メッセージ %}
+{% tab アプリ中電文 %}
 
-1. Brazeプラットフォームで、URLを**リッチプッシュ通知メディア**フィールドに貼り付けます。![]({% image_buster /assets/img/movable_ink/image.png %}){: style="max-width:60%"}<br><br>
-2. キャッシュを防ぐためにユニークなURLを提供してください。Movable Ink のリアルタイム画像が機能し、キャッシュの影響を受けないことを確認するには、Liquid を使用して Movable Ink 画像 URL の末尾にタイムスタンプを追加します。
+1. Braze プラットフォームで \[**リッチプッシュ通知メディア**] フィールドに URL を貼り付けます。![]({% image_buster /assets/img/movable_ink/image.png %}){: style="max-width:60%"}<br><br>
+2. キャッシュの防止に役立つ一意のURL を指定します。Movable Ink のリアルタイム画像が機能し、キャッシュの影響を受けないようにするため、Liquid を使用して、Movable Ink 画像 URL の末尾にタイムスタンプを付加します。
 
-これを行うには、必要に応じて画像URLを置き換えて、次の構文を使用します:
+これを行うには、次の構文を使用します。必要に応じて画像 URL を置き換えます。
 {% raw %}
 ```
 {% assign timestamp = "now" | date: "%s" %}
@@ -132,19 +133,19 @@ Brazeプラットフォームで、クリエイティブタグをメール本文
 {{img}}
 ```
 {% endraw %}
-このテンプレートは現在の時間（秒単位）を取得し、それをMovable Ink画像タブの末尾に（クエリパラメータとして）追加して、最終結果を出力します。**テスト** タブでプレビューできます - これによりコードが評価され、プレビューが表示されます。
+このテンプレートは、現在の時刻 (秒単位) を取得し、それを Movable Ink 画像タブの終わりに (クエリパラメーターとして) 付加し、最終結果を出力します。**Test**タブでプレビューできます。これにより、コードが評価され、プレビューが表示されます。
 
-**3\.**最後に、Segmentのメンバーシップを再評価します。これを行うには、`Re-evaluate audience membership and liquid at send-time`オプションを**ターゲットオーディエンス**ステップのキャンペーンで有効にします。このオプションが利用できない場合は、顧客成功マネージャーまたはBrazeサポートに連絡してください。このオプションは、アプリ内メッセージがトリガーされるたびに一意のURLを提供するキャンペーンを再リクエストするようにBraze SDKに指示します。
+**3\.**最後に、セグメントのメンバーシップを再評価します。これを行うには、キャンペーンの**Target Audiences**ステップにある`Re-evaluate audience membership and liquid at send-time`を有効にします。この項目を選択できない場合は、顧客のサクセスマネージャーまたはBrazeサポートに連絡してください。このオプションは、アプリ内メッセージがトリガーされるたびに、一意の URL を指定してキャンペーンを再要求するように Braze SDK に指示します。
 
 {% endtab %}
-{% tab コンテンツカード %}
+{% tab Content Card %}
 
-1. Brazeプラットフォームで、URLを**リッチプッシュ通知メディア**フィールドに貼り付けます。![]({% image_buster /assets/img/movable_ink/image.png %}){: style="max-width:60%"}<br><br>
-2. モバイルの場合:iOSおよびAndroidのコンテンツカード画像は受信時にキャッシュされ、更新されません。 
-  - 回避策として、キャンペーンを毎日、毎週、または毎月の定期的なメッセージとしてスケジュールし、対応する有効期限を設定してコンテンツカードを再テンプレート化します。例えば、コンテンツカードは1日に1回更新する必要がある場合、1日の有効期限で毎日スケジュールされた送信として設定する必要があります。
-3. Movable Ink のリアルタイム画像が機能し、コンテンツカードが再テンプレート化されたときにキャッシュの影響を受けないようにするために、Liquid を使用して Movable Ink 画像 URL の末尾にタイムスタンプを追加します。
+1. Braze プラットフォームで \[**リッチプッシュ通知メディア**] フィールドに URL を貼り付けます。![]({% image_buster /assets/img/movable_ink/image.png %}){: style="max-width:60%"}<br><br>
+2. モバイル:iOS および Android のコンテンツカードの画像は、受信時にキャッシュされ、更新されません。 
+  - 回避策として、キャンペーンを毎日、毎週、または毎月の定期的なメッセージとしてスケジュールし、対応する有効期限を設定します。これにより、コンテンツカードが再テンプレート化されます。たとえば、1日に1回更新する必要があるコンテンツカードは、有効期間が1日に設定された毎日のスケジュール送信として設定する必要があります。
+3. コンテンツカードが再テンプレート化されたときに、Movable Ink のリアルタイム画像が機能し、キャッシュの影響を受けないようにするため、Liquid を使用して、Movable Ink 画像 URL の末尾にタイムスタンプを付加します。
 
-これを行うには、必要に応じて画像URLを置き換えて、次の構文を使用します:
+これを行うには、次の構文を使用します。必要に応じて画像 URL を置き換えます。
 {% raw %}
 ```
 {% assign timestamp = "now" | date: "%s" %}
@@ -152,26 +153,26 @@ Brazeプラットフォームで、クリエイティブタグをメール本文
 {{img}}
 ```
 {% endraw %}
-このテンプレートは現在の時間（秒単位）を取得し、それをMovable Ink画像タブの末尾に（クエリパラメータとして）追加して、最終結果を出力します。**テスト** タブでプレビューでき、コードを評価してプレビューを表示します。
+このテンプレートは、現在の時刻 (秒単位) を取得し、それを Movable Ink 画像タブの終わりに (クエリパラメーターとして) 付加し、最終結果を出力します。**Test**タブでプレビューできます。これにより、コードが評価され、プレビューが表示されます。
 
 {% endtab %}
 {% endtabs %}
 
 ## トラブルシューティング
- 
-#### ダイナミックな画像が正しく表示されない？どのチャネルに問題がありますか？
-- **押す**:Movable Ink 画像 URL の前に空のロジックがあることを確認してください。<br>{% raw %}```{% if true %}{% endif %}https://movable-ink-image-url-goes-here```{% endraw %}
-- **アプリ内メッセージとコンテンツカード**:各インプレッションの画像URLが一意であることを確認してください。これは、各URLが異なるように適切なLiquidを追加することで実行できます。[アプリ内およびコンテンツカードメッセージの指示][指示]をご覧ください。 
-- **画像 not loading**:必ずすべての「マージタグ」をBrazeダッシュボードの対応するLiquidフィールドに置き換えてください。例えば: {% raw %}```https://mi-msg.com/p/rp/image.png?mi_u=%%email%%```{% endraw %} と {% raw %}```https://mi-msg.com/p/rp/image.png?mi_u={{${email_address}}}```{% endraw %}。
 
-#### AndroidでGIFを表示するのに問題がありますか？
-- Androidは実装にGIFサポートを必要とします。Androidの[アプリ内メッセージカスタマイズ][GIFサポート]記事に従って、この設定がない場合は設定してください。
+### 動的画像が正しく表示されませんか?どんなチャネルで苦労していますか？
+- **プッシュ通知**Movable Ink 画像 URL の前に空のロジックがあることを確認します。<br>{% raw %}```{% if true %}{% endif %}https://movable-ink-image-url-goes-here```{% endraw %}
+- **アプリ内メッセージとコンテンツカード**:画像 URL がインプレッションごとに一意であることを確認します。このためには、各URL が異なる URL になるように適切な Liquid を追加します。\[アプリ内メッセージとコンテンツカードメッセージの手順]\[手順]を参照してください。 
+- **画像が読み込まれない**:Braze ダッシュボードで、すべての「マージタグ」を対応する Liquid フィールドに必ず置き換えてください。たとえば、{% raw %}```https://mi-msg.com/p/rp/image.png?mi_u=%%email%%```{% endraw %} を {% raw %}```https://mi-msg.com/p/rp/image.png?mi_u={{${email_address}}}```{% endraw %} に置き換えます。
+
+### Android で GIF を表示するときに問題がありますか?
+- Androidには、実施にあたってGIFの支援が必要である。この設定がない場合は、Android\[アプリ内メッセージ customization]\[GIFsupport] 記事に従ってください。
 
 [1]: https://www.movableink.com/
-[データソース]: ({% image_buster /assets/img/movable_ink/movable_ink1.png %})
-[サポート]: https://support.movableink.com/
-[GIFサポート]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/customization/gifs/
-[指示]: {{site.baseurl}}/partners/message_personalization/dynamic_content/movable_ink/#step-4-braze-experience
+\[datasource]: ({% image_buster /assets/img/movable_ink/movable_ink1.png %})
+\[support]: https://support.movableink.com/
+\[GIFsupport]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/customization/gifs/
+\[Instructions]: {{site.baseurl}}/partners/message_personalization/dynamic_content/movable_ink/#step-4-braze-experience
 [1]: ({% image_buster /assets/img/movable_ink/android.png %})
 [2]: ({% image_buster /assets/img/movable_ink/ios.png %})
 [3]: ({% image_buster /assets/img/movable_ink/web.png %})
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink/customer_data_api.md b/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink/customer_data_api.md
index a02434f2f7d..a12d9ffcc8d 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink/customer_data_api.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink/customer_data_api.md
@@ -1,31 +1,31 @@
 ---
-nav_title: 顧客データAPIに接続する
-article_title: Movable Ink Customer Data APIに接続する
-description: "この参考記事では、Customer Data APIを使用して、Brazeに保存されている顧客のイベントデータを活性化し、Movable Ink内でパーソナライズされたコンテンツを生成するための接続方法について概説する。"
+nav_title: Customer Data API への接続
+article_title: Movable Ink Customer Data API への接続
+description: "このリファレンス記事では、Braze に保存されている顧客イベントデータをアクティブ化して、Movable Ink 内でパーソナライズされたコンテンツを生成するために、Customer Data API を使用して接続する方法について説明します。"
 page_type: partner
 search_tag: Partner
 ---
 
-# Movable Ink Customer Data APIに接続する
+# Movable Ink Customer Data API への接続
 
-> BrazeとMovable Inkの顧客データAPI統合により、マーケティング担当者はBrazeに保存された顧客イベントデータを有効化して、Movable Ink内でパーソナライズされたコンテンツを生成することができる。
+> Braze と Movable Ink Customer Data API の統合により、マーケターは Braze に保存されている顧客イベントデータをアクティブ化して、Movable Ink 内でパーソナライズされたコンテンツを生成できます。
 
-ムーバブル・インクは、顧客データAPIを通じてBrazeから行動イベントを取り込むことができる。イベントは、ムーバブルインクに渡される一意のユーザーID（UUID）に基づいてユーザープロファイルに保存される。
+Movable Ink は、Customer Data API を介して Braze から行動イベントを取り込むことができます。イベントは、Movable Ink に渡されるユニークユーザー ID (UUID) に基づいてユーザープロファイルに保存されます。
 
-ストーリーズ、Movable Ink Customer Data API、およびMovable Inkが行動データをどのように活用しているかについての詳細は、以下のサポートセンターの記事を参照されたい：
+ストーリー、Movable Ink Customer Data API、および Movable Ink がどのように行動データを活用するかの詳細については、以下のサポートセンターの記事を参照してください。
 
 - [行動データでコンテンツを強化する](https://support.movableink.com/hc/en-us/sections/360001239453-Power-content-with-behavioral-data)
-- [顧客データAPIの紹介とガイド](https://support.movableink.com/hc/en-us/articles/13815957200663-Customer-Data-API-introduction-and-guide)
-- [よくある質問顧客データAPI](https://support.movableink.com/hc/en-us/articles/12423178752279-FAQ-Customer-Data-API)
+- [Customer Data API の概要およびガイド](https://support.movableink.com/hc/en-us/articles/13815957200663-Customer-Data-API-introduction-and-guide)
+- [FAQ:Customer Data API](https://support.movableink.com/hc/en-us/articles/12423178752279-FAQ-Customer-Data-API)
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| ムーバブル・インクアカウント | このパートナーシップを利用するには、ムーバブル・インクのアカウントが必要である。 |
-| Movable Ink API認証情報 | Movable Inkのソリューション・チームがAPI認証情報を生成する。APIクレデンシャルは以下のものである：{::nomarkdown}<ul><li>エンドポイントURL（データの送信先）</li><li>ユーザー名とパスワード（APIの認証に使用される）</li></ul>{:/} 必要であれば、Movable Inkはユーザー名とパスワードをbase64エンコード値として提供し、基本認証ヘッダー値として使用することができる。 |
-| 行動イベント・ペイロード | イベントペイロードをMovable Inkクライアントエクスペリエンスチームと共有する必要がある。詳細については、「Movable Inkと[イベントペイロードを共有する](#event-payloads)」を参照のこと。 |
-| クリエイティブ・アセットとビジネス・ロジック | ブロックを構築する方法についてMovable Inkに指示するAdobe Photoshop（PSD）ファイルや予備画像など、クリエイティブ資産をMovable Inkと共有する必要がある。また、パートナーがアクティベートしたコンテンツ・ブロックをいつ、どのように表示するかのビジネス・ロジックを提供する必要がある。 |
+| Movable Ink アカウント | このパートナーシップを活用するには、Movable Ink アカウントが必要です。 |
+| Movable Ink API 認証情報 | Movable Ink のソリューションチームが API 認証情報を生成します。API 認証情報は、以下で構成されます。{::nomarkdown}<ul><li>エンドポイントURL（データの送信先）</li><li>ユーザー名とパスワード（APIの認証に使用される）</li></ul>{:/} 必要に応じて、Movable Ink はユーザー名とパスワードを、基本認証ヘッダー値として使用される base64 でエンコードされた値として指定できます。 |
+| 行動イベント・ペイロード | イベントペイロード をMovable Ink クライアントエクスペリエンスチームと共有する必要があります。詳細については、「Movable Inkと[イベントペイロードを共有する](#event-payloads)」を参照のこと。 |
+| クリエイティブ・アセットとビジネス・ロジック | Movable Ink とクリエイティブアセットを共有する必要があります。これには、ブロックとフォールバックイメージの作成方法を Movable Ink に指示する Adobe Photoshop (PSD) ファイルも含まれます。また、パートナーによってアクティブ化されたコンテンツブロックをいつどのように表示するかについてのビジネスロジックを提供する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
@@ -36,45 +36,45 @@ search_tag: Partner
 
 1. Brazeで、[Webhookキャンペーンを作成する][1]。
 2. キャンペーン名と任意の説明をつける。
-3. テンプレートとして**Blank Templateを**選択する。
+3. テンプレートとして \[**空白のテンプレート**] を選択します。
 
-#### ステップ 1b: 顧客データAPIの認証情報を追加する
+#### ステップ 1b: Customer Data API 認証情報を追加する
 
 1. **Webhook URL**フィールドに、Movable InkのエンドポイントURLを入力する。
 
-![BrazeのWebhookコンポーザーのComposeタブで、Movable InkのエンドポイントURLとリクエストボディをJSON Key/Value Pairsに設定する。]\[img1]{: style="max-width:75%" }
+![Braze の Webhook コンポーザーの「作成」タブ。Movable Ink エンドポイントのURL と、「JSON キーと値のペア」が設定された「リクエスト本文」が表示されている。]\[img1]{: style="max-width:75%" }
 
 {:start="2"}
-2\.**設定**タブを選択する。
+2\.\[**設定**] タブを選択します。
 3\.以下のリクエストヘッダーをキーと値のペアとして追加する：
 
-| キー | 価値 |
+| キー | 値 |
 | --- | --- |
 | コンテンツタイプ | application/json |
-| 認可 | ムーバブルインクから受け取った基本認証を入力する。 |
+| Authorization | Movable Ink から受け取った基本認証を入力します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ![BrazeのWebhookコンポーザーの設定タブ。Content-TypeとAuthorizationのキー・バリュー・ペアがある。]\[img2]{: style="max-width:75%" }
 
-#### ステップ1c：ペイロードを設定する
+#### ステップ1c: ペイロードを設定する
 
-1. **作曲**タブに戻る。
-2. **リクエストボディには**、JSONキーと値のペアで独自のリクエストボディを作成するか、生のテキストとしてイベントペイロードを入力する。標準的なeコマースイベントの例については、[サンプルペイロードを](#sample-payloads)参照のこと。
+1. \[**作成**] タブに戻ります。
+2. **リクエスト本文**として、JSON キーと値のペアを使用して独自のリクエスト本文を作成するか、イベントペイロードを生のテキストとして入力します。標準的な e コマースイベントの例については、[サンプルペイロード](#sample-payloads)を参照してください。
 
-![Brazeのウェブフック・コンポーザーのコンポーズ・タブに、ID、タイムスタンプ、ユーザーID、イベントタイプのJSONキー・バリュー・ペアがある。]\[img3]{: style="max-width:75%" }
+![ID、タイムスタンプ、ユーザー ID、およびイベントタイプの JSON キーと値のペアが指定されている、Braze の Webhook コンポーザーの「作成」タブ。]\[img3]{: style="max-width:75%" }
 
-#### ステップ1d：ウェブフックをテストする {#step-1d}
+#### ステップ1d: Webhook をテストする {#step-1d}
 
-ペイロードのサンプルをMovable Inkクライアント・エクスペリエンス・チームと共有する必要がある。このペイロードは、作成したペイロードに基づいて、**Test**タブで生成することができる。
+サンプルペイロード をMovable Ink クライアントエクスペリエンスチームと共有する必要があります。このペイロードは、作成したペイロードに基づいて、**Test**タブで生成することができる。
 
 {% alert important %}
-Movable Inkでは、Movable Inkクライアントエクスペリエンスチームがマッピングを完了し、テストを受ける準備ができていることを確認するまで、BrazeでのWebhookのテストを待つことを推奨している。このマッピングが完全でない場合、テスト時にエラーが出る可能性が高い。
+Movable Ink は、Movable Ink クライアントエクスペリエンスチームがマッピングを完了し、テストを受ける準備ができていることを確認するまでは、Braze での Webhook のテストを行わないようにすることが推奨されています。このマッピングが完全でない場合、テスト時にエラーが出る可能性が高い。
 {% endalert %}
 
 ウェブフックをテストするには、以下のようにする：
 
 1. \[**テスト**] タブを選択します。
-2. ユーザーとしてメッセージをプレビューし、そのユーザーのイベントペイロードのサンプルを表示する。プレビューは、ランダムユーザー、特定ユーザー、カスタムユーザーのいずれかを選択できる。
+2. ユーザーとしてメッセージをプレビューし、そのユーザーのイベントペイロードのサンプルを表示する。ランダムユーザー、特定のユーザー、またはカスタムユーザーとしてのプレビューのいずれかを選択できます。
 3. 問題がなければ、**Send testを**クリックしてテストリクエストを送信する。
 
 ![200OKレスポンスを示すBrazeのWebhookレスポンスメッセージ。]\[img4]{: style="max-width:75%" }
@@ -85,23 +85,23 @@ Movable Inkでは、Movable Inkクライアントエクスペリエンスチー
 
 ウェブフックの作成とテストが終わったら、[キャンペーンをスケジュールする][2]。 
 
-Brazeは、スケジュール配信、アクションベース配信、APIトリガー配信をサポートしている。[アクション・ベースの配信は][3]通常、ほとんどの行動イベントのユースケースに最適である。お客様のユースケースにとって何が理にかなっているかについてのご質問は、BrazeおよびMovable Inkのカスタマーサクセスマネージャーにお問い合わせいただきたい。
+Braze では、スケジュールされたアクションベースのAPI トリガー配信がサポートされています。[アクション・ベースの配信は][3]通常、ほとんどの行動イベントのユースケースに最適である。お客様のユースケースにとって何が理にかなっているかについてのご質問は、BrazeおよびMovable Inkのカスタマーサクセスマネージャーにお問い合わせいただきたい。
 
-アクション・ベースのデリバリーのために：
+アクションベースの配信の場合:
 
 1. トリガーアクションを指定する。これは、Movable Inkへのウェブフックをトリガーするイベントである。
-2. **Schedule Delayが** **Immediatelyに**設定されていることを確認する。イベントデータは、イベント発生直後に遅延なくムーバブルインクに送信されるべきである。
-3. 開始時間を指定してキャンペーン期間を設定する。終了時刻は適用されない可能性が高いが、ユースケースに必要であれば設定できる。
+2. \[**スケジュールの遅延**] が \[**すぐに実行**] に設定されていることを確認します。イベント発生直後にイベントデータが遅滞なく Movable Ink に送信される必要があります。
+3. 開始時間を指定してキャンペーン期間を設定する。終了時刻を適用できない可能性がありますが、ユースケースに必要な場合は設定できます。
 
 {% alert note %}
-データがリアルタイムでMovable Inkにストリーミングされるようにするには、**ローカルタイムゾーンのユーザーにキャンペーンを送信するを**選択しないこと。
+データが Movable Ink にリアルタイムでストリーミングされるようにするには、\[**ユーザーのローカルタイムゾーンにあわせてキャンペーンを送信**]を選択しないでください。
 {% endalert %}
 
-#### ステップ 2b: 聴衆を特定する
+#### ステップ 2b: オーディエンスを指定する
 
 次に、このキャンペーンでターゲットにしたいユーザーを決定する。詳細については、「[ユーザーをターゲットにする][4]」を参照のこと。
 
-**コントロールグループの**チェックボックスをオフにして、キャンペーンでA/Bテストを使用しないことを確認する。コントロールグループが含まれる場合、ユーザーの何割かはMovable Inkにデータが送信されない。聴衆は全員、対照群ではなく変種に行くべきだ。
+**コントロールグループの**チェックボックスをオフにして、キャンペーンでA/Bテストを使用しないことを確認する。コントロールグループが含まれている場合、一定の割合のユーザーのデータが Movable Ink に送信されません。オーディエンス全体を、コントロールグループではなくバリアントに移動する必要があります。
 
 ![BrazeキャンペーンにおけるA/Bテストパネル。100％のバリアント分布がバリアント1に割り当てられ、コントロールグループはない。]\[img5]
 
@@ -109,7 +109,7 @@ Brazeは、スケジュール配信、アクションベース配信、APIトリ
 
 必要であれば、Braze内でこのキャンペーンにコンバージョンイベントを割り当てることができる。
 
-しかし、Webhookはあくまでデータをストリーミングするためのものであることを考えると、このレベルでのアトリビューションは、Brazeからの行動データがコンテンツのパーソナライズに使用された後、キャンペーンレベルでのアトリビューションを見るよりも役に立たない可能性が高い。
+ただし、Webhook がデータのストリーミングのみを目的としている場合、このレベルでのアトリビューションは、Braze の行動データを使用してコンテンツをパーソナライズした後にキャンペーンレベルでアトリビューションを確認するよりも、有用性が低い可能性があります。
 
 ### ステップ3:キャンペーンを開始する
 
@@ -119,23 +119,23 @@ Brazeは、スケジュール配信、アクションベース配信、APIトリ
 
 ### 一意のユーザー識別子で整列する
 
-`mi_u` として使用している一意のユーザー識別子（UUID）値がBraze内で利用可能であり、Movable Inkに送信されるイベントペイロードに含めることができることを確認する。
+`mi_u` として使用しているユニークユーザー識別子 (UUID) 値が Braze 内で使用可能であり、Movable Ink に送信されるイベントペイロードに含めることができることを確認します。
 
-これにより、画像を生成する際にMovable Inkが参照する行動イベントが、行動イベントを受け取ったのと同じ顧客に関連付けられていることが保証される。UUID値がBraze`external_id` と同じでない場合、UUIDを取得し、属性としてBrazeに渡すか、Brazeイベントのイベントプロパティでこの識別子を活用する必要がある。
+これにより、イメージを生成するときに Movable Ink が参照する動作イベントが、その動作イベントを受信した同一の顧客に関連付けられます。UUID 値がBraze `external_id` と同じではない場合、UUID はキャプチャされ、属性として Braze に渡されるか、またはこの ID を利用するために Braze イベントのイベントプロパティに入れて渡される必要があります。
 
-Brazeは、複数のプラットフォーム（ウェブやモバイルアプリなど）でユーザーの行動を追跡するため、1人のユーザーが複数の異なる匿名IDを持つ可能性がある。`identify` イベントが匿名識別子と単一の既知の識別子の両方を含む限り、これらのIDは、`identify` イベントがMovable Inkに送信されたときに、単一の既知のストーリーズユーザープロファイルにマージすることができる。
+Braze は複数のプラットフォーム (Web やモバイルアプリなど) にわたってユーザーの動作を追跡するため、1人のユーザーが複数の異なる匿名 ID を持つことがあります。`identify` イベントに匿名 ID と既知の単一 ID の両方が含まれている限り、`identify` イベントが Movable Ink に送信される時点で、これらの匿名 ID を単一の既知のストーリーズユーザープロファイルにマージできます。
 
-一旦Movable Inkが一人のユーザーについて`user_id` を受け取ると、そのユーザーに関する今後のすべてのイベントには、同じ`user_id` を含めなければならない。
+Movable Ink が単一ユーザーの`user_id` を受信したら、そのユーザーの今後のすべてのイベントには同じ `user_id` が含まれている必要があります。
 
-### Movable Inkでイベントペイロードを共有する {#event-payloads}
+### Movable Ink でのイベントペイロードの共有 {#event-payloads}
 
-Movable Inkの顧客データAPIへのコネクタを設定する前に、イベントのペイロードをMovable Inkのクライアント・エクスペリエンス・チームと共有しておくこと。これにより、Movable Inkはあなたのイベントを彼らのイベントスキーマにマッピングすることができ、APIコールの拒否や失敗を防ぐことができる。
+Movable Ink の Customer Data API へのコネクターを設定する前に、イベントペイロードを Movable Ink クライアントエクスペリエンスチームと共有してください。これにより、Movable Ink がお客様のイベントを Movable Ink のイベントスキーマにマッピングでき、API 呼び出しの拒否や失敗を防ぐことができます。
 
-任意のイベントプロパティを使用して、Braze内でイベントペイロードを生成できる。ランダムなユーザー、または特定のユーザーIDを検索してサンプルペイロードを生成する。詳細は上記の[ステップ1dを](#step-1d)参照のこと。
+任意のイベントプロパティを使用して、Braze内でイベントペイロードを生成できる。ランダムなユーザー、または特定のユーザーIDを検索してサンプルペイロードを生成する。詳細については上記の「[ステップ 1d](#step-1d)」を参照してください。
 
-このサンプルペイロードをMovable Inkクライアントエクスペリエンスチームと共有する。サンプルのペイロードに、個人を特定できる機密情報（電子メールアドレス、電話番号、生年月日など）が含まれていないことを確認する。 
+このサンプルペイロードをMovable Inkクライアントエクスペリエンスチームと共有する。サンプルペイロードに、機密性の高い個人識別情報 (メールアドレス、電話番号、誕生日全体など) が含まれていないことを確認します。 
 
-カスタムイベント・プロパティと、プロパティに含まれるデータの期待されるフォーマットの詳細については、[カスタムイベント・プロパティを][5]参照のこと。
+カスタムイベントプロパティと、プロパティに含まれるデータに必要な形式について詳しくは、「[カスタムイベントプロパティ][5]」を参照してください。
 
 ### 既知のユーザーと匿名のユーザー
 
@@ -143,20 +143,20 @@ Brazeでは、匿名のユーザープロファイルでイベントを記録す
 
 #### 既知のユーザーのBrazeイベントのみを転送する
 
-ウェブフック・キャンペーンでは、`External User ID` フィルタを使用して、`External User ID` `is not blank` フィルタで`external_id` を持つユーザーのみをターゲットにする。
+Webhook キャンペーンで `External User ID` フィルターを使用して、フィルター `External User ID` `is not blank` に一致する `external_id` を持つユーザーのみをターゲットにします。
 
 #### 匿名ユーザーと既知ユーザーのBrazeイベントを転送する
 
-匿名ユーザー（プロファイルに`external_id` が割り当てられる前のユーザー）からのBrazeイベントを転送したい場合、`external_id` が利用可能になるまで、Movable Inkの`anonymous_id` として使用する識別子を決定する必要がある。Brazeユーザープロフィールに常に表示される`anonymous_id` 。Webhook 本体の Liquid ロジックを使って、`anonymous_id` と`user_id` のどちらを渡すかを決めることができる。
+匿名ユーザー（プロファイルに`external_id` が割り当てられる前のユーザー）からのBrazeイベントを転送したい場合、`external_id` が利用可能になるまで、Movable Inkの`anonymous_id` として使用する識別子を決定する必要がある。Brazeユーザープロフィールに常に表示される`anonymous_id` 。Webhook 本文で Liquid ロジックを使用して、`anonymous_id` または `user_id` を渡すかどうかを決定できます。
 
-詳しくは、[サンプルペイロードの](#sample-payloads)下にあるサンプルウェブフックを参照のこと。
+詳細については、[サンプルペイロード](#sample-payloads)にある Webhook の例を参照してください。
 
 ## ペイロードの例
 
 ### プロダクト・ビュー・イベント
 
 {% tabs ローカル %}
-{% tab ブレイズ・トリガー・イベント例 %}
+{% tab Braze トリガーイベントの例 %}
 
 {% raw %}
 
@@ -190,7 +190,7 @@ Brazeでは、匿名のユーザープロファイルでイベントを記録す
 {% endraw %}
 
 {% endtab %}
-{% tab 予想される可動インク要求ペイロード %}
+{% tab 必要な Movable Ink リクエストペイロード %}
 
 {% raw %}
 
@@ -278,7 +278,7 @@ curl --location --request POST 'https://collector.movableink-dmz.com/behavioral/
 ### カテゴリー表示イベント
 
 {% tabs ローカル %}
-{% tab ブレイズ・トリガー・イベント例 %}
+{% tab Braze トリガーイベントの例 %}
 
 {% raw %}
 
@@ -302,7 +302,7 @@ curl --location --request POST 'https://collector.movableink-dmz.com/behavioral/
 {% endraw %}
 
 {% endtab %}
-{% tab 予想される可動インク要求ペイロード %}
+{% tab 必要な Movable Ink リクエストペイロード %}
 
 {% raw %}
 
@@ -361,7 +361,7 @@ curl --location --request POST 'https://collector.movableink-dmz.com/behavioral/
 ### イベントを特定する
 
 {% tabs ローカル %}
-{% tab ブレイズ・トリガー・イベント例 %}
+{% tab Braze トリガーイベントの例 %}
 
 {% raw %}
 
@@ -379,7 +379,7 @@ curl --location --request POST 'https://collector.movableink-dmz.com/behavioral/
 
 {% endraw %}
 {% endtab %}
-{% tab 予想される可動インク要求ペイロード %}
+{% tab 必要な Movable Ink リクエストペイロード %}
 
 {% raw %}
 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink/dynamic_sms_link.md b/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink/dynamic_sms_link.md
index cf79cdd0e7c..8889621eeb5 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink/dynamic_sms_link.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/movable_ink/dynamic_sms_link.md
@@ -1,53 +1,53 @@
 ---
 nav_title: ダイナミックSMSリンクプレビュー
 article_title: ダイナミックSMSリンクプレビュー
-description: "ここでは、Movable InkのSMSリンクプレビュー機能を有効にして使用する方法について説明します。"
+description: "このリファレンス記事では、Movable Ink の SMS プレビュー機能をオンにして使用する方法について説明します。"
 page_type: partner
 search_tag: Partner
 ---
 
-# ダイナミックSMS連携プレビュー
+# ダイナミック SMS リンクプレビュー
 
-> Movable Ink のダイナミックな SMS リンクプレビューを使用すると、SMS と同じ料金でMMS の没入感を活用できます。これにより、BrazeとMovable Inkを使用して、コスト効率の高いパーソナライズされた豊富なメッセージングエクスペリエンスを実現できます。
+> Movable Ink のダイナミック SMS リンクプレビューを使用すると、SMS と同じコストで MMS の没入感を活用できます。これにより、Braze と Movable Ink を使用して、コスト効率の高いパーソナライズされたリッチなメッセージングエクスペリエンスを実現できます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | --- | --- |
-| Movable Ink勘定 | この提携の前進タグeを考慮するには、Movable Inkな考慮が必要である。 |
-| データソース | データソースをMovable Inkに接続する必要があります。これは、CSV、Web サイト読み込み、またはAPI を使用して実行できます。 |
+| Movable Ink アカウント | このパートナーシップを活用するには、Movable Ink アカウントが必要です。 |
+| データソース | データソースをMovable Inkに接続する必要があります。これは、CSV、Web サイトインポート、または API を使用して実行できます。 |
 | MMS送信機能 | Braze 経由でMMS 用に設定されていることを確認します。
 | [リンク短縮]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/) | リンク短縮がオンになっていることを確認します。 | 
-| コンタクトカード | あなたのブランド(送信者)は、iOSと連携するために、リンクプレビューのためにユーザーの電話機に連絡先として保存されなければなりません。これは、連絡先カードまたは別のメソッドで行うことができます。 |
+| 連絡先カード | あなたのブランド(送信者)は、iOSと連携するために、リンクプレビューのためにユーザーの電話機に連絡先として保存されなければなりません。これは、連絡先カードまたは別の方法で行うことができます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-以下の各ステップs に従って、iOS とAndroid オペレーティングシステム s のダイナミックな SMS を送信します。
+iOS および Android オペレーティングシステム用のダイナミック SMS リンクを送信するには、以下のそれぞれの手順に従います。
 
 ### iOS
 
 {% alert important %}
-iOSのリンクプレビュー "画像sを許可するには、ユーザーsが連絡先としてブランド(送信者)を追加する必要があります。
+iOS 用のリンクプレビュー画像を許可するには、ユーザーがブランド (送信者) を連絡先として追加する必要があります。
 {% endalert %}
 
-#### ステップ1:コンタクトカードキャンペーンの作成
+#### ステップ1:連絡先カードキャンペーンを作成する
 
-ユーザー が連絡先としてブランドを保存した後、Braze [コンテンツカード]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/contact_card/) または別の方法で、**タップしてプレビューをロード** プロンプトとMovable Inkリンクを表示できます。
+ユーザーが Braze [コンテンツカード]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/contact_card/)または別の方法でブランドを連絡先として保存したら、\[**タップしてプレビューを読み込む**] プロンプトとMovable Ink リンクが表示されます。
 
 ![1]{: style="max-width:30%;"}
 
-#### ステップ2:Movable Ink送信
+#### ステップ2:Movable Ink リンクを送信する
 
 1. Movable InkでSMS キャンペーンを作成し、クリックスルー URLを生成します。
-2. Braze ダッシュボードで、**キャンペーン s** に移動し、**キャンペーン** ドロップダウンから新しいSMS/MMS キャンペーンを設定します。
-3. キャンペーン作成者:
+2. Braze ダッシュボードで \[**キャンペーン**] に移動し、\[**キャンペーンを作成**] ドロップダウンから新しい SMS/MMS キャンペーンを設定します。
+3. SMS キャンペーン作成画面で、次のようにします。
     - サブスクリプショングループを設定する。
     - メッセージを入力します。
     - Movable Inkリンク**最後の**を、メッセージ本文の他のすべてのテキストの後に追加します。<br><br>![2]{: style="max-width:50%;"}
 
 {% alert tip %}
-リキッドパーソナライゼーションのリフレッシュ版は[リキッド]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/using_liquid/)をご覧ください。  
+Liquid パーソナライゼーションについて再確認するには、[Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/using_liquid/) を参照してください。  
 {% endalert %}
 
 {: start="4"}
@@ -55,21 +55,21 @@ iOSのリンクプレビュー "画像sを許可するには、ユーザーsが
 
 ![3]{: style="max-width:70%;"}
 
-ユーザー s がリンクプレビューを読み込むすると、パーソナライズされた "画像がレンダリングされ、Web サイト、アプリ、またはランディングページにリンクアウトできます。
+ユーザーがリンクプレビューを読み込むと、パーソナライズされたされた画像がレンダリングされ、Web サイト、アプリ、ランディングページにリンクアウトする機能が示されます。
 
 ![4]{: style="max-width:30%;"}
 
-### Android(グーグル&アンプ、サムスン端末)
+### Android (Google および Samsung デバイス)
 
-Android ユーザー は、ダイナミックなのSMS リンクプレビューを受信するために、連絡先としてブランドを保存する必要はありません。ただし、自動的にリンクプレビューs を読み込むできるようにすることをお勧めします。
+Android ユーザーは、ダイナミック SMS リンクプレビューを受信するためにブランドを連絡先として保存する必要はありません。ただし、デバイスが自動的にリンクプレビューを読み込むことができるように、このように保存することが推奨されます。
 
 ![5]{: style="max-width:30%;"}
 
-連絡先としてブランドを保存しておらず、自動プレビューを有効にしているユーザは、**タップしてプレビュー"画像を読み込むするために**を選択する必要があります。<br>![6]{: style="max-width:30%;"}
+ブランドを連絡先として保存しておらず、自動プレビューを有効にしているユーザーは、プレビュー画像を読み込むには \[**タップしてプレビューを読み込む**]を選択する必要があります。<br>![6]{: style="max-width:30%;"}
 
 ## 考慮事項
 
-- 1つのプレビューのみを表示します。SMS本体に複数のリンクがある場合、コンテンツは生成されません。 
+- メッセージには1つのプレビューリンクのみを含めてください。SMS本体に複数のリンクがある場合、コンテンツは生成されません。 
 - プレビューリンクの後に文字を含めないでください。そうしないと、破損する可能性があります。
 
 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/niftyimages.md b/_lang/ja/_partners/message_personalization/dynamic_content/niftyimages.md
index 7b417b70f84..942e8f19230 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/niftyimages.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/niftyimages.md
@@ -9,28 +9,28 @@ search_tag: Partner
 
 # NiftyImages
 
-> [NiftyImages](https://niftyimages.com)は、マーケターがより効率的に最新の関連性のあるメールコミュニケーションを送信しながら、エンゲージメントと収益を向上させることができるリアルタイムのメールパーソナライゼーションソフトウェアです。それはマーケティング担当者が簡単かつ迅速にメールにダイナミックなコンテンツを追加できるユーザーに優しいセルフサービングツールです。
+> [NiftyImages](https://niftyimages.com) は、マーケターが関連性のある最新情報を含むメールをより効率的に送信し、かつエンゲージメントを強化し収益を増やすことができるリアルタイムのメールパーソナライゼーションソフトウェアです。それはマーケティング担当者が簡単かつ迅速にメールにダイナミックなコンテンツを追加できるユーザーに優しいセルフサービングツールです。
 
 ## 前提条件
 
-NiftyImagesは、統合を必要とせずにデフォルトのBrazeプラットフォームで動作します。始めるには、[NiftyImagesアカウント](https://niftyimages.com/Signup)が必要です。
+NiftyImages はデフォルトの Braze プラットフォームで動作し、統合は不要です。使用を開始するために必要なものは、[NiftyImages アカウント](https://niftyimages.com/Signup)だけです。
 
 ## サポートされている機能
 
 BrazeでNiftyImagesを活用することで、既存のBrazeパーソナライゼーションタグをNiftyImagesのURLにマッピングすることにより、メールキャンペーン用のダイナミックでパーソナライズされた画像を作成できます。
 
 - **プライバシー;**すべてのデータはNiftyImagesではなく、Brazeに保存されます。
-- **パーソナライズされた画像:**Brazeのマージタグを使用して画像をパーソナライズします。
+- **パーソナライズされた画像:**Braze のマージタグを使用して画像をパーソナライズします。
 - **チャートとグラフ:**カスタマイズ可能なチャートやグラフを通じて、ティアレベル、顧客ステータス、支出金額、ポイントなどを表示します。
 - **地図:**ユーザーがメールを開く場所に最も近い場所を使用して地図の画像を表示します。
-- **カスタムカウントダウンタイマー:**誕生日、試用期限、最終購入日、延滞請求書、または最終サインイン日のための日付データベース変数を使用して、ユニークなタイマーを表示します。
-- **リアルタイムコンテンツ:**製品の推奨、カートの放棄、価格の下落、在庫レベル、天気などのリアルタイム画像を表示します。
+- **カスタムカウントダウンタイマー:**誕生日、トライアルの有効期限、最終購入日、支払期日を過ぎた請求書、最終サインイン日などの日付データベース変数を使用して独自のタイマーを表示します。
+- **リアルタイムコンテンツ:**おすすめ製品、カートの放棄、値下げ、在庫レベル、天気などのリアルタイム画像を表示します。
 - **ライブ投票:**ライブ投票を表示してエンゲージメントを促進し、関心レベルに関するインサイトを得る。
 - **ルールベースのロジック:**ユーザーデータ、人口統計、行動、場所、時刻、曜日、開いているデバイス、オペレーティングシステムなどに基づいてダイナミックな画像を表示します。
 
-例えば、これはNiftyImagesが顧客の名を使用して生成したカスタム画像です。
+たとえば次の画像は、顧客の名を使用して NiftyImages によって生成されたカスタム画像です。
 
-![代替テキスト。]({% image_buster /assets/img/niftyimages/1.png %}){: style="max-width:70%;"}
+![ALT_TEXT.]({% image_buster /assets/img/niftyimages/1.png %}){: style="max-width:70%;"}
 
 ## NiftyImageを作成する
 
@@ -45,7 +45,7 @@ NiftyImagesでマージタグを選択し、デフォルト値を入力します
 ![代替テキスト]({% image_buster /assets/img/niftyimages/3.png %})
 {: style="max-width:70%;"}
 
-オプションとして、将来の使用のためにタグを保存することができます。完了したら、**保存**を選択してマージタグを作成します。
+必要に応じて、タグを将来使用するために保存することもできます。完了したら、**保存**を選択してマージタグを作成します。
 
 ![代替テキスト]({% image_buster /assets/img/niftyimages/4.png %}){: style="max-width:70%;"}
 
@@ -57,6 +57,6 @@ NiftyImagesでマージタグを選択し、デフォルト値を入力します
 
 ### ステップ 3:Brazeに画像URLを追加
 
-Brazeでキャンペーンまたはキャンバスを開封し、NiftyImageのURLを貼り付けます。オプションで、変更をプレビューしてLiquidタグを確認できます。
+Braze でキャンペーンまたはキャンバスを開き、NiftyImage URL を貼り付けます。必要に応じて、変更をプレビューして Liquid タグを確認できます。
 
 ![代替テキスト]({% image_buster /assets/img/niftyimages/6.png %})
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/offerfit.md b/_lang/ja/_partners/message_personalization/dynamic_content/offerfit.md
index 28b2686d323..244860bd4a0 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/offerfit.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/offerfit.md
@@ -13,56 +13,56 @@ search_tag: OfferFit
 
 > [OfferFit](https://www.offerfit.ai/) 手動A/B テストをAI テストに置き換えます。ライフサイクルマーケターでは、OfferFitのAIテストを使用して、顧客ごとに1:1の最適な判断を行い、すべての変数を同時にテストし、マーケットの変化を検出して適応させます。
 
-OfferFitとBrazeインテグレーションを使用すると、顧客データに基づいて、すべての顧客の正しいメッセージ、チャネル、タイミングを自動的に検出できます。クロスセル、アップセル、再購入、リテンション、更新、照会、ウィンバックなどの業務目標を使用して、キャンペーンs を既存の識別された顧客s に最適化できます。
+OfferFitとBrazeインテグレーションを使用すると、顧客データに基づいて、すべての顧客の正しいメッセージ、チャネル、タイミングを自動的に検出できます。ビジネス目標 (クロスセル、アップセル、再購入、リテンション、更新、紹介、ウィンバックなど) を使用して、既存の特定された顧客に合わせてキャンペーンを最適化できます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 |-------------|-------------|
-| OfferFit使用許諾 | この提携の事前タグeを受けるためには、積極的なOfferFit免許が必要である。 |
+| OfferFit使用許諾 | このパートナーシップを活用するには、有効な OfferFit ライセンスが必要です。 |
 | Braze REST API キー | 次の権限を持つBraze REST API キー。 {::nomarkdown}<ul><li><code>users.export.ids</code></li><li><code>users.export.segment</code></li><li><code>messages.send</code></li><li><code>campaigns.trigger.send</code></li> <li><code>campaigns.list</code></li><li><code>campaigns.data_series</code></li><li><code>campaigns.details</code></li><li><code>canvas.trigger.send</code></li><li><code>canvas.list</code></li><li><code>canvas.data_series</code></li><li><code>canvas.details</code></li><li><code>segments.list</code></li><li><code>segments.data_series</code></li><li><code>segments.details</code></li><li><code>templates.create</code></li><li><code>templates.update</code></li><li><code>templates.info</code></li><li><code>templates.list</code></li></ul>{:/} これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
-| Braze REST原薬エンドポイント | [Your REST API エンドポイント URL][1].エンドポイントは、インスタンスのBraze URL によって異なります。 |
+| Braze REST API エンドポイント | [REST API エンドポイントURL][1]。エンドポイントはインスタンスの Braze URL に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、**デベロッパコンソール**> **API設定**でAPI キーを作成できます。
 {% endalert %}
 
-### Braze REST原薬エンドポイント
+### Braze REST API エンドポイント
 
 OfferFitの使用許諾およびユースケースによって、使用するBraze REST API エンドポイントが決まります。以下に、使用できるさまざまなAPI エンドポイントを示します。
 
-| Braze REST原薬エンドポイント | OfferFit使用量 |
+| Braze REST API エンドポイント | OfferFit使用量 |
 |--------------|----------------|
-| [POST /users/export/ids]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)                          | キャンペーンまたはキャンバスがターゲットとする顧客の一覧を取得します。OfferFit はPII データを一切受け付けないため、`fields_to_export` 属性は、プラットフォーム ユーザーと一致するデータ属性のみを取得するために使用されます。 |
-| [POST /users/export/segment]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/)                         | 指定したSegmentの一部であるすべてのユーザーを取得します。OfferFit はPII データを一切受け付けないため、`fields_to_export` 属性は、プラットフォーム ユーザーと一致する非PII フィールドs のみを取得するために使用されます。 |
-| [POST/ユーザー/トラック]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)                                            | OfferFit は、このエンドポイントを使用して、メッセージングをパーソナライズするために使用できるカスタムデータ属性s でs を更新 ユーザープロファイルできます。                                                                                                                                            |
-| [POST /messages/send]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_messages/)                         | Braze でのAPI キャンペーンのトリガ。 |
+| [POST /users/export/ids]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)                          | キャンペーンまたはキャンバスがターゲットとする顧客のリストを取得します。OfferFit は PII データを受け入れないため、`fields_to_export` 属性は、プラットフォームユーザーと合意したデータ属性のみを取得するために使用されます。 |
+| [POST /users/export/segment]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/)                         | 指定したSegmentの一部であるすべてのユーザーを取得します。OfferFit は PII データを一切受け入れないため、`fields_to_export` 属性は、プラットフォームユーザーと合意した非 PII フィールドのみを取得するために使用されます。 |
+| [POST /users/track]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)                                            | OfferFit では、このエンドポイントを使用して、メッセージングのパーソナライズに使用できるカスタムデータ属性でユーザープロファイルを更新できます。                                                                                                                                            |
+| [POST /messages/send]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_messages/)                         | Braze で API キャンペーンをトリガーします。 |
 | [POST /campaigns/trigger/send]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns/)     | API-トリガー配信用に設定されたキャンペーンの送信をトリガーします。 |
-| [GET/キャンペーン/リスト]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaigns/)                                     | Braze で設定されているすべてのキャンペーンとその関連メタデータの一覧を取得します。 |
-| [GET /キャンペーンs/data_series]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_analytics/)                     | 指定したBraze キャンペーンの分析情報を取得します。 |
-| [GET/キャンペーン/詳細]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/)                           | Braze キャンペーンの内容を取得します。 |
-| [POST /canvas/trigger/send]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/)         | API-トリガー配信用に設定されたキャンバスの送信をトリガーします。 |
-| [GET/キャンバス/リスト]({{site.baseurl}}/api/endpoints/export/canvas/get_canvases/)                                            | Braze で設定されたすべてのキャンバスとその関連メタデータの一覧を取得します。 |
-| [GET /キャンバス/data_series]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_analytics/)                             | 指定したキャンバスの分析情報を取得します。 |
-| [GET/キャンバス/詳細]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/)                                   | 特定のキャンバスの詳細を取得します。 |
-| [GET/Segment/リスト]({{site.baseurl}}/api/endpoints/export/segments/get_segment/)                                        | Braze で設定されているすべてのSegmentとその関連メタデータの一覧を取得します。 |
-| [GET /Segments/data_series]({{site.baseurl}}/api/endpoints/export/segments/get_segment_analytics/)                        | Braze Segmentの大きさを取得します。 |
-| [GET/Segment/詳細]({{site.baseurl}}/api/endpoints/export/segments/get_segment_details/)                              | Braze Segmentの内容を取得します。 |
+| [GET /campaigns/list]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaigns/)                                     | Braze で設定されているすべてのキャンペーンとその関連メタデータの一覧を取得します。 |
+| [GET /campaigns/data_series]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_analytics/)                     | 指定したBraze キャンペーンの分析情報を取得します。 |
+| [GET /campaigns/details]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/)                           | 特定の Braze キャンペーンの詳細を取得します。 |
+| [POST /canvas/trigger/send]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/)         | API トリガー配信用に設定されたキャンバスの送信をトリガーします。 |
+| [GET /canvas/list]({{site.baseurl}}/api/endpoints/export/canvas/get_canvases/)                                            | Braze で設定されたすべてのキャンバスとその関連メタデータの一覧を取得します。 |
+| [GET /canvas/data_series]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_analytics/)                             | 特定のキャンバスの分析データを取得します。 |
+| [GET /canvas/details]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/)                                   | 特定のキャンバスの詳細を取得します。 |
+| [GET /segments/list]({{site.baseurl}}/api/endpoints/export/segments/get_segment/)                                        | Braze で設定されているすべてのSegmentとその関連メタデータの一覧を取得します。 |
+| [GET /segments/data_series]({{site.baseurl}}/api/endpoints/export/segments/get_segment_analytics/)                        | Braze セグメントのサイズを取得します。 |
+| [GET /segments/details]({{site.baseurl}}/api/endpoints/export/segments/get_segment_details/)                              | 特定の Braze セグメントの詳細を取得します。 |
 | [POST /templates/email/create]({{site.baseurl}}/api/endpoints/templates/email_templates/post_create_email_template/)      | 新しいBraze HTML メール テンプレートを作成します。 |
-| [POST /templates/email/update]({{site.baseurl}}/api/endpoints/templates/email_templates/post_update_email_template/)      | Braze HTML メール テンプレートをアップデートします。 |
-| [取得/templates/email/info]({{site.baseurl}}/api/endpoints/templates/email_templates/get_see_email_template_information/) | Braze HTML メール テンプレートの内容を取得します。 |
-| [取得/templates/email/list]({{site.baseurl}}/api/endpoints/templates/email_templates/get_list_email_templates/)           | Braze で設定されているすべてのBraze HTML メール テンプレートと`subject line` および`HTML content` の一覧を取得します。 |
+| [POST /templates/email/update]({{site.baseurl}}/api/endpoints/templates/email_templates/post_update_email_template/)      | 既存の Braze HTML メールテンプレートを更新します。 |
+| [GET /templates/email/info]({{site.baseurl}}/api/endpoints/templates/email_templates/get_see_email_template_information/) | 特定の Braze HTML メールテンプレートの詳細を取得します。 |
+| [GET /templates/email/list]({{site.baseurl}}/api/endpoints/templates/email_templates/get_list_email_templates/)           | Braze で設定されているすべてのBraze HTML メール テンプレートと`subject line` および`HTML content` の一覧を取得します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
 [integrate OfferFit](#integration)を実行した後、次の手順を実行して実験処理を自動化できます。
 
-1. 収益、コンバージョン s、ARPU など、最大化する**success metric** を選択します
-顧客データから測定できます。これは、人工知能で最大化しようとする測定基準OfferFitです。
+1. 最大化する**成功指標** (収益、コンバージョン、ARPU、
+または顧客データから測定できる KPIなど) を選択します。これは、人工知能で最大化しようとする測定基準OfferFitです。
 2. テストする**dimensions**を選択します(オファー、件名、クリエイティブ、チャネル、時刻、曜日、頻度など)。
-3. 各ディメンションで使用可能な**オプション**を選択します。たとえば、チャネルディメンションにメール、SMS、およびpush を選択し、度数ディメンションに日単位、週単位、および週単位を選択できます。
+3. 各ディメンションで使用可能な**オプション**を選択します。たとえば、チャネルのディメンションとしてメール、SMS、およびプッシュを選択してから、頻度ディメンションとして毎日、週2回、毎週などを選択できます。
 
 ![of_use_case_example][2]
 
@@ -72,29 +72,29 @@ OfferFitの使用許諾およびユースケースによって、使用するBra
 OfferFit人工知能は、あらゆる顧客の相互アクションから学び、それらのインサイトを翌日の勧告にアプリするだろう。
 
 
-| ユースケース | 目標 | 事前のアプローチ | OfferFit手法 |
+| ユースケース | 目標 | 事前のアプローチ | OfferFit のアプローチ |
 |----------|------|----------------|-------------------|
-| **クロスセルまたはアップセル** | ネットサブスクリプションからの1ユーザー当たり収益最大化 | 年間キャンペーンを実行すると、すべての顧客に次の最上位層プランが提供されます。 | 経験的に、それぞれの顧客に最適なメッセージ、送信時間、割引を発見し、提供する予定がある。どの顧客が飛躍的なオファーを受けやすく、どの顧客がアップグレードに割引や他の奨励金を必要とするかを学ぶ。 |
-| **リニューアル&アンプ;リテンション** | 契約更新を確保し、契約期間と純現在価値(NPV)の両方を最大化する。 | A/Bは手動でテストし、更新を確保するためにかなりの割引を提供します。 | 自動化された実験を利用して、顧客ごとに最高のリニューアルオファーを見つけ、価格感応度が低く、リニューアルにあまり割引を必要としない顧客を特定する。 |
-| **リピート購入** | 購入・買戻し率を最大化する。 | すべての顧客は、Web サイトアカウント(同じケイデンスの同じメール順序など)を作成した後、同じジャーニーを受け取ります。 | 実験を自動化して、それぞれの顧客に最適なメニューアイテムを見つけ、最も効果的な件名、送信時間、および通信頻度を確認します。 |
-| **ウィンバック** | 過去のサブスクライバーに再申請を促すことで、再活性化を高める。 | 高度なA/Bテストとセグメンテーション。 | 自動化された実験を活用して、一度に何千もの変量をテストし、一人ひとりに最適な創造力、伝言、チャネル、ケイデンスを発見する。 |
-| **紹介** | 既設顧客からの営業信用カード照会による新規口座開封の最大化 | すべての顧客 s のメール順序を固定し、顧客集団に最適な送信時間、ケイデンスなどを決定するための広範なA/B テストを行います。 | アイデア l メール、クリエイティブ、送信時刻、信用カードを決定するための実験を自動化し、具体的な顧客を提供します。 |
-| **リード・ナチュアリング&アンプ;コンバージョン** | 増分収益を推進し、顧客ごとに適切な金額を支払う。 | Fac eBookなどのプラットフォームでプライバシーポリシーが変更されると、以前のアプリがパーソナライズされたの有料広告に侵入するのが最後に有効になります。 | ロバストな第一者データを活用して、顧客 Segmentの試乗、入札方法、入札水準、クリエイティブを自動的に試す。 |
-| **ロイヤリティ&アンプ、エンゲージメント** | 顧客 ロイヤルティプログラムへの新規加入者による購買を最大化する。 | 顧客は、アクションsに応じて、一定のメールsを受け取った。たとえば、ロイヤルティプログラム内のすべての新規登録者は同じジャーニーを受け取ります。 | さまざまなメールの提供、クリエイティブ、送信時間、頻度を自動的に試し、それぞれの顧客の購買と再購入を最大化します。 |
+| **クロスセルまたはアップセル** | インターネットサブスクリプションからのユーザーあたりの平均収益 (ARPU) を最大化する。 | すべての顧客に対し次に最も高いティアプランを提供する年間キャンペーンを実行する。 | 顧客ごとに最適なメッセージ、送信時刻、割引、提案プランを経験的に特定し、リープフロッグオファーを受け入れやすい顧客や、アップグレードの際に割引やその他のインセンティブを必要とする顧客を把握する。 |
+| **更新とリテンション** | 契約更新を確保し、契約期間と純現在価値 (NPV)の両方を最大化する。 | AB テストを手動で実施し、更新を確保するために大幅な割引を提示する。 | 自動化された実験を利用して、顧客ごとに最適な更新オファーを特定し、価格にそれほど敏感ではなく、更新に大幅な割引を必要としない顧客を特定する。 |
+| **リピート購入** | 購入率と再購入率を最大化する。 | すべての顧客に対し、Web サイトアカウントの作成後に同じジャーニーが提供される (同じケイデンスでの同じメールシーケンスなど)。 | 実験を自動化して、それぞれの顧客に最適なメニューアイテムを見つけ、最も効果的な件名、送信時刻、およびコミュニケーションの頻度を確認する。 |
+| **ウィンバック** | 以前にサブスクライブしていたユーザーに再度サブスクリプションを促すことで、再アクティベーションを増やす。 | 高度なA/Bテストとセグメンテーション。 | 自動化された実験を利用して、数千個の変数を一括でテストし、顧客ごとに最適なクリエイティブ、メッセージ、チャネル、ケイデンスを特定する。 |
+| **紹介** | 既存の顧客からのビジネスクレジットカード紹介による新規アカウントの開設を最大化する。 | すべての顧客に対する固定のメールシーケンスと、顧客群に対する最適な送信時刻、ケイデンスなどを判断するための大規模な AB テスト。 | 特定の顧客に対して理想的なメール、クリエイティブ、送信時刻、クレジットカードを決定するための実験を自動化する。 |
+| **リードナーチャリングとコンバージョン** | 増分収益を促進し、顧客ごとに適切な金額を支払う。 | Facebook などのプラットフォームでのプライバシーポリシーの変更に伴い、パーソナライズされた有料広告に対する以前のアプローチが最後に有効になります。 | 強固なファーストパーティデータを利用して、顧客セグメント、入札方法、入札レベル、クリエイティブに対する実験を自動的に行う。 |
+| **ロイヤルティとエンゲージメント** | 顧客ロイヤルティプログラムの新規登録者による購入を最大化する。 | 顧客のアクションに対して一定の順序でメールが顧客に送信された。たとえば、ロイヤルティプログラムのすべての新規登録者が同じジャーニーを受け取った。 | 各顧客の購入と再購入を最大化するため、さまざまなメールオファー、クリエイティブ、送信時刻、および頻度で実験を行う。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 
 ## 統合
 
-### ステップ1:Braze での対象オーディエンスの定義
+### ステップ1:Braze でターゲットオーディエンスを定義する
 
-Braze で少なくとも1 つのSegmentを作成して、対象オーディエンスを定義します。このSegmentは、キャンペーンまたはキャンバスを正しいユーザーs に送信するために使用されます。
+Braze で少なくとも1つのセグメントを作成して、ターゲットオーディエンスを定義します。このセグメントは、キャンペーンまたはキャンバスを適切なユーザーに送信するために使用されます。
 
-### ステップ2:API-トリガーのBraze キャンペーンまたはキャンバスを設定し、キャンペーンアセットを作成する(たとえば、HTML テンプレート s、"画像 s) {#step-2}
+### ステップ2:API によってトリガーされる Braze キャンペーンまたはキャンバスを設定し、キャンペーンアセット (HTML テンプレート、イメージなど) を作成する {#step-2}
 
 1. Braze でキャンペーンまたはキャンバスを作成します。OfferFit はこのキャンペーンまたはキャンバスを使用して、定義したオーディエンスから1:1 パーソナライズされたアクティベーションイベントを適切なユーザーs に送信します。 
 2. キャンペーンまたはキャンバスにBraze[コントロールグループ]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign#including-a-control-group)を含めないでください。これにより、OfferFit コントロールグループのみが有効になります。
-3. 寸法に応じて、クリエイティブコンテンツの「リキッドタグ」を設定して、キャンペーンまたはキャンバスにOfferFitの推奨事項をダイナミックな入力できます。OfferFit は、Braze API を介してテンプレートs のリキッドタグs に顧客固有のコンテンツを渡します。
+3. 寸法に応じて、クリエイティブコンテンツの「リキッドタグ」を設定して、キャンペーンまたはキャンバスにOfferFitの推奨事項をダイナミックな入力できます。OfferFit は、Braze API を介して顧客固有のコンテンツをテンプレートの Liquid タグに渡します。
 
 ### ステップ3:OfferFit ユースケース設定をアップデートして、Brazeアクティベーションイベントを調整します
 
@@ -102,13 +102,13 @@ OfferFitのネイティブアクティベーションインテグレーション
 
 ## カスタマイズ
 
-Braze でのアクティベーションイベントの編成に加えて、OfferFit では、Brazeから顧客 プロファイル(非PII)およびエンゲージメントデータを取得するためのデータインテグレーション機能を、使用可能なAPI エンドポイントで提供しています。
+OfferFit は、Braze でのアクティベーションイベントのオーケストレーションの他に、データ統合機能を提供します。このデータ統合機能により、利用可能な API エンドポイントを介して顧客プロファイル (非PII) とエンゲージメントデータを Braze から取得できます。
 
 ## この統合の使用
 
 OfferFitが設定されると、自動化された実験プラットフォームは、対象オーディエンスのユーザーごとに、自動的に1:1 パーソナライズされたアクティベーションイベントをBrazeに送信します。これらのアクティベーションイベントは、[ ステップ 2](#step-2) で設定したBraze キャンペーンs またはキャンバスを介してトリガーされます。
 
-Braze で使用可能な分析情報に加えて、OfferFit は、自己学習AI 機能を使用してOfferFit が検出した顧客 インサイトをマーケター s が探索できるようにする包括的なレポートリングレイヤーを提供します。
+OfferFit では、Braze で利用可能な分析データに加えて包括的なレポートレイヤーを提供しています。このレイヤーにより、マーケターは自己学習 AI 機能により OfferFit で検出された顧客のインサイトを検討できるようになります。
 
 
 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/peak.md b/_lang/ja/_partners/message_personalization/dynamic_content/peak.md
index c2d7df15c59..87356b4fe83 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/peak.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/peak.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Peak
 article_title: Peak
-description: "このリファレンス記事では、Brazeと意思決定インテリジェンスプラットフォームであるPeakとの提携について説明しています。これにより、顧客の行動やインタラクションに基づいた予測離脱確率と属性を取得し、それらをBrazeにインポートして顧客セグメンテーションとターゲティングに使用することができます。"
+description: "このリファレンス記事では、Braze と Peak のパートナーシップについて説明します。この Peak は意思決定インテリジェンスプラットフォームであり、顧客の行動とインタラクションに基づいて予測される解約確率と属性を取得し、それらを Braze にインポートして顧客セグメンテーションとターゲット設定に使用できます。"
 alias: /partners/Peak/
 page_type: partner
 search_tag: Partner
@@ -12,33 +12,33 @@ search_tag: Partner
 
 > [ピーク](https://platform.peak.ai/)、意思決定インテリジェンスプラットフォームは、意思決定インテリジェンスがビジネスの意思決定を強化し、収益と利益を増加させるためのAIの商業的応用であるエンドツーアウトカムシステムです。
 
-BrazeとPeakのパートナーシップにより、顧客の行動やインタラクションに基づいた予測離脱確率と属性を取得し、それらをBrazeにインポートして顧客セグメンテーションとターゲティングに使用することができます。 
+Braze と Peak のパートナーシップにより、顧客の行動とインタラクションに基づいて予測される解約確率と属性を取得し、それらを Braze にインポートして顧客セグメンテーションとターゲット設定に使用できます。 
 
 ## 前提条件
 
-出発点として、PeakテナントはPeakとBrazeの間の統合をホストする必要があります。これは通常、Peak顧客のオンボーディング中に作成されます。さらに、意思決定インテリジェンスソリューションが最初に必要です。これは、後でBrazeに統合されるAI駆動の出力を生成するためです。
+出発点として、PeakテナントはPeakとBrazeの間の統合をホストする必要があります。これは通常、Peak の顧客の登録中に作成されます。さらに、意思決定インテリジェンスソリューションが最初に必要です。これは、後でBrazeに統合されるAI駆動の出力を生成するためです。
 
 | 要件 | 説明 |
 | ----------- | ----------- |
 | ピークテナント | 統合をホストおよびオーケストレーションするには、テナントとして知られるPeakプラットフォームのインスタンスが必要です。 |
-| 意思決定インテリジェンスソリューション | PeakとBrazeの統合はAI駆動の出力に基づいているため、テナント内にPeakまたは顧客が展開したソリューションが必要です。 |
+| 意思決定インテリジェンスソリューション | Peak と Braze の統合は AI を使用した出力に基づいているため、テナント内に Peak または顧客が導入したソリューションが必要です。 |
 | Braze REST API キー | `users.track`の権限を持つBraze REST APIキー。<br><br>これはBrazeダッシュボードの**設定** > **APIキー**から作成できます。 |
 
 ## 統合
 
-ピークソリューション顧客インテリジェンスは、顧客の行動と相互作用に基づいて将来の属性を予測するモデルを利用します。これらの属性はPeak内に保存され、顧客の解約確率を含む予測セグメンテーションを生成するために使用できます。これらの予測属性の更新は、設定可能なリズム（毎日または毎週）に基づいて行われます。
+Peak ソリューションの顧客インテリジェンスはモデルを活用して、顧客行動とインタラクションに基づいてさまざまな将来的な属性を予測します。これらの属性は Peak 内に保存され、顧客の解約率などの予測セグメンテーションを生成するために使用できます。これらの予測属性の更新は、設定可能なリズム（毎日または毎週）に基づいて行われます。
 
 ### ステップ1:モデルを実行して顧客を抽出する
 
-AIモデルの実行と予測顧客属性の再計算の結果として統合がトリガーされます。これらのAI出力はPeak内に保存され、属性が新しいステータスまたは値で更新されたときも含まれます。
+この統合は、AI モデルの実行と予測顧客属性の再計算によってトリガーされます。これらのAI出力はPeak内に保存され、属性が新しいステータスまたは値で更新されたときも含まれます。
 
-属性が更新された時期に基づいて、PeakとBrazeの間の最後の同期以降に更新された予測属性を持つすべての顧客を収集するための選択が行われます。
+属性が更新されたタイミングに基づいて、Peak と Braze の最終同期以降に予測属性が更新されているすべての顧客を収集するための選択が行われます。
 
 ### ステップ2:更新 Braze
 
 更新された顧客と関連する属性を使用して、Peakは[`/user/track`エンドポイント][1]を使用してこれらをBrazeにPOSTし、[一括]({{site.baseurl}}/api/endpoints/user_data/post_user_track/#making-bulk-updates)ヘッダーを利用します。
 
-APIからの成功したステータスコードを受信すると、PeakはPeakとBraze間の成功した同期を記録します。
+Peak は API から成功ステータスコードを受信すると、Peak と Braze の間での同期の成功を記録します。
 
 ### ステップ3:この統合を使用する
 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/personalize.md b/_lang/ja/_partners/message_personalization/dynamic_content/personalize.md
index 87f09102252..509f525cb15 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/personalize.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/personalize.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Personalize.AI
 article_title: Personalize.AI
-description: "この参考記事では、Brazeと、パーソナライズされたレコメンデーションから収益成長を促進するAIベースのSaaSビジネスプラットフォームであるPersonalize.AIの提携について概説している。"
+description: "このリファレンス記事では、Braze と Personalize.AI のパートナーシップについて説明します。Personalize.AI は、パーソナライズされたレコメンデーションによる収益成長を促進する AI ベースの SaaS ビジネスプラットフォームです。"
 alias: /partners/personalize/
 page_type: partner
 search_tag: Partner
@@ -9,9 +9,9 @@ search_tag: Partner
 
 # Personalize.AI
 
-> [Personalize.AI](https://www.zs.com/solutions/artificial-intelligence-and-analytics/personalize-ai/) はBrazeと提携し、Brazeを通じて送信されるパーソナライズされたメッセージやオファーを配信することで、収益の増加を生み出している。 
+> [Personalize.AI](https://www.zs.com/solutions/artificial-intelligence-and-analytics/personalize-ai/) は Braze と連携し、Braze から送信されるパーソナライズされたメッセージやオファーを配信することで、収益の増加を実現します。 
 
-BrazeとPersonalize.AI の統合により、Personalize.AI からBrazeプラットフォームにデータをエクスポートし、メッセージのパーソナライズとターゲティングを行うことができる。
+Braze とPersonalize.AI の統合により、メッセージのパーソナライゼーションとターゲティングのために Personalize.AI から Braze プラットフォームにデータをエクスポートできます。
 
 ## 前提条件
 
@@ -19,55 +19,55 @@ BrazeとPersonalize.AI の統合により、Personalize.AI からBrazeプラッ
 | ----------- | ----------- |
 | Personalize.AI インスタンス | このパートナーシップを利用するには、Personalize.AI インスタンスが必要である。 |
 | Braze REST API キー | すべての権限を持つBraze REST APIキー。<br><br>これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントは、[インスタンスのBraze URLに][1]依存する。 |
+| Braze RESTエンドポイント | RESTエンドポイントのURL。エンドポイントはインスタンスの [Braze URL][1] に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
 * 柔軟な層別化を含むテストを展開し、顧客からのフィードバックから結果を導き出す。
 * 待遇、タイミング、内容など、アイテムやオファーに対してパーソナライズされた推奨を提供する。
-* Brazeを通じて、優先順位をつけた目標を特定し、最適な視聴者をターゲットにする。
+* 優先する目標を特定し、Braze を通じて最適なオーディエンスをターゲティングする
 * 既に利用されなくなったユーザーを再び獲得する機会を特定する
 * ジオロケーションデータを活用し、新規オープン店舗に適した顧客を見つける
 * そっくりさんモデリングを使って、新規ユーザー向けの限られた利用可能なデータを構築し、最も関連性の高いレコメンデーションとマッチングさせる。
-* 顧客のライフサイクル全体を通して、顧客を惹きつける適切な方法を特定する 
-* 解約の可能性について顧客をプロアクティブに評価し、リスクスコアを割り当てて、解約の早期指標を見つける。
+* 顧客のライフサイクル全体を通して顧客に関与するための適切な方法を特定する 
+* 解約の可能性について顧客を事前対応的に評価し、リスクスコアを割り当て、解約の早期徴候を見つける
 * パーソナライズされた介入策で顧客をターゲットにし、非活動的になるのを防ぐ
 
 ## 統合
 
-### でBrazeとの接続を設定する。 Personalize.AI
+### Personalize.AI で Braze との接続を設定する
 
-1. Personalize.AI で、Personalize.AI インスタンスの「**Operationalization」の**下にある**「Integrations」**タブに移動する。
-2. **Brazeを**クリックする。 
+1. Personalize.AI で、Personalize.AI インスタンスの \[**Operationalization**] にある \[**Integrations**] タブに移動します。
+2. \[**Braze**] をクリックします。 
 3. Brazeとの統合を設定する。
-    * **コネクション名だ：**コネクションに名前をつける。これが、Personalize.AI であなたの統合が参照される方法である。
-    * **同期周波数：**同期頻度は、Personalize.AI 、Brazeにデータをエクスポートする頻度を制御する。**毎日**、**毎週**、**毎月を**選択する。 
-    * **APIキー：**BrazeのAPIキーを追加する。
-    * **APIのURL：**Braze RESTエンドポイントURLを追加する。
-4. Brazeにデータを**エクスポート**するには**EXPORTを**クリックする。
+    * **Connection Name:**コネクションに名前をつける。これは、Personalize.AI で統合を参照する方法です。
+    * **同期周波数：**同期の頻度により、Personalize.AI が Braze にデータをエクスポートする頻度が制御されます。\[**Daily**]、\[**Weekly**]、\[**Monthly**.] のいずれかを選択します。 
+    * **API Key:**BrazeのAPIキーを追加する。
+    * **API URL:**Braze RESTエンドポイントURLを追加する。
+4. \[**EXPORT**] をクリックして Braze にデータをエクスポートします。
 
 いったんデータがエクスポートされると、Personalize.AI 、統合時に設定した同期頻度によって決められた間隔で、Brazeにデータを渡し続ける。
 
 ## この統合を使う
 
-Personalize.AI パーソナライズされたターゲティングに使用される識別子をBrazeにエクスポートする。これらのカスタム属性は、各顧客のタイミング、内容、待遇、オファーを示す。Personalize.AI は、識別子として`external_id` の使用をサポートしている。
+Personalize.AI により、パーソナライズされたターゲティングに使用される識別子が Braze にエクスポートされます。これらのカスタム属性は、各顧客のタイミング、内容、待遇、オファーを示します。統合によっては、フィールドを顧客のプロファイルに保存する代わりに、イベントとして渡すか、[コネクテッドコンテンツ API][2] に取り込むことができます。Personalize.AI では、`external_id` を識別子として使用することがサポートされています。
 
-Brazeにインポートされたデータ属性は、一貫した用語に従って、Canvasesで使用するために直感的に命名される。例えば、Personalize.AI の属性`C402_Target_Variant` は、`"P.AI_Model_Treatment"` としてBrazeにエクスポートされる。Personalize.AI 、エクスポートされる属性は、既存の属性やトラッキングに干渉しないように設計されている。これらの属性は継続的に検証され、自信を持って参照できることが確認されている。 
+Braze にインポートされたデータ属性には、一貫した用語に従って、キャンバスで使用するために直感的な名前が指定されます。たとえば Personalize.AI の属性 `C402_Target_Variant` は、Braze に `"P.AI_Model_Treatment"` としてエクスポートされます。Personalize.AI からエクスポートされる属性は、既存の属性や使用状況のトラッキングを妨げないように設計されています.。これらの属性は継続的に検証されるため、確実に参照できます。 
 
-例えば、解約に焦点を当てたキャンバスの例に関連する顧客属性のセットである。
+たとえば、解約に焦点を当てたキャンバスの例に関連する顧客属性のセットを次に示します。
 
-| Personalize.AI 属性 | 価値 |
+| Personalize.AI 属性 | 値 |
 | ----------- | ------------- | 
 | `Customer_ID` | 12345 |
 | `Target_Canvas` | C4 |
-| `Target_Objective` |  "チャーン_ミティゲーション" |
+| `Target_Objective` |  "Churn_Mitigation" |
 | `C4_Target_Date` | 3/1/2023 |
 | `C4_Target_Variant` | 治療 |
 | `C4_Treatment` | "P.AI_Model" |
 | `C4_Offer_Value` | $3 |
-| `C4_Item_Recom` | 「シーザーサラダ |
-| `C4_Subject_Line` | 「寂しいよ |
+| `C4_Item_Recom` | "Caesar Salad" |
+| `C4_Subject_Line` | "We miss you" |
 {: .reset-td-br-1 .reset-td-br-2}
 
 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/playable.md b/_lang/ja/_partners/message_personalization/dynamic_content/playable.md
index 15b86bd3c02..99702ae2872 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/playable.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/playable.md
@@ -1,7 +1,7 @@
 ---
 nav_title: "Playable"
 article_title: Playable
-description: "このリファレンス記事では、Braze とPlayable の連携について説明します。この動画 プラットフォームでは、Braze メール キャンペーンs に動画内容を追加できます。"
+description: "このリファレンス記事では、Braze と Playable のパートナーシップについて説明します。Playable は動画プラットフォームであり、動画コンテンツを Braze メールキャンペーンに追加できます。"
 alias: /partners/playable/
 page_type: partner
 search_tag: Partner
@@ -12,28 +12,28 @@ search_tag: Partner
 
 > [Playable][1] では、自動再生動画をBraze メール キャンペーンs に追加できます。
 
-BrazeとPlayableインテグレーションにより、最高のコンテンツ(高品質の動画)を最高のオーディエンス(メール)に届けることができ、受信トレイ内で自動的に再生される刺激的な高品質のコンテンツで、クリックスルーとポストクリックのメトリクスを向上させることができます。
+Braze と Playable の統合により、最高のコンテンツ( 高品質動画) を最高のオーディエンスに配信でます (メール)。受信トレイで自動的に再生されるエキサイティングな高品質のコンテンツにより、クリックスルーとポストクリックの指標が向上します。
 
 ## 前提条件
 
 | 要件 | 説明 | 
 | ----------- | ----------- |
-| Playable会計 | この提携の前進タグeを考慮するには、Playableな考慮が必要である。Playable アカウントをまだ持っていない場合は、[ここで][signup] にサインアップします。
-ビデオコンテンツ | Fac eBook、Ins タグ ram、YouTube、X (旧Twitter)、TikTokなどのWeb サイトから動画URLをPlayableしたり、提供したりするための読み込む 動画。 |
+| Playable アカウント | このパートナーシップを活用するには、Playable アカウントが必要です。Playable アカウントをまだお持ちでない場合は、[こちら][signup]からご登録ください。
+ビデオコンテンツ | 動画ファイルを Playable にアップロードするか、または Facebook、Instagram、YouTube、X (旧 Twitter)、TikTok などの Web サイトの動画 URL を指定します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 実装
 
-### ステップ1:動画をPlayableに追加する
+### ステップ1:動画を Playable に追加する
 
-Playable プラットフォームでは、Fac eBook、Ins タグ ram、YouTube、X (旧Twitter)、TikTok などの動画のURL を指定して、s をアップロード 動画または追加します。
+Playable プラットフォームで、動画ファイルをアップロードするか、または Facebook、Instagram、YouTube、X (旧 Twitter)、TikTok などの動画の URL を指定して動画を追加します。
 
 ### ステップ2:埋め込みコードをPlayableからコピーする
 
-アップロードが「ed」になると、Playableはコードを生成します。このコードは、Braze キャンペーンに挿入すると、メールに動画が埋め込まれ、開封が鳴ったときに自動再生されます。メールが開封されている場合、Playableサーバーは、メール クライアント、機器、スクリーンサイズ、およびネットワーク状況に応じて、最適な動画を提供します。
+アップロードが完了すると、Playable によりコードが生成されます。このコードが Braze キャンペーンに挿入されると、メールに動画が埋め込まれ、メールを開封すると自動再生されます。メールが開封されると、メールクライアント、デバイス、スクリーンサイズ、およびネットワーク状況に応じて最適な動画が Playable サーバーから配信されます。
 
 {% alert tip %}
-ビデオは、iPhone Mail、Gmail、Apple Mail、Outlook for iOS、Outlook for Android、Outlook for Mac、Outlook 365 for Windowsなど、受信トレイの98%以上で自動再生されます。従来のWindows版のOutlookのユーザには、代わりにスタティック"画像が表示されます。
+動画は、iPhone Mail、Gmail、Apple Mail、Outlook for iOS、Outlook for Android、Outlook for Mac、Outlook 365 for Windows など、受信トレイの 98% 以上で自動再生されます。従来の Outlook for Windows をご利用の場合は、動画の代わりに静止画像が表示されます。
 {% endalert %}
 
 ### ステップ3:埋め込みコードをBrazeに貼り付けます
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/sheetlabs.md b/_lang/ja/_partners/message_personalization/dynamic_content/sheetlabs.md
index d72b6d7eb35..39db67be981 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/sheetlabs.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/sheetlabs.md
@@ -10,7 +10,7 @@ search_tag: Partner
 
 # Sheetlabs
 
-> [Sheetlabsは][1]、スプレッドシートをパワフルで文書化されたAPIに変えることを可能にするプラットフォームだ。Google SheetsやExcelからデータをインポートしてAPI化し、そのAPIをBrazeなどの他のアプリケーションで使うことができる。
+> [Sheetlabs][1] は、スプレッドシートを、強力で明確に文書化された API に変換できるプラットフォームです。Google SheetsやExcelからデータをインポートしてAPI化し、そのAPIをBrazeなどの他のアプリケーションで使うことができる。
 
 SheetlabsとBrazeの統合により、[Connected Contentを][2]活用して、BrazeのマーケティングキャンペーンにSheetlabsのAPIを含めることができる。これは、Googleスプレッドシート（マーケティングチームが直接更新する）とBrazeテンプレートの橋渡しによく使われる。これにより、翻訳やカスタム属性の大規模なセットなど、Brazeテンプレートでより多くのことを実現できる。
 
@@ -18,7 +18,7 @@ SheetlabsとBrazeの統合により、[Connected Contentを][2]活用して、Br
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| シートラボアカウント | このパートナーシップを利用するには、[Sheetlabsのアカウントが][1]必要である。 |
+| Sheetlabs アカウント | このパートナーシップを活用するには、[Sheetlabs アカウント][1]が必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
@@ -26,19 +26,19 @@ SheetlabsとBrazeの統合により、[Connected Contentを][2]活用して、Br
 BrazeとSheetlabsの統合により、以下のユースケースを実現できる：
 
 1. **マーケターアクセスとBrazeキャンペーンアクセスを分離する**：チームによっては、すべてのスタッフにBrazeのテンプレートやコンテンツを直接設定するためのアクセス権を与えたくない場合もある。その代わり、スタッフはスプレッドシートでマーケティング・コンテンツを更新することを望んでいる。SheetlabsはスプレッドシートとBrazeの橋渡しをし、リアルタイムで更新できる。
-2. **翻訳する**：Brazeのテンプレートはネイティブに翻訳をサポートしていない。複数の言語をサポートしたい場合は、複数のテンプレートを作成する必要がある。SheetlabsとBrazeを併用することで、一つのBrazeテンプレートを多言語に翻訳することができる。
-3. **カスタム属性を拡張する**：Brazeには、設定可能なカスタム属性が一定数用意されている。SheetlabsをBrazeと併用することで、この最初の割り当てを超えてカスタム属性を追加することができる。
+2. **翻訳**:Brazeのテンプレートはネイティブに翻訳をサポートしていない。複数の言語をサポートしたい場合は、複数のテンプレートを作成する必要がある。Sheetlabs と Braze を併用することで、1つの Braze テンプレートを多言語に翻訳できます。
+3. **カスタム属性の拡張**:Brazeには、設定可能なカスタム属性が一定数用意されている。SheetlabsをBrazeと併用することで、この最初の割り当てを超えてカスタム属性を追加することができる。
 
-これらの使用例の詳細については、[Sheetlabsを][3]参照のこと。
+これらのユースケースの詳細については、[Sheetlabs][3] を参照してください。
 
 ## 統合
 
 ### ステップ1:スプレッドシートをSheetlabsにインポートする
 
-Sheetlabsでは、エクセルのスプレッドシートをアップロードするか、グーグルアカウントをリンクしてグーグルシートをインポートする。 
+Sheetlabs では、Excel スプレッドシートをアップロードするか、Google アカウントをリンクして Google スプレッドシートをインポートします。 
 
 - エクセルのスプレッドシートをインポートするには、メニューバーの「**Data Tables**」をクリックし、「**Import from CSV/Excel**」をクリックする。
-- Google Sheetsからインポートするには、メニューバーの**Data Tablesを**クリックし、次に**Import from Googleを**クリックする。その後、グーグルのログイン認証情報を入力し、シートをインポートする必要がある。
+- Google スプレッドシートからインポートするには、メニューバーの \[**Data Tables**] をクリックし、次に \[**Import from Google**] をクリックします。その後、Google ログイン認証情報を入力してスプレッドシートをインポートする必要があります。
 
 また、Google Sheetを同期させておくこともできる。つまり、SheetlabsはGoogle Sheetに変更があった場合、自動的に最新のデータを取得する。
 
@@ -46,13 +46,13 @@ BrazeのユーザーIDをスプレッドシートに含めるか、後で検索
 
 ### ステップ2:SheetlabsでAPIを作成する
 
-次に、Sheetlabsで**API > Create APIと**進み、APIに名前を付ける。おそらく、BrazeユーザーIDのようなスプレッドシートからのルックアップフィールド経由でのクエリーを許可したいだろう。
+次に Sheetlabs で **\[APIs] > \[Create API]** に移動し、API に名前を付けます。おそらく、BrazeユーザーIDのようなスプレッドシートからのルックアップフィールド経由でのクエリーを許可したいだろう。
 
-この時点で、以下のようなリンクでAPIにアクセスできるはずだ：<br> [`https://sheetlabs.com/ACME/email1_translations?country=en`][4].
+この時点で、以下のようなリンクでAPIにアクセスできるはずだ：<br> [`https://sheetlabs.com/ACME/email1_translations?country=en`][4]。.
 
 ### ステップ3:Braze Connected ContentでAPIを使用する
 
-これでAPIにアクセスできるようになったので、Connected Contentの呼び出しでAPIを使うことができる。以下は、翻訳テンプレートの例である：
+API にアクセスできるようになったので、コネクテッドコンテンツ呼び出しで API を使用できます。以下は、翻訳テンプレートの例である：
 
 {% raw %}
 ```js
@@ -65,7 +65,7 @@ BrazeのユーザーIDをスプレッドシートに含めるか、後で検索
 {% endraw %}
 
 {% alert tip %}
-Sheetlabsとの統合に関する詳しい例やアドバイスについては、[Sheetlabsのドキュメントを](https://app.sheetlabs.com/docs/producers/braze/)参照されたい。
+Sheetlabs との統合に関する詳しい例やアドバイスについては、[Sheetlabs のドキュメント](https://app.sheetlabs.com/docs/producers/braze/)を参照してください。
 {% endalert %}
 
 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/storyly.md b/_lang/ja/_partners/message_personalization/dynamic_content/storyly.md
index 145632251c6..1e6d998155a 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/storyly.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/storyly.md
@@ -1,18 +1,18 @@
 ---
-nav_title: ストーリー
-article_title: ストーリー
-description: "この参考記事では、Brazeと軽量SDKであるStorylyのパートナーシップについて概説しており、アプリ所有者はセグメントを絞り込み、より多くのファーストパーティデータをBrazeに供給することができる。"
+nav_title: Storyly
+article_title: Storyly
+description: "このリファレンス記事では、Braze と Storyly のパートナーシップについて説明します。Storyly は、アプリオーナーがセグメントを絞り込み、より多くのファーストパーティデータを Braze にフィードできるようにする軽量 SDK です。"
 alias: /partners/storyly/
 page_type: partner
 search_tag: Partner
 
 ---
 
-# ストーリー
+# Storyly
 
-> [Storylyは](https://www.storyly.io/)、あなたのアプリやウェブサイトにストーリーをもたらす軽量SDKだ。直感的なデザインスタジオ、洞察に満ちた分析、シームレスな接続性を備えたStorylyは、視聴者の体験を豊かにする強力なツールだ。 
+> [Storyly](https://www.storyly.io/) は、アプリや Web サイトにストーリーをもたらす軽量 SDK です。直感的なデザインスタジオ、洞察に満ちた分析、シームレスな接続性を備えたStorylyは、視聴者の体験を豊かにする強力なツールだ。 
 
-BrazeとStorylyの統合により、BrazeのセグメントをStorylyプラットフォームのオーディエンスとして使うことができる。この統合によって、あなたは次のことができる：
+Braze と Storyly の統合により、Braze のセグメントを Storyly プラットフォームでオーディエンスとして使用できます。この統合により、次のことが可能になります。
 - 特定のストーリーを持つセグメントをターゲットにする
 - ユーザー属性を使ってストーリー・コンテンツをパーソナライズする
 
@@ -20,8 +20,8 @@ BrazeとStorylyの統合により、BrazeのセグメントをStorylyプラッ
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| ストーリーリー・アカウント | このパートナーシップを利用するには、Storylyのアカウントが必要である。 |
-| ストーリーリーSDK | [Storyly SDKを](https://integration.storyly.io/)インストールする必要がある。 |
+| Storyly アカウント | このパートナーシップを活用するには、Storyly アカウントが必要です。 |
+| Storyly SDK | [Storyly SDK](https://integration.storyly.io/)をインストールする必要があります。 |
 | Braze REST API キー | 以下の権限を持つBraze REST APIキー。 <br><br> `users.export.ids`<br> `users.export.segments`<br> `segments.list`<br> `segments.details`<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 | Braze RESTエンドポイント | [RESTエンドポイントのURL][1]。エンドポイントは、インスタンスのBraze URLに依存する。 |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -32,8 +32,8 @@ BrazeとStorylyの統合により、アプリのオーナーはBrazeの全セグ
 
 一般的な使用例には以下のようなものがある：
 
-__Storylyのターゲット・ブレイズ・セグメント__<br>統合が完了したら、Brazeセグメントに基づいてStorylyオーディエンスを作成できる。これは、人口統計学的または行動学的セグメントである可能性がある。例えば、特定の場所に住んでいるユーザー、アプリで特定のアクションを起こしたユーザー、特定のストーリーのある特定の商品に興味があるユーザーなどをターゲットにすることで、コンバージョンを高めることができる。<br>
-__ユーザー属性でパーソナライズされたストーリー__<br>Brazeのユーザー属性はStorylyでも使用でき、動的なストーリーを生成することができる。これには、ユーザーの名前、バスケット内の商品、あるいはお気に入り商品などが含まれ、ユーザーにユニークなパーソナライズされたストーリーを提供することができる。パーソナライゼーションは、ストーリーのコンバージョン率とストーリー全体のエンゲージメント率を高めるのに役立つ。
+__Storyly で Braze セグメントをターゲットにする__<br>統合が完了したら、Brazeセグメントに基づいてStorylyオーディエンスを作成できる。これは、デモグラフィックセグメントまたは行動セグメントです。例えば、特定の場所に住んでいるユーザー、アプリで特定のアクションを起こしたユーザー、特定のストーリーのある特定の商品に興味があるユーザーなどをターゲットにすることで、コンバージョンを高めることができる。<br>
+__ユーザー属性でパーソナライズされたストーリー__<br>Brazeのユーザー属性はStorylyでも使用でき、動的なストーリーを生成することができる。これには、ユーザーの名前、買い物かごに入っている製品、お気に入りの製品などを含めることができ、独自のパーソナライズされたストーリーをユーザーに提供できます。パーソナライゼーションは、ストーリーのコンバージョン率とストーリー全体のエンゲージメント率を高めるのに役立つ。
 
 ## データ・エクスポートの統合
 
@@ -41,18 +41,18 @@ Braze Storylyの統合については、以下のビデオで説明されてい
 
 {% multi_lang_include video.html id="3-OEqQs48Zw" source="youtube" %}
 
-Storylyインテグレーションがカスタムパラメータを保持していることを確認する。これらのパラメータは、Braze`external id` のユーザー・プロパティと一致する。ここでは、[iOS](https://integration.storyly.io/ios/personalization-customaudience.html)、[Android](https://integration.storyly.io/android/personalization-customaudience.html)、[React Native](https://integration.storyly.io/react-native/personalization-customaudience.html)、[Flutter](https://integration.storyly.io/flutter/personalization-customaudience.html)、[Web](https://integration.storyly.io/web/personalization-customaudience.html)用のカスタム・パラメーターの実装について説明する。
+Storylyインテグレーションがカスタムパラメータを保持していることを確認する。これらのパラメーターは、Braze `external id` ユーザープロパティに対応します。ここでは、[iOS](https://integration.storyly.io/ios/personalization-customaudience.html)、[Android](https://integration.storyly.io/android/personalization-customaudience.html)、[React Native](https://integration.storyly.io/react-native/personalization-customaudience.html)、[Flutter](https://integration.storyly.io/flutter/personalization-customaudience.html)、[Web](https://integration.storyly.io/web/personalization-customaudience.html)用のカスタム・パラメーターの実装について説明する。
 
-詳細は[Storylyの](https://docs.storyly.io/page/connect-your-braze-audiences-with-storyly)ドキュメントを参照することもできる。
+詳細については、[Storyly](https://docs.storyly.io/page/connect-your-braze-audiences-with-storyly) のドキュメントを参照してください。
 
 ### ステップ1:Storylyダッシュボードで統合を設定する
 
-**Storylyダッシュボード＞設定＞統合＞Brazeと接続で**統合を作成する。ここでは、Braze REST APIキーとBraze RESTエンドポイントが必要である。 
+**Storylyダッシュボード > \[Settings] > \[Integrations] > \[Connect with Braze]** で統合が作成されます。ここでは、Braze REST APIキーとBraze RESTエンドポイントが必要である。 
 
 ### ステップ2:セグメントを取得する 
 
-次に、Brazeセグメントを使ってStorylyオーディエンスを作成する。これは、**Storylyダッシュボード＞設定＞オーディエンス＞新規オーディエンス＞Brazeでオーディエンスを作成で**作成できる。
+次に、Braze セグメントを使用して Storyly オーディエンスを作成できます。これは、**Storylyダッシュボード > \[Settings] > \[Audiences] > \[New Audience] > \[Create Audience with Braze]** で作成できます。
 
-ここには2つの同期オプションがある。特定のキャンペーン・ストーリーには**1回限りの同期を**、長期的なストーリーには**毎日の同期を**選択する。
+ここには2つの同期オプションがあります。特定のキャンペーン・ストーリーには**1回限りの同期を**、長期的なストーリーには**毎日の同期を**選択する。
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/stylitics.md b/_lang/ja/_partners/message_personalization/dynamic_content/stylitics.md
index 5a184a320af..c9af3a716a1 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/stylitics.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/stylitics.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Stylitics
 article_title: Stylitics
-description: "このリファレンス記事では、Braze と Stylitics の提携について説明しています。Stylitics はクラウドベースの SaaS プラットフォームで、既存のメールキャンペーンを魅力的で関連性の高いバンドルコンテンツで強化し、パーソナライズされたカスタマーエクスペリエンスを創出します。"
+description: "このリファレンス記事では、Braze と Stylitics のパートナーシップについて説明します。Stylitics はクラウドベースの SaaS プラットフォームで、既存のメールキャンペーンを、魅力的で関連性の高いバンドルコンテンツで強化し、パーソナライズされたカスタマーエクスペリエンスを創出できます。"
 alias: /partners/stylitics/
 page_type: partner
 search_tag: Partner
@@ -12,7 +12,7 @@ search_tag: Partner
 
 > [Stylitics](https://stylitics.com/)は、小売業者が視覚コンテンツを大規模に自動化および配信するためのクラウドベースのSaaSプラットフォームです。Styliticsのバンドルは、製品を文脈化することでインスピレーションを与え、購入の自信を高め、エンゲージメントを増加させ、最終的には平均注文額とコンバージョン率を向上させます。
 
-あなたのBrazeとStyliticsの統合により、魅力的で関連性のあるバンドルコンテンツを使用して既存のメールキャンペーンを強化し、パーソナライズされたカスタマーエクスペリエンスを創造することができます。
+Braze と Stylitics の統合により、既存のメールキャンペーンを、魅力的で関連性の高いバンドルコンテンツで強化し、パーソナライズされたカスタマーエクスペリエンスを創出できます。
 
 ![][0]{: style="max-width:60%;"}
 
@@ -20,14 +20,14 @@ search_tag: Partner
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| スタイリティクスアカウント | このパートナーシップを利用するには、[Stylitics](https://stylitics.com/)アカウントが必要です。 |
+| Stylitics アカウント | このパートナーシップを利用するには、[Stylitics](https://stylitics.com/)アカウントが必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
 次に、一般的なトリガーメールプログラムの例をいくつか示します。
 - 放棄カートメール 
-- 放棄された閲覧メール 
+- 閲覧放棄メール 
 - 配送確認メール
 - 購入後のメール 
 
@@ -35,11 +35,11 @@ search_tag: Partner
 
 Styliticsは、この統合のためのバンドルデータを提供します。お客様のメールサービスプロバイダーは、Styliticsバンドルを含むメールテンプレートを作成または更新できます。Styliticsは、メールのレイアウトやデザインを変更することはできません。 
 
-1. バンドルをメールに統合します。メールサービスプロバイダー (ESP) は位置とカスタマイズを決定します。
-2. メールサービスプロバイダー (ESP)は、トリガーメールコードを更新してStyliticsコンテンツを含めるようにします。
-3. メールサービスプロバイダー (ESP) は、更新されたトリガーシリーズをテスト、プレビュー、および開始します。 
+1. バンドルをメールに統合します。メールサービスプロバイダー (ESP) により位置とカスタマイズが決定します。
+2. メールサービスプロバイダー (ESP) により、Stylitics コンテンツを組み込むためにメールコードが更新されます。
+3. メールサービスプロバイダー (ESP) により、更新トリガーシリーズがテスト、プレビュー、および開始されます。 
 
-Styliticsはアイテムのバンドルデータのみを提供します。あなたとメールサービスプロバイダー (ESP) の間で、ユーザーデータを持ち、ユーザーに送信するためにStyliticsバンドルデータをプラグインできます。
+Styliticsはアイテムのバンドルデータのみを提供します。お客様とメールサービスプロバイダー (ESP) の間にはユーザーデータがあり、ユーザーに送信する Stylitics バンドルデータを組み込むことができます。
 
 ## データ交換
 
@@ -47,44 +47,44 @@ Styliticsはアイテムのバンドルデータのみを提供します。あ
 
 ### 1\.APIアプローチ（推奨）
 
-あなたまたはあなたのメールサービスプロバイダー (ESP) は、アイテムごとにAPIコールを行い、バンドルデータをメールに入力できます。Styliticsは、すぐに使用できるAPIを使用してAPIコールを行うことをお勧めします。
+お客様またはお客様のメールサービスプロバイダー (ESP) は、アイテムごとに API 呼び出しを実行して、バンドルデータをメールに取り込みます。Stylitics では、すぐに使用できる Stylitics の API を使用して API 呼び出しを実行することが推奨されています。
 
 {% alert note %}
-Stylitics が実行する A/B テストを実行する場合、`styliticsCID` および `styliticsoverride` パラメーターを Stylitics アイテムの PDP URL に追加する必要があります。ユーザーがメールでクリックします。
+Stylitics により実行される AB テストを行う場合、ユーザーがメールでクリックする Stylitics アイテムの PDP URL に、`styliticsCID` および `styliticsoverride` パラメーターを追加する必要があります。
 <br><br>
-例えば、{% raw %}`&styliticsoverride=001?styliticsCID=email[clientname]`{% endraw %}
+たとえば {% raw %}`&styliticsoverride=001?styliticsCID=email[clientname]`{% endraw %} などです。
 {% endalert %}
 
 ### 2\.フラットファイルアプローチ
-あなたまたはあなたのメールサービスプロバイダー (ESP) は、フラットファイル内のアイテムのバンドルデータを参照して、メールにバンドルデータを入力できます。StyliticsはバンドルデータをCSV、TXT、またはXML形式にフラット化し、毎日送信することができます。彼らはまた、ESPのニーズに応じてファイル形式を調整するのに役立ちます。このファイルの作成には2〜3週間かかることに注意してください。
+お客様またはお客様のメールサービスプロバイダー (ESP) は、フラットファイル内のアイテムのバンドルデータを参照して、メールにバンドルデータを取り込むことができます。Stylitics ではバンドルデータを CSV、TXT、または XML 形式でフラット化し、そのデータを毎日送信できます。また、メールサービスプロバイダー (ESP) のニーズに合わせてファイル形式を調整することもできます。このファイルの作成には2～3週間かかることに注意してください。
 
-#### 要件:
-- **場所**:StyliticsはファイルをStyliticsのSFTPに毎日ドロップすることができますし、またはあなたのSFTPの認証情報を送ってファイルをドロップしてもらうこともできます。 
-- **時間**:Styliticsは毎朝ファイルをドロップします。特定の時間が必要な場合は知らせてください。 
+#### 要件
+- **ロケーション**:Stylitics が ファイルを Stylitics SFTP にドロップしてお客様がファイルを毎日取り込むか、またはお客様が Stylitics に SFTP 認証情報を送信してファイルをドロップすることができます。 
+- **時間**:Styliticsは毎朝ファイルをドロップします。特定の時間にファイルが必要となるかどうかを Stylitics にお知らせください。 
 - **ファイルキー**:あなたとStyliticsは、ESPがデータを参照できるように、ファイルのキーとなるアイテムデータ文字列について合意する必要があります。SKU、`item_group_id`、または`item_number`が一般的に使用されます。 
 
 ### 3\.Web サイト データ抽出アプローチ
-ベンダーは、あなたのサイトのフロントエンドからStyliticsのコンテンツをスクレイピングし、バンドルデータをメールに挿入することができます。Styliticsからの追加作業は必要ありません。 
+ベンダーは、サイトのフロントエンドをスクレイピングして Stylitics のコンテンツを取得し、バンドルデータをメールに挿入できます。Styliticsからの追加作業は必要ありません。 
 
 ## メールテンプレートのベストプラクティス 
 
-あなたとあなたのメールサービスプロバイダー (ESP) は、Styliticsのデータとバンドルを挿入するためのHTMLメールテンプレートを作成します。ここにいくつかのベストプラクティスと推奨事項があります。 
-- メールで最も高価なアイテムまたはユーザーが購入または操作した最初の定価アイテムの2〜4個のバンドルを表示する 
+お客様とお客様のメールサービスプロバイダー (ESP) は、Stylitics データとバンドルを挿入するための HTML メールテンプレートを作成します。ここにいくつかのベストプラクティスと推奨事項があります。 
+- ユーザーが購入または反応した最も高額なアイテムまたは最初の定価アイテムについて、2～4個のバンドルをメールに表示します 
 - 複数の`item_numbers`を呼び出して、最初のいくつかのバンドル応答を表示します 
 - バンドルがアイテムに利用できない場合は、フォールバックオプションを用意してください。 
-	- スタイリティクスのバンドルがあるセクションを非表示にする 
+	- Stylitics バンドルがあるセクションを非表示にします 
 	- 次のアイテムのバンドルをユーザーが表示しました 
-- バンドル画像と製品タイトルおよびサムネイル画像のリストを表示して、ユーザーが明確なクリックスルーを持つようにします。
+- バンドル画像と製品タイトルおよびサムネイル画像のリストを表示して、ユーザーが明確にクリックスルーできるようにします
 
 {% alert note %}
-StyliticsウィジェットのJavaScriptは、メールに挿入することはできません。なぜなら、メールはJavaScriptをサポートしていないからです。
+メールでは JavaScript がサポートされていないため、Stylitics ウィジェットの JavaScript をメールに挿入することはできません。
 {% endalert %}
 
 ## 分析
 
-Styliticsは、このタイプのメールプログラムのバンドルデータを提供します。したがって、あなた、あなたのメールサービスプロバイダー (ESP)、およびStyliticsの間で開封データの共有をお願いしています。可能であれば、リフトを理解し、プログラムを改善するために、次の指標を受け取りたいと考えています。
-- 送信されたメール 
-- 開封されたメール 
+Styliticsは、このタイプのメールプログラムのバンドルデータを提供します。そのため、お客様、お客様のメールサービスプロバイダー (ESP)、Stylitics の間でオープンなデータ共有を行ってください。可能であれば、リフト (効果) を理解し、プログラムを改善するために、Braze に次の指標を提供していただくことを希望しています。
+- 送信メール数 
+- 開封メール数 
 - ビューとエンゲージメント 
 - クリック率 
 - バッグに追加 
@@ -93,8 +93,8 @@ Styliticsは、このタイプのメールプログラムのバンドルデー
 ## 次のステップ 
 
 メールプログラムの次のステップとタイムラインを調整するために、Styliticsのアカウントマネージャーに連絡してください。次のステップには以下が含まれます： 
-- 使用したいメールを決定する
-- Styliticsをメールサービスプロバイダー (ESP)に接続して、APIオプションまたはフラットファイルオプションを決定するためのデータ交換について話し合います。 
+- 使用するメールを決定する
+- API オプションまたはフラットファイルオプションを決定するためにデータ交換について検討するため、Stylitics をお客様のメールサービスプロバイダー (ESP) に紹介する 
 - ESPを使用してモックアップを作成する 
 - 分析に合わせる 
 - 打ち上げのタイムラインに合わせる 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/worthy.md b/_lang/ja/_partners/message_personalization/dynamic_content/worthy.md
index 1f2a091d684..002e341b585 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/worthy.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/worthy.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Worthy
 article_title: Worthy
-description: "このリファレンス記事では、Braze とWorthy の提携について説明します。これは、メッセージパーソナライゼーション プラットフォームで、Braze を通じてパーソナライズされた、豊富なアプリ体験を作成し、配信することができます。"
+description: "このリファレンス記事では、Braze と Worthy のパートナーシップについて説明します。Worthy は、パーソナライズされたリッチなアプリ内エクスペリエンスを作成し、Braze を通じて配信できるメッセージパーソナライゼーションプラットフォームです。"
 alias: /partners/worthy/
 page_type: partner
 search_tag: Partner
@@ -10,17 +10,17 @@ search_tag: Partner
 
 # Worthy
 
-> [Worthy](https://worthy.ai/)とBrazeインテグレーションにより、Worthyのドラッグアンドドロップエディタを使用して、簡単にパーソナライズされたを作成し、豊富なアプリ体験を作成し、Brazeを通して配信することができます。さらに、Worthyは自動的に次のことを行います。
+> [Worthy](https://worthy.ai/) と Braze の統合により、Worthy のドラッグ＆ドロップダイナミックコンテンツエディターを使用して、パーソナライズされたリッチなアプリ内エクスペリエンスを簡単に作成し、Braze を通じて提供できるようになります。さらに、Worthy により以下の処理が自動的に行われます。
 
-- メッセージングに接続されたコンテンツサーバーとセキュアなAPI を作成します。
-- 分析 でアプリ内メッセージ s を作成し、Braze で直接イヤーをアプリする"トラッキングをクリックします。
-- Worthy のドラッグアンドドロップエディタを使用して自動的にHTMLをエクスポートし、**カスタムコード** Braze のアプリ内メッセージ キャンペーンs で使用します。これには、設定する必要なAPI コネクションとダイナミックな内容が含まれます。
+- メッセージングのためにコネクテッドコンテンツサーバーとセキュアな API を作成する。
+- 分析とクリックトラッキングを使用して、Braze に直接表示されるアプリ内メッセージを作成する。
+- Braze の**カスタムコード**アプリ内メッセージキャンペーンで使用する HTML を、Worthy のドラッグ＆ドロップエディターで自動的にエクスポートする。これには、お客様が設定する必要な API 接続とダイナミックコンテンツが含まれます。
 
 ## ユースケース
 
-- ユーザー オンボーディング選択に基づくカスタムウェルカムエクスペリエンス
+- ユーザーオンボーディングの選択に基づくカスタムウェルカムエクスペリエンス
 - スペシャルイベントやプロモーションのアプリ体験
-- アプリ行動に基づく顧客 フィードバック・格付けの収集
+- アプリの動作に基づく顧客フィードバックと評価の収集
 - アプリ商品アイデアの早期検証
 - 豊富な通知、ニュース、コミュニティー更新
 
@@ -28,22 +28,22 @@ search_tag: Partner
 
 | 要件 | 説明 |
 | --- | --- |
-| [Worthy](https://worthy.ai/)アカウント | この提携の前進タグeを考慮するためには、価値ある考慮が必要である。 |
-| Braze SDK | 豊富なアプリ内メッセージを送信するには、携帯アプリライセンスでBraze SDKを設定する必要があります。 |
+| [Worthy](https://worthy.ai/) アカウント | このパートナーシップを活用するには、Worthy アカウントが必要です。 |
+| Braze SDK | リッチなアプリ内メッセージを送信するには、モバイルアプリケーションで Braze SDK を設定する必要があります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 ## 統合
 
-### ステップ1:価値あるパーソナライズされた メッセージングの創造
+### ステップ1:Worthy でパーソナライズされたメッセージングを作成する
 
-Worthy ダッシュボードでアプリに移動し、**Message Creator** を選択し、ユーザーs に参加するために使用するパーソナライズされたを作成します。
+Worthy ダッシュボードでアプリに移動し、\[**Message Creator**] を選択し、ユーザーを獲得するために使用するパーソナライズされたメッセージを作成します。
 
 ### ステップ2:Braze キャンペーンの作成
 
 Brazeで[アプリ内メッセージ キャンペーン]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/create/)を作成し、**Message Type**を**カスタムコード**に設定します。
 
-### ステップ3:パーソナライズされたをBrazeにコピーする
+### ステップ3:パーソナライズされたメッセージを Braze にコピーする
 
-Worthyメッセージクリエータで、**Export**をクリックし、**Braze**を選択して、パーソナライズされたメッセージをBraze キャンペーン s で使用するためにエクスポートします。エクスポートされたコンテンツを、Braze キャンペーンエディタの**HTML + Asset Zip** のHTML テキストボックスにコピーします。
+Worthyメッセージクリエータで、**Export**をクリックし、**Braze**を選択して、パーソナライズされたメッセージをBraze キャンペーン s で使用するためにエクスポートします。エクスポートされたコンテンツを、Braze キャンペーンエディターの \[**HTML + アセット zip**] の下の HTML テキストボックスにコピーします。
 
-以上でBraze キャンペーンエディタの**Test**タブを使用して、すぐにパーソナライズされたをテストできます。 
+以上でBraze キャンペーンエディターの \[**テスト**] タブを使用して、パーソナライズされたメッセージをすぐにテストできます。 
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/wsc_sports.md b/_lang/ja/_partners/message_personalization/dynamic_content/wsc_sports.md
index 1094ec952ce..981b927a98c 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/wsc_sports.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/wsc_sports.md
@@ -1,7 +1,7 @@
 ---
 nav_title: WSC Sports
 article_title: WSC Sports
-description: "この参考記事では、BrazeとWSC Sportsの提携について説明しています。WSC Sportsはスポーツ動画プラットフォームであり、Brazeのプッシュ通知に豊かで強力なスポーツメディアを含めることができます。"
+description: "このリファレンス記事では、Braze と WSC Sports のパートナーシップについて説明します。WSC Sports は、リッチで安定したスポーツメディアをBraze のプッシュ通知に組み込むことができるスポーツ動画プラットフォームです。"
 alias: /partners/wsc_sports/
 page_type: partner
 search_tag: Partner
@@ -36,7 +36,7 @@ WSC Sportsアプリケーションは、動画の選択からエンドユーザ
 
 送信されると、WSC Sportsは選択されたオプションに基づいて、次のBrazeエンドポイントを使用して、選択されたユーザーセグメントにプッシュ通知を配信します:
 - [/messages/schedule/create]({{site.baseurl}}/api/endpoints/messaging/schedule_messages/post_schedule_messages#create-scheduled-messages)
-- /メッセージ/送信
+- [/messages/send]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_messages#sending-messages-immediately-via-api-only)
 
 メッセージの本文は次のとおりです: 
 ```
@@ -56,4 +56,4 @@ WSC Sportsアプリケーションは、動画の選択からエンドユーザ
 この時点で、あなたのキャンペーンはテストと送信の準備ができているはずです。エラーに遭遇した場合は、Brazeエラーメッセージログを確認してください。 
 
 [1]: https://wsc-sports.com/
-[2]: {% image_buster /assets/img/wsc_sports/braze_integration.jpg %}「braze_integration.jpg」
\ No newline at end of file
+[2]: {% image_buster /assets/img/wsc_sports/braze_integration.jpg %} "braze_integration.jpg"
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_personalization/dynamic_content/wyng.md b/_lang/ja/_partners/message_personalization/dynamic_content/wyng.md
index e08bbaa10af..70f4b2156bf 100644
--- a/_lang/ja/_partners/message_personalization/dynamic_content/wyng.md
+++ b/_lang/ja/_partners/message_personalization/dynamic_content/wyng.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Wyng
 article_title: Wyng
-description: "このレファレンス記事では、BrazeとWyngの提携、ゼロパーティデータプラットフォームの概要を説明します。これにより、マイクロエクスペリエンス、顧客プリファレンスポータル、API プラットフォームを介して、顧客のプリファレンスと属性を簡単に収集、使用、統合できます。"
+description: "このリファレンス記事では、Braze と Wyng のパートナーシップについて説明します。Wyng は、マイクロエクスペリエンス、カスタマーユーザー設定ポータル、API プラットフォームで顧客のユーザー設定と属性を容易に収集、利用、統合できるようにするゼロパーティデータプラットフォームです。"
 alias: /partners/wyng/
 page_type: partner
 search_tag: Partner
@@ -9,16 +9,16 @@ search_tag: Partner
 
 # Wyng
 
-> [Wyng][0]は、適切な瞬間に消費者を巻き込み、好みや他のゼロパーティデータを収集し、リアルタイムでパーソナライズする対話型デジタルエクスペリエンスs(すなわちクイズ、ユーザー設定センターs、プロモーション)を容易に構築できるようにします。
+> [Wyng][0] では、適切なタイミングで消費者に働きかけ、ユーザー設定やその他のゼロパーティデータを収集し、リアルタイムでパーソナライズを行うインタラクティブなデジタルエクスペリエンス (クイズ、好みのセンター、プロモーション)を簡単に構築できます。
 
-BrazeとWyngインテグレーションでは、BrazeキャンペーンとBrazeキャンバスでWyngエクスペリエンスで得たゼロパーティデータを活用して、インターアクションをパーソナライズできます。Wyngはユーザー設定センターを動かすこともできるので、消費者sは自分のブランドと共有するデータや好み(通信の好みを含む)をコントロールすることができる。
+Braze と Wyng の統合により、Wyng のエクスペリエンスから取得したゼロパーティデータを利用して、Braze キャンペーンと Braze キャンバスでインタラクションをパーソナライズできます。また、Wyng ではユーザー設定センターにより、消費者がブランドと共有するデータや好み (好みのコミュニケーション方法など) をコントロールできます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| Wyng勘定 | この提携の前進タグeを考慮するには、Wyngな考慮が必要である。 |
-| Braze REST API キー | `users.track` 権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
+| Wyng アカウント | このパートナーシップを活用するには、Wyng アカウントが必要です。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
@@ -27,43 +27,43 @@ BrazeとWyngインテグレーションでは、BrazeキャンペーンとBraze
 
 Wyngで、[**Integrations**][1]に移動し、**Add**タブを選択します。次に、**Braze**にマウスを合わせ、**Connect**をクリックして統合します。
 
-![Wyng プラットフォームのBrazeパートナタイル。][2]{: style="max-width:80%;"}
+![Wyng プラットフォームの Braze パートナータイル。][2]{: style="max-width:80%;"}
 
 ### ステップ2:Braze コネクターを設定する
 
-1. s を開封する設定ウィンドウで、Braze REST API キーを指定します。
-![認証情報のプロンプトの"画像。][4]{: style="max-width:80%;"}<br><br>
-2. 次に、ドロップダウンを使用して、Brazeと共有するWyng キャンペーンを選択します。![Braze コネクターの"画像で、Braze と共有する既存のWyng キャンペーンを選択します。][5]{: style="max-width:80%;"}<br><br>
-3. 次に、サブスクリプションs、属性およびイベントオブジェクト、およびカスタムイベントs を設定する必要があります。<br><br>
+1. 表示される設定ウィンドウで、Braze REST API キーを指定します。
+![認証情報プロンプト。][4]{: style="max-width:80%;"}<br><br>
+2. 次にドロップダウンを使用して、Braze と共有する Wyng キャンペーンを選択します。![Braze と共有する既存の Wyng キャンペーンを選択するように求める Braze コネクター。][5]{: style="max-width:80%;"}<br><br>
+3. 次に、サブスクリプション、属性オブジェクトとイベントオブジェクト、およびカスタムイベントを設定する必要があります。<br><br>
 - **サブスクリプションの設定(必須)**<br>
-ユーザー s をサブスクリプショングループ s にサブスクライブするには、**サブスクリプション** を追加し、サブスクリプショングループの名前とID を追加します。複数のグループ名とID を追加するには、**Add Subscription** ボタンを再度クリックします。<br>![サブスクリプショングループの名前とID の入力を求める"画像。][8]{: style="max-width:80%;"}<br><br>
-- **ユーザートラックの設定**<br>
-**カスタムプロパティ**を追加をクリックして、`/users/track`エンドポイントに送信する属性とイベントオブジェクトペアを追加します。これを使用して、インテグレーション用に送信されたデータトランスアクションごとにハードコードd 属性を追加します。複数のプロパティーを追加するには、**カスタムプロパティ** ボタンを再度クリックします。<br>![属性のカスタムプロパティを追加するように求める"画像。][9]{: style="max-width:80%;"}<br><br>
-- **送信カスタムイベント**<br>
-オプションで、**送信カスタムイベント**を有効にすることができます。有効になっている場合、イベント名と対応するアプリ ID を含める必要があります。<br>![必要に応じて、カスタムイベントs を送信するように促す"画像。][10]{: style="max-width:80%;"}<br><br>
-4. 最後に、Wyng フィールドs をユースケースに基づいてBraze API フィールドs にマップする必要があります。**フィールド**を選択してマップするsを選択し、その後、**統合を保存します。保存すると、これらのm アプリ ed フィールド s は**Integrations > Manage** にあります。
-![さまざまなWyng フィールドs を特定のBraze フィールドs にマップできます。][11]{: style="max-width:80%;"}
+ユーザーをサブスクリプショングループに登録するには、\[**Add Subscription**] をクリックし、サブスクリプショングループの名前と ID を追加します。複数のグループ名とID を追加するには、**Add Subscription** ボタンを再度クリックします。<br>![サブスクリプショングループの名前と ID の入力を促す画面。][8]{: style="max-width:80%;"}<br><br>
+- **User track setup**<br>
+**カスタムプロパティ**を追加をクリックして、`/users/track`エンドポイントに送信する属性とイベントオブジェクトペアを追加します。これを使用して、統合のために送信された各データトランザクションのハードコーディングされた属性値を追加します。複数のプロパティーを追加するには、**カスタムプロパティ** ボタンを再度クリックします。<br>![属性のカスタムプロパティの追加を促す画面。][9]{: style="max-width:80%;"}<br><br>
+- **Send custom event**<br>
+オプションで、**送信カスタムイベント**を有効にすることができます。有効になっている場合、イベント名と対応するアプリ ID を含める必要があります。<br>![必要に応じてカスタムイベントの送信を促す画面。][10]{: style="max-width:80%;"}<br><br>
+4. 最後に、ユースケースに基づいて Wyng のフィールドを Braze API のフィールドにマッピングする必要があります。\[**Select a field**] を選択してマップピングするフィールドを選択し、その後、統合を**保存**します。保存すると、これらのマッピングされたフィールドは**\[Integrations] > \[Manage]** の下で確認できます。
+![特定の Braze フィールドにマッピングできるさまざまな Wyng フィールドの例。][11]{: style="max-width:80%;"}
 ![使用可能なシンクフィールドの一覧。][12]{: style="max-width:80%;margin-top:2px"}
 
 ### ステップ3:連携のテスト
 
-Wyng で、Wyng キャンペーンでフォームを送信するかどうかを確認します。主な本番キャンペーンにレコードを追加しない場合は、プレビュー キャンペーンで送信することもできます。**Integration** ダッシュボードに、正常なトランスアクションが表示されます。
+Wyng で、Wyng キャンペーンでフォームを送信するかどうかを確認します。メインの本番キャンペーンにレコードを追加したくない場合は、プレビューキャンペーンでフォームを送信することもできます。\[**Integration**] ダッシュボードに、正常に完了したトランザクションが表示されます。
 
 ## この統合の使用
 
-データコネクターが配置されると、他のデータフィールドと同様に、Wyng で作成され、Braze に追加されたすべてのフィールドを使用して、s、Segment オーディエンスs、またはフィード パーソナライズされたの内容をトリガー キャンペーンできます。
+データコネクターが配置されると、Wyng で作成され、Braze に追加されたフィールドを、他のデータフィールドのように使用して、キャンペーンのトリガー、オーディエンスのセグメンテーション、パーソナライズされたコンテンツのフィードを行うことができます。
 
-アプリケーションは幅広く、具体的な質問は\[contact@wyng.com][13]または独自のアカウントマネージャーに対応できます。
+用途が幅広いため、具体的なご質問がある場合には、\[contact@wyng.com][13]または担当のアカウントマネージャーにお問い合わせください。
 
 ## トラブルシューティング
 
-### 送信失敗
+### 失敗した送信
 
 送信に失敗した場合、Brazeにデータを送信するときに、**View Log**リンクをクリックして、失敗した送信と関連するエラーメッセージを確認します。
 
-!["View Log"アクション s ヘッダーにあるリンク。][14]{: style="max-width:80%;"}
+![アクションヘッダーの下にある「View Log」リンク。][14]{: style="max-width:80%;"}
 
-ログページには、失敗した送信、再試行回数、送信、エラー、および送信を再プッシュするためのリンクが表示されます。
+ログページには、失敗した送信、再試行回数、送信されたデータ、エラー、および送信を再プッシュするためのリンクが表示されます。
 
 ![失敗した送信が表示される例。][15]{: style="max-width:80%;"}
 
diff --git a/_lang/ja/_partners/message_personalization/localization.md b/_lang/ja/_partners/message_personalization/localization.md
index 9d541413484..22630221fa9 100644
--- a/_lang/ja/_partners/message_personalization/localization.md
+++ b/_lang/ja/_partners/message_personalization/localization.md
@@ -4,7 +4,7 @@ article_title: ローカライズパートナー
 page_order: 6
 
 page_type: landing
-description: "このランディングには、メッセージング キャンペーンs でローカライゼーションを使用できるBrazeパートナ(Alloys) が一覧表示されます。"
+description: "このランディングページには、メッセージングキャンペーンでローカライゼーションデータを使用できるようにする Braze パートナー (Alloys) が一覧表示されています。"
 layout: partner_page
 search_tag: Partner
 
diff --git a/_lang/ja/_partners/message_personalization/localization/crowdin.md b/_lang/ja/_partners/message_personalization/localization/crowdin.md
index 2ef6a0fcf08..dc45caa534c 100644
--- a/_lang/ja/_partners/message_personalization/localization/crowdin.md
+++ b/_lang/ja/_partners/message_personalization/localization/crowdin.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Crowdin
 article_title: Crowdin
-description: "この参考記事では、BrazeとクラウドベースのソフトウェアプラットフォームであるCrowdinのパートナーシップについて概説している。"
+description: "このリファレンス記事では、Braze と Crowdin のパートナーシップについて説明します。Crowdin は、クラウドベースのソフトウェアプラットフォームであり、Braze でのメールテンプレートとコンテンツブロックの翻訳を自動化できます。"
 alias: /partners/crowdin/
 page_type: partner
 search_tag: Partner
@@ -10,59 +10,59 @@ search_tag: Partner
 
 # Crowdin
 
-> Crowdinは、ローカライゼーション管理のためのクラウドベースのソフトウェアである。Crowdinを使えば、AndroidやiOSのアプリ、ウェブサイト、店舗のスクリーンショット、その他のコンテンツを翻訳することができる。翻訳は、社内チーム、翻訳会社、または機械翻訳エンジンを使って行うことができる。
+> Crowdin はローカライゼーション管理のためのクラウドベースのソフトウェアです。Crowdin を使用して、Android や iOS のアプリ、Web サイト、ストアスクリーンショットなどのコンテンツを翻訳できます。翻訳は、社内チーム、翻訳会社、または機械翻訳エンジンを使って行うことができる。
 
-BrazeとCrowdinの統合により、メールテンプレートやコンテンツブロックを翻訳することができる。また、BrazeアカウントからCrowdinプロジェクトにコンテンツを同期し、Brazeに戻って翻訳を追加することもできる。
+Braze と Crowdin の統合により、メールテンプレートとコンテンツブロックを翻訳できます。また、Braze アカウントから Crowdin プロジェクトにコンテンツを同期し、Braze に戻って翻訳を追加することもできます。
 
 ## 前提条件
 
 | 必要条件| 説明|
 | ---| ---|
-| クラウディンアカウント | このパートナーシップを利用するには、[Crowdinアカウントが](https://accounts.crowdin.com/register)必要である。 |
-| クラウディン翻訳プロジェクト | BrazeアカウントとCrowdinまたはCrowdin Enterpriseを接続するには、まずサインアップして翻訳プロジェクトを作成する必要がある。 |
+| Crowdin アカウント | このパートナーシップを活用するには、[Crowdin アカウント](https://accounts.crowdin.com/register)が必要です。 |
+| Crowdin 翻訳プロジェクト | Braze アカウントと Crowdin または Crowdin Enterprise を接続するには、最初にサインアップして翻訳プロジェクトを作成する必要があります。 |
 | Braze REST API キー | すべてのテンプレートとコンテンツブロックの権限を持つBraze REST APIキー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| Braze SDKエンドポイント | SDKエンドポイントURLは、[インスタンスの]({{site.baseurl}}/api/basics/#endpoints)Braze URLに依存する。 |
+| Braze SDKエンドポイント | SDK エンドポイントは[インスタンス]({{site.baseurl}}/api/basics/#endpoints)の Braze URL に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 統合
 
-### ステップ1:Crowdin/Crowdin EnterpriseでBrazeアプリをセットアップする
+### ステップ1:Crowdin/Crowdin Enterprise で Braze アプリを設定する
 
 #### Crowdin
 CrowdinでBrazeアプリをセットアップするには、以下の手順に従う：
 
-1. [マーケットプレイスのBrazeアプリに](https://store.crowdin.com/braze-app)アクセスする。
-2. **インストールを**クリックしてアカウントに追加する。
-3. Brazeコンテンツのローカライズ用に作成したプロジェクトを開く。
+1. [マーケットプレイスの Braze アプリ](https://store.crowdin.com/braze-app)に移動します。
+2. \[**Install**] をクリックしてアプリをアカウントに追加します。
+3. Braze コンテンツのローカライズ用に作成したプロジェクトを開きます。
 4. **設定＞統合**タブに進む。
 5. **アプリケーション・**セクションで、Brazeアプリをクリックする。
-6. ダイアログで、Brazeの認証情報（Braze REST APIキーとBraze SDKエンドポイント）を入力する。
-7. **Braze Connectorでログインを**クリックする。 
+6. ダイアログで、Braze の認証情報 (Braze REST API キーと Braze SDK エンドポイント) を入力します。
+7. \[**Log in with Braze Connector**] をクリックします。 
 
-#### クラウドイン・エンタープライズ
+#### Crowdin Enterprise
 Crowdin EnterpriseでBrazeアプリをセットアップするには、以下の手順に従う：
 
-1. **ワークスペースの**ホームページ＞**マーケットプレイスに**アクセスする。
-2. Brazeアプリの**インストールを**クリックし、組織に追加する。
-3. Brazeコンテンツのローカライズ用に作成したプロジェクトを開く。
-4. **アプリケーション＞カスタムと**進む。
+1. \[**Workspace**] ホームページ > \[**Marketplace**] に移動します。
+2. Braze アプリで \[**Install**] をクリックし、組織に追加します。
+3. Braze コンテンツのローカライズ用に作成したプロジェクトを開きます。
+4. **\[Applications] > \[Custom]** に移動します。
 5. Brazeアプリをクリックする。
-6. ダイアログで、Brazeの認証情報（Braze REST APIキーとBraze SDKエンドポイント）を入力する。
-7. **Braze Connectorでログインを**クリックする。
+6. ダイアログで、Braze の認証情報 (Braze REST API キーと Braze SDK エンドポイント) を入力します。
+7. \[**Log in with Braze Connector**] をクリックします。
 
-### ステップ2:コンテンツをCrowdin/Crowdin Enterpriseに追加する
+### ステップ2:コンテンツを Crowdin/Crowdin Enterprise に追加する
 
-Brazeの認証情報を入力すると、2つのパネルが表示される。Brazeアカウントから翻訳用ファイルを同期するコンテンツを選択し、**Crowdinに同期を**クリックする。
+Brazeの認証情報を入力すると、2つのパネルが表示される。Braze アカウントから翻訳用ファイルを同期するコンテンツを選択し、\[**Sync to Crowdin**] をクリックします。
 
-CrowdinのEditorモードでは、Brazeアカウントから同期されたコンテンツを、文字列リストまたはファイルプレビューとして翻訳者に表示することができる。
+Crowdin の Editor モードでは、Braze アカウントから同期されたコンテンツを、文字列リストまたはファイルプレビューとして翻訳者に表示できます。
 
 ![Crowdin Editorのメールコンポーザーに基本的な翻訳を追加したイメージ。][2]
 
-### ステップ3:ブレイズに翻訳を追加する
+### ステップ3:Braze に翻訳を追加する
 
-翻訳が完了したら、CrowdinでBrazeアプリを開き、左側のパネルで翻訳したファイル（ファイルごとに、すべての対象言語か特定の言語かを選択できる）を選択し、**Brazeに同期を**クリックする。
+翻訳が完了したらすぐに Crowdin で Braze アプリを開き、左側のパネルで翻訳済みファイルを選択し (ファイルごとに、すべての翻訳言語または特定の翻訳言語のみを選択できます)、\[**Sync to Braze**] をクリックします。
 
-![ユーザーが翻訳ファイルを選択し、Brazeに同期している様子。][3]
+![翻訳ファイルを選択し、Braze に同期しているユーザー。][3]
 
 [1]: {% image_buster /assets/img/crowdin/copy_api_key_identifier.png %}
 [2]: {% image_buster /assets/img/crowdin/crowdin_editor_email_preview.png %}
diff --git a/_lang/ja/_partners/message_personalization/localization/lokalise.md b/_lang/ja/_partners/message_personalization/localization/lokalise.md
index 4bc27f50594..91fe892cd55 100644
--- a/_lang/ja/_partners/message_personalization/localization/lokalise.md
+++ b/_lang/ja/_partners/message_personalization/localization/lokalise.md
@@ -12,40 +12,40 @@ search_tag: Partner
 
 > [Lokaliseは](https://lokalise.com)アジャイルチームのための翻訳管理サービスである。
 
-BrazeとLokaliseの統合は、Connected Contentを活用し、ユーザーの言語設定に基づいてBrazeキャンペーンに翻訳コンテンツを簡単に挿入できる。
+Braze と Lokalise の統合により、コネクテッドコンテンツを活用し、ユーザーの言語設定に基づいて翻訳されたコンテンツを Braze キャンペーンに簡単に挿入できるようになります。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 | ----------- | ----------- |
-| Lokalise アカウント | このパートナーシップを利用するには、Lokaliseアカウントが必要である。 |
+| Lokalise アカウント | このパートナーシップを活用するには、Lokalise アカウントが必要です。 |
 | Lokalise 翻訳プロジェクト | この統合を設定する前に、Lokalise翻訳プロジェクトを作成する必要がある。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-### 新しいLokaliseプロジェクトを作成する
+### 新しい Lokalise プロジェクトを作成する
 
-新しい翻訳プロジェクトを作成するには、Lokaliseにログインし、**新規プロジェクトを**選択する。次に、プロジェクトに名前を付け、**ベース言語**（翻訳元の言語）を選択し、1つ以上の**ターゲット言語を**追加し、**ソフトウェアローカリゼーションプロジェクトタイプを**選択する。準備ができたら、**Proceedを**クリックする。
+新しい翻訳プロジェクトを作成するには、Lokalise にログインして \[**New Project**] を選択します。次に、プロジェクトに名前を付け、**ベース言語**（翻訳元の言語）を選択し、1つ以上の**ターゲット言語を**追加し、**ソフトウェアローカリゼーションプロジェクトタイプを**選択する。準備ができたら、\[**Proceed**] をクリックします。
 
 ## 統合
 
-Lokaliseでは、Brazeで定義したConnected Content変数ごとに翻訳キーを作成する。翻訳の準備ができたら、言語ごとに1つのJSONファイルを生成し、コネクテッド・コンテンツを提供するURLに公開することができる。
+Lokalise で、Braze で定義したコネクテッドコンテンツ変数ごとに翻訳キーを作成します。翻訳の準備ができたら、言語ごとに1つのJSONファイルを生成し、コネクテッド・コンテンツを提供するURLに公開することができる。
 
 ### ステップ1:ユーザー言語を設定する
 
-まだの場合は、Brazeダッシュボードを開き、**Users > User importに**進む。ここで、ユーザーをインポートすることができる。インポート用のCSVファイルを準備する際には、ユーザーの言語を記載した言語カラムを必ず含めること。この言語フィールドは、後で翻訳を表示するときに使われる。 
+まだ設定していない場合は、Braze ダッシュボードを開いて **\[ユーザー] > \[ユーザーインポート]** に移動します。ここで、ユーザーをインポートすることができる。インポート用のCSVファイルを準備する際には、ユーザーの言語を記載した言語カラムを必ず含めること。この言語フィールドは、後で翻訳を表示するときに使われる。 
 
 {% alert important %}
-使用する言語コードは、BrazeとLokaliseの両方で一致していなければならない。
+使用する言語コードは、Braze と Lokalise の両方で一致している必要があります。
 {% endalert %}
-### ステップ2:Lokaliseで翻訳を準備する
+### ステップ2:Lokalise で翻訳を準備する
 
 次に、Lokaliseで翻訳を準備するには、Braze Connected Content変数で使用しているのと同じ名前の翻訳キーを手動で作成する必要がある。 
 
 例えば、単純な翻訳キー、`description` を作ってみよう：
-1. Lokaliseプロジェクトを開き、**Add Keyを**クリックし、**Key**フィールドに "description "を入力する。
+1. Lokaliseプロジェクトを開いて \[**Add Key**] をクリックし、\[**Key**] フィールドに「description」と入力します。
 2. **Base Language Value**フィールドに「Demo description」と入力する。
-3. **Platformsの**ドロップダウンに "Web "を追加する。 
-4. 準備ができたら、**Saveを**クリックする。
+3. \[**Platforms**] のドロップダウンに「Web」を追加します。 
+4. 準備ができたら、\[**Save**] をクリックします。
 
 ![][1]{: style="max-width:60%"}
 
@@ -55,12 +55,12 @@ Lokaliseでは、Brazeで定義したConnected Content変数ごとに翻訳キ
 
 #### 既知の問題
 
-- キーは**ウェブ・プラットフォームに**割り当てられなければならない。
-- ピリオド（`.` ）や`_on` 文字列を含むキーの使用は避けること。例えば、`this.is.the.key` の代わりに`this_is_the_key` を使い、`join_us_on_instagram` の代わりに`join_us_instagram` を使う。
+- キーが **Web** プラットフォームに割り当てられている必要があります。
+- ピリオド（`.` ）や`_on` 文字列を含むキーの使用は避けること。たとえば、`this.is.the.key` の代わりに `this_is_the_key` を使用し、`join_us_on_instagram` の代わりに `join_us_instagram` を使用します。
 
-### ステップ3:LokaliseでBrazeアプリを設定する
+### ステップ3:Lokalise で Braze アプリを設定する
 
-Lokaliseプロジェクトを開き、**Appsを**クリックする。ここで、Brazeアプリを検索してインストールする。以下の画面が表示される：
+Lokalise プロジェクトを開いて \[**Apps**] をクリックします。ここで、Brazeアプリを検索してインストールする。以下の画面が表示される：
 
 ![Lokalise上のBraze設定には、プロジェクトIDと翻訳ファイルのURLが記載されている。][3]
 
@@ -69,7 +69,7 @@ Lokaliseプロジェクトを開き、**Appsを**クリックする。ここで
 1. URLパスの最初の部分はすべての言語に共通である。
 2. URL末尾のJSONファイル名は、言語コードに基づいている。
 
-翻訳ファイルのURLは、Brazeキャンペーンを設定する際に必要となるURLである。**Refreshを**クリックすれば、JSONファイルの内容を更新できる。URLは変わらないので、BrazeのConnected Contentコールを変更する必要はない。
+翻訳ファイルのURLは、Brazeキャンペーンを設定する際に必要となるURLである。JSON ファイルのコンテンツを更新するには \[**Refresh**] をクリックします。URL は変更されず、Braze でコネクテッドコンテンツ呼び出しを変更する必要がないことに注意してください。
 
 ### テストURL
 
@@ -77,13 +77,13 @@ Lokaliseプロジェクトを開き、**Appsを**クリックする。ここで
 
 ![][4]
 
-### ステップ4:Brazeキャンペーンで翻訳を使用する
+### ステップ4:Braze キャンペーンで翻訳を使用する
 
-#### コネクテッド・コンテンツを挿入する
+#### コネクテッドコンテンツ呼び出しを挿入する
 
-準備ができたら、Brazeに戻り、既存のキャンペーンを開くか、新しいキャンペーンを作成する。この例では、サンプルコンテンツで新しいメールキャンペーンを作成する。**メール本文の編集を**クリックする。
+準備ができたら、Brazeに戻り、既存のキャンペーンを開くか、新しいキャンペーンを作成する。この例では、サンプルコンテンツで新しいメールキャンペーンを作成する。\[**メール本文を編集**] をクリックします。
 
-翻訳を挿入するには、HTMLにConnected Contentリクエストを追加する必要がある。これは、以下のマークアップを挿入することで可能になる：
+翻訳を挿入するには、ドキュメントの最上部または翻訳が必要な最初の位置の直前に、HTML 形式のコネクテッドコンテンツリクエストを追加する必要があります。これは、以下のマークアップを挿入することで可能になる：
 
 {% raw %}
 `{% connected_content https://exports.live.lokalise.cloud/braze/123abc/456xyz/{{${language}}}.json :save translations %}`
@@ -93,34 +93,34 @@ Lokaliseプロジェクトを開き、**Appsを**クリックする。ここで
 
 {% raw %}
 
-- `{{${language}}}` とは、「この位置にユーザー言語を挿入する」という意味である。あるいは、言語コードをハードコードすることもできる。例えば、`en.json` 。
+- `{{${language}}}` は、「この位置にユーザー言語を挿入する」という意味です。あるいは、言語コードをハードコードすることもできる。例えば、`en.json` 。
   - 各ユーザに適切な翻訳JSONファイルが取得されるようにするには、`{{${language}}}` profile属性か、ユーザの言語を保持する別の同様のカスタム属性を翻訳ファイルのURLの最後に配置する必要がある。(例えば、`/{{${language}}}.json`) これらの属性に保持される値は、翻訳されたJSONファイルのそれぞれの接頭辞と一致しなければならない。これにより、各ユーザーに対して正しい翻訳ファイルが返されるようになる。
-- `:save translations` はJSONコンテンツをtranslations変数の下に保存する。
+- `:save translations` により JSON コンテンツが translations 変数に保存されます。
 
 #### 翻訳を表示する
 
 ここでtranslations変数を使い、必要な翻訳をキーで表示する。
 
-例えば、`description` キーを表示するには、`{{ translations.description }}` とする。
+たとえば、`description` キーを表示するには `{{ translations.description }}` を使用します。
 
 {% endraw %}
 ![][6]
 
-最後に、メールテンプレートを保存し、プレビューする。翻訳が表示されるはずだ。
+最後に、メールテンプレートを保存し、プレビューする。翻訳が表示されるはずです。
 
 ## よくある質問
 
-**誤ってLokaliseからキーを削除した場合はどうなるのか？**<br>
+**誤って Lokalise からキーを削除した場合はどうなりますか?**<br>
 Brazeの対応する文字列はもう翻訳を持たない。
 
 **`en` のロケールをLokaliseの`en-US` で上書きした場合、Brazeはそれを`en-US` と読み取るのだろうか？**<br>
-いいえ、ロケールのISOコードはBrazeとLokaliseで一致していなければならない。
+いいえ、ロケールの ISO コードは Braze と Lokalise で一致している必要があります。
 
-**Lokaliseコンテンツに接続する際、`:rerender` フラグを使用できるか？**<br>
-ああ、もちろんだ。このフラグの追加方法については、Brazeのドキュメントを参照されたい。
+**Lokalise コンテンツを接続する際に `:rerender` フラグを使用できますか?**<br>
+使用できます。このフラグの追加方法については、Brazeのドキュメントを参照されたい。
 
-**Lokaliseで翻訳ファイルを更新した後、Brazeで翻訳されたコンテンツの変更を確認できないのはなぜか？**<br>
-Brazeは翻訳されたコンテンツをキャッシュするので、更新に数分かかることがある。キャンペーンをテストしていて、翻訳の結果をすぐに確認する必要がある場合は、この参考記事で説明されているように、`:cache_max_age` パラメータを使うことができる。
+**Lokalise で翻訳ファイルを更新した後、Braze に翻訳コンテンツの変更が表示されないのはなぜですか?**<br>
+Braze では翻訳コンテンツがキャッシュされ、その更新には数分かかることがあります。キャンペーンをテストしていて、翻訳の結果をすぐに確認する必要がある場合は、このリファレンス記事で説明されているように、`:cache_max_age` パラメーターを使用できます。
 
 [1]: {% image_buster /assets/img/lokalise/1_add_key.png %}
 [2]: {% image_buster /assets/img/lokalise/2_translation_key_added.png %}
diff --git a/_lang/ja/_partners/message_personalization/localization/phrase.md b/_lang/ja/_partners/message_personalization/localization/phrase.md
index 1716836c6e2..7b5f08e6332 100644
--- a/_lang/ja/_partners/message_personalization/localization/phrase.md
+++ b/_lang/ja/_partners/message_personalization/localization/phrase.md
@@ -2,7 +2,7 @@
 nav_title: Phrase
 article_title: Phrase
 alias: /partners/phrase/
-description: "このリファレンス記事では、Brazeと、ローカライゼーション向けクラウドベースのソフトウエアであるフレーズとの提携について概説します。このインテグレーションを使用すると、Braze インターフェイスを離れることなく、メール テンプレートとコンテンツブロックを変換できます。"
+description: "このリファレンス記事では、Braze と Phrase のパートナーシップについて説明します。Phrase はクラウドベースのローカライゼーションソフトウェアです。この統合により、Braze インターフェイスを離れることなく、メールテンプレートとコンテンツブロックを翻訳できます。"
 page_type: partner
 search_tag: Partner
 
@@ -10,36 +10,36 @@ search_tag: Partner
 
 # Phrase 
 
-> [フレーズ](https://phrase.com/)は、ローカライゼーションマネジメントのためのクラウドベースのソフトです。句は自動化された翻訳ワークフローを有効にし、アジャイルチームの継続的なローカライゼーションをサポートします。
+> [Phrase](https://phrase.com/) はローカライゼーション管理のためのクラウドベースのソフトウェアです。句は自動化された翻訳ワークフローを有効にし、アジャイルチームの継続的なローカライゼーションをサポートします。
 
-フレーズとBrazeインテグレーションを使用すると、Braze インターフェイスを離れることなく、メール テンプレートとコンテンツブロックを変換できます。Braze向けフレーズTMSインテグレーションでは、シームレスなローカライゼーションでカスタマーエンゲージメントを高め、新たなマーケットへの成長を牽引できます。
+Phrase と Braze の統合により、Braze インターフェイスを離れることなく、メールテンプレートとコンテンツブロックを翻訳できます。Braze 向け Phrase TMS 統合により、シームレスなローカライゼーションでカスタマーエンゲージメントを高め、新しい市場への拡大を促進できます。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | --- | --- |
-| フレーズTMSアカウント | フレーズTMS Ultimate またはEnterprise アカウントは、この提携の前進タグe を考慮する必要があります。 |
+| Phrase TMS アカウント | この提携を利用するには、Phrase TMS Ultimate または Enterprise アカウントが必要です。 |
 | Braze REST API キー | すべての権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
-| Braze REST エンドポイント | [Your REST エンドポイント URL][1].エンドポイントは、インスタンスのBraze URL によって異なります。 |
+| Braze REST エンドポイント | [REST エンドポイント URL][1]。エンドポイントはインスタンスの Braze URL に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-## ステップ1:TMSフレーズ設定
+## ステップ1:Phrase TMS の設定
 
-フレーズで、**Settings > Integrations > Connectors > New** に移動します。
+Phraseで、**\[Settings] > \[Integrations] > \[Connectors] > \[New]** の順に進みます。
 
 1. コネクションの名前を指定し、型を**Braze**に変更します。<br><br>
 2. REST API キーとBraze REST エンドポイントを入力します。<br><br>
-3. リンクされたコンテンツブロックを持つメール テンプレートをどのように読み込むかを選択します。 
+3. コネクターがメール テンプレートおよびリンクされたコンテンツブロックをインポートする方法を選択します。 
 - 選択メール テンプレートのみ
 - コンテンツブロックを含める<br><br>
 4. コネクターがメール テンプレート変換をエクスポートする方法を選択します。 
 - 新規アイテムの作成
-- Originアルアイテム
+- 元のアイテム
   - すべてのアイテムをOriginすると、同じテンプレート/ブロックに翻訳がエクスポートされます。言語Segments は、提供された属性によって定義されます。<br><br>
     {% raw %}
-    元のアイテムが選択されている場合は、言語属性を入力します。言語属性はif/elsif引き数の言語を定義する。オリジナルのアイテムオプションを使用する場合は、以下のように構造化する必要があります。
+    元のアイテムが選択されている場合は、言語属性を入力します。言語属性はif/elsif引き数の言語を定義する。元のアイテムのオプションを使用している場合は、次のように構造化する必要があります。
 
     ```liquid
     {% if {{custom_attribute.${attribute_name}}} == 'da-DK' %}
@@ -52,7 +52,7 @@ search_tag: Partner
     Original content
     {% endif %}
     ```
-    または、アサインキー/アサイン値m アプリリングを使用します。
+    または、assign キー/値マッピングを使用します。
     ```liquid
     {% if {{custom_attribute.${attribute_name}}} == 'da-DK' %}
       {% assign abc_key1 = "danish_value1" %}
@@ -64,21 +64,21 @@ search_tag: Partner
       {% assign abc_key = "Source language value" %}
     {% endif %}
     ```
-    上記のリキッドは厳守する必要がありますが、言語属性、言語、鍵、数値は調整可能です。<br><br>
+    上記の Liquid に厳密に従う必要がありますが、言語属性と言語、キー、および値は調整可能です。<br><br>
     各言語コードは1 回のみ使用できますが、複数の言語を1 つのSegmentに使用できます。たとえば、次のようになります。
     ```liquid
     {% elsif {{custom_attribute.${attribute_name}}} == 'de-DE' or {{custom_attribute.${attribute_name}}} == 'de-AT' or {{custom_attribute.${attribute_name}}} == 'de-CH' %}
     {% endraw %}
     ```
-5. **Test connection**をクリックします。接続が成功すると、耳にチェックマークがアプリされます。アイコンの上にマウスポインタを置くと、詳細が表示されます。<br><br>
-7. 最後に、**Save**をクリックします。このコネクタは、**Connectors**ページで使用できます。
+5. \[**Test connection**] をクリックします。接続に成功するとチェックマークが表示されます。アイコンの上にマウスポインタを置くと、詳細が表示されます。<br><br>
+7. 最後に、**Save**をクリックします。このコネクターは \[**Connectors**] ページで使用可能になります。
 
-## ステップ3:文節に内容を送信し、Brazeに書き戻す
+## ステップ3:コンテンツを Phrase に送信して Braze に再びエクスポートする
 
-1. まず、[submitter portal](https://support.phrase.com/hc/en-us/articles/5709602111132)を設定して、サブミッターがオンラインリポジトリから直接リクエストにファイルを追加できるようにします。<br><br>
-2. 指定されたワークフロー状態の変更が検出されたときにフレーズTMS が自動的に新しいプロジェクトを作成するようにするには、[Automated Project Creation (APC)](https://support.phrase.com/hc/en-us/articles/5709647363356) を使用します。<br><br>
-3. 選択したコンテンツ項目は、APC の初回実行時にインポートされます。
+1. まず [submitter portal](https://support.phrase.com/hc/en-us/articles/5709602111132) を設定して、送信者がオンラインリポジトリからファイルを直接リクエストに追加できるようにします。<br><br>
+2. 指定されたワークフロー状態の変更が検出されたときに Phrase TMS が新しいプロジェクトを自動的に作成するようにするには、[Automated Project Creation (APC)](https://support.phrase.com/hc/en-us/articles/5709647363356) を使用します。<br><br>
+3. 選択されているコンテンツアイテムは、APC の初回実行時にインポートされます。
 
-[Connector API](https://cloud.memsource.com/web/docs/api#) は、ステップを自動化できます。それ以外の場合は、UI を使用して手動で実行します。[Webフック](https://support.phrase.com/hc/en-us/articles/5709693398812) を使用して、フレーズTMS が特定のイベント(たとえば、ジョブステータスの変更) についてサードパーティシステムに通知するようにすることができます。
+[Connector API](https://cloud.memsource.com/web/docs/api#) は、ステップを自動化できます。それ以外の場合は、UI を使用して手動で実行します。[webhook](https://support.phrase.com/hc/en-us/articles/5709693398812) を使用して、Phrase TMS が特定のイベント (ジョブのステータス変更など) についてサードパーティのシステムに通知するようにできます。
 
 [1]: {{site.baseurl}}/developer_guide/rest_api/basics/#endpoints
diff --git a/_lang/ja/_partners/message_personalization/localization/smartling.md b/_lang/ja/_partners/message_personalization/localization/smartling.md
index b0f0a6878ff..87b129397bd 100644
--- a/_lang/ja/_partners/message_personalization/localization/smartling.md
+++ b/_lang/ja/_partners/message_personalization/localization/smartling.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Smartling
 article_title: Smartling
-description: "このリファレンス記事では、Brazeとローカライゼーション向けクラウドベースのソフト「スマートリング」の提携について概説します。このインテグレーションを使用すると、Brazeでメール テンプレートとコンテンツブロックを変換できます。"
+description: "このリファレンス記事では、Braze と Smartling のパートナーシップについて説明します。Smartling はクラウドベースのローカライゼーションソフトウェアです。この統合により、Braze でメールテンプレートとコンテンツブロックを翻訳できます。"
 alias: /partners/smartling/
 page_type: partner
 search_tag: Partner
@@ -11,21 +11,21 @@ search_tag: Partner
 
 > [Smartling][2] は、Web サイト s、アプリライセンス、およびカスタマーエクスペリエンス s の翻訳を自動化することを目的とした顧客向けのエンドツーエンドの クラウド翻訳マネジメントソフトウェアです。
 
-Brazeとスマートリングインテグレーションを使用すると、メール テンプレートとコンテンツブロックを変換できます。スマートリングは、翻訳中の視覚的な文脈の利点を言語学者に提供し、エラーを減らし、質を維持します。
+Braze と Smartling の統合により、メールテンプレートとコンテンツブロックを翻訳できます。Smartling は、翻訳中に視覚的なコンテキストを利用できるようにすることで、エラーを減らし、品質を維持します。
 
 ## 前提条件
 
 | 要件 | 説明 |
 | ----------- | ----------- |
-| スマートリング・アカウント | この提携の前進タグeを取るには、[Smartlingアカウント][2]が必要です。 |
-| スマートリング翻訳プロジェクト | Brazeをスマートリングに接続するには、まずサインアップし、[翻訳プロジェクト][3]を作成する必要があります。 |
+| Smartling アカウント | このパートナーシップを活用するには、[Smartling アカウント][2]が必要です。 |
+| Smartling 翻訳プロジェクト | Braze アカウントを Smartling に接続するには、まずサインアップし、[翻訳プロジェクト][3]を作成する必要があります。 |
 | Braze REST API キー | すべてのテンプレートとコンテンツブロック権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
-| Braze REST エンドポイント | [Your REST エンドポイント URL][1].エンドポイントは、インスタンスのBraze URL によって異なります。 |
+| Braze REST エンドポイント | [REST エンドポイント URL][1]。エンドポイントはインスタンスの Braze URL に応じて異なります。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-スマートリングBrazeインテグレーションでは、メール テンプレートとコンテンツブロックを翻訳できます。 
+Braze と Smartling の統合により、メールテンプレートとコンテンツブロックを翻訳できます。 
 
 電子メールテンプレート: 
 * HTMLエディタの電子メールのみがサポートされます。 
@@ -36,38 +36,38 @@ Brazeとスマートリングインテグレーションを使用すると、メ
 * コンテンツブロックには、元のバージョンと翻訳されたバージョンの両方が含まれます。
 * リキッドスクリプトは、受信者の言語環境設定に基づいて、ディスプレイの正しい言語を決定します。
 
-### ステップ1:スマートリングTMSでのBraze事業の設定
+### ステップ1:Smartling TMS で Braze プロジェクトを設定する
 
-#### Brazeをスマートリングに接続する
+#### Braze を Smartling に接続する
 
-1. [Smartling][2] で、スマートリングアカウントに[Braze Connector][6] プロジェクトタイプを作成します。 
+1. [Smartling][2] で、Smartling アカウントに [Braze Connector][6] プロジェクトタイプを作成します。 
   - 必要なすべてのターゲット言語がプロジェクトに追加されていることを確認します。
-2. 本事業では、**Settings**> **Braze設定**> **Braze**に接続します。
-3. Braze API のURL とBraze API キーを入力します。
+2. このプロジェクト内から、\[**Settings**] > \[**Braze Settings**] > \[**Connect to Braze**] をクリックします。
+3. Braze API の URL とBraze API キーを入力します。
 4. \[**保存**] をクリックします。
 
-#### 完全なBrazeコネクター構成
+#### Braze コネクター設定を完了する
 
-コネクタ構成については、スマートリング[ドキュメント][3]を参照してください。
+コネクター設定の詳細については、Smartling の[ドキュメント][3]を参照してください。
 
 以前の翻訳リクエストのオートメーション方法を選択します。
 
-**Language Configuration**でソース言語とターゲット言語を設定します。これは、Smartling TMSにコンテンツを取り込み、翻訳をBrazeに送り返すためにコネクターによって使用されます。
+\[**Language Configuration**] でソース言語とターゲット言語を設定します。これは、Smartling TMSにコンテンツを取り込み、翻訳をBrazeに送り返すためにコネクターによって使用されます。
 
 ![][8]
 
 ### ステップ2:Smartling にコンテンツを送信する
 
-Brazeコネクターを接続して設定すると、スマートリングプロジェクトの**Braze**タブにBrazeの内容が表示されます。詳細については、スマートリング[ドキュメント][7]を参照してください。
+Brazeコネクターを接続して設定すると、スマートリングプロジェクトの**Braze**タブにBrazeの内容が表示されます。詳細については、Smartling の[ドキュメント][7]を参照してください。
 
 Smartling は、以下の方法でコンテンツを検索および選択する高度な機能を提供します。
 * キーワード検索
-* Braze内容種別
-* Braze タグギング
+* Braze コンテンツタイプ
+* Braze タグ付け
 
 ![][9]
 
-### ステップ3:Brazeへの変換の追加
+### ステップ3:Braze に翻訳を追加する
 
 翻訳がスマートリングプラットフォームで完了すると、自動的にBrazeに送信されます。スマートリングとBraze間で手動でコンテンツを同期する必要はありません。
 
diff --git a/_lang/ja/_partners/message_personalization/localization/transifex.md b/_lang/ja/_partners/message_personalization/localization/transifex.md
index 8c96779abf4..7189e1c30d5 100644
--- a/_lang/ja/_partners/message_personalization/localization/transifex.md
+++ b/_lang/ja/_partners/message_personalization/localization/transifex.md
@@ -10,26 +10,26 @@ search_tag: Partner
 
 # Transifex
 
-> Transifexは、言語に関係なく、ユーザーベース全体で強固なローカリゼーションを可能にする。
+> Transifex は、あらゆる言語で、ユーザー群にわたる強力なローカライゼーションを支援しています。
 
 BrazeとTransifexの統合は、Connected Contentを活用することで、リソース文字列コレクションを引き出し、言語ベースの条件付き書式の行の代わりに、関連する翻訳をメッセージに含めることができる。これにより、翻訳が自動化され、チームは優れたカスタマー・エクスペリエンスの提供に集中することができる。
 
 {% alert important %}
-2022年4月7日をもって、TransifexはAPIバージョン2と2.5を廃止し、バージョン3に移行した。<br><br>以下の統合手順は、バージョン3のアップデートを反映したものである。コネクテッド・コンテンツのコールを適宜更新する。
+2022年4月7日をもって、Transifex は API バージョン2と2.5を廃止し、バージョン3に移行しました。バージョン2と2.5は動作せず、関連するリクエストは失敗します。<br><br>以下の統合手順は、バージョン3のアップデートを反映したものである。コネクテッドコンテンツ呼び出しを適宜更新します。
 {% endalert %}
 
 ## 前提条件
 
 | 必要条件| 説明|
 | ---| ---|
-|トランシフェックス アカウント | このパートナーシップを利用するには、[トランシフェックスのアカウントが](https://www.transifex.com/signin/)必要である。 |
+|トランシフェックス アカウント | このパートナーシップを活用するには、[Transifexアカウント](https://www.transifex.com/signin/)が必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-Transifexの統合は、Transifexの[リソース翻訳APIを](https://developers.transifex.com/reference/get_resource-translations)使用する。以下のcURLで、自分のアカウントに翻訳に関連するコンテンツ値があるかどうかを確認できる。 
+Transifex 統合では、Transifex の[リソース翻訳 API](https://developers.transifex.com/reference/get_resource-translations) を使用します。次の cURL を使用すると、翻訳に関連付けられたコンテンツ値がアカウントにあるかどうかを確認できます。 
 
-まず、Transifexアカウントにある`<ORGANIZATION_NAME>` 、`<PROJECT_NAME>` 、`<RESOURCE_NAME>` を入力する。次に、`<LANGUAGE>` を翻訳をフィルタリングしたい言語コードに、`<TRANSIFEX_BEARER_TOKEN>` をTransifexの[ベアラートークンに](https://developers.transifex.com/reference/api-authentication)置き換える。
+まず、Transifexアカウントにある `<ORGANIZATION_NAME>`、`<PROJECT_NAME>`、`<RESOURCE_NAME>` を入力します。次に、`<LANGUAGE>` を翻訳をフィルタリングしたい言語コードに、`<TRANSIFEX_BEARER_TOKEN>` をTransifexの[ベアラートークンに](https://developers.transifex.com/reference/api-authentication)置き換える。
 
 ```
 curl --request GET \
@@ -40,9 +40,9 @@ curl --request GET \
 
 例えば、Transifexプロジェクトが`https://www.transifex.com/appboy-3/french2/french_translationspo/` にある場合、`project_name` は "french2"、`resource_name` は "french_translationspo "となる。
 
-## コネクテッド・コンテンツ・メッセージの例
+## コネクテッドコンテンツメッセージの例
 
-このコード例は、Transifexリソース翻訳APIとユーザーの`language` 属性を利用している。ニーズに応じて、文字列オブジェクトをループし、以下のリキッドを使って関連するコンテンツを取り込むことができる：`{{strings.data[X].attributes.strings.other}}`.
+このコード例は、Transifexリソース翻訳APIとユーザーの`language` 属性を利用している。必要に応じて文字列オブジェクトをループし、Liquid `{{strings.data[X].attributes.strings.other}}` を使用して関連するコンテンツを取得できます。
 
 {% raw %}
 ```
diff --git a/_lang/ja/_partners/message_personalization/location.md b/_lang/ja/_partners/message_personalization/location.md
index 2738dae91bc..c61340c0690 100644
--- a/_lang/ja/_partners/message_personalization/location.md
+++ b/_lang/ja/_partners/message_personalization/location.md
@@ -1,6 +1,6 @@
 ---
-nav_title: コンテクスチュアル・ロケーション
-article_title: コンテクスチュアル・ロケーション・パートナー
+nav_title: 状況に基づく位置情報
+article_title: 状況に基づく位置情報のパートナー
 page_order: 1
 
 page_type: landing
@@ -14,7 +14,7 @@ partner_path: "https://www.braze.com/product/alloys/partners/"
 partner_top_header: "Contextual Location"
 
 valid_partner_list:
-- name: アキュウェザー
+- name: AccuWeather
   url: /docs/partners/message_personalization/location/accuweather/
 - name: Foursquare
   url: /docs/partners/message_personalization/location/foursquare/
diff --git a/_lang/ja/_partners/message_personalization/location/accuweather.md b/_lang/ja/_partners/message_personalization/location/accuweather.md
index 2814bac6db4..bdaac5b20c5 100644
--- a/_lang/ja/_partners/message_personalization/location/accuweather.md
+++ b/_lang/ja/_partners/message_personalization/location/accuweather.md
@@ -1,6 +1,6 @@
 ---
-nav_title: アキュウェザー
-article_title: アキュウェザー
+nav_title: AccuWeather
+article_title: AccuWeather
 alias: /partners/accuweather/
 description: "この参考記事では、BrazeとAccuWeatherのパートナーシップについて概説している。AccuWeatherは、マーケティング・キャンペーンをパーソナライズするために使用できる天気APIである。"
 page_type: partner
@@ -8,15 +8,15 @@ search_tag: Partner
 
 ---
 
-# アキュウェザー
+# AccuWeather
 
-> [アキュウェザーは](https://www.accuweather.com/)、世界中の天気予報サービスを提供するメディア企業である。アキュウェザーでは、Braze \[Connected Content][60]. 
+> [AccuWeather](https://www.accuweather.com/) は、世界中で気象予報サービスを提供するメディア企業です。AccuWeather を使用すると、マーケティングキャンペーンを強化、パーソナライズし、Braze \[コネクテッドコンテンツ][60]]を使用して翻訳を自動化できます。 
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| アキュウェザーAPIキー | リクエストURLに使用する互換性のあるAPIキーについては、アキュウェザーアカウントマネージャーに問い合わせること。<br><br>詳細な手順は、\[AccuWeather Enterprise API][57] page]に記載されている。 |
+| AccuWeather API キー | リクエスト URL で使用する互換性のある API キーについては、AccuWeather アカウントマネージャーにお問い合わせください。<br><br>詳細な手順は、\[AccuWeather Enterprise API][57] page]に記載されている。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 利用可能なAccuWeather API
@@ -25,20 +25,20 @@ search_tag: Partner
 
 | API | 説明 |
 |---|---|
-|\[所在地][48] | 希望の場所のロケーションキーを取得する。ロケーションキーを使って、ForecastまたはCurrent Conditions APIから気象データを取得する。 |
-| 予想][49] | 特定の場所の予報情報を得る。 |
-| \[現在の状況][50] | 特定の場所の現況データを取得する。 |
-| \[インデックス][51] | 特定の場所の日次指数値を取得する。インデックスの入手可能性は地域によって異なる。 |
-| \[ウェザーアラーム][52] | 特定の場所の天気アラームを取得する。AccuWeatherの天気予報アラームは、その場所の毎日の予報を使って決定される。予報天候が\[特定の閾値][58]]を満たすか超える場合、その場所にアラームが存在する。 |
-| \[アラート][53] | 政府気象機関や世界的な気象警報プロバイダーから、悪天候警報を受け取ることができる。 |
-| \[イメージ][54] | レーダーと衛星画像を入手する。 |
-| \[トロピカル][55] | 世界中の熱帯低気圧の現在位置、過去位置、予報を入手できる。 |
-| 翻訳][56] | 利用可能な言語のリストを取得する。特定のフレーズグループの翻訳を取得する。 |
+|\[Locations][48] | 希望の場所のロケーションキーを取得する。ロケーションキーを使用して、Forecast API または Current Conditions API から気象データを取得します。 |
+| \[Forecast][49] | 特定の場所の予報情報を得る。 |
+| \[Current Conditions][50] | 特定のロケーションの Current Conditions データを取得します。 |
+| \[Indices][51] | 特定の場所の日次指数値を取得する。インデックスの入手可能性は地域によって異なる。 |
+| \[Weather Alarms][52] | 特定の場所の天気アラームを取得する。AccuWeatherの天気予報アラームは、その場所の毎日の予報を使って決定される。天気予報が\[特定のしきい値][58]]を満たしているか超えている場合、そのロケーションにアラームが存在します。 |
+| \[Alerts][53] | 政府の気象庁や世界的な気象警報プロバイダーから悪天候警報を取得します。 |
+| \[Imagery][54] | レーダーと衛星画像を入手する。 |
+| \[Tropical][55] | 世界中の熱帯低気圧の現在位置、過去の位置、予報を取得します。 |
+| \[Translations][56] | 利用可能な言語のリストを取得する。特定のフレーズグループの翻訳を取得します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-## コネクテッド・コンテンツの例
+## コネクテッドコンテンツの例
 
-次の例は、コネクテッド・コンテンツの呼び出しが、ユーザーのアメリカの郵便番号の現在の状況に基づいて、2つの異なるタイプのメッセージを表示することを示している。AccuWeather locations and current conditions APIエンドポイントが使用される。
+次に、米国内のユーザーの郵便番号に対応する場所の現在の状況に基づいて、2つの異なるタイプのメッセージを表示するコネクテッドコンテンツ呼び出しの例を示します。AccuWeather の Locations API エンドポイントと Current Conditions API エンドポイントが使用されています。
 {% raw %}
 
 ```liquid
@@ -58,14 +58,14 @@ Enjoy the weather!
 
 ![雨が降っています」というコネクテッド・コンテンツのプッシュメッセージ！アンドロイド端末で表示される「傘を持とう][17]{: style="max-width:40%"}
 
-つのコネクテッド・コンテンツの呼び出しの内訳は、以下の例で見ることができる。
+2つのコネクテッドコンテンツ呼び出しの詳細を以下の例に示します。
 
 {% tabs %}
-{% tab 所在地 %}
+{% tab Locations %}
 #### ロケーションAPIの例
 
 {% raw %}
-最初の`connected_content` タグ内で、[Locations APIへの](https://apidev.accuweather.com/developers/locationsAPIguide)GETリクエストが行われる。この例では、郵便番号のカスタム属性がない場合、ユーザーの`{{${city}}}` 。
+1番目の `connected_content` タグ内で、[Locations API](https://apidev.accuweather.com/developers/locationsAPIguide) に対する GET リクエストが実行されます。この例では、郵便番号のカスタム属性がない場合には、代わりにユーザーの `{{${city}}}` を利用できます。
 
 ```
 {% connected_content http://dataservice.accuweather.com/locations/v1/postalcodes/{{${country}}}/search?q={{custom_attribute.${Zip Code}}}&apikey={your API key} :save location_info %}
@@ -150,14 +150,14 @@ Enjoy the weather!
 ]
 ```
 
-Key "IDは、2番目のGETリクエストで使われるので、便利な変数である。
-このJSONオブジェクトは、URLの後に`:save location_info` を指定することで、ローカル変数`location_info` に格納することができる。
+「Key」ID は有用な変数であり、2番目の GET リクエストで使用されています。
+この JSON オブジェクトは、URL の後に `:save location_info` を指定することで、ローカル変数 `location_info` に格納できます。
 {% endtab %}
-{% tab 現在の状況 %}
+{% tab Current Conditions %}
 
-#### 現状APIの例
+#### Current Conditions API の例
 
-2つ目の`connected_content` 、[現在の状況APIに](https://apidev.accuweather.com/developers/currentConditionsAPIGuide)GETリクエストが行われる。リクエストURLに**ロケーションキーを**追加する必要がある。`connected_content` ：
+2番目の `connected_content` タグで、[Current Conditions API](https://apidev.accuweather.com/developers/currentConditionsAPIGuide) に対する GET リクエストが実行されます。リクエスト URLに **ロケーションキー**を追加する必要があります。`connected_content` タグの例を次に示します。
 
 {% raw %}
 ```
@@ -196,14 +196,14 @@ Key "IDは、2番目のGETリクエストで使われるので、便利な変数
 
 `{{local_weather[0].WeatherText}}` を参照することで、[WeatherText](https://apidev.accuweather.com/developers/currentConditionsAPIGuide)の出力がどうなるかをテストすることができる。
 
-APIコールが`{{local_weather[0].WeatherText}}` 、`Rain` を返すと、ユーザーはプッシュを受け取る。
+API 呼び出しが `{{local_weather[0].WeatherText}}` で応答し、`Rain` を返す場合、ユーザーはプッシュを受信します。
 
 {% endraw %}
 {% endtab %}
 {% endtabs %}
 
 [16]: [success@braze.com](mailto:success@braze.com)
-[17]: {% image_buster /assets/img_archive/connected_weather_push2.png %} 「コネクテッド・コンテンツ・プッシュの使用例
+[17]: {% image_buster /assets/img_archive/connected_weather_push2.png %} 「コネクテッドコンテンツのプッシュの使用例」
 [48]: https://apidev.accuweather.com/developers/locationsAPIguide
 [49]: https://apidev.accuweather.com/developers/forecastsAPIguide
 [50]: https://apidev.accuweather.com/developers/currentConditionsAPIGuide
@@ -215,4 +215,4 @@ APIコールが`{{local_weather[0].WeatherText}}` 、`Rain` を返すと、ユ
 [56]: https://apidev.accuweather.com/developers/translationsApiGuide
 [57]: https://apidev.accuweather.com/developers/
 [58]: https://apidev.accuweather.com/developers/weatheralarms
-[60]: {{site.baseurl}}/user_guide/パーソナライゼーションとダイナミックスcontent/connected_content/about_connected_content/
+[60]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/
diff --git a/_lang/ja/_partners/message_personalization/location/bluedot.md b/_lang/ja/_partners/message_personalization/location/bluedot.md
index ad072459f9e..efa57c98f73 100644
--- a/_lang/ja/_partners/message_personalization/location/bluedot.md
+++ b/_lang/ja/_partners/message_personalization/location/bluedot.md
@@ -10,7 +10,7 @@ search_tag: Partner
 
 # Bluedot
 
-> [ブルードットは](https://bluedot.io/)、正確でわかりやすいジオフェンシングプラットフォームをアプリに提供するロケーションプラットフォームだ。BluedotのSDKを使用して、よりスマートなメッセージを発信し、モバイル注文のチェックインを自動化し、ワークフローを最適化し、摩擦のない体験を生み出す。 
+> [Bluedot](https://bluedot.io/) は、アプリのための正確でシンプルなジオフェンシングプラットフォームを提供するロケーションプラットフォームです。BluedotのSDKを使用して、よりスマートなメッセージを発信し、モバイル注文のチェックインを自動化し、ワークフローを最適化し、摩擦のない体験を生み出す。 
 
 BrazeとBluedotの統合により、Bluedotのジオフェンス位置情報サービスを利用してユーザーイベントを作成し、ジャーニーやキャンペーンの構築、顧客の行動や関心の分析に利用できる。ユーザーがデバイス上で発生させたイベント（入退場）は、すべての関連情報とともに即座にBrazeに送信される。 
 
@@ -18,38 +18,38 @@ BrazeとBluedotの統合により、Bluedotのジオフェンス位置情報サ
 
 | 必要条件 | 説明 |
 |---|---|
-| ブルードット・アカウント | この統合を利用するには、ブルードット・アカウントが必要である。 |
+| Bluedot アカウント | この統合を活用するには、Bluedot アカウントが必要です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## ユースケース
 
-ブルードットが提供するカスタム・イベント・ロケーション情報は、以下のような一般的なユースケースを達成するためにキャンペーンで使用することができる：
+Bluedot によって提供されるカスタムイベントロケーション情報は、キャンペーンで次のような一般的なユースケースを実現するために使用できます。
 - [`QSR`](https://bluedot.io/solutions/quick-service-restaurants/) (クイックサービスレストラン)
 - [`Click and Collect`](https://bluedot.io/solutions/click-and-collect/)
 - [`Drive-Thru`](https://bluedot.io/solutions/qsr-drive-thru/) 
 
 ## 統合
 
-### ステップ1:ブルードット・プロジェクトを作成する
-ブルードット・アカウントを設定し、[ブルードット・キャンバスのダッシュボードに](https://docs.bluedot.io/canvas/)ログインする。新規プロジェクトの作成方法については、[ブルードットのドキュメントを](https://docs.bluedot.io/canvas/creating-a-new-project/)参照されたい。
+### ステップ1:Bluedot プロジェクトを作成する
+Bluedot アカウントを設定し、[Bluedot キャンバスダッシュボード](https://docs.bluedot.io/canvas/)にログインします。新しいプロジェクトの作成方法については、[Bluedot のドキュメント](https://docs.bluedot.io/canvas/creating-a-new-project/)を参照してください。
 
 ### ステップ2:SDKを統合する
-[Bluedot-Braze統合](https://docs.bluedot.io/integrations/braze-integration/)ドキュメントに記載されている手順で、アプリにBluedot Point SDKとBraze SDKを統合する。
+[Bluedot と Braze の統合](https://docs.bluedot.io/integrations/braze-integration/)に関するドキュメントに記載されている手順を使用して、Bluedot Point SDK とBraze SDK をアプリに統合します。
 
-### ステップ3:ブルードットSDKを認証する
-ステップ 1 で作成した`projectId` を使用して、Bluedot Point SDK を認証する。
+### ステップ3:Bluedot SDK を認証する
+ステップ1で作成した `projectId` を使用して Bluedot Point SDK を認証します。
 
-### ステップ4:ブレイズでブルードット・イベントを使う
+### ステップ4:Braze で Bluedot イベントを使用する
 
-#### <b>メッセージのトリガー</b>
+#### メッセージのトリガー
 
-ブルードットSDKによって生成されたロケーション・イベントからアクションを起こすプッシュ・キャンペーンやキャンバスを設定することができる。この統合ルートは、ユーザーが会場や興味のある場所に入った直後のリアルタイムのメッセージングや、ユーザーがその場を離れた後の遅延したフォローアップ・コミュニケーションに最適である。
+Bluedot SDK によって生成されたロケーションイベントから起動するプッシュキャンペーンまたはキャンバスを設定できます。この統合ルートは、ユーザーが会場や興味のある場所に入った直後のリアルタイムのメッセージングや、ユーザーがその場を離れた後の遅延したフォローアップ・コミュニケーションに最適である。
 
 Brazeでアクションベースのキャンペーンを設定し、設定した場所に基づいてメッセージを送信する。トリガーには、以下のスクリーンショットに示すように、`bluedot_entry` または`bluedot_exit` のカスタムイベントを使用する：
 
-![配信ステップにおけるアクションベースのキャンペーン。ここでは、ユーザーがカスタム`bluedot_entry` または`bluedot_exit` イベントを実行した場合にキャンペーンを送信する2つのスケジュールオプションがある。]({%image_buster /assets/img_archive/Campaign-Delivery-BD.png %}){: style="max-width:80%"}
+![配信ステップでのアクションベースのキャンペーン。ここでは、ユーザーがカスタム`bluedot_entry` または`bluedot_exit` イベントを実行した場合にキャンペーンを送信する2つのスケジュールオプションがある。]({%image_buster /assets/img_archive/Campaign-Delivery-BD.png %}){: style="max-width:80%"}
 
 #### ユーザーへのターゲット設定
 
 ワークスペースのターゲットが**「すべてのユーザー」**であることを確認する。
-![] （{%image_buster /assets/img_archive/Campaign-Target_users-BD.png %} ）「すべてのユーザー」を希望セグメントとして選択するよう、ターゲットユーザーのステップで促すアクションベースのキャンペーン。{: style="max-width:80%"}
\ No newline at end of file
+![セグメントとして「すべてのユーザー」を選択するように促すターゲットユーザーステップを使用したアクションベースのキャンペーン。]({%image_buster /assets/img_archive/Campaign-Target_users-BD.png %}){: style="max-width:80%"}
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_personalization/location/foursquare.md b/_lang/ja/_partners/message_personalization/location/foursquare.md
index f3fb9f9ba07..f72d416dec4 100644
--- a/_lang/ja/_partners/message_personalization/location/foursquare.md
+++ b/_lang/ja/_partners/message_personalization/location/foursquare.md
@@ -2,7 +2,7 @@
 nav_title: Foursquare
 article_title: Foursquare
 alias: /partners/foursquare/
-description: "この参考記事では、Brazeと位置情報プラットフォームであるFoursquareのパートナーシップについて概説している。"
+description: "このリファレンス記事では、Braze と Foursquare のパートナーシップについて説明します。Foursquare は、位置情報に基づいてリアルタイムでイベントをトリガーする機能を提供する位置情報データプラットフォームです。"
 page_type: partner
 search_tag: Partner
 
@@ -12,45 +12,45 @@ search_tag: Partner
 
 {% multi_lang_include video.html id="G2ZoJqZGqrU" align="right" %}
 
-> [Foursquareは](https://foursquare.com/)、Brazeのキャンペーンに位置情報のターゲティングを提供する位置情報プラットフォームである。iOSとAndroidアプリでFoursquareのPilgrim SDKを使用して、位置情報に基づいたリアルタイムのイベントトリガーを提供し、Foursquareの強力なジオターゲティング機能を利用して、Brazeで関連性の高いパーソナライズされたメッセージを送信できる。
+> [Foursquare](https://foursquare.com/) は、Braze キャンペーンに位置情報データターゲティング機能を提供する位置情報データプラットフォームです。iOSとAndroidアプリでFoursquareのPilgrim SDKを使用して、位置情報に基づいたリアルタイムのイベントトリガーを提供し、Foursquareの強力なジオターゲティング機能を利用して、Brazeで関連性の高いパーソナライズされたメッセージを送信できる。
 
 ## 前提条件
 
 | 必要条件 | 説明 |
 |---|---|
-| フォースクエアアカウント | このパートナーシップを利用するには、Foursquareのアカウントが必要である。 |
+| Foursquare アカウント | このパートナーシップを利用するには、Foursquareのアカウントが必要である。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
-| BrazeのワークスペースとApp ID | BrazeのワークスペースとApp IDは、[開発者コンソールで]({{site.baseurl}}/api/api_key/)確認できる。 |
+| BrazeのワークスペースとApp ID | Braze ワークスペースと アプリ ID は[開発者コンソール]({{site.baseurl}}/api/api_key/)で確認できます。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 統合
 
-2つのプラットフォームを統合するには、2つのSDKを統合し、一致するユーザー・フィールドをマッピングする必要がある。ピルグリムSDKを統合すると、デバイス上またはウェブフックに位置情報イベントを受信できるようになる。 
+2つのプラットフォームを統合するには、2つの SDK を統合し、一致するユーザーフィールドをマッピングする必要があります。Pilgrim SDK を統合すると、デバイスまたは Webhook で位置情報イベントを受け取ることができます。 
 
 ### ステップ1:ユーザーIDフィールドをマップする
 
-つのSDK間でフィールドを正しくマッピングするには、Braze SDKの[`changeUser` メソッドと]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/setting_user_ids/#setting-user-ids)Pilgrim SDKの`setUserId` メソッドを使用して、両方のシステムで同じユーザーIDを設定する。 [`PilgrimUserInfo`](https://developer.foursquare.com/docs/pilgrim-sdk/advanced-setup-guide#custom-user-data)のメソッドを使用する。
+2つの SDK 間でフィールドを正しくマッピングするには、Braze SDK の[`changeUser` メソッド]({{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/setting_user_ids/#setting-user-ids)と Pilgrim SDK の [`PilgrimUserInfo`](https://developer.foursquare.com/docs/pilgrim-sdk/advanced-setup-guide#custom-user-data) の `setUserId` メソッドを使用して、両方のシステムで同じユーザー ID を設定します。
 
-### ステップ2:ピルグリムコンソールを設定する
-![グループID、AndroidアプリID、iOSアプリIDを尋ねるピルグリムのコンソールの画像。][2]{: style="float:right;max-width:40%;margin-left:15px;"}
+### ステップ2:Pilgrim コンソールを設定する
+![Group ID、Android App ID、iOS App ID の入力を促す Pilgrim コンソール。][2]{: style="float:right;max-width:40%;margin-left:15px;"}
 
 Braze開発者コンソールでワークスペースとApp IDを見つける。次に、Foursquare Pilgrim ConsoleにBraze REST API KeyとApp IDを入力する。
 
-ピルグリムコンソールを設定すると、ピルグリムSDKがロケーションイベントを記録し、Brazeに転送する。詳細は[Foursquare開発者サイトを](https://developer.foursquare.com/)参照のこと。
+Pilgrim コンソールの設定が完了したら、Pilgrim SDK が位置情報イベントを記録して Braze に転送します。これにより、条件を満たした顧客をリターゲティングおよびセグメント化できます。詳細は[Foursquare開発者サイトを](https://developer.foursquare.com/)参照のこと。
 
 {% alert important %}
-ピルグリムSDKでは、位置情報サービスを有効にする必要がある。
+Pilgrim SDK を使用するには、位置情報サービスを有効にする必要があります。
 {% endalert %}
 
 ## メッセージのトリガー
 
-統合がセットアップされると、ピルグリムSDKによって生成されたロケーションイベントからアクションを起こすキャンペーンやキャンバスをセットアップすることができる。この統合ルートは、ユーザーが興味のある会場に入った直後のリアルタイムのメッセージングや、お礼状やリマインダーのような、ユーザーが去った後の遅れたフォローアップ・コミュニケーションに最適である。
+統合が設定されたら、Pilgrim SDK により生成される位置情報イベントからアクションを実行するキャンペーンやキャンバスを設定できます。この統合ルートは、ユーザーが特定の会場に入った直後にリアルタイムメッセージを送信する場合、または退場後にフォローアップコミュニケーション (お礼やリマインダーなど) を行う場合に最適です。
 
 設定した場所に基づいてメッセージを送信するキャンペーンを行う：
-- **アクションベース配信で**送信するBrazeキャンペーンまたはキャンバスを作成する
-- トリガーには、以下のスクリーンショットに示すように、`locationType` のイベント・プロパティ・フィルタを持つ`arrival` のカスタム・イベントを使用する。
+- **アクションベースの配信**で送信する Braze キャンペーンまたはキャンバスを作成する
+- トリガーには、以下のスクリーンショットに示すように、`locationType` のイベントプロパティフィルターを含むカスタムイベント `arrival` を使用します。
 
-![配送ステップにおけるアクションベースのキャンペーンで、「カスタムイベントを実行する」オプションとして「到着」が選択されていることを示す。]({% image_buster /assets/img_archive/action-based-campaign.png %})
+![配送ステップにおけるアクションベースのキャンペーン。「カスタムイベントを実行」オプションとして「arrival」が選択されており、「locationType」が「home」と等しいという条件が設定されている。]({% image_buster /assets/img_archive/action-based-campaign.png %})
 
 ## リターゲティング
 
@@ -58,7 +58,7 @@ Braze開発者コンソールでワークスペースとApp IDを見つける。
 
 ![ターゲットユーザーのステップで、"last_location "が "Pizza Place "と等しいことを示すアクションベースのキャンペーン。]({% image_buster /assets/img_archive/last-location-segment.png %})
 
-Brazeでは、特定の時間帯にFoursquareの`primaryCategoryId` 、特定のタイプの会場を訪れたユーザーをセグメントすることもできる。このデータポイントをリターゲティングのユースケースに活用するには、オーディエンスのセグメンテーションプロセス中に、イベントプロパティとして`primaryCategoryId` 。Foursquare API と Pilgrim SDK で使用されるユーザーとプロパティを確認するには、[Foursquare の開発者サイトを](https://developer.foursquare.com/)参照のこと。
+また Braze で、特定のタイプの会場を訪問したユーザーを、特定の期間内の Foursquare の `primaryCategoryId` に基づいてセグメント化することもできます。このデータポイントをリターゲティングのユースケースに利用するには、オーディエンスのセグメンテーションプロセスでイベントプロパティとして `primaryCategoryId` をログに記録します。Foursquare API と Pilgrim SDK で使用されるユーザーとプロパティを確認するには、[Foursquare の開発者サイトを](https://developer.foursquare.com/)参照のこと。
 
 [1]: {% image_buster /assets/img_archive/dashboard_keys_locations.png %}
 [2]: {% image_buster /assets/img_archive/pilgrim-dev-console.png %}
\ No newline at end of file
diff --git a/_lang/ja/_partners/message_personalization/location/gimbal.md b/_lang/ja/_partners/message_personalization/location/gimbal.md
index 8a5d525b269..3d60f0dcc1c 100644
--- a/_lang/ja/_partners/message_personalization/location/gimbal.md
+++ b/_lang/ja/_partners/message_personalization/location/gimbal.md
@@ -10,32 +10,32 @@ search_tag: Partner
 
 # Gimbal
 
-> [ジンバルは](https://gimbal.com/)、位置情報を使ってマーケティングの関連性を完璧にすることを可能にする。同社の位置情報SDKは、ジオフェンシング・ソフトウェアやビーコンと組み合わせることで、関連性が高く、パーソナライズされた、近接を意識したモバイル体験を提供する。
+> [Gimbal](https://gimbal.com/) は、位置情報データを活用して、適切なマーケティングのパーフェクトな実行を支援しています。同社の位置情報SDKは、ジオフェンシング・ソフトウェアやビーコンと組み合わせることで、関連性が高く、パーソナライズされた、近接を意識したモバイル体験を提供する。
 
-ビーコンやジオフェンスサポートをBrazeのターゲティングやメッセージング機能と組み合わせることで、ユーザーの物理的な行動を詳しく知り、それに応じてメッセージを送ることができる。このパートナーシップの統合によって、さまざまな使用例が可能になる：
-- **マーケティングだ：**文脈に関連したメッセージを送り、体験型の消費者ジャーニーを構築する。
-- **競合分析：**消費者の傾向やパターンを理解するために、競合する場所の周辺にトリガーを設定する。
-- **オーディエンス・インサイト**ユーザーの訪問行動を理解し、それらの学習に基づいてさらにセグメント化する。
+ビーコンやジオフェンスサポートをBrazeのターゲティングやメッセージング機能と組み合わせることで、ユーザーの物理的な行動を詳しく知り、それに応じてメッセージを送ることができる。このパートナー連携により、次のようなさまざまなユースケースが可能になります。
+- **マーケティング:**状況に対応した関連性のあるメッセージを送信し、体験型の消費者ジャーニーを構築します。
+- **競合分析:**消費者の傾向やパターンを理解するために、競合ロケーション周辺にトリガーを設定します。
+- **オーディエンスインサイト:**ユーザーの訪問行動を理解し、それらの学習に基づいてさらにセグメント化する。
 
 ## 前提条件
 
 | 必要条件| 説明|
 | ---| ---|
-| [ジンバル・マネージャー・アカウント][1] | このパートナーシップを利用するには、ジンバル・マネージャーのアカウントが必要である。 |
-|[ジンバル・ロケーションSDK](https://docs.gimbal.com/index.html) | Gimbal Location SDKは、近接ビーコンとジオフェンスを使用したマクロおよびミクロの位置情報ベースのモバイル体験を提供し、アプリのユーザーとより効果的なコミュニケーションを可能にする。SDKを実装し、ジオフェンス（またはビーコン）を設定する必要がある。 |
+| [Gimbal マネージャーアカウント][1] | このパートナーシップを活用するには、Gimbal マネージャーアカウントが必要です。 |
+|[Gimbal Location SDK](https://docs.gimbal.com/index.html) | Gimbal Location SDK は、近接ビーコンとジオフェンスを使用してマクロおよびミクロの位置情報ベースのモバイルエクスペリエンスを提供し、アプリのユーザーとのより効果的なコミュニケーションを可能にします。SDK を実装し、ジオフェンス (またはビーコン) を設定しておく必要があります。 |
 | Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、Brazeダッシュボードの**「設定」**>「**APIキー**」から作成できる。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## SDKの統合
 
-BrazeとGimbalを統合するには、Gimbal Location SDKを実装し、Gimbal managerアカウントを作成する必要がある。Android、FireOS、iOS用の以下の統合は、ユーザーが新しい場所に入るたびにユニークなカスタムイベントを作成し、これらのイベントは、キャンペーンやキャンバスでトリガーやリターゲティングに使用することができる。
+Braze と Gimbal を統合するには、Gimbal Location SDK を実装し、Gimbal マネージャーアカウントを作成する必要があります。Android、FireOS、iOS 向けの以下の統合では、ユーザーが入る新しい場所ごとに固有のカスタムイベントが作成されます。これらのイベントをキャンペーンやキャンバスでのトリガーやリターゲティングに使用できます。
 
 50以上の場所を作成することが予想される場合は、一般的な`Places Entered` カスタムイベントを作成し、イベントプロパティとして場所名を追加することを推奨する。 
 
-1. [ジン][2] [バルのドキュメントの][3]指示に従って、AndroidとiOS用の[ジンバルSDKを][2]アプリに統合する。
+1. [Gimbal ドキュメント][3]の手順に従って [Gimbal SDK][2] for Android and iOS をアプリに統合します。
 2. Gimbal's[place REST APIを使って][4]、ユーザー`places` を取得する。
-3. Braze[REST APIキーを][5]入力して、GimbalアカウントをBrazeにリンクする。
-4. Braze SDKで[カスタムイベントを][6]設定する。ジンバルは[Android、FireOS][7]、[iOS][8]用のBrazeと統合できる。
+3. Braze [REST API キー][5]を入力して、Gimbal アカウントを Braze にリンクします。
+4. Braze SDKで[カスタムイベントを][6]設定する。[Android および FireOS][7] と [iOS][8] 向けに、Braze に Gimbal を統合できます。
 5. これらのイベントのログ・プロパティ（場所名、滞留時間）。
 6. Brazeでキャンペーンやキャンバスをトリガーするには、これらのプロパティとイベントを使用する。 
 
diff --git a/_lang/ja/_partners/message_personalization/location/loplat.md b/_lang/ja/_partners/message_personalization/location/loplat.md
index 99934e152f4..8fbac2bf490 100644
--- a/_lang/ja/_partners/message_personalization/location/loplat.md
+++ b/_lang/ja/_partners/message_personalization/location/loplat.md
@@ -10,7 +10,7 @@ search_tag: Partner
 
 # loplat
 
-> [Loplat][1]は、主要なオフラインの位置情報ベースのプラットフォームです。loplat SDK を使用して店舗の来店者数を賢く増やし、店内購入を促進するマーケティングキャンペーンを実行します。キャンペーン終了後、フットフォール分析を通じて店舗のパフォーマンスを測定できます。
+> [Loplat][1]は、主要なオフラインの位置情報ベースのプラットフォームです。loplat SDK を使用して店舗の来店者数を賢く増やし、店内購入を促進するマーケティングキャンペーンを実行します。キャンペーン終了後、フットフォール分析で店舗のパフォーマンスを測定できます。
 
 Brazeとloplatの統合により、loplatの位置情報サービス（店舗POIおよびカスタムジオフェンス）を使用して、ジオ文脈に応じたマーケティングキャンペーンをトリガーし、オフラインセグメンテーションを使用してカスタムイベントを作成できます。ユーザーがloplat Xで設定したターゲットロケーションを訪れると、キャンペーンおよびロケーション情報が即座にBrazeに送信されます。
 
@@ -25,7 +25,7 @@ Brazeとloplatの統合により、loplatの位置情報サービス（店舗POI
 
 ## ユースケース
 
-ロプラットが提供するカスタムイベントの位置情報は、次のようなユースケースを達成するためにキャンペーンで使用できます:
+loplat によって提供されるカスタムイベントロケーション情報は、キャンペーンで次のようなユースケースを実現するために使用できます。
 
 - [免税プロモーションアラート][2]
     - 空港の搭乗ゲート付近にいるユーザーに免税店の割引クーポンを送信します。
@@ -53,7 +53,7 @@ Braze ダッシュボードで新しい API キーを作成します。API キ
 
 #### アクションベースの配信
 
-統合により、ジオフェンス情報、地域、ブランド名、または店舗名を送信することで、位置条件を適用できます。さらに、作成したカスタムイベントを使用してセグメントを追加したり、コンバージョンを割り当てたりできます。
+統合により、ジオフェンス情報、地域、ブランド名、または店舗名を送信することで、ロケーション条件を適用できます。さらに、作成したカスタムイベントを使用してセグメントを追加したり、コンバージョンを割り当てたりできます。
 1. [loplat X ユーザーのガイド][6]の指示に従って、loplat X キャンペーンを作成します。
 2. **キャンペーンメッセージ設定**の下にカスタムイベントを追加し、キャンペーンを開始します。
 3. Brazeのダッシュボードに移動して、**アクションベースの配信**で送信するキャンペーンまたはキャンバスを作成します。
diff --git a/_lang/ja/_partners/message_personalization/location/radar.md b/_lang/ja/_partners/message_personalization/location/radar.md
index 997a9599460..a58786cfbb6 100644
--- a/_lang/ja/_partners/message_personalization/location/radar.md
+++ b/_lang/ja/_partners/message_personalization/location/radar.md
@@ -2,7 +2,7 @@
 nav_title: Radar
 article_title: Radar
 alias: /partners/radar/
-description: "このリファレンス記事では、位置情報と\"トラッキングをiOSとAndroid アプリsに追加するために、ジオフェンシングプラットフォームであるBrazeとRadarの提携について概説します。"
+description: "このリファレンス記事では、Braze と Radar のパートナーシップについて説明します。Radar は、位置情報コンテキストとトラッキングを iOS アプリと Android アプリに追加するためのジオフェンシングプラットフォームです。"
 page_type: partner
 search_tag: Partner
 
@@ -10,29 +10,29 @@ search_tag: Partner
 
 # Radar
 
-> [Radar](https://www.onradar.com/) は、先頭のジオフェンシングと位置"トラッキング プラットフォームです。Radar プラットフォームには3つの主力商品があります。[Geofences](https://radar.io/product/geofencing), [Trip Tracking](https://radar.io/product/trip-tracking), and [Geo APIs](https://radar.io/product/api).Brazeの業界をリードするエンゲージメント プラットフォームとRadarの業界をリードするジオフェンシング機能を組み合わせることで、ロケーションベースの幅広い商品・サービス体験を通じて収益とロイヤルティを牽引することができます。これには、集配"トラッキング、場所-トリガーの通知s、文脈に応じた or 状況に即した パーソナライゼーション、場所の確認、店舗のロケーター、住所の自動完了などが含まれます。
+> [Radar](https://www.onradar.com/) は、業界をリードするジオフェンシングおよび位置情報追跡プラットフォームです。Radar プラットフォームには3つの主力商品があります。[Geofences](https://radar.io/product/geofencing)、[Trip Tracking](https://radar.io/product/trip-tracking)、および [Geo APIs](https://radar.io/product/api)。Brazeの業界をリードするエンゲージメント プラットフォームとRadarの業界をリードするジオフェンシング機能を組み合わせることで、ロケーションベースの幅広い商品・サービス体験を通じて収益とロイヤルティを牽引することができます。これには、集荷と配送の追跡、ロケーショントリガー通知、コンテキストパーソナライゼーション、ロケーション検証、ストアロケーター、住所オートコンプリートなどが含まれます。
 
-BrazeとRadarの統合により、高度なロケーションベースのキャンペーン トリガーと、豊富なファーストパーティロケーションデータを使用したユーザープロファイルエンリッチメントにアクセスできます。Radar ジオフェンスまたはトリップ"トラッキングが生成されると、カスタムイベントs およびユーザー 属性s がリアルタイムでBrazeに送信されます。これらの事象および属性sは、次いで、位置に基づくキャンペーンsをトリガーし、ラストマイルのピックアップおよび配送オペレーションを駆動し、フリートおよび配送物流を監視し、または位置パターンに基づいてユーザー Segmentsを構築するために使用することができる。 
+BrazeとRadarの統合により、高度なロケーションベースのキャンペーン トリガーと、豊富なファーストパーティロケーションデータを使用したユーザープロファイルエンリッチメントにアクセスできます。Radar のジオフェンスまたは移動追跡イベントが生成されると、カスタムイベントとユーザー属性がリアルタイムで Braze に送信されます。これらの事象および属性sは、次いで、位置に基づくキャンペーンsをトリガーし、ラストマイルのピックアップおよび配送オペレーションを駆動し、フリートおよび配送物流を監視し、または位置パターンに基づいてユーザー Segmentsを構築するために使用することができる。 
 
-さらに、Radar Geo API を活用して、[Connected Content]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/) を通じてマーケティング キャンペーンを強化またはパーソナライズできます。 
+さらに、Radar Geo API を活用して、[コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/)を介してマーケティングキャンペーンを強化・パーソナライズできます。 
 
 ## 前提条件
 
 | 要件 | 説明 |
 |---|---|
-| Radar勘定 | この提携の前進タグeを考慮するには、Radarな考慮が必要である。 |
-| Braze REST API キー | `users.track` 権限を持つBraze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
-| アプリ識別子 | [アプリ 識別子]({{site.baseurl}}/api/identifier_types/?tab=app%20ids) は、**設定**> **API Keys** のBraze ダッシュボード内にあります。 |
+| Radar アカウント | このパートナーシップを活用するには、Radar アカウントが必要です。 |
+| Braze REST API キー | `users.track` 権限を持つ Braze REST API キー。<br><br> これは、**Settings** > **API Keys** のBraze ダッシュボードで作成できます。 |
+| アプリ識別子 | [アプリ識別子]({{site.baseurl}}/api/identifier_types/?tab=app%20ids)は、Braze ダッシュボードの \[**設定**] > \[**API キー**] で確認できます。 |
 | iOS API キー<br>Android API キー | これらのAPI キーsは、**設定**>**アプリ設定**のBraze ダッシュボード内にあります。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 ## 統合
 
-Braze とRadar SDK s の間でデータマッピングを行うには、両方のシステムで同じユーザー ID s またはユーザー別名を設定する必要があります。これは、Braze SDKの`changeUser()` メソッドとRadar SDKの`setUserId()` メソッドを使用して実行できます。
+Braze SDK と Radar SDK 間でデータをマッピングするには、両方のシステムで同じユーザー ID またはユーザーエイリアスを設定する必要があります。これは、Braze SDK の`changeUser()` メソッドと、Radar SDK の`setUserId()` メソッドを使用して実行できます。
 
 統合を有効にするには:
 
-1. [Integrations](https://radar.com/documentation/integrations) ページのRadarで、Braze を見つけます。
+1. Radar の \[[Integrations](https://radar.com/documentation/integrations)] ページで Braze を見つけます。
 1. **Enabled**を**Yes**に設定します。
 3. アプリ 識別子とAPI キーs に貼り付けます。
 
@@ -42,37 +42,37 @@ Braze とRadar SDK s の間でデータマッピングを行うには、両方
 
 {:start="4"}
 4\.Braze エンドポイントを選択します。
-5. イベントまたはイベント属性 フィルターを入力して、関連するデータのみがエンゲージメント マーケティングのためにBraze に送信されるようにします。Radar事象が発生するたびに、Radarはカスタムイベントsとユーザー 属性sをBrazeに送信する。iOS デバイスからのイベントはiOS API キー s を使用して送信され、Android デバイスからのイベントおよびユーザー 属性 s はAndroid API キー s を使用して送信されます。
+5. イベントまたはイベント属性フィルタリングを入力して、関連データのみがエンゲージメントマーケティングのために Braze に送信されるようにします。Radar イベントが生成されるたびに、Radar からカスタムイベントとユーザー属性が Braze に送信されます。iOS デバイスからのイベントは iOS API キーを使用して送信され、Android デバイスからのイベントおよびユーザー属性は Android API キーを使用して送信されます。
 
 {% alert note %}
-デフォルトでは、Radar`userId` は、ログインしているユーザーs のBraze`external_id` にマップされます。ただし、ログアウトしたユーザーs を追跡したり、設定 Radar`metadata.brazeAlias` または`metadata.brazeExternalId` でカスタムm アプリ ings を指定したりできます。`metadata.brazeAlias` を設定した場合は、ラベル`radarAlias` のBrazeにも一致する別名を追加する必要があります。
+デフォルトでは、ログインユーザーの Radar `userId` は Braze の `external_id` にマッピングされます。ただし、ログアウトしたユーザーを追跡すること、Radar の `metadata.brazeAlias` または `metadata.brazeExternalId` を設定してカスタムマッピングを指定することはできます。`metadata.brazeAlias` を設定した場合は、Braze でラベル `radarAlias` を使用して一致エイリアスを追加する必要もあります。
 {% endalert %}
 
 ## イベントベースおよび属性ベースのユースケース
 
-カスタムイベント s およびユーザー 属性 s を使用して、ロケーションベースのSegments またはトリガーのロケーションベースのキャンペーンs を構築できます。
+カスタムイベントとユーザー属性を使用して、ロケーションベースのセグメントを作成し、ロケーションベースのキャンペーンをトリガーすることができます。
 
 ### カーブサイドピックアップの店舗到着通知のトリガ 
 
-カーブサイドピックアップのためにあなたのお店に到着した時、到着指示のあるプッシュ通知をユーザーに送ってください。
+ユーザーがカーブサイドピックアップのために店舗に到着したときに、到着の手順を案内するプッシュ通知を送信します。
 
-!["arrived_at_trip_送信先"カスタムイベントが発生し、"trip_metadata"equals "curbside".]({% image_buster /assets/img_archive/radar-campaign.png %})が発生したときにキャンペーンが配信されることを示すアクションベースの配信キャンペーン
+![「arrived_at_trip_destination」カスタムイベントが発生し、「trip_metadata"equals "curbside」が「curbside」の場合にキャンペーンが配信されることを示すアクションベースの配信キャンペーン。]({% image_buster /assets/img_archive/radar-campaign.png %})
 
-### 最近の来店者オーディエンス Segmentの構築
+### 最近の来店者のオーディエンスセグメントを作成する
 
 たとえば、購買の有無にかかわらず、過去7日間にあなたの店舗を訪問したユーザーを対象にします。
 
-!["radar_ジオフェンス_タグ s" value my_store と"radar_更新 d_at" が7 日前より少ないSegment。]({% image_buster /assets/img_archive/radar-segment.png %})
+![「radar_geofence_tags」に値 my_store が含まれており、「radar_updated_at」が過去7日以内のセグメント。]({% image_buster /assets/img_archive/radar-segment.png %})
 
 ## コネクテッドコンテンツ
 
-次に、ディジタルオファーで近くのユーザー s 店内をドライブするプロモーションを実行する例を示します。 
+次の例は、デジタルオファーを使用して近くにいるユーザーを店舗に引き付けるプロモーションを実行する方法を示しています。 
 
-!["New In Store Deals, Walmart, target near you"を表示するConnected ContentプッシュメッセージのAndroid "画像。][1]{: style="float:right;max-width:30%;border:0;"}
+![Android に表示されている「New In Store Deals, Walmart and target near you」というコネクテッドコンテンツプッシュメッセージ。][1]{: style="float:right;max-width:30%;border:0;"}
 
-開始するには、リクエストURL 内で使用するために、Radarの公開可能なAPI キーを手元に用意する必要があります。
+開始するには、リクエスト URL 内で使用するために、Radar が公開可能な API キーを手元に用意しておく必要があります。
 
-次に、`connected_content` タグ内で、[ Search Places API](https://radar.io/documentation/api#search-places) へのGET リクエストを行います。検索では、[ Radar Places](https://radar.io/documentation/places): ワールドの包括的なビューを提供するプレイス、チェーン、およびカテゴリのロケーションのデータベースに基づいて、API が近くのロケーションを返します。
+次に、`connected_content` タグ内で、[ Search Places API](https://radar.io/documentation/api#search-places) へのGET リクエストを行います。Search Places API は、[Radar Places](https://radar.io/documentation/places) (場所の位置情報、チェーン、カテゴリを収録しており、全世界の包括的なビューを提供する:データベース) に基づいて付近の位置情報を返します。
 
 以下のコード スニペットは、API 呼び出しからJSON オブジェクトとしてRadarが返す例です。
 
@@ -125,7 +125,7 @@ Braze とRadar SDK s の間でデータマッピングを行うには、両方
 }
 ```
 
-Connected Content ターゲットおよびパーソナライズされた Braze メッセージを作成するには、Braze`most_recent_location` 属性をAPI リクエストのURL の`near` パラメータの入力として活用できます。`most_recent_location` 属性は、RadarイベントインテグレーションまたはBraze SDKを介して収集されます。
+コネクテッドコンテンツのターゲットを絞りパーソナライズされた Braze メッセージを作成するには、Braze の `most_recent_location` 属性を API リクエスト URL の`near` パラメーターの入力として使用できます。`most_recent_location` 属性は、Radar イベント統合から収集されるか、または Braze SDK を介して直接収集されます。
 
 次の例題では、Radarチェーンフィルターのing はTarget とWalmart のロケーションではアプリになり、近くのロケーションの検索範囲は2km に設定されています。
 
@@ -138,7 +138,7 @@ Connected Content ターゲットおよびパーソナライズされた Braze 
 `connect_content` タグからわかるように、JSON オブジェクトはURL の後に`:save nearbyplaces` を追加することで、ローカル変数`nearbyplaces` に保存されます。
 出力内容をテストするには、{% raw %}`{{nearbyplaces.places}}`{% endraw%} を参照します。
 
-ユースケースをまとめると、キャンペーンのシンタックスがどのように見えるかがわかります。以下のコードは、`nearbyplaces.places` オブジェクトを反復処理し、一意の値を抽出し、メッセージの適切な人間が読める区切り文字で連結します。
+ユースケースをまとめると、キャンペーンのシンタックスがどのように見えるかがわかります。以下のコードは、`nearbyplaces.places` オブジェクトを反復処理し、一意の値を抽出し、それらの値を可読可能な区切り文字で連結してメッセージにします。
 
 {% raw %}
 ```
diff --git a/_lang/ja/_partners/message_personalization/location/tangerine.md b/_lang/ja/_partners/message_personalization/location/tangerine.md
index a03e7b13d2f..a6a823436ed 100644
--- a/_lang/ja/_partners/message_personalization/location/tangerine.md
+++ b/_lang/ja/_partners/message_personalization/location/tangerine.md
@@ -1,7 +1,7 @@
 ---
 nav_title: Tangerine
 article_title: Tangerine
-description: "この記事では、Braze と Tangerine Store360 の提携について説明します。Tangerine Store360 は、物理店舗とオンライン店舗を接続し、消費者と店舗従業員に優れた店内体験を提供するオムニチャネルプラットフォームです。この統合により、Brazeの生のキャンペーンおよびインプレッションデータがSnowflake Secure Data Sharingを介してStore360で利用可能になり、ブランドはキャンペーンが店内のエンゲージメントや店舗のトラフィックにどのように影響するかを測定できます。"
+description: "この記事では、Braze と Tangerine Store360 の提携について説明します。Tangerine Store360 は、物理店舗とオンライン店舗を接続し、消費者と店舗従業員に優れた店内体験を提供するオムニチャネルプラットフォームです。この統合により、Snowflake セキュアデータシェアリングを介して Store360 で Braze で生のキャンペーンデータとインプレッションデータが利用可能になります。ブランドは、ストアエンゲージメントとストアトラフィックにおける各自のキャンペーンの影響を測定できます。"
 alias: /partners/tangerine/
 page_type: partner
 search_tag: Partner
@@ -10,9 +10,9 @@ search_tag: Partner
 
 # Tangerine Store360
 
-> Tangerineは、Store360というオムニチャネルプラットフォームを設計、構築、運営しています。Store360は、消費者と店舗従業員の店内体験を向上させるために、実店舗とオンラインストアを接続するオムニチャネル対応のプラットフォームです。Store360は、小売業者のモバイルアプリユーザーと店内エンゲージメントを含む、物理店舗の訪問トラフィックを追跡および分析します。
+> Tangerineは、Store360というオムニチャネルプラットフォームを設計、構築、運営しています。Store360は、消費者と店舗従業員の店内体験を向上させるために、実店舗とオンラインストアを接続するオムニチャネル対応のプラットフォームです。Store360 は、小売業者のモバイルアプリのユーザーとユーザーの店舗内エンゲージメントを含む、実店舗訪問トラフィックを追跡および分析します。
 
-BrazeとTangerineの統合により、Brazeの生のキャンペーンおよびインプレッションデータをSnowflake Secure Data Sharingを通じてStore360に統合することができます。ブランドは、これらのキャンペーンが実店舗への訪問や店内エンゲージメントに与える影響を測定できるようになりました。
+Braze と Tangerine の統合により、Braze から Snowflake セキュアデータシェアリングを介して Store360 に生のキャンペーンデータとインプレッションデータを統合できます。ブランドは、これらのキャンペーンが実店舗への訪問や店内エンゲージメントに与える影響を測定できるようになりました。
 
 ## 前提条件
 
@@ -25,31 +25,31 @@ BrazeとTangerineの統合により、Brazeの生のキャンペーンおよび
 
 ## ユースケース
 
-### 物理店舗訪問へのキャンペーンの影響を分析する
+### 実店舗への訪問に対するへのキャンペーンの影響を分析する
 
 ブランドはBrazeを使用して、キャンペーンメッセージを消費者に送信し、店舗訪問を増やします。キャンペーン中、Store360はユーザーIDで識別されたモバイルアプリユーザーの訪問を記録します。
 
-Store360インサイト分析機能を使用すると、ブランドは送信および読み取られたメッセージ（Brazeのデータ）から物理店舗を訪れた受信者の数と方法（Store360のデータ）まで、キャンペーンの影響の詳細を視覚化できます。
+ブランドは Store360 インサイト分析機能を使用して、送信され閲覧されたメッセージ (Braze のデータ) から、実店舗を訪問した受信者の情報と訪問受信者数 (Store360 のデータ) まで、キャンペーンの影響の詳細を視覚化できます。
 
 ## 統合
 
 ### ステップ1:Snowflakeセキュアデータ共有を有効にする
 
-Brazeチームと協力して、Snowflake Secure Data Shareを有効化および構成します。
+Braze チームと協力して、Snowflake セキュアデータシェアリングを有効にして設定します。
 
 ### ステップ2:Store360を構成してBrazeデータを取得する
 
-Store360管理者マネージャーWebコンソールを使用して、BrazeアプリグループIDをStore360サービスアカウントに設定します。これは、Tangerine管理チームにBrazeデータをSnowflake Data Sharingを使用してStore360に同期するよう依頼します。
+Store360管理者マネージャーWebコンソールを使用して、BrazeアプリグループIDをStore360サービスアカウントに設定します。これにより、Tangerine 管理者チームに対し、Snowflake データシェアリングを使用して Braze データを Store360 に同期することが求められます。
 
 ### ステップ3:モバイルアプリにStore360 SDKを統合する
 
-モバイルアプリユーザーの店舗訪問と店内活動をBrazeキャンペーンおよびインプレッションデータと共に追跡および分析するには、Store360 SDKインストールドキュメントに記載されている手順を使用して、Store360 SDKをモバイルアプリに統合する必要があります。このドキュメントは、Tangerine Store 360とのクライアント契約に署名した後に提供されます。
+モバイルアプリユーザーのストア訪問とストア内アクティビティを、Braze キャンペーンデータおよびインプレッションデータとともに追跡、分析するには、Store360 SDK インストールドキュメントに記載されている手順に従って、Store360 SDK をモバイルアプリに統合する必要があります。このドキュメントは、Tangerine Store 360 とのクライアント契約を締結した後でお客様に提供されます。
 
 ## Store360でBrazeデータを分析する
 
 Snowflakeの安全なデータ共有を利用して、Brazeの生のキャンペーンおよびインプレッションデータをStore360のインサイト分析と共有し、オンラインからオフラインまでのユーザーのライフサイクルと活動の全体像を提供します。
 
-参考までに、Store360分析に組み込むことができるすべての[Brazeフィールド](https://www.braze.com/docs/assets/download_file/data-sharing-raw-table-schemas.txt?ffbc5f5ca7092bc9ae26268aa0e711df)を以下に示します。このステップの詳細は非常に顧客固有であり、特別な構成が必要です。ストア360のアカウントマネージャーまたはsupport@tangerine.ioにお問い合わせください。
+参考までに、Store360分析に組み込むことができるすべての[Brazeフィールド](https://www.braze.com/docs/assets/download_file/data-sharing-raw-table-schemas.txt?ffbc5f5ca7092bc9ae26268aa0e711df)を以下に示します。このステップの詳細は顧客によって大きく異なり、特別な設定を必要とします。詳細については、Store360 のアカウントマネージャーまたは support@tangerine.io までお問い合わせください。
 
 ## 重要な情報と制限
 
@@ -66,7 +66,7 @@ Tangerineは2023年に以下の国々でStore360製品の発売を計画して
 
 ### データリテンション
 
-Snowflakeデータ共有のためのBrazeデータには2年間のリテンションポリシーがあります。
+Snowflake データシェアリングに関して、2年間の Braze データのリテンションポリシーがあります。
 
 ### Brazeイベントデータの反映に時間差がある
 
diff --git a/_lang/ja/_partners/third_party_liability.md b/_lang/ja/_partners/third_party_liability.md
index a570bd66552..daf54858575 100644
--- a/_lang/ja/_partners/third_party_liability.md
+++ b/_lang/ja/_partners/third_party_liability.md
@@ -3,7 +3,7 @@ nav_title: 第三者責任
 article_title: 第三者責任
 page_order: 8
 page_type: reference
-description: "この参考文献は、負債Brazeに関する方針を、関連する第三者に照らして詳述している。"
+description: "このリファレンス記事では、関連する第三者に関して Braze が有する賠償責任に関するポリシーを詳しく説明します。"
 
 ---
 
@@ -13,4 +13,4 @@ Warning! Don't make any changes to this document without approval from the legal
 
 # 第三者の責任
 
-Brazeまたはサードパーティは、Brazeのオンラインドキュメント内のサードパーティ製品または機能を参照する場合があります。 このようなサードパーティのサービスまたは機能の顧客による使用、および顧客とそのようなサードパーティとの間のデータ交換は、その顧客とそのサードパーティとの間でのみ行われます。 Braze は、サードパーティのサービスや機能を保証するものではなく、顧客 の使用に関連していかなる責任も負いません。
+Braze または第三者は、Braze オンラインドキュメントで第三者の製品または機能に言及することがあります。 お客様によるこのような第三者のサービスまたは機能の使用、およびお客様と第三者の間でのデータ交換は、お客様と当該の第三者間においてのみ行うものとします。 Braze は、第三者のいかなるサービスまたは機能を保証するものではなく、またお客様の使用に関連していかなる責任も負わないものとします。
diff --git a/_lang/ja/_user_guide/administrative/access_braze/single_sign_on/okta.md b/_lang/ja/_user_guide/administrative/access_braze/single_sign_on/okta.md
index 477e5e8281a..fc53cf0b669 100644
--- a/_lang/ja/_user_guide/administrative/access_braze/single_sign_on/okta.md
+++ b/_lang/ja/_user_guide/administrative/access_braze/single_sign_on/okta.md
@@ -9,7 +9,7 @@ description: "この記事では、シングルサインオンに Okta を使用
 
 # Okta 
 
-![オークタSSO を有効にした状態でのBraze ダッシュボードログイン。][4]{: style="float:right;max-width:30%;margin-left:15px;margin-bottom:15px;"}
+![Okta SSO を有効にした Braze ダッシュボードログイン。][4]{: style="float:right;max-width:30%;margin-left:15px;margin-bottom:15px;"}
 
 > Okta は、あらゆるデバイス上のあらゆるアプリケーションとあらゆるユーザーを接続します。Okta はクラウド向けに構築されたエンタープライズクラスの ID 管理サービスですが、多くのオンプレミスアプリケーションと互換性があります。Okta を使用すると、IT チームはあらゆる従業員によるあらゆるアプリケーションやデバイスへのアクセスを管理できます。
 <br>
@@ -18,10 +18,10 @@ description: "この記事では、シングルサインオンに Okta を使用
 
 | 要件 | 詳細 |
 | ----------- | ------- |
-| アカウントでOktaがオンになっている | Braze アカウントマネージャーに連絡して、アカウントでこれを有効にしましょう。 |
-| Okta 管理者権限 | オークタを設定するときは、事前に管理者権限を持っていることを確認してください。 |
-| Braze管理者権限 | オークタを設定するときは、事前に管理者権限を持っていることを確認してください。 |
-| リレーステートAPI キー | IdP ログインを有効にするには、**Settings** > **API キー s** に移動し、`sso.saml.login` 権限を持つAPI キーを作成します。 |
+| アカウントで Okta がオンになっている | Braze アカウントマネージャーに連絡して、アカウントでこれを有効にしましょう。 |
+| Okta 管理者権限 | Okta を設定する前に、管理者権限があることを確認してください。 |
+| Braze管理者権限 | Okta を設定する前に、管理者権限があることを確認してください。 |
+| RelayState API キー | IdP ログインを有効にするには、\[**設定**] > \[**API キー**] に移動し、`sso.saml.login` 権限を持つ API キーを作成します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
@@ -32,13 +32,13 @@ description: "この記事では、シングルサインオンに Okta を使用
 
 ### ステップ 1a: Braze の \[セキュリティ設定] に移動
 
-アカウントマネージャーがアカウントのSAML SSO を有効にした後、**Settings**> **Admin Settings**> **Security Settings**に移動し、SAML SSO セクションを**ON**に切り替えます。
+アカウントマネージャーがアカウントの SAML SSO を有効にした後、\[**設定**] > \[**管理者設定**] > \[**セキュリティ設定**] に移動し、SAML SSO セクションを \[**オン**] に切り替えます。
 
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、アカウントアイコンを選択し、\[**会社の設定**] > \[**セキュリティ設定**] に移動して、\[SAML SSO] セクションを見つけます。
 {% endalert %}
 
-![セキュリティー設定ページで、OKTA SAML SSO が有効になっています。][1]
+![\[セキュリティ設定] ページで、Okta SAML SSO が有効になっています。][1]
 
 ### ステップ 1b: SAML SSO 設定の編集
 
@@ -48,9 +48,9 @@ Okta Admin ダッシュボードから、ターゲットURL (ログインURL) 
 
 | 要件 | 詳細 |
 |---|---|
-| `SAML Name` | これにより、ログイン画面のボタンテキストとして耳がアプリされます。これは通常、ID プロバイダーの名前です(例: "Okta")。 |
-| `Target URL` | これは、オークタ管理者ダッシュボードが提供するログインURL です。** アプリ lications** > あなたのアプリ lication > ** General** tab > ** アプリ 埋め込みリンク** > ** 埋め込みリンク</スパン> を検索します。 |
-| `Certificate` | `x.509` PEM en コード d 証明書は、ID プロバイダーによって提供されます。このフィールドにコピーアンドペーストする必要があります。** SAML Signing 証明書 s** に進み、**Actions** > **Down 読み込む 証明書** を選択して、Okta で取得します。 |
+| `SAML Name` | これはログイン画面のボタンテキストとして表示されます。これは通常、ID プロバイダーの名前です(例: "Okta")。 |
+| `Target URL` | これは、Okta 管理者ダッシュボードで提供されるログイン URL です。これを確認するには、\[**アプリケーション**] > 自分のアプリケーション > \[**一般**] タブ > \[**アプリ埋め込みリンク**] > \[**埋め込みリンク**] に移動します。 |
+| `Certificate` | PEM エンコードされた `x.509` 証明書は、ID プロバイダーから提供されます。このフィールドにコピーアンドペーストする必要があります。これを Okta で取得するには、\[**SAML 署名証明書**] に移動し、> \[**アクション**] > \[**証明書をダウンロード**] を選択します。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 完了したら、ページ下部の \[**変更内容を保存**] を選択します。
@@ -61,7 +61,7 @@ Okta で、Braze SAML アプリの \[**サインオン**] タブを選択し、\
 
 次に、\[**デフォルトのリレーステート**] フィールドに、`sso.saml.login` 権限を持つ RelayState API キーを入力します。 
 
-![サインオンタブのOkta Default RelayState。][2]{: style="max-width:75%"}
+![\[サインオン] タブの Okta のデフォルト RelayState。][2]{: style="max-width:75%"}
 
 これらの新しい設定を必ず保存してください。
 
diff --git a/_lang/ja/_user_guide/administrative/app_settings/email_settings.md b/_lang/ja/_user_guide/administrative/app_settings/email_settings.md
index a8b935b1e76..2df757b0cee 100644
--- a/_lang/ja/_user_guide/administrative/app_settings/email_settings.md
+++ b/_lang/ja/_user_guide/administrative/app_settings/email_settings.md
@@ -28,7 +28,7 @@ channel: email
 メール設定を行うときに、送信メール設定は、Braze がユーザーにメールを送信するときに使用する名前とメールアドレスを特定します。
 
 {% tabs local %}
-{% tab 表示名 住所 %}
+{% tab 表示名とアドレス %}
 
 このセクションでは、Braze からユーザーにメールを送信するときに使用できる名前とメールアドレスを追加できます。表示名とメールアドレスは、メールキャンペーンを作成するときに \[**送信情報を編集**] オプションで使用できます。送信メール設定を更新しても、過去にさかのぼって既存の送信には影響しないことに注意してください。 
 
@@ -93,7 +93,7 @@ Braze は現在、メールサービスプロバイダー (ESP) のデフォル
 SSL を有効にすると、トラッキングピクセルの URL が HTTP ではなく HTTPS でラップされます。SSL が正しく設定されていない場合、トラッキングピクセルの効果に影響する可能性があります。
 {% endalert %}
 
-## リスト配信停止ヘッダー {#list-unsubscribe}
+## list-unsubscribe ヘッダー {#list-unsubscribe}
 
 {% alert note %}
 2024 年 2 月 15 日以降、新規の会社では list-unsubscribe ヘッダー (ワンクリックで配信停止) がデフォルトで有効になります。
@@ -111,13 +111,13 @@ list-unsubscribe を有効にすることは、配信到達性のベストプラ
 
 次の表に、「mailto:」ヘッダー、list-unsubscribe URL、およびワンクリック配信停止 ([RFC 8058](https://datatracker.ietf.org/doc/html/rfc8058)) に対するメールボックスプロバイダーのサポートをまとめています。
 
-| list-unsubscribe ヘッダー | Mailto: ヘッダー | 配信停止URL | ワンクリックで配信停止（RFC 8058） | 
+| list-unsubscribe ヘッダー | Mailto: ヘッダー | list-unsubscribe URL | ワンクリック配信停止 （RFC 8058） | 
 | ----- | --- | --- | --- |
-| Gmail | 対応\*。 | サポート | サポート |
+| Gmail | 対応* | 対応 | 対応 |
 | Gmailモバイル | サポートされていない | サポートされていない | サポートされていない |
-| アップル・メール | サポート | サポートされていない | サポートされていない |
-| Outlook.com | サポート | サポートされていない | サポートされていない |
-| ヤフーだ！メール | 対応\*。 | サポートされていない | サポート |
+| Apple メール | 対応 | サポートされていない | サポートされていない |
+| Outlook.com | 対応 | サポートされていない | サポートされていない |
+| Yahoo!メール | 対応* | サポートされていない | 対応 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
 
 _\*Yahoo と Gmail は最終的に「mailto:」ヘッダーを廃止し、ワンクリックのみをサポートする予定です。_
@@ -133,7 +133,7 @@ _\*Yahoo と Gmail は最終的に「mailto:」ヘッダーを廃止し、ワン
 
 ![]({% image_buster /assets/img/email_settings/email_unsub_header_workspaces.png %}){: style="float:right;max-width:60%;margin-left:15px;"}
 
-メール配信停止ヘッダー機能がオンになっている場合、この設定は会社レベルではなく、ワークスペース全体に適用される。キャンペーンやキャンバスビルダーの**ターゲットオーディエンスの**ステップで、購読またはオプトインしたユーザー、またはオプトインしたユーザーに送信するように設定されているキャンペーンやキャンバスに追加される。
+メール配信停止ヘッダー機能がオンになっている場合、この設定は会社レベルではなく、ワークスペース全体に適用される。これは、サブスクリプション登録やオプトインしているユーザー、あるいはキャンペーンとキャンバスビルダーの \[**ターゲットオーディエンス**] ステップでオプトインしているユーザーに送信するように設定されているキャンペーンとキャンバスに追加されます。
 
 Brazeは、トランザクションとみなされるものにはヘッダーを追加しないので、配信停止ユーザーを含むすべてのユーザーにメッセージを送信するように設定されている場合、メッセージレベルのワンクリックリスト配信停止設定で特に指定しない限り、list-unsubscribeヘッダーはメッセージに添付されない。さらに、list-unsubscribe ヘッダーは Braze 内の対象ユーザープロファイルについてのみ生成と追加が行われるため、テスト送信によって配信されるメッセージにヘッダーは追加されません。
 
@@ -145,15 +145,15 @@ Gmail は、2024 年 6 月 1 日以降、送信するすべての商用および
 
 Braze の配信停止機能を使用して配信停止を直接処理するには、 \[**配信登録済みまたはオプトイン済みのユーザーに送信されるメールに One-Click List-Unsubscribe (mailto および HTTP) ヘッダーを含める**] を選択し、標準の Braze URl および mail-to として \[**Braze のデフォルト**] を選択します。 
 
-![]({% image_buster /assets/img/email_settings/email_unsubscribe_header.png %}) 購読済みユーザーまたはオプトインユーザーに送信される電子メールに、リスト購読解除ヘッダーを自動的に含めるオプション。{: style="max-width:80%;"}
+![配信登録またはオプトインしているユーザーに送信されるメールに、list-unsubscribe ヘッダーを自動的に含めるオプション。]({% image_buster /assets/img/email_settings/email_unsubscribe_header.png %}){: style="max-width:80%;"}
 
 Braze は、次のバージョンの list-unsubscribe ヘッダーをサポートしています。
 
 | リスト配信停止バージョン | 説明 | 
 | ----- | --- |
-| ワンクリック（RFC 8058） | 受信者がワンクリックでメールからオプトアウトできる簡単な方法を提供する。これはヤフーとGmailが大量送信者に要求しているものだ。 |
+| ワンクリック（RFC 8058） | 受信者がワンクリックでメールからオプトアウトできる簡単な方法を提供します。これは、Yahoo と Gmail から一括送信者に課される要件です。 |
 | リスト配信停止URLまたはHTTPS | 受信者に、購読を解除できるウェブページに誘導するリンクを提供する。 |
-| メール | 受信者からブランドへの配信停止リクエストメッセージの送信先としてメールアドレスを指定する。<br><br> _mailto list-unsubscribe リクエストを処理するには、そのような配信停止リクエストに、配信を停止するエンドユーザーについて Braze に保存されているメールアドレスが含まれている必要があります。これは、エンドユーザーが配信を停止するメールの「差出人アドレス」、配信を停止するエンドユーザーが受信したメールのエンコードされた件名またはエンコードされた本文で提供される場合があります。非常に限られたケースですが、一部の受信トレイプロバイダーが [RFC 2368](https://datatracker.ietf.org/doc/html/rfc2368) プロトコルに準拠していないため、メールアドレスが適切に渡されません。このため、配信停止リクエストがBrazeで処理できないことがある。_ |
+| mailto | 受信者からブランドへの配信停止リクエストメッセージの送信先としてメールアドレスを指定する。<br><br> _mailto list-unsubscribe リクエストを処理するには、そのような配信停止リクエストに、配信を停止するエンドユーザーについて Braze に保存されているメールアドレスが含まれている必要があります。これは、エンドユーザーが配信を停止するメールの「差出人アドレス」、配信を停止するエンドユーザーが受信したメールのエンコードされた件名またはエンコードされた本文で提供される場合があります。非常に限られたケースですが、一部の受信トレイプロバイダーが [RFC 2368](https://datatracker.ietf.org/doc/html/rfc2368) プロトコルに準拠していないため、メールアドレスが適切に渡されません。このため、配信停止リクエストが Braze で処理できないことがあります。_ |
 {: .reset-td-br-1 .reset-td-br-2}
 
 Braze が上記の方法のいずれかでユーザーから list-unsubscribe リクエストを受信すると、このユーザーのグローバルサブスクリプション状態が配信停止に設定されます。一致しない場合、Braze はこのリクエストを処理しません。
@@ -164,9 +164,9 @@ list-unsubscribe ヘッダーにワンクリック配信停止を使用するこ
 
 ### メッセージレベルのワンクリック・リスト配信停止
 
-メッセージレベルのワンクリックリスト購読解除設定は、ワークスペースの電子メール購読解除ヘッダー機能を上書きする。キャンペーンまたはキャンバスのステップごとに、以下の用途でワンクリック配信停止動作を適用する：
+メッセージレベルのワンクリックリスト購読解除設定は、ワークスペースの電子メール購読解除ヘッダー機能を上書きする。次の用途では、キャンペーンまたはキャンバスステップごとにワンクリック配信停止動作を適用します。
 
-- 1つのワークスペース内で複数のブランド/リストをサポートするために、特定の購読グループに対してBrazeのワンクリック購読停止機能を追加する。
+- 1 つのワークスペース内で複数のブランド/リストをサポートするために、特定のサブスクリプショングループに対して Braze のワンクリック配信停止機能を追加する
 - デフォルトのBraze配信停止URLかカスタムURLかを切り替える
 - カスタム・ワンクリック配信停止URLを追加する
 - このメッセージのワンクリック配信停止を省略する
@@ -177,15 +177,15 @@ list-unsubscribe ヘッダーにワンクリック配信停止を使用するこ
 
 メールエディターで、「**送信設定」**＞「**送信情報**」と進む。以下のオプションから選択する：
 
-- **ワークスペースのデフォルトを使用する**：**メール**設定で設定された**メール配信停止ヘッダー**設定を使用する。この設定を変更すると、すべてのメッセージに適用される。
-- **すべてのメールをグローバルに配信停止する**：Brazeデフォルトのワンクリック配信停止ヘッダを使用する。配信停止ボタンをクリックしたユーザーは、グローバルメール購読状態が「配信停止」に設定される。
-- **特定の購読グループから購読を解除する**：指定されたサブスクリプショングループを使用する。購読解除ボタンをクリックしたユーザーは、選択した購読グループから購読解除される。
-    - サブスクリプショングループを選択する際、**ターゲットオーディエンスに** **サブスクリプショングループフィルタを**追加し、この特定のグループにサブスクライブしているユーザーのみをターゲットにする。ワンクリックで購読解除するために選択した購読グループは、あなたがターゲットにしている購読グループと一致していなければならない。購読グループに不一致がある場合、すでに購読を解除している購読グループから購読を解除しようとしているユーザーに送信する危険性がある。
-- **カスタムだ：**ワンクリックで配信停止できるURLを追加し、配信停止を直接処理できるようにする。
-- **配信停止を除く**
+- **ワークスペースのデフォルトを使用**: **メール**設定で設定された**メール配信停止ヘッダー**設定を使用する。この設定を変更すると、すべてのメッセージに適用される。
+- **すべてのメールからの配信をすべて停止**: Braze デフォルトのワンクリック配信停止ヘッダーを使用します。配信停止ボタンをクリックしたユーザーは、グローバルメール配信登録状態が「配信停止済み」に設定されます。
+- **特定のサブスクリプショングループから配信停止**: 指定されたサブスクリプショングループを使用する。配信停止ボタンをクリックしたユーザーは、選択したサブスクリプショングループからの配信が停止されます。
+    - サブスクリプショングループを選択する際、この特定グループを購読しているユーザーのみをターゲットにするには、\[**ターゲットオーディエンス**] で \[**サブスクリプショングループフィルター**] を追加します。ワンクリック配信停止用に選択したサブスクリプショングループは、ターゲットにしているサブスクリプショングループと一致していなければなりません。サブスクリプショングループが一致しない場合、すでに配信停止済みのグループからの配信を停止しようとしているユーザーに送信してしまう危険性があります。
+- **カスタム:** 配信停止を直接処理するためのカスタムのワンクリック配信停止 URL を追加します。
+- **配信停止を除外**
 
 {% alert important %}
-ワンクリック・アンサブスクライブや、いかなるアンサブスクライブ・メカニズムも、パスワード・リセット、領収書、確認メールなどのトランザクション・メッセージングにのみ適用されるべきである。
+ワンクリック配信停止や任意の配信停止メカニズムを除外するのは、パスワードのリセット、領収書、確認メールなど、トランザクションメッセージングに対してのみ行ってください。
 {% endalert %}
 
 この設定を調整すると、このメールでのワンクリックによるリスト購読解除のデフォルトの動作が上書きされる。
@@ -199,7 +199,7 @@ list-unsubscribe ヘッダーにワンクリック配信停止を使用するこ
 * URL は配信停止 POST リクエストを処理できる必要があります。
 * URL は `https://` で始まる必要があります。
 * URLはHTTPSリダイレクトやボディを返してはならない。ランディングページや他のタイプのウェブページに移動するワンクリック退会リンクは、RFC 8058に準拠していない。
-* POSTリクエストはクッキーを設定してはならない。
+* POST リクエストがクッキーを設定してはなりません。
 
 \[**カスタムの list-unsubscribe ヘッダー**] を選択して、独自に構成したワンクリック配信停止エンドポイントと、オプションの \[mailto:] を追加します。ワンクリック配信停止 HTTP が Yahoo および Gmail の一括送信者に対する要件であるため、Braze では、カスタムの list-unsubscribe ヘッダーをサポートするために URL を入力する必要があります。
 
@@ -231,8 +231,8 @@ CSS インライン化は、メールと新規メールの CSS スタイルを
 商用メールの場合、[CAN-SPAM 法](https://en.wikipedia.org/wiki/CAN-SPAM_Act_of_2003)では、すべての商用メールに配信停止オプションを含めることを義務付けています。\[カスタムフッター] 設定を使用すると、CAN-SPAM を遵守したうえで、メールのオプトアウトフッターをカスタマイズできます。遵守状態を維持するために、このワークスペースのキャンペーンの一部として送信されるすべてのメールにカスタムフッターを追加する必要があります。
 
 メールメッセージングのカスタムフッターを作成するときには、次の要件に注意してください。
-- 配信停止URLと物理的な郵送先住所を記載すること。
-- 100KB以下でなければならない。
+- 配信停止 URL と物理的な郵送先住所を含める必要があります。
+- 100 KB 未満でなければなりません。
 
 ![]({% image_buster /assets/img/email_settings/custom_footer.png %})
 
@@ -248,7 +248,7 @@ Braze を使用すると、独自の HTML を使用して**カスタム配信停
 メールリスト管理のベストプラクティスの詳細については、「[メールサブスクリプションの管理]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/managing_email_subscriptions/#unsubscribed-email-addresses)」を参照してください。
 
 {% endtab %}
-{% tab カスタム・オプトイン・ページ %}
+{% tab カスタムオプトインページ %}
 
 独自の HTML を使用してカスタムのオプトインページを作成できます。これをメールに含めると、特にユーザーのライフサイクル全体を通じてブランディングとメッセージの一貫性を維持する場合にメリットがあります。このページは 750 KB 未満でなければならないことに注意してください。 
 
@@ -268,12 +268,12 @@ Braze を使用すると、独自の HTML を使用して**カスタム配信停
 {% enddetails %}
 
 {% details プリファレンスセンターを作成する際、「本文に配信停止リンクが含まれていません」というエラーメッセージが表示されるのはなぜか？ %}
-プリファレンスセンターは、配信停止リンクとはみなされない。CAN-SPAMに準拠するためには、メール受信者が商業メールの配信を停止できるようにしなければならない。
+ユーザー設定センターは、配信停止リンクとはみなされません。CAN-SPAMに準拠するためには、メール受信者が商業メールの配信を停止できるようにしなければならない。
 {% enddetails %}
 
 
 {% details ワンクリック配信停止設定を有効にした後、過去のメールキャンペーンやキャンバスを編集して適用する必要があるか？ %}
-メッセージレベルのワンクリックリスト配信停止設定のユースケースに該当しない場合は、「**メール設定**」でこの設定がオンになっている限り、必要なアクションはない。Brazeは、すべての送信マーケティングおよびプロモーションメッセージにワンクリック配信停止ヘッダーを自動的に追加する。ただし、ワンクリック配信停止をメッセージ単位で設定する必要がある場合は、それに合わせて以前のキャンペーンとキャンバスのステップメールを更新する必要がある。
+メッセージレベルのワンクリックリスト配信停止設定のユースケースに該当しない場合は、「**メール設定**」でこの設定がオンになっている限り、必要なアクションはない。Brazeは、すべての送信マーケティングおよびプロモーションメッセージにワンクリック配信停止ヘッダーを自動的に追加する。ただし、ワンクリック配信停止の動作をメッセージごとに設定する必要がある場合は、それに応じてメールで以前のキャンペーンとキャンバスステップを更新する必要があります。
 {% enddetails %}
 
 {% details 元のメッセージや生データでは、リスト配信停止やワンクリック配信停止のヘッダーが見えるのに、なぜGmailやYahooでは配信停止ボタンが見えないのか？ %}
@@ -294,12 +294,12 @@ Braze を使用すると、独自の HTML を使用して**カスタム配信停
 ワンクリックリスト配信停止のために追加されたメールヘッダは、このキャンペーンの今後のすべての送信に適用される。
 {% enddetails %}
 
-{% details なぜサブスクリプション・グループは、ローンチするためにメッセージ・バリアント間で一致しなければならないのか？ %}
+{% details サブスクリプショングループを起動するには、メッセージのバリアント間でグループが一致しなければならないのはなぜか? %}
 A/Bテストのキャンペーンでは、Brazeはユーザーにランダムにバリアントの1つを送信する。同じキャンペーンに2つの異なる購読グループが設定されている場合（バリアントAが購読グループAに設定され、バリアントBが購読グループBに設定されている）、購読グループBにのみ購読しているユーザーがバリアントBを取得することを保証することはできません。
 {% enddetails %}
 
-{% details メール設定」の「メール配信停止ヘッダー」の設定はオフになっているが、私のキャンペーンの送信情報では、ワンクリックリストの配信停止設定が「ワークスペースのデフォルトを使用」に設定されている。これはバグなのだろうか？ %}
-ワークスペースの設定がオフで、メッセージの設定が**Use workspace defaultに**設定されている場合、Brazeは**Email Preferencesで**設定された内容に従う。これは、キャンペーンにワンクリック配信停止ヘッダーを追加しないことを意味する。
+{% details 「メール環境設定」ではメールの配信停止ヘッダー設定が無効になっていますが、キャンペーンの送信情報では、ワンクリックリスト配信停止設定が「ワークスペースのデフォルトを使用」するように設定されています。これはバグですか? %}
+いいえ。ワークスペースの設定が無効になっていて、メッセージの設定が「**ワークスペースデフォルトを使用**」に設定されている場合、Braze は**メール環境設定**で指定されている設定に従います。したがって、キャンペーンのワンクリック配信停止ヘッダーは追加されません。
 {% enddetails %}
 
 {% details 購読グループがアーカイブされるとどうなるか？この場合、送信されたメールのワンクリック配信停止は解除されるのか？ %}
@@ -311,7 +311,7 @@ Eメールテンプレートは送信ドメインに割り当てられていな
 {% enddetails %}
 
 {% details この機能は、カスタムオプションに追加されたワンクリック配信停止URLが有効かどうかをチェックするのか？ %}
-Brazeのダッシュボードでは、リンクのチェックや検証は行っていない。ローンチする前に、URLをきちんとテストすること。
+Braze ダッシュボードでは、リンクのチェックや検証は行っていません。ローンチする前に、URLをきちんとテストすること。
 {% enddetails %}
 
 
diff --git a/_lang/ja/_user_guide/administrative/app_settings/push_ttl_settings.md b/_lang/ja/_user_guide/administrative/app_settings/push_ttl_settings.md
index 3b0c29a0c4e..c0432e4be93 100644
--- a/_lang/ja/_user_guide/administrative/app_settings/push_ttl_settings.md
+++ b/_lang/ja/_user_guide/administrative/app_settings/push_ttl_settings.md
@@ -20,7 +20,7 @@ channel: push
 
 この機能は、ユーザーのデバイスがすでに受信している通知を削除しません。プッシュプロバイダーが通知の配信を試行する期間のみを制御します。
 
-![プッシュTTL Settings tab under Manage Settings][1]
+![「設定の管理」の「プッシュ TTL の設定」タブ][1]
 
 {% alert tip %}
 ページを離れる前に、必ず \[**保存**] をクリックしてください。
diff --git a/_lang/ja/_user_guide/administrative/app_settings/subscription_and_usage.md b/_lang/ja/_user_guide/administrative/app_settings/subscription_and_usage.md
index 55c0dc1d07d..c4394015937 100644
--- a/_lang/ja/_user_guide/administrative/app_settings/subscription_and_usage.md
+++ b/_lang/ja/_user_guide/administrative/app_settings/subscription_and_usage.md
@@ -19,7 +19,7 @@ search_rank: 5
 [古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、アカウントアイコンを選択し、\[**サブスクリプションと使用法**] をクリックすると、このページが表示されます。
 {% endalert %}
 
-**Billing** ページには、次のタブが含まれています。
+\[**請求**] ページには次のタブが含まれています。
 
 - [サブスクリプションと使用法](#subscriptions-and-usage)
 - [アプリ別の最も使用されたイベントと属性](#most-used-events-and-attributes-by-app)
@@ -33,9 +33,9 @@ search_rank: 5
 
 ここには、ワークスペースに適用される使用量のグラフがあります。購入した製品によって、ダッシュボードに表示される使用量の指標がこの画像とは異なる場合があります。
 
-![月間ユニークビジター数の使用量グラフ][3]{: style="max-width:90%;"}
+![1 か月あたりのユニーク訪問者数を示す使用量グラフ][3]{: style="max-width:90%;"}
 
-これらのグラフには、月次のアクティブユーザー、月次の一意のビジター、およびメール送信が表示されます。このような使用量のグラフは、使用量の予算を立てたり、全体の使用量のうち多くを占めているワークスペースをより詳しく理解しようとしたりするときに、特に役立ちます。
+これらのグラフには、1 か月あたりのアクティブユーザー数、1 か月あたりのユニーク訪問者数、およびメール送信数が表示されます。このような使用量のグラフは、使用量の予算を立てたり、全体の使用量のうち多くを占めているワークスペースをより詳しく理解しようとしたりするときに、特に役立ちます。
 
 ### 契約の詳細
 
@@ -66,7 +66,7 @@ search_rank: 5
 - **割り当てられたデータポイント:**請求期間ごとに契約で割り当てられるデータポイントの量。
 - **契約のデータポイント使用量:**契約期間中に消費された全データポイントの累積合計であり、次の請求期間ではリセットされません。
 
-![Total Data Point UsageタブのContract Detailsセクション][5]
+![「データポイント使用量の合計」タブの「契約の詳細」セクション][5]
 
 ### 現在の請求サイクル
 
@@ -77,7 +77,7 @@ search_rank: 5
 - 割り当てられたデータポイント数 
 - データポイント使用量の合計 
 
-![Total Data Points UsageタブのCurrent Billing Cycleセクション][6]{: style="max-width:90%;"}
+![「データポイント使用量の合計」タブの「現在の請求サイクル」セクション][6]{: style="max-width:90%;"}
 
 ### 会社の請求データ
 
@@ -103,25 +103,25 @@ search_rank: 5
 
 \[**ワークスペースの内訳**] を使用すると、各ワークスペースの詳細なデータポイントデータを表示できます。ワークスペースをクリックすると、そのデータポイントの詳細が表示されます。
 
-![請求可能データポイントのワークスペース訓練][9]{: style="max-width:90%;"}
+![請求可能なデータポイントのワークスペースの内訳][9]{: style="max-width:90%;"}
 
 ##### カテゴリ別のワークスペースレベルデータポイント使用量
 
-ワークスペースの名前の横にあるメニューを選択し、<サービスプロバイダー an id="1">Billable Data Points For ワークスペース_NAME</サービスプロバイダー an>を選択して、<サービスプロバイダー an id="2">カテゴリ別のワークスペースレベルデータポイント使用状況</サービスプロバイダー an>テーブルを表示します。このテーブルには、データポイントsのカテゴリごとにデータポイント数が表示されます。例えば、セッションやカスタムイベントによって使用されるデータポイント数を確認できます。この表を使用して、ワークスペースのデータポイント消費を促進しているデータポイントカテゴリを特定できます。
+ワークスペースの名前の横にあるメニューを選択し、<サービスプロバイダー **Billable Data Points For ワークスペース_NAME**/サービスプロバイダー an>を選択して、<サービスプロバイダー **カテゴリ別のワークスペースレベルデータポイント使用状況</サービスプロバイダー **テーブルを表示します。このテーブルには、データポイントのカテゴリごとにデータポイントカウントが表示されます。例えば、セッションやカスタムイベントによって使用されるデータポイント数を確認できます。この表を使用して、ワークスペースのデータポイント消費を促進しているデータポイントカテゴリを特定できます。
 
 ![カテゴリ別のワークスペースレベルデータポイントの使用状況][10]{: style="max-width:90%;"}
 
 ##### ワークスペースレベルのデータポイント使用量の推移
 
-** Time** のワークスペースレベルデータポイント使用量テーブルは、ワークスペースのデータポイント使用量が課金周期全体でどのように変化したかを示します。
+\[**経時的なワークスペースレベルのデータポイント使用量**] の表には、請求サイクルにわたるワークスペースのデータポイント使用量の変化が表示されます。
 
 ![時間経過に伴うワークスペースレベルのデータポイントの使用状況][11]{: style="max-width:90%;"}
 
 ##### アプリケーションレベルトータルデータポイント使用量
 
-** アプリ Level Total データポイント使用量** テーブルには、ワークスペース内のアプリs ごとのデータポイント使用量が表示されます。この表を使用して、ワークスペースのデータポイント消費を促進しているアプリを特定できます。
+\[**アプリレベルのデータポイント使用量の合計**] の表には、ワークスペース内の各アプリのデータポイント使用量が表示されます。この表を使用して、ワークスペースのデータポイント消費を促進しているアプリを特定できます。
 
-![多重アプリのためのアプリレベル総データポイント使用量テーブル][12]{: style="max-width:90%;"}
+![複数アプリのアプリレベルにおけるデータポイント使用量の合計の表][12]{: style="max-width:90%;"}
 
 
 [2]: {% image_buster /assets/img/subscription_and_billing2.png %}
diff --git a/_lang/ja/_user_guide/administrative/app_settings/workspaces.md b/_lang/ja/_user_guide/administrative/app_settings/workspaces.md
index d1af4ed2c7e..4367aff8b87 100644
--- a/_lang/ja/_user_guide/administrative/app_settings/workspaces.md
+++ b/_lang/ja/_user_guide/administrative/app_settings/workspaces.md
@@ -21,7 +21,7 @@ Braze での操作はすべて、ワークスペース内で行われます。
 
 始める前に、チームや Braze のオンボーディングマネージャーと協力して、ユースケースに最適なワークスペース構成を決定する必要があります。Braze でのワークスペース計画の詳細については、\[開始;ワークスペース]\[link] ガイド。
 
-### ステップ2:ワークスペースの追加
+### ステップ 2: ワークスペースの追加
 
 グローバルヘッダーのワークスペースのドロップダウンから、新しいワークスペースを作成したり、既存のワークスペース間で切り替えたりできます。
 
@@ -30,14 +30,14 @@ Braze での操作はすべて、ワークスペース内で行われます。
 ![][1]
 
 {:start="2"}
-2. ワークスペースに名前を付けます。
+2\.ワークスペースに名前を付けます。
 
 {% alert tip %}
-社内の他のユーザーがこのワークスペースを簡単に見つけられるように、命名規則を採用することをお勧めします。例えば、「Upon Voyage US - Production」と「On Voyage US - Staging」です。
+社内の他のユーザーがこのワークスペースを簡単に見つけられるように、命名規則を採用することをお勧めします。以下に例を示します。「Upon Voyage US - Production」と「On Voyage US - Staging」です。
 {% endalert %}
 
 {:start="3"}
-3\.**Create**を選択します。Braze が ワークスペースを作成するまで数秒かかることがあります。
+3\.\[**作成**] を選択します。Braze が ワークスペースを作成するまで数秒かかることがあります。
 
 ![][2]
 
@@ -55,7 +55,7 @@ Braze での操作はすべて、ワークスペース内で行われます。
 ![][4]{: style="max-width:60%" }
 
 {:start="3"}
-3. \[**アプリを追加**] をクリックして確定します。
+3\.\[**アプリを追加**] をクリックして確定します。
 
 #### アプリの API キー
 
@@ -69,7 +69,7 @@ Braze での操作はすべて、ワークスペース内で行われます。
 
 #### ライブ SDK バージョン
 
-アプリの「設定」ページに表示されるライブSDKのバージョンは、最高アプリのバージョンで、1日の総セッションsの少なくとも5%が表示され、過去1日で少なくとも500 セッションsが表示されます。
+特定アプリの \[アプリ設定] ページに表示される \[ライブ SDK バージョン] は、1 日の総セッション数の 5% を占める最高のアプリバージョンであり、過去 1 日で少なくとも 500 件のセッションがあります。
 
 このフィールドは、Braze SDK とアプリまたは Web サイトを連携した後に表示されます。新しいバージョンの Braze SDK がプラットフォームで利用可能の場合、「新しいバージョンが利用可能」というタグとともにここに表示されます。
 
diff --git a/_lang/ja/_user_guide/administrative/privacy.md b/_lang/ja/_user_guide/administrative/privacy.md
index e0accfbaa76..f221c6b5116 100644
--- a/_lang/ja/_user_guide/administrative/privacy.md
+++ b/_lang/ja/_user_guide/administrative/privacy.md
@@ -11,7 +11,7 @@ page_type: reference
 
 guide_featured_title: "記事"
 guide_featured_list:
-- name: データ保護技術支援
+- name: データ保護のテクニカルサポート
   link: /docs/dp-technical-assistance
   image: /assets/img/braze_icons/database-01.svg
 - name: スパム規制
diff --git a/_lang/ja/_user_guide/administrative/privacy/spam_regulations.md b/_lang/ja/_user_guide/administrative/privacy/spam_regulations.md
index 624cb64cb4e..1d47605e1a8 100644
--- a/_lang/ja/_user_guide/administrative/privacy/spam_regulations.md
+++ b/_lang/ja/_user_guide/administrative/privacy/spam_regulations.md
@@ -86,7 +86,7 @@ CASL には 2017 年 7 月 1 日まで 3 年間の移行期間がありますが
 
 ## スパムフィルター
 
-メールが正常に送信されても、必ずしも読まれたとは限りません。各フィルターは独自の方法でメールの「スパムスコア」を評価するため、すべてのスパムフィルターを回避する万能のソリューションはありません。しかし、あなたのEメールが "スパム "であるというレッテルを貼られないようにするためのヒントをいくつか紹介しよう。
+メールが正常に送信されても、必ずしも読まれたとは限りません。各フィルターは独自の方法でメールの「スパムスコア」を評価するため、すべてのスパムフィルターを回避する万能のソリューションはありません。ここでは、メールに「スパム」のラベルが付けられないようにするためのヒントをいくつか紹介します。
 
 ### 許可を得る
 
diff --git a/_lang/ja/_user_guide/brazeai.md b/_lang/ja/_user_guide/brazeai.md
new file mode 100644
index 00000000000..cfed4117e92
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai.md
@@ -0,0 +1,43 @@
+---
+nav_title: BrazeAI
+article_title: BrazeAI
+page_order: 6.5
+layout: dev_guide
+search_rank: 12
+guide_top_header: "BrazeAI<sup>TM</sup>"
+guide_top_text: "BrazeAI<sup>TM</sup>は、エンゲージメント戦略のための創造性、パーソナライゼーション、最適化のための参入障壁を低くする、アクセシブルで使いやすいツールの集合体に力を与えます。BrazeAI<sup>TM</sup> 機能を使用すると、信頼できるアドバイザーを使用して、クリエイティビティを導き、より良い決定を行い、顧客のためにユーザエクスペリエンスを最適化することができます。"
+description: "BrazeAI<sup>TM</sup>は、エンゲージメント戦略のための創造性、パーソナライゼーション、最適化のための参入障壁を低くする、アクセシブルで使いやすいツールの集合体に力を与えます。"
+
+Tool:
+  - Dashboard
+
+guide_featured_title: "特長"
+guide_featured_list:
+- name: Intelligence Suite
+  link: /docs/user_guide/brazeai/intelligence/
+  image: /assets/img/braze_icons/clock.svg
+- name: Predictive Suite
+  link: /docs/user_guide/brazeai/predictive_suite/
+  image: /assets/img/braze_icons/stars-01.svg
+- name: 生成 AI
+  link: /docs/user_guide/brazeai/generative_ai/
+  image: /assets/img/braze_icons/lightbulb-02.svg
+
+guide_menu_title: "Other"
+guide_menu_list:
+- name: 勝者バリアントとパーソナライズされたバリアント
+  link: /docs/user_guide/engagement_tools/testing/multivariant_testing/optimizations/
+  image: /assets/img/braze_icons/trophy-01.svg
+- name: 勝者パス
+  link: /docs/user_guide/engagement_tools/canvas/canvas_components/experiment_step/winning_path/
+  image: /assets/img/braze_icons/dataflow-03.svg
+- name: パーソナライズされたパス
+  link: /docs/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths/
+  image: /assets/img/braze_icons/chevron-up-double.svg
+- name: おすすめ
+  link: /docs/user_guide/brazeai/recommendations/
+  image: /assets/img/braze_icons/hearts.svg
+---
+
+
+<br>
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/brazeai/generative_ai.md b/_lang/ja/_user_guide/brazeai/generative_ai.md
new file mode 100644
index 00000000000..c46cf612638
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/generative_ai.md
@@ -0,0 +1,31 @@
+---
+nav_title: 生成 AI
+article_title: 生成 AI
+page_order: 20
+layout: dev_guide
+guide_top_header: "生成 AI"
+guide_top_text: "BrazeAI<sup>TM</sup>は、効率性と創造性を高める様々なオートメーション生成AI機能を搭載している。定型的なコピーライティング作業、コンテンツの改良、画像写真の作成に費やす時間を減らしながら、魅力的なクロスチャネルのカスタマーエクスペリエンスを創造する。<br><br>詳しくは以下の記事を学習してほしい。"
+description: "BrazeAI<sup>TM</sup>は、効率性と創造性を高める様々なオートメーション生成AI機能を搭載している。"
+
+guide_featured_title: "特徴"
+guide_featured_list:
+- name: AIコピーライティング・アシスタント
+  link: /docs/user_guide/brazeai/generative_ai/ai_copywriting/
+  image: /assets/img/braze_icons/edit-05.svg
+- name: AI 画像ジェネレーター
+  link: /docs/user_guide/engagement_tools/templates_and_media/media_library/#generate-ai
+  image: /assets/img/braze_icons/image-03.svg
+- name: AIコンテンツQA
+  link: /docs/user_guide/brazeai/generative_ai/ai_content_qa/
+  image: /assets/img/braze_icons/clipboard-check.svg
+- name: AI Liquidアシスタント
+  link: /docs/user_guide/brazeai/generative_ai/ai_liquid/
+  image: /assets/img/braze_icons/beaker-02.svg
+- name: SQLクエリビルダ
+  link: /docs/user_guide/data_and_analytics/query_builder/
+  image: /assets/img/braze_icons/tool-01.svg
+- name: SQLセグメンテーション
+  link: /docs/sql_segments/
+  image: /assets/img/braze_icons/users-01.svg
+
+---
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/brazeai/generative_ai/ai_content_qa.md b/_lang/ja/_user_guide/brazeai/generative_ai/ai_content_qa.md
new file mode 100644
index 00000000000..b21937f705c
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/generative_ai/ai_content_qa.md
@@ -0,0 +1,55 @@
+---
+nav_title: AI によるコンテンツ QA
+article_title: AI によるコンテンツ QA
+page_order: 10
+description: "このリファレンス記事では、メッセージ作成画面から AI を直接使用してメッセージコンテンツの品質保証を実行する方法について説明します。"
+---
+
+# AI によるコンテンツ QA
+
+> メッセージ作成画面から AI を直接使用してメッセージコンテンツの品質保証を実行する方法を学習します。
+
+AI によるコンテンツ QA では、GPT と OpenAI の機能を使用してメッセージコンテンツをチェックし、スペルミス、文法の問題、不適切なトーン、不快な言葉遣いなど、効果的でない要素を特定することで、メッセージコンテンツが確実に品質基準を満たすようにすることができます。キャンペーンやキャンバスでプッシュ、SMS、アプリ内メッセージを作成する際、**Test**タブからこの機能にアクセスできる。
+
+## 主な機能
+
+AIによるコンテンツQAは、メッセージ・コンテンツの品質を高めるために、以下の主要な機能を提供する：
+
+- **スペルと文法のチェック:**メッセージのスペルミスや文法ミスを自動的にチェックします。コンテンツの全体的な正確性を向上させるために、修正を提案し、推奨事項を提示する。
+- **トーン分析:**メッセージのトーンを評価し、潜在的な問題を識別する。意図したトーンを目的のコミュニケーションスタイルと一致させ、誤解や意図しない無礼を避けるために役立ちます。
+- **無礼な言葉遣いの検出:**無礼または不適切な言葉遣いがないかメッセージをスキャンするため、コンテンツを修正して丁寧なコミュニケーションを維持できます。
+- **偶発的なコンテンツのチェック:**意図せずに追加されたコード、マークアップ言語、またはテストメッセージが含まれている場合に検出します。
+
+## AIでコンテンツQAにアクセスする
+
+{% alert note %}
+AIによるコンテンツQAは、現時点ではプッシュとSMSチャネルでのみ利用できる。
+{% endalert %}
+
+コンテンツチェッカーにアクセスするには、次の手順に従います。
+
+1. プッシュまたはSMSメッセージを作成したら、**Test**タブに移動する。
+2. **AIによるコンテンツQA**セクションを探す。
+3. \[**コンテンツのテスト**] をクリックします。
+
+![テストタブのAIセクションでコンテンツQAを行う。][1]{: style="max-width:60%"}
+
+### 言語サポート
+
+GPTは[複数の言語](https://openai.com/research/gpt-4#:~:text=GPT%2D4%203%2Dshot%20accuracy%20on%20MMLU%20across%20languages)を理解できますが、OpenAI は複数の言語を公式にはサポートしていません。メッセージコンテンツを OpenAI に送信するときに、Braze は文章の言語やロケールに関する追加情報を渡しません。したがって、その決定は GPT によって行われます。
+
+結果は書く言語によって異なるかもしれない。
+
+## 効果的な使い方のヒント
+
+AIによるコンテンツQA機能を最大限に活用するために、以下のヒントを考えてみよう：
+
+- **メッセージの校正:**コンテンツチェッカーはエラーの識別に役立つが、それでもコンテンツの校正は手作業で行うことが不可欠だ。AIが生成した提案は有用なガイドとして頼りにするが、正確さを期すために自分の判断を使うこと。
+- **トーン分析の解釈:**トーン分析の結果は主観的で、AI モデルの理解に基づいています。有用なインサイトを提供することもできるが、あなたの意図するトーンと会話の文脈を考慮し、適切な調整を行うこと。
+- **フラグが設定された無礼な言葉遣いのダブルチェック:**無礼な言葉遣いの検出は堅牢に設計されていますが、誤検知によりフラグを設定する可能性があります。フラグが立った箇所を注意深く見直し、必要に応じて適切な変更を加える。
+
+## データはどのように使用されて、OpenAI に送信されるのですか?
+
+メッセージの内容を確認するために、BrazeはOpenAIのAPIプラットフォームにメッセージを送信する。Braze から OpenAI に送信されるすべてのクエリは匿名化されます。つまり、提供するメッセージコンテンツに一意に識別できる情報を含めない限り、OpenAI はクエリの送信元を特定できません。[OpenAI の API プラットフォームコミットメント](https://openai.com/policies/api-data-usage-policies)に詳述されているように、Braze 経由で OpenAI の API に送信されたデータは、モデルのトレーニングや改善には使用されず、30日後に削除されます。お客様に関連する OpenAI のポリシーを必ず遵守してください。これには、OpenAI の[使用ポリシー](https://openai.com/policies/usage-policies)や[共有および公開ポリシー](https://openai.com/policies/sharing-publication-policy)が含まれる場合があります。Braze は AI が生成したコンテンツに関していかなる種類の保証も行いません。
+
+[1]: {% image_buster /assets/img/content_qa_ai.png %}
diff --git a/_lang/ja/_user_guide/brazeai/generative_ai/ai_copywriting.md b/_lang/ja/_user_guide/brazeai/generative_ai/ai_copywriting.md
new file mode 100644
index 00000000000..df6ee29ff6d
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/generative_ai/ai_copywriting.md
@@ -0,0 +1,52 @@
+---
+nav_title: AIコピーライティングアシスタント
+article_title: AIコピーライティングアシスタント
+page_order: 4
+description: "この記事では、AI のコピーライティングアシスタントについて説明します。この機能は、OpenAI の GPT コピー生成ツールに製品名や簡単な説明を渡し、メッセージングで使用できる、人間が書いたように自然なマーケティングコピーを生成します。"
+---
+
+# AIコピーライティングアシスタント
+
+> AI のコピーライティングアシスタントは、OpenAI の GPT コピー生成ツールに製品名や簡単な説明を渡し、メッセージングで使用できる、人間が書いたように自然なマーケティングコピーを生成します。この機能は、Braze ダッシュボード内のほとんどのメッセージ作成画面でデフォルトで使用できます。
+
+## コピーの作成 {#steps}
+
+AI コピーライティングアシスタントを使用してコピーを生成するには、次の手順に従います。
+
+1. メッセージ作成画面から、<i class="fa-solid fa-wand-magic-sparkles"></i> \[**AI コピーライターを起動**] を選択します。
+   * アプリ内メッセージのドラッグ＆ドロップエディターで、テキストブロックを選択し、ブロックのツールバーで \[<i class="fa-solid fa-wand-magic-sparkles" title="AI コピーライター"></i>] を選択します。
+2. 入力フィールドに製品名または説明を入力します。
+3. 出力のおおよその長さを選択します。チャンネル固有のベストプラクティスに基づいて、出力長の特定のチャンネルを選択したり、短い(1 センテンス)、中程度(2～3 センテンス)、長い(1 パラグラフ)のいずれかを選択したりできます。 
+4. (オプション) ブランドガイドラインを作成するか適用して、このコピーをブランド用にカスタマイズします。これらのガイドラインはワークスペースに保存され、作成後に再利用できます。詳細については、[ブランドガイドラインの作成]({{site.baseurl}}/user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines/)を参照してください。
+5. (オプション) 使用可能なオプションからメッセージトーンを選択します。これにより、生成されるコピーのスタイルが決まります。
+6. (オプション)プッシュ通知に使用できます。**過去のキャンペーンデータを参照**を選択すると、以前のモバイルプッシュメッセージ(キャンペーンとキャンバスステップ)が新しいコピーを生成するためのスタイルの参照として使用されます。選択すると、出力は以前のメッセージのスタイルを模倣します。
+7. 出力言語を選択する。これは入力言語とは異なる場合があります。
+8. **生成** をクリックします。
+
+私たちは、あなたが提供した情報を使用して、あなたのためにコピーを書くようにGPTに促します。応答は OpenAI から取得され、ユーザーに提供されます。 
+
+![AI copywriting assistant modalは、利用可能なさまざまな機能を示します。][1]{: style="max-width:70%;"}
+
+{% alert important %}
+OpenAI の[content policy](https://beta.openai.com/docs/usage-guidelines/content-policy) に違反する攻撃コンテンツの応答をフィルタリングします。
+{% endalert %}
+
+## 過去のキャンペーンデータの使用
+
+出力長としてプッシュを使用する場合、\[**過去のキャンペーンデータを参照**] を選択すると、ランダムに選択された以前のモバイルプッシュキャンペーンが OpenAI に送信され、これを GPT がコピー生成のベースとして使用できるようになります。この機能を活用しない場合は、このボックスをオフのままにします。Braze および OpenAI でのデータの使用方法の詳細については、次のセクションを参照してください。 
+
+[ブランドガイドライン]({{site.baseurl}}/user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines/)と組み合わせて使用すると、ブランドガイドラインと過去のキャンペーンデータの両方が最終出力に組み込まれます。
+
+## GPTとは。
+
+[GPT](https://openai.com/product/gpt-4)は、人工知能を駆使したOpenAIの最先端の自然言語生成ツールです。テキストの生成、完了、分類など、さまざまな自然言語タスクを実行できます。弊社ではこれを Braze ダッシュボードに組み入れ、作業している最中にコピー作成のためのヒントやバリエーションを直接得られるようにしています。
+
+## データはどのように使用されて、OpenAI に送信されるのですか?
+
+コピーを生成するために、Braze は OpenAI にクエリを送信します。Braze から OpenAI に送信されるすべてのクエリは匿名化されます。したがって、ユーザーが提供する入力内容や、「過去のキャンペーンデータを参照」というオプションを有効にした場合は過去のキャンペーンデータの中に一意に識別可能な情報を含めない限り、OpenAI がクエリの送信元を特定することはできません。[OpenAI のポリシー](https://openai.com/policies/api-data-usage-policies) により、Braze 経由でOpenAI のAPI に送信されたデータは、モデルのトレーニングや改善には使用されず、30 日後に削除されます。お客様と Braze の間で、GPT を使って生成されたコンテンツはすべて、お客様の知的財産となります。Braze は、当該コンテンツに関する著作権所有権の主張を主張せず、AI が生成したコンテンツに関していかなる種類の保証も行いません。
+
+## その他のAI ツール
+
+また、メディアライブラリを使って [AI で画像を生成]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/media_library/#generate-ai)することもできます。これは、[DALL·E 3](https://openai.com/index/dall-e-3/)を活用しています。これは、自然言語の記述からリアルなイメージやアートを作成できるOpenAIのAIシステムです。
+
+[1]: {% image_buster /assets/img/ai_copywriter/gpt3.png %} "GPT3"
diff --git a/_lang/ja/_user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines.md b/_lang/ja/_user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines.md
new file mode 100644
index 00000000000..14ba92f1dc1
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/generative_ai/ai_copywriting/brand_guidelines.md
@@ -0,0 +1,69 @@
+---
+nav_title: ブランドガイドライン
+article_title: AIコピーライティングのためのブランド・ガイドライン
+page_order: 1
+description: "この参考記事では、AIコピーライティングアシスタントのブランドガイドラインを取り上げる。AIコピーライティングアシスタントが生成するコピーのスタイルを、ブランドの声やスタイルに合わせて調整できる機能だ。"
+---
+
+# AIコピーライティング・アシスタントのブランド・ガイドライン
+
+> カスタマイズされたブランドガイドラインで、AIが生成するコピーのスタイルをブランドの声や個性に合わせて調整する。
+
+## ブランド・ガイドラインを作成する {#steps}
+
+以下のステップに従い、AIコピーライティングアシスタントでブランドガイドラインを作成する。
+
+### ステップ 1:ブランドガイドラインを作成する
+
+1. メッセージ作成画面から、<i class="fa-solid fa-wand-magic-sparkles"></i> \[**AI コピーライターを起動**] を選択します。
+   * アプリ内メッセージのドラッグ＆ドロップエディターで、テキストブロックを選択し、ブロックのツールバーで \[<i class="fa-solid fa-wand-magic-sparkles" title="AI コピーライター"></i>] を選択します。
+2. **Apply brand guidelineを**選択し、次に**Create a brand guidelineを**選択する。
+3. このガイドラインの名前を入力する。前の選択で表示されたラベルになる。
+4. **このブランド・ガイドラインをいつ使用しますか**」には、同僚（そして将来のあなた）がこのガイドラインを使用する背景を理解できるよう、詳細を加える。
+
+![ブランド・ガイドライン作成の見解。][1]
+
+### ステップ 2:ブランドのパーソナリティを説明する
+
+**ブランド・パーソナリティについては**、何があなたのブランドをユニークなものにしているかを考える。あなたのブランドを定義する特徴、価値観、声、あらゆる原型を含める。以下は、考慮すべきいくつかの特徴である：
+
+| **特徴**       | **定義**                                                                       | **例**                                                        |
+|--------------------------|--------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+| レピュテーション               | あなたのブランドがマーケットでどのように認知されたいか。                               | 私たちは業界で最も信頼性が高く、顧客重視のブランドとして知られている。 |
+| パーソナライゼーションの特徴       | あなたのブランドの特徴を表す、人間らしい特徴。                     | 私たちのブランドはフレンドリーで親しみやすく、常に明るい。          |
+| 価値観                   | ブランドのアクションや意思決定の指針となるコアバリュー。                           | 私たちは、持続可能性、透明性、そしてコミュニティを大切にしている。            |
+| 差別化          | あなたのブランドを競合他社から際立たせる独自の品質。                         | それ以上のパーソナライズされた顧客サービスを提供することで、私たちは際立った存在となっている。 |
+| ブランド・ボイス              | あなたのブランドが使うコミュニケーションのトーンとスタイル。                                 | 私たちの声はカジュアルでありながら情報量が多く、堅苦しくなりすぎず明瞭である。 |
+| ブランドの原型          | あなたのブランドのペルソナ（ヒーロー、創造主など）を表す原型。    | 私たちは「探検家」の原型を体現し、常に新しい挑戦と冒険を求めている。 |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+### ステップ 3:避けるべき言葉を定義する（オプション）
+
+**除外項目には**、あなたのブランドと一致しない言葉やスタイルを列挙する。例えば、「皮肉」「否定的な態度」「慇懃無礼」なトーンは避けた方がいいかもしれない。
+
+### ステップ 4:ガイドラインをテスト
+
+ガイドラインをテストし、そのパフォーマンスを確認する。拡大**ガイドラインをテストして**コピー例を作成し、必要に応じて調整する。
+
+### ステップ 5: ガイドラインを保存する
+
+ガイドラインに満足したら、**ブランドのガイドラインを保存する**。新しいガイドラインは、今後使用できるようにワークスペースに保存される。
+
+{% alert important %}
+コピーの言語に関係なく出力言語を変更できるが、BrazeもOpenAIも翻訳の品質を保証しない。翻訳を使用する前に、必ずテストと検証を行うこと。
+{% endalert %}
+
+## 編集ガイドライン
+
+既存のブランド・ガイドラインを編集する：
+
+1. AIコピーライティングアシスタントを開封する。
+2. 変更したいブランドガイドラインを適用する。フィールドの近くにボタンが表示される。
+3. **ガイドラインの編集を**選択する。
+
+## データはどのように使用されて、OpenAI に送信されるのですか?
+
+ブランドガイドラインを使ってコピーを生成するために、Brazeはガイドラインの内容を含む問い合わせをOpenAIに送る。Braze から OpenAI に送信されるすべてのクエリは匿名化されます。したがって、ユーザーが提供する入力内容や、「過去のキャンペーンデータを参照」というオプションを有効にした場合は過去のキャンペーンデータの中に一意に識別可能な情報を含めない限り、OpenAI がクエリの送信元を特定することはできません。[OpenAIのポリシーにより](https://openai.com/policies/api-data-usage-policies)、Braze経由でOpenAIのAPIに送られたデータは、モデルのトレーニングや改良には使用されず、30日後に削除される。お客様と Braze の間で、GPT を使って生成されたコンテンツはすべて、お客様の知的財産となります。Brazeは、かかるコンテンツの著作権所有権を主張せず、AIが生成したコンテンツに関していかなる保証も行わない。
+
+
+[1]: {% image_buster /assets/img/ai_copywriter/manual_brand_guidelines.png %} 「ブランド・ガイドライン
diff --git a/_lang/ja/_user_guide/brazeai/generative_ai/ai_liquid.md b/_lang/ja/_user_guide/brazeai/generative_ai/ai_liquid.md
new file mode 100644
index 00000000000..6413083bee6
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/generative_ai/ai_liquid.md
@@ -0,0 +1,78 @@
+---
+nav_title: BrazeAIリキッドアシスタント
+article_title: BrazeAIリキッドアシスタント
+description: "この記事では、AI Liquid Assistant の仕組みと、メッセージング用のLiquid スニペットを生成するためのAI Liquid Assistant の使用方法について説明します。"
+page_type: reference
+page_order: 5
+---
+
+# BrazeAI<sup>TM</sup> 液体アシスタント
+
+> BrazeAI<sup>TM</sup> Liquid Assistant は、BrazeAI<sup>TM</sup> を搭載したチャットアシスタントで、メッセージコンテンツをパーソナライズするために必要なLiquid の生成に役立ちます。SMS メッセージの作成、プッシュ通知、HTML メールキャンペーン、およびキャンバスの作成時に使用できます。メールチャネルの場合、アシスタントはテンプレートではなくメールメッセージで動作し、既に構築されているメールメッセージで最適に動作します。
+
+BrazeAI<sup>TM</sup> Liquid Assistant を使用すると、テンプレートからLiquid を生成したり、パーソナライズされたLiquid の提案を受信したり、BrazeAI<sup>TM</sup> をサポートして既存のLiquid を最適化したりすることができます。アシスタントには、使用されている液体を説明するアノテーションも用意されているため、Liquid についての理解を深め、自分で書くことを学ぶことができます。
+
+## その仕組み
+
+BrazeAI<sup>TM</sup> Liquid Assistant は、お客様のマーケティングニーズに合わせた効果的なLiquid コードの作成を支援するよう設計されています。リキッドのシンタックスと、マーケターがリキッドをどのようにメッセージに活用するかの両方についてトレーニングを受け、私たちのAIはパーソナライズされたコンテンツを作り上げるニュアンスを理解しています。さらに、BrazeAI<sup>TM</sup> Liquid Assistant にカスタム属性名("favourite_color" など) とデータ型(boolean やstring など) を指定することで、BrazeAI<sup>TM</sup> Liquid Assistant を使用することで、メッセージが正確にターゲット設定され、目標に合わせて調整されます。さらに、ブランド・ガイドラインを作成する場合、BrazeAI<sup>TM</sup>Liquid Assistantは、ブランド・ガイドラインを使用して、生成された出力をより適切にカスタマイズし、コンテンツを自社のブランド・ボイスにカスタマイズすることができる。あなたが作成したブランドガイドラインは、あなた自身の使用のためにコンテンツをパーソナライズするためにのみ使用されます。 
+
+## Liquid コードの生成
+
+BrazeAI<sup>TM</sup>Liquid assistantを起動するには、メッセージコンポーザーでAI assistantアイコンを選択します。
+
+![AI アシスタントを持つメッセージ作成画面。][1]{: style="max-width:50%;"}
+
+[提供されたプロンプト](#provided-prompts)を選択するか、テキストボックスに独自の情報を入力することができます。Liquid コードを生成するには、\[**作成ツールを更新**] を選択します。
+
+![プロンプトが表示された AI アシスタントウィンドウ。][2]{: style="max-width:50%;"}
+ 
+同じプロンプトを使用して別のメッセージを生成するには、**Regenerate**を選択します。メッセージを削除して前のメッセージに戻すには、**Undo update** を選択します。
+
+### 提供されるプロンプト
+
+BrazeAI<sup>TM</sup> Liquid Assistant の使用中に、Liquid の使用を開始するためのさまざまなプロンプトが表示されることがあります。プロンプトの一部を以下に示します。
+
+#### アプリアクティビティを使用
+
+**Use app activity** プロンプトは、アプリが最後に使用された日時に基づいて異なるメッセージを送信するのに役立つLiquid コードを生成します。アシスタントがより正確な結果を得ることができるように、フォローアップの質問を受けることがあります。
+
+![「アプリアクティビティの使用」プロンプトの出力例。][3]{: style="max-width:45%;"}
+
+#### カウントダウンの追加
+
+このプロンプトは、イベントが開始されるまでの時間を含むメッセージを送信する Liquid コードを生成します。イベント日時の詳細を入力するように要求されます。
+
+!["Add countdown"プロンプトの出力例。][4]{: style="max-width:45%;"}
+
+#### インスピレーションの指定
+
+このプロンプトは、メッセージボックスに内容がある場合に表示されます。Liquidでメッセージをパーソナライズするために選択できるオプションのリストが生成されます。 
+
+!["Inspire me"プロンプトの出力例。][5]{: style="max-width:45%;"}
+
+#### Liquid を改善
+
+このプロンプトは、メッセージ作成画面に内容がある場合に表示されます。アシスタントがコードをより効率的に読みやすくする場合に選択します。
+
+![「Liquid を改善」プロンプトの出力例。][6]{: style="max-width:45%;"}
+
+## ベータでサポートされる属性
+
+| 条件 | ナレッジタイプ |
+| - | - |
+| 液体(`for` ループ、`if` ステートメント、数学、その他を含む) | コーディング|
+| デフォルトおよび標準ユーザー属性| 属性|
+| 以下のいずれかのデータ型を持つカスタム属性: {::nomarkdown}<ul><li>ブール値</li><li>数値</li><li>文字列</li><li>配列</li><li>時刻</li></ul>{:/} | 属性 |
+| 接続されたコンテンツ| コーディング|
+{: .reset-td-br-1 .reset-td-br-2 }
+
+## データはどのように使用されて、OpenAI に送信されるのですか?
+
+メッセージコンテンツを変更または作成するために、Braze は、BrazeAI<sup>TM</sup> AI アシスタントに送信されたプロンプト、メッセージコンテンツ、ブランドガイドライン(作成する場合) をOpenAI のAPI プラットフォームに送信します。Braze から OpenAI に送信されるすべてのクエリは匿名化されます。つまり、提供するコンテンツに一意に識別できる情報を含めない限り、OpenAI はクエリの送信元を特定できません。[OpenAIのAPIプラットフォームコミットメント](https://openai.com/policies/api-data-usage-policies)に詳述されているように、Braze経由でOpenAIのAPIに送信されるデータは、モデルのトレーニングや改良には使用されず、30日後に削除されます。[Usage policies](https://openai.com/policies/usage-policies) とその[Sharing & publication policy](https://openai.com/policies/sharing-publication-policy) を含む、OpenAI の関連ポリシーを遵守してください。Braze は AI が生成したコンテンツに関していかなる種類の保証も行いません。
+
+[1]: {% image_buster /assets/img/ai_liquid/ai_assistant_icon.png %}
+[2]: {% image_buster /assets/img/ai_liquid/ai_assistant_window.png %}
+[3]: {% image_buster /assets/img/ai_liquid/use_app_activity.png %}
+[4]: {% image_buster /assets/img/ai_liquid/add_countdown.png %}
+[5]: {% image_buster /assets/img/ai_liquid/inspire_me.png %}
+[6]: {% image_buster /assets/img/ai_liquid/improve_my_liquid.png %}
diff --git a/_lang/ja/_user_guide/brazeai/generative_ai/ai_liquid/ai_liquid_prompts.md b/_lang/ja/_user_guide/brazeai/generative_ai/ai_liquid/ai_liquid_prompts.md
new file mode 100644
index 00000000000..fc34de868c6
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/generative_ai/ai_liquid/ai_liquid_prompts.md
@@ -0,0 +1,71 @@
+---
+nav_title: プロンプトについて
+article_title: BrazeAI 液体アシスタントのプロンプトについて
+description: "この記事では、ベストプラクティスやプロンプト例など、AI Liquid Assistant のプロンプトを表示する方法について説明します。"
+page_type: reference
+page_order: 0
+noindex: true
+---
+
+# BrazeAI<sup>TM</sup> Liquid Assistant のプロンプトについて
+
+> プロンプトとは、BrazeAI<sup>TM</sup> Liquid Assistant に、何をしたいかを明確に指示するプロセスです。
+
+BrazeAI<sup>TM</sup> Liquid Assistantは、影響力のあるマーケティングメッセージを作成するためにBraze and Liquidを使用するエキスパートであるクラス最高のマーケターとして機能するように設計されていますが、それでも特定のユースケースや質問に関するガイダンスが必要です。
+
+アシスタントにプロンプトを表示する正しい方法は1 つもありません。会話中にプロンプトに詳細をいつでも追加できます。つまり、「完璧な」最初のプロンプトの作成に多くの時間を費やす必要はありません。ただし、いくつかのベストプラクティスに従うことで、アシスタントを最大限に活用できます。
+
+## 効果的なプロンプトのためのベストプラクティス
+
+### 自然言語の使用
+
+BrazeAI<sup>TM</sup> Liquid Assistant は自然言語を理解するためのトレーニングを受けています。助けを求めるときは、同僚と同じようにチャットしてください。これにより、アシスタントがニーズを理解し、正確な支援を提供しやすくなります。
+
+### コンテキストを与える
+
+コンテキストを提供すると、BrazeAI<sup>TM</sup> Liquid Assistant がプロジェクトを取り巻く大きな画像を理解するのに役立ちます。次のようなコンテキストを含めると便利です。
+
+- 貴社名・業界
+- ブラック・フライデーやホリデー・セールなど、あなたが取り組んでいるキャンペーン
+- クリックスルー率を上げるなど、目標
+- メッセージに含める特定のカスタム属性
+
+プロンプトにコンテキストを含めると、アシスタントは、必要に応じて対応を調整できます。また、キャンペーン、メッセージ・ブリーフ、またはブレインストーミング・ドキュメントの詳細を含めると、アシスタントを高速化できます。
+
+### 特異的である
+
+BrazeAI<sup>TM</sup> Liquid Assistant はフォローアップの質問をすることができますが、詳細を事前に指定するとより正確な結果がより早く得られる可能性があります。以下のような詳細を含めることを検討してください。
+
+- メッセージの既知のプリファレンスまたは要件
+- メッセージ受信者からの応答不足やフォールバックメッセージオプションなどの状況の処理方法に関する指示
+- Connected Content を使用するLiquid、API エンドポイントのドキュメント、サンプルAPI レスポンス、またはその両方を要求する場合
+
+### クリエイティブを手に入れる
+
+BrazeAI<sup>TM</sup>Liquid Assistantがどのようにメッセージングを向上させるか、プロンプトとともにボックスの外側で考えてみましょう。クリエイティビティはより魅力的な結果につながる可能性があるため、さまざまなプロンプトやアイデアを試してみてください。
+
+## プロンプトの例
+
+インスピレーションが必要ですか?以下のプロンプトをチェックして、試してみてください(または、お好みに合わせて調整してください)。
+
+### 一般情報
+
+- Liquidとは何か、そしてどのようにすれば、Braze内のマーケティングキャンペーンのパーソナライズを強化するのに役立つか。
+- リキッドでは、人口統計情報や過去の購入など、マーケティングメッセージをカスタマイズするためにどのようなデータを使用できますか?
+
+### パーソナライゼーションと動的コンテンツ
+
+- 顧客のロイヤルティステータスに基づいて、異なるコンテンツを表示するメッセージを作成します。彼らのロイヤルティ状況がわからない場合は、フォールバックメッセージを送信します。
+- ユーザーのお気に入りの製品とその最終購入日を含む動的メッセージを書きます。最後の購入がない場合は、メッセージを中止します。
+- 残り時間のカウントダウンを含むメッセージを誰かにクリックしてもらうように、私のリキッドを書いてください。オファーの有効期限が切れている場合は、メッセージを中止します。
+- ユーザーが帰ってきて、カートに商品が残っているかどうかチェックアウトするように促すメッセージを書くのを手伝ってください。
+- 顧客の国に基づいてメッセージをパーソナライズするには、Liquid を記述します。メッセージに国名を記入したいです。どちらも持っていない場合は、リンクをクリックしてプロファイルを更新することをお勧めします。
+- ユーザのファーストネームでウェルカムメッセージをパーソナライズし、ユーザの性別に基づいて異なるコピーを書き込むにはどうすればよいですか?
+- カスタム属性「CUSTOM_ATTRIBUTE_NAME」とその値に基づいて異なるメッセージを表示するには、Liquid を記述します。送信できるオプションは6種類あります。カスタム属性の値がない場合は、プレースホルダメッセージを送信します。
+
+### 特定のユースケース
+
+- エンゲージメント率とコンバージョン率を高めるために、マーケティングキャンペーンでLiquidがどのように使用されているか、いくつかの例を教えていただけますか?
+- 放棄されたカートのリマインダーやパーソナライズされたプロモーションなど、夏のセールスのテキストメッセージに含まれるLiquidの一般的なユースケースは何ですか?
+
+[フィードバックセッション](https://research.rallyuxr.com/braze/schedule/clxxhw8em0d071ak4b279553s?channel=share)をご予約いただき、興味深いプロンプトや体験がございましたらお知らせください。
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/brazeai/intelligence.md b/_lang/ja/_user_guide/brazeai/intelligence.md
new file mode 100644
index 00000000000..5da778fdbdd
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/intelligence.md
@@ -0,0 +1,79 @@
+---
+nav_title: Intelligence Suite
+article_title: Intelligence Suite
+page_order: 10
+layout: dev_guide
+search_rank: 12
+guide_top_header: "Intelligence Suite"
+guide_top_text: "Braze Intelligence Suiteは、データに基づくインサイトで意思決定のオートメーション化を支援する。配信時間から多変量テストまで、ブランドはこれらのツールと機能を使用して、大規模に最適化されるダイナミックなクロスチャネルのエクスペリエンスを構築できます。<br> <br> インテリジェンス・スイートは、次の 3 つの主要機能で構成されています。インテリジェントタイミング、インテリジェントチャネル、インテリジェントセレクション。"
+description: "Braze Intelligence Suiteは、データに基づくインサイトで意思決定のオートメーション化を支援する。配信時間から多変量テストまで、ブランドはこれらのツールと機能を使用して、大規模に最適化されるダイナミックなクロスチャネルのエクスペリエンスを構築できます。"
+
+Tool:
+  - Dashboard
+
+guide_featured_title: "ツールと機能"
+guide_featured_list:
+- name: インテリジェントタイミング
+  link: /docs/user_guide/brazeai/intelligence/intelligent_timing/
+  image: /assets/img/braze_icons/clock.svg
+- name: インテリジェントチャネル
+  link: /docs/user_guide/brazeai/intelligence/intelligent_channel/
+  image: /assets/img/braze_icons/mail-04.svg
+- name: インテリジェントセレクション
+  link: /docs/user_guide/brazeai/intelligence/intelligent_selection/
+  image: /assets/img/braze_icons/hearts.svg
+
+guide_menu_title: "Additional resources"
+guide_menu_list:
+- name: インテリジェンスFAQ
+  link: /docs/user_guide/brazeai/intelligence/faqs/
+  image: /assets/img/braze_icons/annotation-question.svg
+
+
+---
+
+## ユースケース
+
+Intelligence Suite は、ユーザー履歴やキャンペーン、キャンバスのパフォーマンスを分析し、エンゲージメント、視聴率、コンバージョンを高めるための自動調整を行う強力な機能を提供しています。これらの機能がさまざまな業界にどのようなメリットをもたらすかについては、以下のユースケースを参照されたい。
+
+### e コマース
+
+- **フラッシュセール:**[インテリジェントチャネルフィルター]({{site.baseurl}}/user_guide/brazeai/intelligence/intelligent_channel/)を使用してユーザー履歴を調査し、メールよりプッシュ通知への反応が高いユーザーを特定してから、それぞれのユーザーにプッシュ通知とメールを送信します。オプションとして、好みのチャネルを決定するのに十分なデータを持っていないユーザーのために、特定のチャネルを選択する。
+- **プロモーション用バナー:**[インテリジェントセレクションを]({{site.baseurl}}/user_guide/brazeai/intelligence/intelligent_selection/)使用して、定期キャンペーンのさまざまなプロモーションバナーのパフォーマンスを分析し、最もクリック率の高いバナーを自動的に選択して送信する。
+
+### 旅行
+
+- **パッケージの提供:**インテリジェントセレクションを使用して、繰り返しキャンバスでさまざまな旅行パッケージのオファーをテストし、最もパフォーマンスの高いバリアントにキャンバスのトラフィックを徐々にシフトさせることで、より高い予約率を促進する。
+- **お得な旅行情報：**インテリジェントチャネルフィルターを使用して、パーソナライズされた旅行情報をメールやSMSなど、ユーザーの最もアクティブなチャネルを通じて送信し、ユーザーがメッセージングにエンゲージする可能性を最大限に高める。
+
+### エンターテイメント
+
+- **新コンテンツのプロモーション:**[インテリジェントタイミングを]({{site.baseurl}}/user_guide/brazeai/intelligence/intelligent_timing/)使用して、ユーザーがメッセージングを開封する可能性が最も高いときに、新しい映画、番組、音楽、その他のタイプのコンテンツに関する通知を送信する。
+- **ゲーム内購入:**インテリジェントセレクションを使用して、ゲーム内購入に向けたさまざまなプロモーションメッセージをテストし、最も高いコンバージョン率が得られたものを自動的に選択します。
+
+### クイックサービスレストラン
+
+勤務している SandwichEmperor というファストフード店に、期間限定の新メニューアイテム「Royal Roast」があるとします。Intelligence Suite の 2 つの機能を使用して、キャンバスのパーソナライズされたプロモーションを送信します。
+
+#### インテリジェント・タイミングで通知を送る
+
+インテリジェントタイミングを使用して、当店のアプリと各メッセージングチャネルに対するユーザーの過去のインタラクションを分析し、各ユーザーに Royal Roast を宣伝する最適なタイミングを自動的に選択します。午後にプロモーションを受信するユーザーもいれば、夕方に受信するユーザーもいるでしょう。 
+
+分析するために十分な過去のインタラクションがないユーザーには、フォールバック時間 (ユーザー全体でアプリが使用される最も一般的な時間) を指定します。
+
+![メッセージステップのインテリジェントタイミング配信設定。][1]
+
+#### インテリジェントセレクションを使ってプロモーションを選択する。
+
+実際の販促メッセージについては、インテリジェントセレクションを使用して、Royal Roast 用の 3 種類のメッセージ (プッシュ通知、メール、SMS) をテストします。インテリジェントセレクションは、すべてのプロモーションメッセージのパフォーマンスを1日2回分析し、最もパフォーマンスの高いメッセージを徐々に多く送り、その他のメッセージは少なくしていく。
+
+インテリジェントセレクションは、十分なデータを収集し、最もパフォーマンスの高いメッセージを決定した後、今後送信するメッセージの100%にそのメッセージを使用する。
+
+![インテリジェントセレクションを有効にしたキャンバスのABテストセクション。][3]
+
+#### キャンバスを立ち上げる
+
+インテリジェントタイミングとインテリジェントセレクションの両方を使用して、Royal Roast のプロモーションのタイミングとメッセージングが最適化されるように設定しました。キャンバスを開始して、ユーザーの好みに合わせて送信が変化していく様子を確認できます。
+
+[1]: {% image_buster /assets/img/intelligence_suite1.png %}
+[3]: {% image_buster /assets/img/intelligent_selection_canvas.png %}
diff --git a/_lang/ja/_user_guide/brazeai/intelligence/faqs.md b/_lang/ja/_user_guide/brazeai/intelligence/faqs.md
new file mode 100644
index 00000000000..ff7192cfcdb
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/intelligence/faqs.md
@@ -0,0 +1,103 @@
+---
+nav_title: FAQ
+article_title: インテリジェンスFAQ
+page_order: 191
+description: "この記事では、インテリジェント・チャンネル、インテリジェント・セレクション、インテリジェント・タイミングに関するよくある質問に対する回答を提供します。"
+---
+
+# よくある質問
+
+> この記事では、Intelligence Suite に関するよくある質問にお答えします。
+
+## インテリジェントセレクション
+
+### インテリジェントセレクションと組み合わせた場合、24 時間が経過しないと再適格性が利用できないのはなぜですか?
+
+インテリジェントセレクションキャンペーンは、コントロールバリアントの整合性に影響を与えるため、ウィンドウが短すぎると再適格性を得ることはできません。24 時間のギャップを作成することで、アルゴリズムが統計的に有効なデータセットを使用できるようになります。
+
+通常、再適格性のあるキャンペーンでは、ユーザーは以前に受け取ったのと同じバリアントに再エントリします。インテリジェントセレクションを使用すると、バリアントの分布がこの機能の最適な割り当てアスペクトによってシフトするため、ユーザが同じキャンペーンバリアントを受け取ることが保証されません。インテリジェントセレクションがバリアントのパフォーマンスを再確認する前にユーザーの再エントリが許可された場合、再エントリしたユーザーが原因でデータに歪みが生じる可能性があります。
+
+たとえば、キャンペーンが次のバリアントを使用しているとします。
+
+- バリアントA:20%
+- バリアントB:20%
+- コントロール: 60%
+
+次に、第2ラウンドのバリアント分布は次のようになります。
+
+- バリアントA:15%
+- バリアントB:25%
+- コントロール: 60%
+
+### キャンペーンの初期段階で、等しいセンドを示すインテリジェントセレクションバリアントがあるのはなぜですか?
+
+インテリジェントセレクションは、キャンペーンコンバージョンの現在のステータスに基づいて、送信するバリアントを割り当てます。これは、送信がバリアント間で均等に送られる、トレーニング周期を 1 度経た後の最終的なバリアント割り当てのみを決定します。キャンペーンの初期段階でインテリジェントセレクションが均等に送信されないようにするには、従来のA/B テストに固定バリアントを使用します。
+
+### インテリジェント・セレクションは、明確な勝者を選ばずに最適化を停止するか?
+
+インテリジェントセレクションは、実験を継続してもコンバージョン率の改善は現在の 1% を超えることはないという信頼度が 95% に達すると、最適化を停止します。
+
+### キャンバスまたはキャンペーンでインテリジェントセレクションを有効にできないのはなぜですか(グレー表示)?
+
+インテリジェント選択は、次の場合には使用できません。
+
+- キャンペーンまたはキャンバスに変換イベントを追加していない
+- 単一送信キャンペーンを作成している
+- 24 時間未満のウィンドウで再適格性が有効になっている
+- キャンバスが 1 つのバリアントで構成されており、追加のバリアントやコントロールグループは追加されない
+- キャンバスは、1 つのコントロールグループで構成され、バリアントは追加されません
+
+## インテリジェントタイミング
+
+### インテリジェント・タイミングは、ユーザがいつ変換される可能性が最も高いか、またはユーザが開いたりクリックしたりする可能性が最も高い場合にのみ予測しますか?
+
+インテリジェントタイミングは、ユーザがいつ開いたりクリックしたりするかを予測します。
+
+### 最も人気のあるアプリの時間はどのように決められていますか?
+
+最も人気の高いアプリの時間は、ワークスペースのセッション開始時刻の平均 (現地時刻) によって決まります。このメトリクスは、キャンペーンの時間をプレビューするときにダッシュボードに表示されます(赤色で表示)。
+
+### マシンのインテリジェントタイミングアカウントが開きますか?
+
+はい、マシン開封数はインテリジェントタイミングでフィルタリングされるため、出力には影響しません。
+
+### インテリジェントタイミングを可能な限り確実に機能させるにはどうすればよいですか?
+
+Intelligent Timing は、メッセージを受信した時点で、各ユーザのメッセージエンゲージメントの個々の履歴を使用します。Intelligent Timing を使用する前に、一日の異なる時間帯にユーザーメッセージを送信していることを確認してください。こうすることで、それぞれのユーザーにとっていつが最良の時期かを「サンプリング」することができます。さまざまな時間帯のサンプリングが不十分だと、インテリジェントタイミングはユーザーにとって最適でない送信時刻を選択してしまう可能性があります。 
+
+### すべてのタイムゾーンのすべてのユーザーにインテリジェント・タイミング・キャンペーンを成功裏に配信するには、どの程度前もって開始すればよいですか?
+
+ろう付けは、サモア時間の午前0時(世界初のタイムゾーンの1つ)に最適な時間を計算します。1 日は約 48 時間に及びます。例えば、最適な時刻が午前 12 時 1 分で、オーストラリアに住んでいる人にとって、すでに最適な時刻が過ぎているので、送信するには「遅すぎる」ことになります。こうした理由から、アプリを利用する世界中のすべての人に確実に配信されるようにするには、48 時間前にはスケジュールする必要があります。
+
+### インテリジェント・タイミング・キャンペーンが送信をほとんど表示しないのはなぜですか?
+
+Braze は、良好な推定を行うためにデータポイント数のベースラインデータを必要とします。十分なセッションデータがなかったり、ターゲットとなるユーザーのメールクリック数や開封数がほとんどない場合 (例えば新規ユーザーの場合など)、インテリジェントタイミングは、その曜日のワークスペースの最も人気の高い時間帯をデフォルトとして使用することがあります。ワークスペースに関する十分な情報がない場合は、デフォルトの午後 5 時にフォールバックします。特定の[フォールバック時間]({{site.baseurl}}/user_guide/brazeai/intelligence/intelligent_timing/#fallback-options)を設定することもできます。
+
+### インテリジェント・タイミング・キャンペーンがスケジュールされた日付を過ぎて送信するのはなぜですか?
+
+インテリジェントタイミングキャンペーンでは、A/B テストを活用しているため、スケジュールされた日付を過ぎて送信される場合があります。A/Bテストを使用するキャンペーンは、A/Bテストが終了した後、自動的にWinning Variantを送信することができ、キャンペーン送信の期間が長くなります。デフォルトでは、インテリジェントタイミングキャンペーンは、翌日の残りのユーザーに勝者バリアントを送信するようにスケジュールされますが、この送信日は変更することができます。
+
+インテリジェント・タイミング・キャンペーンがある場合は、A/Bテストが終了するまでさらに時間を置いて、Winning Variantが1つではなく2日間送信するようにスケジュールすることをお勧めします。 
+
+### ブレーズは、セグメントおよびオーディエンスフィルタの適格性基準をいつチェックしますか?
+
+キャンペーンが起動されると、Braze は次の2 つのチェックを実行します。
+
+1. 最初のタイムゾーンが識別されたらすぐに、ユーザーのキュー処理を開始し、
+2. スケジュールされた時刻にユーザーがまだキャンペーンを受け取る資格があるかどうかを確認します。
+
+他のキャンペーンの送信をフィルタリングするキャンペーンを登録する場合は、注意が必要です。たとえば、同じ日に2 つのキャンペーンを異なる時間に送信し、ユーザが最初のキャンペーンを受信した場合に2 番目のキャンペーンしか受信できないフィルタを追加した場合、ユーザは2 番目のキャンペーンを受信しません。これは、キャンペーンが最初に作成され、セグメントが形成されたときに、誰も適格ではなかったためです。
+
+### インテリジェントタイミングキャンペーンでサイレント時間を使用できますか?
+
+キャンペーンまたはキャンバスにインテリジェントタイミングと静かな時間の両方を使用することは、逆効果であるためお勧めしません。サイレント時間はユーザーの行動に関するトップダウンの仮定に基づいているのに対し、インテリジェントタイミングはユーザーのアクティビティに基づいています。
+
+### インテリジェントタイミングとレートリミットを使用できますか?
+
+Braze では、メッセージがいつ配信されるかが保証されないため、インテリジェントタイミングとレート制限の使用はお勧めしません。
+
+### IP ウォーミング中にインテリジェントタイミングを使用できますか?
+
+Braze では、ユーザーが最初に IP ウォーミングを行うときにインテリジェントタイミングを使用することはお勧めしていません。その動作によっては、1 日の容量達成が困難になる場合があるためです。これは、インテリジェントタイミングがキャンペーンセグメントを 2 回評価することが原因です。キャンペーンが最初に作成されたときに 1 回評価した後、ユーザーに送信する前に 2 回目を行い、ユーザーがまだそのセグメントにいるべきかを確認します。 
+
+これにより、セグメントがシフトおよび変更される可能性があり、2回目の評価で一部のユーザーがセグメントから外れてしまうことがよくあります。これらのユーザーは置き換えられないため、最大ユーザー数にどれだけ近づけるかに影響します。
diff --git a/_lang/ja/_user_guide/brazeai/intelligence/intelligent_channel.md b/_lang/ja/_user_guide/brazeai/intelligence/intelligent_channel.md
new file mode 100644
index 00000000000..1f8e9a3163c
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/intelligence/intelligent_channel.md
@@ -0,0 +1,67 @@
+---
+nav_title: インテリジェントチャネルフィルター
+article_title: インテリジェントチャネルフィルター
+page_order: 0
+description: "この記事では、インテリジェント・チャンネル・フィルタについて説明します。このフィルタは、選択したメッセージング・チャンネルが最良のチャンネルである聴衆の部分を選択するフィルタです。この場合、最良の手段は、ユーザの履歴を所与として、関与の可能性が最も高い。"
+search_rank: 11
+---
+
+# [![ブレーズラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/most-engaged-channel){: style="float:right;width:120px;border:0;" class="noimgborder"}インテリジェントチャネルフィルタ
+
+> インテリジェントまたは `Most Engaged` チャネルフィルターは、選択したメッセージングチャネルが「最良」のチャネルであるオーディエンス部分を選択します。 
+
+この場合、最良とは、ユーザの履歴を所与として、関与の可能性が最も高いチャネルを意味する。メール、SMS、ウェブプッシュ、またはモバイルプッシュ(利用可能なモバイルOS またはデバイスを含む)をチャネルとして選択できます。
+
+![][1]{: style="float:right;max-width:40%;margin-left:10px;margin-top:10px;border:0"}
+
+インテリジェントチャネルは、3 つのチャネルそれぞれのエンゲージメント比率をユーザーごとに計算します。これは、過去 6 か月間に受信されたメッセージの数に対する、メッセージのインタラクション間 (開封数またはクリック数) の比率を取得することによって行われます。利用可能なチャネルはそれぞれのエンゲージメント比率に応じてランク付けされ、最も比率が高いチャネルがそのユーザーについて「エンゲージメントが最も高い」ことになります。 
+
+メッセージがユーザに送信されるたびに、またはユーザがメッセージとやり取りするたびに、エンゲージメント比が数秒以内に再計算されます。ユーザは、メッセージとのインタラクションとして1 回のみカウントできます(たとえば、開いているメールをクリックすると、そのメッセージは2 回ではなく1 回だけ関与したものとしてマークされます)。 
+
+インテリジェントチャネルフィルタを有効にするには、メール、ウェブプッシュ、またはモバイルプッシュキャンペーンの作成時に**Target Users** ページで**インテリジェントチャネル** フィルタを選択します。
+
+{% alert important %}
+SMS チャネルのエンゲージメント比率を計算するには、高度な追跡とクリック追跡で \[[SMS リンク短縮]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#overview/)] を有効にします。
+{% endalert %}
+
+## 「データ不足」のオプション
+
+Braze が「最良」チャネルを判定するには、十分なデーターが必要です。つまり、ユーザーは、使用可能な 3 つのチャネルのうち少なくとも 2 つを介して少なくとも 3 つ以上のメッセージを受信している必要があります。メッセージは必ずしも開封されている必要はありません。 
+
+ユーザーがこれらのチャネルにわたって十分なメッセージを受信していない場合、これらのユーザーにはこのフィルターの「データ不足」オプションが適用されます。これにより、3 つの使用可能なメッセージングチャネルのいずれかを使用して、これらのユーザーをターゲットとすることができます。
+
+例えば、プッシュメッセージを好むユーザーにプッシュを受信させ、十分なデータがないユーザーにも同じプッシュメッセージを受信させたいとします。この場合、インテリジェントチャネルフィルタを**Mobile** に設定し、**OR** を使用して、2 番目のインテリジェントチャネルフィルタを**Not Enough Data** に設定します。メールを好むユーザーには、インテリジェントチャネルフィルターがメールに設定されている別のキャンペーンで対応できます。
+
+![][2]
+
+{% alert note %}
+[frequency capping]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#delivery-rules)を無視するキャンペーンとキャンバスのステップは、インテリジェントチャネルでは考慮されず、データ要件に貢献できません。
+{% endalert %}
+
+## "Mobile push"オプション
+
+Mobile push には、Android、iOS、Kindle、およびBraze で利用可能なその他のモバイルデバイスチャンネルが組み込まれています。インテリジェントチャネルを計算する際、Braze は各種類のモバイルデバイスを別々に調べ、その中で最も高いエンゲージメント率を選択して「モバイルプッシュ」カテゴリとし、メールおよび Web プッシュと比較します。 
+
+たとえば、ユーザが複数のモバイルデバイスを持っている場合、そのモバイルエンゲージメント率は、デバイス全体で表示される最高率で表されます。しかし、これは、ユーザーがそのデバイス上で排他的にプッシュ通知を受信することを強制しません。この率は、メールおよび Web プッシュと比較する場合にのみ使用されます。
+
+## 個別チャンネル
+
+Braze で 1 人のユーザー用に単一の最小チャネルを選択さえる代わりに、選択したチャネルでユーザーがメッセージを開封する確率に基づいて、単にユーザーをフィルタリングすることもできます。そのためには、[セグメンテーションフィルタ]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters) でメッセージオープン尤度フィルタを使用できます。
+
+## ベストプラクティスと有効利用戦略
+
+### タイブレーク
+
+受信されるメッセージの数が少ないユーザがいるため、特定のユーザの利用可能なチャネル間でエンゲージメントレートに関係することは珍しくありません(たとえば、単一のユーザが**両方の**メールとモバイルプッシュに対して0.2エンゲージメントレートを持つなど)。このような場合、最新のオープンイベントを持つチャネルを優先順位付け(より高いランク付け)することで、タイが解除されます。
+
+### 到達不能なチャネル
+
+ユーザーがランク付けを決定するのに十分なデータを持っていても、最もエンゲージメントの高いチャネルで到達不能になった場合、そのユーザーは「フォールアウト」し、メッセージを一切受信しなくなります。特定のチャネルで到達不能なユーザは、個別にターゲットを設定する必要があります。
+
+### オーディエンスのサイズ
+
+インテリジェントチャネルを使用すると、オーディエンスの残りの部分よりもメッセージにエンゲージする可能性がはるかに高いごく小数のユーザーを、事前に選択してターゲットとすることができます。この場合、典型的なオーディエンスにおいてはユーザーの大部分をカバーできる可能性は低くなります。むしろ、このフィルターでは、通常のオーディエンスのうち、特定のチャネルでエンゲージメントの実績を持つ 5 ～ 20% のユーザーを見つけられると予想されます。
+
+
+[1]: {% image_buster /assets/img/intelligent_channel_filter.png %} 「インテリジェントチャネルフィルター」
+[2]: {% image_buster /assets/img/intelligent_example.png %}
diff --git a/_lang/ja/_user_guide/brazeai/intelligence/intelligent_selection.md b/_lang/ja/_user_guide/brazeai/intelligence/intelligent_selection.md
new file mode 100644
index 00000000000..526b4d8e077
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/intelligence/intelligent_selection.md
@@ -0,0 +1,55 @@
+---
+nav_title: インテリジェントセレクション
+article_title: インテリジェントセレクション
+page_order: 1
+description: "この記事では、インテリジェントセレクションについて説明します。インテリジェントセレクションは、定期的なキャンペーンまたはキャンバスのパフォーマンスを1 日に2 回分析し、各メッセージバリアントを受信するユーザの割合を自動的に調整する機能です。"
+search_rank: 10
+---
+
+# インテリジェントセレクション {#intelligent-selection}
+
+> インテリジェントセレクションは、定期的なキャンペーンまたはキャンバスのパフォーマンスを1 日に2 回分析し、各メッセージバリアントを受信するユーザの割合を自動的に調整する機能です。 
+
+パフォーマンスが他のユーザーよりも優れていると思われるバリアントは、より多くのユーザーに送信され、パフォーマンスの低いバリアントは、より少ないユーザーをターゲットにします。各調整は、\[統計的アルゴリズム][227]を使用して行われ、ランダムな確率だけでなく実際のパフォーマンスの違いを調整していることを確認します。
+
+![インテリジェント選択を有効にしたキャンペーンのA/B テストセクション。][3]
+
+インテリジェントセレクションは以下のことを行います。
+- パフォーマンスデータを繰り返し確認し、キャンペーンのトラフィックを段階的に勝者バリアントにシフトさせる。
+- 統計的な信頼性を犠牲にすることなく、より多くのユーザーがベストパフォーマンスのバリアントを受け取っていることを確認します。
+- [従来の AB テスト][1]よりも迅速にパフォーマンスの低いバリアントを除外し、パフォーマンスの高いバリアントを特定する。
+- より頻繁にテストを行い、ユーザーに最高のメッセージが表示されることを確信してください。 
+
+インテリジェントセレクションは、複数回送信するようにスケジュールされたキャンペーンに最適です。キャンペーンの調整を開始するには、最初の結果が必要です。したがって、一度だけ送信するキャンペーンはメリットがありません。これらのキャンペーンでは、[A/B test][1] の方が効果的です。
+
+## インテリジェントセレクションをキャンペーンに追加するにはどうすればよいですか?
+
+### キャンペーンインテリジェントセレクション
+インテリジェントセレクションは、Braze キャンペーンコンポーザーの**Target Audiences** ステップの任意のマルチセンドキャンペーンに追加できます。一度だけ送信するキャンペーンは、この機能を利用できません。
+
+### キャンバスインテリジェント選択
+キャンバスにバリアントを追加する際、バリアントのパーセンテージのうち 1 つをクリックします。すると、バリアント分布を編集してインテリジェントセレクションをオンにすることができます。
+
+![それぞれが 50% のバリアント分布に設定された 2 つのバリアントがあり、インテリジェントセレクションを有効化できるキャンバス。][2]
+
+キャンバスに変換イベントをまだ追加していない場合、またはキャンペーンがソロバリアントで構成されている場合、インテリジェント選択は使用できません。
+
+{% alert note %}
+インテリジェントセレクションは、コントロールバリアントの整合性に影響するため、24 時間未満の再適格性チェックが有効なキャンペーンでは使用できません。詳細については、[インテリジェンス FAQ]({{site.baseurl}}/user_guide/brazeai/intelligence/faqs/#why-is-re-eligibility-in-less-than-24-hours-not-available-when-combined-with-intelligent-selection) を参照してください。
+{% endalert %}
+
+## いつまで実行されますか?
+
+キャンペーンおよびキャンバスの場合、インテリジェントセレクションは、"true"バリアントの換算レートに関する十分なエビデンスを収集するまで実行されます。「十分」かどうかは、「後悔」と呼ばれる特別な指標によって決定されます。インテリジェントセレクションは、どのバリアントが最良かを特定するのに十分なデータがあれば、自らオフになるという点で、信頼度に似ていると考えることができます。 
+
+ほとんどの場合、インテリジェントセレクションはいずれかのバリアントを勝者バリアントとして選択します。このバリアントは、今後送信されるオーディエンスの100% に送られます。
+
+{% alert note %}
+インテリジェント・セレクションは、1つの明確な勝者を選ばずに最適化を停止することが可能です。インテリジェント・セレクションは、実験を継続しても現在の割合の1%を超える変換率は向上しないという95%の信頼度がある場合、最適化を停止します。
+{% endalert %}
+
+[1]: {{site.baseurl}}/user_guide/intelligence/multivariate_testing/
+[2]: {% image_buster /assets/img/intelligent_selection.png %}
+[3]: {% image_buster /assets/img/intelligent_selection1.png %}
+\[227]: https://en.wikipedia.org/wiki/Multi-armed_bandit
+
diff --git a/_lang/ja/_user_guide/brazeai/intelligence/intelligent_timing.md b/_lang/ja/_user_guide/brazeai/intelligence/intelligent_timing.md
new file mode 100644
index 00000000000..00c19fd5381
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/intelligence/intelligent_timing.md
@@ -0,0 +1,207 @@
+---
+nav_title: インテリジェントタイミング
+article_title: インテリジェントタイミング
+page_order: 2
+description: "この記事では、インテリジェントタイミング(以前はインテリジェント配信)の概要と、キャンペーンおよびキャンバスでこの機能を活用する方法について説明します。"
+
+---
+
+# [![Braze ラーニングコース] ({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/intelligent-timing) {: style="float:right;width:120px;border:0;" class="noimgborder"}インテリジェントタイミング
+
+> Intelligent Timing を使用して、Braze が、最適な送信時間と呼ばれる、ユーザーがエンゲージ(オープンまたはクリック)する可能性が最も高いと判断したときに、各ユーザーにメッセージを配信します。これにより、ユーザーが希望する時間にメッセージを送信していることを確認しやすくなり、エンゲージメントが高くなる可能性があります。
+
+## ユースケース
+
+- 時間に依存しない定期的なキャンペーンを送信する
+- 複数のタイムゾーンのユーザーによるキャンペーンの自動化
+- 最もエンゲージメントの高いユーザーにメッセージを送る場合(エンゲージメントデータが最も多くなります)
+
+## その仕組み
+
+ブレーズは、ユーザーのアプリとの過去のインタラクションと、各メッセージングチャネルとのインタラクションの統計分析に基づいて、最適な送信時間を計算します。
+
+たとえば、Sam は午前中にメールを定期的に開くことができますが、彼女はあなたのアプリを開き、夕方には通知とやり取りします。つまり、サムは午前中にインテリジェント・タイミングでメールキャンペーンを受け取る一方で、エンゲージする可能性が高い夕方にプッシュ通知でキャンペーンを受け取るということです。
+
+ユーザが最適な送信時間を計算するためのBraze のエンゲージメントデータが不足している場合は、[fallback time](#fallback-time) を指定できます。さらに、マシン開封数は、最適な時刻を計算するための考慮対象から除外されます。
+
+## インテリジェントタイミングの使用
+
+このセクションでは、キャンペーンとキャンバスのインテリジェントタイミングを設定する方法について説明します。
+
+### キャンペーン
+
+キャンペーンにインテリジェントタイミングを使用するには:
+
+1. キャンペーンを作成してメッセージを作成します。
+2. 配送タイプとして**Scheduled Delivery**を選択します。
+3. **Time-Based Scheduling Options**で、**Intelligent Timing**を選択します。
+4. 送信日を選択します。考慮事項については、[キャンペーンニュアンス](#campaign-nuances)を参照してください。
+5. [特定の時間内にメッセージのみを送信するかどうかを決定します](#sending-within-specific-hours)。
+6. [フォールバック時刻](#fallback-time)を指定します。これは、ユーザのプロファイルに最適な時間を計算するのに十分なデータがない場合にメッセージが送信される場合です。
+
+![インテリジェントタイミングを使用したキャンペーンのスケジュール][1]
+
+#### 特定の時間内にメッセージを送信する {#sending-within-specific-hours}
+
+必要に応じて、特定の時間枠内に最適な時間を制限することができます。これは、キャンペーンが特定のイベント、販売、またはプロモーションに関連する場合に役立ちますが、通常は推奨されません。特定の時間内に送信する機能は、Quiet Hours と同様に機能します。インテリジェント・タイミングでは逆効果であるため、これは推奨されません。詳細については、この記事の[制限](#limitations)のセクションを参照してください。
+
+1. インテリジェントタイミングを設定する場合は、**特定時間内のメッセージのみ送信**を選択します。
+2. 配信時間枠の開始時刻と終了時刻を入力します。
+
+![「特定の時間内にのみメッセージを送信する」のチェックボックスを選択し、時間枠をユーザーの現地時間で午前 8 時から午前 12 時の間に設定します。][4]
+
+デリバリーウィンドウが指定されている場合、Brazeはウィンドウ内のエンゲージメントデータのみを調べて、ユーザーの最適な時間を決定します。そのウィンドウ内に十分なエンゲージメントデータがない場合、メッセージは指定された[fallback time](#fallback-time)で送信されます。
+
+#### 配信時間のプレビュー
+
+1 日の各時間にメッセージを受信するユーザ数の見積もりを表示するには、プレビューチャートを使用します(キャンペーンのみ)。
+
+1. ターゲットオーディエンスのステップでセグメントまたはフィルターを追加します。
+2. \[**配信時間のプレビュー**] セクション （\[ターゲットオーディエンス] と \[配信のスケジュール] ステップの両方に表示されます） で、チャネルを選択します。
+3. \[**データの更新**] をクリックします。
+
+![][2]
+
+インテリジェントタイミングまたはキャンペーンオーディエンスに関する設定を変更するたびに、データを再度更新して更新されたチャートを表示します。
+
+このグラフは、青色で最適な時間を計算するのに十分なデータを持っているユーザーと、フォールバック時間を赤色で使用するユーザーを示しています。計算フィルタを使用して、プレビュービュービューを調整し、いずれかのユーザーグループをより詳細に表示します。
+
+#### キャンペーンのニュアンス
+
+インテリジェントタイミングでキャンペーンをスケジューリングする際に注意すべきニュアンスを次に示します。
+
+##### キャンペーンの開始
+
+送信予定日の少なくとも 48 時間前までにキャンペーンを開始します。これは、タイムゾーンが異なるためです。Braze は、世界で最初のタイムゾーンの 1 つであるサモア時間 (UTC+13) の午前 0 時に最適な時刻を計算します。1 日の時間数は世界中で約 48 時間に当たります。つまり、その 48 時間のバッファー内にキャンペーンを開始すると、ユーザーの最適な時刻が現地のタイムゾーンではすでに過ぎているため、メッセージが送信されないことがあります。
+
+{% alert important %}
+キャンペーンが開始され、ユーザの最適な時間が過去1 時間未満の場合、メッセージはただちに消えます。過去1時間以上の時間が最適な場合、メッセージは一切送信されません。
+{% endalert %}
+
+##### セグメントの選択
+
+特定の期間にアクションを実行したオーディエンスをターゲットにする場合は、セグメントフィルタで少なくとも3 日間のウィンドウを使用します。例えば、`First used these apps more than 1 day ago` と `First used these apps less than 3 days ago` の代わりに、1 日と 4 日を使います。
+
+![1 ～4 日前にこれらのアプリを最初に使用したユーザをキャンペーンがターゲットとするターゲットオーディエンスのフィルタ。][3]
+
+これは、タイムゾーンによるものでもあります。3 日未満の期間を選択すると、最適な送信時刻になる前に一部のユーザーがセグメントから外れてしまう可能性があるためです。
+
+[Braze がセグメントとフィルターの適格性基準をチェックするタイミング]({{site.baseurl}}/user_guide/brazeai/intelligence/faqs/#when-does-braze-check-the-eligibility-criteria-for-segment-and-audience-filters)についての詳細。
+
+##### 最適化によるA/Bテスト
+
+A/Bテストの終了後に自動的にWinning Variantを送信するなど、最適化を使用して[A/Bテストを活用している場合、キャンペーンの期間は長くなります。デフォルトでは、インテリジェントタイミングキャンペーンは最初のテストの翌日に残りのユーザーに勝者バリアントを送信しますが、この送信日は変更が可能です。
+
+インテリジェントタイミングとA/B テストの両方を使用している場合は、最初のテストの2 日後に1 日ではなくWinning Variant を送信するようにスケジュールすることをお勧めします。
+
+![最初のテストが開始されてから 2 日後に、テストが終了して勝者バリアントを送信する、ターゲットオーディエンスステップの AB テスト部分。][5]
+
+### キャンバス
+
+このセクションでは、キャンバスでインテリジェントタイミングを使用する方法について説明します。手順は、使用しているキャンバスワークフローによって若干異なります。
+
+{% alert important %}
+2023 年 2 月 28 日以降、元のエディターを使用したキャンバスの作成や複製はできなくなりました。このセクションは、インテリジェントタイミングが元のエディターでどのように機能するかを理解するための参考資料として利用できます。<br><br>Braze では、従来のキャンバスエクスペリエンスを使用しているお客様に、キャンバスフローへの移行をお勧めしています。これは、キャンバスの構築と管理をより良く行う目的で改良された編集エクスペリエンスです。「[キャンバスからキャンバスフローへの複製]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases/)」を参照してください。
+{% endalert %}
+
+{% tabs %}
+{% tab キャンバスフロー %}
+
+キャンバスフローでは、インテリジェントタイミングがメッセージステップで設定されます。キャンバスでインテリジェントタイミングを使用するには:
+
+1. [メッセージステップ]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/)をキャンバスに追加します。
+2. \[**配信設定**] に移動します。
+3. \[**インテリジェントタイミングを使用**] を選択します。
+4. [フォールバック時刻](#fallback-time)を指定します。
+
+このステップに入ったユーザーは、その時刻が経過していない場合、エントリの日の最適な時刻にメッセージを受け取ります。ユーザがメッセージステップを入力した日に最適な時間(ローカル時間)が過ぎた場合、最適な時間に翌日に送信されることに注意してください。複数のチャネルをターゲットとするメッセージステップは、異なるチャネルに対して異なる時間にメッセージを送信するか、または送信しようとすることがあります。メッセージステップの最初のメッセージを送信しようとすると、すべてのユーザーが自動的に進められます。
+
+#### 遅延ステップとインテリジェントタイミング
+
+[Delay step]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/delay_step/)後のIntelligent Timing を使用する場合、遅延の計算方法によって納期が異なる場合があります。これは、"days"および"calendar days"の計算方法に違いがあるため、遅延が**デュレーション**の後に設定されている場合にのみ適用されます。
+
+- **日:**1 日は 24 時間で、ユーザーが遅延ステップに入ったときから計算されます。
+- **暦日:**1 日とは、ユーザーが遅延ステップに入ってから、そのタイムゾーンの午前 0 時までの期間です。つまり、1 日のカレンダーは、数分の短さにすることができます。
+
+インテリジェントタイミングを使用する場合は、24 時間制ではなく、遅延にカレンダー日を使用することをお勧めします。これは、カレンダーの日付を指定すると、メッセージは遅延の最終日に最適な時刻に送信されるためです。24時間制では、ユーザーの最適な時間がステップに入る前にある可能性があります。これは、ユーザーの遅延に余分な日が追加されることを意味します。
+
+例えば、ルカの最適な時刻が午後 2 時だとします。彼は 3 月 1 日午後 2 時 1 分に遅延ステップに入り、遅延は 2 日に設定されています。
+
+- 1 日目は 3 月 2 日午後 2 時 1 分まで
+- 2 日目は 3 月 3 日午後 2 時 1 分まで
+
+ただし、Intelligent Timing は、すでに経過した午後2 時に配信するように設定されています。したがって、ルカがメッセージを受け取るのは翌日の 3 月 4 日午後 2 時になります。
+
+![ユーザーの最適な時間が午後2 時であるが、午後2:01 に遅延ステップに入り、遅延が2 日に設定されている場合の、日とカレンダーの差を示すグラフィック。「日」は、ユーザーが最適な時刻の後にステップに入ったため 3 日後にメッセージを配信するのに対し、「暦日」は 2 日後、遅延の最終日にメッセージを配信します。]({% image_buster /assets/img/intelligent_timing_daysvcalendardays.png %}){: style="border:none;"}
+
+{% endtab %}
+{% tab 元のCanvas ワークフロー %}
+
+元のキャンバスワークフローでは、インテリジェントタイミングはフルステップの遅延セクションで設定されています。キャンバスでインテリジェントタイミングを使用するには:
+
+1. キャンバスにステップを追加します。
+2. ステップの \[**遅延**] を開きます。
+3. \[**スケジュール設定**] を選択します。
+4. *after*、*in*、*on the next* を使用して遅延を設定します。
+   - *after* を選択した場合は、日または週単位で遅延を設定します。遅延は、カレンダー日を使用して自動的に計算されます。つまり、メッセージは、ユーザの最適な時刻に遅延の最終日に送信されます。インテリジェントタイミングは、1 日より短い遅延では使用できません。
+5. \[**インテリジェントタイミングを使用**] を選択します。
+6. [フォールバック時刻](#fallback-time)を指定します。
+
+{% endtab %}
+{% endtabs %}
+
+#### キャンバスの起動
+
+キャンペーンとは異なり、キャンバスを送信日の 48 時間前に立ち上げる必要はありません。これは、インテリジェントタイミングがキャンバスレベルではなくステップレベルに設定されているためです。代わりに、キャンバスに入ってからインテリジェントタイミングが使用されるステップを受信するまでに、少なくとも48 時間の遅延があることをお勧めします。
+
+### 立ち下がり時間 {#fallback-time}
+
+メッセージが、最適な送信時間を計算するためのBraze のエンゲージメントデータが十分でないユーザーに送信するためのフォールバック時間を選択する必要があります。2 つのオプションがあります。
+
+- 全ユーザーの中で最も人気のあるアプリ使用時間
+- 特定のカスタムフォールバック時刻 (ユーザーのローカルタイムゾーン)
+
+#### 最も人気の高いアプリの時間
+
+最も人気の高いアプリの時間は、ワークスペースのセッション開始時刻の平均 (現地時刻) によって決まります。この時間は、[プレビューチャート](#preview-delivery-times)(キャンペーンのみ)に赤色で表示されます。
+
+キャンペーンでは、[配信ウィンドウ](#sending-within-specific-hours)を指定し、アプリを使用する最も一般的な時間がそのウィンドウの外側にある場合、メッセージは配信ウィンドウの端に最も近い位置に送信されます。たとえば、配信ウィンドウが午後1時から午後8時で、最も人気のあるアプリ時間が午後10時である場合、メッセージは午後8時に送信されます。
+
+**セッションデータの不足**<br>
+まれに、アプリが最もよく使用される時間を計算するのに十分なセッションデータがアプリにない場合 (データがない全く新しいアプリの場合)、メッセージはユーザーのローカルタイムゾーンで午後 5 時に送信されます。ユーザーの現地時間が不明な場合は、会社のタイムゾーンで午後5時に送信されます。
+
+限られたデータが利用可能な場合、ユーザのライフサイクルの初期にインテリジェント・タイミングを使用することの制限に注意することが重要です。記録されたセッションがほとんどないユーザーであっても、その行動についての洞察を提供することができるため、価値はあります。ただし、Braze が最適な送信時刻をより効果的に計算できるのは、ユーザーのライフサイクルの後の方です。
+
+#### カスタムフォールバック時間
+
+カスタムフォールバック時間を使用して、メッセージを送信する別の時間を選択します。最も人気のあるアプリ時刻と同様に、メッセージはユーザのローカルタイムゾーンのフォールバック時刻に送信されます。ユーザーのローカルタイムゾーンが不明な場合は、会社のタイムゾーンで送信されます。
+
+カスタムフォールバック時間を指定したキャンペーンの場合、送信日から24時間以内にキャンペーンを起動すると、最適な時間が既に経過したユーザは、カスタムフォールバック時間にキャンペーンを受信します。カスタムフォールバック時間がすでにタイムゾーンで経過している場合、メッセージはすぐに送信されます。
+
+## 制限事項
+
+- アプリ内メッセージ、コンテンツカード、ウェブフックはすぐに配信され、最適な時間は与えられません。
+- インテリジェントタイミングは、アクションベースまたはAPI トリガキャンペーンでは使用できません。
+- インテリジェントタイミングは、次のシナリオでは使用しないでください。
+    - **サイレント時間:**Quiet Hours とIntelligent Timing の両方を使用すると逆効果になります。Quiet Hours は、夜中に誰かにメッセージを送信しないなど、ユーザーの動作に関するトップダウンの仮定に基づいていますが、Intelligent Timing はユーザーのアクティビティに基づいています。サムは午前 3 時にアプリの通知をよくチェックしているのかもしれません。批判はやめましょう。
+    - **レート制限:**レート制限とインテリジェントタイミングの両方が使用されている場合、メッセージがいつ配信されるかは保証されません。インテリジェントタイミングを使用した毎日の繰り返しキャンペーンでは、メッセージ送信の上限の合計が正確にサポートされません。
+    - **IP ウォームアップキャンペーン:**インテリジェントタイミングビヘイビアの中には、最初にIP をウォームアップするときに必要となる毎日のボリュームにヒットする際に問題が発生するものがあります。これは、Intelligent Timing が、キャンペーンまたはキャンバスが最初に作成されたときにセグメントを2 回評価し、ユーザに送信してそのセグメントにまだ存在する必要があることを確認する前に再度評価するためです。これにより、セグメントがシフトおよび変更される可能性があり、2回目の評価で一部のユーザーがセグメントから外れてしまうことがよくあります。これらのユーザーは置き換えられず、最大ユーザー上限にどれだけ近づくことが可能かに影響します。
+
+## トラブルシューティング
+
+### 最適な時間で少数のユーザーを表示するプレビューチャート
+
+ろう付けは、良好な推定を行うために、ある程度の係合データを必要とする。セッション・データが不足している場合、またはターゲット・ユーザーにクリックやオープン(新規ユーザーなど)がほとんどない場合、Brazeはデフォルトでフォールバック時間になります。設定によっては、これが最も一般的なアプリ時間またはカスタムフォールバック時間になる場合があります。
+
+### 送信予定日を過ぎてからの送信
+
+最適化 を使用して[A/B テストを利用している場合、インテリジェントタイミングキャンペーンがスケジュールされた日付を過ぎて送信している可能性があります。A/Bテスト最適化を使用するキャンペーンは、最初のテストが終了した後、自動的にWinning Variantを送信し、キャンペーンの期間を延長できます。デフォルトでは、最適化を使用したキャンペーンは最初のテストの翌日に残りのユーザーに勝者バリアントを送信しますが、この送信日は変更することができます。
+
+インテリジェント・タイミングを使用する場合は、A/Bテストが終了するまでさらに時間を残し、最初のテストから1日ではなく2日間、Winning Variantを送信するようにスケジュールすることをお勧めします。
+
+
+[1]: {% image_buster /assets/img/intelligent_timing_1.png %}
+[2]: {% image_buster /assets/img/intel-timing-preview.png %}
+[3]: {% image_buster /assets/img/intelligent_timing.png %}
+[4]: {% image_buster /assets/img/intelligent_timing_hours.png %}
+[5]: {% image_buster /assets/img/intelligent_timing_ab_test_duration.png %}
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite.md b/_lang/ja/_user_guide/brazeai/predictive_suite.md
new file mode 100644
index 00000000000..8eca674d4b5
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite.md
@@ -0,0 +1,25 @@
+---
+nav_title: Predictive Suite
+article_title: Predictive Suite
+page_order: 5
+layout: dev_guide
+search_rank: 3
+guide_top_header: "Predictive Suite"
+guide_top_text: "Braze Predictive Suite では、追加の開発を必要とせずに機械学習ツールを手に入れることができます。解約予測と予測イベント (旧称「予測購入」) は、Braze プラットフォーム内でデータをシームレスに活用して行動に移すために数分で作成できるカスタマイズ可能なオンデマンド予測モデルです。<br><br>これらの機能の詳細については、以下の記事をご覧いただきたい。"
+description: "このランディング・ページは、Brazeのこの予測をすべて伝える場所である！Braze Predictive Suite は、Braze キャンペーンとキャンバス内での解約予測とイベント予測のソリューションを提供します。"
+
+guide_featured_title: "特徴"
+guide_featured_list:
+- name: 解約予測
+  link: /docs/user_guide/brazeai/predictive_suite/predictive_churn/
+  image: /assets/img/braze_icons/lightbulb-02.svg
+- name: 予測イベント
+  link: /docs/user_guide/brazeai/predictive_suite/predictive_events/
+  image: /assets/img/braze_icons/stars-01.svg
+---
+
+{% alert tip %}
+予測を生成し、その予測に基づいてユーザー群をターゲティングしても、データポイントを消費することはない。
+{% endalert %}
+
+<br><br>
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn.md
new file mode 100644
index 00000000000..b6961d44975
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn.md
@@ -0,0 +1,53 @@
+---
+nav_title: 解約予測
+article_title: 解約予測
+page_order: 6.4
+layout: dev_guide
+alias: /predictive_churn/
+search_rank: 2
+guide_top_header: "解約予測"
+guide_top_text: "顧客解約は、顧客回転率や顧客喪失とも呼ばれ、成長する企業にとって最も重要な指標の 1 つです。解約を最小限に抑え、カスタマーリテンションを最大限に引き出すためには、解約に対処する適切なツールが不可欠です。Braze には、このような潜在的なユーザー離脱に先手を打つため、将来のユーザー離脱を最小限に抑えるプロアクティブアプローチを提供する「解約予測」という機能が用意されています。"
+description: "このランディングページでは解約予測について説明します。これは、貴社にとって解約予測の意味と、解約予測を防止したいユーザーを定義するためのツールです。"
+
+guide_featured_title: "トピック"
+guide_featured_list:
+- name: 解約予測を立てる
+  link: /docs/user_guide/brazeai/predictive_suite/predictive_churn/creating_a_churn_prediction/
+  image: /assets/img/braze_icons/settings-01.svg
+- name: 予測分析
+  link: /docs/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/
+  image: /assets/img/braze_icons/bar-chart-01.svg
+- name: ユーザーへのメッセージング
+  link: /docs/user_guide/brazeai/predictive_suite/predictive_churn/messaging_users/
+  image: /assets/img/braze_icons/arrow-narrow-right.svg
+- name: トラブルシューティング
+  link: /docs/user_guide/brazeai/predictive_suite/predictive_churn/prediction_faq/
+  image: /assets/img/braze_icons/annotation-question.svg
+
+---
+
+## 概要
+
+![解約の概要。過去のデータによるトレーニングで過去の予測対象ユーザーを含む。これは、解約リスクスコアを用いて現在の予測オーディエンスを測定することにより、将来の解約リスクを予測するのに役立ちます。][1]
+
+> 解約予測では、ビジネスにとって解約が意味するもの ([解約の定義]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/creating_a_churn_prediction/#step-2-define-churn)) と、解約を防ぎたいユーザー ([予測対象ユーザー]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/creating_a_churn_prediction/#step-3-filter-your-prediction-audience)) を定義することができます。予測を作成すると、Brazeは[勾配ブースティング決定木を](https://en.wikipedia.org/wiki/Gradient_boosting)使用して機械学習モデルをトレーニングし、あなたの定義に従って解約したユーザーとしなかった過去のユーザーの活動パターンから学習して、解約リスクのあるユーザーを識別する。
+
+予測モデルが構築されると、定義した内容に従って解約の可能性を示す 0 ～ 100 の間の[解約リスクスコア]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/#churn_score)が予測対象ユーザーに割り当てられます。スコアが高いほど、ユーザーが解約する可能性が高くなる。 
+
+予測対象ユーザーのリスクスコアの更新は、[選択した頻度]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/creating_a_churn_prediction/#step-4-choose-the-update-frequency-for-churn-predictions)で行うことができます。こうすることで、実際に解約される前に、解約リスクのあるユーザーにリーチし、解約を未然に防ぐことができます。最大3つのアクティブユーザー予測を使用することで、Predictive Churnを活用して個々のモデルをカスタマイズし、最も価値があると思われるユーザーの特定のセグメンテーションにおける解約防止を支援することができる。
+
+## 解約予測にアクセスする
+
+\[**予測**] ページは \[**分析**] セクションにあります。フルアクセスが必要な場合、アカウントマネージャーにお問い合わせください。
+
+{% alert note %}
+[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、**「** **エンゲージメント**」の下に**「予測」が**ある。
+{% endalert %}
+
+この機能を購入する前に、プレビュー・モードで利用できる。これにより、合成データを使った解約予測のデモを見ることができ、ユーザーデータに基づいて解約予測モデルを一度に1つ作成することができる。このプレビューでは、解約リスクに応じてユーザーをメッセージングのターゲットにすることはできず、作成後に定期的に更新されることもありません。
+
+プレビューを使えば、1つの予測を編集して再構築したり、アーカイブして他の予測を作成し、異なる[定義の]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/creating_a_churn_prediction/#step-2-define-churn) [予測品質を]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/)テストすることもできる。
+
+<br><br>
+
+[1]: {% image_buster /assets/img/churn/churn_overview.png %}
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/creating_a_churn_prediction.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/creating_a_churn_prediction.md
new file mode 100644
index 00000000000..7f4b057e91f
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/creating_a_churn_prediction.md
@@ -0,0 +1,113 @@
+---
+nav_title: チャーン予測の作成
+article_title: チャーン予測の作成
+description: "この記事では、Braze ダッシュボード内でチャーン予測を作成する方法について説明します。"
+page_order: 1
+
+---
+
+# チャーン予測の作成
+
+> Braze ダッシュボード内でチャーン予測を作成する方法について説明します。
+
+## ステップ 1:新しい予測を作成する
+
+ブレーズで、**Analytics**> **Predictive Churn** に移動します。
+
+{% alert note %}
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、**Predictions**は**Engagement**にあります。
+{% endalert %}
+
+予測は、訓練された機械学習モデルの1つのインスタンスであり、それが使用するすべてのパラメータとデータです。このページには、現在アクティブな予測のリストと、それらに関する基本情報が表示されます。ここでは、名前の変更、アーカイブ、および新しい予測の作成ができます。アーカイブされた予測は非アクティブであり、ユーザースコアは更新されません。 
+
+新しい予測を作成するには、**予測の作成**を選択し、新しい**Churn Prediction**を選択します。
+
+{% alert note %}
+同時にアクティブなチャーン予測は5 つに制限されています。Predictive Churn を購入する前に、制限は1 つのアクティブなプレビューチャーン予測です。プレビューチャーン予測では、スコアが定期的に更新されないか、予測の出力に基づいてターゲットユーザーがターゲットになることが許可されません。詳細については、アカウントマネージャにお問い合わせください。
+{% endalert %}
+
+**Basics** ページで、新しい予測に一意の名前を付けます。また、オプションの説明を指定して、この特定の予測に関するメモを取ることもできます。
+
+次の手順に進むには、**Forward**をクリックします。必要に応じて、**Build Now**をクリックしてすべてのデフォルト設定を使用し、作成の最後のステップにスキップすることができます。ビルドプロセスを開始する前に、設定を確認することができます。上の進行状況トラッカーで選択すると、後で任意のステップに戻ることができます。
+
+## ステップ 2:チャーンの定義
+
+**Churn Definition** パネルで、提供されたフィルタを使用して、ビジネスのユーザーチャーンを定義する方法を指定します。言い換えれば、ユーザーが解雇されたとみなすには、どのような時間枠で何をしなければならないのか?
+
+覚えておいてほしいのは、どのようなビヘイビアがチャーンの前にあるのかを説明する必要がないということです。ユーザーがチャーンされたユーザーを作るのは、どのビヘイビアだけなのかということです。これは、ユーザーが一度やる(`do`)か、チャーニングを構成する(`do not`)をやめるという意味で考えてみてください。たとえば、7 日以内にアプリを開いていないユーザーを解約するとします。登録解除、アカウントの無効化などのカスタムイベントをアンインストールしたり、ユーザを解凍させたりすることを検討してください。 
+
+#### チャーンウインドウ
+
+チャーン・ウィンドウは、ユーザーがチャーンを構成するために指定された動作を実行する時間枠です。60日まで設定できます。このウィンドウは、予測をトレーニングするために履歴データを照会するために使用されます。さらに、予測が作成され、ユーザーがスコアを受け取った後、_Churn Risk Score_ は、チャーンウィンドウで指定された日数内にユーザーがチャーンする可能性を示します。 
+
+ここでは、過去7 日間のセッションの失効に基づく単純な定義の例を示します。
+
+![ユーザーが7日以内にセッションを開始しない場合、そのユーザーがチャーンしたと見なされるチャーン定義][1]
+
+この場合、`do not` および`start a session` を選択します。他のフィルタを`AND` および`OR` と組み合わせて、必要な定義を作成することができます。考慮すべきいくつかの潜在的なチャーンの定義に関心があるか?次のセクションでは、[サンプルチャーン定義](#sample-definitions) のインスピレーションをいくつか示します。
+
+{% alert note %}
+`do` の場合、アクティブなユーザーは、チャーンされる前にこの行に対して指定したアクションを実行しなかったと想定します。アクションを実行すると、それらは撹拌されます。<br><br>`do not` の場合、アクティブユーザは前日にそのアクションを実行し、その後停止したユーザであると見なされます。
+{% endalert %}
+
+定義の下には、利用可能なユーザー数(過去にチャーンしたユーザーと定義に従ってチャーンしなかったユーザー) の見積もりが表示されます。必要な最小値も表示されます。ろう付けでは、ヒストリカル・データで利用可能なユーザーの数がこの最小限でなければならないため、予測には学習に必要な十分なデータが含まれています。
+
+## ステップ 3:予測オーディエンスをフィルタリングする
+
+予測オーディエンスは、解約リスクを予測するユーザーのグループです。デフォルトでは、これは**All Users** に設定されます。これは、この予測により、アクティブなすべてのユーザーのチャーン・リスク・スコアが作成されることを意味します。通常、いくつかの基準で混乱を防ぎたいユーザーのグループを絞り込んでフィルタリングすると、モデルのパフォーマンスが向上する可能性があります。ここでは、保持して定義したい特定のユーザーについて考えてみましょう。たとえば、1 か月以上前にアプリを初めて使用したユーザー、または購入したことのあるユーザーを保持することができます。
+
+{% alert note %}
+予測対象者は1億 人を超えることはできません。
+{% endalert %}
+
+予測ウィンドウが14 日以内の場合、"Last..." like "Last Used App" and "Last Made Purchase" **で始まるフィルタの時間枠は、チャーン定義でChurn ウィンドウに指定された**を超えることはできません。たとえば、チャーン定義のウィンドウが14日の場合、"Last..."フィルタの時間枠は14日を超えることはできません。
+
+#### フルフィルターモード
+
+新しい予測をすぐに構築するために、ブレーズセグメンテーションフィルタのサブセットのみがサポートされています。Full Filter Mode(フルフィルタモード)では、すべてのろう付けフィルターを使用できますが、予測を作成するには1 つのチャーンウィンドウが必要です。たとえば、チャーンウィンドウが15 日に設定されている場合、フルフィルタモードでのみサポートされるフィルタを使用すると、ユーザデータの収集と予測の作成に15 日かかります。 また、フルフィルタモードでは、視聴者のサイズに関する一部の見積もりが利用できなくなります。
+
+予測オーディエンス定義のサンプルリストについては、[ サンプルチャーン定義](#sample-definitions) の次のセクションでサンプル定義を確認してください。
+
+![][3]
+
+前のページと同様に、下部のパネルには、チャーン定義と予測オーディエンス定義に起因するヒストリックユーザーの推定数が表示されます。これらの見積もりは、予測を作成するために表示される最小要件を満たす必要があります。
+
+## ステップ 4:チャーン予測の更新頻度の選択
+
+このページを完了したときに作成された機械学習モデルは、ここで選択したスケジュールで使用され、新しいチャーン・リスク・スコアが生成されます。役立つと思われる**更新の最大頻度**を選択します。たとえば、ユーザーの解約を防ぐために週間プロモーションを送信する場合は、選択した日時に更新頻度を**Weekly** に設定します。 
+
+![予測更新スケジュールが毎日午後5時に設定されます。][2]
+
+{% alert note %}
+プレビューとデモの予測は、ユーザーの解約リスクを更新しません。さらに、予測の毎日の更新には、Predictive Churn による週次または月次の更新を超える追加購入が必要です。この機能を購入するには、アカウントマネージャにお問い合わせください。
+{% endalert %}
+
+## ステップ 5: 予測を構築する
+
+指定した詳細が正しいことを確認し、**Build Prediction** を選択します。また、**Save As Draft**を選択してこのページに戻り、後でモデルをビルドすることで、ドラフトフォームに変更を保存することもできます。**Build Prediction**をクリックすると、モデルを生成するプロセスが開始されます。データ量によっては、30 分から数時間かかる場合があります。この予測では、モデル構築プロセスの間、トレーニングが進行中であることを説明するページが表示されます。
+
+完了すると、ページが自動的にAnalytics ビューに切り替わり、予測と結果の準備ができたことを知らせる電子メールが送信されます。エラーが発生した場合、ページは編集モードに戻り、何が間違っていたかが説明されます。
+
+予測は再構築され("retrained")、**2 週間ごとに自動的に更新されます**。これにより、最新の利用可能なデータが更新されます。これは、ユーザーの_Churn Risk Scores_(予測の出力)が生成される場合とは別のプロセスであることに注意してください。後者は、手順4で選択した更新頻度によって決まります。
+
+## サンプルチャーンと予測オーディエンスの定義 {#sample-definitions}
+
+**チャーンの定義例**<br>
+- "7日以内に、カスタムイベント「Subscription Cancellation」&quotを実行します。<br>
+- "30日以内に、カスタムイベント「Trial Expired」&quotを実行します。<br>
+- "1 日以内にアンインストールを行います。"<br>
+- " 14日以内に購入を行わない。"<br>
+
+説明したチャーンの定義には、対応する予測オーディエンスの定義があるかもしれません。<br>
+- **2週間以上前にサブスクリプションを開始または2週間未満前にサブスクリプションを開始**<br>この場合、2 つの予測を作成し、新しいサブスクライバを長期サブスクライバとは異なる方法でメッセージを送信することができます。これを" First Made Purchase 30 日以上前に定義することもできます。<br>
+- **アンインストーラー**<br>過去に何かを購入したことがあるか、最近アプリを使用したことがある顧客に焦点を当てるかもしれません。<br>
+- **解約の定義として購入しないリスクのある者**<br>最近、あなたのアプリをブラウズしたり検索したり、エンゲージしている顧客に焦点を当てることができます。おそらく、適切な割引介入は、このより関与したグループが混乱することを防ぐだろう。
+
+## アーカイブ済み予測
+
+アーカイブされた予測では、ユーザースコアの更新が停止します。アーカイブされていないアーカイブされた予測は、事前に設定されたスケジュールでユーザーのスコアを更新し続けます。アーカイブされた予測は削除されず、リストに残ります。
+
+[1]: {% image_buster /assets/img/churn/churn1.png %}
+[2]: {% image_buster /assets/img/churn/churn2.png %}
+[3]: {% image_buster /assets/img/churn/churn5.png %}
+
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/messaging_users.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/messaging_users.md
new file mode 100644
index 00000000000..f2fdfe7a025
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/messaging_users.md
@@ -0,0 +1,35 @@
+---
+nav_title: ユーザーへのメッセージング
+article_title: 解約予測ユーザーをターゲットにする
+description: "この参考記事では、フィルターの導入や戦略的考察など、解約予測を行った後に考えられる次のステップについて取り上げている。"
+page_order: 3
+
+---
+
+# ユーザーへのメッセージング {#what-do-next}
+
+{% alert note %}
+プレビューおよびデモ予測ではユーザーをメッセージングの対象にすることはできず、\[**セグメントを作成**] ボタンと \[**キャンペーンを作成**] ボタンは無効になります。この機能を購入するには、アカウントマネージャーに連絡する。
+{% endalert %}
+
+## フィルターの実装{#filters}
+
+ターゲットにしたい_解約リスクスコア_またはカテゴリーの範囲が決まったら、**セグメントの作成**または**キャンペーンの作成**ボタンを使って、スライダーで選択した_解約リスクスコア_またはカテゴリーを持つユーザーをフィルターする新しいセグメントまたはキャンペーンを作成することができる。
+
+![オーディエンス定義時に利用可能な解約フィルターには、購入可能性カテゴリーと購入可能性スコアがある。][5]
+
+キャンペーンやセグメンテーションでフィルターを使い、その閾値に従ってユーザーをターゲットにすることもできる。キャンペーン、キャンバス、セグメンテーションでは、Brazeの他のフィルターと同じように、「チャーンスコア」や「チャーンカテゴリー」でユーザーをフィルターすることができる。
+
+## 戦略的考察
+
+さて、アクティブユーザーを維持し、エンゲージメントを維持するために、何らかのインセンティブや新しいメッセージングシリーズが必要と思われる、解約リスクのあるユーザーグループを識別子し、選択したところで、どうするか？Currentsのパッシブ・ユーザーシリーズに積極的に追加するだけなのか？それとも、キャンバスやキャンペーンの新しいシリーズを作り上げるのか？ 
+
+**いくつかアイデアを挙げてみよう：**
+
+- 予測されるミディアムからハイリスクのユーザーを対象に、特別割引、無料商品（物理的なギフトまたはデジタルクレジット）、限定コンテンツ、または新しいエクスペリエンス（製品、アプリ機能、レベル）への早期アクセスを提供する。<br><br>
+- これらのユーザーを1週間毎日キャンバスに送り込み、彼らが最も好むチャネルでメッセージを配信したり、3日間集中的にブラストを行い、メールからFacebookまであらゆるチャネルで顧客にリーチしたり、実在の人物からメッセージを送り、ブランドのフィードバックを求めたり、プロフェッショナルなヒントを提供したりする。<br><br>
+- もしかしたら、あなたのブランドの価値や、その顧客が以前あなたのブランドから価値を見出した方法を、あらためて伝える新しい楽しい方法が必要なのかもしれない。これは、ペルソナに特化した週刊ニュースレターのようなものであったり、あなたのブランドに関する実際のユーザーからのリアルストーリーのシリーズであったり、その他のコンテンツマーケティングの遊びのようなものであったりする。
+
+リスクのあるユーザーのレベルに応じて、メッセージングを変えることができることを覚えておいてほしい！つまり、リスクの高い顧客は中程度の顧客よりも高い割引を受けられるが、リスクの低い顧客は新しい種類のメッセージングやコンテンツを得られるだけで、それ以上のインセンティブは得られない。また、これらのセグメンテーションに他のフィルターを重ねることで、誰がどのようなオファーやメッセージを受け取るかをさらに限定することもできる。
+
+[5]: {% image_buster /assets/img_archive/predictive_churn_filters.png %}
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics.md
new file mode 100644
index 00000000000..5ef0e55405c
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics.md
@@ -0,0 +1,78 @@
+---
+nav_title: 予測分析
+article_title: 予測分析
+description: "この記事では、解約予測分析ページに含まれるさまざまなコンポーネントと、インサイトに満ちた積極的な意思決定を行うためにそれらをどのように使用できるかを説明します。"
+page_order: 2
+
+---
+
+# 予測アナリティクス
+
+> 予測の構築とトレーニングが完了したら、**Prediction Analytics** ページにアクセスできます。このページでは、_Churn Risk Score_ またはカテゴリに基づいて、どのユーザーをターゲットにするかを決定するのに役立ちます。 
+
+予測が完了し、このページが入力されるとすぐに、単に[filters]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/messaging_users/#filters) をセグメントまたはキャンペーンで使用して、モデルの出力の使用を開始できます。しかし、誰をターゲットにするのか、なぜターゲットにするのかを決めるのに役立ちたいのであれば、このページはモデルの歴史的な正確さと自分自身のビジネス目標に基づいて役立ちます。 
+
+**分析のコンポーネント**<br>
+- [解約スコアとカテゴリ](#churn_score)<br>
+- [予測品質](#prediction_quality)<br>
+- [推定結果](#estimated_results)<br>
+- [解約相関表](#correlation_table)
+
+## 概要
+
+予測オーディエンス全体のスコアの分布は、グラフの一番上に表示されます。グラフでは、カテゴリ別またはスコア別に表示できます。右側にあるビンのユーザーは、スコアが高く、チャーンする可能性が高くなります。左側にあるビンには、解約の可能性が低いユーザーが入っています。グラフの下にあるスライダを使用すると、ユーザーの範囲を選択し、選択した範囲の_Churn Risk Score_ またはカテゴリのユーザーをターゲットにする場合の結果を見積もることができます。
+
+![][4]{: style="max-width:90%"}
+
+スライダーを動かすと、下側のパネルの左半分のバーに、予測オーディエンス全体からターゲットになるユーザの数が表示されます。
+
+## 解約スコアとカテゴリ {#churn_score}
+
+予測対象ユーザーには、0 ～ 100 の間で_解約リスクスコア_が割り当てられます。スコアが高ければ高いほど、解約の可能性は高くなります。 
+- スコアが 0 ～ 50 のユーザーは、_低リスク_カテゴリに分類されます。 
+- スコアが 50 ～ 75、75 ～ 100 のユーザーは、それぞれ_中リスク_と_高リスク_のカテゴリに分類されます。 
+
+スコアと対応するカテゴリは、モデル作成ページで選択したスケジュールに従って更新されます。同じサイズのバケット 20 個のそれぞれに解約スコアがあるユーザーの数が、ページ上部のチャートに表示されます。これは、この予測に基づいて、母集団全体でどのような解約リスクがあるかを判断するのに役立ちます。
+
+## ユーザーをターゲットにして解約を減らす
+
+### 予測品質 {#prediction_quality}
+
+モデルの精度を測定するために、_Prediction Quality_ メトリクスは、この特定の機械学習モデルが履歴データでテストされたときにどの程度有効であるかを示します。メトリックの詳細については、[予測品質]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/)を参照してください。
+
+_ Prediction Quality_ のさまざまな範囲にお勧めします。
+
+| 予測品質範囲(%) | 推奨 |
+| ---------------------- | -------------- |
+| 60 - 100 | 非常に良い。トップクラスの精度。オーディエンスの定義を変更しても新たなメリットが得られる可能性はあまりありません。 |
+| 40 - 60 | 良い。このモデルでは正確な予測が生成されますが、さまざまなオーディエンス設定を試すことで、さらに正確な結果が得られる可能性があります。 |
+| 20 - 40| 普通。このモデルでは正確で価値のある予測が提供されますが、さまざまなオーディエンス定義を試して、パフォーマンスが向上するかどうかを確認してみてください。 |
+| 0 - 20 | 悪い。オーディエンスの定義を変更して、もう一度やり直すことをお勧めします。 |
+{: .reset-td-br-1 .reset-td-br-2}
+
+予測は、2 週間ごとに再度トレーニングされ、予測品質メトリクスと一緒に更新されます。これにより、予測が最新のユーザー動作パターンで更新されたままになります。最後にこの再トレーニングが発生した時刻は、予測リストページと予測の分析ページに表示されます。
+
+## 推計結果 {#estimated_results}
+
+![][6]{: style="float:right;max-width:30%;margin-left:15px;"}
+
+チャートの下のパネルの右半分では、予測対象者のこの領域をターゲットとする期待精度の推定値を示します。過去の予測対象ユーザーに関するデータと、その過去のデータについて解約ユーザーと非解約ユーザーを識別するモデルの精度に基づいて、これらのプログレスバーは、スライダーで強調表示されたオーディエンスを使用した将来の潜在的なメッセージについて以下を推定します。
+
+1. 実際の解約者のうち、何人が正しいターゲットになるかの推定 <br><br> もちろん、私たちは未来を完全に予知できるわけではないので、予測対象のうちどのユーザーが将来解約するかは正確にはわかりません。しかし、この予測は信頼できる推論である。このプログレスバーは、過去のパフォーマンスに基づいて、予測対象ユーザーで予想される （過去の解約率に基づく）「実際の」または「真の」解約者のうち、現在のターゲティング選択でターゲットにされる人の数を示しています。この数のユーザーが、追加のメッセージや異常なメッセージでターゲットにしない場合には、混乱することが予想されます。<br><br>
+
+2. 実際には解約しないはずであったユーザーのうち、何人が誤ってターゲットとされるかの推定<br><br>すべての機械学習モデルはエラーを作ります。選択したユーザーの中に、_Churn Risk Score_が高く、最終的に解読されないユーザーがいる可能性があります。これは、貴社が何もしなくても、解約しなかったはずのユーザーです。いずれにしても対象となるので、これはエラーまたは"false positive."です。この 2 番目のプログレスバーの全幅は、解約しないユーザーの予想数を表し、塗りつぶされた部分は、現在のスライダー位置を使用して誤ってターゲットとなっているユーザーです。
+
+この情報をもとに、何人の解約者をキャプチャしたいのか、また偽陽性エラーのコストはどれほどかを判断することをお勧めします。価値あるプロモーションを発信しているのであれば、非解約者のターゲティングを最小限に抑える一方で、モデルが許す限り、予想される真の解約者をできるだけ多くキャプチャするのが理想的です。あるいは、誤検出の感度が低く、ユーザが追加のメッセージを受信した場合、より多くのオーディエンスにメッセージを送って、より多くの期待されるチャーナーをキャプチャし、可能性のあるエラーを無視することができます。
+
+## チャーン相関表 {#correlation_table}
+
+この分析では、ヒストリカル予測オーディエンスのユーザーチャーンと相関するユーザー属性またはビヘイビアが表示されます。それぞれの表は、解約の可能性が高い方が左、低い方が右に分割されています。各行について、左の列の行動や属性を持つユーザーの解約する可能性を示す比率が、右の列に表示されます。この数値は、この行動や属性を持つユーザーの解約可能性を、予測対象ユーザー全体の解約可能性で割った比率です。
+
+このテーブルは、ユーザ_Churn Risk Scores_ が更新されたときではなく、予測が再試行されたときにのみ更新されます。
+
+{% alert note %}
+プレビュー予測の相関データは部分的に非表示になります。この情報を表示するには、購入が必要です。詳細については、アカウントマネージャーにお問い合わせください。
+{% endalert %}
+
+[6]: {% image_buster /assets/img/churn/churnEstimatedResults.png %}
+[4]: {% image_buster /assets/img/churn/churnTargeting.gif %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md
new file mode 100644
index 00000000000..25d692c60f5
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md
@@ -0,0 +1,36 @@
+---
+nav_title: 予測品質
+title: 予測品質
+description: "この参考記事では、予測分析ページにある予測品質指標を詳しく見ていく。"
+page_order: 1
+Tool:
+  - Dashboard
+---
+
+# 予測の質
+
+> モデルの精度を測定するために、_予測品質_メトリックは、過去のデータでテストしたときに、この特定の機械学習モデルがどの程度効果的に見えるかを示す。Brazeは、モデル作成ページで指定したグループに従ってデータをプルする。モデルは、1つのデータセット（「トレーニング」セット）でトレーニングされ、次に新しい別のデータセット（「テスト」セット）でテストされる。 
+
+我々の_予測品質の_尺度は[揚力品質](https://dl.acm.org/doi/10.1145/380995.381018)である。コンバージョンのような成功した成果の増加を、比率やパーセンテージで測定する「リフト」はよく知られているだろう。ここでの成功した結果とは、解約したであろうユーザーを正しく特定することです。リフト品質とは、テストセットにメッセージングを行うときに考えられるすべてのオーディエンスサイズについて、予測が提供する平均リフトです。このアプローチでは、モデルがランダムな推測よりもどれだけ優れているかを測定する。この指標の 0% は、誰が解約するかについて、モデルの精度がランダムな推測と同程度であり、100% は誰が解約するかを完全に把握していることを示します。
+
+以下は、様々な_予測クオリティの_範囲に対する我々の推奨である：
+
+| 予測品質範囲(%) | 推奨 |
+| ---------------------- | -------------- |
+| 60 - 100 | 非常に良い。トップクラスの精度。オーディエンスの定義を変更しても新たなメリットが得られる可能性はあまりありません。 |
+| 40 - 60 | 良い。このモデルでは正確な予測が生成されますが、さまざまなオーディエンス設定を試すことで、さらに正確な結果が得られる可能性があります。 |
+| 20 - 40| 普通。このモデルでは正確で価値のある予測が提供されますが、さまざまなオーディエンス定義を試して、パフォーマンスが向上するかどうかを確認してみてください。 |
+| 0 - 20 | 悪い。オーディエンスの定義を変更して、もう一度やり直すことをお勧めします。 |
+{: .reset-td-br-1 .reset-td-br-2}
+
+予測は2週間ごとに再度トレーニングされ、_Prediction Quality_指標とともに更新されるため、最新のユーザー行動パターンに基づいて予測が更新される。さらに、その都度、直近2週間の予測を実際のユーザーの結果と照らし合わせてテストする。_予測品質は_、（予測ではなく）これらの実際の結果に基づいて計算される。これは、実際のシナリオで予測が正確であることを確認するための自動バックテスト（つまり、過去のデータを使って予測モデルをテストすること）である。この再トレーニングとバックテストが最後に行われた時間は、**予測**ページと個々の予測の分析ページに表示される。プレビュー予測であっても、作成後に一度だけこのバックテストが実行される。こうすることで、無料版でもカスタマイズされた予測の精度を確かめることができる。
+
+{% details 予測品質の詳細 %}
+
+例えば、通常、ユーザーの平均 20% が解約する場合、ユーザーの 20% のサブセットを無作為に選択し、それらのユーザーに「解約済み」のラベルを無作為に付けると (実際に解約したかどうかは問わない)、正しく特定される解約者は実際の 20% のみであると予想されます。それは当て推量です。もし、このモデルがその程度しかできないとしたら、この場合の揚力は1となる。
+
+一方、モデルがユーザーの 20% にメッセージを送信することを許可し、その結果、「真の」解約者をすべて捕捉し、解約者以外をまったく捕捉しなかった場合、リフトは 100% / 20% = 5 になります。この比率を、メッセージを送れる可能性の高い解約者の割合ごとにグラフにすると、[リフト・カーブが](https://towardsdatascience.com/the-lift-curve-unveiled-998851147871)得られる。 
+
+リフト品質 (および_予測品質_) を検討するもう 1 つの方法は、テストセットで解約者を特定する予測のリフト曲線が当て推量 (0%) から完全 (100%) までのどの位置にあるかです。リフト品質に関する元の論文については、「[Measuring lift quality in database marketing](https://dl.acm.org/doi/10.1145/380995.381018)」を参照してください。
+
+{% enddetails %}
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_faq.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_faq.md
new file mode 100644
index 00000000000..3fc42256edf
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_churn/prediction_faq.md
@@ -0,0 +1,58 @@
+---
+nav_title: トラブルシューティング
+article_title: 解約予測のトラブルシューティング
+description: "このリファレンス記事では、解約予測を使用する際に留意すべきトラブルシューティングステップと考慮事項について説明します。"
+page_order: 3
+
+---
+
+# トラブルシューティング
+
+> 解約予測 (およびすべての機械学習モデル) は、モデルに利用可能なデータと同程度にのみ優れています。また、それに使用する特定のデータ量に大きく依存します。 
+
+## 潜在的なエラー
+
+### トレーニングに十分なデータがない 
+
+このエラーメッセージは、解約の定義が厳しすぎるために、返された解約済みユーザーが少なすぎる場合に表示されます。 
+
+これを修正するには、解約を定義する日数またはアクション数のいずれか、または両方を変更して、より多くのユーザーをキャプチャする必要があります。制限の厳しい定義を作成しないように、`AND/OR` フィルタを正しく使用していることを確認します。 
+
+{% alert important %}
+解約予測が会社レベルでオンになっていても、一部のワークスペースには予測を作成するために十分なユーザーがいない場合があります。通常、単一のワークスペースに月間アクティブユーザー 300,000 人が必要です。
+{% endalert %}
+
+### 予測オーディエンスサイズの問題
+
+![][3]{: style="float:right;max-width:60%;margin-left:15px;margin-bottom:15px;margin-top:15px;"}
+
+予測オーディエンスを構築して、モデルでトレーニングしたい使用方法を微調整する場合、予測オーディエンスのユーザ数が少なすぎることを通知する次のメッセージが表示されることがあります。 
+
+" 過去7 日間、選択した予測オーディエンスから利用可能な過去のチャーナーが、確実に予測を構築するには十分ではありません。"
+
+予測オーディエンスの定義が厳しすぎる場合、履歴ユーザーとアクティブユーザーの両方の十分なサイズのプールがない可能性があります。これを修正するには、定義に使用する日数と属性の種類を変更するか、解約を定義するアクションを切り替えるか、またはその両方を行う必要があります。 
+
+定義を切り換えた後も、予測の対象者が引き続き問題である場合は、このオプション機能をサポートするユーザーが少なすぎる可能性があります。代わりに、追加のレイヤーとフィルタなしで予測を構築することをお勧めします。 
+
+### 観客の予測サイズが大きすぎる
+
+予測対象ユーザー定義のユーザー数が 1 億人を超えることはできません。オーディエンスが多すぎるというメッセージが表示された場合は、オーディエンスにより多くのレイヤーを追加するか、その基になっている時間枠を変更することをお勧めします。
+
+### 予測の質が悪い
+
+![][1]{: style="float:right;max-width:40%;margin-left:15px;"}
+あなたのモデルが[予測品質]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/)が40%以上であれば、素晴らしい場所にいます!ただし、予測品質が39% 以下に低下する場合は、チャーンおよび予測オーディエンスの定義をより具体的に編集するか、異なる時間枠を設定する必要があります。 
+
+予測定義を構築し、予測品質が40% を超えている間にオーディエンスのサイズ要件を満たすことができない場合は、Braze に送信されるデータがこのユースケースに適していないこと、モデルを構築するためのユーザーが十分でないこと、または製品のライフサイクルが現在の60 日間のルックバックウィンドウでサポートされている期間よりも長いことを意味します。 
+
+## データに関する考慮事項
+
+Predictive Churn を設定する際には、以下の質問が必要です。機械学習モデルは、彼らを訓練するデータと同じくらい優れているだけなので、良いデータ衛生の実践を持ち、モデルに入るものを理解することは大きな違いを生み出します。
+
+- リテンションとロイヤルティにつながる高価値行動とは?
+- これらの特定のアクションにマップバックするカスタムイベントを設定しましたか?Predictive Churn は、カスタム属性ではなく、カスタムイベントで動作します。
+- あなたはチャーンを定義する時間の窓で考えていますか?チャーンは、最大60日以内に発生するものとして定義できます。
+- 休日などの非定型的なユーザー行動につながる時間を考慮しましたか?消費者行動の急激な変化は、あなたの予測に影響を与えるだろう。 
+
+[1]: {% image_buster /assets/img/churn/churn3.png %}
+[3]: {% image_buster /assets/img/churn/audience_size_error.png %}
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events.md
new file mode 100644
index 00000000000..a97a58b27b9
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events.md
@@ -0,0 +1,51 @@
+---
+nav_title: 予測イベント
+article_title: 予測イベント
+page_order: 6.4
+layout: featured
+alias: /predictive_purchases/
+search_rank: 1
+guide_top_header: "予測イベント"
+guide_top_text: "どのユーザーが特定のイベント(購入のような)を実行する可能性が高いかを知ることは、成長するビジネスにとって極めて重要な洞察です。それがなければ、どのキャンペーンをどのように構築するかを決めるのだろうか。誰が割引とプロモーションを受けるべきですか？限られた予算をどこで使うのか。Braze は、これらの質問にPredictive Events (以前はPredictive Purchases) で回答するのに役立ちます。これは、マーケティングチームが将来の行動を理解しやすくし、エンゲージメントと収益最大化キャンペーンにリソースを集中させる機械学習モデルです。"
+description: "この記事では、予測イベント(以前はPredictive Purchases)について説明します。これは、マーケターがイベントを実行する可能性に基づいてユーザーを識別し、メッセージを送る機能を提供するツールです。"
+
+guide_featured_title: "トピック"
+guide_featured_list:
+- name: 予測の作成
+  link: /docs/user_guide/brazeai/predictive_suite/predictive_events/creating_an_event_prediction/
+  image: /assets/img/braze_icons/settings-01.svg
+- name: 予測分析
+  link: /docs/user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics/
+  image: /assets/img/braze_icons/bar-chart-01.svg
+- name: ユーザーへのメッセージング
+  link: /docs/user_guide/brazeai/predictive_suite/predictive_events/messaging_users/
+  image: /assets/img/braze_icons/arrow-narrow-right.svg
+
+---
+
+## 概要
+
+![「"Predictive Events Works"」というタイトルのグラフィック。左側には、機械学習モデルに組み込まれているユーザデータが表示されます。ラベルは"Train と履歴データを読み取り、特定の期間にイベントを実行したユーザの動作を&quot 以外のユーザと比較します。右側には、機械学習の結果が表示されます。ここでは、ユーザがイベントを実行する可能性が最も低い順位にランク付けされています。ラベルは" Predict likely of future eventsを読み取り、正確で便利なターゲティングのために、ユーザに尤度スコアを割り当てます。][1]
+
+> 予測イベントは、マーケターがイベントを実行する可能性に基づいてユーザーを識別し、メッセージを送るための強力なツールとなります。イベント予測を作成すると、Braze は[グラデーションブーストされた意思決定ツリー](https://en.wikipedia.org/wiki/Gradient_boosting) を使用して機械学習モデルをトレーニングし、以前のアクティビティから学習し、将来のアクティビティを予測します。
+
+予測が作成されると、ユーザーには、選択したイベントを実行する可能性を示す[尤度スコア]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics/#purchase_score) 0 ～100 が割り当てられます。スコアが高いほど、ユーザーはそのイベントを実行する可能性が高くなります。また、ユーザは低、中、高の尤度カテゴリ別にソートされます。
+
+予測イベントの実際の値は、予測結果を使用してセグメントまたはキャンペーンを作成することです。マーケターは、**Prediction** ページで直接ターゲットを絞ったキャンペーンを構築して、すぐに収益を上げる結果を得たり、将来のキャンペーンやキャンバスのセグメントを保存したりできます。誰が最初にターゲットにするのかわからない?メッセージングユーザの可能性スコアに基づいて、[戦略的考慮事項]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_purchases/messaging_users/#strategy)を読みます。
+
+## アクセス予測イベント
+
+\[**予測**] ページは \[**分析**] セクションにあります。フルアクセスが必要な場合、アカウントマネージャーにお問い合わせください。
+
+{% alert note %}
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、**Predictions**は**Engagement**にあります。
+{% endalert %}
+
+この機能を購入する前に、プレビューモードで使用できます。これにより、合成データを使用してデモ予測を表示したり、一度に1 つのプレビュー予測モデルを作成したりできます。この予測は、実際のユーザデータに基づいて作成されますが、ユーザの尤度スコアに従ってメッセージングをターゲットにすることはできません。また、作成後も定期的に更新されません。
+
+プレビューでは、この1 つの予測を編集して再構築したり、アーカイブしたりして、期待される[予測品質]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics/#prediction_quality) of [異なるオーディエンス]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_events/creating_an_event_prediction/#audience) をテストし、アナリティクスに精通するように他のユーザを作成することもできます。
+
+<br><br>
+
+[1]: {% image_buster /assets/img/how_predictive_events_works.png %}
+
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events/creating_an_event_prediction.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events/creating_an_event_prediction.md
new file mode 100644
index 00000000000..4623d71eb60
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events/creating_an_event_prediction.md
@@ -0,0 +1,90 @@
+---
+nav_title: イベント予測の作成
+article_title: イベント予測の作成
+page_order: 1
+description: "この記事では、Braze ダッシュボード内でイベント予測を作成する方法について説明します。"
+
+---
+
+# イベント予測の作成
+
+> 予測は、訓練された機械学習モデルの1つのインスタンスであり、それが使用するすべてのパラメータとデータです。予測イベントの詳細については、[予測イベントの概要]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_events)を参照してください。
+
+ブレーズで、**Analytics**> **Predictive Events** に移動します。
+
+{% alert note %}
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、**Predictions**は**Engagement**にあります。
+{% endalert %}
+
+このページでは、現在アクティブなイベント予測とその基本情報のリストが表示されます。ここでは、名前の変更、アーカイブ、および新しい予測の作成ができます。アーカイブされた予測は非アクティブであり、ユーザースコアは更新されません。
+
+## ステップ 1:新しい予測を作成する
+
+1. **予測の作成**を選択し、新しい**イベント予測**を選択します。
+
+{% alert note %}
+同時にアクティブな予測は5 つに制限されます。Predictive Events を購入する前に、制限は1 つのアクティブなプレビュー予測です。プレビュー予測では、予測の出力に基づいてスコアまたはターゲットユーザーが定期的に更新されることはありません。詳細については、アカウントマネージャにお問い合わせください。
+{% endalert %}
+
+{: start="2"}
+2\.予測に一意の名前を付けます。関連するメモを保存するための説明を指定することもできます。
+
+![][1]
+
+{: start="3"}
+3\.次の手順に進むには、**Forward**をクリックします。<br><br>必要に応じて、**Build Now**をクリックしてすべてのデフォルト設定を使用し、作成の最後のステップにスキップすることができます。ビルドプロセスを開始する前に、設定を確認することができます。また、一番上のバーでクリックすると、後で任意のステップに戻ることができます。
+
+## ステップ 2:イベントトラッキングの指定 {#event-tracking}
+
+ユーザのイベントがブレーズに[購入イベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/)または[カスタムイベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/)として保存されているかどうかを指定します。
+
+ここでは、選択したメソッドが、機械学習モデルを作成するためにBraze に十分なデータを提供しているかどうかを確認します。要件が満たされていない場合は、アプリケーションでも使用されている他のロギング方法を選択してみてください。残念ながら、そうでない場合、Brazeは利用可能なデータの量で予測を作成できません。このエラーを間違って見ていると思われる場合は、カスタマー・サクセス・マネージャーに連絡してください。
+
+#### イベントウィンドウ
+
+イベント・ウィンドウは、ユーザーがイベントを実行するかどうかを予測する時間枠です。60日まで設定できます。このウィンドウは、予測をトレーニングするために履歴データを照会するために使用されます。さらに、予測が作成され、ユーザがスコアを受け取った後、尤度スコアは、ユーザがイベントウィンドウで指定された日数内にイベントを実行する可能性を示します。
+
+### ステップ 3:予測オーディエンスをフィルタリングする(オプション) {#audience}
+
+予測対象者は、予測する可能性スコアを持つユーザのグループです。必要に応じて、ユーザーの母集団全体について予測を実行できます。これを行うには、デフォルトのオプション**All Users** を選択したままにします。
+
+通常、評価するユーザーをいくつかの基準でフィルタリングすると、モデルのパフォーマンスが向上します。これを行うには、**自分の予測オーディエンスを定義**を選択し、オーディエンスフィルタを選択します。たとえば、" First Used App" filter set to 30 days を選択して、アプリを少なくとも30 日間使用していたユーザーに集中することができます。
+
+予測オーディエンス定義は、機械学習モデルが過去から学習できるように、履歴データのクエリにも使用されます。前のページと同様に、これらのフィルタによって提供されるデータの量が、要件とともに表示されます。必要なオーディエンスを指定し、最小値を満たさない場合は、より広範なフィルタを指定するか、**All Users** オプションを使用します。
+
+{% alert note %}
+予測対象者は1億 人を超えることはできません。
+{% endalert %}
+
+イベントウィンドウが14日以内の場合、"Last..." like "Last Used App"および"Last Made Purchase" **で始まるフィルタの時間枠は、[イベントトラッキング](#event-tracking)**で指定されたイベントウィンドウを超えることはできません。たとえば、イベントウィンドウが14日に設定されている場合、"Last..."フィルタの時間枠は14日を超えることはできません。
+
+#### フルフィルターモード
+
+新しい予測をすぐに構築するために、ブレーズセグメンテーションフィルタのサブセットのみがサポートされています。Full Filter Mode(フルフィルタモード)では、すべてのろう付けフィルターを使用できますが、予測を作成するには1 つのイベントウィンドウが必要です。 
+
+たとえば、イベントウィンドウが14 日に設定されている場合、フルフィルタモードでのみサポートされるフィルタを使用すると、ユーザデータの収集と予測の作成に14 日かかります。 また、フルフィルタモードでは、視聴者のサイズに関する一部の見積もりが利用できなくなります。
+
+### ステップ 4:アップデートスケジュールを選択する
+
+このページを完了したときに作成された機械学習モデルは、ここで選択したスケジュールで使用され、ユーザがイベントを実行する確率(尤度スコア)の新規スコアを生成します。役立つと思われる**更新の最大頻度**を選択します。たとえば、購入を予測しており、週次プロモーションを送信する予定の場合は、選択した日時に更新頻度を**Weekly** に設定します。
+
+{% alert note %}
+プレビューとデモの予測では、ユーザの尤度スコアは更新されません。
+{% endalert %}
+
+### ステップ 5: 予測を構築する
+
+指定した詳細が正しいことを確認し、**Build Prediction** を選択します。また、**Save As Draft**を選択してこのページに戻り、後でモデルをビルドすることで、ドラフトフォームに変更を保存することもできます。 
+
+**Build Prediction**をクリックすると、モデルを生成するプロセスが開始されます。これには、データボリュームに応じて、30 分から数時間かかる場合があります。この予測では、モデル構築プロセスの間、トレーニングが進行中であることを説明するページが表示されます。
+
+完了すると、ページが自動的に分析ビューに切り替わり、予測と結果の準備ができたことを知らせる電子メールが送信されます。エラーが発生すると、ページは編集モードに戻り、何が間違っていたかが説明されます。
+
+予測は自動的に再構築され("retrained")、**2 週間** ごとに最新のデータで更新されます。これは、ユーザの尤度スコア(予測の出力)が生成される場合とは別のプロセスであることに注意してください。後者は、手順4で選択した更新頻度によって決まります。
+
+## アーカイブ済み予測
+
+アーカイブされた予測では、ユーザースコアの更新が停止します。アーカイブされていないアーカイブされた予測は、事前に設定されたスケジュールでユーザーのスコアを更新し続けます。アーカイブされた予測は削除されず、リストに残ります。
+
+[1]: {% image_buster /assets/img/purchasePrediction/purchases_step1.png %}
+
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events/messaging_users.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events/messaging_users.md
new file mode 100644
index 00000000000..e1750dc43aa
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events/messaging_users.md
@@ -0,0 +1,47 @@
+---
+nav_title: ユーザーへのメッセージング
+article_title: 予測イベントのターゲットユーザー
+description: "このリファレンス記事では、イベント予測を作成した後に発生する可能性のあるステップ (フィルターの実装や戦略的な考慮事項など) について説明します。"
+page_order: 3
+
+---
+
+# ユーザーへのメッセージング {#what-do-next}
+
+> イベント予測を作成した後で、ユーザを予測イベントのターゲットにする方法について説明します。
+
+{% alert note %}
+プレビューおよびデモ予測ではユーザーをメッセージングの対象にすることはできず、\[**セグメントを作成**] ボタンと \[**キャンペーンを作成**] ボタンは無効になります。この機能を購入するには、アカウントマネージャにお問い合わせください。
+{% endalert %}
+
+## フィルターの実装{#filters}
+
+個々の**Predictions**ページから、目標とする可能性スコアまたはカテゴリの範囲を決定した後、**セグメント**または**キャンペーン**ボタンを使用して、新しいセグメントまたはキャンペーンを作成できます。このセグメントまたはキャンペーンは、スライダで選択した尤度スコアまたはカテゴリを持つユーザをフィルタします。
+
+![オーディエンスを定義するときに使用できるフィルターには、可能性カテゴリおよび可能性スコアが含まれます。][5]
+
+他のフィルターを Braze で使用する場合と同様に、フィルターをキャンペーン、キャンバス、またはセグメントでも使用して、可能性のスコアまたはカテゴリに基づいてユーザーを対象にすることができます。
+
+## 戦略的考慮事項 {#strategy}
+
+今後、誰がイベントを実行するか、または実行しないかがわかったので、これから顧客に対するメッセージをどのように行うか、そしてマーケティングリソースをどのように割り当てるかについて考えましょう。
+
+可能性スコアやカテゴリに基づいてユーザにメッセージを送ることは、単にお金を稼ぐのに役立つだけではなく、お金を節約するのにも役立ちます。スライディングスケールでプロモーションを提供する:ユーザが購入する可能性が高いほど、必要となる割引は少なくなる。これらが釣り合う位置を見つけると、顧客ごとに適切な価値の量を提供し、取得することができます。また、他のフィルターをこれらのセグメントにレイヤー化して、誰がどのメッセージを受け取るかをさらに限定することもできる点に留意してください。
+
+以下に、ユーザーの可能性スコアに基づいて予測イベント戦略をただちに始めるためのアイデアをいくつか示します。
+
+### 可能性の高いユーザー
+
+買い物を完了するなどのイベントを実行する可能性が最も高いユーザーへのメッセージングによって、迅速に目的が達成されます。カートに入れたままになっているアイテムに関するリマインダーメール、「今すぐご購入ください」というアプリ内メッセージ、またはパーソナライズされたプッシュ通知が有効な場合があります。
+
+### 可能性が中程度のユーザー
+
+可能性が中程度のユーザーに対して追加の微調整が必要なプロモーションを保存します。特別割引の提供、Facebook や Google の関連コンテンツに基づくリターゲティング、または新規エクスペリエンス (商品、機能、またはレベル) への早期独占アクセスの提供を行います。
+
+### 可能性が低いユーザー
+
+可能性が低いユーザーに対して試すことのできるパスがいくつかあります。そのようなユーザーに購入を促す方法を考えてみましょう。より高率の割引を提供するか、3 日間集中的なクロスチャネルの宣伝を行います。パーソナライズされたおすすめやハンズオンサポートを提供し、購入プロセスをできるだけシンプルで簡単にする。
+
+自社ブランドを最優先に考えて、これらのユーザーを、リソースの負荷が軽く、より受動的なキャンペーンまたはキャンバスのターゲットにします。これには、ペルソナに固有の週刊ニュースレター、関連する一連の顧客ケーススタディ、月刊の新しいヒントやコツのまとめなどがあります。
+
+[5]: {% image_buster /assets/img_archive/predictive_event_filters.png %}
diff --git a/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics.md b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics.md
new file mode 100644
index 00000000000..8c4395edb88
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/predictive_suite/predictive_events/prediction_analytics.md
@@ -0,0 +1,91 @@
+---
+nav_title: 予測分析
+article_title: 予測分析
+description: "この参考記事では、予測イベント分析ページに含まれるさまざまなコンポーネントと、それらを使用してインサイト主導の意思決定を行う方法について説明する。"
+page_order: 2
+
+---
+
+# 予測分析
+
+> 予測が構築されトレーニングされると、**予測分析**ページにアクセスできるようになる。このページは、好感度スコアやカテゴリーに基づいて、ターゲットとすべきユーザーを決定するのに役立つ。
+
+予測がトレーニングされ、このページが入力されるとすぐに、セグメントやキャンペーンで[フィルターを]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/messaging_users/#filters)使い始め、モデルの出力を使い始めることができる。誰をターゲットにするのか、なぜターゲットにするのかを決める手助けが必要なら、このページがモデルの歴史的正確さとあなた自身のビジネス目標に基づいて手助けしてくれるだろう。
+
+## 分析コンポーネント
+
+- [可能性スコア](#purchase_score)
+- [ユーザーへのターゲット設定](#target_users)
+- [予測品質](#prediction_quality)
+- [推定結果](#estimated_results)
+- [イベント相関表](#correlation_table)
+
+## 可能性スコア {#purchase_score}
+
+予測対象ユーザーには、0から100の間で尤度スコアが割り当てられる。スコアが高いほど、そのイベントをパフォーマンスする可能性が高くなる。 
+
+以下は、可能性スコアによってユーザーがどのように分類されるかである：
+
+- **低：**0から50の間
+- **ミディアム：**50～75
+- **高：**75～100
+
+得点と対応するカテゴリーは、**予測作成**ページで選択したスケジュールに従って更新される。尤度スコアが20の等しい大きさのバケツのそれぞれ、または尤度カテゴリのそれぞれにあるユーザーの数は、ページ上部のグラフに表示されている。
+
+## オーディエンスビルダーでユーザーをターゲティングする {#target_users}
+
+予測対象ユーザー全体の尤度スコアの分布は、ページの上部に表示される。さらに右側のバケツにいるユーザーはスコアが高く、イベントを実行する可能性が高い。左寄りのバケツのユーザーは、イベントを実行する可能性が低い。チャートの下にあるスライダーでユーザーのセクションを選択し、そのユーザーをターゲットにした場合の結果を推定することができる。
+
+![][4]{: style="max-width:90%"} 
+
+スライダーのハンドルをさまざまな位置に動かすと、パネルの左半分にあるバーが、選択したターゲット層を使って予測対象ユーザー全体のうち何人のユーザーをターゲットにするかを知らせてくれる。
+
+### 推定結果 {#estimated_results}
+
+チャートの下にあるパネルの右半分には、選択した予測対象ユーザーのうち、イベントを実行すると予想されるユーザー数と、実行しないと予想されるユーザー数という2つの方法で、選択した部分をターゲットにした場合の予想精度を示している。
+
+![][6]
+
+
+#### 選ばれた何人のユーザーがそのイベントを実行すると予想されるか
+
+つまり、Brazeはイベントを実行する未来のユーザーをすべて識別できるわけではない。尤度スコアは、情報に基づいた信頼できる予測の集合のようなものだ。プログレスバーは、予測対象ユーザーで予想される「真陽性」のうち、選択したオーディエンスでターゲットになる数を示す。なお、メッセージを送らなくても、この数のユーザーがイベントを実行することを期待している。
+
+#### 選ばれたユーザーのうち、何人がそのイベントを実行しないと予想されるか
+
+すべての機械学習モデルはエラーを起こす。選択したユーザーの中に、可能性スコアが高くても、実際にイベントを実行しないユーザーがいるかもしれない。あなたが何もアクションを起こさなければ、彼らはイベントをパフォーマンスしないだろう。いずれにせよ標的にされるのだから、これはエラーあるいは "偽陽性 "である。この2番目のプログレスバーの全幅は、イベントを実行しないユーザーの予想数を表し、塗りつぶされた部分は、現在のスライダーの位置を使用して、誤ってターゲットにされるユーザーである。
+
+この情報をもとに、どれだけの真陽性を捕捉したいのか、どれだけの偽陽性をターゲットとして許容できるのか、エラーのコストはビジネスにとってどれくらいなのかを決めることをお勧めする。価値のあるプロモーションを発信している場合、チャートの左側を優先することで、非購入者（偽陽性）だけをターゲットにすることができる。あるいは、チャートの右側を好むユーザーのセクションを選択することで、よく購入してくれるバイヤー（トゥルーポジティブ）に再度購入してもらいたいと思うかもしれない。
+
+### 予測品質 {#prediction_quality}
+
+モデルの精度を測定するために、_予測品質_メトリックは、この特定の機械学習モデルがどの程度効果的であるかを示す。これは、この予測がイベント・パフォーマーとそうでないパフォーマーを見分けるのにどれだけ優れているかを示す指標である。_予測品質が_100であれば、誰がそのイベントを行うか、また行わないかをエラーなく完璧に把握していることを意味し（こんなことは決して起こらない！）、0であればランダムに推測していることを意味する。この指標の詳細については、「[予測品質]({{site.baseurl}}/user_guide/brazeai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/)」を参照されたい。
+
+以下は、様々な_予測クオリティの_範囲に対する我々の推奨である：
+
+| 予測品質範囲(%) | 推奨 |
+| ---------------------- | -------------- |
+| 60 - 100 | 非常に良い。トップクラスの精度。オーディエンスの定義を変更しても新たなメリットが得られる可能性はあまりありません。 |
+| 40 - 60 | 良い。このモデルでは正確な予測が生成されますが、さまざまなオーディエンス設定を試すことで、さらに正確な結果が得られる可能性があります。 |
+| 20 - 40| 普通。このモデルでは正確で価値のある予測が提供されますが、さまざまなオーディエンス定義を試して、パフォーマンスが向上するかどうかを確認してみてください。 |
+| 0 - 20 | 悪い。オーディエンスの定義を変更して、もう一度やり直すことをお勧めします。 |
+{: .reset-td-br-1 .reset-td-br-2}
+
+予測は2週間ごとに再度トレーニングされ、予測品質指標とともに更新されるため、予測は常に最新のユーザー行動パターンに更新される。この再トレーニングが最後に行われた時刻は、予測リストページと予測分析ページに表示される。 
+
+予測が最初に作成されるとき、予測の質は、**予測を構築するを**クリックしたときに照会される履歴データに基づいている。その後2週間ごとに、予測スコアと実際の転帰を比較することで、予測の質が導き出される。
+
+## イベント相関表 {#correlation_table}
+
+この分析では、予測対象ユーザーのイベントに相関するユーザー属性や行動が表示される。評価される属性は、年齢、国、性別、言語である。分析される行動には、セッション、購入、総支出額、カスタムイベント、過去30日間に受けたキャンペーンやキャンバスステップなどが含まれる。
+
+表はそれぞれ、そのイベントを行う可能性が高い方を左、低い方を右に分けている。各行について、左の列の行動またはアトリビューションを持つユーザーが、そのイベントを実行する可能性が高いか低いかの比率が、右の列に表示される。この数値は、この行動またはアトリビューションを持つユーザーの尤度スコアを、予測対象ユーザー全体からそのイベントを実行する尤度で割った比率である。
+
+このテーブルは、予測が再学習するときにのみ更新され、ユーザーの尤度スコアが更新されるときには更新されない。
+
+{% alert note %}
+プレビュー予測の相関データは部分的に隠される。この情報を表示するには、購入が必要です。詳細については、アカウントマネージャーにお問い合わせください。
+{% endalert %}
+
+[6]: {% image_buster /assets/img/purchasePrediction/purchaseEstimatedResults.png %}
+[4]: {% image_buster /assets/img/purchasePrediction/purchaseTargeting.png %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/brazeai/recommendations.md b/_lang/ja/_user_guide/brazeai/recommendations.md
new file mode 100644
index 00000000000..4924ffe930e
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/recommendations.md
@@ -0,0 +1,24 @@
+---
+nav_title: おすすめ
+article_title: おすすめ
+page_order: 15
+layout: dev_guide
+search_rank: 1
+guide_top_header: "おすすめ"
+guide_top_text: "Brazeで推薦のステップアップを図ろう。ここでは、レコメンデーションエンジンの設定について知っておくべきことをまとめ、ユーザーが実際に欲しいアイテムやコンテンツを提案できるようにする。AIを使ったカスタマーエクスペリエンスのカスタマイズから、リキッドやコネクテッドコンテンツを使った独自のエンジンの開発まで、あらゆるレコメンデーションに必要なすべてが見つかる。"
+description: "このランディングページでは、Brazeでのレコメンデーションエンジンの構築と使用に関する記事を掲載している。"
+
+guide_featured_title: "記事"
+guide_featured_list:
+- name: 推薦について
+  link: /docs/user_guide/brazeai/recommendations/about_item_recommendations/
+  image: /assets/img/braze_icons/book-closed.svg
+- name: AI 項目のレコメンデーション
+  link: /docs/user_guide/brazeai/recommendations/ai_item_recommendations/
+  image: /assets/img/braze_icons/user-check-01.svg
+- name: ルールに基づく推薦
+  link: /docs/user_guide/brazeai/recommendations/rules_based_recommendations/
+  image: /assets/img/braze_icons/list.svg
+---
+
+<br><br>
diff --git a/_lang/ja/_user_guide/brazeai/recommendations/about_item_recommendations.md b/_lang/ja/_user_guide/brazeai/recommendations/about_item_recommendations.md
new file mode 100644
index 00000000000..2f075ab0d17
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/recommendations/about_item_recommendations.md
@@ -0,0 +1,395 @@
+---
+nav_title: アイテムのおすすめについて
+article_title: アイテムのおすすめについて
+description: "このリファレンス記事では、ブレーズを使用するお客様にアイテムを推奨するためのさまざまなユースケースについて説明します。"
+page_order: 1
+---
+
+# アイテムのおすすめについて
+
+この記事では、顧客が興味を持っているアイテムを提案できるさまざまな方法について学び、Brazeを使ってレコメンドエンジンを作成するための一般的なユースケースのインスピレーションを得ることができます。
+
+## 前提条件
+
+すべてのおすすめのタイプについて、少なくとも 1 つの[カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/) (おすすめのアイテムを取り出す元) を設定する必要があります。
+
+## 推奨事項のタイプ
+
+顧客におすすめのアイテムを提示するときに、実行できるいくつかのアプローチがあります。
+
+- [AI によるパーソナライズ](#ai)
+- [最も人気がある](#most-popular)
+- [最新](#most-recent)
+- [セレクションベース](#selections-based)
+- [ルールベース](#rules-based)
+- [トレンド](#trending)
+
+### AI カスタマイズされた推奨事項 {#ai}
+
+[AI 項目の推奨事項][1] 機能の一部として、AI カスタマイズされた推奨事項はディープラーニングを利用して、ユーザーが過去に関心を示した内容に基づいて、次にユーザーが関心を持つ可能性が最も高いものを予測します。この方法は、ユーザーの行動に適応する動的でカスタマイズされた推奨システムを提供します。
+
+AI パーソナライズされたレコメンドは、購入やカスタムイベントなど、アイテムのインタラクションデータの過去6 か月間を使用してレコメンドモデルを構築します。パーソナライズされたリストに十分なデータがないユーザーの場合、最も人気のあるアイテムがフォールバックとして機能するため、ユーザーはまだ関連する提案を受けています。
+
+AI 項目の推奨事項を使用すると、使用可能な項目をさらに絞り込むこともできます
+[選択項目]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)。ただし、Liquid を使用したセレクションは AI によるおすすめに使用できないため、カタログのセレクションを作成するときにはその点に留意してください。
+
+例については、この記事の[Use cases](#use-cases)セクションを参照してください。
+
+{% alert tip %}
+AI によりパーソナライズされたおすすめは、数百から数千のアイテムが用意され、かつ通常、購入データまたはインタラクションデータを持つユーザーが 30,000 人以上の場合に最も効果的です。これはあくまでも目安であり、様々です。他の推奨タイプは、より少ないデータで動作できます。
+{% endalert %}
+
+### 最も人気のあるアイテムのおすすめ {#most-popular}
+
+"AI Personalized" model に加えて、[AI item recommendations][1] 機能には、&quot のおすすめモデルも含まれています。最も人気のある" は、ユーザーが最も多く関わるアイテムを特徴としています。
+
+追跡しているインタラクションデータに基づき、このモデルのユースケースとして、次のおすすめが考えられます。
+
+- [最も人気のある商品](#most-popular-items)
+- [多数が「いいね」したアイテム](#liked-items)
+- [閲覧数が上位のアイテム](#most-viewed-items)
+- [ユーザーのカートで人気のアイテム](#popular-items-in-users-carts)
+
+### 最新アイテムのおすすめ{#most-recent}
+
+"AI Personalized" model に加えて、[AI item recommendations][1] 機能には&quot のおすすめモデルも含まれています。最新の" は、ユーザーが最も多く関わるアイテムを特徴としています。このモデルを使用して、離脱ユーザーに関連コンテンツへの再エンゲージを促すことにより、解約を防止します。
+
+追跡しているインタラクションデータに基づき、このモデルのユースケースとして、次のおすすめが考えられます。
+
+- [最近クリックしたアイテム](#recently-clicked-items)
+- [最近「いいね」したアイテム](#liked-items)
+- [最近エンゲージしたアイテムまたは購入したアイテム](#recently-engaged-with-or-purchased-items)
+- [最近カートに追加したアイテム](#items-recently-added-to-cart)
+
+### トレンド項目の推奨事項 {#trending}
+
+"AI Personalized" model に加えて、[AI item recommendations][1] 機能には"Trending" のおすすめモデルも含まれています。このモデルには、最近のユーザーインタラクションに関して最も肯定的なモメンタムを持つ項目が含まれています。 
+
+" Most Popular" model (一貫して高いインタラクションを持つアイテムを特徴とする) とは異なり、このモデルはインタラクションでアップティックを経験したアイテムを特徴としています。新進気鋭で、現在けん引力が増している製品をおすすめするのに使えます。
+
+追跡しているインタラクションデータに基づき、このモデルのユースケースとして、次のおすすめが考えられます。
+
+- [購入品の推移](#trending-purchased-items)
+- [好きなアイテムのトレンド](#trending-liked-items)
+
+### 選択に基づく推奨事項 {#selections-based}
+
+[選択]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)はカタログデータの特定のグループです。選択範囲を使用する場合、基本的にはカタログ内の特定の列に基づいてカスタムフィルタを設定します。これには、ブランド、サイズ、場所、追加日などのフィルターがあります。これにより、ユーザに表示する項目を満たす必要がある条件を定義できるため、推奨する内容を制御できます。
+
+これまでの3つのタイプはすべて、Brazeで推奨モデルを設定し、トレーニングすることです。これらのモデルでセレクションを使用することもできますが、カタログのセレクションと Liquid でのパーソナライゼーションだけを使用するだけで、おすすめのユースケースのいくつかを実現することもできます。
+
+次のおすすめを含むいくつかのユースケースがあります。
+
+- [新しいアイテム](#new-items)
+- [ランダムなアイテム](#random-items)
+
+### ルールに基づく推奨事項 {#rules-based}
+
+[ルールベースのレコメンド]({{site.baseurl}}/rules_based_recommendations/)エンジンは、ユーザデータと製品情報を使用して、メッセージ内のユーザに関連する項目を提案します。Liquid と、Braze のカタログまたはコネクテッドコンテンツを使用して、ユーザーの行動や属性に基づいてコンテンツをダイナミックにパーソナライズします。
+
+ルールベースの推奨事項は、手動で設定する必要がある固定ロジックに基づいています。つまり、ロジックを更新しない限り、おすすめはユーザの個々の購入履歴や嗜好に合わせて調整されません。したがって、この方法は、頻繁な更新を必要としないおすすめに最適です。
+
+次のようなユースケースがあります。
+
+- **補充のリマインダー:**毎月のビタミンや毎週の食料雑貨品など、前回の購入日に基づいて、予測可能な使用サイクルを持つ品目の再在庫リマインダーを送信する。
+- **初回購入者:**2回目の購入を奨励するために、初回購入者にスターターキットまたは導入オファーをお勧めします。
+ロイヤリティプログラム:顧客の現在のポイント残高に基づいて、顧客のロイヤルティポイントまたは報酬を最大化するような製品を強調する。
+- **教育的なコンテンツ:**以前に消費または購入した素材の話題に基づいて、新しいコースまたはコンテンツを提案します。
+
+## ユースケース
+
+### ユーザーが次に購入する可能性が最も高いアイテム
+
+購入イベントまたは購入に関連するカスタムイベントに基づいて、ユーザーが次に購入する可能性が最も高いアイテムを予測して推奨します。以下に例を示します。
+
+- 旅行サイトは、ユーザーのブラウジング履歴と以前の予約に基づいて、休暇パッケージ、フライト、またはホテル滞在を提案することができ、次の旅行先を予測し、旅行を計画しやすくすることができます。
+- ストリーミングプラットフォームでは、視聴習慣を分析して、ユーザーが次に視聴する可能性が最も高い番組や映画をおすすめすることにより、ユーザーのエンゲージメントを維持して解約率を下げることができます。
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- 購入オブジェクトまたはカスタムイベントの購入を追跡する方法
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/)を作成します。
+2. \[**タイプ**] を \[**AI パーソナライズ済み**] に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。
+5. 購入イベントの現在の追跡方法と、対応するイベントプロパティを選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングでおすすめを使用します。]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)
+
+{% enddetails %}
+
+### 最近カートに追加したアイテム
+
+最近カートに追加したがまだ購入していないアイテムへの関心をユーザーに思い出させます。例えば、オンライン小売業者は、リマインダーを送ったり、カートの中の商品に期間限定の割引を提供したりすることができ、ユーザーは、オファーの期限が切れる前に購入を完了するよう促すことができる。
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- カートに追加のカスタムイベント
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/)を作成します。
+2. \[**タイプ**] を \[**最新**] に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。
+5. \[**カスタムイベント**] を選択し、リストから「カートに追加」のカスタムイベントを選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングでおすすめを使用します。]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)
+
+{% enddetails %}
+
+### 気に入ったアイテム
+
+最近気に入ったアイテムや人気のあるアイテムを、好きなカスタムイベントに基づいて探索するようユーザーに促す。例えば、音楽ストリーミングアプリでは、ユーザーが過去に「いいね」したジャンルやアーティストに基づいて、パーソナライズされたプレイリストを作成したり、新しいアルバムのリリースをおすすめしたりして、ユーザーのエンゲージメントやアプリの使用時間を増大させることができます。
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- 「いいね」のカスタムイベント
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/)を作成します。
+2. \[**タイプ**] を \[**最新**] に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。
+5. \[**カスタムイベント**] を選択し、リストから「いいね」のカスタムイベントを選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングでおすすめを使用します。]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)
+
+{% enddetails %}
+
+### 最も人気のある商品
+
+購入に基づいて、ユーザーにカタログの人気アイテムを見て回るように促します。関連するコンテンツのみを表示するようにするには、選択範囲でフィルタリングすることをお勧めします。例えば、フードデリバリーサービスでは、プラットフォーム上での注文の人気度に基づいて、ユーザーの地域内で評価の高い料理やレストランを取り上げ、お試しでの使用や新規開拓を促すことができます。
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- 購入オブジェクトまたはカスタムイベント
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/)を作成します。
+2. \[**タイプ**] を \[**最も人気がある**] に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。例えば、食品配送サービスは、レストランのロケーションまたは料理のタイプをフィルタリングするための選択肢を有する。
+5. 現在のイベントのトラッキング方法と対応するイベントプロパティを選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングでおすすめを使用します。]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)
+
+{% enddetails %}
+
+### 閲覧数が上位のアイテム
+
+エンゲージメントや購入を奨励するために、ビューを通じてユーザーベース全体で注目を集めた項目を強調表示します。例えば、不動産の Web サイトでは、ユーザーの検索エリアで閲覧数が上位のリストを表示し、多くの注目を集めている物件 (お買い得物件または良好な立地の可能性が高い) を取り上げることができます。
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- ビューのカスタムイベント
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/)を作成します。
+2. \[**タイプ**] を \[**最も人気がある**] に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。
+5. \[**カスタムイベント**] を選択し、リストから表示数のカスタムイベントを選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングでおすすめを使用します。]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)
+
+{% enddetails %}
+
+### 新しいアイテム
+
+このシナリオは、ユーザーの操作に直接依存するのではなく、カタログデータに依存します。カタログに追加された日付に基づいて新しいアイテムをフィルター処理し、ターゲット設定したキャンペーンやキャンバスを通じて新しいアイテムを宣伝できます。おすすめモデルのトレーニングは不要です。
+
+例えば、技術系の e コマースプラットフォームではフィルターを使用し、カタログに最近追加されたアイテムをターゲットにして、最新のガジェットや今後の予約注文についてハイテク愛好家に通知できます。
+
+{% details 要件 %}
+
+- 日付欄が追加された関連項目のカタログ
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. カタログに基づいて選択を作成します。カタログに、アイテムが追加された日付に対応する時間フィールド (\[**データ型**] が \[**時間**] に設定されたフィールド) があることを確認します。
+2. (オプション) 必要に応じてフィルタを追加します。
+3. **Randomize Sort Order**がオフになっていることを確認します。
+4. **ソートフィールド**の場合は、日付追加フィールドを選択します。
+5. \[**順序を並べ替え**] を \[降順] に設定します。
+6. [メッセージングでセレクションを使用します。]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/#using-selections-in-messaging)
+
+{% enddetails %}
+
+### ユーザーカートの人気アイテム
+
+他の多くの買い物客がカートに追加したショーケースアイテムは、あなたのオファリングの現在のトレンドを垣間見ることができます。
+
+例えば、ファッション小売業者は、他の顧客がカートに追加した人気アイテムに基づいて、流行している服やアクセサリーを宣伝できます。その後、ホームページとモバイルアプリで動的な"Trending Now"セクションを作成し、リアルタイムで更新して、買い物客がアイテムを売り切る前に購入するよう促すことができます。
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- カートに追加のカスタムイベント
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/)を作成します。
+2. \[**タイプ**] を \[**最も人気がある**] に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。
+5. \[**カスタムイベント**] を選択し、リストから「カートに追加」のカスタムイベントを選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングでおすすめを使用します。]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)
+
+{% enddetails %}
+
+### ランダムなアイテム
+
+さまざまなユーザー体験を目的として、ランダムなアイテムをおすすめすると、充実した品揃えを紹介でき、訪問回数の少ないカタログ領域への興味を喚起できる可能性があります。このメソッドは、特定のモデルやイベントを必要とせず、カタログ選択を使用して項目がランダムに表示されるようにします。
+
+たとえば、オンライン書店では"Surprise Me"機能を提供して、ユーザーの過去の購入や閲覧習慣に基づいてランダムな本を推薦し、通常の読書ジャンル以外の探索を奨励することができます。
+
+{% details 要件 %}
+
+- 関連品目のカタログ
+- \[**並べ替え順序をランダム化**] をオンにしたセレクション
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [カタログに基づいて選択]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/#creating-a-selection)を作成します。
+2. (オプション) 必要に応じてフィルタを追加します。
+3. \[**並べ替え順序をランダム化**] をオンにします。
+4. [メッセージングでセレクションを使用します。]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/#using-selections-in-messaging)
+
+{% enddetails %}
+
+### 最近クリックしたアイテム
+
+クリックのカスタムイベントに基づいて、最近クリックした項目を再訪問するようユーザーに促します。例えば、オンライン・ファッション小売業者は、フォローアップ・メールを送信するための推薦を作成したり、ユーザが自分の関心を示した服を掲載したプッシュ通知を作成したりすることができ、ユーザがそのアイテムを再訪問し、購入することを促すことができる。
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- クリックのカスタムイベント
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/)を作成します。
+2. \[**タイプ**] を \[**最新**] に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。
+5. \[**カスタムイベント**] を選択し、リストからクリック数のカスタムイベントを選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングでおすすめを使用します。]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)
+
+{% enddetails %}
+
+### 最近エンゲージしたアイテムまたは購入したアイテム
+
+ユーザーが最近、表示、クリック、購入などの操作を行ったアイテムを宣伝します。このアプローチでは、おすすめを新鮮に保ち、ユーザーの最新の興味に合わせます。.以下に例を示します。
+
+- **教育:**オンライン教育プラットフォームでは、最近教育動画を視聴したもののコースに登録していないユーザーに対して、類似のコースや興味のある科目をチェックするように促すことで、ユーザーのエンゲージメントと学習を開始しようという意欲を維持させることができます。
+- **フィットネス:**フィットネスアプリでは、ユーザーが最近完了した、またはインタラクションを行ったものに似たワークアウトや課題を紹介することで、変化に富んだ魅力的なエクササイズルーティンをユーザーに提供し続けることができます。
+- **ホームセンター:**顧客が電動工具を購入した後に、最近の購入品に基づいて関連アクセサリーや安全用品をおすすめして、ユーザーの体験と安全性を向上できます。
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- エンゲージメントインタラクションの購入オブジェクトまたはカスタムイベント
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/)を作成します。
+2. \[**タイプ**] を \[**最新**] に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。
+5. \[**カスタムイベント**] を選択し、リストからクリック数のカスタムイベントを選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングでおすすめを使用します。]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)
+
+{% enddetails %}
+
+### 購入品の推移
+
+ユーザーが最近購入したアイテムを頻度を上げて強調表示します。たとえば、eコマース事業では、次のシーズンの準備期間中にユーザーが在庫を取り始めている季節商品を勧めることができる。 
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- 購入(購入オブジェクトまたはカスタムイベント) を追跡する方法。
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/ai_item_recommendations/)を作成します。
+2. **Type**を**Trending**に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。
+5. 購入イベントまたは購入を追跡するカスタムイベントを、対応するプロパティとともに選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングで推奨事項を使用します。]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)
+
+{% enddetails %}
+
+### 好きなアイテムのトレンド
+
+ユーザーが最近気に入った項目を、頻度を増やして強調表示します。たとえば、音楽アプリには、最近ユーザーの好きなものが急増した新進アーティストが登場する可能性がある。
+
+{% details 要件 %}
+
+- AI によるアイテムのおすすめ
+- 関連品目のカタログ
+- トラッキング用のカスタムイベント
+
+{% enddetails %}
+
+{% details 設定方法 %}
+
+1. [AI によるアイテムのおすすめ]({{site.baseurl}}/ai_item_recommendations/)を作成します。
+2. **Type**を**Trending**に設定します。
+3. カタログを選択します。
+4. (オプション) 選択を追加して、関連する項目のみにおすすめをフィルタリングします。
+5. トラッキングのいいね!のカスタムイベントを、対応するプロパティとともに選択します。
+6. 推奨事項をトレーニングします。
+7. [メッセージングで推奨事項を使用します。]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging/)
+
+{% enddetails %}
+
+[1]: {{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/
diff --git a/_lang/ja/_user_guide/brazeai/recommendations/ai_item_recommendations.md b/_lang/ja/_user_guide/brazeai/recommendations/ai_item_recommendations.md
new file mode 100644
index 00000000000..8f8411e83f0
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/recommendations/ai_item_recommendations.md
@@ -0,0 +1,328 @@
+---
+nav_title: AI 項目のレコメンデーション
+article_title: AI 項目のレコメンデーション
+page_order: 15
+alias: "/ai_item_recommendations/"
+description: "この参照記事では、カタログ内のアイテムのAI アイテム推奨を作成する方法について説明します。"
+---
+
+# AI によるアイテムのおすすめ
+
+> カタログ内のアイテムのAI アイテム推奨を作成する方法について説明します。
+
+AI 項目の推奨事項を使用して、最も人気のある製品を計算したり、特定の\[catalog]\[catalog]] に対してカスタマイズされたAI 推奨事項を作成したりします。おすすめを作成したら、パーソナライゼーションを使用してメッセージに製品を挿入できます。
+
+## 前提条件
+
+開始する前に、次の作業を完了する必要があります。
+
+- 以下に説明する推奨タイプのいずれかを使用するには、少なくとも1 つの\[catalog]\[catalog]] が必要です。
+- カタログに保存されている一意の製品ID への参照を含む、Braze (カスタムイベントまたは購入オブジェクト) の購入またはイベントデータが必要です。
+
+{% alert tip %}
+[AI パーソナライズされたおすすめ](#recommendation-types) は、数百または数千のアイテム、通常は購入またはインタラクションデータを持つ30,000 人以上のユーザーで最適に動作します。これはあくまでも目安であり、様々です。他の推奨タイプは、より少ないデータで動作できます。
+{% endalert %}
+
+## AI アイテムの推奨の作成
+
+アイテムの推奨を作成するには:
+
+1. **Analytics**> **AI Item Recommendation** に移動します。
+2. **Create Prediction**> **AI Item Recommendation**を選択します。
+
+また、個々のカタログからレコメンドストレートを作成することもできます。**Catalogs**ページからカタログを選択し、**推奨の作成**を選択します。
+
+### ステップ 1:推奨事項の詳細を追加する
+
+おすすめに名前と説明(オプション)を付けます。
+
+![][1]
+
+### ステップ 2:おすすめを定義する {#recommendation-type}
+
+推奨タイプを選択します。すべてのレコメンドタイプは、アイテムのインタラクション(購入またはカスタムイベント) データの過去6 か月間を使用します。以下で説明するインタラクションとは、購入イベントまたは[ステップ3](#step-3-select-the-interaction-to-drive-recommendations)で選択されたカスタムイベントのいずれかを指します。
+
+- **最も人気がある:**カタログから最大30 個のアイテムを計算し、ワークスペース内のすべてのユーザーが最も頻繁に(最も購入された製品など) やり取りするようにします。
+- **最新:**ユーザが最近操作した製品のリストを最大30 個作成します。
+- **AI パーソナライズ:**新しい種類のディープラーニングである変圧器を使用して、各ユーザーが次に対話する可能性の高い項目のセットを予測します。次の最も可能性の高い項目のうち、最も可能性が高い項目から最も可能性が低い項目までを30 個まで計算します。このタイプの推奨事項では、大規模な言語モデル(LLM) を使用して、データを他のBraze 顧客のデータと組み合わせることはありません。
+- **トレンド:**ユーザーインタラクションに関して、直近のプラスのモメンタムを持つワークスペースから最大30 個の項目を計算します。
+
+{% alert tip %}
+**最新の**または**AI Personalized**を使用している場合、個別の推奨事項を作成するのに十分なデータがないユーザーは、**最も人気のある**項目をフォールバックとして受け取ります。**最も人気のある**フォールバックを受信したユーザーの割合は、**Analytics**ページに表示されます。
+{% endalert %}
+
+#### ステップ 2a: 事前の購入またはやり取りを除外する(オプション)
+
+ユーザがすでに購入した、またはインタラクションしたアイテムを提案しないようにするには、**ユーザが以前に**とインタラクションしたアイテムを推奨しません。このオプションは、推奨**Type** が**AI Personalized** に設定されている場合にのみ使用できます。
+
+![]\[2-3]
+
+この設定により、ユーザがすでに購入または操作した項目をメッセージが再利用できなくなります。ただし、推奨が最近更新された場合に限ります。おすすめの更新間に購入された、またはやり取りされたアイテムがまだ表示される場合があります。アイテムレコメンドの無料バージョンでは、更新は毎週行われます。AI アイテム推奨のプロバージョンでは、更新は24 時間ごとに行われます。
+
+たとえば、AIアイテムの推奨のプロバージョンを使用する場合、ユーザーが何かを購入し、その後30分以内にマーケティングメールを受信した場合、購入したばかりのアイテムは、間に合うようにメールから除外されないことがあります。ただし、24時間後に送信されるメッセージには、その項目は含まれません。
+
+#### ステップ 2b: カタログを選択
+
+まだ入力されていない場合は、\[catalog]\[catalog] を選択します。この推奨では、アイテムを取得します。
+
+#### ステップ 2c: 選択範囲の追加(オプション)
+
+推奨事項をさらに制御したい場合は、[選択]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)を選択してカスタムフィルタを適用します。選択は、ブランド、サイズ、場所など、カタログ内の特定の列によって推奨事項をフィルタリングします。「Liquid」を含む選択は、おすすめでは使用できません。
+
+![]\[2-2]
+
+{% alert tip %}
+選択内容が見つからない場合は、最初にカタログで設定されていることを確認してください。
+{% endalert %}
+
+### ステップ 3:推奨を駆動するインタラクションを選択します
+
+この推奨を最適化するイベントを選択します。このイベントは通常、購入ですが、アイテムとのインタラクションも可能です。
+
+次のために最適化できます。
+
+- [Purchase Object]({{site.baseurl}}/api/objects_filters/purchase_object/)のイベントを購入する
+- 購入を表すカスタムイベント
+- 他のアイテムインタラクションを表すカスタムイベント(製品ビュー、クリック、メディア再生など)
+
+**カスタムイベント**を選択した場合は、リストからイベントを選択します。
+
+![][3]
+
+### ステップ 4:対応するプロパティ名を選択します {#property-name}
+
+おすすめを作成するには、インタラクションイベント(購入オブジェクトまたはカスタムイベント) のどのフィールドに、カタログ内のアイテムの`id` フィールドに一致する一意の識別子があるかをBraze に伝える必要があります。わかりませんか?[要件](#requirements)を表示します。
+
+**Property Name**でこのフィールドを選択します。
+
+**Property Name**フィールドには、SDKからブレーズに送信されるフィールドのリストが事前に入力されます。十分なデータが提供されている場合、これらのプロパティは、正しいプロパティである確率順にランク付けされます。カタログの`id` フィールドに対応するものを選択します。
+
+![][4]
+
+#### 要件
+
+プロパティを選択するには、いくつかの要件があります。
+
+- 選択したカタログの`id` フィールドにマップする必要があります。
+- **オブジェクトの購入を選択した場合:**`product_id` またはインタラクションイベントの`properties` フィールドである必要があります。
+- **カスタムイベントを選択した場合:**カスタムイベントの`properties` のフィールドである必要があります。
+- ネストされたフィールドは、`event_property.nested_property` の形式でドット表記で**Property Name** ドロップダウンに入力する必要があります。たとえば、イベントプロパティ`location` 内でネストされたプロパティ`district_name` を選択する場合は、`location.district_name` と入力します。
+- このフィールドは、1 つのイベント内の複数のカタログアイテムの配列に含めることができます。自動的に平坦化されます。
+
+#### マッピングの例
+
+以下のマッピング例は、どちらもこのサンプル・カタログを参照します。
+
+<style type="text/css">
+.tg td{word-break:normal;}
+.tg th{word-break:normal;font-size: 14px; font-weight: bold; background-color: #f4f4f7; text-transform: lowercase; color: #212123; font-family: "Sailec W00 Bold",Arial,Helvetica,sans-serif;}
+.tg .tg-0pky{border-color:inherit;text-align:left;vertical-align:top;word-break:normal}
+</style>
+<table class="tg">
+<thead>
+  <tr>
+    <th class="tg-0pky">id</th>
+    <th class="tg-0pky">名称</th>
+    <th class="tg-0pky">価格</th>
+  </tr>
+</thead>
+<tbody>
+  <tr>
+    <td class="tg-0pky">ADI-BL-7</td>
+    <td class="tg-0pky">アディダスブラックサイズ7</td>
+    <td class="tg-0pky">100.00 米ドル</td>
+  </tr>
+  <tr>
+    <td class="tg-0pky">ADI-RD-8</td>
+    <td class="tg-0pky">アディダスレッドサイズ8</td>
+    <td class="tg-0pky">100.00 米ドル</td>
+  </tr>
+  <tr>
+    <td class="tg-0pky">ADI-WH-9</td>
+    <td class="tg-0pky">アディダスホワイトサイズ9</td>
+    <td class="tg-0pky">100.00 米ドル</td>
+  </tr>
+  <tr>
+    <td class="tg-0pky">ADI-PP-10</td>
+    <td class="tg-0pky">アディダスパープルサイズ10</td>
+    <td class="tg-0pky">75.00 米ドル</td>
+  </tr>
+</tbody>
+</table>
+
+{% tabs %}
+{% tab カスタムイベント %}
+
+たとえば、カスタムイベント`added_to_cart` を使用して、顧客がチェックアウトする前に同様の製品をお勧めできるようにしましょう。イベント`added_to_cart` のイベント・プロパティーは`product_sku` です。
+
+次に、`product_sku` プロパティには、サンプルカタログの`id` 列の値の少なくとも1 つが含まれている必要があります。"ADI-BL-7"、"ADI-RD-8"、"ADI-WH-9"、または"ADI-PP-10"すべてのカタログアイテムにイベントは必要ありませんが、推奨エンジンが作業するのに十分なコンテンツを持つように、それらの一部が必要です。
+
+##### カスタムイベントオブジェクトの例
+
+このイベントには`"product_sku": "ADI-BL-7"` があり、サンプルカタログの最初の項目と一致します。
+
+```json
+{
+  "events" : [
+    {
+      "external_id" : "user1",
+      "app_id" : "your-app-id",
+      "name" : "added_to_cart",
+      "time" : "2024-07-16T19:20:30+01:00",
+      "properties" : {
+        "product_sku": "ADI-BL-7"
+      }
+    }
+  ]
+}
+```
+
+{% endtab %}
+{% tab 購入対象 %}
+
+購入オブジェクトは、購入が行われたときにAPI に渡されます。
+
+マッピングに関しては、カスタムイベントと同様に購入オブジェクトにも同様のロジックが適用されますが、購入オブジェクトの`product_id` または`properties` オブジェクトの項目を使用するか選択できます。
+
+すべてのカタログアイテムのイベントは必要ありませんが、推奨エンジンに十分なコンテンツが含まれるようにするには、これらのイベントの一部が必要です。
+
+##### 製品ID にマップされた購入オブジェクトの例
+
+このイベントには`"product_id": "ADI-BL-7` があり、カタログの最初の項目にマップされます。
+
+```json
+{
+  "purchases": [
+    {
+      "external_id": "user1",
+      "app_id": "11ae5b4b-2445-4440-a04f-bf537764c9ad",
+      "product_id": "ADI-BL-7",
+      "currency": "USD",
+      "price": 100.00,
+      "time": "2024-07-16T19:20:30+01:00",
+      "properties": {
+        "color": "black",
+        "checkout_duration": 180,
+        "size": "7",
+        "brand": "Adidas"
+      }
+    }
+  ]
+}
+```
+
+##### プロパティフィールドにマップされた購入オブジェクトの例
+
+このイベントのプロパティは`"sku": "ADI-RD-8"` で、カタログの2 番目の項目にマップされます。
+
+```json
+{
+  "purchases": [
+    {
+      "external_id": "user1",
+      "app_id": "11ae5b4b-2445-4440-a04f-bf537764c9ad",
+      "product_id": "shoes",
+      "currency": "USD",
+      "price": 100.00,
+      "time": "2024-07-16T19:20:30+01:00",
+      "properties": {
+        "sku": "ADI-RD-8",
+        "color": "red",
+        "checkout_duration": 180,
+        "size": "8",
+        "brand": "Adidas"
+      }
+    }
+  ]
+}
+```
+
+{% endtab %}
+{% endtabs %}
+
+### ステップ 5: 推奨事項をトレーニングする
+
+準備ができたら、**推奨の作成**を選択します。このプロセスは、完了までに10 分から36 時間かかることがあります。推奨事項が正常にトレーニングされるか、作成が失敗した理由の説明が表示されると、E メールの更新が表示されます。
+
+推奨事項は**Predictions** ページにあり、必要に応じて編集またはアーカイブできます。推奨は、毎月1回自動的に再試行されます。
+
+## 分析
+
+おすすめの分析を表示して、ユーザがおすすめした項目とおすすめモデルの精度を確認できます。
+
+1. **Analytics**> **Item Recommendation**に移動します。
+2. リストからおすすめを選択します。
+
+ページの上部で、精度やカバレッジなど、おすすめに関する統計を見つけることができます。
+
+![][5]
+
+これらのメトリックは、次の表で定義されます。 
+
+| 指標              | 説明 |
+| ------------------- | ---------- |
+| 精度           | モデルがユーザーが購入した次のアイテムを正しく推測した時間のパーセンテージ。精度は、特定のカタログサイズとミックスに大きく依存します。また、モデルが正しい頻度を理解するためのガイドとして使用する必要があります。<br><br>過去のテストでは、モデルが6～20%の精度で良好な性能を発揮していることがわかりました。このメトリクスは、モデルが次に再試行されるときに更新されます。  |
+| 範囲            | カタログ内の使用可能なアイテムのうち、少なくとも1 人のユーザーに推奨されるものの割合。最も人気のあるものよりも、パーソナライズされたアイテムのおすすめで、より高いアイテムカバレッジが見られることが期待できます。 |
+| レコメンデーションのタイプ | パーソナライズされた、または最新の推奨を受信するユーザの割合と、最も人気のあるアイテムのフォールバックの割合。フォールバックは、パーソナライズされた、または最新の推奨を生成するのに十分なデータがないユーザーに送信されます。 |
+{: .reset-td-br-1 .reset-td-br-2}
+
+次のセクションでは、カタログ内のアイテムの内訳を2つの列に分割して示します。
+
+- **パーソナライズされたアイテム**または**最新のアイテム:**この列には、カタログ内の各項目が、最も推奨されるユーザーの降順で表示されます。この列には、モデルによって各項目に割り当てられたユーザの数も表示されます。
+- **最も人気のある商品**この列には、カタログ内の各項目が人気の高い順に表示されます。ここでの人気とは、ユーザーがワークスペース全体で最も頻繁に操作するカタログ内の項目を指します。パーソナライズされた場合や、個々のユーザに対して最新の計算ができない場合に、フォールバックとして使用されます。
+
+![][6]
+
+**おすすめ概要**には、おすすめが最後に更新された日時など、選択したおすすめ設定の概要が表示されます。
+
+![][7]{: style="max-width:45%" }
+
+## メッセージングでの推奨事項の使用
+
+![][10]{: style="max-width:30%;float:right;margin-left:15px;"}
+
+おすすめがトレーニングを終了したら、Liquidでメッセージをカスタマイズして、そのカタログで最も人気のある製品を挿入できます。リキッドは、メッセージコンポーザーのパーソナライゼーションウィンドウで生成できます。
+
+1. パーソナライゼーションをサポートするメッセージコンポーザーでは、<i class="fa-solid fa-circle-plus" style="color: #12aec5;" title="パーソナライゼーションを追加"></i>を選択してパーソナライゼーションウィンドウを開きます。
+2. **Personalization Type** では、**Item Recommendation** を選択します。
+3. **Item Recommendation Name**の場合は、作成した推奨を選択します。
+4. **Number of Predicted Items**には、挿入したい上位製品の数を入力します。たとえば、購入数の多い上位3 つのアイテムを表示できます。
+5. **Information to Display**では、カタログのどのフィールドを各アイテムに含めるかを選択します。各アイテムのこれらのフィールドの値は、この推奨に関連付けられたカタログから取得されます。
+6. **Copy**アイコンを選択し、メッセージ内の必要な場所に液体を貼り付けます。
+
+## AI 項目の推奨階層
+
+次の表に、AI Personalized、Popular、およびTrending 推奨タイプの無償バージョンとプロバージョンの違いを示します。
+
+| エリア                   | 無料版                          | Proバージョン            |
+| :---------------------- | ------------------------------------- | :--------------------------------------- |
+| ユーザ更新頻度<sup>1</sup>   | 毎週                                | 毎日                                    |
+| モデル再訓練回数  | 毎月                               | 毎月                                   |
+| 最大推奨値 | タイプごとに1つの推奨事項<sup>1</sup> | タイプごとに 100 の推奨事項 <sup>2</sup> |
+
+<sup>1. これは、ユーザ固有の項目の推奨事項が更新される頻度です(ほとんどの一般的な項目を除くすべてのモデル。モデルが再試行されると更新されます)。たとえば、ユーザーがAI アイテムの推奨に基づいてアイテムを購入した場合、その推奨アイテムはこの頻度に従って更新されます</sup>
+<sup>2\.利用可能なレコメンドタイプは、AI パーソナライズ、最新、最も一般的、および傾向です。</sup>
+
+## よくある質問
+
+### " 最も人気のある" 項目が他のモデルの推奨事項に混在する原因は何ですか?
+
+推奨エンジンがリストをキュレーションすると、まず"Most lanced"または"AI Personalized"のように、選択した特定のモデルに基づいてパーソナライズされた選択が優先されます。このモデルが、何らかの理由で30の推奨事項の完全なリストを満たすことができない場合、すべてのユーザーの中で最も人気のある項目の一部が追加され、各ユーザーが常に完全な推奨事項を持っていることを確認します。
+
+これは、いくつかの特定の条件下で発生します。
+
+- このモデルでは、条件に一致する項目が30 個未満検出されます。
+- 関連する品目は、もはや入手できず、在庫にありません。
+- 品目は現在の選択基準を満たしていません。おそらく、在庫やユーザーの好みの変更によるものです。
+
+[1]: {% image_buster /assets/img/item_recs_1.png %}
+\[2-1]: {% image_buster /assets/img/item_recs_2-1.png %}
+\[2-2]: {% image_buster /assets/img/item_recs_2-2.png %}
+\[2-3]: {% image_buster /assets/img/item_recs_2-3.png %}
+[3]: {% image_buster /assets/img/item_recs_3.png %}
+[4]: {% image_buster /assets/img/item_recs_4.png %}
+[5]: {% image_buster /assets/img/item_recs_analytics_1.png %}
+[6]: {% image_buster /assets/img/item_recs_analytics_2.png %}
+[7]: {% image_buster /assets/img/item_recs_analytics_3.png %}
+[10]: {% image_buster /assets/img/add_personalization.png %}
+\[catalog]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/
diff --git a/_lang/ja/_user_guide/brazeai/recommendations/rules_based_recommendations.md b/_lang/ja/_user_guide/brazeai/recommendations/rules_based_recommendations.md
new file mode 100644
index 00000000000..6b5e196664e
--- /dev/null
+++ b/_lang/ja/_user_guide/brazeai/recommendations/rules_based_recommendations.md
@@ -0,0 +1,283 @@
+---
+nav_title: ルールに基づく推薦
+article_title: ルールに基づく推薦
+page_type: tutorial
+page_order: 16
+alias: "/rules_based_recommendations/"
+description: "この記事では、カタログやコネクテッドコンテンツを使用したルールベースのレコメンデーションエンジンの作成方法について概説する。"
+tool:
+  - Campaigns
+  - Canvas
+
+---
+
+# ルールに基づく推奨
+
+> ルールベースのレコメンデーションエンジンは、ユーザーデータと商品情報を使って、メッセージング内でユーザーに関連アイテムを提案する。[Liquidと]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/)Braze[カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/)または[コネクテッドコンテンツを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/)使用し、ユーザーの行動や属性に基づいてダイナミックなパーソナライゼーションを行う。
+
+Liquid、カタログ、コネクテッドコンテンツの詳細については、Brazeラーニングコースをチェック：
+
+- [メールによるパーソナライズされたおすすめ](https://learning.braze.com/personalized-recommendations-with-email)
+- [Liquid によるダイナミックパーソナライゼーション](https://learning.braze.com/path/dynamic-personalization-with-liquid)
+- [コネクテッドコンテンツの基礎](https://learning.braze.com/path/dynamic-personalization-with-liquid/connected-content-fundamentals)
+
+{% alert important %}
+ルールに基づいた推奨は、手動で設定しなければならない固定ロジックに基づいている。つまり、ロジックを更新しない限り、ユーザーの購入履歴や嗜好に合わせてレコメンドが調整されないということだ。<br><br>AI によりパーソナライズされたおすすめ (ユーザーの履歴に合わせて自動的に調整される) を作成するには、「[AI によるアイテムのおすすめ]({{site.baseurl}}/user_guide/brazeai/recommendations/ai_item_recommendations/)」を参照してください。
+{% endalert %}
+
+## カタログレコメンデーションエンジンの開発
+
+1. 製品の[カタログを作成]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/)します。
+2. 各製品について、推奨製品のリストをデリミタ（パイプのようなもの`|` ）で区切った文字列として、"product_recommendations "という名前のカラムに追加する。
+3. カタログにおすすめを探したい製品IDを渡す。
+4. そのカタログアイテムの `product_recommendations` 値を取得し、Liquid の分割フィルターを使用して区切り記号で区切ります。
+5. それらの 1 つ以上の ID をカタログに渡して、他の製品の詳細を収集します。
+
+### カタログのユースケース
+
+例えば、あなたが健康食品のアプリを持っていて、ユーザーがアプリに登録した期間に応じて異なるレシピを送るコンテンツカードキャンペーンを作りたいとしよう。 
+
+1. 以下の情報を含むカタログをCSVで作成し、アップロードする：<br>- **id:**ユーザーがアプリに登録してからの日数に関連する一意の数字。例えば、`3` は3日間に相当する。<br>**タイプ:** `comfort` 、`fresh` などのレシピカテゴリーがある。<br>**タイトル:** 各 ID に送信されるコンテンツカードのタイトル。「今週のランチ用の作り置き」や「タコスについて話そう」などです。<br>**リンク:** レシピ記事へのリンク。<br>- **image_url:** レシピに対応する画像, 写真。
+
+{: start="2"}
+2\.カタログが Braze にアップロードされた後、カタログアイテムの一部のプレビューを確認して、情報が正確にインポートされたことを確認してください。プレビューでは項目がランダムになっているかもしれないが、レコメンデーションエンジンの出力には影響しない。
+
+![][1]
+
+{: start="3"}
+3\.コンテンツカードキャンペーンを作成する。作成画面で、キャンペーンの送信先のユーザー、および表示するレシピと画像を決定する Liquid ロジックを入力します。このユースケースで、Braze はユーザーの `start_date` (または登録日) を取得し、現在の日付と比較します。日数の違いによって、送信されるコンテンツカードが決まります。 
+
+![][2]
+
+**Title:**
+
+{% raw %}
+```liquid
+{% assign start_date = {{custom_attribute.${start_date}}} | date: "%s" %}
+{% assign current_date = "now" | date: "%s" %}
+{% assign diff = {{current_date}} | minus: {{start_date}} | divided_by: 86400 %}
+{% assign days = {{diff}} | round %}
+{% catalog_items Healthy_Recipe_Catalog_SMB {{days}} %}
+{{ items[0].title }}
+```
+{% endraw %}
+
+**メッセージ:**
+
+{% raw %}
+```liquid
+{% assign start_date = {{custom_attribute.${start_date}}} | date: "%s" %}
+{% assign current_date = "now" | date: "%s" %}
+{% assign diff = {{current_date}} | minus: {{start_date}} | divided_by: 86400 %}
+{% assign days = {{diff}} | round %}
+{% catalog_items Healthy_Recipe_Catalog_SMB {{days}} %}
+{% if items[0].title != blank %}
+{{ items[0].body }}
+{% else %}
+{% abort_message('no card for today') %}
+{% endif %}
+```
+{% endraw %}
+
+**画像：**
+
+{% raw %}
+```liquid
+{% assign start_date = {{custom_attribute.${start_date}}} | date: "%s" %}
+{% assign current_date = "now" | date: "%s" %}
+{% assign diff = {{current_date}} | minus: {{start_date}} | divided_by: 86400 %}
+{% assign days = {{diff}} | round %}
+{% catalog_items Healthy_Recipe_Catalog_SMB {{days}} %}
+{{ items[0].image_url }}
+```
+{% endraw %}
+
+{: start="4"}
+4\.**On click behavior**セクションで、iOS、Android、Webデバイスでユーザーがコンテンツカードをクリックしたときに、どこにリダイレクトされるべきかのLiquidロジックを入力する。 
+
+{% raw %}
+```liquid
+{% assign start_date = {{custom_attribute.${start_date}}} | date: "%s" %}
+{% assign current_date = "now" | date: "%s" %}
+{% assign diff = {{current_date}} | minus: {{start_date}} | divided_by: 86400 %}
+{% assign days = {{diff}} | round %}
+{% catalog_items Healthy_Recipe_Catalog_SMB {{days}} %}
+{{ items[0].link }}
+```
+{% endraw %}
+
+![][3]{: style="max-width:60%;"}<br><br>
+
+{: start="5"}
+5\.**テスト」**タブに移動し、「**ユーザーとしてメッセージをプレビュー**」で**「カスタムユーザー**」を選択する。**カスタム属性**フィールドに日付を入力し、その日にサインアップしたユーザーに送信されるコンテンツカードをプレビューする。<br><br>
+
+![][4]
+
+## コネクテッド・コンテンツ・レコメンデーションエンジンの開発
+
+1. 以下のいずれかの方法でコネクテッド・コンテンツ・エンドポイントを作成する：
+- SheetDPのようなサービスを使って、スプレッドシートをJSON APIエンドポイントに変換する。
+- カスタムビルドの社内エンドポイントを構築し、ホストおよびメンテナンスを行います。
+- [Amazon Personalise]({{site.baseurl}}/partners/message_personalization/dynamic_content/amazon_personalize/)、[Certona]({{site.baseurl}}/partners/message_personalization/dynamic_content/certona/)、[Dynamic Yieldなどの]({{site.baseurl}}/partners/message_personalization/dynamic_content/dynamic_yield/) [Alloysパートナーなどの]({{site.baseurl}}/partners/message_personalization/dynamic_content/)サードパーティパートナー経由でレコメンデーションエンジンを購入する。
+
+2. コネクテッドコンテンツLiquidをメッセージボディまたはコンテンツブロックHTMLエディタに記述し、エンドポイントを呼び出してデータベースを検索する。
+3. ユーザープロファイルで見つけたカスタム属性の値でLiquidを整列させる。
+4. 結果的に正しい推薦を引き出せた。
+
+{% raw %}
+```
+{% connected_content YOUR-API-URL :save items %}
+
+{% assign recommended_item_ids_from_user_profile = custom_attribute.${RECOMMENDED_ITEM_IDS} | split: ';' %}
+
+{% for item_id in recommended_item_ids_from_user_profile %}
+  {% assign recommended_item = items | where: "ITEM_ID", ITEM_ID | first %}
+  recommended_item.item_name
+{% endfor %}
+```
+{% endraw %}
+
+| 属性 | 交換 |
+| --- | --- |
+|`YOUR-API-URL` | 実際のAPIのURLに置き換える。 |
+|`RECOMMENDED_ITEM_IDS` | 推奨アイテムのIDを含むカスタム属性の実際の名前に置き換える。この属性は、セミコロンで区切られたIDの文字列であることが期待される。 |
+|`ITEM_ID` | アイテムIDに対応するAPIレスポンスの実際の属性名に置き換える。 |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{% alert note %}
+これは基本的な例であり、特定のニーズやデータ構造に基づいてさらに修正する必要があるかもしれない。詳細なガイダンスについては、[Liquid のドキュメント]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/)を参照するか、開発者に相談してください。
+{% endalert %}
+
+## コネクテッド・コンテンツのユースケース
+
+例えば、Zomato Restaurantsデータベースからお勧めのレストランを取得し、その結果を`restaurants` という内部変数として保存したいとしよう。次のコネクテッドコンテンツの呼び出しができます。
+
+{% raw %}
+```liquid
+
+{% connected_content https://developers.zomato.com/api/v2.1/search?entity_id={{city_id}}&entity_type=city&count=20&cuisines={{food_type}}&sort=rating:headers{“user-key”:“USER_KEY”} :save restaurants %}
+
+{{city_food.restaurants[0]}}
+```
+{% endraw %}
+
+次に、ユーザーの市区町村と食べ物の種類に基づいて、お勧めのレストランを引き出したいとしよう。ユーザーの市区町村と料理の種類のカスタム属性を呼び出しの冒頭にダイナミックに挿入し、`restaurants` の値を変数 `city_food.restaurants` に代入することで、これを行うことができます。
+
+コネクテッド・コンテンツの呼び出しは次のようになる：
+
+{% raw %}
+```liquid
+{% assign city_id = {{custom_attribute.${city_id} | default: ‘306’}} %}
+{% assign food_type = {{custom_attribute.${food_type} | default: ‘471’}} %}
+
+{%- connected_content https://developers.zomato.com/api/v2.1/search?entity_id={{city_id}}&entity_type=city&count=20&cuisines={{food_type}}&sort=rating:headers{“user-key”:“USER_KEY”} :save restaurants %}
+
+{% assign restaurants = city_food.restaurants %}
+
+{{city_food.restaurants[0]}}
+```
+{% endraw %}
+
+レストラン名と評価だけを取得するようにレスポンスを調整したい場合は、次のようにフィルターを呼び出しの最後に追加することができる：
+
+{% raw %}
+```liquid
+{% assign city_id = {{custom_attribute.${city_id} | default: ‘306’}} %}
+{% assign food_type = {{custom_attribute.${food_type} | default: ‘471’}} %}
+
+{%- connected_content https://developers.zomato.com/api/v2.1/search?entity_id={{city_id}}&entity_type=city&count=20&cuisines={{food_type}}&sort=rating:headers{“user-key”:”USER_KEY”} :save restaurants %}
+{% assign restaurants = city_food.restaurants %}
+
+{{city_food.restaurants[0].restaurant.name}}
+{{city_food.restaurants[0].restaurant.user_rating.rating_text}}
+```
+{% endraw %}
+
+最後に、お勧めのレストランを評価別にまとめたいとしよう。次の手順を実行します。
+
+1. `assign` 、「素晴らしい」、「非常に良い」、「良い」の評価カテゴリー用の空白の配列を作成する。
+2. `for` 、リスト内の各レストランの評価を調べるループを追加する。 
+- 評価が「優れている」場合は、レストラン名を `excellent_restaurants` 文字列の後に追加し、各レストラン名を区切る * 文字を最後に追加します。 
+- 評価が "Very Good "の場合、`very_good_restaurants` の文字列にレストラン名を追加し、最後に*を追加する。
+- 評価が "Good "の場合、`good_restaurants` の文字列にレストラン名を追加し、最後に*を追加する。
+3. 返されるおすすめレストランの数を各カテゴリで 4 店に制限します。
+
+最終的な呼び出しは次のようになります。
+
+{% raw %}
+```liquid
+{% assign city_id = {{custom_attribute.${city_id} | default: ‘306’}} %}
+{% assign food_type = {{custom_attribute.${food_type} | default: ‘471’}} %}
+{%- connected_content https://developers.zomato.com/api/v2.1/search?entity_id={{city_id}}&entity_type=city&count=20&cuisines={{food_type}}&sort=rating:headers{“user-key”:”USER_KEY”} :save restaurants %}
+{% assign restaurants = city_food.restaurants %}
+{% assign excellent_restaurants = “” %}
+{% assign very_good_resturants = “” %}
+{% assign good_restaurants = “” %}
+{% for list in restaurants %}
+{% if {{list.restaurant.user_rating.rating_text}} == `Excellent` %}
+{% assign excellent_restaurants = excellent_restaurants | append: list.restaurant.name | append: `*` %}
+{% elseif {{list.restaurant.user_rating.rating_text}} == `Very Good` %}
+{% assign very_good_restaurants = very_good_restaurants | append: list.restaurant.name | append: `*` %}
+{% elseif {{list.restaurant.user_rating.rating_text}} == `Good` %}
+{% assign good_restaurants = good_restaurants | append: list.restaurant.name | append: `*` %}
+{% endif %}
+{% endfor %}
+{% assign excellent_array = excellent_restaurants | split: `*` %}
+{% assign very_good_array = very_good_restaurants | split: `*` %}
+{% assign good_array = good_restaurants | split: `*` %}
+
+Excellent places
+{% for list in excellent_array %}
+
+{{list}}
+{% assign total_count = total_count | plus:1 %}
+{% if total_count >= 4 %}
+{% break %}
+{% endif %}
+{% endfor %}
+
+Very good places
+{% for list in very_good_array %}
+
+{{list}}
+{% assign total_count = total_count | plus:1 %}
+{% if total_count >= 4 %}
+{% break %}
+{% endif %}
+{% endfor %}
+
+Good places
+{% for list in good_array %}
+
+{{list}}
+{% assign total_count = total_count | plus:1 %}
+{% if total_count >= 4 %}
+{% break %}
+{% endif %}
+{% endfor %}
+```
+{% endraw %}
+
+ユーザー端末でのレスポンシブの表示例については、以下のスクリーンショットを参照のこと。
+
+![][5]{: style="max-width:30%;"}
+
+## 考慮事項
+
+どのレコメンデーションエンジンが、あなたの利用可能なリソースやユースケースに適しているかを決める際には、この検討表を参考にしてほしい：
+
+| 考慮事項 | Liquid | カタログCSV | カタログ API | コネクテッドコンテンツ |
+| --- | --- | --- | --- | --- |
+| データポイントを消費しない | サポートされていない | 対応 | 対応 | 対応 |
+| コードソリューションなし | サポートされていない | Liquid 事前生成されている場合にサポートされる | サポートされていない | サポートされていない |
+| 多くの場合、高度な Liquid が必要 | 対応 | サポートされていない | サポートされていない | 対応 |
+| 製品フィードのデータ更新 | サポートされていない | 推奨事項が頻繁に更新されない場合はサポートされる | 推奨事項が1時間ごとに更新される場合はサポートされる | サポートされており、おすすめがリアルタイムまで更新される |
+| Braze UI内で推薦文を生成する | 対応 | 対応 | 対応 | Braze以外で生成された場合はサポートされない。 |
+| 推奨データのホスティング、マネージャー、トラブルシューティングがない | 対応 | 対応 | 対応 | サポートされていない |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+[1]: {% image_buster /assets/img/recs/catalog_items.png %}
+[2]: {% image_buster /assets/img/recs/content_card_preview.png %}
+[3]: {% image_buster /assets/img/recs/on_click_behavior.png %}
+[4]: {% image_buster /assets/img/recs/custom_attributes_test.png %}
+[5]: {% image_buster /assets/img/recs/sample_response.png %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/create.md b/_lang/ja/_user_guide/create.md
deleted file mode 100644
index a5264320723..00000000000
--- a/_lang/ja/_user_guide/create.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-nav_title: LINE メッセージの作成
-article_title: LINE メッセージの作成
-page_order: 1
-description: "この記事では、LINE メッセージのキャンペーンまたはキャンバスを作成する方法について説明します。"
-page_type: reference
-tool:
- - Campaigns
-channel:
- - LINE
-hidden: true
-permalink: /line/create/
----
-
-# LINE メッセージの作成
-
-> LINE キャンペーンは、顧客に直接配信され、プログラムでチャットできます。Liquid などのダイナミックコンテンツを使用して、ユーザー一人ひとりに合わせた体験を作り出し、控えめなブランド体験を強化する環境を作ることができます。<br><br>この記事は LINE ベータ版コレクションの一部です。[メインページに戻ります](https://www.braze.com/docs/line/)。
-
-{% alert important %}
-LINE アクセスはベータ版であり、一部の Braze パッケージでのみ利用できます。利用を始めるには、アカウントマネージャーまたはカスタマーサクセスマネージャーにお問い合わせください。
-{% endalert %}
-
-## 前提条件
-
-LINE メッセージを作成する前に、次の手順を実行します。
-
-1. LINE の概要を読みます。
-2. ポリシー、制限、コンテンツルールを確認します。
-3. [LINE への接続を設定します]({{site.basesurl}}/user_guide/message_building_by_channel/line/line_setup/)。
-
-
-## ステップ 1:メッセージを作成する場所を選択する
-
-メッセージは、キャンペーンとキャンバスのどちらを使用して配信すべきでしょうか。キャンペーンは単一のシンプルなメッセージングキャンペーンに適していますが、キャンバスはマルチステップのユーザーのジャーニーに適しています。
-
-{% tabs %}
-{% tab キャンペーン %}
-
-**ステップ:**
-
-1. \[**メッセージング**] > \[**キャンペーン**] の順に進み、\[**キャンペーンを作成**] を選択します。
-{% alert note %}
-[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**エンゲージメント**] の下に \[**キャンペーン**] が表示されます。
-{% endalert %}
-
-{: start="2"}
-2\.\[**LINE**] を選択するか、マルチチャネルをターゲットとするキャンペーンでは、\[**マルチチャネルキャンペーン**] を選択します。
-3\.キャンペーンに、明確で意味のある名前を付けます。
-4\.必要に応じて、\[[チーム]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/teams/)] と \[[タグ]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/)] を追加します。
-   * タグを使用すると、キャンペーンを検索してレポートを作成しやすくなります。例えば、\[[レポートビルダー]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/)] を使用する場合、特定のタグでフィルターできます。
-5. キャンペーンに必要な数だけバリアントを追加して名前を付けます。追加したバリアントごとに、さまざまなプラットフォーム、メッセージタイプ、レイアウトを選択できます。このトピックの詳細については、「[多変量テストと AB テスト]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/)」を参照してください。
-6. \[[サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/)] を選択して、適切なユーザーに送信していることを確認します。サブスクリプショングループを選択すると、Braze によって自動的にセグメンテーションフィルターが追加され、配信登録済みのユーザーのみがキャンペーンを受信できるようになります。そのサブスクリプショングループに属する長いコードと短いコードのみが、SMS を対象ユーザーに送信するために使用されます。
-
-{% alert tip %}
-キャンペーン内のすべてのメッセージが類似しているか、同じ内容になる場合は、メッセージを作成してからバリアントを追加します。その後、\[**バリアントを追加**] ドロップダウンから \[**バリアントをコピー**] を選択できます。
-{% endalert %}
-
-{% endtab %}
-{% tab キャンバス %}
-
-**ステップ:**
-
-1. キャンバス作成ツールを使用して \[[キャンバスを作成]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)] します。
-2. キャンバスを設定したら、キャンバスビルダーにステップを追加します。ステップに、明確で意味のある名前を付けます。
-3. \[[ステップスケジュール]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/time_based_canvas/#schedule-delay)] を選択し、必要に応じて遅延を指定します。
-4. 必要に応じて、このステップのオーディエンスをフィルターします。セグメントを指定し、フィルターを追加して、このステップの受信者をさらに絞り込むことができます。後から、メッセージの送信時に、オーディエンスオプションがチェックされます。
-5. \[[昇進動作]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/advancement/)] を選択します。
-6. メッセージと組み合わせる他のメッセージングチャネルを選択します。
-
-{% endtab %}
-{% endtabs %}
-
-## ステップ 2:LINE メッセージを作成する
-
-必要に応じて、言語とパーソナライゼーション (Liquid またはコネクテッドコンテンツなど) を使用してメッセージを作成します。LINE では、メッセージごとに最大 5 つのメッセージバブルが許可されます。これは、テキストメッセージまたは画像メッセージになります。
-
-![プレビューにメッセージが表示された LINE コンポーザー。][1]{: style="max-width:70%;"}
-
-{% alert tip %}
-Liquid を使用する場合は、必ずパーソナライゼーションのデフォルト値を含めてください。これにより、不完全なユーザープロファイルを持つ受信者が空のプレースホルダーを受信しないようにできます。例えば、ユーザーは、メッセージ「様」を受信する代わりに、メッセージ「新規に配信登録をいただいたお客様へ」を受信できます。
-{% endalert %}
-
-## ステップ 3:メッセージをプレビューしてテストする
-
-\[**テスト**] タブに切り替えて、コンテンツテストグループまたは個々のユーザーにテスト用の LINE メッセージを送信するか、ユーザーとしてメッセージを Braze で直接プレビューします。
-
-![\[テスト] タブには、テストメッセージのプレビューが表示されます。][2]
-
-## ステップ 4:キャンペーンまたはキャンバスの残りの部分を作成する
-
-{% tabs %}
-{% tab キャンペーン %}
-
-キャンペーンの残りの部分を作成します。ツールを最適に使用して LINE メッセージを作成する方法の詳細については、次のセクションを参照してください。
-
-### 配信スケジュールまたはトリガーを選択する
-
-LINE メッセージは、スケジュールされた時刻、アクション、または API トリガーに基づいて配信できます。スケジュールとトリガーの詳細については、「[キャンペーンのスケジュール設定]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/)」を参照してください。
-
-配信コントロールを指定できます。たとえば、ユーザーを[再有効化]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/#campaigns)してキャンペーンを受信できるようにしたり、[フリークエンシーキャップ]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)ルールを有効にしたりできます。アクションベースの配信では、キャンペーンの継続時間と \[[サイレント時間]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign/#quiet-hours)] を設定することもできます。
-
-### ターゲットとするユーザーを選択する
-
-セグメントまたはフィルターを選択して \[[ユーザーをターゲットに設定]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)] し、オーディエンスを絞り込みます。すでにサブスクリプショングループを選択しているため、ユーザーがブランドと希望するコミュニケーションの程度やカテゴリによって、ユーザーが絞り込まれます。 
-
-セグメントから大きなオーディエンスを選択し、必要に応じて[フィルター]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/)でさらにセグメントを絞り込みます。セグメントのおおよその人数について現在の状態を示すスナップショットが自動的に表示されます。正確なセグメントメンバーシップは常にメッセージが送信される直前に計算されることに注意してください。
-
-### コンバージョンイベントを選択する
-
-Braze では、キャンペーンを受信した後、ユーザーが指定のアクションや[コンバージョンイベント]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/conversion_events/)を実行する頻度を追跡できます。ユーザーが指定したアクションを実行した場合にコンバージョンがカウントされる期間は、最大 30 日間まで設定できます。
-
-コンバージョンイベントにより、キャンペーンの成否を測定できます。以下に例を示します。
-
-- ジオターゲティングを使用して、購入を行うユーザーの最終目標を持つ LINE メッセージをトリガーする場合は、コンバージョンイベントを `Purchase` に設定します。
-- ユーザーをアプリに誘導しようとする場合は、コンバージョンイベントを `Starts Session` に設定します。
-
-独自のユースケースに基づいて、カスタムコンバージョンイベントを設定することもできます。このキャンペーンの成功を測定する方法について独創的に考えてみましょう。
-
-{% endtab %}
-{% tab キャンバス %}
-
-まだキャンバスの残りのセクションを完了していない場合は、完了します。キャンバスの残りの部分を作成する方法の詳細については、多変量テストとインテリジェントセレクションを使用してください。詳しくは、「[キャンバスの作成](/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)」を参照してください。
-
-{% endtab %}
-{% endtabs %}
-
-## ステップ 5: レビューと展開
-
-キャンペーンまたはキャンバスの最後の部分の作成が完了したら、その詳細を確認し、テストしてから送信してください。
-
-次に、[LINE レポート](https://www.braze.com/docs/line/reporting/)をチェックして、LINE キャンペーンの結果にアクセスする方法を確認します。
-
-
-[1]: {% image_buster /assets/img/line/line_composer.png %}
-[2]: {% image_buster /assets/img/line/test_preview.png %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/data_and_analytics/analytics/home_dashboard.md b/_lang/ja/_user_guide/data_and_analytics/analytics/home_dashboard.md
index af9a4617ec5..f1daa4b24a1 100644
--- a/_lang/ja/_user_guide/data_and_analytics/analytics/home_dashboard.md
+++ b/_lang/ja/_user_guide/data_and_analytics/analytics/home_dashboard.md
@@ -19,7 +19,7 @@ tool:
 [古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、これは \[**概要**] ページです。
 {% endalert %}
 
-![ブレイズのホームダッシュボード][1]
+![Braze のホームダッシュボード][1]
 
 ## ダッシュボードの読み取り
 
@@ -37,17 +37,17 @@ tool:
 
 ダッシュボード統計の各行で \[**内訳を表示**] をクリックすると、指定した日付範囲の 1 日あたりの各統計値が表示されます。
 
-![拡大する][2]
+![展開][2]
 
 ## 利用可能な統計値
 
 ここでは、これらの統計値の定義、計算方法、統計値が重要な理由を示します。
 
-### ユーザー数
+### ユーザー
 
 *ユーザー数*とは、そのワークスペースで作成されたユーザーの総数です。これには、ある時点でアプリや Web サイトを使用したことが記録されたすべてのユーザーと、特定のアプリや Web サイトとは無関係のユーザーも含まれます。この数値は、生涯ユーザー数のうち、*1 か月あたりのアクティブユーザー* (MAU) として表される人数の割合であり、長期にわたるユーザーリテンションを確認するときに便利です。
 
-ユーザー数に対する MAU の割合が低い場合は、メッセージングチャネルを多様化するか、離脱ユーザーへの接触を強化する必要があることを示している可能性があります。詳しくは、\[周回遅れのユーザーをキャプチャする]][3] のクイックウィンを参照のこと。一般的に、MAU 対生涯ユーザー数の比は、ユーザーの解約により時間の経過とともに必然的に減少しますが、Braze のツールは、ユーザーのエンゲージメントをより長く維持することで、この影響を最小限に抑える役に立ちます。
+ユーザー数に対する MAU の割合が低い場合は、メッセージングチャネルを多様化するか、離脱ユーザーへの接触を強化する必要があることを示している可能性があります。詳細については、\[離脱ユーザーの収集]][3] に関するクイックウィンを参照してください。一般的に、MAU 対生涯ユーザー数の比は、ユーザーの解約により時間の経過とともに必然的に減少しますが、Braze のツールは、ユーザーのエンゲージメントをより長く維持することで、この影響を最小限に抑える役に立ちます。
 
 ### 生涯セッション数
 
diff --git a/_lang/ja/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md b/_lang/ja/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md
index e29fea3a2e1..7e11ed8abfb 100644
--- a/_lang/ja/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md
+++ b/_lang/ja/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md
@@ -30,7 +30,7 @@ search_rank: 7
 | --- | --- |
 | iOS | `ios` |
 | Android | `android` |
-| ファイヤーTV | `kindle` |
+| FireTV | `kindle` |
 | Kindle | `kindle` |
 | Web | `web` |
 | tvOS | `tvos` |
@@ -40,7 +40,7 @@ search_rank: 7
 {% enddetails %}
 
 {% alert important %}
-ストレージスキーマは、データウェアハウスパートナー（Google Cloud Storage、Amazon S3、Microsoft Azure Blob Storage）に送信するフラットファイルイベントデータに適用されます。いくつかのイベントと送信先の組み合わせは、まだ一般的に利用できません。さまざまなパートナーがサポートするイベントの情報については、[利用可能なパートナー]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/available_partners/)のリストを参照し、それぞれのページを確認してください。<br><br>さらに、Currents は 900 KB 超の過度に大きいペイロードを持つイベントをドロップすることに注意してください。
+ストレージスキーマは、データウェアハウスパートナー（Google Cloud Storage、Amazon S3、Microsoft Azure Blob Storage）に送信するフラットファイルイベントデータに適用されます。ここにリストされているいくつかのイベントと宛先の組み合わせは、まだ一般的には利用できません。さまざまなパートナーがサポートするイベントの情報については、[利用可能なパートナー]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/available_partners/)のリストを参照し、それぞれのページを確認してください。<br><br>さらに、Currents は 900 KB 超の過度に大きいペイロードを持つイベントをドロップすることに注意してください。
 {% endalert %}
 {% api %}
 
@@ -427,7 +427,7 @@ search_rank: 7
 セッション
 {% endapitags %}
 
-このイベントは、ユーザーがセッションを開始したときに発生します。このデータを使用して、ユーザーがセッションを開始した時点を追跡します。
+このイベントは、ユーザーがセッションを開始したときに発生します。このデータを使用して、ユーザーがいつセッションを開始したかを追跡します。
 
 {% alert tip %}
 ユーザーが最初のセッションを開始すると、`FirstSession` イベントと `SessionStart` イベントの両方がトリガーされます。
@@ -900,7 +900,7 @@ search_rank: 7
 {% endtabs %}
 
 {% alert important %}
-このCurrentsイベントは、「すべてのイベントコネクタ」を購入した顧客のみが利用可能であり、ストレージイベントコネクタ（i.e Amazon S3、Microsoft Azure、Google Cloud Storage）のみで利用可能です。
+この Currents イベントは「すべてのイベントコネクター」を購入した場合にのみ利用でき、ストレージイベントコネクター (i.e Amazon S3、Microsoft Azure、Google Cloud Storage) についてのみ利用できることに注意してください。
 <br><br>このイベントを有効にして、ワークスペース内の既存ユーザーのランダムバケット番号の埋め戻しをスケジュールする方法については、カスタマーサクセスマネージャーにお問い合わせください。
 {% endalert %}
 
diff --git a/_lang/ja/_user_guide/data_and_analytics/cloud_ingestion/overview.md b/_lang/ja/_user_guide/data_and_analytics/cloud_ingestion/overview.md
index ba10156d4c2..33647383e21 100644
--- a/_lang/ja/_user_guide/data_and_analytics/cloud_ingestion/overview.md
+++ b/_lang/ja/_user_guide/data_and_analytics/cloud_ingestion/overview.md
@@ -50,7 +50,7 @@ Braze のクラウドデータ取り込み (CDI) では、データウェアハ
 
 データウェアハウスで、次のユーザーと属性をテーブルに追加し、`UPDATED_AT` の時間をこのデータを追加する時間に設定します。
 
-| 更新日 | 外部ID | PAYLOAD |
+| UPDATED_AT | EXTERNAL_ID | PAYLOAD |
 | --- | --- | --- |
 | `2022-07-19 09:07:23` | `customer_1234` | {<br>    "attribute_1":"abcdefg",<br>    "attribute_2": {<br>        "attribute_a":"example_value_2",<br>        "attribute_b":"example_value_2"<br>    },<br>    "attribute_3":"2019-07-16T19:20:30+1:00"<br>} |
 | `2022-07-19 09:07:23` | `customer_3456` | {<br>    "attribute_1":"abcdefg",<br>    "attribute_2":42,<br>    "attribute_3":"2019-07-16T19:20:30+1:00",<br>    "attribute_5":"testing"<br>} |
@@ -173,7 +173,7 @@ FROM EXAMPLE_DATA;
 
 このデータはどれも Braze に同期されていないため、CDI のソーステーブルにすべて追加されます。
 
-| 更新日          | 外部ID | PAYLOAD                                                                                   |
+| UPDATED_AT          | EXTERNAL_ID | PAYLOAD                                                                                   |
 | :------------------ | ----------- | ----------------------------------------------------------------------------------------- |
 | 2023-03-16 15:00:00 | 12345       | { "ATTRIBUTE_1": "823", "ATTRIBUTE_2":"blue", "ATTRIBUTE_3":"380", "ATTRIBUTE_4":"FALSE"} |
 | 2023-03-16 15:00:00 | 23456       | { "ATTRIBUTE_1": "28", "ATTRIBUTE_2":"blue", "ATTRIBUTE_3":"823", "ATTRIBUTE_4":"TRUE"}   |
@@ -235,7 +235,7 @@ FROM EXAMPLE_DATA;
 
 ここで、変更された値のみを CDI ソーステーブルに追加する必要があります。古い行を更新するのではなく、これらの行を追加することができます。そのテーブルは次のようになります。
 
-| 更新日          | 外部ID | PAYLOAD                                                                                   |
+| UPDATED_AT          | EXTERNAL_ID | PAYLOAD                                                                                   |
 | :------------------ | ----------- | ----------------------------------------------------------------------------------------- |
 | 2023-03-16 15:00:00 | 12345       | { "ATTRIBUTE_1": "823", "ATTRIBUTE_2":"blue", "ATTRIBUTE_3":"380", "ATTRIBUTE_4":"FALSE"} |
 | 2023-03-16 15:00:00 | 23456       | { "ATTRIBUTE_1": "28", "ATTRIBUTE_2":"blue", "ATTRIBUTE_3":"823", "ATTRIBUTE_4":"TRUE"}   |
@@ -338,7 +338,7 @@ UPDATED_AT	EXTERNAL_ID	PAYLOAD
 
 ## データポイント使用量
 
-Cloud Data Ingestion のデータポイント課金は、[`/users/track`エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track#user-track) を介した更新の課金と同等です。詳細については、「[データポイント]({{site.baseurl}}/user_guide/data_and_analytics/data_points/)」を参照してください。 
+クラウドデータ取り込みのデータポイント請求は、[`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track#user-track) を介した更新の請求に相当します。詳細については、[データポイント]({{site.baseurl}}/user_guide/data_and_analytics/data_points/)を参照してください。 
 
 {% alert important %}
 Braze のクラウドデータ取り込みは利用可能なレート制限で考慮されるため、別の方法でデータを送信する場合、レート制限は Braze API とクラウドデータ取り込みの和になります。
@@ -478,12 +478,12 @@ Braze に正常に同期されたデータの追跡には、`UPDATED_AT` タイ
 | --------- | ---------| --------- | ----------- |
 | `attributes` | [ユーザー属性オブジェクト]({{site.baseurl}}/api/objects_filters/user_attributes_object/)を参照してください |
 | `events` | [イベントオブジェクト]({{site.baseurl}}/api/objects_filters/event_object/)を参照してください |
-| `purchases` | [購入オブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/)を参照 |
+| `purchases` | [購入オブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/)を参照してください |
 
 ネストされた属性で[日付をキャプチャする]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/#capturing-dates-as-object-properties)ための特別な要件に注意してください。 
 
 {% tabs local %}
-{% tab ネストされたカスタム属性 %}
+{% tab 階層化カスタム属性 %}
 カスタム属性を同期するために、階層化カスタム属性をペイロード列に含めることができます。 
 
 ```json
@@ -560,19 +560,19 @@ Braze に正常に同期されたデータの追跡には、`UPDATED_AT` タイ
 
 ### データウェアハウスのクエリのタイムアウトを回避する
 
-クエリは最適なパフォーマンスを得るために1時間以内に完了し、潜在的なエラーを回避することをお勧めします。クエリがこの時間枠を超える場合は、データウェアハウスの構成を見直すことを検討してください。倉庫に割り当てられたリソースを最適化することで、クエリ実行速度を向上させることができます。 
+最適なパフォーマンスを実現し、潜在的なエラーを回避するために、クエリは 1 時間以内に完了することをお勧めします。クエリがこの時間枠を超える場合は、データウェアハウスの構成を見直すことを検討してください。倉庫に割り当てられたリソースを最適化することで、クエリ実行速度を向上させることができます。 
 
 ## 製品の制限事項
 
 | 制限事項            | 説明                                                                                                                                                                        |
 | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 統合の数 | 統合の設定数に制限はありません。ただし、テーブルまたはビューごとに1つの統合しか設定できません。                                             |
-| 行数         | 行を同期できる数に制限はありません。各行は、`UPDATED`列に基づいて一度だけ同期されます。                                                            |
+| 統合の数 | 設定できる統合の数に制限はありません。ただし、テーブルまたはビューごとに1つの統合しか設定できません。                                             |
+| 行数         | 行を同期できる数に制限はありません。各行は、`UPDATED` 列に基づいて一度だけ同期されます。                                                            |
 | 行ごとの属性     | 各行には単一のユーザー ID と最大 250 の属性を持つ JSON オブジェクトが含まれている必要があります。JSONオブジェクトの各キーは1つの属性としてカウントされます（つまり、配列は1つの属性としてカウントされます）。 |
-| ペイロードサイズ           | 各行には最大1 MBのペイロードを含めることができます。ペイロードが1MBを超えると拒否され、エラー「ペイロードが1MBを超えました」が同期ログに関連するexternal IDおよび切り捨てられたペイロードと共に記録されます。 |
-| データタイプ              | Cloud Data Ingestionを通じて、ユーザー属性、イベント、および購入を同期できます。                                                                                                  |
-| Braze地域           | この製品はすべてのBrazeリージョンで利用可能です。任意のBrazeリージョンは、任意のソースデータリージョンに接続できます。                                                                              |
-| ソース地域       | Brazeは、任意のリージョンまたはクラウドプロバイダーのデータウェアハウスまたはクラウド環境に接続します。                                                                                        |
+| ペイロードサイズ           | 各行に最大 1 MB のペイロードを含めることができます。ペイロードが 1 MB を超えると拒否され、「ペイロードが 1 MB を超えました」というエラーが関連する外部 ID および切り捨てられたペイロードと共に同期ログに記録されます。 |
+| データタイプ              | クラウドデータ取り込みを通じて、ユーザー属性、イベント、および購入を同期できます。                                                                                                  |
+| Braze リージョン           | この商品はすべての Braze リージョンで利用可能です。任意の Braze リージョンを任意のソースデータリージョンに接続できます。                                                                              |
+| ソースリージョン       | Braze は、あらゆるリージョンまたはクラウドプロバイダーのデータウェアハウスやクラウド環境に接続できます。                                                                                        |
 {: .reset-td-br-1 .reset-td-br-2}
 
 <br><br>
diff --git a/_lang/ja/_user_guide/data_and_analytics/creating_a_formula.md b/_lang/ja/_user_guide/data_and_analytics/creating_a_formula.md
index 65a8df5ca06..932e161d2ba 100644
--- a/_lang/ja/_user_guide/data_and_analytics/creating_a_formula.md
+++ b/_lang/ja/_user_guide/data_and_analytics/creating_a_formula.md
@@ -9,33 +9,33 @@ tool: Reports
 ---
 # 式の作成
 
-> Braze で分析を表示する場合、複数のデータポイントs を組み合わせて、貴重なインサイトs をユーザーデータに取り込むことができます。これらは式と呼ばれます。数式を使用して、月次アクティブユーザー(MAU)と日次アクティブユーザー(DAU)の総数に基づいて時系列データを正規化します。 
+> Braze で分析を確認する場合、複数のデータポイントを組み合わせてユーザーデータに関する貴重なインサイトを得ることができます。これらは式と呼ばれます。数式を使用して、月次アクティブユーザー(MAU)と日次アクティブユーザー(DAU)の総数に基づいて時系列データを正規化します。 
 
 数式は、データに存在する複雑な関係を理解するのに役立ちます。例えば、特定のセグメントに該当する日次アクティブユーザーが完了したカスタムイベントの数を、一般層 (または他のセグメント) と比較できます。
 
 ## ユースケース
 
-数式は、とくにカスタムイベント s と組み合わせると、アプリ内のユーザーの動作を理解するのに役立ちます。また、Google 広告やテレビなどの有料メディアを Braze とともに使用している場合でも、式によりセグメントの購入パターンについてより深いインサイトが得られます。 
+式を使用して、特にカスタムイベントと組み合わせると、アプリ内のユーザー行動を理解するのに役立ちます。また、Google 広告やテレビなどの有料メディアを Braze とともに使用している場合でも、式によりセグメントの購入パターンについてより深いインサイトが得られます。 
 
 以下に、式を使用して検出できる行動パターンの種類の例をいくつか示します。
 
 - **ライドシェアアプリ:**ユーザー キャンセルが乗車するときにカスタムイベントがある場合は、キャンセル ed Rides / DAU の機能を設定して、特定のユーザー Segmentが他よりも多くの乗車をキャンセルする傾向があるかどうかを確認できます。
-- **Eコマースアプリ:**特定の商品ID/MAUを購入する機能を設定することで、すべてのプロモーションをBrazeで追跡できなくても、最近プロモーションした商品の人気をSegments間で比較することができます。
+- **e コマースアプリ:** 特定の商品ID/MAUを購入する機能を設定することで、すべてのプロモーションをBrazeで追跡できなくても、最近プロモーションした商品の人気をSegments間で比較することができます。
 - **広告を使用したメディアアプリ:**ユーザー体験が動画やオーディオクリップの間にある広告によって中断される場合、広告途中の離脱をカスタムイベントとして記録し、「広告途中の離脱 / DAU」の比率を計算することで、広告なしのプレミアムサブスクリプションのキャンペーンでターゲットにする最適なセグメントを見つけることができます。
 
 ## 式の作成
 
-数式は、ダッシュボードの[Home][9]、[Revenue Report][10]、および[Custom Events Report][11] ページの統計パネルからアクセスできます。このパネルを表示するには、**Performance Over Time** チャートに移動し、**Statistics For** ドロップダウンを**KPI Formulas** に変更してから、少なくとも1 つのKPI 数式を選択してチャートに入力します。
+式には、ダッシュボードの \[[ホーム][9]]、\[[収益レポート][10]]、\[[カスタムイベントレポート][11]] の各ページにある統計パネルからアクセスできます。このパネルを表示するには、**Performance Over Time** チャートに移動し、**Statistics For** ドロップダウンを**KPI Formulas** に変更してから、少なくとも1 つのKPI 数式を選択してチャートに入力します。
 
 ![Braze ダッシュボードでのKPI 数式の統計の表示][16]
 
 新規の式を作成するには、次の手順に従います。
 
-1. アプリの適切なダッシュボードに移動します(**Home**、**Revenue Report**、または**カスタムイベントレポート**)。
+1. 適切なダッシュボード (\[**ホーム**]、\[**収益レポート**]、または \[**カスタムイベントレポート**]) に移動します。
 2. **KPI 数式の管理**を選択します。
 3. 式の名前を入力します。
 4. 該当する分子と分母を選択します。
-5. **Save**を選択します。
+5. \[**保存**] を選択します。
 
 ## 利用可能な分子と分母
 
@@ -66,7 +66,7 @@ table td {
 | 分子 | 分母 |
 | --- | --- |
 | DAU | MAU |
-| セッション数 | DAU |
+| セッション | DAU |
 | | セグメントサイズ |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -84,7 +84,7 @@ table td {
 | --- | --- |
 | カスタムイベントカウント | MAU |
 |  | DAU |
-|  | Segment容量(\[分析 "トラッキング][17] が有効なSegment s のみ使用可能) |
+|  | セグメントサイズ (\[分析の追跡][17] が有効になっているセグメントのみが使用可能) |
 {: .reset-td-br-1 .reset-td-br-2}
 
 [9]: {{site.baseurl}}/user_guide/data_and_analytics/analytics/understanding_your_app_usage_data/
diff --git a/_lang/ja/_user_guide/data_and_analytics/custom_data/purchase_events.md b/_lang/ja/_user_guide/data_and_analytics/custom_data/purchase_events.md
index bc8dbecb3a9..a63cdc4363e 100644
--- a/_lang/ja/_user_guide/data_and_analytics/custom_data/purchase_events.md
+++ b/_lang/ja/_user_guide/data_and_analytics/custom_data/purchase_events.md
@@ -59,7 +59,7 @@ Braze で購入データを使用する方法には、いくつかがありま
 
 各フィルターの詳細については、[セグメンテーションフィルター]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters)の用語集を参照し、「購入行動」でフィルター処理してください。
 
-![正確に3回仕入れたユーザーのフィルタリング][1]{: style="max-width:80%;"}
+![ちょうど 3 回購入したユーザーのフィルター適用][1]{: style="max-width:80%;"}
 
 {% alert tip %}
 特定の購入の発生回数に基づいてセグメンテーションを行う場合は、その購入を個別に[増分カスタム属性]({{site.baseurl}}/developer_guide/platform_wide/analytics_overview/#custom-attribute-storage)として記録する必要があります。
@@ -142,7 +142,7 @@ Braze には、ユーザーの LTV を把握するために参照できる主な
 
 **購入イベントプロパティに基づくトリガーの例:**
 
-![ヘッドフォンマートと同じブランド名でヘッドフォンを購入するユーザーにキャンペーンを送るアクションベースの配信設定s][2]{: style="max-width:80%;margin-left:15px;"}
+![ブランド名が HeadphoneMart に等しいヘッドフォンを購入したユーザーにキャンペーンを送信するアクションベースの配信設定][2]{: style="max-width:80%;margin-left:15px;"}
 
 詳細については、「[購入プロパティオブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/#purchase-properties-object)」を参照してください。
 
@@ -154,7 +154,7 @@ Braze には、ユーザーの LTV を把握するために参照できる主な
 
 これらのセグメンテーションフィルターには次のようなものがあります。
 - 最後のY 日間に、V X 倍のプロパティ Y でカスタムイベントを実行しました。
-- 最後のY日間に、価値V×倍のプロパティ Yで購入したことがある。
+- 過去 Y 日間に、プロパティ Y とその値 V を持つ購入を X 回行った。
 - 1、3、7、14、21、30 日以内に、セグメントに加えられる条件を満たした。
 
 [セグメントエクステンション]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/)とは異なり、使用されるセグメントはリアルタイムで更新され、サポートされるセグメントの数に制限はなく、最大 30 日間の履歴を確認でき、データポイントが使用されます。データポイントが追加で消費されるため、カスタムイベントのイベントプロパティを有効にするように、Braze カスタマーサクセスマネージャーに依頼してください。
@@ -164,7 +164,7 @@ Braze には、ユーザーの LTV を把握するために参照できる主な
 ### キャンバスエントリのプロパティとイベントプロパティ
 
 {% alert important %}
-2023 年 2 月 28 日以降、元のエディターを使用したキャンバスを作成または複製はできなくなりました。このセクションは、元のキャンバスワークフローで `canvas_entry_properties` や `event_properties` を使用するとき場合の参考として用意されています。
+2023 年 2 月 28 日以降、元のエディターを使用したキャンバスの作成や複製はできなくなりました。このセクションは、元のキャンバスワークフローで `canvas_entry_properties` や `event_properties` を使用するとき場合の参考として用意されています。
 {% endalert %}
 
 キャンバスのユーザージャーニーで `canvas_entry_properties` と `event_properties` を活用できます。詳細と例については、「[キャンバスエントリのプロパティとイベントプロパティ]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties/)」を参照してください。
@@ -176,7 +176,7 @@ Braze には、ユーザーの LTV を把握するために参照できる主な
 {% tabs local %}
 {% tab キャンバスエントリのプロパティ %}
 
-[キャンバスエントリのプロパティ]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/)は、アクションベースまたは API でトリガーされるキャンバスにマップするプロパティです。`canvas_entry_properties` オブジェクトのサイズ上限は 100 KB であることに注意してください。
+[キャンバスエントリのプロパティ]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/)は、アクションベースまたは API でトリガーされるキャンバスにマップするプロパティです。`canvas_entry_properties` オブジェクトのサイズ上限は 50 KB であることに注意してください。
 
 {% alert important %}
 特にアプリ内メッセージチャネルでは、以前の早期アクセスの一環として元のエディターで永続的なエントリプロパティを有効にしている場合、キャンバスフローと元のキャンバスエディターでのみ `canvas_entry_properties` を参照できます。
diff --git a/_lang/ja/_user_guide/data_and_analytics/data_transformation/use_cases.md b/_lang/ja/_user_guide/data_and_analytics/data_transformation/use_cases.md
index c71ad232a70..021f76af762 100644
--- a/_lang/ja/_user_guide/data_and_analytics/data_transformation/use_cases.md
+++ b/_lang/ja/_user_guide/data_and_analytics/data_transformation/use_cases.md
@@ -15,7 +15,7 @@ description: "このリファレンス記事では、Braze Data Transformation 
 自社の Web サイトで、リードを創出する Typeform フォームをホストしています。新規ユーザーがこのフォームに入力すると、次のことができます。
 - Brazeで新規ユーザーを作成する。
 - BrazeのEメールリストに追加する。
-- 彼らの回答は貴重なファーストパーティデータであり、将来的にパーソナライズされたメッセージング体験を提供することができる。
+- 回答のいくつかを Braze のカスタム属性として同期します。回答は、将来に向けてパーソナライズされたメッセージングエクスペリエンスを強化できる貴重なファーストパーティデータであるためです。
 
 ## サービスチケットを開く
 
diff --git a/_lang/ja/_user_guide/data_and_analytics/export_braze_data/export_canvas_data.md b/_lang/ja/_user_guide/data_and_analytics/export_braze_data/export_canvas_data.md
index 108d8c7d2b0..4ce86be9ac0 100644
--- a/_lang/ja/_user_guide/data_and_analytics/export_braze_data/export_canvas_data.md
+++ b/_lang/ja/_user_guide/data_and_analytics/export_braze_data/export_canvas_data.md
@@ -18,19 +18,19 @@ tool:
 
 特定キャンバスのデータをエクスポートするには、次の手順に従います。
 
-1. **メッセージング**＞**キャンバスと**進み、キャンバスを選択する。
+1. \[**メッセージング**] > \[**キャンバス**] に移動し、キャンバスを選択します。
 2. **Canvas Details**セクションで**User Data**ドロップダウンを選択する。 
 3. 次のいずれかのエクスポートオプションを選択します。
   - **ユーザーデータを CSV 形式でエクスポート**
   - **メールアドレスを CSV 形式でエクスポート**
 
-キャンバスの全出場者のユーザーデータをCSVファイルとしてエクスポートすることもできる。
+キャンバスに入った全ユーザーのデータを CSV ファイルとしてエクスポートすることもできます。
 
 ## 特定コンポーネントのデータのエクスポート (元のワークフローのみ)
 
 キャンバスの結果は、元のキャンバスワークフローのコンポーネント単位でエクスポートできます。これを行うには、特定のコンポーネントを選択し、**キャンバス・ステップの詳細**ページで**User Data**ドロップダウンを選択する。 
 
-![キャンバスの詳細ページのユーザーデータドロップダウン。][1]
+![\[キャンバスの詳細] ページの \[ユーザーデータ] ドロップダウン。][1]
 
 {% alert tip %}
 CSV および API のエクスポートに関するヘルプについては、「[エクスポートのトラブルシューティング]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/)」の記事を参照してください。
diff --git a/_lang/ja/_user_guide/data_and_analytics/export_braze_data/segment_data_to_csv.md b/_lang/ja/_user_guide/data_and_analytics/export_braze_data/segment_data_to_csv.md
index 4e4f97bd91b..b1a2c9c3486 100644
--- a/_lang/ja/_user_guide/data_and_analytics/export_braze_data/segment_data_to_csv.md
+++ b/_lang/ja/_user_guide/data_and_analytics/export_braze_data/segment_data_to_csv.md
@@ -9,7 +9,7 @@ description: "このリファレンス記事では、セグメントデータを
 
 # CSV へのセグメントデータのエクスポート
 
-> セグメントからユーザーデータのCSVエクスポートを要求するには、セグメントを編集中に**ユーザーデータドロップダウンを**選択し、セグメントのユーザーデータまたはメールアドレスのいずれかをエクスポートするように選択する。
+> セグメントからユーザーデータの CSV エクスポートをリクエストするには、セグメントを編集中に \[**ユーザーデータ]** ドロップダウンを選択し、セグメントのユーザーデータまたはメールアドレスのいずれかをエクスポートするように選択します。
 
 ![][1]
 
@@ -21,13 +21,13 @@ description: "このリファレンス記事では、セグメントデータを
 すべてのユーザープロファイルからデータをエクスポートするには、フィルタなしでセグメントを作成し、CSVエクスポートをリクエストする。
 {% endalert %}
 
-CSV 出力には、エクスポート時にセグメントに収集済みの各ユーザープロファイルのデータが含まれています。歯車のアイコンを選択し、CSVエクスポートを選択することで、任意のセグメントをエクスポートできる。Braze はバックグラウンドでレポートを生成し、現在ログインしているユーザーにメールで通知します。
+CSV 出力には、エクスポート時にセグメントに収集済みの各ユーザープロファイルのデータが含まれています。歯車アイコンを選択して CSV エクスポートを選択することで、任意のセグメントをエクスポートできます。Braze はバックグラウンドでレポートを生成し、現在ログインしているユーザーにメールで通知します。
 
 {% alert important %}
 ファイルサイズの制限により、セグメントの推定サイズがユーザー数 500,000 人を超える場合、エクスポートに失敗する可能性があります。この制限は、セグメントの正確な計算ではなく推定サイズを使用することに注意してください。詳細については、「[大規模なセグメントのエクスポート]({{site.baseurl}}/help/help_articles/segments/exporting_large_segments/)」を参照してください。
 {% endalert %}
 
-Amazon S3 credentials][26] をBrazeにリンクしている場合、CSVは代わりにS3バケットに`segment-export/SEGMENT_ID/YYYY-MM-dd/users-RANDOMSTRING.zip` というキーでアップロードされる。メールで送信されたリンクはエクスポート後 1 日で期限切れになり、アクセスするにはダッシュボードにログインする必要があります。
+\[Amazon S3 の認証情報][26] を Braze にリンクしている場合、CSV は代わりに S3 バケットのキー `segment-export/SEGMENT_ID/YYYY-MM-dd/users-RANDOMSTRING.zip` の下にアップロードされます。メールで送信されたリンクはエクスポート後 1 日で期限切れになり、アクセスするにはダッシュボードにログインする必要があります。
 
 ## エクスポートに含まれるデータ
 
@@ -39,39 +39,39 @@ Amazon S3 credentials][26] をBrazeにリンクしている場合、CSVは代わ
 | --------------------------- | -------------------------------------------------------- |
 | Appboy ID                   | 内部ID（変更不可）                           |
 | country                     | 国                                    |
-| 作成日時                  | ユーザープロファイルが作成された日時                   |
-| デバイス                     | デバイス情報                           |
-| 生年月日               | 生年月日                                            |
+| created_at                  | ユーザープロファイルが作成された日時                   |
+| devices                     | デバイス情報                           |
+| date_of_birth               | 生年月日                                            |
 | email                       | メールアドレス                                            |
-| 配信停止_from_emails_at | メール配信停止日                            |
+| unsubscribed_from_emails_at | メールの配信停止日                            |
 | user_id                     | external ID                                              |
 | first_name                  | 名                                               |
 | first_session               | 初回セッションの日時                           |
 | gender                      | 性別                                                   |
 | google_ad_ids               | ユーザーに関連付けられたGoogle広告ID                      |
-| 都市                        | 市区町村                                     |
+| city                        | 市区町村                                     |
 | IDFA                       | 広告用識別子（IDFA）の値                 |
-| IDFVs                       | ベンダー識別子（IDFV）の値                      |
+| IDFVs                       | ベンダー識別子 (IDFV) の値                      |
 | language                    | ISO-639-1規格の言語                                        |
-| 最後に使用したアプリのバージョン       | 最後に使用したアプリのバージョン                             |
+| last_app_version_used       | 最後に使用したアプリのバージョン                             |
 | last_name                   | 姓                                                |
-| ラスト・セッション                | 前回のセッション日時                            |
-| Google広告のID数     | 関連するGoogle広告IDの数               |
-| IDFA数             | 関連するIDFAの数                                |
-| IDFV数             | 関連するIDFVの数                                |
-| プッシュ・トークン数       | 関連するプッシュ通知トークンの数             |
-| roku_ad_idsの数       | 関連するRoku広告IDの数                 |
-| ウィンドウズ広告数    | 関連するWindows広告IDの数              |
-| 電話番号                | 電話番号                                             |
-| opted_into_push_at          | プッシュ通知をオプトインした日付                       |
-| 配信停止_from_push_at   | プッシュ通知の配信停止日                |
-| ランダムバケット               | ランダムバケット番号                                 |
+| last_session                | 最終セッションの日時                            |
+| number_of_google_ad_ids     | 関連するGoogle広告IDの数               |
+| number_of_IDFAs             | 関連するIDFAの数                                |
+| number_of_IDFVs             | 関連する IDFV の数                                |
+| number_of_push_tokens       | 関連するプッシュ通知トークンの数             |
+| number_of_roku_ad_ids       | 関連するRoku広告IDの数                 |
+| number_of_windows_ad_ids    | 関連するWindows広告IDの数              |
+| phone_number                | 電話番号                                             |
+| opted_into_push_at          | プッシュ通知にオプトインした日付                       |
+| unsubscribed_from_push_at   | プッシュ通知の配信停止日                |
+| random_bucket               | ランダムバケット番号                                 |
 | roku_ad_ids                 | ロクの広告ID                          |
-| セッション数               | 総セッション数                                 |
+| session_count               | セッションの総数                                 |
 | timezone                    | IANAタイムゾーンデータベースと同じフォーマットによるユーザーのタイムゾーン                                         |
-| アプリ内購入総額       | アプリ内課金の総額                   |
-| ユーザー・エイリアス                | ユーザーエイリアスがある場合                                          |
-| windows_ad_ids              | ウィンドウズの広告ID                       |
+| in_app_purchase_total       | アプリ内購入の支出総額                   |
+| user_aliases                | ユーザーエイリアスがある場合                                          |
+| windows_ad_ids              | Windows の広告 ID                       |
 | カスタムイベント               | 輸出時の選択に基づく                             |
 | カスタム属性           | 輸出時の選択に基づく                             |
 {: .reset-td-br-1 .reset-td-br-2 }
@@ -84,9 +84,9 @@ Amazon S3 credentials][26] をBrazeにリンクしている場合、CSVは代わ
 | first_name                  | 名             |
 | last_name                   | 姓              |
 | email                       | メール                  |
-| 配信停止_from_emails_at | メール配信停止日 |
-| オプトイン・トゥ・メールアドレス       | メールオプトイン日      |
-| ユーザー・エイリアス                | ユーザーエイリアスがある場合   |
+| unsubscribed_from_emails_at | メール配信停止日 |
+| opted_in_to_emails_at       | メールオプトイン日      |
+| user_aliases                | ユーザーエイリアスがある場合   |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert tip %}
@@ -95,4 +95,4 @@ CSV と API のエクスポートについては、[トラブルシューティ
 
 [1]: {% image_buster /assets/img_archive/csvexport.png %}
 [2]: {% image_buster /assets/img_archive/csvexport2.png %}
-{{site.baseurl}} partners/data_and_infrastructure_agility/data_warehouses/amazon_s3/#amazon-s3-integration/
+[26]: {{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/amazon_s3/#amazon-s3-integration
diff --git a/_lang/ja/_user_guide/data_and_analytics/query_builder/query_templates.md b/_lang/ja/_user_guide/data_and_analytics/query_builder/query_templates.md
index a07d8ceb05c..4c4eef79f5f 100644
--- a/_lang/ja/_user_guide/data_and_analytics/query_builder/query_templates.md
+++ b/_lang/ja/_user_guide/data_and_analytics/query_builder/query_templates.md
@@ -4,7 +4,7 @@ article_title: クエリビルダーテンプレート
 page_order: 0
 page_type: reference
 toc_headers: h2
-description: "このリファレンス記事では、Query BuilderでSnowflakeのBrazeデータを使用して作成できるレポートの種類を一覧表示します。"
+description: "この記事では、クエリビルダーで Snowflake の Braze データを使用して作成できるレポートのタイプを示します。"
 tool: Reports
 ---
 
@@ -28,38 +28,38 @@ table td {
 
 | クエリ名 | 説明 | 
 | --- | --- | 
-| チャネルエンゲージメントと収益 | このレポートは、各チャネルごとに、すべてのエンゲージメント指標（開封数やクリック数など）、収益、取引数、および平均価格を示しています。{::nomarkdown}<ul> <li> <i>取引数:</i>購入イベント数 </li> <li> <i>平均価格:</i>取引によって分けられた収益 </li> </ul> {:/} ![]({% image_buster /assets/img_archive/channel_engagement_revenue.png %}) |
-| セグメント別の購入と収益 | このレポートは、特定のセグメントに送信されたメッセージのメトリクスを示しています。<br><br> 購入指標は報告期間全体で一意です。1人のユーザーは、最大で1回の購入を生成できます。収益は、報告期間中のすべての購入を考慮に入れます。 |
-| セグメント別のバリアントまたはステップの購入と収益 | このレポートは、各セグメントに送信されたメッセージのバリアントまたはキャンバスステップのメトリクスを示しています。<br><br> 購入指標は報告期間全体で一意です。1人のユーザーは、最大で1回の購入を生成できます。収益は、報告期間中のすべての購入を考慮に入れます。 |
-| 購入のためのトップ/ボトムメッセージング | このレポートは、上位または下位のキャンペーン、キャンバス、またはキャンバスステップの購入指標を示しています。各行はキャンペーン、キャンバス、またはキャンバスステップです。トップパフォーマーまたはボトムパフォーマーを表示するかどうか、およびこの分析を実行する特定の指標（例えば、*受領時のユニーク購入数*、*受領時の収益*、*ユニーク受信者数*）を指定する必要があります。<br><br> トップパフォーマーレポートの行は、最高から最悪の順に並べられ、ボトムパフォーマーレポートの行は、最悪から最高の順に並べられます。 |
+| チャネルエンゲージメントと収益 | このレポートは、各チャネルごとに、すべてのエンゲージメント指標（開封数やクリック数など）、収益、取引数、および平均価格を示しています。{::nomarkdown}<ul> <li> <i>トランザクション数:</i> 購入イベント数 </li> <li> <i>平均価格:</i>収益をトランザクション数で除算した値 </li> </ul> {:/} ![]({% image_buster /assets/img_archive/channel_engagement_revenue.png %}) |
+| セグメント別の購入と収益 | このレポートは、特定のセグメントに送信されたメッセージのメトリクスを示しています。<br><br> 購入指標はレポート期間全体を通じて一意です。1 人のユーザーは、最大で 1 回の購入を生成できます。収益は、レポート期間中のすべての購入を考慮しています。 |
+| セグメント別のバリアントまたはステップの購入と収益 | このレポートは、各セグメントに送信されたメッセージのバリアントまたはキャンバスステップのメトリクスを示しています。<br><br> 購入指標はレポート期間全体を通じて一意です。1 人のユーザーは、最大で 1 回の購入を生成できます。収益は、レポート期間中のすべての購入を考慮しています。 |
+| 購入のための上位/下位メッセージング | このレポートは、上位または下位のキャンペーン、キャンバス、またはキャンバスステップの購入指標を示しています。各行はキャンペーン、キャンバス、またはキャンバスステップです。上位パフォーマーまたは下位パフォーマーを表示するかどうか、およびこの分析を実行する特定の指標 (例えば、*受領後のユニーク購入*、*受領後の収益*、*ユニーク受信者数*) を指定する必要があります。<br><br> トップパフォーマーレポートの行は、最高から最悪の順に並べられ、ボトムパフォーマーレポートの行は、最悪から最高の順に並べられます。 |
 {: .reset-td-br-1 .reset-td-br-2 }
 
 ## キャンペーンテンプレート
 
 | クエリ名 | 説明 | 
 | --- | --- | 
-| 国別のキャンペーン収益 | このレポートは、特定のキャンペーンにおける国ごとの収益を示しています。このレポートを実行するには、キャンペーンのAPI識別子を指定する必要があります。キャンペーンのAPI識別子は、そのキャンペーンの詳細ページの下部にあります。<br><br> このレポートは、各国の収益額、注文数、返品数、純収益、および総収益を示しています。<br><br> {::nomarkdown}<ul> <li> <i>注文:</i>購入イベント数 </li> <li><i> 戻り値:</i>負の収益値を持つ購入イベントの数 </li> <li><i> 純収益:</i>すべての非返品の収益 </li> <li><i> 総収入:</i>返品の価値を含む収益 </li></ul>{:/} ![]({% image_buster /assets/img_archive/campaign_revenue_country.png %}){: style="max-width:70%;"} |
+| 国別のキャンペーン収益 | このレポートは、特定のキャンペーンにおける国ごとの収益を示しています。このレポートを実行するには、キャンペーンのAPI識別子を指定する必要があります。キャンペーンのAPI識別子は、そのキャンペーンの詳細ページの下部にあります。<br><br> このレポートは、国ごとの収益額、注文数、返品数、純収益、および総収益を示しています。<br><br> {::nomarkdown}<ul> <li> <i>注文数:</i> 購入イベント数 </li> <li><i> 返品数:</i> 負の収益値を持つ購入イベントの数 </li> <li><i> 純収益:</i> 返品を除いた収益の合計 </li> <li><i>総収益</i>: 返品額を含めた収益 </li></ul>{:/} ![]({% image_buster /assets/img_archive/campaign_revenue_country.png %}){: style="max-width:70%;"} |
 {: .reset-td-br-1 .reset-td-br-2 }
 
 ## キャンバステンプレート
 
 | クエリ名 | 説明 | 
 | --- | --- | 
-| 国別のキャンバス収益 | このレポートは、特定のキャンバスの国ごとの収益を示しています。このレポートを実行するには、キャンバスのAPI識別子を指定する必要があります。**Analyze Variants**の下にキャンバスAPI識別子があります。<br><br> このレポートは、各国の収益額、注文数、返品数、純収益、および総収益を示しています。<br><br> {::nomarkdown}<ul> <li> <i>注文:</i>購入イベント数 </li> <li><i> 戻り値:</i>負の収益値を持つ購入イベントの数 </li> <li><i> 純収益:</i>すべての非返品の収益 </li> <li><i> 総収入:</i>返品の価値を含む収益 </li></ul>{:/} ![]({% image_buster /assets/img_archive/canvas_revenue_country.png %}){: style="max-width:70%;"} |
+| 国別のキャンバス収益 | このレポートは、特定のキャンバスの国ごとの収益を示しています。このレポートを実行するには、キャンバスのAPI識別子を指定する必要があります。キャンバス API 識別子は \[**バリアント分析**] の下にあります。<br><br> このレポートは、国ごとの収益額、注文数、返品数、純収益、および総収益を示しています。<br><br> {::nomarkdown}<ul> <li> <i>注文数:</i> 購入イベント数 </li> <li><i> 返品数:</i> 負の収益値を持つ購入イベントの数 </li> <li><i> 純収益:</i> 返品を除いた収益の合計 </li> <li><i>総収益</i>: 返品額を含めた収益 </li></ul>{:/} ![]({% image_buster /assets/img_archive/canvas_revenue_country.png %}){: style="max-width:70%;"} |
 {: .reset-td-br-1 .reset-td-br-2 }
 
 ## メールテンプレート
 
 | クエリ名 | 説明 | 
 | --- | --- | 
-| ドメインごとのメールのバウンス | メールドメインごとのバウンス数を、総バウンス数、ハードバウンス数、ソフトバウンス数に分けて示します。<br> ![]({% image_buster /assets/img_archive/query_builder_q4.png %}){: style="max-width:60%;"} |
-| 日ごとのメール配信指標 | このレポートは、各日に送信されたメッセージのメトリクスを示しており、送信されたメールの数、配信されたメールの数、ソフトバウンスの数、ハードバウンスの数などが含まれています。<br><br> すべての指標は報告期間を通じて一意です。例えば、11月21日にウェルカムメールが1回ソフトバウンスし、11月22日に2回ソフトバウンスし、一度も配信されなかった場合: {::nomarkdown}<ul><li> 11月21日の<i>ソフトバウンス</i>メトリックが1つ増加します。</li><li> 11月22日の<i>ソフトバウンス</i>メトリックには影響がありません。</li></ul>{:/} ![]({% image_buster /assets/img_archive/email_delivery_day.png %})|
-|  セグメント別のメールエンゲージメント指標 | このレポートは、各セグメントに送信されたメッセージのメトリクスを示しています。例えば、送信されたメールの数、配信されたメールの数、ソフトバウンスの数、ハードバウンスの数などです。<br><br> すべての指標は報告期間を通じて一意です。例えば、11月21日にウェルカムメールが1回ソフトバウンスし、11月22日に2回ソフトバウンスし、一度も配信されなかった場合: {::nomarkdown}<ul><li> 11月21日の<i>ソフトバウンス</i>メトリックが1つ増加します。</li><li> 11月22日の<i>ソフトバウンス</i>メトリックには影響がありません。</li></ul>{:/} ![]({% image_buster /assets/img_archive/email_engagement_segment.png %}) |
-| セグメント別のバリアントまたはステップのメールエンゲージメント指標 | このレポートは、各セグメントに送信されたメッセージのバリアントまたはキャンバスステップのメトリクスを示しています。これらの指標には、送信されたメールの数、配信されたメールの数、ソフトバウンスしたメールの数、およびハードバウンスしたメールの数が含まれます。<br><br> すべての指標は報告期間を通じて一意です。例えば、11月21日にウェルカムメールが1回ソフトバウンスし、11月22日に2回ソフトバウンスし、一度も配信されなかった場合: {::nomarkdown}<ul><li> 11月21日の<i>ソフトバウンス</i>メトリックが1つ増加します。</li> <li> 11月22日の<i>ソフトバウンス</i>メトリックには影響がありません。</li></ul> {:/} |
-| 国別のメールパフォーマンス | このレポートは、各国の送信数、間接開封率、および直接開封率のメトリクスを示しています。国はプッシュ送信時のユーザーの国です。<br><br> ![]({% image_buster /assets/img_archive/query_builder_q3.png %}) |
+| ドメイン別のメールバウンス数 | メールドメインごとのバウンス数を、総バウンス数、ハードバウンス数、ソフトバウンス数に分けて示します。<br> ![]({% image_buster /assets/img_archive/query_builder_q4.png %}){: style="max-width:60%;"} |
+| 日別のメール配信指標 | このレポートは、各日に送信されたメッセージのメトリクスを示しており、送信されたメールの数、配信されたメールの数、ソフトバウンスの数、ハードバウンスの数などが含まれています。<br><br> すべての指標はレポート期間全体を通じて一意です。例えば、11月21日にウェルカムメールが1回ソフトバウンスし、11月22日に2回ソフトバウンスし、一度も配信されなかった場合: {::nomarkdown}<ul><li> 11 月 21 日の<i>ソフトバウンス</i>指標が 1 つ増加します。</li><li> 11月22日の<i>ソフトバウンス</i>メトリックには影響がありません。</li></ul>{:/} ![]({% image_buster /assets/img_archive/email_delivery_day.png %})|
+|  セグメント別のメールエンゲージメント指標 | このレポートは、各セグメントに送信されたメッセージのメトリクスを示しています。例えば、送信されたメールの数、配信されたメールの数、ソフトバウンスの数、ハードバウンスの数などです。<br><br> すべての指標はレポート期間全体を通じて一意です。例えば、11月21日にウェルカムメールが1回ソフトバウンスし、11月22日に2回ソフトバウンスし、一度も配信されなかった場合: {::nomarkdown}<ul><li> 11 月 21 日の<i>ソフトバウンス</i>指標が 1 つ増加します。</li><li> 11月22日の<i>ソフトバウンス</i>メトリックには影響がありません。</li></ul>{:/} ![]({% image_buster /assets/img_archive/email_engagement_segment.png %}) |
+| セグメント別のバリアントまたはステップのメールエンゲージメント指標 | このレポートは、各セグメントに送信されたメッセージのバリアントまたはキャンバスステップのメトリクスを示しています。これらの指標には、送信されたメールの数、配信されたメールの数、ソフトバウンスしたメールの数、およびハードバウンスしたメールの数が含まれます。<br><br> すべての指標はレポート期間全体を通じて一意です。例えば、11月21日にウェルカムメールが1回ソフトバウンスし、11月22日に2回ソフトバウンスし、一度も配信されなかった場合: {::nomarkdown}<ul><li> 11 月 21 日の<i>ソフトバウンス</i>指標が 1 つ増加します。</li> <li> 11月22日の<i>ソフトバウンス</i>メトリックには影響がありません。</li></ul> {:/} |
+| 国別のメールパフォーマンス | このレポートは、国ごとの送信数、間接開封率、および直接開封率の指標を示しています。国はプッシュ送信時のユーザーの国です。<br><br> ![]({% image_buster /assets/img_archive/query_builder_q3.png %}) |
 | メールサブスクリプション変更ログ | このレポートは、各ユーザーのサブスクリプション変更に関して記録されたメトリクスを示しています。例えば、メールアドレス、サブスクリプションステータス、ステータスが変更された時間、および関連するキャンバスまたはキャンペーンなどです。 |
-| メールサブスクリプショングループのオプトインとオプトアウト | このレポートは、各週の任意のメールサブスクリプショングループに対するユニークなユーザーのオプトインおよびオプトアウトの数を示しています。<br><br> ![]({% image_buster /assets/img_archive/query_builder_q2.png %}){: style="max-width:70%;"} |
-| メールURLクリック | このレポートは、メール内の各リンクのクリック数を示しています。このレポートを実行するには、キャンペーンまたはキャンバスの API 識別子を指定する必要があります。キャンペーンのAPI識別子は、そのキャンペーンの詳細ページの下部にあり、キャンバスAPI識別子は**Analyze Variants**の下にあります。<br><br> このレポートは、非パーソナライズされたリンクと各リンクのクリック数を示しています。CSVダウンロードには、クリックしたすべてのユーザーのユーザーID、クリックしたリンク、およびクリックした時刻のタイムスタンプが含まれます。<br><br> *パーソナライズされていないURL:*Liquidタグが削除されたURL。<br><br> ![]({% image_buster /assets/img_archive/query_builder_q5.png %}){: style="max-width:70%;"} |
+| メールサブスクリプショングループのオプトインとオプトアウト | このレポートは、週ごとの任意のメールサブスクリプショングループにおけるユニークユーザーのオプトインおよびオプトアウトの数を示しています。<br><br> ![]({% image_buster /assets/img_archive/query_builder_q2.png %}){: style="max-width:70%;"} |
+| メールURLクリック | このレポートは、メール内の各リンクのクリック数を示しています。このレポートを実行するには、キャンペーンまたはキャンバスの API 識別子を指定する必要があります。キャンペーンのAPI識別子は、そのキャンペーンの詳細ページの下部にあり、キャンバスAPI識別子は**Analyze Variants**の下にあります。<br><br> このレポートは、非パーソナライズされたリンクと各リンクのクリック数を示しています。CSVダウンロードには、クリックしたすべてのユーザーのユーザーID、クリックしたリンク、およびクリックした時刻のタイムスタンプが含まれます。<br><br> *非パーソナライズされた URL:* Liquidタグが削除されたURL。<br><br> ![]({% image_buster /assets/img_archive/query_builder_q5.png %}){: style="max-width:70%;"} |
 | トップ/ボトムメッセージングによるメールエンゲージメント | このレポートは、トップまたはボトムのキャンペーン、キャンバス、またはキャンバスステップのメールエンゲージメント指標を示しています。トップまたはボトムのパフォーマーを表示するかどうか、およびこの分析を実行する特定の指標（*送信*、*ソフトバウンス*、*ユニークオープン*など）を指定する必要があります。<br><br> トップパフォーマーレポートの行は、最高から最悪の順に並べられ、ボトムパフォーマーレポートの行は、最悪から最高の順に並べられます。<br><br> ![]({% image_buster /assets/img_archive/top-bottom-email.png %}) |
 {: .reset-td-br-1 .reset-td-br-2 }
 
@@ -67,7 +67,7 @@ table td {
 
 | クエリ名 | 説明 | 
 | --- | --- | 
-| デバイスキャリア | デバイスキャリアごとのユーザー数（VerizonやT-Mobileなど）。<br><br> ![]({% image_buster /assets/img_archive/device_carriers.png %}){: style="max-width:50%;"} |
+| デバイスの通信事業者 | デバイスの通信事業者 (Verizon や T-Mobile など) ごとのユーザー数。<br><br> ![]({% image_buster /assets/img_archive/device_carriers.png %}){: style="max-width:50%;"} |
 | デバイスモデル | デバイスモデルごとのユーザー数、例えばiPhone 15 ProやPixel 7。<br><br> ![]({% image_buster /assets/img_archive/device_models.png %}){: style="max-width:50%;"} |
 | デバイスのオペレーティングシステム | オペレーティングシステムごとのユーザー数（17.4やAndroid 14など）。<br><br> ![]({% image_buster /assets/img_archive/os_version.png %}){: style="max-width:50%;"} |
 | デバイス画面解像度 | デバイス画面解像度ごとのユーザー数、例えば1179x2556や750x1334。<br><br> ![]({% image_buster /assets/img_archive/device_screen_resolutions.png %}){: style="max-width:40%;"} |
@@ -75,11 +75,11 @@ table td {
 | SMSユーザーによるエラーの提供 | このレポートは特定のユーザーのSMSエラーコードを表示します。 |
 {: .reset-td-br-1 .reset-td-br-2 }
 
-## テンプレートを押す
+## プッシュテンプレート
 
 | クエリ名 | 説明 | 
 | --- | --- | 
-| 国ごとのパフォーマンスを押し上げる | このレポートは、各国の配信数、開封率、およびクリック率を示しています。国は、メール送信時のユーザーの国です。<br><br> ![]({% image_buster /assets/img_archive/query_builder_q7.png %}){: style="max-width:70%;"} |
+| 国別のプッシュ通知のパフォーマンス | このレポートは、国ごとの配信数、開封率、およびクリック率を示しています。国は、メール送信時のユーザーの国です。<br><br> ![]({% image_buster /assets/img_archive/query_builder_q7.png %}){: style="max-width:70%;"} |
 {: .reset-td-br-1 .reset-td-br-2 }
 
 ## セグメントの内訳
@@ -89,6 +89,6 @@ table td {
 | セグメント別のメールエンゲージメント指標 | このレポートは、キャンペーンまたはキャンバスレベルでセグメント別に分けられたメールのパフォーマンス指標を示しています。 |
 | セグメント別の購入と収益 | このレポートは、特定のキャンペーンまたはキャンバスのセグメントごとに分類された購入および収益の指標を示しています。 |
 | トップ/ボトムメッセージングによるメールエンゲージメント | このレポートは、指定されたメールエンゲージメント指標に対して最も高いまたは低いパフォーマンスを示したキャンペーン、キャンバス、またはキャンバスステップを示しています。|
-| 購入のためのトップ/ボトムメッセージング | このレポートは、指定された購入または収益の指標に対して、最も高いまたは最も低いパフォーマンスを示したキャンペーン、キャンバス、またはキャンバスステップを示しています。 |
+| 購入のための上位/下位メッセージング | このレポートは、指定された購入または収益の指標に対して、最も高いまたは最も低いパフォーマンスを示したキャンペーン、キャンバス、またはキャンバスステップを示しています。 |
 | セグメントごとのパフォーマンスを押し上げる | このレポートは、セグメントごとに分類されたプッシュメトリクスを示しています。|
 {: .reset-td-br-1 .reset-td-br-2 }
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/data_and_analytics/reporting.md b/_lang/ja/_user_guide/data_and_analytics/reporting.md
index 22aa3750926..590290de840 100644
--- a/_lang/ja/_user_guide/data_and_analytics/reporting.md
+++ b/_lang/ja/_user_guide/data_and_analytics/reporting.md
@@ -4,7 +4,7 @@ article_title: レポート
 page_order: 7
 layout: dev_guide
 guide_top_header: "レポート"
-guide_top_text: "あなたのデータはあなたにとって重要なものなので、Brazeではいくつかのレポートオプションを用意している（<a href='/docs/user_guide/data_and_analytics/braze_currents/'>Currentsを</a>除く）。<br><br> 何から始めたらよいかわからない場合は、<a href='/docs/user_guide/data_and_analytics/reporting/reports_overview/'>レポート概要を</a>チェックして、マーケティング戦略に関する一般的な質問に答えるためにどのレポートやアナリティクスを使用できるかのガイダンスを得よう。"
+guide_top_text: "貴社のデータは貴社にとって多くの意味を持つため、当社は Braze 内にいくつかのレポート処理のオプションが用意されています (ただし <a href='/docs/user_guide/data_and_analytics/braze_currents/'>Currents</a>を除く)。<br><br> 何から始めたらよいかわからない場合は、<a href='/docs/user_guide/data_and_analytics/reporting/reports_overview/'>レポート概要を</a>チェックして、マーケティング戦略に関する一般的な質問に答えるためにどのレポートやアナリティクスを使用できるかのガイダンスを得よう。"
 
 page_type: landing
 description: "このランディングページには、セグメントレポート、エンゲージメントレポート、レポートビルダーなど、Braze (Currents を含まない) で利用可能なレポートオプションに関する記事がまとめられています。"
@@ -42,7 +42,7 @@ guide_menu_list:
   - name: 目標到達プロセスレポート
     link: /docs/user_guide/engagement_tools/campaigns/testing_and_more/campaign_funnel_report/
     image: /assets/img/braze_icons/flag-02.svg
-  - name: グローバル・コントロール・レポート
+  - name: グローバルコントロールレポート
     link: /docs/user_guide/engagement_tools/testing/global_control_group/#viewing-reporting
     image: /assets/img/braze_icons/globe-04.svg
   - name: リテンションレポート
diff --git a/_lang/ja/_user_guide/data_and_analytics/reporting/data_by_segments.md b/_lang/ja/_user_guide/data_and_analytics/reporting/data_by_segments.md
index a756e7738be..d2e9e1d38cf 100644
--- a/_lang/ja/_user_guide/data_and_analytics/reporting/data_by_segments.md
+++ b/_lang/ja/_user_guide/data_and_analytics/reporting/data_by_segments.md
@@ -3,7 +3,7 @@ nav_title: セグメント別指標
 article_title: セグメント別指標
 page_order: 2.5
 page_type: reference
-description: "この参考記事では、クエリビルダーのレポートテンプレートを使って、キャンペーン、キャンバス、バリアント、ステップのパフォーマンス指標をセグメント別に分類する方法を紹介する。"
+description: "この記事では、クエリビルダーのレポートテンプレートを使用して、キャンペーン、キャンバス、バリアント、ステップのパフォーマンス指標をセグメント別に分類する方法について説明します。"
 tool: 
   - Segments
   - Reports
@@ -21,12 +21,12 @@ tool:
 2. フィルターを使用して、指標に「セグメントの内訳」が含まれているテンプレートを表示します。
 - セグメント別のEメール・パフォーマンス・メトリクス
 - セグメント別のバリアントまたはステップのメールエンゲージメント指標
-- セグメント別仕入高・売上高
-- バリアントまたはステップの購入および収益（セグメント別
+- セグメント別の購入と収益
+- セグメント別のバリアントまたはステップの購入と収益
 - セグメント別プッシュ・パフォーマンス
 
 
-![セグメントの内訳ページには、SQLエディター、変数、利用可能なデータテーブル、クエリ履歴、AIクエリビルダーのタブがあるサイドパネル、結果セクションがある。]({% image_buster /assets/img_archive/segment_breakdown.png %})
+![セグメントの内訳ページには、SQL エディター、変数、利用可能なデータテーブル、クエリ履歴、AI クエリビルダーのタブがあるサイドパネルと、結果セクションが表示されます。]({% image_buster /assets/img_archive/segment_breakdown.png %})
 
 ## レポートテンプレート
 
@@ -41,13 +41,13 @@ tool:
 - 送信数
 - 配信数
 - 苦情
-- ユニークなオープン
-- ユニークなマシンがオープン
-- ユニークな非マシンオープン
+- ユニーク開封数
+- ユニークマシン開封数
+- ユニーク非マシン開封数
 - ユニーククリック数
 - 配信停止数
 - バウンス数
-- ソフトバウンド
+- ソフトバウンス数
 - 繰延
 
 #### 結果
@@ -106,7 +106,7 @@ tool:
 
 例えば、あるセグメントに 10 人のユーザーがいて、そのうちの 5 人がメール受信後に購入したとします。この 5 人のうち 1 人がメールのクリック後に購入した場合、「受信後のユニーク購入」率は 50%、「クリック後のユニーク購入」率は 10% になります。
 
-![]({% image_buster /assets/img_archive/segment_breakdown_results.png %}) 受信時のユニーク購入、受信時の収益、クリック時のユニーク購入、クリック時の収益、ユニーク受信者、ユニークメールクリックを含むメール指標を示す。
+![レポートには、受信後のユニーク購入、受信後の収益、クリック後のユニーク購入、クリック後の収益、ユニーク受信者数、ユニークなメールクリック数を含む、メール指標が表示されます。]({% image_buster /assets/img_archive/segment_breakdown_results.png %})
 
 #### 結果
 
@@ -141,34 +141,34 @@ tool:
 \[[変数](#variables)] タブ内のこのレポートには、指定したメールエンゲージメント指標について最高または最低のパフォーマンスを記録したキャンペーン、キャンバス、またはキャンバスステップが表示されます。 
 
 ユースケースには次の項目が含まれます。 
-- ユニークメール開封率が最も高い10のキャンペーン
-- メール配信停止が最も多い25のキャンバス
-- 50のキャンバスステップでユニーククリック数が最も多い
+- ユニークメール開封率が最も高い 10 件のキャンペーン
+- メールの配信停止数が最も多い 25 個のキャンバス
+- ユニーククリック数が最も多い 50 件のキャンバスステップ
 
 このレポートでは、次のメール指標を使用できます。
 - 送信数
 - 配信数
 - 苦情
-- ユニークなオープン
-- ユニークなマシンがオープン
-- ユニークな非マシンオープン
+- ユニーク開封数
+- ユニークマシン開封数
+- ユニーク非マシン開封数
 - ユニーククリック数
 - 配信停止数
 - バウンス数
-- ソフトバウンド
+- ソフトバウンス数
 - 苦情
 
 このレポートを表示するには、「**変数」**タブで以下の変数を指定する必要がある：
-- **指標**結果のランク付けに使用する指標のいずれかを選択します。
-- **報告書の数**上位10件、下位15件など、上位または下位の結果と件数を選択する。
-- **メッセージの種類**結果として、キャンペーン、キャンバス、またはキャンバスステップのいずれかを指定します。
+- **指標:** 結果のランク付けに使用する指標のいずれかを選択します。
+- **レポート件数:** 上位 10 件、下位 15 件など、上位または下位の結果と件数を選択します。
+- **メッセージタイプ:** 結果として、キャンペーン、キャンバス、またはキャンバスステップのいずれかを指定します。
 
 #### 結果
 
 結果には、選択したキャンペーン、キャンバス、またはキャンバスステップの上位 (または下位) が表示されます。例えば、クリック率の上位 10 件のキャンペーンを選択した場合、クリック率の高い順に上位 10 件のキャンペーンが表示されます。カラムには、各行（キャンペーン、キャンバス、メッセージステップ）のすべてのメールエンゲージメントメトリクスが表示される。
 
 {% endtab %}
-{% tab トップ/ボトムの購入メッセージ %}
+{% tab 購入に関するトップ/ボトムメッセージング %}
 
 ### 上位または下位のパフォーマンスを示した項目の表示
 
@@ -188,9 +188,9 @@ tool:
 - ユニークなメールクリック数
 
 このレポートを表示するには、「**変数」**タブで以下の変数を指定する必要がある：
-- **指標**結果のランク付けに使用する指標のいずれかを選択します。
-- **報告書の数**上位10件、下位15件など、上位または下位の結果と件数を選択する。
-- **メッセージの種類**結果として、キャンペーン、キャンバス、またはキャンバスステップのいずれかを指定します。
+- **指標:** 結果のランク付けに使用する指標のいずれかを選択します。
+- **レポート件数:** 上位 10 件、下位 15 件など、上位または下位の結果と件数を選択します。
+- **メッセージタイプ:** 結果として、キャンペーン、キャンバス、またはキャンバスステップのいずれかを指定します。
 - **コンバージョン期間:**メールを受信するかクリックしてから、購入または収益が発生する (と Braze が見なす) までの日数) 
 
 #### 定義
@@ -218,7 +218,7 @@ tool:
 - 送信数
 - バウンス数
 - 配信数
-- ダイレクトオープン
+- 直接開封数
 
 #### 結果
 
diff --git a/_lang/ja/_user_guide/data_and_analytics/reporting/engagement_reports.md b/_lang/ja/_user_guide/data_and_analytics/reporting/engagement_reports.md
index 697af3ba57e..cac484cd9cc 100644
--- a/_lang/ja/_user_guide/data_and_analytics/reporting/engagement_reports.md
+++ b/_lang/ja/_user_guide/data_and_analytics/reporting/engagement_reports.md
@@ -65,12 +65,12 @@ tool:
 
 ![engagement_report_add_stats][3]
 
-| Channel | 利用可能な統計値 |
+| チャネル | 利用可能な統計値 |
 | ------| --------------|
 | メール | 送信数、開封数、ユニーク開封数、クリック数、ユニーククリック数、クリックトゥーオープン、未登録、バウンス、配信数、スパム報告数 |
-| プッシュ  | 送信、開封、影響された開封、バウンス、ボディクリック |
-| ウェブプッシュ | 送信、開封、バウンス、ボディクリック |
-| アプリ内メッセージ | インプレッション、クリック、ファーストボタンのクリック、セカンドボタンのクリック |
+| プッシュ  | 送信数、開封数、誘発された開封数、バウンス数、本文クリック数 |
+| ウェブプッシュ | 送信数、開封数、バウンス数、本文クリック数 |
+| アプリ内メッセージ | インプレッション数、クリック数、ファーストボタンクリック数、セカンドボタンクリック数 |
 | Webhook  |  送信、エラー |
 | SMS | 送信、キャリアへの送信、配達確認、配達失敗、拒否 |
 {: .reset-td-br-1 .reset-td-br-2}
diff --git a/_lang/ja/_user_guide/data_and_analytics/tracking.md b/_lang/ja/_user_guide/data_and_analytics/tracking.md
index f6a9978bc4a..19e6532d48f 100644
--- a/_lang/ja/_user_guide/data_and_analytics/tracking.md
+++ b/_lang/ja/_user_guide/data_and_analytics/tracking.md
@@ -4,14 +4,14 @@ article_title: 追跡
 page_order: 5
 layout: dev_guide
 guide_top_header: "追跡"
-guide_top_text: "アプリ上の多くのユーザー行動を追跡することができる。お客様のユースケースに最適な追跡の実装方法について、以下の記事を参照することをお勧めします。"
+guide_top_text: "アプリでの多くのアクションを追跡できます。お客様のユースケースに最適な追跡の実装方法について、以下の記事を参照することをお勧めします。"
 
 page_type: landing
 description: "このランディングページには、開封ピクセル追跡やクリック追跡、アンインストール追跡、誘発された開封数、セグメント分析追跡など、アプリに追跡を実装するためのリソースがまとめられています。"
 
 guide_featured_title: "セクションの記事"
 guide_featured_list:
-  - name: オープンピクセルとクリックトラッキング
+  - name: 開封ピクセルとクリック追跡
     link: /docs/user_guide/data_and_analytics/tracking/email_tracking/
     image: /assets/img/braze_icons/users-01.svg
   - name: アンインストール追跡
diff --git a/_lang/ja/_user_guide/data_and_analytics/tracking/uninstall_tracking.md b/_lang/ja/_user_guide/data_and_analytics/tracking/uninstall_tracking.md
index ca886cba589..db75048c979 100644
--- a/_lang/ja/_user_guide/data_and_analytics/tracking/uninstall_tracking.md
+++ b/_lang/ja/_user_guide/data_and_analytics/tracking/uninstall_tracking.md
@@ -18,7 +18,7 @@ Brazeのアンインストール追跡では、以下の詳細が提供される
 2. キャンペーンレベルのアンインストール統計情報: 特定キャンペーンの \[**キャンペーンの詳細**] ページの時系列グラフに表示されます。この統計情報は、アンインストールしたキャンペーン受信者の日次数を示します。
 
 {% alert note %}
-Brazeのダッシュボードでトラッキングをアンインストールするには、オプトインする必要がある。この機能は現在、iOS、Android、Fire OSのアプリで利用できる。
+Braze ダッシュボードでアンインストール追跡にオプトインする必要があります。この機能は現在、iOS、Android、Fire OS のアプリで利用できます。
 {% endalert %}
 
 ## その仕組み
@@ -27,37 +27,37 @@ Braze では、通常のプッシュキャンペーンから基本レベルの
 
 ## アンインストール追跡をオンにする
 
-アンインストールのトラッキングは、**App Settings**ページの**Settingsの**下にある、トラッキングしたいアプリごとにオンにすることができる。
+アンインストール追跡は、追跡するアプリごとに、\[**アプリ設定**] ページの \[**設定**] で有効にできます。
 
 {% alert note %}
-古いナビゲーションを使用している場合、**App Settingsは** **Settings**であり、**Manage Settingsの**下にある。
+古いナビゲーションを使用している場合、\[**アプリ設定**] は \[**設定**] であり、\[**設定の管理**] の下にあります。
 {% endalert %}
 
 アプリのアンインストール・トラッキングがオンになっている場合、24時間以内にセッションを記録していない、またはプッシュを受け取っていないユーザーに対して、バックグラウンド・プッシュ・メッセージが毎晩送信される。
 
 ### 構成
 
-iOSアプリケーションのアンインストールトラッキングを設定するには、\[utility method]\[iOS docs].Androidアプリケーションの場合は、\[`BrazeNotificationUtils.isUninstallTrackingPush()`][8].Brazeがアンインストールを検出した場合、アンインストール追跡、または通常のプッシュキャンペーン配信のいずれであっても、ユーザーにおけるアンインストールの最良推定時間を記録する。この時間は、標準属性としてユーザープロファイルに保存され、ウィンバックキャンペーンのためのユーザーセグメントを定義するために使用することができる。
+iOS アプリケーションのアンインストール追跡を構成するには、\[utility method]\[iOS docs] を使用します。Android アプリケーションの場合は、\[`BrazeNotificationUtils.isUninstallTrackingPush()`][8] を使用します。Brazeがアンインストールを検出した場合、アンインストール追跡、または通常のプッシュキャンペーン配信のいずれであっても、ユーザーにおけるアンインストールの最良推定時間を記録する。この時刻はユーザープロファイルに標準属性項目として保存され、奪還キャンペーンのユーザーのセグメントを定義するために使用できます。
 
 ## アンインストールによるセグメントのフィルタリング
 
-**セグメント**ページの**アンインストールフィルターは**、時間範囲内にアプリをアンインストールしたユーザーを選択する。アンインストールの正確な時刻を特定することは難しいため、アンインストールフィルタは、アンインストールするすべての人がある時点でセグメントに該当するように、より広い時間範囲を持つことを推奨する。
+\[**セグメント**] ページの「**アンインストール済み**」フィルターを使用すると、一定期間内にアプリをアンインストールしたユーザーを選択できます。アンインストールの正確な時刻を特定することは難しいため、アンインストールフィルタは、アンインストールするすべての人がある時点でセグメントに該当するように、より広い時間範囲を持つことを推奨する。
 
-![セグメントをアンインストールする][5]
+![アンインストールのセグメント][5]
 
 ### アプリレベルの分析
 
-アンインストールに関する日々の統計は**ホームページに**掲載されている。このグラフは、Brazeが提供する他の統計と同様に、アプリやセグメントごとに分類することができる。**パフォーマンス概要**セクションで、日付範囲と、必要であればアプリを選択する。そして、「**パフォーマンス・オーバー・タイム」**グラフまでスクロールダウンし、以下のようにする：
+アンインストールに関する日次統計は \[**ホーム**] ページに表示されます。このグラフは、Brazeが提供する他の統計と同様に、アプリやセグメントごとに分類することができる。**パフォーマンス概要**セクションで、日付範囲と、必要であればアプリを選択する。そして、「**パフォーマンス・オーバー・タイム」**グラフまでスクロールダウンし、以下のようにする：
 
 1. **Statistics For]**ドロップダウンで、\[**Uninstalls]**を選択する。
-2. **Breakdown "**ドロップダウンで、"**By segment**"を選択する。
+2. \[**内訳**] ドロップダウンで、\[**セグメント別**] を選択します。
 3. **内訳値**ドロップダウンで、グラフに含めるセグメントを選択する。
 
 {% alert note %}
 アンインストール追跡が有効になっていないアプリでは、一部のユーザー (プッシュ通知対象のユーザー) のアンインストール数のみが報告されるため、日次アンインストール総数は表示されている数より多くなる可能性があります。
 {% endalert %}
 
-![グラフ選択をアンインストールする][2]
+![アンインストールグラフの選択肢][2]
 
 ## キャンペーンのアンインストール追跡
 
@@ -69,13 +69,13 @@ iOSアプリケーションのアンインストールトラッキングを設
 
 ### その仕組み
 
-Braze は、ユーザーのデバイスに送信されたプッシュメッセージが Firebase Cloud Messaging (FCM) または Apple プッシュ通知サービス (APN) から、アプリがもうインストールされていないというシグナルを返すタイミングを観察することで、アンインストールを追跡します。特定のアプリでグローバルアンインストールトラッキングがオンになっている場合、ユーザーがアンインストールしたかどうかを検出するために、毎日サイレントプッシュメッセージを送信する。この "サイレント "プッシュは、（ユーザーがアプリの設定でサイレントプッシュを無効にしていない限り）すべてのユーザーに送信されるが、プッシュはユーザーには表示されない。ユーザーがアンインストールしたことを検出した場合、我々はアンインストールする：
+Braze は、ユーザーのデバイスに送信されたプッシュメッセージが Firebase Cloud Messaging (FCM) または Apple プッシュ通知サービス (APN) から、アプリがもうインストールされていないというシグナルを返すタイミングを観察することで、アンインストールを追跡します。特定のアプリでグローバルアンインストールトラッキングがオンになっている場合、ユーザーがアンインストールしたかどうかを検出するために、毎日サイレントプッシュメッセージを送信する。この「サイレント」プッシュはすべてのユーザーに送信されますが (ユーザーがアプリ設定でサイレントプッシュを無効にしている場合を除く)、ユーザーには表示されません。ユーザーがアンインストールされたことを検出すると、次の処理が行われます。
 
-* アプリの総アンインストール数を1増やす。
-* 過去24時間以内にユーザーが受信に成功したすべてのキャンペーンのアンインストールカウントを1増やす。
+* アプリの総アンインストール数を 1 増やします。
+* ユーザーが過去 24 時間に正常に受信したすべてのキャンペーンのアンインストール数を 1 増やします。
 * あるユーザーが24時間以内に3つのキャンペーンを受け、その後アンインストールした場合、3つのキャンペーンすべてについて「アンインストール」のカウントをインクリメントする。
 
-アンインストール追跡には、FCM と APN によるこの情報に関する制限が適用されます。Brazeは、FCMまたはAPNからユーザーがアンインストールしたことが通知された場合にのみアンインストールカウントを増加させるが、これらのサードパーティシステムは、任意の時点でアンインストールを通知する権利を有する。その結果、アンインストールの追跡は、正確な統計とは対照的に、方向性の傾向を検出するために使用されるべきである。
+アンインストール追跡には、FCM と APN によるこの情報に関する制限が適用されます。Brazeは、FCMまたはAPNからユーザーがアンインストールしたことが通知された場合にのみアンインストールカウントを増加させるが、これらのサードパーティシステムは、任意の時点でアンインストールを通知する権利を有する。そのため、正確な統計情報ではなく、方向性の傾向を検出するには、アンインストール追跡を使用する必要があります。
 
 アンインストール・トラッキングの使い方については、ブログ記事\[アンインストール・トラッキング]を参照のこと：その強みと限界についての業界的考察][7].
 
diff --git a/_lang/ja/_user_guide/data_and_analytics/user_data_collection/user_import.md b/_lang/ja/_user_guide/data_and_analytics/user_data_collection/user_import.md
index 659ceaffca5..b77fd6d8eec 100644
--- a/_lang/ja/_user_guide/data_and_analytics/user_data_collection/user_import.md
+++ b/_lang/ja/_user_guide/data_and_analytics/user_data_collection/user_import.md
@@ -10,16 +10,14 @@ description: "このリファレンス記事では、REST API、クラウドデ
 
 > Braze には、次のようにユーザーデータをプラットフォームにインポートするさまざまな方法が用意されています。SDK、API、クラウドデータ取り込み、テクノロジーパートナー連携、CSV。
 
-{% multi_lang_include email-via-sms-warning.md %}
-
-先に進む前に、Brazeはインポート時にHTMLデータをサニタイズ（検証または適切なフォーマット）しないことに注意すること。つまり、Web のパーソナライゼーション用にインポートしたすべてのデータから、スクリプトタグを取り除く必要があります。
+進む前に、Brazeはインポート中にHTMLデータをサニタイズ（検証または適切にフォーマット）しないことに注意してください。つまり、Web のパーソナライゼーション用にインポートしたすべてのデータから、スクリプトタグを取り除く必要があります。
 
-ウェブブラウザでのパーソナライズ使用を特に意図したデータをBrazeにインポートする場合は、ウェブブラウザでレンダリングされたときに悪意を持って利用される可能性のあるHTML、JavaScript、その他のスクリプトタグが取り除かれていることを確認すること。  
+Web ブラウザでのパーソナライゼーション用に特別に意図されたデータをBraze にインポートする場合は、Web ブラウザでレンダリングされたときに悪意で利用される可能性があるHTML、JavaScript、またはその他のスクリプトタグが削除されていることを確認してください。  
 
-HTMLの場合は、Braze Liquidフィルタ(`strip_html`)を使って、レンダリングされたテキストをHTMLエスケープすることもできる。以下に例を示します。
+別の方法として、HTML の場合は、Braze の Liquid フィルター (`strip_html`) を HTML のエスケープ付きテキストに使用できます。以下に例を示します。
 
 {% tabs local %}
-{% tab インプット %}
+{% tab 入力 %}
 {% raw %}
 ```liquid
 {{ "Have <em>you</em> read <strong>Ulysses</strong>?" | strip_html }}
@@ -37,29 +35,126 @@ Have you read Ulysses?
 
 ## REST API
 
-`/users/track` エンドポイント][12] を使って、ユーザーのカスタム・イベント、ユーザー属性、購入を記録することができる。
+[`/users/track` endpoint][12] を使用して、ユーザのカスタムイベント、ユーザ属性、および購入を記録します。
 
 ## クラウドデータ取り込み
 
-Brazeの\[Cloud Data Ingestion][14] ]を使って、ユーザー属性をインポートし、管理することができる。 
+ユーザー属性をインポートおよび維持するには、ブレーズ[クラウドデータ取り込み][14] を使用します。 
 
 ## CSV インポート
 
-**Audience**>**Import Users（** **オーディエンス**>**ユーザーのインポート**）からCSVファイルをアップロードして、ユーザー・プロフィールを更新することもできる。
+CSVファイルから**オーディエンス** > **ユーザーのインポート**を通じてユーザープロフィールをアップロードおよび更新できます。
 
-この機能は、靴のサイズなどのカスタム属性に加えて、名やメールアドレスなどのユーザー属性の記録と更新をサポートしています。`external_id` 、またはユーザー・エイリアスの2つの一意のユーザー識別子のいずれかを指定することで、CSVをインポートできる。
+CSV インポートでは、シューサイズなどのカスタム属性に加えて、ファーストネームや電子メールなどのユーザー属性の記録と更新がサポートされます。CSV をインポートするには、2 つの一意のユーザー識別子 `external_id` またはユーザーエイリアスのいずれかを指定します。
 
 {% alert note %}
-`external_id` を持つユーザーと持たないユーザーを混ぜてアップロードする場合は、インポートごとに1つのCSVを作成する必要がある。1 つの CSV に `external_ids` とユーザーエイリアスの両方を含めることはできません。
+`external_id` を持つユーザとユーザが混在してアップロードする場合は、インポートごとに1 つのCSV を作成する必要があります。1 つの CSV に `external_ids` とユーザーエイリアスの両方を含めることはできません。
+{% endalert %}
+
+### CSV の作成
+
+Braze にはいくつかのデータ型があります。CSV ファイルを使用してユーザープロファイルをインポートまたは更新する場合、デフォルトのユーザー属性またはカスタム属性を作成または更新できます。
+
+- デフォルトのユーザー属性は Braze の予約キーです。`first_name`、`email` などがあります。
+- カスタム属性は、お客様のビジネスに合わせてカスタマイズされます。例えば、旅行予約アプリには、`last_destination_searched` というカスタム属性を作成できます。
+
+{% alert important %}
+顧客データをインポートするときに、使用する列ヘッダーは、デフォルトのユーザー属性と正確に一致する必要があります (スペル、大文字小文字の区別)。一致しない場合、Braze は自動的にそのユーザープロファイルにカスタム属性を作成します。
+{% endalert %}
+
+Braze は、最大 500 MB のファイルから標準 CSV 形式のユーザーデータを受け入れます。ダウンロード可能な CSV テンプレートについては、インポートに関する前述のセクションを参照してください。
+
+#### データポイントの考慮事項
+
+CSV ファイルからインポートされた各顧客データは、ユーザープロファイルの既存の値を上書きし、external ID および空白の値を除き、1 データポイントとしてカウントされます。 
+
+- CSV ファイルからアップロードされた外部ID は、データポイントを消費しません。既存の Braze ユーザーのセグメンテーションを行うために、external ID のみを CSV でアップロードする場合、データポイントを消費せずに実行できます。インポートにユーザメールや電話番号などの追加データを追加すると、既存のユーザデータが上書きされ、データポイントが消費されます。
+  - セグメンテーション目的の CSV インポート (唯一のフィールドとして `external_id`、`braze_id`、または `user_alias_name`を使用して行われたインポート) は、データポイントを消費しません。
+- 空白の値はユーザープロファイルの既存の値を上書きしないため、CSV ファイルに既存のすべてのユーザー属性を含める必要はありません。
+- `email_subscribe`、`push_subscribe`、`subscription_group_id`、または `subscription_state` を更新しても、データポイントは消費されません。
+
+{% alert important %}
+CSV インポートまたはAPI を介してユーザに`language` または`country` を設定すると、Braze がSDK を介してこの情報を自動的にキャプチャすることができなくなります。
 {% endalert %}
 
+#### デフォルトのユーザーデータ列のヘッダー
+
+| ユーザープロファイル フィールド | データ型 | 情報 | 必須 |
+|---|---|---|---|
+| `external_id` | string | 顧客固有のユーザー識別子 | はい。次の注記を参照してください。 |
+| `user_alias_name` | string | 匿名ユーザーの一意のユーザー識別子。`external_id` に代わるものです。 | いいえ。次の注記を参照してください。 |
+| `user_alias_label` | string | ユーザーのエイリアスをグループ化するための一般的なラベル。 | `user_alias_name` を使用する場合は、はい。 |
+| `first_name` | string | ユーザーが自分で指定した名 (例: `Jane`)。 | いいえ |
+| `last_name` | string | ユーザーが指定したユーザーの姓 (例: `Doe`)。 | いいえ |
+| `email` | string | ユーザーが指定したユーザーのメール (例: `jane.doe@braze.com`)。 | いいえ |
+| `country` | string | 国コードは、ISO-3166-1アルファ2標準（例えば、`GB`）でBrazeに渡す必要があります。 | いいえ |
+| `dob` | string | 「YYYY-MM-DD」の形式で渡す必要があります （例：`1980-12-21`)。これにより、ユーザーの生年月日がインポートされ、「今日」が誕生日のユーザーをターゲットにすることができます。 | いいえ |
+| `gender` | string | 「M」、「F」、「O」(その他)、「N」(該当なし)、「P」(言いたくない) または「nil」(不明)。 | いいえ |
+| `home_city` | string | ユーザーが示したユーザーの自宅の市区町村 (例えば、`London`)。 | いいえ |
+| `language` | string | 言語はISO-639-1標準（例：`en`）でBrazeに渡す必要があります。<br>[受け入れ可能な言語のリスト][1]を参照してください。 | いいえ |
+| `phone` | string | ユーザーが指定した電話番号。`E.164` 形式 (`+442071838750` など)。<br> フォーマットのガイダンスについては、[ユーザー電話番号][2]を参照してください。 | いいえ |
+| `email_open_tracking_disabled` | ブール値 | true または false が受け入れられます。 このユーザーに送信されるすべての将来のメールに開封トラッキングピクセルが追加されないようにするには、trueに設定します。   | いいえ |
+| `email_click_tracking_disabled` | ブール値 | true または false が受け入れられます。 将来のメール内のすべてのリンクに対するクリックトラッキングを無効にするには、trueに設定します。このユーザーに送信されます。 | いいえ |
+| `email_subscribe` | string | 使用できる値は、`opted_in` (メールメッセージの受信を明示的に登録)、`unsubscribed` (メールメッセージの受信を明示的に拒否)、`subscribed` (明示的に登録も拒否もしていない) です。 | いいえ |
+| `push_subscribe` | string | 使用できる値は、`opted_in` (プッシュメッセージの受信を明示的に登録)、`unsubscribed` (プッシュメッセージの受信を明示的に拒否)、`subscribed` (登録も拒否もしていない) です。 | いいえ |
+| `time_zone` | string | タイムゾーンは、IANA タイムゾーンデータベースと同じ形式で Braze に渡す必要があります (`America/New_York`、`Eastern Time (US & Canada)` など)。  | いいえ |
+| `date_of_first_session`<br><br> `date_of_last_session`| string | 以下の ISO 8601 形式のいずれかで渡すことができます。{::nomarkdown}<ul> <li> 「YYYY-MM-DD」 </li> <li> 「YYYY-MM-DDTHH:MM:SS+00:00」 </li> <li> 「YYYY-MM-DDTHH:MM:SSZ」 </li> <li> 「YYYY-MM-DDTHH:MM:SS」(2019-11-20T18:38:57 など) </li> </ul> {:/} | いいえ |
+| `subscription_group_id` | string | サブスクリプショングループの`id`。この識別子は、ダッシュボードの [購読グループ] ページにあります。 | いいえ |
+| `subscription_state` | string | `subscription_group_id` で指定されたサブスクリプショングループのサブスクリプション状態。使用できる値は、`unsubscribed` (購読グループに含まれない) または `subscribed` (購読グループに含まれる) です。 | いいえ。しかし `subscription_group_id` が使用されている場合は強くお勧めします。 |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
+{% alert note %}
+`external_id` 自体は必須でありませんが、以下のフィールドの 1 つを含める**必要があります**。
+- `external_id`:顧客固有のユーザー識別子 <br> \- または -
+- `braze_id`:既存の Braze ユーザーについて取得される一意のユーザー識別子 <br> \- または -
+- `user_alias_name`:匿名ユーザーの一意のユーザー識別子
+{% endalert %}
+
+### CSV のインポート
+
+CSV ファイルをインポートするには、[**ユーザーインポート**] ページの [**オーディエンス**] セクションに移動します。ここには、最近のインポートがリストされた表があり、アップロード日、アップローダー名、ファイル名、ターゲティングの使用可能性、インポートされた行数、各インポートのステータスなどの詳細が表示されます。
+
+![][3]
+
+[**ファイルを参照**] を選択し、ファイルを選択します。Braze はファイルをアップロードし、各列の列ヘッダーとデータ型をチェックします。
+
+CSV テンプレートをダウンロードする場合は、このページの「[external ID を使用するインポート](#importing-with-external-id)」または「[ユーザーエイリアスを使用するインポート](#importing-with-user-alias)」のセクションを参照してください。
+
+{% alert important %}
+CSV インポートでは大文字と小文字が区別されます。つまり、CSV インポートに大文字が含まれていると、フィールドが標準属性ではなくカスタム属性として書き込まれます。例えば、「email」は正しい標準属性項目ですが、「Email」はカスタム属性として書き込まれます。
+{% endalert %}
+
+アップロードが完了すると、ファイルの内容のプレビューが表示されたモーダルが表示されます。このテーブルのすべての情報は、CSV ファイルの最上部の数行の値に基づきます。列ヘッダーの場合、標準属性は通常のテキストで表記されますが、カスタム属性はイタリック体で表記され、括弧内にそのタイプが示されます。ポップアップの上部には、ファイルの概要も表示されます。
+
+同時に複数の CSV をインポートできます。CSVインポートは同時に実行されるため、更新の順序がシリアルであることは保証されません。CSV インポートを順番に実行する必要がある場合は、CSV インポートが終了するまで待ってから、2 番目のインポートをアップロードします。
+
+アップロード中にファイルに不正な形式が見つかった場合、これらのエラーがサマリーとともに表示されます。たとえば、ファイルに不正形式行が含まれている場合、ファイルをインポートするときにそのエラーがプレビューに記録されます。そのため、エラーがあってもファイルをインポートできますが、インポートの開始後にキャンセルしたりロールバックしたりすることはできません。プレビューを確認し、エラーが表示された場合は、インポートをキャンセルしてファイルを修正してください。 
+
+{% alert important %}
+Braze はプレビューの入力ファイルのすべての行をスキャンしないため、アップロード前に完全なCSV ファイルを調べます。これは、このプレビューの生成中にブレーズがキャッチしないエラーが存在する可能性があることを意味します。
+{% endalert %}
+
+形式が正しくない行や external ID のない行はインポートされません。その他すべてのエラーはインポートできますが、セグメント作成時のフィルター処理が困難になる可能性があります。詳細については、「[トラブルシューティング](#troubleshooting)」セクションを参照してください。
+
+![CSV アップロードが完了し、1 つの列にデータ型が混在するエラーが発生した場合][4]{: style="max-width:70%"}
+
+{% alert warning %}
+エラーの検出はデータ型とファイル構造のみに基づきます。例えば、メールアドレスの形式が正しくなくても、文字列として解析できるため、インポートされます。
+{% endalert %}
+
+アップロードしたファイルに問題がないことを確認したら、インポートを開始します。ポップアップが閉じ、バックグラウンドでインポートが開始されます。5 秒ごとに更新される**User Import** ページ、または**Recent Imports** ボックスの更新ボタンを押すと、進行状況を追跡できます。
+
+[**処理した行数**] の下に、インポートの進捗状況が表示されます。インポートが完了すると、ステータスが [**完了**] に変化します。インポート中も Braze ダッシュボードの他の機能を使用でき、インポートの開始と終了時に通知を受け取ります。
+
+インポートプロセスでエラーが発生した場合、黄色の警告アイコンがファイルの総行数の横に表示されます。アイコンにカーソルを合わせると、特定の行が失敗した理由の詳細が表示されます。インポートが完了すると、すべてのデータが既存のプロファイルに追加されるか、新規プロファイルが作成されます。
+
 ### external ID を使用するインポート
 
-顧客データをインポートする場合、各顧客の一意の識別子 (`external_id` とも呼ばれる) を指定する必要があります。CSVインポートを開始する前に、Brazeでユーザーをどのように識別するかをエンジニアリングチームから理解しておくことが重要である。通常、これは内部データベースIDである。これは、モバイルとウェブでBraze SDKがユーザーを識別する方法と一致するはずであり、各顧客がデバイスを問わずBraze内で単一のユーザープロファイルを持つように設計されている。Braze \[ユーザープロファイルのライフサイクル]][13] についてもっと読む。
+顧客データをインポートする場合は、各顧客の一意の識別子(`external_id`) を指定する必要があります。CSV インポートの開始前に、Braze によるユーザーの識別方法を開発チームから聞いて理解しておくことが重要です。通常、これは内部データベースIDです。これは、モバイルと Web で Braze SDK がユーザーを識別する方法と一致する必要があり、各顧客がデバイスを問わず Braze 内で単一のユーザープロファイルを持つように設計されています。詳細については、Braze の[「ユーザープロファイルのライフサイクル」][13]を参照してください。
 
 インポートで `external_id` を指定すると、Braze は、同じ `external_id` を持つ既存のユーザーを更新します。`external_id` が見つからない場合は、その external_id を持つ新規ユーザーを作成します。
 
-**ダウンロード:** \[CSV インポートのテンプレート]\[テンプレート］
+**ダウンロード:** [CSV インポートのテンプレート][template]
 
 ### ユーザーエイリアスを使用するインポート
 
@@ -73,7 +168,7 @@ Brazeの\[Cloud Data Ingestion][14] ]を使って、ユーザー属性をイン
 | user_alias_name | user_alias_label | last_name | email | sample_attribute |
 | --- | --- | --- | --- | --- |
 | 182736485 | my_alt_identifier | Smith | smith@user.com | TRUE |
-| 182736486 | my_alt_identifier | グエン | nguyen@user.com | FALSE |
+| 182736486 | my_alt_identifier | Nguyen | nguyen@user.com | FALSE |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
 
 インポート時に `user_alias_name` と`user_alias_label` の両方を指定すると、Braze は同じ `user_alias_name` と`user_alias_label` を使用して既存のユーザーを更新します。ユーザーが見つからない場合、Braze はその `user_alias_name` を設定して新規ユーザーを作成します。
@@ -82,107 +177,52 @@ Brazeの\[Cloud Data Ingestion][14] ]を使って、ユーザー属性をイン
 既存のユーザーがすでに `external_id` を持っている場合、CSV インポートを使用して `user_alias_name` を更新することはできません。この場合、関連する `user_alias_name` を持つ新規ユーザープロファイルが作成されます。エイリアスのみを持つユーザーを `external_id` に関連付けるには、[ユーザーの識別エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_identify/)を使用します。
 {% endalert %}
 
-**ダウンロード:** \[CSV によるエイリアスインポートのテンプレート]\[template_alias］
+**ダウンロード:** [CSV によるエイリアスインポートのテンプレート][template_alias]
 
 ### Braze ID を使用するインポート
 
-`external_id` または`user_alias_name` /`user_alias_label` 値の代わりに内部 Braze ID 値を使用して Braze の既存のユーザープロファイルを更新するには、列のヘッダーに`braze_id` を指定する。
+`external_id` または `user_alias_name` および `user_alias_label` 値の代わりに内部 Braze ID 値を使用して、Braze の既存のユーザープロファイルを更新するには、列のヘッダーとして `braze_id` を指定します。
 
-セグメンテーション内のCSVエクスポートオプションでBrazeからユーザーデータをエクスポートし、それらの既存ユーザーに新しいカスタム属性を追加したい場合に役立つ。
+これは、セグメンテーション内のCSVエクスポートオプションを使用してBrazeからユーザーデータをエクスポートし、既存のユーザーに新しいカスタム属性を追加したい場合に役立ちます。
 
 {% alert important %}
 `braze_id` と CSV インポートを使用して、新規ユーザーを作成することはできません。この方法は、Braze プラットフォーム内で既存のユーザーを更新する場合にのみ使用できます。
 {% endalert %}
 
 {% alert tip %}
-BrazeダッシュボードからのCSVエクスポートでは、`braze_id` の値が`Appboy ID` と表示されることがある。このIDはユーザーの`braze_id` と同じになるので、CSVを再インポートする際にこの列の名前を`braze_id` に変更すればよい。
-{% endalert %}
-
-### CSV の作成
-
-Braze にはいくつかのデータ型があります。CSV ファイルを使用してユーザ プロファイルをインポートまたは更新する場合、デフォルト のユーザ属性またはカスタム属性を作成または更新することができる。
-
-- デフォルトのユーザー属性は Braze の予約キーです。`first_name`、`email` などがあります。
-- カスタム属性は、お客様のビジネスに合わせてカスタマイズされます。例えば、旅行予約アプリには、`last_destination_searched` というカスタム属性を作成できます。
-
-{% alert important %}
-顧客データをインポートするときに、使用する列ヘッダーは、デフォルトのユーザー属性と正確に一致する必要があります (スペル、大文字小文字の区別)。一致しない場合、Braze は自動的にそのユーザープロファイルにカスタム属性を作成します。
-{% endalert %}
-
-Braze は、最大 500 MB のファイルから標準 CSV 形式のユーザーデータを受け入れます。ダウンロード可能な CSV テンプレートについては、インポートに関する前述のセクションを参照してください。
-
-#### データポイントの考慮事項
-
-CSVファイルからインポートされた各顧客データは、外部IDと空白の値を除き、ユーザープロファイル上の既存の値を上書きし、データポイントとしてカウントされる。 
-
-- CSVファイルからアップロードされた外部IDはデータポイントを消費しない。既存の Braze ユーザーのセグメンテーションを行うために、external ID のみを CSV でアップロードする場合、データポイントを消費せずに実行できます。インポート時にユーザーのEメールや電話番号などのデータを追加すると、既存のユーザーデータが上書きされ、データポイントが消費されてしまう。
-  - セグメンテーション目的のCSVインポート（`external_id` 、`braze_id` 、`user_alias_name` を唯一のフィールドとしてインポート）は、データポイントを消費しない。
-- 空白の値はユーザープロファイルの既存の値を上書きしないため、CSV ファイルに既存のすべてのユーザー属性を含める必要はありません。
-- `email_subscribe`、`push_subscribe`、`subscription_group_id`、または `subscription_state` を更新しても、データポイントは消費されません。
-
-{% alert important %}
-CSVインポートまたはAPIを通じてユーザーに`language` または`country` を設定すると、BrazeがSDKを通じて自動的にこの情報を取得するのを防ぐことができる。
-{% endalert %}
-
-#### デフォルトのユーザーデータ列のヘッダー
-
-| ユーザー・プロファイル・フィールド | データ型 | インフォメーション | 必須 |
-|---|---|---|---|
-| `external_id` | string | 顧客固有のユーザー識別子。 | はい。 |
-| `user_alias_name` | string | 匿名ユーザー用の一意のユーザー識別子。`external_id` に代わるものだ。 | いや、次の注を参照されたい。 |
-| `user_alias_label` | string | ユーザー・エイリアスをグループ化するための共通のラベル。 | `user_alias_name` を使用する場合は「はい」である。 |
-| `first_name` | string | ユーザーが指定したファーストネーム（たとえば、`Jane` ）。 | いいえ |
-| `last_name` | string | ユーザーが指定した姓（たとえば、`Doe` ）。 | いいえ |
-| `email` | string | ユーザーが指定したEメール（たとえば、`jane.doe@braze.com` ）。 | いいえ |
-| `country` | string | 国コードはISO-3166-1 alpha-2規格でBrazeに渡さなければならない（例えば、`GB` ）。 | いいえ |
-| `dob` | string | YYYY-MM-DD "のフォーマットで渡されなければならない（例えば、`1980-12-21` ）。これにより、ユーザーの生年月日がインポートされ、誕生日が「今日」のユーザーをターゲットにすることができる。 | いいえ |
-| `gender` | string | M"、"F"、"O"（その他）、"N"（該当なし）、"P"（言いたくない）、または "nil"（不明）である。 | いいえ |
-| `home_city` | string | ユーザーが指定した居住地（たとえば、`London` ）。 | いいえ |
-| `language` | string | 言語はISO-639-1規格でBrazeに渡さなければならない（例えば、`en` ）。<br>[受け入れ可能な言語のリストを][1]参照のこと。 | いいえ |
-| `phone` | string | ユーザーが指定した電話番号。`E.164` 形式（例：`+442071838750` ）。<br> 書式については、「[ユーザー電話番号][2]」を参照のこと。 | いいえ |
-| `email_open_tracking_disabled` | ブール値 | 真偽は問わない。 trueに設定すると、今後このユーザーに送信されるすべてのメールに開封トラッキングピクセルが追加されないようにする。   | いいえ |
-| `email_click_tracking_disabled` | ブール値 | 真偽は問わない。 trueに設定すると、今後このユーザーに送信されるメール内のすべてのリンクのクリックトラッキングを無効にする。 | いいえ |
-| `email_subscribe` | string | 利用可能な値は、`opted_in` （電子メールメッセージの受信を明示的に登録）、`unsubscribed` （電子メールメッセージの受信を明示的に拒否）、`subscribed` （受信も拒否もしていない）である。 | いいえ |
-| `push_subscribe` | string | 利用可能な値は、`opted_in` （プッシュメッセージの受信を明示的に登録）、`unsubscribed` （プッシュメッセージの受信を明示的に拒否）、`subscribed` （受信も拒否もしていない）である。 | いいえ |
-| `time_zone` | string | タイムゾーンは、IANAタイムゾーンデータベースと同じフォーマットでBrazeに渡さなければならない（例えば、`America/New_York` または`Eastern Time (US & Canada)` ）。  | いいえ |
-| `date_of_first_session`<br><br> `date_of_last_session`| string | 以下のISO 8601フォーマットのいずれかで渡される： {::nomarkdown}<ul> <li> 「YYYY-MM-DD」 </li> <li> "YYYY-MM-DDTHH:MM:SS+00:00" </li> <li> "YYYY-MM-DDTHH:MM:SSZ" </li> <li> 「YYYY-MM-DDTHH:MM:SS」(2019-11-20T18:38:57 など) </li> </ul> {:/} | いいえ |
-| `subscription_group_id` | string | サブスクリプション・グループの`id` 。この識別子は、ダッシュボードの購読グループページで確認できる。 | いいえ |
-| `subscription_state` | string | `subscription_group_id` で指定されたサブスクリプショングループのサブスクリプション状態。許可される値は、`unsubscribed` （サブスクリプション・グループに属さない）または`subscribed` （サブスクリプション・グループに属する）である。 | `subscription_group_id` 、強く推奨する。 |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
-
-{% alert note %}
-`external_id` 自体は必須でありませんが、以下のフィールドの 1 つを含める**必要があります**。
-- `external_id`:顧客固有のユーザー識別子 <br> \- または -
-- `braze_id`:既存の Braze ユーザーについて取得される一意のユーザー識別子 <br> \- または -
-- `user_alias_name`:匿名ユーザーの一意のユーザー識別子
+Braze ダッシュボードからの CSV エクスポートでは、`braze_id` 値に `Appboy ID` のラベルが付けられる場合があります。このIDはユーザーの`braze_id`と同じになるので、CSVを再インポートする際にこの列の名前を`braze_id`に変更できます。
 {% endalert %}
 
 ### カスタムデータのインポート
 
-ヘッダーがデフォルトのユーザーデータと完全に一致しない場合、Braze にカスタム属性が作成されます。
+デフォルトのユーザーデータと完全に一致しないヘッダーは、ブレーズ内にカスタム属性を作成します。
 
 ユーザーインポートでは、以下のデータ型が受け入れられます。
-- Datetime（[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)形式で保存すること。）
-- ブール値（TRUE/FALSE）
-- 数値（整数または浮動小数点数で、スペースやカンマは使用しない、浮動小数点数の区切りにはピリオド（.）
-- 文字列（カラム値をダブルクォーテーションで囲む限り、カンマを含むことができる）
-- 空白(空白の値は、ユーザ・プロファイル上の既存の値を上書きしないため、CSVファイルに既存のすべてのユーザ属性を含める必要はない)
+- **日時:**[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)形式で格納する必要があります
+- **Boolean:** `true` または `false`
+- **番号:**スペースまたはカンマを使用しない整数または浮動小数点数、浮動小数点数は、小数点の区切り文字としてピリオド(`.`)を使用する必要があります
+- **文字列:**列の値を囲む二重引用符(`""`)がある場合と同様にカンマを含めることができます
+- **無記号:**空白の値はユーザープロファイルの既存の値を上書きせず、CSV ファイルに既存のすべてのユーザー属性を含める必要はありません
 
 {% alert important %}
 配列、プッシュトークン、およびカスタムイベントのデータ型は、ユーザーインポートではサポートされていません。
-特に配列の場合、CSV ファイル内のコンマは列の区切り文字として解釈されるため、値でコンマが使用されているとファイルの解析でエラーが発生します。
-
-この種の値をアップロードするには、[`/users/track` エンドポイントか]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) [Cloud Data Ingestionを]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/)使う。
+特に配列の場合、CSV ファイルのカンマは列区切り文字として解釈されるため、値のカンマを使用すると、ファイルの解析にエラーが発生します。<br><br>このような値をアップロードするには、[`/users/track` エンドポイント]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)または[クラウドデータ取り込み]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/)を使用します。
 {% endalert %}
 
+### Lambda でのユーザー CSV インポート
+
+弊社のサーバーレス S3 Lambda CSV インポートスクリプトを使用して、ユーザー属性をプラットフォームにアップロードできます。このソリューションはCSVアップローダーとして機能し、CSVをS3バケットにドロップすると、スクリプトがAPIを通じてアップロードします。
+
+1,000,000 行のファイルの推定実行時間は、約5 分になります。詳細については、「[Braze へのユーザー属性 CSV のインポート]({{site.baseurl}}/user_csv_lambda/)」を参照してください。
+
 ### サブスクリプショングループのステータスの更新
 
-ユーザーのインポートにより、EメールまたはSMS購読グループにユーザーを追加できる。SMSチャンネルでメッセージを送るには、ユーザーがSMS購読グループに登録されていなければならないからである。詳細については、[SMS サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/#subscription-group-mms-enablement)を参照してください。
+ユーザーをメールまたはSMSサブスクリプショングループにユーザーインポートを通じて追加できます。これは特に SMS で便利です。ユーザーが SMS チャネルでメッセージを受信するには、SMS 購読グループに登録されていなければならないためです。詳細については、[SMS サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/#subscription-group-mms-enablement)を参照してください。
 
 サブスクリプショングループのステータスを更新する場合、CSV に以下の 2 列が必要です。
 
 - `subscription_group_id`: [サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#subscription-groups)の `id`。
-- `subscription_state`:利用可能な値は、`unsubscribed` （サブスクリプション・グループ内ではない）または`subscribed` （サブスクリプション・グループ内）である。
+- `subscription_state`: 使用できる値は、`unsubscribed` (購読グループに含まれない) または `subscribed` (購読グループに含まれる) です。
 
 <style type="text/css">
 .tg td{word-break:normal;}
@@ -203,13 +243,13 @@ CSVインポートまたはAPIを通じてユーザーに`language` または`co
     <td class="tg-0pky">A8i3mkd99</td>
     <td class="tg-0pky">Colby</td>
     <td class="tg-0pky">6ff593d7-cf69-448b-aca9-abf7d7b8c273</td>
-    <td class="tg-0pky">配信登録済み</td>
+    <td class="tg-0pky">subscribed</td>
   </tr>
   <tr>
     <td class="tg-0pky">k2LNhj8Ks</td>
     <td class="tg-0pky">Tom</td>
     <td class="tg-0pky">aea02307-a91e-4bc0-abad-1c0bee817dfa</td>
-    <td class="tg-0pky">配信登録済み</td>
+    <td class="tg-0pky">subscribed</td>
   </tr>
 </tbody>
 </table>
@@ -218,88 +258,48 @@ CSVインポートまたはAPIを通じてユーザーに`language` または`co
 ユーザーインポートでは、1 行につき `subscription_group_id` を 1 つのみ設定できます。異なる行に異なる `subscription_group_id` の値を設定できます。ただし、同じユーザーを複数のサブスクリプショングループに登録する必要がある場合は、複数のインポートを行う必要があります。
 {% endalert %}
 
-### CSV のインポート
-
-CSVファイルをインポートするには、**Audiences**セクションの**User Import**ページに行く。ここには、アップロード日、アップローダー名、ファイル名、ターゲット可用性、インポートされた行数、各インポートのステータスなどの詳細を含む、最新のインポートを一覧表示するテーブルがある。
+## ユーザーインポートからのセグメントの作成
 
-![][3]
+ユーザインポートは、**インポートを開始する前に、このCSV**からインポートされたユーザから自動的にセグメントを生成することで、セグメントを作成するためにも使用できます。
 
-**Browse Filesを**選択し、ファイルを選択する。Brazeはあなたのファイルをアップロードし、カラムヘッダーと各カラムのデータ型をチェックする。
-
-CSV テンプレートをダウンロードする場合は、このページの「[external ID を使用するインポート](#importing-with-external-id)」または「[ユーザーエイリアスを使用するインポート](#importing-with-user-alias)」のセクションを参照してください。
-
-{% alert important %}
-CSV インポートでは大文字と小文字が区別されます。つまり、CSV インポートに大文字が含まれていると、フィールドが標準属性ではなくカスタム属性として書き込まれます。例えば、「email」は正しい標準属性項目ですが、「Email」はカスタム属性として書き込まれます。
-{% endalert %}
-
-アップロードが完了すると、ファイルの内容をプレビューするモーダルが表示される。このテーブルのすべての情報は、CSV ファイルの最上部の数行の値に基づきます。列ヘッダーの場合、標準属性は通常のテキストで書かれ、カスタム属性はイタリック体で書かれ、そのタイプは括弧で示される。ポップアップの上部にはファイルの概要も表示される。
-
-同時に複数の CSV をインポートできます。CSVインポートは同時に実行されるため、更新の順序が連続であることは保証されない。CSVインポートを次々に実行する必要がある場合は、CSVインポートが終了するまで待ってから、2つ目のCSVインポートをアップロードする。
-
-Brazeがアップロード中にファイルに不正な形があることに気づいた場合、これらのエラーはサマリーとともに表示される。例えば、ファイルに不正な行が含まれている場合、ファイルをインポートする際にそのエラーがプレビューに表示される。そのため、エラーがあってもファイルをインポートできますが、インポートの開始後にキャンセルしたりロールバックしたりすることはできません。プレビューを確認し、エラーが表示された場合は、インポートをキャンセルしてファイルを修正してください。 
-
-{% alert important %}
-Brazeはプレビューのために入力ファイルのすべての行をスキャンするわけではないので、アップロードする前にCSVファイル全体を調べること。つまり、Brazeがこのプレビューを生成する際にキャッチしないエラーが存在しうるということだ。
-{% endalert %}
-
-形式が正しくない行や external ID のない行はインポートされません。その他すべてのエラーはインポートできますが、セグメント作成時のフィルター処理が困難になる可能性があります。詳細については、「[トラブルシューティング](#troubleshooting)」セクションを参照してください。
-
-![CSVのアップロードが完了したが、1つの列にデータ型が混在するエラーが発生した][4]{: style="max-width:70%"}
-
-{% alert warning %}
-エラーの検出はデータ型とファイル構造のみに基づきます。例えば、メールアドレスの形式が正しくなくても、文字列として解析できるため、インポートされます。
-{% endalert %}
-
-アップロードしたファイルに問題がないことを確認したら、インポートを開始します。ポップアップが閉じ、バックグラウンドでインポートが開始されます。その進捗状況は、5秒ごとに更新される「**ユーザーインポート」**ページ、または**「最近のインポート」**ボックスの更新ボタンを押すことで確認できる。
-
-**処理が完了**すると、ステータスは**Completeに**変わる。インポート中も Braze ダッシュボードの他の機能を使用でき、インポートの開始と終了時に通知を受け取ります。
-
-インポート処理でエラーが発生した場合、ファイルの総行数の横に黄色の警告アイコンが表示される。アイコンの上にカーソルを置くと、特定の行が失敗した理由の詳細を見ることができる。インポートが完了すると、すべてのデータが既存のプロファイルに追加されるか、新規プロファイルが作成されます。
-
-### Lambda でのユーザー CSV インポート
-
-弊社のサーバーレス S3 Lambda CSV インポートスクリプトを使用して、ユーザー属性をプラットフォームにアップロードできます。このソリューションはCSVアップローダーとして機能し、CSVをS3バケットにドロップすると、スクリプトがAPIを通じてアップロードする。
-
-100万行のファイルの推定実行時間は約5分である。詳細については、「[Braze へのユーザー属性 CSV のインポート]({{site.baseurl}}/user_csv_lambda/)」を参照してください。
-
-## セグメンテーション
+セグメント名を設定することも、デフォルト (ファイル名) をそのまま使用することもできます。セグメントの作成に使用されたファイルには、インポート完了後にセグメントを表示するためのリンクが表示されます。
 
-ユーザーインポートではユーザープロファイルの作成と更新が行われますが、セグメントの作成にも使用できます。セグメントを作成するには、インポートの開始前に、\[**この CSV からインポートされたユーザーからセグメントを自動生成する**] を選択します。
+セグメント作成に使用するフィルターにより、選択したインポートで作成された、または更新されたユーザーが選択されます。このフィルターは、[セグメントを編集] ページでその他すべてのフィルターとともに使用できます。
 
-セグメント名を設定することも、デフォルト (ファイル名) をそのまま使用することもできます。セグメントの作成に使用されたファイルには、インポート完了後にセグメントを表示するためのリンクが表示されます。
+## 考慮事項
 
-セグメント作成に使用するフィルターにより、選択したインポートで作成された、または更新されたユーザーが選択されます。このフィルターは、\[セグメントを編集] ページでその他すべてのフィルターとともに使用できます。
+{% multi_lang_include email-via-sms-warning.md %}
 
-## トラブルシューティング {#troubleshooting}
+## トラブルシューティング
 
 ### 行の欠落
 
 インポートされたユーザー数が CSV ファイルの合計行数と一致しない理由はいくつかあります。
 
-- **external ID の重複:**external ID 列が重複している場合、行の形式が正しくても、インポートされた行の形式が変形したり、行がインポートされなかったりする可能性があります。場合によっては、具体的なエラーとして報告されないこともあります。CSV に重複した external ID がないか確認してください。ある場合は、重複を削除して再度アップロードを試してください。
+- **external ID の重複:**外部ID 列が重複している場合、行が正しくフォーマットされていても、不正な形式またはインポートされていない行が発生する可能性があります。場合によっては、具体的なエラーとして報告されないこともあります。CSV に重複した external ID がないか確認してください。ある場合は、重複を削除して再度アップロードを試してください。
 - **アクセント付きの文字:**CSV 内の名前や属性に、アクセント付きの文字が含まれている可能性があります。問題を防ぐために、ファイルが UTF-8 でエンコードされていることを確認してください。
 
 ### 正しくない形式の行
 
-データを正しくインポートするためには、ヘッダー行が必要です。各行のセル数はヘッダー行と同じでなければなりません。ヘッダー行より値の数が多い、または少ない行は、インポートから除外されます。値に含まれるコンマは区切り文字として解釈され、このエラーを引き起こす可能性があります。さらに、すべてのデータが UTF-8 でエンコードされていなければなりません。
+データを正しくインポートするには、ヘッダ行が必要です。各行のセル数はヘッダー行と同じでなければなりません。ヘッダー行より値の数が多い、または少ない行は、インポートから除外されます。値のカンマは区切り文字として解釈され、このエラーが発生する可能性があります。さらに、すべてのデータが UTF-8 でエンコードされていなければなりません。
 
 CSV ファイルに空白行があり、インポートされた行数が CSV ファイルの合計行数より少ない場合、これはインポートの問題ではない可能性があります。空白行はインポートする必要がないためです。正しくインポートされた行数を調べて、インポートしようとしているユーザー数と一致することを確認してください。
 
 ### 複数のデータ型
 
-Braze では、列の各値が同じデータ型である必要があります。属性のデータ型と一致しない値があると、セグメンテーションでエラーが発生します。
+Braze では、列の各値が同じデータ型である必要があります。属性のデータ型に一致しない値は、セグメンテーションでエラーを引き起こします。
 
 ### 正しくない形式の日付
 
-[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) 形式以外の日付は、インポート時に日時として読み取られません。
+[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)形式でない日付は、インポート時に`datetimes`として読み込まれません。
 
 ### 文字列の引用符
 
-一重引用符 ('') または二重引用符 ("") で囲まれた値は、インポート時に文字列として読み取られます。
+シングル(`''`)またはダブル(`""`)でカプセル化された値は、インポート時に文字列として読み込まれます。
 
 ### データがカスタム属性としてインポートされる
 
-デフォルトのユーザーデータ (`email` や `first_name` など) がカスタム属性としてインポートされている場合は、CSV ファイルの大文字小文字とスペースを確認してください。例えば、`First_name` はカスタム属性としてインポートされますが、`first_name` はユーザープロファイルの \[名] フィールドに正しくインポートされます。
+デフォルトのユーザーデータ(`email` または`first_name` など) がカスタム属性としてインポートされた場合は、CSV ファイルの大文字と小文字の間隔を確認します。例えば、`First_name` はカスタム属性としてインポートされますが、`first_name` はユーザープロファイルの [名] フィールドに正しくインポートされます。
 
 [1]: {{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/language_codes/
 [2]: {{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/
@@ -309,8 +309,8 @@ Braze では、列の各値が同じデータ型である必要があります
 [8]: {% image_buster /assets/img_archive/user_alias_import_1.png %}
 [9]: {% image_buster /assets/img/subscription_group_import.png %}
 [12]: {{site.baseurl}}/api/endpoints/user_data/post_user_track/
- {{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/
+[13]: {{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/
 [14]: {{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/
-\[errors]:#common-errors
-\[template]: {% image_buster /assets/download_file/braze-user-import-template-csv.xlsx %}
-\[template_alias]: {% image_buster /assets/download_file/braze-user-import-alias-template-csv.xlsx %}
+[errors]:#common-errors
+[template]: {% image_buster /assets/download_file/braze-user-import-template-csv.xlsx %}
+[template_alias]: {% image_buster /assets/download_file/braze-user-import-alias-template-csv.xlsx %}
diff --git a/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/conversion_events.md b/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/conversion_events.md
index 455172c127f..1ae12dfdc17 100644
--- a/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/conversion_events.md
+++ b/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/conversion_events.md
@@ -25,21 +25,21 @@ Brazeでは、エンゲージメントの指標と、メッセージングがど
 
 - 多変量][4] キャンペーンまたはキャンバス]の当選メッセージのバリエーションを計算する。
 - キャンペーンまたはキャンバスの収益を計算する期間を指定します。
-- インテリジェント・セレクション][5] を使って、キャンペーンやキャンバスのメッセージ配分を調整する。
+- \[インテリジェントセレクション][5] を使用してキャンペーンやキャンバスのメッセージ配布を調整します。
 
 {% alert note %}
-Liquid`abort` タグを使ってメッセージが中止された場合、バリアントを通過したユーザーだけが中止される可能性がある。これは、コントロールグループを通過したユーザーへのメッセージが中止されないことを意味し、バリアントグループとコントロールグループ間でコンバージョン率が偏る可能性がある。回避策として、[セグメンテーションを使って]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment)、キャンペーンとキャンバスのエントリー時にユーザーをターゲティングする。
+Liquid の `abort` タグを使ってメッセージが中止された場合、中止の可能性があるのはバリアントを通過したユーザーだけです。これは、コントロールグループを通過したユーザーへのメッセージが中止されないことを意味し、バリアントグループとコントロールグループ間でコンバージョン率が偏る可能性がある。回避策として、[セグメンテーションを使って]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment)、キャンペーンとキャンバスのエントリー時にユーザーをターゲティングする。
 {% endalert %}
 
-## ステップ 1:コンバージョントラッキングを使ってキャンペーンを作成
+## ステップ 1: コンバージョントラッキングを使ってキャンペーンを作成
 
 目的のメッセージングチャネル用の[キャンペーンを作成]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/creating_campaign)します。キャンペーンのメッセージとスケジュールを設定したら、トラッキングするコンバージョンイベントを最大 4 つまで追加できます。
 
-2つ目（または3つ目）のコンバージョンイベントを追加することで、レポートを大幅に充実させることができるからだ。たとえば、離脱ユーザーをターゲットとするキャンペーンがあるとします。この場合、セカンダリのコンバージョンイベントとプライマリの**Starts Session**コンバージョンイベントを追加することで、キャンペーンがユーザーをアプリケーションに呼び戻すのに、どの程度効果的であるかの理解を深めることができる。 
+2 番目 （または 3 番目） のコンバージョンイベントを追加すると、レポーティングの内容が大幅に充実するため、必要と思われる数のコンバージョンイベントを使用することを強くお勧めします。たとえば、離脱ユーザーをターゲットとするキャンペーンがあるとします。この場合、セカンダリのコンバージョンイベントとプライマリの**Starts Session**コンバージョンイベントを追加することで、キャンペーンがユーザーをアプリケーションに呼び戻すのに、どの程度効果的であるかの理解を深めることができる。 
 
-## ステップ2:コンバージョンイベントを追加
+## ステップ 2: コンバージョンイベントを追加
 
-追跡したいコンバージョンイベントごとに、イベントとコンバージョン期限を選択する。
+追跡したいコンバージョンイベントごとに、イベントとコンバージョンの期限を選択します。
 
 1. 使用したいイベントの一般的なタイプを選択します。
   - **アプリを開く**: ユーザーは、指定したアプリのいずれかを開くと、コンバージョンしたものとみなされます (これがワークスペース内のすべてのアプリでのデフォルト設定)。
@@ -48,7 +48,7 @@ Liquid`abort` タグを使ってメッセージが中止された場合、バリ
   - **アプリをアップグレード**: ユーザーは、指定したいずれかのアプリでアプリのバージョンをアップグレードすると、コンバージョンしたものとみなされます (これがワークスペース内のすべてのアプリでのデフォルト設定)。Braze は可能な限りの数値比較を行い、バージョン変更がアップグレードによるものかどうかを判断します。たとえば、ユーザーがアプリケーションをバージョン 1.2.3 から 1.3.0 にアップグレードするとコンバージョンとなりますが、1.2.3 から 1.2.2 にダウングレードした場合はコンバージョンとして登録されません。しかし、アプリのバージョン名に「1.2.3-beta2」のような文字列が含まれていると、Brazeはバージョン変更がアップグレードかどうかを判断できない。この場合、ユーザーのアプリの最新バージョンが変更された時点でコンバージョンとしてカウントされます。<br><br>
 2. コンバージョンの期限を設定します。これは、コンバージョンを検討するまでにかかる可能性がある最大時間です。ユーザーが指定されたアクションを取った場合、コンバージョンがカウントされる最大30日間のウィンドウを許可するオプションがある。  
 
-![例えば、"Makes Purchase "コンバージョンイベントタイプは、何らかの購入をしたユーザーのコンバージョンを記録する。変換期限は12時間である。][2]
+![例えば、「購入する」というコンバージョンイベントタイプは、何らかの購入を行ったユーザーのコンバージョンを記録します。このコンバージョン期限は 12 時間です。][2]
 
 コンバージョンイベントを選択したら、キャンペーンの作成プロセスを続けてキャンペーンの送信を開始します。
 
@@ -68,7 +68,7 @@ Liquid`abort` タグを使ってメッセージが中止された場合、バリ
 
 コンバージョンイベントを使用すると、ユーザーのアクションをエンゲージメントポイントに紐づけることができます。とはいえ、Braze が複数のコンバージョンを処理する方法については、注意すべき点がいくつかあります。Braze がこれらのコンバージョンを追跡する方法を理解するには、以下のシナリオをご覧ください。
 
-- コンバージョンは、デバイス単位ではなく、ユーザー単位で発生する。つまり、1つのメッセージが複数のデバイスに送信されたとしても、ユーザーが変換できるのは1回だけということだ。別の例として、あるキャンペーンにコンバージョンイベントが1つだけあるとする。このキャンペーンを受け取ったユーザーがコンバージョン期限内に 2 回に分けて購入した場合、1 回のコンバージョンだけがカウントされます。
+- コンバージョンは、デバイス単位ではなく、ユーザー単位で発生する。つまり、1つのメッセージが複数のデバイスに送信されたとしても、ユーザーが変換できるのは1回だけということだ。別の例として、あるキャンペーンに「何かを購入する」という 1 つのコンバージョンイベントしかないとします。このキャンペーンを受け取ったユーザーがコンバージョン期限内に 2 回に分けて購入した場合、1 回のコンバージョンだけがカウントされます。
 - ユーザーが受信した 2 つのキャンペーンまたはキャンバスのコンバージョン期限内に 1 つのコンバージョンイベントを実行すると、そのコンバージョンは両方に登録されます。
 - ユーザーは、メッセージを開いたりクリックしたりしなくても、ウィンドウで特定のコンバージョンイベントを実行すると、コンバージョンされたユーザーとしてカウントされます。
 
diff --git a/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/creating_campaign.md b/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/creating_campaign.md
index 82aaf2dabe9..3718f9a9ad8 100644
--- a/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/creating_campaign.md
+++ b/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/creating_campaign.md
@@ -29,10 +29,10 @@ guide_featured_list:
 - name: MMSキャンペーン
   link: /docs/user_guide/message_building_by_channel/sms/mms/create/
   image: /assets/img/braze_icons/channel-sms.svg
-- name: Webフック運動
+- name: Webhook キャンペーン
   link: /docs/user_guide/message_building_by_channel/webhooks/creating_a_webhook/
   image: /assets/img/braze_icons/channel-webhook.svg
-- name: マルチチャネル運動
+- name: マルチチャネルキャンペーン
   link: /docs/user_guide/engagement_tools/campaigns/faq/#how-do-you-create-a-multichannel-campaign
   image: /assets/img/braze_icons/plus.svg
 
diff --git a/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery.md b/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery.md
index 7ceeef4a5a2..093c032e106 100644
--- a/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery.md
+++ b/_lang/ja/_user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery.md
@@ -37,8 +37,8 @@ tool: Campaigns
     - メールのエイリアスをクリックする
     - 任意のキャンペーンまたはキャンバスステップでエイリアスをクリックしました
     - メールを開く
-    - 開封 メール (machine opens)
-    - 開封メール (other opens)
+    - メールの開封 (マシンの開封数)
+    - メールの開封 (その他の開封数)
     - プッシュ通知を直接開く
     - プッシュ通知ボタンをクリックする
     - プッシュ通知ストーリーページをクリックする
@@ -52,15 +52,15 @@ tool: Campaigns
     - コンテンツカードを表示
     - コンテンツカードをクリック
     - コンテンツカードを閉じる
-- ニュースフィードカードとの対話（\[キャンペーンコネクタ][33]を参照）
-- 場所に入る
+- ニュースフィードカードとの対話 （\[キャンペーンコネクタ][33] を参照）
+- 場所の入力
 - 別のキャンペーンのために例外イベントを実行する
 - キャンバス ステップとの対話
 - ジオフェンスのトリガー
-- SMS受信メッセージの送信
+- SMS インバウンドメッセージの送信
 - WhatsAppの受信メッセージを送信
 
-また、Braze \[カスタムイベントプロパティ][32] を通じてトリガーイベントをさらにフィルターし、カスタムイベントやアプリ内購入のためのカスタマイズ可能なイベントプロパティを可能にします。この機能により、カスタムイベントの特定の属性に基づいてメッセージを受信するユーザーをさらに調整できるため、キャンペーンのパーソナライズやデータ収集の高度化が可能になります。 
+Braze \[カスタムイベントプロパティ][32] を使用してトリガーイベントをさらにフィルタリングし、カスタムイベントやアプリ内購入のイベントプロパティをカスタマイズすることもできます。この機能により、カスタムイベントの特定の属性に基づいてメッセージを受信するユーザーをさらに調整できるため、キャンペーンのパーソナライズやデータ収集の高度化が可能になります。 
 
 たとえば、「カート値」プロパティフィルターによってさらにターゲット設定された、放棄カートのカスタムイベントを含むキャンペーンがあるとします。このキャンペーンは、カートに 100 ドルから 200 ドル相当の商品を残したユーザーのみを対象としています。 
 
@@ -70,7 +70,7 @@ tool: Campaigns
 キャンペーンのセグメントが新規ユーザーに適用される場合は、トリガーイベントの「セッション開始」がユーザーの最初のアプリ起動になることがあります。(たとえば、セグメントにセッションのないユーザーが含まれている場合など)。
 {% endalert %}
 
-なお、トリガーされたキャンペーンは特定のユーザーセグメントに送信できるため、そのセグメントに参加していないユーザーは、トリガーイベントを完了してもキャンペーンを受け取ることはありません。ユーザーがセグメントに適格であってもキャンペーンを受け取っていない場合は、トリガーされたキャンペーン][49]を受け取っていない理由に関するセクションをご覧ください。
+なお、トリガーされたキャンペーンは特定のユーザーセグメントに送信できるため、そのセグメントに参加していないユーザーは、トリガーイベントを完了してもキャンペーンを受け取ることはありません。セグメントの対象であるにもかかわらずユーザーがキャンペーンを受け取っていないことに気付いた場合は、\[ユーザーがトリガーされたキャンペーンを受け取らなかった理由][49] のセクションを参照してください。
 
 ユーザーが自分のプロファイルにメールアドレスを追加したときのトリガーイベントに関しては、次のルールが適用されます。
 
@@ -96,7 +96,7 @@ tool: Campaigns
 
 ### ステップ 3: 例外イベントを選択する
 
-ユーザーがこのキャンペーンを受け取らないようにする例外イベントを選択します。これを実行できるのは、トリガーされたメッセージが一定時間遅れて送信される場合だけです。例外イベントには、購入、セッションの開始、キャンペーンの指定された\[コンバージョンイベント][18]の実行、またはカスタムイベントの実行が含まれます。ユーザーがトリガーイベントを完了したが、遅延時間によりメッセージが送信される前に例外イベントを完了した場合、そのユーザーはキャンペーンを受け取りません。例外イベントが原因でキャンペーンを受け取れなかったユーザーは、[再有効化]({{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/delivery_types/reeligibility/)するよう設定しなくても、次回にトリガーイベントを完了したときに自動的にキャンペーンの受け取りが可能になります。
+ユーザーがこのキャンペーンを受け取らないようにする例外イベントを選択します。これを実行できるのは、トリガーされたメッセージが一定時間遅れて送信される場合だけです。例外イベントには、購入、セッションの開始、キャンペーンで指定された \[コンバージョンイベント][18] のいずれかの実行、またはカスタムイベントの実行があります。ユーザーがトリガーイベントを完了したが、遅延時間によりメッセージが送信される前に例外イベントを完了した場合、そのユーザーはキャンペーンを受け取りません。例外イベントが原因でキャンペーンを受け取れなかったユーザーは、[再有効化]({{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/delivery_types/reeligibility/)するよう設定しなくても、次回にトリガーイベントを完了したときに自動的にキャンペーンの受け取りが可能になります。
 
 ![][20]
 
@@ -116,7 +116,7 @@ tool: Campaigns
 
 ユーザーが指定された時間枠内にトリガーイベントを完了したが、スケジュールされた遅延により時間枠外にメッセージを受け取る資格を得た場合、そのユーザーはキャンペーンを受け取りません。そのため、メッセージの時間枠よりも長い時間遅延を設定すると、キャンペーンを受け取るユーザーはなくなります。さらに、ユーザーの[ローカルタイムゾーン]({{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/delivery_types/scheduled_delivery/#local-time-zone-campaigns)でメッセージを送信するように選択できます。
 
-### ステップ 5: 時間枠を選択する
+### ステップ 5: 期間の選択
 
 ユーザーがその日の特定の時間帯にキャンペーンを受け取るかどうかを選択します。メッセージに時間枠を指定し、ユーザーが時間枠外にトリガーイベントを完了するか、メッセージの遅延により時間枠を逃した場合、デフォルトではユーザーはメッセージを受け取りません。
 
@@ -132,7 +132,7 @@ tool: Campaigns
 
 ### ステップ 6: 再有効化を判断する
 
-ユーザーがキャンペーンの\[再適格][24]になるかどうかを判断します。ユーザーを再有効化する場合、ユーザーがキャンペーンを再度受け取れるようになるまでの時間を指定できます。これにより、トリガーされたキャンペーンが「スパム」になるのを防ぐことができます。
+ユーザーがキャンペーンに \[再適格][24] になるかどうかを判断します。ユーザーを再有効化する場合、ユーザーがキャンペーンを再度受け取れるようになるまでの時間を指定できます。これにより、トリガーされたキャンペーンが「スパム」になるのを防ぐことができます。
 
 ![][28]
 
@@ -149,7 +149,7 @@ tool: Campaigns
 以下のいずれかにより、トリガーイベントを完了したユーザーがキャンペーンを受け取れなくなります。
 
 - 遅延時間が完全に経過する前に、ユーザーが例外イベントを完了した。
-- Liquid [`abort_message` ロジック]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/aborting_messages) が使用され、メッセージは`abort_message` ロジックまたはルールに基づいて中止されました。
+- Liquid の [`abort_message` ロジック]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/aborting_messages) が使用され、メッセージは `abort_message` ロジックまたはルールに基づいて中止されました。
 - 遅延時間により、ユーザーが期間終了後にキャンペーンを受け取る資格を得た。
 - 遅延時間により、ユーザーはその日の特定の時間帯以外にキャンペーンを受け取る資格を得た。
 - ユーザーは既にキャンペーンを受け取っており、再有効化されない。
@@ -159,16 +159,16 @@ tool: Campaigns
 
 たとえば、登録したばかりの男性ユーザーにイベントトリガーキャンペーンを送信したいとします。ユーザーが登録すると、カスタムイベント `registration` を記録すると同時にユーザーの `gender` 属性を設定します。Braze がユーザーの性別を処理する前にイベントによってキャンペーンがトリガーされ、ユーザーがキャンペーンを受け取れなくなる可能性があります。
 
-ベストプラクティスとして、キャンペーンがセグメント化されている属性がイベントの前に Braze サーバーにフラッシュされていることを確認してください。これが不可能な場合、配信を保証する最良の方法は、カスタムイベントプロパティ][48]を使用して関連するユーザープロパティをイベントに添付し、セグメンテーションフィルターの代わりに特定のイベントプロパティにプロパティフィルターを適用することです。この例では、カスタムイベントの`registration` に `gender` プロパティを追加すると、キャンペーンがトリガーされたときに必要なデータが Braze に確実に届くようになります。
+ベストプラクティスとして、キャンペーンがセグメント化されている属性がイベントの前に Braze サーバーにフラッシュされていることを確認してください。これが不可能な場合、配信を確実に行うための最善の方法は、\[カスタムイベントプロパティ][48] を使用して関連するユーザープロパティをイベントに添付し、セグメンテーションフィルターの代わりに特定のイベントプロパティにプロパティフィルターを適用することです。この例では、カスタムイベントの`registration` に `gender` プロパティを追加すると、キャンペーンがトリガーされたときに必要なデータが Braze に確実に届くようになります。
 
 さらに、キャンペーンがアクションベースであり、遅延が発生する場合は、**送信時にセグメントメンバーシップを再評価する**オプションをチェックして、メッセージが送信されたときにユーザーがターゲットオーディエンスの一部であることを確認できます。
 
 キャンペーンが特定のカスタムイベントによってトリガーされ、オーディエンスとしてSegmentを選択した場合、ユーザーはSegmentに含まれるために同じカスタムイベントを実行する必要があります。これは、アクションベースのキャンペーンをトリガーする前に、ユーザーがオーディエンスの一部である必要があることを意味します。トリガーされたキャンペーンの一般的なワークフローは次のとおりです:
 
-1. **オーディエンスに参加する:**ユーザーがカスタムイベントを実行すると、キャンペーンのターゲットオーディエンスに追加されます。
-2. **メールをトリガーする:**ユーザーはカスタムイベントを再度実行してトリガーをメールする必要があります。メールを送信する前にオーディエンスの一部である必要があります。
+1. **オーディエンスに参加する:** ユーザーがカスタムイベントを実行すると、キャンペーンのターゲットオーディエンスに追加されます。
+2. **メールをトリガーする:** ユーザーは、カスタムイベントを再度実行してメールをトリガーする必要があります。これは、メールを送信するにはユーザーがオーディエンスの一部でなければならないためです。
 
-ターゲットオーディエンスをすべてのユーザーに含めるように変更するか、イベントを実行することが期待されるユーザーがすでにキャンペーンのオーディエンスの一部であることを確認することをお勧めします。
+すべてのユーザーを含むようにターゲットオーディエンスを変更するか、イベントを実行すると予想されるユーザーが、メッセージをトリガーするキャンペーンのオーディエンスに含まれることを確認することをお勧めします。
 
 ![][51]
 
@@ -179,7 +179,7 @@ tool: Campaigns
 [19]: {% image_buster /assets/img_archive/schedule_triggered22.png %}
 [20]: {% image_buster /assets/img_archive/schedule_triggered32.png %}
 [21]: {% image_buster /assets/img_archive/schedule_triggered43.png %}
-[22]: \#ユースケース-2
+[22]: \#use-cases-2
 [24]: {% image_buster /assets/img_archive/ReEligible.png %}
 [27]: {% image_buster /assets/img_archive/schedule_triggered5.png %}
 [28]: {% image_buster /assets/img_archive/schedule_triggered6.png %}
diff --git a/_lang/ja/_user_guide/engagement_tools/campaigns/managing_campaigns/campaign_alerts.md b/_lang/ja/_user_guide/engagement_tools/campaigns/managing_campaigns/campaign_alerts.md
index c419dddb38b..28fbc4a4f9a 100644
--- a/_lang/ja/_user_guide/engagement_tools/campaigns/managing_campaigns/campaign_alerts.md
+++ b/_lang/ja/_user_guide/engagement_tools/campaigns/managing_campaigns/campaign_alerts.md
@@ -26,7 +26,7 @@ channel:
 
 アラートの設定を開始するには、キャンペーンの分析ページに移動します。\[**アラートを設定**] を選択すると、アラートの上限と下限のしきい値、およびアラートの受信者とチャネルを指定できます。
 
-![キャンペーン監視ダイアログボックスには2つのボタンがある：キャンセルして保存する。][2]
+![「キャンペーンモニタリング」ダイアログボックスにある 2 つのボタン: \[キャンセル] と \[保存]。][2]
 
 スケジュールされた定期的なキャンペーンでは、キャンペーンが送信するたびに送られるメッセージの上限と下限のしきい値を設定できます。トリガーキャンペーンでは、毎時および毎日送信されるメッセージ数の上限と下限を設定できます。
 
diff --git a/_lang/ja/_user_guide/engagement_tools/campaigns/managing_campaigns/change_your_campaign_after_launch.md b/_lang/ja/_user_guide/engagement_tools/campaigns/managing_campaigns/change_your_campaign_after_launch.md
index cf6402c3074..f69fe57e89c 100644
--- a/_lang/ja/_user_guide/engagement_tools/campaigns/managing_campaigns/change_your_campaign_after_launch.md
+++ b/_lang/ja/_user_guide/engagement_tools/campaigns/managing_campaigns/change_your_campaign_after_launch.md
@@ -15,7 +15,7 @@ description: "この記事では、キャンペーン開始後に特定の要素
 ## キャンペーンの停止
 
 キャンペーンを停止するには、\[**キャンペーンの詳細**] ページを開き、ページ右下の \[**キャンペーンを停止**] ボタンを選択します。キャンペーンが停止されると、
-- 送信スケジュールされたがキャンセルされます
+- 送信予定のメッセージはキャンセルされます
 - イニシャルテストがすでに送信されているA/Bテストは永久にキャンセルされます
 - 送信済みのメール(開封クリックなど)のイベントは追跡されます
 - キャンペーンを再開するには、**Resume**をクリックします。
diff --git a/_lang/ja/_user_guide/engagement_tools/campaigns/testing_and_more/triggered_action_based.md b/_lang/ja/_user_guide/engagement_tools/campaigns/testing_and_more/triggered_action_based.md
index a73f45467f2..8f12f21ab02 100644
--- a/_lang/ja/_user_guide/engagement_tools/campaigns/testing_and_more/triggered_action_based.md
+++ b/_lang/ja/_user_guide/engagement_tools/campaigns/testing_and_more/triggered_action_based.md
@@ -29,6 +29,6 @@ Braze のログを使用して、トリガー、送信、イベントの問題
 - [イベントユーザーログ]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/)は、API-トリガーリクエストの生のペイロード、キャンペーンをトリガーするカスタムイベント、および関連するトリガーまたはイベントプロパティを表示します。
 - [メッセージアクティビティログ]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/message_activity_log_tab/)は、エラーを記録し、特定のメッセージが配信されなかった理由を理解するのに役立ちます。
 
-## ステップ 4:テストセグメントを削除してキャンペーンを開始する
+## ステップ 4: テストセグメントを削除してキャンペーンを開始する
 
 クリックしたすべてのリンクが登録された状態でメッセージがトリガーされ、正しく表示されるようになったら、セグメントを削除してキャンペーンを更新できます。テストユーザーのインプレッションがほとんどない状態で最初からキャンペーンを開始したい場合は、キャンペーンを複製してテストユーザーセグメントなしで再開することもできます。 
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md b/_lang/ja/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md
index b3777e163df..f3cdde258f7 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md
@@ -22,15 +22,15 @@ tool: Canvas
 遅延を作成するには、まずキャンバスにステップを追加します。サイドバーからコンポーネントをドラッグ＆ドロップするか、ステップの一番下にある <i class="fas fa-plus-circle"></i> プラスのボタンを押して、\[**延期期間**] を選択します。
 
 キャンバスジャーニーに遅延を作成する場合、考慮すべき点がいくつかあります。
-- 遅延リミットは30日である。
-- ディレイ・コンポーネントは、1つの次のステップにしか接続できない。
+- 遅延制限は 30 日です。
+- 遅延コンポーネントは、次の 1 つのステップだけに接続できます。
 
 ### 時間の遅延オプション
 
 キャンバスの次のメッセージまでの遅延のタイプを選択できます。ユーザーを指定期間が経過するまで遅延させるか、特定の日時まで遅延させるかを設定できます。
 
 {% tabs %}
-  {% tab 期間終了後 %}
+  {% tab 期間より後 %}
 
   \[**期間より後**] オプションでは、設定した秒数、分数、時間数、日数、週数、および特定の時刻が経過するまでユーザーを遅延させることができます。例えば、ユーザーを 4 時間遅らせたり、1 日遅らせたりできます。 
   
@@ -40,7 +40,7 @@ tool: Canvas
     - A "calendar day" defines a day as 24 hours after a specified time, meaning you can choose to delay at company time or at a user's local time. If a time is not specified, the user will be delayed until midnight the next day in company time.
 
   {% endtab %}
-  {% tab 特定の日付まで %}
+  {% tab 特定の日まで %}
 
   \[**特定の日付まで**] オプションでは、ユーザーを特定の日時までステップに留めることができます。
 
@@ -70,11 +70,11 @@ tool: Canvas
 
 遅延には、アクティブなあるいは以前にアクティブだったキャンバスの分析ビューに 3 つの統計があります。
 
-| メートル | 説明 |
+| 指標 | 説明 |
 |---|---|
-| `Entered` | ステップの入力回数を反映する。キャンバスに再入場資格があり、ユーザーが遅延ステップを2回入力した場合、2回の入力が記録される。 |
+| `Entered` | ステップの入力回数を反映する。キャンバスに再適格性があり、ユーザーが延期期間ステップに 2 回入った場合、2 つのエントリが記録されます。 |
 | `Proceeded to Next Step` | キャンバスで次のステップに進んだエントリーの数を反映する。 |
-| `Exited Canvas` | キャンバスを終了し、次のステップに進まなかったエントリーの数を反映する。 |
+| `Exited Canvas` | キャンバスを終了し、次のステップに進まなかったエントリの数を示します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 これらの分析の時系列は、展開されたコンポーネントビューに表示されます。
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/canvas_components/user_update.md b/_lang/ja/_user_guide/engagement_tools/canvas/canvas_components/user_update.md
index 84b54c6765c..811dab52342 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/canvas_components/user_update.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/canvas_components/user_update.md
@@ -14,7 +14,7 @@ tool: Canvas
 
 > ユーザーの更新コンポーネントを使用すると、JSON コンポーザーでユーザーの属性、イベント、購入を更新できるため、API キーなどの機密情報を含める必要はありません。
 
-ユーザー・アップデートでは、アップデートは`/users/track` /分のレート制限にカウントされない。代わりに、Braze ではこれらの更新がバッチ処理されるので、Braze-to-Braze の Webhook よりも効率的に処理することができます。このコンポーネントは、請求対象外のデータポイント (サブスクリプショングループなど) の更新に使用される場合、[データポイント]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points/)を消費しないことに注意してください。
+ユーザー更新では、更新は 1 分あたり `/users/track` 件のリクエストのレート制限にはカウントされません。代わりに、Braze ではこれらの更新がバッチ処理されるので、Braze-to-Braze の Webhook よりも効率的に処理することができます。このコンポーネントは、請求対象外のデータポイント (サブスクリプショングループなど) の更新に使用される場合、[データポイント]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points/)を消費しないことに注意してください。
 
 ユーザーは、関連するユーザーの更新が完了した後でのみ、次のキャンバスステップに進みます。後続のメッセージングが作成中のユーザー更新に依存している場合は、メッセージが送信される前にこれらの更新が完了していることを確認できます。
 
@@ -36,15 +36,15 @@ tool: Canvas
 
 ### カスタム属性を削除する
 
-カスタム属性を削除するには、ドロップダウンを使用して属性名を選択します。さらに編集するには、[高度なJSONコンポーザーに](#advanced-json-composer)切り替えることができる。 
+カスタム属性を削除するには、ドロップダウンを使用して属性名を選択します。[高度な JSON コンポーザー](#advanced-json-composer)に切り替えて、さらに編集することができます。 
 
 ![][5]{: style="max-width:90%;"}
 
 ### 増加値と減少値
 
-ユーザー更新ステップは、属性値を増減させることができる。属性を選択し、**Increment By**または**Decrement Byを**選択し、数値を入力する。 
+ユーザー更新ステップによって属性値を増減させることが可能です。属性を選択し、\[**増分**] または \[**減分**] を選択して数値を入力します。 
 
-#### 毎週の進捗状況を追跡する
+#### 週次の進捗状況を追跡する
 
 イベントを追跡するカスタム属性をインクリメントすることで、ユーザーが1週間に受講したクラス数を追跡することができる。このコンポーネントを使用すると、クラスカウントを週の始めにリセットして、再びトラッキングを開始できます。 
 
@@ -54,7 +54,7 @@ tool: Canvas
 
 [オブジェクトの配列は]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects/)、データ豊富なユーザープロファイルに保存されるカスタム属性である。これにより、ユーザーとあなたのブランドとのインタラクションの履歴を作成することができる。これにより、購入履歴やライフタイムバリューの合計など、計算フィールドであるカスタム属性に基づいてセグメントを作成することができる。
 
-ユーザー更新ステップは、このオブジェクトの配列に属性を追加したり削除したりすることができる。配列を更新するには、属性リストから配列属性名を選択し、キー値を入力する。
+ユーザー更新ステップによって、このオブジェクトの配列に属性を追加したり削除したりすることが可能です。配列を更新するには、属性リストから配列属性名を選択し、キー値を入力する。
 
 #### ユースケース:ユーザーのウィッシュリストを更新する
 
@@ -66,7 +66,7 @@ tool: Canvas
 
 ユーザーがいつショッピングカートに商品を入れたか、いつ新しい商品を入れたか、いつ商品を削除したか、ショッピングカートの合計金額はいくらかなどを追跡する。 
 
-1. `shopping_cart` というオブジェクトのカスタム配列を作成する。次の例は、この属性がどのように見えるかを示している。各アイテムは、`price` を含むオブジェクトの独自のネストされた配列に、より複雑なデータを持つユニークな`product_id` を持っている。
+1. `shopping_cart` というオブジェクトのカスタム配列を作成する。次の例は、この属性がどのように見えるかを示している。各アイテムは、`price` を含むオブジェクトの独自の階層化配列に、より複雑なデータを持つユニークな `product_id` を持っています。
 
 {% raw %}
 ```javascript
@@ -92,9 +92,9 @@ tool: Canvas
 
 {:start="2"}
 2\.ユーザーがバスケットに商品を追加したときに記録される`add_item_to_cart` という[カスタムイベントを]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/)作成する。
-3\.このカスタムイベントで、ターゲットとなるユーザーとキャンバスを作ろう。さて、ユーザーが商品をカートに入れると、このキャンバスがトリガーされる。そして、そのユーザーをターゲットに直接メッセージを送ることができ、一定の金額に達した時や、一定時間カートを放棄した時など、ユースケースに沿ったクーポンコードを提供することができる。 
+3\.このカスタムイベントで、ターゲットとなるユーザーとキャンバスを作成します。さて、ユーザーが商品をカートに入れると、このキャンバスがトリガーされる。その後、そのユーザーを直接ターゲットにしたメッセージングを行い、一定の支出額に達したとき、一定の期間カートを放棄したとき、あるいはその他のユースケースに一致したときに、クーポンコードを提供することができます。 
 
-`shopping_cart` 属性は、多くのカスタムイベントの合計を運ぶ：すべてのアイテムの合計金額、カート内のアイテムの合計数、ショッピングカートにギフトが含まれている場合など。これは次のようなものだ：
+`shopping_cart` 属性は、多くのカスタムイベントの合計を運ぶ：すべてのアイテムの合計金額、カート内のアイテムの合計数、ショッピングカートにギフトが含まれている場合など。例えば、次のようになります。
 
 {% raw %}
 ```javascript
@@ -129,8 +129,8 @@ tool: Canvas
 キャンバスのトリガーイベントのプロパティを属性として保存するには、パーソナライゼーションモーダルを使ってキャンバスのエントリプロパティを抽出し、保存します。ユーザーの更新では、次のパーソナライゼーション機能もサポートされています。 
 * [コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/) 
 * [コンテンツブロック]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/)
-* [エントリー物件]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_persistent_entry_properties/)
-* リキッドロジック（[メッセージの中断を]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/aborting_messages/)含む）
+* [エントリのプロパティ]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_persistent_entry_properties/)
+* Liquid ロジック ([メッセージの中止]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/aborting_messages/)を含む)
 * オブジェクトごとに複数の属性またはイベントを更新する
 
 {% alert warning %}
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas.md b/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas.md
index bb02c7443fe..ff755c5da90 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas.md
@@ -4,7 +4,7 @@ article_title: キャンバスの作成
 page_order: 1
 layout: dev_guide
 guide_top_header: "キャンバスの作成"
-guide_top_text: "このセクションの記事は、アイデアから実行まで、ユーザーに向けて多次元のキャンバスを迅速に作成および起動する方法をガイドします。直感的なドラッグアンドドロップインターフェイスとコラボレーションのためのスペースを備えたこのビジュアルプログラミング環境を活用して、カスタマーエンゲージメント目標の最良の結果を促進することができます。"
+guide_top_text: "このセクションの記事では、アイデアからユーザーに向けた実行まで、多次元のキャンバスを迅速に作成して実施する方法について説明します。直感的なドラッグアンドドロップインターフェイスとコラボレーションのためのスペースを備えたこのビジュアルプログラミング環境を活用して、カスタマーエンゲージメント目標の最良の結果を促進することができます。"
 
 page_type: landing
 description: "このランディングページには、キャンバスの作成方法、例外イベント、終了基準、キャンバスのエントリプロパティなど、多次元キャンバスの作成と開始に役立つリソースがまとめられています。"
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas/advancement.md b/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas/advancement.md
index 5aa19a7022a..e45bbd451e6 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas/advancement.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas/advancement.md
@@ -17,7 +17,7 @@ tool: Canvas
 
 > **ユーザー昇進の動作**機能を使用すると、[キャンバスコンポーネント]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/)を進ませる基準を選択できます。 
 
-![メッセージが送信されたときにオーディエンスを進めるか、すぐにオーディエンスを進めるかの2つのオプションがあるアドバンスメントビヘイビア設定。][1]
+![オーディエンスをメッセージの送信時に進めるか、すぐに進めるかの 2 つのオプションを持つ「昇進動作」の設定。][1]
 
 ステップを進むには、ステップの基準を満たす必要があります。[メッセージ]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/)ステップでは、配信検証をオンにして、オーディエンスがメッセージ送信時に配信基準を満たしていることを確認できます。これは、キャンバスフローを使用する場合にステップの基準として考慮されます。そのため、配信検証の基準を満たさないユーザーはキャンバスから退出します。
 
@@ -65,7 +65,7 @@ tool: Canvas
 
 3 日目のプッシュで \[**オーディエンスをすぐに昇進させる**] を選択した場合、Braze がプッシュの送信を試行した時点でユーザーが先に進みます。オーディエンスのオプションに一致し、プッシュ経由でリーチできないユーザーの場合、プッシュは送信されませんが、キャンバスを先に進みます。
 
-{% details 以前のキャンバスの進行動作 %}
+{% details 以前のキャンバスの昇進動作 %}
 
 昇進動作をリリースする前の Braze では、ユーザーは、そのコンポーネントからメッセージを受信した後に、キャンバスコンポーネント内を進んでいました。その場合、キャンバスコンポーネントにメールとプッシュが含まれていると、ユーザーは、Braze がユーザーにプッシュまたはメールを送信するまで、キャンバスの次のステップに進みません。
 
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties/canvas_persistent_entry_properties.md b/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties/canvas_persistent_entry_properties.md
index 8cb2241046b..c6ace963c00 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties/canvas_persistent_entry_properties.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties/canvas_persistent_entry_properties.md
@@ -17,13 +17,13 @@ page_order: 5
 ## エントリプロパティを使用する
 
 エントリプロパティは、アクションベースおよび API トリガーのキャンバスで使用できます。これらのエントリプロパティは、キャンバスがカスタムイベント、購入、または API 呼び出しによってトリガーされた時点で定義されます。詳細については、次の記事を参照してください。
-- [キャンバスエントリー・プロパティ・オブジェクト]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/)
-- [イベント・プロパティ・オブジェクト]({{site.baseurl}}/api/objects_filters/event_object/)
+- [キャンバスエントリのプロパティオブジェクト]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/)
+- [イベントのプロパティオブジェクト]({{site.baseurl}}/api/objects_filters/event_object/)
 - [購入対象]({{site.baseurl}}/api/objects_filters/purchase_object/#purchase-product_id)
 
 これらのオブジェクトから渡されるプロパティは、Liquid タグ `canvas_entry_properties` を使用して参照できます。例えば、`\"canvas_entry_properties\" : {\"product_name\" : \"shoes\", \"product_price\" : 79.99}` を使ったリクエストの場合、{% raw %}`{{canvas_entry_properties.${product_name}}}`{% endraw %} という Liquid を追加して、メッセージに「shoes」という単語を追加できます。
 
-キャンバスが`canvas_entry_properties` Liquidタグを持つメッセージを含むとき、これらのプロパティに関連する値は、キャンバス内でユーザが移動する間保存され、ユーザがキャンバスを終了すると削除される。キャンバスエントリのプロパティは、Liquid で参照用にのみ使用できる点に注意してください。キャンバス内のプロパティをフィルタリングするには、代わりに[イベントプロパティのセグメンテーション]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/nested_objects/)を使用します。
+キャンバスに Liquid タグ `canvas_entry_properties` を持つメッセージが含まれている場合、これらのプロパティに関連付けられている値は、ユーザーのジャーニーの間保持され、ユーザーがキャンバスを退出したときに削除されます。キャンバスエントリのプロパティは、Liquid で参照用にのみ使用できる点に注意してください。キャンバス内のプロパティをフィルタリングするには、代わりに[イベントプロパティのセグメンテーション]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/nested_objects/)を使用します。
 
 {% alert note %}
 キャンバスエントリのプロパティオブジェクトの最大サイズは 50 KB に制限されています。
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/get_started/canvas_outlines.md b/_lang/ja/_user_guide/engagement_tools/canvas/get_started/canvas_outlines.md
index 8a4a89e6c46..010c06cba83 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/get_started/canvas_outlines.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/get_started/canvas_outlines.md
@@ -17,11 +17,11 @@ tool: Canvas
 Braze ラーニングでは、一般的なキャンバスの概要を解説する専用のキャンバスコースもいくつか提供しています。専門用語や概念に関する重要なインサイトについては、動画、レッスン、インタラクティブな演習を組み合わせたコースをチェックしてください。 
 - [キャンバスフローによるカスタマージャーニーの作成](https://learning.braze.com/create-customer-journeys-with-canvas-flow)
 - [新規ロイヤルティ会員のオンボーディング](https://learning.braze.com/new-loyalty-member-onboarding)
-- [失効したユーザー](https://learning.braze.com/lapsing-users)
-- [放棄されたカートユーザージャーニーの構築](https://learning.braze.com/build-an-abandoned-cart-user-journey)
+- [離脱ユーザー](https://learning.braze.com/lapsing-users)
+- [放棄カートのユーザージャーニーの構築](https://learning.braze.com/build-an-abandoned-cart-user-journey)
 
 {% alert important %}
-2023 年 2 月 28 日以降、従来のキャンバスエクスペリエンスを使用したキャンバスの作成や複製ができなくなりました。Braze では、従来のキャンバスエクスペリエンスを使用しているお客様に、キャンバスフローへの移行をお勧めしています。これは、キャンバスの構築と管理をより良く行う目的で改良された編集エクスペリエンスです。「[キャンバスからキャンバスフローへの複製]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases/)」を参照してください。
+2023 年 2 月 28 日以降、従来のキャンバスエクスペリエンスを使用したキャンバスの作成や複製ができなくなりました。Braze では、元のキャンバスエクスペリエンスを使用しているお客様に、キャンバスフローへの移行をお勧めしています。これは、キャンバスの構築と管理をより良く行う目的で改良された編集エクスペリエンスです。「[キャンバスからキャンバスフローへの複製]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases/)」を参照してください。
 {% endalert %}
 
 ### オンボーディング
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/ideas_and_strategies/best_practices.md b/_lang/ja/_user_guide/engagement_tools/canvas/ideas_and_strategies/best_practices.md
index a8cf60efac7..aada97886b7 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/ideas_and_strategies/best_practices.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/ideas_and_strategies/best_practices.md
@@ -14,15 +14,15 @@ tool: Canvas
 ## 目的を特定する
 
 「何を」、「誰が」、「なぜ」を詳しく調べてみましょう。
-- ユーザーに何を達成させようとしているのか？
-- リーチしようとしているユーザーは誰なのか？
+- ユーザーに何を達成してもらいたいのか?
+- リーチしようとしているユーザーは誰か?
 - なぜこのキャンバスを作るのか？
 
 ## 組み合わせる
 
 [キャンバスコンポーネント]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components)で、ユーザージャーニーの新たな組み合わせを実現しましょう。
-- [デシジョン・スプリットで]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/decision_split/)ユーザーを分割し、異なるワークフローを構築する。
-- [Delay]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/delay_step/)ステップでユーザー・ジャーニーの間隔を空ける。
+- [条件分岐]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/decision_split/)でユーザーを分割し、異なるワークフローを作成します。
+- [遅延]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/delay_step/)ステップでユーザージャーニーの間隔を空けます。
 - キャンバスフローの好きな場所に[スタンドアロンメッセージを]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/)追加できる。 
 
 ## より充実したメッセージを作成する
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/managing_canvases/canvas_version_history.md b/_lang/ja/_user_guide/engagement_tools/canvas/managing_canvases/canvas_version_history.md
index b3c794b4dd0..5e1cf12b70d 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/managing_canvases/canvas_version_history.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/managing_canvases/canvas_version_history.md
@@ -32,7 +32,7 @@ tool: Canvas
 
 バージョン履歴の数が増えたら、サイドバーで各バージョンの名前を変更して整理することもできます。デフォルトでは、バージョン名は以前に作成されたバージョンの数に基づく番号として生成されます。アクティブでなくなったバージョンの名前を変更すると、キャンバスの変更ログには表示されますが、バージョン履歴ビュー内のバージョンの変更ログには表示されません。
 
-![キャンバスの変更履歴の例では、2つの新しいキャンバスが作成されている。][2]{: style="max-width:85%" }
+![キャンバスの変更ログの例では、2 つの新しいキャンバスバージョンが作成されています。][2]{: style="max-width:85%" }
 
 ### バージョンを破棄する
 
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md b/_lang/ja/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md
index 7b2a9829221..1e6e452296e 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/managing_canvases/change_your_canvas_after_launch.md
@@ -15,8 +15,8 @@ tool:
 > この参考記事では、初回開始後にキャンバスで変更できることについて説明します。
 
 キャンバスフローまたはオリジナルエディタで開始したキャンバスでは、開始後に以下の方法でキャンバスを編集できます。
-* ユーザー・ジャーニーに新しいキャンバスのステップを挿入する
-* 新しいバリアントとコネクションを追加する
+* ユーザージャーニーに新しいキャンバスのステップを挿入する
+* 新しいバリアントと接続を追加する
 * バリアントの分布を調整する
 * すべてのキャンバスステップを停止または再開する
 
@@ -44,7 +44,7 @@ tool:
 
 具体的な編集のユースケースについては、[ベストプラクティス](#best-practices)のセクションを参照してください。一般的に、予期しない動作が発生する可能性もあるので、ベストプラクティスとしては、ライブキャンバスの編集を避けることをおすすめします。
 
-{% details オリジナル・キャンバス・エディター %}
+{% details オリジナルのキャンバスエディター %}
 
 {% alert important %}
 2023 年 2 月 28 日以降、従来のキャンバスエクスペリエンスを使用したキャンバスの作成や複製ができなくなりました。Braze では、従来のキャンバスエクスペリエンスを使用しているお客様に、キャンバスフローへの移行をお勧めしています。これは、キャンバスの構築と管理をより良く行う目的で改良された編集エクスペリエンスです。「[キャンバスからキャンバスフローへの複製]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases/)」を参照してください。
@@ -69,12 +69,12 @@ tool:
 これらのキャンバスの設定や情報は、キャンバスの開始後に、いずれのエディタ (オリジナルまたはキャンバスフロー) を使用しても編集できます。 
 * キャンバスの名前と説明
 * チームとタグ
-* エントリータイプ、スケジュール、コントロール
+* エントリタイプ、スケジュール、コントロール
 * サブスクリプションステータス
 * レート制限
 * フリークエンシーキャップ
 * サイレント時間
-* 対象読者
+* ターゲットオーディエンス
 
 キャンバスが開始した後は、コンバージョンイベントを編集することはできません。
 
diff --git a/_lang/ja/_user_guide/engagement_tools/canvas/testing_canvases/sending_test_canvases.md b/_lang/ja/_user_guide/engagement_tools/canvas/testing_canvases/sending_test_canvases.md
index 5da6427f730..68968ad55fc 100644
--- a/_lang/ja/_user_guide/engagement_tools/canvas/testing_canvases/sending_test_canvases.md
+++ b/_lang/ja/_user_guide/engagement_tools/canvas/testing_canvases/sending_test_canvases.md
@@ -13,7 +13,7 @@ tool: Canvas
 
 可能な限り、Braze はキャンバスを発売する前にテストすることを推奨しています。このテストは通常、Braze 環境で行います。キャンバスのテストには、キャンバスを複製し、テストユーザーをユーザージャーニーに誘導し、ユーザー行動がキャンバスで説明したものと一致するかどうかを確認することなどが含まれます。
 
-## ステップ 1:テスト計画を作成する
+## ステップ 1: テスト計画を作成する
 
 キャンバスのテストを始める前に、テスト計画を必ず作成しなければなりません。テスト計画は、キャンバスジャーニーにおける特定の分野を特定し、追跡するのに役立ちます。
 
@@ -23,7 +23,7 @@ tool: Canvas
 	- セグメントが使用されている場合、ユーザーがユーザー ジャーニーの対象となる前にキャンバスに入るための前提条件があるかもしれません。
 - テストキャンバスのメッセージには、メッセージとユーザーの両方をテスト目的で簡単に識別できるようにするために、ユーザーIDまたはメールアドレスを引き込むメッセージタイトルにLiquidが含まれていますか？
 
-## ステップ2:テストユーザーを特定する
+## ステップ 2: テストユーザーを特定する
 
 次に、意図したユーザーに実際にメッセージを送信せずに、キャンバスのステップを通過するテストユーザーのセットを特定します。テストユーザーは、Braze ダッシュボードの実際のサービスに使用されていない既存のメールアドレス、またはテスト目的のみに使用される新しいメールアドレスのどちらも可能です。 
 
@@ -31,17 +31,17 @@ tool: Canvas
 
 次はキャンバスのテストだ！元のキャンバスとテスト用キャンバスの情報を整理するため、テスト用にキャンバスの複製を作成します。
 
-キャンバスをテストする方法は2つあります。 
+キャンバスをテストするには 2 つの方法があります。 
 
-- **方法1:**重複したキャンバスで、キャンバスビルダーの**エントリオーディエンス**部分を編集して、テストユーザーのみがキャンバスの対象となるようにします。また、**メールアドレス**のテストフィルターを追加することで、自分のメールアドレスをテストユーザーとして入力することもできます。以下の例では、キャンバスを、アプリを初めて使ってから 3 日以内の 2 人のテストユーザーに限定しています。
+- **方法1:**複製されたキャンバスで、キャンバスビルダーの \[**エントリオーディエンス**] の部分を編集し、テストユーザーのみがキャンバスに適格になるようにします。また、**メールアドレス**のテストフィルターを追加することで、自分のメールアドレスをテストユーザーとして入力することもできます。以下の例では、キャンバスを、アプリを初めて使ってから 3 日以内の 2 人のテストユーザーに限定しています。
 
 ![][2]
 
-- **方法2:**[プレビュー your ユーザー paths]({{site.baseurl}}/preview_user_paths/) by selecting the **Test キャンバス** button in the footer of the キャンバス builder.
+- **方法2:**キャンバスビルダーのフッターで \[**テストキャンバス**] ボタンを選択して、[ユーザーパスをプレビュー]({{site.baseurl}}/preview_user_paths/)します。
 
-## ステップ 4:テストを開始する
+## ステップ 4: テストを開始する
 
-テストキャンバスを開始し、ユーザーが入り始めるようにします。アプリケーションでユーザーの行動を完了し、それぞれのキャンバスの旅にユーザーを送ります。
+テストキャンバスを開始し、ユーザーが入り始めるようにします。ユーザーをそれぞれのキャンバスジャーニーに送るアプリケーションのユーザーの行動を完成させます。
 
 テストユーザーがキャンバスのステップから意図したメッセージを受け取っていることを確認する。以下のような理由で、メッセージがテストユーザーに届かない場合もあります。
 
diff --git a/_lang/ja/_user_guide/engagement_tools/news_feed/news_feed_analytics_and_retargeting_data.md b/_lang/ja/_user_guide/engagement_tools/news_feed/news_feed_analytics_and_retargeting_data.md
index 2cef3eb6f8e..f4996b8c00e 100644
--- a/_lang/ja/_user_guide/engagement_tools/news_feed/news_feed_analytics_and_retargeting_data.md
+++ b/_lang/ja/_user_guide/engagement_tools/news_feed/news_feed_analytics_and_retargeting_data.md
@@ -58,7 +58,7 @@ Braze は、ユーザーがいつフィードを閲覧したか、また何回
   - ユーザーのフィードが空になる可能性があるため、このターゲティングを過度に使用しないでください。ベストプラクティスは、静的コンテンツと自動的に削除されるコンテンツを組み合わせて使用​​することです。
 - また、カードをクリックしなかったユーザーをリターゲティングして、別の行動喚起をフォローアップするのにも効果的です。
 
-![カード "Cheersをクリックしていないユーザーsを対象としたフィルター事例！Toast&quot を付与するにあたっての注意事項。][14]
+![カード「乾杯！」をクリックしていないユーザーをターゲットに表示するセグメントフィルターの例。乾杯の際にすべきこととしてはいけないこと。][14]
 
 
 [19]: {% image_buster /assets/img_archive/braze_newsfeedanalytics.png %}
diff --git a/_lang/ja/_user_guide/engagement_tools/news_feed/news_feed_categories.md b/_lang/ja/_user_guide/engagement_tools/news_feed/news_feed_categories.md
index 40b886e09cb..6aa17256f62 100644
--- a/_lang/ja/_user_guide/engagement_tools/news_feed/news_feed_categories.md
+++ b/_lang/ja/_user_guide/engagement_tools/news_feed/news_feed_categories.md
@@ -18,9 +18,9 @@ hidden: true
 
 > ニュースフィードのカテゴリを使用すると、ニュースフィードの複数のインスタンスをアプリケーションに統合できます。特定のカテゴリのニュースフィードカードのみを表示するさまざまな期間内でフィードを統合することができます。
 
-![Sweet Teeth - Buy candy in bulk!"というタイトルのニュースフィードアイテムのキャプション付きイメージカードプレビューが付いたニュースフィードパネルには、"Satisfy your sweet tooth and stop by our store. "というメッセージが添えられている！この広告に言及すると、最初のキャンディー 1 袋が 50% オフになります」というメッセージが添えられています。]ニュースフィードのカテゴリには、\[ニュース]、\[お知らせ]、\[広告]、\[ソーシャル] の 4 つのチェックボックスがあります。どのカテゴリーも選ばれていない。][1]
+![Sweet Teeth - Buy candy in bulk!"というタイトルのニュースフィードアイテムのキャプション付きイメージカードプレビューが付いたニュースフィードパネルには、"Satisfy your sweet tooth and stop by our store. "というメッセージが添えられている！この広告に言及すると、最初のキャンディー 1 袋が 50% オフになります」というメッセージが添えられています。]ニュースフィードのカテゴリには、\[ニュース]、\[お知らせ]、\[広告]、\[ソーシャル] の 4 つのチェックボックスがあります。どのカテゴリも選択されていません。][1]
 
-ニュースフィードを特定のカテゴリからのものとしてマークしても、エンド ユーザーには表示されません。デフォルトでは、特定のカテゴリを表示するようにアプリコードでフィードが特別に構成されていない限り、Braze のニュースフィードにはすべてのカテゴリのカードが表示されます。アプリコードの設定については、\[ニュースフィードカテゴリーの定義][2] を参照のこと。
+ニュースフィードを特定のカテゴリからのものとしてマークしても、エンド ユーザーには表示されません。デフォルトでは、特定のカテゴリを表示するようにアプリコードでフィードが特別に構成されていない限り、Braze のニュースフィードにはすべてのカテゴリのカードが表示されます。アプリコードの設定の詳細については、\[ニュースフィードカテゴリの定義][2] を参照してください。
 
 [1]: {% image_buster /assets/img_archive/Newsfeed_category.png %}
-[2]: {{site.baseurl}}/developer_guide/platform_integration_guides/ios/news_feed/defining_a_news_feed_category/
+/developer_ guide/platform_integration_guides/ios/news_feed/defining_a_news_feed_category/
diff --git a/_lang/ja/_user_guide/engagement_tools/segments/creating_a_segment.md b/_lang/ja/_user_guide/engagement_tools/segments/creating_a_segment.md
index aab6d2afdc2..67f9d9fae5d 100644
--- a/_lang/ja/_user_guide/engagement_tools/segments/creating_a_segment.md
+++ b/_lang/ja/_user_guide/engagement_tools/segments/creating_a_segment.md
@@ -22,14 +22,14 @@ search_rank: 3
 
 ## ステップ2:セグメントに名前を付ける
 
-**Create Segment**を選択して、セグメントの作成を開始します。セグメントに名前を付けます。絞り込むユーザーのタイプがわかるような名前にしてください。これは、キャンペーンやキャンバスでセグメントを特定するのに役立つ。曖昧なセグメント名は混乱を招く。
+セグメントの作成を開始するには、\[**セグメントを作成**] を選択します。セグメントに名前を付けます。絞り込むユーザーのタイプがわかるような名前にしてください。これは、キャンペーンまたはキャンバスにターゲットを設定するときに、セグメントを特定するのに役立ちます。曖昧なセグメント名は混乱を招く。
 
-オプションとして、以下のことができる：
+オプションとして、以下を行うことができます。
 - セグメントに説明を追加して、この視聴者の意図について詳しく説明し、他のチームメンバーが参照できるようにメモを残す。
-- [チームを]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/teams/)セグメントに加える。
+- セグメントに[チーム]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/teams/)を追加する。
 - さらに整理するために、セグメントに[タグを]({{site.baseurl}}/user_guide/administrative/app_settings/tags/)追加する。
 
-![セグメント名を "Lapsed Users "とし、セグメント説明を "This is our main Lapsed User segment to target non-actives within past 14 days "として、2つのボタンを持つセグメントモーダルを作成する：キャンセルしてセグメントを作成する。][2]{: style="max-width:70%;"}
+![セグメントに「離脱ユーザー」という名前を付け、セグメントの説明に「過去 14 日以内に非アクティブだったユーザーをターゲットとする主な離脱ユーザーセグメント」と書き込んだセグメントの作成モーダル。次の 2 つのボタンがあります: キャンセルしてセグメントを作成する。][2]{: style="max-width:70%;"}
 
 ## ステップ 3:アプリまたはプラットフォームを選択する
 
@@ -37,7 +37,7 @@ search_rank: 3
 
 例えば、アプリ内メッセージを iOS デバイスのみに送信したい場合は、iOS アプリを選択します。これにより、iOS デバイスと Android デバイスの両方を使用するユーザーは、iOS デバイスのみでメッセージを受信します。特定のアプリのリストで、\[**どのアプリも使用していないユーザー**] オプションを選択すると、セッションもアプリデータもないユーザーを含められます (通常はユーザーインポートまたは REST API で作成)。
 
-![セグメント詳細パネルで、「使用アプリ」セクションで「すべてのアプリからのユーザー」オプションを選択した状態。][5]{: style="max-width:70%;"}
+![\[使用したアプリ] セクションで \[すべてのアプリのユーザー] オプションが選択されている \[セグメント詳細] パネル][5]{: style="max-width:70%;"}
 
 ## ステップ 4:セグメントにフィルターを追加する
 
@@ -47,40 +47,40 @@ search_rank: 3
 Braze は、アプリを初めて使用するまでユーザーのプロファイルを生成しないため、アプリをまだ開いていないユーザーをターゲットにすることはできません。
 {% endalert %}
 
-#### フィルター・グループ
+#### フィルターグループ
 
-フィルターはフィルター・グループにまとめられている。すべてのフィルターは、最低1つのフィルターを持つフィルターグループの一部でなければならない。セグメントは複数のフィルターグループを持つことができる。追加するには、**Add filter groupを**選択する。フィルターグループ名の横にカーソルを置くと表示されるアイコンを選択して、フィルターグループ名を編集する。
+フィルターはフィルター・グループにまとめられている。すべてのフィルターは、最低1つのフィルターを持つフィルターグループの一部でなければならない。セグメントは複数のフィルターグループを持つことができる。1 つ追加するには、\[**フィルターグループを追加**] を選択します。フィルターグループ名の横にカーソルを置くと表示されるアイコンを選択して、フィルターグループ名を編集する。
 
-![フィルタグループの名前の横に編集アイコンがある。][14]{: style="max-width:70%;"}
+![名前の横に編集アイコンがあるフィルターグループ][14]{: style="max-width:70%;"}
 
-各フィルタの横にあるアイコンを選択すると、フィルタエディタを折りたたんだり、フィルタを複製したり、フィルタを削除したりできる。フィルターを複製した後、各ドロップダウン内でその値を調整することができる。
+各フィルターの横にあるアイコンを選択して、フィルターエディターを折りたたんだり、フィルターを複製したり削除したりします。フィルターを複製した後、各ドロップダウン内でその値を調整することができます。
 
 各フィルターグループ内のアイコンを使って、そのフィルターグループとその中のフィルターを複製したり、セグメントからそのフィルターグループを削除することもできる。
 
 #### ANDとORを使ったセグメンテーション・ロジック
 
-フィルターグループ内では、フィルターは "AND "か "OR "で結合できる。フィルター・グループ間では、グループは "AND "か "OR "で結合できる。フィルターグループを使うと、次のようなセグメンテーション・ロジックを作ることができる：
-- (AとBとC)または(CとEとF)
-- (AまたはBまたはC)と(CまたはDまたはF)
+フィルターグループ内では、フィルターを「AND」または「OR」で結合できます。フィルターグループ間では、グループを「AND」または「OR」で結合できます。フィルターグループを使うと、次のようなセグメンテーション・ロジックを作ることができる：
+- (A AND B AND C) OR (C AND E AND F)
+- (A OR B OR C) AND (C OR D OR F)
 
 フィルターに "OR "を選択すると、セグメントには、これらのフィルターの1つ、いくつか、またはすべての組み合わせを満たすユーザーが含まれることになる。AND」を選択すると、そのフィルターを通らなかったユーザーはセグメントに含まれない。
 
 {% alert tip %}
-否定的なフィルター（購読グループに "いない "など）を含むフィルターのために "OR "を選択するとき、ユーザーはセグメントに含まれるために "OR "フィルターの1つを満たすだけでよいことを覚えておいてほしい。他のフィルターに関係なくネガティブフィルターを適用するには、[除外グループを](#exclusion)使う。
+否定フィルター (サブスクリプショングループの「is not」など) を含む複数のフィルターに「OR」を選択した場合、ユーザーをセグメントに含めるには「OR」が適用されるフィルターのいずれかを満たすだけで良いということを覚えておいてください。他のフィルターに関係なく否定フィルターを適用するには、[除外グループ](#exclusion)を使います。
 {% endalert %}
 
 #### フィルター演算子
 
-選択したフィルターによって、フィルター値を特定するための演算子は異なる。さまざまなタイプのカスタム属性で利用可能な演算子について詳しく知りたい場合は、[カスタム属性ストレージを]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#setting-custom-attributes)参照のこと。is any of」演算子を使う場合、そのフィールドに含めることができる項目の最大数は256であることに注意。
+選択したフィルターによって、フィルター値を特定するための演算子は異なります。さまざまなタイプのカスタム属性で利用可能な演算子について詳しく知りたい場合は、[カスタム属性ストレージを]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#setting-custom-attributes)参照のこと。is any of」演算子を使う場合、そのフィールドに含めることができる項目の最大数は256であることに注意。
 
 {% alert note %}
 Braze は、アプリを初めて使用するまでユーザーのプロファイルを生成しないため、アプリをまだ開いていないユーザーをターゲットにすることはできません。
 {% endalert %}
 
-![セグメンターはAND演算子でグループをフィルターする。][9]{: style="max-width:70%;"}
+![AND 演算子のあるセグメント化フィルターグループ][9]{: style="max-width:70%;"}
 
 {% alert important %}
-すでに**セグメント・メンバーシップ・フィルターを**使用しているセグメントを、さらに他のセグメントに含めたり、入れ子にしたりすることはできない。
+すでに**セグメントメンバーシップ**フィルターを使用しているセグメントは、さらに他のセグメントに含めたり、ネストしたりすることはできません。
 {% endalert %}
 
 #### 除外グループ（オプション） {#exclusion}
@@ -108,23 +108,23 @@ Braze は、アプリを初めて使用するまでユーザーのプロファ
 
 ユーザーがセグメント、フィルター、アプリの条件にマッチすると、アラートにその旨が表示される。
 
-![user007 "のユーザー検索は、"user007はすべてのセグメント、フィルタ、およびアプリに一致する "というアラートをトリガーする。][7]{: style=" max-width:80%;"}
+![「user007」のユーザー検索により、「user007 はすべてのセグメント、フィルター、およびアプリケーションに一致しました」というアラートがトリガーされます。][7]{: style=" max-width:80%;"}
 
 ユーザーがセグメント、フィルター、またはアプリの条件の一部またはすべてに一致しない場合、トラブルシューティングのために欠落している条件がリストされます。
 
-![user1234 "のユーザールックアップは、"user1234 does not match following targeting criteria:（user1234は以下のターゲット条件にマッチしません）"というアラートをトリガーし、2つの欠けている条件を表示する。][8]{: style=" max-width:80%;"}
+![「user1234」のユーザー検索により、「user1234 は次のターゲット基準に一致しません」というアラートが表示され、一致しない 2 つの条件が表示されます。1 つは在職期間が 1 年を超えていること、もう 1 つは今日が記念日であることです。][8]{: style=" max-width:80%;"}
 
 #### シングルユーザーセグメント
 
 ユーザー名やユーザーID などのユーザーを識別する一意の属性を使用して、単一のユーザーセグメント (または少数のユーザーのセグメント) を作成できます。
 
-ただし、セグメント統計は、結果が +/-1% 以内という 95% の信頼区間のランダムサンプルに基づいて計算されるため、セグメンテーション統計またはプレビューにはこの個々のユーザーが表示されない場合があります。ユーザーベースが大きいほど、セグメントのサイズは概算である可能性が高くなります。セグメントにターゲットとするユーザーが含まれていることを確認するには、「**正確な統計情報を計算する**」を選択する。これにより、セグメント内の正確なユーザー数が 99.999% を超える精度で計算されます。
+ただし、セグメント統計は、結果が +/-1% 以内という 95% の信頼区間のランダムサンプルに基づいて計算されるため、セグメンテーション統計またはプレビューにはこの個々のユーザーが表示されない場合があります。ユーザーベースが大きいほど、セグメントのサイズは概算である可能性が高くなります。セグメントにターゲットとする単一のユーザーが含まれていることを確認するには、\[**正確な統計を計算する**] を選択します。これにより、セグメント内の正確なユーザー数が 99.999% を超える精度で計算されます。
 
 Braze には、ユーザー ID またはメールアドレスで特定のユーザーをターゲットにするテストフィルターがあります。
 
 ### ステップ 5: セグメントを保存する
 
-**保存を**選択する。これで、ユーザーへのメッセージ送信を開始する準備が整った！
+\[**保存**] を選択します。これで、ユーザーへのメッセージ送信を開始する準備が整った！
 
 ## セグメントメンバーシップの計算 {#segment-membership-calculation}
 
@@ -134,29 +134,29 @@ Braze は、データが当社のサーバーに送り返されて処理され
 
 各セグメントには、そのセグメントのメンバーであるユーザーの総数が表示されます。**すべてのアプリのユーザー**をフィルターすると、ウェブプッシュやメールなど、それらのユーザーと通信できるさまざまなチャネルもすべて表示されます。ユーザーの合計数は、各チャネルでリーチ可能なユーザー数と異なる場合があります。
 
-![電子メール、iOSプッシュ、Androidプッシュ、ウェブプッシュ、Kindleプッシュ、Androidチャイナプッシュで到達可能なユーザー別に、到達可能な総ユーザーを表示した表。][10]
+![リーチ可能なユーザーの合計を、メール、iOS プッシュ、Android プッシュ、Web プッシュ、Kindle プッシュ、Android China プッシュでリーチ可能なユーザー別に表示するテーブル][10]
 
 ユーザーが特定のチャネルを通じてリーチ可能と表示されるには、次の両方が必要です: 
 * プロフィールに関連付けられた有効な電子メールアドレスまたはプッシュトークン。
-* あなたのアプリに登録した。
+* アプリをオプトインまたはサブスクライブしていること。
 
 1 人のユーザーが異なるリーチ可能なユーザーグループに属している場合があります。例えば、ユーザーが有効なメールアドレスと有効な Android プッシュトークンの両方を持っていて、両方にオプトインしている一方、iOS プッシュトークンは関連付けられていない場合があります。リーチ可能なユーザーの総数と、異なるチャネルの合計との差は、セグメントの対象でありながら、それらの通信チャネルではリーチできないユーザーの数です。
 
 ### セグメント・サイズの統計
 
-Brazeはセグメントサイズについて次のような統計を行っている。すべての推定統計値は、実際の値の上下1％以内であり、正確なセグメントメンバーシップは、キャンペーンまたはキャンバスで送信されたメッセージによってセグメントが影響を受ける前に、常に計算される。
+Brazeはセグメントサイズについて次のような統計を行っている。すべての推定統計値は、実際の値の上下 1% 以内であり、正確なセグメントメンバーシップは、常にキャンペーンまたはキャンバスで送信されたメッセージによってセグメントが影響を受ける前に計算されます。
 
 #### フィルター統計
 
-フィルターグループごとに、推定到達可能ユーザーを見ることができる。チャンネル間の内訳を見るには、**Expand extra funnel statisticsを**選択する。
+フィルターグループごとに、到達可能なユーザー数の推定を表示できます。チャネル間の内訳を見るには、\[**追加の目標到達プロセスの統計を展開する**] を選択します。
 
-![性別が不明でないフィルターグループ。][4]{: style="max-width:80%;"}
+![性別が不明ではないフィルターを持つフィルターグループ。][4]{: style="max-width:80%;"}
 
 #### セグメント統計
 
 セグメント全体について、到達可能な推定ユーザー数、および各チャネルの推定ユーザー数をページ下部で見ることができる。また、「**正確な統計情報を計算する**」を選択することで、到達可能なユーザーの正確な数（セグメント全体とチャネルごとの両方）を表示することもできる。
 
-注意してほしい：
+注意事項:
 - 正確な統計の計算には数分かかる。この関数は、フィルターやフィルターグループレベルではなく、セグメントレベルでの正確な統計を計算するだけである。
 - 大きなセグメントでは、正確な統計を計算しても、通常はわずかな変動が見られます。この機能の精度は、99.999% 以上であることが期待されます。
 
@@ -174,9 +174,9 @@ Brazeはセグメントサイズについて次のような統計を行ってい
 
 ## ユーザーが複数のデバイスを持っている場合のターゲティング行動
 
-複数のデバイスで同じアカウントにログインしている場合、ユーザーは複数のデバイスを持っている。[ユーザー・プロフィールの]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/)「**最近使ったデバイス**」セクションで、複数のデバイスをチェックできる。
+複数のデバイスで同じアカウントにログインしている場合、ユーザーは複数のデバイスを持っています。\[[ユーザープロファイル]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/)] の \[**最近のデバイス**] セクションで複数のデバイスをチェックできます。
 
-デバイス依存のフィルター（デバイスモデル、デバイスOS、アプリのバージョン）を使ってセグメント化する場合、セグメントにはフィルター基準に一致するすべてのユーザーが含まれる。これらのユーザーには、フィルター基準を満たさないものも含め、すべてのデバイスにメッセージが送信される。例えば、ユーザーAが2台のデバイスを持っているとしよう：デバイス1はOS 13.0、デバイス2はOS 10.0だ。あるセグメントがOS 10.0のユーザーをターゲットにしている場合、このユーザーはそのセグメントの一部となり、両方のデバイスでメッセージを受け取ることになる。
+デバイス依存のフィルター（デバイスモデル、デバイスOS、アプリのバージョン）を使ってセグメント化する場合、セグメントにはフィルター基準に一致するすべてのユーザーが含まれる。これらのユーザーには、フィルター基準を満たさないものも含め、すべてのデバイスにメッセージが送信される。例えば、ユーザーAが2台のデバイスを持っているとしよう：デバイス 1 は OS 13.0、デバイス 2 は OS 10.0です。あるセグメントがOS 10.0のユーザーをターゲットにしている場合、このユーザーはそのセグメントの一部となり、両方のデバイスでメッセージを受け取ることになる。
 
 ### プッシュ通知
 
@@ -186,10 +186,10 @@ Brazeはセグメントサイズについて次のような統計を行ってい
 
 ### 考慮事項
 
-- **送信されたメッセージは視聴者数を超えることがある。**複数のデバイスを持つユーザーがいる場合、それぞれのデバイスがメッセージを受信することができる。そのため、セグメント内のユーザーよりもメッセージ送信数が多くなる。
-- **ユーザーのセグメントメンバーシップは、あなたが期待するようなものではないかもしれない。**
-    - ユーザーは、別のデバイスに関連する属性に基づいて、現在のデバイスをターゲットにすることができる。ユーザーがメッセージを受信することを予期していなかった場合、そのユーザーのユーザー・プロフィールに複数のデバイスがないか確認する。
-    - あるユーザーは、送信時にはターゲット・セグメントに入っていたかもしれないが、その後、そのユーザーのデバイスに関連する行動によって、ターゲット・セグメントに含まれなくなる可能性がある。その結果、現在フィルター条件にマッチしていないにもかかわらず、ユーザーがキャンペーンやキャンバスを受け取ってしまう可能性がある。<br><br>例えば、現在OS 13.0を使っているにもかかわらず、最新アプリのバージョンがOS 10.0のユーザーをターゲットにしたメッセージを受け取る可能性がある。このケースでは、メッセージ送信時にOS10.0を使用しており、その後OS13.0にアップグレードした。<br><br> 同様に、ユーザーが後に異なるアプリバージョンのデバイスを使用した場合、ユーザープロファイルは新しい最新アプリバージョンで更新される。これでは、メッセージが送信されたときには適格であったにもかかわらず、ユーザーはそのメッセージを受け取る資格がなかったと思われるかもしれない。
+- **送信メッセージ数は、オーディエンスサイズを超える場合があります。**複数のデバイスを持つユーザーがいる場合、それぞれのデバイスがメッセージを受信することができる。そのため、セグメント内のユーザーよりもメッセージの送信数が多くなります。
+- **ユーザーのセグメントメンバーシップは、予想どおりに表示されない場合があります。**
+    - ユーザーは、別のデバイスに関連する属性に基づいて、現在のデバイスをターゲットにすることができます。ユーザーがメッセージを受信することを予期していなかった場合、そのユーザーのユーザー・プロフィールに複数のデバイスがないか確認する。
+    - あるユーザーは、送信時にはターゲット・セグメントに入っていたかもしれないが、その後、そのユーザーのデバイスに関連する行動によって、ターゲット・セグメントに含まれなくなる可能性がある。その結果、現在フィルター条件にマッチしていないにもかかわらず、ユーザーがキャンペーンやキャンバスを受け取ってしまう可能性がある。<br><br>たとえば、現在 OS 13.0 を使っているユーザーが、最新アプリのバージョンが OS 10.0 のユーザー向けのメッセージを受け取る可能性があります。この場合、ユーザーはメッセージの送信時に OS 10.0 を使用しており、その後 OS 13.0 にアップグレードしたためです。<br><br> 同様に、ユーザーが後に異なるアプリバージョンのデバイスを使用した場合、そのユーザーのプロファイルは新しい最新アプリバージョンで更新されます。すると、メッセージの送信時には適格であったにも関わらず、そのメッセージを受け取る適格性がなかったように見えるかもしれません。
 
 
 [1]: {% image_buster /assets/img_archive/Segment1.png %}
diff --git a/_lang/ja/_user_guide/engagement_tools/segments/segment_extension.md b/_lang/ja/_user_guide/engagement_tools/segments/segment_extension.md
index af1672d3ba8..c2f82d66ba8 100644
--- a/_lang/ja/_user_guide/engagement_tools/segments/segment_extension.md
+++ b/_lang/ja/_user_guide/engagement_tools/segments/segment_extension.md
@@ -14,13 +14,13 @@ tool: Segments
 
 セグメントエクステンションは、階層化イベントプロパティを使用したり、過去2年間 (730日間) のカスタムイベントプロパティや購入イベントプロパティをウィンドウ形式で集計したりできるオーディエンス定義です。たとえば、Braze セグメンテーションを使用すると、これまでの期間に特定の製品を購入したユーザーを見つけることができます。セグメントエクステンションを使用すると、過去2年間に特定の製品の特定の色を2回以上購入したユーザーにオーディエンスをさらに絞り込むことができます。セグメントエクステンションを作成するときに、オーディエンスを固定するか、毎日再生成するかを指定することもできます。
 
-ネストされたイベントプロパティの使用は、アクションベースの配信][19]にはセグメントエクステンションを必要としません。イベント処理はリアルタイムで行われます。階層化カスタム属性も同様に、セグメントエクステンションを使用する必要はありません。
+\[アクションベースの配信][19] に階層化イベントプロパティを使用する場合、イベント処理はリアルタイムで行われるため、セグメントエクステンションは必要ありません。階層化カスタム属性も同様に、セグメントエクステンションを使用する必要はありません。
 
 {% alert important %}
 デフォルトでは、特定の時間に1つのワークスペースにつき25個のアクティブなセグメントエクステンションが割り当てられます。この制限を増やす必要がある場合は、Brazeカスタマーサクセスマネージャーに連絡して、ユースケースについて話し合ってください。
 {% endalert %}
 
-## ステップ 1 セグメントエクステンションに移動する
+## ステップ 1: セグメントエクステンションに移動する
 
 \[**オーディエンス**] > \[**セグメントエクステンション**] に移動します。
 
@@ -46,9 +46,9 @@ SQL を使用するエクスペリエンスを選択した場合の詳細は、[
 
 フィルタリングするユーザーのタイプを記述して、セグメントエクステンションに名前を付けます。これにより、このエクステンションをフィルターとしてセグメントに適用するときに、このエクステンションを簡単かつ正確に検出できます。
 
-![Segment 拡張機能「オンラインショッパー拡張 - 90日」が「拡張機能を毎日再生成する」チェックボックスが選択された状態で。][2]
+![「オンラインショッパーエクステンション - 90日」という名前のセグメントエクステンション。「エクステンションを毎日再生成」チェックボックスが選択されています。][2]
 
-## ステップ 3:条件を選択する
+## ステップ 3: 条件を選択する
 
 ターゲティングの条件として、購入、メッセージエンゲージメント、カスタムイベントのいずれかを選択します。希望のイベントタイプ条件を選択したら、ユーザーリストでターゲットにする購入アイテム、メッセージインタラクション、または特定のカスタムイベントを選択します。次に、ユーザーがイベントを完了する必要がある回数 (より大きい、より小さい、または等しい) と期間を選択します。特にセグメントエクステンションの場合は、過去730日間 (2年間) までさかのぼることができます。
 
@@ -116,7 +116,7 @@ Braze セグメントエクステンションフィルターリストから、
 
 ![][8]{: style="max-width:70%;"}
 
-これで、通常どおりにセグメント][11]を作成できます。
+これで、通常どおりに \[セグメントを作成][11] できます。
 
 [2]: {% image_buster /assets/img/segment/segment_extension2.png %}
 [3]: {% image_buster /assets/img/segment/segment_extension1.png %}
diff --git a/_lang/ja/_user_guide/engagement_tools/segments/segmentation_filters.md b/_lang/ja/_user_guide/engagement_tools/segments/segmentation_filters.md
index 0ae21f0b868..9c2790b0b71 100644
--- a/_lang/ja/_user_guide/engagement_tools/segments/segmentation_filters.md
+++ b/_lang/ja/_user_guide/engagement_tools/segments/segmentation_filters.md
@@ -18,7 +18,7 @@ glossary_tags:
   - name: セグメントまたはCSVメンバーシップ
   - name: カスタム属性
   - name: カスタムイベント
-  - name: セッション数
+  - name: セッション
   - name: リターゲット
   - name: チャンネルサブスクリプションの動作
   - name: 購買行動
@@ -29,113 +29,113 @@ glossary_tags:
   - name: ロケーション
   - name: コホート会員
   - name: アトリビューションのインストール
-  - name: 情報と予知
+  - name: インテリジェンスと予測
   - name: 社会活動
   - name: その他のフィルタ
 
 glossaries:
-  - name: セグメント会員数
-    description: フィルター s が使用されているSegmentメンバーシップ(Segment s、キャンペーン s など) に基づいてフィルターし、1 つのキャンペーン内で複数の異なるs を対象とすることができます。<br><br>Segmentsがすでにこのフィルターを使用している場合、他のSegmentsに追加またはネストできないことに注意してください。同じフィルターs を使用して、含めるSegmentを再作成する必要があります。
+  - name: セグメントのメンバーシップ
+    description: フィルターが使用されている任意のセグメントメンバーシップ (セグメントやキャンペーンなど) に基づいてフィルターし、1 つのキャンペーン内で複数の異なるセグメントをターゲットにすることができます。<br><br>すでにこのフィルターを使用しているセグメントは、他のセグメントに追加しり、ネストしたりできないことに注意してください。同じフィルターを使用して、含めるセグメントを再作成する必要があります。
     tags:
       - Segment or CSV membership
-  - name: Braze分野
-    description: Segment拡張をBraze ダッシュボードに作成した後、それらの拡張をSegmentに含める/除外することができます。
+  - name: Braze のセグメントエクステンション
+    description: セグメントエクステンションを Braze ダッシュボードで作成した後、それらのエクステンションをセグメントに含めたり除外したりできます。
     tags:
       - Segment or CSV membership
   - name: CSV から更新/インポート
-    description: CSV アップロードの一部であるかどうかに基づいて、ユーザーをセグメント化します。
+    description: CSV アップロードの一部であるかどうかに基づいてユーザーをセグメント化します。
     tags:
       - Segment or CSV membership
   - name: カスタム属性
-    description: "ユーザーが個別に記録された属性と一致するかどうかを決定します。(24時間) <br><br>タイムゾーン:<br>会社のタイムゾーン"
+    description: "ユーザーが、記録されたカスタム属性値と一致するかどうかを決定します。(24時間) <br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Custom attributes
   - name: 階層化カスタム属性
-    description: "カスタム属性s のプロパティーである属性s。<br><br>階層化された時間のカスタム属性にフィルターを適用する場合、基準として [年間通算日] または [時刻] を選択できます。[年間通算日] では、比較対象として月と日のみがチェックされます。[時刻] では、年を含むタイムスタンプ全体が比較されます。"
+    description: "カスタム属性のプロパティである属性。<br><br>階層化された時間のカスタム属性にフィルターを適用する場合、基準として [年間通算日] または [時刻] を選択できます。[年間通算日] では、比較対象として月と日のみがチェックされます。[時刻] では、年を含むタイムスタンプ全体が比較されます。"
     tags:
       - Custom attributes
   - name: 定期的なイベントの日
-    description: "このフィルターでは、データタイプが\"date\"のカスタム属性の月と日を調べますが、年は調べません。このフィルターは年中行事に役立つ。<br><br>タイムゾーン:<br>このフィルターは、ユーザーがどのタイムゾーンにあるかを調整します。"
+    description: "このフィルターでは、データタイプが\"date\"のカスタム属性の月と日を調べますが、年は調べません。このフィルターは毎年発生するイベントに役立ちます。<br><br>タイムゾーン:<br>このフィルターは、ユーザーがどのタイムゾーンにあるかを調整します。"
     tags:
       - Custom attributes
   - name: カスタムイベント
-    description: "ユーザーが特別に録音された行動を実行したかどうかを決定します。<br><br> 例: <br>プロパティ activty_name で完了したアクティビティー。<br><br>タイムゾーン:<br>UTC - カレンダ日= 1 暦日は、ユーザー履歴の24 ～48 時間を表示します"
+    description: "ユーザーが特別に記録された行動を実行したかどうかを決定します。<br><br> 例: <br>プロパティ activty_name で完了したアクティビティー。<br><br>タイムゾーン:<br>UTC - 暦日 = 1 暦日は、ユーザー履歴の 24 ～ 48 時間を含みます"
     tags:
       - Custom events
   - name: 最初にカスタムイベントを実行した
-    description: "ユーザーが特別に録音された行動を実行した最も早い時刻を決定します。(24時間) <br><br>例: <br> 1日前に放棄されたカート<br><br>タイムゾーン:<br>会社のタイムゾーン"
+    description: "ユーザーが特別に記録された行動を実行した最も早い時刻を決定します。(24時間) <br><br>例: <br> 初回のカート放棄が過去 1 日未満<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Custom events
-  - name: 前回のカスタムイベント 
-    description: "ユーザーが特別に録音された行動を最後に実行した時刻を決定します。(24時間) <br><br>例: <br> 前回放棄されたカート1日未満<br><br>タイムゾーン:<br>会社のタイムゾーン"
+  - name: 最後に実行したカスタムイベント 
+    description: "ユーザーが特別に記録された行動を最後に実行した時刻を決定します。(24時間) <br><br>例: <br> 最後のカート放棄が過去 1 日未満<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Custom events
   - name: X Y日間のカスタムイベント
-    description: "ユーザーが、最後に指定されたカレンダ日数の0～50 回の間に、特別に記録されたイベントを1～30 日の間で実行したかどうかを決定します。(暦日= 1 暦日はユーザー履歴の24 ～48 時間を表示します)<br> <a href=\"/docs/x-in-y-behavior/\"> ここでは、X-in-Y の動作について詳しく説明します。</a><br><br>例: <br>最後の1 暦日にカートをちょうど0 回放棄した<br><br>タイムゾーン:<br>UTC - すべてのタイムゾーンを考慮すると、1 暦日はユーザー履歴の24 ～48 時間を、Segmentが評価される時刻に応じて、2 暦日はユーザー履歴の48 ～72 時間を、などと表示します。"
+    description: "ユーザーが、最後に指定された暦日数 (1 ～ 30 日) の間に、特別に記録されたイベントを 0 ～ 50 回実行したかどうかを決定します。(暦日 = 1 暦日は、ユーザー履歴の 24 ～ 48 時間を含みます)<br> <a href=\"/docs/x-in-y-behavior/\"> ここでは、X-in-Y の動作について詳しく説明します。</a><br><br>例: <br>過去 1 暦日内にカートをちょうど 0 回放棄した<br><br>タイムゾーン:<br>UTC - すべてのタイムゾーンを考慮すると、1 暦日はユーザー履歴の24 ～48 時間を、Segmentが評価される時刻に応じて、2 暦日はユーザー履歴の48 ～72 時間を、などと表示します。"
     tags:
       - Custom events
   - name: X Y 日間のカスタムイベントプロパティ
-    description: "ユーザーが、1 から30 までの最後に指定されたカレンダ日数の0 から50 回の間の指定されたプロパティに関して、特別に記録されたイベントを実行したかどうかを決定します。(暦日= 1 暦日はユーザー履歴の24 ～48 時間を表示します)<br><a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a><br><br>例: <br> お気に入りに追加されましたw/プロパティ\"event_name\"最後の1 暦日で正確に0 回<br><br>タイムゾーン:<br>UTC - すべてのタイムゾーンを考慮すると、1 暦日はユーザー履歴の24 ～48 時間を、Segmentが評価される時刻に応じて、2 暦日はユーザー履歴の48 ～72 時間を、などと表示します。"
+    description: "ユーザーが、最後に指定された暦日数 (1 ～ 30 日) の間に、特別に記録されたイベントを特定のプロパティについて 0 ～ 50 回実行したかどうかを決定します。(暦日 = 1 暦日は、ユーザー履歴の 24 ～ 48 時間を含みます)<br><a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a><br><br>例: <br> 過去 1 暦日内にカートをちょうど 0 回お気に入りに追加した<br><br>タイムゾーン:<br>UTC - すべてのタイムゾーンを考慮すると、1 暦日はユーザー履歴の24 ～48 時間を、Segmentが評価される時刻に応じて、2 暦日はユーザー履歴の48 ～72 時間を、などと表示します。"
     tags:
       - Custom events
   - name: 電子メールアドレス 
-    description: "テスト用の個々のメールアドレスによってキャンペーン 受信者s を指定できます。これは、&amp;quot を使用して、トランスアクション al メール s をすべてのユーザーs (配信停止d を含む) に送信するためにも使用できます。メール Address is not Blank\" specifier in the フィルター."
+    description: テスト用に個々のメールアドレスによってキャンペーン 受信者を指定できます。これは、「メールアドレスが空白でない」指定子を使用して、トランザクションメールをすべてのユーザー (配信停止済みユーザーを含む) に送信するためにも使用できます。
     tags:
       - Other Filters
   - name: 外部ユーザーID
-    description: テストのために、キャンペーン 受信者sを個々のユーザー IDsで指定することができます。
+    description: テストのために、キャンペーン受信者を個々のユーザー ID で指定することができます。
     tags:
       - Other Filters
   - name: "ランダムバケット番号"
-    description: ユーザーをランダムに割り当てられた番号(0～9999を含む)でセグメント化します。それは、A/Bと多変量テストに対する真の乱数ユーザーsの均一に分布したSegmentsの生成を可能にする。
+    description: ユーザーをランダムに割り当てられた番号(0～9999を含む)でセグメント化します。これにより、AB テストと多変量テストに対する真のランダムユーザーの一様分布セグメントを生成できるようになります。
     tags:
       - Other Filters
   - name: セッション数
-    description: ユーザーs を、ワークスペース内のアプリs のどれかに含まれていたセッションの個数で分割します。
+    description: ユーザーをワークスペース内のいずれかのアプリでこれまでに行ったセッション数でセグメント化します。
     tags:
       - Sessions
   - name: アプリのセッション数
-    description: ユーザーを、指定されたアプリ内に保持されているセッションの個数でセグメント化します。
+    description: 指定されたアプリ内でこれまでに行ったセッション数によってユーザーをセグメント化します。
     tags:
       - Sessions
-  - name: X 過去Y日間のセッション
-    description: "ユーザーs を、1 から30 までの最後に指定されたカレンダ日数のアプリに保持されていたセッションs (0 から50) でセグメント化します。<br> <a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a>"
+  - name: 過去 Y 日間の X 回のセッション
+    description: "最後に指定された暦日数 (1 ～ 30 日) の間に、貴社のアプリで行ったセッション数 (0 ～ 50 回) によってユーザーをセグメント化します。<br> <a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a>"
     tags:
       - Sessions
   - name: 最初に使用したアプリ
-    description: "ユーザーを、アプリに開封した記録されている最も早い時刻に分割します。<em>これは、Braze SDKを組み込んだアプリを使用している最初のセッションをキャプチャすることに注意してください。</em>(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
+    description: "アプリを開封した記録の最も早い時刻によってユーザーをセグメント化します。<em>これは、ユーザーが Braze SDK を統合したアプリを使用した最初のセッションをキャプチャすることに注意してください。</em>(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Sessions
   - name: 最初に使用した特定のアプリ
-    description: "ワークスペース内の任意のアプリに開封した、記録されている最も早い時刻でユーザーをセグメント化します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
+    description: "ワークスペース内の任意のアプリを開封した記録の最も早い時刻によってユーザーをセグメント化します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Sessions
   - name: 最後に使用したアプリ
-    description: "ユーザーがアプリに開封された最新の時刻までにセグメント化します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
+    description: "アプリを開封した最後の時刻によってユーザーをセグメント化します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Sessions
-  - name: 最後に使用した特定のアプリ
-    description: "ユーザーを、指定したアプリに開封した最新の時刻に分割します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
+  - name: 特定のアプリの最終使用
+    description: "指定されたアプリを開封した最後の時刻によってユーザーをセグメント化します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Sessions
-  - name: セッション期間中央値
-    description: アプリ内のセッションの中央値の長さでユーザーを分割します。
+  - name: セッション時間の中央値
+    description: アプリ内のセッションの長さの中央値によってユーザーをセグメント化します。
     tags:
       - Sessions
   - name: キャンペーンから受信したメッセージ
-    description: "指定したキャンペーンを受信したかどうかによってユーザーをセグメント化します。<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが送信されたときではなく、ユーザーがインプレッションを記録するときです。<br><br>プッシュおよびwebhookの場合、これはメッセージがユーザーに送信されるときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されるときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されるときです。<br><br>メール sの場合、メールリクエストが(実際に配信されたかどうかに関係なく)そのプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新 d です。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。"
+    description: "指定したキャンペーンを受信したかどうかによってユーザーをセグメント化します。<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが送信されたときではなく、ユーザーがインプレッションを記録するときです。<br><br>プッシュおよびwebhookの場合、これはメッセージがユーザーに送信されるときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されるときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されるときです。<br><br>メールの場合、メールリクエストが (実際に配信されたかどうかに関係なく) メールサービスプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新されます。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。"
     tags:
       - Retargeting
-  - name: キャンペーンバリアントを受賞
-    description: "受信した多変量 キャンペーンのバリアントのユーザーを分割します。<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが送信されたときではなく、ユーザーがインプレッションを記録するときです。<br><br>プッシュおよびwebhookの場合、これはメッセージがユーザーに送信されるときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されるときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されるときです。<br><br>メール sの場合、メールリクエストが(実際に配信されたかどうかに関係なく)そのプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新 d です。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。"
+  - name: キャンペーンバリアントを受信
+    description: "受信した多変量キャンペーンのバリアントによってユーザーをセグメント化します。<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが送信されたときではなく、ユーザーがインプレッションを記録するときです。<br><br>プッシュおよびwebhookの場合、これはメッセージがユーザーに送信されるときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されるときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されるときです。<br><br>メールの場合、メールリクエストが (実際に配信されたかどうかに関係なく) メールサービスプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新されます。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。"
     tags:
       - Retargeting
-  - name: キャンバスステップから受信したメッセージ
-    description: "特定のキャンバスコンポーネントを受信したかどうかによって、ユーザーをセグメント化します。<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが送信されたときではなく、ユーザーがインプレッションを記録するときです。<br><br>プッシュおよびwebhookの場合、これはメッセージがユーザーに送信されるときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されるときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されるときです。<br><br>メール sの場合、メールリクエストが(実際に配信されたかどうかに関係なく)そのプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新 d です。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。"
+  - name: キャンバスステップからメッセージを受信
+    description: "特定のキャンバスコンポーネントを受信したかどうかによってユーザーをセグメント化します。<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが送信されたときではなく、ユーザーがインプレッションを記録するときです。<br><br>プッシュおよびwebhookの場合、これはメッセージがユーザーに送信されるときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されるときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されるときです。<br><br>メールの場合、メールリクエストが (実際に配信されたかどうかに関係なく) メールサービスプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新されます。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。"
     tags:
       - Retargeting
   - name: 特定のキャンバスステップから最後に受信したメッセージ
-    description: 特定のキャンバスコンポーネントを受信したときに、ユーザーをセグメント化します。
+    description: 特定のキャンバスコンポーネントを受信した日時によってユーザーをセグメント化します。
     tags:
       - Retargeting
   - name: 特定のキャンペーンから最後に受信したメッセージ
@@ -143,11 +143,11 @@ glossaries:
     tags:
       - Retargeting
   - name: キャンペーンまたはキャンバスからタグ付きで受信したメッセージ
-    description: "指定したキャンペーンを受信したかどうか、または指定したタグのキャンバスを受信したかどうかによって、ユーザーを分割します。<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが送信されたときではなく、ユーザーがインプレッションを記録するときです。<br><br>プッシュおよびwebhookの場合、これはメッセージがユーザーに送信されるときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されるときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されるときです。<br><br>メール sの場合、メールリクエストが(実際に配信されたかどうかに関係なく)そのプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新 d です。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。"
+    description: "指定したキャンペーンを受信したかどうか、または指定したタグのキャンバスを受信したかどうかによって、ユーザーを分割します。<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが送信されたときではなく、ユーザーがインプレッションを記録するときです。<br><br>プッシュおよびwebhookの場合、これはメッセージがユーザーに送信されるときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されるときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されるときです。<br><br>メールの場合、メールリクエストが (実際に配信されたかどうかに関係なく) メールサービスプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新されます。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。"
     tags:
       - Retargeting
   - name: キャンペーンまたはCanvas With Tagから最後に受信したメッセージ
-    description: 指定したタグのキャンペーンまたはキャンバスを受信したときに、ユーザーをセグメント化します。(24時間)
+    description: 特定のタグを持つ特定のキャンペーンまたはキャンバスを受信した日時によってユーザーをセグメント化します。(24時間)
     tags:
       - Retargeting
   - name: キャンペーンステップまたはキャンバスステップからメッセージを受信していない
@@ -162,7 +162,7 @@ glossaries:
     description: "ユーザーを最後にプッシュ通知s のいずれかを受信したときにセグメント化します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Retargeting
-  - name: アプリメッセージの最後の印象
+  - name: 最後のアプリ内メッセージインプレッション
     description: ユーザーを最後にアプリ内メッセージを表示したときにセグメント化します。
     tags:
       - Retargeting
@@ -170,11 +170,11 @@ glossaries:
     description: "最後のメッセージがSMSプロバイダーに配信された時刻までにユーザーをセグメント化します。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Retargeting
-  - name: 最後に受信したWeb
+  - name: 最後に受信した Webhook
     description: "ユーザーを、BrazeがそのユーザーのWebhookを最後に送信した時刻までに分割します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Retargeting
-  - name: 最終受信WhatsApp
+  - name: 最後に受信した WhatsApp
     description: "最後にWhatsAppを受信したときに、ユーザーをセグメント化します。これは、メッセージがユーザーの機器に配信されるときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されるときです。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Retargeting
@@ -183,35 +183,35 @@ glossaries:
     tags:
       - Retargeting
   - name: ニュースフィードの閲覧数
-    description: ユーザーがニュースフィードを何回表示したかをセグメント化します。
+    description: ニュースフィードを表示した何回によってユーザーをセグメント化します。
     tags:
       - Retargeting
   - name: クリックされた/開封されたキャンペーン
-    description: "指定したキャンペーンでインターアクションでフィルタリングします。<br><br> メールとして、複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーもプロファイルs 更新 d を持ちます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封またはクリックの前にある場合、元のユーザーではなくそのメールアドレスを持つすべての残りのユーザーに開封またはクリックがアプリされます。<br><br>SMSの場合、インターアクションは次のように定義されます。<br>- ユーザーは、指定されたキーワードカテゴリに一致するリプライSMSを最後に送信しました。これは、この電話番号を持つすべてのユーザーs が受信した最新のキャンペーンに属性されます。キャンペーンは、過去4時間以内に受信されている必要があります。<br>- ユーザーの\"トラッキングが有効になっているSMSメッセージ内の短縮されたリンクを、特定のキャンペーンから最後に選択したユーザー。"
+    description: "特定のキャンペーンとのインタラクションでフィルタリングします。<br><br> メールとして、複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーのプロファイルも更新されます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封/クリックをまだ行っていない場合、元のユーザーではなく、そのメールアドレスを持つすべての残りのユーザーに開封またはクリックが適用されます。<br><br>SMSの場合、インターアクションは次のように定義されます。<br>- ユーザーは、指定されたキーワードカテゴリに一致するリプライSMSを最後に送信しました。これは、この電話番号を持つすべてのユーザーs が受信した最新のキャンペーンに属性されます。キャンペーンは、過去4時間以内に受信されている必要があります。<br>- ユーザーは、指定のキャンペーンから、ユーザーのクリック追跡が有効になっている SMS メッセージ内の短縮リンクを最後に選択しました。"
     tags:
       - Retargeting
   - name: クリック/開いたキャンペーンまたはタグ付きキャンバス
-    description: "特定のタグを持つ特定のキャンペーンを持つアクション間でフィルタリングします。<br><br> 複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーもプロファイルs 更新 d を持ちます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封またはクリックの前にある場合、元のユーザーではなくそのメールアドレスを持つすべての残りのユーザーに開封またはクリックがアプリされます。<br><br>SMSの場合、インターアクションは次のように定義されます。<br>- ユーザーは、指定されたキーワードカテゴリに一致するリプライSMSを最後に送信しました。これは、この電話番号を持つすべてのユーザーs が受信した最新のキャンペーンに属性されます。キャンペーンは、過去4時間以内に受信されている必要があります。<br>- ユーザーが\"トラッキングを有効にしたSMSメッセージの短縮リンクを、特定のキャンペーンまたはキャンバスステップのタグで最後に選択したとき。"
+    description: "特定のタグを持つ特定のキャンペーンとのインタラクションでフィルタリングします。<br><br> 複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーのプロファイルも更新されます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封/クリックをまだ行っていない場合、元のユーザーではなく、そのメールアドレスを持つすべての残りのユーザーに開封またはクリックが適用されます。<br><br>SMSの場合、インターアクションは次のように定義されます。<br>- ユーザーは、指定されたキーワードカテゴリに一致するリプライSMSを最後に送信しました。これは、この電話番号を持つすべてのユーザーs が受信した最新のキャンペーンに属性されます。キャンペーンは、過去4時間以内に受信されている必要があります。<br>- ユーザーがタグを持つ指定のキャンペーンまたはキャンバスステップから、ユーザーのクリック追跡が有効になっている SMS メッセージ内の短縮リンクを最後に選択した日時。"
     tags:
       - Retargeting
-  - name: クリック/オープンステップ
-    description: "特定のキャンバスコンポーネントを使用して、インターアクションでフィルタリングする。<br><br>SMSの場合、インターアクションは次のように定義されます。<br>- ユーザーは、指定されたキーワードカテゴリに一致するリプライSMSを最後に送信しました。これは、この電話番号を持つすべてのユーザーs が受信した最新のキャンペーンに属性されます。キャンペーンは、過去4時間以内に受信されている必要があります。<br>- ユーザークリック\"トラッキングが有効になっているSMSメッセージ内の短縮リンクを、特定のキャンバスステップから最後に選択したユーザー。"
+  - name: クリックされた/開封されたステップ
+    description: 特定のキャンバスコンポーネントとのインタラクションでフィルタリングします。<br><br>SMSの場合、インターアクションは次のように定義されます。<br>- ユーザーは、指定されたキーワードカテゴリに一致するリプライSMSを最後に送信しました。これは、この電話番号を持つすべてのユーザーs が受信した最新のキャンペーンに属性されます。キャンペーンは、過去4時間以内に受信されている必要があります。<br>- ユーザーは、指定のキャンバスステップから、ユーザーのクリック追跡が有効になっている SMS メッセージ内の短縮リンクを最後に選択しました。
     tags:
       - Retargeting
   - name: キャンペーンでクリックしたエイリアス
-    description: "指定したキャンペーンの特定の別名をクリックしたかどうかによって、ユーザーをフィルタリングします。この唯一のアプリはメールにあります。<br><br> 複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーもプロファイルs 更新 d を持ちます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封またはクリックの前にある場合、元のユーザーではなくそのメールアドレスを持つすべての残りのユーザーに開封またはクリックがアプリされます。"
+    description: "指定したキャンペーンの特定の別名をクリックしたかどうかによって、ユーザーをフィルタリングします。これはメールメッセージだけに適用されます。<br><br> 複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーのプロファイルも更新されます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封/クリックをまだ行っていない場合、元のユーザーではなく、そのメールアドレスを持つすべての残りのユーザーに開封またはクリックが適用されます。"
     tags:
       - Retargeting
   - name: キャンバスステップでクリックしたエイリアス
-    description: "特定のキャンバスで特定のエイリアスをクリックしたかどうかによって、ユーザーをフィルタリングします。この唯一のアプリはメールにあります。<br><br> 複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーもプロファイルs 更新 d を持ちます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封またはクリックの前にある場合、元のユーザーではなくそのメールアドレスを持つすべての残りのユーザーに開封またはクリックがアプリされます。"
+    description: "特定のキャンバスで特定のエイリアスをクリックしたかどうかによって、ユーザーをフィルタリングします。これはメールメッセージだけに適用されます。<br><br> 複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーのプロファイルも更新されます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封/クリックをまだ行っていない場合、元のユーザーではなく、そのメールアドレスを持つすべての残りのユーザーに開封またはクリックが適用されます。"
     tags:
       - Retargeting
   - name: キャンペーンステップまたはキャンバスステップでクリックしたエイリアス
-    description: "ユーザーをフィルタリングするには、キャンペーンまたはキャンバスの別名をクリックします。この唯一のアプリはメールにあります。<br><br> 複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーもプロファイルs 更新 d を持ちます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封またはクリックの前にある場合、元のユーザーではなくそのメールアドレスを持つすべての残りのユーザーに開封またはクリックがアプリされます。"
+    description: "ユーザーを、任意のキャンペーンまたはキャンバス内で特定のエイリアスをクリックしたかどうかによってフィルタリングします。これはメールメッセージだけに適用されます。<br><br> 複数のユーザーが同じメールアドレスを共有している場合:<br>- メールを開封またはクリックすると、同じメールアドレスを持つ他のすべてのユーザーのプロファイルも更新されます。<br>- 元のユーザーがメッセージの送信後にメールアドレスを変更し、開封/クリックをまだ行っていない場合、元のユーザーではなく、そのメールアドレスを持つすべての残りのユーザーに開封またはクリックが適用されます。"
     tags:
       - Retargeting
   - name: ハードバウンス
-    description: メールアドレスがハードバウンスされたかどうか(メールアドレスが不正な場合など)によって、ユーザーs をセグメント化します。
+    description: ユーザーを、メールアドレスがハードバウンスされたかどうか (メールアドレスが不正な場合など) によってセグメント化します。
     tags:
       - Retargeting
   - name: スパムとしてマークされた
@@ -222,16 +222,16 @@ glossaries:
     description: 電話番号が不正かどうかによってユーザーをセグメント化します。
     tags:
       - Retargeting
-  - name: 最後に送信されたSMS受信キーワードカテゴリ
+  - name: 最後に送信された特定の SMS インバウンドキーワードカテゴリ
     description: 特定のキーワードカテゴリ内の特定のサブスクリプショングループにSMSを最後に送信したときに、ユーザーをセグメント化します。 
     tags:
       - Retargeting
   - name: キャンペーンからコンバージョン済み
-    description: 指定したキャンペーンに変換されたかどうかによって、ユーザーをセグメント化します。このフィルターには、コントロールグループに含まれるユーザーは含まれません。
+    description: 特定のキャンペーンでコンバージョンしたかどうかによってユーザーをセグメント化します。このフィルターには、コントロールグループに含まれるユーザーは含まれません。
     tags:
       - Retargeting
   - name: キャンバスからコンバージョン済み
-    description: 特定のキャンバスで変換されたかどうかによって、ユーザーをセグメント化します。このフィルターには、コントロールグループに含まれるユーザーは含まれません。
+    description: 特定のキャンバスでコンバージョンしたかどうかによってユーザーをセグメント化します。このフィルターには、コントロールグループに含まれるユーザーは含まれません。
     tags:
       - Retargeting
   - name: キャンペーンのコントロールグループ内
@@ -243,7 +243,7 @@ glossaries:
     tags:
       - Retargeting
   - name: 任意のコントロールグループに最後に登録された
-    description: "最後にキャンペーンでコントロールグループに落ちたときまでにユーザーを分割します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
+    description: "キャンペーンで最後にコントロールグループに割り当てられた時刻によってユーザーをセグメント化します。(24時間)<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Retargeting
   - name: 入力したキャンバスバリエーション
@@ -251,15 +251,15 @@ glossaries:
     tags:
       - Retargeting
   - name: メッセージの最終受信
-    description: "最後に受信したメッセージを判別して、ユーザーをセグメント化します。(24時間)<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが最後に送信されたときではなく、ユーザーが最後にインプレッションを記録したときです。<br><br>プッシュおよびwebhookの場合、これは、任意のメッセージがユーザーに送信されたときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されたときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されたときです。<br><br>メール sの場合、メールリクエストが(実際に配信されたかどうかに関係なく)そのプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新 d です。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。<br><br>例: <br>前回受信メール1日未満=24時間未満<br><br>タイムゾーン:<br>会社のタイムゾーン"
+    description: "最後に受信したメッセージを判別して、ユーザーをセグメント化します。(24時間)<br><br> コンテンツカードs およびアプリ内メッセージs の場合、カードまたはアプリ内メッセージが最後に送信されたときではなく、ユーザーが最後にインプレッションを記録したときです。<br><br>プッシュおよびwebhookの場合、これは、任意のメッセージがユーザーに送信されたときです。<br><br> WhatsAppの場合、これは、メッセージがユーザーの機器に配信されたときではなく、最後のメッセージAPIリクエストがWhatsAppに送信されたときです。<br><br>メールの場合、メールリクエストが (実際に配信されたかどうかに関係なく) メールサービスプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新されます。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、これは最後のメッセージがSMSプロバイダーに配信されたときです。これは、メッセージがユーザーの機器に配信されたことを保証するものではありません。<br><br>例: <br>前回受信メール1日未満=24時間未満<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Retargeting
   - name: メッセージへの最終エンゲージ
-    description: "ユーザーを前回クリックまたは開封したときに、メッセージング チャネルのいずれか(コンテンツカード、メール、インアプリ、SMS、プッシュ、WhatsApp)をセグメント化します。マシン開封s またはメールの他の開封s でフィルターするための選択肢が含まれています。(24時間)<br><br>メール sの場合、メールリクエストが(実際に配信されたかどうかに関係なく)そのプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新 d です。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、ユーザークリック\"トラッキングが有効になっているメッセージ内の短縮リンクを最後に選択したユーザー。<br><br>タイムゾーン:<br>会社のタイムゾーン"
+    description: "メッセージングチャネルのいずれか (コンテンツカード、メール、アプリ内、SMS、プッシュ通知、WhatsApp) を最後にクリックまたは開封した日時によって、ユーザーをセグメント化します。マシン開封数またはメールのその他の開封数でフィルタリングするオプションが含まれています。(24時間)<br><br>メールの場合、メールリクエストが (実際に配信されたかどうかに関係なく) メールサービスプロバイダーに送信されるときです。複数のユーザーが同じメールアドレスを共有している場合:<br>- 最初の送信では、指定されたターゲットユーザーのプロファイルのみが更新されます。<br>- メールが配信されたとき、またはユーザーがメールまたはメール内のリンクを開封する場合、そのユーザーアドレスを共有するすべてのユーザーは、メッセージを受信するように耳を傾けます。<br><br>SMSの場合、ユーザークリック\"トラッキングが有効になっているメッセージ内の短縮リンクを最後に選択したユーザー。<br><br>タイムゾーン:<br>会社のタイムゾーン"
     tags:
       - Retargeting
-  - name: クリックカード 
-    description: "コンテンツカードをクリックしたかどうかによって、ユーザーを分割します。このフィルターは、\"Clicked/開封/キャンペーン\"、\"Clicked/開封 またはCanvas with Tag\"、および\"Clicked/開封 \"のサブフィルターとして使用できます。ステップ\""
+  - name: クリックされたカード 
+    description: 特定のコンテンツカードをクリックしたかどうかによってユーザーをセグメント化します。このフィルターは、「キャンペーンをクリック/開封」、「タグ付きのキャンペーンまたはキャンバスをクリック/開封」、および「ステップをクリック/開封」のサブフィルターとして使用できます。
     tags:
       - Retargeting
   - name: フィーチャーフラグ
@@ -267,47 +267,47 @@ glossaries:
     tags:
       - Retargeting
   - name: サブスクリプショングループ
-    description: メール、SMS/MMS、またはWhatsAppのサブスクリプショングループでユーザーを分割します。アーカイブグループは耳元をアプリせず、使用できません。
+    description: メール、SMS/MMS、またはWhatsAppのサブスクリプショングループでユーザーを分割します。アーカイブ済みグループは表示されず、使用できません。
     tags:
       - Channel subscription behavior
   - name: 利用可能なメール
-    description: ユーザーを、有効なメールアドレスを持っているかどうか、およびメールにサブスクライブ/オプトインしているかどうかによってセグメント化します。メール利用可能なフィルターは、ユーザーがメールsから配信停止dであるかどうか、Brazeがハードバウンスを受信したかどうか、およびスパムとしてマークされたかどうかの3つの基準を確認します。これらの基準のいずれかが満たされている場合、またはメールがユーザーに存在しない場合、ユーザーは含まれません。
+    description: ユーザーを、有効なメールアドレスを持っているかどうか、およびメールにサブスクライブ/オプトインしているかどうかによってセグメント化します。「メールが利用可能」フィルターは、ユーザーがメールを配信停止したかどうか、Braze がハードバウンスを受信したかどうか、およびスパムとしてマークされたかどうかの 3 つの基準を確認します。これらの基準のいずれかが満たされている場合、またはメールがユーザーに存在しない場合、ユーザーは含まれません。
     tags:
       - Channel subscription behavior
-  - name: メール選択日
-    description: ユーザーをメールに選択した日に分割します。
+  - name: メールオプトイン日
+    description: メールをオプトインした日付によってユーザーをセグメント化します。
     tags:
       - Channel subscription behavior
   - name: メールサブスクリプションステータス
-    description: メールのサブスクリプション ステータスでユーザーを分割します。
+    description: メールのサブスクリプション ステータスによってユーザーをセグメント化します。
     tags:
       - Channel subscription behavior
-  - name: メール未購読日付 
-    description: ユーザーs を、将来のメールs からd を配信停止した日に分割します。
+  - name: メールの配信停止日 
+    description: 今後のメールを配信停止した日付によってユーザーをセグメント化します。
     tags:
       - Channel subscription behavior
   - name: プッシュ通知が有効
-    description: 暫定的なプッシュ認証があるか、フォアグラウンドプッシュが有効になっているユーザーをセグメント化します。特に、このカウントには以下が含まれます。<br>1. 暫定的にプッシュを許可されているiOS ユーザー。<br>2.ワークスペース内の任意のアプリに対してプッシュ通知を明示的にアクティブ化したユーザ。これらのユーザーs では、この数にはフォアグラウンドプッシュのみが含まれます。<br><br>プッシュ有効は、配信停止 d を持つユーザーを含みません。<br><br>このSegmentでフィルターを実行すると、<em>Reachable Users</em> という名前のAndroid、iOS、ウェブサイトのユーザーの内訳が下部に表示されます。
+    description: 暫定的なプッシュ認証があるか、フォアグラウンドプッシュが有効になっているユーザーをセグメント化します。具体的には、このカウントには以下が含まれます。<br>1. 暫定的にプッシュが承認されている iOS ユーザー。<br>2.ワークスペース内の任意のアプリに対してプッシュ通知を明示的にアクティブ化したユーザー。これらのユーザーの場合、この数にはフォアグラウンドプッシュのみが含まれます。<br><br>「プッシュ通知が有効」には、配信停止済みのユーザーは含まれません。<br><br>このSegmentでフィルターを実行すると、<em>Reachable Users</em> という名前のAndroid、iOS、ウェブサイトのユーザーの内訳が下部に表示されます。
     tags:
       - Channel subscription behavior
   - name: アプリのプッシュ有効化
-    description: ユーザーが機器のアプリに対してプッシュを有効にしているかどうかによって区切ります。これらのユーザーs はプッシュで到達可能ですが、オプトインされない可能性があります。この数には、仮にフォアグラウンドおよびバックグラウンド プッシュトークンs を許可されたユーザーが含まれます。
+    description: デバイス上のアプリでプッシュ通知を有効にしているかどうかによってユーザーをセグメント化します。これらのユーザーはプッシュで到達可能ですが、オプトインされない可能性があります。この数には、仮にフォアグラウンドおよびバックグラウンドのプッシュトークンを暫定的に承認されたユーザーが含まれます。
     tags:
       - Channel subscription behavior
   - name: バックグラウンドプッシュ有効
     description: バックグラウンドプッシュが有効になっているかどうかに基づいて、ユーザーをセグメント化します。
     tags:
       - Channel subscription behavior
-  - name: Opt In Dateを押します
-    description: プッシュを選択した日にユーザーを分割します。
+  - name: プッシュ通知のオプトイン日
+    description: プッシュ通知をオプトインした日付によってユーザーをセグメント化します。
     tags:
       - Channel subscription behavior
-  - name: プッシュサブスクリプションステータス
+  - name: プッシュ通知のサブスクリプションのステータス
     description: "ユーザーを<a href=\"/docs/user_guide/message_building_by_channel/push/users_and_subscriptions/#push-subscription-state\">サブスクリプション ステータス</a> でセグメント化してプッシュします。"
     tags:
       - Channel subscription behavior
-  - name: 登録解除日を押す
-    description: ユーザーs を、将来のプッシュ通知s からd を配信停止した日に分割します。
+  - name: プッシュ通知の配信停止日
+    description: 今後のプッシュ通知を配信停止した日付によってユーザーをセグメント化します。
     tags:
       - Channel subscription behavior
   - name: 購入した製品
@@ -315,27 +315,27 @@ glossaries:
     tags:
       - Purchase behavior
   - name: 購入数の合計
-    description: ユーザーのアプリでの購買数を分割します。
+    description: アプリでの購入数によってユーザーをセグメント化します。
     tags:
       - Purchase behavior
-  - name: X Y日購入商品
+  - name: Y 日間に購入した製品 X
     description: 指定の商品を購入した回数でユーザーをフィルターします。
     tags:
       - Purchase behavior
   - name: 過去 Y 日間の X 回の購入
-    description: "ユーザーを、1 から30 の間の最後に指定されたカレンダー日数に購入した回数(0 から50 の間) でセグメント化します。<br> <a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a>"
+    description: "最後に指定された暦日数 (1 ～ 30 日) の間に、購入を行った回数 (0 ～ 50 回) によってユーザーをセグメント化します。<br> <a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a>"
     tags:
       - Purchase behavior
   - name: X Y日以内に物件を購入
-    description: "ユーザーs を、1 から30 の間の最後の指定されたカレンダ日数の特定の購買プロパティに関連して購買が行われた回数でセグメント化します。<br> <a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a>"
+    description: "最後に指定された暦日数 (1 ～ 30 日) の間に、特定の購入プロパティに関連して購入を行った回数 (0 ～ 50 回) によってユーザーをセグメント化します。<br> <a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a>"
     tags:
       - Purchase behavior
   - name: 最初に行った購入
-    description: ユーザーがアプリで購買した最も早い時点までに、ユーザーを分割します。
+    description: アプリ内で購入を行った最も早い時刻によってユーザーをセグメント化します。
     tags:
       - Purchase behavior
   - name: アプリでの最初の購入
-    description: ユーザーがアプリから購入した最も早い時点までに、ユーザーを分割します。
+    description: アプリから購入を行った最も早い時刻によってユーザーをセグメント化します。
     tags:
       - Purchase behavior
   - name: 前回購入
@@ -347,11 +347,11 @@ glossaries:
     tags:
       - Purchase behavior
   - name: 支出金額
-    description: ユーザーを、アプリで費やした金額で分割します。
+    description: アプリで費やした金額によってユーザーをセグメント化します。
     tags:
       - Purchase behavior
   - name: X 日間に支出した金額
-    description: "ユーザーを、1 から30 までの最後に指定されたカレンダ日数でアプリに費やした金額でセグメント化します。この金額には、最後の50 回の購入の合計のみが含まれます。<br> <a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a>"
+    description: "最後に指定された暦日数 (1 ～ 30 日) の間に、アプリで費やした金額によってユーザーをセグメント化します。この金額には、最後の50 回の購入の合計のみが含まれます。<br> <a href=\"/docs/x-in-y-behavior/\">ここでは、X-in-Y の動作について詳しく説明します。</a>"
     tags:
       - Purchase behavior
   - name: 国
@@ -359,7 +359,7 @@ glossaries:
     tags:
       - Demographic attributes
   - name: 市区町村
-    description: ユーザーを、最後に示された都市の場所でセグメント化します。
+    description: 最後に示された市区町村の場所によってユーザーをセグメント化します。
     tags:
       - Demographic attributes
   - name: 言語
@@ -367,11 +367,11 @@ glossaries:
     tags:
       - Demographic attributes
   - name: 年齢
-    description: ユーザーをアプリ内から示すように、年代別に分割します。
+    description: ユーザーをアプリ内で示した年齢によってセグメント化します。
     tags:
       - Demographic attributes
   - name: 生年月日
-    description: "アプリ内から示されているように、ユーザーを誕生日ごとに分割します。<br> 2月29日に誕生日を迎える利用者は、3月1日を含むSegmentsに含まれます。<br><br>12 月または1 月の誕生日をターゲットにするには、ターゲットとする年の12 か月の期間内にフィルターロジックのみを挿入します。言い換えれば、前の暦年の12月を振り返るロジックや、翌年の1月までのフォワードロジックを挿入しないでください。たとえば、12 月の誕生日を目標にするには、\" 12 月31 日\" \" 12 月31 日\" または\" を11 月30 日\" の後にフィルターします。"
+    description: ユーザーをアプリ内で示した誕生日によってセグメント化します。<br> 2 月 29 日に誕生日を迎えるユーザーは、3 月 1 日を含むセグメントに含まれます。<br><br>12 月または 1 月の誕生日をターゲットにするには、ターゲットとする年の 12 か月の期間内のフィルターロジックのみを挿入してください。言い換えれば、前の暦年の12月を振り返るロジックや、翌年の1月までのフォワードロジックを挿入しないでください。たとえば、12 月の誕生日をターゲットにするには、「12 月 31 日」、「12 月 31 日の前」、または「11 月 30 日の後」でフィルタリングすることができます。
     tags:
       - Demographic attributes
   - name: 性別
@@ -383,43 +383,43 @@ glossaries:
     tags:
       - Demographic attributes
   - name: 名
-    description: アプリ内から示されたように、ユーザーを名で分割します。
+    description: ユーザーをアプリ内で示した名によってセグメント化します。
     tags:
       - Demographic attributes
   - name: 姓
-    description: ユーザーを、アプリ内から示された姓でセグメント化します。
+    description: ユーザーをアプリ内で示した姓でセグメント化します。
     tags:
       - Demographic attributes
   - name: アプリあり
-    description: ユーザーがアプリをインストールしたことがあるかどうかによって分割されます。これには、現在アプリがインストールされているユーザーと、以前にアンインストールされたものが含まれます。通常、このフィルターに含めるアプリを開封する(セッションを起動する)には、ユーザーsが必要です。ただし、ユーザーがBraze にインポートされ、アプリに手動で関連付けられた場合など、いくつかの例外があります。
+    description: ユーザーがアプリをインストールしたことがあるかどうかによって分割されます。これには、現在アプリがインストールされているユーザーと、以前にアンインストールされたものが含まれます。通常、このフィルターに一致するには、ユーザーがアプリを開封する (セッションを開始する) 必要があります。ただし、ユーザーがBraze にインポートされ、アプリに手動で関連付けられた場合など、いくつかの例外があります。
     tags:
       - App
   - name: 最新のアプリバージョン名
-    description: ユーザーのアプリの最近の名前によって分割されます。
+    description: ユーザーのアプリの最新の名前によってセグメント化します。
     tags:
       - App 
   - name: 最新のアプリバージョン番号
-    description: アプリのユーザーの最新版番号によって分割されます。
+    description: ユーザーのアプリの最新バージョン番号によってセグメント化します。
     tags:
       - App 
   - name: アンインストール
-    description: アプリをアンインストールし、再インストールしていないかどうかによって、ユーザーを分割します。
+    description: アプリをアンインストールした後、再インストールしていないかどうかによって、ユーザーをセグメント化します。
     tags:
       - Uninstall 
   - name: デバイスの通信事業者
-    description: デバイスキャリアごとにユーザーを分割します。
+    description: デバイスの通信事業者によってユーザーをセグメント化します。
     tags:
       - Devices
   - name: デバイス数
-    description: ユーザーを、アプリを使用した機器の数で分割します。
+    description: アプリを使用したデバイスの数でユーザーをセグメント化します。
     tags:
       - Devices
   - name: デバイスモデル
     description: 携帯電話機の機種別にユーザーを分割します。
     tags:
       - Devices
-  - name: デバイスOS
-    description: 指定したオペレーティングシステムを持つ1つ以上の装置を持つユーザーをセグメント化します。
+  - name: デバイス OS
+    description: 指定のオペレーティングシステムを持つ 1 台以上のデバイスを持つユーザーをセグメント化します。
     tags:
       - Devices
   - name: 最新のデバイスロケール
@@ -430,7 +430,7 @@ glossaries:
     description: ユーザーを最新のスマートウォッチモデルでセグメント化します。
     tags:
       - Devices    
-  - name: iOSで仮承認
+  - name: iOS で暫定的に承認済み
     description: iOS 12 で特定のアプリに対して暫定的に許可されているユーザーを検索できます。
     tags:
       - Devices   
@@ -439,19 +439,19 @@ glossaries:
     tags:
       - Devices
   - name: デバイスIDFA
-    description: テストするキャンペーン 受信者をIDFA で指定できます。
+    description: テスト用のキャンペーン受信者を IDFA で指定できます。
     tags:
       - Advertising use cases
-  - name: デバイスIDFV
+  - name: デバイス IDFV
     description: テスト用にIDFV でキャンペーン 受信者を指定できます。
     tags:
       - Advertising use cases 
-  - name: デバイスGoogle Ad ID
+  - name: デバイスの Google 広告 ID
     description: ユーザーをグーグルの広告ID でセグメント化します。
     tags:
       - Advertising use cases
-  - name: デバイスロク広告ID
-    description: ユーザーを道路番号で分割します。
+  - name: デバイスの Roku 広告 ID
+    description: ユーザーを Roku 広告 ＩＤ でセグメント化します。
     tags:
       - Advertising use cases
   - name: デバイスのWindows Ad ID
@@ -459,7 +459,7 @@ glossaries:
     tags:
       - Advertising use cases  
   - name: 広告の追跡が有効
-    description: "ユーザーがアド\"トラッキングを選択しているかどうかに基づいてフィルターできます。広告\"トラッキングはIDFA または&amp;quot に関連します。広告主&amp;quot の識別子。Apple によってすべてのiOS 機器に割り当てられます。これはSDK s によって設定できます。この識別子により、広告主はユーザーsを追跡し、ターゲット広告を提供することができます。"
+    description: ユーザーが広告の追跡をオプトインしているかどうかに基づいてフィルターできます。広告の追跡は IDFA または Apple によってすべての iOS 機器に割り当てられている「広告主用の識別子」に関連します。これは SDK によって設定できます。この識別子により、広告主はユーザーを追跡し、ターゲット広告を提供することができます。
     tags:
       - Advertising use cases
   - name: 最新の場所
@@ -467,62 +467,62 @@ glossaries:
     tags:
       - Location
   - name: 利用可能な場所
-    description: "ユーザーの位置がレポートされているかどうかによって、それらをセグメント化します。このフィルターを使用するには、アプリに<a href=\"/docs/search/?query=location%20tracking\">位置\"トラッキングが統合されている必要があります。</a>"
+    description: "ユーザーの位置がレポートされているかどうかによって、それらをセグメント化します。このフィルターを使用するには、アプリに<a href=\"/docs/search/?query=location%20tracking\">位置情報の追跡が統合</a>されている必要があります。"
     tags:
       - Location
-  - name: Amplitudeコホート
-    description: Amplitude を使用するクライアントは、Amplitude でコホートs を選択してインポートすることで、Segmentを補完できます。
+  - name: Amplitude コホート
+    description: Amplitude を使用するクライアントは、Amplitude でコホートを選択してインポートすることで、セグメントを補完できます。
     tags:
       - Cohort membership
-  - name: Censusコホート
-    description: Census を使用するクライアントは、Census でコホートs を選択してインポートすることで、Segmentを補完できます。
+  - name: Census コホート
+    description: Census を使用するクライアントは、Census でコホートを選択してインポートすることで、セグメントを補完できます。
     tags:
       - Cohort membership
-  - name: ヒープコホート
-    description: ヒープを使用するクライアントは、ヒープ内のコホートを選択してインポートすることで、Segmentを補完できます。
+  - name: Heap コホート
+    description: Heap を使用するクライアントは、Heap 内のコホートを選択してインポートすることで、セグメントを補完できます。
     tags:
       - Cohort membership
-  - name: Hightouchコホート
-    description: Hightouch を使用するクライアントは、Hightouch でコホートs を選択してインポートすることで、Segmentを補完できます。
+  - name: Hightouch コホート
+    description: Hightouch を使用するクライアントは、Hightouch でコホートを選択してインポートすることで、セグメントを補完できます。
     tags:
       - Cohort membership
   - name: Kubitコホート
-    description: Kubit を使用するクライアントは、Kubit でコホートs を選択してインポートすることで、Segmentを補完できます。
+    description: Kubit を使用するクライアントは、Kubit でコホートを選択してインポートすることで、セグメントを補完できます。
     tags:
       - Cohort membership
-  - name: ミックスパネルコホート
-    description: Mixpanel を使用するクライアントは、Mixpanel でコホートを選択してインポートすることで、Segmentを補完できます。
+  - name: Mixpanel コホート
+    description: Mixpanel を使用するクライアントは、Mixpanel でコホートを選択してインポートすることで、セグメントを補完できます。
     tags:
       - Cohort membership
   - name: セグメントコホート
-    description: Segment を使用するクライアントは、Segment でコホートを選択してインポートすることで、そのSegmentを補完できます。
+    description: Segment を使用するクライアントは、Segment でコホートを選択してインポートすることで、セグメントを補完できます。
     tags:
       - Cohort membership
-  - name: 微小なコホート
-    description: Tinyclues を使用するクライアントは、Tinyclues でコホートを選択してインポートすることで、Segmentを補完できます。
+  - name: Tinyclues コホート
+    description: Tinyclues を使用するクライアントは、Tinyclues でコホートを選択してインポートすることで、セグメントを補完できます。
     tags:
       - Cohort membership
-  - name: 属性アドのインストール
-    description: インストール先がd 属性であった広告によって、ユーザーs をセグメント化します。
+  - name: インストールアトリビューション広告
+    description: インストールアトリビューションとなった広告によってユーザーをセグメント化します。
     tags:
       - User Attributes
-  - name: 属性Adgroupのインストール
-    description: ユーザーs を、そのインストール先がd 属性であった広告グループによってセグメント化します。
+  - name: インストールアトリビューション広告グループ
+    description: インストールアトリビューションとなった広告グループによってユーザーをセグメント化します。
     tags:
       - Install Attribution
-  - name: 属性のインストールキャンペーン
+  - name: インストールアトリビューションキャンペーン
     description: インストール先が属性である広告キャンペーンによって、ユーザーs をセグメント化します。
     tags:
       - Install Attribution
-  - name: 属性ソースのインストール
-    description: ユーザーを、インストール先が属性dであった送信元別にセグメント化します。
+  - name: インストールアトリビューションソース
+    description: インストールアトリビューションとなったソースによってユーザーをセグメント化します。
     tags:
       - Install Attribution
-  - name: チャーン・リスク分類
+  - name: 解約リスクカテゴリ
     description:  ユーザーを、具体的な予測に応じて、解約リスクカテゴリ別にセグメント化します。
     tags:
       - Intelligence and predictive
-  - name: チャーン・リスクスコア
+  - name: 解約リスクスコア
     description: ユーザーを、具体的な予測に応じて、チャーンリスクスコア別にセグメント化します。
     tags:
       - Intelligence and predictive
@@ -538,19 +538,19 @@ glossaries:
     description: 過去3 カ月間で最も有効なチャネルごとにユーザーを分割します。
     tags:
       - Intelligence and predictive
-  - name: メッセージオープン可能性
-    description: "指定したチャネルに0 ～100% の範囲で開封する可能性に基づいてユーザーをフィルタリングします。チャネルの可能性を測定するのに十分なデータがないユーザは、\"is blank.&amp;quot を使用して選択できます。"
+  - name: メッセージ開封の可能性
+    description: 指定したチャネルに0 ～100% の範囲で開封する可能性に基づいてユーザーをフィルタリングします。チャネルの可能性を測定するのに十分なデータがないユーザーは、「空白である」を使用して選択できます。
     tags:
       - Intelligence and predictive
-  - name: アプリを利用しているファクスeBookの友達の人数
-    description: ユーザーを、同じアプリを使用しているFac eBookの友達の数でセグメント化します。
+  - name: アプリを使用している Facebook の友達の人数
+    description: 同じアプリを使用している Facebook の友達の人数でユーザーをセグメント化します。
     tags:
       - Social activity
-  - name: 接続されたFaceBook
-    description: アプリをファクスeBookに接続したかどうかによって、ユーザーを分割します。
+  - name: Facebook でつながりがある
+    description: アプリを Facebook に接続したかどうかによって、ユーザーをセグメント化します。
     tags:
       - Social activity
-  - name: 接続済みTwitter
+  - name: Twitter でつながりがある
     description: アプリをX(以前のTwitter)に接続したかどうかによって、ユーザーをセグメント化します。
     tags:
       - Social activity
diff --git a/_lang/ja/_user_guide/engagement_tools/segments/sql_segments.md b/_lang/ja/_user_guide/engagement_tools/segments/sql_segments.md
index afd47973167..35afb3e2a91 100644
--- a/_lang/ja/_user_guide/engagement_tools/segments/sql_segments.md
+++ b/_lang/ja/_user_guide/engagement_tools/segments/sql_segments.md
@@ -46,7 +46,7 @@ SQL セグメントエクステンションの作成時に選択できる SQL 
 4\.セグメントエクステンションを保存します。
 
 {% endtab %}
-{% tab インクリメンタル・リフレッシュ %}
+{% tab 増分更新 %}
 
 増分更新 SQL エディターを使用すると、特定の時間枠内のイベントについて、日付ごとにユーザークエリ集計を行うことができます。増分更新 SQL セグメントエクステンションを作成するには以下を実行します。
 
@@ -62,7 +62,7 @@ SQL セグメントエクステンションの作成時に選択できる SQL 
 3\.セグメントエクステンションの名前を追加し、SQL を入力します。要件とリソースについては、\[[SQL の作成](#writing-sql)] セクションを参照してください。<br><br>
    ![インクリメンタルSQLセグメント拡張の例を示すSQLエディター。]({% image_buster /assets/img_archive/sql_segments_editor_incremental.png %}){: style="max-width:60%" }<br><br>
 4\.必要に応じて、\[**エクステンションを毎日再生成する**] を選択します。<br><br>
-   ![] （{% image_buster /assets/img_archive/sql_segments_regenerate.png %} ）。{: style="max-width:60%" }<br><br>
+   ![エクステンションを毎日再生成するチェックボックス。]({% image_buster /assets/img_archive/sql_segments_regenerate.png %}){: style="max-width:60%" }<br><br>
    選択すると、Braze はセグメントメンバーシップを毎日自動的に更新します。つまり、毎日会社のタイムゾーンの午前0時 (1時間遅れる可能性があります) に、Braze はセグメントの新規ユーザーを確認し、自動的にセグメントに追加します。セグメントエクステンションを 7 日間使用しなかった場合、Braze は毎日の再生成を自動的に一時停止します。未使用のセグメントエクステンションとは、キャンペーンやキャンバスの一部ではないエクステンションです (エクステンションが「使用済み」と見なされるには、キャンペーンまたはキャンバスがアクティブでなくてもかまいません)。<br><br>
 5. セグメントエクステンションを保存します。
 
@@ -76,7 +76,7 @@ AI SQL ジェネレーターは現在、ベータ機能としてご利用いた
 
 AI SQL ジェネレーターは OpenAI を搭載した [GPT](https://openai.com/gpt-4) を活用して、お客様の SQL セグメントに SQL を推奨します。
 
-![プロンプト "先月通知を受け取ったユーザー "のAI SQLジェネレーター]({% image_buster /assets/img/ai_sql_generator.png %}){: style="max-width:70%;"}
+![「先月に通知を受信したユーザー」というプロンプトが表示された AI SQL ジェネレーター]({% image_buster /assets/img/ai_sql_generator.png %}){: style="max-width:70%;"}
 
 AI SQL ジェネレーターを使用するには、以下を実行します。
 
@@ -103,7 +103,7 @@ SQL を生成するために、Braze はプロンプトを OpenAI の API プラ
 実行に20分以上かかる SQL クエリはタイムアウトします。
 {% endalert %}
 
-エクステンションの処理が完了したら、\[セグメントエクステンションを使用してセグメント][4] を作成し、キャンペーンやキャンバスでこの新しいセグメントをターゲットにすることができる。
+エクステンションの処理が完了したら、セグメントエクステンションを使用して \[セグメントを作成][4] し、この新しいセグメントをキャンペーンやキャンバスでターゲットにすることができます。
 
 ## SQL の記述
 
@@ -130,24 +130,24 @@ SELECT DISTINCT user_id FROM "INSERT TABLE NAME"
    2. セグメント内のセグメントエクステンションを参照する場合、`doesn't include` を選択すると結果が反転します。
 
 {% endtab %}
-{% tab インクリメンタルSQLエディター %}
+{% tab 増分 SQL エディター %}
 
 すべての増分更新クエリは、クエリとスキーマの詳細という2つの部分で構成されます。
 
 1. エディターで、目的のテーブルから `user_id` を選択するクエリを記述します。
 2. エディターの上のフィールドから \[**演算子**]、\[**回数**]、および \[**期間**] を選択して、スキーマの詳細を追加します。クエリでは、集計列の合計が {% raw %}`{{operator}}` および `{{number of times}}`{% endraw %} プレースホルダーで指定された特定の条件を満たすかどうかが確認されます。これは、従来のセグメントエクステンションを作成するワークフローと同様に機能します。<br><br>
    - **演算子:**イベントの発生回数が、発生回数よりも多いか、少ないか、等しいかを示します。<br>
-   ![以上」が選択された演算子フィールド]({% image_buster /assets/img_archive/sql_segments_operator.png %})<br><br>
+   ![「超 (過去)」が選択された演算子フィールド。]({% image_buster /assets/img_archive/sql_segments_operator.png %})<br><br>
    - **回数:**演算子に関してイベントを評価したい回数。<br>
-   ![5」が入力された回数]({% image_buster /assets/img_archive/sql_segments_times.png %})<br><br>
+   ![「5」が入力された回数フィールド。]({% image_buster /assets/img_archive/sql_segments_times.png %})<br><br>
    - **期間:**イベントのインスタンスを確認する日数 (1 ～ 730日)。この期間は、現在の日を基準とした過去の日数を指します。次の例は、過去365日間にイベントを5回以上実行したユーザーのクエリを示しています。<br>
-   ![期間フィールドに "365 "が入力されている。]({% image_buster /assets/img_archive/sql_segments_period.png %})
+   ![「365」が入力された期間フィールド。]({% image_buster /assets/img_archive/sql_segments_period.png %})
 
 次の例では、結果のセグメントには、指定した日付以降の過去3日間に `favorited` イベントを3回以上実行したユーザーが含まれます。
 
 ![インクリメンタルSQLセグメント拡張の例を示すSQLエディター。]({% image_buster /assets/img_archive/sql_segments_editor_incremental.png %}){: style="max-width:65%" }
 
-![増分SQLセグメント拡張のSQLプレビュー。]({% image_buster /assets/img_archive/sql_segments_incremental_preview.png %}){: style="max-width:85%" }
+![増分 SQL セグメントエクステンションの SQL プレビュー。]({% image_buster /assets/img_archive/sql_segments_incremental_preview.png %}){: style="max-width:85%" }
 
 ### その他の規則
 
@@ -176,7 +176,7 @@ SELECT DISTINCT user_id FROM "INSERT TABLE NAME"
 
 SQL セグメントエクステンションを選択すると、そのエクステンションが使用されている場所を表示したり、エクステンションをアーカイブしたり、[セグメントのメンバーシップを手動で更新](#refreshing-segment-membership)したりできます。
 
-![SQLエディターのMessaging Useセクションは、SQLセグメントがどこで使用されているかを示している。][3]
+![SQL セグメントの使用場所を示す SQL エディターの「Messaging Use」セクション。][3]
 
 ### セグメントのメンバーシップの更新
 
@@ -200,7 +200,7 @@ Snowflake クレジットは機能間で共有されません。例えば、SQL
 
 クレジットは、毎月1日午前12 時 (UTC) に5にリセットされます。クレジット使用状況パネルで、その月のクレジット使用状況を監視できます。\[**セグメントエクステンション**] ページから、\[<i class="fa-solid fa-chart-column"></i>**SQL クレジット使用状況を表示**] をクリックします。
 
-![SQL Segment ExtensionsページのSQL Credit Usageパネル][5]{: style="max-width:60%"}
+![SQL セグメントエクステンションページの SQL クレジット使用状況パネル][5]{: style="max-width:60%"}
 
 クレジットがゼロになると、次のことが起こります。
 
diff --git a/_lang/ja/_user_guide/engagement_tools/testing/multivariant_testing/optimizations.md b/_lang/ja/_user_guide/engagement_tools/testing/multivariant_testing/optimizations.md
index 79c0277df14..1820f6554ad 100644
--- a/_lang/ja/_user_guide/engagement_tools/testing/multivariant_testing/optimizations.md
+++ b/_lang/ja/_user_guide/engagement_tools/testing/multivariant_testing/optimizations.md
@@ -10,7 +10,7 @@ description: "多変量テストと AB テストを作成する際に、勝者
 
 1回送信するようにスケジュールされたメール、プッシュ、Webhook、SMS、WhatsApp キャンペーンの [AB テストを作成する][1]際に、最適化を選択できます。最適化には2つのオプションがあります。**勝利バリアント**と**パーソナライズされたバリアント**。
 
-![目的のオーディエンスを選択するときに、AB テストの項に記載されている最適化オプション。次の3 つのオプションが表示されます。最適化なし、勝利バリアント、個人用バリアント。Personalized Variant is selected.]({% image_buster /assets/img_archive/ab_personalized_variant.png %})
+![目的のオーディエンスを選択するときに、AB テストの項に記載されている最適化オプション。次の3 つのオプションが表示されます。最適化なし、勝利バリアント、個人用バリアント。パーソナライズされたバリアントが選択されています。]({% image_buster /assets/img_archive/ab_personalized_variant.png %})
 
 どちらのオプションも、ターゲットセグメントの一定の割合に初期テストを送信することで機能します。テスト終了後、オーディエンスの残りのユーザーには、最もパフォーマンスの高いバリアント (勝者バリアント) またはエンゲージメントの可能性が最も高いバリアント (パーソナライズされたバリアント) のいずれかが送信されます。
 
@@ -28,9 +28,9 @@ description: "多変量テストと AB テストを作成する際に、勝者
 | フィールド | 説明 |
 | --- | --- | 
 | 最適化メトリック | 最適化するメトリック。メールの場合は「*ユニーク開封数*」または「*クリック数*」、プッシュの場合は「*開封数*」、すべてのチャネルの場合は「*1次コンバージョン率*」のいずれかを選択します。\[*開封数*] または \[*クリック数*] を選択して勝者を決定しても、キャンペーンの[コンバージョンイベント]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/conversion_events/)の選択には影響しません。<br><br>コントロールグループを使用している場合、コントロールグループのユーザーは \[*開封*] や \[*クリック*] を実行できないため、コントロールグループのパフォーマンスは `0` であることが保証されます。その結果、コントロールグループは AB テストに勝つことができません。ただし、コントロールグループを使用して、メッセージを受信しないユーザーの他のメトリクスを追跡することもできます。 |
-| 初回試験開始日 | 最初のテストが開始される日時。 |
-| 初回試験終了日 | 最初のテストが終了する日時。勝者バリアントが残りのユーザーに送信されるタイミングです。<br><br>ユーザーの現地時刻またはインテリジェント・タイミングで送信する場合、A/Bテスト後少なくとも24時間は、Winning Variantグループのすべてのユーザーに配信するために、Winning Variantを送信する必要があります。 |
-| フォールバック | hがアプリするのは、バリアントが統計的に有意な余裕で勝利しない場合である。とにかく最高のパフォーマンスのバリアントを送信するか、試験を終了してそれ以上のメールを送信しないかを選択します。 |
+| 最初のテスト開始日 | 最初のテストが開始される日時。 |
+| 最初のテスト終了日 | 最初のテストが終了する日時。勝者バリアントが残りのユーザーに送信されるタイミングです。<br><br>ユーザーの現地時間またはインテリジェントタイミングで送信する場合は、勝者バリアントを AB テストの少なくとも 24 時間後に送信して、勝者バリアントグループのすべてのユーザーに確実に配信する必要があります。 |
+| フォールバック | 統計的に有意な差をつける勝者バリアントがない場合の動作。とにかく最高のパフォーマンスのバリアントを送信するか、試験を終了してそれ以上のメールを送信しないかを選択します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## パーソナライズされたバリアント
@@ -45,9 +45,9 @@ description: "多変量テストと AB テストを作成する際に、勝者
 | フィールド | 説明 |
 | --- | --- | 
 | 最適化メトリック | 最適化するメトリック。メールの場合は「*ユニーク開封数*」または「*クリック数*」、プッシュの場合は「*開封数*」、すべてのチャネルの場合は「*1次コンバージョン率*」のいずれかを選択します。\[*開封数*] または \[*クリック数*] を選択して勝者を決定しても、キャンペーンの[コンバージョンイベント]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/conversion_events/#conversion-events)の選択には影響しません。<br><br>コントロールグループを使用している場合、コントロールグループのユーザーは \[*開封*] や \[*クリック*] を実行できないため、コントロールグループのパフォーマンスは `0` であることが保証されます。その結果、コントロールグループは AB テストに勝つことができません。ただし、コントロールグループを使用して、メッセージを受信しないユーザーの他のメトリクスを追跡することもできます。 |
-| 初回試験開始日 | 最初のテストが開始される日時。 |
-| 初回試験終了日 | 最初のテストが終了する日時。これは、パーソナライズされたバリアントが残りのユーザーに送信される場合です。統計的に有意で意味のある結果を得るために、24時間をベースラインとして推奨しています。テストに時間をかければかけるほど、より多くの応答を受け取ることができ、Braze はより最適化できます。メールキャンペーンでは特に重要です。パーソナライズされたバリアントの初期テストは4時間以上継続する必要があります。<br><br>ユーザーの現地時間またはインテリジェントタイミングで送信する場合は、Personalized Variant グループのすべてのユーザーに配信するために、Personalized Variant をA/B テストの少なくとも24 時間後に送信する必要があります。 |
-| フォールバック | h パーソナライズされたバリアントが見つからない場合に表示されるアプリ。代わりにWinning Variant を送信するか、テストを終了してそれ以上メッセージを送信しないかを選択します。 |
+| 最初のテスト開始日 | 最初のテストが開始される日時。 |
+| 最初のテスト終了日 | 最初のテストが終了する日時。これは、パーソナライズされたバリアントが残りのユーザーに送信される場合です。統計的に有意で意味のある結果を得るために、24時間をベースラインとして推奨しています。テストに時間をかければかけるほど、より多くの応答を受け取ることができ、Braze はより最適化できます。メールキャンペーンでは特に重要です。パーソナライズされたバリアントの初期テストは4時間以上継続する必要があります。<br><br>ユーザーの現地時間またはインテリジェントタイミングで送信する場合は、パーソナライズされたバリアントを AB テストの少なくとも 24 時間後に送信して、パーソナライズされたバリアントグループのすべてのユーザーに確実に配信する必要があります。 |
+| フォールバック | パーソナライズされたバリアントが見つからなかった場合の動作。代わりに勝者バリアントを送信するか、テストを終了してそれ以上メッセージを送信しないかを選択します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 分析
diff --git a/_lang/ja/_user_guide/engagement_tools/testing/race_conditions.md b/_lang/ja/_user_guide/engagement_tools/testing/race_conditions.md
index f5251bb542d..ab064a2a05c 100644
--- a/_lang/ja/_user_guide/engagement_tools/testing/race_conditions.md
+++ b/_lang/ja/_user_guide/engagement_tools/testing/race_conditions.md
@@ -37,7 +37,7 @@ Braze で最も一般的な競合状態の1つは、新しく作成されたユ
 前述のどちらのシナリオでも、これらのリクエストが同じAPIリクエストで行われれば問題はない。
 
 {% alert note %}
-ユーザー属性とイベントが同じリクエストで送信された場合（`/users/track` またはSDKから）、Brazeはイベントやメッセージの送信を試みる前に属性を処理する。
+ユーザー属性とイベントが同じリクエストで送信される場合 (`/users/track` または SDK から)、Braze は、イベントやメッセージの送信を試みる前に属性を処理します。
 {% endalert %}
 
 スケジュールされたメッセージ API リクエストを送信する場合、これらのリクエストは別個のものでなければならず、スケジュールされた API リクエストを送信する前にユーザーを作成しなければならないことに注意してください。
diff --git a/_lang/ja/_user_guide/getting_started/campaigns_canvases.md b/_lang/ja/_user_guide/getting_started/campaigns_canvases.md
index 23328d8104c..de572219baf 100644
--- a/_lang/ja/_user_guide/getting_started/campaigns_canvases.md
+++ b/_lang/ja/_user_guide/getting_started/campaigns_canvases.md
@@ -7,7 +7,7 @@ description: "この記事では、Braze でメッセージを送信するさま
 
 ---
 
-# はじめに: キャンペーンとキャンバス
+# 開始:キャンペーンとキャンバス
 
 Braze では、[キャンペーン](#campaigns)または[キャンバス](#canvas-flow)を介してメッセージを送信できます。
 
@@ -21,9 +21,9 @@ Braze では、[キャンペーン](#campaigns)または[キャンバス](#canva
 | キャンペーン種別        | 説明                                                                                                                                                                                                                                                                                              |
 | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | 通常              | これは最も一般的なキャンペーンです。メッセージの目標に応じて1つまたは複数のチャネルをターゲットに設定し、Braze のビジュアルエディターを使用してコンテンツを Braze 上で直接デザイン、カスタマイズ、テストできます。[ キャンペーン]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/creating_campaign) を作成する方法について説明します。 |
-| A/B テスト          | キャンペーン s が1 つのチャネルをターゲットにしている場合、同じキャンペーンの複数のバージョンを送信し、上に表示されるバージョンを確認できます。[多変量 キャンペーン]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/) を使用して、最大8 つのさまざまなバージョンのコピー、パーソナライゼーションなどをテストできます。 |
-| API                  | [API キャンペーン s]({{site.baseurl}}/api/api_campaigns/) を使用すると、できるだけ早くタイムリーなメッセージを送信できます。他のキャンペーンタイプとは異なり、Braze ダッシュボードではメッセージ、受信者、スケジュールを指定しません。代わりに、これらの識別子を API 呼び出しに渡します。これらは、通常、リアルタイム・トランス・アクションのメッセージングやニュースの更新に使用されます。  |
-| アクションメールを送信する | Braze [Trans アクション al メール s]({{site.baseurl}}/user_guide/message_building_by_channel/email/transactional_message_api_campaign/) は、お客様と顧客との間で合意されたトランスアクションを容易にするために、自動化された非プロモーションメールを送信する目的で構築されています。ビジネスクリティカルな通知を、スピードが最も重要な1人のユーザーに送信します。*選択したパッケージで使用できます。* |
+| A/B テスト          | 1 つのチャネルをターゲットとするキャンペーンの場合、同じキャンペーンの複数のバージョンを送信して、どれが一番効果が上がるかを確認できます。[多変量 キャンペーン]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/) を使用して、最大8 つのさまざまなバージョンのコピー、パーソナライゼーションなどをテストできます。 |
+| API                  | [API キャンペーン]({{site.baseurl}}/api/api_campaigns/)では、タイムリーなメッセージをできるだけ早く送信できます。他のキャンペーンタイプとは異なり、Braze ダッシュボードではメッセージ、受信者、スケジュールを指定しません。代わりに、これらの識別子を API 呼び出しに渡します。これらは通常、リアルタイムトランザクションメッセージングや最新ニュースに使用されます。  |
+| トランザクションメール | Braze [トランザクションメール]({{site.baseurl}}/user_guide/message_building_by_channel/email/transactional_message_api_campaign/)は、お客様とお客様の顧客との間で合意したトランザクションを円滑に進めるために、自動化されたプロモーション以外のメールメッセージを送信することを目的としています。ビジネスクリティカルな通知を、スピードが最も重要な1人のユーザーに送信します。*一部のパッケージでご利用いただけます。* |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
@@ -48,7 +48,7 @@ Braze のキャンペーンの詳細については、以下の追加リソー
 
 キャンバスを作成するときは、キャンペーンの設定と同じステップの多くに従います。つまり、オーディエンス全体、応募条件、送信設定を指定します。キャンバスは、誰かがトリガー条件に一致したときに起動します。その後、終了条件を満たすまで、キャンバス内のパス内を移動します。
 
-キャンバスには、[メッセージ]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/)、[遅延]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/delay_step/)、[実験]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/)などを自由に組み合わせることができます。サポートされているすべてのメッセージングチャネルで送信でき、Facebook、Google、TikTok などの[ソーシャルプラットフォームや広告プラットフォームと統合する]({{site.baseurl}}/partners/canvas_steps/overview/)こともできます。
+キャンバスには、[messages]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/)、[delays]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/delay_step/)、[experiments]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/)などを自由に組み合わせることができます。サポートされているすべてのメッセージングチャネルで送信でき、Facebook、Google、TikTok などの[ソーシャルプラットフォームや広告プラットフォームと統合する]({{site.baseurl}}/partners/canvas_steps/overview/)こともできます。
 
 キャンバスフローの詳細については、以下の追加リソースをご覧ください。
 
@@ -64,16 +64,16 @@ Braze のキャンペーンの詳細については、以下の追加リソー
 
 次の表は、サポートされているチャネルの概要です。
 
-| Channel                                                                                              | 説明                                                                                                                                            |
+| チャネル                                                                                              | 説明                                                                                                                                            |
 | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [メール]({{site.baseurl}}/user_guide/message_building_by_channel/email/about/)                        | パーソナライズされた メールs をユーザーの受信トレイes に送信します。                                                                                                       |
-| [モバイルプッシュ]({{site.baseurl}}/user_guide/message_building_by_channel/push/about/)                   | ユーザーの携帯電話に通知で送る。                                                                                   |
+| [メール]({{site.baseurl}}/user_guide/message_building_by_channel/email/about/)                        | パーソナライズされたメールをユーザーの受信トレイに送信します。                                                                                                       |
+| [モバイルプッシュ]({{site.baseurl}}/user_guide/message_building_by_channel/push/about/)                   | メッセージをユーザーのモバイルデバイスに通知として直接配信します。                                                                                   |
 | [Web プッシュ]({{site.baseurl}}/user_guide/message_building_by_channel/push/web)                         | Web サイトでアクティブでない場合でも、通知をユーザーのウェブブラウザに配信します。                                                         |
-| [アプリ内メッセージ]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/about/)    | ユーザー s が積極的に使用している間、モバイルアプリ内のメールを表示します。                                                                             |
+| [アプリ内メッセージ]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/about/)    | ユーザーがモバイルアプリをアクティブに使用している間に、モバイルアプリ内にメッセージを表示します。                                                                             |
 | [SMS/MMS]({{site.baseurl}}/user_guide/message_building_by_channel/sms/about_sms/)*                   | ユーザーの携帯電話にメールを送信します。                                                                                                            |
 | [WhatsApp]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/)*              | 人気のメッセージング プラットフォームであるWhatsAppを通じて、ユーザーsに手を差し伸べ、エンゲージするように伝言を送る。                                                   |
-| [コンテンツカード]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/about/)*       | ユーザー s がメッセージを受信して操作したり、バナーとしてカルーセルにメッセージを表示したりできるように、アプリまたはWeb サイト内に受信トレイを提供します。 |
-| [接続したテレビ]({{site.baseurl}}/developer_guide/platform_wide/tv_and_ott/)                           | 接続されたTV プラットフォームでユーザーS を操作します。                                                                                                   |
+| [コンテンツカード]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/about/)*       | ユーザーがメッセージを受信して操作したり、カルーセルにメッセージを表示したり、バナーとしてメッセージを表示したりできる受信トレイをアプリや Web サイト内に用意します。 |
+| [コネクテッド TV]({{site.baseurl}}/developer_guide/platform_wide/tv_and_ott/)                           | コネクテッド TV プラットフォームでユーザーと交流します。                                                                                                   |
 | [Webhook]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/understanding_webhooks/) | カスタムHTTPコールバックを使用して、外部システムとのリアルタイム通信および統合を有効にします。                                                    |
 {: .reset-td-br-1 .reset-td-br-2}
 
diff --git a/_lang/ja/_user_guide/getting_started/users_segments.md b/_lang/ja/_user_guide/getting_started/users_segments.md
index c01e76a1898..d66b1ff4a0a 100644
--- a/_lang/ja/_user_guide/getting_started/users_segments.md
+++ b/_lang/ja/_user_guide/getting_started/users_segments.md
@@ -7,7 +7,7 @@ description: "この記事では、ユーザーとセグメントの概要を示
 
 ---
 
-# はじめに: ユーザーとセグメント
+# 開始:ユーザーとセグメント
 
 パーソナライズされたターゲットを絞ったマーケティングキャンペーンを送信するためには、ユーザーを理解し、効果的なターゲティングを行うことが不可欠です。この記事では、ユーザーとセグメントの概要を示し、その意義と、オーディエンスをエンゲージするためにどのように活用するかについて概説します。
 
@@ -37,11 +37,11 @@ Braze プラットフォームの SDK は、27種類の属性とイベントを
 
 #### 標準属性
 
-標準属性は、Braze が提供する事前定義された属性です。これらは、SDKがアプリに統合された後、Brazeによって自動的に追跡される。これらは、ユーザー層やデバイスデータなど、ほとんどのアプリにとって役立つと思われる一般的なユーザー情報です。標準属性の例を次に示します。
+標準属性は、Braze が提供する事前定義された属性です。SDK がアプリに組み込まれた後、これらは Braze によって自動的に追跡されます。これらは、ユーザー層やデバイスデータなど、ほとんどのアプリにとって役立つと思われる一般的なユーザー情報です。標準属性の例を次に示します。
 
 - 名
 - 姓
-- メールアドレス
+- メール
 - 性別
 - 生年月日
 - 国
@@ -78,7 +78,7 @@ Braze プラットフォームの SDK は、27種類の属性とイベントを
 
 #### 標準イベント
 
-[標準イベントは]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/events#standard-events)、SDKがアプリやサイトに統合された後、Brazeが自動的に追跡する定義済みのイベントである。標準イベントの例をいくつか次に示します。
+[標準イベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/events#standard-events)は、SDK がアプリやサイトに統合された後に Braze が自動的に追跡する定義済みイベントです。標準イベントの例をいくつか次に示します。
 
 - **セッション開始:**このイベントは、ユーザーがアプリを開いたときにトリガーされます。
 - **セッション終了:**このイベントは、ユーザーがアプリを終了したときにトリガーされます。
diff --git a/_lang/ja/_user_guide/line.md b/_lang/ja/_user_guide/line.md
deleted file mode 100644
index 597c61af44b..00000000000
--- a/_lang/ja/_user_guide/line.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-nav_title: LINE
-article_title: LINE
-page_order: 3
-layout: dev_guide
-channel:
-  - LINE
-guide_top_header: "LINE"
-guide_top_text: "[LINE](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf) は日本で使用率が最も高いメッセージングアプリです。月間アクティブユーザー数は 9,500 万人を超えます。メッセージングに加え、LINE はソーシャルメディア、ゲーム、ショッピング、決済の「オールインワン」プラットフォームをユーザーに提供しています。<br><br>LINE アカウントを Braze と統合することで、ゼロパーティおよびファーストパーティの顧客データを活用し、顧客の嗜好、行動、クロスチャネルでのインタラクションに基づいて、適切な顧客に魅力的な LINE メッセージを送信できます。<br><br>LINE アクセスはベータ版であり、一部の Braze パッケージでのみ利用できます。利用を始めるには、アカウントマネージャーまたはカスタマーサクセスマネージャーにお問い合わせください。"
-description: "このランディングページは、LINE チャネルのホームです。ここでは、LINE の設定、LINE サブスクリプショングループ、LINE キャンペーン、LINE レポートなどに関する記事をご覧いただけます。"
-hidden: true
-permalink: /line/
-
-guide_featured_title: "LINE"
-guide_featured_list:
-- name: LINE Setup
-  link: https://www.braze.com/docs/line/line_setup/
-  image: /assets/img/braze_icons/phone-02.svg
-- name: Create a LINE Message
-  link: https://www.braze.com/docs/line/create/
-  image: /assets/img/braze_icons/table.svg
-- name: Messaging LINE Users
-  link: https://www.braze.com/docs/line/messaging_users/
-  image: /assets/img/braze_icons/message-chat-circle.svg
-- name: LINE Subscription Groups
-  link: https://www.braze.com/docs/line/subscription_groups/
-  image: /assets/img/braze_icons/table.svg
-- name: LINE Reporting
-  link: https://www.braze.com/docs/line/reporting/
-  image: /assets/img/braze_icons/bar-chart-01.svg
----
-<br><br>
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/line_setup.md b/_lang/ja/_user_guide/line_setup.md
deleted file mode 100644
index 7c1e3773a53..00000000000
--- a/_lang/ja/_user_guide/line_setup.md
+++ /dev/null
@@ -1,134 +0,0 @@
----
-nav_title: LINE の設定
-article_title: LINE の設定
-description: "この記事では、Braze の LINE チャネルを設定する方法について、前提条件や推奨される次のステップを含めて説明します。"
-page_type: partner
-search_tag: Partner
-page_order: 0
-channel:
- - LINE
-hidden: true
-permalink: /line/line_setup/
----
-
-
-# LINE の設定
-
-> この記事では、Braze で LINE チャネルを設定する方法について説明します。また、この記事は LINE ベータ版コレクションの一部です。[メインページに戻ります](https://www.braze.com/docs/line/)。
-
-{% alert important %}
-LINE アクセスはベータ版であり、一部の Braze パッケージでのみ利用できます。利用を始めるには、アカウントマネージャーまたはカスタマーサクセスマネージャーにお問い合わせください。
-{% endalert %}
-
-## 前提条件
-
-LINE と Braze を統合するには、以下が必要です。
-
-- [LINE ビジネスアカウント](https://www.linebiz.com/jp-en/manual/OfficialAccountManager/tutorial-steps/?list=7171)
-- [プレミアムアカウントまたは認証済みアカウント](https://www.infobip.com/docs/line/get-started#premium-id-line-official-account)のステータス (既存のフォロワーを同期するために必要)
-   - [LINE のアカウントガイドライン](https://terms2.line.me/official_account_guideline_oth)を見る
-- [LINE 開発者アカウント](https://developers.line.biz/en/docs/line-developers-console/login-account/)
-- [LINE メッセージング API チャネル](https://developers.line.biz/en/docs/line-developers-console/overview/#channel)
-
-## 統合
-
-### ステップ 1:LINE チャネルを Braze に接続する
-
-1. LINE の \[**メッセージング API**] タブで、\[**Webhook の設定**] を編集します。
-   - \[**Webhook URL**] を \[`https://anna.braze.com/line/events`] に設定します。
-       - これは、Braze により、ダッシュボードのクラスターに基づいて、統合時に別の URL に自動的に変更されます。
-   - \[**Webhook を使用**] と \[**Webhook の再配信**] をオンにします。<br><br> ![Webhook 設定ページでは、Webhook URL の確認や編集、\[webhook を使用]、\[Webhook の再配信]、\[エラー統計の集約]のオンとオフを切り替えることができます。][1]{: style="max-width:70%;"}
-2. \[**プロバイダー**] タブに表示される以下の情報をメモしておきます。
-
-| 情報タイプ | ロケーション |
-| --- | --- |
-| プロバイダー ID | プロバイダーを選択し、\[**設定**] > \[**基本情報**] の順に進みます。 |
-| チャネル ID | プロバイダーを選択し、\[**チャネル**] > \[チャネル] > \[**基本設定**] の順に進みます。 |
-| チャネルシークレット | プロバイダーを選択し、\[**チャネル**] > \[チャネル] > \[**基本設定**] の順に進みます。 |
-| チャネルアクセストークン | プロバイダーを選択し、\[**チャネル**] > \[チャネル] > \[**メッセージング API**] の順に進みます。チャネルアクセストークンがない場合は、\[**発行**] を選択してください。 |
-{: .reset-td-br-1 .reset-td-br-2}
-
-{: start="3"}
-3\.\[**設定**] ページ > \[**応答設定**]の順に進み、以下を実行します。
-   - \[**グリーティングメッセージ**]をオフにする。これは、Braze では、トリガーオンフォロー (trigger on follow) で処理できます。
-   - \[**自動応答メッセージ**] をオフにする。トリガーメッセージはすべて Braze 経由で送信されます。これにより、LINE コンソールから直接送信できなくなることはありません。
-   - \[**Webhook**] をオンにする。
-
-![アカウントがチャットを処理する方法を切り替えられる、応答設定ページ。][2]{: style="max-width:80%;"}
-
-### ステップ 2:Braze で LINE ページを設定する
-
-1. LINE の Braze テクノロジーパートナーページにアクセスし、LINE の \[**プロバイダー**] タブからメモした情報を入力します。
-   - プロバイダー ID
-   - チャネル ID
-   - チャネルシークレット
-   - チャネルアクセストークン
-
-![LINE 統合セクションが掲載された、LINE メッセージング統合ページ。][3]{: style="max-width:80%;"}
-
-{: start="2"}
-2\.接続後、Brazeによって、ワークスペースに正常に追加された LINE 統合ごとに Braze サブスクリプショングループが自動的に生成されます。<br><br> フォロワーリストの変更 (新しいフォロワーやフォロー解除など) は、自動的に Braze にプッシュされます。
-
-![「LINE」チャネルに 1 つのサブスクリプショングループを表示する LINE サブスクリプショングループセクション。][4]{: style="max-width:80%;"}
-
-## LINE アカウントのタイプ
-
-| アカウントタイプ | 説明 |
-| --- | --- |
-| 未認証アカウント | 未審査のアカウントで、誰でも (個人でも法人でも) 取得できます。このアカウントはグレーのバッジで表示され、LINE アプリ内の検索結果には表示されません。 |
-| 認証済みアカウント | LINE Yahoo の審査に合格したアカウント。このアカウントは青いバッジで表示され、LINE アプリ内の検索結果に表示されます。<br><br>このアカウントは、日本、台湾、タイ、インドネシアに拠点を置くアカウントでのみ利用できます。  |
-| プレミアムアカウント | LINE Yahoo の審査に合格したアカウント。このアカウントは緑色のバッジで表示され、LINE アプリ内の検索結果に表示されます。このアカウントタイプは、LINE の判断で審査時に自動的に付与されます。 |
-{: .reset-td-br-1 .resest-td-br-2}
-
-## 既存のフォロワーを Braze に同期する
-
-フォロワーを Braze に同期するには、LINE アカウントが認証済みかプレミアムである必要があります。アカウントを作成すると、デフォルトのステータスは「未認証」になります。アカウント認証を申請する必要があります。
-
-### 認証済みLINEアカウントを申請する
-
-{% alert important %}
-認証済みアカウントは、日本、台湾、タイ、インドネシアを拠点とするアカウントでのみ利用できます。
-{% endalert %}
-
-1. LINE の \[**公式アカウント**] ページで \[**設定**] を選択します。
-2. \[**情報の公開**] の \[認証ステータス]で、\[**アカウント認証をリクエスト**] を選択します。
-3. 必要な情報を入力します。
-4. 審査結果の通知を待ちます。
-
-チャネルが Braze と同期される前に特定のチャネルをフォローしていたユーザーを同期する場合は、カスタマーサクセスマネージャーまたはアカウントマネージャーに、WhatsApp チームに[リクエストを提出](https://servicedesk.braze.com/plugins/servlet/desk/portal/12)するよう依頼してください。
-
-## Braze で LINE テストユーザーを作成する
-
-ユーザーの照合を設定する前に、次の 2 種類の方法で LINE チャネルをテストできます。
-
-### LINE セグメントを参照する
-
-1. アカウント接続後、LINE チャネルをフォローします。
-
-2. Braze の \[**セグメント**] から、LINE のサブスクリプショングループのセグメントを作成します。<br><br>![サブスクリプショングループを持つフィルターグループ。][5]{: style="max-width:80%;"}<br><br>
-
-3. \[**ユーザーデータ**] > \[**ユーザーデータを CSV 形式でエクスポート**] の順に選択します。<br><br>![「LINE の配信登録済み」という名前のセグメントの \[セグメントの詳細] と、エクスポートオプションのリストが表示される \[ユーザーデータ] メニュー。][6]{: style="max-width:80%;"}<br><br>
-
-4. CSV ダウンロードで、`created_at` フィールドと LINE チャネルをフォローした日時を参照し、ユーザーを検索します。
-
-5. Braze で、Appboy ID を使用して特定のユーザーを検索し、必要に応じて修正します。
-
-### 「IDがわかる」キャンバスまたはキャンペーンを作成する
-
-1. 特定のトリガーワードでユーザーの Braze ユーザー ID を返すキャンバスを設定します。<br><br>トリガーの例 <br><br>![特定のサブスクリプショングループにインバウンド LINE を送信したユーザーにキャンペーンを送信するトリガー。][7]{: style="max-width:80%;"}<br><br>メッセージの例<br><br>![Braze ユーザー ID を記載した LINE メッセージ。][8]{: style="max-width:40%;"}<br><br>
-
-2. Braze で、Braze ID を使用して特定のユーザーを検索し、必要に応じて変更します。
-
-{% alert important %}
-キャンバスに、送信を妨げるグローバルコントロールやコントロールグループがないことを確認します。
-{% endalert %}
-
-
-[1]: {% image_buster /assets/img/line/webhook_settings.png %}
-[2]: {% image_buster /assets/img/line/response_settings.png %}
-[3]: {% image_buster /assets/img/line/integration.png %}
-[4]: {% image_buster /assets/img/line/line_subscription_groups.png %}
-[5]: {% image_buster /assets/img/line/filter_group.png %}
-[6]: {% image_buster /assets/img/line/csv_export_user_data.png %}
-[7]: {% image_buster /assets/img/line/trigger.png %}
-[8]: {% image_buster /assets/img/line/message.png %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/message_building_by_channel/content_cards/best_practices.md b/_lang/ja/_user_guide/message_building_by_channel/content_cards/best_practices.md
index 4f8435ce6fb..ca4bc641b72 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/content_cards/best_practices.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/content_cards/best_practices.md
@@ -4,7 +4,7 @@ nav_title: ベストプラクティス
 article_title: コンテンツ・カードのベストプラクティス
 layout: dev_guide
 guide_top_header: "コンテンツ・カードのベストプラクティス"
-guide_top_text: "コンテンツ・カード・メッセージを送る前に、以下の記事で知っておくべきこと、チェックすべきことを参照されたい。"
+guide_top_text: "コンテンツカードメッセージを送信する前に、以下の記事を参照し、知っておくべき情報と確認事項をチェックしてください。"
 
 page_type: landing
 description: "このランディングページには、カード送付前に知っておくべきこと、チェックすべきことを強調したベストプラクティスが掲載されている。"
diff --git a/_lang/ja/_user_guide/message_building_by_channel/content_cards/create/card_creation.md b/_lang/ja/_user_guide/message_building_by_channel/content_cards/create/card_creation.md
index 57429e12f4d..39d11679827 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/content_cards/create/card_creation.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/content_cards/create/card_creation.md
@@ -19,7 +19,7 @@ channel:
 
 {% sdk_min_versions swift:5.2.0 android:23.0.0 web:4.2.0 %}
 
-SDKをアップグレードしたら、モバイルユーザーはアプリをアップグレードしなければならない。キャンペーンまたはキャンバスのオーディエンスをフィルタリングして、[これらの最小アプリバージョンのユーザーのみをターゲットにする]({{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features/#filtering-by-most-recent-app-versions)ことができる。
+SDK をアップグレードした後、モバイルユーザーはアプリをアップグレードする必要があります。キャンペーンまたはキャンバスオーディエンスをフィルター処理して、[これらの最小アプリバージョンのユーザーのみをターゲットとする]({{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features/#filtering-by-most-recent-app-versions)ことができます。
 
 ## 概要
 
@@ -28,26 +28,26 @@ SDKをアップグレードしたら、モバイルユーザーはアプリを
 
 Brazeは、スケジュール配信で新しい[コンテンツカードキャンペーンを]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/)作成する際に、**配信**ステップでカードを作成するタイミングを選択できる。
 
-![]({% image_buster /assets/img_archive/card_creation.png %})
+![スケジュールされたコンテンツカードの配信を編集する際のコンテンツカードコントロールセクション。]({% image_buster /assets/img_archive/card_creation.png %})
 
-以下のオプションがある：
+以下のオプションがあります。
 
-- **キャンペーン発表会にて：**以前のコンテンツカードのデフォルト動作。Brazeは、キャンペーン開始時にオーディエンスの適格性とパーソナライズを計算し、その後カードを作成し、ユーザーがアプリを開くまで保存する。 
-- **第一印象で（推奨）：**ユーザーが次にアプリを開いたとき（つまり、新しい[セッションを](https://www.braze.com/resources/articles/whats-an-app-session-anyway)開始したとき）、Brazeはそのユーザーがどのコンテンツカードが適用可能かを判断し、リキッドやコネクテッドコンテンツのようなパーソナライゼーションをテンプレート化し、カードを作成する。このオプションは通常、カード配送でより良いパフォーマンスを発揮する。
+- **キャンペーン開始時:** 以前のコンテンツカードのデフォルト動作。Brazeは、キャンペーン開始時にオーディエンスの適格性とパーソナライズを計算し、その後カードを作成し、ユーザーがアプリを開くまで保存する。 
+- **ファーストインプレッション発生時 (推奨):** ユーザーが次にアプリを開いたとき（つまり、新しい[セッションを](https://www.braze.com/resources/articles/whats-an-app-session-anyway)開始したとき）、Brazeはそのユーザーがどのコンテンツカードが適用可能かを判断し、リキッドやコネクテッドコンテンツのようなパーソナライゼーションをテンプレート化し、カードを作成する。このオプションでは通常、カード配信数のパフォーマンスが向上します。
 
-選択したオプションにかかわらず、キャンペーン開始時にコンテンツカードの有効期限カウントダウンが始まる。
+選択したオプションに関係なく、キャンペーン開始時にコンテンツカードの有効期限のカウントダウンが始まります。
 
 {% endtab %}
 {% tab キャンバス %}
 
 Brazeがカードを作成するタイミングは、[コンテンツカードメッセージステップの]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/) **Messaging Channels**タブで選択できる。
 
-![]({% image_buster /assets/img_archive/card_creation_canvas.png %})
+![スケジュールされたコンテンツカードの配信を編集する際のコンテンツカードコントロールセクション。]({% image_buster /assets/img_archive/card_creation_canvas.png %})
 
-以下のオプションがある：
+以下のオプションがあります。
 
-- **ステップエントリ時:**以前のコンテンツカードのデフォルト動作。Brazeは、ユーザーがCanvasステップに入った時点で視聴資格を計算し、カードを作成して、ユーザーがアプリを開くまで保存する。
-- **第一印象で（推奨）：**Brazeは、ユーザーがCanvasステップに入った時点で視聴者資格を計算する。ユーザーが次にアプリを開く（つまり、新しい[セッションを](https://www.braze.com/resources/articles/whats-an-app-session-anyway)開始する）と、BrazeはLiquidやConnected Contentのようなパーソナライズをテンプレート化し、カードを作成する。このオプションでは、カード配送のパフォーマンスが向上し、より最新のパーソナライズが可能になる。
+- **ステップエントリ時:**以前のコンテンツカードのデフォルト動作。Braze は、ユーザーがキャンバスステップに入った時点でオーディエンスの適格性を計算し、その後カードを作成して、ユーザーがアプリを開くまで保存します。
+- **最初のインプレッション発生時 (推奨):** Braze は、ユーザーがキャンバスステップに入った時点でオーディエンスの適格性を計算します。ユーザーが次にアプリを開く（つまり、新しい[セッションを](https://www.braze.com/resources/articles/whats-an-app-session-anyway)開始する）と、BrazeはLiquidやConnected Contentのようなパーソナライズをテンプレート化し、カードを作成する。このオプションでは、カード配信数のパフォーマンスが向上し、より最新のパーソナライゼーションが可能になります。
 
 選択したオプションにかかわらず、コンテンツカードの有効期限のカウントダウンは、ユーザーがキャンバスのステップに入ったときに開始される。
 
@@ -55,7 +55,7 @@ Brazeがカードを作成するタイミングは、[コンテンツカード
 {% endtabs %}
 
 {% alert note %}
-どちらのオプションでも、カード作成後、Brazeは視聴資格やパーソナライズを再計算しない。
+どちらのオプションでも、カードの作成後、Braze はオーディエンスの適格性やパーソナライゼーションを再計算しません。
 {% endalert %}
 
 ### ローンチ時やエントリー時と第一印象時のカード作成の違い
@@ -72,7 +72,7 @@ Brazeがカードを作成するタイミングは、[コンテンツカード
 <thead>
   <tr>
     <th class="tg-0pky"></th>
-    <th class="tg-0pky">キャンペーン開始時／キャンバスステップエントリー時</th>
+    <th class="tg-0pky">キャンペーン開始時/キャンバスステップのエントリ時</th>
     <th class="tg-0pky">第一印象</th>
   </tr>
 </thead>
@@ -84,44 +84,44 @@ Brazeがカードを作成するタイミングは、[コンテンツカード
   </tr>
   <tr>
     <td class="leftHeader">オーディエンス</td>
-    <td class="tg-0pky">Brazeは、キャンペーン送信時にオーディエンスのメンバーシップを評価する。<br><br>新規または匿名のユーザーが、キャンペーン送信後にカードを閲覧しようとしても、適格性は評価されない。定期的なキャンペーンの場合、これは次回の更新間隔となる。</td>
-    <td class="tg-0pky">Brazeは、ユーザーが次にアプリを開く（セッションを開始する、<a href="#campaign_note">キャンペーンのみ*）</a>ときにメンバーシップを評価する。<br><br> この設定は、新規ユーザーや匿名ユーザーがカードを閲覧しようとする際に、常に適格性が評価されるため、より多くのオーディエンスにリーチすることができる。また、ファーストインプレッション<a href="#campaign_note">（キャンペーンのみ*）に</a>設定した場合、レート制限（キャンペーンを受け取る人数を制限すること）は適用されない。</td>
+    <td class="tg-0pky">Brazeは、キャンペーン送信時にオーディエンスのメンバーシップを評価する。<br><br>新規または匿名のユーザーが、キャンペーン送信後にカードを閲覧しようとしても、適格性は評価されない。定期的なキャンペーンの場合、これは次回の繰り返し間隔となります。</td>
+    <td class="tg-0pky">Brazeは、ユーザーが次にアプリを開く（セッションを開始する、<a href="#campaign_note">キャンペーンのみ*）</a>ときにメンバーシップを評価する。<br><br> この設定は、新規ユーザーや匿名ユーザーがカードを閲覧しようとする際に、常に適格性が評価されるため、より多くのオーディエンスにリーチすることができる。さらに、レート制限 (キャンペーンを受け取る人数の制限) は、ファーストインプレッション(<a href="#campaign_note">キャンペーンのみ</a>) に設定されている場合は適用されません。</td>
   </tr>
   <tr>
     <td class="leftHeader">パーソナライゼーション</td>
-    <td class="tg-0pky">Brazeは、リキッド、コネクテッドコンテンツ、コンテンツブロックを、キャンペーン開始時またはユーザーがキャンバスステップに入った時点で評価する。定期的なキャンペーンの場合、これは次回の更新間隔となる。</td>
-    <td class="tg-0pky">Brazeは、リキッド、コネクテッド・コンテンツ、コンテンツ・ブロックを、最初のインプレッション時、または次の再発間隔後に評価する。</td>
+    <td class="tg-0pky">Brazeは、リキッド、コネクテッドコンテンツ、コンテンツブロックを、キャンペーン開始時またはユーザーがキャンバスステップに入った時点で評価する。定期的なキャンペーンの場合、これは次回の繰り返し間隔となります。</td>
+    <td class="tg-0pky">Braze は、Liquid、コネクテッドコンテンツ、コンテンツブロックを、ファーストインプレッション時、または次の繰り返し間隔後に評価します。</td>
   </tr>
   <tr>
     <td class="leftHeader">分析</td>
-    <td class="tg-0pky"><em>Messages Sentは</em>、作成され、閲覧可能なカードの数を指す。ユーザーがカードを見たかどうかはカウントされない。</td>
-    <td class="tg-0pky"><em>Messages Sentは</em>、ユーザーに表示されたカードの数を指す。<br><br>リーチ可能なユーザーとインプレッションは変わらないが、ファーストインプレッションでカードを作成した場合、キャンペーン開始時やキャンバスステップエントリー時に同じカードを作成した場合と比べて、送信量<em>（メッセージ送信</em>数）が減少することが予想される。</td>
+    <td class="tg-0pky"><em>送信済みメッセージ</em>は、作成済みで表示が可能なカードの数を示します。ユーザーがカードを見たかどうかはカウントされない。</td>
+    <td class="tg-0pky"><em>送信済みメッセージ</em>は、ユーザーに表示されたカードの数を示します。<br><br>リーチ可能なユーザーとインプレッションは変わらないが、ファーストインプレッションでカードを作成した場合、キャンペーン開始時やキャンバスステップエントリー時に同じカードを作成した場合と比べて、送信量<em>（メッセージ送信</em>数）が減少することが予想される。</td>
   </tr>
   <tr>
     <td class="leftHeader">処理時間</td>
-    <td class="tg-0pky">カードは、立ち上げ時にセグメント内の対象ユーザー全員に作成される。大人数の観客には、発売後すぐにカードが入手できる<b>At First Impressionを</b>選択することをお勧めする。</td>
-    <td class="tg-0pky">カードは、ユーザーが最初に表示しようとしたときに作成されるため、ファーストインプレッションで表示されるまで1～2秒かかることがある。</td>
+    <td class="tg-0pky">カードは、開始時にセグメント内の適格ユーザーごとに作成されます。大規模なオーディエンスの場合は、開始後に短時間でカードが利用可能になるため、[<b>ファーストインプレッション</b>] を選択することをお勧めします。</td>
+    <td class="tg-0pky">カードはユーザーが表示しようとしたときに初めて作成されるため、ファーストインプレッションで表示されるまで 1 ～ 2 秒かかることがあります。</td>
   </tr>
 </tbody>
 </table>
 
-<p id="campaign_note"><sup>* キャンバスのオーディエンスは、ステップレベルではなく、キャンバスのエントリーで評価されるため、このシナリオはキャンペーンにのみ適用される。</sup></p>
+<p id="campaign_note"><sup>* キャンバスオーディエンスはステップではなくキャンバスエントリで評価されるため、このシナリオはキャンペーンのみに該当します。</sup></p>
 
 ## 考慮事項
 
 ### ローンチ後にカード作成を変更する
 
-Brazeは、キャンペーン開始後にカードの作成方法を変更しないことを推奨している。2つのカード作成タイプで送信メッセージの計算方法が異なるため、キャンペーン開始後にカードの作成方法を変更すると、送信ボリュームの精度に影響する可能性がある。
+Brazeは、キャンペーン開始後にカードの作成方法を変更しないことを推奨している。2 つのカード作成タイプでは送信メッセージの計算方法が異なるため、キャンペーン開始後にカードの作成方法を変更すると、送信ボリュームの精度に影響する可能性があります。
 
 ### 潜在的な処理時間
 
 キャンペーン開始後、より早くカードが利用できるようになるため、オーディエンス数が多いキャンペーンでは、ファーストインプレッションでカードを作成するオプションを選択することをお勧めする。セッション開始時にトリガーされるキャンペーンも、パフォーマンス向上を実現するために、ファーストインプレッション時にカードを作成する（スケジュール配信で利用可能）ように移行することを検討するとよいだろう。
 
-第一印象でカードを作成した場合、カードの処理に1～2秒かかることがある。この処理時間の長さは、カードサイズやメッセージテンプレートのオプションの複雑さなど、様々な要因に依存する。例えば、コネクテッド・コンテンツを使用するカードの処理時間は、少なくともコネクテッド・コンテンツのレスポンス・タイムと同じくらいかかる。
+第一印象でカードを作成した場合、カードの処理に1～2秒かかることがある。この処理時間の長さは、カードサイズやメッセージテンプレートのオプションの複雑さなど、様々な要因に依存する。例えば、コネクテッドコンテンツを使用するカードの処理時間は、少なくともコネクテッドコンテンツの応答時間と同じくらいかかります。
 
 ### 以前のSDKバージョン
 
-ユーザーのアプリが以前のバージョンのSDKを実行している場合でも、指定されたカード作成で送信されたコンテンツ・カードを受け取ることができる。ただし、これらのユーザーにはカードが表示されるまでに時間がかかり、次回のコンテンツカード同期まで表示されないこともある。
+ユーザーのアプリが以前のバージョンの SDK を実行している場合でも、指定されたカード作成で送信されたコンテンツカードを受信します。ただし、これらのユーザーにはカードが表示されるまでに時間がかかり、次回のコンテンツカード同期まで表示されないこともある。
 
 [1]: {% image_buster /assets/img_archive/card_creation.png %}
 [2]: {{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/
diff --git a/_lang/ja/_user_guide/message_building_by_channel/content_cards/creative_details.md b/_lang/ja/_user_guide/message_building_by_channel/content_cards/creative_details.md
index 5c4df274dc9..f6097b07570 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/content_cards/creative_details.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/content_cards/creative_details.md
@@ -11,23 +11,23 @@ tool: Media
 
 # コンテンツ・カードのクリエイティブ詳細
 
-> コンテンツカードとそのフィードのカスタマイズは、キャンペーン作成中に行うことはできない。技術的な詳細については、\[開発者向けドキュメント]][7] を参照のこと。
+> キャンペーンの作成プロセス中に、コンテンツカードとそれらが配置されるフィードをカスタマイズすることはできません。カードの作成とカスタマイズを行うには、エンジニアおよび開発者との共同作業が必要です。技術的な詳細については、\[開発者向けドキュメント][7] を参照してください。
 
-## コンテンツ・カードの種類
+## コンテンツカードのタイプ
 
 {% tabs %}
 {% tab クラシック %}
 
-クラシックカードは、標準的なメッセージや通知、あるいはアイコンでメッセージを視覚的に分類するのに最適だ。画像は任意だが、1:1の比率でなければならない。  
+クラシックカードは、標準的なメッセージングや通知、あるいはアイコンを使ってメッセージを視覚的に分類するのに適しています。画像は任意だが、1:1の比率でなければならない。  
 
-![おすすめ詳細とクラシックカードのイメージ例]({% image_buster /assets/img/content_card_classic.png %}){: style="max-width:45%;border:0;"}
+![推奨されるディテールとクラシックカードのサンプルを持つ、クラシックなカードの画像]({% image_buster /assets/img/content_card_classic.png %}){: style="max-width:45%;border:0;"}
 
 | カード機能 | 詳細 |
 | --- | ---|
-| ヘッダーテキスト | 18px; 太字 <br> テキストは1行が理想的だ。<br> ここでリキッドを使ってメッセージをパーソナライズすることもできる。 |
-| メッセージ | 13px; レギュラーウェイト <br> 2行から4行のテキストが理想的だ。<br> ここでリキッドを使ってメッセージをパーソナライズすることもできる。 |
-| リンクテキスト | オプションだ。<br> 13 px <br> ウェブページへのリンク、またはアプリ内へのディープリンク。 |
-| イメージ | オプションだ。<br> 1対1の比率でなければならない。<br> 画質は60×60pxを推奨する。 |
+| ヘッダーテキスト | 18px; 太字 <br> テキストは1行が理想的だ。<br> ここで Liquid を使ってメッセージをパーソナライズできます。 |
+| メッセージテキスト | 13px; 標準の太さ <br> 2行から4行のテキストが理想的だ。<br> ここで Liquid を使ってメッセージをパーソナライズできます。 |
+| リンクテキスト | オプション。<br> 13 px <br> ウェブページへのリンク、またはアプリ内へのディープリンク。 |
+| 画像 | オプション。<br> 1 対 1 の比率でなければなりません。<br> 画質は60×60pxを推奨する。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 {% endtab %}
@@ -35,27 +35,27 @@ tool: Media
 
 キャプション付き画像カードは、ビッグセールやアプリの新機能など、重要なコンテンツをアピールし、注目を集めるのに最適な方法だ。
 
-![推奨詳細とキャプション付きイメージカードの例]({% image_buster /assets/img/content_card_captioned.png %}){: style="max-width:90%;border:0;"}
+![推奨されるディテールとキャプション付き画像カードのサンプルを持つ、キャプション付き画像カードの画像]({% image_buster /assets/img/content_card_captioned.png %}){: style="max-width:90%;border:0;"}
 
 | カード機能 | 詳細 |
 | --- | ---|
-| ヘッダーテキスト | 18px; 太字 <br> テキストは1行が理想的だ。<br> ここでリキッドを使ってメッセージをパーソナライズすることもできる。 |
-| メッセージ | 13px; レギュラーウェイト <br> 2行から4行のテキストが理想的だ。<br> ここでリキッドを使ってメッセージをパーソナライズすることもできる。 |
-| リンクテキスト | オプションだ。<br> 13 px <br> ウェブページへのリンク、またはアプリ内へのディープリンク。 |
-| イメージ | 4：3の比率を推奨する。<br> 最小幅600px。 <br> 高解像度のPNG、JPEG、GIFをサポートする。 |
+| ヘッダーテキスト | 18px; 太字 <br> テキストは1行が理想的だ。<br> ここで Liquid を使ってメッセージをパーソナライズできます。 |
+| メッセージテキスト | 13px; 標準の太さ <br> 2行から4行のテキストが理想的だ。<br> ここで Liquid を使ってメッセージをパーソナライズできます。 |
+| リンクテキスト | オプション。<br> 13 px <br> ウェブページへのリンク、またはアプリ内へのディープリンク。 |
+| 画像 | 4:3 の比率を推奨。<br> 最小幅 600 px。 <br> 高解像度のPNG、JPEG、GIFをサポートする。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endtab %}
 {% tab バナー %}
 
-派手さを求めるなら、バナーカードが向いている。これはあなたが望むものに完全にカスタマイズされる。別の場所でコンテンツを作成し、それをアップロードするだけで、あなただけの美しいカードが完成する。
+趣向を凝らした演出にはバナーカードが向いています。これは必要に応じて完全にカスタマイズすることができます。別の場所でコンテンツを作成し、それをアップロードするだけで、あなただけの美しいカードが完成する。
 
-![推奨詳細とバナー例の画像]({% image_buster /assets/img/content_card_banner.png %}){: style="max-width:45%;border:0;"}
+![推奨される詳細とバナーのサンプルを持つ、バナーの画像]({% image_buster /assets/img/content_card_banner.png %}){: style="max-width:45%;border:0;"}
 
 | カード機能 | 詳細 |
 | --- | ---|
-| リンクカード | オプションだ。<br> 13 px <br> オンクリックビヘイビアは、ウェブページまたはアプリ内へのディープリンクにリンクする。 |
-| イメージ | あらゆるアスペクト比に対応する。<br> 最小幅600px。 <br> 高解像度のPNG、JPEG、GIFをサポートする。 |
+| リンク付きカード | オプション。<br> 13 px <br> Web ページまたはアプリ内のディープリンクへの、クリック時動作リンク。 |
+| 画像 | あらゆるアスペクト比に対応しています。<br> 最小幅 600 px。 <br> 高解像度のPNG、JPEG、GIFをサポートする。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endtab %}
@@ -63,11 +63,11 @@ tool: Media
 
 ## グローバル・クリエイティブの詳細 {#general}
 
-コンテンツ・カードは最初から優れた機能を備えている。現時点では、カードのスタイリングはBrazeアカウントでネイティブに行うことはできないが、統合時にタイプやコンテンツカードフィードによってコンテンツカードをスタイリングすることができる。詳しくは\[コンテンツカードのカスタマイズ][4] ]を参照のこと。
+コンテンツカードは、最初から素晴らしい機能を備えています。現時点では、カードのスタイリングを Braze アカウントでネイティブに行うことはできませんが、統合時にタイプやコンテンツカードフィードによってコンテンツカードをスタイリングすることができます。詳しくは、\[コンテンツカードのカスタマイズ][4]] を参照してください。
 
-### 解雇行動
+### 破棄の動作
 
-ユーザーがカードを退会するには、モバイルでスワイプするか、次のスクリーンショットのように`close X` 。Web SDKのみ、カーソルを合わせると`x` が表示される。
+ユーザーがカードを破棄するには、次のスクリーンショットのようにモバイルでスワイプするか、`close X` 機能を使用します。Web SDK のみ、カーソルを合わせると `x` が表示されます。
 
 ![カードのスワイプまたはクローズ解除の動作を示す画像][5]
 
@@ -76,14 +76,14 @@ tool: Media
 ![空のコンテンツ・カード・フィードのイメージ][6]{: style="max-width:45%"}
 
 {% alert tip %}
-コンテンツカードは、ユーザーが関連するアクションを起こしたときに解除されるように設定することで、関連性を保つことができる。例えば、プロモーション用のコンテンツカードは、ユーザーが購入するとすぐに破棄されるように設定し、すでに購入した商品のオファーが表示され続けないようにする。
+コンテンツカードの関連性を維持できるよう、ユーザーが関連するアクションを起こしたときに破棄されるように設定します。例えば、プロモーション用のコンテンツカードは、ユーザーが購入するとすぐに破棄されるように設定し、すでに購入した商品のオファーが表示され続けないようにします。
 {% endalert %}
 
 ### コンテンツ・カードでGIFを使う
 
 | Android用コンテンツカード | iOS用コンテンツカード | ウェブ用コンテンツカード |
 | --- | --- |---|
-| Android SDKは、デフォルトではアニメーションGIFをサポートしていない。GIFサポートの有効化の詳細については、[GIFを]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/GIFs/)参照のこと。 | Swift SDK では、アニメーション GIF がデフォルトではサポートされていません。GIFサポートの有効化の詳細については、[GIFサポートチュートリアルを](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/c3-gif-support)参照のこと。 | GIFのサポートは、Web SDK統合にデフォルトで含まれている。 |
+| Android SDK は、デフォルトではアニメーション GIF をサポートしていません。GIF サポートの有効化の詳細については、[GIF]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/GIFs/) を参照してください。 | Swift SDK では、アニメーション GIF がデフォルトではサポートされていません。GIF サポートの有効化の詳細については、[GIF サポートのチュートリアル](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/c3-gif-support)を参照してください。 | GIF のサポートは、Web SDK 統合にデフォルトで含まれています。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 <br><br>
diff --git a/_lang/ja/_user_guide/message_building_by_channel/content_cards/reporting.md b/_lang/ja/_user_guide/message_building_by_channel/content_cards/reporting.md
index 7abf8add6ef..a7e43b70e9a 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/content_cards/reporting.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/content_cards/reporting.md
@@ -2,7 +2,7 @@
 nav_title: レポート
 article_title: コンテンツ・カードのレポート
 page_order: 4
-description: "この参考記事では、Brazeダッシュボードで提供されるさまざまなContent Cardレポートメトリクスと分析オプションの概要を説明する。"
+description: "この記事では、Braze ダッシュボードで提供されるさまざまなコンテンツカードレポートの指標と分析オプションの概要を説明します。"
 channel:
   - content cards
 tool:
@@ -12,6 +12,6 @@ tool:
 
 # コンテンツ・カードのレポート
 
-> この参考記事では、Brazeダッシュボードで提供されるさまざまなContent Cardレポートメトリクスと分析オプションの概要を説明する。
+> この記事では、Braze ダッシュボードで提供されるさまざまなコンテンツカードレポートの指標と分析オプションの概要を説明します。
 
 {% multi_lang_include campaign_analytics.md channel="Content Card" %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/about.md b/_lang/ja/_user_guide/message_building_by_channel/email/about.md
index b23e34ba8bc..caeb6d24e4f 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/about.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/about.md
@@ -8,15 +8,15 @@ channel:
 
 ---
 
-# [![Brazeラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/messaging-channels-email){: style="float:right;width:120px;border:0;" class="noimgborder"} メールについて
+# [![Braze ラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/messaging-channels-email){: style="float:right;width:120px;border:0;" class="noimgborder"} メールについて
 
-> Eメールのメッセージでできることはたくさんある！Eメールメッセージは、リッチコンテンツをユーザーに届けるのに最適な方法だ。Eメール・メッセージングには、アプリやウェブサイトの外でユーザーとコミュニケーションするための無限の柔軟性がある。閲覧者の管理から目を引くマルチメディアコンテンツの挿入まで、Eメールメッセージをカスタマイズしよう。Eメールキャンペーンの事例をご覧になりたい方は、[ケーススタディを][6]ご覧ください。
+> Eメールのメッセージでできることはたくさんある！Eメールメッセージは、リッチコンテンツをユーザーに届けるのに最適な方法だ。メールメッセージングは、アプリや Web サイトの外でユーザーとコミュニケーションを図るための無限の柔軟性を提供します。閲覧者の管理から目を引くマルチメディアコンテンツの挿入まで、Eメールメッセージをカスタマイズしよう。Eメールキャンペーンの事例をご覧になりたい方は、[ケーススタディを][6]ご覧ください。
 
 ## メールをカスタマイズする
 
 メールメッセージは、以下のようなさまざまな方法でカスタマイズできる：
 
-- [Eメールテンプレート][2]
+- [Braze メールテンプレート][2]
 - [カスタムHTMLテンプレート][7]
 - [ドラッグ＆ドロップ・エディター用ブロック][4]
 - [ユーザーサブスクリプション][5]
@@ -27,11 +27,11 @@ channel:
 
 | ユースケース | 説明 |
 | --- | --- |
-| 再エンゲージメント | アプリをインストールしていないユーザーを含め、アプリ外のユーザーにリーチする。 |
-| オンボーディング | 新規ユーザーを取り込み、プッシュ通知をオンにしたり、ソーシャルネットワークでアプリを共有するよう促す。 |
+| 再エンゲージメント | アプリをまだインストールしていないユーザーを含め、アプリ外のユーザーにリーチします。 |
+| オンボーディング | オンボーディングでは、新しいユーザーにプッシュ通知の有効化やソーシャルネットワーク上でのアプリ共有を促します。 |
 | リッチなメッセージ | リッチでダイナミックなHTMLメッセージを可能にする。 |
 | マルチメディア・コンテンツ | ビデオや画像など、ユーザーを惹きつけるマルチメディア・コンテンツの配置のしやすさ。 |
-| ニュースレター | ユーザーのエンゲージメントを維持するために、毎月または毎週ニュースレターを送ることができる。 |
+| ニュースレター | ユーザーエンゲージメントを維持するために、月刊や週刊のニュースレターを簡単に送信できます。 |
 | トランザクション | 最近購入した商品をユーザーに通知し、重要な商品情報や配送情報を[トランザクションメールで][3]配信する。
 {: .reset-td-br-1 .reset-td-br-2}
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/amphtml.md b/_lang/ja/_user_guide/message_building_by_channel/email/amphtml.md
index 58b8a957032..55783255bf2 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/amphtml.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/amphtml.md
@@ -3,15 +3,15 @@ nav_title: メール用AMP
 article_title: メール用AMP
 alias: /amphtml/
 page_order: 11
-description: "このリファレンス記事は、メール用AMPの概要と一般的な使用例を提供します。"
+description: "この記事では、メール用 AMP と一般的なユースケースの概要について説明します。"
 channel:
   - email
 
 ---
 
-# メールのためのAMP
+# メール用 AMP
 
-> メール用[AMP<1>}を使用すると、メールにインタラクティブな要素を追加し、顧客とのコミュニケーションを向上させ、ユーザーの受信トレイに直接完全な体験を提供できます。AMPは、アンケート、フィードバック質問票、投票キャンペーン、レビュー、サブスクリプションセンターなどのエキサイティングなメール提供を構築するのに役立つさまざまなコンポーネントを使用することで、これを可能にします。このようなツールは、エンゲージメント向上とリテンションの機会を提供することができます。
+> メール用[AMP](https://amp.dev/about/email)を使用すると、メールにインタラクティブな要素を追加し、顧客とのコミュニケーションを向上させ、ユーザーの受信トレイに直接完全な体験を提供できます。AMP は、アンケート、フィードバック質問票、投票キャンペーン、レビュー、サブスクリプションセンターなど、エキサイティングなメールオファリングの作成に役立つさまざまなコンポーネントを使用することで、これを可能にします。このようなツールは、エンゲージメント向上とリテンションの機会を提供することができます。
 
 ## 要件
 
@@ -19,21 +19,21 @@ Brazeは、Googleで登録するユーザーや必要なセキュリティ要件
 
 | 要件   | 説明 |
 | --------------| ----------- |
-| AMPがメールでオンになりました | AMPは誰でも利用できます。この機能を有効にしたい場合は、アカウントマネージャーに連絡してください。 |
-| Gmailアカウントイネーブルメント | [Gmailアカウントの有効化](#enabling-gmail-account)を参照してください。 |
-| Google送信者認証 | Gmail [は送信者を認証します](https://developers.google.com/gmail/ampemail/security-requirements#sender_authentication) AMPメールのDKIM、SPF、およびDMARCを使用します。これらはあなたのアカウントに設定する必要があります。<br><br>[ドメインキー識別メール](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) (DKIM) <br>[送信者ポリシーフレームワーク](https://en.wikipedia.org/wiki/Sender_Policy_Framework)(SPF)<br>[ドメインベースのメッセージ認証、報告、および適合](https://en.wikipedia.org/wiki/DMARC)(DMARC)
-| AMP メール要素 | 説得力のあるAMPメールには、さまざまなコンポーネントの戦略的な使用が含まれます。以下の[コンポーネント](#components)セクションの必須タブを参照してください。 |
+| メール用 AMP がオンになっている | AMPは誰でも利用できます。この機能を有効にしたい場合は、アカウントマネージャーに連絡してください。 |
+| Gmail アカウントの有効化 | [Gmailアカウントの有効化](#enabling-gmail-account)を参照してください。 |
+| Google送信者認証 | Gmail は DKIM、SPF、および DMARC を使用して AMP メールの[送信者を認証](https://developers.google.com/gmail/ampemail/security-requirements#sender_authentication)します。お客様のアカウントにこれらが設定されている必要があります。<br><br>- [ドメインキー識別メール](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) (DKIM) <br>- [送信者ポリシーフレームワーク](https://en.wikipedia.org/wiki/Sender_Policy_Framework) (SPF)<br>- [ドメインベースのメッセージ認証、レポート、および準拠](https://en.wikipedia.org/wiki/DMARC) (DMARC)
+| AMP メール要素 | 説得力のある AMP メールでは、さまざまなコンポーネントが戦略的に使用されます。以下の[コンポーネント](#components)セクションの必須タブを参照してください。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ### サポートされているクライアント
 
-ユーザーにAMPメールを送信する前に、クライアントに登録する必要があります。登録プロセスには、承認を得るためにテストAMP HTMLメールを送信することが含まれます。承認時間はクライアントごとに異なります。詳細については、登録リンクに従ってください。
+ユーザーにAMPメールを送信する前に、クライアントに登録する必要があります。登録プロセスには、承認を得るためにテストAMP HTMLメールを送信することが含まれます。承認の所要時間はクライアントごとに異なります。詳細については、登録リンクに従ってください。
 
 | クライアント | 登録リンク |
 | ------ | -------- |
-| Gmail | [グーグル](https://developers.google.com/gmail/ampemail/register) |
-| フェアメール | [フェアメール](https://email.faircode.eu/) |
-| ヤフー | [ヤフー](https://senders.yahooinc.com/amp/) |
+| Gmail | [Google](https://developers.google.com/gmail/ampemail/register) |
+| FairEmail | [FairEmail](https://email.faircode.eu/) |
+| ヤフー | [Yahoo](https://senders.yahooinc.com/amp/) |
 | Mail.ru | [Mail.ru](https://postmaster.mail.ru/amp/) |
 
 サポートされているプラットフォームの完全なリストについては、[AMPドキュメント](https://amp.dev/support/faq/email-support)を参照してください。 
@@ -48,7 +48,7 @@ Gmailの設定に移動し、**ダイナミックなメールを有効にする*
 
 また、APIを使用してメールにAMPを使用することもできます。Brazeの[メッセージングエンドポイント]({{site.baseurl}}/api/endpoints/messaging/)を使用してメールを送信する場合は、以下に示すように`amp_body`をオブジェクト仕様として追加します。
 
-### メール object specification
+### メールオブジェクトの指定
 
 ```json
 {
@@ -69,11 +69,11 @@ Gmailの設定に移動し、**ダイナミックなメールを有効にする*
 }
 ```
 
-## AMPメールを作成する
+## AMP メールの作成
 
-まず、[コンポーネント](#components)を使用してAMPメールを作成します。次に、[Braze API](#api-usage)を使用してメッセージを送信し、AMP `amp_body` HTMLを含めるようにしてください。
+まず、[コンポーネント](#components)を使用して AMP メールを作成します。次に、[Braze API](#api-usage) を使用してメッセージを送信します。AMP HTML の `amp_body` を必ず含めてください。
 
-AMP HTML に加えて、通常の HTML `body` バージョンが必要であり、AMP メールの `plaintext_body` バージョンを提案します。すべてのAMPメールはマルチパートで送信されます。つまり、BrazeはHTML、プレーンテキスト、およびAMP HTMLをサポートするメールを送信します。これは、メールがAMP for emailをまだサポートしていないプロバイダー経由で送信された場合に役立ちます。なぜなら、メールはユーザーとそのデバイスに基づいて適切なバージョンに自動的にデフォルトするからです。
+AMP HTML に加えて、通常の HTML `body` バージョンが必要です。AMP メールの `plaintext_body` バージョンをお勧めします。すべてのAMPメールはマルチパートで送信されます。つまり、BrazeはHTML、プレーンテキスト、およびAMP HTMLをサポートするメールを送信します。これは、メール用 AMP をまだサポートしていないプロバイダー経由でメールが送信された場合に役立ちます。なぜなら、メールはユーザーとそのデバイスに基づいて適切なバージョンに自動的にデフォルト設定されるからです。
 
 {% alert note %}
 AMPメールを作成する際には、AMPコードをHTMLエディタに追加しないように、AMPエディタにいることを確認してください。
@@ -81,26 +81,26 @@ AMPメールを作成する際には、AMPコードをHTMLエディタに追加
 
 これらの追加リソースを参照してください:
 
-- [AMPチュートリアル](https://amp.dev/documentation/guides-and-tutorials/start/create_email?format=email)
+- [AMP チュートリアル](https://amp.dev/documentation/guides-and-tutorials/start/create_email?format=email)
 - [サンプルコード](https://gist.github.com/CrystalOnScript/988c3f0a2eb406da27e9d9bf13a8bf73)が最終製品の見た目を確認するためのものです。 
-- [AMP メール components ライブラリー](https://amp.dev/documentation/components/?format=email/)
+- [AMP メールコンポーネントライブラリ](https://amp.dev/documentation/components/?format=email/)
 
 ### コンポーネント
 
 {% tabs %}
-  {% tab 必需品 %}
+  {% tab 必要なもの %}
 
-これらはAMP HTML email...AMPを作るものです！これらの要素はすべて、AMPメールの本文に必要です。
+これらによって AMP HTML を email...AMP 対応にします。これらの要素はすべて、AMPメールの本文に必要です。
 
 | コンポーネント | 説明 | 例 |
 |---------|--------------|---------|
-| 識別 <br><br> `⚡4email` または `amp4email`| AMP HTML メールとしてメールを識別します。 | `<!doctype html>`<br> `<html ⚡4email>`<br> `<head>` |
-| 読み込む AMP ランタイム <br><br> `<script>` | JavaScriptを使用して、AMPがメール内で機能するようにします。 | `<script async src="https://cdn.ampproject.org/v0.js"></script>`|
-| CSSボイラープレート | AMPが読み込まれるまでコンテンツを非表示にします。<br> AMP メールをサポートするメールプロバイダーは、クライアントで審査済みの AMP スクリプトのみが実行されるようにするセキュリティチェックを実施します。 | `<style amp4email-boilerplate>body{visibility:hidden}</style>` |
+| 識別 <br><br> `⚡4email` または `amp4email`| メールを AMP HTML メールとして識別します。 | `<!doctype html>`<br> `<html ⚡4email>`<br> `<head>` |
+| 読み込む AMP ランタイム <br><br> `<script>` | JavaScript を使用して、AMP がメール内で機能するようにします。 | `<script async src="https://cdn.ampproject.org/v0.js"></script>`|
+| CSSボイラープレート | AMPが読み込まれるまでコンテンツを非表示にします。<br> AMP メールをサポートするメールプロバイダーは、クライアントで審査済みの AMP スクリプトのみが実行されるように、セキュリティチェックを実施します。 | `<style amp4email-boilerplate>body{visibility:hidden}</style>` |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
   {% endtab %}
-  {% tab ダイナミックな %}
+  {% tab ダイナミック %}
 
 これらのコンポーネントを使用して、メールにダイナミックなレイアウトと動作を作成します。
 
@@ -111,12 +111,12 @@ AMPメールを作成する際には、AMPコードをHTMLエディタに追加
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 {% alert note %}
-ユーザーを認証する必要があるコンポーネントは、[Googleアクセス トークン](https://developers.google.com/gmail/ampemail/authenticating-requests#access_tokens)または[プロキシ アサーション トークン](https://developers.google.com/gmail/ampemail/authenticating-requests#proxy_assertion_tokens)を使用する必要があります。
+ユーザーの認証を必要とするコンポーネントは、[Google アクセス トークン](https://developers.google.com/gmail/ampemail/authenticating-requests#access_tokens)または[プロキシアサーショントークン](https://developers.google.com/gmail/ampemail/authenticating-requests#proxy_assertion_tokens)を使用する必要があります。
 {% endalert %}
   {% endtab %}
   {% tab クリエイティブ %}
 
-  AMP のコンポーネントを使用して、メールをオーディエンスに合わせてカスタマイズしましょう。
+  お客様のメールをオーディエンスに届けるのに役立つ AMP のクリエイティブなコンポーネントの使用をお勧めします。
 
 | コンポーネント | 説明 | 必須スクリプト |
 |---------|--------------|---------|
@@ -126,57 +126,57 @@ AMPメールを作成する際には、AMPコードをHTMLエディタに追加
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 {% alert note %}
-ユーザーを認証する必要があるコンポーネントは、[Googleアクセス トークン](https://developers.google.com/gmail/ampemail/authenticating-requests#access_tokens)または[プロキシ アサーション トークン](https://developers.google.com/gmail/ampemail/authenticating-requests#proxy_assertion_tokens)を使用する必要があります。
+ユーザーの認証を必要とするコンポーネントは、[Google アクセス トークン](https://developers.google.com/gmail/ampemail/authenticating-requests#access_tokens)または[プロキシアサーショントークン](https://developers.google.com/gmail/ampemail/authenticating-requests#proxy_assertion_tokens)を使用する必要があります。
 {% endalert %}
 
   {% endtab %}
-  {% tab 他の %}
+  {% tab その他 %}
 
 | コンポーネント | 説明 |
 |---------|--------------|
-| [データバインディングと式](https://amp.dev/documentation/components/amp-anim?format=email)<br><br> `amp-bind`| データバインディングとJavaScriptのような式を介して、AMPページにカスタムのステートフルなインタラクティビティを追加します。 |
+| [データバインディングと式](https://amp.dev/documentation/components/amp-anim?format=email)<br><br> `amp-bind`| データバインディングと JavaScript 風の式を介して、AMP ページにカスタムのステートフルなインタラクティビティを追加します。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
-ユーザーを認証する必要があるコンポーネントは、[Googleアクセス トークン](https://developers.google.com/gmail/ampemail/authenticating-requests#access_tokens)または[プロキシ アサーション トークン](https://developers.google.com/gmail/ampemail/authenticating-requests#proxy_assertion_tokens)を使用する必要があります。
+ユーザーの認証を必要とするコンポーネントは、[Google アクセス トークン](https://developers.google.com/gmail/ampemail/authenticating-requests#access_tokens)または[プロキシアサーショントークン](https://developers.google.com/gmail/ampemail/authenticating-requests#proxy_assertion_tokens)を使用する必要があります。
 {% endalert %}
 
 {% endtab %}
 {% endtabs %}
 
-AMPコンポーネントの完全なリストについては、[AMPドキュメント](https://amp.dev/documentation/components/?format=email)を確認してください。  
+AMP コンポーネントの完全なリストについては、[AMP のドキュメント](https://amp.dev/documentation/components/?format=email)を確認してください。  
 
 ### ユースケース
 
 {% tabs local %}
 {% tab インタラクティブアンケート %}
 
-`<amp-form>`コンポーネントを使用すると、メール受信トレイを離れることなく完了できるインタラクティブなアンケートを作成できます。これは、`<amp-form>`を使用して調査の回答を送信し、その後バックエンドがこの集計データを提供することによって行うことができます。 
+`<amp-form>` コンポーネントを使用すると、メール受信トレイを離れずに行えるインタラクティブなアンケートを作成できます。これは、`<amp-form>` を使用して調査の回答を送信し、その後バックエンドがこの集計データを提供することによって行うことができます。 
 
-いくつかの例が含まれます:
-* カンファレンス調査メール
+例としては次のようなものがあります。
+* 会議のアンケートメール
 * フィード内のアイテムを動的に更新する
 * 記事ブックマークメール
 
-このコンポーネントを使用すると、ユーザーはフィールド値を送信またはクリアできます。また、メールの設定方法によっては、調査の送信が成功したかどうかなど、ユーザーに追加のプロンプトを表示したり、ユーザーからの回答を表示して調査の結果（投票キャンペーンなど）を表示することができます。
+このコンポーネントを使用すると、ユーザーはフィールド値を送信したりクリアしたりできます。また、メールの設定方法によっては、調査の送信が成功したかどうかなど、ユーザーに追加のプロンプトを表示したり、調査の結果 (投票キャンペーンなど) を含むユーザーからの回答を表示したりできます。
 
 {% endtab %}
 {% tab 折りたたみ可能なコンテンツ %}
 
-`<amp-accordion>`コンポーネントを使用してコンテンツセクションを拡張します。このコンポーネントを使用すると、折りたたみ可能および展開可能なコンテンツセクションを表示でき、視聴者がコンテンツの概要を一目で確認し、任意のセクションにジャンプする方法を提供します。 
+`<amp-accordion>` コンポーネントを使用してコンテンツのセクションを展開表示します。このコンポーネントを使用すると、折りたたみと展開が可能なコンテンツセクションを表示でき、オーディエンスはコンテンツの概要を一目で確認し、任意のセクションにジャンプできるようになります。 
 
-長い教育記事やパーソナライズされたおすすめを送る傾向がある場合、これにより視聴者はコンテンツの概要を一目で確認し、任意のセクションや特定の製品のおすすめにジャンプして詳細を得ることができます。これは、セクションに数文を入力するだけでもスクロールが必要なモバイルユーザーにとって特に役立ちます。
+長い教育記事やパーソナライズされたおすすめを送る傾向がある場合、これにより視聴者はコンテンツの概要を一目で確認し、任意のセクションや特定の製品のおすすめにジャンプして詳細を得ることができます。これは、セクションに数行入力するだけでもスクロールが必要なモバイルユーザーにとって特に便利です。
 {% endtab %}
-{% tab 画像 Heavy Emails %}
+{% tab 画像の多いメール %}
 
-小売ブランドのように多くのプロフェッショナルな写真を含むメールを送信する傾向がある場合、ユーザーが自分に訴求する画像と対話できる`<amp-image-lightbox>`コンポーネントを使用できます。ユーザーが画像をクリックすると、このコンポーネントはメッセージの中央に画像を表示し、ライトボックス効果を作成します。 
+小売ブランドのように多くのプロフェッショナルな写真を含むメールを頻繁に送信する場合、ユーザーにとって魅力のある画像と対話できるように `<amp-image-lightbox>` コンポーネントを使用できます。ユーザーが画像をクリックすると、このコンポーネントはメッセージの中央に画像を表示し、ライトボックス効果を作成します。 
 
-さらに、`<amp-image-lightbox>`コンポーネントにより、ユーザーは詳細な画像の説明を表示できます。同じコンポーネントを複数の画像に使用できます。例えば、メールに複数の画像が含まれている場合、ユーザーがどちらかの画像をクリックすると、画像がライトボックスに表示されます。
+さらに、`<amp-image-lightbox>` コンポーネントを使用すると、ユーザーは画像の詳細な説明を表示できます。同じコンポーネントを複数の画像に使用することができます。例えば、メールに複数の画像が含まれている場合、ユーザーがどちらかの画像をクリックすると、画像がライトボックスに表示されます。
 
 {% endtab %}
 {% tab フォント駆動のメール %}
 
-テキストコピーに主に依存するメールの場合、`<amp-fit-text>`コンポーネントを使用すると、指定された領域内のテキストのサイズとフィット感を管理できます。
+主にテキストコピーに依存するメールの場合、`<amp-fit-text>` コンポーネントを使用すると、指定した領域内のテキストのサイズとフィットを管理できます。
 
 例としては次のようなものがあります:
 
@@ -187,20 +187,20 @@ AMPコンポーネントの完全なリストについては、[AMPドキュメ
 {% endtab %}
 {% endtabs %}
 
-### アンプ-ムスタッシュを使用する
+### amp-mustache の使用
 
-Liquidと同様に、AMPはより高度なユースケースのためのスクリプト言語をサポートしています。このコンポーネントは[`amp-mustache`](https://amp.dev/documentation/components/amp-mustache/?format=email)と呼ばれます。Liquidの[`raw`](https://shopify.github.io/liquid/tags/raw/)タグで囲む必要があります。LiquidとMustacheは構文スタイルを共有していることに注意してください。 
+Liquidと同様に、AMPはより高度なユースケースのためのスクリプト言語をサポートしています。このコンポーネントは [`amp-mustache`](https://amp.dev/documentation/components/amp-mustache/?format=email) と呼ばれます。Mustache マークアップ言語を含める場合、これを Liquid の [`raw`](https://shopify.github.io/liquid/tags/raw/) タグで囲む必要があります。LiquidとMustacheは構文スタイルを共有していることに注意してください。 
 
 コンテンツを`raw`タグで囲むと、Braze処理エンジンは`raw`タグ間のコンテンツを無視し、チームが必要とするMustache変数を送信します。
 
 ## メトリクスと分析
 
-| メートル法 | 詳細 |
+| 指標 | 詳細 |
 |---|---|
 | 開封数の合計 | AMPメールのHTMLおよびプレーンテキストバージョンの合計オープン数。 |
 | クリック数の合計 | AMPメールのHTMLおよびプレーンテキストバージョンでの総クリック数。 |
 | AMPが開く | AMP HTML メールおよび AMP HTML バージョンのメールの開封総数。 |
-| AMP クリック数 | AMP HTML メールのクリック数の合計、HTML、プレーンテキスト、および AMP HTML バージョンのメールの累積数。 |
+| AMP クリック数 | AMP HTML メールのクリック数の合計、HTML、プレーンテキスト、および AMP HTML バージョンのメールの総計。 |
 {: .reset-td-br-1 .reset-td-br-2}  
 
 ## テストとトラブルシューティング
@@ -209,22 +209,22 @@ Liquidと同様に、AMPはより高度なユースケースのためのスク
 
 送信する前に、AMPメールをこれらの[Gmailガイドライン](https://developers.google.com/gmail/ampemail/testing-dynamic-email)に従ってテストすることをお勧めします。
 
-AMPメールを任意のGmailアカウントに配信するには、メールが次の条件を満たしている必要があります:
-- メールのセキュリティ要件のためのAMPを満たす必要があります。
+AMP メールを任意の Gmail アカウントに配信するには、メールが次の条件を満たしている必要があります。
+- メールのセキュリティ要件のための AMP を満たしていること。
 - AMP MIMEパートには有効なAMPドキュメントが含まれている必要があります。
-- メールにはHTML MIMEパートの前にAMP MIMEパートを含める必要があります。
+- メールの HTML MIME 部分の前に AMP MIME 部分が含まれていること。
 - AMP MIME パートは 100 KB 未満である必要があります。
 
 これらの条件のいずれもエラーを引き起こしていない場合は、\[サポート]\[support]に連絡してください。
 
 ### よくある質問
 
-{% details AMPメールでセグメント化すべきですか？ %}
+{% details AMP メールはセグメント化する必要がありますか? %}
 私たちは、すべての異なるタイプのユーザーに送信するためにセグメント化しないことを提唱しています。これは、元のメールに含まれる異なるバージョンを持つマルチパートでAMPメッセージを送信するためです。ユーザーがAMPバージョンを表示できない場合、デフォルトでHTMLに戻ります。
 {% enddetails %}
 
-{% details AMPメールを作成するための追加のヒントはありますか？ %}
-AMP要素を構築するために、開発チームに確認してください。これらの要素が設定された後、デザインリソースや要素を追加して、さらに磨きをかけることをお勧めします。
+{% details AMP メールを作成するための追加のヒントはありますか? %}
+AMP 要素を作成する際は、担当の開発チームと協力してください。これらの要素を設定したら、デザインリソースと要素を含めてさらに磨きをかけることをお勧めします。
 {% enddetails %}
 
 [1]: {% image_buster /assets/img/dynamic-content.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/apple_mail/email_private_relay_apple_SSO.md b/_lang/ja/_user_guide/message_building_by_channel/email/apple_mail/email_private_relay_apple_SSO.md
index ec4b603694e..b478f68c20f 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/apple_mail/email_private_relay_apple_SSO.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/apple_mail/email_private_relay_apple_SSO.md
@@ -1,6 +1,6 @@
 ---
-nav_title: Appleプライベートリレーにメールを送信する
-article_title: Appleプライベートリレーにメールを送信する
+nav_title: Apple Private Relay へのメール送信
+article_title: Apple Private Relay へのメール送信
 alias: /email_relay/
 page_order: 0
 description: "この記事では、Apple Private Relayにメールを送信する手順について説明する。"
@@ -11,30 +11,30 @@ channel:
 
 # Apple Private Relayにメールを送信する
 
-> iOS13のリリースに伴い、アップルはアップル顧客向けに、電子メールの送信方法に影響を与える機能を導入した。アップルのシングルサインオン（SSO）機能は、ユーザーがメールアドレスを共有したり（`example@icloud.com` ）、個人的なメールアドレスではなくブランドに提供されるものをマスキングしてメールアドレスを隠したり（`tq1234snin@privaterelay.appleid.com` ）することを可能にする。
+> Apple では iOS 13 のリリースに伴い、同社の顧客向けメールが送信される方法に影響を与える機能を導入しました。Apple のシングルサインオン (SSO) 機能は、ユーザーがメールアドレスを共有したり (`example@icloud.com`)、個人のメールアドレスではなくブランドに提供されるものをマスキングしてメールアドレスを隠したり (`tq1234snin@privaterelay.appleid.com`) することを可能にします。
 
-これらのユーザーは、Apple IDの設定ページから、Appleとのサインインを使用するアプリを管理することができる（[Appleのドキュメントを](https://support.apple.com/en-us/HT210426)参照）。ユーザーがアプリのリレーメールへのメール転送を無効にした場合、Brazeは通常通りメールのバウンス情報を受信する。アップルのプライベート・メール・リレーにメールを送信するには、送信ドメインをアップルに登録する。
+これらのユーザーは、Apple ID の設定ページから、Apple へのサインインを使用するアプリを管理することができます ([Apple のドキュメント](https://support.apple.com/en-us/HT210426)を参照してください)。ユーザーがアプリのリレーメールへのメール転送を無効にした場合、Brazeは通常通りメールのバウンス情報を受信する。Apple のプライベートメールリレーにメールを送信するには、送信ドメインを Apple に登録します。
 
 ## SendGridでメールを送信する
 
-メールプロバイダとしてSendGridを使用している場合、DNSを変更することなくアップルにメールを送信することができる。**アップル証明書の**ページにアクセスし、アップルのEメール・リレー・サービス経由で送信するために使用するEメールアドレスを許可する（希望の「From」アドレス）。  
+SendGrid をメールプロバイダーとして使用している場合、DNS を変更せずに Apple にメールを送信することができます。\[**Apple Certificate**] ページにアクセスし、Apple のメールリレーサービス経由での送信に使用するメールアドレス (希望の「差出人」アドレス) を許可します。  
 
-![]({% image_buster /assets/img/email-relay-whitelabel-address.png %}) アップル証明書ページで個々のメールアドレスを許可するオプション。
+![Apple Certificate ページで個々のメールアドレスを許可するオプション。]({% image_buster /assets/img/email-relay-whitelabel-address.png %})
 
-アドレスの書式は次のようにする：`bounces+<YOUR_UID>@<YOUR_WHITELABELED_SUBDOMAIN_AND_DOMAIN>`(e.g.,`bounces+1234567@braze.online.docs.com`).Apple証明書ページにアドレスが追加されると、このドメインからのメールはApple Private Relayシステム経由で配信される。
+アドレスのフォーマットは次のようにします: `bounces+<YOUR_UID>@<YOUR_WHITELABELED_SUBDOMAIN_AND_DOMAIN>`(e.g., `bounces+1234567@braze.online.docs.com`)。Apple証明書ページにアドレスが追加されると、このドメインからのメールはApple Private Relayシステム経由で配信される。
 
 {% alert important %}
 希望する "From "アドレスが`abmail` の場合、サブドメインにそのアドレスを含める。例えば、`docs.braze.com` の代わりに`abmail.docs.braze.com` を使う。あなたの住所はそうではないかもしれない。SendGridのDNSレコードを確認する。
 {% endalert %}
 
-### アドレスの値
+### 差出人アドレスの値
 
 Apple Private Relayでメールアドレスを追加する際に使用するコンポーネントについては、この表を参照のこと。
 
-| 価値 | 説明 |
+| 値 | 説明 |
 |---|---|
-| UID | この値は、Brazeが（SendGridから）提供するDNSレコードで提供される。メールアドレスのUIDに「u」を含めないこと。例えば、あなたのUIDがSendGridで`u1234567.wl134.sendgrid.net` と表示されている場合、`1234567` がUID値である。<br><br> DNSレコードにアクセスできない場合は、Brazeカスタマーサクセスマネージャーに連絡してUIDを提供してもらう。 |
-| ホワイトラベル付きサブドメインとドメイン | SendGridに入力した最初のドメインとサブドメイン。SendGridのDNSレコードで**HOST値を**使用することもできる。 |
+| UID | この値は、Braze が (SendGrid から) 提供する DNS レコードで提供されます。メールアドレスの UID に「u」の文字を含めることはできません。例えば、あなたのUIDがSendGridで`u1234567.wl134.sendgrid.net` と表示されている場合、`1234567` がUID値である。<br><br> DNSレコードにアクセスできない場合は、Brazeカスタマーサクセスマネージャーに連絡してUIDを提供してもらう。 |
+| ホワイトラベル付きサブドメインとドメイン | SendGridに入力した最初のドメインとサブドメイン。SendGrid の DNS レコードで**HOST 値**を使用することもできます。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## SparkPostのメールを送信する
@@ -42,11 +42,11 @@ Apple Private Relayでメールアドレスを追加する際に使用するコ
 SparkPost用のApple Private Relayを設定するには、以下の手順に従う： 
 
 1. Appleでサインインする。 
-2. Eメールのドメインを追加する。 
-3. アップルは自動的にドメインをチェックし、どのドメインが確認済みかを表示し、ドメインを修正または削除するオプションを提供する。
+2. メールのドメインを追加します。 
+3. Apple が自動的にドメインをチェックし、どのドメインが検証済みかを表示し、ドメインを再検証または削除するオプションを提供します。
 
 {% alert important %}
-検証ファイルが作成されてから2〜3日以内にこのプロセスを完了させなければならない。アップルは有効期間を明らかにしていない。
+このプロセスは検証ファイルが作成されてから 2 〜 3 日以内に完了させる必要があります。そうでないと有効期限が切れます。Apple ではこの有効期間を開示していません。
 {% endalert %}
 
-さらに質問がある場合は、[サポートチケットを]({{site.baseurl}}/braze_support/)開く。
+さらにご不明な点がある場合は、[サポートチケット]({{site.baseurl}}/braze_support/)を作成してください。
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/best_practices/use_cases.md b/_lang/ja/_user_guide/message_building_by_channel/email/best_practices/use_cases.md
index 4e47c131924..fc3a99cd840 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/best_practices/use_cases.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/best_practices/use_cases.md
@@ -22,37 +22,37 @@ channel: email
 
 ## 営業および販売促進
 
-コンテンツは、割引やセール情報、オファーの期間など、プロモーションの価値を伝えるものでなければならない。グラフィックを提供することは、あなたが宣伝している商品を説明する素晴らしい方法である。簡潔でシンプルなコピーを心がけ、メールを乱雑にし、本質的な内容からユーザーを遠ざけることのないようにする。行動喚起を明確にし、受信者がすぐにプロモーションに参加できる簡単な方法を提供する。
+コンテンツは、割引やセール情報、オファーの期間など、プロモーションの価値を伝えるものでなければならない。グラフィックの提供は、宣伝している商品を説明するための素晴らしい方法です。簡潔でシンプルなコピーを心がけ、メールを乱雑にし、本質的な内容からユーザーを遠ざけることのないようにする。コールトゥアクションを明確にして、受信者がすぐにプロモーションに参加できる簡単な方法を提供します。
 
-特定の商品を推薦する場合は、ユーザーが気に入る可能性のある、キュレーションされた個人的な提案として提示するようにする。期間限定のキャンペーンを宣伝する場合は、必ずユーザーに知らせること！イデリはこのEメールで緊急性を見事に伝えている：
+特定の商品を推薦する場合は、ユーザーが気に入る可能性のある、キュレーションされた個人的な提案として提示するようにする。期間限定のキャンペーンを宣伝する場合は、必ずユーザーに知らせること！Ideeli は次のメールで緊急性を見事に伝えています: 
 
-![Ideeliから送信される、期間限定のキャンペーンをお知らせするプロモーションメール。大きなバナーには「米国東部夏時間午前零時で終了」と書かれている。6時間のフラッシュセール。お急ぎください！このような素晴らしい発見は長くは続かないだろう」。][27]{: style="max-width:70%;"}
+![Ideeliから送信される、期間限定のキャンペーンをお知らせするプロモーションメール。大きなバナーには「米国東部夏時間午前零時で終了」と書かれている。6時間のフラッシュセール。お急ぎください！またとない素晴らしいチャンスです。」][27]{: style="max-width:70%;"}
 
 ## トランザクション
 
 ユーザーがアプリ内課金を行った後、ユーザーとのトランザクションに特化したメールキャンペーンのコンテンツガイドラインをいくつか紹介しよう：
 - お礼を述べ、その買い物を最大限に活用するためのヒントを提供する。 
-- 出荷の確認と、出荷に関する質問の方法を提供する。
+- 出荷の確認と、配送に関する質問の方法を提供する。
 - 押しつけがましくなく、意見を求めるためにフィードバックを求める
 
 ユーザーにサービスを提供しただけなので、ユーザーは自分の考えを共有しやすいかもしれない。Restaurant.com からのメールの例である：
 
-![Restaurants.com から送信される、ユーザーにフィードバックを求めるトランザクションメール。そのEメールには「私たちにすべてを教えてください」と書かれている！REDACTEDでの食事と経験を楽しんでいただけたなら幸いだ。お客様に最高のサービス、料理、そして全体的な体験を提供するために、私たちができることをすべて行っていることを確認するために、ぜひご意見をお寄せください。あなたの意見は我々にとって非常に貴重であり、あなたの考えに感謝している」。行動喚起には「アンケートに答える」とある。][28]{: style="max-width:80%;"}
+![Restaurants.com から送信される、ユーザーにフィードバックを求めるトランザクションメール。内容は次のとおり: 「いかがでしたか? REDACTEDでの食事と経験を楽しんでいただけたなら幸いだ。お客様に最高のサービス、料理、そして全体的な体験を提供するために、私たちができることをすべて行っていることを確認するために、ぜひご意見をお寄せください。お客様の意見はとても貴重です。お忙しいところフィードバックをお寄せいだき誠にありがとうございます。」コールトゥアクションは「アンケートに答える」。][28]{: style="max-width:80%;"}
 
 ## リテンション
 
 友好的な口調を心がけよう！ユーザーを取り戻す最後のチャンスかもしれないので、アプリの価値をアピールするコンテンツを必ず盛り込もう。インストール後、ユーザーが比較的活動的でない場合は、使い始めるのに役立つヒントを提供する。
 
-- ソーシャルアプリの場合、ユーザーの友人のアクティビティを常に更新する。
+- ソーシャルアプリの場合、ユーザーの友達のアクティビティを常に更新します。
 - ユーザーを呼び戻すために、割引やその他のインセンティブを提供する。
 
-ユーザーがまだ大切にされていることを示すために、メッセージを個人的なものにするよう心がけよう。たとえばルー・ララでは、リテンションメールをCEOからのメモとして位置づけている：
+ユーザーがまだ大切にされていることを示すために、メッセージを個人的なものにするよう心がけよう。たとえば Rue La La では、リテンションメールを CEO からのメモとして位置付けています。
 
-![Rue La LaのCEOからパーソナライズされたメッセージとともに顧客に送られたリテンションメール。そのメールには「ちょっとした挨拶だ。ルーのCEOとして、私はメンバーたちの様子をチェックするのが好きだ。ほとんどの人がルーが大好きだと言ってくれる。(お世辞でも嬉しいよ）。でも、まだ感じていないようだね...。ここで微妙なことを言うつもりはない。デザイナーズ・バッグでも、新しいジーンズでも、自宅のための素晴らしいものでも、このサイトを見て、あなたの心に響くものを見つけてほしい。私は（本当に）ここからルー愛を感じ始めると信じている。お楽しみに！"][29]{: style="max-width:80%;"}
+![Rue La LaのCEOからパーソナライズされたメッセージとともに顧客に送られたリテンションメール。内容は次のとおり:「こんにちは。今日は Rue の CEO から会員の皆さんに簡単なご挨拶です。日頃から Rue が大好きと言ってくださる皆さん。(お世辞でも嬉しいよ）。でも、まだ、どこか何かが足りないような気がします。そこで本日は特別なオファーを提供したいと思います。デザイナーズ・バッグでも、新しいジーンズでも、自宅のための素晴らしいものでも、このサイトを見て、あなたの心に響くものを見つけてほしい。これで皆さんに Rue の愛を実感ていただけるものと心から信じています。Enjoy!」][29]{: style="max-width:80%;"}
 
 ## ソーシャル
 
-Eメールは、受信者をソーシャル・メディア・プラットフォームに誘導することで、ソーシャル・ファンを増やすのに役立つ。ユーザーが簡単につながることができるように、ソーシャルメディアアカウントへのリンクをメール内に含める。
+メールは、受信者をソーシャルメディアプラットフォームに誘導することで、ソーシャルファンを増やすのに役立ちます。ユーザーが簡単につながることができるように、ソーシャルメディアアカウントへのリンクをメール内に含めます。
 
 楽しくしよう！フォトコンテストを開催したり、ハッシュタグを宣伝したり、プレゼントを用意したりしてみよう。以下は、フォト・チャレンジに参加すると報酬がもらえるというHailoからのメールだ：
 
@@ -60,11 +60,11 @@ Eメールは、受信者をソーシャル・メディア・プラットフォ
 
 ## 更新情報
 
-すべてのユーザーに新機能や改良された機能のアップデートを送信する。新機能のアップデートは、アプリの価値を失効しているユーザーに思い出させるため、リエンゲージメントツールにもなる。
+すべてのユーザーに新機能や改良された機能のアップデートを送信する。新機能のアップデートは、離脱ユーザーにアプリの価値を再確認してもらう再エンゲージメントツールにもなります。
 
-説明やデモが必要な機能の場合は、メッセージにリンクを含める。Allrecipes.com ：
+説明やデモが必要な機能の場合は、メッセージにリンクを含める。次は Allrecipes.com からの例です。
 
-![Allrecipesの新機能を知らせる、アップデートに焦点を当てたEメールの例。メールのトップには「あまりにも」と書かれている。大勢だ。パスワードだ。パスワードにうんざりしている？我々もそうだ。メール本文は、フェイスブックかグーグルプラスでサインインするようユーザーを誘導し、"See How "というコールトゥアクションを促している。][31]{: style="max-width:70%;"}
+![ユーザーに Allrecipes の新機能を知らせる、アップデートに焦点を当てたメールの例。メールのトップには、「あまりにも...多すぎる...パスワード...もうたくさん! と思いませんか」とあり、メールの本文はユーザーに Facebook か Google plus でサインインするように促し、「やり方を見る」コールトゥアクションを呼び出します。][31]{: style="max-width:70%;"}
 
 
 [26]: {% image_buster /assets/img_archive/Livingsocial_email.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks.md b/_lang/ja/_user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks.md
index c664c22949b..3331ce5cec4 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks.md
@@ -1,5 +1,5 @@
 ---
-nav_title: エディター・ブロック
+nav_title: エディターブロック
 article_title: ドラッグ＆ドロップ・エディター・ブロック
 alias: "/dnd/editor_blocks/"
 channel: email
@@ -9,13 +9,13 @@ tool: Media
 
 ---
 
-# エディター・ブロック
+# エディターブロック
 
-> このリファレンスでは、エディター・ブロックの種類とカスタマイズ可能なプロパティをリストアップしている。これらのブロックは、ドラッグ・アンド・ドロップ・エディターの「**コンテンツ」**セクションで利用できる。
+> この記事では、エディターブロックのタイプとカスタマイズ可能なプロパティを列挙します。これらのブロックは、ドラッグ・アンド・ドロップ・エディターの「**コンテンツ」**セクションで利用できる。
 
-エディターブロックを使うには、ドラッグ＆ドロップ・エディターでエディターブロックを列の中にドラッグする。カラム幅に自動調整される。各エディター・ブロックは、パディングのきめ細かなコントロールなど、独自の設定を持っている。
+エディターブロックを使うには、ドラッグ＆ドロップ・エディターでエディターブロックを列の中にドラッグする。カラム幅に自動調整される。各エディターブロックは、埋め込みのきめ細かなコントロールなど、独自の設定を持っています。
 
-これらのエディタブロックの使い方やカスタマイズ方法については、[クリエイティブの詳細]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/#creative-details)セクションをチェックしよう。
+これらのエディターブロックのメールでの使い方やカスタマイズ方法については、[さらにクリエイティブな詳細]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/#creative-details)のセクションを参照してください。
 
 {% alert tip %}
 また、`Image` 、`Button` 、`Text` エディターブロック内の任意のURLに[カスタム属性を追加する]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/#creative-details/)こともできる。
@@ -23,7 +23,7 @@ tool: Media
 
 ## 種類
 
-次の表は、ユーザーが各エディター・ブロック・タイプをどのように使用できるかを説明している。
+次の表は、ユーザーが各エディターブロックタイプをどのように使用できるかについて説明しています。
 
 | 名前 | 記述 |
 |---|---|
@@ -31,13 +31,13 @@ tool: Media
 |`Paragraph`| メッセージにテキストを入力する。ツールバーは、フォントやテキスト編集機能をサポートする。 | 
 |`List`| 箇条書きリストを追加する。 |
 |`Button`| 標準ボタンを追加する。このブロックのプロパティでは、リンクを簡単に編集・設定できる。 | 
-|`Divider`| 実線、点線、または破線を挿入し、間隔を調整する。|
+|`Divider`| 実線、点線、または破線を挿入し、間隔を調整します。|
 |`Spacer`| 他のブロックの間にスペース（パディング）を追加する。 |
 |`Image`| メディアライブラリから画像を挿入する。 | 
 |`Video`| 動画コンテンツへのリンクを作成する。 |
-|`Social`| ソーシャルメディア・プラットフォームのアイコンを挿入する。ブランド固有のアイコンのためにカスタム画像をアップロードすることもできる。 |
-|`Icons`| アイコンを挿入する。カスタム画像もアップロードできる。画像がアップロードされるまで、特大のプレースホルダー・アイコンが使用される。 |
-|`HTML`| 生のHTMLを挿入する。コネクテッド・コンテンツや条件文のような高度なリキッドに最適だ。 | 
+|`Social`| ソーシャルメディアプラットフォームのアイコンを挿入します。ブランド固有のアイコンのためにカスタム画像をアップロードすることもできる。 |
+|`Icons`| アイコンを挿入する。カスタム画像もアップロードできます。画像がアップロードされるまで、特大のプレースホルダー・アイコンが使用される。 |
+|`HTML`| 生のHTMLを挿入する。コネクテッドコンテンツや条件文のような高度な Liquid に適しています。 | 
 |`Menu`| デザインするメッセージに合わせたフレキシブルなメニューを作成する。 |
 {: .reset-td-br-1 .reset-td-br-2} 
 
@@ -49,9 +49,9 @@ tool: Media
 
 | プロパティ | 記述 |
 |---|---|
-|`Title`| 見出しのスタイルを選択する。H1、H2、H3のみ使用可能である。 | 
+|`Title`| 見出しのスタイルを選択する。H1、H2、H3 のみ使用可能です。 | 
 |`Font family`| これはタイトルのフォントスタイルである。 |
-|`Font weight`| これはフォントの全体的な太さである。 |
+|`Font weight`| これはフォントの全体的な太さです。 |
 |`Font size`| テキストのサイズを決定する。 |
 |`Text color`| タイトルの色を変更する。 |
 |`Link color`| リンクの色を変更する。 |
@@ -68,7 +68,7 @@ tool: Media
 | プロパティ | 記述 |
 |---|---|
 |`Font family`| これは段落テキストのフォントスタイルである。 |
-|`Font weight`| これはフォントの全体的な太さである。 |
+|`Font weight`| これはフォントの全体的な太さです。 |
 |`Font size`| テキストのサイズを決定する。 |
 |`Text color`| タイトルの色を変更する。 |
 |`Link color`| リンクの色を変更する。 |
@@ -85,11 +85,11 @@ tool: Media
 
 | プロパティ | 記述 |
 |---|---|
-|`List type`| これがリストの種類だ。箇条書きでも番号でもよい。 |
+|`List type`| これがリストの種類だ。箇条書きまたは番号リストが可能です。 |
 |`List style type`| リストのスタイルを決定する。 |
 |`Start list from`| リストの開始番号を決定する。 |
 |`Font family`| これは段落テキストのフォントスタイルである。 |
-|`Font weight`| これはフォントの全体的な太さである。 |
+|`Font weight`| これはフォントの全体的な太さです。 |
 |`Font size`| テキストのサイズを決定する。 |
 |`Text color`| タイトルの色を変更する。 |
 |`Link color`| リンクの色を変更する。 |
@@ -108,18 +108,18 @@ tool: Media
 | プロパティ | 記述 |
 |---|---|
 |`Link Type`| ボタンをクリックしたときの動作を決定し、適切なリンクプロトコルを設定する。 |
-|`URL`| 選択された`Link Type` に基づいて動的に変化する。|
+|`URL`| 選択された `Link Type` に応じてダイナミックに変化します。|
 {: .reset-td-br-1 .reset-td-br-2}
 
-### ディバイダー
+### 区切り線
 
 `Divider` エディター・ブロックの詳細については、以下の表を参照のこと。
 
 | プロパティ | 記述 |
 |---|---|
 |`Transparent`| 有効にすると、'line' と 'width' オプションは削除される。 |
-|`Line`| 点線、斑点、実線など、さまざまな線形式がある。 さらに、仕切り線の太さや色も変更できる。 |
-|`Width `| デバイダーのスプレッドを5刻みで調整する。  |
+|`Line`| 点線、斑点、実線など、さまざまな線形式。 さらに、区切り線の太さや色も変更できます。 |
+|`Width `| 区切り線の幅を 5 刻みで調整します。  |
 |`Align`| 線を左、中央、右向きのいずれかに移動する。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -129,12 +129,12 @@ tool: Media
 
 | プロパティ | 記述 |
 |---|---|
-|`Height`| スペーサーブロックの高さを調整する。デフォルトは60pxである。|
+|`Height`| スペーサーブロックの高さを調整します。デフォルトは60pxである。|
 {: .reset-td-br-1 .reset-td-br-2}
 
-### イメージ
+### 画像
 
-`Image` エディター・ブロックの詳細については、以下の表を参照のこと。ダイナミック画像（リキッド付き画像）については、自動幅設定を使用するためのフォールバック画像を設定する必要がある。
+`Image` エディター・ブロックの詳細については、以下の表を参照のこと。ダイナミック画像 (Liquid 使用画像) については、自動幅設定を使用するためのフォールバック画像を設定する必要があります。
 
 | プロパティ | 記述 |
 |---|---|
@@ -159,7 +159,7 @@ tool: Media
 |`URL`| ビデオのURL。 |
 |`Title`| 動画のメタデータから自動生成されるが、カスタマイズすることもできる。 なお、YouTubeとVimeoのみ対応している。 |
 |`Play Icon Style`| ビデオ画像の上部にある再生ボタンのさまざまなオプションを含む。 |
-|`Play Icon Color`| 再生ボタンのために**ライト**または**ダーク**を選択するオプション。 |
+|`Play Icon Color`| 再生ボタンの**ライト**または**ダーク**を選択するオプション。 |
 |`Play Icon Size`| 再生ボタンのピクセルサイズを選択する。固定範囲は50pxから80pxまで（5px刻み）。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -186,7 +186,7 @@ Vimeoでホストされている動画は、公開に設定されている場合
 | プロパティ | 記述 |
 |---|---|
 |`Font family`| これは段落テキストのフォントスタイルである。 |
-|`Font weight`| これはフォントの全体的な太さである。 |
+|`Font weight`| これはフォントの全体的な太さです。 |
 |`Font size`| テキストのサイズを決定する。 |
 |`Text color`| タイトルの色を変更する。 |
 |`Link color`| リンクの色を変更する。 |
@@ -217,12 +217,12 @@ Vimeoでホストされている動画は、公開に設定されている場合
 |`Font Size`| メニューのサイズ。 |
 |`Text Color`| メニューの色を変更する。 |
 |`Link Color`| メニューテキストの色を変更する。 |
-|`Align`| メニューを左、中央、右方向に移動する。 |
+|`Align`| メニューを左、中央、右方向に移動します。 |
 |`Letter spacing`| 各文字間の距離を変更する。 |
-|`Layout`| レイアウトを水平または垂直に決定する。 |
+|`Layout`| レイアウトを横方向か縦方向に決定します。 |
 |`Separator`| メニューオプションの間に文字を追加する。 |
 |`Mobile menu`| モバイル・デバイスで表示する際のアイコンのサイズ、色、アイコンの種類を変更するオプションを含む。 |
-|`Item padding`| **+**または**-**ボタンを使用するか、特定の数値を入力して、パディングを変更します。 |
+|`Item padding`| **+** または **-** ボタンを使用するか、特定の数値を入力して、埋め込みを変更します。 |
 |`All sides`| `Item padding` が無効の場合、一貫したパディング番号を設定する。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -232,5 +232,5 @@ Vimeoでホストされている動画は、公開に設定されている場合
 
 | 名前 | 記述 |
 |---|---|
-| `Add Personalization` | 標準(デフォルト)アトリビュート、カスタムアトリビュート、コンテンツブロックなどの標準的なリキッドスニペットを検索できる。 | 
+| `Add Personalization` | 標準 (デフォルト) アトリビュート、カスタムアトリビュート、コンテンツブロックなどの標準的な Liquid スニペットを検索できます。 | 
 {: .reset-td-br-1 .reset-td-br-2}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup.md b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup.md
index b4f23226f6a..124b0e61947 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup.md
@@ -4,7 +4,7 @@ article_title: オンボーディングメールセットアップ
 layout: dev_guide
 page_order: 1
 guide_top_header: "メール設定"
-guide_top_text: "Brazeは、メールキャンペーンの送信を開始するのに役立ちます。ガイドに従うか、<a href='https://learning.braze.com/email-onboarding-for-pro-and-enterprise-achieving-high-deliverability' target='_blank'>メールオンボーディング</a> Brazeラーニングコースをチェックしてください。"
+guide_top_text: "Brazeは、メールキャンペーンの送信を開始するのに役立ちます。ガイドに従うか、<a href='https://learning.braze.com/email-onboarding-for-pro-and-enterprise-achieving-high-deliverability' target='_blank'>メールオンボーディング</a>の Braze ラーニングコースを参照してください。"
 page_type: landing
 description: "このランディングページには、メールキャンペーンの開始に関するリソースが含まれており、IPやドメインの設定、IPウォーミング、メールの検証などが含まれています。"
 channel: email
@@ -17,7 +17,7 @@ guide_featured_list:
 - name: "IP ウォームアップ"
   link: /docs/user_guide/message_building_by_channel/email/email_setup/ip_warming/
   image: /assets/img/braze_icons/annotation-alert.svg
-- name: "メール Validation"
+- name: "メール検証"
   link: /docs/user_guide/message_building_by_channel/email/email_setup/email_validation/
   image: /assets/img/braze_icons/check-square-broken.svg
 - name: "メール認証"
@@ -43,21 +43,21 @@ guide_featured_list:
 
 | 要件 | 説明 | ソース |
 |---|---|---|
-| 専用IP（インターネットプロトコル）| 専用IPは、単一のホスティングアカウントにのみ提供されるユニークなインターネットアドレスです。 | Brazeは顧客に専用のIPを提供し、メール送信者の評判をコントロールできるようにします。Brazeのオンボーディングがこれを設定します。|
-| ホワイトラベルドメイン | これらはドメインとサブドメインで構成されています。ホワイトラベリングを使用することで、DKIMおよびSPFのメール認証チェックを通過できます。 | Brazeオンボーディングチームはこれらのドメインを生成しますが、名前を選択する必要があります。 |
-| サブドメイン | これは、メールアドレス内のドメイン（「@news.company.com」など）のサブディビジョンです。サブドメインを持つことで、会社の公式メールの評判を損なう可能性のあるエラーを防ぐことができます。 | オンボーディングチームがこれを生成しますが、サブドメインの名前を決めるのはあなたです。Brazeの外部で現在使用されているサブドメインは使用できません。 |
+| 専用IP（インターネットプロトコル）| 専用 IP は、単一のホスティングアカウント用に提供される一意のインターネットアドレスです。 | Brazeは顧客に専用のIPを提供し、メール送信者の評判をコントロールできるようにします。これは Braze のオンボーディングによって設定されます。|
+| ホワイトラベルドメイン | これらはドメインとサブドメインで構成されています。ホワイトラベルを使用することで、DKIM および SPF のメール認証検査を通過できます。 | これらのドメインは Braze オンボーディングチームによって生成されますが、ドメインの名前は選択する必要があります。 |
+| サブドメイン | これは、メールアドレス内のドメイン（「@news.company.com」など）のサブディビジョンです。サブドメインを持つことで、会社の公式メールの評判を損なう可能性のあるエラーを防ぐことができます。 | これはオンボーディングチームによって生成されますが、サブドメインの名前は決定する必要があります。Brazeの外部で現在使用されているサブドメインは使用できません。 |
 | IP プール | これらは、1つのメールの評判が他のメールに影響を与えるのを防ぎ、より高い配信率をサポートするために、異なる種類のメール（「プロモーション」や「トランザクション」など）の評判を分けるために使用されるオプションの設定です。 | オンボーディングチームがプールを設定します。次に、メールを作成するときに、**IP Pool** ドロップダウンからメールのIPプールを選択し、**Target Users** ページで選択します。|
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## IPウォーミング
 
 {% alert important %}
-IPウォーミングはメール設定プロセスにおける**最も重要なステップ**です。これは最初のステップではありませんが（実際には最後のステップです）、ここでお知らせするのは、IPアドレスをウォームアップしなければ、送信するメールがスパムに送られたり、他の送信障害に遭遇したりする可能性があるためです。
+IP ウォーミングはメール設定のプロセスにおける**最も重要なステップ**です。これは最初のステップではありませんが（実際には最後のステップです）、ここでお知らせするのは、IPアドレスをウォームアップしなければ、送信するメールがスパムに送られたり、他の送信障害に遭遇したりする可能性があるためです。
 {% endalert %}
 
-[IPウォーミング]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/ip_warming/)とは、最初のバッチで比較的少数のメールを送信し、その後、次のバッチで徐々に量を増やしていき、通常の1日の量に達するまでのプロセスです。これは、メール設定プロセスの最後に行われます。
+[IPウォーミング]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/ip_warming/)とは、最初のバッチで比較的少数のメールを送信し、その後、次のバッチで徐々に量を増やしていき、通常の1日の量に達するまでのプロセスです。これは、メールの設定プロセスの最後に行われます。
 
-少量のメールから始めることで、メールプロバイダーとの信頼関係を築き、関連するユーザーにのみメールを送信していることを示しています。最も関心のあるユーザーに最初のメールを送信することで、プロバイダーとの信頼を早く得ることができます。
+少量のメールから始めることで、メールプロバイダーとの信頼関係を確立し、関連のあるユーザーにのみメールを送信していることを示します。最初のバッチを最もエンゲージメントの高いユーザーに送信することで、プロバイダーの信頼をより迅速に得ることができます。
 
 IPのウォームアップが完了したら、[メールの作成と送信を開始できます]({{site.baseurl}}/user_guide/message_building_by_channel/email/html_editor/creating_an_email_campaign/)！
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/deliverability_pitfalls_and_spam_traps.md b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/deliverability_pitfalls_and_spam_traps.md
index 863f3c8d892..7b3d2199e44 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/deliverability_pitfalls_and_spam_traps.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/deliverability_pitfalls_and_spam_traps.md
@@ -12,10 +12,10 @@ channel: email
 
 以下のスパムトラップは、メール配信に影響を与える可能性がある：
 
-| トラップ・タイプ | 説明 |
+| トラップタイプ | 説明 |
 |---|---|
-| プリスティン・トラップ | 一度も使用されたことのないメールアドレスとドメイン。 |
-| リサイクル・トラップ | 元々は実在のユーザーであったが、現在は休止しているメールアドレス。 |
+| プリスティントラップ | 一度も使用されたことのないメールアドレスとドメイン。 |
+| リサイクルトラップ | 元々は実在のユーザーであったが、現在は休止しているメールアドレス。 |
 | タイポの罠 | よくあるタイプミスを含むメールアドレス。 |
 | スパムの苦情 | あなたのメールが顧客によってスパムとしてマークされた場合。 |
 | 高い直帰率 | 受信者のアドレスが無効であるために、メールが常に配信できない場合。 |
@@ -23,11 +23,11 @@ channel: email
 
 ## スパムの罠を回避する方法
 
-このような罠は、確認オプトイン・プロセスを設定すれば回避できる。最初のオプトインメールを送信し、顧客があなたのメッセージを望んでいることを確認するよう求めることで、受信者があなたからの連絡を望んでいること、そして実在する有効なアドレスに送信していることを確認することができる。スパムの罠を回避するその他の方法を紹介しよう：
+このような罠は、確認オプトイン・プロセスを設定すれば回避できる。最初のオプトインメールを送信し、メッセージを希望するかどうかを顧客に確認することで、受信者があなたからの返信を求めているか、そして実際の有効なアドレスに送信しているかどうかを確認できます。スパムの罠を回避するその他の方法を紹介しよう：
 
-1. ダブルオプトインメールを送る。これは、ユーザーがリンクをクリックして購読の選択を確認することを要求するメールである。
-2. ベストプラクティスとして、[サンセット・ポリシーを]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/sunset_policies/)導入する。
-3. **決してEメールリストを購入しないこと。** 
+1. ダブルオプトインメールを送信します。これは、ユーザーがリンクをクリックして購読の選択を確認することを要求するメールです。
+2. ベストプラクティスとして、[サンセットポリシー]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/sunset_policies/)を導入します。
+3. **メールリストは決して購入しないようにします。** 
 
 {% alert tip %}
 Brazeのカスタマーサクセスチームとデリバビリティチームは、お客様がベストプラクティスに従って世界中でデリバビリティを最大化できるようにサポートする。
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/email_validation.md b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/email_validation.md
index 8d64009e65f..bda5a78b800 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/email_validation.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/email_validation.md
@@ -1,6 +1,6 @@
 ---
-nav_title: メール Validation 
-article_title: メール Validation
+nav_title: メール検証 
+article_title: メール検証
 alias: "/email_validation/"
 page_order: 3
 page_type: reference
@@ -13,14 +13,14 @@ channel: email
 
 > このリファレンス記事では、メールアドレスのローカルおよびホスト部分の検証ルールについて説明します。
 
-バリデーションは、ダッシュボードメールアドレス、エンドユーザーメールアドレス（お客様）、およびメールメッセージの送信元および返信先アドレスに使用されます。メールの検証は、ユーザーのメールアドレスが更新されたとき、またはAPI、CSVアップロード、またはSDKを介してBrazeにインポートされているとき、またはダッシュボードで変更されたときに実行されます。メールアドレスには空白を含めることはできません。APIを使用している場合、空白は`400`エラーを引き起こします。
+検証は、ダッシュボードメールアドレス、エンドユーザーメールアドレス （お客様の顧客）、およびメールメッセージの送信元および返信先アドレスに対して行われます。メールの検証は、ユーザーのメールアドレスが更新されたとき、またはAPI、CSVアップロード、またはSDKを介してBrazeにインポートされているとき、またはダッシュボードで変更されたときに実行されます。メールアドレスには空白を含めることはできません。API を使用している場合、空白は `400` エラーを引き起こします。
 
-Brazeは特定の文字を受け付けず、それらを無効として認識します。メールがバウンスされた場合、Brazeはメールを無効としてマークし、サブスクリプションステータスは変更されません。  
+Brazeは特定の文字を受け付けず、それらを無効として認識します。メールがバウンスされた場合、Braze はメールを無効としてマークし、サブスクリプションステータスは変更されません。  
 
-{% details 受け入れられる文字 %}
-- 文字 (A-Z)
-- 数字（0-9）
-- シンボル
+{% details 使用できる文字 %}
+- 文字 (A ～ Z)
+- 数字 (0 ～ 9)
+- 記号
 	- -
 	- ^
 	- +
@@ -28,7 +28,7 @@ Brazeは特定の文字を受け付けず、それらを無効として認識し
 	- ''
 	- ＆
 	- #
-	- テキストを日本語に翻訳します。
+	- /
 	- ％
 	- *
 	- =
@@ -37,16 +37,16 @@ Brazeは特定の文字を受け付けず、それらを無効として認識し
 	- ~
 	- ！
 	- ？
-	- 。
+	- . (文字または他の文字の間のみ)
 {% enddetails %}
 
-{% details 受け入れられない文字 %}
+{% details 使用できない文字 %}
 - 空白文字（ASCIIおよびUnicode）
 {% enddetails %}
 
 この検証は、Briteverifyのような検証サービスと混同しないでください。これは、メールアドレスの構文が正しいことを確認するためのチェックです。この検証プロセスを使用する主な理由の1つは、メールアドレスのローカル部分で国際文字（UTF-8など）をサポートすることです。
 
-メールの構文検証は、メールアドレスのローカル部分とホスト部分の両方を確認します。ローカル部分はアスペランド（@）の前の部分であり、ホスト部分はアスペランドの後の部分です。例えば、メールアドレスのこのローカル部分は、ピリオド (.) を除く許可された文字で始まり、終わることができます。このプロセスはメールアドレスの構文のみを検証しており、ドメインに有効なMXサーバーがあるかどうか、またはリストされたドメインにユーザーが存在するかどうかは考慮していないことに注意してください。
+メールの構文検証は、メールアドレスのローカル部分とホスト部分の両方を確認します。ローカル部分はアスペランド （@） の前のすべての部分、ホスト部分はアスペランドの後のすべての部分です。例えば、メールアドレスのこのローカル部分は、ピリオド (.) を除く任意の許可された文字で始まり、終わることができます。このプロセスはメールアドレスの構文のみを検証しており、ドメインに有効なMXサーバーがあるかどうか、またはリストされたドメインにユーザーが存在するかどうかは考慮していないことに注意してください。
 
 {% alert note %}
 ドメイン部分に非[ASCII](https://en.wikipedia.org/wiki/ASCII)文字が含まれている場合、Brazeに提供される前に[Punycode-encoded](https://www.punycoder.com/)する必要があります。
@@ -54,7 +54,7 @@ Brazeは特定の文字を受け付けず、それらを無効として認識し
 
 Brazeがユーザーを追加するリクエストを受け取り、メールアドレスが無効と見なされた場合、APIでエラー応答が表示されます。CSV経由でアップロードする場合、ユーザーが作成されますが、メールアドレスは追加されません。
 
-## ローカルパートの検証ルール
+## ローカル部分の検証ルール
 
 ### 一般的なメールの検証
 
@@ -71,10 +71,10 @@ Brazeがユーザーを追加するリクエストを受け取り、メールア
 ```
 
 {% alert important %}
-ドメイン部分がGmailアドレスの場合、ローカル部分は少なくとも2文字以上である必要があります。これは、このセクションに記載されている正規表現の検証に加えてです。
+ドメイン部分が Gmail アドレスの場合、ローカル部分は少なくとも 2 文字以上が必要です。これは、このセクションに記載されている正規表現の検証に加えてです。
 {% endalert %}
 
-### マイクロソフト ドメイン
+### Microsoft のドメイン
 
 ホストドメインに「msn」、「hotmail」、「outlook」、または「live」が含まれている場合、ローカル部分を検証するために次の正規表現が使用されます: `/\A\w[\-\w]*(?:\.[\-\w]+)*\z/i`
 
@@ -91,26 +91,26 @@ Microsoft アドレスのローカル部分は次のパラメーターに従う
 
 ## ホスト部分の検証ルール
 
-IPv4 または IPv6 アドレスは、メールアドレスのホスト部分では許可されていません。トップレベルドメイン（.com、.org、.netなど）は完全に数字である必要はありません。
+IPv4 または IPv6 アドレスは、メールアドレスのホスト部分では許可されていません。最上位ドメイン （.com、.org、.net など） は完全に数字である必要はありません。
 
 次の正規表現はドメインを検証するために使用されます：<br>
 `/^[a-z\d](?:[a-z\d-]{0,61}[a-z\d])?(?:\.[a-z\d](?:[a-z\d-]{0,61}[a-z\d])?)+$/i`
 
 ドメイン名は次のパラメーターに従う必要があります:
 
-- 2つ以上のピリオドで区切られたラベルで構成されます
+- ピリオドで区切られた 2 つ以上のラベルで構成されます。
 	- ドメイン名の各部分は「ラベル」と呼ばれます。例えば、ドメイン名「example.com」は「example」ラベルと「com」ラベルで構成されています。
 - 少なくとも1つのピリオド（.）を含める必要があります。
 - 2つ以上の連続するピリオドを含むことはできません
-- 各期間区切りのラベルは次の条件を満たす必要があります:
+- ピリオド区切りの各ラベルは次の条件を満たしている必要があります: 
 	- 英数字（a-zまたは0-9）とハイフン（-）のみを含む
 	- 英数字（a-zまたは0-9）で始めます
 	- 英数字（a-zまたは0-9）で終了
-	- 1から63文字を含む
+	- 1 ～ 63 文字を含む
 
 ### 追加の検証が必要です
 
-ドメインの最終ラベルは、有効なトップレベルドメイン（TLD）でなければならず、これは最終ピリオド（.）の後の何かによって決定されます。このTLDは[ICANNのTLDリスト][2]にあるべきです。Brazeのメールバリデーターは、このセクションに記載されている正規表現に従って、メールの構文が正しいかどうかのみをチェックします。それはタイプミスや存在しないアドレスをキャッチしません。
+ドメインの最終ラベルは有効な最上位ドメイン （TLD） でなければならず、これは最後のピリオド （.） の後にあるものすべてによって決定されます。このTLDは[ICANNのTLDリスト][2]にあるべきです。Brazeのメールバリデーターは、このセクションに記載されている正規表現に従って、メールの構文が正しいかどうかのみをチェックします。それはタイプミスや存在しないアドレスをキャッチしません。
 
 {% alert important %}
 Unicodeはメールアドレスのローカル部分にのみ使用できます。ドメイン部分にはUnicodeは使用できませんが、Punycodeでエンコードされている場合があります。
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/import_your_email_list.md b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/import_your_email_list.md
index 8f6546b393e..d5a22bbf70a 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/import_your_email_list.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/import_your_email_list.md
@@ -1,5 +1,5 @@
 ---
-nav_title: メールリストをインポートする
+nav_title: メールリストのインポート
 article_title: メールリストをBrazeにインポートする
 page_order: 4
 page_type: reference
@@ -8,9 +8,9 @@ channel: email
 
 ---
 
-# メールリストをBrazeにインポートする {#importing-email-lists}
+# メールリストを Braze にインポートする {#importing-email-lists}
 
-> Eメール送信者として成功するための重要なステップは、質の高いEメールリストを確保することである。適切なメールリスト管理は、配信性を向上させ、より正確でクリーンなキャンペーン結果をもたらす。
+> メール送信を成功させるための重要なステップとして、質の高いメールリストを確保することがあります。適切なメールリスト管理によって配信到達性が向上し、より正確でクリーンなキャンペーン成果を得ることができます。
 
 ## 輸入前の注意事項
 
@@ -22,18 +22,18 @@ BrazeにEメールリストをインポートする前に、リストに本物
 
 Eメールリストのクリーニングサービスは、Eメールアドレスが正しい構文に従っているかどうか、Eメールアドレスの物理的な特性を持っているかどうかを判断し、Eメールのドメインを確認し、Eメールアドレスがそこに存在するかどうかを認証するためにEメールサーバーに接続することによって、あなたのためにこれを行うことができる。
 
-### エンゲージユーザーを特定する
+### エンゲージメントの高いユーザーを特定する
 
-最もエンゲージメントの高いユーザーを特定するためには、まず、深い周回遅れのユーザーを排除する。6ヶ月以上メールのやり取りをしていないユーザーにはメールを送らないのがベストプラクティスだ。メールリストをインポートする際は、過去6ヶ月以内にメールを開封したユーザーだけを含めるようにする。
+最もエンゲージメントの高いユーザーを特定するためには、まず、長期間にわたって離脱しているユーザーを排除します。メール送信者としての評判が損なわれないよう、6 か月以上メールのエンゲージメントがないユーザーにはメールを送信しないのがベストプラクティスです。メールリストをインポートする際は、過去 6 か月以内にメールを開封したユーザーだけを含めるようにします。
 
-長期的には、[サンセット・ポリシーの][60]導入も検討すべきだ。
+長期的には、[サンセットポリシー][60]の導入も検討する必要があります。
 
 ### 抑制リストを避ける
 
-既存のEメールプロバイダから移行する場合は、抑制リストからユーザーをインポートしないように注意すること。サプレッションリストは、配信停止、スパム扱い、あるいはハードバウンスされたメールアドレスをリストアップする。
+既存のEメールプロバイダから移行する場合は、抑制リストからユーザーをインポートしないように注意すること。抑制リストは、配信停止、スパム扱い、あるいはハードバウンスされたメールアドレスがリストされています。
 
-## 輸入の方法
+## インポート方法
 
-メールリストの準備ができたら、Braze REST APIやCSVファイルなど、Brazeにユーザーをインポートする方法がいくつかある。詳しくは[ユーザー・インポートの]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/)記事をご覧いただきたい。
+メールリストの準備ができたら、Braze REST API や CSV ファイルなど、Braze にユーザーをインポートする方法がいくつかあります。詳細については、[ユーザーインポート]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/)の専用記事を参照してください。
 
 [60]: {{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/sunset_policies/
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/ssl.md b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/ssl.md
index 1fee69c775f..a55e870c75b 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/ssl.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/email_setup/ssl.md
@@ -1,5 +1,5 @@
 ---
-nav_title: ブレイズのSSL
+nav_title: Braze の SSL
 article_title: SSLの概要
 page_order: 5
 page_type: reference
@@ -8,7 +8,7 @@ channel: email
 
 ---
 
-# ブレイズのSSL
+# Braze の SSL
 
 {% multi_lang_include video.html id="zP1N_wN0SsQ" align="right" %}
 
@@ -20,7 +20,7 @@ channel: email
 
 ウェブサイトやリンクをSSLで保護することは、機密性の高い顧客情報を直接扱わない企業でも一般的に行われている。SSLで保護されたリンクはユーザーからの信頼度が高く、認証のレイヤーが増えることでデータの保護に役立つ。
 
-### クリックと開封のトラッキングに必要
+### クリックと開封の追跡に必要
 
 Brazeでは、Eメールを送信する際、まずブランド化されたリンク追跡サブドメインを使用してリンクを変換し、ユーザーのクリックと開封を追跡する。デフォルトでは、これらのリンクはHTTPで始まる。つまり、非セキュアなトラフィックを制限するブラウザや拡張機能を使用しているユーザーは、たとえURLがセキュアであったとしても、リダイレクト先のURLに到達する前にリダイレクトを通過することが困難になる可能性がある。このため、画像が壊れたり、メール全体のクリックや開封のトラッキングが不正確になったりする可能性がある。このため、リンク追跡サブドメインにSSLレイヤーを適用し、Eメールでの安全なリダイレクトを確認するのがベストプラクティスである。 
 
@@ -34,7 +34,7 @@ HTTPストリクト・トランスポート・セキュリティ（HSTS）ドメ
 
 ## SSL証明書を取得する
 
-サードパーティ、通常はコンテンツ・デリバリー・ネットワーク（CDN）を利用することで、SSL証明書を取得することができる。CDNはSSL証明書をホストし、リンクがクリックされるたびにブラウザに提供することができる。これは、CDNを経由してトラフィックをリダイレクトし、必要な証明書を適用してから、メール・パートナーのSendGridまたはSparkPostに送信することで行われる。
+サードパーティ、通常はコンテンツ配信ネットワーク (CDN) を利用することで、SSL 証明書を取得することができます。CDNはSSL証明書をホストし、リンクがクリックされるたびにブラウザに提供することができる。これは、CDNを経由してトラフィックをリダイレクトし、必要な証明書を適用してから、メール・パートナーのSendGridまたはSparkPostに送信することで行われる。
 
 SSLセットアップを開始するには、Brazeカスタマーサクセスマネージャーに連絡し、BrazeのフルEメールセットアップを開始する。
 
@@ -42,46 +42,46 @@ Brazeがこのセットアップを開始したら、以下の手順に従う：
 1. Brazeは、ドメインレジストリに追加するDNSレコードを提供する。
 2. Brazeは、レコードがレジストリに正しく追加されているかどうかを確認する。
 3. この後、CDNを選択し、サードパーティーのプロバイダーからSSL証明書を取得する。 
-4. この時点で、CDNを設定する。なお、BrazeではCDN設定のトラブルシューティングはできない。さらなるサポートが必要な場合は、CDNプロバイダーに問い合わせること。
-5. SSLを有効にするには、カスタマー・サクセス・マネージャーに連絡しよう。
+4. この時点で、CDNを設定する。Braze は、CDN 設定のトラブルシューティングに役立ちません。さらなるサポートが必要な場合は、CDNプロバイダーに問い合わせること。
+5. SSL を有効にするには、カスタマーサクセスマネージャーに連絡してください。
 
 ### CDNとは何か、なぜ必要なのか？
 
-コンテンツ・デリバリー・ネットワーク（CDN）とは、複数のメディアにわたる高品質なコンテンツの迅速なロードタイムを保証すると同時に、セキュリティ証明書を扱うサーバーのプラットフォームである。 
+コンテンツ配信ネットワーク (CDN) とは、セキュリティ証明書を処理しながら、複数のメディアにわたる高品質なコンテンツの迅速な読み込みを保証するのに役立つサーバーのプラットフォームです。 
 
 {% alert important %}
-CDNの設定は、常にBrazeによってDNSレコードが検証された後に行われる。まだこのステップを開始していない場合は、カスタマー・サクセス・マネージャーに連絡し、開始方法の詳細を確認する。
+CDNの設定は、常にBrazeによってDNSレコードが検証された後に行われる。このステップをまだ開始していない場合は、カスタマーサクセスマネージャーに問い合わせて開始方法の詳細を確認してください。
 {% endalert %}
 
-Brazeでは、クリックトラッキングとオープントラッキングを行うために、配信パートナーがブランドのサブドメインを使用してリンクを変換し、CDNが新しく変換されたリンクにSSL証明書を適用する。リンクや画像を正しく表示させるために、メール受信者のブラウザに有効で信頼できる証明書を提示する必要がある。Brazeはこのような証明書を要求したり管理したりしないため、CDNを通じてユーザー側で設定する必要がある。 
+Brazeでは、クリックトラッキングとオープントラッキングを行うために、配信パートナーがブランドのサブドメインを使用してリンクを変換し、CDNが新しく変換されたリンクにSSL証明書を適用する。多くの場合、当社の配信パートナーは、リンクや画像を正しく表示できるように、有効で信頼できる証明書をメール受信者のブラウザに提示する必要があります。Braze はこのような証明書の要求や管理を行わないため、これは CDN を通じてユーザー側で設定する必要があります。 
 
 {% alert note %}
-クリックトラッキングとオープントラッキングにSSLを設定する際に、リストアップされたCDNを使用できない、または使用したくない場合は、カスタムSSL設定を行うことができる。代替CDNやカスタムプロキシは、より複雑で微妙なセットアップになる可能性がある。このトピックについては、[SendGridと](https://sendgrid.com/docs/ui/account-and-settings/custom-ssl-configurations/) [SparkPostの](https://www.sparkpost.com/docs/tech-resources/using-proxy-https-tracking-domain/)記事を参照のこと。
+クリックトラッキングとオープントラッキングにSSLを設定する際に、リストアップされたCDNを使用できない、または使用したくない場合は、カスタムSSL設定を行うことができる。代替 CDN やカスタムプロキシは、より複雑で細かい設定になる可能性があることに注意してください。このトピックについては、[SendGrid](https://sendgrid.com/docs/ui/account-and-settings/custom-ssl-configurations/) および [SparkPost](https://www.sparkpost.com/docs/tech-resources/using-proxy-https-tracking-domain/) の記事を参照してください。
 {% endalert %}
 
 #### その他のリソース
 
 {% alert important %}
-CDNコンフィギュレーションのトラブルシューティングについては、CDNプロバイダーに問い合わせる必要がある。
+CDN の構成のトラブルシューティングについては、CDN プロバイダーに問い合わせる必要があります。
 {% endalert %}
 
 以下の表には、SendGridとSparkPostが書いた、特定のCDNの設定方法に関するステップバイステップのガイドが含まれている。特定のCDNがリストにない場合もあるが、CDNにSSL証明書を適用する機能があることを確認する必要がある。
 
 | SendGrid | SparkPost |
 | -------- | --------- |
-| [AWSクラウドフロント](https://support.sendgrid.com/hc/en-us/articles/4412701748891-How-to-configure-SSL-for-click-tracking-using-CloudFront)<br>[クラウドフレア](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-cloudflare)<br>[迅速に](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-fastly)<br>[キーシーディーエヌ](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-keycdn) | [AWSクラウドフロント](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-aws-cloudfront)<br>[クラウドフレア](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-cloudflare)<br>[クラウドフロント](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/)<br>[迅速に](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-fastly)<br>[グーグル・クラウド・プラットフォーム](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-google-cloud-platform)<br>[マイクロソフト・アジュール](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-microsoft-azure) |
+| [AWS Cloudfront](https://support.sendgrid.com/hc/en-us/articles/4412701748891-How-to-configure-SSL-for-click-tracking-using-CloudFront)<br>[CloudFlare](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-cloudflare)<br>[Fastly](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-fastly)<br>[KeyCDN](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-keycdn) | [AWS Cloudfront](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-aws-cloudfront)<br>[CloudFlare](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-cloudflare)<br>[Cloudfront](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/)<br>[Fastly](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-fastly)<br>[Google Cloud Platform](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-google-cloud-platform)<br>[Microsoft Azure](https://support.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-microsoft-azure) |
 
 #### トラブルシューティング
 
-CDNのコンフィギュレーション、証明書、プロキシの問題はCDNで対処すべきだが、SSLクリックトラッキングのセットアップでよくある問題を特定するのに役立つ一般的なトラブルシューティングのヒントをいくつか紹介しよう。
+CDN の構成、証明書、プロキシの問題は CDN で処理する必要がありますが、SSL のクリック追跡の設定でよくある問題を特定するのに役立つ一般的なトラブルシューティングのヒントをいくつか紹介します。
 
 ##### ドメイン・レジストリの問題
 
-digコマンドは、リンク追跡がCDNに向いているかどうかを教えてくれる。これはターミナルで`dig CNAME link_tracking_subdomain` を実行することで行える。コマンドの実行後、`ANSWER SECTION` 、CNAMEが指す場所がリストされるはずである。CDNではなく、選択したメールサービスプロバイダ（SendGridまたはSparkPost）を指している場合は、CDNを指すようにドメインレジストリを再設定してみてほしい。
+digコマンドは、リンク追跡がCDNに向いているかどうかを教えてくれる。これはターミナルで `dig CNAME link_tracking_subdomain` を実行することで行えます。コマンドの実行後、`ANSWER SECTION` の下に、CNAME がどこを指しているかが表示されます。CDN ではなく、選択したメールサービスプロバイダー (SendGrid または SparkPost) を指している場合は、CDN を指すようにドメインレジストリを再設定してみます。
 
 ##### CDNの問題
 
-ライブEメールのリンクがセットアップ中に壊れ始めた場合、これは一般的に、DNSが適切に設定されていないままCDNに向けられたことを意味する。これは「間違ったリンク」エラーとして表示されることがある。CDNプロバイダーに連絡し、CDN設定のトラブルシューティングに役立つドキュメントを確認する。
+ライブEメールのリンクがセットアップ中に壊れ始めた場合、これは一般的に、DNSが適切に設定されていないままCDNに向けられたことを意味する。これは「間違ったリンク」エラーとして表示されることがある。CDN プロバイダーに連絡し、CDN 構成のトラブルシューティングに役立つドキュメントを確認してください。
 
 ##### SSL有効化ステータス
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/preference_center.md b/_lang/ja/_user_guide/message_building_by_channel/email/preference_center.md
index 5c103c869c6..7d4737f700a 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/preference_center.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/preference_center.md
@@ -1,10 +1,10 @@
 ---
-nav_title: プリファレンス・センター
-article_title: プリファレンス・センター
+nav_title: ユーザー設定センター
+article_title: ユーザー設定センター
 page_order: 8
 layout: dev_guide
-guide_top_header: "プリファレンス・センター"
-guide_top_text: "メールプレファレンスセンターの作成は、ユーザーがメールキャンペーンやニュースレターの通知設定を管理できるようにする簡単な方法である。<a href='/docs/api/endpoints/preference_center/'>Braze Preference Center API</a>またはドラッグアンドドロップエディターでプリファレンスセンターを作成・管理する方法については、以下の記事を参照。"
+guide_top_header: "ユーザー設定センター"
+guide_top_text: "メールユーザー設定センターを作成すると、ユーザーがメールキャンペーンやニュースレターの通知設定を簡単に管理できるようになります。<a href='/docs/api/endpoints/preference_center/'>Braze Preference Center API</a>またはドラッグアンドドロップエディターでプリファレンスセンターを作成・管理する方法については、以下の記事を参照。"
 description: "このランディングページには、BrazeメールプリファレンスセンターとプリファレンスセンターAPIの使用方法に関する記事が含まれている。"
 channel:
   - email
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/templates/html_email_template.md b/_lang/ja/_user_guide/message_building_by_channel/email/templates/html_email_template.md
index 00149ce1c7b..7e31dcabb23 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/templates/html_email_template.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/templates/html_email_template.md
@@ -12,7 +12,7 @@ channel:
 
 # HTMLメールテンプレートをアップロードする
 
-> Brazeのダッシュボードでは、独自のHTMLメールテンプレートをアップロードし、後でキャンペーンに使用するために保存することができる。また、エディターを使って[Eメールテンプレートを作成する]({{site.baseurl}}/user_guide/message_building_by_channel/email/creating_an_email_template/)こともできる。
+> Braze ダッシュボードでは、独自の HTML メールテンプレートをアップロードし、後でキャンペーンに使用するために保存することができます。また、エディターを使って[Eメールテンプレートを作成する]({{site.baseurl}}/user_guide/message_building_by_channel/email/creating_an_email_template/)こともできる。
 
 ## 前提条件 {#upload-requirements}
 
@@ -20,26 +20,26 @@ channel:
 
 * 1つのHTMLファイル-メールの本文
 * HTMLファイルで参照される画像のフォルダ
-* 画像ファイル数50以下
-* 5MB以下であること
+* 画像ファイル数 50 未満
+* 5 MB 未満であること
 
 ## テンプレートをアップロードする
 
-### ステップ 1:Eメールテンプレートエディターに移動する
+### ステップ 1: Eメールテンプレートエディターに移動する
 
-**Templates**>**Email Templatesに**移動する。
+\[**テンプレート**] > \[**メールテンプレート**] に移動します。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合、このページは**エンゲージメント**>**テンプレートとメディア**>**Eメールテンプレートに**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、このページは \[**エンゲージメント**] > \[**テンプレートとメディア**] > \[**メールテンプレート]**にあります。
 {% endalert %}
 
-### ステップ 2:アップローダーを開く
+### ステップ 2: アップローダーを開く
 
-**Template Type**セクションで**HTML Editorを**選択し、**Start from a Basic HTML Template**セクションまでスクロールダウンする。**ファイルから**」を選択する。
+**Template Type**セクションで**HTML Editorを**選択し、**Start from a Basic HTML Template**セクションまでスクロールダウンする。\[**元のファイル**] を選択します。
 
-### ステップ 3:テンプレートをアップロードする
+### ステップ 3: テンプレートをアップロードする
 
-**ファイルからアップロードを**クリックし、コンピューターからテンプレートを選択する。[前提条件の](#upload-requirements)セクションを参照し、テンプレートがアップロード要件を満たしていることを確認する。
+\[**ファイルからアップロード**] をクリックし、コンピューターからテンプレートを選択します。[前提条件](#upload-requirements)のセクションを参照し、テンプレートがアップロード要件を満たしていることを確認します。
 
 #### テンプレートのアップロードエラーのトラブルシューティング
 
@@ -52,11 +52,11 @@ HTMLテンプレートファイルをアップロードする際に、いくつ
 |HTMLの欠落| HTMLファイルをZIPファイルに追加し、再度アップロードを試みる。|
 |複数のHTML| HTMLファイルの1つを削除し、再度アップロードを試みる。|
 |5MB以上の画像| 画像の数を減らして、再度アップロードを試みる。 |
-|おまけの画像| HTMLファイルで参照されていない画像がファイル内にあるかもしれない。これはフェイルエラーにはならないが、余分な画像は破棄される。もしこれらの画像がHTMLファイルで参照されることになっているのであれば、コンテンツをチェックし、エラーがあれば修正して、再度アップロードを試みる。|
-|消えた画像| HTMLファイル内で参照されている画像があるにもかかわらず、それらの画像がZIPファイルのimageフォルダに含まれていない場合、ファイルエラーが発生する。ファイルを確認し、エラー（スペルミスなど）を修正するか、足りない画像をZIPファイルに追加し、再度アップロードを試みる。|
+|おまけの画像| HTMLファイルで参照されていない画像がファイル内にあるかもしれない。これはフェイルエラーにはなりませんが、余分な画像は破棄されます。もしこれらの画像がHTMLファイルで参照されることになっているのであれば、コンテンツをチェックし、エラーがあれば修正して、再度アップロードを試みる。|
+|画像がありません| HTMLファイル内で参照されている画像があるにもかかわらず、それらの画像がZIPファイルのimageフォルダに含まれていない場合、ファイルエラーが発生する。ファイルを確認し、エラー（スペルミスなど）を修正するか、足りない画像をZIPファイルに追加し、再度アップロードを試みる。|
 {: .reset-td-br-1 .reset-td-br-2}
 
-### ステップ 4:テンプレートを完成させて保存する
+### ステップ 4: テンプレートを完成させて保存する
 
 **Save Template（テンプレートの保存）**」をクリックして、必ずテンプレートを保存すること。これで、このテンプレートを任意のキャンペーンやキャンバスで使用する準備が整った！
 
@@ -66,7 +66,7 @@ HTMLテンプレートファイルをアップロードする際に、いくつ
 
 ## APIキャンペーンでテンプレートを使用する {#api_for_upload_email_templates}
 
-APIキャンペーンにメールを使用するには、`email_template_id` 、Brazeで作成したメールテンプレートの一番下にある。
+API キャンペーンでメールを使用するには、`email_template_id` が必要です。これは、Braze で作成されたメールテンプレートの下部にあります。
 
 ![HTMLメールテンプレートのAPI Identifierセクション。][4]
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/templates/link_aliasing.md b/_lang/ja/_user_guide/message_building_by_channel/email/templates/link_aliasing.md
index 39f7e4c4eb4..167aa36d47d 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/templates/link_aliasing.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/templates/link_aliasing.md
@@ -17,38 +17,38 @@ channel:
 
 リンクエイリアスは、Eメールチャンネル内のリンクにブレイズが生成したクエリーパラメーターを装飾することで機能する。リンクエイリアスを作成するには、以下の手順に従う： 
 
-1. メール本文を開く。
-2. **リンク管理**タブをクリックする。
+1. メールの本文を開きます。
+2. \[**リンク管理**] タブをクリックします。
 3. Brazeは、各リンクに固有のデフォルトリンクエイリアスを自動的に生成する。
-4. エイリアスに名前をつける。エイリアスは、メールキャンペーンのバリアントまたはキャンバスのコンポーネントごとに一意に命名する必要がある。 
+4. エイリアスに名前をつける。エイリアスは、メールキャンペーンのバリアントまたはキャンバスのコンポーネントごとに一意の名前にする必要があります。 
 
-また、レポーティングやセグメンテーションを行う際に、特定のリンクを参照するためのエイリアスを設定することもできる。 
+また、レポーティングやセグメンテーションを行う際に、特定のリンクを参照するためのエイリアスを設定することもできます。 
 
 ![][2]
 
-リンクのエイリアシングは、クエリーパラメーターを付加しても安全なHTMLアンカータグ内の`href` 属性でのみサポートされている。Brazeが簡単に`lid` 。`lid` 。この値を追加しないと、Brazeはリンクエイリアス用のURLを認識しない。
+リンクのエイリアシングは、クエリーパラメーターを付加しても安全なHTMLアンカータグ内の`href` 属性でのみサポートされている。Braze が `lid` の値を簡単に追加できるように、リンクの最後に疑問符 (?) を含めることをお勧めします。`lid` 。この値を追加しないと、Brazeはリンクエイリアス用のURLを認識しない。
 
 ### リンクエイリアスを管理する
 
 以下の手順に従って、トラッキングされたリンクのエイリアスをすべて表示する：
 
-1. **ワークスペース設定]の** **\[設定]>**\[**電子メール設定]**に移動する。
-2. **Link Aliasing Settings**タブをクリックする。
+1. \[**設定**] > \[**メール設定**] (\[**ワークスペース設定**] の下) に移動します。
+2. \[**リンクエイリアスの設定**] タブをクリックします。
 
 {% alert important %}
-[古いナビゲーションを]({{site.baseurl}}/user_guide/administrative/access_braze/navigation/)使用している場合、これらの設定は「**設定の管理**」にある。
+[古いナビゲーション]({{site.baseurl}}/user_guide/administrative/access_braze/navigation/)を使用している場合、これらの設定は \[**設定の管理**] にあります。
 {% endalert %}
 
 ここでは、すべてのリンクエイリアスを並べ替えたり検索したりすることもできる。
 
-![キャンバスのステップのアクティブな部分である「test」という名前のリンクエイリアスを示す「Tracked Link Aliases」ページ。][8]
+![キャンバスステップのアクティブな部分である「test」という名前のリンクエイリアスを示す「追跡されたリンクエイリアス」ページ。][8]
 
-#### リンク・エイリアスの追跡を解除する
+#### リンクエイリアスの追跡の解除
 
 **リンクエイリアシング設定**タブでは、リンクエイリアスのトラッキングをオフにすることができる。
 
 1. リンクエイリアスを選択する。
-2. **トラッキングをオフにするを**クリックする。  
+2. \[**追跡をオフにする**] をクリックします。  
 
 #### エイリアスとユーザー・プロフィール・データをリンクする
 
@@ -60,31 +60,31 @@ Brazeは、メール内のリンクを評価し、リンクテンプレートを
 
 リンクエイリアスが有効な場合、メッセージ、コンテンツブロック、リンクテンプレートは変更されない。リンク・テンプレートやコンテンツ・ブロックを使用した既存のメッセージも同じである。しかし、メッセージを更新すると、リンクエイリアスマークアップがすべてのリンクに適用されるため、リンクを表示するにはリンクテンプレートを適用し直す必要がある。
 
-### データを抽出する
+### データの抽出
 
-List link alias for campaign][3] と \[List link alias for Canvas][4] ] エンドポイントを使用して、キャンペーンまたはメール固有のキャンバスコンポーネントの各メッセージバリアントで設定された`alias` を抽出する。
+\###\[List link alias for campaign][3] と \[List link alias for キャンバス][4] エンドポイントを使用して、キャンペーンまたはメール固有のキャンバスコンポーネントの各メッセージバリアントで設定された `alias` を抽出します。
 
 ## コンテンツブロックのリンクエイリアス
 
-新しいコンテンツブロックはリンクが変更され、Brazeは各リンクに`lid={{placeholder}}` 。このプレースホルダーの値は、Eメールメッセージバリアントに挿入されると解決される。
+新しいコンテンツブロックのリンクが変更され、Braze は該当する各リンクに `lid={{placeholder}}` を追加します。このプレースホルダーの値は、Eメールメッセージバリアントに挿入されると解決される。
 
 Brazeがリンクエイリアスを有効にする前に作成された既存のコンテンツブロック内のリンクを修正するには、既存のコンテンツブロックを複製し、複製したコンテンツブロック内のリンクを修正する。
 
-`lid` 値を持たないコンテンツブロックを新しいメッセージに挿入した場合、そのコンテンツブロックからのリンクはエイリアスで追跡されない。新しいコンテンツブロックが「古い」メッセージバリアントに挿入されると、そのメッセージバリアントからのリンクはリンクエイリアスによって認識される。コンテンツブロックからのリンクも認識される。しかし、「古い」コンテンツ・ブロックは「新しい」コンテンツ・ブロックをネストすることはできない。
+`lid` 値を持たないコンテンツブロックを新しいメッセージに挿入した場合、そのコンテンツブロックからのリンクはエイリアスで追跡されない。新しいコンテンツブロックが「古い」メッセージバリアントに挿入されると、そのメッセージバリアントからのリンクはリンクエイリアスによって認識されます。コンテンツブロックからのリンクも認識される。ただし、「古い」コンテントブロックが「新しい」コンテントブロックをネストすることはできません。
 
 {% alert tip %}
-コンテンツブロックについては、既存のコンテンツブロックのコピーを作成し、新しいメッセージで使用することを推奨する。これは、リンクエイリアスが有効になっていないコンテンツブロッ クを新しいメッセージで参照するようなシナリオを防ぐために、一括複 製によって行うことができる。
+Braze では、コンテンツブロックについては、既存のコンテンツブロックのコピーを作成し、新しいメッセージで使用することをお勧めします。これは、新規メッセージ内でリンクエイリアスが有効になっていないコンテンツブロックを参照してしまう可能性を回避するために、一括複製によって行うことができます。
 {% endalert %}
 
 ## 例
 
 以下の表は、Eメール本文のリンクの例、リンクのエイリアシングの結果、リンクのエイリアシングによって元のリンクがどのように更新されるかの説明である。
 
-| メール本文にリンクを貼る | エイリアシング・リンク | ロジック |
+| メール本文にリンクを貼る | エイリアスによるリンク | ロジック |
 |---|---|---|
 | https://www.braze.com | https://www.braze.com?lid=slfdldtqdhdk | Brazeはクエスチョンマーク(?)を挿入し、最初のクエリーパラメーターをURLに追加する。 |
-| https://www.braze.com?utm_campaign=retention&utm_source=email | https://www.braze.com?utm_campaign=retention&utm_source=email&lid=0goty30mviyz | Brazeは他のクエリーパラメーターを検出し、URLの最後に`lid=` 。 |
-| {%raw%}`<a href="{{custom_attribute.{product_url}}}?">`{%endraw%} | {%raw%}`<a href="{{custom_attribute.{product_url}}}?lid=ac7a548g5kl7">`{%endraw%} | BrazeはこれがURLであることを認識し、すでにクエスチョンマーク（?）そして、`lid` クエリーパラメーターをクエスチョンマークの後に追加する。 |
+| https://www.braze.com?utm_campaign=retention&utm_source=email | https://www.braze.com?utm_campaign=retention&utm_source=email&lid=0goty30mviyz | Braze は他のクエリパラメーターを検出し、URL の末尾に `lid=` を追加します。 |
+| {%raw%}`<a href="{{custom_attribute.{product_url}}}?">`{%endraw%} | {%raw%}`<a href="{{custom_attribute.{product_url}}}?lid=ac7a548g5kl7">`{%endraw%} | BrazeはこれがURLであることを認識し、すでにクエスチョンマーク（?）そして、疑問符の後にクエリパラメーター `lid` を追加します。 |
 | https://www.braze.com#bookmark1?utm_source=email | https://www.braze.com?lid=eqslgd5a9m3y#bookmark1?utm_source=email | Brazeは、クエスチョンマーク(?)の後にアンカー(#)がある標準的なURL構造を期待する。Brazeは左から右に読むので、アンカーの前にクエスチョンマークと`lid` 。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
@@ -116,25 +116,25 @@ HTMLまたはコンテンツ・ブロック内の`assign` ステートメント
 
 ## リンクテンプレート
 
-新しいメッセージバリアントには、**リンク管理**タブから既存の[リンクテンプレートを]({{site.baseurl}}/user_guide/message_building_by_channel/email/templates/link_template/)使うことができる。リンク・テンプレートを使って開始されたメッセージには、リンク・テンプレートが適用される。既存のメッセージが変更された場合、リンク**管理**タブからリンクテンプレートを再適用する必要がある。 
+新しいメッセージバリアントには、**リンク管理**タブから既存の[リンクテンプレートを]({{site.baseurl}}/user_guide/message_building_by_channel/email/templates/link_template/)使うことができる。リンクテンプレートを使って開始されたメッセージには、リンクテンプレートが適用されます。既存のメッセージが変更された場合、リンク**管理**タブからリンクテンプレートを再適用する必要がある。 
 
 {% alert note %}
-リンクテンプレートは、**リンク管理**タブに表示されているリンクにのみ適用できる。つまり、"古い "コンテンツブロックやマークアップできないリンクなど、`lid` URLパラメータを持たないリンクは、リンクテンプレートの対象外となる。これを解決するには、"古い "コンテンツブロックをコピーするか、URLの`href` 属性にクエスチョンマーク（？）またはアンパサンド（&）を含めることをお勧めする。
+リンクテンプレートは、**リンク管理**タブに表示されているリンクにのみ適用できる。つまり、"古い "コンテンツブロックやマークアップできないリンクなど、`lid` URLパラメータを持たないリンクは、リンクテンプレートの対象外となる。これを解決するには、「古い」コンテンツブロックをコピーするか、URL の `href` 属性に疑問符 (?) またはアンパサンド （&） を含めることをお勧めします。
 {% endalert %}
 
 ## リンク・セグメンテーション
 
-エイリアスのリターゲティングフィルタは、メールキャンペーンまたはキャンバスコンポーネントのどちらかから特別に追跡されたエイリアスをクリックした顧客に基づいてセグメンテーションフィルタを作成することができる。このフィルターは、追跡されたエイリアスが存在するキャンペーンまたはキャンバスにのみ使用できる。
+エイリアスフィルターのリターゲティングを使用すると、顧客がメールキャンペーンまたはキャンバスコンポーネントのいずれかから特別に追跡されたエイリアスをクリックする行動に基づいて、セグメンテーションフィルターを作成できます。このフィルターは、追跡されたエイリアスが存在するキャンペーンまたはキャンバスにのみ使用できる。
 
 ### トラッキングリンク
 
-**リンク管理]**タブで、セグメンテーションのために "追跡 "し、セグメンテーション・フィルターに存在させたいエイリアスを選択する。追跡されるエイリアスはセグメンテーションのためだけのものであり、あなたのリンクがレポート目的で追跡されることには何の影響もないことに注意されたい。
+\[**リンク管理**] タブで、セグメンテーションのために「追跡」する、セグメンテーションフィルターに含めるエイリアスを選択します。追跡されるエイリアスはセグメンテーションのためだけのものであり、あなたのリンクがレポート目的で追跡されることには何の影響もないことに注意されたい。
 
 {% alert tip %}
 リンクのエンゲージメントの指標を追跡するには、リンクの前にHTTPまたはHTTPSのいずれかがあることを確認する。
 {% endalert %}
 
-Brazeでは、追跡するリンクを無制限に選択することができるが、ユーザーが開いた直近のリンクに限ってリターゲティングすることができる。ユーザーのプロフィールには、最近クリックされた100のリンクが含まれている。例えば、500のリンクを追跡し、ユーザーが500のリンクをすべてクリックした場合、最近クリックされた100のリンクに基づいてリターゲティングやセグメントを作成することができる。
+Brazeでは、追跡するリンクを無制限に選択することができるが、ユーザーが開いた直近のリンクに限ってリターゲティングすることができる。ユーザープロファイルには、最近クリックした 100 個のリンクが含まれています。例えば、500のリンクを追跡し、ユーザーが500のリンクをすべてクリックした場合、最近クリックされた100のリンクに基づいてリターゲティングやセグメントを作成することができる。
 
 {% tabs local %}
 {% tab ドラッグ・アンド・ドロップ・エディター %}
@@ -171,11 +171,11 @@ Brazeは、プロフィールレベルで、過去100回クリックされたリ
 
 #### キャンバスステップでエイリアスをクリック
 
-キャンバスコンポーネントでクリックされた特定のエイリアスに基づき、ユーザーを再ターゲットする。パイプで区切られたフィルターオプションは、CanvasとCanvasコンポーネントを表示し、その後にCanvasコンポーネント内のエイリアスを表示する。ここでは、追跡されたエイリアスを持つキャンバスのステップのみが表示される。
+キャンバスコンポーネントでクリックした特定のエイリアスに基づき、ユーザーをリターゲティングします。パイプ区切りのフィルターオプションは、キャンバスとキャンバスコンポーネントを表示し、その後にキャンバスコンポーネント内のエイリアスを表示します。ここでは、追跡されたエイリアスを持つキャンバスのステップのみが表示される。
 
 #### キャンペーンまたはキャンバスでエイリアスをクリックした
 
-キャンペーンまたはキャンバスコンポーネントでクリックされたエイリアスに基づき、ユーザーをリターゲティングする。エイリアスは「グローバル」と見なされるため、グローバルエイリアスはすべてのキャンペーンとキャンバスのステップからのリンククリックをターゲットにする。
+キャンペーンまたはキャンバスコンポーネントでクリックした任意のエイリアスに基づき、ユーザーをリターゲティングします。エイリアスは「グローバル」と見なされるため、グローバルエイリアスはすべてのキャンペーンとキャンバスのステップからのリンククリックをターゲットにする。
 
 ![][5]
 
@@ -187,7 +187,7 @@ Brazeは、プロフィールレベルで、過去100回クリックされたリ
 
 ### 電子メールのクリック・イベント
 
-email clicks イベント][7] は、ユーザーがEメールをクリックしたときに発生する。ユーザーがメールを複数回クリックしたり、メール内の異なるリンクをクリックしたりすると、同じキャンペーンについて複数のイベントが生成される場合があります。リンクエイリアスが有効な場合、Eメールクリックイベントに2つの追加フィールドがある：`link_id` と`link_alias` 。
+\[メールクリック数イベント][7] は、ユーザーがメールをクリックしたときに発生します。ユーザーがメールを複数回クリックしたり、メール内の異なるリンクをクリックしたりすると、同じキャンペーンについて複数のイベントが生成される場合があります。リンクエイリアスが有効な場合、Eメールクリックイベントに2つの追加フィールドがある：`link_id` と`link_alias` 。
 
 ```json
 // Email Click: users.messages.email.Click
@@ -221,7 +221,7 @@ email clicks イベント][7] は、ユーザーがEメールをクリックし
 {% alert update %}
 Brazeはキャンバスのステップ（スケジュール可能なエントリーステップを除く）を、たとえ「スケジュール」されていても、トリガーされたイベントとして扱うため、`dispatch_id` の動作はキャンバスとキャンペーンで異なる。Canvasとキャンペーンにおける[`dispatch_id` 行動について]({{site.baseurl}}/help/help_articles/data/dispatch_id/)詳しく知る。
 
-_更新は2019年8月に行われる。_
+_更新は 2019 年 8 月に記録されました。_
 {% endalert %}
 
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/templates/link_template.md b/_lang/ja/_user_guide/message_building_by_channel/email/templates/link_template.md
index 8a7fd02e286..bfd197e54ab 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/templates/link_template.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/templates/link_template.md
@@ -29,11 +29,11 @@ channel:
 
 リンクテンプレートは無制限に作成でき、様々なニーズに対応できる。リンクテンプレートを作成する：
 
-1. **Templates**>**Email Link Templatesに**進む。 
-2. **リンクテンプレートの作成**」をクリックする。
+1. \[**テンプレート**] > \[**メールリンクテンプレート**] に移動します。 
+2. \[**リンクテンプレートの作成**] をクリックします。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合、このページは**エンゲージメント**＞**テンプレート＆メディア**＞**リンクテンプレートに**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、このページは \[**エンゲージメント**] > \[**テンプレートとメディア**] > \[**リンクテンプレート**] にあります。
 {% endalert %}
 
 作成できるリンクテンプレートには2種類ある：
@@ -41,19 +41,19 @@ channel:
 - [URLの前に挿入するリンクテンプレート](#prepend-link-template)
 - [URLの後に挿入するリンクテンプレート](#append-link-template)
 
-リンクテンプレートと[Liquidを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/)使用する場合、一貫したレンダリングを保証するために、Liquidはbodyタグ内にのみ追加されなければならない。
+リンクテンプレートと [Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/) を使用する場合、一貫したレンダリングを保証するために、Liquid は body タグ内にのみ追加する必要があります。
 
-### プリペンドする：URLの前に挿入するリンクテンプレートを作成する {#prepend-link-template}
+### 先頭に追加: URLの前に挿入するリンクテンプレートを作成する {#prepend-link-template}
 
 メールメッセージのリンクの前に文字列やURLを追加したい場合は、新しいリンクテンプレートを作成し、「**テンプレートの位置**」を「**URLの前**」に設定する。次に、URLの前に常に付加される文字列を入力する。 
 
-挿入プロセスの例を示すために、プレビュー・セクションが用意されている。
+挿入プロセスの例を示すプレビューセクションが提供されます。
 
 ![URLの前にリンクテンプレートを挿入する際の「テンプレートの位置」、「URLのプリペンド」、「テンプレートのプレビュー」フィールド。]({% image_buster /assets/img_archive/link_template_preappend.png %}){: style="max-width:90%;"}
 
-### 追加する：URLの後に挿入するリンクテンプレートを作成する {#append-link-template}
+### 追加: URLの後に挿入するリンクテンプレートを作成する {#append-link-template}
 
-メールメッセージのURLの後にクエリパラメータを追加したい場合は、新しいリンクテンプレートを作成し、「**Template Position**」を「**After URL**」に設定する。次に、各URLの末尾にクエリーパラメーター（`value=something` ）を入力する。
+メールメッセージのURLの後にクエリパラメータを追加したい場合は、新しいリンクテンプレートを作成し、「**Template Position**」を「**After URL**」に設定する。次に、各 URL の末尾にクエリパラメーター (`value=something`) を入力します。
 
 URLの末尾に複数のパラメーターを付加することができる。
 
@@ -63,13 +63,13 @@ URLの末尾に複数のパラメーターを付加することができる。
 
 リンクテンプレートの設定が完了したら、メールで使用するテンプレートを選択することができる。
 
-- **HTMLエディター：****コンテンツ・**セクションの**リンク管理**タブに行く。**リンクテンプレートの追加を**クリックし、リンクテンプレートを選択し、**追加を**クリックする。
+- **HTMLエディター：**\[**コンテンツ**] セクションの \[**リンク管理**] タブに移動します。**リンクテンプレートの追加を**クリックし、リンクテンプレートを選択し、**追加を**クリックする。
 
 {% alert important %}
 更新されたHTMLメールエディターで**リンク管理**タブにアクセスするには、リンクエイリアスをオンにしておく必要がある。リンクエイリアスを有効にするには、アカウントマネージャーに連絡する。
 {% endalert %}
 
-- **ドラッグ＆ドロップ・エディター：****コンテンツ**＞**リンク管理**タブを選択する。**リンクテンプレートの追加を**クリックする。ドラッグ＆ドロップ・エディターでリンクテンプレートにアクセスするには、[リンクのエイリアシングを]({{site.baseurl}}/user_guide/message_building_by_channel/email/templates/link_aliasing/)オンにしておく必要がある。
+- **ドラッグ＆ドロップ・エディター：****コンテンツ**＞**リンク管理**タブを選択する。\[**リンクテンプレートを追加**] をクリックします。ドラッグ＆ドロップ・エディターでリンクテンプレートにアクセスするには、[リンクのエイリアシングを]({{site.baseurl}}/user_guide/message_building_by_channel/email/templates/link_aliasing/)オンにしておく必要がある。
 
 ![ドラッグ・アンド・ドロップ・エディターの「リンク管理」タブには、リンク・テンプレートの例がリストアップされている。][1]
 
@@ -80,7 +80,7 @@ URLの末尾に複数のパラメーターを付加することができる。
 リンクテンプレートを[複製する]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/duplicate/)こともできる。テンプレートとクリエイティブ・コンテンツの作成と管理については、「[テンプレートとメディア]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/)」をご覧ください。
 
 {% alert important %}
-テンプレートのアーカイブは、現在リンクテンプレートでは利用できない。
+テンプレートのアーカイブは、現在リンクテンプレートでは利用できません。
 {% endalert %}
 
 ## よくある質問
diff --git a/_lang/ja/_user_guide/message_building_by_channel/email/transactional_message_api_campaign.md b/_lang/ja/_user_guide/message_building_by_channel/email/transactional_message_api_campaign.md
index 403ab9bc117..3726010c46e 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/email/transactional_message_api_campaign.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/email/transactional_message_api_campaign.md
@@ -1,9 +1,9 @@
 ---
-nav_title: アクション通過メールキャンペーン
-article_title: アクション通過メールキャンペーン
+nav_title: トランザクションメールキャンペーン
+article_title: トランザクションメールキャンペーン
 page_order: 10
 
-description: "このリファレンス記事では、新しいBraze Trans アクション アルメールキャンペーンを作成および設定する方法について説明します。"
+description: "この記事では、新しい Braze トランザクションメールキャンペーンを作成して設定する方法を説明します。"
 page_type: reference
 tool:
   - Campaigns
@@ -12,44 +12,44 @@ alias: "/api/api_campaigns/transactional_campaigns"
 
 ---
 
-# アクション間の電子メールキャンペーン
+# トランザクションメールキャンペーン
 
-> Braze Trans アクション al E メールは、送信者と受信者間で合意されたトランスアクションを容易にするために送信されます。このリファレンス記事では、Braze ダッシュボードでtrans アクション al メール キャンペーンを作成し、[`/transactional/v1/campaigns/{campaign_id}/send` エンドポイント]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_transactional_message) のAPI コールに含める`campaign_id` を生成する方法について説明します。
+> Braze トランザクションメールは、送信者と受信者間で合意されたトランザクションを円滑に進めるために送信されます。この記事では、Braze ダッシュボードでトランザクションメールキャンペーンを作成し、[`/transactional/v1/campaigns/{campaign_id}/send` エンドポイント]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_transactional_message)の API 呼び出しに含める`campaign_id` を生成する方法について説明します。
 
 {% alert important %}
-Braze Trans アクション アルメールは、一部のBrazeの一部としてのみ利用可能です。詳しくは、Braze 顧客のサクセスマネージャーに到達するか、[サポートチケット]({{site.baseurl}}/braze_support/)を開封してください。
+Braze トランザクションメールは、一部の Braze パッケージのみで利用できます。詳しくは、Braze 顧客のサクセスマネージャーに到達するか、[サポートチケット]({{site.baseurl}}/braze_support/)を開封してください。
 {% endalert %}
 
-trans アクション al メール キャンペーン型は、お客様と顧客との間で合意されたやり取りを容易にするために、自動化された非プロモーションメールを送信する目的で構築されています。これには以下のような情報が含まれます。
+トランザクションメールキャンペーンのタイプは、お客様とその顧客との間で合意されたトランザクションを円滑に進めるために、自動化された非プロモーションメールを送信する目的で構築されています。これには以下のような情報が含まれます。
 
 - 注文確認
 - パスワードのリセット
 - 請求アラート
-- 出荷警告
+- 出荷のアラート
 
-つまり、trans アクション al メール s を使用して、スピードが最も重要な単一のユーザーに対して、サービスから発信されるビジネスクリティカルな通知s を送信できます。 
+つまり、トランザクションメールを使用して、スピードが特に重要な 1 人のユーザーに対して、サービスから発信されるビジネスクリティカルな通知を送信できます。 
 
 {% alert important %}
-Trans アクション al メール は、Trans アクション al キャンペーン s とは異なり、追加費用なしでユーザー s を対象とすることができます。たとえば、Trans アクション al キャンペーン s には、ユーザーがカートにアイテムを追加した後に送信されるメッセージを含めることができます。詳細については、[オーディエンスターゲットオプション]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)を参照してください。
+トランザクションメールは、トランザクションキャンペーンとは異なり、追加費用なしでユーザーをターゲットとすることができます。例えば、トランザクションキャンペーンには、ユーザーがカートにアイテムを追加した後に送信されるメッセージを含めることができます。詳細については、[オーディエンスターゲットオプション]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)を参照してください。
 {% endalert %}
 
-## ステップ 1:新しいキャンペーンを作成する
+## ステップ 1: 新しいキャンペーンを作成する
 
-新しいトランスアクションのすべてのメール キャンペーンを作成するには、キャンペーンを作成し、**Trans al メール**をメッセージング チャネルとして選択します。
+新しいトランザクションのすべてのメールキャンペーンを作成するには、キャンペーンを作成し、メッセージングチャネルとして \[**トランザクションメール**] を選択します。
 
-![「キャンペーンの作成」ドロップダウンで、トランスアクション al メールの選択肢が強調表示されます。][1]{: style="float:right;max-width:30%;margin-left:15px;"}
+![トランザクションメールの選択肢が強調表示された \[キャンペーンの作成] ドロップダウン。][1]{: style="float:right;max-width:30%;margin-left:15px;"}
 
 これで、トランスアクションのすべてのメール キャンペーンの設定に進むことができます。
 
-## ステップ 2:キャンペーンの設定
+## ステップ 2: キャンペーンの設定
 
 トランザクションアクション メール キャンペーンs のキャンペーン作成フローは、[標準メール キャンペーン]({{site.baseurl}}/user_guide/message_building_by_channel/email/html_editor/creating_an_email_campaign/) と比較して簡略化されており、ビジネスクリティカルなトランザクションアクション メールがすべてのユーザーs に到達できるようになっています。
 
 そのため、他のBraze キャンペーンタイプに精通している設定が、このキャンペーンタイプを設定する際に必要とされない場合があります。
 
-- **Delivery**ステップが簡略化され、スケジュールオプションが削除されました。Trans アクション al メール s は、**Delivery** ページに表示されているキャンペーン ID を使用して、Braze REST API からトリガーされます。再適格性コントロールs やフリークエンシーキャップ 設定s などの追加の設定s も削除され、サービストリガーがリクエストを送信したときに、これらの重要なトランスアクションアラートに対してすべてのユーザーが到達可能であることが確認されました。
-- **Target Users**ステップが削除されました。trans アクション al メール はユーザー群全体を適格(配信停止 d ユーザー s を含む)として登録するため、フィルター s またはSegment s を指定する必要はありません。そのため、このメッセージを受信する必要のあるユーザにアプリするロジックがある場合は、そのロジックをアプリにしてから、特定のユーザーにメッセージをトリガーするようにAPI リクエストをBrazeするかどうかを決定することをお勧めします。
-- **コンバージョン**ステップが削除されました。Trans アクション al メール s は現時点ではコンバージョンイベント "トラッキング に対応していません。
+- **Delivery**ステップが簡略化され、スケジュールオプションが削除されました。トランザクションメールは、\[**配信**] ページに表示されているキャンペーン ID を使用して、Braze REST API 経由でトリガーされます。再適格性コントロールやフリークエンシーキャップ設定などの追加の設定も削除され、サービストリガーがリクエストを送信したときに、これらの重要なトランザクションアラートがすべてのユーザーにリーチできるようにします。
+- **Target Users**ステップが削除されました。トランザクションメールはユーザー群全体を適格 (配信停止ユーザーを含む) として登録するので、フィルターやセグメントを指定する必要はありません。そのため、このメッセージを受信する必要のあるユーザーに適用するロジックがある場合、まずそのロジックを適用してから、特定のユーザーへのメッセージをトリガーする API リクエストを Braze に送信するかどうかを決定することをお勧めします。
+- **コンバージョン**ステップが削除されました。トランザクションメールは現時点ではコンバージョンイベントの追跡に対応していません。
 
 ![トランスアクションの電子メールキャンペーンを作成するためのコンポーズ、配信、および確認ワークフロー。][2]
 
@@ -57,20 +57,20 @@ Trans アクション al メール は、Trans アクション al キャンペ
 
 1. メッセージを送信した後、**Campaigns** ページで結果を確認できるように、説明的な名前を追加します。
 2. メールを作成するか、テンプレートから選択します。
-3. `campaign_id` を書き留めます。API キャンペーンを保存した後、[Trans アクション al E メールエンドポイント]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_transactional_message) の記事に記載されているAPI リクエストに、生成された`campaign_id` フィールドs を含める必要があります。
+3. `campaign_id` を書き留めます。API キャンペーンを保存した後、[トランザクションメールエンドポイント]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_transactional_message)の記事に記載されているように、生成された `campaign_id` フィールドを API リクエストに含める必要があります。
 4. **キャンペーンを保存**をクリックすると、API キャンペーンを開始するように設定されます!
 
 {% alert note %}
-ワンクリックリスト-配信停止 設定trans アクション al メール キャンペーン s デフォルト s to **他のメール キャンペーン s と同様にワークスペース デフォルト** を使用します。これはトランスアクションのメッセージングを対象としているため、Braze はワンクリック配信停止を追加しません。このキャンペーンにワンクリック配信停止を追加するには、[この設定]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#message-level-one-click-list-unsubscribe)を**送信情報**で編集します。
+トランザクションメールキャンペーンのワンクリックのリスト配信停止設定は、デフォルトでは、他のメールキャンペーンと同様に**ワークスペースのデフォルトを使用する**に設定されます。これはトランザクションメッセージングを対象とするため、Braze はワンクリック配信停止を追加しません。このキャンペーンタイプにワンクリック配信停止を追加するには、\[**送信情報**] の[この設定を編集]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#message-level-one-click-list-unsubscribe)します。
 {% endalert %}
 
-### trans アクション al メール s で禁止されたタグs
+### トランザクションメールで禁止されているタグ
 
-`Connected Content`および`Promotion Code`流動タグsは、trans アクション al メール キャンペーン s内では使用できません。
+`Connected Content` および `Promotion Code` の Liquid タグは、トランザクションメールキャンペーン内で使用できません。
 
-`Connected Content`タグを使用すると、送信プロセス中に送信APIリクエストを行うためのBrazeが必要になります。これにより、リクエストした外部サービスに遅延が発生している場合に、メッセージ送信プロセスが遅くなる可能性があります。同様に、`Promotion Code`タグは、Brazeがプロモーションの有効性を評価するために追加の処理を実行することを要求します。これは、送信処理が利用できない場合には、送信処理が遅くなる可能性があります。
+`Connected Content` タグを使用すると、送信プロセス中にアウトバウンド API リクエストを行うための Braze が必要になります。これにより、リクエストした外部サービスに遅延が発生している場合、メッセージ送信プロセスが遅くなる可能性があります。同様に、`Promotion Code` タグは、Braze がプロモーションの有効性を評価するために追加の処理を実行することを要求します。したがって、送信処理が利用できない場合には、処理が遅くなる可能性があります。
 
-そのため、trans アクション al メール キャンペーンのフィールドに`Connected Content` または`Promotion Code` タグ s を含めることはできません。
+そのため、トランザクションメールキャンペーンのフィールドに `Connected Content` タグや `Promotion Code` タグを含めることはできません。
 
 
 [1]: {% image_buster /assets/img/transactional_email_campaign.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/best_practices/prep_guide.md b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/best_practices/prep_guide.md
index 91d129f4b29..dfc1aa1c27f 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/best_practices/prep_guide.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/best_practices/prep_guide.md
@@ -11,30 +11,30 @@ channel: in-app messages
 
 # アプリ内メッセージ準備ガイド
 
-> アプリ内メッセージを作成する前に、メッセージの作成を迅速かつ簡単にするために、次のトピックのいくつかを考慮する必要があります。
+> アプリ内メッセージを作成する前に、以下のトピックを考慮する必要があります。そうすることでメッセージの作成が迅速かつ容易になります。
 
 ## 一般的な考慮事項
 
 - キャンペーンを作成する場合、このメッセージのバリアントをいくつ表示しますか？バリアントテストのアイデアについては、[さまざまなチャネルのヒント]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign/#tips-different-channels)をチェックしてください。
 - キャンバスを構築している場合、そのメッセージはそのステップで他のメッセージングチャネルとペアになりますか？
-- いつ[メッセージを期限切れにしたいですか]({{site.baseurl}}/canvas_in-app_messages/)？
+- [メッセージをいつ期限切れにしますか]({{site.baseurl}}/canvas_in-app_messages/)?
 
-## ターゲティングの考慮事項
+## ターゲット設定の考慮事項
 
-- アプリ内メッセージは、定期的にアプリを訪れるユーザーに最適です。このオーディエンスを含めていますか？
-- あなたのメッセージをユーザーにどこで見せたいですか？あなたのWebアプリで？あなたのモバイルアプリで？
+- アプリ内メッセージは、定期的にアプリを訪れるユーザーに最適です。このオーディエンスを含めますか?
+- あなたのメッセージをユーザーにどこで見せたいですか？貴社の Webアプリで表示しますか?貴社のモバイルアプリで表示しますか?
 - どのイベントがこのメッセージをトリガーする必要がありますか？
-- あなたのユーザーの中に、古いバージョンのアプリを使用している人はいますか？もしそうなら、彼らはあなたのメッセージのいくつかの要素を見ることができないかもしれません。
-- どの種類のデバイスまたはデバイスをこのメッセージのために構築していますか？覚えておいてください、メッセージは**プレビュー**ボックスまたは**テスト**タブを使用してプレビューできます。詳細については[テスト]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/testing/)を参照してください。
+- ユーザーの中に、古いバージョンのアプリを使用している人はいますか?もしそうなら、彼らはあなたのメッセージのいくつかの要素を見ることができないかもしれません。
+- このメッセージはどのタイプのデバイス用に作成しますか?覚えておいてください、メッセージは**プレビュー**ボックスまたは**テスト**タブを使用してプレビューできます。詳細については[テスト]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/testing/)を参照してください。
 
 ## コンテンツの考慮事項
 
 - このメッセージで使用する言語は何ですか？
-- ヘッダーと本文コピーは何ですか？それらはあなたのユーザーにとって目を引くものであり、関連性がありますか？
+- ヘッダーと本文コピーは何ですか?それらはあなたのユーザーにとって目を引くものであり、関連性がありますか？
 - アプリ内メッセージは、設定された時間だけ表示されます。あなたのコピーは簡潔で記憶に残るものですか？
 - カスタムコピーを追加するために[Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/using_liquid/)を使用しますか？
 - 全画面アプリ内メッセージの場合、画像やその他のメディアは[安全ゾーン]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen/#image-safe-zone)内にありますか？
-- アプリ内メッセージの調査では、属性または送信を記録しますか？確認ページを設定しましたか？
+- アプリ内メッセージの調査では、属性または送信を記録しますか?確認ページを設定しましたか？
 
 ## コンバージョンの考慮事項
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen.md b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen.md
index 839d8e71726..186a9f754a9 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/creative_details/fullscreen.md
@@ -30,9 +30,9 @@ tool:
 
 ## 画像
 
-フルスクリーンのアプリ内メッセージは、デバイスの高さいっぱいに表示され、必要に応じて水平方向（左右）にクロップされる。画像とテキストのフルスクリーンメッセージは、デバイスの高さの50％を埋める。ノッチ付き」デバイスでは、アプリ内のフルスクリーンメッセージがすべてステータスバーを埋める。
+全画面のアプリ内メッセージは、デバイスの高さいっぱいに表示され、必要に応じて水平方向 (左右) にクロップされます。画像とテキストのフルスクリーンメッセージは、デバイスの高さの50％を埋める。ノッチ付き」デバイスでは、アプリ内のフルスクリーンメッセージがすべてステータスバーを埋める。
 
-- すべての画像は5MB以下でなければならない。
+- すべての画像は 5 MB 以下でなければなりません。
 - ファイル形式はPNG、JPEG、[GIFのみ]({{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/customization/gifs#gifs)受け付ける。
 - 画像は500KBを推奨する。
 
@@ -42,23 +42,23 @@ tool:
 
 | レイアウト | 資産規模 | 注釈 |
 |--- | --- | --- |
-| 画像とテキスト | アスペクト比6:5<br> 高解像度 1200 x 1000 px<br> 最小600 x 500 px | トリミングは四方で可能だが、画像は常にビューポートの上部50％を埋める。 |
-| 画像のみ | 3:5のアスペクト比<br> 高解像度 1200 x 2000 px<br> 最小600 x 1000 px | 背の高いデバイスでは、左右の端でクロッピングが発生することがある。 |
+| 画像とテキスト | アスペクト比6:5<br> 高解像度 1200 x 1000 px<br> 600 x 500 px 以上 | 四方がトリミングされる可能性がありますが、画像は常にビューポートの上部 50% を占めます。 |
+| 画像のみ | アスペクト比 3:5<br> 高解像度 1200 x 2000 px<br> 600 x 1000 px 以上 | 背の高いデバイスでは、左右の端でクロッピングが発生することがある。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ### 景観
 
 | レイアウト | 資産規模 | 注釈 |
 |--- | --- | --- |
-| 画像とテキスト | アスペクト比10:3<br> 高解像度 2000 x 600px<br> 最小1000 x 300 px | トリミングは四方で可能だが、画像は常にビューポートの上部50％を埋める。 |
-| 画像のみ | アスペクト比5:3<br> 高解像度 2000 x 1200px<br> 最小1000 x 600 px | 背の高いデバイスでは、左右の端でクロッピングが発生することがある。 |
+| 画像とテキスト | アスペクト比10:3<br> 高解像度 2000 x 600px<br> 1000 x 300 px 以上 | 四方がトリミングされる可能性がありますが、画像は常にビューポートの上部 50% を占めます。 |
+| 画像のみ | アスペクト比5:3<br> 高解像度 2000 x 1200px<br> 1000 x 600 px 以上 | 背の高いデバイスでは、左右の端でクロッピングが発生することがある。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-### 画像の安全地帯
+### 画像セーフゾーン
 
 Brazeプラットフォームでフルスクリーンのアプリ内メッセージをプレビューする際、デバイス間で表示される際にトリミングから保護されるメッセージの領域に対して、イメージセーフゾーンを有効にすることができる。プレビューペインでイメージセーフゾーンをテストするだけでなく、いつも通り[メッセージをテスト]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/testing/)することをお勧めする。
 
-![画像セーフゾーンを表示」を有効にしたBrazeで、アプリ内メッセージをプレビューする。画像のセーフゾーンは、画像のどの部分が切り抜きから保護されるかを視覚化する画像上のオーバーレイである。]\[3c]
+![「画像セーフゾーンを表示」を有効にした Braze で、アプリ内メッセージをプレビュー。画像のセーフゾーンは、画像のどの部分が切り抜きから保護されるかを視覚化する画像上のオーバーレイである。]\[3c]
 
 ## 大型スクリーン
 
@@ -67,12 +67,12 @@ Brazeプラットフォームでフルスクリーンのアプリ内メッセー
 {% tabs %}
 {% tab ポートレート %}
 
-![縦向きの大画面で表示されるフルスクリーンのアプリ内メッセージ。]({% image_buster /assets/img/full-screen-large-viewport.png %}){: style="border:none;display:block;margin-left:auto;margin-right:auto"}
+![縦向きの大画面で表示されるフルスクリーンのアプリ内メッセージ。メッセージは、画面中央に配置される大きなモーダルとして表示されます。]({% image_buster /assets/img/full-screen-large-viewport.png %}){: style="border:none;display:block;margin-left:auto;margin-right:auto"}
 
 {% endtab %}
 {% tab 景観 %}
 
-![横向きの大画面で表示されるフルスクリーンのアプリ内メッセージ。]({% image_buster /assets/img/full-screen-large-viewport-landscape.png %}){: style="max-width:80%;border:none;display:block;margin-left:auto;margin-right:auto"}
+![横向きの大画面で表示されるフルスクリーンのアプリ内メッセージ。メッセージは、画面中央に配置される大きなモーダルとして表示されます。]({% image_buster /assets/img/full-screen-large-viewport-landscape.png %}){: style="max-width:80%;border:none;display:block;margin-left:auto;margin-right:auto"}
 
 {% endtab %}
 {% endtabs %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/creative_details/modal.md b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/creative_details/modal.md
index 3f378893e52..9c275bcd8b1 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/creative_details/modal.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/creative_details/modal.md
@@ -10,11 +10,11 @@ description: "この記事では、モーダルのアプリ内メッセージの
 
 ---
 
-# アプリ内モーダルメッセージ
+# モーダルのアプリ内メッセージ
 
 > モーダルは、デバイスの画面の中央に表示され、アプリのバックグラウンドから目立つように画面オーバーレイが表示されます。これらは、ユーザーにセールやプレゼントを利用するようにそれとなく提案するのに最適です。
 
-![並んだ2つのモーダルインアプリメッセージ、画像とテキストの推奨事項を詳述しています。詳細については、次のセクションを参照してください。]\[1a]{: style="max-width: 801px; border: none;"}
+![画像とテキストの推奨事項が詳細を含む、2 つのモーダルアプリ内メッセージを並べて表示したところ。詳細については、次のセクションを参照してください。]\[1a]{: style="max-width: 801px; border: none;"}
 
 ## 画像の仕様
 
@@ -22,9 +22,9 @@ description: "この記事では、モーダルのアプリ内メッセージの
 
 ## より大きな画面
 
-タブレットやデスクトップブラウザでは、モーダルアプリ内メッセージは、次のスクリーンショットに示されているように、アプリ画面の中央に表示されます。
+タブレットやデスクトップブラウザでは、次のスクリーンショットのように、モーダルアプリ内メッセージがアプリ画面の中央に表示されます。
 
-![モーダルアプリ内メッセージが大画面に表示される様子。同様に電話の画面に、メッセージは画面の中央にあります。]\[1b]{: style="max-width: 800px; border: none;"}
+![大画面に表示されたモーダルアプリ内メッセージ。同様に電話の画面に、メッセージは画面の中央にあります。]\[1b]{: style="max-width: 800px; border: none;"}
 
 \[1a]: {% image_buster /assets/img/modal-spec.png %}
 \[1b]: {% image_buster /assets/img/modal-large-viewport.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create.md b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create.md
index 0c56fb2e31c..a7e42cf51bd 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create.md
@@ -17,7 +17,7 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 
 既存のカスタムHTMLテンプレートやサードパーティが作成したテンプレートを使用したい場合は、ドラッグアンドドロップエディタで再作成する必要があります。
 
-アプリ内メッセージはキャンペーンを使用して送信するべきか[キャンバス]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/in-app_messages_in_canvas/)を使用するべきか分からない場合は？キャンペーンは単一のシンプルなメッセージングキャンペーンに適していますが、キャンバスはマルチステップのユーザーのジャーニーに適しています。メッセージを作成する場所を選択したら、ドラッグアンドドロップでアプリ内メッセージを作成する手順に進みましょう。
+アプリ内メッセージはキャンペーンを使用して送信するべきか[キャンバス]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/in-app_messages_in_canvas/)を使用するべきか分からない場合は？キャンペーンは単一のシンプルなメッセージングキャンペーンに適していますが、キャンバスはマルチステップのユーザーのジャーニーに適しています。メッセージを作成する場所を選択したら、次のステップに進み、ドラッグ＆ドロップでアプリ内メッセージを作成します。
 
 ## 前提条件
 
@@ -28,7 +28,7 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 | {::nomarkdown}{% sdk_min_versions swift:5.0.0 android:8.0.0 web:2.5.0 %}{:/} | {::nomarkdown}{% sdk_min_versions swift:6.5.0 android:26.0.0 web:4.8.1 %}{:/} |
 {: .reset-td-br-1 .reset-td-br-2}
 
-{% details 最小SDKに関する詳細情報 %}
+{% details 最小 SDK に関する詳細情報 %}
 
 ドラッグアンドドロップエディタを使用して作成されたメッセージは、最小SDKバージョンのユーザーにのみ送信できます（上記の表を参照）。ユーザーがアプリケーションを更新していない場合（つまり、古いSDKバージョンを使用している場合）、アプリ内メッセージを受信しません。
 
@@ -37,9 +37,9 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 - メッセージを閉じないテキストリンク
 - プッシュプライマーを要求するためのボタンアクション
 
-次に、これらの機能の個々の最小SDK要件を示します。
+以下に、これらの機能に関する個々の最小 SDK 要件の概要を示します。
 
-| テキストリンク*                                                         | プッシュプライマーをリクエスト                                                           |
+| テキストリンク*                                                         | プッシュプライマーのリクエスト                                                           |
 | ------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
 | {::nomarkdown}{% sdk_min_versions swift:6.2.0 android:26.0.0 %}{:/} | {::nomarkdown}{% sdk_min_versions web:4.8.1 swift:6.5.0 android:26.0.0 %}{:/} |
 {: .reset-td-br-1 .reset-td-br-2}
@@ -51,13 +51,13 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 ### 追加の前提条件
 
 - Web SDKの場合、初期化オプション[`allowUserSuppliedJavascript`](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#initializationoptions)を`true`に設定する必要があります。`enableHtmlInAppMessages`オプションでもこれらのメッセージを機能させることができますが、非推奨であり、`allowUserSuppliedJavascript`に更新する必要があります。
-- Google Tag Managerを使用している場合は、GTM構成で「HTMLインアプリメッセージを許可」を有効にする必要があります。
+- Google Tag Manager を使用している場合は、GTM の構成で「Allow HTML In-App Messages」を有効にする必要があります。
 
-## ステップ 1:アプリ内メッセージを作成する
+## ステップ 1: アプリ内メッセージを作成する
 
 新しいアプリ内メッセージまたはキャンバスステップを作成し、編集体験として**ドラッグアンドドロップエディター**を選択します。
 
-## ステップ 2:テンプレートを選択してください
+## ステップ 2: テンプレートを選択してください
 
 ドラッグアンドドロップエディタを編集体験として選択した後、次のことができます:
 
@@ -65,13 +65,13 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 - Brazeのドラッグアンドドロップアプリ内メッセージテンプレートを使用する
 - 保存されたドラッグアンドドロップのアプリ内メッセージテンプレートを選択
 
-**メッセージを作成**をクリックして、ドラッグアンドドロップエディタでアプリ内メッセージのデザインを開始します。
+\[**メッセージを作成**] をクリックして、ドラッグ＆ドロップエディターでアプリ内メッセージのデザインを開始します。
 
 ![]({% image_buster /assets/img_archive/dnd_iam_select_template.png %}){: style="max-width:75%"}
 
 ダッシュボードの**テンプレート**セクションからすべてのテンプレートにアクセスすることもできます。
 
-## ステップ 3:追加のページを追加する（オプション） {#multi-page}
+## ステップ 3: 追加のページを追加する（オプション） {#multi-page}
 
 アプリ内メッセージにページを追加すると、オンボーディングフローやウェルカムジャーニーのように、ユーザーを順次のフローに案内できます。**ページ**セクションの**ビルド**タブからページを管理できます。
 
@@ -82,7 +82,7 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 
 アプリ内メッセージはデフォルトで1ページから始まります。新しいページを追加するには:
 
-1. **「+ ページを追加」**をクリックします。
+1. \[**\+ ページを追加**] をクリックします。
 2. カスタムまたはBraze提供のテンプレートから選択します。
 3. ページに意味のある名前を付けてください。これは、ページをつなぐときに役立ちます。
 
@@ -90,10 +90,10 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 アプリ内メッセージごとに最大10ページ追加できます。
 {% endalert %}
 
-既存のページを複製するには:
+既存のページを複製するには: 
 
 1. リスト内のページにカーソルを合わせて<i class="fas fa-ellipsis-vertical"></i>を選択し、さらにオプションを開封します。
-2. **複製**をクリックします。
+2. \[**複製**] をクリックします。
 3. ページに意味のある名前を付けてください。これは、ページをつなぐときに役立ちます。
 
 {% endtab %}
@@ -107,9 +107,9 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 {% endtab %}
 {% endtabs %}
 
-### ステップ 3a:ページを接続する
+### ステップ 3a: ページを接続する
 
-マルチページのイン{アプリ}メッセージは順次的であり、ユーザーは次のページに進むためにタップまたはクリックしてメッセージと対話します。
+複数ページのアプリ内メッセージはシーケンシャルです。したがって、ユーザーがアプリをタップするかクリックすると、フロー内の次のページに移動します。
 
 ページを接続するには:
 
@@ -127,9 +127,9 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 ユーザーはいつでもメッセージを終了するために閉じるXボタンを押すことができます。このボタンは削除できません。
 {% endalert %}
 
-## ステップ 4:アプリ内メッセージを構築および設計する
+## ステップ 4: アプリ内メッセージを構築および設計する
 
-ここであなたのメッセージが、あなたのブランドのシグネチャースタイルでランウェイを歩くことになります。
+ここでは、あなたのメッセージをブランドのシグネチャースタイルで演出し、オーディエンスに注目してもらいます。
 
 - 利用可能なエディターブロックとそのプロパティのリストについては、[エディターブロック]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/editor_blocks/)を参照してください。
 - メッセージの外観と感触をカスタマイズするためのヘルプについては、[スタイル設定]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/style_settings/)をチェックしてください。
@@ -152,15 +152,15 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 
 ### テストチェックリスト
 
-- 異なるデバイスでメッセージをテストしましたか？
-- 画像やメディアは期待通りに表示され、動作しますか？
+- メッセージをさまざまなデバイスでテストしましたか?
+- 画像やメディアは期待通りに表示され、機能しているか？
 - 液体は期待通りに機能しますか？Liquidが情報を返さない場合に、デフォルト属性値を考慮しましたか？
 - あなたのコピーは明確で簡潔で正しいですか？
 - ボタンはユーザーを行くべき場所に誘導していますか？
 
 ## よくある質問
 
-#### なぜボディクリックが私の分析ページに表示されないのですか？
+#### 本文クリック数がアプリの分析画面に表示されないのはなぜですか?
 
 ドラッグアンドドロップエディタで作成されたアプリ内メッセージのボディクリックは自動的に収集されません。詳細については、[iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/changelog/objc_changelog#3310)および[Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/changelog#1100)のSDK変更ログを参照してください。
 
@@ -176,7 +176,7 @@ local_redirect: #set-message-level-styles, #add-a-custom-font, #drag-and-drop-in
 
 現在、エディターはモーダルおよび全画面メッセージのみに制限されています。**メッセージコンテナ**セクションの**メッセージスタイル**パネルで表示タイプを切り替えることができます。
 
-#### キャンペーンまたはキャンバス内で作成したアプリ内メッセージをテンプレートとして保存できますか？
+#### キャンペーンまたはキャンバス内で作成した後、アプリ内メッセージをテンプレートとして保存できますか?
 
 そうです。将来のキャンペーンやキャンバスステップで再利用したいアプリ内メッセージがある場合は、エディタを終了した後に利用可能な**テンプレートとして保存**ボタンを使用してカスタムテンプレートとして保存できます。テンプレートとして保存する前に、まずキャンペーンを開始するか、下書きとして保存する必要があります。
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/templates/phone_number_capture.md b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/templates/phone_number_capture.md
index bc6f67c5df3..00b68357a2e 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/templates/phone_number_capture.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/drag_and_drop/templates/phone_number_capture.md
@@ -45,15 +45,15 @@ description: "このリファレンスページでは、SMSおよびWhatsAppの
 
 ### ステップ2:電話番号入力コンポーネントをカスタマイズする
 
-サインアップフォームの作成を開始するには、エディタで電話番号入力コンポーネントを選択します。
+サインアップフォームの作成を開始するには、エディターで電話番号の入力コンポーネントを選択します。
 
-![電話番号入力コンポーネントが選択された状態でサインアップフォームを作成する際のプレビューエリア。]\[img3]{: style="max-width:40%"}
+![電話番号の入力コンポーネントを選択したサインアップフォーム作成時のプレビューエリア]\[img3]]{: style="max-width:40%"}
 
-サイドメニューから、このテンプレートが電話番号を収集するサブスクリプショングループを指定します。コンプライアンスのベストプラクティスに従うために、電話番号のサインアップフォームごとに1つのサブスクリプショングループへの同意のみを収集できます。ただし、必要に応じて、他のサブスクリプショングループの同意を収集するために複数のフォームを使用することができます。
+サイドメニューから、このテンプレートが電話番号を収集するサブスクリプショングループを指定します。コンプライアンスのベストプラクティスに従うために、電話番号のサインアップフォームごとに 1 つのサブスクリプショングループに対する同意のみを収集できます。ただし、必要に応じて、他のサブスクリプショングループの同意を収集するために複数のフォームを使用できます。
 
 ![サブスクリプショングループドロップダウンにサブスクリプショングループが選択されています。]\[img4]{: style="max-width:40%"}
 
-デフォルトでは、私たちはグローバルに数値を収集しますが、収集する国の数を制限することができます。これは、特定の国の電話番号を持つユーザーにのみメッセージを送信する場合に役立ち、リストの清潔さを保つのに役立ちます。そのためには、**すべての国から番号を収集する**をオフにして、ドロップダウンを使用して特定の国を選択します。ユーザーは、あなたが明示的に追加した国のみを選択できるようになります。
+デフォルトでは、グローバルに数値を収集しますが、収集する国の数は制限できます。これは、特定の国の電話番号を持つユーザーにのみメッセージを送信する場合に役立ち、リストの清潔さを保つのに役立ちます。そのためには、**すべての国から番号を収集する**をオフにして、ドロップダウンを使用して特定の国を選択します。ユーザーは、あなたが明示的に追加した国のみを選択できるようになります。
 
 ![国のドロップダウンから、番号を収集したい国を選択します。]\[img5]{: style="max-width:40%"}
 
@@ -63,7 +63,7 @@ description: "このリファレンスページでは、SMSおよびWhatsAppの
 
 ### ステップ 3:免責事項の言語を追加する（SMSサインアップフォーム用）
 
-SMSサインアップフォームでは、送信するSMSの種類を明確に伝えることが重要です。フォームに次の情報を含めることで、リストの成長がコンプライアンスに準拠していることを確認してください:
+SMSサインアップフォームでは、送信するSMSの種類を明確に伝えることが重要です。フォームに次の情報を含めることで、リストの増加がコンプライアンスに準拠していることを確認してください。
 
 - お客様が受け取る可能性のあるSMSメッセージの種類の説明（カートのリマインダー、プロモーションやお得情報、予約のリマインダーなど）。すべてのユースケースを列挙する必要はありませんが、ブランドが送信するメッセージの種類について説明する必要があります。
 - 同意は購入の条件ではないことに注意してください（該当する場合）。
@@ -71,10 +71,10 @@ SMSサインアップフォームでは、送信するSMSの種類を明確に
 - 利用規約およびSMSプライバシーポリシーへのリンク。
 - ヘルプとオプトアウトキーワードのリマインダー（ヘルプの場合はHELP、キャンセルするにはSTOP）。
 
-テンプレートにプレースホルダーの免責事項を例として提供していますが、これは法的助言を構成するものではなく、コンプライアンスの目的で依拠すべきではありません。あなたの特定のブランドに合わせた言語を開発するために、法務チームと協力することが重要です。
+テンプレートにプレースホルダーの免責事項を例として提供していますが、これは法的助言を構成するものではなく、コンプライアンスの目的で依拠すべきではありません。法務チームと協力して、特定のブランドに合わせた文面を作成してください。
 
 {% alert note %}
-このドキュメントは、法的助言を提供することを意図しておらず、完全に依存することはできません。
+このドキュメントは、法律上の助言を提供することを意図したものではなく、完全に依存することもできません。
 {% endalert %}
 
 詳細については、[SMSの法律と規制][4]を参照してください。
@@ -85,7 +85,7 @@ SMSサインアップフォームでは、送信するSMSの種類を明確に
 
 ## レポート
 
-キャンペーンが開始された後、リアルタイムで結果を分析して、キャンペーンにどれだけのユーザーが関与したかを確認できます。サブスクリプショングループにオプトインしたユーザーの数を確認するには、アプリ内メッセージを受信し、フォームを送信したユーザーをフィルタリングして、サブスクリプショングループにサブスクライブしたユーザーの[Segment][5]を作成できます。
+キャンペーンの開始後、リアルタイムで結果を分析して、キャンペーンにエンゲージしたユーザー数を確認できます。サブスクリプショングループにオプトインしたユーザーの数を確認するには、アプリ内メッセージを受信してフォームを送信したユーザーをフィルタリングして、サブスクリプショングループに登録したユーザーの[セグメントを作成][5]します。
 
 ![アプリ内メッセージパフォーマンスパネルは、アプリ内メッセージ内の各リンクのクリック数を表示します。]\[img8]
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/faq.md b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/faq.md
index 1c74b183dfd..5a7fe3d2a36 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/faq.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/faq.md
@@ -13,21 +13,21 @@ tool: in-app messages
 
 ### ブラウザ内メッセージとは何か、アプリ内メッセージとどう違うのか？
 
-ブラウザ内メッセージは、ウェブブラウザに送信されるアプリ内メッセージである。インブラウザメッセージを作成するには、アプリ内メッセージキャンペーンまたはCanvasを作成する際に、**送信先**フィールドで**Webブラウザを**選択していることを確認する。 
+ブラウザ内メッセージは、ウェブブラウザに送信されるアプリ内メッセージである。ブラウザ内メッセージを作成するには、アプリ内メッセージキャンペーンまたはキャンバスの作成時に \[**送信先**] フィールドで \[**Web ブラウザ**] を選択します。 
 
 ### デバイスがオフラインの場合、アプリ内メッセージは表示されるのか？
 
-場合によるね。アプリ内メッセージはセッション開始時に配信されるため、デバイスはオフラインになる前にペイロードをダウンロードすることができ、オフライン状態でもアプリ内メッセージを表示することができる。ペイロードがダウンロードされなければ、アプリ内メッセージは表示されない。
+場合によるね。アプリ内メッセージはセッション開始時に配信されるため、デバイスはオフラインになる前にペイロードをダウンロードでき、オフラインの状態でもアプリ内メッセージを表示することができます。ペイロードがダウンロードされなければ、アプリ内メッセージは表示されない。
 
 ### ユーザーがすでにアプリ内メッセージのペイロードを端末に持っていて、メッセージの有効期限が変更された場合、有効期限はその端末で更新されるのか？
 
 ユーザーがセッションを開始すると、Brazeは、対象となるアプリ内メッセージに変更が加えられたかどうかをチェックし、それに応じてメッセージを更新する。そのため、有効期限が変更され、セッションが記録された場合、アプリ内メッセージは更新された情報でデバイスに送信される。
 
-### アプリ内メッセージキャンペーンでクワイエットアワーを設定するには？
+### アプリ内メッセージキャンペーンでサイレント時間を設定するにはどうすればよいですか?
 
-クワイエットアワー機能は、アプリ内メッセージキャンペーンでは使用できない。この機能は、特定の時間帯にユーザーにメッセージが送信されないようにするために使用する。アプリ内メッセージキャンペーンでは、ユーザーがアプリ内でアクティブな場合にのみ、アプリ内メッセージを受信する。 
+サイレント時間機能は、アプリ内メッセージキャンペーンでは使用できません。この機能は、特定の時間帯にユーザーにメッセージが送信されないようにするために使用する。アプリ内メッセージキャンペーンでは、ユーザーがアプリ内でアクティブな場合にのみ、アプリ内メッセージを受信する。 
 
-特定の時間帯にアプリ内メッセージを送信するための回避策として、以下のサンプルリキッドコードを使用する。これにより、アプリ内メッセージが指定した時間帯の午後7時59分以降、または午前8時前に表示された場合、メッセージを中断することができる。
+特定の時間帯にアプリ内メッセージを送信するための回避策として、以下のサンプルリキッドコードを使用する。これにより、アプリ内メッセージが指定したタイムゾーンの午後 7 時 59 分以降、または午前 8 時前に表示された場合、メッセージを中止できます。
 
 {% raw %}
 ```liquid
@@ -39,11 +39,11 @@ MESSAGE HERE
 ```
 {% endraw %}
 
-### アプリ内メッセージの資格はいつ計算されるのか？
+### アプリ内メッセージの適格性はいつ計算されますか?
 
-アプリ内メッセージの対象は、配信時に計算される。アプリ内メッセージが午前7時に送信される予定であれば、午前7時にこのアプリ内メッセージの適格性がチェックされる。
+アプリ内メッセージの適格性は、配信時に計算されます。アプリ内メッセージが午前 7 時に送信される予定の場合、このアプリ内メッセージの適格性は午前 7 時にチェックされます。
 
-アプリ内メッセージが表示されると、資格はアプリ内メッセージがダウンロードされ、トリガーされたタイミングに依存する。
+アプリ内メッセージがいったん表示されると、適格性は、アプリ内メッセージがダウンロードされトリガーされたタイミングに依存します。
 
 ### テンプレート化されたアプリ内メッセージとは何か？
 
@@ -51,23 +51,23 @@ MESSAGE HERE
 
 - `canvas_entry_properties`
 - `connected_content`
-- 以下のようなSMS変数がある。 {% raw %}`{sms.${*}}`{% endraw %}
+- 次のような SMS 変数: {% raw %}`{sms.${*}}`{% endraw %}
 - `catalog_items`
 - `catalog_selection_items`
 - `event_properties`
 
-つまり、セッション開始時に、デバイスはメッセージ全体ではなく、アプリ内メッセージのトリガーを受け取ることになる。ユーザーがアプリ内メッセージをトリガーすると、ユーザーのデバイスは実際のメッセージをフェッチするためにネットワークリクエストを行う。
+したがって、セッション開始時に、デバイスはメッセージ全体ではなく、そのアプリ内メッセージのトリガーを受け取ることになります。ユーザーがアプリ内メッセージをトリガーすると、ユーザーのデバイスは実際のメッセージをフェッチするためにネットワークリクエストを行う。
 
 {% alert note %}
-デバイスがインターネットにアクセスできない場合、メッセージは配信されない。リキッドロジックの解決に時間がかかりすぎると、メッセージは届かないかもしれない。
+デバイスがインターネットにアクセスできない場合、メッセージは配信されない。Liquid ロジックの解決に時間がかかりすぎると、メッセージは配信されないことがあります。
 {% endalert %}
 
-### アーカイブされたアプリ内メッセージキャンペーンがまだアプリ内メッセージインプレッションを配信しているのはなぜか？
+### アーカイブしたアプリ内メッセージキャンペーンがまだアプリ内メッセージのインプレッションを配信しているのはなぜですか?
 
 これは、アプリ内メッセージキャンペーンがアクティブだったときにセグメント基準を満たしたユーザーに対して発生する可能性がある。
 
-これを防ぐには、キャンペーンのセットアップ中に、**表示する前にキャンペーンの適格性を再評価するを**選択する。 
+これを防ぐには、キャンペーンの設定中に \[**表示する前にキャンペーンの適格性を再評価する**] を選択します。 
 
 ### アプリ内メッセージの有効期限を「1日後」に設定した場合、Brazeはどのように計算するのか？
 
-Brazeは、ユーザーがメッセージを受信できるようになってから24時間後を1日として有効期限を計算する。
\ No newline at end of file
+Braze は、ユーザーがメッセージを受信できるようになってから 24 時間後を 1 日として有効期限を計算します。
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/ios_app_rating_prompt.md b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/ios_app_rating_prompt.md
index d204471e434..71191bdabe2 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/ios_app_rating_prompt.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/ios_app_rating_prompt.md
@@ -14,7 +14,7 @@ channel:
 
 アップルは、iOS 10.3で導入されたネイティブ・プロンプトを提供しており、ユーザーはアプリ自体からアプリを評価することができる。iOSのアプリ内メッセージを使用してユーザーにアプリの評価を要求したい場合、Appleはカスタムレビュープロンプトを許可していないため、ネイティブプロンプトを使用する必要がある（[App Store Review Guidelines](https://developer.apple.com/app-store/review/guidelines/#code-of-conduct)、セクション5.6.1を参照）。
 
-Appleのガイドラインによると、アプリのレビューのプロンプトはユーザーに対して年に最大3回表示することができるため、アプリのレビューキャンペーンは[レート制限]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/)を活用する必要があります。ユーザーは、アプリの設定でアプリのレビュープロンプトを表示しないようにすることもできる。App Storeのレーティングについては、Appleの[レーティング、レビュー、レスポンスに関する](https://developer.apple.com/app-store/ratings-and-reviews/)記事を参照のこと。
+Apple のガイドラインによると、アプリのレビュープロンプトはユーザーに対して年に最大 3 回表示できるため、アプリのレビューキャンペーンでは[レート制限]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/)を活用する必要があります。ユーザーは、アプリの設定でアプリのレビュープロンプトを全く表示しないようにすることもできます。App Store のレーティングについては、Apple の[レーティング、レビュー、レスポンス](https://developer.apple.com/app-store/ratings-and-reviews/)に関する記事を参照してください。
 
 ## Brazeを使ってユーザーにアプリのレビューを依頼する
 
@@ -24,24 +24,24 @@ Appleのガイドラインによると、アプリのレビューのプロンプ
 
 このアプローチでは、ユーザーがApp Storeを訪れてレビューを追加するよう促したい。そのためには、App Storeに[ディープリンク]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/deep_linking_to_in-app_content/)するアプリ内メッセージキャンペーンを作成する。
 
-![2つのモバイル画面が並んでいる。1つ目は、App Storeでアプリを評価するようユーザーに求めるアプリ内メッセージだ。もうひとつは、そのアプリのiOS App Storeページだ。][1]
+![2 つのモバイル画面を並べて表示。1つ目は、App Storeでアプリを評価するようユーザーに求めるアプリ内メッセージだ。もうひとつは、そのアプリのiOS App Storeページだ。][1]
 
-### アプローチ2：ソフト・プライミング
+### アプローチ2：ソフトプライミング
 
-ユーザーをアプリから離脱させたくない場合は、まずアプリ内の別メッセージでユーザーに呼びかけることができる。プライミングとは、ネイティブのApp Storeレビュープロンプトを送信する前に、ユーザーに許可を求める方法である。そのためには、アプリ内メッセージキャンペーンを作成し、クリックされると`requestReview` メソッドを呼び出すカスタムディープリンクを追加する。 
+ユーザーをアプリから離脱させたくない場合は、まずアプリ内の個別メッセージでユーザーに呼びかけることができます。プライミングとは、ネイティブのApp Storeレビュープロンプトを送信する前に、ユーザーに許可を求める方法である。そのためには、アプリ内メッセージキャンペーンを作成し、クリックされると`requestReview` メソッドを呼び出すカスタムディープリンクを追加する。 
 
-詳しい手順については、[Custom App Store review promptを]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/custom_app_store_review_prompt/)参照のこと。
+詳しい手順については、[カスタム App Store レビュープロンプト]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/custom_app_store_review_prompt/)を参照してください。
 
-![2つのアプリ内メッセージを並べる。1つ目は、アプリを評価する時間があるかどうかを尋ねることで、ユーザーにアプリを評価するよう促すものだ。2つ目は、iOS App Storeのネイティブ・レビュー・メッセージで、ユーザーがアプリを評価するために選択できる5つ星のスケールが表示される。][2]
+![2 つのアプリ内メッセージを並べて表示。1 つ目は、アプリを評価する時間があるかどうかを尋ね、ユーザーにアプリを評価してもらうよう促します。2 つ目は、iOS App Store のネイティブレビューメッセージで、ユーザーがアプリを評価するために選択できる 5 つ星のスケールが表示されます。][2]
 
-ユーザーはネイティブのApp Storeレビュープロンプトを通じて評価を提出し、アプリを離れることなくレビューを書いて提出することができる。
+ユーザーはネイティブの App Store レビュープロンプトを介して評価を提出し、アプリを離れることなく、レビューを書き込んで提出することができます。
 
 ### 考慮事項
 
-ソフトプライミングの代わりに、Brazeのソフトプライマーメッセージを表示せずに、iOSアプリのレーティングプロンプトを直接表示することもできる。この利点は、ユーザーがアプリのレビュープロンプトをオプトアウトしている場合、アプリを評価しようとしても、そのためのプロンプトが表示されないという、最適とは言えないユーザー体験が発生しないことだ。
+ソフトプライミングの代わりに、事前に Braze のソフトプライマーメッセージを表示せずに、iOS アプリのレーティングプロンプトを直接表示することもできます。この利点は、ユーザーがアプリのレビュープロンプトをオプトアウトしている場合、アプリを評価しようとしても、そのためのプロンプトが表示されないという、最適とは言えないユーザー体験が発生しないことだ。
 
 {% alert important %}
-iOSネイティブアプリのレーティングプロンプトを模倣したカスタムHTMLアプリ内メッセージを作成しないこと。
+iOS ネイティブのアプリレーティングプロンプトを模倣したカスタムの HTML アプリ内メッセージは作成しないでください。これは Apple のガイドラインに違反する行為です。
 {% endalert %}
 
 [1]: {% image_buster /assets/img_archive/app_store_app_review.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/testing.md b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/testing.md
index 7a4ad88ff9e..32bab5e9579 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/testing.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/in-app_messages/testing.md
@@ -2,7 +2,7 @@
 nav_title: テスト
 article_title: アプリ内メッセージをテストする
 page_order: 4.5
-description: "この参考記事では、アプリ内メッセージをテストする価値、テスト方法、送信前に考慮すべきチェックリストについて説明している。"
+description: "この記事では、アプリ内メッセージをテストする価値、テスト方法、および送信前に考慮すべき事項のチェックリストについて説明します。"
 channel:
   - in-app messages
   
@@ -10,7 +10,7 @@ channel:
 
 # アプリ内メッセージテスト
 
-> キャンペーンを送信する前に、必ずアプリ内メッセージをテストすることが非常に重要だ。プレビューとテスト機能は、アプリ内メッセージを見るための2つの方法を提供する。メッセージをプレビューすることで、イメージしながら作成することができる。両方を利用することをお勧めする。
+> キャンペーンを送信する前に、必ずアプリ内メッセージをテストすることが非常に重要だ。プレビューとテスト機能は、アプリ内メッセージを見るための2つの方法を提供する。メッセージをプレビューして、作成中に視覚化したり、テストメッセージを自分や特定のユーザーのデバイスに送信したりできます。両方の機能を利用することをお勧めします。
 
 ## プレビュー
 
@@ -20,13 +20,13 @@ channel:
 **プレビューでは**、あなたのメッセージの表示は、ユーザーのデバイス上での実際のレンダリングと同一ではないかもしれない。メディア、コピー、パーソナライズ、カスタム属性が正しく生成されることを確認するため、デバイスにテストメッセージを送信することを常に推奨する。
 {% endalert %}
 
-### アプリ内メッセージ生成プレビュー
+### アプリ内メッセージの生成プレビュー
 
-あなたのメッセージがランダムなユーザー、特定のユーザー、カスタマイズされたユーザーにどのように見えるかをプレビューする。また、モバイル端末やタブレット端末用にメッセージをプレビューして、ユーザーがどのような体験をするかをよりよく知ることもできる。
+メッセージが任意のユーザー、特定のユーザー、またはカスタマイズされたユーザーにどのように表示されるかをプレビューします。メッセージにパーソナライゼーションや多言語が含まれている場合は、後者の 2 つが役立ちます。また、モバイル端末やタブレット端末用にメッセージをプレビューして、ユーザーがどのような体験をするかをよりよく知ることもできる。
 
-![アプリ内メッセージを作成する際の「作成」タブに、メッセージのプレビューが表示される。ユーザーが選択されていないので、本文に追加されたリキッドがそのまま表示される。][1]
+![アプリ内メッセージを作成する際の「作成」タブに、メッセージのプレビューが表示される。ユーザーが選択されていないため、本文に追加された Liquid はそのまま表示されます。][1]
 
-Brazeには3世代のアプリ内メッセージが用意されている。どの端末がどの世代をサポートしているかによって、どの端末にメッセージを送るかを細かく設定できる。
+Braze には 3 世代のアプリ内メッセージが用意されています。どの端末がどの世代をサポートしているかによって、どの端末にメッセージを送るかを細かく設定できる。
 
 ![アプリ内メッセージのプレビュー時に世代を切り替える。][2]{: height="50%" width="50%"}
 
@@ -38,14 +38,14 @@ Brazeには3世代のアプリ内メッセージが用意されている。ど
 
 ### ユーザーとしてメッセージをプレビューする
 
-また、**Test**タブからは、あたかも自分がユーザーであるかのように、メッセージをプレビューすることができる。特定のユーザーを選択することも、ランダムなユーザーを選択することも、カスタムユーザーを作成することもできる。
+また、**Test**タブからは、あたかも自分がユーザーであるかのように、メッセージをプレビューすることができる。特定のユーザーやランダムなユーザーを選択するか、カスタムユーザーを作成することができます。
 
-![アプリ内メッセージを作成する際のテストタブ。"ユーザーとしてメッセージをプレビュー "が "カスタムユーザー "に設定され、利用可能なプロフィールフィールドが設定可能なオプションとして表示される。][3]
+![アプリ内メッセージを作成する際のテストタブ。「ユーザーとしてメッセージをプレビュー」が「カスタムユーザー」に設定され、利用可能なプロファイルのフィールドが設定可能なオプションとして表示されています。][3]
 
 ### テスト・チェックリスト
 
 - 画像やメディアは期待通りに表示され、機能しているか？
-- リキッドは期待通りに機能しているか？リキッドが情報を返さない場合の[デフォルトの属性値を]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/conditional_logic/#accounting-for-null-attribute-values)考慮したか？
+- リキッドは期待通りに機能しているか？Liquid が情報を返さない場合、[デフォルトの属性値]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/conditional_logic/#accounting-for-null-attribute-values)を考慮したか?
 - コピーは明確で、簡潔で、正しいか？
 - あなたのボタンは、ユーザーをどこに誘導しているだろうか？
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/line.md b/_lang/ja/_user_guide/message_building_by_channel/line.md
index 74e9d3ab4d3..8361342e0fe 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/line.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/line.md
@@ -8,25 +8,23 @@ channel:
 guide_top_header: "LINE"
 guide_top_text: "[LINE](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf) は日本で使用率が最も高いメッセージングアプリです。月間アクティブユーザー数は 9,500 万人を超えます。メッセージングに加え、LINEはソーシャルメディア、ゲーム、ショッピング、決済の「オールインワン」プラットフォームをユーザーに提供している。<br><br>LINEアカウントとBrazeを統合することで、ゼロおよびファーストパーティの顧客データを活用し、顧客の嗜好、行動、クロスチャネルでのインタラクションに基づいて、適切な顧客に魅力的なLINEメッセージを送ることができる。<br><br>LINE アクセスはベータ版であり、一部の Braze パッケージでのみ利用できます。利用を始めるには、アカウントマネージャーまたはカスタマーサクセスマネージャーにお問い合わせください。"
 description: "このランディングページは、LINE チャネルのホームです。ここでは、LINE の設定、LINE サブスクリプショングループ、LINE キャンペーン、LINE レポートなどに関する記事をご覧いただけます。"
-hidden: true
-permalink: /line/
+alias: /line/
 
 guide_featured_title: "LINE"
 guide_featured_list:
 - name: LINE の設定
-  link: https://www.braze.com/docs/line/line_setup/
+  link: /docs/line/line_setup/
   image: /assets/img/braze_icons/phone-02.svg
 - name: LINEメッセージを作成する
-  link: https://www.braze.com/docs/line/create/
+  link: /docs/line/create/
   image: /assets/img/braze_icons/table.svg
 - name: LINE ユーザーへのメッセージング
-  link: https://www.braze.com/docs/line/messaging_users/
+  link: /docs/line/messaging_users/
   image: /assets/img/braze_icons/message-chat-circle.svg
 - name: LINE サブスクリプショングループ
-  link: https://www.braze.com/docs/line/subscription_groups/
+  link: /docs/line/subscription_groups/
   image: /assets/img/braze_icons/table.svg
 - name: LINE レポート
-  link: https://www.braze.com/docs/line/reporting/
+  link: /docs/line/reporting/
   image: /assets/img/braze_icons/bar-chart-01.svg
 ---
-<br><br>
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/message_building_by_channel/line/create.md b/_lang/ja/_user_guide/message_building_by_channel/line/create.md
index 8c09dc86330..75470235e00 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/line/create.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/line/create.md
@@ -8,8 +8,7 @@ tool:
  - Campaigns
 channel:
  - LINE
-hidden: true
-permalink: /line/create/
+alias: /line/create/
 ---
 
 # LINE メッセージの作成
@@ -49,7 +48,7 @@ LINE メッセージを作成する前に、次の手順を実行します。
 4\.必要に応じて、\[[チーム]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/teams/)] と \[[タグ]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/)] を追加します。
    * タグを使用すると、キャンペーンを検索してレポートを作成しやすくなります。例えば、\[[レポートビルダー]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/)] を使用する場合、特定のタグでフィルターできます。
 5. キャンペーンに必要な数だけバリアントを追加して名前を付けます。追加したバリアントごとに、さまざまなプラットフォーム、メッセージタイプ、レイアウトを選択できます。このトピックの詳細については、「[多変量テストと AB テスト]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/)」を参照してください。
-6. \[[サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/)] を選択して、メッセージを送信するユーザーが適切であることを確認します。サブスクリプショングループを選択すると、Braze によって自動的にセグメンテーションフィルターが追加され、配信登録済みのユーザーのみがキャンペーンを受信できるようになります。そのサブスクリプショングループに属する長いコードと短いコードのみを使用して、対象ユーザーに SMS が送信されます。
+6. \[[サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/)] を選択して、適切なユーザーに送信していることを確認します。サブスクリプショングループを選択すると、Braze によって自動的にセグメンテーションフィルターが追加され、配信登録済みのユーザーのみがキャンペーンを受信できるようになります。そのサブスクリプショングループに属する長いコードと短いコードのみが、SMS を対象ユーザーに送信するために使用されます。
 
 {% alert tip %}
 キャンペーン内のすべてのメッセージが類似しているか、同じ内容になる場合は、メッセージを作成してからバリアントを追加します。その後、\[**バリアントを追加**] ドロップダウンから \[**バリアントをコピー**] を選択できます。
@@ -95,13 +94,13 @@ Liquid を使用する場合は、必ずパーソナライゼーションのデ
 
 ### 配信スケジュールまたはトリガーを選択する
 
-LINE メッセージは、スケジュールされた時刻、アクション、または API トリガーに基づいて配信できます。スケジュールとトリガーのオプションの詳細については、「[キャンペーンのスケジュール設定]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/)」を参照してください。
+LINE メッセージは、スケジュールされた時刻、アクション、または API トリガーに基づいて配信できます。スケジュールとトリガーの詳細については、「[キャンペーンのスケジュール設定]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/)」を参照してください。
 
 配信コントロールを指定できます。たとえば、ユーザーを[再有効化]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/#campaigns)してキャンペーンを受信できるようにしたり、[フリークエンシーキャップ]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)ルールを有効にしたりできます。アクションベースの配信では、キャンペーンの継続時間と \[[サイレント時間]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign/#quiet-hours)] を設定することもできます。
 
 ### ターゲットとするユーザーを選択する
 
-セグメントまたはフィルターを選択して \[[ユーザーをターゲットに設定]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)] し、オーディエンスを絞り込みます。すでにサブスクリプショングループを選択しているため、ユーザーがブランドに対して希望しているコミュニケーションの頻度やカテゴリによって、ユーザーが絞り込まれます。 
+セグメントまたはフィルターを選択して \[[ユーザーをターゲットに設定]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)] し、オーディエンスを絞り込みます。すでにサブスクリプショングループを選択しているため、ユーザーがブランドと希望するコミュニケーションの程度やカテゴリによって、ユーザーが絞り込まれます。
 
 セグメントから大きなオーディエンスを選択し、必要に応じて[フィルター]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/)でさらにセグメントを絞り込みます。セグメントのおおよその人数について現在の状態を示すスナップショットが自動的に表示されます。正確なセグメントメンバーシップは常にメッセージが送信される直前に計算されることに注意してください。
 
@@ -132,4 +131,4 @@ Braze では、キャンペーンを受信した後、ユーザーが指定の
 
 
 [1]: {% image_buster /assets/img/line/line_composer.png %}
-[2]: {% image_buster /assets/img/line/test_preview.png %}
\ No newline at end of file
+[2]: {% image_buster /assets/img/line/test_preview.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/line/create/message_types.md b/_lang/ja/_user_guide/message_building_by_channel/line/create/message_types.md
new file mode 100644
index 00000000000..925abba0dd2
--- /dev/null
+++ b/_lang/ja/_user_guide/message_building_by_channel/line/create/message_types.md
@@ -0,0 +1,140 @@
+---
+nav_title: メッセージタイプ
+article_title: LINE メッセージタイプ
+page_order: 1
+description: "この記事では、さまざまなタイプのLINE メッセージについて説明します。"
+page_type: reference
+tool:
+ - Campaigns
+channel:
+ - LINE
+alias: /line/create/message_types/
+---
+
+# LINEメッセージタイプ
+
+> この記事では、構成可能なLINEメッセージタイプについて説明します。これには、側面と制限事項が含まれ、LINEベータコレクションの一部です。[メインページに戻ります]({{site.baseurl}}/line/)。
+
+{% alert important %}
+LINE アクセスはベータ版であり、一部の Braze パッケージでのみ利用できます。利用を始めるには、アカウントマネージャーまたはカスタマーサクセスマネージャーにお問い合わせください。
+{% endalert %}
+
+LINEメッセージを作成するときに、メッセージタイプをコンポーザーにドラッグアンドドロップしてカスタマイズできます。
+
+![テキスト、イメージ、リッチメッセージ、カードベースのメッセージなど、コンポーザーエディタにドラッグするメッセージタイプのメッセージタイプパネル。][5]{: style="max-width:40%;"}
+
+## テキスト
+
+LINEテキストメッセージには、最大5000文字を含めることができ、絵文字とリキッドパーソナライゼーションを含めることができます。
+
+ユースケースには次の項目が含まれます。
+- クリアランスストックの期間限定プロモーションを発表
+- 個性的なプロモーションカードでパーソナライズされた誕生日挨拶を送る
+- 今後のイベントに関するクイックアップデートを共有する
+
+![ブラック・フライデー・パーティーについて忘れず、深夜12時までに最大80%節約できる可能性があることをユーザーに知らせるテキスト・メッセージ。][1]{: style="max-width:40%;"}
+
+## 画像
+
+LINE イメージメッセージは、[メディアライブラリ]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/media_library/)、URL、またはLiquid から追加できます。これらのイメージはスタンドアロンであり、クリック可能なリンクは含まれていません。
+
+ユースケースには次の項目が含まれます。
+- ショーケースの旅行先。ユーザーに飛行機のチケット購入を検討してもらう
+- 来年の冬服を素晴らしい取引で仕入れることをユーザーに奨励するために、シーズン末のプロモーションを強調する
+- 店頭での年間販売に視覚的なカウントダウンを開始
+
+![トースターセールを宣伝するイメージメッセージ。][2]{: style="max-width:40%;"}
+
+### URL画像
+
+以下を組み込んだユースケースにURL イメージを使用します。
+- イメージソース属性に「Liquid」を含めることで、ダイナミックイメージをリキッド化します。たとえば、イメージURL として{% raw %} `https://example.com/images/?imageBanner={{first_name}}` {% endraw %} を挿入して、イメージにユーザーの名を含めることができます
+- [Web サーバーまたはパブリックにアクセス可能なAPI から直接イメージをプルすることで、接続されたコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/)
+- [インポートされたCSV ファイルおよびAPI エンドポイントからのイメージへのアクセスによるカタログのブライズ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/)
+
+| **仕様** | **推奨プロパティ** |
+|--------------------------|----------------------------|
+| 画像ファイルURL長 | 最大2000 文字  |
+| 画像フォーマット          | PNG、JPEG             |
+| ファイルサイズ     |  最大10 MB |
+{: .reset-td-br-1 .reset-td-br-2}
+
+## リッチメッセージ(イメージマップ)
+
+LINEリッチメッセージは、イメージ上の特定の領域を選択して開く1つ以上のリンクを含むイメージです。リッチメッセージテンプレートを選択して、イメージへのリンクのマッピング方法を選択します。
+
+ユースケースには次の項目が含まれます。
+- 新しく到着したハンドバッグのグリッドを、各バッグの各製品ページへのリンク付きで表示する
+- 項目を選択してコンボオーダーを開始するインタラクティブメニューを表示する
+- グリッドスクエアを選択して、ユーザが選択できる複数のプロモーションをレイアウトします
+
+![作曲者エディターで、異なるサンドイッチの写真が入った4平方のリッチメッセージ。][3]
+
+### イメージマップ
+
+| **仕様** | **推奨プロパティ** |
+|--------------------------|----------------------------|
+| 画像ファイルURL長 | 最大2000 文字  |
+| 画像フォーマット          | PNG(透過可)、JPEG             |
+| アスペクト比          | 1:1(幅:高さ)
+| ファイルサイズ     |  最大10 MB |
+{: .reset-td-br-1 .reset-td-br-2}
+
+### URIリンク
+
+| **仕様** | **推奨プロパティ** |
+|--------------------------|----------------------------|
+| 文字数      | 最大1000 |
+| スキーム              | HTTP, HTTPS, LINE, tel |
+{: .reset-td-br-1 .reset-td-br-2}
+
+### テキスト
+
+テキストリッチメッセージには最大 400 文字を含めることができます。
+
+## カードベース(カルーセル)
+
+LINEカードベースのメッセージを使用すると、カルーセルなどの複数のメッセージをスクロールして、カードまたはカードのボタンを選択してメッセージに最も関連するアクションを実行できます。
+
+ユースケースには次の項目が含まれます。
+- 特定のメニュー項目のプロモーションを表示する
+- 今シーズンのベストセラージャケットをハイライト
+- キットに含まれている調理器具や機器のサンプリングを提示する
+
+![コンポーザーエディタでパンとサンドイッチを促進する少なくとも2枚のカードを含むカードベースのメッセージ。][4]
+
+### メッセージ
+
+| **仕様** | **推奨プロパティ** |
+|--------------------------|----------------------------|
+| 列                  | 最大10 |
+| アスペクト比             | 矩形:1.51:1 <br> 正方形:1:1  |
+| タイトル                    | 最大40文字
+{: .reset-td-br-1 .reset-td-br-2}
+
+
+### 画像
+
+| **仕様** | **推奨プロパティ** |
+|--------------------------|----------------------------|
+| 画像の URL                 | 最大2000 文字 |
+| 画像フォーマット              | JPEGまたはPNG |
+| 幅                     | 1024ピクセル  |
+| ファイルサイズ                 | 1 MB |
+{: .reset-td-br-1 .reset-td-br-2}
+
+
+### テキスト
+
+| **仕様** | **推奨プロパティ** |
+|-------------------------|----------------------------|
+| 文字              | 最大120件(画像、タイトルなし) <br> 最大60件(画像やタイトルのついたメール)  |
+| アクション                 | 3 最大 |
+{: .reset-td-br-1 .reset-td-br-2}
+
+
+[1]: {% image_buster /assets/img/line/line_text_message.png %}
+[2]: {% image_buster /assets/img/line/line_image_message.png %}
+[3]: {% image_buster /assets/img/line/line_rich_message.png %}
+[4]: {% image_buster /assets/img/line/line_card_message.png %}
+[5]: {% image_buster /assets/img/line/line_message_types.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/line/line_setup.md b/_lang/ja/_user_guide/message_building_by_channel/line/line_setup.md
index 7c1e3773a53..b8d0827b505 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/line/line_setup.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/line/line_setup.md
@@ -7,8 +7,7 @@ search_tag: Partner
 page_order: 0
 channel:
  - LINE
-hidden: true
-permalink: /line/line_setup/
+alias: /line/line_setup/
 ---
 
 
@@ -131,4 +130,4 @@ LINE と Braze を統合するには、以下が必要です。
 [5]: {% image_buster /assets/img/line/filter_group.png %}
 [6]: {% image_buster /assets/img/line/csv_export_user_data.png %}
 [7]: {% image_buster /assets/img/line/trigger.png %}
-[8]: {% image_buster /assets/img/line/message.png %}
\ No newline at end of file
+[8]: {% image_buster /assets/img/line/message.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/line/line_users.md b/_lang/ja/_user_guide/message_building_by_channel/line/line_users.md
new file mode 100644
index 00000000000..fd64c7831bd
--- /dev/null
+++ b/_lang/ja/_user_guide/message_building_by_channel/line/line_users.md
@@ -0,0 +1,7 @@
+---
+nav_title: LINE Users
+config_only: true
+noindex: true
+layout: blank_config
+page_order: 4
+---
diff --git a/_lang/ja/_user_guide/subscription_groups.md b/_lang/ja/_user_guide/message_building_by_channel/line/line_users/subscription_groups.md
similarity index 95%
rename from _lang/ja/_user_guide/subscription_groups.md
rename to _lang/ja/_user_guide/message_building_by_channel/line/line_users/subscription_groups.md
index 0a296089b6a..a0be4bcb5e4 100644
--- a/_lang/ja/_user_guide/subscription_groups.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/line/line_users/subscription_groups.md
@@ -6,8 +6,7 @@ description: "この記事では、LINE のメッセージサブスクリプシ
 page_type: reference
 channel:
  - LINE
-hidden: true
-permalink: /line/subscription_groups/
+alias: /line/subscription_groups/
 ---
 
 # LINE サブスクリプショングループ
@@ -26,4 +25,4 @@ LINE アクセスはベータ版であり、一部の Braze パッケージで
 
 ## ユーザーの LINE サブスクリプショングループを設定する
 
-LINE はユーザーのサブスクリプションステータスをホストしています。Braze は、サブスクリプションステータスを更新するフォローイベントとフォロー解除イベントを処理します。
\ No newline at end of file
+LINE はユーザーのサブスクリプションステータスをホストしています。Braze は、サブスクリプションステータスを更新するフォローイベントとフォロー解除イベントを処理します。
diff --git a/_lang/ja/_user_guide/message_building_by_channel/line/line_users/user_management.md b/_lang/ja/_user_guide/message_building_by_channel/line/line_users/user_management.md
new file mode 100644
index 00000000000..1f0ecb51a5d
--- /dev/null
+++ b/_lang/ja/_user_guide/message_building_by_channel/line/line_users/user_management.md
@@ -0,0 +1,48 @@
+---
+nav_title: ユーザーマネージャー
+article_title: LINEユーザーマネージャー
+page_order: 0
+description: "この記事では、LINEのユーザーIDとその設定方法について解説する。"
+page_type: reference
+channel:
+ - LINE
+alias: /line/user_management/
+---
+
+# LINEユーザーマネージャー
+
+> LINEのユーザーIDは、`native_line_id` というユーザープロファイル属性に格納されている。この識別子は、LINEチャネルでユーザーにメッセージを送信する際に使用される。この記事は、`native_line_id` 属性をカバーし、LINEベータ・コレクションの一部である。[メインページに戻ります](https://www.braze.com/docs/line/)。
+
+顧客ユーザーデータは、[Brazeユーザープロファイルで]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/)表される。ユーザープロファイルには、名やメール・アドレスなど、企業のユーザーに関する情報や属性が保存される。
+
+Brazeを通じてLINEメッセージを送信する際、Brazeは`native_line_id` 属性を使用してメッセージを送信するユーザーを識別する。ユーザーがチャネルをフォローしたときやメッセージに返信したときなど、LINEがBrazeのWebhookイベントを送信すると、`native_line_id` 、対応するユーザープロファイルが検索される。
+
+{% alert note %}
+LINEのユーザーIDは、LINEの提供元によって区別されている。特定のユーザーは、フォローしているプロバイダーごとに異なるLINEユーザーIDを持つことになる。ユーザーIDはフォローするブランドごとに変わるため、（メールや電話番号と違って）ユーザーが自分のLINE IDを知っている可能性は低い。
+{% endalert %}
+
+## `native_line_id` を設定する。
+
+ユーザープロファイルに`native_line_id` が設定されるシナリオはいくつかあるが、その概要は以下の通り。
+
+| シナリオ | を持つユーザープロファイルが存在するかどうか。 `native_line_id` | 結果 |
+| --- | --- | --- |
+|ユーザーがLINEチャネルをフォローする | いいえ| 匿名ユーザープロファイルが作成される（マージが必要）：<br> -`native_line_id` 、ユーザーのLINE IDが設定される。 <br>-`line_id` ユーザーエイリアスはユーザーのLINE IDに設定される。<br>\- ユーザーがチャネルのサブスクリプショングループにサブスクライブしている。 |
+|ユーザーがLINEチャネルをフォローする| はい | `native_line_id` を持つすべてのユーザープロファイル：<br>\- チャネルのサブスクリプショングループにサブスクライブしている。|
+|ユーザーCSVアップロードで、`ative_line_id` のカラムを使用している。| いいえ| 指定された`external_id` またはユーザーエイリアスのユーザープロファイルが存在しない場合：<br>-`native_line_id` が指定された値に設定される。<br> \- CSVで指定されたその他の属性はすべてユーザープロファイルに設定される|
+|同社はユーザーCSVアップロードを`native_line_id` 列で使用している。 | はい | 指定された`external_id` またはユーザーエイリアスのユーザープロファイルが存在する場合：<br>-`native_line_id` が指定された値に設定される。<br>\- CSVで指定されたその他の属性はすべてユーザープロファイルに設定される<br>\- 複数のプロファイルが同じである。 `native_line_id` |
+| 会社は`/users/track` エンドポイントを使用し、`native_line_id` 属性を指定する。 | いいえ | 指定されたユーザー[（`external_id`]({{site.baseurl}}/api/objects_filters/user_attributes_object/) 、`user_alias`({{site.baseurl}}/api/objects_filters/user_attributes_object/) 、`braze_id` 、`email` で指定({{site.baseurl}}/api/objects_filters/user_attributes_object/)）のユーザープロファイルが存在しない場合：<br>-`native_line_id` が指定された値に設定される。<br>\- リクエストで指定された他のすべての属性は、ユーザープロファイルに設定される。 |
+| 会社は`/users/track` エンドポイントを使用し、`native_line_id` 属性を指定する。 | はい | 指定されたユーザー[（`external_id` 、`user_alias` 、`braze_id` または`email` で指定]({{site.baseurl}}/api/objects_filters/user_attributes_object/)）のユーザープロファイルが存在する場合：<br>-`native_line_id` が指定された値に設定される。<br>\- リクエストで指定された他のすべての属性は、ユーザープロファイルに設定される。<br>\- 複数のプロファイルが同じである。 `native_line_id` |
+| 会社からBrazeにサブスクリプションステータスの同期を依頼する。 | いいえ | LINEから返されたユーザーLINE IDがBrazeに対応するユーザープロファイルを持たない場合、匿名ユーザープロファイルが作成される：<br>-`native_line_id` 、ユーザーのLINE IDが設定される。<br>-`line_id` ユーザーエイリアスはユーザーのLINE IDに設定される。<br>\- ユーザーがチャネルのサブスクリプショングループにサブスクライブしている。<br><br>同じLINE IDのユーザーを後から作成した場合、重複したユーザーが存在することになるが、どちらも正しいLINEのサブスクリプションステータスを持つことになる。ユーザー統合は、このような場合にユーザー群を一掃することができる。 |
+| 会社からBrazeにサブスクリプションステータスの同期を依頼する。 | はい | LINEから返されたユーザーIDがBrazeのユーザープロファイルと一致する場合：<br>\- ユーザーがチャネルのサブスクリプショングループにサブスクライブしている。 |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 }
+
+## を見つける `native_line_id`
+
+Brazeダッシュボードでユーザープロファイルを表示する際、`native_line_id` 属性が設定されているかどうかは、**エンゲージメントタブ**>**コンタクト設定**セクション >**LINE**セクションで確認できる。
+
+`native_line_id` が設定されている場合は、**LINEユーザーIDの**下に表示される。そうでなければ表示されない。
+
+![エンゲージメント・タブのライン・コンタクト設定。][1]{: style="max-width:60%;"}
+
+[1]: {% image_buster /assets/img/line/line_contact_settings.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/line/messaging_users.md b/_lang/ja/_user_guide/message_building_by_channel/line/messaging_users.md
index 35084d5e2a2..e64e2a2ee83 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/line/messaging_users.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/line/messaging_users.md
@@ -6,8 +6,7 @@ description: "この記事では、テンプレート化されたキャンペー
 page_type: reference
 channel:
  - LINE
-hidden: true
-permalink: /line/messaging_users/
+alias: /line/messaging_users/
 ---
 
 # LINE ユーザーへのメッセージング
@@ -53,4 +52,4 @@ LINE アクセスはベータ版であり、一部の Braze パッケージで
 このメッセージについては、このチャネルは人間が監視していないことをユーザーに通知し、必要に応じてサポートチャネルに案内する LINE メッセージを送信する必要があります。
 
 [1]: {% image_buster /assets/img/line/trigger_word_campaign.png %}
-[2]: {% image_buster /assets/img/line/trigger_word_canvas.png %}
\ No newline at end of file
+[2]: {% image_buster /assets/img/line/trigger_word_canvas.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/line/reporting.md b/_lang/ja/_user_guide/message_building_by_channel/line/reporting.md
index 363d35e871c..28a24c7d711 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/line/reporting.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/line/reporting.md
@@ -7,7 +7,7 @@ page_type: reference
 channel:
  - LINE
 hidden: true
-permalink: /line/reporting/
+alias: /line/reporting/
 ---
 
 # LINE レポート
@@ -63,16 +63,16 @@ LINE の開封とクリック関連の統計は、1 日にイベントを実行
 1 日ごとの内訳を確認するには、<i class="fas fa-bars"></i> ハンバーガーメニューを選択し、\[**CSV をダウンロード**] を選択すると、レポートを CSV 形式でエクスポートできます。
 
 ### コンバージョンイベントの詳細
- 
+
 \[**コンバージョンイベントの詳細**] パネルには、キャンペーンのコンバージョンイベントのパフォーマンスが表示されます。詳細については、「[コンバージョンイベント]({{site.baseurl}}/user_guide/engagement_tools/testing/conversion_correlation)」を参照してください。
 
 ### コンバージョンの相関
 
 \[**コンバージョンの相関**] パネルでは、どのようなユーザー属性と行動が、キャンペーンに設定した結果に役立つか、または悪影響を与えるかを把握できます。詳細については、「[コンバージョンの相関]({{site.baseurl}}/user_guide/engagement_tools/testing/conversion_correlation)」を参照してください。
 
-## LINE ユーザー ID 
+## LINE ユーザー ID
 
 LINE ユーザー ID は、プロバイダーごとに各ユーザーに設定されています。LINE ID は、フォローするブランドごとに変わるため、ユーザーが (メールや電話番号とは違って) 自分の LINE ID を知ることはまずありません。
 
 
-[1]: {% image_buster /assets/img/line/line_performance.png %}
\ No newline at end of file
+[1]: {% image_buster /assets/img/line/line_performance.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/line/subscription_groups.md b/_lang/ja/_user_guide/message_building_by_channel/line/subscription_groups.md
deleted file mode 100644
index 0a296089b6a..00000000000
--- a/_lang/ja/_user_guide/message_building_by_channel/line/subscription_groups.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-nav_title: サブスクリプショングループ
-article_title: サブスクリプショングループ
-page_order: 3
-description: "この記事では、LINE のメッセージサブスクリプショングループについて説明します。"
-page_type: reference
-channel:
- - LINE
-hidden: true
-permalink: /line/subscription_groups/
----
-
-# LINE サブスクリプショングループ
-
-> LINE ユーザーのサブスクリプションの状態には「配信登録済み」と「配信停止済み」の 2 種類があります。LINE は 1 つのワークスペースにつき最大 100 のサブスクリプショングループを持つことができ、各サブスクリプショングループは独自の LINE チャネルに接続されています。<br><br>この記事は LINE ベータ版コレクションの一部です。[メインページに戻ります](https://www.braze.com/docs/line/)。
-
-{% alert important %}
-LINE アクセスはベータ版であり、一部の Braze パッケージでのみ利用できます。利用を始めるには、アカウントマネージャーまたはカスタマーサクセスマネージャーにお問い合わせください。
-{% endalert %}
-
-| 状態 | 定義 |
-| --- | --- |
-| 配信登録済み | ユーザーが LINE アプリ内から LINE チャネルをフォローした。統合ステップを完了した後、ユーザーがフォローすると自動的に配信登録されます。 |
-| 配信停止済み | ユーザーが LINE アプリ内から LINE チャネルをフォローしていないか、ユーザーが明示的に LINE チャネルのフォローを解除した。<br><br> LINE のサブスクリプショングループを配信停止したユーザーは、そのサブスクリプショングループに属する送信チャネルからの LINE メッセージを受け取れなくなります。 |
-{: .reset-td-br-1 .reset-td-br-2 }
-
-## ユーザーの LINE サブスクリプショングループを設定する
-
-LINE はユーザーのサブスクリプションステータスをホストしています。Braze は、サブスクリプションステータスを更新するフォローイベントとフォロー解除イベントを処理します。
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/message_building_by_channel/push/advanced_push_options/push_stories.md b/_lang/ja/_user_guide/message_building_by_channel/push/advanced_push_options/push_stories.md
index 6523d10874a..9939ce40e31 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/push/advanced_push_options/push_stories.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/push/advanced_push_options/push_stories.md
@@ -13,13 +13,13 @@ channel:
 
 > プッシュストーリーは、Brazeが導入した新しいタイプのプッシュ通知である。この機能は、インスタグラムやフェイスブックで普及した写真のカルーセル機能を取り入れたもので、マーケティング担当者は、リッチでまとまりのあるストーリーを伝えるプッシュ内のページのカルーセルを作成することができる。これらのページは、画像、クリックアクション、タイトル、説明文で構成されている。ユーザーはこれらのページをスワイプして、あなたが語るストーリーを見ることができる。
 
-| アンドロイドの例（拡大） | IOSの例（拡大） |
+| Android の例 (展開表示) | IOSの例（拡大） |
 | :-----: | :----------: |
 | ![][1] | ![][2] |
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% alert note %}
-iOS SDKバージョン3.13.0以降では、SDKの画像ダウンロード方法の変更により、最初の画像のサムネイルがプッシュのコンデンスビューに表示されない。メッセージのコピーで、画像を見るためにプッシュを展開するようユーザーを促すようにする。
+iOS SDKバージョン3.13.0以降では、SDKの画像ダウンロード方法の変更により、最初の画像のサムネイルがプッシュのコンデンスビューに表示されない。メッセージのコピーで、画像を見るためにプッシュを展開するよう必ずユーザーを促してください。
 {% endalert %}
 
 ## 前提条件
@@ -33,13 +33,13 @@ iOS SDKバージョン3.13.0以降では、SDKの画像ダウンロード方法
 
 ![][6]{: style="float:right;max-width:50%;margin-left:15px;margin-bottom:15px;"}
 
-プッシュストーリーズを使用するには、[プッシュキャンペーンを]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/)作成し、**通知タイプとして** **プッシュストーリーズを**選択する。
+プッシュス通知ストーリーを使用するには、[プッシュキャンペーン]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/)を作成し、\[**通知タイプ**] として \[**プッシュ通知ストーリー**] を選択します。
 
 ### プッシュストーリーの作曲家
 
 ページを作成するには、以下の手順を実行する：
 
-1. メインコンポーザーから**ページの管理を**クリックする。
+1. メインの作成画面から \[**ページを管理**] をクリックします。
     <br><br>![][4]{: style="max-width:70%"}<br><br>
 2. 各ページに画像を挿入し、その画像をクリックする動作を追加する。
 3. 必要であれば、各ページに**タイトルと** **説明を**追加する。1つのページでタイトルとディスクリプションを使用する場合は、すべてのページに挿入する必要がある。
@@ -49,7 +49,7 @@ iOS SDKバージョン3.13.0以降では、SDKの画像ダウンロード方法
 ![][3]{: style="max-width:60%"}
 
 {% alert important %}
-[コネクテッド・コンテンツで]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/#about-connected-content)画像を取り込む場合は、画像のURLが`https://` で始まっていることを確認する。`http://` を使うとアプリがクラッシュする。
+[コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/#about-connected-content)で画像を取り込む場合は、画像の URL が `https://` で始まっていることを確認します。`http://` を使うとアプリがクラッシュする。
 {% endalert %}
 
 ### 画像とテキストの仕様
@@ -59,7 +59,7 @@ iOS SDKバージョン3.13.0以降では、SDKの画像ダウンロード方法
 {% tabs %}
 {% tab 画像 %}
 
-- **画像の比率だ：**2:1（必須）
+- **画像比:** 2:1（必須）
 - **推奨画像サイズ**500 KB
 - **最大画像サイズ：**5 MB
 - **ファイルの種類:**PNG、JPEG
@@ -79,13 +79,13 @@ iOS SDKバージョン3.13.0以降では、SDKの画像ダウンロード方法
 
 ### プッシュ・ストーリーのセグメンテーション
 
-キャンペーンやキャンバスを作成する際、プッシュストーリーページをクリックしたかどうかに基づいて、ターゲットとするユーザーを絞り込むことができる。次に、キャンペーンとユーザーをターゲットにするページを選択する。
+キャンペーンやキャンバスを作成する際、プッシュストーリーページをクリックしたかどうかに基づいて、ターゲットとするユーザーを絞り込むことができる。次に、ユーザーをターゲットにするために使用するキャンペーンとページを選択します。
 
 ### プッシュストーリーズ分析
 
-アナリティクスは、現在のプッシュ通知のアナリティクス・セクションと非常によく似ている。Push Stories分析では、**Direct Opens**指標を開いてページごとのクリック数を見ることができる。
+分析は、プッシュ通知の現行の分析セクションとよく似ています。Push Stories分析では、**Direct Opens**指標を開いてページごとのクリック数を見ることができる。
 
-![iOSのプッシュパフォーマンス表には、分析サンプルとDirect Opens指標の詳細が掲載されている。][5]
+![iOS のプッシュパフォーマンス表には、分析サンプルと直接開封数指標の詳細が表示されます。][5]
 
 ## トラブルシューティング
 
@@ -93,7 +93,7 @@ iOS SDKバージョン3.13.0以降では、SDKの画像ダウンロード方法
 
 #### 自分自身にプッシュストーリーを送ったが、通知は届かなかった。
 
-アップルは、さまざまな要因に基づいて、特定の種類の通知がデバイスに送信されないようにする特定のルールを設けている。これには、顧客のデータプラン、通知サイズ、顧客のストレージ容量の評価が含まれる。その結果、顧客に通知が送られないこともある。
+アップルは、さまざまな要因に基づいて、特定の種類の通知がデバイスに送信されないようにする特定のルールを設けている。これには、顧客のデータプラン、通知サイズ、顧客のストレージ容量の評価が含まれます。その結果、顧客に通知が送られないこともあります。
 
 これらは、プッシュストーリーをデザインする際に考慮すべき、アップルが課す制限である。
 
@@ -105,7 +105,7 @@ iOS SDKバージョン3.13.0以降では、SDKの画像ダウンロード方法
 
 #### 画像をクリックしてもプッシュストーリーが解除されない 
 
-デフォルトでは、Androidではユーザーが画像をクリックしてもプッシュストーリーは解除されない。通知を解除したい場合は、次のように電話する。 [`cancelNotification`](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.push/-braze-notification-utils/index.html#-1466259649%2FFunctions%2F-1725759721).  
+デフォルトでは、Androidではユーザーが画像をクリックしてもプッシュストーリーは解除されない。通知を解除したい場合は、[`cancelNotification`](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze.push/-braze-notification-utils/index.html#-1466259649%2FFunctions%2F-1725759721) を呼び出します。  
 
 [1]: {% image_buster /assets/img_archive/pushstories_android_preview.png %}
 [2]: {% image_buster /assets/img_archive/pushstories_ios_preview.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/push/android/advanced_campaign_settings.md b/_lang/ja/_user_guide/message_building_by_channel/push/android/advanced_campaign_settings.md
index a5661a4dd42..f4805738090 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/push/android/advanced_campaign_settings.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/push/android/advanced_campaign_settings.md
@@ -1,9 +1,9 @@
 ---
-nav_title: "プッシュ・キャンペーンの詳細設定"
-article_title: プッシュ・キャンペーンの詳細設定
+nav_title: "プッシュキャンペーンの詳細設定"
+article_title: プッシュキャンペーンの詳細設定
 page_order: 5
 page_layout: reference
-description: "この参考記事では、優先度、カスタムURL、配信オプションなど、プッシュキャンペーンの詳細設定をいくつか取り上げている。"
+description: "この記事では、優先度、カスタム URL、配信オプションなど、プッシュキャンペーンの詳細設定について説明します。"
 platform: Android
 channel:
   - push
@@ -24,15 +24,15 @@ tool:
 
 ![]({% image_buster /assets/img_archive/notification_ids.png %}){: style="max-width:80%;" }
 
-## タイム・ツー・ライブ（TTL） {#ttl}
+## 有効時間 (TTL) {#ttl}
 
-time-to-live (TTL)フィールドでは、プッシュ・メッセージング・サービスでメッセージを保存する時間の長さをカスタムで設定できる。Time-to-Liveのデフォルト値は、Firebase Cloud Messaging (FCM)では4週間、Amazon Device Messaging (ADM)では31日である。
+time-to-live (TTL)フィールドでは、プッシュ・メッセージング・サービスでメッセージを保存する時間の長さをカスタムで設定できる。有効期限のデフォルト値は、Firebase Cloud Messaging (FCM) では 4 週間、Amazon Device Messaging (ADM) では 31 日間です。
 
-例えば、あなたのアプリがゲームで、ユーザーが毎日ゲームをプレイし続ければゲーム内通貨ボーナスを提供するとする。一定の日数を超えたユーザーに、その日数が破られる危険性があることを警告するプッシュを送ることができる。しかし、ユーザーが4週間後、生存期間をデフォルトに設定した状態でゲームアプリにデバイスを再接続した場合、それらのメッセージはメッセージングサービス内ですでに期限切れとなり、配信されないことになる。
+例えば、貴社のアプリがゲームで、ユーザーが毎日ゲームをプレイし続けることを条件にゲーム内通貨ボーナスを提供するとします。一定の日数を超えたユーザーには、その連続日数が破られる危険性があることを警告するプッシュを送信できます。しかし、ユーザーが4週間後、生存期間をデフォルトに設定した状態でゲームアプリにデバイスを再接続した場合、それらのメッセージはメッセージングサービス内ですでに期限切れとなり、配信されないことになる。
 
 ## Firebase メッセージング配信の優先順位 {#fcm-priority}
 
-**Firebase Messaging Delivery Priority** フィールドでは、「通常」または「高」のどちらの優先度でプッシュを Firebase Cloud Messaging に送信するかを制御できます。詳しくは[FCMのドキュメントを](https://firebase.google.com/docs/cloud-messaging/concept-options#setting-the-priority-of-a-message)参照のこと。
+**Firebase Messaging Delivery Priority** フィールドでは、「通常」または「高」のどちらの優先度でプッシュを Firebase Cloud Messaging に送信するかを制御できます。詳細については、[FCM のドキュメント](https://firebase.google.com/docs/cloud-messaging/concept-options#setting-the-priority-of-a-message)を参照してください。
 
 ## 要約テキスト
 
@@ -46,7 +46,7 @@ time-to-live (TTL)フィールドでは、プッシュ・メッセージング
 
 ## カスタムURI
 
-**カスタム URI** 機能を使用すると、通知がクリックされたときの誘導先 Web URL または Android リソースを指定できます。カスタム URI が指定されていない場合、通知をクリックするとユーザーはアプリに誘導されます。カスタムURIを使えば、アプリ内のディープリンクだけでなく、アプリ外に存在するリソースにもユーザーを誘導することができる。これは、私たちの\[Messaging API][13] ] またはプッシュ・コンポーザーの**設定で**指定できる。
+**カスタム URI** 機能を使用すると、通知がクリックされたときの誘導先 Web URL または Android リソースを指定できます。カスタム URI が指定されていない場合、通知をクリックするとユーザーはアプリに誘導されます。カスタム URI を使用してアプリ内でディープリンクしたり、アプリ外部のリソースにユーザーを誘導することができます。これは、\[メッセージング API][13] またはプッシュコンポーザーの \[**設定**] で指定できます。
 
 ![カスタムURI][12]
 
@@ -58,49 +58,49 @@ time-to-live (TTL)フィールドでは、プッシュ・メッセージング
 
 プッシュ通知の優先度レベルは、通知トレイ内で他の通知と比較して通知がどのように表示されるかに影響します。また、通常のメッセージや優先度の低いメッセージは、バッテリー寿命を延ばすために遅延がわずかに長くなったり、バッチ処理で送信されたりするのに対し、優先度の高いメッセージは常に即座に送信されるため、配信の速度と方法にも影響する可能性があります。
 
-この機能は、メッセージの重要度や一刻を争うかどうかに基づいてメッセージを区別するのに便利だ。たとえば、危険な道路状況についての通知は高い優先順位を受ける良い候補となるだろうし、進行中のセールについての通知は低い優先順位を受けるべきである。ユーザーの受信トレイで常にトップを占めたり、他の活動を邪魔したりすると、悪影響を及ぼす可能性があるからだ。
+この機能は、メッセージの重要度や一刻を争うかどうかに基づいてメッセージを区別するのに便利だ。例えば、危険な道路状況についての通知は高い優先度を付ける候補となり、実施中のセールについての通知は低い優先度を付けるべきです。送信する通知に邪魔になる優先度を実際に使用する必要があるかどうかをよく検討してください。常にユーザーの受信トレイのトップを占有したり、他のアクティビティを中断したりすると、マイナスの影響を与える可能性があります。
 
-Android O では、通知の優先度が通知チャネルのプロパティになりました。開発者と協力して設定中にチャネルの優先度を定義し、ダッシュボードを使用して通知音を送信するときに適切なチャネルを選択する必要があります。Android Oより前のバージョンを実行しているデバイスでは、BrazeダッシュボードとMessaging APIを介して、AndroidとFire OS通知の優先レベルを指定することができる。
+Android O では、通知の優先度が通知チャネルのプロパティになりました。開発者と協力して設定中にチャネルの優先度を定義し、ダッシュボードを使用して通知音を送信するときに適切なチャネルを選択する必要があります。Android O より前のバージョンを実行しているデバイスでは、Braze ダッシュボードとメッセージング API を介して、Android と Fire OS 通知の優先レベルを指定することができます。
 
-特定の優先順位で全ユーザーにメッセージを送るには、\[通知チャネル設定][17] （O+デバイスをターゲットにする）]から間接的に優先順位を指定し、ダッシュボードから個々の優先順位を送信する（<Oデバイスをターゲットにする）ことを推奨する。
+特定の優先度を指定したメッセージをユーザー群全体に送信するには、\[通知チャネル設定][17] (O 以降のデバイスを対象とする) を通じて間接的に優先度を指定し、ダッシュボードから個別の優先度を送信する (O より前のデバイスを対象とする) ことをお勧めします。
 
 AndroidまたはFire OSのプッシュ通知で設定できる優先度については、以下の表を参照のこと：
 
-| 優先順位 | 説明| `priority` 値（APIメッセージ用） |
+| 優先順位 | 説明| `priority` 値 （APIメッセージ用） |
 |------|-----------|----------------------------|
 | マックス | 緊急または一刻を争うメッセージ。 | `2` |
 | 高 | 友人からの新着メッセージなど、重要な連絡。 | `1` |
-| デフォルト | 最も多く通知されている。メッセージが他の優先度タイプのどれにも明確に該当しない場合に使用する。 | `0` |
+| デフォルト | ほとんどの通知。メッセージが他の優先度タイプのどれにも明確に該当しない場合に使用する。 | `0` |
 | 低 | ユーザーに知ってもらいたいが、すぐに行動を起こす必要のない情報。 | `-1`|
-| 最小 | 文脈や背景に関する情報。 | `-2`|
+| 最小 | コンテキストまたは背景情報 | `-2`|
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
-詳細については、Googleの[Android通知に関する][2]ドキュメントを参照のこと。
+詳細については、Google の [Android 通知][2]ドキュメントを参照してください。
 
 ## プッシュ・カテゴリー
 
 アンドロイドのプッシュ通知では、通知があらかじめ定義されたカテゴリーに入るかどうかを指定するオプションがある。AndroidシステムUIは、このカテゴリーを使用して、ユーザーの通知トレイのどこに通知を配置するかについて、ランキングやフィルタリングの決定を行うことができる。
 
-![Settings "タブで "Category "を "None "に設定する。][52]
+![「カテゴリー」が「なし」に設定されている \[設定] タブ (デフォルト設定)。][52]
 
 | カテゴリー | 説明 |
 |---|-------|
-| なし | デフォルトのオプションである。 |
+| なし | デフォルトのオプション。 |
 | アラーム | アラームまたはタイマー。 |
-| 電話 | 着信通話（音声またはビデオ）または同様の同期通信要求。 |
+| 電話 | 着信通話 （音声または動画） または同様の同期通信リクエスト。 |
 | メール | 非同期バルクメッセージ（電子メール）。 |
 | エラー | バックグラウンド操作または認証ステータスでエラーが発生した。 |
 | イベント | カレンダーのイベント。 |
-| メッセージ | ダイレクトメッセージ（SMS、インスタントメッセージなど）を受信する。 |
-| 進捗状況 | バックグラウンドで長時間実行されている操作の進行状況。 |
+| メッセージ | 着信ダイレクトメッセージ （SMS、インスタントメッセージなど）。 |
+| 進捗状況 | バックグラウンドで長時間実行される操作の進行状況。 |
 | プロモーション | プロモーションまたは広告。 |
-| 推薦 | 具体的でタイムリーな、ひとつのことを勧める。 |
+| レコメンデーション | 具体的でタイムリーな、ひとつのことを勧める。 |
 | リマインダー | ユーザーがスケジュールしたリマインダー。 |
 | サービス | バックグラウンドサービスを実行していることを示す。 |
 | ソーシャル | ソーシャルネットワークまたは共有の更新。 |
-| ステータス | デバイスやコンテキストの状態に関する継続的な情報。 |
-| システム | システムまたはデバイスのステータスが更新される。システム用に予約されている。 |
-| 輸送 | 再生用のメディア・トランスポート・コントロール。 |
+| ステータス | デバイスやコンテキストのステータスに関する継続的な情報。 |
+| システム | システムまたはデバイスのステータスが更新される。システム用に予約済み。 |
+| 輸送 | 再生用のメディアトランスポートコントロール。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## プッシュの視認性
@@ -116,7 +116,7 @@ AndroidまたはFire OSのプッシュ通知で設定できる優先度につい
 
 さらに、Androidユーザーは、端末の通知プライバシー設定を変更することで、プッシュ通知をロック画面に表示する方法を上書きすることができる。この設定は、プッシュ通知からの可視性を上書きする。
 
-![ダッシュボードのプッシュ優先順位は、可視性の設定が有効で、プライベートに設定されている。][53]{: style="float:right;max-width:60%;margin-left:15px;"}
+![視認性の設定が有効で、プライベートに設定されたダッシュボードのプッシュ優先度。][53]{: style="float:right;max-width:60%;margin-left:15px;"}
 
 デバイスの通知プライバシー設定が「**すべてのコンテンツを表示**」（デフォルト設定）であれば、可視性にかかわらず、すべての通知がユーザーのロック画面に表示される。同様に、通知のプライバシーが「**通知を表示しない**」に設定されている場合、通知はロック画面に表示されない。可視性は、通知プライバシーが「**機密コンテンツを隠す**」に設定されている場合にのみ効果がある。
 
@@ -130,13 +130,13 @@ Android O では、通知音は通知チャネルのプロパティになりま
 
 Android Oより前のバージョンのAndroidを搭載したデバイスでは、Brazeはダッシュボードのコンポーザーから個々のプッシュメッセージのサウンドを設定できる。これを行うには、デバイスのローカルサウンドリソースを指定します (例: `android.resource://com.mycompany.myapp/raw/mysound`)。 
 
-このフィールドで**Defaultを**選択すると、デバイスのデフォルトの通知音が再生される。これは、私たちの\[Messaging API][13] ] またはプッシュ・コンポーザーの**設定で**指定できる。
+このフィールドで \[**デフォルト**] を選択すると、デバイスのデフォルトの通知音が再生されます。これは、\[メッセージング API][13] またはプッシュコンポーザーの \[**設定**] で指定できます。
 
 ![][11]
 
-次に、ダッシュボードのプロンプトに完全なサウンドリソースURI（例えば、`android.resource://com.mycompany.myapp/raw/mysound` ）を入力する。
+次に、ダッシュボードのプロンプトに完全なサウンドリソース URI （例えば `android.resource://com.mycompany.myapp/raw/mysound`） を入力します。
 
-特定のサウンドで全ユーザーにメッセージを送るには、\[通知チャンネル設定][16] （O+デバイスをターゲットにする）]から間接的にサウンドを指定し、ダッシュボードから個々のサウンドを送信する（<Oデバイスをターゲットにする）ことを推奨する。
+特定のサウンドでメッセージをユーザー群全体に送信するには、\[通知チャネル設定][16] (O 以降のデバイスを対象とする) を通じて間接的にサウンドを指定し、ダッシュボードから個別のサウンドを送信する (O より前のデバイスを対象とする) ことをお勧めします。
 
 [2]: http://developer.android.com/design/patterns/notifications.html
 [9]: {% image_buster /assets/img_archive/summary_text.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/push/android/notification_channels.md b/_lang/ja/_user_guide/message_building_by_channel/push/android/notification_channels.md
index 13ab8187aed..543f1772217 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/push/android/notification_channels.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/push/android/notification_channels.md
@@ -3,101 +3,101 @@ nav_title: "通知チャネル"
 article_title: プッシュ通知チャネル 
 page_order: 4
 page_type: reference
-description: "このリファレンス記事では、Android O トランジション、Brazeにチャネルを追加する方法、フォールバック チャネルを設定する方法など、Android プッシュ通知 チャネルのトピックについて説明します。"
+description: "この記事では、Android O の移行、Braze にチャネルを追加する方法、フォールバックチャネルを設定する方法など、Android のプッシュ通知チャネルのトピックについて説明します。"
 platform: Android
 channel:
   - push
 
 ---
 
-# 通知チャネルs
+# 通知チャネル
 
-> [ 通知 Channels][1] は、O で追加されたプッシュ通知を整理する方法です。O で始まるすべてのプッシュ通知s には、メッセージの種類を示す通知 Channel が必要です(たとえば、"chat 通知 s," または"follow 通知 s")。ユーザーは、個々のチャンネルに基づいて通知の側面(例えば、スヌーズ、ノイズ/バイブレーション設定s、オプトアウトなど)をコントロールできます。
+> [通知チャネル][1]では、Android O で追加されたプッシュ通知を整理することができます。O で始まるすべてのプッシュ通知には、メッセージの種類 (「チャット通知」や「フォロー通知」など) を示す通知チャネルが必要です。これにより、ユーザーは個々のチャネルに基づいて通知のコントロール機能 (例えば、スヌーズ、ノイズ/バイブレーション設定、オプトアウトなど) を操作できます。
 
 ## Android Oへの遷移
 
-通知チャネルs は、アプリライセンスのコードでのみ作成でき、Braze ダッシュボードでプログラムで作成することはできません。必要な通知 チャネルs がダッシュボードに適切に追加されるように、開発チームがマーケターs と連携することをお勧めします。
+通知チャネルは、アプリケーションのコード内でのみ作成でき、Braze ダッシュボードでプログラムを使って作成することはできません。必要な通知チャネルがダッシュボードに適切に追加されるように、開発チームとマーケターが協力して作業を進めるようにしてください。
 
-Android O 以降では、プッシュ通知 s はディスプレイに有効なチャネルを必要とします。アプリがAndroid O 以降を対象としている場合は、Braze SDK 2.1.0 以降を使用する必要があります。開発チームは、使用するチャネルと、推奨される通知 設定(たとえば、重要度、サウンド、ライト)を、アプリライケーションコードのチャネルごとに定義する必要があります。Android の開発者 ドキュメント [ここで][4] とBraze の開発者 ドキュメント [が見つかります。][2]
+Android O 以降、プッシュ通知を表示するために有効なチャネルが必要になります。アプリが Android O 以降をターゲットとしている場合は、Braze SDK 2.1.0 以降を使用する必要があります。開発チームは、使用するチャネルと、推奨される通知設定 (例えば重要度、サウンド、ライトなど) を、アプリケーションコード内でチャネルごとに定義する必要があります。Android の開発者ドキュメントは[こちら][4]、Braze の開発者ドキュメントは[こちら][2]を参照してください。
 
 {% alert note %}
-Android はローカライゼーション でチャネルの名前をサポートしているため、1 つのチャネル ID をチャネルの名前の多重変換に関連付けることがアプリライセンスのコードで可能です。
+Android はチャネル名のローカライゼーションをサポートしているため、アプリケーションのコードで 1 つのチャネル ID を多言語によるチャネル名に関連付けることが可能です。
 {% endalert %}
 
-これらのチャネルが作成されると、エンジニアは関連するチャネルID をマーケティングチームに渡す必要があります。キャンペーンとキャンバスで使用するチャネルの名前とチャネルID をBraze ダッシュボードに入力する必要があります。
+これらのチャネルが作成されると、エンジニアは関連するチャネルID をマーケティングチームに渡す必要があります。キャンペーンとキャンバスで使用できるよう、チャネル名とチャネル ID は Braze ダッシュボードに入力する必要があります。
 
-チャネルをBraze ダッシュボードに追加するには、Android プッシュコンポーザーに移動し、通知 チャネル s フィールドを選択して"manage チャネル s." を選択します。
+チャネルを Braze ダッシュボードに追加するには、Android プッシュ通知作成画面に移動し、通知チャネルフィールドを選択して「チャネルを管理」を選択します。
 {% alert important %}
-"manage アプリ S"を含む権限を持つユーザーのみが、チャネルSを管理できます。
+チャネルを管理できのは「アプリを管理」を含む権限を持つユーザーのみです。
 {% endalert %}
 
 ## SDK デフォルト チャネル
 
-Android では、API レベル26 (Android O) 以降でプッシュ通知s を表示するために有効なチャネルが必要です。Braze Android SDK 2.1.0 には、"General,"というデフォルト チャネルが含まれています。これは、ダッシュボードで追加のチャネルs を指定しない場合や、無効なチャネルに送信しようとした場合に作成され、使用されます。SDKでこのラベルの名前を変更し、チャネルの説明を指定できます。より良いユーザーエクスペリエンスを提供するために、これを考慮することをお勧めします。  
+Android では、API レベル 26 (Android O) 以降でプッシュ通知を表示するために、有効なチャネルが必要です。Braze Android SDK 2.1.0 には、「General」というデフォルトのチャネルが含まれています。これは、ダッシュボードで追加のチャネルを指定しない場合や、無効なチャネルに送信しようとした場合に作成され、使用されます。SDK でこのラベルの名前を変更し、チャネルの説明を指定することができます。より良いユーザーエクスペリエンスを提供するために、これを考慮することをお勧めします。  
 
-チャネルがアプリアプリケーションに追加されたら、削除することができます。ただし、消費者 s は、削除されたチャネルの個数をいつでも確認できます\[].\[3] Braze ダッシュボードは、プログラムによるチャネル s の作成をサポートしていません。チャネル s は、シームレスなエクスペリエンスを提供するために、アプリライセンスのコードで作成および定義する必要があります。
+アプリケーションに追加されたチャネルは、必要に応じて削除できます。ただし、消費者は、\[削除]\[3] されたチャネルの個数をいつでも確認できます。Braze ダッシュボードは、プログラムによるチャネルの作成をサポートしていません。チャネルは、シームレスなエクスペリエンスを提供するために、アプリケーションのコード内で作成して定義する必要があります。
 
 ここでも、開発チームと連携して、Android O をターゲットにするためのシームレスな移行を確実にすることをお勧めします。
 
 ## ダッシュボードフォールバック チャネル
 
-Braze では、ダッシュボード フォールバック チャネルを指定できます。ダッシュボード フォールバック チャネルの目的は、明示的なチャネル選択なしで、レガシープッシュメッセージのためのチャネル IDを提供することである。チャネル選択をAndroidプッシュコンポーザでチャネルを選択すると定義した。
+Braze では、ダッシュボード フォールバック チャネルを指定できます。ダッシュボードにあるフォールバックチャネルの目的は、チャネルが明示的に選択されていないレガシープッシュメッセージ用のチャネル ID を提供することにあります。チャネル選択をAndroidプッシュコンポーザでチャネルを選択すると定義した。
 
 チャネルが選択されていないメールはダッシュボード フォールバック チャネル番号とともに送信されます。ダッシュボード フォールバック チャネルを変更すると、チャネルが明示的に選択されていないメッセージが、新しいフォールバック チャネルのID とともに送信されます。
 
 次に、ダッシュボード フォールバック チャネルの想定される動作のサンプルを示します。
 
-ダッシュボード フォールバック チャネルは"Marketing&quot と呼ばれ、チャネルを選択したことがない10個のAndroidプッシュメッセージがあります。これらのキャンペーンは"Marketing"チャネルを介して送信されます。これは、"Marketing"チャネルがダッシュボード フォールバック チャネルであるためです。
+貴社のダッシュボードフォールバックチャネルは「マーケティング」と呼ばれ、チャネルを選択したことがない Android プッシュメッセージが 10 個あるとします。これらのキャンペーンは「マーケティング」チャネルを介して送信されます。これは、「マーケティング」チャネルがダッシュボードフォールバックチャネルであるためです。
 
-さらに、"Social Notifications" チャネルを通して送信することを選択した15のメッセージと、"Marketing"チャネルを通して送信することを選択した5つのメッセージがあります。
+さらに、「ソーシャル通知」チャネルを介して送信することを選択した 15 個のメッセージと、「マーケティング」チャネルから送信することを選択した 5 個のメッセージがあります。
 
-次に、ダッシュボード デフォルト チャネルを"Marketing"から"Updates"に変更します。
+次に、ダッシュボードデフォルトチャネルを「マーケティング」から「更新」に変更します。
 
-この場合、以前に"Marketing"チャネルを介して送信されたチャネル選択のない10個のキャンペーンsはすべて、"Updates"チャネルを介して送信されます。これは、これらのメッセージがフォールバック チャネルを介して送信されるためです。"Social Notifications&quotを通じて送信された15のメッセージ; チャネルは、"Social Notifications" チャネルを通じて引き続き送信されます。"Marketing"チャネルを通じて送信された5つのメッセージは、"Marketing"チャネルを通じて引き続き送信されます。
+この場合、以前に「マーケティング」チャネルを介して送信されていた、チャネル選択のない 10 個のキャンペーンはすべて「更新」チャネルから送信されます。これは、これらのメッセージがフォールバックチャネルを介して送信されるためです。「ソーシャル通知」チャネルを介して送信された 15 個のメッセージは、引き続き「ソーシャル通知」チャネルから送信されます。「マーケティング」チャネルを介して送信された 5 個のメッセージは、引き続き「マーケティング」チャネルから送信されます。
 
-不正なチャネル IDがBrazeに提供された場合(開発者sがSDKで作成しなかったチャネル IDを提供した場合など)は、通知をあなたのSDK デフォルト チャネルを通じて配信します。そのため、開発中はBrazeのダッシュボードを介して通知 チャネルをテストすることを強くお勧めします。
+Braze に無効なチャネル ID が提供された場合 (開発者が SDK で作成しなかったチャネル ID を提供した場合など) は、これらの通知は貴社の SDK デフォルトチャネルを介して配信されます。そのため、開発中はBrazeのダッシュボードを介して通知 チャネルをテストすることを強くお勧めします。
 
-チャネルs の予想される動作をよりよく理解するには、次のテーブルを参照してください。
+チャネルの予想される動作をよりよく理解するには、次の表を参照してください。
 
-|シナリオ |転帰  |    
+|シナリオ |結果  |    
 | ---|-------------
-|**企業ABC**Android OをサポートするSDKへの更新s<br>**Company ABC**はBraze ダッシュボードにチャネルsを追加しません<br>**企業ABC**はSDK デフォルト チャネルの名前を変更しません | プッシュ通知s はAndroid O 機器に送信され、"General"と呼ばれるチャネルを作成します。通知s は"General" チャネルを介して送信されます
-|**Company XYZ** Android O をサポートするSDKへの更新s <br>**Company XYZ**は、Braze ダッシュボードにチャネルsを追加しません<br>**Company XYZ** SDK デフォルト チャネルの名前を"Marketing&quot に変更します。 | プッシュ通知sがAndroid O機器に送信されると、"Marketing&quotというチャネルが作成され、通知sが"Marketing"チャネルを通じて送信されます
-|**企業LMN**Android OをサポートするSDKへの更新s <br>**Company LMN** は、アプリライセンスコード、"Promotions"および"Order Updates"の2 つのチャネルを定義します。 <br>**Company LMN** は、"Promotions"および"Order Updates"のチャネルID をBraze ダッシュボードに追加します <br>**Company LMN** は"Promotions" をダッシュボード フォールバック チャネルとして指定します<br>**Company LMN** SDK デフォルト チャネルの名前を"Marketing&quot に変更します。 | プッシュ通知s がAndroid O 機器に送信されてもチャネルは作成されません<br><br>マーケターが、通知が"Order Updates"または"Marketing"チャネルを経由して送信することを明示的に指定しない限り、sがチャネルに追加される以前に作成されたすべての通知sは、"Promotions"チャネルを通じてダッシュボードに送信されます<br><br>SDK デフォルト チャネル"Marketing"は、企業が不正なチャネル IDを介して通知を送信しようとした場合、または明示的に選択された場合にのみ作成され使用されます
-|**企業HIJ**更新 s to Android O しかし2.1.0 以降にBraze Android SDKしない | Android O以降を実行しているユーザーに送信された通知が耳元にアプリされない |
+|**ABC 社**が Android O 対応の SDK に更新する<br>**Company ABC**はBraze ダッシュボードにチャネルsを追加しません<br>**企業ABC**はSDK デフォルト チャネルの名前を変更しません | Android O デバイスにプッシュ通知が送信されると「General」というチャネルが作成され、通知は「General」チャネルを介して送信されます。
+|**XYZ 社**が Android O 対応の SDK に更新する <br>**XYZ 社**は Braze ダッシュボードにチャネルを追加しない<br>**XYZ 社**が SDK デフォルトチャネルの名前を「マーケティング」に変更する | Android O デバイスにプッシュ通知が送信されると「マーケティング」というチャネルが作成され、通知は「マーケティング」チャネルを介して送信されます。
+|**LMN 社**が Android O 対応の SDK に更新する <br>**LMN 社**がアプリケーションコードに「プロモーション」と「注文更新」という 2 つのチャネルを定義する <br>**LMN 社**が「プロモーション」と「注文更新」のチャネル ID を Braze ダッシュボードに追加する <br>**LMN 社**が「プロモーション」をダッシュボードフォールバックチャネルとして指定する<br>**LMN 社**が SDK デフォルトチャネルの名前を「マーケティング」に変更する | プッシュ通知s がAndroid O 機器に送信されてもチャネルは作成されません<br><br>マーケターが通知を「注文更新」または「マーケティング」チャネル経由で送信するよう明示的に指定しない限り、チャネルが追加される以前に作成されたすべての通知は、「プロモーション」チャネルを介してダッシュボードに送信されます。<br><br>SDK デフォルトチャネルである「マーケティング」は、同社が無効なチャネル ID を介して通知を送信しようとした場合、またはこれが明示的に選択された場合にのみ作成され使用されます。
+|**HIJ 社**は Android O に更新したが、Braze Android SDK を 2.1.0 以降に更新しない | Android O以降を実行しているユーザーに送信された通知が耳元にアプリされない |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## Braze ダッシュボードへのチャネルの追加
 
-1. キャンペーンまたはキャンバスを開き、**キャンペーンの編集**をクリックします。
+1. Android プッシュ通知を含むキャンペーンまたはキャンバスを開き、\[**キャンペーンを編集**] をクリックします。
 2. Androidのプッシュメッセージ作成画面に移動します。
-3. **Notification Channels**をクリックします。ここに追加されたすべてのチャネルは、すべてのキャンペーンとキャンバスでグローバルに使用できます。ワークスペースがチャネルを管理するには、"Apps&quot の管理; [permissions]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#limited-and-team-role-permissions) が必要です。
+3. \[**通知チャネルを管理**] をクリックします。ここに追加されたすべてのチャネルは、すべてのキャンペーンとキャンバスでグローバルに使用できます。ワークスペースがチャネルを管理するには、「アプリを管理」[権限]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#limited-and-team-role-permissions)が必要です。
 
-アプリする通知 チャネルを特定のキャンペーンまたはキャンバスステップに移動すると、**到達可能なユーザ** タリー(ターゲットオーディエンスステップにあります)は、Androidプッシュの耳は変わりません。ただし、選択した通知 チャネルにサブスクライブされているユーザーのみがメッセージを表示し、このオーディエンスに基づいてキャンペーン 分析(クリックなど) が測定されます。
+通知チャネルを特定のキャンペーンまたはキャンバスステップに適用すると、Android プッシュ通知の**到達可能なユーザー数**の統計 (ターゲットオーディエンスステップにあります) は変更されません。ただし、選択した通知 チャネルにサブスクライブされているユーザーのみがメッセージを表示し、このオーディエンスに基づいてキャンペーン 分析(クリックなど) が測定されます。
 
 ![][6]
 
 {:start="4"}
-4\.**Add Notification Channel**をクリックします。
-5\.追加する通知 チャネルの名前とID を入力します。<br><br>![][8]<br><br>
-6. 追加する通知 チャネルごとにステップs 4 と5 を繰り返します。
+4\.\[**通知チャネルを追加**] をクリックします。
+5. 追加する通知 チャネルの名前とID を入力します。<br><br>![][8]<br><br>
+6. 追加する通知チャネルそれぞれについてステップ 4 と 5 を繰り返します。
 7. **Save** を押して変更を保存します。
 
 ## フォールバック チャネルの指定
 
-フォールバック チャネルは、メッセージのチャネルを選択していない場合にBrazeがAndroidメッセージを送信しようとするチャネルです。キャンペーンとキャンバスでAndroidのメッセージがチャネル選択されていないものは、チームがチャネルをBraze ダッシュボードに追加する前に作成された「キャンペーン」と「キャンバス」だけです。フォールバック チャネルを変更すると、変更内容は、明示的なチャネル選択なしに、すべてのキャンペーンとキャンバスにアプリ反映されます。
+フォールバック チャネルは、メッセージのチャネルを選択していない場合にBrazeがAndroidメッセージを送信しようとするチャネルです。キャンペーンとキャンバスでAndroidのメッセージがチャネル選択されていないものは、チームがチャネルをBraze ダッシュボードに追加する前に作成された「キャンペーン」と「キャンバス」だけです。フォールバックチャネルを変更すると、変更内容は、明示的なチャネル選択なしに、すべてのキャンペーンとキャンバスにグローバルに適用されます。
 
-1. キャンペーンまたはキャンバスを開きます。
-2. Androidのプッシュコンポーザーに移動します。
+1. 既存のキャンペーンまたはキャンバスを開きます。
+2. Android のプッシュ通知作成画面に移動します。
 3. 通知 チャネル項目を展開した後、**管理通知 チャネルs**を選択します。<br><br>![][9]{: style="max-width:80%;"}<br><br>
 4. チャネルをダッシュボードに追加します(まだ追加されていない場合)。
 5. フォールバック チャネルとして指定したいチャネルの横にあるラジオダイアルを選択します。
-6. 変更を保存します。あなたの変更はアプリグローバルに横たわっているでしょう。
+6. 変更を保存します。変更はグローバルに適用されます。
 
 ## Androidプッシュメッセージへのチャネルの追加
 
 1. 任意のキャンペーンまたはキャンバスのAndroidプッシュコンポーザーに移動します。
-2. 使用するチャネルをドロップダウンから選択します。ドロップダウンがなく、次のビューがある場合は、チャネルs を追加してから、キャンペーンs を選択する必要があります。
+2. 使用するチャネルをドロップダウンから選択します。ドロップダウンがなく、次のビューがある場合は、まずチャネルを追加してからキャンペーンを選択する必要があります。
 
 ![][10]
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/push/best_practices/push_primer_messages.md b/_lang/ja/_user_guide/message_building_by_channel/push/best_practices/push_primer_messages.md
index 1ea83e3a04d..9aeffba5d11 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/push/best_practices/push_primer_messages.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/push/best_practices/push_primer_messages.md
@@ -8,13 +8,13 @@ channel: push
 
 ---
 
-# アプリ内メッセージをプッシュする
+# アプリ内メッセージのプッシュプライマー
 
-![ストリーミングアプリのアプリ内メッセージをプッシュする。この通知には「Movie Cannonからプッシュ通知を受け取りますか？通知には新作映画やテレビ番組、その他のお知らせが含まれることがあり、いつでもオフにすることができる。"][1]{: style="float:right;max-width:40%;margin-left:15px;border:none;"}
+![ストリーミングアプリのアプリ内メッセージのプッシュプライマー。この通知は、「Movie Cannon からプッシュ通知を受け取りますか? 通知には新作映画やテレビ番組、その他のお知らせが含まれることがあり、いつでもオフにすることができます」というものです。][1]{: style="float:right;max-width:40%;margin-left:15px;border:none;"}
 
 > ユーザーにプッシュ許可を求めるチャンスは一度しかないため、プッシュ登録を最適化することは、プッシュメッセージのリーチを最大化するために極めて重要である。これを実現するには、アプリ内メッセージを使って、ユーザーがオプトインを選択した場合、どのようなメッセージを受け取ることが期待できるかを、ネイティブのプッシュプロンプトを表示する前に説明すればよい。これはプッシュ・プライマーと呼ばれる。
 
-Brazeでアプリ内プッシュプライマーメッセージを作成するには、iOS、Android、Web用のアプリ内メッセージを作成する際に、ボタンオンクリック時の動作「Request Push Permission」を使用する。
+Braze でプッシュプライマーのアプリ内メッセージを作成するには、iOS、Android、または Web のアプリ内メッセージを作成するときに、ボタンのクリック時動作「プッシュ通知の権限を要求」を使用できます。
 
 ## 前提条件
 
@@ -26,41 +26,41 @@ Brazeでアプリ内プッシュプライマーメッセージを作成するに
 
 #### Android
 
-- **アンドロイド12歳以下：**プッシュはデフォルトでオプトインされているため、プッシュ・プライマーの実装は推奨されない。
-- **アンドロイド13以上：**テスト中に何度もプロンプトを表示させたい場合は、デバイスの設定でアプリのプッシュを無効にし、再度プロンプトを表示できるようにする。
+- **Android 12 以下: **プッシュはデフォルトでオプトインされているため、プッシュプライマーの実装は推奨しません。
+- **Android 13 以上: **テスト中にプロンプトを何度か表示したい場合は、デバイス設定に入り、アプリのプッシュを無効にして、プライマーを再度表示できるようにします。
 
 #### iOS
 
 - iOSプロンプトは、オペレーティングシステムによって強制され、1回のインストー ルにつき1回しか表示できない。
-- アプリのプッシュ設定が明示的にオンまたはオフの場合、プロンプトは表示されず、[仮承認の](https://developer.apple.com/documentation/usernotifications/asking_permission_to_use_notifications#3544375)ユーザーにのみ表示される。
-  - アプリのプッシュ設定がオンになっている場合、ユーザーはすでにオプトインしているため、Brazeはアプリ内メッセージを表示しない。
+- アプリのプッシュ設定が明示的にオンまたはオフの場合、プロンプトは表示されません。プロンプトは[暫定承認](https://developer.apple.com/documentation/usernotifications/asking_permission_to_use_notifications#3544375)を得たユーザーにのみ表示されます。
+  - アプリのプッシュ設定がオンになっている場合、ユーザーがすでにオプトインしているため、Braze はアプリ内メッセージを表示しません。
   - アプリのプッシュ設定がオフになっている場合は、設定アプリでアプリの通知設定にユーザーを転送する必要がある。
 
 ##### 手動でコードを除去する
 
-このチュートリアルを使って設定したアプリ内メッセージは、ユーザーがアプリ内メッセージボタンをクリックすると、ネイティブのプッシュ・プロンプト・コードを自動的に呼び出す。プッシュ通知の許可を2度要求したり、間違ったタイミングで要求したりするのを避けるため、開発者は実装した既存のプッシュ通知統合を修正し、アプリ内メッセージがユーザーに最初に表示されるプッシュ通知プリマーになるようにする必要がある。
+このチュートリアルを使って設定したアプリ内メッセージは、ユーザーがアプリ内メッセージボタンをクリックすると、ネイティブのプッシュ・プロンプト・コードを自動的に呼び出す。プッシュ通知の許可を 2 回要求したり、間違った時間に要求したりしないようにするには、開発者は、実装されている既存のプッシュ通知統合を変更して、アプリ内メッセージがユーザーに表示される最初のプッシュ通知プライマーであることを確認する必要があります。
 
 開発者は、アプリやサイトのプッシュ通知の実装を見直し、プッシュ許可を要求するようなコードを手動で削除すべきである。例えば、以下のコードへの参照を探し、削除する：
 
 {% tabs %}
-{% tab 目標-C %}
+{% tab OBJECTIVE-C %}
 ```objc
 requestAuthorizationWithOptions
 ```
 {% endtab %}
-{% tab 速い %}
+{% tab swift %}
 ```swift
 requestAuthorization
 ```
 {% endtab %}
-{% tab ジャバスクリプト %}
+{% tab JavaScript %}
 ```javascript
 braze.requestPushPermission()
 // or
 appboy.registerAppboyPushMessages()
 ```
 {% endtab %}
-{% tab ジャワ %}
+{% tab Java %}
 ```java
 android.permission.POST_NOTIFICATIONS
 ```
@@ -69,36 +69,36 @@ android.permission.POST_NOTIFICATIONS
 
 ## ステップ 1:アプリ内メッセージを作成する
 
-\[通常通り、アプリ内メッセージ][2] を作成する。
+通常どおり \[アプリ内メッセージを作成][2] します。
 
-メッセージの種類とレイアウトを選択する。ユーザーが期待するプッシュ通知の内容を説明するのに十分なスペースを確保するため（そしてボタンが使えるようにするため）、Brazeはフルスクリーンかモーダルメッセージのどちらかを提案する。フルスクリーンのアプリ内メッセージには画像が必要である。 
+メッセージの種類とレイアウトを選択する。ユーザーが期待するプッシュ通知の内容を説明するのに十分なスペースを確保するため（そしてボタンが使えるようにするため）、Brazeはフルスクリーンかモーダルメッセージのどちらかを提案する。全画面のアプリ内メッセージの場合は画像が必要なことに注意してください。 
 
 ## ステップ 2:メッセージを構築する
 
-さて、いよいよコピーを加える番だ！プッシュ・プライマーは、ユーザーにプッシュ通知をオンにするよう促すものであることを忘れてはならない。メッセージ本文では、ユーザーがプッシュ通知をオンにすべき理由を強調することをお勧めする。どのような種類の通知を送りたいのか、どのような価値を提供できるのか、具体的に説明すること。
+さて、いよいよコピーを加える番だ！ここで、プッシュプライマーは、プッシュ通知をオンにするようにユーザーをプライミングする必要があることに注意してください。メッセージ本文では、ユーザーがプッシュ通知をオンにすべき理由を強調することをお勧めする。どのような種類の通知を送りたいのか、どのような価値を提供できるのか、具体的に説明すること。
 
 例えば、あるニュースアプリは次のようなプッシュ・プライマーを使うかもしれない：
 
-> 外出先でニュース速報プッシュ通知を有効にして、あなたにとって重要な記事やトピックのアラートを受け取ろう。
+> 外出先でニュース速報プッシュ通知を有効にすると、重要なストーリーやトピックに関するアラートが表示されます。
 
-ストリーミング・アプリは次のような使い方をするかもしれない：
+ストリーミングアプリでは、次が使用される場合があります。
 
-> Movie Cannonからのプッシュ通知を受け取る？通知には新作映画やテレビ番組、その他のお知らせが含まれることがあり、いつでもオフにすることができる。
+> Movie Cannon からプッシュ通知を取得しますか?通知には新作映画やテレビ番組、その他のお知らせが含まれることがあり、いつでもオフにすることができる。
 
-ベスト・プラクティスと追加リソースについては、\[カスタム・オプトイン・プロンプトの作成][3] を参照のこと。
+ベストプラクティスとその他のリソースについては、\[カスタムオプトインプロンプトの作成][3] を参照してください。
 
-## ステップ 3:ボタンの動作を指定する {#button-actions}
+## ステップ 3:ボタン動作を指定する {#button-actions}
 
-アプリ内メッセージにボタンを追加するには、**Button 1と** **Button 2の**テキストフィールドにテキストを追加する。私たちは、「通知を許可する」と「今は許可しない」をスターターボタンとして推奨しているが、割り当て可能なボタンのプロンプトはたくさんある。
+アプリ内メッセージにボタンを追加するには、\[**ボタン 1**] と \[**ボタン 2**] のテキストフィールドにテキストを追加します。これらがアプリ内メッセージのプライマリボタンとセカンダリボタンになります。ボタンテキストには「通知を許可する」と「今は許可しない」をお勧めしますが、割り当てることのできるボタンプロンプトはたくさんあります。
 
 ボタンコピーを追加したら、各ボタンのクリック時の動作を指定する：
 
-- **ボタン 1:**メッセージを閉じる」に設定する。これはセカンダリー・ボタン、つまり「今ではない」オプションだ。
-- **ボタン2：**これを "Request Push Permission "に設定する。これがプライマリー・ボタン、つまり「通知を許可する」オプションだ。
+- **ボタン 1:**これを「メッセージを閉じる」に設定します。これはセカンダリーボタンで「今は許可しない」オプションです。
+- **ボタン 2: **これを「プッシュ通知の権限を要求」に設定します。これはプライマリボタンで「通知を許可する」オプションです。
 
 ![][4]
 
-## ステップ 4:スケジュール・デリバリー
+## ステップ 4:配信のスケジュール
 
 プッシュプライマーを適切な時間に送信するように設定するには、アプリ内メッセージをアクションベースのメッセージとしてスケジュールし、トリガーアクションとして**カスタムイベントを実行する**必要がある。
 
@@ -106,11 +106,11 @@ android.permission.POST_NOTIFICATIONS
 
 ![][5]
 
-## ステップ 5: 対象ユーザー
+## ステップ 5: ユーザーのターゲット設定
 
-プッシュプライマーキャンペーンの目的は、ユーザーにプッシュメッセージのオプトインを促すことなので、すでにオプトインしているユーザーをターゲットにすることは避けたい。そのためには、`Push Subscription Status is not Opted In` にセグメントまたはフィルターを追加する。
+プッシュプライマーキャンペーンの目的は、ユーザーにプッシュメッセージングのオプトインを促すことなので、すでにオプトインしているユーザーをターゲットにすることは避けます。そのためには、`Push Subscription Status is not Opted In` にセグメントまたはフィルターを追加する。
 
-そのうえで、どのような追加セグメントが最も適切かを決めることができる。例えば、2回目の購入を完了したユーザー、会員になるためにアカウントを作成したばかりのユーザー、あるいは週に2回以上アプリを訪れるユーザーなどをターゲットにすることができる。これらの重要なセグメントにユーザーをターゲティングすることで、ユーザーがオプトインし、プッシュを有効にする可能性が高まる。
+そのうえで、どのような追加セグメントが最も適切だと感じるかを決めることができます。例えば、2回目の購入を完了したユーザー、会員になるためにアカウントを作成したばかりのユーザー、あるいは週に2回以上アプリを訪れるユーザーなどをターゲットにすることができる。これらの重要なセグメントでユーザーをターゲティングすることで、ユーザーがオプトインし、プッシュを有効にする可能性が高くなります。
 
 ## ステップ 6:コンバージョンイベント
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/push/creating_a_push_message.md b/_lang/ja/_user_guide/message_building_by_channel/push/creating_a_push_message.md
index 4cb1cb2b028..b1702f38f09 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/push/creating_a_push_message.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/push/creating_a_push_message.md
@@ -16,7 +16,7 @@ tool:
 
 プッシュ通知の事例をご覧になりたい方は、\[ケーススタディ][8] をご覧いただきたい。
 
-## ステップ 1:メッセージを発信する場所を選ぶ {#create-new-campaign-push}
+## ステップ 1: メッセージを発信する場所を選ぶ {#create-new-campaign-push}
 
 メッセージは、キャンペーンとキャンバスのどちらを使用して配信すべきでしょうか。キャンペーンは単一のシンプルなメッセージングキャンペーンに適していますが、キャンバスはマルチステップのユーザーのジャーニーに適しています。
 
@@ -25,8 +25,8 @@ tool:
 
 **ステップ:**
 
-1. **Messaging**>**Campaignsに**進み、**Create Campaignを**クリックする。
-2. **プッシュ通知」を**選択するか、複数のチャネルを対象とするキャンペーンの場合は「**マルチチャネルキャンペーン**」を選択する。
+1. \[**メッセージング**] > \[**キャンペーン**] に移動し、\[**キャンペーンを作成**] をクリックします。
+2. \[**プッシュ通知**] を選択するか、複数のチャネルをターゲットとするキャンペーンの場合は \[**マルチチャネルキャンペーン**] を選択します。
 3. キャンペーンに、明確で意味のある名前を付けます。
 4. 必要に応じて、\[[チーム]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/teams/)] と \[[タグ]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/)] を追加します。
    * タグを使用すると、キャンペーンを検索してレポートを作成しやすくなります。例えば、\[[レポートビルダー]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/)] を使用する場合、特定のタグでフィルターできます。
@@ -38,11 +38,11 @@ tool:
 
 マルチチャンネルまたはプッシュ通知キャンペーンを作成する前に、以下の決定チャートを参照のこと：
 
-![「キャンペーンタイプを選択するためのフローチャート。複数のデバイスやプラットフォームをターゲットにしているかどうかを決めることから始める。いいえ」の場合は、「プッシュ通知を選択」につながる。はい」の場合、「どのようなプッシュメッセージのタイプですか」と尋ねられ、選択肢は「標準的なプッシュ」となり、「デバイス固有の設定を使用する必要がありますか」という判断ポイントにつながる。いいえ」の場合は、「プッシュ通知を選択し、クイックプッシュを使用する」につながる。イエスなら、『マルチチャンネルの選択』に進む。どのようなプッシュメッセージのタイプですか」に戻り、答えが「プッシュストーリーまたはインライン画像」であれば、「マルチチャンネルを選択してください」]({% image_buster /assets/img_archive/flowchart_quickpush.png %})
+![「キャンペーンタイプを選択するためのフローチャート。まず、複数のデバイスやプラットフォームをターゲットにしているかどうかを決定します。「いいえ」の場合は、「プッシュ通知を選択」につながります。はい」の場合、「どのようなプッシュメッセージのタイプですか」と尋ねられ、選択肢は「標準的なプッシュ」となり、「デバイス固有の設定を使用する必要がありますか」という判断ポイントにつながる。いいえ」の場合は、「プッシュ通知を選択し、クイックプッシュを使用する」につながる。イエスなら、『マルチチャンネルの選択』に進む。どのようなプッシュメッセージのタイプですか」に戻り、答えが「プッシュストーリーまたはインライン画像」であれば、「マルチチャンネルを選択してください」]({% image_buster /assets/img_archive/flowchart_quickpush.png %})
 
 **プッシュ通知を**選択し、複数のデバイスとプラットフォームをターゲットに選択すると、自動的にクイックプッシュキャンペーンが作成される。クイックプッシュでは、特定のデバイス固有の設定は利用できない：
 
-- アクションボタンを押す
+- プッシュアクションボタン
 - 通知チャネルとグループ
 - プッシュ・タイム・トゥ・ライブ（TTL）
 - 表示優先度
@@ -64,33 +64,33 @@ tool:
 1. キャンバス作成ツールを使用して \[[キャンバスを作成]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)] します。
 2. キャンバスを設定したら、キャンバスビルダーにステップを追加します。ステップに、明確で意味のある名前を付けます。
 3. \[[ステップスケジュール]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/time_based_canvas/#schedule-delay)] を選択し、必要に応じて遅延を指定します。
-4. このステップでは、必要に応じて聴衆をフィルタリングする。セグメントを指定し、フィルターを追加して、このステップの受信者をさらに絞り込むことができます。後から、メッセージの送信時に、オーディエンスオプションがチェックされます。
+4. 必要に応じて、このステップのオーディエンスをフィルターします。セグメントを指定し、フィルターを追加して、このステップの受信者をさらに絞り込むことができます。後から、メッセージの送信時に、オーディエンスオプションがチェックされます。
 5. \[[昇進動作]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/advancement/)] を選択します。
 6. メッセージと組み合わせる他のメッセージングチャネルを選択します。
 
 {% endtab %}
 {% endtabs %}
 
-## ステップ 2:配信プラットフォームを指定する
+## ステップ 2: 配信プラットフォームを指定する
 
-まず、どのデバイスとプラットフォームの組み合わせでプッシュを受け取るかを選択する。プッシュ通知の配信を特定のアプリに限定するには、この選択を使用する。
+まず、どのデバイスとプラットフォームの組み合わせでプッシュを受け取るかを選択する。この選択を使用して、プッシュ通知の配信をアプリの特定のグループに制限します。
 
 これまでの選択によって、いくつかの方法がある：
 
-| 前選考 | options |
+| 前に選択したもの | options |
 | --- | --- | 
-| プッシュ通知キャンペーン | 1つまたは複数のプラットフォームとデバイスを選択する。複数のデバイスやプラットフォームをターゲットに選ぶと、自動的にクイックプッシュキャンペーンが作成される。これにより、1つのエディターで選択したすべてのプラットフォームに対して1つのメッセージを作成するために最適化された編集エクスペリエンスが提供される。この編集エクスペリエンスで何が違うかについては、[クイック・プッシュ・キャンペーンを]({{site.baseurl}}/quick_push)参照のこと。 |
-| マルチチャンネル・キャンペーン | **Add Messaging Channelを**クリックして、プッシュ・プラットフォームを追加する。プラットフォームの選択はそれぞれのバリアントに特有であるため、プラットフォームごとにメッセージのエンゲージメントをテストしてみることができる。
-| キャンバス | メッセージ・ステップで、**「+ Add more**」をクリックし、プッシュ・プラットフォームを追加する。マルチチャネルキャンペーンと同様、プラットフォームの選択は、それぞれのバリアントに特化している。 |
+| プッシュ通知キャンペーン | 1 つまたは複数のプラットフォームとデバイスを選択します。複数のデバイスやプラットフォームをターゲットに選ぶと、自動的にクイックプッシュキャンペーンが作成される。これにより、1つのエディターで選択したすべてのプラットフォームに対して1つのメッセージを作成するために最適化された編集エクスペリエンスが提供される。この編集エクスペリエンスで何が違うかについては、[クイック・プッシュ・キャンペーンを]({{site.baseurl}}/quick_push)参照のこと。 |
+| マルチチャンネル・キャンペーン | \[**メッセージングチャネルを追加**] をクリックして、プッシュプラットフォームを追加します。プラットフォームの選択はそれぞれのバリアントに特有であるため、プラットフォームごとにメッセージのエンゲージメントをテストしてみることができる。
+| キャンバス | メッセージステップで、\[**\+ その他を追加**] をクリックし、プッシュプラットフォームをさらに追加します。マルチチャネルキャンペーンと同様、プラットフォームの選択は、それぞれのバリアントに固有です。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
-## ステップ 3:通知タイプを選択する（iOSとAndroid）
+## ステップ 3: 通知タイプを選択する（iOSとAndroid）
 
 クイックプッシュキャンペーンを作成している場合、通知タイプは自動的に標準プッシュに設定され、変更することはできない。
 
-![通知タイプは、例として標準プッシュが選択されている。][3]{: style="float:right;max-width:40%;margin-left:15px;"}
+![標準プッシュが選択されている通知タイプの例。][3]{: style="float:right;max-width:40%;margin-left:15px;"}
 
-iOSとAndroidの場合は、通知タイプを選択する：
+それ以外の場合、iOS と Android では通知タイプを選択します: 
 
 - スタンダード・プッシュ
 - [プッシュ通知ストーリー]({{site.baseurl}}/user_guide/message_building_by_channel/push/advanced_push_options/push_stories/)
@@ -98,13 +98,13 @@ iOSとAndroidの場合は、通知タイプを選択する：
 
 プッシュ・キャンペーンに画像を含めたい場合は、[iOS]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/rich_notifications/)または[Android]({{site.baseurl}}/user_guide/message_building_by_channel/push/android/rich_notifications/)向けのリッチ通知の作成について、以下のガイドを参照のこと。
 
-## ステップ 4:プッシュメッセージを作成する
+## ステップ 4: プッシュメッセージを作成する
 
 さて、いよいよプッシュ・メッセージを書く番だ！**Compose**タブでは、メッセージの内容と動作のあらゆる面を編集できる。
 
-![] （{% image_buster /assets/img_archive/push_compose.png %} ）。
+![プッシュ通知作成の「作成」タブ。]({% image_buster /assets/img_archive/push_compose.png %})
 
-**Compose "**タブの内容は、前のステップで選択した通知タイプによって異なるが、以下のオプションのいずれかを含むことができる：
+\[**作成**] タブの内容は、前のステップで選択した通知タイプによって異なりますが、以下のオプションのいずれかを使用できます。
 
 #### 通知チャンネルまたはグループ（iOSおよびAndroid）
 
@@ -112,32 +112,32 @@ iOSとAndroidの場合は、通知タイプを選択する：
 
 #### 言語
 
-**Add Languages**ボタンを使って複数の言語でコピーを追加する。コンテンツを書く前に言語を選択することをお勧めする。私たちの\[利用可能な言語の完全なリストを参照してください][18] 。
+**Add Languages**ボタンを使って複数の言語でコピーを追加する。コンテンツを記述する前に言語を選択することをお勧めします。これにより、Liquid 内の適切な場所にテキストを入力することができます。私たちの\[利用可能な言語の完全なリストを参照してください][18] 。
 
 #### タイトルと本文
 
 メッセージボックスに入力を開始し、左側のプレビューボックスにプレビューが表示されるのを見る。プッシュメッセージはプレーンテキストでフォーマットされなければならない。iOSのプッシュ通知に見出しを追加するには、**「タイトル」**フィールドを使う。
 
-あなたのプッシュをパーソナライズされ、ターゲットを絞ったものにするために、[リキッドを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/)含めることができる。
+プッシュをパーソナライズされターゲットを絞ったものにするには、[Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/) を含めることができます。
 
 {% alert tip %}
-素晴らしいコピーの作成にお困りですか？[AIコピーライティング・アシスタントを使って]({{site.baseurl}}/user_guide/intelligence/ai_copywriting/)みよう。商品名や説明を入力すると、AIが人間のようなマーケティングコピーを生成し、メッセージングに使用する。
+魅力的なコピーの作成にお困りですか?[AI コピーライティングアシスタント]({{site.baseurl}}/user_guide/intelligence/ai_copywriting/)を使ってみてください。商品名や説明を入力すると、AIが人間のようなマーケティングコピーを生成し、メッセージングに使用する。
 
-![プッシュコンポーザーのボディ欄にある「AIコピーライター」ボタンを起動する。]({% image_buster /assets/img/ai_copywriter/ai_copywriter_push.png %}){: style="max-width:60%"}
+![プッシュ作成画面の本文フィールドにある「AI コピーライターを起動」ボタン。]({% image_buster /assets/img/ai_copywriter/ai_copywriter_push.png %}){: style="max-width:60%"}
 {% endalert %}
 
-#### イメージ
+#### 画像
 
 サポートされている場合、アプリのアイコンは自動的にプッシュ通知の画像として追加される。また、リッチ通知を送信するオプションもあり、コピー以外のコンテンツを追加することで、プッシュ通知をよりカスタマイズすることができる。
 
 プッシュ通知に画像を使用する際のガイダンスについては、以下の記事を参照のこと：
 
-- [iOS用のリッチな通知を作成する]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/rich_notifications/)
-- [Android向けにリッチな通知を作成する]({{site.baseurl}}/user_guide/message_building_by_channel/push/android/rich_notifications/)
+- [iOS 向けのリッチ通知を作成する]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/rich_notifications/)
+- [Android 向けのリッチ通知を作成する]({{site.baseurl}}/user_guide/message_building_by_channel/push/android/rich_notifications/)
 
 #### オン・クリック動作
 
-**On-Click Behaviorで**、ユーザーがプッシュ通知の本文をクリックしたときの動作を指定する。例えば、顧客にアプリケーションを開くよう促したり、顧客を指定のウェブURLにリダイレクトさせたり、あるいは[ディープリンクを使って]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/deep_linking_to_in-app_content/)アプリケーションの特定のページを開くこともできる。
+**On-Click Behaviorで**、ユーザーがプッシュ通知の本文をクリックしたときの動作を指定する。例えば、顧客にアプリケーションを開くよう促したり、顧客を指定の Web URL にリダイレクトしたり、あるいは[ディープリンク]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/deep_linking_to_in-app_content/)を使ってアプリケーションの特定のページを開くようにすることも可能です。
 
 ここでは、プッシュ通知の中に、次のようなボタンのプロンプトを設定することもできる：
 
@@ -146,21 +146,21 @@ iOSとAndroidの場合は、通知タイプを選択する：
 - 確認/キャンセル
 - もっと見る 
 
-#### デバイス・オプション
+#### デバイスオプション
 
 ユーザーが複数のデバイスにアプリをインストールしている場合、デフォルトでは、有効なプッシュトークンが割り当てられたすべてのデバイスにプッシュメッセージが送信される。必要であれば、**このプッシュをユーザーの最近使用したデバイスにのみ送信する**ように選択することもできる。
 
-![デバイスオプションのチェックボックスで、このプッシュをユーザーの最近使用したデバイスにのみ送信する。][9]{: style="max-width:70%;" }
+![このプッシュをユーザーが最後に使用したデバイスにのみ送信するデバイスオプションのチェックボックス。][9]{: style="max-width:70%;" }
 
 この設定には若干のニュアンスがある。このオプションが選択されている場合、Brazeは、iOSとAndroidの両方など、複数のプラットフォームを対象とするキャンペーンを除き、複数送信が発生しないように制限する。ユーザーがiOSとAndroidの両方のデバイスにアプリを入れている場合、両方のプラットフォーム用のプッシュを受け取ることになる。ユーザーが最近使用したデバイスが[プッシュ対応]({{site.baseurl}}/user_guide/message_building_by_channel/push/users_and_subscriptions/#push-enabled)でない場合、メッセージは送信されない。
 
-iOSの場合、iPadデバイスにのみプッシュ通知を送信したり、iPhoneとiPodデバイスにのみ送信するなど、メッセージングをさらに制限することができる。
+iOS の場合、iPad デバイスにのみプッシュ通知を送信したり、iPhone と iPod デバイスにのみ送信するなど、メッセージングをさらに制限することができます。
 
-### ステップ4a：メッセージをプレビューしてテストする
+### ステップ 4a: メッセージをプレビューしてテストする
 
 ![テスト・プッシュ・メッセージ][7]{: style="float:right;max-width:30%;margin-left:15px;"}
 
-テストは、間違いなく最も重要なステップのひとつである。完璧なプッシュ・メッセージを作り終えたら、送信する前にテストしてみよう。**Test "**タブを選択し、"**Preview Message as User**"を使用して、メッセージがモバイルでどのように表示されるかを確認する。**Send Testを使って**テストプッシュを送信し、メッセージが正しく表示されることを確認する。
+テストは、おそらく最も重要なステップの 1 つです。完璧なプッシュ・メッセージを作り終えたら、送信する前にテストしてみよう。\[**テスト**] タブを選択し、\[**ユーザーとしてメッセージをプレビュー**] を使用して、メッセージがモバイルでどのように表示されるかを確認します。**Send Testを使って**テストプッシュを送信し、メッセージが正しく表示されることを確認する。
 
 ## ステップ 5: キャンペーンまたはキャンバスの残りの部分を作成する
 
@@ -171,23 +171,23 @@ iOSの場合、iPadデバイスにのみプッシュ通知を送信したり、i
 
 #### 配信スケジュールまたはトリガーを選択する
 
-プッシュメッセージは、スケジュールされた時間、アクション、またはAPIトリガーに基づいて配信することができる。詳しくは、[キャンペーンのスケジューリングを]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/)参照のこと。
+プッシュメッセージは、スケジュールされた時刻、アクション、または API トリガーに基づいて配信することができます。詳細については、[キャンペーンのスケジューリング]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/)を参照してください。
 
 アクションベースの配信では、キャンペーンの継続時間と \[[サイレント時間]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign/#quiet-hours)] を設定することもできます。
 
-このステップでは、ユーザーがキャンペーンを受信する[再資格を]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/#campaigns)得ることを許可したり、[頻度の上限]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)ルールを有効にしたりするなど、配信コントロールを指定することもできる。
+このステップでは、配信コントロールを指定できます。例えば、ユーザーを[再有効化]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/#campaigns)してキャンペーンを受信できるようにしたり、[フリークエンシーキャップ]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)ルールを有効にしたりできます。
 
 #### ターゲットとするユーザーを選択する
 
-次に、セグメントやフィルターを選択することで、[ユーザーを絞り込む]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)必要がある。セグメントのおおよその人数について現在の状態を示すスナップショットが自動的に表示されます。キャンペーンがターゲットとするチャンネルの詳細なオーディエンス統計は、フッターで見ることができる。ユーザーベースの何パーセントがターゲットになっているか、またそのセグメントのライフタイムバリューを見るには、**「追加統計情報を表示**」をクリックする。
+次に、セグメントまたはフィルターを選択して[ユーザーをターゲットに設定]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)し、オーディエンスを絞り込む必要があります。セグメントのおおよその人数について現在の状態を示すスナップショットが自動的に表示されます。キャンペーンがターゲットとするチャンネルの詳細なオーディエンス統計は、フッターに表示されます。ユーザーベースの何パーセントがターゲットになっているか、またそのセグメントのライフタイムバリューを見るには、**「追加統計情報を表示**」をクリックする。
 
-{% details リーチャブル・ユーザーの合計が全チャンネルの合計と一致しないのはなぜか？ %}
+{% details リーチ可能なユーザーの合計数の指標がすべてのチャネルの合計と一致しないのはなぜですか? %}
 
-フィルタリングしたオーディエンスの合計到達可能ユーザーを表示すると、個々の列の合計が合計到達可能ユーザーよりも小さいことに気づくかもしれない。このギャップは通常、キャンペーンのセグメントやフィルターに該当するにもかかわらず、プッシュでリーチできないユーザーが多数存在するためである（例えば、有効またはアクティブな[プッシュトークンを持って]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_registration/#push-tokens)いないため）。
+フィルタリングしたオーディエンスのリーチ可能なユーザー合計数を表示した際、個々の列の合計がリーチ可能なユーザー合計数よりも小さい場合があります。このギャップは通常、キャンペーンのセグメントやフィルターに該当するにもかかわらず、プッシュでリーチできないユーザーが多数存在するためである（例えば、有効またはアクティブな[プッシュトークンを持って]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_registration/#push-tokens)いないため）。
 
 {% enddetails %}
 
-![]({% image_buster /assets/img_archive/multi_channel_footer.png %}) リーチャブル・ユーザーの詳細な視聴者統計の表。
+![リーチ可能なユーザーの詳細なオーディエンス統計の表。]({% image_buster /assets/img_archive/multi_channel_footer.png %})
 
 正確なセグメントメンバーシップは常にメッセージが送信される直前に計算されることに注意してください。
 
@@ -197,13 +197,13 @@ iOSの場合、iPadデバイスにのみプッシュ通知を送信したり、i
 
 ##### Eメールとプッシュによるマルチチャネルキャンペーン
 
-Eメールとプッシュチャネルの両方をターゲットにしたマルチチャネルキャンペーンの場合、明示的にオプトインしているユーザーのみがメッセージを受信するようにキャンペーンを制限したい場合がある（購読または購読解除したユーザーを除く）。例えば、オプトインのステータスが異なる3人のユーザーがいるとする：
+メールチャネルとプッシュ通知チャネルの両方をターゲットにしたマルチチャネルキャンペーンの場合、明示的にオプトインしているユーザーのみがメッセージを受け取るようにキャンペーンを制限することができます (配信登録済みユーザーまたは配信停止済みユーザーを除く)。例えば、次のようにオプトインステータスが異なる 3 人のユーザーがいるとします。
 
 - **ユーザー A** はメールを購読しており、プッシュ通知が有効です。このユーザーはメールを受信しませんが、プッシュ通知は受信します。
 - **ユーザー B** はメールにオプトインしていますが、プッシュ通知を有効にしていません。このユーザーはメールを受信しますが、プッシュ通知は受信しません。
 - **ユーザー C** はメールにオプトインしており、プッシュ通知が有効です。このユーザーはメールとプッシュ通知の両方を受け取ります。
 
-そのためには、**「オーディエンス・サマリー**」で、このキャンペーンを「オプトインしたユーザーのみ」に送信することを選択する。このオプションを選択すると、オプトインしたユーザーのみがメールを受信し、Braze は、デフォルトでプッシュ通知が有効になっているユーザーにのみプッシュ通知を送ります。
+そのためには、\[**オーディエンスの概要**] で、このキャンペーンを「オプトインしたユーザーのみ」に送信するように選択します。このオプションを選択すると、オプトインしたユーザーのみがメールを受信し、Braze は、デフォルトでプッシュ通知が有効になっているユーザーにのみプッシュ通知を送ります。
 
 {% alert important %}
 この構成では、**Target Users**ステップに、オーディエンスを単一のチャネルに限定するフィルタ（例えば、`Push Enabled = True` や`Email Subscription = Opted-In` ）を含めない。
@@ -217,16 +217,16 @@ Braze では、キャンペーンを受信した後、ユーザーが指定の
 
 {% tab キャンバス %}
 
-まだやっていない場合は、キャンバス・コンポーネントの残りのセクションを完成させる。キャンバスの残りの部分の構築方法、多変量テストとインテリジェントセレクションの実装方法などの詳細については、キャンバスドキュメントの「[キャンバスを構築する」]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-3-build-your-canvas)ステップを参照のこと。
+キャンバスコンポーネントが完成していない場合、残りのセクションを完成させます。キャンバスの残りの部分の構築方法、多変量テストとインテリジェントセレクションの実装方法などの詳細については、キャンバスドキュメントの「[キャンバスを構築する」]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-3-build-your-canvas)ステップを参照のこと。
 
 {% endtab %}
 {% endtabs %}
 
-## ステップ 6:レビューと配備 {#review-and-deploy-push}
+## ステップ 6: レビューと展開 {#review-and-deploy-push}
 
-キャンペーンやキャンバスの最後の構築が終わったら、その詳細を確認する。キャンペーンの場合、最終ページには、あなたがデザインしたキャンペーンの概要が表示される。関連する詳細をすべて確認し、メッセージをテストしたことを確認してから送信し、データが送られてくるのを見る！
+キャンペーンまたはキャンバスの最後の部分の作成が完了したら、その詳細を確認してください。キャンペーンの場合、最終ページには、あなたがデザインしたキャンペーンの概要が表示される。関連する詳細をすべて確認し、メッセージをテストしたことをチェックしてから送信し、データが送られてくるのを確認します。
 
-次に、[プッシュレポート]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_reporting/)をチェックして、プッシュキャンペーンの結果にアクセスする方法を学びましょう。プッシュ通知については、メッセージの送信数、配信数、バウンス数、開封数、直接開封数の統計を見ることができる。
+次に、\[[プッシュレポート]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_reporting/)] をチェックして、プッシュキャンペーンの結果にアクセスする方法を学んでください。プッシュ通知については、メッセージの送信数、配信数、バウンス数、開封数、直接開封数の統計を見ることができる。
 
 [1]: {% image_buster /assets/img_archive/new_campaign_push.png %}
 [2]: {% image_buster /assets/img_archive/push_1.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/push/ios/utilizing_badge_count.md b/_lang/ja/_user_guide/message_building_by_channel/push/ios/utilizing_badge_count.md
index 47a650d1a5a..9afe301177e 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/push/ios/utilizing_badge_count.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/push/ios/utilizing_badge_count.md
@@ -1,6 +1,6 @@
 ---
-nav_title: バッジ数の使用
-article_title: バッジ数の使用
+nav_title: バッジ数の使用法
+article_title: バッジ数の使用法
 page_order: 8
 
 page_type: reference
@@ -12,33 +12,33 @@ channel:
 
 ---
 
-# バッジ数の使用
+# バッジ数の使用法
 
-> iOS バッジカウントには、アプリライケーション内の未読通知の数が表示されます。アプリアイコンの右上隅に赤い円が表示されます。近年、バッジングは、アプリ ユーザーsを再係合するための効果的な方法となっている。
+> iOS バッジカウントには、アプリライケーション内の未読通知の数が表示されます。アプリアイコンの右上隅に赤い円が表示されます。近年、バッジングは、アプリユーザーを再エンゲージするための効果的な方法となっています。
 
-バッジカウントを使用して、プッシュに気づかなかった、またはフォアグラウンドプッシュ通知s を無効にしたユーザーを再びエンゲージすることができます。同様に、in-アプリ 更新 s などの未表示のメッセージをユーザーに通知するために使用できます。
+バッジカウントを使用して、プッシュに気づかなかった、またはフォアグラウンドプッシュ通知s を無効にしたユーザーを再びエンゲージすることができます。また同様に、アプリ内更新などの未表示のメッセージをユーザーに通知するためにも使用できます。
 
-## Brazeによるバッジ数
+## Braze のバッジ数
 
-Braze ダッシュボードを通じてプッシュ通知を作成するときに、希望のバッジ数を指定できます。これはパーソナライズされた メッセージング でユーザー 属性に設定でき、無限にカスタマイズ可能なロジックを可能にします。ユーザーを妨害することなくバッジ数を更新するサイレントプッシュを送信する場合は、"Content-Available"フラグをプッシュに追加し、そのメッセージコンテンツを空のままにします。
+Braze ダッシュボードを通じてプッシュ通知を作成するときに、希望のバッジ数を指定できます。これをパーソナライズされたメッセージングでユーザー属性に設定して、完全なカスタマイズが可能なロジックを実現できます。ユーザーを妨害することなくバッジ数を更新するサイレントプッシュを送信する場合は、"Content-Available"フラグをプッシュに追加し、そのメッセージコンテンツを空のままにします。
 
 {% alert note %}
-Androidのバッジ数を設定する方法は不思議ですか？Androidは自動的にプッシュのためのアプリバッジングを処理するので、Brazeでのバッジングのためのカスタマイズ設定はありません。
+Android のバッジ数を設定するにはどうしたらよいでしょう? Androidは自動的にプッシュのためのアプリバッジングを処理するので、Brazeでのバッジングのためのカスタマイズ設定はありません。
 {% endalert %}
 
-### バッジカウントの削除
+### バッジ数の削除
 
-バッジ数を0 または"" に設定して、アプリのアイコンからバッジ数を削除します。アプリがフォアグラウンドにある間にプッシュ通知を受信すると、Braze は自動的にバッジをクリアします。
+バッジ数を 0 または "" に設定して、アプリのアイコンからバッジ数を削除します。アプリがフォアグラウンドにある間にプッシュ通知を受信すると、Braze は自動的にバッジをクリアします。
 
 ## ベストプラクティス
 
 バッジングの再エンゲージメント能力を最適化するには、ユーザーの操作性を最も簡素化する方法でバッジ設定を設定することが重要です。
 
 ### バッジ数を低く保つ
-調査によると、バッジ数が2桁を超えて増えた後、ユーザーsは一般に更新sに関心を失い、しばしばアプリの使用を完全に中止する。
+調査によると、バッジ数が 2 桁を超えて増えた後、ユーザーは一般に更新に関心を失い、しばしばアプリの使用を完全に中止することがわかっています。
 
-> この規則には、アプリの性質(メールやグループメッセージング アプリなど) に応じて除外することができます。
+> この規則には、アプリの性質 (メールやグループメッセージングアプリなど) によっては例外があります。
 
 ### バッジ数が表すことを制限する
-バッジング時に、通知s をできるだけ明確にし、ダイレクトにしたい。バッジ通知が表現できるものの数を制限することで、ユーザーにアプリの機能や更新に精通している感覚を与えることができます。
+バッジングの際は、できるだけ明確かつ直接的な通知を送る必要があります。バッジ通知が表現できるものの数を制限することで、アプリの機能や更新に精通しているという感覚をユーザーに与えることができます。
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/push/push_registration.md b/_lang/ja/_user_guide/message_building_by_channel/push/push_registration.md
index 10734b864f3..669229d2f8a 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/push/push_registration.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/push/push_registration.md
@@ -17,67 +17,67 @@ channel:
 
 プッシュトークンとそれが何であるかを理解することは、Brazeでプッシュメッセージを送信する方法を理解するための基本的な要素である。プッシュトークンは、ユーザーのデバイスによって生成され、各受信者の通知を送信する場所を特定するためにBrazeに送信される一意の匿名識別子である。デバイスがプッシュトークンを持っていない場合、プッシュを送信する方法はない。
 
-プッシュトークンはプッシュサービスプロバイダによって生成される。Brazeは、AndroidのFirebase Cloud Messaging Service（FCM）やiOSのApple Push Notification Service（APN）のようなプッシュサービスプロバイダーと接続し、これらのプロバイダーは、あなたのアプリを識別するユニークなデバイストークンを送信する。各デバイスは、メッセージングに使用されるユニークなトークンを1つずつ持っている。トークンは[期限切れや](#push-token-expire)更新が可能である。
+プッシュトークンはプッシュサービスプロバイダによって生成される。Brazeは、AndroidのFirebase Cloud Messaging Service（FCM）やiOSのApple Push Notification Service（APN）のようなプッシュサービスプロバイダーと接続し、これらのプロバイダーは、あなたのアプリを識別するユニークなデバイストークンを送信する。各デバイスには、メッセージングに使用される一意のトークンが 1 つあります。トークンはそのまま[期限切れ](#push-token-expire)にするか、更新することができます。
 
-プッシュトークン]\[プッシュトークン] ]には2つの分類方法があり、プッシュ通知をユーザーに送る方法を理解するのに欠かせない。
+\[プッシュトークン]\[プッシュトークン] には 2 つの分類方法があります。プッシュ通知をユーザーに送る方法を理解するためには、これらを把握しておく必要があります。
 
-1. **フォアグラウンド・プッシュは**、ユーザーのデバイスのフォアグラウンドに定期的に目に見えるプッシュ通知を送信する機能を提供する。
-2. **バックグラウンド・プッシュは**、特定のデバイスがそのブランドからのプッシュ通知を受け取ることをオプトインしているかどうかに関係なく利用できる。バックグラウンド・プッシュでは、ブランドはサイレント・プッシュ通知（意図的に表示されない通知）をデバイスに送信し、アンインストール追跡のような重要な機能をサポートすることができる。
+1. **フォアグラウンドプッシュ**は、ユーザーのデバイスのフォアグラウンドに定期的に表示されるプッシュ通知を送信する機能を提供します。
+2. **バックグラウンドプッシュは**、特定のデバイスがそのブランドからのプッシュ通知の受信にオプトインしているかどうかに関係なく利用できます。バックグラウンドプッシュでは、ブランドがサイレントプッシュ通知 (意図的に表示されない通知) をデバイスに送信して、アンインストール追跡のような重要な機能をサポートすることができます。
 
-ユーザープロファイルにアプリに関連付けられた有効なフォアグラウンドプッシュトークンがある場合、Brazeはそのユーザーを指定されたアプリの「プッシュ登録済み」とみなす。そこでBrazeは、このようなユーザーを特定するための特定のセグメンテーションフィルター、`Push enabled for App,` 。
+ユーザープロファイルにアプリに関連付けられた有効なフォアグラウンドプッシュトークンがある場合、Brazeはそのユーザーを指定されたアプリの「プッシュ登録済み」とみなす。そこで、Braze にはそのようなユーザーの特定に役立つ特定のセグメンテーションフィルター `Push enabled for App,` が用意されています。
 
 {% alert note %}
-`Push enabled for App` フィルタは、指定されたアプリの有効なフォアグラウンドまたはバックグラウンドプッシュトークンの存在のみを考慮する。しかし、より一般的な`Push Enabled` フィルタは、ワークスペース内のアプリのプッシュ通知を明示的に有効にしているユーザーをセグメントする。このカウントには、フォアグラウンド・プッシュのみが含まれ、購読を解除したユーザーは含まれない。これらのフィルターやその他のフィルターについては、[セグメンテーション・フィルターで]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters)詳しく説明されている。
+`Push enabled for App` フィルターは、指定されたアプリについて、有効なフォアグラウンドやバックグラウンドのプッシュトークンの有無のみを考慮します。しかし、より一般的な`Push Enabled` フィルタは、ワークスペース内のアプリのプッシュ通知を明示的に有効にしているユーザーをセグメントする。このカウントには、フォアグラウンドプッシュのみが含まれ、配信停止したユーザーは含まれません。これらのフィルターやその他のフィルターについては、[セグメンテーション・フィルターで]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters)詳しく説明されている。
 {% endalert %}
 
 ### 1台のデバイスで複数のユーザーが利用できる
 
 プッシュトークンはデバイスとアプリの両方に固有なので、プッシュトークンを使って同じデバイスを使っている複数のユーザーを区別することはできない。
 
-例えば、2人のユーザーがいるとする：チャーリーとキムだ。チャーリーが自分の携帯電話であなたのアプリのプッシュ通知を有効にしている場合、キムがチャーリーの携帯電話を使ってチャーリーのプロフィールからログアウトし、自分のプロフィールにログインすると、プッシュトークンはキムのプロフィールに再割り当てされる。プッシュトークンは、キムがログアウトし、チャーリーが再度ログインするまで、そのデバイスのキムのプロファイルに割り当てられたままとなる。
+例えば、2人のユーザーがいるとする：Charlie と Kim です。Charlie が自分の携帯電話でアプリのプッシュ通知を有効にしている場合、Kim が Charlie の携帯電話を使用して Charlie のプロファイルからログアウトし、自分のプロファイルにログインすると、プッシュトークンは Kim のプロファイルに割り当てし直されます。プッシュトークンは、Kim がログアウトして、Charlie が再度ログインするまで、そのデバイスの Kim のプロファイルに割り当てられたままになります。
 
-アプリやウェブサイトは、1つのデバイスにつき1つのプッシュ購読しかできない。そのため、ユーザーがデバイスやウェブサイトからログアウトし、新しいユーザーがログインすると、プッシュトークンは新しいユーザーに再割り当てされる。これは、**Engagement**タブの**Contact Settings**セクションにあるユーザーのプロフィールに反映される：
+アプリや Web サイトは、1 つのデバイスにつき 1 つのプッシュ通知サブスクリプションのみを持つことができます。そのため、ユーザーがデバイスやウェブサイトからログアウトし、新しいユーザーがログインすると、プッシュトークンは新しいユーザーに再割り当てされる。これは、**Engagement**タブの**Contact Settings**セクションにあるユーザーのプロフィールに反映される：
 
-![ユーザーのプロフィールの\*\*Engagement**タブにあるプッシュトークンの変更履歴。][4]
+![ユーザープロファイルの \[エンゲージメント] タブにあるプッシュトークンの変更ログ。プッシュトークンが他のユーザーに移動した時点と、そのトークンがリストされます。][4]
 
 プッシュ・プロバイダ（APN/FCM）には、1つのデバイス上の複数のユーザーを区別する方法がないため、最後にログインしたユーザーにプッシュ・トークンを渡し、デバイス上のどのユーザーをプッシュのターゲットにするかを決定する。
 
 ## プッシュトークン登録
 
-各プラットフォームは、プッシュトークンの登録とプッシュ許可の処理をさまざまな方法で行っている：
+プラットフォームは、プッシュトークン登録とプッシュ権限をさまざまな方法で処理します。
 
 - **Android**:
-  - **Android 13**:<br>プッシュの許可はユーザーに求め、許可を得なければならない。ユーザーからパーミッションが与えられた後にトークンを受け取る。あなたのアプリは、適切なタイミングでユーザーに手動で許可を求めることができるが、そうでない場合は、アプリが[通知チャネルを](https://developer.android.com/reference/android/app/NotificationChannel)作成した後、ユーザーに自動的にプロンプトが表示される。
-  - **アンドロイド12以前**：<br>すべてのユーザーは、Brazeが自動的にプッシュトークンを要求する最初のセッション時に、`Subscribed` 。この時点で、ユーザーはそのデバイスの有効なプッシュトークンと、`Subscribed` というデフォルトのサブスクリプション状態で**プッシュ有効になって**いる。<br><br>
-- **iOS**:自動的にプッシュ登録されるわけではない。
-    - **iOS 12（暫定認証あり）**：<br>アプリは、[仮承認]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/notification_options/#provisional-push)または承認されたプッシュを要求することができる。一方、\[provisional push]\[provisional-blog] ] は、音やアラートなしで、通知センターに直接、__静かに__通知を送ることができる。
-    - **iOS 11以降およびiOS 12（暫定認証なし）**：<br>すべてのユーザーは、プッシュ通知の受信を明示的にオプトインしなければならない。ユーザーがオプトインした後、トークンを受け取る。<br><br>
-- **Web:**ネイティブブラウザの許可ダイアログを通じて、ユーザーに明示的なオプトインを要求しなければならない。ユーザーがオプトインした後、トークンを受け取る。 iOSやAndroidでは、アプリはいつでも許可プロンプトを表示できるが、最近のブラウザの中には、「ユーザージェスチャー」（マウスクリックやキーストローク）によってのみプロンプトを表示するものもある。もしあなたのサイトがページロード時にプッシュ通知の許可を要求しようとすれば、おそらくブラウザによって無視されるか、沈黙させられるだろう。
+  - **Android 13**:<br>プッシュ権限は、ユーザーに求め、ユーザーによって付与される必要があります。ユーザーからパーミッションが与えられた後にトークンを受け取る。アプリから手動で、適切なタイミングでユーザーに許可を求めることができますが、そうでない場合は、アプリが[通知チャネル](https://developer.android.com/reference/android/app/NotificationChannel)を作成した後に、ユーザーに自動的にプロンプトが表示されます。
+  - **Android 12 以前**: <br>Braze が自動的にプッシュトークンを要求すると、すべてのユーザーが最初のセッションで `Subscribed` と見なされます。この時点で、ユーザーはそのデバイスの有効なプッシュトークンと、`Subscribed` というデフォルトのサブスクリプション状態で**プッシュ有効になって**いる。<br><br>
+- **iOS**:自動的にプッシュ登録されません。
+    - **iOS 12（暫定認証あり）**：<br>アプリは、[仮承認]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/notification_options/#provisional-push)または承認されたプッシュを要求することができる。承認プッシュでは、通知を送信する前にユーザーからの明示的な許可が必要ですが (ユーザーから許可された後でトークンを受信します)、\[暫定プッシュ]\[provisional-blog] では、音やアラートなしで通知センターに直接、__静かに__通知を送信できます。
+    - **iOS 11以降およびiOS 12（暫定認証なし）**：<br>すべてのユーザーは、プッシュ通知の受信を明示的にオプトインしなければなりません。ユーザーがオプトインした後にトークンを受け取ります。<br><br>
+- **Web:**ネイティブブラウザーの許可ダイアログを通じて、ユーザーから明示的なオプトインを要求する必要があります。ユーザーがオプトインした後にトークンを受け取ります。 iOS や Android の場合、アプリからいつでも許可プロンプトを表示できますが、最近のブラウザーの中には、「ユーザーのジェスチャー」(マウスクリックやキーストローク) でトリガーされたときにのみプロンプトを表示するものもあります。御社サイトでページの読み込み時にプッシュ通知の許可を要求しようとした場合、おそらくブラウザーによって無視されるか、表示されない可能性があります。
 
 | プッシュトークンを取得する | プッシュトークンを送信する |
 | ---------------- | ----------------- |
-| アプリケーションは、デバイスのプッシュトークンを取得するために、プッシュ・プロバイダに登録しなければならない。 | 開発者は、FCM/APNによって生成されたプッシュトークンを使ってデバイスをターゲットにすることができる。|
+| アプリケーションは、デバイスのプッシュトークンを取得するためにプッシュプロバイダーに登録する必要があります。 | 開発者は、FCM/APN によって生成されたプッシュトークンを使ってデバイスをターゲットにすることができます。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 ### ユーザーのプッシュ購読状態をチェックする
 
 ![John Doeのユーザープロファイルで、プッシュ購読の状態がSubscribedに設定されている。][3]{: style="float:right;max-width:35%;margin-left:15px;"}
 
-Brazeでユーザーのプッシュ購読状態を確認するには、2つの方法がある：
+Braze でユーザーのプッシュ通知のサブスクリプションの状態を確認するには、3 つの方法があります。
 
-1. **ユーザープロフィール][5]Brazeダッシュボードの\[User Search][5] ]ページから、個々のユーザープロファイルにアクセスできる。Eメールアドレス、電話番号、または外部ユーザーIDを介して）ユーザーのプロフィールを見つけた後、**Engagement**タブを選択してユーザーの購読状態を表示し、手動で調整することができる。 
+1. **ユーザープロフィール**Braze ダッシュボードの \[ユーザー検索][5] ページから、個々のユーザープロファイルにアクセスできます。Eメールアドレス、電話番号、または外部ユーザーIDを介して）ユーザーのプロフィールを見つけた後、**Engagement**タブを選択してユーザーの購読状態を表示し、手動で調整することができる。 
 <br>
-2.**Rest API Export***：エクスポート [Users by segment][segment] ]] または [Users by identifier][identifier] ] エンドポイントを使用して、個々のユーザー・プロファイルを JSON 形式でエクスポートできる。Brazeは、デバイスごとのプッシュ有効化情報を含むプッシュトークンオブジェクトを返す。
+2. ** Rest API でのエクスポート **: [セグメント別のユーザー][segment] または[識別子別のユーザー][identifier]のエクスポートのエンドポイントを使用して、個々のユーザープロファイルを JSON 形式でエクスポートできます。Brazeは、デバイスごとのプッシュ有効化情報を含むプッシュトークンオブジェクトを返す。
 
 ### プッシュ登録状況を確認する
 
-ユーザーのプロフィールの**Engagement**タブには、**Push Registered Forの**後にアプリ名が表示される。そのデバイスのアプリ情報が存在しない場合は、2つのダッシュ**（--）が**表示される。ユーザーに属するすべてのデバイスのエントリーが存在することになる。
+ユーザープロファイルの \[**エンゲージメント**] タブに、\[**登録済みのプッシュ通知**] とアプリ名が表示されます。そのデバイスにアプリ情報が存在しない場合は、2 つのダッシュ (**--**) が表示されます。ユーザーに属するすべてのデバイスにエントリが存在します。
 
-デバイスエントリーのアプリ名の前に`Foreground:` が付いている場合、そのアプリはそのデバイス上でフォアグラウンド・プッシュ通知（ユーザーに見える）とバックグラウンド・プッシュ通知（ユーザーに見えない）の両方を受信する権限を持つ。
+デバイスエントリのアプリ名の前に `Foreground:` が付いている場合、アプリはそのデバイスでフォアグラウンドプッシュ通知 (ユーザーに表示されます) と、バックグラウンドプッシュ通知 (ユーザーに表示されません) の両方を受け取るよう承認されています。
 
-![プッシュトークンの例でChangelogをプッシュする。][2]{: style="float:right;max-width:40%;margin-left:15px;margin-top:10px;"}
+![サンプルプッシュトークンのあるプッシュ通知の変更ログ][2]{: style="float:right;max-width:40%;margin-left:15px;margin-top:10px;"}
 
-一方、デバイスエントリーのアプリ名の先頭に`Background:` が付いている場合、そのアプリは[バックグラウンドプッシュの]({{site.baseurl}}/user_guide/message_building_by_channel/push/types/#background-push-notifications)受信のみが許可されており、そのデバイス上でユーザーから見える通知を表示することはできない。これは通常、ユーザーがそのデバイスでアプリの通知を無効にしていることを示す。
+一方、デバイスエントリのアプリ名に `Background:` という接頭辞が付いている場合、アプリは[バックグラウンドプッシュ]({{site.baseurl}}/user_guide/message_building_by_channel/push/types/#background-push-notifications)を受信する権限のみが付与され、ユーザーに表示可能な通知をそのデバイスでは表示できません。これは通常、ユーザーがそのデバイスでアプリの通知を無効にしていることを示します。
 
 プッシュトークンを同じデバイスの別のユーザーに移動すると、最初のユーザーはプッシュ登録されなくなる。
 
@@ -87,35 +87,35 @@ Brazeでユーザーのプッシュ購読状態を確認するには、2つの
 
 | アクション (Action) | 説明 |
 | ------ | ----------- |
-| `changeUser()` というメソッドがある。 | Braze`changeUser()` メソッドは、SDKがユーザー行動データを割り当てるユーザーIDを切り替える。このメソッドは通常、ユーザーがアプリケーションにログインするときに呼び出される。`changeUser()` 、特定のデバイスで異なるユーザーIDまたは新しいユーザーIDで呼び出されると、そのデバイスのプッシュトークンは、対応するユーザーIDを持つ適切なBrazeプロファイルに移動する。 |
-| プッシュエラー発生 | トークン削除につながる一般的なプッシュエラーには、`MismatchSenderId` 、`InvalidRegistration` 、その他のプッシュバウンスがある。<br><br>よくある[プッシュエラーの][errors]リストをご覧いただきたい。 |
+| `changeUser()` メソッドが呼び出される | Braze`changeUser()` メソッドは、SDKがユーザー行動データを割り当てるユーザーIDを切り替える。このメソッドは通常、ユーザーがアプリケーションにログインするときに呼び出される。`changeUser()` 、特定のデバイスで異なるユーザーIDまたは新しいユーザーIDで呼び出されると、そのデバイスのプッシュトークンは、対応するユーザーIDを持つ適切なBrazeプロファイルに移動する。 |
+| プッシュエラー発生 | トークンの削除につながる一般的なプッシュエラーには、`MismatchSenderId`、`InvalidRegistration`、およびその他のタイプのプッシュバウンスがあります。<br><br>よくある[プッシュエラーの][errors]リストをご覧いただきたい。 |
 | ユーザーがアンインストールする | ユーザーがデバイスからアプリケーションをアンインストールすると、Brazeはユーザーのプッシュトークンをプロファイルから削除する。 |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ### これはより広いスケールで見るとどうなるのだろうか？
 
-ユーザーが新しいアプリケーションを開き、プッシュプロンプトからプッシュアクセスを許可すると、Braze SDKからプッシュプロバイダーへの呼び出しが行われる。この呼び出しが行われると、プッシュ・プロバイダはすべてが正しく設定されているかどうかのチェックを行う。もしそうなら、プッシュトークンがあなたのデバイスに渡される。トークンが到着すると、SDKはこれをBrazeに伝える。Brazeがプッシュプロバイダからトークンを受け取った後、ユーザープロファイルを更新または新規作成する。これらのユーザーは登録済みとみなされる。
+ユーザーが新しいアプリケーションを開き、プッシュプロンプトからプッシュアクセスを許可すると、Braze SDKからプッシュプロバイダーへの呼び出しが行われる。この呼び出しが行われると、プッシュプロバイダーはすべてが正しく設定されているかどうかのチェックを実行します。もしそうなら、プッシュトークンがあなたのデバイスに渡される。トークンが到着すると、SDKはこれをBrazeに伝える。Brazeがプッシュプロバイダからトークンを受け取った後、ユーザープロファイルを更新または新規作成する。これらのユーザーは登録済みとみなされる。
 
-キャンペーンを開始したい場合は、Brazeでキャンペーンを作成し、プッシュ・ペイロードを生成してプッシュ・プロバイダに送信する。そこから、プロバイダーはユーザーのデバイスにプッシュペイロードを配信し、SDKはメッセージング状態をBrazeに渡す。
+キャンペーンを開始する場合は、プッシュプロバイダーに送信するプッシュペイロードを生成するキャンペーンを Braze で作成します。そこから、プロバイダーはユーザーのデバイスにプッシュペイロードを配信し、SDKはメッセージング状態をBrazeに渡す。
 
-![前述のBraze、顧客、Apple Push Notification ServiceまたはFirebase Cloud Messaging間のプッシュプロセスをマッピングしたフローチャート。]\[push-process]
+![前述の Braze、カスタマー、Apple Push Notification Service または Firebase Cloud Messaging 間のプッシュプロセスをマッピングしたフローチャート]\[push-process]
 
-| 登録ステップ | メッセージング・ステップ |
+| 登録ステップ | メッセージングステップ |
 | ------------------ | --------------- |
-| 1\.顧客（デバイス）がプッシュ・プロバイダに登録する<br>2\.プロバイダーがプッシュトークンを生成し、配信する<br>3\.Brazeのフラッシュ・トークン |1\.Brazeはプッシュペイロードをプロバイダーに送る<br>2\.プロバイダーはプッシュペイロードをデバイスに配信する。<br>3\.SDKはメッセージング統計情報をBrazeに渡す |
+| 1\.顧客 (デバイス) がプッシュプロバイダーに登録する<br>2\.プロバイダーがプッシュトークンを生成し、配信する<br>3\.Brazeのフラッシュ・トークン |1\.Brazeはプッシュペイロードをプロバイダーに送る<br>2\.プロバイダーはプッシュペイロードをデバイスに配信する。<br>3\.SDKはメッセージング統計情報をBrazeに渡す |
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## よくある質問
 
 ### オプトインしたユーザーがアプリを削除し、再ダウンロードした場合はどうなるのか？
 
-あるユーザーがプッシュを選択し、プッシュメッセージを受け取った後、アプリを削除したとする。これにより、デバイス・レベルでのプッシュ同意が削除される。ここから、アンインストール後の最初のバウンスプッシュは、自動的にそのユーザーを今後のプッシュメッセージングからオプトアウトすることになる。この後、ユーザーがアプリを再インストールしても起動しなかった場合、Brazeはプッシュトークンをユーザーに送信できない。
+あるユーザーがプッシュを選択し、プッシュメッセージを受け取った後、アプリを削除したとします。すると、デバイスレベルでプッシュ同意が削除される。ここから、アンインストール後の最初のバウンスプッシュによって、そのユーザーは将来のプッシュメッセージからオプトアウトされます。この後、ユーザーがアプリを再インストールし、起動しなかった場合、アプリにプッシュトークンが再付与されないため、Braze はユーザーにプッシュを送信できません。
 
-さらに、ユーザーがフォアグラウンド・プッシュを再び有効にする場合、プッシュ・メッセージングの受信を開始するために、ユーザー・プロファイルのこの情報を更新するためにセッションを開始する必要がある。
+さらに、ユーザーがフォアグラウンドプッシュを再び有効にする場合、プッシュメッセージの受信を開始するには、セッションを開始してユーザープロファイル内のこの情報を更新する必要があります。
  
 ### プッシュトークンの有効期限は？ {#push-token-expire}
 
-残念ながら、APNとFCMはこれを定義していない。プッシュトークンは、アプリがアップデートされた時、ユーザーが新しいデバイスにデータを移した時、OSを再インストールした時などに失効することがある。ほとんどの場合、なぜプッシュ・プロバイダが特定のプッシュ・トークンを失効させるのか、私たちにはよくわからない。
+残念ながら、APN と FCM はこれを定義していません。プッシュトークンは、アプリがアップデートされた時、ユーザーが新しいデバイスにデータを移した時、OSを再インストールした時などに失効することがある。ほとんどの場合、プッシュプロバイダーが特定のプッシュトークンを期限切れにする理由について有用なインサイトはありません。
 
 この曖昧さを考慮し、SDKプッシュ統合は常にセッション開始時にトークンを登録し、フラッシュすることで、最新のトークンを確保している。
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/push/push_reporting.md b/_lang/ja/_user_guide/message_building_by_channel/push/push_reporting.md
index a3483587dc9..fe06b752b95 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/push/push_reporting.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/push/push_reporting.md
@@ -9,7 +9,7 @@ tool: Reports
 
 ---
 
-# プッシュ報道
+# プッシュ通知レポート
 
 > この記事では、プッシュ・キャンペーンの成功を確認・分析するためのプッシュ・レポートについて説明する。
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/sms/about_sms.md b/_lang/ja/_user_guide/message_building_by_channel/sms/about_sms.md
index e64f1e29472..c409b7039f2 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/sms/about_sms.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/sms/about_sms.md
@@ -2,7 +2,7 @@
 nav_title: "SMSについて"
 article_title: SMSについて
 page_order: 1
-description: "このリファレンス記事では、SMS チャネルの全般的なユースケースと、SMSを起動して実行するために必要な条件について説明します。"
+description: "この記事では、SMS チャネルの全般的なユースケースと、SMS を起動して実行するために必要な条件について説明します。"
 page_type: reference
 channel:
   - SMS
@@ -11,7 +11,7 @@ search_rank: 2
 
 # [![Brazeラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/messaging-channels-sms){: style="float:right;width:120px;border:0;" class="noimgborder"}SMSについて
 
-> この記事では、SMSの統合を支援し、顧客s.![SMSメッセージとテキスト"Brazeへようこそ!と効果的かつ戦略的なコミュニケーションを可能にすることを知るために、要件、条件から引き出すいくつかの一般的なユースケースを共有しています。私たちはあなたが乗船することに興奮しています。開始するには、私たちのドキュメントを確認してください。https://www.braze.com/docs/ ヘルプのためのテキストHELPと、停止するためのSTOP."]\[ピクチャ]{: style="float:right;max-width:30%;margin-left:15px;margin-top:10px;border: 0;"}
+> この記事では、SMS の統合を支援し、顧客とのコミュニケーションを効果的かつ戦略的に行うために役立つ一般的なユースケース、要件、および用語について説明します。![「Braze へようこそ。弊社の製品をご利用いただきありがとうございます。まずは手始めにドキュメントをご覧ください。https://www.braze.com/docs/ ヘルプが必要な場合は SMS で HELP、停止するには STOP と返信してください。」というテキストを含む SMS メッセージ。]\[picture]{: style="float:right;max-width:30%;margin-left:15px;margin-top:10px;border: 0;"}
 
 <br>
 ショートメッセージサービスとも呼ばれるSMSは、携帯電話にテキストメッセージを送信するために使用されます。現在、世界中で毎日230億通以上のテキストメッセージが送信されており、SMSはユーザーsや顧客sに到達する最も直接的な方法です。このように幅広く利用され、実証された価値があることから、中小企業はあらゆる規模の企業にとって効果的なマーケティング手段となっている。
@@ -20,9 +20,9 @@ search_rank: 2
 
 | ユースケース | 説明 |
 |---|---|
-| ジェネラルマーケティング | SMSメッセージは、今後の取引、好調な販売、現在または将来の商品を顧客に伝えるための、直接的で柔軟かつ効率的な方法です。 |
-| 注意事項 | SMSは、サービスのアプリを設定したユーザーに通知するのに効果的です。例えば、顧客にアプリ用軟膏の前日に注意を促すSMSを送ることで、あなたと顧客の時間と費用を節約して、見落とされたアプリ用軟膏を最小限に抑えることができます。 |
-| 全件送信アクション | SMSは、発注確認や発送情報などのアクション的な通知を効率的に発信し、必要な情報を1カ所にまとめてお届けする方法です。Trans アクション al Messages を送信する際に守るべき法的な指針があることに注意してください。これらの指針がわからない場合は、内部の法務部に連絡してください。|
+| ジェネラルマーケティング | SMS メッセージは、ダイレクトで柔軟かつ効率的な方法で、今後のお買い得情報、有利なセール情報、現在または将来の販売商品などを顧客に伝えることができます。 |
+| リマインダー | SMS は、サービスのアポイントメントを設定したユーザーに通知を送るのに効果的です。例えば、診察予約の前日に SMS でリマインダーメッセージを送ることで、予約ミスを最小限に抑え、お客様と顧客の双方が時間とコストを節約することができます。 |
+| トランザクションメッセージ | SMSは、発注確認や発送情報などのアクション的な通知を効率的に発信し、必要な情報を1カ所にまとめてお届けする方法です。トランザクションメッセージを送信する際は、法的なガイドラインに準拠する必要があることに注意してください。これらの指針がわからない場合は、内部の法務部に連絡してください。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 要件
@@ -31,18 +31,18 @@ SMSの送信を開始する前に、いくつか必要なことがあります
 
 |要件 | 説明 | 取得 |
 |---|---|---|
-| 専用の電話番号(ショートコードまたはロングコード) | 単一のブランドまたはホストにのみ提供される専用の電話番号。 | Brazeは、これらの数値の取得を処理します。[short とlong コード s]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup/short_and_long_codes/) について詳しく説明します。|
-| 電話番号付きユーザー一覧 | メールの送信を始めるには、あらかじめユーザーsを登録しておく必要があります。さらに、オーディエンスの最大アプリ容量を知っておく必要があります。  | ユーザは最初、バックエンドを介してBrazeに追加されます。あなたはこの一覧を私たちにあなたのためにアップロードに渡さなければなりません。電話番号は、国名コードと同様に、10桁の数字でフォーマットする必要があります。[ユーザーの電話番号]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/)について詳しく知りたい。 |
-| [SMSキーワードとレスポンス]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/) | メッセージングを開始するには、すべての基本キーワードsに属性dのレスポンスが必要です | これらを記載し、オンボーディング中にBraze担当者またはオンボーディング マネージャーに送付してください。[SMS キーワード テンプレートs]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/sending_phone_numbers/#short-code-application)を表示します。 |
+| 専用の電話番号(ショートコードまたはロングコード) | 単一のブランドまたはホストにのみ提供される専用の電話番号。 | Braze がこれらの番号の取得を処理します。詳細については、[ショートコードとロングコード]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup/short_and_long_codes/)を参照してください。|
+| 電話番号付きユーザー一覧 | メールの送信を始めるには、あらかじめユーザーsを登録しておく必要があります。さらに、オーディエンスのおおよその規模を把握しておく必要があります。  | ユーザは最初、バックエンドを介してBrazeに追加されます。このリストは Braze に提供していただき、弊社がお客様用にアップロードします。電話番号は 10 桁の数字で記述し、国コードも指定します。詳細については、[ユーザーの電話番号]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/)を参照してください。 |
+| [SMS キーワードと応答]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/) | メッセージングを開始する前に、すべての基本キーワードに応答が属性付けられている必要があります。 | これらをリスト化し、オンボーディング中に Braze 担当者またはオンボーディングマネージャーに提供してください。[SMS キーワード テンプレートs]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/sending_phone_numbers/#short-code-application)を表示します。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 ## 知っておくべき用語
 
-- **短いコード:**5～6桁のコードで、完全な電話番号より短い。このコードは、SMSのアドレス指定と送信に使用されます。<br><br>
-- **長いコードs:**10桁のコードで、SMSの宛先として使用されます。ほとんどの平均的な電話番号は長いコードs と見なされます(e.g 123-456-7891)。これらのコードは、SMSのアドレス指定と送信に使用されます。<br><br>
-- **サブスクリプショングループ:**特定の種類のメッセージングに使用される、送信電話番号(短いコードs、長いコードs、英数字の送信者IDなど)の集まり。たとえば、ブランドがトランスアクションal とプロモーションSMS メッセージングの両方を送信する予定がある場合、電話番号を送信する別々のプールを持つ2 つのサブスクリプショングループをBraze ダッシュボード内に設定する必要があります。<br><br>
-- **メールSegmentと文字数制限:**メッセージSegmentとは、最初のSMSメッセージを分割するSegmentの数のことです。それぞれのメッセージには文字制限があり、それを超えるとメッセージはSegments に分割されます。使用するエンコード標準(UTF-2 またはGSM-7) に基づいて、さまざまな文字制限があります。メッセージング セグメンテーションとメッセージ文字の制限の詳細については、\[message copy limits][2] を参照してください。<br><br>
-- **一般的なSMS キャンペーンメトリクス:**<br>*送信済み*、*キャリアに送信*、*配信失敗*、*確認済み配信*、*拒否*、*Opt-Out*、*ヘルプ*。<br>これらのメトリクスについては、\[SMS レポート ing][1]を参照してください。*キャリアへの送信*は非推奨ですが、すでに存在するユーザーでは引き続きサポートされます。
+- **ショートコード:** 5～6桁のコードで、完全な電話番号より短い。このコードは、SMSのアドレス指定と送信に使用されます。<br><br>
+- **ロングコード:** 10桁のコードで、SMSの宛先として使用されます。ほとんどの平均的な電話番号は長いコードと見なされます (e.g 123-456-7891)。これらのコードは、SMSのアドレス指定と送信に使用されます。<br><br>
+- **サブスクリプショングループ:** 特定の種類のメッセージング目的で使用される送信電話番号 (ショートコード、ロングコード、英数字の送信者 ID など) のコレクションです。例えば、ブランドがトランザクションとプロモーションの両方の SMS メッセージを送信する予定がある場合は、Braze ダッシュボード内で、送信電話番号のプールを別々に持つ 2 つのサブスクリプショングループを設定する必要があります。<br><br>
+- **メッセージセグメントと文字数制限:** メッセージSegmentとは、最初のSMSメッセージを分割するSegmentの数のことです。それぞれのメッセージには文字制限があり、それを超えるとメッセージはSegments に分割されます。使用するエンコード標準(UTF-2 またはGSM-7) に基づいて、さまざまな文字制限があります。メッセージング セグメンテーションとメッセージ文字の制限の詳細については、\[message copy limits][2] を参照してください。<br><br>
+- **一般的な SMS キャンペーン指標:** <br>*送信済み*、*キャリアに送信*、*配信失敗*、*確認済み配信*、*拒否*、*Opt-Out*、*ヘルプ*。<br>これらの指標の詳細については、\[SMS レポート][1] を参照してください。\[*キャリアへの送信数*] は非推奨ですが、すでにご使用の場合は引き続きサポートされます。
 
 <br><br>
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/sms/campaign/create.md b/_lang/ja/_user_guide/message_building_by_channel/sms/campaign/create.md
index 5cca397fd12..e6384321e23 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/sms/campaign/create.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/sms/campaign/create.md
@@ -13,9 +13,9 @@ search_rank: 1
 
 # SMSメッセージを作成する
 
-> SMSキャンペーンは、顧客に直接アプローチし、プログラム上で会話するのに適している。Liquid などのダイナミックコンテンツを使用して、ユーザー一人ひとりに合わせた体験を作り出し、控えめなブランド体験を強化する環境を作ることができます。 
+> SMS キャンペーンは、顧客に直接リーチしてプログラムを使って会話を行うのに適しています。Liquid などのダイナミックコンテンツを使用して、ユーザー一人ひとりに合わせた体験を作り出し、控えめなブランド体験を強化する環境を作ることができます。 
 
-## ステップ 1:メッセージを作成する場所を選択する
+## ステップ 1: メッセージを作成する場所を選択する
 
 メッセージは、キャンペーンとキャンバスのどちらを使用して配信すべきでしょうか。キャンペーンは単一のシンプルなメッセージングキャンペーンに適していますが、キャンバスはマルチステップのユーザーのジャーニーに適しています。
 
@@ -24,13 +24,13 @@ search_rank: 1
 
 **ステップ:**
 
-1. **Messaging**>**Campaignsに**進み、**Create Campaignを**クリックする。
+1. \[**メッセージング**] > \[**キャンペーン**] に移動し、\[**キャンペーンを作成**] をクリックします。
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**エンゲージメント**] の下に \[**キャンペーン**] が表示されます。
 {% endalert %}
 
 {: start="2"}
-2\.**SMSを**選択するか、複数のチャネルを対象とするキャンペーンの場合は、**マルチチャネルキャンペーンを**選択する。
+2\.\[**SMS**] を選択するか、複数のチャネルを対象とするキャンペーンの場合は、\[**マルチチャネルキャンペーン**] を選択します。
 3\.キャンペーンに、明確で意味のある名前を付けます。
 4\.必要に応じて、\[[チーム]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/teams/)] と \[[タグ]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/)] を追加します。
    * タグを使用すると、キャンペーンを検索してレポートを作成しやすくなります。例えば、\[[レポートビルダー]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/)] を使用する場合、特定のタグでフィルターできます。
@@ -56,7 +56,7 @@ search_rank: 1
 {% endtab %}
 {% endtabs %}
 
-## ステップ 2:SMSを作成する
+## ステップ 2: SMSを作成する
 
 必要に応じて言語やパーソナライズ（リキッド、コネクテッド・コンテンツ、絵文字）を使ってメッセージを書く。超過料金を請求される可能性を減らすため、メッセージのコピー数制限を必ず守ること。
 
@@ -64,7 +64,7 @@ search_rank: 1
 先に進む前に、[SMSメッセージのセグメントとコピーの上限に関する]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/segments/)ガイドラインを読む。SMSメッセージ・セグメントとは、電話キャリアがテキスト・メッセージを測定するために使用する文字バッチのことである。メッセージはメッセージセグメントごとに課金されるため、メッセージの分割方法のニュアンスを理解しておくといいだろう。
 {% endalert %}
 
-![BrazeのコンポーザーにSMSで「Hi first_name, we appreciate your support！このSMSを見せれば、特別割引が適用される。私たちからのメッセージを受け取らないようにするには、STOPと返信すること。"]({% image_buster /assets/img/sms_campaign_compose.png %})
+![次のメッセージを含む Braze の SMS コンポーザー: 「first_name さん、いつも応援していただきありがとうございます。このSMSを見せれば、特別割引が適用される。メッセージの受信を中止するには STOP と返信してください。」]({% image_buster /assets/img/sms_campaign_compose.png %})
 
 {% alert tip %}
 {% raw %}
@@ -72,42 +72,42 @@ Liquidを使用する場合は、受信者のユーザープロファイルが
 {% endraw %}
 {% endalert %}
 
-素晴らしいコピーの作成にお困りですか？[AIコピーライティング・アシスタントを使って]({{site.baseurl}}/user_guide/intelligence/ai_copywriting/)みよう。商品名や説明を入力すると、AIが人間のようなマーケティングコピーを生成し、メッセージングに使用する。
+魅力的なコピーの作成にお困りですか?[AI コピーライティングアシスタント]({{site.baseurl}}/user_guide/intelligence/ai_copywriting/)を使用してみてください。商品名や説明を入力すると、AIが人間のようなマーケティングコピーを生成し、メッセージングに使用する。
 
-![SMSコンポーザーのメッセージ・フィールドにある「AIコピーライター」ボタンを起動する。]({% image_buster /assets/img/ai_copywriter/ai_copywriter_sms.png %}){: style="max-width:60%"}
+![SMS コンポーザーのメッセージフィールドにある \[AI コピーライター] ボタンをクリックする。]({% image_buster /assets/img/ai_copywriter/ai_copywriter_sms.png %}){: style="max-width:60%"}
 
-### 連絡先カード
+### コンタクトカード
 
-必要であれば、SMSメッセージに連絡先カードを追加して、顧客があなたのビジネスと連絡先情報を簡単に連絡先に追加できるようにすることもできる。これらのカードには、会社名、電話番号、住所、Eメール、小さな写真など、一般的なプロパティを割り当てることができる。詳しくは[コンタクトカードを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/contact_card/)ご覧いただきたい。
+必要であれば、SMSメッセージに連絡先カードを追加して、顧客があなたのビジネスと連絡先情報を簡単に連絡先に追加できるようにすることもできる。これらのカードには、会社名、電話番号、住所、Eメール、小さな写真など、一般的なプロパティを割り当てることができる。詳細については、[コンタクトカード]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/contact_card/)を参照してください。
 
-## ステップ 3:メッセージをプレビューしてテストする
+## ステップ 3: メッセージをプレビューしてテストする
 
 Brazeでは、送信前にメッセージをプレビューしてテストすることを常に推奨している。**テスト**タブに切り替えて、[コンテンツテストグループ]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#content-test-groups)または個々のユーザーにテストSMSを送信するか、Brazeで直接ユーザーとしてメッセージをプレビューする。
 
-![コンポーザーのテストタブからSMSコピーをプレビューする。プロフィール・セクションのファースト・ネーム・フィールドは "James "に設定されている。プレビュー・セクションでは、SMSに "Hi James, we appreciate your support!"]({% image_buster /assets/img/sms_campaign_test.png %}) と表示されるようになった。
+![コンポーザーのテストタブからの SMS コピーのプレビュー。プロファイルセクションの \[名] フィールドは「James」に設定されている。プレビュー・セクションでは、SMSに "Hi James, we appreciate your support!"]({% image_buster /assets/img/sms_campaign_test.png %}) と表示されるようになった。
 
 {% alert tip %}
 SMSがいくつのセグメントに分けられるかテストしたい場合は、[SMSセグメント計算機を使って]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/segments/#segment-calculator)コピーの長さをテストしてみよう。
 {% endalert %}
 
-## ステップ 4:キャンペーンまたはキャンバスの残りの部分を作成する
+## ステップ 4: キャンペーンまたはキャンバスの残りの部分を作成する
 
 {% tabs %}
 {% tab キャンペーン %}
 
-次に、キャンペーンの残りの部分を構築する。SMSメッセージの作成に最適なツールの使い方については、以下のセクションを参照のこと。
+次に、キャンペーンの残りの部分を作成します。SMSメッセージの作成に最適なツールの使い方については、以下のセクションを参照のこと。
 
 #### 配信スケジュールまたはトリガーを選択する
 
-SMSメッセージは、スケジュールされた時間、アクション、またはAPIトリガーに基づいて配信することができる。詳しくは、[キャンペーンのスケジューリングを]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/)参照のこと。
+SMS メッセージは、スケジュールされた時刻、アクション、または API トリガーに基づいて配信することができます。詳細については、[キャンペーンのスケジューリング]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/)を参照してください。
 
 アクションベースの配信では、キャンペーンの継続時間と \[[サイレント時間]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign/#quiet-hours)] を設定することもできます。
 
-このステップでは、ユーザーがキャンペーンを受信する[再資格を]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/#campaigns)得ることを許可したり、[頻度の上限]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)ルールを有効にしたりするなど、配信コントロールを指定することもできる。
+このステップでは、配信コントロールを指定できます。例えば、ユーザーを[再有効化]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/#campaigns)してキャンペーンを受信できるようにしたり、[フリークエンシーキャップ]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)ルールを有効にしたりできます。
 
 #### ターゲットとするユーザーを選択する
 
-次に、セグメントやフィルターを選択することで、[ユーザーを絞り込む]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)必要がある。すでにサブスクリプショングループを選択しているため、ユーザーがブランドに対して希望しているコミュニケーションの頻度やカテゴリによって、ユーザーが絞り込まれます。このステップでは、セグメントからより多くのオーディエンスを選択し、選択した場合はフィルターを使ってさらにセグメントを絞り込む。セグメントのおおよその人数について現在の状態を示すスナップショットが自動的に表示されます。正確なセグメントメンバーシップは常にメッセージが送信される直前に計算されることに注意してください。
+次に、セグメントまたはフィルターを選択して[ユーザーをターゲットに設定]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)し、オーディエンスを絞り込む必要があります。すでにサブスクリプショングループを選択しているため、ユーザーがブランドに対して希望しているコミュニケーションの頻度やカテゴリによって、ユーザーが絞り込まれます。このステップでは、セグメントからより多くのオーディエンスを選択し、必要であればフィルターを使ってさらにセグメントを絞り込みます。セグメントのおおよその人数について現在の状態を示すスナップショットが自動的に表示されます。正確なセグメントメンバーシップは常にメッセージが送信される直前に計算されることに注意してください。
 
 {% alert tip %}
 SMSリターゲティングに興味がある？詳しくはSMS[リターゲティングの記事を]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/retargeting/)ご覧いただきたい。
@@ -122,13 +122,13 @@ Braze では、キャンペーンを受信した後、ユーザーが指定の
 - ジオターゲティングを使用して、ユーザーが購入するという最終目標を持つSMSメッセージをトリガーする場合、コンバージョンイベントを`Purchase` 。
 - ユーザーをアプリに誘導しようとしている場合は、コンバージョンイベントを`Starts Session` に設定する。
 
-独自のユースケースに基づいて、カスタムコンバージョンイベントを設定することもできます。クリエイティブになり、このキャンペーンの成功をどのように測りたいかを考えよう。
+独自のユースケースに基づいて、カスタムコンバージョンイベントを設定することもできます。このキャンペーンの真の成功を測定する方法について独創的に考えてみましょう。
 
 {% endtab %}
 
 {% tab キャンバス %}
 
-まだやっていない場合は、キャンバス・コンポーネントの残りのセクションを完成させる。キャンバスの残りの部分の構築方法、多変量テストとインテリジェントセレクションの実装方法などの詳細については、キャンバスドキュメントの「[キャンバスを構築する」]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-3-build-your-canvas)ステップを参照のこと。
+キャンバスコンポーネントが完成していない場合、残りのセクションを完成させます。キャンバスの残りの部分の構築方法、多変量テストとインテリジェントセレクションの実装方法などの詳細については、キャンバスドキュメントの「[キャンバスを構築する」]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-3-build-your-canvas)ステップを参照のこと。
 
 {% endtab %}
 {% endtabs %}
@@ -137,4 +137,4 @@ Braze では、キャンペーンを受信した後、ユーザーが指定の
 
 キャンペーンやキャンバスの最後の構築が終わったら、その詳細を確認し、テストしてから送信する！
 
-次に、[SMS reporting]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_campaign_analytics/)をチェックして、SMSキャンペーンの結果にアクセスする方法を学びましょう。
+次に、[SMS レポート]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_campaign_analytics/)をチェックして、SMS キャンペーンの結果にアクセスする方法を確認します。
diff --git a/_lang/ja/_user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out.md b/_lang/ja/_user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out.md
index 6de1fba5680..b58599544da 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out.md
@@ -1,6 +1,6 @@
 ---
-nav_title: ファジィオプトアウト
-article_title: ファジィオプトアウト
+nav_title: あいまいなオプトアウト
+article_title: あいまいなオプトアウト
 description: "このリファレンス記事では、受信メッセージがオプトアウトキーワードと一致しない場合に認識しようとする設定であるファジィオプトアウトを設定する方法について説明します。"
 page_type: reference
 channel:
@@ -9,34 +9,34 @@ page_order: 1
 
 ---
 
-# ファジィオプトアウト
+# あいまいなオプトアウト
 
 ![][1]{: style="float:right;max-width:30%;margin-left:15px;"}
 
-> Braze を使用してSMS を送信するユーザは、定義されているアプリのライセンス適用法令、規則、および業界標準に準拠している必要があります。オプトアウトの場合、ユーザーのテキストが"STOP"のとき、そのメッセージング番組に関連した後続のすべてのメッセージングが停止されることが法則で定められています。Braze はこれらのメッセージを自動的に処理し、ユーザーを配信停止します。<br><br>ファジィオプトアウトは、受信メッセージが[opt-out キーワード]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/optin_optout/)と一致しないときを認識しようとしますが、オプトアウトインテントを示します。fuzzy opt-out が有効で、受信キーワードレスポンスが"fuzzy," Braze が自動的に応答し、ユーザーにそのインテントを確認するように求めます。 
+> Braze を使用して SMS を送信するユーザーは、定義されているアプリのライセンス適用法令、規則、および業界標準に従う必要があります。オプトアウトでは、ユーザーのテキストが「STOP」の場合、そのメッセージングプログラムに関連する後続のすべてのメッセージングを停止することが法で定められています。Braze はこれらのメッセージを自動的に処理し、ユーザーへの配信を停止します。<br><br>[あいまいなオプトアウト]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/optin_optout/)は、インバウンドメッセージがオプトアウトキーワードと一致しなくても、オプトアウトのインテントを示している場合に、それを認識しようとします。あいまいなオプトアウトが有効で、受信キーワードの応答が「あいまい」であると見なされた場合、Braze は自動的に応答し、ユーザーにそのインテントを確認するように求めます。 
 
 現在、[ローカル言語]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/keyword_handling/#multi-language-support)として英語を使用して作成されたオプトアウトキーワードのみがサポートされています。
 
-## ファジィとは何か?
+## 「あいまい」の基準
 
-インバウンド応答が"fuzzy&quot とみなされる基準は次のとおりです。
-- 切り替えるに、文字がQWERTY キーワードの左右に1 つある文字を指定すると、一致するオプトアウトキーワードが生成されます。
+インバウンド応答が「あいまい」と見なされる基準は次のとおりです。
+- QWERTY キーボードで左右隣にある文字に置き換えると一致するオプトアウトキーワードが生成される場合
 - メッセージの部分文字列は、オプトアウトキーワードと一致します。
 
-たとえば、"Stpo"または"Please stopppp"はファジーと見なされ、ファジーオプトアウト応答が送信されます。
+たとえば、「Stpo」や「Please stopppp」はあいまいと見なされ、あいまいなオプトアウト応答が送信されます。
 
 ## ファジィオプトアウトの設定
 
 ファジィオプトアウトを設定するには、サブスクリプショングループ キーワードマネジメントページに移動します。
 
-1. **Audience**> **サブスクリプション s** に進み、SMS サブスクリプショングループを選択します。
+1. \[**オーディエンス**] > \[**サブスクリプション**] に移動して、SMS サブスクリプショングループを選択します。
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation) を使用している場合、**Subscription Groups** は**Users** にあります。
 {% endalert %}
 
 {:start="2"}
 2\.**SMS Global Keywords**で、**opt-out**カテゴリを見つけ、鉛筆アイコンを選択します。
-3\.**Fuzzy Opt-Out**をオンに切り替えて有効にします。
+3\.\[**あいまいなオプトアウト**] をオンに切り替えて有効にします。
 4\.必要に応じて、ファジィオプトアウト応答を変更します。 
 
 ![][2]{: style="max-width:70%;"}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/sms/mms/faqs.md b/_lang/ja/_user_guide/message_building_by_channel/sms/mms/faqs.md
index 5e1a25c0441..ec125e925cf 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/sms/mms/faqs.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/sms/mms/faqs.md
@@ -19,7 +19,7 @@ channel:
 
 ### MMSの画像とメッセージ本文が配信される順序をコントロールできますか？
 
-Brazeは、MMSメッセージにメッセージ本文と画像の両方が含まれている場合の表示順序をコントロールすることはできません。これは、いくつかの要因に依存しますが、これらに限定されません。
+Brazeは、MMSメッセージにメッセージ本文と画像の両方が含まれている場合の表示順序をコントロールすることはできません。これは、以下のようないくつかの要因に依存しますが、これらに限定されません。
 
 - メッセージを受信するキャリア
 - メッセージを受信するデバイス
@@ -27,19 +27,19 @@ Brazeは、MMSメッセージにメッセージ本文と画像の両方が含ま
 
 ### MMSとSMSの料金は異なりますか？
 
-MMSとSMSは異なるコストがかかり、ボリュームに基づいて別々に請求されます。Brazeオンボーディングチームに価格情報をお問い合わせください。
+MMSとSMSは異なるコストがかかり、ボリュームに基づいて別々に請求されます。価格については Braze オンボーディングチームにお問い合わせください。
 
 ### MMSには別のオンボーディングプロセスが必要ですか？
 
-いいえ。MMSは現在、SMSオンボーディングプロセスに含まれています。既存の顧客は、すでにオンボーディングを完了している場合、次の手順を完了した後、MMSキャンペーンの送信を開始できます:
+いいえ。MMSは現在、SMSオンボーディングプロセスに含まれています。オンボーディングをすでに完了している既存の顧客は、以下のステップを完了した後、MMS キャンペーンの送信を始めることができます。
 
 1. MMSを購入する。
-2. MMS機能を有効にするよう依頼するには、Brazeオンボーディングチームに連絡してください。これによりMMSが有効になり、SMS/MMSサブスクリプショングループが作成または更新されます。
+2. Braze オンボーディングチームに連絡して MMS 機能をオンにするよう依頼します。これによりMMSが有効になり、SMS/MMSサブスクリプショングループが作成または更新されます。
 
 次に、Brazeのオンボーディングチームが、MMSのために短縮コードと長コードが（米国およびカナダで）有効になっていることを確認します。また、サブスクリプショングループを更新して、MMS用に追加または有効化された現在の番号を表示します。これらの手順が完了すると、ネイティブのSMS作成ツールからすぐにMMSメッセージを送信できます。
 
 ### なぜ機能が有効になっているのにダッシュボードにMMSが見つからないのですか？
 
-MMSは、サブスクリプショングループが「MMS対応」と見なされる場合にのみ、Brazeダッシュボードに表示されます。これは、SMS/MMSメッセージの作成者がサブスクリプショングループを選択する際に、MMSタグによって反映されます。これは、サブスクリプショングループ内の少なくとも1つの番号がMMSメッセージを送信できることを意味します。
+MMSは、サブスクリプショングループが「MMS対応」と見なされる場合にのみ、Brazeダッシュボードに表示されます。これは、SMS/MMS メッセージの作成画面でサブスクリプショングループを選択するときに MMS タグに反映されます。これは、サブスクリプショングループ内の少なくとも1つの番号がMMSメッセージを送信できることを意味します。
 
-さらに、特定の状況では、MMSが有効になっていなかったショートコードのイネーブルメントを再承認する必要があります。この承認プロセスには数週間かかる可能性があります。
+さらに、場合によっては、Twilio が元々 MMS が有効になっていなかった短いコードのイネーブルメントを再承認する必要があります。この承認プロセスには数週間かかる可能性があります。
diff --git a/_lang/ja/_user_guide/message_building_by_channel/sms/sms_setup.md b/_lang/ja/_user_guide/message_building_by_channel/sms/sms_setup.md
index ba9a76cb310..1fd7083d088 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/sms/sms_setup.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/sms/sms_setup.md
@@ -21,7 +21,7 @@ guide_featured_list:
 - name: SMSメッセージ送信
   link: /docs/user_guide/message_building_by_channel/sms/sms_setup/sms_sending/
   image: /assets/img/braze_icons/message-square-02.svg
-- name: SMS購読グループ
+- name: SMS サブスクリプショングループ
   link: /docs/user_guide/message_building_by_channel/sms/sms_subscription_group/
   image: /assets/img/braze_icons/users-01.svg
   
diff --git a/_lang/ja/_user_guide/message_building_by_channel/sms/sms_setup/user_data_migration.md b/_lang/ja/_user_guide/message_building_by_channel/sms/sms_setup/user_data_migration.md
index 02a6543c17b..3f5b81732b4 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/sms/sms_setup/user_data_migration.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/sms/sms_setup/user_data_migration.md
@@ -24,7 +24,7 @@ noindex: true
 
 ## ユーザーのサブスクリプション状態に関する履歴情報を更新する
 
-ユーザーの\[サブスクリプション状態]\[サブスクリプション状態]の様々なメッセージングチャネルに関する履歴情報がある場合は、この情報をBrazeで更新してください。
+ユーザーの\[サブスクリプション状態]\[サブスクリプション状態] のさまざまなメッセージングチャネルに関する履歴情報がある場合は、必ず Braze でこの情報を更新してください。
 
 ## 例の移行手順
 
@@ -35,7 +35,7 @@ Brazeを通じてSMSキャンペーンを作成し始める前に、すべてが
 1. **ユーザーの電話番号を正しい形式でインポートする** ([E.164][0]) フォーマットにはプラス記号（+）と国コードが必要です。例としては+12408884782です。ユーザーの電話番号のインポート方法の詳細については、[ユーザーの電話番号][userphone]をご覧ください。
     * [`/users/track`エンドポイント][1]を使用して`phone`値を割り当てます。<br><br>
 
-2. **ユーザーのSMSサブスクリプション状態]\[subscriptionstate]**（購読中や購読解除など）を割り当てます。もしこの情報を持っている場合。
+2. 情報がある場合、**ユーザーの SMS \[サブスクリプション状態]\[サブスクリプション状態]を割り当てます** (配信登録済み、配信停止済みなど)。
     * [`/subscription/status/set`エンドポイント][6]を使用して、ユーザーをSMSサブスクリプショングループにサブスクライブまたはサブスクライブ解除として設定します。
 
 {% alert note %}
@@ -50,6 +50,6 @@ Brazeを通じてSMSキャンペーンを作成し始める前に、すべてが
 [4]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/analytics/setting_user_ids/#aliasing-users
 [5]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/setting_user_ids/#aliasing-users
 [6]: {{site.baseurl}}/api/endpoints/subscription_groups/post_update_user_subscription_group_status/
-\[絵]: {% image_buster /assets/img/sms/e164.jpg %}
+\[picture]: {% image_buster /assets/img/sms/e164.jpg %}
 \[customkeyword]: {{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/custom_keyword_handling/
 \[subscriptionstate]: {{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/#sms-subscription-states
diff --git a/_lang/ja/_user_guide/message_building_by_channel/webhooks.md b/_lang/ja/_user_guide/message_building_by_channel/webhooks.md
index 30d79f54056..537ed23dac4 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/webhooks.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/webhooks.md
@@ -5,13 +5,13 @@ page_order: 4
 layout: dev_guide
 guide_top_header: "Webhook"
 guide_top_text: "Webhookはあらゆることに使える。以下の記事をチェックし、柔軟な発送を心がけよう。"
-description: "このランディング・ページにはウェブフックがある。ここでは、ウェブフックの作成、ウェブフックテンプレートの作成、Braze-to-Brazeウェブフックに関する記事を見ることができる。"
+description: "このランディングページは Webhook のホームページです。ここでは、ウェブフックの作成、ウェブフックテンプレートの作成、Braze-to-Brazeウェブフックに関する記事を見ることができる。"
 channel:
   - webhooks
 search_rank: 3
 guide_featured_title: "セクションの記事"
 guide_featured_list:
-- name: ウェブフックについて
+- name: Webhook について
   link: /docs/user_guide/message_building_by_channel/webhooks/understanding_webhooks/
   image: /assets/img/braze_icons/check-square-broken.svg
 - name: Webhookを作成する
@@ -20,7 +20,7 @@ guide_featured_list:
 - name: Webhookテンプレートを作成する
   link: /docs/user_guide/message_building_by_channel/webhooks/webhook_template/
   image: /assets/img/braze_icons/table.svg
-- name: ブレイズ・トゥ・ブレイズ・ウェブフック
+- name: Braze-to-Braze Webhook
   link: /docs/user_guide/message_building_by_channel/webhooks/braze_to_braze_webhooks/
   image: /assets/img/braze_icons/switch-horizontal-01.svg
 - name: レポート
diff --git a/_lang/ja/_user_guide/message_building_by_channel/webhooks/braze_to_braze_webhooks.md b/_lang/ja/_user_guide/message_building_by_channel/webhooks/braze_to_braze_webhooks.md
index 3bf7fcadaa4..ae1412cd8a9 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/webhooks/braze_to_braze_webhooks.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/webhooks/braze_to_braze_webhooks.md
@@ -1,20 +1,20 @@
 ---
-nav_title: ブレイズ・トゥ・ブレイズ・ウェブフック
-article_title: ブレイズ・トゥ・ブレイズ・ウェブフック
+nav_title: Braze-to-Braze Webhook
+article_title: Braze-to-Braze Webhook
 page_order: 3
 channel:
   - webhooks
-description: "この記事では、Braze-to-Brazeウェブフックの作成方法について説明する。"
+description: "この記事では、主なユースケースのために Braze-to-Braze Webhook を作成する方法について説明します。"
 
 ---
 
-# Braze-to-Brazeウェブフック
+# Braze-to-Braze Webhook
 
-> Webhookを使用して、Braze \[REST API][2]] と通信することができる。私たちはこれをBraze-to-Braze webhook-BrazeからBrazeへ通信するwebhookと呼んでいる。
+> Webhook を使用して、Braze \[REST API][2] と通信することができます。基本的には、API で行えるすべての操作を実行できます。弊社では、このように Braze から Braze へ通信する Webhook のことを Braze-to-Braze Webhook と呼んでいます。
 
 ## 前提条件
 
-Braze-to-BrazeのWebhookを作成するには、到達したいエンドポイントのパーミッションを持つ\[APIキー][3] ]が必要だ。
+Braze-to-Braze Webhook を作成するには、目的のエンドポイントの権限を持つ \[APIキー][3] が必要です。
 
 ## ユースケース
 
@@ -24,42 +24,42 @@ Braze-to-BrazeのWebhookでできることはたくさんあるが、ここで
 - 最初のキャンバスから2番目のキャンバスをトリガーする。
 
 {% alert tip %}
-[ユーザー更新ステップを]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/user_update/)キャンバスに追加して、ユーザーの属性、イベント、購入をJSONコンポーザーで追跡する。こうすることで、BrazeがBraze-to-Braze webhookよりも効率的に更新を処理できるように、これらの更新はバッチ処理される。
+[ユーザー更新ステップ]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/user_update/)をキャンバスに追加して、ユーザーの属性、イベント、および購入を JSON 作成画面で追跡します。こうすると更新がバッチ処理され、Braze が Braze-to-Braze Webhook よりも効率的に更新を処理できます。
 {% endalert %}
 
 このページの使用例は、\[Webhookがどのように機能するか][4] ]と\[BrazeでWebhookを作成する方法][5] ]をすでに知っていることを前提としている。
 
-## Braze-to-Brazeウェブフックの作成手順
+## Braze-to-Braze Webhook の作成手順
 
-Webhookリクエストの詳細はユースケースによって異なるが、Braze-to-Braze Webhookを作成するための一般的なワークフローは変わらない。
+Webhook リクエストの詳細はユースケースによって異なりますが、Braze-to-Braze Webhook を作成するための一般的なワークフローは変わりません。
 
-1. \[キャンペーンまたはキャンバスのコンポーネントとしてウェブフック][5] を作成する。 
-2. **空白のテンプレートを**選択する。
-3. **Compose**タブで、**Webhook URLと** **Request Bodyを**ユースケースに応じて指定する。
-4. **Settings "**タブで、**HTTPメソッドと** **リクエスト・ヘッダを**指定する。
-5. 必要に応じて、Webhookの残りの部分を構築し続ける。ユースケースによっては、カスタムイベントからキャンペーンやキャンバスをトリガーするなど、特定の配信設定が必要なものもある。
+1. キャンペーンまたはキャンバスのコンポーネントとして \[ウェブフックを作成][5] します。 
+2. \[**空白のテンプレート**] を選択します。
+3. \[**Compose**] タブで、\[**Webhook URL**] と \[**リクエスト本文**] をユースケースに応じて指定します。
+4. \[**設定**] タブで、\[**HTTP メソッド**] と \[**リクエストヘッダー**] を指定します。
+5. 必要に応じて、Webhook の残りの部分を引き続き作成します。ユースケースによっては、カスタムイベントからキャンペーンやキャンバスをトリガーするなど、特定の配信設定が必要なものもあります。
 
 ### ユースケース:カウンターの整数カスタム属性をインクリメントする
 
 この使用例では、カスタム属性を作成し、特定のアクションが発生した回数をカウントするためにLiquidを使用する。 
 
-例えば、ユーザーがアクティブなアプリ内メッセージ・キャンペーンを何回見たかをカウントし、3回見たら二度とキャンペーンを受け取らないようにしたい場合がある。BrazeのLiquidロジックで何ができるか、より多くのアイデアについては、[Liquidユースケースライブラリを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases)チェックしよう。
+例えば、ユーザーがアクティブなアプリ内メッセージ・キャンペーンを何回見たかをカウントし、3回見たら二度とキャンペーンを受け取らないようにしたい場合がある。Braze の Liquid ロジックでできることのアイデアについては、[Liquid ユースケースライブラリ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases)を参照してください。
 
 Braze-to-BrazeのWebhookを作成するための一般的な手順に従い、Webhookを設定する際には以下を参照すること：
 
-- **Webhook URL:**あなたの\[RESTエンドポイントURL][7] の後に`/users/track`.例えば、US-06のインスタンスの場合、URLは`https://rest.iad-06.braze.com/users/track` となる。
+- **Webhook URL:**\[REST エンドポイント URL][7] の後に `/users/track` を続けます。例えば、US-06 のインスタンスの場合、URL は `https://rest.iad-06.braze.com/users/track` となります。
 - **要求本文:**Raw Text
 
 #### リクエストヘッダと方法
 
-Brazeは認証のために、APIキーと`content-type` を宣言するHTTPヘッダーを要求する。
+Braze には、API キーを含む認証用の HTTP ヘッダーと、`content-type` を宣言する別の HTTP ヘッダーが必要です。
 
 - **要求ヘッダー:**
-  - **認可する：**Bearer {YOUR_API_KEY}
+  - **認証:** Bearer {YOUR_API_KEY}
   - **Content-Type:**application/json
 - **HTTP メソッド:**POST
 
-`YOUR_API_KEY` を、`users.track` 権限を持つ Braze API キーに置き換える。APIキーは、Brazeダッシュボードの**「設定」**>「**APIキー**」で作成できる。
+`YOUR_API_KEY` を、`users.track` 権限を持つ Braze API キーに置き換えます。APIキーは、Brazeダッシュボードの**「設定」**>「**APIキー**」で作成できる。
 
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**開発者コンソール**] > \[**API 設定**] から API キーを作成できます。
@@ -69,9 +69,9 @@ Brazeは認証のために、APIキーと`content-type` を宣言するHTTPヘ
 
 #### Request body
 
-リクエストボディにユーザートラックリクエストを追加し、リキッドにカウンタ変数を代入する。詳しくは\[ユーザートラック][8]]を参照のこと。
+リクエスト本文にユーザー追跡リクエストと、カウンター変数を代入する Liquid を追加します。詳細については、\[ユーザー追跡][8]] を参照してください。
 
-以下は、このエンドポイントに必要なリキッドとリクエストボディの例である。`your_attribute_count` は、ユーザーがメッセージを見た回数をカウントするために使用する属性である： {% raw %}
+以下は、このエンドポイントに必要な Liquid とリクエスト本文の両方の例です。`your_attribute_count` はユーザーがメッセージを見た回数をカウントするために使用する属性です： {% raw %}
 
 ```json
 {% assign new_number = {{custom_attribute.${your_attribute_count}}} | plus: 1 %}
@@ -87,34 +87,34 @@ Brazeは認証のために、APIキーと`content-type` を宣言するHTTPヘ
 {% endraw %}
 
 {% alert note %}
-カスタム属性カウンターが更新（インクリメントまたはデクリメント）されるたびに、[データポイントが]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points/)消費される。
+カスタム属性カウンターが更新 (増加または減少) されるたびに、[データポイント]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points/)が消費され、これは総消費量に加算されます。
 {% endalert %}
 
 ### ユースケース:最初のキャンバスから2番目のキャンバスをトリガーする
 
-この使用例では、2つのCanvasを作成し、最初のCanvasから2つ目のCanvasをトリガーするためにウェブフックを使用する。これは、ユーザーが別のキャンバスのあるポイントに到達したときのエントリートリガーのような役割を果たす。
+この使用例では、2つのCanvasを作成し、最初のCanvasから2つ目のCanvasをトリガーするためにウェブフックを使用する。これは、ユーザーが別のキャンバス内の特定ポイントに到達したときのエントリトリガーのような役割を果たします。
 
-1. 最初のキャンバスによってトリガーされるキャンバスである。 
-2. キャンバスの**入力スケジュールで**、**API-Triggeredを**選択する。
-3. **キャンバスIDを控えて**おくこと。これは後のステップで必要になる。
-4. 2つ目のキャンバスのステップを作り続け、キャンバスを保存する。
+1. まず、2 つ目のキャンバスを作成します。これは最初のキャンバスによってトリガーされるキャンバスです。 
+2. キャンバスの**エントリスケジュール**で、\[**API トリガー**] を選択します。
+3. **キャンバス ID** を書き留めます。これは後のステップで必要になる。
+4. 続いて 2 つ目のキャンバスのステップを作成し、キャンバスを保存します。
 5. 最後に、最初のキャンバスを作成する。2つ目のキャンバスをトリガーしたいステップを見つけ、ウェブフック付きの新しいステップを作成する。 
 
 ウェブフックを設定する際は、以下を参照のこと：
 
-- **Webhook URL:**あなたの\[RESTエンドポイントURL][7] の後に`canvas/trigger/send`.例えば、US-06のインスタンスの場合、URLは`https://rest.iad-06.braze.com/canvas/trigger/send` となる。
+- **Webhook URL:**\[REST エンドポイント URL][7] の後に `canvas/trigger/send` を続けます。例えば、US-06 のインスタンスの場合、URL は `https://rest.iad-06.braze.com/canvas/trigger/send` となります。
 - **要求本文:**Raw Text
 
 #### リクエストヘッダと方法
 
-Brazeは認証のために、APIキーと`content-type` を宣言するHTTPヘッダーを要求する。
+Braze には、API キーを含む認証用の HTTP ヘッダーと、`content-type` を宣言する別の HTTP ヘッダーが必要です。
 
 - **要求ヘッダー:**
-  - **認可する：**ベアラー `YOUR_API_KEY`
+  - **認証:** ベアラー `YOUR_API_KEY`
   - **Content-Type:**application/json
 - **HTTP メソッド:**POST
 
-`YOUR_API_KEY` を、`canvas.trigger.send` 権限を持つ Braze API キーに置き換える。APIキーは、Brazeダッシュボードの**「設定」**>「**APIキー**」で作成できる。
+`YOUR_API_KEY` を、`canvas.trigger.send` 権限を持つ Braze API キーに置き換えます。APIキーは、Brazeダッシュボードの**「設定」**>「**APIキー**」で作成できる。
 
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**開発者コンソール**] > \[**API 設定**] から API キーを作成できます。
@@ -124,7 +124,7 @@ Brazeは認証のために、APIキーと`content-type` を宣言するHTTPヘ
 
 #### Request body
 
-テキストフィールドに`canvas/trigger/send` リクエストを追加する。詳細については、\[APIトリガー配信によるCanvasメッセージの送信][9] を参照のこと。以下は、このエンドポイントのリクエストボディの例である。`your_canvas_id` は、2番目のキャンバスのキャンバスIDである： 
+テキストフィールドに`canvas/trigger/send` リクエストを追加する。詳細については、\[API トリガー配信によるキャンバスメッセージの送信][9] を参照してください。以下はこのエンドポイントのリクエスト本文の例です。ここで `your_canvas_id` は、2 つ目のキャンバスのキャンバス ID です:  
 
 {% raw %}
 ```json
@@ -141,9 +141,9 @@ Brazeは認証のために、APIキーと`content-type` を宣言するHTTPヘ
 
 ## 知っておくべきこと
 
-- Braze-to-BrazeのWebhookは、エンドポイントの[レート制限に]({{site.baseurl}}/api/api_limits/)従う。
+- Braze-to-Braze Webhook は、エンドポイントの[レート制限]({{site.baseurl}}/api/api_limits/)の対象となります。
 - ユーザー・プロフィールの更新には追加の[データ・ポイントが]({{site.baseurl}}/user_guide/onboarding_with_braze/data_points/#consumption-count)発生するが、メッセージング・エンドポイントを通じて別のメッセージがトリガーされることはない。
-- [匿名ユーザーを]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle#anonymous-user-profiles)ターゲットにしたい場合は、Webhookのリクエスト本文で、`external_id` の代わりに`braze_id` を使うことができる。
+- [匿名ユーザー]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle#anonymous-user-profiles)をターゲットにしたい場合は、Webhook のリクエスト本文で、`external_id` の代わりに`braze_id` を使用できます。
 - Braze-to-Brazeウェブフックを[テンプレートとして]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/webhook_template/)保存し、再利用することができる。
 - [メッセージ・アクティビティ・ログを]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/message_activity_log_tab/)チェックして、ウェブフックの失敗を確認し、トラブルシューティングすることができる。
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/webhooks/reporting.md b/_lang/ja/_user_guide/message_building_by_channel/webhooks/reporting.md
index 4d67dc8445d..699af080ed4 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/webhooks/reporting.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/webhooks/reporting.md
@@ -2,7 +2,7 @@
 nav_title: レポート
 article_title: ウェブフック・レポート
 page_order: 10
-description: "この参考記事では、Brazeダッシュボードで提供されるさまざまなWebhookレポートメトリクスと分析オプションの概要を説明する。"
+description: "この記事では、Braze ダッシュボードで提供されるさまざまな Webhook レポート指標と分析オプションの概要について説明します。"
 channel:
   - webhooks
 tool:
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp.md
index 4df52dedfeb..6d29a973067 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp.md
@@ -6,8 +6,8 @@ layout: dev_guide
 channel:
   - WhatsApp
 guide_top_header: "WhatsApp"
-guide_top_text: "WhatsApp は、企業向けの対話ベースのメッセージングを提供する、世界中で使用されている人気のピアツーピアメッセージング プラットフォームです。WhatsApp メッセージング チャネルは、WhatsApp プラットフォーム上のユーザーs および顧客s に直接到達する方法を提供します。<br><br>** WhatsApp接続は、一部のBrazeでのみ利用できます。開始するには、アカウントマネージャーまたは顧客のサクセスマネージャーに到達してください。**"
-description: "このランディングページは、WhatsApp キャンペーンの作成方法、オプトインとオプトアウト、クイックリプライ、レポートリングなど、すべてのWhatsAppのホームページです。"
+guide_top_text: "WhatsApp は、企業向けの対話ベースのメッセージングを提供する、世界中で使用されている人気のピアツーピアメッセージング プラットフォームです。WhatsApp メッセージングチャネルは、WhatsApp プラットフォーム上のユーザーと顧客に直接リーチする方法を提供します。<br><br>** WhatsApp アクセスは、一部の Braze パッケージでのみ使用できます。使い始める場合は、アカウントマネージャーまたはカスタマーサクセスマネージャーにお問い合わせください。**"
+description: "このランディングページは、WhatsApp キャンペーンの作成方法、オプトインとオプトアウト、クイック返信、レポートなど、WhatsApp のすべての機能のホームページです。"
 search_rank: 3
 alias: /whatsapp/
 
@@ -22,7 +22,7 @@ guide_featured_list:
 - name: "ユーザーの電話番号"
   link: /docs/user_guide/message_building_by_channel/whatsapp/user_phone_numbers/
   image: /assets/img/braze_icons/phone-02.svg
-- name: "WhatsAppの作成"
+- name: "WhatsApp キャンペーンの作成"
   link: /docs/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create/
   image: /assets/img/braze_icons/phone-02.svg
 - name: "ユーザーのリターゲット"
@@ -34,7 +34,7 @@ guide_featured_list:
 - name: "ユーザーへのメッセージング"
   link: /docs/user_guide/message_building_by_channel/whatsapp/message_processing/user_messages/
   image: /assets/img/braze_icons/message-chat-circle.svg
-- name: "不明な電話番号を扱う"
+- name: "不明な電話番号の処理"
   link: /docs/user_guide/message_building_by_channel/whatsapp/message_processing/handling_unknown_numbers/
 - name: "WhatsApp販売試験"
   link: /docs/user_guide/message_building_by_channel/whatsapp/message_processing/experiments/
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/message_processing/handling_unknown_numbers.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/message_processing/handling_unknown_numbers.md
index 055817c4bbc..43afae851f8 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/message_processing/handling_unknown_numbers.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/message_processing/handling_unknown_numbers.md
@@ -14,20 +14,20 @@ page_order: 50
 
 ## 不明な番号に対するオプトイン/アウトおよびカスタム・キーワード・ワークフロー
 
-Brazeはまず、番号の一致するユーザーを探そうとする。もし見つからない場合、Brazeは自動的に2つの方法のいずれかで未知の番号に対応する：
+Brazeはまず、番号の一致するユーザーを探そうとする。何も見つからない場合、Braze は 2 つの方法のいずれかで不明な番号を自動的に処理します。
 
-1. **[オプトイン・キャンバスの]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/message_processing/opt-ins_and_opt-outs/)トリガー・ワードが設定されている場合：**
-- Brazeは匿名のプロフィールを作成する
-- プロファイルには、以下の詳細でユーザーエイリアスを割り当てる：
-  - `alias_name` 、値はユーザーが提供した電話番号である。
-  - `alias_label` 。 `phone`
-- 私たちのシステムは電話属性を設定する
+1. **\[[オプトインキャンバス]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/message_processing/opt-ins_and_opt-outs/)] のトリガーワードが設定されている場合**
+- Braze によって匿名プロファイルが作成される
+- プロファイルに以下の詳細を持つユーザーエイリアスを割り当てる
+  - `alias_name` - 値はユーザーが提供した電話番号
+  - `alias_label` - 値は `phone`
+- システムによって phone 属性が設定される
 - ユーザーは、キャンバス内で設定されたロジックに基づいて、対応するサブスクリプショングループにサブスクライブされる。<br><br>
-2. **オプトイン・キャンバスが設定されていない場合：**
-- Brazeは匿名のプロフィールを作成する
-- プロファイルには、以下の詳細でユーザーエイリアスを割り当てる：
-  - `alias_name` 、値はユーザーが提供した電話番号である。
-  - `alias_label` 。 `phone`
-- 私たちのシステムは電話属性を設定する
-- 全てのWhatsApp購読グループにおいて、ユーザーの購読ステータスがデフォルトで`unsubscribed` 。<br><br>
+2. **オプトインキャンバスが設定されていない場合**
+- Braze によって匿名プロファイルが作成される
+- プロファイルに以下の詳細を持つユーザーエイリアスを割り当てる
+  - `alias_name` - 値はユーザーが提供した電話番号
+  - `alias_label` - 値は `phone`
+- システムによって phone 属性が設定される
+- ユーザーのサブスクリプションステータスは、すべての WhatsApp サブスクリプションググループでデフォルトの `unsubscribed` になる<br><br>
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/message_processing/user_messages.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/message_processing/user_messages.md
index 036bd4ae612..6ccf4f40bef 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/message_processing/user_messages.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/message_processing/user_messages.md
@@ -12,17 +12,17 @@ alias: /user_guide/message_building_by_channel/whatsapp/quick_replies/
 
 # ユーザーメッセージ
 
-> WhatsAppは双方向のコミュニケーションチャネルだ。あなたのブランドはユーザーにメッセージを送ることができるだけでなく、テンプレート化されたキャンペーンやCanvasesを使ってユーザーと会話をすることができる。WhatsAppのクイック返信やトリガーワードなど、様々な方法がある。クイック返信コールトゥアクション(CTA)はWhatsAppメッセージのユーザーエンゲージメントを促進する優れた方法。
+> WhatsAppは双方向のコミュニケーションチャネルだ。あなたのブランドはユーザーにメッセージを送ることができるだけでなく、テンプレート化されたキャンペーンやCanvasesを使ってユーザーと会話をすることができる。WhatsAppのクイック返信やトリガーワードなど、様々な方法がある。クイック返信コールトゥアクション (CTA) は、WhatsApp メッセージのユーザーエンゲージメントを促進する優れた方法です。
 
 ## アクションベースのトリガー 
 
-キャンペーンもキャンバスも、WhatsAppのインバウンドメッセージ（ユーザーがあなたのWhatsAppにメッセージを送ること）をトリガーワードとして、開始、分岐、途中変更を行うことができる。 
+キャンペーンとキャンバスはどちらも、トリガーワードなどのインバウンド WhatsApp メッセージ (ユーザーからの WhatsApp メッセージ) から、開始、分岐、および中間ジャーニーの変更を行うことができます。 
 
 トリガー・ワードが、ユーザーから期待されているものと一致していることを確認する。
 
 **知っておくべきこと**
-- トリガー・ワードの各文字は大文字で構成されなければならない。Brazeは、ユーザーが送信するインバウンドのトリガーワードを大文字にする必要はない。例えば、"jOin2023 "とメッセージを送っても、キャンバスやキャンペーンはトリガーされる。
-- エントリースケジュールのアクションベーストリガーにトリガーワードが指定されていない場合、キャンペーンまたはキャンバスは全てのインバウンドメッセージに対して実行される。これには、アクティブなキャンペーンやキャンバスでフレーズが一致したメッセージも含まれ、この場合、ユーザーは2通のWhatsAppメッセージを受け取ることになる。
+- トリガーワードの各文字は設定時に大文字にする必要があります。Braze では、ユーザーが送信するインバウンドトリガーワードを大文字にする必要はありません。例えば、"jOin2023 "とメッセージを送っても、キャンバスやキャンペーンはトリガーされる。
+- エントリスケジュールのアクションベーストリガーにトリガーワードが指定されていない場合、キャンペーンまたはキャンバスはすべてのインバウンドメッセージに対して実行されます。これには、アクティブなキャンペーンやキャンバスでフレーズが一致したメッセージも含まれ、この場合、ユーザーは2通のWhatsAppメッセージを受け取ることになる。
 
 {% tabs %}
 {% tab キャンペーン %}
@@ -42,23 +42,23 @@ alias: /user_guide/message_building_by_channel/whatsapp/quick_replies/
 
 ## 認識されない応答
 
-インタラクティブ・キャンバスでは、認識できない回答に対するオプションを含めることを推奨する。これは、利用可能なプロンプトが何であるかをユーザーに理解させ、チャンネルに対する期待値を設定するものである。ライブエージェントチャット付きのWhatsAppチャンネルがあれば、期待値管理は特に役立つ。 
-- アクションステップで、カスタムフィルターフレーズのアクショングループを作成した後、「WhatsAppメッセージを送信」のための追加のアクショングループを追加しますが、**メッセージ本文を確認しないでください**。これは、"else "節と同様に、認識できないユーザー・レスポンスをすべてキャッチする。 
+インタラクティブ・キャンバスでは、認識できない回答に対するオプションを含めることを推奨する。これは、利用可能なプロンプトが何であるかをユーザーに理解させ、チャネルに対する期待事項を設定するものです。ライブエージェントチャット付きのWhatsAppチャンネルがあれば、期待値管理は特に役立つ。 
+- アクションステップで、カスタムフィルターフレーズのアクショングループを作成した後、「WhatsApp メッセージを送信」のための追加のアクショングループを追加しますが、**メッセージ本文の場所はチェックしないでください**。これは、"else "節と同様に、認識できないユーザー・レスポンスをすべてキャッチする。 
 - WhatsAppのメッセージで、このチャンネルが有人ではないことをユーザーに伝え、必要であればサポートチャンネルを案内することをお勧めする。 
 
-## 迅速な回答 
+## クイック返信 
 
 ![コール・トゥ・アクションのボタンが表示されている電話画面では、クリックされたボタンのテキストが返信される。][11]{: style="float:right;max-width:25%;margin-left:15px;border: 0;"}
 
-クイック返信は、会話内でクリック可能なボタンオプションとして表示されるが、ユーザーがテキストで返信したかのように動作する。そして、Brazeはこれらをインバウンドメッセージとして処理し、クリックされたボタンに基づいたセットレスポンスを送り返すことができる。WhatsAppメッセージ受信アクション "ステップを使用して、ユーザーからの返信を作成し、フィルタリングする。
+クイック返信は、会話内でクリック可能なボタンオプションとして表示されるが、ユーザーがテキストで返信したかのように動作する。そして、Braze はこれらをインバウンドメッセージとして処理し、クリックされたボタンに基づいて設定済みのレスポンスを送り返すことができます。"インバウンド WhatsApp メッセージアクション "ステップを使用して、ユーザーからの返信を作成し、フィルタリングします。
 
 ![WhatsAppメッセージにはテキストと3つの行動喚起ボタンが表示されている。][13]{: style="max-width:50%;"}
 
-### キャンバスでクイックリプライの経験を設定する
+### キャンバスでクイック返信エクスペリエンスを設定する
 
-#### ステップ 1:CTAを構築する
+#### ステップ 1:CTA を構築する
 
-まず、[WhatsAppメッセージテンプレートマネージャーで](https://business.facebook.com/wa/manage/message-templates/)メッセージテンプレート内にクイックリプライCTAを作成する。 
+まず、[WhatsApp メッセージテンプレートマネージャー](https://business.facebook.com/wa/manage/message-templates/)でメッセージテンプレート内にクイック返信 CTA を設定します。 
 
 ![WhatsAppメッセージテンプレートマネージャーのUIでCTAボタンの作成方法、ボタンタイプ(カスタム)、ボタンテキストを確認できる。][12]{: style="max-width:80%;"}
 
@@ -78,21 +78,21 @@ alias: /user_guide/message_building_by_channel/whatsapp/quick_replies/
 
 ![評価アクションが「whatsappの受信メッセージを送信」であるキャンバス。][15]
 
-各クイック返信オプション・グループに対して、マッチさせるボタンとして正確なテキストを指定する。キーワードは大文字でなければならない。 
+各クイック返信オプション・グループに対して、マッチさせるボタンとして正確なテキストを指定する。キーワードは大文字でなければなりません。 
 
 ![キャンバスのステップで、「whatsapp受信メッセージを送信する」というアクションが、特定のメッセージ本文を受信したときに送信されるように設定されている。][16]
 
 クイック返信の代わりにテキストで返信するユーザーに対してデフォルトの返信をしたい場合は、メッセージ本文が一致しないグループを追加で作成する。
 
-この時点から、通常通りにキャンバスを作り続ける。
+この時点から、通常通りにキャンバスの設定を続けます。
 
 ### 回答
 
-各レスポンスに返信メッセージが欲しい場合がほとんどだろう。私たちは、クイック返信の範囲外の回答（たとえば、あらかじめ決められたプロンプトではなく、一般的なメッセージで回答する顧客など）のために、キャッチオールオプションを用意することを推奨する。例えば、「申し訳ありません、あなたの返答に気づきませんでした。サポートに関する問題は、<support channel> 。"
+各レスポンスに返信メッセージが欲しい場合がほとんどだろう。クイック返信の範囲外 (あらかじめ決められたプロンプトではなく、一般的なメッセージで返信する顧客の場合など) の返信には、catch-all オプションを使用することをお勧めします。例えば、「申し訳ありません、あなたの返答に気づきませんでした。サポートに関する問題は、<support channel> というメッセージをお送りください。」
 
 ![それぞれのコールトゥアクションボタンに対する反応を示すキャンバスが構築された。][18]
 
-応答メッセージ、ユーザープロファイルの更新、Braze-to-Brazeウェブフックなど、Braze Canvasが提供する後続のアクションを使用できることに注意すること。 
+レスポンス内のメッセージ、ユーザープロファイルの更新、Braze-to-Braze Webhook など、Braze キャンバスが提供する後続のアクションを使用できることに注意してください。 
 
 [1]: {% image_buster /assets/img/whatsapp/whatsapp24.png %}
 [2]: {% image_buster /assets/img/whatsapp/whatsapp25.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview.md
index 1c32b2e2d55..a1450b31ed0 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview.md
@@ -2,7 +2,7 @@
 nav_title: WhatsAppの設定
 article_title: WhatsAppの設定
 alias: /partners/whatsapp/
-description: "この記事では、Braze WhatsAppチャンネルを設定する方法について、前提条件や次のステップを含めて説明する。"
+description: "この記事では、Braze WhatsApp チャネルを設定する方法について、前提条件や推奨される次のステップを含めて説明します。"
 page_type: partner
 search_tag: Partner
 page_order: 1
@@ -19,99 +19,99 @@ search_rank: 2
 
 統合を進める前に以下を確認する：
 
-- **オプトイン・ポリシー：**WhatsAppは、顧客がメッセージングにオプトインすることを企業に求めている。
-- **WhatsAppのコンテンツルール：**WhatsAppには守るべき[コンテンツルールが](https://www.whatsapp.com/legal/commerce-policy?l=en)いくつかある。
-- **コンプライアンスだ：**適用されるすべてのBrazeおよびMetaの文書と、適用される[Metaのポリシーに](https://www.whatsapp.com/legal/?lang=en)従うこと。
-- **24時間の会話制限：**企業が最初にテンプレート化されたメッセージを送信した後、あるいはユーザーがメッセージを送信した後、両者がメッセージをやり取りできる24時間のウィンドウが発生する。 
-- **会話を始める：**ユーザーはいつでも会話を始めることができる。企業は、承認されたメッセージテンプレートによってのみ会話を開始することができる。
-- **アカウントの制限：**Brazeの各ワークスペースには1つのWhatsApp Businessアカウント、サブスクリプショングループ、電話番号を保存できる。さらに、WhatsApp Businessアカウント1つにつき、[サードパーティとの統合は1つしか](https://developers.facebook.com/docs/whatsapp/embedded-signup/faq#faq_194614375799047)行えない。
+- **オプトインポリシー:** WhatsApp は、顧客がメッセージングにオプトインすることを企業に義務付けています。
+- **WhatsApp のコンテンツルール:** WhatsAppには守るべき[コンテンツルールが](https://www.whatsapp.com/legal/commerce-policy?l=en)いくつかある。
+- **コンプライアンス:** 適用されるすべての Braze および Meta の文書と、適用される [Meta のポリシー](https://www.whatsapp.com/legal/?lang=en)に従います。
+- **24 時間の会話制限:** 企業が最初にテンプレート化されたメッセージを送信した後、あるいはユーザーがメッセージを送信した後、両者がメッセージをやり取りできる24時間のウィンドウが発生する。 
+- **会話を始める:** ユーザーはいつでも会話を始めることができる。企業は、承認されたメッセージテンプレートによってのみ会話を開始することができる。
+- **アカウントの制限:** Brazeの各ワークスペースには1つのWhatsApp Businessアカウント、サブスクリプショングループ、電話番号を保存できる。さらに、WhatsApp Business アカウント 1 つにつき、[サードパーティとの統合は 1 つ](https://developers.facebook.com/docs/whatsapp/embedded-signup/faq#faq_194614375799047)しか行えません。
 <br><br>
 
 | 必要条件| 説明|
 | ---| --- |
-| メタ・ビジネス・マネージャー・アカウント | このメッセージング・チャネルを活用するには、Meta Businessアカウントが必要である。 |
-| WhatsApp ビジネスアカウント | このメッセージングチャネルを利用するにはWhatsApp Businessアカウントが必要である。 |
-| WhatsAppの電話番号 | メッセージングチャンネルを利用するには、WhatsAppの[クラウドAPI](https://developers.facebook.com/docs/whatsapp/cloud-api/phone-numbers)または[オンプレミスAPIの](https://developers.facebook.com/docs/whatsapp/on-premises/phone-numbers)要件を満たす電話番号を取得する必要がある。  | 
+| Facebook Business Manager アカウント | このメッセージングチャネルを活用するには、Meta Business アカウントが必要です。 |
+| WhatsApp ビジネスアカウント | このメッセージングチャネルを利用するには、WhatsApp Business アカウントが必要です。 |
+| WhatsAppの電話番号 | メッセージングチャネルを利用するには、WhatsApp の[クラウド API](https://developers.facebook.com/docs/whatsapp/cloud-api/phone-numbers) または[オンプレミス API ](https://developers.facebook.com/docs/whatsapp/on-premises/phone-numbers)の要件を満たす電話番号を取得する必要があります。  | 
 {: .reset-td-br-1 .reset-td-br-2}
 
 ## 統合
 
-### ステップ 1:WhatsAppメッセンジャーをBrazeに接続する
+### ステップ 1:WhatsApp Messenger を Braze に接続する
 
-Brazeの**Partner Integrations**>**Technology Partnersで** **WhatsAppを**検索する。
+Braze の \[**パートナー連携**] > \[**テクノロジーパートナー**] に移動して、\[**WhatsApp**] を検索します。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**テクノロジー・パートナーが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、\[**テクノロジーパートナー**] は \[**統合**] にあります。
 {% endalert %}
 
-WhatsApp パートナーページで "**Begin Integration "**を選択。
+WhatsApp パートナーページで、\[**統合を開始**] を選択します。
 
 ![][1]
 
-開封ウィンドウで、**次へ**を選択し、**統合開始**ボタンが表示されるまで続けます。ボタンを選択し、統合プロセスを開始する。
+開いたウィンドウで \[**次へ**] を選択し、\[**統合を開始**] ボタンが表示されるまで続けます。ボタンを選択し、統合プロセスを開始します。
 
 ![BrazeとWhatsAppの接続方法。][7]
 
 ### ステップ2:WhatsAppのセットアップ
 
-次に、Brazeセットアップのワークフローが表示される。ステップ・バイ・ステップのチュートリアルについては、[WhatsApp埋め込みサインアップを]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/embedded_signup/)参照のこと。 
+次に、Brazeセットアップのワークフローが表示される。ステップバイステップのウォークスルーについては、[WhatsApp 埋め込みサインアップ]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/embedded_signup/)を参照してください。 
 
-この流れの中で、あなたはこうなる：
-1. MetaとWhatsApp Businessアカウントを作成または選択する。[WhatsApp表示名のガイドラインを](https://www.facebook.com/business/help/757569725593362)必ず確認すること。<br><br>あなたの会社には、すでに少なくとも1つの既存のMeta Businessアカウントがあると思われる。その場合、WhatsApp Businessアカウントを選択する。WhatsAppのユーザー権限とビジネス認証はMeta Businessアカウントで一元管理される。<br><br>
-2. WhatsApp Businessプロフィールを作成する。
-3. WhatsApp Business番号を確認する<br><br>
+このフローでは、次のようになります。
+1. Meta と WhatsApp Business アカウントを作成または選択します。[WhatsApp の表示名のガイドライン](https://www.facebook.com/business/help/757569725593362)を必ず確認してください。<br><br>御社にはすでに少なくとも 1 つの既存の Meta Business アカウントがあると考えられます。その場合は、WhatsApp Business アカウントを配置したいアカウントを選択します。WhatsApp のユーザー権限とビジネス認証は Meta Business アカウントで一元管理されます。<br><br>
+2. WhatsApp Business プロファイルを作成します。
+3. WhatsApp Business 番号を確認します。<br><br>
 
 {% alert note %}
 WhatsAppビジネスアカウント(WABA)は複数のビジネスソリューションプロバイダーと共有することはできない。Brazeのワークスペースごとに特定のWABAが必要になる。
 {% endalert %}	
 
-設定完了後、ユーザー専用のWhatsApp購読グループが作成される。
+設定が完了すると、ユーザー専用の WhatsApp 購読グループが作成されます。
 
 ### ステップ 3:WhatsAppテンプレートを作成する
 
-顧客との会話に使用できるのは、承認されたWhatsAppメッセージテンプレートのみである。WhatsAppテンプレートは[Meta Business Managerで](https://www.facebook.com/business/help/2055875911147364?id=2129163877102343)作成できる。BrazeがサポートするWhatsAppメッセージ機能の一覧は、[サポートされるWhatsApp機能を]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create#supported-whatsapp-features)ご覧下さい。
+承認された WhatsApp メッセージテンプレートのみを使用して、顧客との会話を開始できます。WhatsApp テンプレートは [Meta Business Manager](https://www.facebook.com/business/help/2055875911147364?id=2129163877102343) で作成できます。Braze でサポートされる WhatsApp メッセージ機能の一覧は、[サポートされる WhatsApp 機能]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create#supported-whatsapp-features)を参照してください。
 
-1. **[テンプレート・マネージャーに](https://business.facebook.com/wa/manage/message-templates)移動する**<br>
-Meta Business Managerで、**Account Toolsの**下にある**Message Templatesを**選択する。
-次に、**Create Templatesを**選択する。<br><br>![][3]{: style="max-width:100%;"}<br><br>
-2. **メッセージ設定**<br>
+1. \[**[テンプレートマネージャー](https://business.facebook.com/wa/manage/message-templates)**] に移動します。<br>
+Meta Business Manager で、**Account Tools** の下にある \[**メッセージテンプレート**] を選択します。
+次に、\[**テンプレートを作成**] を選択します。<br><br>![][3]{: style="max-width:100%;"}<br><br>
+2. **メッセージの設定**<br>
 新しいメッセージ・テンプレート・コンポーザーで、メッセージのカテゴリーを選択し、テンプレートに名前を付け、サポートしたい言語を選択する。後で言語を削除したり追加したりすることもできる。<br><br> 
 	利用可能なメッセージテンプレートのカテゴリーには以下のものがある：
-	- マーケティングだ：キャンペーンや製品情報などを配信し、認知度とエンゲージメントを高める
-	- ユーティリティだ：アカウント更新、注文更新、アラートなどを送信し、重要な情報を共有する
-	- 認証を行う：顧客がアカウントにアクセスできるコードを送信する<br><br> 
+	- マーケティング: キャンペーンや製品情報などを配信し、認知度とエンゲージメントを高める
+	- ユーティリティ: アカウント更新、注文更新、アラートなどを送信し、重要な情報を共有する
+	- 認証: 顧客がアカウントにアクセスできるようにするコードを送信する<br><br> 
 	![][4]{: style="max-width:100%;"}<br><br>
 3. **テンプレートを編集する**<br>
-次に、メッセージ・テンプレートを作成するよう促される。<br><br>ここでは、テキストまたはメディアヘッダー、本文、メッセージフッター、ボタンを提供することができる。また、ヘッダーはテキストか画像タイプでなければならない。メッセージのプレビューが右側に表示される。<br><br>MetaはLiquidをサポートしていないが、BrazeでLiquidの変数に置き換えることができる変数をテンプレートすることができる。**変数の追加**ボタンを選択する。<br><br>![][5]{: style="max-width:100%;"}<br><br>テンプレートが完成したら、**Submitを**押す。 
+次に、メッセージ・テンプレートを作成するよう促される。<br><br>ここでは、テキストまたはメディアヘッダー、テキスト本文、メッセージフッター、およびボタンを指定できます。現在、ビデオとドキュメントのヘッダーは使用できず、ヘッダーはテキストまたは画像のいずれかでなければなりません。メッセージのプレビューが右側に表示される。<br><br>Meta は Liquid をサポートしていませんが、後で Braze で Liquid 変数に置き換えることができる変数をテンプレート化することができます。\[**\+ 変数を追加**] ボタンを選択します。<br><br>![][5]{: style="max-width:100%;"}<br><br>テンプレートが完成したら、\[**送信**] をクリックします。 
 
 #### テンプレート承認時間
 
-メッセージテンプレートの承認状況は、Meta Business Managerの**メッセージテンプレートページ**、またはBrazeでキャンペーンやキャンバスを作成する際に確認できる。さらに、通知権限に応じてWhatsAppチームからメールで通知されることもある。 
+メッセージテンプレートの承認状況は、Meta Business Manager の**メッセージテンプレートページ**、または Braze でキャンペーンやキャンバスを作成する際に確認できます。さらに、通知権限に応じてWhatsAppチームからメールで通知されることもある。 
 
 {% alert note %}
-承認されたテンプレートは、好きなだけキャンペーンやキャンバスに使用できる。また、好きなだけ多くのオプトイン・ユーザーに送ることができる。テンプレートの品質が低下しない限り、これは事実である。
+承認されたテンプレートは、好きなだけキャンペーンやキャンバスに使用できる。また、好きなだけ多くのオプトインユーザーに送ることができます。テンプレートの品質が低下しない限り、これは事実である。
 {% endalert %}
 
 ### ステップ 4:WhatsAppキャンペーンを作成する
 
-WhatsAppテンプレートが承認されたら、ダッシュボードに移動して[WhatsAppキャンバスやキャンペーンを]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create/)作成できる。 
+WhatsApp テンプレートが承認されたら、ダッシュボードに移動して [WhatsApp キャンバスやキャンペーン]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create/)を作成できます。 
 
 {% alert note %}
-WhatsApp ビジネスアカウント作成後、Meta がメッセージ送信の上限を決定する。詳しくは[スループットを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/10dlc/#throughput)ご覧いただきたい。
+WhatsApp Business Account が作成されると、Meta によって初期のメッセージ制限が決定されます。詳しくは[スループットを]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/10dlc/#throughput)ご覧いただきたい。
 {% endalert %}
 
 ## 次のステップ
 
-統合が完了したら、次の2つのMetaプロセスを完了させることをお勧めする：
+統合が完了したら、次の 2 つの Meta プロセスを完了させることをお勧めします。
 - [ビジネス検証](https://www.facebook.com/business/help/2058515294227817?id=180505742745347)
-	- 既存のメタ・ビジネス・マネージャーを使用している場合は、すでにビジネス認証を受けているかもしれない。 
+	- 既存の Meta Business Manager を使用している場合は、すでにビジネス検証を行っている可能性があります。 
 - [公式ビジネスアカウント](https://www.facebook.com/business/help/604726921052590?ref=search_new_0)
 
-また、[ユーザーの電話番号]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/user_phone_numbers/)について読むことをお勧めします。組織でメッセージ[テンプレートを作成する必要があるユーザーを追加してください](https://www.facebook.com/business/help/2169003770027706?id=2190812977867143)。
+[ユーザーの電話番号]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/user_phone_numbers/)について読み、メッセージ[テンプレートを組織で作成](https://www.facebook.com/business/help/2169003770027706?id=2190812977867143)する必要があるユーザーを追加することをお勧めします。
 
 ### WhatsApp Cloud API ローカルストレージ
 
-BrazeはWhatsAppの[クラウドAPIローカルストレージを](https://developers.facebook.com/docs/whatsapp/cloud-api/overview/local-storage?content_id=ka6F9gESPqhQpm5)サポートしている。これを有効にするには、Brazeカスタマーサポートマネージャーに連絡すること。
+Braze は WhatsApp の [Cloud API ローカルストレージ](https://developers.facebook.com/docs/whatsapp/cloud-api/overview/local-storage?content_id=ka6F9gESPqhQpm5)をサポートしています。これを有効にするには、Brazeカスタマーサポートマネージャーに連絡すること。
 
 [1]: {% image_buster /assets/img/whatsapp/whatsapp1.png %}
 [2]: {% image_buster /assets/img/whatsapp/whatsapp10.png %}
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups.md
index 4cbf767f011..b159b7c2e27 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups.md
@@ -14,41 +14,41 @@ channel:
 
 ## 複数のWhatsAppビジネスアカウント 
 
-複数のブランドが存在するBrazeワークスペースのユーザーにWhatsAppメッセージを送信する場合、複数のWhatsApp Businessアカウントを持つことが有効である。各ビジネスアカウントはWhatsApp内で個別に運営され、独自の電話番号、メッセージテンプレート、品質評価を持っているからだ。
+複数のブランドを持つ Braze ワークスペースのユーザーに WhatsApp メッセージを送信する場合、複数の WhatsApp Business アカウントを使用すると便利です。各ビジネスアカウントはWhatsApp内で個別に運営され、独自の電話番号、メッセージテンプレート、品質評価を持っているからだ。
 
-同じMeta Business Manager内にネストされたビジネスアカウントは、ユーザーアクセス権限管理とカタログも共有する（Brazeではまだサポートされていない）。
+同じ Meta Business Manager 内にネストされているビジネスアカウントは、ユーザーアクセス権限管理とカタログも共有します (Brazeではまだサポートされていません)。
 
 ### WhatsApp Businessアカウントを追加する
 
-1ワークスペースにつきWhatsApp Businessアカウントを10個まで追加できる。アカウントを追加する：
+1 つのワークスペースにつき WhatsApp Business アカウントを 10 個まで追加できます。アカウントを追加する：
 
-1. **テクノロジーパートナー**>**WhatsAppの**順に選択し、**WhatsAppビジネスアカウントを追加する**。![WhatsAppメッセージングインテグレーションセクションでは、ビジネスアカウントの追加、購読グループと番号の追加ができる。][1]<br>
-2. サインアップのワークフローに従う。ステップバイステップの詳しい説明は、[WhatsApp埋め込みサインアップを]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/embedded_signup/)参照のこと。
+1. \[**テクノロジーパートナー**] > \[**WhatsApp**] に移動して \[**WhatsApp ビジネスアカウントを追加**] を選択します。![WhatsAppメッセージングインテグレーションセクションでは、ビジネスアカウントの追加、購読グループと番号の追加ができる。][1]<br>
+2. サインアップのワークフローを実行します。ステップごとの詳しいガイドは、[WhatsApp 埋め込みサインアップ]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/embedded_signup/)を参照してください。
 
 {% alert important %}
 他のWhatsAppアカウントに登録されていないなど、WhatsApp電話番号に必要な条件を全て満たしていること。
 {% endalert %}
 
-## 複数の契約グループと電話番号
+## 複数のサブスクリプショングループと電話番号
 
-メッセージテンプレートはWhatsApp Businessアカウント内の全ての電話番号で共有される。WhatsAppサブスクリプショングループの詳細は[サブスクリプショングループを]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/user_subscription/)ご覧下さい。
+メッセージテンプレートは同じ WhatsApp Business アカウント内のすべての電話番号で共有されます。WhatsAppサブスクリプショングループの詳細は[サブスクリプショングループを]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/user_subscription/)ご覧下さい。
 
 WhatsAppの各電話番号は、ユーザーには個別のWhatsAppチャットとして表示される。WhatsApp Businessアカウント内の電話番号はそれぞれ独立しているため、以下のように同じ値を設定することも、異なる値を設定することもできる： 
 - 表示名 
 - ステータス 
 - 品質評価 
-- メッセージ送信制限 
+- メッセージング制限 
 
-### 購読グループと電話番号を追加する
+### サブスクリプショングループと電話番号の追加
 
-WhatsApp Businessアカウント1つにつき、最大20のサブスクリプショングループ(および送信電話番号)を追加できる。購読グループと電話番号を追加するには
+WhatsApp Business アカウント 1 つにつき、最大 20 のサブスクリプショングループ (および送信電話番号) を追加できます。サブスクリプショングループと電話番号を追加するには:
 
-1. **テクノロジーパートナー** > **WhatsApp** に移動し、**サブスクリプショングループと番号を追加** を選択します。![WhatsApp メッセージング統合セクションには、ビジネスアカウントを追加するか、サブスクリプショングループと番号を追加するオプションがあります。][1]<br>
-2. サインアップのワークフローに従う。<br><br> **WhatsApp Businessアカウントを選択**"ステップで既存のWhatsApp Businessアカウントを選択し、新しい電話番号を追加する。この電話番号は、他のWhatsAppアカウントに登録されていないなど、WhatsApp電話番号の全ての条件を満たしている必要がある。
+1. \[**テクノロジーパートナー**] > \[**WhatsApp**] に移動し、\[**サブスクリプショングループと番号を追加**] を選択します。![ビジネスアカウントを追加するか、サブスクリプショングループと番号を追加するオプションが表示された WhatsApp メッセージング統合セクション。][1]<br>
+2. サインアップのワークフローを実行します。<br><br> **WhatsApp Businessアカウントを選択**"ステップで既存のWhatsApp Businessアカウントを選択し、新しい電話番号を追加する。この電話番号は、他のWhatsAppアカウントに登録されていないなど、WhatsApp電話番号の全ての条件を満たしている必要がある。
 
-### 購読グループと電話番号を削除する 
+### サブスクリプショングループと電話番号の削除 
 
-1. **Audience**>**Subscriptionsに**移動し、購読グループをアーカイブする。
-2. メタビジネスマネージャーに行き、電話番号を削除する。
+1. \[**オーディエンス**] > \[**サブスクリプション**] に移動し、サブスクリプショングループをアーカイブします。
+2. Meta Business Manager に移動して電話番号を削除します。
 
 [1]: {% image_buster /assets/img/whatsapp/multiple_wabas.png %} 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/phone_number_acquisition.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/phone_number_acquisition.md
index f896475064b..46da9bc4a7c 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/phone_number_acquisition.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/phone_number_acquisition.md
@@ -2,7 +2,7 @@
 nav_title: 電話番号取得
 article_title: 電話番号取得
 page_order: 3
-description: "この記事では、TwilioとInfobipから電話番号を取得する方法について説明します。"
+description: "この記事では、Twilio と Infobip から電話番号を取得する方法について説明します。"
 page_type: reference
 channel:
   - WhatsApp
@@ -10,15 +10,15 @@ channel:
 
 # 電話番号の取得
 
-> WhatsAppメッセージングチャネルを使用するには、[Cloud API](https://developers.facebook.com/docs/whatsapp/cloud-api/phone-numbers)または[On-Premises API](https://developers.facebook.com/docs/whatsapp/on-premises/phone-numbers)の要件を満たす電話番号が必要です。
+> WhatsApp メッセージングチャネルを使用するには、[Cloud API](https://developers.facebook.com/docs/whatsapp/cloud-api/phone-numbers) または [On-Premises API](https://developers.facebook.com/docs/whatsapp/on-premises/phone-numbers) の要件を満たす電話番号が必要です。
 
-電話番号は自分で取得する必要があります。Brazeは番号を提供しません。ビジネス電話プロバイダーを通じて物理的な電話をSIMカード付きで購入するか、当社のパートナーの1つを使用することができます。トゥイリオまたはインフォブリップ。**TwilioまたはInfobipのアカウントを持っている必要があります。これはBrazeを通じて行うことはできません。**
+電話番号は自分で取得する必要があります。Brazeは番号を提供しません。ビジネス電話プロバイダーを通じて物理的な電話をSIMカード付きで購入するか、当社のパートナーの1つを使用することができます。Twilio または Infoblip。**Twilio または Infobip のアカウントを持っていなければなりません。これは Braze を通じて行うことはできません。**
 
 ## WhatsApp API 要件
 
 お使いの電話番号は、これらのWhatsApp API要件を満たしている必要があります:
 
-- あなたのビジネスが所有 
+- お客様のビジネスが所有する番号である 
 - 国番号と市外局番を持っている（例えば、固定電話と携帯電話番号）
 - 音声通話やSMSを受信可能
 - アカウント設定中にアクセス可能（認証コードを受け取るため）
@@ -28,25 +28,25 @@ channel:
 
 ## Twilioの電話番号を取得する
 
-### ステップ 1:TwilioコンソールまたはAPIから電話番号を購入する
+### ステップ 1: TwilioコンソールまたはAPIから電話番号を購入する
 
 1. Twilioコンソールから、**開発** > **電話番号** > **管理** > **番号を購入** に移動します。このオプションが表示されない場合は、**製品を探す**を選択し、**スーパー ネットワーク**までスクロールして、**電話番号** > **番号を購入**を選択します。<br><br>![「開発」タブが開かれ、「番号を購入」オプションが表示されているTwilioコンソール。][1]{: style="max-width:20%;"}<br><br>
 
-2. ご希望の市外局番または地域（お持ちの場合）を入力してください。数字を見つけて、**購入**を選択します。<br><br> ![記載された電話番号を購入するためのボタン。][2]<br><br>
+2. 目的の市外局番または地域 （該当する場合） を入力します。数字を見つけて、**購入**を選択します。<br><br> ![記載の電話番号を購入するボタン。][2]<br><br>
 
-3. 電話番号を購入した後、**Active Numbers**に移動して、購入したばかりの電話番号を選択します。<br><br>![「アクティブ番号」は購入した電話番号を表示します。][3]{: style="max-width:70%;"}<br><br>
+3. 電話番号を購入した後、**Active Numbers**に移動して、購入したばかりの電話番号を選択します。<br><br>![購入した電話番号を示す「アクティブ番号」。][3]{: style="max-width:70%;"}<br><br>
 
-### ステップ2:電話番号を設定する
+### ステップ 2: 電話番号を設定する
 
-Twilio の指示に従って、[ボイスメールの文字起こしを使用して、確認コードをメールで受信するために Twilio の電話番号を設定します](https://www.twilio.com/docs/whatsapp/self-sign-up#setting-up-your-twilio-phone-number-to-receive-the-verification-code-via-email-using-voicemail-transcription)。**他のステップの指示に従わないでください。それはあなたの電話番号をTwilioに接続し、Brazeには接続しません。**
+Twilio の指示に従って、[ボイスメールの文字起こしを使用して、確認コードをメールで受信するための Twilio の電話番号を設定](https://www.twilio.com/docs/whatsapp/self-sign-up#setting-up-your-twilio-phone-number-to-receive-the-verification-code-via-email-using-voicemail-transcription)します。**それ以外のステップの指示には従わないでください。この電話番号は Braze ではなく Twilio に接続する必要があります。**
 
 {% alert warning %}
 **Twilioの指示に従って確認コードを受け取ってください。**
 
-次の手順に従うと、Twilioの指示に従って、電話番号をTwilioに接続できます。つまり、移行を行うか、別の番号を購入しない限り、その番号をBrazeに接続することはできません。
+Twilio の指示にある以下の手順に従うと、電話番号を Twilio に接続できます。つまり、移行を行うか、別の番号を購入しない限り、その番号をBrazeに接続することはできません。
 {% endalert %}
 
-### ステップ 3:埋め込みサインアップワークフローを完了する
+### ステップ 3: 埋め込みサインアップワークフローを完了する
 
 1. Twilioの設定が完了したら、Brazeのダッシュボード > **Technology Partners** > **WhatsApp** に移動し、**Begin integration** または **Add WhatsApp Business Account** のいずれかが表示された方を選択して、[embedded sign up workflow]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/embedded_signup/) をトリガーします。<br><br>「**WhatsAppの電話番号を追加する**」ステップで、電話番号の確認方法として「**電話**」を選択します。<br><br>![テキストメッセージまたは電話で電話番号を確認するオプションがあるセクション。][4]{: style="max-width:50%;"}<br><br>
 
@@ -54,7 +54,7 @@ Twilio の指示に従って、[ボイスメールの文字起こしを使用し
 
 ## Infobipの電話番号を取得する 
 
-1. Infobipコンソールで、**チャネルと番号**に移動し、**番号**を選択します。<br><br>![インフォブリップ「チャンネルと番号」セクションに「番号」が記載されています。][5]{: style="max-width:30%;"}<br><br>
+1. Infobipコンソールで、**チャネルと番号**に移動し、**番号**を選択します。<br><br>![Infoblip の「Channels and Numbers」セクションに表示された「Numbers」。][5]{: style="max-width:30%;"}<br><br>
 
 2. **購入番号**を選択 > メッセージを送信したい国を選択 > **SMS**。<br><br>![番号を購入するボタン。][6]<br><br>
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration.md
index 68b597964d0..87d529a47bd 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration.md
@@ -2,7 +2,7 @@
 nav_title: WhatsApp電話番号の移行
 article_title: WhatsApp電話番号の移行
 page_order: 2
-description: "この記事では、WhatsAppの電話番号を移行する方法について説明します。"
+description: "この記事では、WhatsApp の電話番号を移行する方法について説明します。"
 page_type: reference
 channel:
   - WhatsApp
@@ -10,16 +10,16 @@ channel:
 
 # WhatsApp電話番号の移行
 
-> Metaの埋め込みサインアップを使用して、WhatsApp Businessアカウント間でWhatsAppの電話番号を移行します。
+> Meta の埋め込みサインアップを使用して、WhatsApp Business アカウント間で WhatsApp の電話番号を移行します。
 
 ## 前提条件
 
-お客様の電話番号は、移行の対象となるためにMetaの要件を満たしている必要があります。
+移行の対象となるには、電話番号が Meta の要件を満たしている必要があります。
 
 - あなたのMetaビジネスアカウントは確認されました。
 - お客様の既存のWhatsAppビジネスアカウントが承認されました。
 - お客様の既存のWhatsAppビジネスアカウントには、**支払い設定**に有効な支払い方法があります。
-- あなたのビジネス電話番号は二段階認証がオフになっています。WhatsApp ビジネスアカウントを所有している場合、WhatsApp マネージャーで番号の二段階認証をオフにすることができます。それ以外の場合は、ソリューションプロバイダーに依頼してオフにしてもらう必要があります。
+- あなたのビジネス電話番号は二段階認証がオフになっています。WhatsApp Business アカウントを所有している場合、WhatsApp Manager で番号の二段階認証をオフにすることができます。そうでない場合、ソリューションプロバイダーに依頼してオフにしてもらう必要があります。
 
 WhatsAppの電話番号の移行に関する情報については、Metaの[埋め込みサインアップを介したWhatsAppビジネスアカウント間の電話番号の移行](https://developers.facebook.com/docs/whatsapp/business-management-api/guides/migrate-phone-to-different-waba/)に関するドキュメントを参照してください。
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/user_phone_numbers.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/user_phone_numbers.md
index 41181280631..729a5e189b3 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/user_phone_numbers.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/user_phone_numbers.md
@@ -1,8 +1,8 @@
 ---
 nav_title: "ユーザーの電話番号"
-article_title: WhatsAppの電話番号
+article_title: WhatsApp ユーザーの電話番号
 page_order: 1.5
-description: "このリファレンス記事では、WhatsAppの電話番号の書式設定、電話番号のインポート方法、およびWhatsApp サブスクリプショングループs にユーザーs を追加する方法について説明します。"
+description: "この記事では、WhatsApp 電話番号のフォーマット、電話番号のインポート方法、および WhatsApp サブスクリプショングループにユーザーを追加する方法について説明します。"
 page_type: reference
 channel: 
   - WhatsApp
@@ -11,43 +11,43 @@ channel:
 
 # ユーザーの電話番号
 
-> ここでは、ユーザーや顧客の電話番号について説明します。
+> この記事では、ユーザーや顧客の電話番号に関するさまざまなトピックについて説明します。
 
 電話番号はローカル形式でユーザープロファイルに表示されますが、番号の読み込みに使用する形式では表示されません(`(724) 123 4567`)。
 
-## 電話番号をインポートする
+## 電話番号のインポート
 
-CSV または [ を使用して [ アップロードすることで、API]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv) を使用して電話番号を読み込んでユーザーを作成できます。
+[CSV]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv) または [API]({{site.baseurl}}/api/endpoints/user_data/#user-track-endpoint) 経由でアップロードしてユーザーを作成する方法で、電話番号をインポートできます。
 
 ### フォーマット
 
 [`E.164`](https://en.wikipedia.org/wiki/e.164) 形式のU.S以外の数値を、"+" とカントリーコードを含めて読み込むことが大切です。この形式で指定されていない電話番号は、US 番号として解釈されます。  
 
-電話番号が強制的にE.164形式に変換され、検証に合格しない場合、Brazeはこの番号にWhatsAppを送信できません。フォーマットテーブルではない電話番号のユーザーは、WhatsAppを含むキャンバスステップから自動的に終了します
+電話番号が強制的にE.164形式に変換され、検証に合格しない場合、Brazeはこの番号にWhatsAppを送信できません。フォーマット可能でない電話番号を持つユーザーは、WhatsApp を含むキャンバスステップを自動的に終了します。
 
 すべてのU.S. 番号は有効で、有効な市外コードのある10 桁の電話番号である必要があります。`+` とカントリーコードを指定せずに入力できます。Braze はすべての有効な10 桁の電話番号をU.S. 番号としてマッピングします。
 
 すべての国際番号は、`+` で始まり、その後に国別コードと電話番号が続きます(e.g `+442071838750`)。
 
-![]\[ピクチャ]]{: style="max-width:50%;border: 0;"}
+![]\[picture]{: style="max-width:50%;border: 0;"}
 
-ただし、国または地域コードs の異なる複数の地域に送信する場合は、`E.164` 形式を使用することをお勧めします。これは、U.S.ベースの電話番号でも同様です。
+ただし、国コードや市外局番が異なる複数の地域に送信する場合は、`E.164` 形式を使用することをお勧めします。これは米国ベースの電話番号でも同様です。
 
 次の表では、ローカル数値フォーマットとユニバーサル、`E.164` フォーマットの違いを確認できます。
 
-| 国 | ローカル | 国番号 | `E.164` |
+| 国 | ローカル | 国コード | `E.164` |
 |---|---|---|---|
-| USA | `4155552671` | 1 | `+14155552671` |
+| アメリカ合衆国 | `4155552671` | 1 | `+14155552671` |
 | 英国 | `2071838750` | 44 | `+442071838750` |
 | ブラジル | `1155256325` | 55 | `+551155256325` |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 reset-td-br-4}
 
 ### サブスクリプショングループをWhatsAppするためのユーザーの追加
 
-顧客がWhatsAppを受信するには、有効な電話番号を持っていて、サブスクリプショングループにオプトインする必要があります。詳細については、[WhatsApp サブスクリプショングループ s]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/user_subscription/)を参照してください。
+顧客が WhatsApp メッセージを受信するには、有効な電話番号を持っていて、サブスクリプショングループにオプトインしている必要があります。詳細については、[WhatsApp サブスクリプショングループ]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/user_subscription/)を参照してください。
 
 
-### 同じ電話番号のマルチユーザーs
+### 同じ電話番号を持つ複数のユーザー
 
 複数のユーザーが1 つのキャンペーンまたはキャンバスステップのSegment内で同じ電話番号を持つ場合、Braze は送信を重複排除し、その1 つの電話番号に1 つのメッセージのみを送信します。 
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create.md
index 9efe1cc2676..f8f43efdeb3 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create.md
@@ -2,7 +2,7 @@
 nav_title: WhatsAppメッセージを作成する
 article_title: WhatsAppメッセージを作成する
 page_order: 4
-description: "この参考記事では、WhatsAppメッセージの作成手順を説明する。"
+description: "この記事では、WhatsApp メッセージの構築と作成に関連するステップについて説明します。"
 page_type: reference
 tool:
   - Campaigns
@@ -13,16 +13,16 @@ search_rank: 1
 
 # WhatsAppメッセージを作成する
 
-> WhatsAppキャンペーンは、顧客に直接アプローチし、プログラム上で会話するのに適している。Liquid などのダイナミックコンテンツを使用して、ユーザー一人ひとりに合わせた体験を作り出し、控えめなブランド体験を強化する環境を作ることができます。 
+> WhatsApp キャンペーンは、顧客に直接リーチしてプログラムを使って会話を行うのに適しています。Liquid などのダイナミックコンテンツを使用して、ユーザー一人ひとりに合わせた体験を作り出し、控えめなブランド体験を強化する環境を作ることができます。 
 
 ## 前提条件
 
-WhatsAppメッセージを作成し、WhatsAppチャンネルを活用するには、まずWhatsAppの[概要に]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/)目を通し、以下のことを行う必要がある：
+WhatsApp メッセージを作成して WhatsApp チャネルを活用するには、まず WhatsApp の[概要]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/)を読み、以下のことを行う必要があります。
   - ポリシー、制限、コンテンツのルールを認識する
   - WhatsApp接続を設定する
   - メッセージに使用する初期テンプレートをMetaで作成する
 
-## ステップ 1:メッセージを作成する場所を選択する
+## ステップ 1: メッセージを作成する場所を選択する
 
 {% alert note %}
 WhatsAppは言語ごとに異なる[メッセージテンプレートを](#template-messages)作成する。ユーザーに適切なテンプレートを提供するために、セグメンテーションを使って言語ごとにキャンペーンを作成するか、キャンバスを使う。
@@ -35,8 +35,8 @@ WhatsAppは言語ごとに異なる[メッセージテンプレートを](#templ
 
 **ステップ:**
 
-1. **Campaigns**ページに行き、<i class="fas fa-plus"></i> **Create Campaignを**クリックする。
-2. **WhatsAppを**選択するか、複数のチャンネルを対象とするキャンペーンの場合は**マルチチャンネルキャンペーンを**選択する。
+1. \[**キャンペーン**] ページに移動して、<i class="fas fa-plus"></i> \[**キャンペーンを作成**] をクリックします。
+2. \[**WhatsApp**] を選択するか、複数のチャネルをターゲットとするキャンペーンの場合は \[**マルチチャンネルキャンペーン**] を選択します。
 3. キャンペーンに、明確で意味のある名前を付けます。
 4. 必要に応じて、\[[チーム]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/teams/)] と \[[タグ]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/tags/)] を追加します。
    * タグを使用すると、キャンペーンを検索してレポートを作成しやすくなります。例えば、\[[レポートビルダー]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/)] を使用する場合、特定のタグでフィルターできます。
@@ -56,37 +56,37 @@ WhatsAppは言語ごとに異なる[メッセージテンプレートを](#templ
 3. \[[ステップスケジュール]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/time_based_canvas/#schedule-delay)] を選択し、必要に応じて遅延を指定します。
 4. 必要に応じて、このステップのオーディエンスをフィルターします。セグメントを指定し、フィルターを追加して、このステップの受信者をさらに絞り込むことができます。後から、メッセージの送信時に、オーディエンスオプションがチェックされます。
 5. \[[昇進動作]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/advancement/)] を選択します。
-6. メッセージと組み合わせたい他のメッセージング・チャンネルを選択する。
+6. このメッセージと組み合わせる他のメッセージングチャネルを選択します。
 
 {% endtab %}
 {% endtabs %}
 
-## ステップ 2:WhatsAppメッセージを作成する
+## ステップ 2: WhatsAppメッセージを作成する
 
-WhatsApp[テンプレートメッセージを](#template-messages)作成するか、レスポンスメッセージを作成するか、用途に応じて選択する。ビジネス主導の会話は承認されたテンプレートから始めなければならないが、応答メッセージは24時間以内のユーザーからのインバウンドメッセージへの応答で使用できる。
+ユースケースに応じて WhatsApp [テンプレートメッセージ](#template-messages)を作成するか、応答メッセージを作成します。ビジネス主導の会話は承認されたテンプレートから始めなければならないが、応答メッセージは24時間以内のユーザーからのインバウンドメッセージへの応答で使用できる。
 
 {% alert note %}
 現在、WhatsAppテンプレートはクーポンコードボタンをサポートしていない。
 {% endalert %}
 
-![Message Variantsセクションでは、サブスクリプション・グループと2つのメッセージ・タイプから1つを選択できる：WhatsApp テンプレートメッセージとレスポンスメッセージ。][5]{: style="max-width:80%;"}
+![「メッセージバリアント」セクションでは、サブスクリプショングループを 1 つと、2 つのメッセージタイプのいずれかを選択できます。WhatsApp テンプレートメッセージとレスポンスメッセージ。][5]{: style="max-width:80%;"}
 
 ### テンプレートメッセージ
 
-[承認されたWhatsAppテンプレートメッセージを使って]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/#step-3-create-whatsapp-templates
-)WhatsAppユーザーと会話を始めることができる。これらのメッセージは事前にWhatsAppに提出され、内容の承認を受けるが、承認には最大24時間かかる。コピーを編集した場合は、WhatsAppに再送信する必要がある。
+[承認済みの WhatsApp テンプレートメッセージ]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/#step-3-create-whatsapp-templates
+)を使って WhatsApp ユーザーと会話を始めることができます。これらのメッセージは事前に WhatsApp に提出され、コンテンツの承認を受けますが、承認には最大 24 時間かかります。コピーを編集した場合は、WhatsApp に再送信する必要があります。
 
 無効なテキストフィールド(灰色でハイライト)は、承認されたWhatsAppテンプレートの一部であるため、編集することはできない。無効化されたテキストを更新するには、テンプレートを編集し、再承認を得る必要がある。
 
 #### 言語
 
-各テンプレートには言語が割り当てられているため、ユーザーマッチングを正しく設定するには、言語ごとにキャンペーンまたはキャンバスのステップを作成する必要がある。例えば、インドネシア語と英語が割り当てられたテンプレートを使用するキャンバスを構築する場合、インドネシア語テンプレート用のキャンバス・ステップと英語テンプレート用のキャンバス・ステップを作成する必要がある。
+各テンプレートには言語が割り当てられているため、ユーザーマッチングを正しく設定するには、言語ごとにキャンペーンまたはキャンバスのステップを作成する必要がある。例えば、インドネシア語と英語が割り当てられたテンプレートを使用するキャンバスを作成する場合、インドネシア語テンプレート用のキャンバスステップと英語テンプレート用のキャンバスステップを作成する必要があります。
 
 ![メッセージのプレビュー、割り当てられた言語、承認されたステータスを含むテンプレートのリスト。][8]{: style="max-width:80%;"}
 
 #### 変数
 
-Meta Business Manager で WhatsApp テンプレートを作成する際に変数を追加した場合、その変数はメッセージ作成時に空白として表示される。これらの空白をリキッドまたはプレーンテキストに置き換える。プレーン・テキストを使うには、二重中括弧で囲まれた "text here "という書式を使う。テンプレート作成時に画像を含めることを選択した場合は、メディアライブラリから画像をアップロードするか追加する。
+Meta Business Manager で WhatsApp テンプレートを作成する際に変数を追加した場合、それらはメッセージ作成画面に空白として表示されます。これらの空白をリキッドまたはプレーンテキストに置き換える。プレーン・テキストを使うには、二重中括弧で囲まれた "text here "という書式を使う。テンプレート作成時に画像を含めることを選択した場合は、メディアライブラリから画像をアップロードするか追加する。
 
 無効化されたテキストフィールド(灰色でハイライト)は、承認されたWhatsAppテンプレートの一部であるため、編集することはできない。無効化されたテキストを更新したい場合は、テンプレートを編集し、再承認を得る必要がある。
 
@@ -96,71 +96,71 @@ Liquidを使用する場合は、受信者のユーザープロファイルが
 {% endraw %}
 {% endalert %}
 
-![パーソナライズの追加ツールで、属性 "first_name "とデフォルト値 "you "を指定する。][2]{: style="max-width:80%;"}
+![属性 "first_name" とデフォルト値 "you" を使用したパーソナライゼーション追加ツール。][2]{: style="max-width:80%;"}
 
 ### ダイナミック・リンク 
 
-コールトゥアクションのURLは変数を含むことができるが、Metaは`{% raw %}https://example.com/{{variable}}{% endraw %}` のようにURLの末尾に置くことを要求している。リンクはテンプレートの一部として本文に含めることもできる。現時点では、どちらのリンクも短縮することはできない。 
+コールトゥアクション URL は、Meta では `{% raw %}https://example.com/{{variable}}{% endraw %}` のように URL の末尾になければなりませんが、URL に変数を含めることができます。この変数は Braze で Liquid に置き換えることができます。リンクはテンプレートの一部として本文に含めることもできる。現時点では、どちらのリンクも短縮することはできない。 
 
 ### 応答メッセージ
 
 {% alert note %}
-レスポンス・メッセージは現在、早期アクセス中である。早期アクセスへの参加に興味がある方は、Brazeのアカウントマネージャーに連絡を。
+応答メッセージは現在、早期アクセス段階です。早期アクセスへの参加に興味がある方は、Brazeのアカウントマネージャーに連絡を。
 {% endalert %}
 
-ユーザーからのインバウンドメッセージに返信するために、レスポンスメッセージを使うことができる。これらのメッセージは、作曲体験中にBrazeのアプリ内に組み込まれ、いつでも編集することができる。リキッドを使えば、応答メッセージの言語を適切なユーザーに合わせることができる。
+ユーザーからのインバウンドメッセージに返信するために、応答メッセージを使うことができます。これらのメッセージは、作成中に Braze のアプリ内で作成され、いつでも編集できます。Liquid を使えば、応答メッセージの言語を適切なユーザーに合わせることができます。
 
 使用できるレスポンス・メッセージのレイアウトは3種類ある：
-- クイック・リプライ
+- クイック返信
 - テキストメッセージ
 - メディア・メッセージ
 
 ![新規ユーザーを割引コードで歓迎する返信メッセージの作成者。][6]{: style="max-width:80%;"}
 
-## ステップ 3:メッセージをプレビューしてテストする
+## ステップ 3: メッセージをプレビューしてテストする
 
-Brazeでは、メッセージを送信する前にプレビューしてテストすることを常に推奨している。**テスト]**タブに切り替えると、テスト用のWhatsAppメッセージを[コンテンツテストグループや]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#content-test-groups)個々のユーザーに送信したり、Brazeで直接ユーザーとしてメッセージをプレビューすることができる。
+Brazeでは、メッセージを送信する前にプレビューしてテストすることを常に推奨している。\[**テスト**] タブに切り替えて、[コンテンツテストグループ]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#content-test-groups)または個々のユーザーにテスト用の WhatsApp メッセージを送信するか、ユーザーとしてメッセージを Braze で直接プレビューします。
 
-![スザンヌという名前の既存ユーザーのプレビュー・メッセージ。][3]{: style="max-width:80%;"}
+![Suzanne という名前の既存ユーザー用のプレビューメッセージ。][3]{: style="max-width:80%;"}
 
 {% alert note %}
-テスト・メッセージを含む応答メッセージを送信するには、会話ウィンドウが必要である。会話ウィンドウを開くには、このメッセージに使用する購読グループに関連付けられている電話番号にWhatsAppメッセージを送信する。関連する電話番号は、**Test**タブのアラートに表示される。
+テストメッセージを含む応答メッセージを送信するには、会話ウィンドウが必要です。会話ウィンドウを開くには、このメッセージに使用する購読グループに関連付けられている電話番号にWhatsAppメッセージを送信する。関連する電話番号は、**Test**タブのアラートに表示される。
 {% endalert %}
 
-![テストするには、まずWhatsAppメッセージを+1 631-202-0907に送信して会話ウィンドウを開いてください」というアラート。その後、テストユーザーに応答メッセージを送信する。"][7]{: style="max-width:80%;"}
+![テストするには、まずWhatsAppメッセージを+1 631-202-0907に送信して会話ウィンドウを開いてください」というアラート。その後、テストユーザーに応答メッセージを送信します。」][7]{: style="max-width:80%;"}
 
-## ステップ 4:キャンペーンまたはキャンバスの残りの部分を作成する
+## ステップ 4: キャンペーンまたはキャンバスの残りの部分を作成する
 
 {% tabs %}
 {% tab キャンペーン %}
 
-次に、キャンペーンの残りの部分を構築する。WhatsAppメッセージ作成に最適なツールの使い方については以下のセクションを参照。
+次に、キャンペーンの残りの部分を作成します。WhatsAppメッセージ作成に最適なツールの使い方については以下のセクションを参照。
 
 #### 配信スケジュールまたはトリガーを選択する
 
-WhatsAppメッセージは、スケジュールされた時間、アクション、またはAPIトリガーに基づいて配信することができる。詳しくは、[キャンペーンのスケジューリングを]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/)参照のこと。
+WhatsApp メッセージは、スケジュールされた時刻、アクション、または API トリガーに基づいて配信することができます。詳細については、[キャンペーンのスケジューリング]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/)を参照してください。
 
 アクションベースの配信では、キャンペーンの継続時間と \[[サイレント時間]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/time_based_campaign/#quiet-hours)] を設定することもできます。
 
-このステップでは、ユーザーがキャンペーンを受信する[再資格を]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/#campaigns)得ることを許可したり、[頻度の上限]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)ルールを有効にしたりするなど、配信コントロールを指定することもできる。
+このステップでは、配信コントロールを指定できます。例えば、ユーザーを[再有効化]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/reeligibility/#campaigns)してキャンペーンを受信できるようにしたり、[フリークエンシーキャップ]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping)ルールを有効にしたりできます。
 
 #### ターゲットとするユーザーを選択する
 
-次に、セグメントやフィルターを選択することで、[ユーザーを絞り込む]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)必要がある。すでにサブスクリプショングループを選択しているため、ユーザーがブランドに対して希望しているコミュニケーションの頻度やカテゴリによって、ユーザーが絞り込まれます。このステップでは、セグメントからより多くのオーディエンスを選択し、フィルターを使ってさらにセグメントを絞り込む。セグメントのおおよその人数について現在の状態を示すスナップショットが自動的に表示されます。正確なセグメント・メンバーシップは、常にメッセージが送信される直前に計算されることを覚えておいてほしい。
+次に、セグメントまたはフィルターを選択して[ユーザーをターゲットに設定]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/targeting_users/)し、オーディエンスを絞り込む必要があります。すでにサブスクリプショングループを選択しているため、ユーザーがブランドに対して希望しているコミュニケーションの頻度やカテゴリによって、ユーザーが絞り込まれます。このステップでは、セグメントからより多くのオーディエンスを選択し、フィルターを使ってさらにセグメントを絞り込みます。セグメントのおおよその人数について現在の状態を示すスナップショットが自動的に表示されます。正確なセグメントメンバーシップは常にメッセージが送信される直前に計算されることに注意してください。
 
 #### コンバージョンイベントを選択する
 
 Braze では、キャンペーンを受信した後、ユーザーが指定のアクションや[コンバージョンイベント]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/conversion_events/)を実行する頻度を追跡できます。ユーザーが指定されたアクションを取った場合、コンバージョンがカウントされる最大30日間のウィンドウを許可することができる。
 
-独自のユースケースに基づいて、カスタムコンバージョンイベントを設定することもできます。クリエイティブになり、このキャンペーンの成功をどのように測りたいかを考えよう。
+独自のユースケースに基づいて、カスタムコンバージョンイベントを設定することもできます。このキャンペーンの真の成功を測定する方法について独創的に考えてみましょう。
 
 {% endtab %}
 
 {% tab キャンバス %}
 
-まだやっていない場合は、キャンバス・コンポーネントの残りのセクションを完成させる。キャンバスの残りの部分の構築方法、多変量テストとインテリジェントセレクションの実装方法などの詳細については、キャンバスドキュメントの「[キャンバスを構築する」]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create/)ステップを参照のこと。
+キャンバスコンポーネントが完成していない場合、残りのセクションを完成させます。キャンバスの残りの部分の構築方法、多変量テストとインテリジェントセレクションの実装方法などの詳細については、キャンバスドキュメントの「[キャンバスを構築する」]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_campaign/create/)ステップを参照のこと。
 
-会話ウィンドウは1つの受信メッセージにつき24時間しか使用できないため、Brazeは受信メッセージと応答メッセージの間に24時間を超える遅延がないことを確認する。 
+対話ウィンドウはインバウンドメッセージごとに 24 時間しか継続できないため、Braze はインバウンドメッセージと応答メッセージの間に 24 時間を超える遅延がないことを確認します。 
 
 {% endtab %}
 {% endtabs %}
@@ -183,22 +183,22 @@ WhatsAppのメッセージで以下の内容をユーザーに送ることがで
 ----------- |---------------- 
 ヘッダー | 
 テキスト | 可変パラメーターをサポートする
-画像（JPEGおよびPNG） | 8ビット、RGBまたはRGBAでなければならない。 
-本文 | 可変パラメーターをサポートする
+画像（JPEGおよびPNG） | 8 ビット、RGB または RGBA である必要があり、全タイプで最大 5 MB 
+本文テキスト | 可変パラメーターをサポートする
 フッターテキスト | 可変パラメーターをサポートする 
-CTA | [行動喚起を](#ctas)参照のこと。
+CTA | [コールトゥアクション](#ctas)を参照してください。
 {: .reset-td-br-1 .reset-td-br-2}
 
-#### 行動への呼びかけ {#ctas}
+#### コールトゥアクション {#ctas}
 
 WhatsAppメッセージに次のような行動喚起を追加できる：
 
 CTAタイプ    | 詳細
 ----------- |---------------- 
 ウェブサイトを見る | メッセージテンプレートのみで利用可能。<br>最大1ボタン（可変パラメーターを含む）。
-電話番号 | メッセージテンプレートのみで利用可能。<br>ボタンは最大1つだ。
-カスタムクイック返信ボタン | ボタンは3つまでだ。 
-マーケティング・オプトアウト・ボタン | このオプションは、購読ステータスを自動的に更新しない。<br><br>設定方法については、[オプトインとオプトアウトを]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/message_processing/opt-ins_and_opt-outs/#marketing-opt-out-selection)参照のこと。
+電話番号にかける | メッセージテンプレートのみで利用可能。<br>ボタンは最大 1 つ。
+カスタムクイック返信ボタン | ボタンは最大 3 つ。 
+マーケティング・オプトアウト・ボタン | このオプションは、サブスクリプションステータスを自動的に更新しません。<br><br>設定方法については、[オプトインとオプトアウト]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/message_processing/opt-ins_and_opt-outs/#marketing-opt-out-selection)を参照してください。
 {: .reset-td-br-1 .reset-td-br-2}
 
 ### インバウンドメッセージ
@@ -208,11 +208,11 @@ CTAタイプ    | 詳細
 メッセージ機能    | 詳細
 ----------- |---------------- 
 テキスト | 
-画像（JPEGおよびPNG）| 8ビット、RGBまたはRGBAでなければならない。 
-オーディオ| オーディオ/AAC<br>オーディオ/mp4<br>オーディオ/MPEG<br>オーディオ/AMR<br>audio/ogg （Opus コーデックのみ、ベース audio/ogg はサポートされていない）
-文書 | テキスト/プレーン<br>アプリケーション/pdf<br>application/vnd.ms-powerpoint<br>アプリケーション/msword<br>application/vnd.ms-excel<br>application/vnd.openxmlformats-officedocument.wordprocessingml.document<br>application/vnd.openxmlformats-officedocument.presentationml.presentation<br>application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
-CTA | [行動喚起を](#ctas)参照のこと。
-動画 | ビデオ/MP4、ビデオ/3GP<br><br>H.264 ビデオコーデックとAACオーディオコーデックのみがサポートされている。オーディオ・ストリームが1つだけのビデオや、オーディオ・ストリームがないビデオもサポートしている。
+画像（JPEGおよびPNG）| 8 ビット、RGB または RGBA である必要があり、全タイプで最大 5 MB 
+オーディオ| オーディオ/AAC<br>オーディオ/mp4<br>オーディオ/MPEG<br>オーディオ/AMR<br>audio/ogg (Opus Codec のみ、ベースオーディオ/ogg は非対応)
+文書 | テキスト/プレーン<br>application/pdf<br>application/vnd.ms-powerpoint<br>application/msword<br>application/vnd.ms-excel<br>application/vnd.openxmlformats-officedocument.wordprocessingml.document<br>application/vnd.openxmlformats-officedocument.presentationml.presentation<br>application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
+CTA | [コールトゥアクション](#ctas)を参照してください。
+動画 | ビデオ/MP4、ビデオ/3GP<br><br>H.264 ビデオコーデックと AAC オーディオコーデックのみがサポートされます。オーディオストリームが 1 つだけの動画や、オーディオストリームがない動画もサポートされます。
 {: .reset-td-br-1 .reset-td-br-2}
 
 
diff --git a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign_analytics.md b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign_analytics.md
index 97b9d6b5730..2654f9ba44d 100644
--- a/_lang/ja/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign_analytics.md
+++ b/_lang/ja/_user_guide/message_building_by_channel/whatsapp/whatsapp_campaign_analytics.md
@@ -2,7 +2,7 @@
 nav_title: "レポート"
 article_title: WhatsAppレポート
 page_order: 7
-description: "この記事では、Brazeで使用されているWhatsAppの指標と、WhatsAppキャンペーンでそれらを表示する方法について説明します。"
+description: "この記事では、Braze で使用している WhatsApp の指標と、WhatsApp キャンペーンでそれらを表示する方法について説明します。"
 page_type: reference
 tool:
   - Reports
@@ -13,7 +13,7 @@ channel:
 
 # WhatsAppレポート
 
-> この記事では、Brazeで使用されているWhatsAppの指標と、WhatsAppキャンペーンでそれらを表示する方法について説明します。
+> この記事では、Braze で使用している WhatsApp の指標と、WhatsApp キャンペーンでそれらを表示する方法について説明します。
 
 {% multi_lang_include campaign_analytics.md channel="whatsapp" %}
 
diff --git a/_lang/ja/_user_guide/messaging_users.md b/_lang/ja/_user_guide/messaging_users.md
deleted file mode 100644
index 35084d5e2a2..00000000000
--- a/_lang/ja/_user_guide/messaging_users.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-nav_title: ユーザーへのメッセージング
-article_title: LINE ユーザーへのメッセージング
-page_order: 2
-description: "この記事では、テンプレート化されたキャンペーンとキャンバスを使用してユーザーとチャットする方法について説明します。"
-page_type: reference
-channel:
- - LINE
-hidden: true
-permalink: /line/messaging_users/
----
-
-# LINE ユーザーへのメッセージング
-
-> LINE は双方向通信チャネルです。テンプレート化されたキャンペーンやキャンバスを使用して、ユーザーにメッセージを送信するだけでなく、ユーザーとの会話に参加できます。<br><br>この記事は LINE ベータ版コレクションの一部です。[メインページに戻ります](https://www.braze.com/docs/line/)。
-
-LINE トリガーワードを使用するなど、LINE を通じてユーザーと会話するさまざまな方法があります。また、行動喚起 (CTA) を使用して、LINE メッセージングでユーザーエンゲージメントを促進することもできます。
-
-{% alert important %}
-LINE アクセスはベータ版であり、一部の Braze パッケージでのみ利用できます。利用を始めるには、アカウントマネージャーまたはカスタマーサクセスマネージャーにお問い合わせください。
-{% endalert %}
-
-## アクションベースのトリガー
-
-トリガーワードを含む LINE インバウンドメッセージ (ユーザーから送信されるメッセージ) を受信すると、開始、分岐、途中で変更が行われるキャンペーンやキャンバスを作成できます。ユーザーが送信すると予想される内容と一致するトリガーワードを選択してください。
-
-### キャンペーン
-
-アクションベースの配信キャンペーンをスケジュールする際に、トリガーワードを設定します。
-
-![「メッセージ本文が以下の内容であるサブスクリプショングループにインバウンド LINE を送信したユーザーに、このキャンペーンを送信する」というアクションベースのトリガーと空白フィールド。][1]
-
-### キャンバス
-
-キャンバス内の[アクションパス]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/action_paths)にトリガーワードを設定します。
-
-![「メッセージ本文が以下の内容であるサブスクリプショングループにインバウンド LINE を送信したユーザーに、このキャンペーンを送信する」というトリガーを持つアクションパスと空白フィールド。][2]
-
-### 要件
-
-キャンペーンやキャンバスを作成する際には、トリガーワードの各文字を大文字にする必要がありますが、Braze では、インバウンドトリガーワードを大文字にする必要はありません。例えば、トリガーワードが「JOIN2023」の場合、インバウンドメッセージが「jOin2023」であっても、キャンバスまたはキャンペーンはトリガーされます。
-
-トリガーワードが指定されていない場合、キャンペーンまたはキャンバスは、*すべての*インバウンド LINE メッセージに対して実行されます。これには、アクティブなキャンペーンとキャンバス全体で一致するフレーズを含むメッセージが含まれます。その場合、ユーザーは 2 つの LINE メッセージを受信します。
-
-## 認識されない応答
-
-インタラクティブキャンバスで認識されない応答に対するトリガーオプションを含める必要があります。これにより、ユーザーは利用可能なプロンプト (またはトリガーワード) について通知され、チャネルに対する期待事項が設定されます。
-
-### 認識されない応答に対するトリガーを作成する
-
-カスタムフィルターフレーズのアクショングループを作成後、\[**LINE メッセージを送信**] アクションパスに別のアクショングループを追加し、\[**メッセージ本文の場所**] はチェックしないでください。これは、認識されないユーザー応答をすべてキャッチし、「else」句と同様です。
-
-このメッセージについては、このチャネルは人間が監視していないことをユーザーに通知し、必要に応じてサポートチャネルに案内する LINE メッセージを送信する必要があります。
-
-[1]: {% image_buster /assets/img/line/trigger_word_campaign.png %}
-[2]: {% image_buster /assets/img/line/trigger_word_canvas.png %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/onboarding_faq.md b/_lang/ja/_user_guide/onboarding_faq.md
index fff1306d68b..06fda0467eb 100644
--- a/_lang/ja/_user_guide/onboarding_faq.md
+++ b/_lang/ja/_user_guide/onboarding_faq.md
@@ -16,21 +16,21 @@ description: "このページでは、よくある質問をカテゴリー別に
 
 {% api %}
 
-### 匿名のユーザーデータをどのように扱うか？
+### 匿名ユーザーデータはどのように処理すればよいですか?
 
 {% apitags %}
 ユーザー
 {% endapitags %}
 
-最初に、SDKを介してユーザープロファイルが認識されると、Brazeは、関連する`braze_id` ：Brazeによって設定される一意のユーザー識別子を持つ匿名ユーザープロファイルを作成する。
+まず最初に、ユーザープロファイルが SDK 経由で認識されると、Braze は関連付けられた `braze_id` を持つ匿名ユーザープロファイルを作成します。これは Braze によって設定される一意のユーザー識別子です。
 
-匿名ユーザーをさらに追跡するために、匿名ユーザーに識別子を付けることができる[ユーザーエイリアスを]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle#user-aliases)実装することができる。これらのユーザーは、エイリアスを使用してエクスポートしたり、APIから参照することができる。
+匿名ユーザーをさらに追跡するために、匿名ユーザーに識別子を付けるための[ユーザーエイリアス]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle#user-aliases)を実装できます。これらのユーザーは、エイリアスを使用してエクスポートしたり、API から参照することができます。
 
 エイリアスを持つ、ある匿名ユーザープロファイルが後で `external_id` で認識された場合、それらは通常の識別されたユーザープロファイルとして扱われます。ただし、既存のエイリアスは保持され、そのエイリアスによって参照できます。
 
-識別されたユーザーとマージしたいエイリアスユーザーの場合、保持したい実際のプロ ファイルに関連するフィールドをマージすることができる。エイリアスプロファイルからデータを削除する前に、我々の[Export user profile by identifierエンドポイントを]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)使用して、そのデータをエクスポートする必要がある。そして、[Track usersエンドポイントを使って]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)、これらのイベントをあなたが保持しているプロフィールに投稿することができる。これにより、一方のプロファイルに記録されていたが、もう一方のプロファイルには記録されていなかった属性など、保持したいデータが保持される。
+識別されたユーザーとマージしたいエイリアスユーザーの場合、保持したい実際のプロファイルに関連するフィールドをマージできます。エイリアスプロファイルからデータを削除する前に、[ID でユーザープロファイルをエクスポート]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)エンドポイントを使用して、そのデータをエクスポートする必要があります。その後、[ユーザーを追跡]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)エンドポイントを使って、これらのイベントをあなたが保持しているプロファイルに投稿できます。これにより、一方のプロファイルに記録されていたが、もう一方のプロファイルには記録されていなかった属性など、保持したいデータが保持される。
 
-Brazeで新規および既存のユーザーデータを収集するためのさまざまな方法の詳細については、[データ収集のベストプラクティスを]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/best_practices/)参照のこと。
+Braze で新規および既存のユーザーデータを収集するためのさまざまな方法の詳細については、[データ収集のベストプラクティス]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/best_practices/)を参照してください。
 
 {% endapi %}
 {% api %}
@@ -48,18 +48,18 @@ Brazeで新規および既存のユーザーデータを収集するためのさ
 CSVファイルから**オーディエンス** > **ユーザーのインポート**を通じてユーザープロファイルをアップロードおよび更新できます。顧客データをインポートする場合、各顧客の一意の識別子 (`external_id` とも呼ばれる) を指定する必要があります。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合、これは**Users**>**User Import** にある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、これは \[**ユーザー**] > \[**ユーザーインポート**] にあります。
 {% endalert %}
 
-CSVインポートを開始する前に、Brazeでユーザーをどのように識別するかをエンジニアリングチームから理解しておくことが重要である。一般的に、これは内部で使用されるデータベース ID です。これは、モバイルとウェブでBraze SDKがユーザーを識別する方法と一致するはずで、各顧客は、デバイスを問わず、Braze内で単一のユーザープロファイルを持つことになる。Braze[ユーザープロフィールのライフサイクルについて]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/)詳しく知る。
+CSVインポートを開始する前に、Brazeでユーザーをどのように識別するかをエンジニアリングチームから理解しておくことが重要である。一般的に、これは内部で使用されるデータベース ID です。これは、モバイルと Web で Braze SDK がユーザーを識別する方法と一致する必要があります。これは、各顧客がデバイスを問わず Braze 内で単一のユーザープロファイルを持つようにするためです。詳細については、Braze の[ユーザープロファイルのライフサイクル]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/)を参照してください。
 
 インポートで `external_id` を指定すると、Braze は、同じ `external_id` を持つ既存のユーザーを更新します。`external_id` が見つからない場合は、その external_id を持つ新規ユーザーを作成します。
 
-詳細とCSVインポート・テンプレートのダウンロードについては、[ユーザー・インポートを]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv)参照のこと。
+CSV インポートテンプレートの詳細およびダウンロードについては、[ユーザーインポート]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv)を参照してください。
 
 #### API
 
-API経由でユーザーをアップロードするには、[Track usersエンドポイントを]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)使用してBrazeにユーザーをインポートできる。
+API 経由でユーザーをアップロードするには、[ユーザーを追跡]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)エンドポイントを使用して Braze にユーザーをインポートできます。
 
 ユーザーがすでにBrazeに存在するかどうか不明な場合は、[Export user profile by identifierエンドポイントを]({{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier/)実装して確認することができる。ユーザーがすでにBrazeに存在することを確認したら、`/users/track` エンドポイントを使用して、Brazeにすでに存在するユーザープロファイルに追加したい新しいデータを投稿できる。
 
@@ -67,7 +67,7 @@ API経由でユーザーをアップロードするには、[Track usersエン
 `/users/track` エンドポイントを使用する際には、以下のニュアンスに留意すること：
 
 - このエンドポイントを通じてエイリアスのみのユーザーを作成する場合は、明示的に`_update_existing_only` フラグを false に設定する必要がある。
-- このエンドポイントを使用して購読ステータスを更新すると、外部IDで指定されたユーザー（User1など）が更新され、そのユーザー（User1）と同じ電子メールを持つすべてのユーザーの購読ステータスが更新される。
+- このエンドポイントを使用してサブスクリプションステータスを更新すると、その外部 ID で指定されたユーザー (User1 など) と、そのユーザー (User1) と同じメールアドレスを持つすべてのユーザーのサブスクリプションステータスの両方が更新されます。
 {% endalert %}
 
 {% endapi %}
@@ -79,42 +79,42 @@ API経由でユーザーをアップロードするには、[Track usersエン
 ユーザー
 {% endapitags %}
 
-3つのプッシュ購読状態オプションがある：購読、オプトイン、購読解除。
+プッシュサブスクリプションの状態オプションには、購読、オプトイン、および購読解除の 3 つがあります。
 
-デフォルトでは、ユーザーがプッシュでメッセージを受け取るには、プッシュ購読の状態が購読済みかオプトインになっており、プッシュが有効になっていなければならない。メッセージを作成する際、必要に応じてこの設定を上書きすることができる。
+デフォルトで、プッシュ通知でユーザーがメッセージを受信するには、プッシュ通知のサブスクリプションの状態が購読またはオプトインのいずれかであり、かつプッシュ通知が有効になっていなければなりません。メッセージの作成時に、この設定をオーバーライドできます。
 
 |オプトイン状態|説明|
 |---|---|
-|サブスクリプション登録済み| Brazeでユーザープロファイルが作成されたときのデフォルトのプッシュ購読状態。 |
-|オプトイン| ユーザーは、プッシュ通知を受け取ることを明示的に希望した。Brazeは、ユーザーがOSレベルのプッシュプロンプトを受け入れた場合、ユーザーのオプトイン状態を自動的に`Opted-In` 。<br><br>アンドロイド12以下のユーザーには適用されない。|
-|配信停止済み| ユーザーがアプリケーションやブランドが提供するその他の方法で、プッシュ配信を明示的に解除した。デフォルトでは、Brazeのプッシュキャンペーンは、`Subscribed` 、または`Opted-in` 、プッシュの対象になっているユーザーのみをターゲットとしている。|
+|サブスクリプション登録済み| Braze でユーザープロファイルが作成されたときのデフォルトのプッシュ通知のサブスクリプション状態。 |
+|オプトイン| ユーザーは、プッシュ通知を受け取ることを明示的に希望した。Braze では、ユーザーが OS レベルのプッシュプロンプトを承認した場合に、ユーザーのオプトイン状態を自動的に `Opted-In` に移動します。<br><br>これは Android 12 以下のユーザーには適用されません。|
+|配信停止済み| ユーザーがアプリケーションやブランドが提供するその他の方法で、プッシュ配信を明示的に解除した。デフォルトで、Braze のプッシュキャンペーンは、プッシュが `Subscribed` または `Opted-in` のユーザーのみをターゲットにしています。|
 {: .reset-td-br-1 .reset-td-br-2}
 
 {% endapi %}
 {% api %}
 
-### 重複ユーザーを特定した場合は？
+### 重複ユーザーを特定した場合はどうなりますか?
 
 {% apitags %}
 ユーザー
 {% endapitags %}
 
-重複ユーザーを特定した場合、それらのユーザープロファイルをクリーンアップする必要がある。そのためには以下のステップを踏む：
+重複ユーザーを特定した場合、それらのユーザープロファイルをクリーンアップする必要がある。これは、次の手順で行うことができます。
 
 1. `/users/export/ids` エンドポイントを使用してユーザープロファイルをエクスポートする。
 2. 正しいユーザープロフィールを特定し（最終的には、チームが正しい情報を決定する必要がある）、どちらかを行う：
-    - `/user/track` エンドポイントを使用して、保持したい実際のプロファイルに関連するフィールドをマージする。
+    - `/user/track` エンドポイントを使用して、保持したい実際のプロファイルに関連するフィールドをすべてマージする。
     - users/deleteエンドポイントを使用して、いかなるデータもマージすることなく、重複する非有用なプロファイルを削除する。ユーザープロファイルを削除した後、**その情報を取り出す方法はない**。
 
 {% alert important %}
-まず、正しい`external_id` 、対応するカスタム属性とイベントを持つ新しいユーザープロファイルをインポートすることを推奨する。ユーザー・プロフィールは削除された後、取り戻すことはできないので、削除は最後のステップであるべきだ。
+最初に、新しいユーザープロファイルを正しい `external_id` と対応するカスタム属性およびイベントでインポートすることをお勧めします。ユーザープロファイルが削除されると、それらは取得できなくなるため、削除は最後に行ってください。
 {% endalert %}
 
 いくつか補足しておきたいことがある：
 
 - 重複したユーザープロファイルのエンゲージメントデータ（キャンペーンやキャンバス受信など）は失われる。過去のエンゲージメントコンテキストを保持する唯一の方法は、カスタム属性として追加することである（すべてのキャンペーンやキャンバスを受信した配列カスタム属性など）。
 - ユーザー・プロファイルを移行する際、重複するユーザー・プロファイルのうち、どのユーザー・プロファイルを残すかはチーム次第である。Brazeは、削除するプロフィールのリストを決めたり、提供したりすることはできない。  
-- 最終的には、ユーザーの体験からサインアップ・プロセスを評価し、ユーザーが特定されたときだけ`changeUser()` 。
+- 最終的には、チームがユーザーの経験に基づいてサインアッププロセスを評価し、ユーザーが識別されたときのみに `changeUser()` メソッドを呼び出すようにすることが重要になります。
 
 {% endapi %}
 {% api %}
@@ -127,13 +127,13 @@ API経由でユーザーをアップロードするには、[Track usersエン
 セグメント
 {% endapitags %}
 
-CSV ファイルをインポートするには、\[**ユーザーインポート**] ページの \[ユーザー] セクションに移動します。**最近のインポート」**表には、最近インポートした最大20件のファイル名、ファイル内の行数、インポートに成功した行数、各ファイルの総行数、各インポートのステータスが表示される。
+CSV ファイルをインポートするには、\[**ユーザーインポート**] ページの \[ユーザー] セクションに移動します。\[**最近のインポート**] テーブルには、最近のインポートの最大 20 個までと、それらのファイル名、ファイル内の行数、正常にインポートされた行数、各ファイル内の合計行数、各インポートのステータスが表示されます。
 
-**CSVインポートパネルには**、インポートの指示とインポートを開始するボタンがある。**Select CSV Fileを**クリックし、目的のファイルを選択する。**インポート開始]**をクリックする前に、\[このCSVのユーザーをどうしますか？
+\[**CSV インポート**] パネルには、インポートの指示とインポートを開始するボタンがあります。\[**CSV ファイルを選択**] をクリックし、目的のファイルを選択します。次に、\[**インポートを開始**] をクリックする前に、\[この CSV ファイル内のユーザーに対して何を実行しますか?] の下に、このリストをどうするかを Braze に知らせるオプションがあります。
 
-**このCSVでユーザーをインポートし、この特定のバッチユーザーをグループとして再ターゲットすることも可能にしてから**、**このCSVからインポートされたユーザーからセグメントを自動的に生成するを**選択する。**インポート開始を**クリックすると、Brazeがファイルをアップロードし、列見出しと各列のデータ型をチェックし、セグメントを作成する。
+\[**この CSV ファイル内のユーザーをインポートします。これにより、特定のユーザー群をグループとしてリターゲティングすることもできます**] を選択し、次に \[**この CSV ファイルからインポートされたユーザーから、セグメントを自動的に生成します**] を選択します。**インポート開始を**クリックすると、Brazeがファイルをアップロードし、列見出しと各列のデータ型をチェックし、セグメントを作成する。
 
-CSVテンプレートをダウンロードするには、[ユーザーインポートを]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv)参照のこと。
+CSV テンプレートをダウンロードするには、[ユーザーインポート]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#csv)を参照してください。
 
 {% endapi %}
 {% api %}
@@ -144,7 +144,7 @@ CSVテンプレートをダウンロードするには、[ユーザーインポ
 セグメント
 {% endapitags %}
 
-Braze SDKは、特定の機能や属性に基づいてユーザーをセグメント化し、ターゲットを絞るための強力なフィルター群を提供する。[セグメンテーション・フィルター]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters)用語集を使用して、フィルター・カテゴリー（カスタム・データ、ユーザー・アクティビティ、リターゲティング、マーケティング・アクティビティ、ユーザー属性、インストール・アトリビューション、ソーシャル・アクティビティ、テスト、その他）で検索したり、これらのフィルターを絞り込むことができる。
+Braze SDKは、特定の機能や属性に基づいてユーザーをセグメント化し、ターゲットを絞るための強力なフィルター群を提供する。[セグメンテーションフィルター]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters)用語集を使用して、フィルターカテゴリ (カスタムデータ、ユーザアクティビティ、リターゲティング、マーケティングアクティビティ、ユーザー属性、インストール属性、ソーシャルアクティビティ、テスト、その他) でこれらのフィルターを検索したり絞り込むことができます。
 
 {% endapi %}
 {% api %}
@@ -157,7 +157,7 @@ Braze SDKは、特定の機能や属性に基づいてユーザーをセグメ
 
 Engagementの下にある**Segments**ページに移動し、現在のユーザーセグメントをすべて表示する。このページでは、新しいセグメントを作成して名前を付けることができます。開始するには、\[**セグメントを作成**] をクリックし、セグメントに名前を付けます。
 
-セグメントを作成したら、`Most Recent Location` フィルタを追加し、アプリを最後に使用した場所でユーザーをターゲティングする。標準の円形領域でユーザーをハイライトすることも、カスタム多角形領域を作成することもできる。
+セグメントを作成したら、`Most Recent Location` フィルターを追加して、アプリを使用した最後の場所によりユーザーをターゲットに設定します。標準の円形リージョンのユーザーを強調表示するか、カスタムのポリゴンリージョンを作成できます。
 
 - 円形領域の場合は、原点を移動し、セグメンテーションの位置半径を調整できます。
 - 多角形領域の場合、セグメントに含めたい領域をより具体的に指定できます。
@@ -175,22 +175,22 @@ Braze パートナーによる支援を受けながら、ロケーションタ
 セグメント
 {% endapitags %}
 
-[セグメント・エクステンションを]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/)使うことができる！セグメントエクステンションを使えば、通常のセグメントでは不可能な、より正確なユーザーリストをターゲットにすることができる。
+[セグメントエクステンションを]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/)使うことができます。セグメントエクステンションを使えば、通常のセグメントでは不可能な、より正確なユーザーリストをターゲットにすることができる。
 
-1つのワークスペースにつき最大10個のSegment Extensionsを作成できる。これらの拡張子リストが生成された後、セグメントのフィルターとして含めたり除外したりすることができる。Segment Extensionを作成する際、24時間に1回リストを再生成するように指定することもできる。
+1 つのワークスペースにつき最大 10 個のセグメントエクステンションを作成できます。これらのエクステンションリストは、生成後にセグメントにフィルターとして含めるか、除外することができます。セグメントエクステンションを作成するときに、24 時間ごとにリストを再生成するように指定することもできます。
 
-1. Engagementsの下にある**Segmentsを**展開し、**Segment Extensionを**クリックする。
-2. Segment Extensionsテーブルから、**\+ Create New Extensionを**クリックする。
+1. エンゲージメントの下にある \[**セグメント**] を展開し、\[**セグメントエクステンション**] をクリックします。
+2. セグメントエクステンションテーブルから、\[**\+ 新しいエクステンションを作成**] をクリックします。
 3. フィルタリングするユーザーのタイプを記述して、セグメントエクステンションに名前を付けます。これにより、このエクステンションをフィルターとしてセグメントに適用するときに、このエクステンションを簡単かつ正確に検出できます。
-4. ターゲティングの基準を購入またはカスタムイベントのどちらかから選択する。
+4. ターゲット設定の基準を購入またはカスタムイベントのどちらかから選択します。
 5. ユーザーリストのターゲットにしたい購入アイテムや特定のカスタムイベントを選択する。 
-6. ユーザーが何回（以上、以下、等しい）イベントを完了させる必要があるか、また、何日間（最大365日間）まで振り返るかを選択する。
+6. 次に、ユーザーがイベントを完了する必要がある回数 (より大きい、より小さい、または等しい) と、さかのぼる期間 (過去 365 日間以内) を選択します。
 
 ターゲティングの精度を上げるために、**プロパティフィルターを追加を**選択し、購入またはカスタムイベントの特定のプロパティに基づいてセグメントすることができる。Brazeは、文字列、数値、ブーリアン、および時間オブジェクトに基づくイベントプロパティのセグメンテーションをサポートしている。
 
 [階層化イベントプロパティ]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/nested_objects/)に基づくセグメンテーションもサポートしています。
 
-セグメント・エクステンションは、イベント・プロパティの長期保存に依存しており、30日間のカスタム・イベント・プロパティの保存制限がない。つまり、過去1年以内にトラッキングされたイベント・プロパティを振り返ることができ、トラッキングはエクステンションがセットアップされるまで待つ必要がない。
+セグメントエクステンションはイベントプロパティの長期保存に依存しており、30 日間のカスタムイベント保存制限はありません。つまり、過去1年以内にトラッキングされたイベント・プロパティを振り返ることができ、トラッキングはエクステンションがセットアップされるまで待つ必要がない。
 
 {% alert note %}
 セグメントエクステンション内でイベントプロパティを使用しても、データポイント使用量には影響しません。
@@ -205,11 +205,11 @@ Braze パートナーによる支援を受けながら、ロケーションタ
 セグメント
 {% endapitags %}
 
-このエクステンションで特定の時点の1つのスナップショットを表すかどうか、またはこのエクステンションを毎日再生成するかどうかを指定できます。エクステンションは常に最初の保存後に処理を開始します。拡張機能を毎日再生成したい場合は、**Regenerate Extension Daily（拡張機能を毎日再生成**）を選択すると、御社のタイムゾーンで毎日午前0時ごろに再生成が開始される。
+このエクステンションで特定の時点の1つのスナップショットを表すかどうか、またはこのエクステンションを毎日再生成するかどうかを指定できます。エクステンションは常に最初の保存後に処理を開始します。エクステンションを毎日再生成する場合は、\[**エクステンションを毎日再生成**] を選択すると、会社のタイムゾーンで毎日午前 0 時頃に再生成の処理が開始されます。
 
-終わったら、**Saveを**クリックする。延長手続きが開始される。エクステンションの生成にかかる時間は、ユーザーの数、キャプチャするカスタムイベントまたは購入イベントの数、履歴を振り返る日数によって異なります。
+完了したら、\[**保存**] をクリックします。延長手続きが開始される。エクステンションの生成にかかる時間は、ユーザーの数、キャプチャするカスタムイベントまたは購入イベントの数、履歴を振り返る日数によって異なります。
 
-最後に、エクステンションを作成した後、セグメントを作成したり、キャンペーンやキャンバスのオーディエンスを定義する際にフィルターとして使用することができる。まず、**ユーザー属性**セクションのフィルターリストから`Braze Segment Extension` 。Braze セグメントエクステンションフィルターリストから、このセグメントに含める、または除外したいエクステンションを選択します。エクステンションの基準を表示するには、**View Extension Detailsを**クリックする。これで、通常通りセグメントの作成ができる。
+最後に、エクステンションを作成した後、セグメントを作成したり、キャンペーンやキャンバスのオーディエンスを定義する際にフィルターとして使用することができる。まず、**ユーザー属性**セクションのフィルターリストから`Braze Segment Extension` 。Braze セグメントエクステンションフィルターリストから、このセグメントに含める、または除外したいエクステンションを選択します。エクステンションの基準を表示するには、\[**エクステンションの詳細を表示**] をクリックします。これで、セグメントの作成を通常どおり進めることができます。
 
 {% endapi %}
 {% api %}
@@ -222,7 +222,7 @@ Braze パートナーによる支援を受けながら、ロケーションタ
 キャンペーン
 {% endapitags %}
 
-マルチチャネルキャンペーンを作成するには、**キャンペーン**ページに行き、**キャンペーンの作成を**選択し、**マルチチャネルキャンペーンを**選択する。マルチチャネルキャンペーン内では、作成タブから**メッセージングチャネルを追加を**選択し、希望のチャネルを追加する。表示されるチャンネルアイコンをクリックすると、さまざまなメッセージングコンポーザーが切り替わり、異なるチャンネル用にキャンペーンコピーを作成することができる。
+マルチチャネルキャンペーンを作成するには、\[**キャンペーン**] ページに移動して、\[**キャンペーンを作成**] を選択し、\[**マルチチャネルキャンペーン**] を選択します。マルチチャネルキャンペーン内では、作成タブから \[**メッセージングチャネルを追加**] を選択し、目的のチャネルを追加します。表示されるチャンネルアイコンをクリックすると、さまざまなメッセージングコンポーザーが切り替わり、異なるチャンネル用にキャンペーンコピーを作成することができる。
 
 {% endapi %}
 {% api %}
@@ -233,7 +233,7 @@ Braze パートナーによる支援を受けながら、ロケーションタ
 キャンペーン
 {% endapitags %}
 
-多変量キャンペーンを作成し、複数のバリアントでキャンバスを実行することは、始めるのに最適な方法だ！例えば、[多変量キャンペーン]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/)を実行して、コピーや件名が異なる 1 つのメッセージをテストできます。複数のバリアントを持つキャンバスは、ワークフロー全体のテストに役立ちます。
+まずは多変量キャンペーンを作成して複数のバリアントでキャンバスを実行することをお勧めします。例えば、[多変量キャンペーン]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/)を実行して、コピーや件名が異なる 1 つのメッセージをテストできます。複数のバリアントを持つキャンバスは、ワークフロー全体のテストに役立ちます。
 
 {% endapi %}
 {% api %}
@@ -244,7 +244,7 @@ Braze パートナーによる支援を受けながら、ロケーションタ
 キャンペーン
 {% endapitags %}
 
-この違いの 1 つの説明としては、キャンペーンまたはキャンバスの再適格性がオンになっていることが考えられます。これをオンにすると、セグメントと配信設定に該当するユーザーがメッセージを複数回受信できるようになります。再受信資格がオンになっていない場合、送信者と一意の受信者の違いの説明として、ユーザーが自分のプロファイルに関連するプラットフォーム間で複数のデバイスを持っていることが考えられる。
+この違いの 1 つの説明としては、キャンペーンまたはキャンバスの再適格性がオンになっていることが考えられます。これをオンにすると、セグメントと配信設定に該当するユーザーがメッセージを複数回受信できるようになります。再適格性がオンになっていない場合、送信数とユニーク受信者数の違いについての説明として、ユーザーがプラットフォームをまたぐ複数のデバイスをプロファイルに関連付けていることが考えられます。
 
 たとえば、iOS と Web の両方のプッシュ通知を持つキャンバスがある場合、モバイルデバイスとデスクトップデバイスの両方を使用する特定のユーザーは複数のメッセージを受信する可能性があります。
 
@@ -270,9 +270,9 @@ Braze パートナーによる支援を受けながら、ロケーションタ
 キャンペーン
 {% endapitags %}
 
-Braze はユーザーのタイムゾーンをデバイスから自動的に判別します。これは、タイムゾーンの正確さとユーザーの完全なカバーをサポートするように設計されている。ユーザー API を通じて作成されたユーザーや、タイムゾーンなしで作成されたユーザーは、SDK によってアプリで認識されるまで、既定のタイムゾーンとして貴社のタイムゾーンが使用されます。
+Braze はユーザーのタイムゾーンをデバイスから自動的に判別します。これは、タイムゾーンの正確さとユーザーの完全な範囲をサポートするように設計されています。ユーザー API を通じて作成されたユーザーや、タイムゾーンなしで作成されたユーザーは、SDK によってアプリで認識されるまで、既定のタイムゾーンとして貴社のタイムゾーンが使用されます。
 
-会社のタイムゾーンは[会社の]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/company-wide_settings_management/)設定で確認できる。
+会社のタイムゾーンは \[[会社の設定]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/company-wide_settings_management/)] で確認できます。
 
 {% endapi %}
 {% api %}
@@ -283,7 +283,7 @@ Braze はユーザーのタイムゾーンをデバイスから自動的に判
 キャンペーン
 {% endapitags %}
 
-キャンペーンをスケジューリングする際には、指定した時間に送信することを選択し、次に**ローカルタイムゾーンのユーザーにキャンペーンを送信するを**選択する必要がある。
+キャンペーンをスケジュールするときは、指定した時刻に送信することを選択してから、\[**ユーザーのローカルタイムゾーンにあわせてキャンペーンを送信**] を選択する必要があります。
 
 Braze では、すべてのローカルタイムゾーンキャンペーンを 24 時間前までにスケジュールすることを強く推奨しています。このようなキャンペーンは丸一日かけて送信する必要があるため、24時間前にスケジューリングすることで、セグメント全体にメッセージを届けることができる。ただし、これらのキャンペーンは、必要に応じて 24 時間以内にスケジュールすることもできます。Braze は、送信時刻から 1 時間以上が経過しているユーザーに対してはメッセージを送信しないことに注意してください。
 
@@ -292,7 +292,7 @@ Braze では、すべてのローカルタイムゾーンキャンペーンを 2
 24 時間以内にスケジュールされているローカルタイムゾーンのキャンペーンを編集しても、メッセージのスケジュールは変更されません。ローカルタイムゾーンのキャンペーンを後で送信するよう (例えば午後 6 時ではなく午後 7 時) に編集した場合、元の送信時刻が選択されたときにターゲットセグメントにいたユーザーは、引き続き元の時刻 (午後 6 時) にメッセージを受信します。ローカルタイムゾーンをより早い時刻 (例えば午後 5 時ではなく午後 4 時<b>) </b>に送信するよう編集しても、キャンペーンは元の時刻 (午後5時) にすべてのセグメントメンバーに送信されます。
 
 {% alert note %}
-キャンバス・ステップの場合、ローカル・タイムゾーン配信のため、ユーザーは次のステップを受信するために24時間ステップにいる必要はない。
+キャンバスステップの場合、ローカルタイムゾーン配信の次のステップを受信するために、ユーザーが 24 時間ステップにいる必要はありません。
 {% endalert %}
 
 ユーザーがキャンペーンの対象になることを許可している場合は、元の時刻 (午後 5 時) にユーザーが再度受け取ることになります。ただし、それ以降のキャンペーンでは、メッセージは更新された時刻にのみ送信されます。
@@ -333,9 +333,9 @@ Braze では、すべてのローカルタイムゾーンキャンペーンを 2
 キャンペーン
 {% endapitags %}
 
-- 一度だけスケジュールされたキャンペーンは、スケジュールされた送信時間まで編集することができる。
-- 定期的なスケジュールキャンペーンは、送信予定時刻まで編集できる。
-- ローカル送信時間キャンペーンは、送信予定時間の24時間前まで編集できる。
+- 1 回限りのスケジュールキャンペーンは、送信予定時刻になるまで編集できます。
+- 定期的なスケジュールキャンペーンは、送信予定時刻になるまで編集できます。
+- ローカル送信時間キャンペーンは、送信予定時間の 24 時間前まで編集できます。
 - 最適な送信時間のキャンペーンは、送信予定日の24時間前まで編集できる。
 
 {% endapi %}
@@ -384,7 +384,7 @@ Braze では、すべてのローカルタイムゾーンキャンペーンを 2
 - 2021 年 8 月 6 日午後 9 時、ニューヨーク
 - 2021 年 8 月 7 日午後 2 時、ニューヨーク
 
-ユーザーは打ち上げの24時間前からセグメントにいる必要がある。ユーザーが最初のチェックで不適格となった場合、Braze は 2 回目のチェックを試みません。
+ユーザーは開始の 24 時間前からセグメントにいる必要があります。ユーザーが最初のチェックで不適格となった場合、Braze は 2 回目のチェックを試みません。
 
 {% endapi %}
 {% api %}
@@ -395,7 +395,7 @@ Braze では、すべてのローカルタイムゾーンキャンペーンを 2
 キャンペーン
 {% endapitags %}
 
-キャンペーンに入るユーザー数は、オーディエンスやトリガーの評価方法によって、予想数と異なる場合があります。Brazeでは、オーディエンスはトリガーの前に評価される（[属性変更トリガーを]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery/attribute_triggers#change-custom-attribute-value)使用しない限り）。これは、トリガーアクションが評価される前に、ユーザーが最初に選択したオーディエンスの一部でない場合、キャンペーンから脱落する原因となる。
+キャンペーンに入るユーザー数は、オーディエンスやトリガーの評価方法によって、予想数と異なる場合があります。Braze では、オーディエンスはトリガーの前に評価されます (ただし、[属性の変更トリガー]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/delivery_types/triggered_delivery/attribute_triggers#change-custom-attribute-value)を使用する場合を除きます)。これは、トリガーアクションが評価される前に、ユーザーが最初に選択したオーディエンスの一部でない場合、キャンペーンから脱落する原因となる。
 
 {% endapi %}
 {% api %}
@@ -425,10 +425,10 @@ Canvases
 
 - ユーザーがキャンバスに入れなくなる。
 - ユーザーがフローのどの位置にいても、メッセージはそれ以上送信されない。
-    - **例外:**メールキャンバスはすぐには止まらない。送信リクエストが SendGrid に送られた後は、ユーザーへの配信を即停止するために Braze ができることは何もありません。
+    - **例外:**メールキャンバスはすぐには停止しません。送信リクエストが SendGrid に送られた後は、ユーザーへの配信を即停止するために Braze ができることは何もありません。
 
 {% alert note %}
-キャンバスを停止しても、ステップで待機しているユーザーは退出しません。キャンバスを再度有効にしてもユーザーがまだ待っている場合、ユーザーはステップを完了し、次のコンポーネントに移る。しかし、ユーザーが次のコンポーネントに進むべき時間を過ぎてしまった場合、ユーザーはキャンバスから退出してしまう。
+キャンバスを停止しても、ステップで待機しているユーザーは退出しません。キャンバスを再度有効にしてもユーザーがまだ待っている場合、ユーザーはステップを完了し、次のコンポーネントに進みます。しかし、ユーザーが次のコンポーネントに進むべき時間を過ぎてしまった場合、ユーザーはキャンバスを終了します。
 {% endalert %}
 
 {% endapi %}
@@ -455,7 +455,7 @@ Canvases
 
 マルチステップキャンバスの一部のステップを編集した場合、すでにオーディエンスでありながらステップを受け取っていないユーザーは、更新後のバージョンのメッセージを受け取ることになります。これは、まだそのステップで評価されていない場合のみに該当することに注意してください。
 
-ローンチ後に編集できること、できないことの詳細については、[ローンチ後にキャンバスを変更するを]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/change_your_canvas_after_launch/)参照のこと。
+開始後に編集できる内容については、[開始後にキャンバスを変更する]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/change_your_canvas_after_launch/)を参照してください。
 
 {% endapi %}
 {% api %}
@@ -488,10 +488,10 @@ Canvases
 
 #### 使用例2
 
-クワイエットアワーにはワンステップキャンバスがある：
+サイレント時間を有効にした 1 ステップのキャンバスがあるとします。
 
 1. ユーザーがキャンバスに入ります。
-2. 最初のステップにはディレイはないが、クワイエットアワー内であるため、メッセージは抑制される。
+2. 最初のステップに遅延はありませんが、サイレント時間内であるため、メッセージは抑制されます。
 3. ユーザーがコンバージョンイベントを実行します。
 
 **結果:**
@@ -543,22 +543,22 @@ Canvases
 分析
 {% endapitags %}
 
-**収益**ページでは、特定の期間、特定の製品、またはアプリの総収益または購入に関するデータを表示することができる。これらの収益数は、一定のコンバージョン期間内にキャンペーン受信者から購入されたものから発生する。
+\[**収益**] ページでは、特定商品の特定期間の収益または購入、またはアプリの総収益または購入に関するデータを表示できます。これらの収益データは、一定のコンバージョン期間内にキャンペーン受信者が行った購入から生成されます。
 
-とはいえ、Brazeはマーケティングツールであり、収益管理ツールではないことに注意する必要がある。私たちの[購買オブジェクトは]({{site.baseurl}}/api/objects_filters/purchase_object/)払い戻しやキャンセルをサポートしていないため、他のツールとデータを比較する際に矛盾が生じる可能性がある。
+ただし、Braze はマーケティングツールであり、収益管理ツールではないことに注意する必要があります。私たちの[購買オブジェクトは]({{site.baseurl}}/api/objects_filters/purchase_object/)払い戻しやキャンセルをサポートしていないため、他のツールとデータを比較する際に矛盾が生じる可能性がある。
 
 {% endapi %}
 {% api %}
 
-### Currentsはどのようなレポーティングを可能にするのか？
+### Currents ではどのようなレポート機能が有効になりますか?
 
 {% apitags %}
 分析
 {% endapitags %}
 
-BrazeのCurrentsツールは、メッセージングエンゲージメントと顧客行動データの両方を、Brazeの数あるデータパートナーのいずれかに継続的にストリーミングする。
+Braze の Currents ツールは、メッセージングエンゲージメントと顧客行動データの両方を、弊社の多くのデータパートナーのいずれかに継続的にストリーミングします。これにより、Braze が作成するユニークで価値のあるデータを活用して、クラス最高のパートナー各社におけるビジネスインテリジェンスと分析の取り組みを強化することができます。
 
-このデータには、メッセージング・エンゲージメントの指標にとどまらず、カスタム属性やイベントのパフォーマンスなど、より複雑な数値も含まれる。詳しくは、[時事用語集を]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events)ご覧いただきたい。
+このデータには、メッセージング・エンゲージメントの指標にとどまらず、カスタム属性やイベントのパフォーマンスなど、より複雑な数値も含まれる。詳細については、[Currents のイベント用語集]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events)を参照してください。
 
 {% endapi %}
 {% api %}
@@ -571,15 +571,15 @@ BrazeのCurrentsツールは、メッセージングエンゲージメントと
 
 定期的なエンゲージメント・レポートをスケジュールするには、以下のようにする：
 
-1. ダッシュボードのアカウントで、「**データ」の**下にある「**エンゲージメント・レポート**」に移動する。
+1. ダッシュボードアカウントで、\[**エンゲージメントレポート**] (\[**データ**] の下) に移動します。
 2. \[**\+ 新しいレポートを作成**] をクリックします。
 3. レポートにまとめたい[キャンペーンとキャンバスメッセージを]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#manually-select-campaigns-or-canvases)（個別または[タグごとに]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#automatically-select-campaigns-or-canvases)）追加する。
 4. レポートに[統計を追加する]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#add-statistics-to-your-report)。
 5. レポートの圧縮とデリミネーターを選択する。
 6. このレポートを受け取るBrazeユーザーのEメールアドレスを入力する。
-7. レポートを作成する[時間枠を]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#time-frame)選択する。
+7. レポートでデータを実行する \[[期間]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#time-frame)] を選択します。
 8. データの内訳を確認したい[間隔（毎日、毎週など）を]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#data-display)選択する。
-9. スケジュールあなたのレポートを[すぐに送信する]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#send-immediately)か、[将来の指定された時間]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#send-at-designated-time)に送信するように設定します。
+9. レポートを[すぐに送信]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#send-immediately)するか、[将来の時刻を指定]({{site.baseurl}}//user_guide/data_and_analytics/reporting/engagement_reports/#send-at-designated-time)して送信するかを設定します。
 10. レポートを実行し、Eメールが届いたらそれを開く！
 
 {% endapi %}
@@ -595,6 +595,6 @@ BrazeのCurrentsツールは、メッセージングエンゲージメントと
 
 レポートビルダーを使用すると、複数のキャンペーンまたはキャンバスの結果を 1 つのビューで比較できるため、主要な指標に最も影響を与えたエンゲージメント戦略を簡単に判断できます。キャンペーンとキャンバスの両方について、データをエクスポートし、レポートを保存して今後表示できます。
 
-Brazeのレポートとアナリティクスの使い方については、[レポートの概要を]({{site.baseurl}}/user_guide/data_and_analytics/reporting/reports_overview/)参照のこと。
+Braze のレポートと分析の使用方法の詳細については、[レポートの概要]({{site.baseurl}}/user_guide/data_and_analytics/reporting/reports_overview/)を参照してください。
 
 {% endapi %}
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/catalog_triggers/price_drop_notifications.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/catalog_triggers/price_drop_notifications.md
index 25ef808739c..abc4302d9d1 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/catalog_triggers/price_drop_notifications.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/catalog_triggers/price_drop_notifications.md
@@ -8,21 +8,21 @@ description: "この参考記事では、Brazeカタログで値下げ通知を
 
 # 値下げ通知
 
-> Brazeカタログによる値下げ通知とCanvasを組み合わせることで、商品の価格が下がったことを顧客に通知することができる。顧客が選択したカスタムイベントを実行するたびに、その商品の価格が値下げされたときに通知されるように自動的に購読することができる。
+> Brazeカタログによる値下げ通知とCanvasを組み合わせることで、商品の価格が下がったことを顧客に通知することができる。選択されたカスタムイベントを実行した顧客が、商品の価格が下がった時に通知を受け取れるよう自動的に配信登録できます。
 
 {% alert important %}
-カタログの値下げ通知は、現在早期アクセス中である。この早期アクセスへの参加に興味がある場合は、アカウント・マネージャーに連絡しよう。
+カタログの価格低下通知は現在早期アクセス中です。早期アクセスへの参加に興味がある場合は、アカウントマネージャーにお問い合わせください。
 {% endalert %}
 
-ユーザーがアイテムのカスタムイベントをトリガーすると、自動的にそのアイテムの値下がり通知を受け取るように登録する。商品の価格が在庫ルール（50％以上の下落など）を満たすと、すべての購読者はキャンペーンやキャンバスを通じて通知を受けることができる。ただし、通知を受け取ることができるのは、通知をオプトインしたユーザーのみである。 
+ユーザーがアイテムのカスタムイベントをトリガーすると、そのアイテムの価格低下通知を受信できるよう自動的に購読登録されます。商品の価格が在庫ルール (50% 以上の値下げなど) を満たすと、すべての購読者はキャンペーンやキャンバスを通じて通知を受けることができます。ただし、通知を受け取ることができるのは、通知にオプトインしたユーザーのみです。 
 
 ## 値下げ通知の仕組み
 
-`product_clicked` イベントなど、購読イベントとして使用するカスタムイベントを設定する。このイベントには、アイテムID（カタログアイテムID）のプロパティが含まれていなければならない。カタログ名を入れることをお勧めするが、これは必須ではない。価格フィールドの名前も指定するが、これは数値データ型でなければならない。選択されたカスタムイベントがユーザーによって実行され、`price_drop` を含む`type` プロパティを持つとき、それはユーザーとそれが発生したカタログアイテムのためのプライスドロップサブスクリプションを作成するために使用することができる。
+`product_clicked` イベントなど、購読イベントとして使用するカスタムイベントを設定します。このイベントには、アイテム ID (カタログアイテム ID) のプロパティが含まれている必要があります。カタログ名を入れることをお勧めするが、これは必須ではない。価格フィールドの名前も指定するが、これは数値データ型でなければならない。選択されたカスタムイベントがユーザーによって実行され、`price_drop` を含む `type` プロパティを持つ場合、ユーザーとそれが発生したカタログアイテムのための価格低下サブスクリプションを作成するためにこのイベントを使用できます。
 
-アイテムが価格ルールを満たす価格変更をした場合、そのアイテムを購読しているすべてのユーザー（購読イベントを行ったユーザー）を検索し、キャンペーンやキャンバスのトリガーに使用できるBrazeカスタムイベントを送信する。
+アイテムに価格ルールを満たす価格変更がある場合、そのアイテムを購読しているすべてのユーザー (サブスクリプションイベントを行ったユーザー) を検索し、キャンペーンまたはキャンバスのトリガーに使用できる Braze カスタムイベントを送信します。
 
-イベントプロパティはユーザーと一緒に送信されるので、送信するキャンペーンやキャンバスにアイテムの詳細をテンプレートすることができる！
+イベントプロパティはユーザーと一緒に送信されるため、アイテムの詳細を送信するキャンペーンまたはキャンバスにテンプレートで挿入できます。
 
 ## 値下げ通知を設定する
 
@@ -32,10 +32,10 @@ description: "この参考記事では、Brazeカタログで値下げ通知を
 2. **値下げ**トグルを選択する。<br>
 3. グローバル・カタログ設定が構成されていない場合、通知のトリガーに使用されるカスタム・イベントとプロパティをセットアップするよう促される：
     <br> ![カタログ設定の引き出し。][2]{: style="max-width:70%;"}
-    - **購読のためのカスタムイベント：**カタログ通知をユーザーに購読させるために使用されるBrazeカスタムイベント。このイベントが発生すると、そのイベントを実行したユーザーがサブスクライブされる。
-    - **配信停止用のカスタムイベント：**Brazeカスタムイベントは、ユーザーを通知から解除するために使用される。
-    - **アイテム ID イベントプロパティ：**サブスクリプションまたはアンサブスクリプションのアイテムを決定するために使用される、上記のカスタムイベントのプロパティ。カスタムイベントのこのプロパティは、カタログに存在するアイテムIDを含むべきである。カスタムイベントは、このアイテムがどのカタログにあるかを指定するために、`catalog_name` プロパティを含まなければならない。
-    - **フォールバック・カタログ**カスタムイベントに`catalog_name` プロパティがない場合、サブスクリプションに使用されるカタログ。
+    - **購読のカスタムイベント: **カタログ通知をユーザーに購読させるために使用されるBrazeカスタムイベント。このイベントが発生すると、そのイベントを実行したユーザーがサブスクライブされる。
+    - **配信停止のカスタムイベント: **ユーザーを通知から購読解除するために使用される Braze カスタムイベント。
+    - **アイテム ID イベントプロパティ: **サブスクリプションまたはアンサブスクリプションのアイテムを決定するために使用される、上記のカスタムイベントのプロパティ。カスタムイベントのこのプロパティは、カタログに存在するアイテムIDを含むべきである。カスタムイベントは、このアイテムがどのカタログにあるかを指定するために、`catalog_name` プロパティを含んでいる必要があります。
+    - **フォールバックカタログ: **カスタムイベントに`catalog_name` プロパティがない場合、サブスクリプションに使用されるカタログ。
     - カスタムイベントのサンプルは次のようになる。
     ```json
     {
@@ -54,13 +54,13 @@ description: "この参考記事では、Brazeカタログで値下げ通知を
     }
     ```
     <br>
-4. **保存を**選択し、カタログの**設定**ページに進む。<br>
-5. 通知ルールを設定する。選択肢は2つある：
-    - **すべての購読ユーザーに通知 "**は、商品の価格が下がったときに、待機しているすべての顧客に通知する。
-    - **一定時間ごとに一定数のユーザーに通知する**設定した通知時間ごとに、指定した数の顧客に通知する。Brazeは、通知する顧客がいなくなるまで、または商品の価格が上がるまで、指定された数の顧客に小刻みに通知する。通知速度は、1分あたり10,000ユーザーを超えることはできない。
-6. **カタログの価格欄を**設定する。これは、商品の価格を決定するために使用されるカタログフィールドである。数値型でなければならない。<br>
-7. **値下げルールを**設定する。これは、通知が送信されるべきかどうかを決定するために使用されるロジックである。価格下落は、価格の変化率、または価格フィールドの変化量として設定することができる。<br>
-8. **Save settingsを**選択する。
+4. \[**保存**] を選択し、カタログの \[**設定**] ページに進みます。<br>
+5. 通知ルールを設定する。2 つのオプションがあります。
+    - \[**サブスクリプション登録済みのすべてのユーザーに通知**] は、商品の価格が下がったときに、待機しているすべての顧客に通知します。
+    - **一定時間ごとに一定数のユーザーに通知する**設定した通知時間ごとに、指定した数の顧客に通知する。Braze は、通知する顧客がいなくなるまで、または商品の価格が再び上がるまで、指定された数の顧客に段階的に通知します。通知速度は 1 分あたり 10,000 ユーザーを超えることはできません。
+6. **カタログの価格フィールド**を設定します。これは、商品の価格を決定するために使用されるカタログフィールドである。数値型でなければなりません。<br>
+7. **値下げルール**を設定します。これは、通知が送信されるべきかどうかを決定するために使用されるロジックである。価格の低下は、価格の変化率、価格フィールドがどれだけ変化したかによって設定できます。<br>
+8. \[**設定を保存**] を選択します。
 
 ![値下げ機能がオンになっていることを示すカタログ設定。値下げルールは、元の価格に対して3％の変更である。][1]{:style="max-width:60%;"}
 
@@ -73,25 +73,25 @@ description: "この参考記事では、Brazeカタログで値下げ通知を
 カタログで値下がり通知を設定した後、これらの通知をキャンバスで使用するには以下の手順に従う。
 
 1. アクションベースのキャンバスを設定する。
-2. トリガーとして**Perform Price Drop Eventを**選択する。
+2. トリガーとして \[**値下げイベントを実行**] を選択します。
 3. 価格下落通知のあるカタログ名を選択する。
 4. キャンバスの[セットアップを]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/)通常通り続ける。
 
 これで、商品の価格が下がったときに顧客に通知される。
 
-### 液体の使用
+### Liquid の使用
 
-値下がりしたカタログ商品の詳細をテンプレート化するには、`canvas_entry_properties` リキッドタグを使用して、`item_id` にアクセスすることができる。 
+値下がりしたカタログアイテムの詳細をテンプレートで挿入するには、`canvas_entry_properties` リキッドタグを使用して、`item_id` にアクセスします。 
 
-{%raw%}``{{canvas_entry_properties.${catalog_update}.item_id}}``{%endraw%} 、値下がりしたアイテムのIDが返される。{%raw%}``{{canvas_entry_properties.${catalog_update}.previous_value}}``{%endraw%} 、更新前のアイテムの価格値が返され、{%raw%}``{{canvas_entry_properties.${catalog_update}.new_value}}``{%endraw%} 、更新後の新しい価格値が返される。 
+{%raw%}``{{canvas_entry_properties.${catalog_update}.item_id}}``{%endraw%} を使用すると、価格が下がったアイテムの ID が返されます。{%raw%}``{{canvas_entry_properties.${catalog_update}.previous_value}}``{%endraw%} は更新前のアイテムの価格を返し、{%raw%}``{{canvas_entry_properties.${catalog_update}.new_value}}``{%endraw%} は更新後の新しい価格を返します。 
 
-このリキッドタグ{%raw%}``{% catalog_items <name_of_your_catalog> {{canvas_entry_properties.${catalog_update}.item_id}} %}}``{%endraw%} をメッセージの先頭で使い、{%raw%}`{{items[0].<field_name>}}`{%endraw%} を使ってメッセージ全体を通してそのアイテムに関するデータにアクセスする。
+この Liquid タグ {%raw%}``{% catalog_items <name_of_your_catalog> {{canvas_entry_properties.${catalog_update}.item_id}} %}}``{%endraw%} をメッセージの冒頭で使い、{%raw%}`{{items[0].<field_name>}}`{%endraw%} をメッセージ全体で使用してそのアイテムに関するデータにアクセスします。
 
 ## 考慮事項
 
-- ユーザーは90日間契約する。アイテムが90日経っても値下がりしない場合、ユーザーはサブスクリプションから外される。
+- ユーザーの購読期間は 90 日間です。アイテムが90日経っても値下がりしない場合、ユーザーはサブスクリプションから外される。
 - **Notify all subscribed users**通知ルールを使用する場合、Brazeは10分間で10万人のユーザーに通知する。
-- Brazeは1分間に最大10件のアイテム更新を処理する。つまり、1分間に11のアイテムを更新した場合、最初の10アイテムだけが値下げ通知のトリガーとなる。
+- Braze は、1 分あたり最大 10 のアイテム更新を処理します。つまり、1分間に11のアイテムを更新した場合、最初の10アイテムだけが値下げ通知のトリガーとなる。
 
 [1]: {% image_buster /assets/img/price_drop_notifications.png %}
 [2]: {% image_buster /assets/img/catalog_settings_drawer.png %}
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/selections.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/selections.md
index 90e04fbee84..de5189d1fe8 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/selections.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/selections.md
@@ -2,56 +2,56 @@
 nav_title: セレクション
 article_title: セレクション
 page_order: 5
-description: "この参考記事では、Brazeのキャンペーンでデータを参照するために、カタログでセレクションを作成し、使用する方法について説明する。"
+description: "この記事では、Braze キャンペーンでデータを参照するために、カタログでセレクションを作成し、使用する方法について説明します。"
 ---
 
 # セレクション
 
 > カタログでセレクションを作成し、使用する方法を学ぶ。
 
-セレクションは、キャンペーンの各ユーザーにメッセージをパーソナライズするために使用できるデータのグループである。選択範囲を使用する場合、基本的にはカタログの特定の列に基づいてカスタムフィルターを設定することになる。これには、ブランド、サイズ、場所、追加日などのフィルターが含まれる。アイテムが最初に満たさなければならない基準を定義できるため、ユーザーに何を見せるかをコントロールできる。
+セレクションは、キャンペーンの各ユーザーにメッセージをパーソナライズするために使用できるデータのグループである。選択範囲を使用する場合、基本的にはカタログの特定の列に基づいてカスタムフィルターを設定することになる。これには、ブランド、サイズ、場所、追加日などのフィルターが含まれます。アイテムが最初に満たさなければならない基準を定義できるため、ユーザーに何を見せるかをコントロールできる。
 
-[カタログを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalog/)作成した後、Brazeのキャンペーンやレコメンデーションに選択項目を組み込むことで、カタログデータをさらに参照することができる。
+[カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalog/)を作成した後、Braze キャンペーンや推奨事項にセレクションを組み込むことで、カタログデータをさらに参照することができます。
 
-![カタログ例のセレクション・セクション。][1]
+![カタログ例の「セレクション」セクション。][1]
 
 ## 知っておくべきこと
 
-- カタログ1冊につき30セレクションまで作成できる。
-- セレクションは、ブレイズのカタログデータからおすすめを絞り込むのに最適だ。インスピレーションを得たいのであれば、使用例として[「About item recommendations」を]({{site.baseurl}}/user_guide/sage_ai/recommendations/about_item_recommendations/)チェックしてほしい。
+- カタログごとに最大 30 個のセレクションを作成できます。
+- セレクションは、Braze のカタログデータから推奨事項を絞り込むのに最適です。インスピレーションをお探しの場合、「[アイテムのおすすめについて]({{site.baseurl}}/user_guide/sage_ai/recommendations/about_item_recommendations/)」にあるユースケースの例を参照してください。
 
 ## セレクションを作成する
 
 セレクションを作成するには、以下のようにする。
 
-1. **カタログ**」を開き、リストから自分のカタログを選択する。
-2. **Selection**タブを選択し、**Create Selectionを**クリックする。
+1. \[**カタログ**] に移動し、リストからカタログを選択します。
+2. \[**セレクション**] タブを選択し、\[**セレクションを作成**] をクリックします。
 3. 選択範囲に名前と任意の説明を付ける。
 4. **Filter Field（フィルター・フィールド**）で、フィルターしたいカタログ・カラムを選択する。1,000文字を超える文字列フィールドはフィルターに選択できない。
 5. 関連する演算子（例えば "equals "や "doesn't equal"）と属性を選択して、フィルター基準の定義を終える。
-6. **Sort type**セクションで、結果のソート方法を決定する。デフォルトでは、結果は順不同で返される。特定のフィールドによるソートを指定するには、**Randomize Sort Orderを**オフにし、**Sort Fieldと** **Sort Order**（昇順または降順）を指定する。
+6. **Sort type**セクションで、結果のソート方法を決定する。デフォルトでは、結果は順不同で返されます。特定のフィールドによるソートを指定するには、**Randomize Sort Orderを**オフにし、**Sort Fieldと** **Sort Order**（昇順または降順）を指定する。
 7. **Results limit**セクションで、結果の最大数を50まで入力する。
-8. **選択範囲を作成**」をクリックする。
+8. \[**セレクションを作成**] をクリックします。
 
-### 選考結果が流動的
+### セレクション結果内の Liquid
 
-カスタム属性やカスタムイベントのようなカタログ内のリキッドを使用すると、選択したユーザーごとに異なる結果が返される可能性がある。
+カスタム属性やカスタムイベントなど任意のカタログ内で Liquid を使用すると、セレクションにあるユーザーごとに異なる結果が返される可能性があります。
 
 ![属性がリキッドカスタム属性に設定されているカタログ選択のフィルタ設定。][7]
 
 ## メッセージングで選択範囲を使用する
 
-セレクションを作成したら、リキッドでメッセージをパーソナライズし、そのカタログからフィルタリングされたアイテムを挿入する。Brazeは、メッセージコンポーザーにあるパーソナライズウィンドウからリキッドを生成させることができる：
+セレクションを作成したら、Liquid でメッセージをパーソナライズし、そのカタログからフィルタリングされた項目を挿入します。Braze を使用して、メッセージ作成画面にあるパーソナライゼーションウィンドウから Liquid を生成することができます。
 
 1. パーソナライズをサポートしているメッセージ作成ツールで <i class="fa-solid fa-circle-plus" style="color: #12aec5;" title="パーソナライズを追加する"></i>をクリックしてパーソナライズウィンドウを開く。
 2. **Personalization Type（パーソナライゼーション・タイプ）**」で「**Catalog Items（カタログ商品**）」を選択する。
 3. カタログ名を選択する。
 4. **項目選択方法]**で\[**選択項目を使用する**]を選択する。
-4. リストから選択する。
+4. リストからセレクションを選択します。
 5. **表示する情報**」では、カタログのどのフィールドを各アイテムに含めるかを選択する。
-6. **コピー」**アイコンをクリックし、メッセージ内の必要な場所にリキッドを貼り付ける。
+6. \[**コピー**] アイコンをクリックし、メッセージ内の必要な場所に Liquid を貼り付けます。
 
-![パーソナライゼーションの追加]モーダルで、以下の選択ができる：「パーソナライズ・タイプ」は「カタログ・アイテム」、「カタログ名」は「ゲーム」、「セレクション・タイプ」は「セレクション」、「セレクション」は「game_selection」、「表示する情報」は「title」と「description_ja」である。][6]{: style="max-width:70%;"}
+![以下のセレクションがある「パーソナライゼーションの追加」モーダル: 「パーソナライズ・タイプ」は「カタログ・アイテム」、「カタログ名」は「ゲーム」、「セレクション・タイプ」は「セレクション」、「セレクション」は「game_selection」、「表示する情報」は「title」と「description_ja」である。][6]{: style="max-width:70%;"}
 
 ## ユースケース
 
@@ -61,7 +61,7 @@ description: "この参考記事では、Brazeのキャンペーンでデータ
 
 ![食事宅配サービスの選択例で、2つのフィルターがある。1つは商品タイプを食事として識別するもの、もう1つはカテゴリーを最近閲覧されたものとして識別するものである。セレクションは、3つの結果が返される順番がランダムになるように設定されている。][2]{: style="max-width:90%;"}
 
-このカタログと選択をキャンペーンで使用するには、キャンペーンを構築する際のメッセージ構成セクションで**パーソナライゼーションの追加**モーダルを使用する。この例では、食事宅配サービスの情報が掲載されたカタログと、最近閲覧したカテゴリーに基づく食事の推薦を選択した。これにより、食事名と価格を表示することができる。さらにメッセージを構築するために、選択項目を使って最初のおすすめ料理の画像を追加することもできる。
+このカタログと選択をキャンペーンで使用するには、キャンペーンを構築する際のメッセージ構成セクションで**パーソナライゼーションの追加**モーダルを使用する。この例では、食事宅配サービスの情報が掲載されたカタログと、最近閲覧したカテゴリーに基づく食事の推薦を選択した。これにより、食事名と価格を表示することができます。メッセージをさらに構築するには、セレクションを使って最初のおすすめ料理の画像を追加することもできます。
 
 ![コンテンツカード。ヘッダーは「高評価の食事がきっと気に入るはず！」、メッセージの構成セクションは「recommendations_be_recent_category」を選択する。][3]{: style="max-width:90%;"}
 
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/using_catalogs.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/using_catalogs.md
index ea0e0cb95fe..8787d0e2311 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/using_catalogs.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/catalogs/using_catalogs.md
@@ -7,15 +7,15 @@ description: "この参考記事では、Liquidを通してBrazeのキャンペ
 
 # メッセージでカタログを使う
 
-> カタログを作成した後、[Liquidを通して]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid)Brazeキャンペーンで非ユーザーデータを参照できる。Liquidがサポートされているドラッグ・アンド・ドロップ・エディター内の任意の場所を含む、すべてのメッセージング・チャンネルでカタログを使用できる。
+> カタログを作成した後、[Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid) を使用して、Braze キャンペーンの非ユーザーデータを参照できます。Liquidがサポートされているドラッグ・アンド・ドロップ・エディター内の任意の場所を含む、すべてのメッセージング・チャンネルでカタログを使用できる。
 
-## ステップ 1:パーソナライゼーション・タイプを追加する {#step-one-personalization}
+## ステップ 1:パーソナライゼーションタイプを追加する {#step-one-personalization}
 
-選択したメッセージコンポーザーで、<i class="fas fa-plus-circle"></i> プラスアイコンを選択して**パーソナライズの追加**モーダルを開き、**パーソナライズのタイプに** **カタログアイテムを**選択する。次に、**カタログ名を**選択する。先ほどの例を使って、「ゲーム」カタログを選択する。
+選択したメッセージコンポーザーで、<i class="fas fa-plus-circle"></i> プラスアイコンを選択して**パーソナライズの追加**モーダルを開き、**パーソナライズのタイプに** **カタログアイテムを**選択する。次に、**カタログ名**を選択します。先ほどの例を使って、「ゲーム」カタログを選択する。
 
 ![][1]
 
-リキッドのプレビューはすぐに見ることができる：
+以下の Liquid プレビューがすぐに表示されます。
 
 {% raw %}
 ```liquid
@@ -25,9 +25,9 @@ description: "この参考記事では、Liquidを通してBrazeのキャンペ
 
 ## ステップ 2:カタログ項目を選択する
 
-次に、カタログ項目を追加する番だ！ドロップダウンを使って、カタログ項目と表示する情報を選択する。この情報は、カタログを生成するために使用される、アップロードされたCSVファイルの列に対応している。
+ここではカタログアイテムを追加します。ドロップダウンを使って、カタログ項目と表示する情報を選択する。この情報は、カタログを生成するために使用される、アップロードされたCSVファイルの列に対応している。
 
-例えば、『テイルズ』ゲームのタイトルと価格を参照するには、カタログ項目として『テイルズ』の`id` （1234）を選択し、表示される情報に対して`title` 、`price` 。
+例えば、Tales ゲームのタイトルと価格を参照するには、カタログアイテムとして Tales (1234) の `id` を選択し、表示される情報に対して `title` と `price` をリクエストします。
 
 {% raw %}
 ```liquid
@@ -39,7 +39,7 @@ Get {{ items[0].title }} for just {{ items[0].price }}!
 
 これは次のように表示される：
 
-> テイルズ』をわずか7.49ドルで手に入れよう！
+> 「Tales」をわずか 7.49 ドルでゲットしよう!
 
 ## その他の使用例
 
@@ -47,11 +47,11 @@ Get {{ items[0].title }} for just {{ items[0].price }}!
 
 1つのメッセージに含まれる項目は1つに限定されない！**パーソナライズの追加]**モーダルを使用して、表示する追加カタログ項目と情報を挿入するだけである。なお、追加できるカタログ項目は3つまでである。 
 
-この例をチェックしてください。3つのゲーム、Tales、Teslagrad、Acaratusの`id`を**カタログ**アイテムに追加し、**表示する情報**のために`title`を選択します。
+この例では、Tales、Teslagrad、Acaratus の 3 つのゲームの `id` を**カタログアイテム**に追加し、[**表示する情報**] のために `title` を選択します。
 
 ![][2]{: style="max-width:70%" }
 
-リキッドの周りにテキストを追加することで、メッセージをさらにパーソナライズすることができる：
+Liquid の周りにテキストを追加することで、メッセージをさらにパーソナライズできます。
 
 {% raw %}
 ```liquid
@@ -62,17 +62,17 @@ Get the ultimate trio {% catalog_items games 1234 1235 1236 %}
 
 これは以下のように返される：
 
-> 究極のトリオ「テイルズ」、「テスラグラッド」、「アカラタス」を今すぐ手に入れよう！
+> 究極のトリオ「Tales」、「Teslagrad」、「Acaratus」を今すぐゲット!
 
 {% alert tip %}
-よりパーソナライズされたメッセージングのために、データのグループを作成するための[選択を]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)チェックする！
+さらにパーソナライズされたメッセージングのために、データグループを作成するには、[セレクション]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)を参照してください。
 {% endalert %}
 
 ### リキッド`if` ステートメントを使用する
 
-カタログ項目を使って条件文を作ることができる。例えば、キャンペーンで特定のアイテムが選択されたときに、特定のメッセージを表示させることができる。
+カタログ項目を使って条件文を作ることができる。例えば、キャンペーンで特定の項目が選択されたときに、特定メッセージの表示をトリガーできます。
 
-そのためには、リキッド`if` ：
+これを行うには、次のような形式で Liquid の `if` ステートメントを使用します。
 
 {% raw %}
 ```liquid
@@ -85,11 +85,11 @@ Do that
 ```
 {% endraw %}
 
-カタログ・リストを宣言してから、`if` 。上の例では、`Test-list` がカタログ・リストである。
+`if` ステートメントを使用する前に、カタログリストを宣言する必要があることに注意してください。上の例では、`Test-list` がカタログ・リストである。
 
-#### ユースケース:リキッド`if` スニペット
+#### ユースケース:Liquid の `if` スニペット
 
-このシナリオでは、カスタム属性`venue_name` の文字数が10文字以上か10文字未満かで、異なるメッセージが表示される。`venue_name` が`blank` の場合、何も表示されない。
+このシナリオでは、カスタム属性`venue_name` の文字数が10文字以上か10文字未満かで、異なるメッセージが表示される。`venue_name` が `blank` の場合、何も表示されません。
 
 {% raw %}
 ```liquid
@@ -104,11 +104,11 @@ Message if the venue name's size is less than 10 characters.
 ```
 {% endraw %}
 
-### 画像を使用する {#using-images}
+### 画像の使用 {#using-images}
 
-また、カタログの画像を参照してメッセージに使用することもできる。そのためには、画像のリキッドフィールドで`catalogs` タグと`item` オブジェクトを使う。
+また、カタログ内の画像を参照してメッセージングで使用することもできます。そのためには、画像のリキッドフィールドで`catalogs` タグと`item` オブジェクトを使う。
 
-例えば、「テイルズ」のプロモーション・メッセージに「ゲーム」カタログの`image_link` を追加するには、「**カタログ項目**」フィールドに`id` を、「**表示する情報」**フィールドに`image_link` を選択する。これにより、以下のリキッドタグが画像フィールドに追加される：
+例えば、Games カタログの `image_link` を「Tales」のプロモーションメッセージに追加するには、[**カタログ項目**] フィールドで `id` を選択し、\[**表示する情報**] フィールドで `image_link` を選択します。これにより、以下のリキッドタグが画像フィールドに追加される：
 
 {% raw %}
 ```liquid
@@ -118,15 +118,15 @@ Message if the venue name's size is less than 10 characters.
 ```
 {% endraw %}
 
-![コンテンツカードコンポーザーで、画像フィールドにカタログのリキッドタグが使用されている。][3]
+![画像フィールドで使用されるカタログの Liquid タグを含むコンテンツカード作成画面。][3]
 
-リキッドがレンダリングされるとこうなる：
+Liquid がレンダリングされると、次のように表示されます。
 
 ![カタログのリキッドタグをレンダリングしたコンテンツカードの例。][4]{: style="max-width:50%" }
 
 ### カタログ項目をテンプレート化する
 
-また、テンプレート化を使って、カスタム属性に基づいてカタログ項目を動的に引き出すこともできる。たとえば、あるユーザーがカスタム属性`wishlist` （カタログのゲームIDの配列）を持っているとする。
+また、テンプレート化を使って、カスタム属性に基づいてカタログ項目を動的に引き出すこともできる。例えば、あるユーザーがカスタム属性`wishlist` （カタログのゲームIDの配列）を持っているとする。
 
 ```json
 {
@@ -139,13 +139,13 @@ Message if the venue name's size is less than 10 characters.
 }
 ```
 
-リキッドテンプレートを使えば、ウィッシュリストのIDを動的に引き出し、メッセージの中で使うことができる。そのためには、\[変数][10] をカスタム属性に割り当て、**パーソナライゼーションの追加**モーダルを使用して、配列から特定のアイテムを取り出す。
+Liquid テンプレートを使用することで、ウィッシュリストから ID をダイナミックに取り出し、メッセージで使用できます。そのためには、\[変数][10] をカスタム属性に割り当て、**パーソナライゼーションの追加**モーダルを使用して、配列から特定のアイテムを取り出す。
 
 {% alert tip %}
 配列は`1` ではなく`0` から始まることを忘れないでほしい。
 {% endalert %}
 
-例えば、「テイルズ」（カタログに掲載されている、ユーザーが欲しいと思っている商品）がセール中であることをユーザーに知らせるには、メッセージ・コンポーザーに次のように追加すればいい：
+例えば、「Tales」(ウィッシュリストに含まれている、御社カタログの項目) が販売中であることをユーザーに通知するために、メッセージ作成画面で以下を追加できます。
 
 {% raw %}
 ```liquid
@@ -157,20 +157,20 @@ Get {{ items[0].title }} now, for just {{ items[0].price }}!
 {% endraw %}
 
 以下のように表示される：
-> たった7.49ドルで、今すぐ『テイルズ』を手に入れよう！
+> 「Tales」をわずか 7.49 ドルで今すぐゲットしよう!
 
 テンプレート化により、各ユーザーのカスタム属性、イベントプロパティ、その他のテンプレート化可能なフィールドに基づいて、各ユーザーに異なるカタログ項目をレンダリングすることができる。
 
 ### CSVをアップロードする
 
-追加する新しいカタログ項目や更新するカタログ項目のCSVをアップロードできる。アイテムのリストを削除するには、アイテムIDのCSVをアップロードして削除する。
+追加する新しいカタログ項目や、更新するカタログ項目の CSV をアップロードできます。アイテムのリストを削除するには、アイテムIDのCSVをアップロードして削除する。
 
-### 液体の使用
+### Liquid の使用
 
-また、リキッドロジックのカタログを手作業で組み合わせることもできる。ただし、存在しないIDを入力しても、Brazeはオブジェクトのないitems配列を返すことに注意。配列のサイズをチェックしたり、`if` ステートメントを使用して配列が空の場合を考慮するなど、エラー処理を含めることを推奨する。
+Liquid ロジックを手動で作成することもできます。ただし、存在しないIDを入力しても、Brazeはオブジェクトのないitems配列を返すことに注意。配列のサイズをチェックしたり、`if` ステートメントを使用して配列が空の場合を考慮するなど、エラー処理を含めることを推奨する。
 
 {% alert note %}
-リキッドは現在、カタログ内で使用することはできない。リキッドパーソナライゼーションがカタログのセル内にリストされている場合、ダイナミック値はレンダリングされず、実際のリキッドのみが表示される。
+現在、カタログ内で Liquid を使用することはできません。リキッドパーソナライゼーションがカタログのセル内にリストされている場合、ダイナミック値はレンダリングされず、実際のリキッドのみが表示される。
 {% endalert %}
 
 
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/connected_content/connected_content_retries.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/connected_content/connected_content_retries.md
index 067113dbd16..bbded93005e 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/connected_content/connected_content_retries.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/connected_content/connected_content_retries.md
@@ -1,16 +1,16 @@
 ---
-nav_title: 接続コンテンツの再試行
-article_title: 接続コンテンツの再試行
+nav_title: コネクテッドコンテンツの再試行
+article_title: コネクテッドコンテンツの再試行
 page_order: 3
-description: "この参考記事では、コネクテッド・コンテンツの再試行に対処する方法を取り上げている。"
+description: "この記事では、コネクテッドコンテンツの再試行に対処する方法を説明します。"
 
 ---
 
-# コネクテッド・コンテンツの再試行
+# コネクテッドコンテンツの再試行
 
-> Connected ContentはAPIからのデータ受信に依存しているため、Brazeがコールしている間、APIが断続的に利用できない可能性がある。この場合、Brazeは指数バックオフを使用してリクエストを再試行するリトライロジッ クをサポートする。 
+> コネクテッドコンテンツは API からのデータ受信に依存するため、Braze が呼び出しを処理する間、API が断続的に利用できなくなる可能性があります。その場合、Braze は指数バックオフを使用してリクエストを再試行する、再試行ロジックをサポートしています。 
 
-再試行を有効にするには、次のコード・スニペットに示すように、Connected Content呼び出しに`:retry` ：
+再試行を有効にするには、次のコードスニペットにあるように、コネクテッドコンテンツ呼び出しに `:retry` を追加します。
 {% raw %}
 ```
 {% connected_content https://yourwebsite.com/api/endpoint :retry %}
@@ -20,10 +20,10 @@ description: "この参考記事では、コネクテッド・コンテンツの
 
 APIコールが失敗し、これが有効になっている場合、Brazeは、各再送に設定した[レート制限を][47]尊重しながら、コールを再試行する。Brazeは、失敗したメッセージをキューの最後尾に移動させ、必要であれば、メッセージ送信にかかる総時間をさらに数分追加する。
 
-再試行が成功した場合、そのメッセージは送信され、以後そのメッセージの再試行は行われない。Connected Content呼び出しが5回エラーになった場合、メッセージは、[中止メッセージタグが][1]トリガーされた場合と同様に、中止される。
+再試行が成功した場合、そのメッセージは送信され、以後そのメッセージの再試行は行われない。コネクテッドコンテンツ呼び出しが 5 回エラーになった場合、メッセージは、[メッセージ中止タグ][1]がトリガーされた場合と同様に中止されます。
 
 {% alert note %}
-Connected Content`:retry` はアプリ内メッセージでは利用できない。
+コネクテッドコンテンツ `:retry` は、アプリ内メッセージでは利用できません。
 {% endalert %}
 
 
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call.md
index c3f34efbe1d..6b6a7c83a6c 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call.md
@@ -2,21 +2,21 @@
 nav_title: API コールの実行
 article_title: 接続されたコンテンツAPI コールの実行
 page_order: 0
-description: "このリファレンス記事では、Connected Content API 呼び出しの方法、役立つサンプル、高度なConnected Content ユースケースについて説明します。"
+description: "この記事では、コネクテッドコンテンツ API 呼び出しを行う方法と、役立つサンプル、および高度なコネクテッドコンテンツのユースケースについて説明します。"
 search_rank: 2
 ---
 
 # [![Brazeラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/connected-content){: style="float:right;width:120px;border:0;" class="noimgborder"}API 呼び出し
 
-> 接続コンテンツを使用して、ユーザー s に送信するメッセージにAPI を介して直接アクセス可能な情報を挿入します。Web サーバーから直接、またはパブリックにアクセス可能なAPI からコンテンツをプルできます。
+> コネクテッドコンテンツを使用して、ユーザーに送信するメッセージに API を介して直接アクセス可能な情報を挿入します。Web サーバーから直接、またはパブリックにアクセス可能な API からコンテンツをプルできます。
 
-## 接続内容タグ
+## コネクテッドコンテンツタグ
 
 {% raw %}
 
-接続内容呼び出しを送信するには、`{% connected_content %}` タグを使用します。このタグでは、`:save` を使用して変数を割り当てたり宣言したりできます。これらの変数の側面は、メッセージの後で[Liquid][2] で参照できます。
+コネクテッドコンテンツ呼び出しを送信するには、`{% connected_content %}` タグを使用します。このタグでは、`:save` を使用して変数を割り当てたり宣言したりできます。これらの変数の内容には、メッセージの後の方で [Liquid][2] を使って参照できます。
 
-たとえば、次のメッセージ本文は、URL `http://numbersapi.com/random/trivia` にアクセスし、メッセージに面白いトライビアファクトを含めます。
+たとえば、次のメッセージ本文は、`http://numbersapi.com/random/trivia` という URL にアクセスし、メッセージに楽しいトライビアを含めます。
 
 ```
 {% connected_content http://numbersapi.com/random/trivia :save result %}
@@ -25,9 +25,9 @@ Hi there, here is fun some trivia for you!: {{result.text}}
 
 ### 変数の追加
 
-また、接続コンテンツリクエストを作成するときに、URL 文字列に変数としてユーザープロファイル 属性s を含めることもできます。 
+また、コネクテッドコンテンツリクエストを作成するときに、URL 文字列に変数としてユーザープロファイル 属性を含めることもできます。 
 
-たとえば、ユーザーのメールの住所とID に基づいてコンテンツを返すウェブサービスがあるとします。アットマーク(@) などの特殊文字を含む属性s を渡す場合は、URL で許可されていない文字をURL フレンドリエスケープバージョンで置き換えるために、リキッドフィルター`url_param_escape` を使用するようにしてください(次のメール住所属性を参照)。
+たとえば、ユーザーのメールの住所とID に基づいてコンテンツを返すウェブサービスがあるとします。アットマーク (@) などの特殊文字を含む属性を渡す場合は、URL で使用できない文字を URL フレンドリなエスケープバージョンで置き換えるために、Liquid フィルター `url_param_escape` を必ず使用してください (次のメールアドレス属性を参照)。
 
 ```
 Hi, here are some articles that you might find interesting:
@@ -36,7 +36,7 @@ Hi, here are some articles that you might find interesting:
 ```
 {% endraw %}
 {% alert note %}
-Liquid 構文のバージョン内で適切に動作するには、属性値を`${}` で囲む必要があります。
+Liquid 構文のバージョン内で適切に動作するには、属性値を `${}` で囲む必要があります。
 {% endalert %}
 
 接続コンテンツリクエストは、GET およびPOST リクエストのみをサポートします。
@@ -45,26 +45,26 @@ Liquid 構文のバージョン内で適切に動作するには、属性値を`
 
 URL が使用できず、404 ページに達すると、Braze はその場所に空の文字列を表示します。URL がHTTP 500 または502 ページに達すると、URL は再試行ロジックで失敗します。
 
-エンドポイントがJSON を返す場合は、`connected` の値がnull であるかどうかを確認して、[条件付きでメッセージ][1] を中止することで、そのことを検出できます。Braze では、ポート80 (HTTP) と443 (HTTPS) を介して通信するURL のみが許可されます。
+エンドポイントがJSON を返す場合は、`connected` の値がnull であるかどうかを確認して、[条件付きでメッセージ][1] を中止することで、そのことを検出できます。Braze では、ポート 80 (HTTP) と 443 (HTTPS) を介して通信する URL のみが許可されます。
 
 ## パフォーマンス
 
-Braze はメッセージを非常に高速で配信するため、サーバーが数千の同時接続を処理できるようにして、コンテンツをプルダウンするときにサーバーが読み込むを乗り越えないようにしてください。パブリックAPI を使用する場合は、API プロバイダーが使用するレート制限に違反しないように使用してください。Braze では、パフォーマンス上の理由からサーバーの応答時間が2 秒未満である必要があります。サーバーの応答時間が2 秒を超えると、その内容は挿入されません。
+Braze はメッセージを非常に高速で配信するため、サーバーが数千の同時接続を処理できるようにして、コンテンツをプルダウンするときにサーバーが過負荷状態にならないようにしてください。パブリック API を使用する場合は、API プロバイダーが使用するレート制限に違反しないように使用してください。Braze では、パフォーマンス上の理由からサーバーの応答時間が2 秒未満である必要があります。サーバーの応答時間が2 秒を超えると、その内容は挿入されません。
 
-Brazeは、1受信者に複数回、同じConnected Content API呼び出しを行うことができます。これは、Braze がメッセージペイ読み込むを表示するために接続コンテンツAPI 呼び出しを行う必要がある場合があるためです。また、メッセージペイ読み込むは、検証、再試行ロジック、または他の内部のために、受信者ごとに複数回レンダリングできます。1受信者に1回以上、同じ接続内容の呼び出しを許容できる必要があります。
+Braze は、各受信者に複数回、同じコネクテッドコンテンツ API 呼び出しを行うことができます。これは、状況によっては Braze がメッセージペイロードを表示するためにコネクテッドコンテンツ API 呼び出しを行う必要があり、メッセージペイロードは、検証、再試行ロジック、またはその他の内部目的のために、受信者ごとに複数回レンダリングされることがあるためです。システムは、各受信者につき複数回、同じコネクテッドコンテンツ API 呼び出しの処理を行わなければなりません。
 
 ## 知っておくべきこと
 
-* Braze はAPI コールの料金を請求せず、指定されたデータポイント割り当てにはカウントされません。
-* Connected Content レスポンスには1MB の制限があります。
-* 接続されたコンテンツコールは、メッセージが送信されるとh をアプリします。ただし、アプリ内メッセージs は、メッセージが表示されたときにこのコールを発信します。
-* 接続されたコンテンツコールはリダイレクトに従いません。
+* Braze は API 呼び出しについて課金せず、指定のデータポイント割り当てにはカウントされません。
+* コネクテッドコンテンツ応答には 1 MB の制限があります。
+* コネクテッドコンテンツ呼び出しは、メッセージの送信時に行われます。ただし、アプリ内メッセージは、メッセージが表示されたときにこの呼び出しを行います。
+* コネクテッドコンテンツ呼び出しはリダイレクトに従いません。
 
 ## 認証タイプ
 
 ### 基本認証の使用
 
-URL に基本的な認証が必要な場合、Braze はAPI 呼び出しで使用するための基本的な認証 認証情報を生成できます。既存の基本認証 認証情報s を管理し、**Settings**> **Connected Content** から新しいものを追加できます。
+URL に基本的な認証が必要な場合、Braze は API 呼び出しで使用するための基本的な認証情報を生成できます。既存の基本的な認証情報を管理したり、\[**設定**] > \[**コネクテッドコンテンツ**] から新しいものを追加したりできます。
 
 {% alert note %}
 [古いナビゲーション]({{site.baseurl}}/navigation) を使用している場合、**Connected Content** は**設定の管理** にあります。
@@ -76,7 +76,7 @@ URL に基本的な認証が必要な場合、Braze はAPI 呼び出しで使用
 
 ![][35]{: style="max-width:30%" }
 
-次に、トークンの名前を参照することで、API 呼び出しでこの基本認証 認証情報を使用できます。
+次に、トークンの名前を参照することで、API 呼び出しでこの基本的な認証情報を使用できます。
 
 {% raw %}
 ```
@@ -85,12 +85,12 @@ Hi there, here is fun some trivia for you!: {% connected_content https://yourweb
 {% endraw %}
 
 {% alert note %}
-認証情報を削除する場合、使用しようとしている接続コンテンツコールはすべて中止されることに注意してください。
+認証情報を削除する場合、これを使用しようとしているコネクテッドコンテンツ呼び出しはすべて中止されることに注意してください。
 {% endalert %}
 
 ### トークン 認証の使用
 
-Braze 接続コンテンツを使用する場合、特定のAPI では、ユーザーの名前とパスワードの代わりにトークンが必要になることがあります。次の呼び出しに含まれているのは、メッセージをリファレンスし、モデル化するためのコードな抜粋です。
+Braze コネクテッドコンテンツを使用する場合、特定の API では、ユーザー名とパスワードの代わりにトークンが必要になることがあります。次の呼び出しに含まれているのは、メッセージを参照し、それをメッセージのモデルとして使用するためのコードスニペットです。
 
 {% raw %}
 ```
@@ -111,11 +111,11 @@ Braze 接続コンテンツを使用する場合、特定のAPI では、ユー
 
 ### オープン認証(OAuth)の使用
 
-一部のAPI 設定では、アクセスするAPI エンドポイントの認証に使用できるアクセストークンを取得する必要があります。
+一部の API 設定では、アクセスする API エンドポイントの認証に使用できるアクセストークンを取得する必要があります。
 
-#### 接続トークンを取得する
+#### アクセストークンを取得する
 
-次の例は、アクセストークンを取得してローカル変数に保存し、後続のAPI 呼び出しの認証に使用できるようにする方法を示しています。`:cache_max_age`パラメータを追加して、アクセストークンが有効な時刻を照合し、発信接続コンテンツコールの回数を減らすことができます。詳細については、\[構成可能なキャッシュ][36]] を参照してください。
+次の例は、アクセストークンを取得してローカル変数に保存し、後続の API 呼び出しの認証に使用できるようにする方法を示しています。パラメーター `:cache_max_age` を追加して、アクセストークンの有効期間を照合し、アウトバウンドコネクテッドコンテンツ呼び出しの回数を減らすことができます。詳細については、\[構成可能なキャッシュ][36] を参照してください。
 
 {% raw %}
 ```
@@ -132,9 +132,9 @@ Braze 接続コンテンツを使用する場合、特定のAPI では、ユー
 ```
 {% endraw %}
 
-#### 取得したアクセストークンを使用してAPI を許可する
+#### 取得したアクセストークンを使用して API を承認する
 
-これでトークンが保存されたので、dをダイナミックな接続内容呼び出しにテンプレートして、リクエストを承認できます。
+これでトークンが保存されたので、これをダイナミックなコネクテッドコンテンツ呼び出しにテンプレート化して、リクエストを承認できます。
 
 {% raw %}
 ```
@@ -150,15 +150,15 @@ Braze 接続コンテンツを使用する場合、特定のAPI では、ユー
 ```
 {% endraw %}
 
-## 接続されたコンテンツIP の許可
+## コネクテッドコンテンツ IP の許可リスト
 
-Brazeサーバーは、Connected Contentを使用したメッセージをBrazeから送信すると、自動的に顧客またはサードパーティのサーバーにネットワークリクエストを行い、データをプルバックします。IP allowlisting を使用すると、Connected Content リクエストが実際にBraze から送信されていることを確認し、セキュリティレイヤーを追加できます。
+コネクテッドコンテンツを使用したメッセージが Braze から送信されると、Braze サーバーは、自動的に顧客またはサードパーティのサーバーにネットワークリクエストを行い、データをプルバックします。IP 許可リストを使用すると、コネクテッドコンテンツリクエストが実際に Braze から送信されていることを確認し、セキュリティレイヤーを追加することができます。
 
-Braze は、次のIP 範囲から接続コンテンツリクエストを送信します。リストされている範囲は自動的に追加され、allowlisting にオプトインされているすべてのAPI キーにダイナミックな追加されます。 
+Braze は、次のIP 範囲から接続コンテンツリクエストを送信します。リストされている範囲は自動的に追加され、許可リストにオプトインされているすべての API キーにダイナミックに追加されます。 
 
-Braze には、すべてのサービスに使用される予約のIP があります。すべてのIP が一度に有効になるわけではありません。これは、Brazeが別のデータセンタから送信したり、保守を行ったりするために、顧客に影響を与えることなく設計されています。Brazeは、接続コンテンツリクエストを作成するときに、以下のIPの1つ、サブセット、またはすべてを使用できます。
+Braze には、すべてのサービスに使用される一連の予約済み IP があります。これらの ＩＰ はすべて一度にアクティブになるわけではありません。これは、Braze が別のデータセンターから送信したり、保守を行ったりするために、顧客に影響を与えないように設計されています。Braze は、コネクテッドコンテンツリクエストを作成するときに、以下の IP のいずれか 1 つ、サブセット、またはすべてを使用できます。
 
-| インスタンス`US-01`、`US-02`、`US-03`、`US-04`、`US-05`、`US-06`、`US-07`: |
+| インスタンス `US-01`、`US-02`、`US-03`、`US-04`、`US-05`、`US-06`、`US-07` の場合:  |
 |---|
 | `23.21.118.191`
 | `34.206.23.173`
@@ -204,12 +204,12 @@ Braze には、すべてのサービスに使用される予約のIP があり
 
 ## トラブルシューティング
 
-接続コンテンツコールのトラブルシューティングには、[Webhook.site](https://webhook.site/) を使用します。 
+コネクテッドコンテンツ呼び出しのトラブルシューティングには、[Webhook.site](https://webhook.site/) を使用します。 
 
-1. Connected Content コールのURL をサイトで生成された一意のURL に切り替えます。
-2. キャンペーンまたはキャンバスステップをプレビューしてテストし、リクエストがこのWeb サイトを通過するかどうかを確認します。
+1. コネクテッドコンテンツ呼び出しの URL を、サイトで生成された一意の URL に切り替えます。
+2. キャンペーンまたはキャンバスステップをプレビューしてテストし、リクエストがこの Web サイトを介して処理されることを確認します。
 
-このツールを使用して、リクエストヘッダーs、リクエストボディ、およびコールで送信されている他の情報に関する問題を診断できます。
+このツールを使用して、リクエストヘッダー、リクエスト本文、および呼び出しで送信される他の情報に関する問題を診断できます。
 
 [1]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/aborting_connected_content/
 [2]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/using_liquid/#liquid-usage-use-cases--overview
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/deep_linking_to_in-app_content.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/deep_linking_to_in-app_content.md
index f9d5e296f75..b6ded805b4b 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/deep_linking_to_in-app_content.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/deep_linking_to_in-app_content.md
@@ -2,7 +2,7 @@
 nav_title: アプリ内コンテンツへのディープリンク
 article_title: アプリ内コンテンツへのディープリンク
 page_order: 3
-description: "この参考記事では、アプリ内のメッセージコンテンツにディープリンクを追加する方法について解説している。"
+description: "この記事では、アプリ内メッセージのコンテンツにディープリンクを追加する方法について説明します。"
 
 ---
 
@@ -10,17 +10,17 @@ description: "この参考記事では、アプリ内のメッセージコンテ
 
 ## ディープリンクとは何か？
 
-ディープリンクは、ネイティブアプリを起動し、特定のアクションを実行したり、特定のコンテンツを表示したりするよう指示する追加情報を提供する方法だ。
+ディープリンクは、ネイティブアプリを起動し、特定のアクションを実行したり、特定のコンテンツを表示したりするように指示する追加情報を提供する方法です。
 
-これには3つの部分がある：
+これには 3 つの部分があります。
 
 1. 起動するアプリを特定する
 2. どのアクションを実行するかをアプリに指示する
 3. アクションが必要とする追加データを提供する。
 
-ディープリンクは、アプリの特定の部分にリンクするカスタムURIで、これら3つの部分すべてを含む。重要なのは、カスタムスキームを定義することである。`http:` はほとんど誰もが知っているスキームだが、スキームはどんな単語でも始めることができる。スキームは文字で始まらなければならないが、文字、数字、プラス記号、マイナス記号、ドットを含むことができる。現実的に言えば、競合を防ぐための中央レジストリは存在しないので、ドメイン名をスキームに含めるのがベストプラクティスである。例えば、`twitter://` は、X（旧ツイッター）のモバイルアプリを起動するためのiOS URIである。
+ディープリンクは、アプリの特定の部分にリンクするカスタムURIで、これら3つの部分すべてを含む。キーは、カスタムスキームを定義することです。`http:` は、ほとんどの人が慣れ親しんでいるスキームですが、スキームは任意の単語から始めることができます。スキームは文字で始める必要がありますが、文字、数字、プラス記号、マイナス記号、ドットを含むことができます。現実的に言えば、競合を防ぐための中央レジストリは存在しないので、ドメイン名をスキームに含めるのがベストプラクティスである。例えば、`twitter://` は、X (旧称ツイッター) のモバイルアプリを起動するための iOS 用 URI です。
 
-ディープリンク内のコロン以降はすべて自由形式のテキストである。その構造と解釈を定義するのはあなた次第だが、一般的な慣例としては、先頭の`//` とクエリーパラメーター（例えば、`?foo=1&bar=2` ）を含む、`http:` URLをモデルにしている。先ほどの例では、`twitter://user?screen_name=[id]` 、アプリ内の特定のプロフィールを起動するために使われる。
+ディープリンク内のコロン以降はすべて自由形式のテキストである。その構造と解釈の定義はユーザー次第です。`http:` URL の後に、先頭の `//` とクエリパラメーター (`?foo=1&bar=2` など) を含めて、モデル化するのが一般的な方法です。先ほどの例では、`twitter://user?screen_name=[id]` 、アプリ内の特定のプロフィールを起動するために使われる。
 
 {% alert important %}
 Brazeは、Flutterのようなラッパーを使ってディープリンクを送信することはサポートしていない。この機能を使うには、ネイティブ層でディープリンクを設定する必要がある。
@@ -33,8 +33,8 @@ Brazeは、Flutterのようなラッパーを使ってディープリンクを
 
 [UTM（Urchin Traffic Manager）タグを][4]使えば、キャンペーンのアトリビューションの詳細をリンクに直接含めることができる。UTMタグは、Googleアナリティクスがキャンペーンのアトリビューションデータを収集するために使用され、以下のプロパティを追跡するために使用することができる：
 
-- `utm_source`トラフィックの送信元の識別子（たとえば、`my_app` ）。
-- `utm_medium`キャンペーン媒体（例えば、`newsfeed` ）。
+- `utm_source`: トラフィックの送信元の識別子 (`my_app` など)
+- `utm_medium`: キャンペーンメディア (`newsfeed` など)
 - `utm_campaign`: キャンペーンの識別子（例えば、`spring_2016_campaign` ）。
 - `utm_term`: ユーザーをアプリやウェブサイトに導いた有料検索キーワードの識別子（例：`pizza` ）。
 - `utm_content`: ユーザーがクリックした特定のリンク/コンテンツの識別子（例えば、`toplink` または`android_iam_button2` ）。
@@ -45,11 +45,11 @@ UTMタグは、通常のHTTP（ウェブ）リンクとディープリンクの
 
 通常のHTTP（ウェブ）リンクでUTMタグを使いたい場合（例えば、メールキャンペーンのアトリビューションを行う場合など）、すでにGoogleアナリティクスを使用している組織では、[GoogleのURLビルダーを使って][6]UTMリンクを生成するだけでよい。これらのリンクは、他のリンクと同様に、Brazeのキャンペーンコピーに簡単に埋め込むことができる。
 
-アプリへのディープリンクでUTMタグを使用するには、アプリに関連する[GoogleアナリティクスSDKが][5]統合され、[ディープリンクを処理するように正しく設定されて][7]いる必要がある。不明な点は開発者に確認すること。
+アプリへのディープリンクで UTM タグを使用するには、アプリに適切な [Google Analytics SDK][5] が統合され、[ディープリンクを処理するように正しく設定][7]されている必要があります。不明な点は開発者に確認すること。
 
 アナリティクスSDKを統合して設定すれば、BrazeのキャンペーンでUTMタグをディープリンクで使用できる。キャンペーンにUTMタグを設定するには、宛先URLまたはディープリンクに必要なUTMタグを含めるだけでよい。以下の例は、プッシュ通知やアプリ内メッセージでUTMタグを使う方法を示している。
 
-#### UTMタグでプッシュオープンをアトリビュートする
+#### UTM タグによるプッシュ開封のアトリビュート指定
 
 プッシュ通知用のディープリンクにUTMタグを含めるには、プッシュメッセージのクリック時の動作をディープリンクに設定し、ディープリンクのアドレスを記述し、以下の方法で目的のUTMタグを含めるだけでよい：
 
@@ -59,7 +59,7 @@ myapp://products/20-gift-card?utm_source=my_app&utm_medium=push&utm_campaign=spr
 
 ![][8]
 
-#### UTMタグでアプリ内メッセージのクリックをアトリビュートする
+#### UTM タグによるアプリ内メッセージのクリックのアトリビュート指定
 
 アプリ内メッセージに含まれるディープリンクには、以下の方法でUTMタグを含めることができる。
 
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid.md
index 47be03af2e2..9b3fa75c882 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid.md
@@ -5,12 +5,12 @@ page_order: 0
 layout: dev_guide
 search_rank: 3
 guide_top_header: "液体タグを使用したカスタマイズ"
-guide_top_text: "Braze は、指定されたユーザーの値を自動的にメッセージに置き換えます。中括弧の2組の内側に式を置き、補間値を使用していることをBrazeに通知します。これらの括弧内では、置換するユーザーの数値は、先頭にドル記号を付けた括弧で囲む必要があります。<br><br>Liquidの詳細については、ガイド付きの<b><a href='https://learning.braze.com/path/dynamic-personalization-with-liquid'>Liquid</a></b>Braze 学習 パスでダイナミックパーソナライゼーションをご覧ください!"
-description: "このランディングページでは、サポートされているパーソナライゼーション タグs、フィルターs、設定 デフォルトバリューなど、リキッドのすべてを網羅しています。"
+guide_top_text: "Braze は、指定されたユーザーの値を自動的にメッセージに置き換えます。中括弧の2組の内側に式を置き、補間値を使用していることをBrazeに通知します。これらの括弧内では、置換するユーザー値は、先頭にドル記号を付けた追加の括弧で囲む必要があります。<br><br>Liquid の詳細については、Braze Learning のガイド付きの「<b><a href='https://learning.braze.com/path/dynamic-personalization-with-liquid'>Liquid のダイナミックパーソナライゼーション</a></b>」の Braze 学習パスをご覧ください。"
+description: "このランディングページでは、サポートされているパーソナライゼーションタグ、フィルター、デフォルト値の設定など、Liquid のすべてを網羅しています。"
 
 guide_featured_title: "セクションの記事"
 guide_featured_list:
-- name: 液体の使用
+- name: Liquid の使用
   link: /docs/user_guide/personalization_and_dynamic_content/liquid/using_liquid/
   image: /assets/img/braze_icons/beaker-02.svg
 - name: サポートされているカスタマイズタグ
@@ -34,7 +34,7 @@ guide_featured_list:
 - name: メッセージの中止
   link: /docs/user_guide/personalization_and_dynamic_content/liquid/aborting_messages/
   image: /assets/img/braze_icons/refresh-ccw-01.svg
-- name: 液体使用例
+- name: Liquid のユースケース
   link: /docs/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases/
   image: /assets/img/braze_icons/list.svg
 - name: よくある質問
@@ -43,27 +43,27 @@ guide_featured_list:
   
 ---
 
-## 液体について
+## Liquid について
 
-> Liquidは、Shopifyが開発し、ルビーで書かれた開封ソースのテンプレート語です。Brazeでは、リキッドを使用してユーザーのプロファイルからデータをメッセージにテンプレートします。 
+> Liquid は、Shopify が開発した Ruby で書かれているオープンソースのテンプレート言語です。Braze では、Liquid を使用してユーザーのプロファイルからデータをメッセージにテンプレート化します。 
 
-たとえば、整数データタイプのユーザープロファイルからカスタム属性を取得し、その値を最も近い整数に丸めることができます。リキッドのシンタックスと使用方法については、[**対応パーソナライゼーション タグs**][1]を参照してください。
+例えば、整数データ型のユーザープロファイルからカスタム属性を取得し、その値を最も近い整数に丸めることができます。Liquid の構文と使用方法については、[**サポートされているパーソナライゼーションタグ**][1]を参照してください。
 
 リキッドテンプレーティング言語は、オブジェクト、タグs、およびフィルターs の使用をサポートします。
 
 - [**オブジェクト**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/)を使用すると、メッセージにパーソナライズされた 属性sを挿入できます。
-- [**タグ**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/)を使用すると、メッセージングにデータを挿入し、アウトライン条件が満たされている場合に条件ロジックを使用してメッセージを送信できます。たとえば、タグsを使用して、"if"文などのインテリジェントロジックをキャンペーンsに含めることができます。
-- [**フィルタ**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/filters/) では、パーソナライズされた 属性s とダイナミックなの内容を再フォーマットできます。たとえば、*2016-09-07 08:43:50 UTC* などのタイムスタンプを、*September 7, 2016* などの日付に変換できます。
+- [**タグ**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/)を使用すると、メッセージングにデータを挿入し、アウトライン条件が満たされている場合に条件ロジックを使用してメッセージを送信できます。例えば、タグを使用して、「if」文などのインテリジェントロジックをキャンペーンに含めることができます。
+- [**フィルター**]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/filters/)では、パーソナライズされた属性とダイナミックコンテンツを再フォーマットできます。たとえば、*2016-09-07 08:43:50 UTC* などのタイムスタンプを、*September 7, 2016* などの日付に変換できます。
 
 {% alert warning %}
-Brazeは現在、Shopify社のリキッドの100%を支持しておらず、当社のドキュメントで概説しようとした特定の部分のみを支持しています。エラーの危険を減らすため、またはサポートされていない液体を使用するために、すべてのメッセージを液体でテストしてから送信することを強くお勧めします。
+Brazeは現在、Shopify社のリキッドの100%を支持しておらず、当社のドキュメントで概説しようとした特定の部分のみを支持しています。エラーの危険、またはサポートされていない Liquid の使用を減らすため、送信する前にすべてのメッセージを Liquid でテストすることを強くお勧めします。
 {% endalert %}
 
 ### Liquid 5
 
-Braze は、**Shopify** からのLiquid 5 までのLiquid をサポートします。リキッドインプリメンテーションでは、シンタックスパーソナライゼーション タグタイプと空白コントロールがサポートされます。タグの詳細については、[構文タグs]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#syntax-tags)を参照してください。
+Braze は、**Shopify** からのLiquid 5 までのLiquid をサポートします。Liquid の実装では、構文パーソナライゼーションタグのタイプと空白コントロールがサポートされます。タグの詳細については、[構文タグs]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#syntax-tags)を参照してください。
 
-次の新しい配列と演算フィルターは、メッセージングの構築時にリキッドで使用できます。
+次の新しい配列と演算フィルターは、メッセージングの構築時に Liquid で使用することができます。
 - `at_least`
 - `at_most`
 - `compact`
@@ -73,13 +73,13 @@ Braze は、**Shopify** からのLiquid 5 までのLiquid をサポートしま
 
 定義については、[Filters]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/filters/)の記事を参照してください。
 
-### 流動更新s
+### Liquid の更新
 
-各Liquid エレメントはカラーに対応しており、Liquid エディターでLiquid を一目で区別できます。
+各 Liquid 要素は色分けされているので、Liquid エディターではこれらを一目で区別することができます。
 
 ![]({% image_buster /assets/img/liquid_color_code.png %})
 
-また、パーソナライズされたを作成する際に、カスタム属性s、属性の名前などにプレディケーティブリキッドを活用することもできます。
+また、パーソナライズされたメッセージを作成する際に、カスタム属性や属性の名前などにプレディケーティブ Liquid を活用することもできます。
 
 ![]({% image_buster /assets/img/liquid_auto_complete.gif %}){: style="max-width:70%;"}
 
@@ -92,11 +92,11 @@ Braze は、**Shopify** からのLiquid 5 までのLiquid をサポートしま
 
 | 用語 | 定義 | 例 |  
 |---|---|---|
-| Liquid | Shopify によって作成され、ルビーで書かれた、一般的に使用される、顧客に面したテンプレート。ダイナミックなの内容を読み込む/プルするために使用されます。 | `{{${first_name}}}` ユーザーの名をメッセージに挿入します。 |
-| オブジェクト | 変数のデノテーションと、メッセージ内のコンテンツを表示する場所をLiquid に伝える目的の変数名の場所。 | `{{${city}}}` ユーザーの都市を伝言メモに挿入します。 |
-| 条件付きロジックタグ | タグはロジックを作成し、メッセージ内容の流れをコントロールします。Braze では、条件付きロジックタグを使用して、事前定義された特定の条件に基づいて、メッセージに例外やバリエーションを作成します。 | ```{% if ${language} == 'en' %}``` ユーザーが"English"を指定した場合、指定された方法でメッセージをトリガーします。 |
-| フィルター | 液体オブジェクトの出力を変更、狭め、または再フォーマットするために使用します。多くの場合、数学演算を作成するために使用されます。 | ```{{"Big Sale" | upcase}}``` "Big Sale"という単語が、メッセージの中でear as "BIG SALE"をアプリします。 |
-| 演算子 | メッセージで使用され、ユーザーが受信するメッセージに影響を与える可能性のある依存関係または基準を作成します。 | ユーザーが、`{% custom_attribute.${Total_Revenue} > 0%}` のメッセージタグで定義された条件を満たしている場合、メッセージを受信します。設定されていない場合は、設定した内容に応じて、別の指定されたメッセージが受信されます(または受信されません)。 |
+| Liquid | Shopify によって作成され、ルビーで書かれた、一般的な顧客に面したテンプレート言語。ダイナミックなコンテンツを読み込む (プルする) ために使用されます。 | `{{${first_name}}}`は、ユーザーの名をメッセージに挿入します。 |
+| オブジェクト | 変数のデノテーションと、メッセージ内のコンテンツを表示する場所をLiquid に伝える目的の変数名の場所。 | `{{${city}}}` は、ユーザーの都市をメッセージに挿入します。 |
+| 条件付きロジックタグ | タグはロジックを作成し、メッセージ内容の流れをコントロールします。Braze では、条件付きロジックタグを使用して、事前定義された特定の条件に基づいて、メッセージに例外やバリエーションを作成します。 | ```{% if ${language} == 'en' %}``` は、ユーザーが自分の言語として英語を指定した場合、指定の方法でメッセージをトリガーします。 |
+| フィルター | Liquid オブジェクトの出力を変更、狭め、または再フォーマットするために使用します。多くの場合、数学演算を作成するために使用されます。 | ```{{"Big Sale" | upcase}}``` は、メッセージの中で「Big Sale」という言葉を「BIG SALE」として表示します。 |
+| 演算子 | メッセージで使用され、ユーザーが受信するメッセージに影響を与える可能性のある依存関係または基準を作成します。 | ユーザーが、`{% custom_attribute.${Total_Revenue} > 0%}` のメッセージタグで定義された条件を満たしている場合、メッセージを受信します。そうでない場合は、設定した内容に応じて、別の指定されたメッセージが受信されます (または受信されません)。 |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 {% endraw %}
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/aborting_messages.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/aborting_messages.md
index dd72e85268b..9e361107875 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/aborting_messages.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/aborting_messages.md
@@ -8,13 +8,13 @@ description: "このリファレンス記事では、リキッドメッセージ
 
 # メッセージの中止
 
-> 必要に応じて、条件内のリキッドメッセージを中止できます。このリファレンス記事では、この機能をマーケティング キャンペーン s で使用する方法をいくつか例示します。
+> 必要に応じて、条件内のリキッドメッセージを中止できます。この記事では、この機能をマーケティングキャンペーンで使用する方法の例をいくつか紹介します。
 
 {% alert note %}
-キャンバスでメッセージステップが中止された場合、ユーザー**はキャンバスを終了せず、**は次回のステップに進みます。
+キャンバスでメッセージステップが中止された場合、ユーザーはキャンバスを**終了せず**、**次のステップに進みます**。
 {% endalert %}
 
-## "Number Games Attended" = 0の場合、メッセージを中止します
+## "Number Games Attended" = 0 の場合、メッセージを中止する
 
 たとえば、ゲームに参加していない顧客にメッセージを送信したくなかったとします。
 
@@ -30,11 +30,11 @@ Love the games? Get 10% off your next one with code SAVE10.
 ```
 {% endraw %}
 
-このメッセージは、試合に出席したことがわかっている顧客にのみ送信されます。
+このメッセージは、ゲームに参加したことがわかっている顧客にのみ送信されます。
 
-## 英語圏顧客のみ
+## 英語圏の顧客専用のメッセージング
 
-英語圏の顧客にメッセージを送るには、"if"文を作成します。顧客の言語が英語で"else"文は、英語を話さない人やプロファイルに言語がない人のメッセージを中止します。
+英語圏の顧客にメッセージを送るには、顧客の言語が英語の場合に一致する「if」ステートメントを使い、英語を話さない顧客やプロファイルに言語がない顧客の場合は「else」ステートメントを使用してメッセージを中止します。
 
 {% raw %}
 ```liquid
@@ -46,24 +46,24 @@ Send this message in English!
 {% endif %}
 ```
 
-デフォルト Brazeでは、一般的なエラーメッセージがメッセージアクティビティログに記録されます。
+デフォルトでは、Braze はメッセージアクティビティログに一般的なエラーメッセージを記録します。
 
 ```text
 {% abort_message %} called
 ```
 
-また、かっこs 内に文字列を含めることで、メッセージアクティビティログに何かを記録することもできます。
+また、かっこ内に文字列を含めることで、メッセージアクティビティログに何らかの中止メッセージログを記録することもできます。
 
 ```liquid
 {% abort_message('language was nil') %}
 ```
 {% endraw %}
 
-![メッセージエラーは、"language がnil"のアボートメッセージで開発者コンソールにログインします。][26]
+![「language was nil」という中止メッセージのある開発者コンソールのメッセージエラーログ][26]
 
 [15]: {% image_buster /assets/img_archive/liquid_abort.png %}
 [26]: {% image_buster /assets/img_archive/developer_console.png %}
 [31]:https://docs.shopify.com/themes/liquid/tags/variable-tags
 [32]:https://docs.shopify.com/themes/liquid/tags/iteration-tags
 [34]:{% image_buster /assets/img_archive/personalized_iflogic_.png %}
-[37]:\#accounting-for-null-属性-values
+[37]:\#accounting-for-null-attribute-values
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters.md
index 5e00fdb5eff..777bd596218 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters.md
@@ -1,6 +1,6 @@
 ---
 nav_title: 高度なフィルター
-article_title: 高度なLiquidフィルター
+article_title: 高度な Liquid フィルター
 page_order: 4
 description: "このリファレンス記事には、高度なフィルター、例、およびキャンペーンでの使用方法が一覧表示されています。"
 
@@ -11,13 +11,13 @@ description: "このリファレンス記事には、高度なフィルター、
 ## エンコーディングフィルター
 
 {% raw %}
-| フィルター name | フィルター description | example input | example output |
+| フィルター名 | フィルター説明 | 入力例 | 出力例 |
 \|---|---|---|---|
 `md5` | md5エンコードされた文字列を返します | `{{'hey' | md5}}` | 6057f13c496ecf7fd777ceb9e79ae285 |
 `sha1` | sha1エンコードされた文字列を返します | `{{'hey' | sha1}}` | 7f550a9f4c44173a37664d938f1355f0f92a47a7 |
-`sha2` | sha2（256ビット、SHA-256とも呼ばれる）エンコードされた文字列を返します | `{{'hey' | sha2}}` | fa690b82061edfd2852629aeba8a8977b57e40fcb77d1a7a28b26cba62591204 |
+`sha2` | sha2（256 ビット、別称 SHA-256) エンコードされた文字列を返します | `{{'hey' | sha2}}` | fa690b82061edfd2852629aeba8a8977b57e40fcb77d1a7a28b26cba62591204 |
 `base64` | base64エンコードされた文字列を返します | `{{'blah' | base64_encode}}` | YmxhaA== |
-`hmac_sha1_hex`（以前は`hmac_sha1`）| hmac-sha1署名を返し、16進文字列としてエンコード | `{{'hey' | hmac_sha1_hex: 'secret_key'}}` | 2a3969bed25bfeefb00aca4063eb9590b4df8f0e |
+`hmac_sha1_hex`(旧 `hmac_sha1`） | 16 進文字列としてエンコードされた hmac-sha1 署名を返します | `{{'hey' | hmac_sha1_hex: 'secret_key'}}` | 2a3969bed25bfeefb00aca4063eb9590b4df8f0e |
 `hmac_sha1_base64` | hmac-sha1署名を返し、base64文字列としてエンコードされます | `{{'hey' | hmac_sha1_base64: 'secret_key'}}` | KjlpvtJb/u+wCspAY+uVkLTfjw4= |
 `hmac_sha256_hex` | hmac-sha256署名を返し、16進文字列としてエンコードされます | `{{'hey' | hmac_sha256_hex: 'secret_key'}}` | 8df897f8da3d7992fe57c8dbc6f27578cfbf2dcc4d0fbb4000b8c924841d508e |
 `hmac_sha256_base64` | hmac-sha256署名を返し、base64文字列としてエンコードされます | `{{'hey' | hmac_sha256_base64: 'secret_key'}}` | jfiX+No9eZL+V8jbxvJ1eM+/LcxND7tAALjJJIQdUI4= |
@@ -27,9 +27,9 @@ description: "このリファレンス記事には、高度なフィルター、
 
 | フィルター名 | フィルター 説明 | 例の入力 | 例の出力 |
 |---|---|---|---|
-| `url_escape` | URLで許可されていない文字列内のすべての文字を識別し、エスケープされたバリアントに置き換えます | `{{'hey<>hi' | url_escape}}` | こんにちは |
-| `url_param_escape` | URLで許可されていない文字をすべてエスケープされたバリアントに置き換えます。アンパサンド（&）を含みます。 | `{{'hey<&>hi' | url_param_escape}` | こんにちは |
-| `url_encode` | URL フレンドリーな文字列をエンコードします | `{{ 'google search' | url_encode }}` | グーグル+検索 |
+| `url_escape` | URLで許可されていない文字列内のすべての文字を識別し、エスケープされたバリアントに置き換えます | `{{'hey<>hi' | url_escape}}` | hey%3C%3Ehi |
+| `url_param_escape` | 文字列内の URL で許可されていない文字をすべてエスケープされたバリアントに置き換えます。アンパサンド (&) を含みます。 | `{{'hey<&>hi' | url_param_escape}` | hey%3C%26%3Ehi |
+| `url_encode` | URL フレンドリーな文字列をエンコードします | `{{ 'google search' | url_encode }}` | google+search |
 {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
 
 {% endraw %}
@@ -44,23 +44,23 @@ description: "このリファレンス記事には、高度なフィルター、
 {% endalert %}
 {% raw %}
 
-## プロパティ アクセサ フィルター
+## プロパティアクセサーフィルター
 
 | フィルター名 | フィルター 説明 |
 |---|---|---|---|
 | `property_accessor` | ハッシュとハッシュキーを受け取り、そのキーでそのハッシュの値を返します |
 {: .reset-td-br-1 .reset-td-br-2}
 
-**例のハッシュ:**`{"a" => 42, "b" => 0}`
-**例の入力:**`{{hash | property_accessor: 'a'}}`
-**例の出力:** `42`
+**ハッシュ例:** `{"a" => 42, "b" => 0}`
+**入力例:** `{{hash | property_accessor: 'a'}}`
+**出力例:** `42`
 
 さらに、プロパティアクセサフィルターを使用すると、カスタム属性をテンプレート化してハッシュキーに変換し、特定のハッシュ値にアクセスできます。
 
 {% endraw %}
 
 {% alert note %}
-Liquid内のBrazeでは、ハッシュを変数（式など）としてインスタンス化する方法はありません。
+Liquid 内の Braze では、ハッシュを変数 （式など） としてインスタンス化する方法はありません。
 {% endalert %}
 
 {% raw %}
@@ -86,4 +86,4 @@ Liquid内のBrazeでは、ハッシュを変数（式など）としてインス
 [31]:https://docs.shopify.com/themes/liquid/tags/variable-tags
 [32]:https://docs.shopify.com/themes/liquid/tags/iteration-tags
 [34]:{% image_buster /assets/img_archive/personalized_iflogic_.png %}
-[37]:\#ヌル属性値の会計
+[37]:\#accounting-for-null-attribute-values
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/conditional_logic.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/conditional_logic.md
index 9e5d6e36b2d..1881c9c6583 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/conditional_logic.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/conditional_logic.md
@@ -8,10 +8,10 @@ description: "この参考記事では、キャンペーンでタグをどのよ
 
 # 条件付きメッセージング・ロジック
 
-> \[タグ][7] を使えば、メッセージング・キャンペーンにプログラミング・ロジックを含めることができる。タグは、条件文の実行だけでなく、変数の代入やコードブロックの反復のような高度なユースケースにも使うことができる。
+> \[タグ ][7] では、メッセージングキャンペーンにプログラミングロジックを含めることができます。タグは、条件付きステートメントの実行や、変数の代入やコードブロックの反復のような高度なユースケースにも使用できます。
 
 {% raw %}
-タグは`{% %}` で囲む必要がある。
+タグは `{% %}` で囲む必要があります。
 {% endraw %}
 
 {% alert tip %}
@@ -27,7 +27,7 @@ description: "この参考記事では、キャンペーンでタグをどのよ
 {% endif %}
 ```
 
-緑色でハイライトされていることを確認し、`X` を選択したリキッドまたはコネクテッド・コンテンツに置き換え、メッセージ・フィールドの隅にある青色の`+` を使用し、`0` を希望する値に置き換える。
+緑色で強調表示されることを確認し、`X` を選択した Liquid またはコネクテッドコンテンツに置き換えて、メッセージフィールドの隅にある青色の `+` を使用して `0` を希望する値に置き換えます。
 <br><br>
 そして、`else` の条件文の間に、必要に応じてメッセージのバリエーションを追加する：
 ```liquid
@@ -42,7 +42,7 @@ Buy now! Would 5% off convince you?
 
 ## 条件論理
 
-][1] 、条件文のような多くのタイプの\[インテリジェント・ロジック]をメッセージに含めることができる。キャンペーンを国際化するために\[conditionals][8] ]を使用した次の例を参照のこと：
+条件付きステートメントなど、さまざまなタイプの \[インテリジェントロジックをメッセージ内][1] に含めることができます。キャンペーンを国際化するために\[conditionals][8] ]を使用した次の例を参照のこと：
 {% raw %}
 
 ```liquid
@@ -65,7 +65,7 @@ This is a message from Braze! This is going to go to anyone who did not match th
 {% if ${language} == 'en' %}
 This is a message in English from Braze!
 ```
-顧客の言語が英語の場合、最初の条件が満たされ、顧客は英語のメッセージを受け取る。
+顧客の言語が英語の場合、最初の条件が満たされ、顧客は英語で通知を受け取ります。
 
 ```liquid
 {% elsif ${language} == 'es' %}
@@ -74,21 +74,21 @@ Este es un mensaje en español de Braze !
 这是一条来自Braze的中文消息。
 ```
 
-条件文はいくつでも指定できる。前の条件が満たされない場合、次の条件がチェックされる。この例では、顧客のデバイスが英語に設定されていない場合、このコードは顧客のデバイスがスペイン語または中国語に設定されているかどうかを確認する。顧客のデバイスがこれらの条件のいずれかに当てはまる場合、顧客は該当する言語でメッセージを受け取る。
+条件付きステートメントはいくつでも指定できます。前の条件が満たされない場合、後続の条件がチェックされます。この例では、顧客のデバイスが英語に設定されていない場合、このコードは顧客のデバイスがスペイン語または中国語に設定されているかどうかを確認する。顧客のデバイスがこれらの条件のいずれかを満たす場合、顧客は該当する言語でメッセージを受け取ります。
 
 ```liquid
 {% else %}
 This is a message from Braze! This is going to go to anyone who did not match the other specified languages!
 ```
 
-条件ロジックに`{% else %}` 。設定した条件のどれにも当てはまらない場合、`{% else %}` ステートメントで送信すべきメッセージを指定する。この場合、顧客の言語が英語、スペイン語、中国語でない場合、デフォルトは英語になる。
+条件ロジックにはオプションで `{% else %}` ステートメントを含めることができます。設定した条件のどれにも当てはまらない場合、`{% else %}` ステートメントで送信すべきメッセージを指定する。この場合、顧客の言語が英語、スペイン語、中国語のどれでもない場合、デフォルトで英語になります。
 
 ```liquid
 {% endif %}
 ```
 
-`{% endif %}` 、条件ロジックが終了したことを知らせる。を含めなければならない。
-`{% endif %}`  タグを、条件付きロジックを持つメッセージに使用する。条件ロジックに`{% endif %}` タグを含めないと、Brazeがメッセージを解析できず、エラーになる。
+`{% endif %}` タグは、条件ロジックが終了したことを知らせます。条件ロジックを持つメッセージには、
+`{% endif %}` タグを必ず含める必要があります。条件ロジックに`{% endif %}` タグを含めないと、Brazeがメッセージを解析できず、エラーになる。
 
 {% endraw %}
 
@@ -98,11 +98,11 @@ This is a message from Braze! This is going to go to anyone who did not match th
 
 ### NULL および NIL 属性値
 
-nullまたはnil値は、カスタム属性の値が設定されていない場合に発生する。例えば、まだファーストネームを設定していないユーザーは、Brazeにファーストネームが記録されない。
+nullまたはnil値は、カスタム属性の値が設定されていない場合に発生する。例えば、まだ名を設定していないユーザーは、Braze に名が記録されません。
 
 状況によっては、ファーストネームを設定しているユーザーと設定していないユーザーとで、まったく異なるメッセージを送りたい場合もあるだろう。
 
-以下のタグは、"first name "属性がNULLのユーザーに対するメッセージを指定することができる：
+以下のタグは、「first name」属性が NULL のユーザーに対するメッセージを指定することができます。
 
 {% raw %}
 ```liquid
@@ -123,15 +123,15 @@ Hey {{${first_name} | default: 'there'}}, we're having a sale! Hurry up and get
 {% endif %}
 ```
 
-したがって、上の例では、null属性値は設定されていないファーストネームを参照していることになる。
+NULL の属性値は、値型と厳密には関連付けられていないことに注意してください (例えば、「null」の string は「null」 の array と同じです)。そのため、上記の例では、NULL 属性値が未設定の名 (文字列) を参照しています。
 
 {% endraw %}
 
 ### 空白の属性値
 
-空白の値は、ユーザープロファイルの属性が設定されていないか、空白文字列（` ` ）が設定されているか、`false` として設定されている場合に発生する。リキッド処理エラーを避けるため、ブランク値は他の変数より先にチェックすべきである。
+空白の値は、ユーザープロファイルで属性が設定されていないか、空白文字列 (` `) が設定されているか、`false` として設定されている場合に発生します。Liquid の処理エラーを避けるため、空白値は他の変数より先にチェックするようにします。
 
-以下のタグは、"first name "属性が空白のユーザーに対するメッセージを指定することができる。
+以下のタグは、「first name」属性が空白のユーザーに対するメッセージを指定することができます。
 
 {% raw %}
 ```liquid
@@ -143,19 +143,19 @@ Hey {{${first_name} | default: 'there'}}, we're having a sale! Hurry up and get
 
 ## カスタム属性を参照する
 
-カスタム属性を作成\[][2]]したら、リキッドメッセージングでこれらのカスタム属性を参照できる。
+\[カスタム属性を作成][2] したら、Liquid メッセージングでこれらのカスタム属性を参照することができます。
 
 条件付きロジックを使用する場合、正しい構文を使用していることを確認するために、カスタム属性のデータ型を知っておく必要がある。ダッシュボードの**カスタム属性**ページから、カスタム属性に関連するデータタイプを探し、各データタイプに記載されている以下の例を参照する。
 
 ![カスタム属性のデータ型を選択する。この例では、Favorite_Category属性のデータ型が文字列であることを示している。][20]{: style="max-width:80%;"}
 
 {% alert tip %}
-文字列と配列にはアポストロフィが必要だが、ブーリアンと整数にはアポストロフィはない。
+文字列と配列には一重引用符が必要ですが、ブール値と整数には必要ありません。
 {% endalert %}
 
 #### ブール値
 
-`registration_complete: true`[][9] はバイナリ値であり、`true` または`false` のいずれかに設定することができる。ブール値にはアポストロフィは付かない。
+\[ブール値][9] はバイナリ値なので、`true` または`false` のいずれかに設定することができます (例: `registration_complete: true`)。ブール値にはアポストロフィは付かない。
 
 {% raw %}
 
@@ -167,7 +167,7 @@ Hey {{${first_name} | default: 'there'}}, we're having a sale! Hurry up and get
 
 #### 数値
 
-\[][10] は数値であり、整数または浮動小数点数である。例えば、ユーザーは`shoe_size: 10` や`levels_completed: 287` を持っているかもしれない。数値にはアポストロフィは付かない。
+\[数値][10] は数値であり、整数または浮動小数点数にできます。たとえば、ユーザーには `shoe_size: 10` や `levels_completed: 287` などの属性があります。数値にはアポストロフィは付かない。
 
 {% raw %}
 
@@ -189,7 +189,7 @@ Hey {{${first_name} | default: 'there'}}, we're having a sale! Hurry up and get
 
 #### string
 
-文字列][11] は英数字で構成され、ユーザーに関するデータの一部を保存する。例えば、`favorite_color: red` または`phone_number: 3025981329` 。文字列の値にはアポストロフィをつけなければならない。
+\[文字列][11] は英数字で構成され、ユーザーに関する 1 つのデータを保存します。例えば、`favorite_color: red` や `phone_number: 3025981329` などです。文字列の値にはアポストロフィをつけなければならない。
 
 {% raw %}
 
@@ -203,7 +203,7 @@ Hey {{${first_name} | default: 'there'}}, we're having a sale! Hurry up and get
 
 #### 配列
 
-配列][12] は、ユーザーに関する情報のリストである。例えば、ユーザーは`last_viewed_shows: stranger things, planet earth, westworld` を持っているかもしれない。配列の値はアポストロフィで囲む必要がある。
+\[配列][12] は、ユーザーに関する情報のリストです。例えば、ユーザーには `last_viewed_shows: stranger things, planet earth, westworld` などの属性があります。配列の値はアポストロフィで囲む必要がある。
 
 {% raw %}
 
@@ -217,7 +217,7 @@ Hey {{${first_name} | default: 'there'}}, we're having a sale! Hurry up and get
 
 #### 時刻
 
-イベントが発生した時刻を示すタイムスタンプ。条件ロジックで使用するには、\[Time][13] value must have a \[math filter][5] on them.
+イベントが発生した時刻を示すタイムスタンプ。\[時刻][13] 値を条件ロジックで使用するには、\[数式フィルター][5] がなければなりません。
 
 {% raw %}
 
@@ -233,7 +233,7 @@ Hey {{${first_name} | default: 'there'}}, we're having a sale! Hurry up and get
 [2]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#managing-custom-attributes
 [5]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/filters/#math-filters
 [7]: https://docs.shopify.com/themes/liquid-documentation/tags
-[8]: http://docs.shopify.com/themes/liquid-documentation/tags/control-flow-tags 「コントロール・フロー・タグ
+[8]: http://docs.shopify.com/themes/liquid-documentation/tags/control-flow-tags 「コントロールフロータグ」
 [9]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#booleans
 [10]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#numbers
 [11]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#strings
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/faq.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/faq.md
index 6a12f5de279..a4d9d261a1f 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/faq.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/faq.md
@@ -2,7 +2,7 @@
 nav_title: FAQ
 article_title: よくある質問
 page_order: 11
-description: "この記事では、Liquidに関するよくある質問への回答を提供します。"
+description: "この記事では、Liquid に関してよくある質問にお答えします。"
 
 ---
 
@@ -10,21 +10,21 @@ description: "この記事では、Liquidに関するよくある質問への回
 
 > このページでは、Liquidに関するよくある質問への回答を見つけることができます。<br><br>Brazeは現在、ShopifyのLiquidの100%をサポートしているわけではなく、ドキュメントで概説しようとした特定の部分のみをサポートしています。すべてのメッセージを送信する前にLiquidを使用してテストすることを強くお勧めします。これにより、エラーのリスクやサポートされていないLiquidの使用を減らすことができます。
 
-### BrazeでLiquidスニペットをどのように使用しますか？
+### Braze で Liquid スニペットを使用するにはどうすればよいですか?
 
 多くの場合、キャンペーンやキャンバスに移動し、パーソナライゼーションモーダルのメールメッセージ本文やセグメントなどの領域にLiquidを挿入することで、Liquidスニペットを組み込むことができます。 
 
 #### もっと詳しく知るにはどこで学べますか？
 
-Liquidの詳細については、Braze学習パスの[ダイナミックなパーソナライゼーション](https://learning.braze.com/path/dynamic-personalization-with-liquid)ガイドをご覧ください！また、インスピレーションやLiquidを使用したさまざまなパーソナライゼーションの例については、[Liquidユースケースライブラリー]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases/)を参照することもできます。
+Liquid の詳細については、Braze ラーニングのガイド付きパス「[Liquid を使用したダイナミックなパーソナライゼーション](https://learning.braze.com/path/dynamic-personalization-with-liquid)」を参照してください。また、インスピレーションやLiquidを使用したさまざまなパーソナライゼーションの例については、[Liquidユースケースライブラリー]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases/)を参照することもできます。
 
-### Liquidとコネクテッドコンテンツをパーソナライゼーションに使用する場合の違いは何ですか？
+### Liquid とコネクテッドコンテンツをパーソナライゼーションに使用する場合の違いは何ですか?
 
-BrazeコネクテッドコンテンツはLiquidタグの例です。また、パーソナライゼーションにも使用されますが、このデータはBraze内の保存データではなく、外部のエンドポイントから取得されます。専用の[コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content)セクションをご覧になり、メッセージのパーソナライズ方法を拡張する方法について詳しく学んでください。
+Braze コネクテッドコンテンツは Liquid タグの一例です。これはパーソナライゼーションにも使用されますが、このデータは Braze 内の保存データではなく、外部のエンドポイントから取得されます。専用の[コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content)セクションをご覧になり、メッセージのパーソナライズ方法を拡張する方法について詳しく学んでください。
 
-### Liquidテンプレートとは何ですか？
+### Liquid テンプレートとは何ですか?
 
-これは、BrazeでLiquidを使用する最も一般的な方法です。Liquidテンプレートは、ユーザーのプロファイルからデータをメッセージに引き出すことを含みます。このデータは、ユーザーの名からイベントトリガーメッセージのカスタムイベントまで多岐にわたります。
+これは、Braze で Liquid を使用する最も一般的な方法です。Liquid テンプレートでは、ユーザーのプロファイルからデータをメッセージに引き出します。このデータは、ユーザーの名からイベントトリガーメッセージのカスタムイベントまで多岐にわたっています。
 
 [サポートされているパーソナライゼーションタグ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/)の完全なリストについては、サポートされているLiquidタグを参照してください。
 
@@ -36,9 +36,9 @@ BrazeコネクテッドコンテンツはLiquidタグの例です。また、パ
 
 いいえ。
 
-### Liquidを使用してパーソナライズされた挨拶を送信するにはどうすればよいですか？
+### Liquid を使用してパーソナライズされた挨拶を送信するにはどうすればよいですか?
 
-パーソナライズされた挨拶にユーザーの名を使用する場合、標準的なユーザープロファイル属性を{% raw %} `{{${first_name}}}`、`{{${last_name}}}`のように引き出すことができます。
+パーソナライズされた挨拶にユーザーの名を使用する場合、標準的なユーザープロファイル属性を {% raw %} `{{${first_name}}}`、`{{${last_name}}}`のように取得することができます。
 
 Liquidを使用して、曜日やカスタム属性などに基づいて条件付きレンダリングを行う`{% if X %}` {% endraw %}ステートメントを使用することもできます。サポートされているLiquid演算子の条件文で使用できる演算子の詳細については、[演算子]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/operators/)をチェックしてください。
 
@@ -61,16 +61,16 @@ Brazeには、メッセージで使用できるセグメントのLiquidコード
 ### イベント属性を使用して、イベントがトリガーしているメッセージをどのようにパーソナライズしますか？
 
 {% raw %}
-API トリガー イベントのプロパティには `api_triggered_property` タグ: `{{api_trigger_properties.${attribute_key}}}` を使用してアクセスできます。  
+API トリガーイベントのプロパティにアクセスするには、`api_triggered_property` タグ: `{{api_trigger_properties.${attribute_key}}}` を使用できます。  
 {% endraw %}
 
 ### 中止ロジックとは何ですか、それをどのように使用できますか？
 
 中止ロジックにより、条件が満たされている場合、メッセージの送信を停止できます。これは、未完成のメッセージがユーザーに送信されるのを防ぐのに特に役立ちます。マーケティングキャンペーンにおける中止ロジックの例については、[メッセージの中止]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/aborting_messages/)をお読みください。
 
-### ループロジックとは何ですか、それをどのように使用できますか？
+### ループロジックとは何ですか、それはどのように使用できますか?
 
-For loops are also known as [反復タグ](https://shopify.github.io/liquid/tags/iteration/).Liquidスニペットでforループロジックを使用すると、条件が満たされるまでLiquidのブロックを循環できます。 
+For loops are also known as [反復タグ](https://shopify.github.io/liquid/tags/iteration/).Liquid スニペットで for ループロジックを使用すると、条件が満たされるまで Liquid のブロックを反復実行できます。 
 
 Brazeでは、これは配列のカスタム属性、または[カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs)や[コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content)の呼び出し応答によって返される値やオブジェクトのリストをチェックするために使用できます。具体的には、メッセージングの一環としてforループロジックを使用して、製品が在庫にあるかどうか、または製品が最低評価を持っているかどうかを確認できます。 
 
@@ -88,4 +88,4 @@ Brazeでは、これは配列のカスタム属性、または[カタログ]({{s
 
 {% endraw %}
 
-設定された条件が満たされると、メッセージを進めることができます。このロジックを使用することは、異なる条件のためにLiquidブロックを繰り返す代わりに、時間を節約するための役立つ方法です。
+設定された条件が満たされると、メッセージを進めることができます。さまざまな条件で Liquid ブロックを繰り返す代わりに、このロジックを使用すると、時間を節約できて便利です。
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/operators.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/operators.md
index 71325d46c60..669ac07ad60 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/operators.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/operators.md
@@ -1,25 +1,25 @@
 ---
 nav_title: 演算子
-article_title: 液体事業者
+article_title: Liquid の演算子
 page_order: 2
-description: "このリファレンスページでは、Liquidがサポートする演算子と関連する例について説明します。"
+description: "このリファレンスページでは、Liquid がサポートする演算子と関連する例について説明します。"
 
 ---
 
 # 演算子
 
-Liquid は、条件文で使用できる多くの\[operators][25] をサポートしています。
+Liquid は、条件文で使用できる多くの \[演算子][25] をサポートしています。
 
 |   構文| オペレータの説明|
 |---------|-----------|
 | ==  | 等しい        |
 | !=  | 等しくない|
 |  >  | より大きい  |
-| その他   | 未満     |
+| <   | 未満     |
 | >=| 以上|
-| ;&lt= | 以下 |
+| <= | 以下 |
 | または | 条件Aまたは条件B|
-| および | 条件Aと条件B|
+| および | 条件 A および条件 B|
 | 含む | 文字列または文字列配列に文字列が含まれているかどうかを調べる|
 {: .reset-td-br-1 .reset-td-br-2}
 
@@ -27,7 +27,7 @@ Liquid は、条件文で使用できる多くの\[operators][25] をサポー
 
 以下に、これらの演算子がマーケティング キャンペーンs に役立つ例を示します。
 
-### 整数カスタム属性で選択
+### 整数カスタム属性でメッセージを選択する
 
 {% raw %}
 ```liquid
@@ -41,7 +41,7 @@ Buy now! Would 5% off convince you?
 
 ![][13]{: width="100%"}
 
-この例題では、顧客の"Total Spend" カスタム属性 が`0` より大きい場合、次のメッセージが表示されます。
+この例では、顧客の「Total Spend」カスタム属性が `0` より大きい場合、次のメッセージが表示されます。
 
 ```
 Thanks for purchasing! Here's another 10% off!
@@ -74,7 +74,7 @@ Hey! Get in here and play this Game!
 You played our Game! We're so happy!
 ```
 
-別の指定されたゲームをプレイした場合:
+別の指定されたゲームをプレイした場合は次のように表示されます。
 
 ```
 You played our other Game! Woop!
@@ -88,7 +88,7 @@ Hey! Get in here and play this Game!
 
 ### 位置に基づいてメッセージをアボートする
 
-何でもメッセージを中止することができます。次のサンプルは、ユーザーが指定された領域に基づいていない場合にメッセージをアボートする方法を示しています。これは、昇格、表示、または配信の対象外となる可能性があるためです。
+あらゆる条件に基づいてメッセージを中止することができます。次のサンプルは、ユーザーが指定された領域に基づいていない場合にメッセージをアボートする方法を示しています。これは、昇格、表示、または配信の対象外となる可能性があるためです。
 
 {% raw %}
 ```liquid
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/setting_default_values.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/setting_default_values.md
index a7c13e0537c..4cc05d0dcc6 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/setting_default_values.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/liquid/setting_default_values.md
@@ -1,24 +1,24 @@
 ---
 nav_title: デフォルト値の設定
-article_title: デフォルトの液体値の設定
+article_title: Liquid のデフォルト値の設定
 page_order: 5
 description: "このリファレンス記事では、メッセージで使用するパーソナライゼーション 属性のデフォルト フォールバックを設定する方法について説明します。"
 
 ---
 
-# デフォルトを設定する
+# デフォルト値を設定する
 
 {% raw %}
 
 > 既定のフォールバックは、メッセージで使用する任意のパーソナライゼーション 属性に設定できます。 
 
-デフォルトを追加するには、[液体フィルター][3]を"デフォルト.&quotという名前で指定します(`|`を使用して、インラインでフィルターを区別します)。
+デフォルト値を追加するには、[Liquid フィルター][3]を「デフォルト」という名前で指定します (インラインでフィルターを区別するには `|` を使用します)。
 
 ```
 | default: 'Insert Your Desired Default Here'
 ```
 
-デフォルトが指定されておらず、フィールドがないか、ユーザーに設定されていない場合、フィールドは空白になります。
+デフォルト値が指定されておらず、フィールドがないか、ユーザーに設定されていない場合、メッセージ内のフィールドは空白になります。
 
 次の例は、デフォルトを追加するための正しい構文を示しています。この例では、"Valued ユーザー" という単語は、ユーザーの`first_name` フィールドが空白または使用不可の場合、属性`{{ ${first_name} }}` を置き換えます。
 
@@ -26,7 +26,7 @@ description: "このリファレンス記事では、メッセージで使用す
 Hi {{ ${first_name} | default: 'Valued User' }}, thanks for using the App!
 ```
 
-ジャネット・ドーという名前のユーザーには、次のいずれかの方法でユーザーに耳元をアプリします。
+Janet Doe という名前のユーザーには、次のいずれかの方法でメッセージが表示されます。
 
 ```
 Hi Janet, thanks for using the App!
@@ -44,4 +44,4 @@ Hi Valued User, thanks for using the App!
 [31]:https://docs.shopify.com/themes/liquid/tags/variable-tags
 [32]:https://docs.shopify.com/themes/liquid/tags/iteration-tags
 [34]:{% image_buster /assets/img_archive/personalized_iflogic_.png %}
-[37]:\#accounting-for-null-属性-values
+[37]:\#accounting-for-null-attribute-values
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/promotion_codes.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/promotion_codes.md
index 380b07fd476..4433f2f6e1e 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/promotion_codes.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/promotion_codes.md
@@ -9,9 +9,9 @@ description: "この参考記事では、プロモーションコード・リス
 
 # プロモーションコード
 
-> プロモーションコード-プロモコードとも呼ばれる-は、購買に重点を置いたインタラクションを促進することで、ユーザーを引き留める素晴らしい方法である。
+> プロモーションコード (別名「プロモコード」) は、購入に重点を置いたインタラクションを促進することで、ユーザーのエンゲージメントを維持するための優れた方法です。
 
-Braze Liquidの機能により、プロモーションコードを簡単に使用できるようになり、メッセージは自動的に直感的に提供されたプロモーションリストから取得できるようになった。プロモーションコード機能は、最長6ヶ月の有効期限と、1リストあたり最大20MMの個別コードをサポートする。
+Braze Liquid の機能により、プロモーションコードを簡単に使用できるようになり、提供したプロモーションリストからメッセージを自動的かつ直感的に取得できるようになりました。プロモーションコード機能は、最長6ヶ月の有効期限と、1リストあたり最大20MMの個別コードをサポートする。
 
 {% alert important %}
 プロモーションコードはアプリ内メッセージでは送信できない。
@@ -26,7 +26,7 @@ Braze Liquidの機能により、プロモーションコードを簡単に使
 ダッシュボードから「**Data Settings（データ設定）**」＞「**Promotion Codes（プロモーション・コード）**」と進み、「**Create Promotion Code List（プロモーション・コード・リストを作成**）」を選択する。
 
 {% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、「**統合」の**下に**プロモーション・コードが**ある。
+[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合は、\[**プロモーションコード**] の下に \[**統合**] があります。
 {% endalert %}
 
 ### ステップ 2:プロモーション・コードの命名と作成
@@ -35,7 +35,7 @@ Braze Liquidの機能により、プロモーションコードを簡単に使
 
 ![][2]{: style="max-width:90%"}
 
-次に、プロモーション・コードのコード・スニペットを作成する。このコードスニペットは、特定のプロモーションコードを表示するためにLiquidで参照するものになる。他のリストですでに使われていないコード・スニペットであることを確認する。
+次に、プロモーション・コードのコード・スニペットを作成する。このコードスニペットは、プロモーションコードのこの特定のセットを表示するために Liquid で参照するコードスニペットです。他のリストですでに使われていないコード・スニペットであることを確認する。
 
 {% alert important %}
 スニペットは大文字と小文字を区別する。例えば、"Birthday_promo "と "birthday_promo "は異なるスニペットとして認識される。
@@ -44,7 +44,7 @@ Braze Liquidの機能により、プロモーションコードを簡単に使
 ![][3]{: style="max-width:90%"}
 
 {% alert warning %}
-保存後にコード・スニペットを変更することはできない！
+保存後にコードスニペットを変更することはできないので注意してください。
 {% endalert %}
 
 ### ステップ 3:プロモーションコードのオプション
@@ -53,16 +53,16 @@ Braze Liquidの機能により、プロモーションコードを簡単に使
 
 ![][4]{: style="max-width:90%"}
 
-また、オプションでカスタマイズした閾値アラートを設定するオプションもある。これらのアラートを設定すると、リスト内の利用可能なプロモーションコードが少なくなったとき、またはプロモーションコードリストの有効期限が近づいたときに、指定された受信者にEメールが送信される。受信者には1日1回通知される。
+また、オプションでカスタマイズした閾値アラートを設定するオプションもある。これらのアラートを設定すると、リスト内の利用可能なプロモーションコードが少なくなったとき、またはプロモーションコードリストの有効期限が近づいたときに、指定された受信者にEメールが送信される。受信者は 1 日 1 回通知を受け取ります。
 
 ![][5]
 
 ### ステップ 4:プロモーションコードのアップロード
 
-Brazeはコードの作成や償還を管理しない。そのため、プロモーションコードをCSVファイルに生成し、Brazeにアップロードする必要がある。[Voucherifyとの]({{site.baseurl}}/partners/channel_extensions/loyalty/voucherify/)ビルトイン統合または [Talon.One]({{site.baseurl}}/partners/channel_extensions/loyalty/talonone/)を使用してプロモーションコードを作成し、エクスポートすることができる。各行にコードが1つしかないことを確認する。
+Brazeはコードの作成や償還を管理しない。そのため、プロモーションコードをCSVファイルに生成し、Brazeにアップロードする必要がある。[Voucherify]({{site.baseurl}}/partners/channel_extensions/loyalty/voucherify/) との組み込み統合または [Talon.One]({{site.baseurl}}/partners/channel_extensions/loyalty/talonone/) を使用して、プロモーションコードを作成しエクスポートすることができます。各行にコードが1つしかないことを確認する。
 
 {% alert note %}
-最大ファイルサイズは100MB、最大リストサイズは20MMの未使用コードである。間違ったファイルがアップロードされた場合は、新しいファイルをアップロードすれば、前のファイルは置き換えられる。
+最大ファイルサイズは 100 MB、最大リストサイズは 20 MM の未使用コードです。間違ったファイルがアップロードされた場合は、新しいファイルをアップロードすれば、前のファイルは置き換えられる。
 {% endalert %}
 
 ![][6]
@@ -71,19 +71,19 @@ Brazeはコードの作成や償還を管理しない。そのため、プロモ
 
 ![][7]
 
-保存を選択すると、**インポート履歴に**新しい行が表示される。インポートが完了したかどうかを確認するために表を更新するには、表の上部にある<span style="font-size: 14px;margin-bottom: .5rem;height: 16px;width: 16px;" class="fas fa-sync" ></span> **Syncを**選択する。
+保存を選択すると、\[**インポート履歴**] に新しい行が表示されます。インポートが完了したかどうかを確認するためにテーブルを更新するには、テーブルの上部にある <span style="font-size: 14px;margin-bottom: .5rem;height: 16px;width: 16px;" class="fas fa-sync" ></span> \[**同期**] を選択します。
 
 ![][8]
 
 {% alert note %}
-大きなファイルはインポートに数分かかる。待っている間、インポートが進行している間、ページを離れて何か作業をすることができる。インポートが完了すると、表のステータスが**Completeに**変わるのがわかる。
+大きなファイルはインポートに数分かかる。待つ間、インポートが進行している間はページを離れて他の作業をすることができます。インポートが完了すると、テーブル内のステータスが \[**完了**] に変わります。
 {% endalert %}
 
 #### プロモーションコード一覧を更新する
 
 リストを更新するには、既存のリストを1つ選択する。名前、説明、リストの有効期限、しきい値アラートを変更できる。また、新しいファイルをアップロードし、「**Update List**」を選択することで、リストにさらにコードを追加することもできる。
 
-リスト内のすべてのコードは、輸入日に関係なく、同じ有効期限を持つ。
+インポート日に関係なく、リスト内のすべてのコードの有効期限が同じになります。
 
 ### ステップ 5: プロモーションコードを使用する
 
@@ -95,11 +95,11 @@ Brazeはコードの作成や償還を管理しない。そのため、プロモ
 
 ![][10]{: style="max-width:70%"}
 
-Liquid][11] を使って、アップロードされたCSVファイルからユニークなプロモーションコードをメッセージに挿入することができる。そのコードはBrazeのバックエンドで送信済みとマークされ、他のメッセージが同じコードを送信しないようにする。 
+\[Liquid][11] を使って、アップロードされた CSV ファイルから一意のプロモーションコードの 1 つをメッセージに挿入することができます。そのコードはBrazeのバックエンドで送信済みとマークされ、他のメッセージが同じコードを送信しないようにする。 
 
 マルチチャネルキャンペーンやキャンバスステップでコードスニペットが使用されると、各ユーザーは常にユニークなコードを受け取る。キャンバスのさまざまなステップで、各ユーザーは複数のプロモーションコードを受け取る。 
 
-特定のユーザーが複数のチャネルを通じてコードを受け取る資格がある場合、そのユーザーは各チャネルを通じて同じコードを受け取る。例えば、あるユーザーが2つのチャンネルを通じて2つのメッセージを受け取った場合、そのユーザーは1つのコードしか受け取らない。1つのコードが送信され、ユーザーは2つのチャンネルを通じてこのコードを受信する。例えば、マルチチャンネルのキャンバス・ステップの場合、ユーザーが使用するコードは1つだけである。
+特定のユーザーが複数のチャネルを通じてコードを受け取る資格がある場合、そのユーザーは各チャネルを通じて同じコードを受け取る。例えば、あるユーザーが2つのチャンネルを通じて2つのメッセージを受け取った場合、そのユーザーは1つのコードしか受け取らない。これは、レポートの目的でも同様です。1 つのコードが送信され、ユーザーは 2 つのチャネルを通じてこのコードを受信します。例えば、マルチチャンネルのキャンバス・ステップの場合、ユーザーが使用するコードは1つだけである。
 
 {% alert important %}
 プロモーションコードを取り込むキャンペーンからテストまたはライブメッセージを送信する際に、利用可能なプロモーションコードが残っていない場合、メッセージは送信されない。
@@ -109,7 +109,7 @@ Liquid][11] を使って、アップロードされたCSVファイルからユ
 
 テスト送信とシードグループのメール送信では、特にリクエストがない限り、プロモーションコードが使用される。Brazeのアカウントマネージャーに連絡して、この機能の動作を更新し、テスト送信やシードグループのメール送信時にプロモーションコードが使用されないようにする。
 
-## いくつのコードが使用されたかを判断する
+## 使用されたコードの数の判断
 
 残りのコード数は、**プロモーションコード・**ページにあるプロモーションコード・リストの「**Remaining」**欄で確認できる。
 
@@ -119,7 +119,7 @@ Liquid][11] を使って、アップロードされたCSVファイルからユ
 
 ![][13]{: style="max-width:50%"}
 
-## マルチチャンネルとシングルチャンネルのセンド
+## マルチチャネルとシングルチャネルの送信
 
 マルチチャネル、シングル送信キャンペーン、キャンバスでは、メッセージのリキッドで参照されるすべてのプロモーションコードは、メッセージが送信される**前に**使用されるように差し引かれ、次のことが起こることを確認する：
 
@@ -130,7 +130,7 @@ Liquid][11] を使って、アップロードされたCSVファイルからユ
 
 ### ユースケース
 
-以下の例では、プロモーションコード・リスト`vip-deal` と`regular-deal` の両方が差し引かれる。これがリキッドだ：
+以下の例では、プロモーションコード・リスト`vip-deal` と`regular-deal` の両方が差し引かれる。Liquid は以下のとおりです。
 
 {% raw %}
 ```
@@ -156,7 +156,7 @@ Brazeでは、使用予定数よりも多くのプロモーションコードを
 
 ### テスト送信やシード送信はプロモーションコードを使い切るのか？
 
-デフォルトでは、テスト送信とシードグループのメール送信では、テスト送信ごとにユーザーごとのプロモーションコードが使用される。しかし、Brazeのアカウントマネージャーに連絡すれば、テスト中にプロモーションコードを使用しないようにこの動作を更新することができる。
+デフォルトでは、テスト送信とシードグループのメール送信では、テスト送信ごとにユーザーごとのプロモーションコードが使用されます。しかし、Brazeのアカウントマネージャーに連絡すれば、テスト中にプロモーションコードを使用しないようにこの動作を更新することができる。
 
 ### マルチチャネルキャンペーンやキャンバスステップにおいて、プロモーションコードはどのように機能するのか？
 
@@ -164,7 +164,7 @@ Brazeでは、使用予定数よりも多くのプロモーションコードを
 
 ### 同じプロモーションコード一覧を参照するリキッドスニペットがメッセージ内に複数ある場合はどうなるのか？
 
-同じプロモーションコードが、メッセージ内のリキッドスニペットのすべてのインスタンスにテンプレート化される。
+同じプロモーションコードが、メッセージ内の Liquid スニペットのすべてのインスタンスにテンプレート化されます。
 
 ### プロモーションコードのリストが期限切れや空だった場合はどうなるのか？
 
diff --git a/_lang/ja/_user_guide/personalization_and_dynamic_content/promotion_codes/migrating_from_data_feeds.md b/_lang/ja/_user_guide/personalization_and_dynamic_content/promotion_codes/migrating_from_data_feeds.md
index 109d635807d..d5875099c56 100644
--- a/_lang/ja/_user_guide/personalization_and_dynamic_content/promotion_codes/migrating_from_data_feeds.md
+++ b/_lang/ja/_user_guide/personalization_and_dynamic_content/promotion_codes/migrating_from_data_feeds.md
@@ -8,16 +8,16 @@ description: "この参考文献は、データフィードからプロモーシ
 # データフィードから昇格コードへの移行
 
 {% alert note %}
-データフィードは非推奨です。Brazeは、データフィードを使用する顧客が昇格コード一覧に移行することを推奨します。
+データフィードは廃止されます。データフィードをご使用のお客様は、プロモーションコードリストに移行することを推奨します。
 {% endalert %}
 
-> データフィードからプロモーションコードsへの移行は、簡単な手順です。これには、データフィードの情報を含む昇格コード一覧を手動で作成し、それに応じてメッセージリファレンスを更新する必要があります。
+> データフィードからプロモーションコードsへの移行は、簡単な手順です。これには、データフィードの情報を含むプロモーションコードのリストを手動で作成し、それに応じてメッセージリファレンスを更新する必要があります。
 
 ## 特長と機能
 
-昇格コード一覧とデータフィードには、いくつかの違いがあります。
+プロモーションコードリストとデータフィードには、いくつかの違いがあります。
 
-| 機能          | 推進コード | データフィード   |
+| 機能          | プロモーションコード | データフィード   |
 |------------------|-----------------|--------------|
 | 説明     | はい             | いいえ           |
 | 有効期限 | はい             | いいえ           |
@@ -26,8 +26,8 @@ description: "この参考文献は、データフィードからプロモーシ
 
 ## 移行方法
 
-データフィードを昇格コード一覧に置き換えるには、次の手順を実行します。 
+データフィードをプロモーションコードリストに置き換えるには、次の手順を実行します。 
 
-1. **Data Settings**に進み、**プロモーションコードリストの作成**を選択します。
-2. [昇格コード一覧]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/promotion_codes)を設定します。
-3. 以前にデータフィードを参照したメッセージに移動し、昇格コード一覧を使用するように更新します。
\ No newline at end of file
+1. \[**データ設定**] に移動し、\[**プロモーションコードリストの作成**] を選択します。
+2. [プロモーションコードリストを設定]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/promotion_codes)します。
+3. 以前にデータフィードを参照したメッセージに移動し、プロモーションコードリストを使用するように更新します。
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/reporting.md b/_lang/ja/_user_guide/reporting.md
deleted file mode 100644
index 363d35e871c..00000000000
--- a/_lang/ja/_user_guide/reporting.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-nav_title: レポート
-article_title: LINE レポート
-page_order: 4
-description: "この参考記事では、Braze で使用されている LINE の指標と、LINE キャンペーンでの表示方法について説明します。"
-page_type: reference
-channel:
- - LINE
-hidden: true
-permalink: /line/reporting/
----
-
-# LINE レポート
-
-> キャンペーンやキャンバスを開始後、キャンペーンの詳細ページやキャンバス分析で主要な指標を表示できます。<br><br>この記事は LINE ベータ版コレクションの一部です。[メインページに戻ります](https://www.braze.com/docs/line/)。
-
-{% alert tip %}
-レポートの用語や指標の定義を確認したい場合は、[レポート指標の用語集]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics/)を参照してください。
-{% endalert %}
-
-## キャンペーン分析
-
-\[**キャンペーン分析**] タブでは、一連のパネルでレポートを表示できます。以下のセクションに列挙されている指標よりも多く、あるいは少なく表示される場合もありますが、それぞれに目的があります。
-
-{% alert note %}
-LINE の開封とクリック関連の統計は、1 日にイベントを実行したユーザーが 20 人以上の場合のみ計算されます。
-{% endalert %}
-
-### キャンペーンの詳細
-
-\[**キャンペーンの詳細**] パネルには、LINE メッセージのパフォーマンスの概要が表示されます。
-
-このパネルでは、受信者に送信されたメッセージの数、1 次コンバージョン率、このメッセージによって生み出された総収益などの全体的な指標を確認します。このページから、配信、オーディエンス、コンバージョン設定を確認することもできます。
-
-#### コントロールグループ
-
-個々の LINE メッセージの影響を測定するには、AB テストに[コントロールグループ]({{site.baseurl}}/user_guide/intelligence/multivariate_testing/)を追加できます。トップレベルの \[**キャンペーン詳細**] パネルには、コントロールグループのバリアントからの指標が含まれません。
-
-### LINE のパフォーマンス
-
-\[**LINEのパフォーマンス**] パネルでは、さまざまな角度からメッセージのパフォーマンスを確認できます。このパネルの指標は、選択したメッセージングチャネルや、多変量テストを実行しているかどうかに応じて異なります。<i class="fa fa-eye preview-icon"></i>\[**プレビュー**] アイコンをクリックすると、バリアントやチャネルごとにメッセージを表示できます。
-
-![2 つのバリアントの指標が表示される \[LINE のパフォーマンス] パネル。][1]
-
-表示を簡素化する場合は、\[**\+ 列を追加/削除**] を選択し、必要に応じて指標をクリアします。デフォルトでは、すべての指標が表示されます。
-
-#### LINE の指標
-
-分析に表示される主な LINE の指標を一部ご紹介します。Braze で使用されているすべての LINE の指標の定義については、「[レポート指標の用語集]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics/)」を参照してください。
-
-| 用語 | 定義 |
-| 送信数 | Braze と LINE の間で通信に成功した総送信数。これは、メッセージがユーザーによって受信されたことを意味しません。
-| ユニーク開封数 | 送信された LINE メッセージのうち、1 日 20 通の最小しきい値に達した後、ユーザーが開封したメッセージの総数。 |
-| 開封数の合計 | 送信された LINE メッセージのうち、1 日 20 通の最小しきい値に達した後、ユーザーが開封した回数の合計。 |
-| ユニーククリック数 | 送信された LINE メッセージのうち、1 日 20 通の最小しきい値に達した後、ユーザーがクリックしたメッセージの総数。 |
-| クリック数の合計 | 送信された LINE メッセージのうち、1 日 20 通の最小しきい値に達した後、ユーザーがクリックした回数の合計。 |
-{: .reset-td-br-1 .reset-td-br-2 }
-
-### 過去のパフォーマンス
-
-\[**過去のパフォーマンス**] パネルでは、\[**メッセージのパフォーマンス**] パネルの指標を時系列でグラフ表示できます。パネル上部のフィルターを使用して、グラフに表示される統計やチャネルを変更します。このグラフの時間範囲は、常にページ上部で指定された時間範囲を反映します。
-
-1 日ごとの内訳を確認するには、<i class="fas fa-bars"></i> ハンバーガーメニューを選択し、\[**CSV をダウンロード**] を選択すると、レポートを CSV 形式でエクスポートできます。
-
-### コンバージョンイベントの詳細
- 
-\[**コンバージョンイベントの詳細**] パネルには、キャンペーンのコンバージョンイベントのパフォーマンスが表示されます。詳細については、「[コンバージョンイベント]({{site.baseurl}}/user_guide/engagement_tools/testing/conversion_correlation)」を参照してください。
-
-### コンバージョンの相関
-
-\[**コンバージョンの相関**] パネルでは、どのようなユーザー属性と行動が、キャンペーンに設定した結果に役立つか、または悪影響を与えるかを把握できます。詳細については、「[コンバージョンの相関]({{site.baseurl}}/user_guide/engagement_tools/testing/conversion_correlation)」を参照してください。
-
-## LINE ユーザー ID 
-
-LINE ユーザー ID は、プロバイダーごとに各ユーザーに設定されています。LINE ID は、フォローするブランドごとに変わるため、ユーザーが (メールや電話番号とは違って) 自分の LINE ID を知ることはまずありません。
-
-
-[1]: {% image_buster /assets/img/line/line_performance.png %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/sage_ai.md b/_lang/ja/_user_guide/sage_ai.md
deleted file mode 100644
index 6901d429d1a..00000000000
--- a/_lang/ja/_user_guide/sage_ai.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-nav_title: セージAI by ブレイズ
-article_title: セージAI by ブレイズ
-page_order: 6.5
-layout: dev_guide
-search_rank: 12
-guide_top_header: "セージAI by ブレイズ"
-guide_top_text: "Sageとは、Start Anywhere Go Everywhereの頭文字をとったものだ。Sage AI by Brazeは、クリエイティビティ、パーソナライゼーション、エンゲージメント戦略の最適化のための参入障壁を下げる、アクセスしやすく使いやすいツールのコレクションを提供する。Sage AI by Brazeの機能を使えば、創造性を導き、より良い決断を下し、顧客のユーザー体験を最適化するための信頼できるアドバイザーを持つことができる。"
-description: "Sage AI by Brazeは、クリエイティビティ、パーソナライゼーション、エンゲージメント戦略の最適化のための参入障壁を下げる、アクセスしやすく使いやすいツールのコレクションを提供する。"
-
-Tool:
-  - Dashboard
-
-guide_featured_title: "特徴"
-guide_featured_list:
-- name: Intelligence Suite
-  link: /docs/user_guide/sage_ai/intelligence
-  image: /assets/img/braze_icons/clock.svg
-- name: Predictive Suite
-  link: /docs/user_guide/sage_ai/predictive_suite/
-  image: /assets/img/braze_icons/stars-01.svg
-- name: 生成AI
-  link: /docs/user_guide/sage_ai/generative_ai/
-  image: /assets/img/braze_icons/lightbulb-02.svg
-
-guide_menu_title: "Other"
-guide_menu_list:
-- name: ウイニング・バリアントとパーソナライズド・バリアント
-  link: /docs/user_guide/engagement_tools/testing/multivariant_testing/optimizations/
-  image: /assets/img/braze_icons/trophy-01.svg
-- name: 勝者パス
-  link: /docs/user_guide/engagement_tools/canvas/canvas_components/experiment_step/winning_path/
-  image: /assets/img/braze_icons/dataflow-03.svg
-- name: パーソナライズされたパス
-  link: /docs/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths/
-  image: /assets/img/braze_icons/chevron-up-double.svg
-- name: おすすめ
-  link: /docs/user_guide/sage_ai/recommendations/
-  image: /assets/img/braze_icons/hearts.svg
----
-
-
-<br>
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/sage_ai/generative_ai.md b/_lang/ja/_user_guide/sage_ai/generative_ai.md
deleted file mode 100644
index c8ea0777a2c..00000000000
--- a/_lang/ja/_user_guide/sage_ai/generative_ai.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-nav_title: 生成AI
-article_title: 生成AI
-page_order: 20
-layout: dev_guide
-guide_top_header: "生成AI"
-guide_top_text: "Sage AI by Brazeは、効率性と創造性を高める様々な自動生成AI機能を提供する。定型的なコピーライティング作業、コンテンツの洗練、画像作成に費やす時間を減らしながら、魅力的なクロスチャネル顧客体験を創造する。<br><br>詳しくは以下の記事をご覧いただきたい。"
-description: "Sage AI by Brazeは、効率性と創造性を高める様々な自動生成AI機能を提供する。"
-
-guide_featured_title: "特徴"
-guide_featured_list:
-- name: AIコピーライティング・アシスタント
-  link: /docs/user_guide/sage_ai/generative_ai/ai_copywriting/
-  image: /assets/img/braze_icons/edit-05.svg
-- name: AI画像ジェネレーター
-  link: /docs/user_guide/engagement_tools/templates_and_media/media_library/#generate-ai
-  image: /assets/img/braze_icons/image-03.svg
-- name: AIコンテンツQA
-  link: /docs/user_guide/sage_ai/generative_ai/ai_content_qa/
-  image: /assets/img/braze_icons/clipboard-check.svg
-- name: AIリキッド・アシスタント
-  link: /docs/user_guide/sage_ai/generative_ai/ai_liquid/
-  image: /assets/img/braze_icons/beaker-02.svg
-- name: SQLクエリビルダ
-  link: /docs/user_guide/data_and_analytics/query_builder/
-  image: /assets/img/braze_icons/tool-01.svg
-- name: SQLセグメント
-  link: /docs/sql_segments/
-  image: /assets/img/braze_icons/users-01.svg
-
----
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_content_qa.md b/_lang/ja/_user_guide/sage_ai/generative_ai/ai_content_qa.md
deleted file mode 100644
index e9a5b19847d..00000000000
--- a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_content_qa.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-nav_title: AIによるコンテンツQA
-article_title: AIによるコンテンツQA
-page_order: 10
-description: "この参考記事では、メッセージ作成ソフトから直接AIを使ってメッセージ内容の品質保証を行う方法を取り上げる。"
----
-
-# AIによるコンテンツQA
-
-> メッセージコンポーザーから直接AIを使ってメッセージコンテンツの品質保証を行う方法を学ぶ。
-
-AIによるコンテンツQAは、GPTとOpenAIの機能を使用して、メッセージのコンテンツのチェックを行い、スペルミス、文法の問題、不適切なトーン、不快な言葉遣いなど、効果的でない要素を特定することで、品質基準を満たしていることを確認する。キャンペーンやキャンバスでプッシュ、SMS、アプリ内メッセージを作成する際、**Test**タブからこの機能にアクセスできる。
-
-## 主な機能
-
-AIによるコンテンツQAは、メッセージ・コンテンツの品質を高めるために、以下の主要な機能を提供する：
-
-- **スペルと文法をチェックする：**メッセージのスペルや文法の間違いを自動的にチェックする。コンテンツの全体的な正確性を向上させるために、修正を提案し、推奨事項を提示する。
-- **トーン分析だ：**メッセージのトーンを評価し、潜在的な問題を特定する。これは、意図したトーンと望ましいコミュニケーション・スタイルが一致していることを確認し、誤解や意図しない不快感を避けるのに役立つ。
-- **攻撃的な言葉の検出：**メッセージをスキャンし、攻撃的または不適切な表現がないか確認する。
-- **事故内容チェック：**意図せずに追加された可能性のあるコード、マークアップ言語、テストメッセージの包含を検出する。
-
-## AIでコンテンツQAにアクセスする
-
-{% alert note %}
-AIによるコンテンツQAは、現時点ではプッシュとSMSチャンネルでのみ利用できる。
-{% endalert %}
-
-コンテンツ・チェッカーにアクセスするには、以下の手順に従う：
-
-1. プッシュまたはSMSメッセージを作成した後、**Test**タブに移動する。
-2. **AIによるコンテンツQA**セクションを探す。
-3. **Test Contentを**クリックする。
-
-![テストタブのAIセクションでコンテンツQAを行う。][1]{: style="max-width:60%"}
-
-### 言語サポート
-
-GPTは[複数の言語を](https://openai.com/research/gpt-4#:~:text=GPT%2D4%203%2Dshot%20accuracy%20on%20MMLU%20across%20languages)理解することができるが、OpenAIは公式にはサポートしていない。Brazeは、メッセージの内容がOpenAIに送信されるときに、コピーの言語やロケールに関する追加情報を渡さないので、その判断はGPTに任されている。
-
-結果は書く言語によって異なるかもしれない。
-
-## 効果的な使い方のヒント
-
-AIによるコンテンツQA機能を最大限に活用するために、以下のヒントを考えてみよう：
-
-- **メッセージを校正する：**コンテンツチェッカーはエラーの特定に役立つが、それでもコンテンツの校正は手作業で行うことが不可欠だ。AIが生成した提案は有用なガイドとして頼りにするが、正確さを期すために自分の判断を用いること。
-- **トーン分析を理解する：**トーン分析結果は主観的で、AIモデルの理解に基づいている。これらは有益な洞察を与えてくれるが、あなたの意図するトーンと会話の文脈を考慮し、適切な調整を行うこと。
-- **攻撃的な言葉遣いのフラグをダブルチェックする：**攻撃的な言葉の検出はロバストであるように設計されているが、時折、偽陽性のフラグが立つことがある。フラグが立った箇所を注意深く見直し、必要に応じて適切な変更を加える。
-
-## データはどのように使用されて、OpenAI に送信されるのですか?
-
-メッセージの内容を確認するために、BrazeはOpenAIのAPI Platformに送信する。BrazeからOpenAIに送信されるクエリはすべて匿名化される。つまり、OpenAIは、ユーザーが提供するメッセージコンテンツに一意に特定できる情報が含まれていない限り、クエリが誰から送信されたかを特定することはできない。[OpenAI の API プラットフォームコミットメント](https://openai.com/policies/api-data-usage-policies)に詳述されているように、Braze 経由で OpenAI の API に送信されたデータは、モデルのトレーニングや改善には使用されず、30日後に削除されます。お客様に関連する OpenAI のポリシーを必ず遵守してください。これには、OpenAI の[使用ポリシー](https://openai.com/policies/usage-policies)や[共有および公開ポリシー](https://openai.com/policies/sharing-publication-policy)が含まれる場合があります。Braze は AI が生成したコンテンツに関していかなる種類の保証も行いません。
-
-[1]: {% image_buster /assets/img/content_qa_ai.png %}
diff --git a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_copywriting.md b/_lang/ja/_user_guide/sage_ai/generative_ai/ai_copywriting.md
deleted file mode 100644
index 56d4554c92c..00000000000
--- a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_copywriting.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-nav_title: AIコピーライティングアシスタント
-article_title: AIコピーライティングアシスタント
-page_order: 4
-description: "このリファレンス記事では、AI のコピーライティングアシスタントについて説明します。この機能は、OpenAI のGPT コピー生成ツールに簡単な製品名または説明を渡し、メッセージングで使用するための人のようなマーケティングコピーを生成します。"
----
-
-# AIコピーライティングアシスタント
-
-> AI コピーライティングアシスタントは、OpenAI が所有するサードパーティプロバイダーのGPT コピー生成ツールに簡単な製品名または説明を渡し、メッセージングで使用するための人的なマーケティングコピーを生成します。この機能は、Braze ダッシュボード内のほとんどのメッセージ作成画面でデフォルトで使用できます。
-
-## コピーの作成 {#steps}
-
-AI コピーライティングアシスタントを使用してコピーを生成するには、次のステップに従います。
-
-1. メッセージ作成画面から、<i class="fa-solid fa-wand-magic-sparkles"></i>**Launch AI Copy writer**を選択します。
-   * アプリ内メッセージ sのドラッグアンドドロップエディタで、テキストブロックを選択し、ブロックのツールバーで<i class="fa-solid fa-wand-magic-sparkles" title="AIコピーライタ"></i>を選択します。
-2. インプットフィールドに商品名または説明を入力します。
-3. アプリの長さを選択します。チャネル固有のベストプラクティスに基づいて、出力長に固有のチャネルを選択するか、短(1 文)、中(2～3 文)、長(1 段落)のいずれかを選択できます。 
-4. (オプション) ブランドガイドラインを作成またはアプリして、このコピーをブランドに合わせます。これらのガイドラインはワークスペースに保存され、作成後に再利用できます。詳細については、[ブランドガイドラインの作成]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines/)を参照してください。
-5. (オプション) 使用可能なオプションからメッセージトーンを選択します。これにより、生成されるコピーのスタイルが決まります。
-6. (オプション)プッシュ通知で使用可能:**過去のキャンペーンデータのリファレンス**を選択すると、以前のモバイルプッシュメッセージ(キャンペーン s およびキャンバスステップs)を新しいコピーを生成するためのスタイルリファレンスとして使用できます。選択すると、出力は以前のメッセージのスタイルを模倣します。
-7. 出力言語を選択する。これは入力言語とは異なる場合があります。
-8. \[**生成**] をクリックします。
-
-私たちは、あなたが提供した情報を使用して、あなたのためにコピーを書くようにGPTに促します。応答はOpenAI から取得され、ユーザーに提供されます。 
-
-![AI コピーライティングアシスタントのモーダルで、利用可能なさまざまな機能を表示します。][1]{: style="max-width:70%;"}
-
-{% alert important %}
-OpenAIの[コンテンツポリシー](https://beta.openai.com/docs/usage-guidelines/content-policy)に違反する不快なコンテンツに対するレスポンスをフィルターします。
-{% endalert %}
-
-## キャンペーン履歴を利用する
-
-push を出力長として使用する場合、**Reference past キャンペーン data** を選択すると、ランダムに選択された以前のモバイルプッシュキャンペーンs がOpenAI に送信され、GPT がそのコピー生成の基礎として使用できるようになります。この機能を活用しない場合は、このボックスをオフのままにします。Braze およびOpenAI でのデータの使用方法の詳細については、次の項を参照してください。 
-
-[ブランドガイドライン]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines/)と組み合わせて使用すると、ブランドガイドラインとこれまでのキャンペーンデータの両方が最終アウトプットに組み込まれる。
-
-## GPTとは。
-
-[GPT](https://openai.com/product/gpt-4)は、人工知能を駆使したOpenAIの最先端の自然言語生成ツールです。テキストの生成、完了、分類など、さまざまな自然言語タスクを実行できます。私たちはそれをBraze ダッシュボードに差し込み、あなたが仕事をする中で、あなたの複製を直接的に刺激し、多様化させるのを助けてきました。
-
-## データはどのように使用されて、OpenAI に送信されるのですか?
-
-コピーを生成するために、Braze はクエリーをOpenAI に送信します。Braze からOpenAI に送信されるすべてのクエリーは匿名化されます。つまり、OpenAI は、入力に一意に識別可能な情報を含めるか、または" というラベルの付いたオプションを有効にする際に過去のキャンペーンデータに含めない限り、クエリーの送信元を識別できません。[OpenAI のポリシー](https://openai.com/policies/api-data-usage-policies) により、Braze を介してOpenAI のAPI に送信されるデータは、モデルのトレーニングや改善には使用されず、30 日後に削除されます。あなたとBrazeの間で、GPTを使って生成された内容は、あなたの知的なプロパティです。Braze は、そのようなコンテンツに対する著作権所有権の主張を主張するものではなく、AI が生成したコンテンツに関するいかなる保証も行いません。
-
-## その他のAI ツール
-
-また、[メディアライブラリーからAI]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/media_library/#generate-ai)を使用して"画像を生成することもできます。これは、OpenAIのAIシステムであるDALL·E 2を活用し、自然言語の記述からリアルな"画像や芸術を生み出すことができます。
-
-[1]: {% image_buster /assets/img/ai_copywriter/gpt3.png %} "GPT3"
diff --git a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines.md b/_lang/ja/_user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines.md
deleted file mode 100644
index 705fd73cd1f..00000000000
--- a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-nav_title: ブランド・ガイドライン
-article_title: AIコピーライティングのためのブランド・ガイドライン
-page_order: 1
-description: "この参考記事では、AIコピーライティングアシスタントのブランドガイドラインを取り上げる。AIコピーライティングアシスタントが生成するコピーのスタイルを、ブランドの声やスタイルに合わせて調整できる機能だ。"
----
-
-# AIコピーライティング・アシスタントのブランド・ガイドライン
-
-> AIコピーライティングアシスタントが生成するコピーのスタイルをあなたのブランドと声に合わせるために、ブランドガイドラインを作成し、適用する。
-
-## ブランド・ガイドラインを作成する {#steps}
-
-AIコピーライティング・アシスタントで使用する新しいブランド・ガイドラインを作成するには、以下の手順に従う：
-
-1. AIコピーライティングアシスタントを開く。
-2. **ブランドガイドラインを適用する**」を選択し、「**ブランドガイドラインを作成する**」を選択する。
-2. このガイドラインの名前を入力する。これは、前の選択で見たラベルの役割を果たす。
-3. **このブランド・ガイドラインをいつ使用しますか**」には、このガイドラインを使用する状況やマーケティングのタイプを記述する。
-4. **ブランド・パーソナリティでは**、特徴、価値観、声、原型など、ブランドのパーソナリティを記述する。
-5. (オプション)**除外項目には**、生成されたコンテンツで避けるべき言葉やスタイルを追加する。例えば、「嫌味」、「否定的な態度」、「慇懃無礼」など、あなたが望まない性格的特徴を除外することができる。
-6. ガイドラインをテストして微調整する。これらのガイドラインを使ったコピー例を作成するには、**Test your guidelinesを**展開し、プロンプトを入力する。
-7. 満足したら、**セーブブランドのガイドラインを**選択する。
-
-これでコピーライティング・ビューに戻ることができる。新しいガイドラインはワークスペースに保存され、今後使用することができる。
-
-{% alert important %}
-コピーの言語に関係なく出力言語を変更できるが、BrazeもOpenAIも翻訳の品質を保証しない。翻訳を使用する前にテストし、検証すべきである。
-{% endalert %}
-
-![ブランド・ガイドライン作成の視点"][1]
-
-## 編集ガイドライン
-
-既存のブランド・ガイドラインを編集する：
-
-1. AIコピーライティングアシスタントを開く。
-2. 編集したいブランドガイドラインを適用する。フィールドの近くにボタンが表示される。
-3. **ガイドラインの編集を**選択する。
-
-## データはどのように使用されて、OpenAI に送信されるのですか?
-
-ブランドガイドラインを使ってコピーを生成するために、ブレイズはガイドラインの内容を含む問い合わせをOpenAIに送る。BrazeからOpenAIに送信されるクエリはすべて匿名化される。つまり、「過去のキャンペーンデータを参照する」というオプションを有効にした場合に、提供する入力内容や過去のキャンペーンデータに一意に特定できる情報が含まれていない限り、OpenAIはクエリが誰から送信されたかを特定することはできない。[OpenAIのポリシーに](https://openai.com/policies/api-data-usage-policies)よれば、Braze経由でOpenAIのAPIに送られたデータは、モデルの訓練や改良には使用されず、30日後に削除される。お客様とBrazeとの間で、GPTを使用して生成されたコンテンツは、お客様の知的財産である。Brazeは、かかるコンテンツの著作権所有権を主張せず、AIが生成したコンテンツに関していかなる保証も行わない。
-
-
-[1]: {% image_buster /assets/img/ai_copywriter/manual_brand_guidelines.png %} 「ブランド・ガイドライン
diff --git a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_liquid.md b/_lang/ja/_user_guide/sage_ai/generative_ai/ai_liquid.md
deleted file mode 100644
index 248f272434f..00000000000
--- a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_liquid.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-nav_title: AIリキッドアシスタント
-article_title: AIリキッドアシスタント
-description: "本稿では、Sage AI Liquid Assistant の仕組みと、メッセージング用のLiquid スニペットの生成方法について説明します。"
-page_type: reference
-page_order: 5
----
-
-# AI Liquidアシスタント
-
-> Sage AI Liquid Assistant は、Sage AI を搭載したチャットアシスタントで、メッセージコンテンツをパーソナライズするために必要なLiquid を生成するのに役立ちます。 
-
-AI Liquid Assistant を使用すると、テンプレート s からLiquid を生成したり、パーソナライズされた Liquid の提案を受信したり、Sage AI を使用して既存のLiquid を最適化したりできます。AI Liquid Assistant には、使用されているLiquid を説明するアノテーションも用意されているため、Liquid について理解を深め、自分で書くことを学ぶことができます。
-
-{% alert important %}
-AIリキッドアシスタントは現在、プッシュ型およびSMS型のチャネルを積極的に利用している限られた顧客のためにベータ版に入っている。ベータの検討を希望する場合は、顧客のサクセスマネージャーに連絡するか、この[ポータルカード](https://braze.productboard.com/entity-detail/features/27273918)に関心を示します。
-{% endalert %}
-
-## その仕組み
-
-AI Liquid Assistant は、マーケティングのニーズに合わせて効果的なLiquid コードを作成するのに役立ちます。リキッドのシンタックスとマーケター s がリキッドをどのように使っているかの両方についてトレーニングを受け、私たちのAI はパーソナライズされた内容の作り方のニュアンスを理解しています。さらに、AI Liquid Assistant にカスタム属性の名前(`favourite_color` など) とデータ型(ブール値や文字列など) を提供することで、AI Assistant によってメッセージが正確にターゲット設定され、目標と整合性がとれていることが保証されます。
-
-## リキッドコードの生成
-
-AI Liquid Assistant を起動するには、メッセージ作成画面でAI Assistant アイコンを選択します。
-
-![AI アシスタントを持つメッセージコンポーザー。][1]{: style="max-width:50%;"}
-
-[提供されたプロンプト](#provided-prompts)を選択するか、テキストボックスに独自の情報を入力することができます。リキッドコードを生成するには、**コンポーザーの更新**を選択します。
-
-![AI アシスタントウィンドウ。プロンプトが表示されます。][2]{: style="max-width:50%;"}
- 
-同じプロンプトを使用して別のメッセージを生成するには、**Regenerate**を選択します。メッセージを削除して前のメッセージに戻すには、**更新を元に戻します**を選択します。
-
-### 提供されるプロンプト
-
-AI Liquid Assistant の使用中に、Liquid の使用を開始するためのさまざまなプロンプトが表示されることがあります。プロンプトの一部を以下に示します。
-
-#### アプリ活動を利用する
-
-**アプリアクティビティを使用**プロンプトは、アプリが最後に使用された日時に基づいてさまざまなメッセージを送信するのに役立つリキッドコードを生成します。アシスタントがより多くのキュレートを得ることができるように、フォローアップ質問を受けることがあります。
-
-!["Use アプリ activity"プロンプトの出力例。][3]{: style="max-width:45%;"}
-
-#### カウントダウンの追加
-
-このプロンプトは、イベントhがアプリするまでの時間を示すメッセージを送信するリキッドコードを生成します。イベント日時の詳細をお聞きします。
-
-!["Add countdown"プロンプトの出力例。][4]{: style="max-width:45%;"}
-
-#### インスパイア・ミー
-
-このプロンプトアプリは、メッセージボックスに内容がある場合に表示されます。Liquidでメッセージをパーソナライズするために選択できるオプションのリストが生成されます。 
-
-!["Inspire me"プロンプトの出力例。][5]{: style="max-width:60%;"}
-
-#### リキッドの改良
-
-このプロンプトアプリは、メッセージ作成画面に内容がある場合に有効になります。アシスタントがコードをより効率的に読みやすくする場合に選択します。
-
-![&quot の出力例;Liquid"prompt を改善します。][6]{: style="max-width:45%;"}
-
-## ベータ版でサポートされる属性
-
-| 条件| ナレッジタイプ|
-| - | - |
-| 液体(`for` ループ、`if` ステートメント、数学、その他を含む) | コーディング|
-| 既定および規格のユーザー 属性 s | 属性s |
-| 以下のいずれかのデータタイプを持つカスタム属性s: {::nomarkdown}<ul><li>ブール値</li><li>数値</li><li>文字列</li><li>配列</li><li>時刻</li></ul>{:/} | 属性|
-| 接続されたコンテンツ| コーディング|
-{: .reset-td-br-1 .reset-td-br-2 }
-
-## データはどのように使用されて、OpenAI に送信されるのですか?
-
-メッセージの内容を変更または作成するには、Braze はプロンプト、メッセージ、およびOpenAI のAPI プラットフォームにLiquid AI Assistant に送信されたコンテンツを送信します。Braze から OpenAI に送信されるすべてのクエリは匿名化されます。つまり、提供するコンテンツに一意に識別できる情報を含めない限り、OpenAI はクエリの送信元を特定できません。[OpenAI のAPI プラットフォーム コミットメント](https://openai.com/policies/api-data-usage-policies)に詳述されているように、Braze を介してOpenAI のAPI に送信されるデータは、モデルのトレーニングや改善には使用されず、30 日後に削除されます。[Usage policies](https://openai.com/policies/usage-policies) とその[Sharing & publication policy](https://openai.com/policies/sharing-publication-policy) が含まれている可能性がある、ユーザーに関連するOpenAI のポリシーを遵守してください。Braze は、AI が生成した内容に関していかなる保証も行いません
-
-[1]: {% image_buster /assets/img/ai_liquid/ai_assistant_icon.png %}
-[2]: {% image_buster /assets/img/ai_liquid/ai_assistant_window.png %}
-[3]: {% image_buster /assets/img/ai_liquid/use_app_activity.png %}
-[4]: {% image_buster /assets/img/ai_liquid/add_countdown.png %}
-[5]: {% image_buster /assets/img/ai_liquid/inspire_me.png %}
-[6]: {% image_buster /assets/img/ai_liquid/improve_my_liquid.png %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_liquid/ai_liquid_prompts.md b/_lang/ja/_user_guide/sage_ai/generative_ai/ai_liquid/ai_liquid_prompts.md
deleted file mode 100644
index 022dc9e0a31..00000000000
--- a/_lang/ja/_user_guide/sage_ai/generative_ai/ai_liquid/ai_liquid_prompts.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-nav_title: プロンプティングについて
-article_title: AIリキッド・アシスタントへのプロンプトについて
-description: "この記事では、ベストプラクティスやプロンプトの例を含め、AIリキッドアシスタントにプロンプトを出す方法を説明する。"
-page_type: reference
-page_order: 0
-hidden: true
-permalink: /ai_liquid_prompts/
-noindex: true
----
-
-# AIリキッドアシスタントのプロンプトについて
-
-> プロンプティングとは、AIリキッドアシスタントにやってほしいことを明確に指示するプロセスだ。
-
-{% alert important %}
-AIリキッド・アシスタントは現在、プッシュとSMSチャンネルを積極的に利用する限られた顧客向けにベータ版を提供している。ベータ版への参加を希望する場合は、カスタマー・サクセス・マネージャーに連絡するか、この[ポータル・カードに](https://braze.productboard.com/entity-detail/features/27273918)その旨を記入してほしい。
-{% endalert %}
-
-AIリキッドアシスタントは、Brazeとリキッドを使ってインパクトのあるマーケティングメッセージを作成する専門家であるクラス最高のマーケターとして機能するように設計されているが、それでも特定のユースケースや質問に対するガイダンスが必要だ。
-
-アシスタントにプロンプトを出す正しい方法はひとつではないし、会話中にいつでもプロンプトに詳細を加えることができる。つまり、「完璧な」最初のプロンプトを作るのに多くの時間を費やす必要はないのだ。しかし、いくつかのベストプラクティスに従うことで、アシスタントを最大限に活用することができる。
-
-## 効果的なプロンプティングのベストプラクティス
-
-### 自然言語を使う
-
-AIリキッド・アシスタントは自然言語を理解するよう訓練されている。同僚に助けを求めるときのように、雑談をするのだ。こうすることで、アシスタントはあなたのニーズを理解しやすくなり、的確なサポートを提供しやすくなる。
-
-### 背景を説明する
-
-コンテキストを提供することで、AIリキッドアシスタントはあなたのプロジェクトを取り巻く全体像を理解することができる。というような文脈を含めるとよい：
-
-- 会社名と業種
-- ブラックフライデーやホリデーセールなど、あなたが取り組んでいるキャンペーン
-- クリック率を上げるなど、あなたの目標
-- メッセージに含めたい特定のカスタム属性
-
-プロンプトに文脈を含めることで、アシスタントがあなたのニーズにより適した返答をできるようになる。また、キャンペーンやメッセージの概要、ブレーンストーミングの文書から詳細を盛り込み、アシスタントにスピードを上げてもらうこともできる。
-
-### 具体的に
-
-AIリキッド・アシスタントはフォローアップの質問をすることができるが、前もって詳細を提供することで、より正確な結果を早く得ることができる。などの詳細を含めることを検討する：
-
-- メッセージに対する既知の嗜好や要件がある場合
-- メッセージの受信者からの応答がない場合や、フォールバックメッセージオプションなどの状況に対処する方法を指示する。
-- コネクテッド・コンテンツを使用するリキッドを求める場合、APIエンドポイントのドキュメント、APIレスポンスのサンプル、またはその両方
-
-### クリエイティブになる
-
-AIリキッド・アシスタントがあなたのメッセージングをどのように向上させることができるか、プロンプトの枠にとらわれずに考えてみよう。創造性がより魅力的な結果につながるので、さまざまなプロンプトやアイデアを試してみよう。
-
-## プロンプトの例
-
-インスピレーションを探している？以下のプロンプトをチェックして、試してみてほしい（あるいは、好きなようにアレンジして）。
-
-### 一般情報
-
-- Liquidとは何か、Brazeのマーケティングキャンペーンのパーソナライゼーションを強化するのに役立つのか？
-- リキッドでは、人口統計情報や過去の購入履歴など、どのような種類のデータを使ってマーケティング・メッセージをパーソナライズできるのか？
-
-### パーソナライゼーションとダイナミック・コンテンツ
-
-- 顧客のロイヤリティ・ステータスに応じて異なるコンテンツを表示するメッセージを作成する。相手のロイヤリティの状況がわからない場合は、予備のメッセージを送る。
-- ユーザーの好きな商品と最終購入日を含むダイナミックメッセージを書く。最後の購入がなければ、メッセージを中断する。
-- 残り時間のカウントダウンを含む私のメッセージをクリックするよう促すリキッドを書いてくれ。オファーの有効期限が切れている場合は、メッセージを中止する。
-- カートに商品が残っている場合、ユーザーに再度チェックアウトを促すメッセージを書くのを手伝ってほしい。
-- 顧客の国に基づいてメッセージをパーソナライズするリキッドを書く。メッセージを国名で埋めたい。もしどちらも持っていなければ、リンクをクリックしてプロフィールを更新するよう勧める。
-- ユーザーのファーストネームでウェルカムメッセージをパーソナライズし、ユーザーの性別に応じて異なるコピーを書くにはどうすればよいか？
-- カスタム属性 "CUSTOM_ATTRIBUTE_NAME "とその値に基づいて異なるメッセージを表示するリキッドを書く。送れるオプションは6種類ある。カスタム属性に値がない場合は、プレースホルダ・メッセージを送りたい。
-
-### 具体的な使用例
-
-- エンゲージメントとコンバージョン率を高めるために、リキッドがマーケティングキャンペーンでどのように使われているか、いくつか例を挙げてくれる？
-- 夏のセールでリキッドにテキストメッセージを使う一般的なユースケースには、カート放棄のリマインダーやパーソナライズされたプロモーションなどがあるだろうか？
-
-興味深いプロンプトや経験があれば、[フィードバック・セッションを](https://research.rallyuxr.com/braze/schedule/clxxhw8em0d071ak4b279553s?channel=share)予約して知らせてほしい。
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/sage_ai/intelligence.md b/_lang/ja/_user_guide/sage_ai/intelligence.md
deleted file mode 100644
index 128b505c7dc..00000000000
--- a/_lang/ja/_user_guide/sage_ai/intelligence.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-nav_title: Intelligence Suite
-article_title: Intelligence Suite
-page_order: 10
-layout: dev_guide
-search_rank: 12
-guide_top_header: "Intelligence Suite"
-guide_top_text: "Braze Intelligence Suiteは、データに基づく洞察で意思決定の自動化を支援する。配信時間から多変量テストに至るまで、ブランドはこれらのツールや機能を使用して、スケールで最適化されたダイナミックなクロスチャネル体験を作り出すことができる。<br> <br> インテリジェンス・スイートは3つの主要機能で構成されている：インテリジェント・タイミング、インテリジェント・チャンネル、インテリジェント・セレクションだ。"
-description: "Braze Intelligence Suiteは、データに基づく洞察で意思決定の自動化を支援する。配信時間から多変量テストに至るまで、ブランドはこれらのツールや機能を使用して、スケールで最適化されたダイナミックなクロスチャネル体験を作り出すことができる。"
-
-Tool:
-  - Dashboard
-
-guide_featured_title: "ツールと機能"
-guide_featured_list:
-- name: インテリジェントタイミング
-  link: /docs/user_guide/sage_ai/intelligence/intelligent_timing/
-  image: /assets/img/braze_icons/clock.svg
-- name: インテリジェントチャネル
-  link: /docs/user_guide/sage_ai/intelligence/intelligent_channel/
-  image: /assets/img/braze_icons/mail-04.svg
-- name: インテリジェントセレクション
-  link: /docs/user_guide/sage_ai/intelligence/intelligent_selection/
-  image: /assets/img/braze_icons/hearts.svg
-
-guide_menu_title: "Additional resources"
-guide_menu_list:
-- name: インテリジェンスFAQ
-  link: /docs/user_guide/sage_ai/intelligence/faqs/
-  image: /assets/img/braze_icons/annotation-question.svg
-
-
----
-
-## ユースケース
-
-インテリジェンス・スイートは、ユーザー履歴やキャンペーン、キャンバスのパフォーマンスを分析し、エンゲージメント、視聴率、コンバージョンを高めるための自動調整を行う強力な機能を提供する。これらの機能がさまざまな業界にどのようなメリットをもたらすかについては、以下の使用例を参照されたい。
-
-### e コマース
-
-- **フラッシュセールだ：**[インテリジェント・チャネル・フィルターを使って]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_channel/)ユーザー履歴を調査し、プッシュ通知とEメールの反応が高いユーザーを特定し、それぞれのユーザーにプッシュ通知とEメールを送信する。オプションとして、好みのチャネルを決定するのに十分なデータがないユーザーのために、特定のチャネルを選択する。
-- **プロモーション用バナー：**[インテリジェントセレクションを]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_selection/)使用して、定期的なキャンペーンにおけるさまざまなプロモーションバナーのパフォーマンスを分析し、最も高いクリックスルー率を生み出すバナーを自動的に選択して送信する。
-
-### 旅行
-
-- **パッケージを提供する：**インテリジェントセレクションを使用して、繰り返しキャンバスでさまざまな旅行パッケージのオファーをテストし、キャンバスのトラフィックを最もパフォーマンスの高いバリアントに徐々にシフトさせることで、より高い予約率を促進する。
-- **お得な旅行情報：**インテリジェント・チャネル・フィルターを使用して、EメールやSMSなど、ユーザーの最もアクティブなチャネルを通じてパーソナライズされた旅行情報を送信し、ユーザーがメッセージングに参加する可能性を最大限に高める。
-
-### エンターテイメント
-
-- **新コンテンツのプロモーション：**[インテリジェント・タイミングを使って]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_timing/)、ユーザーがメッセージを開く可能性が最も高い時に、新しい映画、番組、音楽、その他のタイプのコンテンツに関する通知を送る。
-- **ゲーム内で購入する：**インテリジェントセレクションを使用して、ゲーム内購入のためのさまざまなプロモーションメッセージをテストし、最も高いコンバージョン率を生み出すものを自動的に選択する。
-
-### クイックサービスレストラン
-
-サンドイッチ・エンペラーというファストフード店で、期間限定の新メニュー「ロイヤル・ロースト」を作っているとしよう。Intelligence Suiteの2つの機能を使って、キャンバスにパーソナライズされたプロモーションを送る。
-
-#### 通知を送るタイミングにインテリジェント・タイミングを使う
-
-私たちは、インテリジェント・タイミングを使って、私たちのアプリと各メッセージング・チャネルに対するユーザーの過去のインタラクションを分析し、各ユーザーにロイヤル・ローストを宣伝する最適なタイミングを自動的に選択する。午後にプロモーションを受け取るユーザーもいれば、夕方に受け取るユーザーもいるだろう。 
-
-分析するのに十分な過去のインタラクションがないユーザーのために、フォールバック・タイムを提供する。
-
-![メッセージステップのインテリジェントタイミング配信設定。][1]
-
-#### インテリジェント・セレクションを使ってプロモーションを選択する
-
-実際の販促メッセージについては、Intelligent Selectionを使って、ロイヤル・ロースト用の3種類のメッセージ（プッシュ通知、Eメール、SMS）をテストする。インテリジェント・セレクションは、すべてのプロモーション・メッセージのパフォーマンスを1日2回分析し、最もパフォーマンスの高いメッセージを徐々に多く送り、その他のメッセージは少なくしていく。
-
-インテリジェント・セレクションは、十分なデータを収集し、最もパフォーマンスの高いメッセージを決定した後、今後送信するメッセージの100%にそのメッセージを使用する。
-
-![インテリジェントセレクションを有効にしたキャンバスのA/Bテストセクション。][3]
-
-#### キャンバスを立ち上げる
-
-インテリジェント・タイミングとインテリジェント・セレクションの両方により、ロイヤル・ロースト・プロモーションはタイミングとメッセージングが最適化されるように設定されている。キャンバスを立ち上げ、ユーザーの好みに合わせてセンドが変化していくのを見ることができる。
-
-[1]: {% image_buster /assets/img/intelligence_suite1.png %}
-[3]: {% image_buster /assets/img/intelligent_selection_canvas.png %}
diff --git a/_lang/ja/_user_guide/sage_ai/intelligence/faqs.md b/_lang/ja/_user_guide/sage_ai/intelligence/faqs.md
deleted file mode 100644
index 6d56e29e19d..00000000000
--- a/_lang/ja/_user_guide/sage_ai/intelligence/faqs.md
+++ /dev/null
@@ -1,103 +0,0 @@
----
-nav_title: FAQ
-article_title: インテリジェンスFAQ
-page_order: 191
-description: "この記事では、インテリジェント・チャンネル、インテリジェント・セレクション、インテリジェント・タイミングに関するよくある質問に対する回答を掲載している。"
----
-
-# よくある質問
-
-> この記事では、インテリジェンス・スイートに関するよくある質問に対する回答を提供する。
-
-## インテリジェントセレクション
-
-### インテリジェント・セレクションと併用した場合、なぜ24時間以内の再資格取得ができないのか？
-
-インテリジェント・セレクションのキャンペーンでは、あまりに短い期間での再選考は認めていない。24時間のギャップを設けることで、アルゴリズムが統計的に有効なデータセットを確実に使えるようにする。
-
-通常、再入会資格のあるキャンペーンでは、ユーザーは以前に受け取ったのと同じバリアントを再度入力することになる。インテリジェントセレクションでは、この機能のための最適配分という側面からバリアント配分がシフトしているため、Brazeはユーザーが同じキャンペーンバリアントを受け取ることを保証できない。インテリジェント・セレクションがバリアントのパフォーマンスを再調査する前に、ユーザーに再入力を許可した場合、再入力したユーザーによってデータが歪む可能性がある。
-
-例えば、あるキャンペーンが以下のようなバリアントを使用している場合だ：
-
-- バリアントA：20%
-- バリアントB：20%
-- コントロールする：60%
-
-そうすると、第2ラウンドのバリアント分布は次のようになる：
-
-- バリアントA：15%
-- バリアントB：25%
-- コントロールする：60%
-
-### キャンペーンの初期段階で、インテリジェントセレクションのバリアントが同じ送信数を表示するのはなぜか？
-
-インテリジェントセレクションは、キャンペーンコンバージョンの現在のステータスに基づいて、送信するバリアントを割り当てる。最終的なバリアントの割り当ては、バリアント間で均等にセンドが送られるトレーニング期間の後にのみ決定される。キャンペーンの初期段階でインテリジェントセレクションを均等に送信したくない場合は、従来のA/Bテストに固定バリアントを使用する。
-
-### インテリジェント・セレクションは、明確な勝者を選ぶことなく最適化をやめてしまうのだろうか？
-
-インテリジェント・セレクションは、実験を続けてもコンバージョン率が現在の1％以上改善されないと95％確信した時点で、最適化を中止する。
-
-### キャンバスやキャンペーンでインテリジェントセレクションを有効にできない（グレーアウトしている）のはなぜか？
-
-以下の場合、インテリジェントセレクションは利用できない：
-
-- キャンペーンまたはキャンバスにコンバージョンイベントを追加していない
-- 単一送信キャンペーンを作成している
-- 24時間未満のウィンドウでリレジビリティを有効にしている
-- あなたのキャンバスは単一のバリアントで構成され、バリアントやコントロールグループは追加されない。
-- あなたのキャンバスは、バリアントが加えられていない単一のコントロールグループで構成されている。
-
-## インテリジェントタイミング
-
-### インテリジェント・タイミングは、ユーザーがコンバージョンする可能性が最も高いタイミングを予測するのか、それともユーザーが開いたりクリックしたりする可能性が最も高いタイミングだけを予測するのか？
-
-インテリジェント・タイミングは、ユーザーが開いたりクリックしたりしそうなタイミングを予測する。
-
-### 最も人気のあるアプリの時間はどのように決まるのか？
-
-最も人気のあるアプリの時間は、ワークスペースの平均セッション開始時間（現地時間）によって決定される。この指標は、ダッシュボードでキャンペーンの時間をプレビューする際に確認することができ、赤色で表示される。
-
-### インテリジェント・タイミングはマシンのオープンを考慮しているか？
-
-そう、マシンのオープンはインテリジェント・タイミングによってフィルタリングされるため、出力には影響しない。
-
-### インテリジェント・タイミングを可能な限りうまく機能させるには？
-
-インテリジェント・タイミングは、各ユーザーがどのようなタイミングでメッセージを受信したかに関わらず、各ユーザーのメッセージのエンゲージメント履歴を使用する。インテリジェント・タイミングを使用する前に、1日の異なる時間帯にユーザーにメッセージを送信していることを確認する。そうすることで、各ユーザーにとってベストなタイミングを "サンプリング "することができる。異なる時間帯のサンプリングが不十分だと、インテリジェント・タイミングはユーザーにとって最適でない送信時間を選ぶことになる。 
-
-### インテリジェント・タイミング・キャンペーンをすべてのタイムゾーンのすべてのユーザーにうまく配信するには、どのくらい前にキャンペーンを開始すべきか？
-
-Brazeは、世界初のタイムゾーンのひとつであるサモア時間の真夜中に最適な時刻を計算する。1日では約48時間に及ぶ。例えば、最適時刻が午前12時1分で、オーストラリアに住んでいる人は、すでに最適時刻を過ぎており、その人に送るには「遅すぎる」。このような理由から、あなたのアプリを利用する世界中のすべての人に確実にアプリを届けるためには、48時間前にスケジュールを立てる必要がある。
-
-### なぜ私のインテリジェント・タイミング・キャンペーンはほとんど送信されないのか？
-
-ブレイズでは、適切な推定を行うために基準点数のデータが必要だ。十分なセッションデータがない場合、または対象となるユーザーのメールのクリック数や開封数がほとんどない場合（新規ユーザーなど）、Intelligent Timingは、その曜日のワークスペースの最も人気のある時間帯をデフォルトにすることがある。ワークスペースに関する十分な情報がない場合は、デフォルトの午後5時に戻る。特定の[フォールバック時間を]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_timing/#fallback-options)設定することもできる。
-
-### Intelligent Timingキャンペーンが予定日を過ぎて送信されるのはなぜか？
-
-インテリジェント・タイミング・キャンペーンは、A/Bテストを活用しているため、予定日を過ぎて送信されているかもしれない。A/Bテストを使用したキャンペーンでは、A/Bテスト終了後に自動的にWinning Variantを送信することができ、キャンペーン送信の期間が長くなる。デフォルトでは、Intelligent Timingキャンペーンは、翌日の残りのユーザーにWinning Variantを送信するようにスケジュールされるが、この送信日を変更することができる。
-
-インテリジェント・タイミング・キャンペーンを実施している場合は、A/Bテストが終了するまでの時間を多めにとり、ウィニング・バリアントを1日後ではなく2日後に送信するようスケジュールすることをお勧めする。 
-
-### Brazeは、セグメントとオーディエンスフィルターの適格性基準をいつチェックするのか？
-
-Brazeはキャンペーン開始時に2つのチェックを行う：
-
-1. 最初のタイムゾーンが特定されるとすぐに、ユーザーキュー処理を開始する。
-2. 予定時刻に、ユーザーがまだキャンペーンを受け取る資格があるかどうかを確認する。
-
-他のキャンペーンの送信をフィルタリングするキャンペーンを作成する場合は注意が必要だ。例えば、同じ日に異なる時間帯に2つのキャンペーンを配信し、1つ目のキャンペーンを受信したユーザーにのみ2つ目のキャンペーンの受信を許可するフィルターを追加した場合、ユーザーは2つ目のキャンペーンを受信しない。というのも、キャンペーンが最初に作られ、セグメントが形成された時点では、誰も対象者ではなかったからだ。
-
-### インテリジェント・タイミング・キャンペーンでクワイエット・アワーを使用できるか？
-
-キャンペーンやキャンバスで、インテリジェント・タイミングとクワイエット・アワーを両方使うのは逆効果なのでお勧めしない。クワイエットアワーはユーザーの行動に関するトップダウンの仮定に基づいているのに対し、インテリジェントタイミングはユーザーの活動に基づいている。
-
-### インテリジェント・タイミングとレート制限は使えるか？
-
-Brazeでは、インテリジェント・タイミングとレート制限の使用は推奨していない。
-
-### IPウォーミング中にインテリジェント・タイミングを使用できるか？
-
-Brazeは、ユーザーが初めてIPウォーミングを行う際に、インテリジェント・タイミングを使用することを推奨していない。これは、インテリジェント・タイミングがキャンペーン・セグメントを2回評価したことが原因である。キャンペーンが最初に構築されたときに1回、そしてユーザーに送信する前に2回目を行い、彼らがまだそのセグメントにいるべきかを確認する。 
-
-このため、セグメントがずれたり変更されたりすることがあり、2回目の評価でセグメントから外れてしまうユーザーが出てくることがよくある。これらのユーザーは入れ替わらないため、最大ユーザー数にどれだけ近づけることができるかに影響する。
diff --git a/_lang/ja/_user_guide/sage_ai/intelligence/intelligent_channel.md b/_lang/ja/_user_guide/sage_ai/intelligence/intelligent_channel.md
deleted file mode 100644
index 1a681717da5..00000000000
--- a/_lang/ja/_user_guide/sage_ai/intelligence/intelligent_channel.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-nav_title: インテリジェント・チャネル・フィルタ
-article_title: インテリジェント・チャネル・フィルタ
-page_order: 0
-description: "ここでは、インテリジェントチャネル フィルターについて説明します。インテリジェントチャネル フィルターは、選択したメッセージング チャネルが最適なチャネルであるオーディエンスの部分を選択するフィルターです。このケースでは、ユーザーの履歴を考慮すると、最良の方法でエンゲージメントする可能性が最も高くなります。"
-search_rank: 11
----
-
-# [![Brazeラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/most-engaged-channel){: style="float:right;width:120px;border:0;" class="noimgborder"}インテリジェントチャンネルフィルター
-
-> インテリジェントまたは`Most Engaged`チャネル フィルターは、選択したメッセージング チャネルが"best"チャネルであるオーディエンスの部分を選択します。 
-
-このケースでは、最善とは、ユーザーの履歴を所与として、エンゲージメントの可能性が最も高いチャネルを意味する。メール、SMS、Web プッシュ、またはモバイルプッシュ(利用可能なモバイルOS またはデバイスを含む)をチャネルとして選択できます。
-
-![][1]{: style="float:right;max-width:40%;margin-left:10px;margin-top:10px;border:0"}
-
-インテリジェントチャネルは、3 つのチャネルs それぞれのエンゲージメント率をユーザーごとに計算します。これは、過去6 か月間に受信されたメッセージの数に対するメッセージのアクション間s (開封s またはクリックs) の比率を取得することによって行われます。利用可能なチャネルs はそれぞれのエンゲージメント比率に応じてランク付けされ、最も比率が高いチャネルは" 最もEngaged" のユーザーです。 
-
-メッセージがユーザーに送信されるたびに、またはユーザーがメッセージとやり取りするたびに、エンゲージメント率が数秒で再計算されます。ユーザーは、メッセージとのインタラクションとして1 回だけカウントできます(たとえば、同じメールを開封してクリックすると、そのメッセージは2 回ではなく1 回だけ関与したものとしてマークされます)。 
-
-インテリジェントチャネルフィルターを有効にするには、メール、Web プッシュ、またはモバイルプッシュキャンペーンの作成時に**Target Users** ページで**インテリジェントチャネル** フィルターを選択します。
-
-{% alert important %}
-SMS チャネルのエンゲージメント速度を計算するには、詳細"トラッキングで[SMS リンク短縮]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#overview/) を有効にして"トラッキング を選択します。
-{% endalert %}
-
-## "十分でないデータ"オプション
-
-Brazeが"best"のチャネルを決定するには、十分なデーターが必要です。つまり、ユーザーは、使用可能な3 つのチャネルs のうち少なくとも2 つのメッセージを少なくとも3 つ以上受信している必要があります。必ずしも開封されている必要はありません。 
-
-ユーザーがチャネルs 全体で十分なメッセージを受信していない場合、これらのユーザーs は"Not Enough Data" オプションのフィルターになります。これにより、3 つの使用可能なメッセージング チャネルs のいずれかを使用して、これらのユーザーs を対象とすることができます。
-
-たとえば、プッシュメッセージを好むユーザーに、同じプッシュメッセージを受信するのに十分なデータがないプッシュおよびユーザーを受信させるとします。このような場合は、インテリジェントチャネルフィルターを**モバイル**に設定し、**OR**を使用して、**Not Enough Data**に設定された2番目のインテリジェントチャネルフィルターを追加できます。インテリジェント・チャンネル・フィルターをメールに設定した別のキャンペーンは、メールを好むユーザーに対応できます。
-
-![][2]
-
-{% alert note %}
-[フリークエンシーキャップ]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#delivery-rules)を無視するキャンペーンおよびキャンバスステップは、インテリジェントチャネルによって考慮されず、データ要件に寄与できません。
-{% endalert %}
-
-## "Mobile push"オプション
-
-モバイルプッシュには、Android、iOS、Kindle、およびBrazeで利用可能な他のモバイルデバイスチャネルが組み込まれています。インテリジェントチャンネルを計算するとき、Braze はそれぞれの種類のモバイルデバイスを別々に調べ、その中で最も高いエンゲージメント率を選択して"Mobile Push"カテゴリをメール およびWeb プッシュと比較します。 
-
-たとえば、ユーザーに複数のモバイルデバイスがある場合、そのモバイルエンゲージメント速度はデバイス全体で表示される最高速度で表されます。しかし、これは、ユーザーがその装置上で排他的にプッシュ通知sを受信することを強制しません。このレートは、レートをメールおよびWeb プッシュと比較する場合にのみ使用されます。
-
-## 個別チャネル
-
-Brazeがチャネルを1つのユーザーに対して選択するのではなく、選択したチャネルにメッセージを開封するかどうかに基づいて単にsをフィルター ユーザーすることもできます。そのためには、[セグメンテーションフィルターs]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters)でメッセージオープン尤度フィルターを使用できます。
-
-## ベストプラクティスと効果的な使用戦略
-
-### タイブレイク
-
-ユーザーによっては、受信されるメッセージの数が少ないため、特定のユーザーの利用可能なエンゲージメントレートs に関係があることは珍しくありません(たとえば、単一のユーザーは**両方の**メールとモバイルプッシュに対して0.2 エンゲージメントレートを持っています)。このような場合、最新の開封事象を持つチャネルを優先順位付け(より高い順位付け)することで、関係が崩れてしまいます。
-
-### 到達不能チャネル
-
-ユーザーがランク付けを決定するのに十分なデータを持っているが、最もエンゲージしたチャネルで到達不能になった場合、ユーザーは"fall out"およびメッセージを受信しません。特定のチャネルに到達できないユーザは、個別にターゲットを設定する必要があります。
-
-### オーディエンスのサイジング
-
-インテリジェントチャンネルを使用すると、オーディエンスの残りの部分よりもメッセージに関与する可能性がはるかに高いユーザーのアクションを事前に選択的に標的にすることができます。これは、典型的なオーディエンスにおけるユーザーsの大部分を代表するとは考えにくい。むしろ、このフィルターは、特定のチャネルに従事した実績があるあなたの普段のオーディエンスから5-20%を見つけることができると期待できます。
-
-
-[1]: {% image_buster /assets/img/intelligent_channel_filter.png %} "インテリジェントチャネルフィルタ&クォート;
-[2]: {% image_buster /assets/img/intelligent_example.png %}
diff --git a/_lang/ja/_user_guide/sage_ai/intelligence/intelligent_selection.md b/_lang/ja/_user_guide/sage_ai/intelligence/intelligent_selection.md
deleted file mode 100644
index 12aa8bd53d4..00000000000
--- a/_lang/ja/_user_guide/sage_ai/intelligence/intelligent_selection.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-nav_title: インテリジェントセレクション
-article_title: インテリジェントセレクション
-page_order: 1
-description: "この記事では、インテリジェント・セレクションについて説明する。インテリジェント・セレクションは、1日に2回、定期的なキャンペーンやキャンバスのパフォーマンスを分析し、各メッセージのバリエーションを受け取るユーザーの割合を自動的に調整する機能である。"
-search_rank: 10
----
-
-# インテリジェントセレクション {#intelligent-selection}
-
-> インテリジェント・セレクションは、定期的なキャンペーンやキャンバスのパフォーマンスを1日2回分析し、各メッセージのバリエーションを受け取るユーザーの割合を自動的に調整する機能である。 
-
-他よりもパフォーマンスが良いと思われるバリアントは、より多くのユーザーに送られ、パフォーマンスの低いバリアントは、より少ないユーザーにターゲットとされる。各調整は\[統計的アルゴリズム][227] ]を使って行われ、単なるランダムな偶然ではなく、実際のパフォーマンスの違いを調整していることを確認する。
-
-![インテリジェントセレクションを有効にしたキャンペーンのA/Bテストセクション。][3]
-
-インテリジェントセレクションは以下のことを行います。
-- パフォーマンスデータを繰り返し見て、キャンペーンのトラフィックを徐々にWinning Variantsにシフトさせる。
-- 統計的な信頼性を犠牲にすることなく、より多くのユーザーが最もパフォーマンスの高いバリアントを受け取れるようにする。
-- [従来のA/Bテストよりも][1]早く、パフォーマンスの低いバリアントを除外し、パフォーマンスの高いバリアントを特定する。
-- より頻繁にテストを行い、ユーザーが最高のメッセージを目にすることをより確信できるようにする。 
-
-インテリジェント・セレクションは、複数回送信するようスケジュールされているキャンペーンに最適である。キャンペーンを調整し始めるには、最初の結果が必要である。従って、一度しか送信しないキャンペーンは有益ではない。こうしたキャンペーンでは、[A/Bテストが][1]より効果的だろう。
-
-## キャンペーンにインテリジェント・セレクションを追加するには？
-
-### キャンペーン・インテリジェント・セレクション
-インテリジェントセレクションは、Brazeのキャンペーンコンポーザーの**ターゲットオーディエンスの**ステップで、マルチ送信キャンペーンに追加することができる。一度しか送信しないキャンペーンは、この機能を利用できない。
-
-### キャンバス・インテリジェント・セレクション
-キャンバスにバリアントを追加するとき、バリアントパーセンテージの一つをクリックする。これにより、バリアント分布を編集し、インテリジェントセレクションをオンにすることができる。
-
-![キャンバスには2つのバリアントがあり、それぞれ50％のバリアント分布に設定されている。][2]
-
-キャンバスにまだコンバージョンイベントを追加していない場合、またはキャンペーンがソロバリアントで構成されている場合、インテリジェントセレクションは利用できない。
-
-{% alert note %}
-私たちは、24時間以内に再入会資格が有効になるキャンペーンでのインテリジェントセレクションの使用を許可していない。詳しくは[インテリジェンスFAQを]({{site.baseurl}}/user_guide/intelligence/faqs/#why-is-re-eligibility-not-available-when-combined-with-intelligent-selection)ご覧いただきたい。
-{% endalert %}
-
-## いつまで走るのか？
-
-キャンペーンとキャンバスでは、インテリジェントセレクションは、バリアントの「真の」コンバージョン率について十分な証拠を集めるまで実行される。"十分 "は "後悔 "と呼ばれる特別な尺度によって決定される。インテリジェント・セレクションは、どのバリアントがベストかを知るのに十分なデータがあれば、勝手にオフになるという点で、確信に似ていると考えることができる。 
-
-ほとんどの場合、Intelligent SelectionはいずれかのバリエーションをWinning Variantとして選ぶ。このバリアントは、今後送信される観客の100％に与えられる。
-
-{% alert note %}
-インテリジェント・セレクションが、明確な勝者を1人も選ばずに最適化をやめてしまうことはあり得る。インテリジェント・セレクションは、実験を続けてもコンバージョン率が現在の1％以上改善されないと95％確信した時点で、最適化を中止する。
-{% endalert %}
-
-[1]: {{site.baseurl}}/user_guide/intelligence/multivariate_testing/
-[2]: {% image_buster /assets/img/intelligent_selection.png %}
-[3]: {% image_buster /assets/img/intelligent_selection1.png %}
-\[227] ： https://en.wikipedia.org/wiki/Multi-armed_bandit
-
diff --git a/_lang/ja/_user_guide/sage_ai/intelligence/intelligent_timing.md b/_lang/ja/_user_guide/sage_ai/intelligence/intelligent_timing.md
deleted file mode 100644
index f0d9a53f990..00000000000
--- a/_lang/ja/_user_guide/sage_ai/intelligence/intelligent_timing.md
+++ /dev/null
@@ -1,207 +0,0 @@
----
-nav_title: インテリジェントタイミング
-article_title: インテリジェントタイミング
-page_order: 2
-description: "この記事では、インテリジェント・タイミング（旧インテリジェント・デリバリー）の概要と、キャンペーンやキャンバスでこの機能を活用する方法について説明する。"
-
----
-
-# [![Brazeラーニングコース]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/intelligent-timing){: style="float:right;width:120px;border:0;" class="noimgborder"}インテリジェントタイミング
-
-> インテリジェントタイミングを使用して、Brazeが最適な送信時刻と呼ぶ、ユーザーが最も関心を持つ（開封またはクリックする）可能性が高いと判断したときに、各ユーザーにメッセージを配信する。これにより、ユーザーの希望する時間帯にメッセージを送っているかどうかを簡単にチェックすることができ、エンゲージメントの向上につながる。
-
-## ユースケース
-
-- 時間に制約のないキャンペーンを定期的に送る
-- 複数のタイムゾーンのユーザーとのキャンペーンを自動化する
-- 最もエンゲージメントの高いユーザーにメッセージを送る場合（彼らが最もエンゲージメントデータを持っているはずだ）
-
-## その仕組み
-
-Brazeは、ユーザーの過去のアプリとのやり取りや、各メッセージングチャンネルとのやり取りの統計分析に基づいて、最適な送信時間を計算する。
-
-例えば、サムは朝に定期的にあなたのEメールを開くかもしれないが、夕方にはあなたのアプリを開き、通知とやりとりする。つまり、サムは朝にインテリジェント・タイミングを使ったEメール・キャンペーンを受け取り、夕方にはプッシュ通知を使ったキャンペーンを受け取ることになる。
-
-Brazeが最適な送信時間を計算するのに十分なエンゲージメントデータをユーザーが持っていない場合、[フォールバック時間を](#fallback-time)指定することができる。さらに、マシンオープンは、最適な時間を計算する目的から除外される。
-
-## インテリジェント・タイミングを使う
-
-このセクションでは、キャンペーンとキャンバスにインテリジェントタイミングを設定する方法について説明する。
-
-### キャンペーン
-
-キャンペーンにインテリジェント・タイミングを使用する：
-
-1. キャンペーンを作成し、メッセージを作成する。
-2. 配送タイプとして「**定期配送**」を選択する。
-3. **Time-Based Scheduling Options（時間ベースのスケジューリングオプション**）」で、**Intelligent Timing（インテリジェントタイミング**）を選択する。
-4. 送信日を選択する。考慮すべき点については、[キャンペーンのニュアンスを](#campaign-nuances)参照のこと。
-5. [特定の時間内にのみメッセージを送信](#sending-within-specific-hours)するかどうかを決定する。
-6. [フォールバック時間を](#fallback-time)指定する。ユーザーのプロフィールに最適な時間を計算するのに十分なデータがない場合、このタイミングでメッセージが送信される。
-
-![インテリジェント・タイミングでキャンペーンをスケジューリングする][1]
-
-#### 特定の時間内にメッセージを送信する {#sending-within-specific-hours}
-
-必要であれば、最適な時間を特定の時間内に制限することもできる。これは、キャンペーンが特定のイベント、セール、プロモーションに関するものであれば有効だが、そうでない場合は一般的に推奨されない。特定の時間内に送信することは、クワイエットアワーと同様に機能するが、インテリジェントタイミングでは逆効果となるため推奨されない。詳しくはこの記事の[制限の](#limitations)セクションを参照のこと。
-
-1. インテリジェント・タイミングを設定する際、「**特定の時間内にのみメッセージを送信する**」を選択する。
-2. 配信ウィンドウの開始時刻と終了時刻を入力する。
-
-![特定の時間内にのみメッセージを送信する」のチェックボックスを選択し、時間ウィンドウをユーザーの現地時間で午前8時から午前12時の間に設定する。][4]
-
-配信ウィンドウが指定されると、Brazeはウィンドウ内のエンゲージメントデータのみを見て、ユーザーの最適な時間を決定する。そのウィンドウ内に十分なエンゲージメント・データがない場合、メッセージは指定された[フォールバック・タイムに](#fallback-time)送信される。
-
-#### 納期プレビュー
-
-1日の各時間帯に何人のユーザーがメッセージを受信するかの概算を見るには、プレビューチャートを使用する（キャンペーンのみ）。
-
-1. ターゲットオーディエンスのステップでセグメントまたはフィルタを追加する。
-2. **配信時間のプレビュー]**セクション（\[ターゲットオーディエンス]と\[配信のスケジュール]ステップの両方に表示される）で、チャンネルを選択する。
-3. **データの更新を**クリックする。
-
-![][2]
-
-Intelligent Timingまたはキャンペーンオーディエンスの設定を変更した場合は、データを再度更新して最新のチャートを表示する。
-
-グラフは、最適な時間を計算するのに十分なデータがあったユーザーを青で、フォールバック時間を使用するユーザーを赤で示している。計算フィルターを使用して、プレビュー表示を調整し、どちらのユーザーグループもより詳細に見ることができる。
-
-#### キャンペーンのニュアンス
-
-Intelligent Timingでキャンペーンをスケジューリングする際に注意すべきニュアンスをいくつか紹介しよう。
-
-##### キャンペーンを開始する
-
-送信予定日の48時間前までにキャンペーンを開始する。これはタイムゾーンの違いによるものだ。Brazeは、世界で最初のタイムゾーンのひとつであるサモア時間（UTC+13）の真夜中に最適な時刻を計算する。つまり、48時間以内にキャンペーンを開始すると、ユーザーのタイムゾーンで最適な時間がすでに過ぎてしまい、メッセージが送信されない可能性がある。
-
-{% alert important %}
-キャンペーンが開始され、ユーザーの最適時間が過去1時間以内であれば、メッセージは即座に配信される。最適な時間が1時間以上過ぎている場合、メッセージはまったく送信されない。
-{% endalert %}
-
-##### セグメントを選ぶ
-
-ある期間にアクションを実行したオーディエンスをターゲットにしている場合は、セグメントフィルターに少なくとも3日間のウィンドウを設定する。例えば、`First used these apps more than 1 day ago` と`First used these apps less than 3 days ago` の代わりに、1日と4日を使う。
-
-![キャンペーンが1日～4日前にこれらのアプリを初めて使用したユーザーをターゲットとするターゲットオーディエンスのフィルター。][3]
-
-3日未満の期間を選択すると、最適な送信時刻に到達する前にセグメントから外れてしまうユーザーが出てくる可能性がある。
-
-[Brazeがセグメントとフィルターの適格性基準をチェックするタイミングについて]({{site.baseurl}}/user_guide/intelligence/faqs/#when-does-braze-check-the-eligibility-criteria-for-segment-and-audience-filters)詳しく知る。
-
-##### 最適化されたA/Bテスト
-
-[A/Bテストを最適化で]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign/#optimizations)活用する場合、例えばA/Bテスト終了後に自動的にWinning Variantを送信するような場合、キャンペーンの期間は長くなる。デフォルトでは、Intelligent Timingキャンペーンは、最初のテストの翌日に残りのユーザーにWinning Variantを送信するが、この送信日を変更することができる。
-
-Intelligent TimingとA/Bテストの両方を使用している場合は、最初のテストの1日後ではなく、2日後にWinning Variantを送信するようにスケジュールすることをお勧めする。
-
-![Target AudiencesステップのA/B Testingセクションでテストを終了し、最初のテスト開始から2日後にWinning Variantを送信する。][5]
-
-### キャンバス
-
-このセクションでは、キャンバスでインテリジェント・タイミングを使用する方法について説明する。使用するCanvasワークフローによって手順は若干異なる。
-
-{% alert important %}
-2023 年 2 月 28 日以降、元のエディターを使用したキャンバスの作成や複製はできなくなりました。このセクションは、インテリジェント・タイミングがオリジナル・エディターでどのように機能するかを理解するための参考資料として利用できる。<br><br>Braze では、従来のキャンバスエクスペリエンスを使用しているお客様に、キャンバスフローへの移行をお勧めしています。これは、キャンバスの構築と管理をより良く行う目的で改良された編集エクスペリエンスです。「[キャンバスからキャンバスフローへの複製]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases/)」を参照してください。
-{% endalert %}
-
-{% tabs %}
-{% tab キャンバスの流れ %}
-
-キャンバスフローでは、インテリジェントタイミングはメッセージステップで設定される。キャンバスでインテリジェント・タイミングを使用する：
-
-1. キャンバスに[メッセージ・ステップを]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/)追加する。
-2. **配信設定に**進む。
-3. **Using Intelligent Timingを**選択する。
-4. [フォールバック時間を](#fallback-time)指定する。
-
-このステップにエントリーしたユーザーは、エントリーした日の最適な時間に、その時間がまだ経過していなければ、メッセージを受け取る。なお、ユーザーがメッセージ・ステップを入力した日に最適な時間（現地時間）を過ぎていた場合は、翌日の最適な時間に送信される。複数のチャンネルを対象とするメッセージ・ステップでは、異なるチャンネルに対して異なる時間にメッセージを送信したり、送信しようとしたりすることがある。Messageステップの最初のメッセージを送信しようとすると、すべてのユーザーが自動アドバンスされる。
-
-#### ディレイ・ステップとインテリジェント・タイミング
-
-[Delayステップの]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/delay_step/)後にIntelligent Timingを使用する場合、遅延の計算方法によって納期が異なる場合がある。日」と「暦日」では計算方法に違いがあるため、これは、ディレイを「**期間を指定する**」に設定した場合にのみ適用される。
-
-- **日間だ：**1日は24時間で、ユーザーがDelayステップを入力した時間から計算される。
-- **暦日：**1日とは、ユーザーがDelayステップを入力してから、そのタイムゾーンの真夜中までの期間である。これは、1暦日が数分という短さであることを意味する。
-
-インテリジェント・タイミングを使用する場合、遅延には24時間ではなく暦日を使用することを推奨する。なぜなら、暦日の場合、メッセージは遅延の最終日に最適なタイミングで送信されるからだ。1日が24時間であれば、ユーザーの最適な時間はステップに入る前である可能性があり、つまり、遅延に1日追加されることになる。
-
-例えば、ルカの最適な時間が午後2時だとする。彼は3月1日午後2時1分にディレイのステップに入り、ディレイは2日に設定されている。
-
-- 初日は3月2日午後2時1分まで
-- 2日目は3月3日午後2時1分まで
-
-しかし、インテリジェント・タイミングは午後2時に配達することになっており、すでに午後2時を過ぎている。だから、ルカがメッセージを受け取るのは翌日になる：3月4日午後2時だ。
-
-![ユーザーの最適時刻が午後2時であるにもかかわらず、午後2時1分に遅延ステップに入り、遅延が2日に設定された場合の、日とカレンダーの日の違いを表したグラフ。Daysは、ユーザーが最適な時間より後にステップに入ったため、3日後にメッセージを配信するのに対し、calendar daysは2日後、遅延の最終日にメッセージを配信する。]({% image_buster /assets/img/intelligent_timing_daysvcalendardays.png %}){: style="border:none;"}
-
-{% endtab %}
-{% tab オリジナル・キャンバスのワークフロー %}
-
-オリジナルのCanvasワークフローでは、インテリジェントタイミングはフルステップのディレイセクションで設定される。キャンバスでインテリジェント・タイミングを使用する：
-
-1. キャンバスにステップを追加します。
-2. ステップの**ディレイを**開く。
-3. **スケジュールを**選択する。
-4. *after*、*in*、*on nextを使って*ディレイを設定する。
-   - *afterを*選択した場合は、日または週単位で遅延を設定する。遅延は暦日を使って自動的に計算されるため、メッセージは遅延の最終日にユーザーの最適な時間に送信される。インテリジェント・タイミングは、1日未満の遅延には利用できない。
-5. **Using Intelligent Timingを**選択する。
-6. [フォールバック時間を](#fallback-time)指定する。
-
-{% endtab %}
-{% endtabs %}
-
-#### キャンバスを起動する
-
-キャンペーンとは異なり、キャンバスを送信日の48時間前に立ち上げることを心配する必要はない。これは、インテリジェント・タイミングがキャンバス・レベルではなく、ステップ・レベルで設定されるためである。その代わり、インテリジェント・タイミングが使用される場合、ユーザーがキャンバスを入力してからステップを受け取るまで、少なくとも48時間の遅延があることを推奨する。
-
-### フォールバック時間 {#fallback-time}
-
-Brazeが最適な送信時間を計算するのに十分なエンゲージメントデータを持っていないオーディエンスのユーザーにメッセージを送信するための予備時間を選択する必要がある。選択肢は2つある：
-
-- 全ユーザーの中で、アプリを使用する最も人気のある時間帯
-- 特定のカスタムフォールバック時間（ユーザーのローカルタイムゾーンで）
-
-#### 最も人気のあるアプリの時間
-
-最も人気のあるアプリの時間は、ワークスペースの平均セッション開始時間（現地時間）によって決定される。この時間は、[プレビュー・チャート](#preview-delivery-times)（キャンペーンのみ）で赤く表示される。
-
-キャンペーンの場合、[配信ウィンドウを](#sending-within-specific-hours)指定し、アプリの利用が最も多い時間帯がそのウィンドウの外にある場合、メッセージは配信ウィンドウの端に最も近いところに送信される。例えば、配信ウィンドウが午後1時から午後8時で、最も人気のあるアプリの時間が午後10時であれば、メッセージは午後8時に送信される。
-
-**セッションデータが足りない**<br>
-まれに、アプリが最も使用されている時間を計算するのに十分なセッションデータがアプリにない場合（データがない完全に新しいアプリ）、メッセージはユーザーのローカルタイムゾーンで午後5時に送信される。ユーザーの現地時間が不明な場合、あなたの会社のタイムゾーンでは午後5時に送信される。
-
-データが限られているユーザーのライフサイクルの初期にインテリジェント・タイミングを使用することの限界に注意することが重要である。記録されたセッションが少ないユーザーであっても、その行動についての洞察を提供することができるのだから。しかし、Brazeはユーザーのライフサイクルの後半で、より効果的に最適な送信時間を計算することができる。
-
-#### カスタムフォールバックタイム
-
-カスタムフォールバックタイムを使用して、メッセージを送信する別の時間を選択する。最も人気のあるアプリの時間と同様に、メッセージはユーザーのローカルタイムゾーンでのフォールバックタイムで送信される。ユーザーのローカルタイムゾーンが不明な場合は、あなたの会社のタイムゾーンで送信される。
-
-カスタムフォールバックタイムが指定されたキャンペーンでは、送信日から24時間以内にキャンペーンを開始した場合、最適な時間がすでに経過しているユーザーはカスタムフォールバックタイムにキャンペーンを受信する。相手のタイムゾーンでカスタムフォールバックタイムがすでに経過している場合、メッセージは即座に送信される。
-
-## 制限事項
-
-- アプリ内メッセージ、コンテンツカード、ウェブフックは即座に配信され、最適な時間は与えられない。
-- インテリジェントタイミングは、アクションベースまたはAPIトリガーのキャンペーンでは利用できない。
-- インテリジェント・タイミングは、以下のシナリオでは使用すべきではない：
-    - **静かな時間だ：**クワイエット・アワーとインテリジェント・タイミングの両方を使うのは逆効果だ。クワイエット・アワーは、夜中に誰かにメッセージを送らないなど、ユーザーの行動に関するトップダウンの仮定に基づいているのに対し、インテリジェント・タイミングはユーザーの活動に基づいているからだ。サムは午前3時にアプリの通知をよくチェックしているのかもしれない。私たちは裁かない。
-    - **レート制限:**レート制限とインテリジェント・タイミングの両方が使用されている場合、メッ セージがいつ配信されるかは保証されない。インテリジェントタイミングを使用した日次反復キャンペーンは、メッセージ送信総数の上限を正確にサポートしない。
-    - **IP温暖化キャンペーン**インテリジェント・タイミングの動作の中には、IPのウォームアップを始めたばかりのときに必要なデイリー・ボリュームを達成するのが難しくなるものがある。これは、インテリジェント・タイミングが、キャンペーンやキャンバスを最初に作成したときと、ユーザーに送信する前に、2回セグメントを評価し、ユーザーがそのセグメントに属しているかどうかを確認するためである。このため、セグメントがずれたり変更されたりすることがあり、2回目の評価でセグメントから外れてしまうユーザーが出てくることがよくある。これらのユーザーは入れ替わらないため、最大ユーザー数にどれだけ近づけることができるかに影響する。
-
-## トラブルシューティング
-
-### 数少ないユーザーの最適タイムを示すプレビュー・チャート
-
-Brazeが適切な見積もりをするためには、ある程度のエンゲージメントデータが必要だ。十分なセッションデータがない場合、または対象ユーザーのクリックや開封がほとんどない場合（新規ユーザーなど）、Brazeはフォールバックタイムをデフォルトとする。設定によっては、これは最も人気のあるアプリの時間か、カスタムのフォールバック時間になる。
-
-### 送信予定日を過ぎて送信する
-
-インテリジェントタイミングキャンペーンは、[最適化でA/Bテストを]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign/#optimizations)活用している場合、予定日を過ぎて送信される可能性がある。A/Bテストの最適化を使用したキャンペーンでは、最初のテストが終わった後、自動的にWinning Variantを送信し、キャンペーンの期間を長くすることができる。デフォルトでは、最適化されたキャンペーンは、最初のテストの翌日に残りのユーザーにウィニングバリアントを送信するが、この送信日を変更することができる。
-
-Intelligent Timingを使用する場合は、A/Bテストが終了するまでの時間を多めにとり、最初のテストから1日後ではなく、2日後にWinning Variantを送信するようにスケジュールすることを推奨する。
-
-
-[1]: {% image_buster /assets/img/intelligent_timing_1.png %}
-[2]: {% image_buster /assets/img/intel-timing-preview.png %}
-[3]: {% image_buster /assets/img/intelligent_timing.png %}
-[4]: {% image_buster /assets/img/intelligent_timing_hours.png %}
-[5]: {% image_buster /assets/img/intelligent_timing_ab_test_duration.png %}
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite.md b/_lang/ja/_user_guide/sage_ai/predictive_suite.md
deleted file mode 100644
index 4b87d44119f..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-nav_title: Predictive Suite
-article_title: Predictive Suite
-page_order: 5
-layout: dev_guide
-search_rank: 3
-guide_top_header: "Predictive Suite"
-guide_top_text: "Braze Predictive Suiteは、追加の開発を必要とせずに機械学習ツールを手に入れることができます。解約予測と予測イベント（以前は予測購入）は、Brazeプラットフォーム内でデータをシームレスに活用し、行動に移すために数分で作成できるカスタマイズ可能なオンデマンド予測モデルです。<br><br>これらの機能について詳しく知るには、次の記事をご覧ください。"
-description: "このランディングページは、Brazeでのすべての予測のための場所です！Braze Predictive Suiteは、BrazeキャンペーンおよびCanvases内での解約およびイベント予測のソリューションを提供します。"
-
-guide_featured_title: "特徴"
-guide_featured_list:
-- name: 解約予測
-  link: /docs/user_guide/sage_ai/predictive_suite/predictive_churn/
-  image: /assets/img/braze_icons/lightbulb-02.svg
-- name: 予測イベント
-  link: /docs/user_guide/sage_ai/predictive_suite/predictive_events/
-  image: /assets/img/braze_icons/stars-01.svg
----
-
-{% alert tip %}
-予測を生成し、その予測に基づいてユーザーをターゲットにすることは、データポイントを消費しません。
-{% endalert %}
-
-<br><br>
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn.md
deleted file mode 100644
index 9c2a4503393..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-nav_title: 解約予測
-article_title: 解約予測
-page_order: 6.4
-layout: dev_guide
-alias: /predictive_churn/
-search_rank: 2
-guide_top_header: "解約予測"
-guide_top_text: "顧客離職率や顧客喪失率とも呼ばれる顧客離れは、成長企業にとって最も重要な指標の一つである。解約に対処するための適切なツールを持つことは、損失を最小限に抑え、顧客維持を最大化する上で極めて重要である。Brazeは、このような潜在的なユーザー離脱に先手を打つため、将来のユーザー離脱を最小限に抑えるプロアクティブアプローチを提供するPredictive Churnを提供している。"
-description: "このランディングページでは、ビジネスにとっての解約とは何か、解約を防ぎたいユーザーを定義できるツール、Predictive Churnを取り上げる。"
-
-guide_featured_title: "トピック"
-guide_featured_list:
-- name: 解約予測の作成
-  link: /docs/user_guide/sage_ai/predictive_suite/predictive_churn/creating_a_churn_prediction/
-  image: /assets/img/braze_icons/settings-01.svg
-- name: 予測分析
-  link: /docs/user_guide/sage_ai/predictive_suite/predictive_churn/prediction_analytics/
-  image: /assets/img/braze_icons/bar-chart-01.svg
-- name: ユーザーへのメッセージング
-  link: /docs/user_guide/sage_ai/predictive_suite/predictive_churn/messaging_users/
-  image: /assets/img/braze_icons/arrow-narrow-right.svg
-- name: トラブルシューティング
-  link: /docs/user_guide/sage_ai/predictive_suite/predictive_churn/prediction_faq/
-  image: /assets/img/braze_icons/annotation-question.svg
-
----
-
-## 概要
-
-![解約の概要。過去のデータを使ったトレーニングによる過去の予測視聴者を含む。これは、今日の予測視聴者を解約リスクスコアで測定することで、将来の解約リスクを予測することに貢献する。][1]
-
-> Predictive Churnでは、ビジネスにとっての解約とは何か[（解約定義]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/creating_a_churn_prediction/#step-2-define-churn)）と、解約を防ぎたいユーザー[（予測対象者]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/creating_a_churn_prediction/#step-3-filter-your-prediction-audience)）を定義することができる。予測を作成すると、Brazeは[勾配ブースティング決定木を](https://en.wikipedia.org/wiki/Gradient_boosting)使用して機械学習モデルを訓練し、あなたの定義に従って解約したユーザーと解約しなかった過去のユーザーの活動パターンから学習して、解約リスクのあるユーザーを特定する。
-
-予測モデルが構築されると、予測対象ユーザーには、あなたの定義に従って解約する可能性を示す0から100の間の[解約リスクスコア]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/prediction_analytics/#churn_score)が割り当てられます。スコアが高ければ高いほど、ユーザーが解約する可能性は高くなる。 
-
-予測対象者のリスクスコアの更新は、[選択した頻度で]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/creating_a_churn_prediction/#step-4-choose-the-update-frequency-for-churn-predictions)行うことができる。こうすることで、実際に解約される前に、解約リスクのあるユーザーに接触し、解約を未然に防ぐことができる。最大3つのアクティブな予測を使用することで、Predictive Churnを活用して個々のモデルを調整し、最も価値があると思われるユーザーの特定のセグメントにおける解約防止を支援することができる。
-
-## 解約予測にアクセスする
-
-**予測」**ページは**「アナリティクス」**セクションにある。完全なアクセスについては、アカウント・マネージャーに連絡すること。
-
-{% alert note %}
-古いナビゲーション を使用している場合は、\[**エンゲージメント**] の下に \[[位置情報]({{site.baseurl}}/navigation)] が表示されます。
-{% endalert %}
-
-この機能を購入する前に、プレビュー・モードで利用できる。これにより、合成データを使った解約予測のデモを見ることができ、ユーザーデータに基づいて解約予測モデルを一度に1つ作成することができる。このプレビューでは、解約リスクに応じてユーザーをメッセージングのターゲットにすることはできず、作成後も定期的に更新されることはない。
-
-プレビューを使えば、1つの予測を編集して再構築したり、アーカイブして他の予測を作成し、異なる[定義の]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/creating_a_churn_prediction/#step-2-define-churn) [予測品質を]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/)テストすることもできる。
-
-<br><br>
-
-[1]: {% image_buster /assets/img/churn/churn_overview.png %}
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/creating_a_churn_prediction.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/creating_a_churn_prediction.md
deleted file mode 100644
index d4f3e881aed..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/creating_a_churn_prediction.md
+++ /dev/null
@@ -1,113 +0,0 @@
----
-nav_title: 解約予測の作成
-article_title: 解約予測の作成
-description: "この記事では、Brazeダッシュボード内で解約予測を作成する方法について説明します。"
-page_order: 1
-
----
-
-# 解約予測の作成
-
-> Brazeダッシュボード内で解約予測を作成する方法を学びます。
-
-## ステップ 1:新しい予測を作成する
-
-Braze で、**分析** > **解約予測** に移動します。
-
-{% alert note %}
-古いナビゲーションを使用している場合、予測はエンゲージメントの下にあります。
-{% endalert %}
-
-予測は、訓練された機械学習モデルの1つのインスタンスであり、それが使用するすべてのパラメーターとデータです。このページでは、現在のアクティブな予測のリストとそれらに関する基本情報が表示されます。ここでは、名前の変更、アーカイブ、新しい予測の作成ができます。アーカイブされた予測は非アクティブであり、ユーザーのスコアを更新しません。 
-
-新しい予測を作成するには、**予測を作成**を選択し、新しい**解約予測**を選択します。
-
-{% alert note %}
-同時にアクティブなチャーン予測はFIVEに制限されています。購入前に解約予測を行う場合、アクティブなプレビュー解約予測は1つまでです。プレビュー離脱予測は、スコアを定期的に更新したり、予測の出力に基づいてユーザーをターゲットにしたりすることはありません。詳細については、アカウントマネージャーにお問い合わせください。
-{% endalert %}
-
-「**基本**」ページで、新しい予測にユニークな名前を付けてください。また、この特定の予測に関するメモを取るためのオプションの説明を提供することもできます。
-
-**次へ**をクリックして次のステップに進みます。オプションとして、すべてのデフォルト設定を使用して作成の最後のステップにスキップするには、**ビルドナウ**をクリックすることができます。ビルドプロセスを開始する前に設定を確認する機会があります。進捗トラッカーの上部で選択することで、後で任意のステップに戻ることができます。
-
-## ステップ 2:解約を定義する
-
-「**解約の定義**」パネルで、提供されたフィルターを使用して、ビジネスにおけるユーザーの解約をどのように定義するかを指定します。言い換えれば、ユーザーが解約したと見なすためには、どの時間枠で何をする必要がありますか？
-
-覚えておいてください、解約に至る行動を説明する必要はありません—ユーザーが解約したユーザーになる理由だけを説明してください。これを、ユーザーが一度行うこと（`do`）または停止すること（`do not`）として考えてみてください。たとえば、7日間アプリを開いていないユーザーを離脱と見なすことができます。アンインストールやカスタムイベント（例：購読解除、アカウントの無効化など）を検討することで、ユーザーが離脱する原因となる可能性があります。 
-
-#### 解約ウィンドウ
-
-チャーンウィンドウは、ユーザーがチャーンを構成する行動を行う時間枠です。最大60日まで設定できます。このウィンドウは、予測のトレーニングのために履歴データを照会するために使用されます。さらに、予測が作成され、ユーザーがスコアを受け取った後、_Churn Risk Score_は、ユーザーがチャーンする可能性がチャーンウィンドウで指定された日数内でどれくらい高いかを示します。 
-
-これは、過去7日間のセッションの経過に基づく簡単な定義の例です。
-
-![解約の定義では、ユーザーが7日間セッションを開始しない場合、解約と見なされます][1]
-
-この場合、`do not`と`start a session`を選択します。他のフィルターを`AND`および`OR`と組み合わせて、必要な定義を作成することができます。考慮すべき潜在的な解約の定義に興味がありますか？次のセクションの[サンプルチャーン定義](#sample-definitions)にいくつかのインスピレーションを見つけることができます。
-
-{% alert note %}
-`do`については、アクティブユーザーが解約する前にこの行で指定されたアクションを実行しなかったと仮定します。アクションを行うと、彼らは解約される。<br><br>`do not`のために、アクティブユーザーとは、以前の日にそのアクションを行い、その後停止したユーザーと見なします。
-{% endalert %}
-
-定義の下には、利用可能なユーザー数（過去に解約したユーザーと解約しなかったユーザーの推定値）が表示されます。また、必要な最小値も表示されます。Brazeは、予測が学習するのに十分なデータを持つために、履歴データで利用可能なユーザーの最小数を持っている必要があります。
-
-## ステップ 3:フィルター 予測対象ユーザー
-
-予測対象ユーザーは、解約リスクを予測したいユーザーグループです。デフォルトでは、これは**すべてのユーザー**に設定されます。つまり、この予測はすべてのアクティブユーザーの解約リスクスコアを作成します。通常、モデルは、いくつかの基準で絞り込み、{filter}ユーザーグループを絞り込むと、解約を防ぐためにより良いパフォーマンスを発揮する可能性があります。あなたが保持したいと考える最も重要な特定のユーザーについて考え、ここで定義してください。たとえば、最初にアプリを使用したのが1か月以上前であるか、購入したことがあるユーザーを保持したい場合があります。
-
-{% alert note %}
-予測対象ユーザーは1億人を超えることはできません。
-{% endalert %}
-
-予測ウィンドウが14日以内の場合、「最後に使用したアプリ」や「最後に購入した」など「最後に...」で始まるフィルターの時間ウィンドウは、チャーン定義で指定されたチャーンウィンドウを**超えることはできません**。例えば、解約の定義に14日間のウィンドウがある場合、「最後の...」フィルターの時間ウィンドウは14日を超えることはできません。
-
-#### フルフィルターモード
-
-新しい予測をすぐに構築するために、Brazeのセグメンテーションフィルターのサブセットのみがサポートされています。フルフィルターモードを使用すると、すべてのBrazeフィルターを使用できますが、予測を構築するには1つのチャーンウィンドウが必要です。例えば、チャーンウィンドウが15日に設定されている場合、ユーザーデータを収集し、予測を構築するのに15日かかります。これは、フルフィルターモードでのみサポートされているフィルターを使用する場合です。 さらに、オーディエンスの規模に関するいくつかの推定値は、フルフィルターモードでは利用できません。
-
-予測対象ユーザー定義のサンプルリストについては、次の「[解約予測定義のサンプル](#sample-definitions)」セクションをご覧ください。
-
-![][3]
-
-前のページと同様に、下部パネルには、チャーン定義と予測対象ユーザー定義から得られる過去のユーザー数の推定値が表示されます。これらの見積もりは、予測を作成するために示された最小要件を満たす必要があります。
-
-## ステップ 4:解約予測の更新頻度を選択してください
-
-このページを完了すると作成される機械学習モデルは、ここで選択したスケジュールで使用され、新しいチャーンリスクスコアを生成します。更新の**最大頻度**を選択してください。例えば、ユーザーの離脱を防ぐために毎週のプロモーションを送信する場合、更新頻度を**毎週**に設定し、希望する日と時間に送信します。 
-
-![予測更新スケジュールは毎日午後5時に設定されています。][2]
-
-{% alert note %}
-プレビューとデモ予測は、ユーザーの解約リスクを更新することはありません。さらに、解約予測を使用した予測の毎日の更新には、毎週または毎月の更新に加えて追加の購入が必要です。この機能を購入するには、アカウントマネージャーに連絡してください。
-{% endalert %}
-
-## ステップ 5: ビルド予測
-
-詳細が正しいことを確認し、**予測を構築**を選択してください。変更を下書き形式で保存するには、**下書きとして保存**を選択してこのページに戻り、後でモデルを構築することができます。**予測の構築**をクリックすると、モデルを生成するプロセスが開始されます。これにはデータ量に応じて30分から数時間かかる可能性があります。この予測のために、モデル構築プロセスの期間中、トレーニングが進行中であることを説明するページが表示されます。
-
-完了すると、ページは自動的に分析ビューに切り替わり、予測と結果が準備完了したことを知らせるメールも届きます。エラーが発生した場合、ページは何が問題だったかの説明とともに編集モードに戻ります。
-
-予測は、最新のデータに基づいて更新を維持するために、**2週間ごとに自動的に**再構築（「再訓練」）されます。これは、ユーザーの_解約リスクスコア_（予測の出力）が生成されるプロセスとは別のプロセスであることに注意してください。後者は、ステップ4で選択した更新頻度によって決定されます。
-
-## サンプル離脱と予測対象ユーザーの定義 {#sample-definitions}
-
-**サンプルチャーン定義**<br>
-- 7日以内に、カスタムイベント「サブスクリプションのキャンセル」を実行してください。<br>
-- 30日以内に、カスタムイベント「Trial Expired」を実行してください<br>
-- 1日以内にアンインストールしてください。<br>
-- 14日以内に購入しないでください。<br>
-
-解約の定義について説明したように、対応する予測対象ユーザーの定義があるかもしれません。<br>
-- **サブスクリプションを2週間以上前に開始したか、2週間未満前に開始した**<br>この場合、2つの予測を作成し、新しい購読者には長期購読者とは異なるメッセージを送信することをお勧めします。「最初の購入が30日以上前に行われた」と定義することもできます。<br>
-- **アンインストーラー**<br>最近何かを購入したか、最近アプリを使用した顧客に焦点を当てるかもしれません。<br>
-- **購入しないリスクがある人々を解約の定義とする**<br>最近、アプリを閲覧したり検索したり、アプリを利用したりしている顧客に焦点を当てると良いでしょう。おそらく、適切な割引介入により、このより積極的なグループが離脱するのを防ぐことができるでしょう。
-
-## アーカイブされた予測
-
-アーカイブされた予測はユーザースコアの更新を停止します。アーカイブされた予測がアーカイブ解除されると、ユーザーのスコアは所定のスケジュールに従って更新され続けます。アーカイブされた予測は削除されることはなく、リストに残ります。
-
-[1]: {% image_buster /assets/img/churn/churn1.png %}
-[2]: {% image_buster /assets/img/churn/churn2.png %}
-[3]: {% image_buster /assets/img/churn/churn5.png %}
-
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/messaging_users.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/messaging_users.md
deleted file mode 100644
index 44ee66bb76d..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/messaging_users.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-nav_title: ユーザーへのメッセージング
-article_title: 解約予測のためにユーザーをターゲットにする
-description: "この参考記事では、フィルターの導入や戦略的考察など、解約予測を作成した後に考えられる次のステップについて取り上げている。"
-page_order: 3
-
----
-
-# メッセージング・ユーザー {#what-do-next}
-
-{% alert note %}
-プレビューおよびデモ予測では、ユーザーをメッセージングの対象にすることはできず、「**セグメントを作成**」、「**キャンペーンを作成」**ボタンは無効になる。この機能を購入するには、アカウント・マネージャーに連絡すること。
-{% endalert %}
-
-## フィルターを実装する {#filters}
-
-ターゲットとする_Churn Risk Score_またはカテゴリの範囲が決まったら、**Create Segment**または**Create Campaign**ボタンを使って、スライダーで選択した_Churn Risk Score_またはカテゴリを持つユーザーをフィルタリングする新しいセグメントまたはキャンペーンを作成することができる。
-
-![視聴者を定義する際に利用できる解約フィルターには、購入可能性カテゴリーと購入可能性スコアがある。][5]
-
-また、キャンペーンやセグメントでフィルターを使い、その閾値に従ってユーザーをターゲットにすることもできる。キャンペーン、キャンバス、セグメントでは、Brazeの他のフィルターと同じように、「解約スコア」や「解約カテゴリー」でユーザーをフィルターすることができる。
-
-## 戦略的考察
-
-さて、アクティブでエンゲージメントの高い状態を維持するために、何らかのインセンティブや新しいメッセージング・シリーズが必要だと思われる、解約リスクのあるユーザーグループを特定し、選択したところで、何をすればいいのだろうか？現在のパッシブ・ユーザー・シリーズに積極的に追加するだけなのか？それとも、キャンバスとキャンペーンの新しいシリーズを作り上げるのか？ 
-
-**ここでいくつかのアイデアを考えてみよう：**
-
-- 特別割引、無料商品（物理的ギフトまたはデジタルクレジット）、限定コンテンツ、または新しい体験（製品、アプリ機能、レベル）への早期アクセスで、中リスクから高リスクのユーザーを予測する。<br><br>
-- これらのユーザーを1週間毎日キャンバスに投下し、彼らが最も好むチャネルでメッセージを配信したり、3日間集中的にブラストを行い、Eメールからフェイスブックまであらゆるチャネルで顧客にアプローチしたり、実在の人物からメッセージを送り、ブランドのフィードバックやプロフェッショナルなヒントを求めたりする。<br><br>
-- もしかしたら、あなたのブランドの価値や、その顧客が以前あなたのブランドに価値を見出したあらゆる方法を、あらためて伝えるための、新しく楽しい方法が必要なのかもしれない。これは、ペルソナに特化した週刊ニュースレターのようなものかもしれないし、あなたのブランドに関する実際のユーザーからのリアルストーリーのシリーズかもしれないし、その他のコンテンツマーケティングの遊びかもしれない。
-
-リスクのあるユーザーのレベルに応じて、メッセージを変えることができることに留意してほしい！つまり、最もリスクの高い顧客は中程度の顧客よりも高い割引を受けられるが、最もリスクの低い顧客は新しい種類のメッセージやコンテンツを得られるだけで、それ以上のインセンティブは得られない。また、これらのセグメントに他のフィルターを重ねることで、誰がどのオファーやメッセージを受け取るかをさらに限定することもできる。
-
-[5]: {% image_buster /assets/img_archive/predictive_churn_filters.png %}
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/prediction_analytics.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/prediction_analytics.md
deleted file mode 100644
index 8a6c6142a3f..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/prediction_analytics.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-nav_title: 予測分析
-article_title: 予測分析
-description: "この参考記事では、解約予測分析ページに含まれるさまざまなコンポーネントと、洞察に満ちた主導的な意思決定を行うためにそれらをどのように使用できるかを取り上げている。"
-page_order: 2
-
----
-
-# 予測分析
-
-> 予測が構築され、トレーニングされると、**予測分析**ページにアクセスできるようになる。このページは、_Churn Risk Score（解約リスクスコア_）やカテゴリーに基づいて、どのユーザーをターゲットにすべきかを決めるのに役立つ。 
-
-予測がトレーニングされ、このページが入力されるとすぐに、セグメントやキャンペーンで[フィルターを]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/messaging_users/#filters)使うだけで、モデルの出力を使い始めることができる。しかし、誰をターゲットにするのか、なぜターゲットにするのかを決める手助けが欲しいのであれば、このページがモデルの歴史的正確さとあなた自身のビジネス目標に基づいて手助けしてくれるだろう。 
-
-**アナリティクス・コンポーネント**<br>
-[\- 解約スコアとカテゴリー](#churn_score)<br>
-[\- 予測の質](#prediction_quality)<br>
-[\- 推定結果](#estimated_results)<br>
-[\- 解約相関表](#correlation_table)
-
-## 概要
-
-予想者全体の得点分布は、ページ上部にチャートで表示され、カテゴリー別または得点別に見ることができる。さらに右側のビンにいるユーザーはスコアが高く、解約する可能性が高い。左側にあるビンのユーザーは、解約する可能性が低い。チャートの下にあるスライダーでユーザーの範囲を選択し、選択した_解約リスクスコア_またはカテゴリの範囲のユーザーをターゲットにした場合の結果を見積もることができる。
-
-![][4]{: style="max-width:90%"}
-
-スライダーを動かすと、下パネルの左半分にあるバーが、予測対象者全体のうち何人のユーザーをターゲットにするかを知らせてくれる。
-
-## 解約スコアとカテゴリー {#churn_score}
-
-予測対象のユーザーには、0から100の間で_解約リスク・スコアが_割り当てられる。スコアが高ければ高いほど、解約の可能性は高くなる。 
-- スコアが0から50のユーザーは、_「低リスク」_カテゴリーに分類される。 
-- スコアが50から75、75から100のユーザーは、それぞれ_「中リスク_」と「_高リスク」の_カテゴリーに分類される。 
-
-得点と対応するカテゴリーは、モデル作成ページで選択したスケジュールに従って更新される。20の等しい大きさのバケツにそれぞれ解約スコアを持つユーザー数が、ページ上部のグラフに表示されている。この予測によって、母集団全体の解約リスクがどのようになるかを判断することができる。
-
-## ユーザーをターゲットにして解約を減らす
-
-### 予測品質 {#prediction_quality}
-
-モデルの精度を測定するために、_Prediction Quality_指標は、過去のデータでテストしたときに、この特定の機械学習モデルがどの程度効果的であるかを示す。指標についての詳細は「[予測品質]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/)」を参照されたい。
-
-以下は、様々な_予測クオリティの_範囲に対して我々が推奨するものである：
-
-| 予測品質範囲(%) | 推薦 |
-| ---------------------- | -------------- |
-| 60 - 100 | 素晴らしい。トップクラスの精度だ。観客の定義を変えても、新たなメリットが得られるとは思えない。 |
-| 40 - 60 | 良いことだ。このモデルは正確な予測を行うが、観客の設定を変えてみると、さらに良い結果が得られるかもしれない。 |
-| 20 - 40| フェアだ。このモデルは、正確さと価値を提供することができるが、パフォーマンスが向上するかどうかを確認するために、異なる視聴者定義を試してみることを検討する。 |
-| 0 - 20 | 貧しい。視聴者定義を変更して、もう一度試してみることをお勧めする。 |
-{: .reset-td-br-1 .reset-td-br-2}
-
-予測は2週間ごとに再度トレーニングされ、予測品質指標とともに更新されるため、予測は最新のユーザー行動パターンに更新され続ける。この再トレーニングが最後に行われた時刻は、予測リストページと予測のアナリティクスページに表示される。
-
-## 推定結果 {#estimated_results}
-
-![][6]{: style="float:right;max-width:30%;margin-left:15px;"}
-
-グラフの下のパネルの右半分には、予測視聴者のこの範囲をターゲットにした場合の期待精度の推定値を示している。過去の予測オーディエンスのユーザーに関するデータと、その過去のデータに対する解約ユーザーと非解約ユーザーを識別するモデルの見かけの精度に基づき、これらのプログレスバーは、スライダーで強調表示されたオーディエンスを使用した将来の潜在的なメッセージの推定を行う：
-
-1. 実際の解約者のうち、どれだけが正しいターゲットになるかの見積もり <br><br> もちろん、私たちは未来を完璧に知っているわけではないので、予測視聴者のどのユーザーが将来解約するのか正確にはわからない。しかし、この予測は信頼できる推論である。過去の実績に基づいて、このプログレスバーは、予測オーディエンスで予想される（過去の解約率に基づく）「実際の」または「真の」解約者のうち、現在のターゲティング選択でターゲットにされる人の数を示している。余計なメッセージングや変わったメッセージングをしなければ、この数のユーザーは解約すると予想される。<br><br>
-
-2. 実際には解約していないはずのユーザーのうち、どれだけが誤ったターゲットになるかを推定する。<br><br>すべての機械学習モデルは誤りを犯す。選択したユーザーの中に、_解約リスク・スコアが_高くても解約に至らないユーザーがいるかもしれない。あなたが何もしなくても、彼らは解約しないだろう。いずれにせよ標的にされるのだから、これはエラー、あるいは "偽陽性 "である。この2番目のプログレスバーの全幅は、解約しないユーザーの予想数を表し、塗りつぶされた部分は、現在のスライダーの位置でターゲットとして間違っているユーザーである。
-
-この情報をもとに、どれだけの解約者を捕捉したいのか、また誤検知のコストはどれくらいなのかを決めることをお勧めする。価値のあるプロモを送るのであれば、ターゲットとする非回転者を最小限に抑える一方で、モデルが許す限り、期待される真の解約者を獲得したいと思うかもしれない。あるいは、誤検知にあまり敏感でなく、ユーザーが余分なメッセージを受け取る場合は、より多くのオーディエンスにメッセージを送り、より多くの解約予定者を捕捉し、エラーの可能性が高いものを無視することができる。
-
-## 解約相関表 {#correlation_table}
-
-この分析では、過去の予測対象においてユーザー離脱と相関のあるユーザー属性や行動が表示される。表はそれぞれ、解約の可能性が高い方を左、低い方を右に分けている。各行について、左の列の行動や属性を持つユーザーが解約する可能性が高いか低いかの比率が右の列に表示される。この数値は、この行動や属性を持つユーザーの解約可能性を、予測対象者全体の解約可能性で割った比率である。
-
-このテーブルは、予測が再トレーニングされるときにのみ更新され、ユーザーの_解約リスク・スコアが_更新されるときには更新されない。
-
-{% alert note %}
-プレビュー予測の相関データは部分的に隠される。この情報を公開するには購入が必要だ。詳細はアカウント・マネージャーに問い合わせること。
-{% endalert %}
-
-[6]: {% image_buster /assets/img/churn/churnEstimatedResults.png %}
-[4]: {% image_buster /assets/img/churn/churnTargeting.gif %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md
deleted file mode 100644
index 90962769078..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/prediction_analytics/prediction_quality.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-nav_title: 予測品質
-title: 予測品質
-description: "このリファレンス記事では、予測分析ページにある予測品質メトリックについて詳しく見ていきます。"
-page_order: 1
-Tool:
-  - Dashboard
----
-
-# 予測品質
-
-> モデルの精度を測定するために、_予測品質_メトリックは、この特定の機械学習モデルが過去のデータでテストされたときにどれほど効果的であるかを示します。Brazeは、モデル作成ページで指定したグループに従ってデータを取得します。モデルは1つのデータセット（「トレーニング」セット）でトレーニングされ、その後、新しい別のデータセット（「テスト」セット）でテストされます。 
-
-我々の_予測品質_の測定値は[リフト品質](https://dl.acm.org/doi/10.1145/380995.381018)です。おそらく「リフト」という言葉に馴染みがあるでしょう。これは、コンバージョンのような成功した結果の増加を比率やパーセンテージで測定することが多いです。この場合、成功した結果は、解約したであろうユーザーを正しく特定することです。リフト品質は、テストセットにメッセージングするためのすべての可能なオーディエンスサイズに対して予測が提供する平均リフトです。このアプローチは、モデルがランダムな推測よりもどれだけ優れているかを測定します。この指標では、0%はモデルが誰が解約するかをランダムに推測するのと同じくらいの精度であり、100%は誰が解約するかを完全に把握していることを示します。
-
-こちらがさまざまな範囲の_予測品質_に対して私たちが推奨するものです:
-
-| 予測品質範囲 (%) | 推薦 |
-| ---------------------- | -------------- |
-| 60 - 100 | 優れた。トップティアの精度。オーディエンス定義を変更しても追加の利益は得られない可能性があります。 |
-| 40 - 60 | 良い。このモデルは正確な予測を生成しますが、異なるオーディエンス設定を試すことでさらに良い結果が得られるかもしれません。 |
-| 20 - 40| 公正。このモデルは精度と価値を提供できますが、パフォーマンスを向上させるために異なるオーディエンスの定義を試してみることを検討してください。 |
-| 0 - 20 | 貧しい。オーディエンス定義を変更して、再試行することをお勧めします。 |
-{: .reset-td-br-1 .reset-td-br-2}
-
-予測は2週間ごとに再トレーニングされ、_予測品質_メトリックとともに更新され、最新のユーザー行動パターンに基づいて予測が更新されます。さらに、これが発生するたびに、過去2週間の予測が実際のユーザーの結果と照らし合わせてテストされます。その_予測の質_は、これらの実際の結果（推定ではなく）に基づいて計算されます。これは自動バックテストです（つまり、予測モデルを過去のデータでテストすること）で、予測が実際のシナリオで正確であることを確認します。この再トレーニングとバックテストが最後に行われた時刻は、**予測**ページおよび個々の予測の分析ページに表示されます。プレビュー予測であっても、作成後にこのバックテストを一度実行します。この方法を使用すると、機能の無料バージョンでもカスタマイズされた予測の精度を確信できます。
-
-{% details 予測 Quality details %}
-
-例えば、ユーザーの20％が通常平均して離脱する場合、ユーザーの20％のランダムなサブセットを選び、彼らをランダムに離脱したとラベル付けすると（実際にそうであるかどうかに関わらず）、実際の離脱者のうち20％しか正しく識別できないと予想されます。それはランダムな推測です。モデルがそれだけうまくいけば、この場合のリフトは1になります。
-
-一方で、モデルがユーザーの20％にメッセージを送信することを許可し、その結果、すべての「真の」解約者を捕捉し、他の誰も捕捉しなかった場合、リフトは100％ / 20％ = 5になります。最も解約する可能性が高い顧客の割合ごとにこの比率をグラフ化すると、[リフトカーブ](https://towardsdatascience.com/the-lift-curve-unveiled-998851147871)が得られます。 
-
-リフト品質（および_予測品質_）を考えるもう1つの方法は、ランダムな推測（0％）と完璧（100％）の間で、テストセットでチャーナーを識別する際の予測のリフト曲線がどれだけ進んでいるかです。リフト品質に関する元の論文については、[データベースマーケティングにおけるリフト品質の測定](https://dl.acm.org/doi/10.1145/380995.381018)を参照してください。
-
-{% enddetails %}
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/prediction_faq.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/prediction_faq.md
deleted file mode 100644
index d6d0a50fecd..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_churn/prediction_faq.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-nav_title: トラブルシューティング
-article_title: 解約予測トラブルシューティング
-description: "この記事では、解約予測を使用する際のトラブルシューティング手順と考慮事項について説明します。"
-page_order: 3
-
----
-
-# トラブルシューティング
-
-> 解約予測（および任意の機械学習モデル）は、モデルに利用可能なデータと同じくらい優れています。また、作業するための特定のデータ量に大きく依存します。 
-
-## 潜在的なエラー
-
-### トレーニングするデータが不十分です 
-
-このエラーメッセージは、チャーンの定義が厳しすぎて、チャーンしたユーザーが少なすぎる場合に表示されます。 
-
-これを修正するには、チャーンを定義する日数および/またはアクションの数を変更して、より多くのユーザーをキャプチャする必要があります。フィルター`AND/OR`を正しく使用して、過度に制限的な定義を作成しないようにしてください。 
-
-{% alert important %}
-Predictive Churn が会社レベルでオンになっている間、一部のワークスペースには予測を構築するのに十分なユーザーがいない場合があります。通常、単一のワークスペースで300,000人の月間アクティブユーザーが必要です。
-{% endalert %}
-
-### 予測対象ユーザー数の問題
-
-![][3]{: style="float:right;max-width:60%;margin-left:15px;margin-bottom:15px;margin-top:15px;"}
-
-予測対象ユーザーを構築して、モデルをトレーニングする対象を微調整する際に、予測対象ユーザーのユーザー数が少なすぎることを通知するメッセージが表示されることがあります。 
-
-過去7日間に選択された予測対象ユーザーから利用可能な過去の解約者が十分でないため、予測を確実に構築することができません。
-
-予測対象ユーザーの定義が厳しすぎると、過去および現在のユーザーのプールが十分に大きくない可能性があります。これを修正するには、定義で使用される日数と属性の種類を変更するか、解約を定義するアクションを切り替えるか、またはその両方を行う必要があります。 
-
-予測対象ユーザーが定義を変更しても問題であり続ける場合、このオプション機能をサポートするユーザーが少なすぎる可能性があります。追加のレイヤーやフィルターなしで予測を構築してみることをお勧めします。 
-
-### 予測対象ユーザーサイズが大きすぎます
-
-予測対象ユーザー定義は1億ユーザーを超えることはできません。オーディエンスが大きすぎるというメッセージが表示された場合は、オーディエンスにレイヤーを追加するか、それが基づいている時間枠を変更することをお勧めします。
-
-### 予測は質が悪い
-
-![][1]{: style="float:right;max-width:40%;margin-left:15px;"}
-あなたのモデルの[予測品質]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/)が40％以上であれば、素晴らしい状態にあります！ただし、予測の質が39％以下に低下した場合は、解約および予測対象ユーザーの定義をより具体的にするか、異なる時間枠を設定する必要があるかもしれません。 
-
-予測定義を構築する際にオーディエンスサイズの要件を満たし、予測精度が40％を超えることができない場合、Brazeに送信されたデータがこのユースケースに適していないか、モデルを構築するためのユーザーが十分でないか、製品ライフサイクルが現在の60日間の振り返りウィンドウをサポートするよりも長いことを意味します。 
-
-## データの考慮事項
-
-次の質問は、解約予測を設定する際に自問するべき質問です。機械学習モデルは、それらを訓練するデータと同じくらい優れているだけなので、良いデータ衛生習慣を持ち、モデルに何が入るかを理解することが大きな違いを生むでしょう。
-
-- 高価値アクションはリテンションとロイヤルティにつながりますか？
-- これらの特定のアクションにマップされるカスタムイベントを設定しましたか？解約予測はカスタム属性ではなくカスタムイベントで動作します。
-- 時間枠の中で解約を定義することを考えていますか？チャーンは最大60日以内に発生するものとして定義できます。
-- 年中行事など、通常とは異なるユーザー行動を引き起こす時期を考慮したことがありますか？消費者行動の急速な変化は、あなたの予測に影響を与えるでしょう。 
-
-[1]: {% image_buster /assets/img/churn/churn3.png %}
-[3]: {% image_buster /assets/img/churn/audience_size_error.png %}
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events.md
deleted file mode 100644
index 2d6b51df654..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-nav_title: イベント予測
-article_title: イベント予測
-page_order: 6.4
-layout: featured
-alias: /predictive_purchases/
-search_rank: 1
-guide_top_header: "イベント予測"
-guide_top_text: "どのユーザーが購入のような特定のイベントを行う可能性が高いかを知ることは、成長企業にとって極めて重要な洞察である。それがなければ、どのキャンペーンを作るかどうやって決めるのか？誰が割引やプロモーションを受けるべきか？限られた予算をどこに使うか？Brazeは、マーケティングチームが将来の行動を理解し、エンゲージメントと収益を最大化するキャンペーンにリソースを集中させることを容易にする機械学習モデルであるPredictive Events（旧Predictive Purchases）で、こうした疑問への回答を支援する。"
-description: "この記事では、マーケターがイベントを実行する可能性に基づいてユーザーを特定し、メッセージを送る機能を提供するツール、プレディクティブ・イベント（以前はプレディクティブ・パーチェス）を取り上げる。"
-
-guide_featured_title: "トピック"
-guide_featured_list:
-- name: 予測を立てる
-  link: /docs/user_guide/sage_ai/predictive_suite/predictive_events/creating_an_event_prediction/
-  image: /assets/img/braze_icons/settings-01.svg
-- name: 予測分析
-  link: /docs/user_guide/sage_ai/predictive_suite/predictive_events/prediction_analytics/
-  image: /assets/img/braze_icons/bar-chart-01.svg
-- name: ユーザーへのメッセージング
-  link: /docs/user_guide/sage_ai/predictive_suite/predictive_events/messaging_users/
-  image: /assets/img/braze_icons/arrow-narrow-right.svg
-
----
-
-## 概要
-
-![予測イベントの仕組み」と題されたグラフィック。左側は、機械学習モデルに取り込まれるユーザーデータを示している。ラベルには、"過去のデータを使って訓練し、ある期間にイベントを実行したユーザーと実行しなかったユーザーの行動を比較する "と書かれている。右側は機械学習の結果で、ユーザーがそのイベントを実行する可能性が最も低いものから最も高いものへとランク付けされている。ラベルには "将来の出来事の可能性を予測し、正確で便利なターゲティングのためにユーザーに可能性スコアを割り当てる "と書かれている。][1]
-
-> Predictive Eventsは、マーケティング担当者がイベントを実行する可能性に基づいてユーザーを特定し、メッセージを送るための強力なツールを提供する。イベント予測を作成すると、Brazeは[勾配ブースティング決定木を](https://en.wikipedia.org/wiki/Gradient_boosting)使用して機械学習モデルを訓練し、過去の活動から学習して将来の活動を予測する。
-
-予測が構築されると、ユーザーは0から100の間で、選択したイベントを実行する可能性を示す[可能性スコアを]({{site.baseurl}}/user_guide/predictive_suite/predictive_purchases/prediction_analytics/#purchase_score)割り当てられる。スコアが高いほど、ユーザーがそのイベントを実行する可能性が高い。ユーザーはまた、可能性が低い、中程度、高いのカテゴリー別に分類される。
-
-プレディクティブ・イベントの本当の価値は、予測結果を使ってセグメントやキャンペーンを作成することにある。マーケティング担当者は、**予測**ページで直接ターゲットを絞ったキャンペーンを構築し、即座に収益を上げることも、将来のキャンペーンやキャンバスのためにセグメントを保存することもできる。誰を最初にターゲットにするか迷っている？可能性スコアに基づくメッセージング・ユーザーの[戦略的考察を]({{site.baseurl}}/user_guide/predictive_suite/predictive_purchases/messaging_users/#strategy)読む。
-
-## 予測イベントにアクセスする
-
-**予測」**ページは**「アナリティクス」**セクションにある。完全なアクセスについては、アカウント・マネージャーに連絡すること。
-
-{% alert note %}
-[古いナビゲーションを]({{site.baseurl}}/navigation)使用している場合は、**「** **エンゲージメント**」の下に**「予測」が**ある。
-{% endalert %}
-
-この機能を購入する前に、プレビュー・モードで利用できる。これにより、合成データを使ったデモ予測を見ることができるほか、プレビュー予測モデルを一度に1つ作成することもできる。この予測は、実際のユーザーデータに基づいて作成されるが、ユーザーの可能性スコアに従ってメッセージングのターゲットを絞ることはできない。また、作成後に定期的に更新されることもない。
-
-プレビューを使えば、この1つの[予測を]({{site.baseurl}}/user_guide/predictive_suite/predictive_purchases/prediction_analytics/#prediction_quality)編集して再構築したり、アーカイブして他の予測を作成したりすることもできる[。]({{site.baseurl}}/user_guide/predictive_suite/predictive_purchases/creating_a_purchase_prediction/#audience)
-
-<br><br>
-
-[1]: {% image_buster /assets/img/how_predictive_events_works.png %}
-
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events/creating_an_event_prediction.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events/creating_an_event_prediction.md
deleted file mode 100644
index c797cf9c8a9..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events/creating_an_event_prediction.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-nav_title: イベント予測の作成
-article_title: イベント予測の作成
-page_order: 1
-description: "この記事では、Brazeダッシュボード内でイベント予測を作成する方法について説明します。"
-
----
-
-# イベント予測の作成
-
-> 予測は、訓練された機械学習モデルの1つのインスタンスと、それが使用するすべてのパラメーターおよびデータです。予測イベントの詳細については、[予測イベントの概要]({{site.baseurl}}/user_guide/sage_ai/predictive_suite/predictive_events)を参照してください。
-
-Brazeで、**分析** > **予測イベント**に移動します。
-
-{% alert note %}
-[古いナビゲーション]({{site.baseurl}}/navigation)を使用している場合、**予測**は**エンゲージメント**の下にあります。
-{% endalert %}
-
-このページでは、現在のアクティブなイベント予測のリストとそれらに関する基本情報が表示されます。ここでは、名前の変更、アーカイブ、新しい予測の作成ができます。アーカイブされた予測は非アクティブであり、ユーザーのスコアを更新しません。
-
-## ステップ 1:新しい予測を作成する
-
-1. **予測の作成**を選択し、新しい**イベント予測**を選択します。
-
-{% alert note %}
-同時にアクティブな予測はFIVE個までです。購入前に予測イベントを購入する場合、アクティブなプレビュー予測は1つまでです。プレビュー予測は、予測の出力に基づいてスコアやターゲットユーザーを定期的に更新しません。詳細については、アカウントマネージャーにお問い合わせください。
-{% endalert %}
-
-{: start="2"}
-2\.予測にユニークな名前を付けてください。説明を提供して、関連するメモを保存することもできます。
-
-![][1]
-
-{: start="3"}
-3\.**次へ**をクリックして次のステップに進みます。<br><br>オプションとして、**Build Now**をクリックして、すべてのデフォルト設定を使用し、作成の最後のステップにスキップすることができます。ビルドプロセスを開始する前に設定を確認する機会があります。また、上部バーの任意のステップをクリックすることで、後で任意のステップに戻ることができます。
-
-## ステップ 2:イベントトラッキング{#event-tracking}を指定する
-
-Braze にユーザーのイベントが [購入イベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/) または [カスタムイベント]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/) として保存されているかどうかを指定します。
-
-ここでは、選択した方法がBrazeに機械学習モデルを作成するのに十分なデータを提供するかどうかを確認します。要件が満たされない場合、アプリケーションで使用されている他のログ記録方法を選択してみてください。残念ながら、そうでない場合、Brazeは利用可能なデータ量で予測を作成することができません。このエラーが誤って表示されていると思われる場合は、顧客成功マネージャーに連絡してください。
-
-#### イベントウィンドウ
-
-イベントウィンドウは、ユーザーがイベントを実行するかどうかを予測したい時間枠です。60日まで設定できます。このウィンドウは、予測のトレーニングのために履歴データを照会するために使用されます。さらに、予測が作成され、ユーザーがスコアを受け取ると、確率スコアは、イベントウィンドウで指定された日数内にユーザーがイベントを実行する可能性を示します。
-
-### ステップ 3:フィルター予測対象ユーザー（オプション）{#audience}
-
-予測対象ユーザーは、予測したい可能性スコアを持つユーザーのグループです。必要に応じて、ユーザー全体に対して予測を実行できます。これを行うには、デフォルトのオプション**すべてのユーザー**を選択したままにします。
-
-モデルは通常、いくつかの基準で評価したいユーザーをフィルターすると、より良いパフォーマンスを発揮します。そのためには、**独自の予測対象ユーザーを定義する**を選択し、オーディエンスフィルターを選択します。例えば、「最初に使用したアプリ」フィルターを30日に設定することで、少なくとも30日間アプリを使用しているユーザーに焦点を当てることができます。
-
-予測対象ユーザー定義は、機械学習モデルが過去から学習できるように、履歴データをクエリするためにも使用されます。前のページと同様に、これらのフィルターによって提供されるデータの量が要件とともに表示されます。希望するオーディエンスを指定し、最小限に達しない場合は、より広いフィルターを指定するか、**すべてのユーザー**オプションを使用してください。
-
-{% alert note %}
-予測対象ユーザーは1億人を超えることはできません。
-{% endalert %}
-
-イベントウィンドウが14日以内の場合、「最後に使用したアプリ」や「最後に購入した」など「最後に...」で始まるフィルターの時間ウィンドウは、**指定されたイベントウィンドウを超えることはできません[イベントトラッキング](#event-tracking)**。例えば、イベントウィンドウが14日に設定されている場合、「最後の...」フィルターの時間ウィンドウは14日を超えることはできません。
-
-#### フルフィルターモード
-
-新しい予測をすぐに構築するために、Brazeのセグメンテーションフィルターのサブセットのみがサポートされています。フルフィルターモードを使用すると、すべてのBrazeフィルターを使用できますが、予測を構築するには1つのイベントウィンドウが必要です。 
-
-例えば、イベントウィンドウが14日に設定されている場合、ユーザーデータを収集し、フルフィルターモードでのみサポートされているフィルターを使用して予測を構築するのに14日かかります。 さらに、オーディエンスの規模に関するいくつかの推定値は、フルフィルターモードでは利用できません。
-
-### ステップ 4:更新スケジュールを選択
-
-このページを完了すると作成される機械学習モデルは、ここで選択したスケジュールで使用され、ユーザーがイベントを実行する確率（可能性スコア）の新しいスコアを生成します。更新の**最大頻度**を選択してください。例えば、購入を予測していて毎週のプロモーションを送る予定がある場合、更新頻度を**毎週**に設定し、希望する日と時間に設定してください。
-
-{% alert note %}
-プレビューとデモ予測はユーザーの可能性スコアを更新することはありません。
-{% endalert %}
-
-### ステップ 5: ビルド予測
-
-詳細が正しいことを確認し、**予測の構築**を選択してください。変更を下書き形式で保存するには、**下書きとして保存**を選択してこのページに戻り、後でモデルを構築することができます。 
-
-**予測の構築**をクリックすると、モデルを生成するプロセスが開始されます。これにはデータ量に応じて30分から数時間かかる可能性があります。この予測のために、モデル構築プロセスの期間中、トレーニングが進行中であることを説明するページが表示されます。
-
-完了すると、ページは自動的に分析ビューに切り替わり、予測と結果が準備できたことを知らせるメールが届きます。エラーが発生した場合、何が問題だったのかの説明とともにページは編集モードに戻ります。
-
-予測は、利用可能な最新のデータに基づいて更新を維持するために、**2週間ごと**に自動的に再構築（「再訓練」）されます。ユーザーの可能性スコア、予測の出力が生成されるときとは別のプロセスであることに注意してください。後者は、ステップ4で選択した更新頻度によって決定されます。
-
-## アーカイブされた予測
-
-アーカイブされた予測はユーザーのスコアの更新を停止します。アーカイブされた予測がアーカイブ解除されると、ユーザーのスコアは所定のスケジュールに従って更新され続けます。アーカイブされた予測は削除されることはなく、リストに残ります。
-
-[1]: {% image_buster /assets/img/purchasePrediction/purchases_step1.png %}
-
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events/messaging_users.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events/messaging_users.md
deleted file mode 100644
index d932fa10d4d..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events/messaging_users.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-nav_title: ユーザーへのメッセージング
-article_title: 予測イベントのターゲットユーザー
-description: "このリファレンス記事では、フィルターインプリメンテーションや戦略的な考慮事項など、行動予測を作成した後に発生する可能性のある次回のステップについて説明します。"
-page_order: 3
-
----
-
-# メッセージユーザー {#what-do-next}
-
-> イベント予測を作成した後で、予測イベントのユーザーを対象にする方法について説明します。
-
-{% alert note %}
-プレビューおよびデモ予測s では、ユーザーs をメッセージング対象とすることはできません。**セグメント** を作成、**キャンペーン** ボタンは無効になります。この機能をお買い求めの場合は、アカウントマネージャーにお問い合わせください。
-{% endalert %}
-
-## フィルターの実装 {#filters}
-
-個々の**Predictions**ページから、目標とする可能性スコアまたはカテゴリの範囲を決定した後、**Segmentを作成**または**キャンペーンを作成**ボタンを使用して新しいSegmentまたはキャンペーンを作成できます。このSegmentまたはキャンペーンは、スライダで選択した尤度スコアまたはカテゴリでユーザーs をフィルターします。
-
-![オーディエンスを定義するときに使用できるフィルタには、尤度カテゴリおよび尤度スコアが含まれます。][5]
-
-フィルター s をキャンペーン s、キャンバス、またはSegment s で使用して、他のフィルターをBrazeで使用する場合と同様に、尤度スコアまたはカテゴリに基づいてユーザーを対象にすることもできます。
-
-## 戦略的検討事項 {#strategy}
-
-今後、誰がイベントを実行するか、または実行しないかがわかったので、顧客にどのようにマーケティングを割り当てるかについて考え始めましょう。
-
-可能性スコアやカテゴリに基づいたメッセージユーザーは、お金を稼ぐのに役立つだけではなく、お金を節約するのにも役立ちます。スライドスケールでプロモーションを行う。つまり、ユーザーが購買を行う可能性が高ければ高いほど、必要な割引は少なくなる。この残高を見つけることで、顧客ごとに適切な金額を提供し、取得することができます。また、他のフィルターをこれらのSegments にレイヤー化して、誰がどのメッセージを取得するかをさらに限定することもできます。
-
-ユーザーの尤度スコアに基づいて予測イベント戦略を始めるためのいくつかのアイデアを次に示します。
-
-### 高尤度ユーザー
-
-買い物を完了するなど、イベントを実行する可能性が最も高いメッセージング ユーザーs によって、迅速に勝利を得ます。カートで待機しているアイテム、"buy now!&quot....
-
-### 中尤度ユーザーs
-
-追加の微調整が必要な中期ユーザーのプロモーションを保存します。特別割引、Fac eBook とGoogle で関連する内容のリターゲティングする、または新しいエクスペリエンス(商品、機能、またはレベル) への早期独占的なアクセス権を共有する
-
-### 低尤度ユーザーs
-
-低尤度ユーザーs をテストすることができるパスは2 つあります。購入するように彼らを説得できると思いますか?より高い割引を出すか、3日間集中的なクロスチャネルの吹きをする。購買過程をできるだけ簡単かつ容易にするためのパーソナライズされた提言や実践的な支援を提供する。
-
-これらのユーザーsを、あなたのブランドの心のトップを保つためのリソースライトな方法として、よりパッシブなキャンペーンまたはキャンバスに落としましょう。これは、ペルソナ特有の週刊ニュースレター、関連する一連の顧客ケーススタディ、または新しいヒントやコツの月例ラウンドアップである可能性がある。
-
-[5]: {% image_buster /assets/img_archive/predictive_event_filters.png %}
diff --git a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events/prediction_analytics.md b/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events/prediction_analytics.md
deleted file mode 100644
index 463921c3912..00000000000
--- a/_lang/ja/_user_guide/sage_ai/predictive_suite/predictive_events/prediction_analytics.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-nav_title: 予測 分析
-article_title: 予測 分析
-description: "このリファレンス記事では、予測イベント分析ページに含まれるさまざまなコンポーネントと、それらを使用して洞察に基づいた意思決定を行う方法について説明します。"
-page_order: 2
-
----
-
-# 予測分析
-
-> 予測が構築され、トレーニングされた後、**予測分析**ページにアクセスできます。このページは、ユーザーの可能性スコアやカテゴリに基づいてターゲットにすべきユーザーを決定するのに役立ちます。
-
-予測のトレーニングが完了し、このページが入力されるとすぐに、セグメントやキャンペーンで[フィルター]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/messaging_users/#filters)を使用してモデルの出力を使用し始めることができます。このページは、モデルの歴史的な精度とあなた自身のビジネス目標に基づいて、誰をターゲットにするか、なぜターゲットにするかを決定するのに役立ちます。
-
-## 分析 components
-
-- [可能性スコア](#purchase_score)
-- [ユーザーへのターゲット設定](#target_users)
-- [予測品質](#prediction_quality)
-- [推定結果](#estimated_results)
-- [イベント相関表](#correlation_table)
-
-## 可能性スコア {#purchase_score}
-
-予測対象ユーザーのユーザーには、0から100の間の確率スコアが割り当てられます。スコアが高いほど、イベントを実行する可能性が高くなります。 
-
-次のように、ユーザーはその可能性スコアに応じて分類されます:
-
-- **低:** 0から50の間
-- **中:** 50 と 75 の間
-- **高い:** 75 と 100 の間
-
-スコアと対応するカテゴリは、**予測作成**ページで選択したスケジュールに従って更新されます。ページの上部にあるチャートには、20の同じサイズのバケットまたは各可能性カテゴリのそれぞれにおけるユーザー数が表示されています。
-
-## オーディエンスビルダーでユーザーをターゲティングする {#target_users}
-
-ページの上部に、全予測対象ユーザーの確率スコアの分布が表示されます。右側のバケットにいるユーザーはスコアが高く、イベントを実行する可能性が高くなります。左側のバケットにいるユーザーは、そのイベントを実行する可能性が低くなります。グラフの下のスライダーを使用すると、ユーザーのセクションを選択し、それらのユーザーをターゲットにした場合の結果を推定できます。
-
-![][4]{: style="max-width:90%"} 
-
-スライダーハンドルをさまざまな位置に移動すると、パネルの左半分のバーが、選択した人口の一部を使用して、全予測対象ユーザーのうち何人がターゲットになるかを知らせます。
-
-### 推定結果 {#estimated_results}
-
-チャートの下のパネルの右半分には、選択した予測対象ユーザーの一部をターゲットにした場合の予想精度の推定値を2つの方法で表示します。選択したユーザーのうち、イベントを実行することが予想されるユーザーの数と、実行しないことが予想されるユーザーの数です。
-
-![][6]
-
-
-#### イベントを実行する予定の選択されたユーザーは何人ですか
-
-予測は完全に正確ではなく、どの予測もそうであるため、Brazeはすべての将来のユーザーを特定してイベントを実行することはできません。可能性スコアは、情報に基づいた信頼できる予測のセットのようなものです。進捗バーは、予測対象ユーザーの「真陽性」のうち、選択されたオーディエンスでターゲットされる数を示します。メッセージを送信しなくても、この数のユーザーがイベントを実行することを期待しています。
-
-#### 選択されたユーザーのうち、どれくらいの人数がそのイベントを実行しないと予想されますか
-
-すべての機械学習モデルはエラーを犯します。選択したユーザーの中には、高い可能性スコアを持っているが実際にはイベントを実行しないユーザーがいるかもしれません。アクションを起こさなければ、彼らはイベントを実行しません。彼らはとにかく標的にされるので、これはエラーまたは「偽陽性」です。この2番目の進捗バーの全幅は、イベントを実行しないと予想されるユーザーの数を表しており、塗りつぶされた部分は現在のスライダー位置を使用して誤ってターゲットにされるユーザーを示しています。
-
-この情報を使用して、どれだけの真陽性を捕捉したいか、どれだけの偽陽性を許容できるか、そしてエラーのコストがビジネスにとってどれほどのものかを決定することをお勧めします。貴重なプロモーションを送信する場合、チャートの左側を優先することで、非購入者（偽陽性）のみをターゲットにすることを検討するかもしれません。あるいは、チャートの右側を好むユーザーのセクションを選択することで、頻繁に購入する（真のポジティブ）購入者に再度購入を促すことができます。
-
-### 予測品質 {#prediction_quality}
-
-モデルの精度を測定するために、_予測品質_メトリックは、この特定の機械学習モデルがどれほど効果的であるかを示します。それは、この予測がイベントの実行者と非実行者を区別する能力の良さを測る尺度です。100の_予測品質_は、エラーなしで誰がイベントを実行するかしないかを完全に知っていることを意味します（これは決して起こりません！）、0はランダムに推測していることを意味します。メトリックの詳細については、[予測品質]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/prediction_analytics/prediction_quality/)を参照してください。
-
-こちらがさまざまな範囲の_予測品質_に対して私たちが推奨するものです:
-
-| 予測品質範囲 (%) | 推薦 |
-| ---------------------- | -------------- |
-| 60 - 100 | 優れた。トップティアの精度。オーディエンス定義を変更しても追加の利益は得られない可能性があります。 |
-| 40 - 60 | 良い。このモデルは正確な予測を生成しますが、異なるオーディエンス設定を試すことでさらに良い結果が得られるかもしれません。 |
-| 20 - 40| 公正。このモデルは精度と価値を提供できますが、パフォーマンスが向上するかどうかを確認するために、さまざまなオーディエンスの定義を試してみてください。 |
-| 0 - 20 | 貧しい。オーディエンス定義を変更して、再試行することをお勧めします。 |
-{: .reset-td-br-1 .reset-td-br-2}
-
-予測は2週間ごとに再トレーニングされ、予測品質メトリックと共に更新されて、最新のユーザー行動パターンに基づいて予測が更新されます。再トレーニングが最後に行われた時刻は、予測リストページおよび予測の分析ページに表示されます。 
-
-予測が最初に作成されると、予測の品質は**予測の構築**をクリックしたときにクエリされる履歴データに基づきます。その後、2週間ごとに、予測の質は予測スコアを実際の結果と比較することによって導き出されます。
-
-## イベント相関テーブル {#correlation_table}
-
-この分析は、予測対象ユーザーのイベントと相関するユーザーの属性や行動を表示します。評価される属性は年齢、国、性別、言語です。分析される行動には、セッション、購入、総支出額、カスタムイベント、キャンペーン、および過去30日間に受信したキャンバスステップが含まれます。
-
-テーブルは、イベントを実行する可能性が高いものと低いものに分かれています。各行について、左列にある行動や属性を持つユーザーがイベントを実行する可能性が高いか低いかの比率が右列に表示されます。この数値は、この行動または属性を持つユーザーの可能性スコアを、全予測対象ユーザーがイベントを実行する可能性で割った比率です。
-
-このテーブルは予測が再トレーニングされるときにのみ更新され、ユーザーの可能性スコアが更新されるときには更新されません。
-
-{% alert note %}
-プレビュー予測の相関データは一部非表示になります。この情報を表示するには購入が必要です。詳細については、アカウントマネージャーにお問い合わせください。
-{% endalert %}
-
-[6]: {% image_buster /assets/img/purchasePrediction/purchaseEstimatedResults.png %}
-[4]: {% image_buster /assets/img/purchasePrediction/purchaseTargeting.png %}
\ No newline at end of file
diff --git a/_lang/ja/_user_guide/sage_ai/recommendations.md b/_lang/ja/_user_guide/sage_ai/recommendations.md
deleted file mode 100644
index 3b616d7c21c..00000000000
--- a/_lang/ja/_user_guide/sage_ai/recommendations.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-nav_title: おすすめ
-article_title: おすすめ
-page_order: 15
-layout: dev_guide
-search_rank: 1
-guide_top_header: "おすすめ"
-guide_top_text: "Brazeで推薦のステップアップを図ろう。ここでは、レコメンデーション・エンジンの設定について知っておくべきことを集め、ユーザーが実際に欲しいアイテムやコンテンツを提案できるようにする。AIを使った体験のカスタマイズから、リキッドやコネクテッド・コンテンツを使った独自のエンジンの構築まで、あらゆるレコメンデーションに必要なすべてが見つかる。"
-description: "このランディングページには、Brazeでのレコメンデーションエンジンの構築と使用に関する記事が掲載されている。"
-
-guide_featured_title: "記事"
-guide_featured_list:
-- name: 推薦について
-  link: /docs/user_guide/sage_ai/recommendations/about_item_recommendations/
-  image: /assets/img/braze_icons/book-closed.svg
-- name: AIアイテムの推奨
-  link: /docs/user_guide/sage_ai/recommendations/ai_item_recommendations/
-  image: /assets/img/braze_icons/user-check-01.svg
-- name: ルールに基づく推薦
-  link: /docs/user_guide/sage_ai/recommendations/rules_based_recommendations/
-  image: /assets/img/braze_icons/list.svg
----
-
-<br><br>
diff --git a/_lang/ja/_user_guide/sage_ai/recommendations/about_item_recommendations.md b/_lang/ja/_user_guide/sage_ai/recommendations/about_item_recommendations.md
deleted file mode 100644
index ecae54b7c23..00000000000
--- a/_lang/ja/_user_guide/sage_ai/recommendations/about_item_recommendations.md
+++ /dev/null
@@ -1,335 +0,0 @@
----
-nav_title: 推奨アイテムについて
-article_title: 推奨アイテムについて
-description: "この参考記事では、Brazeを使用して顧客に商品を推薦するさまざまな使用例について説明する。"
-page_order: 1
----
-
-# 推奨アイテムについて
-
-この記事では、顧客が実際に興味を持っているアイテムを提案するさまざまな方法について学び、Brazeを使ってレコメンデーション・エンジンを作成する一般的なユースケースのヒントを得る。
-
-## 前提条件
-
-すべてのレコメンデーションタイプは、少なくとも1つの[カタログを]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/)設定する必要がある。
-
-## 推薦の種類
-
-顧客に商品を薦める場合、いくつかのアプローチがある：
-
-- [AIパーソナライズド](#ai)
-- [最も人気がある](#most-popular)
-- [直近のもの](#most-recent)
-- [セレクション・ベース](#selections-based)
-- [ルール・ベース](#rules-based)
-
-### AI パーソナライズされたレコメンデーション {#ai}
-
-[AIアイテム・レコメンデーション][1]機能の一部であるAIパーソナライズド・レコメンデーションは、ディープラーニングを活用し、ユーザーが過去に興味を示したものに基づいて、次に興味を持ちそうなものを予測する。この方法は、ユーザーの行動に適応する、ダイナミックでカスタマイズされた推薦システムを提供する。
-
-AIパーソナライズド・レコメンデーションは、レコメンデーションモデルを構築するために、購入やカスタムイベントなど、過去6ヶ月間のアイテムとのインタラクションデータを使用する。パーソナライズされたリストを作成するのに十分なデータがないユーザーには、最も人気のあるアイテムが予備として機能するため、ユーザーは引き続き関連性の高い提案を得ることができる。
-
-AIアイテム・レコメンデーションを使えば、さらに以下の方法でアイテムを絞り込むこともできる。
-[選択項目]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)。ただし、リキッド入りのセレクションはAIのレコメンデーションには使えないので、カタログのセレクションを作る際にはその点に留意してほしい。
-
-例については、この記事の[使用例の](#use-cases)セクションを参照のこと。
-
-{% alert tip %}
-AI パーソナライズされたレコメンデーションは、数百から数千のアイテムがあり、通常、少なくとも3万人のユーザーが購入またはインタラクションデータを持っている場合に最も効果的である。これはあくまでも目安であり、変動する可能性がある。他の推薦タイプは、より少ないデータで機能する。
-{% endalert %}
-
-### 最も人気のあるおすすめアイテム {#most-popular}
-
-[AIアイテム・レコメンデーション][1]機能には、「AIパーソナライズド」モデルに加え、ユーザーが最も興味を持つアイテムをフィーチャーする「最も人気」のレコメンデーションモデルも含まれている。
-
-追跡されているインタラクションデータに基づき、このモデルのユースケースには、レコメンデーションが含まれる：
-
-- [最も人気のある商品](#most-popular-items)
-- [最も人気のある「いいね！」アイテム](#liked-items)
-- [最も閲覧されたアイテム](#most-viewed-items)
-- [ユーザーのカートで人気のアイテム](#popular-items-in-users-carts)
-
-### 最新のおすすめアイテム {#most-recent}
-
-[AIアイテム・レコメンデーション][1]機能には、「AIパーソナライズド」モデルに加え、ユーザーが最も興味を持ったアイテムを紹介する「最新」のレコメンデーションモデルも含まれている。このモデルを利用して、離脱したユーザーに関連コンテンツへの再アクセスを促し、解約を減らす。
-
-追跡されているインタラクションデータに基づき、このモデルのユースケースには、レコメンデーションが含まれる：
-
-- [最近クリックされた項目](#recently-clicked-items)
-- [最近「いいね！」されたアイテム](#liked-items)
-- [最近契約または購入した商品](#recently-engaged-with-or-purchased-items)
-- [最近カートに入れた商品](#items-recently-added-to-cart)
-
-### セレクションに基づく推薦 {#selections-based}
-
-[セレクションは]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)、カタログデータの特定のグループである。選択範囲を使用する場合、基本的にはカタログの特定の列に基づいてカスタムフィルターを設定することになる。これには、ブランド、サイズ、場所、追加日などのフィルターが含まれる。ユーザーに表示するアイテムを満たすべき基準を定義できるため、何を推薦するかをコントロールできる。
-
-前の3つのタイプはすべて、Brazeで推薦モデルを設定し、トレーニングする。これらのモデルでセレクションを使うこともできるが、カタログのセレクションとリキッドパーソナライゼーションだけで、レコメンデーションのユースケースを達成することもできる。
-
-いくつかの使用例には、推薦が含まれる：
-
-- [新商品](#new-items)
-- [ランダムアイテム](#random-items)
-
-### ルールに基づく推奨 {#rules-based}
-
-[ルールベースのレコメンデーションエンジンは]({{site.baseurl}}/rules_based_recommendations/)、ユーザーデータと商品情報を使って、メッセージ内でユーザーに関連商品を提案する。LiquidとBrazeカタログまたはConnected Contentを使用して、ユーザーの行動や属性に基づいてコンテンツを動的にパーソナライズする。
-
-ルール・ベースの推奨は、手動で設定しなければならない固定ロジックに基づいている。つまり、ロジックを更新しない限り、レコメンデーションはユーザー個々の購入履歴や嗜好に合わせて調整されないため、この方法は頻繁な更新を必要としないレコメンデーションに最適である。
-
-いくつかの使用例がある：
-
-- **再入荷のリマインダー：**毎月のビタミン剤や毎週の食料品など、使用サイクルが予測できる商品については、最終購入日に基づいて再入荷リマインダーを送信する。
-- **初回購入者である：**初回購入者にスターターキットや紹介キャンペーンを勧め、2回目の購入を促す。
-ロイヤリティ・プログラム：顧客の現在のポイント残高に応じて、ロイヤルティポイントや特典を最大限に活用できる商品を紹介する。
-- **教育的な内容である：**過去に消費または購入した教材のトピックに基づいて、新しいコースやコンテンツを提案する。
-
-## ユースケース
-
-### ユーザーが次に購入する可能性の高いアイテム
-
-購入イベントや購入に関連するカスタムイベントに基づいて、ユーザーが次に購入する可能性の高いアイテムを予測し、推奨する。以下に例を示します。
-
-- 旅行サイトは、ユーザーの閲覧履歴や過去の予約に基づいて、バケーション・パッケージやフライト、ホテルの宿泊を提案し、ユーザーの次の旅行先を予測し、旅行の計画を立てやすくすることができる。
-- ストリーミング・プラットフォームは、視聴習慣を分析し、ユーザーが次に見る可能性の高い番組や映画を推薦することができる。
-
-{% details 必要条件 %}
-
-- AIアイテムの推奨
-- 関連商品カタログ
-- 購入オブジェクトまたはカスタムイベントによる購入を追跡する方法。
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. [AIアイテムの推奨を]({{site.baseurl}}/ai_item_recommendations)作成する。
-2. **タイプを** **AIパーソナライズドに**設定する。
-3. カタログを選択する。
-4. (オプション) 選択肢を追加して、関連するアイテムのみに推薦文をフィルタリングする。
-5. 現在どのように購入イベントを追跡しているか、また対応するイベントプロパティを選択する。
-6. 推薦者を訓練する。
-7. [メッセージングに推薦文を使う]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)。
-
-{% enddetails %}
-
-### 最近カートに入れた商品
-
-最近カートに入れたが、まだ購入していない商品への興味をユーザーに思い出させる。例えば、オンライン小売業者は、リマインダーを送信したり、カート内の商品について期間限定の割引を提供したりすることで、ユーザーにオファーの期限が切れる前に購入を完了するよう促すことができる。
-
-{% details 必要条件 %}
-
-- AIアイテムの推奨
-- 関連商品カタログ
-- カートに入れた時のカスタムイベント
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. [AIアイテムの推奨を]({{site.baseurl}}/ai_item_recommendations)作成する。
-2. **Typeを** **Most recentに**設定する。
-3. カタログを選択する。
-4. (オプション) 選択肢を追加して、関連するアイテムのみに推薦文をフィルタリングする。
-5. **カスタムイベントを**選択し、リストからカートに追加するカスタムイベントを選択する。
-6. 推薦者を訓練する。
-7. [メッセージングに推薦文を使う]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)。
-
-{% enddetails %}
-
-### 気に入ったアイテム
-
-ユーザーが最近「いいね！」したアイテムや、「いいね！」が多いアイテムを、「いいね！」用のカスタムイベントに基づいて探索するよう促す。例えば、音楽ストリーミングアプリは、ユーザーが過去に気に入ったジャンルやアーティストに基づいて、パーソナライズされたプレイリストを作成したり、新しいアルバムのリリースを提案したりすることができる。
-
-{% details 必要条件 %}
-
-- AIアイテムの推奨
-- 関連商品カタログ
-- いいね！のためのカスタムイベント
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. [AIアイテムの推奨を]({{site.baseurl}}/ai_item_recommendations)作成する。
-2. **Typeを** **Most recentに**設定する。
-3. カタログを選択する。
-4. (オプション) 選択肢を追加して、関連するアイテムのみに推薦文をフィルタリングする。
-5. **カスタムイベントを**選び、リストから「いいね！」のカスタムイベントを選ぶ。
-6. 推薦者を訓練する。
-7. [メッセージングに推薦文を使う]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)。
-
-{% enddetails %}
-
-### 最も人気のある商品
-
-購入履歴をもとに、ユーザーにカタログの人気アイテムの探索を促す。関連性の高いコンテンツだけを表示させるには、選択項目でフィルタリングすることをお勧めする。例えば、フードデリバリー・サービスは、プラットフォーム上での注文の人気度に基づいて、ユーザーの地域内で評価の高い料理やレストランをハイライトし、試食や発見を促すことができる。
-
-{% details 必要条件 %}
-
-- AIアイテムの推奨
-- 関連商品カタログ
-- 購入オブジェクトまたはカスタムイベント
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. [AIアイテムの推奨を]({{site.baseurl}}/ai_item_recommendations)作成する。
-2. **Typeを** **Most popularに**設定する。
-3. カタログを選択する。
-4. (オプション) 選択肢を追加して、関連するアイテムのみに推薦文をフィルタリングする。例えば、フードデリバリーサービスでは、レストランの場所や料理の種類をフィルターにかけることができる。
-5. 現在のイベント追跡方法と、対応するイベントプロパティを選択する。
-6. 推薦者を訓練する。
-7. [メッセージングに推薦文を使う]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)。
-
-{% enddetails %}
-
-### 最も閲覧されたアイテム
-
-ビューを通じてユーザー全体の注目を集めたアイテムを強調し、エンゲージメントや購入を促す。例えば、不動産サイトは、ユーザーの検索エリアで最も閲覧された物件を表示し、多くの注目を集めている物件を強調することができる。
-
-{% details 必要条件 %}
-
-- AIアイテムの推奨
-- 関連商品カタログ
-- ビューのカスタムイベント
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. [AIアイテムの推奨を]({{site.baseurl}}/ai_item_recommendations)作成する。
-2. **Typeを** **Most popularに**設定する。
-3. カタログを選択する。
-4. (オプション) 選択肢を追加して、関連するアイテムのみに推薦文をフィルタリングする。
-5. **カスタムイベントを**選択し、リストからビューのカスタムイベントを選択する。
-6. 推薦者を訓練する。
-7. [メッセージングに推薦文を使う]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)。
-
-{% enddetails %}
-
-### 新商品
-
-このシナリオは、ユーザーのアクションに直接依存するのではなく、カタログデータに依存する。カタログに追加された日付に基づいて新商品をフィルタリングし、レコメンデーションモデルをトレーニングすることなく、ターゲットキャンペーンやキャンバスを通じて新商品をプロモーションすることができる。
-
-例えば、ハイテクeコマース・プラットフォームは、カタログに最近追加されたアイテムをターゲットとするフィルターを使用して、最新のガジェットや今後の予約注文についてハイテク愛好家に警告することができる。
-
-{% details 必要条件 %}
-
-- 日付フィールドが追加された関連アイテムのカタログ
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. カタログに基づいてセレクションを作成する。カタログに、アイテムが追加された日付に対応する時間フィールド（**データ型が** **時間に**設定されたフィールド）があることを確認する。
-2. (オプション）必要に応じてフィルターを追加する。
-3. **ソート順のランダム化**」がオフになっていることを確認する。
-4. **ソート・フィールド（Sort Field）**」で、追加した日付のフィールドを選択する。
-5. **ソート順を**降順に設定する。
-6. [メッセージで選択する]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/#using-selections-in-messaging)。
-
-{% enddetails %}
-
-### ユーザーのカートで人気のアイテム
-
-多くの買い物客がカートに入れた商品を紹介することで、ユーザーに商品のトレンドを伝える。
-
-例えば、ファッション小売業者は、他の顧客によってカートに追加された人気商品に基づいて、流行の服やアクセサリーを宣伝することができる。そして、ホームページやモバイルアプリにダイナミックな "Trending Now "セクションを作り、リアルタイムで更新することで、商品が売り切れる前に買い物客に購入を促すことができる。
-
-{% details 必要条件 %}
-
-- AIアイテムの推奨
-- 関連商品カタログ
-- カートに入れた時のカスタムイベント
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. [AIアイテムの推奨を]({{site.baseurl}}/ai_item_recommendations)作成する。
-2. **Typeを** **Most popularに**設定する。
-3. カタログを選択する。
-4. (オプション) 選択肢を追加して、関連するアイテムのみに推薦文をフィルタリングする。
-5. **カスタムイベントを**選択し、リストからカートに追加するカスタムイベントを選択する。
-6. 推薦者を訓練する。
-7. [メッセージングに推薦文を使う]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)。
-
-{% enddetails %}
-
-### ランダムアイテム
-
-多様なユーザー体験のために、ランダムなアイテムを推薦することは、多様性を導入し、あまり訪問されていないカタログ領域への興味を喚起する可能性がある。この方法では、特定のモデルやイベントを必要とせず、カタログのセレクションを使ってアイテムがランダムに表示されるようにする。
-
-例えば、オンライン書店が「サプライズ・ミー」機能を提供し、ユーザーの過去の購入履歴や閲覧習慣に基づいてランダムに本を推薦することで、通常の読書ジャンル以外の探求を促すことができる。
-
-{% details 必要条件 %}
-
-- 関連商品カタログ
-- **ソート順をランダムにするを**オンにした選択
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. カタログに基づいて[セレクションを作成する]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/#creating-a-selection)。
-2. (オプション）必要に応じてフィルターを追加する。
-3. **ソート順をランダムにするを**オンにする。
-4. [メッセージで選択する]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/#using-selections-in-messaging)。
-
-{% enddetails %}
-
-### 最近クリックされた項目
-
-クリックのカスタムイベントに基づいて、最近クリックしたアイテムへの再訪問をユーザーに促す。例えば、オンライン・ファッションの小売業者は、ユーザーが興味を示した洋服をクリックすると、その洋服を特集したフォローアップ・メールやプッシュ通知を送るレコメンデーションを作成し、ユーザーにその商品を再訪問して購入するよう促すことができる。
-
-{% details 必要条件 %}
-
-- AIアイテムの推奨
-- 関連商品カタログ
-- クリック用のカスタムイベント
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. [AIアイテムの推奨を]({{site.baseurl}}/ai_item_recommendations)作成する。
-2. **Typeを** **Most recentに**設定する。
-3. カタログを選択する。
-4. (オプション) 選択肢を追加して、関連するアイテムのみに推薦文をフィルタリングする。
-5. **Custom Eventを**選択し、リストからクリック用のカスタムイベントを選択する。
-6. 推薦者を訓練する。
-7. [メッセージングに推薦文を使う]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)。
-
-{% enddetails %}
-
-### 最近契約または購入した商品
-
-閲覧、クリック、購入など、ユーザーが最近接触したアイテムを宣伝する。このアプローチにより、レコメンデーションは常に新鮮で、ユーザーの最新の関心に沿ったものになる。.以下に例を示します。
-
-- **教育だ：**オンライン教育プラットフォームは、最近教育ビデオを見たがコースに登録していないユーザーに対し、類似のコースや興味のある科目をチェックするよう促すことで、ユーザーの学習意欲を維持し、学習を開始させることができる。
-- **フィットネスだ：**フィットネス・アプリは、ユーザーが最近こなした、あるいは交流したものに似たワークアウトやチャレンジを提案することができ、エクササイズ・ルーティンを変化に富んだ魅力的なものに保つことができる。
-- **ホームセンターである：**顧客が電動工具を購入した後、ホームセンターは最近の購入品に基づいて関連アクセサリーや安全用品を推奨し、ユーザーの体験と安全性を高めることができる。
-
-{% details 必要条件 %}
-
-- AIアイテムの推奨
-- 関連商品カタログ
-- 購入オブジェクト、またはエンゲージメント・インタラクションのカスタム・イベント
-
-{% enddetails %}
-
-{% details 設定方法 %}
-
-1. [AIアイテムの推奨を]({{site.baseurl}}/ai_item_recommendations)作成する。
-2. **Typeを** **Most recentに**設定する。
-3. カタログを選択する。
-4. (オプション) 選択肢を追加して、関連するアイテムのみに推薦文をフィルタリングする。
-5. **Custom Eventを**選択し、リストからクリック用のカスタムイベントを選択する。
-6. 推薦者を訓練する。
-7. [メッセージングに推薦文を使う]({{site.baseurl}}/user_guide/sage_ai/recommendations/ai_item_recommendations/#using-recommendations-in-messaging)。
-
-{% enddetails %}
-
-[1]: {{site.baseurl}}/ai_item_recommendations
diff --git a/_lang/ja/_user_guide/sage_ai/recommendations/ai_item_recommendations.md b/_lang/ja/_user_guide/sage_ai/recommendations/ai_item_recommendations.md
deleted file mode 100644
index 0447583654d..00000000000
--- a/_lang/ja/_user_guide/sage_ai/recommendations/ai_item_recommendations.md
+++ /dev/null
@@ -1,322 +0,0 @@
----
-nav_title: AIアイテムのおすすめ
-article_title: AIアイテムのおすすめ
-page_order: 15
-alias: "/ai_item_recommendations/"
-description: "このリファレンス記事では、カタログ内のアイテムに対するAIアイテム推薦の作成方法について説明します。"
----
-
-# AIアイテムのおすすめ
-
-> カタログ内のアイテムに対するAIアイテム推薦の作成方法を学びます。
-
-AIアイテムの推奨を使用して、最も人気のある製品を計算したり、特定の[カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/)のためにパーソナライズされたAI推奨を作成したりできます。レコメンデーションを作成した後、パーソナライゼーションを使用してそれらの製品をメッセージに挿入できます。
-
-## 前提条件
-
-- 少なくとも1つの\[カタログ]\[カタログ]を使用して、以下に説明する推奨タイプのいずれかを使用する必要があります。
-- Braze（カスタムイベントまたは購入オブジェクト）に購入またはイベントデータがあり、カタログに保存されている一意の製品IDへの参照が含まれている必要があります。
-- AIパーソナライズされた推奨事項は、数百または数千のアイテムで最も効果的に機能し、通常、購入またはインタラクションデータを持つ少なくとも30,000人のユーザーが必要です。これはあくまで大まかなガイドであり、変動する可能性があります。他の推奨タイプは、より少ないデータで動作できます。
-
-## AIアイテム推薦の作成
-
-アイテムの推薦を作成するには:
-
-1. **分析** > **AIアイテム推薦**に移動します。
-2. **Create 予測** > **AI アイテム推薦**。
-
-個々のカタログから直接推奨を作成することもできます。**カタログ** ページからカタログを選択し、**おすすめを作成** をクリックします。
-
-### ステップ 1:推奨事項の詳細を追加
-
-まず、あなたの推薦に名前とオプションの説明を付けてください。
-
-![][1]
-
-### ステップ 2:あなたの推薦を定義する {#recommendation-type}
-
-次に、推奨タイプを選択します。すべての推奨タイプは、過去6か月間のアイテムインタラクション（購入またはカスタムイベント）データを使用します。以下に記載されているインタラクションは、購入イベントまたはステップ3で選択されたカスタムイベントを指します。
-
-- **最も人気があります:**カタログ内のすべてのユーザーが最も頻繁に操作する最大30個のアイテムを計算します。例えば、最も購入された製品などです。
-- **最新:**ユーザーが最近最も多くやり取りした最大30製品のリストを作成します。
-- **AIパーソナライズされた:**トランスフォーマーという新しい種類の深層学習を使用して、各ユーザーが次に操作する可能性が最も高いアイテムのセットを予測します。次に最も可能性の高いアイテムを最も可能性の高い順に最大30個まで計算します。このタイプの推奨は、他のBraze顧客のデータとあなたのデータを組み合わせるために大規模言語モデル（LLM）を使用しません。
-
-{% alert tip %}
-**最新**または**AIパーソナライズされた**を使用する場合、個別の推奨を作成するためのデータが不十分なユーザーは、フォールバックとして**最も人気のある**アイテムを受け取ります。ユーザーの割合が**最も人気のある**フォールバックを受け取っていることが**分析**ページに表示されます。
-{% endalert %}
-
-#### ステップ 2a: 以前の購入またはやり取りを除外する（オプション）
-
-ユーザーがすでに購入または操作したアイテムを提案しないようにするには、**ユーザーが以前に操作したアイテムを推奨しない**を選択してください。このオプションは、推奨**タイプ**が**AIパーソナライズされた**に設定されている場合にのみ利用可能です。
-
-![]\[2-3]
-
-この設定により、ユーザーが既に購入または操作したアイテムが、最近推奨が更新された場合にメッセージに再表示されないようにします。推奨の更新間に購入または操作されたアイテムは、まだ表示される場合があります。アイテム推薦の無料版では、更新は毎週行われます。AIアイテム推奨のプロバージョンでは、更新は24時間ごとに行われます。
-
-例えば、AIアイテム推薦のプロバージョンを使用する場合、ユーザーが何かを購入し、その後30分以内にマーケティングメールを受け取ると、購入したばかりのアイテムがメールから除外されない可能性があります。ただし、24時間後に送信されたメッセージにはそのアイテムは含まれません。
-
-#### ステップ 2b: カタログを選択
-
-まだ入力されていない場合は、この推奨事項がアイテムを取得する \[カタログ]\[カタログ] を選択します。
-
-#### ステップ 2c: 選択を追加（オプション）
-
-推奨事項をさらに制御したい場合は、[選択]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/)を選択してカスタムフィルタを適用します。選択は、カタログ内の特定の列（ブランド、サイズ、場所など）によってフィルター推奨を行います。Liquid を含む選択は、あなたの推薦に使用できません。
-
-![]\[2-2]
-
-{% alert tip %}
-選択が見つからない場合は、まずカタログに設定されていることを確認してください。
-{% endalert %}
-
-### ステップ 3:推奨事項を推進するためのインタラクションを選択
-
-次に、この推奨事項を最適化するイベントを選択します。このイベントは通常購入ですが、アイテムとのやり取りである場合もあります。
-
-最適化できます:
-
-- [購入オブジェクト]({{site.baseurl}}/api/objects_filters/purchase_object/)でイベントを購入する
-- 購入を表すカスタムイベント
-- カスタムイベントは、他のアイテムのインタラクション（製品の閲覧、クリック、メディアの再生など）を表します。
-
-**カスタムイベント**を選択した場合、リストからイベントを選択してください。
-
-![][3]
-
-### ステップ 4:対応するプロパティ名{#property-name}を選択してください
-
-レコメンデーションを作成するには、Braze に対して、インタラクションイベント（購入オブジェクトまたはカスタムイベント）のどのフィールドにアイテムのカタログ内の`id`フィールドと一致する一意の識別子があるかを伝える必要があります。わからない？[要件を表示](#requirements).
-
-このフィールドを**プロパティ名**に選択します。
-
-**プロパティ名**フィールドは、SDKを通じてBrazeに送信されたフィールドのリストで事前に入力されます。十分なデータが提供されれば、これらのプロパティも正しいプロパティである確率の順にランク付けされます。カタログの`id`フィールドに対応するものを選択してください。
-
-![][4]
-
-#### 要件 {#requirements}
-
-プロパティを選択するためのいくつかの要件があります：
-
-- 選択したカタログの`id`フィールドにマップする必要があります。
-- **購入オブジェクトを選択した場合:**`product_id` またはインタラクションイベントの`properties`のフィールドである必要があります。
-- **カスタムイベントを選択した場合:**`properties`のカスタムイベントのフィールドである必要があります。
-- ネストされたフィールドは、**プロパティ名** ドロップダウンにドット表記で `event_property.nested_property` の形式で入力する必要があります。例えば、イベントプロパティ`location`内のネストされたプロパティ`district_name`を選択する場合、`location.district_name`を入力します。
-- フィールドは、（単一のイベント内の複数のカタログアイテムの）配列に含まれることがあります。それは自動的に平坦化されます。
-
-#### 例のマッピング
-
-次の例のマッピングはどちらもこのサンプルカタログを参照しています:
-
-<style type="text/css">
-.tg td{word-break:normal;}
-.tg th{word-break:normal;font-size: 14px; font-weight: bold; background-color: #f4f4f7; text-transform: lowercase; color: #212123; font-family: "Sailec W00 Bold",Arial,Helvetica,sans-serif;}
-.tg .tg-0pky{border-color:inherit;text-align:left;vertical-align:top;word-break:normal}
-</style>
-<table class="tg">
-<thead>
-  <tr>
-    <th class="tg-0pky">id</th>
-    <th class="tg-0pky">タイトル</th>
-    <th class="tg-0pky">価格</th>
-  </tr>
-</thead>
-<tbody>
-  <tr>
-    <td class="tg-0pky">ADI-BL-7</td>
-    <td class="tg-0pky">アディダス ブラック サイズ 7</td>
-    <td class="tg-0pky">100.00米ドル</td>
-  </tr>
-  <tr>
-    <td class="tg-0pky">ADI-RD-8</td>
-    <td class="tg-0pky">アディダス レッド サイズ 8</td>
-    <td class="tg-0pky">100.00米ドル</td>
-  </tr>
-  <tr>
-    <td class="tg-0pky">ADI-WH-9</td>
-    <td class="tg-0pky">アディダス ホワイト サイズ 9</td>
-    <td class="tg-0pky">100.00米ドル</td>
-  </tr>
-  <tr>
-    <td class="tg-0pky">ADI-PP-10</td>
-    <td class="tg-0pky">アディダス パープル サイズ 10</td>
-    <td class="tg-0pky">75.00米ドル</td>
-  </tr>
-</tbody>
-</table>
-
-{% tabs %}
-{% tab カスタムイベント %}
-
-たとえば、顧客がチェックアウトする前に類似商品を推薦できるように、カスタムイベント`added_to_cart`を使用したいとします。イベント`added_to_cart`には`product_sku`のイベントプロパティがあります。
-
-次に、`product_sku`プロパティには、サンプルカタログの`id`列の値のうち少なくとも1つを含める必要があります。「ADI-BL-7」、「ADI-RD-8」、「ADI-WH-9」、または「ADI-PP-10」。すべてのカタログアイテムにイベントが必要なわけではありませんが、レコメンデーションエンジンが動作するための十分なコンテンツを持つためには、いくつかのイベントが必要です。
-
-##### カスタムイベントオブジェクトの例
-
-このイベントには`"product_sku": "ADI-BL-7"`があり、サンプルカタログの最初のアイテムに一致します。
-
-```json
-{
-  "events" : [
-    {
-      "external_id" : "user1",
-      "app_id" : "your-app-id",
-      "name" : "added_to_cart",
-      "time" : "2024-07-16T19:20:30+01:00",
-      "properties" : {
-        "product_sku": "ADI-BL-7"
-      }
-    }
-  ]
-}
-```
-
-{% endtab %}
-{% tab 購入オブジェクト %}
-
-購入オブジェクトは、購入が行われたときにAPIを通じて渡されます。
-
-マッピングに関しては、カスタムイベントと同様のロジックが購入オブジェクトにも適用されますが、購入オブジェクトの`product_id`または`properties`オブジェクトのフィールドを使用するかを選択できます。
-
-覚えておいてください、すべてのカタログアイテムにイベントが必要なわけではありませんが、レコメンデーションエンジンが作業するのに十分なコンテンツを持つためには、いくつかのイベントが必要です。
-
-##### 製品IDにマッピングされた購入オブジェクトの例
-
-このイベントには`"product_id": "ADI-BL-7`があり、カタログの最初の項目に対応しています。
-
-```json
-{
-  "purchases": [
-    {
-      "external_id": "user1",
-      "app_id": "11ae5b4b-2445-4440-a04f-bf537764c9ad",
-      "product_id": "ADI-BL-7",
-      "currency": "USD",
-      "price": 100.00,
-      "time": "2024-07-16T19:20:30+01:00",
-      "properties": {
-        "color": "black",
-        "checkout_duration": 180,
-        "size": "7",
-        "brand": "Adidas"
-      }
-    }
-  ]
-}
-```
-
-##### プロパティフィールドにマッピングされた購入オブジェクトの例
-
-このイベントには`"sku": "ADI-RD-8"`のプロパティがあり、カタログの2番目のアイテムにマップされます。
-
-```json
-{
-  "purchases": [
-    {
-      "external_id": "user1",
-      "app_id": "11ae5b4b-2445-4440-a04f-bf537764c9ad",
-      "product_id": "shoes",
-      "currency": "USD",
-      "price": 100.00,
-      "time": "2024-07-16T19:20:30+01:00",
-      "properties": {
-        "sku": "ADI-RD-8",
-        "color": "red",
-        "checkout_duration": 180,
-        "size": "8",
-        "brand": "Adidas"
-      }
-    }
-  ]
-}
-```
-
-{% endtab %}
-{% endtabs %}
-
-### ステップ 5: トレーニング the recommendation
-
-準備ができたら、**推奨事項を作成**を選択します。このプロセスは完了するまでに10分から36時間かかることがあります。推奨が正常にトレーニングされるか、作成が失敗した理由の説明があると、メール更新を受け取ります。
-
-推奨事項は**予測**ページにあり、必要に応じて編集またはアーカイブできます。推奨事項は毎月1回自動的に再訓練されます。
-
-## 分析
-
-推奨事項の分析を表示して、ユーザーに推奨されたアイテムと推奨モデルの精度を確認できます。
-
-1. **分析** > **アイテム推薦** に移動します。
-2. リストからあなたの推薦を選択してください。
-
-ページの上部には、精度やカバレッジなど、あなたの推薦に関する統計情報が表示されます。
-
-![][5]
-
-これらの指標は次の表で定義されています。 
-
-| メートル法              | 説明 |
-| ------------------- | ---------- |
-| 精度           | モデルがユーザーが次に購入したアイテムを正しく予測した時間の割合。精度は特定のカタログのサイズとミックスに大きく依存しており、モデルがどのくらい正しいかを理解するためのガイドとして使用する必要があります。<br><br>過去のテストでは、精度が6〜20％の範囲でモデルが良好に機能することを確認しました。このメトリックは、モデルが次に再トレーニングされると更新されます。  |
-| カバレッジ            | カタログ内の利用可能なアイテムのうち、少なくとも1人のユーザーに推奨される割合はどれくらいですか。最も人気のあるアイテムよりも、パーソナライズされたアイテムのおすすめで、より高いアイテムカバレッジが期待できます。 |
-| 推奨タイプ | パーセンテージのユーザーがパーソナライズされたまたは最新の推奨事項を受け取るのに対し、最も人気のあるアイテムのフォールバック。フォールバックは、パーソナライズされたまたは最新の推薦を生成するのに十分なデータがないユーザーに送信されます。 |
-{: .reset-td-br-1 .reset-td-br-2}
-
-次のセクションでは、カタログ内のアイテムの内訳を示し、2つの列に分けています。
-
-- **パーソナライズされたアイテム** または **最新のアイテム:**この列には、ユーザーに最も頻繁に推奨される順にカタログ内の各アイテムが表示されます。この列は、モデルによって各アイテムに割り当てられたユーザーの数も示しています。
-- **最も人気のある商品**この列には、カタログ内の各アイテムが人気の降順でリストされています。ここでの人気度とは、ユーザーがワークスペース全体で最も頻繁に操作するカタログ内のアイテムを指します。パーソナライズされたまたは最新のものを個々のユーザーに対して計算できない場合、フォールバックとして最も人気のあるものが使用されます。
-
-![][6]
-
-**推奨事項の概要**には、選択した推奨事項の構成の概要が表示され、推奨事項が最後に更新された日時が含まれます。
-
-![][7]{: style="max-width:45%" }
-
-## メッセージングでの推奨事項の使用
-
-![][10]{: style="max-width:30%;float:right;margin-left:15px;"}
-
-推奨事項のトレーニングが終了したら、Liquidを使用してメッセージをパーソナライズし、そのカタログで最も人気のある製品を挿入できます。Liquidは、メッセージ作成者にあるパーソナライゼーションウィンドウで生成できます:
-
-1. パーソナライゼーションをサポートするメッセージ作成者では、パーソナライゼーションウィンドウを開くには、<i class="fa-solid fa-circle-plus" style="color: #12aec5;" title="パーソナライゼーションを追加"></i>をクリックします。
-2. **パーソナライゼーション Type**、**Item Recommendation**を選択します。
-3. **アイテム推奨名**の場合は、作成したばかりの推奨を選択します。
-4. 「**予測されたアイテムの数**」には、挿入したいトップ製品の数を入力してください。例えば、最も購入されたアイテムのトップ3を表示できます。
-5. **表示する情報**については、各アイテムに含めるべきカタログのフィールドを選択します。これらのフィールドの各項目の値は、この推奨事項に関連付けられたカタログから取得されます。
-6. **アイコンをクリックして**、メッセージ内の必要な場所にLiquidを貼り付けてください。
-
-## AIアイテム推奨ティア
-
-次の表は、AIアイテム推奨の無料版とプロ版の違いを説明しています:
-
-| エリア                   | 無料版                          | プロバージョン            |
-| :---------------------- | ------------------------------------- | :--------------------------------------- |
-| ユーザー更新頻度<sup>1</sup>   | 毎週                                | 毎日                                    |
-| モデル再訓練の頻度  | 毎月                               | 毎月                                   |
-| 最大の推奨事項 | タイプごとに1つの推奨事項<sup>1</sup> | タイプごとの100の推奨事項<sup>2</sup> |
-
-<sup>1. これは、ユーザー固有のアイテム推奨が更新される頻度です（モデルが再トレーニングされると更新されるMost Popularアイテムを除くすべてのモデル）。例えば、ユーザーがAIアイテム推薦に基づいて推奨されたアイテムを購入した場合、推奨アイテムはこの頻度</sup>に従って更新されます。
-<sup>2\.利用可能な推奨タイプは、AIパーソナライズされた、最新、および最も人気があります。</sup>
-
-## よくある質問
-
-### 「最も人気のある」アイテムが他のモデルの推薦に混ざる原因は何ですか？
-
-当社のレコメンデーションエンジンがリストをキュレーションする際、まず「最新」や「AIパーソナライズされた」など、選択した特定のモデルに基づいてパーソナライズされた選択を優先します。このモデルが何らかの理由で30件の推奨事項の完全なリストを埋めることができない場合、すべてのユーザーの中で最も人気のあるアイテムのいくつかが追加され、各ユーザーが常に完全な推奨事項のセットを持つようにします。
-
-これはいくつかの特定の条件下で発生します:
-
-- モデルは、条件に一致するアイテムが30個未満であることを見つけます。
-- 該当する商品はもう利用できないか、在庫がありません。
-- アイテムは現在の選択基準を満たしていない可能性があります。在庫の変更やユーザーの好みによるものかもしれません。
-
-[1]: {% image_buster /assets/img/item_recs_1.png %}
-\[2-1]: {% image_buster /assets/img/item_recs_2-1.png %}
-\[2-2]: {% image_buster /assets/img/item_recs_2-2.png %}
-\[2-3]: {% image_buster /assets/img/item_recs_2-3.png %}
-[3]: {% image_buster /assets/img/item_recs_3.png %}
-[4]: {% image_buster /assets/img/item_recs_4.png %}
-[5]: {% image_buster /assets/img/item_recs_analytics_1.png %}
-[6]: {% image_buster /assets/img/item_recs_analytics_2.png %}
-[7]: {% image_buster /assets/img/item_recs_analytics_3.png %}
-[10]: {% image_buster /assets/img/add_personalization.png %}
-\[catalog]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/
diff --git a/_lang/ja/_user_guide/sage_ai/recommendations/rules_based_recommendations.md b/_lang/ja/_user_guide/sage_ai/recommendations/rules_based_recommendations.md
deleted file mode 100644
index f8083cc709f..00000000000
--- a/_lang/ja/_user_guide/sage_ai/recommendations/rules_based_recommendations.md
+++ /dev/null
@@ -1,283 +0,0 @@
----
-nav_title: ルールベースの推奨
-article_title: ルールベースの推奨
-page_type: tutorial
-page_order: 16
-alias: "/rules_based_recommendations/"
-description: "この記事では、カタログまたはコネクテッドコンテンツを使用するルールベースのレコメンデーションエンジンの作成方法について説明します。"
-tool:
-  - Campaigns
-  - Canvas
-
----
-
-# ルールベースの推奨事項
-
-> ルールベースのレコメンデーションエンジンは、ユーザーデータと製品情報を使用して、メッセージ内でユーザーに関連するアイテムを提案します。それは[Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/)とBraze [カタログ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/)または[コネクテッドコンテンツ]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/)のいずれかを使用して、ユーザーの行動と属性に基づいてコンテンツを動的にパーソナライズします。
-
-Liquid、カタログ、コネクテッドコンテンツについて詳しく知るには、これらのBraze学習コースをチェックしてください:
-
-- [パーソナライズされたおすすめとメール](https://learning.braze.com/personalized-recommendations-with-email)
-- [Liquid によるダイナミックパーソナライゼーション](https://learning.braze.com/path/dynamic-personalization-with-liquid)
-- [コネクテッドコンテンツの基礎](https://learning.braze.com/path/dynamic-personalization-with-liquid/connected-content-fundamentals)
-
-{% alert important %}
-ルールベースの推奨事項は、手動で設定する必要がある固定ロジックに基づいています。これは、ロジックを更新しない限り、あなたの推奨事項がユーザーの購入履歴や好みに調整されないことを意味します。<br><br>ユーザーの履歴に自動的にAdjustするパーソナライズされたAIレコメンデーションを作成するには、[AI item recommendations]({{site.baseurl}}/ai_item_recommendations)をチェックしてください。
-{% endalert %}
-
-## カタログのレコメンデーションエンジンを作成する
-
-1. [製品のカタログを作成する]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/)
-2. 各製品について、区切り文字（パイプ`|`など）で区切られた文字列として推奨製品のリストを「product_recommendations」という列に追加します。
-3. 製品IDをカタログに渡して、推奨事項を見つけてください。
-4. そのカタログアイテムの`product_recommendations`値を取得し、Liquid分割フィルターでデリミタで分割します。
-5. それらのIDの1つ以上をカタログに戻して、他の製品の詳細を収集します。
-
-### カタログのユースケース
-
-たとえば、健康食品アプリを持っていて、ユーザーがアプリにサインアップしてからの期間に応じて異なるレシピを送信するコンテンツカードキャンペーンを作成したいとします。 
-
-1. CSVを介して次の情報を含むカタログを作成してアップロードします:<br>- **id:**ユーザーがあなたのアプリにサインアップしてからの日数に相当するユニークな番号。例えば、`3`は3日間に相当します。<br>**タイプ:**レシピのカテゴリ、例えば`comfort`、`fresh`、その他。<br>**タイトル:**各IDに送信されるコンテンツカードのタイトルは、「今週のランチのために作り置き」や「タコスについて話そう」などです。<br>**リンク:**レシピ記事へのリンク。<br>**画像_url:**レシピに対応する画像。
-
-{: start="2"}
-2\.カタログがBrazeにアップロードされた後、カタログアイテムの一部のプレビューを確認して、情報が正確にインポートされたことを確認してください。アイテムはプレビューでランダム化される場合がありますが、レコメンデーションエンジンの出力には影響しません。
-
-![][1]
-
-{: start="3"}
-3\.コンテンツカードキャンペーンを作成します。コンポーザーで、どのユーザーがキャンペーンを受け取るべきか、どのレシピと画像を表示するべきかを決定するためにLiquidロジックを入力します。このユースケースでは、Braze はユーザーの`start_date`（またはサインアップ日）を取得し、現在の日付と比較します。日数の違いによって、どのコンテンツカードが送信されるかが決まります。 
-
-![][2]
-
-**Title:**
-
-{% raw %}
-```liquid
-{% assign start_date = {{custom_attribute.${start_date}}} | date: "%s" %}
-{% assign current_date = "now" | date: "%s" %}
-{% assign diff = {{current_date}} | minus: {{start_date}} | divided_by: 86400 %}
-{% assign days = {{diff}} | round %}
-{% catalog_items Healthy_Recipe_Catalog_SMB {{days}} %}
-{{ items[0].title }}
-```
-{% endraw %}
-
-**メッセージ:**
-
-{% raw %}
-```liquid
-{% assign start_date = {{custom_attribute.${start_date}}} | date: "%s" %}
-{% assign current_date = "now" | date: "%s" %}
-{% assign diff = {{current_date}} | minus: {{start_date}} | divided_by: 86400 %}
-{% assign days = {{diff}} | round %}
-{% catalog_items Healthy_Recipe_Catalog_SMB {{days}} %}
-{% if items[0].title != blank %}
-{{ items[0].body }}
-{% else %}
-{% abort_message('no card for today') %}
-{% endif %}
-```
-{% endraw %}
-
-**画像：**
-
-{% raw %}
-```liquid
-{% assign start_date = {{custom_attribute.${start_date}}} | date: "%s" %}
-{% assign current_date = "now" | date: "%s" %}
-{% assign diff = {{current_date}} | minus: {{start_date}} | divided_by: 86400 %}
-{% assign days = {{diff}} | round %}
-{% catalog_items Healthy_Recipe_Catalog_SMB {{days}} %}
-{{ items[0].image_url }}
-```
-{% endraw %}
-
-{: start="4"}
-4\.「**クリック時の動作**」セクションで、iOS、Android、およびWebデバイスでコンテンツカードをクリックしたときにユーザーがリダイレクトされる場所のLiquidロジックを入力します。 
-
-{% raw %}
-```liquid
-{% assign start_date = {{custom_attribute.${start_date}}} | date: "%s" %}
-{% assign current_date = "now" | date: "%s" %}
-{% assign diff = {{current_date}} | minus: {{start_date}} | divided_by: 86400 %}
-{% assign days = {{diff}} | round %}
-{% catalog_items Healthy_Recipe_Catalog_SMB {{days}} %}
-{{ items[0].link }}
-```
-{% endraw %}
-
-![][3]{: style="max-width:60%;"}<br><br>
-
-{: start="5"}
-5\.**テスト** タブに移動し、**ユーザーとしてメッセージをプレビュー** の下の **カスタムユーザー** を選択します。日付を**カスタム属性**フィールドに入力して、その日にサインアップしたユーザーに送信されるコンテンツカードをプレビューします。<br><br>
-
-![][4]
-
-## コネクテッドコンテンツレコメンデーションエンジンの作成
-
-1. 次のいずれかの方法でコネクテッドコンテンツエンドポイントを作成します:
-- スプレッドシートをJSON APIエンドポイントに変換するには、SheetDPのようなサービスを使用し、生成されるAPI URLに注意してください。
-- カスタムビルドの社内エンドポイントを構築、ホスト、および維持する
-- サードパーティのパートナーを通じてレコメンデーションエンジンを購入します。例えば、[Alloyパートナー]({{site.baseurl}}/partners/message_personalization/dynamic_content)の1つである[Amazon Personalise]({{site.baseurl}}/partners/message_personalization/dynamic_content/amazon_personalize/)、[Certona]({{site.baseurl}}/partners/message_personalization/dynamic_content/certona/)、[ダイナミックなYield]({{site.baseurl}}/partners/message_personalization/dynamic_content/dynamic_yield/)などがあります。
-
-2. メッセージ本文またはコンテンツブロックHTMLエディタにコネクテッドコンテンツLiquidを記述して、データベースを検索するエンドポイントを呼び出します。
-3. 与えられたユーザーのプロファイルで見つけたカスタム属性の値にLiquidを合わせます。
-4. 正しい推奨事項を結果として引き出します。
-
-{% raw %}
-```
-{% connected_content YOUR-API-URL :save items %}
-
-{% assign recommended_item_ids_from_user_profile = custom_attribute.${RECOMMENDED_ITEM_IDS} | split: ';' %}
-
-{% for item_id in recommended_item_ids_from_user_profile %}
-  {% assign recommended_item = items | where: "ITEM_ID", ITEM_ID | first %}
-  recommended_item.item_name
-{% endfor %}
-```
-{% endraw %}
-
-| 属性 | 交換 |
-| --- | --- |
-|`YOUR-API-URL` | APIの実際のURLに置き換えてください。 |
-|`RECOMMENDED_ITEM_IDS` | 推奨アイテムのIDを含むカスタム属性の実際の名前に置き換えてください。この属性は、セミコロンで区切られたIDの文字列であることが期待されます。 |
-|`ITEM_ID` | APIレスポンス内のアイテムIDに対応する属性の実際の名前に置き換えてください。 |
-{: .reset-td-br-1 .reset-td-br-2}
-
-{% alert note %}
-これは基本的な例であり、特定のニーズやデータ構造に基づいてさらに修正する必要があるかもしれません。詳細なガイダンスについては、[Liquidドキュメント]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid)を参照するか、開発者に相談してください。
-{% endalert %}
-
-## コネクテッドコンテンツ ユースケース
-
-レストランの推薦をZomatoレストランデータベースから引き出し、その結果を`restaurants`というローカル変数として保存したいとしましょう。次のコネクテッドコンテンツ呼び出しを行うことができます:
-
-{% raw %}
-```liquid
-
-{% connected_content https://developers.zomato.com/api/v2.1/search?entity_id={{city_id}}&entity_type=city&count=20&cuisines={{food_type}}&sort=rating:headers{“user-key”:“USER_KEY”} :save restaurants %}
-
-{{city_food.restaurants[0]}}
-```
-{% endraw %}
-
-次に、ユーザーの市区町村と食べ物の種類に基づいてレストランの推薦を引き出したいとしましょう。ユーザーの市区町村と食べ物の種類のカスタム属性を動的に挿入し、`restaurants`の値を変数`city_food.restaurants`に割り当てることで、これを行うことができます。
-
-コネクテッドコンテンツの呼び出しは次のようになります:
-
-{% raw %}
-```liquid
-{% assign city_id = {{custom_attribute.${city_id} | default: ‘306’}} %}
-{% assign food_type = {{custom_attribute.${food_type} | default: ‘471’}} %}
-
-{%- connected_content https://developers.zomato.com/api/v2.1/search?entity_id={{city_id}}&entity_type=city&count=20&cuisines={{food_type}}&sort=rating:headers{“user-key”:“USER_KEY”} :save restaurants %}
-
-{% assign restaurants = city_food.restaurants %}
-
-{{city_food.restaurants[0]}}
-```
-{% endraw %}
-
-応答をレストランの名前と評価のみに絞りたい場合は、次のように呼び出しの最後にフィルターを追加できます:
-
-{% raw %}
-```liquid
-{% assign city_id = {{custom_attribute.${city_id} | default: ‘306’}} %}
-{% assign food_type = {{custom_attribute.${food_type} | default: ‘471’}} %}
-
-{%- connected_content https://developers.zomato.com/api/v2.1/search?entity_id={{city_id}}&entity_type=city&count=20&cuisines={{food_type}}&sort=rating:headers{“user-key”:”USER_KEY”} :save restaurants %}
-{% assign restaurants = city_food.restaurants %}
-
-{{city_food.restaurants[0].restaurant.name}}
-{{city_food.restaurants[0].restaurant.user_rating.rating_text}}
-```
-{% endraw %}
-
-最後に、レストランのおすすめを評価ごとにグループ化したいとしましょう。次のことを行ってください:
-
-1. 「優秀」、「非常に良い」、「良い」の評価カテゴリの空の配列を作成するには`assign`を使用します。
-2. リスト内の各レストランの評価を調べる`for`ループを追加します。 
-- 評価が「優れている」場合は、レストラン名を`excellent_restaurants`文字列に追加し、各レストラン名を区切るために最後に*文字を追加します。 
-- 評価が「非常に良い」の場合は、レストラン名を`very_good_restaurants`文字列に追加し、最後に*文字を追加します。
-- 評価が「良い」の場合、レストラン名を`good_restaurants`文字列に追加し、最後に*文字を追加します。
-3. カテゴリごとのレストランの推薦数を4つに制限する。
-
-これは最終的な呼び出しがどのように見えるかです:
-
-{% raw %}
-```liquid
-{% assign city_id = {{custom_attribute.${city_id} | default: ‘306’}} %}
-{% assign food_type = {{custom_attribute.${food_type} | default: ‘471’}} %}
-{%- connected_content https://developers.zomato.com/api/v2.1/search?entity_id={{city_id}}&entity_type=city&count=20&cuisines={{food_type}}&sort=rating:headers{“user-key”:”USER_KEY”} :save restaurants %}
-{% assign restaurants = city_food.restaurants %}
-{% assign excellent_restaurants = “” %}
-{% assign very_good_resturants = “” %}
-{% assign good_restaurants = “” %}
-{% for list in restaurants %}
-{% if {{list.restaurant.user_rating.rating_text}} == `Excellent` %}
-{% assign excellent_restaurants = excellent_restaurants | append: list.restaurant.name | append: `*` %}
-{% elseif {{list.restaurant.user_rating.rating_text}} == `Very Good` %}
-{% assign very_good_restaurants = very_good_restaurants | append: list.restaurant.name | append: `*` %}
-{% elseif {{list.restaurant.user_rating.rating_text}} == `Good` %}
-{% assign good_restaurants = good_restaurants | append: list.restaurant.name | append: `*` %}
-{% endif %}
-{% endfor %}
-{% assign excellent_array = excellent_restaurants | split: `*` %}
-{% assign very_good_array = very_good_restaurants | split: `*` %}
-{% assign good_array = good_restaurants | split: `*` %}
-
-Excellent places
-{% for list in excellent_array %}
-
-{{list}}
-{% assign total_count = total_count | plus:1 %}
-{% if total_count >= 4 %}
-{% break %}
-{% endif %}
-{% endfor %}
-
-Very good places
-{% for list in very_good_array %}
-
-{{list}}
-{% assign total_count = total_count | plus:1 %}
-{% if total_count >= 4 %}
-{% break %}
-{% endif %}
-{% endfor %}
-
-Good places
-{% for list in good_array %}
-
-{{list}}
-{% assign total_count = total_count | plus:1 %}
-{% if total_count >= 4 %}
-{% break %}
-{% endif %}
-{% endfor %}
-```
-{% endraw %}
-
-ユーザーのデバイスに応答が表示される例については、以下のスクリーンショットを参照してください。
-
-![][5]{: style="max-width:30%;"}
-
-## 考慮事項
-
-どのレコメンデーションエンジンが利用可能なリソースとユースケースに適しているかを決定する際には、この考慮事項の表を参照してください。
-
-| 考慮事項 | Liquid | カタログ CSV | カタログ API | コネクテッドコンテンツ |
-| --- | --- | --- | --- | --- |
-| データポイントを消費しません | サポートされていません | サポートされている | サポートされている | サポートされている |
-| コードなしソリューション | サポートされていません | 事前生成されたLiquidがサポートされている場合 | サポートされていません | サポートされていません |
-| 高度なLiquidが必要な場合が多い | サポートされている | サポートされていません | サポートされていません | サポートされている |
-| 製品フィードのデータの更新 | サポートされていません | 推奨事項が頻繁に更新されない場合にサポートされます | 推奨事項が毎時更新される場合にサポートされます | サポートと推奨事項はリアルタイムまで更新されます |
-| Braze UI内で推奨事項を生成する | サポートされている | サポートされている | サポートされている | Braze 以外で生成された場合はサポートされません |
-| ホスティング、管理、トラブルシューティングの推奨データはありません | サポートされている | サポートされている | サポートされている | サポートされていません |
-{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
-
-[1]: {% image_buster /assets/img/recs/catalog_items.png %}
-[2]: {% image_buster /assets/img/recs/content_card_preview.png %}
-[3]: {% image_buster /assets/img/recs/on_click_behavior.png %}
-[4]: {% image_buster /assets/img/recs/custom_attributes_test.png %}
-[5]: {% image_buster /assets/img/recs/sample_response.png %}
\ No newline at end of file
diff --git a/_lang/ko/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/huawei_integration.md b/_lang/ko/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/huawei_integration.md
new file mode 100644
index 00000000000..ec148dff3ab
--- /dev/null
+++ b/_lang/ko/_developer_guide/platform_integration_guides/android/push_notifications/android/integration/huawei_integration.md
@@ -0,0 +1,132 @@
+---
+nav_title: 화웨이 통합
+article_title: Android용 화웨이 푸시 통합
+platform: Android
+page_order: 9
+description: "이 문서에서는 Huawei Android 연동 설정 방법에 대해 설명합니다."
+channel:
+  - push
+
+---
+
+# 화웨이 푸시 통합
+
+> [화웨이에서](https://huaweimobileservices.com/) 제조한 최신 휴대폰에는 Google의 FCM(Firebase Cloud Messaging) 대신 푸시 전송에 사용되는 서비스인 화웨이 모바일 서비스(HMS)가 탑재되어 있습니다.<br><br>이 가이드에서는 Braze를 통해 푸시를 전송하고 세분화, 분석, 캔버스 등 기존의 모든 Braze 기능을 활용하기 위해 Huawei Android 통합을 설정하는 방법을 설명합니다!
+
+## 1단계: 화웨이 개발자 계정 등록
+
+시작하기 전에 [Huawei 개발자 계정을](https://developer.huawei.com/consumer/en/console) 등록하고 설정해야 합니다. Huawei 계정에서 **내 프로젝트 > 프로젝트 설정 > 앱 정보로** 이동하여 `App ID` 및 `App secret` 을 기록해 둡니다.
+
+![]({% image_buster /assets/img/huawei/huawei-credentials.png %})
+
+## 2단계: Braze 대시보드에서 새 Huawei 앱 만들기
+
+Braze 대시보드의 **설정** 탐색 아래에 있는 **앱 설정으로** 이동합니다.
+
+**앱 추가를** 클릭하고 이름(예: 내 Huawei 앱)을 입력한 다음 플랫폼으로 `Android` 을 선택합니다.
+
+![]({% image_buster /assets/img/huawei/huawei-create-app.png %}){: style="max-width:60%;"}
+
+새 Braze 앱이 생성되면 푸시 알림 설정에서 푸시 제공업체로 `Huawei` 을 선택합니다. 다음으로 `Huawei Client Secret` 및 `Huawei App ID` 을 입력합니다.
+
+![]({% image_buster /assets/img/huawei/huawei-dashboard-credentials.png %})
+
+## 3단계: 앱에 화웨이 메시징 SDK를 통합하세요.
+
+화웨이는 애플리케이션에 화웨이 메시징 서비스를 통합하는 방법을 자세히 설명하는 [안드로이드 통합 코델랩을](https://developer.huawei.com/consumer/en/codelab/HMSPushKit/index.html) 제공했습니다. 시작하려면 다음 단계를 따르세요.
+
+코델랩을 완료한 후에는 사용자 지정 [Huawei 메시지 서비스를](https://developer.huawei.com/consumer/en/doc/development/HMS-References/push-HmsMessageService-cls) 생성하여 푸시 토큰을 얻고 메시지를 Braze SDK로 전달해야 합니다.
+
+{% tabs %}
+{% tab JAVA %}
+
+```java
+public class CustomPushService extends HmsMessageService {
+  @Override
+  public void onNewToken(String token) {
+    super.onNewToken(token);
+    Braze.getInstance(this.getApplicationContext()).setRegisteredPushToken(token);
+  }
+
+  @Override
+  public void onMessageReceived(RemoteMessage remoteMessage) {
+    super.onMessageReceived(remoteMessage);
+    if (BrazeHuaweiPushHandler.handleHmsRemoteMessageData(this.getApplicationContext(), remoteMessage.getDataOfMap())) {
+      // Braze has handled the Huawei push notification
+    }
+  }
+}
+```
+
+{% endtab %}
+{% tab KOTLIN %}
+
+```kotlin
+class CustomPushService: HmsMessageService() {
+  override fun onNewToken(token: String?) {
+    super.onNewToken(token)
+    Braze.getInstance(applicationContext).setRegisteredPushToken(token!!)
+  }
+
+  override fun onMessageReceived(hmsRemoteMessage: RemoteMessage?) {
+    super.onMessageReceived(hmsRemoteMessage)
+    if (BrazeHuaweiPushHandler.handleHmsRemoteMessageData(applicationContext, hmsRemoteMessage?.dataOfMap)) {
+      // Braze has handled the Huawei push notification
+    }
+  }
+}
+```
+
+{% endtab %}
+{% endtabs %}
+
+사용자 지정 푸시 서비스를 추가한 후 `AndroidManifest.xml` 에 다음을 추가합니다:
+
+```xml
+<service
+  android:name="package.of.your.CustomPushService"
+  android:exported="false">
+  <intent-filter>
+    <action android:name="com.huawei.push.action.MESSAGING_EVENT" />
+  </intent-filter>
+</service>
+```
+
+## 4단계: Huawei 푸시 보내기
+
+이 시점에서 Braze 대시보드에서 새 Huawei Android 앱을 생성하고, Huawei 개발자 자격 증명으로 앱을 구성하고, Braze 및 Huawei SDK를 앱에 통합했습니다.
+
+다음으로, Braze에서 새로운 푸시 캠페인을 테스트하여 통합을 테스트할 수 있습니다.
+
+### 새 푸시 알림 캠페인 만들기
+
+**캠페인** 페이지에서 새 캠페인을 만들고 메시지 유형으로 **푸시 알림을** 선택합니다.
+
+캠페인 이름을 지정한 후 푸시 플랫폼으로 **Android 푸시를** 선택합니다.
+
+![사용 가능한 푸시 플랫폼을 표시하는 캠페인 생성 작성기.]({% image_buster /assets/img/huawei/huawei-test-push-platforms.png %})
+
+다음으로 제목과 메시지로 푸시 캠페인을 작성합니다.
+
+### 테스트 푸시 보내기
+
+**테스트** 탭에서 [`changeUser(USER_ID_STRING)` 방법을]({{site.baseurl}}/developer_guide/platform_integration_guides/android/analytics/setting_user_ids/#assigning-a-user-id) 사용하여 앱에서 설정한 사용자 ID를 입력하고 **테스트 보내기를** 클릭하여 테스트 푸시를 보냅니다.
+
+![캠페인 작성 작성기의 테스트 탭에서 사용자 ID를 제공하고 '개별 사용자 추가' 필드에 입력하면 자신에게 테스트 메시지를 보낼 수 있습니다.]({% image_buster /assets/img/huawei/huawei-test-send.png %})
+
+이 시점에서 Braze로부터 Huawei(HMS) 디바이스로 테스트 푸시 알림을 받게 될 것입니다.
+
+### Huawei 세분화 설정(선택 사항)
+
+Braze 대시보드의 화웨이 앱은 안드로이드 푸시 플랫폼을 기반으로 구축되었으므로 모든 안드로이드 사용자(Firebase 클라우드 메시징 및 화웨이 모바일 서비스)에게 푸시를 보내거나 특정 앱으로 캠페인 대상을 세분화할 수 있는 유연성이 있습니다.
+
+화웨이 앱에만 푸시를 보내려면 \[새 세그먼트]({{ site.baseurl }}/user_guide/engagement_tools/segments/creating_a_segment/#step-3-choose-your-app-or-platform) )를 생성하고 **앱** 섹션에서 화웨이 앱을 선택합니다.
+
+![]({% image_buster /assets/img/huawei/huawei-segmentation.png %})
+
+물론 모든 안드로이드 푸시 제공업체에 동일한 푸시를 보내려면 현재 작업 영역 내에 구성된 모든 안드로이드 앱에 보낼 앱을 지정하지 않도록 선택할 수 있습니다.
+
+## 분석
+
+캠페인이 시작되면 Android 푸시용으로 집계된 캠페인 또는 캔버스에 대한 애널리틱스가 표시됩니다. Android 푸시 분석 및 설정에 대한 자세한 내용은 [푸시 사용 가이드를]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_reporting/) 참조하세요.
+
diff --git a/_lang/ko/_help/accessibility.md b/_lang/ko/_help/accessibility.md
new file mode 100644
index 00000000000..0f58829f37f
--- /dev/null
+++ b/_lang/ko/_help/accessibility.md
@@ -0,0 +1,179 @@
+---
+nav_title: 접근성 높은 메시지 작성
+article_title: Braze에서 접근성 높은 메시지 작성
+page_order: 3.5
+page_type: reference
+description: "이 참고 문서에서는 마케팅 콘텐츠에서 접근성을 고려하는 것이 중요한 이유와 Braze에서 접근성 메시지를 작성하는 방법을 설명합니다."
+---
+
+# Braze에서 접근성 높은 메시지 작성
+
+> 의도하지 않았더라도 장애인을 배제하는 마케팅 콘텐츠는 수백만 명의 사람들이 브랜드와 소통하지 못하게 만들 수 있습니다. 마케팅에서 접근성이란 누구나 쉽게 마케팅을 경험하고, 커뮤니케이션을 수신하고 이해하며, 제품, 서비스 또는 브랜드에 투자하거나 팬이 될 수 있는 기회를 가질 수 있도록 하는 것입니다. 메시징을 디자인할 때는 모든 고객이 디자인에 액세스할 수 있도록 하는 방법을 고려하는 데 시간을 할애하세요.
+
+## 접근성이 중요한 이유
+
+- **더 나은 사용성:** 접근성은 사용자가 콘텐츠와 상호 작용하는 방식을 고려하기 때문에 앱이나 사이트의 사용성에 대해 생각하도록 장려합니다. 즉, 접근성은 장애가 있는 사용자뿐만 아니라 모든 사용자의 온라인 경험을 개선하는 경우가 많습니다.
+- **시장 범위 확장:** 전 세계 장애인 시장은 10억 명이 넘는 인구가 약 7조 달러의 소비력을 가지고 있습니다.
+   > "전 세계 인구의 고령화로 인해 장애인 시장은 규모가 크고 성장하고 있습니다. 대규모 장애인 시장을 퍼플 파운드라고 부르는 영국에서는 장애인과 그 가족이 매년 최소 2,490억 파운드를 지출하고 있습니다. 미국에서는 장애인의 연간 재량 지출이 2,000억 달러가 넘습니다. 전 세계 장애 시장의 규모는 약 7조 달러에 달합니다."<br>*출처: [W3C](https://www.w3.org/WAI/business-case/)*
+- **법적 리스크를 최소화하세요:** 많은 국가에서 디지털 접근성을 요구하는 법률을 시행하고 있습니다.
+
+## 고려해야 할 장애 영역
+
+*이 섹션은 [W3C에서 부분적으로 수정되었습니다. 다양한 능력과 장벽](https://www.w3.org/WAI/people-use-web/abilities-barriers/).*
+
+### 시각적
+
+시각 장애는 한쪽 또는 양쪽 눈의 경증 또는 중등도 시력 상실부터 양쪽 눈의 상당한 또는 완전한 시력 상실까지 다양합니다. 어떤 사람들은 특정 색에 대한 민감도가 감소하거나 부족하거나 밝은 색에 대한 민감도가 증가합니다.
+
+이러한 사용자가 콘텐츠와 상호 작용하려면 다음과 같은 기능이 필요합니다.
+
+- 텍스트 크기 및 이미지 확대 또는 축소
+- 글꼴, 색상 및 간격에 대한 설정 사용자 지정하기
+- 콘텐츠의 텍스트 음성 합성 듣기(즉, 화면 리더 사용)
+- 동영상에 대한 오디오 설명 듣기
+- 새로 고침 점자를 사용하여 텍스트 읽기
+
+{% alert note %}
+- 전 세계적으로 최소 22억 명의 사람들이 근거리 또는 원거리 시력 장애를 가지고 있습니다( [WHO](https://www.who.int/news-room/fact-sheets/detail/blindness-and-visual-impairment) 참조).
+- 남성 12명 중 1명, 여성 200명 중 1명은 어느 정도의 색각 결핍을 가지고 있으며, 전 세계적으로 약 3억 명으로 추산됩니다([NHS](https://www.nhs.uk/conditions/colour-vision-deficiency/) 참조).
+{% endalert %}
+
+### 청각
+
+청각 또는 청각 장애에는 한쪽 또는 양쪽 귀의 경증에서 중등도 청각 장애가 포함될 수 있습니다. 부분적인 청력 상실도 오디오 콘텐츠와 관련하여 문제가 될 수 있습니다.
+
+이러한 사용자는 콘텐츠를 이해하기 위해 다음과 같은 정보를 활용합니다:
+
+- 오디오 콘텐츠의 대본 및 캡션
+- 캡션을 표시하고 캡션의 텍스트 크기와 색상을 조정할 수 있는 옵션을 제공하는 미디어 플레이어
+- 오디오 콘텐츠의 볼륨을 중지, 일시 중지 및 조정하는 옵션(시스템 볼륨과 무관)
+- 배경 소음과 명확하게 구분되는 고품질 포그라운드 오디오
+
+{% alert note %}
+- 표준 청력 검사에 따르면 미국 12세 이상 인구 8명 중 1명(13%, 3천만 명)이 양쪽 귀에 난청이 있습니다
+- 18세 이상 미국 성인의 약 15%(3,750만 명)가 청력에 문제가 있다고 보고합니다([NIH](https://www.nidcd.nih.gov/health/statistics/quick-statistics-hearing) 참조).
+{% endalert %}
+
+### 신체적
+
+신체적 장애에는 근육 조절이나 감각의 약화 및 제한, 관절 장애, 움직임을 방해하는 통증, 사지 결손 등이 포함될 수 있습니다.
+
+이러한 사용자는 표준 키보드를 사용하지 않더라도 기능을 활성화하기 위해 키보드 지원에 의존합니다. 이러한 사용자가 콘텐츠와 상호 작용하려면 다음이 필요합니다:
+
+- 클릭 가능한 넓은 영역
+- 작업을 완료하는 데 충분한 시간
+- 현재 초점의 가시적 표시기
+- 페이지 헤더 또는 탐색 모음과 같은 콘텐츠 블록을 건너뛰는 메커니즘
+
+{% alert note %}
+미국에서는 거의 2백만 명의 사람들이 사지를 잃고 살아가고 있습니다([절단 환자 연합](https://www.amputee-coalition.org/limb-loss-resource-center/resources-filtered/resources-by-topic/limb-loss-statistics/limb-loss-statistics/#1) 참조)
+{% endalert %}
+
+### 인지
+
+인지, 학습 및 신경 장애에는 신경 다양성 및 신경 장애뿐만 아니라 반드시 신경학적 장애가 아닌 행동 및 정신 건강 장애도 포함됩니다. 신경계의 모든 부분에 영향을 미칠 수 있으며 사람들이 듣고, 움직이고, 보고, 말하고, 정보를 이해하는 능력에 영향을 줄 수 있습니다.
+
+개인의 필요에 따라 이러한 사용자는 다음을 사용합니다:
+
+- 명확하게 구조화된 콘텐츠
+- 양식, 버튼 및 기타 콘텐츠의 일관된 레이블 지정
+- 예측 가능한 링크 타겟 및 전반적인 상호 작용
+- 메뉴 및 검색창과 같은 다양한 탐색 방법
+- 깜박임, 플래시 또는 기타 산만하게 하는 콘텐츠를 끌 수 있는 설정
+- 이미지로 지원되는 더 간단한 텍스트
+
+
+{% alert note %}
+- 미국인 5명 중 1명은 학습 및 주의력 장애가 있습니다( [LDA](https://ldaamerica.org/lda_today/the-state-of-learning-disabilities-today/#:~:text=LD%20Today,have%20learning%20and%20attention%20issues.) 참조).
+- 전 세계 인구의 약 10~20%가 신경 발산적 성향으로 간주됩니다([Deloitte](https://www2.deloitte.com/us/en/insights/topics/talent/neurodiversity-in-the-workplace.html) 참조)
+- 전 세계 어린이 100명 중 약 1명이 자폐증을 앓고 있습니다( [WHO](https://www.who.int/news-room/fact-sheets/detail/autism-spectrum-disorders) 참조).
+{% endalert %}
+
+## 모범 사례
+
+### 콘텐츠
+
+- 콘텐츠는 브랜드에 맞게 유지하되 평이한 언어를 사용하세요. 미국 초등학교 7학년 읽기 수준으로 글을 씁니다. [헤밍웨이 앱과](https://hemingwayapp.com/) 같은 리소스를 사용하여 텍스트의 읽기 수준을 확인할 수 있습니다.
+- 콘텐츠를 논리적으로 구성하고 제목이 올바른 계층 구조를 따르도록 하세요. 제목 레벨을 건너뛰지 마세요.
+- 긴 콘텐츠의 경우 중앙에 정렬된 텍스트를 피하세요. 인지 장애나 학습 장애가 있는 사용자는 이 글을 읽기 어려울 수 있습니다. 두 줄 이상으로 래핑되는 콘텐츠는 왼쪽으로 정렬해야 합니다.
+- 디지털 기기에서 읽기 쉬운 산세리프 글꼴을 사용합니다.
+- 항상 기기에 [테스트 메시지를 보내]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/sending_test_push_notifications/) 사본을 테스트하여 텍스트가 잘리지 않는지 확인하세요. 메시지가 끊어지면 콘텐츠가 사용자에게 전달되지 못하기 때문에 운영자와 사용자 모두에게 피해를 줍니다.
+
+### 링크
+
+사용자를 외부 페이지로 안내하는 등 탐색에 링크를 사용합니다.
+
+{% alert tip %}
+버튼처럼 보이고 버튼처럼 작동하는 것을 원한다면 링크를 버튼처럼 스타일링하지 말고 항상 실제 버튼을 사용하세요. 일반 사용자에게는 링크와 버튼이 동일하게 느껴질 수 있지만(마우스로 링크나 버튼을 가리키고 마우스로 클릭할 수 있음), 버튼과 링크는 제어 방식이 다르기 때문에(예를 들어 버튼은 <kbd>스페이스키나</kbd> <kbd>엔터</kbd> 키를 눌러 활성화할 수 있지만 링크는 <kbd>엔터</kbd> 키로만 활성화 가능) 링크를 버튼처럼 스타일링하면 혼란을 초래할 수 있습니다.
+{% endalert %}
+
+링크가 사용자를 어디로 이동시킬지 명확하게 설명하는 링크 텍스트를 작성합니다. 화면 리더 사용자는 콘텐츠를 훑어보기 위해 링크에서 링크로 건너뛰는 경우가 많으므로 링크 텍스트가 독립적으로 서 있을 수 있는지 확인하세요. '여기를 클릭하세요', '자세히 보기', '자세히 보기'와 같은 문구는 문맥에서 읽으면 모호하므로 피하세요.
+
+예를 들어 일기 예보를 볼 수 있는 링크를 작성하는 방법을 생각해 보세요.
+
+| 나쁨  | 나음 | 최고 |
+| --- | --- | --- | 
+| 여기를 클릭하세요 | 오늘의 날씨를 확인하려면 여기를 클릭하세요. | 오늘의 날씨 |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+모든 콘텐츠와 마찬가지로 추가 단어를 최대한 줄이고 간결하게 작성하세요.
+
+### 버튼
+
+양식 전송이나 캐러셀 재생과 같은 클릭 가능한 작업에는 버튼을 사용합니다.
+
+링크 텍스트와 마찬가지로 사용자가 버튼을 누를 때 수행되는 작업을 명확하게 설명하는 버튼 텍스트를 작성합니다(예: "자세히 보기"가 아닌 "전체 스토리 읽기"). 버튼 텍스트가 너무 길지 않은지 테스트합니다. 버튼이 모든 텍스트를 표시할 수 없는 경우 텍스트가 새 줄로 줄 바꿈되는 대신 줄임표로 잘립니다.
+
+### 이미지
+
+일부 사용자는 마케팅 콘텐츠의 이미지를 볼 수 없습니다. 접근성을 고려하지 않으면 이미지가 모든 사용자에게 동일한 콘텐츠를 제공하지 못하는 장벽이 될 수 있습니다.
+
+#### 대체 텍스트
+
+대체 텍스트는 화면 리더 및 기타 보조 기술이 사용자에게 제공하는 이미지의 콘텐츠에 대한 짧은 설명입니다.
+
+- 모든 이미지에 대해 이미지의 정보나 기능을 제공하는 대체 텍스트를 작성합니다.
+- 이미지가 [장식용](https://www.w3.org/WAI/tutorials/images/decorative/) (콘텐츠에 추가되지 않음)인 경우 빈 alt 속성(`alt=""`)을 사용합니다.
+- 대체 텍스트에 '사진' 또는 '이미지'라는 단어를 사용하지 마세요.
+
+#### 텍스트 이미지
+
+화면 리더는 이미지 안에 포함된 텍스트를 읽을 수 없으므로 텍스트 이미지를 사용하지 마세요. 텍스트 이미지도 크기가 잘 조정되지 않으며 사용자의 요구와 선호도에 맞게 커스텀할 수 없습니다. 실제 텍스트를 사용하면 색상과 대비 등을 사용자 지정하고 품질 저하 없이 텍스트 크기를 조정할 수 있습니다. 텍스트 이미지가 확대되면 픽셀화되고 품질이 낮아져 읽기 어려워집니다.
+
+### 동영상
+
+동영상에 자막을 제공합니다. 시각 장애가 있는 사람, 시끄러운 곳에서 시청하는 사람, 동영상에 나오는 언어와 다른 언어를 사용하는 사람에게 도움이 됩니다.
+
+### 색상 대비
+
+색상 대비가 충분하면 접근성을 높이는 데 큰 도움이 될 수 있습니다. 포그라운드(텍스트)와 배경색 간의 대비 비율은 [WCAG 2.1 AA 수준 요구 사항](https://www.w3.org/TR/WCAG/#contrast-minimum)을 준수해야 합니다.
+
+- 일반 텍스트(본문 텍스트, 버튼, 링크)의 명암비는 4.5:1입니다.
+- 큰 텍스트(헤더 등)의 대비 비율 3:1
+
+[WebAim 대비 검사 도구](https://webaim.org/resources/contrastchecker/)를 사용하여 텍스트가 배경색에 대해 가독성이 있는지 확인할 수 있습니다.
+
+### 양식
+
+**더 긴 양식을 더 작은 섹션으로 분할** <br>인지 부하를 줄이려면 긴 양식을 작은 섹션으로 나누세요. 이를 청킹이라고 하며, 정보를 더 쉽게 소비할 수 있도록 점진적으로 공개하는 패턴입니다. 이는 모든 사용자에게 도움이 되지만 특히 인지 장애가 있는 사용자에게 유용합니다.
+
+**툴팁이나 기타 마우스오버 상태에서 중요한 콘텐츠를 숨기지 마세요.** <br>호버 상태에 포함된 콘텐츠는 검색성과 모바일 친화성이 떨어지며 화면 확대기 사용자는 호버 상태에서만 사용할 수 있는 콘텐츠를 보는 데 어려움을 겪을 수 있습니다.
+
+**필드에서 유효하지 않은 문자 차단 방지** <br>양식 필드에 특정 문자 유형을 입력하지 못하도록 막지 마세요. 사용자가 원하는 내용을 입력할 수 있도록 허용한 다음 무엇이 잘못되었는지에 대한 오류 메시지를 제공하는 것이 좋습니다. 보조 기술 사용자는 양식을 올바르게 작성했는지 확인하기 위해 인라인 유효성 검사에 크게 의존하기 때문에 키보드 입력을 차단하는 것은 특히 문제가 될 수 있습니다.
+
+**명확한 오류 메시지 작성** <br>좋은 오류 메시지는 무슨 일이 일어났는지, 무엇이 잘못되었는지, 어떻게 해결할 수 있는지 등 세 부분으로 구성됩니다. 오류 메시지는 명확하고 이해하기 쉬워야 합니다. 간단한 언어로 말하세요. 화려한 전문 용어는 필요 없습니다.
+<br>
+
+### 사용자 지정 HTML
+
+메시징에 사용자 지정 HTML을 사용하는 경우:
+
+- [시맨틱 HTML](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML)을 사용합니다. 즉, 한 요소를 다른 요소처럼 보이도록 스타일을 지정하는 대신 의도한 목적에 맞는 올바른 HTML 요소를 사용해야 합니다. 대부분의 HTML 요소에는 자체 접근성 지원이 내장되어 있습니다.
+- HTML 내에서 언어 속성을 설정하여 콘텐츠의 언어를 식별합니다. 화면 리더는 해당 언어의 발음과 특성에 따라 각 언어마다 다른 사운드 라이브러리를 사용합니다. 언어를 지정하면 화면 리더는 필요에 따라 언어 라이브러리 간에 자동으로 전환할 수 있습니다. 예를 들어, 다음과 같습니다.
+
+{% raw %}
+```html
+<html lang="en-us">
+```
+{% endraw %}
+
diff --git a/_lang/ko/_help/faqs.md b/_lang/ko/_help/faqs.md
new file mode 100644
index 00000000000..43f89597e3a
--- /dev/null
+++ b/_lang/ko/_help/faqs.md
@@ -0,0 +1,85 @@
+---
+nav_title: 모범 사례 및 FAQ
+article_title: 자주 묻는 질문
+page_order: 3
+hide_toc: true
+layout: dev_guide
+guide_top_header: "모범 사례 및 자주 묻는 질문"
+guide_top_text: "이 랜딩 페이지에서는 Braze 대시보드 및 기능에 대해 자주 묻는 질문과 모범 사례에 대한 게시물을 확인할 수 있습니다."
+
+guide_featured_title: "FAQ 문서"
+guide_featured_list:
+  - name: 캔버스 FAQ
+    link: /docs/user_guide/engagement_tools/canvas/faqs/
+    image: /assets/img/braze_icons/brush-02.svg
+  - name: 캠페인 FAQ
+    link: /docs/user_guide/engagement_tools/campaigns/faq/
+    image: /assets/img/braze_icons/send-01.svg
+  - name: "이메일 및 링크 템플릿 FAQ"
+    link: /docs/user_guide/message_building_by_channel/email/templates/faq/
+    image: /assets/img/braze_icons/link-03.svg
+  - name: "내보내기 FAQ"
+    link: /docs/user_guide/data_and_analytics/export_braze_data/faqs/
+    image: /assets/img/braze_icons/file-download-01.svg
+  - name: "인앱 메시지 FAQ"
+    link: /docs/user_guide/message_building_by_channel/in-app_messages/faq/
+    image: /assets/img/braze_icons/channel-in-app-messages.svg
+  - name: "위치 및 지오펜스 FAQ"
+    link: /docs/user_guide/engagement_tools/locations_and_geofences/faqs/
+    image: /assets/img/braze_icons/marker-pin-01.svg
+  - name: "미디어 라이브러리 FAQ"
+    link: /docs/user_guide/engagement_tools/templates_and_media/faqs/
+    image: /assets/img/braze_icons/image-01.svg
+  - name: "MMS FAQ"
+    link: /docs/user_guide/message_building_by_channel/sms/mms/faqs/
+    image: /assets/img/braze_icons/message-circle-01.svg
+  - name: "SMS FAQ"
+    link: /docs/user_guide/message_building_by_channel/sms/faqs/
+    image: /assets/img/braze_icons/message-text-circle-01.svg
+  - name: "WhatsApp FAQ"
+    link: /docs/user_guide/message_building_by_channel/whatsapp/faqs/
+    image: /assets/img/braze_icons/whatsapp.svg
+  - name: "인텔리전스 FAQ"
+    link: /docs/user_guide/intelligence/faqs/
+    image: /assets/img/braze_icons/lightbulb-05.svg
+  - name: "이메일 드래그 앤 드롭 편집기 FAQ"
+    link: /docs/user_guide/message_building_by_channel/email/drag_and_drop/faq/
+    image: /assets/img/braze_icons/channel-email.svg
+  - name: "API 및 CSV 내보내기 FAQ"
+    link: /docs/user_guide/data_and_analytics/export_braze_data/faqs/
+    image: /assets/img/braze_icons/file-download-01.svg
+  - name: "기능 플래그 FAQ"
+    link: /docs/developer_guide/platform_wide/feature_flags/faq/
+    image: /assets/img/braze_icons/flag-01.svg
+  - name: "라이브 활동 FAQ"
+    link: /docs/developer_guide/platform_integration_guides/swift/live_activities/faq/
+    image: /assets/img/braze_icons/swift.svg
+  - name: "Liquid FAQ"
+    link: /docs/user_guide/personalization_and_dynamic_content/liquid/faq/
+    image: /assets/img/braze_icons/beaker-02.svg
+
+
+guide_menu_title: "Best practices"
+guide_menu_list:
+  - name: "콘텐츠 카드 모범 사례"
+    link: /docs/user_guide/message_building_by_channel/content_cards/best_practices/
+    image: /assets/img/braze_icons/sticker-square.svg
+  - name: "이메일 모범 사례"
+    link: /docs/user_guide/message_building_by_channel/email/best_practices/
+    image: /assets/img/braze_icons/mail-01.svg
+  - name: "인앱 메시지 모범 사례"
+    link: /docs/user_guide/message_building_by_channel/in-app_messages/best_practices/
+    image: /assets/img/braze_icons/phone-02.svg
+  - name: "푸시 모범 사례"
+    link: /docs/user_guide/message_building_by_channel/push/best_practices/
+    image: /assets/img/braze_icons/message-square-02.svg
+  - name: "SMS 모범 사례"
+    link: /docs/user_guide/message_building_by_channel/sms/best_practices/
+    image: /assets/img/braze_icons/message-text-circle-01.svg
+
+
+local_redirect: #what-does-local-time-zone-delivery-offer
+  what-does-local-time-zone-delivery-offer: '/docs/user_guide/engagement_tools/campaigns/faq/#what-does-local-time-zone-delivery-offer'
+---
+
+<br>
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles.md b/_lang/ko/_help/help_articles.md
new file mode 100644
index 00000000000..2a8774300d5
--- /dev/null
+++ b/_lang/ko/_help/help_articles.md
@@ -0,0 +1,45 @@
+---
+nav_title: 도움말
+article_title: 도움말
+page_order: 1
+layout: dev_guide
+guide_top_header: "도움말"
+guide_top_text: "문제를 해결하고 캠페인의 종속성을 파악하는 데 도움이 되는 도움말 문서가 많이 있습니다. 새 도움말 문서에 대한 제안이 있으면 이 도움말 문서나 다른 도움말 문서 페이지 하단에 피드백을 남겨 주세요. 또는 <a href='https://www.braze.com/docs/contributing/home'>Braze 기여자 가이드로</a> 이동하여 직접 글을 작성하는 방법을 배울 수 있습니다. <br> <br>다음 인기 주제 중에서 선택하거나 탐색 패널에 나열된 다른 문서를 참조하세요."
+
+page_type: landing
+description: "이 랜딩 페이지에는 Braze 사용 시 문제를 해결하고 종속성을 파악하는 데 도움이 되는 도움말 문서가 있습니다."
+
+guide_featured_title: "주제"
+guide_featured_list:
+  - name: 계정
+    link: /docs/help/help_articles/account/
+    image: /assets/img/braze_icons/user-circle.svg
+  - name: API
+    link: /docs/help/help_articles/api/
+    image: /assets/img/braze_icons/terminal-square.svg
+  - name: 캠페인 및 캔버스
+    link: /docs/help/help_articles/campaigns_and_canvas/
+    image: /assets/img/braze_icons/annotation.svg
+  - name: 콘텐츠 카드
+    link: /docs/help/help_articles/content_cards/
+    image: /assets/img/braze_icons/sticker-square.svg
+  - name: 데이터
+    link: /docs/help/help_articles/data/
+    image: /assets/img/braze_icons/line-chart-up-01.svg
+  - name: 기술문서
+    link: /docs/help/help_articles/docs/
+    image: /assets/img/braze_icons/file-06.svg
+  - name: 이메일
+    link: /docs/help/help_articles/email/
+    image: /assets/img/braze_icons/mail-01.svg
+  - name: 인앱 메시지
+    link: /docs/help/help_articles/in-app_messages/
+    image: /assets/img/braze_icons/phone-02.svg
+  - name: 푸시
+    link: /docs/help/help_articles/push/
+    image: /assets/img/braze_icons/message-square-02.svg
+  - name: 세그먼트
+    link: /docs/help/help_articles/segments/
+    image: /assets/img/braze_icons/users-01.svg
+---
+
diff --git a/_lang/ko/_help/help_articles/account.md b/_lang/ko/_help/help_articles/account.md
new file mode 100644
index 00000000000..1b6b6e9b36e
--- /dev/null
+++ b/_lang/ko/_help/help_articles/account.md
@@ -0,0 +1,18 @@
+---
+nav_title: 계정
+page_order: 1
+layout: dev_guide
+guide_top_header: "계정 도움말 문서"
+guide_top_text: "사용자 권한을 명확히 설명하는 다음 도움말 문서를 확인하세요. <br><br> Braze 계정 및 대시보드 관리에 대한 자세한 정보를 찾고 계신가요? <a href='/docs/user_guide/administrative/'>관리</a> 섹션에서 저희의 글을 읽어보세요!"
+
+page_type: landing
+description: "이 랜딩 페이지는 Braze 계정과 관련된 도움말 문서가 있는 곳입니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 계정 잠김
+    link: /docs/help/help_articles/account/locked_out/
+    image: /assets/img/braze_icons/lock-01.svg
+
+noindex: true
+---
diff --git a/_lang/ko/_help/help_articles/account/locked_out.md b/_lang/ko/_help/help_articles/account/locked_out.md
new file mode 100644
index 00000000000..1dcc070d431
--- /dev/null
+++ b/_lang/ko/_help/help_articles/account/locked_out.md
@@ -0,0 +1,47 @@
+---
+nav_title: 계정 잠김
+article_title: 계정 잠김
+page_order: 0
+
+page_type: solution
+description: "이 도움말 설명서에서는 Braze 계정이 잠긴 경우 문제 해결 단계를 안내합니다."
+tool: Dashboard
+---
+
+# 계정 잠김
+
+Braze 계정이 잠겼더라도 걱정하지 마세요! 다시 참여할 수 있도록 도와드리겠습니다.	
+
+어떤 종류의 잠금이 발생했는지는 오류 메시지로 확인할 수 있습니다.	
+
+- [비밀번호 관련 오류가 표시됩니다.](#password-error)	
+- [오류는 표시되지 않지만 여전히 Braze가 나를 허용하지 않습니다.](#instance-error)	
+- [계정 일시 정지에 대한 오류가 표시됩니다.](#account-suspension)	
+
+## 비밀번호 오류
+
+계정 보안은 당사에 매우 중요하므로 Braze 계정에 로그인하려면 비밀번호가 필요합니다.	
+- 올바른 [Braze 대시보드 인스턴스에][1] 로그인하고 있는지 확인합니다. 계정 관리자 또는 Braze 계정 관리자에게 문의하여 확인하세요.	
+- 비밀번호가 만료되었을 수 있으므로 비밀번호를 [재설정해야][2] 합니다.	
+- [통합][3] 인증 서비스를 사용하는 경우 계정 관리자에게 설정이 제대로 완료되었는지 확인하세요.	
+- 회사에서 여러 개의 Braze 인스턴스를 사용 중인 경우 잘못된 이메일을 사용하여 로그인하고 있을 수 있습니다.  	
+
+확실하지 않은 경우 언제든지 [비밀번호를 재설정할][2] 수 있습니다.	
+
+## 인스턴스 오류
+
+평소 로그인할 때 사용하는 것과 동일한 기기를 사용하는 경우, Braze는 자동으로 올바른 인스턴스를 감지합니다. 그러나 그렇지 않거나 처음 로그인하는 경우 다음 사항을 고려하는 것이 좋습니다:	
+
+- 올바른 [Braze 대시보드 인스턴스에][1] 로그인하고 있는지 확인합니다. 계정 관리자 또는 Braze 계정 관리자에게 문의하여 확인하세요.
+- 회사에서 여러 개의 Braze 인스턴스를 사용 중인 경우 잘못된 이메일을 사용하여 로그인하고 있을 수 있습니다.	
+
+## 계정 일시 정지	
+
+이런 일이 자주 발생하지는 않지만 일시 정지 및 삭제는 매우 심각하게 고려하고 있습니다. 이 오류를 발견한 경우, 가장 좋은 방법은 회사의 Braze 관리자, Braze 계정 관리자 또는 [Braze 지원팀에][support] 문의하는 것입니다.
+
+_마지막 업데이트: 2019년 10월 19일_
+
+[support]: {{site.baseurl}}/support_contact/	
+[1]: {{site.baseurl}}/user_guide/administrative/access_braze/braze_instances/#braze-instances
+[2]: {{site.baseurl}}/user_guide/administrative/access_braze/accessing_your_account/#resetting-your-password
+[3]: {{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/
diff --git a/_lang/ko/_help/help_articles/api.md b/_lang/ko/_help/help_articles/api.md
new file mode 100644
index 00000000000..e9614dba230
--- /dev/null
+++ b/_lang/ko/_help/help_articles/api.md
@@ -0,0 +1,23 @@
+---
+page_order: 1.1
+nav_title: API
+layout: dev_guide
+guide_top_header: "API 도움말 문서"
+guide_top_text: "API가 사용자 데이터 영역에 어떤 영향을 미칠 수 있는지에 대한 설명은 다음 문서를 참조하세요. <br><br> <a href='/docs/api/basics/'>API</a> 섹션에서 Braze REST API에 대해 자세히 알아보세요!"
+
+page_type: landing
+description: "이 랜딩 페이지는 Braze API와 관련된 도움말 문서가 있는 곳입니다."
+guide_menu_title: ""
+guide_menu_list:
+  - name: API를 통해 사용자 삭제하기
+    link: /docs/help/help_articles/api/delete_user/
+    image: /assets/img/braze_icons/user-minus-01.svg
+  - name: 캠페인과 캔버스 속성의 소스 간 차이점
+    link: /docs/help/help_articles/api/attribute_name_id_across_sources/
+    image: /assets/img/braze_icons/info-circle.svg
+
+noindex: true
+---
+
+
+
diff --git a/_lang/ko/_help/help_articles/api/attribute_name_id_across_sources.md b/_lang/ko/_help/help_articles/api/attribute_name_id_across_sources.md
new file mode 100644
index 00000000000..9bf475679fd
--- /dev/null
+++ b/_lang/ko/_help/help_articles/api/attribute_name_id_across_sources.md
@@ -0,0 +1,51 @@
+---
+nav_title: 캠페인과 캔버스 속성의 소스 간 차이점
+article_title: Braze에서 캠페인과 캔버스 속성이 소스 간에 어떻게 다른가요? 
+page_order: 1
+
+page_type: reference
+description: "이 도움말 문서에서는 Braze의 여러 소스에서 캠페인과 캔버스 속성 이름 및 ID를 비교합니다."
+platform: API
+---
+
+# Braze에서 캠페인과 캔버스 속성이 소스 간에 어떻게 다른가요?
+
+캠페인, 캔버스, 캔버스 단계 이름과 ID는 모두 Liquid, REST API, 커런츠에서 사용할 수 있습니다. 이러한 속성은 세 소스 모두에서 동일한 값에 매핑되지만 이름은 다르게 지정될 수 있습니다. 이 페이지는 이 세 가지를 연결하는 데 도움을 주기 위한 페이지입니다.
+
+## 사용 사례
+
+### Liquid
+
+캠페인 및 캔버스 속성은 Braze =Liquid 태그 대시보드 {% raw %}(예: `{{campaign.${api_id}}}`)에서 리퀴드 태그로 사용할 수 있습니다. Liquid를 사용하여 이러한 속성을 메시지 자체, 연결된 콘텐츠 호출 또는 키-값 페어로 전달할 수 있습니다. 이는 일반적으로 추적 목적으로 수행됩니다.
+
+### REST API
+
+캠페인 및 캔버스 속성은 [캠페인 세부 정보 내보내기 엔드포인트]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/) 또는 [캔버스 세부 정보 내보내기 엔드포인트에서도]({{site.baseurl}}/api/endpoints/export/canvas/get_canvas_details/) 사용할 수 있습니다. REST API를 사용하여 매핑, 즉 모든 캔버스 이름과 해당 ID의 목록을 작성할 수 있습니다.
+
+### 커런츠
+
+캠페인 및 캔버스 속성은 커런츠의 [메시지 인게이지먼트 이벤트]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events) 연결됩니다. 이는 푸시 전송 또는 이메일 열기가 어떤 캠페인 또는 캔버스 구성 요소와 연결되어 있는지 확인할 수 있도록 하는 중요한 정보입니다.
+
+## 캠페인 속성
+
+| 속성 | Liquid | REST API | 커런츠 |
+| --- | --- | --- | --- |
+| 캠페인 이름 | {% raw %}`{{campaign.${name}}}`{% endraw %} | `name` | `campaign_name` |
+| 캠페인 ID | {% raw %}`{{campaign.${api_id}}}`{% endraw %} | N/A(API 호출 자체의 입력으로 사용됨) | campaign_id |
+| 배리언트 이름 | {% raw %}`{{campaign.${message_name}}}`{% endraw %} | `messages.message_variation_id.name` | 해당 없음(캠페인 세부 정보 내보내기 엔드포인트를 사용하여 이형 상품 이름을 이형 상품 ID에 매핑) |
+| 배리언트 상품 ID | {% raw %}`{{campaign.${message_api_id}}}`{% endraw %} | `messages.message_variation_id` | `message_variation_api_id` |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
+
+## 캔버스 속성
+
+| 속성 | Liquid | REST API | 커런츠 |
+| --- | --- | --- | --- |
+| 캔버스 이름 | {% raw %}`{{canvas.${name}}}`{% endraw %} | `name` | `canvas_name` |
+| 캔버스 ID | {% raw %}`{{canvas.${api_id}}}`{% endraw %} | N/A(API 호출 자체의 입력으로 사용됨) | canvas_id |
+| 배리언트 이름 | {% raw %}`{{canvas.${variant_name}}}`{% endraw %} | `variants.name` | `canvas_variation_name` |
+| 배리언트 상품 ID | {% raw %}`{{canvas.${variant_api_id}}}`{% endraw %} | `variants.name.id` | `canvas_variation_id` |
+| 단계 이름 | {% raw %}`{{campaign.${name}}}`{% endraw %} | `steps.name` | `canvas_step_name` |
+| 단계 ID | {% raw %}`{{campaign.${api_id}}}`{% endraw %} | `steps.id` | `canvas_step_id` |
+| 메시지 채널 | N/A | `steps.messages.message_variation_id.channel` | 해당 없음(푸시 전송 또는 이메일 열기와 같은 이벤트 유형에서 내재됨) |
+| 메시지 ID | {% raw %}`{{campaign.${message_api_id}}}`{% endraw %} | `steps.message.message_variation_id` | `canvas_step_message_variation_api_id` |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4}
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/api/delete_user.md b/_lang/ko/_help/help_articles/api/delete_user.md
new file mode 100644
index 00000000000..ac4df545841
--- /dev/null
+++ b/_lang/ko/_help/help_articles/api/delete_user.md
@@ -0,0 +1,42 @@
+---
+nav_title: API를 통해 사용자 제거하기
+article_title: API를 통해 사용자 제거하기
+page_order: 0
+
+page_type: reference
+description: "이 도움말 문서에서는 Braze REST API를 통해 고객 프로필을 제거할 때의 의미를 설명합니다."
+tool: Dashboard
+platform: API
+---
+
+# API를 통해 사용자 제거하기
+
+[Braze REST API를 통해 사용자를 제거하면][1] 다음 데이터가 삭제(무효화)됩니다.
+- 사용자가 보유한 모든 속성
+- 이메일 주소
+- 전화번호
+- 외부 사용자 ID 
+- 성별
+- 국가
+- 언어
+
+[Braze REST API를 통해 사용자를 제거하면][1] 다음 이벤트가 발생합니다:
+- 사용자 프로필은 익명으로 처리됩니다.
+- [평생 사용자][2] 수는 새로 익명화된 사용자를 고려하여 업데이트됩니다.	
+- 익명화된 사용자도 여전히 집계된 전환율에 포함됩니다. 익명화된 사용자의 경우 사용자 지정 이벤트 횟수 및 구매 횟수가 업데이트되지 않습니다.
+
+## 공유 이메일 주소가 있는 여러 프로필
+
+동일한 이메일 주소를 공유하는 여러 사용자 프로필을 병합하고 싶다고 가정해 보겠습니다. 
+
+이러한 사용자 프로필을 병합하려면 다음과 같이 하세요:
+
+ 1. 이메일 주소가 중복된 사용자를 식별합니다. 
+ 2. 단일 프로필의 모든 속성을 내보냅니다. 
+ 3. API 또는 CSV를 통해 이러한 속성을 사용자 프로필로 가져옵니다. 
+ 4. API를 통해 사용자를 제거하면 기본적으로 위에서 설명한 중복 사용자 및 데이터를 삭제할 수 있습니다.
+
+_마지막 업데이트 2023년 9월 13일_
+
+[1]: {{site.baseurl}}/api/endpoints/user_data/#user-delete-endpoint/
+[2]: {{site.baseurl}}/user_guide/data_and_analytics/analytics/understanding_your_app_usage_data/#lifetime-users
diff --git a/_lang/ko/_help/help_articles/campaigns_and_canvas.md b/_lang/ko/_help/help_articles/campaigns_and_canvas.md
new file mode 100644
index 00000000000..b1407e3ac5b
--- /dev/null
+++ b/_lang/ko/_help/help_articles/campaigns_and_canvas.md
@@ -0,0 +1,43 @@
+---
+page_order: 2
+nav_title: 캠페인 &amp; 캔버스
+layout: dev_guide
+guide_top_header: "캠페인 및 캔버스 도움말 문서"
+guide_top_text: "도움이 되는 정보를 찾고 있습니까? 잘 찾아 오셨습니다! 캔버스와 캠페인의 문제 해결에 유용한 도움말 문서를 확인하세요. <br><br> 사용자와의 참여를 구축하고 최적화하는 방법에 대한 자세한 내용은 <a href='/docs/user_guide/engagement_tools/campaigns/'>캠페인</a> 및 <a href='/docs/user_guide/engagement_tools/canvas/'>캔버스</a>의 기사를 확인하세요!"
+
+page_type: landing
+description: "이 랜딩 페이지는 캠페인 또는 캔버스와 관련된 일반적인 문제에 대한 도움말 기사가 있는 곳입니다."
+tool:
+- Campaigns
+- Canvas
+noindex: true
+guide_menu_title: ""
+guide_menu_list:
+  - name: 캔버스 전달 문제
+    link: /docs/help/help_articles/campaigns_and_canvas/canvas_not_sending/
+    image: /assets/img/braze_icons/send-01.svg
+  - name: 위치 데이터 확인
+    link: /docs/help/help_articles/campaigns_and_canvas/locations_data_in_campaigns/
+    image: /assets/img/braze_icons/navigation-pointer-01.svg
+  - name: 대형 대조군 다루기
+    link: /docs/help/help_articles/campaigns_and_canvas/more_people_in_control_group/
+    image: /assets/img/braze_icons/target-05.svg
+  - name: 커스텀 이벤트 속성 로깅
+    link: /docs/help/help_articles/campaigns_and_canvas/using_custom_event_properties/
+    image: /assets/img/braze_icons/code-02.svg
+  - name: 낮은 캠페인 또는 캔버스 전환
+    link: /docs/help/help_articles/campaigns_and_canvas/conversions_low/
+    image: /assets/img/braze_icons/shopping-cart-03.svg
+  - name: 트리거되지 않은 캠페인 또는 캔버스
+    link: /docs/help/help_articles/campaigns_and_canvas/not_triggering/
+    image: /assets/img/braze_icons/x-circle.svg
+  - name: 이벤트 로깅 사용
+    link: /docs/help/help_articles/campaigns_and_canvas/using_event_logging/
+    image: /assets/img/braze_icons/list.svg
+
+    
+---
+
+{% alert tip %}
+캠페인 문제 해결에 대한 추가 지원이 필요한 경우, 최근 30일간의 진단 로그만 보유하고 있으므로 문제 발생 후 30일 이내에 Braze 지원팀에 문의하시기 바랍니다.
+{% endalert %}
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/campaigns_and_canvas/canvas_not_sending.md b/_lang/ko/_help/help_articles/campaigns_and_canvas/canvas_not_sending.md
new file mode 100644
index 00000000000..72563b9686f
--- /dev/null
+++ b/_lang/ko/_help/help_articles/campaigns_and_canvas/canvas_not_sending.md
@@ -0,0 +1,40 @@
+---
+nav_title: 캔버스 배달 문제
+article_title: 캔버스 배달 문제
+page_order: 0
+page_type: solution
+description: "이 도움말 문서에서는 캔버스의 전달 문제 해결 방법을 안내합니다."
+tool: Canvas
+---
+
+# 캔버스 배달 문제
+
+캔버스는 견고하고 복잡하며, 캔버스를 만들 때 많은 시간과 정성을 쏟는다는 것을 잘 알고 있습니다. 따라서 캔버스가 원하는 방식으로 전송되지 않는다면 캔버스 일정, 항목 오디언스 및 항목 설정을 확인하고 [캔버스 생성]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/) 단계를 검토하는 것이 좋습니다.
+
+## 스케줄
+
+- 캔버스가 [올바르게 예약되어]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#scheduled-delivery) 있나요?
+- 정확한 날짜와 시간을 선택하셨나요?
+- [실행 기반 전달]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#action-based-delivery)의 경우, 캔버스를 시작한 이후 사용자가 지정된 액션을 수행했나요?
+
+## 항목 설정
+
+[항목 설정]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-2-set-up-your-canvas)은 캔버스가 전송되는 방식을 이해하는 데 중요합니다. 캔버스에 입장할 수 있는 사람의 수를 제한했는지 확인합니다.
+
+사용자는 더 이상 메시지를 받을 자격이 없는 경우 캔버스를 종료할 수도 있습니다. 예를 들어 캔버스에 푸시 알림만 포함되어 있고 사용자가 첫 번째 단계를 수신한 후 푸시 수신을 거부하면 해당 사용자는 캔버스에서 탈퇴하게 됩니다. [다른 캔버스 단계를]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components) 사용하여 대체 사용자 여정을 추가하는 것을 고려하세요.
+
+## 오디언스 세분화
+
+타겟 고객을 위해 다음 질문을 고려하세요:
+
+- 올바른 세그먼트를 선택하셨나요?
+- 세그먼트는 어떻게 설정되나요?
+- 세그먼트에 사용자가 포함되어 있는지 확인하셨나요?
+- 캔버스에 입장하는 사용자 수를 제한하는 추가 필터를 추가했나요?
+- 사용자가 이형 상품의 첫 번째 단계를 받을 수 있는 자격이 있나요? 예를 들어 캔버스의 첫 번째 단계가 푸시 알림이지만 입력 오디언스가 모두 푸시를 사용하도록 설정되어 있으면 메시지를 수신하는 사용자가 없습니다.
+
+{% alert tip %}
+캔버스 문제 해결에 대한 추가 지원이 필요하시면 문제 발생 후 30일 이내에 Braze 지원팀에 문의하세요. 진단 로그는 최근 30일 동안만 보관됩니다.
+{% endalert %}
+
+_마지막 업데이트 2024년 6월 25일_
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/campaigns_and_canvas/conversions_low.md b/_lang/ko/_help/help_articles/campaigns_and_canvas/conversions_low.md
new file mode 100644
index 00000000000..f053122bb5e
--- /dev/null
+++ b/_lang/ko/_help/help_articles/campaigns_and_canvas/conversions_low.md
@@ -0,0 +1,41 @@
+---
+nav_title: 낮은 캠페인 또는 캔버스 전환율
+article_title: 낮은 캠페인 또는 캔버스 전환율
+page_order: 4
+
+page_type: solution
+description: "이 도움말 문서에서는 예상보다 낮은 전환율을 보이는 캠페인 또는 캔버스의 문제 해결 방법을 안내합니다."
+tool:
+- Canvas
+- Campaigns
+---
+
+# 낮은 캠페인 또는 캔버스 전환율
+
+전환은 사용자가 캠페인을 생성하는 동안 정의한 메시지 내에서 액션을 수행할 때 발생합니다.
+
+이전 캠페인이나 기대치와 비교했을 때 전환율이 기대만큼 높지 않을 수 있습니다. 전환은 까다로운 비즈니스이지만, 이벤트 추적과 전환 마감일이라는 플랫폼의 몇 가지 간단한 기능에 따라 달라집니다.
+
+그 이유를 빠르게 해결하려면 이벤트 추적 및 전환 기한을 확인하는 것이 좋습니다.
+
+## 이벤트 추적
+
+캠페인이 세션 시작 또는 커스텀 이벤트를 트리거하는 경우, 이 이벤트 또는 세션이 메시지를 트리거할 만큼 충분히 자주 발생하고 있는지 확인해야 합니다. 이 데이터는 [개요][1] (세션 데이터의 경우) 또는 [사용자 지정 이벤트][2] 페이지에서 확인할 수 있습니다:
+
+![사용자 지정 이벤트 수에 대한 통계가 포함된 사용자 지정 이벤트 페이지입니다.][43]
+
+## 전환 마감일
+
+캠페인별로 선택한 각 전환 이벤트에 대해 \[마감일][44]]을 설정합니다. 즉, 전환이 각 캠페인에 포함되기 위해 전환이 발생해야 하는 시간 제한을 설정할 수 있습니다.
+
+캠페인 측정기준을 이해하기 위해 \[전환 계산하기][45]에 대한 정보를 검토했는지 확인하세요. 캔버스에서 사용자 전환에 대해서는 [캔버스 FAQ]({{site.baseurl}}/user_guide/engagement_tools/canvas/faqs/#how-are-user-conversions-tracked-in-a-canvas)를 참조하세요. 
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트 5월 6일, 2021_
+
+[1]: {{site.baseurl}}/user_guide/data_and_analytics/analytics/understanding_your_app_usage_data/
+[2]: {{site.baseurl}}/user_guide/data_and_analytics/configuring_reporting/#configuring-reporting
+[43]: {% image_buster /assets/img_archive/trouble5.png %}
+[44]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/conversion_events/#step-2-add-conversion-events
+[45]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/conversion_events/#conversion-tracking-rule
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/campaigns_and_canvas/know_before_send.md b/_lang/ko/_help/help_articles/campaigns_and_canvas/know_before_send.md
new file mode 100644
index 00000000000..d392f7bf513
--- /dev/null
+++ b/_lang/ko/_help/help_articles/campaigns_and_canvas/know_before_send.md
@@ -0,0 +1,96 @@
+---
+nav_title: 보내기 전에 알아두세요
+article_title: 보내기 전에 알아두세요
+description: "사전 출시 가이드를 방문한 후, 콘텐츠 카드, 이메일, 인앱 메시지, 푸시 및 SMS에 대한 최종 확인 목록 또는 '주의 사항'을 참조하세요."
+alias: /know_before_send/
+
+---
+
+# 보내기 전에 알아두세요: 채널
+
+자신감을 가지고 캠페인과 캔버스를 시작하세요! 콘텐츠 카드, 이메일, 인앱 메시지, 푸시 및 SMS에 대한 최종 확인 또는 "주의 사항" 목록을 참조하세요.
+
+{% alert note %}
+저희는 발송 전 참조할 수 있는 방대한 자료 목록을 제공하지만, 각 채널은 저희 제품이 발전함에 따라 계속해서 성장하는 개별적인 특성을 가지고 있습니다. 아래 나열된 검사는 유용한 제안이며, 발송하기 전에 캠페인과 대량 발송을 철저히 테스트할 것을 권장합니다.
+{% endalert %}
+
+## 일반
+
+#### 확인할 사항
+- [**API 속도 제한**](https://braze.com/resources/articles/whats-rate-limiting): 워크스페이스에서 오류가 발생하지 않도록 Braze API [사용량 제한]({{site.baseurl}}/api/api_limits/)을 검토하세요. 요청을 일괄 처리하고 있는 경우 사용량 제한을 늘리고 싶다면 고객 성공 매니저에게 문의하세요. 이 과정에는 리드 타임이 필요하므로 이에 따라 계획을 세우십시오.
+- [**필요한 최대 게재빈도 설정 재정의**]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping): 일부 캠페인, 예를 들어 트랜잭션 메시지와 같은 경우, 사용자의 빈도 제한에 도달했더라도 항상 사용자에게 도달하기를 원할 것입니다(예: 전달 알림). 특정 캠페인이 최대 게재빈도 설정 규칙을 무시하도록 하려면, 해당 캠페인의 전달을 예약할 때 Braze 대시보드에서 최대 게재빈도 설정을 끔으로 설정할 수 있습니다.
+
+#### 알아야 할 사항
+- [**글로벌 컨트롤 그룹**]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group#global-control-group): 글로벌 컨트롤 그룹을 사용하는 경우, 일부 사용자는 캠페인이나 캔버스를 받지 않습니다. (제외 설정[을 사용하여 예외를 만들 수 있습니다]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/#step-3-assign-exclusion-settings)). 이 사용자 목록을 보려면 CSV 또는 [API]({{site.baseurl}}/api/endpoints/export/user_data/post_users_global_control_group/)를 통해 내보내십시오.
+- [**캔버스 사용량 제한**]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#rate-limiting): 캔버스에서 사용량 제한은 개별 단계가 아닌 전체 캔버스에 적용됩니다. 예를 들어, 여러 단계가 있는 캔버스에 분당 10,000 메시지의 사용량 제한을 설정하면 첫 번째 단계에서 제한에 도달했기 때문에 여전히 10,000 메시지로 제한됩니다.
+- **최대 게재빈도 설정**: 
+  - 최대 게재빈도 설정 규칙은 푸시, 이메일, SMS 및 웹훅에 적용되지만, 인앱 메시지 및 콘텐츠 카드에는 적용되지 않습니다.
+  - 전역 최대 게재빈도 설정은 사용자의 시간대를 기준으로 예약되며 24시간이 아닌 캘린더 일 기준으로 계산됩니다. 예를 들어, 하루에 한 개의 캠페인만 보내도록 최대 게재빈도 설정 규칙을 설정한 경우, 사용자는 현지 시간대로 오후 11시에 메시지를 받을 수 있으며 한 시간 후에 또 다른 메시지를 받을 자격이 주어집니다.
+
+{% alert tip %}
+캔버스 및 캠페인 문제 해결에 대한 추가 지원이 필요하시면 문제 발생 후 30일 이내에 Braze 지원팀에 문의하세요. 진단 로그는 최근 30일 동안만 보관됩니다.
+{% endalert %}
+
+## 이메일
+
+#### 확인할 사항
+- **고객 consent**: 초기 이메일을 보내기 전에 고객의 허락을 먼저 받는 것이 중요합니다. [동의 및 주소 수집]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/consent_and_address_collection/) 및 자세한 내용은 당사의 [Braze 허용 사용 정책](https://www.braze.com/company/legal/aup)을 참조하십시오.
+- **예상 볼륨**: 일일 200만 개의 이메일을 단일 IP로 보내는 것은 해당 볼륨이 [적절히 준비된]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/ip_warming#ip-warming) 경우 일반적인 권장 사항입니다. 
+  - 만약 이보다 더 많은 양을 지속적으로 보내려는 계획이 있다면, 제공업체가 이메일 수신을 제한하여 많은 소프트 바운스, 낮은 전달 가능성 비율, 그리고 IP 평판 저하를 초래하는 것을 피하기 위해, IP 풀에 묶인 여러 IP 주소를 사용하는 것을 고려하세요. 
+  - 짧은 시간 내에만 보내고자 한다면, 다양한 제공업체가 메일을 수락하는 속도를 조사하여 적절한 IP 수를 파악하는 것을 권장합니다. 
+
+#### 알아야 할 사항
+- **발송량 요소**: IP의 유능한 발송량을 결정하는 몇 가지 요인에는 다음이 포함됩니다.
+  - 우편함: 대형 이메일 제공업체는 단일 IP에서 하루에 수백만 건을 처리할 수 있는 반면, 소규모 지역 받은편지함 제공업체나 인프라가 작은 제공업체는 그 양을 처리하지 못할 수 있습니다.
+  - 발송자 평판: 발송자가 해당 볼륨으로 증가되고 각 받은편지함 또는 도메인에서 발송자 평판이 충분히 강한 경우 단일 IP에서 하루에 더 많은 양을 보낼 수 있습니다.
+- **모범 사례**: Braze [이메일 모범 사례]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices)를 검토하고 전달 가능성 서비스에 대해 더 알고 싶다면 Braze 계정 팀에 문의하세요.
+
+## 푸시
+
+#### 확인할 사항
+- [**옵트인/구독 및 푸시 사용**]({{site.baseurl}}/user_guide/message_building_by_channel/push/users_and_subscriptions/): 사용자가 Braze로부터 푸시 메시지를 받으려면 구독 상태가 옵트인(iOS) 또는 구독(Android) 및 `Push Enabled = True`여야 합니다. Android 13은 푸시 알림을 보내는 앱을 관리하는 방식에 큰 변화를 도입했습니다. Braze [Android 13 소프트웨어 개발 키트 업그레이드 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_13/)는 새로운 Android 13 베타 버전이 출시될 때마다 계속 업데이트될 것입니다.
+
+#### 알아야 할 사항
+- **웹 푸시**: Braze [웹 SDK 설정]({{site.baseurl}}/user_guide/message_building_by_channel/push/web)이 있는 경우 웹 푸시를 사용하여 사용자를 참여시키는 것을 고려하세요. 웹 푸시는 앱 푸시 알림이 휴대폰에서 작동하는 방식과 동일하게 작동합니다. 웹 푸시 작성에 대한 자세한 내용은 [푸시 알림 만들기]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/#creating-a-push-message)을 참조하세요.
+- **Singular 앱 타겟팅**: [세분화의 차이점]({{site.baseurl}}/developer_guide/platform_wide/app_group_configuration/#targeting-a-singular-app)을 검토하여 단일 앱과 그 사용자를 타겟팅합니다.
+
+## SMS
+
+#### 확인할 사항
+- **할당량 및 처리량**: 현재 귀하의 계정에 할당된 SMS 할당량(짧은 코드, 긴 코드 등)과 [이를 통해 제공되는 처리량]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup/short_and_long_codes/)을 이해하여 원하는 시간에 보낼 수 있는 충분한 처리량이 있는지 확인하십시오.
+- **SMS 복사본에서 세그먼트 추정**: SMS 복사본을 [SMS 세그먼트 계산기]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/segments/#things-to-keep-in-mind-as-you-create-your-copy)에서 테스트하세요. SMS 세그먼트 수를 처리량 능력과 함께 고려해야 합니다. (오디언스 * SMS segments = Throughput needed). SMS FAQ를 참조하여 [초과 사용을 피하는 방법]({{site.baseurl}}/user_guide/message_building_by_channel/sms/faqs/#how-can-i-avoid-overages)에 대해 알아보세요.
+- **SMS 법률 및 규정**: [SMS 법률, 규정 및 남용 방지]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_laws_and_regulations/)를 검토하여 모든 관련 법률을 준수하여 SMS 서비스를 사용하고 있는지 확인하십시오. 보내기 전에 법률 자문을 구해야 합니다.
+
+#### 알아야 할 사항
+- **SMS 메시지 기본값**: SMS 메시지는 일반적으로 발신자 풀의 짧은 코드에서 보내도록 기본 설정됩니다.
+- **영숫자 발신자 ID**: 알파벳과 숫자가 혼합된 발신자 ID를 사용하면 양방향 메시징이 더 이상 작동하지 않습니다. 이제 이러한 ID는 단방향으로만 작동합니다.
+- **미국에서 업데이트된 처리량**: 미국에서 [A2P 10DLC 등록](https://support.twilio.com/hc/en-us/articles/1260803225669-Message-throughput-MPS-and-Trust-Scores-for-A2P-10DLC-in-the-US)으로 처리량이 변경되었습니다. 여러 가지 요인(예: 트래픽 혼잡 및 운송업체 문제)으로 인해 실제 전달 속도에 영향을 미칠 수 있으므로, 우리는 계약상 어떠한 전송 속도 SLA에도 동의하지 않습니다.
+- **구독 그룹**: Braze를 통해 SMS 캠페인을 시작하려면 구독 그룹을 선택해야 합니다. 또한 국제 [통신 규정 및 지침]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_laws_and_regulations/)을 준수하기 위해 Braze는 [선택한 구독 그룹에 가입하지 않은]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/#how-to-check-a-users-sms-subscription-group) 사용자에게 SMS를 보내지 않습니다.
+
+## WhatsApp
+
+#### 알아야 할 사항
+
+- [**모범 사례**]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_best_practices/): 제안된 WhatsApp 모범 사례를 검토하십시오.
+
+## 콘텐츠 카드
+
+#### 확인할 사항
+- **콘텐츠 카드 크기**: 콘텐츠 카드 메시지 필드는 압축 전 크기가 2KB로 제한되며 제목, 메시지, 이미지 URL, 링크 텍스트, 링크 URL 및 키-값 페어 필드의 바이트 크기를 합산하여 계산됩니다. 이 크기를 초과하는 메시지는 전송되지 않습니다. 이것은 이미지의 크기가 아니라 이미지 URL의 길이를 포함한다는 점에 유의하십시오.
+- **전송 후 복사본 업데이트**: 카드를 보낸 후에는 동일한 카드의 복사본을 업데이트할 수 없습니다. [보낸 카드 업데이트]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/#updating-sent-cards)를 참조하여 이 시나리오에 접근하는 방법을 이해하십시오.
+
+#### 알아야 할 사항
+- **활성 콘텐츠 카드 캠페인 제한**: 최대 500개의 활성 콘텐츠 카드 캠페인을 가질 수 있습니다. 이 수에는 [카드 생성]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/) 옵션으로 전송된 콘텐츠 카드가 포함됩니다.  
+- [**보고 용어**]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/reporting/): 총 노출 횟수, 고유 노출 횟수, 고유 수신자와 같은 용어를 검토하세요. 정의가 때때로 혼란을 일으킬 수 있습니다.
+- **콘텐츠 카드 새로고침**: 기본값으로, Braze는 콘텐츠 카드 요청을 세션 시작 시, 피드 아래로 스와이프할 때(모바일), 그리고 마지막 새로고침이 1분 이상 지났을 때 카드 보기를 열 때 동기화합니다.
+- **캐싱 콘텐츠 카드**: 콘텐츠 카드 캐싱 옵션은 저희 [Android/FireOS]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/customization/custom_styling/#customizing-card-rendering-for-android) 및 [웹](https://js.appboycdn.com/web-sdk/latest/doc/modules/appboy.html#getcachedcontentcards) 문서에서 찾을 수 있습니다. 
+- **최대 게재빈도 설정**: 최대 게재빈도 설정은 콘텐츠 카드에 적용되지 않습니다.
+- **노출 횟수**: 노출 횟수는 일반적으로 카드가 보일 때 기록됩니다. 예를 들어, 받은편지함에 콘텐츠 카드가 가득 차 있는 경우 사용자가 특정 콘텐츠 카드로 스크롤할 때까지 노출 횟수가 기록되지 않습니다. 웹, Android 및 iOS 플랫폼 간에는 몇 가지 미묘한 차이가 있습니다.  
+
+## 인앱 메시지
+
+#### 알아야 할 사항
+- **인앱 메시지 트리거링**: 세션 시작 시, SDK는 모든 적격 인앱 메시지가 트리거와 함께 기기로 전송되도록 요청하므로, 세션 중에 이벤트를 수행하면 인앱 메시지를 빠르고 신뢰성 있게 받을 수 있습니다. 이로 인해 캔버스 내에서 인앱 메시지는 커스텀 이벤트로 트리거될 수 없습니다.
+- **전송 대 노출 횟수**: 인앱 메시지의 경우, "발송됨"의 개념은 다른 사용 가능한 채널과 다릅니다. 인앱 메시지를 보려면 사용자가 세션을 시작하고, 해당 오디언스에 속하며, 트리거를 수행해야 합니다. 이 때문에 우리는 "노출 횟수"를 더 명확하게 추적합니다.
+- **트리거**: 기본값으로, 인앱 메시지는 SDK에 의해 기록된 이벤트에 의해 트리거됩니다. 서버에서 보낸 이벤트로 인해 인앱 메시지를 트리거하려면 [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/custom_triggering/) 및 [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/customization)에 대한 이러한 가이드를 통해서도 이를 달성할 수 있습니다.
+- [**캔버스 인-앱 메시지**]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/in-app_messages_in_canvas/#advancement-behavior-options): 이 메시지는 사용자가 앱을 처음 열 때(세션 시작 시 트리거됨) 캔버스 구성 요소에서 예약된 메시지가 전송된 후에 나타납니다.
diff --git a/_lang/ko/_help/help_articles/campaigns_and_canvas/locations_data_in_campaigns.md b/_lang/ko/_help/help_articles/campaigns_and_canvas/locations_data_in_campaigns.md
new file mode 100644
index 00000000000..25e213749f4
--- /dev/null
+++ b/_lang/ko/_help/help_articles/campaigns_and_canvas/locations_data_in_campaigns.md
@@ -0,0 +1,41 @@
+---
+nav_title: 위치 데이터 확인
+article_title: 위치 데이터 확인
+page_order: 1
+page_type: solution
+description: "이 도움말 문서에서는 사용 가능한 위치가 없는 경우 도움이 될 수 있는 빠른 확인 방법을 안내합니다."
+tool: Location
+---
+
+# 위치 데이터 확인
+
+Braze는 기본적으로 SDK를 통해 사용자의 가장 최근 위치를 캡처합니다. 일반적으로 "최근 위치"는 사용자가 가장 최근에 앱을 사용한 위치를 의미합니다. Braze 백그라운드 위치 데이터를 전송하면 더 세분화된 데이터를 사용할 수 있습니다.
+
+사용 가능한 위치가 없는 경우 두 가지 빠른 확인을 통해 데이터 수집 및 날짜 전송을 확인할 수 있습니다.
+
+## 데이터 수집
+
+앱이 위치 데이터를 수집하고 있는지 확인합니다:
+
+- iOS의 경우, 이는 사용자가 사용자 여정의 어느 시점에서 메시지를 통해 위치 데이터 공유에 옵트인한다는 의미입니다. 
+- Android의 경우 앱 설치 시 앱이 미세 또는 거친 위치 권한을 요청하는지 확인합니다.
+
+사용자 위치 데이터가 Braze로 전송되고 있는지 확인하려면 **위치 사용 가능** 필터를 사용하세요. 이 필터를 사용하면 '가장 최근 위치'를 가진 사용자의 비율을 확인할 수 있습니다.
+
+![][25]
+
+## 데이터 전송
+
+개발자가 위치 데이터를 Braze에 전달하고 있는지 확인하세요. 일반적으로 위치 데이터 전달은 사용자가 권한을 부여한 후 SDK에서 자동으로 처리되지만, 개발자가 Braze에서 위치 추적을 비활성화했을 수 있습니다. 위치 추적에 대한 자세한 내용은 다음에서 확인할 수 있습니다:
+- \[Android][26]
+- \[iOS][27]
+- \[웹][28]
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트: 2022년 11월 16일_
+
+[25]: {% image_buster /assets/img_archive/trouble7.png %}
+[26]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/analytics/location_tracking/
+[27]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/location_tracking/
+[28]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/location_tracking/
diff --git a/_lang/ko/_help/help_articles/campaigns_and_canvas/more_people_in_control_group.md b/_lang/ko/_help/help_articles/campaigns_and_canvas/more_people_in_control_group.md
new file mode 100644
index 00000000000..89917578585
--- /dev/null
+++ b/_lang/ko/_help/help_articles/campaigns_and_canvas/more_people_in_control_group.md
@@ -0,0 +1,46 @@
+---
+nav_title: 대형 대조군 다루기
+article_title: 대형 대조군 다루기
+page_order: 2
+
+page_type: solution
+description: "이 도움말 기사에서는 대조군이 예상보다 클 수 있는 이유를 설명하고 이를 해결하기 위한 단계를 안내합니다."
+tool: Canvas
+---
+
+# 대형 대조군 다루기
+
+캔버스를 만들 때 다음 [예시](#example)와 같이 대조군과 배리언트 그룹 사이에 오디언스가 균등하게 나뉘기를 기대했을 수 있습니다. Braze가 그 이유와 해결 방법을 설명해 드리죠!
+
+사용자가 가입하는 그룹은 설정에 따라 다릅니다. 이것은 대조군 또는 배리언트 그룹일 수 있습니다. 사용자가 모든 기준을 충족하면 \[진입 단계][1]에서 캔버스에 들어갑니다. 캔버스를 설정할 때, 각 배리언트와 대조군에 들어갈 사용자 비율을 정의합니다.
+
+만약 대조군이 배리언트 그룹에 비해 크다면 (그리고 이것이 본인의 의도가 아니라면) 다음을 권장합니다.
+1. 진입 오디언스 필터를 "푸시 활성화 여부"로 설정하세요.
+2. 진입 오디언스 필터를 "옵트인 또는 구독됨"으로 설정하세요.
+
+캔버스를 대조군과 함께 만들 때, 엔트리 오디언스의 모든 사용자가 캔버스 내에서 메시지를 받을 수 있도록 하세요(예: 캔버스에는 푸시 및 이메일 메시지가 포함되어야 합니다).
+
+## 사용 사례
+
+다음 시나리오를 상상해 봅시다:
+- 캔버스는 하나의 배리언트와 대조군을 가지고 있습니다.
+- 배리언트의 첫 번째 단계는 푸시 알림입니다.
+- 사용자의 90%는 배리언트에 들어가도록 선택되었고, 10%는 대조군에 들어가도록 선택되었습니다.
+
+![캔버스 예제][41]
+
+이 시나리오에서 캔버스에 들어가는 사용자의 90%가 배리언트에 들어갈 것입니다. 
+
+활성 사용자로 돌아보면, 39.8k 사용자가 포함되어 있지만 그 중 73%만 푸시가 활성화되어 있음을 알 수 있습니다.
+
+![항목 오디언스][42]
+
+이는 사용자의 90%가 배리언트에 들어가도록 지정했더라도 실제로 모든 사용자가 푸시 알림을 받을 수 있는 것은 아니라는 것을 의미합니다. 푸시 알림을 받을 수 없는 이러한 사용자는 여전히 배리언트에 들어갑니다.
+
+아직 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을(를) 여세요.
+
+_마지막 업데이트 날짜: 2020년 12월 3일_
+
+[1]: {{site.baseurl }}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-2-use-the-entry-wizard-to-set-up-your-canvas
+[41]: {% image_buster /assets/img_archive/trouble15.png %}
+[42]: {% image_buster /assets/img_archive/trouble16.png %}
diff --git a/_lang/ko/_help/help_articles/campaigns_and_canvas/not_triggering.md b/_lang/ko/_help/help_articles/campaigns_and_canvas/not_triggering.md
new file mode 100644
index 00000000000..241efa5eb07
--- /dev/null
+++ b/_lang/ko/_help/help_articles/campaigns_and_canvas/not_triggering.md
@@ -0,0 +1,34 @@
+---
+nav_title: 트리거되지 않은 캠페인 또는 캔버스
+article_title: 트리거되지 않은 캠페인 또는 캔버스
+page_order: 5
+
+page_type: solution
+description: "이 도움말 문서에서는 캠페인 또는 캔버스가 예상대로 트리거되지 않는 문제를 해결하는 단계를 안내합니다."
+tool: 
+- Campaigns
+- Canvas
+---
+
+# 트리거되지 않은 캠페인 또는 캔버스
+
+예상한 트리거 동작을 얻지 못한 데에는 여러 가지 이유가 있습니다. 가장 일반적인 오류에 대한 솔루션은 트리거하는 캠페인이 세그먼트에서 동일한 트리거 이벤트를 사용하지 않는지 확인하는 것입니다.
+
+## 캠페인 트리거
+
+세그먼트 멤버십은 트리거 작업 전에 평가됩니다. 즉, 사용자가 먼저 세그먼트에 속하지 않으면 트리거를 수행하더라도 캠페인을 수신하지 못합니다.
+
+캠페인이 사용자 지정 이벤트에서 트리거되는 경우 캠페인에서 사용하려는 세그먼트에 의해 이 이벤트가 사전 필터링되지 않았는지 확인해야 합니다. 
+
+예를 들어 세그먼트에 `SessionStart` "앱을 한 번 이상 사용함" 이벤트가 포함되어 있고 캠페인이 트리거되는 이벤트가 `SessionStart`인 경우 사용자는 메시지를 받게 되지만 반드시 첫 번째 세션에 대한 메시지가 아닐 수도 있습니다. 이는 사용자가 캠페인을 수신해야 하는지 확인하는 첫 번째 단계에서 캠페인이 세그먼트 타겟 오디언스를 검토하기 때문입니다. 
+
+즉, 오디언스 필터와 동일한 트리거(예: 속성 변경 또는 사용자 지정 이벤트 수행)를 사용하여 액션 기반 캠페인 또는 캔버스를 구성하지 마세요. 사용자가 트리거 이벤트를 수행할 때 오디언스에 없는 [경합 조건][2]이 발생할 수 있으며, 이는 사용자가 캠페인을 수신하지 못하거나 캔버스에 입장하지 못한다는 의미입니다.
+
+{% alert tip %}
+캠페인 문제 해결에 대한 추가 지원이 필요한 경우, 최근 30일간의 진단 로그만 보유하고 있으므로 문제 발생 후 30일 이내에 Braze 지원팀에 문의하시기 바랍니다.
+{% endalert %}
+
+_마지막 업데이트 2024년 6월 25일_
+
+[1]: {{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/#session-start-event/
+[2]: {{site.baseurl}}/user_guide/engagement_tools/testing/race_conditions/#race-conditions/
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/campaigns_and_canvas/using_custom_event_properties.md b/_lang/ko/_help/help_articles/campaigns_and_canvas/using_custom_event_properties.md
new file mode 100644
index 00000000000..39f57904d8e
--- /dev/null
+++ b/_lang/ko/_help/help_articles/campaigns_and_canvas/using_custom_event_properties.md
@@ -0,0 +1,56 @@
+---
+nav_title: 커스텀 이벤트 속성 로깅
+article_title: 커스텀 이벤트 속성 로깅
+page_order: 3
+page_type: solution
+description: "이 도움말 문서는 커스텀 이벤트가 예상대로 기록되도록 보장하기 위한 세 가지 중요한 점검을 안내합니다."
+tool: 
+- Campaigns
+- Canvas
+---
+
+# 커스텀 이벤트 속성 로깅
+
+세 가지 중요한 확인 사항이 있습니다. 커스텀 이벤트가 예상대로 기록되고 있는지 확인하세요.
+
+* [어떤 이벤트가 기록되는지 확인](#verify-events)
+* [로그 확인](#verify-log)
+* [값 확인](#verify-values)
+
+## 커스텀 이벤트 속성 확인
+
+[커스텀 이벤트 속성][22]은 커스텀 이벤트를 설명하는 메타데이터입니다. 커스텀 이벤트가 기록될 때마다 여러 속성이 기록될 수 있습니다.
+
+### 이벤트 확인
+
+개발자에게 어떤 이벤트 속성정보가 추적되고 있는지 확인하세요. 모든 이벤트 속성은 대소문자를 구분한다는 점을 명심하세요. 커스텀 이벤트 추적에 대한 추가 정보는 플랫폼에 따라 다음 기사를 확인하세요.
+
+* [Android][51]
+* [iOS][23]
+* [웹][52]
+
+### 로그 확인
+
+이벤트 속성이 성공적으로 추적되었는지 확인하려면 **커스텀 이벤트** 페이지에서 모든 이벤트 속성을 볼 수 있습니다.
+
+1. **데이터 설정** > **커스텀 이벤트**로 이동합니다.
+2. 목록에서 커스텀 이벤트를 찾으세요.
+3. 이벤트를 위해 **속성 관리**를 클릭하십시오. 이것은 이벤트와 관련된 속성의 이름을 보여줍니다.
+
+### 값 확인
+
+사용자를 테스트 사용자로 추가한 후, 값을 확인하려면 다음 단계를 따르세요. 
+
+1. 앱 내에서 커스텀 이벤트를 수행합니다.
+2. 데이터가 플러시될 때까지 약 10초 정도 기다리세요.
+3. [이벤트 사용자 로그][24]를 새로고침하여 커스텀 이벤트 및 함께 전달된 이벤트 속성정보 값을 확인하세요.
+
+아직 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을(를) 여세요.
+
+_마지막 업데이트 날짜: 2023년 4월 10일_
+
+[22]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-properties
+[23]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/tracking_custom_events/
+[24]: {{site.baseurl}}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab
+[51]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/analytics/tracking_custom_events/ 
+[52]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/tracking_custom_events/
diff --git a/_lang/ko/_help/help_articles/campaigns_and_canvas/using_event_logging.md b/_lang/ko/_help/help_articles/campaigns_and_canvas/using_event_logging.md
new file mode 100644
index 00000000000..4c4dff89483
--- /dev/null
+++ b/_lang/ko/_help/help_articles/campaigns_and_canvas/using_event_logging.md
@@ -0,0 +1,24 @@
+---
+nav_title: 이벤트 로깅 사용
+article_title: 이벤트 로깅 사용
+page_order: 6
+page_type: solution
+description: "이 도움말 문서에서는 이벤트 로깅을 사용하여 Braze 통합 관련 문제를 해결하는 방법을 설명합니다."
+---
+
+# 이벤트 로깅 사용
+
+Braze 통합 관련 문제를 해결하는 데 도움이 되도록 익명 사용자 프로필과 [이벤트 사용자 로그][1]를 설정할 수 있습니다. 익명 프로필을 설정하는 방법에 대한 단계는 [테스트 사용자 추가하기][2]를 참조하세요.
+
+## 로깅 정보
+
+이벤트 로깅을 사용하여 익명 사용자의 동작을 테스트하세요. 이는 테스트 중인 앱이 이메일을 수집하지 않는 경우 사용자 ID를 식별하는 데 특히 유용할 수 있습니다. Braze와 디바이스의 IP 주소를 사용하여 해당 디바이스를 테스트 사용자로 추가할 수 있습니다.
+
+익명의 사용자를 찾을 수 있는 좋은 방법입니다. 또한 이 정보를 사용하여 Braze로 전송되는 데이터를 테스트하고 불일치 여부를 확인할 수 있습니다. 이 보기에서 데이터의 델타가 Braze로 전송되는지 여부를 확인할 수 있습니다. 이벤트가 기록될 때마다 이메일 주소 또는 푸시 토큰이 전송되면 모든 데이터가 Braze로 전송됩니다.
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트: 2022년 11월 16일_
+
+[1]: {{site.baseurl}}/user_guide/administrative/app_settings/developer_console/event_user_log_tab
+[2]: {{site.baseurl}}/user_guide/administrative/app_settings/developer_console/internal_groups_tab/#adding-test-users
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/content_cards.md b/_lang/ko/_help/help_articles/content_cards.md
new file mode 100644
index 00000000000..c9ed3106c22
--- /dev/null
+++ b/_lang/ko/_help/help_articles/content_cards.md
@@ -0,0 +1,18 @@
+---
+page_order: 2.5
+nav_title: 콘텐츠 카드
+layout: dev_guide
+guide_top_header: "콘텐츠 카드 도움말 문서"
+guide_top_text: "콘텐츠 카드 문제 해결 방법은 다음 문서를 참조하세요. <br><br> <a href='/docs/user_guide/message_building_by_channel/content_cards/'>콘텐츠 카드</a> 섹션에서 캠페인과 캔버스에 콘텐츠 카드를 통합할 수 있는 다양한 방법에 대해 자세히 알아보세요!"
+
+page_type: landing
+description: "이 랜딩 페이지는 콘텐츠 카드와 관련된 도움말 문서가 있는 곳입니다."
+channel: content cards
+noindex: true
+guide_menu_title: ""
+guide_menu_list:
+  - name: 빈 콘텐츠 카드 피드
+    link: /docs/help/help_articles/content_cards/empty_content_card_feed/
+    image: /assets/img/braze_icons/x-circle.svg
+
+---
diff --git a/_lang/ko/_help/help_articles/content_cards/empty_content_card_feed.md b/_lang/ko/_help/help_articles/content_cards/empty_content_card_feed.md
new file mode 100644
index 00000000000..d01d2ef31d6
--- /dev/null
+++ b/_lang/ko/_help/help_articles/content_cards/empty_content_card_feed.md
@@ -0,0 +1,22 @@
+---
+nav_title: 빈 콘텐츠 카드 피드
+article_title: 빈 콘텐츠 카드 피드
+page_order: 0
+
+page_type: solution
+description: "이 도움말 문서에서는 신규 사용자의 피드에 콘텐츠 카드가 없는 이유와 이 문제를 해결하는 방법에 대해 설명합니다."
+channel: content cards
+---
+
+# 빈 콘텐츠 카드 피드
+
+예약 전송으로 콘텐츠 카드 캠페인을 보낼 때 [카드 생성]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/#overview)에 선택하는 옵션은 새 사용자의 첫 세션에서 피드에 카드가 표시되는지 여부에 영향을 줄 수 있습니다. **카드 생성**이 **캠페인 시작** 시로 설정된 경우, 캠페인이 전송될 때 Braze가 오디언스 멤버십을 평가하기 때문에 캠페인이 시작된 후에 생성된 사용자는 피드에서 콘텐츠 카드를 받지 못합니다.
+
+새 사용자가 카드를 받도록 하려면 다음 중 하나를 수행하세요:
+
+- 예약 배송 캠페인을 생성하고 **카드 생성을** **첫인상으로** 설정합니다. 첫 번째 세션에서 이 카드를 받게 됩니다.
+- 액션 기반 전달 캠페인을 만듭니다. 다음 번에 선택한 행동을 수행할 때 이 카드를 받게 됩니다.
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트 2023년 4월 17일_
diff --git a/_lang/ko/_help/help_articles/data.md b/_lang/ko/_help/help_articles/data.md
new file mode 100644
index 00000000000..6b6156964ce
--- /dev/null
+++ b/_lang/ko/_help/help_articles/data.md
@@ -0,0 +1,22 @@
+---
+page_order: 2.5
+nav_title: 데이터
+layout: dev_guide
+guide_top_header: "데이터 도움말 문서"
+guide_top_text: "Braze에서 데이터의 미묘한 차이에 대한 질문을 명확히 하는 데 도움이 될 수 있는 이러한 기사를 확인하세요. <br><br> 더 일반적인 데이터 관련 정보는 <a href='/docs/user_guide/data_and_analytics/'>데이터 &amp; 분석</a>에 있는 기사를 참조하세요!"
+
+page_type: landing
+description: "이 랜딩 페이지에는 Braze 데이터와 관련된 도움말 문서가 포함되어 있습니다."
+noindex: true
+guide_menu_title: ""
+guide_menu_list:
+  - name: 커스텀 속성 또는 이벤트 데이터 유형 변경
+    link: /docs/help/help_articles/data/change_custom_data_type/
+    image: /assets/img/braze_icons/table.svg
+  - name: 디스패치 ID 동작
+    link: /docs/help/help_articles/data/dispatch_id/
+    image: /assets/img/braze_icons/key-01.svg
+  - name: 차단 목록 대 삭제
+    link: /docs/help/help_articles/data/blocklisting_deletion/
+    image: /assets/img/braze_icons/trash-01.svg
+---
diff --git a/_lang/ko/_help/help_articles/data/blocklisting_deletion.md b/_lang/ko/_help/help_articles/data/blocklisting_deletion.md
new file mode 100644
index 00000000000..42dc4b47ab1
--- /dev/null
+++ b/_lang/ko/_help/help_articles/data/blocklisting_deletion.md
@@ -0,0 +1,23 @@
+---
+nav_title: 차단 목록과 삭제의 차이점
+article_title: 차단 목록과 삭제의 차이점
+page_order: 2
+
+page_type: solution
+description: "이 도움말 문서에서는 속성 차단 목록과 삭제의 차이점에 대해 설명합니다."
+---
+
+# 차단 목록과 삭제의 차이점
+
+Braze에서 속성을 차단 목록에 추가하는 것과 삭제하는 것의 차이를 이해하기 위해 각 작업의 결과를 검토해 보겠습니다:
+
+- **차단 목록:** 커스텀 속성, 이벤트 또는 구매가 차단 목록에 있는 경우 해당 속성은 고객 프로필에 남아 있지만 해당 속성에 대한 새로운 요청은 처리되지 않습니다.
+- **삭제:** 커스텀 속성, 이벤트 또는 구매가 삭제되면 데이터가 제거됩니다. 그러나 Braze는 해당 속성이 여전히 SDK를 통해 추적되거나 API 또는 CSV를 통해 업로드되는 경우 해당 속성에 대한 새로운 수신 요청을 계속 수락합니다.
+
+## 어떻게 해야 하나요?
+
+차단 목록을 작성하려면 Braze는 차단 목록 정보를 각 사용자의 기기로 전송해야 하며, 이는 데이터 집약적인 작업으로, Braze는 이를 피하고자 합니다. 또한 목록이 너무 많으면(속성, 이벤트 또는 구매가 100개 이상) 앱 속도가 느려질 수 있습니다. 
+
+더 이상 Braze에 속성을 전송할 계획이 없다면 삭제 경로를 사용하는 것이 좋습니다.
+
+경로에 관계없이 제거하려는 사용자 지정 속성, 이벤트 및 구매는 더 이상 **워크스페이스 관리** 페이지에 표시되지 않으며, 세그먼트 필터로 제거됩니다. 사용자 수준 데이터는 프로필에 그대로 유지됩니다. 
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/data/change_custom_data_type.md b/_lang/ko/_help/help_articles/data/change_custom_data_type.md
new file mode 100644
index 00000000000..3e77501fc8a
--- /dev/null
+++ b/_lang/ko/_help/help_articles/data/change_custom_data_type.md
@@ -0,0 +1,32 @@
+---
+nav_title: 커스텀 속성 또는 이벤트 데이터 유형 변경
+article_title: 커스텀 속성 또는 이벤트 데이터 유형 변경
+page_order: 1
+
+page_type: solution
+description: "이 도움말 문서는 커스텀 속성 또는 커스텀 이벤트의 데이터 유형을 변경하는 방법과 그에 따른 영향을 안내합니다."
+---
+
+# 커스텀 속성 또는 이벤트 데이터 유형 변경
+
+커스텀 속성 또는 이벤트의 데이터 유형을 변경하려면 Braze 대시보드에서 **데이터 설정**으로 이동한 다음 **커스텀 속성** 또는 **커스텀 이벤트**을 선택하십시오.
+
+{% alert note %}
+[이전 탐색]({{site.baseurl}}/navigation)을 사용하는 경우 **커스텀 이벤트** 및 **커스텀 속성** 페이지는 **설정 관리** 아래에 있습니다.
+{% endalert %}
+
+![커스텀 속성 탭에서 속성 또는 데이터 유형을 편집][1]
+
+커스텀 속성 또는 이벤트의 데이터 유형을 변경해야 하는 경우(예: `time`을 `string`으로 변경), 다음을 고려합니다.
+
+- 변경된 속성 또는 이벤트를 사용하는 세그먼트, 캠페인, 캔버스 또는 기타 위치의 관련 필터는 자동으로 업데이트되지 않습니다. 속성을 수정하기 전에 속성을 세그먼트나 필터에서 사용하는 캠페인이나 캔버스를 중지하고, 속성을 참조하는 필터에서 속성을 제거해야 합니다.
+- 사용자 데이터는 소급하여 업데이트되지 않습니다. 변경된 속성이 데이터 유형 변경 전에 고객 프로필에 있었다면, 해당 값은 여전히 이전 데이터 유형일 것입니다. 이로 인해 변경된 속성을 포함하고 있는 세그먼트에서 사용자가 제외될 수도 있습니다. 필터는 새 데이터 유형을 찾아 나서게 되지만, 프로필에 여전히 이전 데이터 유형이 있는 경우라면, 해당 사용자는 지금부터는 세그먼트에서 제외됩니다. 이러한 사용자를 적절한 세그먼트에 다시 포함하려면 먼저 업데이트가 필요합니다. [`users/track` 엔드포인트]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)를 사용하여 이 작업을 수행할 수 있습니다.
+- 새로운 데이터는 새로운 데이터 유형이 아니면 허용되지 않습니다. 예를 들어, 변경된 속성에 대한 이전 데이터 유형을 포함하는 `users/track` 엔드포인트에 대한 API 호출은 허용되지 않습니다. 새로운 데이터 유형을 호출해야 합니다.
+
+{% alert important %}
+자동 감지가 커스텀 속성 데이터 유형을 업데이트하지 못하도록 방지하는 기능은 현재 초기 액세스 중입니다. 이 얼리 액세스에 참여하려면 고객 성공 매니저에게 문의하세요.
+{% endalert %}
+
+_마지막 업데이트 날짜: 2024년 2월 8일_
+
+[1]: {% image_buster /assets/img/change_custom_attribute.png %}
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/data/dispatch_id.md b/_lang/ko/_help/help_articles/data/dispatch_id.md
new file mode 100644
index 00000000000..03f70416310
--- /dev/null
+++ b/_lang/ko/_help/help_articles/data/dispatch_id.md
@@ -0,0 +1,44 @@
+---
+nav_title: 디스패치 ID 동작
+article_title: 디스패치 ID 동작
+page_order: 0
+
+page_type: solution
+description: "이 도움말 문서에서는 사용 방법, 의미 및 제한 사항 등 디스패치 ID 동작에 대해 설명합니다."
+---
+
+# 디스패치 ID 동작
+
+`dispatch_id`는 메시지 발송의 ID로, Braze에서 보낸 각 "전송"에 대한 고유 ID입니다. 예약 메시지를 받은 사용자에게는 동일한 `dispatch_id` 메시지가 전송됩니다. 일반적으로 액션 기반 또는 API 트리거된 메시지는 사용자당 고유한 `dispatch_id`를 수신하지만, 서로 가까운 거리에서 전송된 메시지는 여러 사용자 간에 동일한 `dispatch_id`를 공유할 수 있습니다.
+
+따라서 메시지가 두 개의 다른 시간에 전송된 경우 단일 캠페인에 대해 서로 다른 두 명의 사용자가 서로 다른 발송 ID를 갖게 될 수 있습니다. 이는 API 요청이 개별적으로 이루어졌기 때문인 경우가 많습니다. 두 사용자가 단일 전송에서 동일한 캠페인 오디언스 그룹에 속해 있다면 두 사용자의 발송 ID는 동일합니다.
+
+## 캠페인의 디스패치 ID 동작
+
+예약된 캠페인 메시지는 동일한 `dispatch_id`를 가져옵니다. 액션 기반 또는 API 트리거 캠페인 메시지는 위에서 설명한 대로 사용자당 고유한 `dispatch_id`를 받거나, 위에서 설명한 대로 근접한 위치에서 또는 동일한 API 호출로 전송되는 경우 여러 사용자에게 동일한 `dispatch_id`를 받을 수 있습니다. 예를 들어, 예약된 캠페인 오디언스에 속한 두 명의 사용자는 캠페인이 예약될 때마다 동일한 `dispatch_id`를 갖게 됩니다. 그러나 API 트리거 캠페인의 오디언스에 있는 두 사용자가 서로 가까이 있지 않고 별도의 API 호출을 통해 전송된 경우 서로 다른 디스패치 ID를 가질 수 있습니다.
+
+멀티채널 캠페인은 전달 유형에 대해 설명한 것과 동일한 동작을 갖습니다.
+
+{% alert warning %}
+`dispatch_id`는 모든 캔버스 단계에 대해 무작위로 생성되는데, 이는 Braze가 캔버스 단계가 "예약된" 경우에도 트리거된 이벤트로 취급하기 때문입니다. 이로 인해 ID 생성에 불일치가 발생할 수 있습니다. 때때로 캔버스 구성 요소는 전송당 사용자당 고유한 `dispatch_id`를 갖거나 전송당 사용자 간에 공유 디스패치 ID를 가질 수 있습니다.
+{% endalert %}
+
+## Liquid를 사용하여 발송 ID를 메시지로 템플릿화
+
+메시지 내에서 메시지 발송을 추적하려면(예: URL) `dispatch_id`에서 템플릿을 만들 수 있습니다. [지원되는 개인화 태그]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/) 목록의 캔버스 속성에서 이에 대한 서식을 찾을 수 있습니다.
+
+캠페인 생성 시 `api_id`를 사용할 수 없으므로 입력 안내로 템플릿이 지정되고 `dispatch_id_for_unsent_campaign`으로 미리 보기된다는 점에서 `api_id`와 동일하게 작동합니다. ID는 메시지가 전송되기 전에 생성되며 전송 시간에 포함됩니다.
+
+{% alert warning %}
+인앱 메시지에는 `dispatch_id`가 없으므로 `dispatch_id_for_unsent_campaign`의 Liquid 템플릿은 인앱 메시지에서 작동하지 않습니다.
+{% endalert %}
+
+## 이메일용 발송 ID 커런츠 필드
+
+커런츠 기능을 지속적으로 개선하기 위해 모든 커넥터 유형에 걸쳐 커런츠 이메일 이벤트에 `dispatch_id` 필드를 추가했습니다. `dispatch_id`는 Braze 플랫폼에서 전송되는 각 전송 또는 디스패치에 대해 생성된 고유 ID입니다.
+
+예약 메시지를 받는 모든 고객은 동일한 `dispatch_id`를 받지만, 작업 기반 또는 API 트리거된 메시지를 받는 고객은 메시지당 고유한 `dispatch_id`를 받습니다. `dispatch_id` 필드를 사용하면 어떤 반복 캠페인 인스턴스가 전환을 담당하고 있는지 식별할 수 있으므로 어떤 유형의 캠페인이 비즈니스 목표를 달성하는 데 도움이 되는지에 대한 더 많은 인사이트와 정보를 얻을 수 있습니다.
+
+`dispatch_id`를 [개인화 태그]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#supported-personalization-tags)로 사용하거나 [메시지 인게이지먼트 이벤트에서]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/), 또는 [세그먼트]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment_for_currents/#integration-details), [Mixpanel]({{site.baseurl}}/partners/insights/behavioral_analytics/mixpanel_for_currents/#email-events) 또는 커런츠 [Amplitude]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_for_currents/)를 사용할 때 사용할 수 있습니다.
+
+_마지막 업데이트: 2021년 7월 15일_
diff --git a/_lang/ko/_help/help_articles/docs.md b/_lang/ko/_help/help_articles/docs.md
new file mode 100644
index 00000000000..a8c252b9517
--- /dev/null
+++ b/_lang/ko/_help/help_articles/docs.md
@@ -0,0 +1,20 @@
+---
+page_order: 10
+nav_title: 기술문서
+layout: dev_guide
+guide_top_header: "문서 도움말 문서"
+guide_top_text: "Braze 설명서 사이트와 관련된 추가 정보는 다음 리소스를 확인하세요."
+
+page_type: landing
+description: "이 랜딩 페이지에는 오픈 소스 문서에 기여하는 방법 등 Braze 설명서 사이트와 관련된 리소스가 포함되어 있습니다."
+noindex: true
+guide_menu_title: ""
+guide_menu_list:
+  - name: Braze 설명서에 기여하기
+    link: /docs/help/help_articles/docs/contribution/
+    image: /assets/img/braze_icons/edit-05.svg
+  - name: 스크롤 막대 겹침
+    link: /docs/help/help_articles/docs/scroll_bar_overlap/
+    image: /assets/img/braze_icons/arrow-square-right.svg
+
+---
diff --git a/_lang/ko/_help/help_articles/docs/scroll_bar_overlap.md b/_lang/ko/_help/help_articles/docs/scroll_bar_overlap.md
new file mode 100644
index 00000000000..ba3761cc14b
--- /dev/null
+++ b/_lang/ko/_help/help_articles/docs/scroll_bar_overlap.md
@@ -0,0 +1,39 @@
+---
+nav_title: 스크롤 막대 겹침
+article_title: 스크롤 막대 겹침
+page_order: 0
+
+page_type: solution
+description: "이 도움말 문서에서는 Mac 사용자에게 Braze 설명서 내에서 콘텐츠가 겹치는 스크롤 막대를 해결하는 방법을 안내합니다."
+---
+
+# 스크롤 막대 겹침
+
+Mac을 사용 중인데 다음 예시와 같이 Braze Docs 내에서 스크롤 막대가 콘텐츠와 겹치는 현상이 발생하나요?
+
+![스크롤 막대 겹침의 예][1]
+
+스크롤 막대가 다음 코드 블록과 겹치는지 확인합니다:
+
+```
+<your-bucket-prefix>/dataexport.<cluster-identifier>.S3.integration.<integration-id>/event_type=<event-type>/date=<date>/<schema-id>/<zone>/dataexport.<cluster-identifier>.S3.integration.<integration-id>+<partition>+<offset>.avro
+```
+
+스크롤 막대가 코드 블록과 겹치는 경우 **일반 설정에서** **스크롤 막대 표시:** 설정을 **항상으로** 변경하는 것이 좋습니다. 이렇게 하면 문서에서 코드 블록과 같은 기능을 확장하여 스크롤 막대를 항상 표시하고 가독성을 방지할 수 있습니다.
+
+![MacOS 일반 설정][2]
+
+이제 업데이트된 스크롤 막대의 모습은 다음과 같습니다:
+
+![겹치지 않는 고정 스크롤 막대 예시][3]
+
+_마지막 업데이트: 2019년 3월 27일_
+
+{% comment %}
+문제를 일으킬 수 있는 한 줄의 긴 코드가 있는 곳에 삽입하세요:
+_스크롤 막대 때문에 코드가 보이지 않나요? [이]({{site.baseurl}}/help/help_articles/docs/scroll_bar_overlap/) 문제를 해결하는 방법은 [여기에서]({{site.baseurl}}/help/help_articles/docs/scroll_bar_overlap/) 확인하세요._
+{% endcomment %}
+
+[1]: {% image_buster /assets/img/scroll-overlap.png %}
+[2]: {% image_buster /assets/img/general-on-mac.png %}
+[3]: {% image_buster /assets/img/scroll-bar-on.png %}
diff --git a/_lang/ko/_help/help_articles/email.md b/_lang/ko/_help/help_articles/email.md
new file mode 100644
index 00000000000..943688447f9
--- /dev/null
+++ b/_lang/ko/_help/help_articles/email.md
@@ -0,0 +1,26 @@
+---
+page_order: 3
+nav_title: 이메일
+layout: dev_guide
+guide_top_header: "이메일 도움말 문서"
+guide_top_text: "다음 도움말 기사를 확인하여 이메일 캠페인에 대한 일반적인 문제 및 질문에 대한 정보를 확인하세요. <br><br> Braze를 사용하여 개인화된 이메일 메시지를 만드는 방법에 관심이 있으신가요? <a href='/docs/user_guide/message_building_by_channel/email/'>이메일</a> 섹션을 확인하여 자세히 알아보세요!"
+
+page_type: landing
+description: "이 랜딩 페이지는 일반적인 이메일 문제에 대한 도움말 기사가 있는 곳입니다."
+channel: email
+noindex: true
+guide_menu_title: ""
+guide_menu_list:
+  - name: 이메일 바운스
+    link: /docs/help/help_articles/email/email_bounces
+    image: /assets/img/braze_icons/mail-04.svg
+  - name: 클릭률 증가 처리
+    link: /docs/help/help_articles/email/open_rates/
+    image: /assets/img/braze_icons/cursor-click-02.svg
+  - name: 테스트 이메일의 HTML 렌더링 문제 해결 
+    link: /docs/help/help_articles/email/html_looks_strange/
+    image: /assets/img/braze_icons/code-02.svg
+  - name: 유니버설 링크 및 앱 링크
+    link: /docs/help/help_articles/email/universal_links/
+    image: /assets/img/braze_icons/link-03.svg
+---
diff --git a/_lang/ko/_help/help_articles/email/email_bounces.md b/_lang/ko/_help/help_articles/email/email_bounces.md
new file mode 100644
index 00000000000..4a972be9678
--- /dev/null
+++ b/_lang/ko/_help/help_articles/email/email_bounces.md
@@ -0,0 +1,37 @@
+---
+nav_title: 이메일 반송
+article_title: 이메일 반송
+page_order: 0
+page_type: solution
+description: "이 도움말 문서에서는 하드 바운스와 소프트 바운스의 차이점을 명확하게 설명합니다."
+channel: email
+---
+
+# 이메일 반송
+
+이메일 캠페인에서 보낸 메시지가 사용자의 이메일 주소에서 반송되면 어떻게 해야 하나요? 먼저 이메일 반송의 두 가지 유형인 하드 반송과 소프트 반송을 정의하고 문제를 해결해 보겠습니다. 
+
+## 하드 바운스
+
+이메일 메시지가 하드 반송되면 이메일 주소가 유효하지 않거나 존재하지 않는 것입니다. 이 경우 Braze는 이메일 주소를 유효하지 않은 것으로 표시하지만 사용자의 [구독 상태][1]는 업데이트하지 않습니다. 이 시점에서 Braze는 유효하지 않은 것으로 표시된 이메일 주소로 메시지를 보내려고 시도하지 않습니다.
+
+## 소프트바운스
+
+소프트 반송은 수신자의 이메일 주소가 유효하거나 이메일 메시지가 수신자의 이메일 서버에 도달했지만 일시적인 문제로 인해 메시지가 거부된 경우에 발생합니다. 이러한 일시적인 문제는 다음과 같은 경우에 발생할 수 있습니다:
+- 수신자의 받은편지함이 꽉 찼습니다.
+- 메시지가 너무 커서 수신자의 받은편지함에 넣을 수 없습니다.  
+- 이메일 서버가 다운되었습니다.
+
+이메일이 소프트바운스되면 일반적으로 72시간 이내에 재시도하지만, 재시도 횟수는 수신자마다 다릅니다.
+
+소프트바운스는 캠페인 분석에서 추적되지 않지만, [메시지 활동 로그][3]에서 소프트바운스를 모니터링할 수 있습니다. 여기에서 소프트바운스의 원인을 확인하고 이메일 캠페인의 "전송"과 "전달" 간에 발생할 수 있는 불일치를 파악할 수도 있습니다.
+
+이메일 구독 및 캠페인 관리에 대해 자세히 알아보려면 [이메일 관련 모범 사례][2]를 확인하세요.
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트 2024년 5월 2일_
+
+[1]: {{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions
+[2]: {{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices
+[3]: {{site.baseurl}}/user_guide/administrative/app_settings/message_activity_log_tab/
diff --git a/_lang/ko/_help/help_articles/email/html_looks_strange.md b/_lang/ko/_help/help_articles/email/html_looks_strange.md
new file mode 100644
index 00000000000..0f21075d110
--- /dev/null
+++ b/_lang/ko/_help/help_articles/email/html_looks_strange.md
@@ -0,0 +1,44 @@
+---
+nav_title: 테스트 이메일에서 HTML 렌더링
+article_title: 테스트 이메일에서 HTML 렌더링
+page_order: 2
+
+page_type: solution
+description: "이 도움말 문서는 테스트 이메일에서 HTML 렌더링 문제를 해결하는 방법을 안내합니다."
+channel: email
+---
+
+# 테스트 이메일에서 HTML 렌더링 문제 해결
+
+[테스트 이메일][37]이 이상해 보이면 먼저 HTML 설정을 확인하는 것이 좋습니다. 다음으로, 이러한 문제를 확인할 수 있습니다:
+* [확장 충돌](#check-conflicts)
+* [이메일 렌더링](#check-rendering)
+* [CSS](#switch-css-inlining)
+
+### 확장 충돌
+
+일부 브라우저 확장 프로그램은 이메일 편집기에서 문제를 일으킬 수 있습니다. 한 가지 예는 [Grammarly][38])가 Google Chrome과 함께 사용될 때입니다. 이 확장 프로그램 중 하나를 사용 중인 경우 다음 중 하나를 수행해야 합니다. 
+- 브라우저 확장 프로그램으로 Grammarly가 없는 브라우저에서 Braze 이메일을 편집합니다
+- 귀하의 Braze 계정 매니저에게 연락하여 이메일 편집기를 HTML 전용 또는 일반 텍스트로 전환하도록 요청하십시오. 
+
+일반 텍스트 보기에서는 ```WYSIWYG``` (보이는 대로 편집) 편집기가 제거되므로, 이 요청을 하기 전에 모든 팀원이 HTML에 익숙한지 먼저 확인해야 합니다.
+
+### 이메일 렌더링
+
+이메일은 브라우저와 이메일 클라이언트에 따라 다르게 렌더링되므로, 문제가 발생하는 브라우저와 이메일 클라이언트를 주의 깊게 확인하세요.
+
+- [받은편지함 Vision]({{site.baseurl}}/user_guide/message_building_by_channel/email/inbox_vision/#inbox-vision/)을 사용하여 이메일을 미리 보고, 다양한 브라우저와 이메일 클라이언트에서 이메일이 어떻게 보이는지 확인하세요.
+- 어떤 브라우저나 이메일 클라이언트가 문제를 일으키는지 확인한 후, 개발자 팀에게 HTML을 수정하고 해당 브라우저나 이메일 클라이언트를 수용할 수 있도록 편집해야 한다고 알려주세요.
+
+### CSS
+
+받은편지함 비전의 미리보기가 여전히 Braze로 전송된 것과 일치하지 않는 경우가 있습니다. 이것은 Braze 및 기타 도구에 의해 수행되는 CSS 인라인 차이로 인해 발생할 수 있습니다. 이 경우라고 의심되면 Braze 계정 매니저에게 CSS 인라이닝을 끄도록 요청하세요.
+
+아직 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트 날짜: 2021년 12월 21일_
+
+[37]: {{site.baseurl}}/developer_guide/platform_wide/sending_test_messages/#sending-a-test-push-notification-or-in-app-messages-a-classmargin-fix-namepush-inapp-testa
+[38]: https://chrome.google.com/webstore/detail/grammarly-for-chrome/kbfnbcaeplbcioakkpcpgfkobkghlhen?hl=en
+[39]: https://www.emailonacid.com/
+[40]: https://litmus.com/
diff --git a/_lang/ko/_help/help_articles/email/open_rates.md b/_lang/ko/_help/help_articles/email/open_rates.md
new file mode 100644
index 00000000000..1ee83b2ca4d
--- /dev/null
+++ b/_lang/ko/_help/help_articles/email/open_rates.md
@@ -0,0 +1,24 @@
+---
+nav_title: 클릭률 증가 처리
+article_title: 클릭률 증가 처리
+page_order: 1
+
+page_type: solution
+description: "이 도움말 문서에서는 이메일 클릭률 증가를 처리하는 방법을 안내합니다."
+channel: email
+---
+
+# 클릭률 증가 처리
+
+오픈율은 이메일 캠페인에서 추적할 수 있는 통찰력 있는 지표가 될 수 있습니다. 하지만 이러한 오픈율이 반드시 이메일 캠페인에 대한 사람들의 참여를 정확하게 나타내는 지표는 아닙니다. 열람 이벤트는 사용자가 이메일을 열었을 때 발생하며, 이는 투명한 열람 추적 픽셀이 성공적으로 다운로드되었음을 의미합니다. 
+
+또한 보안 스캐닝 도구를 사용하면 오픈율이 부풀려질 수 있습니다. 이러한 도구 중 일부는 수신되는 이메일에서 악성 콘텐츠를 스캔하여 링크를 클릭하여 합법성을 확인함으로써 사용자를 보호합니다. 이러한 클릭을 흔히 "봇 클릭" 또는 "비인간 상호작용(NHI)"이라고 합니다. 
+
+궁극적으로 이메일이 서버를 떠난 후에는 다음에 어떤 일이 발생하는지 파악하기 어렵지만, 결과에 영향을 미치는 NHI를 관리하기 위한 권장 사항은 다음과 같습니다.
+
+1. 이는 발신자와 거의 모든 수신자에게 발생할 수 있다는 점에 유의하세요. 열기와 같은 클릭은 메시지와 사람의 상호 작용을 완전히 신뢰할 수 있는 지표가 아니므로 NHI를 방지할 수 없습니다.
+2. 긍정적인 인게이지먼트가 높을수록 NHI가 낮아지는 경향이 있으므로 이메일 메시징 [모범 사례]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices)를 따르는 것이 중요합니다. 여기에는 사용자로부터 이메일 전송에 대한 명시적인 권한을 받고 참여하지 않는 구독자를 정기적으로 일몰시키는 것이 포함됩니다. 
+3. 가능하면 이메일에 HTTPS 링크를 사용하세요. NHI는 보안 링크를 사용하는 발신자에게는 덜 일반적입니다.
+4. 현재 원클릭 수신 거부 프로세스를 사용하고 있다면 사용자가 알림 환경설정을 편집하고 관리할 수 있는 페이지로 이동하는 [환경설정 센터를]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center/overview) 만드는 것이 좋습니다. 이는 NHI가 실수로 사용자의 구독을 취소할 수 있기 때문에 유용할 수 있습니다.
+5. 전환, 앱 세션 또는 사이트 방문과 같은 [다른 측정기준]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/email_reporting/#email-performance)을 사용하여 이메일 마케팅의 성공 여부를 측정하는 것도 고려해 보세요.
+6. 이메일 캠페인에 숨겨진 링크를 추가하세요. 이 링크는 흰색 위에 흰색 텍스트나 구두점처럼 사람이 알아차리지 못할 것입니다. 봇은 모든 링크를 클릭하는 경향이 있으므로 보이지 않는 링크에서 클릭 이벤트를 생성하는 사용자가 실제로는 NHI의 결과라고 결론 내릴 수 있으므로 열기 또는 클릭이 반드시 긍정적인 참여를 의미하지는 않습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/email/universal_links.md b/_lang/ko/_help/help_articles/email/universal_links.md
new file mode 100644
index 00000000000..123f9dc9718
--- /dev/null
+++ b/_lang/ko/_help/help_articles/email/universal_links.md
@@ -0,0 +1,284 @@
+---
+nav_title: 유니버설 링크 및 앱 링크
+article_title: 유니버설 링크 및 앱 링크
+page_order: 1
+page_type: solution
+description: "이 도움말에서는 Apple 유니버설 링크 및 Android 앱 링크 설정 방법을 안내합니다."
+channel: email
+---
+
+# 유니버설 링크 및 앱 링크
+
+Apple 유니버설 링크와 Android 앱 링크는 웹 콘텐츠와 모바일 앱 간의 원활한 전환을 제공하기 위해 고안된 메커니즘입니다. 보편적 링크는 iOS에만 해당되지만, Android 앱 링크는 Android 애플리케이션에 동일한 목적을 제공합니다.
+
+## 유니버설 링크 및 앱 링크의 작동 방식
+
+유니버설 링크(iOS) 및 앱 링크(Android)는 웹 페이지와 앱 내의 콘텐츠를 모두 가리키는 표준 웹 링크(`http://mydomain.com`)입니다.
+
+유니버셜 링크 또는 앱 링크가 열리면 운영 체제가 설치된 앱이 해당 도메인에 등록되어 있는지 확인합니다. 앱이 발견되면 웹 페이지를 로드하지 않고 즉시 실행됩니다. 앱이 발견되지 않으면 사용자의 기본 웹 브라우저에서 웹 URL이 로드되며, 이는 각각 App Store 또는 Google Play Store로 리디렉션되도록 구성될 수도 있습니다.
+
+명백히, 유니버설 링크는 웹사이트가 특정 앱 화면과 웹 페이지를 연결할 수 있게 하여 사용자가 앱 화면에 해당하는 웹 페이지 링크를 클릭하면 앱이 직접 열리도록 합니다 (앱이 현재 설치되어 있는 경우).
+
+이 표는 유니버설 링크와 전통적인 딥 링크 간의 주요 차이점을 설명합니다:
+
+|                        | 유니버설 링크 및 앱 링크                                  | 딥링크                   |
+| ---------------------- | -------------------------------------------------------------- | ---------------------------- |
+| 플랫폼 호환성 | iOS (버전 9 이상) 및 Android (버전 6.0 이상)  | 다양한 모바일 운영 체제에서 사용    |
+| 목적                | iOS 및 Android 기기에서 웹 및 앱 콘텐츠를 원활하게 연결 | 특정 앱 콘텐츠로 연결 |
+| 기능               | 문맥에 따라 웹 페이지 또는 앱 콘텐츠로 이동합니다           | 특정 앱 화면을 엽니다   |
+| 앱 설치       | 앱이 설치되어 있으면 앱을 열고, 그렇지 않으면 웹 콘텐츠를 엽니다 | 앱 설치가 필요합니다 |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3}
+
+## 사용 사례
+
+유니버설 링크와 앱 링크는 이메일 캠페인에 가장 많이 사용됩니다. 이메일은 데스크탑과 모바일 장치 모두에서 열리고 클릭될 수 있기 때문입니다.
+
+일부 채널은 이러한 링크와 잘 작동하지 않습니다. 예를 들어, 푸시 알림, 인앱 메시지 및 콘텐츠 카드에는 스킴 기반의 딥링크를 사용해야 합니다(`mydomain://`).
+
+{% alert note %}
+Android 앱 링크에는 다른 웹 URL과 별도로 도메인의 링크를 처리하는 로직이 포함된 커스텀 `IBrazeDeeplinkHandler`가 필요합니다. 대신 딥링크를 사용하는 것이 더 쉬울 수 있으며 이메일 이외의 채널에 대한 링크 관행을 일관되게 유지할 수 있습니다.
+{% endalert %}
+
+## 필수 조건
+
+유니버설 링크 및 앱 링크를 사용하려면:
+
+- 귀하의 웹사이트는 HTTPS를 통해 액세스할 수 있어야 합니다
+- 귀하의 앱은 App Store(iOS) 또는 Google Play Store(Android)에서 사용할 수 있어야 합니다
+
+## 유니버설 링크 및 앱 링크 설정
+
+앱이 유니버설 링크 또는 앱 링크를 지원하려면 iOS와 Android 모두 링크 도메인에 호스팅되는 특수 권한 파일이 필요합니다. 이 파일에는 해당 도메인에서 링크를 열 수 있는 앱과 iOS에서 이러한 앱이 열 수 있는 경로에 대한 정의가 포함되어 있습니다:
+
+- **iOS:** Apple 앱 Site Association (AASA) file
+- **Android:** 디지털 자산 링크 파일
+
+이 권한 파일 외에도 앱 내에서 설정된 앱이 열 수 있는 링크 도메인의 하드코딩된 정의가 있습니다.
+
+- **iOS:** Xcode에서 "연관 도메인"으로 설정
+- **Android:** 앱의 `AndroidManifest.xml` 파일에 정의됨
+
+이 두 부분으로 구성된 도메인-앱 연관은 유니버설 링크 또는 앱 링크가 작동하기 위해 필요하며 특정 도메인에서 링크를 가로채거나 특정 앱을 여는 것을 방지합니다.
+
+{% tabs %}
+<!--iOS instructions-->
+{% tab iOS %}
+
+이 단계는 Apple 개발자 설명서에서 가져온 것입니다. 자세한 내용은 [앱과 웹사이트가 귀하의 콘텐츠에 연결되도록 허용하기](https://developer.apple.com/documentation/xcode/allowing-apps-and-websites-to-link-to-your-content?language=objc)를 참조하십시오.
+
+### 1단계: 앱 권한을 구성합니다
+
+{% alert note %}
+[Xcode 13 및 이후 버전에서](https://developer.apple.com/help/account/reference/provisioning-with-managed-capabilities/), Xcode는 권한 프로비저닝을 자동으로 처리할 수 있습니다. 문제가 발생하면 [1c 단계](#step-1c)로 건너뛰고 이 지침을 참조할 수 있습니다.
+{% endalert %}
+
+#### 1단계 a: 앱 을 등록합니다{#step-1a}
+
+1. developer.apple.com으로 이동하고 로그인하세요.
+2. **인증서, 식별자 및 프로필**을 클릭합니다.
+3. **식별자**를 클릭합니다.
+4. 앱 식별자가 아직 등록되지 않은 경우 +를 클릭하여 하나를 만듭니다.
+   a. **이름**을 입력하세요. 원하는 아무 이름을 사용할 수 있습니다.
+   b. **번들 ID**를 입력하세요. Xcode 프로젝트의 **일반** 탭에서 번들 ID를 찾아 올바른 구축 대상을 설정할 수 있습니다.
+
+#### 1b단계: 앱 식별자에서 연결된 도메인을 켜십시오
+
+1. 기존 또는 새로 생성한 앱 식별자에서 **앱 서비스** 섹션을 찾으십시오.
+2. **연관된 도메인**을 선택하십시오.
+3. **저장**을 클릭합니다.
+
+![]({% image_buster /assets/img_archive/universal_links_1b.png %}){: style="max-width:75%;"}
+
+#### 1단계 c: Xcode 프로젝트에서 연결된 도메인을 켭니다 {#step-1c}
+
+진행하기 전에 Xcode 프로젝트에서 방금 등록한 앱 식별자와 동일한 팀이 선택되어 있는지 확인하세요. 
+
+1. Xcode에서 프로젝트 파일의 **Capabilities** 탭으로 이동합니다.
+2. **연관된 도메인**을 켜십시오.
+
+##### 문제 해결 팁
+
+다음 오류가 발생하면 "'your-app-id' 식별자를 가진 앱 ID를 사용할 수 없습니다. 다른 문자열을 입력하십시오", 다음을 수행하십시오:
+
+1. 선택한 팀이 올바른지 확인하십시오.
+2. Xcode 프로젝트의 번들 ID([step 1a](#step-1a))가 앱 식별자를 등록하는 데 사용된 것과 일치하는지 확인합니다.
+
+#### 1단계 d: 도메인 자격 추가
+
+도메인 섹션에서 적절한 도메인 태그를 추가하십시오. `applinks:`로 시작해야 합니다. 이 경우, 우리는 `applinks:yourdomain.com`을 추가한 것을 볼 수 있습니다.
+
+![]({% image_buster /assets/img_archive/universal_links_1d.png %})
+
+#### 1단계 e: 구축 시 권한 파일이 포함되어 있는지 확인하세요
+
+프로젝트 브라우저에서 새 사용 권한 파일이 **대상 멤버십**에 선택되어 있는지 확인하세요.
+
+Xcode는 이를 자동으로 처리해야 합니다.
+
+### 2단계: 웹사이트를 구성하여 AASA 파일을 호스팅하십시오
+
+iOS에서 네이티브 앱과 웹사이트 도메인을 연결하려면 Apple 앱 사이트 연결(AASA) 파일을 웹사이트에 호스팅해야 합니다. 이 파일은 iOS에 도메인 소유권을 확인하는 안전한 방법으로 사용됩니다. iOS 9 이전에는 개발자가 검증 없이 앱을 열기 위해 임의의 URI 스킴을 등록할 수 있었습니다. 그러나 AASA를 통해 이 과정은 훨씬 더 안전하고 신뢰할 수 있게 되었습니다.
+
+AASA 파일에는 도메인에서 보편적 링크로 포함되거나 제외되어야 하는 앱 목록과 URL 경로가 포함된 JSON 객체가 포함되어 있습니다. 다음은 샘플 AASA 파일입니다:
+
+```json
+{
+  "applinks": {
+    "apps": [],
+    "details": [
+      {
+        "appID": “JHGFJHHYX.com.facebook.ios",
+        "paths": [
+          "*"
+        ]
+      }
+    ]
+  }
+}
+```
+
+- `appID`: 앱의 **팀 ID** (팀 ID를 얻으려면 `https://developer.apple.com/account/#/membership/`로 이동) 및 **번들 식별자**를 결합하여 빌드되었습니다. 위의 예에서 "JHGFJHHYX"는 팀 ID이고, "com.facebook.ios"는 번들 ID입니다.
+- `paths`: 포함되거나 제외되는 경로를 지정하는 문자열 배열. 경로를 비활성화하려면 경로 앞에 `NOT`을 사용할 수 있습니다. 이 예제에서는 이 경로의 모든 링크가 앱을 여는 대신 웹으로 이동합니다. 디렉토리의 모든 경로를 활성화하려면 `*`를 와일드카드로 사용할 수 있으며, 단일 문자를 일치시키려면 `?`를 사용할 수 있습니다 (예: /archives/201?/는 2010년부터 2019년까지의 모든 숫자와 일치합니다).
+
+{% alert note %}
+이 문자열들은 대소문자를 구분하며 쿼리 문자열과 프래그먼트 식별자는 무시됩니다.
+{% endalert %}
+
+### 3단계: 도메인에 AASA 파일을 호스팅하십시오
+
+AASA 파일을 준비하면 `https://<<yourdomain>>/apple-app-site-association` 또는 `https://<<yourdomain>>/.well-known/apple-app-site-association`에서 도메인에 호스팅할 수 있습니다.
+
+HTTPS 웹 서버에 `apple-app-site-association` 파일을 업로드하십시오. 파일을 서버의 루트 또는 `.well-known` 하위 디렉토리에 배치할 수 있습니다. 파일 이름에 `.json`을 추가하지 마십시오.
+
+{% alert important %}
+iOS는 안전한 연결(HTTPS)을 통해서만 AASA 파일을 가져오려고 시도할 것입니다.
+{% endalert %}
+
+AASA 파일을 호스팅하는 동안 파일이 다음 지침을 따르는지 확인하세요.
+
+- HTTPS를 통해 제공됩니다.
+- `application/json` MIME 유형을 사용합니다.
+- 128KB를 초과하지 않습니다(iOS 9.3.1 이상에서 요구됨)
+
+### 4단계: 앱이 범용 링크를 처리할 수 있도록 준비하십시오
+
+사용자가 iOS 기기에서 범용 링크를 탭하면, 기기가 앱을 실행하고 [NSUserActivity](https://developer.apple.com/documentation/foundation/nsuseractivity) 객체를 보냅니다. 그 앱은 NSUserActivity 오브젝트를 쿼리하여 어떻게 실행되었는지 확인할 수 있습니다.
+
+앱에서 유니버설 링크를 지원하려면 다음 단계를 따르세요:
+
+1. 앱이 지원하는 도메인을 지정하는 권한을 추가합니다.
+2. NSUserActivity 오브젝트를 받을 때 적절하게 응답하도록 앱 대리자를 업데이트하세요.
+
+Xcode에서 **연관된 도메인** 섹션을 **기능** 탭에서 열고, 앱이 지원하는 각 도메인에 대해 `applinks:`로 시작하는 항목을 추가합니다. 예를 들어, `applinks:www.mywebsite.com`.
+
+{% alert note %}
+Apple은 이 목록을 20~30개 도메인으로 제한할 것을 권장합니다.
+{% endalert %}
+
+### 5단계: 보편적 링크를 테스트하세요
+
+이메일에 유니버설 링크를 추가하고 테스트 기기로 보내세요. Safari URL 필드에 유니버설 링크를 직접 붙여넣어도 앱이 자동으로 열리지 않습니다. 이 작업을 수행하면 웹사이트를 수동으로 내려서 해당 앱을 열라는 메시지가 상단에 나타나도록 해야 합니다.
+
+{% endtab %}
+
+<!--Android instructions-->
+{% tab Android %}
+
+이 단계는 Android 개발자 설명서에서 가져온 것입니다. 자세한 내용은 [Android 앱 링크 추가](https://developer.android.com/training/app-links#add-app-links) 및 [앱 콘텐츠에 대한 딥 링크 생성](https://developer.android.com/training/app-links/deep-linking)을 참조하세요.
+
+{% alert note %}
+Android 앱 링크에는 다른 웹 URL과 별도로 도메인의 링크를 처리하는 로직이 포함된 커스텀 `IBrazeDeeplinkHandler`가 필요합니다. 대신 딥링크를 사용하는 것이 더 쉬울 수 있으며 이메일 이외의 채널에 대한 링크 관행을 일관되게 유지할 수 있습니다.
+{% endalert %}
+
+### 1단계: 딥 링크 생성
+
+먼저, Android 앱에 대한 딥링크를 생성해야 합니다. 이것은 `AndroidManifest.xml` 파일에 [의도 필터](https://developer.android.com/guide/components/intents-filters)를 추가하여 수행할 수 있습니다. 의도 필터는 `VIEW` 작업 및 `BROWSABLE` 카테고리를 포함해야 하며, 데이터 요소에 웹사이트의 URL을 포함해야 합니다.
+
+### 2단계: 앱을 웹사이트와 연결하세요
+
+귀하의 앱을 웹사이트와 연결해야 합니다. 이는 디지털 자산 링크 파일을 생성하여 수행할 수 있습니다. 이 파일은 JSON 형식이어야 하며, 귀하의 웹사이트로 연결되는 링크를 열 수 있는 Android 앱에 대한 세부 정보를 포함합니다. 귀하의 웹사이트 `.well-known` 디렉토리에 배치해야 합니다.
+
+### 3단계: 앱 매니페스트 파일을 업데이트하세요
+
+귀하의 `AndroidManifest.xml` 파일에서 애플리케이션 요소 내에 메타 데이터 요소를 추가하십시오. 메타데이터 요소에는 "asset_statements"의 `android:name` 속성이 있어야 하며, 문자열 배열이 포함된 리소스 파일을 가리키는 `android:resource` 속성이 있어야 합니다.
+
+### 4단계: 앱이 딥 링크를 처리할 수 있도록 준비하십시오
+
+Android 앱에서 들어오는 딥 링크를 처리해야 합니다. 활동을 시작한 의도를 얻고 거기에서 데이터를 추출하여 이 작업을 수행할 수 있습니다.
+
+### 5단계: 딥링크 테스트
+
+마침내, 딥링크를 테스트할 수 있습니다. 메시징 앱 또는 이메일을 통해 링크를 자신에게 보내고 클릭하세요. 모든 설정이 올바르게 되어 있으면 앱이 열릴 것입니다.
+
+{% endtab %}
+{% endtabs %}
+
+## 유니버설 링크, 앱 링크, 및 클릭-추적
+
+{% alert note %}
+클릭-추적 링크는 일반적으로 이메일 온보딩의 일부로 설정됩니다. 고객 온보딩 중에 완료되지 않은 경우 계정 매니저에게 도움을 요청하세요.
+{% endalert %}
+
+우리의 이메일 발송 파트너인 SendGrid와 SparkPost는 모든 링크를 래핑하고 Braze 이메일에서 클릭 추적을 위해 URL 매개변수를 포함하기 위해 클릭 추적 도메인을 사용합니다.
+
+예를 들어, `https://www.example.com` 같은 링크는 `https://links.email.example.com/uni/wf/click?upn=abcdef123456…`과 같은 것이 됩니다.
+
+이메일 링크가 클릭 추적과 함께 유니버설 링크 또는 앱 링크로 작동하도록 하려면 추가 설정이 필요합니다. 앱이 열 수 있도록 허용된 도메인으로 클릭-추적 도메인(`links.email.example.com`)을 추가하세요. 게다가, 클릭-추적 도메인은 AASA (iOS) 또는 Digital 자산 Links(Android) 파일을 제공해야 합니다. 이것은 이메일 링크가 클릭-추적과 원활하게 작동하도록 도와줍니다.
+
+모든 클릭-추적 링크가 유니버설 링크 또는 앱 링크가 되지 않도록 하려면, 이메일 발송 파트너를 기준으로 어떤 링크가 유니버설 링크가 되어야 하는지 지정할 수 있습니다. 다음 섹션을 참조하세요.
+
+### SendGrid
+
+SendGrid 클릭-추적 링크를 범용 링크로 취급하려면:
+
+1. AASA 또는 AndroidManifest pathPrefix 값을 설정하여 URL 경로에 `/uni/`이 포함된 링크만 범용 링크로 처리하도록 하십시오.
+2. 링크의 앵커 태그(`<a>`)에 속성 `universal="true"`를 추가하세요. 이것은 래핑된 링크의 URL 경로가 `/uni/`를 포함하도록 변경합니다.
+
+{% alert note %}
+AMP 이메일의 경우 이 속성은 data-universal="true"이어야 합니다.
+{% endalert %}
+
+예를 들어, 다음과 같습니다.
+
+```html
+<a href=”https://www.example.com” universal="true">
+```
+
+{:start="3"}
+3\. 앱이 래핑된 링크를 올바르게 처리하도록 설정되어 있는지 확인하세요. SendGrid의 [SendGrid 클릭 추적 링크 해결](https://docs.sendgrid.com/ui/sending-email/universal-links#resolving-sendgrid-click-tracking-links)에 관한 기사를 참고하고 운영 체제에 맞는 단계를 따르세요. 이 기사에는 [iOS](https://docs.sendgrid.com/ui/sending-email/universal-links#resolving-links-in-ios) 및 [Android](https://docs.sendgrid.com/ui/sending-email/universal-links#resolving-links-in-android)에 대한 예제 코드가 포함되어 있습니다.
+
+이 구성으로 `/uni/` URL 경로가 있는 링크는 유니버셜 링크로 작동하며, 다른 모든 링크는 웹 링크로 작동합니다.
+
+### SparkPost
+
+SparkPost 클릭 추적 링크를 범용 링크로 처리하려면 이메일의 드래그 앤 드롭 편집기의 속성 섹션에 다음 속성을 추가하거나 링크 HTML을 수동으로 편집하여 링크의 앵커 태그에 다음 속성을 포함하십시오: `data-msys-sublink="custom_path"`.
+
+이 커스텀 경로를 사용하면 해당 값을 가진 URL을 범용 링크로 선택적으로 처리할 수 있습니다.
+
+예를 들어, 다음과 같습니다.
+
+```html
+<a href=”https://www.example.com” data-msys-sublink="open-in-app">
+```
+
+그런 다음, 앱이 커스텀 경로를 올바르게 처리하도록 설정되어 있는지 확인하세요. SparkPost의 [딥링크에서 SparkPost 클릭 추적 사용](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve#preferred-solution-using-sparkpost-click-tracking-on-deep-links)에 관한 기사를 참조하세요. 이 문서에는 [iOS](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve#ios-swift-forwarding-clicks-to-sparkpost) 및 [Android](https://support.sparkpost.com/docs/tech-resources/deep-links-self-serve#forwarding-clicks-from-android-to-sparkpost)에 대한 예제 코드가 포함되어 있습니다.
+
+### 클릭-추적으로 유니버셜 링크 문제 해결
+
+이메일에서 유니버셜 링크가 예상대로 작동하지 않는 경우, 예를 들어 수신자를 이메일 앱에서 웹 브라우저로 이동한 후 최종적으로 앱으로 리디렉션하는 경우, 유니버셜 링크 설정 문제를 해결하기 위한 다음 팁을 참조하세요.
+
+#### 링크 파일 위치 확인
+
+AASA 파일(iOS) 또는 Digital Asset Links 파일(Android)이 올바른 위치에 있는지 확인하십시오:
+
+- **iOS:** `https://click.tracking.domain/.well-known/apple-app-site-association`
+- **Android:** `https://click.tracking.domain/.well-known/assetlinks.json`
+
+이 파일들이 항상 공개적으로 접근 가능하도록 하는 것이 중요합니다. 액세스할 수 없는 경우 이메일에 대한 유니버셜 링크 설정에서 단계를 놓쳤을 수 있습니다.
+
+#### 도메인 정의 확인
+
+도메인이 앱에서 열 수 있도록 허용된 정의가 올바른지 확인하세요.
+
+- **iOS:** Xcode에서 앱([1단계 c]({{site.baseurl}}/help/help_articles/email/universal_links/?tab=ios#step-1c))에 대한 관련 도메인 설정을 검토하세요. 해당 목록에 클릭 추적 도메인이 포함되어 있는지 확인하십시오.
+- **Android:** 앱 정보 페이지를 여세요 (앱 아이콘을 길게 누르고 ⓘ를 클릭하세요). 앱 정보 메뉴에서 **기본값으로 열기**를 찾아 탭하세요. 이것은 앱이 열 수 있도록 허용된 모든 검증된 링크가 있는 화면을 표시해야 합니다. 해당 목록에 클릭 추적 도메인이 포함되어 있는지 확인하십시오.
diff --git a/_lang/ko/_help/help_articles/in-app_messages.md b/_lang/ko/_help/help_articles/in-app_messages.md
new file mode 100644
index 00000000000..c852270334b
--- /dev/null
+++ b/_lang/ko/_help/help_articles/in-app_messages.md
@@ -0,0 +1,22 @@
+---
+page_order: 4
+nav_title: 인앱 메시지
+layout: dev_guide
+guide_top_header: "인앱 메시지 도움말 문서"
+guide_top_text: "다음 도움말 문서에서는 인앱 메시지와 관련된 일반적인 문제에 대한 문제 해결 정보를 제공합니다."
+
+page_type: landing
+description: "이 랜딩 페이지에서는 인앱 메시지와 관련된 일반적인 문제에 대한 도움말 문서를 확인할 수 있습니다."
+channel: in-app messages
+noindex: true
+guide_menu_title: ""
+guide_menu_list:
+  - name: 낮은 인앱 메시지 노출 수
+    link: /docs/help/help_articles/in-app_messages/in-app_message_impressions_appear_lower_than_expected/
+    image: /assets/img/braze_icons/eye.svg
+  - name: 인앱 메시지가 표시되지 않음
+    link: /docs/help/help_articles/in-app_messages/in-app_messages_not_displaying/
+    image: /assets/img/braze_icons/message-x-circle.svg
+
+
+---
diff --git a/_lang/ko/_help/help_articles/in-app_messages/in-app_messages_not_displaying.md b/_lang/ko/_help/help_articles/in-app_messages/in-app_messages_not_displaying.md
new file mode 100644
index 00000000000..c6eecd1c1e6
--- /dev/null
+++ b/_lang/ko/_help/help_articles/in-app_messages/in-app_messages_not_displaying.md
@@ -0,0 +1,70 @@
+---
+nav_title: 인앱 메시지가 표시되지 않음
+article_title: 인앱 메시지가 표시되지 않음
+page_order: 1
+
+page_type: solution
+description: "이 도움말 문서에서는 인앱 메시지가 제대로 표시되지 않거나 렌더링되지 않는 문제 해결 방법을 안내합니다."
+channel: in-app messages
+---
+
+# 인앱 메시지가 표시되지 않음
+
+인앱 메시지가 제대로 표시되지 않거나 렌더링되지 않는 경우 여러 가지 방법으로 확인할 수 있습니다:
+
+* [이벤트 트리거](#event-triggers)
+* [메시지 노출 횟수](#message-impressions)
+* [테스트](#run-tests)
+* [세션 시간 초과](#session-timeout)
+* [메시징 간격](#minimum-interval)
+
+## 이벤트 트리거
+
+캠페인이 세션 시작 또는 사용자 지정 이벤트에 의해 트리거되는 경우, 이 이벤트 또는 세션이 메시지를 트리거할 수 있을 만큼 자주 발생하는지 확인해야 합니다. 이 데이터는 [개요][1] (세션 데이터의 경우) 또는 [사용자 지정 이벤트][2] 페이지에서 확인할 수 있습니다:
+
+![한 달 동안 즐겨찾기에 추가된 커스텀 이벤트가 발생한 횟수를 그래프로 보여주는 커스텀 이벤트 페이지][14]
+
+## 메시지 노출 횟수
+
+SDK 내에서 인앱 메시지 UI 또는 전달 메커니즘을 커스텀하려면 개발자가 인앱 메시지 노출 횟수를 수동으로 기록하는 방법을 활용해야 할 수 있습니다. 인앱 메시지 사용자 지정을 사용하는지 개발자에게 문의하세요.
+
+## 테스트 실행
+
+트리거 이벤트가 발생하지 않거나 메시지 자체가 표시되지 않는지 확인하는 것이 중요합니다. 테스트하려면 다른 작업(세션 시작 또는 다른 커스텀 이벤트 등)을 사용하여 메시지를 트리거하고 표시되는지 확인합니다. 이렇게 하면 데이터 문제일 가능성이 있는 경우 이를 격리하는 데 도움이 됩니다.
+
+또는 다른 유형의 인앱 메시지 템플릿이나 이미지 크기를 사용해 보세요. 반드시 준수해야 하는 \[인앱 메시지 사양][15]이 있습니다. 간혹 이미지가 너무 크면 인앱 메시지가 표시되지 않는 경우가 있습니다.
+
+## 세션 시간 초과
+
+세션 시간 초과를 사용자 지정했는지 확인하세요. 기본적으로 Braze는 세션이 시작될 때 서버에서 인앱 메시지를 검색합니다.
+
+세션 시간 초과가 연장되면 귀하가 받을 수 있는 잠재적인 인앱 메시지를 새로고침할 수 있는 기간이 연장됩니다. 또한 캠페인이 세션 시작 시 트리거되도록 설정된 경우 새 세션을 등록하려면 적절한 시간이 경과했는지 확인해야 합니다. 예를 들어 세션 시간 초과를 30초로 사용자 지정했을 수 있습니다. 30초 이내에 앱을 열었다가 닫으면 세션 시작 시 트리거되는 다른 인앱 메시지를 받을 수 없습니다. 
+
+다음 플랫폼의 세션 시간 초과를 사용자 지정하는 방법에 대해 자세히 알아보세요:
+* \[iOS][16]
+* \[Android][17]
+* \[웹][18]
+
+## 최소 간격
+
+인앱 메시지가 연속적으로 트리거되도록 허용하는 최소 간격이 있으므로 너무 빨리 트리거하려고 할 수 있습니다. 다음 플랫폼의 최소 간격에 대해 자세히 알아보세요: 
+* \[iOS][19]
+* \[Android][20]
+* \[웹][21]
+
+간격은 사용자 지정할 수 있지만, 사용자에게 과도한 메시지가 전송되는 것을 방지하기 위해 간격을 설정할 수 있습니다.
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트: 2021년 7월 15일_
+
+[1]: {{site.baseurl}}/user_guide/data_and_analytics/analytics/understanding_your_app_usage_data/#understanding-your-app-usage-data
+[2]: {{site.baseurl}}/user_guide/data_and_analytics/configuring_reporting/#configuring-reporting
+[14]: {% image_buster /assets/img_archive/trouble5.png %}
+[15]: {{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/creative_details/
+[16]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/tracking_sessions/
+[17]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/analytics/tracking_sessions/#customizing-session-timeout
+[18]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/analytics/tracking_sessions/#customizing-session-timeout
+[19]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers
+[20]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/in-app_message_delivery/#minimum-time-interval-between-triggers
+[21]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/in-app_messaging/in-app_message_delivery/#in-app-message-delivery
diff --git a/_lang/ko/_help/help_articles/overview.md b/_lang/ko/_help/help_articles/overview.md
new file mode 100644
index 00000000000..f1c0b4b9024
--- /dev/null
+++ b/_lang/ko/_help/help_articles/overview.md
@@ -0,0 +1,5 @@
+---
+layout: redirect
+redirect_to: /docs/help/help_articles/
+hidden: true
+---
diff --git a/_lang/ko/_help/help_articles/push.md b/_lang/ko/_help/help_articles/push.md
new file mode 100644
index 00000000000..4d4b7603763
--- /dev/null
+++ b/_lang/ko/_help/help_articles/push.md
@@ -0,0 +1,33 @@
+---
+page_order: 5
+nav_title: 푸시
+layout: dev_guide
+guide_top_header: "푸시 도움말 문서"
+guide_top_text: "다음 도움말 기사를 확인하여 푸시 메시지의 일반적인 문제 해결에 대한 지원을 받으세요."
+
+page_type: landing
+description: "이 랜딩 페이지는 푸시 메시지와 관련된 일반적인 문제에 대한 도움말 기사를 제공합니다."
+channel: push
+noindex: true
+guide_menu_title: ""
+guide_menu_list:
+  - name: 일반적인 푸시 오류 메시지
+    link: /docs/help/help_articles/push/push_error_codes/
+    image: /assets/img/braze_icons/alert-circle.svg
+  - name: 푸시 인에이블먼트 정의
+    link: /docs/help/help_articles/push/defining_push_enablement/
+    image: /assets/img/braze_icons/book-closed.svg
+  - name: 푸시 알림 누락
+    link: /docs/help/help_articles/push/no_push_notification_was_received/
+    image: /assets/img/braze_icons/message-x-circle.svg
+  - name: 푸시 토큰 마이그레이션
+    link: /docs/help/help_articles/push/push_token_migration/
+    image: /assets/img/braze_icons/map-01.svg
+  - name: 푸시 권한 재설정
+    link: /docs/help/help_articles/push/resetting_push_permissions/
+    image: /assets/img/braze_icons/check-circle.svg
+  - name: 푸시 수신 거부 추적
+    link: /docs/help/help_articles/push/push_unsubscribes/
+    image: /assets/img/braze_icons/users-01.svg
+
+---
diff --git a/_lang/ko/_help/help_articles/push/no_push_notification_was_received.md b/_lang/ko/_help/help_articles/push/no_push_notification_was_received.md
new file mode 100644
index 00000000000..7417d8417b6
--- /dev/null
+++ b/_lang/ko/_help/help_articles/push/no_push_notification_was_received.md
@@ -0,0 +1,82 @@
+---
+nav_title: 누락된 푸시 알림
+article_title: 누락된 푸시 알림
+page_order: 3
+
+page_type: solution
+description: "이 도움말 문서에서는 사용자가 푸시 알림을 받지 못하는 경우 수행할 수 있는 문제 해결 단계를 안내합니다."
+channel: push
+---
+# 누락된 푸시 알림
+
+푸시 알림으로 인해 전달에 어려움을 겪고 계신가요? 이 문제를 해결하기 위해 취할 수 있는 여러 단계가 있습니다.
+
+* [푸시 구독 상태](#push-subscription-status)
+* [세그먼트](#segment)
+* [푸시 알림 캡](#push-notification-caps)
+* [요금 제한](#rate-limits)
+* [대조군 상태](#control-group-status)
+
+### 푸시 구독 상태
+
+**사용자 프로필** 섹션의 [참여][1] 탭에서 **사용자** 프로필을 확인하여 테스트 중인 워크스페이스에 대해 푸시 등록이 되어 있는지 확인하세요. 여러 앱에 등록되어 있는 경우 **푸시 등록 대상** 필드에 해당 앱이 나열됩니다:
+
+![푸시 등록 대상][2]
+
+Braze 내보내기 엔드포인트를 사용하여 사용자 프로필을 내보낼 수도 있습니다:
+- \[식별자별 사용자][12]
+- \[세그먼트별 사용자][13]
+
+두 엔드포인트 모두 기기별 푸시 인에이블먼트 정보가 포함된 푸시 토큰 객체를 반환합니다.
+
+### 세그먼트
+
+타겟팅하는 세그먼트에 속하는지 확인하세요(테스트가 아닌 라이브 캠페인인 경우). **고객 프로필**에 사용자가 현재 속해 있는 세그먼트 목록이 표시됩니다. 세분화는 실시간으로 업데이트되므로 계속 변화하는 변수라는 점을 기억하세요.
+
+![세그먼트 목록][3]
+
+### 푸시 알림 캡
+
+글로벌 주파수 한도를 확인하세요. 워크스페이스에 글로벌 최대 게재빈도 설정이 적용되어 있고 지정된 기간 동안 푸시 알림 한도에 이미 도달했기 때문에 푸시 알림을 받지 못했을 수 있습니다.
+
+대시보드에서 \[글로벌 최대 게재빈도 설정][4]을 확인하여 이 작업을 수행할 수 있습니다. 캠페인이 빈도 제한 규칙을 준수하도록 설정된 경우, 이러한 설정의 영향을 받는 사용자가 다수 발생할 수 있습니다.
+
+![캠페인 세부 정보][5]
+
+### 요금 제한
+
+캠페인 또는 캔버스에 사용량 제한이 설정되어 있는 경우 이 한도를 초과하여 메시징 수신이 중단될 수 있습니다. 자세한 내용은 \[요금 제한][9]]을 참조하세요.
+
+### 제어 그룹 상태
+
+단일 채널 캠페인이거나 캔버스에 대조 그룹이 있는 경우 대조 그룹에 속할 수 있습니다.
+
+  1. 대조군이 있는지 확인하려면 \[배리언트 배포][6]]를 확인하세요.
+  2. 그렇다면 \[캠페인 대조군][7]에 \[세그먼트 내보내기]에 대한 세그먼트 필터링을 생성하고 사용자 ID가 이 목록에 있는지 확인합니다.
+
+### 유효한 푸시 토큰
+푸시 토큰은 발신자가 푸시 알림으로 특정 기기를 타겟팅할 때 사용하는 식별자입니다. 따라서 기기에 유효한 푸시 토큰이 없는 경우 푸시 알림을 보낼 방법이 없습니다. 
+
+### 푸시 알림 유형
+
+올바른 유형의 푸시 알림을 사용하고 있는지 확인하세요. 예를 들어, FireTV를 타겟팅하려는 경우 Android 푸시 캠페인이 아닌 Kindle 푸시 알림을 사용합니다. Braze 워크플로우를 이해하는 방법에 대한 자세한 내용은 다음 문서를 참조하세요.
+- \[Apple 푸시 알림][10]
+- \[Firebase Cloud Messaging][11]
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을(를) 여세요.
+
+_마지막 업데이트: 2021년 1월 21일_
+
+[1]: {{site.baseurl}}/user_guide/engagement_tools/segments/using_user_search/#engagement-tab
+[2]: {% image_buster /assets/img_archive/trouble1.png %}
+[3]: {% image_buster /assets/img_archive/trouble2.png %}
+[4]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#freq-cap-feat-over
+[5]: {% image_buster /assets/img_archive/trouble3.png %}
+[6]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/multivariate_testing/#step-5-distribute-users-among-your-variants
+[7]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/retargeting_campaigns/#in-campaign-control-group-filter
+[8]: {{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/segment_data_to_csv/#exporting-to-csv
+[9]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#rate-limiting
+[10]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/troubleshooting/
+[11]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/troubleshooting
+[12]: {{site.baseurl}}/api/endpoints/export/user_data/post_users_identifier
+[13]: {{site.baseurl}}/api/endpoints/export/user_data/post_users_segment
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/push/push_enablement.md b/_lang/ko/_help/help_articles/push/push_enablement.md
new file mode 100644
index 00000000000..da5f69025eb
--- /dev/null
+++ b/_lang/ko/_help/help_articles/push/push_enablement.md
@@ -0,0 +1,25 @@
+---
+nav_title: 푸시 활성화 정의
+article_title: 푸시 활성화 정의
+page_order: 1
+
+page_type: solution
+description: "이 도움말 문서에서는 사용자의 푸시 인에이블먼트 상태를 설명하는 데 사용되는 두 가지 기본 용어를 정의합니다."
+channel: push
+---
+
+# 푸시 사용 설정 정의
+
+푸시 알림을 처음 설정할 때는 어떤 사용자가 어떤 방식으로 메시지를 받게 될지 파악하는 것이 중요합니다.
+
+푸시 사용은 푸시 토큰을 사용할 수 있는 사용자를 의미합니다. 예를 들어, 워크스페이스 내의 앱에 대한 활성 푸시 토큰일 수 있습니다.
+
+백그라운드 푸시 사용은 푸시가 활성화되어 있지만 포그라운드 푸시 알림을 비활성화한 사용자를 의미합니다. 이 경우 Braze는 해당 기기에 사용자가 볼 수 있는 알림을 표시할 수 없습니다. 그러나 백그라운드 푸시를 사용하여 제거 추적, 무음 푸시 알림 사용, 지오펜싱을 사용할 수 있습니다.  
+
+자세한 내용은 [푸시 알림에 대한][1] 도움말 문서를 참조하세요.
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트: 2021년 1월 24일_
+
+[1]: {{site.baseurl}}/user_guide/message_building_by_channel/push/about
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/push/push_error_codes.md b/_lang/ko/_help/help_articles/push/push_error_codes.md
new file mode 100644
index 00000000000..53486cf4dd5
--- /dev/null
+++ b/_lang/ko/_help/help_articles/push/push_error_codes.md
@@ -0,0 +1,60 @@
+---
+nav_title: 일반적인 푸시 오류 메시지
+article_title: 일반적인 푸시 오류 메시지
+page_order: 2
+
+page_type: solution
+description: "이 도움말 문서는 iOS 및 Android에 대한 일반적인 푸시 관련 오류 메시지를 다루고 잠재적인 솔루션을 안내합니다."
+channel: push
+platform:
+- iOS
+- Android
+---
+
+# 일반적인 푸시 오류 메시지
+
+푸시 메시징에 대한 일반적인 오류 메시지를 확인하세요:
+
+{% tabs %}
+{% tab Android %} 
+### 푸시 반송됨: MismatchSenderId
+`MismatchSenderId`은 인증 실패를 나타냅니다. Firebase Cloud Messaging(FCM)은 주요 데이터 조각인 senderID 및 FCM API 키로 인증합니다.  이들은 모두 정확성을 위해 검증되어야 합니다. 자세한 내용은 이 문제에 대한 [Android 설명서](https://firebase.google.com/docs/cloud-messaging/http-server-ref#error-codes)를 참조하십시오.
+
+일반적인 실패에는 다음이 포함될 수 있습니다:
+- 나쁜 [senderID]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/integration/standard_integration/#step-1-enable-firebase)
+- 다른 senderID로 다른 푸시 서비스에 등록하면 여러 번 등록됩니다
+
+### 푸시 반송됨: InvalidRegistration
+`InvalidRegistration`은 푸시 토큰이 잘못된 형식일 때 발생할 수 있습니다. 일반적인 실패에는 다음과 같은 경우가 포함될 수 있습니다.
+- 사람들이 Braze 등록 토큰을 수동으로 전달하고 있지만 `getToken()`을(를) 호출하지 않습니다. 예를 들어, 그들은 전체 인스턴스 ID를 전달할 수 있습니다. 오류 메시지의 토큰은 `&#124;ID&#124;1&#124;:[regular token]`처럼 보입니다.  
+- 사람들이 여러 서비스에 등록하고 있습니다. 현재 푸시 등록 의도가 구식으로 도착할 것으로 예상되므로, 사람들이 여러 장소에서 등록하고 다른 서비스에서 의도를 포착하면 잘못된 푸시 토큰을 받을 수 있습니다.
+
+### 푸시 반송됨: NotRegistered
+`NotRegistered`는 일반적으로 앱이 기기에서 삭제되었음을 의미합니다(예: 제거 신호). 이것은 여러 등록이 발생하고 두 번째 등록이 Braze가 받는 푸시 토큰을 무효화하는 경우에도 발생할 수 있습니다.
+
+{% endtab %}
+{% tab iOS %}
+
+### 푸시 반송됨: 잘못된 푸시 토큰으로 전송 오류
+
+이 오류는 여러 가지 이유로 발생할 수 있습니다:
+- 푸시 토큰이 `[[Appboy sharedInstance] registerPushToken:]`에게 올바르게 전송되지 않고 있습니다
+	- **메시지 활동 로그**에서 토큰을 확인하세요. 일반적으로 문자와 숫자의 긴 문자열처럼 보여야 합니다(e.g `6e407a9be8d07f0cdeb9e714733a89445f57a89ec890d63867c482a483506fa6`). 그렇지 않으면 Braze 푸시 토큰 오류를 보내는 데 관련된 코드를 확인하세요.<br><br>
+- 프로비저닝 환경이 일치하지 않음:
+	- 개발 인증서로 등록하고 프로덕션 인증서로 보내려고 하면 이 오류를 볼 수 있습니다.  
+	- Braze는 프로덕션 환경에서만 범용 인증서를 지원합니다. 개발 환경에서 보편적인 인증서를 사용하여 푸시를 테스트하는 것은 작동하지 않습니다. 
+	- 이 보고서는 개발이 아닌 프로덕션에서 바운싱을 보냅니다.<br><br>
+- 프로비저닝 프로필 불일치:
+	- 인증서가 토큰을 얻는 데 사용된 것과 일치하지 않으면 이런 일이 발생할 수 있습니다. 이것이 의심되는 경우 다음 단계는 다음을 포함합니다:
+		- 푸시 인증서가 Braze 대시보드에서 푸시를 보내는 데 사용되고 프로비저닝 프로필이 올바르게 구성되었는지 확인합니다.
+		- APNS 인증서를 재생성한 후 APNS 인증서가 `app_id`에 구성되면 프로비저닝 프로필을 다시 생성합니다. 이것은 때때로 더 눈에 띄는 문제를 해결할 수 있습니다.
+
+### 푸시 반송됨: APNS 피드백 서비스 제거됨
+
+일반적으로 누군가가 프로그램을 제거할 때 발생합니다. Braze는 매일 밤 APNS 피드백 서비스에 쿼리를 보내 잘못된 토큰 목록을 가져옵니다. 자세한 내용은 Apple의 [APNs와의 통신](https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/CommunicatingwithAPNs.html)을 참조하십시오.
+
+
+{% endtab %}
+{% endtabs %}
+
+_마지막 업데이트 날짜: 2021년 1월 24일_
diff --git a/_lang/ko/_help/help_articles/push/push_token_migration.md b/_lang/ko/_help/help_articles/push/push_token_migration.md
new file mode 100644
index 00000000000..0874483b2fd
--- /dev/null
+++ b/_lang/ko/_help/help_articles/push/push_token_migration.md
@@ -0,0 +1,122 @@
+---
+nav_title: 푸시 토큰 마이그레이션
+article_title: 푸시 토큰 마이그레이션
+page_order: 0
+
+page_type: solution
+description: "이 도움말 문서에서는 Braze로 전환한 후에도 사용자에게 푸시 메시지를 계속 보낼 수 있도록 푸시 토큰을 마이그레이션하는 방법을 설명합니다."
+channel: push
+---
+
+# 푸시 토큰 마이그레이션
+
+[푸시 토큰]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_registration/#push-tokens/)은 앱의 알림을 전송할 위치를 지정하는 고유한 익명 식별자입니다. Braze는 Android용 Firebase 클라우드 메시징 서비스(FCM) 및 iOS용 Apple 푸시 알림 서비스(APN)와 같은 푸시 서비스 제공업체와 연결되며, 이러한 제공업체는 앱을 식별하는 고유 기기 토큰을 전송합니다. Braze를 통합하기 전에 자체적으로 또는 다른 제공업체를 통해 푸시 알림을 보내고 있었다면, 푸시 토큰 마이그레이션을 통해 등록된 푸시 토큰으로 사용자에게 푸시 알림을 계속 보낼 수 있습니다.
+
+## SDK를 통한 자동 마이그레이션
+
+Braze SDK는 이전에 푸시 알림을 옵트인한 사용자가 Braze 통합 앱 또는 사이트에 처음 로그인할 때 푸시 토큰을 자동으로 마이그레이션합니다. Braze SDK를 통합하는 경우 API를 사용하여 푸시 토큰을 마이그레이션할 필요가 없습니다.
+
+그러나 사용자가 앱에 처음 로그인할 때 푸시 토큰이 마이그레이션되므로, Braze는 SDK 연동 후 로그인하지 않은 사용자에게 푸시 알림을 보낼 수 없다는 점에 유의하세요. 이러한 사용자와 다시 참여하기 위한 방법으로 Android 및 iOS 푸시 토큰을 수동으로 마이그레이션할 수도 있습니다.
+
+{% alert note %}
+웹 푸시 토큰의 특성상 최대 60일마다 토큰이 만료되고 초기화됩니다. 해당 기간 내에 세션이 없는 사람은 웹 푸시 토큰이 활성화되지 않습니다. Braze는 만료된 웹 푸시 토큰을 마이그레이션하지 않습니다. 이러한 사용자는 [푸시 프라이머를]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/push_primer_messages) 통해 다시 참여해야 합니다.
+{% endalert %}
+
+## API를 통한 수동 마이그레이션
+
+수동 푸시 토큰 마이그레이션은 API를 통해 이전에 생성한 키를 Braze 플랫폼으로 가져오는 프로세스입니다.
+
+[`users/track` 엔드포인트]({{site.baseurl}}/api/endpoints/user_data/post_user_track/)를 사용하여 프로그래밍 방식으로 iOS(APN) 및 Android(FCM) 토큰을 플랫폼으로 마이그레이션합니다. 식별된 사용자(연결된 외부 ID가 있는 사용자)와 익명 사용자(외부 ID가 없는 사용자)를 모두 마이그레이션할 수 있습니다.
+
+푸시 토큰 마이그레이션 중에 앱의 `app_id`를 지정하여 적절한 푸시 토큰을 적절한 앱에 연결합니다. 각 앱(iOS, Android 등)에는 [API 키]({{site.baseurl}}/user_guide/administrative/app_settings/api_settings_tab/) 페이지의 **식별** 섹션에서 찾을 수 있는 고유한 `app_id` 이 있습니다. 올바른 플랫폼의 `app_id` 을 사용해야 합니다.
+
+{% alert important %}
+API를 통해 웹 푸시 토큰을 마이그레이션하는 것은 불가능합니다. 이는 웹 푸시 토큰이 다른 플랫폼과 동일한 스키마를 따르지 않기 때문입니다. 
+
+<br>프로그래밍 방식으로 웹 푸시 토큰을 마이그레이션하려는 경우 `Received '400: Invalid subscription auth' sending to 'https://fcm.googleapis.com/fcm/send` 오류가 표시될 수 있습니다.
+
+<br>
+API 마이그레이션의 대안으로 SDK를 통합하여 토큰 기반이 자연스럽게 다시 채워질 수 있도록 하는 것이 좋습니다.
+{% endalert %}
+
+### 외부 ID가 있는 경우 마이그레이션
+식별된 사용자의 경우 `push_token_import` 플래그를 `false`로 설정(또는 매개변수 생략)하고 사용자 `attributes` 오브젝트에 `external_id`, `app_id`, `token` 값을 지정합니다. 
+
+예를 들어, 다음과 같습니다.
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+--data-raw '{
+  "attributes" : [
+    {
+      "push_token_import" : false,
+      "external_id": "example_external_id",
+      "country": "US",
+      "language": "en",
+      "YOUR_CUSTOM_ATTRIBUTE": "YOUR_VALUE",
+      "push_tokens": [
+        {"app_id": "APP_ID_OF_OS", "token": "PUSH_TOKEN_STRING"}
+      ]
+    }
+  ]
+}'
+```
+
+### 외부 ID가 없는 경우 마이그레이션
+다른 시스템에서 푸시 토큰을 가져올 때 `external_id`를 항상 사용할 수 있는 것은 아닙니다. 이 경우 `push_token_import` 플래그를 `true`로 설정하고 `app_id` 및 `token` 값을 지정합니다. Braze는 각 토큰에 대해 임시 익명 고객 프로필을 생성하여 이러한 개인에게 계속 메시지를 보낼 수 있도록 합니다. 토큰이 이미 Braze에 존재하는 경우 요청은 무시됩니다.
+
+예를 들어, 다음과 같습니다.
+
+```json
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-API-KEY-HERE' \
+--data-raw '{
+  "attributes": [ 
+    {
+      "push_token_import" : true,
+      "email": "braze.test1@testbraze.com",
+      "country": "US",
+      "language": "en",
+      "YOUR_CUSTOM_ATTRIBUTE": "YOUR_VALUE",
+      "push_tokens": [
+        {"app_id": "APP_ID_OF_OS", "token": "PUSH_TOKEN_STRING", "device_id": "DEVICE_ID"}
+      ]
+    },
+      
+    {
+      "push_token_import" : true,
+      "email": "braze.test2@testbraze.com",
+      "country": "US",
+      "language": "en",
+      "YOUR_CUSTOM_ATTRIBUTE_1": "YOUR_VALUE",
+      "YOUR_CUSTOM_ATTRIBUTE_2": "YOUR_VALUE",
+      "push_tokens": [
+        {"app_id": "APP_ID_OF_OS", "token": "PUSH_TOKEN_STRING", "device_id": "DEVICE_ID"}  
+      ]
+    }
+  ]
+}'
+```
+
+가져온 후 익명 사용자가 Braze 지원 버전의 앱을 실행하면, Braze는 가져온 푸시 토큰을 자동으로 Braze 고객 프로필로 이동하고 임시 프로필을 정리합니다.
+
+Braze는 한 달에 한 번씩 푸시 토큰이 없으며 `push_token_import` 플래그가 있는 익명 프로필을 확인합니다. 익명 프로필에 더 이상 푸시 토큰이 없는 경우 해당 프로필을 삭제합니다. 그러나 익명 프로필에 푸시 토큰이 남아 있어 실제 사용자가 아직 해당 푸시 토큰으로 기기에 로그인하지 않았다는 것을 암시하는 경에는 아무 조치도 취하지 않습니다.
+
+## Android 푸시 토큰 가져오기
+
+{% alert important %}
+다음 고려 사항은 Android 앱에만 적용됩니다. iOS 앱에는 푸시 표시를 위한 프레임워크가 하나만 있으며, Braze에 필요한 푸시 토큰과 인증서가 있는 한 푸시 알림이 즉시 렌더링되므로 이러한 단계가 필요하지 않습니다.
+{% endalert %}
+
+Braze SDK 통합이 완료되기 전에 사용자에게 Android 푸시 알림을 보내야 하는 경우 키-값 페어를 사용하여 푸시 알림의 유효성을 검사하세요. 
+
+푸시 페이로드를 처리하고 표시하려면 수신기가 있어야 합니다. 수신자에게 푸시 페이로드를 알리려면 푸시 캠페인에 필요한 키-값 쌍을 추가합니다. 이 쌍의 값은 Braze 이전에 사용한 특정 푸시 파트너에 따라 달라집니다.
+
+{% alert note %}
+일부 푸시 알림 제공업체의 경우, Braze가 키-값 페어를 올바르게 해석할 수 있도록 평평하게 만들어야 합니다. 특정 Android 앱의 키-값 페어를 평평하게 하려면 고객 온보딩 또는 성공 매니저에게 문의하세요.
+{% endalert %}
+
+_마지막 업데이트: 2022년 12월 5일_
diff --git a/_lang/ko/_help/help_articles/push/push_unsubscribes.md b/_lang/ko/_help/help_articles/push/push_unsubscribes.md
new file mode 100644
index 00000000000..042344d775b
--- /dev/null
+++ b/_lang/ko/_help/help_articles/push/push_unsubscribes.md
@@ -0,0 +1,34 @@
+---
+nav_title: 푸시 수신 거부 추적
+article_title: 푸시 수신 거부 추적
+page_type: solution
+description: "이 도움말 문서에서는 푸시 수신 거부 추적에 대한 몇 가지 팁을 제공합니다."
+channel: push
+---
+
+# 푸시 수신 거부 추적 기술
+
+푸시 수신 거부 여부는 Apple 또는 Google과 같은 제공업체의 사용자 푸시 상태 업데이트에 따라 달라집니다. 이러한 업데이트는 드물고 예측하기 어려울 수 있습니다. 따라서 푸시 구독 취소는 푸시 캠페인 분석의 지표로 포함되지 않습니다. 
+
+하지만 수동으로 푸시 수신 취소를 추적하면 알림 빈도 및 콘텐츠 관련성에 대한 사용자 반응에 대한 귀중한 인사이트를 얻을 수 있습니다. 다음은 푸시 수신 거부 추적을 위한 두 가지 옵션입니다.
+
+## 옵션 1: 세그먼트 필터 사용
+
+해결 방법으로 세그먼트를 생성하여 푸시가 활성화되지 않은 사용자, 즉 구독 또는 옵트인하지 않았고 [포그라운드 푸시 토큰]({{site.baseurl}}/user_guide/message_building_by_channel/push/push_registration/#push-tokens)이 없는 사용자를 식별할 수 있습니다. 예를 들어 Android 앱에서 구독 취소 횟수를 확인하려면 다음 세그먼트의 조합을 사용합니다. 
+
+- `Background or Foreground Push Enabled for App "TEST (Android)" is false`
+- `Has Uninstalled`
+
+![테스트(Android) 앱에 대해 "앱에 백그라운드 또는 포그라운드 푸시 사용" 필터가 있는 세그먼트 빌더 섹션이 거짓이고 "제거됨" 필터가 선택되어 도달 가능한 사용자 2,393명을 표시합니다.]({% image_buster /assets/img/push_unsub_segment_example.png %})
+
+세분화 필터는 대략적인 기준이며 날짜 및 캠페인에 구체적으로 연결될 수 없습니다.
+
+## 옵션 2: 사용자 지정 이벤트 사용
+
+{% alert important %}
+구독 변경에 대한 사용자 지정 이벤트를 기록하면 [데이터 포인트가]({{site.baseurl}}/user_guide/data_and_analytics/data_points#consumption-count) 소모된다는 점에 유의하세요. 또는 세그먼트 필터를 사용하여 푸시를 사용 설정하지 않은 사용자를 식별하고 타겟팅할 수 있습니다.
+{% endalert %}
+
+다른 해결 방법으로는 사용자의 푸시 사용 설정 상태가 `true` 또는 `false`인지에 따라 푸시 수신 거부 커스텀 이벤트를 생성하여 이 지표를 추적하는 것이 좋습니다.
+
+_마지막 업데이트 2024년 6월 13일_
diff --git a/_lang/ko/_help/help_articles/push/reducing_payload_size.md b/_lang/ko/_help/help_articles/push/reducing_payload_size.md
new file mode 100644
index 00000000000..9dcd3645932
--- /dev/null
+++ b/_lang/ko/_help/help_articles/push/reducing_payload_size.md
@@ -0,0 +1,46 @@
+---
+nav_title: 푸시 알림 페이로드 크기 줄이기
+article_title: 푸시 알림 페이로드 크기 줄이기
+page_type: solution
+description: "이 도움말 문서에서는 푸시 페이로드 크기 제한으로 인해 캠페인 또는 캔버스 단계를 시작할 수 없는 경우 푸시 알림의 페이로드 크기를 줄일 수 있는 몇 가지 팁을 제공합니다."
+channel: push
+---
+
+# 푸시 알림 페이로드 크기 줄이기
+
+푸시 페이로드가 너무 커서 푸시 캠페인이나 캔버스 단계를 시작할 수 없는 경우 푸시 알림 페이로드 크기를 줄이기 위한 다음 팁을 확인하세요.
+
+{% alert note %}
+최대 페이로드 크기는 **3,807바이트입니다**. 푸시 크기가 이 크기를 초과하면 메시지가 전송되지 않을 수 있습니다. 페이로드를 수백 바이트로 유지하는 것이 가장 좋습니다.
+{% endalert %}
+
+## 푸시 페이로드란 무엇인가요?
+
+푸시 서비스 제공업체는 전체 푸시 페이로드의 바이트 크기를 보고 사용자에게 푸시 알림을 표시할 수 있는지 여부를 계산합니다. 페이로드는 다음을 포함한 대부분의 푸시 서비스에서 **4KB(4,096바이트)**로 제한됩니다.
+
+- Apple 푸시 알림 서비스(APN)
+- Android의 Firebase Cloud Messaging(FCM)
+- 웹 푸시
+- Huawei 푸시
+
+이러한 푸시 서비스는 이 한도를 초과하는 모든 알림을 거부합니다.
+
+Braze는 통합 및 분석 목적으로 푸시 페이로드의 일부를 보유합니다. 이를 감안할 때 최대 페이로드 크기는 **3,807바이트**입니다. 푸시 크기가 이 크기를 초과하면 메시지가 전송되지 않을 수 있습니다. 페이로드를 수백 바이트로 유지하는 것이 가장 좋습니다.
+
+푸시의 다음 요소는 푸시 페이로드를 구성합니다:
+
+- 제목 및 메시지 본문과 같은 복사본
+- Liquid 개인화의 최종 렌더링
+- 이미지의 URL(이미지 자체의 크기는 제외)
+- 클릭 타겟의 URL
+- 버튼 이름
+- 키-값 쌍
+
+## 페이로드 크기를 줄이기 위한 팁
+
+페이로드 크기를 줄이려면:
+
+- 메시지를 간결하게 작성하세요. 일반적인 가이드라인은 40자 이내로 실행 가능하고 유익한 내용을 작성하는 것입니다.
+- 사본에서 공백과 줄 바꿈은 생략하세요.
+- Liquid가 전송 시 렌더링하는 방식을 고려하세요. Liquid 개인화의 최종 렌더링은 사용자마다 다르므로, Braze는 Liquid가 포함된 경우 푸시 페이로드가 크기 제한을 초과할지 여부를 판단할 수 없습니다. Liquid에서 더 짧은 메시지를 렌더링해도 괜찮을 수 있습니다. 그러나 Liquid로 인해 메시지가 길어지면 푸시가 페이로드 크기 제한을 초과할 수 있습니다. 사용자에게 푸시 메시지를 보내기 전에 항상 실제 디바이스에서 테스트하세요.
+- URL 단축기를 사용하여 URL을 단축하는 것을 고려하세요.
diff --git a/_lang/ko/_help/help_articles/push/resetting_push_permissions.md b/_lang/ko/_help/help_articles/push/resetting_push_permissions.md
new file mode 100644
index 00000000000..8f31c6c0094
--- /dev/null
+++ b/_lang/ko/_help/help_articles/push/resetting_push_permissions.md
@@ -0,0 +1,88 @@
+---
+nav_title: 푸시 권한 재설정
+article_title: 푸시 권한 재설정
+page_type: solution
+description: "이 도움말 문서에서는 브라우저 푸시 권한 및 데이터를 재설정하는 방법을 다룹니다."
+channel: push
+---
+
+# 푸시 권한 재설정
+
+브라우저에서 푸시 알림에 문제가 있는 경우 사이트의 알림 권한을 재설정하고 사이트의 저장소를 지워야 할 수 있습니다. 이 단계들을 참조하여 도움을 받으세요.
+
+## 데스크탑에서 Chrome 재설정
+
+1. Chrome 브라우저에서 URL 옆에 있는 **사이트 정보 보기** 슬라이더 아이콘을 클릭하세요.
+2. 알림에서, **권한 재설정**을 클릭하십시오.
+3. Chrome 개발자 도구를 엽니다. 다음은 운영 체제별 관련 단축키입니다.
+
+<style> 
+table {
+    max-width: 50%;
+}
+</style>
+
+| OS      | 키보드 단축키                                                  |
+| ------- | ------------------------------------------------------------------- |
+| Mac      | `Fn` + `F12`<br>`Ctrl` + `Shift` + `I` |
+| Windows | `F12`<br>`Ctrl` + `Shift` + `I` |
+{: .reset-td-br-1 .reset-td-br-2}
+
+{:start="4"}
+4\. DevTools에서 **Application** 탭으로 이동합니다.
+5\. 사이드바에서 **스토리지**를 선택합니다.
+6\. **사이트 데이터 지우기**를 클릭합니다.
+7\. Chrome은 업데이트된 설정을 적용하기 위해 페이지를 새로 고치도록 요청할 것입니다. **새로고침**을 클릭합니다.
+
+귀하의 푸시 권한이 이제 재설정되었습니다. 새 탭을 열어 사이트에 접속하여 시도해 보세요.
+
+## Android에서 Chrome 재설정
+
+사이트에서 Android 알림 드로어에 알림이 표시되는 경우:
+
+1. 푸시 알림에서 <i class="fas fa-cog" title="설정"></i>을(를) 탭하고 **사이트 설정**을(를) 선택합니다.
+2. **사이트 설정**에서 **지우기 및 재설정**을 탭하세요.
+
+사이트에서 알림을 열지 않은 경우:
+
+1. Android에서 Chrome을 여세요.
+2. <i class="fas fa-ellipsis-vertical"></i> 메뉴를 누르세요.
+3. **설정** > **사이트 설정** > **알림**로 이동하십시오.
+4. 알림이 "보내기 전에 묻기(권장)"로 설정되어 있는지 확인하십시오.
+5. 목록에서 귀하의 사이트를 찾으세요.
+6. 항목을 선택하고 **지우기 및 재설정**을 탭하세요.
+
+귀하의 푸시 권한이 이제 재설정되었습니다. 새 탭을 열어 사이트에 접속하여 시도해 보세요.
+
+## 데스크톱에서 Firefox 재설정
+
+1. 사이트 URL 옆에 <i class="fa-solid fa-circle-info" alt="info icon"></i> 또는 <i class="fas fa-lock" alt="lock icon"></i>을 클릭하세요.
+2. **권한**에서 **알림 받기** 옆에 있는 <i class="fa-solid fa-circle-xmark" title="이 권한을 지우고 다시 요청"></i>을 선택하여 알림 권한을 지웁니다.
+3. 같은 메뉴에서 **쿠키 및 사이트 데이터 지우기**를 선택합니다.
+4. 대화 상자가 나타나 선택을 확인합니다. **확인**을 클릭합니다.
+
+귀하의 푸시 권한이 이제 재설정되었습니다. 새 탭을 열어 사이트에 접속하여 시도해 보세요.
+
+## Android에서 Firefox 재설정
+
+Android에서 푸시 권한을 재설정하려면 이 [Mozilla 지원 문서](https://support.mozilla.org/en-US/kb/clear-your-browsing-history-and-other-personal-data#w_clear-specific-items-from-your-browser)를 참조하세요.
+
+## MacOS에서 Safari 재설정
+
+{% alert note %}
+이 단계는 MacOS 전용입니다. Apple은 Windows의 Safari에 대해 웹 푸시를 지원하지 않기 때문입니다.
+{% endalert %}
+
+1. Safari를 여세요.
+2. Mac의 [메뉴 막대](https://support.apple.com/guide/mac-help/whats-in-the-menu-bar-mchlp1446/mac)에서 **Safari** > **설정** > **웹사이트** > **알림**으로 이동합니다.
+3. 목록에서 사이트를 선택하세요.
+4. **제거**를 클릭하여 사이트의 알림 권한을 삭제합니다.
+5. 그런 다음, **개인정보 보호** > **웹사이트 데이터 관리**로 이동합니다.
+6. 목록에서 사이트를 선택하세요.
+7. **제거**를 클릭하거나 모든 사이트 데이터를 제거하려면 **모두 제거**를 클릭합니다.
+8. **완료**를 클릭합니다.
+
+귀하의 푸시 권한이 이제 재설정되었습니다. 새 탭을 열어 사이트에 접속하여 시도해 보세요.
+
+
+*마지막 업데이트 날짜: 2024년 2월 12일*
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/segments.md b/_lang/ko/_help/help_articles/segments.md
new file mode 100644
index 00000000000..1e93a3c1d83
--- /dev/null
+++ b/_lang/ko/_help/help_articles/segments.md
@@ -0,0 +1,30 @@
+---
+page_order: 6
+nav_title: 세그먼트
+layout: dev_guide
+guide_top_header: "세그먼트 도움말 문서"
+guide_top_text: "다음은 세분화 로직과 필터링 문제를 명확히 하는 데 도움이 되는 몇 가지 유용한 글입니다. <br><br> Braze 캠페인 또는 캔버스에서 세분화를 사용하는 방법에 대한 자세한 내용은 <a href='/docs/user_guide/engagement_tools/segments'>세그먼트</a> 섹션을 참조하세요."
+
+page_type: landing
+description: "이 랜딩 페이지에서는 세그먼트와 관련된 일반적인 문제에 대한 도움말 문서를 확인할 수 있습니다."
+tool: Segments
+noindex: true
+guide_menu_title: ""
+guide_menu_list:
+  - name: 필터 옵션 변경
+    link: /docs/help/help_articles/segments/my_filter_options_have_changed/
+    image: /assets/img/braze_icons/flag-02.svg
+  - name: 세그먼트에 누락된 사용자
+    link: /docs/help/help_articles/segments/segment_showing_0_users/
+    image: /assets/img/braze_icons/users-01.svg
+  - name: 세분화 로직
+    link: /docs/help/help_articles/segments/segmentation_logic_with_and_or/
+    image: /assets/img/braze_icons/columns-01.svg
+  - name: 정확한 텍스트 검색
+    link: /docs/help/help_articles/segments/search_exact_text/
+    image: /assets/img/braze_icons/search-refraction.svg
+  - name: 대형 세그먼트 내보내기
+    link: /docs/help/help_articles/segments/exporting_large_segments/
+    image: /assets/img/braze_icons/file-download-01.svg
+
+---
diff --git a/_lang/ko/_help/help_articles/segments/exporting_large_segments.md b/_lang/ko/_help/help_articles/segments/exporting_large_segments.md
new file mode 100644
index 00000000000..ba718de5a4e
--- /dev/null
+++ b/_lang/ko/_help/help_articles/segments/exporting_large_segments.md
@@ -0,0 +1,25 @@
+---
+nav_title: 대형 세그먼트 내보내기
+article_title: 대형 세그먼트 내보내기
+page_order: 4
+
+page_type: solution
+description: "이 도움말 문서는 대규모 사용자 세그먼트를 내보내는 여러 방법을 안내합니다."
+tool: Segments
+---
+
+# 대형 세그먼트 내보내기
+
+큰 사용자 세그먼트를 내보내는 여러 가지 방법이 있습니다. 세그먼트에 500,000명 이상의 사용자가 포함된 경우, 이 더 큰 세그먼트를 더 작은 세그먼트로 분할하여 이러한 사용자를 캡처하고 각 더 작은 세그먼트를 Braze 대시보드에서 내보낼 수 있습니다. 
+
+또한 [무작위 버킷 번호]({{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/ab_testing_with_random_buckets/#step-1-segment-your-users-by-the-random-bucket-attribute)를 사용하여 사용자 기반을 여러 세그먼트로 나눈 다음 내보낸 후 결합하는 것을 고려할 수 있습니다. 예를 들어, 세그먼트를 두 개의 다른 세그먼트로 나누어야 하는 경우 다음 필터를 사용하여 수행할 수 있습니다:
+- 세그먼트 1: 무작위 버킷 번호는 5000보다 작습니다 (0-4999 포함)
+- 세그먼트 2: 무작위 버킷 번호는 4999보다 큽니다 (5000-9999 포함)
+
+다음 엔드포인트를 활용하여 특정 세그먼트의 사용자 데이터를 내보낼 수도 있습니다. 이러한 엔드포인트는 데이터 제한을 받을 수 있습니다.
+- [`/users/export/segment`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/)
+- [`/users/export/global_control_group`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_global_control_group/)
+
+아직 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트 날짜: 2022년 10월 24일_
diff --git a/_lang/ko/_help/help_articles/segments/my_filter_options_have_changed.md b/_lang/ko/_help/help_articles/segments/my_filter_options_have_changed.md
new file mode 100644
index 00000000000..e1db7618ab4
--- /dev/null
+++ b/_lang/ko/_help/help_articles/segments/my_filter_options_have_changed.md
@@ -0,0 +1,27 @@
+---
+nav_title: 필터 옵션 변경
+article_title: 필터 옵션 변경
+page_order: 0
+
+page_type: solution
+description: "이 도움말 문서에서는 사용자 지정 속성에 대한 필터 옵션이 변경된 경우의 의미에 대해 설명합니다."
+tool: Segments
+---
+
+# 필터 옵션 변경
+
+필터 옵션은 사용자 지정 속성을 위해 Braze에 전달하는 형식(데이터 유형)과 관련이 있습니다. Braze가 사용자 지정 속성에 대해 인식하는 데이터 유형을 검토하려면 **데이터 설정** > **사용자 지정 속성으로** 이동하세요.
+
+{% alert note %}
+[이전 탐색]({{site.baseurl}}/navigation)을 사용하는 경우 **설정 관리**에서 **커스텀 속성을** 찾을 수 있습니다.
+{% endalert %}
+
+필터 옵션이 변경된 경우, 이는 데이터가 이전과 다른 형식(데이터 유형)으로 Braze에 전달되고 있음을 나타냅니다. 다양한 데이터 유형과 해당 필터링 옵션에 대한 자세한 설명은 [커스텀 속성 데이터 유형][36]을 참조하세요.
+
+대시보드에서 커스텀 속성의 데이터 유형을 변경하면 다른 형식으로 Braze에 전송된 데이터는 거부된다는 점에 유의하세요.
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트: 2021년 5월 5일_
+
+[36]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#custom-attribute-data-types
diff --git a/_lang/ko/_help/help_articles/segments/search_exact_text.md b/_lang/ko/_help/help_articles/segments/search_exact_text.md
new file mode 100644
index 00000000000..9b52ab9d3a6
--- /dev/null
+++ b/_lang/ko/_help/help_articles/segments/search_exact_text.md
@@ -0,0 +1,17 @@
+---
+nav_title: 정확한 텍스트 검색
+article_title: 검색 필드에서 정확한 텍스트 검색
+page_order: 5
+
+page_type: solution
+description: "이 도움말 문서에서는 Braze의 검색 필드에서 정확한 텍스트를 찾는 방법에 대해 설명합니다."
+tool: Segments
+---
+
+# 정확한 텍스트 검색
+
+특정 항목을 검색하면 검색어가 포함된 모든 결과를 표시하기 때문에 Braze에서 가끔 너무 많은 결과가 표시될 수 있습니다.
+
+정확한 텍스트를 검색하려면 검색어를 `[ ]`대괄호로 묶으세요.
+
+예를 들어 **세그먼트** 페이지에서 `[Purchase]` 을 검색하면 "구매"라는 단어가 포함된 세그먼트는 표시되지만 "구매자" 또는 "구매"는 표시되지 않습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/help_articles/segments/segment_showing_0_users.md b/_lang/ko/_help/help_articles/segments/segment_showing_0_users.md
new file mode 100644
index 00000000000..15b7343072a
--- /dev/null
+++ b/_lang/ko/_help/help_articles/segments/segment_showing_0_users.md
@@ -0,0 +1,41 @@
+---
+nav_title: 세그먼트에서 사용자 누락
+article_title: 세그먼트에서 사용자 누락
+page_order: 1
+
+page_type: solution
+description: "이 도움말 문서는 세그먼트에 사용자가 표시되지 않지만 더 많은 사용자가 예상되는 경우 문제 해결 단계를 안내합니다."
+tool: Segments
+---
+
+# 세그먼트에 사용자 누락
+
+`0` 사용자를 보고 있지만 더 많은 사용자를 예상했을 때 가능한 두 가지 솔루션이 있습니다.
+* [상세 통계 계산](#calculate-exact-statistics)
+* [데이터 전송 확인](#verify-data-transfer)
+
+## 정확한 통계를 계산하하세요
+
+세그먼트 통계는 추정치를 제공할 수 있습니다. 추정치는 95%의 신뢰구간을 가지는 무작위 샘플을 기반으로 계산되며, 그 결과는 `+/- 1%` 이내입니다. 사용자 기반이 작을수록 세그먼트의 규모가 대략적인 추정치에 그칠 가능성이 높아집니다. **세그먼트 세부정보** 패널에서 **정확한 통계 계산**을 클릭하세요. 이것은 귀하의 세그먼트에 있는 정확한 사용자 수를 계산할 것입니다.
+
+![세그먼트 세부사항 패널은 정확한 통계 계산 옵션을 보여줍니다][28]
+
+## 데이터 전송 확인
+
+데이터를 필터링할 때 Braze로 전송되지 않을 수 있습니다. 어떤 커스텀 이벤트가 Braze로 전송되고 있는지 확인하려면 [커스텀 이벤트 보고서][1]를 참조하세요.
+
+커스텀 이벤트와 특정 날짜 및 앱을 선택하여 실제로 Braze로 전송되는 데이터가 무엇인지 확인합니다. 만약 `0` 데이터가 Braze로 전송되고 있음을 알게 된다면, 다음 단계는 이벤트를 Braze로 전송하는 방법을 평가하는 것입니다.
+
+![커스텀 이벤트 수를 0으로 표시하는 그래프][29]
+
+{% alert important %}
+Braze 대시보드에서 보는 데이터는 Braze로 보내는 것과 동일한 구문이 아닐 수 있습니다. Ensure that these two match exactly.
+{% endalert %}
+
+아직 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트 날짜: 2021년 1월 5일_
+
+[1]: {{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_events/#custom-event-analytics
+[28]: {% image_buster /assets/img_archive/trouble8.png %}
+[29]: {% image_buster /assets/img_archive/trouble9.png %}
diff --git a/_lang/ko/_help/help_articles/segments/segmentation_logic_with_and_or.md b/_lang/ko/_help/help_articles/segments/segmentation_logic_with_and_or.md
new file mode 100644
index 00000000000..f126dabbcb2
--- /dev/null
+++ b/_lang/ko/_help/help_articles/segments/segmentation_logic_with_and_or.md
@@ -0,0 +1,63 @@
+---
+nav_title: 세분화 로직
+article_title: 세분화 로직 
+page_order: 3
+
+page_type: solution
+description: "이 도움말 문서에서는 AND 연산자와 OR 연산자의 차이점과 이를 사용하여 강력한 세그먼트를 구축하는 방법을 안내합니다."
+tool: Segments
+---
+
+# 세분화 로직 
+
+`AND` 및 `OR` 연산자를 사용하면 [세그먼트를 만들]({{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/) 때 강력한 필터링이 가능합니다. 이러한 연산자를 사용하면 캠페인 또는 캔버스를 구축하는 **타겟 오디언스** 단계에서 사용자의 행동이나 행동을 기반으로 사용자 기반을 타겟팅할 수 있습니다.
+
+## AND 및 OR 연산자 이해
+
+`AND` 및 `OR` 운영자는 서로 다른 방식으로 작동합니다. 오디언스를 세분화할 때 달성하려는 목표에 따라 각 연산자를 사용할 수 있습니다. 
+
+### AND 연산자를 사용해야 하는 경우
+
+일반적으로 특정 속성에 대한 두 개 이상의 값의 교집합에 관심이 있는 경우 `AND`를 사용하세요.
+
+캐나다와 미국을 제외한 모든 국가의 캠페인에서 사용자를 타겟팅하는 방법을 고려해 보겠습니다. 이 경우 `AND` 연산자를 사용하면 이러한 사용자를 필터링하는 데 도움이 될 수 있습니다. `Country is not United States AND Country is not Canada` 문구에는 미국 출신이 아니며 캐나다 출신이 아닌 사용자만 포함됩니다. 따라서 이 논리를 사용하면 캐나다와 미국의 사용자 모두 제외됩니다.
+
+### OR 연산자를 사용해야 하는 경우
+
+조건 집합에서 하나 이상의 조건을 충족하는 사용자를 타겟팅하는 것이 목표인 경우 `OR`을 사용하세요. `OR`로 연결된 세 가지 조건이 있는 경우 실제 문이 참이 되려면 조건 중 하나, 둘 또는 모두가 참일 수 있습니다.
+
+예를 들어 앱 버전 1.0 또는 1.1을 사용하는 모든 사용자에게 메시지를 보내려고 한다고 가정해 보겠습니다. 버전 1.0 및 버전 1.1을 사용하는 사용자를 타겟팅하려면 세그먼트에 `OR` 연산자와 함께 `Is 1.0` 및 `Is 1.1` 필터를 사용할 수 있습니다. 이는 버전 1.0 또는 1.1을 사용하는 모든 사용자를 대상으로 합니다.
+
+다음 예제에서는 미국과 캐나다의 사용자 모두에게 유효한 프로모션을 고려합니다. 프로모션이 유효한 지역의 사용자만 프로모션을 받도록 하려고 합니다. 이 시나리오에서는 다음 문장을 사용하여 캠페인을 타겟팅합니다: `Country is United States OR Country is Canada`. `OR` 연산자를 사용하면 국가가 캐나다 또는 미국인 사용자에게만 캠페인이 전달됩니다.
+
+#### OR 연산자를 피해야 하는 경우
+
+`OR` 연산자 사용을 피해야 하는 사용자 타겟팅 상황이 있을 수 있습니다. `OR` 연산자는 사용자가 문에 있는 하나 이상의 필터 기준을 충족하면 참으로 평가되는 문을 만듭니다. 예를 들어 "식도락가"에 속하지만 "비식도락가"나 "사탕 애호가"에 속하지 않는 사용자 세그먼트를 만들려면 `OR` 연산자를 사용하면 됩니다.
+
+![][1]
+
+그러나 "식도락가" 세그먼트에 속하고 "비식도락가" 및 "사탕 애호가" 세그먼트에 속하지 않는 사용자를 세분화하는 것이 목표인 경우 `AND` 연산자를 사용하세요. 이렇게 하면 캠페인이나 캔버스를 수신하는 사용자가 의도한 세그먼트("식도락가")에 속하고 다른 세그먼트("비식도락가" 및 "사탕 애호가")에는 동시에 속하지 않게 됩니다. 
+
+두 개 이상의 필터가 동일한 속성을 참조하는 경우 다음 네거티브 타겟팅 기준을 `OR` 연산자와 함께 사용해서는 안 됩니다.
+
+- `is not`
+- `does not equal`
+- `does not match regex`
+
+`is not`, `does not equal` 또는 `does not match regex` 이 문장에서 `OR` 연산자와 함께 두 번 이상 사용되는 경우 해당 속성의 모든 값을 가진 사용자가 타겟팅됩니다.
+
+### 두 연산자 모두 사용
+
+다음 예제에서는 `AND` 및 `OR` 연산자를 모두 사용합니다. 여기서 오디언스에는 나이키 운동화 또는 아디다스 운동화를 구매하고 이메일 알림을 수신하도록 옵트인한 사용자가 포함됩니다.
+
+![사용자가 좋아하는 브랜드가 나이키 또는 아디다스이고 이메일 수신에 동의한 스니커즈 쇼핑객을 위한 세그먼트를 구축합니다][33]
+
+올바른 로직을 구축하고 있는지 확인하는 또 다른 방법은 세그먼트를 만들고 필터에 따라 세그먼트에 속하는 사용자][35] 를 미리 보는 것입니다. 이렇게 하면 해당 속성, 앱 버전 또는 기타 세분화가 현재 표시되는 것과 일치하는지 확인할 수 있습니다.
+
+아직도 도움이 필요하신가요? [지원 티켓]({{site.baseurl}}/braze_support/)을 여세요.
+
+_마지막 업데이트: 2022년 6월 3일_
+
+[1]: {% image_buster /assets/img_archive/or_operator_segment.png %}
+[33]: {% image_buster /assets/img_archive/NikeSneakers.png %}
+[35]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/
diff --git a/_lang/ko/_help/home.md b/_lang/ko/_help/home.md
new file mode 100644
index 00000000000..674cdbbb210
--- /dev/null
+++ b/_lang/ko/_help/home.md
@@ -0,0 +1,53 @@
+---
+page_order: 0
+nav_title: 홈
+article_title: Braze 도움말
+layout: self_help
+help_top_header: "Braze Help"
+
+page_type: landing
+user_top_text: "Welcome to the Braze self-help section! Here you'll find a variety of help articles that can help you troubleshoot issues you may encounter. You can also learn more about the best practices to communicate with and reach your users."
+description: "이 랜딩 페이지에는 베스트 셀프 도움말 섹션이 있습니다. 여기에서 다양한 도움말 문서, 모범 사례 및 FAQ, 릴리스 노트, 미디어 리소스 등을 찾을 수 있습니다."
+
+resources_list:
+  - name: 도움말
+    link: /docs/help/help_articles/overview/
+    image: /assets/img/braze_icons/info-circle.svg
+  - name: 모범 사례 및 FAQ
+    link: /docs/help/faqs/
+    image: /assets/img/braze_icons/book-open-01.svg
+  - name: 릴리스 정보
+    link: /docs/help/release_notes/most_recent/
+    image: /assets/img/braze_icons/sticker-square.svg
+  - name: Braze 학습 로그인
+    link: https://learning.braze.com/
+    image: /assets/img/braze_icons/user-square.svg
+  - name: 미디어 리소스
+    link: https://www.youtube.com/channel/UCEXVTEWeAHx1OlddOMRTaOg
+    image: /assets/img/braze_icons/youtube.svg
+  - name: Braze 고객지원팀
+    link: /docs/braze_support/
+    image: /assets/img/braze_icons/mail-01.svg
+
+popular_topic_list:
+  - name: 보내기 전에 알아두어야 할 사항
+    link: /docs/help/help_articles/campaigns_and_canvas/know_before_send/
+  - name: 푸시 토큰 마이그레이션
+    link: /docs/help/help_articles/push/push_token_migration/
+  - name: 사용자 지정 이벤트 속성 로깅
+    link: /docs/help/help_articles/campaigns_and_canvas/using_custom_event_properties/
+  - name: 디스패치 ID
+    link: /docs/help/help_articles/data/dispatch_id/
+  - name: 이메일 반송
+    link: /docs/help/help_articles/email/email_bounces/
+  - name: API를 통해 사용자 삭제하기
+    link: /docs/help/help_articles/api/delete_user/
+  - name: 사용자 지정 데이터 유형 변경
+    link: /docs/help/help_articles/data/change_custom_data_type/
+  - name: 인앱 메시지가 표시되지 않음
+    link: /docs/help/help_articles/in-app_messages/in-app_messages_not_displaying/  
+  - name: 이벤트 로깅 사용
+    link: /docs/help/help_articles/campaigns_and_canvas/using_event_logging/ 
+---
+
+
diff --git a/_lang/ko/_help/release_notes.md b/_lang/ko/_help/release_notes.md
new file mode 100644
index 00000000000..a0b8cb572ee
--- /dev/null
+++ b/_lang/ko/_help/release_notes.md
@@ -0,0 +1,757 @@
+---
+nav_title: 릴리스 정보
+article_title: 릴리스 정보
+page_order: 4
+layout: dev_guide
+guide_top_header: "릴리스 정보"
+guide_top_text: "여기에서 Braze 플랫폼의 모든 업데이트를 확인할 수 있으며, <a href='/docs/help/release_notes/#most-recent'>가장 최근의 플랫폼 업데이트</a>는 다음과 같습니다."
+page_type: landing
+search_rank: 1
+description: "이 랜딩 페이지에서는 Braze 릴리즈 노트를 확인할 수 있습니다. 여기에서 Braze 플랫폼과 SDK에 대한 모든 업데이트, 더 이상 사용되지 않는 기능 목록을 확인할 수 있습니다."
+
+guide_featured_title: "릴리스 노트"
+guide_featured_list:
+  - name: 2024
+    link: /docs/help/release_notes/2024/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: 2023
+    link: /docs/help/release_notes/2023/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: 2022
+    link: /docs/help/release_notes/2022/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: 2021
+    link: /docs/help/release_notes/2021/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: 2020
+    link: /docs/help/release_notes/2020/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: 2019
+    link: /docs/help/release_notes/2019/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: 2018
+    link: /docs/help/release_notes/2018/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: 2017
+    link: /docs/help/release_notes/2017/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: 2016
+    link: /docs/help/release_notes/2016/
+    image: /assets/img/braze_icons/calendar-check-02.svg
+  - name: 사용 중단
+    link: /docs/help/release_notes/deprecations/
+    image: /assets/img/braze_icons/calendar-minus-01.svg
+  - name: SDK 변경 로그
+    link: /docs/developer_guide/platform_integration_guides/sdk_changelogs/
+    image: /assets/img/braze_icons/file-code-01.svg
+
+---
+
+# 최신 Braze 릴리즈 노트 {#most-recent}
+
+> Braze는 주요 제품 출시에 맞춰 한 달 주기로 제품 업데이트에 대한 정보를 공개하지만 매주 기타 개선 사항이 업데이트됩니다.
+> <br>
+> <br>
+> 이 섹션에 나열된 업데이트에 대한 자세한 내용은 계정 관리자에게 문의하거나 [지원 티켓을 개설하세요]({{site.baseurl}}/help/support/). 또한 [SDK 체인지로그에서]({{site.baseurl}}/developer_guide/platform_integration_guides/sdk_changelogs/) 월별 SDK 릴리스, 업데이트 및 개선 사항에 대한 자세한 정보를 확인할 수 있습니다.
+
+## 2024년 7월 23일 출시
+
+### Braze 문서 업데이트
+
+#### Diátaxis 및 Braze 문서
+
+현재 [Diátaxis](https://diataxis.fr/)라는 프레임워크를 사용하여 설명서 표준화하는 작업을 진행 중입니다. 작가와 기여자가 이 새로운 프레임워크에 맞는 콘텐츠를 만들 수 있도록 [각 콘텐츠 유형에 맞는 템플릿을 만들었습니다]({{site.baseurl}}/contributing/content_types).
+
+#### Braze 문서를 위한 새로운 풀-리퀘스트 템플릿
+
+시간을 들여 풀 리퀘스트(PR) 템플릿을 개선하여 더 쉽고 혼란스럽지 않게 [Braze 설명서에 기여하실]({{site.baseurl}}/contributing/home/) 수 있도록 했습니다. 그래도 개선의 여지가 있다고 생각되면 PR을 개설하거나 [이슈를 제출하세요](https://github.com/braze-inc/braze-docs/issues/new?assignees=&labels=enhancement&projects=&template=request_a_feature.md&title=). 모든 게 더 쉬워졌습니다!
+ 
+### 데이터 유연성
+
+#### 사용자 지정 이벤트 및 속성 내보내기
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[`/custom_attributes`]({{site.baseurl}}/api/endpoints/export/custom_attributes/get_custom_attributes) 및 [`/events`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events_data) API 엔드포인트를 통한 내보내기는 더 이상 얼리 액세스로 제공되지 않습니다.
+
+#### 사용자를 위한 새로운 커런츠 권한
+
+사용자를 위한 두 가지 새로운 권한 설정이 있습니다: **전류 통합 보기** 및 **전류 통합 편집하기**. [여기에서]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions) 사용자 권한에 대해 자세히 알아보세요. 
+
+#### Snowflake 데이터 유지 정책 업데이트
+ 
+8월 27일부터 2년이 지난 모든 Snowflake 보안 데이터 공유 이벤트 데이터에서 개인 식별 정보(PII)가 삭제됩니다. Snowflake를 사용하는 경우 유지 정책이 적용되기 전에 Snowflake 계정에 사본을 저장하여 환경의 전체 이벤트 데이터를 유지하도록 선택할 수 있습니다. 자세히 알아보려면 [Snowflake 데이터 유지]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention/)를 참조하세요.
+ 
+### 창의력 발휘
+
+#### 여러 페이지로 구성된 인앱 메시지
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+인앱 메시지에 페이지를 추가하면 온보딩 흐름이나 환영 여정과 같은 순차적인 흐름을 통해 사용자를 안내할 수 있습니다. 자세한 내용은 [드래그 앤 드롭으로 인앱 메시지 만들기]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create#multi-page)를 참조하세요.
+
+#### Liquid를 사용한 링크 단축
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[Liquid를 사용하여 URL을 개인화]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#enabling-link-shortening)하면 SMS 메시지에 포함된 URL을 자동으로 단축하고 클릭률 분석을 수집할 수 있습니다. 사용해 보려면 [링크 단축을]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/) 참조하세요.
+
+#### 카탈로그용 API 예제
+
+배열 필드를 사용하는 `/catalogs` 엔드포인트에 대한 예제를 추가했습니다. 예시를 보려면 다음을 확인하세요:
+
+- [여러 카탈로그 항목 편집]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk)
+- [여러 카탈로그 항목 만들기]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk)
+- [카탈로그 항목 업데이트]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items)
+- [카탈로그 항목 편집]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item)
+- [카탈로그 항목 생성]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item)
+- [카탈로그 항목 업데이트]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item)
+- [카탈로그 만들기]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog)
+ 
+### 강력한 채널
+
+### 여러 개의 WhatsApp 비즈니스 계정
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 각 워크스페이스에 여러 개의 WhatsApp 비즈니스 계정과 구독 그룹(및 전화번호)을 추가할 수 있습니다. 자세한 내용은 [다중 WhatsApp 비즈니스 계정]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups)을 참조하세요. 
+
+#### SMS 지리적 허용
+
+SMS 지리적 권한은 SMS 메시지를 보낼 수 있는 국가에 대한 제어를 적용하여 보안을 강화하고 사기성 SMS 트래픽으로부터 보호합니다. SMS 메시지를 승인된 지역으로만 보낼 수 있도록 국가 허용 목록을 지정하는 방법을 알아보려면 [SMS 국가 허용 목록 구성하기를]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_geographic_permissions/#configuring-your-sms-country-allowlist) 참조하세요.
+
+#### LINE과 Braze
+
+{% multi_lang_include release_type.md release="베타" %}
+
+[LINE](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf)은 일본에서 가장 인기 있는 메시징 앱으로, 월간 활성 사용자가 9,500만 명이 넘습니다. LINE 계정을 Braze와 통합하여 자사 및 타사 고객 데이터를 활용하여 고객의 선호도, 행동, 크로스채널 상호 작용을 기반으로 적합한 고객에게 매력적인 LINE 메시지를 보낼 수 있습니다. 시작하려면 [LINE]({{site.baseurl}}/line)을 참조하세요.
+
+#### Shopify: 가격 인하 및 재입고
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+이제 Shopify를 사용하면 [가격 인하]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/price_drop_notifications) 및 [품절 품목에]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications) 대한 사용자 지정 알림을 생성할 수 있습니다.
+
+ 
+### AI 및 ML 자동화
+ 
+#### 중복 사용자에 대한 규칙 기반 병합
+
+이전에는 Braze에서 중복 사용자를 개별적으로 또는 일괄적으로 찾아서 병합할 수 있었습니다. 이제 중복 확인 방법을 제어하는 규칙을 만들어 가장 관련성이 높은 사용자를 유지하도록 할 수 있습니다. 자세히 알아보려면 [규칙 기반 병합]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users/#rules-based-merging)을 참조하세요.
+
+#### AI Liquid 어시스턴트
+
+{% multi_lang_include release_type.md release="베타" %}
+
+Sage AI Liquid 어시스턴트는 메시지 콘텐츠를 개인화하는 데 필요한 Liquid를 생성하는 것을 돕는 Sage AI 기반의 채팅 도우미입니다. 템플릿에서 Liquid를 생성하고, 개인화된 Liquid 제안을 받고, Sage AI의 지원을 받아 기존 Liquid를 최적화할 수 있습니다. AI Liquid 도우미는 사용된 Liquid를 설명하는 주석도 제공하므로 Liquid에 대한 이해를 높이고 직접 작성하는 방법을 배울 수 있습니다.
+
+시작하려면 [AI Liquid 어시스턴트]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_liquid)를 참조하세요.
+ 
+### SDK
+ 
+#### Android SDK 로그
+
+앱에서 더 쉽게 읽고 사용할 수 있도록 [Braze Android SDK의 로깅 설명서]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/additional_customization_and_configuration/#logging)를 개편했습니다. 또한 각 로그 수준에 대한 설명도 추가했습니다.
+
+#### iOS SDK 포그라운드 푸시 알림
+
+이제 Braze iOS SDK의 `subscribeToUpdates` 메서드가 포그라운드 푸시 알림 수신 여부를 감지할 수 있습니다. 자세히 알아보려면 [iOS 푸시 알림 통합]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration)을 참조하세요.
+ 
+#### Xamarin 문서 업데이트
+ 
+[버전 4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/releases/tag/4.0.0)부터 Braze Xamarin SDK는 Swift SDK 바인딩을 사용하므로 코드 스니펫과 참조 자료를 업데이트했습니다. 또한 읽고 이해하기 쉽도록 섹션을 재구성했습니다. 자세한 내용은 [Xamarin 문서를]({{site.baseurl}}/developer_guide/platform_integration_guides/xamarin/initial_sdk_setup) 참조하세요.
+
+#### SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+ 
+- [Swift SDK 9.3.1](https://github.com/braze-inc/braze-swift-sdk/releases/tag/9.3.1)
+- [웹 SDK 5.3.2](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#532)
+    - 5.2.0에서 외부 스크립트가 동기식으로 로드될 때 HTML 인앱 메시지가 잘못 렌더링될 수 있는 회귀 현상을 수정했습니다.
+- [웹 SDK 5.4.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#540)
+
+## 2024년 6월 25일 출시
+
+### 일본어 문서
+
+이제 Braze Docs에서 일본어를 지원합니다!
+
+![일본어 인터페이스가 표시된 Braze Docs 사이트]({% image_buster /assets/img/braze-docs-japan.png %}){: style="max-width:70%;"}
+ 
+### 데이터 유연성
+
+#### API 트리거 캠페인용 첨부 파일
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 [`/campaigns/trigger/send` 엔드포인트]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns)에서 첨부 파일을 지원합니다(`/messages/send` 엔드포인트에서 이메일의 첨부 파일을 지원하는 것과 유사). 
+
+#### 추가 데이터 웨어하우스 지원
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+이제 Braze [클라우드 데이터 수집(CDI)]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/connected_sources)은 BigQuery, Databricks Redshift 및 Snowflake를 지원합니다.
+
+#### WhatsApp 전화번호 마이그레이션
+
+메타의 임베디드 가입을 사용하여 WhatsApp 비즈니스 계정 간에 WhatsApp 전화번호를 마이그레이션하세요. [WhatsApp 전화번호 마이그레이션]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration)에 대해 자세히 알아보세요.
+ 
+### 창의력 발휘
+
+#### 기기별 참여
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+새로운 **디바이스별 참여도** 보고서에서는 사용자가 이메일에 참여하는 데 사용하는 디바이스에 대한 분석 정보를 제공합니다. 이 데이터는 모바일, 데스크톱, 태블릿 및 기타 기기 유형에서 이메일 인게이지먼트를 추적합니다. [보고서와 이메일 성능 대시보드]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard)에 대해 자세히 알아보세요.
+
+#### 캔버스 흐름의 WhatsApp 및 SMS Liquid 속성
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[캔버스 플로우에 WhatsApp 및 SMS Liquid 속성]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties)에 대한 지원을 추가했습니다. 이제 행동 경로 단계에 "SMS 인바운드 메시지 보내기" 또는 "WhatsApp 인바운드 메시지 보내기" 트리거가 포함된 경우 후속 캔버스 단계에 SMS 또는 WhatsApp Liquid 속성정보를 포함할 수 있습니다. 이는 캔버스 플로우에서 이벤트 속성정보가 작동하는 방식을 반영합니다. 이렇게 하면 메시지를 활용하여 사용자 프로필 및 대화 메시지에 대한 퍼스트 파티 데이터를 저장하고 참조할 수 있습니다.
+ 
+#### 반복 캔버스의 개인화된 경로
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+캔버스에서 개인화된 경로를 사용하면 전환 가능성에 따라 개별 사용자에 대한 캔버스 여정의 모든 지점을 개인화할 수 있습니다. 이제 반복 캔버스에 개인화된 경로를 사용할 수 있습니다. [개인화된 이형]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths) 상품에 대해 자세히 알아보세요.
+
+#### 세그먼트 문제 해결
+
+세그먼트로 작업하시나요? 다음은 몇 가지 [문제 해결 단계 및 유의해야 할 사항]({{site.baseurl}}/user_guide/engagement_tools/segments/troubleshooting)입니다.
+
+#### 리퀴드 하이라이트
+
+접근성 가이드라인을 더 잘 지원하기 위해 [Liquid에서 사용하는 색상 코딩을]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid) 개선했습니다.
+
+![]({% image_buster /assets/img/liquid_color_code.png %})
+ 
+### 강력한 채널
+
+#### SMS 지리적 권한
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+SMS 지리적 권한은 SMS 메시지를 보낼 수 있는 국가에 대한 제어를 적용하여 보안을 강화하고 사기성 SMS 트래픽으로부터 보호합니다. 이제 관리자는 허용 국가 목록을 지정하여 SMS 메시지가 승인된 지역으로만 전송되도록 할 수 있습니다. 자세한 내용은 [SMS 지리적 권한에서]({{site.baseurl}}/sms_geographic_permissions) 확인하세요. 
+
+![가장 일반적인 국가가 상단에 표시되는 '국가 허용 목록' 드롭다운.]({% image_buster /assets/img/sms/allowlist_dropdown.png %}){: style="max-width:80%;"}
+
+#### SMS/MMS 모범 사례
+
+수신 거부 모니터링 및 트래픽 펌핑에 대한 권장 사항을 포함하여 [Braze를 사용한 SMS/MMS 모범 사례에]({{site.baseurl}}/user_guide/message_building_by_channel/sms/best_practices/best_practices) 대해 자세히 알아보세요. 
+
+#### 푸시 수신 거부 추적 기술
+
+새로운 [도움말 문서]({{site.baseurl}}/help/help_articles/push/push_unsubscribes)에서 푸시 수신 거부 추적 기술에 대한 몇 가지 팁을 확인하세요.
+
+#### Shopify `checkout.liquid` 사용 중단
+
+Shopify `checkout.liquid`에 대한 지원은 2024년 8월에 지원 중단이 시작되어 2025년 8월에 종료됩니다. Braze가 [이 전환을 어떻게 처리할지]({{site.baseurl}}/help/release_notes/deprecations/shopify_checkout) 자세히 알아보세요. 
+
+### SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+ 
+- [Swift SDK 9.3.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/9.3.0)
+    - 기존 기능 플래그 API를 더 이상 사용하지 않으며, 향후 버전에서 제거될 예정입니다.
+        - `Braze.FeatureFlag.jsonStringProperty(key:)` 는 더 이상 사용되지 않습니다.
+        - `Braze.FeatureFlag.jsonObjectProperty(key:)`는 `Braze.FeatureFlag.jsonProperty(key:)`를 위해 더 이상 사용되지 않습니다.
+- [Roku SDK 2.2.0](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md)
+- [Braze Expo 플러그인 2.1.2](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+
+#### tvOS 문서
+
+몇 달 전, 실수로 [tvOS 콘텐츠 카드]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/tvos) 및 [인앱 메시징]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/tvos)에 대한 설명서가 더 이상 사용되지 않게 되었습니다. 이 설명서는 이제 Braze 문서의 Swift 섹션에 다시 게시되었습니다.
+
+{% alert note %}
+Braze 설명서의 [기여자]({{site.baseurl}}/contributing/home)는 이제 사이트가 Ruby 3.3.0에서 실행된다는 점에 유의하세요. 필요에 따라 Ruby 버전을 업그레이드하세요.
+{% endalert %}
+
+## 2024년 5월 28일 출시
+
+### 문서 사이트의 시각적 업데이트
+
+문서 웹사이트가 멋지게 바뀐 것을 눈치채셨을 것입니다! 새롭고 활기찬 Braze의 브랜드 아이덴티티를 반영하여 개편했습니다. 새 브랜드에 대한 비하인드 스토리는 [새 브랜드 공개에서 자세히 알아보세요: Braze 수석 크리에이티브 디렉터 그렉 에르델레이와의 대화](https://www.braze.com/resources/articles/unveiling-our-new-brand-a-conversation-with-braze-executive-creative-director-greg-erdelyi).
+
+### 포르투갈어 및 스페인어 지원
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 Braze를 포르투갈어와 스페인어로 이용할 수 있습니다. Braze 대시보드가 표시되는 언어를 변경하려면 [언어 설정]({{site.baseurl}}/user_guide/administrative/access_braze/language/)을 참조하세요.
+
+### 강력한 채널
+
+#### 다국어 설정
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[다국어 설정]({{site.baseurl}}/multi_language_support/)을 조정하면 하나의 이메일 메시지 내에서 서로 다른 언어와 위치의 사용자를 대상으로 서로 다른 메시지를 보낼 수 있습니다. 다국어 지원을 편집하고 관리하려면 "다국어 설정 관리" 사용자 권한이 있어야 합니다. 메시지에 로캘을 추가하려면 캠페인을 편집할 수 있는 권한이 필요합니다.
+
+#### 메시지 수준의 원클릭 목록-수신 취소 헤더
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+목록 수신 거부 헤더([RFC 8058](https://datatracker.ietf.org/doc/html/rfc8058))의 원클릭 수신 거부 기능은 수신자가 이메일을 쉽게 수신 거부할 수 있는 방법을 제공합니다. 이 헤더 설정을 이메일의 메시지 수준에서 적용하도록 조정할 수 있습니다. 이 설정에 대한 자세한 내용은 [워크스페이스의 이메일 수신 거부 헤더]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#email-unsubscribe-header-in-workspaces)를 참조하세요.
+
+#### 이메일 살균 정보
+
+Braze가 이메일 메시지에서 특정 유형의 JavaScript를 감지할 때 발생하는 프로세스에 대해 자세히 알아보려면 새로운 [위생 처리]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/sanitization) 문서를 참조하세요. 주요 목적은 악의적인 공격자가 다른 Braze 대시보드 사용자의 세션 데이터에 액세스하는 것을 방지하는 것입니다.
+
+#### 콘텐츠 블록의 포함 횟수
+
+활성 캠페인 또는 캔버스에 콘텐츠 블록을 추가한 후 콘텐츠 블록을 마우스로 가리키고 <i class="fa fa-eye preview-icon"></i> **미리보기** 아이콘을 선택하면 콘텐츠 블록 라이브러리에서 [이 콘텐츠 블록을 미리 볼]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/) 수 있습니다.
+
+#### 캔버스 상태
+
+Braze 대시보드에서 캔버스는 상태별로 그룹화되어 있습니다. 다양한 [캔버스 상태와]({{site.baseurl}}/user_guide/engagement_tools/canvas/get_started/canvas_status) 그 의미에 대한 [설명을]({{site.baseurl}}/user_guide/engagement_tools/canvas/get_started/canvas_status) 확인하세요.
+
+### AI 및 ML 자동화
+
+#### AI 카피라이팅 어시스턴트를 위한 브랜드 가이드라인
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 [브랜드 가이드라인]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines/)을 생성하고 적용하여 AI 카피라이팅 어시스턴트가 생성한 카피 스타일을 브랜드에 맞게 맞춤 설정할 수 있습니다. 다양한 시나리오에 대해 여러 가지 가이드라인을 설정하여 항상 상황에 맞는 어조를 유지할 수 있습니다.
+ 
+### 새로운 Braze 파트너십
+
+#### Adikteev - 애널리틱스
+
+Braze와 [Adikteev의]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/adikteev/) 통합을 통해 Braze CRM 캠페인 내에서 Adikteev의 이탈 예측 기술을 활용하여 고위험 사용자 세그먼트를 우선적으로 타겟팅함으로써 사용자 유지율을 높일 수 있습니다.
+ 
+#### Celebrus - 애널리틱스
+ 
+Braze와 [Celebrus]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/celebrus) 통합은 웹 및 모바일 앱 채널 전반에서 Braze SDK와 원활하게 통합되어 채널 활동 데이터로 Braze의 인구를 늘리는 데 도움이 됩니다. 여기에는 지정된 기간 동안 디지털 자산 전반의 방문자 트래픽에 대한 포괄적인 인사이트가 포함됩니다.
+ 
+#### IAM Studio - 메시지 템플릿
+ 
+Braze와 [IAM Studio의]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/iam_studio/) 통합을 통해 이미지 교체, 텍스트 수정, 딥링크 설정, 사용자 지정 속성 및 이벤트 설정을 제공하는 사용자 지정 가능한 인앱 메시지 템플릿을 Braze 인앱 메시지에 쉽게 삽입할 수 있습니다. IAM Studio를 사용하면 메시지 제작 시간을 단축하고 콘텐츠 기획에 더 많은 시간을 할애할 수 있습니다.
+ 
+#### Regal - 인스턴트 채팅
+
+Braze와 [Regal]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/regal/)을 통합하면 모든 고객 터치포인트에서 보다 일관되고 개인화된 경험을 제공할 수 있습니다.
+
+#### Treasure Data - 코호트 가져오기
+ 
+Braze와 [Treasure Data]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/treasuredata/) 통합을 통해 사용자 코호트를 Treasure Data에서 Braze로 가져올 수 있으므로, 웨어하우스에만 존재할 수 있는 데이터를 기반으로 타겟팅 캠페인을 보낼 수 있습니다.
+ 
+#### Zapier - 워크플로 자동화
+ 
+Braze와 [Zapier의]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/zapier/) 파트너십은 Braze API와 Braze 웹훅을 활용하여 타사 애플리케이션과 연결하여 다양한 작업을 자동화합니다.
+
+### SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Android SDK 31.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [Braze 세그먼트 Swift 플러그인 3.0.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md#300)
+    - 9.2.0+ SemVer 버전 이상의 릴리스가 필요하도록 Braze Swift SDK 바인딩을 업데이트합니다.
+        - 이를 통해 9.2.0부터 10.0.0까지 모든 버전의 Braze SDK와 호환됩니다(단, 10.0.0은 포함되지 않음).
+        - 잠재적인 변경 사항에 대한 자세한 내용은 [7.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#700), [8.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#800) 및 [9.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#900)의 체인지로그 항목을 참조하세요.
+    - 이제 푸시 알림을 지원하려면 앱 수명 주기 초기에 애플리케이션의 `AppDelegate.application(_:didFinishLaunchingWithOptions:)` 메서드에서 정적 메서드 `BrazeDestination.prepareForDelayedInitialization()`을 호출해야 합니다.
+- [Cordova SDK 9.0.0-9.2.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
+    - [Braze Swift SDK 7.7.0에서 9.0.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 네이티브 iOS 브릿지를 업데이트했습니다.
+- [Expo 플러그인 2.1.1](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md#211)
+- [Flutter SDK 10.1.0](https://pub.dev/packages/braze_plugin/changelog)
+- [React Native SDK 11.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/11.0.0/CHANGELOG.md)
+- [Swift SDK 9.1.0-9.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#920)
+- Unity 6.0.0
+    - [Braze Swift SDK 7.7.0에서 9.0.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 네이티브 iOS 브릿지를 업데이트했습니다.
+    - 네이티브 Android 브릿지를 [Braze Android SDK 29.0.1에서 30.3.0으로](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트했습니다.
+- [웹 SDK 5.3.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- Xamarin SDK 버전 5.0.0
+    - [Braze Swift SDK 8.4.0에서 9.0.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/8.4.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) iOS 바인딩을 업데이트했습니다.
+
+## 2024년 4월 30일 출시
+
+### 프로모션 코드 목록을 생성하거나 업데이트할 수 있는 권한
+
+2024년 4월부터 사용자는 프로모션 코드 목록을 만들거나 업데이트하려면 '캠페인, 캔버스, 카드, 세그먼트, 미디어 라이브러리에 액세스' 권한이 필요합니다. 권한 이름과 설명에 대한 목록은 [제한된 권한 및 팀 역할 권한 관리하기]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#managing-limited-and-team-role-permissions)를 참조하세요.
+
+### 데이터 유연성
+
+#### SAML 적시 프로비저닝
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+[적시 프로비저닝은 SAML SSO와 함께 작동하여 새로운 대시보드 사용자가 처음 로그인할 때 Braze 계정을 만들 수 있도록 합니다. 따라서 관리자가 새 대시보드 사용자의 계정을 수동으로 만들고, 권한을 선택하고, 워크스페이스에 할당하고, 사용자가 계정을 활성화할 때까지 기다릴 필요가 없습니다.
+
+#### 권한 집합 및 역할
+
+[권한 세트]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#permission-sets-and-roles)를 사용하여 특정 주제 영역 또는 작업과 관련된 권한을 묶을 수 있습니다. 이러한 권한 집합은 여러 워크스페이스에서 동일한 액세스 권한이 필요한 대시보드 사용자에게 적용할 수 있습니다.
+
+#### 클라우드 데이터 수집 세그먼트
+
+Braze [클라우드 데이터 수집 세그먼트를]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/cdi_segments) 사용하면 CDI 연결을 통해 제공되는 데이터를 사용하여 자체 데이터 웨어하우스에 직접 쿼리하는 SQL을 작성하고, Braze 내에서 타겟팅할 수 있는 사용자 그룹을 만들 수 있습니다.
+
+### 창의력 발휘
+
+### 쿼리 빌더 템플릿
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+쿼리 빌더 템플릿을 사용하면 Snowflake의 Braze 데이터를 사용하여 보고서를 만들 수 있습니다. [쿼리 빌더]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/) 템플릿에 액세스하려면 보고서를 만들 때 **쿼리 템플릿**을 선택합니다. 모든 템플릿은 최대 최근 60일까지의 데이터를 표시하지만 편집기에서 해당 값과 다른 값을 직접 편집할 수 있습니다.
+
+### 세그먼트별 성능 데이터
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+캠페인, 배리언트, 캔버스 및 세그먼트별 캔버스 단계에 대한 쿼리 빌더 보고서 템플릿에서 [성과 데이터]({{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/#performance-data-by-segment)를 세그먼트별로 분류할 수 있습니다.
+
+### 강력한 채널
+
+#### SMS 메시징을 위한 자동 링크 단축
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[자동 링크 단축을]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/keyword_handling/?tab=manage%20responses#managing-keywords-and-auto-responses) 사용하여 응답에서 정적 URL을 자동으로 단축할 수 있습니다. 이렇게 하면 문자 카운터가 단축된 URL의 예상 길이를 표시하도록 업데이트되므로 응답을 구체화하는 데 도움이 될 수 있습니다.
+
+### 새로운 Braze 파트너십
+
+#### Friendbuy - 로열티
+
+Braze와 [Friendbuy의]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/friendbuy/) 통합을 활용하여 이메일 및 SMS 기능을 확장하는 동시에 추천 및 로열티 프로그램 커뮤니케이션을 손쉽게 자동화할 수 있습니다. Braze는 Friendbuy를 통해 수집된 모든 옵트인 전화번호에 대한 고객 프로필을 생성합니다.
+
+### NiftyImages - 동적 콘텐츠
+
+Braze와 [NiftyImages]({{site.baseurl}}/partners/message_personalization/dynamic_content/niftyimages/)의 파트너십을 통해 기존 Braze 개인화된 태그를 NiftyImages URL에 매핑하여 이메일 캠페인을 위한 역동적인 개인화 이미지를 만들 수 있습니다.
+
+### SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Android SDK 30.4.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [Braze 세그먼트 Swift 플러그인 2.4.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md#240)
+- [Flutter SDK 9.0.0](https://pub.dev/packages/braze_plugin/changelog)
+    - 네이티브 iOS 브릿지를 [Braze Swift SDK 7.7.0에서 8.4.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...8.4.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트합니다.
+        - 최소 iOS 배포 대상이 12.0으로 업데이트되었습니다.
+    - 네이티브 Android 브릿지를 [Braze Android SDK 29.0.1에서 30.3.0으로](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트합니다.
+    - 지원되는 최소 Dart 버전은 2.15.0입니다.
+- [React Native SDK 9.2.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+- [Swift SDK 8.3.0-8.4.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+- [Swift SDK 9.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+    - BrazeKit 개인정보 매니페스트에서 기본 개인정보 추적 도메인을 제거합니다.
+        - Braze [데이터 추적 기술 기능]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest/)을 사용하는 경우, 앱 수준의 개인정보 매니페스트에 추적 기술 엔드포인트를 수동으로 추가해야 합니다.
+        - 통합 지침은 업데이트된 [튜토리얼](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/e1-privacy-tracking)을 참조하세요.
+    - 더 이상 사용되지 않는 `BrazeDelegate.braze(_:sdkAuthenticationFailedWithError) method in favor of BrazeSDKAuthDelegate.braze(_:sdkAuthenticationFailedWithError)` 을 제거합니다.
+        - 이 방법은 원래 [릴리스 5.14.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/5.14.0)에서 더 이상 사용되지 않았습니다.
+        - 새 델리게이트 메서드로 전환하지 않으면 컴파일러 오류가 트리거되지 않고 정의한 `BrazeDelegate.braze(_:sdkAuthenticationFailedWithError)` 메서드가 호출되지 않을 뿐입니다.
+- [Xamarin SDK 버전 4.0.3](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md#403)
+
+## 2024년 4월 2일 출시
+
+### WhatsApp
+
+#### 여러 비즈니스 계정
+
+이제 각 워크스페이스에 여러 개의 WhatsApp 비즈니스 계정과 구독 그룹을 추가할 수 있습니다. 전체 안내는 [여러 개의 WhatsApp 비즈니스 계정 및 전화번호]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups/)를 참조하세요.
+
+#### 읽기 속도
+
+WhatsApp은 인도의 소비자들을 시작으로 보다 가치 있는 경험을 제공하고 기업의 마케팅 대화 참여를 극대화하기 위해 새로운 접근 방식을 테스트하고 있습니다. 여기에는 특정 기간 동안 특정 비즈니스에서 개인이 받는 마케팅 대화 수를 제한하는 것이 포함될 수 있으며, 읽을 가능성이 적은 소수의 대화부터 시작합니다. 자세한 내용은 [메타 리소스를]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/meta_resources/) 참조하세요.
+
+### 데이터 유연성
+
+#### Amazon S3 버킷을 Braze에 동기화하기
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+이제 S3용 클라우드 데이터 수집을 사용하여 AWS 계정에 있는 하나 이상의 S3 버킷을 Braze와 직접 통합할 수 있습니다. 새 파일이 S3에 게시되면 SQS에 메시지가 게시되고 Braze 클라우드 데이터 수집이 해당 새 파일을 받습니다. 자세한 내용은 [파일 스토리지 통합]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/file_integrations/)을 참조하세요.
+
+#### Shopify OAuth
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+Shopify는 모든 규모의 소매 비즈니스를 시작, 성장, 마케팅 및 관리할 수 있는 신뢰할 수 있는 도구를 제공하는 선도적인 글로벌 상거래 기업입니다. 이제 Braze용 Shopify를 설정할 때 [워크스페이스에 OAuth를 사용하도록]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/) 설정할 수 있습니다.
+
+#### iOS용 Expo 푸시 알림 사용
+
+React Native와 함께 Expo를 사용하여 iOS 앱에 리치 푸시 알림 및 푸시 스토리를 통합하는 [방법을 추가했습니다]({{site.baseurl}}/developer_guide/platform_integration_guides/react_native/push_notifications/?tab=expo).
+
+#### iOS 라이브 활동 원격 시작
+
+이제 [`/messages/live_activity/start`]({{site.baseurl}}/api/endpoints/messaging/live_activity/start/) 엔드포인트를 사용하여 iOS에서 라이브 활동을 원격으로 시작할 수 있습니다. 전체 안내는 [라이브 활동: ]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/#step-2-start-the-activity) 활동 시작을 참고하세요.
+
+### AI 및 ML 자동화
+
+#### 항목 추천
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+이제 Braze의 Sage AI를 사용하면 가장 인기 있는 제품을 계산하거나 특정 카탈로그에 대한 개인화된 AI 추천을 생성할 수 있습니다. 자세한 내용은 [항목 추천 정보를]({{site.baseurl}}/user_guide/sage_ai/recommendations/about_item_recommendations/) 참조하세요.
+
+#### QA 인앱 메시지 콘텐츠
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이전에는 Braze 대시보드에서 Sage AI를 사용하여 SMS 및 푸시 알림 콘텐츠에 대한 품질 보증을 수행할 수 있었습니다. 이제 [인앱 메시지 콘텐츠도 QA할]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_content_qa/) 수 있습니다.
+
+### 새로운 Braze 파트너십
+
+#### 인구조사 - 코호트 가져오기
+
+이제 Snowflake, BigQuery와 같은 클라우드 데이터 웨어하우스를 Braze에 연결하는 데이터 활성화 플랫폼인 [Census로 코호트 사용자를 가져올]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/census/) 수 있습니다. 마케팅 팀은 퍼스트 파티 데이터를 활용하여 동적 오디언스 세그먼트를 구축하고, 고객 속성을 동기화하여 캠페인을 맞춤화하며, Braze의 모든 데이터를 최신 상태로 유지할 수 있습니다.
+
+### SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [React Native 9.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+  - React Native 최소 버전을 0.71.0으로 업데이트했습니다.
+  - iOS 최소 버전을 12.0으로 업데이트했습니다.
+  - Braze Swift SDK 8.1.0을 사용하도록 iOS 바인딩을 업데이트했습니다.
+  - Braze Android SDK 30.1.1을 사용하도록 Android 바인딩을 업데이트했습니다.
+
+## 2024년 3월 5일 출시
+
+### Google EU 사용자 동의 정책
+
+Google은 2024년 3월 6일부터 시행되는 [디지털 시장법(DMA)](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html) 개정 사항에 따라 [EU 사용자 동의 정책](https://www.google.com/about/company/user-consent-policy/)을 업데이트하고 있습니다. 이 새로운 변경 사항에 따라 광고주는 EEA 및 영국 최종 사용자에게 특정 정보를 공개하고 해당 사용자로부터 필요한 동의를 얻어야 합니다. 곧 변경될 사항의 일환으로, [Braze에서 두 동의 신호를 모두 커스텀 속성으로 수집]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)할 수 있습니다. Braze는 이러한 커스텀 속성의 데이터를 Google의 적절한 동의 필드에 동기화합니다.
+
+### 데이터 유연성
+
+#### 중복 사용자 병합
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+이제 Braze 대시보드에서 [중복 사용자를 검색하고 병합하여]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users) 캠페인과 캔버스의 효과를 극대화할 수 있습니다. 사용자 프로필을 개별적으로 병합하거나 식별자가 일치하는 모든 프로필을 가장 최근에 업데이트된 사용자 프로필로 병합하는 일괄 병합을 수행할 수 있습니다.
+
+#### 보관된 콘텐츠 검색
+
+이제 Braze 대시보드에서 **아카이브된 콘텐츠 표시**를 선택하여 [검색 결과에 아카이브된 콘텐츠]({{site.baseurl}}/user_guide/administrative/access_braze/global_search/#filter-for-archived-content)를 포함할 수 있습니다.
+
+#### AWS S3 및 Google Cloud Storage에 대한 메시지 아카이빙 지원
+
+[메시지 보관을]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/) 사용하여 보관 또는 규정 준수 목적으로 사용자에게 보낸 메시지의 사본을 AWS S3 버킷, Azure Blob Storage 컨테이너 또는 Google Cloud Storage 버킷에 저장할 수 있습니다.
+
+#### SQL 테이블 참조
+
+쿼리 빌더에서 또는 SQL 세그먼트 확장을 생성할 때 쿼리할 수 있는 테이블과 열을 보려면 [SQL 테이블 참조]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/sql_segments_tables/)를 방문하세요.
+
+### 창의력 발휘
+
+#### AI 카피라이팅을 위한 톤 제어
+
+이제 AI 카피라이팅 어시스턴트로 생성된 카피의 스타일을 결정하기 위해 [메시지 톤]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/#steps)을 선택할 수 있습니다.
+
+### 강력한 채널
+
+#### 카드 생성
+
+카드 [생성]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/) 시기를 지정하여 Braze가 새 콘텐츠 카드 캠페인 및 캔버스 단계에 대한 오디언스 자격 및 개인화를 평가하는 시기를 선택할 수 있습니다. 
+
+#### 사용자 경로 미리보기
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+사용자가 받게 될 메시지와 타이밍을 미리 보는 등 사용자를 위해 만든 캔버스 여정을 경험해 보세요. 이러한 [테스트 실행]({{site.baseurl}}/preview_user_paths/)은 캔버스를 보내기 전에 메시지가 올바른 오디언스에게 전송되는지 확인하는 품질 보증 역할을 합니다.
+
+#### 빠른 푸시 캠페인
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+Braze에서 푸시 캠페인을 만들 때 여러 플랫폼과 기기를 선택하여 [퀵 푸시]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/quick_push/)라는 단일 편집 환경에서 모든 플랫폼에 하나의 메시지를 작성할 수 있습니다. 이 기능은 캠페인에만 사용할 수 있습니다.
+
+#### 사용자 지정 List-Unsubscribe 헤더
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이메일 메시징에 [커스텀 목록 수신 거부 헤더]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#custom-list-unsubscribe-header)를 추가하면 수신자가 수신 거부할 수 있습니다. 이렇게 하면 직접 구성한 원클릭 수신 거부 엔드포인트와 선택 사항인 "mailto:"를 추가할 수 있습니다. 원클릭 수신 거부 HTTP는 대량 발신자에 대한 Yahoo 및 Gmail의 요구 사항이므로 Braze는 커스텀 목록 수신 거부 헤더를 지원하기 위해 URL을 입력해야 합니다.
+
+#### 인앱 메시지를 위한 여러 페이지
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+[인앱 메시지에 페이지를 추가하면]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/#multi-page) 온보딩 흐름이나 환영 여정과 같은 순차적인 흐름을 통해 사용자를 안내할 수 있습니다. **빌드** 탭의 **페이지** 섹션에서 페이지를 관리할 수 있습니다.
+
+#### 실험 경로에 대한 경로 무작위화
+
+실험 경로 단계의 [경로 할당을 항상 무작위로 지정]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step)하려면 단계의 **실험 경로에서 무작위 경로를** 선택합니다. 이 옵션은 위닝 또는 개인화된 경로를 사용할 때는 사용할 수 없습니다.
+
+#### 이메일 캡처 양식
+
+[이메일 캡처 메시지를]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form/) 사용하면 사이트 사용자에게 이메일 주소를 제출하라는 메시지를 쉽게 보낼 수 있으며, 이후에는 모든 메시징 캠페인에서 사용할 수 있도록 사용자 프로필에서 해당 주소를 사용할 수 있습니다.
+
+### SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [AppboyKit iOS SDK 4.7.0](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.7.0)
+    - 이는 2024년 3월 1일([Swift SDK](https://github.com/braze-inc/braze-swift-sdk/) 사용을 위해) 서비스 종료 이전에 Objective-C SDK의 마지막 릴리스가 될 것입니다.
+    - SDWebImage의 최소 요구 버전을 5.8.2에서 5.18.7로 업데이트합니다. 이 버전에는 [개인정보에 영향을 미치는 SDK 목록](https://developer.apple.com/support/third-party-SDK-requirements/)에 표시되는 SDWebImage에 대한 개인정보 매니페스트가 포함되어 있습니다.
+- [Flutter SDK 8.1.0](https://pub.dev/packages/braze_plugin/changelog)
+- [Unity 5.2.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
+- [React Native SDK 8.4.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.4.0/CHANGELOG.md)
+- [Xamarin SDK 버전 4.0.2](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
+- [Swift SDK 7.7.0-8.0.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#801)
+- [Android SDK 30.1.0-30.2.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [웹 SDK 5.1.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- [Cordova SDK 8.0.0-Cordova SDK 8.1.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
+    - 네이티브 Android 브릿지를 [Braze Android SDK 27.0.1에서 30.0.0으로](https://github.com/braze-inc/braze-android-sdk/compare/v27.0.0...v30.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트했습니다.
+    - [Braze Swift SDK 6.6.0에서 7.6.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/6.6.0...7.6.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 네이티브 iOS 브릿지를 업데이트했습니다.
+    - `Banner` 콘텐츠 카드 유형 이름을 `ImageOnly` 으로 변경했습니다:
+        - `ContentCardTypes.BANNER`부터 `ContentCardTypes.IMAGE_ONLY`까지
+        - Android에서 프로젝트의 XML 파일에 콘텐츠 카드용 배너라는 단어가 포함된 경우 `image_only`로 대체해야 합니다.
+    - `BrazePlugin.getFeatureFlag(id)`는 이제 기능 플래그가 존재하지 않으면 `null`을 반환합니다.
+    - `BrazePlugin.subscribeToFeatureFlagsUpdates(function)`는 새로 고침 요청이 성공 또는 실패로 완료된 경우와 현재 세션에서 이전에 캐시된 데이터가 있는 경우 최초 구독 시에만 트리거됩니다.
+    - 더 이상 사용되지 않는 메서드 `registerAppboyPushMessages` 를 제거했습니다. 대신 `setRegisteredPushToken` 을 사용하세요.
+
+## 2024년 2월 6일 출시
+
+### Braze 프라이버시 매니페스트
+
+Braze는 신고된 추적 기술 데이터를 전용 `-tracking` 엔드포인트로 자동 리라우팅하는 유연한 새 API와 함께 자체 개인정보처리방침을 공개했습니다. 자세한 내용은 [Braze 개인정보취급방침]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest)을 참조하세요.
+
+### Google EU 사용자 동의 정책
+
+Google은 2024년 3월 6일부터 시행되는 [디지털 시장법(DMA)](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)의 변경사항에 따라 [EU 사용자 동의 정책](https://www.google.com/about/company/user-consent-policy/)을 업데이트합니다. 이 새로운 변경 사항에 따라 광고주는 EEA 및 영국 최종 사용자에게 특정 정보를 공개하고 해당 사용자로부터 필요한 동의를 얻어야 합니다. 곧 변경될 사항의 일환으로, [Braze에서 두 동의 신호를 모두 커스텀 속성으로 수집]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)할 수 있습니다. Braze는 이러한 커스텀 속성의 데이터를 Google의 적절한 동의 필드에 동기화합니다.
+
+### 데이터 유연성
+
+#### Google 파이어베이스 클라우드 메시징(FCM) API
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 [더 이상 사용되지 않는 Google의 클라우드 메시징 API에서 완전히 지원되는 Firebase 클라우드 메시징(FCM) API로 마이그레이션할]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/) 수 있습니다. 
+
+#### Braze 클라우드 데이터 수집(CDI) 엔드포인트
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+Braze CDI 엔드포인트를 사용하려면
+- [기존 연동 목록을 반환합니다]({{site.baseurl}}/api/endpoints/cdi/get_integration_list/).
+- 지정된 통합에 대한 [과거 동기화 상태 목록을 반환합니다]({{site.baseurl}}/api/endpoints/cdi/get_job_sync_status/).
+- 지정된 통합에 대한 [동기화를 트리거합니다]({{site.baseurl}}/api/endpoints/cdi/post_job_sync/).
+
+#### Databricks용 Braze 클라우드 데이터 수집(CDI) 지원
+
+이제 [Databricks 데이터 소스에서]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/sync_catalogs_data/#step-2-integrate-cloud-data-ingestion-with-catalog-data) 카탈로그에 대한 Braze CDI 지원을 사용할 수 있습니다.
+
+#### 수동 Swift SDK 통합
+
+통합 가이드에 [수동 통합]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration) 문서를 추가하여 패키지 관리자를 사용하지 않고 Swift SDK를 수동으로 통합하는 방법을 설명했습니다.
+
+#### 사용 중단
+
+2024년 1월 11일, Braze는 Windows 앱과 Baidu 앱에서 메시지 서비스 및 데이터 수집을 중단했습니다.
+
+### 창의력 발휘
+
+#### SQL 세그먼트 확장 사용 사례
+
+[SQL 세그먼트 확장 사용 사례]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/use_cases) 라이브러리에는 자체 SQL 쿼리를 만들 때 영감을 얻기 위해 사용할 수 있는 SQL 세그먼트 확장에 대한 테스트된 쿼리가 포함되어 있습니다.
+
+### 강력한 채널
+
+#### 사용자 지정 코드 블록
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[사용자 지정 코드 블록을]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/editor_blocks/#custom-code) 사용하면 인앱 메시지에 HTML, CSS 및 JavaScript를 추가, 편집 또는 삭제할 수 있습니다.
+
+#### 푸시 알림의 페이로드 크기 줄이기
+
+새로운 도움말 문서 [알림 페이로드 크기]({{site.baseurl}}/help/help_articles/push/reducing_payload_size#reducing-push-notification-payload-size)에서는 푸시 페이로드 크기 제한으로 인해 캠페인 또는 캔버스 단계를 시작할 수 없는 경우 푸시 알림의 페이로드 크기를 줄일 수 있는 몇 가지 팁을 제공합니다.
+
+#### 캠페인 또는 캔버스에 BCC 주소 추가하기
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이메일 메시지에 숨은 참조 [주소를]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/?tab=bcc%20address#outbound-email-settings) 추가할 수 있습니다. 이렇게 하면 사용자가 받은 메시지의 동일한 사본이 사용자의 BCC 받은편지함으로 전송됩니다. 이를 통해 규정 준수 요구 사항이나 고객 지원 문제를 위해 사용자에게 보낸 메시지의 사본을 보관할 수 있습니다.
+
+#### 이메일의 원클릭 수신 거부 링크
+
+[목록 수신 거부 헤더]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#list-unsubscribe-header)를 사용하면 메시지 본문이 아닌 사서함 UI 내에 수신 **거부** 버튼을 표시하여 수신자가 클릭 한 번으로 마케팅 이메일의 수신을 거부할 수 있습니다.
+
+### 새로운 Braze 파트너십
+
+#### Criteo - 캔버스 오디언스 동기화
+
+브랜드는 [Braze 오디언스 싱크 투 Criteo]({{site.baseurl}}/partners/canvas_steps/criteo_audience_sync/)를 사용하여 자체 Braze 통합의 사용자 데이터를 Criteo 고객 목록에 추가하여 행동 트리거, 세분화 등을 기반으로 광고를 게재할 수 있습니다. 사용자 데이터를 기반으로 Braze 캔버스에서 메시지(푸시, 이메일, SMS, 웹훅 등)를 트리거하는 데 일반적으로 사용하는 모든 기준을 이제 Criteo 고객 목록에서 해당 사용자에게 광고를 트리거하는 데 사용할 수 있습니다.
+
+#### 이동식 잉크 - 동적 콘텐츠
+
+[무버블 잉크]({{site.baseurl}}/partners/message_personalization/dynamic_content/movable_ink#movable-ink) 고객 데이터 API 통합을 통해 마케터는 Braze에 저장된 고객 이벤트 데이터를 활성화하여 무버블 잉크 내에서 개인화된 콘텐츠를 생성할 수 있습니다.
+
+#### 스쿠버 애널리틱스 - 분석
+
+[Scuba 분석]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/scuba#scuba-analytics)은 고속 시계열 데이터를 위해 설계된 풀스택 머신 러닝 기반 데이터 협업 플랫폼입니다. Scuba를 사용하면 사용자(액터라고도 함)를 선택적으로 내보내고 Braze 플랫폼에 로드할 수 있습니다. Scuba에서는 커스텀 액터 속성을 사용하여 행동 추세를 분석하고, 다양한 플랫폼에서 데이터를 활성화하고, 머신 러닝을 사용하여 예측 모델링을 수행합니다.
+
+### SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+ 
+- [Expo 플러그인 2.0.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+    - [엑스포 SDK 50 요구 사항](https://expo.dev/changelog/2024/01-18-sdk-50)에 따라 iOS 최소 플랫폼 버전을 `13.4`로 상향 조정합니다.
+    - 이 버전은 Expo SDK 50을 완벽하게 지원하려면 Braze React Native SDK 버전 [8.3.0 이상](https://github.com/braze-inc/braze-react-native-sdk/releases/tag/8.3.0)이 필요합니다.
+- [React Native SDK 8.3.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.3.0/CHANGELOG.md)
+- [Unity SDK 5.1.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
+- [Android SDK 30.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+    - 인앱 메시지에 사용되는 웹뷰가 `WebViewAssetLoader`를 사용하도록 업데이트되었습니다.
+        - `WebSettings.allowFileAccess`는 이제 `InAppMessageHtmlBaseView` 및 `BrazeWebViewActivity`에서 false로 설정됩니다.
+        - 직접 `InAppMessageWebViewClient` 또는 `InAppMessageHtmlBaseView` 을 사용하는 경우 원본 클래스와 비교하여 구현이 에셋을 올바르게 로드하고 있는지 확인하세요.
+        - 사용자 정의 클래스를 사용하지 않는 경우 모든 것이 이전과 동일하게 작동합니다.
+- [Braze Swift SDK 6.6.2](https://github.com/braze-inc/braze-swift-sdk/blob/6.6.2/CHANGELOG.md)
+- [Braze Swift SDK 7.6.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0)
+- [Xamarin SDK 버전 3.0.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
+    - NuGet 패키지의 이름이 `AppboyPlatformXamariniOSBinding`에서 [`BrazePlatform.BrazeiOSBinding`](https://www.nuget.org/packages/BrazePlatform.BrazeiOSBinding/)으로 변경되었습니다.
+        - 업데이트된 패키지를 사용하려면 `AppboyPlatformXamariniOSBinding;` 사용 인스턴스를 Braze 사용으로 바꾸세요
+    - 이 버전에서는 .NET 6+를 사용해야 하며 Xamarin 프레임워크를 사용하는 프로젝트에 대한 지원이 제거됩니다. Xamarin 지원 종료에 대한 [Microsoft의 정책](https://dotnet.microsoft.com/en-us/platform/support/policy/xamarin)을 참조하세요.
+    - Android 바인딩을 [Braze Android SDK 26.3.2에서 29.0.1로](https://github.com/braze-inc/braze-android-sdk/compare/v26.3.1...v29.0.1#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트했습니다.
+- [Xamarin SDK 4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
+    - 이 버전에서는 iOS 바인딩이 [Braze Swift SDK를](https://github.com/braze-inc/braze-swift-sdk/) 사용하도록 업데이트됩니다. 대부분의 iOS 공용 API가 변경되었으므로, 대체 사용에 대한 안내는 [마이그레이션 가이드](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/appboy-migration-guide/) (Swift)를 참조하세요. 기존 공개 API를 계속 사용할 수 있도록 호환성 바인딩을 제공합니다.
+        - 이제 iOS 바인딩은 여러 모듈로 구성됩니다:
+            - **BrazeKit:** 분석 및 푸시 알림을 지원하는 기본 SDK 라이브러리(nuget: [Braze.iOS.BrazeKit](https://www.nuget.org/packages/Braze.iOS.BrazeKit)).
+            - BrazeUI: 인앱 메시지 및 콘텐츠 카드를 위한 Braze 제공 사용자 인터페이스 라이브러리(nuget: [Braze.iOS.BrazeUI](https://www.nuget.org/packages/Braze.iOS.BrazeUI)).
+            - BrazeLocation: 위치 분석 및 지오펜스 모니터링을 지원하는 위치 라이브러리(nuget: [Braze.iOS.BrazeLocation](https://www.nuget.org/packages/Braze.iOS.BrazeLocation)).
+            - BrazeKitCompat: 4.0.0 이전 API를 지원하는 호환성 라이브러리(nuget: [Braze.iOS.BrazeKitCompat](https://www.nuget.org/packages/Braze.iOS.BrazeKitCompat)).
+            - BrazeUICompat: 4.0.0 이전 UI API를 지원하는 호환성 라이브러리(nuget: [Braze.iOS.BrazeUICompat](https://www.nuget.org/packages/Braze.iOS.BrazeUICompat)).
+        - 새로운 통합에 대해서는 BrazeiOSMauiSampleApp을, 호환성 모듈의 사용법에 대해서는 BrazeiOSMauiCompatSampleApp을 참조하세요.
+    - [Braze Swift SDK 7.6.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0)에 대한 iOS 바인딩을 업데이트했습니다.
+    - iOS 바인딩을 사용하려면 Xcode 15와의 호환성을 위해 .NET 7을 사용해야 합니다.
+- [Xamarin SDK 4.0.1](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
+
+## 2024년 1월 9일 출시
+
+### 업데이트된 Shopify 통합 문서
+
+다음을 포함하여 Braze와 Shopify 통합 설명서의 섹션을 업데이트했습니다:
+
+- [Shopify 시작하기]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/)
+- [Braze에서 Shopify 설정]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/)
+- [Shopify 사용자 ID 관리]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_user_identity/)
+
+### 데이터 유연성
+
+#### 카탈로그의 재고 부족 알림
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+카탈로그와 캔버스를 통한 [품절 알림을]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications/) 조합하여 품목의 품절 시 고객에게 알릴 수 있습니다. 고객이 선택한 커스텀 이벤트를 수행할 때마다 아이템이 보충될 때마다 자동으로 알림을 받도록 구독할 수 있습니다.
+
+#### 카탈로그 세그먼트
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+[카탈로그 세그먼트는]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/catalog_segments/) SQL 세그먼트 확장의 카탈로그 데이터를 기반으로 하는 사용자 대상입니다. 이러한 SQL 세그먼트 확장은 세그먼트에서 참조한 다음 캠페인 및 캔버스에서 타겟팅할 수 있습니다. 카탈로그 세그먼트는 SQL을 사용하여 카탈로그의 데이터와 사용자 지정 이벤트 또는 구매의 데이터를 조인합니다. 이렇게 하려면 카탈로그와 커스텀 이벤트 또는 구매에 공통 식별자 필드가 있어야 합니다.
+
+#### Firebase Cloud 메시징 API로 마이그레이션하기
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+더 이상 사용되지 않는 Google의 클라우드 메시징 API에서 완전히 지원되는 Firebase 클라우드 메시징(FCM) API로 [마이그레이션하는 방법을]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/) 알아보세요.
+
+### SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Swift SDK 7.5.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+    - Braze의 데이터 수집 정책을 설명하기 위해 `BrazeKit` 및 `BrazeLocation`에 대한 개인정보처리방침을 추가합니다. 자세한 내용은 Apple의 개인정보처리방침 [설명서](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests)를 참조하세요. 데이터 수집 관행을 관리하기 위한 더 많은 구성은 향후 릴리스에서 제공될 예정입니다.
+    - 7.1.0에 도입된 XC프레임워크의 코드 서명 관련 문제를 수정합니다.
+- [웹 SDK v5.1.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- [Unity SDK 5.0.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
+    - Braze Swift SDK 6.1.0에서 7.4.0으로 네이티브 iOS 브릿지를 업데이트했습니다.
+        - 이제 iOS 리포지토리 링크는 이 [리포지토리](https://github.com/braze-inc/braze-swift-sdk-prebuilt-dynamic)에서 미리 빌드된 동적 XC프레임웍스를 가리킵니다.
+    - 네이티브 Android 브릿지를 Braze Android SDK 27.0.1에서 29.0.1로 업데이트했습니다.
+    - `AppboyBinding.GetFeatureFlag(string id)`는 이제 기능 플래그가 존재하지 않으면 `null`을 반환합니다.
+    - `FEATURE_FLAGS_UPDATED`는 새로 고침 요청이 성공 또는 실패로 완료된 경우와 현재 세션에서 이전에 캐시된 데이터가 있는 경우 최초 구독 시에만 트리거됩니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2016.md b/_lang/ko/_help/release_notes/2016.md
new file mode 100644
index 00000000000..729bf01d20c
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2016.md
@@ -0,0 +1,40 @@
+---
+page_order: 8
+nav_title: 2016
+layout: dev_guide
+noindex: true
+guide_top_header: "2016 릴리스 노트"
+
+page_type: landing
+description: "이 섹션에서는 2016년의 릴리스 노트를 확인할 수 있습니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 1월~5월
+    link: /docs/help/release_notes/2016/jantomay/
+    image: /assets/img/braze_icons/calendar-date.svg
+  - name: 6월
+    link: /docs/help/release_notes/2016/june/
+    image: /assets/img/braze_icons/umbrella-03.svg
+  - name: 7월
+    link: /docs/help/release_notes/2016/july/
+    image: /assets/img/braze_icons/flag-01.svg
+  - name: 8월
+    link: /docs/help/release_notes/2016/august/
+    image: /assets/img/braze_icons/wind-02.svg
+  - name: 9월
+    link: /docs/help/release_notes/2016/september/
+    image: /assets/img/braze_icons/backpack.svg
+  - name: 10월
+    link: /docs/help/release_notes/2016/october/
+    image: /assets/img/braze_icons/magic-wand-02.svg
+  - name: 11월
+    link: /docs/help/release_notes/2016/november/
+    image: /assets/img/braze_icons/cloud-sun-02.svg
+  - name: 12월
+    link: /docs/help/release_notes/2016/december/
+    image: /assets/img/braze_icons/gift-01.svg
+
+
+
+---
diff --git a/_lang/ko/_help/release_notes/2016/august.md b/_lang/ko/_help/release_notes/2016/august.md
new file mode 100644
index 00000000000..1e430504f45
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2016/august.md
@@ -0,0 +1,15 @@
+---
+nav_title: 8월
+page_order: 5
+noindex: true
+page_type: update
+description: "이 문서에는 2016년 8월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2016년 8월
+
+## iOS 10 리치 알림
+이제 iOS 10을 사용하는 고객에게 리치 알림을 보낼 수 있습니다. 자세한 내용은 iOS 10 리치 알림을 지원하도록 [앱을 설정하는]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration/#ios-10-rich-notifications) 방법을 참조하세요.
+
+## 전환 이벤트로 앱 업그레이드 추가
+사용자가 앱을 업그레이드하도록 유도하는 것은 많은 고객사의 주요 사용 사례입니다. 새 앱 버전은 더 안정적이거나 수익을 창출할 기회가 더 많을 수 있습니다. 앱 업그레이드를 캠페인 [전환 이벤트]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/conversion_events/#conversion-events)로 추적하면 메시징 활동이 목표를 어떻게 달성하고 있는지 쉽게 추적할 수 있습니다.
diff --git a/_lang/ko/_help/release_notes/2016/december.md b/_lang/ko/_help/release_notes/2016/december.md
new file mode 100644
index 00000000000..61ef5073c6a
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2016/december.md
@@ -0,0 +1,20 @@
+---
+nav_title: 12월
+page_order: 1
+noindex: true
+page_type: update
+description: "이 문서에는 2016년 12월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2016년 12월
+
+## 이메일 헤더
+
+이메일 헤더는 보내기 엔드포인트를 통해 이메일 헤더의 명시적 설정을 추가합니다. Braze로 이메일을 보내는 방법에 대한 자세한 내용은 [이메일 모범 사례][14]를 참조하세요.
+
+## 캔버스 업데이트
+
+이 업데이트를 통해 하나의 스텝을 여러 스텝에 연결하거나 여러 스텝을 하나의 병합된 스텝으로 연결할 수 있을 뿐만 아니라 스텝 사이에 연결 지점을 그릴 수도 있습니다. 예를 들어, 구매를 한 사용자는 그렇지 않은 사용자와 다른 흐름을 따를 수 있습니다. 캔버스에 대한 자세한 내용은 [브랜치 만들기][15]를 참조하세요.
+
+[14]: {{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/
+[15]: {{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/branching/#branching
diff --git a/_lang/ko/_help/release_notes/2016/jantomay.md b/_lang/ko/_help/release_notes/2016/jantomay.md
new file mode 100644
index 00000000000..ef65bf9fc9f
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2016/jantomay.md
@@ -0,0 +1,11 @@
+---
+nav_title: 1월 - 5월
+page_order: 8
+noindex: true
+page_type: update
+description: "이 문서에는 2016년 6월 이전의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2016년 6월 이전의 변경 사항
+
+이 릴리즈 노트는 2016년 6월에 작성되었으며 그 이전의 플랫폼 업데이트는 포함되어 있지 않습니다.
diff --git a/_lang/ko/_help/release_notes/2016/july.md b/_lang/ko/_help/release_notes/2016/july.md
new file mode 100644
index 00000000000..6f8c61d2682
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2016/july.md
@@ -0,0 +1,36 @@
+---
+nav_title: 7월
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서에는 2016년 7월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2016년 7월
+
+## 오류 유형별로 개발자 콘솔의 오류 로그 필터링하기
+
+이번 업그레이드를 통해 개발자 콘솔의 메시지 오류 로그를 사용하여 Braze 연동 관련 문제를 더 쉽게 해결할 수 있습니다. 이 사용성 업데이트를 통해 메시지 오류 로그를 유형별로 필터링하고 특정 연동 문제를 훨씬 쉽게 찾고 식별할 수 있습니다.
+
+## 마지막 제거 추적 푸시 전송에 대한 타임스탬프 추가
+
+Braze는 고객의 앱에 무음 푸시를 보내 응답하는 기기를 확인하여 제거를 감지합니다. 이 기능은 제거 추적이 마지막으로 실행된 시점을 나타내는 눈에 잘 띄지 않는 타임스탬프를 추가합니다. 이 타임스탬프는 제거 추적이 구성된 설정 페이지에서 찾을 수 있습니다. [제거 추적 해제]({{site.baseurl}}/user_guide/data_and_analytics/uninstall_tracking/#uninstall-tracking)에 대해 자세히 알아보세요.
+
+![추적 제거 확인란][6]
+
+## 웹훅 테스트 개선 사항 추가
+
+이제 캠페인을 라이브로 설정하기 전에 Braze에서 라이브 웹훅 메시지를 테스트 전송할 수 있습니다. 테스트 메시지를 보내면 안전한 샌드박스 환경에서 메시지와 서버 엔드포인트가 올바르게 구성되었는지 확인할 수 있습니다. [웹훅]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/#creating-a-webhook)에 대해 자세히 알아보세요.
+
+## 캠페인 수신자에게 수신되는 메시지 변형 CSV 내보내기 추가
+
+캠페인 수신자 CSV 내보내기에 수신된 메시지 변형을 나타내는 열을 추가했습니다. Braze에서 [데이터 내보내기]({{site.baseurl}}/user_guide/data_and_analytics/exporting_dashboard_data/#exporting-dashboard-data)에 대해 자세히 알아보세요.
+
+## 노출 수에 대한 대략적인 제한
+
+인앱 메시지가 일정 횟수 이상 노출 횟수가 다성되면 Braze는 사용자가 메시지를 수신할 수 있는 자격을 더 이상 허용하지 않습니다. [노출 횟수에 대한 대략적인 제한]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#setting-a-max-impression-cap) 설정에 대해 자세히 알아보세요.
+
+![IAM 노출 한도][11]
+
+[6]: {% image_buster /assets/img_archive/uninstall_tracking_checkbox.png %}
+[11]: {% image_buster /assets/img_archive/approx_limit_for_IAM.png %}
diff --git a/_lang/ko/_help/release_notes/2016/june.md b/_lang/ko/_help/release_notes/2016/june.md
new file mode 100644
index 00000000000..ad0ccd7c5b5
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2016/june.md
@@ -0,0 +1,32 @@
+---
+nav_title: 6월
+page_order: 7
+noindex: true
+page_type: update
+description: "이 문서에는 2016년 6월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2016년 6월
+
+## 예외 이벤트 수행을 위한 액션 기반 트리거
+
+예외 이벤트는 액션 기반 캠페인 내에서 강력한 로직을 만드는 데 사용됩니다. 최종 사용자가 메시지를 받지 못하도록 하는 데 사용됩니다. 예를 들어 "장바구니를 유기한 사용자에게 결제하지 않으면 푸시 알림 보내기"를 사용할 수 있습니다. 예외 이벤트를 트리거하여 장바구니를 유기한 후 결제한 사용자에게 추가 메시지와 관심을 유도하여 원활하고 일관된 경험을 제공할 수 있습니다.
+
+## "태그가 있는 캠페인에서 메시지 수신" 세그먼트 필터
+
+이제 고객은 기존에 사용하던 것과 동일한 "태그" 기능으로 캠페인 그룹을 수신한 사용자를 제외할 수 있습니다.
+
+## 여러 캠페인을 동시에 일시 중지하고 다시 시작하기
+
+이제 고객은 캠페인 페이지에서 여러 캠페인을 동시에 일시 중지했다가 다시 시작할 수 있습니다.
+
+## 데이터 API 엔드포인트 제거
+
+이제 고객은 내보내기 API에서 직접 제거 추적 데이터를 가져올 수 있습니다. 자세한 내용은 [내보내기 엔드포인트에서][4] 확인하세요.
+
+## 오류 로그 개선
+
+\[메시지 오류 로그][5]에서 오류 유형별로 정렬하는 기능을 개선했습니다!
+
+[4]: {{site.baseurl}}/developer_guide/rest_api/export/#kpi-export
+[5]: {% image_buster /assets/img_archive/improved_error_log.png %}
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2016/november.md b/_lang/ko/_help/release_notes/2016/november.md
new file mode 100644
index 00000000000..816d1d1987a
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2016/november.md
@@ -0,0 +1,18 @@
+---
+nav_title: 11월
+page_order: 2
+noindex: true
+page_type: update
+description: "이 문서에는 2016년 11월 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2016년 11월
+
+## 연결된 오디언스
+
+연결된 오디언스는 Braze에서 사전 구성 없이 사용자 기반의 하위 집합을 사용하여 메시지를 즉시 타겟팅할 수 있도록 합니다. 예를 들어, 미디어 앱은 고객이 즐겨찾는 모든 카테고리나 TV 프로그램을 추적하기 위해 커스텀 속성 배열을 사용할 수 있습니다. 연결된 오디언스를 사용하면 커스텀 CMS를 Braze와 연결하여 새로운 에피소드가 출시될 때마다 쇼를 즐겨찾기한 사람에게 자동으로 푸시 알림 또는 이메일을 보낼 수 있습니다.
+
+[연결된 오디언스 객체][12]를 참조하거나 [연결된 오디언스][13]에 대한 블로그를 확인하세요.
+
+[12]: {{site.baseurl}}/api/objects_filters/connected_audience/
+[13]: https://www.braze.com/blog/connected-audiences/
diff --git a/_lang/ko/_help/release_notes/2016/october.md b/_lang/ko/_help/release_notes/2016/october.md
new file mode 100644
index 00000000000..44222d4a8bc
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2016/october.md
@@ -0,0 +1,26 @@
+---
+nav_title: 10월
+page_order: 3
+noindex: true
+page_type: update
+description: "이 문서에는 2016년 10월 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2016년 10월
+
+## 새 보안 설정
+Braze에 보안 기능이 강화되었습니다. 비밀번호 만료 규칙, 비밀번호 길이 규칙, 비밀번호 복잡성 규칙, 대시보드 IP 로그인 허용 목록, 2단계 인증이 포함됩니다.
+
+> 업데이트: Braze의 **보안 설정**은 **회사 설정** 페이지에서 액세스할 수 있으며, 비밀번호 재사용 및 만료에 대한 규칙도 포함됩니다.
+
+## 가져온 후 CSV 다운로드
+Braze 사용자는 이제 최근에 가져온 사용자의 CSV를 다운로드할 수 있습니다. 이를 통해 시스템에서 데이터 동기화에 대한 가시성을 높일 수 있습니다. [CSV 가져오기]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/)에 대해 자세히 알아보세요.
+
+## 기념일 필터
+생일 필터 외에도 Braze는 이제 기념일 필터를 지원하여 로열티 마일스톤, 리필 알림 등을 위한 캘린더 날짜를 기준으로 사용자를 타겟팅할 수 있는 기능을 제공합니다! 세그먼트 페이지에서 "커스텀 속성의 날짜" 필터를 선택하여 이 기능에 액세스하세요. [필터]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#segmentation-filters)에 대해 자세히 알아보세요.
+
+## 최대 게재빈도 설정 업데이트
+이전에 캠페인 또는 캔버스가 최대 게재빈도 설정 제한을 무시하더라도 여전히 게재빈도 제한에 포함되었습니다. 기본값으로 새로운 캠페인과 캔버스가 게재빈도 제한을 따르지 않을 경우, 그것들에 대한 카운트도 하지 않도록 동작을 변경했습니다. 이것은 각 캠페인 및 캔버스에 대해 구성할 수 있습니다. [최대 게재빈도 설정]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/#frequency-capping)에 대해 자세히 알아보세요.
+
+## 인앱 메시지 색상 프로필
+앱 내 메시지에 [색상 프로필]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/customize/#color-profile)을 추가하여 고객이 Braze에서 새 메시지를 만들 때 브랜드 색상 스키마를 재사용할 수 있도록 했습니다.
diff --git a/_lang/ko/_help/release_notes/2016/september.md b/_lang/ko/_help/release_notes/2016/september.md
new file mode 100644
index 00000000000..1c7d1df1b86
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2016/september.md
@@ -0,0 +1,15 @@
+---
+nav_title: 9월
+page_order: 4
+noindex: true
+page_type: update
+description: "이 문서에는 2016년 9월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2016년 9월
+
+## 세그먼트 변경 로그
+이제 세그먼트에 대한 변경 내역을 확인할 수 있습니다.
+
+## 가장 최근에 사용한 기기
+모든 플랫폼에서 사용자의 가장 최근 기기에 대해 다음 속성을 템플릿으로 만들 수 있습니다.
diff --git a/_lang/ko/_help/release_notes/2017.md b/_lang/ko/_help/release_notes/2017.md
new file mode 100644
index 00000000000..b5fba01548e
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017.md
@@ -0,0 +1,58 @@
+---
+page_order: 7
+nav_title: 2017
+layout: dev_guide
+noindex: true
+guide_top_header: "2017 릴리스 노트"
+
+page_type: landing
+description: "이 섹션에서는 2017년의 릴리스 노트를 확인할 수 있습니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 1월
+    link: /docs/help/release_notes/2017/january/
+    image: /assets/img/braze_icons/snowflake-01.svg
+  - name: 2월
+    link: /docs/help/release_notes/2017/february/
+    image: /assets/img/braze_icons/hearts.svg
+  - name: 3월
+    link: /docs/help/release_notes/2017/march/
+    image: /assets/img/braze_icons/trophy-01.svg
+  - name: 4월
+    link: /docs/help/release_notes/2017/april/
+    image: /assets/img/braze_icons/droplets-01.svg
+  - name: 5월
+    link: /docs/help/release_notes/2017/may/
+    image: /assets/img/braze_icons/sun.svg
+  - name: 6월
+    link: /docs/help/release_notes/2017/june/
+    image: /assets/img/braze_icons/umbrella-03.svg
+  - name: 7월
+    link: /docs/help/release_notes/2017/july/
+    image: /assets/img/braze_icons/flag-01.svg
+  - name: 8월
+    link: /docs/help/release_notes/2017/august/
+    image: /assets/img/braze_icons/wind-02.svg
+  - name: 9월
+    link: /docs/help/release_notes/2017/september/
+    image: /assets/img/braze_icons/backpack.svg
+  - name: 10월
+    link: /docs/help/release_notes/2017/october/
+    image: /assets/img/braze_icons/magic-wand-02.svg
+  - name: 11월
+    link: /docs/help/release_notes/2017/november/
+    image: /assets/img/braze_icons/cloud-sun-02.svg
+  - name: 12월
+    link: /docs/help/release_notes/2017/december/
+    image: /assets/img/braze_icons/gift-01.svg
+
+
+
+
+
+
+
+
+
+---
diff --git a/_lang/ko/_help/release_notes/2017/april.md b/_lang/ko/_help/release_notes/2017/april.md
new file mode 100644
index 00000000000..0be52105895
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/april.md
@@ -0,0 +1,55 @@
+---
+nav_title: 4월
+page_order: 9
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 4월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 4월
+
+## HTML 브라우저 내 메시지
+
+이제 커스텀 HTML 및 이메일 캡처 형식을 포함한 대화형 인브라우저 메시지 유형을 지원하므로 고객이 어디에 있든 고객에게 다가갈 수 있습니다. [인앱 메시지][48]에 대해 자세히 알아보세요.
+
+## 연결된 콘텐츠가 포함된 맞춤형 인앱 메시지
+
+트리거된 인앱 메시지에 {% raw %} {%connected_content%} {% endraw %} 블록을 추가하여 API를 통해 액세스할 수 있는 모든 정보를 메시지에 직접 삽입하여 풍부한 개인화 기능을 추가할 수 있습니다. 이제 앱 내에서 푸시, 이메일, 웹훅 외에도 연결된 콘텐츠를 사용할 수 있습니다. [연결된 콘텐츠][34]에 대해 자세히 알아보세요.
+
+## 뉴스피드 카드 탐색 기능 개선
+
+뉴스피드 카드 제작 UI를 개선하여 캠페인을 더 쉽게 탐색하고 만들 수 있도록 개선했습니다. [뉴스피드 카드][33]에 대해 자세히 알아보세요.
+
+## iOS 리치 알림의 미리보기 개선
+
+이제 iOS의 미리보기 알림에 리치 알림이 표시되어 고객에게 보내는 내용을 글꼴 크기까지 정확하게 확인할 수 있습니다. [iOS 리치 알림][32]에 대해 자세히 알아보세요.
+
+## 푸시 통계에 "영향받은 열람 수"를 추가했습니다.
+
+Braze에서 제공하는 표준 캠페인 및 캔버스 통계 목록에 "영향력받은 열람 수"를 추가하여 영향력, 직접 및 총 열람 수의 캠페인 내역을 더 쉽게 파악할 수 있도록 했습니다. [영향받은 열람 수][31]에 대해 자세히 알아보세요.
+
+## 내부 그룹으로 업그레이드
+
+이제 여러 개의 내부 그룹을 만들고 해당 그룹을 SDK 로깅, REST API 로깅 또는 메시지 콘텐츠 테스트에 사용할지 여부를 나타내는 속성을 할당할 수 있습니다. [이벤트 사용자 로그][30]에 대해 자세히 알아보세요.
+
+> 업데이트: 내부 그룹을 사용하여 [시드 이메일을 보낼]({{site.baseurl}}/user_guide/administrative/app_settings/developer_console/#seed-groups) 수도 있습니다.
+
+## 웹 URL에 대한 새로운 옵션
+
+이제 푸시 메시지, 인앱 및 브라우저 내 메시지, 뉴스피드 카드에 대해 외부 웹 브라우저에서 웹 URL을 열 수 있는 옵션이 제공됩니다. "앱으로 딥링크" 동작은 이제 HTTP/HTTPS 딥링크와도 호환됩니다. Branch 또는 Apple의 유니버설 링크와 같은 파트너를 사용하는 경우 SDK 사용자 지정이 필요합니다. [딥링킹][29]에 대해 자세히 알아보세요.
+
+## 새로운 '수행된 전환' 이벤트 캔버스
+
+새로운 "전환 수행" 이벤트와 "캔버스 컨트롤 내" 필터를 추가하여 리타겟팅 옵션을 개선했습니다. [리타겟팅 필터][28] 사용에 대해 자세히 알아보세요.
+
+
+
+[28]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/retargeting_campaigns/#retargeting-campaigns
+[29]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/deep_linking_to_in-app_content/#what-is-deep-linking
+[30]: {{site.baseurl}}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab
+[31]: {{site.baseurl}}/user_guide/data_and_analytics/influenced_opens/#influenced-opens
+[32]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration/#ios-10-rich-notifications
+[33]: {{site.baseurl}}/user_guide/engagement_tools/news_feed/creating_a_news_feed_item/#news-feed-cards
+[34]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/
+[48]: {{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/best_practices/
+[98]:{{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
diff --git a/_lang/ko/_help/release_notes/2017/august.md b/_lang/ko/_help/release_notes/2017/august.md
new file mode 100644
index 00000000000..1468ddaf882
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/august.md
@@ -0,0 +1,81 @@
+---
+nav_title: 8월
+page_order: 5
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 8월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 8월
+
+## 푸시 액션 버튼으로 업데이트
+
+REST API 메시징 엔드포인트에 [푸시 실행 버튼][70]에 대한 지원을 추가했습니다.
+
+## Liquid 템플릿으로 업데이트
+
+이제 다음을 기준으로 [메시지를 개인화할][69] 수 있습니다:
+- 전송받은 기기,
+- 기기 ID,
+- 이동통신사,
+- IDFA,
+- 모델,
+- OS 및
+- 플랫폼
+
+## API 트리거 캔버스
+
+이제 캠페인의 기존 엔드포인트와 일치하는 API 엔드포인트(전송, 예약, 업데이트, 삭제)를 통해 [캔버스를][68] 트리거할 수 있으므로 마케팅을 더욱 자동화하고 최적화할 수 있습니다.
+
+## 웹 푸시 액션 버튼
+
+Chrome용 웹 SDK에 푸시 실행 버튼에 대한 지원을 추가하여 사용자에게 상황별 선택권을 제공함으로써 바쁜 일상을 간소화하여 인게이지먼트를 높일 수 있습니다. [푸시 알림에 대한 모범 사례][66]를 확인하세요.
+
+## 새로운 API 엔드포인트
+
+이메일 주소 또는 지정된 날짜 범위에서 하드 바운스를 가져올 수 있는 /email/hard_bounces와 예약된 캠페인 및 예약된 입력 캔버스가 시작될 다음 시간을 가져올 수 있는 messages/scheduled_broadcasts라는 새로운 API 엔드포인트를 노출했습니다. 이러한 새로운 엔드포인트를 통해 캠페인을 더욱 맞춤화하고 최적화할 수 있습니다. [API 엔드포인트][65]에 대해 자세히 알아보세요.
+
+## 지오펜스
+
+고객이 지정된 지리적 영역에 들어오고 나갈 때 실시간으로 메시지를 트리거할 수 있는 새로운 기능인 지오펜스를 추가하여 고객과 관련성 높은 개인화된 커뮤니케이션을 진행할 수 있습니다. [위치 마케팅][64]에 대해 자세히 알아보세요.
+
+## 이메일 편집기로 업데이트
+
+새로운 이메일 편집기에 동적 자동 완성 기능을 추가하여 이제 Liquid를 사용할 때 고객의 실제 사용자 지정 속성 및 이벤트가 자동 완성되어 더욱 편리하게 사용할 수 있습니다. [아카데미][63]에서 이메일 모범 사례에 대해 자세히 알아보세요.
+
+## 최신 필터 업데이트
+
+메시지를 수신하거나 상호 작용한 적이 없는 고객을 타겟팅할 수 있도록 "절대" 날짜 필터를 추가하여 고객 목록을 정리하고 이메일 전달 가능성을 보장할 수 있습니다. [필터][62]에 대해 자세히 알아보세요.
+
+## 캔버스로 업데이트
+
+이제 각 캔버스 변형의 상단에 백분율을 추가하여 어떤 변형의 실적이 더 좋은지 한눈에 확인할 수 있습니다. [캔버스][61]에 대해 자세히 알아보세요.
+
+## 지능형 선택 기능이 있는 캔버스
+
+이제 캔버스에 지능형 선택 기능이 추가되어 캔버스를 더욱 효율적으로 테스트할 수 있습니다. [Intelligence Suite][60]에 대해 자세히 알아보세요.
+
+## 이메일 표시 이름으로 업데이트
+
+이메일 표시 이름에 특수 UTF-8 문자를 지원하므로 고객에게 더욱 개인화된 이메일을 만들 수 있습니다. [이메일 모범 사례][67]에 대해 자세히 알아보세요.
+
+## 참여 보고서 CSV 집계
+
+이제 선택한 캠페인이나 캔버스 수에 관계없이 모든 캠페인과 모든 캔버스에 대한 통합 데이터를 두 개의 개별 파일로 받아볼 수 있으므로 필요한 데이터를 필요한 시점에 모두 확보할 수 있습니다. [참여 보고서][59]에 대해 자세히 알아보세요.
+
+> [2017년 9월 릴리즈 노트]({{site.baseurl}}/help/release_notes/2017/september/)에서 언급했듯이 이제 특정 기간의 데이터를 집계할 수 있을 뿐만 아니라 내보내기를 반복적으로 실행하도록 예약할 수도 있습니다.
+
+
+[59]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/engagement_reports/
+[60]: {{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/
+[61]: {{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/
+[62]: {{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#segmentation-filters
+[63]: {{site.baseurl}}/help/troubleshooting_guide/troubleshooting_guide/#email
+[64]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/advanced_use_cases/locations_and_geofences/
+[65]: {{site.baseurl}}/developer_guide/rest_api/basics/#what-is-a-rest-api
+[66]: {{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/
+[67]: {{site.baseurl}}/help/troubleshooting_guide/troubleshooting_guide/#email
+[68]: {{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/
+[69]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/personalized_messaging/#personalized-messaging
+[70]: {{site.baseurl}}/user_guide/message_building_by_channel/push/push_action_buttons/#how-to-use-action-buttons
+[98]:{{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
diff --git a/_lang/ko/_help/release_notes/2017/december.md b/_lang/ko/_help/release_notes/2017/december.md
new file mode 100644
index 00000000000..d73001b3af4
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/december.md
@@ -0,0 +1,11 @@
+---
+nav_title: 12월
+page_order: 1
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 12월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 12월
+
+이번 달에는 업데이트가 없습니다! 2018년 1월에 다시 확인하세요!
diff --git a/_lang/ko/_help/release_notes/2017/february.md b/_lang/ko/_help/release_notes/2017/february.md
new file mode 100644
index 00000000000..4bb4184ee71
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/february.md
@@ -0,0 +1,36 @@
+---
+nav_title: 2월
+page_order: 11
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 2월 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 2월
+
+## 출시 후 캔버스 단계 추가
+
+이제 캔버스가 시작된 후에도 기존 단계에 [캔버스 단계를 추가][23]할 수 있습니다.
+
+## 대량 CSV 참여 보고서용
+
+이제 [참여 보고서][22]를 사용하여 캠페인 데이터 CSV를 대량으로 내보낼 수 있습니다. 캔버스 데이터는 참여 보고서를 통해서도 내보낼 수 있습니다.
+
+## 마지막으로 받은 인앱 메시지로 필터
+
+더 개인화된 사용자 타겟팅을 위해 이제 "마지막으로 받은 인앱 메시지"를 시간 기반 필터로 사용할 수 있습니다. Braze를 사용한 사용자 타겟팅에 대해 자세히 알아보려면 [세분화][21]를 방문하세요.
+
+## 이벤트 사용자 로그 업그레이드
+
+이제 업그레이드된 [이벤트 사용자 로그][20]를 통해 SDK 통합에서 무슨 일이 일어나고 있는지 쉽게 확인할 수 있습니다.
+
+## 뉴스피드 템플릿
+
+이제 {% raw %} {{card.${name}}} {% endraw %} 및 {% raw %}  {{card.${api_id}}}{% endraw %} 두 개의 뉴스피드 카드 필드가 있습니다. 이 카드들은 Liquid 템플릿에 추가될 수 있습니다. [개인화된 메시징 및 템플릿][19]에 대해 자세히 알아보세요.
+
+[19]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/personalized_messaging/#personalized-messaging
+[20]: {{site.baseurl}}/user_guide/administrative/app_settings/developer_console/event_user_log_tab/#event-user-log-tab
+[21]: {{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/
+[22]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/engagement_reports/#engagement-reports
+[23]: {{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#creating-a-canvas
+[98]:{{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
diff --git a/_lang/ko/_help/release_notes/2017/january.md b/_lang/ko/_help/release_notes/2017/january.md
new file mode 100644
index 00000000000..2ef36823711
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/january.md
@@ -0,0 +1,30 @@
+---
+nav_title: 1월
+page_order: 12
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 1월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2017년 1월
+
+## 이메일 메시지에 대한 새로운 전환 이벤트
+
+이제 "캠페인에서 이메일 열기" 또는 "캠페인에서 이메일 클릭"에 대한 전환 이벤트를 지정할 수 있습니다. [캠페인 전달 유형][16]에 대해 자세히 알아보세요.
+
+## 대조군으로 CSV 내보내기
+이제 사용자 캠페인 CSV를 내보낼 때 데이터에 대조군을 포함할 수 있습니다. [대시보드 데이터 내보내기][17]에 대해 자세히 알아보세요.
+
+## 환영 및 이중 옵트인 이메일
+이제 새로 생성된 '이메일 주소 추가' 액션 기반 트리거를 사용하여 사용자가 처음 이메일 주소를 추가할 때 이중 옵트인 또는 환영 이메일을 쉽게 보낼 수 있습니다. [이메일 모범 사례][18]에 대해 자세히 알아보세요.
+
+## 이메일 목록-수신 거부 헤더
+이제 구독 상태가 "구독/옵트인 사용자" 또는 "옵트인 사용자만"인 목록-수신 취소 헤더를 구성할 수 있습니다. 이렇게 하면 발신자 이름 옆에 Gmail에 "수신 거부" 링크가 추가되어 전달 가능성 등급을 높일 수 있습니다.
+
+## 사용성 업데이트
+이제 버튼을 클릭하여 작은 화면을 위해 캔버스 헤더를 최소화하고 Braze의 사용자 프로필에서 캔버스 및 캠페인의 전체 이름 위로 마우스를 가져갈 수 있습니다.
+
+
+
+[16]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/delivery_types/
+[17]: {{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/
+[18]: {{site.baseurl}}/user_guide/message_building_by_channel/email/faq/
diff --git a/_lang/ko/_help/release_notes/2017/july.md b/_lang/ko/_help/release_notes/2017/july.md
new file mode 100644
index 00000000000..92322ba782c
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/july.md
@@ -0,0 +1,52 @@
+---
+nav_title: 7월
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 7월 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 7월
+
+## 웹 푸시에서 큰 이미지
+
+웹 푸시에서 Windows 및 Android의 Chrome에 대한 대형 이미지 지원을 추가하여 풍부하고 매력적인 고객 경험을 창출할 수 있습니다. [웹 푸시][58]에 대해 자세히 알아보세요.
+
+## 이메일 필드 업데이트
+
+이제 이메일을 특정 발신 주소 세트로 잠글 수 있어 잘못된 주소를 실수로 입력하지 않도록 할 수 있습니다. 이메일 작성 양식은 프로세스를 간소화하기 위해 지난 6개월 동안 사용된 주소로 미리 채워질 것입니다. [이메일][57] 모범 사례를 확인하여 더 많은 정보를 얻으십시오.
+
+## 캠페인 세부 정보 API 업데이트
+
+`/campaign/details` 엔드포인트는 이제 메시지에 대한 정보를 제공하여 API를 사용하여 제목, HTML 본문, 발신 주소 및 회신 주소 필드를 가져올 수 있습니다. [Braze][56] API에 대해 자세히 알아보세요.
+
+## Liquid 템플릿 업데이트
+
+캔버스와 캠페인에서 배리언트 속성을 템플릿화할 수 있는 기능을 추가했습니다. 캔버스에서 이제 배리언트의 API ID뿐만 아니라 배리언트의 이름도 템플릿할 수 있으며, 캠페인에서는 메시지의 `message_api_id` 및 `message_name`을 템플릿할 수 있습니다. 두 업데이트 모두 메시징에서 더 많은 유연성을 제공하여 개인화된 캠페인을 구축할 수 있습니다. [개인화된 메시징][55]에 대해 자세히 알아보세요.
+
+## 새 HTML 이메일 편집기
+
+이제 라이브 프리뷰, Liquid를 통한 개인화 및 줄 번호와 구문 강조가 있는 개선된 전체 화면 텍스트 편집기를 가능하게 하는 전체 화면 HTML 편집기로 이메일을 쉽게 작성하고 테스트할 수 있습니다. [이메일 구성][54]에 대해 자세히 알아보세요.
+
+## 미리보기 업데이트
+
+화면 창을 따라 캠페인 및 캔버스에서 메시지 미리보기를 스크롤하면서 항상 변경 사항이 반영되는 것을 볼 수 있습니다. [미리보기 및 테스트][53]에 대해 자세히 알아보기.
+
+## 새로운 세그먼트 멤버십 필터
+
+Braze는 [세그먼트 멤버십 필터][52]를 추가하여 사용자가 기존 세그먼트의 멤버십을 기반으로 사용자를 타겟팅할 수 있도록 했습니다. 또한 세그먼트 필터에서 "And" 및 "Or" 논리를 모두 사용할 수 있는 기능과 세그먼트를 서로 중첩할 수 있는 기능을 추가했습니다. 이 업데이트를 통해 고객에게 더 정확하게 맞춤형 메시지를 보낼 수 있습니다. 
+
+## Android 프리뷰로 업데이트
+
+Android 프리뷰를 [Android N 이후의 최신 버전을 반영하도록 업데이트했습니다.][51]
+
+
+[51]: {{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/create/#step-5-preview-message
+[52]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features/#targeting-filters
+[53]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/campaigns_in_multiple_languages/#step-6-preview-message
+[54]: {{site.baseurl}}/user_guide/message_building_by_channel/email/creating_an_email_template/#creating-an-email-template
+[55]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/personalized_messaging/#personalized-messaging
+[56]: {{site.baseurl}}/developer_guide/rest_api/basics/#what-is-a-rest-api
+[57]: {{site.baseurl}}/help/troubleshooting_guide/troubleshooting_guide/#email
+[58]: {{site.baseurl}}/user_guide/message_building_by_channel/push/web
+[98]:{{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
diff --git a/_lang/ko/_help/release_notes/2017/june.md b/_lang/ko/_help/release_notes/2017/june.md
new file mode 100644
index 00000000000..c422fc09818
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/june.md
@@ -0,0 +1,42 @@
+---
+nav_title: 6월
+page_order: 7
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 6월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 6월
+
+## 외부 API로 업데이트
+
+외부 API를 업데이트하여 Apple 푸시용 collapse_id 필드를 지원하므로 고객에게 정확하게 메시지를 보낼 수 있습니다. [Braze 메시징 API][49]에 대해 자세히 알아보세요.
+
+## 웹 푸시 알림으로 업데이트
+
+웹 푸시 알림 미리 보기에 드롭다운과 올바른 이미지 높이 렌더링을 포함한 업데이트가 추가되어 웹 푸시 알림을 더 쉽게 테스트하고 보낼 수 있습니다. [웹 푸시에][47] 대해 자세히 알아보세요.
+
+## 보안 설정 개선
+
+고객이 비밀번호 복잡도 규칙, 대시보드 IP 화이트리스트, 2단계 인증을 설정할 수 있는 기능을 추가하여 더 많은 제어 기능을 제공합니다. [보안 설정][46]에 대해 자세히 알아보세요.
+
+## 동시 CSV 가져오기
+
+이제 여러 개의 CSV를 업로드하고 동시에 처리할 수 있으므로 더 빠르게 작업할 수 있습니다. [사용자 가져오기][50]에 대해 자세히 알아보세요.
+
+## 캔버스 템플릿 속성
+
+캔버스 단계에서 보낸 메시지에 [템플릿 속성][45]을 포함할 수 있는 기능이 추가되어 더욱 효율적으로 작업할 수 있습니다.
+
+## 타겟팅 업데이트
+
+이제 날짜와 시간을 필터링할 때 시간 단위를 선택할 수 있어 보다 정확하게 메시지를 타겟팅할 수 있습니다. [필터][44]에 대해 자세히 알아보세요.
+
+
+[44]: {{site.baseurl}}/user_guide/engagement_tools/segments/creating_a_segment/#step-4-add-filters-to-your-segment
+[45]: {{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/
+[46]: {{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#security-settings
+[47]: {{site.baseurl}}/user_guide/message_building_by_channel/push/web
+[49]: {{site.baseurl}}/api/endpoints/messaging/
+[50]: {{site.baseurl}}/user_guide/administrative/manage_your_users/user_import/#user-import
+[98]:{{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
diff --git a/_lang/ko/_help/release_notes/2017/march.md b/_lang/ko/_help/release_notes/2017/march.md
new file mode 100644
index 00000000000..100390ccefd
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/march.md
@@ -0,0 +1,31 @@
+---
+nav_title: 3월
+page_order: 10
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 3월 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 3월
+
+## 새로운 리타겟팅 필터
+
+"캔버스에서 변환됨" 필터를 추가하여 보다 원활한 리타겟팅 옵션을 제공합니다. [리타겟팅 필터][27]에 대해 자세히 알아보세요.
+
+## 웹훅 템플릿
+
+이제 웹훅 메시지를 템플릿으로 저장하여 쉽게 재사용하거나 Twilio와 같은 SMS 플랫폼 또는 Facebook 메신저와 같은 챗봇을 위한 사전 구성된 템플릿으로 시작할 수 있습니다. [웹훅 생성<1>에 대해 자세히 알아보세요.
+
+## 다중 이메일 지원 참여 보고서
+
+[참여 보고서][25]는 이제 여러 이메일 주소로 보낼 수 있습니다.
+
+## 실행 기반 전달에 시간을 지정하기
+
+지연된 동작 기반 트리거를 사용할 때 지연 후 특정 시간에 보낼 수 있는 옵션이 생겼습니다. 이 기능은 캔버스 및 캠페인에 사용할 수 있습니다. [실행 기반 전달 캠페인][24]에 대해 자세히 알아보세요.
+
+
+[24]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/delivery_types/triggered_delivery/
+[25]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/engagement_reports/#engagement-reports
+[26]: {{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/#creating-a-webhook
+[27]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/retargeting_campaigns/#retargeting-campaigns
diff --git a/_lang/ko/_help/release_notes/2017/may.md b/_lang/ko/_help/release_notes/2017/may.md
new file mode 100644
index 00000000000..5d3552bebf4
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/may.md
@@ -0,0 +1,57 @@
+---
+nav_title: 5월
+page_order: 8
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 5월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 5월
+
+## 내부 그룹으로 업데이트
+
+시드 그룹을 위한 내부 그룹에 새로운 기능을 추가하여 이메일을 쉽게 테스트할 수 있도록 했습니다. 이제 사용자를 대량으로 업로드하고, 개인화된 사용자 데이터로 테스트 이메일을 실시간으로 전송하고, 메시지 템플릿을 사용할 수 있습니다. [여기][43]에서 내부 그룹에 대해 자세히 알아보세요.
+
+## 태그 업데이트
+
+이제 세그먼트 태그를 중첩하여 대시보드를 더 잘 구성할 수 있습니다. [세그먼트 태그][42]에 대해 자세히 알아보세요.
+
+## 인앱 메시지 구성 업데이트
+
+이제 인앱 메시지 발송을 특정 기간으로 커스텀 설정할 수 있으므로 고객에게 더욱 개인화된 메시지를 전달할 수 있습니다. [인앱 메시지 작성][41]에 대해 자세히 알아보세요.
+
+## 템플릿 갤러리로 업데이트
+
+마케팅 프로세스를 간소화하기 위해 Braze의 **템플릿 및 미디어** 탭에 모든 [템플릿][40]과 이미지를 통합했습니다. **템플릿 및 미디어** 페이지에는 링크 템플릿도 있습니다.
+
+## 푸시 액션 버튼
+
+이제 푸시 액션 버튼을 사용하여 사용자에게 상황에 맞는 선택권을 제공함으로써 바쁜 일상을 간소화하여 참여도를 높일 수 있습니다. [푸시 알림의][39] 모범 사례에 대해 자세히 알아보세요.
+
+## Liquid 개인화로 업데이트
+
+메시지에 고객 데이터를 쉽게 삽입할 수 있는 팝업을 통해 Liquid 개인화 기능을 간소화했습니다. [Liquid 개인화][38]에 대해 자세히 알아보세요.
+
+## 대시보드 UI 업데이트
+
+이제 캠페인 타겟팅 및 세그먼트 세부 정보 페이지의 대시보드 하단에 표를 통해 나와 관련된 통계만 볼 수 있으므로 캠페인을 수신하는 대상과 그 성과를 더 효과적으로 구축하고 추적할 수 있습니다. [타겟팅 및 인게이지먼트 보고][37]에 대해 자세히 알아보세요.
+
+## IP 온난화에 대한 새로운 할당량 알림
+
+이제 IP 워밍 일정에 따라 할당량에 도달하면 알려주는 알림이 표시되므로 할당량을 초과하지 않도록 할 수 있습니다. [IP 워밍][36]에 대해 자세히 알아보세요.
+
+## 참여 보고서의 캔버스 데이터
+
+이제 캔버스와 캠페인 데이터를 인게이지먼트 보고서에서 함께 내보낼 수 있어 데이터 분석을 간소화할 수 있습니다. [참여 보고서][35]에 대해 자세히 알아보세요.
+
+
+[35]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/engagement_reports/#engagement-reports
+[36]: {{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/
+[37]: {{site.baseurl}}/user_guide/data_and_analytics/configuring_reporting/
+[38]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/personalized_messaging/#adding-personalizable-attributes-objects
+[39]: {{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/
+[40]: {{site.baseurl}}/user_guide/engagement_tools/templates_and_media/
+[41]: {{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/create/#creating-an-in-app-message
+[42]: {{site.baseurl}}/user_guide/administrative/app_settings/tags/#campaign-segment-and-news-feed-card-tags
+[43]: {{site.baseurl}}/user_guide/administrative/app_settings/developer_console/#content-test-groups
+[98]:{{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
diff --git a/_lang/ko/_help/release_notes/2017/november.md b/_lang/ko/_help/release_notes/2017/november.md
new file mode 100644
index 00000000000..e24876c3e9f
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/november.md
@@ -0,0 +1,27 @@
+---
+nav_title: 11월
+page_order: 2
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 11월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 11월
+
+## Braze 알림 환경설정
+
+회사 설정 페이지의 Braze [알림 환경설정 센터][77]에서 팀 사용자가 이메일을 통해 주간 분석 보고서, 캠페인이 전송된 시점 알림, 푸시 자격 증명 오류 등 다양한 알림을 받도록 선택할 수 있습니다. 또한 웹훅을 설정하여 [Slack과 같은][78] 다른 채널에 알림을 표시할 수도 있습니다.
+
+## 미디어 라이브러리 업데이트
+
+이제 **템플릿 및 미디어** 페이지에서 [미디어 라이브러리에][79] 여러 개의 에셋과 에셋 폴더를 업로드하고 태그를 적용하거나 여러 개의 에셋을 삭제하는 등의 대량 작업을 수행할 수 있습니다.
+
+## 캔버스용 브랜치 첫 단계
+
+이제 이형 상품의 첫 번째 단계에서 브랜치를 만들 수 있습니다. 이 기능을 사용하면 배리언트의 첫 단계로 여러 개의 메시지를 보낼 수 있으므로 오디언스를 더욱 세분화할 수 있는 기회가 열립니다.
+
+
+[77]: {{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#notification-preferences
+[78]: {{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#slack-incoming-webhook-integration
+[79]: {{site.baseurl}}/user_guide/engagement_tools/templates_and_media/media_library/#media-library
+[98]:{{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
diff --git a/_lang/ko/_help/release_notes/2017/october.md b/_lang/ko/_help/release_notes/2017/october.md
new file mode 100644
index 00000000000..b759906dc05
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/october.md
@@ -0,0 +1,33 @@
+---
+nav_title: 10월
+page_order: 3
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 10월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 10월
+
+## 푸시 스토리
+
+이제 iOS 및 Android에서 이미지, 클릭 동작, 선택 사항 제목 및 부제목이 포함된 여러 페이지로 구성된 [알림을 만들][74] 수 있습니다. 이 기능을 사용하려면 iOS SDK 3.2.1 및 Android SDK 2.2.0이 필요합니다. 이 새로운 제품에 액세스하려면 고객 성공 매니저나 계정 매니저에게 문의하거나 [지원 티켓][support]을 개설하세요.
+
+## 커런츠
+
+[커런츠][75]는 데이터 웨어하우스, 비즈니스 인텔리전스 도구, 데이터 관리 플랫폼과 같은 기술에 직접 미리 구축된 연결을 통해 고객 데이터에 대한 실시간 대용량 데이터 연결 세트를 표시합니다. Amazon Redshift, Amplitude, 데이터 관리 플랫폼 Segment 및 mParticle에 대한 통합과 함께 출시됩니다. 이 새로운 제품에 액세스하려면 고객 성공 매니저나 계정 매니저에게 문의하거나 [지원 티켓][support]을 개설하세요.
+
+## Okta 싱글 사인온 (2017년 10월)
+
+기업은 Okta를 사용하여 Braze 액세스를 제어하고 동료 Braze 사용자가 Okta 자격 증명을 사용하여 로그인하도록 허용하거나 강제할 수 있습니다. 이 새로운 제품에 액세스하려면 고객 성공 매니저나 계정 매니저에게 문의하거나 [지원 티켓][support]을 개설하세요.
+
+> 업데이트: Okta에 액세스하는 방법에 대한 자세한 내용은 [2018년 5월 릴리즈 노트]({{site.baseurl}}/help/release_notes/2017/august/#may-2018)에서 확인할 수 있습니다.
+
+## 이메일 바닥글 길이 제한 업데이트
+
+이제 [이메일 바닥글][76]의 제한은 100KB입니다. 이 업데이트는 이메일 모범 사례에 따른 것으로, 본문이 400KB를 초과하는 이메일은 스팸으로 분류될 가능성이 높기 때문입니다.
+
+[74]: {{site.baseurl}}/user_guide/message_building_by_channel/push/push_stories/
+[75]: {{site.baseurl}}/partners/braze_currents/how_it_works/
+[76]: {{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#custom-footer
+[98]:{{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
+[support]: {{site.baseurl}}/braze_support/
diff --git a/_lang/ko/_help/release_notes/2017/september.md b/_lang/ko/_help/release_notes/2017/september.md
new file mode 100644
index 00000000000..0c9934680c1
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2017/september.md
@@ -0,0 +1,39 @@
+---
+nav_title: 9월
+page_order: 4
+noindex: true
+page_type: update
+description: "이 문서에는 2017년 9월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2017년 9월
+
+## 참여 보고서의 새로운 기능
+
+이제 [참여 보고서를][72] 사용하여 특정 기간 동안 캠페인에 대한 지표를 집계할 수 있습니다. 예를 들어, 분기별 총 오픈 횟수 또는 캠페인 또는 캔버스의 전체 기간 동안의 총 클릭 횟수를 내보낼 수 있습니다. 여러분이 해야 할 일은 간단합니다:
+- 데이터를 내보낼 기간을 선택합니다,
+- 한 명 이상의 수신자에게 정기적으로 전송하는 인게이지먼트 보고서를 예약합니다.
+- 태그를 기반으로 캠페인과 캔버스를 보고서에 추가합니다.
+
+## 사용자 프로필 페이지 업데이트
+
+[사용자 프로필 페이지가][73] 업데이트되었습니다.
+
+## 해제하려면 사용자 조치가 필요한 웹 푸시 알림
+
+이제 Chrome 웹 푸시에 대해 메시지 닫기 동작을 설정하여 수신자가 메시지와 상호 작용해야만 메시지가 해제되도록 할 수 있습니다. 이 기능을 사용하려면 웹 SDK 버전 1.6.13 이상이 필요합니다.
+
+## 이메일 프리헤더
+
+이제 Braze 내에서 이메일 메시지를 작성할 때, **정보 보내기** 섹션에 프리헤더를 쉽게 삽입할 수 있습니다.
+
+## 원시 이벤트 내보내기를 위한 새로운 API 엔드포인트
+
+원시 이벤트 내보내기에 특정 날짜가 로드되었는지 쿼리할 수 있는 새로운 [API 엔드포인트인][71]/raw_data/status를 추가했습니다. 특정 날짜의 원시 데이터를 사용할 수 있는지 확인하여 디버깅 및 자동화를 지원하는 데 사용할 수 있습니다.
+
+
+
+[71]: {{site.baseurl}}/developer_guide/rest_api/api_network_connectivity_issues/#whitelisting-brazes-api-endpoint-ip-ranges
+[72]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/engagement_reports/#engagement-reports
+[73]: {{site.baseurl}}/user_guide/engagement_tools/segments/using_user_search/#using-user-search
+[98]:{{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
diff --git a/_lang/ko/_help/release_notes/2018.md b/_lang/ko/_help/release_notes/2018.md
new file mode 100644
index 00000000000..ef4c6c90c4b
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018.md
@@ -0,0 +1,51 @@
+---
+page_order: 6
+nav_title: 2018
+layout: dev_guide
+noindex: true
+guide_top_header: "2018 릴리스 노트"
+
+page_type: landing
+description: "이 섹션에서는 2018년의 릴리스 노트를 확인할 수 있습니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 1월
+    link: /docs/help/release_notes/2018/january/
+    image: /assets/img/braze_icons/snowflake-01.svg
+  - name: 2월
+    link: /docs/help/release_notes/2018/february/
+    image: /assets/img/braze_icons/hearts.svg
+  - name: 3월
+    link: /docs/help/release_notes/2018/march/
+    image: /assets/img/braze_icons/trophy-01.svg
+  - name: 4월
+    link: /docs/help/release_notes/2018/april/
+    image: /assets/img/braze_icons/droplets-01.svg
+  - name: 5월
+    link: /docs/help/release_notes/2018/may/
+    image: /assets/img/braze_icons/sun.svg
+  - name: 6월
+    link: /docs/help/release_notes/2018/june/
+    image: /assets/img/braze_icons/umbrella-03.svg
+  - name: 7월
+    link: /docs/help/release_notes/2018/july/
+    image: /assets/img/braze_icons/flag-01.svg
+  - name: 8월
+    link: /docs/help/release_notes/2018/august/
+    image: /assets/img/braze_icons/wind-02.svg
+  - name: 9월
+    link: /docs/help/release_notes/2018/september/
+    image: /assets/img/braze_icons/backpack.svg
+  - name: 10월
+    link: /docs/help/release_notes/2018/october/
+    image: /assets/img/braze_icons/magic-wand-02.svg
+  - name: 11월
+    link: /docs/help/release_notes/2018/november/
+    image: /assets/img/braze_icons/cloud-sun-02.svg
+  - name: 12월
+    link: /docs/help/release_notes/2018/december/
+    image: /assets/img/braze_icons/gift-01.svg
+
+
+---
diff --git a/_lang/ko/_help/release_notes/2018/april.md b/_lang/ko/_help/release_notes/2018/april.md
new file mode 100644
index 00000000000..3b8c9d54afe
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/april.md
@@ -0,0 +1,41 @@
+---
+nav_title: 4월
+page_order: 9
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 4월 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 4월
+
+## 웹훅 업데이트가 진행 중입니다
+
+5월에 Braze는 웹훅 리디렉션에 대한 보안 이니셔티브를 구현할 예정입니다. 앞으로 웹훅 발신자는 이러한 리디렉션을 따를 수 없습니다. 대신, 리디렉션은 무한 리디렉션 루프를 방지하기 위해 오류로 처리됩니다. Braze는 이것이 누구에게도 영향을 미치지 않을 것으로 예상하지만, 리디렉션하는 웹훅이 있는 경우 해당 캠페인을 다시 방문하고 편집할 것을 권장합니다.
+
+## CSV 저장소 증가
+
+Braze는 사용자가 업데이트된 최근 10개의 CSV 대신 100개의 최신 CSV를 포함하도록 CSV X 필터를 업데이트했습니다.
+
+## Android 앱의 기본값으로 제거 추적 켜기
+
+모든 새로운 Android 앱의 [제거 추적][94] 기능은 기본값으로 "켜짐"으로 설정됩니다. 모든 기존 Android 앱에서 제거 추적이 꺼져 있는 경우 이제 "켜짐"으로 변경됩니다. Android 제거 추적은 더 이상 기기에 푸시를 전송하지 않으며, 사용자 측에서 다른 업데이트나 조치가 필요하지 않습니다.
+
+## 업데이트되고 개선된 검색 기능
+
+Braze는 대규모 Braze 배포를 관리하는 경험을 개선하기 위해 Braze에 태그 지정 및 더 나은 검색 기능을 추가했습니다. [커스텀 이벤트 및 속성][92], 템플릿 등을 검색할 때 도움이 됩니다.
+
+## 푸시 스토리
+
+[알림 생성][95] 여러 페이지, 이미지, 클릭 동작, 선택적 제목 및 부제목을 포함합니다. 간단히 푸시 메시지를 만들고 드롭다운에서 **푸시 스토리**를 선택하세요.
+
+Android(버전 2.2.0+) 및 iO (버전 3.2.0+)의 최신 버전으로 업데이트해야 이 기능을 사용할 수 있습니다.
+
+
+## 받은편지함 비전
+
+이제 고객의 플랫폼을 기반으로 이메일을 [미리보기][96]할 수 있으며, 썸네일의 개요 페이지나 각 클라이언트의 HTML 렌더링에 존재할 수 있는 문제에 대한 보다 구체적인 분석과 큰 스크린샷을 포함한 목록 보기를 통해 확인할 수 있습니다. 자세한 내용은 고객 성공 매니저 또는 계정 매니저에게 문의하십시오.
+
+
+[92]: {{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#custom-event-and-attribute-management
+[94]: {{site.baseurl}}/user_guide/data_and_analytics/uninstall_tracking/#uninstall-tracking-for-campaigns
+[95]: {{site.baseurl}}/user_guide/message_building_by_channel/push/push_stories/#push-stories
+[96]: {{site.baseurl}}/user_guide/message_building_by_channel/email/inbox_vision/#inbox-vision
diff --git a/_lang/ko/_help/release_notes/2018/august.md b/_lang/ko/_help/release_notes/2018/august.md
new file mode 100644
index 00000000000..aafc42e921e
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/august.md
@@ -0,0 +1,26 @@
+---
+nav_title: 8월
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 8월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 8월
+
+## iOS 12 알림 그룹
+
+최근 iOS 12 릴리스에서는 애플리케이션에 대한 알림 그룹화(Android 알림 채널과 유사)를 지원합니다. [Braze에서는 메시지 작성기를 사용하여 iOS에서 이 그룹화 기능을 활용할 수 있습니다.]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/#notification-groups)
+
+## 푸시 스토리 트리거링
+
+이제 푸시 스토리 슬라이드의 특정 페이지 클릭을 기반으로 사용자를 리타겟팅할 수 있습니다. **캠페인과 상호 작용한 캠페인**에 대한 추가 필터를 사용합니다.
+
+## 익명 사용자의 S3 및 Azure 데이터 이벤트
+
+이제 Amazon S3 및 Microsoft Azure로 데이터를 내보내는 고객은 익명 사용자의 이벤트를 포함할 수 있습니다. 이 기능은 새로 생성된 모든 통합에 대해 기본적으로 켜짐으로 설정되지만 기존 통합에 대해서는 꺼진 상태로 유지됩니다. 궁금한 점이 있으면 계정 매니저에게 문의하거나 [지원 티켓][support]을 개설하세요.
+
+## 믹스패널 코호트 통합
+
+이제 Braze와 Mixpanel을 모두 사용하는 고객은 [Mixpanel 코호트를 통합하여 세그먼트 필터로 Braze에 보낼]({{site.baseurl}}/partners/insights/behavioral_analytics/mixpanel_for_currents/#mixpanel-cohort-import) 수 있습니다. 한 번 수동 내보내기를 설정하거나 2시간마다 동적 내보내기를 설정할 수 있습니다. 업데이트된 각 사용자는 데이터 포인트로 계산되지만 Mixpanel은 마지막 동기화 이후의 변경 사항만 전송합니다.
+
+[support]: {{site.baseurl}}/braze_support/
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2018/december.md b/_lang/ko/_help/release_notes/2018/december.md
new file mode 100644
index 00000000000..6321fd34262
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/december.md
@@ -0,0 +1,22 @@
+---
+nav_title: 12월
+page_order: 2
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 12월 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 12월
+
+## 콘텐츠 블록
+
+[콘텐츠 블록]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/)을 사용하면 재사용 가능한 크로스채널 콘텐츠를 단일 중앙 위치에서 관리할 수 있습니다. 이 기능에 액세스하려면 Braze 계정의 **템플릿 및 미디어** 섹션에서 **콘텐츠 블록 라이브러리** 탭으로 이동하십시오. 
+
+콘텐츠 블록을 사용하면 다음을 수행할 수 있습니다.
+ - 콘텐츠 블록을 헤더 및 푸터로 사용하여 이메일 캠페인에 일관된 모양과 느낌을 만드세요.
+ - 다양한 채널을 통해 동일한 제안 코드를 배포하세요.
+ - 미리 정의된 자산을 생성하여 일관된 정보와 자산으로 메시지를 빌드할 수 있습니다.
+ - 전체 메시지 본문을 다른 메시지로 복사합니다.
+
+## Gmail 홍보 도구
+
+Gmail은 모바일 프로모션 탭을 업데이트하여 마케터가 제목란이나 프리헤더 정보만이 아니라 "카드"의 주석을 통해 더 많은 정보를 보낼 수 있도록 했습니다. [Gmail 프로모션 도구]({{site.baseurl}}/user_guide/message_building_by_channel/email/gmail_promotions_tab/)를 사용하여 Braze는 사용자가 Braze의 제품에서 카드를 구축할 수 있도록 도와줍니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2018/february.md b/_lang/ko/_help/release_notes/2018/february.md
new file mode 100644
index 00000000000..b08ee77b626
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/february.md
@@ -0,0 +1,34 @@
+---
+nav_title: 2월
+page_order: 11
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 2월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 2월
+
+## iOS 푸시 배지 수
+
+이제 Braze에서 푸시 작성기 내에서 [배지 수를 업데이트할][89] 수 있습니다.
+각 푸시 메시지에 대해 해당 알림이 트리거하는 배지 수를 지정할 수 있습니다.
+
+## 이메일 주소를 사용하여 API를 통해 사용자 내보내기
+
+이제 이메일 주소를 지정하여 [API를 통해 사용자 프로필 데이터를 내보낼][88] 수 있습니다.
+이 내보내기에는 해당 이메일 주소와 연결된 모든 프로필이 포함됩니다.
+
+## 이메일 템플릿 API
+
+이제 [API를 통해 이메일 템플릿][87]을 만들고 업데이트할 수 있습니다. 각 템플릿에는 다른 API 호출에서 참조할 수 있는 **email_template_id**가 있습니다.
+
+## REST API 키 권한
+
+이제 [여러 개의 REST API 키][86]를 만들고 각각에 대한 액세스 권한을 구성할 수 있습니다. 각 키는 특정 엔드포인트에 대한 액세스 권한을 부여하도록 구성할 수 있습니다.
+
+또한 주어진 REST API 키에 대해 REST API 요청을 할 수 있는 [IP 주소][85] 및 서브넷의 화이트리스트를 지정할 수도 있습니다.
+
+[85]: {{site.baseurl}}/developer_guide/rest_api/basics/#api-ip-whitelisting
+[86]: {{site.baseurl}}/developer_guide/rest_api/basics/#app-group-rest-api-keys
+[87]: {{site.baseurl}}/developer_guide/rest_api/email_templates/#email-templates
+[88]: {{site.baseurl}}/developer_guide/rest_api/export/#user-export
+[89]: {{site.baseurl}}/help/best_practices/utilizing_badge_count/#utilizing-badge-count
diff --git a/_lang/ko/_help/release_notes/2018/january.md b/_lang/ko/_help/release_notes/2018/january.md
new file mode 100644
index 00000000000..6cbec64fd1e
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/january.md
@@ -0,0 +1,43 @@
+---
+nav_title: 1월
+page_order: 12
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 1월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 1월
+
+## CSS 인라이닝
+
+이제 **이메일 설정**으로 이동하여 개별 이메일 메시지에 대해 [CSS 인라인][84]을 켜거나 끌 수 있습니다.
+
+## 새로운 세그먼트 필터
+
+이제 다음 필터를 사용하여 세그먼트를 만들 수 있습니다:
+- 캔버스 단계 수신
+- 연/클릭한 캔버스 단계
+- 마지막으로 수신된 특정 캔버스 단계
+
+{% alert update %}
+2019년 3월부터 `Received Canvas Step`은 `Received Message from Canvas Step`으로, `Last Received Specific Canvas Step`은 `Last Received Message from Specific Canvas Step`으로 이름이 변경되었습니다.
+{% endalert %}
+
+## 디바이스 ID를 사용하여 사용자 내보내기
+
+이 엔드포인트는 이제 [익명 사용자 프로필을 내보낼][82] 수 있는 기기 식별자를 매개변수로 허용합니다.
+
+기기 ID를 사용하여 해당 기기의 모든 고객 프로필을 내보낼 수 있습니다.
+
+## 참여 보고서 업데이트
+
+이제 **푸시 오픈율** 및 **전환율과** 같은 추가 통계를 [참여 보고서에서][81] 확인할 수 있습니다.
+
+## Apple 푸시 인증서: .p8 파일 사용
+
+이제 Apple 푸시 인증서를 업로드할 때 [p8 파일][80]을 사용하여 iOS 푸시 자격 증명이 만료되지 않도록 할 수 있습니다.
+
+
+[80]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration/#recommended-option-using-a-p8-file-authentication-tokens
+[81]: {{site.baseurl}}/user_guide/data_and_analytics/reporting/engagement_reports/#engagement-reports
+[82]: {{site.baseurl}}/developer_guide/rest_api/export/#users-by-identifier-endpoint
+[84]: {{site.baseurl}}/user_guide/message_building_by_channel/email/css_inline/#css-inlining
diff --git a/_lang/ko/_help/release_notes/2018/july.md b/_lang/ko/_help/release_notes/2018/july.md
new file mode 100644
index 00000000000..83cbbc293ec
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/july.md
@@ -0,0 +1,24 @@
+---
+nav_title: 7월
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서는 2018년 7월 릴리스 노트를 포함하고 있습니다."
+---
+# 2018년 7월
+
+## 속성 변경에서 트리거
+
+이제 속성 값 변경(예: 구독 상태 및 커스텀 속성 변경)을 기반으로 캠페인 및 캔버스 단계를 트리거할 수 있습니다. 이전에 캠페인을 실시간으로 트리거하려면 Braze에 이벤트 또는 API 트리거를 보내야 했습니다. 그러나 속성 트리거를 사용하면 이벤트를 추가하지 않고도 Braze에서 직접 트리거된 워크플로를 설정할 수 있습니다!
+
+이 기능은 아직 모든 고객에게 제공되지 않습니다. Braze 계정에 이 기능을 활성화하는 데 관심이 있다면 계정 매니저에게 문의하세요.
+
+## 캔버스 시간 옵션 추가: 현지 시간
+
+이제 회사의 현지 시간 또는 사용자의 현지 시간에 메시지를 보낼 수 있습니다. 캔버스 단계를 만들 때 "예약됨"을 선택한 다음 "다음에" 또는 "안에"를 선택하세요. 그러면 "회사 시간"과 "사용자 현지 시간" 중에서 선택할 수 있습니다.
+
+## 캠페인 알림
+
+Braze 캠페인은 이제 캠페인 내 전송 횟수에 대한 매개변수를 설정할 수 있게 하여, 전송 횟수가 선택한 숫자보다 낮아지거나 높아질 경우 캠페인에 대한 알림을 받을 수 있습니다. 캠페인을 모니터링하려면 클릭한 다음 첫 번째 블록 **캠페인 모니터링**을 식별하십시오. **경고 설정**을 클릭한 다음 경고를 설정하고 저장하세요! 
+
+[캠페인 알림]({{site.baseurl}}/user_guide/engagement_tools/campaigns/scheduling_and_organizing/campaign_alerts/#campaign-alerts)에 대해 자세히 알아보세요.
diff --git a/_lang/ko/_help/release_notes/2018/june.md b/_lang/ko/_help/release_notes/2018/june.md
new file mode 100644
index 00000000000..f8a5afe945a
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/june.md
@@ -0,0 +1,21 @@
+---
+nav_title: 6월
+page_order: 7
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 6월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 6월
+
+## 비밀번호 재사용 여부
+
+이제 관리자는 회사 내 다른 Braze 사용자가 이전 비밀번호를 재사용하기 전에 사용해야 하는 새 고유 비밀번호의 최소 개수를 결정할 수 있습니다. 이는 **보안 설정** 탭의 **회사 설정**에 있는 \[인증 규칙][98] 패널에서 제어할 수 있습니다.
+
+## 캔버스 단계에 대한 추적 제거
+
+이제 캔버스 단계별 제거를 추적하고 통계로 볼 수 있습니다.
+
+![캔버스 제거 추적][1]
+
+[1]: {% image_buster /assets/img/uninstall_tracking_canvas_step.png %}
+[98]: {{site.baseurl}}/user_guide/onboarding/platform_administrative_features/#authentication-rules
diff --git a/_lang/ko/_help/release_notes/2018/march.md b/_lang/ko/_help/release_notes/2018/march.md
new file mode 100644
index 00000000000..b376e151f87
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/march.md
@@ -0,0 +1,19 @@
+---
+nav_title: 3월
+page_order: 10
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 3월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 3월
+
+## 링크 템플릿
+
+이제 이메일 메시지의 모든 링크에 [매개변수를 추가하거나][91] URI를 미리 추가하는 템플릿을 만들 수 있습니다. 모든 링크에 Google 애널리틱스 쿼리 매개변수를 추가하고 싶으신가요? 시작하세요!
+
+## 개발 빌드를 위한 범용 APN 인증서
+
+이제 개발 환경에 사용하도록 [APN 인증서를 구성할][90] 수 있습니다.
+
+[90]: {{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/troubleshooting//#step-1-configuring-the-push-certificate-and-provisioning-profile
+[91]: {{site.baseurl}}/user_guide/message_building_by_channel/email/link_templates/#link-templates
diff --git a/_lang/ko/_help/release_notes/2018/may.md b/_lang/ko/_help/release_notes/2018/may.md
new file mode 100644
index 00000000000..b53f8ef9c1e
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/may.md
@@ -0,0 +1,32 @@
+---
+nav_title: 5월
+page_order: 8
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 5월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 5월
+
+## Okta 싱글 사인온 업데이트(SSO)
+
+회사에서 Okta를 사용하는 경우, Okta 관리자는 Okta 애플리케이션 네트워크에서 Braze 앱을 설치할 수 있습니다. 그런 다음 Braze 앱의 회사 설정 페이지에서 보안 설정 탭의 적절한 위치에 Okta 인증서를 입력해야 합니다.
+
+활성화가 완료되면 Okta 로그인 버튼을 사용하여 Braze 앱에 로그인할 수 있습니다.
+
+## 모바일 반응형 이메일 템플릿
+
+Braze에는 일반적인 이메일 마케팅 요구 사항에 맞는 16개의 새로운 모바일 반응형 [이메일 템플릿이][97] 있습니다. 여기에는 다음 템플릿 테마의 다양한 버전이 포함됩니다:
+
+- 환영합니다.
+- 감사합니다
+- 뉴스레터
+- 주문 확인
+- 배송 확인
+- 제품
+- 이벤트
+- 정보
+
+각 템플릿을 나타내는 아이콘에 해당 템플릿의 레이아웃이 표시되는 것을 확인할 수 있습니다.
+
+
+[97]: {{site.baseurl}}/user_guide/message_building_by_channel/email/creating_an_email_template/#step-2-create-or-choose-a-template
diff --git a/_lang/ko/_help/release_notes/2018/november.md b/_lang/ko/_help/release_notes/2018/november.md
new file mode 100644
index 00000000000..46baa58111a
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/november.md
@@ -0,0 +1,18 @@
+---
+nav_title: 11월
+page_order: 3
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 11월의 릴리스 노트가 포함되어 있습니다."
+---
+## 2018년 11월
+
+### 캔버스 항목 설정 마법사
+
+작업 누락과 그로 인한 오류를 방지하기 위해 캔버스 UI가 간소화됩니다. 특히 캔버스 구성은 이제 **캠페인** 마법사의 디자인과 유사하게 마법사에 표시됩니다. 자세한 내용은 [캔버스 만들기]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/) 단계를 확인하세요!
+
+이 새로운 기능에 대해 더 자세히 알고 싶으신가요? [엔트리 마법사](https://learning.braze.com/the-new-canvas-entry-step/264889/scorm/20z5ij5ublxbk)에서 Braze학습 과정을 확인하세요!
+
+### 인앱 메시지 웹 모달 CSS
+
+[웹 모달 CSS 편집기]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/create/#web-modal-css)가 업데이트되어 새로운 [CSS 템플릿]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/in_app_message_color_templates/#css-template)을 사용하여 인앱 메시지의 모양을 더 잘 제어할 수 있게 되었습니다.
diff --git a/_lang/ko/_help/release_notes/2018/october.md b/_lang/ko/_help/release_notes/2018/october.md
new file mode 100644
index 00000000000..ffe5c9989a2
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/october.md
@@ -0,0 +1,50 @@
+---
+nav_title: 10월
+page_order: 4
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 10월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 10월
+
+{% comment %}
+  나중에 추가할 수 있습니다...
+  지능형 선택 대조군 토글
+  이제 지능형 선택 상자에 [대조군 사용을 켜거나 끌]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/multivariate_testing/#including-a-control-group) 수 있는 확인란이 생겼습니다. 이 기능을 켜면 대조군은 대상 규모의 20%가 되며 지능형 선택 기능이 배리언트 오디언스 규모별로 최적화함에 따라 변경됩니다.
+  캔버스 항목 설정 마법사(베타)
+  작업 누락과 그로 인한 오류를 방지하기 위해 캔버스 UI가 간소화됩니다. 특히 캔버스 구성은 이제 캠페인 마법사의 디자인과 유사하게 마법사에 표시됩니다. 이 기능은 점진적으로 배포 중이므로 현재 설명서에는 반영되어 있지 않습니다. 자세한 내용은 곧 다시 확인해 주세요!
+  구독 그룹 API (숨김)
+  Braze는 외부 ID 또는 이메일 주소를 기반으로 요청할 수 있는 새로운 GET 호출 기능을 추가했습니다. 그러면 해당 사용자와 연결된 모든 구독 그룹이 제공됩니다.
+{% endcomment %}
+
+## 캠페인의 정확한 잠재고객 통계 계산하기
+
+이제 **캠페인 분석으로** 이동하여 오디언스에 대한 정확한 통계를 계산할 수 있습니다. **타겟 사용자** 섹션의 바닥글에서 정확한 **통계 계산**을 클릭하면 정확한 오디언스 통계가 채워집니다. 계산하기 전에 캠페인을 저장해야 합니다(초안 캠페인은 초안으로 저장됩니다).
+
+## Windows 8 지원 중단
+
+Braze는 2018년 10월 10일부터 Windows 8을 더 이상 지원하지 않습니다.
+
+## 파트너십 허브
+
+이제 Braze 플랫폼의 통합에서 **통합** 키 및 지침과 함께 통합 목록을 찾을 수 있습니다.
+
+## 이메일 분석 계산
+
+Braze는 이제 이메일 분석의 정확도를 크게 향상시키기 위해 이메일 전송 파트너(ESP)의 이벤트 데이터를 사용하여 모든 이메일 분석을 계산하고 있습니다. 이 솔루션은 오픈 소스 데이터베이스 솔루션인 Postgres를 활용하여 데이터 무결성을 보장합니다.
+
+{% alert important %}
+고유 열람 수와 고유 클릭 수는 현재 이메일 전송 파트너가 제공하는 집계 데이터에 따라 달라집니다. 이번 릴리스에 도입된 것과 동일한 인프라를 사용하여 이러한 고유성 통계를 계산하는 작업이 진행 중입니다.
+{% endalert %}
+
+## 작곡가 패널 컨트롤
+
+메시지 작성기 컨트롤이 아이콘과 연관된 문구를 포함하도록 개편되어 사용성과 탐색 기능이 향상되었습니다.
+
+## 커런츠용 Azure
+
+이제 커런츠를 사용하는 Braze 고객은 [Azure]({{site.baseurl}}/partners/braze_currents/data_storage_integrations/partners/microsoft_azure_blob_storage/)를 잠재적인 통합 대상으로 볼 수 있습니다.
+
+## 입력 필드 확장
+
+이제 이메일 제목과 푸시 제목의 입력 상자를 확장할 수 있습니다.
diff --git a/_lang/ko/_help/release_notes/2018/september.md b/_lang/ko/_help/release_notes/2018/september.md
new file mode 100644
index 00000000000..aa111021af9
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2018/september.md
@@ -0,0 +1,42 @@
+---
+nav_title: 9월
+page_order: 5
+noindex: true
+page_type: update
+description: "이 문서에는 2018년 9월 릴리스 노트가 포함되어 있습니다."
+---
+# 2018년 9월
+
+## iOS 12 알림 그룹: 추가 능력
+
+이제 Braze를 사용하여 [Apple의 알림 그룹 기능]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/#notification-groups)에 액세스할 수 있습니다! 요약 인수 및 그룹을 추가하고, 중요 경고를 활용하고, 필터를 사용하여 임시 인증된 사용자를 표시하고, 고객 프로필에서 임시 인증된 상태를 볼 수 있습니다.
+
+## 조용한 시간
+
+고객은 이제 캔버스에 대해 [방해금지 시간]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#step-5-select-your-send-settings) (메시지가 전송되지 않는 시간)을 지정할 수 있습니다. 그냥 **캔버스 전송 설정**으로 가서 "방해금지 시간 활성화"를 확인하세요. 그런 다음 사용자의 로컬 시간에 맞춰 방해금지 시간을 선택하고 메시지가 해당 방해금지 시간 내에 트리거될 경우 어떤 조치가 따를지 선택합니다.
+
+캠페인은 이제 "하루 중 특정 시간에 이 메시지를 보내기" 대신 조용한 시간을 사용합니다.
+
+## 고객 조정
+
+Braze 고객은 이제 [Adjust]({{site.baseurl}}/partners/advertising_technologies/attribution/adjust/)를 사용하여 Braze API 키와 Braze 인스턴스 URL을 확인할 수 있으며, 이를 Adjust 플랫폼에서 통합하는 데 사용할 수 있습니다.
+
+## 세그먼트 필터에 없음
+
+고객은 이제 [특정 세그먼트에 포함되지 않은]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#retargeting) 사용자를 세그먼트로 만들 수 있습니다.
+
+## 캔버스 수신자 CSV 내보내기
+
+고객은 이제 캔버스에 들어간 사용자에 대한 [데이터]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_canvas_data/)를 내보낼 수 있습니다. 생성된 CSV는 캠페인 CSV와 유사할 것입니다.
+
+## 임시로 승인된 iOS 12 세그먼트 필터
+
+iOS 12에서 특정 앱에 대해 임시로 승인된 사용자를 찾을 수 있는 [세그먼트 필터]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/#other)가 추가되었습니다.
+
+## 인앱 메시지 이미지 업로더
+
+인앱 메시지용 이미지 업로더가 디자인 패널에서 작성 패널로 이동했습니다.
+
+## 읽기 전용 권한 고객 프로필 페이지에서
+
+이 릴리스 이전에는 고객이 [읽기 전용 권한]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#available-limited-and-team-role-permissions)으로 고객 프로필에서 구독 상태 및 이메일 주소를 변경할 수 있었습니다. Braze는 `import_user` 권한의 이름을 `import_and_update_user` 권한으로 변경하고 구독 상태 및 이메일 주소에 대한 편집 액세스를 제한했습니다. 이제 개발자가 읽기 전용으로 가장하거나 이 권한이 없는 경우 구독 상태나 이메일 주소를 변경할 수 없습니다.
diff --git a/_lang/ko/_help/release_notes/2019.md b/_lang/ko/_help/release_notes/2019.md
new file mode 100644
index 00000000000..bbb5a5b3532
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019.md
@@ -0,0 +1,50 @@
+---
+page_order: 5
+nav_title: 2019
+layout: dev_guide
+noindex: true
+guide_top_header: "2019 릴리스 노트"
+
+page_type: landing
+description: "이 섹션에서는 2019년의 릴리스 노트를 확인할 수 있습니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 1월
+    link: /docs/help/release_notes/2019/january/
+    image: /assets/img/braze_icons/snowflake-01.svg
+  - name: 2월
+    link: /docs/help/release_notes/2019/february/
+    image: /assets/img/braze_icons/hearts.svg
+  - name: 3월
+    link: /docs/help/release_notes/2019/march/
+    image: /assets/img/braze_icons/trophy-01.svg
+  - name: 4월
+    link: /docs/help/release_notes/2019/april/
+    image: /assets/img/braze_icons/droplets-01.svg
+  - name: 5월
+    link: /docs/help/release_notes/2019/may/
+    image: /assets/img/braze_icons/sun.svg
+  - name: 6월
+    link: /docs/help/release_notes/2019/june/
+    image: /assets/img/braze_icons/umbrella-03.svg
+  - name: 7월
+    link: /docs/help/release_notes/2019/july/
+    image: /assets/img/braze_icons/flag-01.svg
+  - name: 8월
+    link: /docs/help/release_notes/2019/august/
+    image: /assets/img/braze_icons/wind-02.svg
+  - name: 9월
+    link: /docs/help/release_notes/2019/september/
+    image: /assets/img/braze_icons/backpack.svg
+  - name: 10월
+    link: /docs/help/release_notes/2019/october/
+    image: /assets/img/braze_icons/magic-wand-02.svg
+  - name: 11월
+    link: /docs/help/release_notes/2019/november/
+    image: /assets/img/braze_icons/cloud-sun-02.svg
+  - name: 12월
+    link: /docs/help/release_notes/2019/december/
+    image: /assets/img/braze_icons/gift-01.svg
+
+---
diff --git a/_lang/ko/_help/release_notes/2019/april.md b/_lang/ko/_help/release_notes/2019/april.md
new file mode 100644
index 00000000000..8ffe0aedc19
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/april.md
@@ -0,0 +1,25 @@
+---
+nav_title: 4월
+page_order: 9
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 4월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2019년 4월
+
+## 신규 커런츠 이벤트 및 분야
+
+섹션의 일부 수정 사항과 더불어, 메시지 인게이지먼트 이벤트 페이지에 새로운 \[구독 이벤트]({{ site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/#subscription-events)가 추가되었습니다. 
+
+이제 구독 그룹 상태 변경 데이터를 Braze에서 [세그먼트]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/segment_for_currents/#integration-details) 및 [mParticle]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle_for_currents/)로 내보낼 수 있을 뿐만 아니라 [Mixpanel]({{site.baseurl}}/partners/insights/behavioral_analytics/mixpanel_for_currents)에서 설치 경로 이벤트도 설치할 수 있습니다.
+
+또한 `canvas_step_id` 속성정보가 사용 가능한 [전환 이벤트에]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/#conversion-events) 추가되었습니다.
+
+{% alert important %}
+이러한 업데이트를 활용하려면 커런츠 커넥터 설정을 편집하고 사용하려는 이벤트를 활성화해야 합니다. 궁금한 점이 있으면 계정 관리자에게 문의하세요.
+{% endalert %}
+
+## 구독 그룹 아카이빙
+
+이제 [정기구독 그룹을 보관할]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#archiving-groups) 수 있습니다! 보관된 구독 그룹은 편집할 수 없으며 세그먼트 필터에 더 이상 표시되지 않습니다.  이메일, 캠페인 또는 캔버스에서 세그먼트 필터로 사용 중인 그룹을 보관하려고 하면 해당 그룹에 대한 모든 사용을 제거할 때까지 그룹을 보관할 수 없다는 오류 메시지가 표시됩니다.
diff --git a/_lang/ko/_help/release_notes/2019/august.md b/_lang/ko/_help/release_notes/2019/august.md
new file mode 100644
index 00000000000..b485a2c8432
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/august.md
@@ -0,0 +1,33 @@
+---
+nav_title: 8월
+page_order: 5
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 8월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2019년 8월
+
+## 보고서의 캠페인 세부 정보
+
+이제 캠페인 실적 보고서에 캠페인 세부 정보가 나열되므로 보고서를 설정할 때 선택한 전달, 대상 또는 전환 설정을 확인하기 위해 캠페인으로 돌아갈 필요가 없습니다.
+
+![캠페인 세부 정보]({% image_buster /assets/img/campaign_details_update.png %})
+
+## 새로운 이메일 콘텐츠 블록 API 엔드포인트
+
+이제 API를 통해 이메일 콘텐츠 블록을 관리[(생성]({{site.baseurl}}/api/endpoints/email_templates/#create-content-block), [사용 가능한 목록]({{site.baseurl}}/api/endpoints/email_templates/#list-available-content-blocks), [정보 가져오기]({{site.baseurl}}/api/endpoints/email_templates/#see-content-block-information))할 수 있습니다!
+
+{% alert update %}
+이 기능은 일시적으로 제한적으로 제공됩니다. 자세한 내용은 Braze 계정 관리자에게 문의하세요.
+{% endalert %}
+
+## 사용자 지정 이메일 수신 거부 랜딩 페이지 업데이트
+
+기본 [사용자 지정 이메일 수신 거부 페이지가]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#custom-unsubscribe-landing-page) 보다 세련되고 현대적인 디자인으로 업데이트되었습니다.
+
+## iOS SDK: 노치폰 지원 개선
+
+"노치형" 기기(예: iPhone X, Pixel 3XL)에서 인앱 메시지 지원이 개선되었습니다. 이제 전체 화면 메시지가 확장되어 모든 휴대폰의 전체 화면을 채우면서 상태 표시줄을 덮을 수 있습니다.
+
+아직 Braze 설명서에 이 변경 사항이 반영된 업데이트가 많이 보이지는 않겠지만, 곧 업데이트가 진행될 예정입니다!
diff --git a/_lang/ko/_help/release_notes/2019/december.md b/_lang/ko/_help/release_notes/2019/december.md
new file mode 100644
index 00000000000..d67d565aa85
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/december.md
@@ -0,0 +1,12 @@
+---
+nav_title: 12월
+page_order: 1
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 12월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2019년 12월
+
+12월 코드 동결로 인해 12월 릴리즈 노트가 없습니다. 
+
+추가 업데이트는 다음 달 릴리스 노트에서 확인하세요.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2019/february.md b/_lang/ko/_help/release_notes/2019/february.md
new file mode 100644
index 00000000000..33a7db98edd
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/february.md
@@ -0,0 +1,21 @@
+---
+nav_title: 2월
+page_order: 11
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 2월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2019년 2월
+
+## 이메일 구독 그룹
+
+[구독 그룹]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#subscription-groups) 위의 [글로벌 구독 상태]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/)에서 오디언스를 더욱 좁힐 수 있는 세그먼트 필터입니다. 이러한 그룹은 최종 사용자에게 보다 세분화된 구독 옵션을 제공할 수 있는 기능을 제공합니다.
+
+예를 들어, 여러 카테고리의 이메일 캠페인을 발송하는 경우 [이메일 환경설정 센터를](#email-preference-center) 사용하여 고객에게 단일 페이지에서 해당 그룹을 일괄적으로 구독하거나 구독을 취소할 수 있는 옵션을 제공할 수 있습니다.
+
+[구독 그룹 REST API를]({{site.baseurl}}/developer_guide/rest_api/subscription_group_api/) 사용하여 Braze 대시보드에 저장한 구독 그룹을 프로그래밍 방식으로 관리하려면 **구독 그룹** 페이지로 이동합니다.
+
+## 이메일 환경설정 센터
+
+[이메일 환경설정 센터를]({{site.baseurl}}/user_guide/message_building_by_channel/email/managing_user_subscriptions/#email-preference-center) 통해 특정 그룹의 뉴스레터를 수신할 사용자를 쉽게 관리할 수 있습니다. 생성하는 각 구독 그룹은 환경설정 센터 목록에 추가됩니다. 환경설정 센터의 이름을 클릭하면 대화형 미리 보기를 볼 수 있습니다.
+
diff --git a/_lang/ko/_help/release_notes/2019/january.md b/_lang/ko/_help/release_notes/2019/january.md
new file mode 100644
index 00000000000..70214e04b02
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/january.md
@@ -0,0 +1,26 @@
+---
+nav_title: 1월
+page_order: 12
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 1월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2019년 1월
+
+새해를 맞이한 것을 환영합니다!
+
+## 푸시 타임 투 라이브(TTL)
+
+계정의 **설정 관리에서** [푸시 TTL 설정]({{site.baseurl}}/user_guide/administrative/app_settings/push_ttl_settings/) 탭을 클릭하여 디바이스가 오프라인 상태일 때 재전송을 시도하는 시간을 관리할 수 있습니다.
+
+## 커넥티드 콘텐츠 IP 화이트리스트
+
+Braze는 내부 팀의 인프라 업그레이드를 통해 이제 모든 클러스터에서 연결된 콘텐츠에 대한 IP 화이트리스트를 제공할 수 있게 되었음을 알려드리게 되어 기쁩니다. 향후에는 비유럽연합 클러스터를 위한 IP를 추가할 계획입니다.
+
+## 캔버스 지연
+
+모든 캔버스 단계를 즉시 전송할 수 있는 옵션을 추가했습니다.
+
+![캔버스 지연][1]
+
+[1]: {% image_buster /assets/img/canvas_delay_immediate.png %}
diff --git a/_lang/ko/_help/release_notes/2019/july.md b/_lang/ko/_help/release_notes/2019/july.md
new file mode 100644
index 00000000000..18013dd6aa4
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/july.md
@@ -0,0 +1,95 @@
+---
+nav_title: 7월
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 7월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2019년 7월
+
+{% alert update %}
+이번 달에는 Braze의 제품 출시 주기가 두 번(맞습니다. **두 번**) 있었습니다! 최신 릴리스는 상단에 표시되며, 이전 릴리스는 [이 페이지의 아래쪽에서 시작됩니다](#earlier-this-month)!
+{% endalert %}
+
+## SAML/SSO
+
+[싱글 사인온]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/) (SSO)을 통해 기업들은 Braze 대시보드에 대한 액세스를 안전하고 중앙 집중화된 방식으로 제어할 수 있습니다. 즉, 하나의 자격 증명 세트를 사용하여 Braze를 포함한 다양한 애플리케이션에 액세스할 수 있습니다.
+
+[OAuth 2.0 지원을 사용하는 Google 로그인](https://developers.google.com/identity/protocols/OAuth2) 외에도 기업들은 SAML(Security Assertion Markup Language)이 지원되는 SSO를 원합니다. 이를 통해 최신 업계 표준(SAML 2.0)을 지원하는 [Azure 액티브 디렉토리]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/) 및 [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/)를 비롯한 대규모 ID 공급자(IdP)와 원활하게 통합할 수 있습니다.
+
+Braze 지원:
+- [OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/)
+- [Azure 액티브 디렉토리]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/)
+- [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/)
+
+## 이벤트 API 키 표시 조정
+
+고객이 이 API 키에 액세스할 수 있도록 Adjust의 파트너 페이지를 업데이트했습니다.
+
+## 새로운 파트너
+
+새로운 파트너가 Alloys 프로그램에 합류하여 문서에 추가되었습니다! 신규 파트너 목록:
+- [FiveTran]({{site.baseurl}}/partners/fivetran/)
+- [Talon.One]({{site.baseurl}}/partners/talonone/)
+- [Voucherify]({{site.baseurl}}/partners/voucherify/)
+
+## 캠페인 세부 정보 개선
+
+확장된 캠페인 세부 정보는 이제 **캠페인** 페이지의 ...잠깐만..**.캠페인 세부 정보** 섹션에 표시됩니다!
+
+## 세그먼트 및 캔버스에 내 것만 표시
+
+**캠페인** 페이지의 '내 것만 표시' 확인 필터는 큰 인기를 얻고 있습니다. 따라서 캔버스 및 세그먼트 목록에도 이 옵션을 추가합니다!
+
+### 진급 행동
+
+이제 [사용자가 한 캔버스 단계에서 다음 단계로 넘어갈 시점]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/advancement/)을 선택할 수 있습니다. 이러한 옵션에는 "메시지 전송메" 및 "지연 후 전체 오디언스"가 포함됩니다.
+
+### 캔버스의 인앱 메시지
+
+이제 캔버스에서 [인앱 메시지]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/in-app_messages_in_canvas/)를 사용할 수 있습니다! 캔버스 단계를 추가하고 사용 가능한 채널을 탐색하여 인앱 메시지를 추가합니다.
+
+# 이달 초
+
+## 사용자 프로필 이미지 제거
+
+Braze 사용자 프로필과 사용자 검색에 표시되는 사용자 프로필 사진을 삭제합니다.
+
+## 콘텐츠 카드의 연결된 콘텐츠
+
+이제 [콘텐츠 카드에서]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/overview/) [커넥티드 콘텐츠]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/#about-connected-content) 문자열과 기능을 사용할 수 있습니다.
+
+외부 서버에 연결된 콘텐츠 호출은 사용자가 카드를 볼 때가 아니라 실제로 카드가 전송될 때 발생합니다. 이메일과 마찬가지로 동적 콘텐츠는 카드가 실제로 조회되는 시점이 아니라 전송 시점에 계산되고 결정됩니다.
+
+## "회신 주소"가 없습니다.
+
+이제 고객은 Braze의 **이메일 설정** 페이지 또는 [API]({{site.baseurl}}/api/endpoints/messaging/#email-object-specification)를 사용하여 이메일 메시지의 "회신 주소"로 `null` 값을 설정할 수 있습니다.  사용 시 답장은 나열된 "보낸 사람" 주소로 전송됩니다.  이제 "보낸 사람" 주소 필드를 `dan@emailaddress.com`으로 개인화할 수 있으며, 고객은 Dan에게 직접 답장할 수 있습니다.
+
+Braze에서 이메일 메시지의 '답장 받는 사람' 주소로 `null` 값을 설정하려면 탐색 메뉴에서 **설정 관리로** 이동한 다음 **이메일 설정** 탭으로 이동합니다. 발신 **이메일 설정** 섹션으로 스크롤하여 **"회신 주소" 제외를 선택하고 를"보낸 사람"을 기본 주소로 **하여 답장을 보냅니다.
+
+## 캠페인 비교
+
+하나의 창에서 [여러 캠페인을 한 번에 확인하여 상대적인 성과를]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/comparing_campaigns/) Braze에서 나란히 비교해보세요!
+
+## Liquid를 사용하여 발송 ID를 메시지로 템플릿화
+
+{% alert note %}
+`dispatch_id`에 대한 동작은 캔버스와 캠페인 간에 다르며, 이는 Braze가 캔버스 단계(예약 가능한 엔트리 단계 제외)를 "예약된" 경우에도 트리거된 이벤트로 취급하기 때문입니다. 캔버스 및 캠페인의 [`dispatch_id` 동작에]({{site.baseurl}}/help/help_articles/data/dispatch_id/) 대해 자세히 알아보세요.
+{% endalert %}
+
+메시지 내에서 메시지 발송을 추적하려면(예: URL) `dispatch_id`에서 템플릿을 만들 수 있습니다. [캔버스 속성]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/) 아래의 지원되는 개인화 태그 목록에서 이에 대한 서식을 찾을 수 있습니다.
+
+캠페인 생성 시 `api_id`를 사용할 수 없으므로 입력 안내로 템플릿이 지정되고 `dispatch_id_for_unsent_campaign`으로 미리 보기된다는 점에서 `api_id`와 동일하게 작동합니다. ID는 메시지가 전송되기 전에 생성되며 전송 시간에 포함됩니다.
+
+{% alert warning %}
+인앱 메시지에는 `dispatch_id`가 없으므로 `dispatch_id_for_unsent_campaign`의 Liquid 템플릿은 인앱 메시지에서 작동하지 않습니다.
+{% endalert %}
+
+## "내 것만 표시" 설정이 유지됨
+
+**캠페인** 그리드의 '내 것만 표시' 필터는 **캠페인** 페이지를 방문할 때마다 그대로 유지됩니다.
+
+## A/B 테스트 업데이트
+
+최대 8개의 배리언트항(및 선택 사항 제어)이 포함된 일회성 [A/B 테스트]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/multivariate_testing/)를 사용자가 지정한 캠페인 오디언스의 비율로 전송한 다음, 미리 예약된 시간에 나머지 오디언스에게 최적의 변형을 전송할 수 있습니다.
diff --git a/_lang/ko/_help/release_notes/2019/june.md b/_lang/ko/_help/release_notes/2019/june.md
new file mode 100644
index 00000000000..5b049ceff0b
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/june.md
@@ -0,0 +1,19 @@
+---
+nav_title: 6월
+page_order: 7
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 6월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2019년 6월
+
+## Snowflake 파트너십
+
+Braze가 Snowflake와의 파트너십을 발표하게 되어 자랑스럽게 생각합니다!
+
+Snowflake는 모든 데이터와 모든 사용자를 위해 특별히 제작된 SQL 클라우드 데이터 웨어하우스입니다. 특허를 받은 Snowflake의 고유한 아키텍처를 사용하면 모든 데이터를 쉽게 수집하고, 신속한 분석을 가능하게 하며, 모든 사용자를 위한 데이터 중심 인사이트를 도출할 수 있습니다.
+
+Braze는 Snowflake의 데이터 교환을 활용하여 입지를 구축하고, 신규 고객을 찾고, 지속적으로 성장하는 Snowflake 고객층을 통해 도달 범위를 확장합니다.
+
+이 파트너십에 대한 자세한 내용은 [여기](https://www.braze.com/perspectives/article/snowflake-partner-announcement) 또는 [문서에서]({{site.baseurl}}/partners/snowflake/) 확인하세요.
diff --git a/_lang/ko/_help/release_notes/2019/march.md b/_lang/ko/_help/release_notes/2019/march.md
new file mode 100644
index 00000000000..792a7e81f7c
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/march.md
@@ -0,0 +1,40 @@
+---
+nav_title: 3월
+page_order: 10
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 3월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2019년 3월
+
+## 인앱 메시지 - 3세대
+
+Braze는 최신 UX 및 UI 모범 사례를 준수하기 위해 인앱 메시지의 모양과 느낌을 개선했음을 발표하게 되어 자랑스럽게 생각합니다. 최신 인앱 메시지에서는 사용자가 메시지와 상호 작용할 수 있는 대상을 기대할 수 있습니다.
+- 더 큰 글꼴 크기
+- 세련된 간격
+- 새 닫기 `x` 자산
+- 뷰포트에 더 잘 맞도록 모든 메시지 유형에 대한 반응형 동작이 개선되었습니다.
+- 버튼 테두리로 버튼 간 사용자 지정 대비 만들기
+
+[새로운 인앱 메시지]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/overview/)를 통해 사용자와의 상호작용을 좋은 수준에서 앱의 미로와 같은 수준으로 끌어올릴 수 있습니다!
+
+![전체 화면 동작]({% image_buster /assets/img/full-screen-behavior.gif %}){: style="border:0px;"}
+
+### 해야 할 일
+
+[웹]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/#upgrading-the-sdk), [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overview), [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/)용 Braze SDK의 최신 버전으로 업데이트하는 것을 적극 권장합니다.
+
+그 후에는 바로 사용할 수 있습니다!
+
+## 콘텐츠 블록 아카이브 업데이트
+
+이제 [콘텐츠 블록]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/#archiving-content-blocks)을 아카이브하고 아카이브 해제할 수 있습니다.
+
+## Inkit 파트너 추가
+
+이제 [Inkit]({{site.baseurl}}/partners/inkit/)을 미리 디자인된 웹훅 템플릿으로 사용하거나 새 웹훅 캠페인을 만들 수 있습니다.
+
+## Google Cloud Storage
+
+[Google Cloud Storage]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/google_cloud_storage_for_currents/)는 더 이상 베타 버전이 아닙니다! Braze는 관심 있는 고객이 Braze 플랫폼 내에서 Google Cloud Storage를 사용할 수 있게 되었음을 자랑스럽게 발표합니다. Braze 계정에서 **기술 파트너로** 이동하여 Google 클라우드 스토리지를 검색합니다.
diff --git a/_lang/ko/_help/release_notes/2019/may.md b/_lang/ko/_help/release_notes/2019/may.md
new file mode 100644
index 00000000000..5fe95c3217c
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/may.md
@@ -0,0 +1,107 @@
+---
+nav_title: 5월
+page_order: 8
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 5월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2019년 5월
+
+## 콘텐츠 카드
+
+콘텐츠 카드는 고객의 앱 및 웹 경험 내에 표시되는 영구 콘텐츠입니다.
+
+콘텐츠 카드를 사용하면 고객의 경험을 방해하지 않고도 고객이 즐겨 사용하는 앱 내에서 바로 고도로 타겟팅된 풍부한 콘텐츠의 동적 스트림을 고객에게 보낼 수 있습니다. 또는 콘텐츠 카드를 이메일이나 푸시 알림과 같은 다른 채널과 페어링하여 일관된 마케팅 전략을 사용할 수 있습니다.
+
+![콘텐츠 카드 피드]({% image_buster /assets/img/cc-feed.png %}){: height="50%" width="50%"}
+
+또한 콘텐츠 카드는 카드 고정, 카드 방출, API 기반 전달, 커스텀 카드 만료 시간, 카드 분석 등 더욱 개인화된 기능을 지원합니다.
+
+알림 센터, 홈페이지 피드, 프로모션 피드를 만드는 데 사용할 수 있습니다.
+
+지원되는 Braze SDK 버전으로 업데이트해야 합니다:
+- iOS: 3.8.0 이상
+- Android: 2.6.0 이상
+- 웹: 2.2.0 이상
+
+[여기에서 콘텐츠 카드에 대해 자세히 알아보세요!]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/overview/)
+
+{% alert update %}
+커런츠용 콘텐츠 카드와 콘텐츠 카드용 API 설명서는 이번 주 후반에 출시될 예정입니다. 기대해 주세요!
+{% endalert %}
+
+## Roku 플랫폼 추가
+
+Braze의 기능에 새로운 채널이 추가되었습니다! 새로운 채널로 확장함으로써 고객은 시청 행동을 이해하여 데이터를 강화하거나 모든 관련 채널에서 소비자에게 의미 있는 경험을 제공할 수 있습니다.
+
+이제 데이터 강화 및 커스텀 이벤트 추적 기술을 위해 [Roku 기기에서 데이터를 검색]({{site.baseurl}}/developer_guide/platform_integration_guides/roku/initial_sdk_setup/)할 수 있습니다.
+
+## 캔버스 또는 캠페인 업데이트에 대한 알림 기본 설정
+
+이 [새로운 알림]({{site.baseurl}}/user_guide/administrative/company_settings/notification_preferences/#notification-preferences)은 캠페인이나 캔버스가 활성화, 업데이트, 재활성화 또는 비활성화되면 이메일을 통해 알려줍니다. Braze 계정의 **알림 환경설정에서** 이 기능을 활성화하세요.
+
+## Jampp 기술 파트너 문서
+
+Jampp는 모바일 고객을 확보하고 리타겟팅하기 위한 퍼포먼스 마케팅 플랫폼입니다. 행동 데이터와 예측 및 프로그래매틱 기술을 결합하여 소비자가 처음 구매하거나 더 자주 구매하도록 유도하는 개인 맞춤형 관련성 광고를 표시함으로써 광고주에게 수익을 창출합니다.
+
+Braze 고객은 이벤트를 Jampp로 스트리밍하도록 Braze 웹훅 채널을 구성하여 [Jampp와 통합]({{site.baseurl}}/partners/advertising_technologies/retargeting/jampp/)할 수 있습니다. 그 결과, 고객은 모바일 광고 생태계 내에서 Jampp를 통해 리타겟팅 이니셔티브에 더 풍부한 데이터 세트를 추가할 수 있습니다.
+
+## 인앱 메시지용 플랫폼 선택기
+
+캠페인 제작 과정에서 이 단계를 강조하는 플랫폼 선택 기능을 통해 인앱 메시지가 전달될 위치와 플랫폼을 쉽게 선택할 수 있습니다.
+
+![플랫폼 선택기][1]
+
+## 이메일용 발송 ID 커런츠 필드
+
+{% alert update %}
+`dispatch_id`에 대한 동작은 캔버스와 캠페인 간에 다르며, 이는 Braze가 캔버스 단계(예약 가능한 엔트리 단계 제외)를 "예약된" 경우에도 트리거된 이벤트로 취급하기 때문입니다. 캔버스 및 캠페인의 [`dispatch_id` 동작]({{site.baseurl}}/help/help_articles/data/dispatch_id/)에 대해 자세히 알아보세요.
+
+_2019년 8월에 업데이트되었습니다._
+{% endalert %}
+
+커런츠 기능을 지속적으로 개선하기 위해 모든 커넥터 유형에 걸쳐 커런츠 이메일 이벤트에 `dispatch_id` 필드를 추가하고 있습니다.
+
+`dispatch_id`는 Braze 플랫폼에서 전송되는 각 전송 또는 발송에 대해 생성된 고유 ID입니다.
+
+예약 메시지를 받는 모든 고객은 동일한 `dispatch_id`를 받지만, 작업 기반 또는 API 트리거된 메시지를 받는 고객은 메시지당 고유한 `dispatch_id`를 받습니다. `dispatch_id` 필드를 사용하면 어떤 반복 캠페인 인스턴스가 전환을 담당하고 있는지 식별할 수 있으므로 어떤 유형의 캠페인이 비즈니스 목표를 달성하는 데 도움이 되는지에 대한 더 많은 인사이트와 정보를 얻을 수 있습니다.
+
+## '내 것만 표시' 캠페인 정렬 기능
+
+사용자가 캠페인 그리드에서 `Only Show Mine` 확인란을 선택하면 로그인한 사용자가 만든 캠페인만 표시되도록 결과가 필터링됩니다. 또한 사용자는 `created_by_me:true` 을 입력하여 검색창을 사용할 수 있습니다.
+
+또한 캠페인 그리드 사이드바의 크기를 조정할 수 있습니다!
+
+## 별칭으로 사용자 삭제
+
+이제 `users/delete` 엔드포인트를 사용하여 [별칭별로 사용자를 삭제]({{site.baseurl}}/api/endpoints/user_data/#user-delete-request)할 수 있습니다!
+
+## 이메일 클릭 및 열람에 대한 고유한 계산
+
+이제 이메일의 고유 클릭 수와 고유 열람 횟수가 사용자당 7일을 기준으로 캡처되어 표시되며, 해당 7일 기간 내에 각 `dispatch_id`당 1씩 증가합니다.
+
+`dispatch_id`를 사용하면 반복 메시지에 각 메시지의 실제 고유 열람 수 또는 고유 클릭 수를 반영할 수 있습니다. 이제 고객들은 커런츠에서 `dispatch_id`를 통해 이 데이터를 쉽게 찾을 수 있습니다.
+
+이전 고유성 기간이 30일 이상이었기 때문에 Mailjet을 사용하는 모든 사용자도 이 수치가 급증하는 것을 볼 수 있습니다. 이 변경 사항은 3주 전에 알려드렸어야 합니다.  SendGrid 고객은 아무런 차이를 느끼지 못할 것입니다.
+
+업데이트된 용어는 [보고서 메트릭 용어집에서]({{site.baseurl}}/user_guide/data_and_analytics/report_metrics/) 검색할 수 있습니다.
+
+{% alert update %}
+`dispatch_id`에 대한 동작은 캔버스와 캠페인 간에 다르며, 이는 Braze가 캔버스 단계(예약 가능한 엔트리 단계 제외)가 "예약된" 경우에도 트리거된 이벤트로 취급하기 때문입니다. [캔버스와 캠페인의 [`dispatch_id` 동작]({{site.baseurl}}/help/help_articles/data/dispatch_id/)에 대해 자세히 알아보세요.
+
+_2019년 8월에 업데이트되었습니다._
+{% endalert %}
+
+
+## 참여도가 가장 높은 채널
+
+{% alert update %}
+[2019년 11월 제품 릴리스부터]({{site.baseurl}}/help/release_notes/2019/november/#intelligence-suite)'가장 참여도가 높은 채널'은 ['지능형 채널']({{site.baseurl}}/user_guide/intelligence/intelligent_channel/)로 이름이 변경되었습니다 [.]({{site.baseurl}}/user_guide/intelligence/intelligent_channel/)
+{% endalert %}
+
+참여도가 가장 높은 채널 필터는 선택한 메시징 채널이 "최고"의 채널인 오디언스 중 일부를 선택합니다. 이 경우 "최고"는 "사용자의 기록을 고려할 때 인게이지먼트 가능성이 가장 높음"을 의미합니다. 이메일, 웹 푸시 또는 모바일 푸시(사용 가능한 모든 모바일 OS 또는 기기 포함)를 채널로 선택할 수 있습니다.
+
+이 새 필터 확인하기: \[세분화 필터 라이브러리]({{site.baseurl }}/user_guide/engagement_tools/segments/segmentation_filters/).
+
+[1]: {% image_buster /assets/img/iam_platforms.gif %}
diff --git a/_lang/ko/_help/release_notes/2019/november.md b/_lang/ko/_help/release_notes/2019/november.md
new file mode 100644
index 00000000000..303345e2456
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/november.md
@@ -0,0 +1,33 @@
+---
+nav_title: 11월
+page_order: 2
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 11월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2019년 11월
+
+앞으로 더 추가될 예정입니다! 이달 말에 더 많은 업데이트를 다시 확인하세요!
+
+## 인텔리전스 스위트
+
+Braze의 [Intelligence Suite]({{site.baseurl}}/user_guide/intelligence/)는 데이터 기반 인사이트를 통해 의사결정을 자동화할 수 있도록 도와줍니다. 브랜드는 전달 시간부터 다변량 테스트에 이르기까지 이러한 도구와 기능을 사용하여 규모에 맞게 최적화되는 역동적인 크로스채널 경험을 만들 수 있습니다. <br> <br> Intelligence Suite는 세 가지 주요 기능으로 구성되어 있습니다. [인텔리전트 타이밍]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_timing/), [인텔리전트 채널]({{site.baseurl}}/user_guide/intelligence/intelligent_channel/) 및 [인텔리전트 선택]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_selection/).
+
+{% alert note %}
+"Intelligence Suite"는 이전에 "가장 참여도가 높은 채널", "Intelligent Timing", "다변량 및 A/B 테스트"로 알려진 기능들을 개정하고 그룹화한 것입니다.
+{% endalert %}
+
+## 인앱 메시지용 다크 모드 테마
+
+iOS 13과 Android 10 모두 휴대폰의 색상 테마를 "다크 모드"로 변경할 수 있는 설정이 도입되었습니다. 이 기능에 맞춰 Braze는 [인앱 메시지에 다크 모드]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/dark-mode/)를 도입했습니다! 이 기능을 사용하면 '밝은 테마'와 '어두운 테마'로 인앱 메시지를 만들 수 있습니다. 보내는 기기에 "다크 모드"가 활성화되어 있으면 선택한 다크 모드 테마가 메시지에 표시됩니다.
+
+<img src="{% image_buster /assets/img_archive/iam-dark-mode.gif %}" style="width:100%;max-width:800px;" />
+
+## 참여 보고서의 SMS 지표
+
+이제 [참여 보고서]({{site.baseurl}}/user_guide/data_and_analytics/reporting/engagement_reports/)에서 SMS 측정기준을 사용할 수 있습니다!
+
+## Braze 사용자의 팀 삭제
+
+이제 Braze 사용자 계정에서 팀을 삭제할 수 있습니다!
diff --git a/_lang/ko/_help/release_notes/2019/october.md b/_lang/ko/_help/release_notes/2019/october.md
new file mode 100644
index 00000000000..7efe7f2674b
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/october.md
@@ -0,0 +1,25 @@
+---
+nav_title: 10월
+page_order: 3
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 10월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2019년 10월
+
+## 향상된 캔버스 변형 분석
+
+캔버스에는 각 이형 상품의 성과를 확인할 수 있는 새롭고 개선된 분석 기능이 있습니다. 특히 전환 이벤트 및 신뢰도와 관련된 새로운 측정기준을 셀 복사, API ID, 결과 다운로드(`.csv`)와 같은 새로운 기능이 있습니다. [개선된 캔버스 변형 분석에]({{site.baseurl}}/user_guide/engagement_tools/canvas/get_started/measuring_and_testing_with_canvas_analytics/#performance-breakdown-by-variant) 대해 자세히 알아보세요.
+
+## SMS
+
+이제 Braze에서 캠페인, 캔버스, [커런트가]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/message_engagement_events/) 포함된 SMS를 제공합니다! 시작하기 위한 [설정 가이드와]({{site.baseurl}}/user_guide/onboarding_with_braze/sms_setup/) 자세한 내용은 [SMS 전송 가이드를]({{site.baseurl}}/user_guide/message_building_by_channel/sms/) 확인하세요!
+
+## 콘텐츠 블록 개선 사항
+
+이제 콘텐츠 블록의 API ID가 대시보드의 선택한 콘텐츠 블록 페이지에 표시됩니다. 또한 콘텐츠 블록이 사용되는 위치도 표시합니다.
+
+## API를 통한 별칭 전용 사용자 생성 및 식별
+
+이제 속성 개체의 모든 필드에 [API 요청을 사용하면]({{site.baseurl}}/api/endpoints/user_data/#user-attributes-object-specification) 지정된 고객 프로필에 지정된 값으로 해당 이름의 속성을 만들거나 업데이트할 수 있습니다.
diff --git a/_lang/ko/_help/release_notes/2019/september.md b/_lang/ko/_help/release_notes/2019/september.md
new file mode 100644
index 00000000000..6eaeaacf786
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2019/september.md
@@ -0,0 +1,43 @@
+---
+nav_title: 9월
+page_order: 4
+noindex: true
+page_type: update
+description: "이 문서에는 2019년 9월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2019년 9월
+
+## OneLogin 내 Braze 앱
+
+고객은 SP 또는 IdP 시작 로그인을 위해 [원로그인]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/) 내에서 Braze를 간단히 검색하고 선택할 수 있습니다. 즉, 고객은 OneLogin 내에서 커스텀 애플리케이션을 추가할 필요가 없습니다. 그 결과, SAML SSO를 시작한 이후 나타난 속성 등의 특정 설정이 미리 채워집니다.
+
+## Rokt 캘린더 파트너십
+
+[Rokt 캘린더는]({{site.baseurl}}/partners/additional_channels/calendar/rokt_calendar/) Braze 고객에게 개인화된 마케팅 이니셔티브를 조정하고 개인화된 콘텐츠를 최종 사용자의 캘린더로 확장할 수 있는 기능을 제공합니다. 이를 통해 최종 사용자에게 보다 원활한 경험을 제공하고 고객 서비스와의 밀착도를 더욱 높일 수 있습니다. 고객은 다음을 수행할 수 있습니다.
+
+- Braze 플랫폼을 통해 캘린더 초대를 보내 "날짜 저장"을 하고 커뮤니케이션을 확장하세요
+- 이벤트 내용이 변경된 경우 기존 초대를 업데이트합니다.
+
+## Passkit 파트너십
+
+Braze 고객은 [Passkit]({{site.baseurl}}/partners/additional_channels/mobile_wallet/passkit/)을 통해 모바일 지갑으로 고객 참여를 확대할 수 있습니다. Braze의 강력한 세분화 기능을 사용하여 개인화된 지갑 캠페인을 진행하고 푸시, 인앱 메시지 등의 채널과 함께 오케스트레이션할 수 있습니다.
+
+## 메시징 엔드포인트를 통한 디스패치 ID 값 반환
+
+메시지의 `dispatch_id` 은 다음 메시징 엔드포인트 응답에 포함됩니다:
+- [`/campaigns/trigger/send`]({{site.baseurl}}/api/endpoints/messaging/#sending-messages-via-api-triggered-delivery)
+- [`/campaigns/trigger/schedule`]({{site.baseurl}}/api/endpoints/messaging/#create-schedule-endpoint)
+- [`/messages/send`]({{site.baseurl}}/api/endpoints/messaging/#sending-messages-immediately-via-api-only)
+- [`/messages/schedule`]({{site.baseurl}}/api/endpoints/messaging/#create-schedule-endpoint)
+- [`/canvases/trigger/send`]({{site.baseurl}}/api/endpoints/messaging/#canvas)
+- [`/canvases/trigger/schedule`]({{site.baseurl}}/api/endpoints/messaging/#api-triggered-canvases)
+
+이렇게 하면 트랜잭션 메시징을 사용하는 고객이 커런츠를 통해 콜백을 추적할 수 있습니다.
+
+## 캔버스 변경 로그
+
+계정에서 캔버스 작업을 하는 사람에 대한 세부 정보가 더 궁금하신가요? 더 이상 궁금해하지 마세요! 이제 캔버스 변경 로그에 액세스할 수 있습니다.
+
+![캔버스 변경 로그]({% image_buster /assets/img/canvas-changelog1.png %})
+![캔버스 변경 로그]({% image_buster /assets/img/canvas-changelog2.png %})
diff --git a/_lang/ko/_help/release_notes/2020.md b/_lang/ko/_help/release_notes/2020.md
new file mode 100644
index 00000000000..3801ed5b50c
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020.md
@@ -0,0 +1,49 @@
+---
+page_order: 4
+nav_title: 2020
+layout: dev_guide
+noindex: true
+guide_top_header: "2020 릴리스 노트"
+
+page_type: landing
+description: "이 섹션은 2020년 릴리스 노트가 있는 곳입니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 1월
+    link: /docs/help/release_notes/2020/january/
+    image: /assets/img/braze_icons/snowflake-01.svg
+  - name: 2월
+    link: /docs/help/release_notes/2020/february/
+    image: /assets/img/braze_icons/hearts.svg
+  - name: 3월
+    link: /docs/help/release_notes/2020/march/
+    image: /assets/img/braze_icons/trophy-01.svg
+  - name: 4월
+    link: /docs/help/release_notes/2020/april/
+    image: /assets/img/braze_icons/droplets-01.svg
+  - name: 5월
+    link: /docs/help/release_notes/2020/may/
+    image: /assets/img/braze_icons/sun.svg
+  - name: 6월
+    link: /docs/help/release_notes/2020/june/
+    image: /assets/img/braze_icons/umbrella-03.svg
+  - name: 7월
+    link: /docs/help/release_notes/2020/july/
+    image: /assets/img/braze_icons/flag-01.svg
+  - name: 8월
+    link: /docs/help/release_notes/2020/august/
+    image: /assets/img/braze_icons/wind-02.svg
+  - name: 9월
+    link: /docs/help/release_notes/2020/september/
+    image: /assets/img/braze_icons/backpack.svg
+  - name: 10월
+    link: /docs/help/release_notes/2019/october/
+    image: /assets/img/braze_icons/magic-wand-02.svg
+  - name: 11월
+    link: /docs/help/release_notes/2020/november/
+    image: /assets/img/braze_icons/cloud-sun-02.svg
+  - name: 12월
+    link: /docs/help/release_notes/2020/december/
+    image: /assets/img/braze_icons/gift-01.svg
+---
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2020/april.md b/_lang/ko/_help/release_notes/2020/april.md
new file mode 100644
index 00000000000..32cc43e8010
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/april.md
@@ -0,0 +1,46 @@
+---
+nav_title: 4월
+page_order: 9
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 4월 릴리스 노트가 포함되어 있습니다."
+---
+# 2020년 4월
+
+## Movable Ink 파트너십
+
+Movable Ink는 Braze 고객에게 푸시, 인앱 메시지 및 콘텐츠 카드 캠페인에서 카운트다운 타이머, 설문 조사 및 긁기와 같은 지능형 크리에이티브 기능을 사용할 수 있는 기능을 제공합니다. Movable Ink와 Braze는 데이터 중심의 동적 메시지에 대한 보다 균형 잡힌 접근 방식을 제공하여 사용자에게 중요한 것들에 대한 실시간 요소를 제공합니다.
+
+귀하의 캠페인에 [Movable Ink]({{site.baseurl}}/partners/channel_extensions/creative_and_personalization/intelligent_creative/movable_ink/) 통합을 시작하세요!
+
+## Intelligent Timing
+
+캠페인을 예약할 때, [Intelligent Timing]({{site.baseurl}}/user_guide/sage_ai/intelligence/intelligent_timing/)(이전의 Intelligent Delivery)를 사용하여 각 사용자가 참여할 가능성이 가장 높은 시간에 메시지를 전달할 수 있습니다. 이 시간은 Braze가 결정합니다.
+
+이 기능에 대한 업데이트는 다음을 포함합니다:
+- **방해금지 시간에 대한 설명**: 방해금지 시간 기능은 동일하게 유지되지만, UI는 명확성을 위해 조정되었습니다.
+- **미리보기 차트 추가**: 이제 Intelligent Timing을 사용하여 하루 중 각 시간에 메시지를 받을 사용자의 수와 최적의 시간을 계산할 수 있는 충분한 데이터를 가진 사용자의 비율을 확인할 수 있는 차트를 생성할 수 있습니다.
+- **커스텀 대체 추가**: 이제 사용자가 최적의 시간을 계산하기에 충분한 인게이지먼트 데이터가 부족할 때 메시지를 보낼 현지 시간을 선택할 수 있습니다.
+
+## Facebook 오디언스 내보내기
+
+Braze는 Braze 세그먼트 페이지에서 사용자를 수동으로 내보내 Facebook 커스텀 오디언스를 생성할 수 있는 기능을 제공합니다. 이것은 일회성 정적 오디언스 내보내기이며 새 [Facebook 커스텀 오디언스]({{site.baseurl}}/partners/facebook/)만 생성됩니다.
+
+현재 모든 클러스터에서 사용할 수 있는 새로운 Braze Facebook 오디언스 내보내기 프로세스가 있으며, 간단한 통합 단계로 프로세스를 간소화합니다. 더 이상 OAuth 리디렉션 URI를 화이트리스트에 추가하여 커스텀 오디언스를 전송하거나 Facebook 앱 설정 내에서 통합할 필요가 없습니다.
+
+{% alert important %}
+모든 클라이언트는 현재 Facebook 커스텀 오디언스를 사용하고 있으며, 새로운 단계로 Braze 세그먼트를 다시 통합해야 합니다.
+{% endalert%}
+
+
+## 콘텐츠 블록 및 이메일 템플릿 API 업데이트
+
+[template/email/list]({{site.baseurl}}/api/endpoints/templates/email_templates/get_list_email_templates/) 및 [content_block/list]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/get_list_email_content_blocks/) API 엔드포인트가 새로운 `tags` 필드를 포함하도록 업데이트되었습니다. 이 필드는 현재 블록 또는 이메일 템플릿에 적용되는 모든 태그를 배열로 나열합니다.
+
+## 개인화된 from-address
+
+Braze 내에서 이메일 메시지를 작성할 때, 이제 이메일 작성의 **보내기 정보** 섹션에서 메시지의 발신 주소를 개인화할 수 있습니다. 당사의 지원되는 [개인화 태그]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/)를 사용할 수 있습니다
+
+![개인화된 From Address][0]{: style="max-width:80%"}
+
+[0]: {% image_buster /assets/img/personalized-from-name.png %}
diff --git a/_lang/ko/_help/release_notes/2020/august.md b/_lang/ko/_help/release_notes/2020/august.md
new file mode 100644
index 00000000000..19b0d0f5475
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/august.md
@@ -0,0 +1,38 @@
+---
+nav_title: 8월
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 8월의 릴리스 노트가 포함되어 있습니다."
+---
+# 8월
+
+## 외부 ID 마이그레이션 엔드포인트
+
+Braze는 두 개의 새로운 외부 ID 마이그레이션 엔드포인트를 출시했습니다. 이러한 엔드포인트를 통해 고객은 Braze API를 활용하여 사용자의 Braze 외부 ID의 이름을 변경하거나 제거할 수 있습니다. 이러한 엔드포인트를 활용하여 다른 이름 지정 스키마를 가진 사용자를 마이그레이션하는 동시에 해당 사용자의 기록 데이터를 유지할 수 있습니다. [`users.external_ids.rename`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_rename/) 및 [`users.external_ids.remove`]({{site.baseurl}}/api/endpoints/user_data/external_id_migration/post_external_ids_remove/) 엔드포인트에 대한 자세한 내용은 Braze 설명서를 참고하세요.
+
+## Predictive Churn
+
+Braze의 Predictive Suite은 머신 러닝을 직접 손에 넣을 수 있습니다. [예측 이탈]({{site.baseurl}}/user_guide/predictive_suite/)을 시작으로, 그 어느 때보다 쉽게 데이터를 효과적으로 활용하고 Braze 플랫폼 내에서 원활하게 조치를 취할 수 있습니다. 이를 통해 특정 고객층의 이탈 위험을 예측하는 맞춤형 머신러닝 모델을 만든 다음, 머신러닝이 위험하다고 판단한 사용자에게 너무 늦기 전에 메시지를 보낼 수 있습니다. 
+
+이 기능의 미리보기는 8월 초에 해당되는 Braze 고객의 대시보드에 표시될 예정입니다. 전체 기능을 이용하려면 계정 관리자에게 문의하세요.
+
+## 커런츠 추적 기술 속성정보 업데이트
+
+특정 커런츠 메시지 인게이지먼트 이벤트 내에서 추적 기술 속성정보 `canvas_variation_name` 및 `canvas_step_name`이 추가되었습니다. 전체 목록은 [메시지 참여 이벤트 용어집과]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) [커런츠 변경 로그에서]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/) 확인하세요.
+
+## Amazon 개인화 파트너십
+
+Amazon Personalize는 머신 러닝을 사용하여 웹사이트와 애플리케이션에 대한 고품질 추천을 생성합니다. Amazon 개인화를 사용하면 실시간 개인화된 상품 및 콘텐츠 추천과 타겟 마케팅 프로모션을 통해 고객 참여를 향상시킬 수 있습니다. 자세한 내용은 [Amazon 개인화]({{site.baseurl}}/partners/data_augmentation/recommendation/amazon_personalize/) 문서를 참조하세요.
+
+## Vizbee 파트너십
+
+Vizbee를 사용하면 집에 있는 모든 스마트폰과 스마트 TV를 하나의 원활한 기기로 통합하여 뛰어난 사용자 경험을 제공할 수 있습니다. Vizbee는 알림, 딥링크, 이메일과 같은 기존 모바일 앱 마케팅 채널을 활용하여 모든 CTV 기기(예: Roku, FireTV, 삼성 TV, LG TV 등)에서 시청자를 확보하고 참여를 유도할 수 있도록 지원합니다. 자세한 내용은 [Vizbee]({{site.baseurl}}/partners/channel_extensions/deep_linking/vizbee_for_tv_deeplinking/) 설명서를 참조하십시오. 
+
+## Bluedot 파트너십
+
+Bluedot은 앱에 정확하고 간단한 지오펜싱을 제공하는 위치 플랫폼입니다. Bluedot의 SDK를 사용하여 더 스마트하게 메시지를 보내고, 모바일 주문 체크인을 자동화하고, 워크플로를 최적화하고, 마찰 없는 경험을 만들 수 있습니다. 자세한 내용은 [Bluedot]({{site.baseurl}}/partners/data_augmentation/contextual_location/bluedot/#bluedot) 설명서를 참조하세요. 
+
+## 파트너십 반복
+
+Iterate는 브랜드와 같은 모양과 느낌의 스마트하고 사용자 친화적인 설문조사 도구를 제공하여 고객으로부터 쉽게 학습할 수 있도록 도와줍니다. 자세한 내용은 [반복하기]({{site.baseurl}}/partners/additional_channels/surveys/iterate/) 문서를 참조하세요. 
diff --git a/_lang/ko/_help/release_notes/2020/december.md b/_lang/ko/_help/release_notes/2020/december.md
new file mode 100644
index 00000000000..e6ef7b5a81f
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/december.md
@@ -0,0 +1,40 @@
+---
+nav_title: 12월
+page_order: 1
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 12월 릴리스 노트가 포함되어 있습니다."
+---
+# 2020년 12월
+
+## 커런츠 메시징 이벤트 속성정보 업데이트
+
+커런츠 이메일 메시징 인게이지먼트 이벤트 내에서 추적 기술 속성정보`ip_pool`가 추가되었습니다. `bounce_reason` 및 `bounce_code`보 추적 기술 속성정보가 `users.messages.email.Bounce` 및 `users.messages.email.SoftBounce` 이벤트에도 추가되었습니다. <br>전체 목록은 [메시지 참여 이벤트 용어집]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)에서 확인하세요.
+
+## 예측 이탈 FAQ
+
+자주 묻는 질문 기사가 기존의 예측 이탈 설명서에 추가되었습니다. 이러한 잠재적인 오류, 타이밍 명확성 및 데이터 고려 사항에 대해 자세히 알아보려면 [예측 이탈 FAQ]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/prediction_faq/)를 확인하세요.
+
+## CSV 및 API 내보내기 문제 해결 문서
+
+Braze 설명서에 일반적인 CSV 및 API 오류를 설명하는 문제 해결 문서가 추가되었습니다. 이러한 오류 및 자주 묻는 질문에 대해 자세히 알아보려면 CSV 및 API 내보내기 [문제 해결]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/export_troubleshooting/) 설명서를 확인하세요. 
+
+## EduMe 파트너십
+
+EduMe는 귀하의 직원들에게 성공에 필요한 지식을 제공하는 모바일 기반 교육 도구입니다. Braze에서 연결된 콘텐츠를 사용하여 EduMe에서 귀하의 직원이나 고객에게 수업 및 강좌에 대한 액세스를 제공하세요. 이들은 브라우저에서 이 콘텐츠에 원활하게 액세스할 수 있으며, EduMe 보고 기능을 사용하여 그룹 또는 개인으로서의 진행 상황을 추적할 수 있습니다. 자세한 내용은 [EduMe]({{site.baseurl}}/partners/channel_extensions/learning/edume/) 설명서를 참조하십시오.
+
+## Pypestream 파트너십
+
+Pypestream은 브랜드를 "항상 켜져 있는" 디지털 엔티티로 변환하기 위해 특허받은 올인원 클라우드 메시징을 제공하는 풀스택 대화형 AI 플랫폼입니다. Braze-Pypestream 파트너십을 통해 브랜드는 초기 아웃리치에서 대화형 경험으로 라우팅되고, 지능형 리타겟팅을 통한 옴니채널 후속 조치까지 고객 생애주기를 원활하게 조정할 수 있습니다. 자세한 내용은 [Pypestream]({{site.baseurl}}/partners/advertising_technologies/attribution/pypestream/) 설명서를 참조하십시오.
+
+## Dyspatch 파트너십
+
+Dyspatch를 사용하면 직관적인 드래그 앤 드롭 이메일 작성기를 사용하여 코드를 작성할 필요 없이 아름답고 반응이 빠르며 매력적인 이메일을 만들 수 있습니다. Dyspatch 내에서 팀과 협력하여 이메일을 작성하고 승인한 후 Braze 내에서 사용할 수 있도록 업로드하세요. 이 모든 것이 몇 단계 안에 가능합니다! 자세한 내용은 [Dyspatch]({{site.baseurl}}/partners/channel_extensions/creative_and_personalization/email_orchestration/dyspatch/) 설명서를 참조하십시오.
+
+## Rudderstack 파트너십
+
+RudderStack은 오픈 소스 고객 데이터 인프라로, 고객 이벤트 데이터를 수집하고 선호하는 데이터 웨어하우스 및 Braze와 같은 수십 개의 다른 분석 제공업체로 라우팅합니다. 엔터프라이즈 준비가 되어 있으며, 이벤트 데이터를 실시간으로 처리할 수 있는 강력한 변환 프레임워크를 제공합니다. 자세한 내용은 [Rudderstack]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/rudderstack/#rudderstack) 설명서를 참조하십시오.
+
+## Jebbit 파트너십
+
+Jebbit은 사용자가 퍼스트파티 데이터를 수집하기 위해 매력적인 경험을 구축할 수 있는 PaaS입니다. Jebbit는 Braze와 제휴하여 Jebbit 캠페인에서 사용자 이메일과 속성을 실시간으로 Braze에 사용자 데이터로 전달할 수 있습니다. 이 데이터는 개인화된 이메일 캠페인 및 트리거와 같은 마케팅 이니셔티브를 추진하는 데 활용될 수 있습니다. 자세한 내용은 [Jebbit]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/jebbit/#jebbit) 설명서를 참조하십시오.
diff --git a/_lang/ko/_help/release_notes/2020/february.md b/_lang/ko/_help/release_notes/2020/february.md
new file mode 100644
index 00000000000..a987ce8d857
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/february.md
@@ -0,0 +1,24 @@
+---
+nav_title: 2월
+page_order: 11
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 2월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2020년 2월
+
+## 리텐션 보고서
+
+Braze는 이제 캠페인을 위한 [리텐션 리포트를]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/retention_reports/) 제공합니다. 이 기능은 특정 캠페인에서 메시지를 받은 사용자에 대한 사용자 리텐션을 측정하는 데 도움이 됩니다. 리텐션 보고서는 대시보드 내 **캠페인 분석** 페이지에서 편리하게 확인할 수 있습니다. 
+
+![전체 보고서][4]
+
+{% alert important %}
+2020년 1월 13일 현재 이 기능은 EU 지역에 배포된 클라이언트나 HIPPA 준수 클러스터에서는 아직 사용할 수 없습니다. 전체 플랫폼에 기능을 지속적으로 배포하면서 해당 지역에서도 이 보고서를 사용할 수 있도록 할 예정입니다.
+{% endalert %}
+
+## 새로운 이메일 콘텐츠 차단 API 엔드포인트
+
+이제 API를 통해 이메일 콘텐츠 블록을 [업데이트할]({{site.baseurl}}/api/endpoints/templates/content_blocks_templates/post_update_content_block/) 수 있습니다!
+
+[4]: {% image_buster /assets/img/retention_report_full_report.png %}
diff --git a/_lang/ko/_help/release_notes/2020/january.md b/_lang/ko/_help/release_notes/2020/january.md
new file mode 100644
index 00000000000..ea7b095f5d7
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/january.md
@@ -0,0 +1,16 @@
+---
+nav_title: 1월
+page_order: 12
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 1월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2020년 1월
+
+새해와 새로운 10년을 맞이한 것을 환영합니다! 
+
+## SMS 기능 추가
+
+이제 Braze를 사용하면 \[SMS 메시지의 빈도 제한]({{ site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/rate-limiting/)을 참고하세요. \[세그먼트 필터]({{ site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters/) "마지막으로 받은 SMS"를 추가할 수도 있습니다.
+
+사용자 설정 및 동작에 대한 자세한 내용은 [SMS 키워드 처리에서](/docs/user_guide/message_building_by_channel/sms/keywords/) 확인하세요.
diff --git a/_lang/ko/_help/release_notes/2020/july.md b/_lang/ko/_help/release_notes/2020/july.md
new file mode 100644
index 00000000000..18f0147cfd9
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/july.md
@@ -0,0 +1,34 @@
+--- 
+nav_title: 7월
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 7월 릴리스 노트가 포함되어 있습니다."
+---
+# 2020년 7월
+
+## 프로모션 코드
+
+Liquid을 사용하면 업로드한 [프로모션 코드][1] 목록에서 메시지를 가져올 수 있습니다. 이 기능은 최대 6개월의 만료 날짜를 제공하며 목록당 최대 20MM의 개별 코드를 지원합니다.
+
+## 배리언트 유지 보고서
+
+[캠페인][2] 또는 [캔버스][3]에 대한 유지 보고서를 볼 때 이제 결과를 배리언트별로 나누어 볼 수 있습니다. 
+
+## '필터' 옵션 캠페인 및 캔버스용
+
+캔버스 및 캠페인 GET 목록 엔드포인트에 대한 필터 옵션은 고객이 캠페인 또는 캔버스 메시지가 마지막으로 업데이트된 시간을 알 수 있도록 합니다.
+
+## 커런츠 `ad-id`
+
+새로운 `ad-id` (광고주 ID) 필드를 커런츠에 반영하기 위해 [스토리지 연결 설명서][4]를 업데이트했습니다.
+
+## BCC 기능
+
+[BCC 주소 설정][5]을 사용하면 Braze에서 발송되는 아웃바운드 이메일 메시지에 추가할 수 있는 BCC 주소를 추가하고 관리할 수 있습니다.	
+
+[1]: {{site.baseurl}}/user_guide/personalization_and_dynamic_content/promotion_codes/#promotion-codes
+[2]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/retention_reports/
+[3]: {{site.baseurl}}/user_guide/engagement_tools/canvas/retention_reports/
+[4]: {{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/#content-card-click-events
+[5]: {{site.baseurl}}/user_guide/administrative/app_settings/email_settings/
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2020/june.md b/_lang/ko/_help/release_notes/2020/june.md
new file mode 100644
index 00000000000..6cdeec00a8b
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/june.md
@@ -0,0 +1,22 @@
+---
+nav_title: 6월
+page_order: 7
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 6월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2020년 6월
+
+## 리텐션 보고서
+
+이제 리텐션 보고서에서 [캠페인과][2] [캔버스에][1] 대한 범위 리텐션을 제공합니다. 범위 유지는 특정 시간 간격 동안 얼마나 많은 사용자가 다시 돌아와서 선택한 유지 이벤트를 수행했는지 측정합니다. 
+
+## 사용자 추적 API 업데이트
+
+이제 [`users/track` 엔드포인트][3]는 2020년 6월 2일 이후에 생성된 대시보드 회사에 대해 분당 50,000건의 API 요청을 기본으로 처리합니다. 이 날짜 이전에 생성된 기존 회사 및 해당 워크스페이스는 `users/track` 엔드포인트에 대한 API 요청을 무제한으로 허용합니다.
+
+Braze는 API와 인프라의 안정성과 신뢰성 목표를 향한 한 걸음으로 가장 많이 사용되는 고객 대면 엔드포인트에 이 기본값을 적용하고 있습니다. 부과된 한도는 매우 느슨한 수준이며, 대시보드 회사 및 일반 운영에 영향을 미치는 경우는 극히 일부에 불과합니다. 이 한도를 늘려야 하는 경우 고객 성공 관리자 또는 지원팀에 문의하여 한도 증액을 요청하세요.
+
+[1]: {{site.baseurl}}/user_guide/engagement_tools/canvas/retention_reports/
+[2]: {{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/retention_reports/
+[3]: {{site.baseurl}}/api/endpoints/user_data/post_user_track/
diff --git a/_lang/ko/_help/release_notes/2020/march.md b/_lang/ko/_help/release_notes/2020/march.md
new file mode 100644
index 00000000000..00b6f288ba3
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/march.md
@@ -0,0 +1,20 @@
+---
+nav_title: 3월
+page_order: 10
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 3월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2020년 3월
+
+## 사용자 지정 속성 필터 동작
+
+대시보드의 [필터가 개선되어]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/#dates) 보다 직관적인 동작을 포함할 수 있게 되었습니다.
+특정 사용자 정의 속성 필터의 작동 방식에 두 가지 중요한 변경 사항이 있습니다. 
+
+사용자 지정 속성 필터 변경 사항은 필터에 반영됩니다: 
+- **X일** 전
+- 향후 **X일** 미만
+- 반복 이벤트의 날짜<br>
+
+세그먼트에 이러한 필터를 사용하는 경우 이러한 변경 사항을 고려하여 세그먼트를 다시 조정하는 것이 좋습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2020/may.md b/_lang/ko/_help/release_notes/2020/may.md
new file mode 100644
index 00000000000..b0de6989e6f
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/may.md
@@ -0,0 +1,79 @@
+---
+nav_title: 5월
+page_order: 8
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 5월 릴리스 노트가 포함되어 있습니다."
+---
+# 2020년 5월
+
+## Google Tag Manager
+
+[Google Tag Manager]({{site.baseurl}}/developer_guide/platform_integration_guides/android/advanced_use_cases/android_google_tag_manager/)를 사용하여 Braze의 Android 소프트웨어 개발 키트를 배포하고 관리하는 방법에 대한 설명서 및 예제가 추가되었습니다.
+
+## 새로운 블랙리스트 이메일 API 엔드포인트
+
+이제 Braze API를 통해 이메일 주소를 [블랙리스트에 추가]({{site.baseurl}}/api/endpoints/email/post_blacklist/)할 수 있습니다. 이메일 주소를 블랙리스트에 추가하면 사용자가 이메일에서 탈퇴하고 하드바운스로 표시됩니다.
+
+## Braze API 엔드포인트에 대한 API 키 변경
+
+2020년 5월부터 Braze는 API 키를 읽는 방식을 더 안전하게 변경했습니다. 이제 API 키는 요청 헤더로 전달되어야 합니다. 예제는 **예제 요청** 아래의 개별 엔드포인트 페이지와 **API 키 설명**에서 찾을 수 있습니다.
+
+Braze는 요청 본문과 URL 매개변수를 통해 전달되는 `api_key`를 계속 지원할 것이지만, 결국에는 중단될 예정입니다(TBD). **API 호출을 적절히 업데이트하세요.** 이러한 변경 사항은 [Postman](https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#intro) 내에서 업데이트되었습니다.
+{% details API 키 설명 %}
+{% tabs %}
+{% tab GET 요청 %}
+이 예제는 `/email/hard_bounces` 엔드포인트를 사용합니다.
+
+**이전: 요청 본문의 API 키**
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/email/hard_bounces?api_key={YOUR_REST_API_KEY}&start_date=2019-01-01&end_date=2019-02-01&limit=100&offset=1&email=foo@braze.com' \
+```
+**지금: 헤더의 API 키**
+```
+curl --location --request GET 'https://rest.iad-01.braze.com/email/hard_bounces?start_date=2019-01-01&end_date=2019-02-01&limit=100&offset=1&email=foo@braze.com' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY'
+```
+{% endtab %}
+{% tab POST 요청 %}
+이 예제는 `/user/track` 엔드포인트를 사용합니다.
+
+**이전: 요청 본문의 API 키**
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
+--header 'Content-Type: application/json' \
+--data-raw '{
+	"api_key": YOUR-API-KEY-HERE ,
+	"attributes": [ 
+ 	{
+ 	  "external_id":"user_id",
+      "string_attribute": "sherman",
+      "boolean_attribute_1": true,
+      "integer_attribute": 25,
+      "array_attribute": ["banana", "apple"]
+    }
+    ]
+}'
+```
+**지금: 헤더의 API 키**
+```
+curl --location --request POST 'https://rest.iad-01.braze.com/users/track' \
+--header 'Content-Type: application/json' \
+--header 'Authorization: Bearer YOUR-REST-API-KEY' \
+--data-raw '{
+	"attributes": [ 
+ 	{
+	  "external_id":"user_id",
+      "string_attribute": "sherman",
+      "boolean_attribute_1": true,
+      "integer_attribute": 25,
+      "array_attribute": ["banana", "apple"]
+    }
+    ]
+}'
+```
+{% endtab %}
+{% endtabs %}
+{% enddetails %}
+
+
diff --git a/_lang/ko/_help/release_notes/2020/november.md b/_lang/ko/_help/release_notes/2020/november.md
new file mode 100644
index 00000000000..25c9a131f57
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/november.md
@@ -0,0 +1,25 @@
+---
+nav_title: 11월
+page_order: 2
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 11월 릴리스 노트가 포함되어 있습니다."
+---
+ 
+# 2020년 11월
+
+## Tealium 파트너십이 시작되었습니다
+
+[Tealium]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/#about-tealium)은 모바일, 웹 및 타사 소스의 대체 데이터를 쉽게 연결할 수 있는 데이터 허브입니다. Braze와 연결되면 Tealium은 커스텀 이벤트, 사용자 속성 및 구매의 데이터 흐름을 실시간 데이터 작업을 위해 활성화합니다.
+
+## Braze 제품 포털
+
+[Braze 제품 포털]({{site.baseurl}}/user_guide/administrative/access_braze/portal/#product-portal-)에는 Braze 제품 로드맵과 사용자가 아이디어를 제출할 수 있는 기회가 포함되어 있습니다. 또한 최근에 출시된 기능을 확인할 수 있습니다. 제품 포털은 **리소스** 아래 Braze 대시보드에서 찾을 수 있습니다.
+
+## iOS 콘텐츠 카드 구현 가이드
+
+개발자 중심의 기술 전략을 수용하여, Braze는 사용 사례 중심의 iOS 콘텐츠 카드 지침 및 모범 사례를 강조하는 첫 번째 구현 가이드를 발표했습니다. 이 포괄적인 가이드는 고유한 사용 사례, 비디오 워크스루, 관련 코드 스니펫 및 귀중한 사용자 측정기준을 기록하는 방법에 대한 지침을 제공합니다. iOS 콘텐츠 카드를 전문가처럼 구현하는 방법에 대해 더 읽어보려면 [구현 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/content_cards/implementation_guide/)를 확인하세요. 
+
+## 스위프트 패키지 매니저
+
+[스위프트 패키지 매니저]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overviewswift_package_manager)는 스위프트 구축 시스템과 통합되어 있으며, 자동으로 종속성을 다운로드, 컴파일 및 링크합니다. 스위프트 패키지 매니저를 통해 iOS SDK를 설치하면 설치 과정의 대부분이 자동화됩니다.
diff --git a/_lang/ko/_help/release_notes/2020/october.md b/_lang/ko/_help/release_notes/2020/october.md
new file mode 100644
index 00000000000..2690e8a2cec
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/october.md
@@ -0,0 +1,41 @@
+---
+nav_title: 10월
+page_order: 3
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 10월 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2020년 10월
+
+## 보고서 빌더
+
+![캠페인 비교 예제][5]{: style="max-width:80%;"}
+
+[보고서 빌더]({{site.baseurl}}/report_builder)를 사용하면 여러 캠페인의 결과를 한 화면에서 비교할 수 있어 어떤 참여 전략이 주요 측정기준에 가장 큰 영향을 미쳤는지 쉽게 확인할 수 있습니다.
+
+## iOS 14 업그레이드 가이드
+
+iOS 14 업그레이드 가이드는 iOS 14에서 도입된 Braze 관련 변경 사항과 Braze iOS SDK 통합을 위한 필수 업그레이드 단계를 설명합니다. 미래의 IDFA 권한 요구 사항, 지오펜스 지원 및 필요한 Xcode 업그레이드가 주목할 만한 몇 가지 변경 사항입니다. [업그레이드 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/initial_sdk_setup/overview/)를 확인하여 더 읽어보세요. 
+
+## Android 11 업그레이드 가이드
+
+Android 11 가이드는 Android 11 릴리스에서 도입된 관련 변경 사항과 Braze Android SDK 통합을 위한 필수 업그레이드 단계를 설명합니다. 일부 변경 사항은 딥링크, HTML 인앱 메시지 및 위치 권한과 관련이 있습니다. [업그레이드 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_11/)를 확인하여 더 읽어보세요.
+
+## 기여도 파트너 - 클릭 추적 가이드
+
+선택적 기여도 파트너 클릭 추적 설명서가 이제 각 기여도 파트너 페이지에 추가되었습니다. 여기에는 캠페인에서 클릭 추적을 작동시키기 위한 모범 사례 및 구현 지침이 포함됩니다. 귀하의 [기여도 파트너]({{site.baseurl}}/partners/advertising_technologies/attribution/) 페이지를 방문하여 자세히 읽어보세요. 
+
+## 새 설명 필드
+
+사용자는 이제 캠페인 및 캔버스에 설명을 추가할 수 있습니다! 이 새 필드는 캠페인 또는 캔버스를 생성하거나 기존 캠페인을 편집할 때 캠페인 또는 캔버스 이름 필드 아래에서 찾을 수 있습니다. 
+
+## 캔버스 예외 이벤트
+
+새로운 설명서가 캔버스에서 [예외 이벤트]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/exception_events/)의 예상 동작을 설명하는 내용으로 추가되었습니다. 
+
+## 사용자 삭제 업데이트
+
+Braze는 고객이 추가적인 고객 조치 없이도 데이터 삭제를 요청하는 데이터 주체의 최종사용자 프로필뿐만 아니라 데이터 주체의 전화번호나 이메일 주소와 관련된 구독 상태도 동시에 삭제할 수 있도록 API를 개선했습니다. 업데이트된 설명서는 [여기]({{site.baseurl}}/help/dp-technical-assistance/#braze-recommendation-2)에서 찾을 수 있습니다
+
+[5]: {% image_buster /assets/img/campaign_comparison/campaign_main.png %} 
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2020/september.md b/_lang/ko/_help/release_notes/2020/september.md
new file mode 100644
index 00000000000..b5bc0005f91
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2020/september.md
@@ -0,0 +1,39 @@
+---
+nav_title: 9월
+page_order: 4
+noindex: true
+page_type: update
+description: "이 문서에는 2020년 9월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 9월
+
+## 퍼널 보고
+
+퍼널 리포팅은 고객이 [캠페인이나]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/campaign_funnel_report/) [캔버스를]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_funnel_reports) 수신한 후의 여정을 분석할 수 있는 시각적 보고서를 제공합니다.
+
+## iOS 14 업그레이드 가이드
+
+Apple의 새로운 iOS 14에서 발표된 변경 사항에 따라 Braze 관련 변경 사항과 Braze iOS SDK 통합에 필요한 조치 항목이 몇 가지 있습니다. 자세한 내용은 이 [업그레이드 가이드를]({{site.baseurl}}/ios_14/) 참조하세요.
+
+## iOS 14용 IDFA 및 IDFV 변경 사항
+
+iOS 14에서는 사용자가 광고 추적에 옵트인하고 앱과 광고 네트워크가 앱 방문 시 자신의 IDFA를 읽을 수 있도록 허용할지 여부를 결정해야 합니다. 따라서 Braze의 전략은 '공급업체 식별자'(예: IDFV)를 대신 사용하여 여러 기기에서 사용자를 계속 추적할 수 있도록 하는 것입니다. 자세한 내용은 [iOS 14 업그레이드 가이드]({{site.baseurl}}/ios_14/)를 참조하세요.
+
+## 이메일 유효성 검사
+
+이 새로운 이메일 구문 유효성 검사 프로세스는 Braze의 기존 프로세스를 업그레이드한 것입니다. 이 검사는 Braze로 업데이트하거나 가져온 이메일이 올바른지 확인하기 위한 검사입니다. 자세한 내용은 [이 가이드라인과 참고 사항]({{site.baseurl}}/user_guide/onboarding_with_braze/email_setup/email_validation)을 참조하세요.
+
+## 커런츠의 무작위 버킷 사용자 이벤트
+
+무작위 버킷 번호(예: RBN)는 워크스페이스 내에서 새 사용자가 생성될 때마다 발생합니다. 이 이벤트 기간 동안 각 신규 사용자에게는 무작위 버킷 번호가 할당되며, 이를 사용하여 균일하게 분포된 무작위 사용자 세그먼트를 생성할 수 있습니다. 이를 사용하여 다양한 임의의 버킷 번호 값을 그룹화하고 캠페인 및 캠페인 변형의 성과를 비교할 수 있습니다. 이 이벤트의 이용 가능 여부를 확인하려면 커런츠 [고객 행동 이벤트 용어집]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events/)을 참조하세요.
+
+## 캔버스 구성 요소 - 곧 출시됩니다!
+
+Braze는 캔버스의 유연성과 기능을 향상시키는 데 도움이 되는 네 가지 새로운 캔버스 구성 요소를 추가했습니다. 이러한 새로운 구성 요소에는 다음이 포함됩니다: [의사 결정 분할 단계]({{site.baseurl}}/decision_split/), [지연 단계]({{site.baseurl}}/delay_step/), [메시징 단계]({{site.baseurl}}/message_step/) 및 [대상 그룹을 Facebook에 동기화합니다]({{site.baseurl}}/audience_sync_facebook/).
+- **캔버스 의사 결정 분할, 지연 및 메시징 단계**<br>결정 분할을 사용하여 사용자가 정의된 쿼리와 일치하는지 여부에 따라 캔버스 브랜치를 만들 수 있습니다. 지연 단계를 사용하면 해당 메시지 없이도 캔버스에 독립형 지연을 추가할 수 있습니다. 메시징 단계를 사용하면 캔버스 흐름에서 원하는 위치에 독립형 메시지를 추가할 수 있습니다.
+- **Facebook에 오디언스 동기화**<br>브랜드는 Braze 오디언스 동기화 기능을 Facebook에 사용하여 자체 Braze 통합의 사용자 데이터를 Facebook 맞춤 오디언스에 추가하여 행동 트리거, 세분화 등을 기반으로 광고를 게재할 수 있습니다. 사용자 데이터를 기반으로 Braze 캔버스에서 메시지(푸시, 이메일, SMS, 웹훅 등)를 트리거하는 데 일반적으로 사용하는 모든 기준을 이제 Facebook 커스텀 오디언스에서 해당 사용자에게 광고를 트리거하는 데 사용할 수 있습니다.
+
+## SMS 인바운드 수신 이벤트
+
+커런츠에 새로운 메시징 인게이지먼트 이벤트가 추가되었습니다. 이 이벤트는 사용자 중 한 명이 Braze SMS 구독 그룹 중 하나에 있는 전화번호로 SMS를 보낼 때 발생합니다. 자세한 내용은 커런츠 [메시징 및 인게이지먼트 이벤트 용어집]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/)에서 확인하세요.
diff --git a/_lang/ko/_help/release_notes/2021.md b/_lang/ko/_help/release_notes/2021.md
new file mode 100644
index 00000000000..5c9700b6ab8
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021.md
@@ -0,0 +1,49 @@
+---
+page_order: 3
+nav_title: 2021
+layout: dev_guide
+noindex: true
+guide_top_header: "2021 릴리스 노트"
+
+page_type: landing
+description: "이 섹션에서는 2021년에 대한 릴리스 노트를 확인할 수 있습니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 1월
+    link: /docs/help/release_notes/2021/january/
+    image: /assets/img/braze_icons/snowflake-01.svg
+  - name: 2월
+    link: /docs/help/release_notes/2021/february/
+    image: /assets/img/braze_icons/hearts.svg
+  - name: 3월
+    link: /docs/help/release_notes/2021/march/
+    image: /assets/img/braze_icons/trophy-01.svg
+  - name: 4월
+    link: /docs/help/release_notes/2021/april/
+    image: /assets/img/braze_icons/droplets-01.svg
+  - name: 5월
+    link: /docs/help/release_notes/2021/may/
+    image: /assets/img/braze_icons/sun.svg
+  - name: 6월
+    link: /docs/help/release_notes/2021/june/
+    image: /assets/img/braze_icons/umbrella-03.svg
+  - name: 7월
+    link: /docs/help/release_notes/2021/july/
+    image: /assets/img/braze_icons/flag-01.svg
+  - name: 8월
+    link: /docs/help/release_notes/2021/august/
+    image: /assets/img/braze_icons/wind-02.svg
+  - name: 9월
+    link: /docs/help/release_notes/2021/september/
+    image: /assets/img/braze_icons/backpack.svg
+  - name: 10월
+    link: /docs/help/release_notes/2021/october/
+    image: /assets/img/braze_icons/magic-wand-02.svg 
+  - name: 11월
+    link: /docs/help/release_notes/2021/november/
+    image: /assets/img/braze_icons/cloud-sun-02.svg
+  - name: 12월
+    link: /docs/help/release_notes/2021/december/
+    image: /assets/img/braze_icons/gift-01.svg
+---
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2021/april.md b/_lang/ko/_help/release_notes/2021/april.md
new file mode 100644
index 00000000000..79f82fc0692
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/april.md
@@ -0,0 +1,41 @@
+---
+nav_title: 4월
+page_order: 8
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 4월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2021년 4월
+
+## iOS 푸시 고급 구현 가이드
+
+이 상세 가이드에서는 푸시 알림 콘텐츠 앱 확장 프로그램을 활용하여 푸시 메시지를 최대한 활용하는 방법에 대해 설명합니다. 여기에는 저희 팀이 구축한 세 가지 사용자 지정 사용 사례(대화형 푸시, 데이터 캡처 푸시, 진행률 기반 푸시)와 함께 제공되는 코드 스니펫, 로깅 분석에 대한 안내가 포함되어 있습니다. 자세한 내용은 [iOS 푸시 고급 구현 가이드](/docs/developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide/)를 참조하세요.
+
+## 멀티미디어 메시지 서비스(MMS)에 대한 VFC 지원
+
+가상 연락처 파일(VCF)이라고도 하는 vCard는 주소록/연락처로 쉽게 가져올 수 있는 비즈니스/연락처 정보를 전송하기 위한 표준화된 파일 형식입니다. 이제 이러한 VFC 파일을 [MMS를]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/create/) 통해 전송하고 Braze 미디어 라이브러리에 추가할 수 있습니다. 
+
+## 사용자 삭제에 대한 업데이트
+
+2020년 10월에는 데이터 주체의 전화번호 또는 이메일 주소 삭제 처리 방식을 [개선]({{site.baseurl}}/help/release_notes/2020/october/)했습니다. 
+
+## 새로운 Braze 파트너십
+
+### Airbridge - 기여도
+
+[에어브릿지와 Braze의 통합을]({{site.baseurl}}/partners/message_orchestration/attribution/airbridge/) 통해 모든 오가닉 및 비오가닉 설치 어트리뷰션 데이터를 Braze에 전달하여 보다 개인화된 마케팅 캠페인을 구축하고 사용자가 어디서 유입되었는지 정확히 파악할 수 있습니다.
+### Kubit - 분석
+
+[Kubit]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/kubit/)은 코드가 필요 없는 셀프 서비스 분석 플랫폼으로, 즉각적인 제품 인사이트를 제공합니다. Braze와의 원활한 코드 없는 통합을 통해 사용자 코호트 정보를 Braze로 가져와 특정 코호트를 타겟팅하는 참여 캠페인을 시작할 수 있습니다. 또한, Snowflake 보안 데이터 공유를 사용하면 Braze의 원시 캠페인 및 노출 횟수 데이터를 Kubit의 제품 분석과 통합하여 이러한 캠페인의 영향을 실시간으로 측정할 수 있습니다. 
+
+### Census - 고객 데이터 플랫폼
+
+[Census]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/census/)를 사용하면 엔지니어링 부서의 지속적인 도움 없이도 고객 데이터를 동기화하여 고객 성공, 영업, 마케팅 팀이 모두 동일한 정보를 공유할 수 있습니다.
+
+### 트레저데이터 - 고객 데이터 플랫폼
+
+[Treasure Data]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/treasure_data/)는 데이터, 인사이트, 인게이지먼트가 완벽하게 조화를 이루도록 함으로써 관련성 높은 고객 경험을 제공할 수 있도록 지원합니다. 실행 가능한 지표로 무장한 마케팅, 영업, 고객 서비스를 포함한 CX 팀은 전체 고객 여정에서 지출을 효과적으로 최적화하고 옴니채널 상호 작용을 개인화할 수 있습니다. 
+
+## 자카드 - A/B 테스트
+
+Braze 고객 참여는 멀티채널 마케팅을 통해 관계를 발전시킵니다. Braze는 [Jacquard와]({{site.baseurl}}/partners/data_and_infrastructure_agility/ab_testing/jacquard/) 협력하여 브랜드 보이스에 맞게 맞춤화된 브랜드 언어를 여러 채널에 대규모로 배포할 수 있습니다. Jacquard의 딥러닝 엔진은 테스트를 처리하고 결과를 모니터링하며 학습한 내용을 기반으로 새로운 언어를 생성합니다. 
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2021/august.md b/_lang/ko/_help/release_notes/2021/august.md
new file mode 100644
index 00000000000..28eafea2c2b
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/august.md
@@ -0,0 +1,65 @@
+---
+nav_title: 8월
+page_order: 4
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 8월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2021년 8월
+
+## Google 오디언스 동기화
+
+Braze [오디언스 싱크와 Google]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/) 통합을 통해 브랜드는 크로스채널 고객 여정의 도달 범위를 Google 검색, Google 쇼핑, 지메일, 유튜브, Google 디스플레이로 확장할 수 있습니다. 퍼스트파티 고객 데이터를 사용하면 동적 행동 트리거, 세분화 등을 기반으로 광고를 안전하게 전달할 수 있습니다. 일반적으로 메시지를 트리거하는 데 사용하는 모든 기준(예: 푸시, 이메일, SMS 등)을 Braze 캔버스의 일부로 사용하여 Google의 고객 일치를 통해 해당 사용자에게 광고를 트리거할 수 있습니다.
+
+## 모범 사례 iOS SDK 통합 가이드
+
+이 선택 사항 [iOS 통합 SDK 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overviewios_sdk_integration/)는 iOS SDK와 핵심 구성 요소를 애플리케이션에 처음 통합할 때 설정 모범 사례에 대한 단계별 여정을 안내합니다. 이 가이드는 나머지 프로덕션 코드에서 Braze iOS SDK에 대한 모든 종속성을 분리하는 `BrazeManager.swift` 도움말 파일을 빌드하여 전체 애플리케이션에서 하나의 `import AppboyUI` 도움말 파일을 생성하는 데 도움이 됩니다. 이 접근 방식은 과도한 SDK 가져오기로 인해 발생하는 문제를 제한하여 코드를 쉽게 추적, 디버그 및 변경할 수 있도록 합니다. 
+
+## 예측 기반 구매
+
+예측 구매는 마케터에게 구매 가능성을 기반으로 사용자를 식별하고 메시지를 전달할 수 있는 강력한 도구를 제공합니다. 구매 예측을 생성하면 Braze는 [그라데이션 부스트 의사 결정 트리를](https://en.wikipedia.org/wiki/Gradient_boosting) 사용하여 머신러닝 모델을 학습시켜 이전 구매 활동에서 학습하고 향후 구매 활동을 예측합니다. 자세한 내용은 [예측 구매]({{site.baseurl}}/user_guide/predictive_suite/predictive_purchases/) 문서를 참조하세요. 
+
+## 드래그 앤 드롭 편집기
+
+Braze Email을 사용하면 새로운 [드래그 앤 드롭 편집 환경을]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/) 사용하여 캠페인이나 캔버스에서 완전히 맞춤화된 개인 이메일 메시지를 만들 수 있습니다. 이제 사용자는 편집기 블록을 이메일로 드래그하여 보다 직관적으로 사용자 지정할 수 있습니다. 
+
+## 사용자 별칭 가져오기
+
+`external_id`가 없는 사용자를 타겟팅하려면 [사용자 별칭이 있는 사용자 목록을 가져올]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_import/#import-with-user-alias) 수 있습니다. 별칭은 대체 고유 사용자 식별자 역할을 합니다. 앱에 가입하거나 계정을 만들지 않은 익명 사용자를 대상으로 마케팅하려는 경우 유용할 수 있습니다. 
+
+## iOS 15 업그레이드 가이드
+
+이 [iOS 15 업그레이드 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/ios_15/)는 iOS 15(WWDC21)에 도입된 변경 사항과 Braze iOS SDK 통합에 필요한 업그레이드 단계를 간략하게 설명합니다.
+
+## Android 12 업그레이드 가이드
+
+이 [안드로이드 12 업그레이드 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_12/)에서는 Android 12(2021)에 도입된 관련 변경 사항과 Braze Android SDK 통합에 필요한 업그레이드 단계를 설명합니다.
+
+## A2P 10DLC
+
+A2P 10DLC는 미국에서 기업이 표준 10자리 긴 코드(10DLC) 전화번호를 통해 A2P(애플리케이션 대 개인) 유형의 메시징을 보낼 수 있는 시스템을 말합니다. 10자리 길이의 코드는 전통적으로 P2P(개인 간) 트래픽을 위해 설계되었기 때문에 제한된 처리량과 강화된 필터링으로 인해 비즈니스에 제약이 있었습니다. 이 서비스는 이러한 문제를 완화하여 전반적인 메시지 전달력을 개선하고 브랜드가 링크와 클릭 유도 문안을 포함한 메시지를 대규모로 전송할 수 있도록 지원하며 원치 않는 메시지로부터 소비자를 더욱 보호할 수 있습니다. 
+
+현재 미국 긴 코드를 보유하고 있거나 미국 고객에게 전송하기 위해 사용하는 모든 고객은 10DLC에 긴 코드를 등록해야 합니다. 10DLC의 세부 사항과 필요한 이유에 대해 자세히 알아보려면 [10DLC]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/10dlc/) 전용 [문서를]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/10dlc/) 참조하세요.
+
+## 2단계 인증 초기화
+
+2단계 인증을 통해 로그인하는 데 문제가 있는 사용자는 회사 관리자에게 연락하여 [2단계 인증을 재설정할]({{site.baseurl}}/user_guide/administrative/app_settings/company_settings/security_settings/#user-authetication-reset) 수 있습니다.
+
+## 새로운 Braze 파트너십
+
+### Hightouch - 워크플로 자동화
+
+Braze와 [하이터치]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/hightouch/) 통합을 통해 데이터 웨어하우스의 최신 고객 데이터로 Braze에서 더 나은 캠페인을 구축할 수 있습니다. 고객에게 관련성 있고 시의적절한 상호작용을 제공하려면 정확하고 최신의 Braze 계정 데이터에 크게 의존해야 합니다. 데이터 웨어하우스의 고객 데이터를 Braze에 자동으로 동기화하면 더 이상 데이터 일관성에 대해 걱정할 필요가 없으며, 세계 최고 수준의 고객 경험을 구축하는 데 집중할 수 있습니다.
+
+### Transcend - 데이터 프라이버시 및 규정 준수
+
+Braze와 [Transcend]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_privacy/transcend/)는 파트너십을 통해 사용자는 수십 개의 데이터 시스템에서 데이터를 조율하여 개인정보 보호 요청을 자동화할 수 있습니다. 궁극적으로 이는 팀이 GDPR 및 CCPA와 같은 규정을 준수하고 개인이 자신의 데이터에 대해 주도권을 가질 수 있도록 도와줍니다.
+
+### Tinyclues - 코호트 가져오기
+
+고객 경험을 해치지 않으면서 캠페인 수와 수익을 늘릴 수 있는 잠재고객 구축 기능과 온라인과 오프라인에서 CRM 캠페인의 성과를 추적할 수 있는 분석 기능을 제공하는 [Tinyclues입니다]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/tinyclues/). Braze와 Tinyclues의 통합은 사용자에게 더 나은 CRM 계획 및 전략의 길을 열어주며, 사용자 친화적인 UI를 통해 더 많은 타겟팅 캠페인을 보내고, 새로운 제품 기회를 찾고, 매출을 확대할 수 있도록 지원합니다.
+
+### optilyz - 다이렉트 메일
+
+[optilyz]({{site.baseurl}}/partners/message_orchestration/additional_channels/direct_mail/optilyz/)는 보다 고객 중심적이고 지속 가능하며 수익성 있는 다이렉트 메일 캠페인을 운영할 수 있는 다이렉트 메일 자동화 플랫폼으로, 유럽 전역의 수백 개 기업이 사용하고 있으며 편지, 엽서, 셀프 메일러를 크로스채널 마케팅에 통합하고 캠페인을 자동화하고 개인화할 수 있도록 지원합니다. optilyz와 Braze 웹훅 통합을 사용하여 고객에게 다이렉트 메일을 보낼 수 있습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2021/december.md b/_lang/ko/_help/release_notes/2021/december.md
new file mode 100644
index 00000000000..42a19d753c7
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/december.md
@@ -0,0 +1,60 @@
+---
+nav_title: 12월
+page_order: 0
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 12월의 릴리스 노트가 포함되어 있습니다."
+alias: "/help/release_notes/2022/january/"
+---
+# 2021년 12월
+
+## 세그먼트 엔드포인트별로 사용자를 내보내도록 업데이트
+
+2021년 12월부터 [세그먼트 엔드포인트별 내보내기 사용자]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/)에 대해 다음과 같은 변경 사항이 적용됩니다.
+
+1. 이 API 요청의 `fields_to_export` 필드는 필수입니다. 모든 필드를 기본값으로 설정하는 옵션이 제거됩니다.
+2. `custom_events`, `purchases`, `campaigns_received`, `canvases_received`의 필드에는 지난 90일 동안의 데이터만 포함됩니다.
+
+## 커런츠 메시지 참여 이벤트의 새로운 속성
+
+일부 [메시지 참여 이벤트에]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) 대한 새로운 속성이 추가되었습니다. 이 업데이트는 다음 커런츠 메시지 인게이지먼트 이벤트와 이를 사용하는 모든 파트너에 적용됩니다.
+
+- `LINK_ID`, `LINK_ALIAS`를 다음에 추가:
+  - 이메일 클릭(모든 대상)
+- `USER_AGENT`를 다음에 추가:
+  - 이메일 열람
+  - 이메일 클릭
+  - 이메일 스팸으로 표시
+- `MACHINE_OPEN`을 다음에 추가:
+  - 이메일 열람
+
+## 새로운 리퀴드 개인화 태그
+
+이제 기기에서 포그라운드 푸시를 사용하도록 설정한 사용자를 다음 Liquid 태그를 사용하여 타겟팅할 수 있습니다.
+
+{% raw %}
+- `{{most_recently_used_device.${foreground_push_enabled}}}`
+- `{{targeted_device.${foreground_push_enabled}}}`
+{% endraw %}
+
+자세한 내용은 [지원되는 개인화 태그]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/)를 참조하세요.
+
+## 웹훅 정보
+
+웹훅은 강력하고 유연한 도구이지만 다소 혼란스러울 수 있습니다. 웹훅이 무엇이고 Braze에서 웹훅을 어떻게 사용할 수 있는지 궁금하다면 [웹훅]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/understanding_webhooks/)에 대한 새 글을 확인하세요.
+
+## Amazon Personalize
+
+Amazon Personalize는 나만의 아마존 머신 러닝 추천 시스템을 하루 종일 사용하는 것과 같습니다. 20년 이상의 추천 경험을 바탕으로 한 Amazon Personalize를 사용하면 실시간 개인화 상품 및 콘텐츠 추천과 타겟 마케팅 프로모션을 통해 고객 참여를 향상시킬 수 있습니다. 
+
+더 자세히 알아보려면 Amazon Personalize가 제공하는 사용 사례, 연동되는 데이터, 서비스 구성 방법, Braze와 통합하는 방법을 이해하는 새로운 [Amazon Personalize]({{site.baseurl}}/partners/message_personalization/dynamic_content/amazon_personalize/amazon_personalize/) 문서를 참조하세요.
+
+## 새로운 Braze 파트너십
+
+### Yotpo - 전자상거래
+
+[Yotpo와]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/yotpo/) Braze의 통합을 통해 이메일 및 기타 커뮤니케이션 채널 내에서 제품에 대한 별점, 인기 리뷰, 시각적 사용자 생성 콘텐츠를 동적으로 가져와서 표시할 수 있습니다. 또한 이메일 및 기타 커뮤니케이션 방법에 고객 수준 로열티 데이터를 포함시켜 보다 개인화된 상호 작용을 생성하여 매출과 로열티를 높일 수 있습니다.
+
+### Zeotap - 고객 데이터 플랫폼
+
+[Zeotap과]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/zeotap/) Braze의 통합을 통해 Zeotap 고객 세그먼트를 동기화하여 Zeotap 사용자 데이터를 Braze 사용자 계정에 매핑함으로써 캠페인의 규모와 도달 범위를 확장할 수 있습니다. 그런 다음 이 데이터를 기반으로 조치를 취하여 사용자에게 개인화된 타겟 경험을 제공할 수 있습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2021/february.md b/_lang/ko/_help/release_notes/2021/february.md
new file mode 100644
index 00000000000..749cfe28ecd
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/february.md
@@ -0,0 +1,17 @@
+---
+nav_title: 2월
+page_order: 10
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 2월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2021년 2월
+
+## 빠른 업데이트
+
+2021년 3월 22일부터 Braze 서비스에서는 업스트림 콘텐츠 전송 네트워크인 Fastly가 모든 TLS 트래픽을 SNI(서버 이름 표시)를 지원하도록 마이그레이션함에 따라 TLS 연결에 SNI(서버 이름 표시)가 필요합니다. 모든 최신 브라우저, 운영 체제 및 HTTPS 연결 프로토콜은 SNI를 지원합니다. SNI를 지원하지 않는 기기는 더 이상 Braze에 연결할 수 없습니다. 트래픽 추정치에 따르면 이는 최종 사용자 디바이스의 약 0.000001%에 해당합니다.
+
+## 오디언스 경로
+
+[캔버스 오디언스 경로]({{site.baseurl}}/audience_paths/)를 사용하면 전략적 우선순위 기반 사용자 그룹화를 통해 대규모로 사용자를 직관적으로 필터링하고 세분화할 수 있습니다. 이 새로운 캔버스 단계는 과도한 오디언스 기반 전체 단계를 만들 필요성을 대체하여 8개의 전체 단계였던 것을 하나로 통합할 수 있습니다! 이 새로운 단계를 도입하면 사용자 타겟팅을 단순화하는 동시에 캔버스를 불필요한 잡동사니와 복잡함으로부터 정리할 수 있습니다.
+
diff --git a/_lang/ko/_help/release_notes/2021/january.md b/_lang/ko/_help/release_notes/2021/january.md
new file mode 100644
index 00000000000..079c55bb01f
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/january.md
@@ -0,0 +1,33 @@
+---
+nav_title: 1월
+page_order: 11
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 1월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2021년 1월
+
+## 캔버스 보고서 빌더
+
+보고서 빌더를 사용하면 여러 캠페인 또는 캔버스의 결과를 단일 보기에서 비교할 수 있으므로 어떤 참여 전략이 주요 지표에 가장 큰 영향을 미쳤는지 쉽게 확인할 수 있습니다. [캔버스 보고서 빌더에]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/) 대해 자세히 알아보세요.
+
+## 인앱 메시지 iOS 구현 가이드
+
+이 상세 가이드에서는 서브클래싱을 활용하여 사용자 지정 슬라이드업 인앱 메시지, 사용자 지정 모달 인앱 메시지, 사용자 지정 전체 인앱 메시지를 만들어 Braze 캠페인과 캔버스에 추가하는 방법에 대해 설명합니다. 여기에는 필요한 코드 고려사항, Braze 팀이 구축한 자세한 사용 사례, 함께 제공되는 코드 스니펫이 포함되어 있습니다. 자세한 내용은 [여기에서]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/in-app_messaging/implementation_guide/) 설명서를 참조하세요. 
+
+## SMS 맞춤 키워드 카테고리 및 리타겟팅 옵션
+
+Braze는 양방향 메시징을 위한 사용자 지정 키워드 추가 기능, 사용자 지정 키워드 카테고리, 다국어 지원, 키워드 리타겟팅 및 필터링 옵션 등 기본 SMS 기능을 확장했습니다. SMS 키워드 처리에 대한 자세한 내용은 [SMS 설명서를]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/keyword_handling/) 참조하세요. 
+
+## Playable 파트너십 출시
+
+[Playable을]({{site.baseurl}}/partners/playable/) 통해 최고의 콘텐츠(고품질 동영상)를 최고의 대상(이메일)에게 전달할 수 있도록 Braze의 이메일 기능을 확장하세요. Playable 동영상 이메일을 사용하면 받은편지함 내에서 자동으로 재생되는 흥미로운 고품질 동영상 콘텐츠로 클릭률과 클릭 후 측정기준을 높일 수 있습니다. 
+
+## Zendesk 파트너십이 시작되었습니다.
+
+[Zendesk Support Suite(ZSS)]({{site.baseurl}}/partners/zendesk/)는 이메일, 온라인 채팅, 음성 앱 또는 소셜 메시징 앱에서 옴니채널 지원을 제공함으로써 고객과 자연스럽게 대화를 이어갈 수 있도록 하는 소프트웨어입니다. ZSS는 상호 작용을 추적하고 우선 순위를 지정하여 기업이 고객에 대한 통합된 기록 보기를 가질 수 있도록 함으로써 고객 지원을 중시합니다. 간소화된 티켓팅 시스템과 같은 강력한 도구를 통해 기업은 개인화된 접근 방식으로 고객에게 직접 다가갈 수 있습니다. Braze는 Zendesk와의 서버 간 통합을 제공하므로 Braze와 Zendesk 간에 지원 티켓 데이터를 동기화할 수 있는 Braze 웹훅을 활용할 수 있습니다. 
+
+## Crowdin 파트너십 출시
+
+[Crowdin]({{site.baseurl}}/partners/crowdin/)은 현지화 관리를 위한 클라우드 기반 소프트웨어입니다. Braze와 Crowdin의 통합으로 이메일 템플릿과 콘텐츠 블록을 번역할 수 있습니다. Braze 계정의 콘텐츠를 Crowdin 프로젝트에 동기화하고 번역을 다시 Braze에 추가할 수 있습니다.
+
diff --git a/_lang/ko/_help/release_notes/2021/july.md b/_lang/ko/_help/release_notes/2021/july.md
new file mode 100644
index 00000000000..5b6df272f24
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/july.md
@@ -0,0 +1,37 @@
+--- 
+nav_title: 7월
+page_order: 5
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 7월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2021년 7월
+
+## 간단한 설문조사 인앱 메시지
+
+[간단한 설문조사 인앱 메시지 템플릿을]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/) 사용하여 캠페인 전략에 도움이 되는 사용자 속성, 인사이트 및 선호도를 수집하세요. 예를 들어, 사용자에게 앱 사용 방법을 묻거나 개인 선호도에 대해 자세히 알아보거나 특정 기능에 대한 만족도를 물어볼 수 있습니다. 이 설문조사 템플릿은 모바일 앱과 웹 브라우저 모두에서 지원됩니다.
+
+## 리퀴드 사용 사례 라이브러리
+
+Liquid로 한 가지 일을 하는 방법이 궁금하신가요? 영감을 찾고 계신가요? 기념일, 생일부터 플랫폼 타겟팅 등 다양한 사용 사례 모음을 보려면 [Liquid 사용 사례 라이브러리]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases/)를 확인하세요.
+
+## 이메일 추적
+
+이제 사용자 프로필별로 오픈 픽셀 추적 및 클릭 추적을 비활성화할 수 있습니다. 이러한 유연성을 통해 고객은 개별 고객 프로필에서 더 이상 추적을 원하지 않는다고 표시할 수 있는 지역 개인정보 보호법을 준수할 수 있습니다. 자세한 내용은 [이메일 추적]({{site.baseurl}}/user_guide/data_and_analytics/tracking/email_tracking/) 도움말을 참조하세요.
+
+## SDK 데이터 수집 옵션
+
+Braze SDK를 통합하여 유연한 데이터 수집을 가능하게 하는 방법에 대한 자세한 내용은 [SDK 데이터 수집 옵션]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/sdk_data_collection/)에 대한 새 설명서에서 확인할 수 있습니다.
+
+## SSL 개요
+
+새로운 [SSL 개요]({{site.baseurl}}/user_guide/message_building_by_channel/email/email_setup/ssl/) 문서에서 Braze의 SSL에 대해 자세히 알아보고, SSL이 중요한 이유와 SSL 인증서를 획득하는 방법을 알아보세요.
+
+## 앰플리튜드 사용자 프로필 API 엔드포인트
+
+Amplitude의 고객 프로필 API는 Amplitude의 고객 프로필을 제공합니다. 여기에는 사용자 속성, 계산된 사용자 속성, 해당 사용자를 포함하는 코호트의 코호트 ID 목록 및 권장 사항이 포함됩니다. 자세한 내용은 [Amplitude 고객 프로필 API 엔드포인트]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_user_profile_api/)를 참조하세요.
+
+## 캠페인 세부 정보 엔드포인트 
+
+[`/campaigns/details` 엔드포인트에]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/) 인앱 메시지 채널을 위한 전용 `message` 응답이 추가되었습니다. 이에 대한 문서는 [여기에서]({{site.baseurl}}/api/endpoints/export/campaigns/get_campaign_details/#messages) 확인할 수 있습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2021/june.md b/_lang/ko/_help/release_notes/2021/june.md
new file mode 100644
index 00000000000..6cd937c4b3d
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/june.md
@@ -0,0 +1,44 @@
+--- 
+nav_title: 6월
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 6월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2021년 6월
+
+## 트랜잭션 이메일 캠페인
+
+거래 이메일은 발신자와 수신자 간에 합의된 거래를 진행하기 위해 전송되는 이메일입니다. Braze의 [거래 이메일 캠페인은]({{site.baseurl}}/api/api_campaigns/transactional_campaigns) 주문 확인, 비밀번호 재설정, 청구 알림 또는 기타 비즈니스에 중요한 알림과 같은 자동화된 비홍보성 이메일 메시지를 전송하기 위해 특별히 제작되었습니다. 또한 해당 [트랜잭션 이메일 엔드포인트가]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_transactional_message/) 생성되었습니다. 트랜잭션 이메일과 새로운 엔드포인트는 일부 Braze 패키지의 일부로만 사용할 수 있습니다. 
+
+## 이벤트 속성에 대한 중첩 개체 지원
+
+이제 Braze는 커스텀 이벤트와 구매 이벤트에 [중첩된 개체]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/nested_object_support/)를 지원합니다. 중첩된 개체를 사용하면 데이터 배열을 커스텀 이벤트 및 구매의 속성으로 전송할 수 있습니다. 이 중첩된 데이터는 Liquid 및 점 표기법을 사용하여 API 트리거 메시지에서 개인화된 정보를 템플릿화하는 데 사용할 수 있습니다.
+
+## 새로운 HMAC 액체 필터
+
+새로운 [`hmac_sha1` 및 `hmac_sha256` 리퀴드 인코딩 필터가]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/) Braze 플랫폼에 추가되었습니다.
+
+## 구매 이벤트 페이지
+
+Braze의 구매 이벤트에 대한 자세한 내용이 궁금하신가요? 자세한 내용은 전용 [구매 이벤트]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/) 게시글을 참조하세요.
+
+## 새로운 Braze 파트너십
+
+### Nexla - 워크플로 자동화
+
+[Nexla]({{site.baseurl}}/partners/nexla)는 통합 데이터 운영 분야의 리더이자 2021년 Gartner의 쿨 벤더로 선정된 기업입니다. 커런츠를 사용하여 데이터 웨어하우스로 데이터를 전송하는 고객은 Nexla를 활용하여 해당 데이터를 추출, 변환, 다른 위치로 로드할 수 있으므로 전체 에코시스템에서 데이터에 쉽게 액세스할 수 있습니다. Nexla를 사용하면 Braze 커런츠에서 간단한 포인트 앤 클릭만으로 원하는 목적지로 커스텀 형식의 데이터를 전송할 수 있습니다. 
+
+### Amperity - 고객 데이터 플랫폼
+
+[Amperity는]({{site.baseurl}}/partners/amperity/) 종합적인 기업 고객 데이터 플랫폼으로, 브랜드가 고객을 파악하고 전략적 결정을 내리며 소비자에게 더 나은 서비스를 제공하기 위한 올바른 조치를 일관되게 취할 수 있도록 지원합니다. Amperity는 CDP와 Braze에 걸쳐 고객에 대한 통합 보기를 제공하여 귀사의 중요한 Amperity 데이터를 Braze로 전송할 수 있도록 함으로써 Braze 플랫폼을 지원합니다.
+
+### Digioh - 설문조사
+
+[Digioh]({{site.baseurl}}/partners/digioh/)를 사용하면 목록을 늘리고, 퍼스트파티 데이터를 수집하고, 데이터를 Braze 캠페인에 활용할 수 있습니다. 드래그 앤 드롭 빌더를 사용하면 브랜드 양식, 팝업, 환경 설정 센터, 랜딩 페이지 및 설문조사를 쉽게 생성하여 고객과 소통할 수 있습니다.
+
+### AppsFlyer 오디언스 - 기여도/분석
+
+[AppsFlyer]({{site.baseurl}}/partners/message_orchestration/attribution/appsflyer/)는 마케팅 분석 모바일 기여도와 딥링킹을 통해 앱을 분석하고 최적화할 수 있도록 도와주는 모바일 마케팅 분석 및 기여도 플랫폼입니다. [AppsFlyer 오디언스]({{site.baseurl}}/partners/appsflyer_audiences/)를 사용하면 오디언스 세그먼트를 생성하고 이러한 세그먼트를 Braze에 직접 전달하여 강력한 고객 참여 캠페인을 만들 수 있습니다.
+
diff --git a/_lang/ko/_help/release_notes/2021/march.md b/_lang/ko/_help/release_notes/2021/march.md
new file mode 100644
index 00000000000..1e620500925
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/march.md
@@ -0,0 +1,20 @@
+---
+nav_title: 3월
+page_order: 9
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 3월 릴리스 노트가 포함되어 있습니다."
+---
+# 2021년 3월
+
+## 세그먼트 확장
+
+[세그먼트 확장]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension)은(는) 기존 세분화 기능을 확장하여 사용자가 지난 365일 동안의 커스텀 이벤트 및 구매 행동을 기반으로 더 정밀한 사용자 목록을 타겟팅할 수 있도록 합니다. 이 확장 목록이 생성되면 세그먼트에서 필터로 포함/제외할 수 있습니다. 세그먼트 확장을 만들 때 목록이 24시간마다 한 번씩 재생성되도록 지정할 수도 있습니다.
+
+## A2P 10DLC
+
+A2P 10DLC는 미국에서 기업이 표준 10자리 긴 코드(10DLC) 전화번호를 통해 A2P(애플리케이션 대 개인) 유형의 메시징을 보낼 수 있는 시스템을 말합니다. 10자리 긴 코드는 전통적으로 개인 간(P2P) 트래픽을 위해 설계되어 기업이 제한된 처리량과 강화된 필터링에 의해 제약을 받게 됩니다. 현재 긴 코드를 보유하거나 사용하는 모든 고객은 10DLC에 긴 코드를 등록해야 합니다. [A2P 10DLC]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_setup/short_and_long_codes/#application-to-person-10-digit-long-codes-a2p-10dlc) 기사에서 자세히 알아보세요.
+
+## 글로벌 컨트롤 그룹
+
+[글로벌 컨트롤 그룹]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/)을 통해 시간 경과에 따른 메시징 노력의 전반적인 영향을 분석할 수 있습니다. 이 그룹들은 메시징을 받는 사용자와 받지 않는 사용자의 행동을 비교하여 마케팅 캠페인과 캔버스가 세션 및 커스텀 이벤트에서 어떻게 상승을 가져오는지 이해하는 데 도움을 줄 수 있습니다. 
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2021/may.md b/_lang/ko/_help/release_notes/2021/may.md
new file mode 100644
index 00000000000..9d3c200ffbd
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/may.md
@@ -0,0 +1,36 @@
+---
+nav_title: 5월
+page_order: 7
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 5월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2021년 5월
+
+## 전환 상관관계
+
+이 가이드에서는 캠페인 **분석** 페이지의 [전환 상관관계]({{site.baseurl}}/user_guide/engagement_tools/testing/conversion_correlation/) 분석에 대해 설명하며, 이를 통해 어떤 사용자 속성과 행동이 캠페인에 대해 설정한 결과에 도움이 되거나 해가 되는지에 대한 인사이트를 얻을 수 있습니다. 분석의 개요, 확인 대상, 사용 가능한 시기, Braze가 유의성을 확인하는 방법에 대해 설명합니다.
+
+## 글로벌 제어 그룹 보고서
+
+시간 경과에 따른 메시징 활동의 전반적인 영향을 더 잘 분석할 수 있도록 [글로벌 관리 그룹]({{site.baseurl}}/user_guide/engagement_tools/testing/global_control_group/) 보고서의 메트릭을 업데이트했습니다. 주요 변경 사항으로는 **사용자당 이벤트** 및 **예상 그룹 규모를** 추가하고, 치료 그룹과 대조군 간의 총 이벤트 차이를 반영하도록 **증분 상승률** 계산을 조정하는 것이 있습니다.
+
+## 보고서 개요
+
+캠페인 또는 캔버스 분석을 어디서부터 시작해야 할지 모르시겠어요? [보고서 개요]({{site.baseurl}}/user_guide/data_and_analytics/reporting/reports_overview/)에서는 일반적인 마케팅 전략 질문에 답하는 데 사용할 수 있는 보고서 및 분석에 대한 지침을 제공합니다.
+
+## 새로운 US-05 클러스터
+
+Braze는 새로운 미국 클러스터인 US-05를 지원합니다. 자세한 내용은 대시보드 및 REST [엔드포인트]({{site.baseurl}}/api/basics/#endpoints) 목록을 참조하세요.
+
+## Braze UI 업데이트
+
+2021년 5월, Braze 대시보드에서 다음과 같은 라벨과 용어가 업데이트되었습니다.
+
+- 앱 사용 --> 개요
+- 앱 설정 --> 설정
+- 앱 그룹 관리 --> 설정 관리
+- 앱 내에서 지출한 금액 --> 지출 금액
+- 앱 사용(사용자 프로필) --> 세션 개요
+- 이 앱 그룹에 사용자를 추가 또는 업데이트하려면 사용자 정보의 CSV를 가져옵니다 --> 사용자 정보의 CSV를 가져와 사용자를 추가 또는 업데이트하기
diff --git a/_lang/ko/_help/release_notes/2021/november.md b/_lang/ko/_help/release_notes/2021/november.md
new file mode 100644
index 00000000000..6cf95609103
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/november.md
@@ -0,0 +1,50 @@
+---
+nav_title: 11월
+page_order: 1
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 11월의 릴리스 노트가 포함되어 있습니다."
+---
+# 2021년 11월
+
+## 클릭 투 오픈 비율 보고 지표
+Braze는 [보고서 작성기에서]({{site.baseurl}}/user_guide/data_and_analytics/reporting/report_builder/) 사용할 수 있는 새로운 이메일 지표인 클릭 후 열기 비율을 추가했습니다. 이 메트릭은 클릭된 열린 이메일의 비율을 나타냅니다.
+
+## 머신 오픈 보고 메트릭
+
+새로운 이메일 지표인 [머신 오픈]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/analytics_glossary/#machine-opens)은 이메일에 대한 캔버스 및 캠페인 분석 페이지에서 사용할 수 있습니다. 이 메트릭은 사람이 아닌 사람이 열어본 이메일(예: Apple 서버에서 열어본 이메일)을 식별하며, 전체 열어본 이메일의 하위 집합으로 표시됩니다.
+
+## random_bucket_number Liquid 변수
+메시지 개인화를 위해 [지원되는 Liquid 변수]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags/#supported-personalization-tags) 목록에 `random_bucket_number` 변수가 추가되었습니다. 
+
+## iOS 15 리치 푸시 알림 가이드라인
+iOS 리치 문서에 알림 상태 및 텍스트 잘림 변수에 대한 분석 정보를 포함한 새로운 [iOS 푸시 알림 가이드라인]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/rich_notifications/)이 추가되었습니다.
+
+## 웹훅 및 커넥티드 콘텐츠에 대해 EU에서 화이트리스트에 등록할 IP
+[웹훅]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/) 및 커넥티드 콘텐츠 문서에 EU에서 웹훅 및 [커넥티드 콘텐츠에]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/making_an_api_call/) 대해 화이트리스트에 추가할 IP가 추가되었습니다. 이러한 새로운 IP에는 `18.157.135.97`, `3.123.166.46`, `3.64.27.36`, `3.65.88.25`, `3.68.144.188`, `3.70.107.88`이 포함됩니다.
+
+## 구매 엔드포인트 내보내기
+Braze에 새로운 [`/purchases/product_list` 엔드포인트]({{site.baseurl}}/api/endpoints/export/purchases/get_list_product_id/)가 추가되었습니다. 이 엔드포인트는 제품 ID의 페이지가 매겨진 목록을 반환합니다.
+
+## 새로운 Braze 파트너십
+
+### Adobe - 고객 데이터 플랫폼
+Braze와 [Adobe]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/adobe/#adobe)의 통합을 통해 브랜드는 Adobe 데이터(커스텀 속성 및 세그먼트)를 실시간으로 Braze에 연결하고 매핑할 수 있습니다. 그런 다음 브랜드는 이 데이터를 기반으로 조치를 취하여 해당 사용자에게 개인화된 타겟팅 경험을 제공할 수 있습니다. 
+
+### BlueConic - 고객 데이터 플랫폼
+Braze 사용자는 [Blueconic]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/blueconic/#blueconic)을 통해 데이터를 영구적인 개별 프로필로 통합한 다음 고객 생애주기 오케스트레이션, 모델링 및 분석, 디지털 제품 및 경험, 오디언스 기반 수익화 등 광범위한 성장 중심 이니셔티브를 지원하기 위해 고객 터치포인트와 시스템 전반에서 이를 동기화할 수 있습니다.
+
+### Worthy - 동적 콘텐츠
+Braze와 [Worthy]({{site.baseurl}}/partners/message_personalization/dynamic_content/worthy/#worthy)의 통합을 통해 Worthy의 드래그 앤 드롭 동적 콘텐츠 에디터를 사용하여 개인화된 풍부한 인앱 경험을 손쉽게 제작하고 Braze를 통해 전달할 수 있습니다.
+
+### 유도 - 동적 콘텐츠
+[Judo]({{site.baseurl}}/partners/message_personalization/dynamic_content/judo/#judo) 및 Braze 통합을 통해 캠페인의 구성 요소를 덮어쓰고 유도 경험으로 대체할 수 있습니다. Braze의 데이터는 Judo 경험에서 개인화된 콘텐츠를 지원하기 위해 사용될 수 있습니다. 사용자 이벤트와 경험에서 얻은 데이터는 기여도 및 타겟팅을 위해 Braze에 피드백될 수 있습니다.
+
+### Line - 메시징
+[Line]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/line/#line)과 Braze 통합을 통해 Braze 웹훅, 고급 세분화, 개인화 및 트리거 기능을 활용하여 [Line 메시징 API](https://developers.line.biz/en/docs/messaging-api/overview/)를 통해 라인에서 사용자에게 메시지를 보낼 수 있습니다.
+
+### RevenueCat - 결제
+[RevenueCat과]({{site.baseurl}}/partners/data_and_infrastructure_agility/payments/revenuecat/#revenuecat) Braze의 통합을 통해 고객의 구매 및 구독 생애주기 이벤트를 여러 플랫폼에서 자동으로 동기화할 수 있습니다. 이를 통해 무료 평가판 사용 중 옵트아웃한 고객과 소통하거나 청구 문제가 있는 고객에게 알림을 보내는 등 고객의 구독 라이프사이클 단계에 따라 반응하는 캠페인을 구축할 수 있습니다.
+
+### Punchh - 로열티
+[Punchh]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/punchh/#punchh)는 선물 및 로열티 목적으로 Braze와 제휴하여 두 플랫폼에서 데이터를 동기화했습니다. Braze에 게시된 데이터는 세분화에 사용할 수 있으며, Braze에서 설정한 웹훅 템플릿을 통해 사용자 데이터를 다시 Punchh로 동기화할 수 있습니다.  
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2021/october.md b/_lang/ko/_help/release_notes/2021/october.md
new file mode 100644
index 00000000000..db7e87d6c9c
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/october.md
@@ -0,0 +1,49 @@
+---
+nav_title: 10월
+page_order: 2
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 10월의 릴리스 노트가 포함되어 있습니다."
+---
+ 
+# 2021년 10월
+
+## 데이터 포인트 사용량 대시보드
+
+**총 데이터 포인트 사용량** 대시보드를 사용하여 계약 할당량과 관련된 데이터 포인트 사용 속도를 추적하세요. 이 대시보드는 계약, 현재 청구 주기, 회사 청구 데이터 및 워크스페이스 청구 데이터에 대한 정보를 제공합니다. 자세한 내용은 [청구서]({{site.baseurl}}/user_guide/onboarding_with_braze/subscription_and_usage/#total-data-points-dashboard)를 참조하세요.
+
+## 세그먼트 확장 재생성으로 변경
+
+2022년 2월 1일부터는 사용하지 않는 [세그먼트 확장]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/)에 대해 매일 확장을 재생성하는 설정이 자동으로 해제됩니다. Braze는 다음 기준을 충족하는 확장을 사용되지 않은 확장으로 정의합니다.
+
+- 활성 캠페인, 캔버스 또는 세그먼트에 사용되지 않음
+- 비활성(임시저장본, 중지되었거나 아카이브된 상태) 캠페인, 캔버스 또는 세그먼트에 사용되지 않음
+- 7일이 넘도록 수정되지 않음
+
+Braze는 이 설정이 꺼지면 회사 연락처와 생성자에게 확장을 알립니다. 매일 확장 프로그램을 재생성하는 옵션은 언제든지 다시 설정할 수 있습니다.
+
+## Android 고급 구현 가이드
+
+### 콘텐츠 카드
+
+이 선택 사항인 고급 [구현 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/implementation_guide/)에서는 콘텐츠 카드 코드 고려사항, 유니티 팀이 구축한 세 가지 맞춤 사용 사례, 함께 제공되는 코드 스니펫, 노출 횟수, 클릭 수 및 해제 로깅에 대한 지침을 다룹니다.
+
+### 인앱 메시징
+
+이 선택적 고급 [구현 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/implementation_guide/)는 인앱 메시지 코드 고려사항, 저희 팀이 구축한 세 가지 사용자 지정 사용 사례 및 함께 제공되는 코드 스니펫을 다룹니다.
+
+### 푸시 알림
+
+이 선택 사항인 고급 [구현 가이드에서는]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/implementation_guide/) 사용자 지정 `FirebaseMessagingService` 하위 클래스를 활용하여 푸시 메시지를 최대한 활용하는 방법에 대해 설명합니다. 저희 팀이 구축한 커스텀 사용 사례와 함께 제공되는 코드 스니펫, 로깅 분석에 대한 안내가 포함되어 있습니다.
+
+## 새로운 Braze 파트너십
+
+### Adobe - 고객 데이터 플랫폼
+
+Adobe Experience Platform을 기반으로 구축된 Adobe의 실시간 고객 데이터 플랫폼(실시간 CDP)은 기업이 여러 기업 소스의 알려진 데이터와 익명 데이터를 통합하여 모든 채널과 디바이스에서 개인화된 고객 경험을 실시간으로 제공하는 데 사용할 수 있는 고객 프로필을 생성할 수 있도록 지원합니다.
+
+Braze와 [Adobe]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/adobe/) CDP 통합을 통해 브랜드는 Adobe 데이터(사용자 지정 속성 및 세그먼트)를 실시간으로 Braze에 연결하고 매핑할 수 있습니다. 그런 다음 브랜드는 이 데이터를 기반으로 조치를 취하여 해당 사용자에게 개인화된 타겟팅 경험을 제공할 수 있습니다. 
+
+### Shopify - 전자상거래
+
+[Shopify는]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/) 모든 규모의 소매 비즈니스를 시작, 성장, 마케팅 및 관리할 수 있는 신뢰할 수 있는 도구를 제공하는 선도적인 글로벌 상거래 기업입니다. Braze와 Shopify 통합을 통해 브랜드는 Shopify 스토어를 Braze와 원활하게 연결하여 일부 Shopify 웹훅을 Braze로 전달할 수 있습니다. Braze의 크로스채널 전략과 캔버스를 활용하여 결제 중단 메시징으로 사용자를 리타겟팅하고 고객이 구매를 완료하도록 넛지하거나 이전 구매를 기반으로 사용자를 리타겟팅할 수 있습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2021/september.md b/_lang/ko/_help/release_notes/2021/september.md
new file mode 100644
index 00000000000..10f876f96bd
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2021/september.md
@@ -0,0 +1,39 @@
+---
+nav_title: 9월
+page_order: 3
+noindex: true
+page_type: update
+description: "이 문서에는 2021년 9월의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2021년 9월
+
+## iOS 15
+
+### Apple MPP 
+
+Apple의 MPP(메일 개인정보 보호)는 9월 중순에 출시되는 iOS 15, iPadOS 15, macOS 몬터레이 및 watchOS 8의 Apple Mail 앱 사용자가 사용할 수 있는 개인정보 보호 업데이트입니다. MPP에 옵트인한 사용자의 경우 이제 이메일이 프록시 서버를 사용하여 미리 로드되어 이미지를 캐싱하고 [열람 추적]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#open-tracking-pixel)과 같은 측정기준에 추적 픽셀을 활용하는 기능을 방해하게 됩니다. 이메일 전달 가능성 측정기준과 관련된 MPP 및 문제, 이러한 측정기준을 기반으로 트리거되는 기존 캠페인 및 캔버스와 관련된 문제에 대해 자세히 알아보려면 [설명서]({{site.baseurl}}/user_guide/message_building_by_channel/email/mpp/)를 참조하세요.
+
+### 푸시 기능
+
+iOS 15에는 사용자가 하루 종일 집중하고 자주 방해받지 않도록 도와주는 새로운 알림 기능이 도입되었습니다. [중단 수준 및 관련성 점수]({{site.baseurl}}/user_guide/message_building_by_channel/push/ios/notification_options/)를 포함한 새로운 기능을 지원하게 되어 매우 기쁩니다.
+
+## 연락처 카드
+
+연락처 카드는 비즈니스 및 연락처 정보를 전송하기 위한 표준화된 파일 형식으로 주소록이나 연락처 목록으로 쉽게 가져올 수 있습니다. 이제 SMS 및 MMS 메시지에 대한 연락처 카드를 업로드하고 만들 수 있습니다. 기본 제공 연락처 카드 생성기에서 연락처 카드를 만드는 방법에 대해 자세히 알아보려면 [설명서]({{site.baseurl}}/user_guide/message_building_by_channel/sms/mms/contact_card/)를 참조하세요.
+
+## 기본 콘텐츠 카드 사용자 지정
+
+`ABKContentCardsTableViewController`를 확장하여 모든 UI 요소와 콘텐츠 카드 동작을 커스텀하여 나만의 콘텐츠 카드 인터페이스를 만들 수 있습니다. 콘텐츠 카드 피드를 커스텀하는 방법에 대한 자세한 내용은 [설명서]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/customization/customizing_feed/)를 참조하세요. 
+
+## API 사용량 제한
+
+[사용량 제한]({{site.baseurl}}/api/basics/#api-limits/)은 2021년 9월 16일 이후에 가입한 모든 고객에게 적용됩니다. 
+
+## Android 및 FireOS 개발자 가이드 업데이트
+
+Android 및 FireOS 개발자 가이드가 한 곳으로 통합되었습니다. FireOS 전용 문서는 이 [새로운 Android 섹션]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/fireos/integration/)에서 확인할 수 있습니다.
+
+## 퍼널 및 리텐션 보고서 업데이트
+
+이제 SMS 캠페인에 [퍼널 보고서]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_funnel_reports/) 와 [리텐션 보고서를]({{site.baseurl}}/user_guide/engagement_tools/campaigns/testing_and_more/retention_reports/) 사용할 수 있습니다.
diff --git a/_lang/ko/_help/release_notes/2022.md b/_lang/ko/_help/release_notes/2022.md
new file mode 100644
index 00000000000..30219a6e26c
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022.md
@@ -0,0 +1,52 @@
+---
+page_order: 2
+nav_title: 2022
+layout: dev_guide
+noindex: true
+guide_top_header: "2022 릴리스 노트"
+
+page_type: landing
+description: "이 섹션은 2022년 릴리스 노트가 있는 곳입니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 2022년 1월 11일
+    link: /docs/help/release_notes/2022/1_11_22/
+    image: /assets/img/braze_icons/snowflake-01.svg
+  - name: 2022년 2월 8일
+    link: /docs/help/release_notes/2022/2_8_22/
+    image: /assets/img/braze_icons/hearts.svg 
+  - name: 2022년 3월 8일
+    link: /docs/help/release_notes/2022/3_8_22/
+    image: /assets/img/braze_icons/trophy-01.svg
+  - name: 2022년 4월 5일
+    link: /docs/help/release_notes/2022/4_5_22/
+    image: /assets/img/braze_icons/droplets-01.svg 
+  - name: 2022년 5월 3일
+    link: /docs/help/release_notes/2022/5_3_22/
+    image: /assets/img/braze_icons/sun.svg 
+  - name: 2022년 5월 31일
+    link: /docs/help/release_notes/2022/5_31_22/
+    image: /assets/img/braze_icons/sun.svg
+  - name: 2022년 6월 28일
+    link: /docs/help/release_notes/2022/6_28_22/
+    image: /assets/img/braze_icons/umbrella-03.svg
+  - name: 2022년 7월 26일
+    link: /docs/help/release_notes/2022/7_26_22/
+    image: /assets/img/braze_icons/flag-01.svg
+  - name: 2022년 8월 23일
+    link: /docs/help/release_notes/2022/8_23_22/
+    image: /assets/img/braze_icons/wind-02.svg
+  - name: 2022년 9월 20일
+    link: /docs/help/release_notes/2022/9_20_22/
+    image: /assets/img/braze_icons/backpack.svg
+  - name: 2022년 10월 18일
+    link: /docs/help/release_notes/2022/10_18_22/
+    image: /assets/img/braze_icons/magic-wand-02.svg 
+  - name: 2022년 11월 15일
+    link: /docs/help/release_notes/2022/11_15_22/
+    image: /assets/img/braze_icons/cloud-sun-02.svg
+  - name: 2022년 12월 13일
+    link: /docs/help/release_notes/2022/12_13_22/
+    image: /assets/img/braze_icons/gift-01.svg
+---
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2022/10_18_22.md b/_lang/ko/_help/release_notes/2022/10_18_22.md
new file mode 100644
index 00000000000..7855a4bc7eb
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/10_18_22.md
@@ -0,0 +1,57 @@
+---
+nav_title: 2022년 10월 18일
+page_order: 1
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 10월 18일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2022년 10월 18일 출시
+
+## 고객 프로필 메시징 기록
+
+고객 프로필의 **메시지 기록** 탭은 지난 30일 동안 개별 사용자의 최근 메시징 관련 이벤트(약 40개)를 보여줍니다. 이러한 이벤트에는 사용자가 보낸, 받은, 상호작용한 메시지 등이 포함됩니다. [사용자 프로필]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/#messaging-history-tab)을 참조하여 자세히 알아보세요. 
+
+## 드래그 앤 드롭 편집기를 위한 콘텐츠 블록
+
+드래그 앤 드롭 편집기에서 독점적으로 사용되는 [콘텐츠 블록]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/)은(는) 다양한 채널에서 사용되는 콘텐츠 블록과 기능적으로 유사합니다. 다양한 이메일 캠페인에서 참조할 수 있는 정보를 보관하는 중앙 집중식 위치입니다. 이것은 이메일 헤더, 프로모션 호출 등을 하나의 재사용 가능한 행으로 그룹화하는 것을 포함할 수 있습니다.
+
+## Shopify ScriptTag
+
+[Braze와 Shopify 통합]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify)을 통해 이제 ScriptTag를 사용하여 Shopify 스토어에 우리의 Web SDK 통합을 삽입할 수 있습니다. ScriptTag를 통해 Braze의 웹 SDK를 임베딩하면 다음을 추적할 수 있습니다.
+- 익명 사용자 추적을 통해 매장에서 손님 활동을 추적합니다
+- 월간 활성 사용자 추적은 웹 SDK가 스토어 방문자로부터 세션 데이터를 추적할 수 있기 때문입니다.
+- Shopify 온사이트 활동 사용자를 수집하는 옵션으로 데이터 포인트 소비에 포함됩니다
+- Shopify 스토어에서 채널로 브라우저 내 메시징을 활성화하는 옵션
+
+## SCIM 엔드포인트
+
+다음 Braze SCIM 엔드포인트를 사용하여 자동 사용자 프로비저닝을 관리하십시오:
+- [삭제: 대시보드 사용자 계정 제거]({{site.baseurl}}/api/endpoints/scim/delete_existing_dashboard_user/)
+- [가져오기: 기존 대시보드 사용자 계정]({{site.baseurl}}/api/endpoints/scim/get_see_user_account_information/) 조회
+- [게시: 새 대시보드 사용자 계정 만들기]({{site.baseurl}}/api/endpoints/scim/post_create_user_account/)
+- [넣기: 대시보드 사용자 계정]({{site.baseurl}}/api/endpoints/scim/put_update_existing_user_account/) 업데이트
+
+## SMS 퍼지 옵트아웃
+
+[퍼지 옵트아웃]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out#fuzzy-opt-out)은 수신 SMS 메시지가 옵트아웃 키워드와 일치하지 않지만, 옵트아웃 의도를 나타낼 때 이를 인식하려고 시도합니다. 퍼지 옵트아웃이 활성화되어 있고 수신 키워드 응답이 "퍼지"로 간주되는 경우, Braze는 사용자의 의도를 확인하도록 자동으로 응답합니다.
+
+## SDK 업데이트
+
+다음 소프트웨어 개발 키트 업데이트가 출시되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Android SDK 23.2.0-23.2.1](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2321)
+- [iOS Objective-C SDK 4.5.1](https://github.com/Appboy/appboy-ios-sdk/blob/master/CHANGELOG.md#451)
+- [iOS Swift SDK 5.5.0S-SDK 5.5.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#550)
+- [Cordova SDK 2.31.0](https://github.com/Appboy/appboy-cordova-sdk/blob/master/CHANGELOG.md#2310)
+  - [Braze Android 소프트웨어 개발 키트 23.0.1](https://github.com/braze-inc/braze-android-sdk/releases/tag/v23.0.1)로 업데이트되었습니다.
+- [Unity 3.10.0](https://github.com/Appboy/appboy-unity-sdk/blob/master/CHANGELOG.md#3100)
+- [React SDK v1.39.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#1400)
+  - 네이티브 Android SDK를 23.2.0으로 업데이트했습니다.
+  - `kotlin_versio`그레이들 템플릿 변수의 이름을 `kotlinVersion`으로 이름을 변경했습니다
+- [Flutter SDK 2.6.0](https://pub.dev/packages/braze_plugin/changelog#260)
+  - 네이티브 Android 브리지는 Braze Android SDK 23.2.0을 사용합니다.
+  - 네이티브 iOS 브리지는 Braze iOS SDK 4.5.1을 사용합니다.
+  - `process(inAppMessage)`는 iOS 계층에서 `processInAppMessage(inAppMessage)`(으)로 이름이 변경되었습니다.
+- [세그먼트 iOS 4.6.0](https://github.com/Appboy/appboy-segment-ios/blob/master/CHANGELOG.md#460)
+  - Braze [iOS SDK 4.5.1+](https://github.com/Appboy/appboy-ios-sdk/blob/master/CHANGELOG.md#451)로 업데이트되었습니다.
diff --git a/_lang/ko/_help/release_notes/2022/11_15_22.md b/_lang/ko/_help/release_notes/2022/11_15_22.md
new file mode 100644
index 00000000000..e9af04c8f8c
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/11_15_22.md
@@ -0,0 +1,52 @@
+---
+nav_title: 2022년 11월 15일
+page_order: 0.5
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 11월 15일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2022년 11월 15일 출시
+
+## 새로운 드래그 앤 드롭 편집기 인앱 메시지용
+
+새로운 [드래그 앤 드롭 편집기]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop)를 사용하면 HTML을 알 필요 없이 완전히 커스텀되고 개인화된 인앱 메시지를 만들 수 있습니다. 드래그 앤 드롭 편집기는 향후 몇 달 동안 모든 고객에게 출시될 예정입니다. 접근을 더 빨리 요청하고 싶다면, 고객 성공 매니저에게 연락하세요.
+
+## 이메일을 위한 드래그 앤 드롭 편집기 업데이트
+
+### 새 편집기 블록
+
+이메일을 위한 드래그 앤 드롭 편집기에 두 개의 새로운 편집기 블록이 추가되었습니다: [문단 블록]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks/#paragraph) 및 [목록 블록]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks/#list).
+
+{% alert important %}
+기존 텍스트 블록은 사용 중단될 예정이지만, 텍스트 블록이 포함된 기존 이메일은 계속 지원됩니다.
+{% endalert %}
+
+### 다크 모드 미리보기
+
+드래그 앤 드롭 편집기에서 [이메일을 미리 보고 테스트할 때]({{site.baseurl}}/user_guide/message_building_by_channel/email/html_editor/creating_an_email_campaign/#step-3b-preview-and-test-your-message), 이제 **다크 모드 미리보기**를 켜서 다크 모드 사용자가 이메일을 어떻게 보는지 확인할 수 있습니다.
+
+## 승리의 길 얼리 액세스
+
+캔버스의 실험 경로의 일부로 제공되는 [위닝 경로]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/#step-2-turn-on-winning-path-optional)는 A/B 테스트를 자동화할 수 있습니다. 승리 경로가 켜지면 지정된 기간 후에 모든 후속 사용자는 가장 높은 전환율을 가진 경로로 보내집니다.
+
+이 기능은 현재 초기 액세스 중입니다. 미리 맛보기에 참여하고 싶다면 고객 성공 매니저에게 문의하세요.
+
+## tvOS에서 인앱 메시지 및 콘텐츠 카드
+
+이 새로운 기사는 tvOS에서 [인앱 메시지 및 콘텐츠 카드]({{site.baseurl}}/developer_guide/platform_integration_guides/tvos/in-app_messaging)를 통합하는 미묘한 차이를 다루며, 이는 Braze Swift SDK를 통해 사용할 수 있습니다.
+
+## 새로운 Liquid 사용 사례
+
+우리는 메시지에서 고객의 구독 상태를 사용하여 콘텐츠를 개인화하는 방법에 대한 새로운 사용 사례를 [Liquid 사용 사례 라이브러리]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases#misc-personalize-content)에 추가했습니다. 이 사용 사례에서는 특정 구독 그룹에 가입한 고객이 이메일 및 SMS 구독 그룹 모두에 대한 독점 메시지를 받게 됩니다.
+
+## SDK 업데이트
+
+다음 소프트웨어 개발 키트 업데이트가 출시되었습니다. 이 릴리스에는 중요한 업데이트가 없습니다. 다른 모든 업데이트는 해당 SDK 체인지로그를 확인하여 찾을 수 있습니다.
+
+- [Android SDK 23.3.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2330)
+- [웹 SDK 4.4.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#440)
+- [Unity SDK 3.11.0](https://github.com/Appboy/appboy-unity-sdk/blob/master/CHANGELOG.md#3110)
+- [Xamarin SDK 1.26.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md#1260)
+- [iOS Swift SDK 5.6.0–5.6.2](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#562)
+- [Flutter SDK 2.6.1](https://pub.dev/packages/braze_plugin/changelog#261)
diff --git a/_lang/ko/_help/release_notes/2022/12_13_22.md b/_lang/ko/_help/release_notes/2022/12_13_22.md
new file mode 100644
index 00000000000..4530a248628
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/12_13_22.md
@@ -0,0 +1,98 @@
+---
+nav_title: 2022년 12월 13일
+page_order: 0
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 12월 13일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2022년 12월 13일 출시
+
+## 뉴스피드가 더 이상 사용되지 않습니다.
+뉴스피드는 사용 중지될 예정입니다. Braze는 뉴스피드 도구를 사용하는 고객에게 보다 유연하고 맞춤 설정이 가능하며 안정적인 콘텐츠 카드 메시징 채널로 전환할 것을 권장합니다. 자세한 내용은 [마이그레이션 가이드를]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/migrating_from_news_feed/) 확인하세요.
+
+## 새로운 API 엔드포인트: 카탈로그
+[Braze API 카탈로그 엔드포인트를]({{site.baseurl}}/api/endpoints/catalogs) 사용하여 [카탈로그]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs) 및 카탈로그 항목 세부 정보를 추가, 편집, 관리하세요. 비동기 카탈로그 엔드포인트를 사용하여 카탈로그를 대량으로 변경할 수 있습니다.
+
+## 이메일용 드래그 앤 드롭 편집기의 링크에 대한 HTML 속성
+이제 이메일용 드래그 앤 드롭 편집기에서 `Image`, `Button` 또는 `Text` 편집기 블록 내의 모든 URL에 [HTML 속성을 추가]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/#creative-details/)할 수 있습니다. 사용자 지정 속성을 사용하면 이메일의 HTML 태그에 추가 정보를 쉽게 추가할 수 있습니다. 이는 메시지 개인화, 세분화 및 스타일링에 특히 유용할 수 있습니다. 
+
+## 히트맵 표시 토글
+이제 [히트맵 표시 토글]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/email_reporting#heatmaps)을 사용하여 이메일 캠페인 기간 동안의 전체 클릭 빈도와 위치를 보여주는 **메시지 분석**의 시각적 보기를 불러올 수 있습니다. 나중에 참조할 수 있도록 히트맵 사본을 다운로드할 수도 있습니다.
+
+## 이메일 설정 업데이트
+이전의 **일반 이메일 설정** 섹션이 두 개의 새로운 섹션으로 분리되었습니다: **구성** 및 **구독 페이지 및 바닥글**보내기. 개별 설정에 대한 자세한 내용은 [이메일 설정에서]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#sending-configuration) 확인하세요.
+
+## 미디어 라이브러리를 위한 AI 이미지 생성
+자연어 설명으로 사실적인 이미지와 아트를 생성할 수 있는 OpenAI의 AI 시스템인 DALL-E 2를 사용하여 미디어 라이브러리에 사용할 이미지를 생성할 수 있습니다. [AI를 사용하여 이미지 생성하기]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/media_library/#generate-ai)에 대해 자세히 알아보세요.
+
+## 중첩된 사용자 지정 속성에 대한 개선 사항
+중첩된 사용자 지정 속성을 사용하여 객체를 사용자 지정 속성에 대한 새 데이터 유형으로 보낼 수 있습니다. 
+- [중첩된 커스텀 속성 개체가 변경될 때 트리거]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/#trigger-nested-custom-attribute-changes)할 수 있습니다.
+- 이제 [커스텀 속성 개체와 Liquid를 사용하여 메시지를 개인화]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/#personalization)할 수도 있습니다.
+
+## 새로운 비디오 블록
+이메일용 드래그 앤 드롭 편집기에 새로운 [동영상용]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_editor_blocks/#video) 콘텐츠 블록이 추가되었습니다.
+
+## 벤더 수집을 위한 선택적 식별자 - Swift
+이전 버전의 Braze iOS Swift SDK에서는 IDFV(공급업체 식별자) 필드가 사용자의 기기 ID로 자동 수집되었습니다. Swift SDK v5.7.0부터는 IDFV 필드를 선택적으로 비활성화할 수 있으며, 대신 Braze에서 임의의 UUID를 기기 ID로 설정합니다. 자세한 내용은 [IDFV 수집을]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/analytics/swift_idfv/) 참조하세요.
+
+## Snowflake 리더 계정
+Snowflake 리더 계정은 Snowflake 계정이나 Snowflake와의 고객 관계 없이도 Snowflake [데이터 공유]({{site.baseurl}}/partners/snowflake/)와 동일한 데이터 및 기능에 액세스할 수 있도록 해줍니다. 리더 계정을 사용하면 Braze에서 데이터를 생성하여 계정으로 공유하고 로그인하여 데이터에 액세스할 수 있는 자격 증명을 제공합니다. 이렇게 하면 모든 데이터 공유 및 사용량 청구는 Braze가 전적으로 처리하게 됩니다. 
+
+자세히 알아보려면 고객 성공 매니저에게 문의하세요.
+
+## 업데이트된 Shopify 통합
+이제 [Shopify 통합을]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/) 통해 Shopify 스토어에서 이메일 및 SMS 옵트인을 수집하여 Braze의 가입 그룹에 할당할 수 있습니다.
+
+
+## 새로운 Braze 파트너십
+
+### Ada - 설문조사
+[Ada와]({{site.baseurl}}/partners/message_orchestration/channel_extensions/surveys/ada/) Braze의 통합을 통해 자동화된 Ada 대화에서 수집한 데이터로 사용자 프로필을 보강할 수 있습니다. Ada 채팅 중에 수집한 정보를 기반으로 커스텀 사용자 속성을 설정하고 Ada 대화의 지정된 지점에서 Braze에 커스텀 이벤트를 기록할 수 있습니다. Ada 챗봇을 Braze에 연결하면 소비자가 브랜드에 대해 어떤 질문을 하는지를 기반으로 소비자에 대해 더 많이 알 수 있으며, 선제적으로 대화를 시작하여 소비자의 관심사와 선호도에 대해 더 많이 알 수 있는 질문을 할 수도 있습니다.
+
+### B.Layer \- 메시지 템플릿
+그리고 [B.Layer]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/blayer) 와 Braze의 통합을 통해 B.Layer 인앱 메시지 빌더를 활용하면 브랜드 내 인앱 메시지를 작성하여 zip 파일 또는 인라인 HTML로 내보내 Braze로 전송할 수 있습니다. 이 통합에는 추가적인 개발자 리소스가 필요하지 않으므로 시간과 예산을 절약할 수 있습니다.
+
+### Contentsquare - 분석
+[Contentsquare]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/contentsquare/)와 Braze의 통합을 통해 실시간 신호(사기, 좌절 신호 등)를 Braze에서 커스텀 이벤트로 전송할 수 있습니다. Contentsquare의 경험 인사이트를 활용하여 고객의 디지털 경험과 바디랭귀지를 기반으로 메시지를 타겟팅하여 캠페인의 관련성과 전환율을 향상시킬 수 있습니다.
+
+### 동적 수익률 - 동적 콘텐츠
+[동적 수익률과]({{site.baseurl}}/partners/message_personalization/dynamic_content/dynamic_yield/) Braze의 파트너십을 통해 동적 수익률의 추천 및 세분화 엔진을 활용하여 Braze 메시지에 삽입할 수 있는 경험 블록을 만들 수 있습니다. 경험 블록은 다음으로 만들 수 있습니다.
+- **권장 사항 블록**: 알고리즘과 필터링을 설정하여 이메일이 열릴 때 전파되는 사용자의 개인화된 콘텐츠를 소싱하세요. 
+- **동적 콘텐츠 블록**: 다양한 사용자에게 다양한 프로모션과 메시지를 타겟팅하세요. 타겟팅은 친밀도 또는 오디언스를 기반으로 할 수 있습니다. 동적 수익률은 이메일이 열렸을 때 제공할 개인화된 경험을 결정합니다. 
+
+### Octolis - 분석
+[Octolis]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/contentsquare/)와 Braze의 통합은 원시 데이터 소스와 Braze 사이의 미들웨어 역할을 하여 온라인과 오프라인의 다양한 소스에서 데이터를 검색하고 통합할 수 있게 해줍니다.
+
+### 자카드 - AB 테스트
+Jacquard X가 제공하는 [Jacquard React]({{site.baseurl}}/partners/data_and_infrastructure_agility/ab_testing/jacquard/jacquard_react/)는 Braze 커런츠와 연결된 콘텐츠를 활용하여 웹훅을 통해 구독자로부터 클릭 추적 기술 정보를 수집합니다. 그런 다음 Jacquard는 이러한 이벤트를 언어 배리언트에 다시 연결하여 실시간 언어 최적화를 수행합니다.
+
+### Sheetlabs - 동적 콘텐츠
+[Sheetlabs]({{site.baseurl}}/partners/message_personalization/dynamic_content/sheetlabs/)와 Braze 통합을 통해 [연결된 콘텐츠]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/connected_content/about_connected_content/)를 활용하여 Braze 마케팅 캠페인에 Sheetlabs API를 포함할 수 있습니다. 이는 일반적으로 마케팅 팀에서 직접 업데이트하는 Google 스프레드시트와 Braze의 템플릿을 연결하는 데 사용됩니다. 이를 통해 번역이나 대규모 사용자 지정 속성 세트와 같은 Braze 템플릿으로 더 많은 것을 달성할 수 있습니다.
+
+### Tellius - 분석
+[Tellius]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/tellius/)와 Braze의 통합을 통해 사용자는 BI 엔지니어에 의존하지 않고도 데이터를 활용하여 대시보드를 구축하고 더 나은 마케팅 의사 결정을 내릴 수 있는 인사이트를 생성할 수 있습니다.
+
+### ThoughtSpot - 분석
+[ThoughtSpot과]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/thoughtspot/) Braze의 통합은 미리 빌드된 워크시트와 모델 템플릿으로 사용자 행동 분석을 가속화할 수 있는 ThoughtSpot TML 블록을 활용하여 Braze 사용자가 사용자 행동 분석을 가속화할 수 있도록 합니다. 이 통합을 통해 사용자는 Braze 상호작용 데이터 전반을 무제한으로 검색하고 유용한 인사이트를 발견할 수 있습니다. 
+
+### Wunderkind - 분석
+[Wunderkind]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/wunderkind/)와 Braze의 통합을 통해 성능 향상을 분석하고 더 많은 익명 사용자를 식별할 수 있으며, Braze를 통해 전송되는 일대일 메시지와 Braze에 직접 추가된 연락처를 크게 확장할 수 있습니다.
+
+
+## SDK 업데이트
+다음 SDK 업데이트가 릴리스되었습니다. 주요 변경 사항은 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [iOS Swift SDK 5.6.3-5.7.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+- [Flutter SDK 3.0.0](https://pub.dev/packages/braze_plugin/changelog)
+    - 네이티브 iOS 브릿지는 이제 [새로운 Braze Swift SDK 버전 5.6.4](https://github.com/braze-inc/braze-swift-sdk)를 사용하며, 최소 iOS 배포 대상은 10.0입니다.
+    - 마이그레이션하는 동안 다음 변경 사항으로 프로젝트를 업데이트하세요:
+        - Braze를 초기화하려면 [다음 통합 단계에 따라 구성 개체를 생성하세요](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/a2-configure-braze). 그런 다음 이 코드를 추가하여 설정을 완료합니다: `let braze = BrazePlugin.initBraze(configuration)`
+        - `SDWebImage`를 종속성으로 계속 사용하려면 프로젝트의 `/ios/Podfile`인 `pod 'SDWebImage', :modular_headers => true`에 이 줄을 추가하세요. 그런 다음 다음 [설정 지침을](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/c3-gif-support) 따르세요.
+        - 인앱 메시지 및 콘텐츠 카드 데이터 수신과 같은 기타 변경 사항에 대한 지침은 [`AppDelegate.swift`](https://github.com/braze-inc/braze-flutter-sdk/blob/master/example/ios/Runner/AppDelegate.swift) 샘플을 참고하세요.
+- [React Native SDK v1.41.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+- [웹 SDK 4.5.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+
+### 새로운 SDK 라이브러리: 세그먼트 Kotlin SDK 
+세그먼트는 세그먼트 코틀린이라는 새로운 코틀린 우선 접근 방식으로 라이브러리를 업데이트했습니다. Braze는 이 새로운 라이브러리 패러다임에 맞춰 새로운 라이브러리를 출시했습니다. [GitHub에서 초기 릴리스](https://github.com/braze-inc/braze-segment-kotlin)를 확인하세요.
diff --git a/_lang/ko/_help/release_notes/2022/1_11_22.md b/_lang/ko/_help/release_notes/2022/1_11_22.md
new file mode 100644
index 00000000000..a5b4ffa3dbe
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/1_11_22.md
@@ -0,0 +1,34 @@
+---
+nav_title: 2022년 1월 11일
+page_order: 11
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 1월 11일 릴리스 노트가 포함되어 있습니다."
+alias: "/help/release_notes/2022/february/"
+---
+# 2022년 1월 11일 출시
+
+새해에 오신 것을 환영합니다!
+
+## 캔버스 실험 경로 단계
+새로운 캔버스 실험 경로 단계는 사용자 여정의 어느 지점에서든 여러 캔버스 경로를 서로 및 대조군과 비교하여 경로 성능을 추적하는 데 도움이 됩니다. 이제 여기서 수집된 분석을 활용하여 어떤 경로가 가장 효과적인지 추가로 결정할 수 있습니다. [실험 경로 단계]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/)를 만드는 방법에 대해 자세히 알아보세요.
+
+## 유효하지 않은 전화번호 처리
+사용자가 유효하지 않은 전화번호를 입력한 시나리오를 만났습니다. 여기 솔루션이 있습니다! Braze는 이러한 유효하지 않은 전화번호를 표시하고 해당 번호로 추가 통신을 시도하지 않습니다. Braze가 [유효하지 않은 전화번호를 처리하는 방법]({{site.baseurl}}/user_guide/message_building_by_channel/sms/phone_numbers/user_phone_numbers/#handling-invalid-phone-numbers/)에 대해 자세히 알아보세요.
+
+## 새로운 SMS 엔드포인트
+이제 새로운 [Braze SMS 엔드포인트]({{site.baseurl}}/api/endpoints/sms/)를 사용하여 잘못된 전화번호를 관리할 수 있습니다! 이번 업데이트의 특징:
+- [가져오기: 유효하지 않은 전화번호 엔드포인트]({{site.baseurl}}/api/endpoints/sms/get_query_invalid_numbers/)는 Braze에서 "유효하지 않음"으로 간주되는 전화번호 목록을 반환합니다.
+- [게시: 잘못된 전화번호 엔드포인트]({{site.baseurl}}/api/endpoints/sms/post_remove_invalid_numbers/)를 사용하면 Braze의 잘못된 목록에서 "잘못된" 전화번호를 제거할 수 있습니다.
+
+## 요금 한도
+모든 [Braze 엔드포인트 기사]({{site.baseurl}}/api/basics/#nav_top_endpoints)에 대해 API 사용량 제한이 포함되었습니다. 이제 요청 유형별로 사용량 제한을 쉽게 확인할 수 있습니다. 사용량 제한에 대한 자세한 내용은 [API 사용량 제한]({{site.baseurl}}/api/api_limits/)에 대한 기사를 확인하세요.
+
+## 새로운 REST 엔드포인트
+Braze는 [새로운 EU-02 REST 엔드포인트]({{site.baseurl}}/api/basics/#api-definitions)를 추가했습니다.
+
+## 이메일 소개
+이메일 messages are a great way to connect with your customers. 이메일 메시지를 사용자 정의하고 활용하는 방법에 대한 빠른 소개는 [이메일에 대하여]({{site.baseurl}}/user_guide/message_building_by_channel/email/about/)에 대한 새 기사를 확인하십시오. 
+
+## 인앱 메시지 소개
+인앱 메시지는 앱 내에서 활동하는 사용자에게 서식 있는 콘텐츠를 제공합니다. 인앱 메시지를 만들어 개인화된 인사말이나 기능 채택을 통해 활발한 고객과 쉽게 소통할 수 있습니다. 장점과 메시지 유형에 대해 알아보려면 [인앱 메시지 소개]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/about/) 신규 기사를 확인하세요.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2022/2_8_22.md b/_lang/ko/_help/release_notes/2022/2_8_22.md
new file mode 100644
index 00000000000..1f12eb7b20e
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/2_8_22.md
@@ -0,0 +1,27 @@
+---
+nav_title: 2022년 2월 8일
+page_order: 10
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 2월 8일에 대한 릴리스 노트가 포함되어 있습니다."
+alias: "/help/release_notes/2022/march/"
+---
+# 2022년 2월 8일 출시
+
+## 캔버스 작업 경로
+
+[작업 경로]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/action_paths/)를 사용하면 사용자의 작업에 따라 사용자를 정렬할 수 있습니다. 작업 경로로 가능한 작업:
+- 특정 작업을 기반으로 사용자 경로를 사용자 지정합니다. 
+- 이 평가 기간 동안 사용자의 행동에 따라 다음 경로의 우선순위를 정하기 위해 주어진 기간 동안 사용자를 보류합니다. 
+
+액션 경로에 대한 액세스는 모든 Braze 인스턴스에 천천히 적용될 예정입니다. 자세한 내용은 Braze 계정 관리자에게 문의하세요.
+
+## API 엔드포인트 참조 페이지
+
+사용 가능한 모든 Braze 엔드포인트에 대한 빠른 참조 페이지를 찾고 계신가요? [API 엔드포인트 색인을]({{site.baseurl}}/api/endpoints/) 방문하세요.
+
+## Transifex v2 및 v2.5 API 사용 중단
+[트랜시펙스는]({{site.baseurl}}/partners/message_personalization/localization/transifex/#transifex) 2022년 4월 7일부터 API 버전 2와 2.5를 더 이상 지원하지 않고 버전 3으로 전환할 예정입니다. 이 날짜 이후에는 v2 및 v2.5가 더 이상 작동하지 않으며 관련 요청이 실패합니다. 이 파트너 통합의 사용자는 이 날짜 이전에 API 버전을 업데이트하시기 바랍니다.
+
+## 사용 가능한 사용자 지정 속성 데이터 유형
+곧 출시됩니다! 커스텀 속성에 대한 오브젝트 및 오브젝트 배열 데이터 유형 지원은 2022년 봄에 제공될 예정입니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2022/3_8_22.md b/_lang/ko/_help/release_notes/2022/3_8_22.md
new file mode 100644
index 00000000000..23a2af0a049
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/3_8_22.md
@@ -0,0 +1,70 @@
+---
+nav_title: 2022년 3월 8일
+page_order: 9
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 3월 8일에 대한 릴리스 노트가 포함되어 있습니다."
+alias: "/help/release_notes/2022/april/"
+---
+
+# 2022년 3월 8일 출시
+
+## Roku용 인앱 메시지
+
+이제 Braze는 Roku 기기에서 사용자에게 인앱 메시지 전송을 지원합니다! 이 기능은 추가 SDK 구성이 필요하며 즉시 사용할 수 없습니다. Roku용 인앱 메시지 통합에 대한 자세한 내용은 [Roku 인앱 메시지]({{site.baseurl}}/developer_guide/platform_integration_guides/roku/in-app_messaging/overview/)를 참조하세요.
+
+## 이탈 예측 및 구매 예측을 위한 전체 필터 모드
+
+새로운 예측을 즉시 구축하기 위해 기본적으로 Braze 세분화 필터의 하위 집합만 지원됩니다. 이제 전체 필터 모드를 활성화하여 모든 세분화 필터를 사용할 수 있지만, 이 모드에서는 예측을 작성할 때 하나의 창으로 제한됩니다. 자세한 내용은 다음 문서를 참조하세요:
+
+- [고객이탈 예측 생성]({{site.baseurl}}/user_guide/predictive_suite/predictive_churn/creating_a_churn_prediction/#full-filter-mode)
+- [구매 예측 생성]({{site.baseurl}}/user_guide/predictive_suite/predictive_purchases/creating_a_purchase_prediction/#full-filter-mode)
+
+## 키워드 응답을 위한 리타겟팅 옵션
+
+이제 SMS 캠페인에 대한 분석을 볼 때 특정 키워드 카테고리로 응답한 사용자를 기반으로 리타겟팅할 세그먼트를 편리하게 생성할 수 있습니다. 자세한 내용은 SMS 보고의 [키워드 응답]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_campaign_analytics/#keyword-responses)으 참조하세요.
+
+## 데이터 수집 모범 사례
+
+알려진 사용자와 알려지지 않은 사용자를 모두 처리할 때 사용자 데이터를 언제 어떻게 수집해야 하는지 궁금한 적이 있나요? Braze에서 사용자 프로필의 라이프사이클이 다소 혼란스러울 수 있다는 것을 알고 있으므로, 신규 및 기존 사용자 데이터를 수집하는 다양한 방법과 모범 사례를 명확히 하기 위해 몇 가지 [데이터 수집 모범 사례를]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/best_practices/) 정리해 보았습니다.
+
+## 트랜시펙스 API 사용 중단
+
+2022년 4월 7일부로 Transifex는 버전 3을 위해 API 버전 2와 2.5를 더 이상 지원하지 않습니다. 이 날짜 이후에는 v2 및 v2.5가 더 이상 작동하지 않으며 관련 요청이 실패합니다. Transifex API를 활용하는 경우, 그에 따라 연결된 콘텐츠 호출을 업데이트하세요. 자세한 내용은 [Transifex]({{site.baseurl}}/partners/message_personalization/localization/transifex/)를 참조하세요.
+
+## 새로운 Braze 파트너십
+
+### Toovio - 고객 데이터 플랫폼
+
+Braze와 [Toovio]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/toovio/)의 파트너십은 실시간에 가까운 메시지 트리거링, 성과 향상을 위한 도구, Toovio의 고급 캠페인 측정 도구에 대한 액세스를 제공합니다.
+
+### Snowplow - 분석
+
+Braze와 [Snowplow]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/snowplow/)의 통합을 통해 사용자는 Google Tag Manager 서버 측 태깅을 통해 Snowplow 이벤트를 Braze에 전달할 수 있습니다. Snowplow Braze 태그를 사용하면 추가적인 유연성과 제어 기능을 제공하면서 이벤트를 Braze로 보낼 수 있습니다.
+
+- 데이터의 모든 변환에 대한 완전한 가시성 확보
+- 시간이 지남에 따라 정교함을 발전시키는 능력
+- 모든 데이터는 전달을 선택할 때까지 개인 클라우드에 남아 있습니다.
+- 풍부한 태그 라이브러리와 친숙한 Google 태그 관리자 UI로 설정이 간편합니다.
+
+Snowplow의 풍부한 행동 데이터를 활용하여 Braze에서 강력한 고객 중심 상호작용을 유도하고 실시간으로 개인화된 메시지를 전달하세요.
+
+### Clarisights - 분석
+
+Braze와 [Clarisights]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/clarisights/)의 통합을 통해 Braze 캠페인과 캔버스에서 데이터를 가져와 성과 및 CRM/유지 마케팅의 통합된 보고 인터페이스를 구축할 수 있습니다.
+
+### Wyng - 동적 콘텐츠
+
+Braze와 [Wyng]({{site.baseurl}}/partners/message_personalization/dynamic_content/wyng/)의 통합을 통해 Wyng경험을 활용하여 Braze 캠페인과 캔버스에서 개인화된 경험을 제공할 수 있습니다. 또한 Wyng에는 고객 선호도 포털이 포함되어 있어 사용자가 브랜드와 공유하는 데이터와 선호도를 제어할 수 있습니다.
+
+### Grouparoo - 워크플로 자동화
+
+Braze와 [Grouparoo]({{site.baseurl}}/help/release_notes/deprecations/grouparoo)의 통합을 통해 웨어하우스에 저장된 데이터를 Braze로 전송하여 손쉽게 운영할 수 있습니다. 자동 동기화 일정을 설정하면 최신 정보로 고객 커뮤니케이션을 일관성 있게 강화할 수 있습니다.
+
+### Lexer - 고객 데이터 플랫폼
+
+Braze와 [Lexer]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/lexer/)의 통합을 통해 두 플랫폼에서 데이터를 동기화할 수 있습니다. Lexer 데이터를 사용하여 가치 있는 Braze 세그먼트를 생성하거나 기존 세그먼트를 Lexer로 가져와 인사이트를 확보하세요.
+
+### Knak - 이메일 오케스트레이션
+
+Braze와 [Knak]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/knak/)의 통합을 통해 며칠 또는 몇 주가 아닌 몇 분 또는 몇 시간 만에 완벽하게 반응하는 이메일을 작성하고 바로 사용할 수 있는 Braze 템플릿으로 내보낼 수 있습니다. Knak은 외부 에이전시나 수작업 코딩 없이도 Braze에서 관리하는 캠페인의 이메일 작성 수준을 높이고자 하는 마케터를 위해 만들어졌습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2022/4_5_22.md b/_lang/ko/_help/release_notes/2022/4_5_22.md
new file mode 100644
index 00000000000..029fc3fac93
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/4_5_22.md
@@ -0,0 +1,49 @@
+---
+nav_title: 2022년 4월 5일
+page_order: 8
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 4월 5일에 대한 릴리스 노트가 포함되어 있습니다."
+alias: "/help/release_notes/2022/may/"
+---
+
+# 2022년 4월 5일 출시
+
+## 캠페인 또는 캔버스 어트리뷰션으로 필터링
+이제 특정 SMS 캠페인이나 캔버스 단계, 키워드 카테고리 또는 태그에 댓글을 단 사용자를 필터링할 수 있습니다. 자세한 내용은 [SMS 리타겟팅][8]을 참조하세요.
+
+## 이메일 성능 대시보드
+[이메일 실적 대시보드를][1] 사용하면 선택한 날짜 범위의 캠페인과 캔버스 모두에서 전체 이메일 채널에 대한 종합적인 실적 지표를 확인할 수 있습니다.
+
+Braze에서 사용할 수 있는 애널리틱스 대시보드에 대한 자세한 내용은 [애널리틱스 대시보드][2] 섹션을 참조하세요.
+
+## 글로벌 스타일 설정
+
+드래그 앤 드롭 에디터의 [글로벌 스타일 설정을][3] 소개합니다! 이제 기본 테마를 추가하고 기본 텍스트 스타일을 설정하는 등 이메일 캠페인과 캔버스의 모양을 쉽게 개인화할 수 있습니다.
+
+## Braze-Braze 웹훅
+Braze to Braze 웹훅을 사용하면 웹훅을 사용하여 Braze REST API와 통신하여 API가 허용하는 모든 작업을 수행할 수 있습니다. 기본적으로 이것은 Braze에서 Braze로 통신하는 웹훅입니다. 자세한 내용은 [브레이즈 투 브레이즈 웹훅][4] 문서를 참조하세요.
+
+## 사용 중단
+
+### Windows SDK
+2022년 3월 24일부로 [Braze Windows SDK][6]는 더 이상 사용되지 않으며, Braze 대시보드에서 새로운 Windows 앱을 만들 수 없습니다. 
+
+### Baidu 푸시 통합
+2022년 3월 24일부터 [Braze Baidu 푸시 통합][7]은 더 이상 사용되지 않으며, Braze 대시보드에서 새로운 Baidu 앱을 생성할 수 없습니다. 
+
+## 새로운 Braze 파트너십
+
+### 전류용 테일륨
+
+Braze와 [Tealium][5]의 통합을 통해 두 시스템 간의 정보 흐름을 원활하게 제어할 수 있습니다. 이제 커런츠를 사용하면 데이터를 Tealium에 연결하여 전체 성장 스택에서 실행 가능한 데이터로 만들 수 있습니다.
+
+
+[1]: {{site.baseurl}}/user_guide/data_and_analytics/analytics/
+[2]: {{site.baseurl}}/user_guide/data_and_analytics/analytics/understanding_your_app_usage_data/
+[3]: {{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_email_style_settings/
+[4]: {{site.baseurl}}/user_guide/message_building_by_channel/webhooks/braze_to_braze_webhooks/
+[5]: {{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/tealium/tealium_for_currents/
+[6]: {{site.baseurl}}/developer_guide/platform_integration_guides/windows_universal/initial_sdk_setup/
+[7]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/integration/baidu_integration/
+[8]: {{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/retargeting/
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2022/5_31_22.md b/_lang/ko/_help/release_notes/2022/5_31_22.md
new file mode 100644
index 00000000000..410715f4279
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/5_31_22.md
@@ -0,0 +1,68 @@
+---
+nav_title:  2022년 5월 31일
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 5월 31일에 대한 릴리스 노트가 포함되어 있습니다."
+alias: "/help/release_notes/2022/july/"
+---
+
+# 2022년 5월 31일 출시
+
+## Inbox Vision
+
+Inbox Vision을 사용하면 드래그 앤 드롭 이메일 캠페인이 모든 이메일 클라이언트 및 모바일 플랫폼에서 정렬되어 있는지 전송 전에 확인할 수 있습니다. 자세히 알아보려면 [Inbox Vision]({{site.baseurl}}/user_guide/message_building_by_channel/email/inbox_vision/)을 확인하세요.
+
+## 업데이트된 HTML 엔진
+
+드래그 앤 드롭 편집기에서 HTML을 생성하는 기본 엔진이 최적화 및 업데이트되어 HTML 파일 압축 및 렌더링과 관련된 이점이 있습니다. 업데이트에 대한 자세한 내용은 [HTML 엔진 업데이트에서]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/overview/#updated-html-engine/) 확인하세요.
+
+## 업데이트된 키워드 카테고리별 리타겟팅
+
+필터링 및 리타겟팅에 사용할 임의의 키워드와 응답을 식별할 수 있도록 최대 25개의 고유한 SMS 키워드 카테고리를 생성할 수 있습니다. SMS 키워드 카테고리와 설정 방법에 대해 자세히 알아보려면 [SMS 리타겟팅을]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/retargeting/) 확인하세요. 
+
+## 이벤트 속성 세분화
+
+[이벤트 속성 세분화를]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/purchase_events/#event-property-segmentation/) 사용하면 발생한 사용자 지정 이벤트 및 해당 이벤트와 관련된 속성을 기반으로 사용자를 타겟팅할 수 있습니다. 이 기능은 구매 및 사용자 지정 이벤트를 세분화할 때 추가 필터링 옵션을 추가합니다.
+
+## Google에 오디언스 동기화
+
+Braze 오디언스 구글 동기화 구현 프로세스가 간소화되어 여러 Google Ads 계정에 대한 Braze 액세스 권한을 부여할 수 있습니다. 자세한 내용은 오디언스 [Google에 동기화하기]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/)를 참조하세요. 
+
+## 새로운 Braze 파트너십
+
+### Amperity - 고객 데이터 플랫폼
+
+Braze와 [Amperity]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/amperity/)의 통합은 두 플랫폼에서 고객에 대한 통합된 뷰를 제공합니다. 이 통합을 통해 Amperity 사용자 목록을 생성하여 사용자 목록을 동기화하여 Amperity 사용자 데이터를 Braze 고객 계정에 매핑할 수 있습니다. 
+
+### Dynamic 365 고객 인사이트 - 고객 데이터 플랫폼
+
+Braze와 [Dynamics 365 고객 인사이트]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/dynamics_365_customer_insights/) 통합을 통해 고객 세그먼트를 Braze로 내보내 캠페인이나 캔버스에서 사용할 수 있습니다.
+
+### Extole - 로열티
+
+Braze와 [Extole]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/extole/)의 통합을 통해 Extole 친구 추천 및 성장 프로그램의 고객 이벤트 및 속성을 Braze로 가져와서 고객 확보, 인게이지먼트, 로열티를 높이는 보다 개인화된 마케팅 캠페인을 만들 수 있습니다. 또한 개인화된 공유 코드 및 링크와 같은 Extole 콘텐츠 속성을 Braze 커뮤니케이션으로 동적으로 가져올 수도 있습니다.
+
+### Heap - 코호트 가져오기
+
+Braze와 [Heap]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/heap/)의 통합을 통해 Heap 데이터를 Braze로 가져오고, 사용자 코호트를 생성할 수 있을 뿐만 아니라, Braze 데이터를 Heap으로 내보내 세그먼트를 생성할 수도 있습니다.
+
+### Hightouch - 워크플로 자동화
+
+Braze와 [Hightough]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/hightouch/)의 통합을 통해 사용자 코호트를 Braze로 가져와서 웨어하우스에만 존재할 수 있는 데이터를 기반으로 타겟팅 캠페인을 보낼 수 있습니다.
+
+### 피크 - 동적 콘텐츠
+
+Braze와 [Peak]({{site.baseurl}}/partners/message_personalization/dynamic_content/peak/)의 통합을 통해 고객 행동 및 상호 작용을 기반으로 예측된 고객이탈 확률과 속성을 가져와서 고객 세분화 및 타겟팅에 사용할 수 있도록 Braze로 가져올 수 있습니다. 
+
+### Shopify - 전자상거래
+
+Braze와 [Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/) 통합이 확장되어 결제 지연 포기, 기본 제품 식별자 설정, `shopify_paid_order`, `shopify_partially_fulfilled_order`, `shopify_fulfilled_order`, `shopify_cancelled_order`, `shopify_created_refund` 등 여러 가지 새로운 Shopify 이벤트가 제공됩니다. 
+
+### Survicate - 설문조사
+
+Braze와 [Survicate의]({{site.baseurl}}/partners/message_orchestration/channel_extensions/surveys/survicate/) 통합을 통해 이메일에 설문조사 링크를 포함하거나 설문조사 스니펫을 직접 삽입하여 응답률을 높일 수 있습니다. 설문조사가 완료되면 Survicate로 돌아와 설문조사 응답자의 속성과 응답을 식별하고 분석합니다.
+
+### Viralsweep - 로열티
+
+Braze와 [ViralSweep]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/viralsweep/)의 통합을 통해 ViralSweep 플랫폼에서 경품 행사와 콘테스트를 개최하고(이메일 및 SMS 목록을 늘리고), 캠페인이나 캔버스에서 사용할 경품이나 콘테스트 참가 정보를 Braze로 전송할 수 있습니다. 
diff --git a/_lang/ko/_help/release_notes/2022/5_3_22.md b/_lang/ko/_help/release_notes/2022/5_3_22.md
new file mode 100644
index 00000000000..661924f5f5d
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/5_3_22.md
@@ -0,0 +1,46 @@
+---
+nav_title: 2022년 5월 3일
+page_order: 7
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 5월 3일의 릴리스 노트가 포함되어 있습니다."
+alias: "/help/release_notes/2022/june/"
+---
+
+# 2022년 5월 3일 출시
+
+## 캠페인 승인
+
+캠페인 승인은 캠페인을 시작하기 전에 워크플로에 검토 프로세스를 추가합니다. 이제 캠페인을 시작하기 위해 각 확인이 승인되었는지 확인할 수 있습니다. 승인 절차에 대해 자세히 알아보려면 [캠페인 승인에서]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/campaign_approval/) 확인하세요.
+
+## 캔버스 메시지 단계
+
+메시지 단계를 사용하면 캔버스 흐름에서 원하는 위치에 독립형 메시지를 추가할 수 있습니다. 자세한 내용은 [메시지 단계]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/) 도움말을 참조하세요.
+
+## AI 카피라이팅 어시스턴트
+
+Braze [AI 카피라이팅 어시스턴트]({{site.baseurl}}/user_guide/intelligence/ai_copywriting#ai-copywriting-assistant)는 간단한 제품명이나 설명을 OpenAI의 GPT3 카피 생성 도구에 전달하여 메시징에 사용할 사람과 유사한 마케팅 카피를 생성합니다. 이 기능은 대부분의 메시지 작성기가 Braze 대시보드에서 기본적으로 사용할 수 있습니다.
+
+## iOS 푸시 알림 단위 테스트 가이드
+
+[푸시 알림에 대한 iOS 단위 테스트 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/push_notifications/unit_tests#unit-tests)가 개발자 가이드에 추가되었습니다. 이 가이드에서는 앱 위임이 올바르게 설정되었는지 확인할 수 있는 단위 테스트를 제공합니다. 
+
+## Google 개인정보 보호 설문지
+
+2022년 4월부터 Android 개발자는 Google Play의 \[데이터 안전 양식][4]을 작성하여 개인정보 보호 및 보안 관행을 공개해야 합니다. [이 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/android/google_play_privacy#google-play-privacy-questionnaire)는 Braze가 앱 데이터를 처리하는 방법에 대한 정보와 함께 이 새 양식을 작성하는 방법에 대한 지침을 제공합니다. 
+
+## RelayState SAML SSO
+
+초기 SSO 설정 지침이 `RelayState` API 키 사용을 권장하도록 업데이트되었습니다. 자세한 내용은 [SAML SSO 설정]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up/) 및 해당 [OneLogin]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/onelogin/), [Okta]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/okta/) 및 [Azure Active Directory]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/azure_ad/) 문서를 참조하세요. 
+
+## Talon.One 통합 업데이트
+
+저희 [Talon.One]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/talonone#talonone) 파트너십 문서에 업데이트된 통합 단계, 엔드포인트 및 예시가 추가되었습니다. Talon.One 파트너십을 활용하고 있다면 그에 따라 통합을 업데이트하는 것이 좋습니다.
+
+## Braze 웹 SDK V4 출시
+
+Braze SDK 팀이 웹 SDK v4를 출시했습니다. 주요 변경 사항, 업데이트 및 추가 사항 목록을 보려면 웹 SDK [체인지로그](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)에서 확인하세요. V3에서 V4로 업그레이드하는 사용자를 위한 [업그레이드 가이드가](https://github.com/braze-inc/braze-web-sdk/blob/master/UPGRADE_GUIDE.md) 작성되었습니다.
+
+## Grouparoo 사용 중단
+
+Grouparoo에 대한 지원은 2022년 4월부터 중단되었습니다.
diff --git a/_lang/ko/_help/release_notes/2022/6_28_22.md b/_lang/ko/_help/release_notes/2022/6_28_22.md
new file mode 100644
index 00000000000..555bd6d767a
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/6_28_22.md
@@ -0,0 +1,36 @@
+--- 
+nav_title: 2022년 6월 6일
+page_order: 5
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 6월 22일 릴리스 노트가 포함되어 있습니다."
+alias: "/help/release_notes/2022/august/"
+---
+
+# 2022년 6월 6일 출시
+
+## 캔버스 메시지 단계에 대한 전달 검증
+
+전달 유효성 검사를 캔버스 [메시지 단계]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/)에서 켤 수 있으며, 메시지 전송 시 오디언스가 전달 기준을 충족하는지 추가로 확인할 수 있습니다. 이 설정은 방해금지 시간, Intelligent Timing 또는 사용량 제한조치가 활성화된 경우 권장됩니다.
+
+## Android 13 SDK 업그레이드 가이드
+
+2022년 6월 8일 현재 Android 13은 [플랫폼 안정성 마일스톤](https://developer.android.com/about/versions/13/overview#platform_stability)에 도달했습니다. 이는 모든 변경 사항이 확정되었으며, 앱 사용자들은 곧 자신의 기기를 업그레이드할 수 있게 될 것임을 의미합니다. Android 13에서 도입된 관련 변경 사항 및 Braze Android SDK 통합에 필요한 업그레이드 단계에 대해 자세히 알아보려면 [Android 13 SDK 업그레이드 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_13/)를 참조하세요.
+
+## iOS 16 SDK 업그레이드 가이드
+
+iOS 16 베타 2(2022년 6월 22일) 기준으로, iOS 16에서 Braze SDK 통합에 영향을 미치는 기능적 변경 사항은 없었습니다. 이것은 Apple이 iOS 16의 새로운 베타 버전을 출시함에 따라 변경될 수 있으므로, iOS 16에 도입된 관련 변경 사항을 설명하는 [iOS 16 소프트웨어 개발 키트 업그레이드 가이드]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/ios_16/)를 주기적으로 확인하는 것을 권장합니다.
+
+## 채널 전송 가이드 사전 안내
+
+자신감을 가지고 캠페인과 캔버스를 시작하세요! 사전 출시 가이드를 방문한 후, 콘텐츠 카드, 이메일, 인앱 메시지, 푸시 및 SMS에 대한 최종 확인 목록 또는 "주의 사항"은 [발송 전에 알아야 할 사항: 채널]({{site.baseurl}}/help/help_articles/campaigns_and_canvas/know_before_send/)을 참조하세요.
+
+## 캠페인 및 캔버스 속성 이름과 ID가 소스마다 어떻게 다른지
+
+캠페인, 캔버스, 및 캔버스 단계 이름과 ID는 모두 Liquid, Braze REST API, 및 커런츠에서 사용할 수 있습니다. 이 속성들은 세 가지 소스 모두에서 동일한 값에 매핑되지만, 이름이 다를 수 있습니다. 이 [새로운 도움말 기사]({{site.baseurl}}/help/help_articles/api/attribute_name_id_across_sources/)은 세 가지 사이의 연결을 그리는 데 도움이 될 것입니다.
+
+## Braze 학습센터
+
+[Braze 학습센터](https://learning.braze.com/)(옛 Learning at Braze·LAB)는 Braze의 주요 개념과 기본 사항에 대한 마케터, 관리자 및 개발자를 위한 과정을 제공합니다. 선택된 기사에서 Braze 학습센터 로고를 주의 깊게 살펴보고, 해당 주제에 대해 더 알아보려면 링크를 클릭하세요.
+
+![커스텀 속성 기사에 있는 Braze 학습 로고는 커스텀 속성을 위한 Braze 학습 과정으로 안내합니다]({% image_buster /assets/img_archive/release_notes_brazelearning.png %})
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2022/7_26_22.md b/_lang/ko/_help/release_notes/2022/7_26_22.md
new file mode 100644
index 00000000000..4896c35daa6
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/7_26_22.md
@@ -0,0 +1,51 @@
+---
+nav_title: 2022년 7월 26일
+page_order: 4
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 7월 26일의 릴리스 노트가 포함되어 있습니다."
+alias: "/help/release_notes/2022/september/"
+---
+
+# 2022년 7월 26일 출시
+
+## 캔버스 플로우
+최신 버전의 캔버스 제품, [캔버스 플로우]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/#editing-a-step)가 출시되었습니다. Canvas Flow를 사용하면 가벼운 [캔버스 구성 요소]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components), [지속적인 항목 속성]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_persistent_entry_properties/), [출시 후 편집]({{site.baseurl}}/post-launch_edits)에 액세스할 수 있습니다.
+
+![]({% image_buster /assets/img/canvas_flow.png %})
+
+## 객체 배열
+관련 속성을 그룹화하려면 [객체 배열]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects#array-of-objects)을 사용하십시오. 예를 들어, 한 사용자에게 속하는 애완동물 객체, 노래 객체 및 계정 객체 그룹이 있을 수 있습니다. 이 배열의 객체는 Liquid로 메시징을 개인화하거나 객체 내의 요소가 기준에 맞으면 오디언스 세그먼트를 생성하는 데 사용할 수 있습니다.
+
+## 업데이트된 파트너 통합
+[Amplitude Recommend]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/amplitude/amplitude_recommend/) 및 [mParticle]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/mParticle/mparticle/)는 이제 업데이트된 통합 단계를 가지고 있습니다. 이 파트너들을 활용하려면, 최신 설정을 따랐는지 확인하기 위해 그들의 설명서를 방문하세요.
+
+## Shopify 요구 사항
+- [전제 조건]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/#prerequisites)에 나열된 필수 사용자 권한이 업데이트되었습니다.
+- 예시 Shopify [payloads]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/#supported-shopify-events)에는 `price`, `total_price`, `total_discounts`, `amount` 속성이 포함되어 있으며, 이 속성들은 문자열 대신 숫자로 형식화되도록 업데이트되었습니다.
+
+## 예측 업데이트
+고객이탈 예측 및 구매 예측을 위한 최대 시간 창이 14일에서 60일로 증가했습니다.
+
+## SDK 업데이트
+다음 소프트웨어 개발 키트 업데이트가 출시되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+- [웹 SDK 4.1.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#410)
+- [Cordova SDK 2.30.1](https://github.com/Appboy/appboy-cordova-sdk/blob/master/CHANGELOG.md#2301)
+- [Unity SDK 3.8.1](https://github.com/Appboy/appboy-unity-sdk/blob/master/CHANGELOG.md#381)
+- [Swift SDK 5.0.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#501)
+- [Roku SDK 0.1.2](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md#012)
+- [React Native SDK 1.37.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#1370)
+  - Braze React Native SDK는 이제 기본값 객체를 ES 모듈로 내보냅니다. 현재 `require()`를 사용하여 SDK를 가져오는 경우 이제 표준 ES 모듈로 가져와야 합니다(예: import Braze from "`@braze/react-native-sdk`").
+- [Android SDK 22.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2200)
+  - `Appboy.java`는 이제 `Braze.kt`입니다. Kotlin 클라이언트는 필요한 경우 Braze 싱글톤에서 Kotlin 속성의 사용을 지원하기 위해 코드를 업데이트해야 합니다.
+    - `Braze.registerPushToken()`/`Braze.getRegisteredPushToken()`은 이제 `Braze.setRegisteredPushToken()/Braze.getRegisteredPushToken()`입니다. Kotlin을 사용하는 경우 속성 `Braze.registeredPushToken`을 사용하십시오.
+    - `Braze.getDeviceId`는 이제 Kotlin의 `Braze.deviceId`입니다.
+    - `Braze.enableMockNetworkAppboyRequestsAndDropEventsMode`는 이제 `Braze.enableMockNetworkRequestsAndDropEventsMode()`입니다.
+    - `Appboy.java`가 제거되었습니다. 예를 들어, `Appboy.getInstance()`와 같은 호출은 앞으로 `Braze.getInstance()`로 이동해야 합니다.
+    - `setCustomAppboyNotificationFactory()`을(를) `setCustomBrazeNotificationFactory()` / `customBrazeNotificationFactory`(으)로 교체했습니다.
+    - 이름을 `enableMockAppboyNetworkRequestsAndDropEventsMode`에서 `enableMockNetworkRequestsAndDropEventsMode`(으)로 변경했습니다.
+  - `com.appboy.IBrazeEndpointProvider`를 `com.braze.IBrazeEndpointProvider`로 이동했습니다.
+  - 이름을 `com.braze.events.IEventSubscriber`에서 `com.braze.events.IEventSubscriber`(으)로 변경했습니다.
+  - `Appboy.registerAppboyPushMessages()` / `Appboy.getAppboyPushMessageRegistrationId()`가 제거되었습니다. `getRegisteredPushToken()` / `setRegisteredPushToken()`으로 교체되었습니다.
+  - `IAppboyNotificationFactory`을(를) `IBrazeNotificationFactory`(으)로 교체했습니다.
+  - `com.appboy.ui.inappmessage.listeners.IHtmlInAppMessageActionListener`로 제거되었습니다. 대신 `com.braze.ui.inappmessage.listeners.IHtmlInAppMessageActionListener`를 사용하세요.
diff --git a/_lang/ko/_help/release_notes/2022/8_23_22.md b/_lang/ko/_help/release_notes/2022/8_23_22.md
new file mode 100644
index 00000000000..e783050b83d
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/8_23_22.md
@@ -0,0 +1,79 @@
+---
+nav_title: 2022년 8월 23일
+page_order: 3
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 8월 23일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2022년 8월 23일 출시
+
+## 개발자 포털
+
+Braze와 함께 구축하는 다른 개발자들과 연결하고 배우며 영감을 얻으세요. 우리의 [개발자 포털](https://www.braze.com/dev-portal)을 확인하고 Slack에서 Braze 개발자 커뮤니티에 참여하세요.
+
+## 메시지 보관
+
+[메시지 보관]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/)은(는) 사용자가 보낸 메시지의 사본을 보관 또는 준수 목적으로 S3 버킷에 저장할 수 있는 추가 기능입니다.
+
+## 캔버스 항목 속성과 이벤트 속성
+
+이름은 비슷하지만, 캔버스 항목 속성과 이벤트 속성정보는 캔버스 워크플로 내에서 다르게 작동합니다. 각 속성을 사용할 시기와 [캔버스 항목 속성과 이벤트 속성]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties)의 동작 차이에 대해 자세히 알아보세요.
+
+## 추적된 링크 별칭
+
+이제 **설정 관리** > **이메일 설정** > **링크 별칭 지정 설정**에서 이메일에서 추적 중인 모든 링크 별칭을 볼 수 있습니다. 자세한 내용은 [추적 링크]({{site.baseurl}}/user_guide/message_building_by_channel/email/templates/link_aliasing/#tracking-links)를 참조하십시오.
+
+## Liquid 5
+
+Braze는 Shopify의 **Liquid 5**까지 Liquid에 대한 지원을 업데이트했습니다. 새로운 Braze 사용자에게 Liquid 5가 일반적으로 제공됩니다. 기존 Braze 사용자에게 Liquid 5는 초기 액세스 상태입니다. [Liquid 5의 새로운 기능]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid#whats-new-with-liquid-5)에 대해 자세히 알아보세요.
+
+## 캠페인 및 캔버스에 대한 모범 사례
+
+성공적인 캠페인과 캔버스를 만드는 것은 복잡할 수 있으므로, 메시징을 최대한 활용하기 위해 알아야 할 모범 사례 목록을 확인하세요.
+
+- [캠페인 best practices]({{site.baseurl}}/user_guide/engagement_tools/campaigns/ideas_and_strategies/best_practices/)
+- [캔버스 모범 사례]({{site.baseurl}}/user_guide/engagement_tools/canvas/best_practices/)
+
+## 캠페인 검색
+
+캠페인을 API 식별자로 검색할 수 있다는 것을 알고 계셨나요? 이것과 다른 방법으로 캠페인을 필터링하고 찾는 방법에 대해 자세히 알아보려면 [캠페인 검색]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/search_campaigns/)을 참조하십시오.
+
+## 새로운 Braze 파트너십
+
+### IAM Studio - 메시지 템플릿
+
+Braze와 [IAM Studio]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/iam_studio/) 통합을 통해 Braze 인앱 메시지에 맞춤형 인앱 메시지 템플릿을 쉽게 삽입할 수 있으며, 이미지 교체, 텍스트 수정, 딥링크 설정, 커스텀 속성 및 이벤트 설정을 제공합니다. IAM Studio를 사용하면 메시지 제작 시간을 줄이고 콘텐츠 계획에 더 많은 시간을 할애할 수 있습니다.
+
+### actionable.me \- 분석
+
+Braze와 [actionable.me]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/actionableme/) 통합을 통해 Braze 활용의 진행 상황을 모니터링할 수 있는 서비스를 배포할 수 있습니다. 도구와 프로세스의 조합을 통해, 귀하의 CRM 성능을 신속하게 벤치마킹하고 새로운 영업 기회를 식별하며 더 나은 성과를 내기 위한 권장 사항을 제공합니다.
+
+### Storyly - 코호트 가져오기
+
+Braze와 [Storyly]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/storyly/) 통합을 통해 Braze의 세그먼트를 Storyly 플랫폼의 오디언스로 사용할 수 있습니다. 이 통합을 통해 다음을 수행할 수 있습니다:
+
+- 특정 스토리로 세그먼트를 타겟팅하세요
+- 사용자 속성을 사용하여 스토리 콘텐츠를 개인화하세요
+
+### Lokalise - 현지화
+
+Braze와 [Lokalise]({{site.baseurl}}/partners/message_personalization/localization/lokalise/) 통합은 연결된 콘텐츠를 활용하여 사용자 언어 설정에 따라 번역된 콘텐츠를 Braze 캠페인에 쉽게 삽입할 수 있도록 합니다.
+
+### Quikly - 리타겟팅
+
+Braze와 [Quikly]({{site.baseurl}}/partners/message_orchestration/additional_channels/retargeting/quikly/) 파트너십을 통해 Braze 고객 여정 내 이벤트의 전환을 가속화할 수 있습니다. Quikly는 긴급 심리학을 사용하여 소비자들을 재미있고 즉각적인 방식으로 동기 부여함으로써 이를 수행합니다. 예를 들어, 브랜드는 Quikly를 사용하여 새로운 이메일 및 SMS 구독자를 Braze에 직접 추가하거나 모바일 앱 다운로드와 같은 다른 주요 마케팅 목표를 달성하도록 유도할 수 있습니다.
+
+### DataGrail - 데이터 프라이버시 및 준수
+
+Braze와 [DataGrail]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_privacy/datagrail/) 통합을 통해 Braze 내에 수집 및 저장된 소비자 데이터를 감지하여 DSR(접근, 삭제 및 판매 금지 요청)을 신속하게 처리할 수 있습니다. Braze는 소비자 데이터가 조직 내 어디에 있는지에 대한 정확한 청사진에 추가될 것이며, 자동화된 데이터 매핑을 통해 더 이상 설문 조사나 스프레드시트가 필요하지 않습니다. 이를 통해 개인정보 보호 프레임워크를 유지하거나 처리 활동 기록(RoPA)을 생성할 수 있습니다.
+
+## SDK 업데이트
+
+다음 소프트웨어 개발 키트 업데이트가 출시되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [웹 SDK 4.2.0–4.2.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#421)
+- [iOS 4.5.0](https://github.com/Appboy/appboy-ios-sdk/blob/master/CHANGELOG.md#450) (Objective-C)
+- [iOS Swift 5.1.0–5.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#520)
+- [Android 23.0.0–23.0.1](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2301)
+    - `BaseContentCardView.bindViewHolder()`는 이제 일반 유형 대신 `Card`를 사용합니다.
diff --git a/_lang/ko/_help/release_notes/2022/9_20_22.md b/_lang/ko/_help/release_notes/2022/9_20_22.md
new file mode 100644
index 00000000000..284705120ab
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2022/9_20_22.md
@@ -0,0 +1,42 @@
+---
+nav_title: 2022년 9월 20일
+page_order: 2
+noindex: true
+page_type: update
+description: "이 문서에는 2022년 9월 20일에 대한 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2022년 9월 20일 출시
+
+## API 가이드
+[Braze API 가이드]({{site.baseurl}}/api/home)에서 엔드포인트 유형에 따라 엔드포인트를 검색하여 용어집의 범위를 좁힐 수 있습니다.
+
+## 개인화된 변형
+[개인화된 배리언트를]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign/#optimizations) 사용하여 타겟 세그먼트의 각 사용자에게 참여 가능성이 가장 높은 배리언트를 보내세요.
+
+## 테스트 캔버스
+캔버스를 만든 후에는 오디언스 규모나 세분화 필터 수와 같은 세부 사항에 따라 시작하기 전에 수행해야 할 몇 가지 점검 사항이 있습니다. 팁은 [테스트 캔버스 보내기에서]({{site.baseurl}}/user_guide/engagement_tools/canvas/testing_canvases/sending_test_canvases/) 확인하세요.
+
+## 액체 5
+기존 Braze 사용자의 경우, 일반적으로 Liquid 5를 사용할 수 있습니다. [Liquid 5의 새로운 기능]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid#whats-new-with-liquid-5)에 대해 자세히 알아보세요.
+
+## 새로운 Braze 파트너십
+
+### Shopify
+Braze와 [Shopify]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify/)를 사용하면 Shopify 스토어에서 캡처되는 리드, 가입 및 계정 등록을 위해 기존 고객 프로필을 업데이트하거나 Braze에서 새 프로필을 생성할 수 있습니다.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Android SDK 23.1.0-23.12](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [React Native SDK v1.38.0-v1.38.1](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+	- 네이티브 Android 브릿지를 Braze Android SDK 23.0.1로 업데이트했습니다.
+	- 네이티브 iOS 브릿지를 Braze iOS SDK 4.5.0으로 업데이트했습니다.
+	- 이제 Braze React Native Android SDK는 컴파일 시 코틀린을 직접 사용해야 합니다.
+- [Braze Expo 플러그인 0.4.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+	- 소품 `fcmSenderID` 의 이름을 `firebaseCloudMessagingSenderId` 으로 변경했습니다.
+- [Unity 3.9.0](https://github.com/Appboy/appboy-unity-sdk/blob/master/CHANGELOG.md)
+	- Braze Android SDK 23.1.0을 사용하도록 Android 플러그인을 업데이트했습니다.
+	- `Appboy.AppboyBinding.PromptUserForPushPermissions(false)`를 통해 Android 13 이상 기기에서 푸시 알림 권한을 요청할 수 있는 기능이 추가되었습니다.
+- [Swift SDK 5.3.0-5.4.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#540)
diff --git a/_lang/ko/_help/release_notes/2023.md b/_lang/ko/_help/release_notes/2023.md
new file mode 100644
index 00000000000..08d68b6d5fe
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023.md
@@ -0,0 +1,52 @@
+---
+page_order: 1
+nav_title: 2023
+layout: dev_guide
+noindex: true
+guide_top_header: "2023 릴리스 노트"
+
+page_type: landing
+description: "이 섹션은 2023년 릴리스 노트가 있는 곳입니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 2023년 1월 10일
+    link: /docs/help/release_notes/2023/1_10_23/
+    image: /assets/img/braze_icons/snowflake-01.svg
+  - name: 2023년 2월 7일
+    link: /docs/help/release_notes/2023/2_7_23/
+    image: /assets/img/braze_icons/hearts.svg
+  - name: 2023년 3월 7일
+    link: /docs/help/release_notes/2023/3_7_23/
+    image: /assets/img/braze_icons/trophy-01.svg
+  - name: 2023년 4월 4일
+    link: /docs/help/release_notes/2023/4_4_23/
+    image: /assets/img/braze_icons/droplets-01.svg
+  - name: 2023년 5월 2일
+    link: /docs/help/release_notes/2023/5_2_23/
+    image: /assets/img/braze_icons/sun.svg
+  - name: 2023년 5월 30일
+    link: /docs/help/release_notes/2023/5_30_23/
+    image: /assets/img/braze_icons/sun.svg
+  - name: 2023년 6월 27일
+    link: /docs/help/release_notes/2023/6_27_23/
+    image: /assets/img/braze_icons/umbrella-03.svg
+  - name: 2023년 7월 25일
+    link: /docs/help/release_notes/2023/7_25_23/
+    image: /assets/img/braze_icons/flag-01.svg
+  - name: 2023년 8월 22일
+    link: /docs/help/release_notes/2023/8_22_23/
+    image: /assets/img/braze_icons/wind-02.svg
+  - name: 2023년 9월 19일
+    link: /docs/help/release_notes/2023/9_19_23/
+    image: /assets/img/braze_icons/backpack.svg
+  - name: 2023년 10월 17일
+    link: /docs/help/release_notes/2023/10_17_23/
+    image: /assets/img/braze_icons/magic-wand-02.svg
+  - name: 2023년 11월 14일
+    link: /docs/help/release_notes/2023/11_14_23/
+    image: /assets/img/braze_icons/cloud-sun-02.svg
+  - name: 2023년 12월 12일
+    link: /docs/help/release_notes/2023/12_12_23/
+    image: /assets/img/braze_icons/gift-01.svg
+---
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2023/10_17_23.md b/_lang/ko/_help/release_notes/2023/10_17_23.md
new file mode 100644
index 00000000000..2076699e39d
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/10_17_23.md
@@ -0,0 +1,80 @@
+---
+nav_title: 2023년 10월 17일
+page_order: 2
+noindex: true
+page_type: update
+description: "이 문서에는 10/17/23에 대한 릴리스 노트가 포함되어 있습니다."
+ 
+---
+# 2023년 10월 17일 출시
+
+## 워크스페이스에 복사하기
+
+[워크스페이스 전반에 걸쳐 캠페인을 복사하면]({{site.baseurl}}/user_guide/engagement_tools/campaigns/managing_campaigns/copying_to_workspace/) 다른 워크스페이스에 있는 캠페인의 복사본으로 시작하여 메시지 구성을 빠르게 시작할 수 있습니다. 이 사본은 편집하고 시작할 때까지 초안으로 유지되므로 성공적인 메시징 전략을 유지하고 발전시키는 데 도움이 됩니다.
+
+## 테스트 커런츠 커넥터
+
+[테스트 커런츠 커넥터]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/setting_up_currents/#test-currents-connectors)는 다양한 대상을 테스트하고 사용해 볼 수 있는 기존 커넥터의 무료 버전입니다. 테스트 커런츠의 특징:
+
+- 빌드할 수 있는 테스트 커런츠 커넥터 수에는 제한이 없습니다.
+- 30일 롤링 기간당 총 최대 10,000개의 이벤트가 집계됩니다. 이 이벤트 총계는 대시보드에서 매시간 업데이트됩니다.
+
+## 기능 플래그
+
+[피처 플래그]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/about/)를 사용하면 특정 또는 무작위로 선택한 사용자에 대해 원격으로 기능을 활성화 또는 비활성화할 수 있습니다. 중요한 점은 추가 코드 배포나 앱 스토어 업데이트 없이 프로덕션 환경에서 기능을 켜고 끌 수 있다는 점입니다. 이를 통해 새로운 기능을 안심하고 안전하게 출시할 수 있습니다.
+
+## 기능 플래그 실험
+
+[피처 플래그 실험]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/experiments/)을 통해 애플리케이션의 변경 사항을 A/B 테스트하여 전환율을 최적화할 수 있습니다. 마케터는 기능 플래그를 사용하여 새로운 기능이 전환율에 긍정적인 영향을 미치는지 부정적인 영향을 미치는지 또는 어떤 피처 플래그 속성 집합이 가장 적합한지 결정할 수 있습니다.
+
+## 사용자 프로필 병합하기
+
+**사용자 검색** 페이지에서 검색한 결과 여러 개의 사용자 프로필이 표시되는 경우 **중복 항목 병합** 버튼을 클릭하여 [사용자 프로필을 병합]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles#merge-profiles)할 수 있습니다. 유지할 사용자 프로필을 선택할 수 있습니다. 즉, 이 프로필은 유지되며 병합된 프로필의 속성을 얻게 됩니다.
+
+## 세그먼트별 성능 데이터
+
+이제 쿼리 빌더 보고서 템플릿을 사용하여 캠페인, 캔버스, 배리언트 상품 및 단계에 대한 세그먼트별로 [성과 데이터를 세분화할]({{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/#performance-data-by-segment) 수 있습니다.
+
+## 사용자 프로필 업데이트
+
+이제 [`/users/track` 엔드포인트를]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) 사용하여 전화번호나 이메일로 사용자 프로필을 업데이트할 수 있습니다.
+
+## SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+ 
+- [Braze 세그먼트 Swift 플러그인 v2.1.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md)
+- [웹 SDK v4.10.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- [웹 SDK v5.0.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+    - 이제 [`subscribeToFeatureFlagsUpdates()`](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#subscribetofeatureflagsupdates) 콜백은 이제 새로 고침 성공/실패에 관계없이 항상 호출됩니다. 업데이트 수신에 실패하면 현재 캐시된 피처 플래그를 사용하여 콜백이 호출됩니다.
+    - 이제 [`getFeatureFlag()`](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#getfeatureflag) 메서드는 이제 기능 플래그가 존재하지 않거나 기능 플래그가 비활성화되어 있는 경우 null을 반환합니다.
+    - 4.0.4에서 사용되지 않던 `logContentCardsDisplayed()` 메서드를 제거했습니다.
+    - 더 이상 사용되지 않는 초기화 옵션 `enableHtmlInAppMessages` 을 제거했습니다. 대신 `allowUserSuppliedJavascript` 옵션으로 대체해야 합니다.
+    - [`ImageOnly`](https://js.appboycdn.com/web-sdk/latest/doc/classes/braze.imageonly.html)를 위해 이전에 4.9.0에서 더 이상 사용되지 않던 배너 클래스를 제거했습니다.
+    - `Banner` 클래스 제거의 일부로 `ab-banner` CSS 클래스명을 제거했습니다. CSS 사용자 정의는 대신 `ab-image-only` 클래스를 대상으로 해야 합니다.
+    - SDK는 더 이상 런타임 오류를 발생시키지 않습니다. 초기화 전에 Braze 메서드가 호출되면 대신 콘솔에 경고가 기록됩니다.
+    - SDK는 더 이상 사용자 지정 HTML 인앱 메시지에 기본 Braze 인앱 메시지 스타일을 추가하지 않습니다. 이러한 스타일은 이전에는 기존 인앱 메시지 유형에서 사용되었습니다.
+- [Android SDK 29.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+    - `BannerImageCard`, `BannerImageCardView`, `BannerImageContentCardView`의 이름을 `ImageOnlyCard`, `ImageOnlyCardView`, `ImageOnlyContentCardView`로 변경했습니다 .
+    - 배너 카드에 사용되는 모든 스타일이 이미지 전용 카드로 업데이트되었습니다. `banner`라는 단어가 포함된 모든 키는 `image_only`로 대체해야 합니다.
+    - 이제 디바이스 브랜드 정보가 전송됩니다. 이를 차단하려면 데이터 수집 차단하기를 참조하세요.
+- [Flutter SDK 7.0.0](https://pub.dev/packages/braze_plugin/changelog)
+    - 네이티브 Android 브릿지를 [Braze 안드로이드 SDK 26.1.1에서 27.0.1로](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2701) 업데이트합니다.
+    - Gradle 8에 대한 지원을 추가합니다.
+- [Swift SDK 7.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+    - 이제 `useUUIDAsDeviceId` 구성이 기본적으로 활성화됩니다.
+        - 영향에 대한 자세한 내용은 [IDFV 수집 - Swift를]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/swift_idfv/) 참조하세요.
+    - 배너 콘텐츠 카드 유형 및 해당 UI 요소의 이름이 `ImageOnly` 으로 변경되었습니다. 모든 멤버 메서드와 프로퍼티는 동일하게 유지됩니다.
+        - `Braze.ContentCard.Banner` → `Braze.ContentCard.ImageOnly`
+        - `BrazeContentCardUI.BannerCell` → `BrazeContentCardUI.ImageOnlyCell`
+    - BrazeUI의 일부 텍스트 레이아웃 로직을 새로운 Braze.ModalTextView 클래스로 리팩터링합니다.
+    - 기능 플래그 메서드에 대한 동작을 업데이트합니다.
+        - `FeatureFlags.featureFlag(id:)` 는 이제 존재하지 않는 ID에 대해 nil을 반환합니다.
+        - `FeatureFlags.subscribeToUpdates(:)`는 새로 고침 요청이 성공 또는 실패로 완료되면 콜백을 트리거합니다.
+            - 콜백은 또한 이전에 캐시된 데이터가 있는 경우 최초 구독 시 즉시 트리거됩니다.
+- [AppboyKit iOS SDK 4.6.0](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.6.0)
+    - 이 릴리스에는 Xcode `14.x` 가 필요합니다.
+    - iOS 9 및 iOS 10에 대한 지원이 중단됩니다.
+    - Carthage를 통해 가져올 때 오래된 `.framework` 에셋에 대한 지원을 제거하고 최신 `.xcframework` 에셋을 사용합니다.
+        - `carthage update --use-xcframeworks` 명령을 사용하여 적절한 Braze 에셋을 가져옵니다.
+        - `appboy_ios_sdk_full.json` 사용을 위해 `appboy_ios_sdk.json` 지원을 제거합니다
diff --git a/_lang/ko/_help/release_notes/2023/11_14_23.md b/_lang/ko/_help/release_notes/2023/11_14_23.md
new file mode 100644
index 00000000000..6680d4558bc
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/11_14_23.md
@@ -0,0 +1,92 @@
+---
+nav_title: 2023년 11월 14일
+page_order: 1
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 11월 14일에 대한 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 11월 14일 출시
+
+## Braze 시작하기
+
+흥미로운 소식입니다! Braze [마케터와]({{site.baseurl}}/user_guide/getting_started) [개발자]({{site.baseurl}}/developer_guide/platform_wide/getting_started)를 위해 특별히 맞춤화된 두 개의 시작하기 섹션을 소개합니다. 이 섹션은 필요한 모든 도구와 안내를 제공하여 Braze를 시작하는 데 도움이 되도록 설계되었습니다. 들어가서 탐색을 시작하세요.
+
+## 새로운 Braze 대시보드 인스턴스
+
+Braze는 대시보드 및 REST 엔드포인트에 대한 다양한 인스턴스를 관리합니다. 새 대시보드 인스턴스를 추가했습니다 `US-07`. 자세한 내용은 [API 개요]({{site.baseurl}}/api/basics/)를 참조하세요.
+
+## 강력한 채널
+
+### 인앱 메시지를 위한 사용자 지정 드래그 앤 드롭 템플릿
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 드래그 앤 드롭 편집기에서 인앱 메시지에 대한 [커스텀 드래그 앤 드롭 템플릿]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/)을 사용하여 인앱 메시지 디자인을 시작할 수 있습니다.
+
+### SMS 이중 옵트인
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[SMS 이중 옵트인]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/sms_double_opt_in/)을 사용하면 사용자가 SMS 메시지를 수신하기 전에 명시적으로 옵트인 의도를 확인하도록 요구할 수 있습니다. 이를 통해 SMS에 참여할 가능성이 높거나 참여 중인 사용자에 초점을 맞출 수 있습니다.
+
+### 이메일 보고를 위한 예상 실제 오픈율
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[실제 열람율 추정치]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/email_reporting#estimated-real-open-rate)는 Braze에서 개발한 독점 분석 모델을 사용하여 기계 오픈이 존재하지 않는 것처럼 캠페인의 고유한 오픈율 추정치를 재구성합니다. Braze는 각 캠페인의 클릭 데이터를 사용하여 실제 사용자가 메시지를 열어본 비율을 추론합니다. 이는 Apple의 MPP를 비롯한 다양한 기기 개방 메커니즘을 보완합니다. 
+
+### 캔버스를 위한 개인화된 경로
+
+{% multi_lang_include release_type.md release="베타" %}
+
+[개인화된 경로를]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths/) 사용하면 캠페인의 개인화된 변형과 유사하게 전환 가능성에 따라 개별 사용자의 전체 캔버스 여정을 개인화할 수 있습니다. 개인화된 경로와 실험 경로 단계를 사용하여 일부 사용자를 지연 그룹에 묶어두고 나머지 경로를 Braze가 서로 테스트하는 동안 기다립니다.
+
+## 데이터 유연성
+
+### Braze 대시보드 검색하기
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[검색창을]({{site.baseurl}}/user_guide/administrative/access_braze/global_search/) 사용하여 Braze 대시보드 내에서 내 작업 및 기타 정보를 찾을 수 있습니다. 검색창은 Braze 대시보드 상단에 있습니다. 
+
+### 사용자 지정 속성 및 이벤트 차단 목록
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 한 번에 최대 10개의 커스텀 속성 또는 이벤트를 차단 목록에 추가할 수 있습니다. 자세한 내용은 [커스텀 이벤트 및 속성 관리]({{site.baseurl}}/user_guide/administrative/app_settings/custom_event_and_attribute_management/)를 참조하세요.
+
+### 새 도움말 문서: 유니버설 링크 및 앱 링크
+
+Apple 유니버설 링크와 Android 앱 링크는 웹 콘텐츠와 모바일 앱 간의 원활한 전환을 제공하기 위해 고안된 메커니즘입니다. 보편적 링크는 iOS에만 해당되지만, Android 앱 링크는 Android 애플리케이션에 동일한 목적을 제공합니다. 
+
+이 주제에 대한 자세한 내용은 [유니버설 링크 및 앱 링크]({{site.baseurl}}/help/help_articles/email/universal_links/) 전용 문서를 참조하세요.
+
+## 새로운 Braze 파트너십
+
+### Olo - 채널 확장
+
+Braze와 [Olo의]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/olo/) 통합을 통해 Braze에서 사용자 프로필을 업데이트하여 Olo 사용자 프로필과 일관성을 유지할 수 있습니다. 또한 Olo 이벤트에 따라 Braze에서 적절한 메시지를 보낼 수도 있습니다.
+
+### Typeform - 고객 데이터 플랫폼
+
+Braze와 [Typeform]({{site.baseurl}}/partners/message_orchestration/channel_extensions/surveys/typeform/) 통합을 통해 Typeform 응답에서 수집된 데이터로 Braze의 사용자 프로필을 업데이트하고, 사용자의 Typeform 참여에 따라 Braze에서 메시지를 트리거하고, 사용자의 Typeform 응답에 따라 Braze 메시지를 개인화할 수 있습니다.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [웹 SDK v4.10.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- [웹 SDK v5.0.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- [Android SDK 29.0.1](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [Swift SDK 7.1.0-7.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+    - `Braze.Configuration.DeviceProperty.pushDisplayOptions` 는 더 이상 사용되지 않습니다. 이 값을 제공해도 더 이상 효과가 없습니다.
+- [React Native SDK 8.0.0-8.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+    - 네이티브 Android 브릿지를 Braze Android SDK 27.0.1에서 29.0.0으로 업데이트합니다.
+    - 네이티브 iOS 브릿지를 Braze Swift SDK 6.6.0에서 7.0.0으로 업데이트합니다.
+    - `Banner` 콘텐츠 카드 유형의 이름을 이미지 전용으로 변경합니다:
+        - `BannerContentCard`부터 `ImageOnlyContentCard`까지
+        - `ContentCardTypes.BANNER`부터 `ContentCardTypes.IMAGE_ONLY`까지
+    - Android에서 프로젝트의 XML 파일에 콘텐츠 카드의 경우 `banner`라는 단어가 포함되어 있으면 `image_only`로 대체해야 합니다.
+    - `Braze.getFeatureFlag(id)`는 이제 기능 플래그가 존재하지 않으면 `null`을 반환합니다.
+    - `Braze.Events.FEATURE_FLAGS_UPDATED`는 새로 고침 요청이 성공 또는 실패로 완료된 경우와 현재 세션에서 이전에 캐시된 데이터가 있는 경우 최초 구독 시에만 트리거됩니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2023/12_12_23.md b/_lang/ko/_help/release_notes/2023/12_12_23.md
new file mode 100644
index 00000000000..366ff9cf9cc
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/12_12_23.md
@@ -0,0 +1,92 @@
+---
+nav_title: 2023년 12월 12일
+page_order: 0
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 12워 12일에 대한 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 12월 12일 출시
+
+## Android 푸시 통합 업데이트
+
+2023년 6월 20일, Google은 Android 앱에 푸시 알림을 보내기 위한 클라우드 메시징 API를 더 이상 사용하지 않습니다. 이제 [표준 Android 푸시 통합](https://www.braze.com/docs/developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration/)을ㄹ 통해 Google의 Firebase 클라우드 메시징 API를 설정하는 방법을 대신 확인할 수 있습니다.
+
+Google의 클라우드 메시징 API 감가상각에 대한 자세한 내용은 [Firebase FAQ](https://firebase.google.com/support/faq#fcm-23-deprecation)를 참조하세요.
+
+## 강력한 채널
+
+### WhatsApp 응답 메시지
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+캠페인 또는 캔버스에서 [WhatsApp 메시지를 만들]({{site.baseurl}}/whatsapp_response_messaging/) 때 24시간 이내에 사용자의 WhatsApp 메시지에 답장할 수 있는 응답 메시지를 만들 수 있습니다. 응답 메시지는 옵트인 캠페인과 같이 브랜드와 사용자 간의 상호 작용을 장려하는 캔버스에서 특히 유용할 수 있습니다.
+
+### WhatsApp 주파수 제한
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 WhatsApp에 대한 [사용 횟수 제한 규칙을]({{site.baseurl}}/user_guide/engagement_tools/campaigns/building_campaigns/rate-limiting/#frequency-capping) 설정할 수 있습니다. 빈도 제한은 캠페인 또는 캔버스 컴포넌트 전송 수준에서 적용되며 **설정** > **최대 게재빈도 설정 규칙**에서 각 워크스페이스에 대해 설정할 수 있습니다.  
+
+## 데이터 유연성
+
+### 전환 대시보드
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[전환 대시보드]({{site.baseurl}}/user_guide/data_and_analytics/analytics/conversions_dashboard/)에서는 다양한 기여도 방법을 사용하여 캠페인, 캔버스 및 채널 전반의 전환을 분석할 수 있습니다. 전환을 측정할 때 시간 프레임, 전환 이벤트, 전환 기간을 지정할 수 있습니다.
+
+### 이메일 인사이트 보고서
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[이메일 성능 대시보드]({{site.baseurl}}/email_engagement_dashboard/) 내에 이메일 인사이트라는 새 탭이 있으며, 이 탭에는 두 개의 새 보고서가 포함되어 있습니다:
+
+- **받은편지함 공급자별 이메일 인게이지먼트:** 사서함 공급자별 클릭 및 열기 횟수를 표시합니다. 사서함 공급업체를 선택하고 특정 수신 도메인으로 드릴다운할 수 있습니다.
+- **요일별 참여도:** 사용자가 이메일에 참여하는 시기를 표시합니다.
+
+### 구독 그룹 시계열 그래프로 업데이트
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 **구독 그룹** 페이지에 표시되는 **구독** **그룹** **시계열** 그래프에 이메일이나 전화번호가 아닌 사용자당 구독 수가 표시됩니다. 이는 Braze가 대시보드의 다른 영역에서 통계를 계산하는 방식과 더 잘 일치합니다.
+
+## AI 및 ML 자동화
+
+### AI 항목 추천
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[AI 상품]({{site.baseurl}}/ai_item_recommendations) 추천은 사용자의 구매 행동을 종합하여 상품을 추천하는 딥러닝 기반 상품 추천 엔진입니다. AI 품목 추천을 사용하여 가장 인기 있는 제품을 계산하거나 특정 카탈로그에 대한 개인화된 AI 추천을 생성할 수 있습니다. 추천을 생성한 후 개인화를 사용하여 해당 제품을 메시지에 삽입할 수 있습니다.
+
+## 새로운 Braze 파트너십
+
+### Zapier를 통한 페이스북 리드 광고 - 리드 캡처
+
+[Zapier를 통한 Facebook 리드 광고 통합을]({{site.baseurl}}/partners/data_and_infrastructure_agility/leads_capture/facebook_via_zapier/) 사용하면 Facebook에서 Braze로 리드를 가져오고 리드가 캡처되면 사용자 지정 이벤트를 추적할 수 있습니다.
+
+### SmarterSends - 메시지 템플릿
+
+Braze와 [SmarterSends]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/smartersends/)의 파트너십을 통해 분산된 사용자가 소유한 초지역화 콘텐츠에 Braze의 강력한 기능을 결합하여 마케팅 캠페인을 향상시킬 수 있습니다.
+
+### Recurly - 결정
+
+[Recurly와]({{site.baseurl}}/partners/data_and_infrastructure_agility/payments/recurly/) Braze 통합 의부로 구독 데이터 공유 프로세스가 간소화되어 고객과 타겟팅된 커뮤니케이션이 가능해집니다.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Flutter SDK 8.0.0-8.1.0](https://pub.dev/packages/braze_plugin/changelog)
+  - 네이티브 Android 브릿지를 Braze Android SDK 27.0.1에서 29.0.1로 업데이트합니다.
+  - 네이티브 iOS 브릿지를 Braze Swift SDK 6.6.1에서 7.2.0으로 업데이트합니다.
+  - 기능 플래그 메서드의 동작을 수정합니다.
+    - `BrazePlugin.getFeatureFlagByID(String id)`는 이제 기능 플래그가 존재하지 않으면 `null`을 반환합니다.
+    - `BrazePlugin.subscribeToFeatureFlags(void Function(List<BrazeFeatureFlag>) onEvent))` 는 다음 상황에서만 트리거됩니다:
+      - 새로 고침 요청이 성공 또는 실패로 완료된 경우.
+      - 현재 세션에서 이전에 캐시된 데이터가 있는 경우 최초 구독 시.
+  - 지원되는 최소 Android SDK 버전은 21입니다.
+- [React Native SDK 8.2.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.2.0/CHANGELOG.md)
+- [Swift SDK 7.3.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+- [Braze 세그먼트 스위프트 플러그인 2.2.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md)
+- [Braze Expo 플러그인 1.2.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.2.0/CHANGELOG.md)
diff --git a/_lang/ko/_help/release_notes/2023/1_10_23.md b/_lang/ko/_help/release_notes/2023/1_10_23.md
new file mode 100644
index 00000000000..34328046d5c
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/1_10_23.md
@@ -0,0 +1,47 @@
+---
+nav_title: 2023년 1월 10일
+page_order: 12
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 1월 10일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 1월 10일 출시
+
+## 캔버스 플로우용 사용자 업데이트 구성 요소
+
+[사용자 업데이트]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/user_update/) 컴포넌트를 사용하면 JSON 컴포저에서 사용자의 속성, 이벤트 및 구매를 업데이트할 수 있으므로 API 키와 같은 민감한 정보를 포함할 필요가 없습니다. 
+
+## API를 통해 구독 그룹 설정하기
+
+[`/users/track` 엔드포인트를]({{site.baseurl}}/api/endpoints/user_data/post_user_track/) 통해 새 사용자를 만들 때 사용자 속성 개체 내에서 구독 그룹을 설정하면 한 번의 API 호출로 사용자를 만들고 구독 그룹 상태를 설정할 수 있습니다.
+
+## 전환 대시보드 얼리 액세스
+
+[전환 대시보드]({{site.baseurl}}/user_guide/data_and_analytics/analytics/conversions_dashboard/)에서는 다양한 기여도 방법을 사용하여 캠페인, 캔버스 및 채널 전반의 전환을 분석할 수 있습니다. 이러한 어트리뷰션 방법을 구체적으로 추적할 수 있습니다:
+
+- **열린 전환** 사용자가 메시지를 연 후 발생한 전환 수
+- **클릭전환:** 사용자가 메시지를 클릭한 후 발생한 전환 수
+- **전환 수신:** 사용자가 메시지를 수신한 후 발생한 전환 수
+- **마지막 클릭 전환:** 사용자가 메시지를 클릭한 후 발생한 전환(해당 메시지가 사용자가 클릭한 가장 최근의 메시지인 경우) (이 기능은 현재 일부 얼리 액세스 고객을 대상으로 테스트 중입니다.)
+
+이 기능은 현재 얼리 액세스 중입니다. 얼리 액세스에 참여하고 싶다면 고객 성공 매니저에게 문의하세요.
+
+## Braze 커런츠용 캔버스 종료 이벤트
+
+이제 이벤트를 수행하거나 오디언스를 매칭하여 사용자가 캔버스에서 나가는 시점을 추적할 수 있습니다. 자세한 내용은 커런츠 이벤트 용어집의 [메시지 참여 이벤트]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events/) 섹션을 참조하세요.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [웹 SDK 4.5.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- [AppboyKit iOS SDK 4.5.2](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.5.2)
+- [Swift SDK 5.8.0-5.8.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#580)
+	- `BrazeLocation` 클래스의 이름을 `BrazeLocationProvider`로 변경하여 같은 이름의 모듈을 섀도잉하지 않도록 합니다.
+- [Flutter SDK 3.0.1](https://pub.dev/packages/braze_plugin/changelog)
+- [Android SDK 24.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+	- 위치 및 지오펜스 기능이 `com.braze:android-sdk-location` 라는 새 모듈로 이전되었습니다.
+	- Appboy 클래스와 파일이 Braze로 일괄 이전되었습니다.
+	- 콘텐츠 카드를 정렬할 때 마지막 업데이트 시간 대신 생성 시간을 사용하도록 `DefaultContentCardsUpdateHandler`의 기본 동작을 변경했습니다.
+	- BrazeUser.setFacebookData() 및 BrazeUser.setTwitterData()를 제거했습니다.
diff --git a/_lang/ko/_help/release_notes/2023/2_7_23.md b/_lang/ko/_help/release_notes/2023/2_7_23.md
new file mode 100644
index 00000000000..9bf5eaf2bb7
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/2_7_23.md
@@ -0,0 +1,90 @@
+---
+nav_title: 2023년 2월 7일
+page_order: 11
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 2월 7일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 2월 7일 출시
+
+## 접근성 높은 메시지 작성
+
+의도하지 않았더라도 장애인을 배제하는 마케팅 콘텐츠는 수백만 명의 사람들이 브랜드와 소통하지 못하게 만들 수 있습니다. 마케팅에서 접근성이란 누구나 쉽게 마케팅을 경험하고, 커뮤니케이션을 수신하고 이해하며, 제품, 서비스 또는 브랜드에 투자하거나 팬이 될 수 있는 기회를 가질 수 있도록 하는 것입니다. 자세한 내용은 [Braze에서 접근성 높은 메시지 작성하기]({{site.baseurl}}/help/accessibility#building-accessible-messages-in-braze)를 참조하세요.
+
+## 쿼리 작성기 미리 보기
+
+[쿼리 빌더]({{site.baseurl}}/user_guide/data_and_analytics/query_builder#query-builder
+)를 사용하면 Snowflake에서 Braze 데이터를 사용하여 보고서를 생성할 수 있습니다. 쿼리 빌더에는 미리 작성된 SQL 쿼리 템플릿이 제공되므로 바로 시작할 수 있습니다. 현재는 템플릿화된 쿼리만 허용됩니다. 사용자 지정 SQL 쿼리에 대한 지원도 곧 추가될 예정입니다.
+
+이 기능은 현재 얼리 액세스 중입니다. 미리 맛보기에 참여하고 싶다면 고객 성공 매니저에게 문의하세요.
+
+## 기능 플래그 베타
+
+[피처 플래그]({{site.baseurl}}/developer_guide/platform_wide/feature_flags)를 사용하면 선택한 사용자에 대한 기능을 원격으로 활성화 또는 비활성화할 수 있습니다. 추가 코드 배포나 앱 스토어 업데이트 없이 프로덕션 환경에서 기능을 켜고 끌 수 있습니다. 이를 통해 새로운 기능을 안심하고 안전하게 출시할 수 있습니다.
+
+이 기능은 현재 베타 버전입니다. 베타 버전에 참여하려면 고객 성공 매니저에게 문의하세요.
+
+## 신규 커런츠 이벤트
+
+최근 다음과 같은 커런츠 이벤트가 출시되어 [메시지 참여 이벤트와]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events) [고객 행동 및 사용자 이벤트]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events) 용어집에 추가되었습니다:
+
+메시지 중단 이벤트:
+- `users.messages.contentcard.abort`
+- `users.messages.email.abort`
+- `users.messages.inappmessage.abort`
+- `users.messages.pushnotification.abort`
+- `users.messages.sms.abort`
+- `users.messages.webhook.abort`
+
+SMS 짧은 링크 클릭 이벤트:
+- `users.messages.sms.ShortLinkClick`
+
+글로벌 상태 변경 구독 이벤트:
+- `users.behaviors.subscription.GlobalStateChange`
+
+구독 그룹 상태 변경 이벤트:
+- `users.behaviors.subscriptiongroup.StateChange`
+
+캔버스 종료 이벤트:
+- `users.canvas.exit.PerformedEvent`
+- `users.canvas.exit.MatchedAudience`
+
+## 개인화된 배리언트
+
+A/B 테스트를 보낼 때 사용자에게 개인화된 변형을 전송하여 참여 가능성이 가장 높은 변형을 보낼 수 있습니다. 개인화된 이형 상품을 선택하는 방법과 캠페인에서 이를 활용하는 방법에 대한 자세한 내용은 [다변량 분석을]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/multivariate_analytics/#personalized-variant) 참조하세요. 
+
+## SQL 세그먼트 확장 얼리 액세스
+
+[세그먼트 확장]({{site.baseurl}}/sql_segments/)을 사용하면 Snowflake 데이터의 Snowflake SQL 쿼리를 사용하여 세그먼트 확장을 생성할 수 있습니다. SQL은 다른 세그먼트 기능으로는 달성할 수 없는 방식으로 데이터 간의 관계를 설명할 수 있는 유연성을 제공하기 때문에 새로운 세그먼트 사용 사례를 발굴하는 데 도움이 될 수 있습니다.
+
+## 캔버스 출시 전 및 출시 후 체크리스트
+
+캔버스를 시작하기 전과 후에 확인해야 할 몇 가지 세부 사항이 있습니다:
+- 메시징 및 전송 시간이 오디언스의 선호도에 맞게 조정되었는지 확인하세요.
+- 시간대, 항목 설정 등의 변화를 고려하세요.
+- 출시 후 불일치하는 경우 다음 시나리오에 따라 캔버스를 검토하고 조정합니다.
+
+이 [체크리스트]({{site.baseurl}}/user_guide/engagement_tools/canvas/ideas_and_strategies/pre_post_launch_checklist#pre-and-post-launch-checklist)를 가이드로 삼아 사용 사례에 따라 이러한 영역을 세밀하게 조정하여 캔버스의 성공에 기여하세요. 
+
+## 새로운 API 엔드포인트: 사용자 별칭 업데이트
+
+[사용자 별칭 업데이트 엔드포인트를]({{site.baseurl}}/api/endpoints/user_data/post_users_alias_update/) 사용하여 기존 사용자 별칭을 업데이트합니다.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [웹 SDK 4.6.0-4.6.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#461)
+- [Android SDK 24.1.0-24.2.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2420)
+- [AppboyKit iOS SDK 4.5.3](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.5.3)
+- [Swift SDK 5.9.0-5.9.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#591)
+	- 최소 배포 대상을 iOS 11.0 및 tvOS 11.0으로 올립니다.
+	- Xcode 버전을 14.1(14B47b)로 올립니다.
+- [Flutter SDK 3.1.0](https://pub.dev/packages/braze_plugin/changelog)
+	- 네이티브 Android 브릿지는 Braze Android SDK 24.2.0을 사용합니다.
+	- 기본 iOS 브릿지는 Braze iOS SDK 5.9.0을 사용합니다.
+	- 최소 iOS 배포 대상은 11.0입니다.
+- [Cordova SDK 2.33.0](https://github.com/Appboy/appboy-cordova-sdk/blob/2.33.0/CHANGELOG.md#2330)
+	- 새로운 Braze Swift SDK(5.8.1)를 사용하도록 iOS 플러그인을 마이그레이션했습니다.
+	- iOS에서는 뉴스피드 UI가 더 이상 지원되지 않습니다.
diff --git a/_lang/ko/_help/release_notes/2023/3_7_23.md b/_lang/ko/_help/release_notes/2023/3_7_23.md
new file mode 100644
index 00000000000..587e162bffa
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/3_7_23.md
@@ -0,0 +1,131 @@
+---
+nav_title: 2023년 3월 7일
+page_order: 10
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 3월 7일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 3월 7일 출시
+
+## 원본 경험 캔버스 복제 지원 제거
+
+2023년 2월 28일부터는 더 이상 기존 캔버스 환경을 사용하여 캔버스를 만들거나 복제할 수 없습니다. Braze는 기존 캔버스 환경을 사용하는 고객은 캔버스 플로우로 전환할 것을 권장합니다. 캔버스를 더 잘 만들고 관리할 수 있는 개선된 편집 환경입니다. [캔버스를 캔버스 플로우에 복제하는]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/cloning_canvases/) 방법에 대해 자세히 알아보세요.
+
+## iOS용 라이브 액티비티(미리 체험하기)
+
+실시간 [활동]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/)은 잠금 화면에 표시되는 지속적인 대화형 알림으로, 실시간으로 상황을 파악할 수 있습니다. 실시간 활동은 잠금 화면에 표시되므로 알림을 놓치지 않고 확인할 수 있습니다. 영구적이므로 사용자가 휴대폰의 잠금을 해제하지 않아도 최신 콘텐츠를 표시할 수 있습니다.
+
+## 콘텐츠 카드용 카드 만들기
+
+이제 카드 생성 시점을 지정하여 Braze가 새 콘텐츠 카드 캠페인에 대한 오디언스 자격 및 개인화를 평가하는 시점을 선택할 수 있습니다.
+
+다음 옵션을 사용할 수 있습니다:
+
+- **캠페인 시작 시:** 콘텐츠 카드의 이전 기본 동작입니다. Braze는 캠페인이 시작될 때 잠재 고객 자격 및 개인화를 계산한 다음, 사용자가 앱을 열 때까지 카드를 생성하고 저장합니다.
+- **첫인상:** 사용자가 다음에 앱을 열면(즉, 새 세션을 시작하면) Braze는 사용자가 어떤 콘텐츠 카드를 받을 수 있는지 확인하고, 리퀴드 또는 커넥티드 콘텐츠와 같은 개인화를 템플릿화한 다음 카드를 생성합니다.
+
+자세한 내용은 [카드 만들기를]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/) 참조하세요.
+
+## 앱 내 메시지 드래그 앤 드롭 편집기의 스타일 재설정
+
+이제 인앱 메시지 드래그 앤 드롭 편집기에서 스타일을 변경한 후 기본 스타일로 빠르게 초기화할 수 있습니다. 자세한 내용은 [스타일을 기본값으로 재설정하기]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/#resetting-styles-to-default)를 참조하세요.
+
+## 링크 단축을 위한 사용자 지정 도메인
+
+또한 링크 단축을 사용하면 자체 도메인을 사용하여 단축 URL의 모양과 느낌을 맞춤화할 수 있으므로 일관된 브랜드 이미지를 표현하는 데 도움이 됩니다. [커스텀 도메인]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#custom-domains)을 구성한 후에는 하나 또는 여러 개의 SMS 구독 그룹에 할당할 수 있습니다.
+
+## Safari 모바일 웹 푸시
+
+Safari v16.4는 모바일 웹 푸시를 지원하므로 이제 iOS 및 iPadOS에서 푸시 알림을 통해 모바일 사용자의 참여를 다시 유도할 수 있습니다. [iOS 및 iPadOS용 Safari에서 웹 푸시를]({{site.baseurl}}/developer_guide/platform_integration_guides/web/push_notifications/safari_mobile_push/) 지원하는 방법에 대한 단계별 가이드는 전용 가이드를 참조하세요.
+
+## 사용자 업데이트 컴포넌트 사용 사례
+
+캔버스의 사용자 업데이트 컴포넌트를 사용하면 JSON 컴포저에서 사용자의 속성, 이벤트 및 구매를 업데이트할 수 있지만 이 기능을 최대한 활용하는 방법을 잘 모르시나요? 몇 가지 아이디어를 제공하기 위해 [세 가지 사용 사례 예시]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/user_update/#use-cases)를 추가했습니다.
+
+## 사용자 조회
+
+이 새 문서에서는 [사용자 조회를]({{site.baseurl}}/user_guide/engagement_tools/segments/user_lookup) 사용하여 작성기에서 직접 특정 사용자를 검색하여 필터와 세그먼트가 올바르게 설정되었는지 테스트하는 방법에 대해 설명합니다. 이는 예상대로 전송되지 않는 캠페인이나 캔버스 문제를 해결할 때도 유용합니다(예: 사용자가 메시지를 받아야 할 때 수신하지 못하는 경우).
+
+사용자 조회를 사용할 수 있는 경우는 다음과 같습니다.
+
+- 세그먼트 만들기
+- 캠페인 또는 Canvas 대상 설정
+- 오디언스 경로 단계 설정
+
+## 사용자 지정 데이터 차단 목록 또는 삭제
+
+이 새 문서에서는 [커스텀 데이터를 차단 목록에 추가하거나 삭제하여]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/blocklist_delete_custom_data/) 커스텀 데이터 개체를 폐기하는 방법에 대해 설명합니다.
+
+때때로 너무 많은 데이터 포인트를 소비하거나 마케팅 전략에 더 이상 유용하지 않거나 오류로 기록된 사용자 지정 속성, 사용자 지정 이벤트 또는 구매 이벤트를 식별할 수 있습니다. 이 데이터가 Braze로 전송되지 않도록 하려면 엔지니어링 팀이 앱이나 웹사이트의 백엔드에서 해당 데이터를 제거하는 작업을 하는 동안 사용자 지정 데이터 개체를 차단 목록에 추가할 수 있습니다.
+
+## 새로운 Braze 파트너십
+
+### Sisu Data - 비즈니스 인텔리전스
+
+[Sisu Data]({{site.baseurl}}/partners/data_and_infrastructure_agility/business_intelligence/sisu_data/)와 Braze의 통합을 통해 전체 캠페인 또는 캠페인 수준에서 측정기준(예: 열람율, 클릭률, 전환율 등)이 변화하는 이유와 가장 최적의 결과를 이끌어내는 요인을 파악할 수 있습니다. 이러한 세그먼트가 식별되면 Braze 사용자는 데이터 웨어하우스에서 결과물을 구체화하거나 Sisu에서 Braze로 직접 전송하여 사용자를 리타겟팅하고 재참여시킬 수 있습니다.
+
+### Loplat - 상황에 맞는 위치
+
+Braze와 [loplat]({{site.baseurl}}/partners/message_personalization/location/loplat/)의 통합을 통해 loplat의 위치 서비스(매장 POI 및 커스텀 지오펜스)를 사용하여 지리적 맥락 마케팅 캠페인을 트리거하고 오프라인 세분화를 사용하여 커스텀 이벤트를 생성할 수 있습니다. 사용자가 loplat X에서 설정한 타겟 위치를 방문하면, 캠페인과 위치 정보가 Braze로 즉시 전송됩니다.
+
+### ActionIQ - 고객 데이터 플랫폼
+
+Braze와 [ActionIQ의]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/actioniq/) 통합을 통해 브랜드는 ActionIQ 데이터를 Braze에 직접 동기화하고 매핑하여 광범위한 고객 데이터를 기반으로 탁월한 고객 경험을 제공할 수 있습니다. 통합을 통해 사용자는 다음을 수행할 수 있습니다:
+
+- 잠재 고객 세그먼트 또는 사용자 지정 속성을 ActionIQ에서 바로 Braze에 매핑하세요.
+- ActionIQ가 추적한 이벤트를 실시간으로 Braze에 전달하여 개인화된 타겟팅 캠페인을 트리거합니다.
+
+### Komo - 동적 콘텐츠
+
+Braze와 [Komo]({{site.baseurl}}/partners/message_personalization/dynamic_content/komo/)의 통합으로 Komo인게이지먼트 허브를 통해 퍼스트파티 및 제로파티 데이터를 수집할 수 있습니다. 이러한 허브는 대화형 콘텐츠와 게임화 기능을 제공하는 동적 마이크로사이트입니다. 이러한 허브에서 수집된 사용자 데이터는 Braze API로 전송됩니다.
+
+- Komo에서 Braze로 수집한 퍼스트 및 제로파티 사용자 데이터를 실시간으로 수집합니다
+- 설문조사, 투표, 퀴즈 질문에 답할 때 시장 조사 및 사용자 선호도 데이터를 수집합니다
+- 사용자가 계속해서 참여하고 자신에 대한 더 많은 데이터를 공유함에 따라 시간이 지남에 따라 Braze에서 점진적으로 고객 프로필을 구축합니다.
+- Braze를 통해 전송되는 트랜잭션 이메일의 모양과 느낌을 표준화하세요
+
+### Phrase - 현지화
+
+[Phrase]({{site.baseurl}}/partners/message_personalization/localization/phrase/)와 Braze 통합을 사용하면 Braze 인터페이스에서 나가지 않고도 이메일 템플릿과 콘텐츠 블록을 번역할 수 있습니다. Braze용 Phrase TMS 통합을 사용하면 원활한 현지화를 통해 고객 참여를 높이고 새로운 시장으로의 성장을 촉진할 수 있습니다.
+
+### Nift - 로열티
+
+Braze와 [Nift]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/nift/)의 통합을 통해 고객 생애주기의 중요한 순간에 Nift 선물이 포함된 "감사" 메시지를 자동으로 트리거하고 어떤 고객이 선물을 사용했는지 파악할 수 있습니다. Nift 기프트 카드는 Nift의 매치메이킹 기술에 의존하는 브랜드가 제공하는 제품과 서비스에 액세스하여 대규모로 비용 효율적으로 신규 고객을 확보하는 데 사용할 수 있습니다.
+
+### Sageflo - 메시지 템플릿
+
+Braze와 [Sageflo의]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/sageflo/) 통합으로 현지 팀은 Braze와의 API 통합을 통해 마케팅에서 승인한 템플릿, 이미지 및 대상 세그먼트를 사용하여 자체 이메일을 쉽게 보낼 수 있습니다.
+
+### Airbyte - 워크플로 자동화
+
+Braze와 [Airbyte의]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/airbyte/) 통합을 통해 사용자는 모든 애플리케이션과 데이터베이스를 중앙 웨어하우스에 연결하여 Braze 데이터를 수집하고 분석할 수 있는 데이터 파이프라인을 만들 수 있습니다. 중앙 데이터 웨어하우스에 데이터가 수집되면 데이터 팀은 선호하는 비즈니스 인텔리전스 툴을 사용하여 Braze 데이터를 효과적으로 탐색할 수 있습니다.
+
+### GrowthLoop - 워크플로 자동화
+
+Braze와 [GrowthLoop]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/growthloop/)의 통합을 통해 데이터 웨어하우스에서 직접 고객 데이터를 세분화하여 Braze로 전송할 수 있으므로 사용자는 단일 데이터 소스와 함께 Braze의 심층적인 기능 세트를 최적화할 수 있습니다. 고객 세분화 및 활성화를 위한 마케팅 노력을 간소화하여 Braze로 전송된 타겟팅 캠페인의 세분화, 실행, 테스트 및 결과 측정에 걸리는 시간을 단축합니다.
+
+### Mozart Data - 워크플로 자동화
+
+Braze와 [Mozart Data의]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/mozart_data/) 통합을 통해 다음을 수행할 수 있습니다:
+
+- Fivetran을 사용하여 Braze 데이터를 Snowflake로 가져오기
+- Braze 데이터를 다른 애플리케이션 데이터와 결합하여 트랜스폼을 생성하고 사용자 행동을 효과적으로 분석하세요
+- Snowflake에서 Braze로 데이터를 가져와 새로운 고객 참여 기회를 창출하세요
+- Braze 데이터를 다른 애플리케이션 데이터와 결합하여 사용자 행동에 대한 보다 전체적인 이해를 얻으세요
+- 비즈니스 인텔리전스 도구와 통합하여 Snowflake에 저장된 데이터를 더욱 자세히 살펴보세요
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Swift SDK 5.10.0-5.11.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+- [웹 SDK 4.6.2-4.6.3](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- [세그먼트 iOS SDK 4.6.1](https://github.com/Appboy/appboy-segment-ios/releases)
+- [AppboyKit iOS SDK 4.5.4](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.5.4)
+- [React Native SDK 2.0.0-2.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+- [Xamarin SDK 1.27.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
+- [ExpoPlugin 1.0.0-1.1.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+   - 이제 Braze React Native SDK v2.1.0 이상이 필요합니다.
+   - Expo 48과의 호환성을 위해 기본 Kotlin 버전을 1.8.10으로 업데이트합니다. 이 값은 `app.json`의 `android.kotlinVersion` 속성정보에 의해 재정의됩니다.
+- [Roku SDK 0.1.3](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md)
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2023/4_4_23.md b/_lang/ko/_help/release_notes/2023/4_4_23.md
new file mode 100644
index 00000000000..d101e4c8dc0
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/4_4_23.md
@@ -0,0 +1,68 @@
+---
+nav_title: 2023년 4월 4일
+page_order: 9
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 4월 4일 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 4월 4일 출시
+
+## 설명서 breadcrumbs 
+사이트의 각 기사 상단에 있는 브레드크럼을 통해 현재 위치를 확인할 수 있다는 것을 Braze 문서 사이트에서 알 수 있습니다. 이 역시 탐색에 도움이 되는 옵션들입니다!
+
+![사용자 가이드 > 채널별 메시지 작성 > 인앱 메시지 > 템플릿 > 간단한 설문조사로 이동하는 이동 경로][1]{: style="max-width:55%"}
+
+## 브라우저에서 카탈로그 생성
+카탈로그를 사용하여 Liquid를 통해 Braze 캠페인에서 비사용자 데이터를 참조할 수 있습니다. Braze는 이제 CSV를 가져오는 대신 브라우저에서 직접 카탈로그를 생성할 수 있도록 합니다. 자세한 내용은 [카탈로그 만들기]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog)을 참조하십시오.
+
+## 쿼리 빌더에서 커스텀 SQL
+쿼리 빌더를 사용하면 Snowflake에서 Braze 데이터를 사용하여 보고서를 생성할 수 있습니다. 이제 [커스텀 SQL]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/custom_sql)을 사용하여 새로운 인사이트를 얻을 수 있습니다.
+
+{% alert important %}
+SQL 편집기는 초기 액세스 중입니다. 미리 맛보기에 참여하고 싶다면 고객 성공 매니저에게 문의하세요.
+{% endalert %}
+
+## 기능 flag FAQ
+[피처 플래그에 대한 자주 묻는 질문]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/faq)을 정리했습니다.
+
+## 메시지 extras Liquid 태그 for 커런츠
+[`message_extras` Liquid 태그]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras)를 사용하여 연결된 콘텐츠, 커스텀 속성(예: 언어, 국가) 및 캔버스 입력 속성의 동적 데이터로 전송 이벤트에 주석을 달 수 있습니다. 이 Liquid 태그는 커런츠의 해당 전송 이벤트에 키-값 페어를 추가합니다.
+
+{% alert important %}
+이 Liquid 태그는 현재 이메일, SMS 및 푸시 전송 이벤트에 대한 베타 버전입니다. 베타에 참여하고 싶으시면 Braze 고객 성공 매니저에게 문의하세요.
+{% endalert %}
+
+## 새로운 커런츠 이벤트: users_campaigns_abort 및 users_canvas_abort
+커런츠 용어집에 두 개의 새로운 이벤트가 추가되었습니다: [캔버스 중단 메시지 이벤트]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events#canvas-abort-message-events) 및 [캠페인 중단 메시지 이벤트]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events#campaign-abort-message-events).
+
+## 새로운 API 엔드포인트: 카탈로그
+[카탈로그 항목 업데이트]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item/) 및 [카탈로그 항목 업데이트]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items/) 엔드포인트를 사용하여 카탈로그의 항목 또는 여러 항목을 업데이트하십시오.
+
+## Shopify 히스토리컬 백필
+[Shopify Historical Backfill](https://www.braze.com/docs/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_backfill/)은 Braze가 Shopify 통합 연결 이전 90일 동안의 모든 고객, 주문 및 구매 이벤트를 가져올 수 있도록 합니다.
+
+## WhatsApp
+WhatsApp은 전 세계적으로 사용되는 인기 있는 개인 간 메시징 플랫폼으로, 비즈니스를 위한 대화 기반 메시징을 제공합니다. [WhatsApp 메시징 채널]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp)은 캠페인, 옵트인 및 옵트아웃, 빠른 응답 등을 통해 WhatsApp 플랫폼에서 사용자를 직접 참여시키는 방법을 제공합니다.
+
+### WhatsApp API 객체
+Braze의 WhatsApp 지원의 일환으로, `whats_app` 객체를 사용하여 [메시징 엔드포인트]({{site.baseurl}}/api/endpoints/messaging)를 통해 WhatsApp 메시지를 수정하거나 생성할 수 있습니다. 전체 사양은 [`whats_app` 객체 설명서]({{site.baseurl}}/api/objects_filters/messaging/whats_app_object)를 참조하십시오.
+
+## 새로운 Braze 파트너십
+
+### Merkury - 분석
+Braze와 [Merkury]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/merkury) 통합을 통해 `MerkuryID`을 활용하여 Braze 고객의 사이트 방문자 인식률을 높일 수 있습니다.
+
+## SDK 업데이트
+
+다음 소프트웨어 개발 키트 업데이트가 출시되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Cordova SDK 3.0.0](https://github.com/Appboy/appboy-cordova-sdk/blob/3.0.0/CHANGELOG.md)
+- [Swift SDK 5.11.1-5.13.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+- [Android SDK 24.3.0](https://github.com/Appboy/appboy-android-sdk/blob/master/CHANGELOG.md)
+- [React Native SDK v3.0.0-v4.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+- [Flutter SDK 4.1.0](https://pub.dev/packages/braze_plugin/changelog)
+- [Expo 플러그인 v1.1.1](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+- [웹 SDK v4.7.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+
+[1]: {% image_buster /assets/img/doc-breadcrumbs.png %} 
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2023/5_2_23.md b/_lang/ko/_help/release_notes/2023/5_2_23.md
new file mode 100644
index 00000000000..62188f5d967
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/5_2_23.md
@@ -0,0 +1,64 @@
+---
+nav_title: 2023년 5월 2일
+page_order: 8
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 5월 2일에 대한 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 5월 2일 출시
+
+## 새롭게 디자인된 Braze UI/UX
+
+_2023년 5월 16일부터 일반 사용 가능_
+
+새롭게 디자인된 UI/UX 및 정보 아키텍처로 시간을 절약하고 필요한 정보를 정확하게 찾아보세요. 플랫폼 전반을 빠르게 탐색하고, 작업을 완료하고, 새로운 기능을 쉽게 발견하세요. 여러분과 여러분의 팀이 보다 쉽게 전환할 수 있도록 전용 [탐색 가이드를]({{site.baseurl}}/navigation) 통해 변경된 사항과 향후 예상되는 사항을 알아보세요.
+
+## 쿼리 작성기
+
+[쿼리 빌더]({{site.baseurl}}/user_guide/data_and_analytics/query_builder)를 사용하면 Snowflake에서 Braze 데이터를 사용하여 보고서를 생성할 수 있습니다. 쿼리 작성기에는 미리 작성된 SQL 쿼리 템플릿이 제공되어 쉽게 시작할 수 있으며, 사용자 지정 SQL 쿼리를 직접 작성하여 더 많은 인사이트를 얻을 수도 있습니다.
+
+## 캔버스 버전 기록
+
+[버전 기록]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/canvas_version_history/)을 통해 캔버스의 이전 버전에 대한 캔버스 분석 및 사용자 여정을 보고 액세스할 수 있습니다. 캔버스 버전 기록을 참조하면 캔버스의 진화 과정을 기록하는 데 특히 유용할 수 있습니다.
+
+## SQL 세그먼트의 증분 새로 고침
+
+이제 최근 2일 분량의 데이터만 새로 고치는 증분 새로 고침을 사용하는 [SQL 세그먼트 확장]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/)을 만들 수 있습니다. 이렇게 하면 비용 효율성이 더 높고 세그먼트 멤버십이 새로 고쳐질 때마다 SQL 세그먼트 크레딧을 더 적게 사용할 수 있습니다. 전체 새로 고침 연장과 달리 증분 새로 고침 연장은 멤버십을 매일 자동으로 갱신하도록 설정할 수 있습니다.
+
+## 이메일 전달 가능성 센터
+
+[전달 가능성 센터]({{site.baseurl}}/user_guide/data_and_analytics/analytics/deliverability_center#deliverability-center)는 Gmail 포스트마스터 도구를 사용하여 전송된 이메일의 데이터를 추적하고 전송 도메인에 대한 데이터를 수집할 수 있도록 지원하여 이메일 성능에 대한 더 많은 인사이트를 제공합니다.
+
+{% alert important %}
+전달 가능성 센터는 현재 얼리 액세스 중입니다. 얼리 액세스에 참여하려면 Braze 고객 성공 매니저에게 문의하세요.
+{% endalert %}
+
+## 카탈로그 제한 사항 업데이트
+
+2023년 5월 1일부로 [카탈로그 저장 한도]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog/#limits)에 대한 업데이트가 있었습니다. 카탈로그 저장소 업그레이드를 요청하려면 Braze 계정 관리자에게 문의하세요.
+
+## 새로운 API 및 SDK 엔드포인트 문서
+
+Braze는 "클러스터"라고 부르는 대시보드, SDK 및 REST 엔드포인트에 대한 다양한 인스턴스를 관리합니다. 사용 가능한 Braze 인스턴스에 대한 대시보드 URL, API 엔드포인트 및 SDK 엔드포인트 목록을 보려면 [API 및]({{site.baseurl}}/user_guide/administrative/access_braze/sdk_endpoints) SDK 엔드포인트를 확인하세요.
+
+## Liquid FAQ
+
+[Liquid에 대해 자주 묻는 질문에 대한]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/faq/) 답변을 준비했습니다. 
+
+## iOS SDK 지원 중단 - Swift
+
+Braze의 레거시 iOS SDK는 새로운 Swift SDK를 위해 더 이상 사용되지 않습니다. 이를 통해 향상된 성능, 새로운 기능, [새로운 설명서](https://www.braze.com/docs/developer_guide/platform_integration_guides/swift/initial_sdk_setup/overview)를 포함한 많은 개선 사항이 제공됩니다!
+
+업그레이드하고 싶으신가요? 자세한 내용은 [마이그레이션 가이드를](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/appboy-migration-guide/) 확인하세요.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [React Native SDK v4.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+- [Android SDK 25.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [Swift SDK 5.14.0-6.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#600)
+- [Flutter SDK 5.0.0](https://pub.dev/packages/braze_plugin/changelog)
+- [Unity 4.0.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
+- [세그먼트 Kotlin 1.3.0](https://github.com/braze-inc/braze-segment-kotlin/blob/main/CHANGELOG.md)
diff --git a/_lang/ko/_help/release_notes/2023/5_30_23.md b/_lang/ko/_help/release_notes/2023/5_30_23.md
new file mode 100644
index 00000000000..ed31ccc012a
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/5_30_23.md
@@ -0,0 +1,102 @@
+---
+nav_title: 2023년 5월 30일
+page_order: 7
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 5월 30일에 대한 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 5월 30일 출시
+
+## 새롭게 디자인된 Braze 내비게이션
+
+콘텐츠를 더 빠르고 효율적으로 만들고 액세스할 수 있도록 Braze 탐색 기능을 업데이트했습니다. 이제 기능은 Braze에서 마케터의 워크플로에 친숙하고 관련성이 높은 직관적인 카테고리로 구성됩니다. 앞으로 몇 달 동안 이전 탐색 경험과 새로운 탐색 간에 전환할 수 있습니다. 변경된 사항에 대한 자세한 내용은 [Braze 탐색]({{site.baseurl}}/navigation)을 참조하세요.
+
+## 신규 커런츠 이벤트
+
+최근 다음과 같은 WhatsApp 전류 이벤트가 출시되어 [메시지 참여 이벤트]({{site.baseurl}}/user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events) 용어집에 추가되었습니다:
+
+메시지 중단 이벤트:
+- `users.messages.whatsapp.Send`
+- `users.messages.whatsapp.Abort`
+- `users.messages.whatsapp.Delivery`
+- `users.messages.whatsapp.Failure`
+- `users.messages.whatsapp.Read`
+- `users.messages.whatsapp.InboundReceive`
+
+## 브라우저 내 카탈로그 편집 및 카탈로그 선택 
+
+이제 카탈로그는 브라우저 내 편집 및 [선택]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections)을 지원합니다. 선택 항목은 캠페인의 각 사용자에 대한 메시지를 맞춤 설정하는 데 사용할 수 있는 데이터 그룹입니다. [카탈로그를]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalog/) 생성한 후에는 Braze 캠페인에 선택 항목을 통합하여 이 데이터를 추가로 참조할 수 있습니다.
+
+## message_extras Liquid 태그를 공유하는 커런츠 및 Snowflake 데이터
+
+[`message_extras` Liquid 태그]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras/)를 사용하면 연결된 콘텐츠, 카탈로그, 커스텀 속성(예: 언어, 국가), 캔버스 항목 속성 또는 기타 데이터 소스의 동적 데이터로 보내기 이벤트에 주석을 달고 추가 데이터를 커런츠 또는 Snowflake 데이터 공유로 다시 보낼 수 있습니다.
+
+## 새로운 Braze 파트너십
+
+### Tangerine - 현지화
+Braze와 [Tangerine]({{site.baseurl}}/partners/message_personalization/location/tangerine/)의 통합을 통해 Snowflake보안 데이터 공유를 통해 Braze의 캠페인 및 노출 횟수 데이터를 스토어360에 통합할 수 있습니다. 이제 브랜드는 이러한 캠페인이 실제 매장 방문 및 매장 내 참여에 미치는 영향을 측정할 수 있습니다.
+
+### Personalize.AI \- 동적 콘텐츠
+Braze와 [Personalize.AI]({{site.baseurl}}/partners/message_personalization/dynamic_content/personalize/) 통합을 통해 Personalize.AI 에서 메시지 개인화 및 타겟팅을 위해 Braze 플랫폼으로 데이터를 내보낼 수 있습니다.
+
+### Regal - 메시징
+[Regal]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/regal/)과 Braze를 통합하면 모든 고객 터치포인트에서 보다 일관되고 개인화된 경험을 제공할 수 있습니다.
+- Regal과의 전화 대화 내용을 바탕으로 적절한 차선책 이메일 또는 Braze의 푸시 알림을 보내세요.
+- 고가치 고객이 Braze에서 보낸 마케팅 이메일을 클릭했지만 전환하지 않으면 Regal에서 통화를 트리거하세요.
+
+### Sendbird - 메시징
+Braze와 [Sendbird의]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/sendbird) 통합을 통해 Braze 사용자는 다음을 수행할 수 있습니다:
+- Braze의 세분화 및 트리거링 기능을 활용하여 개인화된 인앱 알림을 시작하세요.
+- Sendbird 알림 플랫폼에서 맞춤 인앱 알림을 생성하고, 이를 앱 환경 내에서 전달하여 사용자 인게이지먼트를 높일 수 있습니다.
+
+### 새로운 관련성 - 동적 콘텐츠
+Braze와 [Fresh Relevance]({{site.baseurl}}/partners/message_personalization/dynamic_content/fresh_relevance/) 통합을 통해 트리거 이메일에 고객이 검색한 제품 또는 동일한 카테고리 내의 품목을 기반으로 한 제품 추천, 가격 인하, 재고 있음, 다단계 검색, 장바구니 이탈 메시지 등의 고급 트리거 이메일 캠페인 전송 등 개인화된 콘텐츠를 포함할 수 있습니다!
+
+### Smartling - 현지화
+Braze와 [Smartling]({{site.baseurl}}/partners/message_personalization/localization/smartling/)의 통합을 통해 이메일 템플릿과 콘텐츠 블록을 번역할 수 있습니다. 스마트링은 번역 중 언어 전문가에게 시각적 컨텍스트의 이점을 제공하여 오류를 줄이고 품질을 유지합니다.
+
+### SalesWings - 분석
+Braze와 [SalesWings]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/saleswings#saleswings)의 통합을 통해 두 플랫폼에서 데이터를 유연하게 동기화하여 잠재 고객 스코어링 및 잠재 고객 등급 지정 기능을 통해 잠재 고객을 검증할 수 있습니다.
+
+### Kognitiv Inspire - 로열티
+Braze와 [Kognitiv]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/kognitiv/)의 통합을 통해 로열티 전략을 구현하고 평가할 수 있으며, 혁신적인 기능과 맞춤형 회원 커뮤니케이션을 제공하여 프로그램 효과를 높일 수 있습니다.
+
+### OneTrust - 데이터 개인 정보 보호
+Braze와 [OneTrust]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_privacy/onetrust/)의 통합을 통해 OneTrust 워크플로 빌더를 사용하여 제품에 대한 보안 워크플로를 만들 수 있습니다.
+
+### Stylitics - 동적 콘텐츠
+Braze와 [Stylitics]({{site.baseurl}}/partners/message_personalization/dynamic_content/stylitics/)를 통합하면 매력적이고 관련성 높은 번들 콘텐츠로 기존 이메일 캠페인을 강화하여 개인화된 고객 경험을 만들 수 있습니다.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Swift SDK 6.1.0-6.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#620)
+- [웹 SDK 4.7.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#471)
+- [React Native SDK 5.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#500)
+	- 네이티브 iOS 브릿지를 Braze Swift SDK 5.13.0에서 6.2.0으로 업데이트합니다.
+	- 버전 2.0.0부터 운영되지 않는 `setSDKFlavor` 및 `setMetadata`를 제거합니다.
+	- iOS에서는 SDK 초기화 시 `Braze.Configuration` 오브젝트를 사용하여 이러한 필드를 설정해야 합니다.
+	- Android에서는 braze.xml 파일을 통해 이러한 필드를 설정해야 합니다.
+- [Cordova SDK 4.0.0-5.0.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md#500)
+	- **Cordova SDK 4.0.0**
+		- Appboy 인스턴스의 이름을 Braze로 변경했습니다.
+			- 프로젝트가 새 명명 규칙으로 제대로 마이그레이션되었는지 확인하려면 프로젝트에서 다음 인스턴스를 찾아서 교체하세요.
+				- 플러그인 이름이 `cordova-plonugin-appboy` 에서 `cordova-plugin-braze` 으로 변경되었습니다.
+					- Cordova 플러그인을 실행하고 `cordova-plugin-appboy`를 제거한 다음 [README](https://github.com/braze-inc/braze-cordova-sdk/blob/master/README.md)의 지침에 따라 플러그인을 다시 추가하세요.
+				- 이 GitHub 리포지토리는 https://github.com/braze-inc/braze-cordova-sdk URL로 이전되었습니다.
+				- 프로젝트의 config.xml 파일에서 각 구성 속성정보 키에 대해 com.appboy의 인스턴스 이름을 com.braze로 바꿉니다.
+				- JavaScript 클래스 인터페이스 `AppboyPlugin` 의 이름이 `BrazePlugin` 으로 변경되었습니다.
+		- Braze Android SDK 25.0.0으로 업데이트되었습니다.
+		- Braze Swift SDK 5.13.0으로 업데이트되었습니다.
+			- 이 업데이트는 콘텐츠 카드에 대한 클릭을 기록할 때 버전 2.33.0에 도입된 iOS 동작을 수정합니다. 이제 `logContentCardClicked`를 호출하면 클릭 이벤트를 전송하고 연결된 URL 필드로 리디렉션하는 대신 측정기준에 대한 클릭 이벤트만 전송합니다.
+	- **Cordova SDK 5.0.0**
+		- 콜백 매개변수를 사용하는 대신 프로미스를 반환하도록 기능 플래그 메서드를 업데이트했습니다.
+			- `getAllFeatureFlags()`
+			- `getFeatureFlag(id)`
+			- `getFeatureFlagBooleanProperty(id, key)`
+			- `getFeatureFlagStringProperty(id, key)`
+			- `getFeatureFlagNumberProperty(id, key)`
+- [언리얼 SDK 2.5.0](https://github.com/braze-inc/braze-unreal-sdk/blob/master/CHANGELOG.md#250)
+- [Unity SDK 4.1.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md#410)
diff --git a/_lang/ko/_help/release_notes/2023/6_27_23.md b/_lang/ko/_help/release_notes/2023/6_27_23.md
new file mode 100644
index 00000000000..21a007e9895
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/6_27_23.md
@@ -0,0 +1,49 @@
+---
+nav_title: 2023년 6월 27일
+page_order: 6
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 6월 27일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 6월 27일 출시
+
+## 끌어서 놓기 이메일 환경설정 센터
+
+환경설정 센터를 설정하면 사용자가 이메일 메시징에 대한 알림 환경설정을 편집하고 관리할 수 있는 원스톱 상점이 제공됩니다. 이제 드래그 앤 드롭 편집기를 사용하여 특정 유형의 커뮤니케이션을 수신하는 사용자를 관리하는 데 도움이 되는 환경설정 센터를 만들고 사용자 지정할 수 있습니다. 자세한 내용은 [드래그 앤 드롭으로 이메일 환경설정 센터 만들기]({{site.baseurl}}/user_guide/message_building_by_channel/email/preference_center/dnd_preference_center/)를 참조하세요.
+
+## 캔버스에 초안 저장
+
+캔버스를 만들고 실행할 때 활성 캔버스를 편집하고 초안으로 저장하여 다른 캔버스를 실행하기 전에 변경 사항을 시험해 볼 수도 있습니다. 대규모 변경이 필요한 활성 캔버스가 있는 경우 이 기능을 사용하여 이러한 편집에 대해 별도의 초안을 만들 수 있습니다. 자세한 내용은 [캔버스에 초안 저장하기]({{site.baseurl}}/save_as_draft)를 참조하세요.
+
+## 한 번만 참가할 수 있는 우승 경로
+
+사용자가 한 번만 입장할 수 있는 캔버스에서 [위닝 경로]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/winning_path/#one-time-entry)를 사용할 때 이제 지연 그룹이 자동으로 포함됩니다. 즉, 더 이상 실험 경로에서 위닝 경로를 사용하기 위해 일회성 항목 캔버스에 대한 해결 방법을 수행하지 않아도 됩니다.
+
+## 콘텐츠 카드 사용량 제한 새로 고침
+
+2023년 6월 14일 이후에 가입한 고객의 경우, 성능 저하 및 오류를 방지하기 위해 `requestContentCardsRefresh()` 수동 호출의 기본 사용량 제한은 기기당 10분당 3회로 설정됩니다. 콘텐츠 카드 새로 고침에 대한 자세한 내용은 [iOS]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/integration#refreshing-content-cards), [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/content_cards/refreshing_the_feed) 및 [웹용]({{site.baseurl}}/developer_guide/platform_integration_guides/web/content_cards/refreshing_the_feed) 각 문서를 참조하세요.
+
+## Facebook에 오디언스 동기화
+
+[Facebook에 오디언스 동기화]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync/)를 사용하는 경우, 2023년 7월부터 Meta는 이 새로운 계정 유형을 채택하는 데 관심이 있는 소규모 비즈니스에 메타 업무용 계정을 출시할 예정이라는 점을 알아두세요. Braze와 통합된 비즈니스 계정이 있는 경우, 이 구현을 유지하고 활성 캔버스를 방해하지 않으려면 비즈니스 계정으로 [Facebook 파트너 페이지]({{site.baseurl}}/partners/canvas_steps/facebook_audience_sync#step-1-connect-to-facebook)에 연결을 끊었다가 다시 연결해야 합니다.
+
+## Databricks를 위한 클라우드 데이터 수집
+
+Databricks용 Braze 클라우드 데이터 수집을 통해 고객은 사용자 데이터(속성, 이벤트, 구매)는 물론 사용자 삭제를 Databricks에서 Braze로 직접 동기화할 수 있습니다. Braze에 동기화되면 이 데이터는 Braze 플랫폼의 다른 데이터와 마찬가지로 사용할 수 있습니다. 이 기능은 [클라우드 데이터 수집]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/) 제품의 확장 기능이며 현재 얼리 액세스 중입니다.
+
+## 개인정보 보호 포털
+
+새로운 [Braze 개인정보 보호 포털은]({{site.baseurl}}/user_guide/privacy_portal) 고객 데이터를 잘 관리하고, 비즈니스와 관련된 데이터 보호 규칙을 준수하기 위한 조치를 취할 수 있도록 Braze가 어떻게 도움을 줄 수 있는지에 대한 유용한 정보를 제공합니다. 당사는 귀하가 관련 데이터 보호 법률 및 규정을 준수하여 Braze 서비스를 사용하는 데 도움이 될 수 있는 정보와 문서 링크를 모았습니다.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Android SDK 26.0.0-26.1.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2610)
+	- {% raw %}`BrazeConfig.setIsHtmlInAppMessageHtmlLinkTargetEnabled()` 또는 `braze.xml` 에 `<bool name="com_braze_html_in_app_message_enable_html_link_target">true</bool>`를 추가하여 HTML 인앱 메시지에 대한 링크 대상 동작을 구성할 수 있는 기능이 추가되었습니다. 기본값은 활성화입니다.{% endraw %}
+		- {% raw %}이 기능을 활성화하면 링크 대상이 설정된 인앱 메시지의 링크(예: `<a HREF="https://www.braze.com" target="_blank">Please Read</a>`)는 브라우저에서 링크가 열리지만 인앱 메시지는 닫히지 않습니다.{% endraw %}
+- [웹 SDK 4.7.2-4.8.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#480)
+- [Swift SDK 6.3.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#630)
+- [Unity SDK 4.1.1](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md#411)
+- [React Native SDK 5.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#510)
diff --git a/_lang/ko/_help/release_notes/2023/7_25_23.md b/_lang/ko/_help/release_notes/2023/7_25_23.md
new file mode 100644
index 00000000000..158b5169b41
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/7_25_23.md
@@ -0,0 +1,48 @@
+---
+nav_title: 2023년 7월 25일
+page_order: 5
+noindex: true
+page_type: update
+description: "이 문서에는 07/25/23에 대한 릴리스 노트가 포함되어 있습니다."
+ 
+---
+# 2023년 7월 25일 출시
+
+## 캔버스 승인 
+새로운 캔버스 승인 워크플로 설정은 새 캔버스를 시작하기 전에 검토 프로세스를 추가합니다. 이 기능은 기본적으로 꺼져 있으므로 사용자가 구현을 제어할 수 있습니다. [캔버스 승인 및 권한]({{site.baseurl}}/user_guide/engagement_tools/canvas/managing_canvases/canvas_approval/)에서 이 워크플로를 활성화하는 방법에 대한 자세한 내용을 살펴보세요.
+ 
+## 캔버스의 피처 플래그
+기능 플래그를 사용하면 사용자 기반의 여러 섹션에 대해 기능을 끄고 켜서 새로운 기능에 대한 가설을 실험하고 확인할 수 있습니다. 캔버스의 새로운 피처 플래그 구성 요소를 사용하면 사용자의 피처 플래그가 켜져 있는지 또는 꺼져 있는지에 따라 캔버스에서 오디언스를 세분화할 수 있습니다. 또한 실험 경로를 사용하면 서로 다른 메시지 또는 경로를 테스트하고 가장 효과적인 경로를 결정하여 이러한 전환을 최적화할 수 있습니다. 피처 플래그에 대한 일반적인 정보는 피처 플래그 [개요]({{site.baseurl}}/developer_guide/platform_wide/feature_flags/about/)를 참조하거나 [캔버스에서 피처 플래그를 사용하는 방법]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/feature_flags/)에 대해 자세히 알아보세요.
+
+## 세그먼트 관리 문서
+새로운 [세그먼트 관리하기]({{site.baseurl}}/user_guide/engagement_tools/segments/managing_segments/) 문서에서는 세그먼트 목록 필터링, 세그먼트 만들기, 세그먼트 편집 등 세그먼트를 구성하기 위해 수행할 수 있는 작업에 대해 설명합니다.
+ 
+## 행 컴포넌트 콘텐츠 블록
+이제 행 컴포넌트를 콘텐츠 블록으로 저장하여 캔버스의 모든 이메일 캠페인과 이메일 메시지에서 사용할 수 있습니다. 콘텐츠 블록 끌어서 놓기에 대한 자세한 내용은 [콘텐츠 블록을]({{site.baseurl}}/user_guide/message_building_by_channel/email/drag_and_drop/dnd_content_blocks/) 참조하세요.
+
+## Sage AI
+Braze의 Sage AI는 창의성, 개인화 및 인게이지먼트 전략 최적화를 위한 진입 장벽을 낮춰주는 접근하기 쉽고 사용하기 쉬운 도구 모음을 제공합니다. Sage AI 기능 및 성능에 대한 자세한 내용은 [설명서]({{site.baseurl}}/user_guide/sage_ai)에서 확인하세요.
+
+## 전화번호로 사용자 프로필 업데이트하기
+[`/users/track`]({{site.baseurl}}/api/endpoints/user_data/post_user_track) 엔드포인트를 사용하면 전화번호를 사용하여 고객 프로필을 업데이트할 수 있습니다. 
+
+{% alert important %}
+이 기능은 현재 얼리 액세스 중입니다. 얼리 액세스에 참여하려면 Braze 계정 매니저에게 문의하세요.
+{% endalert %}
+
+## 이메일 프리헤더 뒤 공백 
+새로운 **프리헤더 뒤에 공백 추가** 확인란은 이메일 프리헤더에 있는 이메일 본문의 텍스트 또는 HTML을 숨깁니다. 이메일 헤더 추가에 대한 자세한 내용은 [이메일 만들기]({{site.baseurl}}/user_guide/message_building_by_channel/email/html_editor/creating_an_email_campaign/#step-3-compose-your-email)에서 확인하세요.
+
+## SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Android SDK 26.2.0-26.3.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2620) 
+- [Swift SDK 6.3.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#631)
+- [웹 SDK 4.8.1-4.8.3](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#481)
+- [Flutter SDK 6.0.0](https://github.com/braze-inc/braze-flutter-sdk/blob/master/CHANGELOG.md#600)
+    - 네이티브 Android 브릿지를 Braze Android SDK 25.0.0에서 26.1.0으로 업데이트합니다.
+- [React Native SDK 5.2.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#520)
+- [Roku SDK 1.0.0](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md#100)
+- [Unity 4.2.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md#420)
+    - Braze Android SDK 26.2.0을 사용하도록 Android 플러그인을 업데이트했습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2023/8_22_23.md b/_lang/ko/_help/release_notes/2023/8_22_23.md
new file mode 100644
index 00000000000..91f3b277393
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/8_22_23.md
@@ -0,0 +1,77 @@
+---
+nav_title: 2023년 8월 22일
+page_order: 4
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 8월 22일 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 8월 22일 출시
+
+## Shopify 카탈로그 
+
+Shopify 카탈로그를 사용하면 Shopify 스토어에서 제품을 Braze 카탈로그로 가져올 수 있으며, 이 과정을 자동화하여 메시지의 더 깊은 개인화를 위한 제품 데이터를 가져올 수 있습니다. 유기한 장바구니, 주문 확인 등을 최신 제품 세부 정보 및 정보로 풍부하게 할 수 있습니다.
+
+## 이메일로 사용자 병합하기
+
+이제 [이메일로 사용자를 병합]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/#merging-users-by-email)할 수 있으며 `/users/merge` 엔드포인트를 사용합니다. 
+
+{% alert important %}
+이메일로 사용자를 병합하고 식별자가 일치하지 않는 `/users/merge`를 사용하는 것은 현재 초기 액세스 중입니다. 초기 액세스에 참여하고 싶으시면 Braze 계정 매니저에게 문의하세요.
+{% endalert %}
+
+## WhatsApp 모범 사례
+
+WhatsApp 메시지를 보내기 전에 제안된 [모범 사례]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/whatsapp_best_practices/)를 참조하여 높은 전화 품질 등급을 유지하고, 차단 및 보고를 피하며, 사용자를 옵트인 및 옵트아웃할 수 있습니다.
+
+## 도메인 평판
+
+전달 가능성 센터에서 이제 [도메인 평판]({{site.baseurl}}/user_guide/data_and_analytics/analytics/deliverability_center#domain-reputation)을(를) 확인하고 모니터링하여 스팸 폴더로 필터링되는 것을 방지할 수 있습니다.
+
+## 사용자 정의 가이드 
+
+개발자 포털의 재구성을 소개합니다. 이제 [콘텐츠 카드]({{site.baseurl}}/developer_guide/customization_guides/content_cards)부터 시작하는 SDK의 사용자 정의 옵션이 전용 사용자 정의 가이드로 통합되었습니다. 이 변경 사항은 세부 지침에 대한 액세스를 간소화하여 특정 요구 사항에 맞게 경험을 조정하기 쉽게 만듭니다.
+
+## 캔버스에서 카드 생성
+
+카드 생성 시기를 지정하여 Braze가 새 콘텐츠 카드 캠페인 및 캔버스 단계에 대한 오디언스 자격 및 개인화를 평가하는 시기를 선택할 수 있습니다.
+
+{% alert important %}
+캔버스 단계에서 카드 생성에 대한 제어는 초기 액세스 중입니다. 초기 액세스에 참여하고 싶다면 Braze 계정 매니저에게 문의하세요.
+{% endalert %}
+
+## 워크스페이스로 복사
+
+[워크스페이스 전반에 걸쳐 캠페인을 복사하면]({{site.baseurl}}/copying_to_workspaces/) 다른 워크스페이스에 있는 캠페인의 복사본으로 시작하여 메시지 구성을 빠르게 시작할 수 있습니다. 이 사본은 편집하고 시작할 때까지 초안으로 유지되므로 성공적인 메시징 전략을 유지하고 발전시키는 데 도움이 됩니다.
+
+{% alert important %}
+캠페인을 워크스페이스 간에 복사하는 기능은 현재 초기 액세스 중입니다. 이 얼리 액세스에 참여하고 싶다면 Braze 계정 매니저에게 문의하세요.
+{% endalert %}
+
+## 푸시 극대화
+
+[푸시 극대화]({{site.baseurl}}/user_guide/message_building_by_channel/push/android/push_max/)는 실패한 푸시 알림을 추적하고 사용자가 푸시를 받을 가능성이 더 높은 시점에 푸시를 다시 발송함으로써 Android 푸시 알림의 효과를 증대시켜 줍니다. 푸시 맥스에 대해 알아보고 이 기능을 사용하여 Android 푸시 알림의 전달 가능성을 [중국 OEM 장치]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/chinese_push_deliverability/)에 잠재적으로 향상시킬 수 있는 방법을 알아보세요.
+
+{% alert important %}
+푸시 극대화는 현재 얼리 액세스 중입니다. 초기 액세스에 참여하고 싶다면 Braze 계정 매니저에게 문의하세요.
+{% endalert %}
+
+## SDK 업데이트
+
+다음 소프트웨어 개발 키트 업데이트가 출시되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Xamarin SDK 2.0.0–2.0.1](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
+    - Android 바인딩을 Braze Android SDK 26.3.2로 업데이트했습니다
+- [Flutter SDK 6.0.1](https://pub.dev/packages/braze_plugin/changelog)
+    - 네이티브 Android 브리지를 Braze Android SDK 26.1.0에서 26.1.1로 업데이트했습니다.
+- [Android SDK 27.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [Swift SDK 6.5.0–6.6.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+    - HTML 인앱 메시지에서 커스텀 이벤트 및 구매 속성정보의 값이 항상 `1` 및 `0`으로 변환되어 각각 `true` 및 `false`가 되는 문제를 수정했습니다. 이 속성 값들은 이제 HTML에서 원래 형태를 존중할 것입니다.
+- [React Native SDK 6.0.0–6.0.2](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+    - 네이티브 Android 브리지를 Braze Android SDK 26.3.1에서 26.3.2로 업데이트했습니다.
+- [Cordova SDK 6.0.0-6.0.1](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
+    - 네이티브 Android 버전을 Braze Android SDK 26.3.1에서 26.3.2로 업데이트했습니다
+- [Expo 플러그인 1.1.2](https://github.com/braze-inc/braze-expo-plugin/blob/1.1.2/CHANGELOG.md)
+- [Unity 4.3.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
+- [세그먼트 Kotlin 1.4.1](https://github.com/braze-inc/braze-segment-kotlin/blob/main/CHANGELOG.md)
+- [세그먼트-Android 15.0.1](https://github.com/Appboy/appboy-segment-android/blob/master/CHANGELOG.md)
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2023/9_19_23.md b/_lang/ko/_help/release_notes/2023/9_19_23.md
new file mode 100644
index 00000000000..a2f99e4f045
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2023/9_19_23.md
@@ -0,0 +1,116 @@
+---
+nav_title: 2023년 9월 19일
+page_order: 3
+noindex: true
+page_type: update
+description: "이 문서에는 2023년 9월 19일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2023년 9월 19일 출시
+
+## 클라우드 데이터 수집을 위한 BigQuery
+
+이제 서버리스 엔터프라이즈 데이터 웨어하우스인 [BigQuery](https://cloud.google.com/bigquery)와 클라우드 데이터 수집 통합을 만들 수 있습니다. 자세한 내용은 [클라우드 데이터 통합 통합]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/integrations/?tab=bigquery)을 참조하세요.
+
+## Braze 데이터 혁신
+
+[Braze 데이터 트랜스포메이션]({{site.baseurl}}/user_guide/data_and_analytics/data_transformation/overview/)을 사용하면 웹훅 통합을 구축 및 관리하여 외부 플랫폼에서 Braze 고객 프로필로의 데이터 흐름을 자동화할 수 있습니다. 이렇게 새롭게 통합된 사용자 데이터는 더욱 정교한 마케팅 사용 사례를 뒷받침할 수 있습니다.
+
+## 캔버스에서 댓글 달기
+
+[캔버스의 댓글]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_comments/)은 마케팅 팀이 캔버스의 세부 사항을 파악하고, 토론하고, 검토할 수 있는 훌륭한 협업 공간이 될 수 있습니다. 캔버스를 작성할 때 댓글을 작성하고 관리하여 동료의 추가 피드백이 필요할 수 있는 영역을 식별할 수 있습니다.
+
+## 전달 가능성 센터
+
+[전달 가능성 센터]({{site.baseurl}}/user_guide/data_and_analytics/analytics/deliverability_center)는 Gmail 포스트마스터 도구를 사용하여 전송된 이메일의 데이터를 추적하고 전송 도메인에 대한 데이터를 수집할 수 있도록 지원하여 이메일 성능에 대한 더 많은 인사이트를 제공합니다. 
+
+이메일 전달 가능성은 캠페인 성공의 핵심입니다. Braze 대시보드의 배달 가능성 센터를 사용하면 IP 평판 또는 배달 오류별로 도메인을 확인하여 이메일 배달 가능성과 관련된 잠재적인 문제를 발견하고 해결할 수 있습니다.
+
+## 앱 내 메시지를 위한 드래그 앤 드롭 편집기
+
+이러한 추가 기능은 [인앱 메시지 드래그 앤 드롭 편집기에]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/) 추가되었습니다:
+
+- 메시지를 삭제하지 않는 텍스트 링크
+- 푸시 프라이머를 요청하는 버튼 동작
+- 사용자 지정 코드 편집기 블록
+
+드래그 앤 드롭 편집기에서 사용할 수 있는 모든 기능을 활용하려면 SDK를 권장 SDK 버전으로 업데이트하세요.
+
+### 사용자 지정 템플릿 저장(미리 보기)
+
+얼리 액세스 참가자는 인앱 메시지 드래그 앤 드롭 에디터에서 **템플릿으로 저장** 버튼을 사용하여 사용자 지정 인앱 메시지 템플릿을 만들고 저장할 수 있으며, 이 버튼은 에디터를 종료한 후 사용할 수 있습니다. 템플릿으로 저장하려면 먼저 캠페인을 시작하거나 초안으로 저장해야 합니다. 
+
+**템플릿** > **인앱 메시지 템플릿**으로 이동하여 인앱 메시지 템플릿을 만들고 저장할 수도 있습니다.
+
+{% alert important %}
+커스텀 템플릿 저장 기능은 현재 얼리 액세스 중입니다. 얼리 액세스에 참여하려면 Braze 계정 매니저에게 문의하세요.
+{% endalert %}
+
+## 인앱 메시지에서 다크 모드 비활성화하기
+
+개발자는 사용자 기기에 다크 모드가 켜져 있는 경우 인앱 메시지에 다크 모드 스타일이 적용되지 않도록 설정할 수 있습니다. 이를 구현하는 방법에 대한 단계는 다음 플랫폼별 문서를 참조하세요:
+
+- [Swift]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/setting_delegates/#disabling-dark-mode)
+- [Objective-C]({{site.baseurl}}/developer_guide/platform_integration_guides/ios/in-app_messaging/customization/handling_in_app_display/#disabling-dark-mode)
+
+## 메시지 보관을 위한 새로운 필드
+
+[메시지 아카이빙]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/)을 사용하면 보관 또는 규정 준수 목적으로 사용자에게 보낸 메시지의 사본을 S3 버킷에 저장할 수 있습니다. 메시지가 전송될 때마다 S3 버킷에 전달되는 JSON 페이로드에 다음 필드가 추가되었습니다:
+
+- `user_id`
+- `campaign_name`
+- `canvas_name`
+- `canvas_step_name`
+
+## 새로운 Liquid 개인화 태그
+
+인앱 메시지의 경우, Liquid 내에서 다음 앱 속성을 사용할 수 있습니다. 이 값은 앱에서 메시징을 요청하는 데 사용하는 SDK API 키를 기반으로 합니다.
+
+- {% raw %}`{{app.${api_id}}}`{% endraw %}
+- {% raw %}`{{app.${name}}}`{% endraw %}
+
+자세한 내용은 [지원되는 개인화 태그]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid/supported_personalization_tags#targeted-app-information)를 참조하세요.
+
+## 새로운 Braze 파트너십
+
+### Antavo 로열티 클라우드 - 채널 확장
+
+[Antavo와]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/antavo/) Braze의 통합을 통해 로열티 프로그램 관련 데이터를 사용하여 고객 경험을 향상시키는 개인화된 캠페인을 구축할 수 있습니다. Antavo는 두 플랫폼 간의 로열티 데이터 동기화를 지원하며, 이는 단방향 데이터 동기화로서 Antavo에서 Braze로만 동기화됩니다.
+
+### Ketch - 고객 데이터 플랫폼
+
+Braze와 [Ketch]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/ketch/)의 통합을 통해 Ketch 환경설정 센터 내에서 고객 커뮤니케이션 환경설정을 제어하고 이러한 변경 사항을 자동으로 Braze에 전파할 수 있습니다.
+
+### Redpoint - 고객 데이터 플랫폼
+
+Redpoint는 마케터에게 완전히 통합된 캠페인 오케스트레이션 플랫폼을 제공하는 기술 플랫폼입니다. Braze와 [Redpoint]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/redpoint/)의 통합을 통해 Redpoint CDP 데이터를 기반으로 Braze 세그먼트를 만들 수 있습니다. 
+
+### Simon Data - 고객 데이터 플랫폼
+ 
+Braze와 [Simon Data]({{site.baseurl}}/partners/data_and_infrastructure_agility/customer_data_platform/simondata/) 통합을 사용하면 코드 없이 실시간으로 오케스트레이션을 위해 정교한 오디언스를 생성하고 Braze에 동기화할 수 있습니다. 이 통합을 통해 Simon의 캠페인 우선순위 지정 및 아이덴티티 매칭 기능, 복잡한 통합 지원 등의 장점을 활용하여 Braze 캠페인을 다운스트림으로 향상시킬 수 있습니다.
+
+### OfferFit - 동적 콘텐츠
+
+[OfferFit]({{site.baseurl}}/partners/message_personalization/dynamic_content/offerfit/)과 Braze의 통합을 통해 고객 데이터를 기반으로 모든 고객에게 적합한 메시지, 채널, 타이밍을 자동으로 찾아낼 수 있습니다. 교차 판매, 상향 판매, 재구매, 유지, 갱신, 추천, 윈백과 같은 비즈니스 목표에 따라 기존에 식별된 고객을 대상으로 캠페인을 최적화할 수 있습니다.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Swift SDK 6.6.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#661)
+- [웹 SDK 4.9.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#490)
+- [Android SDK 28.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2800)
+    - 최소 SDK 버전이 21(롤리팝)로 업데이트되었습니다.
+    - 기능 플래그 기능이 수정되었습니다.
+    - `Braze.getFeatureFlag(id)` 는 이제 기능 플래그가 존재하지 않는 경우 null을 반환합니다.
+    - `Braze.subscribeToFeatureFlagsUpdates()`는 새로 고침 요청이 완료될 때, 그리고 이전에 캐시된 데이터가 존재하는 경우에만 콜백합니다. 또한 새로 고침 실패 시 캐시된 기능 플래그와 함께 호출됩니다.
+        - 앱 시작 시 캐시된 값을 즉시 사용하려면 `Braze.getFeatureFlag(id)`를 사용하세요.
+    - `DefaultInAppMessageViewWrapper.createButtonClickListener()` 을 `DefaultInAppMessageViewWrapper.createButtonClickListeners()` 으로 리팩터링했습니다.
+- [React Native SDK 7.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md#700)
+    - 네이티브 Android 브릿지를 [Braze Android SDK 26.3.2에서 27.0.1로](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2701) 업데이트합니다.
+- [Cordova SDK 7.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2800)
+    - 네이티브 Android 브릿지를 [Braze Android SDK 26.3.2에서 27.0.1로](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2701) 업데이트합니다.
+- [Roku SDK 2.0.0](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md#200)
+    - `getFeatureFlag` 플래그가 존재하지 않으면 무효로 반환됩니다.
+    - `BrazeTask`는 이제 `BrazeFeatureFlagsUpdated`를 관찰하여 기능 플래그 새로 고침의 성공 또는 실패 시점을 파악합니다. 데이터 값이 항상 다른 것은 아닙니다.
+
diff --git a/_lang/ko/_help/release_notes/2024.md b/_lang/ko/_help/release_notes/2024.md
new file mode 100644
index 00000000000..4e63232f2ee
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2024.md
@@ -0,0 +1,37 @@
+---
+page_order: 0
+nav_title: 2024
+layout: dev_guide
+noindex: true
+guide_top_header: "2024 릴리스 노트"
+
+page_type: landing
+description: "이 섹션에서는 2024년에 대한 릴리스 노트를 확인할 수 있습니다."
+
+guide_menu_title: ""
+guide_menu_list:
+  - name: 2024년 1월 9일
+    link: /docs/help/release_notes/2024/1_9_24/
+    image: /assets/img/braze_icons/snowflake-01.svg
+  - name: 2024년 2월 6일
+    link: /docs/help/release_notes/2024/2_6_24/
+    image: /assets/img/braze_icons/hearts.svg
+  - name: 2024년 3월 5일
+    link: /docs/help/release_notes/2024/3_5_24/
+    image: /assets/img/braze_icons/trophy-01.svg
+  - name: 2024년 4월 2일
+    link: /docs/help/release_notes/2024/4_2_24/
+    image: /assets/img/braze_icons/droplets-01.svg
+  - name: 2024년 4월 30일
+    link: /docs/help/release_notes/2024/4_30_24/
+    image: /assets/img/braze_icons/droplets-01.svg
+  - name: 2024년 5월 28일
+    link: /docs/help/release_notes/2024/5_28_24/
+    image: /assets/img/braze_icons/sun.svg
+  - name: 2024년 6월 25일
+    link: /docs/help/release_notes/2024/6_25_24/
+    image: /assets/img/braze_icons/umbrella-03.svg
+  - name: 2024년 7월 23일
+    link: /docs/help/release_notes/2024/7_23_24/
+    image: /assets/img/braze_icons/flag-01.svg
+---
diff --git a/_lang/ko/_help/release_notes/2024/1_9_24.md b/_lang/ko/_help/release_notes/2024/1_9_24.md
new file mode 100644
index 00000000000..199a42f277a
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2024/1_9_24.md
@@ -0,0 +1,53 @@
+---
+nav_title: 2024년 1월 9일
+page_order: 12
+noindex: true
+page_type: update
+description: "이 문서에는 2024년 1월 9일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2024년 1월 9일 출시
+
+## 업데이트된 Shopify 통합 문서
+
+다음을 포함하여 Braze와 Shopify 통합 설명서의 섹션을 업데이트했습니다:
+
+- [Shopify 시작하기]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/getting_started_shopify/)
+- [Braze에서 Shopify 설정]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/)
+- [Shopify 사용자 ID 관리]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_user_identity/)
+
+## 데이터 유연성
+
+### 카탈로그의 재고 부족 알림
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+카탈로그와 캔버스를 통한 [품절 알림을]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications/) 조합하여 품목의 품절 시 고객에게 알릴 수 있습니다. 고객이 선택한 커스텀 이벤트를 수행할 때마다 아이템이 보충될 때마다 자동으로 알림을 받도록 구독할 수 있습니다.
+
+### 카탈로그 세그먼트
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+[카탈로그 세그먼트는]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/catalog_segments/) SQL 세그먼트 확장의 카탈로그 데이터를 기반으로 하는 사용자 대상입니다. 이러한 SQL 세그먼트 확장은 세그먼트에서 참조한 다음 캠페인 및 캔버스에서 타겟팅할 수 있습니다. 카탈로그 세그먼트는 SQL을 사용하여 카탈로그의 데이터와 사용자 지정 이벤트 또는 구매의 데이터를 조인합니다. 이렇게 하려면 카탈로그와 커스텀 이벤트 또는 구매에 공통 식별자 필드가 있어야 합니다.
+
+### Firebase Cloud 메시징 API로 마이그레이션하기
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+더 이상 사용되지 않는 Google의 클라우드 메시징 API에서 완전히 지원되는 Firebase 클라우드 메시징(FCM) API로 [마이그레이션하는 방법을]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/) 알아보세요.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Swift SDK 7.5.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+    - Braze의 데이터 수집 정책을 설명하기 위해 `BrazeKit` 및 `BrazeLocation`에 대한 개인정보처리방침을 추가합니다. 자세한 내용은 Apple의 개인정보처리방침 [설명서](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests)를 참조하세요. 데이터 수집 관행을 관리하기 위한 더 많은 구성은 향후 릴리스에서 제공될 예정입니다.
+    - 7.1.0에 도입된 XC프레임워크의 코드 서명 관련 문제를 수정합니다.
+- [웹 SDK v5.1.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- [Unity SDK 5.0.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
+    - Braze Swift SDK 6.1.0에서 7.4.0으로 네이티브 iOS 브릿지를 업데이트했습니다.
+        - 이제 iOS 리포지토리 링크는 이 [리포지토리](https://github.com/braze-inc/braze-swift-sdk-prebuilt-dynamic)에서 미리 빌드된 동적 XC프레임웍스를 가리킵니다.
+    - 네이티브 Android 브릿지를 Braze Android SDK 27.0.1에서 29.0.1로 업데이트했습니다.
+    - `AppboyBinding.GetFeatureFlag(string id)`는 이제 기능 플래그가 존재하지 않으면 `null`을 반환합니다.
+    - `FEATURE_FLAGS_UPDATED`는 새로 고침 요청이 성공 또는 실패로 완료된 경우와 현재 세션에서 이전에 캐시된 데이터가 있는 경우 최초 구독 시에만 트리거됩니다.
+
diff --git a/_lang/ko/_help/release_notes/2024/2_6_24.md b/_lang/ko/_help/release_notes/2024/2_6_24.md
new file mode 100644
index 00000000000..7ea6c18276a
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2024/2_6_24.md
@@ -0,0 +1,122 @@
+---
+nav_title: 2024년 2월 6일
+page_order: 11
+noindex: true
+page_type: update
+description: "이 문서에는 2024년 2월 6일의 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2024년 2월 6일 출시
+
+## Braze 프라이버시 매니페스트
+
+Braze는 신고된 추적 기술 데이터를 전용 `-tracking` 엔드포인트로 자동 리라우팅하는 유연한 새 API와 함께 자체 개인정보처리방침을 공개했습니다. 자세한 내용은 [Braze 프라이버시 매니페스트]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest)를 참조하세요.
+
+## Google EU 사용자 동의 정책
+
+Google은 2024년 3월 6일부터 시행되는 [디지털 시장법(DMA)](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html)의 변경사항에 따라 [EU 사용자 동의 정책](https://www.google.com/about/company/user-consent-policy/)을 업데이트합니다. 이 새로운 변경 사항에 따라 광고주는 EEA 및 영국 최종 사용자에게 특정 정보를 공개하고 해당 사용자로부터 필요한 동의를 얻어야 합니다. 곧 변경될 사항의 일환으로, [Braze에서 두 동의 신호를 모두 커스텀 속성으로 수집]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)할 수 있습니다. Braze는 이러한 커스텀 속성의 데이터를 Google의 적절한 동의 필드에 동기화합니다.
+
+## 데이터 유연성
+
+### Google 파이어베이스 클라우드 메시징(FCM) API
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 [더 이상 사용되지 않는 Google의 클라우드 메시징 API에서 완전히 지원되는 Firebase 클라우드 메시징(FCM) API로 마이그레이션할]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/migrating_to_firebase_cloud_messaging/) 수 있습니다. 
+
+### Braze 클라우드 데이터 수집(CDI) 엔드포인트
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+Braze CDI 엔드포인트를 사용하려면
+- [기존 연동 목록을 반환합니다]({{site.baseurl}}/api/endpoints/cdi/get_integration_list/).
+- 지정된 통합에 대한 [과거 동기화 상태 목록을 반환합니다]({{site.baseurl}}/api/endpoints/cdi/get_job_sync_status/).
+- 지정된 통합에 대한 [동기화를 트리거합니다]({{site.baseurl}}/api/endpoints/cdi/post_job_sync/).
+
+### Databricks용 Braze 클라우드 데이터 수집(CDI) 지원
+
+이제 [Databricks 데이터 소스에서]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/sync_catalogs_data/#step-2-integrate-cloud-data-ingestion-with-catalog-data) 카탈로그에 대한 Braze CDI 지원을 사용할 수 있습니다.
+
+### 수동 Swift SDK 통합
+
+통합 가이드에 [수동 통합]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/initial_sdk_setup/installation_methods/manual_integration) 문서를 추가하여 패키지 관리자를 사용하지 않고 Swift SDK를 수동으로 통합하는 방법을 설명했습니다.
+
+## 사용 중단
+
+2024년 1월 11일, Braze는 Windows 앱과 Baidu 앱에서 메시지 서비스 및 데이터 수집을 중단했습니다.
+
+## 창의력 발휘
+
+### SQL 세그먼트 확장 사용 사례
+
+[SQL 세그먼트 확장 사용 사례]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/use_cases) 라이브러리에는 자체 SQL 쿼리를 만들 때 영감을 얻기 위해 사용할 수 있는 SQL 세그먼트 확장에 대한 테스트된 쿼리가 포함되어 있습니다.
+
+## 강력한 채널
+
+### 사용자 지정 코드 블록
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[사용자 지정 코드 블록을]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/editor_blocks/#custom-code) 사용하면 인앱 메시지에 HTML, CSS 및 JavaScript를 추가, 편집 또는 삭제할 수 있습니다.
+
+### 푸시 알림의 페이로드 크기 줄이기
+
+새로운 도움말 문서 [알림 페이로드 크기]({{site.baseurl}}/help/help_articles/push/reducing_payload_size#reducing-push-notification-payload-size)에서는 푸시 페이로드 크기 제한으로 인해 캠페인 또는 캔버스 단계를 시작할 수 없는 경우 푸시 알림의 페이로드 크기를 줄일 수 있는 몇 가지 팁을 제공합니다.
+
+### 캠페인 또는 캔버스에 BCC 주소 추가하기
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이메일 메시지에 숨은 참조 [주소를]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/?tab=bcc%20address#outbound-email-settings) 추가할 수 있습니다. 이렇게 하면 사용자가 받은 메시지의 동일한 사본이 사용자의 BCC 받은편지함으로 전송됩니다. 이를 통해 규정 준수 요구 사항이나 고객 지원 문제를 위해 사용자에게 보낸 메시지의 사본을 보관할 수 있습니다.
+
+### 이메일의 원클릭 수신 거부 링크
+
+[목록 수신 거부 헤더]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#list-unsubscribe-header)를 사용하면 메시지 본문이 아닌 사서함 UI 내에 수신 **거부** 버튼을 표시하여 수신자가 클릭 한 번으로 마케팅 이메일의 수신을 거부할 수 있습니다.
+
+## 새로운 Braze 파트너십
+
+### Criteo - 캔버스 오디언스 동기화
+
+브랜드는 [Braze 오디언스 싱크 투 Criteo]({{site.baseurl}}/partners/canvas_steps/criteo_audience_sync/)를 사용하여 자체 Braze 통합의 사용자 데이터를 Criteo 고객 목록에 추가하여 행동 트리거, 세분화 등을 기반으로 광고를 게재할 수 있습니다. 사용자 데이터를 기반으로 Braze 캔버스에서 메시지(푸시, 이메일, SMS, 웹훅 등)를 트리거하는 데 일반적으로 사용하는 모든 기준을 이제 Criteo 고객 목록에서 해당 사용자에게 광고를 트리거하는 데 사용할 수 있습니다.
+
+### 이동식 잉크 - 동적 콘텐츠
+
+[무버블 잉크]({{site.baseurl}}/partners/message_personalization/dynamic_content/movable_ink#movable-ink) 고객 데이터 API 통합을 통해 마케터는 Braze에 저장된 고객 이벤트 데이터를 활성화하여 무버블 잉크 내에서 개인화된 콘텐츠를 생성할 수 있습니다.
+
+### 스쿠버 애널리틱스 - 분석
+
+[Scuba 분석]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/scuba#scuba-analytics)은 고속 시계열 데이터를 위해 설계된 풀스택 머신 러닝 기반 데이터 협업 플랫폼입니다. Scuba를 사용하면 사용자(액터라고도 함)를 선택적으로 내보내고 Braze 플랫폼에 로드할 수 있습니다. Scuba에서는 커스텀 액터 속성을 사용하여 행동 추세를 분석하고, 다양한 플랫폼에서 데이터를 활성화하고, 머신 러닝을 사용하여 예측 모델링을 수행합니다.
+
+## SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+ 
+- [Expo 플러그인 2.0.0](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+    - [엑스포 SDK 50 요구 사항](https://expo.dev/changelog/2024/01-18-sdk-50)에 따라 iOS 최소 플랫폼 버전을 `13.4`로 상향 조정합니다.
+    - 이 버전은 Expo SDK 50을 완벽하게 지원하려면 Braze React Native SDK 버전 [8.3.0 이상](https://github.com/braze-inc/braze-react-native-sdk/releases/tag/8.3.0)이 필요합니다.
+- [React Native SDK 8.3.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.3.0/CHANGELOG.md)
+- [Unity SDK 5.1.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
+- [Android SDK 30.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+    - 인앱 메시지에 사용되는 웹뷰가 `WebViewAssetLoader`를 사용하도록 업데이트되었습니다.
+        - `WebSettings.allowFileAccess`는 이제 `InAppMessageHtmlBaseView` 및 `BrazeWebViewActivity`에서 false로 설정됩니다.
+        - 직접 `InAppMessageWebViewClient` 또는 `InAppMessageHtmlBaseView` 을 사용하는 경우 원본 클래스와 비교하여 구현이 에셋을 올바르게 로드하고 있는지 확인하세요.
+        - 사용자 정의 클래스를 사용하지 않는 경우 모든 것이 이전과 동일하게 작동합니다.
+- [Braze Swift SDK 6.6.2](https://github.com/braze-inc/braze-swift-sdk/blob/6.6.2/CHANGELOG.md)
+- [Braze Swift SDK 7.6.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0)
+- [Xamarin SDK 버전 3.0.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
+    - NuGet 패키지의 이름이 `AppboyPlatformXamariniOSBinding`에서 [`BrazePlatform.BrazeiOSBinding`](https://www.nuget.org/packages/BrazePlatform.BrazeiOSBinding/)으로 변경되었습니다.
+        - 업데이트된 패키지를 사용하려면 `AppboyPlatformXamariniOSBinding;` 사용 인스턴스를 Braze 사용으로 바꾸세요
+    - 이 버전에서는 .NET 6+를 사용해야 하며 Xamarin 프레임워크를 사용하는 프로젝트에 대한 지원이 제거됩니다. Xamarin 지원 종료에 대한 [Microsoft의 정책](https://dotnet.microsoft.com/en-us/platform/support/policy/xamarin)을 참조하세요.
+    - Android 바인딩을 [Braze Android SDK 26.3.2에서 29.0.1로](https://github.com/braze-inc/braze-android-sdk/compare/v26.3.1...v29.0.1#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트했습니다.
+- [Xamarin SDK 4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
+    - 이 버전에서는 iOS 바인딩이 [Braze Swift SDK를](https://github.com/braze-inc/braze-swift-sdk/) 사용하도록 업데이트됩니다. 대부분의 iOS 공용 API가 변경되었으므로, 대체 사용에 대한 안내는 [마이그레이션 가이드](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/appboy-migration-guide/) (Swift)를 참조하세요. 기존 공개 API를 계속 사용할 수 있도록 호환성 바인딩을 제공합니다.
+        - 이제 iOS 바인딩은 여러 모듈로 구성됩니다:
+            - **BrazeKit:** 분석 및 푸시 알림을 지원하는 기본 SDK 라이브러리(nuget: [Braze.iOS.BrazeKit](https://www.nuget.org/packages/Braze.iOS.BrazeKit)).
+            - BrazeUI: 인앱 메시지 및 콘텐츠 카드를 위한 Braze 제공 사용자 인터페이스 라이브러리(nuget: [Braze.iOS.BrazeUI](https://www.nuget.org/packages/Braze.iOS.BrazeUI)).
+            - BrazeLocation: 위치 분석 및 지오펜스 모니터링을 지원하는 위치 라이브러리(nuget: [Braze.iOS.BrazeLocation](https://www.nuget.org/packages/Braze.iOS.BrazeLocation)).
+            - BrazeKitCompat: 4.0.0 이전 API를 지원하는 호환성 라이브러리(nuget: [Braze.iOS.BrazeKitCompat](https://www.nuget.org/packages/Braze.iOS.BrazeKitCompat)).
+            - BrazeUICompat: 4.0.0 이전 UI API를 지원하는 호환성 라이브러리(nuget: [Braze.iOS.BrazeUICompat](https://www.nuget.org/packages/Braze.iOS.BrazeUICompat)).
+        - 새로운 통합에 대해서는 BrazeiOSMauiSampleApp을, 호환성 모듈의 사용법에 대해서는 BrazeiOSMauiCompatSampleApp을 참조하세요.
+    - [Braze Swift SDK 7.6.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/7.6.0)에 대한 iOS 바인딩을 업데이트했습니다.
+    - iOS 바인딩을 사용하려면 Xcode 15와의 호환성을 위해 .NET 7을 사용해야 합니다.
+- [Xamarin SDK 4.0.1](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
diff --git a/_lang/ko/_help/release_notes/2024/3_5_24.md b/_lang/ko/_help/release_notes/2024/3_5_24.md
new file mode 100644
index 00000000000..6679aa6c1a4
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2024/3_5_24.md
@@ -0,0 +1,101 @@
+---
+nav_title: 2024년 3월 5일
+page_order: 10
+noindex: true
+page_type: update
+description: "이 문서에는 2024년 3월 5일에 대한 릴리스 노트가 포함되어 있습니다."
+---
+
+# 2024년 3월 5일 출시
+
+## Google EU 사용자 동의 정책
+
+Google은 2024년 3월 6일부터 시행되는 [디지털 시장법(DMA)](https://ads-developers.googleblog.com/2023/10/updates-to-customer-match-conversion.html) 개정 사항에 따라 [EU 사용자 동의 정책](https://www.google.com/about/company/user-consent-policy/)을 업데이트하고 있습니다. 이 새로운 변경 사항에 따라 광고주는 EEA 및 영국 최종 사용자에게 특정 정보를 공개하고 해당 사용자로부터 필요한 동의를 얻어야 합니다. 곧 변경될 사항의 일환으로, [Braze에서 두 동의 신호를 모두 커스텀 속성으로 수집]({{site.baseurl}}/partners/canvas_steps/google_audience_sync/#collecting-consent-for-eea-and-uk-end-users)할 수 있습니다. Braze는 이러한 커스텀 속성의 데이터를 Google의 적절한 동의 필드에 동기화합니다.
+
+## 데이터 유연성
+
+### 중복 사용자 병합
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+이제 Braze 대시보드에서 [중복 사용자를 검색하고 병합하여]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users) 캠페인과 캔버스의 효과를 극대화할 수 있습니다. 사용자 프로필을 개별적으로 병합하거나 식별자가 일치하는 모든 프로필을 가장 최근에 업데이트된 사용자 프로필로 병합하는 일괄 병합을 수행할 수 있습니다.
+
+### 보관된 콘텐츠 검색
+
+이제 Braze 대시보드에서 **아카이브된 콘텐츠 표시**를 선택하여 [검색 결과에 아카이브된 콘텐츠]({{site.baseurl}}/user_guide/administrative/access_braze/global_search/#filter-for-archived-content)를 포함할 수 있습니다.
+
+### AWS S3 및 Google Cloud Storage에 대한 메시지 아카이빙 지원
+
+[메시지 보관을]({{site.baseurl}}/user_guide/data_and_analytics/export_braze_data/message_archiving/) 사용하여 보관 또는 규정 준수 목적으로 사용자에게 보낸 메시지의 사본을 AWS S3 버킷, Azure Blob Storage 컨테이너 또는 Google Cloud Storage 버킷에 저장할 수 있습니다.
+
+### SQL 테이블 참조
+
+쿼리 빌더에서 또는 SQL 세그먼트 확장을 생성할 때 쿼리할 수 있는 테이블과 열을 보려면 [SQL 테이블 참조]({{site.baseurl}}/user_guide/engagement_tools/segments/sql_segments/sql_segments_tables/)를 방문하세요.
+
+## 창의력 발휘
+
+### AI 카피라이팅을 위한 톤 제어
+
+이제 AI 카피라이팅 어시스턴트로 생성된 카피의 스타일을 결정하기 위해 [메시지 톤]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/#steps)을 선택할 수 있습니다.
+
+## 강력한 채널
+
+### 카드 생성
+
+카드 [생성]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/) 시기를 지정하여 Braze가 새 콘텐츠 카드 캠페인 및 캔버스 단계에 대한 오디언스 자격 및 개인화를 평가하는 시기를 선택할 수 있습니다. 
+
+### 사용자 경로 미리보기
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+사용자가 받게 될 메시지와 타이밍을 미리 보는 등 사용자를 위해 만든 캔버스 여정을 경험해 보세요. 이러한 [테스트 실행]({{site.baseurl}}/preview_user_paths/)은 캔버스를 보내기 전에 메시지가 올바른 오디언스에게 전송되는지 확인하는 품질 보증 역할을 합니다.
+
+### 빠른 푸시 캠페인
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+Braze에서 푸시 캠페인을 만들 때 여러 플랫폼과 기기를 선택하여 [퀵 푸시]({{site.baseurl}}/user_guide/message_building_by_channel/push/creating_a_push_message/quick_push/)라는 단일 편집 환경에서 모든 플랫폼에 하나의 메시지를 작성할 수 있습니다. 이 기능은 캠페인에만 사용할 수 있습니다.
+
+### 사용자 지정 List-Unsubscribe 헤더
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이메일 메시징에 [커스텀 목록 수신 거부 헤더]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#custom-list-unsubscribe-header)를 추가하면 수신자가 수신 거부할 수 있습니다. 이렇게 하면 직접 구성한 원클릭 수신 거부 엔드포인트와 선택 사항인 "mailto:"를 추가할 수 있습니다. 원클릭 수신 거부 HTTP는 대량 발신자에 대한 Yahoo 및 Gmail의 요구 사항이므로 Braze는 커스텀 목록 수신 거부 헤더를 지원하기 위해 URL을 입력해야 합니다.
+
+### 인앱 메시지를 위한 여러 페이지
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+[인앱 메시지에 페이지를 추가하면]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create/#multi-page) 온보딩 흐름이나 환영 여정과 같은 순차적인 흐름을 통해 사용자를 안내할 수 있습니다. **빌드** 탭의 **페이지** 섹션에서 페이지를 관리할 수 있습니다.
+
+### 실험 경로에 대한 경로 무작위화
+
+실험 경로 단계의 [경로 할당을 항상 무작위로 지정]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step)하려면 단계의 **실험 경로에서 무작위 경로를** 선택합니다. 이 옵션은 위닝 또는 개인화된 경로를 사용할 때는 사용할 수 없습니다.
+
+### 이메일 캡처 양식
+
+[이메일 캡처 메시지를]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form/) 사용하면 사이트 사용자에게 이메일 주소를 제출하라는 메시지를 쉽게 보낼 수 있으며, 이후에는 모든 메시징 캠페인에서 사용할 수 있도록 사용자 프로필에서 해당 주소를 사용할 수 있습니다.
+
+## SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [AppboyKit iOS SDK 4.7.0](https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.7.0)
+    - 이는 2024년 3월 1일([Swift SDK](https://github.com/braze-inc/braze-swift-sdk/) 사용을 위해) 서비스 종료 이전에 Objective-C SDK의 마지막 릴리스가 될 것입니다.
+    - SDWebImage의 최소 요구 버전을 5.8.2에서 5.18.7로 업데이트합니다. 이 버전에는 [개인정보에 영향을 미치는 SDK 목록](https://developer.apple.com/support/third-party-SDK-requirements/)에 표시되는 SDWebImage에 대한 개인정보 매니페스트가 포함되어 있습니다.
+- [Flutter SDK 8.1.0](https://pub.dev/packages/braze_plugin/changelog)
+- [Unity 5.2.0](https://github.com/braze-inc/braze-unity-sdk/blob/master/CHANGELOG.md)
+- [React Native SDK 8.4.0](https://github.com/braze-inc/braze-react-native-sdk/blob/8.4.0/CHANGELOG.md)
+- [Xamarin SDK 버전 4.0.2](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md)
+- [Swift SDK 7.7.0-8.0.1](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#801)
+- [Android SDK 30.1.0-30.2.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [웹 SDK 5.1.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- [Cordova SDK 8.0.0-Cordova SDK 8.1.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
+    - 네이티브 Android 브릿지를 [Braze Android SDK 27.0.1에서 30.0.0으로](https://github.com/braze-inc/braze-android-sdk/compare/v27.0.0...v30.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트했습니다.
+    - [Braze Swift SDK 6.6.0에서 7.6.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/6.6.0...7.6.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 네이티브 iOS 브릿지를 업데이트했습니다.
+    - `Banner` 콘텐츠 카드 유형 이름을 `ImageOnly` 으로 변경했습니다:
+        - `ContentCardTypes.BANNER`부터 `ContentCardTypes.IMAGE_ONLY`까지
+        - Android에서 프로젝트의 XML 파일에 콘텐츠 카드용 배너라는 단어가 포함된 경우 `image_only`로 대체해야 합니다.
+    - `BrazePlugin.getFeatureFlag(id)`는 이제 기능 플래그가 존재하지 않으면 `null`을 반환합니다.
+    - `BrazePlugin.subscribeToFeatureFlagsUpdates(function)`는 새로 고침 요청이 성공 또는 실패로 완료된 경우와 현재 세션에서 이전에 캐시된 데이터가 있는 경우 최초 구독 시에만 트리거됩니다.
+    - 더 이상 사용되지 않는 메서드 `registerAppboyPushMessages` 를 제거했습니다. 대신 `setRegisteredPushToken` 을 사용하세요.
diff --git a/_lang/ko/_help/release_notes/2024/4_2_24.md b/_lang/ko/_help/release_notes/2024/4_2_24.md
new file mode 100644
index 00000000000..faafeb2fedb
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2024/4_2_24.md
@@ -0,0 +1,70 @@
+---
+nav_title: 2024년 4월 2일
+description: "이 문서에는 2024년 4월 2일의 릴리스 노트가 포함되어 있습니다."
+page_order: 9
+page_type: reference
+---
+
+# 2024년 4월 2일 출시
+
+## WhatsApp
+
+### 다수의 비즈니스 계정
+
+이제 각 워크스페이스에 여러 개의 WhatsApp 비즈니스 계정과 구독 그룹을 추가할 수 있습니다. 전체 절차를 보려면 [여러 WhatsApp 비즈니스 계정 및 전화번호]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups/)를 참조하세요.
+
+### 열람율
+
+WhatsApp은 인도의 소비자들과 함께 새로운 접근 방식을 테스트하여 더 가치 있는 경험을 창출하고 비즈니스의 마케팅 대화에 대한 참여를 극대화하고 있습니다. 이는 주어진 기간 동안 어떤 사업체로부터 한 사람이 받는 마케팅 대화의 수를 제한하는 것을 포함할 수 있으며, 읽힐 가능성이 적은 소수의 대화로 시작할 수 있습니다. 자세한 내용은 [Meta resources]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/meta_resources/)를 참조하십시오.
+
+## 데이터 유연성
+
+### Amazon S3 버킷을 Braze에 동기화
+
+{% multi_lang_include release_type.md release="얼리 액세스" %}
+
+이제 S3용 클라우드 데이터 수집을 사용하여 AWS 계정에 있는 하나 이상의 S3 버킷을 Braze와 직접 통합할 수 있습니다. 새 파일이 S3에 게시되면 SQS에 메시지가 게시되고 Braze 클라우드 데이터 수집이 해당 새 파일을 받습니다. 자세한 내용은 [파일 스토리지 통합]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/file_integrations/)을 참조하세요.
+
+### Shopify OAuth
+
+{% multi_lang_include release_type.md release="일반 가용성" %}
+
+Shopify는 모든 규모의 소매 비즈니스를 시작하고 성장시키며 마케팅하고 관리할 수 있는 신뢰할 수 있는 도구를 제공하는 선도적인 글로벌 상거래 회사입니다. 이제 Braze용 Shopify를 설정할 때 [워크스페이스에 OAuth를 사용하도록]({{site.baseurl}}/partners/message_orchestration/channel_extensions/ecommerce/shopify/setting_up_shopify/) 설정할 수 있습니다.
+
+### iOS 푸시 알림에 Expo를 사용하세요
+
+React Native와 함께 Expo를 사용하여 iOS 앱에 리치 푸시 알림 및 푸시 스토리를 통합하는 [방법을 추가했습니다]({{site.baseurl}}/developer_guide/platform_integration_guides/react_native/push_notifications/?tab=expo).
+
+### 원격 시작 iOS 라이브 활동
+
+이제 [`/messages/live_activity/start` 엔드포인트]({{site.baseurl}}/api/endpoints/messaging/live_activity/start/)를 사용하여 iOS에서 라이브 활동을 원격으로 시작할 수 있습니다. 전체 안내는 [라이브 활동: ]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/live_activities/live_activities/#step-2-start-the-activity) 활동 시작을 참고하세요.
+
+## AI 및 ML 자동화
+
+### 항목 추천
+
+{% multi_lang_include release_type.md release="얼리 액세스" %}
+
+이제 Braze의 Sage AI를 사용하면 가장 인기 있는 제품을 계산하거나 특정 카탈로그에 대한 개인화된 AI 추천을 생성할 수 있습니다. 자세한 내용은 [항목 추천에 대한 정보]({{site.baseurl}}/user_guide/sage_ai/recommendations/about_item_recommendations/)를 참조하세요.
+
+### QA 인앱 메시지 콘텐츠
+
+{% multi_lang_include release_type.md release="일반 가용성" %}
+
+이전에 Braze 대시보드에서 Sage AI를 사용하여 SMS 및 푸시 알림 콘텐츠에 대한 품질 보증을 수행할 수 있었습니다. 이제 [QA 인앱 메시지 콘텐츠]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_content_qa/)도 가능합니다.
+
+## 새로운 Braze 파트너십
+
+### Census - 코호트 가져오기
+
+이제 [코호트 사용자들을 Braze에서 Census로 가져올 수 있습니다]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/census/). 이는 Snowflake 및 BigQuery와 같은 클라우드 데이터 웨어하우스를 Braze에 연결하는 데이터 활성화 플랫폼입니다. 귀하의 마케팅 Teams는 퍼스트파티 데이터를 활용하여 동적 오디언스 세그먼트를 구축하고, 고객 속성을 동기화하여 캠페인을 개인화하며, 모든 데이터를 Braze에서 최신 상태로 유지할 수 있습니다.
+
+## SDK 업데이트
+
+다음 소프트웨어 개발 키트 업데이트가 출시되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [React Native 9.1.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+  - 최소 React Native 버전을 0.71.0으로 업데이트했습니다.
+  - 최소 iOS 버전을 12.0으로 업데이트했습니다.
+  - Braze Swift SDK 8.1.0을 사용하도록 iOS 바인딩을 업데이트했습니다.
+  - Braze Android SDK 30.1.1을 사용하도록 Android 바인딩을 업데이트했습니다.
diff --git a/_lang/ko/_help/release_notes/2024/4_30_24.md b/_lang/ko/_help/release_notes/2024/4_30_24.md
new file mode 100644
index 00000000000..5934c6301fa
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2024/4_30_24.md
@@ -0,0 +1,82 @@
+---
+nav_title: 2024년 4월 30일
+description: "이 문서에는 2024년 4월 30일에 대한 릴리스 노트가 포함되어 있습니다."
+page_order: 8
+page_type: reference
+---
+
+# 2024년 4월 30일 출시
+
+## 프로모션 코드 목록을 생성하거나 업데이트할 수 있는 권한
+
+2024년 4월부터 사용자는 프로모션 코드 목록을 만들거나 업데이트하려면 '캠페인, 캔버스, 카드, 세그먼트, 미디어 라이브러리에 액세스' 권한이 필요합니다. 권한 이름과 설명에 대한 목록은 [제한된 권한 및 팀 역할 권한 관리하기]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#managing-limited-and-team-role-permissions)를 참조하세요.
+
+## 데이터 유연성
+
+### SAML 적시 프로비저닝
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+[적시 프로비저닝]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/saml_jit)은 SAML SSO와 함께 작동하여 새로운 대시보드 사용자가 처음 로그인할 때 Braze 계정을 만들 수 있도록 합니다. 따라서 관리자가 새 대시보드 사용자의 계정을 수동으로 만들고, 권한을 선택하고, 워크스페이스에 할당하고, 사용자가 계정을 활성화할 때까지 기다릴 필요가 없습니다.
+
+### 권한 집합 및 역할
+
+[권한 세트]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions/#permission-sets-and-roles)를 사용하여 특정 주제 영역 또는 작업과 관련된 권한을 묶을 수 있습니다. 이러한 권한 집합은 여러 워크스페이스에서 동일한 액세스 권한이 필요한 대시보드 사용자에게 적용할 수 있습니다.
+
+### 클라우드 데이터 수집 세그먼트
+
+Braze [클라우드 데이터 수집 세그먼트를]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/cdi_segments) 사용하면 CDI 연결을 통해 제공되는 데이터를 사용하여 자체 데이터 웨어하우스에 직접 쿼리하는 SQL을 작성하고, Braze 내에서 타겟팅할 수 있는 사용자 그룹을 만들 수 있습니다.
+
+## 창의력 발휘
+
+### 쿼리 빌더 템플릿
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+쿼리 빌더 템플릿을 사용하면 Snowflake의 Braze 데이터를 사용하여 보고서를 만들 수 있습니다. [쿼리 빌더]({{site.baseurl}}/user_guide/data_and_analytics/query_builder/) 템플릿에 액세스하려면 보고서를 만들 때 **쿼리 템플릿**을 선택합니다. 모든 템플릿은 최대 최근 60일까지의 데이터를 표시하지만 편집기에서 해당 값과 다른 값을 직접 편집할 수 있습니다.
+
+### 세그먼트별 성능 데이터
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+캠페인, 배리언트, 캔버스 및 세그먼트별 캔버스 단계에 대한 쿼리 빌더 보고서 템플릿에서 [성과 데이터]({{site.baseurl}}/user_guide/data_and_analytics/reporting/viewing_and_understanding_segment_data/#performance-data-by-segment)를 세그먼트별로 분류할 수 있습니다.
+
+## 강력한 채널
+
+### SMS 메시징을 위한 자동 링크 단축
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[자동 링크 단축을]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/keyword_handling/?tab=manage%20responses#managing-keywords-and-auto-responses) 사용하여 응답에서 정적 URL을 자동으로 단축할 수 있습니다. 이렇게 하면 문자 카운터가 단축된 URL의 예상 길이를 표시하도록 업데이트되므로 응답을 구체화하는 데 도움이 될 수 있습니다.
+
+## 새로운 Braze 파트너십
+
+### Friendbuy - 로열티
+
+Braze와 [Friendbuy의]({{site.baseurl}}/partners/message_orchestration/channel_extensions/loyalty/friendbuy/) 통합을 활용하여 이메일 및 SMS 기능을 확장하는 동시에 추천 및 로열티 프로그램 커뮤니케이션을 손쉽게 자동화할 수 있습니다. Braze는 Friendbuy를 통해 수집된 모든 옵트인 전화번호에 대한 고객 프로필을 생성합니다.
+
+### NiftyImages - 동적 콘텐츠
+
+Braze와 [NiftyImages]({{site.baseurl}}/partners/message_personalization/dynamic_content/niftyimages/)의 파트너십을 통해 기존 Braze 개인화된 태그를 NiftyImages URL에 매핑하여 이메일 캠페인을 위한 역동적인 개인화 이미지를 만들 수 있습니다.
+
+## SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Android SDK 30.4.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [Braze 세그먼트 Swift 플러그인 2.4.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md#240)
+- [Flutter SDK 9.0.0](https://pub.dev/packages/braze_plugin/changelog)
+    - 네이티브 iOS 브릿지를 [Braze Swift SDK 7.7.0에서 8.4.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...8.4.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트합니다.
+        - 최소 iOS 배포 대상이 12.0으로 업데이트되었습니다.
+    - 네이티브 Android 브릿지를 [Braze Android SDK 29.0.1에서 30.3.0으로](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트합니다.
+    - 지원되는 최소 Dart 버전은 2.15.0입니다.
+- [React Native SDK 9.2.0](https://github.com/braze-inc/braze-react-native-sdk/blob/master/CHANGELOG.md)
+- [Swift SDK 8.3.0-8.4.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+- [Swift SDK 9.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md)
+    - BrazeKit 개인정보 매니페스트에서 기본 개인정보 추적 도메인을 제거합니다.
+        - Braze [데이터 추적 기술 기능]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest/)을 사용하는 경우, 앱 수준의 개인정보 매니페스트에 추적 기술 엔드포인트를 수동으로 추가해야 합니다.
+        - 통합 지침은 업데이트된 [튜토리얼](https://braze-inc.github.io/braze-swift-sdk/tutorials/braze/e1-privacy-tracking)을 참조하세요.
+    - 더 이상 사용되지 않는 `BrazeDelegate.braze(_:sdkAuthenticationFailedWithError) method in favor of BrazeSDKAuthDelegate.braze(_:sdkAuthenticationFailedWithError)` 을 제거합니다.
+        - 이 방법은 원래 [릴리스 5.14.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/5.14.0)에서 더 이상 사용되지 않았습니다.
+        - 새 델리게이트 메서드로 전환하지 않으면 컴파일러 오류가 트리거되지 않고 정의한 `BrazeDelegate.braze(_:sdkAuthenticationFailedWithError)` 메서드가 호출되지 않을 뿐입니다.
+- [Xamarin SDK 버전 4.0.3](https://github.com/braze-inc/braze-xamarin-sdk/blob/master/CHANGELOG.md#403)
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2024/5_28_24.md b/_lang/ko/_help/release_notes/2024/5_28_24.md
new file mode 100644
index 00000000000..5d02ecb4326
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2024/5_28_24.md
@@ -0,0 +1,101 @@
+---
+nav_title: 2024년 5월 28일
+description: "이 문서에는 2024년 5월 28일의 릴리스 노트가 포함되어 있습니다."
+page_order: 7 
+page_type: reference
+---
+
+# 2024년 5월 28일 출시
+
+## 문서 사이트의 시각적 업데이트
+
+문서 웹사이트가 멋지게 바뀐 것을 눈치채셨을 것입니다! 새롭고 활기찬 Braze의 브랜드 아이덴티티를 반영하여 개편했습니다. 새 브랜드에 대한 비하인드 스토리는 [새 브랜드 공개에서 자세히 알아보세요: Braze 수석 크리에이티브 디렉터 그렉 에르델레이와의 대화](https://www.braze.com/resources/articles/unveiling-our-new-brand-a-conversation-with-braze-executive-creative-director-greg-erdelyi).
+
+## 포르투갈어 및 스페인어 지원
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 Braze를 포르투갈어와 스페인어로 이용할 수 있습니다. Braze 대시보드가 표시되는 언어를 변경하려면 [언어 설정]({{site.baseurl}}/user_guide/administrative/access_braze/language/)을 참조하세요.
+
+## 강력한 채널
+
+### 다국어 설정
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[다국어 설정]({{site.baseurl}}/multi_language_support/)을 조정하면 하나의 이메일 메시지 내에서 서로 다른 언어와 위치의 사용자를 대상으로 서로 다른 메시지를 보낼 수 있습니다. 다국어 지원을 편집하고 관리하려면 "다국어 설정 관리" 사용자 권한이 있어야 합니다. 메시지에 로캘을 추가하려면 캠페인을 편집할 수 있는 권한이 필요합니다.
+
+### 메시지 수준의 원클릭 목록-수신 취소 헤더
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+목록 수신 거부 헤더([RFC 8058](https://datatracker.ietf.org/doc/html/rfc8058))의 원클릭 수신 거부 기능은 수신자가 이메일을 쉽게 수신 거부할 수 있는 방법을 제공합니다. 이 헤더 설정을 이메일의 메시지 수준에서 적용하도록 조정할 수 있습니다. 이 설정에 대한 자세한 내용은 [워크스페이스의 이메일 수신 거부 헤더]({{site.baseurl}}/user_guide/administrative/app_settings/email_settings/#email-unsubscribe-header-in-workspaces)를 참조하세요.
+
+### 이메일 살균 정보
+
+Braze가 이메일 메시지에서 특정 유형의 JavaScript를 감지할 때 발생하는 프로세스에 대해 자세히 알아보려면 새로운 [위생 처리]({{site.baseurl}}/user_guide/message_building_by_channel/email/best_practices/sanitization) 문서를 참조하세요. 주요 목적은 악의적인 공격자가 다른 Braze 대시보드 사용자의 세션 데이터에 액세스하는 것을 방지하는 것입니다.
+
+### 콘텐츠 블록의 포함 횟수
+
+활성 캠페인 또는 캔버스에 콘텐츠 블록을 추가한 후 콘텐츠 블록을 마우스로 가리키고 <i class="fa fa-eye preview-icon"></i> **미리보기** 아이콘을 선택하면 콘텐츠 블록 라이브러리에서 [이 콘텐츠 블록을 미리 볼]({{site.baseurl}}/user_guide/engagement_tools/templates_and_media/content_blocks/) 수 있습니다.
+
+### 캔버스 상태
+
+Braze 대시보드에서 캔버스는 상태별로 그룹화되어 있습니다. 다양한 [캔버스 상태와]({{site.baseurl}}/user_guide/engagement_tools/canvas/get_started/canvas_status) 그 의미에 대한 [설명을]({{site.baseurl}}/user_guide/engagement_tools/canvas/get_started/canvas_status) 확인하세요.
+
+## AI 및 ML 자동화
+
+### AI 카피라이팅 어시스턴트를 위한 브랜드 가이드라인
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 [브랜드 가이드라인]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_copywriting/brand_guidelines/)을 생성하고 적용하여 AI 카피라이팅 어시스턴트가 생성한 카피 스타일을 브랜드에 맞게 맞춤 설정할 수 있습니다. 다양한 시나리오에 대해 여러 가지 가이드라인을 설정하여 항상 상황에 맞는 어조를 유지할 수 있습니다.
+ 
+## 새로운 Braze 파트너십
+
+### Adikteev - 애널리틱스
+
+Braze와 [Adikteev의]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/adikteev/) 통합을 통해 Braze CRM 캠페인 내에서 Adikteev의 이탈 예측 기술을 활용하여 고위험 사용자 세그먼트를 우선적으로 타겟팅함으로써 사용자 유지율을 높일 수 있습니다.
+ 
+### Celebrus - 애널리틱스
+ 
+Braze와 [Celebrus]({{site.baseurl}}/partners/data_and_infrastructure_agility/analytics/celebrus) 통합은 웹 및 모바일 앱 채널 전반에서 Braze SDK와 원활하게 통합되어 채널 활동 데이터로 Braze의 인구를 늘리는 데 도움이 됩니다. 여기에는 지정된 기간 동안 디지털 자산 전반의 방문자 트래픽에 대한 포괄적인 인사이트가 포함됩니다.
+ 
+### IAM Studio - 메시지 템플릿
+ 
+Braze와 [IAM Studio의]({{site.baseurl}}/partners/message_orchestration/channel_extensions/email_templates/iam_studio/) 통합을 통해 이미지 교체, 텍스트 수정, 딥링크 설정, 사용자 지정 속성 및 이벤트 설정을 제공하는 사용자 지정 가능한 인앱 메시지 템플릿을 Braze 인앱 메시지에 쉽게 삽입할 수 있습니다. IAM Studio를 사용하면 메시지 제작 시간을 단축하고 콘텐츠 기획에 더 많은 시간을 할애할 수 있습니다.
+ 
+### Regal - 인스턴트 채팅
+
+Braze와 [Regal]({{site.baseurl}}/partners/message_orchestration/additional_channels/messaging/regal/)을 통합하면 모든 고객 터치포인트에서 보다 일관되고 개인화된 경험을 제공할 수 있습니다.
+
+### Treasure Data - 코호트 가져오기
+ 
+Braze와 [Treasure Data]({{site.baseurl}}/partners/data_and_infrastructure_agility/cohort_import/treasuredata/) 통합을 통해 사용자 코호트를 Treasure Data에서 Braze로 가져올 수 있으므로, 웨어하우스에만 존재할 수 있는 데이터를 기반으로 타겟팅 캠페인을 보낼 수 있습니다.
+ 
+### Zapier - 워크플로 자동화
+ 
+Braze와 [Zapier의]({{site.baseurl}}/partners/data_and_infrastructure_agility/workflow_automation/zapier/) 파트너십은 Braze API와 Braze 웹훅을 활용하여 타사 애플리케이션과 연결하여 다양한 작업을 자동화합니다.
+
+## SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+
+- [Android SDK 31.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)
+- [Braze 세그먼트 Swift 플러그인 3.0.0](https://github.com/braze-inc/braze-segment-swift/blob/main/CHANGELOG.md#300)
+    - 9.2.0+ SemVer 버전 이상의 릴리스가 필요하도록 Braze Swift SDK 바인딩을 업데이트합니다.
+        - 이를 통해 9.2.0부터 10.0.0까지 모든 버전의 Braze SDK와 호환됩니다(단, 10.0.0은 포함되지 않음).
+        - 잠재적인 변경 사항에 대한 자세한 내용은 [7.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#700), [8.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#800) 및 [9.0.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#900)의 체인지로그 항목을 참조하세요.
+    - 이제 푸시 알림을 지원하려면 앱 수명 주기 초기에 애플리케이션의 `AppDelegate.application(_:didFinishLaunchingWithOptions:)` 메서드에서 정적 메서드 `BrazeDestination.prepareForDelayedInitialization()`을 호출해야 합니다.
+- [Cordova SDK 9.0.0-9.2.0](https://github.com/braze-inc/braze-cordova-sdk/blob/master/CHANGELOG.md)
+    - [Braze Swift SDK 7.7.0에서 9.0.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 네이티브 iOS 브릿지를 업데이트했습니다.
+- [Expo 플러그인 2.1.1](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md#211)
+- [Flutter SDK 10.1.0](https://pub.dev/packages/braze_plugin/changelog)
+- [React Native SDK 11.0.0](https://github.com/braze-inc/braze-react-native-sdk/blob/11.0.0/CHANGELOG.md)
+- [Swift SDK 9.1.0-9.2.0](https://github.com/braze-inc/braze-swift-sdk/blob/main/CHANGELOG.md#920)
+- Unity 6.0.0
+    - [Braze Swift SDK 7.7.0에서 9.0.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/7.7.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 네이티브 iOS 브릿지를 업데이트했습니다.
+    - 네이티브 Android 브릿지를 [Braze Android SDK 29.0.1에서 30.3.0으로](https://github.com/braze-inc/braze-android-sdk/compare/v29.0.1...v30.3.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) 업데이트했습니다.
+- [웹 SDK 5.3.1](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md)
+- Xamarin SDK 버전 5.0.0
+    - [Braze Swift SDK 8.4.0에서 9.0.0으로](https://github.com/braze-inc/braze-swift-sdk/compare/8.4.0...9.0.0#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) iOS 바인딩을 업데이트했습니다.
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2024/6_25_24.md b/_lang/ko/_help/release_notes/2024/6_25_24.md
new file mode 100644
index 00000000000..45604a539b8
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2024/6_25_24.md
@@ -0,0 +1,106 @@
+---
+nav_title: 2024년 6월 25일
+description: "이 문서에는 2024년 6월 25일의 릴리스 노트가 포함되어 있습니다."
+page_order: 6 
+page_type: reference
+---
+
+# 2024년 6월 25일 출시
+
+## 일본어 문서
+
+이제 Braze Docs에서 일본어를 지원합니다!
+
+![일본어 인터페이스가 표시된 Braze Docs 사이트][1]{: style="max-width:70%;"}
+ 
+## 데이터 유연성
+
+### API 트리거 캠페인용 첨부 파일
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 [`/campaigns/trigger/send` 엔드포인트]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_campaigns)에서 첨부 파일을 지원합니다(`/messages/send` 엔드포인트에서 이메일의 첨부 파일을 지원하는 것과 유사). 
+
+### 추가 데이터 웨어하우스 지원
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+이제 Braze [클라우드 데이터 수집(CDI)]({{site.baseurl}}/user_guide/data_and_analytics/cloud_ingestion/connected_sources)은 BigQuery, Databricks Redshift 및 Snowflake를 지원합니다.
+
+### WhatsApp 전화번호 마이그레이션
+
+메타의 임베디드 가입을 사용하여 WhatsApp 비즈니스 계정 간에 WhatsApp 전화번호를 마이그레이션하세요. [WhatsApp 전화번호 마이그레이션]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/phone_number_migration)에 대해 자세히 알아보세요.
+ 
+## 창의력 발휘
+
+### 기기별 참여
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+새로운 **디바이스별 참여도** 보고서에서는 사용자가 이메일에 참여하는 데 사용하는 디바이스에 대한 분석 정보를 제공합니다. 이 데이터는 모바일, 데스크톱, 태블릿 및 기타 기기 유형에서 이메일 인게이지먼트를 추적합니다. [보고서와 이메일 성능 대시보드]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard)에 대해 자세히 알아보세요.
+
+### 캔버스 흐름의 WhatsApp 및 SMS Liquid 속성
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[캔버스 플로우에 WhatsApp 및 SMS Liquid 속성]({{site.baseurl}}/user_guide/engagement_tools/canvas/create_a_canvas/canvas_entry_properties_event_properties)에 대한 지원을 추가했습니다. 이제 행동 경로 단계에 "SMS 인바운드 메시지 보내기" 또는 "WhatsApp 인바운드 메시지 보내기" 트리거가 포함된 경우 후속 캔버스 단계에 SMS 또는 WhatsApp Liquid 속성정보를 포함할 수 있습니다. 이는 캔버스 플로우에서 이벤트 속성정보가 작동하는 방식을 반영합니다. 이렇게 하면 메시지를 활용하여 사용자 프로필 및 대화 메시지에 대한 퍼스트 파티 데이터를 저장하고 참조할 수 있습니다.
+ 
+### 반복 캔버스의 개인화된 경로
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+캔버스에서 개인화된 경로를 사용하면 전환 가능성에 따라 개별 사용자에 대한 캔버스 여정의 모든 지점을 개인화할 수 있습니다. 이제 반복 캔버스에 개인화된 경로를 사용할 수 있습니다. [개인화된 이형]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths) 상품에 대해 자세히 알아보세요.
+
+### 세그먼트 문제 해결
+
+세그먼트로 작업하시나요? 다음은 몇 가지 [문제 해결 단계 및 유의해야 할 사항]({{site.baseurl}}/user_guide/engagement_tools/segments/troubleshooting)입니다.
+
+### 리퀴드 하이라이트
+
+접근성 가이드라인을 더 잘 지원하기 위해 [Liquid에서 사용하는 색상 코딩을]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/liquid) 개선했습니다.
+
+![]({% image_buster /assets/img/liquid_color_code.png %})
+ 
+## 강력한 채널
+
+### SMS 지리적 권한
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+SMS 지리적 권한은 SMS 메시지를 보낼 수 있는 국가에 대한 제어를 적용하여 보안을 강화하고 사기성 SMS 트래픽으로부터 보호합니다. 이제 관리자는 허용 국가 목록을 지정하여 SMS 메시지가 승인된 지역으로만 전송되도록 할 수 있습니다. 자세한 내용은 [SMS 지리적 권한에서]({{site.baseurl}}/sms_geographic_permissions) 확인하세요. 
+
+![가장 일반적인 국가가 상단에 표시되는 '국가 허용 목록' 드롭다운이 표시됩니다.][2]{: style="max-width:80%;"}
+
+### SMS/MMS 모범 사례
+
+수신 거부 모니터링 및 트래픽 펌핑에 대한 권장 사항을 포함하여 [Braze를 사용한 SMS/MMS 모범 사례에]({{site.baseurl}}/user_guide/message_building_by_channel/sms/best_practices/best_practices) 대해 자세히 알아보세요. 
+
+### 푸시 수신 거부 추적 기술
+
+새로운 [도움말 문서]({{site.baseurl}}/help/help_articles/push/push_unsubscribes)에서 푸시 수신 거부 추적 기술에 대한 몇 가지 팁을 확인하세요.
+
+### Shopify `checkout.liquid` 사용 중단
+
+Shopify `checkout.liquid`에 대한 지원은 2024년 8월에 지원 중단이 시작되어 2025년 8월에 종료됩니다. Braze가 [이 전환을 어떻게 처리할지]({{site.baseurl}}/help/release_notes/deprecations/shopify_checkout) 자세히 알아보세요. 
+
+## SDK 업데이트
+ 
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+ 
+- [Swift SDK 9.3.0](https://github.com/braze-inc/braze-swift-sdk/releases/tag/9.3.0)
+    - 기존 기능 플래그 API를 더 이상 사용하지 않으며, 향후 버전에서 제거될 예정입니다.
+        - `Braze.FeatureFlag.jsonStringProperty(key:)` 는 더 이상 사용되지 않습니다.
+        - `Braze.FeatureFlag.jsonObjectProperty(key:)`는 `Braze.FeatureFlag.jsonProperty(key:)`를 위해 더 이상 사용되지 않습니다.
+- [Roku SDK 2.2.0](https://github.com/braze-inc/braze-roku-sdk/blob/main/CHANGELOG.md)
+- [Braze Expo 플러그인 2.1.2](https://github.com/braze-inc/braze-expo-plugin/blob/main/CHANGELOG.md)
+
+### tvOS 문서
+
+몇 달 전, 실수로 [tvOS 콘텐츠 카드]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/content_cards/tvos) 및 [인앱 메시징]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/in-app_messaging/customization/tvos)에 대한 설명서가 더 이상 사용되지 않게 되었습니다. 이 설명서는 이제 Braze 문서의 Swift 섹션에 다시 게시되었습니다.
+
+{% alert note %}
+Braze 설명서의 [기여자]({{site.baseurl}}/contributing/home)는 이제 사이트가 Ruby 3.3.0에서 실행된다는 점에 유의하세요. 필요에 따라 Ruby 버전을 업그레이드하세요.
+{% endalert %}
+
+[1]: {% image_buster /assets/img/braze-docs-japan.png %}
+[2]: {% image_buster /assets/img/sms/allowlist_dropdown.png %}
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/2024/7_23_24.md b/_lang/ko/_help/release_notes/2024/7_23_24.md
new file mode 100644
index 00000000000..c1a4dbb6d1f
--- /dev/null
+++ b/_lang/ko/_help/release_notes/2024/7_23_24.md
@@ -0,0 +1,121 @@
+---
+nav_title: 2024년 7월 23일
+description: "이 문서에는 2024년 7월 23일의 릴리스 노트가 포함되어 있습니다."
+page_order: 5
+page_type: reference
+---
+ 
+# 2024년 7월 23일 출시
+
+## Braze 문서 업데이트
+
+### Diátaxis 및 Braze 문서
+
+현재 [Diátaxis](https://diataxis.fr/)라는 프레임워크를 사용하여 설명서 표준화하는 작업을 진행 중입니다. 작가와 기여자가 이 새로운 프레임워크에 맞는 콘텐츠를 만들 수 있도록 [각 콘텐츠 유형에 맞는 템플릿을 만들었습니다]({{site.baseurl}}/contributing/content_types).
+
+### Braze 문서를 위한 새로운 풀-리퀘스트 템플릿
+
+시간을 들여 풀 리퀘스트(PR) 템플릿을 개선하여 더 쉽고 혼란스럽지 않게 [Braze 설명서에 기여하실]({{site.baseurl}}/contributing/home/) 수 있도록 했습니다. 그래도 개선의 여지가 있다고 생각되면 PR을 개설하거나 [이슈를 제출하세요](https://github.com/braze-inc/braze-docs/issues/new?assignees=&labels=enhancement&projects=&template=request_a_feature.md&title=). 모든 게 더 쉬워졌습니다!
+ 
+## 데이터 유연성
+
+### 사용자 지정 이벤트 및 속성 내보내기
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[`/custom_attributes`]({{site.baseurl}}/api/endpoints/export/custom_attributes/get_custom_attributes) 및 [`/events`]({{site.baseurl}}/api/endpoints/export/custom_events/get_custom_events_data) API 엔드포인트를 통한 내보내기는 더 이상 얼리 액세스로 제공되지 않습니다.
+
+### 사용자를 위한 새로운 커런츠 권한
+
+사용자를 위한 두 가지 새로운 권한 설정이 있습니다: **전류 통합 보기** 및 **전류 통합 편집하기**. [여기에서]({{site.baseurl}}/user_guide/administrative/app_settings/manage_your_braze_users/user_permissions) 사용자 권한에 대해 자세히 알아보세요. 
+
+### Snowflake 데이터 유지 정책 업데이트
+ 
+8월 27일부터 2년이 지난 모든 Snowflake 보안 데이터 공유 이벤트 데이터에서 개인 식별 정보(PII)가 삭제됩니다. Snowflake를 사용하는 경우 유지 정책이 적용되기 전에 Snowflake 계정에 사본을 저장하여 환경의 전체 이벤트 데이터를 유지하도록 선택할 수 있습니다. 자세히 알아보려면 [Snowflake 데이터 유지]({{site.baseurl}}/partners/data_and_infrastructure_agility/data_warehouses/snowflake/data_retention/)를 참조하세요.
+ 
+## 창의력 발휘
+
+### 여러 페이지로 구성된 인앱 메시지
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+인앱 메시지에 페이지를 추가하면 온보딩 흐름이나 환영 여정과 같은 순차적인 흐름을 통해 사용자를 안내할 수 있습니다. 자세한 내용은 [드래그 앤 드롭으로 인앱 메시지 만들기]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/drag_and_drop/create#multi-page)를 참조하세요.
+
+### Liquid를 사용한 링크 단축
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+[Liquid를 사용하여 URL을 개인화]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/#enabling-link-shortening)하면 SMS 메시지에 포함된 URL을 자동으로 단축하고 클릭률 분석을 수집할 수 있습니다. 사용해 보려면 [링크 단축을]({{site.baseurl}}/user_guide/message_building_by_channel/sms/campaign/link_shortening/) 참조하세요.
+
+### 카탈로그용 API 예제
+
+배열 필드를 사용하는 `/catalogs` 엔드포인트에 대한 예제를 추가했습니다. 예시를 보려면 다음을 확인하세요:
+
+- [여러 카탈로그 항목 편집]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/patch_catalog_items_bulk)
+- [여러 카탈로그 항목 만들기]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/post_create_catalog_items_bulk)
+- [카탈로그 항목 업데이트]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/asynchronous/put_update_catalog_items)
+- [카탈로그 항목 편집]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/patch_catalog_item)
+- [카탈로그 항목 생성]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/post_create_catalog_item)
+- [카탈로그 항목 업데이트]({{site.baseurl}}/api/endpoints/catalogs/catalog_items/synchronous/put_update_catalog_item)
+- [카탈로그 만들기]({{site.baseurl}}/api/endpoints/catalogs/catalog_management/synchronous/post_create_catalog)
+ 
+## 강력한 채널
+
+## 여러 개의 WhatsApp 비즈니스 계정
+
+{% multi_lang_include release_type.md release="일반 사용 가능" %}
+
+이제 각 워크스페이스에 여러 개의 WhatsApp 비즈니스 계정과 구독 그룹(및 전화번호)을 추가할 수 있습니다. 자세한 내용은 [다중 WhatsApp 비즈니스 계정]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/overview/multiple_subscription_groups)을 참조하세요. 
+
+### SMS 지리적 허용
+
+SMS 지리적 권한은 SMS 메시지를 보낼 수 있는 국가에 대한 제어를 적용하여 보안을 강화하고 사기성 SMS 트래픽으로부터 보호합니다. SMS 메시지를 승인된 지역으로만 보낼 수 있도록 국가 허용 목록을 지정하는 방법을 알아보려면 [SMS 국가 허용 목록 구성하기를]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_geographic_permissions/#configuring-your-sms-country-allowlist) 참조하세요.
+
+### LINE과 Braze
+
+{% multi_lang_include release_type.md release="베타" %}
+
+[LINE](https://www.lycbiz.com/sites/default/files/media/jp/download/LINE%20Business%20Guide_202310-202403.pdf)은 일본에서 가장 인기 있는 메시징 앱으로, 월간 활성 사용자가 9,500만 명이 넘습니다. LINE 계정을 Braze와 통합하여 자사 및 타사 고객 데이터를 활용하여 고객의 선호도, 행동, 크로스채널 상호 작용을 기반으로 적합한 고객에게 매력적인 LINE 메시지를 보낼 수 있습니다. 시작하려면 [LINE]({{site.baseurl}}/line)을 참조하세요.
+
+### Shopify: 가격 인하 및 재입고
+
+{% multi_lang_include release_type.md release="조기 액세스" %}
+
+이제 Shopify를 사용하면 [가격 인하]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/price_drop_notifications) 및 [품절 품목에]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/back_in_stock_notifications) 대한 사용자 지정 알림을 생성할 수 있습니다.
+ 
+## AI 및 ML 자동화
+ 
+### 중복 사용자에 대한 규칙 기반 병합
+
+이전에는 Braze에서 중복 사용자를 개별적으로 또는 일괄적으로 찾아서 병합할 수 있었습니다. 이제 중복 확인 방법을 제어하는 규칙을 만들어 가장 관련성이 높은 사용자를 유지하도록 할 수 있습니다. 자세히 알아보려면 [규칙 기반 병합]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users/#rules-based-merging)을 참조하세요.
+
+### AI Liquid 어시스턴트
+
+{% multi_lang_include release_type.md release="베타" %}
+
+Sage AI Liquid 어시스턴트는 메시지 콘텐츠를 개인화하는 데 필요한 Liquid를 생성하는 것을 돕는 Sage AI 기반의 채팅 도우미입니다. 템플릿에서 Liquid를 생성하고, 개인화된 Liquid 제안을 받고, Sage AI의 지원을 받아 기존 Liquid를 최적화할 수 있습니다. AI Liquid 도우미는 사용된 Liquid를 설명하는 주석도 제공하므로 Liquid에 대한 이해를 높이고 직접 작성하는 방법을 배울 수 있습니다.
+
+시작하려면 [AI Liquid 어시스턴트]({{site.baseurl}}/user_guide/sage_ai/generative_ai/ai_liquid)를 참조하세요.
+ 
+## SDK
+ 
+### Android SDK 로그
+
+앱에서 더 쉽게 읽고 사용할 수 있도록 [Braze Android SDK의 로깅 설명서]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/additional_customization_and_configuration/#logging)를 개편했습니다. 또한 각 로그 수준에 대한 설명도 추가했습니다.
+
+### iOS SDK 포그라운드 푸시 알림
+
+이제 Braze iOS SDK의 `subscribeToUpdates` 메서드가 포그라운드 푸시 알림 수신 여부를 감지할 수 있습니다. 자세히 알아보려면 [iOS 푸시 알림 통합]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/push_notifications/integration)을 참조하세요.
+ 
+### Xamarin 문서 업데이트
+ 
+[버전 4.0.0](https://github.com/braze-inc/braze-xamarin-sdk/releases/tag/4.0.0)부터 Braze Xamarin SDK는 Swift SDK 바인딩을 사용하므로 코드 스니펫과 참조 자료를 업데이트했습니다. 또한 읽고 이해하기 쉽도록 섹션을 재구성했습니다. 자세한 내용은 [Xamarin 문서를]({{site.baseurl}}/developer_guide/platform_integration_guides/xamarin/initial_sdk_setup) 참조하세요.
+
+### SDK 업데이트
+
+다음 SDK 업데이트가 릴리스되었습니다. 주요 업데이트는 아래에 나열되어 있으며, 그 외의 모든 업데이트는 해당 SDK 체인지로그를 확인하면 확인할 수 있습니다.
+ 
+- [Swift SDK 9.3.1](https://github.com/braze-inc/braze-swift-sdk/releases/tag/9.3.1)
+- [웹 SDK 5.3.2](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#532)
+    - 5.2.0에서 외부 스크립트가 동기식으로 로드될 때 HTML 인앱 메시지가 잘못 렌더링될 수 있는 회귀 현상을 수정했습니다.
+- [웹 SDK 5.4.0](https://github.com/braze-inc/braze-web-sdk/blob/master/CHANGELOG.md#540)
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/deprecations.md b/_lang/ko/_help/release_notes/deprecations.md
new file mode 100644
index 00000000000..555974ba962
--- /dev/null
+++ b/_lang/ko/_help/release_notes/deprecations.md
@@ -0,0 +1,148 @@
+---
+nav_title: 사용 중단
+article_title: 사용 중단
+page_order: 9
+page_type: reference
+description: "이 페이지에는 더 이상 사용되지 않는 문서에 대한 참조가 포함되어 있으며 더 이상 사용되지 않는 기능 및 지원되지 않는 기능의 목록이 제공됩니다."
+---
+
+# 사용 중단
+
+기술은 항상 Braze 내부와 외부에서 움직이고 있습니다! 그리고 Braze는 이에 발맞추기 위해 최선을 다하고 있습니다. 이 문서에서는 Braze의 기원과 기술, 즉 "지난 시대"에 사람들을 어떻게 지원했는지 살펴볼 수 있습니다.
+
+더 이상 존재하지 않는 연동 서비스나 기능에 대한 용어를 검색하다가 이 페이지에 오셨을 수도 있습니다. 이는 기술 업계의 진행 상황과 움직임에 대한 정보를 제공하기 위한 시도입니다. 다음 링크를 방문하여 더 이상 사용되지 않는 기능 및 지원되지 않는 기능 목록을 확인하고 사용되지 않는 도움말을 읽을 수 있습니다.
+
+## 더 이상 사용되지 않는 문서
+
+- [Android용 맞춤형 푸시 브로드캐스트 수신기]({{site.baseurl}}/help/release_notes/deprecations/custom_broadcast_receiver/)
+- [Eclipse SDK 설정]({{site.baseurl}}/help/release_notes/deprecations/eclipse_setup_deprecated/)
+- [TLS 1.0 및 1.1 사용 중단]({{site.baseurl}}/help/release_notes/deprecations/tls_deprecation/)
+- [Twilio 웹훅 통합]({{site.baseurl}}/help/release_notes/deprecations/twilio/)
+- [파트너십 최적화]({{site.baseurl}}/help/release_notes/deprecations/apptimize/)
+- [Grouparoo 파트너십]({{site.baseurl}}/help/release_notes/deprecations/grouparoo)
+- [Shopify `checkout.liquid` 사용 중단]({{site.baseurl}}/help/release_notes/deprecations/shopify_checkout/)
+
+## 사용 중단 로그
+
+### Shopify `checkout.liquid`
+
+**지원 철회**: 2024년 8월(1단계), 2025년 8월(2단계)
+
+Shopify 에 대한 지원`checkout.liquid` 은 2024년 8월에 중단되기 시작하여 2025년 8월에 종료됩니다. Shopify는 더 안전하고 성능이 뛰어나며 사용자 지정이 가능한 [Checkout 확장성으로](https://www.shopify.com/enterprise/blog/checkout-extensibility-winter-editions) 전환할 예정입니다.
+
+### Android용 맞춤형 푸시 브로드캐스트 수신기
+
+**지원 철회**: 2022년 10월
+
+푸시 알림에 사용자 지정 `BroadcastReceiver` 사용은 더 이상 사용되지 않습니다. 대신 [` subscribeToPushNotificationEvents()`](/docs/developer_guide/platform_integration_guides/android/push_notifications/android/customization/custom_event_callback/) 대신 사용하세요.
+
+### Grouparoo 파트너십
+
+**지원 철회**: 2022년 4월
+
+Grouparoo에 대한 지원은 2022년 4월부터 중단되었습니다.
+
+### Braze Windows SDK
+
+**2022년 3월 24일**: Braze Windows SDK는 더 이상 사용되지 않으며, Braze 대시보드에서 새로운 Windows 앱을 만들 수 없습니다.<br>
+**2022년 9월 15일**: Windows 앱에 새 메시지를 보낼 수 없습니다. 기존 메시지 및 데이터 수집은 영향을 받지 않습니다.<br>
+**2024년 1월 11일**: Braze는 더 이상 Windows 앱에서 메시지를 제공하거나 데이터를 수집하지 않습니다.
+
+### Baidu 푸시 통합
+
+**2022년 3월 24일**: Braze 바이두 푸시 통합은 더 이상 사용되지 않으며, Braze 대시보드에서 새로운 바이두 앱을 만들 수 없습니다. <br>
+**2022년 9월 15일**: 새로운 Baidu 푸시 메시지를 만들 수 없습니다. 기존 메시지 및 데이터 수집은 영향을 받지 않습니다.<br>
+**2024년 1월 11일**: Braze는 더 이상 Baidu 앱에서 메시지를 제공하거나 데이터를 수집하지 않습니다.
+
+### appboyBridge 전역 변수
+
+**지원 철회**: 2021년 5월<br>
+**대체됨**: `brazeBridge`
+
+`appboyBridge` 글로벌 변수는 더 이상 사용되지 않으며 `brazeBridge` 로 대체됩니다. `appboyBridge`는 기존 고객에게는 계속 작동하지만 `appboyBridge`를 사용 중인 경우 `brazeBridge`로 마이그레이션하는 것이 좋습니다.
+
+### Amazon Moments 파트너십
+
+**지원 철회**: 2020년 6월
+
+Amazon Moments에 대한 지원은 2020년 6월부터 중단되었습니다. Amazon Moments가 Amazon Advertising에 통합되어 해당 API와 연동이 더 이상 사용되지 않습니다.
+
+### 사실적인 파트너십
+
+**지원 철회**: 2020년 6월
+
+Factual에 대한 지원은 2020년 6월부로 중단되었습니다. 최근 Foursquare가 인수한 Factual은 더 이상 Braze 플랫폼과 통합되지 않습니다.
+
+### Twilio 웹훅 통합
+
+**지원 철회**: 2020년 1월
+
+2020년 1월 31일부로 [Twilio 웹훅 통합]({{site.baseurl}}/partners/twilio/)에 대한 지원이 중단되었습니다. Braze에서 여전히 SMS 서비스에 액세스하려면 [SMS 문서를]({{site.baseurl}}/user_guide/message_building_by_channel/sms/) 참조하세요.
+
+### 파트너십 최적화
+
+**지원 철회**: 2019년 8월
+
+현재 [Braze와 함께 Apptimize]({{site.baseurl}}/help/release_notes/deprecations/apptimize)를 사용 중인 경우 서비스 중단은 발생하지 않습니다. 여전히 Apptimize 커스텀 속성을 Braze 고객 프로필에 설정할 수 있습니다. 그러나 파트너와의 공식적인 에스컬레이션 지원은 제공되지 않습니다.
+
+### 인앱 메시지 원본
+
+**지원 철회:** 2019년 2월<br>
+**대체됨**: [인앱 메시징]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/creating_an_in-app_message)
+
+Braze는 최신 UX 및 UI 모범 사례를 준수하도록 인앱 메시지의 모양과 느낌을 개선했으며, 더 이상 기존 인앱 메시지를 지원하지 않습니다.
+
+Braze는 다음 SDK 릴리스에서 새로운 형태의 인앱 메시지로 전환했습니다.
+- iOS: `2.19.0`
+- Android: `1.13.0`
+- 웹: `1.3.0`
+
+이번 릴리스 이전에는 Braze에서 "원본 인앱 메시지"를 지원했습니다. 이전에는 새 릴리스 이전에 인앱 캠페인을 실행한 모든 고객에게 오리지널 인앱 메시지에 대한 지원이 제공되었습니다. 모든 캠페인 통계는 변경 사항의 영향을 받지 않았으며, 기존 인앱 메시지를 보낸 사람들은 **캠페인** 페이지의 **캠페인 만들기** 버튼을 통해 다른 사람들에게 메시지를 보낼 수 있었습니다.
+
+### 피드백 위젯
+
+**지원 철회**: 2019년 7월 1일.
+
+Braze SDK는 앱에 추가할 수 있는 피드백 위젯을 제공하여 사용자가 `submitfeedback` 메서드를 사용하여 피드백을 남기고 Desk.com 또는 Zendesk로 전달할 수 있도록 하며 대시보드에서 관리합니다.
+
+### Google 클라우드 메시징(GCM)
+
+**지원 철회**: Braze 지원 중단: 2018년 7월, Google 지원 중단: 2019년 5월 29일<br>
+**대체됨**: [Firebase 클라우드 메시징(FCM)]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/integration/standard_integration/#step-1-enable-firebase)
+
+Google은 2019년 5월 29일부로 [GCM에 대한 지원을 중단했습니다](https://developers.googleblog.com/2018/04/time-to-upgrade-from-gcm-to-fcm.html). Braze는 2018년 7월에 Android SDK에서 GCM에 대한 지원을 중단했으며, 이는 [Android SDK 체인지로그](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md)에 명시되어 있습니다. 즉, 기존 GCM 토큰은 계속 작동하며 기존 사용자에게 메시지를 보낼 수 있습니다. 그러나 새 사용자에게는 메시지를 보낼 수 없습니다.
+
+아직 [FCM(Firebase Cloud Messaging)]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/integration/standard_integration/#step-1-enable-firebase) 으로 마이그레이션하지 않은 고객은 이 변경 사항의 영향을 받을 수 있습니다.
+
+FCM으로 전환하지 않은 경우 모든 GCM 푸시 토큰 등록이 실패합니다. 현재 앱이 GCM을 지원하는 경우 개발팀과 협력하여 [GCM에서 FCM(파이어베이스 클라우드 메시징)으로 전환](https://developers.google.com/cloud-messaging/android/android-migrate-fcm)해야 합니다.
+
+### Eclipse
+
+**지원 철회**: 2014-2015<br>
+**대체됨**: [Android 스튜디오]({{site.baseurl}}/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/#using-android-studio)
+
+Braze는 Eclipse Android 개발자 도구(ADT) 플러그인에 대한 Google의 [서비스 종료](http://android-developers.blogspot.com/2015/06/an-update-on-eclipse-android-developer.html)로 인해 Eclipse IDE에 대한 지원을 중단했습니다. 
+
+마이그레이션 전에 Eclipse 통합에 대한 도움이 필요한 경우 [지원팀]({{site.baseurl}}/support_contact/)에 문의하여 도움을 받으세요.
+
+### 원시 이벤트 스트림(RES)
+
+**지원 철회**: 2018년 7월<br>
+**대체됨**: [커런츠]({{site.baseurl}}/partners/braze_currents/about/)
+
+원시 이벤트 스트림은 [커런츠]({{site.baseurl}}/partners/braze_currents/about/)의 전신으로, 향후 Braze 데이터를 위한 공간을 마련하기 위해 더 이상 사용되지 않습니다.
+
+### 유휴 상태에서의 지연 - GCM 기능
+
+**지원 철회**: 2016년 11월
+
+유휴 상태 동안 지연 매개변수는 이전에는 [GCM 푸시 옵션](https://developers.google.com/cloud-messaging/http-server-ref)의 일부였습니다. Google은 2016년 11월 15일에 이 옵션에 대한 지원을 철회했습니다. 이전에는 **true**로 설정하면 기기가 활성화될 때까지 메시지를 보내지 않아야 함을 나타냅니다.
+
+### 사용자 지정 엔드포인트
+
+**지원 철회**: 2019년 12월
+
+사용자 지정 엔드포인트 제거. 사용자 지정 엔드포인트가 있는 경우 계속 사용할 수 있지만 Braze에서는 더 이상 제공하지 않습니다.
+
+
+[15]: {% image_buster /assets/img_archive/in-app-choices.png %}
diff --git a/_lang/ko/_help/release_notes/deprecations/apptimize.md b/_lang/ko/_help/release_notes/deprecations/apptimize.md
new file mode 100644
index 00000000000..da4039ce8b5
--- /dev/null
+++ b/_lang/ko/_help/release_notes/deprecations/apptimize.md
@@ -0,0 +1,404 @@
+---
+nav_title: Apptimize 파트너십
+page_order: 0
+
+page_type: update
+description: "이 아카이브 문서에서는 Apptimize와 Braze의 파트너십에 대해 설명합니다. Braze는 2019년 9월부터 Apptimize 파트너십에 대한 지원을 중단했습니다."
+---
+
+# Apptimize
+
+{% alert update %}
+Braze는 2019년 9월부터 Apptimize 파트너십에 대한 지원을 중단했습니다.
+
+<br>
+
+현재 Braze와 함께 Apptimize를 사용 중인 경우 서비스 중단은 발생하지 않습니다. 여전히 Apptimize 커스텀 속성을 Braze 고객 프로필에 설정할 수 있습니다. 그러나 파트너와의 공식적인 에스컬레이션 지원은 제공되지 않습니다.
+
+<br>
+
+추가 질문이 있는 경우 Braze 또는 Apptimize 담당자에게 문의하세요.
+{% endalert %}
+
+
+[Apptimize](https://apptimize.com/)는 모바일 앱 테스트 및 성장 플랫폼이며
+이를 이용하면 고객이 앱 개발 프로세스 전반을 빠르게 반복할 수 있습니다.
+
+Apptimize와 Braze를 함께 사용하여 성장
+마케팅/CRM 전략으 실험을 두 플랫폼 전반에 걸쳐 실험과 데이터를 동기화하여 제품 UI 테스트를
+보완할 수 있습니다.
+
+## 사용 사례
+
+Braze와 Apptimize를 함께 사용하면 두 플랫폼을 함께 활용하여
+강력한 엔드투엔드 경험을 만들 수 있습니다.
+
+* 맞춤형 프로모션을 위해 인앱 및 CRM 마케팅 경험을 동기화하세요.
+* Apptimize에서 새로운 온보딩 경험을 테스트하고, Braze를 사용하여 새로운 흐름 전반에 걸쳐 사용자를 육성하세요.
+* 적절한 사용자 메시지와 함께 제품 기능 구성을 동시에 테스트할 수 있습니다.
+* 다양한 사용자 세그먼트에 맞게 인앱 경험과 적절한 메시지를 맞춤 설정할 수 있습니다.
+
+## 작동 원리
+
+Braze와 Apptimize를 함께 통합하여 SDK에서 SDK로 데이터를 전달할 수 있습니다.
+활성 Apptimize A/B 테스트 그룹을 다시 Braze에 동기화하여
+푸시, 이메일 또는 인앱 메시징을 통해 Braze 내 특정 Apptimize 테스트의 사용자를
+리타겟팅할 수 있습니다.
+
+Apptimize 실험 데이터를 바탕으로 Braze와 Apptimize SDK가
+어떻게 데이터를 전달하여 커스텀 타겟팅 및 세분화를 지원하는지 보여주는 샘플 통합 코드가 준비되어 있습니다.
+실험 데이터를 최적화합니다.
+
+이 샘플 통합은 사용자의 Braze 사용자에 대한 사용자 지정 속성을 설정합니다.
+다음 Apptimize 데이터에 대한 프로필:
+
+* 사용자가 현재 등록되어 있는 활성 실험의 전체 목록입니다.
+* 완료된 실험을 포함하여 사용자가 등록한 모든 실험의 전체 목록입니다.
+* 사용자가 실험 참여의 일부로 본 배리언트입니다.
+
+> 피처 플래그는 피처 플래그가 켜져 있는지 여부가 유일한 배리언트인 실험으로 간주됩니다. 기능 플래그가 꺼져 있으면 데이터가 보고되지 않습니다.
+
+또한, 이 통합은 첫 번째 Braze 커스텀 이벤트를 기록합니다.
+실험 참여 이벤트입니다. 이 작업은 두 가지 방법 중 하나로 수행할 수 있습니다.
+
+* 실험 이름, 실험 ID, 배리언트 상품 이름 및 배리언트 상품 ID를 나타내는 속성정보 데이터로 커스텀 이벤트가 생성됩니다. 그런 다음 Braze의 실행 기반 전달 캠페인과 캔버스를 사용하여 실시간 트리거링을 통해 사용자를 리타겟팅할 수 있습니다. 이러한 속성을 사용하여 트리거할 정확한 Apptimize 실험을 식별할 수 있습니다.
+* 발생한 모든 참여에 대한 항목이 포함된 속성 배열이 생성됩니다. 각 참여의 형식은 다음과 같습니다. `experiment_id_EXPERIMENT_ID:variant_id_VARIANT_ID:experiment_name_EXPERIMENT_NAME:variant_name_VARIANT_NAME`
+
+그런 다음 Braze의 실행 기반 전달 캠페인 또는 캔버스를 사용하여
+이러한 이벤트가 트리거되었을 때 실시간으로 사용자에게 후속 메시지를 보낼 수 있습니다.
+
+## 통합
+
+### iOS
+앱과 통합하려면 다음 `Appboy-Apptimize.m` 및
+`Apptimize-Appboy.h` 파일을 Xcode 프로젝트로 가져오고 `Appboy-Apptimize.h` 헤더를
+AppDelegate 구현에 추가하고
+Appboy와 Apptimize를 모두 초기화한 후 `didFinishLaunchingWithOptions`에 다음을 추가합니다.
+
+```objc
+[ApptimizeAppboy setupExperimentTracking];
+```
+
+#### Appboy-Apptimize.h:
+
+```objc
+//  Apptimize-Appboy.h
+
+#ifndef Apptimize_Appboy_h
+#define Apptimize_Appboy_h
+
+@interface ApptimizeAppboy : NSObject
++ (void)setupExperimentTracking;
+@end
+
+#endif /* Apptimize_Appboy_h */
+```
+
+#### Appboy-Apptimize.m:
+
+```objc
+//  Apptimize-Appboy.m
+
+#import <Foundation/Foundation.h>
+
+#import "Apptimize-Appboy.h"
+
+#import <Apptimize/Apptimize.h>
+#import <Apptimize/Apptimize+Variables.h>
+
+#import "Appboy.h"
+#import "ABKUser.h"
+
+// Key to store previous enrollment dictionary to check against to see if enrollment has changed
+NSString *const ApptimizeAppboyTestEnrollmentStorageKey = @"ApptimizeAppboyTestEnrollmentStorageKey";
+
+@implementation ApptimizeAppboy
+
++ (void)setupExperimentTracking
+{
+    // Track for enrollment changes
+    [[NSNotificationCenter defaultCenter] addObserver:self
+                                                selector:@selector(apptimizeTestsProcessed:)
+                                                    name:ApptimizeTestsProcessedNotification
+                                                object:nil];
+    // Track for participation events
+    [[NSNotificationCenter defaultCenter] addObserver:self
+                                                selector:@selector(experimentDidGetViewed:)
+                                                    name:ApptimizeTestRunNotification
+                                                object:nil];
+}
+
++ (void)apptimizeTestsProcessed:(NSNotification*)notification
+{
+    NSLog(@"Appboy-Apptimize integration processing new Apptimize tests");
+    [self updateForNewTests];
+}
+
++ (void)updateForNewTests
+{
+    NSDictionary *savedEnrollmentDictionary = [[NSUserDefaults standardUserDefaults] objectForKey:ApptimizeAppboyTestEnrollmentStorageKey];
+    NSDictionary *currentEnrollmentDictionary = [self getEnrollmentDictionaryFromTestInfo];
+
+    BOOL enrollmentChanged = NO;
+
+    for (id key in currentEnrollmentDictionary) {
+        if (![savedEnrollmentDictionary[key] isEqualToString:currentEnrollmentDictionary[key]]) {
+            enrollmentChanged = YES;
+            NSString *testAttributeKey = [@"apptimize_test_" stringByAppendingString:key];
+            [[Appboy sharedInstance].user addToCustomAttributeArrayWithKey:testAttributeKeyvalue :currentEnrollmentDictionary[key]];
+        }
+    }
+
+    if (currentEnrollmentDictionary.count != savedEnrollmentDictionary.count) {
+        enrollmentChanged = YES;
+    }
+
+    if (enrollmentChanged) {
+        [[Appboy sharedInstance].user setCustomAttributeArrayWithKey:@"active_apptimize_tests" array:currentEnrollmentDictionary.allKeys];
+
+        for (id key in currentEnrollmentDictionary.allKeys) {
+            [[Appboy sharedInstance].user addToCustomAttributeArrayWithKey:@"all_apptimize_tests" value:key];
+        }
+
+        [[NSUserDefaults standardUserDefaults] setObject:currentEnrollmentDictionary forKey:ApptimizeAppboyTestEnrollmentStorageKey];
+        [[NSUserDefaults standardUserDefaults] synchronize];
+    }
+}
+
+// Dictionary with variant IDs keyed by test ID, both as NSStrings
++ (NSMutableDictionary *)getEnrollmentDictionaryFromTestInfo
+{
+    NSMutableDictionary *enrollmentDictionary = [NSMutableDictionary dictionary];
+
+    for(id key in [Apptimize testInfo]) {
+        NSLog(@"key=%@ value=%@", key, [[Apptimize testInfo] objectForKey:key]);
+        NSDictionary<ApptimizeTestInfo> *testInfo = [[Apptimize testInfo] objectForKey:key];
+        enrollmentDictionary[[testInfo.testID stringValue]] = [testInfo.enrolledVariantID stringValue];
+    }
+
+    return enrollmentDictionary;
+}
+
++ (void)experimentDidGetViewed:(NSNotification*)notification
+{
+    if (![notification.userInfo[ApptimizeTestFirstRunUserInfoKey] boolValue]) {
+        return;
+    }
+
+    // Apptimize doesn't notify with IDs, so we iterate over all experiments to find the matching one.
+    NSString *name = notification.userInfo[ApptimizeTestNameUserInfoKey];
+    NSString *variant = notification.userInfo[ApptimizeVariantNameUserInfoKey];
+
+    [[Apptimize testInfo] enumerateKeysAndObjectsUsingBlock:^(id key, id<ApptimizeTestInfo> experiment, BOOL *stop) {
+        BOOL match = [experiment.testName isEqualToString:name] && [experiment.enrolledVariantName isEqualToString:variant];
+        if (!match) {
+            return;
+        }
+
+        // If you want to log a custom event for each participation
+        [[Appboy sharedInstance] logCustomEvent:@"apptimize_experiment_viewed"
+                                    withProperties: @{@"apptimize_experiment_name" : [experiment testName],
+                                                        @"apptimize_variant_name" : [experiment enrolledVariantName],
+                                                        @"apptimize_experiment_id" : [experiment testID],
+                                                        @"apptimize_variant_id" : [experiment enrolledVariantID]}];
+
+        // If you want a custom attribute array set for each participation
+        [[Appboy sharedInstance].user addToCustomAttributeArrayWithKey:@"apptimize_experiments"
+                                                                    value:[NSString stringWithFormat:@"experiment_id_%@:variant_id_%@:experiment_name_%@:variant_name_%@",
+                                                                            [experiment testID], [experiment enrolledVariantID], [experiment testName], [experiment enrolledVariantName] ]];
+        *stop = YES;
+    }];
+}
+
+@end
+```
+
+### Android
+
+`apptimizeappboy.java` 클래스를 앱으로 가져오고 기본 `activity`
+구현, `appboyApptimizeIntegration` 개인 구성원을 만듭니다.
+
+```java
+private ApptimizeAppboy appboyApptimizeIntegration;
+```
+
+그런 다음 onCreate 메서드에서 Braze 및 Apptimize를 초기화한 후 사용합니다.
+
+```java
+appboyApptimizeIntegration = new ApptimizeAppboy();
+appboyApptimizeIntegration.configureExperimentTracking(this);
+```    
+
+#### ApptimizeAppboy.java:
+
+```java
+package com.apptimize.appboykit;
+
+import java.io.File;
+import java.io.FileInputStream;
+import java.io.FileOutputStream;
+import java.io.ObjectInputStream;
+import java.io.ObjectOutputStream;
+import java.util.Map;
+import java.util.HashMap;
+import android.util.Log;
+
+import android.content.Context;
+
+import com.apptimize.Apptimize;
+import com.apptimize.ApptimizeTestInfo;
+import com.apptimize.Apptimize.OnExperimentsProcessedListener;
+import com.apptimize.Apptimize.OnExperimentRunListener;
+
+import com.appboy.Appboy;
+import com.appboy.AppboyUser;
+import com.appboy.models.outgoing.AppboyProperties;
+
+public class ApptimizeAppboy
+        implements Apptimize.OnExperimentRunListener,
+                    Apptimize.OnExperimentsProcessedListener {
+
+    public void configureExperimentTracking(Context context) {
+        appboyInstance = Braze.getInstance(context);
+        enrollmentStorage = new File(context.getDir("apptimize-appboy", Context.MODE_PRIVATE), ApptimizeAppboyTestEnrollmentStorage);
+
+        Apptimize.setOnExperimentRunListener(this);
+        Apptimize.addOnExperimentsProcessedListener(this);
+    }
+
+    @Override
+    public void onExperimentRun(String experimentName, String variantName, boolean firstRun) {
+        if (!firstRun) {
+            return;
+        }
+        Map<String,ApptimizeTestInfo> testInfoMap = Apptimize.getTestInfo();
+
+        if (testInfoMap == null) {
+            return;
+        }
+
+        String experimentId = "";
+        String variantId = "";
+
+        Log.d("Apptimize-Appboy", "In onExperimentRun");
+
+        for (ApptimizeTestInfo testInfo : testInfoMap.values()) {
+            if (testInfo.getTestName().equals(experimentName) &&
+                testInfo.getEnrolledVariantName().equals(variantName)) {
+                experimentId = String.valueOf(testInfo.getTestId());
+                variantId = String.valueOf(testInfo.getEnrolledVariantId());
+            }
+        }
+        Log.d("Apptimize-Appboy", "Logging participation for " + experimentName + ":" + experimentId + " and variant " + variantName + ":" + variantId);
+
+        // If you want to log a custom event for each participation
+        logParticipationEventAsEvent(experimentName, variantName, experimentId, variantId);
+
+        // If you want a custom attribute array set for each participation
+        logParticipationEventAsAttributes(experimentName, variantName, experimentId, variantId);
+    }
+
+    private void logParticipationEventAsEvent(String experimentName, String variantName, String experimentId, String variantId) {
+        AppboyProperties eventProperties = new AppboyProperties();
+
+        eventProperties.addProperty("apptimize_experiment_name", experimentName);
+        eventProperties.addProperty("apptimize_variant_name", variantName);
+        eventProperties.addProperty("apptimize_experiment_id", experimentId);
+        eventProperties.addProperty("apptimize_variant_id", variantId);
+
+        appboyInstance.logCustomEvent("apptimize_experiment_viewed", eventProperties);
+    }
+
+    private void logParticipationEventAsAttributes(String experimentName, String variantName, String experimentId, String variantId) {
+        appboyInstance.getCurrentUser().addToCustomAttributeArray("apptimize_experiments",
+                "experiment_id_" + experimentId + ":variant_id_" + variantId + ":experiment_name_" + experimentName + ":variant_name_" + variantName);
+    }
+
+    @Override
+    public void onExperimentsProcessed() {
+        Map<String,String> currentEnrollmentDictionary = getEnrollmentDictionary();
+        Map<String,String> savedEnrollmentDictionary = getPreviousEnrollmentDictionary();
+        AppboyUser appboyUser = appboyInstance.getCurrentUser();
+
+        boolean enrollmentChanged = false;
+
+        Log.d("Apptimize-Appboy", "Processing experiments");
+
+        for (String key : currentEnrollmentDictionary.keySet()) {
+            if (savedEnrollmentDictionary == null ||
+                !currentEnrollmentDictionary.get(key).equals(savedEnrollmentDictionary.get(key))) {
+                Log.d("Apptimize-Appboy", "Found change in enrollment" + currentEnrollmentDictionary.get(key));
+                enrollmentChanged = true;
+                String testAttributeKey = "apptimize_test_" + key;
+                appboyUser.addToCustomAttributeArray(testAttributeKey, currentEnrollmentDictionary.get(key));
+            }
+        }
+
+        if (currentEnrollmentDictionary.size() == 0 && savedEnrollmentDictionary.size() != 0) {
+            enrollmentChanged = true;
+        }
+
+        if (enrollmentChanged) {
+            Log.d("Apptimize-Appboy", "Enrollment changed");
+            appboyUser.setCustomAttributeArray("active_apptimize_tests", currentEnrollmentDictionary.keySet().toArray(new String[0]));
+
+            for (String key : currentEnrollmentDictionary.keySet()) {
+                appboyUser.addToCustomAttributeArray("all_apptimize_tests", key);
+            }
+
+            storePreviousEnrollmentDictionary(currentEnrollmentDictionary);
+        }
+    }
+
+    private Map<String,String> getEnrollmentDictionary()
+    {
+        Map<String,String> enrollment = new HashMap<String,String>();
+        Map<String,ApptimizeTestInfo> testInfoMap = Apptimize.getTestInfo();
+        for (ApptimizeTestInfo testInfo : testInfoMap.values()) {
+            Log.d("Apptimize-Appboy", "TestID: " + String.valueOf(testInfo.getTestId()) + " VariantID: " + String.valueOf(testInfo.getEnrolledVariantId()));
+            enrollment.put(String.valueOf(testInfo.getTestId()), String.valueOf(testInfo.getEnrolledVariantId()));
+        }
+        return enrollment;
+    }
+
+    private Map<String,String> getPreviousEnrollmentDictionary()
+    {
+        ObjectInputStream enrollmentStream;
+        try {
+            enrollmentStream = new ObjectInputStream(new FileInputStream(enrollmentStorage));
+        } catch(Exception e) {
+            Log.d("Apptimize-Appboy", "Unable to open file");
+            return null;
+        }
+
+        Map<String, String> previousEnrollment;
+        try {
+                previousEnrollment = (Map<String,String>)enrollmentStream.readObject();
+        } catch (Exception e) {
+            Log.d("Apptimize-Appboy", "Unable to get previous enrollment");
+            return null;
+        }
+
+        return previousEnrollment;
+    }
+
+    private void storePreviousEnrollmentDictionary(Map<String,String> enrollmentDictionary)
+    {
+        try {
+            ObjectOutputStream enrollmentStream = new ObjectOutputStream(new FileOutputStream(enrollmentStorage));
+            enrollmentStream.writeObject(enrollmentDictionary);
+            enrollmentStream.flush();
+            enrollmentStream.close();
+        } catch (Exception e) {
+            Log.d("Apptimize-Appboy", "Unable to save enrollment information");
+        }
+
+    }
+
+    private Appboy appboyInstance;
+    private File enrollmentStorage;
+
+    private static String ApptimizeAppboyStorageDirectory;
+    private static String ApptimizeAppboyTestEnrollmentStorage = "ApptimizeAppboyTestEnrollmentStorage";
+}
+```
diff --git a/_lang/ko/_help/release_notes/deprecations/custom_broadcast_receiver.md b/_lang/ko/_help/release_notes/deprecations/custom_broadcast_receiver.md
new file mode 100644
index 00000000000..5e604f84aeb
--- /dev/null
+++ b/_lang/ko/_help/release_notes/deprecations/custom_broadcast_receiver.md
@@ -0,0 +1,153 @@
+---
+nav_title: 푸시 콜백 브로드캐스트 수신기
+article_title: Android용 사용자 지정 방송 수신기 푸시 콜백
+description: "이 참조 문서에서는 Android 푸시 알림을 위한 커스텀 브로드캐스트 수신기 만들기에 대해 설명합니다."
+---
+
+# 브로드캐스트 수신기를 통한 푸시 수신, 열기, 해지 및 키-값 페어에 대한 커스텀 처리 {#android-push-listener-broadcast-receiver}
+
+{% alert important %}
+푸시 알림에 커스텀 `BroadcastReceiver` 사용은 더 이상 사용되지 않습니다. 대신 [` subscribeToPushNotificationEvents()`](/docs/developer_guide/platform_integration_guides/android/push_notifications/android/customization/custom_event_callback/) 대신 사용하세요.
+{% endalert %}
+
+또한 Braze는 푸시 알림을 수신, 열거나 해제할 때 커스텀 의도를 브로드캐스트합니다. 이러한 시나리오에 대한 특정 사용 사례(예: 커스텀 키-값 페어를 수신해야 하거나 딥링크를 독점적으로 처리해야 하는 경우)가 있는 경우 커스텀 `BroadcastReceiver`를 생성하여 이러한 의도를 수신해야 합니다.
+
+## 1단계: BroadcastReceiver 등록하기
+
+커스텀 `BroadcastReceiver`를 등록하여 [`AndroidManifest.xml`][71]에서 Braze 푸시 열기 및 수신 의도를 수신하기 위한 조건:
+
+```xml
+<receiver android:name="YOUR-BROADCASTRECEIVER-NAME" android:exported="false" >
+  <intent-filter>
+    <action android:name="com.braze.push.intent.NOTIFICATION_RECEIVED" />
+    <action android:name="com.braze.push.intent.NOTIFICATION_OPENED" />
+    <action android:name="com.braze.push.intent.NOTIFICATION_DELETED" />
+  </intent-filter>
+</receiver>
+```
+
+## 2단계: BroadcastReceiver 만들기
+
+수신기는 Braze가 브로드캐스트한 의도를 처리하고 활동을 시작해야 합니다:
+
+- [`BroadcastReceiver`][53] 하위크래스에 포함하고 `onReceive()`를 재정의해야 합니다.
+- `onReceive()` 메서드는 Braze가 브로드캐스트하는 인텐트를 수신해야 합니다.
+  - 푸시 알림이 도착하면 `NOTIFICATION_RECEIVED` 인텐트가 수신됩니다.
+  - 사용자가 푸시 알림을 클릭하면 `NOTIFICATION_OPENED` 인텐트가 수신됩니다.
+  - 사용자가 푸시 알림을 해제(스와이프)하면 `NOTIFICATION_DELETED` 의도가 수신됩니다.
+- 이러한 각 경우에 대해 커스텀 로직을 수행해야 합니다. 수신기가 딥링크를 열 경우 `braze.xml`에서 `com_braze_handle_push_deep_links_automatically`를 `false`로 설정하여 자동 딥링크 열기를 해제해야 합니다.
+
+자세한 사용자 지정 수신기 예제는 다음 코드 스니펫을 참조하세요:
+
+{% tabs %}
+{% tab JAVA %}
+
+```java
+public class CustomBroadcastReceiver extends BroadcastReceiver {
+  private static final String TAG = CustomBroadcastReceiver.class.getName();
+
+  @Override
+  public void onReceive(Context context, Intent intent) {
+    String pushReceivedAction = Constants.BRAZE_PUSH_INTENT_NOTIFICATION_RECEIVED;
+    String notificationOpenedAction = Constants.BRAZE_PUSH_INTENT_NOTIFICATION_OPENED;
+    String notificationDeletedAction = Constants.BRAZE_PUSH_INTENT_NOTIFICATION_DELETED;
+
+    String action = intent.getAction();
+    Log.d(TAG, String.format("Received intent with action %s", action));
+
+    if (pushReceivedAction.equals(action)) {
+      Log.d(TAG, "Received push notification.");
+    } else if (notificationOpenedAction.equals(action)) {
+      BrazeNotificationUtils.routeUserWithNotificationOpenedIntent(context, intent);
+    } else if (notificationDeletedAction.equals(action)) {
+      Log.d(TAG, "Received push notification deleted intent.");
+    } else {
+      Log.d(TAG, String.format("Ignoring intent with unsupported action %s", action));
+    }
+  }
+}
+```
+
+{% endtab %}
+{% tab KOTLIN %}
+
+```kotlin
+class CustomBroadcastReceiver : BroadcastReceiver() {
+  override fun onReceive(context: Context, intent: Intent) {
+    val pushReceivedAction = Constants.BRAZE_PUSH_INTENT_NOTIFICATION_RECEIVED
+    val notificationOpenedAction = Constants.BRAZE_PUSH_INTENT_NOTIFICATION_OPENED
+    val notificationDeletedAction = Constants.BRAZE_PUSH_INTENT_NOTIFICATION_DELETED
+
+    val action = intent.action
+    Log.d(TAG, String.format("Received intent with action %s", action))
+
+    when (action) {
+      pushReceivedAction -> {
+        Log.d(TAG, "Received push notification.")
+      }
+      notificationOpenedAction -> {
+        BrazeNotificationUtils.routeUserWithNotificationOpenedIntent(context, intent)
+      }
+      notificationDeletedAction -> {
+        Log.d(TAG, "Received push notification deleted intent.")
+      }
+      else -> {
+        Log.d(TAG, String.format("Ignoring intent with unsupported action %s", action))
+      }
+    }
+  }
+
+  companion object {
+    private val TAG = CustomBroadcastReceiver::class.java.name
+  }
+}
+```
+
+{% endtab %}
+{% endtabs %}
+
+{% alert tip %}
+알림 실행 버튼의 경우 `opens app` 또는 `deep link` 동작이 있는 버튼을 클릭하면 `BRAZE_PUSH_INTENT_NOTIFICATION_OPENED` 의도가 실행됩니다. 딥링크 및 추가 처리 기능은 동일하게 유지됩니다. `close` 동작이 있는 버튼은 `BRAZE_PUSH_INTENT_NOTIFICATION_OPENED` 의도를 실행하지 않으며 알림을 자동으로 해제합니다.
+{% endalert %}
+
+## 3단계: 사용자 지정 키-값 쌍에 액세스
+
+대시보드 또는 메시징 API를 통해 전송된 커스텀 키-값 페어는 원하는 목적에 따라 커스텀 생방송 수신기에서 액세스할 수 있습니다.
+
+{% tabs %}
+{% tab JAVA %}
+
+```java
+// intent is the Braze push intent received by your custom broadcast receiver.
+String deepLink = intent.getStringExtra(Constants.BRAZE_PUSH_DEEP_LINK_KEY);
+
+// The extras bundle extracted from the intent contains all custom key-value pairs.
+Bundle extras = intent.getBundleExtra(Constants.BRAZE_PUSH_EXTRAS_KEY);
+
+// example of getting specific key-value pair from the extras bundle.
+String myExtra = extras.getString("my_key");
+```
+
+{% endtab %}
+{% tab KOTLIN %}
+
+```kotlin
+// intent is the Braze push intent received by your custom broadcast receiver.
+val deepLink = intent.getStringExtra(Constants.BRAZE_PUSH_DEEP_LINK_KEY)
+
+// The extras bundle extracted from the intent contains all custom key-value pairs.
+val extras = intent.getBundleExtra(Constants.BRAZE_PUSH_EXTRAS_KEY)
+
+// example of getting specific key-value pair from the extras bundle.
+val myExtra = extras.getString("my_key")
+```
+
+{% endtab %}
+{% endtabs %}
+
+{% alert note %}
+Braze 푸시 데이터 키에 대한 설명서는 [Android SDK](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze/-constants/index.html?query=object%20Constants)를 참조하세요.
+{% endalert %}
+
+[53]: https://developer.android.com/reference/android/content/BroadcastReceiver.html
+[71]: https://github.com/braze-inc/braze-android-sdk/blob/master/samples/custom-broadcast/src/main/AndroidManifest.xml "AndroidManifest.xml"
diff --git a/_lang/ko/_help/release_notes/deprecations/eclipse_setup_deprecated.md b/_lang/ko/_help/release_notes/deprecations/eclipse_setup_deprecated.md
new file mode 100644
index 00000000000..a70c5e43406
--- /dev/null
+++ b/_lang/ko/_help/release_notes/deprecations/eclipse_setup_deprecated.md
@@ -0,0 +1,81 @@
+---
+nav_title: Eclipse를 사용한 초기 SDK 설정
+page_order: 1
+
+page_type: update
+description: "이 보관된 문서에서는 Eclipse를 사용하여 초기 SDK 설정을 수행하는 방법을 설명합니다. Braze는 Eclipse IDE에 대한 지원을 중단했습니다."
+---
+
+# Eclipse를 사용한 초기 SDK 설정
+
+{% alert update %}
+[Google이 Eclipse 안드로이드 개발자 도구 플러그인에 대한 지원을 서비스 종료함](http://android-developers.blogspot.com/2015/06/an-update-on-eclipse-android-developer.html)에 따라 Braze는 Eclipse IDE에 대한 지원을 중단했습니다. 마이그레이션 전에 Eclipse 통합에 대한 도움이 필요한 경우 [지원팀에 이메일을 보내]({{site.baseurl}}/support_contact/) 도움을 요청하세요.
+{% endalert %}
+
+## 1단계
+명령줄에서 [Braze Android GitHub 리포지토리][03]를 복제합니다.
+
+```bash
+$ git clone git@github.com:braze-inc/braze-android-sdk.git
+```
+
+## 2단계
+Braze 프로젝트를 로컬 작업 공간으로 가져오기
+
+Eclipse에서
+
+  - 파일 > 가져오기로 이동합니다.
+
+    ![파일 가져오기][04]
+  - Android > 기존 Android 코드를 워크스페이스로 가져오기를 선택합니다.
+
+    ![Android 가져오기][05]
+  - "찾아보기"를 클릭합니다.
+
+    ![찾아보기][06]
+  - Braze UI 프로젝트 폴더를 확인하고 "프로젝트를 워크스페이스에 복사"를 클릭한 다음 "마침"을 클릭합니다.
+
+    ![Android UI 프로젝트 선택][07]
+
+## 3단계
+자신의 프로젝트에서 Braze를 참조하세요.
+Eclipse에서
+
+  - 프로젝트를 마우스 오른쪽 버튼으로 클릭하고 "속성"을 선택합니다.
+
+    ![속성 클릭][08]
+  - "Android"의 라이브러리 섹션에서 "추가..."를 클릭하고 안드로이드-sdk-ui를 앱에 라이브러리로 추가합니다.
+
+    ![Braze 추가][09]
+
+## 4단계
+종속성 오류를 해결하고 빌드 대상을 수정합니다.
+
+이때 Braze 코드에 오류가 표시될 수 있는데, 이는 해당 종속성이 채워지지 않았거나 빌드 대상이 잘못되었을 가능성이 있기 때문입니다:
+
+   - Braze UI 프로젝트를 마우스 오른쪽 버튼으로 클릭하고 속성->Android를 선택하여 빌드 대상이 Braze의 현재 빌드 도구 버전으로 설정되어 있는지 확인합니다.
+
+      ![대상 구축][10]
+   - Braze UI 프로젝트를 마우스 오른쪽 버튼으로 클릭하고 속성->Java 빌드 경로->JAR 추가...를 선택한 다음 기본 애플리케이션에서 'android-support-v4.jar'를 라이브러리로 추가합니다.
+
+      ![고객지원][11]
+
+## 5단계
+
+마지막 조각을 추가합니다.
+
+  - SDK 버전 1.10.0 이상의 경우 다음을 추가해야 합니다.
+  `<service android:name="com.appboy.services.AppboyDataSyncService" />`
+  를 AndroidManifest.xml에 추가합니다. Eclipse는 매니페스트 병합을 지원하지 않기 때문입니다.
+
+  - SDK 버전 1.7.0 이상의 경우, 라이브러리 프로젝트에서 "assets/fontawesome-webfont.ttf"을 애플리케이션에 복사해야 합니다. Eclipse는 라이브러리의 에셋 폴더를 자동으로 포함하지 않습니다.
+
+[03]: https://github.com/braze-inc/braze-android-sdk "Appboy Android GitHub 리포지토리"
+[04]: {{site.baseurl}}/assets/img_archive/file_import.png
+[05]: {{site.baseurl}}/assets/img_archive/android_import.png
+[06]: {{site.baseurl}}/assets/img_archive/click_browse.png
+[07]: {{site.baseurl}}/assets/img_archive/select_project_android.png
+[08]: {{site.baseurl}}/assets/img_archive/click_properties.png
+[09]: {{site.baseurl}}/assets/img_archive/add_appboy_ui.png
+[10]: {{site.baseurl}}/assets/img_archive/build_target.png
+[11]: {{site.baseurl}}/assets/img_archive/android_support_v4.png
diff --git a/_lang/ko/_help/release_notes/deprecations/grouparoo.md b/_lang/ko/_help/release_notes/deprecations/grouparoo.md
new file mode 100644
index 00000000000..1f1dda121e5
--- /dev/null
+++ b/_lang/ko/_help/release_notes/deprecations/grouparoo.md
@@ -0,0 +1,76 @@
+---
+nav_title: Grouparoo
+page_order: 1
+description: "이 글에서는 Braze와 Grouparoo 간의 파트너십을 설명합니다. Grouparoo는 오픈 소스 리버스 ETL 도구로, 데이터 웨어하우스의 데이터를 사용하여 마케팅, 영업 및 지원 도구를 쉽게 활용할 수 있게 해줍니다."
+page_type: update
+
+---
+
+# Grouparoo
+
+{% alert update %}
+Grouparoo에 대한 지원은 2022년 4월부로 중단되었습니다.
+{% endalert %}
+
+> [Grouparoo][1]는 창고에 있는 데이터를 사용하여 마케팅, 영업 및 지원 도구를 쉽게 사용할 수 있게 해주는 오픈 소스 리버스 ETL 도구입니다. 구성은 모델 중심 UI에서 수행되므로 비기술 팀 구성원도 운영을 지원하기 위해 데이터 동기화를 구성하고 예약할 수 있습니다.
+
+Braze와 Grouparoo 통합은 데이터를 Braze로 전송하여 창고에 저장된 데이터를 운영하기 쉽게 만듭니다. 자동 동기화 일정을 설정하면 최신 정보로 고객 커뮤니케이션을 지속적으로 향상시킬 수 있습니다.
+
+## 필수 조건
+
+| 요구 사항 | 설명 |
+| ----------- | ----------- |
+| Grouparoo 계정 및 프로젝트 | Grouparoo 계정과 프로젝트가 이 파트너십을 활용하는 데 필요합니다.<br><br>이 통합은 Grouparoo에서 제공하는 무료 커뮤니티 에디션 및 엔터프라이즈 솔루션과 함께 사용할 수 있습니다. 설정은 Grouparoo 구성 사용자 인터페이스에서 이루어집니다. |
+| Braze REST API 키 | 사용자 및 추적 권한이 있는 Braze REST API 키. <br><br> 이는 **설정** > **API 키**에서 Braze 대시보드에서 생성할 수 있습니다. |
+| Braze REST 엔드포인트 | [당신의 REST 엔드포인트 URL][1]. 사용자의 엔드포인트는 인스턴스를 위한 Braze URL에 따라 달라집니다. |
+{: .reset-td-br-1 .reset-td-br-2}
+
+## 통합
+
+### 1단계: Grouparoo에서 Braze 앱 만들기
+
+Grouparoo에서 **앱**으로 이동하여 **Braze**를 선택하여 새 Braze 앱을 만드세요. 표시되는 모달에서 Braze API 키 및 REST 엔드포인트를 제공하십시오.
+
+![][2]
+
+### 2단계: 모델 및 데이터 소스를 설정
+
+이 통합은 다음 단계로 진행하기 전에 기존 모델과 데이터 소스가 설정되어 있어야 합니다. 이 설정이 되어 있지 않으면 Grouparoo 설명서를 방문하여 [모델](https://www.grouparoo.com/docs/config/models) 및 [데이터 소스](https://www.grouparoo.com/docs/config/sources)를 설정하는 방법을 배우십시오.
+
+### 3단계: Grouparoo에서 Braze 대상을 생성하세요
+
+#### 동기화 모드 선택
+
+Grouparoo에서 탐색 모음에서 모델을 선택하세요. 다음으로, **대상** 섹션으로 스크롤하고 **새 대상 추가**을 클릭합니다.
+
+다음으로, **Braze** 앱을 선택하고, 대상을 이름 짓고, 다음 중 원하는 동기화 모드를 선택하세요.
+- **동기화**: 필요에 따라 Braze 사용자를 추가, 업데이트 및 제거합니다. 이 옵션은 새 레코드, 기존 레코드의 변경 사항 및 삭제를 찾습니다.
+- **첨가제**: 필요에 따라 Braze 사용자를 추가 및 업데이트하지만, 아무도 제거하지 마십시오. 이 옵션은 Braze에 추가할 새로운 사용자와 기존 Braze 사용자의 변경 사항을 찾지만 삭제는 추적하지 않습니다.
+- **강화**: Braze에 이미 존재하는 사용자만 업데이트하십시오. 사용자를 추가하거나 제거하지 마십시오. 이 옵션은 Braze의 기존 사용자만 업데이트합니다.
+
+#### 속성 필드 매핑
+
+다음으로, Grouparoo 속성 필드를 Braze 속성 필드에 매핑해야 합니다. 
+
+![예제 속성 매핑 필드. Grouparoo userID는 external_id에 매핑되도록 설정됩니다. 이메일, firstName, lastName은 각각 "이메일", "first_name", "last_name" grouparoo 필드로 설정됩니다.][3]{: style="max-width:80%;"}
+
+Braze `external_id` 필드가 소스 테이블의 기본 키에 매핑되었는지 확인하세요. 필요한 사용 사례에 따라 나머지 필드를 매핑합니다.
+
+**레코드 속성정보 보내기** 섹션: 데이터를 매핑할 수 있는 미리 설정된 고객 프로필 필드 목록. 이 중 어느 것이든 Grouparoo 속성에서 동기화할 수 있습니다.
+
+**선택적 Braze 고객 프로필 필드** 섹션: 선택적 커스텀 Braze 고객 프로필 필드를 생성합니다. **새 Braze 고객 프로필 필드**를 클릭하면 Braze에 매핑할 수 있는 모든 사용 가능한 속성을 볼 수 있습니다. 새로 만드는 모든 필드의 이름은 Grouparoo 속성과 동일하지만 이름을 변경할 수 있습니다.
+
+#### Grouparoo 그룹
+
+매핑 외에도 Grouparoo 그룹을 Braze 구독 그룹에 추가할 수도 있습니다. 
+
+![Grouparoo 대상 구성 창의 "Braze 구독 그룹"에서 "최근 자동차 구매와 함께 높은 가치" Grouparoo 그룹이 "최근 자동차 구매와 함께 높은 가치" Braze 구독 그룹에 추가됩니다.][4]{: style="max-width:80%;"}
+
+{% alert important %}
+이 통합에 대한 추가 세부 정보 및 업데이트는 [Grouparoo의 설명서](https://www.grouparoo.com/docs/integrations/grouparoo-braze)에서 찾을 수 있습니다.
+{% endalert %}
+
+[1]: https://www.grouparoo.com/
+[2]: {% image_buster /assets/img/grouparoo/add-app.png %}
+[3]: {% image_buster /assets/img/grouparoo/mapping.png %}
+[4]: {% image_buster /assets/img/grouparoo/lists.png %}
\ No newline at end of file
diff --git a/_lang/ko/_help/release_notes/deprecations/shopify_checkout.md b/_lang/ko/_help/release_notes/deprecations/shopify_checkout.md
new file mode 100644
index 00000000000..e8135190d5e
--- /dev/null
+++ b/_lang/ko/_help/release_notes/deprecations/shopify_checkout.md
@@ -0,0 +1,60 @@
+---
+nav_title: Shopify checkout.liquid
+page_order: 7
+description: "이 문서에서는 Shopify 통합에 미치는 영향 및 개발자를 위한 지침을 포함하여 Shopify checkout.liquid의 사용 중단에 대해 설명합니다."
+page_type: update
+
+---
+
+# Shopify checkout.liquid 사용 중단
+
+Shopify는 모든 판매자에게 `checkout.liquid` 의 사용 중단과 맞춤형 결제 환경을 구축하기 위한 새로운 기반인 [Checkout Extensibility](https://www.shopify.com/enterprise/blog/checkout-extensibility-winter-editions) 로의 마이그레이션에 대해 알렸습니다. 
+
+Shopify는 `checkout.liquid` 을 두 단계에 걸쳐 사용 중단할 예정입니다:
+
+1. **[2024년 8월 13일](#phase-one-august-13-2024):** 정보, 배송 및 결제 페이지 업그레이드 마감일입니다.
+2. **[2025년 8월 28일](#phase-two-august-28-2025):** 스크립트 태그 및 추가 스크립트를 사용하여 앱을 포함한 감사 및 주문 상태 페이지를 업그레이드할 수 있는 마감일입니다.
+
+Checkout 확장성 업그레이드에 대한 일반 정보는 [Shopify의 업그레이드 가이드](https://help.shopify.com/en/manual/checkout-settings/customize-checkout-configurations/checkout-extensibility)를 참조하세요.
+
+## 통합에 미치는 영향
+
+Braze와 Shopify 통합은 [Shopify ScriptTags](https://shopify.dev/docs/apps/build/online-store/script-tag-legacy)를 사용하여 헤드리스 사이트가 아닌 사이트에 대한 Braze 웹 SDK를 로드합니다. `checkout.liquid`가 완전히 지원 중단되기 전에 모든 고객을 지원하기 위해 2025년 마감일 이전에 새로운 버전의 통합을 출시할 계획입니다. 
+
+2024년 8월 13일에 예정된 변경 사항에 대해 아래 세부 정보를 확인하여 개발팀에서 영향을 받는지 확인하세요.
+
+### 1단계: 2024년 8월 13일
+
+기본 Braze와 Shopify 통합은 결제 환경 내에서 정보, 배송 및 결제 페이지를 사용하지 않습니다. 따라서 기본 통합에는 영향을 미치지 않습니다. 
+
+#### Shopify Plus
+
+Shopify Plus 고객의 경우 정보, 배송 또는 결제 페이지의 `checkout.liquid` 을 수정하는 모든 사용자 지정 SDK 코드 스니펫은 이 날짜 이후에는 비활성 상태가 됩니다. 예를 들어, 이러한 페이지에서 이벤트를 기록하는 사용자 지정 코드는 더 이상 작동하지 않습니다. 사용자 지정 SDK 코드가 있는 경우 마이그레이션에 대한 [개발자 가이드를](#developer-guidance) 참조하세요.
+
+#### 비 Shopify Plus
+
+Shopify Plus 비사용 고객의 경우 정보, 결제 및 배송 페이지를 사용자 지정해야 하는 경우 [Shopify Plus로 업그레이드한](https://help.shopify.com/en/manual/checkout-settings/customize-checkout-configurations/checkout-extensibility#eligibility) 다음 [개발자 지침](#developer-guidance)을 따라야 합니다.
+
+### 2단계: 2025년 8월 28일
+
+Shopify는 통합에 사용되는 `checkout.liquid` 페이지의 [스크립트 태그](https://shopify.dev/docs/apps/build/online-store/script-tag-legacy)에 대한 지원을 중단할 예정입니다. 이에 따라 2025년 8월 마감일보다 훨씬 앞서 출시할 계획인 새 버전의 Shopify 통합을 적극적으로 구축하고 있습니다. Braze 제품팀에서 더 많은 정보를 알려드릴 테니 기대해 주세요. 
+
+## 개발자 가이드
+
+이 지침은 `checkout.liquid` 에서 정보, 배송 또는 결제 페이지에 사용자 지정 SDK 코드 스니펫을 추가한 Shopify Plus 고객에게 적용됩니다. 이러한 사용자 지정을 수행하지 않은 경우 이 지침을 무시해도 됩니다.
+
+더 이상 `checkout.liquid`에서 정보, 배송 또는 결제 페이지에 커스텀 SDK 코드 스니펫을 추가할 수 없습니다. 대신 감사 또는 주문 상태 페이지에 커스텀 SDK 코드 스니펫을 추가해야 합니다. 이를 통해 결제를 완료한 사용자를 조정할 수 있습니다.
+1. 감사 및 주문 상태 페이지에서 Braze 웹 SDK를 로드합니다.
+2. 사용자로부터 이메일을 검색합니다.
+3. `setEmail` 호출.
+
+{% raw %}
+```java
+braze.getUser().setEmail(<email address>);
+```
+{% endraw %}
+
+{: start="4"}
+4\. Braze에서 이메일의 사용자 프로필을 병합합니다.
+
+중복된 고객 프로필이 있는 경우 [일괄 병합 도구]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users#bulk-merging)를 사용하여 데이터를 간소화할 수 있습니다. 
diff --git a/_lang/ko/_help/release_notes/deprecations/tls_deprecation.md b/_lang/ko/_help/release_notes/deprecations/tls_deprecation.md
new file mode 100644
index 00000000000..de52e0aae44
--- /dev/null
+++ b/_lang/ko/_help/release_notes/deprecations/tls_deprecation.md
@@ -0,0 +1,62 @@
+---
+nav_title: TLS 1.0 및 1.1 사용 중단
+page_order: 2
+
+page_type: update
+description: "이 문서에서는 2018년 5월에 완료된 Braze의 TLS 1.0 및 TLS 1.1 사용 중단에 대해 설명합니다."
+---
+# TLS 1.0 및 1.1 사용 중단
+
+{% alert update %}
+Braze는 PCI 보안 표준 위원회의 권고에 따라 TLS 1.0과 1.1 모두에서 TLS(전송 계층 보안) 암호에 대한 지원을 제거했습니다. 지원 중단은 2018년 5월에 완료된 두 단계에 걸쳐 진행되었습니다.
+{% endalert %} 
+
+## 배경
+
+Braze는 PCI 보안표준위원회가 2018년 5월 두 단계에 걸쳐 발표한 권고에 따라 TLS 1.0과 1.1 모두에서 취약한 것으로 알려진 TLS(전송 계층 보안) 암호를 더 이상 사용하지 않습니다.
+
+이번 변경은 Braze 플랫폼과 관련된 침해나 문제에 대응하기 위한 것이 아니라 업계 최고 수준의 보안 및 데이터 표준을 유지하고 고객과 고객의 고객을 선제적으로 보호하기 위한 예방 조치로 이루어졌습니다.
+
+최근 몇 년 동안 TLS와 그 이전 버전인 SSL(보안 소켓 계층)과 관련된 여러 가지 체계적인 보안 문제([POODLE][1], [Heartbleed][2], [LOGJAM][3] 등)로 인해 암호화된 웹 트래픽이 위협받고 인터넷의 일부가 보안 침해에 노출되었습니다. Braze는 다른 기술 회사들과 함께 2014년에 SSLv3에 대한 지원을 중단하는 등 공격이 발견되면 취약한 암호화 프로토콜과 암호를 비활성화하는 조치를 취한 바 있습니다.
+
+최근에는 PCI 보안 표준 협의회에서 2015년 4월 [결제 카드 업계 데이터 보안 표준][4] (PCI-DSS)에 대한 암호화 관련 지침을 발표했습니다. 이 지침은 강력한 암호화 암호의 프로토콜 목록에서 SSL 3.0, TLS 1.0 및 TLS 1.1에서 지원하는 일부 암호 스위트를 제외하며, 인터넷 사용자의 보안을 위해 기업이 해당 프로토콜 또는 암호에 대한 지원을 중단할 것을 권장합니다.
+
+암호 스위트는 보안 SSL 또는 TLS 연결을 협상할 때 암호화, 인증 및 통신 무결성을 제공하는 알고리즘의 조합입니다. 현재 알려진 공격이 있든 없든 특정 암호를 해독할 수 있는 가능성이 발견되면 해당 암호는 향후 공격을 가능하게 할 수 있는 "약점"이 있는 것으로 간주됩니다. 이러한 TLS 암호를 PCI DSS 규정 준수 요구 사항에서 제외하여 PCI DSS 협의회는 서비스 제공업체가 동급 최강의 암호화 표준만 지원하도록 요구하고 있습니다. PCI DSS 협의회는 2018년 6월 30일을 암호화 요건 준수 기한으로 정하여 TLS 1.0 및 TLS 1.1에 대한 지원을 중단하도록 했습니다.
+
+## Braze의 지원 중단 계획
+PCI DSS 위원회의 권고 사항을 준수하기 위해 Braze는 당사 서비스에서 지원하는 최소 버전의 TLS를 상향 조정할 예정입니다. 규정 준수 계획과 이 계획이 브랜드와 사용자에게 미칠 수 있는 잠재적 영향에 대한 이해를 돕기 위해 두 가지 주요 단계에 대해 알아두어야 할 사항이 있습니다:
+
+### 1단계: 2017년 10월 1일
+
+Braze의 웹 대시보드 및 REST API에서 다음 암호를 사용할 수 있는 기능이 제거됩니다.
+
+- `TLS_RSA_WITH_AES_256_CBC_SHA`
+- `TLS_RSA_WITH_AES_128_CBC_SHA`
+- `TLS_RSA_WITH_AES_256_CBC_SHA256`
+- `TLS_RSA_WITH_AES_256_GCM_SHA384`
+- `TLS_RSA_WITH_AES_128_CBC_SHA256`
+- `TLS_RSA_WITH_AES_128_GCM_SHA256`
+- `TLS_RSA_WITH_3DES_EDE_CBC_SHA`
+
+모든 최신 웹 브라우저는 더 안전한 암호를 지원하므로 이러한 변경 사항은 Braze 대시보드에 액세스하는 고객에게는 영향을 미치지 않습니다. 그러나 10월 1일 이후 웹 대시보드에 액세스할 때 SSL 암호화 오류가 발생하는 경우 최신 버전의 웹 브라우저로 업그레이드하기만 하면 문제를 해결할 수 있습니다.
+
+엔지니어링 팀은 Braze의 REST API를 사용한 서버 간 통신에 이러한 암호를 사용하지 않도록 해야 합니다. 그렇다면 10월 1일 이전에 더 안전한 암호화 암호를 사용하도록 코드를 업데이트해야만 Braze의 API를 계속 사용할 수 있습니다. 그러나 취약한 암호를 사용할 수 있는 오래된 구형 모바일 기기에 대한 지원을 유지하기 위해 Braze는 SDK에서 데이터를 수신한 APIS에서 이러한 암호를 계속 지원할 것입니다.
+
+### 2단계: 2018년 5월 31일
+
+Braze는 2018년 5월 31일에 Braze 대시보드, REST API, SDK와 통신하는 API를 포함한 모든 Braze 서비스에서 TLS 1.0 및 TLS 1.1에 대한 지원을 중단할 예정입니다. 또한 SDK 데이터를 수신하는 API와 관련하여 이전 섹션에 나열된 암호에 대한 지원도 제거할 예정입니다. 즉, 이 날짜부터 Braze와 주고받는 모든 TLS 1.0 및 1.1 통신은 당사 네트워크에서 지원되지 않습니다.
+
+이 변경으로 인해, 일부 구형 또는 오래된 모바일 기기(Android 초기 버전을 실행하는 기기 등)는 Braze와 통신할 수 없게 되어 Braze로 데이터를 전송하거나 Braze로부터 인앱 메시지를 수신하지 못할 수 있습니다. 그러나 이러한 변경은 소수의 기기에만 영향을 미칠 것으로 예상됩니다. 영향을 받는 모든 기기는 한 달 후인 2018년 6월 30일, 즉 PCI DSS 위원회에서 TLS 1.0 및 TLS 1.1 암호 제거를 위해 정한 날짜에 PCI 호환 웹사이트 또는 서비스와 통신할 수 없게 됩니다.
+
+## 실행 계획
+브랜드에서 Braze의 REST API를 사용하는 경우, 서비스 중단을 방지하기 위해 엔지니어링 팀에 문의하여 모든 서버 간 호출이 위에 나열된 TLS 1.2를 사용하여 이루어지도록 하세요. Java 7과 같은 일부 프로그래밍 언어에서는 기본적으로 이전 버전의 TLS를 사용하므로 엔지니어링 팀에서 업그레이드된 암호화 요구 사항을 지원하기 위해 일부 코드를 변경해야 할 수도 있습니다.
+
+Apple 기기는 2016년 말부터 TLS 1.2를 요구해 왔기 때문에 Braze의 계획된 사용 중단에 영향을 받지 않습니다. 최신 웹 브라우저도 마찬가지이므로 이러한 변경 사항이 웹 SDK 사용에는 영향을 미치지 않을 것으로 예상합니다. 그러나 Android 4.4(킷캣) 이하를 실행하는 안드로이드 기기는 기본적으로 TLS 1.2를 사용하지 않을 수 있으므로 2018년 5월 31일까지 모든 Android 통합 기능을 Braze SDK 버전 2.0.3(해당 기기에서 지원할 수 있는 경우 기본적으로 TLS 1.2를 사용) 이상으로 업그레이드하세요.
+
+마지막으로, TLS 1.0 및 TLS 1.1 암호 스위트의 알려진 취약점으로 인해 향후 공격이 발생할 수 있으며, 이로 인해 Braze는 모든 고객의 보안을 보호하기 위해 사용 중단 계획을 가속화해야 할 수도 있습니다. Braze는 TLS 1.0 및 1.1 프로토콜과 관련된 보안 상태 및 관련 공격을 모니터링하고, 이전 섹션에서 설명한 타임라인을 변경할 수 있는 공격이 발견될 경우 계속 알려드리겠습니다. 그러나 이러한 잠재적인 영향 때문에 엔지니어링 팀과 협력하여 Braze에 대한 API 호출이 TLS 1.2로 보호되도록 하고, 향후 몇 달 내에 최신 Android SDK로 업그레이드할 계획을 세우는 것이 좋습니다.
+
+
+[1]: https://www.us-cert.gov/ncas/alerts/TA14-290A
+[2]: https://en.wikipedia.org/wiki/Heartbleed
+[3]: https://en.wikipedia.org/wiki/Logjam_(computer_security)
+[4]: https://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard
diff --git a/_lang/ko/_help/release_notes/deprecations/twilio.md b/_lang/ko/_help/release_notes/deprecations/twilio.md
new file mode 100644
index 00000000000..d1b7f86fc4e
--- /dev/null
+++ b/_lang/ko/_help/release_notes/deprecations/twilio.md
@@ -0,0 +1,63 @@
+---
+nav_title: Twilio 파트너십
+alias: /partners/twilio/
+
+description: "이 기사는 Braze와 Twilio 간의 파트너십을 설명합니다."
+page_type: update
+channel: 
+  - SMS
+  - Webhook
+---
+
+# Twilio
+
+{% alert warning %}
+Twilio 웹훅 통합에 대한 지원은 2020년 1월 31일에 중단됩니다. SMS 서비스를 Braze와 함께 계속 이용하려면 [SMS 설명서]({{site.baseurl}}/user_guide/message_building_by_channel/sms/)를 참조하세요.
+{% endalert %}
+
+이 예제에서는 Braze 웹훅 채널을 구성하여 Twilio의 [메시지 전송 API][20]를 통해 사용자에게 SMS 및 MMS를 보냅니다. 사용자의 편의를 위해 대시보드에 Twilio 웹훅 템플릿이 포함되어 있습니다.
+
+## HTTP URL
+
+대시보드에서 Twilio가 제공한 웹훅 URL입니다. 이 URL은 Twilio 계정 ID(`TWILIO_ACCOUNT_SID`)를 포함하고 있기 때문에 사용자의 Twilio 계정에 고유합니다.
+
+Braze의 Twilio 예제에서, 웹훅 URL은 `https://api.twilio.com/2010-04-01/Accounts/TWILIO_ACCOUNT_SID/Messages.json`입니다. Twilio 콘솔의 *시작하기* 섹션에서 이 URL을 찾을 수 있습니다.
+
+![Twilio_Console][28]
+
+## 요청 본문
+
+Twilio API는 요청 본문이 URL 인코딩되기를 기대하므로 Braze 웹훅 작성기에서 요청 유형을 `Raw Text`로 변경하는 것부터 시작해야 합니다. 요청 본문에 필요한 매개변수는 *To*, *From*, 및 *Body*입니다.
+
+다음 스크린샷은 각 사용자의 전화번호로 SMS를 보낼 때 본문에 "Braze에서 인사드립니다!"라는 메시지를 포함한 요청이 어떻게 보일 수 있는지에 대한 예시입니다.
+
+- 각 고객 프로필에 유효한 전화번호가 대상 오디언스에 있어야 합니다.
+- Twilio의 요청 형식을 충족하려면 메시지 내용에 `url_param_escape` Liquid 필터를 사용하세요. 이 필터는 문자열을 인코딩하여 모든 문자가 HTML 요청에서 허용되도록 합니다. 예를 들어, 전화번호 `+12125551212`의 더하기 문자(`+`)는 URL 인코딩된 데이터에서 금지되어 있으며 `%2B12125551212`로 변환됩니다.
+
+![웹훅 본문][29]
+
+## 요청 헤더 및 메서드
+
+Twilio는 두 개의 요청 헤더, 요청 콘텐츠-유형 및 \[HTTP 기본 인증][32] 헤더가 필요합니다. 웹훅 작성기 옆에 있는 톱니바퀴 아이콘을 클릭한 다음 *새 쌍 추가*를 두 번 클릭하여 웹훅에 추가하십시오.
+
+헤더 이름 | 헤더 값
+--- | ---
+콘텐츠-유형 | `application/x-www-form-urlencoded`
+승인 | `{% raw %}Basic {{ 'TWILIO_ACCOUNT_SID:TWILIO_AUTH_TOKEN' | base64_encode }}{% endraw %}`
+
+`TWILIO_ACCOUNT_SID` 및 `TWILIO_AUTH_TOKEN`을 Twilio 대시보드의 값으로 바꾸세요. 마지막으로, Twilio의 API 엔드포인트는 HTTP POST 요청을 기대하고 있으므로 *HTTP Method* 드롭다운에서 해당 옵션을 선택하세요.
+
+![웹훅 메서드][30]
+
+## 요청 미리보기
+
+웹훅 작성기를 사용하여 무작위 사용자 또는 특정 자격 증명을 가진 사용자의 요청을 미리 보고 요청이 올바르게 렌더링되는지 확인하세요.
+
+![웹훅 미리보기][31]
+
+[20]: https://www.twilio.com/docs/api/rest/sending-messages
+[28]: {% image_buster /assets/img_archive/Twilio_Console.png %}
+[29]: {% image_buster /assets/img_archive/Webhook_Body.png %}
+[30]: {% image_buster /assets/img_archive/Webhook_Method.png %}
+[31]: {% image_buster /assets/img_archive/Webhook_Preview.png %}
+[32]:https://en.wikipedia.org/wiki/Basic_access_authentication#Client_side
diff --git a/_lang/ko/_help/release_notes/sdk_changelogs.md b/_lang/ko/_help/release_notes/sdk_changelogs.md
new file mode 100644
index 00000000000..758e21fb643
--- /dev/null
+++ b/_lang/ko/_help/release_notes/sdk_changelogs.md
@@ -0,0 +1,6 @@
+---
+nav_title: SDK 체인지로그
+layout: redirect
+page_order: 10
+redirect_to: /docs/developer_guide/platform_integration_guides/sdk_changelogs/
+---
diff --git a/_lang/ko/_help/support.md b/_lang/ko/_help/support.md
new file mode 100644
index 00000000000..bb7866daf88
--- /dev/null
+++ b/_lang/ko/_help/support.md
@@ -0,0 +1,66 @@
+---
+nav_title: Braze 고객지원팀
+article_title: 고객지원
+description: "이 페이지에서는 Braze 제품 피드백을 제출할 수 있는 Braze 지원 포털을 찾을 수 있습니다. 이 페이지는 Braze 고객만 액세스할 수 있습니다."
+alias: /braze_support/
+page_type: reference
+search_rank: 1
+---
+
+# [![Braze 학습 과정]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/the-braze-support-portal/){: style="float:right;width:120px;border:0;" class="noimgborder"}Braze 지원
+
+## 지원 포털에 액세스
+
+Braze 지원팀에 문의하려면 Braze 대시보드로 이동하세요. 대시보드에서 **지원** > **도움말 받기를** 선택합니다.
+
+![]({% image_buster /assets/img_archive/get_help.png %})
+
+Braze 권한에 따라, 그리고 지정된 지원 담당자(프리미엄)인 경우 사례를 제출하고 추적할 수 있는 Braze 지원 포털로 이동하거나 표준 지원 양식으로 이동하게 됩니다. 자신이 Braze 지원 담당자인지 확실하지 않은 경우 회사의 Braze 매니저, Braze 성공 매니저 또는 계정 소유자에게 문의하세요.
+
+{% alert note %}
+[이전 탐색]({{site.baseurl}}/navigation) 기능을 사용하는 경우에는 **도움말 받기** > **지원**을ㄹ 선택합니다.
+{% endalert %}
+
+## 개발자 콘솔 스크린샷 제공
+
+지원팀과 소통할 때 추가 정보를 제공하기 위해 개발자 콘솔에 액세스해야 할 수도 있습니다:
+- Chrome
+  1. 웹페이지를 마우스 오른쪽 버튼으로 클릭하고 **검사를** 클릭합니다.
+  2. 열리는 창에서 **콘솔** 탭을 클릭합니다.
+  3. 콘솔 탭의 스크린샷을 찍습니다.<br><br>
+- Firefox
+  1. 웹페이지를 마우스 오른쪽 버튼으로 클릭하고 **요소 검사**를 클릭합니다.
+  2. 열리는 창에서 **콘솔** 탭을 클릭합니다.
+  3. 콘솔 탭의 스크린샷을 찍습니다.<br><br>
+- Safari
+  1. 화면 상단의 메뉴 막대에서 Safari로 이동한 다음 **환경설정을** 선택합니다.
+  2. 상단의 **고급**을 클릭한 다음 **메뉴 표시줄에서 개발 메뉴 표시** 옆에 있는 확인란을 선택합니다. 그런 다음 창을 종료할 수 있습니다.
+  3. 웹페이지를 마우스 오른쪽 버튼으로 클릭하고 **요소 검사**를 클릭합니다.
+  4. 열리는 창에서 **콘솔** 탭을 클릭합니다.
+  5. 콘솔 탭의 스크린샷을 찍습니다.
+
+## 지원 사례 제출을 위한 모범 사례
+
+### 가능한 한 많은 정보 제공
+
+제공할 수 있는 인사이트가 많을수록 좋습니다. 워크스페이스, 캠페인 또는 세그먼트의 URL, 관련 외부 ID와 같은 세부 정보를 포함하세요. 이렇게 하면 문제를 더 효율적으로 해결하는 데 도움이 됩니다.
+
+### 사용자 샘플 제공
+
+영향을 받는 전체 세그먼트가 아닌 사용자 표본을 공유하세요. 적은 수의 사용자를 제공하면 조사 범위를 좁히고 조사 속도를 높이는 데 도움이 됩니다.
+
+### 예상 행동과 실제 행동을 명확히 구분
+
+예상했던 것과 실제로 어떤 일이 일어났는지 알려주세요. 이를 통해 문제의 가능한 원인을 좁히는 데 도움이 될 수 있습니다.
+
+### 관련 이미지 첨부
+
+스크린샷을 첨부하여 문제를 설명하는 것이 좋습니다. 이러한 이미지를 제공하면 문제를 이해하는 데 큰 도움이 되고 해결 과정의 속도를 높일 수 있습니다.
+
+### 영향 평가
+
+적절한 심각도 수준을 선택하면 문제 해결에 적합한 리소스를 할당하는 데 도움이 됩니다. 
+
+{% alert important %}
+이슈를 "심각"으로 표시하면 프로덕션 인스턴스가 다운되고 Braze 내의 모든 작업이 중단됩니다.
+{% endalert %}
\ No newline at end of file
diff --git a/_layouts/api_glossary.html b/_layouts/api_glossary.html
index 0acbf29e04f..615059b2acd 100644
--- a/_layouts/api_glossary.html
+++ b/_layouts/api_glossary.html
@@ -274,7 +274,7 @@ <h1> {{ page.glossary_top_header }} </h1>
             <i class="{{menu_list.fa_icon}}"></i>
             {%- else -%}
               {%- if menu_list.image -%}
-              <img src="{{site.baseurl}}{{ menu_list.image}} " />
+              <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
               {%- endif -%}
             {%- endif -%}
             <div class="menu_description">
@@ -285,20 +285,20 @@ <h1> {{ page.glossary_top_header }} </h1>
         </a>
         {%- endif %}
       {%- endfor -%}
-      <b class="glossary_text">  {{ page.glossary_mid_text }} </b>
     </div>
-    <div id="glossary_filter">
+    <fieldset id="glossary_filter">
+        <legend class="glossary_text">  {{ page.glossary_mid_text }} </legend>
         <input id="glossary_search" type="search" placeholder="Search" />
         <div id="glossary_filter_titlev2">{{ page.glossary_filter_text }}</div>
         {%- for tag in page.glossary_tags -%}
         <div class="glossary_filter_div">
-          <label for="filter_{{ tag.name | slugify }}"> <input type="checkbox" name="filter_{{ tag.name | slugify }}" id="input_filter_{{ tag.name | slugify }}" value="{{tag.name | downcase }}" />
+          <label for="filter_{{ tag.name | slugify }}"> <input type="checkbox" name="filter_{{ tag.name | slugify }}" id="filter_{{ tag.name | slugify }}" value="{{tag.name | downcase }}" />
             {{tag.name}}
           </label>
         </div>
         {%- endfor -%}
 
-    </div>
+    </fieldset>
 
     <div id="glossary_list" class="flex mx-auto">
       <div class="d-flex" style="width: 100%;">
@@ -309,7 +309,7 @@ <h1> {{ page.glossary_top_header }} </h1>
       {%- for glossary in glossary_sorted -%}
       {%- assign glossary_id = glossary['name'] | slugify | downcase -%}
         <div id="filter_{{ glossary_id }}" class="term flex">
-          <h2 id="{{ glossary_id }}"></h2>
+          <div id="{{ glossary_id }}" class="anchor"></div>
           <div class="col-6" style="word-break: break-all;"><p class="title">{{ glossary['name'] }} <a class="glossary_share" data-clipboard-text="#{{ glossary_id }}" id="cp_{{glossary_id}}"><i class="fas fa-link"></i></a><span id="dv_cp_{{glossary_id}}"></span></p>
           </div>
           <div class="col-6">{{ glossary['description'] }}
@@ -342,4 +342,3 @@ <h2 id="{{ glossary_id }}"></h2>
   <div id="toc" ></div>
 </div>
 {%- endunless -%}
-
diff --git a/_layouts/api_page.html b/_layouts/api_page.html
index f87b3d6cd76..835814309d4 100644
--- a/_layouts/api_page.html
+++ b/_layouts/api_page.html
@@ -82,7 +82,7 @@
 <div class="d-none d-lg-block col-lg-2 d-print-none" id="toc_col">
   <div class="gitedit_div" style="margin-top: 30px;padding-left: 5px;">
       <a href="{{site.github_baseurl}}{{page.relative_path }}" class="extignore" target="_blank">
-          <img src="{{site.baseurl}}/assets/img/{{site.github_icon}}" /> &nbsp; {{ site.data.i18n[site.language]['edit_github'] | default: "Edit this page on GitHub" }}
+          <img src="{{site.baseurl}}/assets/img/{{site.github_icon}}" alt="Github" /> &nbsp; {{ site.data.i18n[site.language]['edit_github'] | default: "Edit this page on GitHub" }}
       </a>
   </div>
   <div id="toc" ></div>
diff --git a/_layouts/broken_page.html b/_layouts/broken_page.html
index 1ba30e254db..18a3f6c0442 100644
--- a/_layouts/broken_page.html
+++ b/_layouts/broken_page.html
@@ -151,7 +151,7 @@
 
     <div id="broken-main">
       <div id="broken_banner">
-        <div id="broken_banner_img"><img src="{{ page.broken_image | multi_lang }}" /></div>
+        <div id="broken_banner_img"><img src="{{ page.broken_image | multi_lang }}" alt="Broken Image" /></div>
         <div id="broken_banner_info" class="broken_info">
           <div id="content_start"></div>
           <div id="broken_banner_text">
diff --git a/_layouts/dev_guide.html b/_layouts/dev_guide.html
index cfb599d5e89..b36861537a8 100644
--- a/_layouts/dev_guide.html
+++ b/_layouts/dev_guide.html
@@ -70,7 +70,7 @@ <h2 class="guide_featured_title"> {{ page.guide_featured_title }} </h2>
             <i class="{{menu_list.fa_icon}}"></i>
             {%- else -%}
               {%- if menu_list.image -%}
-              <img src="{{site.baseurl}}{{ menu_list.image}} " />
+              <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
               {%- endif -%}
             {%- endif -%}
             <div class="menu_description">
@@ -102,7 +102,7 @@ <h2 class="guide_menu_title"> {{ page.guide_menu_title }} </h2>
         <i class="{{menu_list.fa_icon}}"></i>
         {%- else -%}
           {%- if menu_list.image -%}
-          <img src="{{site.baseurl}}{{ menu_list.image}} " />
+          <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
           {%- endif -%}
         {%- endif -%}
         <div class="menu_description">
@@ -130,7 +130,7 @@ <h2 class="guide_menu_title"> {{ page.guide_menu_title2 }} </h2>
         <i class="{{menu_list.fa_icon}}"></i>
         {%- else -%}
           {%- if menu_list.image -%}
-          <img src="{{site.baseurl}}{{ menu_list.image}} " />
+          <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
           {%- endif -%}
         {%- endif -%}
         <div class="menu_description">
@@ -160,7 +160,7 @@ <h2 class="guide_menu_title"> {{ page.guide_menu_title3 }} </h2>
         <i class="{{menu_list.fa_icon}}"></i>
         {%- else -%}
           {%- if menu_list.image -%}
-          <img src="{{site.baseurl}}{{ menu_list.image}} " />
+          <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
           {%- endif -%}
         {%- endif -%}
         <div class="menu_description">
@@ -189,7 +189,7 @@ <h2 class="guide_menu_title"> {{ page.guide_menu_title4 }} </h2>
         <i class="{{menu_list.fa_icon}}"></i>
         {%- else -%}
           {%- if menu_list.image -%}
-          <img src="{{site.baseurl}}{{ menu_list.image}} " />
+          <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
           {%- endif -%}
         {%- endif -%}
         <div class="menu_description">
@@ -218,7 +218,7 @@ <h2 class="guide_menu_title"> {{ page.guide_menu_title5 }} </h2>
         <i class="{{menu_list.fa_icon}}"></i>
         {%- else -%}
           {%- if menu_list.image -%}
-          <img src="{{site.baseurl}}{{ menu_list.image}} " />
+          <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
           {%- endif -%}
         {%- endif -%}
         <div class="menu_description">
@@ -247,7 +247,7 @@ <h2 class="guide_menu_title"> {{ page.guide_menu_title6 }} </h2>
         <i class="{{menu_list.fa_icon}}"></i>
         {%- else -%}
           {%- if menu_list.image -%}
-          <img src="{{site.baseurl}}{{ menu_list.image}} " />
+          <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
           {%- endif -%}
         {%- endif -%}
         <div class="menu_description">
@@ -276,7 +276,7 @@ <h2 class="guide_menu_title"> {{ page.guide_menu_title7 }} </h2>
         <i class="{{menu_list.fa_icon}}"></i>
         {%- else -%}
           {%- if menu_list.image -%}
-          <img src="{{site.baseurl}}{{ menu_list.image}} " />
+          <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
           {%- endif -%}
         {%- endif -%}
         <div class="menu_description">
@@ -305,7 +305,7 @@ <h2 class="guide_menu_title"> {{ page.guide_menu_title8 }} </h2>
         <i class="{{menu_list.fa_icon}}"></i>
         {%- else -%}
           {%- if menu_list.image -%}
-          <img src="{{site.baseurl}}{{ menu_list.image}} " />
+          <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
           {%- endif -%}
         {%- endif -%}
         <div class="menu_description">
@@ -331,7 +331,7 @@ <h2 class="guide_menu_title"> {{ page.guide_menu_title9 }} </h2>
         <i class="{{menu_list.fa_icon}}"></i>
         {%- else -%}
           {%- if menu_list.image -%}
-          <img src="{{site.baseurl}}{{ menu_list.image}} " />
+          <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
           {%- endif -%}
         {%- endif -%}
         <div class="menu_description">
@@ -362,4 +362,4 @@ <h1> {{ page.guide_footer_header }} </h1>
     {%- endunless -%}
 
     {% include footer.html class="footer_dev" %}
-</div>
\ No newline at end of file
+</div>
diff --git a/_layouts/doc_guide.html b/_layouts/doc_guide.html
index 2c8f330d2b8..492180fa940 100644
--- a/_layouts/doc_guide.html
+++ b/_layouts/doc_guide.html
@@ -61,7 +61,7 @@ <h2 class="doc_menu_title"> {{ page.doc_top_header }} </h2>
         <div id="{{ doc_list.name | handle }}" class="doc_item">
           <div class="doc_img">
           {%- if doc_list.image -%}
-          <img src="{{site.baseurl}}{{ doc_list.image}} " />
+          <img src="{{site.baseurl}}{{ doc_list.image}} " alt="{{doc_list.name}}" />
           {%- endif -%}
           </div>
           <div class="doc_info">
@@ -73,7 +73,7 @@ <h2 class="doc_menu_title"> {{ page.doc_top_header }} </h2>
             </div>
           </div>
           <div class="doc_img arrow">
-            <img src="{{site.baseurl}}/assets/img/braze_icons/arrow-circle-right-pink.svg" />
+            <img src="{{site.baseurl}}/assets/img/braze_icons/arrow-circle-right-pink.svg" alt="Arrow Right" />
           </div>
         </div>
           {%- if doc_list.link -%}
@@ -86,7 +86,7 @@ <h2 class="doc_menu_title"> {{ page.doc_top_header }} </h2>
           <a href="https://learning.braze.com" target="_blank">
 
           <div id="doc_lab">
-            <div id="doc_lab_img"><img src="{{site.baseurl}}/assets/img/braze_learning.png" /></div>
+            <div id="doc_lab_img"><img src="{{site.baseurl}}/assets/img/braze_learning.png" alt="Braze Learning" /></div>
             <div id="doc_lab_info" class="doc_info">
               <div class="doc_name">
                 Braze Learning
diff --git a/_layouts/documents.html b/_layouts/documents.html
index b157734c3cd..48fa0f242b4 100644
--- a/_layouts/documents.html
+++ b/_layouts/documents.html
@@ -71,7 +71,7 @@
 <div class="d-none d-lg-block col-lg-2 d-print-none" id="toc_col">
   <div class="gitedit_div" style="margin-top: 30px;padding-left: 5px;">
       <a href="{{site.github_baseurl}}{{page.relative_path }}" class="extignore" target="_blank">
-          <img src="{{site.baseurl}}/assets/img/{{site.github_icon}}" /> &nbsp; {{ site.data.i18n[site.language]['edit_github'] | default: "Edit this page on GitHub" }}
+          <img src="{{site.baseurl}}/assets/img/{{site.github_icon}}" alt="Github" /> &nbsp; {{ site.data.i18n[site.language]['edit_github'] | default: "Edit this page on GitHub" }}
       </a>
   </div>
   <div id="toc" ></div>
diff --git a/_layouts/email_report_metrics.html b/_layouts/email_report_metrics.html
new file mode 100644
index 00000000000..cd6f139f9c1
--- /dev/null
+++ b/_layouts/email_report_metrics.html
@@ -0,0 +1,285 @@
+---
+layout: default
+hide_toc: true
+hide_bottom_nav: false
+hide_breadcrumb: false
+---
+
+
+
+{%- comment -%} Assigned variables first by page, then by layout {%- endcomment -%}
+{%- assign hide_nav = page.hide_nav -%}
+
+
+{%- assign hide_bottom_nav = page.hide_bottom_nav -%}
+{%- assign hide_breadcrumb = page.hide_breadcrumb -%}
+{%- assign hide_feedback = page.hide_feedback -%}
+{%- assign hide_toc = page.hide_toc -%}
+{%- unless hide_nav -%}
+{%- assign hide_nav = layout.hide_nav -%}
+{%- endunless -%}
+{%- unless hide_toc -%}
+{%- assign hide_toc = layout.hide_toc -%}
+{%- endunless -%}
+
+{%- unless hide_bottom_nav -%}
+{%- assign hide_bottom_nav = layout.hide_bottom_nav -%}
+{%- endunless -%}
+{%- unless hide_breadcrumb -%}
+{%- assign hide_breadcrumb = layout.hide_breadcrumb -%}
+{%- endunless -%}
+{%- unless hide_feedback -%}
+{%- assign hide_feedback = layout.hide_feedback -%}
+{%- endunless -%}
+
+{% unless hide_nav %}
+<!-- button id="sidebar_toggle" class="btn btn-info d-print-none" data-toggle="collapse" aria-expanded="true" href="#nav_bar" >
+   <i class="fas"></i>
+</button -->
+
+<script type="text/javascript">
+
+$(document).ready(function() {
+  function string_to_slug(str) {
+    str = str.replace(/^\s+|\s+$/g, ''); // trim
+    str = str.toLowerCase();
+
+    // remove accents, swap ñ for n, etc
+    var from = "àáäâèéëêìíïîòóöôùúüûñç·/_,:;";
+    var to   = "aaaaeeeeiiiioooouuuunc------";
+    for (var i=0, l=from.length ; i<l ; i++) {
+        str = str.replace(new RegExp(from.charAt(i), 'g'), to.charAt(i));
+    }
+
+    str = str.replace(/[\(\)]/g, '') // remove parenthsis
+        .replace(/[^a-z0-9 -]/g, '-') // remove invalid chars
+        .replace(/\s+/g, '-') // collapse whitespace and replace by -
+        .replace(/-+/g, '-');  // collapse dashes
+
+    return str;
+  }
+  function getUrlParameter(name) {
+    name = name.replace(/[\[]/, '\\[').replace(/[\]]/, '\\]');
+    var regex = new RegExp('[\\?&]' + name + '=([^&#]*)');
+    var results = regex.exec(location.search);
+    return results === null ? '' : decodeURIComponent(results[1].replace(/\+/g, ' '));
+  };
+
+
+  var alltags = {}
+
+  function matchterms(searchterm, items) {
+    var found = false;
+    if (Array.isArray(items)) {
+      for (var i = 0; i < items.length; i++ ) {
+        if (Array.isArray(searchterm)) {
+          for (var j = 0; j < searchterm.length; j++ ) {
+            if (items[i].trim().toLowerCase() == searchterm[j].trim().toLowerCase()) {
+              found = true
+            }
+          }
+        }
+        else {
+          if (items[i].trim().toLowerCase() == searchterm.trim().toLowerCase()) {
+            found = true
+          }
+        }
+      }
+    }
+    else {
+      if (Array.isArray(searchterm)) {
+        for (var j = 0; j < searchterm.length; j++ ) {
+          if (items.trim().toLowerCase() == searchterm[j].trim().toLowerCase()) {
+            found = true
+          }
+        }
+      }
+      else {
+        if (items.trim().toLowerCase().indexOf(searchterm.trim().toLowerCase()) > -1) {
+          found = true
+        }
+      }
+    }
+    return found;
+  }
+
+  function find_tags(){
+    var api_tags = $('.api_tags');
+    var alltags = {};
+    api_tags.each(function(k,v){
+      var curtag = $(this);
+      var tag_list = curtag.attr('data-tags').split(',');
+      for (var i = 0; i < tag_list.length; i++) {
+        var trimtag = tag_list[i].trim();
+        if (trimtag.toLowerCase() != 'all') {
+          alltags[trimtag.toLowerCase()] = trimtag;
+        }
+      }
+    });
+    return alltags;
+  }
+  function set_tags(alltags) {
+    var tag_div = $('#api_filter_list');
+    var sorted_tags = []
+    $.each(alltags, function(k,v){
+      sorted_tags.push(k)
+    });
+    sorted_tags.sort();
+    $.each(sorted_tags,function(k,v){
+      var filter_slug = string_to_slug(v);
+      var filter_div = $('<div>').addClass('api_filter_div');
+      var filter_label = $('<label>').attr('for','api_' + filter_slug);
+      var filter_cb = $('<input>').attr('id','api_' + filter_slug).attr('type','checkbox').attr('name','filter_' + filter_slug).val(v)
+      filter_label.append(filter_cb).append(' ' + alltags[v]);
+      filter_div.append(filter_label);
+      tag_div.append(filter_div);
+    })
+  }
+
+
+    function search_apis(api_hash) {
+      var result_cnt = 0;
+      $('#results_msg').hide();
+      var api_div = $('#api_list .api_div');
+      var search_str = $('#api_search').val().toLowerCase();
+      var selected_vals = [];
+      $('.api_filter_div input[type="checkbox"]:checked').each(function(k,v){
+       selected_vals.push($(this).val());
+      })
+      var showall = true;
+      if (selected_vals.length || search_str) {
+        showall = false;
+      }
+      api_div.each(function(k,v){
+        var filtered = false;
+        var curdiv = $(this);
+        curdiv.show();
+        if (!showall) {
+          var curtag = curdiv.find('.api_tags').first();
+          var apitags = []
+          if (curtag) {
+            apitags = curtag.attr('data-tags-lower').split(',');
+          }
+
+          if (selected_vals.length) {
+            // api doesn't have an all tag filter explicitly
+            if (apitags.indexOf('all') == -1) {
+              // check if tag
+
+              if (!matchterms(selected_vals, apitags) && !filtered) {
+                filtered = true;
+              }
+            }
+          }
+          if (!filtered && search_str) {
+            var curcontent = curdiv.text().replace(/(\n|\r\n|\r)\d+/g,"").toLowerCase().replace(/\s\s+/g, ' ');
+            if (curcontent.indexOf(search_str) < 0) {
+              filtered = true
+            }
+          }
+          if (filtered) {
+            curdiv.hide();
+          }
+          else {
+            curdiv.show();
+            result_cnt++;
+          }
+        }
+      })
+      if (!result_cnt && !showall) {
+        $('#results_msg').html('<p>No metrics matching these filters</p>');
+        $('#results_msg').show();
+      }
+    };
+
+
+  function initialize() {
+    alltags = find_tags();
+    set_tags(alltags);
+    var query_str = getUrlParameter('tags').toLowerCase().split(',');
+    $('.api_filter_div input[type="checkbox"]').each(function(e){
+      $(this).on('click', function(e){
+        search_apis();
+      });
+      if (matchterms($(this).val(), query_str)) {
+        $(this).prop('checked',true);
+      }
+    });
+
+    if (query_str.length) {
+      search_apis();
+    }
+
+    $('#api_search').on('keyup',function(e){
+      search_apis();
+    });
+
+    if (location.hash && $(location.hash.replace('%20','-').replace('+','-')).offset()) {
+      // Scroll to generated hash
+      $('html, body').animate({
+        scrollTop: $(location.hash).offset().top
+      });
+    }
+  };
+  initialize();
+});
+</script>
+
+
+<div class="col-sm-12 col-md-3 col-lg-3 col-xl-2 d-print-none collapse d-md-block" id="nav_bar"  >
+  <div id="nav_col" class="  ">
+  {% include left_nav_menu.html  %}
+  </div>
+</div>
+{% endunless %}
+
+<div class="col d-print-block " id="main_content" >
+
+    <div id="api-main">
+    <div id="content_start"></div>
+    
+    {%- unless hide_breadcrumb -%}
+    <div id="breadcrumb">
+    </div>
+    {%- endunless -%}
+
+
+    <h1> Email report metrics glossary </h1>
+    <p class="api_text">These are terms you'll find in the analytics section of your email campaign or Canvas, post-launch. You can search for the metrics you need or filter by the type of metric. This glossary does not necessarily include metrics you might see in Currents or in other downloaded reports outside of your Braze account.</p>
+
+    <div id="api_filter">
+        <input id="api_search" type="search" placeholder="Search" />
+        <div id="api_filter_list"></div>
+    </div>
+
+    <div id="api_list" class="flex mx-auto api_div">
+      {{content}}
+    </div>
+    <div id="results_msg"></div>
+
+
+  </div>
+    {%- unless hide_bottom_nav -%}
+    <div id="bottom_nav" >
+      {%- unless hide_feedback -%}
+      {% include feedback.html  %}
+      {%- endunless -%}
+      <!-- div class="gradient-line" ></div -->
+      <div id="bottom_page_nav">
+        <a id="page_prev_link"><div id="page_prev" ></div></a>
+        <a id="page_next_link"><div id="page_next" ></div></a>
+      </div>
+    </div>
+
+    {%- endunless -%}
+
+    {% include footer.html class="footer_api" %}
+</div>
+{%- unless hide_toc -%}
+<!-- button id="toc_toggle" class="btn btn-info collapsed notoc d-print-none" data-toggle="collapse" aria-expanded="false" href="#toc_col" >
+   <i class="fas"></i>
+</button -->
+<div class="d-none d-lg-block col-lg-2 d-print-none" id="toc_col">
+  <div id="toc" ></div>
+</div>
+{%- endunless -%}
diff --git a/_layouts/featured.html b/_layouts/featured.html
index 963fc952c63..5f2329d51f6 100644
--- a/_layouts/featured.html
+++ b/_layouts/featured.html
@@ -62,7 +62,7 @@ <h2 class="guide_featured_title"> {{ page.guide_featured_title }} </h2>
             <i class="{{menu_list.fa_icon}}"></i>
             {%- else -%}
               {%- if menu_list.image -%}
-              <img src="{{site.baseurl}}{{ menu_list.image}} " />
+              <img src="{{site.baseurl}}{{ menu_list.image}} " alt="{{ menu_list.name }}" />
               {%- endif -%}
             {%- endif -%}
             <div class="menu_description">
diff --git a/_layouts/glossary_page.html b/_layouts/glossary_page.html
index 81bea041bca..4883fa59451 100644
--- a/_layouts/glossary_page.html
+++ b/_layouts/glossary_page.html
@@ -271,7 +271,7 @@ <h1> {{ page.glossary_top_header }} </h1>
         <div id="glossary_filter_title">{{ page.glossary_filter_text }}</div>
         {%- for tag in page.glossary_tags -%}
         <div class="glossary_filter_div">
-          <label for="filter_{{ tag.name | slugify }}"> <input type="checkbox" name="filter_{{ tag.name | slugify }}" id="input_filter_{{ tag.name | slugify }}" value="{{tag.name | downcase }}" />
+          <label for="filter_{{ tag.name | slugify }}"> <input type="checkbox" name="filter_{{ tag.name | slugify }}" id="filter_{{ tag.name | slugify }}" value="{{tag.name | downcase }}" />
             {{tag.name}}
           </label>
         </div>
@@ -285,10 +285,10 @@ <h1> {{ page.glossary_top_header }} </h1>
       {%- for glossary in glossary_sorted -%}
       {%- assign glossary_id = glossary['name'] | slugify | downcase -%}
         <span id="filter_{{ glossary_id }}" class="term">
-          <h2 id="{{ glossary_id }}"></h2>
+          <div id="{{ glossary_id }}" class="anchor"></div>
           <div class="content"><p class="title">{{ glossary['name'] }} <a class="glossary_share" data-clipboard-text="#{{ glossary_id }}" id="cp_{{glossary_id}}"><i class="fas fa-link"></i></a><span id="dv_cp_{{glossary_id}}"></span></p>
             {%- if glossary['image'] -%}
-            <img src="{{ glossary['image'] }}" />
+            <img src="{{ glossary['image'] }}" alt="{{ glossary['name'] }}" />
             {%- endif -%}
             <p class="desc">{{ glossary['description'] }}</p>
             {%- if glossary['metric'] -%}
@@ -339,4 +339,3 @@ <h2 id="{{ glossary_id }}"></h2>
   <div id="toc" ></div>
 </div>
 {%- endunless -%}
-
diff --git a/_layouts/partner_page.html b/_layouts/partner_page.html
index 5e8a38b04df..f65701b9b0b 100644
--- a/_layouts/partner_page.html
+++ b/_layouts/partner_page.html
@@ -137,7 +137,7 @@
         }
     }
 
-    var card_speciality =  $('<h6>').html((cur_partner['partner_specialties'] || []).join(' '));
+    var card_speciality =  cur_partner['partner_specialties'] ? $('<h6>').html((cur_partner['partner_specialties'] || []).join(' ')) : null;
     var card_content =  $('<div>').addClass('hover_content').append($('<p>').html(cur_partner['partner_description']));
 
     var card_div = $('<div>').addClass('content').append(card_img).append(card_title).append(card_speciality).append(card_content);
@@ -200,10 +200,10 @@
              var toappend = true;
              var filtered = true;
              for (var k = 0 ; k < filter_select.length; k++ ) {
-               var selected_val = $('#' + filter_select[k] +  " option:selected").val();
+             var selected_val = $('#' + filter_select[k] +  " option:selected").val();
                if (selected_val) {
                  toappend = false;
-                 if (cur_partner[filter_map[k]].indexOf(selected_val) < 0 ) {
+                 if ((cur_partner[filter_map[k]] || []).indexOf(selected_val) < 0 ) {
                    filtered = false;
                  }
                }
@@ -299,27 +299,30 @@
     {%- endunless -%}
 
     <h1> {{ page.partner_top_header | markdownify }} </h1>
-    <p class="partner_text">  {{ page.partner_top_text }} </p>
-
-    <div id="partner_filter">
-      <div class="partner_filter_div">
-        <input id="partner_search" type="search" placeholder="Search"></div>
-      <div class="partner_filter_div"><select id="partner_category" class="select">
-        <option value="">All Categories</option>
-      </select>
-
-  </div>
-      <div class="partner_filter_div"><select id="partner_specialty" class="select">
-        <option value="">All Specialties</option>
-      </select>
-  </div>
-      <div class="partner_filter_div"><select id="partner_solutions" class="select">
-        <option value="">All Solutions</option>
-      </select>
-  </div>
-
-    </div>
 
+    <fieldset class="partner_text">
+      <legend>  {{ page.partner_top_text }} </legend>
+
+      <div id="partner_filter">
+        <div class="partner_filter_div">
+          <input id="partner_search" type="search" placeholder="Search" aria-label="Partner Search"></div>
+        <div class="partner_filter_div">
+          <select id="partner_category" class="select" aria-label="Partner Category">
+            <option value="">All Categories</option>
+          </select>
+        </div>
+        <div class="partner_filter_div">
+          <select id="partner_specialty" class="select" aria-label="Partner Speciality">
+            <option value="">All Specialties</option>
+          </select>
+        </div>
+        <div class="partner_filter_div">
+          <select id="partner_solutions" class="select" aria-label="Partner Solutions">
+            <option value="">All Solutions</option>
+          </select>
+        </div>
+      </div>
+    </fieldset>
     <div id="partner_list" class="flex mx-auto">
 
     </div>
diff --git a/_layouts/self_help.html b/_layouts/self_help.html
index 783767dc8f0..7967f8bd9d4 100644
--- a/_layouts/self_help.html
+++ b/_layouts/self_help.html
@@ -62,7 +62,7 @@ <h1> {{ page.help_top_header }} </h1>
           <i class="{{help_list.fa_icon}}"></i>
           {%- else -%}
             {%- if help_list.image -%}
-            <img src="{{site.baseurl}}{{ help_list.image}} " />
+            <img src="{{site.baseurl}}{{ help_list.image}} " alt="Help List" />
             {%- endif -%}
           {%- endif -%}
         </div>
@@ -88,7 +88,7 @@ <h1> {{ page.help_top_header }} </h1>
       <div id="{{ user_list.name | handle }}" class="user_item">
         <div class="user_img" style="background-color: {{ user_list.bg_color}}">
         {%- if user_list.image -%}
-        <img src="{{site.baseurl}}{{ user_list.image}} " />
+        <img src="{{site.baseurl}}{{ user_list.image}} " alt="User List" />
         {%- endif -%}
         </div>
         <div class="user_info">
@@ -130,4 +130,4 @@ <h1> {{ page.help_top_header }} </h1>
 
 {%- endunless -%}
 
-{% include footer.html class="footer_help" %}
\ No newline at end of file
+{% include footer.html class="footer_help" %}
diff --git a/_layouts/user_guide.html b/_layouts/user_guide.html
index dbcb1ef133e..74afd12262b 100644
--- a/_layouts/user_guide.html
+++ b/_layouts/user_guide.html
@@ -62,7 +62,7 @@ <h1> {{ page.user_top_header }} </h1>
       <div id="{{ user_list.name | handle }}" class="user_item">
         <div class="user_img" style="background-color: {{ user_list.bg_color}}">
         {%- if user_list.image -%}
-        <img src="{{site.baseurl}}{{ user_list.image}} " />
+        <img src="{{site.baseurl}}{{ user_list.image}} " alt="User List" />
         {%- endif -%}
         </div>
         <div class="user_info">
diff --git a/_plugins/tabs.rb b/_plugins/tabs.rb
index 63e6accd506..adc273de945 100644
--- a/_plugins/tabs.rb
+++ b/_plugins/tabs.rb
@@ -14,7 +14,7 @@ def render(context)
           if tabs.length > 0
             tabs.each_with_index do |tab, ind|
               # scan returns array of results, only care about first match
-              tabslist += '    <li class="coderow ' + tab[0].gsub(' ', '-')
+              tabslist += '    <li tabindex="0" class="coderow ' + tab[0].gsub(' ', '-')
               if ind == 0
                 tabslist += ' active'
               end
@@ -70,7 +70,7 @@ def render(context)
           if tabs.length > 0
             tabs.each_with_index do |tab, ind|
               # scan returns array of results, only care about first match
-              tabslist += '    <li class="coderow ' + tab[0].gsub(' ', '-') + '_sub_tab'
+              tabslist += '    <li tabindex="0" class="coderow ' + tab[0].gsub(' ', '-') + '_sub_tab'
               if ind == 0
                 tabslist += ' sub_active'
               end
diff --git a/assets/css/_glossary_page.scss b/assets/css/_glossary_page.scss
index b2b3d568e3b..8ecaaeb0a89 100644
--- a/assets/css/_glossary_page.scss
+++ b/assets/css/_glossary_page.scss
@@ -63,6 +63,7 @@
     color: $black-shark;
     margin: 8px 40px;
   }
+
   .glossary_text {
     margin-top: auto;
     color: $text-color;
@@ -91,6 +92,16 @@
     }
   }
 
+  legend {
+    &.glossary_text {
+      font-size: 30px;
+      line-height: 1.4;
+      color: $braze-purple-dark;
+      margin-top: 20px;
+      margin-bottom: 10px;
+    }
+  }
+
   #guide_list, #guide_featured_list {
     width: 100%;
     display: flex;
@@ -374,12 +385,7 @@
     }
 
     // Hack the sticky header
-    > h1[id],
-    > h2[id],
-    > h3[id],
-    > h4[id],
-    > h5[id],
-    > h6[id] {
+    .anchor {
       pointer-events: none;
 
       > div,
@@ -387,13 +393,10 @@
         pointer-events: auto;
       }
 
-      &::before {
-        display: block;
-        height: $calc_offset_top;
-        margin-top: -$calc_offset_top;
-        visibility: hidden;
-        content: "";
-      }
+      display: block;
+      height: $calc_offset_top;
+      margin-top: -$calc_offset_top;
+      visibility: hidden;
       @media print {
         &::before {
           display: none;
@@ -407,7 +410,6 @@
         }
       }
     }
-
   }
 
 
diff --git a/assets/css/_partner_page.scss b/assets/css/_partner_page.scss
index 009c576e4a6..b2312d6928f 100644
--- a/assets/css/_partner_page.scss
+++ b/assets/css/_partner_page.scss
@@ -101,7 +101,7 @@
     }
     #partner_search {
       width: 100%;
-      padding: 14px 14px 14px 30px;
+      padding: 16px 14px 14px 30px;
       font-size: 14px;
       line-height: 1.15;
       margin: 0;
@@ -114,6 +114,7 @@
       background-repeat: no-repeat;
       background-color: transparent;
       border-radius: 6px;
+      border: 2px solid black;
     }
 
     .select {
diff --git a/assets/css/main.scss b/assets/css/main.scss
index b5fa9c76928..86cf81bb7b1 100644
--- a/assets/css/main.scss
+++ b/assets/css/main.scss
@@ -59,9 +59,8 @@ $base_font_size: 16.5px;
 $banner_height: 80px;
 $header_height: 60px;
 $footer_height: 60px;
-$base_off_set: $base_font_size * 1.5;
-$calc_offset_top: $header_height + $base_off_set;
-$calc_offset_view: $header_height  + $base_off_set;
+$calc_offset_top: $header_height;
+$calc_offset_view: $header_height;
 
 // Body variables—Responsive breakpoints and layout dimensions
 $spacing-unit: 30px;
@@ -310,4 +309,3 @@ details {
     color: $text-color;
   }
 }
-
diff --git a/assets/favicon.ico b/assets/favicon.ico
index 73c72ee4670..3d9020bf30b 100644
Binary files a/assets/favicon.ico and b/assets/favicon.ico differ
diff --git a/assets/img/Shopify/catalog_toggle.png b/assets/img/Shopify/catalog_toggle.png
new file mode 100644
index 00000000000..85bd4e154e1
Binary files /dev/null and b/assets/img/Shopify/catalog_toggle.png differ
diff --git a/assets/img/Shopify/edit_config.png b/assets/img/Shopify/edit_config.png
new file mode 100644
index 00000000000..fbcfe4aedc4
Binary files /dev/null and b/assets/img/Shopify/edit_config.png differ
diff --git a/assets/img/add_languages.png b/assets/img/add_languages.png
new file mode 100644
index 00000000000..262bcbe57e1
Binary files /dev/null and b/assets/img/add_languages.png differ
diff --git a/assets/img/adobe/currents_add_data.png b/assets/img/adobe/currents_add_data.png
new file mode 100644
index 00000000000..00dd5c7a63d
Binary files /dev/null and b/assets/img/adobe/currents_add_data.png differ
diff --git a/assets/img/adobe/currents_mapping.png b/assets/img/adobe/currents_mapping.png
new file mode 100644
index 00000000000..eadb2836cdb
Binary files /dev/null and b/assets/img/adobe/currents_mapping.png differ
diff --git a/assets/img/adobe/currents_no_errors.png b/assets/img/adobe/currents_no_errors.png
new file mode 100644
index 00000000000..a369838b377
Binary files /dev/null and b/assets/img/adobe/currents_no_errors.png differ
diff --git a/assets/img/adobe/currents_sources.png b/assets/img/adobe/currents_sources.png
new file mode 100644
index 00000000000..7649464645a
Binary files /dev/null and b/assets/img/adobe/currents_sources.png differ
diff --git a/assets/img/b2b/sf_accounts.png b/assets/img/b2b/sf_accounts.png
new file mode 100644
index 00000000000..8f3ec13d355
Binary files /dev/null and b/assets/img/b2b/sf_accounts.png differ
diff --git a/assets/img/b2b/sf_opportunities.png b/assets/img/b2b/sf_opportunities.png
new file mode 100644
index 00000000000..9cde6ac15fb
Binary files /dev/null and b/assets/img/b2b/sf_opportunities.png differ
diff --git a/assets/img/banner_cards/banner_card_styles.png b/assets/img/banner_cards/banner_card_styles.png
new file mode 100644
index 00000000000..7b6aa8a6a0b
Binary files /dev/null and b/assets/img/banner_cards/banner_card_styles.png differ
diff --git a/assets/img/braze_icons/channel-line.svg b/assets/img/braze_icons/channel-line.svg
new file mode 100644
index 00000000000..2018f83a975
--- /dev/null
+++ b/assets/img/braze_icons/channel-line.svg
@@ -0,0 +1,7 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M15.4789 8.44434H18.7122V9.29767H16.4856V10.3043H18.5122V11.111H16.4856V12.2577H18.7856V13.111H15.4789V8.44434Z" fill="#801ED7"/>
+<path d="M10.6073 8.44434H11.6406L13.6139 11.391V8.44434H14.5739V13.111H13.6806L11.5606 9.931V13.111H10.6073V8.44434Z" fill="#801ED7"/>
+<path d="M8.69136 8.44434H9.69803V13.111H8.69136V8.44434Z" fill="#801ED7"/>
+<path d="M5.19345 8.44434H6.20012V12.2577H8.20012V13.111H5.19345V8.44434Z" fill="#801ED7"/>
+<path d="M21.8659 11.5517C20.8181 16.5833 14.9167 20.3333 12.8776 21.3383C10.5762 22.4725 10.2256 22.0719 10.7415 20.8133C11.536 18.875 10.7415 18.6667 8.88038 18.107C5.71343 17.1547 2.92866 15.5811 2.14521 11.8018C1.34028 7.91894 3.80179 2.51399 11.536 2.02753C18.9804 1.5593 22.7806 7.15915 21.8659 11.5517Z" stroke="#801ED7" stroke-width="2"/>
+</svg>
diff --git a/assets/img/braze_icons/linkedin.svg b/assets/img/braze_icons/linkedin.svg
new file mode 100644
index 00000000000..0bddd625c98
--- /dev/null
+++ b/assets/img/braze_icons/linkedin.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" standalone="no"?>
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN"
+ "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
+<svg version="1.0" xmlns="http://www.w3.org/2000/svg"
+ width="256.000000pt" height="256.000000pt" viewBox="0 0 256.000000 256.000000"
+ preserveAspectRatio="xMidYMid meet">
+
+<g transform="translate(0.000000,256.000000) scale(0.100000,-0.100000)"
+fill="#000000" stroke="none">
+<path d="M141 2550 c-72 -17 -126 -82 -136 -163 -3 -29 -5 -547 -3 -1152 3
+-1017 4 -1102 20 -1131 21 -39 71 -82 106 -92 15 -4 538 -7 1162 -7 1053 0
+1137 1 1166 17 39 21 82 71 92 106 9 35 9 2269 0 2304 -10 35 -53 85 -92 106
+-29 16 -114 17 -1156 19 -619 0 -1140 -2 -1159 -7z m549 -374 c22 -14 52 -45
+67 -68 24 -36 28 -51 28 -118 0 -67 -4 -82 -28 -118 -15 -23 -46 -54 -69 -69
+-36 -24 -51 -28 -118 -28 -67 0 -82 4 -118 28 -85 56 -124 166 -92 262 16 48
+88 121 132 134 58 18 153 7 198 -23z m1169 -555 c157 -49 258 -158 301 -326
+18 -72 20 -111 20 -497 l0 -418 -189 0 -190 0 -4 372 c-4 412 -6 425 -67 489
+-102 107 -299 55 -367 -96 -16 -36 -18 -79 -21 -402 l-3 -363 -190 0 -189 0 0
+610 0 610 180 0 180 0 0 -79 0 -79 58 57 c58 59 152 112 228 130 69 16 188 12
+253 -8z m-1099 -631 l0 -610 -190 0 -190 0 0 610 0 610 190 0 190 0 0 -610z"/>
+</g>
+</svg>
diff --git a/assets/img/campaign_list_example.png b/assets/img/campaign_list_example.png
new file mode 100644
index 00000000000..c7bbad9aafa
Binary files /dev/null and b/assets/img/campaign_list_example.png differ
diff --git a/assets/img/contributing/github/allow_maintainers_to_edit.png b/assets/img/contributing/github/allow_maintainers_to_edit.png
new file mode 100644
index 00000000000..1ad457fc2da
Binary files /dev/null and b/assets/img/contributing/github/allow_maintainers_to_edit.png differ
diff --git a/assets/img/contributing/github/menu_pull_requests.png b/assets/img/contributing/github/menu_pull_requests.png
new file mode 100644
index 00000000000..85a982a073f
Binary files /dev/null and b/assets/img/contributing/github/menu_pull_requests.png differ
diff --git a/assets/img/dixa/dixa-braze-integration.png b/assets/img/dixa/dixa-braze-integration.png
new file mode 100644
index 00000000000..07c5af4f39b
Binary files /dev/null and b/assets/img/dixa/dixa-braze-integration.png differ
diff --git a/assets/img/dixa/dixa-create-integration.png b/assets/img/dixa/dixa-create-integration.png
new file mode 100644
index 00000000000..10d911b3e7e
Binary files /dev/null and b/assets/img/dixa/dixa-create-integration.png differ
diff --git a/assets/img/export_custom_attributes.png b/assets/img/export_custom_attributes.png
new file mode 100644
index 00000000000..4e1563f7ffc
Binary files /dev/null and b/assets/img/export_custom_attributes.png differ
diff --git a/assets/img/line/line_composer.png b/assets/img/line/line_composer.png
index 3a9a2f82c3b..2cc404224c2 100644
Binary files a/assets/img/line/line_composer.png and b/assets/img/line/line_composer.png differ
diff --git a/assets/img/line/test_preview.png b/assets/img/line/test_preview.png
index 8b5c74e5f72..38b7a03cc96 100644
Binary files a/assets/img/line/test_preview.png and b/assets/img/line/test_preview.png differ
diff --git a/assets/img/line/webhook_settings.png b/assets/img/line/webhook_settings.png
index 287c6a6f6b4..cb936220d28 100644
Binary files a/assets/img/line/webhook_settings.png and b/assets/img/line/webhook_settings.png differ
diff --git a/assets/img/mypostcard/mypostcard_compose.jpg b/assets/img/mypostcard/mypostcard_compose.jpg
new file mode 100644
index 00000000000..84c37cd9760
Binary files /dev/null and b/assets/img/mypostcard/mypostcard_compose.jpg differ
diff --git a/assets/img/mypostcard/mypostcard_test.jpg b/assets/img/mypostcard/mypostcard_test.jpg
new file mode 100644
index 00000000000..bc10ed9c383
Binary files /dev/null and b/assets/img/mypostcard/mypostcard_test.jpg differ
diff --git a/assets/img/tracked_aliases.png b/assets/img/tracked_aliases.png
index b62bf45edc8..deea73e0efe 100644
Binary files a/assets/img/tracked_aliases.png and b/assets/img/tracked_aliases.png differ
diff --git a/assets/img_archive/duplicate_canvas.png b/assets/img_archive/duplicate_canvas.png
index e47dc3f0a37..db00e98865a 100644
Binary files a/assets/img_archive/duplicate_canvas.png and b/assets/img_archive/duplicate_canvas.png differ
diff --git a/assets/img_archive/insert_liquid_var_arrow.png b/assets/img_archive/insert_liquid_var_arrow.png
index 11605887231..9758586047b 100644
Binary files a/assets/img_archive/insert_liquid_var_arrow.png and b/assets/img_archive/insert_liquid_var_arrow.png differ
diff --git a/assets/img_archive/insert_var_shot.gif b/assets/img_archive/insert_var_shot.gif
new file mode 100644
index 00000000000..fe98b4530a8
Binary files /dev/null and b/assets/img_archive/insert_var_shot.gif differ
diff --git a/assets/img_archive/rate_limiting_overview_2.png b/assets/img_archive/rate_limiting_overview_2.png
index b800e15996d..78adf263023 100644
Binary files a/assets/img_archive/rate_limiting_overview_2.png and b/assets/img_archive/rate_limiting_overview_2.png differ
diff --git a/assets/js/algolia_search.js b/assets/js/algolia_search.js
index d742d4992de..14b88afdf04 100644
--- a/assets/js/algolia_search.js
+++ b/assets/js/algolia_search.js
@@ -2,14 +2,14 @@
 !function(e,t){"object"==typeof exports&&"undefined"!=typeof module?module.exports=t():"function"==typeof define&&define.amd?define(t):(e=e||self).algoliasearch=t()}(this,(function(){"use strict";function e(e,t,r){return t in e?Object.defineProperty(e,t,{value:r,enumerable:!0,configurable:!0,writable:!0}):e[t]=r,e}function t(e,t){var r=Object.keys(e);if(Object.getOwnPropertySymbols){var n=Object.getOwnPropertySymbols(e);t&&(n=n.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),r.push.apply(r,n)}return r}function r(r){for(var n=1;n<arguments.length;n++){var o=null!=arguments[n]?arguments[n]:{};n%2?t(Object(o),!0).forEach((function(t){e(r,t,o[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(r,Object.getOwnPropertyDescriptors(o)):t(Object(o)).forEach((function(e){Object.defineProperty(r,e,Object.getOwnPropertyDescriptor(o,e))}))}return r}function n(e,t){if(null==e)return{};var r,n,o=function(e,t){if(null==e)return{};var r,n,o={},a=Object.keys(e);for(n=0;n<a.length;n++)r=a[n],t.indexOf(r)>=0||(o[r]=e[r]);return o}(e,t);if(Object.getOwnPropertySymbols){var a=Object.getOwnPropertySymbols(e);for(n=0;n<a.length;n++)r=a[n],t.indexOf(r)>=0||Object.prototype.propertyIsEnumerable.call(e,r)&&(o[r]=e[r])}return o}function o(e,t){return function(e){if(Array.isArray(e))return e}(e)||function(e,t){if(!(Symbol.iterator in Object(e)||"[object Arguments]"===Object.prototype.toString.call(e)))return;var r=[],n=!0,o=!1,a=void 0;try{for(var u,i=e[Symbol.iterator]();!(n=(u=i.next()).done)&&(r.push(u.value),!t||r.length!==t);n=!0);}catch(e){o=!0,a=e}finally{try{n||null==i.return||i.return()}finally{if(o)throw a}}return r}(e,t)||function(){throw new TypeError("Invalid attempt to destructure non-iterable instance")}()}function a(e){return function(e){if(Array.isArray(e)){for(var t=0,r=new Array(e.length);t<e.length;t++)r[t]=e[t];return r}}(e)||function(e){if(Symbol.iterator in Object(e)||"[object Arguments]"===Object.prototype.toString.call(e))return Array.from(e)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance")}()}function u(e){var t,r="algoliasearch-client-js-".concat(e.key),n=function(){return void 0===t&&(t=e.localStorage||window.localStorage),t},a=function(){return JSON.parse(n().getItem(r)||"{}")};return{get:function(e,t){var r=arguments.length>2&&void 0!==arguments[2]?arguments[2]:{miss:function(){return Promise.resolve()}};return Promise.resolve().then((function(){var r=JSON.stringify(e),n=a()[r];return Promise.all([n||t(),void 0!==n])})).then((function(e){var t=o(e,2),n=t[0],a=t[1];return Promise.all([n,a||r.miss(n)])})).then((function(e){return o(e,1)[0]}))},set:function(e,t){return Promise.resolve().then((function(){var o=a();return o[JSON.stringify(e)]=t,n().setItem(r,JSON.stringify(o)),t}))},delete:function(e){return Promise.resolve().then((function(){var t=a();delete t[JSON.stringify(e)],n().setItem(r,JSON.stringify(t))}))},clear:function(){return Promise.resolve().then((function(){n().removeItem(r)}))}}}function i(e){var t=a(e.caches),r=t.shift();return void 0===r?{get:function(e,t){var r=arguments.length>2&&void 0!==arguments[2]?arguments[2]:{miss:function(){return Promise.resolve()}},n=t();return n.then((function(e){return Promise.all([e,r.miss(e)])})).then((function(e){return o(e,1)[0]}))},set:function(e,t){return Promise.resolve(t)},delete:function(e){return Promise.resolve()},clear:function(){return Promise.resolve()}}:{get:function(e,n){var o=arguments.length>2&&void 0!==arguments[2]?arguments[2]:{miss:function(){return Promise.resolve()}};return r.get(e,n,o).catch((function(){return i({caches:t}).get(e,n,o)}))},set:function(e,n){return r.set(e,n).catch((function(){return i({caches:t}).set(e,n)}))},delete:function(e){return r.delete(e).catch((function(){return i({caches:t}).delete(e)}))},clear:function(){return r.clear().catch((function(){return i({caches:t}).clear()}))}}}function s(){var e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:{serializable:!0},t={};return{get:function(r,n){var o=arguments.length>2&&void 0!==arguments[2]?arguments[2]:{miss:function(){return Promise.resolve()}},a=JSON.stringify(r);if(a in t)return Promise.resolve(e.serializable?JSON.parse(t[a]):t[a]);var u=n(),i=o&&o.miss||function(){return Promise.resolve()};return u.then((function(e){return i(e)})).then((function(){return u}))},set:function(r,n){return t[JSON.stringify(r)]=e.serializable?JSON.stringify(n):n,Promise.resolve(n)},delete:function(e){return delete t[JSON.stringify(e)],Promise.resolve()},clear:function(){return t={},Promise.resolve()}}}function c(e){for(var t=e.length-1;t>0;t--){var r=Math.floor(Math.random()*(t+1)),n=e[t];e[t]=e[r],e[r]=n}return e}function l(e,t){return Object.keys(void 0!==t?t:{}).forEach((function(r){e[r]=t[r](e)})),e}function f(e){for(var t=arguments.length,r=new Array(t>1?t-1:0),n=1;n<t;n++)r[n-1]=arguments[n];var o=0;return e.replace(/%s/g,(function(){return encodeURIComponent(r[o++])}))}var h={WithinQueryParameters:0,WithinHeaders:1};function d(e,t){var r=e||{},n=r.data||{};return Object.keys(r).forEach((function(e){-1===["timeout","headers","queryParameters","data","cacheable"].indexOf(e)&&(n[e]=r[e])})),{data:Object.entries(n).length>0?n:void 0,timeout:r.timeout||t,headers:r.headers||{},queryParameters:r.queryParameters||{},cacheable:r.cacheable}}var m={Read:1,Write:2,Any:3},p=1,v=2,y=3;function g(e){var t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:p;return r(r({},e),{},{status:t,lastUpdate:Date.now()})}function b(e){return"string"==typeof e?{protocol:"https",url:e,accept:m.Any}:{protocol:e.protocol||"https",url:e.url,accept:e.accept||m.Any}}var O="GET",P="POST";function q(e,t){return Promise.all(t.map((function(t){return e.get(t,(function(){return Promise.resolve(g(t))}))}))).then((function(e){var r=e.filter((function(e){return function(e){return e.status===p||Date.now()-e.lastUpdate>12e4}(e)})),n=e.filter((function(e){return function(e){return e.status===y&&Date.now()-e.lastUpdate<=12e4}(e)})),o=[].concat(a(r),a(n));return{getTimeout:function(e,t){return(0===n.length&&0===e?1:n.length+3+e)*t},statelessHosts:o.length>0?o.map((function(e){return b(e)})):t}}))}function j(e,t,n,o){var u=[],i=function(e,t){if(e.method===O||void 0===e.data&&void 0===t.data)return;var n=Array.isArray(e.data)?e.data:r(r({},e.data),t.data);return JSON.stringify(n)}(n,o),s=function(e,t){var n=r(r({},e.headers),t.headers),o={};return Object.keys(n).forEach((function(e){var t=n[e];o[e.toLowerCase()]=t})),o}(e,o),c=n.method,l=n.method!==O?{}:r(r({},n.data),o.data),f=r(r(r({"x-algolia-agent":e.userAgent.value},e.queryParameters),l),o.queryParameters),h=0,d=function t(r,a){var l=r.pop();if(void 0===l)throw{name:"RetryError",message:"Unreachable hosts - your application id may be incorrect. If the error persists, contact support@algolia.com.",transporterStackTrace:A(u)};var d={data:i,headers:s,method:c,url:w(l,n.path,f),connectTimeout:a(h,e.timeouts.connect),responseTimeout:a(h,o.timeout)},m=function(e){var t={request:d,response:e,host:l,triesLeft:r.length};return u.push(t),t},p={onSucess:function(e){return function(e){try{return JSON.parse(e.content)}catch(t){throw function(e,t){return{name:"DeserializationError",message:e,response:t}}(t.message,e)}}(e)},onRetry:function(n){var o=m(n);return n.isTimedOut&&h++,Promise.all([e.logger.info("Retryable failure",x(o)),e.hostsCache.set(l,g(l,n.isTimedOut?y:v))]).then((function(){return t(r,a)}))},onFail:function(e){throw m(e),function(e,t){var r=e.content,n=e.status,o=r;try{o=JSON.parse(r).message}catch(e){}return function(e,t,r){return{name:"ApiError",message:e,status:t,transporterStackTrace:r}}(o,n,t)}(e,A(u))}};return e.requester.send(d).then((function(e){return function(e,t){return function(e){var t=e.status;return e.isTimedOut||function(e){var t=e.isTimedOut,r=e.status;return!t&&0==~~r}(e)||2!=~~(t/100)&&4!=~~(t/100)}(e)?t.onRetry(e):2==~~(e.status/100)?t.onSucess(e):t.onFail(e)}(e,p)}))};return q(e.hostsCache,t).then((function(e){return d(a(e.statelessHosts).reverse(),e.getTimeout)}))}function S(e){var t={value:"Algolia for JavaScript (".concat(e,")"),add:function(e){var r="; ".concat(e.segment).concat(void 0!==e.version?" (".concat(e.version,")"):"");return-1===t.value.indexOf(r)&&(t.value="".concat(t.value).concat(r)),t}};return t}function w(e,t,r){var n=T(r),o="".concat(e.protocol,"://").concat(e.url,"/").concat("/"===t.charAt(0)?t.substr(1):t);return n.length&&(o+="?".concat(n)),o}function T(e){return Object.keys(e).map((function(t){return f("%s=%s",t,(r=e[t],"[object Object]"===Object.prototype.toString.call(r)||"[object Array]"===Object.prototype.toString.call(r)?JSON.stringify(e[t]):e[t]));var r})).join("&")}function A(e){return e.map((function(e){return x(e)}))}function x(e){var t=e.request.headers["x-algolia-api-key"]?{"x-algolia-api-key":"*****"}:{};return r(r({},e),{},{request:r(r({},e.request),{},{headers:r(r({},e.request.headers),t)})})}var C=function(e){var t=e.appId,n=function(e,t,r){var n={"x-algolia-api-key":r,"x-algolia-application-id":t};return{headers:function(){return e===h.WithinHeaders?n:{}},queryParameters:function(){return e===h.WithinQueryParameters?n:{}}}}(void 0!==e.authMode?e.authMode:h.WithinHeaders,t,e.apiKey),a=function(e){var t=e.hostsCache,r=e.logger,n=e.requester,a=e.requestsCache,u=e.responsesCache,i=e.timeouts,s=e.userAgent,c=e.hosts,l=e.queryParameters,f={hostsCache:t,logger:r,requester:n,requestsCache:a,responsesCache:u,timeouts:i,userAgent:s,headers:e.headers,queryParameters:l,hosts:c.map((function(e){return b(e)})),read:function(e,t){var r=d(t,f.timeouts.read),n=function(){return j(f,f.hosts.filter((function(e){return 0!=(e.accept&m.Read)})),e,r)};if(!0!==(void 0!==r.cacheable?r.cacheable:e.cacheable))return n();var a={request:e,mappedRequestOptions:r,transporter:{queryParameters:f.queryParameters,headers:f.headers}};return f.responsesCache.get(a,(function(){return f.requestsCache.get(a,(function(){return f.requestsCache.set(a,n()).then((function(e){return Promise.all([f.requestsCache.delete(a),e])}),(function(e){return Promise.all([f.requestsCache.delete(a),Promise.reject(e)])})).then((function(e){var t=o(e,2);t[0];return t[1]}))}))}),{miss:function(e){return f.responsesCache.set(a,e)}})},write:function(e,t){return j(f,f.hosts.filter((function(e){return 0!=(e.accept&m.Write)})),e,d(t,f.timeouts.write))}};return f}(r(r({hosts:[{url:"".concat(t,"-dsn.algolia.net"),accept:m.Read},{url:"".concat(t,".algolia.net"),accept:m.Write}].concat(c([{url:"".concat(t,"-1.algolianet.com")},{url:"".concat(t,"-2.algolianet.com")},{url:"".concat(t,"-3.algolianet.com")}]))},e),{},{headers:r(r(r({},n.headers()),{"content-type":"application/x-www-form-urlencoded"}),e.headers),queryParameters:r(r({},n.queryParameters()),e.queryParameters)}));return l({transporter:a,appId:t,addAlgoliaAgent:function(e,t){a.userAgent.add({segment:e,version:t})},clearCache:function(){return Promise.all([a.requestsCache.clear(),a.responsesCache.clear()]).then((function(){}))}},e.methods)},N=function(e){return function(t){var r=arguments.length>1&&void 0!==arguments[1]?arguments[1]:{},n={transporter:e.transporter,appId:e.appId,indexName:t};return l(n,r.methods)}},k=function(e){return function(t,n){var o=t.map((function(e){return r(r({},e),{},{params:T(e.params||{})})}));return e.transporter.read({method:P,path:"1/indexes/*/queries",data:{requests:o},cacheable:!0},n)}},J=function(e){return function(t,o){return Promise.all(t.map((function(t){var a=t.params,u=a.facetName,i=a.facetQuery,s=n(a,["facetName","facetQuery"]);return N(e)(t.indexName,{methods:{searchForFacetValues:I}}).searchForFacetValues(u,i,r(r({},o),s))})))}},E=function(e){return function(t,r){return e.transporter.read({method:P,path:f("1/indexes/%s/query",e.indexName),data:{query:t},cacheable:!0},r)}},I=function(e){return function(t,r,n){return e.transporter.read({method:P,path:f("1/indexes/%s/facets/%s/query",e.indexName,t),data:{facetQuery:r},cacheable:!0},n)}},F=1,R=2,D=3;function W(e,t,n){var o,a={appId:e,apiKey:t,timeouts:{connect:1,read:2,write:30},requester:{send:function(e){return new Promise((function(t){var r=new XMLHttpRequest;r.open(e.method,e.url,!0),Object.keys(e.headers).forEach((function(t){return r.setRequestHeader(t,e.headers[t])}));var n,o=function(e,n){return setTimeout((function(){r.abort(),t({status:0,content:n,isTimedOut:!0})}),1e3*e)},a=o(e.connectTimeout,"Connection timeout");r.onreadystatechange=function(){r.readyState>r.OPENED&&void 0===n&&(clearTimeout(a),n=o(e.responseTimeout,"Socket timeout"))},r.onerror=function(){0===r.status&&(clearTimeout(a),clearTimeout(n),t({content:r.responseText||"Network request failed",status:r.status,isTimedOut:!1}))},r.onload=function(){clearTimeout(a),clearTimeout(n),t({content:r.responseText,status:r.status,isTimedOut:!1})},r.send(e.data)}))}},logger:(o=D,{debug:function(e,t){return F>=o&&console.debug(e,t),Promise.resolve()},info:function(e,t){return R>=o&&console.info(e,t),Promise.resolve()},error:function(e,t){return console.error(e,t),Promise.resolve()}}),responsesCache:s(),requestsCache:s({serializable:!1}),hostsCache:i({caches:[u({key:"".concat("4.5.1","-").concat(e)}),s()]}),userAgent:S("4.5.1").add({segment:"Browser",version:"lite"}),authMode:h.WithinQueryParameters};return C(r(r(r({},a),n),{},{methods:{search:k,searchForFacetValues:J,multipleQueries:k,multipleSearchForFacetValues:J,initIndex:function(e){return function(t){return N(e)(t,{methods:{search:E,searchForFacetValues:I}})}}}}))}return W.version="4.5.1",W}));
 
 /*! InstantSearch.js 4.8.3 | © Algolia, Inc. and contributors; MIT License | https://github.com/algolia/instantsearch.js */
-!function(e,t){"object"==typeof exports&&"undefined"!=typeof module?module.exports=t():"function"==typeof define&&define.amd?define(t):(e=e||self).instantsearch=t()}(this,function(){"use strict";function h(e){return(h="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e})(e)}function k(e,t){if(!(e instanceof t))throw new TypeError("Cannot call a class as a function")}function r(e,t){for(var n=0;n<t.length;n++){var r=t[n];r.enumerable=r.enumerable||!1,r.configurable=!0,"value"in r&&(r.writable=!0),Object.defineProperty(e,r.key,r)}}function M(e,t,n){return t&&r(e.prototype,t),n&&r(e,n),e}function L(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function f(){return(f=Object.assign||function(e){for(var t=1;t<arguments.length;t++){var n=arguments[t];for(var r in n)Object.prototype.hasOwnProperty.call(n,r)&&(e[r]=n[r])}return e}).apply(this,arguments)}function i(t,e){var n=Object.keys(t);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(t);e&&(r=r.filter(function(e){return Object.getOwnPropertyDescriptor(t,e).enumerable})),n.push.apply(n,r)}return n}function D(t){for(var e=1;e<arguments.length;e++){var n=null!=arguments[e]?arguments[e]:{};e%2?i(Object(n),!0).forEach(function(e){L(t,e,n[e])}):Object.getOwnPropertyDescriptors?Object.defineProperties(t,Object.getOwnPropertyDescriptors(n)):i(Object(n)).forEach(function(e){Object.defineProperty(t,e,Object.getOwnPropertyDescriptor(n,e))})}return t}function j(e,t){if("function"!=typeof t&&null!==t)throw new TypeError("Super expression must either be null or a function");e.prototype=Object.create(t&&t.prototype,{constructor:{value:e,writable:!0,configurable:!0}}),t&&n(e,t)}function O(e){return(O=Object.setPrototypeOf?Object.getPrototypeOf:function(e){return e.__proto__||Object.getPrototypeOf(e)})(e)}function n(e,t){return(n=Object.setPrototypeOf||function(e,t){return e.__proto__=t,e})(e,t)}function A(e,t){if(null==e)return{};var n,r,i=function(e,t){if(null==e)return{};var n,r,i={},a=Object.keys(e);for(r=0;r<a.length;r++)n=a[r],0<=t.indexOf(n)||(i[n]=e[n]);return i}(e,t);if(Object.getOwnPropertySymbols){var a=Object.getOwnPropertySymbols(e);for(r=0;r<a.length;r++)n=a[r],0<=t.indexOf(n)||Object.prototype.propertyIsEnumerable.call(e,n)&&(i[n]=e[n])}return i}function H(e){if(void 0===e)throw new ReferenceError("this hasn't been initialised - super() hasn't been called");return e}function B(e,t){return!t||"object"!=typeof t&&"function"!=typeof t?H(e):t}function Q(e,t){return function(e){if(Array.isArray(e))return e}(e)||function(e,t){if(!(Symbol.iterator in Object(e)||"[object Arguments]"===Object.prototype.toString.call(e)))return;var n=[],r=!0,i=!1,a=void 0;try{for(var s,o=e[Symbol.iterator]();!(r=(s=o.next()).done)&&(n.push(s.value),!t||n.length!==t);r=!0);}catch(e){i=!0,a=e}finally{try{r||null==o.return||o.return()}finally{if(i)throw a}}return n}(e,t)||function(){throw new TypeError("Invalid attempt to destructure non-iterable instance")}()}function _(e){return function(e){if(Array.isArray(e)){for(var t=0,n=new Array(e.length);t<e.length;t++)n[t]=e[t];return n}}(e)||function(e){if(Symbol.iterator in Object(e)||"[object Arguments]"===Object.prototype.toString.call(e))return Array.from(e)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance")}()}function s(e){return"function"==typeof e||Array.isArray(e)||"[object Object]"===Object.prototype.toString.call(e)}function o(e,t){if(e===t)return e;for(var n in t)if(Object.prototype.hasOwnProperty.call(t,n)){var r=t[n],i=e[n];void 0!==i&&void 0===r||(s(i)&&s(r)?e[n]=o(i,r):e[n]="object"==typeof(a=r)&&null!==a?o(Array.isArray(a)?[]:{},a):a)}var a;return e}function m(){return Array.prototype.slice.call(arguments).reduceRight(function(t,n){return Object.keys(Object(n)).forEach(function(e){void 0!==n[e]&&(void 0!==t[e]&&delete t[e],t[e]=n[e])}),t},{})}var p=function(e){s(e)||(e={});for(var t=1,n=arguments.length;t<n;t++){var r=arguments[t];s(r)&&o(e,r)}return e};var a=function(n,r){return n.filter(function(e,t){return-1<r.indexOf(e)&&n.indexOf(e)===t})},v=function(e,t){if(Array.isArray(e))for(var n=0;n<e.length;n++)if(t(e[n]))return e[n]};var c=function e(t){if("number"==typeof t)return t;if("string"==typeof t)return parseFloat(t);if(Array.isArray(t))return t.map(e);throw new Error("The value should be a number, a parsable string or an array of those.")};var u=function(e,t){if(null===e)return{};var n,r,i={},a=Object.keys(e);for(r=0;r<a.length;r++)n=a[r],0<=t.indexOf(n)||(i[n]=e[n]);return i};var l=function(e){return e&&0<Object.keys(e).length},d={addRefinement:function(e,t,n){if(d.isRefined(e,t,n))return e;var r=""+n,i=e[t]?e[t].concat(r):[r],a={};return a[t]=i,m({},a,e)},removeRefinement:function(e,n,t){if(void 0===t)return d.clearRefinement(e,function(e,t){return n===t});var r=""+t;return d.clearRefinement(e,function(e,t){return n===t&&r===e})},toggleRefinement:function(e,t,n){if(void 0===n)throw new Error("toggleRefinement should be used with a value");return d.isRefined(e,t,n)?d.removeRefinement(e,t,n):d.addRefinement(e,t,n)},clearRefinement:function(i,a,s){if(void 0===a)return l(i)?{}:i;if("string"==typeof a)return u(i,[a]);if("function"==typeof a){var o=!1,e=Object.keys(i).reduce(function(e,t){var n=i[t]||[],r=n.filter(function(e){return!a(e,t,s)});return r.length!==n.length&&(o=!0),e[t]=r,e},{});return o?e:i}},isRefined:function(e,t,n){var r=!!e[t]&&0<e[t].length;if(void 0===n||!r)return r;var i=""+n;return-1!==e[t].indexOf(i)}},g=d;function y(e,n){return Array.isArray(e)&&Array.isArray(n)?e.length===n.length&&e.every(function(e,t){return y(n[t],e)}):e===n}function b(e){var r=e?b._parseNumbers(e):{};this.facets=r.facets||[],this.disjunctiveFacets=r.disjunctiveFacets||[],this.hierarchicalFacets=r.hierarchicalFacets||[],this.facetsRefinements=r.facetsRefinements||{},this.facetsExcludes=r.facetsExcludes||{},this.disjunctiveFacetsRefinements=r.disjunctiveFacetsRefinements||{},this.numericRefinements=r.numericRefinements||{},this.tagRefinements=r.tagRefinements||[],this.hierarchicalFacetsRefinements=r.hierarchicalFacetsRefinements||{};var i=this;Object.keys(r).forEach(function(e){var t=-1!==b.PARAMETERS.indexOf(e),n=void 0!==r[e];!t&&n&&(i[e]=r[e])})}b.PARAMETERS=Object.keys(new b),b._parseNumbers=function(i){if(i instanceof b)return i;var r={};if(["aroundPrecision","aroundRadius","getRankingInfo","minWordSizefor2Typos","minWordSizefor1Typo","page","maxValuesPerFacet","distinct","minimumAroundRadius","hitsPerPage","minProximity"].forEach(function(e){var t=i[e];if("string"==typeof t){var n=parseFloat(t);r[e]=isNaN(n)?t:n}}),Array.isArray(i.insideBoundingBox)&&(r.insideBoundingBox=i.insideBoundingBox.map(function(e){return Array.isArray(e)?e.map(function(e){return parseFloat(e)}):e})),i.numericRefinements){var a={};Object.keys(i.numericRefinements).forEach(function(n){var r=i.numericRefinements[n]||{};a[n]={},Object.keys(r).forEach(function(e){var t=r[e].map(function(e){return Array.isArray(e)?e.map(function(e){return"string"==typeof e?parseFloat(e):e}):"string"==typeof e?parseFloat(e):e});a[n][e]=t})}),r.numericRefinements=a}return p({},i,r)},b.make=function(e){var n=new b(e);return(e.hierarchicalFacets||[]).forEach(function(e){if(e.rootPath){var t=n.getHierarchicalRefinement(e.name);0<t.length&&0!==t[0].indexOf(e.rootPath)&&(n=n.clearRefinements(e.name)),0===(t=n.getHierarchicalRefinement(e.name)).length&&(n=n.toggleHierarchicalFacetRefinement(e.name,e.rootPath))}}),n},b.validate=function(e,t){var n=t||{};return e.tagFilters&&n.tagRefinements&&0<n.tagRefinements.length?new Error("[Tags] Cannot switch from the managed tag API to the advanced API. It is probably an error, if it is really what you want, you should first clear the tags with clearTags method."):0<e.tagRefinements.length&&n.tagFilters?new Error("[Tags] Cannot switch from the advanced tag API to the managed API. It is probably an error, if it is not, you should first clear the tags with clearTags method."):e.numericFilters&&n.numericRefinements&&l(n.numericRefinements)?new Error("[Numeric filters] Can't switch from the advanced to the managed API. It is probably an error, if this is really what you want, you have to first clear the numeric filters."):l(e.numericRefinements)&&n.numericFilters?new Error("[Numeric filters] Can't switch from the managed API to the advanced. It is probably an error, if this is really what you want, you have to first clear the numeric filters."):null},b.prototype={constructor:b,clearRefinements:function(e){var t={numericRefinements:this._clearNumericRefinements(e),facetsRefinements:g.clearRefinement(this.facetsRefinements,e,"conjunctiveFacet"),facetsExcludes:g.clearRefinement(this.facetsExcludes,e,"exclude"),disjunctiveFacetsRefinements:g.clearRefinement(this.disjunctiveFacetsRefinements,e,"disjunctiveFacet"),hierarchicalFacetsRefinements:g.clearRefinement(this.hierarchicalFacetsRefinements,e,"hierarchicalFacet")};return t.numericRefinements===this.numericRefinements&&t.facetsRefinements===this.facetsRefinements&&t.facetsExcludes===this.facetsExcludes&&t.disjunctiveFacetsRefinements===this.disjunctiveFacetsRefinements&&t.hierarchicalFacetsRefinements===this.hierarchicalFacetsRefinements?this:this.setQueryParameters(t)},clearTags:function(){return void 0===this.tagFilters&&0===this.tagRefinements.length?this:this.setQueryParameters({tagFilters:void 0,tagRefinements:[]})},setIndex:function(e){return e===this.index?this:this.setQueryParameters({index:e})},setQuery:function(e){return e===this.query?this:this.setQueryParameters({query:e})},setPage:function(e){return e===this.page?this:this.setQueryParameters({page:e})},setFacets:function(e){return this.setQueryParameters({facets:e})},setDisjunctiveFacets:function(e){return this.setQueryParameters({disjunctiveFacets:e})},setHitsPerPage:function(e){return this.hitsPerPage===e?this:this.setQueryParameters({hitsPerPage:e})},setTypoTolerance:function(e){return this.typoTolerance===e?this:this.setQueryParameters({typoTolerance:e})},addNumericRefinement:function(e,t,n){var r=c(n);if(this.isNumericRefined(e,t,r))return this;var i=p({},this.numericRefinements);return i[e]=p({},i[e]),i[e][t]?(i[e][t]=i[e][t].slice(),i[e][t].push(r)):i[e][t]=[r],this.setQueryParameters({numericRefinements:i})},getConjunctiveRefinements:function(e){return this.isConjunctiveFacet(e)&&this.facetsRefinements[e]||[]},getDisjunctiveRefinements:function(e){return this.isDisjunctiveFacet(e)&&this.disjunctiveFacetsRefinements[e]||[]},getHierarchicalRefinement:function(e){return this.hierarchicalFacetsRefinements[e]||[]},getExcludeRefinements:function(e){return this.isConjunctiveFacet(e)&&this.facetsExcludes[e]||[]},removeNumericRefinement:function(n,r,i){return void 0!==i?this.isNumericRefined(n,r,i)?this.setQueryParameters({numericRefinements:this._clearNumericRefinements(function(e,t){return t===n&&e.op===r&&y(e.val,c(i))})}):this:void 0!==r?this.isNumericRefined(n,r)?this.setQueryParameters({numericRefinements:this._clearNumericRefinements(function(e,t){return t===n&&e.op===r})}):this:this.isNumericRefined(n)?this.setQueryParameters({numericRefinements:this._clearNumericRefinements(function(e,t){return t===n})}):this},getNumericRefinements:function(e){return this.numericRefinements[e]||{}},getNumericRefinement:function(e,t){return this.numericRefinements[e]&&this.numericRefinements[e][t]},_clearNumericRefinements:function(s){if(void 0===s)return l(this.numericRefinements)?{}:this.numericRefinements;if("string"==typeof s)return l(this.numericRefinements[s])?u(this.numericRefinements,[s]):this.numericRefinements;if("function"==typeof s){var o=!1,t=this.numericRefinements,e=Object.keys(t).reduce(function(e,r){var i=t[r],a={};return i=i||{},Object.keys(i).forEach(function(t){var e=i[t]||[],n=[];e.forEach(function(e){s({val:e,op:t},r,"numeric")||n.push(e)}),n.length!==e.length&&(o=!0),a[t]=n}),e[r]=a,e},{});return o?e:this.numericRefinements}},addFacet:function(e){return this.isConjunctiveFacet(e)?this:this.setQueryParameters({facets:this.facets.concat([e])})},addDisjunctiveFacet:function(e){return this.isDisjunctiveFacet(e)?this:this.setQueryParameters({disjunctiveFacets:this.disjunctiveFacets.concat([e])})},addHierarchicalFacet:function(e){if(this.isHierarchicalFacet(e.name))throw new Error("Cannot declare two hierarchical facets with the same name: `"+e.name+"`");return this.setQueryParameters({hierarchicalFacets:this.hierarchicalFacets.concat([e])})},addFacetRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return g.isRefined(this.facetsRefinements,e,t)?this:this.setQueryParameters({facetsRefinements:g.addRefinement(this.facetsRefinements,e,t)})},addExcludeRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return g.isRefined(this.facetsExcludes,e,t)?this:this.setQueryParameters({facetsExcludes:g.addRefinement(this.facetsExcludes,e,t)})},addDisjunctiveFacetRefinement:function(e,t){if(!this.isDisjunctiveFacet(e))throw new Error(e+" is not defined in the disjunctiveFacets attribute of the helper configuration");return g.isRefined(this.disjunctiveFacetsRefinements,e,t)?this:this.setQueryParameters({disjunctiveFacetsRefinements:g.addRefinement(this.disjunctiveFacetsRefinements,e,t)})},addTagRefinement:function(e){if(this.isTagRefined(e))return this;var t={tagRefinements:this.tagRefinements.concat(e)};return this.setQueryParameters(t)},removeFacet:function(t){return this.isConjunctiveFacet(t)?this.clearRefinements(t).setQueryParameters({facets:this.facets.filter(function(e){return e!==t})}):this},removeDisjunctiveFacet:function(t){return this.isDisjunctiveFacet(t)?this.clearRefinements(t).setQueryParameters({disjunctiveFacets:this.disjunctiveFacets.filter(function(e){return e!==t})}):this},removeHierarchicalFacet:function(t){return this.isHierarchicalFacet(t)?this.clearRefinements(t).setQueryParameters({hierarchicalFacets:this.hierarchicalFacets.filter(function(e){return e.name!==t})}):this},removeFacetRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return g.isRefined(this.facetsRefinements,e,t)?this.setQueryParameters({facetsRefinements:g.removeRefinement(this.facetsRefinements,e,t)}):this},removeExcludeRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return g.isRefined(this.facetsExcludes,e,t)?this.setQueryParameters({facetsExcludes:g.removeRefinement(this.facetsExcludes,e,t)}):this},removeDisjunctiveFacetRefinement:function(e,t){if(!this.isDisjunctiveFacet(e))throw new Error(e+" is not defined in the disjunctiveFacets attribute of the helper configuration");return g.isRefined(this.disjunctiveFacetsRefinements,e,t)?this.setQueryParameters({disjunctiveFacetsRefinements:g.removeRefinement(this.disjunctiveFacetsRefinements,e,t)}):this},removeTagRefinement:function(t){if(!this.isTagRefined(t))return this;var e={tagRefinements:this.tagRefinements.filter(function(e){return e!==t})};return this.setQueryParameters(e)},toggleRefinement:function(e,t){return this.toggleFacetRefinement(e,t)},toggleFacetRefinement:function(e,t){if(this.isHierarchicalFacet(e))return this.toggleHierarchicalFacetRefinement(e,t);if(this.isConjunctiveFacet(e))return this.toggleConjunctiveFacetRefinement(e,t);if(this.isDisjunctiveFacet(e))return this.toggleDisjunctiveFacetRefinement(e,t);throw new Error("Cannot refine the undeclared facet "+e+"; it should be added to the helper options facets, disjunctiveFacets or hierarchicalFacets")},toggleConjunctiveFacetRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return this.setQueryParameters({facetsRefinements:g.toggleRefinement(this.facetsRefinements,e,t)})},toggleExcludeFacetRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return this.setQueryParameters({facetsExcludes:g.toggleRefinement(this.facetsExcludes,e,t)})},toggleDisjunctiveFacetRefinement:function(e,t){if(!this.isDisjunctiveFacet(e))throw new Error(e+" is not defined in the disjunctiveFacets attribute of the helper configuration");return this.setQueryParameters({disjunctiveFacetsRefinements:g.toggleRefinement(this.disjunctiveFacetsRefinements,e,t)})},toggleHierarchicalFacetRefinement:function(e,t){if(!this.isHierarchicalFacet(e))throw new Error(e+" is not defined in the hierarchicalFacets attribute of the helper configuration");var n=this._getHierarchicalFacetSeparator(this.getHierarchicalFacetByName(e)),r={};return void 0!==this.hierarchicalFacetsRefinements[e]&&0<this.hierarchicalFacetsRefinements[e].length&&(this.hierarchicalFacetsRefinements[e][0]===t||0===this.hierarchicalFacetsRefinements[e][0].indexOf(t+n))?-1===t.indexOf(n)?r[e]=[]:r[e]=[t.slice(0,t.lastIndexOf(n))]:r[e]=[t],this.setQueryParameters({hierarchicalFacetsRefinements:m({},r,this.hierarchicalFacetsRefinements)})},addHierarchicalFacetRefinement:function(e,t){if(this.isHierarchicalFacetRefined(e))throw new Error(e+" is already refined.");if(!this.isHierarchicalFacet(e))throw new Error(e+" is not defined in the hierarchicalFacets attribute of the helper configuration.");var n={};return n[e]=[t],this.setQueryParameters({hierarchicalFacetsRefinements:m({},n,this.hierarchicalFacetsRefinements)})},removeHierarchicalFacetRefinement:function(e){if(!this.isHierarchicalFacetRefined(e))return this;var t={};return t[e]=[],this.setQueryParameters({hierarchicalFacetsRefinements:m({},t,this.hierarchicalFacetsRefinements)})},toggleTagRefinement:function(e){return this.isTagRefined(e)?this.removeTagRefinement(e):this.addTagRefinement(e)},isDisjunctiveFacet:function(e){return-1<this.disjunctiveFacets.indexOf(e)},isHierarchicalFacet:function(e){return void 0!==this.getHierarchicalFacetByName(e)},isConjunctiveFacet:function(e){return-1<this.facets.indexOf(e)},isFacetRefined:function(e,t){return!!this.isConjunctiveFacet(e)&&g.isRefined(this.facetsRefinements,e,t)},isExcludeRefined:function(e,t){return!!this.isConjunctiveFacet(e)&&g.isRefined(this.facetsExcludes,e,t)},isDisjunctiveFacetRefined:function(e,t){return!!this.isDisjunctiveFacet(e)&&g.isRefined(this.disjunctiveFacetsRefinements,e,t)},isHierarchicalFacetRefined:function(e,t){if(!this.isHierarchicalFacet(e))return!1;var n=this.getHierarchicalRefinement(e);return t?-1!==n.indexOf(t):0<n.length},isNumericRefined:function(e,t,n){if(void 0===n&&void 0===t)return!!this.numericRefinements[e];var r=this.numericRefinements[e]&&void 0!==this.numericRefinements[e][t];if(void 0===n||!r)return r;var i=c(n),a=void 0!==function(e,t){return v(e,function(e){return y(e,t)})}(this.numericRefinements[e][t],i);return r&&a},isTagRefined:function(e){return-1!==this.tagRefinements.indexOf(e)},getRefinedDisjunctiveFacets:function(){var t=this,e=a(Object.keys(this.numericRefinements).filter(function(e){return 0<Object.keys(t.numericRefinements[e]).length}),this.disjunctiveFacets);return Object.keys(this.disjunctiveFacetsRefinements).filter(function(e){return 0<t.disjunctiveFacetsRefinements[e].length}).concat(e).concat(this.getRefinedHierarchicalFacets())},getRefinedHierarchicalFacets:function(){var t=this;return a(this.hierarchicalFacets.map(function(e){return e.name}),Object.keys(this.hierarchicalFacetsRefinements).filter(function(e){return 0<t.hierarchicalFacetsRefinements[e].length}))},getUnrefinedDisjunctiveFacets:function(){var t=this.getRefinedDisjunctiveFacets();return this.disjunctiveFacets.filter(function(e){return-1===t.indexOf(e)})},managedParameters:["index","facets","disjunctiveFacets","facetsRefinements","facetsExcludes","disjunctiveFacetsRefinements","numericRefinements","tagRefinements","hierarchicalFacets","hierarchicalFacetsRefinements"],getQueryParams:function(){var n=this.managedParameters,r={},i=this;return Object.keys(this).forEach(function(e){var t=i[e];-1===n.indexOf(e)&&void 0!==t&&(r[e]=t)}),r},setQueryParameter:function(e,t){if(this[e]===t)return this;var n={};return n[e]=t,this.setQueryParameters(n)},setQueryParameters:function(e){if(!e)return this;var t=b.validate(this,e);if(t)throw t;var n=this,i=b._parseNumbers(e),r=Object.keys(this).reduce(function(e,t){return e[t]=n[t],e},{}),a=Object.keys(i).reduce(function(e,t){var n=void 0!==e[t],r=void 0!==i[t];return n&&!r?u(e,[t]):(r&&(e[t]=i[t]),e)},r);return new this.constructor(a)},resetPage:function(){return void 0===this.page?this:this.setPage(0)},_getHierarchicalFacetSortBy:function(e){return e.sortBy||["isRefined:desc","name:asc"]},_getHierarchicalFacetSeparator:function(e){return e.separator||" > "},_getHierarchicalRootPath:function(e){return e.rootPath||null},_getHierarchicalShowParentLevel:function(e){return"boolean"!=typeof e.showParentLevel||e.showParentLevel},getHierarchicalFacetByName:function(t){return v(this.hierarchicalFacets,function(e){return e.name===t})},getHierarchicalFacetBreadcrumb:function(e){if(!this.isHierarchicalFacet(e))return[];var t=this.getHierarchicalRefinement(e)[0];if(!t)return[];var n=this._getHierarchicalFacetSeparator(this.getHierarchicalFacetByName(e));return t.split(n).map(function(e){return e.trim()})},toString:function(){return JSON.stringify(this,null,2)}};var R=b;function w(e,t){if(e!==t){var n=void 0!==e,r=null===e,i=void 0!==t,a=null===t;if(!a&&t<e||r&&i||!n)return 1;if(!r&&e<t||a&&n||!i)return-1}return 0}function t(e){return Array.isArray(e)?e.filter(Boolean):[]}function S(e,t){if(!Array.isArray(e))return-1;for(var n=0;n<e.length;n++)if(t(e[n]))return n;return-1}function P(e,t){var i=(t||[]).map(function(e){return e.split(":")});return e.reduce(function(e,t){var n=t.split(":"),r=v(i,function(e){return e[0]===n[0]});return 1<n.length||!r?(e[0].push(n[0]),e[1].push(n[1])):(e[0].push(r[0]),e[1].push(r[1])),e},[[],[]])}var N=function(e,n,i){if(!Array.isArray(e))return[];Array.isArray(i)||(i=[]);var t=e.map(function(t,e){return{criteria:n.map(function(e){return t[e]}),index:e,value:t}});return t.sort(function(e,t){for(var n=-1;++n<e.criteria.length;){var r=w(e.criteria[n],t.criteria[n]);if(r)return n>=i.length?r:"desc"===i[n]?-r:r}return e.index-t.index}),t.map(function(e){return e.value})},x=function(h){return function(e,t){var n=h.hierarchicalFacets[t],r=h.hierarchicalFacetsRefinements[n.name]&&h.hierarchicalFacetsRefinements[n.name][0]||"",i=h._getHierarchicalFacetSeparator(n),a=h._getHierarchicalRootPath(n),s=h._getHierarchicalShowParentLevel(n),o=P(h._getHierarchicalFacetSortBy(n)),c=e.every(function(e){return e.exhaustive}),u=function(o,c,u,l,h){return function(e,n,t){var r=e;if(0<t){var i=0;for(r=e;i<t;){var a=r&&Array.isArray(r.data)?r.data:[];r=v(a,function(e){return e.isRefined}),i++}}if(r){var s=Object.keys(n.data).map(function(e){return[e,n.data[e]]}).filter(function(e){return function(e,t,n,r,i,a){return(!i||0===e.indexOf(i)&&i!==e)&&(!i&&-1===e.indexOf(r)||i&&e.split(r).length-i.split(r).length==1||-1===e.indexOf(r)&&-1===n.indexOf(r)||0===n.indexOf(e)||0===e.indexOf(t+r)&&(a||0===e.indexOf(n)))}(e[0],r.path||u,h,c,u,l)});r.data=N(s.map(function(e){var t=e[0];return function(e,t,n,r,i){var a=t.split(n);return{name:a[a.length-1].trim(),path:t,count:e,isRefined:r===t||0===r.indexOf(t+n),exhaustive:i,data:null}}(e[1],t,c,h,n.exhaustive)}),o[0],o[1])}return e}}(o,i,a,s,r),l=e;return a&&(l=e.slice(a.split(i).length)),l.reduce(u,{name:h.hierarchicalFacets[t].name,count:null,isRefined:!0,path:null,exhaustive:c,data:null})}};function F(e){var n={};return e.forEach(function(e,t){n[e]=t}),n}function I(e,t,n){t&&t[n]&&(e.stats=t[n])}function C(l,n){var c=n[0];this._rawResults=n;var h=this;Object.keys(c).forEach(function(e){h[e]=c[e]}),this.processingTimeMS=n.reduce(function(e,t){return void 0===t.processingTimeMS?e:e+t.processingTimeMS},0),this.disjunctiveFacets=[],this.hierarchicalFacets=l.hierarchicalFacets.map(function(){return[]}),this.facets=[];var e=l.getRefinedDisjunctiveFacets(),u=F(l.facets),f=F(l.disjunctiveFacets),r=1,d=c.facets||{};Object.keys(d).forEach(function(e){var t=d[e],n=function(e,t){return v(e,function(e){return-1<(e.attributes||[]).indexOf(t)})}(l.hierarchicalFacets,e);if(n){var r=n.attributes.indexOf(e),i=S(l.hierarchicalFacets,function(e){return e.name===n.name});h.hierarchicalFacets[i][r]={attribute:e,data:t,exhaustive:c.exhaustiveFacetsCount}}else{var a,s=-1!==l.disjunctiveFacets.indexOf(e),o=-1!==l.facets.indexOf(e);s&&(a=f[e],h.disjunctiveFacets[a]={name:e,data:t,exhaustive:c.exhaustiveFacetsCount},I(h.disjunctiveFacets[a],c.facets_stats,e)),o&&(a=u[e],h.facets[a]={name:e,data:t,exhaustive:c.exhaustiveFacetsCount},I(h.facets[a],c.facets_stats,e))}}),this.hierarchicalFacets=t(this.hierarchicalFacets),e.forEach(function(e){var a=n[r],s=a&&a.facets?a.facets:{},o=l.getHierarchicalFacetByName(e);Object.keys(s).forEach(function(t){var n,e=s[t];if(o){n=S(l.hierarchicalFacets,function(e){return e.name===o.name});var r=S(h.hierarchicalFacets[n],function(e){return e.attribute===t});if(-1===r)return;h.hierarchicalFacets[n][r].data=p({},h.hierarchicalFacets[n][r].data,e)}else{n=f[t];var i=c.facets&&c.facets[t]||{};h.disjunctiveFacets[n]={name:t,data:m({},e,i),exhaustive:a.exhaustiveFacetsCount},I(h.disjunctiveFacets[n],a.facets_stats,t),l.disjunctiveFacetsRefinements[t]&&l.disjunctiveFacetsRefinements[t].forEach(function(e){!h.disjunctiveFacets[n].data[e]&&-1<l.disjunctiveFacetsRefinements[t].indexOf(e)&&(h.disjunctiveFacets[n].data[e]=0)})}}),r++}),l.getRefinedHierarchicalFacets().forEach(function(e){var s=l.getHierarchicalFacetByName(e),o=l._getHierarchicalFacetSeparator(s),c=l.getHierarchicalRefinement(e);if(!(0===c.length||c[0].split(o).length<2)){var t=n[r],u=t&&t.facets?t.facets:{};Object.keys(u).forEach(function(t){var e=u[t],n=S(l.hierarchicalFacets,function(e){return e.name===s.name}),r=S(h.hierarchicalFacets[n],function(e){return e.attribute===t});if(-1!==r){var i={};if(0<c.length){var a=c[0].split(o)[0];i[a]=h.hierarchicalFacets[n][r].data[a]}h.hierarchicalFacets[n][r].data=m(i,e,h.hierarchicalFacets[n][r].data)}}),r++}}),Object.keys(l.facetsExcludes).forEach(function(t){var e=l.facetsExcludes[t],n=u[t];h.facets[n]={name:t,data:c.facets[t],exhaustive:c.exhaustiveFacetsCount},e.forEach(function(e){h.facets[n]=h.facets[n]||{name:t},h.facets[n].data=h.facets[n].data||{},h.facets[n].data[e]=0})}),this.hierarchicalFacets=this.hierarchicalFacets.map(x(l)),this.facets=t(this.facets),this.disjunctiveFacets=t(this.disjunctiveFacets),this._state=l}function T(t,e){if(!e.data||0===e.data.length)return e;var n=e.data.map(function(e){return T(t,e)}),r=t(n);return p({},e,{data:r})}function E(e,t){var n=v(e,function(e){return e.name===t});return n&&n.stats}function q(e,t,n,r,i){var a=v(i,function(e){return e.name===n}),s=a&&a.data&&a.data[r]?a.data[r]:0,o=a&&a.exhaustive||!1;return{type:t,attributeName:n,name:r,count:s,exhaustive:o}}C.prototype.getFacetByName=function(t){function e(e){return e.name===t}return v(this.facets,e)||v(this.disjunctiveFacets,e)||v(this.hierarchicalFacets,e)},C.DEFAULT_SORT=["isRefined:desc","count:desc","name:asc"],C.prototype.getFacetValues=function(e,t){var n=function(t,n){function e(e){return e.name===n}if(t._state.isConjunctiveFacet(n)){var r=v(t.facets,e);return r?Object.keys(r.data).map(function(e){return{name:e,count:r.data[e],isRefined:t._state.isFacetRefined(n,e),isExcluded:t._state.isExcludeRefined(n,e)}}):[]}if(t._state.isDisjunctiveFacet(n)){var i=v(t.disjunctiveFacets,e);return i?Object.keys(i.data).map(function(e){return{name:e,count:i.data[e],isRefined:t._state.isDisjunctiveFacetRefined(n,e)}}):[]}if(t._state.isHierarchicalFacet(n))return v(t.hierarchicalFacets,e)}(this,e);if(n){var r=m({},t,{sortBy:C.DEFAULT_SORT});if(Array.isArray(r.sortBy)){var i=P(r.sortBy,C.DEFAULT_SORT);return Array.isArray(n)?N(n,i[0],i[1]):T(function(e){return N(e,i[0],i[1])},n)}if("function"==typeof r.sortBy)return Array.isArray(n)?n.sort(r.sortBy):T(function(e){return function(e,t){return t.sort(e)}(r.sortBy,e)},n);throw new Error("options.sortBy is optional but if defined it must be either an array of string (predicates) or a sorting function")}},C.prototype.getFacetStats=function(e){return this._state.isConjunctiveFacet(e)?E(this.facets,e):this._state.isDisjunctiveFacet(e)?E(this.disjunctiveFacets,e):void 0},C.prototype.getRefinements=function(){var r=this._state,n=this,i=[];return Object.keys(r.facetsRefinements).forEach(function(t){r.facetsRefinements[t].forEach(function(e){i.push(q(r,"facet",t,e,n.facets))})}),Object.keys(r.facetsExcludes).forEach(function(t){r.facetsExcludes[t].forEach(function(e){i.push(q(r,"exclude",t,e,n.facets))})}),Object.keys(r.disjunctiveFacetsRefinements).forEach(function(t){r.disjunctiveFacetsRefinements[t].forEach(function(e){i.push(q(r,"disjunctive",t,e,n.disjunctiveFacets))})}),Object.keys(r.hierarchicalFacetsRefinements).forEach(function(t){r.hierarchicalFacetsRefinements[t].forEach(function(e){i.push(function(e,t,n,r){var i=e.getHierarchicalFacetByName(t),a=e._getHierarchicalFacetSeparator(i),s=n.split(a),o=v(r,function(e){return e.name===t}),c=s.reduce(function(e,t){var n=e&&v(e.data,function(e){return e.name===t});return void 0!==n?n:e},o),u=c&&c.count||0,l=c&&c.exhaustive||!1,h=c&&c.path||"";return{type:"hierarchical",attributeName:t,name:h,count:u,exhaustive:l}}(r,t,e,n.hierarchicalFacets))})}),Object.keys(r.numericRefinements).forEach(function(n){var e=r.numericRefinements[n];Object.keys(e).forEach(function(t){e[t].forEach(function(e){i.push({type:"numeric",attributeName:n,name:e,numericValue:e,operator:t})})})}),r.tagRefinements.forEach(function(e){i.push({type:"tag",attributeName:"_tags",name:e})}),i};var U=C;function V(){this._events=this._events||{},this._maxListeners=this._maxListeners||void 0}var e=V;function W(e){return"function"==typeof e}function $(e){return"object"==typeof e&&null!==e}function z(e){return void 0===e}(V.EventEmitter=V).prototype._events=void 0,V.prototype._maxListeners=void 0,V.defaultMaxListeners=10,V.prototype.setMaxListeners=function(e){if(!function(e){return"number"==typeof e}(e)||e<0||isNaN(e))throw TypeError("n must be a positive number");return this._maxListeners=e,this},V.prototype.emit=function(e){var t,n,r,i,a,s;if(this._events||(this._events={}),"error"===e&&(!this._events.error||$(this._events.error)&&!this._events.error.length)){if((t=arguments[1])instanceof Error)throw t;var o=new Error('Uncaught, unspecified "error" event. ('+t+")");throw o.context=t,o}if(z(n=this._events[e]))return!1;if(W(n))switch(arguments.length){case 1:n.call(this);break;case 2:n.call(this,arguments[1]);break;case 3:n.call(this,arguments[1],arguments[2]);break;default:i=Array.prototype.slice.call(arguments,1),n.apply(this,i)}else if($(n))for(i=Array.prototype.slice.call(arguments,1),r=(s=n.slice()).length,a=0;a<r;a++)s[a].apply(this,i);return!0},V.prototype.on=V.prototype.addListener=function(e,t){var n;if(!W(t))throw TypeError("listener must be a function");return this._events||(this._events={}),this._events.newListener&&this.emit("newListener",e,W(t.listener)?t.listener:t),this._events[e]?$(this._events[e])?this._events[e].push(t):this._events[e]=[this._events[e],t]:this._events[e]=t,$(this._events[e])&&!this._events[e].warned&&(n=z(this._maxListeners)?V.defaultMaxListeners:this._maxListeners)&&0<n&&this._events[e].length>n&&(this._events[e].warned=!0,console.error("(node) warning: possible EventEmitter memory leak detected. %d listeners added. Use emitter.setMaxListeners() to increase limit.",this._events[e].length),"function"==typeof console.trace&&console.trace()),this},V.prototype.once=function(e,t){if(!W(t))throw TypeError("listener must be a function");var n=!1;function r(){this.removeListener(e,r),n||(n=!0,t.apply(this,arguments))}return r.listener=t,this.on(e,r),this},V.prototype.removeListener=function(e,t){var n,r,i,a;if(!W(t))throw TypeError("listener must be a function");if(!this._events||!this._events[e])return this;if(i=(n=this._events[e]).length,r=-1,n===t||W(n.listener)&&n.listener===t)delete this._events[e],this._events.removeListener&&this.emit("removeListener",e,t);else if($(n)){for(a=i;0<a--;)if(n[a]===t||n[a].listener&&n[a].listener===t){r=a;break}if(r<0)return this;1===n.length?(n.length=0,delete this._events[e]):n.splice(r,1),this._events.removeListener&&this.emit("removeListener",e,t)}return this},V.prototype.removeAllListeners=function(e){var t,n;if(!this._events)return this;if(!this._events.removeListener)return 0===arguments.length?this._events={}:this._events[e]&&delete this._events[e],this;if(0===arguments.length){for(t in this._events)"removeListener"!==t&&this.removeAllListeners(t);return this.removeAllListeners("removeListener"),this._events={},this}if(W(n=this._events[e]))this.removeListener(e,n);else if(n)for(;n.length;)this.removeListener(e,n[n.length-1]);return delete this._events[e],this},V.prototype.listeners=function(e){return this._events&&this._events[e]?W(this._events[e])?[this._events[e]]:this._events[e].slice():[]},V.prototype.listenerCount=function(e){if(this._events){var t=this._events[e];if(W(t))return 1;if(t)return t.length}return 0},V.listenerCount=function(e,t){return e.listenerCount(t)};var K=function(e,t){e.prototype=Object.create(t.prototype,{constructor:{value:e,enumerable:!1,writable:!0,configurable:!0}})};function J(e,t){this.main=e,this.fn=t,this.lastResults=null}K(J,e.EventEmitter),J.prototype.detach=function(){this.removeAllListeners(),this.main.detachDerivedHelper(this)},J.prototype.getModifiedState=function(e){return this.fn(e)};var Y=J,G={_getQueries:function(i,a){var s=[];return s.push({indexName:i,params:G._getHitsSearchParams(a)}),a.getRefinedDisjunctiveFacets().forEach(function(e){s.push({indexName:i,params:G._getDisjunctiveFacetSearchParams(a,e)})}),a.getRefinedHierarchicalFacets().forEach(function(e){var t=a.getHierarchicalFacetByName(e),n=a.getHierarchicalRefinement(e),r=a._getHierarchicalFacetSeparator(t);0<n.length&&1<n[0].split(r).length&&s.push({indexName:i,params:G._getDisjunctiveFacetSearchParams(a,e,!0)})}),s},_getHitsSearchParams:function(e){var t=e.facets.concat(e.disjunctiveFacets).concat(G._getHitsHierarchicalFacetsAttributes(e)),n=G._getFacetFilters(e),r=G._getNumericFilters(e),i={facets:t,tagFilters:G._getTagFilters(e)};return 0<n.length&&(i.facetFilters=n),0<r.length&&(i.numericFilters=r),p({},e.getQueryParams(),i)},_getDisjunctiveFacetSearchParams:function(e,t,n){var r=G._getFacetFilters(e,t,n),i=G._getNumericFilters(e,t),a={hitsPerPage:1,page:0,attributesToRetrieve:[],attributesToHighlight:[],attributesToSnippet:[],tagFilters:G._getTagFilters(e),analytics:!1,clickAnalytics:!1},s=e.getHierarchicalFacetByName(t);return a.facets=s?G._getDisjunctiveHierarchicalFacetAttribute(e,s,n):t,0<i.length&&(a.numericFilters=i),0<r.length&&(a.facetFilters=r),p({},e.getQueryParams(),a)},_getNumericFilters:function(e,i){if(e.numericFilters)return e.numericFilters;var a=[];return Object.keys(e.numericRefinements).forEach(function(r){var t=e.numericRefinements[r]||{};Object.keys(t).forEach(function(n){var e=t[n]||[];i!==r&&e.forEach(function(e){if(Array.isArray(e)){var t=e.map(function(e){return r+n+e});a.push(t)}else a.push(r+n+e)})})}),a},_getTagFilters:function(e){return e.tagFilters?e.tagFilters:e.tagRefinements.join(",")},_getFacetFilters:function(o,c,u){var l=[],e=o.facetsRefinements||{};Object.keys(e).forEach(function(t){(e[t]||[]).forEach(function(e){l.push(t+":"+e)})});var n=o.facetsExcludes||{};Object.keys(n).forEach(function(t){(n[t]||[]).forEach(function(e){l.push(t+":-"+e)})});var r=o.disjunctiveFacetsRefinements||{};Object.keys(r).forEach(function(t){var e=r[t]||[];if(t!==c&&e&&0!==e.length){var n=[];e.forEach(function(e){n.push(t+":"+e)}),l.push(n)}});var h=o.hierarchicalFacetsRefinements||{};return Object.keys(h).forEach(function(e){var t=(h[e]||[])[0];if(void 0!==t){var n,r,i=o.getHierarchicalFacetByName(e),a=o._getHierarchicalFacetSeparator(i),s=o._getHierarchicalRootPath(i);if(c===e){if(-1===t.indexOf(a)||!s&&!0===u||s&&s.split(a).length===t.split(a).length)return;t=s?(r=s.split(a).length-1,s):(r=t.split(a).length-2,t.slice(0,t.lastIndexOf(a))),n=i.attributes[r]}else r=t.split(a).length-1,n=i.attributes[r];n&&l.push([n+":"+t])}}),l},_getHitsHierarchicalFacetsAttributes:function(s){return s.hierarchicalFacets.reduce(function(e,t){var n=s.getHierarchicalRefinement(t.name)[0];if(!n)return e.push(t.attributes[0]),e;var r=s._getHierarchicalFacetSeparator(t),i=n.split(r).length,a=t.attributes.slice(0,i+1);return e.concat(a)},[])},_getDisjunctiveHierarchicalFacetAttribute:function(e,t,n){var r=e._getHierarchicalFacetSeparator(t);if(!0===n){var i=e._getHierarchicalRootPath(t),a=0;return i&&(a=i.split(r).length),[t.attributes[a]]}var s=(e.getHierarchicalRefinement(t.name)[0]||"").split(r).length-1;return t.attributes.slice(0,1+s)},getSearchForFacetQuery:function(e,t,n,r){var i=r.isDisjunctiveFacet(e)?r.clearRefinements(e):r,a={facetQuery:t,facetName:e};return"number"==typeof n&&(a.maxFacetHits=n),p({},G._getHitsSearchParams(i),a)}},X=G,Z="3.2.2";function ee(e,t,n){"function"==typeof e.addAlgoliaAgent&&e.addAlgoliaAgent("JS Helper (3.2.2)"),this.setClient(e);var r=n||{};r.index=t,this.state=R.make(r),this.lastResults=null,this._queryId=0,this._lastQueryIdReceived=-1,this.derivedHelpers=[],this._currentNbQueries=0}function te(e){if(e<0)throw new Error("Page requested below 0.");return this._change({state:this.state.setPage(e),isPageReset:!1}),this}function ne(){return this.state.page}K(ee,e.EventEmitter),ee.prototype.search=function(){return this._search({onlyWithDerivedHelpers:!1}),this},ee.prototype.searchOnlyWithDerivedHelpers=function(){return this._search({onlyWithDerivedHelpers:!0}),this},ee.prototype.getQuery=function(){var e=this.state;return X._getHitsSearchParams(e)},ee.prototype.searchOnce=function(e,t){var n=e?this.state.setQueryParameters(e):this.state,r=X._getQueries(n.index,n),i=this;if(this._currentNbQueries++,this.emit("searchOnce",{state:n}),!t)return this.client.search(r).then(function(e){return i._currentNbQueries--,0===i._currentNbQueries&&i.emit("searchQueueEmpty"),{content:new U(n,e.results),state:n,_originalResponse:e}},function(e){throw i._currentNbQueries--,0===i._currentNbQueries&&i.emit("searchQueueEmpty"),e});this.client.search(r).then(function(e){i._currentNbQueries--,0===i._currentNbQueries&&i.emit("searchQueueEmpty"),t(null,new U(n,e.results),n)}).catch(function(e){i._currentNbQueries--,0===i._currentNbQueries&&i.emit("searchQueueEmpty"),t(e,null,n)})},ee.prototype.searchForFacetValues=function(t,e,n,r){var i="function"==typeof this.client.searchForFacetValues;if(!i&&"function"!=typeof this.client.initIndex)throw new Error("search for facet values (searchable) was called, but this client does not have a function client.searchForFacetValues or client.initIndex(index).searchForFacetValues");var a=this.state.setQueryParameters(r||{}),s=a.isDisjunctiveFacet(t),o=X.getSearchForFacetQuery(t,e,n,a);this._currentNbQueries++;var c=this;return this.emit("searchForFacetValues",{state:a,facet:t,query:e}),(i?this.client.searchForFacetValues([{indexName:a.index,params:o}]):this.client.initIndex(a.index).searchForFacetValues(o)).then(function(e){return c._currentNbQueries--,0===c._currentNbQueries&&c.emit("searchQueueEmpty"),(e=Array.isArray(e)?e[0]:e).facetHits.forEach(function(e){e.isRefined=s?a.isDisjunctiveFacetRefined(t,e.value):a.isFacetRefined(t,e.value)}),e},function(e){throw c._currentNbQueries--,0===c._currentNbQueries&&c.emit("searchQueueEmpty"),e})},ee.prototype.setQuery=function(e){return this._change({state:this.state.resetPage().setQuery(e),isPageReset:!0}),this},ee.prototype.clearRefinements=function(e){return this._change({state:this.state.resetPage().clearRefinements(e),isPageReset:!0}),this},ee.prototype.clearTags=function(){return this._change({state:this.state.resetPage().clearTags(),isPageReset:!0}),this},ee.prototype.addDisjunctiveFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().addDisjunctiveFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.addDisjunctiveRefine=function(){return this.addDisjunctiveFacetRefinement.apply(this,arguments)},ee.prototype.addHierarchicalFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().addHierarchicalFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.addNumericRefinement=function(e,t,n){return this._change({state:this.state.resetPage().addNumericRefinement(e,t,n),isPageReset:!0}),this},ee.prototype.addFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().addFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.addRefine=function(){return this.addFacetRefinement.apply(this,arguments)},ee.prototype.addFacetExclusion=function(e,t){return this._change({state:this.state.resetPage().addExcludeRefinement(e,t),isPageReset:!0}),this},ee.prototype.addExclude=function(){return this.addFacetExclusion.apply(this,arguments)},ee.prototype.addTag=function(e){return this._change({state:this.state.resetPage().addTagRefinement(e),isPageReset:!0}),this},ee.prototype.removeNumericRefinement=function(e,t,n){return this._change({state:this.state.resetPage().removeNumericRefinement(e,t,n),isPageReset:!0}),this},ee.prototype.removeDisjunctiveFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().removeDisjunctiveFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.removeDisjunctiveRefine=function(){return this.removeDisjunctiveFacetRefinement.apply(this,arguments)},ee.prototype.removeHierarchicalFacetRefinement=function(e){return this._change({state:this.state.resetPage().removeHierarchicalFacetRefinement(e),isPageReset:!0}),this},ee.prototype.removeFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().removeFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.removeRefine=function(){return this.removeFacetRefinement.apply(this,arguments)},ee.prototype.removeFacetExclusion=function(e,t){return this._change({state:this.state.resetPage().removeExcludeRefinement(e,t),isPageReset:!0}),this},ee.prototype.removeExclude=function(){return this.removeFacetExclusion.apply(this,arguments)},ee.prototype.removeTag=function(e){return this._change({state:this.state.resetPage().removeTagRefinement(e),isPageReset:!0}),this},ee.prototype.toggleFacetExclusion=function(e,t){return this._change({state:this.state.resetPage().toggleExcludeFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.toggleExclude=function(){return this.toggleFacetExclusion.apply(this,arguments)},ee.prototype.toggleRefinement=function(e,t){return this.toggleFacetRefinement(e,t)},ee.prototype.toggleFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().toggleFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.toggleRefine=function(){return this.toggleFacetRefinement.apply(this,arguments)},ee.prototype.toggleTag=function(e){return this._change({state:this.state.resetPage().toggleTagRefinement(e),isPageReset:!0}),this},ee.prototype.nextPage=function(){var e=this.state.page||0;return this.setPage(e+1)},ee.prototype.previousPage=function(){var e=this.state.page||0;return this.setPage(e-1)},ee.prototype.setCurrentPage=te,ee.prototype.setPage=te,ee.prototype.setIndex=function(e){return this._change({state:this.state.resetPage().setIndex(e),isPageReset:!0}),this},ee.prototype.setQueryParameter=function(e,t){return this._change({state:this.state.resetPage().setQueryParameter(e,t),isPageReset:!0}),this},ee.prototype.setState=function(e){return this._change({state:R.make(e),isPageReset:!1}),this},ee.prototype.overrideStateWithoutTriggeringChangeEvent=function(e){return this.state=new R(e),this},ee.prototype.hasRefinements=function(e){return!!l(this.state.getNumericRefinements(e))||(this.state.isConjunctiveFacet(e)?this.state.isFacetRefined(e):this.state.isDisjunctiveFacet(e)?this.state.isDisjunctiveFacetRefined(e):!!this.state.isHierarchicalFacet(e)&&this.state.isHierarchicalFacetRefined(e))},ee.prototype.isExcluded=function(e,t){return this.state.isExcludeRefined(e,t)},ee.prototype.isDisjunctiveRefined=function(e,t){return this.state.isDisjunctiveFacetRefined(e,t)},ee.prototype.hasTag=function(e){return this.state.isTagRefined(e)},ee.prototype.isTagRefined=function(){return this.hasTagRefinements.apply(this,arguments)},ee.prototype.getIndex=function(){return this.state.index},ee.prototype.getCurrentPage=ne,ee.prototype.getPage=ne,ee.prototype.getTags=function(){return this.state.tagRefinements},ee.prototype.getRefinements=function(e){var n=[];if(this.state.isConjunctiveFacet(e))this.state.getConjunctiveRefinements(e).forEach(function(e){n.push({value:e,type:"conjunctive"})}),this.state.getExcludeRefinements(e).forEach(function(e){n.push({value:e,type:"exclude"})});else if(this.state.isDisjunctiveFacet(e)){this.state.getDisjunctiveRefinements(e).forEach(function(e){n.push({value:e,type:"disjunctive"})})}var r=this.state.getNumericRefinements(e);return Object.keys(r).forEach(function(e){var t=r[e];n.push({value:t,operator:e,type:"numeric"})}),n},ee.prototype.getNumericRefinement=function(e,t){return this.state.getNumericRefinement(e,t)},ee.prototype.getHierarchicalFacetBreadcrumb=function(e){return this.state.getHierarchicalFacetBreadcrumb(e)},ee.prototype._search=function(e){var r=this.state,i=[],t=[];e.onlyWithDerivedHelpers||(t=X._getQueries(r.index,r),i.push({state:r,queriesCount:t.length,helper:this}),this.emit("search",{state:r,results:this.lastResults}));var n=this.derivedHelpers.map(function(e){var t=e.getModifiedState(r),n=X._getQueries(t.index,t);return i.push({state:t,queriesCount:n.length,helper:e}),e.emit("search",{state:t,results:e.lastResults}),n}),a=Array.prototype.concat.apply(t,n),s=this._queryId++;this._currentNbQueries++;try{this.client.search(a).then(this._dispatchAlgoliaResponse.bind(this,i,s)).catch(this._dispatchAlgoliaError.bind(this,s))}catch(e){this.emit("error",{error:e})}},ee.prototype._dispatchAlgoliaResponse=function(e,t,n){if(!(t<this._lastQueryIdReceived)){this._currentNbQueries-=t-this._lastQueryIdReceived,this._lastQueryIdReceived=t,0===this._currentNbQueries&&this.emit("searchQueueEmpty");var s=n.results.slice();e.forEach(function(e){var t=e.state,n=e.queriesCount,r=e.helper,i=s.splice(0,n),a=r.lastResults=new U(t,i);r.emit("result",{results:a,state:t})})}},ee.prototype._dispatchAlgoliaError=function(e,t){e<this._lastQueryIdReceived||(this._currentNbQueries-=e-this._lastQueryIdReceived,this._lastQueryIdReceived=e,this.emit("error",{error:t}),0===this._currentNbQueries&&this.emit("searchQueueEmpty"))},ee.prototype.containsRefinement=function(e,t,n,r){return e||0!==t.length||0!==n.length||0!==r.length},ee.prototype._hasDisjunctiveRefinements=function(e){return this.state.disjunctiveRefinements[e]&&0<this.state.disjunctiveRefinements[e].length},ee.prototype._change=function(e){var t=e.state,n=e.isPageReset;t!==this.state&&(this.state=t,this.emit("change",{state:this.state,results:this.lastResults,isPageReset:n}))},ee.prototype.clearCache=function(){return this.client.clearCache&&this.client.clearCache(),this},ee.prototype.setClient=function(e){return this.client===e||("function"==typeof e.addAlgoliaAgent&&e.addAlgoliaAgent("JS Helper (3.2.2)"),this.client=e),this},ee.prototype.getClient=function(){return this.client},ee.prototype.derive=function(e){var t=new Y(this,e);return this.derivedHelpers.push(t),t},ee.prototype.detachDerivedHelper=function(e){var t=this.derivedHelpers.indexOf(e);if(-1===t)throw new Error("Derived helper already detached");this.derivedHelpers.splice(t,1)},ee.prototype.hasPendingRequests=function(){return 0<this._currentNbQueries};var re=ee;function ie(e,t,n){return new re(e,t,n)}ie.version=Z,ie.AlgoliaSearchHelper=re,ie.SearchParameters=R,ie.SearchResults=U;var ae=ie;function se(r){function e(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];null===i&&(i=oe.then(function(){i=null,a?a=!1:r.apply(void 0,t)}))}var i=null,a=!1;return e.wait=function(){if(null===i)throw new Error("The deferred function should be called before calling `wait()`");return i},e.cancel=function(){null!==i&&(a=!0)},e}var oe=Promise.resolve();function ce(e){var t="string"==typeof e,n=t?document.querySelector(e):e;if(function(e){return e instanceof HTMLElement||Boolean(e)&&0<e.nodeType}(n))return n;var r="Container must be `string` or `HTMLElement`.";throw t&&(r+=" Unable to find ".concat(e)),new Error(r)}function ue(e){return 1===e.button||e.altKey||e.ctrlKey||e.metaKey||e.shiftKey}function le(e){return e.filter(function(e,t,n){return n.indexOf(e)===t})}function he(e){var t=e.defaultTemplates,n=e.templates;return D({templatesConfig:e.templatesConfig},function(e,t){var a=0<arguments.length&&void 0!==e?e:{},s=1<arguments.length&&void 0!==t?t:{};return le([].concat(_(Object.keys(a)),_(Object.keys(s)))).reduce(function(e,t){var n=a[t],r=s[t],i=void 0!==r&&r!==n;return e.templates[t]=i?r:n,e.useCustomCompileOptions[t]=i,e},{templates:{},useCustomCompileOptions:{}})}(t,n))}function fe(e,t){return e(t={exports:{}},t.exports),t.exports}var de=fe(function(e,t){!function(R){var w=/\S/,t=/\"/g,n=/\n/g,r=/\r/g,i=/\\/g,a=/\u2028/,s=/\u2029/;function S(e){"}"===e.n.substr(e.n.length-1)&&(e.n=e.n.substring(0,e.n.length-1))}function P(e){return e.trim?e.trim():e.replace(/^\s*|\s*$/g,"")}function _(e,t,n){if(t.charAt(n)!=e.charAt(0))return!1;for(var r=1,i=e.length;r<i;r++)if(t.charAt(n+r)!=e.charAt(r))return!1;return!0}R.tags={"#":1,"^":2,"<":3,$:4,"/":5,"!":6,">":7,"=":8,_v:9,"{":10,"&":11,_t:12},R.scan=function(e,t){var n,r,i,a,s,o=e.length,c=0,u=null,l=null,h="",f=[],d=!1,m=0,p=0,v="{{",g="}}";function y(){0<h.length&&(f.push({tag:"_t",text:new String(h)}),h="")}function b(e,t){if(y(),e&&function(){for(var e=!0,t=p;t<f.length;t++)if(!(e=R.tags[f[t].tag]<R.tags._v||"_t"==f[t].tag&&null===f[t].text.match(w)))return!1;return e}())for(var n,r=p;r<f.length;r++)f[r].text&&((n=f[r+1])&&">"==n.tag&&(n.indent=f[r].text.toString()),f.splice(r,1));else t||f.push({tag:"\n"});d=!1,p=f.length}for(t&&(t=t.split(" "),v=t[0],g=t[1]),m=0;m<o;m++)0==c?_(v,e,m)?(--m,y(),c=1):"\n"==e.charAt(m)?b(d):h+=e.charAt(m):1==c?(m+=v.length-1,c="="==(u=(l=R.tags[e.charAt(m+1)])?e.charAt(m+1):"_v")?(r=m,void 0,i="="+g,a=(n=e).indexOf(i,r),s=P(n.substring(n.indexOf("=",r)+1,a)).split(" "),v=s[0],g=s[s.length-1],m=a+i.length-1,0):(l&&m++,2),d=m):_(g,e,m)?(f.push({tag:u,n:P(h),otag:v,ctag:g,i:"/"==u?d-v.length:m+g.length}),h="",m+=g.length-1,c=0,"{"==u&&("}}"==g?m++:S(f[f.length-1]))):h+=e.charAt(m);return b(d,!0),f};var u={_t:!0,"\n":!0,$:!0,"/":!0};function l(e,t){for(var n=0,r=t.length;n<r;n++)if(t[n].o==e.n)return e.tag="#",!0}function h(e,t,n){for(var r=0,i=n.length;r<i;r++)if(n[r].c==e&&n[r].o==t)return!0}function o(e){var t=[];for(var n in e.partials)t.push('"'+f(n)+'":{name:"'+f(e.partials[n].name)+'", '+o(e.partials[n])+"}");return"partials: {"+t.join(",")+"}, subs: "+function(e){var t=[];for(var n in e)t.push('"'+f(n)+'": function(c,p,t,i) {'+e[n]+"}");return"{ "+t.join(",")+" }"}(e.subs)}R.stringify=function(e,t,n){return"{code: function (c,p,i) { "+R.wrapMain(e.code)+" },"+o(e)+"}"};var c=0;function f(e){return e.replace(i,"\\\\").replace(t,'\\"').replace(n,"\\n").replace(r,"\\r").replace(a,"\\u2028").replace(s,"\\u2029")}function d(e){return~e.indexOf(".")?"d":"f"}function m(e,t){var n="<"+(t.prefix||"")+e.n+c++;return t.partials[n]={name:e.n,partials:{}},t.code+='t.b(t.rp("'+f(n)+'",c,p,"'+(e.indent||"")+'"));',n}function e(e,t){t.code+="t.b(t.t(t."+d(e.n)+'("'+f(e.n)+'",c,p,0)));'}function p(e){return"t.b("+e+");"}R.generate=function(e,t,n){c=0;var r={code:"",subs:{},partials:{}};return R.walk(e,r),n.asString?this.stringify(r,t,n):this.makeTemplate(r,t,n)},R.wrapMain=function(e){return'var t=this;t.b(i=i||"");'+e+"return t.fl();"},R.template=R.Template,R.makeTemplate=function(e,t,n){var r=this.makePartials(e);return r.code=new Function("c","p","i",this.wrapMain(e.code)),new this.template(r,t,this,n)},R.makePartials=function(e){var t,n={subs:{},partials:e.partials,name:e.name};for(t in n.partials)n.partials[t]=this.makePartials(n.partials[t]);for(t in e.subs)n.subs[t]=new Function("c","p","t","i",e.subs[t]);return n},R.codegen={"#":function(e,t){t.code+="if(t.s(t."+d(e.n)+'("'+f(e.n)+'",c,p,1),c,p,0,'+e.i+","+e.end+',"'+e.otag+" "+e.ctag+'")){t.rs(c,p,function(c,p,t){',R.walk(e.nodes,t),t.code+="});c.pop();}"},"^":function(e,t){t.code+="if(!t.s(t."+d(e.n)+'("'+f(e.n)+'",c,p,1),c,p,1,0,0,"")){',R.walk(e.nodes,t),t.code+="};"},">":m,"<":function(e,t){var n={partials:{},code:"",subs:{},inPartial:!0};R.walk(e.nodes,n);var r=t.partials[m(e,t)];r.subs=n.subs,r.partials=n.partials},$:function(e,t){var n={subs:{},code:"",partials:t.partials,prefix:e.n};R.walk(e.nodes,n),t.subs[e.n]=n.code,t.inPartial||(t.code+='t.sub("'+f(e.n)+'",c,p,i);')},"\n":function(e,t){t.code+=p('"\\n"'+(e.last?"":" + i"))},_v:function(e,t){t.code+="t.b(t.v(t."+d(e.n)+'("'+f(e.n)+'",c,p,0)));'},_t:function(e,t){t.code+=p('"'+f(e.text)+'"')},"{":e,"&":e},R.walk=function(e,t){for(var n,r=0,i=e.length;r<i;r++)(n=R.codegen[e[r].tag])&&n(e[r],t);return t},R.parse=function(e,t,n){return function e(t,n,r,i){var a,s=[],o=null,c=null;for(a=r[r.length-1];0<t.length;){if(c=t.shift(),a&&"<"==a.tag&&!(c.tag in u))throw new Error("Illegal content in < super tag.");if(R.tags[c.tag]<=R.tags.$||l(c,i))r.push(c),c.nodes=e(t,c.tag,r,i);else{if("/"==c.tag){if(0===r.length)throw new Error("Closing tag without opener: /"+c.n);if(o=r.pop(),c.n!=o.n&&!h(c.n,o.n,i))throw new Error("Nesting error: "+o.n+" vs. "+c.n);return o.end=c.i,s}"\n"==c.tag&&(c.last=0==t.length||"\n"==t[0].tag)}s.push(c)}if(0<r.length)throw new Error("missing closing tag: "+r.pop().n);return s}(e,0,[],(n=n||{}).sectionTags||[])},R.cache={},R.cacheKey=function(e,t){return[e,!!t.asString,!!t.disableLambda,t.delimiters,!!t.modelGet].join("||")},R.compile=function(e,t){t=t||{};var n=R.cacheKey(e,t),r=this.cache[n];if(r){var i=r.partials;for(var a in i)delete i[a].instance;return r}return r=this.generate(this.parse(this.scan(e,t.delimiters),e,t),e,t),this.cache[n]=r}}(t)}),me=fe(function(e,t){!function(e){function l(e,t,n){var r;return t&&"object"==typeof t&&(void 0!==t[e]?r=t[e]:n&&t.get&&"function"==typeof t.get&&(r=t.get(e))),r}e.Template=function(e,t,n,r){e=e||{},this.r=e.code||this.r,this.c=n,this.options=r||{},this.text=t||"",this.partials=e.partials||{},this.subs=e.subs||{},this.buf=""},e.Template.prototype={r:function(e,t,n){return""},v:function(e){return e=o(e),s.test(e)?e.replace(t,"&amp;").replace(n,"&lt;").replace(r,"&gt;").replace(i,"&#39;").replace(a,"&quot;"):e},t:o,render:function(e,t,n){return this.ri([e],t||{},n)},ri:function(e,t,n){return this.r(e,t,n)},ep:function(e,t){var n=this.partials[e],r=t[n.name];if(n.instance&&n.base==r)return n.instance;if("string"==typeof r){if(!this.c)throw new Error("No compiler available.");r=this.c.compile(r,this.options)}if(!r)return null;if(this.partials[e].base=r,n.subs){for(key in t.stackText||(t.stackText={}),n.subs)t.stackText[key]||(t.stackText[key]=void 0!==this.activeSub&&t.stackText[this.activeSub]?t.stackText[this.activeSub]:this.text);r=function(e,t,n,r,i,a){function s(){}function o(){}var c;o.prototype=(s.prototype=e).subs;var u=new s;for(c in u.subs=new o,u.subsText={},u.buf="",r=r||{},u.stackSubs=r,u.subsText=a,t)r[c]||(r[c]=t[c]);for(c in r)u.subs[c]=r[c];for(c in i=i||{},u.stackPartials=i,n)i[c]||(i[c]=n[c]);for(c in i)u.partials[c]=i[c];return u}(r,n.subs,n.partials,this.stackSubs,this.stackPartials,t.stackText)}return this.partials[e].instance=r},rp:function(e,t,n,r){var i=this.ep(e,n);return i?i.ri(t,n,r):""},rs:function(e,t,n){var r=e[e.length-1];if(h(r))for(var i=0;i<r.length;i++)e.push(r[i]),n(e,t,this),e.pop();else n(e,t,this)},s:function(e,t,n,r,i,a,s){var o;return(!h(e)||0!==e.length)&&("function"==typeof e&&(e=this.ms(e,t,n,r,i,a,s)),o=!!e,!r&&o&&t&&t.push("object"==typeof e?e:t[t.length-1]),o)},d:function(e,t,n,r){var i,a=e.split("."),s=this.f(a[0],t,n,r),o=this.options.modelGet,c=null;if("."===e&&h(t[t.length-2]))s=t[t.length-1];else for(var u=1;u<a.length;u++)s=void 0!==(i=l(a[u],s,o))?(c=s,i):"";return!(r&&!s)&&(r||"function"!=typeof s||(t.push(c),s=this.mv(s,t,n),t.pop()),s)},f:function(e,t,n,r){for(var i=!1,a=!1,s=this.options.modelGet,o=t.length-1;0<=o;o--)if(void 0!==(i=l(e,t[o],s))){a=!0;break}return a?(r||"function"!=typeof i||(i=this.mv(i,t,n)),i):!r&&""},ls:function(e,t,n,r,i){var a=this.options.delimiters;return this.options.delimiters=i,this.b(this.ct(o(e.call(t,r)),t,n)),this.options.delimiters=a,!1},ct:function(e,t,n){if(this.options.disableLambda)throw new Error("Lambda features disabled.");return this.c.compile(e,this.options).render(t,n)},b:function(e){this.buf+=e},fl:function(){var e=this.buf;return this.buf="",e},ms:function(e,t,n,r,i,a,s){var o,c=t[t.length-1],u=e.call(c);return"function"==typeof u?!!r||(o=this.activeSub&&this.subsText&&this.subsText[this.activeSub]?this.subsText[this.activeSub]:this.text,this.ls(u,c,n,o.substring(i,a),s)):u},mv:function(e,t,n){var r=t[t.length-1],i=e.call(r);return"function"==typeof i?this.ct(o(i.call(r)),r,n):i},sub:function(e,t,n,r){var i=this.subs[e];i&&(this.activeSub=e,i(t,n,this,r),this.activeSub=!1)}};var t=/&/g,n=/</g,r=/>/g,i=/\'/g,a=/\"/g,s=/[&<>\"\']/;function o(e){return String(null==e?"":e)}var h=Array.isArray||function(e){return"[object Array]"===Object.prototype.toString.call(e)}}(t)});de.Template=me.Template,de.template=de.Template;var pe=de;function ve(e){var t=e.templates,n=e.templateKey,r=e.compileOptions,i=e.helpers,a=e.data,s=e.bindEvent,o=t[n],c=h(o),u="function"===c;if(!("string"===c)&&!u)throw new Error("Template must be 'string' or 'function', was '".concat(c,"' (key: ").concat(n,")"));if(u)return o(a,s);var l=function(e,t,n){var r=0<arguments.length&&void 0!==e?e:{},i=1<arguments.length?t:void 0,a=2<arguments.length?n:void 0;return Object.keys(r).reduce(function(e,n){return D({},e,L({},n,function(){var t=this;return function(e){return r[n].call(a,e,function(e){return pe.compile(e,i).render(t)})}}))},{})}(i,r,a);return pe.compile(o,r).render(D({},a,{helpers:l})).replace(/[ \n\r\t\f\xA0]+/g,function(e){return e.replace(/(^|\xA0+)[^\xA0]+/g,"$1 ")}).trim()}function ge(e,t,n){return Array.prototype.find?e.find(t,n):e.filter(t,n)[0]}function ye(e){return String(e).replace(/^\\-/,"-")}function be(i,e,a,s,t){var o,n={type:e,attribute:a,name:s},c=ge(4<arguments.length&&void 0!==t?t:[],function(e){return e.name===a});"hierarchical"===e?function(){for(var e=i.getHierarchicalFacetByName(a),n=s.split(e.separator),t=function(t){c=c&&c.data&&ge(Object.keys(c.data).map(function(t){return function(e){return t[e]}}(c.data)),function(e){return e.name===n[t]})},r=0;void 0!==c&&r<n.length;++r)t(r);o=c&&c.count}():o=c&&c.data&&c.data[n.name];var r=c&&c.exhaustive;return void 0!==o&&(n.count=o),void 0!==r&&(n.exhaustive=r),n}function Re(n,r,e){var t=2<arguments.length&&void 0!==e&&e,a=[],i=r.facetsRefinements,s=void 0===i?{}:i,o=r.facetsExcludes,c=void 0===o?{}:o,u=r.disjunctiveFacetsRefinements,l=void 0===u?{}:u,h=r.hierarchicalFacetsRefinements,f=void 0===h?{}:h,d=r.numericRefinements,m=void 0===d?{}:d,p=r.tagRefinements,v=void 0===p?[]:p;return Object.keys(s).forEach(function(t){s[t].forEach(function(e){a.push(be(r,"facet",t,e,n.facets))})}),Object.keys(c).forEach(function(t){c[t].forEach(function(e){a.push({type:"exclude",attribute:t,name:e,exclude:!0})})}),Object.keys(l).forEach(function(t){l[t].forEach(function(e){a.push(be(r,"disjunctive",t,ye(e),n.disjunctiveFacets))})}),Object.keys(f).forEach(function(t){f[t].forEach(function(e){a.push(be(r,"hierarchical",t,e,n.hierarchicalFacets))})}),Object.keys(m).forEach(function(r){var i=m[r];Object.keys(i).forEach(function(e){var t=e,n=i[t];(Array.isArray(n)?n:[n]).forEach(function(e){a.push({type:"numeric",attribute:r,name:"".concat(e),numericValue:e,operator:t})})})}),v.forEach(function(e){a.push({type:"tag",attribute:"_tags",name:e})}),t&&r.query&&r.query.trim()&&a.push({attribute:"query",type:"query",name:r.query,query:r.query}),a}function we(e){var t=e.helper,n=e.attributesToClear,r=void 0===n?[]:n,i=t.state.setPage(0);return i=r.reduce(function(e,t){return i.isNumericRefined(t)?e.removeNumericRefinement(t):i.isHierarchicalFacet(t)?e.removeHierarchicalFacetRefinement(t):i.isDisjunctiveFacet(t)?e.removeDisjunctiveFacetRefinement(t):i.isConjunctiveFacet(t)?e.removeFacetRefinement(t):e},i),-1!==r.indexOf("query")&&(i=i.setQuery("")),i}function Se(e){return"number"==typeof e&&e<0&&(e=String(e).replace(/^-/,"\\-")),e}function Pe(e,t){if(void 0===e||"function"!=typeof e)throw new Error("The render function is not valid (received type ".concat(function(e){return Object.prototype.toString.call(e).slice(8,-1)}(e),").\n\n").concat(t))}function _e(){}function Ne(e,t){return t.split(".").reduce(function(e,t){return e&&e[t]},e)}function xe(e){return"number"==typeof e&&isFinite(e)}function Fe(e){if(!function(e){return"object"===h(e)&&null!==e}(e)||"[object Object]"!==function(e){return null===e?void 0===e?"[object Undefined]":"[object Null]":Object.prototype.toString.call(e)}(e))return!1;if(null===Object.getPrototypeOf(e))return!0;for(var t=e;null!==Object.getPrototypeOf(t);)t=Object.getPrototypeOf(t);return Object.getPrototypeOf(e)===t}function Ie(e){var t=e.start,n=void 0===t?0:t,r=e.end,i=e.step,a=void 0===i?1:i,s=0===a?1:a,o=Math.round((r-n)/s);return _(Array(o)).map(function(e,t){return n+t*s})}function Ce(e){return e!==Object(e)}function Te(e,t){if(e===t)return!0;if(Ce(e)||Ce(t)||"function"==typeof e||"function"==typeof t)return e===t;if(Object.keys(e).length!==Object.keys(t).length)return!1;for(var n=0,r=Object.keys(e);n<r.length;n++){var i=r[n];if(!(i in t))return!1;if(!Te(e[i],t[i]))return!1}return!0}var Ee={"&":"&amp;","<":"&lt;",">":"&gt;",'"':"&quot;","'":"&#39;"},ke=/[&<>"']/g,Me=RegExp(ke.source);function Le(e,t){return e.setQueryParameters({hierarchicalFacets:t.hierarchicalFacets.reduce(function(e,t){var n=function(e,t){if(!Array.isArray(e))return-1;for(var n=0;n<e.length;n++)if(t(e[n]))return n;return-1}(e,function(e){return e.name===t.name});if(-1===n)return e.concat(t);var r=e.slice();return r.splice(n,1,t),r},e.hierarchicalFacets)})}function je(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];return t.reduce(function(e,t){var n=function(e,t){return e.setQueryParameters({hierarchicalFacetsRefinements:D({},e.hierarchicalFacetsRefinements,{},t.hierarchicalFacetsRefinements)})}(e,t);return function(e,t){t.facets,t.disjunctiveFacets,t.facetsRefinements,t.facetsExcludes,t.disjunctiveFacetsRefinements,t.numericRefinements,t.tagRefinements,t.hierarchicalFacets,t.hierarchicalFacetsRefinements,t.ruleContexts;var n=A(t,["facets","disjunctiveFacets","facetsRefinements","facetsExcludes","disjunctiveFacetsRefinements","numericRefinements","tagRefinements","hierarchicalFacets","hierarchicalFacetsRefinements","ruleContexts"]);return e.setQueryParameters(n)}(function(e,t){return t.facets.reduce(function(e,t){return e.addFacet(t)},e)}(function(e,t){var n=le([].concat(e.ruleContexts).concat(t.ruleContexts).filter(Boolean));return 0<n.length?e.setQueryParameters({ruleContexts:n}):e}(function(e,t){return t.disjunctiveFacets.reduce(function(e,t){return e.addDisjunctiveFacet(t)},e)}(function(e,t){return e.setQueryParameters({facetsRefinements:D({},e.facetsRefinements,{},t.facetsRefinements)})}(function(e,t){return e.setQueryParameters({facetsExcludes:D({},e.facetsExcludes,{},t.facetsExcludes)})}(function(e,t){return e.setQueryParameters({disjunctiveFacetsRefinements:D({},e.disjunctiveFacetsRefinements,{},t.disjunctiveFacetsRefinements)})}(function(e,t){return e.setQueryParameters({numericRefinements:D({},e.numericRefinements,{},t.numericRefinements)})}(function(e,t){return t.tagRefinements.reduce(function(e,t){return e.addTagRefinement(t)},e)}(Le(n,t),t),t),t),t),t),t),t),t),t)})}function Oe(e){return Array.isArray(e)?e:[e]}function Ae(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r=t.map(function(e){return function(e){var t=e.name,n=e.connector;return["https://www.algolia.com/doc/api-reference/widgets/",t,"/js/",void 0!==n&&n?"#connector":""].join("")}(e)}).join(", ");return function(e){return[e,"See documentation: ".concat(r)].filter(Boolean).join("\n\n")}}var He=/^(-?\d+(?:\.\d+)?),\s*(-?\d+(?:\.\d+)?)$/;function De(e){return Array.isArray(e)?function(e){var t=Q(e,1)[0],n=Q(t=void 0===t?[void 0,void 0,void 0,void 0]:t,4),r=n[0],i=n[1],a=n[2],s=n[3];if(!(r&&i&&a&&s))throw new Error('Invalid value for "insideBoundingBox" parameter: ['.concat(e,"]"));return{northEast:{lat:r,lng:i},southWest:{lat:a,lng:s}}}(e):function(e){var t=Q(e.split(",").map(parseFloat),4),n=t[0],r=t[1],i=t[2],a=t[3];if(!(n&&r&&i&&a))throw new Error('Invalid value for "insideBoundingBox" parameter: "'.concat(e,'"'));return{northEast:{lat:n,lng:r},southWest:{lat:i,lng:a}}}(e)}function Be(e,n,r){return e.map(function(e,t){return D({},e,{__position:r*n+t+1})})}function Qe(e,t){return t?e.map(function(e){return D({},e,{__queryID:t})}):e}function qe(e){var o=e.instantSearchInstance,c=e.helper,u=e.attribute,l=e.widgetType;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r=t[0],i=t[1],a=t[2],s=void 0===a?"Filter Applied":a;1===t.length&&"object"===h(t[0])?o.sendEventToInsights(t[0]):"click"!==r||2!==t.length&&3!==t.length||function(e,t,n){return e.state.isHierarchicalFacet(t)?e.state.isHierarchicalFacetRefined(t,n):e.state.isConjunctiveFacet(t)?e.state.isFacetRefined(t,n):e.state.isDisjunctiveFacetRefined(t,n)}(c,u,i)||o.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:l,eventType:r,payload:{eventName:s,index:c.getIndex(),filters:["".concat(u,":").concat(JSON.stringify(i))]}})}}function Ue(e){var t=e.index,n=e.widgetType,r=(e.methodName,e.args);if(1===r.length&&"object"===h(r[0]))return r[0];var i=r[0],a=r[1],s=r[2];if(!a)return null;if(("click"===i||"conversion"===i)&&!s)return null;var o=Array.isArray(a)?a:[a];if(0===o.length)return null;var c=o[0].__queryID,u=o.map(function(e){return e.objectID}),l=o.map(function(e){return e.__position});return"view"===i?{insightsMethod:"viewedObjectIDs",widgetType:n,eventType:i,payload:{eventName:s||"Hits Viewed",index:t,objectIDs:u}}:"click"===i?{insightsMethod:"clickedObjectIDsAfterSearch",widgetType:n,eventType:i,payload:{eventName:s,index:t,queryID:c,objectIDs:u,positions:l}}:"conversion"===i?{insightsMethod:"convertedObjectIDsAfterSearch",widgetType:n,eventType:i,payload:{eventName:s,index:t,queryID:c,objectIDs:u}}:null}function Ve(e){var i=e.instantSearchInstance,a=e.index,s=e.widgetType;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r=Ue({widgetType:s,index:a,methodName:"sendEvent",args:t});r&&i.sendEventToInsights(r)}}function We(e){var i=e.index,a=e.widgetType;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r=Ue({widgetType:a,index:i,methodName:"bindEvent",args:t});return r?"data-insights-event=".concat(btoa(JSON.stringify(r))):""}}function $e(e,n){if(!e)return null;var r=e.numericRefinements[n],i=[];return Object.keys(r).filter(function(e){return Array.isArray(r[e])&&0<r[e].length}).forEach(function(t){r[t].forEach(function(e){i.push("".concat(n).concat(t).concat(e))})}),i}var ze=Ae({name:"index-widget"});function Ke(e){return"ais.index"===e.$$type}function Je(e,t){var n=t.state,r=t.isPageReset,i=t._uiState;n!==e.state&&(e.state=n,e.emit("change",{state:e.state,results:e.lastResults,isPageReset:r,_uiState:i}))}function Ye(e,n,t){var r=2<arguments.length&&void 0!==t?t:{};return e.filter(function(e){return!Ke(e)}).reduce(function(e,t){return t.getWidgetState?t.getWidgetState(e,n):e},r)}function Ge(e,t){var n=t.initialSearchParameters,r=A(t,["initialSearchParameters"]);return e.filter(function(e){return!Ke(e)}).reduce(function(e,t){return t.getWidgetSearchParameters?t.getWidgetSearchParameters(e,r):e},n)}function Xe(e){var t=e.getParent();return function n(e){return e.filter(Ke).reduce(function(e,t){return e.concat.apply(e,[{indexId:t.getIndexId(),results:t.getResults(),helper:t.getHelper()}].concat(_(n(t.getWidgets()))))},[])}(t?t.getWidgets():[e])}function Ze(e){if(void 0===e||void 0===e.indexName)throw new Error(ze("The `indexName` option is required."));function o(e){return f._createURL(L({},u,Ye(l,{searchParameters:e,helper:m})))}var c=e.indexName,t=e.indexId,u=void 0===t?c:t,l=[],h={},f=null,d=null,m=null,p=null;return{$$type:"ais.index",getIndexName:function(){return c},getIndexId:function(){return u},getHelper:function(){return m},getResults:function(){return p&&p.lastResults},getParent:function(){return d},getWidgets:function(){return l},addWidgets:function(e){var t=this;if(!Array.isArray(e))throw new Error(ze("The `addWidgets` method expects an array of widgets."));if(e.some(function(e){return"function"!=typeof e.init&&"function"!=typeof e.render}))throw new Error(ze("The widget definition expects a `render` and/or an `init` method."));return l=l.concat(e),f&&Boolean(e.length)&&(Je(m,{state:Ge(l,{uiState:h,initialSearchParameters:m.state}),_uiState:h}),e.forEach(function(e){f&&e.init&&e.init({helper:m,parent:t,uiState:f._initialUiState,instantSearchInstance:f,state:m.state,templatesConfig:f.templatesConfig,createURL:o})}),f.scheduleSearch()),this},removeWidgets:function(t){if(!Array.isArray(t))throw new Error(ze("The `removeWidgets` method expects an array of widgets."));if(t.some(function(e){return"function"!=typeof e.dispose}))throw new Error(ze("The widget definition expects a `dispose` method."));if(l=l.filter(function(e){return-1===t.indexOf(e)}),f&&Boolean(t.length)){var e=t.reduce(function(e,t){return t.dispose({helper:m,state:e})||e},m.state);h=Ye(l,{searchParameters:e,helper:m}),m.setState(Ge(l,{uiState:h,initialSearchParameters:e})),l.length&&f.scheduleSearch()}return this},init:function(e){var t=this,r=e.instantSearchInstance,n=e.parent,i=e.uiState;f=r,d=n,h=i[u]||{};var a=r.mainHelper,s=Ge(l,{uiState:h,initialSearchParameters:new ae.SearchParameters({index:c})});(m=ae({},s.index,s)).search=function(){return r.onStateChange?(r.onStateChange({uiState:r.mainIndex.getWidgetState({}),setUiState:r.setUiState.bind(r)}),a):a.search()},m.searchWithoutTriggeringOnStateChange=function(){return a.search()},m.searchForFacetValues=function(e,t,n,r){var i=m.state.setQueryParameters(r);return a.searchForFacetValues(e,t,n,i)},p=a.derive(function(){return je.apply(void 0,_(function(e){for(var t=e.getParent(),n=[e.getHelper().state];null!==t;)n=[t.getHelper().state].concat(n),t=t.getParent();return n}(t)))}),m.on("change",function(e){e.isPageReset&&!function n(e){var t=e.filter(Ke);0!==t.length&&t.forEach(function(e){var t=e.getHelper();Je(t,{state:t.state.resetPage(),isPageReset:!0}),n(e.getWidgets())})}(l)}),p.on("search",function(){r.scheduleStalledRender()}),p.on("result",function(e){var t=e.results;r.scheduleRender(),m.lastResults=t}),l.forEach(function(e){e.init&&e.init({uiState:i,helper:m,parent:t,instantSearchInstance:r,state:m.state,templatesConfig:r.templatesConfig,createURL:o})}),m.on("change",function(e){var t=e.state,n=e._uiState;h=Ye(l,{searchParameters:t,helper:m},n||{}),r.onStateChange||r.onInternalStateChange()})},render:function(e){var t=this,n=e.instantSearchInstance;l.forEach(function(e){e.render&&p.lastResults&&e.render({helper:m,instantSearchInstance:n,results:p.lastResults,scopedResults:Xe(t),state:p.lastResults._state,templatesConfig:n.templatesConfig,createURL:o,searchMetadata:{isSearchStalled:n._isSearchStalled}})})},dispose:function(){l.forEach(function(e){e.dispose&&e.dispose({helper:m,state:m.state})}),d=f=null,m.removeAllListeners(),m=null,p.detach(),p=null},getWidgetState:function(e){return l.filter(Ke).reduce(function(e,t){return t.getWidgetState(e)},D({},e,L({},this.getIndexId(),h)))},getWidgetSearchParameters:function(e,t){var n=t.uiState;return Ge(l,{uiState:n,initialSearchParameters:e})},refreshUiState:function(){h=Ye(l,{searchParameters:this.getHelper().state,helper:this.getHelper()})}}}var et={highlightPreTag:"__ais-highlight__",highlightPostTag:"__/ais-highlight__"},tt={highlightPreTag:"<mark>",highlightPostTag:"</mark>"};function nt(e){return function(e){return e&&Me.test(e)?e.replace(ke,function(e){return Ee[e]}):e}(e).replace(new RegExp(et.highlightPreTag,"g"),tt.highlightPreTag).replace(new RegExp(et.highlightPostTag,"g"),tt.highlightPostTag)}function rt(n){return Fe(n)&&"string"!=typeof n.value?Object.keys(n).reduce(function(e,t){return D({},e,L({},t,rt(n[t])))},{}):Array.isArray(n)?n.map(rt):D({},n,{value:nt(n.value)})}function it(e){return void 0===e.__escaped&&((e=e.map(function(e){var t=f({},e);return t._highlightResult&&(t._highlightResult=rt(t._highlightResult)),t._snippetResult&&(t._snippetResult=rt(t._snippetResult)),t})).__escaped=!0),e}function at(a){return function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.descendantName,n=e.modifierName,r=t?"-".concat(t):"",i=n?"--".concat(n):"";return"".concat("ais","-").concat(a).concat(r).concat(i)}}var st=at("Highlight");function ot(e){var t=e.attribute,n=e.highlightedTagName,r=void 0===n?"mark":n,i=e.hit,a=e.cssClasses,s=void 0===a?{}:a,o=Ne(i,"_highlightResult.".concat(t,".value"))||"",c=st({descendantName:"highlighted"})+(s.highlighted?" ".concat(s.highlighted):"");return o.replace(new RegExp(tt.highlightPreTag,"g"),"<".concat(r,' class="').concat(c,'">')).replace(new RegExp(tt.highlightPostTag,"g"),"</".concat(r,">"))}var ct=at("Snippet");function ut(e){var t=e.attribute,n=e.highlightedTagName,r=void 0===n?"mark":n,i=e.hit,a=e.cssClasses,s=void 0===a?{}:a,o=Ne(i,"_snippetResult.".concat(t,".value"))||"",c=ct({descendantName:"highlighted"})+(s.highlighted?" ".concat(s.highlighted):"");return o.replace(new RegExp(tt.highlightPreTag,"g"),"<".concat(r,' class="').concat(c,'">')).replace(new RegExp(tt.highlightPostTag,"g"),"</".concat(r,">"))}function lt(e,t){return function(e){var t,n=e.method,r=e.payload;if("object"!==h(r))throw new Error("The insights helper expects the payload to be an object.");try{t=btoa(JSON.stringify(r))}catch(e){throw new Error("Could not JSON serialize the payload object.")}return'data-insights-method="'.concat(n,'" data-insights-payload="').concat(t,'"')}({method:e,payload:t})}function ht(){return function(e){for(var t="".concat(e,"="),n=document.cookie.split(";"),r=0;r<n.length;r++){for(var i=n[r];" "===i.charAt(0);)i=i.substring(1);if(0===i.indexOf(t))return i.substring(t.length,i.length)}}("_ALGOLIA")}function ft(e){e.configure;return A(e,["configure"])}function dt(){return{stateToRoute:function(n){return Object.keys(n).reduce(function(e,t){return D({},e,L({},t,ft(n[t])))},{})},routeToState:function(e){var n=0<arguments.length&&void 0!==e?e:{};return Object.keys(n).reduce(function(e,t){return D({},e,L({},t,ft(n[t])))},{})}}}function mt(e,t){for(var n=t&&t.plainObjects?Object.create(null):{},r=0;r<e.length;++r)void 0!==e[r]&&(n[r]=e[r]);return n}function pt(e,t){kt.apply(e,Et(t)?t:[t])}function vt(e,t,n,r,i,a,s,o,c,u,l,h,f){var d=e;if("function"==typeof s?d=s(t,d):d instanceof Date?d=u(d):"comma"===n&&Et(d)&&(d=d.join(",")),null===d){if(r)return a&&!h?a(t,jt.encoder,f):t;d=""}if(function(e){return"string"==typeof e||"number"==typeof e||"boolean"==typeof e||"symbol"==typeof e||"bigint"==typeof e}(d)||_t.isBuffer(d))return a?[l(h?t:a(t,jt.encoder,f))+"="+l(a(d,jt.encoder,f))]:[l(t)+"="+l(String(d))];var m,p=[];if(void 0===d)return p;if(Et(s))m=s;else{var v=Object.keys(d);m=o?v.sort(o):v}for(var g=0;g<m.length;++g){var y=m[g];i&&null===d[y]||(Et(d)?pt(p,vt(d[y],"function"==typeof n?n(t,y):t,n,r,i,a,s,o,c,u,l,h,f)):pt(p,vt(d[y],t+(c?"."+y:"["+y+"]"),n,r,i,a,s,o,c,u,l,h,f)))}return p}function gt(e,t,n){if(e){var r=n.allowDots?e.replace(/\.([^.[]+)/g,"[$1]"):e,i=/(\[[^[\]]*])/g,a=0<n.depth&&/(\[[^[\]]*])/.exec(r),s=a?r.slice(0,a.index):r,o=[];if(s){if(!n.plainObjects&&Ot.call(Object.prototype,s)&&!n.allowPrototypes)return;o.push(s)}for(var c=0;0<n.depth&&null!==(a=i.exec(r))&&c<n.depth;){if(c+=1,!n.plainObjects&&Ot.call(Object.prototype,a[1].slice(1,-1))&&!n.allowPrototypes)return;o.push(a[1])}return a&&o.push("["+r.slice(a.index)+"]"),function(e,t,n){for(var r=t,i=e.length-1;0<=i;--i){var a,s=e[i];if("[]"===s&&n.parseArrays)a=[].concat(r);else{a=n.plainObjects?Object.create(null):{};var o="["===s.charAt(0)&&"]"===s.charAt(s.length-1)?s.slice(1,-1):s,c=parseInt(o,10);n.parseArrays||""!==o?!isNaN(c)&&s!==o&&String(c)===o&&0<=c&&n.parseArrays&&c<=n.arrayLimit?(a=[])[c]=r:a[o]=r:a={0:r}}r=a}return r}(o,t,n)}}function yt(e){var t=e.qsModule,n=e.routeState,r=e.location,i=r.protocol,a=r.hostname,s=r.port,o=void 0===s?"":s,c=r.pathname,u=r.hash,l=t.stringify(n),h=""===o?"":":".concat(o);return l?"".concat(i,"//").concat(a).concat(h).concat(c,"?").concat(l).concat(u):"".concat(i,"//").concat(a).concat(h).concat(c).concat(u)}function bt(e){var t=e.qsModule,n=e.location;return t.parse(n.search.slice(1),{arrayLimit:99})}function Rt(e){e&&(window.document.title=e)}var wt=Object.prototype.hasOwnProperty,St=Array.isArray,Pt=function(){for(var e=[],t=0;t<256;++t)e.push("%"+((t<16?"0":"")+t.toString(16)).toUpperCase());return e}(),_t={arrayToObject:mt,assign:function(e,n){return Object.keys(n).reduce(function(e,t){return e[t]=n[t],e},e)},combine:function(e,t){return[].concat(e,t)},compact:function(e){for(var t=[{obj:{o:e},prop:"o"}],n=[],r=0;r<t.length;++r)for(var i=t[r],a=i.obj[i.prop],s=Object.keys(a),o=0;o<s.length;++o){var c=s[o],u=a[c];"object"==typeof u&&null!==u&&-1===n.indexOf(u)&&(t.push({obj:a,prop:c}),n.push(u))}return function(e){for(;1<e.length;){var t=e.pop(),n=t.obj[t.prop];if(St(n)){for(var r=[],i=0;i<n.length;++i)void 0!==n[i]&&r.push(n[i]);t.obj[t.prop]=r}}}(t),e},decode:function(e,t,n){var r=e.replace(/\+/g," ");if("iso-8859-1"===n)return r.replace(/%[0-9a-f]{2}/gi,unescape);try{return decodeURIComponent(r)}catch(e){return r}},encode:function(e,t,n){if(0===e.length)return e;var r=e;if("symbol"==typeof e?r=Symbol.prototype.toString.call(e):"string"!=typeof e&&(r=String(e)),"iso-8859-1"===n)return escape(r).replace(/%u[0-9a-f]{4}/gi,function(e){return"%26%23"+parseInt(e.slice(2),16)+"%3B"});for(var i="",a=0;a<r.length;++a){var s=r.charCodeAt(a);45===s||46===s||95===s||126===s||48<=s&&s<=57||65<=s&&s<=90||97<=s&&s<=122?i+=r.charAt(a):s<128?i+=Pt[s]:s<2048?i+=Pt[192|s>>6]+Pt[128|63&s]:s<55296||57344<=s?i+=Pt[224|s>>12]+Pt[128|s>>6&63]+Pt[128|63&s]:(a+=1,s=65536+((1023&s)<<10|1023&r.charCodeAt(a)),i+=Pt[240|s>>18]+Pt[128|s>>12&63]+Pt[128|s>>6&63]+Pt[128|63&s])}return i},isBuffer:function(e){return!(!e||"object"!=typeof e)&&!!(e.constructor&&e.constructor.isBuffer&&e.constructor.isBuffer(e))},isRegExp:function(e){return"[object RegExp]"===Object.prototype.toString.call(e)},merge:function r(i,a,s){if(!a)return i;if("object"!=typeof a){if(St(i))i.push(a);else{if(!i||"object"!=typeof i)return[i,a];(s&&(s.plainObjects||s.allowPrototypes)||!wt.call(Object.prototype,a))&&(i[a]=!0)}return i}if(!i||"object"!=typeof i)return[i].concat(a);var e=i;return St(i)&&!St(a)&&(e=mt(i,s)),St(i)&&St(a)?(a.forEach(function(e,t){if(wt.call(i,t)){var n=i[t];n&&"object"==typeof n&&e&&"object"==typeof e?i[t]=r(n,e,s):i.push(e)}else i[t]=e}),i):Object.keys(a).reduce(function(e,t){var n=a[t];return wt.call(e,t)?e[t]=r(e[t],n,s):e[t]=n,e},e)}},Nt=String.prototype.replace,xt=/%20/g,Ft={RFC1738:"RFC1738",RFC3986:"RFC3986"},It=_t.assign({default:Ft.RFC3986,formatters:{RFC1738:function(e){return Nt.call(e,xt,"+")},RFC3986:function(e){return String(e)}}},Ft),Ct=Object.prototype.hasOwnProperty,Tt={brackets:function(e){return e+"[]"},comma:"comma",indices:function(e,t){return e+"["+t+"]"},repeat:function(e){return e}},Et=Array.isArray,kt=Array.prototype.push,Mt=Date.prototype.toISOString,Lt=It.default,jt={addQueryPrefix:!1,allowDots:!1,charset:"utf-8",charsetSentinel:!1,delimiter:"&",encode:!0,encoder:_t.encode,encodeValuesOnly:!1,format:Lt,formatter:It.formatters[Lt],indices:!1,serializeDate:function(e){return Mt.call(e)},skipNulls:!1,strictNullHandling:!1},Ot=Object.prototype.hasOwnProperty,At={allowDots:!1,allowPrototypes:!1,arrayLimit:20,charset:"utf-8",charsetSentinel:!1,comma:!1,decoder:_t.decode,delimiter:"&",depth:5,ignoreQueryPrefix:!1,interpretNumericEntities:!1,parameterLimit:1e3,parseArrays:!0,plainObjects:!1,strictNullHandling:!1},Ht={formats:It,parse:function(e,t){var n=function(e){if(!e)return At;if(null!==e.decoder&&void 0!==e.decoder&&"function"!=typeof e.decoder)throw new TypeError("Decoder has to be a function.");if(void 0!==e.charset&&"utf-8"!==e.charset&&"iso-8859-1"!==e.charset)throw new Error("The charset option must be either utf-8, iso-8859-1, or undefined");var t=void 0===e.charset?At.charset:e.charset;return{allowDots:void 0===e.allowDots?At.allowDots:!!e.allowDots,allowPrototypes:"boolean"==typeof e.allowPrototypes?e.allowPrototypes:At.allowPrototypes,arrayLimit:"number"==typeof e.arrayLimit?e.arrayLimit:At.arrayLimit,charset:t,charsetSentinel:"boolean"==typeof e.charsetSentinel?e.charsetSentinel:At.charsetSentinel,comma:"boolean"==typeof e.comma?e.comma:At.comma,decoder:"function"==typeof e.decoder?e.decoder:At.decoder,delimiter:"string"==typeof e.delimiter||_t.isRegExp(e.delimiter)?e.delimiter:At.delimiter,depth:"number"==typeof e.depth||!1===e.depth?+e.depth:At.depth,ignoreQueryPrefix:!0===e.ignoreQueryPrefix,interpretNumericEntities:"boolean"==typeof e.interpretNumericEntities?e.interpretNumericEntities:At.interpretNumericEntities,parameterLimit:"number"==typeof e.parameterLimit?e.parameterLimit:At.parameterLimit,parseArrays:!1!==e.parseArrays,plainObjects:"boolean"==typeof e.plainObjects?e.plainObjects:At.plainObjects,strictNullHandling:"boolean"==typeof e.strictNullHandling?e.strictNullHandling:At.strictNullHandling}}(t);if(""===e||null==e)return n.plainObjects?Object.create(null):{};for(var r="string"==typeof e?function(e,t){var n,r={},i=t.ignoreQueryPrefix?e.replace(/^\?/,""):e,a=t.parameterLimit===1/0?void 0:t.parameterLimit,s=i.split(t.delimiter,a),o=-1,c=t.charset;if(t.charsetSentinel)for(n=0;n<s.length;++n)0===s[n].indexOf("utf8=")&&("utf8=%E2%9C%93"===s[n]?c="utf-8":"utf8=%26%2310003%3B"===s[n]&&(c="iso-8859-1"),o=n,n=s.length);for(n=0;n<s.length;++n)if(n!==o){var u,l,h=s[n],f=h.indexOf("]="),d=-1===f?h.indexOf("="):f+1;(l=-1===d?(u=t.decoder(h,At.decoder,c),t.strictNullHandling?null:""):(u=t.decoder(h.slice(0,d),At.decoder,c),t.decoder(h.slice(d+1),At.decoder,c)))&&t.interpretNumericEntities&&"iso-8859-1"===c&&(l=l.replace(/&#(\d+);/g,function(e,t){return String.fromCharCode(parseInt(t,10))})),l&&t.comma&&-1<l.indexOf(",")&&(l=l.split(",")),Ot.call(r,u)?r[u]=_t.combine(r[u],l):r[u]=l}return r}(e,n):e,i=n.plainObjects?Object.create(null):{},a=Object.keys(r),s=0;s<a.length;++s){var o=a[s],c=gt(o,r[o],n);i=_t.merge(i,c,n)}return _t.compact(i)},stringify:function(e,t){var n,r=e,i=function(e){if(!e)return jt;if(null!==e.encoder&&void 0!==e.encoder&&"function"!=typeof e.encoder)throw new TypeError("Encoder has to be a function.");var t=e.charset||jt.charset;if(void 0!==e.charset&&"utf-8"!==e.charset&&"iso-8859-1"!==e.charset)throw new TypeError("The charset option must be either utf-8, iso-8859-1, or undefined");var n=It.default;if(void 0!==e.format){if(!Ct.call(It.formatters,e.format))throw new TypeError("Unknown format option provided.");n=e.format}var r=It.formatters[n],i=jt.filter;return"function"!=typeof e.filter&&!Et(e.filter)||(i=e.filter),{addQueryPrefix:"boolean"==typeof e.addQueryPrefix?e.addQueryPrefix:jt.addQueryPrefix,allowDots:void 0===e.allowDots?jt.allowDots:!!e.allowDots,charset:t,charsetSentinel:"boolean"==typeof e.charsetSentinel?e.charsetSentinel:jt.charsetSentinel,delimiter:void 0===e.delimiter?jt.delimiter:e.delimiter,encode:"boolean"==typeof e.encode?e.encode:jt.encode,encoder:"function"==typeof e.encoder?e.encoder:jt.encoder,encodeValuesOnly:"boolean"==typeof e.encodeValuesOnly?e.encodeValuesOnly:jt.encodeValuesOnly,filter:i,formatter:r,serializeDate:"function"==typeof e.serializeDate?e.serializeDate:jt.serializeDate,skipNulls:"boolean"==typeof e.skipNulls?e.skipNulls:jt.skipNulls,sort:"function"==typeof e.sort?e.sort:null,strictNullHandling:"boolean"==typeof e.strictNullHandling?e.strictNullHandling:jt.strictNullHandling}}(t);"function"==typeof i.filter?r=(0,i.filter)("",r):Et(i.filter)&&(n=i.filter);var a,s=[];if("object"!=typeof r||null===r)return"";a=t&&t.arrayFormat in Tt?t.arrayFormat:t&&"indices"in t?t.indices?"indices":"repeat":"indices";var o=Tt[a];n=n||Object.keys(r),i.sort&&n.sort(i.sort);for(var c=0;c<n.length;++c){var u=n[c];i.skipNulls&&null===r[u]||pt(s,vt(r[u],u,o,i.strictNullHandling,i.skipNulls,i.encode?i.encoder:null,i.filter,i.sort,i.allowDots,i.serializeDate,i.formatter,i.encodeValuesOnly,i.charset))}var l=s.join(i.delimiter),h=!0===i.addQueryPrefix?"?":"";return i.charsetSentinel&&("iso-8859-1"===i.charset?h+="utf8=%26%2310003%3B&":h+="utf8=%E2%9C%93&"),0<l.length?h+l:""}},Dt=function(){function u(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.windowTitle,n=e.writeDelay,r=void 0===n?400:n,i=e.createURL,a=void 0===i?yt:i,s=e.parseURL,o=void 0===s?bt:s;k(this,u),L(this,"windowTitle",void 0),L(this,"writeDelay",void 0),L(this,"_createURL",void 0),L(this,"parseURL",void 0),L(this,"writeTimer",void 0),this.windowTitle=t,this.writeTimer=void 0,this.writeDelay=r,this._createURL=a,this.parseURL=o;var c=this.windowTitle&&this.windowTitle(this.read());Rt(c)}return M(u,[{key:"read",value:function(){return this.parseURL({qsModule:Ht,location:window.location})}},{key:"write",value:function(e){var t=this,n=this.createURL(e),r=this.windowTitle&&this.windowTitle(e);this.writeTimer&&window.clearTimeout(this.writeTimer),this.writeTimer=window.setTimeout(function(){Rt(r),window.history.pushState(e,r||"",n),t.writeTimer=void 0},this.writeDelay)}},{key:"onUpdate",value:function(n){var r=this;this._onPopState=function(e){r.writeTimer&&(window.clearTimeout(r.writeTimer),r.writeTimer=void 0);var t=e.state;n(t||r.read())},window.addEventListener("popstate",this._onPopState)}},{key:"createURL",value:function(e){return this._createURL({qsModule:Ht,routeState:e,location:window.location})}},{key:"dispose",value:function(){this._onPopState&&window.removeEventListener("popstate",this._onPopState),this.writeTimer&&window.clearTimeout(this.writeTimer),this.write({})}}]),u}();function Bt(e){return new Dt(e)}function Qt(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.router,i=void 0===n?Bt():n,r=t.stateMapping,s=void 0===r?dt():r;return function(e){var a=e.instantSearchInstance;a._createURL=function(n){var e=Object.keys(n).reduce(function(e,t){return D({},e,L({},t,n[t]))},a.mainIndex.getWidgetState({})),t=s.stateToRoute(e);return i.createURL(t)},a._initialUiState=D({},a._initialUiState,{},s.routeToState(i.read()));var r=void 0;return{onStateChange:function(e){var t=e.uiState,n=s.stateToRoute(t);void 0!==r&&Te(r,n)||(i.write(n),r=n)},subscribe:function(){i.onUpdate(function(e){var i=s.routeToState(e);!function t(e,n){n(e),e.getWidgets().filter(function(e){return"ais.index"===e.$$type}).forEach(function(e){t(e,n)})}(a.mainIndex,function(e){var t=e.getWidgets(),n=i[e.getIndexId()]||{},r=t.reduce(function(e,t){return t.getWidgetSearchParameters?t.getWidgetSearchParameters(e,{uiState:n}):e},e.getHelper().state);e.getHelper().overrideStateWithoutTriggeringChangeEvent(r),a.scheduleSearch()})})},unsubscribe:function(){i.dispose()}}}}var qt=Ae({name:"instantsearch"});function Ut(){return"#"}function Vt(f,e){var i=1<arguments.length&&void 0!==e?e:_e;return Pe(f,$t()),function(a){var e=a||{},t=e.includedAttributes,s=void 0===t?[]:t,n=e.excludedAttributes,o=void 0===n?["query"]:n,r=e.transformItems,c=void 0===r?function(e){return e}:r;if(a.includedAttributes&&a.excludedAttributes)throw new Error($t("The options `includedAttributes` and `excludedAttributes` cannot be used together."));function u(){return h.refine()}function l(){return h.createURL()}var h={refine:_e,createURL:function(){return""}};return{$$type:"ais.clearRefinements",init:function(e){var t=e.instantSearchInstance;f({hasRefinements:!1,refine:u,createURL:l,instantSearchInstance:t,widgetParams:a},!0)},render:function(e){var t=e.scopedResults,n=e.createURL,r=e.instantSearchInstance,i=t.reduce(function(e,t){return e.concat(function(e){var t=e.scopedResult,n=e.includedAttributes,r=e.excludedAttributes,i=e.transformItems,a=-1!==n.indexOf("query")||-1===r.indexOf("query");return{helper:t.helper,items:i(le(Re(t.results,t.helper.state,a).map(function(e){return e.attribute}).filter(function(e){return 0===n.length||-1!==n.indexOf(e)}).filter(function(e){return"query"===e&&a||-1===r.indexOf(e)})))}}({scopedResult:t,includedAttributes:s,excludedAttributes:o,transformItems:c}))},[]);h.refine=function(){i.forEach(function(e){var t=e.helper,n=e.items;t.setState(we({helper:t,attributesToClear:n})).search()})},h.createURL=function(){return n(je.apply(void 0,_(i.map(function(e){return we({helper:e.helper,attributesToClear:e.items})}))))},f({hasRefinements:i.some(function(e){return 0<e.items.length}),refine:u,createURL:l,instantSearchInstance:r,widgetParams:a},!1)},dispose:function(){i()}}}}var Wt=function(){function b(e){var r;k(this,b),L(H(r=B(this,O(b).call(this))),"client",void 0),L(H(r),"indexName",void 0),L(H(r),"insightsClient",void 0),L(H(r),"onStateChange",null),L(H(r),"helper",void 0),L(H(r),"mainHelper",void 0),L(H(r),"mainIndex",void 0),L(H(r),"started",void 0),L(H(r),"templatesConfig",void 0),L(H(r),"_stalledSearchDelay",void 0),L(H(r),"_searchStalledTimer",void 0),L(H(r),"_isSearchStalled",void 0),L(H(r),"_initialUiState",void 0),L(H(r),"_createURL",void 0),L(H(r),"_searchFunction",void 0),L(H(r),"_mainHelperSearch",void 0),L(H(r),"middleware",[]),L(H(r),"sendEventToInsights",void 0),L(H(r),"scheduleSearch",se(function(){r.started&&r.mainHelper.search()})),L(H(r),"scheduleRender",se(function(){r.mainHelper.hasPendingRequests()||(clearTimeout(r._searchStalledTimer),r._searchStalledTimer=null,r._isSearchStalled=!1),r.mainIndex.render({instantSearchInstance:H(r)}),r.emit("render")})),L(H(r),"setUiState",function(e){if(!r.mainHelper)throw new Error(qt("The `start` method needs to be called before `setUiState`."));r.mainIndex.refreshUiState();var n="function"==typeof e?e(r.mainIndex.getWidgetState({})):e;!function e(t){t.getHelper().overrideStateWithoutTriggeringChangeEvent(t.getWidgetSearchParameters(t.getHelper().state,{uiState:n[t.getIndexId()]})),t.getWidgets().filter(Ke).forEach(e)}(r.mainIndex),r.scheduleSearch(),r.onInternalStateChange()}),L(H(r),"onInternalStateChange",function(){var t=r.mainIndex.getWidgetState({});r.middleware.forEach(function(e){e.onStateChange({uiState:t})})});var t=e.indexName,n=void 0===t?null:t,i=e.numberLocale,a=e.initialUiState,s=void 0===a?{}:a,o=e.routing,c=void 0===o?null:o,u=e.searchFunction,l=e.stalledSearchDelay,h=void 0===l?200:l,f=e.searchClient,d=void 0===f?null:f,m=e.insightsClient,p=void 0===m?null:m,v=e.onStateChange,g=void 0===v?null:v;if(null===n)throw new Error(qt("The `indexName` option is required."));if(null===d)throw new Error(qt("The `searchClient` option is required."));if("function"!=typeof d.search)throw new Error("The `searchClient` must implement a `search` method.\n\nSee: https://www.algolia.com/doc/guides/building-search-ui/going-further/backend-search/in-depth/backend-instantsearch/js/");if("function"==typeof d.addAlgoliaAgent&&d.addAlgoliaAgent("instantsearch.js (".concat("4.8.3",")")),p&&"function"!=typeof p)throw new Error(qt("The `insightsClient` option should be a function."));if(r.client=d,r.insightsClient=p,r.indexName=n,r.helper=null,r.mainHelper=null,r.mainIndex=Ze({indexName:n}),r.onStateChange=g,r.started=!1,r.templatesConfig={helpers:function(e){var n=e.numberLocale;return{formatNumber:function(e,t){return Number(t(e)).toLocaleString(n)},highlight:function(e,t){try{return t(ot(D({},JSON.parse(e),{hit:this})))}catch(e){throw new Error('\nThe highlight helper expects a JSON object of the format:\n{ "attribute": "name", "highlightedTagName": "mark" }')}},snippet:function(e,t){try{return t(ut(D({},JSON.parse(e),{hit:this})))}catch(e){throw new Error('\nThe snippet helper expects a JSON object of the format:\n{ "attribute": "name", "highlightedTagName": "mark" }')}},insights:function(e,t){try{var n=JSON.parse(e),r=n.method,i=n.payload;return t(lt(r,D({objectIDs:[this.objectID]},i)))}catch(e){throw new Error('\nThe insights helper expects a JSON object of the format:\n{ "method": "method-name", "payload": { "eventName": "name of the event" } }')}}}}({numberLocale:i}),compileOptions:{}},r._stalledSearchDelay=h,r._searchStalledTimer=null,r._isSearchStalled=!1,r._createURL=Ut,r._initialUiState=s,u&&(r._searchFunction=u),r.sendEventToInsights=_e,c){var y="boolean"==typeof c?void 0:c;r.use(Qt(y))}return r}return j(b,e),M(b,[{key:"use",value:function(){for(var n=this,e=arguments.length,t=new Array(e),r=0;r<e;r++)t[r]=arguments[r];var i=t.map(function(e){var t=e({instantSearchInstance:n});return n.middleware.push(t),t});return this.started&&i.forEach(function(e){e.subscribe()}),this}},{key:"EXPERIMENTAL_use",value:function(){return this.use.apply(this,arguments)}},{key:"addWidget",value:function(e){return this.addWidgets([e])}},{key:"addWidgets",value:function(e){if(!Array.isArray(e))throw new Error(qt("The `addWidgets` method expects an array of widgets. Please use `addWidget`."));if(e.some(function(e){return"function"!=typeof e.init&&"function"!=typeof e.render}))throw new Error(qt("The widget definition expects a `render` and/or an `init` method."));return this.mainIndex.addWidgets(e),this}},{key:"removeWidget",value:function(e){return this.removeWidgets([e])}},{key:"removeWidgets",value:function(e){if(!Array.isArray(e))throw new Error(qt("The `removeWidgets` method expects an array of widgets. Please use `removeWidget`."));if(e.some(function(e){return"function"!=typeof e.dispose}))throw new Error(qt("The widget definition expects a `dispose` method."));return this.mainIndex.removeWidgets(e),this}},{key:"start",value:function(){var r=this;if(this.started)throw new Error(qt("The `start` method has already been called once."));var t=ae(this.client,this.indexName);if(t.search=function(){return t.searchOnlyWithDerivedHelpers()},this._searchFunction){var i={search:function(){return new Promise(_e)}};this._mainHelperSearch=t.search.bind(t),t.search=function(){var n=r.mainIndex.getHelper(),e=ae(i,n.state.index,n.state);return e.once("search",function(e){var t=e.state;n.overrideStateWithoutTriggeringChangeEvent(t),r._mainHelperSearch()}),e.on("change",function(e){var t=e.state;n.setState(t)}),r._searchFunction(e),t}}t.on("error",function(e){var t=e.error;r.emit("error",{error:t})}),this.mainHelper=t,this.mainIndex.init({instantSearchInstance:this,parent:null,uiState:this._initialUiState}),this.middleware.forEach(function(e){e.subscribe()}),t.search(),this.helper=this.mainIndex.getHelper(),this.started=!0}},{key:"dispose",value:function(){this.scheduleSearch.cancel(),this.scheduleRender.cancel(),clearTimeout(this._searchStalledTimer),this.removeWidgets(this.mainIndex.getWidgets()),this.mainIndex.dispose(),this.started=!1,this.removeAllListeners(),this.mainHelper.removeAllListeners(),this.mainHelper=null,this.helper=null,this.middleware.forEach(function(e){e.unsubscribe()})}},{key:"scheduleStalledRender",value:function(){var e=this;this._searchStalledTimer||(this._searchStalledTimer=setTimeout(function(){e._isSearchStalled=!0,e.scheduleRender()},this._stalledSearchDelay))}},{key:"createURL",value:function(e){var t=0<arguments.length&&void 0!==e?e:{};if(!this.started)throw new Error(qt("The `start` method needs to be called before `createURL`."));return this._createURL(t)}},{key:"refresh",value:function(){if(!this.mainHelper)throw new Error(qt("The `start` method needs to be called before `refresh`."));this.mainHelper.clearCache().search()}}]),b}(),$t=Ae({name:"clear-refinements",connector:!0});function zt(l,e){var r=1<arguments.length&&void 0!==e?e:_e;return Pe(l,Kt()),function(s){if((s||{}).includedAttributes&&(s||{}).excludedAttributes)throw new Error(Kt("The options `includedAttributes` and `excludedAttributes` cannot be used together."));var e=s||{},o=e.includedAttributes,t=e.excludedAttributes,c=void 0===t?["query"]:t,n=e.transformItems,u=void 0===n?function(e){return e}:n;return{$$type:"ais.currentRefinements",init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance,i=u(Jt({results:{},helper:t,includedAttributes:o,excludedAttributes:c}));l({items:i,refine:function(e){return Gt(t,e)},createURL:function(e){return n(Yt(t.state,e))},instantSearchInstance:r,widgetParams:s},!0)},render:function(e){var t=e.scopedResults,n=e.helper,r=e.createURL,i=e.instantSearchInstance,a=t.reduce(function(e,t){return e.concat(u(Jt({results:t.results,helper:t.helper,includedAttributes:o,excludedAttributes:c})))},[]);l({items:a,refine:function(e){return Gt(n,e)},createURL:function(e){return r(Yt(n.state,e))},instantSearchInstance:i,widgetParams:s},!1)},dispose:function(){r()}}}}var Kt=Ae({name:"current-refinements",connector:!0});function Jt(e){var t=e.results,n=e.helper,r=e.includedAttributes,i=e.excludedAttributes,a=-1!==(r||[]).indexOf("query")||-1===(i||[]).indexOf("query"),s=r?function(e){return-1!==r.indexOf(e.attribute)}:function(e){return-1===i.indexOf(e.attribute)},o=Re(t,n.state,a).map(Xt).filter(s);return o.reduce(function(e,t){return[].concat(_(e.filter(function(e){return e.attribute!==t.attribute})),[{indexName:n.state.index,attribute:t.attribute,label:t.attribute,refinements:o.filter(function(e){return e.attribute===t.attribute}).sort(function(e,t){return"numeric"===e.type?e.value-t.value:0}),refine:function(e){return Gt(n,e)}}])},[])}function Yt(e,t){switch(t.type){case"facet":return e.removeFacetRefinement(t.attribute,String(t.value));case"disjunctive":return e.removeDisjunctiveFacetRefinement(t.attribute,String(t.value));case"hierarchical":return e.removeHierarchicalFacetRefinement(t.attribute);case"exclude":return e.removeExcludeRefinement(t.attribute,String(t.value));case"numeric":return e.removeNumericRefinement(t.attribute,t.operator,String(t.value));case"tag":return e.removeTagRefinement(String(t.value));case"query":return e.setQueryParameter("query","");default:return e}}function Gt(e,t){e.setState(Yt(e.state,t)).search()}function Xt(e){var t="numeric"===e.type?Number(e.name):e.name,n=e.operator?"".concat(function(e){switch(e){case">=":return"≥";case"<=":return"≤";default:return e}}(e.operator)," ").concat(e.name):e.name,r={attribute:e.attribute,type:e.type,value:t,label:n};return void 0!==e.operator&&(r.operator=e.operator),void 0!==e.count&&(r.count=e.count),void 0!==e.exhaustive&&(r.exhaustive=e.exhaustive),r}var Zt=Ae({name:"hierarchical-menu",connector:!0});function en(R){var w=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(R,Zt()),function(){var l=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},c=l.attributes,e=l.separator,u=void 0===e?" > ":e,t=l.rootPath,h=void 0===t?null:t,n=l.showParentLevel,f=void 0===n||n,r=l.limit,d=void 0===r?10:r,i=l.showMore,m=void 0!==i&&i,a=l.showMoreLimit,p=void 0===a?20:a,s=l.sortBy,v=void 0===s?["name:asc"]:s,o=l.transformItems,g=void 0===o?function(e){return e}:o;if(!c||!Array.isArray(c)||0===c.length)throw new Error(Zt("The `attributes` option expects an array of strings."));if(!0===m&&p<=d)throw new Error(Zt("The `showMoreLimit` option must be greater than `limit`."));var y,b=Q(c,1)[0];return{$$type:"ais.hierarchicalMenu",isShowingMore:!1,toggleShowMore:function(){},cachedToggleShowMore:function(){this.toggleShowMore()},createToggleShowMore:function(e){var t=this;return function(){t.isShowingMore=!t.isShowingMore,t.render(e)}},getLimit:function(){return this.isShowingMore?p:d},init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance;y=qe({instantSearchInstance:r,helper:t,attribute:b,widgetType:this.$$type}),this.cachedToggleShowMore=this.cachedToggleShowMore.bind(this),this._refine=function(e){y("click",e),t.toggleRefinement(b,e).search()},R({items:[],createURL:function(e){return n(t.state.toggleRefinement(b,e))},refine:this._refine,sendEvent:y,instantSearchInstance:r,widgetParams:l,isShowingMore:!1,toggleShowMore:this.cachedToggleShowMore,canToggleShowMore:!1},!0)},_prepareFacetValues:function(e,i){var a=this;return e.slice(0,this.getLimit()).map(function(e){var t=e.name,n=e.path,r=A(e,["name","path"]);return Array.isArray(r.data)&&(r.data=a._prepareFacetValues(r.data,i)),D({},r,{label:t,value:n})})},render:function(e){var t=e.results,n=e.state,r=e.createURL,i=e.instantSearchInstance,a=t.getFacetValues(b,{sortBy:v}).data||[],s=g(this._prepareFacetValues(a),n);var o=n.maxValuesPerFacet,c=this.getLimit(),u=c<o?a.length<=c:a.length<c;this.toggleShowMore=this.createToggleShowMore(e),R({items:s,refine:this._refine,sendEvent:y,createURL:function(e){return r(n.toggleRefinement(b,e))},instantSearchInstance:i,widgetParams:l,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,canToggleShowMore:m&&(this.isShowingMore||!u)},!1)},dispose:function(e){var t=e.state;return w(),t.removeHierarchicalFacet(b).setQueryParameter("maxValuesPerFacet",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.getHierarchicalFacetBreadcrumb(b);return n.length?D({},e,{hierarchicalMenu:D({},e.hierarchicalMenu,L({},b,n))}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.hierarchicalMenu&&n.hierarchicalMenu[b];if(e.isHierarchicalFacet(b))e.getHierarchicalFacetByName(b);var i=e.removeHierarchicalFacet(b).addHierarchicalFacet({name:b,attributes:c,separator:u,rootPath:h,showParentLevel:f}),a=i.maxValuesPerFacet||0,s=Math.max(a,m?p:d),o=i.setQueryParameter("maxValuesPerFacet",s);return r?o.addHierarchicalFacetRefinement(b,r.join(u)):o.setQueryParameters({hierarchicalFacetsRefinements:D({},o.hierarchicalFacetsRefinements,L({},b,[]))})}}}}function tn(u,e){var r=1<arguments.length&&void 0!==e?e:_e;return Pe(u,rn()),function(i){var a,s,e=i||{},t=e.escapeHTML,o=void 0===t||t,n=e.transformItems,c=void 0===n?function(e){return e}:n;return{$$type:"ais.hits",init:function(e){var t=e.instantSearchInstance,n=e.helper;a=Ve({instantSearchInstance:t,index:n.getIndex(),widgetType:this.$$type}),s=We({index:n.getIndex(),widgetType:this.$$type}),u({hits:[],results:void 0,sendEvent:a,bindEvent:s,instantSearchInstance:t,widgetParams:i},!0)},render:function(e){var t=e.results,n=e.instantSearchInstance;o&&0<t.hits.length&&(t.hits=it(t.hits));var r=t.hits.__escaped;t.hits=Be(t.hits,t.page,t.hitsPerPage),t.hits=Qe(t.hits,t.queryID),t.hits=c(t.hits),t.hits.__escaped=r,a("view",t.hits),u({hits:t.hits,results:t,sendEvent:a,bindEvent:s,instantSearchInstance:n,widgetParams:i},!1)},dispose:function(e){var t=e.state;return r(),o?t.setQueryParameters(Object.keys(et).reduce(function(e,t){return D({},e,L({},t,void 0))},{})):t},getWidgetSearchParameters:function(e){return o?e.setQueryParameters(et):e}}}}function nn(e){var t=e.method,n=e.results,r=e.hits,i=e.objectIDs,a=n.index,s=function(n,e){return e.map(function(t){var e=ge(n,function(e){return e.objectID===t});if(void 0===e)throw new Error('Could not find objectID "'.concat(t,'" passed to `clickedObjectIDsAfterSearch` in the returned hits. This is necessary to infer the absolute position and the query ID.'));return e})}(r,i),o=function(e){var t=le(e.map(function(e){return e.__queryID}));if(1<t.length)throw new Error("Insights currently allows a single `queryID`. The `objectIDs` provided map to multiple `queryID`s.");var n=t[0];if("string"!=typeof n)throw new Error("Could not infer `queryID`. Ensure InstantSearch `clickAnalytics: true` was added with the Configure widget.\n\nSee: https://alg.li/lNiZZ7");return n}(s);switch(t){case"clickedObjectIDsAfterSearch":return{index:a,queryID:o,objectIDs:i,positions:function(e){return e.map(function(e){return e.__position})}(s)};case"convertedObjectIDsAfterSearch":return{index:a,queryID:o,objectIDs:i};default:throw new Error('Unsupported method passed to insights: "'.concat(t,'".'))}}var rn=Ae({name:"hits",connector:!0});function an(n){function r(s){return function(e,t){var n=e.results,r=e.hits,i=e.instantSearchInstance;if(n&&r&&i){var a=function(i,a,s){return function(e,t){if(!i){var n=Ae({name:"instantsearch"});throw new Error(n("The `insightsClient` option has not been provided to `instantsearch`."))}if(!Array.isArray(t.objectIDs))throw new TypeError("Expected `objectIDs` to be an array.");var r=nn({method:e,results:a,hits:s,objectIDs:t.objectIDs});i(e,D({},r,{},t))}}(i.insightsClient,n,r);return s(D({},e,{insights:a}),t)}return s(e,t)}}return function(e,t){return n(r(e),t)}}var sn,on,cn,un,ln,hn={},fn=[],dn=/acit|ex(?:s|g|n|p|$)|rph|grid|ows|mnc|ntw|ine[ch]|zoo|^ord|^--/i;function mn(e,t){for(var n in t)e[n]=t[n];return e}function pn(e){var t=e.parentNode;t&&t.removeChild(e)}function vn(e,t,n){var r,i,a,s,o=arguments;if(t=mn({},t),3<arguments.length)for(n=[n],r=3;r<arguments.length;r++)n.push(o[r]);if(null!=n&&(t.children=n),null!=e&&null!=e.defaultProps)for(i in e.defaultProps)void 0===t[i]&&(t[i]=e.defaultProps[i]);return s=t.key,null!=(a=t.ref)&&delete t.ref,null!=s&&delete t.key,gn(e,t,s,a)}function gn(e,t,n,r){var i={type:e,props:t,key:n,ref:r,__k:null,__p:null,__b:0,__e:null,l:null,__c:null,constructor:void 0};return sn.vnode&&sn.vnode(i),i}function yn(e){return e.children}function bn(e,t){this.props=e,this.context=t}function Rn(e,t){if(null==t)return e.__p?Rn(e.__p,e.__p.__k.indexOf(e)+1):null;for(var n;t<e.__k.length;t++)if(null!=(n=e.__k[t])&&null!=n.__e)return n.__e;return"function"==typeof e.type?Rn(e):null}function wn(e){var t,n;if(null!=(e=e.__p)&&null!=e.__c){for(e.__e=e.__c.base=null,t=0;t<e.__k.length;t++)if(null!=(n=e.__k[t])&&null!=n.__e){e.__e=e.__c.base=n.__e;break}return wn(e)}}function Sn(e){(!e.__d&&(e.__d=!0)&&1===on.push(e)||un!==sn.debounceRendering)&&(un=sn.debounceRendering,(sn.debounceRendering||cn)(Pn))}function Pn(){var e,t,n,r,i,a,s,o;for(on.sort(function(e,t){return t.__v.__b-e.__v.__b});e=on.pop();)e.__d&&(r=n=void 0,a=(i=(t=e).__v).__e,s=t.__P,o=t.u,t.u=!1,s&&(n=[],r=Cn(s,i,mn({},i),t.__n,void 0!==s.ownerSVGElement,null,n,o,null==a?Rn(i):a),Tn(n,i),r!=a&&wn(i)))}function _n(t,n,e,r,i,a,s,o,c){var u,l,h,f,d,m,p,v=e&&e.__k||fn,g=v.length;if(o==hn&&(o=null!=a?a[0]:g?Rn(e,0):null),u=0,n.__k=Nn(n.__k,function(e){if(null!=e){if(e.__p=n,e.__b=n.__b+1,null===(h=v[u])||h&&e.key==h.key&&e.type===h.type)v[u]=void 0;else for(l=0;l<g;l++){if((h=v[l])&&e.key==h.key&&e.type===h.type){v[l]=void 0;break}h=null}if(f=Cn(t,e,h=h||hn,r,i,a,s,null,o,c),(l=e.ref)&&h.ref!=l&&(p=p||[]).push(l,e.__c||f,e),null!=f){if(null==m&&(m=f),null!=e.l)f=e.l,e.l=null;else if(a==h||f!=o||null==f.parentNode){e:if(null==o||o.parentNode!==t)t.appendChild(f);else{for(d=o,l=0;(d=d.nextSibling)&&l<g;l+=2)if(d==f)break e;t.insertBefore(f,o)}"option"==n.type&&(t.value="")}o=f.nextSibling,"function"==typeof n.type&&(n.l=f)}}return u++,e}),n.__e=m,null!=a&&"function"!=typeof n.type)for(u=a.length;u--;)null!=a[u]&&pn(a[u]);for(u=g;u--;)null!=v[u]&&kn(v[u],v[u]);if(p)for(u=0;u<p.length;u++)En(p[u],p[++u],p[++u])}function Nn(e,t,n){if(null==n&&(n=[]),null==e||"boolean"==typeof e)t&&n.push(t(null));else if(Array.isArray(e))for(var r=0;r<e.length;r++)Nn(e[r],t,n);else n.push(t?t(function(e){if(null==e||"boolean"==typeof e)return null;if("string"==typeof e||"number"==typeof e)return gn(null,e,null,null);if(null==e.__e&&null==e.__c)return e;var t=gn(e.type,e.props,e.key,null);return t.__e=e.__e,t}(e)):e);return n}function xn(e,t,n){"-"===t[0]?e.setProperty(t,n):e[t]="number"==typeof n&&!1===dn.test(t)?n+"px":null==n?"":n}function Fn(e,t,n,r,i){var a,s,o,c,u;if("key"===(t=i?"className"===t?"class":t:"class"===t?"className":t)||"children"===t);else if("style"===t)if(a=e.style,"string"==typeof n)a.cssText=n;else{if("string"==typeof r&&(a.cssText="",r=null),r)for(s in r)n&&s in n||xn(a,s,"");if(n)for(o in n)r&&n[o]===r[o]||xn(a,o,n[o])}else"o"===t[0]&&"n"===t[1]?(c=t!==(t=t.replace(/Capture$/,"")),t=((u=t.toLowerCase())in e?u:t).slice(2),n?(r||e.addEventListener(t,In,c),(e.t||(e.t={}))[t]=n):e.removeEventListener(t,In,c)):"list"!==t&&"tagName"!==t&&"form"!==t&&!i&&t in e?e[t]=null==n?"":n:"function"!=typeof n&&"dangerouslySetInnerHTML"!==t&&(t!==(t=t.replace(/^xlink:?/,""))?null==n||!1===n?e.removeAttributeNS("http://www.w3.org/1999/xlink",t.toLowerCase()):e.setAttributeNS("http://www.w3.org/1999/xlink",t.toLowerCase(),n):null==n||!1===n?e.removeAttribute(t):e.setAttribute(t,n))}function In(e){return this.t[e.type](sn.event?sn.event(e):e)}function Cn(e,t,n,r,i,a,s,o,c,u){var l,h,f,d,m,p,v,g,y,b,R=t.type;if(void 0!==t.constructor)return null;(l=sn.__b)&&l(t);try{e:if("function"==typeof R){if(g=t.props,y=(l=R.contextType)&&r[l.__c],b=l?y?y.props.value:l.__p:r,n.__c?v=(h=t.__c=n.__c).__p=h.__E:("prototype"in R&&R.prototype.render?t.__c=h=new R(g,b):(t.__c=h=new bn(g,b),h.constructor=R,h.render=Mn),y&&y.sub(h),h.props=g,h.state||(h.state={}),h.context=b,h.__n=r,f=h.__d=!0,h.__h=[]),null==h.__s&&(h.__s=h.state),null!=R.getDerivedStateFromProps&&mn(h.__s==h.state?h.__s=mn({},h.__s):h.__s,R.getDerivedStateFromProps(g,h.__s)),f)null==R.getDerivedStateFromProps&&null!=h.componentWillMount&&h.componentWillMount(),null!=h.componentDidMount&&s.push(h);else{if(null==R.getDerivedStateFromProps&&null==o&&null!=h.componentWillReceiveProps&&h.componentWillReceiveProps(g,b),!o&&null!=h.shouldComponentUpdate&&!1===h.shouldComponentUpdate(g,h.__s,b)){for(h.props=g,h.state=h.__s,h.__d=!1,(h.__v=t).__e=null!=c?c!==n.__e?c:n.__e:null,t.__k=n.__k,l=0;l<t.__k.length;l++)t.__k[l]&&(t.__k[l].__p=t);break e}null!=h.componentWillUpdate&&h.componentWillUpdate(g,h.__s,b)}for(d=h.props,m=h.state,h.context=b,h.props=g,h.state=h.__s,(l=sn.__r)&&l(t),h.__d=!1,h.__v=t,h.__P=e,l=h.render(h.props,h.state,h.context),t.__k=Nn(null!=l&&l.type==yn&&null==l.key?l.props.children:l),null!=h.getChildContext&&(r=mn(mn({},r),h.getChildContext())),f||null==h.getSnapshotBeforeUpdate||(p=h.getSnapshotBeforeUpdate(d,m)),_n(e,t,n,r,i,a,s,c,u),h.base=t.__e;l=h.__h.pop();)h.__s&&(h.state=h.__s),l.call(h);f||null==d||null==h.componentDidUpdate||h.componentDidUpdate(d,m,p),v&&(h.__E=h.__p=null)}else t.__e=function(e,t,n,r,i,a,s,o){var c,u,l,h,f=n.props,d=t.props;if(i="svg"===t.type||i,null==e&&null!=a)for(c=0;c<a.length;c++)if(null!=(u=a[c])&&(null===t.type?3===u.nodeType:u.localName===t.type)){e=u,a[c]=null;break}if(null==e){if(null===t.type)return document.createTextNode(d);e=i?document.createElementNS("http://www.w3.org/2000/svg",t.type):document.createElement(t.type),a=null}return null===t.type?f!==d&&(null!=a&&(a[a.indexOf(e)]=null),e.data=d):t!==n&&(null!=a&&(a=fn.slice.call(e.childNodes)),l=(f=n.props||hn).dangerouslySetInnerHTML,h=d.dangerouslySetInnerHTML,o||(h||l)&&(h&&l&&h.__html==l.__html||(e.innerHTML=h&&h.__html||"")),function(e,t,n,r,i){var a;for(a in n)a in t||Fn(e,a,null,n[a],r);for(a in t)i&&"function"!=typeof t[a]||"value"===a||"checked"===a||n[a]===t[a]||Fn(e,a,t[a],n[a],r)}(e,d,f,i,o),t.__k=t.props.children,h||_n(e,t,n,r,"foreignObject"!==t.type&&i,a,s,hn,o),o||("value"in d&&void 0!==d.value&&d.value!==e.value&&(e.value=null==d.value?"":d.value),"checked"in d&&void 0!==d.checked&&d.checked!==e.checked&&(e.checked=d.checked))),e}(n.__e,t,n,r,i,a,s,u);(l=sn.diffed)&&l(t)}catch(e){sn.__e(e,t,n)}return t.__e}function Tn(e,t){for(var n;n=e.pop();)try{n.componentDidMount()}catch(e){sn.__e(e,n.__v)}sn.__c&&sn.__c(t)}function En(e,t,n){try{"function"==typeof e?e(t):e.current=t}catch(e){sn.__e(e,n)}}function kn(e,t,n){var r,i,a;if(sn.unmount&&sn.unmount(e),(r=e.ref)&&En(r,null,t),n||"function"==typeof e.type||(n=null!=(i=e.__e)),e.__e=e.l=null,null!=(r=e.__c)){if(r.componentWillUnmount)try{r.componentWillUnmount()}catch(e){sn.__e(e,t)}r.base=r.__P=null}if(r=e.__k)for(a=0;a<r.length;a++)r[a]&&kn(r[a],t,n);null!=i&&pn(i)}function Mn(e,t,n){return this.constructor(e,n)}function Ln(e,t,n){var r,i,a;sn.__p&&sn.__p(e,t),i=(r=n===ln)?null:n&&n.__k||t.__k,e=vn(yn,null,[e]),a=[],Cn(t,r?t.__k=e:(n||t).__k=e,i||hn,hn,void 0!==t.ownerSVGElement,n&&!r?[n]:i?null:fn.slice.call(t.childNodes),a,!1,n||hn,r),Tn(a,e)}sn={},bn.prototype.setState=function(e,t){var n=this.__s!==this.state&&this.__s||(this.__s=mn({},this.state));"function"==typeof e&&!(e=e(n,this.props))||mn(n,e),null!=e&&this.__v&&(this.u=!1,t&&this.__h.push(t),Sn(this))},bn.prototype.forceUpdate=function(e){this.__v&&(e&&this.__h.push(e),this.u=!0,Sn(this))},bn.prototype.render=yn,on=[],cn="function"==typeof Promise?Promise.prototype.then.bind(Promise.resolve()):setTimeout,un=sn.debounceRendering,sn.__e=function(e,t,n){for(var r;t=t.__p;)if((r=t.__c)&&!r.__p)try{if(r.constructor&&null!=r.constructor.getDerivedStateFromError)r.setState(r.constructor.getDerivedStateFromError(e));else{if(null==r.componentDidCatch)continue;r.componentDidCatch(e)}return Sn(r.__E=r)}catch(t){e=t}throw e},ln=hn;function jn(e,t,n){for(var r=e;r&&!n(r);){if(r===t)return null;r=r.parentElement}return r}function On(e){return function(o){return vn("div",{onClick:function(e){if(o.sendEvent){var t=jn(e.target,e.currentTarget,function(e){return e.hasAttribute("data-insights-event")});if(t){var n=function(e){var t=e.getAttribute("data-insights-event");if("string"!=typeof t)throw new Error("The insights middleware expects `data-insights-event` to be a base64-encoded JSON string.");try{return JSON.parse(atob(t))}catch(e){throw new Error("The insights middleware was unable to parse `data-insights-event`.")}}(t);o.sendEvent(n)}}var r=jn(e.target,e.currentTarget,function(e){return function(e){return e.hasAttribute("data-insights-method")}(e)});if(r){var i=function(e){var t=e.getAttribute("data-insights-method"),n=e.getAttribute("data-insights-payload");if("string"!=typeof n)throw new Error("The insights helper expects `data-insights-payload` to be a base64-encoded JSON string.");try{return{method:t,payload:JSON.parse(atob(n))}}catch(e){throw new Error("The insights helper was unable to parse `data-insights-payload`.")}}(r),a=i.method,s=i.payload;o.insights(a,s)}}},vn(e,o))}}function An(h,e){var a=1<arguments.length&&void 0!==e?e:_e;return Pe(h,Dn()),function(s){var e=s||{},t=e.items,n=e.transformItems,o=void 0===n?function(e){return e}:n,c=t;if(!Array.isArray(c))throw new Error(Dn("The `items` option expects an array of objects."));var r=c.filter(function(e){return!0===e.default});if(0===r.length)throw new Error(Dn("A default value must be specified in `items`."));if(1<r.length)throw new Error(Dn("More than one default value is specified in `items`."));function u(e){var t=e.hitsPerPage;return c.map(function(e){return D({},e,{isRefined:Number(e.value)===Number(t)})})}var i=r[0],l={};return{$$type:"ais.hitsPerPage",init:function(e){var t=e.helper,n=e.createURL,r=e.state,i=e.instantSearchInstance,a=c.some(function(e){return Number(r.hitsPerPage)===Number(e.value)});l.setHitsPerPage=function(e){return e||0===e?t.setQueryParameter("hitsPerPage",e).search():t.setQueryParameter("hitsPerPage",void 0).search()},a||(c=[{value:"",label:""}].concat(_(c))),l.createURLFactory=function(t){return function(e){return n(t.setQueryParameter("hitsPerPage",e||0===e?e:void 0))}},h({items:o(u(r)),refine:l.setHitsPerPage,createURL:l.createURLFactory(t.state),hasNoResults:!0,widgetParams:s,instantSearchInstance:i},!0)},render:function(e){var t=e.state,n=e.results,r=e.instantSearchInstance,i=0===n.nbHits;h({items:o(u(t)),refine:l.setHitsPerPage,createURL:l.createURLFactory(t),hasNoResults:i,widgetParams:s,instantSearchInstance:r},!1)},dispose:function(e){var t=e.state;return a(),t.setQueryParameter("hitsPerPage",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.hitsPerPage;return void 0===n||n===i.value?e:D({},e,{hitsPerPage:n})},getWidgetSearchParameters:function(e,t){var n=t.uiState;return e.setQueryParameters({hitsPerPage:n.hitsPerPage||i.value})}}}}var Hn=an(tn),Dn=Ae({name:"hits-per-page",connector:!0}),Bn=Ae({name:"infinite-hits",connector:!0});function Qn(e){var t=e||{};t.page;return A(t,["page"])}function qn(n){return Object.keys(n).map(Number).sort(function(e,t){return e-t}).reduce(function(e,t){return e.concat(n[t])},[])}function Un(P,e){var i=1<arguments.length&&void 0!==e?e:_e;return Pe(P,Bn()),function(l){function h(){return Math.min.apply(Math,_(Object.keys(S||{}).map(Number)))}function f(){return Math.max.apply(Math,_(Object.keys(S||{}).map(Number)))}function d(e){var n=0<arguments.length&&void 0!==e?e:{};return Object.keys(n).filter(function(e){return Array.isArray(n[e])?n[e].length:Object.keys(n[e]).length}).reduce(function(e,t){return e[t]=n[t],e},{})}var m,p,v,g,y,e=l||{},t=e.escapeHTML,b=void 0===t||t,n=e.transformItems,R=void 0===n?function(e){return e}:n,r=e.cache,w=void 0===r?function(){var r=null,i=void 0;return{read:function(e){var t=e.state;return Te(i,Qn(t))?r:null},write:function(e){var t=e.state,n=e.hits;i=Qn(t),r=n}}}():r,S=void 0;return{$$type:"ais.infiniteHits",init:function(e){var t=e.instantSearchInstance,n=e.helper;p=function(e){return function(){e.overrideStateWithoutTriggeringChangeEvent(D({},e.state,{page:h()-1})).searchWithoutTriggeringOnStateChange()}}(n),v=function(e){return function(){e.setPage(f()+1).search()}}(n),g=Ve({instantSearchInstance:t,index:n.getIndex(),widgetType:this.$$type}),y=We({index:n.getIndex(),widgetType:this.$$type}),P({hits:qn(w.read({state:n.state})||{}),results:void 0,sendEvent:g,bindEvent:y,showPrevious:p,showMore:v,isFirstPage:0===h()||void 0===n.state.page,isLastPage:!0,instantSearchInstance:t,widgetParams:l},!0)},render:function(e){var t=e.results,n=e.state,r=e.instantSearchInstance,i=n.page,a=void 0===i?0:i,s=(n.facets,n.hierarchicalFacets,n.disjunctiveFacets,n.maxValuesPerFacet,A(n,["page","facets","hierarchicalFacets","disjunctiveFacets","maxValuesPerFacet"]));s.facetsRefinements=d(s.facetsRefinements),s.hierarchicalFacetsRefinements=d(s.hierarchicalFacetsRefinements),s.disjunctiveFacetsRefinements=d(s.disjunctiveFacetsRefinements),s.numericRefinements=d(s.numericRefinements),Te(s,m)||(S=w.read({state:n})||{},m=s),b&&0<t.hits.length&&(t.hits=it(t.hits));var o=t.hits.__escaped;t.hits=Be(t.hits,t.page,t.hitsPerPage),t.hits=Qe(t.hits,t.queryID),t.hits=R(t.hits),t.hits.__escaped=o,void 0===S&&(S=w.read({state:n})||{}),void 0===S[a]&&(S[a]=t.hits,w.write({state:n,hits:S}));var c=0===h(),u=t.nbPages<=f()+1;g("view",S[a]),P({hits:qn(S),results:t,sendEvent:g,bindEvent:y,showPrevious:p,showMore:v,isFirstPage:c,isLastPage:u,instantSearchInstance:r,widgetParams:l},!1)},dispose:function(e){var t=e.state;i();var n=t.setQueryParameter("page",void 0);return b?n.setQueryParameters(Object.keys(et).reduce(function(e,t){return D({},e,L({},t,void 0))},{})):n},getWidgetState:function(e,t){var n=t.searchParameters.page||0;return n?D({},e,{page:n+1}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=e;b&&(r=e.setQueryParameters(et));var i=n.page?n.page-1:0;return r.setQueryParameter("page",i)}}}}var Vn=an(Un),Wn=Ae({name:"menu",connector:!0});function $n(m){var a=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(m,Wn()),function(){var s,o=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},c=o.attribute,e=o.limit,u=void 0===e?10:e,t=o.showMore,l=void 0!==t&&t,n=o.showMoreLimit,h=void 0===n?20:n,r=o.sortBy,f=void 0===r?["isRefined","name:asc"]:r,i=o.transformItems,d=void 0===i?function(e){return e}:i;if(!c)throw new Error(Wn("The `attribute` option is required."));if(!0===l&&h<=u)throw new Error(Wn("The `showMoreLimit` option must be greater than `limit`."));return{$$type:"ais.menu",isShowingMore:!1,toggleShowMore:function(){},cachedToggleShowMore:function(){this.toggleShowMore()},createToggleShowMore:function(e){var t=this,n=e.results,r=e.instantSearchInstance;return function(){t.isShowingMore=!t.isShowingMore,t.render({results:n,instantSearchInstance:r})}},getLimit:function(){return this.isShowingMore?h:u},refine:function(n){return function(e){var t=Q(n.getHierarchicalFacetBreadcrumb(c),1)[0];s("click",e||t),n.toggleRefinement(c,e||t).search()}},init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance;s=qe({instantSearchInstance:r,helper:t,attribute:c,widgetType:this.$$type}),this.cachedToggleShowMore=this.cachedToggleShowMore.bind(this),this._createURL=function(e){return n(t.state.toggleRefinement(c,e))},this._refine=this.refine(t),m({items:[],createURL:this._createURL,refine:this._refine,sendEvent:s,instantSearchInstance:r,canRefine:!1,widgetParams:o,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,canToggleShowMore:!1},!0)},render:function(e){var t=e.results,n=e.instantSearchInstance,r=t.getFacetValues(c,{sortBy:f}),i=r&&r.data?r.data:[],a=d(i.slice(0,this.getLimit()).map(function(e){var t=e.name,n=e.path;return D({},A(e,["name","path"]),{label:t,value:n})}));this.toggleShowMore=this.createToggleShowMore({results:t,instantSearchInstance:n}),m({items:a,createURL:this._createURL,refine:this._refine,sendEvent:s,instantSearchInstance:n,canRefine:0<a.length,widgetParams:o,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,canToggleShowMore:l&&(this.isShowingMore||i.length>this.getLimit())},!1)},dispose:function(e){var t=e.state;return a(),t.removeHierarchicalFacet(c).setQueryParameter("maxValuesPerFacet",void 0)},getWidgetState:function(e,t){var n=Q(t.searchParameters.getHierarchicalFacetBreadcrumb(c),1)[0];return n?D({},e,{menu:D({},e.menu,L({},c,n))}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.menu&&n.menu[c],i=e.removeHierarchicalFacet(c).addHierarchicalFacet({name:c,attributes:[c]}),a=i.maxValuesPerFacet||0,s=Math.max(a,l?h:u),o=i.setQueryParameter("maxValuesPerFacet",s);return r?o.addHierarchicalFacetRefinement(c,r):o.setQueryParameters({hierarchicalFacetsRefinements:D({},o.hierarchicalFacetsRefinements,L({},c,[]))})}}}}function zn(l,e){var h=1<arguments.length&&void 0!==e?e:_e;return Pe(l,Kn()),function(i){var e=i||{},t=e.attribute,u=void 0===t?"":t,n=e.items,r=void 0===n?[]:n,a=e.transformItems,s=void 0===a?function(e){return e}:a;if(""===u)throw new Error(Kn("The `attribute` option is required."));if(!r||0===r.length)throw new Error(Kn("The `items` option expects an array of objects."));function o(i){return r.map(function(e){var t=e.start,n=e.end,r=e.label;return{label:r,value:window.encodeURI(JSON.stringify({start:t,end:n})),isRefined:Yn(i,u,{start:t,end:n,label:r})}})}var c={};return{$$type:Jn,init:function(e){var n=e.helper,r=e.createURL,t=e.instantSearchInstance;c.sendEvent=function(e){var c=e.instantSearchInstance,u=e.helper,l=e.attribute;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];if(1!==t.length){var r=t[0],i=t[1],a=t[2],s=void 0===a?"Filter Applied":a;if("click"===r){var o=$e(Gn(u.state,l,i),l);o&&0<o.length&&c.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:Jn,eventType:r,payload:{eventName:s,index:u.getIndex(),filters:o}})}}else c.sendEventToInsights(t[0])}}({instantSearchInstance:t,helper:n,attribute:u}),c.refine=function(e){var t=Gn(n.state,u,e);c.sendEvent("click",e),n.setState(t).search()},c.createURL=function(t){return function(e){return r(Gn(t,u,e))}},l({createURL:c.createURL(n.state),items:s(o(n.state)),hasNoResults:!0,refine:c.refine,sendEvent:c.sendEvent,instantSearchInstance:t,widgetParams:i},!0)},render:function(e){var t=e.results,n=e.state,r=e.instantSearchInstance;l({createURL:c.createURL(n),items:s(o(n)),hasNoResults:0===t.nbHits,refine:c.refine,sendEvent:c.sendEvent,instantSearchInstance:r,widgetParams:i},!1)},dispose:function(e){var t=e.state;return h(),t.clearRefinements(u)},getWidgetState:function(e,t){var n=t.searchParameters.getNumericRefinements(u),r=n["="]&&n["="][0];if(r||0===r)return D({},e,{numericMenu:D({},e.numericMenu,L({},u,"".concat(n["="])))});var i=n[">="]&&n[">="][0]||"",a=n["<="]&&n["<="][0]||"";return""===i&&""===a?e:D({},e,{numericMenu:D({},e.numericMenu,L({},u,"".concat(i,":").concat(a)))})},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.numericMenu&&n.numericMenu[u],i=e.clearRefinements(u);if(!r)return i.setQueryParameters({numericRefinements:D({},i.numericRefinements,L({},u,{}))});if(-1===r.indexOf(":"))return i.addNumericRefinement(u,"=",Number(r));var a=Q(r.split(":").map(parseFloat),2),s=a[0],o=a[1],c=xe(s)?i.addNumericRefinement(u,">=",s):i;return xe(o)?c.addNumericRefinement(u,"<=",o):c}}}}var Kn=Ae({name:"numeric-menu",connector:!0}),Jn="ais.numericMenu";function Yn(e,t,n){var r=e.getNumericRefinements(t);return void 0!==n.start&&void 0!==n.end&&n.start===n.end?Xn(r,"=",n.start):void 0!==n.start?Xn(r,">=",n.start):void 0!==n.end?Xn(r,"<=",n.end):void 0===n.start&&void 0===n.end&&Object.keys(r).every(function(e){return 0===(r[e]||[]).length})}function Gn(e,t,n){var r=e,i=JSON.parse(window.decodeURI(n)),a=r.getNumericRefinements(t);if(void 0===i.start&&void 0===i.end)return r.removeNumericRefinement(t);if(Yn(r,t,i)||(r=r.removeNumericRefinement(t)),void 0!==i.start&&void 0!==i.end){if(i.start>i.end)throw new Error("option.start should be > to option.end");if(i.start===i.end)return r=Xn(a,"=",i.start)?r.removeNumericRefinement(t,"=",i.start):r.addNumericRefinement(t,"=",i.start)}return void 0!==i.start&&(r=Xn(a,">=",i.start)?r.removeNumericRefinement(t,">=",i.start):r.addNumericRefinement(t,">=",i.start)),void 0!==i.end&&(r=Xn(a,"<=",i.end)?r.removeNumericRefinement(t,"<=",i.end):r.addNumericRefinement(t,"<=",i.end)),"number"==typeof r.page&&(r.page=0),r}function Xn(e,t,n){return void 0!==e[t]&&e[t].includes(n)}var Zn=function(){function t(e){k(this,t),this.currentPage=e.currentPage,this.total=e.total,this.padding=e.padding}return M(t,[{key:"pages",value:function(){var e=this.total,t=this.currentPage,n=this.padding;if(0===e)return[0];var r=this.nbPagesDisplayed(n,e);if(r===e)return Ie({end:e});var i=this.calculatePaddingLeft(t,n,e,r);return Ie({start:t-i,end:t+(r-i)})}},{key:"nbPagesDisplayed",value:function(e,t){return Math.min(2*e+1,t)}},{key:"calculatePaddingLeft",value:function(e,t,n,r){return e<=t?e:n-t<=e?r-(n-e):t}},{key:"isLastPage",value:function(){return this.currentPage===this.total-1||0===this.total}},{key:"isFirstPage",value:function(){return 0===this.currentPage}}]),t}(),er=Ae({name:"pagination",connector:!0});function tr(c){var r=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(c,er()),function(){var s=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},n=s.totalPages,e=s.padding,o=new Zn({currentPage:0,total:0,padding:void 0===e?3:e});return{$$type:"ais.pagination",init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance;this.refine=function(e){t.setPage(e),t.search()},this.createURL=function(t){return function(e){return n(t.setPage(e))}},c({createURL:this.createURL(t.state),currentRefinement:t.state.page||0,nbHits:0,nbPages:0,pages:[],isFirstPage:!0,isLastPage:!0,refine:this.refine,widgetParams:s,instantSearchInstance:r},!0)},getMaxPage:function(e){var t=e.nbPages;return void 0!==n?Math.min(n,t):t},render:function(e){var t=e.results,n=e.state,r=e.instantSearchInstance,i=n.page||0,a=this.getMaxPage(t);o.currentPage=i,o.total=a,c({createURL:this.createURL(n),currentRefinement:i,refine:this.refine,nbHits:t.nbHits,nbPages:a,pages:o.pages(),isFirstPage:o.isFirstPage(),isLastPage:o.isLastPage(),widgetParams:s,instantSearchInstance:r},!1)},dispose:function(e){var t=e.state;return r(),t.setQueryParameter("page",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.page||0;return n?D({},e,{page:n+1}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.page?n.page-1:0;return e.setQueryParameter("page",r)}}}}var nr=Ae({name:"range-input",connector:!0},{name:"range-slider",connector:!0}),rr="ais.range";function ir(f){var r=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(f,nr()),function(){var c=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},S=c.attribute,P=c.min,_=c.max,e=c.precision,u=void 0===e?0:e,N=xe(P),x=xe(_);if(!S)throw new Error(nr("The `attribute` option is required."));if(N&&x&&_<P)throw new Error(nr("The `max` option can't be lower than `min`."));function F(e){return Number(Number(e).toFixed(u))}function d(e,t,n,r){var i,a,s=e.state,o=t.min,c=t.max,u=Q(s.getNumericRefinement(S,">=")||[],1)[0],l=Q(s.getNumericRefinement(S,"<=")||[],1)[0],h=void 0===n||""===n,f=void 0===r||""===r,d=h?void 0:parseFloat(n),m=f?void 0:parseFloat(r);a=x||c!==m?x&&f?_:m:void 0;var p=void 0===(i=N||o!==d?N&&h?P:d:void 0),v=xe(i),g=xe(o),y=p||v&&(!g||g&&o<=i),b=void 0===a,R=xe(a),w=xe(c);return(u!==i||l!==a)&&y&&(b||R&&(!w||w&&a<=c))?(s=s.removeNumericRefinement(S),v&&(s=s.addNumericRefinement(S,">=",F(i))),R&&(s=s.addNumericRefinement(S,"<=",F(a))),s):null}function m(e,t,n,r){var i=3<arguments.length&&void 0!==r?r:"Filter Applied",a=$e(e,S);a&&0<a.length&&t.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:rr,eventType:"click",payload:{eventName:i,index:n.getIndex(),filters:a}})}function l(l,h,f){return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];if(1!==t.length){var r=t[0],i=t[1],a=t[2];if("click"===r){var s=Q(i,2),o=s[0],c=s[1],u=d(h,f,o,c);m(u,l,h,a)}}else l.sendEventToInsights(t[0])}}var h={from:function(e){return e},to:function(e){return F(e).toLocaleString()}};return{$$type:rr,_getCurrentRange:function(e){var t,n,r=Math.pow(10,u);return t=N?P:xe(e.min)?e.min:0,n=x?_:xe(e.max)?e.max:0,{min:Math.floor(t*r)/r,max:Math.ceil(n*r)/r}},_getCurrentRefinement:function(e){var t=Q(e.getNumericRefinement(S,">=")||[],1)[0],n=Q(e.getNumericRefinement(S,"<=")||[],1)[0];return[xe(t)?t:-1/0,xe(n)?n:1/0]},_refine:function(i,a,s){return function(){var e=Q(0<arguments.length&&void 0!==arguments[0]?arguments[0]:[],2),t=e[0],n=e[1],r=d(a,s,t,n);r&&(m(r,i,a),a.setState(r).search())}},init:function(e){var t=e.helper,n=e.instantSearchInstance,r=this._getCurrentRange({}),i=this._getCurrentRefinement(t);f({refine:this._refine(n,t,{}),sendEvent:l(n,t,{}),format:h,range:r,widgetParams:D({},c,{precision:u}),start:i,instantSearchInstance:n},!0)},render:function(e){var t=e.results,n=e.helper,r=e.instantSearchInstance,i=ge(t.disjunctiveFacets||[],function(e){return e.name===S}),a=i&&i.stats||{},s=this._getCurrentRange(a),o=this._getCurrentRefinement(n);f({refine:this._refine(r,n,s),sendEvent:l(r,n,s),format:h,range:s,widgetParams:D({},c,{precision:u}),start:o,instantSearchInstance:r},!1)},dispose:function(e){var t=e.state;r();var n=t.removeDisjunctiveFacet(S);return n.numericRefinements=D({},t.numericRefinements,L({},S,void 0)),n},getWidgetState:function(e,t){var n=t.searchParameters.getNumericRefinements(S),r=n[">="],i=void 0===r?[]:r,a=n["<="],s=void 0===a?[]:a;return 0===i.length&&0===s.length?e:D({},e,{range:D({},e.range,L({},S,"".concat(i,":").concat(s)))})},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=e.addDisjunctiveFacet(S).setQueryParameters({numericRefinements:D({},e.numericRefinements,L({},S,{}))});N&&(r=r.addNumericRefinement(S,">=",P)),x&&(r=r.addNumericRefinement(S,"<=",_));var i=n.range&&n.range[S];if(!i||-1===i.indexOf(":"))return r;var a=Q(i.split(":").map(parseFloat),2),s=a[0],o=a[1];return xe(s)&&(r=r.addNumericRefinement(S,">=",s)),xe(o)&&(r=r.addNumericRefinement(S,"<=",o)),r}}}}var ar=Ae({name:"refinement-list",connector:!0});function sr(x){var c=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(x,ar()),function(){var d=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},m=d.attribute,e=d.operator,h=void 0===e?"or":e,t=d.limit,p=void 0===t?10:t,n=d.showMore,v=void 0!==n&&n,r=d.showMoreLimit,f=void 0===r?20:r,i=d.sortBy,u=void 0===i?["isRefined","count:desc","name:asc"]:i,a=d.escapeFacetValues,l=void 0===a||a,s=d.transformItems,g=void 0===s?function(e){return e}:s;if(!m)throw new Error(ar("The `attribute` option is required."));if(!/^(and|or)$/.test(h))throw new Error(ar('The `operator` must one of: `"and"`, `"or"` (got "'.concat(h,'").')));if(!0===v&&f<=p)throw new Error(ar("`showMoreLimit` should be greater than `limit`."));function y(e){var t=e.name;return D({},A(e,["name"]),{label:t,value:t,highlighted:t})}function b(e){return e?f:p}function R(e){var t=e.items,n=e.state,r=e.createURL,i=e.helperSpecializedSearchFacetValues,a=e.refine,s=e.isFromSearch,o=e.isFirstSearch,c=e.isShowingMore,u=e.toggleShowMore,l=e.instantSearchInstance,h=i&&i(n,r,i,a,l,c),f=c&&_.length>p||v&&!s&&!N;x({createURL:function(e){return r(n.toggleRefinement(m,e))},items:t,refine:a,searchForItems:h,instantSearchInstance:l,isFromSearch:s,canRefine:s||0<t.length,widgetParams:d,isShowingMore:c,canToggleShowMore:f,toggleShowMore:u,hasExhaustiveItems:N},o)}function o(n,u){return function(r,i,a,s,o,c){return function(e){if(""===e&&_)R({items:_,state:r,createURL:i,helperSpecializedSearchFacetValues:a,refine:s,isFromSearch:!1,isFirstSearch:!1,instantSearchInstance:o,toggleShowMore:u,isShowingMore:c});else{var t={highlightPreTag:l?et.highlightPreTag:tt.highlightPreTag,highlightPostTag:l?et.highlightPostTag:tt.highlightPostTag};n.searchForFacetValues(m,e,Math.min(b(c),100),t).then(function(e){var t=l?function(e){return e.map(function(e){return D({},e,{highlighted:nt(e.highlighted)})})}(e.facetHits):e.facetHits,n=g(t.map(function(e){var t=e.value;return D({},A(e,["value"]),{value:t,label:t})}));R({items:n,state:r,createURL:i,helperSpecializedSearchFacetValues:a,refine:s,isFromSearch:!0,isFirstSearch:!1,instantSearchInstance:o,isShowingMore:c})})}}}}var w,S,P,_=[],N=!0;return{$$type:"ais.refinementList",isShowingMore:!1,toggleShowMore:function(){},cachedToggleShowMore:function(){this.toggleShowMore()},createToggleShowMore:function(e){var t=this;return function(){t.isShowingMore=!t.isShowingMore,t.render(e)}},getLimit:function(){return b(this.isShowingMore)},init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance;this.cachedToggleShowMore=this.cachedToggleShowMore.bind(this),P=qe({instantSearchInstance:r,helper:t,attribute:m,widgetType:this.$$type}),S=function(e){P("click",e),t.toggleRefinement(m,e).search()},w=o(t,this.cachedToggleShowMore),R({items:[],state:t.state,createURL:n,helperSpecializedSearchFacetValues:w,refine:S,isFromSearch:!1,isFirstSearch:!0,instantSearchInstance:r,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,sendEvent:P})},render:function(e){var t=e.results,n=e.state,r=e.createURL,i=e.instantSearchInstance,a=t.getFacetValues(m,{sortBy:u})||[],s=g(a.slice(0,this.getLimit()).map(y)),o=n.maxValuesPerFacet,c=this.getLimit();N=c<o?a.length<=c:a.length<c,_=s,this.toggleShowMore=this.createToggleShowMore(e),R({items:s,state:n,createURL:r,helperSpecializedSearchFacetValues:w,refine:S,isFromSearch:!1,isFirstSearch:!1,instantSearchInstance:i,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,sendEvent:P})},dispose:function(e){var t=e.state;c();var n=t.setQueryParameter("maxValuesPerFacet",void 0);return"and"===h?n.removeFacet(m):n.removeDisjunctiveFacet(m)},getWidgetState:function(e,t){var n=t.searchParameters,r="or"===h?n.getDisjunctiveRefinements(m):n.getConjunctiveRefinements(m);return r.length?D({},e,{refinementList:D({},e.refinementList,L({},m,r))}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r="or"===h,i=n.refinementList&&n.refinementList[m],a=e.clearRefinements(m),s=r?a.addDisjunctiveFacet(m):a.addFacet(m),o=s.maxValuesPerFacet||0,c=Math.max(o,v?f:p),u=s.setQueryParameter("maxValuesPerFacet",c);if(i)return i.reduce(function(e,t){return r?e.addDisjunctiveFacetRefinement(m,t):e.addFacetRefinement(m,t)},u);var l=r?"disjunctiveFacetsRefinements":"facetsRefinements";return u.setQueryParameters(L({},l,D({},u[l],L({},m,[]))))}}}}var or=Ae({name:"search-box",connector:!0});function cr(o){var n=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(o,or()),function(){var i=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},a=i.queryHook;function s(e){return function(){e.setQuery(""),e.search()}}return{$$type:"ais.searchBox",_clear:function(){},_cachedClear:function(){this._clear()},init:function(e){var t=e.helper,n=e.instantSearchInstance;this._cachedClear=this._cachedClear.bind(this),this._clear=s(t);function r(e){e!==t.state.query&&t.setQuery(e).search()}this._refine=function(e){a?a(e,r):r(e)},o({query:t.state.query||"",refine:this._refine,clear:this._cachedClear,widgetParams:i,instantSearchInstance:n},!0)},render:function(e){var t=e.helper,n=e.instantSearchInstance,r=e.searchMetadata;this._clear=s(t),o({query:t.state.query||"",refine:this._refine,clear:this._cachedClear,widgetParams:i,instantSearchInstance:n,isSearchStalled:r.isSearchStalled},!1)},dispose:function(e){var t=e.state;return n(),t.setQueryParameter("query",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.query||"";return""===n||e&&e.query===n?e:D({},e,{query:n})},getWidgetSearchParameters:function(e,t){var n=t.uiState;return e.setQueryParameter("query",n.query||"")}}}}var ur=Ae({name:"sort-by",connector:!0});function lr(c){var n=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(c,ur()),function(){var a=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},s=a.items,e=a.transformItems,o=void 0===e?function(e){return e}:e;if(!Array.isArray(s))throw new Error(ur("The `items` option expects an array of objects."));return{$$type:"ais.sortBy",init:function(e){var t=e.helper,n=e.instantSearchInstance,r=e.parent,i=t.state.index;ge(s,function(e){return e.value===i});this.initialIndex=r.getIndexName(),this.setIndex=function(e){t.setIndex(e).search()},c({currentRefinement:i,options:o(s),refine:this.setIndex,hasNoResults:!0,widgetParams:a,instantSearchInstance:n},!0)},render:function(e){var t=e.helper,n=e.results,r=e.instantSearchInstance;c({currentRefinement:t.state.index,options:o(s),refine:this.setIndex,hasNoResults:0===n.nbHits,widgetParams:a,instantSearchInstance:r},!1)},dispose:function(e){var t=e.state;return n(),t.setIndex(this.initialIndex)},getWidgetState:function(e,t){var n=t.searchParameters.index;return n===this.initialIndex?e:D({},e,{sortBy:n})},getWidgetSearchParameters:function(e,t){var n=t.uiState;return e.setQueryParameter("index",n.sortBy||this.initialIndex||e.index)}}}}var hr=Ae({name:"rating-menu",connector:!0}),fr="ais.ratingMenu",dr=function(e){var o=e.instantSearchInstance,c=e.helper,u=e.getRefinedStar,l=e.attribute;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];if(1!==t.length){var r=t[0],i=t[1],a=t[2],s=void 0===a?"Filter Applied":a;if("click"===r)u()===Number(i)||o.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:fr,eventType:r,payload:{eventName:s,index:c.getIndex(),filters:["".concat(l,">=").concat(i)]}})}else o.sendEventToInsights(t[0])}};function mr(g){var n=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(g,hr()),function(){var d,m=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},p=m.attribute,e=m.max,v=void 0===e?5:e;if(!p)throw new Error(hr("The `attribute` option is required."));return{$$type:fr,init:function(e){var t=this,n=e.helper,r=e.createURL,i=e.instantSearchInstance;this._toggleRefinement=this._toggleRefinement.bind(this,n),this._createURL=function(t){return function(e){return r(t.toggleRefinement(p,e))}},d=dr({instantSearchInstance:i,helper:n,getRefinedStar:function(){return t._getRefinedStar(n.state)},attribute:p}),g({instantSearchInstance:i,items:[],hasNoResults:!0,refine:this._toggleRefinement,sendEvent:d,createURL:this._createURL(n.state),widgetParams:m},!0)},render:function(e){for(var t=e.helper,n=e.results,r=e.state,i=e.instantSearchInstance,a=[],s={},o=v;0<=o;--o)s[o]=0;(n.getFacetValues(p)||[]).forEach(function(e){var t=Math.round(e.name);if(t&&!(v<t))for(var n=t;1<=n;--n)s[n]+=e.count});for(var c=this._getRefinedStar(t.state),u=v-1;1<=u;--u){var l=s[u];if(!c||u===c||0!==l){for(var h=[],f=1;f<=v;++f)h.push(f<=u);a.push({stars:h,name:String(u),value:String(u),count:l,isRefined:c===u})}}g({instantSearchInstance:i,items:a,hasNoResults:0===n.nbHits,refine:this._toggleRefinement,sendEvent:d,createURL:this._createURL(r),widgetParams:m},!1)},dispose:function(e){var t=e.state;return n(),t.removeDisjunctiveFacet(p)},getWidgetState:function(e,t){var n=t.searchParameters,r=this._getRefinedStar(n);return"number"!=typeof r?e:D({},e,{ratingMenu:D({},e.ratingMenu,L({},p,r))})},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.ratingMenu&&n.ratingMenu[p],i=e.clearRefinements(p).addDisjunctiveFacet(p);return r?Ie({start:Number(r),end:v+1}).reduce(function(e,t){return e.addDisjunctiveFacetRefinement(p,t)},i):i.setQueryParameters({disjunctiveFacetsRefinements:D({},i.disjunctiveFacetsRefinements,L({},p,[]))})},_toggleRefinement:function(e,t){d("click",t);var n=this._getRefinedStar(e.state)===Number(t);if(e.removeDisjunctiveFacetRefinement(p),!n)for(var r=Number(t);r<=v;++r)e.addDisjunctiveFacetRefinement(p,r);e.search()},_getRefinedStar:function(e){var t=e.getDisjunctiveRefinements(p);if(t.length)return Math.min.apply(Math,_(t.map(Number)))}}}}var pr=Ae({name:"stats",connector:!0});function vr(i){var e=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(i,pr()),function(){var r=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{};return{$$type:"ais.stats",init:function(e){var t=e.helper,n=e.instantSearchInstance;i({instantSearchInstance:n,hitsPerPage:t.state.hitsPerPage,nbHits:0,nbPages:0,page:t.state.page||0,processingTimeMS:-1,query:t.state.query||"",widgetParams:r},!0)},render:function(e){var t=e.results,n=e.instantSearchInstance;i({instantSearchInstance:n,hitsPerPage:t.hitsPerPage,nbHits:t.nbHits,nbPages:t.nbPages,page:t.page,processingTimeMS:t.processingTimeMS,query:t.query,widgetParams:r},!1)},dispose:function(){e()}}}}var gr=Ae({name:"toggle-refinement",connector:!0}),yr="ais.toggleRefinement",br=function(e){var o=e.instantSearchInstance,c=e.attribute,u=e.on,l=e.helper;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];if(1!==t.length){var r=t[0],i=t[1],a=t[2],s=void 0===a?"Filter Applied":a;"click"===r&&void 0!==u&&(i||o.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:yr,eventType:r,payload:{eventName:s,index:l.getIndex(),filters:u.map(function(e){return"".concat(c,":").concat(JSON.stringify(e))})}}))}else o.sendEventToInsights(t[0])}};function Rr(b){var r=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(b,gr()),function(){var d=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},m=d.attribute,e=d.on,t=void 0===e||e,n=d.off;if(!m)throw new Error(gr("The `attribute` option is required."));var p,v=void 0!==n,g=void 0!==t?Oe(t).map(Se):void 0,y=v?Oe(n).map(Se):void 0;return{$$type:yr,_toggleRefinement:function(t,e){var n=(1<arguments.length&&void 0!==e?e:{}).isRefined;n?(g.forEach(function(e){return t.removeDisjunctiveFacetRefinement(m,e)}),v&&y.forEach(function(e){return t.addDisjunctiveFacetRefinement(m,e)})):(p("click",n),v&&y.forEach(function(e){return t.removeDisjunctiveFacetRefinement(m,e)}),g.forEach(function(e){return t.addDisjunctiveFacetRefinement(m,e)})),t.search()},init:function(e){var t=this,r=e.state,n=e.helper,i=e.createURL,a=e.instantSearchInstance;p=br({instantSearchInstance:a,attribute:m,on:g,helper:n}),this._createURL=function(n){return function(){var e=n?g:y;e&&e.forEach(function(e){r.removeDisjunctiveFacetRefinement(m,e)});var t=n?y:g;return t&&t.forEach(function(e){r.addDisjunctiveFacetRefinement(m,e)}),i(r)}},this.toggleRefinement=function(e){t._toggleRefinement(n,e)};var s=g&&g.every(function(e){return r.isDisjunctiveFacetRefined(m,e)});if(v&&!s){var o=n.state.page;y&&y.forEach(function(e){return n.addDisjunctiveFacetRefinement(m,e)}),n.setPage(o)}var c={name:m,isRefined:s,count:null,onFacetValue:{isRefined:s,count:0},offFacetValue:{isRefined:v&&!s,count:0}};b({value:c,createURL:this._createURL(c.isRefined),refine:this.toggleRefinement,sendEvent:p,instantSearchInstance:a,widgetParams:d},!0)},render:function(e){var t=e.helper,n=e.results,r=e.state,i=e.instantSearchInstance,a=g&&g.every(function(e){return t.state.isDisjunctiveFacetRefined(m,e)}),s=Oe(void 0!==y&&y),o=n.getFacetValues(m)||[],c=g&&g.map(function(t){return ge(o,function(e){return e.name===ye(t)})}).filter(function(e){return void 0!==e}),u={isRefined:0<c.length&&c.every(function(e){return e.isRefined}),count:0===c.length?null:c.reduce(function(e,t){return e+t.count},0)},l=v?s.map(function(t){return ge(o,function(e){return e.name===ye(t)})}).filter(function(e){return void 0!==e}):[],h={isRefined:0<l.length&&l.every(function(e){return e.isRefined}),count:0===l.length?o.reduce(function(e,t){return e+t.count},0):l.reduce(function(e,t){return e+t.count},0)},f={name:m,isRefined:a,count:(a?h:u).count,onFacetValue:u,offFacetValue:h};b({value:f,state:r,createURL:this._createURL(f.isRefined),refine:this.toggleRefinement,sendEvent:p,helper:t,instantSearchInstance:i,widgetParams:d},!1)},dispose:function(e){var t=e.state;return r(),t.removeDisjunctiveFacet(m)},getWidgetState:function(e,t){var n=t.searchParameters,r=g&&g.every(function(e){return n.isDisjunctiveFacetRefined(m,e)});return r?D({},e,{toggle:D({},e.toggle,L({},m,r))}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=e.clearRefinements(m).addDisjunctiveFacet(m);return Boolean(n.toggle&&n.toggle[m])?(g&&g.forEach(function(e){r=r.addDisjunctiveFacetRefinement(m,e)}),r):v?(y&&y.forEach(function(e){r=r.addDisjunctiveFacetRefinement(m,e)}),r):r.setQueryParameters({disjunctiveFacetsRefinements:D({},e.disjunctiveFacetsRefinements,L({},m,[]))})}}}}function wr(l,e){var h=1<arguments.length&&void 0!==e?e:_e;Pe(l,Sr());var f={};return function(o){var e=o||{},t=e.attributes,n=e.separator,r=void 0===n?" > ":n,i=e.rootPath,a=void 0===i?null:i,s=e.transformItems,c=void 0===s?function(e){return e}:s;if(!t||!Array.isArray(t)||0===t.length)throw new Error(Sr("The `attributes` option expects an array of strings."));var u=Q(t,1)[0];return{$$type:"ais.breadcrumb",init:function(e){var n=e.createURL,r=e.helper,t=e.instantSearchInstance;f.createURL=function(e){if(!e){var t=r.getHierarchicalFacetBreadcrumb(u);if(0<t.length)return n(r.state.toggleFacetRefinement(u,t[0]))}return n(r.state.toggleFacetRefinement(u,e))},f.refine=function(e){if(e)r.toggleRefinement(u,e).search();else{var t=r.getHierarchicalFacetBreadcrumb(u);0<t.length&&r.toggleRefinement(u,t[0]).search()}},l({createURL:f.createURL,canRefine:!1,instantSearchInstance:t,items:[],refine:f.refine,widgetParams:o},!0)},render:function(e){var t=e.instantSearchInstance,n=e.results,r=Q(e.state.hierarchicalFacets,1)[0].name,i=n.getFacetValues(r,{}),a=Array.isArray(i.data)?i.data:[],s=c(function(n){return n.map(function(e,t){return{label:e.label,value:t+1===n.length?null:n[t+1].value}})}(function n(e){return e.reduce(function(e,t){return t.isRefined&&(e.push({label:t.name,value:t.path}),Array.isArray(t.data)&&(e=e.concat(n(t.data)))),e},[])}(a)));l({canRefine:0<s.length,createURL:f.createURL,instantSearchInstance:t,items:s,refine:f.refine,widgetParams:o},!1)},dispose:function(){h()},getWidgetSearchParameters:function(e){if(e.isHierarchicalFacet(u)){e.getHierarchicalFacetByName(u);return e}return e.addHierarchicalFacet({name:u,attributes:t,separator:r,rootPath:a})}}}}var Sr=Ae({name:"breadcrumb",connector:!0});function Pr(_,e){var r=1<arguments.length&&void 0!==e?e:_e;return Pe(_,_r()),function(){function u(e){return e.aroundLatLng&&function(e){var t=e.match(He);if(!t)throw new Error('Invalid value for "aroundLatLng" parameter: "'.concat(e,'"'));return{lat:parseFloat(t[1]),lng:parseFloat(t[2])}}(e.aroundLatLng)}function l(e){return e.insideBoundingBox&&De(e.insideBoundingBox)}function h(i){return function(e){var t=e.northEast,n=e.southWest,r=[t.lat,t.lng,n.lat,n.lng].join();i.setQueryParameter("insideBoundingBox",r).search(),P.hasMapMoveSinceLastRefine=!1,P.lastRefineBoundingBox=r}}function f(e){return function(){e.setQueryParameter("insideBoundingBox",void 0).search()}}function d(e){return function(){return Boolean(e.insideBoundingBox)}}function m(){return P.internalToggleRefineOnMapMove()}function p(e,t){return function(){P.isRefineOnMapMove=!P.isRefineOnMapMove,e(t)}}function v(){return P.isRefineOnMapMove}function g(){return P.internalSetMapMoveSinceLastRefine()}function y(t,n){return function(){var e=!0!==P.hasMapMoveSinceLastRefine;P.hasMapMoveSinceLastRefine=!0,e&&t(n)}}function b(){return P.hasMapMoveSinceLastRefine}var R,w=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},e=w.enableRefineOnMapMove,t=void 0===e||e,n=w.transformItems,S=void 0===n?function(e){return e}:n,P={isRefineOnMapMove:t,hasMapMoveSinceLastRefine:!1,lastRefinePosition:"",lastRefineBoundingBox:"",internalToggleRefineOnMapMove:_e,internalSetMapMoveSinceLastRefine:_e};return{$$type:Nr,init:function(e){var t=e.state,n=e.helper,r=e.instantSearchInstance;R=Ve({instantSearchInstance:r,index:n.getIndex(),widgetType:Nr}),P.internalToggleRefineOnMapMove=p(_e,e),P.internalSetMapMoveSinceLastRefine=y(_e,e),_({items:[],position:u(t),currentRefinement:l(t),refine:h(n),sendEvent:R,clearMapRefinement:f(n),isRefinedWithMap:d(t),toggleRefineOnMapMove:m,isRefineOnMapMove:v,setMapMoveSinceLastRefine:g,hasMapMoveSinceLastRefine:b,widgetParams:w,instantSearchInstance:r},!0)},render:function e(t){var n=t.results,r=t.helper,i=t.instantSearchInstance,a=r.state,s=Boolean(a.aroundLatLng)&&Boolean(P.lastRefinePosition)&&a.aroundLatLng!==P.lastRefinePosition,o=!a.insideBoundingBox&&Boolean(P.lastRefineBoundingBox)&&a.insideBoundingBox!==P.lastRefineBoundingBox;(s||o)&&(P.hasMapMoveSinceLastRefine=!1),P.lastRefinePosition=a.aroundLatLng||"",P.lastRefineBoundingBox=a.insideBoundingBox||"",P.internalToggleRefineOnMapMove=p(e,t),P.internalSetMapMoveSinceLastRefine=y(e,t);var c=S(n.hits.filter(function(e){return e._geoloc}));R("view",c),_({items:c,position:u(a),currentRefinement:l(a),refine:h(r),sendEvent:R,clearMapRefinement:f(r),isRefinedWithMap:d(a),toggleRefineOnMapMove:m,isRefineOnMapMove:v,setMapMoveSinceLastRefine:g,hasMapMoveSinceLastRefine:b,widgetParams:w,instantSearchInstance:i},!1)},dispose:function(e){var t=e.state;return r(),t.setQueryParameter("insideBoundingBox",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.insideBoundingBox;return!n||e&&e.geoSearch&&e.geoSearch.boundingBox===n?e:D({},e,{geoSearch:{boundingBox:n}})},getWidgetSearchParameters:function(e,t){var n=t.uiState;return n&&n.geoSearch?e.setQueryParameter("insideBoundingBox",n.geoSearch.boundingBox):e.setQueryParameter("insideBoundingBox",void 0)}}}}var _r=Ae({name:"geo-search",connector:!0}),Nr="ais.geoSearch",xr=Ae({name:"powered-by",connector:!0});function Fr(r){var i=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;Pe(r,xr());var a="https://www.algolia.com/?utm_source=instantsearch.js&utm_medium=website&"+"utm_content=".concat("undefined"!=typeof window&&window.location?window.location.hostname:"","&")+"utm_campaign=poweredby";return function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.url,n=void 0===t?a:t;return{$$type:"ais.poweredBy",init:function(){r({url:n,widgetParams:e},!0)},render:function(){r({url:n,widgetParams:e},!1)},dispose:function(){i()}}}}var Ir=Ae({name:"configure",connector:!0});function Cr(e,t){return e.setQueryParameters(Object.keys(t.searchParameters).reduce(function(e,t){return D({},e,L({},t,void 0))},{}))}function Tr(e,t){var a=0<arguments.length&&void 0!==e?e:_e,n=1<arguments.length&&void 0!==t?t:_e;return function(i){if(!i||!Fe(i.searchParameters))throw new Error(Ir("The `searchParameters` option expects an object."));var r={};return{$$type:"ais.configure",init:function(e){var t=e.instantSearchInstance,n=e.helper;r.refine=function(r){return function(e){var t=Cr(r.state,i),n=je(t,new ae.SearchParameters(e));r.setState(n).search(),i.searchParameters=e}}(n),a({refine:r.refine,instantSearchInstance:t,widgetParams:i},!0)},render:function(e){var t=e.instantSearchInstance;a({refine:r.refine,instantSearchInstance:t,widgetParams:i},!1)},dispose:function(e){var t=e.state;return n(),Cr(t,i)},getWidgetSearchParameters:function(e,t){var n=t.uiState;return je(e,new ae.SearchParameters(D({},n.configure,{},i.searchParameters)))},getWidgetState:function(e){return D({},e,{configure:D({},e.configure,{},i.searchParameters)})}}}}var Er=Ae({name:"configure-related-items",connector:!0});function kr(e){var t=e.attributeName,n=e.attributeValue,r=e.attributeScore;return"".concat(t,":").concat(n,"<score=").concat(r||1,">")}function Mr(c,u){return function(e){var t=e||{},a=t.hit,s=t.matchingPatterns,n=t.transformSearchParameters,r=void 0===n?function(e){return e}:n;if(!a)throw new Error(Er("The `hit` option is required."));if(!s)throw new Error(Er("The `matchingPatterns` option is required."));var i=Object.keys(s).reduce(function(e,t){var n=s[t],r=Ne(a,t),i=n.score;return Array.isArray(r)?[].concat(_(e),[r.map(function(e){return kr({attributeName:t,attributeValue:e,attributeScore:i})})]):"string"==typeof r?[].concat(_(e),[kr({attributeName:t,attributeValue:r,attributeScore:i})]):e},[]),o=D({},r(new ae.SearchParameters({sumOrFiltersScores:!0,facetFilters:["objectID:-".concat(a.objectID)],optionalFilters:i})));return D({},Tr(c,u)({searchParameters:o}),{$$type:"ais.configureRelatedItems"})}}var Lr=Ae({name:"autocomplete",connector:!0}),jr=Ae({name:"query-rules",connector:!0});function Or(e){var t=this.helper,n=this.initialRuleContexts,r=this.trackedFilters,i=this.transformRuleContexts,a=e.state,s=a.ruleContexts||[],o=function(e){var i=e.helper,a=e.sharedHelperState,s=e.trackedFilters;return Object.keys(s).reduce(function(e,t){var n=Re(i.lastResults||{},a).filter(function(e){return e.attribute===t}).map(function(e){return e.numericValue||e.name}),r=(0,s[t])(n);return[].concat(_(e),_(n.filter(function(e){return r.includes(e)}).map(function(e){return function(e){return e.replace(/[^a-z0-9-_]+/gi,"_")}("ais-".concat(t,"-").concat(e))})))},[])}({helper:t,sharedHelperState:a,trackedFilters:r}),c=i([].concat(_(n),_(o))).slice(0,10);Te(s,c)||t.overrideStateWithoutTriggeringChangeEvent(D({},a,{ruleContexts:c}))}function Ar(h,e){var f=1<arguments.length&&void 0!==e?e:_e;return Pe(h,jr()),function(a){var e=a||{},t=e.trackedFilters,i=void 0===t?{}:t,n=e.transformRuleContexts,s=void 0===n?function(e){return e}:n,r=e.transformItems,o=void 0===r?function(e){return e}:r;Object.keys(i).forEach(function(e){if("function"!=typeof i[e])throw new Error(jr("'The \"".concat(e,'" filter value in the `trackedFilters` option expects a function.')))});var c,u=0<Object.keys(i).length,l=[];return{$$type:"ais.queryRules",init:function(e){var t=e.helper,n=e.state,r=e.instantSearchInstance;l=n.ruleContexts||[],c=Or.bind({helper:t,initialRuleContexts:l,trackedFilters:i,transformRuleContexts:s}),u&&((function(e){return[e.disjunctiveFacetsRefinements,e.facetsRefinements,e.hierarchicalFacetsRefinements,e.numericRefinements].some(function(e){return Boolean(e&&0<Object.keys(e).length)})}(n)||Boolean(a.transformRuleContexts))&&c({state:n}),t.on("change",c)),h({items:[],instantSearchInstance:r,widgetParams:a},!0)},render:function(e){var t=e.results,n=e.instantSearchInstance,r=t.userData,i=o(void 0===r?[]:r);h({items:i,instantSearchInstance:n,widgetParams:a},!1)},dispose:function(e){var t=e.helper,n=e.state;return f(),u?(t.removeListener("change",c),n.setQueryParameter("ruleContexts",l)):n}}}}function Hr(e){function t(e){return{status:e,transcript:"",isSpeechFinal:!1,errorCode:void 0}}function n(e){p=D({},p,{},0<arguments.length&&void 0!==e?e:{}),d()}function r(e){n(t(0<arguments.length&&void 0!==e?e:"initial"))}function i(){n({status:"waiting"})}function a(e){n({status:"error",errorCode:e.error})}function s(e){n({status:"recognizing",transcript:e.results[0]&&e.results[0][0]&&e.results[0][0].transcript||"",isSpeechFinal:e.results[0]&&e.results[0].isFinal}),l&&p.transcript&&f(p.transcript)}function o(){p.errorCode||!p.transcript||l||f(p.transcript),"error"!==p.status&&n({status:"finished"})}function c(){u&&(u.stop(),u.removeEventListener("start",i),u.removeEventListener("error",a),u.removeEventListener("result",s),u.removeEventListener("end",o),u=void 0)}var u,l=e.searchAsYouSpeak,h=e.language,f=e.onQueryChange,d=e.onStateChange,m=window.webkitSpeechRecognition||window.SpeechRecognition,p=t("initial");return{getState:function(){return p},isBrowserSupported:function(){return Boolean(m)},isListening:function(){return"askingPermission"===p.status||"waiting"===p.status||"recognizing"===p.status},startListening:function(){(u=new m)&&(r("askingPermission"),u.interimResults=!0,h&&(u.lang=h),u.addEventListener("start",i),u.addEventListener("error",a),u.addEventListener("result",s),u.addEventListener("end",o),u.start())},stopListening:function(){c(),r("finished")},dispose:c}}function Dr(l,e){var h=1<arguments.length&&void 0!==e?e:_e;return Pe(l,Br()),function(u){function i(e){var t=e.isFirstRendering,n=e.instantSearchInstance,r=e.voiceSearchHelper,i=r.isBrowserSupported,a=r.isListening,s=r.startListening,o=r.stopListening,c=r.getState;l({isBrowserSupported:i(),isListening:a(),toggleListening:function(){i()&&(a()?o():s())},voiceListeningState:c(),widgetParams:u,instantSearchInstance:n},t)}var e=u.searchAsYouSpeak,a=void 0!==e&&e,s=u.language,o=u.additionalQueryParameters,t=u.createVoiceSearchHelper,c=void 0===t?Hr:t;return{$$type:"ais.voiceSearch",init:function(e){var t=this,n=e.helper,r=e.instantSearchInstance;this._refine=function(e){if(e!==n.state.query){var t=s?[s.split("-")[0]]:void 0;n.setQueryParameter("queryLanguages",t),"function"==typeof o&&n.setState(n.state.setQueryParameters(D({ignorePlurals:!0,removeStopWords:!0,optionalWords:e},o({query:e})))),n.setQuery(e).search()}},this._voiceSearchHelper=c({searchAsYouSpeak:a,language:s,onQueryChange:function(e){return t._refine(e)},onStateChange:function(){i({isFirstRendering:!1,instantSearchInstance:r,voiceSearchHelper:t._voiceSearchHelper})}}),i({isFirstRendering:!0,instantSearchInstance:r,voiceSearchHelper:this._voiceSearchHelper})},render:function(e){var t=e.instantSearchInstance;i({isFirstRendering:!1,instantSearchInstance:t,voiceSearchHelper:this._voiceSearchHelper})},dispose:function(e){var t=e.state;this._voiceSearchHelper.dispose(),h();var n=t;if("function"==typeof o){var r=o({query:""}),i=r?Object.keys(r).reduce(function(e,t){return e[t]=void 0,e},{}):{};n=t.setQueryParameters(D({queryLanguages:void 0,ignorePlurals:void 0,removeStopWords:void 0,optionalWords:void 0},i))}return n.setQueryParameter("query",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.query||"";return n?D({},e,{query:n}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState;return e.setQueryParameter("query",n.query||"")}}}}var Br=Ae({name:"voice-search",connector:!0}),Qr=Object.freeze({__proto__:null,connectClearRefinements:Vt,connectCurrentRefinements:zt,connectHierarchicalMenu:en,connectHits:tn,connectHitsWithInsights:Hn,connectHitsPerPage:An,connectInfiniteHits:Un,connectInfiniteHitsWithInsights:Vn,connectMenu:$n,connectNumericMenu:zn,connectPagination:tr,connectRange:ir,connectRefinementList:sr,connectSearchBox:cr,connectSortBy:lr,connectRatingMenu:mr,connectStats:vr,connectToggleRefinement:Rr,connectBreadcrumb:wr,connectGeoSearch:Pr,connectPoweredBy:Fr,connectConfigure:Tr,EXPERIMENTAL_connectConfigureRelatedItems:Mr,connectAutocomplete:function(u,e){var r=1<arguments.length&&void 0!==e?e:_e;return Pe(u,Lr()),function(s){var e=(s||{}).escapeHTML,o=void 0===e||e,c={};return{$$type:"ais.autocomplete",init:function(e){var t=e.instantSearchInstance,n=e.helper;c.refine=function(e){n.setQuery(e).search()},u({widgetParams:s,currentRefinement:n.state.query||"",indices:[],refine:c.refine,instantSearchInstance:t},!0)},render:function(e){var n=this,t=e.helper,r=e.scopedResults,i=e.instantSearchInstance,a=r.map(function(e){e.results.hits=o?it(e.results.hits):e.results.hits;var t=Ve({instantSearchInstance:i,index:e.results.index,widgetType:n.$$type});return t("view",e.results.hits),{indexId:e.indexId,indexName:e.results.index,hits:e.results.hits,results:e.results,sendEvent:t}});u({widgetParams:s,currentRefinement:t.state.query||"",indices:a,refine:c.refine,instantSearchInstance:i},!1)},getWidgetState:function(e,t){var n=t.searchParameters.query||"";return""===n||e&&e.query===n?e:D({},e,{query:n})},getWidgetSearchParameters:function(e,t){var n={query:t.uiState.query||""};return o?e.setQueryParameters(D({},n,{},et)):e.setQueryParameters(n)},dispose:function(e){var t=e.state;r();var n=t.setQueryParameter("query",void 0);return o?n.setQueryParameters(Object.keys(et).reduce(function(e,t){return D({},e,L({},t,void 0))},{})):n}}}},connectQueryRules:Ar,connectVoiceSearch:Dr}),qr=fe(function(e){function s(){for(var e=[],t=0;t<arguments.length;t++){var n=arguments[t];if(n){var r=typeof n;if("string"==r||"number"==r)e.push(n);else if(Array.isArray(n)&&n.length){var i=s.apply(null,n);i&&e.push(i)}else if("object"==r)for(var a in n)o.call(n,a)&&n[a]&&e.push(a)}}return e.join(" ")}var o;o={}.hasOwnProperty,e.exports?(s.default=s,e.exports=s):window.classNames=s}),Ur=function(){function e(){return k(this,e),B(this,O(e).apply(this,arguments))}return j(e,bn),M(e,[{key:"shouldComponentUpdate",value:function(e){return!Te(this.props.data,e.data)||this.props.templateKey!==e.templateKey||!Te(this.props.rootProps,e.rootProps)}},{key:"render",value:function(){var e=this.props.rootTagName,t=this.props.useCustomCompileOptions[this.props.templateKey]?this.props.templatesConfig.compileOptions:{},n=ve({templates:this.props.templates,templateKey:this.props.templateKey,compileOptions:t,helpers:this.props.templatesConfig.helpers,data:this.props.data,bindEvent:this.props.bindEvent});return null===n?null:vn(e,f({},this.props.rootProps,{dangerouslySetInnerHTML:{__html:n}}))}}]),e}();Ur.defaultProps={data:{},rootTagName:"div",useCustomCompileOptions:{},templates:{},templatesConfig:{}};function Vr(e){var t=e.hasRefinements,n=e.refine,r=e.cssClasses,i=e.templateProps;return vn("div",{className:r.root},vn(Ur,f({},i,{templateKey:"resetLabel",rootTagName:"button",rootProps:{className:qr(r.button,L({},r.disabledButton,!t)),onClick:n,disabled:!t},data:{hasRefinements:t}})))}function Wr(e){var t=e.items,n=e.cssClasses;return vn("div",{className:n.root},vn("ul",{className:n.list},t.map(function(t,e){return vn("li",{key:"".concat(t.indexName,"-").concat(t.attribute,"-").concat(e),className:n.item},vn("span",{className:n.label},function(e){return e.toString().charAt(0).toUpperCase()+e.toString().slice(1)}(t.label),":"),t.refinements.map(function(e){return vn("span",{key:function(e){var t=e.attribute,n=e.value;return[t,e.type,n,e.operator].map(function(e){return e}).filter(Boolean).join(":")}(e),className:n.category},vn("span",{className:n.categoryLabel},"query"===e.attribute?vn("q",null,e.label):e.label),vn("button",{className:n.delete,onClick:function(t){return function(e){ue(e)||(e.preventDefault(),t())}}(t.refine.bind(null,e))},"✕"))}))})))}function $r(e,t){var n=e.items,r=e.widgetParams;if(!t){var i=r.container,a=r.cssClasses;Ln(vn(Wr,{cssClasses:a,items:n}),i)}}function zr(e){var t=e.className,n=e.disabled;return vn("button",{className:t,onClick:e.onClick,disabled:n},e.children)}var Kr={resetLabel:"Clear refinements"},Jr=Ae({name:"clear-refinements"}),Yr=at("ClearRefinements"),Gr=Ae({name:"current-refinements"}),Xr=at("CurrentRefinements");zr.defaultProps={disabled:!1};function Zr(e){var t=e.classNameLabel,n=e.classNameInput,r=e.checked,i=e.onToggle,a=e.children;return vn("label",{className:t},vn("input",{className:n,type:"checkbox",checked:r,onChange:i}),a)}function ei(e){var t=e.cssClasses,n=e.enableRefine,r=e.enableRefineControl,i=e.enableClearMapRefinement,a=e.isRefineOnMapMove,s=e.isRefinedWithMap,o=e.hasMapMoveSinceLastRefine,c=e.onRefineToggle,u=e.onRefineClick,l=e.onClearClick,h=e.templateProps;return n&&vn("div",null,r&&vn("div",{className:t.control},a||!o?vn(Zr,{classNameLabel:qr(t.label,L({},t.selectedLabel,a)),classNameInput:t.input,checked:a,onToggle:c},vn(Ur,f({},h,{templateKey:"toggle",rootTagName:"span"}))):vn(zr,{className:t.redo,disabled:!o,onClick:u},vn(Ur,f({},h,{templateKey:"redo",rootTagName:"span"})))),!r&&!a&&vn("div",{className:t.control},vn(zr,{className:qr(t.redo,L({},t.disabledRedo,!o)),disabled:!o,onClick:u},vn(Ur,f({},h,{templateKey:"redo",rootTagName:"span"})))),i&&s&&vn(zr,{className:t.reset,onClick:l},vn(Ur,f({},h,{templateKey:"reset",rootTagName:"span"}))))}function ti(e){var t=e.refine,n=e.mapInstance;return t({northEast:n.getBounds().getNorthEast().toJSON(),southWest:n.getBounds().getSouthWest().toJSON()})}function ni(e,t){e.isUserInteraction=!1,t(),e.isUserInteraction=!0}function ri(e,t){var n=e.items,r=e.position,i=e.currentRefinement,a=e.refine,s=e.clearMapRefinement,o=e.toggleRefineOnMapMove,c=e.isRefineOnMapMove,u=e.setMapMoveSinceLastRefine,l=e.hasMapMoveSinceLastRefine,h=e.isRefinedWithMap,f=e.widgetParams,d=e.instantSearchInstance,m=f.container,p=f.googleReference,v=f.cssClasses,g=f.templates,y=f.initialZoom,b=f.initialPosition,R=f.enableRefine,w=f.enableClearMapRefinement,S=f.enableRefineControl,P=f.mapOptions,_=f.createMarker,N=f.markerOptions,x=f.renderState;if(t){x.isUserInteraction=!0,x.isPendingRefine=!1,x.markers=[];var F=document.createElement("div");F.className=v.root,m.appendChild(F);var I=document.createElement("div");I.className=v.map,F.appendChild(I);var C=document.createElement("div");C.className=v.tree,F.appendChild(C),x.mapInstance=new p.maps.Map(I,D({mapTypeControl:!1,fullscreenControl:!1,streetViewControl:!1,clickableIcons:!1,zoomControlOptions:{position:p.maps.ControlPosition.LEFT_TOP}},P));return p.maps.event.addListenerOnce(x.mapInstance,"idle",function(){function e(){x.isUserInteraction&&R&&(u(),c()&&(x.isPendingRefine=!0))}x.mapInstance.addListener("center_changed",e),x.mapInstance.addListener("zoom_changed",e),x.mapInstance.addListener("dragstart",e),x.mapInstance.addListener("idle",function(){x.isUserInteraction&&x.isPendingRefine&&(x.isPendingRefine=!1,ti({mapInstance:x.mapInstance,refine:a}))})}),void(x.templateProps=he({templatesConfig:d.templatesConfig,templates:g}))}var T=n.map(function(e){return e.objectID}),E=Q(function(e,a){return e.reduce(function(e,t){var n=Q(e,2),r=n[0],i=n[1];return a.includes(t.__id)?[r.concat(t),i]:[r,i.concat(t)]},[[],[]])}(x.markers,T),2),k=E[0],M=E[1],L=k.map(function(e){return e.__id}),j=n.filter(function(e){return!L.includes(e.objectID)});M.forEach(function(e){return e.setMap(null)}),x.markers=k.concat(j.map(function(n){var r=_({map:x.mapInstance,item:n});return Object.keys(N.events).forEach(function(t){r.addListener(t,function(e){N.events[t]({map:x.mapInstance,event:e,item:n,marker:r})})}),r}));var O=!l(),A=i?0:null,H=!i&&Boolean(x.markers.length)?function(e,t){var n=t.reduce(function(e,t){return e.extend(t.getPosition())},new e.maps.LatLngBounds);return{northEast:n.getNorthEast().toJSON(),southWest:n.getSouthWest().toJSON()}}(p,x.markers):i;H&&O?ni(x,function(){x.mapInstance.fitBounds(new p.maps.LatLngBounds(H.southWest,H.northEast),A)}):O&&ni(x,function(){x.mapInstance.setCenter(r||b),x.mapInstance.setZoom(y)}),Ln(vn(ei,{cssClasses:v,enableRefine:R,enableRefineControl:S,enableClearMapRefinement:w,isRefineOnMapMove:c(),isRefinedWithMap:h(),hasMapMoveSinceLastRefine:l(),onRefineToggle:o,onRefineClick:function(){return ti({mapInstance:x.mapInstance,refine:a})},onClearClick:s,templateProps:x.templateProps}),m.querySelector(".".concat(v.tree)))}var ii={HTMLMarker:"<p>Your custom HTML Marker</p>",reset:"Clear the map refinement",toggle:"Search as I move the map",redo:"Redo search here"},ai=Ae({name:"geo-search"}),si=at("GeoSearch");function oi(e){var t=e.className,n=e.handleClick,r=e.facetValueToRefine,i=e.isRefined,a=e.templateProps,s=e.templateKey,o=e.templateData,c=e.subItems;return vn("li",{className:t,onClick:function(e){n({facetValueToRefine:r,isRefined:i,originalEvent:e})}},vn(Ur,f({},a,{templateKey:s,data:o})),c)}var ci=function(){function i(){var e,s;k(this,i);for(var t=arguments.length,n=new Array(t),r=0;r<t;r++)n[r]=arguments[r];return L(H(s=B(this,(e=O(i)).call.apply(e,[this].concat(n)))),"state",{query:s.props.query,focused:!1}),L(H(s),"onInput",function(e){var t=s.props,n=t.searchAsYouType,r=t.refine,i=t.onChange,a=e.target.value;n&&r(a),s.setState({query:a}),i(e)}),L(H(s),"onSubmit",function(e){var t=s.props,n=t.searchAsYouType,r=t.refine,i=t.onSubmit;return e.preventDefault(),e.stopPropagation(),s.input.blur(),n||r(s.state.query),i(e),!1}),L(H(s),"onReset",function(e){var t=s.props,n=t.refine,r=t.onReset;s.input.focus(),n(""),s.setState({query:""}),r(e)}),L(H(s),"onBlur",function(){s.setState({focused:!1})}),L(H(s),"onFocus",function(){s.setState({focused:!0})}),s}return j(i,bn),M(i,[{key:"resetInput",value:function(){this.setState({query:""})}},{key:"componentWillReceiveProps",value:function(e){this.state.focused||e.query===this.state.query||this.setState({query:e.query})}},{key:"render",value:function(){var t=this,e=this.props,n=e.cssClasses,r=e.placeholder,i=e.autofocus,a=e.showSubmit,s=e.showReset,o=e.showLoadingIndicator,c=e.templates,u=e.isSearchStalled;return vn("div",{className:n.root},vn("form",{action:"",role:"search",className:n.form,noValidate:!0,onSubmit:this.onSubmit,onReset:this.onReset},vn("input",{ref:function(e){return t.input=e},value:this.state.query,disabled:this.props.disabled,className:n.input,type:"search",placeholder:r,autoFocus:i,autoComplete:"off",autoCorrect:"off",autoCapitalize:"off",spellCheck:"false",maxLength:512,onInput:this.onInput,onBlur:this.onBlur,onFocus:this.onFocus}),vn(Ur,{templateKey:"submit",rootTagName:"button",rootProps:{className:n.submit,type:"submit",title:"Submit the search query.",hidden:!a},templates:c,data:{cssClasses:n}}),vn(Ur,{templateKey:"reset",rootTagName:"button",rootProps:{className:n.reset,type:"reset",title:"Clear the search query.",hidden:!(s&&this.state.query.trim()&&!u)},templates:c,data:{cssClasses:n}}),o&&vn(Ur,{templateKey:"loadingIndicator",rootTagName:"span",rootProps:{className:n.loadingIndicator,hidden:!u},templates:c,data:{cssClasses:n}})))}}]),i}();L(ci,"defaultProps",{query:"",showSubmit:!0,showReset:!0,showLoadingIndicator:!0,autofocus:!1,searchAsYouType:!0,isSearchStalled:!1,disabled:!1,onChange:_e,onSubmit:_e,onReset:_e,refine:_e});var ui=function(){function c(e){var t;return k(this,c),(t=B(this,O(c).call(this,e))).handleItemClick=t.handleItemClick.bind(H(t)),t}return j(c,bn),M(c,[{key:"shouldComponentUpdate",value:function(e,t){var n=this.state!==t,r=!Te(this.props.facetValues,e.facetValues);return n||r}},{key:"refine",value:function(e,t){this.props.toggleRefinement(e,t)}},{key:"_generateFacetItem",value:function(e){var t,n,r=e.data&&0<e.data.length;if(r){var i=this.props.cssClasses,a=(i.root,A(i,["root"]));n=vn(c,f({},this.props,{cssClasses:a,depth:this.props.depth+1,facetValues:e.data,showMore:!1,className:this.props.cssClasses.childList}))}var s=D({},e,{url:this.props.createURL(e.value),attribute:this.props.attribute,cssClasses:this.props.cssClasses,isFromSearch:this.props.isFromSearch}),o=e.value;return void 0!==e.isRefined&&(o+="/".concat(e.isRefined)),void 0!==e.count&&(o+="/".concat(e.count)),vn(oi,{templateKey:"item",key:o,facetValueToRefine:e.value,handleClick:this.handleItemClick,isRefined:e.isRefined,className:qr(this.props.cssClasses.item,(t={},L(t,this.props.cssClasses.selectedItem,e.isRefined),L(t,this.props.cssClasses.disabledItem,!e.count),L(t,this.props.cssClasses.parentItem,r),t)),subItems:n,templateData:s,templateProps:this.props.templateProps})}},{key:"handleItemClick",value:function(e){var t=e.facetValueToRefine,n=e.originalEvent,r=e.isRefined;if(!(ue(n)||r&&n.target.parentNode.querySelector('input[type="radio"]:checked')))if("INPUT"!==n.target.tagName){for(var i=n.target;i!==n.currentTarget;){if("LABEL"===i.tagName&&(i.querySelector('input[type="checkbox"]')||i.querySelector('input[type="radio"]')))return;"A"===i.tagName&&i.href&&n.preventDefault(),i=i.parentNode}n.stopPropagation(),this.refine(t,r)}else this.refine(t,r)}},{key:"componentWillReceiveProps",value:function(e){this.searchBox&&!e.isFromSearch&&this.searchBox.resetInput()}},{key:"refineFirstValue",value:function(){var e=this.props.facetValues[0];if(e){var t=e.value;this.props.toggleRefinement(t)}}},{key:"render",value:function(){var t=this,e=qr(this.props.cssClasses.list,L({},"".concat(this.props.cssClasses.depth).concat(this.props.depth),this.props.cssClasses.depth)),n=qr(this.props.cssClasses.showMore,L({},this.props.cssClasses.disabledShowMore,!(!0===this.props.showMore&&this.props.canToggleShowMore))),r=!0===this.props.showMore&&vn(Ur,f({},this.props.templateProps,{templateKey:"showMoreText",rootTagName:"button",rootProps:{className:n,disabled:!this.props.canToggleShowMore,onClick:this.props.toggleShowMore},data:{isShowingMore:this.props.isShowingMore}})),i=!0!==this.props.searchIsAlwaysActive&&!(this.props.isFromSearch||!this.props.hasExhaustiveItems),a=this.props.searchFacetValues&&vn("div",{className:this.props.cssClasses.searchBox},vn(ci,{ref:function(e){return t.searchBox=e},placeholder:this.props.searchPlaceholder,disabled:i,cssClasses:this.props.cssClasses.searchable,templates:this.props.templateProps.templates,onChange:function(e){return t.props.searchFacetValues(e.target.value)},onReset:function(){return t.props.searchFacetValues("")},onSubmit:function(){return t.refineFirstValue()},searchAsYouType:!1})),s=this.props.facetValues&&0<this.props.facetValues.length&&vn("ul",{className:e},this.props.facetValues.map(this._generateFacetItem,this)),o=this.props.searchFacetValues&&this.props.isFromSearch&&0===this.props.facetValues.length&&vn(Ur,f({},this.props.templateProps,{templateKey:"searchableNoResults",rootProps:{className:this.props.cssClasses.noResults}}));return vn("div",{className:qr(this.props.cssClasses.root,L({},this.props.cssClasses.noRefinementRoot,!this.props.facetValues||0===this.props.facetValues.length),this.props.className)},this.props.children,a,s,o,r)}}]),c}();ui.defaultProps={cssClasses:{},depth:0};var li={item:'<a class="{{cssClasses.link}}" href="{{url}}"><span class="{{cssClasses.label}}">{{label}}</span><span class="{{cssClasses.count}}">{{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}}</span></a>',showMoreText:"\n    {{#isShowingMore}}\n      Show less\n    {{/isShowingMore}}\n    {{^isShowingMore}}\n      Show more\n    {{/isShowingMore}}\n  "},hi=Ae({name:"hierarchical-menu"}),fi=at("HierarchicalMenu");function di(e){var t=e.results,n=e.hits,r=e.bindEvent,i=e.cssClasses,a=e.templateProps;return 0===t.hits.length?vn(Ur,f({},a,{templateKey:"empty",rootProps:{className:qr(i.root,i.emptyRoot)},data:t})):vn("div",{className:i.root},vn("ol",{className:i.list},n.map(function(e,t){return vn(Ur,f({},a,{templateKey:"item",rootTagName:"li",rootProps:{className:i.item},key:e.objectID,data:D({},e,{__hitIndex:t}),bindEvent:r}))})))}di.defaultProps={results:{hits:[]},hits:[]};var mi={empty:"No results",item:function(e){return JSON.stringify(e,null,2)}},pi=Ae({name:"hits"}),vi=at("Hits"),gi=On(di);function yi(e){var t=e.currentValue,n=e.options,r=e.cssClasses,i=e.setValue;return vn("select",{className:qr(r.select),onChange:function(e){return i(e.target.value)},value:"".concat(t)},n.map(function(e){return vn("option",{className:qr(r.option),key:e.label+e.value,value:"".concat(e.value)},e.label)}))}var bi=Ae({name:"hits-per-page"}),Ri=at("HitsPerPage"),wi={empty:"No results",showPreviousText:"Show previous results",showMoreText:"Show more results",item:function(e){return JSON.stringify(e,null,2)}},Si=Ae({name:"infinite-hits"}),Pi=at("InfiniteHits"),_i=On(function(e){var t=e.results,n=e.hits,r=e.bindEvent,i=e.hasShowPrevious,a=e.showPrevious,s=e.showMore,o=e.isFirstPage,c=e.isLastPage,u=e.cssClasses,l=e.templateProps;return 0===t.hits.length?vn(Ur,f({},l,{templateKey:"empty",rootProps:{className:qr(u.root,u.emptyRoot)},data:t})):vn("div",{className:u.root},i&&vn(Ur,f({},l,{templateKey:"showPreviousText",rootTagName:"button",rootProps:{className:qr(u.loadPrevious,L({},u.disabledLoadPrevious,o)),disabled:o,onClick:a}})),vn("ol",{className:u.list},n.map(function(e,t){return vn(Ur,f({},l,{templateKey:"item",rootTagName:"li",rootProps:{className:u.item},key:e.objectID,data:D({},e,{__hitIndex:t}),bindEvent:r}))})),vn(Ur,f({},l,{templateKey:"showMoreText",rootTagName:"button",rootProps:{className:qr(u.loadMore,L({},u.disabledLoadMore,c)),disabled:c,onClick:s}})))}),Ni={item:'<a class="{{cssClasses.link}}" href="{{url}}"><span class="{{cssClasses.label}}">{{label}}</span><span class="{{cssClasses.count}}">{{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}}</span></a>',showMoreText:"\n    {{#isShowingMore}}\n      Show less\n    {{/isShowingMore}}\n    {{^isShowingMore}}\n      Show more\n    {{/isShowingMore}}\n  "},xi=Ae({name:"menu"}),Fi=at("Menu");var Ii={reset:'\n<svg class="{{cssClasses.resetIcon}}" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20" width="10" height="10">\n  <path d="M8.114 10L.944 2.83 0 1.885 1.886 0l.943.943L10 8.113l7.17-7.17.944-.943L20 1.886l-.943.943-7.17 7.17 7.17 7.17.943.944L18.114 20l-.943-.943-7.17-7.17-7.17 7.17-.944.943L0 18.114l.943-.943L8.113 10z"></path>\n</svg>\n  ',submit:'\n<svg class="{{cssClasses.submitIcon}}" xmlns="http://www.w3.org/2000/svg" width="10" height="10" viewBox="0 0 40 40">\n  <path d="M26.804 29.01c-2.832 2.34-6.465 3.746-10.426 3.746C7.333 32.756 0 25.424 0 16.378 0 7.333 7.333 0 16.378 0c9.046 0 16.378 7.333 16.378 16.378 0 3.96-1.406 7.594-3.746 10.426l10.534 10.534c.607.607.61 1.59-.004 2.202-.61.61-1.597.61-2.202.004L26.804 29.01zm-10.426.627c7.323 0 13.26-5.936 13.26-13.26 0-7.32-5.937-13.257-13.26-13.257C9.056 3.12 3.12 9.056 3.12 16.378c0 7.323 5.936 13.26 13.258 13.26z"></path>\n</svg>\n  ',loadingIndicator:'\n<svg class="{{cssClasses.loadingIcon}}" width="16" height="16" viewBox="0 0 38 38" xmlns="http://www.w3.org/2000/svg" stroke="#444">\n  <g fill="none" fillRule="evenodd">\n    <g transform="translate(1 1)" strokeWidth="2">\n      <circle strokeOpacity=".5" cx="18" cy="18" r="18" />\n      <path d="M36 18c0-9.94-8.06-18-18-18">\n        <animateTransform\n          attributeName="transform"\n          type="rotate"\n          from="0 18 18"\n          to="360 18 18"\n          dur="1s"\n          repeatCount="indefinite"\n        />\n      </path>\n    </g>\n  </g>\n</svg>\n  '},Ci={item:'<label class="{{cssClasses.label}}">\n  <input type="checkbox"\n         class="{{cssClasses.checkbox}}"\n         value="{{value}}"\n         {{#isRefined}}checked{{/isRefined}} />\n  <span class="{{cssClasses.labelText}}">{{#isFromSearch}}{{{highlighted}}}{{/isFromSearch}}{{^isFromSearch}}{{highlighted}}{{/isFromSearch}}</span>\n  <span class="{{cssClasses.count}}">{{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}}</span>\n</label>',showMoreText:"\n    {{#isShowingMore}}\n      Show less\n    {{/isShowingMore}}\n    {{^isShowingMore}}\n      Show more\n    {{/isShowingMore}}\n    ",searchableNoResults:"No results",searchableReset:Ii.reset,searchableSubmit:Ii.submit,searchableLoadingIndicator:Ii.loadingIndicator},Ti=Ae({name:"refinement-list"}),Ei=at("RefinementList"),ki=at("SearchBox");var Mi={item:'<label class="{{cssClasses.label}}">\n  <input type="radio" class="{{cssClasses.radio}}" name="{{attribute}}"{{#isRefined}} checked{{/isRefined}} />\n  <span class="{{cssClasses.labelText}}">{{label}}</span>\n</label>'},Li=Ae({name:"numeric-menu"}),ji=at("NumericMenu");function Oi(e){var t=e.cssClasses,n=e.label,r=e.ariaLabel,i=e.url,a=e.isDisabled,s=e.handleClick,o=e.pageNumber;return vn("li",{className:t.item},a?vn("span",{className:t.link,dangerouslySetInnerHTML:{__html:n}}):vn("a",{className:t.link,"aria-label":r,href:i,onClick:function(e){return s(o,e)},dangerouslySetInnerHTML:{__html:n}}))}var Ai=function(){function a(){var e,n;k(this,a);for(var t=arguments.length,r=new Array(t),i=0;i<t;i++)r[i]=arguments[i];return L(H(n=B(this,(e=O(a)).call.apply(e,[this].concat(r)))),"handleClick",function(e,t){ue(t)||(t.preventDefault(),n.props.setCurrentPage(e))}),n}return j(a,bn),M(a,[{key:"pageLink",value:function(e){var t=e.label,n=e.ariaLabel,r=e.pageNumber,i=e.additionalClassName,a=void 0===i?null:i,s=e.isDisabled,o=void 0!==s&&s,c=e.isSelected,u=void 0!==c&&c,l=e.createURL,h={item:qr(this.props.cssClasses.item,a),link:this.props.cssClasses.link};o?h.item=qr(h.item,this.props.cssClasses.disabledItem):u&&(h.item=qr(h.item,this.props.cssClasses.selectedItem));var f=l&&!o?l(r):"#";return vn(Oi,{ariaLabel:n,cssClasses:h,handleClick:this.handleClick,isDisabled:o,key:t+r+n,label:t,pageNumber:r,url:f})}},{key:"previousPageLink",value:function(e){var t=e.isFirstPage,n=e.currentPage,r=e.createURL;return this.pageLink({ariaLabel:"Previous",additionalClassName:this.props.cssClasses.previousPageItem,isDisabled:t,label:this.props.templates.previous,pageNumber:n-1,createURL:r})}},{key:"nextPageLink",value:function(e){var t=e.isLastPage,n=e.currentPage,r=e.createURL;return this.pageLink({ariaLabel:"Next",additionalClassName:this.props.cssClasses.nextPageItem,isDisabled:t,label:this.props.templates.next,pageNumber:n+1,createURL:r})}},{key:"firstPageLink",value:function(e){var t=e.isFirstPage,n=e.createURL;return this.pageLink({ariaLabel:"First",additionalClassName:this.props.cssClasses.firstPageItem,isDisabled:t,label:this.props.templates.first,pageNumber:0,createURL:n})}},{key:"lastPageLink",value:function(e){var t=e.isLastPage,n=e.nbPages,r=e.createURL;return this.pageLink({ariaLabel:"Last",additionalClassName:this.props.cssClasses.lastPageItem,isDisabled:t,label:this.props.templates.last,pageNumber:n-1,createURL:r})}},{key:"pages",value:function(e){var t=this,n=e.currentPage,r=e.pages,i=e.createURL;return r.map(function(e){return t.pageLink({ariaLabel:e+1,additionalClassName:t.props.cssClasses.pageItem,isSelected:e===n,label:e+1,pageNumber:e,createURL:i})})}},{key:"render",value:function(){return vn("div",{className:qr(this.props.cssClasses.root,L({},this.props.cssClasses.noRefinementRoot,this.props.nbPages<=1))},vn("ul",{className:this.props.cssClasses.list},this.props.showFirst&&this.firstPageLink(this.props),this.props.showPrevious&&this.previousPageLink(this.props),this.pages(this.props),this.props.showNext&&this.nextPageLink(this.props),this.props.showLast&&this.lastPageLink(this.props)))}}]),a}();Ai.defaultProps={nbHits:0,currentPage:0,nbPages:0};var Hi=Ae({name:"pagination"}),Di=at("Pagination"),Bi={previous:"‹",next:"›",first:"«",last:"»"};var Qi=function(){function t(e){var n;return k(this,t),L(H(n=B(this,O(t).call(this,e))),"onInput",function(t){return function(e){n.setState(L({},t,e.currentTarget.value))}}),L(H(n),"onSubmit",function(e){e.preventDefault(),n.props.refine([n.state.min&&Number(n.state.min),n.state.max&&Number(n.state.max)])}),n.state={min:e.values.min,max:e.values.max},n}return j(t,bn),M(t,[{key:"componentWillReceiveProps",value:function(e){this.setState({min:e.values.min,max:e.values.max})}},{key:"render",value:function(){var e=this.state,t=e.min,n=e.max,r=this.props,i=r.min,a=r.max,s=r.step,o=r.cssClasses,c=r.templateProps,u=a<=i,l=Boolean(t||n);return vn("div",{className:qr(o.root,L({},o.noRefinement,!l))},vn("form",{className:o.form,onSubmit:this.onSubmit},vn("label",{className:o.label},vn("input",{className:qr(o.input,o.inputMin),type:"number",min:i,max:a,step:s,value:null!=t?t:"",onInput:this.onInput("min"),placeholder:i,disabled:u})),vn(Ur,f({},c,{templateKey:"separatorText",rootTagName:"span",rootProps:{className:o.separator}})),vn("label",{className:o.label},vn("input",{className:qr(o.input,o.inputMax),type:"number",min:i,max:a,step:s,value:null!=n?n:"",onInput:this.onInput("max"),placeholder:a,disabled:u})),vn(Ur,f({},c,{templateKey:"submitText",rootTagName:"button",rootProps:{type:"submit",className:o.submit,disabled:u}}))))}}]),t}(),qi=Ae({name:"range-input"}),Ui=at("RangeInput");var Vi=Ae({name:"search-box"}),Wi=at("SearchBox");var $i=40,zi=35,Ki=27,Ji=36,Yi=37,Gi=34,Xi=33,Zi=39,ea=38,ta=100;function na(e,t,n){return(e-t)/(n-t)*100}function ra(e,t,n){var r=e/100;return 0===e?t:100===e?n:Math.round((n-t)*r+t)}function ia(e){return["rheostat","vertical"===e.orientation?"rheostat-vertical":"rheostat-horizontal"].concat(e.className.split(" ")).join(" ")}function aa(e){return Number(e.currentTarget.getAttribute("data-handle-key"))}function sa(e){e.stopPropagation(),e.preventDefault()}var oa=function(){function e(){return k(this,e),B(this,O(e).apply(this,arguments))}return j(e,bn),M(e,[{key:"render",value:function(){return vn("button",f({},this.props,{type:"button"}))}}]),e}(),ca=vn("div",{className:"rheostat-background"}),ua=function(){function n(e){var t;return k(this,n),L(H(t=B(this,O(n).call(this,e))),"state",{className:ia(t.props),handlePos:t.props.values.map(function(e){return na(e,t.props.min,t.props.max)}),handleDimensions:0,mousePos:null,sliderBox:{},slidingIndex:null,values:t.props.values}),t.getPublicState=t.getPublicState.bind(H(t)),t.getSliderBoundingBox=t.getSliderBoundingBox.bind(H(t)),t.getProgressStyle=t.getProgressStyle.bind(H(t)),t.getMinValue=t.getMinValue.bind(H(t)),t.getMaxValue=t.getMaxValue.bind(H(t)),t.getHandleDimensions=t.getHandleDimensions.bind(H(t)),t.getClosestSnapPoint=t.getClosestSnapPoint.bind(H(t)),t.getSnapPosition=t.getSnapPosition.bind(H(t)),t.getNextPositionForKey=t.getNextPositionForKey.bind(H(t)),t.getNextState=t.getNextState.bind(H(t)),t.handleClick=t.handleClick.bind(H(t)),t.getClosestHandle=t.getClosestHandle.bind(H(t)),t.setStartSlide=t.setStartSlide.bind(H(t)),t.startMouseSlide=t.startMouseSlide.bind(H(t)),t.startTouchSlide=t.startTouchSlide.bind(H(t)),t.handleMouseSlide=t.handleMouseSlide.bind(H(t)),t.handleTouchSlide=t.handleTouchSlide.bind(H(t)),t.handleSlide=t.handleSlide.bind(H(t)),t.endSlide=t.endSlide.bind(H(t)),t.handleKeydown=t.handleKeydown.bind(H(t)),t.validatePosition=t.validatePosition.bind(H(t)),t.validateValues=t.validateValues.bind(H(t)),t.canMove=t.canMove.bind(H(t)),t.fireChangeEvent=t.fireChangeEvent.bind(H(t)),t.slideTo=t.slideTo.bind(H(t)),t.updateNewValues=t.updateNewValues.bind(H(t)),t}return j(n,bn),M(n,[{key:"componentWillReceiveProps",value:function(n){var e=this.props,t=e.className,r=e.disabled,i=e.min,a=e.max,s=e.orientation,o=this.state,c=o.values,u=o.slidingIndex,l=n.min!==i||n.max!==a,h=c.length!==n.values.length||c.some(function(e,t){return n.values[t]!==e}),f=n.className!==t||n.orientation!==s,d=n.disabled&&!r;f&&this.setState({className:ia(n)}),(l||h)&&this.updateNewValues(n),d&&null!==u&&this.endSlide()}},{key:"getPublicState",value:function(){var e=this.props,t=e.min;return{max:e.max,min:t,values:this.state.values}}},{key:"getSliderBoundingBox",value:function(){var e=this.rheostat.getDOMNode?this.rheostat.getDOMNode():this.rheostat,t=e.getBoundingClientRect();return{height:t.height||e.clientHeight,left:t.left,top:t.top,width:t.width||e.clientWidth}}},{key:"getProgressStyle",value:function(e){var t=this.state.handlePos,n=t[e];if(0===e)return"vertical"===this.props.orientation?{height:"".concat(n,"%"),top:0}:{left:0,width:"".concat(n,"%")};var r=t[e-1],i=n-r;return"vertical"===this.props.orientation?{height:"".concat(i,"%"),top:"".concat(r,"%")}:{left:"".concat(r,"%"),width:"".concat(i,"%")}}},{key:"getMinValue",value:function(e){return this.state.values[e-1]?Math.max(this.props.min,this.state.values[e-1]):this.props.min}},{key:"getMaxValue",value:function(e){return this.state.values[e+1]?Math.min(this.props.max,this.state.values[e+1]):this.props.max}},{key:"getHandleDimensions",value:function(e,t){var n=e.currentTarget||null;return n?"vertical"===this.props.orientation?n.clientHeight/t.height*ta/2:n.clientWidth/t.width*ta/2:0}},{key:"getClosestSnapPoint",value:function(n){return this.props.snapPoints.length?this.props.snapPoints.reduce(function(e,t){return Math.abs(e-n)<Math.abs(t-n)?e:t}):n}},{key:"getSnapPosition",value:function(e){if(!this.props.snap)return e;var t=this.props,n=t.max,r=t.min,i=ra(e,r,n);return na(this.getClosestSnapPoint(i),r,n)}},{key:"getNextPositionForKey",value:function(e,t){var n,r=this.state,i=r.handlePos,a=r.values,s=this.props,o=s.max,c=s.min,u=s.snapPoints,l=this.props.snap,h=a[e],f=i[e],d=f,m=1;100<=o?f=Math.round(f):m=100/(o-c);var p=null;l&&(p=u.indexOf(this.getClosestSnapPoint(a[e])));var v=(L(n={},Yi,function(e){return-1*e}),L(n,Zi,function(e){return e}),L(n,ea,function(e){return e}),L(n,$i,function(e){return-1*e}),L(n,Gi,function(e){return 1<e?-e:-10*e}),L(n,Xi,function(e){return 1<e?e:10*e}),n);if(Object.prototype.hasOwnProperty.call(v,t))f+=v[t](m),l&&(d<f?p<u.length-1&&(h=u[p+1]):0<p&&(h=u[p-1]));else if(t===Ji)f=0,l&&(h=u[0]);else{if(t!==zi)return null;f=ta,l&&(h=u[u.length-1])}return l?na(h,c,o):f}},{key:"getNextState",value:function(n,e){var t=this.state.handlePos,r=this.props,i=r.max,a=r.min,s=this.validatePosition(n,e),o=t.map(function(e,t){return t===n?s:e});return{handlePos:o,values:o.map(function(e){return ra(e,a,i)})}}},{key:"getClosestHandle",value:function(r){var i=this.state.handlePos;return i.reduce(function(e,t,n){return Math.abs(i[n]-r)<Math.abs(i[e]-r)?n:e},0)}},{key:"setStartSlide",value:function(e,t,n){var r=this.getSliderBoundingBox();this.setState({handleDimensions:this.getHandleDimensions(e,r),mousePos:{x:t,y:n},sliderBox:r,slidingIndex:aa(e)})}},{key:"startMouseSlide",value:function(e){this.setStartSlide(e,e.clientX,e.clientY),"function"==typeof document.addEventListener?(document.addEventListener("mousemove",this.handleMouseSlide,!1),document.addEventListener("mouseup",this.endSlide,!1)):(document.attachEvent("onmousemove",this.handleMouseSlide),document.attachEvent("onmouseup",this.endSlide)),sa(e)}},{key:"startTouchSlide",value:function(e){if(!(1<e.changedTouches.length)){var t=e.changedTouches[0];this.setStartSlide(e,t.clientX,t.clientY),document.addEventListener("touchmove",this.handleTouchSlide,!1),document.addEventListener("touchend",this.endSlide,!1),this.props.onSliderDragStart&&this.props.onSliderDragStart(),sa(e)}}},{key:"handleMouseSlide",value:function(e){null!==this.state.slidingIndex&&(this.handleSlide(e.clientX,e.clientY),sa(e))}},{key:"handleTouchSlide",value:function(e){if(null!==this.state.slidingIndex)if(1<e.changedTouches.length)this.endSlide();else{var t=e.changedTouches[0];this.handleSlide(t.clientX,t.clientY),sa(e)}}},{key:"handleSlide",value:function(e,t){var n=this.state,r=n.slidingIndex,i=n.sliderBox,a="vertical"===this.props.orientation?(t-i.top)/i.height*ta:(e-i.left)/i.width*ta;this.slideTo(r,a),this.canMove(r,a)&&(this.setState({x:e,y:t}),this.props.onSliderDragMove&&this.props.onSliderDragMove())}},{key:"endSlide",value:function(){var e=this,t=this.state.slidingIndex;if(this.setState({slidingIndex:null}),"function"==typeof document.removeEventListener?(document.removeEventListener("mouseup",this.endSlide,!1),document.removeEventListener("touchend",this.endSlide,!1),document.removeEventListener("touchmove",this.handleTouchSlide,!1),document.removeEventListener("mousemove",this.handleMouseSlide,!1)):(document.detachEvent("onmousemove",this.handleMouseSlide),document.detachEvent("onmouseup",this.endSlide)),this.props.onSliderDragEnd&&this.props.onSliderDragEnd(),this.props.snap){var n=this.getSnapPosition(this.state.handlePos[t]);this.slideTo(t,n,function(){return e.fireChangeEvent()})}else this.fireChangeEvent()}},{key:"handleClick",value:function(e){var t=this;if(!e.target.getAttribute("data-handle-key")){var n=this.getSliderBoundingBox(),r=("vertical"===this.props.orientation?(e.clientY-n.top)/n.height:(e.clientX-n.left)/n.width)*ta,i=this.getClosestHandle(r),a=this.getSnapPosition(r);this.slideTo(i,a,function(){return t.fireChangeEvent()}),this.props.onClick&&this.props.onClick()}}},{key:"handleKeydown",value:function(e){var t=this,n=aa(e);if(e.keyCode!==Ki){var r=this.getNextPositionForKey(n,e.keyCode);null!==r&&(this.canMove(n,r)&&(this.slideTo(n,r,function(){return t.fireChangeEvent()}),this.props.onKeyPress&&this.props.onKeyPress()),sa(e))}else e.currentTarget.blur()}},{key:"validatePosition",value:function(e,t){var n=this.state,r=n.handlePos,i=n.handleDimensions;return Math.max(Math.min(t,void 0!==r[e+1]?r[e+1]-i:ta),void 0!==r[e-1]?r[e-1]+i:0)}},{key:"validateValues",value:function(e,t){var n=t||this.props,i=n.max,a=n.min;return e.map(function(e,t,n){var r=Math.max(Math.min(e,i),a);return n.length&&r<n[t-1]?n[t-1]:r})}},{key:"canMove",value:function(e,t){var n=this.state,r=n.handlePos,i=n.handleDimensions;return!(t<0)&&(!(ta<t)&&(!((void 0!==r[e+1]?r[e+1]-i:1/0)<t)&&!(t<(void 0!==r[e-1]?r[e-1]+i:-1/0))))}},{key:"fireChangeEvent",value:function(){var e=this.props.onChange;e&&e(this.getPublicState())}},{key:"slideTo",value:function(e,t,n){var r=this,i=this.getNextState(e,t);this.setState(i,function(){var e=r.props.onValuesUpdated;e&&e(r.getPublicState()),n&&n()})}},{key:"updateNewValues",value:function(e){var t=this;if(null===this.state.slidingIndex){var n=e.max,r=e.min,i=e.values,a=this.validateValues(i,e);this.setState({handlePos:a.map(function(e){return na(e,r,n)}),values:a},function(){return t.fireChangeEvent()})}}},{key:"render",value:function(){var r=this,e=this.props,t=e.children,i=e.disabled,a=e.handle,s=e.max,o=e.min,c=e.orientation,u=e.pitComponent,n=e.pitPoints,l=e.progressBar,h=this.state,f=h.className,d=h.handlePos,m=h.values;return vn("div",{className:f,ref:function(e){r.rheostat=e},onClick:!i&&this.handleClick,style:{position:"relative"}},ca,d.map(function(e,t){var n="vertical"===c?{top:"".concat(e,"%"),position:"absolute"}:{left:"".concat(e,"%"),position:"absolute"};return vn(a,{"aria-valuemax":r.getMaxValue(t),"aria-valuemin":r.getMinValue(t),"aria-valuenow":m[t],"aria-disabled":i,"data-handle-key":t,className:"rheostat-handle",key:"handle-".concat(t),onClick:r.killEvent,onKeyDown:!i&&r.handleKeydown,onMouseDown:!i&&r.startMouseSlide,onTouchStart:!i&&r.startTouchSlide,role:"slider",style:n,tabIndex:0})}),d.map(function(e,t,n){return 0===t&&1<n.length?null:vn(l,{className:"rheostat-progress",key:"progress-bar-".concat(t),style:r.getProgressStyle(t)})}),u&&n.map(function(e){var t=na(e,o,s),n="vertical"===c?{top:"".concat(t,"%"),position:"absolute"}:{left:"".concat(t,"%"),position:"absolute"};return vn(u,{key:"pit-".concat(e),style:n},e)}),t)}}]),n}();L(ua,"defaultProps",{className:"",children:null,disabled:!1,handle:oa,max:ta,min:0,onClick:null,onChange:null,onKeyPress:null,onSliderDragEnd:null,onSliderDragMove:null,onSliderDragStart:null,onValuesUpdated:null,orientation:"horizontal",pitComponent:null,pitPoints:[],progressBar:"div",snap:!1,snapPoints:[],values:[0]});function la(e){var t=e.style,n=e.children,r=Math.round(parseFloat(t.left)),i=[0,50,100].includes(r),a=Array.isArray(n)?n[0]:n,s=Math.round(100*parseInt(a,10))/100;return vn("div",{style:D({},t,{marginLeft:100===r?"-2px":0}),className:qr("rheostat-marker","rheostat-marker-horizontal",{"rheostat-marker-large":i})},i&&vn("div",{className:"rheostat-value"},s))}var ha=function(){function a(){var e,n;k(this,a);for(var t=arguments.length,r=new Array(t),i=0;i<t;i++)r[i]=arguments[i];return L(H(n=B(this,(e=O(a)).call.apply(e,[this].concat(r)))),"handleChange",function(e){var t=e.values;n.isDisabled||n.props.refine(t)}),L(H(n),"createHandleComponent",function(r){return function(e){var t=Math.round(100*parseFloat(e["aria-valuenow"]))/100,n=r&&r.format?r.format(t):t;return vn("div",f({},e,{className:qr(e.className,{"rheostat-handle-lower":0===e["data-handle-key"],"rheostat-handle-upper":1===e["data-handle-key"]})}),r&&vn("div",{className:"rheostat-tooltip"},n))}}),n}return j(a,bn),M(a,[{key:"computeDefaultPitPoints",value:function(e){var t=e.min,n=e.max,r=(n-t)/34;return[t].concat(_(Ie({end:33}).map(function(e){return t+r*(e+1)})),[n])}},{key:"computeSnapPoints",value:function(e){var t=e.min,n=e.max,r=e.step;if(r)return[].concat(_(Ie({start:t,end:n,step:r})),[n])}},{key:"render",value:function(){var e=this.props,t=e.tooltips,n=e.step,r=e.pips,i=e.values,a=e.cssClasses,s=this.isDisabled?{min:this.props.min,max:this.props.max+.001}:this.props,o=s.min,c=s.max,u=this.computeSnapPoints({min:o,max:c,step:n}),l=!1===r?[]:this.computeDefaultPitPoints({min:o,max:c});return vn("div",{className:qr(a.root,L({},a.disabledRoot,this.isDisabled))},vn(ua,{handle:this.createHandleComponent(t),onChange:this.handleChange,min:o,max:c,pitComponent:la,pitPoints:l,snap:!0,snapPoints:u,values:this.isDisabled?[o,c]:i,disabled:this.isDisabled}))}},{key:"isDisabled",get:function(){return this.props.min>=this.props.max}}]),a}(),fa=Ae({name:"range-slider"}),da=at("RangeSlider");var ma=Ae({name:"sort-by"}),pa=at("SortBy");var va={item:'{{#count}}<a class="{{cssClasses.link}}" aria-label="{{value}} & up" href="{{href}}">{{/count}}{{^count}}<div class="{{cssClasses.link}}" aria-label="{{value}} & up" disabled>{{/count}}\n  {{#stars}}<svg class="{{cssClasses.starIcon}} {{#.}}{{cssClasses.fullStarIcon}}{{/.}}{{^.}}{{cssClasses.emptyStarIcon}}{{/.}}" aria-hidden="true" width="24" height="24">\n    {{#.}}<use xlink:href="#ais-RatingMenu-starSymbol"></use>{{/.}}{{^.}}<use xlink:href="#ais-RatingMenu-starEmptySymbol"></use>{{/.}}\n  </svg>{{/stars}}\n  <span class="{{cssClasses.label}}">& Up</span>\n  {{#count}}<span class="{{cssClasses.count}}">{{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}}</span>{{/count}}\n{{#count}}</a>{{/count}}{{^count}}</div>{{/count}}'},ga=Ae({name:"rating-menu"}),ya=at("RatingMenu"),ba=vn("path",{d:"M12 .288l2.833 8.718h9.167l-7.417 5.389 2.833 8.718-7.416-5.388-7.417 5.388 2.833-8.718-7.416-5.389h9.167z"}),Ra=vn("path",{d:"M12 6.76l1.379 4.246h4.465l-3.612 2.625 1.379 4.246-3.611-2.625-3.612 2.625 1.379-4.246-3.612-2.625h4.465l1.38-4.246zm0-6.472l-2.833 8.718h-9.167l7.416 5.389-2.833 8.718 7.417-5.388 7.416 5.388-2.833-8.718 7.417-5.389h-9.167l-2.833-8.718z"});function wa(e){var t=e.nbHits,n=e.hitsPerPage,r=e.nbPages,i=e.page,a=e.processingTimeMS,s=e.query,o=e.templateProps,c=e.cssClasses;return vn("div",{className:c.root},vn(Ur,f({},o,{templateKey:"text",rootTagName:"span",rootProps:{className:c.text},data:{hasManyResults:1<t,hasNoResults:0===t,hasOneResult:1===t,hitsPerPage:n,nbHits:t,nbPages:r,page:i,processingTimeMS:a,query:s,cssClasses:c}})))}var Sa={text:"{{#hasNoResults}}No results{{/hasNoResults}}\n    {{#hasOneResult}}1 result{{/hasOneResult}}\n    {{#hasManyResults}}{{#helpers.formatNumber}}{{nbHits}}{{/helpers.formatNumber}} results{{/hasManyResults}} found in {{processingTimeMS}}ms"},Pa=Ae({name:"stats"}),_a=at("Stats");function Na(e){var t=e.currentRefinement,n=e.refine,r=e.cssClasses,i=e.templateProps;return vn("div",{className:r.root},vn("label",{className:r.label},vn("input",{className:r.checkbox,type:"checkbox",checked:t.isRefined,onChange:function(e){return n(!e.target.checked)}}),vn(Ur,f({},i,{rootTagName:"span",rootProps:{className:r.labelText},templateKey:"labelText",data:t}))))}var xa={labelText:"{{name}}"},Fa=Ae({name:"toggle-refinement"}),Ia=at("ToggleRefinement");function Ca(e){var r=e.items,i=e.cssClasses,a=e.templateProps,s=e.createURL,o=e.refine;return vn("div",{className:qr(i.root,L({},i.noRefinementRoot,0===r.length))},vn("ul",{className:i.list},vn("li",{className:qr(i.item,L({},i.selectedItem,0===r.length))},vn(Ur,f({},a,{templateKey:"home",rootTagName:"a",rootProps:{className:i.link,href:s(void 0),onClick:function(e){e.preventDefault(),o(void 0)}}}))),r.map(function(t,e){var n=e===r.length-1;return vn("li",{key:t.label+e,className:qr(i.item,L({},i.selectedItem,n))},vn(Ur,f({},a,{templateKey:"separator",rootTagName:"span",rootProps:{className:i.separator,"aria-hidden":!0}})),n?t.label:vn("a",{className:i.link,href:s(t.value),onClick:function(e){e.preventDefault(),o(t.value)}},t.label))})))}var Ta=Ae({name:"analytics"}),Ea={home:"Home",separator:">"},ka=Ae({name:"breadcrumb"}),Ma=at("Breadcrumb");function La(e){var t=e.cssClasses,n=e.templateProps,r=e.items,i=e.refine,a=(ge(r,function(e){return e.isRefined})||{value:""}).value;return vn("div",{className:qr(t.root,L({},t.noRefinementRoot,0===r.length))},vn("select",{className:t.select,value:a,onChange:function(e){i(e.target.value)}},vn(Ur,f({},n,{templateKey:"defaultOption",rootTagName:"option",rootProps:{value:"",className:t.option}})),r.map(function(e){return vn(Ur,f({},n,{templateKey:"item",rootTagName:"option",rootProps:{value:e.value,className:t.option},key:e.value,data:e}))})))}var ja={item:"{{label}} ({{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}})",defaultOption:"See all"},Oa=Ae({name:"menu-select"}),Aa=at("MenuSelect");function Ha(e){var t=e.url,n=e.theme,r=e.cssClasses;return vn("div",{className:r.root},vn("a",{href:t,target:"_blank",className:r.link,"aria-label":"Search by Algolia",rel:"noopener noreferrer"},vn("svg",{height:"1.2em",className:r.logo,viewBox:"0 0 168 24",style:{width:"auto"}},vn("path",{fill:"dark"===n?"#FFF":"#5D6494",d:"M6.97 6.68V8.3a4.47 4.47 0 0 0-2.42-.67 2.2 2.2 0 0 0-1.38.4c-.34.26-.5.6-.5 1.02 0 .43.16.77.49 1.03.33.25.83.53 1.51.83a7.04 7.04 0 0 1 1.9 1.08c.34.24.58.54.73.89.15.34.23.74.23 1.18 0 .95-.33 1.7-1 2.24a4 4 0 0 1-2.6.81 5.71 5.71 0 0 1-2.94-.68v-1.71c.84.63 1.81.94 2.92.94.58 0 1.05-.14 1.39-.4.34-.28.5-.65.5-1.13 0-.29-.1-.55-.3-.8a2.2 2.2 0 0 0-.65-.53 23.03 23.03 0 0 0-1.64-.78 13.67 13.67 0 0 1-1.11-.64c-.12-.1-.28-.22-.46-.4a1.72 1.72 0 0 1-.39-.5 4.46 4.46 0 0 1-.22-.6c-.07-.23-.1-.48-.1-.75 0-.91.33-1.63 1-2.17a4 4 0 0 1 2.57-.8c.97 0 1.8.18 2.47.52zm7.47 5.7v-.3a2.26 2.26 0 0 0-.5-1.44c-.3-.35-.74-.53-1.32-.53-.53 0-.99.2-1.37.58-.38.39-.62.95-.72 1.68h3.91zm1 2.79v1.4c-.6.34-1.38.51-2.36.51a4.02 4.02 0 0 1-3-1.13 4.04 4.04 0 0 1-1.11-2.97c0-1.3.34-2.32 1.02-3.06a3.38 3.38 0 0 1 2.6-1.1c1.03 0 1.85.32 2.46.96.6.64.9 1.57.9 2.78 0 .33-.03.68-.09 1.04h-5.31c.1.7.4 1.24.89 1.61.49.38 1.1.56 1.85.56.86 0 1.58-.2 2.15-.6zm6.61-1.78h-1.21c-.6 0-1.05.12-1.35.36-.3.23-.46.53-.46.89 0 .37.12.66.36.88.23.2.57.32 1.02.32.5 0 .9-.15 1.2-.43.3-.28.44-.65.44-1.1v-.92zm-4.07-2.55V9.33a4.96 4.96 0 0 1 2.5-.55c2.1 0 3.17 1.03 3.17 3.08V17H22.1v-.96c-.42.68-1.15 1.02-2.19 1.02-.76 0-1.38-.22-1.84-.66-.46-.44-.7-1-.7-1.68 0-.78.3-1.38.88-1.81.59-.43 1.4-.65 2.46-.65h1.34v-.46c0-.55-.13-.97-.4-1.25-.26-.29-.7-.43-1.32-.43-.86 0-1.65.24-2.35.72zm9.34-1.93v1.42c.39-1 1.1-1.5 2.12-1.5.15 0 .31.02.5.05v1.53c-.23-.1-.48-.14-.76-.14-.54 0-.99.24-1.34.71a2.8 2.8 0 0 0-.52 1.71V17h-1.57V8.91h1.57zm5 4.09a3 3 0 0 0 .76 2.01c.47.53 1.14.8 2 .8.64 0 1.24-.18 1.8-.53v1.4c-.53.32-1.2.48-2 .48a3.98 3.98 0 0 1-4.17-4.18c0-1.16.38-2.15 1.14-2.98a4 4 0 0 1 3.1-1.23c.7 0 1.34.15 1.92.44v1.44a3.24 3.24 0 0 0-1.77-.5A2.65 2.65 0 0 0 32.33 13zm7.92-7.28v4.58c.46-1 1.3-1.5 2.5-1.5.8 0 1.42.24 1.9.73.48.5.72 1.17.72 2.05V17H43.8v-5.1c0-.56-.14-.99-.43-1.29-.28-.3-.65-.45-1.1-.45-.54 0-1 .2-1.42.6-.4.4-.61 1.02-.61 1.85V17h-1.56V5.72h1.56zM55.2 15.74c.6 0 1.1-.25 1.5-.76.4-.5.6-1.16.6-1.95 0-.92-.2-1.62-.6-2.12-.4-.5-.92-.74-1.55-.74-.56 0-1.05.22-1.5.67-.44.45-.66 1.13-.66 2.06 0 .96.22 1.67.64 2.14.43.47.95.7 1.57.7zM53 5.72v4.42a2.74 2.74 0 0 1 2.43-1.34c1.03 0 1.86.38 2.51 1.15.65.76.97 1.78.97 3.05 0 1.13-.3 2.1-.92 2.9-.62.81-1.47 1.21-2.54 1.21s-1.9-.45-2.46-1.34V17h-1.58V5.72H53zm9.9 11.1l-3.22-7.9h1.74l1 2.62 1.26 3.42c.1-.32.48-1.46 1.15-3.42l.91-2.63h1.66l-2.92 7.87c-.78 2.07-1.96 3.1-3.56 3.1-.28 0-.53-.02-.73-.07v-1.34c.17.04.35.06.54.06 1.03 0 1.76-.57 2.17-1.7z"}),Da,Ba,vn("path",{fill:"dark"===n?"#FFF":"#5468FF",d:"M120.92 18.8c-4.38.02-4.38-3.54-4.38-4.1V1.36l2.67-.42v13.25c0 .32 0 2.36 1.71 2.37v2.24zm-10.84-2.18c.82 0 1.43-.04 1.85-.12v-2.72a5.48 5.48 0 0 0-1.57-.2c-.3 0-.6.02-.9.07-.3.04-.57.12-.81.24-.24.11-.44.28-.58.49a.93.93 0 0 0-.22.65c0 .63.22 1 .61 1.23.4.24.94.36 1.62.36zm-.23-9.7c.88 0 1.62.11 2.23.33.6.22 1.09.53 1.44.92.36.4.61.92.76 1.48.16.56.23 1.17.23 1.85v6.87c-.4.1-1.03.2-1.86.32-.84.12-1.78.18-2.82.18-.69 0-1.32-.07-1.9-.2a4 4 0 0 1-1.46-.63c-.4-.3-.72-.67-.96-1.13a4.3 4.3 0 0 1-.34-1.8c0-.66.13-1.08.39-1.53.26-.45.6-.82 1.04-1.1.45-.3.95-.5 1.54-.62a8.8 8.8 0 0 1 3.79.05v-.44c0-.3-.04-.6-.11-.87a1.78 1.78 0 0 0-1.1-1.22c-.31-.12-.7-.2-1.15-.2a9.75 9.75 0 0 0-2.95.46l-.33-2.19c.34-.12.84-.23 1.48-.35.65-.12 1.34-.18 2.08-.18zm52.84 9.63c.82 0 1.43-.05 1.85-.13V13.7a5.42 5.42 0 0 0-1.57-.2c-.3 0-.6.02-.9.07-.3.04-.57.12-.81.24-.24.12-.44.28-.58.5a.93.93 0 0 0-.22.65c0 .63.22.99.61 1.23.4.24.94.36 1.62.36zm-.23-9.7c.88 0 1.63.11 2.23.33.6.22 1.1.53 1.45.92.35.39.6.92.76 1.48.15.56.23 1.18.23 1.85v6.88c-.41.08-1.03.19-1.87.31-.83.12-1.77.18-2.81.18-.7 0-1.33-.06-1.9-.2a4 4 0 0 1-1.47-.63c-.4-.3-.72-.67-.95-1.13a4.3 4.3 0 0 1-.34-1.8c0-.66.13-1.08.38-1.53.26-.45.61-.82 1.05-1.1.44-.3.95-.5 1.53-.62a8.8 8.8 0 0 1 3.8.05v-.43c0-.31-.04-.6-.12-.88-.07-.28-.2-.52-.38-.73a1.78 1.78 0 0 0-.73-.5c-.3-.1-.68-.2-1.14-.2a9.85 9.85 0 0 0-2.95.47l-.32-2.19a11.63 11.63 0 0 1 3.55-.53zm-8.03-1.27a1.62 1.62 0 0 0 0-3.24 1.62 1.62 0 1 0 0 3.24zm1.35 13.22h-2.7V7.27l2.7-.42V18.8zm-4.72 0c-4.38.02-4.38-3.54-4.38-4.1l-.01-13.34 2.67-.42v13.25c0 .32 0 2.36 1.72 2.37v2.24zm-8.7-5.9a4.7 4.7 0 0 0-.74-2.79 2.4 2.4 0 0 0-2.07-1 2.4 2.4 0 0 0-2.06 1 4.7 4.7 0 0 0-.74 2.8c0 1.16.25 1.94.74 2.62a2.4 2.4 0 0 0 2.07 1.02c.88 0 1.57-.34 2.07-1.02.49-.68.73-1.46.73-2.63zm2.74 0a6.46 6.46 0 0 1-1.52 4.23c-.49.53-1.07.94-1.76 1.22-.68.29-1.73.45-2.26.45-.53 0-1.58-.15-2.25-.45a5.1 5.1 0 0 1-2.88-3.13 7.3 7.3 0 0 1-.01-4.84 5.13 5.13 0 0 1 2.9-3.1 5.67 5.67 0 0 1 2.22-.42c.81 0 1.56.14 2.24.42.69.29 1.28.69 1.75 1.22.49.52.87 1.15 1.14 1.89a7 7 0 0 1 .43 2.5zm-20.14 0c0 1.11.25 2.36.74 2.88.5.52 1.13.78 1.91.78a4.07 4.07 0 0 0 2.12-.6V9.33c-.19-.04-.99-.2-1.76-.23a2.67 2.67 0 0 0-2.23 1 4.73 4.73 0 0 0-.78 2.8zm7.44 5.27c0 1.82-.46 3.16-1.4 4-.94.85-2.37 1.27-4.3 1.27-.7 0-2.17-.13-3.34-.4l.43-2.11c.98.2 2.27.26 2.95.26 1.08 0 1.84-.22 2.3-.66.46-.43.68-1.08.68-1.94v-.44a5.2 5.2 0 0 1-2.54.6 5.6 5.6 0 0 1-2.01-.36 4.2 4.2 0 0 1-2.58-2.71 9.88 9.88 0 0 1 .02-5.35 4.92 4.92 0 0 1 2.93-2.96 6.6 6.6 0 0 1 2.43-.46 19.64 19.64 0 0 1 4.43.66v10.6z"}))))}var Da=vn("path",{fill:"#5468FF",d:"M78.99.94h16.6a2.97 2.97 0 0 1 2.96 2.96v16.6a2.97 2.97 0 0 1-2.97 2.96h-16.6a2.97 2.97 0 0 1-2.96-2.96V3.9A2.96 2.96 0 0 1 79 .94"}),Ba=vn("path",{fill:"#FFF",d:"M89.63 5.97v-.78a.98.98 0 0 0-.98-.97h-2.28a.98.98 0 0 0-.97.97V6c0 .09.08.15.17.13a7.13 7.13 0 0 1 3.9-.02c.08.02.16-.04.16-.13m-6.25 1L83 6.6a.98.98 0 0 0-1.38 0l-.46.46a.97.97 0 0 0 0 1.38l.38.39c.06.06.15.04.2-.02a7.49 7.49 0 0 1 1.63-1.62c.07-.04.08-.14.02-.2m4.16 2.45v3.34c0 .1.1.17.2.12l2.97-1.54c.06-.03.08-.12.05-.18a3.7 3.7 0 0 0-3.08-1.87c-.07 0-.14.06-.14.13m0 8.05a4.49 4.49 0 1 1 0-8.98 4.49 4.49 0 0 1 0 8.98m0-10.85a6.37 6.37 0 1 0 0 12.74 6.37 6.37 0 0 0 0-12.74"}),Qa=at("PoweredBy"),qa=Ae({name:"powered-by"});var Ua,Va,Wa=[],$a=sn.__r;sn.__r=function(e){$a&&$a(e),Ua=0,(Va=e.__c).__H&&(Va.__H.t=ts(Va.__H.t))};var za=sn.diffed;sn.diffed=function(e){za&&za(e);var t=e.__c;if(t){var n=t.__H;n&&(n.u=(n.u.some(function(e){e.ref&&(e.ref.current=e.createHandle())}),[]),n.i=ts(n.i))}};var Ka=sn.unmount;function Ja(e){sn.__h&&sn.__h(Va);var t=Va.__H||(Va.__H={o:[],t:[],i:[],u:[]});return e>=t.o.length&&t.o.push({}),t.o[e]}function Ya(e){return function(n,e,t){var r=Ja(Ua++);return r.__c||(r.__c=Va,r.v=[t?t(e):as(void 0,e),function(e){var t=n(r.v[0],e);r.v[0]!==t&&(r.v[0]=t,r.__c.setState({}))}]),r.v}(as,e)}function Ga(e){return function(e,t){var n=Ja(Ua++);return is(n.m,t)?(n.m=t,n.p=e,n.v=e()):n.v}(function(){return{current:e}},[])}sn.unmount=function(e){Ka&&Ka(e);var t=e.__c;if(t){var n=t.__H;n&&n.o.forEach(function(e){return e.l&&e.l()})}};var Xa=function(){};function Za(){Wa.some(function(e){e.s=!1,e.__P&&(e.__H.t=ts(e.__H.t))}),Wa=[]}if("undefined"!=typeof window){var es=sn.requestAnimationFrame;Xa=function(e){(!e.s&&(e.s=!0)&&1===Wa.push(e)||es!==sn.requestAnimationFrame)&&(es=sn.requestAnimationFrame,(sn.requestAnimationFrame||function(e){function t(){clearTimeout(n),cancelAnimationFrame(r),setTimeout(e)}var n=setTimeout(t,100),r=requestAnimationFrame(t)})(Za))}}function ts(e){return e.forEach(ns),e.forEach(rs),[]}function ns(e){e.l&&e.l()}function rs(e){var t=e.v();"function"==typeof t&&(e.l=t)}function is(n,e){return!n||e.some(function(e,t){return e!==n[t]})}function as(e,t){return"function"==typeof t?t(e):t}function ss(e){var t,n=Q(Ya(e.isCollapsed),2),r=n[0],i=n[1],a=Q(Ya(!1),2),s=a[0],o=a[1],c=Ga(null);return function(e,t){var n=Ja(Ua++);is(n.m,t)&&(n.v=e,n.m=t,Va.__H.t.push(n),Xa(Va))}(function(){if(c.current)return c.current.appendChild(e.bodyElement),function(){c.current.removeChild(e.bodyElement)}},[c,e.bodyElement]),s||e.isCollapsed===r||i(e.isCollapsed),vn("div",{className:qr(e.cssClasses.root,(t={},L(t,e.cssClasses.noRefinementRoot,e.hidden),L(t,e.cssClasses.collapsibleRoot,e.collapsible),L(t,e.cssClasses.collapsedRoot,r),t)),hidden:e.hidden},e.templates.header&&vn("div",{className:e.cssClasses.header},vn(Ur,{templates:e.templates,templateKey:"header",rootTagName:"span",data:e.data}),e.collapsible&&vn("button",{className:e.cssClasses.collapseButton,"aria-expanded":!r,onClick:function(e){e.preventDefault(),o(!0),i(function(e){return!e})}},vn(Ur,{templates:e.templates,templateKey:"collapseButtonText",rootTagName:"span",data:{collapsed:r}}))),vn("div",{className:e.cssClasses.body,ref:c}),e.templates.footer&&vn(Ur,{templates:e.templates,templateKey:"footer",rootProps:{className:e.cssClasses.footer},data:e.data}))}function os(e){var t=e.cssClasses,n=e.isBrowserSupported,r=e.isListening,i=e.toggleListening,a=e.voiceListeningState,s=e.templates,o=a.status,c=a.transcript,u=a.isSpeechFinal,l=a.errorCode;return vn("div",{className:t.root},vn(Ur,{templateKey:"buttonText",rootTagName:"button",rootProps:{className:t.button,type:"button",title:"Search by voice".concat(n?"":" (not supported on this browser)"),onClick:function(e){e.currentTarget.blur(),i()},disabled:!n},data:{status:o,errorCode:l,isListening:r,transcript:c,isSpeechFinal:u,isBrowserSupported:n},templates:s}),vn(Ur,{templateKey:"status",rootProps:{className:t.status},data:{status:o,errorCode:l,isListening:r,transcript:c,isSpeechFinal:u,isBrowserSupported:n},templates:s}))}function cs(e){var t=e.isBrowserSupported,n=e.isListening,r=e.toggleListening,i=e.voiceListeningState,a=e.widgetParams,s=a.container,o=a.cssClasses,c=a.templates;Ln(vn(os,{cssClasses:o,templates:c,isBrowserSupported:t,isListening:n,toggleListening:r,voiceListeningState:i}),s)}function us(e){var t=e.cssClasses,n=e.templates,r=e.items;return vn(Ur,{templateKey:"default",templates:n,rootProps:{className:t.root},data:{items:r}})}function ls(e){var t=e.items,n=e.widgetParams,r=n.container,i=n.cssClasses,a=n.templates;Ln(vn(us,{cssClasses:i,templates:a,items:t}),r)}var hs=Ae({name:"panel"}),fs=at("Panel"),ds={buttonText:function(e){var t=e.status,n=e.errorCode,r=e.isListening;return'<svg\n       xmlns="http://www.w3.org/2000/svg"\n       width="16"\n       height="16"\n       viewBox="0 0 24 24"\n       fill="none"\n       stroke="currentColor"\n       stroke-width="2"\n       stroke-linecap="round"\n       stroke-linejoin="round"\n     >\n       '.concat(function(e,t,n){return"error"===e&&"not-allowed"===t?'<line x1="1" y1="1" x2="23" y2="23"></line>\n            <path d="M9 9v3a3 3 0 0 0 5.12 2.12M15 9.34V4a3 3 0 0 0-5.94-.6"></path>\n            <path d="M17 16.95A7 7 0 0 1 5 12v-2m14 0v2a7 7 0 0 1-.11 1.23"></path>\n            <line x1="12" y1="19" x2="12" y2="23"></line>\n            <line x1="8" y1="23" x2="16" y2="23"></line>':'<path\n            d="M12 1a3 3 0 0 0-3 3v8a3 3 0 0 0 6 0V4a3 3 0 0 0-3-3z"\n            fill="'.concat(n?"currentColor":"none",'">\n          </path>\n          <path d="M19 10v2a7 7 0 0 1-14 0v-2"></path>\n          <line x1="12" y1="19" x2="12" y2="23"></line>\n          <line x1="8" y1="23" x2="16" y2="23"></line>')}(t,n,r),"\n     </svg>")},status:"<p>{{transcript}}</p>"},ms=Ae({name:"voice-search"}),ps=at("VoiceSearch"),vs=Ae({name:"query-rule-custom-data"}),gs=at("QueryRuleCustomData"),ys=Ae({name:"query-rule-context"}),bs=Object.freeze({__proto__:null,clearRefinements:function(e){var t=e||{},n=t.container,r=t.templates,i=void 0===r?Kr:r,a=t.includedAttributes,s=t.excludedAttributes,o=t.transformItems,c=t.cssClasses,u=void 0===c?{}:c;if(!n)throw new Error(Jr("The `container` option is required."));var l=ce(n),h={root:qr(Yr(),u.root),button:qr(Yr({descendantName:"button"}),u.button),disabledButton:qr(Yr({descendantName:"button",modifierName:"disabled"}),u.disabledButton)},f=function(e){var a=e.containerNode,s=e.cssClasses,o=e.renderState,c=e.templates;return function(e,t){var n=e.refine,r=e.hasRefinements,i=e.instantSearchInstance;t?o.templateProps=he({defaultTemplates:Kr,templatesConfig:i.templatesConfig,templates:c}):Ln(vn(Vr,{refine:n,cssClasses:s,hasRefinements:r,templateProps:o.templateProps}),a)}}({containerNode:l,cssClasses:h,renderState:{},templates:i});return Vt(f,function(){return Ln(null,l)})({includedAttributes:a,excludedAttributes:s,transformItems:o})},configure:function(e){return Tr(_e)({searchParameters:e})},EXPERIMENTAL_configureRelatedItems:function(e){return Mr(_e)(e)},currentRefinements:function(e){var t=e||{},n=t.container,r=t.includedAttributes,i=t.excludedAttributes,a=t.cssClasses,s=void 0===a?{}:a,o=t.transformItems;if(!n)throw new Error(Gr("The `container` option is required."));var c=ce(n),u={root:qr(Xr(),s.root),list:qr(Xr({descendantName:"list"}),s.list),item:qr(Xr({descendantName:"item"}),s.item),label:qr(Xr({descendantName:"label"}),s.label),category:qr(Xr({descendantName:"category"}),s.category),categoryLabel:qr(Xr({descendantName:"categoryLabel"}),s.categoryLabel),delete:qr(Xr({descendantName:"delete"}),s.delete)};return zt($r,function(){return Ln(null,c)})({container:c,cssClasses:u,includedAttributes:r,excludedAttributes:i,transformItems:o})},geoSearch:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.initialZoom,r=void 0===n?1:n,i=t.initialPosition,a=void 0===i?{lat:0,lng:0}:i,s=t.templates,o=void 0===s?{}:s,c=t.cssClasses,u=void 0===c?{}:c,l=t.builtInMarker,h=void 0===l?{}:l,f=t.customHTMLMarker,d=t.enableRefine,m=void 0===d||d,p=t.enableClearMapRefinement,v=void 0===p||p,g=t.enableRefineControl,y=void 0===g||g,b=t.container,R=t.googleReference,w=A(t,["initialZoom","initialPosition","templates","cssClasses","builtInMarker","customHTMLMarker","enableRefine","enableClearMapRefinement","enableRefineControl","container","googleReference"]),S={createOptions:_e,events:{}},P={createOptions:_e,events:{}};if(!b)throw new Error(ai("The `container` option is required."));if(!R)throw new Error(ai("The `googleReference` option is required."));var _=ce(b),N={root:qr(si(),u.root),tree:si({descendantName:"tree"}),map:qr(si({descendantName:"map"}),u.map),control:qr(si({descendantName:"control"}),u.control),label:qr(si({descendantName:"label"}),u.label),selectedLabel:qr(si({descendantName:"label",modifierName:"selected"}),u.selectedLabel),input:qr(si({descendantName:"input"}),u.input),redo:qr(si({descendantName:"redo"}),u.redo),disabledRedo:qr(si({descendantName:"redo",modifierName:"disabled"}),u.disabledRedo),reset:qr(si({descendantName:"reset"}),u.reset)},x=D({},ii,{},o),F=D({},S,{},h),I=(Boolean(f)||Boolean(o.HTMLMarker))&&D({},P,{},f),C=function(l){return function(){function u(e){var t,n=e.__id,r=e.position,i=e.map,a=e.template,s=e.className,o=e.anchor,c=void 0===o?{x:0,y:0}:o;return k(this,u),L(H(t=B(this,O(u).call(this))),"__id",void 0),L(H(t),"anchor",void 0),L(H(t),"offset",void 0),L(H(t),"listeners",void 0),L(H(t),"latLng",void 0),L(H(t),"element",void 0),t.__id=n,t.anchor=c,t.listeners={},t.latLng=new l.maps.LatLng(r),t.element=document.createElement("div"),t.element.className=s,t.element.style.position="absolute",t.element.innerHTML=a,t.setMap(i),t}return j(u,l.maps.OverlayView),M(u,[{key:"onAdd",value:function(){this.getPanes().overlayMouseTarget.appendChild(this.element);var e=this.element.getBoundingClientRect();this.offset={x:this.anchor.x+e.width/2,y:this.anchor.y+e.height},this.element.style.width="".concat(e.width,"px")}},{key:"draw",value:function(){var e=this.getProjection().fromLatLngToDivPixel(this.latLng);this.element.style.left="".concat(Math.round(e.x-this.offset.x),"px"),this.element.style.top="".concat(Math.round(e.y-this.offset.y),"px"),this.element.style.zIndex=String(parseInt(this.element.style.top,10))}},{key:"onRemove",value:function(){var t=this;this.element&&(this.element.parentNode.removeChild(this.element),Object.keys(this.listeners).forEach(function(e){t.element.removeEventListener(e,t.listeners[e])}),delete this.element,delete this.listeners)}},{key:"addListener",value:function(e,t){this.listeners[e]=t;var n=this.element;return n.addEventListener(e,t),{remove:function(){return n.removeEventListener(e,t)}}}},{key:"getPosition",value:function(){return this.latLng}}]),u}()}(R),T=I?function(e){var t=e.item,n=A(e,["item"]);return new C(D({},I.createOptions(t),{},n,{__id:t.objectID,position:t._geoloc,className:qr(si({descendantName:"marker"})),template:ve({templateKey:"HTMLMarker",templates:x,data:t})}))}:function(e){var t=e.item,n=A(e,["item"]);return new R.maps.Marker(D({},F.createOptions(t),{},n,{__id:t.objectID,position:t._geoloc}))},E=I||F;return Pr(ri,function(){return Ln(null,_)})(D({},w,{renderState:{},container:_,googleReference:R,initialZoom:r,initialPosition:a,templates:x,cssClasses:N,createMarker:T,markerOptions:E,enableRefine:m,enableClearMapRefinement:v,enableRefineControl:y}))},hierarchicalMenu:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attributes,r=e.separator,i=e.rootPath,a=e.showParentLevel,s=e.limit,o=e.showMore,c=void 0!==o&&o,u=e.showMoreLimit,l=e.sortBy,h=e.transformItems,f=e.templates,d=void 0===f?li:f,m=e.cssClasses,p=void 0===m?{}:m;if(!t)throw new Error(hi("The `container` option is required."));var v=ce(t);return en(function(e){var u=e.cssClasses,l=e.containerNode,h=e.showMore,f=e.templates,d=e.renderState;return function(e,t){var n=e.createURL,r=e.items,i=e.refine,a=e.instantSearchInstance,s=e.isShowingMore,o=e.toggleShowMore,c=e.canToggleShowMore;t?d.templateProps=he({defaultTemplates:li,templatesConfig:a.templatesConfig,templates:f}):Ln(vn(ui,{createURL:n,cssClasses:u,facetValues:r,templateProps:d.templateProps,toggleRefinement:i,showMore:h,toggleShowMore:o,isShowingMore:s,canToggleShowMore:c}),l)}}({cssClasses:{root:qr(fi(),p.root),noRefinementRoot:qr(fi({modifierName:"noRefinement"}),p.noRefinementRoot),list:qr(fi({descendantName:"list"}),p.list),childList:qr(fi({descendantName:"list",modifierName:"child"}),p.childList),item:qr(fi({descendantName:"item"}),p.item),selectedItem:qr(fi({descendantName:"item",modifierName:"selected"}),p.selectedItem),parentItem:qr(fi({descendantName:"item",modifierName:"parent"}),p.parentItem),link:qr(fi({descendantName:"link"}),p.link),label:qr(fi({descendantName:"label"}),p.label),count:qr(fi({descendantName:"count"}),p.count),showMore:qr(fi({descendantName:"showMore"}),p.showMore),disabledShowMore:qr(fi({descendantName:"showMore",modifierName:"disabled"}),p.disabledShowMore)},containerNode:v,templates:d,showMore:c,renderState:{}}),function(){return Ln(null,v)})({attributes:n,separator:r,rootPath:i,showParentLevel:a,limit:s,showMore:c,showMoreLimit:u,sortBy:l,transformItems:h})},hits:function(e){var t=e||{},n=t.container,r=t.escapeHTML,i=t.transformItems,a=t.templates,s=void 0===a?mi:a,o=t.cssClasses,c=void 0===o?{}:o;if(!n)throw new Error(pi("The `container` option is required."));var u=ce(n),l={root:qr(vi(),c.root),emptyRoot:qr(vi({modifierName:"empty"}),c.emptyRoot),list:qr(vi({descendantName:"list"}),c.list),item:qr(vi({descendantName:"item"}),c.item)},h=function(e){var o=e.renderState,c=e.cssClasses,u=e.containerNode,l=e.templates;return function(e,t){var n=e.hits,r=e.results,i=e.instantSearchInstance,a=e.insights,s=e.bindEvent;t?o.templateProps=he({defaultTemplates:mi,templatesConfig:i.templatesConfig,templates:l}):Ln(vn(gi,{cssClasses:c,hits:n,results:r,templateProps:o.templateProps,insights:a,sendEvent:function(e){i.sendEventToInsights(e)},bindEvent:s}),u)}}({containerNode:u,cssClasses:l,renderState:{},templates:s});return an(tn)(h,function(){return Ln(null,u)})({escapeHTML:r,transformItems:i})},hitsPerPage:function(e){var t=e||{},n=t.container,r=t.items,i=t.cssClasses,a=void 0===i?{}:i,s=t.transformItems;if(!n)throw new Error(bi("The `container` option is required."));var o=ce(n),c={root:qr(Ri(),a.root),select:qr(Ri({descendantName:"select"}),a.select),option:qr(Ri({descendantName:"option"}),a.option)},u=function(e){var a=e.containerNode,s=e.cssClasses;return function(e,t){var n=e.items,r=e.refine;if(!t){var i=(ge(n,function(e){return e.isRefined})||{}).value;Ln(vn("div",{className:s.root},vn(yi,{cssClasses:s,currentValue:i,options:n,setValue:r})),a)}}}({containerNode:o,cssClasses:c});return An(u,function(){return Ln(null,o)})({items:r,transformItems:s})},infiniteHits:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.container,r=t.escapeHTML,i=t.transformItems,a=t.templates,s=void 0===a?wi:a,o=t.cssClasses,c=void 0===o?{}:o,u=t.showPrevious,l=t.cache;if(!n)throw new Error(Si("The `container` option is required."));var h=ce(n),f={root:qr(Pi(),c.root),emptyRoot:qr(Pi({modifierName:"empty"}),c.emptyRoot),item:qr(Pi({descendantName:"item"}),c.item),list:qr(Pi({descendantName:"list"}),c.list),loadPrevious:qr(Pi({descendantName:"loadPrevious"}),c.loadPrevious),disabledLoadPrevious:qr(Pi({descendantName:"loadPrevious",modifierName:"disabled"}),c.disabledLoadPrevious),loadMore:qr(Pi({descendantName:"loadMore"}),c.loadMore),disabledLoadMore:qr(Pi({descendantName:"loadMore",modifierName:"disabled"}),c.disabledLoadMore)},d=function(e){var h=e.cssClasses,f=e.containerNode,d=e.renderState,m=e.templates,p=e.showPrevious;return function(e,t){var n=e.hits,r=e.results,i=e.showMore,a=e.showPrevious,s=e.isFirstPage,o=e.isLastPage,c=e.instantSearchInstance,u=e.insights,l=e.bindEvent;t?d.templateProps=he({defaultTemplates:wi,templatesConfig:c.templatesConfig,templates:m}):Ln(vn(_i,{cssClasses:h,hits:n,results:r,hasShowPrevious:p,showPrevious:a,showMore:i,templateProps:d.templateProps,isFirstPage:s,isLastPage:o,insights:u,sendEvent:function(e){c.sendEventToInsights(e)},bindEvent:l}),f)}}({containerNode:h,cssClasses:f,templates:s,showPrevious:u,renderState:{}});return an(Un)(d,function(){return Ln(null,h)})({escapeHTML:r,transformItems:i,showPrevious:u,cache:l})},menu:function(e){var t=e.container,n=e.attribute,r=e.sortBy,i=e.limit,a=e.showMore,s=e.showMoreLimit,o=e.cssClasses,c=void 0===o?{}:o,u=e.templates,l=void 0===u?Ni:u,h=e.transformItems;if(!t)throw new Error(xi("The `container` option is required."));var f=ce(t),d={root:qr(Fi(),c.root),noRefinementRoot:qr(Fi({modifierName:"noRefinement"}),c.noRefinementRoot),list:qr(Fi({descendantName:"list"}),c.list),item:qr(Fi({descendantName:"item"}),c.item),selectedItem:qr(Fi({descendantName:"item",modifierName:"selected"}),c.selectedItem),link:qr(Fi({descendantName:"link"}),c.link),label:qr(Fi({descendantName:"label"}),c.label),count:qr(Fi({descendantName:"count"}),c.count),showMore:qr(Fi({descendantName:"showMore"}),c.showMore),disabledShowMore:qr(Fi({descendantName:"showMore",modifierName:"disabled"}),c.disabledShowMore)};return $n(function(e){var l=e.containerNode,h=e.cssClasses,f=e.renderState,d=e.templates,m=e.showMore;return function(e,t){var n=e.refine,r=e.items,i=e.createURL,a=e.instantSearchInstance,s=e.isShowingMore,o=e.toggleShowMore,c=e.canToggleShowMore;if(t)f.templateProps=he({defaultTemplates:Ni,templatesConfig:a.templatesConfig,templates:d});else{var u=r.map(function(e){return D({},e,{url:i(e.name)})});Ln(vn(ui,{createURL:i,cssClasses:h,facetValues:u,showMore:m,templateProps:f.templateProps,toggleRefinement:n,toggleShowMore:o,isShowingMore:s,canToggleShowMore:c}),l)}}}({containerNode:f,cssClasses:d,renderState:{},templates:l,showMore:a}),function(){return Ln(null,f)})({attribute:n,limit:i,showMore:a,showMoreLimit:s,sortBy:r,transformItems:h})},refinementList:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.operator,i=e.sortBy,a=e.limit,s=e.showMore,o=e.showMoreLimit,c=e.searchable,u=void 0!==c&&c,l=e.searchablePlaceholder,h=void 0===l?"Search...":l,f=e.searchableEscapeFacetValues,d=void 0===f||f,m=e.searchableIsAlwaysActive,p=void 0===m||m,v=e.cssClasses,g=void 0===v?{}:v,y=e.templates,b=void 0===y?Ci:y,R=e.transformItems;if(!t)throw new Error(Ti("The `container` option is required."));var w=!!u&&Boolean(d),S=ce(t),P=function(e){var t=D({},e,{submit:e.searchableSubmit,reset:e.searchableReset,loadingIndicator:e.searchableLoadingIndicator});return t.searchableReset,t.searchableSubmit,t.searchableLoadingIndicator,A(t,["searchableReset","searchableSubmit","searchableLoadingIndicator"])}(D({},Ci,{},b)),_={root:qr(Ei(),g.root),noRefinementRoot:qr(Ei({modifierName:"noRefinement"}),g.noRefinementRoot),list:qr(Ei({descendantName:"list"}),g.list),item:qr(Ei({descendantName:"item"}),g.item),selectedItem:qr(Ei({descendantName:"item",modifierName:"selected"}),g.selectedItem),searchBox:qr(Ei({descendantName:"searchBox"}),g.searchBox),label:qr(Ei({descendantName:"label"}),g.label),checkbox:qr(Ei({descendantName:"checkbox"}),g.checkbox),labelText:qr(Ei({descendantName:"labelText"}),g.labelText),count:qr(Ei({descendantName:"count"}),g.count),noResults:qr(Ei({descendantName:"noResults"}),g.noResults),showMore:qr(Ei({descendantName:"showMore"}),g.showMore),disabledShowMore:qr(Ei({descendantName:"showMore",modifierName:"disabled"}),g.disabledShowMore),searchable:{root:qr(ki(),g.searchableRoot),form:qr(ki({descendantName:"form"}),g.searchableForm),input:qr(ki({descendantName:"input"}),g.searchableInput),submit:qr(ki({descendantName:"submit"}),g.searchableSubmit),submitIcon:qr(ki({descendantName:"submitIcon"}),g.searchableSubmitIcon),reset:qr(ki({descendantName:"reset"}),g.searchableReset),resetIcon:qr(ki({descendantName:"resetIcon"}),g.searchableResetIcon),loadingIndicator:qr(ki({descendantName:"loadingIndicator"}),g.searchableLoadingIndicator),loadingIcon:qr(ki({descendantName:"loadingIcon"}),g.searchableLoadingIcon)}};return sr(function(e){var f=e.containerNode,d=e.cssClasses,m=e.templates,p=e.renderState,v=e.showMore,g=e.searchable,y=e.searchablePlaceholder,b=e.searchableIsAlwaysActive;return function(e,t){var n=e.refine,r=e.items,i=e.createURL,a=e.searchForItems,s=e.isFromSearch,o=e.instantSearchInstance,c=e.toggleShowMore,u=e.isShowingMore,l=e.hasExhaustiveItems,h=e.canToggleShowMore;t?p.templateProps=he({templatesConfig:o.templatesConfig,templates:m}):Ln(vn(ui,{createURL:i,cssClasses:d,facetValues:r,templateProps:p.templateProps,toggleRefinement:n,searchFacetValues:g?a:void 0,searchPlaceholder:y,searchIsAlwaysActive:b,isFromSearch:s,showMore:v&&!s&&0<r.length,toggleShowMore:c,isShowingMore:u,hasExhaustiveItems:l,canToggleShowMore:h}),f)}}({containerNode:S,cssClasses:_,templates:P,renderState:{},searchable:u,searchablePlaceholder:h,searchableIsAlwaysActive:p,showMore:s}),function(){return Ln(null,S)})({attribute:n,operator:r,limit:a,showMore:s,showMoreLimit:o,sortBy:i,escapeFacetValues:w,transformItems:R})},numericMenu:function(e){var t=e||{},n=t.container,r=t.attribute,i=t.items,a=t.cssClasses,s=void 0===a?{}:a,o=t.templates,c=void 0===o?Mi:o,u=t.transformItems;if(!n)throw new Error(Li("The `container` option is required."));var l=ce(n),h={root:qr(ji(),s.root),noRefinementRoot:qr(ji({modifierName:"noRefinement"}),s.noRefinementRoot),list:qr(ji({descendantName:"list"}),s.list),item:qr(ji({descendantName:"item"}),s.item),selectedItem:qr(ji({descendantName:"item",modifierName:"selected"}),s.selectedItem),label:qr(ji({descendantName:"label"}),s.label),radio:qr(ji({descendantName:"radio"}),s.radio),labelText:qr(ji({descendantName:"labelText"}),s.labelText)},f=function(e){var s=e.containerNode,o=e.attribute,c=e.cssClasses,u=e.renderState,l=e.templates;return function(e,t){var n=e.createURL,r=e.instantSearchInstance,i=e.refine,a=e.items;t?u.templateProps=he({defaultTemplates:Mi,templatesConfig:r.templatesConfig,templates:l}):Ln(vn(ui,{createURL:n,cssClasses:c,facetValues:a,templateProps:u.templateProps,toggleRefinement:i,attribute:o}),s)}}({containerNode:l,attribute:r,cssClasses:h,renderState:{},templates:c});return zn(f,function(){return Ln(null,l)})({attribute:r,items:i,transformItems:u})},pagination:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.templates,r=void 0===n?{}:n,i=e.cssClasses,a=void 0===i?{}:i,s=e.totalPages,o=e.padding,c=e.showFirst,u=void 0===c||c,l=e.showLast,h=void 0===l||l,f=e.showPrevious,d=void 0===f||f,m=e.showNext,p=void 0===m||m,v=e.scrollTo,g=void 0===v?"body":v;if(!t)throw new Error(Hi("The `container` option is required."));var y=ce(t),b=!0===g?"body":g,R=!1!==b&&ce(b),w={root:qr(Di(),a.root),noRefinementRoot:qr(Di({modifierName:"noRefinement"}),a.noRefinementRoot),list:qr(Di({descendantName:"list"}),a.list),item:qr(Di({descendantName:"item"}),a.item),firstPageItem:qr(Di({descendantName:"item",modifierName:"firstPage"}),a.firstPageItem),lastPageItem:qr(Di({descendantName:"item",modifierName:"lastPage"}),a.lastPageItem),previousPageItem:qr(Di({descendantName:"item",modifierName:"previousPage"}),a.previousPageItem),nextPageItem:qr(Di({descendantName:"item",modifierName:"nextPage"}),a.nextPageItem),pageItem:qr(Di({descendantName:"item",modifierName:"page"}),a.pageItem),selectedItem:qr(Di({descendantName:"item",modifierName:"selected"}),a.selectedItem),disabledItem:qr(Di({descendantName:"item",modifierName:"disabled"}),a.disabledItem),link:qr(Di({descendantName:"link"}),a.link)},S=D({},Bi,{},r);return tr(function(e){var l=e.containerNode,h=e.cssClasses,f=e.templates,d=e.totalPages,m=e.showFirst,p=e.showLast,v=e.showPrevious,g=e.showNext,y=e.scrollToNode;return function(e,t){var n=e.createURL,r=e.currentRefinement,i=e.nbHits,a=e.nbPages,s=e.pages,o=e.isFirstPage,c=e.isLastPage,u=e.refine;if(!t){Ln(vn(Ai,{createURL:n,cssClasses:h,currentPage:r,templates:f,nbHits:i,nbPages:a,pages:s,totalPages:d,isFirstPage:o,isLastPage:c,setCurrentPage:function(e){u(e),!1!==y&&y.scrollIntoView()},showFirst:m,showLast:p,showPrevious:v,showNext:g}),l)}}}({containerNode:y,cssClasses:w,templates:S,showFirst:u,showLast:h,showPrevious:d,showNext:p,padding:o,scrollToNode:R}),function(){return Ln(null,y)})({totalPages:s,padding:o})},rangeInput:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.min,i=e.max,a=e.precision,s=void 0===a?0:a,o=e.cssClasses,c=void 0===o?{}:o,u=e.templates,l=void 0===u?{}:u;if(!t)throw new Error(qi("The `container` option is required."));var h=ce(t),f=D({separatorText:"to",submitText:"Go"},l),d={root:qr(Ui(),c.root),noRefinement:qr(Ui({modifierName:"noRefinement"})),form:qr(Ui({descendantName:"form"}),c.form),label:qr(Ui({descendantName:"label"}),c.label),input:qr(Ui({descendantName:"input"}),c.input),inputMin:qr(Ui({descendantName:"input",modifierName:"min"}),c.inputMin),inputMax:qr(Ui({descendantName:"input",modifierName:"max"}),c.inputMax),separator:qr(Ui({descendantName:"separator"}),c.separator),submit:qr(Ui({descendantName:"submit"}),c.submit)};return D({},ir(function(e){var d=e.containerNode,m=e.cssClasses,p=e.renderState,v=e.templates;return function(e,t){var n=e.refine,r=e.range,i=e.start,a=e.widgetParams,s=e.instantSearchInstance;if(t)p.templateProps=he({templatesConfig:s.templatesConfig,templates:v});else{var o=r.min,c=r.max,u=Q(i,2),l=u[0],h=u[1],f=1/Math.pow(10,a.precision);Ln(vn(Qi,{min:o,max:c,step:f,values:{min:l!==-1/0&&l!==o?l:void 0,max:h!==1/0&&h!==c?h:void 0},cssClasses:m,refine:n,templateProps:p.templateProps}),d)}}}({containerNode:h,cssClasses:d,templates:f,renderState:{}}),function(){return Ln(null,h)})({attribute:n,min:r,max:i,precision:s}),{$$type:"ais.rangeInput"})},searchBox:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.placeholder,r=void 0===n?"":n,i=e.cssClasses,a=void 0===i?{}:i,s=e.autofocus,o=void 0!==s&&s,c=e.searchAsYouType,u=void 0===c||c,l=e.showReset,h=void 0===l||l,f=e.showSubmit,d=void 0===f||f,m=e.showLoadingIndicator,p=void 0===m||m,v=e.queryHook,g=e.templates;if(!t)throw new Error(Vi("The `container` option is required."));var y=ce(t),b={root:qr(Wi(),a.root),form:qr(Wi({descendantName:"form"}),a.form),input:qr(Wi({descendantName:"input"}),a.input),submit:qr(Wi({descendantName:"submit"}),a.submit),submitIcon:qr(Wi({descendantName:"submitIcon"}),a.submitIcon),reset:qr(Wi({descendantName:"reset"}),a.reset),resetIcon:qr(Wi({descendantName:"resetIcon"}),a.resetIcon),loadingIndicator:qr(Wi({descendantName:"loadingIndicator"}),a.loadingIndicator),loadingIcon:qr(Wi({descendantName:"loadingIcon"}),a.loadingIcon)};return cr(function(e){var i=e.containerNode,a=e.cssClasses,s=e.placeholder,o=e.templates,c=e.autofocus,u=e.searchAsYouType,l=e.showReset,h=e.showSubmit,f=e.showLoadingIndicator;return function(e){var t=e.refine,n=e.query,r=e.isSearchStalled;Ln(vn(ci,{query:n,placeholder:s,autofocus:c,refine:t,searchAsYouType:u,templates:o,showSubmit:h,showReset:l,showLoadingIndicator:f,isSearchStalled:r,cssClasses:a}),i)}}({containerNode:y,cssClasses:b,placeholder:r,templates:D({},Ii,{},g),autofocus:o,searchAsYouType:u,showReset:h,showSubmit:d,showLoadingIndicator:p}),function(){return Ln(null,y)})({queryHook:v})},rangeSlider:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.min,i=e.max,a=e.cssClasses,s=void 0===a?{}:a,o=e.step,c=e.pips,u=void 0===c||c,l=e.precision,h=void 0===l?0:l,f=e.tooltips,d=void 0===f||f;if(!t)throw new Error(fa("The `container` option is required."));var m=ce(t),p={root:qr(da(),s.root),disabledRoot:qr(da({modifierName:"disabled"}),s.disabledRoot)};return D({},ir(function(e){var f=e.containerNode,d=e.cssClasses,m=e.pips,p=e.step,v=e.tooltips;return function(e,t){var n=e.refine,r=e.range,i=e.start;if(!t){var a=r.min,s=r.max,o=Q(i,2),c=o[0],u=o[1],l=c===-1/0?a:c,h=u===1/0?s:u;Ln(vn(ha,{cssClasses:d,refine:n,min:a,max:s,values:[s<l?s:l,h<a?a:h],tooltips:v,step:p,pips:m}),f)}}}({containerNode:m,step:o,pips:u,tooltips:d,renderState:{},cssClasses:p}),function(){return Ln(null,m)})({attribute:n,min:r,max:i,precision:h}),{$$type:"ais.rangeSlider"})},sortBy:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.items,r=e.cssClasses,i=void 0===r?{}:r,a=e.transformItems;if(!t)throw new Error(ma("The `container` option is required."));var s=ce(t),o={root:qr(pa(),i.root),select:qr(pa({descendantName:"select"}),i.select),option:qr(pa({descendantName:"option"}),i.option)};return lr(function(e){var a=e.containerNode,s=e.cssClasses;return function(e,t){var n=e.currentRefinement,r=e.options,i=e.refine;t||Ln(vn("div",{className:s.root},vn(yi,{cssClasses:s,currentValue:n,options:r,setValue:i})),a)}}({containerNode:s,cssClasses:o}),function(){return Ln(null,s)})({items:n,transformItems:a})},ratingMenu:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.max,i=void 0===r?5:r,a=e.cssClasses,s=void 0===a?{}:a,o=e.templates,c=void 0===o?va:o;if(!t)throw new Error(ga("The `container` option is required."));var u=ce(t),l={root:qr(ya(),s.root),noRefinementRoot:qr(ya({modifierName:"noRefinement"}),s.noRefinementRoot),list:qr(ya({descendantName:"list"}),s.list),item:qr(ya({descendantName:"item"}),s.item),selectedItem:qr(ya({descendantName:"item",modifierName:"selected"}),s.selectedItem),disabledItem:qr(ya({descendantName:"item",modifierName:"disabled"}),s.disabledItem),link:qr(ya({descendantName:"link"}),s.link),starIcon:qr(ya({descendantName:"starIcon"}),s.starIcon),fullStarIcon:qr(ya({descendantName:"starIcon",modifierName:"full"}),s.fullStarIcon),emptyStarIcon:qr(ya({descendantName:"starIcon",modifierName:"empty"}),s.emptyStarIcon),label:qr(ya({descendantName:"label"}),s.label),count:qr(ya({descendantName:"count"}),s.count)};return mr(function(e){var s=e.containerNode,o=e.cssClasses,c=e.templates,u=e.renderState;return function(e,t){var n=e.refine,r=e.items,i=e.createURL,a=e.instantSearchInstance;t?u.templateProps=he({defaultTemplates:va,templatesConfig:a.templatesConfig,templates:c}):Ln(vn(ui,{createURL:i,cssClasses:o,facetValues:r,templateProps:u.templateProps,toggleRefinement:n},vn("svg",{xmlns:"http://www.w3.org/2000/svg",style:"display:none;"},vn("symbol",{id:ya({descendantName:"starSymbol"}),viewBox:"0 0 24 24"},ba),vn("symbol",{id:ya({descendantName:"starEmptySymbol"}),viewBox:"0 0 24 24"},Ra))),s)}}({containerNode:u,cssClasses:l,renderState:{},templates:c}),function(){return Ln(null,u)})({attribute:n,max:i})},stats:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.cssClasses,r=void 0===n?{}:n,i=e.templates,a=void 0===i?Sa:i;if(!t)throw new Error(Pa("The `container` option is required."));var s=ce(t),o={root:qr(_a(),r.root),text:qr(_a({descendantName:"text"}),r.text)};return vr(function(e){var u=e.containerNode,l=e.cssClasses,h=e.renderState,f=e.templates;return function(e,t){var n=e.hitsPerPage,r=e.nbHits,i=e.nbPages,a=e.page,s=e.processingTimeMS,o=e.query,c=e.instantSearchInstance;t?h.templateProps=he({defaultTemplates:Sa,templatesConfig:c.templatesConfig,templates:f}):Ln(vn(wa,{cssClasses:l,hitsPerPage:n,nbHits:r,nbPages:i,page:a,processingTimeMS:s,query:o,templateProps:h.templateProps}),u)}}({containerNode:s,cssClasses:o,renderState:{},templates:a}),function(){return Ln(null,s)})()},toggleRefinement:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.cssClasses,i=void 0===r?{}:r,a=e.templates,s=void 0===a?xa:a,o=e.on,c=void 0===o||o,u=e.off;if(!t)throw new Error(Fa("The `container` option is required."));var l=ce(t),h={root:qr(Ia(),i.root),label:qr(Ia({descendantName:"label"}),i.label),checkbox:qr(Ia({descendantName:"checkbox"}),i.checkbox),labelText:qr(Ia({descendantName:"labelText"}),i.labelText)};return Rr(function(e){var s=e.containerNode,o=e.cssClasses,c=e.renderState,u=e.templates;return function(e,t){var n=e.value,r=e.createURL,i=e.refine,a=e.instantSearchInstance;t?c.templateProps=he({defaultTemplates:xa,templatesConfig:a.templatesConfig,templates:u}):Ln(vn(Na,{createURL:r,cssClasses:o,currentRefinement:n,templateProps:c.templateProps,refine:function(e){return i({isRefined:e})}}),s)}}({containerNode:l,cssClasses:h,renderState:{},templates:s}),function(){return Ln(null,l)})({attribute:n,on:c,off:u})},analytics:function(e){var t=e||{},s=t.pushFunction,n=t.delay,r=void 0===n?3e3:n,i=t.triggerOnUIInteraction,a=void 0!==i&&i,o=t.pushInitialSearch,c=void 0===o||o,u=t.pushPagination,l=void 0!==u&&u;if(!s)throw new Error(Ta("The `pushFunction` option is required."));function h(e){if(null!==e){var t=[],n=function(e){var t=[];for(var n in e)if(e.hasOwnProperty(n)){var r=e[n].join("+");t.push("".concat(encodeURIComponent(n),"=").concat(encodeURIComponent(n),"_").concat(encodeURIComponent(r)))}return t.join("&")}(D({},e.state.disjunctiveFacetsRefinements,{},e.state.facetsRefinements,{},e.state.hierarchicalFacetsRefinements)),r=function(e){var t=[];for(var n in e)if(e.hasOwnProperty(n)){var r=e[n];if(r.hasOwnProperty(">=")&&r.hasOwnProperty("<="))r[">="]&&r[">="][0]===r["<="]&&r["<="][0]?t.push("".concat(n,"=").concat(n,"_").concat(r[">="])):t.push("".concat(n,"=").concat(n,"_").concat(r[">="],"to").concat(r["<="]));else if(r.hasOwnProperty(">="))t.push("".concat(n,"=").concat(n,"_from").concat(r[">="]));else if(r.hasOwnProperty("<="))t.push("".concat(n,"=").concat(n,"_to").concat(r["<="]));else if(r.hasOwnProperty("=")){var i=[];for(var a in r["="])r["="].hasOwnProperty(a)&&i.push(r["="][a]);t.push("".concat(n,"=").concat(n,"_").concat(i.join("-")))}}return t.join("&")}(e.state.numericRefinements);""!==n&&t.push(n),""!==r&&t.push(r);var i=t.join("&"),a="Query: ".concat(e.state.query||"",", ").concat(i);!0===l&&(a+=", Page: ".concat(e.state.page||0)),m!==a&&(s(i,e.state,e.results),m=a)}}var f,d=null,m="",p=!0;!0===c&&(p=!1);function v(){h(d)}function g(){h(d)}return{init:function(){!0===a&&(document.addEventListener("click",v),window.addEventListener("beforeunload",g))},render:function(e){var t=e.results,n=e.state;!0!==p?(d={results:t,state:n},f&&clearTimeout(f),f=window.setTimeout(function(){return h(d)},r)):p=!1},dispose:function(){!0===a&&(document.removeEventListener("click",v),window.removeEventListener("beforeunload",g))}}},breadcrumb:function(e){var t=e||{},n=t.container,r=t.attributes,i=t.separator,a=t.rootPath,s=t.transformItems,o=t.templates,c=void 0===o?Ea:o,u=t.cssClasses,l=void 0===u?{}:u;if(!n)throw new Error(ka("The `container` option is required."));var h=ce(n),f={root:qr(Ma(),l.root),noRefinementRoot:qr(Ma({modifierName:"noRefinement"}),l.noRefinementRoot),list:qr(Ma({descendantName:"list"}),l.list),item:qr(Ma({descendantName:"item"}),l.item),selectedItem:qr(Ma({descendantName:"item",modifierName:"selected"}),l.selectedItem),separator:qr(Ma({descendantName:"separator"}),l.separator),link:qr(Ma({descendantName:"link"}),l.link)},d=function(e){var o=e.containerNode,c=e.cssClasses,u=e.renderState,l=e.templates;return function(e,t){var n=e.canRefine,r=e.createURL,i=e.instantSearchInstance,a=e.items,s=e.refine;t?u.templateProps=he({defaultTemplates:Ea,templatesConfig:i.templatesConfig,templates:l}):Ln(vn(Ca,{canRefine:n,cssClasses:c,createURL:r,items:a,refine:s,templateProps:u.templateProps}),o)}}({containerNode:h,cssClasses:f,renderState:{},templates:c});return wr(d,function(){return Ln(null,h)})({attributes:r,separator:i,rootPath:a,transformItems:s})},menuSelect:function(e){var t=e.container,n=e.attribute,r=e.sortBy,i=void 0===r?["name:asc"]:r,a=e.limit,s=void 0===a?10:a,o=e.cssClasses,c=void 0===o?{}:o,u=e.templates,l=void 0===u?ja:u,h=e.transformItems;if(!t)throw new Error(Oa("The `container` option is required."));var f=ce(t),d={root:qr(Aa(),c.root),noRefinementRoot:qr(Aa({modifierName:"noRefinement"}),c.noRefinementRoot),select:qr(Aa({descendantName:"select"}),c.select),option:qr(Aa({descendantName:"option"}),c.option)};return $n(function(e){var s=e.containerNode,o=e.cssClasses,c=e.renderState,u=e.templates;return function(e,t){var n=e.refine,r=e.items,i=e.canRefine,a=e.instantSearchInstance;t?c.templateProps=he({defaultTemplates:ja,templatesConfig:a.templatesConfig,templates:u}):Ln(vn(La,{cssClasses:o,items:r,refine:n,templateProps:c.templateProps,canRefine:i}),s)}}({containerNode:f,cssClasses:d,renderState:{},templates:l}),function(){return Ln(null,f)})({attribute:n,limit:s,sortBy:i,transformItems:h})},poweredBy:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.cssClasses,r=void 0===n?{}:n,i=e.theme,a=void 0===i?"light":i;if(!t)throw new Error(qa("The `container` option is required."));var s=ce(t),o={root:qr(Qa(),Qa({modifierName:"dark"===a?"dark":"light"}),r.root),link:qr(Qa({descendantName:"link"}),r.link),logo:qr(Qa({descendantName:"logo"}),r.logo)};return Fr(function(e){var a=e.containerNode,s=e.cssClasses;return function(e,t){var n=e.url,r=e.widgetParams;if(t){var i=r.theme;Ln(vn(Ha,{cssClasses:s,url:n,theme:i}),a)}else;}}({containerNode:s,cssClasses:o}),function(){return Ln(null,s)})({theme:a})},panel:function(e){var t=e||{},n=t.templates,r=void 0===n?{}:n,i=t.hidden,o=void 0===i?function(){return!1}:i,a=t.collapsed,s=t.cssClasses,c=void 0===s?{}:s,u=document.createElement("div"),l=Boolean(a),h="function"==typeof a?a:function(){return!1},f={root:qr(fs(),c.root),noRefinementRoot:qr(fs({modifierName:"noRefinement"}),c.noRefinementRoot),collapsibleRoot:qr(fs({modifierName:"collapsible"}),c.collapsibleRoot),collapsedRoot:qr(fs({modifierName:"collapsed"}),c.collapsedRoot),collapseButton:qr(fs({descendantName:"collapseButton"}),c.collapseButton),collapseIcon:qr(fs({descendantName:"collapseIcon"}),c.collapseIcon),body:qr(fs({descendantName:"body"}),c.body),header:qr(fs({descendantName:"header"}),c.header),footer:qr(fs({descendantName:"footer"}),c.footer)};return function(n){return function(e){var i=(e||{}).container;if(!i)throw new Error(hs("The `container` option is required in the widget within the panel."));var t={header:"",footer:"",collapseButtonText:function(e){var t=e.collapsed;return'<svg\n          class="'.concat(f.collapseIcon,'"\n          width="1em"\n          height="1em"\n          viewBox="0 0 500 500"\n        >\n        <path d="').concat(t?"M100 250l300-150v300z":"M250 400l150-300H100z",'" fill="currentColor" />\n        </svg>')}},a=function(e){var a=e.containerNode,s=e.bodyContainerNode,o=e.cssClasses,c=e.templates;return function(e){var t=e.options,n=e.hidden,r=e.collapsible,i=e.collapsed;Ln(vn(ss,{cssClasses:o,hidden:n,collapsible:r,isCollapsed:i,templates:c,data:t,bodyElement:s}),a)}}({containerNode:ce(i),bodyContainerNode:u,cssClasses:f,templates:D({},t,{},r)});a({options:{},hidden:!0,collapsible:l,collapsed:!1});var s=n(D({},e,{container:u}));return D({},s,{dispose:function(){if(Ln(null,ce(i)),"function"==typeof s.dispose){for(var e,t=arguments.length,n=new Array(t),r=0;r<t;r++)n[r]=arguments[r];return(e=s.dispose).call.apply(e,[this].concat(n))}},render:function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r,i=t[0];a({options:i,hidden:Boolean(o(i)),collapsible:l,collapsed:Boolean(h(i))}),"function"==typeof s.render&&(r=s.render).call.apply(r,[this].concat(t))}})}}},voiceSearch:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.container,r=t.cssClasses,i=void 0===r?{}:r,a=t.templates,s=t.searchAsYouSpeak,o=void 0!==s&&s,c=t.language,u=t.additionalQueryParameters,l=t.createVoiceSearchHelper;if(!n)throw new Error(ms("The `container` option is required."));var h=ce(n),f={root:qr(ps(),i.root),button:qr(ps({descendantName:"button"}),i.button),status:qr(ps({descendantName:"status"}),i.status)};return Dr(cs,function(){return Ln(null,h)})({container:h,cssClasses:f,templates:D({},ds,{},a),searchAsYouSpeak:o,language:c,additionalQueryParameters:u,createVoiceSearchHelper:l})},queryRuleCustomData:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.container,r=t.cssClasses,i=void 0===r?{}:r,a=t.templates,s=void 0===a?{}:a,o=t.transformItems,c=void 0===o?function(e){return e}:o;if(!n)throw new Error(vs("The `container` option is required."));var u={root:qr(gs(),i.root)},l=D({},{default:function(e){var t=e.items;return JSON.stringify(t,null,2)}},{},s),h=ce(n);return D({},Ar(ls,function(){Ln(null,h)})({container:h,cssClasses:u,templates:l,transformItems:c}),{$$type:"ais.queryRuleCustomData"})},queryRuleContext:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.trackedFilters,r=t.transformRuleContexts;if(!n)throw new Error(ys("The `trackedFilters` option is required."));return D({},Ar(_e)({trackedFilters:n,transformRuleContexts:r}),{$$type:"ais.queryRuleContext"})},index:Ze,places:function(e){var t=e||{},n=t.placesReference,r=void 0===n?void 0:n,i=t.defaultPosition,o=void 0===i?[]:i,a=A(t,["placesReference","defaultPosition"]);if("function"!=typeof r)throw new Error("The `placesReference` option requires a valid Places.js reference.");var c=r(a),u={query:"",initialLatLngViaIP:void 0,isInitialLatLngViaIPSet:!1};return{$$type:"ais.places",init:function(e){var s=e.helper;c.on("change",function(e){var t=e.suggestion,n=t.value,r=t.latlng,i=r.lat,a=r.lng;u.query=n,s.setQueryParameter("insideBoundingBox",void 0).setQueryParameter("aroundLatLngViaIP",!1).setQueryParameter("aroundLatLng","".concat(i,",").concat(a)).search()}),c.on("clear",function(){u.query="",s.setQueryParameter("insideBoundingBox",void 0),1<o.length?s.setQueryParameter("aroundLatLngViaIP",!1).setQueryParameter("aroundLatLng",o.join(",")):s.setQueryParameter("aroundLatLngViaIP",u.initialLatLngViaIP).setQueryParameter("aroundLatLng",void 0),s.search()})},getWidgetState:function(e,t){var n=t.searchParameters.aroundLatLng||o.join(",");if(n!==o.join(",")||u.query)return D({},e,{places:{query:u.query,position:n}});e.places;return A(e,["places"])},getWidgetSearchParameters:function(e,t){var n=t.uiState.places||{},r=n.query,i=void 0===r?"":r,a=n.position,s=void 0===a?o.join(","):a;return u.query=i,u.isInitialLatLngViaIPSet||(u.isInitialLatLngViaIPSet=!0,u.initialLatLngViaIP=e.aroundLatLngViaIP),c.setVal(i),c.close(),e.setQueryParameter("insideBoundingBox",void 0).setQueryParameter("aroundLatLngViaIP",!1).setQueryParameter("aroundLatLng",s||void 0)}}}}),Rs=Object.freeze({__proto__:null,createInsightsMiddleware:function(e){var t=e||{},n=t.insightsClient,r=t.onEvent;if(null!==n&&!n)throw new Error("The `insightsClient` option is required. To disable, set it to `null`.");var s=Boolean(n),o=null===n?_e:n;return function(e){var a=e.instantSearchInstance;return o("_get","_hasCredentials",function(e){if(!e){var t=Q(function(e){if(e.transporter){var t=e.transporter,n=t.headers,r=t.queryParameters,i="x-algolia-application-id",a="x-algolia-api-key";return[n[i]||r[i],n[a]||r[a]]}return[e.applicationID,e.apiKey]}(a.client),2),n=t[0],r=t[1];o("_get","_userToken",function(e){}),o("init",{appId:n,apiKey:r})}}),{onStateChange:function(){},subscribe:function(){function i(e){e&&a.mainIndex.getHelper().setQueryParameter("userToken",e)}a.mainIndex.getHelper().setQueryParameter("clickAnalytics",!0),s&&i(ht()),Array.isArray(o.queue)&&o.queue.forEach(function(e){var t=Q(e,2),n=t[0],r=t[1];"setUserToken"===n&&i(r)}),o("onUserTokenChange",i,{immediate:!0}),a.sendEventToInsights=function(e){r?r(e,n):e.insightsMethod&&o(e.insightsMethod,e.payload)}},unsubscribe:function(){o("onUserTokenChange",void 0),a.sendEventToInsights=_e}}}},createRouterMiddleware:Qt}),ws=Object.freeze({__proto__:null,history:Bt});function Ss(e){e.configure;return A(e,["configure"])}var Ps=Object.freeze({__proto__:null,simple:dt,singleIndex:function(t){return{stateToRoute:function(e){return Ss(e[t]||{})},routeToState:function(e){return L({},t,Ss(0<arguments.length&&void 0!==e?e:{}))}}}});function _s(e){var t=e||{};t.page;return A(t,["page"])}var Ns="ais.infiniteHits";function xs(){return"undefined"!=typeof window&&void 0!==window.sessionStorage}function Fs(e){return new Wt(e)}return Fs.routers=ws,Fs.stateMappings=Ps,Fs.connectors=Qr,Fs.widgets=bs,Fs.version="4.8.3",Fs.createInfiniteHitsSessionStorageCache=function(){return{read:function(e){var t=e.state;if(!xs())return null;try{var n=JSON.parse(window.sessionStorage.getItem(Ns));return n&&Te(n.state,_s(t))?n.hits:null}catch(e){if(e instanceof SyntaxError)try{window.sessionStorage.removeItem(Ns)}catch(e){}return null}},write:function(e){var t=e.state,n=e.hits;if(xs())try{window.sessionStorage.setItem(Ns,JSON.stringify({state:_s(t),hits:n}))}catch(e){}}}},Fs.highlight=ot,Fs.snippet=ut,Fs.insights=lt,Fs.middlewares=Rs,Fs});
+!function(e,t){"object"==typeof exports&&"undefined"!=typeof module?module.exports=t():"function"==typeof define&&define.amd?define(t):(e=e||self).instantsearch=t()}(this,function(){"use strict";function h(e){return(h="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e})(e)}function k(e,t){if(!(e instanceof t))throw new TypeError("Cannot call a class as a function")}function r(e,t){for(var n=0;n<t.length;n++){var r=t[n];r.enumerable=r.enumerable||!1,r.configurable=!0,"value"in r&&(r.writable=!0),Object.defineProperty(e,r.key,r)}}function M(e,t,n){return t&&r(e.prototype,t),n&&r(e,n),e}function L(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function f(){return(f=Object.assign||function(e){for(var t=1;t<arguments.length;t++){var n=arguments[t];for(var r in n)Object.prototype.hasOwnProperty.call(n,r)&&(e[r]=n[r])}return e}).apply(this,arguments)}function i(t,e){var n=Object.keys(t);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(t);e&&(r=r.filter(function(e){return Object.getOwnPropertyDescriptor(t,e).enumerable})),n.push.apply(n,r)}return n}function D(t){for(var e=1;e<arguments.length;e++){var n=null!=arguments[e]?arguments[e]:{};e%2?i(Object(n),!0).forEach(function(e){L(t,e,n[e])}):Object.getOwnPropertyDescriptors?Object.defineProperties(t,Object.getOwnPropertyDescriptors(n)):i(Object(n)).forEach(function(e){Object.defineProperty(t,e,Object.getOwnPropertyDescriptor(n,e))})}return t}function j(e,t){if("function"!=typeof t&&null!==t)throw new TypeError("Super expression must either be null or a function");e.prototype=Object.create(t&&t.prototype,{constructor:{value:e,writable:!0,configurable:!0}}),t&&n(e,t)}function O(e){return(O=Object.setPrototypeOf?Object.getPrototypeOf:function(e){return e.__proto__||Object.getPrototypeOf(e)})(e)}function n(e,t){return(n=Object.setPrototypeOf||function(e,t){return e.__proto__=t,e})(e,t)}function A(e,t){if(null==e)return{};var n,r,i=function(e,t){if(null==e)return{};var n,r,i={},a=Object.keys(e);for(r=0;r<a.length;r++)n=a[r],0<=t.indexOf(n)||(i[n]=e[n]);return i}(e,t);if(Object.getOwnPropertySymbols){var a=Object.getOwnPropertySymbols(e);for(r=0;r<a.length;r++)n=a[r],0<=t.indexOf(n)||Object.prototype.propertyIsEnumerable.call(e,n)&&(i[n]=e[n])}return i}function H(e){if(void 0===e)throw new ReferenceError("this hasn't been initialised - super() hasn't been called");return e}function B(e,t){return!t||"object"!=typeof t&&"function"!=typeof t?H(e):t}function Q(e,t){return function(e){if(Array.isArray(e))return e}(e)||function(e,t){if(!(Symbol.iterator in Object(e)||"[object Arguments]"===Object.prototype.toString.call(e)))return;var n=[],r=!0,i=!1,a=void 0;try{for(var s,o=e[Symbol.iterator]();!(r=(s=o.next()).done)&&(n.push(s.value),!t||n.length!==t);r=!0);}catch(e){i=!0,a=e}finally{try{r||null==o.return||o.return()}finally{if(i)throw a}}return n}(e,t)||function(){throw new TypeError("Invalid attempt to destructure non-iterable instance")}()}function _(e){return function(e){if(Array.isArray(e)){for(var t=0,n=new Array(e.length);t<e.length;t++)n[t]=e[t];return n}}(e)||function(e){if(Symbol.iterator in Object(e)||"[object Arguments]"===Object.prototype.toString.call(e))return Array.from(e)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance")}()}function s(e){return"function"==typeof e||Array.isArray(e)||"[object Object]"===Object.prototype.toString.call(e)}function o(e,t){if(e===t)return e;for(var n in t)if(Object.prototype.hasOwnProperty.call(t,n)){var r=t[n],i=e[n];void 0!==i&&void 0===r||(s(i)&&s(r)?e[n]=o(i,r):e[n]="object"==typeof(a=r)&&null!==a?o(Array.isArray(a)?[]:{},a):a)}var a;return e}function m(){return Array.prototype.slice.call(arguments).reduceRight(function(t,n){return Object.keys(Object(n)).forEach(function(e){void 0!==n[e]&&(void 0!==t[e]&&delete t[e],t[e]=n[e])}),t},{})}var p=function(e){s(e)||(e={});for(var t=1,n=arguments.length;t<n;t++){var r=arguments[t];s(r)&&o(e,r)}return e};var a=function(n,r){return n.filter(function(e,t){return-1<r.indexOf(e)&&n.indexOf(e)===t})},v=function(e,t){if(Array.isArray(e))for(var n=0;n<e.length;n++)if(t(e[n]))return e[n]};var c=function e(t){if("number"==typeof t)return t;if("string"==typeof t)return parseFloat(t);if(Array.isArray(t))return t.map(e);throw new Error("The value should be a number, a parsable string or an array of those.")};var u=function(e,t){if(null===e)return{};var n,r,i={},a=Object.keys(e);for(r=0;r<a.length;r++)n=a[r],0<=t.indexOf(n)||(i[n]=e[n]);return i};var l=function(e){return e&&0<Object.keys(e).length},d={addRefinement:function(e,t,n){if(d.isRefined(e,t,n))return e;var r=""+n,i=e[t]?e[t].concat(r):[r],a={};return a[t]=i,m({},a,e)},removeRefinement:function(e,n,t){if(void 0===t)return d.clearRefinement(e,function(e,t){return n===t});var r=""+t;return d.clearRefinement(e,function(e,t){return n===t&&r===e})},toggleRefinement:function(e,t,n){if(void 0===n)throw new Error("toggleRefinement should be used with a value");return d.isRefined(e,t,n)?d.removeRefinement(e,t,n):d.addRefinement(e,t,n)},clearRefinement:function(i,a,s){if(void 0===a)return l(i)?{}:i;if("string"==typeof a)return u(i,[a]);if("function"==typeof a){var o=!1,e=Object.keys(i).reduce(function(e,t){var n=i[t]||[],r=n.filter(function(e){return!a(e,t,s)});return r.length!==n.length&&(o=!0),e[t]=r,e},{});return o?e:i}},isRefined:function(e,t,n){var r=!!e[t]&&0<e[t].length;if(void 0===n||!r)return r;var i=""+n;return-1!==e[t].indexOf(i)}},g=d;function y(e,n){return Array.isArray(e)&&Array.isArray(n)?e.length===n.length&&e.every(function(e,t){return y(n[t],e)}):e===n}function b(e){var r=e?b._parseNumbers(e):{};this.facets=r.facets||[],this.disjunctiveFacets=r.disjunctiveFacets||[],this.hierarchicalFacets=r.hierarchicalFacets||[],this.facetsRefinements=r.facetsRefinements||{},this.facetsExcludes=r.facetsExcludes||{},this.disjunctiveFacetsRefinements=r.disjunctiveFacetsRefinements||{},this.numericRefinements=r.numericRefinements||{},this.tagRefinements=r.tagRefinements||[],this.hierarchicalFacetsRefinements=r.hierarchicalFacetsRefinements||{};var i=this;Object.keys(r).forEach(function(e){var t=-1!==b.PARAMETERS.indexOf(e),n=void 0!==r[e];!t&&n&&(i[e]=r[e])})}b.PARAMETERS=Object.keys(new b),b._parseNumbers=function(i){if(i instanceof b)return i;var r={};if(["aroundPrecision","aroundRadius","getRankingInfo","minWordSizefor2Typos","minWordSizefor1Typo","page","maxValuesPerFacet","distinct","minimumAroundRadius","hitsPerPage","minProximity"].forEach(function(e){var t=i[e];if("string"==typeof t){var n=parseFloat(t);r[e]=isNaN(n)?t:n}}),Array.isArray(i.insideBoundingBox)&&(r.insideBoundingBox=i.insideBoundingBox.map(function(e){return Array.isArray(e)?e.map(function(e){return parseFloat(e)}):e})),i.numericRefinements){var a={};Object.keys(i.numericRefinements).forEach(function(n){var r=i.numericRefinements[n]||{};a[n]={},Object.keys(r).forEach(function(e){var t=r[e].map(function(e){return Array.isArray(e)?e.map(function(e){return"string"==typeof e?parseFloat(e):e}):"string"==typeof e?parseFloat(e):e});a[n][e]=t})}),r.numericRefinements=a}return p({},i,r)},b.make=function(e){var n=new b(e);return(e.hierarchicalFacets||[]).forEach(function(e){if(e.rootPath){var t=n.getHierarchicalRefinement(e.name);0<t.length&&0!==t[0].indexOf(e.rootPath)&&(n=n.clearRefinements(e.name)),0===(t=n.getHierarchicalRefinement(e.name)).length&&(n=n.toggleHierarchicalFacetRefinement(e.name,e.rootPath))}}),n},b.validate=function(e,t){var n=t||{};return e.tagFilters&&n.tagRefinements&&0<n.tagRefinements.length?new Error("[Tags] Cannot switch from the managed tag API to the advanced API. It is probably an error, if it is really what you want, you should first clear the tags with clearTags method."):0<e.tagRefinements.length&&n.tagFilters?new Error("[Tags] Cannot switch from the advanced tag API to the managed API. It is probably an error, if it is not, you should first clear the tags with clearTags method."):e.numericFilters&&n.numericRefinements&&l(n.numericRefinements)?new Error("[Numeric filters] Can't switch from the advanced to the managed API. It is probably an error, if this is really what you want, you have to first clear the numeric filters."):l(e.numericRefinements)&&n.numericFilters?new Error("[Numeric filters] Can't switch from the managed API to the advanced. It is probably an error, if this is really what you want, you have to first clear the numeric filters."):null},b.prototype={constructor:b,clearRefinements:function(e){var t={numericRefinements:this._clearNumericRefinements(e),facetsRefinements:g.clearRefinement(this.facetsRefinements,e,"conjunctiveFacet"),facetsExcludes:g.clearRefinement(this.facetsExcludes,e,"exclude"),disjunctiveFacetsRefinements:g.clearRefinement(this.disjunctiveFacetsRefinements,e,"disjunctiveFacet"),hierarchicalFacetsRefinements:g.clearRefinement(this.hierarchicalFacetsRefinements,e,"hierarchicalFacet")};return t.numericRefinements===this.numericRefinements&&t.facetsRefinements===this.facetsRefinements&&t.facetsExcludes===this.facetsExcludes&&t.disjunctiveFacetsRefinements===this.disjunctiveFacetsRefinements&&t.hierarchicalFacetsRefinements===this.hierarchicalFacetsRefinements?this:this.setQueryParameters(t)},clearTags:function(){return void 0===this.tagFilters&&0===this.tagRefinements.length?this:this.setQueryParameters({tagFilters:void 0,tagRefinements:[]})},setIndex:function(e){return e===this.index?this:this.setQueryParameters({index:e})},setQuery:function(e){return e===this.query?this:this.setQueryParameters({query:e})},setPage:function(e){return e===this.page?this:this.setQueryParameters({page:e})},setFacets:function(e){return this.setQueryParameters({facets:e})},setDisjunctiveFacets:function(e){return this.setQueryParameters({disjunctiveFacets:e})},setHitsPerPage:function(e){return this.hitsPerPage===e?this:this.setQueryParameters({hitsPerPage:e})},setTypoTolerance:function(e){return this.typoTolerance===e?this:this.setQueryParameters({typoTolerance:e})},addNumericRefinement:function(e,t,n){var r=c(n);if(this.isNumericRefined(e,t,r))return this;var i=p({},this.numericRefinements);return i[e]=p({},i[e]),i[e][t]?(i[e][t]=i[e][t].slice(),i[e][t].push(r)):i[e][t]=[r],this.setQueryParameters({numericRefinements:i})},getConjunctiveRefinements:function(e){return this.isConjunctiveFacet(e)&&this.facetsRefinements[e]||[]},getDisjunctiveRefinements:function(e){return this.isDisjunctiveFacet(e)&&this.disjunctiveFacetsRefinements[e]||[]},getHierarchicalRefinement:function(e){return this.hierarchicalFacetsRefinements[e]||[]},getExcludeRefinements:function(e){return this.isConjunctiveFacet(e)&&this.facetsExcludes[e]||[]},removeNumericRefinement:function(n,r,i){return void 0!==i?this.isNumericRefined(n,r,i)?this.setQueryParameters({numericRefinements:this._clearNumericRefinements(function(e,t){return t===n&&e.op===r&&y(e.val,c(i))})}):this:void 0!==r?this.isNumericRefined(n,r)?this.setQueryParameters({numericRefinements:this._clearNumericRefinements(function(e,t){return t===n&&e.op===r})}):this:this.isNumericRefined(n)?this.setQueryParameters({numericRefinements:this._clearNumericRefinements(function(e,t){return t===n})}):this},getNumericRefinements:function(e){return this.numericRefinements[e]||{}},getNumericRefinement:function(e,t){return this.numericRefinements[e]&&this.numericRefinements[e][t]},_clearNumericRefinements:function(s){if(void 0===s)return l(this.numericRefinements)?{}:this.numericRefinements;if("string"==typeof s)return l(this.numericRefinements[s])?u(this.numericRefinements,[s]):this.numericRefinements;if("function"==typeof s){var o=!1,t=this.numericRefinements,e=Object.keys(t).reduce(function(e,r){var i=t[r],a={};return i=i||{},Object.keys(i).forEach(function(t){var e=i[t]||[],n=[];e.forEach(function(e){s({val:e,op:t},r,"numeric")||n.push(e)}),n.length!==e.length&&(o=!0),a[t]=n}),e[r]=a,e},{});return o?e:this.numericRefinements}},addFacet:function(e){return this.isConjunctiveFacet(e)?this:this.setQueryParameters({facets:this.facets.concat([e])})},addDisjunctiveFacet:function(e){return this.isDisjunctiveFacet(e)?this:this.setQueryParameters({disjunctiveFacets:this.disjunctiveFacets.concat([e])})},addHierarchicalFacet:function(e){if(this.isHierarchicalFacet(e.name))throw new Error("Cannot declare two hierarchical facets with the same name: `"+e.name+"`");return this.setQueryParameters({hierarchicalFacets:this.hierarchicalFacets.concat([e])})},addFacetRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return g.isRefined(this.facetsRefinements,e,t)?this:this.setQueryParameters({facetsRefinements:g.addRefinement(this.facetsRefinements,e,t)})},addExcludeRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return g.isRefined(this.facetsExcludes,e,t)?this:this.setQueryParameters({facetsExcludes:g.addRefinement(this.facetsExcludes,e,t)})},addDisjunctiveFacetRefinement:function(e,t){if(!this.isDisjunctiveFacet(e))throw new Error(e+" is not defined in the disjunctiveFacets attribute of the helper configuration");return g.isRefined(this.disjunctiveFacetsRefinements,e,t)?this:this.setQueryParameters({disjunctiveFacetsRefinements:g.addRefinement(this.disjunctiveFacetsRefinements,e,t)})},addTagRefinement:function(e){if(this.isTagRefined(e))return this;var t={tagRefinements:this.tagRefinements.concat(e)};return this.setQueryParameters(t)},removeFacet:function(t){return this.isConjunctiveFacet(t)?this.clearRefinements(t).setQueryParameters({facets:this.facets.filter(function(e){return e!==t})}):this},removeDisjunctiveFacet:function(t){return this.isDisjunctiveFacet(t)?this.clearRefinements(t).setQueryParameters({disjunctiveFacets:this.disjunctiveFacets.filter(function(e){return e!==t})}):this},removeHierarchicalFacet:function(t){return this.isHierarchicalFacet(t)?this.clearRefinements(t).setQueryParameters({hierarchicalFacets:this.hierarchicalFacets.filter(function(e){return e.name!==t})}):this},removeFacetRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return g.isRefined(this.facetsRefinements,e,t)?this.setQueryParameters({facetsRefinements:g.removeRefinement(this.facetsRefinements,e,t)}):this},removeExcludeRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return g.isRefined(this.facetsExcludes,e,t)?this.setQueryParameters({facetsExcludes:g.removeRefinement(this.facetsExcludes,e,t)}):this},removeDisjunctiveFacetRefinement:function(e,t){if(!this.isDisjunctiveFacet(e))throw new Error(e+" is not defined in the disjunctiveFacets attribute of the helper configuration");return g.isRefined(this.disjunctiveFacetsRefinements,e,t)?this.setQueryParameters({disjunctiveFacetsRefinements:g.removeRefinement(this.disjunctiveFacetsRefinements,e,t)}):this},removeTagRefinement:function(t){if(!this.isTagRefined(t))return this;var e={tagRefinements:this.tagRefinements.filter(function(e){return e!==t})};return this.setQueryParameters(e)},toggleRefinement:function(e,t){return this.toggleFacetRefinement(e,t)},toggleFacetRefinement:function(e,t){if(this.isHierarchicalFacet(e))return this.toggleHierarchicalFacetRefinement(e,t);if(this.isConjunctiveFacet(e))return this.toggleConjunctiveFacetRefinement(e,t);if(this.isDisjunctiveFacet(e))return this.toggleDisjunctiveFacetRefinement(e,t);throw new Error("Cannot refine the undeclared facet "+e+"; it should be added to the helper options facets, disjunctiveFacets or hierarchicalFacets")},toggleConjunctiveFacetRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return this.setQueryParameters({facetsRefinements:g.toggleRefinement(this.facetsRefinements,e,t)})},toggleExcludeFacetRefinement:function(e,t){if(!this.isConjunctiveFacet(e))throw new Error(e+" is not defined in the facets attribute of the helper configuration");return this.setQueryParameters({facetsExcludes:g.toggleRefinement(this.facetsExcludes,e,t)})},toggleDisjunctiveFacetRefinement:function(e,t){if(!this.isDisjunctiveFacet(e))throw new Error(e+" is not defined in the disjunctiveFacets attribute of the helper configuration");return this.setQueryParameters({disjunctiveFacetsRefinements:g.toggleRefinement(this.disjunctiveFacetsRefinements,e,t)})},toggleHierarchicalFacetRefinement:function(e,t){if(!this.isHierarchicalFacet(e))throw new Error(e+" is not defined in the hierarchicalFacets attribute of the helper configuration");var n=this._getHierarchicalFacetSeparator(this.getHierarchicalFacetByName(e)),r={};return void 0!==this.hierarchicalFacetsRefinements[e]&&0<this.hierarchicalFacetsRefinements[e].length&&(this.hierarchicalFacetsRefinements[e][0]===t||0===this.hierarchicalFacetsRefinements[e][0].indexOf(t+n))?-1===t.indexOf(n)?r[e]=[]:r[e]=[t.slice(0,t.lastIndexOf(n))]:r[e]=[t],this.setQueryParameters({hierarchicalFacetsRefinements:m({},r,this.hierarchicalFacetsRefinements)})},addHierarchicalFacetRefinement:function(e,t){if(this.isHierarchicalFacetRefined(e))throw new Error(e+" is already refined.");if(!this.isHierarchicalFacet(e))throw new Error(e+" is not defined in the hierarchicalFacets attribute of the helper configuration.");var n={};return n[e]=[t],this.setQueryParameters({hierarchicalFacetsRefinements:m({},n,this.hierarchicalFacetsRefinements)})},removeHierarchicalFacetRefinement:function(e){if(!this.isHierarchicalFacetRefined(e))return this;var t={};return t[e]=[],this.setQueryParameters({hierarchicalFacetsRefinements:m({},t,this.hierarchicalFacetsRefinements)})},toggleTagRefinement:function(e){return this.isTagRefined(e)?this.removeTagRefinement(e):this.addTagRefinement(e)},isDisjunctiveFacet:function(e){return-1<this.disjunctiveFacets.indexOf(e)},isHierarchicalFacet:function(e){return void 0!==this.getHierarchicalFacetByName(e)},isConjunctiveFacet:function(e){return-1<this.facets.indexOf(e)},isFacetRefined:function(e,t){return!!this.isConjunctiveFacet(e)&&g.isRefined(this.facetsRefinements,e,t)},isExcludeRefined:function(e,t){return!!this.isConjunctiveFacet(e)&&g.isRefined(this.facetsExcludes,e,t)},isDisjunctiveFacetRefined:function(e,t){return!!this.isDisjunctiveFacet(e)&&g.isRefined(this.disjunctiveFacetsRefinements,e,t)},isHierarchicalFacetRefined:function(e,t){if(!this.isHierarchicalFacet(e))return!1;var n=this.getHierarchicalRefinement(e);return t?-1!==n.indexOf(t):0<n.length},isNumericRefined:function(e,t,n){if(void 0===n&&void 0===t)return!!this.numericRefinements[e];var r=this.numericRefinements[e]&&void 0!==this.numericRefinements[e][t];if(void 0===n||!r)return r;var i=c(n),a=void 0!==function(e,t){return v(e,function(e){return y(e,t)})}(this.numericRefinements[e][t],i);return r&&a},isTagRefined:function(e){return-1!==this.tagRefinements.indexOf(e)},getRefinedDisjunctiveFacets:function(){var t=this,e=a(Object.keys(this.numericRefinements).filter(function(e){return 0<Object.keys(t.numericRefinements[e]).length}),this.disjunctiveFacets);return Object.keys(this.disjunctiveFacetsRefinements).filter(function(e){return 0<t.disjunctiveFacetsRefinements[e].length}).concat(e).concat(this.getRefinedHierarchicalFacets())},getRefinedHierarchicalFacets:function(){var t=this;return a(this.hierarchicalFacets.map(function(e){return e.name}),Object.keys(this.hierarchicalFacetsRefinements).filter(function(e){return 0<t.hierarchicalFacetsRefinements[e].length}))},getUnrefinedDisjunctiveFacets:function(){var t=this.getRefinedDisjunctiveFacets();return this.disjunctiveFacets.filter(function(e){return-1===t.indexOf(e)})},managedParameters:["index","facets","disjunctiveFacets","facetsRefinements","facetsExcludes","disjunctiveFacetsRefinements","numericRefinements","tagRefinements","hierarchicalFacets","hierarchicalFacetsRefinements"],getQueryParams:function(){var n=this.managedParameters,r={},i=this;return Object.keys(this).forEach(function(e){var t=i[e];-1===n.indexOf(e)&&void 0!==t&&(r[e]=t)}),r},setQueryParameter:function(e,t){if(this[e]===t)return this;var n={};return n[e]=t,this.setQueryParameters(n)},setQueryParameters:function(e){if(!e)return this;var t=b.validate(this,e);if(t)throw t;var n=this,i=b._parseNumbers(e),r=Object.keys(this).reduce(function(e,t){return e[t]=n[t],e},{}),a=Object.keys(i).reduce(function(e,t){var n=void 0!==e[t],r=void 0!==i[t];return n&&!r?u(e,[t]):(r&&(e[t]=i[t]),e)},r);return new this.constructor(a)},resetPage:function(){return void 0===this.page?this:this.setPage(0)},_getHierarchicalFacetSortBy:function(e){return e.sortBy||["isRefined:desc","name:asc"]},_getHierarchicalFacetSeparator:function(e){return e.separator||" > "},_getHierarchicalRootPath:function(e){return e.rootPath||null},_getHierarchicalShowParentLevel:function(e){return"boolean"!=typeof e.showParentLevel||e.showParentLevel},getHierarchicalFacetByName:function(t){return v(this.hierarchicalFacets,function(e){return e.name===t})},getHierarchicalFacetBreadcrumb:function(e){if(!this.isHierarchicalFacet(e))return[];var t=this.getHierarchicalRefinement(e)[0];if(!t)return[];var n=this._getHierarchicalFacetSeparator(this.getHierarchicalFacetByName(e));return t.split(n).map(function(e){return e.trim()})},toString:function(){return JSON.stringify(this,null,2)}};var R=b;function w(e,t){if(e!==t){var n=void 0!==e,r=null===e,i=void 0!==t,a=null===t;if(!a&&t<e||r&&i||!n)return 1;if(!r&&e<t||a&&n||!i)return-1}return 0}function t(e){return Array.isArray(e)?e.filter(Boolean):[]}function S(e,t){if(!Array.isArray(e))return-1;for(var n=0;n<e.length;n++)if(t(e[n]))return n;return-1}function P(e,t){var i=(t||[]).map(function(e){return e.split(":")});return e.reduce(function(e,t){var n=t.split(":"),r=v(i,function(e){return e[0]===n[0]});return 1<n.length||!r?(e[0].push(n[0]),e[1].push(n[1])):(e[0].push(r[0]),e[1].push(r[1])),e},[[],[]])}var N=function(e,n,i){if(!Array.isArray(e))return[];Array.isArray(i)||(i=[]);var t=e.map(function(t,e){return{criteria:n.map(function(e){return t[e]}),index:e,value:t}});return t.sort(function(e,t){for(var n=-1;++n<e.criteria.length;){var r=w(e.criteria[n],t.criteria[n]);if(r)return n>=i.length?r:"desc"===i[n]?-r:r}return e.index-t.index}),t.map(function(e){return e.value})},x=function(h){return function(e,t){var n=h.hierarchicalFacets[t],r=h.hierarchicalFacetsRefinements[n.name]&&h.hierarchicalFacetsRefinements[n.name][0]||"",i=h._getHierarchicalFacetSeparator(n),a=h._getHierarchicalRootPath(n),s=h._getHierarchicalShowParentLevel(n),o=P(h._getHierarchicalFacetSortBy(n)),c=e.every(function(e){return e.exhaustive}),u=function(o,c,u,l,h){return function(e,n,t){var r=e;if(0<t){var i=0;for(r=e;i<t;){var a=r&&Array.isArray(r.data)?r.data:[];r=v(a,function(e){return e.isRefined}),i++}}if(r){var s=Object.keys(n.data).map(function(e){return[e,n.data[e]]}).filter(function(e){return function(e,t,n,r,i,a){return(!i||0===e.indexOf(i)&&i!==e)&&(!i&&-1===e.indexOf(r)||i&&e.split(r).length-i.split(r).length==1||-1===e.indexOf(r)&&-1===n.indexOf(r)||0===n.indexOf(e)||0===e.indexOf(t+r)&&(a||0===e.indexOf(n)))}(e[0],r.path||u,h,c,u,l)});r.data=N(s.map(function(e){var t=e[0];return function(e,t,n,r,i){var a=t.split(n);return{name:a[a.length-1].trim(),path:t,count:e,isRefined:r===t||0===r.indexOf(t+n),exhaustive:i,data:null}}(e[1],t,c,h,n.exhaustive)}),o[0],o[1])}return e}}(o,i,a,s,r),l=e;return a&&(l=e.slice(a.split(i).length)),l.reduce(u,{name:h.hierarchicalFacets[t].name,count:null,isRefined:!0,path:null,exhaustive:c,data:null})}};function F(e){var n={};return e.forEach(function(e,t){n[e]=t}),n}function I(e,t,n){t&&t[n]&&(e.stats=t[n])}function C(l,n){var c=n[0];this._rawResults=n;var h=this;Object.keys(c).forEach(function(e){h[e]=c[e]}),this.processingTimeMS=n.reduce(function(e,t){return void 0===t.processingTimeMS?e:e+t.processingTimeMS},0),this.disjunctiveFacets=[],this.hierarchicalFacets=l.hierarchicalFacets.map(function(){return[]}),this.facets=[];var e=l.getRefinedDisjunctiveFacets(),u=F(l.facets),f=F(l.disjunctiveFacets),r=1,d=c.facets||{};Object.keys(d).forEach(function(e){var t=d[e],n=function(e,t){return v(e,function(e){return-1<(e.attributes||[]).indexOf(t)})}(l.hierarchicalFacets,e);if(n){var r=n.attributes.indexOf(e),i=S(l.hierarchicalFacets,function(e){return e.name===n.name});h.hierarchicalFacets[i][r]={attribute:e,data:t,exhaustive:c.exhaustiveFacetsCount}}else{var a,s=-1!==l.disjunctiveFacets.indexOf(e),o=-1!==l.facets.indexOf(e);s&&(a=f[e],h.disjunctiveFacets[a]={name:e,data:t,exhaustive:c.exhaustiveFacetsCount},I(h.disjunctiveFacets[a],c.facets_stats,e)),o&&(a=u[e],h.facets[a]={name:e,data:t,exhaustive:c.exhaustiveFacetsCount},I(h.facets[a],c.facets_stats,e))}}),this.hierarchicalFacets=t(this.hierarchicalFacets),e.forEach(function(e){var a=n[r],s=a&&a.facets?a.facets:{},o=l.getHierarchicalFacetByName(e);Object.keys(s).forEach(function(t){var n,e=s[t];if(o){n=S(l.hierarchicalFacets,function(e){return e.name===o.name});var r=S(h.hierarchicalFacets[n],function(e){return e.attribute===t});if(-1===r)return;h.hierarchicalFacets[n][r].data=p({},h.hierarchicalFacets[n][r].data,e)}else{n=f[t];var i=c.facets&&c.facets[t]||{};h.disjunctiveFacets[n]={name:t,data:m({},e,i),exhaustive:a.exhaustiveFacetsCount},I(h.disjunctiveFacets[n],a.facets_stats,t),l.disjunctiveFacetsRefinements[t]&&l.disjunctiveFacetsRefinements[t].forEach(function(e){!h.disjunctiveFacets[n].data[e]&&-1<l.disjunctiveFacetsRefinements[t].indexOf(e)&&(h.disjunctiveFacets[n].data[e]=0)})}}),r++}),l.getRefinedHierarchicalFacets().forEach(function(e){var s=l.getHierarchicalFacetByName(e),o=l._getHierarchicalFacetSeparator(s),c=l.getHierarchicalRefinement(e);if(!(0===c.length||c[0].split(o).length<2)){var t=n[r],u=t&&t.facets?t.facets:{};Object.keys(u).forEach(function(t){var e=u[t],n=S(l.hierarchicalFacets,function(e){return e.name===s.name}),r=S(h.hierarchicalFacets[n],function(e){return e.attribute===t});if(-1!==r){var i={};if(0<c.length){var a=c[0].split(o)[0];i[a]=h.hierarchicalFacets[n][r].data[a]}h.hierarchicalFacets[n][r].data=m(i,e,h.hierarchicalFacets[n][r].data)}}),r++}}),Object.keys(l.facetsExcludes).forEach(function(t){var e=l.facetsExcludes[t],n=u[t];h.facets[n]={name:t,data:c.facets[t],exhaustive:c.exhaustiveFacetsCount},e.forEach(function(e){h.facets[n]=h.facets[n]||{name:t},h.facets[n].data=h.facets[n].data||{},h.facets[n].data[e]=0})}),this.hierarchicalFacets=this.hierarchicalFacets.map(x(l)),this.facets=t(this.facets),this.disjunctiveFacets=t(this.disjunctiveFacets),this._state=l}function T(t,e){if(!e.data||0===e.data.length)return e;var n=e.data.map(function(e){return T(t,e)}),r=t(n);return p({},e,{data:r})}function E(e,t){var n=v(e,function(e){return e.name===t});return n&&n.stats}function q(e,t,n,r,i){var a=v(i,function(e){return e.name===n}),s=a&&a.data&&a.data[r]?a.data[r]:0,o=a&&a.exhaustive||!1;return{type:t,attributeName:n,name:r,count:s,exhaustive:o}}C.prototype.getFacetByName=function(t){function e(e){return e.name===t}return v(this.facets,e)||v(this.disjunctiveFacets,e)||v(this.hierarchicalFacets,e)},C.DEFAULT_SORT=["isRefined:desc","count:desc","name:asc"],C.prototype.getFacetValues=function(e,t){var n=function(t,n){function e(e){return e.name===n}if(t._state.isConjunctiveFacet(n)){var r=v(t.facets,e);return r?Object.keys(r.data).map(function(e){return{name:e,count:r.data[e],isRefined:t._state.isFacetRefined(n,e),isExcluded:t._state.isExcludeRefined(n,e)}}):[]}if(t._state.isDisjunctiveFacet(n)){var i=v(t.disjunctiveFacets,e);return i?Object.keys(i.data).map(function(e){return{name:e,count:i.data[e],isRefined:t._state.isDisjunctiveFacetRefined(n,e)}}):[]}if(t._state.isHierarchicalFacet(n))return v(t.hierarchicalFacets,e)}(this,e);if(n){var r=m({},t,{sortBy:C.DEFAULT_SORT});if(Array.isArray(r.sortBy)){var i=P(r.sortBy,C.DEFAULT_SORT);return Array.isArray(n)?N(n,i[0],i[1]):T(function(e){return N(e,i[0],i[1])},n)}if("function"==typeof r.sortBy)return Array.isArray(n)?n.sort(r.sortBy):T(function(e){return function(e,t){return t.sort(e)}(r.sortBy,e)},n);throw new Error("options.sortBy is optional but if defined it must be either an array of string (predicates) or a sorting function")}},C.prototype.getFacetStats=function(e){return this._state.isConjunctiveFacet(e)?E(this.facets,e):this._state.isDisjunctiveFacet(e)?E(this.disjunctiveFacets,e):void 0},C.prototype.getRefinements=function(){var r=this._state,n=this,i=[];return Object.keys(r.facetsRefinements).forEach(function(t){r.facetsRefinements[t].forEach(function(e){i.push(q(r,"facet",t,e,n.facets))})}),Object.keys(r.facetsExcludes).forEach(function(t){r.facetsExcludes[t].forEach(function(e){i.push(q(r,"exclude",t,e,n.facets))})}),Object.keys(r.disjunctiveFacetsRefinements).forEach(function(t){r.disjunctiveFacetsRefinements[t].forEach(function(e){i.push(q(r,"disjunctive",t,e,n.disjunctiveFacets))})}),Object.keys(r.hierarchicalFacetsRefinements).forEach(function(t){r.hierarchicalFacetsRefinements[t].forEach(function(e){i.push(function(e,t,n,r){var i=e.getHierarchicalFacetByName(t),a=e._getHierarchicalFacetSeparator(i),s=n.split(a),o=v(r,function(e){return e.name===t}),c=s.reduce(function(e,t){var n=e&&v(e.data,function(e){return e.name===t});return void 0!==n?n:e},o),u=c&&c.count||0,l=c&&c.exhaustive||!1,h=c&&c.path||"";return{type:"hierarchical",attributeName:t,name:h,count:u,exhaustive:l}}(r,t,e,n.hierarchicalFacets))})}),Object.keys(r.numericRefinements).forEach(function(n){var e=r.numericRefinements[n];Object.keys(e).forEach(function(t){e[t].forEach(function(e){i.push({type:"numeric",attributeName:n,name:e,numericValue:e,operator:t})})})}),r.tagRefinements.forEach(function(e){i.push({type:"tag",attributeName:"_tags",name:e})}),i};var U=C;function V(){this._events=this._events||{},this._maxListeners=this._maxListeners||void 0}var e=V;function W(e){return"function"==typeof e}function $(e){return"object"==typeof e&&null!==e}function z(e){return void 0===e}(V.EventEmitter=V).prototype._events=void 0,V.prototype._maxListeners=void 0,V.defaultMaxListeners=10,V.prototype.setMaxListeners=function(e){if(!function(e){return"number"==typeof e}(e)||e<0||isNaN(e))throw TypeError("n must be a positive number");return this._maxListeners=e,this},V.prototype.emit=function(e){var t,n,r,i,a,s;if(this._events||(this._events={}),"error"===e&&(!this._events.error||$(this._events.error)&&!this._events.error.length)){if((t=arguments[1])instanceof Error)throw t;var o=new Error('Uncaught, unspecified "error" event. ('+t+")");throw o.context=t,o}if(z(n=this._events[e]))return!1;if(W(n))switch(arguments.length){case 1:n.call(this);break;case 2:n.call(this,arguments[1]);break;case 3:n.call(this,arguments[1],arguments[2]);break;default:i=Array.prototype.slice.call(arguments,1),n.apply(this,i)}else if($(n))for(i=Array.prototype.slice.call(arguments,1),r=(s=n.slice()).length,a=0;a<r;a++)s[a].apply(this,i);return!0},V.prototype.on=V.prototype.addListener=function(e,t){var n;if(!W(t))throw TypeError("listener must be a function");return this._events||(this._events={}),this._events.newListener&&this.emit("newListener",e,W(t.listener)?t.listener:t),this._events[e]?$(this._events[e])?this._events[e].push(t):this._events[e]=[this._events[e],t]:this._events[e]=t,$(this._events[e])&&!this._events[e].warned&&(n=z(this._maxListeners)?V.defaultMaxListeners:this._maxListeners)&&0<n&&this._events[e].length>n&&(this._events[e].warned=!0,console.error("(node) warning: possible EventEmitter memory leak detected. %d listeners added. Use emitter.setMaxListeners() to increase limit.",this._events[e].length),"function"==typeof console.trace&&console.trace()),this},V.prototype.once=function(e,t){if(!W(t))throw TypeError("listener must be a function");var n=!1;function r(){this.removeListener(e,r),n||(n=!0,t.apply(this,arguments))}return r.listener=t,this.on(e,r),this},V.prototype.removeListener=function(e,t){var n,r,i,a;if(!W(t))throw TypeError("listener must be a function");if(!this._events||!this._events[e])return this;if(i=(n=this._events[e]).length,r=-1,n===t||W(n.listener)&&n.listener===t)delete this._events[e],this._events.removeListener&&this.emit("removeListener",e,t);else if($(n)){for(a=i;0<a--;)if(n[a]===t||n[a].listener&&n[a].listener===t){r=a;break}if(r<0)return this;1===n.length?(n.length=0,delete this._events[e]):n.splice(r,1),this._events.removeListener&&this.emit("removeListener",e,t)}return this},V.prototype.removeAllListeners=function(e){var t,n;if(!this._events)return this;if(!this._events.removeListener)return 0===arguments.length?this._events={}:this._events[e]&&delete this._events[e],this;if(0===arguments.length){for(t in this._events)"removeListener"!==t&&this.removeAllListeners(t);return this.removeAllListeners("removeListener"),this._events={},this}if(W(n=this._events[e]))this.removeListener(e,n);else if(n)for(;n.length;)this.removeListener(e,n[n.length-1]);return delete this._events[e],this},V.prototype.listeners=function(e){return this._events&&this._events[e]?W(this._events[e])?[this._events[e]]:this._events[e].slice():[]},V.prototype.listenerCount=function(e){if(this._events){var t=this._events[e];if(W(t))return 1;if(t)return t.length}return 0},V.listenerCount=function(e,t){return e.listenerCount(t)};var K=function(e,t){e.prototype=Object.create(t.prototype,{constructor:{value:e,enumerable:!1,writable:!0,configurable:!0}})};function J(e,t){this.main=e,this.fn=t,this.lastResults=null}K(J,e.EventEmitter),J.prototype.detach=function(){this.removeAllListeners(),this.main.detachDerivedHelper(this)},J.prototype.getModifiedState=function(e){return this.fn(e)};var Y=J,G={_getQueries:function(i,a){var s=[];return s.push({indexName:i,params:G._getHitsSearchParams(a)}),a.getRefinedDisjunctiveFacets().forEach(function(e){s.push({indexName:i,params:G._getDisjunctiveFacetSearchParams(a,e)})}),a.getRefinedHierarchicalFacets().forEach(function(e){var t=a.getHierarchicalFacetByName(e),n=a.getHierarchicalRefinement(e),r=a._getHierarchicalFacetSeparator(t);0<n.length&&1<n[0].split(r).length&&s.push({indexName:i,params:G._getDisjunctiveFacetSearchParams(a,e,!0)})}),s},_getHitsSearchParams:function(e){var t=e.facets.concat(e.disjunctiveFacets).concat(G._getHitsHierarchicalFacetsAttributes(e)),n=G._getFacetFilters(e),r=G._getNumericFilters(e),i={facets:t,tagFilters:G._getTagFilters(e)};return 0<n.length&&(i.facetFilters=n),0<r.length&&(i.numericFilters=r),p({},e.getQueryParams(),i)},_getDisjunctiveFacetSearchParams:function(e,t,n){var r=G._getFacetFilters(e,t,n),i=G._getNumericFilters(e,t),a={hitsPerPage:1,page:0,attributesToRetrieve:[],attributesToHighlight:[],attributesToSnippet:[],tagFilters:G._getTagFilters(e),analytics:!1,clickAnalytics:!1},s=e.getHierarchicalFacetByName(t);return a.facets=s?G._getDisjunctiveHierarchicalFacetAttribute(e,s,n):t,0<i.length&&(a.numericFilters=i),0<r.length&&(a.facetFilters=r),p({},e.getQueryParams(),a)},_getNumericFilters:function(e,i){if(e.numericFilters)return e.numericFilters;var a=[];return Object.keys(e.numericRefinements).forEach(function(r){var t=e.numericRefinements[r]||{};Object.keys(t).forEach(function(n){var e=t[n]||[];i!==r&&e.forEach(function(e){if(Array.isArray(e)){var t=e.map(function(e){return r+n+e});a.push(t)}else a.push(r+n+e)})})}),a},_getTagFilters:function(e){return e.tagFilters?e.tagFilters:e.tagRefinements.join(",")},_getFacetFilters:function(o,c,u){var l=[],e=o.facetsRefinements||{};Object.keys(e).forEach(function(t){(e[t]||[]).forEach(function(e){l.push(t+":"+e)})});var n=o.facetsExcludes||{};Object.keys(n).forEach(function(t){(n[t]||[]).forEach(function(e){l.push(t+":-"+e)})});var r=o.disjunctiveFacetsRefinements||{};Object.keys(r).forEach(function(t){var e=r[t]||[];if(t!==c&&e&&0!==e.length){var n=[];e.forEach(function(e){n.push(t+":"+e)}),l.push(n)}});var h=o.hierarchicalFacetsRefinements||{};return Object.keys(h).forEach(function(e){var t=(h[e]||[])[0];if(void 0!==t){var n,r,i=o.getHierarchicalFacetByName(e),a=o._getHierarchicalFacetSeparator(i),s=o._getHierarchicalRootPath(i);if(c===e){if(-1===t.indexOf(a)||!s&&!0===u||s&&s.split(a).length===t.split(a).length)return;t=s?(r=s.split(a).length-1,s):(r=t.split(a).length-2,t.slice(0,t.lastIndexOf(a))),n=i.attributes[r]}else r=t.split(a).length-1,n=i.attributes[r];n&&l.push([n+":"+t])}}),l},_getHitsHierarchicalFacetsAttributes:function(s){return s.hierarchicalFacets.reduce(function(e,t){var n=s.getHierarchicalRefinement(t.name)[0];if(!n)return e.push(t.attributes[0]),e;var r=s._getHierarchicalFacetSeparator(t),i=n.split(r).length,a=t.attributes.slice(0,i+1);return e.concat(a)},[])},_getDisjunctiveHierarchicalFacetAttribute:function(e,t,n){var r=e._getHierarchicalFacetSeparator(t);if(!0===n){var i=e._getHierarchicalRootPath(t),a=0;return i&&(a=i.split(r).length),[t.attributes[a]]}var s=(e.getHierarchicalRefinement(t.name)[0]||"").split(r).length-1;return t.attributes.slice(0,1+s)},getSearchForFacetQuery:function(e,t,n,r){var i=r.isDisjunctiveFacet(e)?r.clearRefinements(e):r,a={facetQuery:t,facetName:e};return"number"==typeof n&&(a.maxFacetHits=n),p({},G._getHitsSearchParams(i),a)}},X=G,Z="3.2.2";function ee(e,t,n){"function"==typeof e.addAlgoliaAgent&&e.addAlgoliaAgent("JS Helper (3.2.2)"),this.setClient(e);var r=n||{};r.index=t,this.state=R.make(r),this.lastResults=null,this._queryId=0,this._lastQueryIdReceived=-1,this.derivedHelpers=[],this._currentNbQueries=0}function te(e){if(e<0)throw new Error("Page requested below 0.");return this._change({state:this.state.setPage(e),isPageReset:!1}),this}function ne(){return this.state.page}K(ee,e.EventEmitter),ee.prototype.search=function(){return this._search({onlyWithDerivedHelpers:!1}),this},ee.prototype.searchOnlyWithDerivedHelpers=function(){return this._search({onlyWithDerivedHelpers:!0}),this},ee.prototype.getQuery=function(){var e=this.state;return X._getHitsSearchParams(e)},ee.prototype.searchOnce=function(e,t){var n=e?this.state.setQueryParameters(e):this.state,r=X._getQueries(n.index,n),i=this;if(this._currentNbQueries++,this.emit("searchOnce",{state:n}),!t)return this.client.search(r).then(function(e){return i._currentNbQueries--,0===i._currentNbQueries&&i.emit("searchQueueEmpty"),{content:new U(n,e.results),state:n,_originalResponse:e}},function(e){throw i._currentNbQueries--,0===i._currentNbQueries&&i.emit("searchQueueEmpty"),e});this.client.search(r).then(function(e){i._currentNbQueries--,0===i._currentNbQueries&&i.emit("searchQueueEmpty"),t(null,new U(n,e.results),n)}).catch(function(e){i._currentNbQueries--,0===i._currentNbQueries&&i.emit("searchQueueEmpty"),t(e,null,n)})},ee.prototype.searchForFacetValues=function(t,e,n,r){var i="function"==typeof this.client.searchForFacetValues;if(!i&&"function"!=typeof this.client.initIndex)throw new Error("search for facet values (searchable) was called, but this client does not have a function client.searchForFacetValues or client.initIndex(index).searchForFacetValues");var a=this.state.setQueryParameters(r||{}),s=a.isDisjunctiveFacet(t),o=X.getSearchForFacetQuery(t,e,n,a);this._currentNbQueries++;var c=this;return this.emit("searchForFacetValues",{state:a,facet:t,query:e}),(i?this.client.searchForFacetValues([{indexName:a.index,params:o}]):this.client.initIndex(a.index).searchForFacetValues(o)).then(function(e){return c._currentNbQueries--,0===c._currentNbQueries&&c.emit("searchQueueEmpty"),(e=Array.isArray(e)?e[0]:e).facetHits.forEach(function(e){e.isRefined=s?a.isDisjunctiveFacetRefined(t,e.value):a.isFacetRefined(t,e.value)}),e},function(e){throw c._currentNbQueries--,0===c._currentNbQueries&&c.emit("searchQueueEmpty"),e})},ee.prototype.setQuery=function(e){return this._change({state:this.state.resetPage().setQuery(e),isPageReset:!0}),this},ee.prototype.clearRefinements=function(e){return this._change({state:this.state.resetPage().clearRefinements(e),isPageReset:!0}),this},ee.prototype.clearTags=function(){return this._change({state:this.state.resetPage().clearTags(),isPageReset:!0}),this},ee.prototype.addDisjunctiveFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().addDisjunctiveFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.addDisjunctiveRefine=function(){return this.addDisjunctiveFacetRefinement.apply(this,arguments)},ee.prototype.addHierarchicalFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().addHierarchicalFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.addNumericRefinement=function(e,t,n){return this._change({state:this.state.resetPage().addNumericRefinement(e,t,n),isPageReset:!0}),this},ee.prototype.addFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().addFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.addRefine=function(){return this.addFacetRefinement.apply(this,arguments)},ee.prototype.addFacetExclusion=function(e,t){return this._change({state:this.state.resetPage().addExcludeRefinement(e,t),isPageReset:!0}),this},ee.prototype.addExclude=function(){return this.addFacetExclusion.apply(this,arguments)},ee.prototype.addTag=function(e){return this._change({state:this.state.resetPage().addTagRefinement(e),isPageReset:!0}),this},ee.prototype.removeNumericRefinement=function(e,t,n){return this._change({state:this.state.resetPage().removeNumericRefinement(e,t,n),isPageReset:!0}),this},ee.prototype.removeDisjunctiveFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().removeDisjunctiveFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.removeDisjunctiveRefine=function(){return this.removeDisjunctiveFacetRefinement.apply(this,arguments)},ee.prototype.removeHierarchicalFacetRefinement=function(e){return this._change({state:this.state.resetPage().removeHierarchicalFacetRefinement(e),isPageReset:!0}),this},ee.prototype.removeFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().removeFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.removeRefine=function(){return this.removeFacetRefinement.apply(this,arguments)},ee.prototype.removeFacetExclusion=function(e,t){return this._change({state:this.state.resetPage().removeExcludeRefinement(e,t),isPageReset:!0}),this},ee.prototype.removeExclude=function(){return this.removeFacetExclusion.apply(this,arguments)},ee.prototype.removeTag=function(e){return this._change({state:this.state.resetPage().removeTagRefinement(e),isPageReset:!0}),this},ee.prototype.toggleFacetExclusion=function(e,t){return this._change({state:this.state.resetPage().toggleExcludeFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.toggleExclude=function(){return this.toggleFacetExclusion.apply(this,arguments)},ee.prototype.toggleRefinement=function(e,t){return this.toggleFacetRefinement(e,t)},ee.prototype.toggleFacetRefinement=function(e,t){return this._change({state:this.state.resetPage().toggleFacetRefinement(e,t),isPageReset:!0}),this},ee.prototype.toggleRefine=function(){return this.toggleFacetRefinement.apply(this,arguments)},ee.prototype.toggleTag=function(e){return this._change({state:this.state.resetPage().toggleTagRefinement(e),isPageReset:!0}),this},ee.prototype.nextPage=function(){var e=this.state.page||0;return this.setPage(e+1)},ee.prototype.previousPage=function(){var e=this.state.page||0;return this.setPage(e-1)},ee.prototype.setCurrentPage=te,ee.prototype.setPage=te,ee.prototype.setIndex=function(e){return this._change({state:this.state.resetPage().setIndex(e),isPageReset:!0}),this},ee.prototype.setQueryParameter=function(e,t){return this._change({state:this.state.resetPage().setQueryParameter(e,t),isPageReset:!0}),this},ee.prototype.setState=function(e){return this._change({state:R.make(e),isPageReset:!1}),this},ee.prototype.overrideStateWithoutTriggeringChangeEvent=function(e){return this.state=new R(e),this},ee.prototype.hasRefinements=function(e){return!!l(this.state.getNumericRefinements(e))||(this.state.isConjunctiveFacet(e)?this.state.isFacetRefined(e):this.state.isDisjunctiveFacet(e)?this.state.isDisjunctiveFacetRefined(e):!!this.state.isHierarchicalFacet(e)&&this.state.isHierarchicalFacetRefined(e))},ee.prototype.isExcluded=function(e,t){return this.state.isExcludeRefined(e,t)},ee.prototype.isDisjunctiveRefined=function(e,t){return this.state.isDisjunctiveFacetRefined(e,t)},ee.prototype.hasTag=function(e){return this.state.isTagRefined(e)},ee.prototype.isTagRefined=function(){return this.hasTagRefinements.apply(this,arguments)},ee.prototype.getIndex=function(){return this.state.index},ee.prototype.getCurrentPage=ne,ee.prototype.getPage=ne,ee.prototype.getTags=function(){return this.state.tagRefinements},ee.prototype.getRefinements=function(e){var n=[];if(this.state.isConjunctiveFacet(e))this.state.getConjunctiveRefinements(e).forEach(function(e){n.push({value:e,type:"conjunctive"})}),this.state.getExcludeRefinements(e).forEach(function(e){n.push({value:e,type:"exclude"})});else if(this.state.isDisjunctiveFacet(e)){this.state.getDisjunctiveRefinements(e).forEach(function(e){n.push({value:e,type:"disjunctive"})})}var r=this.state.getNumericRefinements(e);return Object.keys(r).forEach(function(e){var t=r[e];n.push({value:t,operator:e,type:"numeric"})}),n},ee.prototype.getNumericRefinement=function(e,t){return this.state.getNumericRefinement(e,t)},ee.prototype.getHierarchicalFacetBreadcrumb=function(e){return this.state.getHierarchicalFacetBreadcrumb(e)},ee.prototype._search=function(e){var r=this.state,i=[],t=[];e.onlyWithDerivedHelpers||(t=X._getQueries(r.index,r),i.push({state:r,queriesCount:t.length,helper:this}),this.emit("search",{state:r,results:this.lastResults}));var n=this.derivedHelpers.map(function(e){var t=e.getModifiedState(r),n=X._getQueries(t.index,t);return i.push({state:t,queriesCount:n.length,helper:e}),e.emit("search",{state:t,results:e.lastResults}),n}),a=Array.prototype.concat.apply(t,n),s=this._queryId++;this._currentNbQueries++;try{this.client.search(a).then(this._dispatchAlgoliaResponse.bind(this,i,s)).catch(this._dispatchAlgoliaError.bind(this,s))}catch(e){this.emit("error",{error:e})}},ee.prototype._dispatchAlgoliaResponse=function(e,t,n){if(!(t<this._lastQueryIdReceived)){this._currentNbQueries-=t-this._lastQueryIdReceived,this._lastQueryIdReceived=t,0===this._currentNbQueries&&this.emit("searchQueueEmpty");var s=n.results.slice();e.forEach(function(e){var t=e.state,n=e.queriesCount,r=e.helper,i=s.splice(0,n),a=r.lastResults=new U(t,i);r.emit("result",{results:a,state:t})})}},ee.prototype._dispatchAlgoliaError=function(e,t){e<this._lastQueryIdReceived||(this._currentNbQueries-=e-this._lastQueryIdReceived,this._lastQueryIdReceived=e,this.emit("error",{error:t}),0===this._currentNbQueries&&this.emit("searchQueueEmpty"))},ee.prototype.containsRefinement=function(e,t,n,r){return e||0!==t.length||0!==n.length||0!==r.length},ee.prototype._hasDisjunctiveRefinements=function(e){return this.state.disjunctiveRefinements[e]&&0<this.state.disjunctiveRefinements[e].length},ee.prototype._change=function(e){var t=e.state,n=e.isPageReset;t!==this.state&&(this.state=t,this.emit("change",{state:this.state,results:this.lastResults,isPageReset:n}))},ee.prototype.clearCache=function(){return this.client.clearCache&&this.client.clearCache(),this},ee.prototype.setClient=function(e){return this.client===e||("function"==typeof e.addAlgoliaAgent&&e.addAlgoliaAgent("JS Helper (3.2.2)"),this.client=e),this},ee.prototype.getClient=function(){return this.client},ee.prototype.derive=function(e){var t=new Y(this,e);return this.derivedHelpers.push(t),t},ee.prototype.detachDerivedHelper=function(e){var t=this.derivedHelpers.indexOf(e);if(-1===t)throw new Error("Derived helper already detached");this.derivedHelpers.splice(t,1)},ee.prototype.hasPendingRequests=function(){return 0<this._currentNbQueries};var re=ee;function ie(e,t,n){return new re(e,t,n)}ie.version=Z,ie.AlgoliaSearchHelper=re,ie.SearchParameters=R,ie.SearchResults=U;var ae=ie;function se(r){function e(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];null===i&&(i=oe.then(function(){i=null,a?a=!1:r.apply(void 0,t)}))}var i=null,a=!1;return e.wait=function(){if(null===i)throw new Error("The deferred function should be called before calling `wait()`");return i},e.cancel=function(){null!==i&&(a=!0)},e}var oe=Promise.resolve();function ce(e){var t="string"==typeof e,n=t?document.querySelector(e):e;if(function(e){return e instanceof HTMLElement||Boolean(e)&&0<e.nodeType}(n))return n;var r="Container must be `string` or `HTMLElement`.";throw t&&(r+=" Unable to find ".concat(e)),new Error(r)}function ue(e){return 1===e.button||e.altKey||e.ctrlKey||e.metaKey||e.shiftKey}function le(e){return e.filter(function(e,t,n){return n.indexOf(e)===t})}function he(e){var t=e.defaultTemplates,n=e.templates;return D({templatesConfig:e.templatesConfig},function(e,t){var a=0<arguments.length&&void 0!==e?e:{},s=1<arguments.length&&void 0!==t?t:{};return le([].concat(_(Object.keys(a)),_(Object.keys(s)))).reduce(function(e,t){var n=a[t],r=s[t],i=void 0!==r&&r!==n;return e.templates[t]=i?r:n,e.useCustomCompileOptions[t]=i,e},{templates:{},useCustomCompileOptions:{}})}(t,n))}function fe(e,t){return e(t={exports:{}},t.exports),t.exports}var de=fe(function(e,t){!function(R){var w=/\S/,t=/\"/g,n=/\n/g,r=/\r/g,i=/\\/g,a=/\u2028/,s=/\u2029/;function S(e){"}"===e.n.substr(e.n.length-1)&&(e.n=e.n.substring(0,e.n.length-1))}function P(e){return e.trim?e.trim():e.replace(/^\s*|\s*$/g,"")}function _(e,t,n){if(t.charAt(n)!=e.charAt(0))return!1;for(var r=1,i=e.length;r<i;r++)if(t.charAt(n+r)!=e.charAt(r))return!1;return!0}R.tags={"#":1,"^":2,"<":3,$:4,"/":5,"!":6,">":7,"=":8,_v:9,"{":10,"&":11,_t:12},R.scan=function(e,t){var n,r,i,a,s,o=e.length,c=0,u=null,l=null,h="",f=[],d=!1,m=0,p=0,v="{{",g="}}";function y(){0<h.length&&(f.push({tag:"_t",text:new String(h)}),h="")}function b(e,t){if(y(),e&&function(){for(var e=!0,t=p;t<f.length;t++)if(!(e=R.tags[f[t].tag]<R.tags._v||"_t"==f[t].tag&&null===f[t].text.match(w)))return!1;return e}())for(var n,r=p;r<f.length;r++)f[r].text&&((n=f[r+1])&&">"==n.tag&&(n.indent=f[r].text.toString()),f.splice(r,1));else t||f.push({tag:"\n"});d=!1,p=f.length}for(t&&(t=t.split(" "),v=t[0],g=t[1]),m=0;m<o;m++)0==c?_(v,e,m)?(--m,y(),c=1):"\n"==e.charAt(m)?b(d):h+=e.charAt(m):1==c?(m+=v.length-1,c="="==(u=(l=R.tags[e.charAt(m+1)])?e.charAt(m+1):"_v")?(r=m,void 0,i="="+g,a=(n=e).indexOf(i,r),s=P(n.substring(n.indexOf("=",r)+1,a)).split(" "),v=s[0],g=s[s.length-1],m=a+i.length-1,0):(l&&m++,2),d=m):_(g,e,m)?(f.push({tag:u,n:P(h),otag:v,ctag:g,i:"/"==u?d-v.length:m+g.length}),h="",m+=g.length-1,c=0,"{"==u&&("}}"==g?m++:S(f[f.length-1]))):h+=e.charAt(m);return b(d,!0),f};var u={_t:!0,"\n":!0,$:!0,"/":!0};function l(e,t){for(var n=0,r=t.length;n<r;n++)if(t[n].o==e.n)return e.tag="#",!0}function h(e,t,n){for(var r=0,i=n.length;r<i;r++)if(n[r].c==e&&n[r].o==t)return!0}function o(e){var t=[];for(var n in e.partials)t.push('"'+f(n)+'":{name:"'+f(e.partials[n].name)+'", '+o(e.partials[n])+"}");return"partials: {"+t.join(",")+"}, subs: "+function(e){var t=[];for(var n in e)t.push('"'+f(n)+'": function(c,p,t,i) {'+e[n]+"}");return"{ "+t.join(",")+" }"}(e.subs)}R.stringify=function(e,t,n){return"{code: function (c,p,i) { "+R.wrapMain(e.code)+" },"+o(e)+"}"};var c=0;function f(e){return e.replace(i,"\\\\").replace(t,'\\"').replace(n,"\\n").replace(r,"\\r").replace(a,"\\u2028").replace(s,"\\u2029")}function d(e){return~e.indexOf(".")?"d":"f"}function m(e,t){var n="<"+(t.prefix||"")+e.n+c++;return t.partials[n]={name:e.n,partials:{}},t.code+='t.b(t.rp("'+f(n)+'",c,p,"'+(e.indent||"")+'"));',n}function e(e,t){t.code+="t.b(t.t(t."+d(e.n)+'("'+f(e.n)+'",c,p,0)));'}function p(e){return"t.b("+e+");"}R.generate=function(e,t,n){c=0;var r={code:"",subs:{},partials:{}};return R.walk(e,r),n.asString?this.stringify(r,t,n):this.makeTemplate(r,t,n)},R.wrapMain=function(e){return'var t=this;t.b(i=i||"");'+e+"return t.fl();"},R.template=R.Template,R.makeTemplate=function(e,t,n){var r=this.makePartials(e);return r.code=new Function("c","p","i",this.wrapMain(e.code)),new this.template(r,t,this,n)},R.makePartials=function(e){var t,n={subs:{},partials:e.partials,name:e.name};for(t in n.partials)n.partials[t]=this.makePartials(n.partials[t]);for(t in e.subs)n.subs[t]=new Function("c","p","t","i",e.subs[t]);return n},R.codegen={"#":function(e,t){t.code+="if(t.s(t."+d(e.n)+'("'+f(e.n)+'",c,p,1),c,p,0,'+e.i+","+e.end+',"'+e.otag+" "+e.ctag+'")){t.rs(c,p,function(c,p,t){',R.walk(e.nodes,t),t.code+="});c.pop();}"},"^":function(e,t){t.code+="if(!t.s(t."+d(e.n)+'("'+f(e.n)+'",c,p,1),c,p,1,0,0,"")){',R.walk(e.nodes,t),t.code+="};"},">":m,"<":function(e,t){var n={partials:{},code:"",subs:{},inPartial:!0};R.walk(e.nodes,n);var r=t.partials[m(e,t)];r.subs=n.subs,r.partials=n.partials},$:function(e,t){var n={subs:{},code:"",partials:t.partials,prefix:e.n};R.walk(e.nodes,n),t.subs[e.n]=n.code,t.inPartial||(t.code+='t.sub("'+f(e.n)+'",c,p,i);')},"\n":function(e,t){t.code+=p('"\\n"'+(e.last?"":" + i"))},_v:function(e,t){t.code+="t.b(t.v(t."+d(e.n)+'("'+f(e.n)+'",c,p,0)));'},_t:function(e,t){t.code+=p('"'+f(e.text)+'"')},"{":e,"&":e},R.walk=function(e,t){for(var n,r=0,i=e.length;r<i;r++)(n=R.codegen[e[r].tag])&&n(e[r],t);return t},R.parse=function(e,t,n){return function e(t,n,r,i){var a,s=[],o=null,c=null;for(a=r[r.length-1];0<t.length;){if(c=t.shift(),a&&"<"==a.tag&&!(c.tag in u))throw new Error("Illegal content in < super tag.");if(R.tags[c.tag]<=R.tags.$||l(c,i))r.push(c),c.nodes=e(t,c.tag,r,i);else{if("/"==c.tag){if(0===r.length)throw new Error("Closing tag without opener: /"+c.n);if(o=r.pop(),c.n!=o.n&&!h(c.n,o.n,i))throw new Error("Nesting error: "+o.n+" vs. "+c.n);return o.end=c.i,s}"\n"==c.tag&&(c.last=0==t.length||"\n"==t[0].tag)}s.push(c)}if(0<r.length)throw new Error("missing closing tag: "+r.pop().n);return s}(e,0,[],(n=n||{}).sectionTags||[])},R.cache={},R.cacheKey=function(e,t){return[e,!!t.asString,!!t.disableLambda,t.delimiters,!!t.modelGet].join("||")},R.compile=function(e,t){t=t||{};var n=R.cacheKey(e,t),r=this.cache[n];if(r){var i=r.partials;for(var a in i)delete i[a].instance;return r}return r=this.generate(this.parse(this.scan(e,t.delimiters),e,t),e,t),this.cache[n]=r}}(t)}),me=fe(function(e,t){!function(e){function l(e,t,n){var r;return t&&"object"==typeof t&&(void 0!==t[e]?r=t[e]:n&&t.get&&"function"==typeof t.get&&(r=t.get(e))),r}e.Template=function(e,t,n,r){e=e||{},this.r=e.code||this.r,this.c=n,this.options=r||{},this.text=t||"",this.partials=e.partials||{},this.subs=e.subs||{},this.buf=""},e.Template.prototype={r:function(e,t,n){return""},v:function(e){return e=o(e),s.test(e)?e.replace(t,"&amp;").replace(n,"&lt;").replace(r,"&gt;").replace(i,"&#39;").replace(a,"&quot;"):e},t:o,render:function(e,t,n){return this.ri([e],t||{},n)},ri:function(e,t,n){return this.r(e,t,n)},ep:function(e,t){var n=this.partials[e],r=t[n.name];if(n.instance&&n.base==r)return n.instance;if("string"==typeof r){if(!this.c)throw new Error("No compiler available.");r=this.c.compile(r,this.options)}if(!r)return null;if(this.partials[e].base=r,n.subs){for(key in t.stackText||(t.stackText={}),n.subs)t.stackText[key]||(t.stackText[key]=void 0!==this.activeSub&&t.stackText[this.activeSub]?t.stackText[this.activeSub]:this.text);r=function(e,t,n,r,i,a){function s(){}function o(){}var c;o.prototype=(s.prototype=e).subs;var u=new s;for(c in u.subs=new o,u.subsText={},u.buf="",r=r||{},u.stackSubs=r,u.subsText=a,t)r[c]||(r[c]=t[c]);for(c in r)u.subs[c]=r[c];for(c in i=i||{},u.stackPartials=i,n)i[c]||(i[c]=n[c]);for(c in i)u.partials[c]=i[c];return u}(r,n.subs,n.partials,this.stackSubs,this.stackPartials,t.stackText)}return this.partials[e].instance=r},rp:function(e,t,n,r){var i=this.ep(e,n);return i?i.ri(t,n,r):""},rs:function(e,t,n){var r=e[e.length-1];if(h(r))for(var i=0;i<r.length;i++)e.push(r[i]),n(e,t,this),e.pop();else n(e,t,this)},s:function(e,t,n,r,i,a,s){var o;return(!h(e)||0!==e.length)&&("function"==typeof e&&(e=this.ms(e,t,n,r,i,a,s)),o=!!e,!r&&o&&t&&t.push("object"==typeof e?e:t[t.length-1]),o)},d:function(e,t,n,r){var i,a=e.split("."),s=this.f(a[0],t,n,r),o=this.options.modelGet,c=null;if("."===e&&h(t[t.length-2]))s=t[t.length-1];else for(var u=1;u<a.length;u++)s=void 0!==(i=l(a[u],s,o))?(c=s,i):"";return!(r&&!s)&&(r||"function"!=typeof s||(t.push(c),s=this.mv(s,t,n),t.pop()),s)},f:function(e,t,n,r){for(var i=!1,a=!1,s=this.options.modelGet,o=t.length-1;0<=o;o--)if(void 0!==(i=l(e,t[o],s))){a=!0;break}return a?(r||"function"!=typeof i||(i=this.mv(i,t,n)),i):!r&&""},ls:function(e,t,n,r,i){var a=this.options.delimiters;return this.options.delimiters=i,this.b(this.ct(o(e.call(t,r)),t,n)),this.options.delimiters=a,!1},ct:function(e,t,n){if(this.options.disableLambda)throw new Error("Lambda features disabled.");return this.c.compile(e,this.options).render(t,n)},b:function(e){this.buf+=e},fl:function(){var e=this.buf;return this.buf="",e},ms:function(e,t,n,r,i,a,s){var o,c=t[t.length-1],u=e.call(c);return"function"==typeof u?!!r||(o=this.activeSub&&this.subsText&&this.subsText[this.activeSub]?this.subsText[this.activeSub]:this.text,this.ls(u,c,n,o.substring(i,a),s)):u},mv:function(e,t,n){var r=t[t.length-1],i=e.call(r);return"function"==typeof i?this.ct(o(i.call(r)),r,n):i},sub:function(e,t,n,r){var i=this.subs[e];i&&(this.activeSub=e,i(t,n,this,r),this.activeSub=!1)}};var t=/&/g,n=/</g,r=/>/g,i=/\'/g,a=/\"/g,s=/[&<>\"\']/;function o(e){return String(null==e?"":e)}var h=Array.isArray||function(e){return"[object Array]"===Object.prototype.toString.call(e)}}(t)});de.Template=me.Template,de.template=de.Template;var pe=de;function ve(e){var t=e.templates,n=e.templateKey,r=e.compileOptions,i=e.helpers,a=e.data,s=e.bindEvent,o=t[n],c=h(o),u="function"===c;if(!("string"===c)&&!u)throw new Error("Template must be 'string' or 'function', was '".concat(c,"' (key: ").concat(n,")"));if(u)return o(a,s);var l=function(e,t,n){var r=0<arguments.length&&void 0!==e?e:{},i=1<arguments.length?t:void 0,a=2<arguments.length?n:void 0;return Object.keys(r).reduce(function(e,n){return D({},e,L({},n,function(){var t=this;return function(e){return r[n].call(a,e,function(e){return pe.compile(e,i).render(t)})}}))},{})}(i,r,a);return pe.compile(o,r).render(D({},a,{helpers:l})).replace(/[ \n\r\t\f\xA0]+/g,function(e){return e.replace(/(^|\xA0+)[^\xA0]+/g,"$1 ")}).trim()}function ge(e,t,n){return Array.prototype.find?e.find(t,n):e.filter(t,n)[0]}function ye(e){return String(e).replace(/^\\-/,"-")}function be(i,e,a,s,t){var o,n={type:e,attribute:a,name:s},c=ge(4<arguments.length&&void 0!==t?t:[],function(e){return e.name===a});"hierarchical"===e?function(){for(var e=i.getHierarchicalFacetByName(a),n=s.split(e.separator),t=function(t){c=c&&c.data&&ge(Object.keys(c.data).map(function(t){return function(e){return t[e]}}(c.data)),function(e){return e.name===n[t]})},r=0;void 0!==c&&r<n.length;++r)t(r);o=c&&c.count}():o=c&&c.data&&c.data[n.name];var r=c&&c.exhaustive;return void 0!==o&&(n.count=o),void 0!==r&&(n.exhaustive=r),n}function Re(n,r,e){var t=2<arguments.length&&void 0!==e&&e,a=[],i=r.facetsRefinements,s=void 0===i?{}:i,o=r.facetsExcludes,c=void 0===o?{}:o,u=r.disjunctiveFacetsRefinements,l=void 0===u?{}:u,h=r.hierarchicalFacetsRefinements,f=void 0===h?{}:h,d=r.numericRefinements,m=void 0===d?{}:d,p=r.tagRefinements,v=void 0===p?[]:p;return Object.keys(s).forEach(function(t){s[t].forEach(function(e){a.push(be(r,"facet",t,e,n.facets))})}),Object.keys(c).forEach(function(t){c[t].forEach(function(e){a.push({type:"exclude",attribute:t,name:e,exclude:!0})})}),Object.keys(l).forEach(function(t){l[t].forEach(function(e){a.push(be(r,"disjunctive",t,ye(e),n.disjunctiveFacets))})}),Object.keys(f).forEach(function(t){f[t].forEach(function(e){a.push(be(r,"hierarchical",t,e,n.hierarchicalFacets))})}),Object.keys(m).forEach(function(r){var i=m[r];Object.keys(i).forEach(function(e){var t=e,n=i[t];(Array.isArray(n)?n:[n]).forEach(function(e){a.push({type:"numeric",attribute:r,name:"".concat(e),numericValue:e,operator:t})})})}),v.forEach(function(e){a.push({type:"tag",attribute:"_tags",name:e})}),t&&r.query&&r.query.trim()&&a.push({attribute:"query",type:"query",name:r.query,query:r.query}),a}function we(e){var t=e.helper,n=e.attributesToClear,r=void 0===n?[]:n,i=t.state.setPage(0);return i=r.reduce(function(e,t){return i.isNumericRefined(t)?e.removeNumericRefinement(t):i.isHierarchicalFacet(t)?e.removeHierarchicalFacetRefinement(t):i.isDisjunctiveFacet(t)?e.removeDisjunctiveFacetRefinement(t):i.isConjunctiveFacet(t)?e.removeFacetRefinement(t):e},i),-1!==r.indexOf("query")&&(i=i.setQuery("")),i}function Se(e){return"number"==typeof e&&e<0&&(e=String(e).replace(/^-/,"\\-")),e}function Pe(e,t){if(void 0===e||"function"!=typeof e)throw new Error("The render function is not valid (received type ".concat(function(e){return Object.prototype.toString.call(e).slice(8,-1)}(e),").\n\n").concat(t))}function _e(){}function Ne(e,t){return t.split(".").reduce(function(e,t){return e&&e[t]},e)}function xe(e){return"number"==typeof e&&isFinite(e)}function Fe(e){if(!function(e){return"object"===h(e)&&null!==e}(e)||"[object Object]"!==function(e){return null===e?void 0===e?"[object Undefined]":"[object Null]":Object.prototype.toString.call(e)}(e))return!1;if(null===Object.getPrototypeOf(e))return!0;for(var t=e;null!==Object.getPrototypeOf(t);)t=Object.getPrototypeOf(t);return Object.getPrototypeOf(e)===t}function Ie(e){var t=e.start,n=void 0===t?0:t,r=e.end,i=e.step,a=void 0===i?1:i,s=0===a?1:a,o=Math.round((r-n)/s);return _(Array(o)).map(function(e,t){return n+t*s})}function Ce(e){return e!==Object(e)}function Te(e,t){if(e===t)return!0;if(Ce(e)||Ce(t)||"function"==typeof e||"function"==typeof t)return e===t;if(Object.keys(e).length!==Object.keys(t).length)return!1;for(var n=0,r=Object.keys(e);n<r.length;n++){var i=r[n];if(!(i in t))return!1;if(!Te(e[i],t[i]))return!1}return!0}var Ee={"&":"&amp;","<":"&lt;",">":"&gt;",'"':"&quot;","'":"&#39;"},ke=/[&<>"']/g,Me=RegExp(ke.source);function Le(e,t){return e.setQueryParameters({hierarchicalFacets:t.hierarchicalFacets.reduce(function(e,t){var n=function(e,t){if(!Array.isArray(e))return-1;for(var n=0;n<e.length;n++)if(t(e[n]))return n;return-1}(e,function(e){return e.name===t.name});if(-1===n)return e.concat(t);var r=e.slice();return r.splice(n,1,t),r},e.hierarchicalFacets)})}function je(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];return t.reduce(function(e,t){var n=function(e,t){return e.setQueryParameters({hierarchicalFacetsRefinements:D({},e.hierarchicalFacetsRefinements,{},t.hierarchicalFacetsRefinements)})}(e,t);return function(e,t){t.facets,t.disjunctiveFacets,t.facetsRefinements,t.facetsExcludes,t.disjunctiveFacetsRefinements,t.numericRefinements,t.tagRefinements,t.hierarchicalFacets,t.hierarchicalFacetsRefinements,t.ruleContexts;var n=A(t,["facets","disjunctiveFacets","facetsRefinements","facetsExcludes","disjunctiveFacetsRefinements","numericRefinements","tagRefinements","hierarchicalFacets","hierarchicalFacetsRefinements","ruleContexts"]);return e.setQueryParameters(n)}(function(e,t){return t.facets.reduce(function(e,t){return e.addFacet(t)},e)}(function(e,t){var n=le([].concat(e.ruleContexts).concat(t.ruleContexts).filter(Boolean));return 0<n.length?e.setQueryParameters({ruleContexts:n}):e}(function(e,t){return t.disjunctiveFacets.reduce(function(e,t){return e.addDisjunctiveFacet(t)},e)}(function(e,t){return e.setQueryParameters({facetsRefinements:D({},e.facetsRefinements,{},t.facetsRefinements)})}(function(e,t){return e.setQueryParameters({facetsExcludes:D({},e.facetsExcludes,{},t.facetsExcludes)})}(function(e,t){return e.setQueryParameters({disjunctiveFacetsRefinements:D({},e.disjunctiveFacetsRefinements,{},t.disjunctiveFacetsRefinements)})}(function(e,t){return e.setQueryParameters({numericRefinements:D({},e.numericRefinements,{},t.numericRefinements)})}(function(e,t){return t.tagRefinements.reduce(function(e,t){return e.addTagRefinement(t)},e)}(Le(n,t),t),t),t),t),t),t),t),t),t)})}function Oe(e){return Array.isArray(e)?e:[e]}function Ae(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r=t.map(function(e){return function(e){var t=e.name,n=e.connector;return["https://www.algolia.com/doc/api-reference/widgets/",t,"/js/",void 0!==n&&n?"#connector":""].join("")}(e)}).join(", ");return function(e){return[e,"See documentation: ".concat(r)].filter(Boolean).join("\n\n")}}var He=/^(-?\d+(?:\.\d+)?),\s*(-?\d+(?:\.\d+)?)$/;function De(e){return Array.isArray(e)?function(e){var t=Q(e,1)[0],n=Q(t=void 0===t?[void 0,void 0,void 0,void 0]:t,4),r=n[0],i=n[1],a=n[2],s=n[3];if(!(r&&i&&a&&s))throw new Error('Invalid value for "insideBoundingBox" parameter: ['.concat(e,"]"));return{northEast:{lat:r,lng:i},southWest:{lat:a,lng:s}}}(e):function(e){var t=Q(e.split(",").map(parseFloat),4),n=t[0],r=t[1],i=t[2],a=t[3];if(!(n&&r&&i&&a))throw new Error('Invalid value for "insideBoundingBox" parameter: "'.concat(e,'"'));return{northEast:{lat:n,lng:r},southWest:{lat:i,lng:a}}}(e)}function Be(e,n,r){return e.map(function(e,t){return D({},e,{__position:r*n+t+1})})}function Qe(e,t){return t?e.map(function(e){return D({},e,{__queryID:t})}):e}function qe(e){var o=e.instantSearchInstance,c=e.helper,u=e.attribute,l=e.widgetType;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r=t[0],i=t[1],a=t[2],s=void 0===a?"Filter Applied":a;1===t.length&&"object"===h(t[0])?o.sendEventToInsights(t[0]):"click"!==r||2!==t.length&&3!==t.length||function(e,t,n){return e.state.isHierarchicalFacet(t)?e.state.isHierarchicalFacetRefined(t,n):e.state.isConjunctiveFacet(t)?e.state.isFacetRefined(t,n):e.state.isDisjunctiveFacetRefined(t,n)}(c,u,i)||o.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:l,eventType:r,payload:{eventName:s,index:c.getIndex(),filters:["".concat(u,":").concat(JSON.stringify(i))]}})}}function Ue(e){var t=e.index,n=e.widgetType,r=(e.methodName,e.args);if(1===r.length&&"object"===h(r[0]))return r[0];var i=r[0],a=r[1],s=r[2];if(!a)return null;if(("click"===i||"conversion"===i)&&!s)return null;var o=Array.isArray(a)?a:[a];if(0===o.length)return null;var c=o[0].__queryID,u=o.map(function(e){return e.objectID}),l=o.map(function(e){return e.__position});return"view"===i?{insightsMethod:"viewedObjectIDs",widgetType:n,eventType:i,payload:{eventName:s||"Hits Viewed",index:t,objectIDs:u}}:"click"===i?{insightsMethod:"clickedObjectIDsAfterSearch",widgetType:n,eventType:i,payload:{eventName:s,index:t,queryID:c,objectIDs:u,positions:l}}:"conversion"===i?{insightsMethod:"convertedObjectIDsAfterSearch",widgetType:n,eventType:i,payload:{eventName:s,index:t,queryID:c,objectIDs:u}}:null}function Ve(e){var i=e.instantSearchInstance,a=e.index,s=e.widgetType;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r=Ue({widgetType:s,index:a,methodName:"sendEvent",args:t});r&&i.sendEventToInsights(r)}}function We(e){var i=e.index,a=e.widgetType;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r=Ue({widgetType:a,index:i,methodName:"bindEvent",args:t});return r?"data-insights-event=".concat(btoa(JSON.stringify(r))):""}}function $e(e,n){if(!e)return null;var r=e.numericRefinements[n],i=[];return Object.keys(r).filter(function(e){return Array.isArray(r[e])&&0<r[e].length}).forEach(function(t){r[t].forEach(function(e){i.push("".concat(n).concat(t).concat(e))})}),i}var ze=Ae({name:"index-widget"});function Ke(e){return"ais.index"===e.$$type}function Je(e,t){var n=t.state,r=t.isPageReset,i=t._uiState;n!==e.state&&(e.state=n,e.emit("change",{state:e.state,results:e.lastResults,isPageReset:r,_uiState:i}))}function Ye(e,n,t){var r=2<arguments.length&&void 0!==t?t:{};return e.filter(function(e){return!Ke(e)}).reduce(function(e,t){return t.getWidgetState?t.getWidgetState(e,n):e},r)}function Ge(e,t){var n=t.initialSearchParameters,r=A(t,["initialSearchParameters"]);return e.filter(function(e){return!Ke(e)}).reduce(function(e,t){return t.getWidgetSearchParameters?t.getWidgetSearchParameters(e,r):e},n)}function Xe(e){var t=e.getParent();return function n(e){return e.filter(Ke).reduce(function(e,t){return e.concat.apply(e,[{indexId:t.getIndexId(),results:t.getResults(),helper:t.getHelper()}].concat(_(n(t.getWidgets()))))},[])}(t?t.getWidgets():[e])}function Ze(e){if(void 0===e||void 0===e.indexName)throw new Error(ze("The `indexName` option is required."));function o(e){return f._createURL(L({},u,Ye(l,{searchParameters:e,helper:m})))}var c=e.indexName,t=e.indexId,u=void 0===t?c:t,l=[],h={},f=null,d=null,m=null,p=null;return{$$type:"ais.index",getIndexName:function(){return c},getIndexId:function(){return u},getHelper:function(){return m},getResults:function(){return p&&p.lastResults},getParent:function(){return d},getWidgets:function(){return l},addWidgets:function(e){var t=this;if(!Array.isArray(e))throw new Error(ze("The `addWidgets` method expects an array of widgets."));if(e.some(function(e){return"function"!=typeof e.init&&"function"!=typeof e.render}))throw new Error(ze("The widget definition expects a `render` and/or an `init` method."));return l=l.concat(e),f&&Boolean(e.length)&&(Je(m,{state:Ge(l,{uiState:h,initialSearchParameters:m.state}),_uiState:h}),e.forEach(function(e){f&&e.init&&e.init({helper:m,parent:t,uiState:f._initialUiState,instantSearchInstance:f,state:m.state,templatesConfig:f.templatesConfig,createURL:o})}),f.scheduleSearch()),this},removeWidgets:function(t){if(!Array.isArray(t))throw new Error(ze("The `removeWidgets` method expects an array of widgets."));if(t.some(function(e){return"function"!=typeof e.dispose}))throw new Error(ze("The widget definition expects a `dispose` method."));if(l=l.filter(function(e){return-1===t.indexOf(e)}),f&&Boolean(t.length)){var e=t.reduce(function(e,t){return t.dispose({helper:m,state:e})||e},m.state);h=Ye(l,{searchParameters:e,helper:m}),m.setState(Ge(l,{uiState:h,initialSearchParameters:e})),l.length&&f.scheduleSearch()}return this},init:function(e){var t=this,r=e.instantSearchInstance,n=e.parent,i=e.uiState;f=r,d=n,h=i[u]||{};var a=r.mainHelper,s=Ge(l,{uiState:h,initialSearchParameters:new ae.SearchParameters({index:c})});(m=ae({},s.index,s)).search=function(){return r.onStateChange?(r.onStateChange({uiState:r.mainIndex.getWidgetState({}),setUiState:r.setUiState.bind(r)}),a):a.search()},m.searchWithoutTriggeringOnStateChange=function(){return a.search()},m.searchForFacetValues=function(e,t,n,r){var i=m.state.setQueryParameters(r);return a.searchForFacetValues(e,t,n,i)},p=a.derive(function(){return je.apply(void 0,_(function(e){for(var t=e.getParent(),n=[e.getHelper().state];null!==t;)n=[t.getHelper().state].concat(n),t=t.getParent();return n}(t)))}),m.on("change",function(e){e.isPageReset&&!function n(e){var t=e.filter(Ke);0!==t.length&&t.forEach(function(e){var t=e.getHelper();Je(t,{state:t.state.resetPage(),isPageReset:!0}),n(e.getWidgets())})}(l)}),p.on("search",function(){r.scheduleStalledRender()}),p.on("result",function(e){var t=e.results;r.scheduleRender(),m.lastResults=t}),l.forEach(function(e){e.init&&e.init({uiState:i,helper:m,parent:t,instantSearchInstance:r,state:m.state,templatesConfig:r.templatesConfig,createURL:o})}),m.on("change",function(e){var t=e.state,n=e._uiState;h=Ye(l,{searchParameters:t,helper:m},n||{}),r.onStateChange||r.onInternalStateChange()})},render:function(e){var t=this,n=e.instantSearchInstance;l.forEach(function(e){e.render&&p.lastResults&&e.render({helper:m,instantSearchInstance:n,results:p.lastResults,scopedResults:Xe(t),state:p.lastResults._state,templatesConfig:n.templatesConfig,createURL:o,searchMetadata:{isSearchStalled:n._isSearchStalled}})})},dispose:function(){l.forEach(function(e){e.dispose&&e.dispose({helper:m,state:m.state})}),d=f=null,m.removeAllListeners(),m=null,p.detach(),p=null},getWidgetState:function(e){return l.filter(Ke).reduce(function(e,t){return t.getWidgetState(e)},D({},e,L({},this.getIndexId(),h)))},getWidgetSearchParameters:function(e,t){var n=t.uiState;return Ge(l,{uiState:n,initialSearchParameters:e})},refreshUiState:function(){h=Ye(l,{searchParameters:this.getHelper().state,helper:this.getHelper()})}}}var et={highlightPreTag:"__ais-highlight__",highlightPostTag:"__/ais-highlight__"},tt={highlightPreTag:"<mark>",highlightPostTag:"</mark>"};function nt(e){return function(e){return e&&Me.test(e)?e.replace(ke,function(e){return Ee[e]}):e}(e).replace(new RegExp(et.highlightPreTag,"g"),tt.highlightPreTag).replace(new RegExp(et.highlightPostTag,"g"),tt.highlightPostTag)}function rt(n){return Fe(n)&&"string"!=typeof n.value?Object.keys(n).reduce(function(e,t){return D({},e,L({},t,rt(n[t])))},{}):Array.isArray(n)?n.map(rt):D({},n,{value:nt(n.value)})}function it(e){return void 0===e.__escaped&&((e=e.map(function(e){var t=f({},e);return t._highlightResult&&(t._highlightResult=rt(t._highlightResult)),t._snippetResult&&(t._snippetResult=rt(t._snippetResult)),t})).__escaped=!0),e}function at(a){return function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.descendantName,n=e.modifierName,r=t?"-".concat(t):"",i=n?"--".concat(n):"";return"".concat("ais","-").concat(a).concat(r).concat(i)}}var st=at("Highlight");function ot(e){var t=e.attribute,n=e.highlightedTagName,r=void 0===n?"mark":n,i=e.hit,a=e.cssClasses,s=void 0===a?{}:a,o=Ne(i,"_highlightResult.".concat(t,".value"))||"",c=st({descendantName:"highlighted"})+(s.highlighted?" ".concat(s.highlighted):"");return o.replace(new RegExp(tt.highlightPreTag,"g"),"<".concat(r,' class="').concat(c,'">')).replace(new RegExp(tt.highlightPostTag,"g"),"</".concat(r,">"))}var ct=at("Snippet");function ut(e){var t=e.attribute,n=e.highlightedTagName,r=void 0===n?"mark":n,i=e.hit,a=e.cssClasses,s=void 0===a?{}:a,o=Ne(i,"_snippetResult.".concat(t,".value"))||"",c=ct({descendantName:"highlighted"})+(s.highlighted?" ".concat(s.highlighted):"");return o.replace(new RegExp(tt.highlightPreTag,"g"),"<".concat(r,' class="').concat(c,'">')).replace(new RegExp(tt.highlightPostTag,"g"),"</".concat(r,">"))}function lt(e,t){return function(e){var t,n=e.method,r=e.payload;if("object"!==h(r))throw new Error("The insights helper expects the payload to be an object.");try{t=btoa(JSON.stringify(r))}catch(e){throw new Error("Could not JSON serialize the payload object.")}return'data-insights-method="'.concat(n,'" data-insights-payload="').concat(t,'"')}({method:e,payload:t})}function ht(){return function(e){for(var t="".concat(e,"="),n=document.cookie.split(";"),r=0;r<n.length;r++){for(var i=n[r];" "===i.charAt(0);)i=i.substring(1);if(0===i.indexOf(t))return i.substring(t.length,i.length)}}("_ALGOLIA")}function ft(e){e.configure;return A(e,["configure"])}function dt(){return{stateToRoute:function(n){return Object.keys(n).reduce(function(e,t){return D({},e,L({},t,ft(n[t])))},{})},routeToState:function(e){var n=0<arguments.length&&void 0!==e?e:{};return Object.keys(n).reduce(function(e,t){return D({},e,L({},t,ft(n[t])))},{})}}}function mt(e,t){for(var n=t&&t.plainObjects?Object.create(null):{},r=0;r<e.length;++r)void 0!==e[r]&&(n[r]=e[r]);return n}function pt(e,t){kt.apply(e,Et(t)?t:[t])}function vt(e,t,n,r,i,a,s,o,c,u,l,h,f){var d=e;if("function"==typeof s?d=s(t,d):d instanceof Date?d=u(d):"comma"===n&&Et(d)&&(d=d.join(",")),null===d){if(r)return a&&!h?a(t,jt.encoder,f):t;d=""}if(function(e){return"string"==typeof e||"number"==typeof e||"boolean"==typeof e||"symbol"==typeof e||"bigint"==typeof e}(d)||_t.isBuffer(d))return a?[l(h?t:a(t,jt.encoder,f))+"="+l(a(d,jt.encoder,f))]:[l(t)+"="+l(String(d))];var m,p=[];if(void 0===d)return p;if(Et(s))m=s;else{var v=Object.keys(d);m=o?v.sort(o):v}for(var g=0;g<m.length;++g){var y=m[g];i&&null===d[y]||(Et(d)?pt(p,vt(d[y],"function"==typeof n?n(t,y):t,n,r,i,a,s,o,c,u,l,h,f)):pt(p,vt(d[y],t+(c?"."+y:"["+y+"]"),n,r,i,a,s,o,c,u,l,h,f)))}return p}function gt(e,t,n){if(e){var r=n.allowDots?e.replace(/\.([^.[]+)/g,"[$1]"):e,i=/(\[[^[\]]*])/g,a=0<n.depth&&/(\[[^[\]]*])/.exec(r),s=a?r.slice(0,a.index):r,o=[];if(s){if(!n.plainObjects&&Ot.call(Object.prototype,s)&&!n.allowPrototypes)return;o.push(s)}for(var c=0;0<n.depth&&null!==(a=i.exec(r))&&c<n.depth;){if(c+=1,!n.plainObjects&&Ot.call(Object.prototype,a[1].slice(1,-1))&&!n.allowPrototypes)return;o.push(a[1])}return a&&o.push("["+r.slice(a.index)+"]"),function(e,t,n){for(var r=t,i=e.length-1;0<=i;--i){var a,s=e[i];if("[]"===s&&n.parseArrays)a=[].concat(r);else{a=n.plainObjects?Object.create(null):{};var o="["===s.charAt(0)&&"]"===s.charAt(s.length-1)?s.slice(1,-1):s,c=parseInt(o,10);n.parseArrays||""!==o?!isNaN(c)&&s!==o&&String(c)===o&&0<=c&&n.parseArrays&&c<=n.arrayLimit?(a=[])[c]=r:a[o]=r:a={0:r}}r=a}return r}(o,t,n)}}function yt(e){var t=e.qsModule,n=e.routeState,r=e.location,i=r.protocol,a=r.hostname,s=r.port,o=void 0===s?"":s,c=r.pathname,u=r.hash,l=t.stringify(n),h=""===o?"":":".concat(o);return l?"".concat(i,"//").concat(a).concat(h).concat(c,"?").concat(l).concat(u):"".concat(i,"//").concat(a).concat(h).concat(c).concat(u)}function bt(e){var t=e.qsModule,n=e.location;return t.parse(n.search.slice(1),{arrayLimit:99})}function Rt(e){e&&(window.document.title=e)}var wt=Object.prototype.hasOwnProperty,St=Array.isArray,Pt=function(){for(var e=[],t=0;t<256;++t)e.push("%"+((t<16?"0":"")+t.toString(16)).toUpperCase());return e}(),_t={arrayToObject:mt,assign:function(e,n){return Object.keys(n).reduce(function(e,t){return e[t]=n[t],e},e)},combine:function(e,t){return[].concat(e,t)},compact:function(e){for(var t=[{obj:{o:e},prop:"o"}],n=[],r=0;r<t.length;++r)for(var i=t[r],a=i.obj[i.prop],s=Object.keys(a),o=0;o<s.length;++o){var c=s[o],u=a[c];"object"==typeof u&&null!==u&&-1===n.indexOf(u)&&(t.push({obj:a,prop:c}),n.push(u))}return function(e){for(;1<e.length;){var t=e.pop(),n=t.obj[t.prop];if(St(n)){for(var r=[],i=0;i<n.length;++i)void 0!==n[i]&&r.push(n[i]);t.obj[t.prop]=r}}}(t),e},decode:function(e,t,n){var r=e.replace(/\+/g," ");if("iso-8859-1"===n)return r.replace(/%[0-9a-f]{2}/gi,unescape);try{return decodeURIComponent(r)}catch(e){return r}},encode:function(e,t,n){if(0===e.length)return e;var r=e;if("symbol"==typeof e?r=Symbol.prototype.toString.call(e):"string"!=typeof e&&(r=String(e)),"iso-8859-1"===n)return escape(r).replace(/%u[0-9a-f]{4}/gi,function(e){return"%26%23"+parseInt(e.slice(2),16)+"%3B"});for(var i="",a=0;a<r.length;++a){var s=r.charCodeAt(a);45===s||46===s||95===s||126===s||48<=s&&s<=57||65<=s&&s<=90||97<=s&&s<=122?i+=r.charAt(a):s<128?i+=Pt[s]:s<2048?i+=Pt[192|s>>6]+Pt[128|63&s]:s<55296||57344<=s?i+=Pt[224|s>>12]+Pt[128|s>>6&63]+Pt[128|63&s]:(a+=1,s=65536+((1023&s)<<10|1023&r.charCodeAt(a)),i+=Pt[240|s>>18]+Pt[128|s>>12&63]+Pt[128|s>>6&63]+Pt[128|63&s])}return i},isBuffer:function(e){return!(!e||"object"!=typeof e)&&!!(e.constructor&&e.constructor.isBuffer&&e.constructor.isBuffer(e))},isRegExp:function(e){return"[object RegExp]"===Object.prototype.toString.call(e)},merge:function r(i,a,s){if(!a)return i;if("object"!=typeof a){if(St(i))i.push(a);else{if(!i||"object"!=typeof i)return[i,a];(s&&(s.plainObjects||s.allowPrototypes)||!wt.call(Object.prototype,a))&&(i[a]=!0)}return i}if(!i||"object"!=typeof i)return[i].concat(a);var e=i;return St(i)&&!St(a)&&(e=mt(i,s)),St(i)&&St(a)?(a.forEach(function(e,t){if(wt.call(i,t)){var n=i[t];n&&"object"==typeof n&&e&&"object"==typeof e?i[t]=r(n,e,s):i.push(e)}else i[t]=e}),i):Object.keys(a).reduce(function(e,t){var n=a[t];return wt.call(e,t)?e[t]=r(e[t],n,s):e[t]=n,e},e)}},Nt=String.prototype.replace,xt=/%20/g,Ft={RFC1738:"RFC1738",RFC3986:"RFC3986"},It=_t.assign({default:Ft.RFC3986,formatters:{RFC1738:function(e){return Nt.call(e,xt,"+")},RFC3986:function(e){return String(e)}}},Ft),Ct=Object.prototype.hasOwnProperty,Tt={brackets:function(e){return e+"[]"},comma:"comma",indices:function(e,t){return e+"["+t+"]"},repeat:function(e){return e}},Et=Array.isArray,kt=Array.prototype.push,Mt=Date.prototype.toISOString,Lt=It.default,jt={addQueryPrefix:!1,allowDots:!1,charset:"utf-8",charsetSentinel:!1,delimiter:"&",encode:!0,encoder:_t.encode,encodeValuesOnly:!1,format:Lt,formatter:It.formatters[Lt],indices:!1,serializeDate:function(e){return Mt.call(e)},skipNulls:!1,strictNullHandling:!1},Ot=Object.prototype.hasOwnProperty,At={allowDots:!1,allowPrototypes:!1,arrayLimit:20,charset:"utf-8",charsetSentinel:!1,comma:!1,decoder:_t.decode,delimiter:"&",depth:5,ignoreQueryPrefix:!1,interpretNumericEntities:!1,parameterLimit:1e3,parseArrays:!0,plainObjects:!1,strictNullHandling:!1},Ht={formats:It,parse:function(e,t){var n=function(e){if(!e)return At;if(null!==e.decoder&&void 0!==e.decoder&&"function"!=typeof e.decoder)throw new TypeError("Decoder has to be a function.");if(void 0!==e.charset&&"utf-8"!==e.charset&&"iso-8859-1"!==e.charset)throw new Error("The charset option must be either utf-8, iso-8859-1, or undefined");var t=void 0===e.charset?At.charset:e.charset;return{allowDots:void 0===e.allowDots?At.allowDots:!!e.allowDots,allowPrototypes:"boolean"==typeof e.allowPrototypes?e.allowPrototypes:At.allowPrototypes,arrayLimit:"number"==typeof e.arrayLimit?e.arrayLimit:At.arrayLimit,charset:t,charsetSentinel:"boolean"==typeof e.charsetSentinel?e.charsetSentinel:At.charsetSentinel,comma:"boolean"==typeof e.comma?e.comma:At.comma,decoder:"function"==typeof e.decoder?e.decoder:At.decoder,delimiter:"string"==typeof e.delimiter||_t.isRegExp(e.delimiter)?e.delimiter:At.delimiter,depth:"number"==typeof e.depth||!1===e.depth?+e.depth:At.depth,ignoreQueryPrefix:!0===e.ignoreQueryPrefix,interpretNumericEntities:"boolean"==typeof e.interpretNumericEntities?e.interpretNumericEntities:At.interpretNumericEntities,parameterLimit:"number"==typeof e.parameterLimit?e.parameterLimit:At.parameterLimit,parseArrays:!1!==e.parseArrays,plainObjects:"boolean"==typeof e.plainObjects?e.plainObjects:At.plainObjects,strictNullHandling:"boolean"==typeof e.strictNullHandling?e.strictNullHandling:At.strictNullHandling}}(t);if(""===e||null==e)return n.plainObjects?Object.create(null):{};for(var r="string"==typeof e?function(e,t){var n,r={},i=t.ignoreQueryPrefix?e.replace(/^\?/,""):e,a=t.parameterLimit===1/0?void 0:t.parameterLimit,s=i.split(t.delimiter,a),o=-1,c=t.charset;if(t.charsetSentinel)for(n=0;n<s.length;++n)0===s[n].indexOf("utf8=")&&("utf8=%E2%9C%93"===s[n]?c="utf-8":"utf8=%26%2310003%3B"===s[n]&&(c="iso-8859-1"),o=n,n=s.length);for(n=0;n<s.length;++n)if(n!==o){var u,l,h=s[n],f=h.indexOf("]="),d=-1===f?h.indexOf("="):f+1;(l=-1===d?(u=t.decoder(h,At.decoder,c),t.strictNullHandling?null:""):(u=t.decoder(h.slice(0,d),At.decoder,c),t.decoder(h.slice(d+1),At.decoder,c)))&&t.interpretNumericEntities&&"iso-8859-1"===c&&(l=l.replace(/&#(\d+);/g,function(e,t){return String.fromCharCode(parseInt(t,10))})),l&&t.comma&&-1<l.indexOf(",")&&(l=l.split(",")),Ot.call(r,u)?r[u]=_t.combine(r[u],l):r[u]=l}return r}(e,n):e,i=n.plainObjects?Object.create(null):{},a=Object.keys(r),s=0;s<a.length;++s){var o=a[s],c=gt(o,r[o],n);i=_t.merge(i,c,n)}return _t.compact(i)},stringify:function(e,t){var n,r=e,i=function(e){if(!e)return jt;if(null!==e.encoder&&void 0!==e.encoder&&"function"!=typeof e.encoder)throw new TypeError("Encoder has to be a function.");var t=e.charset||jt.charset;if(void 0!==e.charset&&"utf-8"!==e.charset&&"iso-8859-1"!==e.charset)throw new TypeError("The charset option must be either utf-8, iso-8859-1, or undefined");var n=It.default;if(void 0!==e.format){if(!Ct.call(It.formatters,e.format))throw new TypeError("Unknown format option provided.");n=e.format}var r=It.formatters[n],i=jt.filter;return"function"!=typeof e.filter&&!Et(e.filter)||(i=e.filter),{addQueryPrefix:"boolean"==typeof e.addQueryPrefix?e.addQueryPrefix:jt.addQueryPrefix,allowDots:void 0===e.allowDots?jt.allowDots:!!e.allowDots,charset:t,charsetSentinel:"boolean"==typeof e.charsetSentinel?e.charsetSentinel:jt.charsetSentinel,delimiter:void 0===e.delimiter?jt.delimiter:e.delimiter,encode:"boolean"==typeof e.encode?e.encode:jt.encode,encoder:"function"==typeof e.encoder?e.encoder:jt.encoder,encodeValuesOnly:"boolean"==typeof e.encodeValuesOnly?e.encodeValuesOnly:jt.encodeValuesOnly,filter:i,formatter:r,serializeDate:"function"==typeof e.serializeDate?e.serializeDate:jt.serializeDate,skipNulls:"boolean"==typeof e.skipNulls?e.skipNulls:jt.skipNulls,sort:"function"==typeof e.sort?e.sort:null,strictNullHandling:"boolean"==typeof e.strictNullHandling?e.strictNullHandling:jt.strictNullHandling}}(t);"function"==typeof i.filter?r=(0,i.filter)("",r):Et(i.filter)&&(n=i.filter);var a,s=[];if("object"!=typeof r||null===r)return"";a=t&&t.arrayFormat in Tt?t.arrayFormat:t&&"indices"in t?t.indices?"indices":"repeat":"indices";var o=Tt[a];n=n||Object.keys(r),i.sort&&n.sort(i.sort);for(var c=0;c<n.length;++c){var u=n[c];i.skipNulls&&null===r[u]||pt(s,vt(r[u],u,o,i.strictNullHandling,i.skipNulls,i.encode?i.encoder:null,i.filter,i.sort,i.allowDots,i.serializeDate,i.formatter,i.encodeValuesOnly,i.charset))}var l=s.join(i.delimiter),h=!0===i.addQueryPrefix?"?":"";return i.charsetSentinel&&("iso-8859-1"===i.charset?h+="utf8=%26%2310003%3B&":h+="utf8=%E2%9C%93&"),0<l.length?h+l:""}},Dt=function(){function u(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.windowTitle,n=e.writeDelay,r=void 0===n?400:n,i=e.createURL,a=void 0===i?yt:i,s=e.parseURL,o=void 0===s?bt:s;k(this,u),L(this,"windowTitle",void 0),L(this,"writeDelay",void 0),L(this,"_createURL",void 0),L(this,"parseURL",void 0),L(this,"writeTimer",void 0),this.windowTitle=t,this.writeTimer=void 0,this.writeDelay=r,this._createURL=a,this.parseURL=o;var c=this.windowTitle&&this.windowTitle(this.read());Rt(c)}return M(u,[{key:"read",value:function(){return this.parseURL({qsModule:Ht,location:window.location})}},{key:"write",value:function(e){var t=this,n=this.createURL(e),r=this.windowTitle&&this.windowTitle(e);this.writeTimer&&window.clearTimeout(this.writeTimer),this.writeTimer=window.setTimeout(function(){Rt(r),window.history.pushState(e,r||"",n),t.writeTimer=void 0},this.writeDelay)}},{key:"onUpdate",value:function(n){var r=this;this._onPopState=function(e){r.writeTimer&&(window.clearTimeout(r.writeTimer),r.writeTimer=void 0);var t=e.state;n(t||r.read())},window.addEventListener("popstate",this._onPopState)}},{key:"createURL",value:function(e){return this._createURL({qsModule:Ht,routeState:e,location:window.location})}},{key:"dispose",value:function(){this._onPopState&&window.removeEventListener("popstate",this._onPopState),this.writeTimer&&window.clearTimeout(this.writeTimer),this.write({})}}]),u}();function Bt(e){return new Dt(e)}function Qt(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.router,i=void 0===n?Bt():n,r=t.stateMapping,s=void 0===r?dt():r;return function(e){var a=e.instantSearchInstance;a._createURL=function(n){var e=Object.keys(n).reduce(function(e,t){return D({},e,L({},t,n[t]))},a.mainIndex.getWidgetState({})),t=s.stateToRoute(e);return i.createURL(t)},a._initialUiState=D({},a._initialUiState,{},s.routeToState(i.read()));var r=void 0;return{onStateChange:function(e){var t=e.uiState,n=s.stateToRoute(t);void 0!==r&&Te(r,n)||(i.write(n),r=n)},subscribe:function(){i.onUpdate(function(e){var i=s.routeToState(e);!function t(e,n){n(e),e.getWidgets().filter(function(e){return"ais.index"===e.$$type}).forEach(function(e){t(e,n)})}(a.mainIndex,function(e){var t=e.getWidgets(),n=i[e.getIndexId()]||{},r=t.reduce(function(e,t){return t.getWidgetSearchParameters?t.getWidgetSearchParameters(e,{uiState:n}):e},e.getHelper().state);e.getHelper().overrideStateWithoutTriggeringChangeEvent(r),a.scheduleSearch()})})},unsubscribe:function(){i.dispose()}}}}var qt=Ae({name:"instantsearch"});function Ut(){return"#"}function Vt(f,e){var i=1<arguments.length&&void 0!==e?e:_e;return Pe(f,$t()),function(a){var e=a||{},t=e.includedAttributes,s=void 0===t?[]:t,n=e.excludedAttributes,o=void 0===n?["query"]:n,r=e.transformItems,c=void 0===r?function(e){return e}:r;if(a.includedAttributes&&a.excludedAttributes)throw new Error($t("The options `includedAttributes` and `excludedAttributes` cannot be used together."));function u(){return h.refine()}function l(){return h.createURL()}var h={refine:_e,createURL:function(){return""}};return{$$type:"ais.clearRefinements",init:function(e){var t=e.instantSearchInstance;f({hasRefinements:!1,refine:u,createURL:l,instantSearchInstance:t,widgetParams:a},!0)},render:function(e){var t=e.scopedResults,n=e.createURL,r=e.instantSearchInstance,i=t.reduce(function(e,t){return e.concat(function(e){var t=e.scopedResult,n=e.includedAttributes,r=e.excludedAttributes,i=e.transformItems,a=-1!==n.indexOf("query")||-1===r.indexOf("query");return{helper:t.helper,items:i(le(Re(t.results,t.helper.state,a).map(function(e){return e.attribute}).filter(function(e){return 0===n.length||-1!==n.indexOf(e)}).filter(function(e){return"query"===e&&a||-1===r.indexOf(e)})))}}({scopedResult:t,includedAttributes:s,excludedAttributes:o,transformItems:c}))},[]);h.refine=function(){i.forEach(function(e){var t=e.helper,n=e.items;t.setState(we({helper:t,attributesToClear:n})).search()})},h.createURL=function(){return n(je.apply(void 0,_(i.map(function(e){return we({helper:e.helper,attributesToClear:e.items})}))))},f({hasRefinements:i.some(function(e){return 0<e.items.length}),refine:u,createURL:l,instantSearchInstance:r,widgetParams:a},!1)},dispose:function(){i()}}}}var Wt=function(){function b(e){var r;k(this,b),L(H(r=B(this,O(b).call(this))),"client",void 0),L(H(r),"indexName",void 0),L(H(r),"insightsClient",void 0),L(H(r),"onStateChange",null),L(H(r),"helper",void 0),L(H(r),"mainHelper",void 0),L(H(r),"mainIndex",void 0),L(H(r),"started",void 0),L(H(r),"templatesConfig",void 0),L(H(r),"_stalledSearchDelay",void 0),L(H(r),"_searchStalledTimer",void 0),L(H(r),"_isSearchStalled",void 0),L(H(r),"_initialUiState",void 0),L(H(r),"_createURL",void 0),L(H(r),"_searchFunction",void 0),L(H(r),"_mainHelperSearch",void 0),L(H(r),"middleware",[]),L(H(r),"sendEventToInsights",void 0),L(H(r),"scheduleSearch",se(function(){r.started&&r.mainHelper.search()})),L(H(r),"scheduleRender",se(function(){r.mainHelper.hasPendingRequests()||(clearTimeout(r._searchStalledTimer),r._searchStalledTimer=null,r._isSearchStalled=!1),r.mainIndex.render({instantSearchInstance:H(r)}),r.emit("render")})),L(H(r),"setUiState",function(e){if(!r.mainHelper)throw new Error(qt("The `start` method needs to be called before `setUiState`."));r.mainIndex.refreshUiState();var n="function"==typeof e?e(r.mainIndex.getWidgetState({})):e;!function e(t){t.getHelper().overrideStateWithoutTriggeringChangeEvent(t.getWidgetSearchParameters(t.getHelper().state,{uiState:n[t.getIndexId()]})),t.getWidgets().filter(Ke).forEach(e)}(r.mainIndex),r.scheduleSearch(),r.onInternalStateChange()}),L(H(r),"onInternalStateChange",function(){var t=r.mainIndex.getWidgetState({});r.middleware.forEach(function(e){e.onStateChange({uiState:t})})});var t=e.indexName,n=void 0===t?null:t,i=e.numberLocale,a=e.initialUiState,s=void 0===a?{}:a,o=e.routing,c=void 0===o?null:o,u=e.searchFunction,l=e.stalledSearchDelay,h=void 0===l?200:l,f=e.searchClient,d=void 0===f?null:f,m=e.insightsClient,p=void 0===m?null:m,v=e.onStateChange,g=void 0===v?null:v;if(null===n)throw new Error(qt("The `indexName` option is required."));if(null===d)throw new Error(qt("The `searchClient` option is required."));if("function"!=typeof d.search)throw new Error("The `searchClient` must implement a `search` method.\n\nSee: https://www.algolia.com/doc/guides/building-search-ui/going-further/backend-search/in-depth/backend-instantsearch/js/");if("function"==typeof d.addAlgoliaAgent&&d.addAlgoliaAgent("instantsearch.js (".concat("4.8.3",")")),p&&"function"!=typeof p)throw new Error(qt("The `insightsClient` option should be a function."));if(r.client=d,r.insightsClient=p,r.indexName=n,r.helper=null,r.mainHelper=null,r.mainIndex=Ze({indexName:n}),r.onStateChange=g,r.started=!1,r.templatesConfig={helpers:function(e){var n=e.numberLocale;return{formatNumber:function(e,t){return Number(t(e)).toLocaleString(n)},highlight:function(e,t){try{return t(ot(D({},JSON.parse(e),{hit:this})))}catch(e){throw new Error('\nThe highlight helper expects a JSON object of the format:\n{ "attribute": "name", "highlightedTagName": "mark" }')}},snippet:function(e,t){try{return t(ut(D({},JSON.parse(e),{hit:this})))}catch(e){throw new Error('\nThe snippet helper expects a JSON object of the format:\n{ "attribute": "name", "highlightedTagName": "mark" }')}},insights:function(e,t){try{var n=JSON.parse(e),r=n.method,i=n.payload;return t(lt(r,D({objectIDs:[this.objectID]},i)))}catch(e){throw new Error('\nThe insights helper expects a JSON object of the format:\n{ "method": "method-name", "payload": { "eventName": "name of the event" } }')}}}}({numberLocale:i}),compileOptions:{}},r._stalledSearchDelay=h,r._searchStalledTimer=null,r._isSearchStalled=!1,r._createURL=Ut,r._initialUiState=s,u&&(r._searchFunction=u),r.sendEventToInsights=_e,c){var y="boolean"==typeof c?void 0:c;r.use(Qt(y))}return r}return j(b,e),M(b,[{key:"use",value:function(){for(var n=this,e=arguments.length,t=new Array(e),r=0;r<e;r++)t[r]=arguments[r];var i=t.map(function(e){var t=e({instantSearchInstance:n});return n.middleware.push(t),t});return this.started&&i.forEach(function(e){e.subscribe()}),this}},{key:"EXPERIMENTAL_use",value:function(){return this.use.apply(this,arguments)}},{key:"addWidget",value:function(e){return this.addWidgets([e])}},{key:"addWidgets",value:function(e){if(!Array.isArray(e))throw new Error(qt("The `addWidgets` method expects an array of widgets. Please use `addWidget`."));if(e.some(function(e){return"function"!=typeof e.init&&"function"!=typeof e.render}))throw new Error(qt("The widget definition expects a `render` and/or an `init` method."));return this.mainIndex.addWidgets(e),this}},{key:"removeWidget",value:function(e){return this.removeWidgets([e])}},{key:"removeWidgets",value:function(e){if(!Array.isArray(e))throw new Error(qt("The `removeWidgets` method expects an array of widgets. Please use `removeWidget`."));if(e.some(function(e){return"function"!=typeof e.dispose}))throw new Error(qt("The widget definition expects a `dispose` method."));return this.mainIndex.removeWidgets(e),this}},{key:"start",value:function(){var r=this;if(this.started)throw new Error(qt("The `start` method has already been called once."));var t=ae(this.client,this.indexName);if(t.search=function(){return t.searchOnlyWithDerivedHelpers()},this._searchFunction){var i={search:function(){return new Promise(_e)}};this._mainHelperSearch=t.search.bind(t),t.search=function(){var n=r.mainIndex.getHelper(),e=ae(i,n.state.index,n.state);return e.once("search",function(e){var t=e.state;n.overrideStateWithoutTriggeringChangeEvent(t),r._mainHelperSearch()}),e.on("change",function(e){var t=e.state;n.setState(t)}),r._searchFunction(e),t}}t.on("error",function(e){var t=e.error;r.emit("error",{error:t})}),this.mainHelper=t,this.mainIndex.init({instantSearchInstance:this,parent:null,uiState:this._initialUiState}),this.middleware.forEach(function(e){e.subscribe()}),t.search(),this.helper=this.mainIndex.getHelper(),this.started=!0}},{key:"dispose",value:function(){this.scheduleSearch.cancel(),this.scheduleRender.cancel(),clearTimeout(this._searchStalledTimer),this.removeWidgets(this.mainIndex.getWidgets()),this.mainIndex.dispose(),this.started=!1,this.removeAllListeners(),this.mainHelper.removeAllListeners(),this.mainHelper=null,this.helper=null,this.middleware.forEach(function(e){e.unsubscribe()})}},{key:"scheduleStalledRender",value:function(){var e=this;this._searchStalledTimer||(this._searchStalledTimer=setTimeout(function(){e._isSearchStalled=!0,e.scheduleRender()},this._stalledSearchDelay))}},{key:"createURL",value:function(e){var t=0<arguments.length&&void 0!==e?e:{};if(!this.started)throw new Error(qt("The `start` method needs to be called before `createURL`."));return this._createURL(t)}},{key:"refresh",value:function(){if(!this.mainHelper)throw new Error(qt("The `start` method needs to be called before `refresh`."));this.mainHelper.clearCache().search()}}]),b}(),$t=Ae({name:"clear-refinements",connector:!0});function zt(l,e){var r=1<arguments.length&&void 0!==e?e:_e;return Pe(l,Kt()),function(s){if((s||{}).includedAttributes&&(s||{}).excludedAttributes)throw new Error(Kt("The options `includedAttributes` and `excludedAttributes` cannot be used together."));var e=s||{},o=e.includedAttributes,t=e.excludedAttributes,c=void 0===t?["query"]:t,n=e.transformItems,u=void 0===n?function(e){return e}:n;return{$$type:"ais.currentRefinements",init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance,i=u(Jt({results:{},helper:t,includedAttributes:o,excludedAttributes:c}));l({items:i,refine:function(e){return Gt(t,e)},createURL:function(e){return n(Yt(t.state,e))},instantSearchInstance:r,widgetParams:s},!0)},render:function(e){var t=e.scopedResults,n=e.helper,r=e.createURL,i=e.instantSearchInstance,a=t.reduce(function(e,t){return e.concat(u(Jt({results:t.results,helper:t.helper,includedAttributes:o,excludedAttributes:c})))},[]);l({items:a,refine:function(e){return Gt(n,e)},createURL:function(e){return r(Yt(n.state,e))},instantSearchInstance:i,widgetParams:s},!1)},dispose:function(){r()}}}}var Kt=Ae({name:"current-refinements",connector:!0});function Jt(e){var t=e.results,n=e.helper,r=e.includedAttributes,i=e.excludedAttributes,a=-1!==(r||[]).indexOf("query")||-1===(i||[]).indexOf("query"),s=r?function(e){return-1!==r.indexOf(e.attribute)}:function(e){return-1===i.indexOf(e.attribute)},o=Re(t,n.state,a).map(Xt).filter(s);return o.reduce(function(e,t){return[].concat(_(e.filter(function(e){return e.attribute!==t.attribute})),[{indexName:n.state.index,attribute:t.attribute,label:t.attribute,refinements:o.filter(function(e){return e.attribute===t.attribute}).sort(function(e,t){return"numeric"===e.type?e.value-t.value:0}),refine:function(e){return Gt(n,e)}}])},[])}function Yt(e,t){switch(t.type){case"facet":return e.removeFacetRefinement(t.attribute,String(t.value));case"disjunctive":return e.removeDisjunctiveFacetRefinement(t.attribute,String(t.value));case"hierarchical":return e.removeHierarchicalFacetRefinement(t.attribute);case"exclude":return e.removeExcludeRefinement(t.attribute,String(t.value));case"numeric":return e.removeNumericRefinement(t.attribute,t.operator,String(t.value));case"tag":return e.removeTagRefinement(String(t.value));case"query":return e.setQueryParameter("query","");default:return e}}function Gt(e,t){e.setState(Yt(e.state,t)).search()}function Xt(e){var t="numeric"===e.type?Number(e.name):e.name,n=e.operator?"".concat(function(e){switch(e){case">=":return"≥";case"<=":return"≤";default:return e}}(e.operator)," ").concat(e.name):e.name,r={attribute:e.attribute,type:e.type,value:t,label:n};return void 0!==e.operator&&(r.operator=e.operator),void 0!==e.count&&(r.count=e.count),void 0!==e.exhaustive&&(r.exhaustive=e.exhaustive),r}var Zt=Ae({name:"hierarchical-menu",connector:!0});function en(R){var w=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(R,Zt()),function(){var l=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},c=l.attributes,e=l.separator,u=void 0===e?" > ":e,t=l.rootPath,h=void 0===t?null:t,n=l.showParentLevel,f=void 0===n||n,r=l.limit,d=void 0===r?10:r,i=l.showMore,m=void 0!==i&&i,a=l.showMoreLimit,p=void 0===a?20:a,s=l.sortBy,v=void 0===s?["name:asc"]:s,o=l.transformItems,g=void 0===o?function(e){return e}:o;if(!c||!Array.isArray(c)||0===c.length)throw new Error(Zt("The `attributes` option expects an array of strings."));if(!0===m&&p<=d)throw new Error(Zt("The `showMoreLimit` option must be greater than `limit`."));var y,b=Q(c,1)[0];return{$$type:"ais.hierarchicalMenu",isShowingMore:!1,toggleShowMore:function(){},cachedToggleShowMore:function(){this.toggleShowMore()},createToggleShowMore:function(e){var t=this;return function(){t.isShowingMore=!t.isShowingMore,t.render(e)}},getLimit:function(){return this.isShowingMore?p:d},init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance;y=qe({instantSearchInstance:r,helper:t,attribute:b,widgetType:this.$$type}),this.cachedToggleShowMore=this.cachedToggleShowMore.bind(this),this._refine=function(e){y("click",e),t.toggleRefinement(b,e).search()},R({items:[],createURL:function(e){return n(t.state.toggleRefinement(b,e))},refine:this._refine,sendEvent:y,instantSearchInstance:r,widgetParams:l,isShowingMore:!1,toggleShowMore:this.cachedToggleShowMore,canToggleShowMore:!1},!0)},_prepareFacetValues:function(e,i){var a=this;return e.slice(0,this.getLimit()).map(function(e){var t=e.name,n=e.path,r=A(e,["name","path"]);return Array.isArray(r.data)&&(r.data=a._prepareFacetValues(r.data,i)),D({},r,{label:t,value:n})})},render:function(e){var t=e.results,n=e.state,r=e.createURL,i=e.instantSearchInstance,a=t.getFacetValues(b,{sortBy:v}).data||[],s=g(this._prepareFacetValues(a),n);var o=n.maxValuesPerFacet,c=this.getLimit(),u=c<o?a.length<=c:a.length<c;this.toggleShowMore=this.createToggleShowMore(e),R({items:s,refine:this._refine,sendEvent:y,createURL:function(e){return r(n.toggleRefinement(b,e))},instantSearchInstance:i,widgetParams:l,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,canToggleShowMore:m&&(this.isShowingMore||!u)},!1)},dispose:function(e){var t=e.state;return w(),t.removeHierarchicalFacet(b).setQueryParameter("maxValuesPerFacet",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.getHierarchicalFacetBreadcrumb(b);return n.length?D({},e,{hierarchicalMenu:D({},e.hierarchicalMenu,L({},b,n))}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.hierarchicalMenu&&n.hierarchicalMenu[b];if(e.isHierarchicalFacet(b))e.getHierarchicalFacetByName(b);var i=e.removeHierarchicalFacet(b).addHierarchicalFacet({name:b,attributes:c,separator:u,rootPath:h,showParentLevel:f}),a=i.maxValuesPerFacet||0,s=Math.max(a,m?p:d),o=i.setQueryParameter("maxValuesPerFacet",s);return r?o.addHierarchicalFacetRefinement(b,r.join(u)):o.setQueryParameters({hierarchicalFacetsRefinements:D({},o.hierarchicalFacetsRefinements,L({},b,[]))})}}}}function tn(u,e){var r=1<arguments.length&&void 0!==e?e:_e;return Pe(u,rn()),function(i){var a,s,e=i||{},t=e.escapeHTML,o=void 0===t||t,n=e.transformItems,c=void 0===n?function(e){return e}:n;return{$$type:"ais.hits",init:function(e){var t=e.instantSearchInstance,n=e.helper;a=Ve({instantSearchInstance:t,index:n.getIndex(),widgetType:this.$$type}),s=We({index:n.getIndex(),widgetType:this.$$type}),u({hits:[],results:void 0,sendEvent:a,bindEvent:s,instantSearchInstance:t,widgetParams:i},!0)},render:function(e){var t=e.results,n=e.instantSearchInstance;o&&0<t.hits.length&&(t.hits=it(t.hits));var r=t.hits.__escaped;t.hits=Be(t.hits,t.page,t.hitsPerPage),t.hits=Qe(t.hits,t.queryID),t.hits=c(t.hits),t.hits.__escaped=r,a("view",t.hits),u({hits:t.hits,results:t,sendEvent:a,bindEvent:s,instantSearchInstance:n,widgetParams:i},!1)},dispose:function(e){var t=e.state;return r(),o?t.setQueryParameters(Object.keys(et).reduce(function(e,t){return D({},e,L({},t,void 0))},{})):t},getWidgetSearchParameters:function(e){return o?e.setQueryParameters(et):e}}}}function nn(e){var t=e.method,n=e.results,r=e.hits,i=e.objectIDs,a=n.index,s=function(n,e){return e.map(function(t){var e=ge(n,function(e){return e.objectID===t});if(void 0===e)throw new Error('Could not find objectID "'.concat(t,'" passed to `clickedObjectIDsAfterSearch` in the returned hits. This is necessary to infer the absolute position and the query ID.'));return e})}(r,i),o=function(e){var t=le(e.map(function(e){return e.__queryID}));if(1<t.length)throw new Error("Insights currently allows a single `queryID`. The `objectIDs` provided map to multiple `queryID`s.");var n=t[0];if("string"!=typeof n)throw new Error("Could not infer `queryID`. Ensure InstantSearch `clickAnalytics: true` was added with the Configure widget.\n\nSee: https://alg.li/lNiZZ7");return n}(s);switch(t){case"clickedObjectIDsAfterSearch":return{index:a,queryID:o,objectIDs:i,positions:function(e){return e.map(function(e){return e.__position})}(s)};case"convertedObjectIDsAfterSearch":return{index:a,queryID:o,objectIDs:i};default:throw new Error('Unsupported method passed to insights: "'.concat(t,'".'))}}var rn=Ae({name:"hits",connector:!0});function an(n){function r(s){return function(e,t){var n=e.results,r=e.hits,i=e.instantSearchInstance;if(n&&r&&i){var a=function(i,a,s){return function(e,t){if(!i){var n=Ae({name:"instantsearch"});throw new Error(n("The `insightsClient` option has not been provided to `instantsearch`."))}if(!Array.isArray(t.objectIDs))throw new TypeError("Expected `objectIDs` to be an array.");var r=nn({method:e,results:a,hits:s,objectIDs:t.objectIDs});i(e,D({},r,{},t))}}(i.insightsClient,n,r);return s(D({},e,{insights:a}),t)}return s(e,t)}}return function(e,t){return n(r(e),t)}}var sn,on,cn,un,ln,hn={},fn=[],dn=/acit|ex(?:s|g|n|p|$)|rph|grid|ows|mnc|ntw|ine[ch]|zoo|^ord|^--/i;function mn(e,t){for(var n in t)e[n]=t[n];return e}function pn(e){var t=e.parentNode;t&&t.removeChild(e)}function vn(e,t,n){var r,i,a,s,o=arguments;if(t=mn({},t),3<arguments.length)for(n=[n],r=3;r<arguments.length;r++)n.push(o[r]);if(null!=n&&(t.children=n),null!=e&&null!=e.defaultProps)for(i in e.defaultProps)void 0===t[i]&&(t[i]=e.defaultProps[i]);return s=t.key,null!=(a=t.ref)&&delete t.ref,null!=s&&delete t.key,gn(e,t,s,a)}function gn(e,t,n,r){var i={type:e,props:t,key:n,ref:r,__k:null,__p:null,__b:0,__e:null,l:null,__c:null,constructor:void 0};return sn.vnode&&sn.vnode(i),i}function yn(e){return e.children}function bn(e,t){this.props=e,this.context=t}function Rn(e,t){if(null==t)return e.__p?Rn(e.__p,e.__p.__k.indexOf(e)+1):null;for(var n;t<e.__k.length;t++)if(null!=(n=e.__k[t])&&null!=n.__e)return n.__e;return"function"==typeof e.type?Rn(e):null}function wn(e){var t,n;if(null!=(e=e.__p)&&null!=e.__c){for(e.__e=e.__c.base=null,t=0;t<e.__k.length;t++)if(null!=(n=e.__k[t])&&null!=n.__e){e.__e=e.__c.base=n.__e;break}return wn(e)}}function Sn(e){(!e.__d&&(e.__d=!0)&&1===on.push(e)||un!==sn.debounceRendering)&&(un=sn.debounceRendering,(sn.debounceRendering||cn)(Pn))}function Pn(){var e,t,n,r,i,a,s,o;for(on.sort(function(e,t){return t.__v.__b-e.__v.__b});e=on.pop();)e.__d&&(r=n=void 0,a=(i=(t=e).__v).__e,s=t.__P,o=t.u,t.u=!1,s&&(n=[],r=Cn(s,i,mn({},i),t.__n,void 0!==s.ownerSVGElement,null,n,o,null==a?Rn(i):a),Tn(n,i),r!=a&&wn(i)))}function _n(t,n,e,r,i,a,s,o,c){var u,l,h,f,d,m,p,v=e&&e.__k||fn,g=v.length;if(o==hn&&(o=null!=a?a[0]:g?Rn(e,0):null),u=0,n.__k=Nn(n.__k,function(e){if(null!=e){if(e.__p=n,e.__b=n.__b+1,null===(h=v[u])||h&&e.key==h.key&&e.type===h.type)v[u]=void 0;else for(l=0;l<g;l++){if((h=v[l])&&e.key==h.key&&e.type===h.type){v[l]=void 0;break}h=null}if(f=Cn(t,e,h=h||hn,r,i,a,s,null,o,c),(l=e.ref)&&h.ref!=l&&(p=p||[]).push(l,e.__c||f,e),null!=f){if(null==m&&(m=f),null!=e.l)f=e.l,e.l=null;else if(a==h||f!=o||null==f.parentNode){e:if(null==o||o.parentNode!==t)t.appendChild(f);else{for(d=o,l=0;(d=d.nextSibling)&&l<g;l+=2)if(d==f)break e;t.insertBefore(f,o)}"option"==n.type&&(t.value="")}o=f.nextSibling,"function"==typeof n.type&&(n.l=f)}}return u++,e}),n.__e=m,null!=a&&"function"!=typeof n.type)for(u=a.length;u--;)null!=a[u]&&pn(a[u]);for(u=g;u--;)null!=v[u]&&kn(v[u],v[u]);if(p)for(u=0;u<p.length;u++)En(p[u],p[++u],p[++u])}function Nn(e,t,n){if(null==n&&(n=[]),null==e||"boolean"==typeof e)t&&n.push(t(null));else if(Array.isArray(e))for(var r=0;r<e.length;r++)Nn(e[r],t,n);else n.push(t?t(function(e){if(null==e||"boolean"==typeof e)return null;if("string"==typeof e||"number"==typeof e)return gn(null,e,null,null);if(null==e.__e&&null==e.__c)return e;var t=gn(e.type,e.props,e.key,null);return t.__e=e.__e,t}(e)):e);return n}function xn(e,t,n){"-"===t[0]?e.setProperty(t,n):e[t]="number"==typeof n&&!1===dn.test(t)?n+"px":null==n?"":n}function Fn(e,t,n,r,i){var a,s,o,c,u;if("key"===(t=i?"className"===t?"class":t:"class"===t?"className":t)||"children"===t);else if("style"===t)if(a=e.style,"string"==typeof n)a.cssText=n;else{if("string"==typeof r&&(a.cssText="",r=null),r)for(s in r)n&&s in n||xn(a,s,"");if(n)for(o in n)r&&n[o]===r[o]||xn(a,o,n[o])}else"o"===t[0]&&"n"===t[1]?(c=t!==(t=t.replace(/Capture$/,"")),t=((u=t.toLowerCase())in e?u:t).slice(2),n?(r||e.addEventListener(t,In,c),(e.t||(e.t={}))[t]=n):e.removeEventListener(t,In,c)):"list"!==t&&"tagName"!==t&&"form"!==t&&!i&&t in e?e[t]=null==n?"":n:"function"!=typeof n&&"dangerouslySetInnerHTML"!==t&&(t!==(t=t.replace(/^xlink:?/,""))?null==n||!1===n?e.removeAttributeNS("http://www.w3.org/1999/xlink",t.toLowerCase()):e.setAttributeNS("http://www.w3.org/1999/xlink",t.toLowerCase(),n):null==n||!1===n?e.removeAttribute(t):e.setAttribute(t,n))}function In(e){return this.t[e.type](sn.event?sn.event(e):e)}function Cn(e,t,n,r,i,a,s,o,c,u){var l,h,f,d,m,p,v,g,y,b,R=t.type;if(void 0!==t.constructor)return null;(l=sn.__b)&&l(t);try{e:if("function"==typeof R){if(g=t.props,y=(l=R.contextType)&&r[l.__c],b=l?y?y.props.value:l.__p:r,n.__c?v=(h=t.__c=n.__c).__p=h.__E:("prototype"in R&&R.prototype.render?t.__c=h=new R(g,b):(t.__c=h=new bn(g,b),h.constructor=R,h.render=Mn),y&&y.sub(h),h.props=g,h.state||(h.state={}),h.context=b,h.__n=r,f=h.__d=!0,h.__h=[]),null==h.__s&&(h.__s=h.state),null!=R.getDerivedStateFromProps&&mn(h.__s==h.state?h.__s=mn({},h.__s):h.__s,R.getDerivedStateFromProps(g,h.__s)),f)null==R.getDerivedStateFromProps&&null!=h.componentWillMount&&h.componentWillMount(),null!=h.componentDidMount&&s.push(h);else{if(null==R.getDerivedStateFromProps&&null==o&&null!=h.componentWillReceiveProps&&h.componentWillReceiveProps(g,b),!o&&null!=h.shouldComponentUpdate&&!1===h.shouldComponentUpdate(g,h.__s,b)){for(h.props=g,h.state=h.__s,h.__d=!1,(h.__v=t).__e=null!=c?c!==n.__e?c:n.__e:null,t.__k=n.__k,l=0;l<t.__k.length;l++)t.__k[l]&&(t.__k[l].__p=t);break e}null!=h.componentWillUpdate&&h.componentWillUpdate(g,h.__s,b)}for(d=h.props,m=h.state,h.context=b,h.props=g,h.state=h.__s,(l=sn.__r)&&l(t),h.__d=!1,h.__v=t,h.__P=e,l=h.render(h.props,h.state,h.context),t.__k=Nn(null!=l&&l.type==yn&&null==l.key?l.props.children:l),null!=h.getChildContext&&(r=mn(mn({},r),h.getChildContext())),f||null==h.getSnapshotBeforeUpdate||(p=h.getSnapshotBeforeUpdate(d,m)),_n(e,t,n,r,i,a,s,c,u),h.base=t.__e;l=h.__h.pop();)h.__s&&(h.state=h.__s),l.call(h);f||null==d||null==h.componentDidUpdate||h.componentDidUpdate(d,m,p),v&&(h.__E=h.__p=null)}else t.__e=function(e,t,n,r,i,a,s,o){var c,u,l,h,f=n.props,d=t.props;if(i="svg"===t.type||i,null==e&&null!=a)for(c=0;c<a.length;c++)if(null!=(u=a[c])&&(null===t.type?3===u.nodeType:u.localName===t.type)){e=u,a[c]=null;break}if(null==e){if(null===t.type)return document.createTextNode(d);e=i?document.createElementNS("http://www.w3.org/2000/svg",t.type):document.createElement(t.type),a=null}return null===t.type?f!==d&&(null!=a&&(a[a.indexOf(e)]=null),e.data=d):t!==n&&(null!=a&&(a=fn.slice.call(e.childNodes)),l=(f=n.props||hn).dangerouslySetInnerHTML,h=d.dangerouslySetInnerHTML,o||(h||l)&&(h&&l&&h.__html==l.__html||(e.innerHTML=h&&h.__html||"")),function(e,t,n,r,i){var a;for(a in n)a in t||Fn(e,a,null,n[a],r);for(a in t)i&&"function"!=typeof t[a]||"value"===a||"checked"===a||n[a]===t[a]||Fn(e,a,t[a],n[a],r)}(e,d,f,i,o),t.__k=t.props.children,h||_n(e,t,n,r,"foreignObject"!==t.type&&i,a,s,hn,o),o||("value"in d&&void 0!==d.value&&d.value!==e.value&&(e.value=null==d.value?"":d.value),"checked"in d&&void 0!==d.checked&&d.checked!==e.checked&&(e.checked=d.checked))),e}(n.__e,t,n,r,i,a,s,u);(l=sn.diffed)&&l(t)}catch(e){sn.__e(e,t,n)}return t.__e}function Tn(e,t){for(var n;n=e.pop();)try{n.componentDidMount()}catch(e){sn.__e(e,n.__v)}sn.__c&&sn.__c(t)}function En(e,t,n){try{"function"==typeof e?e(t):e.current=t}catch(e){sn.__e(e,n)}}function kn(e,t,n){var r,i,a;if(sn.unmount&&sn.unmount(e),(r=e.ref)&&En(r,null,t),n||"function"==typeof e.type||(n=null!=(i=e.__e)),e.__e=e.l=null,null!=(r=e.__c)){if(r.componentWillUnmount)try{r.componentWillUnmount()}catch(e){sn.__e(e,t)}r.base=r.__P=null}if(r=e.__k)for(a=0;a<r.length;a++)r[a]&&kn(r[a],t,n);null!=i&&pn(i)}function Mn(e,t,n){return this.constructor(e,n)}function Ln(e,t,n){var r,i,a;sn.__p&&sn.__p(e,t),i=(r=n===ln)?null:n&&n.__k||t.__k,e=vn(yn,null,[e]),a=[],Cn(t,r?t.__k=e:(n||t).__k=e,i||hn,hn,void 0!==t.ownerSVGElement,n&&!r?[n]:i?null:fn.slice.call(t.childNodes),a,!1,n||hn,r),Tn(a,e)}sn={},bn.prototype.setState=function(e,t){var n=this.__s!==this.state&&this.__s||(this.__s=mn({},this.state));"function"==typeof e&&!(e=e(n,this.props))||mn(n,e),null!=e&&this.__v&&(this.u=!1,t&&this.__h.push(t),Sn(this))},bn.prototype.forceUpdate=function(e){this.__v&&(e&&this.__h.push(e),this.u=!0,Sn(this))},bn.prototype.render=yn,on=[],cn="function"==typeof Promise?Promise.prototype.then.bind(Promise.resolve()):setTimeout,un=sn.debounceRendering,sn.__e=function(e,t,n){for(var r;t=t.__p;)if((r=t.__c)&&!r.__p)try{if(r.constructor&&null!=r.constructor.getDerivedStateFromError)r.setState(r.constructor.getDerivedStateFromError(e));else{if(null==r.componentDidCatch)continue;r.componentDidCatch(e)}return Sn(r.__E=r)}catch(t){e=t}throw e},ln=hn;function jn(e,t,n){for(var r=e;r&&!n(r);){if(r===t)return null;r=r.parentElement}return r}function On(e){return function(o){return vn("div",{onClick:function(e){if(o.sendEvent){var t=jn(e.target,e.currentTarget,function(e){return e.hasAttribute("data-insights-event")});if(t){var n=function(e){var t=e.getAttribute("data-insights-event");if("string"!=typeof t)throw new Error("The insights middleware expects `data-insights-event` to be a base64-encoded JSON string.");try{return JSON.parse(atob(t))}catch(e){throw new Error("The insights middleware was unable to parse `data-insights-event`.")}}(t);o.sendEvent(n)}}var r=jn(e.target,e.currentTarget,function(e){return function(e){return e.hasAttribute("data-insights-method")}(e)});if(r){var i=function(e){var t=e.getAttribute("data-insights-method"),n=e.getAttribute("data-insights-payload");if("string"!=typeof n)throw new Error("The insights helper expects `data-insights-payload` to be a base64-encoded JSON string.");try{return{method:t,payload:JSON.parse(atob(n))}}catch(e){throw new Error("The insights helper was unable to parse `data-insights-payload`.")}}(r),a=i.method,s=i.payload;o.insights(a,s)}}},vn(e,o))}}function An(h,e){var a=1<arguments.length&&void 0!==e?e:_e;return Pe(h,Dn()),function(s){var e=s||{},t=e.items,n=e.transformItems,o=void 0===n?function(e){return e}:n,c=t;if(!Array.isArray(c))throw new Error(Dn("The `items` option expects an array of objects."));var r=c.filter(function(e){return!0===e.default});if(0===r.length)throw new Error(Dn("A default value must be specified in `items`."));if(1<r.length)throw new Error(Dn("More than one default value is specified in `items`."));function u(e){var t=e.hitsPerPage;return c.map(function(e){return D({},e,{isRefined:Number(e.value)===Number(t)})})}var i=r[0],l={};return{$$type:"ais.hitsPerPage",init:function(e){var t=e.helper,n=e.createURL,r=e.state,i=e.instantSearchInstance,a=c.some(function(e){return Number(r.hitsPerPage)===Number(e.value)});l.setHitsPerPage=function(e){return e||0===e?t.setQueryParameter("hitsPerPage",e).search():t.setQueryParameter("hitsPerPage",void 0).search()},a||(c=[{value:"",label:""}].concat(_(c))),l.createURLFactory=function(t){return function(e){return n(t.setQueryParameter("hitsPerPage",e||0===e?e:void 0))}},h({items:o(u(r)),refine:l.setHitsPerPage,createURL:l.createURLFactory(t.state),hasNoResults:!0,widgetParams:s,instantSearchInstance:i},!0)},render:function(e){var t=e.state,n=e.results,r=e.instantSearchInstance,i=0===n.nbHits;h({items:o(u(t)),refine:l.setHitsPerPage,createURL:l.createURLFactory(t),hasNoResults:i,widgetParams:s,instantSearchInstance:r},!1)},dispose:function(e){var t=e.state;return a(),t.setQueryParameter("hitsPerPage",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.hitsPerPage;return void 0===n||n===i.value?e:D({},e,{hitsPerPage:n})},getWidgetSearchParameters:function(e,t){var n=t.uiState;return e.setQueryParameters({hitsPerPage:n.hitsPerPage||i.value})}}}}var Hn=an(tn),Dn=Ae({name:"hits-per-page",connector:!0}),Bn=Ae({name:"infinite-hits",connector:!0});function Qn(e){var t=e||{};t.page;return A(t,["page"])}function qn(n){return Object.keys(n).map(Number).sort(function(e,t){return e-t}).reduce(function(e,t){return e.concat(n[t])},[])}function Un(P,e){var i=1<arguments.length&&void 0!==e?e:_e;return Pe(P,Bn()),function(l){function h(){return Math.min.apply(Math,_(Object.keys(S||{}).map(Number)))}function f(){return Math.max.apply(Math,_(Object.keys(S||{}).map(Number)))}function d(e){var n=0<arguments.length&&void 0!==e?e:{};return Object.keys(n).filter(function(e){return Array.isArray(n[e])?n[e].length:Object.keys(n[e]).length}).reduce(function(e,t){return e[t]=n[t],e},{})}var m,p,v,g,y,e=l||{},t=e.escapeHTML,b=void 0===t||t,n=e.transformItems,R=void 0===n?function(e){return e}:n,r=e.cache,w=void 0===r?function(){var r=null,i=void 0;return{read:function(e){var t=e.state;return Te(i,Qn(t))?r:null},write:function(e){var t=e.state,n=e.hits;i=Qn(t),r=n}}}():r,S=void 0;return{$$type:"ais.infiniteHits",init:function(e){var t=e.instantSearchInstance,n=e.helper;p=function(e){return function(){e.overrideStateWithoutTriggeringChangeEvent(D({},e.state,{page:h()-1})).searchWithoutTriggeringOnStateChange()}}(n),v=function(e){return function(){e.setPage(f()+1).search()}}(n),g=Ve({instantSearchInstance:t,index:n.getIndex(),widgetType:this.$$type}),y=We({index:n.getIndex(),widgetType:this.$$type}),P({hits:qn(w.read({state:n.state})||{}),results:void 0,sendEvent:g,bindEvent:y,showPrevious:p,showMore:v,isFirstPage:0===h()||void 0===n.state.page,isLastPage:!0,instantSearchInstance:t,widgetParams:l},!0)},render:function(e){var t=e.results,n=e.state,r=e.instantSearchInstance,i=n.page,a=void 0===i?0:i,s=(n.facets,n.hierarchicalFacets,n.disjunctiveFacets,n.maxValuesPerFacet,A(n,["page","facets","hierarchicalFacets","disjunctiveFacets","maxValuesPerFacet"]));s.facetsRefinements=d(s.facetsRefinements),s.hierarchicalFacetsRefinements=d(s.hierarchicalFacetsRefinements),s.disjunctiveFacetsRefinements=d(s.disjunctiveFacetsRefinements),s.numericRefinements=d(s.numericRefinements),Te(s,m)||(S=w.read({state:n})||{},m=s),b&&0<t.hits.length&&(t.hits=it(t.hits));var o=t.hits.__escaped;t.hits=Be(t.hits,t.page,t.hitsPerPage),t.hits=Qe(t.hits,t.queryID),t.hits=R(t.hits),t.hits.__escaped=o,void 0===S&&(S=w.read({state:n})||{}),void 0===S[a]&&(S[a]=t.hits,w.write({state:n,hits:S}));var c=0===h(),u=t.nbPages<=f()+1;g("view",S[a]),P({hits:qn(S),results:t,sendEvent:g,bindEvent:y,showPrevious:p,showMore:v,isFirstPage:c,isLastPage:u,instantSearchInstance:r,widgetParams:l},!1)},dispose:function(e){var t=e.state;i();var n=t.setQueryParameter("page",void 0);return b?n.setQueryParameters(Object.keys(et).reduce(function(e,t){return D({},e,L({},t,void 0))},{})):n},getWidgetState:function(e,t){var n=t.searchParameters.page||0;return n?D({},e,{page:n+1}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=e;b&&(r=e.setQueryParameters(et));var i=n.page?n.page-1:0;return r.setQueryParameter("page",i)}}}}var Vn=an(Un),Wn=Ae({name:"menu",connector:!0});function $n(m){var a=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(m,Wn()),function(){var s,o=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},c=o.attribute,e=o.limit,u=void 0===e?10:e,t=o.showMore,l=void 0!==t&&t,n=o.showMoreLimit,h=void 0===n?20:n,r=o.sortBy,f=void 0===r?["isRefined","name:asc"]:r,i=o.transformItems,d=void 0===i?function(e){return e}:i;if(!c)throw new Error(Wn("The `attribute` option is required."));if(!0===l&&h<=u)throw new Error(Wn("The `showMoreLimit` option must be greater than `limit`."));return{$$type:"ais.menu",isShowingMore:!1,toggleShowMore:function(){},cachedToggleShowMore:function(){this.toggleShowMore()},createToggleShowMore:function(e){var t=this,n=e.results,r=e.instantSearchInstance;return function(){t.isShowingMore=!t.isShowingMore,t.render({results:n,instantSearchInstance:r})}},getLimit:function(){return this.isShowingMore?h:u},refine:function(n){return function(e){var t=Q(n.getHierarchicalFacetBreadcrumb(c),1)[0];s("click",e||t),n.toggleRefinement(c,e||t).search()}},init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance;s=qe({instantSearchInstance:r,helper:t,attribute:c,widgetType:this.$$type}),this.cachedToggleShowMore=this.cachedToggleShowMore.bind(this),this._createURL=function(e){return n(t.state.toggleRefinement(c,e))},this._refine=this.refine(t),m({items:[],createURL:this._createURL,refine:this._refine,sendEvent:s,instantSearchInstance:r,canRefine:!1,widgetParams:o,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,canToggleShowMore:!1},!0)},render:function(e){var t=e.results,n=e.instantSearchInstance,r=t.getFacetValues(c,{sortBy:f}),i=r&&r.data?r.data:[],a=d(i.slice(0,this.getLimit()).map(function(e){var t=e.name,n=e.path;return D({},A(e,["name","path"]),{label:t,value:n})}));this.toggleShowMore=this.createToggleShowMore({results:t,instantSearchInstance:n}),m({items:a,createURL:this._createURL,refine:this._refine,sendEvent:s,instantSearchInstance:n,canRefine:0<a.length,widgetParams:o,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,canToggleShowMore:l&&(this.isShowingMore||i.length>this.getLimit())},!1)},dispose:function(e){var t=e.state;return a(),t.removeHierarchicalFacet(c).setQueryParameter("maxValuesPerFacet",void 0)},getWidgetState:function(e,t){var n=Q(t.searchParameters.getHierarchicalFacetBreadcrumb(c),1)[0];return n?D({},e,{menu:D({},e.menu,L({},c,n))}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.menu&&n.menu[c],i=e.removeHierarchicalFacet(c).addHierarchicalFacet({name:c,attributes:[c]}),a=i.maxValuesPerFacet||0,s=Math.max(a,l?h:u),o=i.setQueryParameter("maxValuesPerFacet",s);return r?o.addHierarchicalFacetRefinement(c,r):o.setQueryParameters({hierarchicalFacetsRefinements:D({},o.hierarchicalFacetsRefinements,L({},c,[]))})}}}}function zn(l,e){var h=1<arguments.length&&void 0!==e?e:_e;return Pe(l,Kn()),function(i){var e=i||{},t=e.attribute,u=void 0===t?"":t,n=e.items,r=void 0===n?[]:n,a=e.transformItems,s=void 0===a?function(e){return e}:a;if(""===u)throw new Error(Kn("The `attribute` option is required."));if(!r||0===r.length)throw new Error(Kn("The `items` option expects an array of objects."));function o(i){return r.map(function(e){var t=e.start,n=e.end,r=e.label;return{label:r,value:window.encodeURI(JSON.stringify({start:t,end:n})),isRefined:Yn(i,u,{start:t,end:n,label:r})}})}var c={};return{$$type:Jn,init:function(e){var n=e.helper,r=e.createURL,t=e.instantSearchInstance;c.sendEvent=function(e){var c=e.instantSearchInstance,u=e.helper,l=e.attribute;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];if(1!==t.length){var r=t[0],i=t[1],a=t[2],s=void 0===a?"Filter Applied":a;if("click"===r){var o=$e(Gn(u.state,l,i),l);o&&0<o.length&&c.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:Jn,eventType:r,payload:{eventName:s,index:u.getIndex(),filters:o}})}}else c.sendEventToInsights(t[0])}}({instantSearchInstance:t,helper:n,attribute:u}),c.refine=function(e){var t=Gn(n.state,u,e);c.sendEvent("click",e),n.setState(t).search()},c.createURL=function(t){return function(e){return r(Gn(t,u,e))}},l({createURL:c.createURL(n.state),items:s(o(n.state)),hasNoResults:!0,refine:c.refine,sendEvent:c.sendEvent,instantSearchInstance:t,widgetParams:i},!0)},render:function(e){var t=e.results,n=e.state,r=e.instantSearchInstance;l({createURL:c.createURL(n),items:s(o(n)),hasNoResults:0===t.nbHits,refine:c.refine,sendEvent:c.sendEvent,instantSearchInstance:r,widgetParams:i},!1)},dispose:function(e){var t=e.state;return h(),t.clearRefinements(u)},getWidgetState:function(e,t){var n=t.searchParameters.getNumericRefinements(u),r=n["="]&&n["="][0];if(r||0===r)return D({},e,{numericMenu:D({},e.numericMenu,L({},u,"".concat(n["="])))});var i=n[">="]&&n[">="][0]||"",a=n["<="]&&n["<="][0]||"";return""===i&&""===a?e:D({},e,{numericMenu:D({},e.numericMenu,L({},u,"".concat(i,":").concat(a)))})},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.numericMenu&&n.numericMenu[u],i=e.clearRefinements(u);if(!r)return i.setQueryParameters({numericRefinements:D({},i.numericRefinements,L({},u,{}))});if(-1===r.indexOf(":"))return i.addNumericRefinement(u,"=",Number(r));var a=Q(r.split(":").map(parseFloat),2),s=a[0],o=a[1],c=xe(s)?i.addNumericRefinement(u,">=",s):i;return xe(o)?c.addNumericRefinement(u,"<=",o):c}}}}var Kn=Ae({name:"numeric-menu",connector:!0}),Jn="ais.numericMenu";function Yn(e,t,n){var r=e.getNumericRefinements(t);return void 0!==n.start&&void 0!==n.end&&n.start===n.end?Xn(r,"=",n.start):void 0!==n.start?Xn(r,">=",n.start):void 0!==n.end?Xn(r,"<=",n.end):void 0===n.start&&void 0===n.end&&Object.keys(r).every(function(e){return 0===(r[e]||[]).length})}function Gn(e,t,n){var r=e,i=JSON.parse(window.decodeURI(n)),a=r.getNumericRefinements(t);if(void 0===i.start&&void 0===i.end)return r.removeNumericRefinement(t);if(Yn(r,t,i)||(r=r.removeNumericRefinement(t)),void 0!==i.start&&void 0!==i.end){if(i.start>i.end)throw new Error("option.start should be > to option.end");if(i.start===i.end)return r=Xn(a,"=",i.start)?r.removeNumericRefinement(t,"=",i.start):r.addNumericRefinement(t,"=",i.start)}return void 0!==i.start&&(r=Xn(a,">=",i.start)?r.removeNumericRefinement(t,">=",i.start):r.addNumericRefinement(t,">=",i.start)),void 0!==i.end&&(r=Xn(a,"<=",i.end)?r.removeNumericRefinement(t,"<=",i.end):r.addNumericRefinement(t,"<=",i.end)),"number"==typeof r.page&&(r.page=0),r}function Xn(e,t,n){return void 0!==e[t]&&e[t].includes(n)}var Zn=function(){function t(e){k(this,t),this.currentPage=e.currentPage,this.total=e.total,this.padding=e.padding}return M(t,[{key:"pages",value:function(){var e=this.total,t=this.currentPage,n=this.padding;if(0===e)return[0];var r=this.nbPagesDisplayed(n,e);if(r===e)return Ie({end:e});var i=this.calculatePaddingLeft(t,n,e,r);return Ie({start:t-i,end:t+(r-i)})}},{key:"nbPagesDisplayed",value:function(e,t){return Math.min(2*e+1,t)}},{key:"calculatePaddingLeft",value:function(e,t,n,r){return e<=t?e:n-t<=e?r-(n-e):t}},{key:"isLastPage",value:function(){return this.currentPage===this.total-1||0===this.total}},{key:"isFirstPage",value:function(){return 0===this.currentPage}}]),t}(),er=Ae({name:"pagination",connector:!0});function tr(c){var r=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(c,er()),function(){var s=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},n=s.totalPages,e=s.padding,o=new Zn({currentPage:0,total:0,padding:void 0===e?3:e});return{$$type:"ais.pagination",init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance;this.refine=function(e){t.setPage(e),t.search()},this.createURL=function(t){return function(e){return n(t.setPage(e))}},c({createURL:this.createURL(t.state),currentRefinement:t.state.page||0,nbHits:0,nbPages:0,pages:[],isFirstPage:!0,isLastPage:!0,refine:this.refine,widgetParams:s,instantSearchInstance:r},!0)},getMaxPage:function(e){var t=e.nbPages;return void 0!==n?Math.min(n,t):t},render:function(e){var t=e.results,n=e.state,r=e.instantSearchInstance,i=n.page||0,a=this.getMaxPage(t);o.currentPage=i,o.total=a,c({createURL:this.createURL(n),currentRefinement:i,refine:this.refine,nbHits:t.nbHits,nbPages:a,pages:o.pages(),isFirstPage:o.isFirstPage(),isLastPage:o.isLastPage(),widgetParams:s,instantSearchInstance:r},!1)},dispose:function(e){var t=e.state;return r(),t.setQueryParameter("page",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.page||0;return n?D({},e,{page:n+1}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.page?n.page-1:0;return e.setQueryParameter("page",r)}}}}var nr=Ae({name:"range-input",connector:!0},{name:"range-slider",connector:!0}),rr="ais.range";function ir(f){var r=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(f,nr()),function(){var c=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},S=c.attribute,P=c.min,_=c.max,e=c.precision,u=void 0===e?0:e,N=xe(P),x=xe(_);if(!S)throw new Error(nr("The `attribute` option is required."));if(N&&x&&_<P)throw new Error(nr("The `max` option can't be lower than `min`."));function F(e){return Number(Number(e).toFixed(u))}function d(e,t,n,r){var i,a,s=e.state,o=t.min,c=t.max,u=Q(s.getNumericRefinement(S,">=")||[],1)[0],l=Q(s.getNumericRefinement(S,"<=")||[],1)[0],h=void 0===n||""===n,f=void 0===r||""===r,d=h?void 0:parseFloat(n),m=f?void 0:parseFloat(r);a=x||c!==m?x&&f?_:m:void 0;var p=void 0===(i=N||o!==d?N&&h?P:d:void 0),v=xe(i),g=xe(o),y=p||v&&(!g||g&&o<=i),b=void 0===a,R=xe(a),w=xe(c);return(u!==i||l!==a)&&y&&(b||R&&(!w||w&&a<=c))?(s=s.removeNumericRefinement(S),v&&(s=s.addNumericRefinement(S,">=",F(i))),R&&(s=s.addNumericRefinement(S,"<=",F(a))),s):null}function m(e,t,n,r){var i=3<arguments.length&&void 0!==r?r:"Filter Applied",a=$e(e,S);a&&0<a.length&&t.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:rr,eventType:"click",payload:{eventName:i,index:n.getIndex(),filters:a}})}function l(l,h,f){return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];if(1!==t.length){var r=t[0],i=t[1],a=t[2];if("click"===r){var s=Q(i,2),o=s[0],c=s[1],u=d(h,f,o,c);m(u,l,h,a)}}else l.sendEventToInsights(t[0])}}var h={from:function(e){return e},to:function(e){return F(e).toLocaleString()}};return{$$type:rr,_getCurrentRange:function(e){var t,n,r=Math.pow(10,u);return t=N?P:xe(e.min)?e.min:0,n=x?_:xe(e.max)?e.max:0,{min:Math.floor(t*r)/r,max:Math.ceil(n*r)/r}},_getCurrentRefinement:function(e){var t=Q(e.getNumericRefinement(S,">=")||[],1)[0],n=Q(e.getNumericRefinement(S,"<=")||[],1)[0];return[xe(t)?t:-1/0,xe(n)?n:1/0]},_refine:function(i,a,s){return function(){var e=Q(0<arguments.length&&void 0!==arguments[0]?arguments[0]:[],2),t=e[0],n=e[1],r=d(a,s,t,n);r&&(m(r,i,a),a.setState(r).search())}},init:function(e){var t=e.helper,n=e.instantSearchInstance,r=this._getCurrentRange({}),i=this._getCurrentRefinement(t);f({refine:this._refine(n,t,{}),sendEvent:l(n,t,{}),format:h,range:r,widgetParams:D({},c,{precision:u}),start:i,instantSearchInstance:n},!0)},render:function(e){var t=e.results,n=e.helper,r=e.instantSearchInstance,i=ge(t.disjunctiveFacets||[],function(e){return e.name===S}),a=i&&i.stats||{},s=this._getCurrentRange(a),o=this._getCurrentRefinement(n);f({refine:this._refine(r,n,s),sendEvent:l(r,n,s),format:h,range:s,widgetParams:D({},c,{precision:u}),start:o,instantSearchInstance:r},!1)},dispose:function(e){var t=e.state;r();var n=t.removeDisjunctiveFacet(S);return n.numericRefinements=D({},t.numericRefinements,L({},S,void 0)),n},getWidgetState:function(e,t){var n=t.searchParameters.getNumericRefinements(S),r=n[">="],i=void 0===r?[]:r,a=n["<="],s=void 0===a?[]:a;return 0===i.length&&0===s.length?e:D({},e,{range:D({},e.range,L({},S,"".concat(i,":").concat(s)))})},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=e.addDisjunctiveFacet(S).setQueryParameters({numericRefinements:D({},e.numericRefinements,L({},S,{}))});N&&(r=r.addNumericRefinement(S,">=",P)),x&&(r=r.addNumericRefinement(S,"<=",_));var i=n.range&&n.range[S];if(!i||-1===i.indexOf(":"))return r;var a=Q(i.split(":").map(parseFloat),2),s=a[0],o=a[1];return xe(s)&&(r=r.addNumericRefinement(S,">=",s)),xe(o)&&(r=r.addNumericRefinement(S,"<=",o)),r}}}}var ar=Ae({name:"refinement-list",connector:!0});function sr(x){var c=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(x,ar()),function(){var d=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},m=d.attribute,e=d.operator,h=void 0===e?"or":e,t=d.limit,p=void 0===t?10:t,n=d.showMore,v=void 0!==n&&n,r=d.showMoreLimit,f=void 0===r?20:r,i=d.sortBy,u=void 0===i?["isRefined","count:desc","name:asc"]:i,a=d.escapeFacetValues,l=void 0===a||a,s=d.transformItems,g=void 0===s?function(e){return e}:s;if(!m)throw new Error(ar("The `attribute` option is required."));if(!/^(and|or)$/.test(h))throw new Error(ar('The `operator` must one of: `"and"`, `"or"` (got "'.concat(h,'").')));if(!0===v&&f<=p)throw new Error(ar("`showMoreLimit` should be greater than `limit`."));function y(e){var t=e.name;return D({},A(e,["name"]),{label:t,value:t,highlighted:t})}function b(e){return e?f:p}function R(e){var t=e.items,n=e.state,r=e.createURL,i=e.helperSpecializedSearchFacetValues,a=e.refine,s=e.isFromSearch,o=e.isFirstSearch,c=e.isShowingMore,u=e.toggleShowMore,l=e.instantSearchInstance,h=i&&i(n,r,i,a,l,c),f=c&&_.length>p||v&&!s&&!N;x({createURL:function(e){return r(n.toggleRefinement(m,e))},items:t,refine:a,searchForItems:h,instantSearchInstance:l,isFromSearch:s,canRefine:s||0<t.length,widgetParams:d,isShowingMore:c,canToggleShowMore:f,toggleShowMore:u,hasExhaustiveItems:N},o)}function o(n,u){return function(r,i,a,s,o,c){return function(e){if(""===e&&_)R({items:_,state:r,createURL:i,helperSpecializedSearchFacetValues:a,refine:s,isFromSearch:!1,isFirstSearch:!1,instantSearchInstance:o,toggleShowMore:u,isShowingMore:c});else{var t={highlightPreTag:l?et.highlightPreTag:tt.highlightPreTag,highlightPostTag:l?et.highlightPostTag:tt.highlightPostTag};n.searchForFacetValues(m,e,Math.min(b(c),100),t).then(function(e){var t=l?function(e){return e.map(function(e){return D({},e,{highlighted:nt(e.highlighted)})})}(e.facetHits):e.facetHits,n=g(t.map(function(e){var t=e.value;return D({},A(e,["value"]),{value:t,label:t})}));R({items:n,state:r,createURL:i,helperSpecializedSearchFacetValues:a,refine:s,isFromSearch:!0,isFirstSearch:!1,instantSearchInstance:o,isShowingMore:c})})}}}}var w,S,P,_=[],N=!0;return{$$type:"ais.refinementList",isShowingMore:!1,toggleShowMore:function(){},cachedToggleShowMore:function(){this.toggleShowMore()},createToggleShowMore:function(e){var t=this;return function(){t.isShowingMore=!t.isShowingMore,t.render(e)}},getLimit:function(){return b(this.isShowingMore)},init:function(e){var t=e.helper,n=e.createURL,r=e.instantSearchInstance;this.cachedToggleShowMore=this.cachedToggleShowMore.bind(this),P=qe({instantSearchInstance:r,helper:t,attribute:m,widgetType:this.$$type}),S=function(e){P("click",e),t.toggleRefinement(m,e).search()},w=o(t,this.cachedToggleShowMore),R({items:[],state:t.state,createURL:n,helperSpecializedSearchFacetValues:w,refine:S,isFromSearch:!1,isFirstSearch:!0,instantSearchInstance:r,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,sendEvent:P})},render:function(e){var t=e.results,n=e.state,r=e.createURL,i=e.instantSearchInstance,a=t.getFacetValues(m,{sortBy:u})||[],s=g(a.slice(0,this.getLimit()).map(y)),o=n.maxValuesPerFacet,c=this.getLimit();N=c<o?a.length<=c:a.length<c,_=s,this.toggleShowMore=this.createToggleShowMore(e),R({items:s,state:n,createURL:r,helperSpecializedSearchFacetValues:w,refine:S,isFromSearch:!1,isFirstSearch:!1,instantSearchInstance:i,isShowingMore:this.isShowingMore,toggleShowMore:this.cachedToggleShowMore,sendEvent:P})},dispose:function(e){var t=e.state;c();var n=t.setQueryParameter("maxValuesPerFacet",void 0);return"and"===h?n.removeFacet(m):n.removeDisjunctiveFacet(m)},getWidgetState:function(e,t){var n=t.searchParameters,r="or"===h?n.getDisjunctiveRefinements(m):n.getConjunctiveRefinements(m);return r.length?D({},e,{refinementList:D({},e.refinementList,L({},m,r))}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r="or"===h,i=n.refinementList&&n.refinementList[m],a=e.clearRefinements(m),s=r?a.addDisjunctiveFacet(m):a.addFacet(m),o=s.maxValuesPerFacet||0,c=Math.max(o,v?f:p),u=s.setQueryParameter("maxValuesPerFacet",c);if(i)return i.reduce(function(e,t){return r?e.addDisjunctiveFacetRefinement(m,t):e.addFacetRefinement(m,t)},u);var l=r?"disjunctiveFacetsRefinements":"facetsRefinements";return u.setQueryParameters(L({},l,D({},u[l],L({},m,[]))))}}}}var or=Ae({name:"search-box",connector:!0});function cr(o){var n=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(o,or()),function(){var i=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},a=i.queryHook;function s(e){return function(){e.setQuery(""),e.search()}}return{$$type:"ais.searchBox",_clear:function(){},_cachedClear:function(){this._clear()},init:function(e){var t=e.helper,n=e.instantSearchInstance;this._cachedClear=this._cachedClear.bind(this),this._clear=s(t);function r(e){e!==t.state.query&&t.setQuery(e).search()}this._refine=function(e){a?a(e,r):r(e)},o({query:t.state.query||"",refine:this._refine,clear:this._cachedClear,widgetParams:i,instantSearchInstance:n},!0)},render:function(e){var t=e.helper,n=e.instantSearchInstance,r=e.searchMetadata;this._clear=s(t),o({query:t.state.query||"",refine:this._refine,clear:this._cachedClear,widgetParams:i,instantSearchInstance:n,isSearchStalled:r.isSearchStalled},!1)},dispose:function(e){var t=e.state;return n(),t.setQueryParameter("query",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.query||"";return""===n||e&&e.query===n?e:D({},e,{query:n})},getWidgetSearchParameters:function(e,t){var n=t.uiState;return e.setQueryParameter("query",n.query||"")}}}}var ur=Ae({name:"sort-by",connector:!0});function lr(c){var n=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(c,ur()),function(){var a=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},s=a.items,e=a.transformItems,o=void 0===e?function(e){return e}:e;if(!Array.isArray(s))throw new Error(ur("The `items` option expects an array of objects."));return{$$type:"ais.sortBy",init:function(e){var t=e.helper,n=e.instantSearchInstance,r=e.parent,i=t.state.index;ge(s,function(e){return e.value===i});this.initialIndex=r.getIndexName(),this.setIndex=function(e){t.setIndex(e).search()},c({currentRefinement:i,options:o(s),refine:this.setIndex,hasNoResults:!0,widgetParams:a,instantSearchInstance:n},!0)},render:function(e){var t=e.helper,n=e.results,r=e.instantSearchInstance;c({currentRefinement:t.state.index,options:o(s),refine:this.setIndex,hasNoResults:0===n.nbHits,widgetParams:a,instantSearchInstance:r},!1)},dispose:function(e){var t=e.state;return n(),t.setIndex(this.initialIndex)},getWidgetState:function(e,t){var n=t.searchParameters.index;return n===this.initialIndex?e:D({},e,{sortBy:n})},getWidgetSearchParameters:function(e,t){var n=t.uiState;return e.setQueryParameter("index",n.sortBy||this.initialIndex||e.index)}}}}var hr=Ae({name:"rating-menu",connector:!0}),fr="ais.ratingMenu",dr=function(e){var o=e.instantSearchInstance,c=e.helper,u=e.getRefinedStar,l=e.attribute;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];if(1!==t.length){var r=t[0],i=t[1],a=t[2],s=void 0===a?"Filter Applied":a;if("click"===r)u()===Number(i)||o.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:fr,eventType:r,payload:{eventName:s,index:c.getIndex(),filters:["".concat(l,">=").concat(i)]}})}else o.sendEventToInsights(t[0])}};function mr(g){var n=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(g,hr()),function(){var d,m=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},p=m.attribute,e=m.max,v=void 0===e?5:e;if(!p)throw new Error(hr("The `attribute` option is required."));return{$$type:fr,init:function(e){var t=this,n=e.helper,r=e.createURL,i=e.instantSearchInstance;this._toggleRefinement=this._toggleRefinement.bind(this,n),this._createURL=function(t){return function(e){return r(t.toggleRefinement(p,e))}},d=dr({instantSearchInstance:i,helper:n,getRefinedStar:function(){return t._getRefinedStar(n.state)},attribute:p}),g({instantSearchInstance:i,items:[],hasNoResults:!0,refine:this._toggleRefinement,sendEvent:d,createURL:this._createURL(n.state),widgetParams:m},!0)},render:function(e){for(var t=e.helper,n=e.results,r=e.state,i=e.instantSearchInstance,a=[],s={},o=v;0<=o;--o)s[o]=0;(n.getFacetValues(p)||[]).forEach(function(e){var t=Math.round(e.name);if(t&&!(v<t))for(var n=t;1<=n;--n)s[n]+=e.count});for(var c=this._getRefinedStar(t.state),u=v-1;1<=u;--u){var l=s[u];if(!c||u===c||0!==l){for(var h=[],f=1;f<=v;++f)h.push(f<=u);a.push({stars:h,name:String(u),value:String(u),count:l,isRefined:c===u})}}g({instantSearchInstance:i,items:a,hasNoResults:0===n.nbHits,refine:this._toggleRefinement,sendEvent:d,createURL:this._createURL(r),widgetParams:m},!1)},dispose:function(e){var t=e.state;return n(),t.removeDisjunctiveFacet(p)},getWidgetState:function(e,t){var n=t.searchParameters,r=this._getRefinedStar(n);return"number"!=typeof r?e:D({},e,{ratingMenu:D({},e.ratingMenu,L({},p,r))})},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=n.ratingMenu&&n.ratingMenu[p],i=e.clearRefinements(p).addDisjunctiveFacet(p);return r?Ie({start:Number(r),end:v+1}).reduce(function(e,t){return e.addDisjunctiveFacetRefinement(p,t)},i):i.setQueryParameters({disjunctiveFacetsRefinements:D({},i.disjunctiveFacetsRefinements,L({},p,[]))})},_toggleRefinement:function(e,t){d("click",t);var n=this._getRefinedStar(e.state)===Number(t);if(e.removeDisjunctiveFacetRefinement(p),!n)for(var r=Number(t);r<=v;++r)e.addDisjunctiveFacetRefinement(p,r);e.search()},_getRefinedStar:function(e){var t=e.getDisjunctiveRefinements(p);if(t.length)return Math.min.apply(Math,_(t.map(Number)))}}}}var pr=Ae({name:"stats",connector:!0});function vr(i){var e=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(i,pr()),function(){var r=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{};return{$$type:"ais.stats",init:function(e){var t=e.helper,n=e.instantSearchInstance;i({instantSearchInstance:n,hitsPerPage:t.state.hitsPerPage,nbHits:0,nbPages:0,page:t.state.page||0,processingTimeMS:-1,query:t.state.query||"",widgetParams:r},!0)},render:function(e){var t=e.results,n=e.instantSearchInstance;i({instantSearchInstance:n,hitsPerPage:t.hitsPerPage,nbHits:t.nbHits,nbPages:t.nbPages,page:t.page,processingTimeMS:t.processingTimeMS,query:t.query,widgetParams:r},!1)},dispose:function(){e()}}}}var gr=Ae({name:"toggle-refinement",connector:!0}),yr="ais.toggleRefinement",br=function(e){var o=e.instantSearchInstance,c=e.attribute,u=e.on,l=e.helper;return function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];if(1!==t.length){var r=t[0],i=t[1],a=t[2],s=void 0===a?"Filter Applied":a;"click"===r&&void 0!==u&&(i||o.sendEventToInsights({insightsMethod:"clickedFilters",widgetType:yr,eventType:r,payload:{eventName:s,index:l.getIndex(),filters:u.map(function(e){return"".concat(c,":").concat(JSON.stringify(e))})}}))}else o.sendEventToInsights(t[0])}};function Rr(b){var r=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;return Pe(b,gr()),function(){var d=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},m=d.attribute,e=d.on,t=void 0===e||e,n=d.off;if(!m)throw new Error(gr("The `attribute` option is required."));var p,v=void 0!==n,g=void 0!==t?Oe(t).map(Se):void 0,y=v?Oe(n).map(Se):void 0;return{$$type:yr,_toggleRefinement:function(t,e){var n=(1<arguments.length&&void 0!==e?e:{}).isRefined;n?(g.forEach(function(e){return t.removeDisjunctiveFacetRefinement(m,e)}),v&&y.forEach(function(e){return t.addDisjunctiveFacetRefinement(m,e)})):(p("click",n),v&&y.forEach(function(e){return t.removeDisjunctiveFacetRefinement(m,e)}),g.forEach(function(e){return t.addDisjunctiveFacetRefinement(m,e)})),t.search()},init:function(e){var t=this,r=e.state,n=e.helper,i=e.createURL,a=e.instantSearchInstance;p=br({instantSearchInstance:a,attribute:m,on:g,helper:n}),this._createURL=function(n){return function(){var e=n?g:y;e&&e.forEach(function(e){r.removeDisjunctiveFacetRefinement(m,e)});var t=n?y:g;return t&&t.forEach(function(e){r.addDisjunctiveFacetRefinement(m,e)}),i(r)}},this.toggleRefinement=function(e){t._toggleRefinement(n,e)};var s=g&&g.every(function(e){return r.isDisjunctiveFacetRefined(m,e)});if(v&&!s){var o=n.state.page;y&&y.forEach(function(e){return n.addDisjunctiveFacetRefinement(m,e)}),n.setPage(o)}var c={name:m,isRefined:s,count:null,onFacetValue:{isRefined:s,count:0},offFacetValue:{isRefined:v&&!s,count:0}};b({value:c,createURL:this._createURL(c.isRefined),refine:this.toggleRefinement,sendEvent:p,instantSearchInstance:a,widgetParams:d},!0)},render:function(e){var t=e.helper,n=e.results,r=e.state,i=e.instantSearchInstance,a=g&&g.every(function(e){return t.state.isDisjunctiveFacetRefined(m,e)}),s=Oe(void 0!==y&&y),o=n.getFacetValues(m)||[],c=g&&g.map(function(t){return ge(o,function(e){return e.name===ye(t)})}).filter(function(e){return void 0!==e}),u={isRefined:0<c.length&&c.every(function(e){return e.isRefined}),count:0===c.length?null:c.reduce(function(e,t){return e+t.count},0)},l=v?s.map(function(t){return ge(o,function(e){return e.name===ye(t)})}).filter(function(e){return void 0!==e}):[],h={isRefined:0<l.length&&l.every(function(e){return e.isRefined}),count:0===l.length?o.reduce(function(e,t){return e+t.count},0):l.reduce(function(e,t){return e+t.count},0)},f={name:m,isRefined:a,count:(a?h:u).count,onFacetValue:u,offFacetValue:h};b({value:f,state:r,createURL:this._createURL(f.isRefined),refine:this.toggleRefinement,sendEvent:p,helper:t,instantSearchInstance:i,widgetParams:d},!1)},dispose:function(e){var t=e.state;return r(),t.removeDisjunctiveFacet(m)},getWidgetState:function(e,t){var n=t.searchParameters,r=g&&g.every(function(e){return n.isDisjunctiveFacetRefined(m,e)});return r?D({},e,{toggle:D({},e.toggle,L({},m,r))}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState,r=e.clearRefinements(m).addDisjunctiveFacet(m);return Boolean(n.toggle&&n.toggle[m])?(g&&g.forEach(function(e){r=r.addDisjunctiveFacetRefinement(m,e)}),r):v?(y&&y.forEach(function(e){r=r.addDisjunctiveFacetRefinement(m,e)}),r):r.setQueryParameters({disjunctiveFacetsRefinements:D({},e.disjunctiveFacetsRefinements,L({},m,[]))})}}}}function wr(l,e){var h=1<arguments.length&&void 0!==e?e:_e;Pe(l,Sr());var f={};return function(o){var e=o||{},t=e.attributes,n=e.separator,r=void 0===n?" > ":n,i=e.rootPath,a=void 0===i?null:i,s=e.transformItems,c=void 0===s?function(e){return e}:s;if(!t||!Array.isArray(t)||0===t.length)throw new Error(Sr("The `attributes` option expects an array of strings."));var u=Q(t,1)[0];return{$$type:"ais.breadcrumb",init:function(e){var n=e.createURL,r=e.helper,t=e.instantSearchInstance;f.createURL=function(e){if(!e){var t=r.getHierarchicalFacetBreadcrumb(u);if(0<t.length)return n(r.state.toggleFacetRefinement(u,t[0]))}return n(r.state.toggleFacetRefinement(u,e))},f.refine=function(e){if(e)r.toggleRefinement(u,e).search();else{var t=r.getHierarchicalFacetBreadcrumb(u);0<t.length&&r.toggleRefinement(u,t[0]).search()}},l({createURL:f.createURL,canRefine:!1,instantSearchInstance:t,items:[],refine:f.refine,widgetParams:o},!0)},render:function(e){var t=e.instantSearchInstance,n=e.results,r=Q(e.state.hierarchicalFacets,1)[0].name,i=n.getFacetValues(r,{}),a=Array.isArray(i.data)?i.data:[],s=c(function(n){return n.map(function(e,t){return{label:e.label,value:t+1===n.length?null:n[t+1].value}})}(function n(e){return e.reduce(function(e,t){return t.isRefined&&(e.push({label:t.name,value:t.path}),Array.isArray(t.data)&&(e=e.concat(n(t.data)))),e},[])}(a)));l({canRefine:0<s.length,createURL:f.createURL,instantSearchInstance:t,items:s,refine:f.refine,widgetParams:o},!1)},dispose:function(){h()},getWidgetSearchParameters:function(e){if(e.isHierarchicalFacet(u)){e.getHierarchicalFacetByName(u);return e}return e.addHierarchicalFacet({name:u,attributes:t,separator:r,rootPath:a})}}}}var Sr=Ae({name:"breadcrumb",connector:!0});function Pr(_,e){var r=1<arguments.length&&void 0!==e?e:_e;return Pe(_,_r()),function(){function u(e){return e.aroundLatLng&&function(e){var t=e.match(He);if(!t)throw new Error('Invalid value for "aroundLatLng" parameter: "'.concat(e,'"'));return{lat:parseFloat(t[1]),lng:parseFloat(t[2])}}(e.aroundLatLng)}function l(e){return e.insideBoundingBox&&De(e.insideBoundingBox)}function h(i){return function(e){var t=e.northEast,n=e.southWest,r=[t.lat,t.lng,n.lat,n.lng].join();i.setQueryParameter("insideBoundingBox",r).search(),P.hasMapMoveSinceLastRefine=!1,P.lastRefineBoundingBox=r}}function f(e){return function(){e.setQueryParameter("insideBoundingBox",void 0).search()}}function d(e){return function(){return Boolean(e.insideBoundingBox)}}function m(){return P.internalToggleRefineOnMapMove()}function p(e,t){return function(){P.isRefineOnMapMove=!P.isRefineOnMapMove,e(t)}}function v(){return P.isRefineOnMapMove}function g(){return P.internalSetMapMoveSinceLastRefine()}function y(t,n){return function(){var e=!0!==P.hasMapMoveSinceLastRefine;P.hasMapMoveSinceLastRefine=!0,e&&t(n)}}function b(){return P.hasMapMoveSinceLastRefine}var R,w=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},e=w.enableRefineOnMapMove,t=void 0===e||e,n=w.transformItems,S=void 0===n?function(e){return e}:n,P={isRefineOnMapMove:t,hasMapMoveSinceLastRefine:!1,lastRefinePosition:"",lastRefineBoundingBox:"",internalToggleRefineOnMapMove:_e,internalSetMapMoveSinceLastRefine:_e};return{$$type:Nr,init:function(e){var t=e.state,n=e.helper,r=e.instantSearchInstance;R=Ve({instantSearchInstance:r,index:n.getIndex(),widgetType:Nr}),P.internalToggleRefineOnMapMove=p(_e,e),P.internalSetMapMoveSinceLastRefine=y(_e,e),_({items:[],position:u(t),currentRefinement:l(t),refine:h(n),sendEvent:R,clearMapRefinement:f(n),isRefinedWithMap:d(t),toggleRefineOnMapMove:m,isRefineOnMapMove:v,setMapMoveSinceLastRefine:g,hasMapMoveSinceLastRefine:b,widgetParams:w,instantSearchInstance:r},!0)},render:function e(t){var n=t.results,r=t.helper,i=t.instantSearchInstance,a=r.state,s=Boolean(a.aroundLatLng)&&Boolean(P.lastRefinePosition)&&a.aroundLatLng!==P.lastRefinePosition,o=!a.insideBoundingBox&&Boolean(P.lastRefineBoundingBox)&&a.insideBoundingBox!==P.lastRefineBoundingBox;(s||o)&&(P.hasMapMoveSinceLastRefine=!1),P.lastRefinePosition=a.aroundLatLng||"",P.lastRefineBoundingBox=a.insideBoundingBox||"",P.internalToggleRefineOnMapMove=p(e,t),P.internalSetMapMoveSinceLastRefine=y(e,t);var c=S(n.hits.filter(function(e){return e._geoloc}));R("view",c),_({items:c,position:u(a),currentRefinement:l(a),refine:h(r),sendEvent:R,clearMapRefinement:f(r),isRefinedWithMap:d(a),toggleRefineOnMapMove:m,isRefineOnMapMove:v,setMapMoveSinceLastRefine:g,hasMapMoveSinceLastRefine:b,widgetParams:w,instantSearchInstance:i},!1)},dispose:function(e){var t=e.state;return r(),t.setQueryParameter("insideBoundingBox",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.insideBoundingBox;return!n||e&&e.geoSearch&&e.geoSearch.boundingBox===n?e:D({},e,{geoSearch:{boundingBox:n}})},getWidgetSearchParameters:function(e,t){var n=t.uiState;return n&&n.geoSearch?e.setQueryParameter("insideBoundingBox",n.geoSearch.boundingBox):e.setQueryParameter("insideBoundingBox",void 0)}}}}var _r=Ae({name:"geo-search",connector:!0}),Nr="ais.geoSearch",xr=Ae({name:"powered-by",connector:!0});function Fr(r){var i=1<arguments.length&&void 0!==arguments[1]?arguments[1]:_e;Pe(r,xr());var a="https://www.algolia.com/?utm_source=instantsearch.js&utm_medium=website&"+"utm_content=".concat("undefined"!=typeof window&&window.location?window.location.hostname:"","&")+"utm_campaign=poweredby";return function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.url,n=void 0===t?a:t;return{$$type:"ais.poweredBy",init:function(){r({url:n,widgetParams:e},!0)},render:function(){r({url:n,widgetParams:e},!1)},dispose:function(){i()}}}}var Ir=Ae({name:"configure",connector:!0});function Cr(e,t){return e.setQueryParameters(Object.keys(t.searchParameters).reduce(function(e,t){return D({},e,L({},t,void 0))},{}))}function Tr(e,t){var a=0<arguments.length&&void 0!==e?e:_e,n=1<arguments.length&&void 0!==t?t:_e;return function(i){if(!i||!Fe(i.searchParameters))throw new Error(Ir("The `searchParameters` option expects an object."));var r={};return{$$type:"ais.configure",init:function(e){var t=e.instantSearchInstance,n=e.helper;r.refine=function(r){return function(e){var t=Cr(r.state,i),n=je(t,new ae.SearchParameters(e));r.setState(n).search(),i.searchParameters=e}}(n),a({refine:r.refine,instantSearchInstance:t,widgetParams:i},!0)},render:function(e){var t=e.instantSearchInstance;a({refine:r.refine,instantSearchInstance:t,widgetParams:i},!1)},dispose:function(e){var t=e.state;return n(),Cr(t,i)},getWidgetSearchParameters:function(e,t){var n=t.uiState;return je(e,new ae.SearchParameters(D({},n.configure,{},i.searchParameters)))},getWidgetState:function(e){return D({},e,{configure:D({},e.configure,{},i.searchParameters)})}}}}var Er=Ae({name:"configure-related-items",connector:!0});function kr(e){var t=e.attributeName,n=e.attributeValue,r=e.attributeScore;return"".concat(t,":").concat(n,"<score=").concat(r||1,">")}function Mr(c,u){return function(e){var t=e||{},a=t.hit,s=t.matchingPatterns,n=t.transformSearchParameters,r=void 0===n?function(e){return e}:n;if(!a)throw new Error(Er("The `hit` option is required."));if(!s)throw new Error(Er("The `matchingPatterns` option is required."));var i=Object.keys(s).reduce(function(e,t){var n=s[t],r=Ne(a,t),i=n.score;return Array.isArray(r)?[].concat(_(e),[r.map(function(e){return kr({attributeName:t,attributeValue:e,attributeScore:i})})]):"string"==typeof r?[].concat(_(e),[kr({attributeName:t,attributeValue:r,attributeScore:i})]):e},[]),o=D({},r(new ae.SearchParameters({sumOrFiltersScores:!0,facetFilters:["objectID:-".concat(a.objectID)],optionalFilters:i})));return D({},Tr(c,u)({searchParameters:o}),{$$type:"ais.configureRelatedItems"})}}var Lr=Ae({name:"autocomplete",connector:!0}),jr=Ae({name:"query-rules",connector:!0});function Or(e){var t=this.helper,n=this.initialRuleContexts,r=this.trackedFilters,i=this.transformRuleContexts,a=e.state,s=a.ruleContexts||[],o=function(e){var i=e.helper,a=e.sharedHelperState,s=e.trackedFilters;return Object.keys(s).reduce(function(e,t){var n=Re(i.lastResults||{},a).filter(function(e){return e.attribute===t}).map(function(e){return e.numericValue||e.name}),r=(0,s[t])(n);return[].concat(_(e),_(n.filter(function(e){return r.includes(e)}).map(function(e){return function(e){return e.replace(/[^a-z0-9-_]+/gi,"_")}("ais-".concat(t,"-").concat(e))})))},[])}({helper:t,sharedHelperState:a,trackedFilters:r}),c=i([].concat(_(n),_(o))).slice(0,10);Te(s,c)||t.overrideStateWithoutTriggeringChangeEvent(D({},a,{ruleContexts:c}))}function Ar(h,e){var f=1<arguments.length&&void 0!==e?e:_e;return Pe(h,jr()),function(a){var e=a||{},t=e.trackedFilters,i=void 0===t?{}:t,n=e.transformRuleContexts,s=void 0===n?function(e){return e}:n,r=e.transformItems,o=void 0===r?function(e){return e}:r;Object.keys(i).forEach(function(e){if("function"!=typeof i[e])throw new Error(jr("'The \"".concat(e,'" filter value in the `trackedFilters` option expects a function.')))});var c,u=0<Object.keys(i).length,l=[];return{$$type:"ais.queryRules",init:function(e){var t=e.helper,n=e.state,r=e.instantSearchInstance;l=n.ruleContexts||[],c=Or.bind({helper:t,initialRuleContexts:l,trackedFilters:i,transformRuleContexts:s}),u&&((function(e){return[e.disjunctiveFacetsRefinements,e.facetsRefinements,e.hierarchicalFacetsRefinements,e.numericRefinements].some(function(e){return Boolean(e&&0<Object.keys(e).length)})}(n)||Boolean(a.transformRuleContexts))&&c({state:n}),t.on("change",c)),h({items:[],instantSearchInstance:r,widgetParams:a},!0)},render:function(e){var t=e.results,n=e.instantSearchInstance,r=t.userData,i=o(void 0===r?[]:r);h({items:i,instantSearchInstance:n,widgetParams:a},!1)},dispose:function(e){var t=e.helper,n=e.state;return f(),u?(t.removeListener("change",c),n.setQueryParameter("ruleContexts",l)):n}}}}function Hr(e){function t(e){return{status:e,transcript:"",isSpeechFinal:!1,errorCode:void 0}}function n(e){p=D({},p,{},0<arguments.length&&void 0!==e?e:{}),d()}function r(e){n(t(0<arguments.length&&void 0!==e?e:"initial"))}function i(){n({status:"waiting"})}function a(e){n({status:"error",errorCode:e.error})}function s(e){n({status:"recognizing",transcript:e.results[0]&&e.results[0][0]&&e.results[0][0].transcript||"",isSpeechFinal:e.results[0]&&e.results[0].isFinal}),l&&p.transcript&&f(p.transcript)}function o(){p.errorCode||!p.transcript||l||f(p.transcript),"error"!==p.status&&n({status:"finished"})}function c(){u&&(u.stop(),u.removeEventListener("start",i),u.removeEventListener("error",a),u.removeEventListener("result",s),u.removeEventListener("end",o),u=void 0)}var u,l=e.searchAsYouSpeak,h=e.language,f=e.onQueryChange,d=e.onStateChange,m=window.webkitSpeechRecognition||window.SpeechRecognition,p=t("initial");return{getState:function(){return p},isBrowserSupported:function(){return Boolean(m)},isListening:function(){return"askingPermission"===p.status||"waiting"===p.status||"recognizing"===p.status},startListening:function(){(u=new m)&&(r("askingPermission"),u.interimResults=!0,h&&(u.lang=h),u.addEventListener("start",i),u.addEventListener("error",a),u.addEventListener("result",s),u.addEventListener("end",o),u.start())},stopListening:function(){c(),r("finished")},dispose:c}}function Dr(l,e){var h=1<arguments.length&&void 0!==e?e:_e;return Pe(l,Br()),function(u){function i(e){var t=e.isFirstRendering,n=e.instantSearchInstance,r=e.voiceSearchHelper,i=r.isBrowserSupported,a=r.isListening,s=r.startListening,o=r.stopListening,c=r.getState;l({isBrowserSupported:i(),isListening:a(),toggleListening:function(){i()&&(a()?o():s())},voiceListeningState:c(),widgetParams:u,instantSearchInstance:n},t)}var e=u.searchAsYouSpeak,a=void 0!==e&&e,s=u.language,o=u.additionalQueryParameters,t=u.createVoiceSearchHelper,c=void 0===t?Hr:t;return{$$type:"ais.voiceSearch",init:function(e){var t=this,n=e.helper,r=e.instantSearchInstance;this._refine=function(e){if(e!==n.state.query){var t=s?[s.split("-")[0]]:void 0;n.setQueryParameter("queryLanguages",t),"function"==typeof o&&n.setState(n.state.setQueryParameters(D({ignorePlurals:!0,removeStopWords:!0,optionalWords:e},o({query:e})))),n.setQuery(e).search()}},this._voiceSearchHelper=c({searchAsYouSpeak:a,language:s,onQueryChange:function(e){return t._refine(e)},onStateChange:function(){i({isFirstRendering:!1,instantSearchInstance:r,voiceSearchHelper:t._voiceSearchHelper})}}),i({isFirstRendering:!0,instantSearchInstance:r,voiceSearchHelper:this._voiceSearchHelper})},render:function(e){var t=e.instantSearchInstance;i({isFirstRendering:!1,instantSearchInstance:t,voiceSearchHelper:this._voiceSearchHelper})},dispose:function(e){var t=e.state;this._voiceSearchHelper.dispose(),h();var n=t;if("function"==typeof o){var r=o({query:""}),i=r?Object.keys(r).reduce(function(e,t){return e[t]=void 0,e},{}):{};n=t.setQueryParameters(D({queryLanguages:void 0,ignorePlurals:void 0,removeStopWords:void 0,optionalWords:void 0},i))}return n.setQueryParameter("query",void 0)},getWidgetState:function(e,t){var n=t.searchParameters.query||"";return n?D({},e,{query:n}):e},getWidgetSearchParameters:function(e,t){var n=t.uiState;return e.setQueryParameter("query",n.query||"")}}}}var Br=Ae({name:"voice-search",connector:!0}),Qr=Object.freeze({__proto__:null,connectClearRefinements:Vt,connectCurrentRefinements:zt,connectHierarchicalMenu:en,connectHits:tn,connectHitsWithInsights:Hn,connectHitsPerPage:An,connectInfiniteHits:Un,connectInfiniteHitsWithInsights:Vn,connectMenu:$n,connectNumericMenu:zn,connectPagination:tr,connectRange:ir,connectRefinementList:sr,connectSearchBox:cr,connectSortBy:lr,connectRatingMenu:mr,connectStats:vr,connectToggleRefinement:Rr,connectBreadcrumb:wr,connectGeoSearch:Pr,connectPoweredBy:Fr,connectConfigure:Tr,EXPERIMENTAL_connectConfigureRelatedItems:Mr,connectAutocomplete:function(u,e){var r=1<arguments.length&&void 0!==e?e:_e;return Pe(u,Lr()),function(s){var e=(s||{}).escapeHTML,o=void 0===e||e,c={};return{$$type:"ais.autocomplete",init:function(e){var t=e.instantSearchInstance,n=e.helper;c.refine=function(e){n.setQuery(e).search()},u({widgetParams:s,currentRefinement:n.state.query||"",indices:[],refine:c.refine,instantSearchInstance:t},!0)},render:function(e){var n=this,t=e.helper,r=e.scopedResults,i=e.instantSearchInstance,a=r.map(function(e){e.results.hits=o?it(e.results.hits):e.results.hits;var t=Ve({instantSearchInstance:i,index:e.results.index,widgetType:n.$$type});return t("view",e.results.hits),{indexId:e.indexId,indexName:e.results.index,hits:e.results.hits,results:e.results,sendEvent:t}});u({widgetParams:s,currentRefinement:t.state.query||"",indices:a,refine:c.refine,instantSearchInstance:i},!1)},getWidgetState:function(e,t){var n=t.searchParameters.query||"";return""===n||e&&e.query===n?e:D({},e,{query:n})},getWidgetSearchParameters:function(e,t){var n={query:t.uiState.query||""};return o?e.setQueryParameters(D({},n,{},et)):e.setQueryParameters(n)},dispose:function(e){var t=e.state;r();var n=t.setQueryParameter("query",void 0);return o?n.setQueryParameters(Object.keys(et).reduce(function(e,t){return D({},e,L({},t,void 0))},{})):n}}}},connectQueryRules:Ar,connectVoiceSearch:Dr}),qr=fe(function(e){function s(){for(var e=[],t=0;t<arguments.length;t++){var n=arguments[t];if(n){var r=typeof n;if("string"==r||"number"==r)e.push(n);else if(Array.isArray(n)&&n.length){var i=s.apply(null,n);i&&e.push(i)}else if("object"==r)for(var a in n)o.call(n,a)&&n[a]&&e.push(a)}}return e.join(" ")}var o;o={}.hasOwnProperty,e.exports?(s.default=s,e.exports=s):window.classNames=s}),Ur=function(){function e(){return k(this,e),B(this,O(e).apply(this,arguments))}return j(e,bn),M(e,[{key:"shouldComponentUpdate",value:function(e){return!Te(this.props.data,e.data)||this.props.templateKey!==e.templateKey||!Te(this.props.rootProps,e.rootProps)}},{key:"render",value:function(){var e=this.props.rootTagName,t=this.props.useCustomCompileOptions[this.props.templateKey]?this.props.templatesConfig.compileOptions:{},n=ve({templates:this.props.templates,templateKey:this.props.templateKey,compileOptions:t,helpers:this.props.templatesConfig.helpers,data:this.props.data,bindEvent:this.props.bindEvent});return null===n?null:vn(e,f({},this.props.rootProps,{dangerouslySetInnerHTML:{__html:n}}))}}]),e}();Ur.defaultProps={data:{},rootTagName:"div",useCustomCompileOptions:{},templates:{},templatesConfig:{}};function Vr(e){var t=e.hasRefinements,n=e.refine,r=e.cssClasses,i=e.templateProps;return vn("div",{className:r.root},vn(Ur,f({},i,{templateKey:"resetLabel",rootTagName:"button",rootProps:{className:qr(r.button,L({},r.disabledButton,!t)),onClick:n,disabled:!t},data:{hasRefinements:t}})))}function Wr(e){var t=e.items,n=e.cssClasses;return vn("div",{className:n.root},vn("ul",{className:n.list},t.map(function(t,e){return vn("li",{key:"".concat(t.indexName,"-").concat(t.attribute,"-").concat(e),className:n.item},vn("span",{className:n.label},function(e){return e.toString().charAt(0).toUpperCase()+e.toString().slice(1)}(t.label),":"),t.refinements.map(function(e){return vn("span",{key:function(e){var t=e.attribute,n=e.value;return[t,e.type,n,e.operator].map(function(e){return e}).filter(Boolean).join(":")}(e),className:n.category},vn("span",{className:n.categoryLabel},"query"===e.attribute?vn("q",null,e.label):e.label),vn("button",{className:n.delete,onClick:function(t){return function(e){ue(e)||(e.preventDefault(),t())}}(t.refine.bind(null,e))},"✕"))}))})))}function $r(e,t){var n=e.items,r=e.widgetParams;if(!t){var i=r.container,a=r.cssClasses;Ln(vn(Wr,{cssClasses:a,items:n}),i)}}function zr(e){var t=e.className,n=e.disabled;return vn("button",{className:t,onClick:e.onClick,disabled:n},e.children)}var Kr={resetLabel:"Clear refinements"},Jr=Ae({name:"clear-refinements"}),Yr=at("ClearRefinements"),Gr=Ae({name:"current-refinements"}),Xr=at("CurrentRefinements");zr.defaultProps={disabled:!1};function Zr(e){var t=e.classNameLabel,n=e.classNameInput,r=e.checked,i=e.onToggle,a=e.children;return vn("label",{className:t},vn("input",{className:n,type:"checkbox",checked:r,onChange:i}),a)}function ei(e){var t=e.cssClasses,n=e.enableRefine,r=e.enableRefineControl,i=e.enableClearMapRefinement,a=e.isRefineOnMapMove,s=e.isRefinedWithMap,o=e.hasMapMoveSinceLastRefine,c=e.onRefineToggle,u=e.onRefineClick,l=e.onClearClick,h=e.templateProps;return n&&vn("div",null,r&&vn("div",{className:t.control},a||!o?vn(Zr,{classNameLabel:qr(t.label,L({},t.selectedLabel,a)),classNameInput:t.input,checked:a,onToggle:c},vn(Ur,f({},h,{templateKey:"toggle",rootTagName:"span"}))):vn(zr,{className:t.redo,disabled:!o,onClick:u},vn(Ur,f({},h,{templateKey:"redo",rootTagName:"span"})))),!r&&!a&&vn("div",{className:t.control},vn(zr,{className:qr(t.redo,L({},t.disabledRedo,!o)),disabled:!o,onClick:u},vn(Ur,f({},h,{templateKey:"redo",rootTagName:"span"})))),i&&s&&vn(zr,{className:t.reset,onClick:l},vn(Ur,f({},h,{templateKey:"reset",rootTagName:"span"}))))}function ti(e){var t=e.refine,n=e.mapInstance;return t({northEast:n.getBounds().getNorthEast().toJSON(),southWest:n.getBounds().getSouthWest().toJSON()})}function ni(e,t){e.isUserInteraction=!1,t(),e.isUserInteraction=!0}function ri(e,t){var n=e.items,r=e.position,i=e.currentRefinement,a=e.refine,s=e.clearMapRefinement,o=e.toggleRefineOnMapMove,c=e.isRefineOnMapMove,u=e.setMapMoveSinceLastRefine,l=e.hasMapMoveSinceLastRefine,h=e.isRefinedWithMap,f=e.widgetParams,d=e.instantSearchInstance,m=f.container,p=f.googleReference,v=f.cssClasses,g=f.templates,y=f.initialZoom,b=f.initialPosition,R=f.enableRefine,w=f.enableClearMapRefinement,S=f.enableRefineControl,P=f.mapOptions,_=f.createMarker,N=f.markerOptions,x=f.renderState;if(t){x.isUserInteraction=!0,x.isPendingRefine=!1,x.markers=[];var F=document.createElement("div");F.className=v.root,m.appendChild(F);var I=document.createElement("div");I.className=v.map,F.appendChild(I);var C=document.createElement("div");C.className=v.tree,F.appendChild(C),x.mapInstance=new p.maps.Map(I,D({mapTypeControl:!1,fullscreenControl:!1,streetViewControl:!1,clickableIcons:!1,zoomControlOptions:{position:p.maps.ControlPosition.LEFT_TOP}},P));return p.maps.event.addListenerOnce(x.mapInstance,"idle",function(){function e(){x.isUserInteraction&&R&&(u(),c()&&(x.isPendingRefine=!0))}x.mapInstance.addListener("center_changed",e),x.mapInstance.addListener("zoom_changed",e),x.mapInstance.addListener("dragstart",e),x.mapInstance.addListener("idle",function(){x.isUserInteraction&&x.isPendingRefine&&(x.isPendingRefine=!1,ti({mapInstance:x.mapInstance,refine:a}))})}),void(x.templateProps=he({templatesConfig:d.templatesConfig,templates:g}))}var T=n.map(function(e){return e.objectID}),E=Q(function(e,a){return e.reduce(function(e,t){var n=Q(e,2),r=n[0],i=n[1];return a.includes(t.__id)?[r.concat(t),i]:[r,i.concat(t)]},[[],[]])}(x.markers,T),2),k=E[0],M=E[1],L=k.map(function(e){return e.__id}),j=n.filter(function(e){return!L.includes(e.objectID)});M.forEach(function(e){return e.setMap(null)}),x.markers=k.concat(j.map(function(n){var r=_({map:x.mapInstance,item:n});return Object.keys(N.events).forEach(function(t){r.addListener(t,function(e){N.events[t]({map:x.mapInstance,event:e,item:n,marker:r})})}),r}));var O=!l(),A=i?0:null,H=!i&&Boolean(x.markers.length)?function(e,t){var n=t.reduce(function(e,t){return e.extend(t.getPosition())},new e.maps.LatLngBounds);return{northEast:n.getNorthEast().toJSON(),southWest:n.getSouthWest().toJSON()}}(p,x.markers):i;H&&O?ni(x,function(){x.mapInstance.fitBounds(new p.maps.LatLngBounds(H.southWest,H.northEast),A)}):O&&ni(x,function(){x.mapInstance.setCenter(r||b),x.mapInstance.setZoom(y)}),Ln(vn(ei,{cssClasses:v,enableRefine:R,enableRefineControl:S,enableClearMapRefinement:w,isRefineOnMapMove:c(),isRefinedWithMap:h(),hasMapMoveSinceLastRefine:l(),onRefineToggle:o,onRefineClick:function(){return ti({mapInstance:x.mapInstance,refine:a})},onClearClick:s,templateProps:x.templateProps}),m.querySelector(".".concat(v.tree)))}var ii={HTMLMarker:"<p>Your custom HTML Marker</p>",reset:"Clear the map refinement",toggle:"Search as I move the map",redo:"Redo search here"},ai=Ae({name:"geo-search"}),si=at("GeoSearch");function oi(e){var t=e.className,n=e.handleClick,r=e.facetValueToRefine,i=e.isRefined,a=e.templateProps,s=e.templateKey,o=e.templateData,c=e.subItems;return vn("li",{className:t,onClick:function(e){n({facetValueToRefine:r,isRefined:i,originalEvent:e})}},vn(Ur,f({},a,{templateKey:s,data:o})),c)}var ci=function(){function i(){var e,s;k(this,i);for(var t=arguments.length,n=new Array(t),r=0;r<t;r++)n[r]=arguments[r];return L(H(s=B(this,(e=O(i)).call.apply(e,[this].concat(n)))),"state",{query:s.props.query,focused:!1}),L(H(s),"onInput",function(e){var t=s.props,n=t.searchAsYouType,r=t.refine,i=t.onChange,a=e.target.value;n&&r(a),s.setState({query:a}),i(e)}),L(H(s),"onSubmit",function(e){var t=s.props,n=t.searchAsYouType,r=t.refine,i=t.onSubmit;return e.preventDefault(),e.stopPropagation(),s.input.blur(),n||r(s.state.query),i(e),!1}),L(H(s),"onReset",function(e){var t=s.props,n=t.refine,r=t.onReset;s.input.focus(),n(""),s.setState({query:""}),r(e)}),L(H(s),"onBlur",function(){s.setState({focused:!1})}),L(H(s),"onFocus",function(){s.setState({focused:!0})}),s}return j(i,bn),M(i,[{key:"resetInput",value:function(){this.setState({query:""})}},{key:"componentWillReceiveProps",value:function(e){this.state.focused||e.query===this.state.query||this.setState({query:e.query})}},{key:"render",value:function(){var t=this,e=this.props,n=e.cssClasses,r=e.placeholder,i=e.autofocus,a=e.showSubmit,s=e.showReset,o=e.showLoadingIndicator,c=e.templates,u=e.isSearchStalled;return vn("div",{className:n.root},vn("form",{action:"",role:"search",className:n.form,noValidate:!0,onSubmit:this.onSubmit,onReset:this.onReset},vn("input",{ref:function(e){return t.input=e},value:this.state.query,disabled:this.props.disabled,className:n.input,type:"search",placeholder:r,autoFocus:i,autoComplete:"off",autoCorrect:"off",autoCapitalize:"off",spellCheck:"false",ariaLabel:"aa-search",maxLength:512,onInput:this.onInput,onBlur:this.onBlur,onFocus:this.onFocus}),vn(Ur,{templateKey:"submit",rootTagName:"button",rootProps:{className:n.submit,type:"submit",title:"Submit the search query.",hidden:!a},templates:c,data:{cssClasses:n}}),vn(Ur,{templateKey:"reset",rootTagName:"button",rootProps:{className:n.reset,type:"reset",title:"Clear the search query.",hidden:!(s&&this.state.query.trim()&&!u)},templates:c,data:{cssClasses:n}}),o&&vn(Ur,{templateKey:"loadingIndicator",rootTagName:"span",rootProps:{className:n.loadingIndicator,hidden:!u},templates:c,data:{cssClasses:n}})))}}]),i}();L(ci,"defaultProps",{query:"",showSubmit:!0,showReset:!0,showLoadingIndicator:!0,autofocus:!1,searchAsYouType:!0,isSearchStalled:!1,disabled:!1,onChange:_e,onSubmit:_e,onReset:_e,refine:_e});var ui=function(){function c(e){var t;return k(this,c),(t=B(this,O(c).call(this,e))).handleItemClick=t.handleItemClick.bind(H(t)),t}return j(c,bn),M(c,[{key:"shouldComponentUpdate",value:function(e,t){var n=this.state!==t,r=!Te(this.props.facetValues,e.facetValues);return n||r}},{key:"refine",value:function(e,t){this.props.toggleRefinement(e,t)}},{key:"_generateFacetItem",value:function(e){var t,n,r=e.data&&0<e.data.length;if(r){var i=this.props.cssClasses,a=(i.root,A(i,["root"]));n=vn(c,f({},this.props,{cssClasses:a,depth:this.props.depth+1,facetValues:e.data,showMore:!1,className:this.props.cssClasses.childList}))}var s=D({},e,{url:this.props.createURL(e.value),attribute:this.props.attribute,cssClasses:this.props.cssClasses,isFromSearch:this.props.isFromSearch}),o=e.value;return void 0!==e.isRefined&&(o+="/".concat(e.isRefined)),void 0!==e.count&&(o+="/".concat(e.count)),vn(oi,{templateKey:"item",key:o,facetValueToRefine:e.value,handleClick:this.handleItemClick,isRefined:e.isRefined,className:qr(this.props.cssClasses.item,(t={},L(t,this.props.cssClasses.selectedItem,e.isRefined),L(t,this.props.cssClasses.disabledItem,!e.count),L(t,this.props.cssClasses.parentItem,r),t)),subItems:n,templateData:s,templateProps:this.props.templateProps})}},{key:"handleItemClick",value:function(e){var t=e.facetValueToRefine,n=e.originalEvent,r=e.isRefined;if(!(ue(n)||r&&n.target.parentNode.querySelector('input[type="radio"]:checked')))if("INPUT"!==n.target.tagName){for(var i=n.target;i!==n.currentTarget;){if("LABEL"===i.tagName&&(i.querySelector('input[type="checkbox"]')||i.querySelector('input[type="radio"]')))return;"A"===i.tagName&&i.href&&n.preventDefault(),i=i.parentNode}n.stopPropagation(),this.refine(t,r)}else this.refine(t,r)}},{key:"componentWillReceiveProps",value:function(e){this.searchBox&&!e.isFromSearch&&this.searchBox.resetInput()}},{key:"refineFirstValue",value:function(){var e=this.props.facetValues[0];if(e){var t=e.value;this.props.toggleRefinement(t)}}},{key:"render",value:function(){var t=this,e=qr(this.props.cssClasses.list,L({},"".concat(this.props.cssClasses.depth).concat(this.props.depth),this.props.cssClasses.depth)),n=qr(this.props.cssClasses.showMore,L({},this.props.cssClasses.disabledShowMore,!(!0===this.props.showMore&&this.props.canToggleShowMore))),r=!0===this.props.showMore&&vn(Ur,f({},this.props.templateProps,{templateKey:"showMoreText",rootTagName:"button",rootProps:{className:n,disabled:!this.props.canToggleShowMore,onClick:this.props.toggleShowMore},data:{isShowingMore:this.props.isShowingMore}})),i=!0!==this.props.searchIsAlwaysActive&&!(this.props.isFromSearch||!this.props.hasExhaustiveItems),a=this.props.searchFacetValues&&vn("div",{className:this.props.cssClasses.searchBox},vn(ci,{ref:function(e){return t.searchBox=e},placeholder:this.props.searchPlaceholder,disabled:i,cssClasses:this.props.cssClasses.searchable,templates:this.props.templateProps.templates,onChange:function(e){return t.props.searchFacetValues(e.target.value)},onReset:function(){return t.props.searchFacetValues("")},onSubmit:function(){return t.refineFirstValue()},searchAsYouType:!1})),s=this.props.facetValues&&0<this.props.facetValues.length&&vn("ul",{className:e},this.props.facetValues.map(this._generateFacetItem,this)),o=this.props.searchFacetValues&&this.props.isFromSearch&&0===this.props.facetValues.length&&vn(Ur,f({},this.props.templateProps,{templateKey:"searchableNoResults",rootProps:{className:this.props.cssClasses.noResults}}));return vn("div",{className:qr(this.props.cssClasses.root,L({},this.props.cssClasses.noRefinementRoot,!this.props.facetValues||0===this.props.facetValues.length),this.props.className)},this.props.children,a,s,o,r)}}]),c}();ui.defaultProps={cssClasses:{},depth:0};var li={item:'<a class="{{cssClasses.link}}" href="{{url}}"><span class="{{cssClasses.label}}">{{label}}</span><span class="{{cssClasses.count}}">{{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}}</span></a>',showMoreText:"\n    {{#isShowingMore}}\n      Show less\n    {{/isShowingMore}}\n    {{^isShowingMore}}\n      Show more\n    {{/isShowingMore}}\n  "},hi=Ae({name:"hierarchical-menu"}),fi=at("HierarchicalMenu");function di(e){var t=e.results,n=e.hits,r=e.bindEvent,i=e.cssClasses,a=e.templateProps;return 0===t.hits.length?vn(Ur,f({},a,{templateKey:"empty",rootProps:{className:qr(i.root,i.emptyRoot)},data:t})):vn("div",{className:i.root},vn("ol",{className:i.list},n.map(function(e,t){return vn(Ur,f({},a,{templateKey:"item",rootTagName:"li",rootProps:{className:i.item},key:e.objectID,data:D({},e,{__hitIndex:t}),bindEvent:r}))})))}di.defaultProps={results:{hits:[]},hits:[]};var mi={empty:"No results",item:function(e){return JSON.stringify(e,null,2)}},pi=Ae({name:"hits"}),vi=at("Hits"),gi=On(di);function yi(e){var t=e.currentValue,n=e.options,r=e.cssClasses,i=e.setValue;return vn("select",{className:qr(r.select),onChange:function(e){return i(e.target.value)},value:"".concat(t)},n.map(function(e){return vn("option",{className:qr(r.option),key:e.label+e.value,value:"".concat(e.value)},e.label)}))}var bi=Ae({name:"hits-per-page"}),Ri=at("HitsPerPage"),wi={empty:"No results",showPreviousText:"Show previous results",showMoreText:"Show more results",item:function(e){return JSON.stringify(e,null,2)}},Si=Ae({name:"infinite-hits"}),Pi=at("InfiniteHits"),_i=On(function(e){var t=e.results,n=e.hits,r=e.bindEvent,i=e.hasShowPrevious,a=e.showPrevious,s=e.showMore,o=e.isFirstPage,c=e.isLastPage,u=e.cssClasses,l=e.templateProps;return 0===t.hits.length?vn(Ur,f({},l,{templateKey:"empty",rootProps:{className:qr(u.root,u.emptyRoot)},data:t})):vn("div",{className:u.root},i&&vn(Ur,f({},l,{templateKey:"showPreviousText",rootTagName:"button",rootProps:{className:qr(u.loadPrevious,L({},u.disabledLoadPrevious,o)),disabled:o,onClick:a}})),vn("ol",{className:u.list},n.map(function(e,t){return vn(Ur,f({},l,{templateKey:"item",rootTagName:"li",rootProps:{className:u.item},key:e.objectID,data:D({},e,{__hitIndex:t}),bindEvent:r}))})),vn(Ur,f({},l,{templateKey:"showMoreText",rootTagName:"button",rootProps:{className:qr(u.loadMore,L({},u.disabledLoadMore,c)),disabled:c,onClick:s}})))}),Ni={item:'<a class="{{cssClasses.link}}" href="{{url}}"><span class="{{cssClasses.label}}">{{label}}</span><span class="{{cssClasses.count}}">{{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}}</span></a>',showMoreText:"\n    {{#isShowingMore}}\n      Show less\n    {{/isShowingMore}}\n    {{^isShowingMore}}\n      Show more\n    {{/isShowingMore}}\n  "},xi=Ae({name:"menu"}),Fi=at("Menu");var Ii={reset:'\n<svg class="{{cssClasses.resetIcon}}" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20" width="10" height="10">\n  <path d="M8.114 10L.944 2.83 0 1.885 1.886 0l.943.943L10 8.113l7.17-7.17.944-.943L20 1.886l-.943.943-7.17 7.17 7.17 7.17.943.944L18.114 20l-.943-.943-7.17-7.17-7.17 7.17-.944.943L0 18.114l.943-.943L8.113 10z"></path>\n</svg>\n  ',submit:'\n<svg class="{{cssClasses.submitIcon}}" xmlns="http://www.w3.org/2000/svg" width="10" height="10" viewBox="0 0 40 40">\n  <path d="M26.804 29.01c-2.832 2.34-6.465 3.746-10.426 3.746C7.333 32.756 0 25.424 0 16.378 0 7.333 7.333 0 16.378 0c9.046 0 16.378 7.333 16.378 16.378 0 3.96-1.406 7.594-3.746 10.426l10.534 10.534c.607.607.61 1.59-.004 2.202-.61.61-1.597.61-2.202.004L26.804 29.01zm-10.426.627c7.323 0 13.26-5.936 13.26-13.26 0-7.32-5.937-13.257-13.26-13.257C9.056 3.12 3.12 9.056 3.12 16.378c0 7.323 5.936 13.26 13.258 13.26z"></path>\n</svg>\n  ',loadingIndicator:'\n<svg class="{{cssClasses.loadingIcon}}" width="16" height="16" viewBox="0 0 38 38" xmlns="http://www.w3.org/2000/svg" stroke="#444">\n  <g fill="none" fillRule="evenodd">\n    <g transform="translate(1 1)" strokeWidth="2">\n      <circle strokeOpacity=".5" cx="18" cy="18" r="18" />\n      <path d="M36 18c0-9.94-8.06-18-18-18">\n        <animateTransform\n          attributeName="transform"\n          type="rotate"\n          from="0 18 18"\n          to="360 18 18"\n          dur="1s"\n          repeatCount="indefinite"\n        />\n      </path>\n    </g>\n  </g>\n</svg>\n  '},Ci={item:'<label class="{{cssClasses.label}}">\n  <input type="checkbox"\n         class="{{cssClasses.checkbox}}"\n         value="{{value}}"\n         {{#isRefined}}checked{{/isRefined}} />\n  <span class="{{cssClasses.labelText}}">{{#isFromSearch}}{{{highlighted}}}{{/isFromSearch}}{{^isFromSearch}}{{highlighted}}{{/isFromSearch}}</span>\n  <span class="{{cssClasses.count}}">{{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}}</span>\n</label>',showMoreText:"\n    {{#isShowingMore}}\n      Show less\n    {{/isShowingMore}}\n    {{^isShowingMore}}\n      Show more\n    {{/isShowingMore}}\n    ",searchableNoResults:"No results",searchableReset:Ii.reset,searchableSubmit:Ii.submit,searchableLoadingIndicator:Ii.loadingIndicator},Ti=Ae({name:"refinement-list"}),Ei=at("RefinementList"),ki=at("SearchBox");var Mi={item:'<label class="{{cssClasses.label}}">\n  <input type="radio" class="{{cssClasses.radio}}" name="{{attribute}}"{{#isRefined}} checked{{/isRefined}} />\n  <span class="{{cssClasses.labelText}}">{{label}}</span>\n</label>'},Li=Ae({name:"numeric-menu"}),ji=at("NumericMenu");function Oi(e){var t=e.cssClasses,n=e.label,r=e.ariaLabel,i=e.url,a=e.isDisabled,s=e.handleClick,o=e.pageNumber;return vn("li",{className:t.item},a?vn("span",{className:t.link,dangerouslySetInnerHTML:{__html:n}}):vn("a",{className:t.link,"aria-label":r,href:i,onClick:function(e){return s(o,e)},dangerouslySetInnerHTML:{__html:n}}))}var Ai=function(){function a(){var e,n;k(this,a);for(var t=arguments.length,r=new Array(t),i=0;i<t;i++)r[i]=arguments[i];return L(H(n=B(this,(e=O(a)).call.apply(e,[this].concat(r)))),"handleClick",function(e,t){ue(t)||(t.preventDefault(),n.props.setCurrentPage(e))}),n}return j(a,bn),M(a,[{key:"pageLink",value:function(e){var t=e.label,n=e.ariaLabel,r=e.pageNumber,i=e.additionalClassName,a=void 0===i?null:i,s=e.isDisabled,o=void 0!==s&&s,c=e.isSelected,u=void 0!==c&&c,l=e.createURL,h={item:qr(this.props.cssClasses.item,a),link:this.props.cssClasses.link};o?h.item=qr(h.item,this.props.cssClasses.disabledItem):u&&(h.item=qr(h.item,this.props.cssClasses.selectedItem));var f=l&&!o?l(r):"#";return vn(Oi,{ariaLabel:n,cssClasses:h,handleClick:this.handleClick,isDisabled:o,key:t+r+n,label:t,pageNumber:r,url:f})}},{key:"previousPageLink",value:function(e){var t=e.isFirstPage,n=e.currentPage,r=e.createURL;return this.pageLink({ariaLabel:"Previous",additionalClassName:this.props.cssClasses.previousPageItem,isDisabled:t,label:this.props.templates.previous,pageNumber:n-1,createURL:r})}},{key:"nextPageLink",value:function(e){var t=e.isLastPage,n=e.currentPage,r=e.createURL;return this.pageLink({ariaLabel:"Next",additionalClassName:this.props.cssClasses.nextPageItem,isDisabled:t,label:this.props.templates.next,pageNumber:n+1,createURL:r})}},{key:"firstPageLink",value:function(e){var t=e.isFirstPage,n=e.createURL;return this.pageLink({ariaLabel:"First",additionalClassName:this.props.cssClasses.firstPageItem,isDisabled:t,label:this.props.templates.first,pageNumber:0,createURL:n})}},{key:"lastPageLink",value:function(e){var t=e.isLastPage,n=e.nbPages,r=e.createURL;return this.pageLink({ariaLabel:"Last",additionalClassName:this.props.cssClasses.lastPageItem,isDisabled:t,label:this.props.templates.last,pageNumber:n-1,createURL:r})}},{key:"pages",value:function(e){var t=this,n=e.currentPage,r=e.pages,i=e.createURL;return r.map(function(e){return t.pageLink({ariaLabel:e+1,additionalClassName:t.props.cssClasses.pageItem,isSelected:e===n,label:e+1,pageNumber:e,createURL:i})})}},{key:"render",value:function(){return vn("div",{className:qr(this.props.cssClasses.root,L({},this.props.cssClasses.noRefinementRoot,this.props.nbPages<=1))},vn("ul",{className:this.props.cssClasses.list},this.props.showFirst&&this.firstPageLink(this.props),this.props.showPrevious&&this.previousPageLink(this.props),this.pages(this.props),this.props.showNext&&this.nextPageLink(this.props),this.props.showLast&&this.lastPageLink(this.props)))}}]),a}();Ai.defaultProps={nbHits:0,currentPage:0,nbPages:0};var Hi=Ae({name:"pagination"}),Di=at("Pagination"),Bi={previous:"‹",next:"›",first:"«",last:"»"};var Qi=function(){function t(e){var n;return k(this,t),L(H(n=B(this,O(t).call(this,e))),"onInput",function(t){return function(e){n.setState(L({},t,e.currentTarget.value))}}),L(H(n),"onSubmit",function(e){e.preventDefault(),n.props.refine([n.state.min&&Number(n.state.min),n.state.max&&Number(n.state.max)])}),n.state={min:e.values.min,max:e.values.max},n}return j(t,bn),M(t,[{key:"componentWillReceiveProps",value:function(e){this.setState({min:e.values.min,max:e.values.max})}},{key:"render",value:function(){var e=this.state,t=e.min,n=e.max,r=this.props,i=r.min,a=r.max,s=r.step,o=r.cssClasses,c=r.templateProps,u=a<=i,l=Boolean(t||n);return vn("div",{className:qr(o.root,L({},o.noRefinement,!l))},vn("form",{className:o.form,onSubmit:this.onSubmit},vn("label",{className:o.label},vn("input",{className:qr(o.input,o.inputMin),type:"number",min:i,max:a,step:s,value:null!=t?t:"",onInput:this.onInput("min"),placeholder:i,disabled:u})),vn(Ur,f({},c,{templateKey:"separatorText",rootTagName:"span",rootProps:{className:o.separator}})),vn("label",{className:o.label},vn("input",{className:qr(o.input,o.inputMax),type:"number",min:i,max:a,step:s,value:null!=n?n:"",onInput:this.onInput("max"),placeholder:a,disabled:u})),vn(Ur,f({},c,{templateKey:"submitText",rootTagName:"button",rootProps:{type:"submit",className:o.submit,disabled:u}}))))}}]),t}(),qi=Ae({name:"range-input"}),Ui=at("RangeInput");var Vi=Ae({name:"search-box"}),Wi=at("SearchBox");var $i=40,zi=35,Ki=27,Ji=36,Yi=37,Gi=34,Xi=33,Zi=39,ea=38,ta=100;function na(e,t,n){return(e-t)/(n-t)*100}function ra(e,t,n){var r=e/100;return 0===e?t:100===e?n:Math.round((n-t)*r+t)}function ia(e){return["rheostat","vertical"===e.orientation?"rheostat-vertical":"rheostat-horizontal"].concat(e.className.split(" ")).join(" ")}function aa(e){return Number(e.currentTarget.getAttribute("data-handle-key"))}function sa(e){e.stopPropagation(),e.preventDefault()}var oa=function(){function e(){return k(this,e),B(this,O(e).apply(this,arguments))}return j(e,bn),M(e,[{key:"render",value:function(){return vn("button",f({},this.props,{type:"button"}))}}]),e}(),ca=vn("div",{className:"rheostat-background"}),ua=function(){function n(e){var t;return k(this,n),L(H(t=B(this,O(n).call(this,e))),"state",{className:ia(t.props),handlePos:t.props.values.map(function(e){return na(e,t.props.min,t.props.max)}),handleDimensions:0,mousePos:null,sliderBox:{},slidingIndex:null,values:t.props.values}),t.getPublicState=t.getPublicState.bind(H(t)),t.getSliderBoundingBox=t.getSliderBoundingBox.bind(H(t)),t.getProgressStyle=t.getProgressStyle.bind(H(t)),t.getMinValue=t.getMinValue.bind(H(t)),t.getMaxValue=t.getMaxValue.bind(H(t)),t.getHandleDimensions=t.getHandleDimensions.bind(H(t)),t.getClosestSnapPoint=t.getClosestSnapPoint.bind(H(t)),t.getSnapPosition=t.getSnapPosition.bind(H(t)),t.getNextPositionForKey=t.getNextPositionForKey.bind(H(t)),t.getNextState=t.getNextState.bind(H(t)),t.handleClick=t.handleClick.bind(H(t)),t.getClosestHandle=t.getClosestHandle.bind(H(t)),t.setStartSlide=t.setStartSlide.bind(H(t)),t.startMouseSlide=t.startMouseSlide.bind(H(t)),t.startTouchSlide=t.startTouchSlide.bind(H(t)),t.handleMouseSlide=t.handleMouseSlide.bind(H(t)),t.handleTouchSlide=t.handleTouchSlide.bind(H(t)),t.handleSlide=t.handleSlide.bind(H(t)),t.endSlide=t.endSlide.bind(H(t)),t.handleKeydown=t.handleKeydown.bind(H(t)),t.validatePosition=t.validatePosition.bind(H(t)),t.validateValues=t.validateValues.bind(H(t)),t.canMove=t.canMove.bind(H(t)),t.fireChangeEvent=t.fireChangeEvent.bind(H(t)),t.slideTo=t.slideTo.bind(H(t)),t.updateNewValues=t.updateNewValues.bind(H(t)),t}return j(n,bn),M(n,[{key:"componentWillReceiveProps",value:function(n){var e=this.props,t=e.className,r=e.disabled,i=e.min,a=e.max,s=e.orientation,o=this.state,c=o.values,u=o.slidingIndex,l=n.min!==i||n.max!==a,h=c.length!==n.values.length||c.some(function(e,t){return n.values[t]!==e}),f=n.className!==t||n.orientation!==s,d=n.disabled&&!r;f&&this.setState({className:ia(n)}),(l||h)&&this.updateNewValues(n),d&&null!==u&&this.endSlide()}},{key:"getPublicState",value:function(){var e=this.props,t=e.min;return{max:e.max,min:t,values:this.state.values}}},{key:"getSliderBoundingBox",value:function(){var e=this.rheostat.getDOMNode?this.rheostat.getDOMNode():this.rheostat,t=e.getBoundingClientRect();return{height:t.height||e.clientHeight,left:t.left,top:t.top,width:t.width||e.clientWidth}}},{key:"getProgressStyle",value:function(e){var t=this.state.handlePos,n=t[e];if(0===e)return"vertical"===this.props.orientation?{height:"".concat(n,"%"),top:0}:{left:0,width:"".concat(n,"%")};var r=t[e-1],i=n-r;return"vertical"===this.props.orientation?{height:"".concat(i,"%"),top:"".concat(r,"%")}:{left:"".concat(r,"%"),width:"".concat(i,"%")}}},{key:"getMinValue",value:function(e){return this.state.values[e-1]?Math.max(this.props.min,this.state.values[e-1]):this.props.min}},{key:"getMaxValue",value:function(e){return this.state.values[e+1]?Math.min(this.props.max,this.state.values[e+1]):this.props.max}},{key:"getHandleDimensions",value:function(e,t){var n=e.currentTarget||null;return n?"vertical"===this.props.orientation?n.clientHeight/t.height*ta/2:n.clientWidth/t.width*ta/2:0}},{key:"getClosestSnapPoint",value:function(n){return this.props.snapPoints.length?this.props.snapPoints.reduce(function(e,t){return Math.abs(e-n)<Math.abs(t-n)?e:t}):n}},{key:"getSnapPosition",value:function(e){if(!this.props.snap)return e;var t=this.props,n=t.max,r=t.min,i=ra(e,r,n);return na(this.getClosestSnapPoint(i),r,n)}},{key:"getNextPositionForKey",value:function(e,t){var n,r=this.state,i=r.handlePos,a=r.values,s=this.props,o=s.max,c=s.min,u=s.snapPoints,l=this.props.snap,h=a[e],f=i[e],d=f,m=1;100<=o?f=Math.round(f):m=100/(o-c);var p=null;l&&(p=u.indexOf(this.getClosestSnapPoint(a[e])));var v=(L(n={},Yi,function(e){return-1*e}),L(n,Zi,function(e){return e}),L(n,ea,function(e){return e}),L(n,$i,function(e){return-1*e}),L(n,Gi,function(e){return 1<e?-e:-10*e}),L(n,Xi,function(e){return 1<e?e:10*e}),n);if(Object.prototype.hasOwnProperty.call(v,t))f+=v[t](m),l&&(d<f?p<u.length-1&&(h=u[p+1]):0<p&&(h=u[p-1]));else if(t===Ji)f=0,l&&(h=u[0]);else{if(t!==zi)return null;f=ta,l&&(h=u[u.length-1])}return l?na(h,c,o):f}},{key:"getNextState",value:function(n,e){var t=this.state.handlePos,r=this.props,i=r.max,a=r.min,s=this.validatePosition(n,e),o=t.map(function(e,t){return t===n?s:e});return{handlePos:o,values:o.map(function(e){return ra(e,a,i)})}}},{key:"getClosestHandle",value:function(r){var i=this.state.handlePos;return i.reduce(function(e,t,n){return Math.abs(i[n]-r)<Math.abs(i[e]-r)?n:e},0)}},{key:"setStartSlide",value:function(e,t,n){var r=this.getSliderBoundingBox();this.setState({handleDimensions:this.getHandleDimensions(e,r),mousePos:{x:t,y:n},sliderBox:r,slidingIndex:aa(e)})}},{key:"startMouseSlide",value:function(e){this.setStartSlide(e,e.clientX,e.clientY),"function"==typeof document.addEventListener?(document.addEventListener("mousemove",this.handleMouseSlide,!1),document.addEventListener("mouseup",this.endSlide,!1)):(document.attachEvent("onmousemove",this.handleMouseSlide),document.attachEvent("onmouseup",this.endSlide)),sa(e)}},{key:"startTouchSlide",value:function(e){if(!(1<e.changedTouches.length)){var t=e.changedTouches[0];this.setStartSlide(e,t.clientX,t.clientY),document.addEventListener("touchmove",this.handleTouchSlide,!1),document.addEventListener("touchend",this.endSlide,!1),this.props.onSliderDragStart&&this.props.onSliderDragStart(),sa(e)}}},{key:"handleMouseSlide",value:function(e){null!==this.state.slidingIndex&&(this.handleSlide(e.clientX,e.clientY),sa(e))}},{key:"handleTouchSlide",value:function(e){if(null!==this.state.slidingIndex)if(1<e.changedTouches.length)this.endSlide();else{var t=e.changedTouches[0];this.handleSlide(t.clientX,t.clientY),sa(e)}}},{key:"handleSlide",value:function(e,t){var n=this.state,r=n.slidingIndex,i=n.sliderBox,a="vertical"===this.props.orientation?(t-i.top)/i.height*ta:(e-i.left)/i.width*ta;this.slideTo(r,a),this.canMove(r,a)&&(this.setState({x:e,y:t}),this.props.onSliderDragMove&&this.props.onSliderDragMove())}},{key:"endSlide",value:function(){var e=this,t=this.state.slidingIndex;if(this.setState({slidingIndex:null}),"function"==typeof document.removeEventListener?(document.removeEventListener("mouseup",this.endSlide,!1),document.removeEventListener("touchend",this.endSlide,!1),document.removeEventListener("touchmove",this.handleTouchSlide,!1),document.removeEventListener("mousemove",this.handleMouseSlide,!1)):(document.detachEvent("onmousemove",this.handleMouseSlide),document.detachEvent("onmouseup",this.endSlide)),this.props.onSliderDragEnd&&this.props.onSliderDragEnd(),this.props.snap){var n=this.getSnapPosition(this.state.handlePos[t]);this.slideTo(t,n,function(){return e.fireChangeEvent()})}else this.fireChangeEvent()}},{key:"handleClick",value:function(e){var t=this;if(!e.target.getAttribute("data-handle-key")){var n=this.getSliderBoundingBox(),r=("vertical"===this.props.orientation?(e.clientY-n.top)/n.height:(e.clientX-n.left)/n.width)*ta,i=this.getClosestHandle(r),a=this.getSnapPosition(r);this.slideTo(i,a,function(){return t.fireChangeEvent()}),this.props.onClick&&this.props.onClick()}}},{key:"handleKeydown",value:function(e){var t=this,n=aa(e);if(e.keyCode!==Ki){var r=this.getNextPositionForKey(n,e.keyCode);null!==r&&(this.canMove(n,r)&&(this.slideTo(n,r,function(){return t.fireChangeEvent()}),this.props.onKeyPress&&this.props.onKeyPress()),sa(e))}else e.currentTarget.blur()}},{key:"validatePosition",value:function(e,t){var n=this.state,r=n.handlePos,i=n.handleDimensions;return Math.max(Math.min(t,void 0!==r[e+1]?r[e+1]-i:ta),void 0!==r[e-1]?r[e-1]+i:0)}},{key:"validateValues",value:function(e,t){var n=t||this.props,i=n.max,a=n.min;return e.map(function(e,t,n){var r=Math.max(Math.min(e,i),a);return n.length&&r<n[t-1]?n[t-1]:r})}},{key:"canMove",value:function(e,t){var n=this.state,r=n.handlePos,i=n.handleDimensions;return!(t<0)&&(!(ta<t)&&(!((void 0!==r[e+1]?r[e+1]-i:1/0)<t)&&!(t<(void 0!==r[e-1]?r[e-1]+i:-1/0))))}},{key:"fireChangeEvent",value:function(){var e=this.props.onChange;e&&e(this.getPublicState())}},{key:"slideTo",value:function(e,t,n){var r=this,i=this.getNextState(e,t);this.setState(i,function(){var e=r.props.onValuesUpdated;e&&e(r.getPublicState()),n&&n()})}},{key:"updateNewValues",value:function(e){var t=this;if(null===this.state.slidingIndex){var n=e.max,r=e.min,i=e.values,a=this.validateValues(i,e);this.setState({handlePos:a.map(function(e){return na(e,r,n)}),values:a},function(){return t.fireChangeEvent()})}}},{key:"render",value:function(){var r=this,e=this.props,t=e.children,i=e.disabled,a=e.handle,s=e.max,o=e.min,c=e.orientation,u=e.pitComponent,n=e.pitPoints,l=e.progressBar,h=this.state,f=h.className,d=h.handlePos,m=h.values;return vn("div",{className:f,ref:function(e){r.rheostat=e},onClick:!i&&this.handleClick,style:{position:"relative"}},ca,d.map(function(e,t){var n="vertical"===c?{top:"".concat(e,"%"),position:"absolute"}:{left:"".concat(e,"%"),position:"absolute"};return vn(a,{"aria-valuemax":r.getMaxValue(t),"aria-valuemin":r.getMinValue(t),"aria-valuenow":m[t],"aria-disabled":i,"data-handle-key":t,className:"rheostat-handle",key:"handle-".concat(t),onClick:r.killEvent,onKeyDown:!i&&r.handleKeydown,onMouseDown:!i&&r.startMouseSlide,onTouchStart:!i&&r.startTouchSlide,role:"slider",style:n,tabIndex:0})}),d.map(function(e,t,n){return 0===t&&1<n.length?null:vn(l,{className:"rheostat-progress",key:"progress-bar-".concat(t),style:r.getProgressStyle(t)})}),u&&n.map(function(e){var t=na(e,o,s),n="vertical"===c?{top:"".concat(t,"%"),position:"absolute"}:{left:"".concat(t,"%"),position:"absolute"};return vn(u,{key:"pit-".concat(e),style:n},e)}),t)}}]),n}();L(ua,"defaultProps",{className:"",children:null,disabled:!1,handle:oa,max:ta,min:0,onClick:null,onChange:null,onKeyPress:null,onSliderDragEnd:null,onSliderDragMove:null,onSliderDragStart:null,onValuesUpdated:null,orientation:"horizontal",pitComponent:null,pitPoints:[],progressBar:"div",snap:!1,snapPoints:[],values:[0]});function la(e){var t=e.style,n=e.children,r=Math.round(parseFloat(t.left)),i=[0,50,100].includes(r),a=Array.isArray(n)?n[0]:n,s=Math.round(100*parseInt(a,10))/100;return vn("div",{style:D({},t,{marginLeft:100===r?"-2px":0}),className:qr("rheostat-marker","rheostat-marker-horizontal",{"rheostat-marker-large":i})},i&&vn("div",{className:"rheostat-value"},s))}var ha=function(){function a(){var e,n;k(this,a);for(var t=arguments.length,r=new Array(t),i=0;i<t;i++)r[i]=arguments[i];return L(H(n=B(this,(e=O(a)).call.apply(e,[this].concat(r)))),"handleChange",function(e){var t=e.values;n.isDisabled||n.props.refine(t)}),L(H(n),"createHandleComponent",function(r){return function(e){var t=Math.round(100*parseFloat(e["aria-valuenow"]))/100,n=r&&r.format?r.format(t):t;return vn("div",f({},e,{className:qr(e.className,{"rheostat-handle-lower":0===e["data-handle-key"],"rheostat-handle-upper":1===e["data-handle-key"]})}),r&&vn("div",{className:"rheostat-tooltip"},n))}}),n}return j(a,bn),M(a,[{key:"computeDefaultPitPoints",value:function(e){var t=e.min,n=e.max,r=(n-t)/34;return[t].concat(_(Ie({end:33}).map(function(e){return t+r*(e+1)})),[n])}},{key:"computeSnapPoints",value:function(e){var t=e.min,n=e.max,r=e.step;if(r)return[].concat(_(Ie({start:t,end:n,step:r})),[n])}},{key:"render",value:function(){var e=this.props,t=e.tooltips,n=e.step,r=e.pips,i=e.values,a=e.cssClasses,s=this.isDisabled?{min:this.props.min,max:this.props.max+.001}:this.props,o=s.min,c=s.max,u=this.computeSnapPoints({min:o,max:c,step:n}),l=!1===r?[]:this.computeDefaultPitPoints({min:o,max:c});return vn("div",{className:qr(a.root,L({},a.disabledRoot,this.isDisabled))},vn(ua,{handle:this.createHandleComponent(t),onChange:this.handleChange,min:o,max:c,pitComponent:la,pitPoints:l,snap:!0,snapPoints:u,values:this.isDisabled?[o,c]:i,disabled:this.isDisabled}))}},{key:"isDisabled",get:function(){return this.props.min>=this.props.max}}]),a}(),fa=Ae({name:"range-slider"}),da=at("RangeSlider");var ma=Ae({name:"sort-by"}),pa=at("SortBy");var va={item:'{{#count}}<a class="{{cssClasses.link}}" aria-label="{{value}} & up" href="{{href}}">{{/count}}{{^count}}<div class="{{cssClasses.link}}" aria-label="{{value}} & up" disabled>{{/count}}\n  {{#stars}}<svg class="{{cssClasses.starIcon}} {{#.}}{{cssClasses.fullStarIcon}}{{/.}}{{^.}}{{cssClasses.emptyStarIcon}}{{/.}}" aria-hidden="true" width="24" height="24">\n    {{#.}}<use xlink:href="#ais-RatingMenu-starSymbol"></use>{{/.}}{{^.}}<use xlink:href="#ais-RatingMenu-starEmptySymbol"></use>{{/.}}\n  </svg>{{/stars}}\n  <span class="{{cssClasses.label}}">& Up</span>\n  {{#count}}<span class="{{cssClasses.count}}">{{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}}</span>{{/count}}\n{{#count}}</a>{{/count}}{{^count}}</div>{{/count}}'},ga=Ae({name:"rating-menu"}),ya=at("RatingMenu"),ba=vn("path",{d:"M12 .288l2.833 8.718h9.167l-7.417 5.389 2.833 8.718-7.416-5.388-7.417 5.388 2.833-8.718-7.416-5.389h9.167z"}),Ra=vn("path",{d:"M12 6.76l1.379 4.246h4.465l-3.612 2.625 1.379 4.246-3.611-2.625-3.612 2.625 1.379-4.246-3.612-2.625h4.465l1.38-4.246zm0-6.472l-2.833 8.718h-9.167l7.416 5.389-2.833 8.718 7.417-5.388 7.416 5.388-2.833-8.718 7.417-5.389h-9.167l-2.833-8.718z"});function wa(e){var t=e.nbHits,n=e.hitsPerPage,r=e.nbPages,i=e.page,a=e.processingTimeMS,s=e.query,o=e.templateProps,c=e.cssClasses;return vn("div",{className:c.root},vn(Ur,f({},o,{templateKey:"text",rootTagName:"span",rootProps:{className:c.text},data:{hasManyResults:1<t,hasNoResults:0===t,hasOneResult:1===t,hitsPerPage:n,nbHits:t,nbPages:r,page:i,processingTimeMS:a,query:s,cssClasses:c}})))}var Sa={text:"{{#hasNoResults}}No results{{/hasNoResults}}\n    {{#hasOneResult}}1 result{{/hasOneResult}}\n    {{#hasManyResults}}{{#helpers.formatNumber}}{{nbHits}}{{/helpers.formatNumber}} results{{/hasManyResults}} found in {{processingTimeMS}}ms"},Pa=Ae({name:"stats"}),_a=at("Stats");function Na(e){var t=e.currentRefinement,n=e.refine,r=e.cssClasses,i=e.templateProps;return vn("div",{className:r.root},vn("label",{className:r.label},vn("input",{className:r.checkbox,type:"checkbox",checked:t.isRefined,onChange:function(e){return n(!e.target.checked)}}),vn(Ur,f({},i,{rootTagName:"span",rootProps:{className:r.labelText},templateKey:"labelText",data:t}))))}var xa={labelText:"{{name}}"},Fa=Ae({name:"toggle-refinement"}),Ia=at("ToggleRefinement");function Ca(e){var r=e.items,i=e.cssClasses,a=e.templateProps,s=e.createURL,o=e.refine;return vn("div",{className:qr(i.root,L({},i.noRefinementRoot,0===r.length))},vn("ul",{className:i.list},vn("li",{className:qr(i.item,L({},i.selectedItem,0===r.length))},vn(Ur,f({},a,{templateKey:"home",rootTagName:"a",rootProps:{className:i.link,href:s(void 0),onClick:function(e){e.preventDefault(),o(void 0)}}}))),r.map(function(t,e){var n=e===r.length-1;return vn("li",{key:t.label+e,className:qr(i.item,L({},i.selectedItem,n))},vn(Ur,f({},a,{templateKey:"separator",rootTagName:"span",rootProps:{className:i.separator,"aria-hidden":!0}})),n?t.label:vn("a",{className:i.link,href:s(t.value),onClick:function(e){e.preventDefault(),o(t.value)}},t.label))})))}var Ta=Ae({name:"analytics"}),Ea={home:"Home",separator:">"},ka=Ae({name:"breadcrumb"}),Ma=at("Breadcrumb");function La(e){var t=e.cssClasses,n=e.templateProps,r=e.items,i=e.refine,a=(ge(r,function(e){return e.isRefined})||{value:""}).value;return vn("div",{className:qr(t.root,L({},t.noRefinementRoot,0===r.length))},vn("select",{className:t.select,value:a,onChange:function(e){i(e.target.value)}},vn(Ur,f({},n,{templateKey:"defaultOption",rootTagName:"option",rootProps:{value:"",className:t.option}})),r.map(function(e){return vn(Ur,f({},n,{templateKey:"item",rootTagName:"option",rootProps:{value:e.value,className:t.option},key:e.value,data:e}))})))}var ja={item:"{{label}} ({{#helpers.formatNumber}}{{count}}{{/helpers.formatNumber}})",defaultOption:"See all"},Oa=Ae({name:"menu-select"}),Aa=at("MenuSelect");function Ha(e){var t=e.url,n=e.theme,r=e.cssClasses;return vn("div",{className:r.root},vn("a",{href:t,target:"_blank",className:r.link,"aria-label":"Search by Algolia",rel:"noopener noreferrer"},vn("svg",{height:"1.2em",className:r.logo,viewBox:"0 0 168 24",style:{width:"auto"}},vn("path",{fill:"dark"===n?"#FFF":"#5D6494",d:"M6.97 6.68V8.3a4.47 4.47 0 0 0-2.42-.67 2.2 2.2 0 0 0-1.38.4c-.34.26-.5.6-.5 1.02 0 .43.16.77.49 1.03.33.25.83.53 1.51.83a7.04 7.04 0 0 1 1.9 1.08c.34.24.58.54.73.89.15.34.23.74.23 1.18 0 .95-.33 1.7-1 2.24a4 4 0 0 1-2.6.81 5.71 5.71 0 0 1-2.94-.68v-1.71c.84.63 1.81.94 2.92.94.58 0 1.05-.14 1.39-.4.34-.28.5-.65.5-1.13 0-.29-.1-.55-.3-.8a2.2 2.2 0 0 0-.65-.53 23.03 23.03 0 0 0-1.64-.78 13.67 13.67 0 0 1-1.11-.64c-.12-.1-.28-.22-.46-.4a1.72 1.72 0 0 1-.39-.5 4.46 4.46 0 0 1-.22-.6c-.07-.23-.1-.48-.1-.75 0-.91.33-1.63 1-2.17a4 4 0 0 1 2.57-.8c.97 0 1.8.18 2.47.52zm7.47 5.7v-.3a2.26 2.26 0 0 0-.5-1.44c-.3-.35-.74-.53-1.32-.53-.53 0-.99.2-1.37.58-.38.39-.62.95-.72 1.68h3.91zm1 2.79v1.4c-.6.34-1.38.51-2.36.51a4.02 4.02 0 0 1-3-1.13 4.04 4.04 0 0 1-1.11-2.97c0-1.3.34-2.32 1.02-3.06a3.38 3.38 0 0 1 2.6-1.1c1.03 0 1.85.32 2.46.96.6.64.9 1.57.9 2.78 0 .33-.03.68-.09 1.04h-5.31c.1.7.4 1.24.89 1.61.49.38 1.1.56 1.85.56.86 0 1.58-.2 2.15-.6zm6.61-1.78h-1.21c-.6 0-1.05.12-1.35.36-.3.23-.46.53-.46.89 0 .37.12.66.36.88.23.2.57.32 1.02.32.5 0 .9-.15 1.2-.43.3-.28.44-.65.44-1.1v-.92zm-4.07-2.55V9.33a4.96 4.96 0 0 1 2.5-.55c2.1 0 3.17 1.03 3.17 3.08V17H22.1v-.96c-.42.68-1.15 1.02-2.19 1.02-.76 0-1.38-.22-1.84-.66-.46-.44-.7-1-.7-1.68 0-.78.3-1.38.88-1.81.59-.43 1.4-.65 2.46-.65h1.34v-.46c0-.55-.13-.97-.4-1.25-.26-.29-.7-.43-1.32-.43-.86 0-1.65.24-2.35.72zm9.34-1.93v1.42c.39-1 1.1-1.5 2.12-1.5.15 0 .31.02.5.05v1.53c-.23-.1-.48-.14-.76-.14-.54 0-.99.24-1.34.71a2.8 2.8 0 0 0-.52 1.71V17h-1.57V8.91h1.57zm5 4.09a3 3 0 0 0 .76 2.01c.47.53 1.14.8 2 .8.64 0 1.24-.18 1.8-.53v1.4c-.53.32-1.2.48-2 .48a3.98 3.98 0 0 1-4.17-4.18c0-1.16.38-2.15 1.14-2.98a4 4 0 0 1 3.1-1.23c.7 0 1.34.15 1.92.44v1.44a3.24 3.24 0 0 0-1.77-.5A2.65 2.65 0 0 0 32.33 13zm7.92-7.28v4.58c.46-1 1.3-1.5 2.5-1.5.8 0 1.42.24 1.9.73.48.5.72 1.17.72 2.05V17H43.8v-5.1c0-.56-.14-.99-.43-1.29-.28-.3-.65-.45-1.1-.45-.54 0-1 .2-1.42.6-.4.4-.61 1.02-.61 1.85V17h-1.56V5.72h1.56zM55.2 15.74c.6 0 1.1-.25 1.5-.76.4-.5.6-1.16.6-1.95 0-.92-.2-1.62-.6-2.12-.4-.5-.92-.74-1.55-.74-.56 0-1.05.22-1.5.67-.44.45-.66 1.13-.66 2.06 0 .96.22 1.67.64 2.14.43.47.95.7 1.57.7zM53 5.72v4.42a2.74 2.74 0 0 1 2.43-1.34c1.03 0 1.86.38 2.51 1.15.65.76.97 1.78.97 3.05 0 1.13-.3 2.1-.92 2.9-.62.81-1.47 1.21-2.54 1.21s-1.9-.45-2.46-1.34V17h-1.58V5.72H53zm9.9 11.1l-3.22-7.9h1.74l1 2.62 1.26 3.42c.1-.32.48-1.46 1.15-3.42l.91-2.63h1.66l-2.92 7.87c-.78 2.07-1.96 3.1-3.56 3.1-.28 0-.53-.02-.73-.07v-1.34c.17.04.35.06.54.06 1.03 0 1.76-.57 2.17-1.7z"}),Da,Ba,vn("path",{fill:"dark"===n?"#FFF":"#5468FF",d:"M120.92 18.8c-4.38.02-4.38-3.54-4.38-4.1V1.36l2.67-.42v13.25c0 .32 0 2.36 1.71 2.37v2.24zm-10.84-2.18c.82 0 1.43-.04 1.85-.12v-2.72a5.48 5.48 0 0 0-1.57-.2c-.3 0-.6.02-.9.07-.3.04-.57.12-.81.24-.24.11-.44.28-.58.49a.93.93 0 0 0-.22.65c0 .63.22 1 .61 1.23.4.24.94.36 1.62.36zm-.23-9.7c.88 0 1.62.11 2.23.33.6.22 1.09.53 1.44.92.36.4.61.92.76 1.48.16.56.23 1.17.23 1.85v6.87c-.4.1-1.03.2-1.86.32-.84.12-1.78.18-2.82.18-.69 0-1.32-.07-1.9-.2a4 4 0 0 1-1.46-.63c-.4-.3-.72-.67-.96-1.13a4.3 4.3 0 0 1-.34-1.8c0-.66.13-1.08.39-1.53.26-.45.6-.82 1.04-1.1.45-.3.95-.5 1.54-.62a8.8 8.8 0 0 1 3.79.05v-.44c0-.3-.04-.6-.11-.87a1.78 1.78 0 0 0-1.1-1.22c-.31-.12-.7-.2-1.15-.2a9.75 9.75 0 0 0-2.95.46l-.33-2.19c.34-.12.84-.23 1.48-.35.65-.12 1.34-.18 2.08-.18zm52.84 9.63c.82 0 1.43-.05 1.85-.13V13.7a5.42 5.42 0 0 0-1.57-.2c-.3 0-.6.02-.9.07-.3.04-.57.12-.81.24-.24.12-.44.28-.58.5a.93.93 0 0 0-.22.65c0 .63.22.99.61 1.23.4.24.94.36 1.62.36zm-.23-9.7c.88 0 1.63.11 2.23.33.6.22 1.1.53 1.45.92.35.39.6.92.76 1.48.15.56.23 1.18.23 1.85v6.88c-.41.08-1.03.19-1.87.31-.83.12-1.77.18-2.81.18-.7 0-1.33-.06-1.9-.2a4 4 0 0 1-1.47-.63c-.4-.3-.72-.67-.95-1.13a4.3 4.3 0 0 1-.34-1.8c0-.66.13-1.08.38-1.53.26-.45.61-.82 1.05-1.1.44-.3.95-.5 1.53-.62a8.8 8.8 0 0 1 3.8.05v-.43c0-.31-.04-.6-.12-.88-.07-.28-.2-.52-.38-.73a1.78 1.78 0 0 0-.73-.5c-.3-.1-.68-.2-1.14-.2a9.85 9.85 0 0 0-2.95.47l-.32-2.19a11.63 11.63 0 0 1 3.55-.53zm-8.03-1.27a1.62 1.62 0 0 0 0-3.24 1.62 1.62 0 1 0 0 3.24zm1.35 13.22h-2.7V7.27l2.7-.42V18.8zm-4.72 0c-4.38.02-4.38-3.54-4.38-4.1l-.01-13.34 2.67-.42v13.25c0 .32 0 2.36 1.72 2.37v2.24zm-8.7-5.9a4.7 4.7 0 0 0-.74-2.79 2.4 2.4 0 0 0-2.07-1 2.4 2.4 0 0 0-2.06 1 4.7 4.7 0 0 0-.74 2.8c0 1.16.25 1.94.74 2.62a2.4 2.4 0 0 0 2.07 1.02c.88 0 1.57-.34 2.07-1.02.49-.68.73-1.46.73-2.63zm2.74 0a6.46 6.46 0 0 1-1.52 4.23c-.49.53-1.07.94-1.76 1.22-.68.29-1.73.45-2.26.45-.53 0-1.58-.15-2.25-.45a5.1 5.1 0 0 1-2.88-3.13 7.3 7.3 0 0 1-.01-4.84 5.13 5.13 0 0 1 2.9-3.1 5.67 5.67 0 0 1 2.22-.42c.81 0 1.56.14 2.24.42.69.29 1.28.69 1.75 1.22.49.52.87 1.15 1.14 1.89a7 7 0 0 1 .43 2.5zm-20.14 0c0 1.11.25 2.36.74 2.88.5.52 1.13.78 1.91.78a4.07 4.07 0 0 0 2.12-.6V9.33c-.19-.04-.99-.2-1.76-.23a2.67 2.67 0 0 0-2.23 1 4.73 4.73 0 0 0-.78 2.8zm7.44 5.27c0 1.82-.46 3.16-1.4 4-.94.85-2.37 1.27-4.3 1.27-.7 0-2.17-.13-3.34-.4l.43-2.11c.98.2 2.27.26 2.95.26 1.08 0 1.84-.22 2.3-.66.46-.43.68-1.08.68-1.94v-.44a5.2 5.2 0 0 1-2.54.6 5.6 5.6 0 0 1-2.01-.36 4.2 4.2 0 0 1-2.58-2.71 9.88 9.88 0 0 1 .02-5.35 4.92 4.92 0 0 1 2.93-2.96 6.6 6.6 0 0 1 2.43-.46 19.64 19.64 0 0 1 4.43.66v10.6z"}))))}var Da=vn("path",{fill:"#5468FF",d:"M78.99.94h16.6a2.97 2.97 0 0 1 2.96 2.96v16.6a2.97 2.97 0 0 1-2.97 2.96h-16.6a2.97 2.97 0 0 1-2.96-2.96V3.9A2.96 2.96 0 0 1 79 .94"}),Ba=vn("path",{fill:"#FFF",d:"M89.63 5.97v-.78a.98.98 0 0 0-.98-.97h-2.28a.98.98 0 0 0-.97.97V6c0 .09.08.15.17.13a7.13 7.13 0 0 1 3.9-.02c.08.02.16-.04.16-.13m-6.25 1L83 6.6a.98.98 0 0 0-1.38 0l-.46.46a.97.97 0 0 0 0 1.38l.38.39c.06.06.15.04.2-.02a7.49 7.49 0 0 1 1.63-1.62c.07-.04.08-.14.02-.2m4.16 2.45v3.34c0 .1.1.17.2.12l2.97-1.54c.06-.03.08-.12.05-.18a3.7 3.7 0 0 0-3.08-1.87c-.07 0-.14.06-.14.13m0 8.05a4.49 4.49 0 1 1 0-8.98 4.49 4.49 0 0 1 0 8.98m0-10.85a6.37 6.37 0 1 0 0 12.74 6.37 6.37 0 0 0 0-12.74"}),Qa=at("PoweredBy"),qa=Ae({name:"powered-by"});var Ua,Va,Wa=[],$a=sn.__r;sn.__r=function(e){$a&&$a(e),Ua=0,(Va=e.__c).__H&&(Va.__H.t=ts(Va.__H.t))};var za=sn.diffed;sn.diffed=function(e){za&&za(e);var t=e.__c;if(t){var n=t.__H;n&&(n.u=(n.u.some(function(e){e.ref&&(e.ref.current=e.createHandle())}),[]),n.i=ts(n.i))}};var Ka=sn.unmount;function Ja(e){sn.__h&&sn.__h(Va);var t=Va.__H||(Va.__H={o:[],t:[],i:[],u:[]});return e>=t.o.length&&t.o.push({}),t.o[e]}function Ya(e){return function(n,e,t){var r=Ja(Ua++);return r.__c||(r.__c=Va,r.v=[t?t(e):as(void 0,e),function(e){var t=n(r.v[0],e);r.v[0]!==t&&(r.v[0]=t,r.__c.setState({}))}]),r.v}(as,e)}function Ga(e){return function(e,t){var n=Ja(Ua++);return is(n.m,t)?(n.m=t,n.p=e,n.v=e()):n.v}(function(){return{current:e}},[])}sn.unmount=function(e){Ka&&Ka(e);var t=e.__c;if(t){var n=t.__H;n&&n.o.forEach(function(e){return e.l&&e.l()})}};var Xa=function(){};function Za(){Wa.some(function(e){e.s=!1,e.__P&&(e.__H.t=ts(e.__H.t))}),Wa=[]}if("undefined"!=typeof window){var es=sn.requestAnimationFrame;Xa=function(e){(!e.s&&(e.s=!0)&&1===Wa.push(e)||es!==sn.requestAnimationFrame)&&(es=sn.requestAnimationFrame,(sn.requestAnimationFrame||function(e){function t(){clearTimeout(n),cancelAnimationFrame(r),setTimeout(e)}var n=setTimeout(t,100),r=requestAnimationFrame(t)})(Za))}}function ts(e){return e.forEach(ns),e.forEach(rs),[]}function ns(e){e.l&&e.l()}function rs(e){var t=e.v();"function"==typeof t&&(e.l=t)}function is(n,e){return!n||e.some(function(e,t){return e!==n[t]})}function as(e,t){return"function"==typeof t?t(e):t}function ss(e){var t,n=Q(Ya(e.isCollapsed),2),r=n[0],i=n[1],a=Q(Ya(!1),2),s=a[0],o=a[1],c=Ga(null);return function(e,t){var n=Ja(Ua++);is(n.m,t)&&(n.v=e,n.m=t,Va.__H.t.push(n),Xa(Va))}(function(){if(c.current)return c.current.appendChild(e.bodyElement),function(){c.current.removeChild(e.bodyElement)}},[c,e.bodyElement]),s||e.isCollapsed===r||i(e.isCollapsed),vn("div",{className:qr(e.cssClasses.root,(t={},L(t,e.cssClasses.noRefinementRoot,e.hidden),L(t,e.cssClasses.collapsibleRoot,e.collapsible),L(t,e.cssClasses.collapsedRoot,r),t)),hidden:e.hidden},e.templates.header&&vn("div",{className:e.cssClasses.header},vn(Ur,{templates:e.templates,templateKey:"header",rootTagName:"span",data:e.data}),e.collapsible&&vn("button",{className:e.cssClasses.collapseButton,"aria-expanded":!r,onClick:function(e){e.preventDefault(),o(!0),i(function(e){return!e})}},vn(Ur,{templates:e.templates,templateKey:"collapseButtonText",rootTagName:"span",data:{collapsed:r}}))),vn("div",{className:e.cssClasses.body,ref:c}),e.templates.footer&&vn(Ur,{templates:e.templates,templateKey:"footer",rootProps:{className:e.cssClasses.footer},data:e.data}))}function os(e){var t=e.cssClasses,n=e.isBrowserSupported,r=e.isListening,i=e.toggleListening,a=e.voiceListeningState,s=e.templates,o=a.status,c=a.transcript,u=a.isSpeechFinal,l=a.errorCode;return vn("div",{className:t.root},vn(Ur,{templateKey:"buttonText",rootTagName:"button",rootProps:{className:t.button,type:"button",title:"Search by voice".concat(n?"":" (not supported on this browser)"),onClick:function(e){e.currentTarget.blur(),i()},disabled:!n},data:{status:o,errorCode:l,isListening:r,transcript:c,isSpeechFinal:u,isBrowserSupported:n},templates:s}),vn(Ur,{templateKey:"status",rootProps:{className:t.status},data:{status:o,errorCode:l,isListening:r,transcript:c,isSpeechFinal:u,isBrowserSupported:n},templates:s}))}function cs(e){var t=e.isBrowserSupported,n=e.isListening,r=e.toggleListening,i=e.voiceListeningState,a=e.widgetParams,s=a.container,o=a.cssClasses,c=a.templates;Ln(vn(os,{cssClasses:o,templates:c,isBrowserSupported:t,isListening:n,toggleListening:r,voiceListeningState:i}),s)}function us(e){var t=e.cssClasses,n=e.templates,r=e.items;return vn(Ur,{templateKey:"default",templates:n,rootProps:{className:t.root},data:{items:r}})}function ls(e){var t=e.items,n=e.widgetParams,r=n.container,i=n.cssClasses,a=n.templates;Ln(vn(us,{cssClasses:i,templates:a,items:t}),r)}var hs=Ae({name:"panel"}),fs=at("Panel"),ds={buttonText:function(e){var t=e.status,n=e.errorCode,r=e.isListening;return'<svg\n       xmlns="http://www.w3.org/2000/svg"\n       width="16"\n       height="16"\n       viewBox="0 0 24 24"\n       fill="none"\n       stroke="currentColor"\n       stroke-width="2"\n       stroke-linecap="round"\n       stroke-linejoin="round"\n     >\n       '.concat(function(e,t,n){return"error"===e&&"not-allowed"===t?'<line x1="1" y1="1" x2="23" y2="23"></line>\n            <path d="M9 9v3a3 3 0 0 0 5.12 2.12M15 9.34V4a3 3 0 0 0-5.94-.6"></path>\n            <path d="M17 16.95A7 7 0 0 1 5 12v-2m14 0v2a7 7 0 0 1-.11 1.23"></path>\n            <line x1="12" y1="19" x2="12" y2="23"></line>\n            <line x1="8" y1="23" x2="16" y2="23"></line>':'<path\n            d="M12 1a3 3 0 0 0-3 3v8a3 3 0 0 0 6 0V4a3 3 0 0 0-3-3z"\n            fill="'.concat(n?"currentColor":"none",'">\n          </path>\n          <path d="M19 10v2a7 7 0 0 1-14 0v-2"></path>\n          <line x1="12" y1="19" x2="12" y2="23"></line>\n          <line x1="8" y1="23" x2="16" y2="23"></line>')}(t,n,r),"\n     </svg>")},status:"<p>{{transcript}}</p>"},ms=Ae({name:"voice-search"}),ps=at("VoiceSearch"),vs=Ae({name:"query-rule-custom-data"}),gs=at("QueryRuleCustomData"),ys=Ae({name:"query-rule-context"}),bs=Object.freeze({__proto__:null,clearRefinements:function(e){var t=e||{},n=t.container,r=t.templates,i=void 0===r?Kr:r,a=t.includedAttributes,s=t.excludedAttributes,o=t.transformItems,c=t.cssClasses,u=void 0===c?{}:c;if(!n)throw new Error(Jr("The `container` option is required."));var l=ce(n),h={root:qr(Yr(),u.root),button:qr(Yr({descendantName:"button"}),u.button),disabledButton:qr(Yr({descendantName:"button",modifierName:"disabled"}),u.disabledButton)},f=function(e){var a=e.containerNode,s=e.cssClasses,o=e.renderState,c=e.templates;return function(e,t){var n=e.refine,r=e.hasRefinements,i=e.instantSearchInstance;t?o.templateProps=he({defaultTemplates:Kr,templatesConfig:i.templatesConfig,templates:c}):Ln(vn(Vr,{refine:n,cssClasses:s,hasRefinements:r,templateProps:o.templateProps}),a)}}({containerNode:l,cssClasses:h,renderState:{},templates:i});return Vt(f,function(){return Ln(null,l)})({includedAttributes:a,excludedAttributes:s,transformItems:o})},configure:function(e){return Tr(_e)({searchParameters:e})},EXPERIMENTAL_configureRelatedItems:function(e){return Mr(_e)(e)},currentRefinements:function(e){var t=e||{},n=t.container,r=t.includedAttributes,i=t.excludedAttributes,a=t.cssClasses,s=void 0===a?{}:a,o=t.transformItems;if(!n)throw new Error(Gr("The `container` option is required."));var c=ce(n),u={root:qr(Xr(),s.root),list:qr(Xr({descendantName:"list"}),s.list),item:qr(Xr({descendantName:"item"}),s.item),label:qr(Xr({descendantName:"label"}),s.label),category:qr(Xr({descendantName:"category"}),s.category),categoryLabel:qr(Xr({descendantName:"categoryLabel"}),s.categoryLabel),delete:qr(Xr({descendantName:"delete"}),s.delete)};return zt($r,function(){return Ln(null,c)})({container:c,cssClasses:u,includedAttributes:r,excludedAttributes:i,transformItems:o})},geoSearch:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.initialZoom,r=void 0===n?1:n,i=t.initialPosition,a=void 0===i?{lat:0,lng:0}:i,s=t.templates,o=void 0===s?{}:s,c=t.cssClasses,u=void 0===c?{}:c,l=t.builtInMarker,h=void 0===l?{}:l,f=t.customHTMLMarker,d=t.enableRefine,m=void 0===d||d,p=t.enableClearMapRefinement,v=void 0===p||p,g=t.enableRefineControl,y=void 0===g||g,b=t.container,R=t.googleReference,w=A(t,["initialZoom","initialPosition","templates","cssClasses","builtInMarker","customHTMLMarker","enableRefine","enableClearMapRefinement","enableRefineControl","container","googleReference"]),S={createOptions:_e,events:{}},P={createOptions:_e,events:{}};if(!b)throw new Error(ai("The `container` option is required."));if(!R)throw new Error(ai("The `googleReference` option is required."));var _=ce(b),N={root:qr(si(),u.root),tree:si({descendantName:"tree"}),map:qr(si({descendantName:"map"}),u.map),control:qr(si({descendantName:"control"}),u.control),label:qr(si({descendantName:"label"}),u.label),selectedLabel:qr(si({descendantName:"label",modifierName:"selected"}),u.selectedLabel),input:qr(si({descendantName:"input"}),u.input),redo:qr(si({descendantName:"redo"}),u.redo),disabledRedo:qr(si({descendantName:"redo",modifierName:"disabled"}),u.disabledRedo),reset:qr(si({descendantName:"reset"}),u.reset)},x=D({},ii,{},o),F=D({},S,{},h),I=(Boolean(f)||Boolean(o.HTMLMarker))&&D({},P,{},f),C=function(l){return function(){function u(e){var t,n=e.__id,r=e.position,i=e.map,a=e.template,s=e.className,o=e.anchor,c=void 0===o?{x:0,y:0}:o;return k(this,u),L(H(t=B(this,O(u).call(this))),"__id",void 0),L(H(t),"anchor",void 0),L(H(t),"offset",void 0),L(H(t),"listeners",void 0),L(H(t),"latLng",void 0),L(H(t),"element",void 0),t.__id=n,t.anchor=c,t.listeners={},t.latLng=new l.maps.LatLng(r),t.element=document.createElement("div"),t.element.className=s,t.element.style.position="absolute",t.element.innerHTML=a,t.setMap(i),t}return j(u,l.maps.OverlayView),M(u,[{key:"onAdd",value:function(){this.getPanes().overlayMouseTarget.appendChild(this.element);var e=this.element.getBoundingClientRect();this.offset={x:this.anchor.x+e.width/2,y:this.anchor.y+e.height},this.element.style.width="".concat(e.width,"px")}},{key:"draw",value:function(){var e=this.getProjection().fromLatLngToDivPixel(this.latLng);this.element.style.left="".concat(Math.round(e.x-this.offset.x),"px"),this.element.style.top="".concat(Math.round(e.y-this.offset.y),"px"),this.element.style.zIndex=String(parseInt(this.element.style.top,10))}},{key:"onRemove",value:function(){var t=this;this.element&&(this.element.parentNode.removeChild(this.element),Object.keys(this.listeners).forEach(function(e){t.element.removeEventListener(e,t.listeners[e])}),delete this.element,delete this.listeners)}},{key:"addListener",value:function(e,t){this.listeners[e]=t;var n=this.element;return n.addEventListener(e,t),{remove:function(){return n.removeEventListener(e,t)}}}},{key:"getPosition",value:function(){return this.latLng}}]),u}()}(R),T=I?function(e){var t=e.item,n=A(e,["item"]);return new C(D({},I.createOptions(t),{},n,{__id:t.objectID,position:t._geoloc,className:qr(si({descendantName:"marker"})),template:ve({templateKey:"HTMLMarker",templates:x,data:t})}))}:function(e){var t=e.item,n=A(e,["item"]);return new R.maps.Marker(D({},F.createOptions(t),{},n,{__id:t.objectID,position:t._geoloc}))},E=I||F;return Pr(ri,function(){return Ln(null,_)})(D({},w,{renderState:{},container:_,googleReference:R,initialZoom:r,initialPosition:a,templates:x,cssClasses:N,createMarker:T,markerOptions:E,enableRefine:m,enableClearMapRefinement:v,enableRefineControl:y}))},hierarchicalMenu:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attributes,r=e.separator,i=e.rootPath,a=e.showParentLevel,s=e.limit,o=e.showMore,c=void 0!==o&&o,u=e.showMoreLimit,l=e.sortBy,h=e.transformItems,f=e.templates,d=void 0===f?li:f,m=e.cssClasses,p=void 0===m?{}:m;if(!t)throw new Error(hi("The `container` option is required."));var v=ce(t);return en(function(e){var u=e.cssClasses,l=e.containerNode,h=e.showMore,f=e.templates,d=e.renderState;return function(e,t){var n=e.createURL,r=e.items,i=e.refine,a=e.instantSearchInstance,s=e.isShowingMore,o=e.toggleShowMore,c=e.canToggleShowMore;t?d.templateProps=he({defaultTemplates:li,templatesConfig:a.templatesConfig,templates:f}):Ln(vn(ui,{createURL:n,cssClasses:u,facetValues:r,templateProps:d.templateProps,toggleRefinement:i,showMore:h,toggleShowMore:o,isShowingMore:s,canToggleShowMore:c}),l)}}({cssClasses:{root:qr(fi(),p.root),noRefinementRoot:qr(fi({modifierName:"noRefinement"}),p.noRefinementRoot),list:qr(fi({descendantName:"list"}),p.list),childList:qr(fi({descendantName:"list",modifierName:"child"}),p.childList),item:qr(fi({descendantName:"item"}),p.item),selectedItem:qr(fi({descendantName:"item",modifierName:"selected"}),p.selectedItem),parentItem:qr(fi({descendantName:"item",modifierName:"parent"}),p.parentItem),link:qr(fi({descendantName:"link"}),p.link),label:qr(fi({descendantName:"label"}),p.label),count:qr(fi({descendantName:"count"}),p.count),showMore:qr(fi({descendantName:"showMore"}),p.showMore),disabledShowMore:qr(fi({descendantName:"showMore",modifierName:"disabled"}),p.disabledShowMore)},containerNode:v,templates:d,showMore:c,renderState:{}}),function(){return Ln(null,v)})({attributes:n,separator:r,rootPath:i,showParentLevel:a,limit:s,showMore:c,showMoreLimit:u,sortBy:l,transformItems:h})},hits:function(e){var t=e||{},n=t.container,r=t.escapeHTML,i=t.transformItems,a=t.templates,s=void 0===a?mi:a,o=t.cssClasses,c=void 0===o?{}:o;if(!n)throw new Error(pi("The `container` option is required."));var u=ce(n),l={root:qr(vi(),c.root),emptyRoot:qr(vi({modifierName:"empty"}),c.emptyRoot),list:qr(vi({descendantName:"list"}),c.list),item:qr(vi({descendantName:"item"}),c.item)},h=function(e){var o=e.renderState,c=e.cssClasses,u=e.containerNode,l=e.templates;return function(e,t){var n=e.hits,r=e.results,i=e.instantSearchInstance,a=e.insights,s=e.bindEvent;t?o.templateProps=he({defaultTemplates:mi,templatesConfig:i.templatesConfig,templates:l}):Ln(vn(gi,{cssClasses:c,hits:n,results:r,templateProps:o.templateProps,insights:a,sendEvent:function(e){i.sendEventToInsights(e)},bindEvent:s}),u)}}({containerNode:u,cssClasses:l,renderState:{},templates:s});return an(tn)(h,function(){return Ln(null,u)})({escapeHTML:r,transformItems:i})},hitsPerPage:function(e){var t=e||{},n=t.container,r=t.items,i=t.cssClasses,a=void 0===i?{}:i,s=t.transformItems;if(!n)throw new Error(bi("The `container` option is required."));var o=ce(n),c={root:qr(Ri(),a.root),select:qr(Ri({descendantName:"select"}),a.select),option:qr(Ri({descendantName:"option"}),a.option)},u=function(e){var a=e.containerNode,s=e.cssClasses;return function(e,t){var n=e.items,r=e.refine;if(!t){var i=(ge(n,function(e){return e.isRefined})||{}).value;Ln(vn("div",{className:s.root},vn(yi,{cssClasses:s,currentValue:i,options:n,setValue:r})),a)}}}({containerNode:o,cssClasses:c});return An(u,function(){return Ln(null,o)})({items:r,transformItems:s})},infiniteHits:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.container,r=t.escapeHTML,i=t.transformItems,a=t.templates,s=void 0===a?wi:a,o=t.cssClasses,c=void 0===o?{}:o,u=t.showPrevious,l=t.cache;if(!n)throw new Error(Si("The `container` option is required."));var h=ce(n),f={root:qr(Pi(),c.root),emptyRoot:qr(Pi({modifierName:"empty"}),c.emptyRoot),item:qr(Pi({descendantName:"item"}),c.item),list:qr(Pi({descendantName:"list"}),c.list),loadPrevious:qr(Pi({descendantName:"loadPrevious"}),c.loadPrevious),disabledLoadPrevious:qr(Pi({descendantName:"loadPrevious",modifierName:"disabled"}),c.disabledLoadPrevious),loadMore:qr(Pi({descendantName:"loadMore"}),c.loadMore),disabledLoadMore:qr(Pi({descendantName:"loadMore",modifierName:"disabled"}),c.disabledLoadMore)},d=function(e){var h=e.cssClasses,f=e.containerNode,d=e.renderState,m=e.templates,p=e.showPrevious;return function(e,t){var n=e.hits,r=e.results,i=e.showMore,a=e.showPrevious,s=e.isFirstPage,o=e.isLastPage,c=e.instantSearchInstance,u=e.insights,l=e.bindEvent;t?d.templateProps=he({defaultTemplates:wi,templatesConfig:c.templatesConfig,templates:m}):Ln(vn(_i,{cssClasses:h,hits:n,results:r,hasShowPrevious:p,showPrevious:a,showMore:i,templateProps:d.templateProps,isFirstPage:s,isLastPage:o,insights:u,sendEvent:function(e){c.sendEventToInsights(e)},bindEvent:l}),f)}}({containerNode:h,cssClasses:f,templates:s,showPrevious:u,renderState:{}});return an(Un)(d,function(){return Ln(null,h)})({escapeHTML:r,transformItems:i,showPrevious:u,cache:l})},menu:function(e){var t=e.container,n=e.attribute,r=e.sortBy,i=e.limit,a=e.showMore,s=e.showMoreLimit,o=e.cssClasses,c=void 0===o?{}:o,u=e.templates,l=void 0===u?Ni:u,h=e.transformItems;if(!t)throw new Error(xi("The `container` option is required."));var f=ce(t),d={root:qr(Fi(),c.root),noRefinementRoot:qr(Fi({modifierName:"noRefinement"}),c.noRefinementRoot),list:qr(Fi({descendantName:"list"}),c.list),item:qr(Fi({descendantName:"item"}),c.item),selectedItem:qr(Fi({descendantName:"item",modifierName:"selected"}),c.selectedItem),link:qr(Fi({descendantName:"link"}),c.link),label:qr(Fi({descendantName:"label"}),c.label),count:qr(Fi({descendantName:"count"}),c.count),showMore:qr(Fi({descendantName:"showMore"}),c.showMore),disabledShowMore:qr(Fi({descendantName:"showMore",modifierName:"disabled"}),c.disabledShowMore)};return $n(function(e){var l=e.containerNode,h=e.cssClasses,f=e.renderState,d=e.templates,m=e.showMore;return function(e,t){var n=e.refine,r=e.items,i=e.createURL,a=e.instantSearchInstance,s=e.isShowingMore,o=e.toggleShowMore,c=e.canToggleShowMore;if(t)f.templateProps=he({defaultTemplates:Ni,templatesConfig:a.templatesConfig,templates:d});else{var u=r.map(function(e){return D({},e,{url:i(e.name)})});Ln(vn(ui,{createURL:i,cssClasses:h,facetValues:u,showMore:m,templateProps:f.templateProps,toggleRefinement:n,toggleShowMore:o,isShowingMore:s,canToggleShowMore:c}),l)}}}({containerNode:f,cssClasses:d,renderState:{},templates:l,showMore:a}),function(){return Ln(null,f)})({attribute:n,limit:i,showMore:a,showMoreLimit:s,sortBy:r,transformItems:h})},refinementList:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.operator,i=e.sortBy,a=e.limit,s=e.showMore,o=e.showMoreLimit,c=e.searchable,u=void 0!==c&&c,l=e.searchablePlaceholder,h=void 0===l?"Search...":l,f=e.searchableEscapeFacetValues,d=void 0===f||f,m=e.searchableIsAlwaysActive,p=void 0===m||m,v=e.cssClasses,g=void 0===v?{}:v,y=e.templates,b=void 0===y?Ci:y,R=e.transformItems;if(!t)throw new Error(Ti("The `container` option is required."));var w=!!u&&Boolean(d),S=ce(t),P=function(e){var t=D({},e,{submit:e.searchableSubmit,reset:e.searchableReset,loadingIndicator:e.searchableLoadingIndicator});return t.searchableReset,t.searchableSubmit,t.searchableLoadingIndicator,A(t,["searchableReset","searchableSubmit","searchableLoadingIndicator"])}(D({},Ci,{},b)),_={root:qr(Ei(),g.root),noRefinementRoot:qr(Ei({modifierName:"noRefinement"}),g.noRefinementRoot),list:qr(Ei({descendantName:"list"}),g.list),item:qr(Ei({descendantName:"item"}),g.item),selectedItem:qr(Ei({descendantName:"item",modifierName:"selected"}),g.selectedItem),searchBox:qr(Ei({descendantName:"searchBox"}),g.searchBox),label:qr(Ei({descendantName:"label"}),g.label),checkbox:qr(Ei({descendantName:"checkbox"}),g.checkbox),labelText:qr(Ei({descendantName:"labelText"}),g.labelText),count:qr(Ei({descendantName:"count"}),g.count),noResults:qr(Ei({descendantName:"noResults"}),g.noResults),showMore:qr(Ei({descendantName:"showMore"}),g.showMore),disabledShowMore:qr(Ei({descendantName:"showMore",modifierName:"disabled"}),g.disabledShowMore),searchable:{root:qr(ki(),g.searchableRoot),form:qr(ki({descendantName:"form"}),g.searchableForm),input:qr(ki({descendantName:"input"}),g.searchableInput),submit:qr(ki({descendantName:"submit"}),g.searchableSubmit),submitIcon:qr(ki({descendantName:"submitIcon"}),g.searchableSubmitIcon),reset:qr(ki({descendantName:"reset"}),g.searchableReset),resetIcon:qr(ki({descendantName:"resetIcon"}),g.searchableResetIcon),loadingIndicator:qr(ki({descendantName:"loadingIndicator"}),g.searchableLoadingIndicator),loadingIcon:qr(ki({descendantName:"loadingIcon"}),g.searchableLoadingIcon)}};return sr(function(e){var f=e.containerNode,d=e.cssClasses,m=e.templates,p=e.renderState,v=e.showMore,g=e.searchable,y=e.searchablePlaceholder,b=e.searchableIsAlwaysActive;return function(e,t){var n=e.refine,r=e.items,i=e.createURL,a=e.searchForItems,s=e.isFromSearch,o=e.instantSearchInstance,c=e.toggleShowMore,u=e.isShowingMore,l=e.hasExhaustiveItems,h=e.canToggleShowMore;t?p.templateProps=he({templatesConfig:o.templatesConfig,templates:m}):Ln(vn(ui,{createURL:i,cssClasses:d,facetValues:r,templateProps:p.templateProps,toggleRefinement:n,searchFacetValues:g?a:void 0,searchPlaceholder:y,searchIsAlwaysActive:b,isFromSearch:s,showMore:v&&!s&&0<r.length,toggleShowMore:c,isShowingMore:u,hasExhaustiveItems:l,canToggleShowMore:h}),f)}}({containerNode:S,cssClasses:_,templates:P,renderState:{},searchable:u,searchablePlaceholder:h,searchableIsAlwaysActive:p,showMore:s}),function(){return Ln(null,S)})({attribute:n,operator:r,limit:a,showMore:s,showMoreLimit:o,sortBy:i,escapeFacetValues:w,transformItems:R})},numericMenu:function(e){var t=e||{},n=t.container,r=t.attribute,i=t.items,a=t.cssClasses,s=void 0===a?{}:a,o=t.templates,c=void 0===o?Mi:o,u=t.transformItems;if(!n)throw new Error(Li("The `container` option is required."));var l=ce(n),h={root:qr(ji(),s.root),noRefinementRoot:qr(ji({modifierName:"noRefinement"}),s.noRefinementRoot),list:qr(ji({descendantName:"list"}),s.list),item:qr(ji({descendantName:"item"}),s.item),selectedItem:qr(ji({descendantName:"item",modifierName:"selected"}),s.selectedItem),label:qr(ji({descendantName:"label"}),s.label),radio:qr(ji({descendantName:"radio"}),s.radio),labelText:qr(ji({descendantName:"labelText"}),s.labelText)},f=function(e){var s=e.containerNode,o=e.attribute,c=e.cssClasses,u=e.renderState,l=e.templates;return function(e,t){var n=e.createURL,r=e.instantSearchInstance,i=e.refine,a=e.items;t?u.templateProps=he({defaultTemplates:Mi,templatesConfig:r.templatesConfig,templates:l}):Ln(vn(ui,{createURL:n,cssClasses:c,facetValues:a,templateProps:u.templateProps,toggleRefinement:i,attribute:o}),s)}}({containerNode:l,attribute:r,cssClasses:h,renderState:{},templates:c});return zn(f,function(){return Ln(null,l)})({attribute:r,items:i,transformItems:u})},pagination:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.templates,r=void 0===n?{}:n,i=e.cssClasses,a=void 0===i?{}:i,s=e.totalPages,o=e.padding,c=e.showFirst,u=void 0===c||c,l=e.showLast,h=void 0===l||l,f=e.showPrevious,d=void 0===f||f,m=e.showNext,p=void 0===m||m,v=e.scrollTo,g=void 0===v?"body":v;if(!t)throw new Error(Hi("The `container` option is required."));var y=ce(t),b=!0===g?"body":g,R=!1!==b&&ce(b),w={root:qr(Di(),a.root),noRefinementRoot:qr(Di({modifierName:"noRefinement"}),a.noRefinementRoot),list:qr(Di({descendantName:"list"}),a.list),item:qr(Di({descendantName:"item"}),a.item),firstPageItem:qr(Di({descendantName:"item",modifierName:"firstPage"}),a.firstPageItem),lastPageItem:qr(Di({descendantName:"item",modifierName:"lastPage"}),a.lastPageItem),previousPageItem:qr(Di({descendantName:"item",modifierName:"previousPage"}),a.previousPageItem),nextPageItem:qr(Di({descendantName:"item",modifierName:"nextPage"}),a.nextPageItem),pageItem:qr(Di({descendantName:"item",modifierName:"page"}),a.pageItem),selectedItem:qr(Di({descendantName:"item",modifierName:"selected"}),a.selectedItem),disabledItem:qr(Di({descendantName:"item",modifierName:"disabled"}),a.disabledItem),link:qr(Di({descendantName:"link"}),a.link)},S=D({},Bi,{},r);return tr(function(e){var l=e.containerNode,h=e.cssClasses,f=e.templates,d=e.totalPages,m=e.showFirst,p=e.showLast,v=e.showPrevious,g=e.showNext,y=e.scrollToNode;return function(e,t){var n=e.createURL,r=e.currentRefinement,i=e.nbHits,a=e.nbPages,s=e.pages,o=e.isFirstPage,c=e.isLastPage,u=e.refine;if(!t){Ln(vn(Ai,{createURL:n,cssClasses:h,currentPage:r,templates:f,nbHits:i,nbPages:a,pages:s,totalPages:d,isFirstPage:o,isLastPage:c,setCurrentPage:function(e){u(e),!1!==y&&y.scrollIntoView()},showFirst:m,showLast:p,showPrevious:v,showNext:g}),l)}}}({containerNode:y,cssClasses:w,templates:S,showFirst:u,showLast:h,showPrevious:d,showNext:p,padding:o,scrollToNode:R}),function(){return Ln(null,y)})({totalPages:s,padding:o})},rangeInput:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.min,i=e.max,a=e.precision,s=void 0===a?0:a,o=e.cssClasses,c=void 0===o?{}:o,u=e.templates,l=void 0===u?{}:u;if(!t)throw new Error(qi("The `container` option is required."));var h=ce(t),f=D({separatorText:"to",submitText:"Go"},l),d={root:qr(Ui(),c.root),noRefinement:qr(Ui({modifierName:"noRefinement"})),form:qr(Ui({descendantName:"form"}),c.form),label:qr(Ui({descendantName:"label"}),c.label),input:qr(Ui({descendantName:"input"}),c.input),inputMin:qr(Ui({descendantName:"input",modifierName:"min"}),c.inputMin),inputMax:qr(Ui({descendantName:"input",modifierName:"max"}),c.inputMax),separator:qr(Ui({descendantName:"separator"}),c.separator),submit:qr(Ui({descendantName:"submit"}),c.submit)};return D({},ir(function(e){var d=e.containerNode,m=e.cssClasses,p=e.renderState,v=e.templates;return function(e,t){var n=e.refine,r=e.range,i=e.start,a=e.widgetParams,s=e.instantSearchInstance;if(t)p.templateProps=he({templatesConfig:s.templatesConfig,templates:v});else{var o=r.min,c=r.max,u=Q(i,2),l=u[0],h=u[1],f=1/Math.pow(10,a.precision);Ln(vn(Qi,{min:o,max:c,step:f,values:{min:l!==-1/0&&l!==o?l:void 0,max:h!==1/0&&h!==c?h:void 0},cssClasses:m,refine:n,templateProps:p.templateProps}),d)}}}({containerNode:h,cssClasses:d,templates:f,renderState:{}}),function(){return Ln(null,h)})({attribute:n,min:r,max:i,precision:s}),{$$type:"ais.rangeInput"})},searchBox:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.placeholder,r=void 0===n?"":n,i=e.cssClasses,a=void 0===i?{}:i,s=e.autofocus,o=void 0!==s&&s,c=e.searchAsYouType,u=void 0===c||c,l=e.showReset,h=void 0===l||l,f=e.showSubmit,d=void 0===f||f,m=e.showLoadingIndicator,p=void 0===m||m,v=e.queryHook,g=e.templates;if(!t)throw new Error(Vi("The `container` option is required."));var y=ce(t),b={root:qr(Wi(),a.root),form:qr(Wi({descendantName:"form"}),a.form),input:qr(Wi({descendantName:"input"}),a.input),submit:qr(Wi({descendantName:"submit"}),a.submit),submitIcon:qr(Wi({descendantName:"submitIcon"}),a.submitIcon),reset:qr(Wi({descendantName:"reset"}),a.reset),resetIcon:qr(Wi({descendantName:"resetIcon"}),a.resetIcon),loadingIndicator:qr(Wi({descendantName:"loadingIndicator"}),a.loadingIndicator),loadingIcon:qr(Wi({descendantName:"loadingIcon"}),a.loadingIcon)};return cr(function(e){var i=e.containerNode,a=e.cssClasses,s=e.placeholder,o=e.templates,c=e.autofocus,u=e.searchAsYouType,l=e.showReset,h=e.showSubmit,f=e.showLoadingIndicator;return function(e){var t=e.refine,n=e.query,r=e.isSearchStalled;Ln(vn(ci,{query:n,placeholder:s,autofocus:c,refine:t,searchAsYouType:u,templates:o,showSubmit:h,showReset:l,showLoadingIndicator:f,isSearchStalled:r,cssClasses:a}),i)}}({containerNode:y,cssClasses:b,placeholder:r,templates:D({},Ii,{},g),autofocus:o,searchAsYouType:u,showReset:h,showSubmit:d,showLoadingIndicator:p}),function(){return Ln(null,y)})({queryHook:v})},rangeSlider:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.min,i=e.max,a=e.cssClasses,s=void 0===a?{}:a,o=e.step,c=e.pips,u=void 0===c||c,l=e.precision,h=void 0===l?0:l,f=e.tooltips,d=void 0===f||f;if(!t)throw new Error(fa("The `container` option is required."));var m=ce(t),p={root:qr(da(),s.root),disabledRoot:qr(da({modifierName:"disabled"}),s.disabledRoot)};return D({},ir(function(e){var f=e.containerNode,d=e.cssClasses,m=e.pips,p=e.step,v=e.tooltips;return function(e,t){var n=e.refine,r=e.range,i=e.start;if(!t){var a=r.min,s=r.max,o=Q(i,2),c=o[0],u=o[1],l=c===-1/0?a:c,h=u===1/0?s:u;Ln(vn(ha,{cssClasses:d,refine:n,min:a,max:s,values:[s<l?s:l,h<a?a:h],tooltips:v,step:p,pips:m}),f)}}}({containerNode:m,step:o,pips:u,tooltips:d,renderState:{},cssClasses:p}),function(){return Ln(null,m)})({attribute:n,min:r,max:i,precision:h}),{$$type:"ais.rangeSlider"})},sortBy:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.items,r=e.cssClasses,i=void 0===r?{}:r,a=e.transformItems;if(!t)throw new Error(ma("The `container` option is required."));var s=ce(t),o={root:qr(pa(),i.root),select:qr(pa({descendantName:"select"}),i.select),option:qr(pa({descendantName:"option"}),i.option)};return lr(function(e){var a=e.containerNode,s=e.cssClasses;return function(e,t){var n=e.currentRefinement,r=e.options,i=e.refine;t||Ln(vn("div",{className:s.root},vn(yi,{cssClasses:s,currentValue:n,options:r,setValue:i})),a)}}({containerNode:s,cssClasses:o}),function(){return Ln(null,s)})({items:n,transformItems:a})},ratingMenu:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.max,i=void 0===r?5:r,a=e.cssClasses,s=void 0===a?{}:a,o=e.templates,c=void 0===o?va:o;if(!t)throw new Error(ga("The `container` option is required."));var u=ce(t),l={root:qr(ya(),s.root),noRefinementRoot:qr(ya({modifierName:"noRefinement"}),s.noRefinementRoot),list:qr(ya({descendantName:"list"}),s.list),item:qr(ya({descendantName:"item"}),s.item),selectedItem:qr(ya({descendantName:"item",modifierName:"selected"}),s.selectedItem),disabledItem:qr(ya({descendantName:"item",modifierName:"disabled"}),s.disabledItem),link:qr(ya({descendantName:"link"}),s.link),starIcon:qr(ya({descendantName:"starIcon"}),s.starIcon),fullStarIcon:qr(ya({descendantName:"starIcon",modifierName:"full"}),s.fullStarIcon),emptyStarIcon:qr(ya({descendantName:"starIcon",modifierName:"empty"}),s.emptyStarIcon),label:qr(ya({descendantName:"label"}),s.label),count:qr(ya({descendantName:"count"}),s.count)};return mr(function(e){var s=e.containerNode,o=e.cssClasses,c=e.templates,u=e.renderState;return function(e,t){var n=e.refine,r=e.items,i=e.createURL,a=e.instantSearchInstance;t?u.templateProps=he({defaultTemplates:va,templatesConfig:a.templatesConfig,templates:c}):Ln(vn(ui,{createURL:i,cssClasses:o,facetValues:r,templateProps:u.templateProps,toggleRefinement:n},vn("svg",{xmlns:"http://www.w3.org/2000/svg",style:"display:none;"},vn("symbol",{id:ya({descendantName:"starSymbol"}),viewBox:"0 0 24 24"},ba),vn("symbol",{id:ya({descendantName:"starEmptySymbol"}),viewBox:"0 0 24 24"},Ra))),s)}}({containerNode:u,cssClasses:l,renderState:{},templates:c}),function(){return Ln(null,u)})({attribute:n,max:i})},stats:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.cssClasses,r=void 0===n?{}:n,i=e.templates,a=void 0===i?Sa:i;if(!t)throw new Error(Pa("The `container` option is required."));var s=ce(t),o={root:qr(_a(),r.root),text:qr(_a({descendantName:"text"}),r.text)};return vr(function(e){var u=e.containerNode,l=e.cssClasses,h=e.renderState,f=e.templates;return function(e,t){var n=e.hitsPerPage,r=e.nbHits,i=e.nbPages,a=e.page,s=e.processingTimeMS,o=e.query,c=e.instantSearchInstance;t?h.templateProps=he({defaultTemplates:Sa,templatesConfig:c.templatesConfig,templates:f}):Ln(vn(wa,{cssClasses:l,hitsPerPage:n,nbHits:r,nbPages:i,page:a,processingTimeMS:s,query:o,templateProps:h.templateProps}),u)}}({containerNode:s,cssClasses:o,renderState:{},templates:a}),function(){return Ln(null,s)})()},toggleRefinement:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.attribute,r=e.cssClasses,i=void 0===r?{}:r,a=e.templates,s=void 0===a?xa:a,o=e.on,c=void 0===o||o,u=e.off;if(!t)throw new Error(Fa("The `container` option is required."));var l=ce(t),h={root:qr(Ia(),i.root),label:qr(Ia({descendantName:"label"}),i.label),checkbox:qr(Ia({descendantName:"checkbox"}),i.checkbox),labelText:qr(Ia({descendantName:"labelText"}),i.labelText)};return Rr(function(e){var s=e.containerNode,o=e.cssClasses,c=e.renderState,u=e.templates;return function(e,t){var n=e.value,r=e.createURL,i=e.refine,a=e.instantSearchInstance;t?c.templateProps=he({defaultTemplates:xa,templatesConfig:a.templatesConfig,templates:u}):Ln(vn(Na,{createURL:r,cssClasses:o,currentRefinement:n,templateProps:c.templateProps,refine:function(e){return i({isRefined:e})}}),s)}}({containerNode:l,cssClasses:h,renderState:{},templates:s}),function(){return Ln(null,l)})({attribute:n,on:c,off:u})},analytics:function(e){var t=e||{},s=t.pushFunction,n=t.delay,r=void 0===n?3e3:n,i=t.triggerOnUIInteraction,a=void 0!==i&&i,o=t.pushInitialSearch,c=void 0===o||o,u=t.pushPagination,l=void 0!==u&&u;if(!s)throw new Error(Ta("The `pushFunction` option is required."));function h(e){if(null!==e){var t=[],n=function(e){var t=[];for(var n in e)if(e.hasOwnProperty(n)){var r=e[n].join("+");t.push("".concat(encodeURIComponent(n),"=").concat(encodeURIComponent(n),"_").concat(encodeURIComponent(r)))}return t.join("&")}(D({},e.state.disjunctiveFacetsRefinements,{},e.state.facetsRefinements,{},e.state.hierarchicalFacetsRefinements)),r=function(e){var t=[];for(var n in e)if(e.hasOwnProperty(n)){var r=e[n];if(r.hasOwnProperty(">=")&&r.hasOwnProperty("<="))r[">="]&&r[">="][0]===r["<="]&&r["<="][0]?t.push("".concat(n,"=").concat(n,"_").concat(r[">="])):t.push("".concat(n,"=").concat(n,"_").concat(r[">="],"to").concat(r["<="]));else if(r.hasOwnProperty(">="))t.push("".concat(n,"=").concat(n,"_from").concat(r[">="]));else if(r.hasOwnProperty("<="))t.push("".concat(n,"=").concat(n,"_to").concat(r["<="]));else if(r.hasOwnProperty("=")){var i=[];for(var a in r["="])r["="].hasOwnProperty(a)&&i.push(r["="][a]);t.push("".concat(n,"=").concat(n,"_").concat(i.join("-")))}}return t.join("&")}(e.state.numericRefinements);""!==n&&t.push(n),""!==r&&t.push(r);var i=t.join("&"),a="Query: ".concat(e.state.query||"",", ").concat(i);!0===l&&(a+=", Page: ".concat(e.state.page||0)),m!==a&&(s(i,e.state,e.results),m=a)}}var f,d=null,m="",p=!0;!0===c&&(p=!1);function v(){h(d)}function g(){h(d)}return{init:function(){!0===a&&(document.addEventListener("click",v),window.addEventListener("beforeunload",g))},render:function(e){var t=e.results,n=e.state;!0!==p?(d={results:t,state:n},f&&clearTimeout(f),f=window.setTimeout(function(){return h(d)},r)):p=!1},dispose:function(){!0===a&&(document.removeEventListener("click",v),window.removeEventListener("beforeunload",g))}}},breadcrumb:function(e){var t=e||{},n=t.container,r=t.attributes,i=t.separator,a=t.rootPath,s=t.transformItems,o=t.templates,c=void 0===o?Ea:o,u=t.cssClasses,l=void 0===u?{}:u;if(!n)throw new Error(ka("The `container` option is required."));var h=ce(n),f={root:qr(Ma(),l.root),noRefinementRoot:qr(Ma({modifierName:"noRefinement"}),l.noRefinementRoot),list:qr(Ma({descendantName:"list"}),l.list),item:qr(Ma({descendantName:"item"}),l.item),selectedItem:qr(Ma({descendantName:"item",modifierName:"selected"}),l.selectedItem),separator:qr(Ma({descendantName:"separator"}),l.separator),link:qr(Ma({descendantName:"link"}),l.link)},d=function(e){var o=e.containerNode,c=e.cssClasses,u=e.renderState,l=e.templates;return function(e,t){var n=e.canRefine,r=e.createURL,i=e.instantSearchInstance,a=e.items,s=e.refine;t?u.templateProps=he({defaultTemplates:Ea,templatesConfig:i.templatesConfig,templates:l}):Ln(vn(Ca,{canRefine:n,cssClasses:c,createURL:r,items:a,refine:s,templateProps:u.templateProps}),o)}}({containerNode:h,cssClasses:f,renderState:{},templates:c});return wr(d,function(){return Ln(null,h)})({attributes:r,separator:i,rootPath:a,transformItems:s})},menuSelect:function(e){var t=e.container,n=e.attribute,r=e.sortBy,i=void 0===r?["name:asc"]:r,a=e.limit,s=void 0===a?10:a,o=e.cssClasses,c=void 0===o?{}:o,u=e.templates,l=void 0===u?ja:u,h=e.transformItems;if(!t)throw new Error(Oa("The `container` option is required."));var f=ce(t),d={root:qr(Aa(),c.root),noRefinementRoot:qr(Aa({modifierName:"noRefinement"}),c.noRefinementRoot),select:qr(Aa({descendantName:"select"}),c.select),option:qr(Aa({descendantName:"option"}),c.option)};return $n(function(e){var s=e.containerNode,o=e.cssClasses,c=e.renderState,u=e.templates;return function(e,t){var n=e.refine,r=e.items,i=e.canRefine,a=e.instantSearchInstance;t?c.templateProps=he({defaultTemplates:ja,templatesConfig:a.templatesConfig,templates:u}):Ln(vn(La,{cssClasses:o,items:r,refine:n,templateProps:c.templateProps,canRefine:i}),s)}}({containerNode:f,cssClasses:d,renderState:{},templates:l}),function(){return Ln(null,f)})({attribute:n,limit:s,sortBy:i,transformItems:h})},poweredBy:function(){var e=0<arguments.length&&void 0!==arguments[0]?arguments[0]:{},t=e.container,n=e.cssClasses,r=void 0===n?{}:n,i=e.theme,a=void 0===i?"light":i;if(!t)throw new Error(qa("The `container` option is required."));var s=ce(t),o={root:qr(Qa(),Qa({modifierName:"dark"===a?"dark":"light"}),r.root),link:qr(Qa({descendantName:"link"}),r.link),logo:qr(Qa({descendantName:"logo"}),r.logo)};return Fr(function(e){var a=e.containerNode,s=e.cssClasses;return function(e,t){var n=e.url,r=e.widgetParams;if(t){var i=r.theme;Ln(vn(Ha,{cssClasses:s,url:n,theme:i}),a)}else;}}({containerNode:s,cssClasses:o}),function(){return Ln(null,s)})({theme:a})},panel:function(e){var t=e||{},n=t.templates,r=void 0===n?{}:n,i=t.hidden,o=void 0===i?function(){return!1}:i,a=t.collapsed,s=t.cssClasses,c=void 0===s?{}:s,u=document.createElement("div"),l=Boolean(a),h="function"==typeof a?a:function(){return!1},f={root:qr(fs(),c.root),noRefinementRoot:qr(fs({modifierName:"noRefinement"}),c.noRefinementRoot),collapsibleRoot:qr(fs({modifierName:"collapsible"}),c.collapsibleRoot),collapsedRoot:qr(fs({modifierName:"collapsed"}),c.collapsedRoot),collapseButton:qr(fs({descendantName:"collapseButton"}),c.collapseButton),collapseIcon:qr(fs({descendantName:"collapseIcon"}),c.collapseIcon),body:qr(fs({descendantName:"body"}),c.body),header:qr(fs({descendantName:"header"}),c.header),footer:qr(fs({descendantName:"footer"}),c.footer)};return function(n){return function(e){var i=(e||{}).container;if(!i)throw new Error(hs("The `container` option is required in the widget within the panel."));var t={header:"",footer:"",collapseButtonText:function(e){var t=e.collapsed;return'<svg\n          class="'.concat(f.collapseIcon,'"\n          width="1em"\n          height="1em"\n          viewBox="0 0 500 500"\n        >\n        <path d="').concat(t?"M100 250l300-150v300z":"M250 400l150-300H100z",'" fill="currentColor" />\n        </svg>')}},a=function(e){var a=e.containerNode,s=e.bodyContainerNode,o=e.cssClasses,c=e.templates;return function(e){var t=e.options,n=e.hidden,r=e.collapsible,i=e.collapsed;Ln(vn(ss,{cssClasses:o,hidden:n,collapsible:r,isCollapsed:i,templates:c,data:t,bodyElement:s}),a)}}({containerNode:ce(i),bodyContainerNode:u,cssClasses:f,templates:D({},t,{},r)});a({options:{},hidden:!0,collapsible:l,collapsed:!1});var s=n(D({},e,{container:u}));return D({},s,{dispose:function(){if(Ln(null,ce(i)),"function"==typeof s.dispose){for(var e,t=arguments.length,n=new Array(t),r=0;r<t;r++)n[r]=arguments[r];return(e=s.dispose).call.apply(e,[this].concat(n))}},render:function(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];var r,i=t[0];a({options:i,hidden:Boolean(o(i)),collapsible:l,collapsed:Boolean(h(i))}),"function"==typeof s.render&&(r=s.render).call.apply(r,[this].concat(t))}})}}},voiceSearch:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.container,r=t.cssClasses,i=void 0===r?{}:r,a=t.templates,s=t.searchAsYouSpeak,o=void 0!==s&&s,c=t.language,u=t.additionalQueryParameters,l=t.createVoiceSearchHelper;if(!n)throw new Error(ms("The `container` option is required."));var h=ce(n),f={root:qr(ps(),i.root),button:qr(ps({descendantName:"button"}),i.button),status:qr(ps({descendantName:"status"}),i.status)};return Dr(cs,function(){return Ln(null,h)})({container:h,cssClasses:f,templates:D({},ds,{},a),searchAsYouSpeak:o,language:c,additionalQueryParameters:u,createVoiceSearchHelper:l})},queryRuleCustomData:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.container,r=t.cssClasses,i=void 0===r?{}:r,a=t.templates,s=void 0===a?{}:a,o=t.transformItems,c=void 0===o?function(e){return e}:o;if(!n)throw new Error(vs("The `container` option is required."));var u={root:qr(gs(),i.root)},l=D({},{default:function(e){var t=e.items;return JSON.stringify(t,null,2)}},{},s),h=ce(n);return D({},Ar(ls,function(){Ln(null,h)})({container:h,cssClasses:u,templates:l,transformItems:c}),{$$type:"ais.queryRuleCustomData"})},queryRuleContext:function(e){var t=0<arguments.length&&void 0!==e?e:{},n=t.trackedFilters,r=t.transformRuleContexts;if(!n)throw new Error(ys("The `trackedFilters` option is required."));return D({},Ar(_e)({trackedFilters:n,transformRuleContexts:r}),{$$type:"ais.queryRuleContext"})},index:Ze,places:function(e){var t=e||{},n=t.placesReference,r=void 0===n?void 0:n,i=t.defaultPosition,o=void 0===i?[]:i,a=A(t,["placesReference","defaultPosition"]);if("function"!=typeof r)throw new Error("The `placesReference` option requires a valid Places.js reference.");var c=r(a),u={query:"",initialLatLngViaIP:void 0,isInitialLatLngViaIPSet:!1};return{$$type:"ais.places",init:function(e){var s=e.helper;c.on("change",function(e){var t=e.suggestion,n=t.value,r=t.latlng,i=r.lat,a=r.lng;u.query=n,s.setQueryParameter("insideBoundingBox",void 0).setQueryParameter("aroundLatLngViaIP",!1).setQueryParameter("aroundLatLng","".concat(i,",").concat(a)).search()}),c.on("clear",function(){u.query="",s.setQueryParameter("insideBoundingBox",void 0),1<o.length?s.setQueryParameter("aroundLatLngViaIP",!1).setQueryParameter("aroundLatLng",o.join(",")):s.setQueryParameter("aroundLatLngViaIP",u.initialLatLngViaIP).setQueryParameter("aroundLatLng",void 0),s.search()})},getWidgetState:function(e,t){var n=t.searchParameters.aroundLatLng||o.join(",");if(n!==o.join(",")||u.query)return D({},e,{places:{query:u.query,position:n}});e.places;return A(e,["places"])},getWidgetSearchParameters:function(e,t){var n=t.uiState.places||{},r=n.query,i=void 0===r?"":r,a=n.position,s=void 0===a?o.join(","):a;return u.query=i,u.isInitialLatLngViaIPSet||(u.isInitialLatLngViaIPSet=!0,u.initialLatLngViaIP=e.aroundLatLngViaIP),c.setVal(i),c.close(),e.setQueryParameter("insideBoundingBox",void 0).setQueryParameter("aroundLatLngViaIP",!1).setQueryParameter("aroundLatLng",s||void 0)}}}}),Rs=Object.freeze({__proto__:null,createInsightsMiddleware:function(e){var t=e||{},n=t.insightsClient,r=t.onEvent;if(null!==n&&!n)throw new Error("The `insightsClient` option is required. To disable, set it to `null`.");var s=Boolean(n),o=null===n?_e:n;return function(e){var a=e.instantSearchInstance;return o("_get","_hasCredentials",function(e){if(!e){var t=Q(function(e){if(e.transporter){var t=e.transporter,n=t.headers,r=t.queryParameters,i="x-algolia-application-id",a="x-algolia-api-key";return[n[i]||r[i],n[a]||r[a]]}return[e.applicationID,e.apiKey]}(a.client),2),n=t[0],r=t[1];o("_get","_userToken",function(e){}),o("init",{appId:n,apiKey:r})}}),{onStateChange:function(){},subscribe:function(){function i(e){e&&a.mainIndex.getHelper().setQueryParameter("userToken",e)}a.mainIndex.getHelper().setQueryParameter("clickAnalytics",!0),s&&i(ht()),Array.isArray(o.queue)&&o.queue.forEach(function(e){var t=Q(e,2),n=t[0],r=t[1];"setUserToken"===n&&i(r)}),o("onUserTokenChange",i,{immediate:!0}),a.sendEventToInsights=function(e){r?r(e,n):e.insightsMethod&&o(e.insightsMethod,e.payload)}},unsubscribe:function(){o("onUserTokenChange",void 0),a.sendEventToInsights=_e}}}},createRouterMiddleware:Qt}),ws=Object.freeze({__proto__:null,history:Bt});function Ss(e){e.configure;return A(e,["configure"])}var Ps=Object.freeze({__proto__:null,simple:dt,singleIndex:function(t){return{stateToRoute:function(e){return Ss(e[t]||{})},routeToState:function(e){return L({},t,Ss(0<arguments.length&&void 0!==e?e:{}))}}}});function _s(e){var t=e||{};t.page;return A(t,["page"])}var Ns="ais.infiniteHits";function xs(){return"undefined"!=typeof window&&void 0!==window.sessionStorage}function Fs(e){return new Wt(e)}return Fs.routers=ws,Fs.stateMappings=Ps,Fs.connectors=Qr,Fs.widgets=bs,Fs.version="4.8.3",Fs.createInfiniteHitsSessionStorageCache=function(){return{read:function(e){var t=e.state;if(!xs())return null;try{var n=JSON.parse(window.sessionStorage.getItem(Ns));return n&&Te(n.state,_s(t))?n.hits:null}catch(e){if(e instanceof SyntaxError)try{window.sessionStorage.removeItem(Ns)}catch(e){}return null}},write:function(e){var t=e.state,n=e.hits;if(xs())try{window.sessionStorage.setItem(Ns,JSON.stringify({state:_s(t),hits:n}))}catch(e){}}}},Fs.highlight=ot,Fs.snippet=ut,Fs.insights=lt,Fs.middlewares=Rs,Fs});
 
 /**
  * Skipped minification because the original files appears to be already minified.
  * Do NOT use SRI with dynamically generated files! More information: https://www.jsdelivr.com/using-sri-with-dynamic-files
  */
 /*! @algolia/autocomplete-js 1.0.1 | MIT License | © Algolia, Inc. and contributors | https://github.com/algolia/autocomplete */
-!function(e,t){"object"==typeof exports&&"undefined"!=typeof module?t(exports):"function"==typeof define&&define.amd?define(["exports"],t):t((e="undefined"!=typeof globalThis?globalThis:e||self)["@algolia/autocomplete-js"]={})}(this,(function(e){"use strict";function t(e){return(t="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e})(e)}function n(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function r(){return(r=Object.assign||function(e){for(var t=1;t<arguments.length;t++){var n=arguments[t];for(var r in n)Object.prototype.hasOwnProperty.call(n,r)&&(e[r]=n[r])}return e}).apply(this,arguments)}function o(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function i(e){for(var t=1;t<arguments.length;t++){var r=null!=arguments[t]?arguments[t]:{};t%2?o(Object(r),!0).forEach((function(t){n(e,t,r[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(r)):o(Object(r)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(r,t))}))}return e}function u(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function a(e){return function(e){if(Array.isArray(e))return c(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return c(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return c(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function c(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function l(e){return{current:e}}function s(e,t){var n=void 0;return function(){for(var r=arguments.length,o=new Array(r),i=0;i<r;i++)o[i]=arguments[i];n&&clearTimeout(n),n=setTimeout((function(){return e.apply(void 0,o)}),t)}}var p=0;function f(){return"autocomplete-".concat(p++)}function d(e,t){return t.reduce((function(e,t){return e&&e[t]}),e)}function m(e){return 0===e.collections.length?0:e.collections.reduce((function(e,t){return e+t.items.length}),0)}function v(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function h(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function y(e,t,n){var r=t.initialState;return{getState:function(){return r},dispatch:function(o,i){var u=function(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?v(Object(n),!0).forEach((function(t){h(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):v(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}({},r);r=e(r,{type:o,props:t,payload:i}),n({state:r,prevState:u})}}}function g(e){return e.reduce((function(e,t){return e.concat(t)}),[])}function b(e,t,n,r){if(e<0&&(null===t||null!==r&&0===t))return n+e;var o=(null===t?-1:t)+e;return o<=-1||o>=n?null===r?null:0:o}var _=function(){};function O(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function P(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function S(e){return(S="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e})(e)}function j(e,t){var n=[];return Promise.resolve(e(t)).then((function(e){return Array.isArray(e),"The `getSources` function must return an array of sources but returned type ".concat(JSON.stringify(S(e)),":\n\n").concat(JSON.stringify(e,null,2)),Promise.all(e.filter((function(e){return Boolean(e)})).map((function(e){if(e.sourceId,n.includes(e.sourceId))throw new Error("[Autocomplete] The `sourceId` ".concat(JSON.stringify(e.sourceId)," is not unique."));n.push(e.sourceId);var t=function(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?O(Object(n),!0).forEach((function(t){P(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):O(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}({getItemInputValue:function(e){return e.state.query},getItemUrl:function(){},onSelect:function(e){(0,e.setIsOpen)(!1)},onActive:_},e);return Promise.resolve(t)})))}))}function w(e){var t=function(e){var t=e.collections.map((function(e){return e.items.length})).reduce((function(e,t,n){var r=(e[n-1]||0)+t;return e.push(r),e}),[]).reduce((function(t,n){return n<=e.activeItemId?t+1:t}),0);return e.collections[t]}(e);if(!t)return null;var n=t.items[function(e){for(var t=e.state,n=e.collection,r=!1,o=0,i=0;!1===r;){var u=t.collections[o];if(u===n){r=!0;break}i+=u.items.length,o++}return t.activeItemId-i}({state:e,collection:t})],r=t.source;return{item:n,itemInputValue:r.getItemInputValue({item:n,state:e}),itemUrl:r.getItemUrl({item:n,state:e}),source:r}}function I(e,t){return e===t||e.contains(t)}function E(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function A(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?E(Object(n),!0).forEach((function(t){C(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):E(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function C(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function D(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function k(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?D(Object(n),!0).forEach((function(t){x(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):D(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function x(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function N(e){return function(e){if(Array.isArray(e))return F(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return F(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return F(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function F(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function L(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function R(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?L(Object(n),!0).forEach((function(t){q(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):L(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function q(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function T(e){return(T="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e})(e)}function B(e){return function(e){if(Array.isArray(e))return U(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return U(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return U(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function U(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function M(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function H(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?M(Object(n),!0).forEach((function(t){V(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):M(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function V(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function W(e){return Boolean(e.execute)}function Q(e,t){return Boolean(e.execute)?H(H({},e),{},{requests:e.queries.map((function(n){return{query:n,sourceId:t,transformResponse:e.transformResponse}}))}):{items:e,sourceId:t}}function $(e){var t=e.reduce((function(e,t){if(!W(t))return e.push(t),e;var n=t.searchClient,r=t.execute,o=t.requests,i=e.find((function(e){return W(t)&&W(e)&&e.searchClient===n&&e.execute===r}));if(i){var u;(u=i.items).push.apply(u,B(o))}else{var a={execute:r,items:o,searchClient:n};e.push(a)}return e}),[]).map((function(e){if(!W(e))return Promise.resolve(e);var t=e,n=t.execute,r=t.items;return n({searchClient:t.searchClient,requests:r})}));return Promise.all(t).then((function(e){return g(e)}))}function z(e,t){return t.map((function(t){var n=e.filter((function(e){return e.sourceId===t.sourceId})),r=n.map((function(e){return e.items})),o=n[0].transformResponse,i=o?o(function(e){var t=e.map((function(e){var t;return A(A({},e),{},{hits:null===(t=e.hits)||void 0===t?void 0:t.map((function(t){return A(A({},t),{},{__autocomplete_indexName:e.index,__autocomplete_queryID:e.queryID})}))})}));return{results:t,hits:t.map((function(e){return e.hits})).filter(Boolean),facetHits:t.map((function(e){var t;return null===(t=e.facetHits)||void 0===t?void 0:t.map((function(e){return{label:e.value,count:e.count,_highlightResult:{label:{value:e.highlighted}}}}))})).filter(Boolean)}}(r)):r;return Array.isArray(i),"The `getItems` function must return an array of items but returned type ".concat(JSON.stringify(T(i)),":\n\n").concat(JSON.stringify(i,null,2)),{source:t,items:i}}))}function G(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function J(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?G(Object(n),!0).forEach((function(t){K(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):G(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function K(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function X(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}var Y=null;function Z(e){var t=e.event,n=e.nextState,r=void 0===n?{}:n,o=e.props,i=e.query,u=e.refresh,a=e.store,c=X(e,["event","nextState","props","query","refresh","store"]);Y&&o.environment.clearTimeout(Y);var l,s=c.setCollections,p=c.setIsOpen,f=c.setQuery,d=c.setActiveItemId,m=c.setStatus;return f(i),d(o.defaultActiveItemId),i||!1!==o.openOnFocus?(m("loading"),Y=o.environment.setTimeout((function(){m("stalled")}),o.stallThreshold),o.getSources(J({query:i,refresh:u,state:a.getState()},c)).then((function(e){return m("loading"),Promise.all(e.map((function(e){return Promise.resolve(e.getItems(J({query:i,refresh:u,state:a.getState()},c))).then((function(t){return Q(t,e.sourceId)}))}))).then($).then((function(t){return z(t,e)})).then((function(e){var n;m("idle"),s(e);var l=o.shouldPanelOpen({state:a.getState()});p(null!==(n=r.isOpen)&&void 0!==n?n:o.openOnFocus&&!i&&l||l);var f=w(a.getState());if(null!==a.getState().activeItemId&&f){var d=f.item,v=f.itemInputValue,h=f.itemUrl,y=f.source;y.onActive(J({event:t,item:d,itemInputValue:v,itemUrl:h,refresh:u,source:y,state:a.getState()},c))}})).finally((function(){Y&&o.environment.clearTimeout(Y)}))}))):(m("idle"),s(a.getState().collections.map((function(e){return J(J({},e),{},{items:[]})}))),p(null!==(l=r.isOpen)&&void 0!==l?l:o.shouldPanelOpen({state:a.getState()})),Promise.resolve())}function ee(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function te(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?ee(Object(n),!0).forEach((function(t){ne(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):ee(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function ne(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function re(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function oe(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function ie(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?oe(Object(n),!0).forEach((function(t){ue(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):oe(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function ue(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function ae(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function ce(e){var t=e.props,n=e.refresh,r=e.store,o=ae(e,["props","refresh","store"]);return{getEnvironmentProps:function(e){var n=e.inputElement,o=e.formElement,i=e.panelElement;return ie({onTouchStart:function(e){!1!==r.getState().isOpen&&e.target!==n&&(!1===[o,i].some((function(n){return I(n,e.target)||I(n,t.environment.document.activeElement)}))&&r.dispatch("blur",null))},onTouchMove:function(e){!1!==r.getState().isOpen&&n===t.environment.document.activeElement&&e.target!==n&&n.blur()}},ae(e,["inputElement","formElement","panelElement"]))},getRootProps:function(e){return ie({role:"combobox","aria-expanded":r.getState().isOpen,"aria-haspopup":"listbox","aria-owns":r.getState().isOpen?"".concat(t.id,"-list"):void 0,"aria-labelledby":"".concat(t.id,"-label")},e)},getFormProps:function(e){e.inputElement;return ie({action:"",noValidate:!0,role:"search",onSubmit:function(i){var u;i.preventDefault(),t.onSubmit(ie({event:i,refresh:n,state:r.getState()},o)),r.dispatch("submit",null),null===(u=e.inputElement)||void 0===u||u.blur()},onReset:function(i){var u;i.preventDefault(),t.onReset(ie({event:i,refresh:n,state:r.getState()},o)),r.dispatch("reset",null),null===(u=e.inputElement)||void 0===u||u.focus()}},ae(e,["inputElement"]))},getLabelProps:function(e){return ie({htmlFor:"".concat(t.id,"-input"),id:"".concat(t.id,"-label")},e)},getInputProps:function(e){function i(e){(t.openOnFocus||Boolean(r.getState().query))&&Z(ie({event:e,props:t,query:r.getState().completion||r.getState().query,refresh:n,store:r},o)),r.dispatch("focus",null)}var u="ontouchstart"in t.environment,a=e||{},c=(a.inputElement,a.maxLength),l=void 0===c?512:c,s=ae(a,["inputElement","maxLength"]),p=w(r.getState());return ie({"aria-autocomplete":"both","aria-activedescendant":r.getState().isOpen&&null!==r.getState().activeItemId?"".concat(t.id,"-item-").concat(r.getState().activeItemId):void 0,"aria-controls":r.getState().isOpen?"".concat(t.id,"-list"):void 0,"aria-labelledby":"".concat(t.id,"-label"),value:r.getState().completion||r.getState().query,id:"".concat(t.id,"-input"),autoComplete:"off",autoCorrect:"off",autoCapitalize:"off",enterKeyHint:null!=p&&p.itemUrl?"go":"search",spellCheck:"false",autoFocus:t.autoFocus,placeholder:t.placeholder,maxLength:l,type:"search",onChange:function(e){Z(ie({event:e,props:t,query:e.currentTarget.value.slice(0,l),refresh:n,store:r},o))},onKeyDown:function(e){!function(e){var t=e.event,n=e.props,r=e.refresh,o=e.store,i=re(e,["event","props","refresh","store"]);if("ArrowUp"===t.key||"ArrowDown"===t.key){t.preventDefault(),o.dispatch(t.key,null);var u=n.environment.document.getElementById("".concat(n.id,"-item-").concat(o.getState().activeItemId));u&&(u.scrollIntoViewIfNeeded?u.scrollIntoViewIfNeeded(!1):u.scrollIntoView(!1));var a=w(o.getState());if(null!==o.getState().activeItemId&&a){var c=a.item,l=a.itemInputValue,s=a.itemUrl,p=a.source;p.onActive(te({event:t,item:c,itemInputValue:l,itemUrl:s,refresh:r,source:p,state:o.getState()},i))}}else if("Escape"===t.key)t.preventDefault(),o.dispatch(t.key,null);else if("Enter"===t.key){if(null===o.getState().activeItemId||o.getState().collections.every((function(e){return 0===e.items.length})))return;t.preventDefault();var f=w(o.getState()),d=f.item,m=f.itemInputValue,v=f.itemUrl,h=f.source;if(t.metaKey||t.ctrlKey)void 0!==v&&(h.onSelect(te({event:t,item:d,itemInputValue:m,itemUrl:v,refresh:r,source:h,state:o.getState()},i)),n.navigator.navigateNewTab({itemUrl:v,item:d,state:o.getState()}));else if(t.shiftKey)void 0!==v&&(h.onSelect(te({event:t,item:d,itemInputValue:m,itemUrl:v,refresh:r,source:h,state:o.getState()},i)),n.navigator.navigateNewWindow({itemUrl:v,item:d,state:o.getState()}));else if(t.altKey);else{if(void 0!==v)return h.onSelect(te({event:t,item:d,itemInputValue:m,itemUrl:v,refresh:r,source:h,state:o.getState()},i)),void n.navigator.navigate({itemUrl:v,item:d,state:o.getState()});Z(te({event:t,nextState:{isOpen:!1},props:n,query:m,refresh:r,store:o},i)).then((function(){h.onSelect(te({event:t,item:d,itemInputValue:m,itemUrl:v,refresh:r,source:h,state:o.getState()},i))}))}}}(ie({event:e,props:t,refresh:n,store:r},o))},onFocus:i,onBlur:function(){u||r.dispatch("blur",null)},onClick:function(n){e.inputElement!==t.environment.document.activeElement||r.getState().isOpen||i(n)}},s)},getPanelProps:function(e){return ie({onMouseDown:function(e){e.preventDefault()},onMouseLeave:function(){r.dispatch("mouseleave",null)}},e)},getListProps:function(e){return ie({role:"listbox","aria-labelledby":"".concat(t.id,"-label"),id:"".concat(t.id,"-list")},e)},getItemProps:function(e){var i=e.item,u=e.source,a=ae(e,["item","source"]);return ie({id:"".concat(t.id,"-item-").concat(i.__autocomplete_id),role:"option","aria-selected":r.getState().activeItemId===i.__autocomplete_id,onMouseMove:function(e){if(i.__autocomplete_id!==r.getState().activeItemId){r.dispatch("mousemove",i.__autocomplete_id);var t=w(r.getState());if(null!==r.getState().activeItemId&&t){var u=t.item,a=t.itemInputValue,c=t.itemUrl,l=t.source;l.onActive(ie({event:e,item:u,itemInputValue:a,itemUrl:c,refresh:n,source:l,state:r.getState()},o))}}},onMouseDown:function(e){e.preventDefault()},onClick:function(e){var a=u.getItemInputValue({item:i,state:r.getState()}),c=u.getItemUrl({item:i,state:r.getState()});(c?Promise.resolve():Z(ie({event:e,nextState:{isOpen:!1},props:t,query:a,refresh:n,store:r},o))).then((function(){u.onSelect(ie({event:e,item:i,itemInputValue:a,itemUrl:c,refresh:n,source:u,state:r.getState()},o))}))}},a)}}}function le(e){var t=e.state;return!1===t.isOpen||null===t.activeItemId?null:w(t).itemInputValue||null}function se(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function pe(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?se(Object(n),!0).forEach((function(t){fe(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):se(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function fe(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}var de=function(e,t){switch(t.type){case"setActiveItemId":return pe(pe({},e),{},{activeItemId:t.payload});case"setQuery":return pe(pe({},e),{},{query:t.payload,completion:null});case"setCollections":return pe(pe({},e),{},{collections:t.payload});case"setIsOpen":return pe(pe({},e),{},{isOpen:t.payload});case"setStatus":return pe(pe({},e),{},{status:t.payload});case"setContext":return pe(pe({},e),{},{context:pe(pe({},e.context),t.payload)});case"ArrowDown":var n=pe(pe({},e),{},{activeItemId:b(1,e.activeItemId,m(e),t.props.defaultActiveItemId)});return pe(pe({},n),{},{completion:le({state:n})});case"ArrowUp":var r=pe(pe({},e),{},{activeItemId:b(-1,e.activeItemId,m(e),t.props.defaultActiveItemId)});return pe(pe({},r),{},{completion:le({state:r})});case"Escape":return e.isOpen?pe(pe({},e),{},{isOpen:!1,completion:null}):pe(pe({},e),{},{query:"",status:"idle",collections:[]});case"submit":return pe(pe({},e),{},{activeItemId:null,isOpen:!1,status:"idle"});case"reset":return pe(pe({},e),{},{activeItemId:!0===t.props.openOnFocus?t.props.defaultActiveItemId:null,status:"idle",query:""});case"focus":return pe(pe({},e),{},{activeItemId:t.props.defaultActiveItemId,isOpen:(t.props.openOnFocus||Boolean(e.query))&&t.props.shouldPanelOpen({state:e})});case"blur":return t.props.debug?e:pe(pe({},e),{},{isOpen:!1,activeItemId:null});case"mousemove":return pe(pe({},e),{},{activeItemId:t.payload});case"mouseleave":return pe(pe({},e),{},{activeItemId:t.props.defaultActiveItemId});default:return"The reducer action ".concat(JSON.stringify(t.type)," is not supported."),e}};function me(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function ve(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?me(Object(n),!0).forEach((function(t){he(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):me(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function he(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function ye(e){var t=[],n=function(e,t){var n,r="undefined"!=typeof window?window:{},o=e.plugins||[];return R(R({debug:!1,openOnFocus:!1,placeholder:"",autoFocus:!1,defaultActiveItemId:null,stallThreshold:300,environment:r,shouldPanelOpen:function(e){return m(e.state)>0}},e),{},{id:null!==(n=e.id)&&void 0!==n?n:f(),plugins:o,initialState:R({activeItemId:null,query:"",completion:null,collections:[],isOpen:!1,status:"idle",context:{}},e.initialState),onStateChange:function(t){var n;null===(n=e.onStateChange)||void 0===n||n.call(e,t),o.forEach((function(e){var n;return null===(n=e.onStateChange)||void 0===n?void 0:n.call(e,t)}))},onSubmit:function(t){var n;null===(n=e.onSubmit)||void 0===n||n.call(e,t),o.forEach((function(e){var n;return null===(n=e.onSubmit)||void 0===n?void 0:n.call(e,t)}))},onReset:function(t){var n;null===(n=e.onReset)||void 0===n||n.call(e,t),o.forEach((function(e){var n;return null===(n=e.onReset)||void 0===n?void 0:n.call(e,t)}))},getSources:function(n){return Promise.all([].concat(N(o.map((function(e){return e.getSources}))),[e.getSources]).filter(Boolean).map((function(e){return j(e,n)}))).then((function(e){return g(e)})).then((function(e){return e.map((function(e){return R(R({},e),{},{onSelect:function(n){e.onSelect(n),t.forEach((function(e){var t;return null===(t=e.onSelect)||void 0===t?void 0:t.call(e,n)}))},onActive:function(n){e.onActive(n),t.forEach((function(e){var t;return null===(t=e.onActive)||void 0===t?void 0:t.call(e,n)}))}})}))}))},navigator:R({navigate:function(e){var t=e.itemUrl;r.location.assign(t)},navigateNewTab:function(e){var t=e.itemUrl,n=r.open(t,"_blank","noopener");null==n||n.focus()},navigateNewWindow:function(e){var t=e.itemUrl;r.open(t,"_blank","noopener")}},e.navigator)})}(e,t),r=y(de,n,(function(e){var t=e.prevState,r=e.state;n.onStateChange(ve({prevState:t,state:r,refresh:u},o))})),o=function(e){var t=e.store;return{setActiveItemId:function(e){t.dispatch("setActiveItemId",e)},setQuery:function(e){t.dispatch("setQuery",e)},setCollections:function(e){var n=0,r=e.map((function(e){return k(k({},e),{},{items:g(e.items).map((function(e){return k(k({},e),{},{__autocomplete_id:n++})}))})}));t.dispatch("setCollections",r)},setIsOpen:function(e){t.dispatch("setIsOpen",e)},setStatus:function(e){t.dispatch("setStatus",e)},setContext:function(e){t.dispatch("setContext",e)}}}({store:r}),i=ce(ve({props:n,refresh:u,store:r},o));function u(){return Z(ve({event:new Event("input"),nextState:{isOpen:r.getState().isOpen},props:n,query:r.getState().query,refresh:u,store:r},o))}return n.plugins.forEach((function(e){var n;return null===(n=e.subscribe)||void 0===n?void 0:n.call(e,ve(ve({},o),{},{refresh:u,onSelect:function(e){t.push({onSelect:e})},onActive:function(e){t.push({onActive:e})}}))})),ve(ve({refresh:u},i),o)}var ge=function(e){var t=e.environment,n=t.document.createElementNS("http://www.w3.org/2000/svg","svg");n.setAttribute("class","aa-ClearIcon"),n.setAttribute("viewBox","0 0 24 24"),n.setAttribute("width","18"),n.setAttribute("height","18"),n.setAttribute("fill","currentColor");var r=t.document.createElementNS("http://www.w3.org/2000/svg","path");return r.setAttribute("d","M5.293 6.707l5.293 5.293-5.293 5.293c-0.391 0.391-0.391 1.024 0 1.414s1.024 0.391 1.414 0l5.293-5.293 5.293 5.293c0.391 0.391 1.024 0.391 1.414 0s0.391-1.024 0-1.414l-5.293-5.293 5.293-5.293c0.391-0.391 0.391-1.024 0-1.414s-1.024-0.391-1.414 0l-5.293 5.293-5.293-5.293c-0.391-0.391-1.024-0.391-1.414 0s-0.391 1.024 0 1.414z"),n.appendChild(r),n};function be(e,t){if("string"==typeof t){var n=e.document.querySelector(t);return"The element ".concat(JSON.stringify(t)," is not in the document."),n}return t}function _e(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];return t.reduce((function(e,t){return Object.keys(t).forEach((function(n){var r=e[n],o=t[n];r!==o&&(e[n]=[r,o].filter(Boolean).join(" "))})),e}),{})}var Oe=function(e){return e&&"object"===t(e)};function Pe(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];return t.reduce((function(e,t){return Object.keys(t).forEach((function(n){var r=e[n],o=t[n];Array.isArray(r)&&Array.isArray(o)?e[n]=r.concat.apply(r,a(o)):Oe(r)&&Oe(o)?e[n]=Pe(r,o):e[n]=o})),e}),{})}function Se(e,t,n){e[t]=null===n?"":"number"!=typeof n?n:n+"px"}function je(e){this._listeners[e.type](e)}function we(e,t,n){var r,o,i=e[t];if("style"===t)if("string"==typeof n)e.style=n;else if(null===n)e.style="";else for(t in n)i&&n[t]===i[t]||Se(e.style,t,n[t]);else"o"===t[0]&&"n"===t[1]?(r=t!==(t=t.replace(/Capture$/,"")),(o=t.toLowerCase())in e&&(t=o),t=t.slice(2),e._listeners||(e._listeners={}),e._listeners[t]=n,n?i||e.addEventListener(t,je,r):e.removeEventListener(t,je,r)):"list"!==t&&"tagName"!==t&&"form"!==t&&"type"!==t&&"size"!==t&&"download"!==t&&"href"!==t&&t in e?e[t]=null==n?"":n:"function"!=typeof n&&"dangerouslySetInnerHTML"!==t&&(null==n||!1===n&&!/^ar/.test(t)?e.removeAttribute(t):e.setAttribute(t,n))}function Ie(e){switch(e){case"onChange":return"onInput";default:return e}}function Ee(e,t){for(var n in t)we(e,Ie(n),t[n])}function Ae(e,t){for(var n in t)"o"===n[0]&&"n"===n[1]||we(e,Ie(n),t[n])}function Ce(e){return function(t,n){var r=n.children,o=void 0===r?[]:r,i=u(n,["children"]),c=e.document.createElement(t);return Ee(c,i),c.append.apply(c,a(o)),c}}var De=function(e){var t=e.environment.document.createElementNS("http://www.w3.org/2000/svg","svg");return t.setAttribute("class","aa-LoadingIcon"),t.setAttribute("viewBox","0 0 100 100"),t.setAttribute("width","20"),t.setAttribute("height","20"),t.innerHTML='<circle\n  cx="50"\n  cy="50"\n  fill="none"\n  r="35"\n  stroke="currentColor"\n  stroke-dasharray="164.93361431346415 56.97787143782138"\n  stroke-width="6"\n>\n  <animateTransform\n    attributeName="transform"\n    type="rotate"\n    repeatCount="indefinite"\n    dur="1s"\n    values="0 50 50;90 50 50;180 50 50;360 50 50"\n    keyTimes="0;0.40;0.65;1"\n  />\n</circle>',t},ke=function(e){var t=e.environment,n=t.document.createElementNS("http://www.w3.org/2000/svg","svg");n.setAttribute("class","aa-SubmitIcon"),n.setAttribute("viewBox","0 0 24 24"),n.setAttribute("width","20"),n.setAttribute("height","20"),n.setAttribute("fill","currentColor");var r=t.document.createElementNS("http://www.w3.org/2000/svg","path");return r.setAttribute("d","M16.041 15.856c-0.034 0.026-0.067 0.055-0.099 0.087s-0.060 0.064-0.087 0.099c-1.258 1.213-2.969 1.958-4.855 1.958-1.933 0-3.682-0.782-4.95-2.050s-2.050-3.017-2.050-4.95 0.782-3.682 2.050-4.95 3.017-2.050 4.95-2.050 3.682 0.782 4.95 2.050 2.050 3.017 2.050 4.95c0 1.886-0.745 3.597-1.959 4.856zM21.707 20.293l-3.675-3.675c1.231-1.54 1.968-3.493 1.968-5.618 0-2.485-1.008-4.736-2.636-6.364s-3.879-2.636-6.364-2.636-4.736 1.008-6.364 2.636-2.636 3.879-2.636 6.364 1.008 4.736 2.636 6.364 3.879 2.636 6.364 2.636c2.125 0 4.078-0.737 5.618-1.968l3.675 3.675c0.391 0.391 1.024 0.391 1.414 0s0.391-1.024 0-1.414z"),n.appendChild(r),n};function xe(e){var t=e.autocomplete,n=e.autocompleteScopeApi,r=e.classNames,o=e.environment,a=e.isDetached,c=e.placeholder,l=void 0===c?"Search":c,s=e.propGetters,p=e.setIsModalOpen,f=e.state,d=Ce(o),m=s.getRootProps(i({state:f,props:t.getRootProps({})},n)),v=d("div",i({class:r.root},m)),h=d("div",{class:r.detachedContainer,onMouseDown:function(e){e.stopPropagation()}}),y=d("div",{class:r.detachedOverlay,children:[h],onMouseDown:function(){p(!1),t.setIsOpen(!1)}}),g=s.getLabelProps(i({state:f,props:t.getLabelProps({})},n)),b=d("button",{class:r.submitButton,type:"submit",title:"Submit",children:[ke({environment:o})]}),_=d("label",i({class:r.label,children:[b]},g)),O=d("button",{class:r.clearButton,type:"reset",title:"Clear",children:[ge({environment:o})]}),P=d("div",{class:r.loadingIndicator,children:[De({environment:o})]}),S=function(e){var t=e.autocompleteScopeApi,n=e.environment,r=(e.classNames,e.getInputProps),o=e.getInputPropsCore,a=e.onDetachedEscape,c=e.state,l=u(e,["autocompleteScopeApi","environment","classNames","getInputProps","getInputPropsCore","onDetachedEscape","state"]),s=Ce(n)("input",l),p=r(i({state:c,props:o({inputElement:s}),inputElement:s},t));return Ee(s,i(i({},p),{},{onKeyDown:function(e){if(a&&"Escape"===e.key)return e.preventDefault(),void a();p.onKeyDown(e)}})),s}({class:r.input,environment:o,state:f,getInputProps:s.getInputProps,getInputPropsCore:t.getInputProps,autocompleteScopeApi:n,onDetachedEscape:a?function(){t.setIsOpen(!1),p(!1)}:void 0}),j=d("div",{class:r.inputWrapperPrefix,children:[_,P]}),w=d("div",{class:r.inputWrapperSuffix,children:[O]}),I=d("div",{class:r.inputWrapper,children:[S]}),E=s.getFormProps(i({state:f,props:t.getFormProps({inputElement:S})},n)),A=d("form",i({class:r.form,children:[j,I,w]},E)),C=s.getPanelProps(i({state:f,props:t.getPanelProps({})},n)),D=d("div",i({class:r.panel},C));if(a){var k=d("div",{class:r.detachedSearchButtonIcon,children:[ke({environment:o})]}),x=d("div",{class:r.detachedSearchButtonPlaceholder,textContent:l}),N=d("button",{class:r.detachedSearchButton,onClick:function(e){e.preventDefault(),p(!0)},children:[k,x]}),F=d("button",{class:r.detachedCancelButton,textContent:"Cancel",onClick:function(){t.setIsOpen(!1),p(!1)}}),L=d("div",{class:r.detachedFormContainer,children:[A,F]});h.appendChild(L),v.appendChild(N)}else v.appendChild(A);return{detachedContainer:h,detachedOverlay:y,inputWrapper:I,input:S,root:v,form:A,label:_,submitButton:b,clearButton:O,loadingIndicator:P,panel:D}}var Ne,Fe,Le,Re,qe={},Te=[],Be=/acit|ex(?:s|g|n|p|$)|rph|grid|ows|mnc|ntw|ine[ch]|zoo|^ord|itera/i;function Ue(e,t){for(var n in t)e[n]=t[n];return e}function Me(e){var t=e.parentNode;t&&t.removeChild(e)}function He(e,t,n){var r,o,i,u=arguments,a={};for(i in t)"key"==i?r=t[i]:"ref"==i?o=t[i]:a[i]=t[i];if(arguments.length>3)for(n=[n],i=3;i<arguments.length;i++)n.push(u[i]);if(null!=n&&(a.children=n),"function"==typeof e&&null!=e.defaultProps)for(i in e.defaultProps)void 0===a[i]&&(a[i]=e.defaultProps[i]);return Ve(e,a,r,o,null)}function Ve(e,t,n,r,o){var i={type:e,props:t,key:n,ref:r,__k:null,__:null,__b:0,__e:null,__d:void 0,__c:null,__h:null,constructor:void 0,__v:null==o?++Ne.__v:o};return null!=Ne.vnode&&Ne.vnode(i),i}function We(e){return e.children}function Qe(e,t){this.props=e,this.context=t}function $e(e,t){if(null==t)return e.__?$e(e.__,e.__.__k.indexOf(e)+1):null;for(var n;t<e.__k.length;t++)if(null!=(n=e.__k[t])&&null!=n.__e)return n.__e;return"function"==typeof e.type?$e(e):null}function ze(e){var t,n;if(null!=(e=e.__)&&null!=e.__c){for(e.__e=e.__c.base=null,t=0;t<e.__k.length;t++)if(null!=(n=e.__k[t])&&null!=n.__e){e.__e=e.__c.base=n.__e;break}return ze(e)}}function Ge(e){(!e.__d&&(e.__d=!0)&&Fe.push(e)&&!Je.__r++||Re!==Ne.debounceRendering)&&((Re=Ne.debounceRendering)||Le)(Je)}function Je(){for(var e;Je.__r=Fe.length;)e=Fe.sort((function(e,t){return e.__v.__b-t.__v.__b})),Fe=[],e.some((function(e){var t,n,r,o,i,u;e.__d&&(i=(o=(t=e).__v).__e,(u=t.__P)&&(n=[],(r=Ue({},o)).__v=o.__v+1,rt(u,o,r,t.__n,void 0!==u.ownerSVGElement,null!=o.__h?[i]:null,n,null==i?$e(o):i,o.__h),ot(n,o),o.__e!=i&&ze(o)))}))}function Ke(e,t,n,r,o,i,u,a,c,l){var s,p,f,d,m,v,h,y=r&&r.__k||Te,g=y.length;for(n.__k=[],s=0;s<t.length;s++)if(null!=(d=n.__k[s]=null==(d=t[s])||"boolean"==typeof d?null:"string"==typeof d||"number"==typeof d||"bigint"==typeof d?Ve(null,d,null,null,d):Array.isArray(d)?Ve(We,{children:d},null,null,null):d.__b>0?Ve(d.type,d.props,d.key,null,d.__v):d)){if(d.__=n,d.__b=n.__b+1,null===(f=y[s])||f&&d.key==f.key&&d.type===f.type)y[s]=void 0;else for(p=0;p<g;p++){if((f=y[p])&&d.key==f.key&&d.type===f.type){y[p]=void 0;break}f=null}rt(e,d,f=f||qe,o,i,u,a,c,l),m=d.__e,(p=d.ref)&&f.ref!=p&&(h||(h=[]),f.ref&&h.push(f.ref,null,d),h.push(p,d.__c||m,d)),null!=m?(null==v&&(v=m),"function"==typeof d.type&&null!=d.__k&&d.__k===f.__k?d.__d=c=Xe(d,c,e):c=Ye(e,d,f,y,m,c),l||"option"!==n.type?"function"==typeof n.type&&(n.__d=c):e.value=""):c&&f.__e==c&&c.parentNode!=e&&(c=$e(f))}for(n.__e=v,s=g;s--;)null!=y[s]&&("function"==typeof n.type&&null!=y[s].__e&&y[s].__e==n.__d&&(n.__d=$e(r,s+1)),at(y[s],y[s]));if(h)for(s=0;s<h.length;s++)ut(h[s],h[++s],h[++s])}function Xe(e,t,n){var r,o;for(r=0;r<e.__k.length;r++)(o=e.__k[r])&&(o.__=e,t="function"==typeof o.type?Xe(o,t,n):Ye(n,o,o,e.__k,o.__e,t));return t}function Ye(e,t,n,r,o,i){var u,a,c;if(void 0!==t.__d)u=t.__d,t.__d=void 0;else if(null==n||o!=i||null==o.parentNode)e:if(null==i||i.parentNode!==e)e.appendChild(o),u=null;else{for(a=i,c=0;(a=a.nextSibling)&&c<r.length;c+=2)if(a==o)break e;e.insertBefore(o,i),u=i}return void 0!==u?u:o.nextSibling}function Ze(e,t,n){"-"===t[0]?e.setProperty(t,n):e[t]=null==n?"":"number"!=typeof n||Be.test(t)?n:n+"px"}function et(e,t,n,r,o){var i;e:if("style"===t)if("string"==typeof n)e.style.cssText=n;else{if("string"==typeof r&&(e.style.cssText=r=""),r)for(t in r)n&&t in n||Ze(e.style,t,"");if(n)for(t in n)r&&n[t]===r[t]||Ze(e.style,t,n[t])}else if("o"===t[0]&&"n"===t[1])i=t!==(t=t.replace(/Capture$/,"")),t=t.toLowerCase()in e?t.toLowerCase().slice(2):t.slice(2),e.l||(e.l={}),e.l[t+i]=n,n?r||e.addEventListener(t,i?nt:tt,i):e.removeEventListener(t,i?nt:tt,i);else if("dangerouslySetInnerHTML"!==t){if(o)t=t.replace(/xlink[H:h]/,"h").replace(/sName$/,"s");else if("href"!==t&&"list"!==t&&"form"!==t&&"tabIndex"!==t&&"download"!==t&&t in e)try{e[t]=null==n?"":n;break e}catch(e){}"function"==typeof n||(null!=n&&(!1!==n||"a"===t[0]&&"r"===t[1])?e.setAttribute(t,n):e.removeAttribute(t))}}function tt(e){this.l[e.type+!1](Ne.event?Ne.event(e):e)}function nt(e){this.l[e.type+!0](Ne.event?Ne.event(e):e)}function rt(e,t,n,r,o,i,u,a,c){var l,s,p,f,d,m,v,h,y,g,b,_=t.type;if(void 0!==t.constructor)return null;null!=n.__h&&(c=n.__h,a=t.__e=n.__e,t.__h=null,i=[a]),(l=Ne.__b)&&l(t);try{e:if("function"==typeof _){if(h=t.props,y=(l=_.contextType)&&r[l.__c],g=l?y?y.props.value:l.__:r,n.__c?v=(s=t.__c=n.__c).__=s.__E:("prototype"in _&&_.prototype.render?t.__c=s=new _(h,g):(t.__c=s=new Qe(h,g),s.constructor=_,s.render=ct),y&&y.sub(s),s.props=h,s.state||(s.state={}),s.context=g,s.__n=r,p=s.__d=!0,s.__h=[]),null==s.__s&&(s.__s=s.state),null!=_.getDerivedStateFromProps&&(s.__s==s.state&&(s.__s=Ue({},s.__s)),Ue(s.__s,_.getDerivedStateFromProps(h,s.__s))),f=s.props,d=s.state,p)null==_.getDerivedStateFromProps&&null!=s.componentWillMount&&s.componentWillMount(),null!=s.componentDidMount&&s.__h.push(s.componentDidMount);else{if(null==_.getDerivedStateFromProps&&h!==f&&null!=s.componentWillReceiveProps&&s.componentWillReceiveProps(h,g),!s.__e&&null!=s.shouldComponentUpdate&&!1===s.shouldComponentUpdate(h,s.__s,g)||t.__v===n.__v){s.props=h,s.state=s.__s,t.__v!==n.__v&&(s.__d=!1),s.__v=t,t.__e=n.__e,t.__k=n.__k,t.__k.forEach((function(e){e&&(e.__=t)})),s.__h.length&&u.push(s);break e}null!=s.componentWillUpdate&&s.componentWillUpdate(h,s.__s,g),null!=s.componentDidUpdate&&s.__h.push((function(){s.componentDidUpdate(f,d,m)}))}s.context=g,s.props=h,s.state=s.__s,(l=Ne.__r)&&l(t),s.__d=!1,s.__v=t,s.__P=e,l=s.render(s.props,s.state,s.context),s.state=s.__s,null!=s.getChildContext&&(r=Ue(Ue({},r),s.getChildContext())),p||null==s.getSnapshotBeforeUpdate||(m=s.getSnapshotBeforeUpdate(f,d)),b=null!=l&&l.type===We&&null==l.key?l.props.children:l,Ke(e,Array.isArray(b)?b:[b],t,n,r,o,i,u,a,c),s.base=t.__e,t.__h=null,s.__h.length&&u.push(s),v&&(s.__E=s.__=null),s.__e=!1}else null==i&&t.__v===n.__v?(t.__k=n.__k,t.__e=n.__e):t.__e=it(n.__e,t,n,r,o,i,u,c);(l=Ne.diffed)&&l(t)}catch(e){t.__v=null,(c||null!=i)&&(t.__e=a,t.__h=!!c,i[i.indexOf(a)]=null),Ne.__e(e,t,n)}}function ot(e,t){Ne.__c&&Ne.__c(t,e),e.some((function(t){try{e=t.__h,t.__h=[],e.some((function(e){e.call(t)}))}catch(e){Ne.__e(e,t.__v)}}))}function it(e,t,n,r,o,i,u,a){var c,l,s,p,f=n.props,d=t.props,m=t.type,v=0;if("svg"===m&&(o=!0),null!=i)for(;v<i.length;v++)if((c=i[v])&&(c===e||(m?c.localName==m:3==c.nodeType))){e=c,i[v]=null;break}if(null==e){if(null===m)return document.createTextNode(d);e=o?document.createElementNS("http://www.w3.org/2000/svg",m):document.createElement(m,d.is&&d),i=null,a=!1}if(null===m)f===d||a&&e.data===d||(e.data=d);else{if(i=i&&Te.slice.call(e.childNodes),l=(f=n.props||qe).dangerouslySetInnerHTML,s=d.dangerouslySetInnerHTML,!a){if(null!=i)for(f={},p=0;p<e.attributes.length;p++)f[e.attributes[p].name]=e.attributes[p].value;(s||l)&&(s&&(l&&s.__html==l.__html||s.__html===e.innerHTML)||(e.innerHTML=s&&s.__html||""))}if(function(e,t,n,r,o){var i;for(i in n)"children"===i||"key"===i||i in t||et(e,i,null,n[i],r);for(i in t)o&&"function"!=typeof t[i]||"children"===i||"key"===i||"value"===i||"checked"===i||n[i]===t[i]||et(e,i,t[i],n[i],r)}(e,d,f,o,a),s)t.__k=[];else if(v=t.props.children,Ke(e,Array.isArray(v)?v:[v],t,n,r,o&&"foreignObject"!==m,i,u,e.firstChild,a),null!=i)for(v=i.length;v--;)null!=i[v]&&Me(i[v]);a||("value"in d&&void 0!==(v=d.value)&&(v!==e.value||"progress"===m&&!v)&&et(e,"value",v,f.value,!1),"checked"in d&&void 0!==(v=d.checked)&&v!==e.checked&&et(e,"checked",v,f.checked,!1))}return e}function ut(e,t,n){try{"function"==typeof e?e(t):e.current=t}catch(e){Ne.__e(e,n)}}function at(e,t,n){var r,o,i;if(Ne.unmount&&Ne.unmount(e),(r=e.ref)&&(r.current&&r.current!==e.__e||ut(r,null,t)),n||"function"==typeof e.type||(n=null!=(o=e.__e)),e.__e=e.__d=void 0,null!=(r=e.__c)){if(r.componentWillUnmount)try{r.componentWillUnmount()}catch(e){Ne.__e(e,t)}r.base=r.__P=null}if(r=e.__k)for(i=0;i<r.length;i++)r[i]&&at(r[i],t,n);null!=o&&Me(o)}function ct(e,t,n){return this.constructor(e,n)}Ne={__e:function(e,t){for(var n,r,o;t=t.__;)if((n=t.__c)&&!n.__)try{if((r=n.constructor)&&null!=r.getDerivedStateFromError&&(n.setState(r.getDerivedStateFromError(e)),o=n.__d),null!=n.componentDidCatch&&(n.componentDidCatch(e),o=n.__d),o)return n.__E=n}catch(t){e=t}throw e},__v:0},Qe.prototype.setState=function(e,t){var n;n=null!=this.__s&&this.__s!==this.state?this.__s:this.__s=Ue({},this.state),"function"==typeof e&&(e=e(Ue({},n),this.props)),e&&Ue(n,e),null!=e&&this.__v&&(t&&this.__h.push(t),Ge(this))},Qe.prototype.forceUpdate=function(e){this.__v&&(this.__e=!0,e&&this.__h.push(e),Ge(this))},Qe.prototype.render=We,Fe=[],Le="function"==typeof Promise?Promise.prototype.then.bind(Promise.resolve()):setTimeout,Je.__r=0;var lt="__aa-highlight__",st="__/aa-highlight__";function pt(e){var t=e.highlightedValue.split(lt),n=t.shift(),r=function(){var e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:[];return{get:function(){return e},add:function(t){var n=e[e.length-1];(null==n?void 0:n.isHighlighted)===t.isHighlighted?e[e.length-1]={value:n.value+t.value,isHighlighted:n.isHighlighted}:e.push(t)}}}(n?[{value:n,isHighlighted:!1}]:[]);return t.forEach((function(e){var t=e.split(st);r.add({value:t[0],isHighlighted:!0}),""!==t[1]&&r.add({value:t[1],isHighlighted:!1})})),r.get()}function ft(e){return function(e){if(Array.isArray(e))return dt(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return dt(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return dt(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function dt(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function mt(e){var t=e.hit,n=e.attribute,r=Array.isArray(n)?n:[n],o=d(t,["_highlightResult"].concat(ft(r),["value"]));return"string"!=typeof o&&(o=d(t,r)||""),pt({highlightedValue:o})}var vt={"&amp;":"&","&lt;":"<","&gt;":">","&quot;":'"',"&#39;":"'"},ht=new RegExp(/\w/i),yt=/&(amp|quot|lt|gt|#39);/g,gt=RegExp(yt.source);function bt(e,t){var n,r,o,i=e[t],u=(null===(n=e[t+1])||void 0===n?void 0:n.isHighlighted)||!0,a=(null===(r=e[t-1])||void 0===r?void 0:r.isHighlighted)||!0;return ht.test((o=i.value)&&gt.test(o)?o.replace(yt,(function(e){return vt[e]})):o)||a!==u?i.isHighlighted:a}function _t(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function Ot(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?_t(Object(n),!0).forEach((function(t){Pt(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):_t(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function Pt(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function St(e){return e.some((function(e){return e.isHighlighted}))?e.map((function(t,n){return Ot(Ot({},t),{},{isHighlighted:!bt(e,n)})})):e.map((function(e){return Ot(Ot({},e),{},{isHighlighted:!1})}))}function jt(e){return function(e){if(Array.isArray(e))return wt(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return wt(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return wt(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function wt(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function It(e){var t=e.hit,n=e.attribute,r=Array.isArray(n)?n:[n],o=d(t,["_snippetResult"].concat(jt(r),["value"]));return"string"!=typeof o&&(o=d(t,r)||""),pt({highlightedValue:o})}function Et(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function At(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?Et(Object(n),!0).forEach((function(t){Ct(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):Et(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function Ct(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}var Dt="1.0.1";function kt(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function xt(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?kt(Object(n),!0).forEach((function(t){Nt(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):kt(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function Nt(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function Ft(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function Lt(e){return function(e){if(Array.isArray(e))return Rt(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return Rt(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return Rt(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function Rt(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function qt(e){var t=e.createElement,n=e.Fragment;return function(e){var r,o=e.hit,i=e.attribute,u=e.tagName,a=void 0===u?"mark":u;return t(n,{},(r={hit:o,attribute:i},St(mt(r))).map((function(e,n){return e.isHighlighted?t(a,{key:n},e.value):e.value})))}}function Tt(e){var t=e.createElement,n=e.Fragment;return function(e){var r,o=e.hit,i=e.attribute,u=e.tagName,a=void 0===u?"mark":u;return t(n,{},(r={hit:o,attribute:i},St(It(r))).map((function(e,n){return e.isHighlighted?t(a,{key:n},e.value):e.value})))}}function Bt(e){var t=e.createElement,n=e.Fragment;return function(e){var r=e.hit,o=e.attribute,i=e.tagName,u=void 0===i?"mark":i;return t(n,{},It({hit:r,attribute:o}).map((function(e,n){return e.isHighlighted?t(u,{key:n},e.value):e.value})))}}var Ut={clearButton:"aa-ClearButton",detachedCancelButton:"aa-DetachedCancelButton",detachedContainer:"aa-DetachedContainer",detachedFormContainer:"aa-DetachedFormContainer",detachedOverlay:"aa-DetachedOverlay",detachedSearchButton:"aa-DetachedSearchButton",detachedSearchButtonIcon:"aa-DetachedSearchButtonIcon",detachedSearchButtonPlaceholder:"aa-DetachedSearchButtonPlaceholder",form:"aa-Form",input:"aa-Input",inputWrapper:"aa-InputWrapper",inputWrapperPrefix:"aa-InputWrapperPrefix",inputWrapperSuffix:"aa-InputWrapperSuffix",item:"aa-Item",label:"aa-Label",list:"aa-List",loadingIndicator:"aa-LoadingIndicator",panel:"aa-Panel",panelLayout:"aa-PanelLayout",root:"aa-Autocomplete",source:"aa-Source",sourceFooter:"aa-SourceFooter",sourceHeader:"aa-SourceHeader",sourceNoResults:"aa-SourceNoResults",submitButton:"aa-SubmitButton"},Mt=function(e,t){!function(e,t,n){var r,o,i;Ne.__&&Ne.__(e,t),o=(r="function"==typeof n)?null:n&&n.__k||t.__k,i=[],rt(t,e=(!r&&n||t).__k=He(We,null,[e]),o||qe,qe,void 0!==t.ownerSVGElement,!r&&n?[n]:o?null:t.firstChild?Te.slice.call(t.childNodes):null,i,!r&&n?n:o?o.__e:t.firstChild,r),ot(i,e)}(e.children,t)},Ht={createElement:He,Fragment:We};function Vt(e){var t=e.panelPlacement,n=e.container,r=e.form,o=e.environment,i=n.getBoundingClientRect(),u=i.top+i.height;switch(t){case"start":return{top:u,left:i.left};case"end":return{top:u,right:o.document.documentElement.clientWidth-(i.left+i.width)};case"full-width":return{top:u,left:0,right:0,width:"unset",maxWidth:"unset"};case"input-wrapper-width":var a=r.getBoundingClientRect();return{top:u,left:a.left,right:o.document.documentElement.clientWidth-(a.left+a.width),width:"unset",maxWidth:"unset"};default:throw new Error("[Autocomplete] The `panelPlacement` value ".concat(JSON.stringify(t)," is not valid."))}}var Wt=function(e){function t(t){return e({searchClient:t.searchClient,queries:t.requests.map((function(e){return e.query}))}).then((function(e){return e.map((function(e,n){var r=t.requests[n];return{items:e,sourceId:r.sourceId,transformResponse:r.transformResponse}}))}))}return function(e){return function(n){return At(At({execute:t},e),n)}}}((function(e){return t=i(i({},e),{},{userAgents:[{segment:"autocomplete-js",version:"1.0.1"}]}),n=t.searchClient,r=t.queries,o=t.userAgents,u=void 0===o?[]:o,"function"==typeof n.addAlgoliaAgent&&[{segment:"autocomplete-core",version:Dt}].concat(Lt(u)).forEach((function(e){var t=e.segment,r=e.version;n.addAlgoliaAgent(t,r)})),n.search(r.map((function(e){var t=e.params;return xt(xt({},Ft(e,["params"])),{},{params:xt({hitsPerPage:5,highlightPreTag:lt,highlightPostTag:st},t)})}))).then((function(e){return e.results}));var t,n,r,o,u}));var Qt=Wt({transformResponse:function(e){return e.hits}});e.autocomplete=function(e){var t,o=function(){var e=[],t=[];function n(n){e.push(n);var r=n();t.push(r)}return{runEffect:n,cleanupEffects:function(){var e=t;t=[],e.forEach((function(e){e()}))},runEffects:function(){var t=e;e=[],t.forEach((function(e){n(e)}))}}}(),a=o.runEffect,c=o.cleanupEffects,p=o.runEffects,d=(t=[],{reactive:function(e){var n=e(),r={_fn:e,_ref:{current:n},get value(){return this._ref.current},set value(e){this._ref.current=e}};return t.push(r),r},runReactives:function(){t.forEach((function(e){e._ref.current=e._fn()}))}}),v=d.reactive,h=d.runReactives,y=l(!1),g=l(e),b=l(void 0),_=v((function(){return function(e){var t,n=e.classNames,r=e.container,o=e.getEnvironmentProps,a=e.getFormProps,c=e.getInputProps,l=e.getItemProps,s=e.getLabelProps,p=e.getListProps,d=e.getPanelProps,m=e.getRootProps,v=e.panelContainer,h=e.panelPlacement,y=e.render,g=e.renderNoResults,b=e.renderer,_=e.detachedMediaQuery,O=e.components,P=u(e,["classNames","container","getEnvironmentProps","getFormProps","getInputProps","getItemProps","getLabelProps","getListProps","getPanelProps","getRootProps","panelContainer","panelPlacement","render","renderNoResults","renderer","detachedMediaQuery","components"]),S="undefined"!=typeof window?window:{},j=be(S,r);j.tagName;var w,I,E,A=null!=b?b:Ht,C={Highlight:(w=A,I=w.createElement,E=w.Fragment,function(e){var t=e.hit,n=e.attribute,r=e.tagName,o=void 0===r?"mark":r;return I(E,{},mt({hit:t,attribute:n}).map((function(e,t){return e.isHighlighted?I(o,{key:t},e.value):e.value})))}),ReverseHighlight:qt(A),ReverseSnippet:Tt(A),Snippet:Bt(A)};return{renderer:{classNames:_e(Ut,null!=n?n:{}),container:j,getEnvironmentProps:null!=o?o:function(e){return e.props},getFormProps:null!=a?a:function(e){return e.props},getInputProps:null!=c?c:function(e){return e.props},getItemProps:null!=l?l:function(e){return e.props},getLabelProps:null!=s?s:function(e){return e.props},getListProps:null!=p?p:function(e){return e.props},getPanelProps:null!=d?d:function(e){return e.props},getRootProps:null!=m?m:function(e){return e.props},panelContainer:v?be(S,v):S.document.body,panelPlacement:null!=h?h:"input-wrapper-width",render:null!=y?y:Mt,renderNoResults:g,renderer:A,detachedMediaQuery:null!=_?_:getComputedStyle(S.document.documentElement).getPropertyValue("--aa-detached-media-query"),components:i(i({},C),O)},core:i(i({},P),{},{id:null!==(t=P.id)&&void 0!==t?t:f(),environment:S})}}(g.current)})),O=v((function(){return _.value.core.environment.matchMedia(_.value.renderer.detachedMediaQuery).matches})),P=v((function(){return ye(i(i({},_.value.core),{},{onStateChange:function(e){var t,n,r;y.current=e.state.collections.some((function(e){return e.source.templates.noResults})),null===(t=b.current)||void 0===t||t.call(b,e),null===(n=(r=_.value.core).onStateChange)||void 0===n||n.call(r,e)},shouldPanelOpen:g.current.shouldPanelOpen||function(e){var t=e.state;if(O.value)return!0;var n=m(t)>0;if(!_.value.core.openOnFocus&&!t.query)return n;var r=Boolean(y.current||_.value.renderer.renderNoResults);return!n&&r||n}}))})),S=l(i({collections:[],completion:null,context:{},isOpen:!1,query:"",activeItemId:null,status:"idle"},_.value.core.initialState)),j={getEnvironmentProps:_.value.renderer.getEnvironmentProps,getFormProps:_.value.renderer.getFormProps,getInputProps:_.value.renderer.getInputProps,getItemProps:_.value.renderer.getItemProps,getLabelProps:_.value.renderer.getLabelProps,getListProps:_.value.renderer.getListProps,getPanelProps:_.value.renderer.getPanelProps,getRootProps:_.value.renderer.getRootProps},w={setActiveItemId:P.value.setActiveItemId,setQuery:P.value.setQuery,setCollections:P.value.setCollections,setIsOpen:P.value.setIsOpen,setStatus:P.value.setStatus,setContext:P.value.setContext,refresh:P.value.refresh},I=v((function(){return xe({autocomplete:P.value,autocompleteScopeApi:w,classNames:_.value.renderer.classNames,environment:_.value.core.environment,isDetached:O.value,placeholder:_.value.core.placeholder,propGetters:j,setIsModalOpen:D,state:S.current})}));function E(){Ee(I.value.panel,{style:O.value?{}:Vt({panelPlacement:_.value.renderer.panelPlacement,container:I.value.root,form:I.value.form,environment:_.value.core.environment})})}function A(e){S.current=e;var t={autocomplete:P.value,autocompleteScopeApi:w,classNames:_.value.renderer.classNames,components:_.value.renderer.components,container:_.value.renderer.container,createElement:_.value.renderer.renderer.createElement,dom:I.value,Fragment:_.value.renderer.renderer.Fragment,panelContainer:O.value?I.value.detachedContainer:_.value.renderer.panelContainer,propGetters:j,state:S.current},n=!m(e)&&!y.current&&_.value.renderer.renderNoResults||_.value.renderer.render;!function(e){var t=e.autocomplete,n=e.autocompleteScopeApi,r=e.dom,o=e.propGetters,u=e.state;Ae(r.root,o.getRootProps(i({state:u,props:t.getRootProps({})},n))),Ae(r.input,o.getInputProps(i({state:u,props:t.getInputProps({inputElement:r.input}),inputElement:r.input},n))),Ee(r.label,{hidden:"stalled"===u.status}),Ee(r.loadingIndicator,{hidden:"stalled"!==u.status}),Ee(r.clearButton,{hidden:!u.query})}(t),function(e,t){var n=t.autocomplete,o=t.autocompleteScopeApi,u=t.classNames,a=t.createElement,c=t.dom,l=t.Fragment,s=t.panelContainer,p=t.propGetters,f=t.state,d=t.components;if(f.isOpen){s.contains(c.panel)||"loading"===f.status||s.appendChild(c.panel),c.panel.classList.toggle("aa-Panel--stalled","stalled"===f.status);var m=f.collections.map((function(e,t){var c=e.source,s=e.items;return a("section",{key:t,className:u.source,"data-autocomplete-source-id":c.sourceId},c.templates.header&&a("div",{className:u.sourceHeader},c.templates.header({components:d,createElement:a,Fragment:l,items:s,source:c,state:f})),c.templates.noResults&&0===s.length?a("div",{className:u.sourceNoResults},c.templates.noResults({components:d,createElement:a,Fragment:l,source:c,state:f})):a("ul",r({className:u.list},p.getListProps(i({state:f,props:n.getListProps({})},o))),s.map((function(e){var t=n.getItemProps({item:e,source:c});return a("li",r({key:t.id,className:u.item},p.getItemProps(i({state:f,props:t},o))),c.templates.item({components:d,createElement:a,Fragment:l,item:e,state:f}))}))),c.templates.footer&&a("div",{className:u.sourceFooter},c.templates.footer({components:d,createElement:a,Fragment:l,items:s,source:c,state:f})))})),v=a(l,null,a("div",{className:"aa-PanelLayout aa-Panel--scrollable"},m),a("div",{className:"aa-GradientBottom"})),h=m.reduce((function(e,t){return e[t.props["data-autocomplete-source-id"]]=t,e}),{});e({children:v,state:f,sections:m,elements:h,createElement:a,Fragment:l,components:d},c.panel)}else s.contains(c.panel)&&s.removeChild(c.panel)}(n,t)}function C(){var e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:{};c(),g.current=Pe(_.value.renderer,_.value.core,{initialState:S.current},e),h(),p(),P.value.refresh().then((function(){A(S.current)}))}function D(e){requestAnimationFrame((function(){var t=_.value.core.environment.document.body.contains(I.value.detachedOverlay);e!==t&&(e?(_.value.core.environment.document.body.appendChild(I.value.detachedOverlay),_.value.core.environment.document.body.classList.add("aa-Detached"),I.value.input.focus()):(_.value.core.environment.document.body.removeChild(I.value.detachedOverlay),_.value.core.environment.document.body.classList.remove("aa-Detached"),P.value.setQuery(""),P.value.refresh()))}))}return a((function(){var e=P.value.getEnvironmentProps({formElement:I.value.form,panelElement:I.value.panel,inputElement:I.value.input});return Ee(_.value.core.environment,e),function(){Ee(_.value.core.environment,Object.keys(e).reduce((function(e,t){return i(i({},e),{},n({},t,void 0))}),{}))}})),a((function(){var e=O.value?_.value.core.environment.document.body:_.value.renderer.panelContainer,t=O.value?I.value.detachedOverlay:I.value.panel;return O.value&&S.current.isOpen&&D(!0),A(S.current),function(){e.contains(t)&&e.removeChild(t)}})),a((function(){var e=_.value.renderer.container;return e.appendChild(I.value.root),function(){e.removeChild(I.value.root)}})),a((function(){var e=s((function(e){A(e.state)}),0);return b.current=function(t){var n=t.state,r=t.prevState;(O.value&&r.isOpen!==n.isOpen&&D(n.isOpen),O.value||!n.isOpen||r.isOpen||E(),n.query!==r.query)&&_.value.core.environment.document.querySelectorAll(".aa-Panel--scrollable").forEach((function(e){0!==e.scrollTop&&(e.scrollTop=0)}));e({state:n})},function(){b.current=void 0}})),a((function(){var e=s((function(){var e=O.value;O.value=_.value.core.environment.matchMedia(_.value.renderer.detachedMediaQuery).matches,e!==O.value?C({}):requestAnimationFrame(E)}),20);return _.value.core.environment.addEventListener("resize",e),function(){_.value.core.environment.removeEventListener("resize",e)}})),a((function(){if(!O.value)return function(){};function e(e){I.value.detachedContainer.classList.toggle("aa-DetachedContainer--modal",e)}function t(t){e(t.matches)}var n=_.value.core.environment.matchMedia(getComputedStyle(_.value.core.environment.document.documentElement).getPropertyValue("--aa-detached-modal-media-query"));return e(n.matches),n.addEventListener("change",t),function(){n.removeEventListener("change",t)}})),a((function(){return requestAnimationFrame(E),function(){}})),i(i({},w),{},{update:C,destroy:function(){c()}})},e.getAlgoliaFacets=function(e){var t=Wt({transformResponse:function(e){return e.facetHits}}),n=e.queries.map((function(e){return i(i({},e),{},{type:"facet"})}));return t(i(i({},e),{},{queries:n}))},e.getAlgoliaResults=Qt,Object.defineProperty(e,"__esModule",{value:!0})}));
+!function(e,t){"object"==typeof exports&&"undefined"!=typeof module?t(exports):"function"==typeof define&&define.amd?define(["exports"],t):t((e="undefined"!=typeof globalThis?globalThis:e||self)["@algolia/autocomplete-js"]={})}(this,(function(e){"use strict";function t(e){return(t="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e})(e)}function n(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function r(){return(r=Object.assign||function(e){for(var t=1;t<arguments.length;t++){var n=arguments[t];for(var r in n)Object.prototype.hasOwnProperty.call(n,r)&&(e[r]=n[r])}return e}).apply(this,arguments)}function o(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function i(e){for(var t=1;t<arguments.length;t++){var r=null!=arguments[t]?arguments[t]:{};t%2?o(Object(r),!0).forEach((function(t){n(e,t,r[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(r)):o(Object(r)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(r,t))}))}return e}function u(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function a(e){return function(e){if(Array.isArray(e))return c(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return c(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return c(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function c(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function l(e){return{current:e}}function s(e,t){var n=void 0;return function(){for(var r=arguments.length,o=new Array(r),i=0;i<r;i++)o[i]=arguments[i];n&&clearTimeout(n),n=setTimeout((function(){return e.apply(void 0,o)}),t)}}var p=0;function f(){return"autocomplete-".concat(p++)}function d(e,t){return t.reduce((function(e,t){return e&&e[t]}),e)}function m(e){return 0===e.collections.length?0:e.collections.reduce((function(e,t){return e+t.items.length}),0)}function v(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function h(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function y(e,t,n){var r=t.initialState;return{getState:function(){return r},dispatch:function(o,i){var u=function(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?v(Object(n),!0).forEach((function(t){h(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):v(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}({},r);r=e(r,{type:o,props:t,payload:i}),n({state:r,prevState:u})}}}function g(e){return e.reduce((function(e,t){return e.concat(t)}),[])}function b(e,t,n,r){if(e<0&&(null===t||null!==r&&0===t))return n+e;var o=(null===t?-1:t)+e;return o<=-1||o>=n?null===r?null:0:o}var _=function(){};function O(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function P(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function S(e){return(S="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e})(e)}function j(e,t){var n=[];return Promise.resolve(e(t)).then((function(e){return Array.isArray(e),"The `getSources` function must return an array of sources but returned type ".concat(JSON.stringify(S(e)),":\n\n").concat(JSON.stringify(e,null,2)),Promise.all(e.filter((function(e){return Boolean(e)})).map((function(e){if(e.sourceId,n.includes(e.sourceId))throw new Error("[Autocomplete] The `sourceId` ".concat(JSON.stringify(e.sourceId)," is not unique."));n.push(e.sourceId);var t=function(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?O(Object(n),!0).forEach((function(t){P(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):O(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}({getItemInputValue:function(e){return e.state.query},getItemUrl:function(){},onSelect:function(e){(0,e.setIsOpen)(!1)},onActive:_},e);return Promise.resolve(t)})))}))}function w(e){var t=function(e){var t=e.collections.map((function(e){return e.items.length})).reduce((function(e,t,n){var r=(e[n-1]||0)+t;return e.push(r),e}),[]).reduce((function(t,n){return n<=e.activeItemId?t+1:t}),0);return e.collections[t]}(e);if(!t)return null;var n=t.items[function(e){for(var t=e.state,n=e.collection,r=!1,o=0,i=0;!1===r;){var u=t.collections[o];if(u===n){r=!0;break}i+=u.items.length,o++}return t.activeItemId-i}({state:e,collection:t})],r=t.source;return{item:n,itemInputValue:r.getItemInputValue({item:n,state:e}),itemUrl:r.getItemUrl({item:n,state:e}),source:r}}function I(e,t){return e===t||e.contains(t)}function E(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function A(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?E(Object(n),!0).forEach((function(t){C(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):E(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function C(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function D(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function k(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?D(Object(n),!0).forEach((function(t){x(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):D(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function x(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function N(e){return function(e){if(Array.isArray(e))return F(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return F(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return F(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function F(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function L(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function R(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?L(Object(n),!0).forEach((function(t){q(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):L(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function q(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function T(e){return(T="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e})(e)}function B(e){return function(e){if(Array.isArray(e))return U(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return U(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return U(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function U(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function M(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function H(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?M(Object(n),!0).forEach((function(t){V(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):M(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function V(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function W(e){return Boolean(e.execute)}function Q(e,t){return Boolean(e.execute)?H(H({},e),{},{requests:e.queries.map((function(n){return{query:n,sourceId:t,transformResponse:e.transformResponse}}))}):{items:e,sourceId:t}}function $(e){var t=e.reduce((function(e,t){if(!W(t))return e.push(t),e;var n=t.searchClient,r=t.execute,o=t.requests,i=e.find((function(e){return W(t)&&W(e)&&e.searchClient===n&&e.execute===r}));if(i){var u;(u=i.items).push.apply(u,B(o))}else{var a={execute:r,items:o,searchClient:n};e.push(a)}return e}),[]).map((function(e){if(!W(e))return Promise.resolve(e);var t=e,n=t.execute,r=t.items;return n({searchClient:t.searchClient,requests:r})}));return Promise.all(t).then((function(e){return g(e)}))}function z(e,t){return t.map((function(t){var n=e.filter((function(e){return e.sourceId===t.sourceId})),r=n.map((function(e){return e.items})),o=n[0].transformResponse,i=o?o(function(e){var t=e.map((function(e){var t;return A(A({},e),{},{hits:null===(t=e.hits)||void 0===t?void 0:t.map((function(t){return A(A({},t),{},{__autocomplete_indexName:e.index,__autocomplete_queryID:e.queryID})}))})}));return{results:t,hits:t.map((function(e){return e.hits})).filter(Boolean),facetHits:t.map((function(e){var t;return null===(t=e.facetHits)||void 0===t?void 0:t.map((function(e){return{label:e.value,count:e.count,_highlightResult:{label:{value:e.highlighted}}}}))})).filter(Boolean)}}(r)):r;return Array.isArray(i),"The `getItems` function must return an array of items but returned type ".concat(JSON.stringify(T(i)),":\n\n").concat(JSON.stringify(i,null,2)),{source:t,items:i}}))}function G(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function J(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?G(Object(n),!0).forEach((function(t){K(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):G(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function K(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function X(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}var Y=null;function Z(e){var t=e.event,n=e.nextState,r=void 0===n?{}:n,o=e.props,i=e.query,u=e.refresh,a=e.store,c=X(e,["event","nextState","props","query","refresh","store"]);Y&&o.environment.clearTimeout(Y);var l,s=c.setCollections,p=c.setIsOpen,f=c.setQuery,d=c.setActiveItemId,m=c.setStatus;return f(i),d(o.defaultActiveItemId),i||!1!==o.openOnFocus?(m("loading"),Y=o.environment.setTimeout((function(){m("stalled")}),o.stallThreshold),o.getSources(J({query:i,refresh:u,state:a.getState()},c)).then((function(e){return m("loading"),Promise.all(e.map((function(e){return Promise.resolve(e.getItems(J({query:i,refresh:u,state:a.getState()},c))).then((function(t){return Q(t,e.sourceId)}))}))).then($).then((function(t){return z(t,e)})).then((function(e){var n;m("idle"),s(e);var l=o.shouldPanelOpen({state:a.getState()});p(null!==(n=r.isOpen)&&void 0!==n?n:o.openOnFocus&&!i&&l||l);var f=w(a.getState());if(null!==a.getState().activeItemId&&f){var d=f.item,v=f.itemInputValue,h=f.itemUrl,y=f.source;y.onActive(J({event:t,item:d,itemInputValue:v,itemUrl:h,refresh:u,source:y,state:a.getState()},c))}})).finally((function(){Y&&o.environment.clearTimeout(Y)}))}))):(m("idle"),s(a.getState().collections.map((function(e){return J(J({},e),{},{items:[]})}))),p(null!==(l=r.isOpen)&&void 0!==l?l:o.shouldPanelOpen({state:a.getState()})),Promise.resolve())}function ee(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function te(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?ee(Object(n),!0).forEach((function(t){ne(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):ee(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function ne(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function re(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function oe(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function ie(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?oe(Object(n),!0).forEach((function(t){ue(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):oe(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function ue(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function ae(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function ce(e){var t=e.props,n=e.refresh,r=e.store,o=ae(e,["props","refresh","store"]);return{getEnvironmentProps:function(e){var n=e.inputElement,o=e.formElement,i=e.panelElement;return ie({onTouchStart:function(e){!1!==r.getState().isOpen&&e.target!==n&&(!1===[o,i].some((function(n){return I(n,e.target)||I(n,t.environment.document.activeElement)}))&&r.dispatch("blur",null))},onTouchMove:function(e){!1!==r.getState().isOpen&&n===t.environment.document.activeElement&&e.target!==n&&n.blur()}},ae(e,["inputElement","formElement","panelElement"]))},getRootProps:function(e){return ie({"aria-label":"aa-header-search","aria-haspopup":"listbox","aria-owns":r.getState().isOpen?"".concat(t.id,"-list"):void 0,"aria-labelledby":"".concat(t.id,"-label")},e)},getFormProps:function(e){e.inputElement;return ie({action:"",noValidate:!0,role:"search",onSubmit:function(i){var u;i.preventDefault(),t.onSubmit(ie({event:i,refresh:n,state:r.getState()},o)),r.dispatch("submit",null),null===(u=e.inputElement)||void 0===u||u.blur()},onReset:function(i){var u;i.preventDefault(),t.onReset(ie({event:i,refresh:n,state:r.getState()},o)),r.dispatch("reset",null),null===(u=e.inputElement)||void 0===u||u.focus()}},ae(e,["inputElement"]))},getLabelProps:function(e){return ie({htmlFor:"".concat(t.id,"-input"),id:"".concat(t.id,"-label")},e)},getInputProps:function(e){function i(e){(t.openOnFocus||Boolean(r.getState().query))&&Z(ie({event:e,props:t,query:r.getState().completion||r.getState().query,refresh:n,store:r},o)),r.dispatch("focus",null)}var u="ontouchstart"in t.environment,a=e||{},c=(a.inputElement,a.maxLength),l=void 0===c?512:c,s=ae(a,["inputElement","maxLength"]),p=w(r.getState());return ie({"aria-autocomplete":"both","aria-activedescendant":r.getState().isOpen&&null!==r.getState().activeItemId?"".concat(t.id,"-item-").concat(r.getState().activeItemId):void 0,"aria-controls":r.getState().isOpen?"".concat(t.id,"-list"):void 0,"aria-labelledby":"".concat(t.id,"-label"),value:r.getState().completion||r.getState().query,id:"".concat(t.id,"-input"),autoComplete:"off",autoCorrect:"off",autoCapitalize:"off",enterKeyHint:null!=p&&p.itemUrl?"go":"search",spellCheck:"false",autoFocus:t.autoFocus,placeholder:t.placeholder,maxLength:l,type:"search",onChange:function(e){Z(ie({event:e,props:t,query:e.currentTarget.value.slice(0,l),refresh:n,store:r},o))},onKeyDown:function(e){!function(e){var t=e.event,n=e.props,r=e.refresh,o=e.store,i=re(e,["event","props","refresh","store"]);if("ArrowUp"===t.key||"ArrowDown"===t.key){t.preventDefault(),o.dispatch(t.key,null);var u=n.environment.document.getElementById("".concat(n.id,"-item-").concat(o.getState().activeItemId));u&&(u.scrollIntoViewIfNeeded?u.scrollIntoViewIfNeeded(!1):u.scrollIntoView(!1));var a=w(o.getState());if(null!==o.getState().activeItemId&&a){var c=a.item,l=a.itemInputValue,s=a.itemUrl,p=a.source;p.onActive(te({event:t,item:c,itemInputValue:l,itemUrl:s,refresh:r,source:p,state:o.getState()},i))}}else if("Escape"===t.key)t.preventDefault(),o.dispatch(t.key,null);else if("Enter"===t.key){if(null===o.getState().activeItemId||o.getState().collections.every((function(e){return 0===e.items.length})))return;t.preventDefault();var f=w(o.getState()),d=f.item,m=f.itemInputValue,v=f.itemUrl,h=f.source;if(t.metaKey||t.ctrlKey)void 0!==v&&(h.onSelect(te({event:t,item:d,itemInputValue:m,itemUrl:v,refresh:r,source:h,state:o.getState()},i)),n.navigator.navigateNewTab({itemUrl:v,item:d,state:o.getState()}));else if(t.shiftKey)void 0!==v&&(h.onSelect(te({event:t,item:d,itemInputValue:m,itemUrl:v,refresh:r,source:h,state:o.getState()},i)),n.navigator.navigateNewWindow({itemUrl:v,item:d,state:o.getState()}));else if(t.altKey);else{if(void 0!==v)return h.onSelect(te({event:t,item:d,itemInputValue:m,itemUrl:v,refresh:r,source:h,state:o.getState()},i)),void n.navigator.navigate({itemUrl:v,item:d,state:o.getState()});Z(te({event:t,nextState:{isOpen:!1},props:n,query:m,refresh:r,store:o},i)).then((function(){h.onSelect(te({event:t,item:d,itemInputValue:m,itemUrl:v,refresh:r,source:h,state:o.getState()},i))}))}}}(ie({event:e,props:t,refresh:n,store:r},o))},onFocus:i,onBlur:function(){u||r.dispatch("blur",null)},onClick:function(n){e.inputElement!==t.environment.document.activeElement||r.getState().isOpen||i(n)}},s)},getPanelProps:function(e){return ie({onMouseDown:function(e){e.preventDefault()},onMouseLeave:function(){r.dispatch("mouseleave",null)}},e)},getListProps:function(e){return ie({role:"listbox","aria-labelledby":"".concat(t.id,"-label"),id:"".concat(t.id,"-list")},e)},getItemProps:function(e){var i=e.item,u=e.source,a=ae(e,["item","source"]);return ie({id:"".concat(t.id,"-item-").concat(i.__autocomplete_id),role:"option","aria-selected":r.getState().activeItemId===i.__autocomplete_id,onMouseMove:function(e){if(i.__autocomplete_id!==r.getState().activeItemId){r.dispatch("mousemove",i.__autocomplete_id);var t=w(r.getState());if(null!==r.getState().activeItemId&&t){var u=t.item,a=t.itemInputValue,c=t.itemUrl,l=t.source;l.onActive(ie({event:e,item:u,itemInputValue:a,itemUrl:c,refresh:n,source:l,state:r.getState()},o))}}},onMouseDown:function(e){e.preventDefault()},onClick:function(e){var a=u.getItemInputValue({item:i,state:r.getState()}),c=u.getItemUrl({item:i,state:r.getState()});(c?Promise.resolve():Z(ie({event:e,nextState:{isOpen:!1},props:t,query:a,refresh:n,store:r},o))).then((function(){u.onSelect(ie({event:e,item:i,itemInputValue:a,itemUrl:c,refresh:n,source:u,state:r.getState()},o))}))}},a)}}}function le(e){var t=e.state;return!1===t.isOpen||null===t.activeItemId?null:w(t).itemInputValue||null}function se(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function pe(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?se(Object(n),!0).forEach((function(t){fe(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):se(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function fe(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}var de=function(e,t){switch(t.type){case"setActiveItemId":return pe(pe({},e),{},{activeItemId:t.payload});case"setQuery":return pe(pe({},e),{},{query:t.payload,completion:null});case"setCollections":return pe(pe({},e),{},{collections:t.payload});case"setIsOpen":return pe(pe({},e),{},{isOpen:t.payload});case"setStatus":return pe(pe({},e),{},{status:t.payload});case"setContext":return pe(pe({},e),{},{context:pe(pe({},e.context),t.payload)});case"ArrowDown":var n=pe(pe({},e),{},{activeItemId:b(1,e.activeItemId,m(e),t.props.defaultActiveItemId)});return pe(pe({},n),{},{completion:le({state:n})});case"ArrowUp":var r=pe(pe({},e),{},{activeItemId:b(-1,e.activeItemId,m(e),t.props.defaultActiveItemId)});return pe(pe({},r),{},{completion:le({state:r})});case"Escape":return e.isOpen?pe(pe({},e),{},{isOpen:!1,completion:null}):pe(pe({},e),{},{query:"",status:"idle",collections:[]});case"submit":return pe(pe({},e),{},{activeItemId:null,isOpen:!1,status:"idle"});case"reset":return pe(pe({},e),{},{activeItemId:!0===t.props.openOnFocus?t.props.defaultActiveItemId:null,status:"idle",query:""});case"focus":return pe(pe({},e),{},{activeItemId:t.props.defaultActiveItemId,isOpen:(t.props.openOnFocus||Boolean(e.query))&&t.props.shouldPanelOpen({state:e})});case"blur":return t.props.debug?e:pe(pe({},e),{},{isOpen:!1,activeItemId:null});case"mousemove":return pe(pe({},e),{},{activeItemId:t.payload});case"mouseleave":return pe(pe({},e),{},{activeItemId:t.props.defaultActiveItemId});default:return"The reducer action ".concat(JSON.stringify(t.type)," is not supported."),e}};function me(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function ve(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?me(Object(n),!0).forEach((function(t){he(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):me(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function he(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function ye(e){var t=[],n=function(e,t){var n,r="undefined"!=typeof window?window:{},o=e.plugins||[];return R(R({debug:!1,openOnFocus:!1,placeholder:"",autoFocus:!1,defaultActiveItemId:null,stallThreshold:300,environment:r,shouldPanelOpen:function(e){return m(e.state)>0}},e),{},{id:null!==(n=e.id)&&void 0!==n?n:f(),plugins:o,initialState:R({activeItemId:null,query:"",completion:null,collections:[],isOpen:!1,status:"idle",context:{}},e.initialState),onStateChange:function(t){var n;null===(n=e.onStateChange)||void 0===n||n.call(e,t),o.forEach((function(e){var n;return null===(n=e.onStateChange)||void 0===n?void 0:n.call(e,t)}))},onSubmit:function(t){var n;null===(n=e.onSubmit)||void 0===n||n.call(e,t),o.forEach((function(e){var n;return null===(n=e.onSubmit)||void 0===n?void 0:n.call(e,t)}))},onReset:function(t){var n;null===(n=e.onReset)||void 0===n||n.call(e,t),o.forEach((function(e){var n;return null===(n=e.onReset)||void 0===n?void 0:n.call(e,t)}))},getSources:function(n){return Promise.all([].concat(N(o.map((function(e){return e.getSources}))),[e.getSources]).filter(Boolean).map((function(e){return j(e,n)}))).then((function(e){return g(e)})).then((function(e){return e.map((function(e){return R(R({},e),{},{onSelect:function(n){e.onSelect(n),t.forEach((function(e){var t;return null===(t=e.onSelect)||void 0===t?void 0:t.call(e,n)}))},onActive:function(n){e.onActive(n),t.forEach((function(e){var t;return null===(t=e.onActive)||void 0===t?void 0:t.call(e,n)}))}})}))}))},navigator:R({navigate:function(e){var t=e.itemUrl;r.location.assign(t)},navigateNewTab:function(e){var t=e.itemUrl,n=r.open(t,"_blank","noopener");null==n||n.focus()},navigateNewWindow:function(e){var t=e.itemUrl;r.open(t,"_blank","noopener")}},e.navigator)})}(e,t),r=y(de,n,(function(e){var t=e.prevState,r=e.state;n.onStateChange(ve({prevState:t,state:r,refresh:u},o))})),o=function(e){var t=e.store;return{setActiveItemId:function(e){t.dispatch("setActiveItemId",e)},setQuery:function(e){t.dispatch("setQuery",e)},setCollections:function(e){var n=0,r=e.map((function(e){return k(k({},e),{},{items:g(e.items).map((function(e){return k(k({},e),{},{__autocomplete_id:n++})}))})}));t.dispatch("setCollections",r)},setIsOpen:function(e){t.dispatch("setIsOpen",e)},setStatus:function(e){t.dispatch("setStatus",e)},setContext:function(e){t.dispatch("setContext",e)}}}({store:r}),i=ce(ve({props:n,refresh:u,store:r},o));function u(){return Z(ve({event:new Event("input"),nextState:{isOpen:r.getState().isOpen},props:n,query:r.getState().query,refresh:u,store:r},o))}return n.plugins.forEach((function(e){var n;return null===(n=e.subscribe)||void 0===n?void 0:n.call(e,ve(ve({},o),{},{refresh:u,onSelect:function(e){t.push({onSelect:e})},onActive:function(e){t.push({onActive:e})}}))})),ve(ve({refresh:u},i),o)}var ge=function(e){var t=e.environment,n=t.document.createElementNS("http://www.w3.org/2000/svg","svg");n.setAttribute("class","aa-ClearIcon"),n.setAttribute("viewBox","0 0 24 24"),n.setAttribute("width","18"),n.setAttribute("height","18"),n.setAttribute("fill","currentColor");var r=t.document.createElementNS("http://www.w3.org/2000/svg","path");return r.setAttribute("d","M5.293 6.707l5.293 5.293-5.293 5.293c-0.391 0.391-0.391 1.024 0 1.414s1.024 0.391 1.414 0l5.293-5.293 5.293 5.293c0.391 0.391 1.024 0.391 1.414 0s0.391-1.024 0-1.414l-5.293-5.293 5.293-5.293c0.391-0.391 0.391-1.024 0-1.414s-1.024-0.391-1.414 0l-5.293 5.293-5.293-5.293c-0.391-0.391-1.024-0.391-1.414 0s-0.391 1.024 0 1.414z"),n.appendChild(r),n};function be(e,t){if("string"==typeof t){var n=e.document.querySelector(t);return"The element ".concat(JSON.stringify(t)," is not in the document."),n}return t}function _e(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];return t.reduce((function(e,t){return Object.keys(t).forEach((function(n){var r=e[n],o=t[n];r!==o&&(e[n]=[r,o].filter(Boolean).join(" "))})),e}),{})}var Oe=function(e){return e&&"object"===t(e)};function Pe(){for(var e=arguments.length,t=new Array(e),n=0;n<e;n++)t[n]=arguments[n];return t.reduce((function(e,t){return Object.keys(t).forEach((function(n){var r=e[n],o=t[n];Array.isArray(r)&&Array.isArray(o)?e[n]=r.concat.apply(r,a(o)):Oe(r)&&Oe(o)?e[n]=Pe(r,o):e[n]=o})),e}),{})}function Se(e,t,n){e[t]=null===n?"":"number"!=typeof n?n:n+"px"}function je(e){this._listeners[e.type](e)}function we(e,t,n){var r,o,i=e[t];if("style"===t)if("string"==typeof n)e.style=n;else if(null===n)e.style="";else for(t in n)i&&n[t]===i[t]||Se(e.style,t,n[t]);else"o"===t[0]&&"n"===t[1]?(r=t!==(t=t.replace(/Capture$/,"")),(o=t.toLowerCase())in e&&(t=o),t=t.slice(2),e._listeners||(e._listeners={}),e._listeners[t]=n,n?i||e.addEventListener(t,je,r):e.removeEventListener(t,je,r)):"list"!==t&&"tagName"!==t&&"form"!==t&&"type"!==t&&"size"!==t&&"download"!==t&&"href"!==t&&t in e?e[t]=null==n?"":n:"function"!=typeof n&&"dangerouslySetInnerHTML"!==t&&(null==n||!1===n&&!/^ar/.test(t)?e.removeAttribute(t):e.setAttribute(t,n))}function Ie(e){switch(e){case"onChange":return"onInput";default:return e}}function Ee(e,t){for(var n in t)we(e,Ie(n),t[n])}function Ae(e,t){for(var n in t)"o"===n[0]&&"n"===n[1]||we(e,Ie(n),t[n])}function Ce(e){return function(t,n){var r=n.children,o=void 0===r?[]:r,i=u(n,["children"]),c=e.document.createElement(t);return Ee(c,i),c.append.apply(c,a(o)),c}}var De=function(e){var t=e.environment.document.createElementNS("http://www.w3.org/2000/svg","svg");return t.setAttribute("class","aa-LoadingIcon"),t.setAttribute("viewBox","0 0 100 100"),t.setAttribute("width","20"),t.setAttribute("height","20"),t.innerHTML='<circle\n  cx="50"\n  cy="50"\n  fill="none"\n  r="35"\n  stroke="currentColor"\n  stroke-dasharray="164.93361431346415 56.97787143782138"\n  stroke-width="6"\n>\n  <animateTransform\n    attributeName="transform"\n    type="rotate"\n    repeatCount="indefinite"\n    dur="1s"\n    values="0 50 50;90 50 50;180 50 50;360 50 50"\n    keyTimes="0;0.40;0.65;1"\n  />\n</circle>',t},ke=function(e){var t=e.environment,n=t.document.createElementNS("http://www.w3.org/2000/svg","svg");n.setAttribute("class","aa-SubmitIcon"),n.setAttribute("viewBox","0 0 24 24"),n.setAttribute("width","20"),n.setAttribute("height","20"),n.setAttribute("fill","currentColor");var r=t.document.createElementNS("http://www.w3.org/2000/svg","path");return r.setAttribute("d","M16.041 15.856c-0.034 0.026-0.067 0.055-0.099 0.087s-0.060 0.064-0.087 0.099c-1.258 1.213-2.969 1.958-4.855 1.958-1.933 0-3.682-0.782-4.95-2.050s-2.050-3.017-2.050-4.95 0.782-3.682 2.050-4.95 3.017-2.050 4.95-2.050 3.682 0.782 4.95 2.050 2.050 3.017 2.050 4.95c0 1.886-0.745 3.597-1.959 4.856zM21.707 20.293l-3.675-3.675c1.231-1.54 1.968-3.493 1.968-5.618 0-2.485-1.008-4.736-2.636-6.364s-3.879-2.636-6.364-2.636-4.736 1.008-6.364 2.636-2.636 3.879-2.636 6.364 1.008 4.736 2.636 6.364 3.879 2.636 6.364 2.636c2.125 0 4.078-0.737 5.618-1.968l3.675 3.675c0.391 0.391 1.024 0.391 1.414 0s0.391-1.024 0-1.414z"),n.appendChild(r),n};function xe(e){var t=e.autocomplete,n=e.autocompleteScopeApi,r=e.classNames,o=e.environment,a=e.isDetached,c=e.placeholder,l=void 0===c?"Search":c,s=e.propGetters,p=e.setIsModalOpen,f=e.state,d=Ce(o),m=s.getRootProps(i({state:f,props:t.getRootProps({})},n)),v=d("div",i({class:r.root},m)),h=d("div",{class:r.detachedContainer,onMouseDown:function(e){e.stopPropagation()}}),y=d("div",{class:r.detachedOverlay,children:[h],onMouseDown:function(){p(!1),t.setIsOpen(!1)}}),g=s.getLabelProps(i({state:f,props:t.getLabelProps({})},n)),b=d("button",{class:r.submitButton,type:"submit",title:"Submit",children:[ke({environment:o})]}),_=d("label",i({class:r.label,children:[b]},g)),O=d("button",{class:r.clearButton,type:"reset",title:"Clear",children:[ge({environment:o})]}),P=d("div",{class:r.loadingIndicator,children:[De({environment:o})]}),S=function(e){var t=e.autocompleteScopeApi,n=e.environment,r=(e.classNames,e.getInputProps),o=e.getInputPropsCore,a=e.onDetachedEscape,c=e.state,l=u(e,["autocompleteScopeApi","environment","classNames","getInputProps","getInputPropsCore","onDetachedEscape","state"]),s=Ce(n)("input",l),p=r(i({state:c,props:o({inputElement:s}),inputElement:s},t));return Ee(s,i(i({},p),{},{onKeyDown:function(e){if(a&&"Escape"===e.key)return e.preventDefault(),void a();p.onKeyDown(e)}})),s}({class:r.input,environment:o,state:f,getInputProps:s.getInputProps,getInputPropsCore:t.getInputProps,autocompleteScopeApi:n,onDetachedEscape:a?function(){t.setIsOpen(!1),p(!1)}:void 0}),j=d("div",{class:r.inputWrapperPrefix,children:[_,P]}),w=d("div",{class:r.inputWrapperSuffix,children:[O]}),I=d("div",{class:r.inputWrapper,children:[S]}),E=s.getFormProps(i({state:f,props:t.getFormProps({inputElement:S})},n)),A=d("form",i({class:r.form,children:[j,I,w]},E)),C=s.getPanelProps(i({state:f,props:t.getPanelProps({})},n)),D=d("div",i({class:r.panel},C));if(a){var k=d("div",{class:r.detachedSearchButtonIcon,children:[ke({environment:o})]}),x=d("div",{class:r.detachedSearchButtonPlaceholder,textContent:l}),N=d("button",{class:r.detachedSearchButton,onClick:function(e){e.preventDefault(),p(!0)},children:[k,x]}),F=d("button",{class:r.detachedCancelButton,textContent:"Cancel",onClick:function(){t.setIsOpen(!1),p(!1)}}),L=d("div",{class:r.detachedFormContainer,children:[A,F]});h.appendChild(L),v.appendChild(N)}else v.appendChild(A);return{detachedContainer:h,detachedOverlay:y,inputWrapper:I,input:S,root:v,form:A,label:_,submitButton:b,clearButton:O,loadingIndicator:P,panel:D}}var Ne,Fe,Le,Re,qe={},Te=[],Be=/acit|ex(?:s|g|n|p|$)|rph|grid|ows|mnc|ntw|ine[ch]|zoo|^ord|itera/i;function Ue(e,t){for(var n in t)e[n]=t[n];return e}function Me(e){var t=e.parentNode;t&&t.removeChild(e)}function He(e,t,n){var r,o,i,u=arguments,a={};for(i in t)"key"==i?r=t[i]:"ref"==i?o=t[i]:a[i]=t[i];if(arguments.length>3)for(n=[n],i=3;i<arguments.length;i++)n.push(u[i]);if(null!=n&&(a.children=n),"function"==typeof e&&null!=e.defaultProps)for(i in e.defaultProps)void 0===a[i]&&(a[i]=e.defaultProps[i]);return Ve(e,a,r,o,null)}function Ve(e,t,n,r,o){var i={type:e,props:t,key:n,ref:r,__k:null,__:null,__b:0,__e:null,__d:void 0,__c:null,__h:null,constructor:void 0,__v:null==o?++Ne.__v:o};return null!=Ne.vnode&&Ne.vnode(i),i}function We(e){return e.children}function Qe(e,t){this.props=e,this.context=t}function $e(e,t){if(null==t)return e.__?$e(e.__,e.__.__k.indexOf(e)+1):null;for(var n;t<e.__k.length;t++)if(null!=(n=e.__k[t])&&null!=n.__e)return n.__e;return"function"==typeof e.type?$e(e):null}function ze(e){var t,n;if(null!=(e=e.__)&&null!=e.__c){for(e.__e=e.__c.base=null,t=0;t<e.__k.length;t++)if(null!=(n=e.__k[t])&&null!=n.__e){e.__e=e.__c.base=n.__e;break}return ze(e)}}function Ge(e){(!e.__d&&(e.__d=!0)&&Fe.push(e)&&!Je.__r++||Re!==Ne.debounceRendering)&&((Re=Ne.debounceRendering)||Le)(Je)}function Je(){for(var e;Je.__r=Fe.length;)e=Fe.sort((function(e,t){return e.__v.__b-t.__v.__b})),Fe=[],e.some((function(e){var t,n,r,o,i,u;e.__d&&(i=(o=(t=e).__v).__e,(u=t.__P)&&(n=[],(r=Ue({},o)).__v=o.__v+1,rt(u,o,r,t.__n,void 0!==u.ownerSVGElement,null!=o.__h?[i]:null,n,null==i?$e(o):i,o.__h),ot(n,o),o.__e!=i&&ze(o)))}))}function Ke(e,t,n,r,o,i,u,a,c,l){var s,p,f,d,m,v,h,y=r&&r.__k||Te,g=y.length;for(n.__k=[],s=0;s<t.length;s++)if(null!=(d=n.__k[s]=null==(d=t[s])||"boolean"==typeof d?null:"string"==typeof d||"number"==typeof d||"bigint"==typeof d?Ve(null,d,null,null,d):Array.isArray(d)?Ve(We,{children:d},null,null,null):d.__b>0?Ve(d.type,d.props,d.key,null,d.__v):d)){if(d.__=n,d.__b=n.__b+1,null===(f=y[s])||f&&d.key==f.key&&d.type===f.type)y[s]=void 0;else for(p=0;p<g;p++){if((f=y[p])&&d.key==f.key&&d.type===f.type){y[p]=void 0;break}f=null}rt(e,d,f=f||qe,o,i,u,a,c,l),m=d.__e,(p=d.ref)&&f.ref!=p&&(h||(h=[]),f.ref&&h.push(f.ref,null,d),h.push(p,d.__c||m,d)),null!=m?(null==v&&(v=m),"function"==typeof d.type&&null!=d.__k&&d.__k===f.__k?d.__d=c=Xe(d,c,e):c=Ye(e,d,f,y,m,c),l||"option"!==n.type?"function"==typeof n.type&&(n.__d=c):e.value=""):c&&f.__e==c&&c.parentNode!=e&&(c=$e(f))}for(n.__e=v,s=g;s--;)null!=y[s]&&("function"==typeof n.type&&null!=y[s].__e&&y[s].__e==n.__d&&(n.__d=$e(r,s+1)),at(y[s],y[s]));if(h)for(s=0;s<h.length;s++)ut(h[s],h[++s],h[++s])}function Xe(e,t,n){var r,o;for(r=0;r<e.__k.length;r++)(o=e.__k[r])&&(o.__=e,t="function"==typeof o.type?Xe(o,t,n):Ye(n,o,o,e.__k,o.__e,t));return t}function Ye(e,t,n,r,o,i){var u,a,c;if(void 0!==t.__d)u=t.__d,t.__d=void 0;else if(null==n||o!=i||null==o.parentNode)e:if(null==i||i.parentNode!==e)e.appendChild(o),u=null;else{for(a=i,c=0;(a=a.nextSibling)&&c<r.length;c+=2)if(a==o)break e;e.insertBefore(o,i),u=i}return void 0!==u?u:o.nextSibling}function Ze(e,t,n){"-"===t[0]?e.setProperty(t,n):e[t]=null==n?"":"number"!=typeof n||Be.test(t)?n:n+"px"}function et(e,t,n,r,o){var i;e:if("style"===t)if("string"==typeof n)e.style.cssText=n;else{if("string"==typeof r&&(e.style.cssText=r=""),r)for(t in r)n&&t in n||Ze(e.style,t,"");if(n)for(t in n)r&&n[t]===r[t]||Ze(e.style,t,n[t])}else if("o"===t[0]&&"n"===t[1])i=t!==(t=t.replace(/Capture$/,"")),t=t.toLowerCase()in e?t.toLowerCase().slice(2):t.slice(2),e.l||(e.l={}),e.l[t+i]=n,n?r||e.addEventListener(t,i?nt:tt,i):e.removeEventListener(t,i?nt:tt,i);else if("dangerouslySetInnerHTML"!==t){if(o)t=t.replace(/xlink[H:h]/,"h").replace(/sName$/,"s");else if("href"!==t&&"list"!==t&&"form"!==t&&"tabIndex"!==t&&"download"!==t&&t in e)try{e[t]=null==n?"":n;break e}catch(e){}"function"==typeof n||(null!=n&&(!1!==n||"a"===t[0]&&"r"===t[1])?e.setAttribute(t,n):e.removeAttribute(t))}}function tt(e){this.l[e.type+!1](Ne.event?Ne.event(e):e)}function nt(e){this.l[e.type+!0](Ne.event?Ne.event(e):e)}function rt(e,t,n,r,o,i,u,a,c){var l,s,p,f,d,m,v,h,y,g,b,_=t.type;if(void 0!==t.constructor)return null;null!=n.__h&&(c=n.__h,a=t.__e=n.__e,t.__h=null,i=[a]),(l=Ne.__b)&&l(t);try{e:if("function"==typeof _){if(h=t.props,y=(l=_.contextType)&&r[l.__c],g=l?y?y.props.value:l.__:r,n.__c?v=(s=t.__c=n.__c).__=s.__E:("prototype"in _&&_.prototype.render?t.__c=s=new _(h,g):(t.__c=s=new Qe(h,g),s.constructor=_,s.render=ct),y&&y.sub(s),s.props=h,s.state||(s.state={}),s.context=g,s.__n=r,p=s.__d=!0,s.__h=[]),null==s.__s&&(s.__s=s.state),null!=_.getDerivedStateFromProps&&(s.__s==s.state&&(s.__s=Ue({},s.__s)),Ue(s.__s,_.getDerivedStateFromProps(h,s.__s))),f=s.props,d=s.state,p)null==_.getDerivedStateFromProps&&null!=s.componentWillMount&&s.componentWillMount(),null!=s.componentDidMount&&s.__h.push(s.componentDidMount);else{if(null==_.getDerivedStateFromProps&&h!==f&&null!=s.componentWillReceiveProps&&s.componentWillReceiveProps(h,g),!s.__e&&null!=s.shouldComponentUpdate&&!1===s.shouldComponentUpdate(h,s.__s,g)||t.__v===n.__v){s.props=h,s.state=s.__s,t.__v!==n.__v&&(s.__d=!1),s.__v=t,t.__e=n.__e,t.__k=n.__k,t.__k.forEach((function(e){e&&(e.__=t)})),s.__h.length&&u.push(s);break e}null!=s.componentWillUpdate&&s.componentWillUpdate(h,s.__s,g),null!=s.componentDidUpdate&&s.__h.push((function(){s.componentDidUpdate(f,d,m)}))}s.context=g,s.props=h,s.state=s.__s,(l=Ne.__r)&&l(t),s.__d=!1,s.__v=t,s.__P=e,l=s.render(s.props,s.state,s.context),s.state=s.__s,null!=s.getChildContext&&(r=Ue(Ue({},r),s.getChildContext())),p||null==s.getSnapshotBeforeUpdate||(m=s.getSnapshotBeforeUpdate(f,d)),b=null!=l&&l.type===We&&null==l.key?l.props.children:l,Ke(e,Array.isArray(b)?b:[b],t,n,r,o,i,u,a,c),s.base=t.__e,t.__h=null,s.__h.length&&u.push(s),v&&(s.__E=s.__=null),s.__e=!1}else null==i&&t.__v===n.__v?(t.__k=n.__k,t.__e=n.__e):t.__e=it(n.__e,t,n,r,o,i,u,c);(l=Ne.diffed)&&l(t)}catch(e){t.__v=null,(c||null!=i)&&(t.__e=a,t.__h=!!c,i[i.indexOf(a)]=null),Ne.__e(e,t,n)}}function ot(e,t){Ne.__c&&Ne.__c(t,e),e.some((function(t){try{e=t.__h,t.__h=[],e.some((function(e){e.call(t)}))}catch(e){Ne.__e(e,t.__v)}}))}function it(e,t,n,r,o,i,u,a){var c,l,s,p,f=n.props,d=t.props,m=t.type,v=0;if("svg"===m&&(o=!0),null!=i)for(;v<i.length;v++)if((c=i[v])&&(c===e||(m?c.localName==m:3==c.nodeType))){e=c,i[v]=null;break}if(null==e){if(null===m)return document.createTextNode(d);e=o?document.createElementNS("http://www.w3.org/2000/svg",m):document.createElement(m,d.is&&d),i=null,a=!1}if(null===m)f===d||a&&e.data===d||(e.data=d);else{if(i=i&&Te.slice.call(e.childNodes),l=(f=n.props||qe).dangerouslySetInnerHTML,s=d.dangerouslySetInnerHTML,!a){if(null!=i)for(f={},p=0;p<e.attributes.length;p++)f[e.attributes[p].name]=e.attributes[p].value;(s||l)&&(s&&(l&&s.__html==l.__html||s.__html===e.innerHTML)||(e.innerHTML=s&&s.__html||""))}if(function(e,t,n,r,o){var i;for(i in n)"children"===i||"key"===i||i in t||et(e,i,null,n[i],r);for(i in t)o&&"function"!=typeof t[i]||"children"===i||"key"===i||"value"===i||"checked"===i||n[i]===t[i]||et(e,i,t[i],n[i],r)}(e,d,f,o,a),s)t.__k=[];else if(v=t.props.children,Ke(e,Array.isArray(v)?v:[v],t,n,r,o&&"foreignObject"!==m,i,u,e.firstChild,a),null!=i)for(v=i.length;v--;)null!=i[v]&&Me(i[v]);a||("value"in d&&void 0!==(v=d.value)&&(v!==e.value||"progress"===m&&!v)&&et(e,"value",v,f.value,!1),"checked"in d&&void 0!==(v=d.checked)&&v!==e.checked&&et(e,"checked",v,f.checked,!1))}return e}function ut(e,t,n){try{"function"==typeof e?e(t):e.current=t}catch(e){Ne.__e(e,n)}}function at(e,t,n){var r,o,i;if(Ne.unmount&&Ne.unmount(e),(r=e.ref)&&(r.current&&r.current!==e.__e||ut(r,null,t)),n||"function"==typeof e.type||(n=null!=(o=e.__e)),e.__e=e.__d=void 0,null!=(r=e.__c)){if(r.componentWillUnmount)try{r.componentWillUnmount()}catch(e){Ne.__e(e,t)}r.base=r.__P=null}if(r=e.__k)for(i=0;i<r.length;i++)r[i]&&at(r[i],t,n);null!=o&&Me(o)}function ct(e,t,n){return this.constructor(e,n)}Ne={__e:function(e,t){for(var n,r,o;t=t.__;)if((n=t.__c)&&!n.__)try{if((r=n.constructor)&&null!=r.getDerivedStateFromError&&(n.setState(r.getDerivedStateFromError(e)),o=n.__d),null!=n.componentDidCatch&&(n.componentDidCatch(e),o=n.__d),o)return n.__E=n}catch(t){e=t}throw e},__v:0},Qe.prototype.setState=function(e,t){var n;n=null!=this.__s&&this.__s!==this.state?this.__s:this.__s=Ue({},this.state),"function"==typeof e&&(e=e(Ue({},n),this.props)),e&&Ue(n,e),null!=e&&this.__v&&(t&&this.__h.push(t),Ge(this))},Qe.prototype.forceUpdate=function(e){this.__v&&(this.__e=!0,e&&this.__h.push(e),Ge(this))},Qe.prototype.render=We,Fe=[],Le="function"==typeof Promise?Promise.prototype.then.bind(Promise.resolve()):setTimeout,Je.__r=0;var lt="__aa-highlight__",st="__/aa-highlight__";function pt(e){var t=e.highlightedValue.split(lt),n=t.shift(),r=function(){var e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:[];return{get:function(){return e},add:function(t){var n=e[e.length-1];(null==n?void 0:n.isHighlighted)===t.isHighlighted?e[e.length-1]={value:n.value+t.value,isHighlighted:n.isHighlighted}:e.push(t)}}}(n?[{value:n,isHighlighted:!1}]:[]);return t.forEach((function(e){var t=e.split(st);r.add({value:t[0],isHighlighted:!0}),""!==t[1]&&r.add({value:t[1],isHighlighted:!1})})),r.get()}function ft(e){return function(e){if(Array.isArray(e))return dt(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return dt(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return dt(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function dt(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function mt(e){var t=e.hit,n=e.attribute,r=Array.isArray(n)?n:[n],o=d(t,["_highlightResult"].concat(ft(r),["value"]));return"string"!=typeof o&&(o=d(t,r)||""),pt({highlightedValue:o})}var vt={"&amp;":"&","&lt;":"<","&gt;":">","&quot;":'"',"&#39;":"'"},ht=new RegExp(/\w/i),yt=/&(amp|quot|lt|gt|#39);/g,gt=RegExp(yt.source);function bt(e,t){var n,r,o,i=e[t],u=(null===(n=e[t+1])||void 0===n?void 0:n.isHighlighted)||!0,a=(null===(r=e[t-1])||void 0===r?void 0:r.isHighlighted)||!0;return ht.test((o=i.value)&&gt.test(o)?o.replace(yt,(function(e){return vt[e]})):o)||a!==u?i.isHighlighted:a}function _t(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function Ot(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?_t(Object(n),!0).forEach((function(t){Pt(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):_t(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function Pt(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function St(e){return e.some((function(e){return e.isHighlighted}))?e.map((function(t,n){return Ot(Ot({},t),{},{isHighlighted:!bt(e,n)})})):e.map((function(e){return Ot(Ot({},e),{},{isHighlighted:!1})}))}function jt(e){return function(e){if(Array.isArray(e))return wt(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return wt(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return wt(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function wt(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function It(e){var t=e.hit,n=e.attribute,r=Array.isArray(n)?n:[n],o=d(t,["_snippetResult"].concat(jt(r),["value"]));return"string"!=typeof o&&(o=d(t,r)||""),pt({highlightedValue:o})}function Et(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function At(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?Et(Object(n),!0).forEach((function(t){Ct(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):Et(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function Ct(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}var Dt="1.0.1";function kt(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function xt(e){for(var t=1;t<arguments.length;t++){var n=null!=arguments[t]?arguments[t]:{};t%2?kt(Object(n),!0).forEach((function(t){Nt(e,t,n[t])})):Object.getOwnPropertyDescriptors?Object.defineProperties(e,Object.getOwnPropertyDescriptors(n)):kt(Object(n)).forEach((function(t){Object.defineProperty(e,t,Object.getOwnPropertyDescriptor(n,t))}))}return e}function Nt(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function Ft(e,t){if(null==e)return{};var n,r,o=function(e,t){if(null==e)return{};var n,r,o={},i=Object.keys(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r<i.length;r++)n=i[r],t.indexOf(n)>=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function Lt(e){return function(e){if(Array.isArray(e))return Rt(e)}(e)||function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)}(e)||function(e,t){if(!e)return;if("string"==typeof e)return Rt(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);"Object"===n&&e.constructor&&(n=e.constructor.name);if("Map"===n||"Set"===n)return Array.from(e);if("Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n))return Rt(e,t)}(e)||function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}()}function Rt(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n<t;n++)r[n]=e[n];return r}function qt(e){var t=e.createElement,n=e.Fragment;return function(e){var r,o=e.hit,i=e.attribute,u=e.tagName,a=void 0===u?"mark":u;return t(n,{},(r={hit:o,attribute:i},St(mt(r))).map((function(e,n){return e.isHighlighted?t(a,{key:n},e.value):e.value})))}}function Tt(e){var t=e.createElement,n=e.Fragment;return function(e){var r,o=e.hit,i=e.attribute,u=e.tagName,a=void 0===u?"mark":u;return t(n,{},(r={hit:o,attribute:i},St(It(r))).map((function(e,n){return e.isHighlighted?t(a,{key:n},e.value):e.value})))}}function Bt(e){var t=e.createElement,n=e.Fragment;return function(e){var r=e.hit,o=e.attribute,i=e.tagName,u=void 0===i?"mark":i;return t(n,{},It({hit:r,attribute:o}).map((function(e,n){return e.isHighlighted?t(u,{key:n},e.value):e.value})))}}var Ut={clearButton:"aa-ClearButton",detachedCancelButton:"aa-DetachedCancelButton",detachedContainer:"aa-DetachedContainer",detachedFormContainer:"aa-DetachedFormContainer",detachedOverlay:"aa-DetachedOverlay",detachedSearchButton:"aa-DetachedSearchButton",detachedSearchButtonIcon:"aa-DetachedSearchButtonIcon",detachedSearchButtonPlaceholder:"aa-DetachedSearchButtonPlaceholder",form:"aa-Form",input:"aa-Input",inputWrapper:"aa-InputWrapper",inputWrapperPrefix:"aa-InputWrapperPrefix",inputWrapperSuffix:"aa-InputWrapperSuffix",item:"aa-Item",label:"aa-Label",list:"aa-List",loadingIndicator:"aa-LoadingIndicator",panel:"aa-Panel",panelLayout:"aa-PanelLayout",root:"aa-Autocomplete",source:"aa-Source",sourceFooter:"aa-SourceFooter",sourceHeader:"aa-SourceHeader",sourceNoResults:"aa-SourceNoResults",submitButton:"aa-SubmitButton"},Mt=function(e,t){!function(e,t,n){var r,o,i;Ne.__&&Ne.__(e,t),o=(r="function"==typeof n)?null:n&&n.__k||t.__k,i=[],rt(t,e=(!r&&n||t).__k=He(We,null,[e]),o||qe,qe,void 0!==t.ownerSVGElement,!r&&n?[n]:o?null:t.firstChild?Te.slice.call(t.childNodes):null,i,!r&&n?n:o?o.__e:t.firstChild,r),ot(i,e)}(e.children,t)},Ht={createElement:He,Fragment:We};function Vt(e){var t=e.panelPlacement,n=e.container,r=e.form,o=e.environment,i=n.getBoundingClientRect(),u=i.top+i.height;switch(t){case"start":return{top:u,left:i.left};case"end":return{top:u,right:o.document.documentElement.clientWidth-(i.left+i.width)};case"full-width":return{top:u,left:0,right:0,width:"unset",maxWidth:"unset"};case"input-wrapper-width":var a=r.getBoundingClientRect();return{top:u,left:a.left,right:o.document.documentElement.clientWidth-(a.left+a.width),width:"unset",maxWidth:"unset"};default:throw new Error("[Autocomplete] The `panelPlacement` value ".concat(JSON.stringify(t)," is not valid."))}}var Wt=function(e){function t(t){return e({searchClient:t.searchClient,queries:t.requests.map((function(e){return e.query}))}).then((function(e){return e.map((function(e,n){var r=t.requests[n];return{items:e,sourceId:r.sourceId,transformResponse:r.transformResponse}}))}))}return function(e){return function(n){return At(At({execute:t},e),n)}}}((function(e){return t=i(i({},e),{},{userAgents:[{segment:"autocomplete-js",version:"1.0.1"}]}),n=t.searchClient,r=t.queries,o=t.userAgents,u=void 0===o?[]:o,"function"==typeof n.addAlgoliaAgent&&[{segment:"autocomplete-core",version:Dt}].concat(Lt(u)).forEach((function(e){var t=e.segment,r=e.version;n.addAlgoliaAgent(t,r)})),n.search(r.map((function(e){var t=e.params;return xt(xt({},Ft(e,["params"])),{},{params:xt({hitsPerPage:5,highlightPreTag:lt,highlightPostTag:st},t)})}))).then((function(e){return e.results}));var t,n,r,o,u}));var Qt=Wt({transformResponse:function(e){return e.hits}});e.autocomplete=function(e){var t,o=function(){var e=[],t=[];function n(n){e.push(n);var r=n();t.push(r)}return{runEffect:n,cleanupEffects:function(){var e=t;t=[],e.forEach((function(e){e()}))},runEffects:function(){var t=e;e=[],t.forEach((function(e){n(e)}))}}}(),a=o.runEffect,c=o.cleanupEffects,p=o.runEffects,d=(t=[],{reactive:function(e){var n=e(),r={_fn:e,_ref:{current:n},get value(){return this._ref.current},set value(e){this._ref.current=e}};return t.push(r),r},runReactives:function(){t.forEach((function(e){e._ref.current=e._fn()}))}}),v=d.reactive,h=d.runReactives,y=l(!1),g=l(e),b=l(void 0),_=v((function(){return function(e){var t,n=e.classNames,r=e.container,o=e.getEnvironmentProps,a=e.getFormProps,c=e.getInputProps,l=e.getItemProps,s=e.getLabelProps,p=e.getListProps,d=e.getPanelProps,m=e.getRootProps,v=e.panelContainer,h=e.panelPlacement,y=e.render,g=e.renderNoResults,b=e.renderer,_=e.detachedMediaQuery,O=e.components,P=u(e,["classNames","container","getEnvironmentProps","getFormProps","getInputProps","getItemProps","getLabelProps","getListProps","getPanelProps","getRootProps","panelContainer","panelPlacement","render","renderNoResults","renderer","detachedMediaQuery","components"]),S="undefined"!=typeof window?window:{},j=be(S,r);j.tagName;var w,I,E,A=null!=b?b:Ht,C={Highlight:(w=A,I=w.createElement,E=w.Fragment,function(e){var t=e.hit,n=e.attribute,r=e.tagName,o=void 0===r?"mark":r;return I(E,{},mt({hit:t,attribute:n}).map((function(e,t){return e.isHighlighted?I(o,{key:t},e.value):e.value})))}),ReverseHighlight:qt(A),ReverseSnippet:Tt(A),Snippet:Bt(A)};return{renderer:{classNames:_e(Ut,null!=n?n:{}),container:j,getEnvironmentProps:null!=o?o:function(e){return e.props},getFormProps:null!=a?a:function(e){return e.props},getInputProps:null!=c?c:function(e){return e.props},getItemProps:null!=l?l:function(e){return e.props},getLabelProps:null!=s?s:function(e){return e.props},getListProps:null!=p?p:function(e){return e.props},getPanelProps:null!=d?d:function(e){return e.props},getRootProps:null!=m?m:function(e){return e.props},panelContainer:v?be(S,v):S.document.body,panelPlacement:null!=h?h:"input-wrapper-width",render:null!=y?y:Mt,renderNoResults:g,renderer:A,detachedMediaQuery:null!=_?_:getComputedStyle(S.document.documentElement).getPropertyValue("--aa-detached-media-query"),components:i(i({},C),O)},core:i(i({},P),{},{id:null!==(t=P.id)&&void 0!==t?t:f(),environment:S})}}(g.current)})),O=v((function(){return _.value.core.environment.matchMedia(_.value.renderer.detachedMediaQuery).matches})),P=v((function(){return ye(i(i({},_.value.core),{},{onStateChange:function(e){var t,n,r;y.current=e.state.collections.some((function(e){return e.source.templates.noResults})),null===(t=b.current)||void 0===t||t.call(b,e),null===(n=(r=_.value.core).onStateChange)||void 0===n||n.call(r,e)},shouldPanelOpen:g.current.shouldPanelOpen||function(e){var t=e.state;if(O.value)return!0;var n=m(t)>0;if(!_.value.core.openOnFocus&&!t.query)return n;var r=Boolean(y.current||_.value.renderer.renderNoResults);return!n&&r||n}}))})),S=l(i({collections:[],completion:null,context:{},isOpen:!1,query:"",activeItemId:null,status:"idle"},_.value.core.initialState)),j={getEnvironmentProps:_.value.renderer.getEnvironmentProps,getFormProps:_.value.renderer.getFormProps,getInputProps:_.value.renderer.getInputProps,getItemProps:_.value.renderer.getItemProps,getLabelProps:_.value.renderer.getLabelProps,getListProps:_.value.renderer.getListProps,getPanelProps:_.value.renderer.getPanelProps,getRootProps:_.value.renderer.getRootProps},w={setActiveItemId:P.value.setActiveItemId,setQuery:P.value.setQuery,setCollections:P.value.setCollections,setIsOpen:P.value.setIsOpen,setStatus:P.value.setStatus,setContext:P.value.setContext,refresh:P.value.refresh},I=v((function(){return xe({autocomplete:P.value,autocompleteScopeApi:w,classNames:_.value.renderer.classNames,environment:_.value.core.environment,isDetached:O.value,placeholder:_.value.core.placeholder,propGetters:j,setIsModalOpen:D,state:S.current})}));function E(){Ee(I.value.panel,{style:O.value?{}:Vt({panelPlacement:_.value.renderer.panelPlacement,container:I.value.root,form:I.value.form,environment:_.value.core.environment})})}function A(e){S.current=e;var t={autocomplete:P.value,autocompleteScopeApi:w,classNames:_.value.renderer.classNames,components:_.value.renderer.components,container:_.value.renderer.container,createElement:_.value.renderer.renderer.createElement,dom:I.value,Fragment:_.value.renderer.renderer.Fragment,panelContainer:O.value?I.value.detachedContainer:_.value.renderer.panelContainer,propGetters:j,state:S.current},n=!m(e)&&!y.current&&_.value.renderer.renderNoResults||_.value.renderer.render;!function(e){var t=e.autocomplete,n=e.autocompleteScopeApi,r=e.dom,o=e.propGetters,u=e.state;Ae(r.root,o.getRootProps(i({state:u,props:t.getRootProps({})},n))),Ae(r.input,o.getInputProps(i({state:u,props:t.getInputProps({inputElement:r.input}),inputElement:r.input},n))),Ee(r.label,{hidden:"stalled"===u.status}),Ee(r.loadingIndicator,{hidden:"stalled"!==u.status}),Ee(r.clearButton,{hidden:!u.query})}(t),function(e,t){var n=t.autocomplete,o=t.autocompleteScopeApi,u=t.classNames,a=t.createElement,c=t.dom,l=t.Fragment,s=t.panelContainer,p=t.propGetters,f=t.state,d=t.components;if(f.isOpen){s.contains(c.panel)||"loading"===f.status||s.appendChild(c.panel),c.panel.classList.toggle("aa-Panel--stalled","stalled"===f.status);var m=f.collections.map((function(e,t){var c=e.source,s=e.items;return a("section",{key:t,className:u.source,"data-autocomplete-source-id":c.sourceId},c.templates.header&&a("div",{className:u.sourceHeader},c.templates.header({components:d,createElement:a,Fragment:l,items:s,source:c,state:f})),c.templates.noResults&&0===s.length?a("div",{className:u.sourceNoResults},c.templates.noResults({components:d,createElement:a,Fragment:l,source:c,state:f})):a("ul",r({className:u.list},p.getListProps(i({state:f,props:n.getListProps({})},o))),s.map((function(e){var t=n.getItemProps({item:e,source:c});return a("li",r({key:t.id,className:u.item},p.getItemProps(i({state:f,props:t},o))),c.templates.item({components:d,createElement:a,Fragment:l,item:e,state:f}))}))),c.templates.footer&&a("div",{className:u.sourceFooter},c.templates.footer({components:d,createElement:a,Fragment:l,items:s,source:c,state:f})))})),v=a(l,null,a("div",{className:"aa-PanelLayout aa-Panel--scrollable"},m),a("div",{className:"aa-GradientBottom"})),h=m.reduce((function(e,t){return e[t.props["data-autocomplete-source-id"]]=t,e}),{});e({children:v,state:f,sections:m,elements:h,createElement:a,Fragment:l,components:d},c.panel)}else s.contains(c.panel)&&s.removeChild(c.panel)}(n,t)}function C(){var e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:{};c(),g.current=Pe(_.value.renderer,_.value.core,{initialState:S.current},e),h(),p(),P.value.refresh().then((function(){A(S.current)}))}function D(e){requestAnimationFrame((function(){var t=_.value.core.environment.document.body.contains(I.value.detachedOverlay);e!==t&&(e?(_.value.core.environment.document.body.appendChild(I.value.detachedOverlay),_.value.core.environment.document.body.classList.add("aa-Detached"),I.value.input.focus()):(_.value.core.environment.document.body.removeChild(I.value.detachedOverlay),_.value.core.environment.document.body.classList.remove("aa-Detached"),P.value.setQuery(""),P.value.refresh()))}))}return a((function(){var e=P.value.getEnvironmentProps({formElement:I.value.form,panelElement:I.value.panel,inputElement:I.value.input});return Ee(_.value.core.environment,e),function(){Ee(_.value.core.environment,Object.keys(e).reduce((function(e,t){return i(i({},e),{},n({},t,void 0))}),{}))}})),a((function(){var e=O.value?_.value.core.environment.document.body:_.value.renderer.panelContainer,t=O.value?I.value.detachedOverlay:I.value.panel;return O.value&&S.current.isOpen&&D(!0),A(S.current),function(){e.contains(t)&&e.removeChild(t)}})),a((function(){var e=_.value.renderer.container;return e.appendChild(I.value.root),function(){e.removeChild(I.value.root)}})),a((function(){var e=s((function(e){A(e.state)}),0);return b.current=function(t){var n=t.state,r=t.prevState;(O.value&&r.isOpen!==n.isOpen&&D(n.isOpen),O.value||!n.isOpen||r.isOpen||E(),n.query!==r.query)&&_.value.core.environment.document.querySelectorAll(".aa-Panel--scrollable").forEach((function(e){0!==e.scrollTop&&(e.scrollTop=0)}));e({state:n})},function(){b.current=void 0}})),a((function(){var e=s((function(){var e=O.value;O.value=_.value.core.environment.matchMedia(_.value.renderer.detachedMediaQuery).matches,e!==O.value?C({}):requestAnimationFrame(E)}),20);return _.value.core.environment.addEventListener("resize",e),function(){_.value.core.environment.removeEventListener("resize",e)}})),a((function(){if(!O.value)return function(){};function e(e){I.value.detachedContainer.classList.toggle("aa-DetachedContainer--modal",e)}function t(t){e(t.matches)}var n=_.value.core.environment.matchMedia(getComputedStyle(_.value.core.environment.document.documentElement).getPropertyValue("--aa-detached-modal-media-query"));return e(n.matches),n.addEventListener("change",t),function(){n.removeEventListener("change",t)}})),a((function(){return requestAnimationFrame(E),function(){}})),i(i({},w),{},{update:C,destroy:function(){c()}})},e.getAlgoliaFacets=function(e){var t=Wt({transformResponse:function(e){return e.facetHits}}),n=e.queries.map((function(e){return i(i({},e),{},{type:"facet"})}));return t(i(i({},e),{},{queries:n}))},e.getAlgoliaResults=Qt,Object.defineProperty(e,"__esModule",{value:!0})}));
 
 /**
  * Skipped minification because the original files appears to be already minified.
@@ -24,4 +24,4 @@ var ALGOLIA_INSIGHTS_SRC = "https://cdn.jsdelivr.net/npm/search-insights@2.0.0";
 !function(e,a,t,n,s,i,c){e.AlgoliaAnalyticsObject=s,e[s]=e[s]||function(){
 (e[s].queue=e[s].queue||[]).push(arguments)},i=a.createElement(t),c=a.getElementsByTagName(t)[0],
 i.async=1,i.src=n,c.parentNode.insertBefore(i,c)
-}(window,document,"script",ALGOLIA_INSIGHTS_SRC,"insightsClient");
\ No newline at end of file
+}(window,document,"script",ALGOLIA_INSIGHTS_SRC,"insightsClient");
diff --git a/assets/js/broken_redirect_list.js b/assets/js/broken_redirect_list.js
index 4f8920fa1ab..f183992e5bb 100644
--- a/assets/js/broken_redirect_list.js
+++ b/assets/js/broken_redirect_list.js
@@ -251,7 +251,7 @@ validurls['/docs/partners/channel_extensions/calendar/rokt_calendar/'] = '/docs/
 validurls['/docs/partners/data_and_infrastructure_agility/data_warehouses/amazon_s3/'] = '/docs/partners/data_and_infrastructure_agility/cloud_storage/amazon_s3/';
 validurls['/docs/partners/data_and_infrastructure_agility/data_warehouses/google_cloud_storage_for_currents/'] = '/docs/partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents/';
 validurls['/docs/partners/data_and_infrastructure_agility/data_warehouses/microsoft_azure_blob_storage_for_currents/'] = '/docs/partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents/';
-validurls['/docs/user_guide/administrative/access_braze/single_sign_on/azure_ad'] = '/docs/docs/user_guide/administrative/access_braze/single_sign_on/entra/';
+validurls['/docs/user_guide/administrative/access_braze/single_sign_on/azure_ad'] = '/docs/user_guide/administrative/access_braze/single_sign_on/entra/';
 validurls['/docs/partners/technology_partners/data_and_infrastructure_agility/data_warehouses/amazon_s3/'] = '/docs/partners/data_and_infrastructure_agility/cloud_storage/amazon_s3/';
 validurls['/docs/partners/technology_partners/data_and_infrastructure_agility/data_warehouses/google_cloud_storage_for_currents/'] = '/docs/partners/data_and_infrastructure_agility/cloud_storage/google_cloud_storage_for_currents/';
 validurls['/docs/partners/technology_partners/data_and_infrastructure_agility/data_warehouses/microsoft_azure_blob_storage_for_currents/'] = '/docs/partners/data_and_infrastructure_agility/cloud_storage/microsoft_azure_blob_storage_for_currents/';
@@ -433,6 +433,7 @@ validurls['/docs/user_guide/message_building_by_channel/in-app_messages/generati
 validurls['/docs/help/best_practices/push/use_cases/'] = '/docs/user_guide/message_building_by_channel/push/about/#potential-use-cases';
 validurls['/docs/help/best_practices/push/'] = '/docs/user_guide/message_building_by_channel/push/best_practices/';
 validurls['/docs/help/best_practices/push/ios/notification_headers'] = '/docs/user_guide/message_building_by_channel/push/creating_a_push_message/#step-4-compose-your-push-message';
+validurls['/docs/user_guide/message_building_by_channel/push/ios/notification_payload_examples'] = '/docs/user_guide/message_building_by_channel/push/ios/notification_options/';
 validurls['/docs/help/best_practices/push/additional_android_best_practices/'] = '/docs/user_guide/message_building_by_channel/push/android/advanced_campaign_settings/';
 validurls['/docs/user_guide/message_building_by_channel/push/best_practices/additional_android_best_practices/'] = '/docs/user_guide/message_building_by_channel/push/android/advanced_campaign_settings/';
 validurls['/docs/help/best_practices/push/detailed_push_preferences/'] = '/docs/user_guide/message_building_by_channel/push/best_practices/';
@@ -658,10 +659,12 @@ validurls['/docs/developer_guide/platform_integration_guides/android/push_notifi
 validurls['/docs/developer_guide/platform_integration_guides/fireos/advanced_use_cases/deep_linking'] = '/docs/developer_guide/platform_integration_guides/android/advanced_use_cases/deep_linking/';
 validurls['/docs/developer_guide/platform_integration_guides/fireos/advanced_use_cases/font_customization/'] = '/docs/developer_guide/platform_integration_guides/android/advanced_use_cases/font_customization/';
 validurls['/docs/developer_guide/platform_integration_guides/fireos/analytics/location_tracking/'] = '/docs/developer_guide/platform_integration_guides/android/analytics/location_tracking';
+validurls['/docs/developer_guide/platform_integration_guides/android/advanced_use_cases/deep_linking_to_in-app_resources/'] = '/docs/developer_guide/platform_integration_guides/android/advanced_use_cases/deep_linking/';
 validurls['/docs/developer_guide/platform_integration_guides/fireos/advanced_use_cases/beacon_integration/'] = '/docs/developer_guide/platform_integration_guides/android/advanced_use_cases/beacon_integration';
 validurls['/docs/developer_guide/platform_integration_guides/fireos/analytics/tracking_custom_events/'] = '/docs/developer_guide/platform_integration_guides/android/analytics/tracking_custom_events/';
 validurls['/docs/developer_guide/platform_integration_guides/fireos/content_cards/customization/'] = '/docs/developer_guide/platform_integration_guides/android/content_cards/customization';
 validurls['/docs/developer_guide/platform_integration_guides/fireos/in-app_messaging/'] = '/docs/developer_guide/platform_integration_guides/android/in-app_messaging/integration/';
+validurls['/docs/developer_guide/platform_integration_guides/fireos/in-app_messaging/in-app_message_delivery/'] = '/docs/developer_guide/platform_integration_guides/android/in-app_messaging/in-app_message_delivery/';
 validurls['/docs/developer_guide/platform_integration_guides/fireos/in-app_messaging/ott_devices/'] = '/docs/developer_guide/platform_integration_guides/android/in-app_messaging/ott_devices';
 validurls['/docs/developer_guide/platform_integration_guides/fireos/in-app_messaging/overview/'] = '/docs/developer_guide/platform_integration_guides/android/in-app_messaging/integration/';
 validurls['/docs/developer_guide/platform_integration_guides/fireos/initial_sdk_setup/'] = '/docs/developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration/';
@@ -795,6 +798,7 @@ validurls['/docs/developer_guide/platform_integration_guides/swift/live_activiti
 validurls['/docs/user_guide/message_building_by_channel/in-app_messages/create/'] = '/docs/user_guide/message_building_by_channel/in-app_messages/traditional/create/';
 validurls['/docs/user_guide/message_building_by_channel/in-app_messages/customize'] = '/docs/user_guide/message_building_by_channel/in-app_messages/traditional/customize/';
 validurls['/docs/user_guide/message_building_by_channel/in-app_messages/customize/html_in-app_messages/'] = '/docs/user_guide/message_building_by_channel/in-app_messages/traditional/customize/html_in-app_messages/';
+validurls['/docs/user_guide/message_building_by_channel/in-app_messages/traditional/customize/html_in_app_messages/'] = '/docs/user_guide/message_building_by_channel/in-app_messages/traditional/customize/html_in-app_messages/';
 validurls['/docs/user_guide/message_building_by_channel/in-app_messages/customize/modal_with_css'] = '/docs/user_guide/message_building_by_channel/in-app_messages/traditional/customize/modal_with_css/';
 validurls['/docs/user_guide/message_building_by_channel/in-app_messages/customize/email_capture_form/'] = '/docs/user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form/';
 validurls['/docs/user_guide/message_building_by_channel/in-app_messages/customize/color_profiles_and_css/'] = '/docs/user_guide/message_building_by_channel/in-app_messages/traditional/customize/color_profiles_and_css/';
@@ -952,6 +956,7 @@ validurls['/docs/developer_guide/platform_integration_guides/android/content_car
 validurls['/docs/developer_guide/platform_integration_guides/android/content_cards/customization/GIFs/'] = '/docs/developer_guide/platform_integration_guides/android/content_cards/GIFs/';
 validurls['/docs/developer_guide/platform_integration_guides/android/content_cards/customization/use_cases/carousel_view/'] = '/docs/developer_guide/customization_guides/content_cards/creating_custom_content_cards/';
 validurls['/docs/developer_guide/platform_integration_guides/web/content_cards/multiple_feeds/'] = '/docs/developer_guide/customization_guides/content_cards/customizing_feed/';
+validurls['/docs/developer_guide/platform_integration_guides/web/analytics/user_ids/'] = '/docs/developer_guide/platform_integration_guides/web/analytics/setting_user_ids/';
 validurls['/docs/developer_guide/platform_integration_guides/web/content_cards/refreshing_the_feed/'] = '/docs/developer_guide/customization_guides/content_cards/customizing_feed/';
 validurls['/docs/developer_guide/platform_integration_guides/web/content_cards/customization/badges/'] = '/docs/developer_guide/customization_guides/content_cards/customizing_behavior/#content-card-badges/';
 validurls['/docs/developer_guide/platform_integration_guides/web/content_cards/customization/custom_ui/'] = '/docs/developer_guide/customization_guides/content_cards/customizing_styles/';
@@ -985,6 +990,7 @@ validurls['/docs/user_guide/onboarding_with_braze/data_points'] = '/docs/user_gu
 
 validurls['/docs/developer_guide/platform_wide/analytics_overview/'] = '/docs/developer_guide/platform_wide/getting_started/analytics_overview/';
 validurls['/docs/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personal_path'] = '/docs/user_guide/engagement_tools/canvas/canvas_components/experiment_step/personalized_paths/';
+validurls['/docs/user_guide/engagement_tools/landing_pages/connect_subdomain/'] = '/docs/user_guide/engagement_tools/landing_pages/connect_domain/';
 
 validurls['/docs/help/release_notes/2021/12_14_21/'] = '/docs/help/release_notes/2021/december/';
 
@@ -1182,10 +1188,11 @@ validurls['/docs/developer_guide/platform_integration_guides/tvos/content_cards/
 validurls['/docs/engagement_by_device/'] = '/docs/user_guide/data_and_analytics/analytics/email_performance_dashboard/#engagement-by-device/';
 
 validurls['/docs/partners/message_orchestration/additional_channels/messaging/'] = '/docs/partners/message_orchestration/additional_channels/instant_chat/';
-validurls['/docs/partners/message_orchestration/additional_channels/messaging/line/'] = '/docs/partners/message_orchestration/additional_channels/instant_chat/line/';
 validurls['/docs/partners/message_orchestration/additional_channels/messaging/messenger/'] = '/docs/partners/message_orchestration/additional_channels/instant_chat/messenger/';
 validurls['/docs/partners/message_orchestration/additional_channels/messaging/regal/'] = '/docs/partners/message_orchestration/additional_channels/instant_chat/regal/';
 validurls['/docs/partners/message_orchestration/additional_channels/messaging/sendbird/'] = '/docs/partners/message_orchestration/additional_channels/instant_chat/sendbird/';
+validurls['/docs/partners/message_orchestration/additional_channels/instant_chat/line/'] = '/docs/line/';
+validurls['/docs/partners/message_orchestration/additional_channels/messaging/line/'] = '/docs/line/'; 
 
 validurls['/docs/developer_guide/platform_integration_guides/android/content_cards/customization/'] = '/docs/developer_guide/platform_integration_guides/android/content_cards/implementation_guide/';
 validurls['/docs/canvas_data_retention/'] = '/docs/api/data_retention/';
@@ -1210,4 +1217,6 @@ validurls['/docs/developer_guide/platform_integration_guides/swift/initial_sdk_s
 
 validurls['/docs/user_csv_lambda/'] = '/docs/user_guide/data_and_analytics/cloud_ingestion';
 
+validurls['/docs/user_guide/engagement_tools/segments/beacon_support/'] = '/docs/user_guide/engagement_tools/locations_and_geofences/location_tracking/#partnership-support-for-beacon-and-geofence';
+
 // validurls['OLD'] = 'NEW';
diff --git a/assets/js/toc.js b/assets/js/toc.js
index a5ae032f65b..b73df299b56 100644
--- a/assets/js/toc.js
+++ b/assets/js/toc.js
@@ -57,7 +57,7 @@
 
     var level = get_level(headers[0]),
       this_level,
-      html = " <"+ settings.listType + settings.bootstrapStyling +"><div class='" + settings.toc_header_class + "'>" + settings.toc_header + "</div><div class='" + settings.toc_container_class + "'>";
+      html = " <"+ settings.listType + settings.bootstrapStyling +" aria-label='Table of Content' title='Table of Content'><div class='" + settings.toc_header_class + "'>" + settings.toc_header + "</div><div class='" + settings.toc_container_class + "'>";
     headers.on('click', function() {
       if (!settings.noBackToTopLinks) {
         window.location.hash = this.id;
@@ -80,7 +80,7 @@
       }
       else if (this_level > level) { // lower level than before; expand the previous to contain a ol
         for(i = this_level; i > level; i--) {
-          html += "<"+ settings.listType + settings.bootstrapStyling +">"
+          html += "<"+ settings.listType + settings.bootstrapStyling +" aria-label='ToC " + header.innerHTML + "'>"
         }
         html += "<div><a class='" + settings.toc_link_class + "' href='#" + header.id + "'  id='" + settings.listPrefix + header.id + "' >" + header.innerHTML + "</a></div> ";
       }