How MIQAS works: the full loop

MIQAS runs one loop, continuously: capture, attribute, report, feed back.

Capture

The pixel on your site records each visit in real time, together with the signals the ad platforms attach to their links: Meta's click ID, TikTok's click ID, your UTM labels. Your store or ordering app sends each order to MIQAS the moment it happens.

Attribute

MIQAS joins those two streams. When the visitor who clicked your Meta ad on Tuesday buys on Thursday, the order is credited to that campaign. Orders with no ad trail are honestly labeled direct.

Report

The dashboard updates continuously: revenue by campaign, CPA, ROAS, funnel steps, and every number in your workspace currency and timezone.

Feed back

MIQAS sends every meaningful event to the ad platforms server-side, through Meta's Conversions API and its equivalents: page views, product views, adds to cart, checkouts, purchases, each under the platform's standard event name with strong identity signals attached. The platforms use this to report accurately and to optimize ad delivery toward people who actually buy. Ad blockers and browser privacy features cannot intercept it, because it never runs in the browser.