There are two reasons this can happen, and both come down to how Auware attributes orders.
First, Auware only attributes an order to an Auware campaign if the visitor came directly from an Auware landing page URL. During testing, it is very common to mix navigation between your Shopify store and your Auware pages. For example, if you visit your Shopify store first, click around on a Collections page, and then go to your Auware landing page in the same browser session, that order will be counted as a regular Shopify order, not an Auware order. Even if you open the Auware landing page in a new browser tab while your store is still open in another, Shopify will treat the session as store-driven, not Auware-driven. Auware is purposely conservative about attribution because we want your campaign reporting to be honest and transparent. If we cannot definitively trace an order back to an Auware landing page click, we do not claim credit for it.
The second possible reason is that your browser may have had a script blocker or privacy extension enabled. Auware uses a Shopify Web Pixel Extension to collect visitor and order activity. A Web Pixel Extension is Shopify’s official, privacy-compliant method for apps like Auware to subscribe to store events such as page views, add-to-cart actions, and completed checkouts. When a checkout is completed, Shopify fires a standardized event that includes non-personal information like the session ID, order ID, campaign context, and store metadata. Auware’s analytics system listens for that event through Shopify’s pixel API. This allows your Auware dashboard to display accurate reporting on visits, conversions, average order value, and other key campaign metrics.
However, that pixel runs entirely in the browser - it is client-side code. If a browser or browser extension blocks third-party scripts or prevents analytics pixels from running, the event will never reach Auware. The order itself still goes through Shopify successfully, but Auware will not know it happened, so it will not appear in your Auware dashboard. Script blocking extensions, certain privacy-focused browsers, or even strict corporate security policies can prevent these tracking pixels from executing. That’s why orders created manually or during internal testing sometimes do not show up in reporting.
To summarize:
If you want to test attribution, always start a fresh browser session, paste your Auware landing page URL directly into the address bar, and complete checkout without browsing your Shopify store first. And make sure no script blockers or privacy filters are active during the test. When a real customer comes through one of your paid ads and lands on your Auware page, their visit and purchase will be correctly attributed, provided their browser allows Shopify’s native pixel to function normally.
Auware’s data integrity depends on clear, first-party attribution through Shopify’s infrastructure, which is both accurate and privacy-respectful.