How To Protect Member Content With Tags

Last Updated:

What Are Tags?

In this context, “tags” are Automation Tags (versus Taxonomy Tags), so they are used with your CRM such as FluentCRM to keep track of “yes/no” questions about the status of your user’s journey.

For example:

  • Purchased Product XYZ = “Has the person purchased this product (yes/no)?”
  • Viewed Page 123 = “Has the person viewed this page or post (yes/no)?”
  • Subscribed To Membership ABC = “Has the person subscribed to this membership (yes/no)?”
  • Can Access Content = “Can the person view this protected content (yes/no)?”

We can keep track of every person we add to a CRM as a “contact” and then synchronize their contact profile to their WordPress “user” profile with the WPFusion plugin. Even better, when using FluentCRM instead of an external CRM, this is all automatic.

In sum, we use tags to track the journey of the user, display or hide different content, and then have these tags available to use to use both in the CRM (for email or automations) or in the WordPress site (for conditional display or changing the user’s experience).

Three Ways To Protect Member Content

Since we have tags (as well as custom field data) available to us inside of the WordPress site, we can use the existence of tags as a condition for displaying or hiding content to any user. These are:

  • The Full Page, Post, Navigation or Search Result – This means we can protect the visibility of any such item by using the WPFusion meta box that asks for any or all tags you choose as the condition for displaying item.
  • A Wrapper Block inside of any page or post content – This can be the WPFusion block or if you are using FluentCRM the “Conditional Section” block. These act as containers to hold other blocks, but enable you to program the existence of one or more tags to show what is inside of the wrapper.
  • An individual Block – You can also conditionally display any individual Gutenberg block inside of the WordPress editor by way of the Visibility or Conditional Block meta boxes. This can be by way of Automation Tags, or in combination with other conditions such as the existence of certain products in the Checkout or previous purchases, IP, time of day, etc.

Watch this video for detailed examples of all three: