Sorry, for further clarification, what we have is multiple workspaces, and we want to make sure that when someone becomes and MQL for one workspace, it won't automatically mean they are an MQL for the other workspaces. So our idea was to use a unique identifier in the naming convention of our program, and use those to separate out which lead cycle they will follow. So in your instance with countries, if someone becomes an MQL in workspace A, that doesn't mean they are an MQL in workspace b. We need each workspace to have it's own path.
... View more
.png)