After talking with CRM Perks support and Hubspot support I think I eventually landed on the solution.
Hubspot had suggested that I disconnect and reconnect the CRM Perks plugin which I was reluctant to do because I didn’t want to lose all the settings. But, since neither of the support teams were able to figure it out, (and I’m on free versions for both, so I hardly feel justified in putting a ton of pressure on either HS or CRM Perks) I decided to disconnect/reconnect and see what happens. Some unexpected occurrences happened.
For starters, it reset all of my pipeline headers…
At first, that was really confusing/annoying but it made me realize that the limitations of free versions for both CRM Perks and Hubspot might be what led to this accidental glitch.
With the free version of Hubspot, you have two pre-made/existing pipelines. A sales pipeline and an e-commerce pipeline.
I renamed all the headers in the e-commerce pipeline thinking it would allow me to change the backend “internal naming” and associations as well. If you have the free version you can’t do that, and you can’t create your own custom pipeline. You have to use a pre-existing one.
I think because I linked the free version of CRM Perks to the e-commerce pipeline on a free version of Hubspot is what caused this glitch.
What I did was go in and change headers for the Sales Pipeline and route CRM Perks to that instead of the originally linked “e-commerce pipeline” and since then I have not had any issues.
All of this is POC for my company right now so I need to show a working model before I can justify proposing we pay for either system. Luckily it seems I have landed on the fix/solution, at least for now.
@warrendavey thank you for jumping in and sorry it took me so long to respond. I appreciate your willingness to help 