Fixing 404s - June 2024

[internetisaiah]

Pull Request/Issue Resolution

Description of Change:

Bi-annual maintenance for fixing 404s - June 2024. Google sheet here.

Here's the links that were fixed (with the latest deployment sub URL):

• https://braze-docs-554qcwaf5-braze.vercel.app/docs/developer_guide/platform_integration_guides/android/content_cards/customization
• https://braze-docs-554qcwaf5-braze.vercel.app/docs/canvas_data_retention
• https://braze-docs-554qcwaf5-braze.vercel.app/docs/partners/message_orchestration/channel_extensions/ecommerce/shopify/shopify_features/shopify_catalogs/back_in_stock
• https://braze-docs-554qcwaf5-braze.vercel.app/docs/user_guide/message_building_by_channel/content_cards/integration
• https://braze-docs-554qcwaf5-braze.vercel.app/docs/user_guide/data_and_analytics/your_reports

Is this change associated with a Braze feature/product release?

• Yes (Insert Feature Release Date Here)
• No

---

✔️ Pull Request Checklist

• Check that you haven't removed any images (replacing an image with an updated one of the same name is fine), as this breaks the French site
• Check that all links work.
• Ensure you have completed our Contributors License Agreement.
• Tag @josh-mccrowell-braze and @internetisaiah as a reviewer when your work is done and ready to be reviewed for merge. Are you an internal product manager? Reference the internal reviewing chart to tag the appropriate reviewer.
• If the documentation involves a 1) paid SKU, 2) a third party, 3) SMS, 4) AI, or 5) privacy, ensure that Ana Teresa Serafino on the Legal team has signed off.
• Tag others as reviewers as necessary.
• If you have modified any links, be sure to add redirects to assets > js > broken_redirect_list.js

⭐ Helpful Wiki Shortcuts

• Writing Style Guide
• Image Style Guide
• Styling Test Page

❗ ATTN: For PR Reviewers

• Read our Reviewing a PR page for more on our reviewing suggestions.
• Read our Previewing Documentation page to see how to check the deployment.
  • Preview all changes in the linked Vercel environment by clicking the preview link in the vercel-bot comment in your PR.

❗ ATTN: Internal Reviewing Chart

Work at Braze and not sure who to tag for review?
Before tagging @josh-mccrowell-braze or @internetisaiah for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.

Reviewer	Product Vertical
@josh-mccrowell-braze	Monolith Deployments Quality Infrastructure Platform Infrastructure Datalake SDKs Currents
@internetisaiah	Developer Guide Technology partners Channels
@bre-fitzgerald	Intelligence In-App Messages Channels Frontend Infrastructure & Experience (FIX)
@lydia-xie	Ingestion Core Objects Core Messaging Messaging Experience Message Components Email (Composition and Infrastructure) (tag @rachel-feinberg for Liquid use cases)
@rachel-feinberg	Customer Lifecycle, Identity and Permissions SMS User Targeting Reporting

[lydia-xie]

lgtm! Might need to flag that a FR doc has been updated with Zeyuan, not sure 🤔

[internetisaiah]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[internetisaiah]

@zzhaobraze , looks like the vercel issue is good on this one. we can merge this one and refresh fr whenever you're free. just let me know 👍🏽

[zzhaobraze]

@internetisaiah the FR should be updated once merged to main.

[internetisaiah]

*Fixing merge conflicts