topic Impact Radius Integration (Tracking tags + API post from Deal change) in APIs & Integrations

Impact Radius Integration (Tracking tags + API post from Deal change)

MichaelWallis — Fri, 17 Jan 2020 13:19:05 GMT

Hi everyone

I have been tasked with an API integration for Impact Radius (https://impact.com/) for my client's Hubspot website. The integration needs to happen in two parts, which I have listed as #1 and #2 below. #1 I believe I should be able to accomplish however I have written out my solution just in case someone spots a fault somewhere. #2 is where I’d like some direction or guidance.

#1 Client side tracking tags

Impact has several tracking tags which will be placed in the <head> and <body> of the site, similar to Google analytics. When a user completes a certain form a Javascript action is fired on the thank you page, I use hubl to output the id & email of the contact into the parameters of the <script> tag.

Previously when doing this, there was a delay and so the details weren’t available immediately in hubl. My solution was and will be to introduce a middle-man page which simply has a loading animation for a couple seconds before taking the user to the thank you page.

#2 Posting data to Impact’s API

The sales team of my client use a contact property called Deal Stage to determine what the potential customer's status is. Once they have been set to a certain deal stage, an HTTP post needs to be made to Impact's API, to notify the system a deal has been made. There are several pieces of Impact account specific information which need to be sent as part of the payload.

How can I achieve this?

My only idea at the moment is to try use webhooks to post the data to an intermediary site, which re-organises the data and passes it on to Impact. Would this be a valid approach?

Re: Impact Radius Integration (Tracking tags + API post from Deal change)

Willson — Fri, 17 Jan 2020 14:14:20 GMT

Hi @MichaelWallis

Thanks for the details here on what you're doing. Taking a look into this, #1 looks ok in it's configuration.

For #2 would you be able to provide a bit more detail around this process. Webhooks could work from within HubSpot but we'd need a bit more of an understanding around what the process would ideally look like.

To elaborate on this point, for this to work in HubSpot, we'd need a trigger event, something to trigger this Webhook, especially if we're working with Webhooks via our Workflows tool.

As you mention deal stage (i'm not sure if this is within the external tool or HubSpot, so i'll assume the latter) this can be used as a trigger in the sense that, if a deal stage is equalled to a specific stage in HubSpot, we can enroll the Deal/Contact/Company etc which will then POST the relevant API data respective to the object that is enrolled.

However, you mention that this data is required to be specific for the external tool and so it would be recommended that you have something that can work through this to extract the required values before posting to your external tool.

If this is something that potentially suits, you can find more info on this here:

Webhook API Docs Info: https://developers.hubspot.com/docs/methods/workflows/webhook_information
Webhooks with Workflows: https://knowledge.hubspot.com/workflows/how-do-i-use-webhooks-with-hubspot-workflows

The 1st link will provide you with an idea of what data is posted when this workflow webhook is triggered.

I hope this helps!

Re: Impact Radius Integration (Tracking tags + API post from Deal change)

MichaelWallis — Mon, 20 Jan 2020 14:05:47 GMT

Hi Matthew

Thanks for your response.

I have been busy building out a potential solution for #2 using webhooks. Regarding the enrolment criteria, I have confirmed Deal Stage is a property we can use for this purpose, it will correctly fire the webhook.

I am currently building out a solution using Google Cloud Functions as the middle man. The webhook will post to a Google Cloud Function, which will re-organise the data and send it to Impact Radius.

I have managed to extract the data I need (the email address & VID) from the JSON, however I need to know whether the structure of the JSON that Hubspot sends on webhook posting will always be the same?

For e.g currently to get the email address I use ['properties']['email']['versions'][0]['value’], and to get the VID I am using ['properties']['hs_analytics_source']['versions'][0]['sourceId’]. This relies on Hubspots JSON always staying the same structure on posting.

Can you confirm this is the case?

Re: Impact Radius Integration (Tracking tags + API post from Deal change)

Willson — Mon, 20 Jan 2020 14:18:23 GMT

Hi @MichaelWallis

This is correct, the format should not be changing unless we make an update to the endpoint itself, which will be documented as part of our changes via our Changelog which can be found here:

https://developers.hubspot.com/changelog

I hope this helps!

Re: Impact Radius Integration (Tracking tags + API post from Deal change)

MichaelWallis — Wed, 22 Jan 2020 12:53:32 GMT

Hi Matt

Thanks for this, I think this means that Google Cloud Functions will be a valid middle man between Hubspot & Impact Radius.

The last piece of the puzzle appears to be a piece of information which is stored in step #1, but also needs to be sent to the API in step #2. This piece of data is passed through the Url when the potential customer first lands on the site, and needs to be stored on form submit. To store this I believe should be quite straightforward: Create a custom property, add it as . a hidden field and then populate the field using the form JS.

The question, is how can I send this piece of information using a webhook? Is it possible to send custom properties using webhooks? Or would I somehow need to query the Hubspot API for this information?

Re: Impact Radius Integration (Tracking tags + API post from Deal change)

Willson — Thu, 23 Jan 2020 09:31:03 GMT

Hi @MichaelWallis

The hidden field solution should suffice when it comes to storing this value on form submit. For the Webhook, we do support the use of Customer Properties via Webhooks.

I was able to find a thread where my colleague, Isaac, explains how it works with custom properties. Take a look here:

https://community.hubspot.com/t5/APIs-Integrations/Webhook-Events-on-Custom-Properties/td-p/222017