Analytics and Risk Detection

The Sylius Adyen Plugin includes native support for Adyen’s analytics, data tracking, and the RevenueProtect risk engine. Together, these features help improve fraud detection, optimize conversion rates, and enhance the shopper experience without requiring any additional configuration.


Enabled by default

All necessary JavaScript snippets and data-tracking mechanisms are pre-configured and enabled out of the box.

This means:

  • You don’t need to manually add any Adyen scripts.

  • RevenueProtect and analytics features are automatically active for all Adyen payment methods.

  • Both device fingerprinting and behavioral analytics are collected in the background.


How it works during checkout?

When a customer checks out using an Adyen payment method:

  1. The plugin injects Adyen's JavaScript SDK into the checkout flow.

  2. This script collects browser, device, session, and behavioral data.

  3. The plugin also sends order data, such as:

    • Basket contents (product names, prices, quantities)

    • Customer details (name, email)

    • Billing and shipping addresses

  4. This data is sent along with the payment request to Adyen.

  5. Adyen processes the data through:

    • Device fingerprinting

    • Machine learning algorithms

    • Static or dynamic risk rules


What Adyen does with this data?

Adyen uses this combined data to:

  • Detect fraud attempts and suspicious or bot behavior

  • Trigger block/trust lists based on risk profiles

  • Evaluate global fraud trends to inform real-time decisions

  • Benchmark and optimize checkout performance

  • Provide analytics and diagnostics in the Adyen dashboard

These tools enhance RevenueProtect, Adyen’s built-in risk management system.


Custom Frontend and Template Overrides

⚠️ If you use a custom frontend (e.g., headless) or override Sylius checkout templates:

  • You must ensure Adyen’s JavaScript SDK is still loaded and initialized.

  • Failing to do so will:

    • Prevent device/session data collection

    • Reduce fraud detection effectiveness

    • Potentially cause incomplete or rejected payment requests

Verify that the script is included and executed before the payment is initiated.


Last updated

Was this helpful?