The July 2026 release expands several connectors with new datasets and fields, ships an early version of the Dataddo MCP Server for connecting AI assistants to the platform, and resolves a batch of extraction and authorization issues across Facebook, Google, LinkedIn, Square, and the core platform.
Connectors
New Datasets, Attributes, and Metrics:
- Apple Store Connect: Added a new Customer Reviews dataset.
- Facebook Ads: Added a new Ad Image Hashes dataset, resolving carousel child-attachment image hashes to their permalink URLs.
- Google Ads: Added
Keyword Plannerhistorical metrics. - Google My Business: Added the
BUSINESS_FOOD_MENU_CLICKSengagement metric. - Mailchimp: Added
mmerge1andmmerge2custom merge fields to the List Members dataset. - QuickBooks:
- Added
SKUto the Item dataset. - Added
Countryto the Customer and Vendor datasets. - Added a new TaxCode dataset.
- Added
- TikTok Ads:
- Added new Smart+ Creatives Metrics by Campaign, Smart+ Creatives Metrics by Ad Group, and Smart+ Creatives Metrics by Ad datasets.
- Expanded the existing Smart+ Creatives Daily Metrics dataset with new dimensions and fields.
ReachandFrequencycan now also be pulled consolidated byCampaign IDfor a date range, instead of only daily granularity.
Connector Updates:
- JSON Connector: Clarified that the
{{dateRange}}placeholder must be used twice in a request body — once for the start date, once for the end date — to extract a full range; a single placeholder only resolves to one date.
New Features
Dataddo MCP Server
Connect your AI assistant directly to Dataddo through the Model Context Protocol (MCP) — ask it to search the connector catalog, pull dataset details, or check setup documentation without leaving your assistant of choice. This first version of the server currently covers catalog search and documentation retrieval, with pipeline management, data querying, and monitoring on the roadmap. Available at https://headless.dataddo.com/mcp, no authentication required.
Bug Fixes
Connector Fixes
Facebook Ads:
- Fixed the Insights dataset returning only a hash field instead of resolved values.
Facebook Graph:
- Fixed Instagram Online Followers – Hourly dataset source creation failing because the date range kept reverting to "Yesterday." New sources for this metric should use the Instagram Organic – Online Followers dataset going forward.
Google Analytics:
- Fixed accounts that had been authorized twice with the same email, caused by a stale credential hash on the original authorizer.
LinkedIn Ads:
- Fixed the Ads dataset failing with a validator error (
must specify at least one item in metrics) across all accounts.
Square:
- Fixed Payments datasets ignoring the configured source date range and extracting far more history than requested. This was caused by an incorrect date format being sent to the Square API, plus the extraction window itself needing to be restricted.
General Fixes
"Add New Account" button:
- Fixed the button not working. It was broken because several dashboarding destination templates (Dataiku, Klipfolio, Looker Studio, Power BI, HTTP, Tableau, Zoho Analytics) were missing the authorizer config needed for the redirect flow.
Authorizer creation errors:
- Fixed the original error being hidden behind a generic message.
Authorizer editing:
- Fixed editing an authorizer not updating its identifier.
Database source creation:
- Fixed a JavaScript error that blocked creating database sources.
Extraction errors:
- Fixed
EXTRACTOR_BAD_REQUESTerrors affecting most datasets. This was caused by a regression where timestamps stopped being accepted in grids.
Source creation errors:
- Fixed errors not being surfaced to the user when source creation failed.