# Restrict contact creation when using Visitor Idenfication

**URL:** <https://community.hubspot.com/t/restrict-contact-creation-when-using-visitor-idenfication/143068>\
**Category:** APIs & Integrations\
**Tags:** contacts\
**Created:** [November 20, 2025, 2:46am UTC](https://community.hubspot.com/t/restrict-contact-creation-when-using-visitor-idenfication/143068 "2025-11-20T02:46:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JazReyes](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@JazReyes](https://community.hubspot.com/u/JazReyes)\
**Post date:** [November 20, 2025, 2:46am UTC](https://community.hubspot.com/t/restrict-contact-creation-when-using-visitor-idenfication/143068/1 "2025-11-20T02:46:47Z")

</div>

Hi,

We are currently using this [https://developers.hubspot.com/docs/api-reference/legacy/tracking-code-v1/identify](https://developers.hubspot.com/docs/api-reference/legacy/tracking-code-v1/identify) to identify the contact used for HubSpot Live Chat conversations. Apparently, this auto-creates the contact if it is not yet existing. Is there a way to prevent this? This will break our contact creation process if it will automatically create via the chat.

Thank you!

---

<div class="post-metadata">

**Author:** ![RubenBurdin](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rubenburdin/32/75212_2.png) [@RubenBurdin](https://community.hubspot.com/u/RubenBurdin)\
**Post date:** [November 20, 2025, 10:24pm UTC](https://community.hubspot.com/t/restrict-contact-creation-when-using-visitor-idenfication/143068/2 "2025-11-20T22:24:43Z")

</div>

Hi @JazReyes You’re right about what you’re seeing. The identify call is designed to tie an email to the browser cookie and either update an existing contact or create a new one if none exists. That is baked into how HubSpot’s tracking code works: when you send an email via the Tracking Code API, HubSpot links it to the hubspotutk cookie and will create a contact record if needed so future analytics can attach somewhere

([https://developers.hubspot.com/docs/api-reference/legacy/tracking-code-v1/overview )](https://developers.hubspot.com/docs/api-reference/legacy/tracking-code-v1/overview)

([https://knowledge.hubspot.com/account/how-does-hubspot-track-visitors )](https://knowledge.hubspot.com/account/how-does-hubspot-track-visitors)

There is no switch to “identify but never create.”

So to avoid breaking your contact creation process, the workaround is architectural, not a setting. Typical patterns are:

- Only call identify after you have already created the contact in HubSpot via your own flow (check Contacts API by email; if no record exists, skip identify for that chat).
- Or, if your process allows it, keep some chats fully anonymous and do not call identify at all until your system decides the contact should exist.

Quick question so you can pick the right pattern: are you okay if some chat visitors remain anonymous in HubSpot until your own system approves creating them?

If duplicates start upstream in other tools, Stacksync reduces them by syncing normalized records into HubSpot rather than batch-importing surprises.

---

<div class="post-metadata">

**Author:** ![GRajput](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/grajput/32/102020_2.png) [@GRajput](https://community.hubspot.com/u/GRajput)\
**Post date:** [November 28, 2025, 1:07pm UTC](https://community.hubspot.com/t/restrict-contact-creation-when-using-visitor-idenfication/143068/3 "2025-11-28T13:07:47Z")

</div>

Hi @JazReyes

As of now there is no direct solution to do this. It is not possible to supress the contact creation. for more details you can contact HubSpot support, they can guide you here better.  
Thanks!