topic Assistance Needed - Issue with Google & Facebook Leads Tracking After API Shift in APIs & Integrations

Assistance Needed - Issue with Google & Facebook Leads Tracking After API Shift

SKundu6 — Thu, 05 Dec 2024 06:37:42 GMT

Hi everyone,

I hope you are doing well. We need assistance with an issue that has come up after we transitioned from using Hapikey (v2 version) to a Private App (v3 version) for our API calls. Since this change, we've had trouble tracking Google and Facebook leads in our HubSpot contacts list.

Previously, using [specific code], tracking for Google contacts worked correctly with the v2 version. However, after switching to the v3 version, the tracking no longer differentiates properly between Google and Facebook leads. Instead, [specific code] seems to aggregate contacts from both sources under a single filter in the HubSpot contacts list, specifically under the "Original source drill-down 2" filter option.

Could you help us resolve this issue so that we can correctly track and differentiate leads coming from Google and Facebook separately, as we did before?

Your prompt attention to this matter would be greatly appreciated.

Thank you in advance for your help and support.

Re: Assistance Needed - Issue with Google & Facebook Leads Tracking After API Shift

GRajput — Thu, 05 Dec 2024 14:26:25 GMT

Hi @SKundu6

here is the link of the Custom Objects API's

https://developers.hubspot.com/beta-docs/reference/api/crm/objects/custom-objects

you can read the custom property from here and send it when the webhook is called

I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.
Thanks!

Re: Assistance Needed - Issue with Google & Facebook Leads Tracking After API Shift

SKundu6 — Mon, 09 Dec 2024 07:04:46 GMT

Hi @GRajput,

Thank you for your response.

We have used "Custom Objects API" concept in following way:

We have implemented a "Javascript Cookie" concept on our website pages to track the "utm_source" of visitors coming from Facebook or Google ads. This "utm_source" is then sent to the Deal creation API call and stored in a custom property called "contact_source." While this logic works for some contacts, it does not consistently capture the source for all contacts coming from Facebook or Google ads.

We are using Private App concept in version 3, we are using PHP CURL call concept. Following are the sample:

API endpoint link: https://api.hubapi.com/crm/v3/objects/deals
Request parameters:
$properties = array(
//Other request parameters
'contact_source' => $_COOKIE['sf_source']
);
$hubspot_fields = array(
'properties' => $properties
);

Apart from above logic, we have used the JavaScript tracking script throughout the pages of the website:

This script serves to display the HubSpot chat option on the website and also facilitates the storage of contact source indicators (e.g., Paid social, Paid search) in the 'Original source drill-down 2' filter option in V2.

Should you require further details, please don't hesitate to ask, and we'll gladly provide additional information.

Thank you again.

Re: Assistance Needed - Issue with Google & Facebook Leads Tracking After API Shift

GRajput — Mon, 09 Dec 2024 12:57:33 GMT

Hi @SKundu6

What I understood is that You are creating a deal and want to update the contact custom property. Is it so?
If yes then you will need two APIs here, one to create a deal and the other to update the existing contact's property.

I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.
Thanks!

Re: Assistance Needed - Issue with Google & Facebook Leads Tracking After API Shift

SKundu6 — Thu, 12 Dec 2024 06:51:06 GMT

Hi @GRajput,

Thank you for your response.

We're looking to streamline the process of tagging the contact_source for our deals in HubSpot. Specifically, we want to track whether a deal is being generated from Google Ads or Facebook Ads and automatically update the deal's contact_source property accordingly.

Should you require further details, please don't hesitate to ask, and we'll gladly provide additional information.

Thank you again.

Re: Assistance Needed - Issue with Google & Facebook Leads Tracking After API Shift

GRajput — Fri, 13 Dec 2024 06:50:00 GMT

Hi @SKundu6

Could you please explain from where you are getting the source value that you are want to send in as a deal's contact_source property?

Thanks!

Re: Assistance Needed - Issue with Google & Facebook Leads Tracking After API Shift

SKundu6 — Mon, 16 Dec 2024 06:55:33 GMT

Hi @GRajput,

Thank you for your response.

We are using the COOKIE mechanism to capture the `utm_source`. This allows us to store and track the source of traffic, such as 'google', 'facebook', etc. During the Deal API call, we include the value of the `utm_source` from the COOKIE to ensure the source attribution is carried forward accurately.

Following JS script is used for COOKIE:

if (!currentPage.includes('socialsignup')) {

/* Checking ad source from URL param: start */
// Check if the URL contains 'google'
if (currentPage.includes('google')) {
url_sf_source = 'google';
}
// Check if the URL contains 'fb'
else if (currentPage.includes('fb')) {
url_sf_source = 'facebook';
}
// Check if the URL contains 'Facebook'
else if (currentPage.includes('Facebook')) {
url_sf_source = 'facebook';
}
// Check if the URL contains 'sf_source'
else if (currentPage.includes('sf_source')) {
// Extract the value of sf_source from the URL
var sfSourceIndex = currentPage.indexOf('sf_source=');
if (sfSourceIndex !== -1) {
var sfSourceValue = currentPage.substring(sfSourceIndex + 10); // Length of 'sf_source=' is 10
// Find the end of sf_source value
var sfSourceEndIndex = sfSourceValue.indexOf('&');
if (sfSourceEndIndex !== -1) {
url_sf_source = sfSourceValue.substring(0, sfSourceEndIndex);
} else {
url_sf_source = sfSourceValue;
}
}
}
// Check if the 'utm_source' parameter is present and set the sf_source accordingly
else {
// Parse the URL to extract query parameters
var urlParams = new URLSearchParams(window.location.search);

// Check if the 'utm_source' parameter is present and set the sf_source accordingly
if (urlParams.has('utm_source')) {
var utmSourceValue = urlParams.get('utm_source');

// Check for 'google'
if (utmSourceValue.toLowerCase() === 'google') {
url_sf_source = 'google';
}
// Check for 'facebook'
else if (utmSourceValue.toLowerCase() === 'facebook') {
url_sf_source = 'facebook';
}
// Add additional conditions for other sources if needed
}
}
/* Checking ad source from URL param: end */

// Check if sf_source is null, undefined, or empty, or if it's a different source and more than one day has passed since the last visit
if (sf_source == null || sf_source === '' || isExpired(sf_source_timestamp) || sf_source != url_sf_source) {
sf_source = ''; // Reset sf_source if it's expired or not set, or if the source has changed after one day

// Check if the URL contains 'google'
if (currentPage.includes('google')) {
sf_source = 'google';
}
// Check if the URL contains 'fb'
else if (currentPage.includes('fb')) {
sf_source = 'facebook';
}
// Check if the URL contains 'Facebook'
else if (currentPage.includes('Facebook')) {
sf_source = 'facebook';
}
// Check if the URL contains 'sf_source'
else if (currentPage.includes('sf_source')) {
// Extract the value of sf_source from the URL
var sfSourceIndex = currentPage.indexOf('sf_source=');
if (sfSourceIndex !== -1) {
var sfSourceValue = currentPage.substring(sfSourceIndex + 10); // Length of 'sf_source=' is 10
// Find the end of sf_source value
var sfSourceEndIndex = sfSourceValue.indexOf('&');
if (sfSourceEndIndex !== -1) {
sf_source = sfSourceValue.substring(0, sfSourceEndIndex);
} else {
sf_source = sfSourceValue;
}
}
}
// Check if the 'utm_source' parameter is present and set the sf_source accordingly
else {
// Parse the URL to extract query parameters
var urlParams = new URLSearchParams(window.location.search);

// Check if the 'utm_source' parameter is present and set the sf_source accordingly
if (urlParams.has('utm_source')) {
var utmSourceValue = urlParams.get('utm_source');

// Check for 'google'
if (utmSourceValue.toLowerCase() === 'google') {
sf_source = 'google';
}
// Check for 'facebook'
else if (utmSourceValue.toLowerCase() === 'facebook') {
sf_source = 'facebook';
}
// Check for 'Facebook'
else if (utmSourceValue === 'Facebook') {
sf_source = 'facebook';
}
// Add additional conditions for other sources if needed
}
}
// Store the sf_source value in cookies along with the timestamp
setCookie('sf_source', sf_source, 2); // Cookie expiration time set to 2 days
setCookie('sf_source_timestamp', Date.now(), 2); // Cookie expiration time set to 2 days
}
}

// Function to set a cookie
function setCookie(name, value, days) {
var expires = '';
if (days) {
var date = new Date();
date.setTime(date.getTime() + (days * 24 * 60 * 60 * 1000));
expires = '; expires=' + date.toUTCString();
}
document.cookie = name + '=' + (value || '') + expires + '; path=/';
}

// Function to get a cookie value
function getCookie(name) {
var nameEQ = name + '=';
var cookies = document.cookie.split(';');
for (var i = 0; i < cookies.length; i++) {
var cookie = cookies[i];
while (cookie.charAt(0) === ' ') {
cookie = cookie.substring(1, cookie.length);
}
if (cookie.indexOf(nameEQ) === 0) {
return cookie.substring(nameEQ.length, cookie.length);
}
}
return null;
}

// Function to check if the stored value is expired
function isExpired(timestamp) {
if (!timestamp) return true; // If timestamp is not set, consider it expired
var currentTime = Date.now();
var storedTime = parseInt(timestamp);
var timeDifference = currentTime - storedTime;
var hoursDifference = timeDifference / (1000 * 60 * 60); // Convert milliseconds to hours
return hoursDifference >= 2160; // Check if 2160 hours (90 days) have passed
}
</script>

Should you require further details, please don't hesitate to ask, and we'll gladly provide additional information.

Thank you again.

Re: Assistance Needed - Issue with Google & Facebook Leads Tracking After API Shift

SKundu6 — Thu, 19 Dec 2024 07:18:39 GMT

Hi @GRajput,

Just following up on my previous post regarding the issue with tracking Google and Facebook leads after the recent API shift.

We haven't received any feedback yet and would really appreciate your insights or suggestions on how to resolve this.