Connector Improvement: MNTN Connector Update to V3 API & Enable Custom Reporting
PlannedThe MNTN Connector seems to use their V1 API: the tables that we can ingest are individual summary marts; they're already aggregated by a single dimension, and you can't join or group by dimensions such as campaign groups, advertisers, creatives, nor geographic information. The current data we get from the connector isn't usable by us.
We need the connector updated to their V3 API: the data entities are designed as a star schema - the api query's data parameter can join and group aggregates on dimension tables around a fact table called "graph" that contains all of the metrics. Thus we need the connector to support the V3 API, and probably custom reporting as well.
https://help.mountain.com/en/
https://api3.mountain.com/apidata?format=human&begin=2024-01-01&end=2025-09-31&data=CampaignInfo.name,CreativeInfo.name,stateinfo.name,graph.spend&key=<>
Note that the key value has been removed.
-
Official comment
Hi David,
Thank you for reaching out and sharing your detailed feedback regarding the MNTN Connector. We truly appreciate your insights and the effort you've put into exploring the V3 API capabilities.
I'm pleased to inform you that updating the MNTN Connector to support the V3 API is indeed part of our development roadmap. Our team recognizes the importance of enabling more comprehensive data access and custom reporting capabilities, just as you've described.
We are actively working on this update This upgrade will allow you to leverage the star schema design, facilitating more robust data analysis and reporting.
We appreciate your patience and enthusiasm as we work towards delivering this improved functionality. Please feel free to reach out if you have any further questions or need additional assistance.
Best regards,
Syead Mujtaba Imam Rizwi
Please sign in to leave a comment.
Comments
1 comment