Progressive profile

The Attribute Present Decision node checks whether the specified attribute is present. It doesn’t check the value of the attribute, only that the attribute exists. This can include attributes that might otherwise be private. A common use case for this node is when you want to check for the presence of a password.

The Attribute Value Decision node checks the value of the specified attribute, and determines if it satisfies the conditions configured in the node. It can perform the following comparison operations:

The KBA Decision node is primarily used in a progressive profile journey where you want to ensure an end user has defined answers to the minimum number of questions required by the system. This can be useful if the number of questions changes, so the end user can be prompted for any necessary additional responses when they next log in. In this case, the KBA Decision node would be used together with the KBA Definition node: if the KBA Decision node evaluates false, the end user would then be taken to the KBA Definition node.

The Login Count Decision node checks whether the end user has signed on the specified number of times. It can be triggered once (using the AT interval) or triggered repeatedly after a set number of sign ons (using the EVERY interval). The sign-on count is not automatically incremented: be sure to include the Increment Login Count node in your sign-on journey if you plan to use this node.

The Profile Completeness Decision node checks how complete an end user’s profile is, and compares that amount with a percentage value set in the node. The value for profile completeness is based on the number of visible, user-editable attributes in their profile that have been filled out.

The Query Filter Decision node uses a query filter to check an end user’s profile for specific information. Use this to check whether a particular field has been filled out or that the contents of a field match a specific pattern. For example, you can use this in progressive profile journeys to check if marketing preferences are set on an end user’s profile. Learn more about constructing effective query filters in Construct queries.

The Terms and Conditions Decision node verifies the end user has accepted the currently active set of terms and conditions. Use this node when you want to verify the end user has accepted your current terms and conditions before proceeding. Use this with the Accept Terms and Conditions node: connect the Terms and Conditions Decision node False output to an Accept Terms and Conditions node.

The Time Since Decision node checks the end user’s creation date against a specified amount of time. This is used when you want to have a time-based reminder for end users to check an attribute. Once the specified amount of time has elapsed, the node evaluates to True the next time the node is triggered, for example, by the end user signing on and going through a progressive profile journey.