
GITNUXSOFTWARE ADVICE
Data Science AnalyticsTop 10 Best Payment Analytics Services of 2026
Rank and compare payment analytics services, covering IBM Consulting, Capgemini, and PwC, with criteria for reporting and merchant insights.
How we ranked these tools
Gitnux editors write the brief first: the topic, the inclusion rules, and the frame for what belongs.
Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
IBM Consulting is the best fit when you need managed, governance-heavy payment analytics with integration and production oversight, whereas Glenbrook Partners works well for teams that want transaction-level observability and implementation guidance for routing and failure analysis.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
IBM Consulting
Delivery-focused payment analytics engineering that couples transaction diagnostics with reconciliation and operational handoff.
Best for: Fits when payment programs need managed integration, analytics buildout, and production governance.
Capgemini
Editor pickGoverned delivery of analytics-to-operations workflows, including reconciliation alignment and controlled monitoring rollouts.
Best for: Fits when payment teams need managed analytics integration with strong governance and operations handoff.
PwC
Editor pickAdvisory-driven metric governance that links transaction evidence to control objectives and reconciliation narratives across teams.
Best for: Fits when governance-heavy payment analytics and cross-stakeholder evidence are the primary deliverable.
Comparison Table
IBM Consulting
enterprise_vendorConsulting provider delivering payment data analysis, fraud analytics, processing modernization, and reconciliation services.
Delivery-focused payment analytics engineering that couples transaction diagnostics with reconciliation and operational handoff.
IBM Consulting delivers payment analytics work as an engineering and delivery service, not just software, which makes it distinct for teams needing implementation and operational handoff. Core capabilities typically center on transaction-level analytics pipelines, payment performance diagnostics, and reconciliation automation across PSP, acquirer, and network data sources.
Integrations are usually built around IBMer-led data ingestion, transformation, and API-enabled service layers for observability and workflow automation. Strong governance fit appears in delivery artifacts like access controls, audit-ready logging expectations, and runbook-driven operations for production change control.
- +Implementation-led analytics pipelines for transaction-level observability and diagnostics
- +Integration and automation support across PSP, acquirer, and network data flows
- +Operational governance artifacts for auditability and controlled production change
- +Extensibility for custom payment funnel metrics and routing decision inputs
- –Requires delivery scope alignment and tighter project governance than self-serve tools
- –Depth of analytics depends on chosen reference architecture and partner tooling
Best for: Fits when payment programs need managed integration, analytics buildout, and production governance.
Capgemini
enterprise_vendorConsulting and technology services provider covering payment data, processing, fraud, and reconciliation analysis.
Governed delivery of analytics-to-operations workflows, including reconciliation alignment and controlled monitoring rollouts.
Capgemini is a strong fit for teams that want analytics outcomes embedded into operational change control, including data pipeline monitoring and release governance. Delivery commonly focuses on transaction observability, mapping issuer response codes into analyzable fields, and aligning outputs with reconciliation and operations teams. Automation and API surface typically show up through integration work across existing payment orchestration, ETL or streaming, and analytics environments.
A key tradeoff is that Capgemini delivery depth is easier to realize with existing engineering and data governance support, since customization and integration depend on clear ownership of source systems and target data contracts. Capgemini works well when an organization must diagnose authorization rate drivers across channels and then translate findings into routing, retry, or settlement reconciliation process changes.
- +Integration work ties analytics outputs to reconciliation and operations workflows
- +Transaction-level analytics mapping supports issuer response code driven reporting
- +Delivery governance supports controlled rollout of analytics and monitoring changes
- +Automation planning reduces manual triage across payment failure investigations
- –Implementation effort is higher when data contracts and source ownership are unclear
- –Category analytics depth can depend on included data engineering deliverables
- –Turnaround for new metrics may lag without an agreed change pipeline
- –Admin controls and RBAC patterns require coordination with enterprise identity systems
Payment operations teams
Investigate payment failures by response codes
Fewer unresolved failures
Risk and fraud analytics
Measure dispute and loss drivers
Lower dispute rate
Show 2 more scenarios
Payments engineering
Optimize cascading retries
Improved approval rate
Use transaction observability signals to tune retry logic and monitor authorization outcomes.
Finance reconciliation owners
Automate settlement reconciliation
Faster close
Align analytics outputs with settlement data flows to reduce breaks between reporting and reconciliation.
Best for: Fits when payment teams need managed analytics integration with strong governance and operations handoff.
PwC
enterprise_vendorProfessional services firm advising on payment operating models, transaction data, fraud, and reconciliation.
Advisory-driven metric governance that links transaction evidence to control objectives and reconciliation narratives across teams.
PwC engagement teams commonly build end-to-end views that tie authorization and decline patterns to failure categories, then map those patterns to remediation tasks owned by payments operations, risk, and engineering. The analytics work is usually anchored in documented metric definitions and control objectives, which helps keep chargeback analytics and payment failure analysis aligned across teams. The strongest fit appears when multiple parties need consistent evidence for decisions, including dispute handling, issuer-response-code interpretation, and settlement reconciliation narratives.
A practical tradeoff is limited out-of-the-box automation and API surface compared with analytics vendors that ship standardized developer interfaces for transaction observability. PwC works best when internal systems can provide raw event streams and when governance requirements demand repeatable methodology, especially during payment method performance reviews and involuntary churn investigations driven by recurring soft declines.
- +Control-oriented analytics that translate failures into actionable governance workflows
- +Methodology and metric definitions that keep dispute and chargeback reporting consistent
- +Cross-team delivery that connects decline patterns to operations, risk, and engineering
- +Strong evidence trails that support reconciliation and audit-style decisioning
- –API and automation depth depends heavily on the chosen delivery scope
- –Less self-serve than productized analytics tooling for daily investigators
- –Faster iteration can require extra engineering effort on the client data side
- –Standard dashboards may lag bespoke metric and workflow requirements
Payments risk leaders
Prioritize fraud-loss drivers across declines
Lower fraud-loss rate
Payments operations teams
Reconcile settlement differences at scale
Fewer reconciliation exceptions
Show 2 more scenarios
Disputes and chargeback analysts
Align dispute rates with failure modes
More consistent dispute triage
Connects dispute rate patterns to failure categories and supporting authorization evidence.
Platform and payments engineering
Instrument transaction observability governance
Cleaner payment funnel evidence
Defines measurement contracts for monitoring and routing failures across payment service providers.
Best for: Fits when governance-heavy payment analytics and cross-stakeholder evidence are the primary deliverable.
Deloitte
enterprise_vendorProfessional services firm advising on payment analytics, fraud, disputes, reconciliation, and operating models.
Cross-domain payment performance diagnostics delivered with governance artifacts for audit, risk, and operations alignment.
Deloitte delivers payment analytics through advisory-led engagements that translate transactional data into actionable diagnostics for authorization, acceptance, and operational performance. Deloitte’s distinctive value is the combination of analytics delivery with governance, model documentation, and deployment planning across reporting, risk, and operations teams.
Deloitte typically supports transaction-level observability workflows and reconciliation-oriented analysis that connect payment events to measurable outcomes such as approval rate, decline rate patterns, and exception handling. Deloitte also integrates payment insights into broader enterprise data, controls, and audit processes instead of limiting output to dashboards.
- +Advisory delivery connects payment metrics to operating decisions and controls
- +Strong governance outputs support audit-ready documentation and stakeholder alignment
- +Transaction-level diagnostics support pinpointing decline and routing problem areas
- +Reconciliation-focused analysis reduces gaps between payment events and settlement views
- –Execution depends heavily on engagement scope rather than product self-serve workflows
- –API automation and developer extensibility are not the primary delivery mechanism
- –Time-to-value can be longer than tool-first analytics vendors for new programs
- –Workflow standardization can vary across client teams and engagement leads
Best for: Fits when payment teams need analytics plus governance, reconciliation alignment, and managed delivery oversight.
Accenture
enterprise_vendorConsulting provider delivering payment analytics, processing transformation, fraud analysis, and data services.
Delivery-led analytics architecture that ties transaction-level observability to governed operational workflows across enterprise systems.
Accenture fits payment teams that need cross-enterprise payment analytics delivered with deep systems integration and program governance. It is geared toward transaction-level analytics that connect payment events to operational workflows like reconciliation automation, reporting, and controls.
Core work typically combines data integration pipelines, configurable analytics logic, and managed deployment support for high-throughput environments. Delivery is often shaped by enterprise data and control requirements, not just dashboards for analysts.
- +Enterprise integration delivery across payment data sources and downstream systems
- +Strong audit and governance patterns for analytics and reporting workflows
- +Automation support for reconciliation-related reporting and exception handling
- +Program-scale architecture planning for consistent transaction observability
- –Requires longer implementation cycles than vendor-first analytics tools
- –Depends on Accenture delivery capacity for end-to-end analytics buildout
- –API extensibility is typically shaped by the engagement scope
- –Less suited for teams seeking a quick, self-serve analytics layer
Best for: Fits when enterprises need governed transaction analytics integration with existing reconciliation and reporting workflows.
Mastercard Advisors
enterprise_vendorMastercard advisory practice covering payment portfolio analytics, authorization, fraud, and customer performance.
Network intelligence advisory that connects issuer and network signals to decline and authorization diagnosis.
Mastercard Advisors delivers payment analytics and consulting grounded in Mastercard transaction and network intelligence, not a generic dashboard alone. It supports transaction-level analysis workflows that connect issuer and network context to business outcomes like authorization performance and decline behavior.
The offering is tailored to payment teams that need guided analysis and operational recommendations tied to specific payment ecosystems. Implementation typically follows a structured engagement model that shapes data access, reporting cadences, and governance rather than self-serve configuration.
- +Network-context analytics that tie issuer behavior to authorization outcomes
- +Engagement-driven workflows that translate findings into action plans
- +Accountability through defined reporting cadences for key performance metrics
- +Strong fit for cross-program analysis where multiple payment parties matter
- –Not positioned for rapid self-serve transaction analytics in isolation
- –Automation and API depth depends on engagement scope and data arrangements
Best for: Fits when payment teams want network-informed diagnostics and guided operational recommendations.
Glenbrook Partners
specialistPayments consulting firm advising on payment systems, transaction economics, data, and market structure.
Operational payment failure investigations that connect issuer response codes to authorization behavior and outcome patterns.
Glenbrook Partners delivers payment analytics focused on transaction-level intelligence for troubleshooting, routing analysis, and performance governance. It aggregates payment data from processors and payment infrastructure signals into views that help track authorization behavior and downstream outcomes.
The service emphasizes operational workflows such as reconciliation automation support and retry and failure pattern diagnosis. Glenbrook is distinct for combining analytics delivery with deep payment domain expertise across issuers, acquirers, and network response codes.
- +Strong transaction-level diagnostics tied to processor and network response signals
- +Practical support for reconciliation automation workflows across payment operations
- +Governance-friendly reporting for payment service provider routing and performance reviews
- +Grounded guidance on interpreting authorization rate and downstream outcomes
- –Integration depth can require significant internal data mapping and data ownership
- –Automation coverage depends on implementation scope and data availability
- –Analytics usability may lag self-serve tooling for fast exploratory analysis
- –Less suited for teams that only need high-level dashboards
Best for: Fits when payment teams need transaction-level observability with implementation guidance for routing and failure analysis.
CMSPI
specialistPayments consultancy providing transaction analysis, acceptance optimization, and payment performance benchmarking.
Operational decline and authorization performance reporting tied to payment-processing outcomes for ongoing casework.
CMSPI provides payment analytics focused on transaction-level performance reporting and operations support for payment teams managing processing outcomes. The service is distinct for its emphasis on data aggregation into operational views that track authorization behavior, decline patterns, and resolution outcomes across payment flows.
CMSPI supports automation through reporting outputs and integration pathways that let teams refresh metrics on a schedule for ongoing monitoring and incident response. The offering is best evaluated on how well it turns raw transaction feeds into decision-ready insights for acquirer and issuer performance handling.
- +Transaction-level analytics designed for diagnosing authorization and decline patterns
- +Operational reporting outputs support recurring monitoring without manual spreadsheet work
- +Integration pathways allow feeding aggregated payment data into analytics workflows
- +Reporting focus fits payment operations teams handling routing and performance issues
- –Depth of developer-first API surface is not as transparent as larger analytics vendors
- –Advanced configuration may require ongoing governance to keep attribution accurate
- –UI tooling for ad-hoc exploration can lag behind analytics-first competitors
- –Standalone value is limited when teams need orchestration or routing execution
Best for: Fits when payment operations teams need recurring transaction analytics and reporting for performance investigations.
Edgar, Dunn & Company
specialistPayments consultancy covering transaction analytics, acquiring strategy, fraud, and payment infrastructure.
Failure analysis workflow that links decline patterns to downstream reconciliation questions using controlled transaction mapping.
Edgar, Dunn & Company is a strong fit when payment teams need consistent transaction observability across authorization outcomes and downstream settlement questions. The analytics approach centers on failure analysis and payment method performance so teams can pinpoint where decline patterns emerge and how they propagate through retries. Integration depth is a key differentiator versus many analytics-only vendors because the service typically aligns data ingestion to the team’s existing payment ecosystem. Automation surfaces are designed to reduce manual exports and keep reporting consistent across operating cycles.
A practical tradeoff is that analytics configuration and data mapping require attention to data consistency, especially when multiple acquiring paths and routing behaviors must be represented. Edgar, Dunn & Company fits best when a payment program already has clear operational ownership for reconciliation artifacts and wants automation to reduce reporting drift. Usage is most effective when teams can provide stable identifiers for transactions across authorization, clearing, and reconciliation joins.
- +Transaction-level reporting tied to authorization and failure investigations
- +API-driven data ingestion for recurring analytics without manual exports
- +Operational guidance for reconciliation-driven payment analytics workflows
- +Change handling designed for traceability in managed reporting cycles
- –Data mapping work is necessary when identifiers vary across systems
- –Automation depth depends on integration readiness and stable source fields
- –Admin configuration can take time for teams without analytics governance
- –Coverage of payment orchestration metrics may require additional setup
Best for: Fits when payment teams need transaction observability plus reconciliation-aligned analytics automation.
Oliver Wyman
enterprise_vendorManagement consultancy advising payment companies on economics, strategy, risk, and transaction performance.
Root-cause oriented performance investigations that connect authorization outcomes to operational and routing decisions across the payment journey.
Oliver Wyman is a payment analytics and advisory firm used for transaction-level performance analysis tied to commercial and operational decisions. Its work typically centers on mapping payment flows to measurable outcomes like authorization, approval, decline, and payment failure patterns across journeys and channels.
The distinct differentiator is the focus on decision-grade diagnostics that connect metrics to root causes, including issuer or network signals and routing behaviors. Engagements commonly include analytics design, governance framing, and stakeholder-ready reporting workflows rather than self-serve dashboards.
- +Strong transaction-level diagnostics tied to business root-cause narratives
- +Good fit for multi-stakeholder reporting across payments, risk, and operations
- +Experienced guidance on governance for sensitive payment performance data
- +Works well when analysis must translate into routing and operational decisions
- –Analytics delivery is engagement-dependent rather than productized self-service
- –Limited transparency into automation and API surface for ongoing ingestion
- –Provisioning timelines can stretch when data access and governance need alignment
- –Less suited to high-throughput, real-time transaction observability needs
Best for: Fits when payment teams need decision-grade diagnostics and governance-led analytics design support.
Conclusion
After evaluating 10 payment analytics, IBM Consulting stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right Payment Analytics
Payment analytics teams use specialized providers to turn payment data aggregation into transaction-level observability, investigation workflows, and reconciliation-ready reporting. This guide covers IBM Consulting, Capgemini, PwC, Deloitte, Accenture, Mastercard Advisors, Glenbrook Partners, CMSPI, Edgar, Dunn & Company, and Oliver Wyman.
The providers in this category differ most in how they deliver integration depth, automation and API surface, and governance outputs that guide operations decisions. IBM Consulting and Capgemini lead with delivery-focused architectures that connect PSP, acquirer, and network flows to operational handoff, while PwC and Deloitte emphasize governance artifacts that map transaction evidence to control objectives.
Payment Analytics services for transaction diagnostics, reconciliation alignment, and governance
Payment analytics in this buying set focuses on transaction-level analytics that explain approval rate, decline rate, and payment failure analysis using issuer and network signals, then tie the findings to reconciliation automation and operational workflows. Providers such as Glenbrook Partners and Edgar, Dunn & Company emphasize mapping issuer response codes to authorization outcomes so teams can run repeatable failure investigations.
IBM Consulting and Capgemini differentiate through integration-first delivery that connects analytics outputs to reconciliation alignment and controlled monitoring rollouts across downstream systems. PwC and Deloitte steer toward metric governance and evidence-to-control narratives that keep dispute and chargeback analytics consistent across stakeholders.
What Payment Analytics services must deliver for transaction diagnostics
Payment analytics is only useful when it turns payment data aggregation into transaction-level observability that explains why approval rate, authorization rate, and decline rate shift across PSP and network paths. Teams also need reconciliation-ready outputs that connect investigation findings to operating decisions for disputes, chargebacks, and payment failure analysis.
Integration depth across PSP, acquirer, and network signals
IBM Consulting and Capgemini focus on delivery-led integration that connects analytics outputs to reconciliation alignment and operational handoff across payment data flows.
Automation and governed analytics-to-operations workflow handoff
Capgemini and Accenture emphasize governed delivery of analytics outputs into reconciliation workflows and cross-enterprise reporting processes.
Metric governance tied to control objectives and evidence narratives
PwC and Deloitte steer toward advisory-driven metric governance that keeps dispute and chargeback analytics consistent across stakeholders.
Issuer response mapping for repeatable failure investigations
Glenbrook Partners and Edgar, Dunn & Company tie transaction diagnostics to issuer response codes and authorization outcomes so teams can run repeatable investigation patterns.
Operational decline and authorization performance casework reporting
CMSPI and Glenbrook Partners provide operational decline and authorization performance reporting designed for ongoing casework and recurring monitoring.
Network-context diagnosis for authorization outcomes
Mastercard Advisors ties network context to issuer behavior so payment teams can diagnose decline and authorization outcomes with guided operational recommendations.
Choose based on delivery model, control needs, and how analytics moves into operations
Payment teams should decide whether the work must be delivered as an integration and handoff program or delivered as a governance and evidence framework that supports investigators. They should also map how findings become operational actions, since IBM Consulting and Capgemini route analytics into reconciliation alignment while PwC and Deloitte route evidence into governance workflows.
Pick a delivery model that matches internal integration capacity
Select IBM Consulting or Accenture when internal teams need end-to-end integration delivery across payment data sources and downstream reconciliation systems. Select PwC or Deloitte when cross-stakeholder governance and control evidence delivery matters more than productized self-serve investigation.
Decide whether analytics must be evidence-to-control oriented
Choose PwC or Deloitte when disputes and chargeback reporting must stay consistent with control objectives and evidence narratives across risk, audit, and operations. Choose Deloitte or Capgemini when governance artifacts must pair with reconciliation alignment outputs for audit and operational decision-making.
Confirm the service can support transaction-level observability for failure diagnosis
Choose Glenbrook Partners or Edgar, Dunn & Company when issuer response mapping must drive operational failure investigations tied to authorization outcomes. Choose CMSPI when operational decline and authorization performance reporting must support ongoing casework without turning investigations into spreadsheet work.
Match network-informed diagnostics to the sources available in production
Choose Mastercard Advisors when network-context analytics must connect issuer behavior to authorization outcomes for decline diagnosis. Avoid relying on engagement-dependent delivery when rapid self-serve transaction analytics is the primary operational need.
Validate how analytics outputs align with reconciliation and operations workflows
Select Capgemini or IBM Consulting when reconciliation alignment and controlled monitoring rollouts must be part of the delivery outcomes. Select Accenture or Deloitte when transaction analytics must tie into governed operational workflows across enterprise systems.
Who should buy Payment Analytics services from this set
Payment teams should use these services when transaction-level investigation needs to connect payment diagnostics to reconciliation narratives and operational actions. The set also fits organizations where evidence governance and cross-stakeholder consistency matter as much as day-to-day investigative throughput.
Payment operations teams responsible for recurring authorization and decline monitoring
CMSPI and Glenbrook Partners are built for recurring transaction analytics and operational reporting that supports ongoing casework and failure pattern investigations.
Fraud-loss and dispute teams that require control-consistent reporting
PwC and Deloitte support metric governance that keeps dispute and chargeback reporting consistent with control objectives and stakeholder evidence expectations.
Platform and integration teams that need managed analytics pipelines across payment flows
IBM Consulting and Accenture deliver transaction-level observability tied to reconciliation and operational handoff across PSP, acquirer, and enterprise systems.
Investigators that need issuer response code mapping into repeatable failure workflows
Glenbrook Partners and Edgar, Dunn & Company connect issuer response codes to authorization behavior so teams can repeat investigations and automate follow-on reconciliation questions.
Network-focused teams that need issuer and network context for authorization diagnosis
Mastercard Advisors focuses on network-context analytics that tie issuer behavior to authorization outcomes and guided operational recommendations.
Common buying pitfalls for Payment Analytics delivery and governance
Teams often misalign payment analytics expectations with the service delivery model and the operational handoff they actually need. Other failures come from assuming automation and API depth are self-serve capabilities when IBM Consulting and Capgemini emphasize engagement-led delivery outcomes.
Assuming analytics depth will be self-serve without delivery scope alignment
IBM Consulting and Capgemini can deliver deep transaction diagnostics, but both depend on delivery scope alignment and clear governance over the reference architecture and partner tooling.
Overlooking how metric definitions and evidence narratives affect dispute and chargeback consistency
PwC and Deloitte translate transaction evidence into control-oriented analytics workflows, so teams that skip governance requirements often get inconsistent findings across stakeholders.
Choosing a governance-first provider when transaction-level failure investigations must be repeatable from response codes
Glenbrook Partners and Edgar, Dunn & Company focus on mapping issuer response codes to authorization outcomes, which is missing when the program is only built as an advisory governance narrative.
Treating network-context analytics as a substitute for operational observability
Mastercard Advisors provides network-informed diagnosis, but it is not positioned for rapid self-serve transaction analytics in isolation, so teams must plan for operational observability coverage.
Expecting automation and API extensibility transparency without engagement dependence
Oliver Wyman and PwC highlight engagement-dependent analytics design and delivery, so teams that need ongoing ingestion automation should require clear automation and API surface expectations in the engagement scope.
How analysts checked these Payment Analytics services
Analysts gathered information from provider materials for each named service and copied the figures that appear next to claims about analytics capabilities, delivery scope, and operational handoff. Analysts compared each copied figure with official documentation and the provider changelog and used an independent review only when one was cited for a specific claim.
Analysts kept figures only when they matched across those sources and retained benchmark references only when the benchmark was the cited source. IBM Consulting stood out in these checks because the delivery-focused payment analytics engineering was repeatedly tied to transaction diagnostics plus reconciliation and operational handoff outcomes.
Frequently Asked Questions About Payment Analytics
Which payment analytics services handle payment data integration with an API-first workflow?
Which provider supports governance and audit log expectations for admin-controlled access?
How do payment analytics engagements typically support identity and access management like SSO and RBAC?
When migration is required from legacy reporting, what breaks if transaction identifiers change?
What data model and schema decisions matter when joining issuer response codes to reconciliation outcomes?
Where does payment analytics fall short when a team needs prebuilt developer interfaces for transaction observability?
How should payment teams measure throughput and data freshness for operational monitoring?
Which provider is best for connecting authorization performance diagnostics to retry or routing changes?
When chargeback analytics and dispute rate evidence must be consistent across stakeholders, which service helps most?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
- Data Science AnalyticsTop 10 Best Analytics Services of 2026
- Finance Financial ServicesTop 10 Best Financial Payment Services of 2026
- Data Science AnalyticsTop 10 Best Call Center Analytics Services of 2026
- Data Science AnalyticsTop 10 Best Payment Analytics Software of 2026
- Data Science AnalyticsTop 10 Best Payment Tracker Software of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Data Science Analytics alternatives
See side-by-side comparisons of data science analytics tools and pick the right one for your stack.
Compare data science analytics tools→