diff --git a/_docs/_developer_guide/disclosures/innovation_statement.md b/_docs/_developer_guide/disclosures/innovation_statement.md index 681b71eeda2..6dcee37ded8 100644 --- a/_docs/_developer_guide/disclosures/innovation_statement.md +++ b/_docs/_developer_guide/disclosures/innovation_statement.md @@ -15,15 +15,16 @@ Warning! Don't make any changes to this document without approval from the legal {% tabs %} {% tab English %} -_Last updated December 2018._ +_Last updated September 2022._ -Braze continually strives to enhance existing, and create new, features, functionality, products and services. To do so, Braze not only seeks feedback from its customers, but also endeavors to anticipate its customers’ needs. +Braze continually strives to enhance existing, and create new, features, functionality, products and services. To do so, Braze not only seeks feedback from its customers, but also endeavors to anticipate its customers’ needs. -As part of its innovation strategy, Braze analyzes information contained in the Braze Services and how the Braze Services are used (e.g., analysis of User clicks and movements across the dashboard), in order to provide and improve the Services, as well as to provide consultative and analytical information to its customers generally. +As part of its innovation strategy, Braze analyzes information contained in the Braze Services and how the Braze Services are used (e.g., analysis of User clicks and movements across the dashboard), in order to provide consultative and analytical information to its customers generally, and in order to build, provide or improve its services, provided that this use does not include building or modifying End User profiles to use in providing services to another customer, or correcting or augmenting data acquired by Braze from another source. -Braze also communicates with (dashboard) Users to educate and inform them of ways to optimize their use of the Services and to share Braze’s innovation efforts. Braze may send emails to (dashboard) Users or communicate with them through the dashboard. Customers can also subscribe to Braze’s GitHub repositories to receive notifications when new releases are made. +Braze also communicates with (dashboard) Users to educate and inform them of ways to optimize their use of the Services and to share Braze’s innovation efforts. Braze may send emails to (dashboard) Users or communicate with them through the dashboard. Customers can also subscribe to Braze’s GitHub repositories to receive notifications when new releases are made. Braze owns all right, title and interest in and to any material resulting from such activities. + {% endtab %} {% tab Japanese %} {% raw %} diff --git a/_docs/_developer_guide/platform_integration_guides/ios/in-app_messaging/customization/custom_triggering.md b/_docs/_developer_guide/platform_integration_guides/ios/in-app_messaging/customization/custom_triggering.md index 0e2abf8ea9a..04a37f2229c 100644 --- a/_docs/_developer_guide/platform_integration_guides/ios/in-app_messaging/customization/custom_triggering.md +++ b/_docs/_developer_guide/platform_integration_guides/ios/in-app_messaging/customization/custom_triggering.md @@ -69,7 +69,7 @@ In the following example, the specific in-app message to be triggered has been c ![An action-based delivery in-app message campaign that will be delivered to users who perform the custom event "In-app message trigger" where "campaign_name" equals "In-app message name example".][42] -Due to a push message being used to record an SDK logged custom event, Braze will need to store a push token for each user to enable this solution. For iOS users, Braze will only store a token from the point that a user has been served the OS's push prompt. Before this, the user will not be reachable using push, and the preceding solution will not be possible. +Due to a push message being used to record an SDK logged custom event, Braze will need to store a push token for each user to enable this solution. For both iOS and Android, Braze will only store a token from the point that a user has been served the OS's push prompt. Before this, the user will not be reachable using push, and the preceding solution will not be possible. [39]: {{site.baseurl}}/developer_guide/platform_integration_guides/ios/push_notifications/silent_push_notifications/ [40]: {% image_buster /assets/img_archive/iosServerSentPush.png %} diff --git a/_docs/_developer_guide/platform_wide/tv_and_ott.md b/_docs/_developer_guide/platform_wide/tv_and_ott.md index 7cae9939d21..d9db1ea35bc 100644 --- a/_docs/_developer_guide/platform_wide/tv_and_ott.md +++ b/_docs/_developer_guide/platform_wide/tv_and_ott.md @@ -96,13 +96,14 @@ The following lists features and messaging channels supported today. - + - = Supported +- = Partial support - = Not supported by Braze - N/A = Not supported by OTT platform @@ -158,13 +159,13 @@ Make sure to create a new Android app in the dashboard for your Android OTT inte ### LG webOS -Use Braze's Web SDK to integrate with [LG webOS TVs](http://webostv.developer.lge.com/discover/discover-webos-tv/). +Use Braze's Web SDK to integrate with [LG webOS TVs](https://webostv.developer.lge.com/discover). Features include: - Data and analytics collection for cross-channel engagement -- Content Cards (via [Custom UI](#custom-ui)) -- In-app messages (via [Custom UI](#custom-ui)) +- Content Cards (via [Headless UI](#custom-ui)) +- In-app messages (via [Headless UI](#custom-ui)) For more information, visit the [Web Smart TV integration guide][8]. @@ -175,8 +176,8 @@ Use Braze's Web SDK to integrate with the [Samsung Tizen TVs](https://developer. Features include: - Data and analytics collection for cross-channel engagement -- Content Cards (via [Custom UI](#custom-ui)) -- In-app messages (via [Custom UI](#custom-ui)) +- Content Cards (via [Headless UI](#custom-ui)) +- In-app messages (via [Headless UI](#custom-ui)) For more information, visit the [Web Smart TV integration guide][8]. @@ -187,7 +188,7 @@ Use Braze's Roku SDK to integrate with [Roku TVs](https://developer.roku.com/doc Features include: - Data and analytics collection for cross-channel engagement -- In-app messages (via [Custom UI](#custom-ui)) +- In-app messages (via [Headless UI](#custom-ui)) For more information, visit the [Roku integration guide][3]. @@ -199,10 +200,10 @@ For more information, visit the [iOS Swift SDK integration guide][4]. Features include: -- Data and Analytics collection for cross-channel engagement -- Content Cards (via [Custom UI](#custom-ui)) -- In-app messages (via [Custom UI](#custom-ui)) -- Silent Push Notifications +- Data and analytics collection for cross-channel engagement +- Content Cards (via [Headless UI](#custom-ui)) +- In-app messages (via [Headless UI](#custom-ui)) +- Silent push notifications and update badging **Note**: To avoid showing mobile in-app messages to your TV users, be sure to set up either [App Targeting](#app-targeting) or use key-value pairs to filter out messages. For example, only displaying tvOS messages if they contain a special `tv = true` key-value pair. @@ -212,9 +213,9 @@ To target OTT apps for messaging, we recommend creating a segment specific to yo ![A segment created using the Android OTT app.][1] -## Custom UI {#custom-ui} +## Headless UI {#custom-ui} -For platforms that support in-app messages or Content Cards via Custom UI, Braze will deliver a data model (i.e. JSON) that your app can read and use within a UI your app controls. These platforms don't include any out-of-the-box UI or Views. +For platforms that support in-app messages or Content Cards via headless UI, Braze will deliver a data model (i.e. JSON) that your app can read and use within a UI your app controls. These platforms don't include any out-of-the-box UI or Views. This data will contain the fields configured in the dashboard (title, body, button text, colors, etc.) which your app can read and display accordingly. @@ -241,4 +242,4 @@ Read more about custom handling messaging: [6]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android_tv_push/ [7]: https://developer.amazon.com/docs/fire-tv/notifications.html#headsup [8]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/smart_tvs/ -[android-tv-html]: https://github.com/Appboy/appboy-android-sdk/blob/master/CHANGELOG.md#2310 \ No newline at end of file +[android-tv-html]: https://github.com/Appboy/appboy-android-sdk/blob/master/CHANGELOG.md#2310 diff --git a/_docs/_help/release_notes.md b/_docs/_help/release_notes.md index a2b3b79dede..99cbd863035 100644 --- a/_docs/_help/release_notes.md +++ b/_docs/_help/release_notes.md @@ -50,7 +50,7 @@ guide_featured_list: ## September 20, 2022 release ### API guide -Check out the [Braze API Guide]({{site.baseurl}}/docs/api/home) to search for endpoints based on endpoint types, helping you narrow down the glossary +Check out the [Braze API Guide]({{site.baseurl}}/docs/api/home) to search for endpoints based on endpoint types, helping you narrow down the glossary. ### Personalized variants Use [personalized variants]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign/#optimizations) to send each user in your target segment the variant they're most likely to engage with. diff --git a/_docs/_help/release_notes/2022/9_20_22.md b/_docs/_help/release_notes/2022/9_20_22.md index 81b6a5faa41..d31febf8ddc 100644 --- a/_docs/_help/release_notes/2022/9_20_22.md +++ b/_docs/_help/release_notes/2022/9_20_22.md @@ -9,7 +9,7 @@ description: "This article contains release notes for 9/20/2022." # September 20, 2022 release ## API guide -Check out the [Braze API Guide]({{site.baseurl}}/docs/api/home) to search for endpoints based on endpoint types, helping you narrow down the glossary +Check out the [Braze API Guide]({{site.baseurl}}/docs/api/home) to search for endpoints based on endpoint types, helping you narrow down the glossary. ## Personalized variants Use [personalized variants]({{site.baseurl}}/user_guide/engagement_tools/testing/multivariant_testing/create_multivariate_campaign/#optimizations) to send each user in your target segment the variant they're most likely to engage with. diff --git a/_docs/_hidden/private_betas/shopify_subscription_states.md b/_docs/_hidden/private_betas/shopify_subscription_states.md index 3decf90ce34..124ad38aefe 100644 --- a/_docs/_hidden/private_betas/shopify_subscription_states.md +++ b/_docs/_hidden/private_betas/shopify_subscription_states.md @@ -51,7 +51,7 @@ Next, you are prompted by Braze's setup wizard. Within this flow, you must enter #### Shopify setup within Braze
![Workflow of setting up Shopify within Braze by entering the store name and navigating to Shopify to install the Braze app.][3]{: style="max-width:80%;"} -#### Collect email or SMS subscribers +### Step 3: Collect email or SMS subscribers At this step, select whether you want to collect email and SMS opt-ins from your Shopify store to sync to Braze. diff --git a/_docs/_home/templates/get_endpoint.md b/_docs/_home/templates/get_endpoint.md index 66a1eb49e84..a652c4be578 100644 --- a/_docs/_home/templates/get_endpoint.md +++ b/_docs/_home/templates/get_endpoint.md @@ -4,6 +4,7 @@ article_title: "GET: [Endpoint Name]" search_tag: Endpoint page_order: 1 +excerpt_separator: "" layout: api_page page_type: reference diff --git a/_docs/_home/templates/post_endpoint.md b/_docs/_home/templates/post_endpoint.md index a6c23bf4f5e..150af55c287 100644 --- a/_docs/_home/templates/post_endpoint.md +++ b/_docs/_home/templates/post_endpoint.md @@ -5,6 +5,7 @@ search_tag: Endpoint page_order: 4 layout: api_page page_type: reference +excerpt_separator: "" description: "This article outlines details about and using this POST [endpoint name] Braze endpoint." diff --git a/_docs/_partners/message_orchestration/channel_extensions/loyalty/extole.md b/_docs/_partners/message_orchestration/channel_extensions/loyalty/extole.md index 78479d75f9e..dbe44489c62 100644 --- a/_docs/_partners/message_orchestration/channel_extensions/loyalty/extole.md +++ b/_docs/_partners/message_orchestration/channel_extensions/loyalty/extole.md @@ -75,9 +75,12 @@ Any event that Extole tracks can be sent to Braze. Work with your Extole impleme To start sending data from your Extole programs into Braze, create a new webhook integration in Extole’s outbound webhook center. -1. In the Extole dashboard, navigate to **Tech Center > Outbound Webhooks** and select **+ New Integration**. -2. Enter a name for the key and select **Webhook** as the key type. -3. Add your Braze REST API key in the **Partner Key ID** field, select `HTTP_BASIC` as the **Algorithm**, and click **Create Key**.

![][4]{: style="max-width:80%;"} + +1. Navigate to **Tech Center > Outbound Webhooks** in your My Extole account and click on the **+ New Integration** button. +2. Enter a key name (i.e., how you'd like to refer to the key in Extole) and select **Webhook** as the key type. +3. In the partner key ID field, add a value that you will recognize for this credential (e.g., your account ID, email address, or user ID). +4. Select `PASSWORD` from the algorithm drop-down. +5. Add your Braze REST API key to the key field and click **Create Key**.

![][4]{: style="max-width:80%;"} Next, work with your Extole success or implementation manager to create a new webhook. They will configure the webhook for you using your newly generated key and Braze instance URL.

![][5]{: style="max-width:80%;"} diff --git a/_docs/_user_guide/administrative/company_settings/security_settings.md b/_docs/_user_guide/administrative/company_settings/security_settings.md index eba6c989f2b..c26abf882bd 100644 --- a/_docs/_user_guide/administrative/company_settings/security_settings.md +++ b/_docs/_user_guide/administrative/company_settings/security_settings.md @@ -79,6 +79,8 @@ The Security Event report is a CSV report of security events such as account inv This section covers a permission only accessible to a few select Braze users. For the existing team permission capabilities, see [Setting user permissions]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#available-limited-and-team-role-permissions). +By default, all admins will have their **View PII** permission enabled. This means they can see the following standard and custom attributes throughout the dashboard. When this permission is disabled for users in [user permissions]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#available-limited-and-team-role-permissions), those users will not be able to see this information. + ### Define PII Braze allows you to define which fields are designated as personally identifiable information (PII) in your dashboard. To do this, navigate to **Company Settings > Security Settings**. @@ -90,8 +92,6 @@ The following fields can be hidden from Braze users who don't have **View PII** | - Email address
- Phone number
- First name
- Last name
- Gender
- Birthday
- Device IDs
- Most recent location | - All custom attributes | {: .reset-td-br-1 .reset-td-br-2} -By default, all admins will have their **View PII** permission enabled. This means they can see all standard and custom attributes throughout the dashboard. When this permission is disabled for users in [user permissions]({{site.baseurl}}/user_guide/administrative/manage_your_braze_users/user_permissions/#available-limited-and-team-role-permissions), those users will not be able to see this information. - ### Limited areas The following assumes all fields are set as PII and that the users mentioned are those that use the Braze platform. diff --git a/_docs/_user_guide/administrative/manage_your_braze_users/user_permissions.md b/_docs/_user_guide/administrative/manage_your_braze_users/user_permissions.md index 96117737128..e9cdb45583c 100644 --- a/_docs/_user_guide/administrative/manage_your_braze_users/user_permissions.md +++ b/_docs/_user_guide/administrative/manage_your_braze_users/user_permissions.md @@ -44,8 +44,8 @@ You can manage user permissions by group or on an individual basis using the Use |---|---| |Admin|Has access to all available features, default setting for all new users. Can update company settings (company name and time zone), which Limited Users are unable to do.| |Access Campaigns, Canvases, Cards, Segments, Media Library| User can view campaign and Canvas performance metrics, create and duplicate drafts of campaigns and Canvases, view drafts of News Feed, segments, templates and media, create templates, upload media, and view engagement reports. However, users with this permission cannot view existing live content. | -|Send Campaigns, Canvases| Allows user to edit, archive, and stop campaigns and canvases, create campaigns, launch canvases. To launch existing content blocks, both **Send campaigns, Canvases** and **Publish Cards** permissions are required. | -|Publish Cards| Allows user to create and edit News Feed cards. You can still view cards without this permission. To launch existing content blocks, both **Publish Cards** and **Send campaigns, Canvases** permissions are required. | +|Send Campaigns, Canvases| Allows user to edit, archive, and stop campaigns and Canvases, create campaigns, and launch Canvases. To launch existing Content Blocks, **Send campaigns, Canvases** permission is required. | +|Publish Cards| Allows user to create and edit News Feed cards. You can still view cards without this permission. To launch existing Content Blocks, both **Publish Cards** and **Send campaigns, Canvases** permissions are required if your account is enabled for News Feed. | |Edit Segments| Allows user to create and edit segments. You can still create campaigns with existing segments and filters without this permission. You need this permission to generate a segment from users in a CSV or retarget the group of users in the CSV.| |Export User Data| Allows user to export your user data from Segments, campaigns and Canvases. | |View PII | Allows user to view personally identifiable information within the dashboard. Note that both email addresses and phone number will be visible. | diff --git a/_docs/_user_guide/data_and_analytics/your_analytics_dashboards/email_performance_dashboard.md b/_docs/_user_guide/data_and_analytics/your_analytics_dashboards/email_performance_dashboard.md index ea1e64c9673..d2aec0fdc03 100644 --- a/_docs/_user_guide/data_and_analytics/your_analytics_dashboards/email_performance_dashboard.md +++ b/_docs/_user_guide/data_and_analytics/your_analytics_dashboards/email_performance_dashboard.md @@ -13,12 +13,12 @@ tool: Channel performance dashboards allow you to view aggregate performance metrics for an entire channel, from both campaigns and Canvases. These dashboards are currently available for email and push. +![Email performance dashboard displaying email channel engagement from the last thirty days.][1] + ## Email performance dashboard To use your email performance dashboard, go to **Overview** > **Email Performance**, and select the date range for the period you want to view data. Your date range can be up to one year in the past. -![Email performance dashboard displaying email channel engagement from the last thirty days.][1] - ### Metrics calculations ![][2]{: style="max-width:40%;float:right;margin-left:15px;border:none;"} @@ -41,26 +41,25 @@ Each tile shows the rate metric first, followed by the count metric (with the ex ## SMS performance dashboard -To use your email performance dashboard, go to **Overview** > **SMS Performance**, and select the date range for the period you want to view data. Your date range can be up to one year in the past. +To use your SMS performance dashboard, go to **Overview** > **SMS Performance**, and select the date range for the period you want to view data. Your date range can be up to one year in the past. ### Metrics calculations ![][2]{: style="max-width:40%;float:right;margin-left:15px;border:none;"} -The calculations for different metrics in the email performance dashboard is the same as those on an individual message level (i.e., Campaign Analytics). On this dashboard, the metrics are aggregated across all campaigns and Canvases for the date range you’ve selected. To learn more about these definitions, refer to [Email metrics]({{site.baseurl}}/user_guide/message_building_by_channel/email/reporting_and_analytics/email_reporting#email-metrics). +The calculations for different metrics in the SMS performance dashboard is the same as those on an individual message level (i.e., Campaign Analytics). On this dashboard, the metrics are aggregated across all campaigns and Canvases for the date range you’ve selected. To learn more about these definitions, refer to [SMS metrics]({{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_campaign_analytics/). -Each tile shows the rate metric first, followed by the count metric (with the exception of _Sends_, which displays the count metric followed by the average per day). For example, the unique clicks tile contains the _Unique click rate_ from your selected time period and the count of the total number of unique clicks from that time period. Each tile also shows the [comparison to the last period](#comparison-to-last-period). +Each tile shows the rate metric first, followed by the count metric (with the exception of _Sends_, which displays the count metric followed by the average per day). Each tile also shows the [comparison to the last period](#comparison-to-last-period). | Metric | Type | Calculation | | --- | --- | ---- | | Sends | Count | Total number of sends across each day in the date range | -| Delivery rate | Rate | (Total number of deliveries across each day in the date range) / (Total number of sends across each day in the date range) | -| Bounce rate | Rate | (Total number of bounces across each day in the date range) / (Total number of sends across each day in the date range) | -| Unsubscribe rate | Rate | (Total number of unique unsubscribes across each day in the date range) / (Total number of deliveries for date range)

This uses unique unsubscribes, which is also used in Campaign Analytics, Overview, and Report Builder. | -| Unique open rate | Rate | (Total number of unique opens across each day in the date range) / (Total number of deliveries for date range) | -| Other opens rate | Rate | (Total number of total other opens across each day in the date range) / (Total number of deliveries for date range)

Other opens includes emails that haven’t been identified as machine opens, such as when a user opens an email. This metric is non-unique and is a sub-metric of total opens. | -| Unique click rate | Rate | (Total number of unique clicks across each day in the date range) / (Total number of deliveries for date range) | -| Unique click to open rate | Rate | (Total number of unique clicks across each day in the date range) / (Total number of unique opens across each day in the date range) | +| Confirmed deliveries rate | Rate | (Total number of deliveries across each day in the date range) / (Total number of sends across each day in the date range) | +| Delivery failures rate | Rate | (Total number of failures across each day in the date range) / (Total number of sends across each day in the date range) | +| Rejections rate | Rate | (Total number of rejections across each day in the date range) / (Total number of sends across each day in the date range) | +| Click rate | Rate | (Total number of clicks across each day in the date range) / (Total number of deliveries across each day in the date range) | +| Total opt-ins | Rate | Total number of opt-ins across each day in the date range | +| Total opt-outs | Rate | Total number of opt-outs across each day in the date range | {: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3} ## Dashboard filters @@ -69,18 +68,19 @@ You can filter the data on your dashboard using the following filter options: - **Tag:** Choose one tag; once applied, your dashboard will show metrics for only your selected tag. - **Canvas:** Choose up to 10 Canvases; once applied, your dashboard will show metrics for only your selected Canvases. If you select a tag filter first, then your options for Canvas filters will only include Canvases that have your selected tag. +- **Campaign:** Choose up to 10 campaigns; once applied, your dashboard will show metrics for only your selected campaigns. If you select a tag filter first, then your options for campaign filters will only include campaigns that have your selected tag. -![Filter options on the Email Performance Dashboard where you can select a tag and list of Canvases to filter by.][3] +![Filter options on the Channel Performance Dashboard where you can select a tag and list of Canvases to filter by.][3] ## Comparison to last period: Change in totals or rates -The email dashboard automatically compares the time period you have selected in the date range versus the prior time period totaling the same number of days. For example, if you choose "Last 7 Days" as your date range in the dashboard, the comparison to the last period will compare the metrics from the last seven days against the seven days prior. If you select a custom date range—let's say May 10 to May 15, which is six days' worth of data—the dashboard will compare the metrics from across those days to the metrics from May 4 to May 9. +The channel performance dashboard automatically compares the time period you have selected in the date range versus the prior time period totaling the same number of days. For example, if you choose "Last 7 Days" as your date range in the dashboard, the comparison to the last period will compare the metrics from the last seven days against the seven days prior. If you select a custom date range—let's say May 10 to May 15, which is six days' worth of data—the dashboard will compare the metrics from across those days to the metrics from May 4 to May 9. The comparison is the percentage change between the last and current periods, calculated by taking the difference between the two periods and dividing it by the metric from the last period. You can switch between **Show Change in Totals**—which compares the total counts (i.e., number of emails delivered) between the two periods—and **Show Change in Rates**—which compares the rates (i.e., delivery rate). -![Radio buttons to switch between showing change in totals or change in rates for the Email Performance Dashboard.][4] +![Radio buttons to switch between showing change in totals or change in rates for the Channel Performance Dashboard.][4] ## Frequently asked questions diff --git a/_docs/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md b/_docs/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md index 8c8ae810e75..02e479998ca 100644 --- a/_docs/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md +++ b/_docs/_user_guide/engagement_tools/canvas/canvas_components/delay_step.md @@ -29,9 +29,7 @@ You can choose the type of delay before the next message in your Canvas. You can {% tabs %} {% tab After a duration %} - The **After a duration** option allows you to delay users for a set number of seconds, minutes, hours, days (24-hour period), calendar days, or weeks, and at a specific time. For example, you can delay users for four hours or for one day. - - There are two day options available: days and calendar days. Days are calculated as 24 hours after the user entered the step, whereas calendar days are calculated as midnight the following day. With calendar days, users could enter a Delay step set to 1 calendar day at 11 pm in their local time, then move onto the following step one hour later (on midnight the next calendar day). + The **After a duration** option allows you to delay users for a set number of seconds, minutes, hours, days or weeks, and at a specific time. For example, you can delay users for four hours or for one day. {% endtab %} {% tab Until a specific date %} diff --git a/_docs/_user_guide/engagement_tools/canvas/canvas_components/message_step.md b/_docs/_user_guide/engagement_tools/canvas/canvas_components/message_step.md index e0ef3503f47..271c47b0fc9 100644 --- a/_docs/_user_guide/engagement_tools/canvas/canvas_components/message_step.md +++ b/_docs/_user_guide/engagement_tools/canvas/canvas_components/message_step.md @@ -27,7 +27,11 @@ With a Message component, all users who enter the step advance to the next step - A message is not sent because it is frequency capped - A message is not sent because it is aborted -![Set up Messages settings for a Canvas Message component that includes the option to select your message channel and customize delivery settings.][2]{: style="max-width:75%;"} +![Set up Messages settings for a Canvas Message component that includes the option to select your message channel and customize delivery settings.][2]{: style="max-width:75%;"} + +{% raw %} +If an action-based Canvas is triggered by an inbound SMS message, you can reference SMS properties in the first Message step of the Canvas. For example, in the Message step, you could use `{{sms.${inbound_message_body}}}` or `{{sms.${inbound_media_urls}}}`. +{% endraw %} ### Edit delivery settings diff --git a/_docs/_user_guide/engagement_tools/segments/segmentation_filters.md b/_docs/_user_guide/engagement_tools/segments/segmentation_filters.md index 78120037cb5..6c73437d2e7 100644 --- a/_docs/_user_guide/engagement_tools/segments/segmentation_filters.md +++ b/_docs/_user_guide/engagement_tools/segments/segmentation_filters.md @@ -317,6 +317,54 @@ glossaries: description: Segments your users by their mobile phone’s operating system. tags: - User Attributes + - name: Clicked Content Card + description: Segments your users by whether or not they have clicked a specific Content Card. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Clicked Email + description: Segments your users by whether or not they have clicked a specific email. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Clicked In-App Message + description: Segments your users by whether or not they have clicked a specific in-app message. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Clicked In-App Message Button + description: Segments your users by whether or not they have clicked a specific in-app message button. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Directly Opened Push Notification + description: Segments your users by whether or not they have directly opened a specific push notification. The proportion of opens that are affected by Apple’s Mail Privacy Protection (MPP) for iOS 15. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Dismissed Content Card + description: Segments your users by whether or not they have dismissed a specific Content Card. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Opened Email + description: Segments your users by whether or not they have opened a specific email This includes both user and machine opens. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Opened Email (Other Opens) + description: Segments your users by whether or not they have opened a specific email. This includes email opens that haven’t been identified as “Machine opens”. For example, when a user opens an email on another platform (i.e. Gmail app on a phone, Gmail on desktop browser), this will be logged as an “Other opens”. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Opened Email (Machine Opens) + description: Segments your users by whether or not they have opened a specific email. This includes email opens that are affected by Apple’s Mail Privacy Protection (MPP) for iOS 15. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Replied to SMS + description: Segments your users by whether or not they have replied to a specific SMS message. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Viewed Content Card + description: Segments your users by whether or not they have viewed a specific Content Card. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting + - name: Viewed In-App Message + description: Segments your users by whether or not they have viewed a specific in-app message. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step". + tags: + - Retargeting - name: Email Available description: Segments your users by whether or not they have a valid email address, and if they are subscribed/opted-in to email. The email available filter checks for three criteria: if the user is unsubscribed from emails, if Braze has received a hard bounce, and if the email was marked as spam. If any of these criteria are met, or if an email doesn't doesn't exist for a user, the user will not be included. tags: diff --git a/_docs/_user_guide/message_building_by_channel/sms/campaign/retargeting.md b/_docs/_user_guide/message_building_by_channel/sms/campaign/retargeting.md index c5110e54d32..c4820e7e773 100644 --- a/_docs/_user_guide/message_building_by_channel/sms/campaign/retargeting.md +++ b/_docs/_user_guide/message_building_by_channel/sms/campaign/retargeting.md @@ -65,6 +65,10 @@ Filter for users who have replied to a specific SMS campaign or Canvas component Messages can be triggered as users send messages inbound based on keyword categories (user sent any one of the keywords) or other keywords (user sent a keyword that does not fall into one of the existing categories). These triggers are set in the Delivery step of the campaign builder. +{% alert tip %} +If an action-based Canvas is triggered by an inbound SMS message, you can reference SMS properties in the first [Message step]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/) of the Canvas. +{% endalert %} + **Trigger by inbound keyword category**
![Action-based SMS campaign with the segmentation filter Sent keyword "Opt-in" to subscription group "Marketing SMS".][7]{: style="margin-top:10px;"} 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 375236462ab..b66044fc505 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 @@ -69,6 +69,10 @@ You are able to manage your own responses that get sent to users after they text {% endtab %} {% endtabs %} +{% alert tip %} +If an action-based Canvas is triggered by an inbound SMS message, you can reference SMS properties in the first [Message step]({{site.baseurl}}/user_guide/engagement_tools/canvas/canvas_components/message_step/) of the Canvas. +{% endalert %} + ## Multi-language support When sending to certain countries, a sender may be required to support inbound keywords and outbound replies with a local language. To support this, Braze allows you to create a language-specific keyword setting. diff --git a/_docs/_user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases.md b/_docs/_user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases.md index ac62d02e68f..6ce34fdd42d 100644 --- a/_docs/_user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases.md +++ b/_docs/_user_guide/personalization_and_dynamic_content/liquid/liquid_use_cases.md @@ -242,7 +242,7 @@ This use case adds a specific number of days to the current date to reference an {% raw %} ```liquid -{{ “now” | date:‘%s’ | plus:259200 | date:“%F” }} +{{ "now" | date:'%s' | plus:259200 | date:"%F" }} ``` {% endraw %} diff --git a/assets/img/extole/extole-outbound-webhooks.png b/assets/img/extole/extole-outbound-webhooks.png index 881e48f24a5..a65ca3fb6d4 100644 Binary files a/assets/img/extole/extole-outbound-webhooks.png and b/assets/img/extole/extole-outbound-webhooks.png differ diff --git a/assets/img_archive/canvas_user_update_composer.png b/assets/img_archive/canvas_user_update_composer.png index 88830b57066..cd7c8ac87ce 100644 Binary files a/assets/img_archive/canvas_user_update_composer.png and b/assets/img_archive/canvas_user_update_composer.png differ