How ListenFirst improved efficiency and accuracy with the v2 API

Historically, digital marketers have lacked a unified view of their data. There could be organic data in one system, paid data in another, and conversations coming from different places. But with clients and stakeholders asking questions like, “How many impressions did I receive yesterday?” followed by “What is the organic vs paid split?,” the need for a streamlined way to aggregate and interpret this data is more important than ever.

Looking to solve these questions, ListenFirst - a social analytics platform that has been built with the X Developer Platform for over 10 years – needed to create a tool to collect organic and paid X data from a single source of truth. Historically, this organic and paid data lived in separate silos across different platforms, APIs and endpoints; and was certainly never meant to be aggregated, sumed and/or blended together.

In the quest to find more efficient ways to drive insights for their clients, ListenFirst adopted X’s v2 endpoints to streamline their translation of what users are talking about on X into their platform. ListenFirst’s team got to work with one clear goal in place: to create cleaner data.

“For us, utilizing v2 is about integration optimization. If there are fewer pieces we have to put together on our site, it makes our operations easier and allows us to scale our offering to even more brands, more content and better insights.” - Jonathan Farb, Chief Product Officer, ListenFirst.

What drove the team to prioritize the adoption of X’s v2 API, and specifically the Tweets lookup endpoint, was the accuracy of the engagement and impressions numbers. By utilizing this endpoint, ListenFirst was able to generate more reliable metrics that were aligned with what their customers saw on native X analytics elsewhere.