Restrict Content Pro

#Overview

WP Fusion works with Restrict Content Pro to sync customers with your CRM of choice when they register or purchase a subscription.

You can sync data collected on your registration form to custom fields in your CRM, and apply tags based on membership level and subscription status.

You can also automatically add users to membership levels by applying “linked tags” in your CRM.

#Membership Tagging

You can apply tags in your CRM based on the RCP membership level purchased, and automatically grant membership levels to users by linking membership levels with a CRM tag.

Screenshot of a websites membership settings page seamlessly showcasing WP Fusion CRM integration. The Apply Tags section highlights Bronze Member, while the Remove Tags option ensures original tags are removed upon membership expiration. The Link with Tag section remains unassigned.

There are three options:

  • Apply Tags: When the customer purchases a membership, these tags will be applied in your CRM. This is the default behavior.
  • Remove Tags: When this box is checked, the tags applied at checkout will be removed when a membership expires.
  • Link with Tag: Most sites won’t require this, but it is available as an option for those that need it. This setting allows you to select a tag that becomes linked with the membership level. If this tag is applied to a user, for example via a webhook, they will be automatically enrolled in the membership. Likewise if this tag is removed, they will be removed from the membership. This lets you automate individual users’ membership levels using sequences in your CRM in conjunction with webhooks / HTTP Posts.

#Additional status tagging

WP Fusion also supports applying tags based on specific statuses of memberships. This is in addition to the more general Apply Tags setting, and can be used to trigger emails from your CRM based on changes in a member’s status.

Screenshot of a status tagging options list for memberships with WP Fusion CRM integration, featuring tags for Active, Cancelled, Expired, Free, Trial, and Renewal Payment Failed. Each status is clearly labeled with Membership or Payment for seamless tracking.

The status tags will generally not be removed, unless a member’s status changes back to Active. For example:

  • If a customer has a failed renewal payment, and then cancels their membership, they will be tagged with both Payment Failed and Membership Cancelled
  • If a customer has a failed renewal payment, but then has a successful payment and their status comes back to Active again, the Payment Failed tag will be removed, and they will only be tagged as Membership Active
  • If a customer cancels their membership but then resumes it again, the Membership Cancelled tag will be removed, and they will only be tagged as Membership Active

#Syncing meta fields

WP Fusion makes several meta fields related to Restrict Content Pro memberships available for syncing with your CRM.

Screenshot of a configuration panel titled Restrict Content Pro featuring options like expiration date, notes, and signup method. Integrate WP Fusion CRM to seamlessly manage subscription level ID, account status, and subscription level name, each with its own selection field and type.

You can find these fields and enable them for sync from the Contact Fields tab in the WP Fusion settings.

#Groups

Using the Restrict Content Pro Group Accounts add-on unlocks additional options for tagging your group members in your CRM.

A membership management interface displays Seats: 0/15 with an option to add members. In the Apply tags section, a tag reads Added to Group. The Link with tag section awaits entries. For seamless WP Fusion CRM integration, a blue Update Group button is positioned at the bottom.

When a member is added to a group, they will be automatically synced to a contact record in your CRM.

When editing a group, there are two options for tagging group members:

  • Apply Tags: When a user is enrolled in the group, these tags will be applied in your CRM. This is the default behavior.
  • Link with Tag: Most sites won’t require this, but it is available as an option for those that need it. This setting allows you to select a tag that becomes linked with the group enrollment. If this tag is applied to a user, for example via a webhook, they will be automatically enrolled in the group. Likewise if this tag is removed, they will be removed from the membership. This lets you automate individual users’ group enrollments using sequences in your CRM in conjunction with webhooks / HTTP Posts.

#Group meta fields

WP Fusion adds two additional fields for sync when the Groups Accounts addon is active, Group Leader Email and Group Name.

A screenshot of a settings page shows a table for Restrict Content Pro, now featuring WP Fusion CRM integration. Columns include fields like Membership Level ID, Account Status, and Expiration Date, with options to select field types such as text, date, and textarea.

These fields will be synced to your CRM when a user is added to a group:

  • Group Leader Email: This field will be set to the email address of the group leader.
  • Group Name: This field will be set to the name of the group.

#Exporting member data

WP Fusion includes an export utility that can export historical member data to your CRM (for example from before you installed WP Fusion).

Screenshot of a web page displaying batch operations options with seamless WP Fusion CRM integration. Features include resyncing contact IDs and tags, exporting users, pushing user meta, restricting Content Pro members—this option is currently selected—and managing Gravity Forms entries.

This can be found under the Batch Operations heading on the Advanced tab of the WP Fusion settings.

When you run the Restrict Content Pro members operation all members will be tagged based on the tag settings for their current membership level. Any custom fields related to their membership and membership status will also be synced to your CRM.

#Groups

If the Group Accounts addon is active, you will also see a Restrict Content Pro group memberships batch operation. Running this operation will apply the configured tags to every user based on their current group enrollments.

Was this helpful?