Confirm the installation
Visit an actual campaign landing page, check that tracking is present and confirm the intended advertising account is connected. Include any separate domains used during checkout or enquiry submission.
Check the setup stepsUse your campaign questions to plan a trial: check installation, inspect suspicious visits and measure the enquiries or orders that matter to your business.
These examples show what different teams can investigate. They describe practical checks, rather than measured customer results.
Start with a client account whose campaign history you can explain. Confirm account access, inspect sample visits and agree which information the client needs in a report.
Compare paid traffic with suitable consultation requests. Repeated clicks deserve investigation, but a poor enquiry may also reflect location targeting, service fit or an unanswered call.
Check that purchase events are recorded correctly before judging a campaign. Compare traffic during similar promotions and keep returns, cancellations and stock changes in the picture.
Keep a record of the starting position so you can explain what changed.
Visit an actual campaign landing page, check that tracking is present and confirm the intended advertising account is connected. Include any separate domains used during checkout or enquiry submission.
Check the setup stepsRead the reason attached to a flag and compare it with the visitor history you have. A pattern across several signals is more useful than treating one repeated visit as proof of fraud.
Explore the reporting featuresChoose the outcome your team can verify, such as a booked consultation or paid order. Keep the starting figures, dates and campaign changes alongside any protection adjustments.
Use an investigation exampleDifferent teams need different outcomes: qualified enquiries, completed orders, attended demos or clear client reporting.
Protect high-value legal keywords from competitor fraud.
Improve conversion rates by filtering bot traffic.
Protect patient acquisition campaigns from fraud.
Maximize lead quality from property listings.
Get clean data for accurate funnel analysis.
Protect client budgets across all accounts.
Choose an industry to see what to inspect and which business outcome to track.
Check whether unusual paid visits also create carts, orders or returned purchases. Compare similar products and promotions so a change in sales mix does not look like a change in traffic quality.
See investigation examples →7-Day Free Trial
Start your 7-day trial with a clear question and a record of your current campaign results.
Official Google Ads, Meta and Microsoft Advertising API integrations — no charge during your 7-day free trial.
Cancel anytime. No long-term contracts.
Look for experiences from businesses with needs similar to yours. Comments about setup, reports and support can help you decide what to test. Check that the review refers to a feature or plan still offered today.
Turn useful feedback into questions for your own trial. If reports matter to you, try explaining one to a colleague. If setup is the concern, test the landing pages and account connections you actually plan to use.
Look for reviews that describe something you expect to do yourself: installing the tracker, finding a flagged visit, connecting an account or asking support for help. A review from an agency managing several clients may be especially useful to another agency. A shop owner running one website may have different priorities.
Check when the review was written and whether it refers to the plan or feature you are considering now. Note recurring questions, then try those tasks during your own evaluation. If several reviewers discuss the reports, open a report and see whether you can understand it without help. If support matters to your team, bring a real setup question to the conversation. Customer feedback can help you judge the day-to-day experience, while your own campaign data will be needed to assess results. Keep those two questions separate when deciding whether the service suits your business.
Make a short list of what you need to protect: advertising platforms, campaign types, websites and normal monthly traffic. Add the reporting you need and who will check it. Ask each provider which actions it supports for that setup. If you rely on a particular campaign type, confirm it explicitly instead of assuming every integration offers the same controls.
During a trial or demonstration, open a flagged visit and ask why it was flagged. Check what action followed and how you would correct a mistake. Try a reporting task you actually need, such as explaining an issue to a client or finding the campaign behind repeated visits. Finally, compare the bill for the same websites, usage and billing period. A useful choice should fit the work your team does each week, including setup, support and the time needed to investigate a questionable result.
Pick one campaign you understand well. Install MyClickShield on its landing pages, connect the appropriate account and confirm that a test visit is recorded. Open a few traffic records to see whether you understand the information shown. Check the available response to a suspicious visit and make sure ordinary customers can still submit a form or complete checkout.
Try the tasks you will need after the trial: finding an affected campaign, reviewing a flag and explaining a result to a colleague or client. Write down questions for support as they arise. Before the trial ends, check the selected plan, when charging starts and how cancellation works. A quiet campaign may not produce enough sales in one week to judge a financial improvement. In that case, use the trial to assess installation, reporting and ease of use, and be specific about what you still need to learn.
Look for a clear starting point when reading a case study: the business, advertising channels, dates and problem being addressed. Check what changed and which result was measured. Fewer suspicious visits, lower advertising charges and more qualified sales describe different outcomes. The report should make clear which one actually improved.
Ask whether the business also changed its ads, budget, offer or landing page during the same period. Those changes may affect the result. If you want to run your own comparison, save the original campaign report and note each adjustment as it happens. Choose similar days and allow for the time customers normally take to buy. Use a relevant case study to prepare questions for your trial, especially about setup and reporting. The scenarios and diagrams here explain how to investigate a problem; they are not published customer performance results or a prediction of the saving your account will achieve.
Suppose a campaign suddenly receives more clicks without more enquiries. Before investigating, you only know that costs have risen. Pausing the campaign may stop the spending, but it can also stop genuine customers reaching you. Start by noting the affected dates and checking whether you changed the budget, targeting, offer or landing page around that time.
Next, inspect the traffic source and a few visits from the affected period. Test the enquiry form yourself. If you find a page problem, repair it. If a particular group of visits looks suspicious, review the available protection settings for that campaign and record the change you make. Afterwards, watch both the suspicious activity and genuine enquiries. This before-and-after example shows how to narrow the response. To assess your own result, compare similar days and keep other campaign changes in the record so you can see what helped.
Start with what you were actually charged and the results your business received. A flagged visit does not automatically equal a paid click. Your advertising platform may already have filtered or credited some invalid activity. Check its reporting and billing adjustments before adding up a claimed saving from the same visits.
For a practical comparison, look at spend per qualified enquiry or paid order before and after the change. Include the subscription fee and the time you spend reviewing traffic. For example, if ten flagged visits are multiplied by a $4 average click price, the resulting $40 is an estimate of possible exposure, not proof of a $40 refund. Keep estimates labelled and explain the calculation. A useful review should show whether your account is producing better-quality enquiries or orders for its overall cost, with promotions, bid changes and other adjustments taken into account.
Use a common setup checklist, then adapt the settings to each client. A local emergency service may value answered calls, while an online shop needs completed orders. Agree what a useful result means before reporting on improvements. Confirm who owns each advertising account, who can connect it and who approves changes to campaigns or exclusions.
Choose one client for the first installation and test its main customer journey. Check the traffic records and explain an example flag to the account manager who will handle it. For the next client, review the settings again rather than copying them without context. Keep a note of any exceptions and the reason they exist. In client reports, show the affected campaign, what you found, what you changed and what you will check next. This gives the client a clear account of the work and helps a colleague take over without rebuilding the history from emails.
Start your report with the campaign, dates and question you investigated. For example: enquiries fell after a new placement started sending traffic. Show the change in spend and qualified enquiries, then add a few visits that explain why you investigated that source. Include the action taken and any question that still needs an answer.
If the report goes to a client, explain unfamiliar terms the first time you use them. They should be able to see what happened without interpreting a list of IP addresses. Keep the detailed records available for the person checking the account. Where a change has been made, say when you will review its effect and what you will compare. A short report with a specific follow-up is easier to use in a campaign meeting than a long list of blocked visits with no explanation of how customers or advertising costs were affected.
A real customer might browse through a company network, use a VPN or switch from Wi-Fi to mobile data. Several people can also share one public IP address. These situations matter when you review repeated visits or a network-based flag. If you tighten a rule, check a sample of the affected visits and confirm that ordinary enquiries or purchases still work.
When someone reports a problem, ask which page they tried to use and approximately when it happened. Compare that information with the visit record before changing a broad account setting. Check whether an exclusion or website rule caused the problem, then adjust the relevant setting if needed. Keep a note explaining any exception so the next person managing the account understands it. Include staff, your agency and tools your website relies on in your checks, especially after installing protection or changing a site's forms and checkout.
Tell us which website and advertising platform are affected, what you expected to happen and what you saw instead. Include when the issue started and whether anything changed shortly beforehand, such as a new landing page, tag-manager update or account permission. A missing visit, a disconnected account and an unexpected flag need different checks.
For a particular visit, include its approximate time and the relevant record details. For an installation problem, provide the affected page and how the snippet was added. Remove passwords, payment details and unnecessary personal information from screenshots. If support needs more sensitive records, ask how to share them appropriately. When you receive a suggested change, confirm which account or page it applies to and what result to check afterwards. Keeping the conversation tied to one reproducible example usually makes troubleshooting easier than sending a large export without explaining the problem you want solved.