Issue

When using the Segment HubSpot Cloud Mode (Actions) destination, your contacts and companies may update successfully, but they fail to associate with each other, resulting in a 404 error. During the association step, you will see an error from HubSpot stating No contact with ID [contact_id] exists. This happens when a contact is deleted and recreated in HubSpot, but the same userId is used in Segment.

Product

Twilio Segment

Environment

Segment Console

Cause

The HubSpot Cloud Mode destination maintains an internal mapping between the Segment userId and the HubSpot contact ID. This mapping persists even if the contact is deleted directly inside HubSpot. When you reuse the original userId in Segment, the destination attempts to perform the association using the old, stale HubSpot contact ID, causing HubSpot to return a 404 error because that ID no longer exists. There is currently no self-service method to manually reset or clear this internal mapping.

Resolution

To resolve this error and successfully associate the contact with the company, you must force Segment to generate a fresh mapping by using a new identifier.

1. Update the userId to a new, unique value for the affected contact within your environment.

2. Send a new identify or group event from Segment using this updated userId.