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

Overview

The Jumbo Lottery Platform (JLP) supports real-time behavioural and server-side event tracking that powers audience segmentation, lifecycle automation, and personalised journeys in Ortto. These events are delivered through Segment — built into JLP as a managed, secure data pipeline and governance layer.

Jumbo configures the Segment integration on your behalf. To get started, simply provide:

• Your Ortto Tracking API Key
• Your Ortto Workspace ID

Once connected, your Ortto workspace receives structured supporter data in real time — ready for use in onboarding journeys, subscription engagement, retention campaigns, and more.

Where Segment Fits

Segment is embedded in JLP and manages how supporter activity moves from your branded site or app into downstream platforms like Ortto. As players engage — browsing, purchasing, subscribing — JLP emits structured events. Segment:

• Validates the format
• Delivers the data in real time to Ortto
• Ensures consistency across all channels

Benefits:

• No need to configure custom tags or event tracking
• Data is uniform across devices (web, app, mobile)
• Events are delivered instantly, ready for use in Ortto
• Configuration is fully managed by Jumbo

Segment acts as the “pipe,” seamlessly linking JLP activity to your marketing engine — without engineering rework or compromised data integrity.

How the Integration Works

1. JLP emits structured events (behavioural and server-side)
2. Jumbo connects Segment to Ortto using your API credentials
3. Events flow into Ortto in real time
4. You use these events to trigger journeys, create segments, or personalise outreach in Ortto

This setup aligns with Ortto’s Segment-based ingestion model. For technical references, see Ortto’s Segment documentation (external link).

Events Available

JLP provides a wide range of events that support lifecycle marketing, campaign automation, and audience targeting. A full tracking plan is available on request.

Behavioural Events (Client-side)

Captured when supporters engage with your digital experience:

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

Each event includes metadata like draw number, purchase amount, source channel, and subscription status.

Example: Product Added

{
  "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

These system-triggered events are ideal for journeys and lifecycle programs:

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

These ensure reliability and accuracy by reflecting confirmed platform activity.

Use Cases in Ortto

Once connected, Ortto can consume real-time JLP data to drive intelligent supporter journeys. Common use cases include:

Abandoned Cart Journey

• Trigger: Product Added
• Filter: No Purchase Completed
• Timing: Within 30 minutes of Cart Viewed
• Action: Reminder email or push with prize highlights

VIP Welcome for Subscribers

• Trigger: Recurring Payment Created
• Action: Welcome message outlining benefits of recurring entry (auto-play, rewards, reminders)

Loyalty or Upgrade Journey

• Trigger: Order Completed
• Condition: Not currently subscribed
• Action: Email encouraging subscription or VIP benefits

Subscription Win-back

• Trigger: Subscription Cancelled
• Action: Wait 2–4 weeks, then initiate re-engagement with new prizes, impact stories, or offers

These journeys complement existing operational communications from JLP (e.g. receipts, failed payment alerts) — enabling deeper, behaviour-based engagement.

Getting Started

1. Log into Ortto and retrieve:
   • Tracking API Key
   • Workspace ID
     (See Ortto’s setup guide for instructions)
2. Share these details with your Jumbo Customer Success Manager
3. Jumbo will configure the Segment connection
4. Events begin flowing into Ortto, ready to use in:
   • Journey automations
   • Targeted segments
   • Campaign triggers

Adding Ortto Tracking Code

Ortto’s capture widgets are website widgets that help users convert their store or website visitors into subscribers. Capture widgets are configured in Ortto and are designed to appear on a website when specific criteria have been met.

Add the Ortto Tracking Code via GTM

To use widgets, your site must include the Ortto tracking code.
You can implement this using Google Tag Manager (GTM).

1. Follow Ortto’s official tracking code instructions here:
   Ortto Tracking Code GTM Setup
2. Once the tracking code is live, you can create and publish widgets directly from your Ortto workspace.
   Reference Ortto’s detailed guide for widget configuration and embedding:
   Working with Capture Widgets

Summary

Need Support?

If you need help designing your journeys, aligning data with campaigns, or understanding event fields, your Jumbo Customer Success Manager is ready to assist. We’ll make sure you get the most out of your Ortto integration — from day one.