search

rudderlabs / rudder-server

Privacy and Security focused Segment-alternative, in Golang and React
https://www.rudderstack.com/
Other
4.08k stars 315 forks source link

User details not being sent to Destination Intercom #5213

Open nihallocalo opened 5 days ago

nihallocalo commented 5 days ago

Describe the bug When sending an Identify event from Backend(JavaScript) to Intercom as the destination via RudderStack, an error is returned stating "User Not Found." The event fails to process and does not reach Intercom.

Steps to reproduce the bug

Go to the RudderStack dashboard. Select the source as Elixir Set Intercom as the destination for the event. Trigger an Identify event from the Elixir Check the live event logs in RudderStack for the event delivery status. Observe the error message. Expected behavior The Identify event should be successfully processed and delivered to Intercom, with the user being recognized and identified in the system.

Screenshots : image image image

Desktop (please complete the following information):

OS: macOS Monterey 12.6 Browser: Chrome Version: 117.0.5938.132

Smartphone (please complete the following information): NA

Any additional context

The error may be caused by an incorrect or missing user identifier (e.g., userId or email) in the payload from GA4 to Intercom. This issue could be related to the mapping of user attributes in RudderStack between GA4 and Intercom. This issue can be because of the new pages with events firing before _identify

contributor-support[bot] commented 5 days ago

Thanks for opening this issue! We'll get back to you shortly. If it is a bug, please make sure to add steps to reproduce the issue.