This is as expected.  The policy in your screenshot doesn't specify unsafe-eval, only the unsafe-inline.  And since the unsafe-inline is a Launch problem (not an at.js problem) it'll still throw the exception.  A bit more info is available here: https://docs.adobelaunch.com/launch-reference/client-s...

It sounds like you just need to have your CMS templates that serve the UK pages use the UK property embed code and the CMS templates that serve the Ireland pages use the Ireland property embed code.Then whatever is in the UK property is on the UK pages and whatever is in the Ireland property is on t...

I'm not sure I understand what you're trying to do.  You want to swap them within your own browser for testing?  Or something more broad than that?

Unofficially, I've heard that the new version of AppMeasurement is being tested now.  I'd anticipate AppMeasurement itself will be released a little before a Launch extension with that same update.  I'd probably set my expectations for another week or two.

DTM is not sunsetting in July, the only thing happening in DTM in July is that the Add Property button will be removed.  That said, July currently seems like an achievable time frame.

For DTM both Launch, you'll need to add `unsafe-inline` to the security policy (you can add the domains as in the OP to limit it to a subset of domains).  The whole point of CSP is to block dynamic loading of scripts, which is sort of what tag managers do.at.js 1.X also uses eval(), so if you're usi...

Yes, we marked this as delivered some time ago.  When you're building rules, add a condition, select the Core Extension and look for the Date Range condition type.

I'll talk to Engineering about this.  A very similar problem came up in one of our Slack channels recently (may be the same issue actually).  Changing the structure of the Archive seems like it would be challenging for backward compatibility reasons, but maybe there's something we can do.

Sorry, I'm not super familiar with AEM, but the first two hashed paths are your Company ID (CO1234) and Property ID (PR1234).  Those should never change.  The third is your Build ID (BL1234) and that will change each time you do a build.  The 4th is an Extension Package ID (EP1234) that will change ...