From b8454f4855f6583501a623e356efd06cbae5f098 Mon Sep 17 00:00:00 2001 From: Bre Fitzgerald Date: Fri, 9 Sep 2022 11:32:32 -0700 Subject: [PATCH 1/3] BD-1584 and BD-1586 --- .../customer_behavior_events.md | 27 ------------------- .../message_engagement_events.md | 26 ++++++++++++++++++ 2 files changed, 26 insertions(+), 27 deletions(-) diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md b/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md index c30e755bf65..cc979f84381 100644 --- a/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md +++ b/_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md @@ -286,33 +286,6 @@ We do track other News Feed events; these are located in [Message Engagement Eve ``` {% endapi %} -{% api %} -## Uninstall events - -{% apitags %} -Uninstall -{% endapitags %} - -This event occurs when a user uninstalls an app. Use this data to track when users uninstall an app. - -{% alert important %} -Note that this is not fired when the user actually uninstalls the app - that's impossible to track exactly. Braze sends a daily silent push to determine if the app still exists on your user's device, and if we get an error on that silent push, it is assumed the app has been uninstalled. -{% endalert %} - -```json -// Uninstall Event: users.behaviors.Uninstall -{ - "id": (string) unique id of this event, - "user_id": (string) Braze user id of the user, - "external_user_id": (string) External ID of the user, - "time": (int) 10-digit UTC time of the event in seconds since the epoch, - "app_id": (string) id for the app on which the user action occurred, - "device_id": (string) id of the device on which the session occurred -} -``` - -{% endapi %} - {% api %} ## Attribution events 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 056db41b56c..5ab28588ae9 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 @@ -1296,3 +1296,29 @@ This event occurs when a user is enrolled in a control variant set on a multi-va {% endapi %} +{% api %} +## Uninstall events + +{% apitags %} +Uninstall +{% endapitags %} + +This event occurs when a user uninstalls an app. Use this data to track when users uninstall an app. While this is currently a message engagement event, this will be changed to a user behavior event in the future. + +{% alert important %} +This event is not fired when the user actually uninstalls the app, as that's impossible to track exactly. Braze sends a daily silent push to determine if the app still exists on your user's device, and if we get an error on that silent push, it is assumed the app has been uninstalled. +{% endalert %} + +```json +// Uninstall Event: users.behaviors.Uninstall +{ + "id": (string) unique id of this event, + "user_id": (string) Braze user id of the user, + "external_user_id": (string) External ID of the user, + "time": (int) 10-digit UTC time of the event in seconds since the epoch, + "app_id": (string) id for the app on which the user action occurred, + "device_id": (string) id of the device on which the session occurred +} +``` + +{% endapi %} \ No newline at end of file From 2ce7658e3586d2f48621559948fd0cd360165d07 Mon Sep 17 00:00:00 2001 From: Bre Fitzgerald Date: Fri, 9 Sep 2022 12:00:07 -0700 Subject: [PATCH 2/3] BD-1588 --- .../onboarding_with_braze/email_setup/ssl/ssl_clicktracking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/_user_guide/onboarding_with_braze/email_setup/ssl/ssl_clicktracking.md b/_docs/_user_guide/onboarding_with_braze/email_setup/ssl/ssl_clicktracking.md index 293ab93c89c..df756bfdd24 100644 --- a/_docs/_user_guide/onboarding_with_braze/email_setup/ssl/ssl_clicktracking.md +++ b/_docs/_user_guide/onboarding_with_braze/email_setup/ssl/ssl_clicktracking.md @@ -47,7 +47,7 @@ Braze will be unable to help you troubleshoot your CDN configuration. You must r | Sendgrid Step-By-Step Guides | Sparkpost Step-By-Step Guides | | -------- | --------- | -| [AWS Cloudfront](https://sendgrid.com/docs/ui/sending-email/universal-links/#setting-up-universal-links-using-cloudfront)
[CloudFlare](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-cloudflare)
[Fastly](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-fastly)
[KeyCDN](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-keycdn) | [AWS Cloudfront](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#aws-create)
[CloudFlare](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-cloudflare)
[Cloudfront](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/)
[Fastly](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-fastly)
[Google Cloud Platform](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#gcp-create)
[Microsoft Azure](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#azure-create) | +| [AWS Cloudfront](https://support.sendgrid.com/hc/en-us/articles/4412701748891-How-to-configure-SSL-for-click-tracking-using-CloudFront)
[CloudFlare](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-cloudflare)
[Fastly](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-fastly)
[KeyCDN](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-keycdn) | [AWS Cloudfront](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#aws-create)
[CloudFlare](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-cloudflare)
[Cloudfront](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/)
[Fastly](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-fastly)
[Google Cloud Platform](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#gcp-create)
[Microsoft Azure](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#azure-create) | ### CDN troubleshooting From ca3ecfb66bdfeb5c723246f987613d36dfc4a657 Mon Sep 17 00:00:00 2001 From: Kellie Hawks Date: Fri, 9 Sep 2022 16:15:35 -0400 Subject: [PATCH 3/3] Update Fuzzy Opt-Out to hidden --- .../sms/keywords/fuzzy_opt_out.md | 5 +++-- .../message_building_by_channel/sms/keywords/optin_optout.md | 2 ++ 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/_docs/_user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out.md b/_docs/_user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out.md index 86c27e0a28b..0b8e1019d67 100644 --- a/_docs/_user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out.md +++ b/_docs/_user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out.md @@ -6,6 +6,7 @@ page_type: reference channel: - SMS page_order: 1.1 +hidden: true --- # Fuzzy opt-out @@ -28,9 +29,9 @@ For example, "Stpo" or "Please stopppp" will be deemed fuzzy and a fuzzy opt-out ## Configure fuzzy opt-out -To configure fuzzy opt-out, navigate to the **Subscription Group Keyword Management** page. +To configure fuzzy opt-out, navigate to the subscription group keyword management page. 1. Under **Subscription Groups**, open the **SMS** section. -2. In **SMS Global Keywords**, select the **opt-out** category by selecting the pencil icon. +2. In **SMS Global Keywords**, find the **opt-out** category and select the pencil icon. 3. Enable **Fuzzy Opt-Out** by toggling it on. 4. Modify the fuzzy opt-out response as desired. diff --git a/_docs/_user_guide/message_building_by_channel/sms/keywords/optin_optout.md b/_docs/_user_guide/message_building_by_channel/sms/keywords/optin_optout.md index 3bbd28c9ca8..2ab32ac886d 100644 --- a/_docs/_user_guide/message_building_by_channel/sms/keywords/optin_optout.md +++ b/_docs/_user_guide/message_building_by_channel/sms/keywords/optin_optout.md @@ -30,8 +30,10 @@ Only the **exact, single-word message** will be processed (case _insensitive_). If a recipient uses the keywords `HELP` or `INFO`, a response will be triggered automatically. The SMS template for these automatic response messages will be set during your [onboarding][oblink] and phone number procurement period. Note that you may continue to update these responses after the initial onboarding period. + [oblink]: {{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/#setup-process