Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Dec 19, 2025

The page implied all users need custom push analytics handling and incompletely explained the workflow, creating potential FUD and confusion.

Changes

Main page (logging_message_data.md)

  • Added prominent alert: page only applies to custom notification handling implementations
  • Clarified Braze SDK handles analytics automatically for standard integrations

Android & Swift sections

  • Restructured "Logging data with Braze API" into explicit workflow:
    • Step 1: Configure braze_id in push payload via dashboard
    • Step 2: Extract braze_id from payload and POST to /users/track endpoint
  • Added JSON example clarifying braze_id or external_id can identify users:
{
  "events": [{
    "braze_id": "abc123xyz",
    "name": "push_notification_opened",
    "time": "2024-01-01T00:00:00Z"
  }]
}
  • Improved section organization and readability
Original prompt

This section details on the original issue you should resolve

<issue_title>[BD-5174]:Logging Message Data page confusing and possibly a source of FUD</issue_title>
<issue_description>Description: This page, I think, it trying to talk about how to log analytics if using a custom handler for push messages. But it never really clearly says that, and I think it implies some incorrect things:

  1. It makes it sound like you need to do custom handling for push analytics regardless of your push setup (which could be used by other companies as FUD)
  2. The first part of the page, about passing the Braze userID, makes it sounds like that step is both necessary and sufficient to pass analytics, but I'm pretty sure it's only (maybe) necessary, and the instructions there are incomplete- once you've passed the data, what happens next?

I ran my concerns by an SA, who agreed about the content being confusing and those issues above potentially being a problem.
Request Url: https://www.braze.com/docs/developer_guide/push_notifications/logging_message_data/?tab=custom%20events
JIRA: BD-5174</issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Fixes #10535

Copilot AI changed the title [WIP] Fix confusing content on Logging Message Data page Clarify logging_message_data.md is only for custom push notification handlers Dec 19, 2025
@rachel-feinberg rachel-feinberg removed their request for review December 22, 2025 19:55
@rachel-feinberg rachel-feinberg changed the title Clarify logging_message_data.md is only for custom push notification handlers [BD-5174] Clarify logging_message_data.md is only for custom push notification handlers Dec 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BD-5174]:Logging Message Data page confusing and possibly a source of FUD

2 participants