SAP process automation comparisonPrecisely Automate Evolve
vs. SAP Build Process Automation

Both automate workflow-driven business processes with low-code tools, but they start from different ends: one from cross-application process automation, the other from SAP data. Choose Automate Evolve when the process revolves around SAP data, whether master data or day-to-day transactions; choose SAP Build Process Automation for approval-centric workflows extending S/4HANA, built-in RPA and AI-based document processing.

At a glance

  • Focus: BPA: approvals, RPA, cross-application flows · Evolve: SAP data processes
  • SAP posting: BPA: APIs or bots, built per process · Evolve: native, any transaction
  • Multi-record entry: BPA: form tables or bots · Evolve: SmartTables and Excel
  • AI agents (MCP): BPA: via MCP Gateway in Integration Suite · Evolve: built-in MCP server
  • Deployment: BPA: SAP-managed SaaS on BTP · Evolve: SaaS, hosted or on-premise

Executive summaryProcess automation or SAP data processes

SAP Build Process Automation is SAP’s low-code workflow and automation service on SAP BTP. It combines workflow, request and approval forms, decision tables, RPA bots, document processing and Joule-assisted building, and it runs as SAP-managed SaaS. It is strong for approvals, task automation and cross-application processes, but posting SAP data relies on actions (APIs) or bots that must be configured per object and system, and it leans on other BTP services (Cloud Connector, Integration Suite, SAP Build Apps, SAP Build Work Zone) for connectivity and richer UIs.

Automate Evolve is a no-code/low-code workflow and process automation platform. It also runs processes that do not touch SAP at all, but it is purpose-built for SAP-centric processes on two fronts: master data processes (material, customer, vendor and finance master data, onboarding, product launches) and transactional business and administrative processes such as journal entries and accruals, order management, asset accounting, purchasing and plant maintenance requests. It combines workflow, web forms, Excel (it includes Automate Studio) and deep SAP posting in one tool for business authors.

Dimension SAP Build Process Automation (on SAP BTP) Precisely Automate Evolve
Vendor and nature SAP; low-code workflow and automation SaaS, part of SAP Build on BTP Precisely (formerly Winshuttle Foundation); specialised SAP data process automation platform
Core purpose Automate approvals, tasks and processes across SAP and non-SAP applications, including RPA and AI document processing Digitise data-intensive SAP processes, both master data and transactional (journal entries, orders, asset accounting): collect, enrich, approve and post data to SAP
Primary builders Citizen developers and business process experts (comparable to Evolve’s business authors), with IT for actions, destinations and BTP administration Business authors (e.g. master data, finance, supply chain CoE) or automation CoE with IT support and governance
Front end for users Request and approval forms, task inbox (My Inbox) via SAP Build Work Zone; custom UIs via SAP Build Apps Role-based web forms, SmartTables for multi-record entry, Excel workbooks, external portals
SAP posting Actions on OData/REST APIs (or BAPI/RFC) via destinations and Cloud Connector, or RPA bots; configured per object and process Native: Precisely function module over RFC, recorded transactions, Fiori and GUI for HTML, BAPIs; included Automate Studio
Data stewardship Form validations and decision tables; lookups against SAP need actions configured per process Built in: required fields, form logic, lookups against SAP, field standardisation, audit
ECC support Yes, via Cloud Connector and APIs/RFC; some workflow extension features S/4HANA-only Yes, certified for ECC and S/4HANA; S/4HANA Cloud Public Edition supported through the Studio GUI for HTML module
Deployment SAP-managed SaaS on BTP; Cloud Connector for on-premise back ends; Desktop Agent on PCs for RPA Flexible: SaaS, Precisely-hosted service, or customer-hosted (on-premise or private cloud); SaaS governance layer via Evolve Cloud Essentials (2026)
Pricing logic Advanced users (builders) and standard users (end users) per active user, plus attended automation; add-ons for API calls (in blocks of 10,000 per month), storage and unattended automation connections; bought through Pay-As-You-Go for SAP BTP or an SAP BTP Enterprise Agreement Licensed by platform and user type. Add-on special licences available for specific functions.
Typical time to first process Quick for simple approval flows, especially with SAP’s prebuilt process content; longer when SAP actions, connectivity and multi-object logic must be built Typically 1–3 months for one workflow; larger processes are built as several linked workflows, step by step

Choose Automate Evolve when the process revolves around SAP data, whether master data or day-to-day transactions: multi-record and multi-object requests (for example a product launch, customer onboarding, a batch of journal entries with approval, sales order changes or asset postings), built and changed by business authors, posted directly to standard or custom SAP transactions without API development, and running across ECC and S/4HANA. Evolve handles very complex, multi-level workflows, also runs non-SAP workflows, and, through its built-in MCP server, opens SAP to third-party AI agents in a governed way. It also connects to third-party systems, including RPA platforms and AI agents, through REST APIs.

Choose SAP Build Process Automation for approval-centric workflows extending S/4HANA, built-in RPA of UI tasks in applications without APIs, and AI-based document processing, especially where the organisation is standardising on SAP BTP.

The two are not mutually exclusive. Many organisations can run both: SAP Build Process Automation for approvals inside S/4HANA document flows, RPA and cross-application processes, and Automate Evolve for SAP data processes, master data and transactional alike. The key is a clear boundary agreed in the enterprise architecture.

Overview of each toolThe two tools in brief

SAP BTP serviceSAP Build Process Automation

SAP Build Process Automation is SAP’s low-code workflow and automation service, part of the SAP Build family on SAP Business Technology Platform (BTP). It is delivered as SAP-managed SaaS and SAP positions SAP Build to extend S/4HANA processes without impacting core functionality. Its main components:

  • Process builder (workflow): no-code workflow with approvals, conditions, parallel branches and subprocesses; Joule helps generate processes, forms and decisions from natural language.
  • Forms: drag-and-drop request and approval forms, with tables for line items.
  • Decisions: business rules in spreadsheet-like decision tables and rule flowcharts.
  • Automations (RPA): attended and unattended bots with a recorder; Desktop Agent on user PCs; UiPath add-on.
  • Document processing: extraction from documents with templates or LLM-based extraction.
  • Actions and destinations: calls to SAP and non-SAP APIs (OData/REST) through BTP destinations and Cloud Connector.
  • Process visibility and task inbox: monitoring dashboards; tasks in My Inbox / SAP Build Work Zone.

For richer user interfaces, broad system integration or external users it relies on other BTP services, mainly SAP Build Apps, Integration Suite, SAP Build Work Zone and identity services, which are licensed and run separately.

Its workflows can also be started from or plugged into SAP Business Workflow and S/4HANA flexible workflow. Per SAP Learning, the in-app extension step for flexible workflow is S/4HANA-only, while extension steps for SAP Business Workflow also work on ECC; the integration requires ABAP Platform 7.50 SP35 or higher.

Precisely AutomateAutomate Evolve

Automate Evolve is Precisely’s process automation platform for strategic SAP data processes, where process and data depend on each other: the data is complex, spans many objects, involves many teams, and is subject to audit. Business authors build solutions without SAP programming; business users work in role-based web forms or Excel. Key building blocks, per Precisely’s product material:

  • Workflow: smart logic, parallel tasks, email notifications, SLA tracking, task reassignment, attachments, dashboards and reports.
  • Web forms and SmartTables: patented multi-record forms, so one request can create or update one or many records at once: journal entries, master data records or price conditions, or a material with all its plant and sales org extensions. For larger volumes, Excel-based workflows handle thousands of records in a single request.
  • Dynamic process linking: a master process can launch the right sub-processes across objects (material, BOM, routing, info record, source list) in parallel.
  • Automate Studio included: Excel-to-SAP scripts for mass tasks and quick wins, governed from the same server.
  • Portals: external self-service portals for customers and vendors (deployed via Microsoft Azure) and internal portals.
  • SAP integration: the Precisely Automate function module on each SAP system, RFC communication, and support for SAP GUI, Fiori and GUI for HTML (October 2025). Certified for ECC and S/4HANA.
  • Administration: central content storage, script approval, licence management, policies for SAP data exchanges, audit reports, server-side scheduling. Since August 2026, Automate Evolve Cloud Essentials offers these governance functions as fully managed SaaS.
  • MCP server (AI agents): since release 26.1 the Precisely Automate MCP Server exposes Studio scripts, SAP OData reads (read-only by default) and Evolve tasks and processes as tools for MCP-compatible AI assistants such as Claude, ChatGPT and Microsoft Copilot. Agents work only through approved tools, under existing SAP authorisations and Evolve governance. The MCP server capabilities are available at no extra charge.

Purpose differencesAutomating processes, or getting SAP data right

SAP Build Process Automation is built for automating approvals, tasks and processes across applications; Evolve is built for getting SAP data processes right. The overlap is workflow-driven data collection and approval that ends in an SAP posting.

Aspect SAP Build Process Automation Precisely Automate Evolve
Problem it solves Manual approvals, repetitive tasks and document handling across SAP and non-SAP applications, without modifying the SAP core Slow, error-prone, poorly governed processes for creating and changing SAP data that involve many people and objects
Scope Any workflow-driven process across systems; SAP data posting depends on available APIs or bots Any workflow-driven business process, SAP connection optional; strongest in data-intensive SAP processes: master data lifecycles (materials, customers, vendors, GL accounts, assets, PM objects) and related transactions
Design centre Citizen developers and process experts, with IT providing connectivity and BTP governance Business author and data steward, with IT governing the platform
SAP strategic role SAP’s strategic low-code workflow and RPA service; part of SAP Build on BTP and of SAP’s clean-core extension model Third-party, SAP-certified, clean-core compatible add-on; does not modify the SAP core
Value proposition Standard SAP SaaS; workflow, RPA, document processing and Joule in one service; prebuilt content Faster time to value for SAP data processes; built-in data stewardship and SAP posting; one tool across ECC and S/4HANA
Lifecycle position Grows with the BTP and S/4HANA roadmap; typically adopted with S/4HANA or RISE Operational process automation; often introduced on ECC and carried through the S/4HANA move

Functionality differencesCapability by capability

SAP Build Process Automation wins on built-in RPA, AI (Joule, document processing) and SAP-managed cloud operations; with the separate BTP Integration Suite it adds prebuilt adapters and event-driven integration. For API-based integration the two are comparable: both call third-party REST APIs, including RPA platforms, and Evolve can also call AI agents and be triggered by external systems through its own API. Evolve wins on very complex, data-driven workflows and ready-made SAP data handling: multi-record forms, Excel, posting to any transaction, and multi-object data processes without development.

Capability SAP Build Process Automation Precisely Automate Evolve
Workflow engine Process builder with approvals, parallel branches, conditions, subprocesses, events, process visibility; dynamic parallel branches and loops are not native (branch count is fixed at design time), so complex logic often moves to scripts or pro-code Workflow for very complex, multi-level processes: smart logic, parallel tasks, dynamic sub-processes per object or record, SLAs, reminders, reassignment, attachments, dashboards
Business rules Decision tables and rule flowcharts Form and workflow logic; lookups and validations against SAP
Forms Drag-and-drop request and approval forms; tables with text, checkbox, number and date columns for line items; custom UIs via SAP Build Apps or Code Role-based web forms plus patented SmartTables: one request form can create or change many records at once (e.g. 10, 20, 50 journal entries, master data records or price conditions), each row with the form’s validations
Excel as a front end No Excel front end for forms; Excel files are read by automations (bots with Excel activities) or custom upload apps Native: Excel-based workflows handle thousands of records in one governed request, using Automate Studio workbooks inside the same platform
Multi-object processes Possible, but each object’s API calls, mapping and error handling are developed Built in: dynamic process linking launches sub-processes per object (e.g. material, BOM, routing, info record, source list)
SAP posting APIs (OData/SOAP), BAPI/RFC through Cloud Connector and destinations, or RPA bots; built per process Precisely function module over RFC; recorded SAP GUI, Fiori and GUI for HTML transactions; BAPIs; custom T-codes, tables and fields
Reading SAP data Via APIs or integration flows Live queries and lookups against SAP from forms and Excel
Non-SAP systems Actions on REST/OData APIs, including third-party RPA platforms; built-in RPA for applications without APIs; broad integration (adapters, event mesh) via BTP Integration Suite, a separate service Connections to third-party applications and databases via REST, SOAP, OData, SQL, ODBC and OLE DB; reusable REST API connections (e.g. Snowflake, Salesforce, EnterWorks, OAuth supported), including third-party RPA platforms; inbound Digital Access API lets external systems start processes and read form data; workflows can run without any SAP connection. No adapter catalogue or event mesh comparable to BTP Integration Suite
RPA Built-in attended and unattended bots; UiPath add-on Not a general RPA tool; automation runs through SAP interfaces directly. Third-party RPA bots can be orchestrated through APIs.
AI Joule for generating processes, forms and decisions; document processing with LLM extraction; access to SAP AI services Built-in MCP server (Precisely Automate MCP Server, since release 26.1): third-party AI assistants and agents use governed Studio scripts, SAP OData reads and Evolve tasks and processes as tools; can also call AI agents and services via REST. No built-in document extraction; a generative design assistant is on the product roadmap (no target date yet)
Third-party AI agent access to SAP (MCP) Not a feature of SAP Build Process Automation itself: existing automations and actions can be embedded in SAP’s own Joule agents (Joule Studio), and for external agent interoperability SAP prefers A2A (bidirectional communication with third-party agents through its Agent Gateway is not yet supported). Third-party MCP clients reach SAP through the MCP Gateway in SAP Integration Suite (feature availability depends on the service plan), which builds MCP servers from API artifacts, HTTP endpoints and RFC back ends, with OIDC/OAuth authentication, rate limiting and monitoring. Governance is at API level, so business rules and approvals must be built around it Precisely Automate MCP Server opens SAP to MCP-compatible assistants (e.g. Claude, ChatGPT, Microsoft Copilot) in a controlled way: agents can only call approved Studio scripts and Evolve processes, OData access is read-only by default, existing SAP authorisations and Evolve governance stay in place, and changes can be routed through workflow approvals; included at no extra charge, no separate integration platform needed
External users Possible with BTP identity services plus SAP Build Work Zone or a custom SAP Build Apps UI Portals for customers and vendors deployed via Microsoft Azure, with workflow behind them
Governance and audit Process visibility dashboards, monitoring, BTP audit log and role collections, transport via SAP Cloud Transport Management Content approval, licence and policy management, SAP data-exchange policies, audit reports
ECC support Yes through Cloud Connector; some workflow extension features S/4HANA-only Yes, certified for ECC and S/4HANA; S/4HANA Cloud Public Edition supported through the Studio GUI for HTML module
Multiple SAP systems Yes, via multiple destinations; actions configured per system Yes, multiple SAP connections managed centrally; processes can post to different systems
Infrastructure SAP-managed SaaS on BTP; Cloud Connector on-premise for back-end access; Desktop Agent on PCs for RPA Evolve application server, SQL database and optional worker service, run as SaaS, as a Precisely-hosted service or customer-hosted; function module in SAP; optional SaaS governance (Cloud Essentials)
Skills required Low-code builder for simple flows; API, destination and BTP administration knowledge for SAP integration; developers for custom UIs or complex logic SAP process and data knowledge; no SAP programming; low-code/no-code platform with the option to incorporate custom JavaScript and CSS code

Typical differences in company practicesPart of the BTP landscape, or a business-facing data platform

Companies run SAP Build Process Automation as part of their BTP landscape, with IT governing connectivity and citizen developers building flows. They run Evolve as a business-facing data process platform owned by IT or an automation CoE, or by a specific function such as a master data or finance CoE.

Practice Typical SAP Build Process Automation practice Typical Automate Evolve practice
Adoption route Part of BTP and SAP Build adoption, often within an S/4HANA or RISE programme and the clean-core extension strategy Introduced to improve specific data processes (onboarding, product launch, etc.), often already on ECC
Who builds Citizen developers for simple flows; IT, integration team or SI partner for actions, destinations and complex logic Business authors in a master data, finance or supply-chain CoE; Precisely partner for complex solutions
Who uses Approvers and requesters through the task inbox and apps across the company Requesters, data stewards and approvers through web forms, Excel and portals
Typical scenarios Approval flows, workflow extensions of S/4HANA, RPA of repetitive UI work, document extraction (e.g. invoices), AI-assisted scenarios New material/product launch, customer and vendor onboarding and changes, GL account and cost centre setup, plant maintenance data, mass changes via Studio
Development process Build in the SAP Build lobby, release and deploy versions; transport between BTP subaccounts (dev, test, prod) Solution built and tested by authors, approved and published centrally; iterated by the business
Change frequency Citizen developers change simple flows; changes to SAP actions and integrations go through IT Business authors change forms and rules as processes change
Controls BTP role collections, SAP authorisations behind the APIs, process logs and audit logs SAP authorisations, approved content, data-exchange policies, Evolve audit reports
Funding SAP Build / BTP subscription; consumption grows with users, API calls and bots Business-case funding per process area (time to market, data quality, compliance)

A common pattern: SAP Build Process Automation handles approvals, RPA and document-driven flows, while Evolve is used for the SAP data processes where its SmartTables, Excel integration and multi-object posting make it faster to deliver than building the same process with actions and custom UIs.

Typical company practices reflect general SAP practitioner experience.

Strengths, limitations and risksStrengths, limitations and risks

Both support a clean core. SAP Build Process Automation’s risk is build effort and cost growth for data-heavy SAP processes; Evolve’s risk is being a specialised third-party tool next to SAP’s strategic service.

SAP Build Process Automation

StrengthsStandard SAP SaaS; workflow, RPA, document processing and Joule in one service; integrates with S/4HANA workflows; access to BTP integration and AI services; clean-core extension model

LimitationsData-intensive SAP processes need actions, mapping and error handling per object; forms support simple tables, but Excel input runs through bots or custom upload apps; broad integration and rich UIs need other BTP services; some features S/4HANA-only

Key risksConsumption costs grow with users, API calls and bots; long delivery backlog; workarounds when standard APIs lack fields

MitigationsAgree which process types belong where; reuse prebuilt content; size consumption early

Precisely Automate Evolve

StrengthsPurpose-built for SAP data processes; SmartTables and Excel for multi-record work; posting to any transaction including custom ones; dynamic multi-object processes; business-authored; ECC and S/4HANA

LimitationsStrongest in SAP data and transactional processes (non-SAP workflows are supported, but non-SAP system integration is narrower than BTP Integration Suite); no built-in document extraction; generative design assistant on the roadmap but not yet available

Key risksWhere SAP Build Process Automation is also in use (for example through BTP credits in a RISE contract), overlapping tools if roles are not agreed; dependency on the Precisely partner ecosystem; recordings to retest after UI changes

MitigationsDefine the boundary with SAP Build Process Automation in the architecture; use Cloud Essentials or central administration; maintain a solution inventory

When to choose whichApprovals and RPA, or governed SAP data processes

Use SAP Build Process Automation for approvals, RPA and cross-application flows. Use Evolve where the work is a governed SAP data process that must go live quickly and be changed by the business.

Scenario Recommended tool Why
Approval workflow around a standard S/4HANA document Either, depending on where the approval sits Approval of a document already created in S/4HANA (e.g. extending a flexible workflow for purchase orders): SAP Build Process Automation, via its in-app extension step.
Request and approval before the document is posted (e.g. collect, validate and approve journal entries or orders, then post): Automate Evolve, also on ECC
Process orchestrated across SAP and non-SAP systems Either, depending on the landscape and the focus of the process Both call REST APIs and RPA platforms.
Landscape standardised on BTP and Integration Suite, or UI tasks in systems without APIs: SAP Build Process Automation, with built-in RPA and Integration Suite adapters.
Process centred on SAP data: Automate Evolve, with direct SAP posting and multi-record handling
Document processing, RPA of repetitive UI work, AI-assisted flows SAP Build Process Automation Document processing, bots and Joule in one service
Letting third-party AI agents (Claude, ChatGPT, Copilot) read or change SAP data under control Automate Evolve Built-in MCP server exposes only approved scripts and processes, keeps SAP authorisations and can route changes through approvals
New product launch spanning material, BOM, routing, info record and pricing Automate Evolve Dynamic process linking and SmartTables without development
Customer or vendor onboarding with external self-service Automate Evolve Portals plus workflow and direct SAP posting
Data processes on ECC today that must survive the S/4HANA move Automate Evolve Same solutions across ECC and S/4HANA, including Fiori and GUI for HTML
Mass data requests and changes with approval, from tens to thousands of records (e.g. 100 journal entries, a batch of new customers or a price list update) Automate Evolve SmartTables handle tens to hundreds of records in one web form request; Excel-based workflows (Automate Studio is included) handle thousands; all in one governed approval flow
Custom transactions, Z-fields or Z-tables in the process Automate Evolve Records and posts to custom T-codes, tables and fields

Mass changes from Excel without a workflow? See our Automate Studio vs. SAP Fiori mass maintenance apps comparison.

Use SAP Build Process Automation for approvals, RPA and cross-application flows, and Automate Evolve where the work is a governed SAP data process.

Multi-system SAP landscapesSeveral SAP systems in one landscape

If the landscape contains several SAP systems, especially a mix of ECC and S/4HANA:

SAP Build Process Automation

SAP Build Process Automation can reach each system through Cloud Connector destinations, but every connection, API mapping and error path is configured and developed per system, and some workflow extension features exist only on S/4HANA.

Automate Evolve

Automate Evolve manages multiple SAP connections centrally and can run one governed process that collects data once and posts it to the right ECC or S/4HANA system. This is where Evolve is strongest compared with SAP Build Process Automation for data processes.

Coexistence

Coexistence works well: SAP Build Process Automation for approvals, RPA and cross-application flows, Evolve for SAP data processes, with a clear boundary agreed in the enterprise architecture.

How we helpAutomate Evolve for your SAP data processes

We help you pick the SAP data processes where Automate Evolve pays off first, build and test the workflows, forms and SAP postings with your business authors, and agree a clear boundary with SAP Build Process Automation where both are in use.

Precisely partner since 2016

15 years of hands-on experience with the product.

Frequently asked questionsQuestions we hear most often

What can Automate Evolve do that SAP Build Process Automation doesn’t offer out of the box?

Evolve is purpose-built for SAP data processes. Patented SmartTables let one request form create or change many records at once, Excel-based workflows handle thousands of records in one governed request, and dynamic process linking launches sub-processes per object, such as material, BOM, routing, info record and source list. It posts directly to standard or custom SAP transactions without API development, on ECC and S/4HANA.

When is SAP Build Process Automation the better choice?

For approval-centric workflows extending S/4HANA documents, for example extending a flexible workflow for purchase orders through its in-app extension step, for built-in RPA of UI tasks in applications without APIs, and for AI-based document processing, especially where the organisation is standardising on SAP BTP.

How long does it take to get a first process live with Automate Evolve?

Typically 1–3 months for one workflow. Larger processes are built as several linked workflows, step by step. After go-live, business authors change forms and rules as processes change, without SAP programming.

Can third-party AI agents work with SAP data through Automate Evolve?

Yes. Since release 26.1 the Precisely Automate MCP Server exposes approved Studio scripts, SAP OData reads (read-only by default) and Evolve tasks and processes as tools for MCP-compatible assistants such as Claude, ChatGPT and Microsoft Copilot. Existing SAP authorisations and Evolve governance stay in place, changes can be routed through workflow approvals, and it is included at no extra charge.

Can Automate Evolve and SAP Build Process Automation run side by side?

Yes. A common pattern is SAP Build Process Automation for approvals, RPA and document-driven flows, and Automate Evolve for SAP data processes, master data and transactional alike. The key is a clear boundary agreed in the enterprise architecture, so that the two tools do not overlap.

Planning an SAP data process on SAP Build Process Automation? We will show you how it runs in Automate Evolve.

ContactTalk to an expert

Tell us which SAP process or product you are looking at. One of our consultants will get back to you.

What happens next

  1. We read your message and pass it to the consultant who knows the topic.
  2. We contact you to agree on a short call.
  3. If you wish, we show a demo on a process like yours.

Prefer to write directly?
info@novacon.hu



    * Required fields

    NOVACON ZRT.Headquarters
    H-1048 Budapest, Tófalva u. 11 B/5
    Hungary
    INTERNATIONAL FOOTPRINTProjects in Europe
    Novacon on the map of Europe
    KNOWLEDGE SHARINGNovacon community
    Join and learn about practical experiences, results and client stories!
    NOVACON ZRT.Headquarters
    H-1048 Budapest, Tófalva u. 11 B/5
    Hungary
    INTERNATIONAL FOOTPRINTProjects in Europe
    Novacon on the map of Europe
    KNOWLEDGE SHARINGNovacon community
    Join and learn about practical experiences, results and client stories!

    Copyright 2026 Novacon Zrt. All rights reserved!

    Copyright 2026 Novacon Zrt. All rights reserved!

    GDPR logo
    Privacy Overview

    This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.