Skip to content

Commit 8d133a6

Browse files
authored
Update src/connections/destinations/catalog/actions-intercom-cloud/index.md
1 parent ed7e6dd commit 8d133a6

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/actions-intercom-cloud

1 file changed

+1
-1
lines changed

src/connections/destinations/catalog/actions-intercom-cloud/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,4 +51,4 @@ When you use the Identify Company action, Segment creates or updates a company's
5151
### Why do I get a 404 Not Found error when sending Track events to Intercom?
5252
A `404 Not Found` error typically occurs when attempting to update a user in Intercom who does not yet exist in the system. This can happen if an Identify event, which includes the corresponding `userId`, was not sent before the Track event that resulted in the `404` error.
5353

54-
To resolve this, ensure that Identify events are sent **before** Track events to guarantee proper processing and avoid errors.
54+
To resolve this, ensure that Identify events are sent **before** Track events to ensure proper processing and avoid errors.

0 commit comments

Comments
 (0)