macbookandrew

Okamoto Hidetaka

shulard

Friendly

Brady Cargle

dbhurley

escopecz

mautic

<p>The <a href="https://friendly.ch/automate" rel="nofollow ugc">Friendly Automate</a> WordPress Plugin injects the Friendly Automate tracking script and images into your WordPress website. Your Friendly Automate instance will be able to track information about your visitors like what pages they visit and what content they’re interested in. You can also insert Friendly Automate’s dynamic content inside your website using different shortcodes, as well as integrate with Elementor.</p>
<h3>Key features</h3>
<ul>
<li>Easy setup on WordPress. You don’t have to edit your source code, go through complex tutorials, or hire an expensive expert. </li>
<li>Get detailed analytics. You can see the content that users are engaging with and interested in.</li>
<li>Simple content embedding. Add your forms or dynamic content to your WordPress site with a single shortcode.</li>
</ul>
<h3>Configuration</h3>
<p>Once installed, the plugin will appear in your plugin list:</p>
<ol>
<li>Enable it.</li>
<li>Go to the Settings -> Friendly Automate and set your Friendly Automate URL.</li>
</ol>
<p>You can also customize where you want to insert the tracking script location on your website. Feel free to leave this as the default option.</p>
<h3>Usage</h3>
<h3>Friendly Automate Forms</h3>
<p>To load a Friendly Automate Form to your WordPress page or post, insert this shortcode to the place you want the form to appear:</p>
<pre><code>[friendlyautomate type="form" id="1"]
</code></pre>
<p>Replace “1” with the form ID you want to load. To get the ID of the form, go to your Friendly Automate account, open the form detail and look at the URL. The ID is right there. For example in this URL: http://yourfriendlysite.com/s/forms/view/3 the ID is 3.</p>
<h3>Friendly Automate Dynamic Content</h3>
<p>To load dynamic content into your WordPress content, insert this shortcode where you’d like it to appear:</p>
<pre><code>[friendlyautomate type="content" slot="slot_name"]Default content to display in case of error or unknown contact.[/friendlyautomate]
</code></pre>
<p>Replace the “slot_name” with the slot name you’d like to load. This corresponds to the slot name you defined when building your campaign and adding the “Request Dynamic Content” contact decision.</p>
<h3>Elementor Integration</h3>
<p>Using Elementor Forms to collect your leads? Check out our video guide on how to <a href="https://docs.friendly.ch/automate-elementor-en" rel="nofollow ugc">integrate Friendly Automate with Elementor</a></p>
<h3>Friendly Automate Tracking Script</h3>
<p>Tracking script works right after you finish the configuration steps. That means it will insert the <code>mtc.js</code> script from your Friendly Automate instance. You can check HTML source code (CTRL + U) of your WordPress website to make sure the plugin works. You should be able to find something like this:</p>
<pre><code>html
<script>
    (function(w,d,t,u,n,a,m){w['MauticTrackingObject']=n;
        w[n]=w[n]||function(){(w[n].q=w[n].q||[]).push(arguments)},a=d.createElement(t),
        m=d.getElementsByTagName(t)[0];a.async=1;a.src=u;m.parentNode.insertBefore(a,m)
    })(window,document,'script','http://yourfriendlysite.com/mtc.js','mt');

    friendlyautomate_send();
</script>
</code></pre>


Friendly Automate

The Friendly Automate WordPress Plugin injects the Friendly Automate tracking script and images into your WordPress website.

DAEXT

<p>Restricted Blocks is a WordPress plugin that allows you to restrict access to specific Gutenberg blocks based on a great variety of conditions.</p>
<p>You can, for example, restrict content based on the user role, conditionally display content based on the user device, make parts of the post unavailable to search engines, and more.</p>
<h3>Pro Version</h3>
<p>For professional users, we distribute a <a href="https://daext.com/restricted-blocks/" rel="nofollow ugc">Pro Version</a> of this plugin which includes additional types of restrictions.</p>
<h3>Types of restrictions</h3>
<p>This section will provide you details on the types of restrictions and the related usage examples.</p>
<h3>Fixed</h3>
<p>This restriction, when activated, removes a block from the front end.</p>
<h4>Usage Examples</h4>
<ul>
<li>Temporarily hide existing or new sections of an article until they are ready to be published.</li>
</ul>
<h3>Password</h3>
<p>The restricted content is displayed only after a successful password submission.</p>
<h4>Usage Examples</h4>
<ul>
<li>Display private content only to members of a club, community, or to your friends.</li>
<li>Display downloadable material only to students of a class.</li>
</ul>
<h3>Device</h3>
<p>This restriction allows you to display blocks based on the device of the user.</p>
<h4>Usage Examples</h4>
<ul>
<li>Display complex layout elements only with desktop devices</li>
<li>Display different download links based on the device of the user</li>
</ul>
<h3>Time Range</h3>
<p>With this restriction, you can display content at a specified time interval.</p>
<h4>Usage Examples</h4>
<ul>
<li>Sell tickets in predetermined time intervals</li>
<li>Create a flash sale</li>
</ul>
<h3>Capability</h3>
<p>This restriction uses the <a href="https://wordpress.org/support/article/roles-and-capabilities/" rel="ugc">capabilities of the user</a> to determine whether to display or not a specific block.</p>
<h4>Usage Examples</h4>
<ul>
<li>Allow access to premium material only to specific user roles.</li>
</ul>
<h3>IP Address</h3>
<p>This restriction allows you to display or hide blocks based on the IP address of the visitor.</p>
<h4>Usage Examples</h4>
<ul>
<li>Prevent spam on contact forms or comments area</li>
<li>Prevent hacking attempts</li>
</ul>
<h3>Cookie</h3>
<p>Use this restriction to display content based on the presence of specifics cookies.</p>
<h4>Usage Examples</h4>
<ul>
<li>Hide or display interface elements based on the information available about the user</li>
<li>Display content only to logged user</li>
</ul>
<h3>HTTP Headers</h3>
<p>With this restriction, you can display or hide content based on the information available in the HTTP headers.</p>
<h4>Usage Examples</h4>
<ul>
<li>Hide content to specific bot or search engines</li>
<li>Conditionally display content based on the device of the user</li>
</ul>
<h3>Customizable Style</h3>
<p>You can customize the colors and the typography of the elements displayed in the front-end with the 18 style options available in the back-end.</p>
<h3>Technical Information</h3>
<h3>Plugin manual</h3>
<p>Please see the <a href="https://daext.com/doc/restricted-blocks-lite/" rel="nofollow ugc">plugin manual</a> for more information on the plugin installation and usage.</p>
<h3>Device detection</h3>
<p>The device of the user is detected with the <a href="https://github.com/serbanghita/Mobile-Detect" rel="nofollow ugc">Mobile Detect</a> PHP class.</p>
<h3>Credits</h3>
<p>This plugin makes use of the following resources:</p>
<ul>
<li><a href="https://github.com/select2/select2" rel="nofollow ugc">Select2</a> licensed under the <a href="http://www.opensource.org/licenses/mit-license.php" rel="nofollow ugc">MIT License</a></li>
<li><a href="https://github.com/serbanghita/Mobile-Detect" rel="nofollow ugc">Mobile Detect</a> licensed under the <a href="http://www.opensource.org/licenses/mit-license.php" rel="nofollow ugc">MIT License</a></li>
</ul>


Restricted Blocks – Conditional Visibility Settings for the Block Editor

The feature I like best is the ability to set passwords for each block.

I am very thankful to the developers for the great job they have done in making this functionality available to me!

What a great plugin!

Restricted Blocks is a WordPress plugin that allows you to restrict access to specific Gutenberg blocks based on a great variety of conditions.

Friendly Automate vs Restricted Blocks – Conditional Visibility Settings for the Block Editor