Hi Sasha,

Unfortunately these were named incorrectly when this functionality was originally introduced to the platform.

Because these are publicly available fields, which our existing customers are currently referencing, we cannot just rename them (since this would break functionality for customers who currently use these fields).

Kind regards,

Jonathan,