Limitations of Using Wildcards in Path Queries

Wildcards are an important tool for constructing path queries, but they do have some limitations.

For example, a query path=*^Pricing^*Purchase^* which should return visits in which users visited “Pricing” section and later on in the same visit went to “Purchase” section, would match:

path=^^Pricing^Purchase^^
path=^^Pricing^FAQ/Shipping^Purchase^^
path=^^Product/Details^Pricing^Purchase^^

but it would also match “FAQ/Purchase” section instead of intended “Purchase” section.:

path=^^Pricing^FAQ/Purchase^^

Unfortunately, changing the query to path=*^Pricing^Purchase^* would exclude visits in which users moved from pricing to purchase indirectly:

path=^^Pricing^FAQ/Shipping^Purchase^^

and changing the query to: path=*^Pricing^*^Purchase^* would exclude visits in which users moved from pricing to purchase directly:

path=^^Pricing^Purchase^^

To some extent, this limitation can be mitigated by combining multiple path queries:

path=*^Pricing^*^Purchase^* OR path=*^Pricing^Purchase^*