Skip to content

User details not being sent to Destination Intercom #5213

Open
@nihallocalo

Description

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions