DocumentationExperience PlatformSource Connectors Guide

[Beta]{class="badge informative"}

LAVA

Last update: May 15, 2026

CREATED FOR:

  • Developer
AVAILABILITY
The LAVA source is in beta. Read the terms and conditions in the sources overview for more information on using beta-labeled sources.

LAVA is a customer engagement platform. LAVA integrates with your ticketing, point-of-sale, mobile app and other touch points and creates moments that matter with our automation, loyalty and mobile pass solutions.

The LAVA source connector can be used for several different sets of profile data and events. You can decide which are relevant for you. For each type of data you would like to stream from LAVA to Adobe, repeat the “Connect your LAVA account” steps.

Prerequisites

Before you can use this source connector, ensure the following:

  • You are an existing LAVA customer and have been granted Adobe export rights.
  • You have a LAVA Console account with either “Administrator” or “Export Manager” access.
  • (Recommended) You have sandbox manager permissions in Adobe Experience Cloud.

Member Profiles

The member profile lists key profile attributes LAVA stores on a member. By using email as an identity field, Adobe Real-time Customer Profiles can stitch LAVA records with other Adobe profiles.

Download the sample Member Profiles data file here.

LAVA Source Connector Field
Sample Value
Description
lavaId
c448e091-af0f-4eab-98ff-2c758c149051
The LAVA ID for the user.
firstName
John
The user’s first name.
lastName
Doe
The user’s last name.
email
jdoe@example.com
The user’s email address.
phone
+12223334444
The user’s phone number.
type
profile
An indicator for what type of record this is.
id
c448e091-af0f-4eab-98ff-2c758c149051
A unique ID for the record.
timestamp
2025-10-22T12:51:04.317084Z
When the profile had these attributes set.

Member Balances

The member balance source lists balances of rewards your members have. balances is an array. When using these in audiences, content personalization, conditions and other such locations, you will often have to either select out one particular entry, repeat something for all entries, or aggregate across several entries.

Download the sample Member Balances data file here.

LAVA Source Connector Field
Sample Value
Description
lavaId
c448e091-af0f-4eab-98ff-2c758c149051
The LAVA ID for the user.
balances[]
-
List of reward balances in LAVA. A balance is an instance of a reward with a specific expiration. If a member has some amount of reward expiring on date A and some amount of the same reward expiring on date B, they will be recorded as separate balances. See balanceSummaries for an aggregation.
balances[].amount
500
The amount of reward items in this balance. For stored value, this is in the lowest unit of denomination (cents).
balances[].expiresAt
2025-10-22T12:51:04.317084Z
When this balance expires.
balances[].rewardId
123
The ID for a LAVA reward. This never changes for a given reward.
balances[].rewardName
F&B Credit
The name for the reward configured in the LAVA Moment Activation Console. This can be changed.
balances[].rewardSlug
Credit
The primary slug for the reward configured in the LAVA Moment Activation Console. This can be changed.
balances[].rewardType
stored
The type of reward (access, offer, points, stored or voucher).
type
rewards
An indicator for what type of record this is.
id
8fefe232-0375-4d56-a24c-d009e9d351e8
A unique ID for the record.
timestamp
2025-10-22T12:51:04.317084Z
When this data was recorded.

Ticket Scan Events

The ticket scan event source provides detailed information each time a member scans a ticket at an event. This data can be used to understand attendance, engagement, and behavior patterns at specific venues or activities. By streaming ticket scan events to Adobe Experience Platform, you can augment member profiles and enable event-driven personalization or analytics. Each scan event record includes metadata about the event, the venue, as well as where and when the scan occurred.

Download the sample Ticket Scan Events data file here.

LAVA Source Connector Field
Sample Value
Description
lavaId
aff0ee5f-da62-4054-8cdb-076f5b60bfc3
The LAVA ID for the user who scanned the ticket.
eventId
1234
Identifier for an event provided by a ticketing service.
eventName
GRE1234A
The event name provided by the ticketing service.
eventLabel
Green Vs Blue
Description of an event as provided by the ticketing provider.
venue
ABC
Venue code used by the ticketing provider.
venueLabel
ABC Stadium
Description of the venue as provided by the ticketing provider.
section
GA4
Seating section on the scanned ticket.
sectionLabel
General
A label for the section provided by the ticketing provider.
row
GA3
Row on the scanned ticket.
seat
13
Seat on the scanned ticket.
gate
TEAM ST1
Gate on the scanned ticket.
gateLabel
General
A label for the gate provided by the ticket provider.
type
event-ticketscan
An indicator for what type of record this is.
id
1234567/GRE1234A/GA4/GA3/13/0
A unique ID for the ticket scan event.
timestamp
2025-11-03T01:41:00Z
When the ticket scan occurred.

Load the LAVA package

LAVA provides a package that includes our recommended field groups, schemas, identity namespace and datasets for using LAVA in Experience Platform. Use of these packages is recommended, but not required.

To load these packages, in the Experience Platform UI, select Sandboxes from the left navigation to access the Sandboxes workspace. The Packages screen displays available packages. Select Create package and Paste package payload and paste the following.

{
  "imsOrgId": "1EF71E43679AAD1E0A495C77@AdobeOrg",
  "packageId": "416a0c2a32794092aa1a957cbe9a6698"
}

For more information on loading the package, read the package sharing tutorial.

After the package is created, select the ellipses (...) to open the menu and select Import Package to import the package. For more information on how to import a package, refer to the sandbox tooling guide.

Next steps

The LAVA source connector ingests member profiles, reward balances, and ticket scan events into Experience Platform. Plan for the listed prerequisites, map and extend schemas using the field reference tables and sample JSON files, and optionally import LAVA’s recommended package into a sandbox before you create connections and dataflows.

For step-by-step setup:

recommendation-more-help
experience-platform-help-sources