From 6196a0ee831e8271abdafaf6d7e2c810bbb896a2 Mon Sep 17 00:00:00 2001 From: Rachel Feinberg <135255868+rachel-feinberg@users.noreply.github.com> Date: Wed, 10 Jul 2024 08:55:51 -0700 Subject: [PATCH] Revert "BD-3237 pt 1 glossary audit (through end user)" --- CODE_OF_CONDUCT.md | 2 +- _config.yml | 4 +- .../messaging/android_object.md | 2 +- .../objects_filters/messaging/apple_object.md | 2 +- .../objects_filters/messaging/web_objects.md | 2 +- _docs/_contributing/content_management.md | 2 +- .../content_management/images.md | 2 +- .../yaml_front_matter/metadata.md | 2 +- .../_contributing/your_first_contribution.md | 2 +- .../initial_sdk_setup/ios_sdk_integration.md | 2 +- .../implementation_guide.md | 12 +++--- .../swift/archived_updates/ios_14.md | 2 +- .../swift/archived_updates/ios_17.md | 2 +- .../implementation_guide.md | 10 ++--- .../getting_started/architecture_overview.md | 2 +- .../platform_wide/sdk_authentication.md | 2 +- _docs/_docs_pages/cla.md | 2 +- _docs/_help/release_notes/2024/6_25_24.md | 2 +- _docs/_hidden/compliance/sms_channel.md | 2 +- _docs/_hidden/other/10dlc_application.md | 2 +- _docs/_hidden/other/credit_ratios.md | 4 +- .../sms_traffic_pumping_fraud.md | 2 +- .../cohort_import/treasuredata.md | 2 +- .../customer_data_platform/lexer.md | 2 +- .../treasure_data/treasure_data.md | 2 +- .../customer_data_platform/zeotap/zeotap.md | 2 +- .../data_privacy/transcend.md | 4 +- .../support/pypestream.md | 4 +- .../instant_chat/sendbird.md | 2 +- .../additional_channels/retargeting/quikly.md | 2 +- .../using_shopify/shopify_data_in_braze.md | 4 +- ...stribution_with_braze_custom_attributes.md | 2 +- .../movable_ink/customer_data_api.md | 2 +- .../company_settings/security_settings.md | 2 +- .../app_settings/email_settings.md | 2 +- .../manage_your_braze_users/teams.md | 2 +- .../message_engagement_events.md | 12 +++--- .../cloud_ingestion/connected_sources.md | 2 +- .../file_storage_integrations.md | 6 +-- .../cloud_ingestion/integrations.md | 2 +- .../cloud_ingestion/overview.md | 2 +- .../user_profile_lifecycle.md | 2 +- .../canvas/create_a_canvas/create_a_canvas.md | 8 ++-- .../templates_and_media/media_library.md | 2 +- .../email_private_relay_apple_SSO.md | 2 +- .../best_practices/guidelines_and_tips.md | 2 +- .../email/drag_and_drop/overview.md | 2 +- .../email/email_setup/email_validation.md | 2 +- .../email/managing_user_subscriptions.md | 2 +- .../in-app_messages/traditional/create.md | 2 +- .../customize/email_capture_form.md | 2 +- .../push/creating_a_push_message.md | 2 +- .../sms/keywords/keyword_handling.md | 2 +- .../sms/sms_setup/terms.md | 2 +- .../webhooks/understanding_webhooks.md | 6 +-- .../whatsapp/faqs.md | 40 +++++++++--------- .../about_item_recommendations.md | 42 +++++++++---------- .../ai_item_recommendations.md | 14 +++---- _lang/fr/_api/api_limits.md | 2 +- .../export/canvas/get_canvas_details.md | 2 +- .../post_users_global_control_group.md | 4 +- .../export/user_data/post_users_segment.md | 2 +- .../send_messages/post_send_messages.md | 2 +- .../messaging/android_object.md | 2 +- .../objects_filters/messaging/apple_object.md | 2 +- .../objects_filters/messaging/email_object.md | 2 +- .../objects_filters/messaging/web_objects.md | 2 +- .../_api/objects_filters/purchase_object.md | 4 +- .../initial_sdk_setup/ios_sdk_integration.md | 4 +- .../customization/ignoring_internal_push.md | 8 ++-- .../initial_sdk_setup/ios_sdk_integration.md | 2 +- .../customization/ignoring_internal_push.md | 8 ++-- .../implementation_guide.md | 4 +- .../message_engagement_events.md | 2 +- .../user_data_collection/user_import.md | 2 +- .../implementation_guide.md | 2 +- 76 files changed, 157 insertions(+), 157 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 6509c58db10..57a9c48e190 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -47,7 +47,7 @@ threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of -representing a project or community include using an official project email +representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. diff --git a/_config.yml b/_config.yml index 137a889687c..d209de6628c 100644 --- a/_config.yml +++ b/_config.yml @@ -3,8 +3,8 @@ title: Braze Documentation email: success@braze.com description: >- # this means to ignore newlines until "baseurl:" Welcome to Braze Documentation. Braze provides a comprehensive user engagement solution for your mobile apps. -baseurl: "/docs" # the subpath of your site, such as /blog -homeurl: "https://www.braze.com" # the base hostname & protocol for your site, such as http://example.com +baseurl: "/docs" # the subpath of your site, e.g., /blog +homeurl: "https://www.braze.com" # the base hostname & protocol for your site, e.g., http://example.com twitter_username: Braze github_username: braze-inc diff --git a/_docs/_api/objects_filters/messaging/android_object.md b/_docs/_api/objects_filters/messaging/android_object.md index ebac1e11b90..3dc899e4918 100644 --- a/_docs/_api/objects_filters/messaging/android_object.md +++ b/_docs/_api/objects_filters/messaging/android_object.md @@ -35,7 +35,7 @@ You must include an Android push object in `messages` if you want users you have "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 + "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 via Conversation Push. } ``` diff --git a/_docs/_api/objects_filters/messaging/apple_object.md b/_docs/_api/objects_filters/messaging/apple_object.md index 45f36b2b63a..dee144cdfe3 100644 --- a/_docs/_api/objects_filters/messaging/apple_object.md +++ b/_docs/_api/objects_filters/messaging/apple_object.md @@ -35,7 +35,7 @@ description: "This reference article lists and explains the different Apple obje "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 + "buttons" : (optional, array of Apple Push Action Button Objects) push action buttons to display } ``` diff --git a/_docs/_api/objects_filters/messaging/web_objects.md b/_docs/_api/objects_filters/messaging/web_objects.md index 3d881d21991..ccd9355ff4d 100644 --- a/_docs/_api/objects_filters/messaging/web_objects.md +++ b/_docs/_api/objects_filters/messaging/web_objects.md @@ -26,7 +26,7 @@ description: "This reference article lists and explains the different web object "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 + "buttons" : (optional, array of Web Push Action Button Objects) push action buttons to display } ``` diff --git a/_docs/_contributing/content_management.md b/_docs/_contributing/content_management.md index 4566bfae1b6..2217aa91259 100644 --- a/_docs/_contributing/content_management.md +++ b/_docs/_contributing/content_management.md @@ -98,7 +98,7 @@ Replace the following. | Placeholder | Description | |-------------|-------------------------------------------------------------------------------------------------------------------------| -| `ALT_TEXT` | The alt text for the image. This is required to make sure Braze Docs is equally accessible for those using screen readers. | +| `ALT_TEXT` | The alt text for the image. This is required to ensure Braze Docs is 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} diff --git a/_docs/_contributing/content_management/images.md b/_docs/_contributing/content_management/images.md index 9144b5c5694..e52a1d45adf 100644 --- a/_docs/_contributing/content_management/images.md +++ b/_docs/_contributing/content_management/images.md @@ -62,7 +62,7 @@ Replace the following: | Placeholder | Description | |-------------|-------------------------------------------------------------------------------------------------------------------------| -| `ALT_TEXT` | The alt text for the image. This is required to make sure Braze Docs is equally accessible for those using screen readers. | +| `ALT_TEXT` | The alt text for the image. This is required to ensure Braze Docs is 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} diff --git a/_docs/_contributing/yaml_front_matter/metadata.md b/_docs/_contributing/yaml_front_matter/metadata.md index 94fd8ef385e..20b163269cd 100644 --- a/_docs/_contributing/yaml_front_matter/metadata.md +++ b/_docs/_contributing/yaml_front_matter/metadata.md @@ -34,7 +34,7 @@ Replace the following: ### Article title -The `article_title` key is used to set the page title for online search results and the user's browser tab. This key accepts any `string` value. For naming conventions, see the [Braze Docs Style Guide]({{site.baseurl}}/contributing/style_guide/). +The `article_title` key is used to set the page title for online search results and the end-user's browser tab. This key accepts any `string` value. For naming conventions, see the [Braze Docs Style Guide]({{site.baseurl}}/contributing/style_guide/). {% tabs local %} {% tab usage example %} diff --git a/_docs/_contributing/your_first_contribution.md b/_docs/_contributing/your_first_contribution.md index bf8f4996268..61728739979 100644 --- a/_docs/_contributing/your_first_contribution.md +++ b/_docs/_contributing/your_first_contribution.md @@ -189,7 +189,7 @@ These comments will guide you through your PR description. When you're finished, ## Step 4: Review your work -Make sure your content follows the [Braze Docs Style Guide]({{sitebase.url}}/contributing/style_guide/) by 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. +Ensure your content follows the [Braze Docs Style Guide]({{sitebase.url}}/contributing/style_guide/) by 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. {% tabs %} {% tab github %} 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 1336aa9bdd4..09bff593c4b 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 @@ -427,7 +427,7 @@ Proceed to compile your code and run your application.

Try identifying us ### Log analytics {% tabs local %} -{% tab Step 1: Custom events %} +{% tab Step 1: Custom Events %} ##### Create log custom event method diff --git a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/implementation_guide.md b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/implementation_guide.md index b9350e85263..1f402529edc 100644 --- a/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/implementation_guide.md +++ b/_docs/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/implementation_guide.md @@ -160,7 +160,7 @@ To set up an information capture capable push in the dashboard, you must registe Each action button is uniquely identified. The code checks if your response identifier is equal to the `actionIndentifier`, and if so, knows that the user clicked the action button. -**Handling Push Notification action button responses**
+**Handling Push Notification Action Button Responses**
{% tabs %} {% tab Swift %} @@ -227,7 +227,7 @@ Add a capability `App Groups`. If you haven't had any app group in your app, go The following code snippets are a helpful reference on how to save and send custom events, custom attributes, and user attributes. This guide will be speaking in terms of UserDefaults, but the code representation will be in the form of a helper file `RemoteStorage`. There also exist additional helper files `UserAttributes` and `EventName Dictionary` that are used when sending and saving user attributes. All helper files can be found at the end of this guide. {% tabs local %} -{% tab Custom events %} +{% tab Custom Events %} ##### Saving custom events @@ -368,7 +368,7 @@ func logPendingCustomEventsIfNecessary() { {% endsubtab %} {% endsubtabs %} {% endtab %} -{% tab Custom attributes %} +{% tab Custom Attributes %} ##### Saving custom attributes @@ -485,7 +485,7 @@ func setCustomAttributesWith(keysAndValues: [String: Any]) { {% endsubtab %} {% endsubtabs %} {% endtab %} -{% tab User attributes %} +{% tab User Attributes %} ##### Saving user attributes @@ -611,7 +611,7 @@ func logPendingUserAttributesIfNecessary() { {% endsubtab %} {% endsubtabs %} {% endtab %} -{% tab Helper files %} +{% tab Helper Files %} ##### Helper files @@ -797,7 +797,7 @@ extension UserAttribute: Codable { {% endsubtab %} {% endsubtabs %} {% enddetails %} -{% details EventName dictionary helper file %} +{% details EventName Dictionary Helper File %} {% subtabs global %} {% subtab Swift %} ```swift diff --git a/_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_14.md b/_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_14.md index ecff86c5012..26cb585762d 100644 --- a/_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_14.md +++ b/_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_14.md @@ -82,7 +82,7 @@ Starting in iOS 14.5, a new permission prompt (launched by the new `AppTrackingT If a user does not accept the prompt, or if you do not upgrade to Xcode 12's `AppTrackingTransparency` framework, then a blank IDFA value (`00000000-0000-0000-0000-000000000000`) will be returned, and your app will not be allowed to prompt the user again. {% alert important %} -These IDFA updates will take effect after your users upgrade their device to iOS 14.5. Ensure your app uses the new `AppTransparencyFramework` with Xcode 12 if you plan to collect IDFA. +These IDFA updates will take effect after end-users upgrade their device to iOS 14.5. Ensure your app uses the new `AppTransparencyFramework` with Xcode 12 if you plan to collect IDFA. {% endalert %} #### Changes to Braze IDFA collection diff --git a/_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_17.md b/_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_17.md index 1565e05e0f1..9a56168b725 100644 --- a/_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_17.md +++ b/_docs/_developer_guide/platform_integration_guides/swift/archived_updates/ios_17.md @@ -31,7 +31,7 @@ Apple announced its commitment to expand the scope of [Ad Tracking Transparency #### Privacy manifests -Apple now requires a privacy manifest file that describes the reason your app and third-party SDKs collect data, along with their data-collection methods. Starting with iOS 17.2, Apple will block all declared tracking endpoints in your app until your users accept the ATT prompt. +Apple now requires a privacy manifest file that describes the reason your app and third-party SDKs collect data, along with their data-collection methods. Starting with iOS 17.2, Apple will block all declared tracking endpoints in your app until the end-user accepts the ATT prompt. Braze has released our own privacy manifest, along with new flexible APIs that automatically reroute declared tracking data to dedicated `-tracking` endpoints. For more information, see [Braze's privacy manifest]({{site.baseurl}}/developer_guide/platform_integration_guides/swift/privacy_manifest). diff --git a/_docs/_developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide.md b/_docs/_developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide.md index c3639c928ad..d5b798cffd9 100644 --- a/_docs/_developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide.md +++ b/_docs/_developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide.md @@ -165,7 +165,7 @@ As seen in the example, you may also include an image in your push notification. Each action button is uniquely identified. The code checks if your response identifier is equal to the `actionIndentifier`, and if so, knows that the user clicked the action button. -**Handling Push Notification action button responses**
+**Handling Push Notification Action Button Responses**
{% tabs %} {% tab Swift %} @@ -228,7 +228,7 @@ In Xcode, add the `App Groups` capability. If you haven’t had any workspaces i The following code snippets are a helpful reference on how to save and send custom events, custom attributes, and user attributes. This guide will be speaking in terms of `UserDefaults`, but the code representation will be in the form of the helper file `RemoteStorage`. There are additional helper files, `UserAttributes` and `EventName Dictionary`, that are used when sending and saving user attributes. {% tabs local %} -{% tab Custom events %} +{% tab Custom Events %} ##### Saving custom events @@ -369,7 +369,7 @@ func logPendingCustomEventsIfNecessary() { {% endsubtab %} {% endsubtabs %} {% endtab %} -{% tab Custom attributes %} +{% tab Custom Attributes %} ##### Saving custom attributes @@ -486,7 +486,7 @@ func setCustomAttributesWith(keysAndValues: [String: Any]) { {% endsubtab %} {% endsubtabs %} {% endtab %} -{% tab User attributes %} +{% tab User Attributes %} ##### Saving user attributes @@ -798,7 +798,7 @@ extension UserAttribute: Codable { {% endsubtab %} {% endsubtabs %} {% enddetails %} -{% details EventName dictionary helper file %} +{% details EventName Dictionary Helper File %} {% subtabs global %} {% subtab Swift %} ```swift diff --git a/_docs/_developer_guide/platform_wide/getting_started/architecture_overview.md b/_docs/_developer_guide/platform_wide/getting_started/architecture_overview.md index ff3476bbe69..314d1e348eb 100644 --- a/_docs/_developer_guide/platform_wide/getting_started/architecture_overview.md +++ b/_docs/_developer_guide/platform_wide/getting_started/architecture_overview.md @@ -98,7 +98,7 @@ The [Braze SDK][5] powers additional messaging channels: push, in-app messages, ![][13] ## Exporting data -Critically, all your users' interactions with Braze are tracked so you can measure your engagement and outreach. And after Braze has aggregated your data from all these sources, it can be exported back to your tech stack using a variety of tools, closing the loop. +Critically, all end-user interactions with Braze are tracked so you can measure your engagement and outreach. And once Braze has aggregated your data from all these sources, it can be exported back to your tech stack using a variety of tools, closing the loop. ### Currents [Currents][14] is an optional Braze add-on that provides a granular streaming export that continuously feeds other destinations of your stack. Currents is a per user per event raw data feed that exports data every five minutes, or every 15,000 events, whichever comes first. Examples of some downstream destinations for Currents would be Segment, S3, Redshift and Mixpanel, among others. diff --git a/_docs/_developer_guide/platform_wide/sdk_authentication.md b/_docs/_developer_guide/platform_wide/sdk_authentication.md index cf403f8f64c..6c24e1fe8e0 100644 --- a/_docs/_developer_guide/platform_wide/sdk_authentication.md +++ b/_docs/_developer_guide/platform_wide/sdk_authentication.md @@ -449,7 +449,7 @@ Once disabled, any pending failed SDK requests will eventually be retried by the #### Why does this feature use public/private keys instead of shared secrets? {#faq-shared-secrets} -When using shared secrets, anyone with access to that shared secret, such as the Braze dashboard page, would be able to generate tokens and impersonate your users. +When using shared secrets, anyone with access to that shared secret, such as the Braze dashboard page, would be able to generate tokens and impersonate your end-users. Instead, we use public/private keys so that not even Braze Employees (let alone your dashboard users) have access to your private keys. diff --git a/_docs/_docs_pages/cla.md b/_docs/_docs_pages/cla.md index 76cdf9d1750..c5b698f9e80 100644 --- a/_docs/_docs_pages/cla.md +++ b/_docs/_docs_pages/cla.md @@ -21,7 +21,7 @@ In consideration of the mutual covenants and agreements contained herein and oth 3. **Originality of Work.** You represent that each of Your Submissions is entirely Your original work. Should You wish to Submit materials that are not Your original work, You may Submit them separately to the Project if (a) You retain all copyright and license information that was in the materials as You received them, (b) in the description accompanying Your Submission, You include the phrase "Submission containing materials of a third party" followed by the name(s) of the third party and any licenses or other restrictions of which You are aware, and (c) You follow any other instructions in the Project's written guidelines concerning Submissions.

-4. **Your Employer.** References to "employer" in this Agreement include Your employer or anyone else for whom You are acting in making Your Submission, e.g., a contractor, vendor, or agent. If Your Submission is made in the course of Your work for an employer or Your employer has intellectual property rights in Your Submission by contract or applicable law, You must secure permission from Your employer to make the Submission before signing this Agreement. In that case, the term "You" in this Agreement will refer to You and the employer collectively. If You change employers in the future and desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement and secure permission from the new employer before Submitting those Submissions.

+4. **Your Employer.** References to "employer" in this Agreement include Your employer or anyone else for whom You are acting in making Your Submission, e.g., as a contractor, vendor, or agent. If Your Submission is made in the course of Your work for an employer or Your employer has intellectual property rights in Your Submission by contract or applicable law, You must secure permission from Your employer to make the Submission before signing this Agreement. In that case, the term "You" in this Agreement will refer to You and the employer collectively. If You change employers in the future and desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement and secure permission from the new employer before Submitting those Submissions.

5. **Licenses.**

**a. Copyright License.** You grant Braze, and those who receive the Submission directly or indirectly from Braze, a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable license in the Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third parties.

diff --git a/_docs/_help/release_notes/2024/6_25_24.md b/_docs/_help/release_notes/2024/6_25_24.md index adc6225fb12..a52a56f2ffd 100644 --- a/_docs/_help/release_notes/2024/6_25_24.md +++ b/_docs/_help/release_notes/2024/6_25_24.md @@ -37,7 +37,7 @@ Migrate your WhatsApp phone number between WhatsApp Business Accounts by using M {% multi_lang_include release_type.md release="General availability" %} -The new **Engagement by Device** report provides a breakdown of what devices your users are using to engage with your email. This data tracks email engagement across mobile, desktop, tablet, and other device types. Learn more about [the report and the email performance dashboard]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard). +The new **Engagement by Device** report provides a breakdown of what devices your users are using to engage with your email. This data tracks email engagement across mobile, desktop, tablet, and other device types. Learn more about [the report and the Email Performance Dashboard]({{site.baseurl}}/user_guide/data_and_analytics/analytics/email_performance_dashboard). ### WhatsApp and SMS Liquid properties in Canvas flow diff --git a/_docs/_hidden/compliance/sms_channel.md b/_docs/_hidden/compliance/sms_channel.md index cc90bb3f5ab..5b18fd73956 100644 --- a/_docs/_hidden/compliance/sms_channel.md +++ b/_docs/_hidden/compliance/sms_channel.md @@ -19,7 +19,7 @@ The following additional terms apply in relation to Customer’s use of the SMS **"Aggregators"** shall mean third-party intermediaries that transmit SMS/MMS Messages between SMS/MMS Providers and Carriers. -**"Carriers"** shall mean third-party wireless service providers (such as T-Mobile, AT&T, and similar). +**"Carriers"** shall mean third-party wireless service providers (e.g., T-Mobile, AT&T, etc.). **"SMS/MMS Providers"** shall mean Braze Sub-processors used in the transmission of SMS/MMS Messages, as identified at [www.braze.com/subprocessors](http://www.braze.com/subprocessors). diff --git a/_docs/_hidden/other/10dlc_application.md b/_docs/_hidden/other/10dlc_application.md index 5d0c54fabb5..0b2dae418cf 100644 --- a/_docs/_hidden/other/10dlc_application.md +++ b/_docs/_hidden/other/10dlc_application.md @@ -56,7 +56,7 @@ We'll need to register each SMS subscription group that contains a US long code | Customer Support Email Address | | Where can end users reach out via email for help and support | | Customer Support Phone Number | | Where can end users reach out via phone for help and support | | SMS Terms & Conditions URL | | {::nomarkdown}

To complete US A2P 10DLC Registration your SMS Terms page must include the following:

  1. Program (brand) name
  2. Consistent product disclosure on website and in message flow
  3. Message frequency (consistent with message flow)
  4. “Message and Data rates may apply” disclaimer
  5. HELP/STOP instructions OR customer care contact information

If this page is not live or any of the required disclosures are missing, a draft of SMS Terms along with the expected date of implementation to your live webpage will be needed to complete the registration process.

{:/} | -| How Do End Users Opt-In To Your SMS Campaign? (Please share how your users can opt into your SMS program, such as how end users can give consent to receive your SMS messages. If multiple opt-in methods are used, they must all be listed here.) | | {::nomarkdown}

Examples:

{:/} | +| How Do End Users Opt-In To Your SMS Campaign? (Please share how end-users can opt into your SMS program, such as how end users can give consent to receive your SMS messages. If multiple opt-in methods are used, they must all be listed here.) | | {::nomarkdown}

Examples:

{:/} | | Opt-In Keywords | | {::nomarkdown}

If end users can text in a keyword to start receiving SMS from this campaign, those keywords must be provided. By default, Braze sets up the following keywords:

Please let us know if you wish to add any keywords.

{:/} | | Opt-In Confirmation Message | | The auto-reply message sent to the end users to confirm their opt-in must be provided. The opt-in response should include the Brand name, confirmation of opt-in enrollment to a recurring message campaign, how to get help, and clear description of how to opt-out. (for example, Thanks for joining Braze Marketing Alerts! Message frequency varies. Message and data rates may apply. Reply HELP for help or STOP to opt out.) | | Opt-Out Keywords | | {::nomarkdown}

End users must be able to text in a keyword to stop receiving messages from this campaign. By default, Braze sets up the following keywords:

Please let us know if you wish to add any keywords.

{:/} | diff --git a/_docs/_hidden/other/credit_ratios.md b/_docs/_hidden/other/credit_ratios.md index f066075991c..75b24bb0e1e 100644 --- a/_docs/_hidden/other/credit_ratios.md +++ b/_docs/_hidden/other/credit_ratios.md @@ -7,7 +7,7 @@ hidden: true # WhatsApp Credit Ratios (Confidential) -> **WhatsApp** is a channel focused on 2-way messaging and thus anchors on conversations (instead of number of individual messages). A conversation is a 24-hour thread between a business and a user. The number of individual messages within a conversation does not impact credit usage. +> **WhatsApp** is a channel focused on 2-way messaging and thus anchors on conversations (instead of number of individual messages). A conversation is a 24-hour thread between a business and an end-user. The number of individual messages within a conversation does not impact credit usage. {% alert note %} In the event that Meta modifies its pricing or packaging for WhatsApp, Braze reserves the right to modify its credit ratios accordingly upon reasonable notice. @@ -17,7 +17,7 @@ In the event that Meta modifies its pricing or packaging for WhatsApp, Braze res **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. -**Service Conversations**: A user sends a message to the business. When the business sends a message in response, this begins the 24hr window. +**Service Conversations**: End-user sends a message to the business. When the business sends a message in response, this begins the 24hr window. **Authentication Conversations**: Enable businesses to authenticate users with one-time passcodes, potentially at multiple steps in the login process (for example, account verification, account recovery, integrity challenges) - Authentication conversations will only be supported on a case-by-case basis and Braze cannot guarantee specific SLAs. Additionally, Braze does not support pin generation. diff --git a/_docs/_hidden/private_betas/sms_traffic_pumping_fraud.md b/_docs/_hidden/private_betas/sms_traffic_pumping_fraud.md index 137822ca1fe..026111f5546 100644 --- a/_docs/_hidden/private_betas/sms_traffic_pumping_fraud.md +++ b/_docs/_hidden/private_betas/sms_traffic_pumping_fraud.md @@ -11,7 +11,7 @@ hidden: true SMS traffic pumping is a rising threat in the SMS space. It occurs when fraudsters find a way to trigger SMS message sends to phone numbers that are not associated with real customers in order to collect revenue tied to fraudulent message sending. Most often, they trigger high-volume SMS sends using online forms, such as forms for SMS opt-ins or one-time passwords for password resets or account login. -For example, if a brand has an SMS sign-up form on their website for customers to opt-in to receive text messages, a fraudster will enter fraudulent phone numbers into the form to trigger SMS messages. The fraudster uses premium rate phone numbers for these messages and claims a revenue share from the local mobile carrier, who is responsible for the delivery of the messages to users. This scheme generates fraudulent charges to the brand. +For example, if a brand has an SMS sign-up form on their website for customers to opt-in to receive text messages, a fraudster will enter fraudulent phone numbers into the form to trigger SMS messages. The fraudster uses premium rate phone numbers for these messages and claims a revenue share from the local mobile carrier, who is responsible for the delivery of the messages to end-users. This scheme generates fraudulent charges to the brand. ### What does Braze do to mitigate SMS pumping fraud? 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 bc32917b71c..0dfa959d097 100644 --- a/_docs/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md +++ b/_docs/_partners/data_and_infrastructure_agility/cohort_import/treasuredata.md @@ -11,7 +11,7 @@ search_tag: Partner > This article describes how to import user cohorts from Treasure Data to Braze so you can send targeted campaigns based on data that may only exist in your warehouse. {% alert important %} -This feature is currently in beta. For more information, contact your Treasure Data and Braze representatives. +This feature is currently in Beta. For more information, contact your Treasure Data and Braze representatives. {% endalert %} ## Prerequisites 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 9e0c4723fe2..820b5134860 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 @@ -70,7 +70,7 @@ In Braze, you will see your audience name in Lexer is now a value in your `lexer To create your segment, navigate to **Segment > + Create Segment** and select **Custom Attribute** as the filter. Next, select `lexer_audience` as your attribute and your desired Lexer audience name. When completed, **Save** your audience. -You can now add this newly created segment to future Braze campaigns and Canvases to target your users. +You can now add this newly created segment to future Braze campaigns and Canvases to target these end-users. [1]: {% image_buster /assets/img/lexer/braze_integrate_screen.png %} [2]: {{site.baseurl}}/api/basics/#company-secret-explanation 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 9c15d5563dc..894c61c6942 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 @@ -14,7 +14,7 @@ search_tag: Partner The Braze and Treasure Data integration allows you to write job results from Treasure Data directly to Braze, letting you: * **Map external IDs**: Map IDs to the Braze user account from your CRM system. -* **Manage opt-out**: When a user updates their consent choosing not to participate. +* **Manage opt-out**: When an end-user updates their consent choosing not to participate. * **Upload your tracking of events, purchases, or custom profile attributes**. This information can help you build precise customer segments that enhance the user experience for your campaigns. ## Prerequisites 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 23f5fc71a90..1cb6288355c 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 @@ -58,7 +58,7 @@ Next, you must create and define this segment within Braze: ![In the Braze segment builder, you can find the imported segments set as custom attributes.][3] -You can now add this newly created segment to future Braze campaigns and Canvases to target your users. +You can now add this newly created segment to future Braze campaigns and Canvases to target these end-users. [1]: {% image_buster /assets/img/zeotap/zeotap1.png %} [2]: {% image_buster /assets/img/zeotap/zeotap2.png %} 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 e1427130ffa..fbfb4f63f5f 100644 --- a/_docs/_partners/data_and_infrastructure_agility/data_privacy/transcend.md +++ b/_docs/_partners/data_and_infrastructure_agility/data_privacy/transcend.md @@ -12,7 +12,7 @@ search_tag: Partner > Transcend is a data privacy infrastructure company that makes it simple for companies to give their users control over their data, automatically fulfilling data subject requests inside companies across all of their data systems and vendors. -The Braze and Transcend partnership helps users automate privacy requests by orchestrating data across dozens of data systems, helping teams comply with regulations like GDPR and CCPA. Transcend provides end users with a control panel, or privacy center, hosted at `privacy.\.com` where users can manage their privacy preferences, export their data, or delete it. +The Braze and Transcend partnership helps users automate privacy requests by orchestrating data across dozens of data systems, helping teams comply with regulations like GDPR and CCPA. Transcend provides end-users with a control panel, or privacy center, hosted at `privacy.\.com` where users can manage their privacy preferences, export their data, or delete it. ## Prerequisites @@ -39,7 +39,7 @@ If identifiers are not enabled correctly, Transcend may not process requests for {% endalert %} ### Step 2: Test requests -Transcend recommends testing requests across your Data Map before you start processing requests from your users. +Transcend recommends testing requests across your Data Map before you start processing requests from end-users. 1. Go to **Privacy Center** in Transcend and click **View your Privacy Center**.

2. From your **Privacy Center**, click **Take Control**, then **Download my data**. Enter your email or log in to authenticate yourself before submitting the request.

3. Check your email for a message from Transcend. You'll be asked to click on a verification link to verify the request.

diff --git a/_docs/_partners/data_and_infrastructure_agility/support/pypestream.md b/_docs/_partners/data_and_infrastructure_agility/support/pypestream.md index 1da7c9d9cf9..1fa7794047d 100644 --- a/_docs/_partners/data_and_infrastructure_agility/support/pypestream.md +++ b/_docs/_partners/data_and_infrastructure_agility/support/pypestream.md @@ -28,7 +28,7 @@ The Braze and Pypestream integration allows you to seamlessly orchestrate the en The Braze and Pypestream partnership can be used in your Canvases to achieve common use cases like: * **Intelligent retargeting**: Retarget users with Braze Canvas after their conversational engagement with your brand by leveraging all the rich data points collected via Pypestream. * **Dynamic targeting**: Reach out to existing and prospective customers based on their specific cohorts and segments, serving them with tailored conversational experiences via Pypestream. -* **Contextual customer insights**: After a user (existing or prospective customer) engages on your website, combine webpage tags ingested from the Pypestream Event Listener with customer data stored within Braze to provide a fully-personalized and contextual conversational interaction. +* **Contextual customer insights**: After an end-user (existing or prospective customer) engages on your website, combine webpage tags ingested from the Pypestream Event Listener with customer data stored within Braze to provide a fully-personalized and contextual conversational interaction. ## Integration @@ -276,4 +276,4 @@ class BrazeExample: ### Step 3: Update solution flows to redirect upon success/failure of action node -Lastly, in each solution's design, you can route users to nodes based on if the action node API call was successful. If the action node receives an error message, your user should be handled with care. +Lastly, in each solution's design, you can route users to nodes based on if the action node API call was successful. If the action node receives an error message, the end-user should be handled with care. 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 106de340eaa..c120b982340 100644 --- a/_docs/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md +++ b/_docs/_partners/message_orchestration/additional_channels/instant_chat/sendbird.md @@ -100,7 +100,7 @@ In Braze, from **Templates & Media**, go to **Webhook Templates** and choose the To integrate the notifications' delivery and open status event with a campaign’s conversion metric, add a custom event on the Braze dashboard. -1. From the Braze dashboard, go to **Settings** > **Manage Settings** > **Custom Events**, and click **+ Add Custom Event**. +1. From the Braze dashboard, go to **Settings > Manage Settings > Custom Events**, and click **+ Add Custom Event**. 2. After you’ve created a custom event, click **Manage Properties**, add a property named "status", and choose "String" as the property type. 3. When you compose a notification in campaigns or Canvases, enter the name of the custom event into the **Event Name** field. diff --git a/_docs/_partners/message_orchestration/additional_channels/retargeting/quikly.md b/_docs/_partners/message_orchestration/additional_channels/retargeting/quikly.md index cf07a47f0ca..7cad2b239a4 100644 --- a/_docs/_partners/message_orchestration/additional_channels/retargeting/quikly.md +++ b/_docs/_partners/message_orchestration/additional_channels/retargeting/quikly.md @@ -119,7 +119,7 @@ Authorization: Bearer YOUR-REST-API-KEY {% enddetails %} {% endtab %} -{% tab Custom attributes %} +{% tab Custom Attributes %} ### Custom attributes Depending on your Braze implementation, you may want events within Quikly activation to cascade through Braze for further processing. For example, you may wish to apply a custom user attribute based on what level or incentive was achieved in Quikly activation, allowing you to display the relevant Content Card when they open your app or log in to your website. Quikly will work with you directly to implement these integrations. 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 606aaeff623..2ae4000d88b 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 @@ -861,7 +861,7 @@ After the app installation is complete, Braze automatically creates your webhook ## Supported Shopify custom attributes {% tabs local %} -{% tab Shopify custom attributes %} +{% tab Shopify Custom Attributes %} | Attribute Name | Description | | --- | --- | | `shopify_tags` | Tags that the shop owner has attached to the customer, formatted as a string of comma-separated values. A customer can have up to 250 tags. Each tag can have up to 255 characters. | @@ -902,7 +902,7 @@ After selecting your custom attribute, input a default value and copy the Liquid ``` {% endtab %} -{% tab Example payload %} +{% tab Example Payload %} {% subtabs %} {% subtab Shopify Tags %} ```json diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes.md index 87b9499e932..c355c8aed27 100644 --- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes.md +++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/voucherify/voucherify_distribution_with_braze_custom_attributes.md @@ -45,7 +45,7 @@ You can distribute codes to Braze using two modes: - **Manual mode** - Define an **automated workflow** that triggers code delivery in response to an action taken by your users. -In both manual and automatic modes, Voucherify sends unique codes with their attributes and assigns them to Braze custom attributes in users' profiles. +In both manual and automatic modes, Voucherify sends unique codes with their attributes and assigns them to Braze Custom Attributes in users' profiles. ![Map fields to custom attributes]({% image_buster /assets/img/voucherify/voucherify_custom_attributes_fields_mapping.png %}) 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..97918197c54 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 @@ -25,7 +25,7 @@ For more information on Stories, the Movable Ink Customer Data API, and how Mova | Movable Ink account | A Movable Ink account is required to take advantage of this partnership. | | Movable Ink API credentials | Movable Ink's Solutions team will generate API credentials for you. The API credentials consist of:{::nomarkdown}{:/} 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. | +| 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} ## Integration 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 085b9f60da9..17b53628b39 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 @@ -131,7 +131,7 @@ When previewing a message, the **View PII** permission is not applied, so users You can use this setting to set preferences for whether or not certain fields should be deleted during the user delete process for events. These preferences only impact data for users that have been deleted from Braze. -When a user is deleted, Braze removes all PII from events data but retains the anonymized data for analytics purposes. Some user-defined fields may contain PII if you send your user information to Braze. If these fields contain PII, you can opt to delete the data when event data is anonymized for deleted users; if the fields contain no PII, they can be retained for analytics. +When a user is deleted, Braze removes all PII from events data but retains the anonymized data for analytics purposes. Some user-defined fields may contain PII if you send end-user information to Braze. If these fields contain PII, you can opt to delete the data when event data is anonymized for deleted users; if the fields contain no PII, they can be retained for analytics. You are responsible for determining the correct preferences for your workspace. The best way to determine the appropriate settings is to review with internal teams sending events data to Braze and to teams using message extras in Braze to confirm whether the fields may contain PII. diff --git a/_docs/_user_guide/administrative/app_settings/email_settings.md b/_docs/_user_guide/administrative/app_settings/email_settings.md index 8fcb95a4ec6..763db8a14b7 100644 --- a/_docs/_user_guide/administrative/app_settings/email_settings.md +++ b/_docs/_user_guide/administrative/app_settings/email_settings.md @@ -65,7 +65,7 @@ If you require that all email messages sent from Braze have a BCC address includ [![Braze Learning course]({% image_buster /assets/img/bl_icon3.png %})](https://learning.braze.com/email-open-tracking-pixel/){: style="float:right;width:120px;border:0;" class="noimgborder"} -The email opening tracking pixel is an invisible 1 x 1 px image that automatically gets inserted into your email HTML. This pixel helps Braze detect whether your users have opened your email. Email open information can be very useful, helping users determine effective marketing strategies by understanding the corresponding open rates. +The email opening tracking pixel is an invisible 1 x 1 px image that automatically gets inserted into your email HTML. This pixel helps Braze detect whether the end-users have opened your email. Email open information can be very useful, helping users determine effective marketing strategies by understanding the corresponding open rates. ### Placing the tracking pixel 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 70593513c10..c88200fcba8 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 @@ -27,7 +27,7 @@ If you are using the [older navigation]({{site.baseurl}}/navigation), **Internal Enter the **Team Name**. If desired, use the **Define Team** field to select a custom attribute, location, or language to further define what user data that team has access to. For example, a possible use case is to perform [testing with teams](#testing-with-teams) by creating a development team that only has access to test users, identified by a custom attribute. -If a team is defined by a custom attribute, language, or country, you can then use the team to filter your users for features like campaigns, Canvases, Content Cards, segments, and more. For more, see [Assigning team tags](#tags-and-filters). +If a team is defined by a custom attribute, language, or country, you can then use the team to filter end-users for features like campaigns, Canvases, Content Cards, segments, and more. For more, see [Assigning team tags](#tags-and-filters). ## Assigning users to teams 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 8dd7cfe2db0..1ad267a3509 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 @@ -68,7 +68,7 @@ This event occurs when an WhatsApp message is read by the end user. WhatsApp, Delivery {% endapitags %} -This event occurs when an WhatsApp message sent made it successfully to the user's device. +This event occurs when an WhatsApp message sent made it successfully to the end-users device. {% tabs %} {% tab Braze Standard REST %} @@ -4508,7 +4508,7 @@ This event occurs when an email send request was successfully communicated betwe Email, Delivery {% endapitags %} -This event occurs when an email sent made it successfully to the user's inbox. +This event occurs when an email sent made it successfully to the end-users inbox. {% tabs %} {% tab Braze Standard REST %} @@ -5888,7 +5888,7 @@ This event occurs when an Internet Service Provider returns a soft bounce. A sof Email, Spam {% endapitags %} -This event occurs when the user selects 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. +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 Braze Standard REST %} @@ -6144,7 +6144,7 @@ The behavior for `dispatch_id` differs between Canvas and campaigns because Braz Email, Subscription {% endapitags %} -This event occurs when the user has clicked "unsubscribe" from the email. +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, it will not trigger an event on Currents. @@ -11007,7 +11007,7 @@ Subscription groups are only available for email, SMS, and WhatsApp channels at | REST API | REST API endpoints | | CSV import | CSV user import | | Preference Center | When a user is updated from the preference center | -| Inbound Message | When a user is updated by inbound messages they send through channels such as SMS | +| Inbound Message | When a user is updated by inbound messages from end-users through channels such as SMS | | 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 | @@ -11261,7 +11261,7 @@ This event occurs when Braze receives a request to update the global subscriptio | REST API | REST API endpoints | | CSV import | CSV user import | | Preference Center | When a user is updated from the preference center | -| Inbound Message | When a user is updated by inbound messages they send through channels, such as SMS | +| Inbound Message | When a user is updated by inbound messages from end-users through channels, such as SMS | | 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 | diff --git a/_docs/_user_guide/data_and_analytics/cloud_ingestion/connected_sources.md b/_docs/_user_guide/data_and_analytics/cloud_ingestion/connected_sources.md index 1b8563c809f..16b3f5b9d54 100644 --- a/_docs/_user_guide/data_and_analytics/cloud_ingestion/connected_sources.md +++ b/_docs/_user_guide/data_and_analytics/cloud_ingestion/connected_sources.md @@ -487,5 +487,5 @@ You may set up multiple sources with Braze, but each source should be configured Once the source is created, it can be used to create one or more CDI Segments. For more information on creating a segment with this source, see the [CDI Segments documentation]({{site.baseurl}}/user_guide/engagement_tools/segments/segment_extension/cdi_segments/). {% alert note %} -If queries are consistently timing out and you have set a maximum runtime of 60 minutes, consider trying to optimize your query execution time or dedicating more compute resources (such as a larger warehouse) to the Braze user. +If queries are consistently timing out and you have set a maximum runtime of 60 minutes, consider trying to optimize your query execution time or dedicating more compute resources (e.g., a larger warehouse) to the Braze user. {% endalert %} diff --git a/_docs/_user_guide/data_and_analytics/cloud_ingestion/file_storage_integrations.md b/_docs/_user_guide/data_and_analytics/cloud_ingestion/file_storage_integrations.md index 3d6023a4ee0..a85af235d7d 100644 --- a/_docs/_user_guide/data_and_analytics/cloud_ingestion/file_storage_integrations.md +++ b/_docs/_user_guide/data_and_analytics/cloud_ingestion/file_storage_integrations.md @@ -215,7 +215,7 @@ Files added to the S3 source bucket should not exceed 512MB. Files larger than 5 Every line in your source file must contain valid JSON, or the file will be skipped. {% endalert %} {% endtab %} -{% tab JSON custom events %} +{% tab JSON Custom Events %} ``` json {"external_id":"s3-qa-0","payload":"{\"app_id\": \"YOUR_APP_ID\", \"name\": \"view-206\", \"time\": \"2024-04-02T14:34:08\", \"properties\": {\"bool_value\": false, \"preceding_event\": \"unsubscribe\", \"important_number\": 206}}"} {"external_id":"s3-qa-1","payload":"{\"app_id\": \"YOUR_APP_ID\", \"name\": \"view-206\", \"time\": \"2024-04-02T14:34:08\", \"properties\": {\"bool_value\": false, \"preceding_event\": \"unsubscribe\", \"important_number\": 206}}"} @@ -224,7 +224,7 @@ Every line in your source file must contain valid JSON, or the file will be skip Every line in your source file must contain valid JSON, or the file will be skipped. {% endalert %} {% endtab %} -{% tab JSON purchase events %} +{% tab JSON Purchase Events %} ``` json {"external_id":"s3-qa-0","payload":"{\"app_id\": \"YOUR_APP_ID\", \"product_id\": \"product-11\", \"currency\": \"BSD\", \"price\": 8.511527858335066, \"time\": \"2024-04-02T14:34:08\", \"quantity\": 19, \"properties\": {\"is_a_boolean\": true, \"important_number\": 40, \"preceding_event\": \"click\"}}"} {"external_id":"s3-qa-1","payload":"{\"app_id\": \"YOUR_APP_ID\", \"product_id\": \"product-11\", \"currency\": \"BSD\", \"price\": 8.511527858335066, \"time\": \"2024-04-02T14:34:08\", \"quantity\": 19, \"properties\": {\"is_a_boolean\": true, \"important_number\": 40, \"preceding_event\": \"click\"}}"} @@ -234,7 +234,7 @@ Every line in your source file must contain valid JSON, or the file will be skip {% endalert %} {% endtab %} -{% tab CSV attributes %} +{% tab CSV Attributes %} ``` csv external_id,payload s3-qa-load-0-d0daa196-cdf5-4a69-84ae-4797303aee75,"{""name"": ""SNXIM"", ""age"": 54, ""subscriber"": true, ""retention"": {""previous_purchases"": 19, ""vip"": true}, ""last_visit"": ""2023-08-08T16:03:26.598806""}" diff --git a/_docs/_user_guide/data_and_analytics/cloud_ingestion/integrations.md b/_docs/_user_guide/data_and_analytics/cloud_ingestion/integrations.md index 5111877797f..460853a3fb9 100644 --- a/_docs/_user_guide/data_and_analytics/cloud_ingestion/integrations.md +++ b/_docs/_user_guide/data_and_analytics/cloud_ingestion/integrations.md @@ -405,7 +405,7 @@ Contact emails will only receive notifications of global or sync-level errors su ![]({% image_buster /assets/img/cloud_ingestion/ingestion_2.png %}) -You will also choose the data type and sync frequency. Frequency can be anywhere from every 15 minutes to once per month. We'll use the time zone configured in your Braze dashboard to schedule the recurring sync. Supported data types are custom attributes, custom events, and purchase events, and the data type for a sync cannot be changed after creation. +You will also choose the data type and sync frequency. Frequency can be anywhere from every 15 minutes to once per month. We'll use the time zone configured in your Braze dashboard to schedule the recurring sync. Supported data types are Custom Attributes, Custom Events, and Purchase Events, and the data type for a sync cannot be changed after creation. #### Add a public key to the Braze user At this point, you must go back to Snowflake to complete the setup. Add the public key displayed on the dashboard to the user you created for Braze to connect to Snowflake. 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 807777760ad..869620b3de8 100644 --- a/_docs/_user_guide/data_and_analytics/cloud_ingestion/overview.md +++ b/_docs/_user_guide/data_and_analytics/cloud_ingestion/overview.md @@ -483,7 +483,7 @@ Fields within the payload should follow the same format as the corresponding `/u Note the special requirement for [capturing dates]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/nested_custom_attribute_support/#capturing-dates-as-object-properties) in nested attributes. {% tabs local %} -{% tab Nested custom attributes %} +{% tab Nested Custom Attributes %} You may include nested custom attributes in the payload column for a custom attributes sync. ```json diff --git a/_docs/_user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle.md b/_docs/_user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle.md index 33fc68841ea..068d1217258 100644 --- a/_docs/_user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle.md +++ b/_docs/_user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle.md @@ -71,7 +71,7 @@ Unlike an `external_id`, an alias can be updated with a new name for a given lab ![Two different user profiles for separate users with the same user alias label but different alias names][29] -User aliases also allow you to tag anonymous users with an identifier. For example, if a user provides your ecommerce site with their email address but hasn't yet signed up, the email address can be used as an alias for that anonymous user. These users can then be exported using their aliases or referenced by the API. +User aliases also allow you to tag anonymous users with an identifier. For example, if a user provides your e-commerce site with their email address but hasn't yet signed up, the email address can be used as an alias for that anonymous user. These users can then be exported using their aliases or referenced by the API. If an anonymous user profile with an alias is later recognized with an `external_id`, they will be treated as a normal identified user profile, but will retain their existing alias and can still be referenced by that alias. diff --git a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas.md b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas.md index 764e6b26b84..0c3f6b9fb03 100644 --- a/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas.md +++ b/_docs/_user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas.md @@ -98,14 +98,14 @@ You can choose one of three ways in which users can enter your Canvas. #### Entry schedule types {% tabs local %} - {% tab Scheduled delivery %} + {% tab Scheduled Delivery %} With scheduled delivery, users will enter on a time schedule, similarly to how you would schedule a campaign. You can enroll users in a Canvas as soon as it is launched, enter them into your journey at some point in the future, or on a recurring basis (daily, weekly, or monthly). In this example, based on the time-based options, users will enter this Canvas every Tuesday at 12 pm in their local time zone every week, beginning November 14, 2023 until December 31, 2023. ![]({% image_buster /assets/img_archive/Canvas_Scheduled_Delivery.png %}) {% endtab %} - {% tab Action-based delivery %} + {% tab Action-Based Delivery %} With action-based delivery, users will enter the Canvas and begin receiving messages when they take particular actions, such as opening your app, making a purchase, or triggering a custom event. You can control other aspects of the Canvas behavior from the **Entry Audience** window, including rules for re-eligibility and frequency capping settings. Note that action-based delivery is unavailable for Canvas components with in-app messages. @@ -113,7 +113,7 @@ You can choose one of three ways in which users can enter your Canvas. ![An example of action-based delivery. Users will enter the Canvas if they make a purchase with an entry window beginning at 1:30 pm on June 10, 2023.]({% image_buster /assets/img_archive/Canvas_Action_Based_Delivery.png %}) {% endtab %} - {% tab API-triggered delivery %} + {% tab API-Triggered Delivery %} With API-triggered delivery, users will enter your Canvas and begin receiving messages after they have been added using the [`/canvas/trigger/send` endpoint]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/) via the API. In the dashboard, you can find an example cURL request that does this as well as assign optional [`canvas_entry_properties`]({{site.baseurl}}/api/endpoints/messaging/send_messages/post_send_triggered_canvases/) using the [Canvas entry properties object]({{site.baseurl}}/api/objects_filters/canvas_entry_properties_object/). ![An example of API-triggered delivery with a Canvas ID and an example of a cURL request.]({% image_buster /assets/img_archive/Canvas_API_Triggered_Delivery.png %}) @@ -300,7 +300,7 @@ In this example, we have our Canvas divided into two variants. Variant 1 has 70% ### Intelligent Selection for Canvas -Intelligent Selection capabilities are now available within multivariate Canvases. Similar to the [Intelligent Selection][18a] feature for multivariate campaigns, Intelligent Selection for Canvas analyzes the performance of each Canvas variant and adjusts the percentage of users being funneled through each variant. This distribution is based off each variant's performance metrics to maximize the total expected number of conversions. +Intelligent Selection capabilities are now available within multivariate Canvases. Similar to the [Intelligent Selection][18a] feature for multivariate Campaigns, Intelligent Selection for Canvas analyzes the performance of each Canvas variant and adjusts the percentage of users being funneled through each variant. This distribution is based off each variant's performance metrics to maximize the total expected number of conversions. Keep in mind that multivariate Canvases allow you to test more than copy, but timing and channels as well. Through Intelligent Selection, you can test Canvases more efficiently and have confidence that your users will be sent on the best possible Canvas journey. diff --git a/_docs/_user_guide/engagement_tools/templates_and_media/media_library.md b/_docs/_user_guide/engagement_tools/templates_and_media/media_library.md index 0e2eb574f3c..3b25788acf9 100644 --- a/_docs/_user_guide/engagement_tools/templates_and_media/media_library.md +++ b/_docs/_user_guide/engagement_tools/templates_and_media/media_library.md @@ -72,7 +72,7 @@ For more information, refer to [In-app message creative details]({{site.baseurl} The media library acts as your dashboard's centralized location for assets, as all images are uploaded directly to it. This lets you re-use images across different messages. -![Two common ways of accessing the media library depending on the message composer. One shows the email drag-and-drop editor with the title "Images and GIFs" and a button to "Add from Media Library". The other shows the standard editors, such as push and in-app messages, with the title "Media" and a button to "Add Image".][1.5]{: style="border:none"} +![Two common ways of accessing the media library depending on the message composer. One shows the email Drag and Drop Editor with the title "Images and GIFs" and a button to "Add from Media Library". The other shows the standard editors, such as push and in-app messages, with the title "Media" and a button to "Add Image".][1.5]{: style="border:none"} ## Generate an image using AI {#generate-ai} 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 ec3a7c97d13..9e1a42d3bed 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 @@ -21,7 +21,7 @@ If you use SendGrid as an email provider, you can send emails to Apple without m ![Option to allowlist individual email addresses on the Apple Certificate page.]({% image_buster /assets/img/email-relay-whitelabel-address.png %}) -The address should be formatted as: `bounces+@`(such as `bounces+1234567@braze.online.docs.com`). After the address is added to your Apple Certificate page, emails from this domain will be delivered via the Apple Private Relay system. +The address should be formatted as: `bounces+@`(e.g., `bounces+1234567@braze.online.docs.com`). After the address is added to your Apple Certificate page, emails from this domain will be delivered via the Apple Private Relay system. {% alert important %} If your desired "From" address is an `abmail` address, include that in your subdomain. For example, use `abmail.docs.braze.com` instead of `docs.braze.com`. This might not be the case for your address. Check your DNS records in SendGrid. diff --git a/_docs/_user_guide/message_building_by_channel/email/best_practices/guidelines_and_tips.md b/_docs/_user_guide/message_building_by_channel/email/best_practices/guidelines_and_tips.md index 74e7ed6fa8d..012a44c4ead 100644 --- a/_docs/_user_guide/message_building_by_channel/email/best_practices/guidelines_and_tips.md +++ b/_docs/_user_guide/message_building_by_channel/email/best_practices/guidelines_and_tips.md @@ -29,7 +29,7 @@ Since spam filters watch for both an HTML and a plain text version of a message, ### Email validation {% alert important %} -Validation is used for dashboard email addresses, your users' email addresses, and from and reply-to addresses done of an email message. +Validation is used for dashboard email addresses, end-user email addresses (your customers), and from and reply-to addresses done of an email message. {% endalert %} Email validation is done when a user's email address has been updated or is being imported into Braze via API, CSV upload, SDK, or modified in the dashboard. Note that your email addresses cannot include white spaces, and if send using the API, whitespaces will result in a 400 error. diff --git a/_docs/_user_guide/message_building_by_channel/email/drag_and_drop/overview.md b/_docs/_user_guide/message_building_by_channel/email/drag_and_drop/overview.md index 19a92a2ca5c..5cd0fc7c9d0 100644 --- a/_docs/_user_guide/message_building_by_channel/email/drag_and_drop/overview.md +++ b/_docs/_user_guide/message_building_by_channel/email/drag_and_drop/overview.md @@ -200,7 +200,7 @@ Basic Liquid is supported in the drag-and-drop email editor. To add personalizat 1. Select **Personalization** under the **Content** section. 2. Select the personalization type. This includes default (standard) attributes, device attributes, custom attributes, and more. 3. Search for the attribute to be added. -4. Copy your generated Liquid snippet and paste it into a Content Block in your email body. +4. Copy your generated Liquid snippet and paste it into a content block in your email body. Liquid personalization is not supported for image blocks and button link type fields. diff --git a/_docs/_user_guide/message_building_by_channel/email/email_setup/email_validation.md b/_docs/_user_guide/message_building_by_channel/email/email_setup/email_validation.md index 00f9a774d61..cf24383c5e4 100644 --- a/_docs/_user_guide/message_building_by_channel/email/email_setup/email_validation.md +++ b/_docs/_user_guide/message_building_by_channel/email/email_setup/email_validation.md @@ -13,7 +13,7 @@ channel: email > This reference article covers local and host part validation rules for email addresses. -Validation is used for dashboard email addresses, your users' email addresses, and from and reply-to addresses done of an email message. Email validation is performed when a user's email address has been updated or is being imported into Braze via API, CSV upload, or SDK, or modified in the dashboard. Note that your email addresses cannot include whitespaces. If you're using the API, whitespaces will result in a `400` error. +Validation is used for dashboard email addresses, end-user email addresses (your customers), and from and reply-to addresses done of an email message. Email validation is performed when a user's email address has been updated or is being imported into Braze via API, CSV upload, or SDK, or modified in the dashboard. Note that your email addresses cannot include whitespaces. If you're using the API, whitespaces will result in a `400` error. Braze does not accept certain characters and recognizes them as invalid. If an email is bounced, Braze marks the email as invalid and the subscription status is not changed. 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 4e7c23ba141..0e062cf7cfb 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 @@ -79,7 +79,7 @@ When a user updates their email address, their subscription state will be set to ## Subscription groups -Subscription groups are segment filters that can further narrow your audience from the [global subscription states](#subscription-states). You can add up to 100 subscription groups per workspace. These groups allow you to present more granular subscription options to your users. +Subscription groups are segment filters that can further narrow your audience from the [global subscription states](#subscription-states). You can add up to 100 subscription groups per workspace. These groups allow you to present more granular subscription options to end-users. For example, suppose you send out multiple categories of email campaigns (promotional, newsletter, or product updates). In that case, you can use subscription groups to let your customers pick and choose which email categories they want to subscribe or unsubscribe from in bulk from a single page, using an [email preference center](#email-preference-center). Alternatively, you could use subscription groups to let your customers choose how frequently they want to receive emails from you, by creating subscription groups for daily, weekly, or monthly emails. 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 fbed09cb79e..75bf90ba010 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 @@ -395,7 +395,7 @@ Next, check out [In-app message reporting]({{site.baseurl}}/user_guide/message_b Braze values reliability and speed. Just like we suggest you send only the data you need to Braze, we also recommend turning off any campaigns that are no longer adding any value to your brand. -Processing action-based in-app message campaigns that are still in an active state but no longer sending messages or are no longer needed slows down the overall performance of the Braze services for you and other customers. This extra time needed to process these large numbers of idle campaigns means that any in-app messages will take longer to appear on your user's devices, which impacts your user's experience. +Processing action-based in-app message campaigns that are still in an active state but no longer sending messages or are no longer needed slows down the overall performance of the Braze services for you and other customers. This extra time needed to process these large numbers of idle campaigns means that any in-app messages will take longer to appear on the end-user's devices, which impacts the end user's experience. {% alert important %} There is a limit of 200 active, action-based in-app message campaigns per workspace to optimize the speed of message delivery and to prevent timeouts. This does not apply to Canvases. diff --git a/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form.md b/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form.md index c4c0e055036..46276d6a135 100644 --- a/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form.md +++ b/_docs/_user_guide/message_building_by_channel/in-app_messages/traditional/customize/email_capture_form.md @@ -12,7 +12,7 @@ channel: > Email capture messages allow you to easily prompt users of your site to submit their email address, after which it will be available within their user profile for use in all your messaging campaigns. -When a user enters their email address to this form, the email address will get added to their user profile. +When an end-user enters their email address to this form, the email address will get added to their user profile. - For [anonymous users]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_profile_lifecycle/#anonymous-user-profiles) who don't yet have an account, the email address will live on the anonymous user profile that is tied to the user's device. - If an email address already exists on the user profile, then the existing email address will be overwritten by the newly entered email address. 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 5dcde2a9d6a..185f7aa8ab0 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 @@ -25,7 +25,7 @@ Not sure whether your message should be sent using a campaign or a Canvas? Campa **Steps:** -1. Go to **Messaging** > **Campaigns** and select **Create Campaign**. +1. Go to **Messaging** > **Campaigns** and click **Create Campaign**. 2. Select **Push Notification**, 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. 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 0b1c6b35031..ca5265756c8 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 @@ -15,7 +15,7 @@ channel: ## Two-way messaging (custom keyword responses) -Two-way messaging allows you to send messages and process the responses to those messages. It requires your users to send a keyword to Braze, to which that user will receive an automatic reply. Applied correctly, two-way messaging can be a simple, immediate, and dynamic solution to customer marketing, saving time and resources along the way. +Two-way messaging allows you to send messages and process the responses to those messages. It requires end-users to send a keyword to Braze, to which that user will receive an automatic reply. Applied correctly, two-way messaging can be a simple, immediate, and dynamic solution to customer marketing, saving time and resources along the way. ## Managing keywords and auto responses diff --git a/_docs/_user_guide/message_building_by_channel/sms/sms_setup/terms.md b/_docs/_user_guide/message_building_by_channel/sms/sms_setup/terms.md index 843de51af78..f85fcace770 100644 --- a/_docs/_user_guide/message_building_by_channel/sms/sms_setup/terms.md +++ b/_docs/_user_guide/message_building_by_channel/sms/sms_setup/terms.md @@ -28,7 +28,7 @@ glossaries: - name: Message Segments description: A message segment is a grouping of up to a defined number of characters (160 for GSM-7 encoding; 67 for UCS-2 encoding) that will be sent in a single SMS dispatch. If you dispatch an SMS with 161 characters using GSM-7 encoding, you will see that there are two (2) message segments that were sent. Sending multiple message segments may result in additional charges. - name: Message Service - description: A collection of long codes, short codes, and alphanumeric IDs used to send your SMS message with Braze. + description: A collection of long codes, short codes, and alpha-numeric IDs used to send your SMS message with Braze. - name: Keyword description: "A short word that is sent to a short or long code to interact with a pre-defined SMS program or to request to OPT-OUT of a specific program or all programs on a code. For example, STOP. Keywords should
- be alphanumeric
- have no spaces
- be less than 10 characters.

A specific keyword and short code combination may only be used on one active program at a time. If a keyword is entered that is already in use by another program, a validation error will appear.

There are two mandatory keyword categories that all SMS content providers must comply with: STOP and HELP." - name: Mandatory Keyword HELP 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 dd9fa035928..ff55aa5c31d 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 @@ -65,7 +65,7 @@ The following table describes the four different HTTP methods you can specify in In Braze, you can create a webhook as a webhook campaign, API campaign, or Canvas component. {% tabs %} -{% tab Webhook campaign %} +{% tab Webhook Campaign %} 1. In the Braze dashboard, go to **Campaigns**. 2. Click **Create Campaign** and select **Webhook**. @@ -73,7 +73,7 @@ In Braze, you can create a webhook as a webhook campaign, API campaign, or Canva Refer to [Creating a webhook]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/) for more information. {% endtab %} -{% tab API campaign %} +{% tab API Campaign %} 1. In the Braze dashboard, go to **Campaigns**. 2. Click **Create Campaign** and select **API Campaign**. @@ -83,7 +83,7 @@ Refer to [Creating a webhook]({{site.baseurl}}/user_guide/message_building_by_ch Refer to [Creating a webhook]({{site.baseurl}}/user_guide/message_building_by_channel/webhooks/creating_a_webhook/) for more information. {% endtab %} -{% tab Canvas component %} +{% tab Canvas Component %} 1. In your Canvas, create a new component. 2. In the **Message** section of your component, select **Webhook**. diff --git a/_docs/_user_guide/message_building_by_channel/whatsapp/faqs.md b/_docs/_user_guide/message_building_by_channel/whatsapp/faqs.md index 1cf306863a3..dba85ceaa09 100644 --- a/_docs/_user_guide/message_building_by_channel/whatsapp/faqs.md +++ b/_docs/_user_guide/message_building_by_channel/whatsapp/faqs.md @@ -48,25 +48,25 @@ Refer to Meta's requirements for [phone numbers](https://developers.facebook.com No. A phone number cannot be shared across multiple WABAs. #### Do I need a specific type of phone number to send messages to specific countries? -No. WhatsApp allows you to send messages to your users from any supported phone number in any country. Refer to Meta's requirements for [phone numbers](https://developers.facebook.com/docs/whatsapp/phone-numbers) for more information. +No. WhatsApp allows you to send messages to end-users from any supported phone number in any country. Refer to Meta's requirements for [phone numbers](https://developers.facebook.com/docs/whatsapp/phone-numbers) for more information. #### Do I need to use a country-specific phone number to send to certain countries? -No. With WhatsApp, any supported phone number can send to your users in any supported country. +No. With WhatsApp, any supported phone number can send to end-users in any supported country. ### Opt-in and subscription management -#### Do I need to collect opt-in to send marketing messages to my users on WhatsApp? -Yes, WhatsApp requires businesses to [collect opt-in consent](https://developers.facebook.com/docs/whatsapp/overview/getting-opt-in/) to send marketing messages to your users. +#### Do I need to collect opt-in to send marketing messages to end-users on WhatsApp? +Yes, WhatsApp requires businesses to [collect opt-in consent](https://developers.facebook.com/docs/whatsapp/overview/getting-opt-in/) to send marketing messages to end-users. -#### Can I proactively message my users on WhatsApp to collect opt-in consent? -If you choose to proactively message your users, your first business-initiated message should ask the user if the user wants to receive marketing messages from your business and should comply with Meta's requirements for [getting opt-in](https://developers.facebook.com/docs/whatsapp/overview/getting-opt-in/). Keep in mind that WhatsApp will monitor your business reputation on the channel, so the recommended best practice is to be explicit with your users and only send messages they have indicated they want to receive. +#### Can I proactively message end-users on WhatsApp to collect opt-in consent? +If you choose to proactively message end-users, your first business-initiated message should ask the user if the user wants to receive marketing messages from your business and should comply with Meta's requirements for [getting opt-in](https://developers.facebook.com/docs/whatsapp/overview/getting-opt-in/). Keep in mind that WhatsApp will monitor your business reputation on the channel, so the recommended best practice is to be explicit with end-users and only send messages they have indicated they want to receive. -#### Do I need to collect my user's phone number when I collect opt-in? -You need to have your users' phone number on the Braze profile to message them. +#### Do I need to collect the end user's phone number when I collect opt-in? +You need to have the end-users phone number on the Braze profile to message them. - If you already have their number, you do not need to collect it during opt-in. -- If you do not have their number, your opt-in method should include phone number capture. +- If you do not have the end-users number, your opt-in method should include phone number capture. -#### How do I update the subscription status of my users who opt-in? +#### How do I update the subscription status of end-users who opt-in? Subscription management of the WhatsApp Channel functions similarly to how it functions in other Braze channels. Refer to [Managing user subscriptions]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/user_subscription/) for more information. #### If I already have a list of users who have opted-in to receive marketing messages on WhatsApp, how do I update their subscription status in Braze? @@ -142,13 +142,13 @@ There are various reasons a message would fail to be delivered, including networ #### If a message is not delivered, will I be billed? No. If a message is not delivered, you will not be billed. -#### What happens if a user blocks my business? -If a user blocks your business, subsequent messages you attempt to send will not be delivered, and you will not be billed. +#### What happens if an end-user blocks my business? +If an end-user blocks your business, subsequent messages you attempt to send will not be delivered, and you will not be billed. -#### What happens if a user reports a message? -If a user reports a message, you can still send subsequent messages to this user. However, reporting may affect your quality rating on the channel. +#### What happens if an end-user reports a message? +If an end-user reports a message, you can still send subsequent messages to this user. However, reporting may affect your quality rating on the channel. -#### If a user blocks or reports my business, will their subscription status be updated in Braze? +#### If an end-user blocks or reports my business, will their subscription status be updated in Braze? No. Their Braze subscription status will not be updated. ### Miscellaneous @@ -176,21 +176,21 @@ You can add images, calls to action (URL or phone number), and quick reply butto Yes. You can [import user phone numbers]({{site.baseurl}}/user_guide/message_building_by_channel/whatsapp/user_phone_numbers/). #### What is business verification? -Business verification is a WhatsApp concept used to ensure that the brand is a legitimate business. It can be completed in the WhatsApp Manager. Business verification is also required to scale messaging. Without business verification, customers can only send up to 250 unique users in a rolling 24-hour period. +Business verification is a WhatsApp concept used to ensure that the brand is a legitimate business. It can be completed in the WhatsApp Manager. Business verification is also required to scale messaging. Without business verification, customers can only send up to 250 unique end-users in a rolling 24-hour period. #### What is an official business account? OBA gives you the green check mark next to your display name and is optional. You can apply for an official business account after completing business verification. Note that business verification and an official business account are different WhatsApp concepts. #### What metrics are available in the Braze dashboard? -You can see unique recipients, sends, deliveries, reads, and failures in the Braze dashboard. Note that your users' read receipts must be "On" for Braze to track reads. You can also set up conversion events to monitor campaign performance, similar to other channels. +You can see unique recipients, sends, deliveries, reads, and failures in the Braze dashboard. Note that the end-users read receipts must be "On" for Braze to track reads. You can also set up conversion events to monitor campaign performance, similar to other channels. #### What is a WhatsApp conversation? -WhatsApp is a channel focused on 2-way messaging and thus anchors on conversations (instead of the number of individual messages). A conversation is a 24-hour thread between a business and an user. +WhatsApp is a channel focused on 2-way messaging and thus anchors on conversations (instead of the number of individual messages). A conversation is a 24-hour thread between a business and an end-user. - **Business-initiated conversation**: A conversation where the business starts by sending an approved template message to the end user. As soon as the business sends a message, it begins the 24-hour window. -- **User-initiated conversation**: A conversation where the user sends a message to the business. When the business sends a message in response, this begins the 24-hour window. +- **User-initiated conversation**: A conversation where the end-user sends a message to the business. When the business sends a message in response, this begins the 24-hour window. #### What factors affect phone number quality rating, and what happens when my quality rating drops too low? -Factors that affect phone number quality rating include a user blocking a business (and the reasons they provide when they block a business) and a user reporting a business. +Factors that affect phone number quality rating include an end-user blocking a business (and the reasons they provide when they block a business) and an end-user reporting a business. When a quality rating is low, the phone number status changes from **Connected** to **Flagged**. If the quality doesn't improve over seven days, the status returns to **Connected**. However, the messaging limit will decrease to the next level. For example, a phone number that used to have a 100,000 messaging limit now has a 10,000 messaging limit. diff --git a/_docs/_user_guide/sage_ai/recommendations/about_item_recommendations.md b/_docs/_user_guide/sage_ai/recommendations/about_item_recommendations.md index 5376b090ee2..a825cefe276 100644 --- a/_docs/_user_guide/sage_ai/recommendations/about_item_recommendations.md +++ b/_docs/_user_guide/sage_ai/recommendations/about_item_recommendations.md @@ -25,11 +25,11 @@ When setting out to recommend items to your customers, there are a few approache ### AI Personalized recommendations {#ai} -Part of the [AI item recommendation][1] feature, AI personalized recommendations takes advantage of deep learning to predict what your users are most likely to be interested in next based on what they’ve shown interest for in the past. This method provides a dynamic and tailored recommendation system that adapts to user behavior. +Part of the [AI Item Recommendations][1] feature, AI Personalized recommendations takes advantage of deep learning to predict what your users are most likely to be interested in next based on what they’ve shown interest for in the past. This method provides a dynamic and tailored recommendation system that adapts to user behavior. AI Personalized recommendations use the last 6 months of item interaction data, like purchases or custom events, to build the recommendation model. For users without enough data for a personalized list, the most popular items serve as a fallback so your users are still getting relevant suggestions. -With AI item recommendations, you can also further filter the items available with +With AI Item Recommendations, you can also further filter the items available with [selections]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/). However, selections with Liquid cannot be used in AI recommendations, so keep that in mind when building your catalog selections. For examples, see the [Use cases](#use-cases) section in this article. @@ -40,7 +40,7 @@ AI Personalized recommendations work best with hundreds or thousands of items an ### Most popular item recommendations {#most-popular} -In addition to the "AI Personalized" model, the [AI item recommendations][1] feature also includes a recommendation model for "Most popular", which features items that users engage with most. +In addition to the "AI Personalized" model, the [AI Item Recommendations][1] feature also includes a recommendation model for "Most popular", which features items that users engage with most. Based on the interaction data being tracked, use cases for this model could include recommending: @@ -51,7 +51,7 @@ Based on the interaction data being tracked, use cases for this model could incl ### Most recent item recommendations {#most-recent} -In addition to the "AI Personalized" model, the [AI item recommendations][1] feature also includes a recommendation model for "Most recent", which features items that users engage with most. Use this model to reduce churn by encouraging lapsing users to re-engage with relevant content. +In addition to the "AI Personalized" model, the [AI Item Recommendations][1] feature also includes a recommendation model for "Most recent", which features items that users engage with most. Use this model to reduce churn by encouraging lapsing users to re-engage with relevant content. Based on the interaction data being tracked, use cases for this model could include recommending: @@ -95,7 +95,7 @@ Predict and recommend the items a user is most likely to purchase next, based on {% details Requirements %} -- AI item recommendations +- AI Item Recommendations - Catalog of relevant items - A method for tracking purchases, either a purchase object or custom event @@ -103,7 +103,7 @@ Predict and recommend the items a user is most likely to purchase next, based on {% details How to set up %} -1. Create an [AI item recommendation]({{site.baseurl}}/ai_item_recommendations). +1. Create an [AI Item Recommendation]({{site.baseurl}}/ai_item_recommendations). 2. Set the **Type** to **AI Personalized**. 3. Select your catalog. 4. (Optional) Add a selection to filter your recommendation to only relevant items. @@ -119,7 +119,7 @@ Remind users of their interest in items that they recently added to their cart, {% details Requirements %} -- AI item recommendations +- AI Item Recommendations - Catalog of relevant items - Custom event for added to cart @@ -127,7 +127,7 @@ Remind users of their interest in items that they recently added to their cart, {% details How to set up %} -1. Create an [AI item recommendation]({{site.baseurl}}/ai_item_recommendations). +1. Create an [AI Item Recommendation]({{site.baseurl}}/ai_item_recommendations). 2. Set the **Type** to **Most recent**. 3. Select your catalog. 4. (Optional) Add a selection to filter your recommendation to only relevant items. @@ -143,7 +143,7 @@ Encourage users to explore items that they’ve recently liked or items that are {% details Requirements %} -- AI item recommendations +- AI Item Recommendations - Catalog of relevant items - Custom event for likes @@ -151,7 +151,7 @@ Encourage users to explore items that they’ve recently liked or items that are {% details How to set up %} -1. Create an [AI item recommendation]({{site.baseurl}}/ai_item_recommendations). +1. Create an [AI Item Recommendation]({{site.baseurl}}/ai_item_recommendations). 2. Set the **Type** to **Most recent**. 3. Select your catalog. 4. (Optional) Add a selection to filter your recommendation to only relevant items. @@ -167,7 +167,7 @@ Encourage users to explore popular items in your catalog based on purchases. To {% details Requirements %} -- AI item recommendations +- AI Item Recommendations - Catalog of relevant items - A purchase object or any custom event @@ -175,7 +175,7 @@ Encourage users to explore popular items in your catalog based on purchases. To {% details How to set up %} -1. Create an [AI item recommendation]({{site.baseurl}}/ai_item_recommendations). +1. Create an [AI Item Recommendation]({{site.baseurl}}/ai_item_recommendations). 2. Set the **Type** to **Most popular**. 3. Select your catalog. 4. (Optional) Add a selection to filter your recommendation to only relevant items. For example, the food delivery service might have a selection to filter for restaurant location or type of dish. @@ -191,7 +191,7 @@ Highlight items that have gained attention across your user base through views t {% details Requirements %} -- AI item recommendations +- AI Item Recommendations - Catalog of relevant items - Custom event for views @@ -199,7 +199,7 @@ Highlight items that have gained attention across your user base through views t {% details How to set up %} -1. Create an [AI item recommendation]({{site.baseurl}}/ai_item_recommendations). +1. Create an [AI Item Recommendation]({{site.baseurl}}/ai_item_recommendations). 2. Set the **Type** to **Most popular**. 3. Select your catalog. 4. (Optional) Add a selection to filter your recommendation to only relevant items. @@ -213,7 +213,7 @@ Highlight items that have gained attention across your user base through views t This scenario doesn't rely directly on user actions but rather on catalog data. You can filter for new items based on their addition date to the catalog and promote these through targeted campaigns or Canvases without needing to train a recommendation model. -For example, a tech ecommerce platform could alert tech enthusiasts about the latest gadgets or upcoming pre-orders, using filters to target items that have been recently added to the catalog. +For example, a tech e-commerce platform could alert tech enthusiasts about the latest gadgets or upcoming pre-orders, using filters to target items that have been recently added to the catalog. {% details Requirements %} @@ -240,7 +240,7 @@ For example, a fashion retailer could promote clothes and accessories that are t {% details Requirements %} -- AI item recommendations +- AI Item Recommendations - Catalog of relevant items - Custom event for added to cart @@ -248,7 +248,7 @@ For example, a fashion retailer could promote clothes and accessories that are t {% details How to set up %} -1. Create an [AI item recommendation]({{site.baseurl}}/ai_item_recommendations). +1. Create an [AI Item Recommendation]({{site.baseurl}}/ai_item_recommendations). 2. Set the **Type** to **Most popular**. 3. Select your catalog. 4. (Optional) Add a selection to filter your recommendation to only relevant items. @@ -286,7 +286,7 @@ Encourage users to revisit items that they’ve recently clicked on, based on a {% details Requirements %} -- AI item recommendations +- AI Item Recommendations - Catalog of relevant items - Custom event for clicks @@ -294,7 +294,7 @@ Encourage users to revisit items that they’ve recently clicked on, based on a {% details How to set up %} -1. Create an [AI item recommendation]({{site.baseurl}}/ai_item_recommendations). +1. Create an [AI Item Recommendation]({{site.baseurl}}/ai_item_recommendations). 2. Set the **Type** to **Most recent**. 3. Select your catalog. 4. (Optional) Add a selection to filter your recommendation to only relevant items. @@ -314,7 +314,7 @@ Promote items that users have recently interacted with, including views, clicks, {% details Requirements %} -- AI item recommendations +- AI Item Recommendations - Catalog of relevant items - A purchase object or any custom event for an engagement interaction @@ -322,7 +322,7 @@ Promote items that users have recently interacted with, including views, clicks, {% details How to set up %} -1. Create an [AI item recommendation]({{site.baseurl}}/ai_item_recommendations). +1. Create an [AI Item Recommendation]({{site.baseurl}}/ai_item_recommendations). 2. Set the **Type** to **Most recent**. 3. Select your catalog. 4. (Optional) Add a selection to filter your recommendation to only relevant items. diff --git a/_docs/_user_guide/sage_ai/recommendations/ai_item_recommendations.md b/_docs/_user_guide/sage_ai/recommendations/ai_item_recommendations.md index 811d51f54f1..0326351905f 100644 --- a/_docs/_user_guide/sage_ai/recommendations/ai_item_recommendations.md +++ b/_docs/_user_guide/sage_ai/recommendations/ai_item_recommendations.md @@ -8,7 +8,7 @@ description: "This reference article covers how to create an AI Item Recommendat # AI item recommendations -> Learn how to create an AI item recommendation for items in a catalog. +> Learn how to create an AI Item Recommendation for items in a catalog. You can use AI item recommendations to calculate the most popular products or create personalized AI recommendations for a specific [catalog]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/). After you create your recommendation, you can use personalization to insert those products into your messages. @@ -18,7 +18,7 @@ You can use AI item recommendations to calculate the most popular products or cr - You must have purchase or event data on Braze (custom events or the purchase object) that includes a reference to unique product IDs stored in a catalog. - AI Personalized recommendations work best with hundreds or thousands of items and typically at least 30,000 users with purchase or interaction data. This is only a rough guide and can vary. The other recommendation types can work with less data. -## Creating an AI item recommendation +## Creating an AI Item Recommendation To create an item recommendation: @@ -51,9 +51,9 @@ To avoid suggesting items that a user has already purchased or interacted with, ![][2-3] -This setting makes sure that items a user has already bought or interacted with are not surfaced in messages again, provided the recommendation has been updated recently. Items purchased or interacted with between recommendation updates may still appear. For the free version of AI item recommendations, updates happen weekly. For the pro version of AI item recommendations, updates happen every 24 hours. +This setting makes sure that items a user has already bought or interacted with are not surfaced in messages again, provided the recommendation has been updated recently. Items purchased or interacted with between recommendation updates may still appear. For the free version of Item Recommendations, updates happen weekly. For AI Item Recommendations Pro, updates happen every 24 hours. -For example, when using the pro version of AI item recommendations, if a user purchases something and then receives a marketing email within 30 minutes, the item they just purchased might not be excluded from the email in time. However, any messages sent after 24 hours won't include that item. +For example, when using AI Item Recommendations Pro, if a user purchases something and then receives a marketing email within 30 minutes, the item they just purchased might not be excluded from the email in time. However, any messages sent after 24 hours won't include that item. #### Step 2b: Select a catalog @@ -284,11 +284,11 @@ After your recommendation finishes training, you can personalize your messages w 5. For **Information to Display**, select which fields from the catalog should be included for each item. The values for these fields for each item will be drawn from the catalog associated with this recommendation. 6. Click the **Copy** icon and paste the Liquid wherever it needs to go in your message. -## AI item recommendations tiers +## AI Item Recommendations tiers -The following table describes the differences between the free and pro version of AI item recommendations: +The following table describes the differences between the free and pro version of AI Item Recommendations: -| Area | Free version | Pro version | +| Area | Free version | AI Item Recommendations Pro | | :---------------------- | ------------------------------------- | :--------------------------------------- | | Item update frequency | Weekly | Daily | | Model retraining frequency | Monthly | Monthly | diff --git a/_lang/fr/_api/api_limits.md b/_lang/fr/_api/api_limits.md index 89019ddc342..156fd7dda77 100644 --- a/_lang/fr/_api/api_limits.md +++ b/_lang/fr/_api/api_limits.md @@ -82,7 +82,7 @@ Nom d’en-tête | Description `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 `X-RateLimit-Remaining` chute en dessous d’un certain seuil, vous voudrez peut-être ralentir l’envoi pour vous assurer que tous les emails transactionnels partent. 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. +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 `X-RateLimit-Remaining` chute en dessous d’un certain seuil, vous voudrez peut-être ralentir l’envoi pour vous assurer que tous les e-mails transactionnels partent. 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 d’API, contactez votre gestionnaire du succès des clients ou ouvrez un [ticket d’assistance][support]. diff --git a/_lang/fr/_api/endpoints/export/canvas/get_canvas_details.md b/_lang/fr/_api/endpoints/export/canvas/get_canvas_details.md index 27903c16406..5f15e3db895 100644 --- a/_lang/fr/_api/endpoints/export/canvas/get_canvas_details.md +++ b/_lang/fr/_api/endpoints/export/canvas/get_canvas_details.md @@ -85,7 +85,7 @@ Authorization: Bearer YOUR-REST-API-KEY "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 (such as "email"), + "channel": (string) the channel type of the message (e.g., "email"), // channel-specific fields for this message, see Campaign Details endpoint API Response for example message responses } } diff --git a/_lang/fr/_api/endpoints/export/user_data/post_users_global_control_group.md b/_lang/fr/_api/endpoints/export/user_data/post_users_global_control_group.md index 712ec902527..b6295123000 100644 --- a/_lang/fr/_api/endpoints/export/user_data/post_users_global_control_group.md +++ b/_lang/fr/_api/endpoints/export/user_data/post_users_global_control_group.md @@ -66,7 +66,7 @@ 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, such as ['first_name', 'email', 'purchases'], + "fields_to_export" : (required, array of string) name of user data fields to export, e.g., ['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 } ``` @@ -138,7 +138,7 @@ 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, such as'bb8e2a91-c4aa-478b-b3f2-a4ee91731ad1-1464728599', + "object_prefix": (required, string) the filename prefix that will be used for the JSON file produced by this export, e.g.,'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 } ``` diff --git a/_lang/fr/_api/endpoints/export/user_data/post_users_segment.md b/_lang/fr/_api/endpoints/export/user_data/post_users_segment.md index cd248c3cced..27279e6fa9d 100644 --- a/_lang/fr/_api/endpoints/export/user_data/post_users_segment.md +++ b/_lang/fr/_api/endpoints/export/user_data/post_users_segment.md @@ -155,7 +155,7 @@ 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, such as 'bb8e2a91-c4aa-478b-b3f2-a4ee91731ad1-1464728599', + "object_prefix": (required, string) the filename prefix that will be used for the JSON file produced by this export, e.g., '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 } ``` diff --git a/_lang/fr/_api/endpoints/messaging/send_messages/post_send_messages.md b/_lang/fr/_api/endpoints/messaging/send_messages/post_send_messages.md index d6b6aa9e78d..4ff359ea884 100644 --- a/_lang/fr/_api/endpoints/messaging/send_messages/post_send_messages.md +++ b/_lang/fr/_api/endpoints/messaging/send_messages/post_send_messages.md @@ -44,7 +44,7 @@ Authorization: Bearer YOUR-REST-API-KEY "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 (such as sends, clicks, bounces, etc). see campaign identifier, + "campaign_id": (optional*, string) *required if you wish to track campaign stats (e.g., 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', diff --git a/_lang/fr/_api/objects_filters/messaging/android_object.md b/_lang/fr/_api/objects_filters/messaging/android_object.md index e6bde43f979..c3ed6ca1be8 100644 --- a/_lang/fr/_api/objects_filters/messaging/android_object.md +++ b/_lang/fr/_api/objects_filters/messaging/android_object.md @@ -35,7 +35,7 @@ Vous devez inclure un objet Notification push Android dans `messages` si vous vo "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 + "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 via Conversation Push. } ``` diff --git a/_lang/fr/_api/objects_filters/messaging/apple_object.md b/_lang/fr/_api/objects_filters/messaging/apple_object.md index a9d1286390b..c694a748a64 100644 --- a/_lang/fr/_api/objects_filters/messaging/apple_object.md +++ b/_lang/fr/_api/objects_filters/messaging/apple_object.md @@ -35,7 +35,7 @@ description: "Cet article de référence répertorie et explique les différents "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 + "buttons" : (optional, array of Apple Push Action Button Objects) push action buttons to display } ``` diff --git a/_lang/fr/_api/objects_filters/messaging/email_object.md b/_lang/fr/_api/objects_filters/messaging/email_object.md index bc7fa3f27d5..56b1e23fbdf 100644 --- a/_lang/fr/_api/objects_filters/messaging/email_object.md +++ b/_lang/fr/_api/objects_filters/messaging/email_object.md @@ -30,7 +30,7 @@ description: "Cet article de référence explique les différents composants de "headers": (optional, valid Key-Value Hash), hash of custom extensions headers. Currently, only supported for SendGrid customers, "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 App Group, "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 would like to attach to your email, excluding the extension (such as ".pdf"). You can attach any number of files up to 2 MB. This is required if you use "attachments", + "file_name": (required, string) the name of the file you would like to attach to your email, excluding the extension (e.g., ".pdf"). You can attach any number of files up to 2 MB. This is required if you use "attachments", "url": (required, string) the corresponding URL of the file you would like 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", } ``` diff --git a/_lang/fr/_api/objects_filters/messaging/web_objects.md b/_lang/fr/_api/objects_filters/messaging/web_objects.md index 1ae6a9ce2b3..22463df150a 100644 --- a/_lang/fr/_api/objects_filters/messaging/web_objects.md +++ b/_lang/fr/_api/objects_filters/messaging/web_objects.md @@ -26,7 +26,7 @@ description: "Cet article de référence répertorie et explique les différents "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 + "buttons" : (optional, array of Web Push Action Button Objects) push action buttons to display } ``` diff --git a/_lang/fr/_api/objects_filters/purchase_object.md b/_lang/fr/_api/objects_filters/purchase_object.md index 633b5a67c5d..b36f7f1b2a0 100644 --- a/_lang/fr/_api/objects_filters/purchase_object.md +++ b/_lang/fr/_api/objects_filters/purchase_object.md @@ -25,10 +25,10 @@ Un objet Achat est un objet qui passe par l’API lorsqu’un achat a été effe "braze_id" : (optional, string) Braze User Identifier, "app_id" : (optional, string) see App Identifier, // See the following product_id naming conventions for clarification. - "product_id" : (required, string), identifier for the purchase, such as Product Name or Product Category, + "product_id" : (required, string), identifier for the purchase, e.g., 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 (such as Dollars for USD, Yen for JPY), + "price" : (required, float) value in the base currency unit (e.g., 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. diff --git a/_lang/fr/_developer_guide/platform_integration_guides/ios/initial_sdk_setup/ios_sdk_integration.md b/_lang/fr/_developer_guide/platform_integration_guides/ios/initial_sdk_setup/ios_sdk_integration.md index 92d36af9a94..2d7be32a263 100644 --- a/_lang/fr/_developer_guide/platform_integration_guides/ios/initial_sdk_setup/ios_sdk_integration.md +++ b/_lang/fr/_developer_guide/platform_integration_guides/ios/initial_sdk_setup/ios_sdk_integration.md @@ -459,7 +459,7 @@ func logCustomEvent(_ eventName: String, withProperties properties: [AnyHashable {% endsubtab %} {% endsubtabs %} {% endtab %} -{% tab Step 2: Custom attributes %} +{% tab Step 2: Custom Attributes %} ##### Créer une méthode d’attributs personnalisés de journal @@ -673,7 +673,7 @@ Procédez à la compilation de votre code et exécutez votre application.
Void) { if (!ABKPushUtils.isAppboyInternalRemoteNotification(userInfo)) { - // ... Gated logic here (such as pinging server for content) ... + // ... Gated logic here (e.g., pinging server for content) ... } } ``` diff --git a/_lang/fr/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/ios_sdk_integration.md b/_lang/fr/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/ios_sdk_integration.md index e99b4a3f0ea..e3338e3f282 100644 --- a/_lang/fr/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/ios_sdk_integration.md +++ b/_lang/fr/_developer_guide/platform_integration_guides/swift/initial_sdk_setup/ios_sdk_integration.md @@ -424,7 +424,7 @@ Procédez à la compilation de votre code et exécutez votre application.

Void) { if (!ABKPushUtils.isAppboyInternalRemoteNotification(userInfo)) { - // ... Gated logic here (such as pinging server for content) ... + // ... Gated logic here (e.g., pinging server for content) ... } } ``` diff --git a/_lang/fr/_developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide.md b/_lang/fr/_developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide.md index 9cf7b75bc5f..fef8ac06cc6 100644 --- a/_lang/fr/_developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide.md +++ b/_lang/fr/_developer_guide/platform_integration_guides/swift/push_notifications/implementation_guide.md @@ -225,7 +225,7 @@ Ajoutez une capacité de `Groupes d'apps`. Si vous n’avez pas de groupe d’ap Les extraits de code suivants sont une référence utile sur la façon d’enregistrer et d’envoyer des événements personnalisés, des attributs personnalisés et des attributs utilisateur. Ce guide sera en cours de conversation par défaut d’utilisateur, mais la représentation du code sera sous la forme d’un fichier d’aide `RemoteStorage`. Il existe également des fichiers auxiliaires supplémentaires, `UserAttributes` et `Dictionnaire EventName`, utilisés lors de l’envoi et de l’enregistrement des attributs utilisateur. Tous les fichiers d’aide sont disponibles à la fin de ce guide. {% tabs local %} -{% tab Custom events %} +{% tab Custom Events %} ##### Enregistrement des événements personnalisés @@ -366,7 +366,7 @@ func logPendingCustomEventsIfNecessary() { {% endsubtab %} {% endsubtabs %} {% endtab %} -{% tab Custom attributes %} +{% tab Custom Attributes %} ##### Enregistrer des attributs personnalisés diff --git a/_lang/fr/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md b/_lang/fr/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md index a97b924a786..1ab75ac7975 100644 --- a/_lang/fr/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md +++ b/_lang/fr/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md @@ -819,7 +819,7 @@ Cet événement se produit lorsqu’un utilisateur ouvre un e-mail. Plusieurs é "email_address": (string) email address for this event, "ip_pool": (string) IP pool used for message sending, "user_agent": (string) description of the user's system and browser for the event, - "machine_open": (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 (e.g. "Apple" or "Google" to indicate which process made the fetch) may be added in the future., + "machine_open": (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 (e.g., "Apple" or "Google" to indicate which process made the fetch) may be added in the future., "esp": (string) ESP related to the event (SparkPost or SendGrid), "from_domain": (string) sending domain for the email, "is_amp": (boolean) indicates that this is an AMP event diff --git a/_lang/fr/_user_guide/data_and_analytics/user_data_collection/user_import.md b/_lang/fr/_user_guide/data_and_analytics/user_data_collection/user_import.md index 7fceff70082..2cd32232dc4 100644 --- a/_lang/fr/_user_guide/data_and_analytics/user_data_collection/user_import.md +++ b/_lang/fr/_user_guide/data_and_analytics/user_data_collection/user_import.md @@ -122,7 +122,7 @@ Définir `language` ou `country` sur un utilisateur via une importation CSV ou u | `email_subscribe` | String | Les valeurs disponibles sont `opted_in` (explicitement consenti à recevoir des e-mails), `unsubscribed` (explicitement refusé de recevoir des e-mails), et `subscribed` (ni accepté, ni refusé). | Non | | `push_subscribe` | String | Les valeurs disponibles sont `opted_in` (explicitement consenti à recevoir des messages de notification push), `unsubscribed` (explicitement refusé de recevoir des messages de notification push), et `subscribed` (ni accepté, ni refusé). | Non | | `time_zone` | String | Le fuseau horaire doit être transmis à Braze au même format que la Base de données des fuseaux horaires de l'IANA (par ex., `America/New_York` ou `Eastern Time (US & Canada)`). | Non | -| `date_of_first_session`

`date_of_last_session`| String | Peut être transmis dans l’un des formats ISO 8601 suivants : {::nomarkdown}
  • "YYYY-MM-DD"
  • "YYYY-MM-DDTHH:MM:SS+00:00"
  • "YYYY-MM-DDTHH:MM:SSZ"
  • "YYYY-MM-DDTHH:MM:SS" (e.g. 2019-11-20T18:38:57)
{:/} | Non | +| `date_of_first_session`

`date_of_last_session`| String | Peut être transmis dans l’un des formats ISO 8601 suivants : {::nomarkdown}
  • "YYYY-MM-DD"
  • "YYYY-MM-DDTHH:MM:SS+00:00"
  • "YYYY-MM-DDTHH:MM:SSZ"
  • "YYYY-MM-DDTHH:MM:SS" (e.g., 2019-11-20T18:38:57)
{:/} | Non | | `subscription_group_id` | String | L’`id` de votre groupe d’abonnement. Cet identifiant se trouve sur la page du groupe d’abonnement de votre tableau de bord. | Non | | `subscription_state` | String | Le statut d’abonnement du groupe d’abonnement spécifié par `subscription_group_id`. Les valeurs autorisées sont `unsubscribed` (pas dans le groupe d’abonnement) ou `subscribed` (dans le groupe d’abonnement). | Non, mais fortement recommandé si `subscription_group_id` est utilisé | {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4} diff --git a/_lang/ja/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/implementation_guide.md b/_lang/ja/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/implementation_guide.md index 0cd8b83a3d4..6a17c258fd7 100644 --- a/_lang/ja/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/implementation_guide.md +++ b/_lang/ja/_developer_guide/platform_integration_guides/legacy_sdks/ios/push_notifications/implementation_guide.md @@ -193,7 +193,7 @@ func didReceive(_ response: UNNotificationResponse, completionHandler completion 1. `completion(.dismiss)` - 通知を解除します 2. `completion(.doNotDismiss)` - 通知は開いたままです -3. `completion(.dismissAndForward)` - プッシュが解除され、ユーザーがアプリケーションに転送されます。 +3. `completion(.dismissAndForward)` - プッシュが解除され、ユーザーがアプリケーションに転送されます。 #### その他のユースケース