About conditions

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Altocloud Administrator's Guide for version Current of Altocloud.

Conditions identify who belongs to specific segments and who achieves specific outcomes.

About the different types of conditions

When you create segments or outcomes, you define conditions. Each condition is comprised of an attribute and an operator:

  • Visitor attributes are characteristics that all the visitors in the group share. For example, location, browser, device type, and so on.
  • Campaign attributes are special visitor attributes that enable UTM-tracking of campaign activity.
  • Visitor journey attributes are actions that all visitors in the group take. For example, completing a form or going to a specific webpage.

For information about the available operators, see Operators for conditional expressions.


Add a condition

1

  1. When you create a segment or create an outcome, click Add first attribute or Add next attribute.
  2. Select the attribute.
  3. Select the operator.
  4. Select or specify the value.
  5. To add more conditions, click Add next attribute.

Edit a condition

1

  1. When you create a segment or create an outcome, click Edit next to the condition.
  2. Make your changes.


Delete a condition

1

  1. When you create a segment or create an outcome, click Delete next to the condition.
Important
When you click Delete, your condition is deleted immediately.

Operators for conditional expressions

OperatorsEx0130.png

Operator Description Example
equals Finds alphanumeric values that exactly match the attributes in the expression. Browser version equals 6.5
not equals Finds alphanumeric values that do not exactly match the attributes in the expression. Browser version does not equal 7.0
like Finds alphanumeric values that match the attributes in the expression. Browser like Chrome
not like Finds alphanumeric values that do not match the attributes in the expression.
Browser not like Safari
Important
To match alphanumeric characters, you can use either the equals/not equals or the like/not like operators. Consider how precise you need your matching to be.
  • Use equals/not equals when you want to match exactly what you enter here. For example, use equals when you want to match the URL of your home page.
  • Use like when you want to match non-numeric entries that are similar, but not identical, to what you specify. Altocloud finds values that contain the the complete set of characters you specify. For example, "like auto" matches "automobile," "automatic," and "Automaton."
  • Use not like when you want to find non-numeric entries that do not contain the complete set of characters you specify. For example, "not like auto" matches "life," "Additional," and "car."

Custom attributes

A custom attribute is any extran information that you want to send to Altocloud through an ac('record).

For example, an ecommerce site might add a 'packageDeliveryStatus' attribute to segment users whose packages have been shipped.

Example: abandoned form

In the following example, an action map will be triggered if a visitor using Chrome version 56 goes to the Request Quote page, but then navigates away from it to the About page before completing the request.

First define the visitor attributes: large

Then define the journey details: large


Design tips

Altocloud tracks visitor activity on your website at a very detailed level. In order to trigger a specific action map, the visitor's behavior must exactly match how you define the segments and outcomes for the action map. Keep the following points in mind:

Important
  • When you create your segments and outcomes, create them with a specific action map in mind.
  • Group together all of the parts that are required to complete one visitor journey activity.
  • Define the parts in the correct sequence.
  • You can specify any combination of visitor and journey attributes. The more of these conditions you define, the more specific the segment, and the fewer number of customers who belong to it.
  • You must specify at least one visitor or journey attribute per segment or outcome.
  • You complete the same process of defining attributes when you create both segments and outcomes. However, visitor attributes and journey attributes are not shared across segments and outcomes.