Based on Adverity Support’s feedback, Cards made in the ads.twitter or Twitter Ads API will be available in API reporting. Cards made in the “Twitter User Interface” will not be retrievable in API reporting (links below)
- Can you confirm what the “Twitter User Interface” is and how this differs from ads.twitter or Twitter Ads API?
- Where else can a Twitter Card be created? (i.e outside of ads.twitter or Twitter Ads API)
- Is it possible to convert/tag those cards that were potentially created outside of ads.twitter or Twitter Ads API so that we are able to retrieve card information from these cards natively from API feed?
- If not, is the only solution to ensure that card data is passed back is to create cards exclusively in ads.twitter or Twitter Ads API?
The forums are primarily for developers looking for help with the API integration. I would recommend having Adverity reach out to us to get support integrating Cards into their platform.
Late last year we introduced a new Tweet Composer experience (on ads.twitter.com) that utilizes a new carousel cards. This UI combines creating a Tweet with creating either Website or App Carousel card. These cards can only be accessed via the new cards API endpoint. The support team seems to indicate that their platform has not added support for the new cards endpoint and cannot access these via API.
I would recommend reaching out to Adverity and have them review the following posts:
+Baseline Support for vis
Hi Tom,
Thanks for getting back to me. Will review the below and share this feedback with Adverity Support
Will reach out if we have any additional questions
Thanks,
