Welcome to Version 12
Starting today, October 27, 2022, version 12 (v12) of the Twitter Ads API is available to all developers. This release includes support for the Catalog API and an update to Do Not Reach Lists.
As with our previous versions, there will be a ~6 month transition period to migrate to v12. On March 30, 2023, the existing version 11 (v11) of the Ads API will no longer be available. We encourage all developers to migrate to the latest version of the Ads API as soon as possible to avoid any service disruptions.
Note: As of this release, Version 10 (v10) of the Ads API has reached its end of life and is no longer available.
What’s new:
[NEW] Catalog API
-
Engineering Effort: Med - High
-
Most relevant to: developers wanting to offer programmatic catalog management and/or support the end-to-end creation of Dynamic Product Ads (DPA).
-
Status: Limited availability - request early access here.
As a part of Twitter’s on-going work to support on-platform commerce, we are excited to introduce the Catalog API - a new tool that enables programmatic catalog management and grants advertisers direct control over how their product catalogs are organized, ingested, and updated.
The Catalog API is a foundational building block for commerce on Twitter and a prerequisite for supporting Dynamic Product Ads. Across 4 new endpoints, this API enables programmatic catalog management and gives advertisers the ability to set up product feeds, group products into sets, and holistically manage product catalogs.
Ahead of our broad launch in the coming months, you can gain early access to the new Catalog API by filling out this form.
To learn more, review our forum announcement and detailed developer documentation.
What’s changing:
[CHANGED] Phone Number Matching for Do Not Reach Lists
- Engineering Effort: Medium
- Most relevant to: developers offering campaign management, audiences, or targeting services
- Status: General availability
Do Not Reach Lists (DNRL) serve as an alternative to exclusion Custom Audiences and work as an overarching audience management tool that allows advertisers to seamlessly exclude a single group of people from all campaigns within their ads account.
With this update, we are introducing support for phone number (phone_number) as a new user identifier that can be used for matching users within Do Not Reach Lists (do_not_reach_lists). Previously, we only offered support for email addresses (emails).
By offering support for this new identifier, advertisers will be able to leverage more of their customer data and improve their ability to exclude people from receiving their ads on Twitter.
Key Notes:
-
For Do Not Reach Lists, phone number support will only be available with version 12 or above. However, for Custom Audiences, phone number matching is supported with v11. See the “Phone Number Matching in List Custom Audiences” forum post here.
-
The JSON POST body structure for Do Not Reach Lists will be changing with the release of v12. Please review the DNRL forum post for more information and an example of the new structure.
To learn more, review our forum announcement and detailed developer documentation.
To tap into these new features and to stay on track for future versions, we highly encourage you to migrate to v12 at your earliest convenience.
Please let us know if you have any questions.
Twitter Ads API team
