HubSpot

Use this when you want each submitted response to appear on the matching HubSpot contact as a custom event.

getuserfeedback.com sends submitted response activity to HubSpot. Your response submission must include the HubSpot contact ID as an external ID.

1. Create a HubSpot API token

In HubSpot, create a service key. If service keys are not available in your account, create a private app instead.
Give it access to custom events.
Copy the service key or private app access token.

Paste this token into the HubSpot integration in getuserfeedback.com.

2. Create a custom event in HubSpot

Create a custom event for submitted responses in HubSpot. Add these event properties with the exact internal names:

response_id
flow_id
page_path
page_referrer
locale

If you want HubSpot to store response metadata tags, also add one property for each tag you send, using gx_response_metadata_ plus the metadata key.

Copy the event's fully qualified internal name, then paste it into Event name in getuserfeedback.com.

HubSpot event names are portal-specific and usually look like pe123456_response_submitted. Use the exact value HubSpot shows.

3. Send the HubSpot contact ID with the response

When you submit a response, include the HubSpot contact ID as an external ID:

externalIds: [{id: "123456",type: "hubspot-contact-id",collection: "users",encoding: "none",},]

That external ID becomes externalId.users.none.hubspot-contact-id internally and is used as HubSpot's contact object ID for the custom event. See Identity resolution for how external IDs are sent.

What we send

For each submitted response, getuserfeedback.com sends one HubSpot custom event. The request includes:

Field	How we set it
`eventName`	The fully qualified HubSpot custom event `internal name` from your integration settings.
`objectId`	The HubSpot contact ID submitted as `externalId.users.none.hubspot-contact-id`.
`occurredAt`	When the response was submitted.
`properties.response_id`	The response ID.
`properties.flow_id`	The flow ID, when available.
`properties.page_path`	The page path from response context, when available.
`properties.page_referrer`	The page referrer from response context, when available.
`properties.locale`	The response locale, when available.
`properties.gx_response_metadata_*`	Response metadata tags. Tags are skipped when the full HubSpot property name is longer than 50 characters; values are shortened to 256 characters.

Send a test event

Open the HubSpot integration in getuserfeedback.com.
Click Send test event.
Enter a HubSpot contact ID from your HubSpot portal.
Send the test event and check the request/response trace.
In HubSpot, open that contact and confirm the custom event appears.

What can break

The integration says the event name is invalid. Copy the custom event internal name from HubSpot. Do not use the display label.
HubSpot rejects the request. Check that the HubSpot token can send custom event data.
The event is missing a contact. Submit externalId.users.none.hubspot-contact-id with the response, or use Send test event with a real HubSpot contact ID.