Why did a company with no intent trigger my web intent workflow?

In some cases, intent may appear to be incorrectly attributed to a company when a user initially visits or signs up using an email address from one organization but later logs into an app, or switches wifi with an address from another. When this happens, Unify’s web tag automatically updates the user’s association to the correct organization. As a result, any intent signals that were previously tied to the original company are removed, ensuring that intent data accurately reflects the company that the user is currently associated with.

It's important to note that IP-based company identification has inherent limitations and typically achieves around 70% accuracy. Factors such as remote work, VPN usage, travel, and distributed company networks can affect identification accuracy. While the scenario described above is one specific case, some level of company misattribution is expected due to these fundamental limitations of IP data.

To mitigate these identification challenges, you can implement a workaround by adding a delay node after the trigger, followed by an If-Else node that rechecks the trigger conditions against the audience in the workflow. The sequence of events would be as follows:

1. The user is initially associated with the incorrect organization.

2. A workflow is triggered for the incorrect organization.

3. The delay node is initiated.

4. The is re-associated with the correct organization.

5. The delay node completes its process.

6. The If-Else node evaluates whether the incorrect organization meets the specified conditions. Since the user's data has been reassigned, the condition will now evaluate as false, and the workflow will proceed down the Else path.