Question
Sponsor Tracking Broken
This is a PSA for the Community, and a cathartic complaint:
I learned in Gainsight support ticket 8742 that Sponsor Tracking is simply broken until the May product release. The system is creating records for changes that have been detected that are not real. For example, sponsor tracking says that an individual moved from Google to Apple, but that individual actually moved from Apple to Google 3 years ago, and is still at Google.
Apparently this affects all types of sponsor tracking: company, title, and location. I've turned off our rule that creates CTAs based on this data, deleted all existing sponsor tracking CTAs, and had to notify all our CSMs and my VP.
Sponsor Tracking was one of the great and sexy features of the product when we signed on, but it's been nothing but a disappointment, not just because of this, but also because of the issue described in https://community.gainsight.com/gainsight/topics/make-sponsor-tracking-more-reliable It's regretful that bugs that fundamentally affect the basic uses of a feature cannot be prioritized outside of scheduled product releases.
I learned in Gainsight support ticket 8742 that Sponsor Tracking is simply broken until the May product release. The system is creating records for changes that have been detected that are not real. For example, sponsor tracking says that an individual moved from Google to Apple, but that individual actually moved from Apple to Google 3 years ago, and is still at Google.
Apparently this affects all types of sponsor tracking: company, title, and location. I've turned off our rule that creates CTAs based on this data, deleted all existing sponsor tracking CTAs, and had to notify all our CSMs and my VP.
Sponsor Tracking was one of the great and sexy features of the product when we signed on, but it's been nothing but a disappointment, not just because of this, but also because of the issue described in https://community.gainsight.com/gainsight/topics/make-sponsor-tracking-more-reliable It's regretful that bugs that fundamentally affect the basic uses of a feature cannot be prioritized outside of scheduled product releases.