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 https://cdn.discordapp.com/attachments/1090592836044476426/1522614763321036850/image.png?ex=6a491d00&is=6a47cb80&hm=3371b6e1cf116904406e211defeeecbdd56026025ec0a4fd3183e4dbdcdc94f4&

We take new add-on differently since it should not require the 14 days grace period. But the wording should be improved, agree, will share with the team

Thanks Lukas, one clarification then: is the 14-day grace period actually required in my case? I've hidden the add-on for now to wait it out, but if a new opt-in add-on can be charged right away, I'd rather not hide it and just make it live now. My change currently shows "effective July 17", so I want to know if that date is real or if I can enable it immediately. It's an optional event, off by default, existing pricing unchanged.

I see it says "effective July 17", which means he 14 day period did apply, I will ping the team

thanks!

Ok, team let me know that the add-on optimization will come in near future

@Lukas Krivka or @User hey ! any updates about it? I want to offer a new addon on an actor, but don't want that my users receive a wrong notification again..

@Chico Carrizo just advanced to level 1! Thanks for your contributions! 🎉

It should work fine now

@Lukas Krivka So what should I do then? Going to Monetization and creating the new event for the addon would be enough? In other words, as soon as I set the event, will I be able to enable the addon for users to use, without having to wait the 14 days?

Hey @Chico Carrizo I can see why this is frustrating for you - my hunch is this is an edge-case due to the previous change, but DM me your Actor info and I can take a closer look.

@Ella Thanks Ella! sent you now

Got it, thanks

hey @Ella and @Lukas Krivka , I keep having the same issue when trying to add new addons to my actors. Even though I'm just adding new events, not changing any existing prices, the process still asks me to write a "Reasoning" where I have to explain why the price is changing, but there's no changing on prices, it's just new addons. Also on the last "Review" step it shows a preview of the notification that'll be send to my users, and it's still wrong, it should tell them I'm adding something new, not tell "New price changing".. Adding new addons as you said above, should not count the 14 days grace period right? I think those 2 things should be different workflows: 1. Changing actual event prices: the workflow as is today. 2. Adding new addons: should ask what message we want to show for our users, to let them now about those new events, what's possible to do with them. It should notify the users about those new events, in an exciting way, because we're adding something new. Last time Ella did it for me manually, but it should work for us without having to ask for it.. could you guys check that? https://cdn.discordapp.com/attachments/1522614763761176637/1551692398004928663/image.png?ex=6ab2e5a8&is=6ab19428&hm=0a0935cd9fe5eae15482d456fa524a3344f39f7214e51dd53859181ff1444e20& https://cdn.discordapp.com/attachments/1522614763761176637/1551692399669944390/image.png?ex=6ab2e5a9&is=6ab19429&hm=cdbd74ba5468c5b75b2a04c0df23dad2229734331bc5f0066a244350960d3fad&

This is a bug that Lukas already reported so we are waiting for it to be fixed - DMing you!

thanksss