Yes, that is correct.  The easiest (and probably best) solution would be to create a Calculated metric of Linear (or participation) Revenue. Then, pull the metric into a Pages report. The advantage of this method is that the linear allocation could be for Visit OR Visitors (within the lookback windo...

The default limit is four active data feeds per report suite.

I believe this 'limitation' is based on the shift in 'reporting philosophy' (which Workspace and the 2.0 report API are based on). Namely, large breakdowns (ie 50k, but 50k) should be done in Data Warehouse.  The way breakdowns are requested has changed between the 1.4 and 2.0 report API. It might n...

There are a few differences in reporting between Workspace and Reports & Analytics, which is comparable to report API 1.4--which is what Power BI is currently based on. Most of the differences are based on the 'real-time' and 'lookback' concepts Workspace is able to do (and R&A/API 1.4 are not).   I...

Wonderful! I did notice 32 - 35 show up for report suites that don't have a custom calendar. I put in a request to see if we can only show up to 35 for report suites with custom calendars. No promises...

The default limit is 4 active data feeds at a time. If there are already 4 active feeds, any new feed request go into the 'Approval Pending' status until they can manually be approved. If approve does not come within a few weeks, feel free to reach out to Customer Care, who is able to activate it/th...

Have you already been using Attribution IQ? That might be the closest you'll get at the moment.  This doc: https://experienceleague.adobe.com/docs/target/using/release-notes/known-issues-resolved-issues.html?lang=en has a section that reads:   When using Target activity impressions and conversions i...

Hi! The best way I know to do this is to follow the way Workspace does it (since workspace uses the same 2.0 APIs). The following document talks about how to grab the JSON from Workspace to use in your own (custom) API 2.0 requests: https://github.com/AdobeDocs/analytics-2.0-apis/blob/master/reporti...

Good catch! You are correct, line items 32-35 should not be options. I have opened an internal ticket with our teams to look into this.

Hi, I was reviewing some older posts/questions. I assume you have already found the answer that the "splitting up" and persistence of list var values will come after any edits made via processing rules.