Avoid Overwriting Values

In the following example, two context data variables are used on the site to capture search terms: search_keyword and search_term. However, based on the configuration, the search_keyword value is always overwritten, even if search_term is empty.

This rule should be reconfigured to test each context data variable for a value before populating the Internal Search Term, and optionally, concatenating the two values if there is a use case for keeping them both.

Encode Search Terms to UTF-8 or Unicode

Search terms pulled from a query string must be encoded correctly or they won’t be matched by processing rules.

Starts With, Contains, and Ends With

Select the correct matching condition to find the most restrictive condition that matches correctly. You can search for values in a report before creating a rule to make sure there are no unintended matches. For example, you should search the Prop2 report to find all locations where this condition matches before enabling this rule.

How Processing Rules are Applied when Copying Hits using VISTA

If you have a VISTA rule configured to copy hits to another report suite, the hits are sent through any processing rules defined in the other report suite.

If you have processing rules defined on the original report suite, these rules may or may not be applied based on how the VISTA rule was configured by Engineering Services. To find out, you can ask your implementation specialist if the VISTA rule copies the “pre” or the “post” values to the additional report suite. If the “pre” value is copied, processing rules defined on the original report suite are not applied. If the “post” value is copied, processing rules are applied before the hit is copied.

Analytics