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.

Thanks Divya. Appreciate the responses here. Can you confirm what the "ingestion point" is here? When the "ping" event is sent it includes the full URL so I'd imagine at that ingestion point the full URL is still seen. So are you saying at the actual ingestion point itself there is no logging on?

Hi Vaun McCarthy,

Please find the answers to your questions below.

Can someone please confirm for me what happens with that query on the Genesys side?

Those query parameters are excluded at the ingestion point, so when events are propagated further throughout the platform, they are excluded and no longer present.

Is that still logged?

We redact anything that can potentially contain personal or sensitive information. So, it is not logged.

How can we be certain that those parameters are redacted/excluded everywhere on the Genesys Cloud side?

You can go to “Live now” under Predictive Engagement and click on individual sessions. Then, by clicking on “Page views,” you can verify that the URL does not have the excluded query parameters.

You can also verify the correct behaviours using our API here https://developer.genesys.cloud/devapps/api-explorer#get-api-v2-journey-sessions--sessionId--events

Thanks,
Divya