Audience Specific Content Blocks, the many considerations when turning on paid, how we are thinking about our work right now, the pitfalls of app subscriptions, how to schedule notes.
I was finally able to watch this replay earlier today...lots of excellent food for thought here (on both the audience-specific content, which I've already dabbled in but plan to more, and also on finding the value that will make subscribers want to pay for your work).
Great meeting. Lots of useful info and food for thought. I really enjoyed it. Thank you.
I have a question about the new audience specific content block + paywall. I also really don’t like the fact that paywalling a post means free subscribers can’t comment. So if I decided to paywall my recipes (still not sure about that) would it make sense to use that audience specific content block, place the whole recipe in there, and check the box for paid subscribers (so only they see it)… or is it better to create a separate post that contains the recipe only, paywall that, then place a link in the “main” post, and keep that open to all? I hope I’m making sense.
I know there are benefits to placing the recipe in a separate post, and using the recipe card (which I really dislike by way, ahah, so I haven’t used it yet). But I was wondering what would be better when it comes to paywalling just the recipe: audience specific content block, or separate paywalled post?
I’m not sure there’s a wrong answer here… it mostly just depends on the bigger picture. I am doing both. I just started a new recipe series for paid subscribers called Road Food. I want this to grow into a large collection that can all be found in one place and I want it to be separate from my other recipes. So, I created a section for them and am paywalling every recipe in the series. You can see what I mean, here: https://www.rebeccablackwell.com/s/road-food
But, in my regular newsletters, I’m adding audience specific blocks to make every issue a little bit more customized to free and paid readers without using paywalls. I also hate that paywalling a post cuts off the comments. If I was going to put an entire recipe for paid subscribers in the middle of one of my regular newsletter issues, I think I would use an audience specific block to do so.
Thanks for your reply, Rebecca. And sorry for the delay. I couldn’t find the notification and post. This totally makes sense. Why not do both. I still haven’t figured out what to lock, if anything. I appreciated everyone’s input on that too (during the call). Thanks again
Finally got to listen to the replay! What a great meeting chock full of helpful info!
I was finally able to watch this replay earlier today...lots of excellent food for thought here (on both the audience-specific content, which I've already dabbled in but plan to more, and also on finding the value that will make subscribers want to pay for your work).
Great meeting. Lots of useful info and food for thought. I really enjoyed it. Thank you.
I have a question about the new audience specific content block + paywall. I also really don’t like the fact that paywalling a post means free subscribers can’t comment. So if I decided to paywall my recipes (still not sure about that) would it make sense to use that audience specific content block, place the whole recipe in there, and check the box for paid subscribers (so only they see it)… or is it better to create a separate post that contains the recipe only, paywall that, then place a link in the “main” post, and keep that open to all? I hope I’m making sense.
I know there are benefits to placing the recipe in a separate post, and using the recipe card (which I really dislike by way, ahah, so I haven’t used it yet). But I was wondering what would be better when it comes to paywalling just the recipe: audience specific content block, or separate paywalled post?
Thank you!!
I’m not sure there’s a wrong answer here… it mostly just depends on the bigger picture. I am doing both. I just started a new recipe series for paid subscribers called Road Food. I want this to grow into a large collection that can all be found in one place and I want it to be separate from my other recipes. So, I created a section for them and am paywalling every recipe in the series. You can see what I mean, here: https://www.rebeccablackwell.com/s/road-food
But, in my regular newsletters, I’m adding audience specific blocks to make every issue a little bit more customized to free and paid readers without using paywalls. I also hate that paywalling a post cuts off the comments. If I was going to put an entire recipe for paid subscribers in the middle of one of my regular newsletter issues, I think I would use an audience specific block to do so.
Thanks for your reply, Rebecca. And sorry for the delay. I couldn’t find the notification and post. This totally makes sense. Why not do both. I still haven’t figured out what to lock, if anything. I appreciated everyone’s input on that too (during the call). Thanks again
Couldn't make the meeting, so just watched the replay -- On Paywalling: SO MANY FEELINGS!!! let's talk about this live!
Yes, please!!!