The older version of the API, 1.4, allowed us to download a JSON of the processing rules in a suite. Since these are instrumental in transforming data into eVars, Props, and Events, they are an essential part of maintaining the data quality of a suite. The newest version of the API, 2.0, does not currently support accessing the processing rules, and it's been stated on Github that, as of this idea submission, processing rules access is not even on the roadmap. Unless Adobe is going to eliminate these rules (and the eVars and Props that are driven by them), a mature multi-site installation of Adobe Analytics, esp. across mobile and web, relies on a constant overview of processing rules for maintenance, QA, and to aid site and mobile app developers.
Please make sure that processing rules are accessible via the APIs, not just in version 2.0, but in all future versions. Leaving 1.4 up is not a complete solution, as Adobe may deprecate it at any point.
Any update with this Adobe?
Also, is v1.4 API being sunset? What will be the impact on rSiteCatalyst package?
@devconsole , do you know if this API is anywhere in the work queue? It seems many users are in need of more robust Report Suite/Admin API.
@Jacob-DDdev unfortunately, I am not close enough to the individual product APIs. The Dev Console role is to make Adobe APIs available externally but we don't build or manage the individual APIs and their capabilities. Maybe post in the Questions tab and someone from the Analytics team will be able to address
API support for Processing Rules is not available in API 1.4 or 2.0 at this time, including read-only API methods. Processing Rule changes are currently restricted to the user interface. There is no announced timeline for when this functionality will be available by API.
To answer @anmassey's question, there is no announced timeline for end-of-life with API 1.4. RSiteCatalyst is not provided or supported by Adobe but is an open-source project supported by a community of users.
@Brian_Kent_Watson , firstly, your answer is incorrect.
Secondly, it's extremely rude to just dismiss a popularly used project which extends the capabilities of Analytics both furthering its adoption and picking up the slack where Adobe didn't bother to spend the resources.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.