SB Reports - metrics issue #128
Replies: 1 comment 1 reply
-
Hi michalaleksandrowicz, Sponsored Display will ask you a string Sponsored Product V2 will be deprecate on [PLANNED DEPRECATION 3/30/2023] Sponsored Product V3 is moved to a new endpoint /reporting/reports and | adProduct (string): [required] Enum: The advertising product such as SPONSORED_PRODUCTS or SPONSORED_BRANDS. Sponsored Brands looks more like SPV2 So we will add some notice in help to avoid space after commas that by the way is the standard I used in general. Your details error: 'details': 'Unrecognized metric: campaignRuleBasedBudget\n' Have an ugly \n at the end that may point you to the problem. Anyway thank you to share with us, Kindest Regards, Daniel. |
Beta Was this translation helpful? Give feedback.
-
Dear Friends,
As a home made hobbyist developer, I have been trying to pull SB reports to my database using python. It worked magic for SP and SD, now I have struggled for the past week with SB and the issue was metrics. Whenever I tried to pull in more than one metric, I was getting for example this one:
'payload': {'code': '422',
'details': 'Unrecognized metric: campaignRuleBasedBudget\n'
' at [Source:',
'requestId': 'W0DEWDAXMT3DVB8751DZ'}}
I had metrics written like this in the data dictionary:
"metrics": "campaignName, currency, campaignId, campaignRuleBasedBudget"
And I could not get it work at all. Always getting Unrecognized Metric error.
Then finally Friday evening, today I try having them written without " ", after commas, like this:
"metrics": "campaignName,currency,campaignId,campaignRuleBasedBudget"
Sounds crazy, i know. But it is working now. Curious though if anyone knows why this is the case? For SD metrrics with " " after commas worked fine. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions