Contact identify

Hi there,

I’m currently working on s2s integration to Hubspot. We are using two types of requests:

1) Sending a request from the server to _ptq.gif (we simulate on the server the operation of the pixel and use our user ids)

2) Adding a contact after actions via API: Accounts Dashboard | HubSpot.

But is there any way to link the created contact with the requests made to _ptq.gif from it? Usually for this you can pass the same client id that is used in ptq.gif, but I don’t see such options in the documentation. Am I missing something or are there any other options to do this?

Thanks in advance!


@Dtape wrote:

Hi there,

I’m currently working on s2s integration to Hubspot. We are using two types of requests:

1) Sending a request from the server to _ptq.gif (we simulate on the server the operation of the pixel and use our user ids)

2) Adding a contact after actions via API: Accounts Dashboard | HubSpot.

But is there any way to link the created contact with the requests made to _ptq.gif from it? Usually for this you can pass the same client id that is used in ptq.gif, but I don’t see such options in the documentation. Am I missing something or are there any other options to do this?

Thanks in advance!


Regarding linking the created contact with requests made to _ptq.gif, you’re correct that passing the same client ID used in ptq.gif could typically achieve this. However, I don’t see such options mentioned in the documentation either.

One alternative approach could be to include a unique identifier or token in the payload of the _ptq.gif request, which can then be stored as a property or custom field in the HubSpot contact record. This way, you can correlate the contact with the specific requests made.