Q: What feature / functionality are you looking for?
A: I don’t want Unbounce to create the “Submitter IP” or “Source” Lead custom fields.
Q: What problem are you trying to solve?
A: I already have enough custom fields and each of the fields I create adhere to a certain naming convention. These are dupes of things I already have and each time I delete them they come back into my org. I’ve tested this and it appears to be due to the Unbounce integration.
Q: If solved, what value would this provide (ex. increased efficiency, cost savings, etc.)?
A: This would help to keep my org clean of fields I don’t want or need.
Q: Use Case example? (ex. As a ____ I want to be able to _____ so I can _____.)
A: I want to have only fields that I use and that I’ve created for a given purpose. These fields serve no purpose.
Q: Is this being solved by another workaround or any other tool today?
A: This is specifically caused by the Unbounce integration, so “No”.