Branch.io电商事件日志未捕获，返回branch_view_enabled:false求助

Let’s start with the most obvious clue from your response: the branch_view_enabled: false field. This directly tells you that the event you’re sending won’t be rendered in the Branch Dashboard—so that’s the core issue we need to fix. Here’s a breakdown of possible causes and solutions:

1. Check if you’re manually setting branch_view_enabled to false #

Double-check your API request body. If you’ve explicitly added "branch_view_enabled": false to the payload, that’s why the event isn’t showing up. Remove this parameter or set it to true—Branch’s default behavior for valid e-commerce events is to enable dashboard visibility unless you override it.

2. Verify your event is a recognized Branch e-commerce event #

Branch only automatically tracks and displays its official predefined e-commerce events (like PURCHASE, ADD_TO_CART, VIEW_PRODUCT, etc.) in the dashboard. Even if you’re following the docs, make sure your event parameter uses the exact case-sensitive name from the official list. For example, purchase (lowercase) won’t be treated the same as PURCHASE (uppercase).

3. Confirm dashboard event settings are enabled #

Log into your Branch Dashboard and navigate to the Events section:

• Ensure the specific e-commerce event you’re sending is toggled on (some events might be disabled by default depending on your project setup).
• Check for any event filtering rules in Event Settings or Data Feeds that might be excluding your events from appearing in the dashboard.

4. Validate API authentication and request parameters #

Even if you’re using the doc-specified request, a small misconfiguration can break visibility:

• For server-side API calls: Make sure you’re using your project’s branch_secret for authentication (not the client-side branch_key).
• For client-side calls: Ensure the branch_key matches the one linked to your dashboard project.
• Double-check that required fields (like event, user_id or identity, and relevant e-commerce metadata like revenue) are included—missing required fields might cause Branch to mark the event as invalid and skip dashboard rendering.

5. Wait for data synchronization #

Branch’s dashboard can have a 5-10 minute delay for new events to appear. If you’re checking immediately after sending the request, give it some time and refresh the page before troubleshooting further.

If you’ve gone through all these steps and still don’t see the events, reach out to Branch’s support team with your request ID, project ID, and a copy of your API payload—they can dig into the backend logs to identify the issue.

内容的提问来源于stack exchange，提问作者harshit yadav