Skip to content
Book a demo

Connect documentation

All documentation
Documentation

Version 1.0.12

On this page

MCP3 changed3 fixed

Tools

Changed

Datastream status column can be changed

The Adverity MCP server and Connect Agent can now change a datastream's "Add status column" setting, and on an older Adverity version they say to change it in the datastream's settings.

Fixed

Weekly schedules on a named day and time range

Agents can now set up a weekly schedule on a named day with a named time range, such as every Sunday at 01:00 UTC for the last 365 days. The tool now says which number is which weekday (1 is Monday, 7 is Sunday), listing a datastream's schedules shows every time range with its id, and the approval preview spells out the day, time and range in words and says when the datastream does not offer that range.

Fixed

Datastreams created with a schedule come out enabled

A datastream created through datastream_write with enabled: true and a schedule now comes out enabled, as the confirmation card shows, instead of disabled. When the create carries no schedule and Datatap switches the datastream off, the tool now says so and gives the next step.

Server and sign-in

Fixed

Requests to the instance URL only reach public internet addresses

Requests to the Datatap instance URL a user signs in with, and to anywhere that instance redirects, now only reach public internet addresses. Internal and cloud metadata addresses are refused. The API-key sign-in form also requires an https:// instance address, since the key is sent to it.

Agent guidance

Changed

Facebook Ads and Google Ads guides recommend ids and names of every level

The Facebook Ads and Google Ads guides now recommend that a datastream set up at campaign, ad set (ad group) or ad level also gets the ids and names of its own level and of the levels above it (account or customer, campaign, ad set or ad group), as Adverity's services team sets them up, so reports can group the data by campaign and account. The guides also ask the agent to say in its reply which of these fields it added, so they can be removed if they are not wanted.

Changed

Local data retention guide

A new local data retention guide (read_docs topic local-data-retention) lets the agent answer retention questions, such as how to keep no extracts, without sending users to Support.