A conversion goal is a criterion to count visits as converted. The following options are available:
- Web request
- Method invocation
- Custom measure
Configuring conversion goals is especially useful with e-commerce business applications where the conversion rate (spectator or buyer ratio) should be calculated. For example, if your web-site calls an
orderById method whenever a user orders an item, you can define a corresponding Methods - Invocation measure that identifies a conversion.
After you define at least one conversion criterion, you can use the Visits - Conversion Rate measure (which indicates the conversion rate of any of the conversion measures) and consequently, the conversion count of your visits. There is a separate conversion rate measure created for each measure that is assigned as a conversion measure that only indicates the conversion rate of this specific conversion measure. Default names of these measures are Conversion Rate for <conversion measure name>, but you can rename them as you want.
A visit counts as converted if a web request or a web service is called that matches a specified URI pattern. The pattern can be specified using one of the following modes:
- equals: The pattern applies if the actual name is equal to the pattern text.
- starts: The pattern applies if the actual name starts with the given pattern text.
- ends: The pattern applies if the actual name ends with the given pattern text.
- contains: The pattern applies if the actual name contains the given pattern text.
- regex: Allows regular expressions. For example,
ClassName[0-9]+specifies all classes that start with
ClassNamefollowed by any number.
A visit counts as converted if the selected method is invoked somewhere in the monitored infrastructure by any actions of a visit. Select the required method using the Class Browser.
A visit counts as converted, if specified measure is triggered.