Leftover Deploy Pt. 2 - March 24, 2023

Gemfile

@@ -1,9 +1,9 @@
 source "https://rubygems.org"
 ruby '~> 2.7.0'
-gem "jekyll", "~> 4.2.2"
+gem "jekyll", "~> 4.3.2"
 
 gem 'sassc'
-gem 'kramdown', ">= 2.3.1"
+gem 'kramdown', ">= 2.4"
 gem 'kramdown-parser-gfm'
 gem 'rouge'
 gem 'rack-jekyll'

Gemfile.lock

@@ -30,7 +30,7 @@ GEM
       httpclient (~> 2.8, >= 2.8.3)
       json (>= 1.5.1)
     colorator (1.1.0)
-    concurrent-ruby (1.1.10)
+    concurrent-ruby (1.2.2)
     em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
@@ -39,65 +39,68 @@ GEM
     ffi (1.15.5)
     filesize (0.2.0)
     forwardable-extended (2.6.0)
+    google-protobuf (3.22.2)
+    google-protobuf (3.22.2-x86_64-linux)
     http_parser.rb (0.8.0)
     httpclient (2.8.3)
     i18n (1.12.0)
       concurrent-ruby (~> 1.0)
-    jekyll (4.2.2)
+    jekyll (4.3.2)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
       i18n (~> 1.0)
-      jekyll-sass-converter (~> 2.0)
+      jekyll-sass-converter (>= 2.0, < 4.0)
       jekyll-watch (~> 2.0)
-      kramdown (~> 2.3)
+      kramdown (~> 2.3, >= 2.3.1)
       kramdown-parser-gfm (~> 1.0)
       liquid (~> 4.0)
-      mercenary (~> 0.4.0)
+      mercenary (>= 0.3.6, < 0.5)
       pathutil (~> 0.9)
-      rouge (~> 3.0)
+      rouge (>= 3.0, < 5.0)
       safe_yaml (~> 1.0)
-      terminal-table (~> 2.0)
-    jekyll-sass-converter (2.2.0)
-      sassc (> 2.0.1, < 3.0)
+      terminal-table (>= 1.8, < 4.0)
+      webrick (~> 1.7)
+    jekyll-sass-converter (3.0.0)
+      sass-embedded (~> 1.54)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
     jekyll_asset_pipeline (0.6.2)
       jekyll (>= 3.5, < 5.0)
       liquid (~> 4.0)
-    json (2.6.2)
+    json (2.6.3)
     kramdown (2.4.0)
       rexml
     kramdown-parser-gfm (1.1.0)
       kramdown (~> 2.0)
-    liquid (4.0.3)
-    listen (3.7.1)
+    liquid (4.0.4)
+    listen (3.8.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
     mercenary (0.4.0)
-    mini_portile2 (2.8.0)
+    mini_portile2 (2.8.1)
     mustermann (3.0.0)
       ruby2_keywords (~> 0.0.1)
     nio4r (2.5.8)
-    nokogiri (1.13.10)
+    nokogiri (1.14.2)
       mini_portile2 (~> 2.8.0)
       racc (~> 1.4)
-    nokogiri (1.13.10-x86_64-linux)
+    nokogiri (1.14.2-x86_64-linux)
       racc (~> 1.4)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    progressbar (1.11.0)
-    public_suffix (5.0.0)
-    puma (5.6.5)
+    progressbar (1.13.0)
+    public_suffix (5.0.1)
+    puma (6.1.1)
       nio4r (~> 2.0)
-    racc (1.6.1)
+    racc (1.6.2)
     rack (2.2.6.4)
     rack-jekyll (0.3.5)
       jekyll
       rack
-    rack-protection (3.0.4)
+    rack-protection (3.0.5)
       rack
-    rack-proxy (0.7.4)
+    rack-proxy (0.7.6)
       rack
     rack-reverse-proxy (0.12.0)
       rack (>= 1.0.0)
@@ -108,34 +111,38 @@ GEM
     rb-inotify (0.10.1)
       ffi (~> 1.0)
     rexml (3.2.5)
-    rouge (3.30.0)
+    rouge (4.1.0)
     ruby2_keywords (0.0.5)
     safe_yaml (1.0.5)
+    sass-embedded (1.54.6)
+      google-protobuf (~> 3.19)
+      rake (>= 10.0.0)
     sassc (2.4.0)
       ffi (~> 1.9)
-    sinatra (3.0.4)
+    sinatra (3.0.5)
       mustermann (~> 3.0)
       rack (~> 2.2, >= 2.2.4)
-      rack-protection (= 3.0.4)
+      rack-protection (= 3.0.5)
       tilt (~> 2.0)
-    terminal-table (2.0.0)
-      unicode-display_width (~> 1.1, >= 1.1.1)
-    tilt (2.0.11)
+    terminal-table (3.0.2)
+      unicode-display_width (>= 1.1.1, < 3)
+    tilt (2.1.0)
     uglifier (4.2.0)
       execjs (>= 0.3.0, < 3)
-    unicode-display_width (1.8.0)
+    unicode-display_width (2.4.2)
     verbal_expressions (0.1.5)
+    webrick (1.8.1)
 
 PLATFORMS
   ruby
   x86_64-linux
 
 DEPENDENCIES
   algolia_html_extractor!
-  jekyll (~> 4.2.2)
+  jekyll (~> 4.3.2)
   jekyll-algolia (~> 1.0)!
   jekyll_asset_pipeline
-  kramdown (>= 2.3.1)
+  kramdown (>= 2.4)
   kramdown-parser-gfm
   puma
   rack

_config.yml

@@ -228,15 +228,14 @@ algolia:
       - searchable(channel)
     searchableAttributes:
       - article_title
-      - headings
-      - unordered(description)
+      - description
       - search_rank
       - nav_title
-      - Path_01
       - url
+      - Path_01
       - collection,tags
       - content
-      - platform
+      - unordered(platform)
       - channel
     customRanking:
       - desc(article_title)

_docs/_hidden/other/handbooks.md

@@ -6,11 +6,13 @@ permalink: /handbooks/
 # Support & Success Services Handbook
 <br>
 
+- [Support & Success Services Handbook FY'24 PDF][4]
 - [Support & Success Services Handbook FY'23 PDF][3]
 - [Support & Success Services Handbook FY'22 PDF][2]
 - [Support & Success Services Handbook FY'21 PDF][1]
 
 
+[4]: {{site.baseurl}}/assets/download_file/Braze_Success_and_Support_Services_Handbook_24.pdf
 [3]: {{site.baseurl}}/assets/download_file/Braze_Success_and_Support_Services_Handbook_23v17.pdf
 [2]: {{site.baseurl}}/assets/download_file/Braze_Success_and_Support_Services_Handbook_22.pdf
 [1]: {{site.baseurl}}/assets/download_file/Braze_Success_and_Support_Services_Handbook_21.pdf

_docs/_partners/canvas_steps/facebook_audience_sync.md

@@ -169,6 +169,20 @@ Facebook does not provide this information for privacy reasons.
 At this time, value-based custom audiences are not supported by Braze. If you are interested in syncing these types of custom audiences, reach out to your customer success manager or contact support.
 {% enddetails %}
 
+{% details Why did I receive a Braze email "Accept Facebook terms of service to complete Audience Sync step"? %}
+
+We have received an error from Facebook regarding the user account used to connect to Facebook. As a result, Braze has temporarily disabled your Audience Sync step until this has been corrected. 
+
+To fix this, you must agree to one of Facebook's terms of service:
+
+- User ToS: `https://business.facebook.com/ads/manage/customaudiences/tos/`
+- Account ToS: `https://business.facebook.com/ads/manage/customaudiences/tos/?act=<%= @ad_account_id %>`
+
+Once you have accepted the terms of service, you must do the following:
+1. Refresh your Facebook access token with Braze by disconnecting and reconnecting your Facebook Account.
+2. Re-enable your Facebook Audience Sync step by editing and updating your Canvas. Braze will then be able to sync users as soon as they reach the Facebook audience step. 
+{% enddetails %}
+
 [0]: https://www.braze.com/privacy
 [1]: https://www.facebook.com/business/help/113163272211510
 [2]: https://www.facebook.com/business/help/910137316041095

_docs/_partners/home.md

@@ -243,4 +243,6 @@ valid_partner_list:
   url: /docs/partners/message_personalization/localization/phrase/
 - name: Merkury
   url: /docs/partners/data_and_infrastructure_agility/analytics/merkury/
+- name: WhatsApp
+  url: /docs/user_guide/message_building_by_channel/whatsapp/
 ---

_docs/_user_guide/message_building_by_channel/whatsapp/overview.md

@@ -18,7 +18,7 @@ page_order: 0
 Acknowledge the following before proceeding with integration:
 
 - **Opt-in policy:** WhatsApp requires businesses to have customers opt-in to messaging.
-- **WhatsApp content rules:** WhatsApp has several [content rules](https://www.whatsapp.com/legal/commerce-policy?l=et) that need to be followed.
+- **WhatsApp content rules:** WhatsApp has several [content rules](https://www.whatsapp.com/legal/commerce-policy?l=en) that need to be followed.
 - **Compliance:** Comply with all applicable Braze and Meta documentation and any applicable [Meta policies](https://www.whatsapp.com/legal/?lang=en).
 - **24-hour conversation limits:** After a business sends an initial templated message or a user sends a message, a 24-hour window will occur where the two parties can message back and forth. 
 - **Initiating conversation:** Users can initiate a conversation at any point. A business can only initiate a conversation through an approved message template.
@@ -60,7 +60,7 @@ Once the setup is complete, a dedicated WhatsApp subscription group will be crea
 
 Only approved WhatsApp message templates can be used to initiate conversations with customers. WhatsApp templates can be built in the [Meta Business Manager](https://www.facebook.com/business/help/2055875911147364?id=2129163877102343).
 
-1. **Navigate to the [template manager](https://business.facebook.com/wa/manage/message-template)**<br>
+1. **Navigate to the [template manager](https://business.facebook.com/wa/manage/message-templates)**<br>
 In the Meta Business Manager, under **Account Tools**, select **Message Templates**.
 Next, select **Create Templates**.<br><br>![][3]{: style="max-width:100%;"}<br><br>
 2. **Message settings**<br>

_docs/_user_guide/personalization_and_dynamic_content/liquid/advanced_filters/message_extras.md

@@ -0,0 +1,43 @@
+---
+nav_title: Message Extras Tag
+article_title: Message Extras Tag
+page_order: 1
+description: "This article explains how to use the message extras Liquid tag and how to check for syntax."
+alias: "/message_extras_tag/"
+---
+
+# Message extras Liquid tag
+
+Using the `message_extras` Liquid tag, you can annotate your send events with dynamic data from Connected Content, custom attributes (such as language, country), and Canvas entry properties. This Liquid tag appends key-value pairs to the corresponding send event in Currents.
+
+{% alert important %}
+This Liquid tag is currently in beta for email, SMS, and push send events. Contact your Braze customer success manager if you're interested in participating in the beta.
+{% endalert %}
+
+To send dynamic or extra data back to your Currents send event, insert the proper Liquid tag in the body of your email message. The following is an example of the standard Liquid tag format for `message_extras`: 
+
+{% raw %}
+```
+{% message_extras :key test :value 123 %}
+```
+{% endraw %}
+
+You can add these tags as needed for your key-value pairs in the message body. However, the length of all keys and values should not exceed 1KB. In Currents, you'll see a new event field called `message_extras` for your send events. This will generate a JSON serialized string in one field. 
+
+## Checking syntax
+
+Any other input that doesn't match the aforementioned tag standard may fail to pass to Currents. Check that your syntax or formatting doesn't include any of the following:
+
+- Non-existent, empty, or mistyped delimiters
+- Duplicate keys (Braze will default to sending the key-value pair that is encountered first)
+- Extra text before keys or values are defined
+- Out of order keys and values 
+  - {% raw %}For example, ```{% message_extras :value 123 :key test %}```{% endraw %}
+
+## Considerations
+
+- If your key-values exceed 1KB, they'll truncate. 
+- Whitespace will count towards the character count. Note that Braze omits the leading and trailing whitespaces.
+- The resulting JSON will output only string values.
+- Liquid variables can be included as a key or value, but Liquid tags are not supported directly. 
+  - For example, {% raw %}```{% assign value = '123' %} {% assign key = 'test' %} {% message_extras :key {{key}} :value {{value}} %}```{% endraw %}