Blair Williams

cartpauj

Chris Lema

<h4>WP Revenue Booster</h4>
<p>Imagine walking into any store and talking to a salesperson who forgets everything they know about you, just seconds after they ask you about it.</p>
<p>That’s your website right now!</p>
<p>But it doesn’t have to be for much longer thanks to WP Revenue Booster!</p>
<p>Depending on where your customer is coming from, or what they’ve done on your site, now you can personalize their experience. Improve your site’s conversions by simply making small tweaks in the way you write your offers and products – based on who is visiting. Amazon ran more than 300 tests on their thank you page to determine the best way to encourage post-purchase activity. Now you can too!</p>
<h4>Process</h4>
<ol>
<li>Review where your traffic comes from so that you can determine what kind of segments to create.</li>
<li>Click on the screen and change the text – connecting it to the segment you’ve defined.</li>
<li>You can easily compare how each personalization change is impacting your revenue.</li>
<li>Iterate until you’re happy with how much more money your site is making you.</li>
</ol>
<h4>Features</h4>
<ul>
<li>Context-Based Content</li>
<li>Pre-Purchase Incentives (coming soon)</li>
<li>Post-Purchase Suggestions (coming soon)</li>
<li>Define Your Segments</li>
<li>Customize Your Text</li>
<li>Evaluate Your Conversions (coming soon)</li>
</ul>
<h4>Help</h4>
<p>If you need help with this plugin please visit our website:</p>
<p><a href="https://wprevenuebooster.com/help/" title="Get Help" rel="nofollow ugc">Get Help</a></p>
<h4>Getting Started</h4>
<p><strong>Step 1: Set up your Segments</strong></p>
<p>Segments are the mechanism that WP Revenue Booster uses to determine who will be shown what text.</p>
<p>Some segment examples could include “Returning Visitors,” “Visitors from Canada,” “Logged In Users,” “Mobile Users,” etc.</p>
<p>You can create, edit and destroy segments by visiting “Revenue Booster” -> “Segments” in your WordPress admin after the plugin is installed.</p>
<p><strong>Step 2: Customize Text on your Site</strong></p>
<p>WP Revenue Booster makes it easy for you to add text customizations based on Segment.</p>
<p>Here’s how you can customize text on your website as a logged-in user:</p>
<ol>
<li>Visit any page on your site</li>
<li>Click the “Add Dynamic Text” button on the WordPress toolbar to enter the customizer</li>
<li>Hover over the text you’d like to customize by segment and click it</li>
<li>Add the text you’d like to appear to any segments you’ve previously set up</li>
</ol>
<p>That’s it!</p>
<p><strong>Step 3: Test your Customizations</strong></p>
<p>The easiest way to test your text customizations is by visiting your site as a user in the segment.</p>
<p>For instance if your customization should appear for mobile users try visiting the page from your phone or if you’re targeting users from a different country, use a VPN server in that country to check that your customizations appear.</p>
<p>More sophisticated tools exist to simulate requests that would work for your targeted requests … so that would be a more advanced way to test your customizations.</p>


WP Revenue Booster

Dynamically personalize any text on your site based on your users' behavior.

Jose Mortellaro

<p>Normally, if a web page is served by the <a href="https://wordpress.org/plugins/search/cache/" rel="ugc">cache</a>, its content will be always the same until the cache is deleted.</p>
<p>By adding the content with the shortcode provided by Content No Cache, you will be able to show dynamic content even on pages served by cache.</p>
<p>You don’t need this plugin to exclude the entire page from the <a href="https://wordpress.org/plugins/search/cache/" rel="ugc">cache</a>.<br />
This plugin is to exclude a part of the page from the <a href="https://wordpress.org/plugins/search/cache/" rel="ugc">cache</a>. It’s useful if you need to cache a page, but part of that page should not be cached.</p>
<p>Imagine you have a page that has this content:</p>
<p>Hello this is some text.<br />
Another line of text<br />
Another line of text<br />
Current day: Monday</p>
<p>if that page is served by cache, the user will always see:</p>
<p>Hello this is some text.<br />
Another line of text<br />
Another line of text<br />
Current day: Monday</p>
<p>If you need that the last line of text is always updated, this plugin will help you.<br />
The entire page will be served by the cache, but the plugin will get the updated content that you need.</p>
<h3>How to show dynamic content with full page cache</h3>
<ul>
<li>Install Content No Cache</li>
<li>Create a new element “Content No Cache”</li>
<li>Add to that element all the content that you want to exclude from the cache</li>
<li>Copy the shortcode that you will see in the section “Shortcode”. It will look like [content_no_cache id=”3328″]. The parameter “id” is the ID of the content element (in this example 3328).</li>
<li>Add the shortcode to the page where you want to display that content.</li>
</ul>
<h3>Compatible <a href="https://wordpress.org/plugins/search/cache/" rel="ugc">caching plugins</a> tested with Content No Cache</h3>
<ul>
<li><a href="https://wordpress.org/plugins/w3-total-cache/" rel="ugc">W3 Total Cache</a></li>
<li><a href="https://wordpress.org/plugins/wp-fastest-cache/" rel="ugc">WP Fastest Cache</a></li>
<li><a href="https://wordpress.org/plugins/wp-optimize/" rel="ugc">WP Optimize</a></li>
<li><a href="https://wordpress.org/plugins/comet-cache/" rel="ugc">Comet Cache</a></li>
<li><a href="https://wordpress.org/plugins/cache-enabler/" rel="ugc">Cache Enabler</a></li>
<li><a href="https://wordpress.org/plugins/hyper-cache/" rel="ugc">Hyper Cache</a></li>
<li><a href="https://wordpress.org/plugins/wp-super-cache/" rel="ugc">WP Super Cache</a></li>
<li><a href="https://wordpress.org/plugins/litespeed-cache/" rel="ugc">LiteSpeed Cache</a></li>
<li><a href="https://wordpress.org/plugins/sg-cachepress/" rel="ugc">Speed Optmizer</a></li>
<li><a href="https://wp-rocket.me/" rel="nofollow ugc">WPRocket</a></li>
</ul>
<p>All of those caching plugins are compatible with Content No Cache. If your favorite caching plugin is not compatible for any reason, let us know it</p>
<h3>Compatible CDNs</h3>
<ul>
<li><a href="https://www.cloudflare.com/" rel="nofollow ugc">Cloudflare</a></li>
<li><a href="https://bunny.net/cdn/" rel="nofollow ugc">BunnyCDN</a></li>
<li><a href="https://www.stackpath.com/" rel="nofollow ugc">StackPath</a></li>
<li><a href="https://www.keycdn.com/" rel="nofollow ugc">KeyCDN</a></li>
<li><a href="https://www.fastly.com/" rel="nofollow ugc">Fastly</a></li>
<li><a href="https://aws.amazon.com/cloudfront/" rel="nofollow ugc">CloudFront</a></li>
</ul>
<h3>Main features</h3>
<ul>
<li>Ultralightweight plugin. The few lines of code will run only where you add the shortcode.</li>
<li>No jQuery, no JS libraries, only a couple of lines of pure JavaScript</li>
<li>No database queries, no extra HTTP requests for external assets, no bloat</li>
<li>With a few line of ultralight code you can fully cache the page even if you need dynamic content on that page</li>
<li>It provides a shortcode, so you can add it everywhere, no matter the builder</li>
</ul>
<h3>Tips to speed up the process to get the content</h3>
<ul>
<li>Install <a href="https://wordpress.org/plugins/freesoul-deactivate-plugins/" rel="ugc">Freesoul Deactivate Plugins</a></li>
<li>Go to Freesoul Deactivate Plugins => Actions => Content No Cache</li>
<li>Disable all the plugins that you don’t need to output the content</li>
</ul>
<h3>Example</h3>
<p>You can see Content No Cache in action visiting the blog post <a href="https://josemortellaro.com/exclude-specific-content-from-being-cached/" rel="nofollow ugc">Exclude specific content from being cached</a>.<br />
You will see a number that is always different when you refresh the page. But the page is served by full page cache.<br />
In the example it’s just a number, but you can output whatever content you want.</p>
<h3>Possible conflicts</h3>
<p>Some plugins don’t load the shortcodes during ajax requests. Because Content No Cache retrieves the content through ajax, in those cases the content will not be displayed properly.<br />
If you have this kind of issue set the parameter request=”remote”. In this case the shortcode will look like [content_no_cache id=”3328″ request=”remote”]<br />
The plugin will retrieve the content in a different way that will be a little slower, but this will solve this kind of conflict.</p>
<h3>Help</h3>
<p>If something doesn’t work for you, don’t hesitate to open a thread on the <a href="https://wordpress.org/support/plugin/content-no-cache/" rel="ugc">Support Forum</a><br />
Please, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read <a href="https://freesoul-deactivate-plugins.com/how-to-enable-debugging-in-wordpress-a-step-by-step-guide/" rel="nofollow ugc">this detailed tutorial</a> on <a href="https://freesoul-deactivate-plugins.com/how-to-enable-debugging-in-wordpress-a-step-by-step-guide/" rel="nofollow ugc">how to enable debugging in WordPress</a> to learn more.</p>


Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.

I'm the author, but also a user of this plugin. I solved some serious problems with this plugin, so I will give it a 5 stars review.

By the author

Nice, simple, working as expected, what else can anyone can say?

I just wish there would be a better (and easier way) to trigger the no cache policy, like having a custom CSS class imposing the no cache for a block or div for those who use the Classic editor. Actually even better would be if each block (core or third party) having no cache checkbox on the sidebar.

Nevertheless, for me, for my specific needs, this gets the job done, and some !

Does one thing and it does it really well.


I use this to display "Latest post X hour ago"



It's being cached and sometimes inaccurate. This plugins fix it.



Good job Jose


Works like a charm

Serve uncached partial content even when you add it to a page that is fully cached.

WP Revenue Booster vs Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.