Botman

Botman’s implementation process is designed to be fast, flexible, and developer-friendly—especially for ad networks and marketers looking to combat invalid traffic (IVT). Here's a breakdown of what you can expect:

Typical Implementation Process

1. Onboarding & Setup
   • Botman offers a fast and easy onboarding process, often requiring minimal technical effort.

   • You can choose between passthrough mode (monitoring traffic without blocking) or filter & drop mode (actively blocking suspicious traffic).

2. Integration Options
   • Use Botman’s secure REST or JavaScript API to integrate traffic scoring into your internal systems.

   • It supports a wide range of inventory types: Prebid, oRTB, Postbid, CTV, XML Push/Pop, In-App, Desktop, Mobile, and Native.

3. Configuration & Customization
   • Set risk thresholds per traffic source.
   • Customize traps from over 60+ threat categories, including click spam, fake devices, proxy traffic, and domain spoofing.

   • Assign quality scores to each click and monitor traffic sources via a leaderboard.

4. Real-Time Monitoring
   • Access dashboards to track IVT, conversion-level fraud, and traffic quality.

   • Download actionable data to optimize campaigns and improve Return on Ad Spend (RoAS).

5. Ongoing Optimization
   • Botman’s auto-optimization tools help refine supply sources over time.

   • You can adjust traps and scoring logic with support from Botman’s team.

Implementation Timeline

• Initial setup: Can be completed in a few hours to a couple of days, depending on the complexity of your traffic sources and integration needs.

• Full optimization: Typically takes a few weeks to fine-tune scoring, traps, and traffic source configurations.

Botman offers a highly flexible platform that can be tailored to fit specific business needs across various dimensions:

• Custom Scoring Logic: You can define your own rules and thresholds based on over 60+ fraud traps, including:
  • Click spam
  • Fake devices/emulators
  • Proxy traffic
  • Domain/app spoofing
  • Geo mismatch
  • Data center traffic

  • XML push/pop anomalies

• Traffic Source Segmentation: Businesses can segment traffic by source, geography, device type, or campaign, and apply different filtering rules to each.

• Real-Time API Integration: Botman supports REST and JavaScript APIs, allowing developers to embed fraud detection directly into their ad stack or bidding logic.

• Dashboard Customization: The reporting interface can be tailored to show KPIs that matter most to your business—like IVT rates, partner performance, or campaign RoAS.

• Zero-Code Deployment: For teams without engineering resources, Botman offers a no-code passthrough mode to monitor traffic without disrupting operations.

• Platform Compatibility: Works across Prebid, oRTB, Postbid, CTV, XML, In-App, Desktop, and Mobile environments.

• Support Charges: Standard support appears to be included; premium support may incur extra fees depending on the plan.

• Free Trial: Not available; Botman does not offer a trial period.

• Pricing Model: Quotation-based; tailored to your traffic volume, integration needs, and feature requirements.

Botman provides a variety of onboarding resources to help new users get started smoothly:

• Video Tutorials: Step-by-step instructional videos guide users through setup, integration, and traffic monitoring.

• Technical Documentation: Comprehensive guides cover installation, API usage, message handling, and driver configuration.

• Developer Community: Users can engage with an active developer forum and GitHub repositories to exchange ideas and troubleshoot.

• No-Code Options: For non-technical teams, Botman offers a zero-code passthrough mode to monitor traffic without needing engineering support.

Botman emphasizes strong data protection through several key practices:

• Industry Affiliation: As a member of a recognized data security council, Botman aligns with best practices in cybersecurity and privacy.

• Traffic Filtering: Its core functionality includes detecting and blocking fraudulent traffic, which helps safeguard user data from malicious actors.

• Secure API Integration: All data exchanges occur through secure REST or JavaScript APIs to minimize vulnerabilities.

• User-Controlled Risk Thresholds: Clients can define their own filtering rules, giving them control over how data is handled and protected.

Botman maintains a structured and developer-friendly update cycle:

• Major Releases: Significant upgrades (like the jump from version 1.5 to 2.0) introduce new features such as modular driver support and improved middleware.

• Driver Management: Messaging service drivers are maintained separately, allowing for faster updates and bug fixes.

• Manual Driver Loading: Users have control over which services are active by manually loading drivers as needed.

• Middleware Enhancements: The middleware system has been redesigned for greater flexibility, especially for integrations with third-party platforms.

• Client-Controlled Data: Botman’s platform is designed to let clients define their own traffic filters, scoring logic, and reporting thresholds—implying that businesses retain control over how their data is used and interpreted.

• Custom Scoring & Traps: Since users can configure over 60+ fraud traps and customize scoring logic, it’s likely that the data generated from these configurations remains accessible and exportable by the client.

• Portability: Botman provides real-time dashboards and downloadable reports, which supports data portability. Clients can extract insights, export traffic scores, and use them across other platforms or analytics tools.

• Security Alignment: As a member of the Data Security Council of India (DSCI), Botman aligns with best practices in data privacy and ethical data handling, which typically includes respecting user ownership and offering transparency in data usage.

Botman is built to accommodate dynamic traffic environments, and its terms for scaling are flexible:

• Custom Pricing Model: Botman uses a quotation-based pricing structure, which means businesses can adjust their plan based on traffic volume, integration complexity, and feature requirements.

• Passthrough vs. Filter Mode: Clients can start in monitoring mode (passthrough) and shift to active blocking (filter & drop) as their needs evolve—without reengineering their setup.

• Modular Integration: Whether you're scaling across Prebid, oRTB, CTV, XML, or mobile environments, Botman supports plug-and-play integration with minimal disruption.

• Auto-Optimization Features: As traffic grows, Botman’s auto-optimization tools help maintain performance without manual intervention.

• Support for Custom Traps: Businesses can request new fraud traps or scoring logic as their threat landscape changes, allowing for vertical or horizontal scaling.

• Auto-Renewal Clauses: Contracts may include automatic renewal provisions. These typically renew the agreement unless canceled within a specific notice period—often 30 to 60 days before the renewal date.

• Affirmative Consent: Updated regulations require vendors to obtain clear, affirmative consent for auto-renewals. This usually involves a checkbox, initials, or signature placed directly next to the renewal clause.

• Renewal Notifications: Vendors are expected to send advance notice before a renewal takes effect. This notice should include:
  • The renewal date
  • The final date to cancel

  • Clear instructions for cancellation

• Cancellation Process:
  • Must be straightforward and accessible—ideally through the same method used to sign up (such as an online portal).
  • May involve email, web forms, or written notice.

  • Businesses are advised to retain proof of cancellation and consent for up to three years.

• Legal Protections:
  • If proper notice or consent is not provided, clients may be entitled to cancel without penalty.
  • Local laws may offer additional protections depending on your region.

• Data Security Council Membership: Botman is affiliated with a recognized cybersecurity council, indicating a commitment to secure data handling and privacy best practices.

• GDPR (General Data Protection Regulation): If serving clients in the European Union, Botman would be expected to comply with GDPR requirements such as lawful data processing, user consent, and data access rights.

• CCPA (California Consumer Privacy Act): For U.S.-based clients, especially in California, Botman would need to meet CCPA standards including transparency in data collection and opt-out mechanisms.

• API Security Best Practices: Botman’s use of secure REST and JavaScript APIs suggests adherence to encryption protocols, token-based authentication, and secure data transmission.

• Custom Risk Controls: Clients can define their own fraud filters and scoring logic, which supports internal compliance and governance frameworks.