Conditions - Where and When to Show Website Engagement Campaigns

Conditions determine where and when website interactions appear for visitors on your website. By configuring conditions, you can control which visitors see specific interactions and under what circumstances.

• Campaigns must have at least one condition.

• Conditions can be combined. If multiple conditions are set, a visitor must satisfy all conditions for the interaction to be displayed.

• Each condition type has its own set of configurable parameters.

Determines which pages on your website the interactions can appear on. This is the most commonly used condition and is included in most campaigns.

Checks for the presence, absence, or specific values of query parameters in the page URL. This is useful for targeting specific visitor journeys, such as tracking visitors coming from a marketing campaign link.

Evaluates the presence, absence, or specific values of cookies in the visitor's browser. This is useful for integrating with other campaigns or external systems used on your website.

Determines whether the visitor is logged in, tracked, or anonymous. This helps in differentiating interactions for authenticated users versus anonymous visitors.

Checks for the presence, absence, or specific values of a contact field in PropFuel associated with the visitor. This is particularly useful for targeting visitors based on AMS data synced via an existing integration.

Determines whether a visitor is on a contact list in PropFuel. This is useful for including or excluding specific lists of people from seeing an interaction. For example, you can exclude active members from a renewal campaign.

By leveraging these conditions, you can create highly targeted and personalized interactions that enhance visitor engagement on your website.

The Page URL condition determines which pages on your website will display a specific PropFuel interaction. This condition is the most commonly used and serves as the foundation for many engagement strategies.

• The Page URL condition checks the visitor's current webpage address and matches it against the criteria you define.

• If the URL matches the specified parameters, the associated interaction will be displayed.

• This condition can be combined with others to refine targeting.

A URL consists of different components, primarily the domain and the page path:

• Domain: The main part of the website address (e.g., example.com).

• Page Path: The specific page on the website (e.g., /pricing).

When configuring the Page URL condition in PropFuel:

• The domain is optional, but recommended.

• If you exclude the domain, the condition will apply the same URL pattern across all websites your plugin code is installed on.

You can configure the Page URL condition using the following operators:

• = (Equals): The interaction will only display if the visitor's URL exactly matches the specified URL.

• != (Does Not Equal): The interaction will display if the visitor's URL does not match the specified URL.

• Contains: The interaction will display if the visitor's URL contains a specific string (e.g., /pricing will match example.com/pricing and example.com/pricing/details).

• Does Not Contain: The interaction will display if the visitor's URL does not contain a specific string.

Click the '+' sign to add another URL to check. If multiple tests are configured, the condition will pass if any of the URLs match.

The Page URL condition is useful for:

• Displaying interactions on specific landing pages.

• Targeting visitors browsing product pages.

• Triggering engagements for blog readers.

• Personalizing content based on the visitor's navigation path.

By leveraging the Page URL condition, you can create highly targeted experiences for different segments of your audience.

The Query Parameter condition allows you to target visitors based on the presence, absence, or value of specific query parameters in a page URL. This is useful for tracking specific visitor journeys, such as those coming from marketing campaigns, referrals, or dynamic URLs.

• Query parameters are key-value pairs appended to a URL after a ?, such as example.com/page?utm_source=google.

• The condition evaluates the query parameters in a visitor's URL to determine if an interaction should be displayed.

• This condition can be combined with others to refine targeting.

You can configure the Query Parameter condition using the following operators:

• = (Equals): The interaction will display if the query parameter matches the exact value specified.

• != (Does Not Equal): The interaction will display if the query parameter does not match the specified value.

• Contains: The interaction will display if the query parameter contains a specific value.

• Exists: The interaction will display if the query parameter is present, regardless of its value.

• Does Not Exist: The interaction will display if the query parameter is missing from the URL.

The Query Parameter condition is useful for:

• Displaying different interactions based on UTM parameters from marketing campaigns.

• Targeting visitors based on referral sources (e.g., ?ref=partner).

• Customizing interactions based on search filters or selections in dynamic URLs.

• Excluding or including visitors based on tracking parameters.

By leveraging the Query Parameter condition, you can create highly personalized and relevant interactions based on how visitors arrive at your website.

The Cookie condition allows you to target visitors based on the presence, absence, or value of specific cookies stored in their browser. This condition is useful for personalizing interactions based on external data stored in cookies.

• A cookie is a small piece of data stored in a visitor's browser by a website.

• The condition evaluates whether a specified cookie exists, does not exist, or contains a particular value.

• This condition can be combined with others to refine targeting.

You can configure the Cookie condition using the following operators:

• = (Equals): The interaction will display if the cookie's value matches the specified value.

• != (Does Not Equal): The interaction will display if the cookie's value does not match the specified value.

• Contains: The interaction will display if the cookie contains a specific value.

• Exists: The interaction will display if the cookie is present, regardless of its value.

• Does Not Exist: The interaction will display if the cookie is missing from the visitor's browser.

The Cookie condition is useful for:

• Personalizing experiences based on user preferences stored in cookies.

• Integrating with third-party tracking systems to trigger interactions.

By using the Cookie condition, you can ensure that interactions are relevant and aligned with visitor behavior on your website.

The Contact Authentication condition allows you to control interactions based on a visitor's authentication status. This helps differentiate experiences for logged-in users, returning visitors, and anonymous users.

Visitors can fall into one of three authentication states:

• Logged In: The visitor is authenticated through a configured integration, such as an AMS, CRM, or SSO system. This ensures that their identity is verified, and interactions can be personalized based on their account data.

• Known: The visitor has been identified previously and tracked using a browser cookie but is not currently logged in. This state allows for a level of recognition without requiring an active login session.

• Anonymous: The visitor has not been identified before and does not have an associated cookie. These users are completely unknown, making interactions more generalized.

• When a visitor lands on your website, PropFuel evaluates their authentication status based on integrations and tracking mechanisms.

• The condition filters interactions based on whether the visitor is Logged In, Known, or Anonymous.

• This condition can be combined with others to refine targeting strategies.

The Contact Authentication condition is useful for:

• Displaying member-exclusive interactions to logged-in users.

• Re-engaging known visitors who haven't logged in recently.

• Offering general interactions for anonymous users while encouraging authentication.

• Personalizing content based on authentication level and past interactions.

By leveraging the Contact Authentication condition, you can tailor experiences to different visitor types, ensuring relevant and meaningful engagement.

The Contact Field condition allows you to target interactions based on specific data fields associated with a visitor's contact record in PropFuel. This is particularly useful for personalizing engagements based on AMS, CRM, or other integrated system data.

• PropFuel syncs contact data from integrated systems, storing relevant fields such as membership status, job title, organization, and more.

• The condition evaluates a visitor's contact record to determine whether an interaction should be displayed based on the configured criteria.

• This condition can be combined with others to refine targeting further.

You can configure the Contact Field condition using the following operators:

• = (Equals): The interaction will display if the contact field value matches the specified value.

• != (Does Not Equal): The interaction will display if the contact field value does not match the specified value.

• > (Greater Than) and < (Less Than): The interaction will display if the contact field value is greater than or less than the specified value.

• Contains: The interaction will display if the contact field contains a specific value.

• Does Not Contain: The interaction will display if the contact field does not contain a specific value.

• Exists: The interaction will display if the contact field has any value.

• Does Not Exist: The interaction will display if the contact field is empty or not set.

The Contact Field condition is useful for:

• Displaying interactions only to members based on membership status.

• Showing targeted messaging to specific job titles or industries.

• Triggering interactions for contacts based on event registration status.

• Excluding visitors who have already taken an action, such as completing a survey or opting out of communications.

By leveraging the Contact Field condition, you can create highly targeted and personalized interactions, ensuring relevance for each visitor based on their stored contact information.

The Contact List condition allows you to target interactions based on whether a visitor is included in a specific contact list in PropFuel. This is particularly useful for segmenting audiences, managing engagement for specific groups, and ensuring interactions reach the right people.

• Contact lists in PropFuel are created from synced data or dynamically generated segments.

• The condition checks if the visitor’s contact record is included in a specified list.

• This condition can be combined with others to refine targeting further.

You can configure the Contact List condition using the following operators:

• On List: The interaction will display if the visitor is part of the specified contact list.

• Not On List: The interaction will display if the visitor is not in the specified contact list.

The Contact List condition is useful for:

• Excluding current members from renewal campaigns.

• Targeting event attendees with follow-up interactions.

• Sending personalized content to specific audience segments.

• Ensuring that only selected individuals see a particular engagement.

By leveraging the Contact List condition, you can create highly targeted interactions that align with your audience segmentation strategy.