Thanks @VaunMcCarthy that clarifies: it wasn't clear if you actually wanted to block specific pages from being tracked, but it sounds like your main use-case is to avoid PII capture. Here We will be exploring how to extend our recent Data Filtering Rules for Digital Channels, to include also Journey Tracking. See this new Idea for tracking > Genesys Cloud Ideas Portal

Apologies I can't seem to figure out how to include the text of a URL in a post here without it automatically becoming a shortened hyperlink.

Thanks for reaching out Angelo. While the query parameter is available, there are situations where some type of PII may be within the path itself... eg \customersite.com/account/johnsmith]]. In this case johnsmith is an identifying piece of information that we'd want to have stripped out. So it would be much easier if we could add the "root" of a path say "/account" and any URL would strip that portion of the path out. Understandably though that does mean actual page hits and counts would be inaccurate as in this example it would only be showing the root of the site itself. So potentially we'd have to consider dropping the entire page/URL rather than just the path.

Hi @VaunMcCarthy - what's the concrete use-case for wanting to exclude certain paths from tracking? wouldn't that create a gap in the overall web journey?

Hi Jonathan, Divya

I've taken a look but can't seem to find an answer to this one. How can I exclude certain paths from being tracked as well? e.g. customersite.com where I want to exclude anything that has the /city/ path in it?

Hi Vaun,
The 'ingestion point' is the API where the query is handled on the Genesys Cloud side.

In this scenario there are two ingestion points of interest, the ping you mentioned, and the beacon. These calls work together to implement predictive engagement.

We can confirm that there is no logging of those parameters on the Genesys Cloud side. They are redacted before any logging happens.