Analytics 1.4 API - Rules

[#1]

It seems like there's a gap in the Analytics Admin 1.4 around rules. First, I don't see an endpoint to get standard processing rules. I've checked all of the endpoints listed on GitHub:

analytics-1.4-apis/index.md at master · AdobeDocs/analytics-1.4-apis · GitHub

Additionally, when I call ReportSuite.GetMarketingChannelRules, I don't see the actual eVar in question in the API response, just:

{

   "ruleset_id": 345,

   "channel_id": 1,

   "junction": "all",

   "channel_value": {

   "type": "referring_domain",

   "id": "0",

   "query_string_parameter": ""

  },

   "rules": [

  {

   "rule_id": 123,

   "hit_attribute": {

   "type": "evar",

   "query_string_parameter": ""

  },

   "operator": "equals",

   "matches": [

   "12312313"

  ]

  },

[#2 · Accepted solution]

1) "processing rules" are not available through API 1.4. at least I haven't seen them either

2) I would guess the the eVar is "eVar123", because the key "rule_id" is rather the id for the element in this rule than the real ruleID (which is 345)

[#3]

ursboller​ very true, but it can't hurt to try 🙂 I would of course love to get the admin endpoints in the 2.0 API, it's a pain to switch back and forth between the launch and analytics 1.4 APIs.

[#4]

Thanks ursboller​!

I can't find it either, it looks like it was shot down previously:

https://github.com/AdobeDocs/analytics-1.4-apis/issues/7

But I can't think of an actual reason to not support it so I opened another ticket to re-litigate the issue:

Missing Method ReportSuite.GetProcessingRules · Issue #66 · AdobeDocs/analytics-1.4-apis · GitHub

Regarding #2, 123 was just a placeholder for the real id, since I didn't know if those were meaningful. The ID did not contain the eVar number. So I created a ticket for that as well:

ReportSuite.GetMarketingChannelRules - Missing eVar # · Issue #65 · AdobeDocs/analytics-1.4-apis · G...

[#5]

Processing Rules API is not available in 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.

[#6]

agree - that's why we still are on 1.4 in most cases and haven't switched all over to 2.0

eagerly waiting for more endpoints on 2.0

[#7]

cool! thanks for opening the tickets.

but, I wouldn't expect that they fix a lot on API 1.4 since 2.0 might be the way to go. hopefully we have those API endpoints sooner than later ...