Hey @jeff_bloomer, No worries, as soon as this is fixed or whatever the outcome is, I will update this thread with the information.

In AA, this dimension used to work out-of-the-box and it seems functionality isn't much exposed to mimic the same. In general, it checks how long ago the previous visit was, and buckets the hit in the appropriate dimension item. An alternative that I can think of in CJA is to use Cohorts -https://ex...

Hey @MitchellTe1 The video link is bit outdated. Can you try https://developer.adobe.com/analytics-apis/docs/2.0/guides/ or https://developer.adobe.com/analytics-apis/docs/2.0/guides/use-cases/postman/ instead. If still an issue, please log a support ticket and we can take a further look.

Hey @jeff_bloomer @Jennifer_Dungan We have logged a bug for this issue. You can log a support ticket, and we can share the JIRA ID for reference. It seems something changed with the new UI release.

Hey @UjjwalChandra , as explained by @Jennifer_Dungan, these are just some extra backend rules, but you cannot directly set up them within Adobe Analytics UI. They require additional engagement and scoping depending on your use case. In case you prefer to use them, then you can contact your Account ...

Hey @BryceR22 This has been fixed but if you're still facing issue it could be related to some other problem. Can you please log a ticket with Adobe Support? Please include details like error IDs, steps to replicate, HAR logs so that the team can take a look.

Hey @SoumyaMi1, Unfortunately, there is a hard limit of 31 days. So, I'm unsure about any workarounds.

The daily deliveries expire in a month, so in this case, if you use custom frequency set to 90 days, it won't work. It will work with 31 but not 90.

This is expected behaviour when combining Adobe Launch + gtag.js instead of using GTM I believe. GTM isn’t broken — it's just telling you: "I see a Google tag fired, but I didn't fire it!" and Adobe Launch is doing its job — it’s firing the gtag() calls.When tags like gtag('config') or gtag('event')...

This should be resolved. There was an issue at our end that caused this.