Connecting the Jumbo Lottery Platform to Salesforce: Integration & Activation Guide

    Overview

    The Jumbo Lottery Platform (JLP) integrates directly with Salesforce CRM — including Sales Cloud and Service Cloud — using a managed connection via Segment Actions. This integration enables your organisation to maintain accurate supporter records, enrich leads and contacts, and automate workflows triggered by real-time supporter behaviour.

    Jumbo manages the Segment configuration on your behalf. To begin, you simply provide your Salesforce login credentials and configure the relevant object and field mappings. Once connected, JLP events and properties can be mapped directly into Leads, Contacts, Opportunities, or Custom Objects within Salesforce.

    Where Segment Fits

    Segment functions as the data bridge between JLP and Salesforce. As users interact with your digital experience — viewing tickets, making purchases, or updating their information — JLP emits structured events in real time. Segment validates these events and forwards them to Salesforce via the Actions destination.

    This design offers several advantages:

    • No additional tracking scripts or middleware required
    • Events and traits can be mapped to Salesforce objects and fields
    • Updates occur in near real time
    • Jumbo manages the connection upstream

    The result is a consistent, reliable flow of actionable data, directly available within Salesforce for reporting, automation, and supporter engagement.

    How the Integration Works

    1. JLP emits behavioural and server-side events
    2. Segment receives and enriches the data with supporter traits
    3. Segment delivers events to Salesforce using API-based Actions
    4. Salesforce records are created or updated according to your mappings

    You control which events are sent and how they map to Salesforce objects such as Leads, Contacts, Opportunities, Accounts, or Custom Records.

    Events Available

    JLP supports a comprehensive catalogue of real-time events. Below are commonly used examples. A full tracking plan is available on request.

    Behavioural Events (Client-side)

    • Product Added
    • Cart Viewed
    • Purchase Completed
    • Registration Started
    • Email Link Clicked
    • Subscription Cancelled

    Each event includes rich metadata such as draw number, purchase value, recurring status, platform source, and product details.

    Example: Product Added event

    {
      "timestamp": "2025-07-08T03:13:08.308Z",
      "event": "Product Added",
      "properties": {
        "description": "1 Ticket Book",
        "price": 50,
        "brand": "your_charity_lottery",
        "category": "raffle_ticket",
        "draw_no": "1234",
        "recurring_purchase_enabled": false
      }
    }
    

    Server-side Events

    • Recurring Payment Created
    • Recurring Payment Attempted
    • Recurring Payment Succeeded
    • Recurring Payment Failed
    • Order Completed
    • Ticket Purchase Completed

    These events provide a reliable and complete picture of supporter behaviour, enabling real-time CRM updates and automated processes.

    Use Cases in Salesforce

    Once connected, JLP events can power CRM workflows and data enrichment strategies. Example use cases include:

    Lead Enrichment

    Event: Registration Started
    Action: Create or update a Lead record with supporter details such as email, location, and campaign source.

    Contact Activity Tracking

    Event: Product Added or Cart Viewed
    Action: Log engagement against a Contact or update the related Opportunity Stage.

    Supporter Value Insights

    Event: Purchase Completed
    Action: Update a Contact’s total spend, product type, or recurring purchase status.

    Dunning and Churn Prevention

    Event: Recurring Payment Failed
    Action: Trigger a Salesforce Flow to assign a follow-up task to the supporter care team.

    These use cases ensure your CRM reflects real-time supporter activity without relying on manual updates or delayed batch processing.

    Getting Started

    1. Log into Salesforce and create an API-enabled Connected App with OAuth scopes.
    2. Provide your Salesforce credentials and authentication URL to your Jumbo Customer Success Manager.
    3. Jumbo configures the Segment Actions destination on your behalf.
    4. You define the event-to-field mappings with support from Jumbo as needed.
    5. Events begin updating Salesforce records in real time once the connection is active.

    Summary

    FeatureDescription
    Setup requiredSalesforce Connected App credentials (OAuth), object and field mapping
    Managed byJumbo (via Segment)
    Segment’s roleEvent validation, delivery, and record updates via API
    Event typesBehavioural and server-side (full list available on request)
    Use casesLead creation, contact enrichment, activity logging, churn workflows
    Data availabilityReal time

    Need Support?

    If you need help designing field mappings or deciding which events to activate, your Jumbo Customer Success Manager can work with your CRM or data team to guide setup and ensure the integration aligns with your business goals. Together, we’ll help you build a single source of truth for supporter engagement.

    Was this article helpful?
    0 out of 0 found this helpful