Owala is paying to show a privacy notice before the product
A current Disney Princess Collection ad sends phone shoppers to a screen where the bottle, price, reviews, and Add to cart button are all hidden. The same page also stops some of its own paid-campaign reporting.
Owner brief
We followed a current Owala ad to the exact Disney Princess Collection page. Three leaks stood out. The first two can waste paid attention and blur the numbers used to judge it. The third adds more delay on phones.
We found five current public ads. Three point to US product pages and two to the UK store. The audited ad leads to the Disney Princess Collection. Its record did not include enough ad copy for a detailed promise-to-page comparison, so we did not invent one.
Funnel depth tested: current ad to the Disney Princess Collection page on desktop and mobile. The product, price, options, reviews, and Add to cart control displayed. We did not add a bottle, open the cart or checkout, enter personal details, attempt payment, or test an order email.
Where paid attention is leaking
The privacy panel gets the first screen. The product gets none of it.
On a fresh phone visit, the Privacy & Cookies panel fills the screen below the header. The bottle, $34.99 price, reviews, options, and Add to cart button are out of sight.
This shopper has already responded to an ad. Making them read a long privacy explanation before they can even see the bottle adds a hard stop at the most expensive moment.
Keep the required choices, but make the first notice compact. Let shoppers see the product while they decide. Test the fresh mobile visit, not just a returning browser where consent was already saved.
FunnelWatch should reopen this paid route as a first-time phone visitor after every privacy, theme, and campaign change. The page can remain live while a consent update quietly covers the sale.
The page blocks some of its own ad reporting
The campaign details survived the trip to the product page. But the page refused several requests meant to report the visit and product view back to the advertising system.
That does not prove every sale is misreported. It does mean part of the paid journey is being stopped in the browser. Campaigns can look weaker than they are, and the team may make budget decisions from an incomplete picture.
Review the page's security rules against the reporting destinations the site is trying to use. Then repeat a fresh page-view and product-view check under each consent choice. Do not loosen the rules broadly; allow only the destinations the business has approved.
FunnelWatch should check these requests after every tag, consent, checkout, or security-policy release. A reporting break can run for days without changing anything a shopper sees.
Phone shoppers wait almost four seconds for the product
In our mobile check, the main product content appeared after 3.75 seconds. Desktop showed it in 1.00 second.
That delay comes before the shopper can judge the bottle. Paired with the full-screen privacy panel, it makes a paid phone visit feel slower and more obstructed than the desktop version.
Start with the images and page work needed before the first product view. Send smaller files to phones. Delay anything below the first screen until the bottle, price, and buying action are ready.
FunnelWatch should time this exact paid page after every image, theme, app, and merchandising release. Product pages often get slower one small change at a time.
What the page should reveal first
Once the page is visible, the buying path is clear. Owala shows the Disney Princess bottle, $34.99 price, color choices, review count, and Add to cart button together.
Fix these first
- Shrink the first-visit privacy panel so the product stays visible on phones.
- Repair the blocked visit and product-view reporting requests.
- Get the main mobile product content on screen in under three seconds.
The product page underneath is strong. The risk sits in the layers around it: privacy controls, reporting rules, page code, and heavier media. Those layers change often. FunnelWatch keeps checking the paid route so a quiet leak is caught before more budget runs through it.