Velora — Lead & Ad Analytics

1.0.24

• Each sale now records whether the shopper allowed advertising, separately from whether they allowed measurement. Velora may count a sale on measurement consent alone, but sending it back to an ad platform is a different purpose that needs advertising consent, and a shopper can allow one and refuse the other. Only sales with advertising consent will ever be sent to Google Ads or Meta.

1.0.23

• An order moved along in the back office is no longer credited to the person moving it. When Velora had not seen an order being placed and a shop manager later marked it paid, the sale was filed under the manager’s own visit — their browsing, their channel. It is now counted as a sale Velora did not see, which is what it is.
• The count of sales Velora could not see no longer flickers. It was read through WooCommerce’s order search, which on shops that trim plugins per request sometimes came back empty — and an empty answer was reported as “none”, wiping the real figure until the next report restored it. The count is now read straight from the order tables, and when they cannot be read nothing is reported instead of a zero.
• The consent banner is named correctly. “GDPR Cookies” is a renamed copy of an older banner plugin and was reported under the original’s name; it is now called by its own. How consent is read does not change.
• The shop’s timezone is reported, so “Today” on the dashboard begins at the shop’s midnight rather than the reader’s.
• A returning customer who types their Gmail address differently — with dots, with a +tag, or as googlemail.com — is recognised as the same customer. The address sent to ad platforms for matching is unchanged; the recognition uses a second, separate fingerprint.

1.0.22

• The page a visitor arrives on is measured even when they accept the cookie banner only after it has loaded. Velora used to decide once, as the page was drawn, whether it was allowed to count — and on a visitor’s first page the banner has never been answered, so the answer was always no. The visitor accepted a moment later and that page, the one an ad points at and the only one carrying the campaign it came from, was never recorded. On the shop this was found on, more than half of visitors lost their arrival page this way, including a paid Facebook click that went on to buy and was credited to nothing. Velora now notices when the banner is accepted and records the arrival page then, with the time the visitor actually arrived. Nothing is recorded or stored before the visitor agrees.
• A visitor who accepts the banner only on their second page no longer loses the ad that brought them. The browser still reports the page they came from, campaign and click id included, and Velora now takes the campaign from there when the page itself has none.

1.0.21

• Orders placed on shops that switch plugins off per page are measured again. Several speed plugins decide, request by request, which plugins are allowed to run, and the checkout is one of the requests they trim hardest. Where Velora was not on that list, the order was created in a request Velora never saw: it was met hours later, when someone in the back office marked it done, by which time the shopper was long gone and the sale was filed as unmeasured. On the shop this was found on, thirty-one hours of trading produced twenty orders and not one measurement. Velora now keeps itself loaded on those requests. Nothing to configure; if the site does not allow it, the Velora screen says so instead of failing quietly.
• Product views are no longer counted when no one is looking at a product. The view was recorded wherever the product template was drawn, including quick-view pop-ups and the extras shown beside a cart — so one shopper sitting on the checkout page could add a dozen product views without opening a single product. Measured on a live shop, two product views in three were of this kind, which made the first step of the funnel — the step every later one is compared against — about three times too big. Only a real product page counts now. Past figures are not rewritten; from the update onward the funnel narrows to the truth.

1.0.20

• Product views on translated pages are counted again. Translation plugins that add a language to the address — /cs/, /de/ and so on, as Weglot and similar services do — put that segment where WordPress does not look, so a product page viewed in another language was not recognised as a product at all. On a cached shop that meant no product view and, from the browser’s side, no add-to-cart either, for every visitor browsing in a translated language: they fell out of the funnel at its first step even when they went on to buy. The product is now found behind the language segment. Nothing needs configuring, and a page that is not a product still records nothing.
• The count of orders Velora could not measure now counts sales, not attempts. An order was counted the moment it was placed, which on a card checkout is before the payment has gone through — so a declined card, a closed bank window or an abandoned payment page stayed in the figure for good, and the account could report far more unmeasured orders than the shop actually took. The count is now worked out from the orders themselves: an order is included once it is paid, and drops out again if it is cancelled, refunded or its payment fails. Figures already reported for the last seven days correct themselves after the update.

1.0.19

• Form submissions and contact clicks now follow the same rule as orders: a conversion Velora did not watch is not recorded. Until now a submission from a visitor with no tracking cookie still produced a lead — one with no journey behind it, counted as a conversion but belonging to no traffic source. That flattered the numbers. Expect fewer leads than before on a site behind a consent banner, and every one of them traceable to the visit that produced it.