Lliving-lavender
Hey team 👋 I just added a new optional
Hey team 
I just added a new optional charge event to my LinkedIn Profile Scraper actor. It's opt-in and off by default. Existing users pay nothing extra unless they turn it on. I'm adding something new, not changing what anyone already pays.
The problem is Apify treats this as a "major pricing change." So every existing user gets a notification that says "the pricing for [actor] will change", with an Old pricing vs New pricing comparison. I rewrote the reason message to say it's optional, but the headline and the Old/New framing still read like a price increase.
That feels wrong for an add-on. A positive thing (new optional feature) ends up looking negative (your price is going up). If someone skims and doesn't read the whole message, they get the wrong impression. That can scare users or cause churn over a change that doesn't affect them at all.
My ask: please separate "adding a new optional event" from "raising existing prices". For additive-only changes, a headline like "New optional add-on available" would be accurate, instead of "pricing will change". Or let the publisher edit the headline, not just the reason text.
Not a blocker, I already went ahead. Just think this hurts publishers and confuses users in this case. Thanks
I just added a new optional charge event to my LinkedIn Profile Scraper actor. It's opt-in and off by default. Existing users pay nothing extra unless they turn it on. I'm adding something new, not changing what anyone already pays.The problem is Apify treats this as a "major pricing change." So every existing user gets a notification that says "the pricing for [actor] will change", with an Old pricing vs New pricing comparison. I rewrote the reason message to say it's optional, but the headline and the Old/New framing still read like a price increase.
That feels wrong for an add-on. A positive thing (new optional feature) ends up looking negative (your price is going up). If someone skims and doesn't read the whole message, they get the wrong impression. That can scare users or cause churn over a change that doesn't affect them at all.
My ask: please separate "adding a new optional event" from "raising existing prices". For additive-only changes, a headline like "New optional add-on available" would be accurate, instead of "pricing will change". Or let the publisher edit the headline, not just the reason text.
Not a blocker, I already went ahead. Just think this hurts publishers and confuses users in this case. Thanks
