Retail media product comparison: CitrusAd vs Kevel

What to take away

Build versus buy, stated directly

CitrusAd is the turnkey option and Kevel is the build-it-yourself option, judged on the two suppliers' own descriptions. That verdict concerns delivery model, not measured performance.

CitrusAd's retailer material describes sponsored products together with retailer control of the ad request and the display decision. Kevel's retail media guide describes sponsored listings returned as content that the implementing property renders itself.

The two products describe different reporting workflows, but this comparison has not tested either one. For a fair trial, record who renders each placement and who logs each event. Requests, returned responses, rendered placements and viewable impressions then become distinct units that must not be merged into one number.

Limits of this comparison: neither page publishes a price, a UK contracting entity, a service level, a named UK retailer or a tested deployment result. The table records capability differences, not performance findings.

Example: one sponsored-product slot run through both products

What each product suits, read from documentation alone

CitrusAd suits a retailer with no ad tech team, because screens, auction logic and reporting arrive as one package. Expect less control over rendering detail and export format. The contract workstreams still need separate agreement on claims and consent.

Kevel suits a retailer or agency with engineering capacity, which keeps control of rendering, latency and the data model. Expect to fund and maintain the interface and reporting yourself.

These are expectations read from supplier documentation. No tested build or UK deployment was inspected, so treat them as items to verify in a paid trial.

UK checks that sit outside the product choice

Substantiation rules apply to any objective claim you publish about either product, so the evidence behind a comparison or case study has to exist. The CAP Code's substantiation requirements set that test.

Consent and lawful basis rules apply to any shopper data used in targeting or measurement. ICO direct marketing guidance covers the consent side; the Data Protection Act 2018 and UK GDPR sit behind it. Where ad tech uses cookies or similar technologies, the Privacy and Electronic Communications (EC Directive) Regulations 2003 (PECR) may also apply.

ONS retail industry statistics give UK trading context for sizing the opportunity, and they support no supplier performance claim. Use them for scale, not for a verdict.

Checklist before you commit

Six checks should be completed before this comparison informs a purchase or a published verdict.

Common questions

Which of CitrusAd and Kevel should an England retailer choose?

Turnkey CitrusAd for speed without engineers, and API-first Kevel for control with an in-house stack. Neither choice is currently supported by published pricing or a named UK deployment.

What single assignment is being compared?

One sponsored-product slot on one UK retail site, with the same catalogue, placement, permission conditions, order window and reporting period applied to both.

What would change the verdict?

A published price, a named UK retailer reference, or a paid trial showing one product's rendering and reporting inside your own catalogue. Any of those could overturn the build versus buy split.

Where do England rules bite?

Advertising claims, consent and lawful basis sit outside the product choice and apply to both. The CAP Code sets advertising standards and is administered by the ASA; the ICO oversees data protection and PECR.