How tag-based content protection works

iMEMBER360 lets you define membership levels from Keap tags and use those levels to protect WordPress content. A logged-in member is matched to the Keap contact record tied to their WordPress user account, and access is evaluated against the tags and rules you configure.

This allows a Keap campaign to grant, change, or remove access by applying or removing tags. WordPress does not need to become a separate source of truth for membership status.

What you can protect

  • WordPress pages and posts.
  • Supported custom post types.
  • Menu visibility and member navigation paths.
  • Shortcode-wrapped sections inside otherwise public pages.
  • Feeds and excerpts where configured.
  • Downloads through signed Amazon S3 links where short-lived URLs are appropriate.

Common Keap tag access patterns

Most teams use a small set of practical tag patterns rather than creating hundreds of one-off rules. Examples include membership tier tags, product purchase tags, payment-failure tags, course access tags, cohort tags, partner tags, and lifecycle-stage tags.

For more precise access, iMEMBER360 can also use contact IDs, excluded tags, login state, saved conditionals, and supported integration rules. That gives you more control than a simple "logged in or logged out" membership gate.

Why this helps SEO and conversion

Not every protected page has to be invisible. You can use excerpts, teasers, public landing pages, and member-aware calls to action so search visitors understand the value before logging in or buying. Then iMEMBER360 protects the full content for the right Keap-tagged members.

Related setup pages