Corma brings Adyntel under IT control: the subscription, its spend and the API key behind your marketing data workflows, with an owner beyond its creator.
The Corma and Adyntel integration makes Adyntel visible to IT and finance, so the subscription, its spend and the API key used by your marketing workflows have an owner beyond the person who signed up. Adyntel is an ad intelligence API: you send a company domain and it tells you whether that company advertises on LinkedIn, Google or Meta, drawing on the platforms' ad libraries, such as the Meta Ad Library, the LinkedIn Ad Library and the Google Ads Transparency Center.
Adyntel is built for automation. API requests are authenticated with an API key and the email of the account, and the key is available in the dashboard at any time. In practice, one person signs up, pastes the key into an enrichment workflow or a script, and the whole marketing team ends up relying on it.
That is a classic shadow IT pattern with an extra risk: the key is a credential. When its owner leaves, the subscription can keep renewing, the key can keep running in tools nobody reviews, and the data workflows break the day the account is closed. And when several teams buy their own plans, the company pays more than once for the same lookups.
Through a native API integration where Adyntel allows it, or through Corma's browser-based agents, which work in the Adyntel dashboard the way the account owner would.
Adyntel's pricing is expressed in credits, sold through monthly plans or pay as you go. The figure to follow is credit consumption, while Corma tracks the Adyntel plan and its cost with the rest of your SaaS spend.
In France, on AWS infrastructure, with encryption in transit and at rest. Corma is ISO/IEC 27001:2022 certified and only requests the permissions it needs.
Want to know which API tools your teams pay for? Book a Corma demo.
Check out other integrations that could help you on managing your software licences and accesses!