Gainsight NXT Patch Release Notes: Version 6.42.X series

Email Bot Click Detection and Mitigation Fix in Program Analytics

A recent fix has been implemented in Gainsight to address issues related to email bot activity, particularly concerning false click events recorded by bots. This fix has been implemented globally for all Gainsight CS customers in the patch release scheduled for August 24, 2024.

Fix Details

• Emails sent from Gainsight are now prepended with invisible links (hidden within the email). These links are designed specifically to detect bot activity.
• When a bot clicks on one of these invisible links, the activity is logged and the bot's IP address is identified.
• The identified bot IP addresses are now persisted in Gainsight's system. Future email events originating from these IP addresses are automatically ignored, ensuring that bot clicks do not skew engagement metrics or trigger unintended actions.

This fix enhances the accuracy of email engagement tracking by filtering out false clicks generated by automated bots, allowing for more reliable reporting and decision-making.
IMPORTANT: After this release, you may notice a decrease in the Email Click Analytics stats. This fix also applies to emails sent outside of Journey Orchestrator Programs, such as those sent from Cockpit, People 360, AI Intel in C360, and so on.

Re-Authorization and Re-creation of Jobs Required for Specific Connectors

Gainsight is upgrading connectors to enhance performance and bringing in critical upgrades. As a result, following connectors need to be re-authorized or jobs need to be recreated to avoid data sync failures and job disruptions.

• Recreate jobs on V2 Connector:
  • Zuora
  • Intercom
  • Pipedrive
  • Zoho
• Re-authorize Connection:
  • JIRA
  • ServiceNow
  • Freshdesk (“Edit Connection” and “Save”) 
  • Google Big Query
  • Zendesk

For more details on action required, refer to the Gainsight CS Release Notes July 2024.

With the above upgrades some of the fields are getting deprecated and new fields are getting added.

For any fields that are critical for your usecases, Gainsight recommends to reach out to Gainsight Support.

For more information on the parity gaps, refer to the Key Differences Between V1 and V2 Connectors article.

Upcoming HubSpot API Changes: Impact on Your Connector Jobs

On August 31st, 2024, HubSpot will upgrade its Owner API to version 3, and support for the current version will be discontinued. To ensure that your connector jobs continue to operate smoothly, Gainsight is implementing necessary changes automatically—no action is required from you.

Key Changes: As part of the API upgrade, four fields within the Owner object will be removed: 

• hasContactsAccess
• portalId
• Type
• isActive

What to Expect Starting August 31st:

• Field Unmapping: Any jobs currently using the hasContactsAccess, portalId, or type fields will have these fields automatically unmapped. Data from these fields will no longer be received in HubSpot jobs.
• User Sync Job Update: In the User Sync standard job, where the isActive field is currently mapped, this field will be unmapped.