#advertising

Digital-marketing metrics maths as an API, computed locally and deterministically. The ads endpoint computes campaign KPIs from any two of the spend, impressions, clicks and conversions: the CPM (cost per thousand impressions), the CPC (cost per click), the CTR (click-through rate), the conversion rate and the CPA (cost per acquisition). The roas endpoint computes the return on ad spend, ROAS = revenue ÷ spend, the ROI percentage and the gross profit, and — given a gross margin — the break-even ROAS of 1 ÷ margin. The ltv endpoint computes the customer lifetime value, average order value × purchase frequency × lifespan × gross margin, and, with the marketing spend and number of new customers, the customer acquisition cost, the all-important LTV:CAC ratio and the CAC payback period in months. Everything is computed locally and deterministically, so it is instant and private. Ideal for marketing, advertising, e-commerce and growth app developers, campaign dashboards and reporting tools, and agency calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is marketing-metrics maths; for percentage maths use a percentage API and for currency conversion use a currency API.

api.oanor.com/marketing-api

Marketing and advertising metrics as an API — the everyday campaign maths, computed locally and deterministically and entirely currency-agnostic. The funnel endpoint takes any of impressions, clicks, conversions, spend and revenue and computes every metric the inputs allow: click-through rate (CTR), cost per click (CPC), cost per mille (CPM), conversion rate, cost per acquisition (CPA), average order value, return on ad spend (ROAS), return on investment (ROI) and profit — anything not derivable is returned as null rather than guessed. The roas endpoint focuses on profitability: ROAS, ROI and profit, and — given a gross margin — the break-even ROAS and gross profit, with a profitable flag. The target endpoint reverse-plans a campaign: from a conversion or revenue goal and your known rates it works out the required clicks, impressions and budget and the expected revenue and ROAS. Everything is computed locally and deterministically, so it is instant and private. Rates such as conversion_rate and ctr are given as fractions (0.05 = 5%). Ideal for marketing dashboards and reporting, media-buying and bid tools, agency and campaign planners, and e-commerce analytics. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is advertising-metric maths; for loan and investment maths use a finance-calculator API.

api.oanor.com/admetrics-api

Fetch and evaluate any publisher's ads.txt / app-ads.txt — the IAB authorized-digital-sellers standard. Pass a domain and the check endpoint fetches its ads.txt server-side, then returns every seller record parsed into its fields — advertising system, the publisher's seller/account id, the DIRECT or RESELLER relationship and the optional certification-authority id (TAG-ID) — alongside counts (direct, reseller, distinct ad systems) and the declared variables OWNERDOMAIN, MANAGERDOMAIN, CONTACT and SUBDOMAINS. The verify endpoint answers the one question programmatic-advertising integrations actually ask: is this advertising system, with this publisher id, authorized to sell this domain's inventory? — returning an authorized boolean and the matching records. A missing file is reported as found:false (not an error), and soft-404 HTML pages are detected and rejected so you never parse a "page not found" as records. The request is made server-side and private or internal targets are refused (SSRF-guarded). Built for ad-tech supply-chain verification, SSP/DSP onboarding checks, anti-fraud and inventory audits. An ads.txt seller-authorization checker — distinct from the security-contact file reader (securitytxt), the robots.txt crawlability evaluator (robots) and the sitemap parser (sitemap). No upstream key, no cache.

api.oanor.com/adstxt-api