Connector Improvement: Google Analytics: improve config consistency between create and get in REST API
CompletedHi,
In the REST AP, the config returned by a GET on a connector for Google Analytics returns very different data compared to the config which is expected to POST create a new connector.
E.g. to POST:
"reports": [
{
"table": "raw_traffic_analytics",
"config_type": "Custom",
"dimensions": ["date", "country", "channelGrouping", "deviceCategory", "campaign", "medium", "source", "currencyCode"],
"metrics": "sessions, transactionRevenue, transactions, users",
"filter": "",
"segments": ""
}
]
vs GET
"reports": [
{
"table": "raw_traffic_analytics",
"config_type": "Custom",
"dimensions": ["date", "country", "channelGrouping", "deviceCategory", "campaign", "medium", "source", "currencyCode"],
"metrics": ["sessions", "transactionRevenue", "transactions", "users"],
"segments": []
}
]
this is very confusing and can lead to losing time wondering what is wrong, until you go read the doc and facepalm.
Thanks
Best
Guillaume
-
Official comment
Guillaume have you used the v2 version of the payload? This should fix this issue and will be rolled out to all connectors within the next several months.
-
Hi @..., using header "Accept" did the trick, thanks.
Please sign in to leave a comment.
Comments
2 comments