> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/trade/start-here/evaluation-guide.md). # Evaluation Guide Welcome to your TRADE evaluation. This guide walks you through the \~14-day evaluation, helping you get the most out of the process and reach a confident decision. Your Customer Enablement Manager (CEM) is with you every step of the way: reach out anytime on your dedicated Slack channel. *** ## Your first hour Before anything else, see the data live: 1. Log in with the credentials from your activation email. 2. Open the [Coverage Hub](/u/coverage-hub/coverage-hub.md) and find the sports and leagues you care about. 3. Watch live data move in the [monitoring section](/u/coverage-hub/monitoring.md). This should get you started. The rest of this guide helps you verify it fits your business. *** ## Scope of the evaluation The evaluation assesses the data and the platform; it is not an integration project. Evaluating first lets you confirm latency, uptime, and coverage fit before your engineering team commits weeks to a full production integration. A minimal test connection is enough: connect, consume, measure. Anything production-related comes after a Go decision, with your CEM guiding it. *** ## Before you start Share this with your CEM ahead of kickoff so Day 1 starts moving immediately: * **Business context:** company background and current betting operations, sports and markets of interest, expected volume and usage patterns, compliance and regulatory requirements. * **Team and timeline:** technical team contacts and availability, your expected evaluation timeline and decision process, and who needs platform access. * **Meeting attendance:** a **Business Champion** (owns the Go/No-Go decision) and a **Technical Champion** (owns the integration and data validation) are mandatory for the kickoff, mid-point, and summary meetings. * **Technical details:** any constraints relevant to your setup, preferred SDK ([.NET](/u/trade/integration/sdk/sdk-installation-guide-.net.md), [Java](/u/trade/integration/sdk/sdk-installation-guide-java.md), or [Node.js](/u/trade/integration/sdk/sdk-installation-guide-nodejs.md)), and existing infrastructure considerations for RabbitMQ consumption. * **Success KPIs:** the latency, uptime, or other metrics that would make this evaluation a Go for your business. *** ## Key principles for a successful evaluation * You'll be working with **production-grade data**: no mock or delayed data. * Complete the phases **in order**: they build on each other. * If you hit a blocker at any point, share it with your CEM immediately. Don't wait for the next check-in. * The **mid-point sync (Day 7)** is the moment to raise concerns and recalibrate if needed. * Coverage on your test account is flexible: contact your account owner to adjust it to your needs. *** ## Evaluation timeline | Milestone | When | Description | | --------------------------------------- | --------- | --------------------------------------------------------------------------------- | | **Kickoff meeting** | Day 1 | Align on goals, setup, and the evaluation plan | | **Phase 1: Initial service assessment** | Days 1–2 | Explore the platform, confirm coverage against your KPIs | | **Phase 2: Configuration and setup** | Days 1–2 | Tailor TRADE to your business requirements | | **Phase 3: Core testing** | Days 2–13 | Connect to the feed, test with live data, measure against your KPIs | | **Mid-point sync** | Day 7 | Within Phase 3: review progress with your CEM; confirm you're on track to wrap up | | **Phase 4: Evaluation summary** | Day 14 | Go / no-go decision | *** ## Phase 1: Initial service assessment (Days 1–2) Get familiar with TRADE and validate that the data meets your needs. * Log in with the credentials from your activation email, and invite your business and technical team members to the platform. * Review sports and market coverage in the Coverage Hub ([Markets](/u/coverage-hub/markets.md), [Livescore](/u/coverage-hub/livescore.md), [Settlements](/u/coverage-hub/settlements.md)), alongside the [Settlements Rulebook](/u/trade/settlements-rulebook.md). * Assess live data accuracy in the [monitoring section](/u/coverage-hub/monitoring.md). * Read the documentation, starting with [Capabilities](/u/trade/capabilities.md) and [Concepts](/u/trade/concepts.md). {% hint style="success" %} **Phase 1 is complete when** coverage is mapped to your business requirements. {% endhint %} *** ## Phase 2: Configuration and setup (Days 1–2) Tailor TRADE to match your business requirements. * Configure the [provider list](/u/trade/user-guide/configuration/provider-list.md) for your package; set minimum thresholds, mandatory providers, and weights, or use LSports' recommended provider configuration. * Configure odds formats, margin settings, min-max ranges, and out-of-range actions in [Package Configuration](/u/trade/user-guide/configuration/package.md). * Set up default or custom [templates](/u/trade/user-guide/configuration/templates.md) and test them across hierarchy levels; evaluate template override functionality, or start from LSports' recommended templates. * Configure [Notifications](/u/trade/user-guide/configuration/notifications.md) to monitor system activity. {% hint style="warning" %} InPlay is quota-limited during evaluation: order fixtures individually to make the most of it. {% endhint %} {% hint style="success" %} **Phase 2 is complete when** your configuration is live and templates are validated across your required hierarchy levels. {% endhint %} *** ## Phase 3: Core testing (Days 2–13) Connect to the data feed and test the system with actual data. This is the main phase: keep measuring throughout, not just at the start. * Connect to **RabbitMQ** and consume live data using one of the SDKs ([.NET](/u/trade/integration/sdk/sdk-installation-guide-.net.md), [Java](/u/trade/integration/sdk/sdk-installation-guide-java.md), [Node.js](/u/trade/integration/sdk/sdk-installation-guide-nodejs.md)). If your stack isn't covered by an SDK, see [Connection Setup](/u/trade/integration/connection-setup.md) for a direct RabbitMQ consumer. Keep your consumer connected throughout the phase to validate ordering, odds behavior, and latency. * For PreMatch, test fixture ordering at different hierarchy levels (sport, location, competition, fixture). * For InPlay, test fixture ordering at the fixture level only (quota-limited). * Monitor the [Trading Floor](/u/trade/trade.md#trading-floor); compare [Fixture Logs](/u/trade/user-guide/operational/fixture-logs.md) with the data you've consumed. * Compare `timestamp_in_ms` (when the message was placed on your queue, in the RabbitMQ header) against received time in your system. * Compare the `ServerTimestamp` header field against the last update time on your end to check data freshness. * Test odds updates, market suspension, and odds settings mid-event. {% hint style="success" %} **Phase 3 is complete when** data is flowing correctly, fixture ordering is validated, and latency is measured. {% endhint %} *** ## What to measure Bring numbers, not impressions, to the summary meeting. Track these throughout Phase 3. Use this worksheet as your Day-14 material: | Metric | How to measure | Your target | Observed | | ----------------------- | ------------------------------------------------------------------------------------------------------------------ | ----------- | -------- | | **Consumption latency** | Compare `timestamp_in_ms` against received time, across quiet and busy periods | | | | **Data freshness** | Compare the `ServerTimestamp` header field against the last update time on your end, across quiet and busy periods | | | | **Uptime** | Feed availability over the full window; note any gaps and their duration | | | Consumption latency, data freshness, and uptime are what matter for almost every evaluation. If other metrics matter to your business, ask your CEM what's worth tracking for your use case. *** ## Evaluation conclusions Phase 4 is your **evaluation summary meeting on Day 14**. Come prepared with your findings per KPI, any blockers ranked by severity, and open questions for the team. This is the time to share your formal decision. {% hint style="success" %} If your verdict is **Go**, bring your proposed start date. We're rooting for it. {% endhint %} *** ## After a Go A Go decision starts your onboarding. Full integration follows the [Integration guide](/u/trade/integration.md): from credentials to go-live, typically a few weeks, with data mapping as the longest phase. All the production-grade work (connection resilience, monitoring, market mapping) is covered there, with your CEM alongside; your CSM schedules the actual go-live date. *** ## Support throughout your evaluation 1. **AI knowledgebase:** tag kapa.ai on your Slack channel for the fastest answers. 2. **Dedicated Slack channel** with your account owner and CEM: tag them directly for anything blocking. 3. **24/7 live chat** with [Support](/u/resources/support.md), available around the clock if your CEM is unavailable. {% hint style="info" %} **FYI:** if you don't use Slack, or don't have a paid workspace, LSports will invite you to ours. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lsports.eu/u/trade/start-here/evaluation-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.