The Demandbase Domain API takes a domain parameter as input and returns up to 43 validated firmographic data fields, among which are: 1) industry; 2) revenue; 3) isp (t/f); 4) address; 5) lat/long; and many more. Frequent uses of the API include: increasing conversion rates by enabling customized messaging, shortcutting user's paths to relevant content, streamlining measurement of responses to online campaigns, and reducing the number of required fields in web forms, increasing form fill rates.
The underpinning services work without cookies or personally identifiable identification (PII), instead relying on several proprietary methods to reliably build on the fundamental requirement to connect to the Internet, an IP address, to map a business up, across, and through the API.
The API outputs either XML or JSON data formats.
Of the many APIs we published this week, eight were highlighted on the blog by our team of writers. In this post, we’ll shine a spotlight on those eight, which included the LambdaLabs Face API for facial detection, which takes up where the Face.com API left off. We said it's a great first release, but needs to add face recognition in addition to detection. That feature is coming soon. Read more in the LambdaLabs Face API post or check out the LambdaLabs Face API profile.
Personalization tools have long existed allowing marketers to custom tailor online marketing to consumers. However, business to business marketing has eluded personalization tools until Demandbase created its Real-time Identification service: a "service [that] bridges the gap between known and anonymous web visitors by identifying and segmenting the companies visiting a website, and providing detailed, targetable business attributes in real-time." Now, Demandbase is making its Real-time Identification platform available to third party developers via an the Demandbase API.