# March 2021 Release Note

These are the recent and upcoming Treasure Data releases, features, and improvements. Submit any product feature requests to [feedback.treasuredata.com](http://feedback.treasuredata.com/).

* [Japanese Localization Feature](/release-notes/archive/2021/march-2021-release-note#h1_1633272104)
* [Data Connectors Released](/release-notes/archive/2021/march-2021-release-note#h1_2130797981)
* [VTEX Import Integration Improvement](/release-notes/archive/2021/march-2021-release-note#h2__1470759664)
* [Iterable Import Integration BETA](/release-notes/archive/2021/march-2021-release-note#h2__698172699)
* [Upcoming Releases](/release-notes/archive/2021/march-2021-release-note#h1__368143754)
* [Ads Remarketing](/release-notes/archive/2021/march-2021-release-note#h2_283981909)
* [Braze Output Integration](/release-notes/archive/2021/march-2021-release-note#h2__471688305)
* [Sendgrid Output Integration BETA](/release-notes/archive/2021/march-2021-release-note#h2_52589999)
* [Updates](/release-notes/archive/2021/march-2021-release-note#h1__1539971544)
* [td-agent v4 Release](/release-notes/archive/2021/march-2021-release-note#h2_1114501343)
* [Deprecation of /v3/user/apikey/validate endpoint](/release-notes/archive/2021/march-2021-release-note#h2_1989451295)
* [End of Life for HTTP Endpoints](/release-notes/archive/2021/march-2021-release-note#h2_647739111)
* [Presto](/release-notes/archive/2021/march-2021-release-note#h2__180123269)
* [Presto Function Update](/release-notes/archive/2021/march-2021-release-note#h4__1326892884)


# Japanese Localization Feature

Treasure Data has released a Japanese Localization feature using machine translation on [docs.treasuredata.com](http://docs.treasuredata.com). The new feature is meant to improve the international user experience. Now, [docs.treasuredata.com](http://docs.treasuredata.com) includes a new regional picker to select English and Japanese. After you select the Japanese language, you will be taken back to the page you came from with the content localized in Japanese.

![](/assets/image2021-2-26_10-14-27.f6814e04ee07be77e9ed88070c15e4b8360417301591d2c0a8f4e59bd2d5875a.fffd94dd.png)

# Data Connectors Released

## VTEX Import Integration Improvement

This update supports a new mode to ingest Order Details. Now, detailed information including order items or shipping addresses, and more, can be ingested.

Learn more about [VTEX Import Integration](https://docs.treasuredata.com/smart/project-integrations/vtex-import-integrations).

## Iterable Import Integration BETA

You can now import campaign metric data and user lists from Iterable into Treasure Data for campaign performance analysis and activation.

Learn more about[ Iterable Import Integration](https://docs.treasuredata.com/smart/project-integrations/iterable-import-integration).

# Upcoming Releases

## Ads Remarketing

Support for removal of targets from an existing remarketing list and uploading of your user_ids to Google Ads Remarketing and Audience Targeting is in process. You must have your account whitelisted by Google before being able to send the user_id.

## Braze Output Integration

This new connector sends a list of targeted end-users of the customer. In Braze, you can then configure ads to the targeted list that Treasure Data sent to Braze. Additionally, you can opt-out (delete end users from the existing list).

## Sendgrid Output Integration BETA

SendGrid can send real-time notifications about events that happen on the SendGrid system to a URL. These events include clicks, opens, unsubscribe, bounces, and many others.

# Updates

## td-agent v4 Release

td-agent v3 has been moved to a maintenance mode. We recommend updating your td-agent to the latest stable release of td-agent 4.x as soon as possible.

If you still use td-agent v2 with fluentd v0.12, you are still using td-agent v2 package possibly. It has been deprecated and we recommend upgrading to fluentd v1.0 that is packaged by td-agent 3/4.

## Deprecation of /v3/user/apikey/validate endpoint

/v3/user/apikey/validate API is now deprecated. Using this endpoint will result in a 404 error.

If you have any questions, please contact [support@treasuredata.com](mailto:support@treasuredata.com).

## End of Life for HTTP Endpoints

Toward improving the security of Treasure Data, we are terminating APIs with endpoints that use HTTP for US and Tokyo regions.

No further support is available for HTTP beyond March 1, 2021. If you are using any of the following addresses to access Treasure Data, you must migrate to HTTPS:

* **US region**
  * [http://api.treasuredata.com](http://api.treasuredata.com/)
  * [http://api.treasure-data.com](http://api.treasure-data.com/)
  * [http://api-import.treasuredata.com](http://api-import.treasuredata.com/)
  * [http://api-workflow.treasuredata.com](http://api-workflow.treasuredata.com/)
  * [heroku-logdrain.treasuredata.com](http://heroku-logdrain.treasuredata.com/)
* **Tokyo region**
  * [http://api.treasuredata.co.jp](http://api.treasuredata.co.jp/)
  * [http://api-import.treasuredata.co.jp](http://api-import.treasuredata.co.jp/)
  * [http://api-workflow.treasuredata.co.jp](http://api-workflow.treasuredata.co.jp/)


## Presto

We’ve added some Presto performance improvements:

* We reduced query result output size from 200GB to 100GB. Learn more about the [Presto Query Result output limitation](https://docs.treasuredata.com/articles/project-product-documentation/presto-known-limitations#PrestoKnownLimitations-ErrorMessage%E2%80%93Killedbythesystembecausethisquerygeneratesoutputformorethan100GB) and discover how to apply result_redirect_output magic comments to [speed up your query](https://docs.treasuredata.com/articles/project-product-documentation/speed-up-queries-that-produce-massive-results).
* We updated the default setting for Presto Join and Sort methods. Learn more about [Choosing Presto Join and Sort Algorithms](https://docs.treasuredata.com/articles/project-product-documentation/choosing-presto-join-and-sort-algorithms).


#### Presto Function Update

* TD_TIME_FORMAT now supports a four-word timezone name.
  * For example, TD_TIME_FORMAT(1425168000, ‘yyyy-MM-dd HH', 'WITA') returns WITA’s timezone correctly.