Operators used in event filters and operators used in filters in interactive analytics do not have a one-to-one correspondence by name. However, you can select operators that produce similar results for both formats.

This difference is important when you use the Run in Interactive Analytics menu item from the Event Forwarding page. For example, if you have an event forwarding filter of matches *foo* and select the menu item Run in Interactive Analytics from the Event Filters page, the Interactive Analytics query equates the event forwarding filter to match regexp ^.*foo.*$, which might not match all the same events.

Another example is matches foo, which when run on interactive analytics is treated as contains foo. Because the interactive analytics function also searches keyword queries, contains foo is likely to match more events than matches foo.

You can change the operators used by Interactive Analytics to address these differences.

  • Change the contains operator tomatches regex.

  • Change occurrences of * from event forwarding filters to .* and prefix filter terms with .*. For example, change the event filter expression matches *foo* to matches regex .*foo.* for interactive analytics.

  • For the does not match operator from event filters, you can use the matches regex operator with a regex look ahead value. For example, does not match *foo* is equivalent to matches regex .*(?!foo).*