Aeion Ads for Retail Media Networks

It's how the loop closes. The conversion tracking, order metadata, and ROAS reporting are most valuable when your catalog and orders live in Aeion Commerce, because the ad click and the order it drives sit in the same database. You can still run direct-sold campaigns and conversion pixels without Commerce, but you lose the native catalog + order context.

A conversion pixel or a server-side callback fires on the event you care about (purchase, add-to-cart, signup, lead). Aeion attributes it post-click, post-view, or direct, within a configurable window (default 24 hours), and stores the originating impression ID plus order/product info in the conversion record. That feeds CPA billing and ROAS reporting.

Yes — there's a self-serve advertiser portal where advertisers manage creatives, track delivery, and pull invoices, which cuts the back-and-forth with your ad-ops team. You keep control of the review workflow: creatives are pending until approved.

Line-item targeting (zone, geography, device, daypart, URL-contains / URL-excludes) plus a creative review queue. All configured targeting rules must match for a line item to be eligible, and nothing serves until a creative is approved.

No. Placements are sold as direct campaigns with pacing, not bid on per impression. Direct-sold campaigns get priority in the waterfall; where several match, weighted creative rotation and budget pacing decide the split. There's no live per-impression bidding among sellers.

It falls through the waterfall to house ads (your own merchandising / promotions) and then a static fallback creative, so a slot is never left blank. You can also connect programmatic networks to fill unsold inventory — see the publisher-yield use case.

Ad slots reserve layout space and lazy-load by default, so they don't cause Cumulative Layout Shift or tank Core Web Vitals — which matters more on a storefront than almost anywhere else.