Protecting an online store’s ads: where the money goes
Contents
Share
A store’s money in Direct is not lost only where traffic has been recognised as invalid. Spend on invalid traffic is returned to the shared account balance — and that is what was already recognised, not an estimate of the remainder. Real shoppers with no interest in the offer are not removed by the filter. Repeat conversions in different visits, a repeat of the Thank-you page, a wrong contact, untargeted fields and a form filled for a reward are not invalid traffic.
Click fraud in a store is easy to see in an abandoned cart. A cart with no interest is not that layer. Below is the till: what has already come back, what stays in spend on a live bounce, and what sales calls scrap while the account still counts an ordinary conversion.
What the till has already received back
The refund to the shared account closes spend on invalid traffic that was recognised. You cannot read that sum as “how much the store is still losing to bots”: the refund does not measure the remainder. How a refund works is a separate topic. Here it is enough not to add the refund and abandoned carts into one loss.
Invalid clicks explain why not every odd session is already in this refund. Until there is a recognition, the click is in spend.
A live person the product did not fit
A real user with no interest in the offer is not invalid traffic and is not removed. In a store that is a person who opened the card, saw the price or the delivery time and left. Their click stays. Protecting the ads here means the offer, stock and price, not an expectation that Direct will remove those visits.
Who clicks ads, and why is wider than this exit. An exit because of price should not be written down as the motive “they are wrecking the store” until the traffic is recognised as invalid.
Five store cases that are not account fraud
The help text lists what else is not an invalid conversion:
repeat conversions in different visits — a person ordered, came back and the conversion repeated;
a repeat opening of the Thank-you page — a typical gesture after payment, not a second fraud;
a wrong contact — a bad phone on the order;
untargeted fields — junk in the address, the wrong note;
a form filled for a reward — a bonus, a promo code, a gift for a lead.
Sales may cancel such an order. Direct does not have to treat the conversion as invalid because of that. Click fraud and sklikivanie do not move an order cancellation into a refund on the shared account by themselves.
A store week, in order
Write down the refund of invalid traffic to the shared account. Do not put it into “we are still losing”.
Separate visits by people with no interest: price, delivery, the wrong product. The filter will not take them.
Mark orders with a bad contact, junk in the fields and a bonus motive as sales scrap, not as an invalid conversion.
Do not add a repeat Thank-you and a repeat conversion in another visit as a double fraud charge.
Do not name the remainder of spend, which fell into neither the refund nor these five cases, as a percentage from your head. It is not inside these boundaries.
Do not promise yourself that cancelling an order in the CRM will return the click. The refund to the account is tied to invalid traffic that was recognised.
A week as an example
A teaching example.
During the week a sum for invalid traffic already recognised came back to the shared account. It goes on the line “returned”, not on the line “warehouse scrap”.
Two hundred visits reached the delivery price and left without a cart. These are live people with no interest. They are not in the refund.
Forty orders: ten with a wrong phone, five with a placeholder address, five for a promo code in exchange for a lead, ten opened Thank-you again in a new visit, ten are a repeat conversion of another visit by people who already bought. All five groups are on the list of what Direct does not treat as invalid. Cancellations in the store’s books are appropriate. A second refund to the shared account does not follow from those cancellations.
The example does not price the remaining orders with someone else’s percentage. The remainder of spend is not measured by the refund.
Till checklist
The refund of what was recognised sits apart from scrap orders.
Live bounces because of price and delivery were not handed to the filter.
A bad contact was not called an invalid conversion.
Untargeted fields and a bonus form were not either.
A repeat Thank-you did not double the fraud.
A repeat conversion in another visit did not double the fraud.
An order cancellation was not described as an automatic refund to the shared account.
These boundaries are enough for a store not to treat the offer with a “bots” block and not to treat recognised traffic by rebuilding the product card. The card treats interest. The shared account gets back only what was already recognised.
A repeat purchase in a new visit is often good news for a store, and the help text does not turn it into an invalid conversion. If marketing subtracts such repeats from “clean orders”, it subtracts not fraud but a returning customer. That deserves its own line in the report: “repeat visit, ordinary conversion”. Otherwise a director sees a fall in quality where repeat demand grew.
A Thank-you page opened a second time is an ordinary gesture too. The person is checking the order number. Counting every opening as new click fraud inflates fraud out of the confirmation screen. Direct’s list already places this gesture outside invalid traffic.
A bonus for a lead is harsher for sales and just as soft for the account. A form for a reward does not become an invalid conversion. If the promotion brings empty forms, the promotion is what you fix: the bonus condition, not an expectation of the filter. A bad phone from the same promotion stays on the same list. Two items at once are still not a refund to the shared account, until the traffic is recognised as invalid.
A live exit before the cart and an empty form after the cart diverge. In the first case there is no order, and the filter leaves the click because the person is real and the offer did not fit. In the second there is an order, and it may fall into one of the five cases. You cannot add them into “the store drains the same way”: the first has no conversion to recognise as invalid, and the second has a conversion the help text specifically does not treat as invalid.
A week assembled from the checklist looks dull and useful. A refund line. A line of live bounces. Five lines of scrap the account will not take. An empty line “the remainder is not measured by the refund”. That is enough not to buy protection against a symptom that is the price, the delivery or a bonus for a lead.
How to shelve the forty orders
The teaching example is worth shelving, or “forty” becomes one scrap pile again.
Ten bad phones. Sales cannot get through. The status in the store’s books is a cancellation. In Direct this is “a wrong contact”, not an invalid conversion. The report names the shelf that way. It is not added to the refund on the shared account.
Five placeholder addresses. Untargeted fields. The same shelf in the sense of the help text, a separate row in the table, so you can see the promotion or the form that lets junk through. Direct’s filter does not take the row.
Five forms for a promo code. A form for a reward. It is fixed by the promotion’s condition. If the promo code stays, empty forms stay ordinary conversions. That is the store’s choice, not a hole in antifraud.
Ten repeat Thank-you pages. The person checked the order number. The shelf is named “repeat confirmation”. Order money, if there was any, is not doubled by this shelf and does not become fraud.
Ten repeat conversions in another visit. Some of them are a second purchase. The shelf is named “repeat visit”. Subtracting them from revenue punishes repeat demand. Whether to keep them in “clean” orders is an assortment decision. The help text does not treat them as invalid traffic either way.
Two hundred exits from the delivery price sit on another shelf, with no order. There is nothing to cancel. The filter does not remove them, because interest in the offer did not form for a real person.
Beside that, separately, the refund for invalid traffic that was recognised. It is not divided onto these shelves and is not topped up from them. If the refund grows next week, the recognised part grew, not “ten more bad phones”. If the refund is zero, the scrap shelves can still be full: the account did not promise to take them.
What to tell the store director in one table
| Shelf | Example for the week | Where not to put it |
|---|---|---|
| Refund to the shared account | Invalid traffic already recognised | Into form scrap or the remainder |
| Exit from price and delivery | 200 visits with no order | Into Direct’s filter |
| Bad contact | 10 orders | Into an invalid conversion |
| Junk in the fields | 5 orders | The same |
| A form for a bonus | 5 orders | The same |
| Repeat Thank-you | 10 visits | Into double fraud |
| Repeat conversion in another visit | 10, including repeat purchases | Automatically into lost revenue |
The table is a teaching one. Your numbers will differ. The shelf names come from the help text, not from the season. While a shelf has no name, a director will add everything into “click fraud” and demand one remedy. The remedies differ. The offer and delivery are for a live exit. The bonus condition is for a form filled for a reward. A phone check on the form is for a bad contact, and even that does not make the past conversion invalid. The refund to the shared account is only for what was already recognised.
The example deliberately does not calculate the remainder of spend after these shelves. The refund does not measure it, the five cases do not subtract it from the budget, and live bounces stay in the budget. Calling the remainder “the store’s losses to bots” would be a new claim, and it is outside these boundaries. It is calculated separately, from your own clicks, and it is not mixed into the table.
In the second week it is worth checking whether a shelf moved. If bad phones fell after a mask on the form, that is a fix of the form, not “antifraud started working”: Direct did not treat a bad contact as an invalid conversion before either. If repeat purchases grew, revenue grows on the same help-text boundary. If the refund to the shared account did not change, the recognised part did not change, however the scrap shelves jump. Tying these three movements to one cause, “the store is being click-fraudded”, is possible only by breaking the table. While the table is intact, each movement stays on its shelf, and protecting the ads starts from the right shelf, not from a general alarm about the cart.