Author 詩語

Syncing Contact Fields

#Overview
In addition to applying tags in your CRM, a core feature of WP Fusion is the ability to sync data bidirectionally between WordPress user records and CRM contact records.
This is managed from the Contact Fields tab in the WP Fusion settings.

In the left column are all the fields that WP Fusion has detected in WordPress. To help finding fields easier these are grouped into collapsable sections based on the plugin that registered the field.
In the right column are dropdowns where you can select a corresponding custom field in your CRM.
Note: If you』ve just added a new custom field in your CRM, it may not appear in the dropdown of available fields. Begin typing the name of the new field, and if no matches are found, click the 「Resynchronize」 link that appears in the dropdown. The new custom field will be loaded from the CRM and you should see it appear once you re-type the name.
#Which fields are available
The fields that are available for sync depend on the plugins you have installed. Each of WP Fusion』s plugin integrations has the ability to detect the fields for that plugin.
The fields WP Fusion can sync with your CRM relate to a specific user on your site, not a custom post type or other related content.
Generally these would be standard fields (like Billing Address with WooCommerce), as well as custom fields (for example custom fields you』ve added to a registration form using Ultimate Member).
In addition to that, WP Fusion will scan the database (the wp_usermeta table) for your own admin user to try and find any other fields that might not have been detected, or might come from a plugin we don』t officially support. These will be listed at the bottom of the Contact Fields list in the Additional Fields section.
#Pseudo-fields
With some plugins, WP Fusion has been designed to sync some pseudo fields with your CRM. These are fields that don』t exist in any one place in your database, but WP Fusion can calculate them and sync them as part of a specific process, for example a checkout or membership level status change.
Some examples:

WooCommerce order data
LearnDash course progress
MemberPress current membership details

If the data you』re trying to sync with your CRM isn』t related to a specific user, or is coming from a plugin not currently supported by WP Fusion, you can also extend WP Fusion to detect and sync additional fields. For more info on that, see this tutorial.
#Additional Fields
At the bottom of the Contact Fields list is a section called Additional Fields.
This contains any meta fields that were found in your database but aren』t associated with a particular plugin integration.
Note: To build the list of Additional Fields, for performance reasons WP Fusion only scans the usermeta of your own admin user. If you』ve just added a new field and it』s not showing, try saving some data in that field for your own admin user.
For the most part you can leave this section alone, but if you』re trying to sync data to your CRM from a plugin that WP Fusion doesn』t have an official integration with, you may find the field keys here.

If you』re not using the Additional Fields you can hide them completely by checking the box for Hide Additional Fields on the Advanced settings tab.
If you』re a developer and are creating custom registration or profile forms, you can also type in new field keys into the Add new field line. The field you enter here should match the input name on your form. When the form is submitted, if WP Fusion detects an input with the matching name, then the value will be synced to the corresponding field in your CRM.
By default any enabled Additional Fields will only be synced if those fields are found on a submitted profile form.
If you find the fields aren』t syncing, you can enable Push All from the General settings tab. This causes WP Fusion to run on the added_user_meta and updated_user_meta hooks, and will also sync the field values any time those keys are updated in the wp_usermeta table.
#How data is synced
WP Fusion can either 「push」 data from WordPress to your CRM, or 「pull」 data from your CRM to WordPress.
A 「push」 happens when someone registers a user account, updates their profile, or a batch operation is run. Any available WordPress fields from the left column are synced to their corresponding CRM custom fields from the right column.
A 「pull」 can happen in a few scenarios:

When a webhook is received
When someone logs in and Login Meta Sync is enabled
When a page is loaded that has the [wpf_update_meta] shortcode on it

When that happens any fields that are enabled in the right column on the Contact Fields list are loaded via an API call and saved to their corresponding WordPress fields in the database.
Note: By default WP Fusion will not send an empty field to your CRM, or load an empty field from your CRM into WordPress. This is to avoid overwriting any valid data with a blank value. This can be overridden by setting the field type to raw in the dropdown.
#Field types
For each field there is a Type dropdown where you can tell WP Fusion how to treat the data in that field. These are detected automatically for most plugin integrations and don』t usually need to be changed, but if needed you can click on the type and select a new type from a dropdown to override the defaults.

Generally text type fields are the most compatible. What the other types do depend on your connected CRM. For example:

If a field type is set to checkbox then the value will be converted to a boolean 「true」 or 「false」 when the API call is sent to supported CRMs.
If a field type is set to multiselect then array-formatted data sent to ActiveCampaign will be separated with pipes || to properly update ActiveCampaign list box and checkbox fields.
If a field type is set to country then a country abbreviation will be sent to your CRM, which is compatible with the Country dropdowns in Infusionsoft, Mautic, and others. If it』s set to text the full country name will be sent instead.
If a field type is set to date then a date sent to HubSpot will be converted to a Unix timestamp to properly update a HubSpot datepicker field.
If a field type is set to raw then WP Fusion will not perform any additional checks or formatting on the field data. Fields set to raw will also be synced to your CRM even if they are empty, which has a potential for data loss.

#Dynamic Tagging
With some platforms, WP Fusion can dynamically convert a user meta value into tags in the CRM. To set this up, select Create tag(s) from value from any Select a field dropdown.
When WP Fusion goes to sync the metadata to your CRM, it will convert the value into a tag. If the value is in an array format (like a multiselect or checkboxes field), then the selected values will be converted into multiple tags.
This should be used with caution as it can result in WP Fusion generating many hundreds or thousands of new tags.

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No

Restricting Access to Content

#Overview
WP Fusion adds several methods for restricting access to content based on a user』s tags (or 「lists」 or 「segments」) in your connected CRM.
These features can be used to create members-only content, drip-feed access to content, and create personalized listings of posts, pages, courses, and more.
#Meta Box
WP Fusion adds a meta box to every post, page, and other piece of content on your site, where you can control the visibility of that content and set up redirects if a user doesn』t have access.
You can also apply and remove tags when a page or post is viewed.

There are a few options in WP Fusion』s content restriction meta box:

Users must be logged in to view this page: Check this box to require a user to be logged in to view the content.
Required tags (any): Here you can specify tags that are required to view the content. If the user has at least one of the tags they』ll be able to access it.
Required tags (all): With this setting the user must have all of the tags in order to access the content. For example 「Active Membership」 and 「Gold Member」.
Required tags (not): With this setting, if the user is logged in and has any of the specified tags, they will be denied access.
Redirect if access is denied: Here you can specify a page on your site to redirect to if access is denied. Leave blank to show the restricted content message (see below).
Or enter a URL: Here you can specify an external URL to redirect the user to.
Apply tags when a user views this page: You can specify any number of tags to be applied when the content is viewed.
Remove tags when a user views this page: You can specify any number of tags to be removed when the content is viewed.
Delay: Here you can set a delay in ms before the tags are applied. For example enter 5000 for 5 seconds.

#Restricted Content Message
The restricted content message will be shown if a page is protected and no redirect is specified. You can edit this from the general WP Fusion settings page.

If you enable the setting for Per Post Messages you』ll be able to set a custom message for every restricted post. This setting will appear at the bottom of the post edit screen.
#Restricted Content Message vs Redirect
When protecting a piece of content with WP Fusion you can either set a redirect if access is denied, or leave the redirect blank to show a restricted content message.
This works by replacing the 「content」 area of the page, which works well with normal posts and pages that have a single content area.
The restricted content message on a blog post.
It does not work as well on pages that have multiple content areas or customized templates, for example a product or course page.
The Restricted Content Message isn』t as effective on a product page since the content area is only a small part of the layout.
In cases like that it』s preferable to set a redirect when access is denied.
#Filter Queries
On the General tab of the WP Fusion settings is an option to Filter Queries. When this is enabled WP Fusion will modify any database queries so that posts a user doesn』t have access to are removed from the results.

This can be used to create post grids or course listings of only items a user has access to. It works with all plugins and theme builders.
There are three options:

Off: No filtering (default).
Standard: Restricted posts will be removed from the query results after the query is run.
Advanced: Restricted posts will be excluded from query results before a query is run. This method is slower but works better when using pagination and limits on the number of results.

Generally Standard mode is sufficient. You would only want to use Advanced mode if your restricted items are split across multiple pages (with pagination), or if you』re doing filtering on the items.
For example hiding lessons a user doesn』t have access to in the LearnDash course navigation would work great with Standard mode, but hiding restricted items in the WooCommerce shop catalog or in FacetWP search results would work best with Advanced mode.

Note: Filter Queries is slow. If you have a lot of posts on your site and you haven』t enabled the Filter Queries Post Types setting, it can easily add several seconds to each page load, or even crash your site.
Filter Queries should be used minimally and only when no other method of protecting content will work.

#Filter Queries Post Types
For best performance, it』s recommended to select the post types you want to use query filtering on from the Post Types dropdown.
If this is left blank then query filtering will be run on every piece of content on your site, which may negatively affect performance.
#Filter Queries Arguments
When using Filter Queries in 「Advanced」 mode, by default it will process at most 200 posts in a single query. This is to protect the stability of your site, since each post requires several database queries to calculate the access rules for the current user.
If more than 200 posts are found with WP Fusion access rules, a notice will be logged to the activity logs.
WP Fusion will log a notice if you attempt to process more than 200 posts at a time with Filter Queries in Advanced mode.
Any posts beyond the first 200 will be ignored by Filter Queries, which may result in content being displayed that should be hidden.
You can override this limit using the wpf_query_filter_get_posts_args filter.
However, the higher the limit, the longer the page will take to load, due to the increased number of database queries. This may also result in out of memory errors or timeout errors depending on the available resources of your server.
#Apply Settings in Bulk
You can also apply settings in bulk by selecting multiple posts, pages, or custom post types from the list table in the admin.
Select the items you want to edit, and choose 「Edit」, from the Bulk Actions menu.
Access the bulk edit panel from the Bulk Actions dropdown
Inside the panel will be a section where you can bulk-configure the WP Fusion settings for the selected posts.

If you check the box for Merge Changes, your new settings will be merged into the existing settings for each post.
If Merge Changes is unchecked, each post』s content restriction settings will be overwritten by the settings specified in the bulk edit tool.
#Restricting Access to Archives and Categories
You may wish to restrict access to a category or taxonomy archive page. Click 「Edit」 next to the category or taxonomy term and scroll down to the WP Fusion – Access Settings section.

You can enable Restrict access to archives and select a required tag to protect the archive page for that post type.The access restrictions work the same way they do for pages. Keep in mind that this won』t restrict all content that has the category, tag, or term specified— it will just restrict access to the archive pages for that content.
If you want to restrict access to all content that has the given category or term, check the box next to Restrict access to all. These restrictions will take priority over an individual post』s access rules.
If you want to completely hide the taxonomy term when a user doesn』t have access, check the box for Hide term. This will remove the category / term from all term listings, index pages, search results, and navigation.
#Testing content protection
There are a few ways to review and test your content protection with WP Fusion.
#Review in the admin
When viewing any table of posts, pages, courses, or other content in the admin, you』ll see a lock icon indicating that an item is protected by WP Fusion.

You can hover over the lock icon to display a tooltip showing the access rules for that piece of content.
#Preview with tag
The simplest method for testing access rules is to use the Preview With Tag feature in the admin toolbar.

This will let you preview any page on your site as if your user currently had the selected tag. You can also select Lock All or Unlock All from the menu for additional preview options.
#Testing as a user
The most reliable way to test your site experience is to use an actual user account.
By default your admin user account is excluded from WP Fusion』s content protection rules, but you can disable this by un-checking the box for Exclude Administrators in the WP Fusion settings. Or you can use a test (non administrator) use account.
When testing with a user account, you can see and modify the user』s tags via their admin user profile.

If you』ve just applied a new tag in your CRM, you may need to click Resync Tags to load the updated data into WordPress. To automate this process consider setting up a webhook.

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No

Tracking User Activity

#Tracking User Activity
WP Fusion includes many options for tracking user and customer engagement with your site by applying tags in your CRM. Most of those options are available via the various plugin integrations, but there are a few global options as well.
#Meta Box
The WP Fusion meta box that』s added to every post and page on your site includes an option to either apply or remove tags when that page is viewed.
This can be used to confirm when someone has viewed a page (like when a student starts a course), or to gauge interest in a piece of content by applying a tag after a delay— for example if a user looks at a product for longer than 10 seconds.

#Apply tags
In this example we』ve configured the page to apply the tag Webinar Interest if a user views the page for 10 seconds. This tag could then be used as a trigger to send a followup email from your CRM.
Note that if a page is restricted via WP Fusion, the tags will only be applied if the user has the correct permissions to view the page.
#Remove tags
There is also an option for Remove tags when a user views this page. An example use case for this might be tagging someone as Profile Incomplete when they register on your site, and then removing that tag when they view their profile page.
#Delay
You can specify a delay in milliseconds before any tags are applied or removed. In the screenshot above, 10,000 milliseconds equals 10 seconds.
#Category / term settings
In the same way that you can apply tags whenever a single post or page is viewed, you can also set up any taxonomy term on your site to apply tags when a post with that term is viewed. That can be Categories, Post Tags, or a custom taxonomy.
These settings are accessed by editing any individual taxonomy term.

In this example we have a post tag called 「News」, and WP Fusion is configured to apply the tag Viewed Post in Category 「News」 whenever any post with that post tag is viewed.
For more information on the rest of these settings see the access control documentation.
#Click Tracking
WP Fusion includes an option where you can apply tags when a link, button, or any other HTML element is clicked. That』s covered in the Link Click Tracking documentation.
#Advanced Tracking
WP Fusion also includes a JavaScript API that lets you apply tags and sync data to your CRM with your own JavaScript code. Using this you can create more complex setups such as tagging people based on progress in a video player or based on a quiz score. That』s covered in the JavaScript API tutorial.
#Site tracking
With some CRMs that support page view tracking, WP Fusion bundles the scripts required to enable that functionality. When enabled, all page views are synced to your CRM. More info on that in the Site Tracking documentation.

#Was this helpful?

Let us know if you liked the post. That』s the only way we can improve.

Yes

No