Can we use Pseudonymous Profiles Settings for proper profile enabled

@asheesh_pandey , @bjoern__koth please check if you can assist here

You can... but I'm unclear on why you would want to.

Normally we reserve the list of namespaces for pseudonymous profile deletion to device and cookie namespaces. Plus other relatively short lived identity namespace. So ECID, AAID, AACUSTOMID, IDFA, GAID, etc.

If you have other longer lived identities.... CRM ID, Loyalty ID, etc.... normally those are not included in that P-TTL namespace list. Doing that would shorten the lifespan of those to the same duration as actual pseudonymous profiles such as those with only an ECID from anonymous unauthenticated web site browsing. This is true whether it's a standalone namespace/profile or a namespace that you expect to join with others in some identity graphs.

Lengthening the P-TTL retention setting is allowed of course, but then that increases the retained profile count accordingly which might push your addressable audience count above your licensed limit.

Here's a reference on P-TTL that I've found helpful:

https://experienceleague.adobe.com/en/docs/experience-platform/landing/license/data-management-best-practices#pseudonymous-profile-expirations

You can do what you described... it will work. But consider also using the Data Lifecycle Record Delete feature as a way to remove these profiles when they are no longer needed instead of P-TTL:

https://experienceleague.adobe.com/en/docs/experience-platform/data-lifecycle/home

Would also suggest that you figure out which set of namespaces that you want to be unique per graph and configure Identity Graph Linking Rules accordingly:

https://experienceleague.adobe.com/en/docs/experience-platform/identity/features/identity-graph-linking-rules/overview