See the field mapping for Loby – Support Heyloyalty

Here you get an overview of the fields the Loby integration populates in Heyloyalty, and where the data comes from in Loby. The fields are prefilled on the setup page, and a field mapping you leave empty is not transferred to Heyloyalty.

You can read how to set up the integration in Set up the Loby integration.

Customer fields

The customer fields link the customer in Loby to the standard fields on your list. The mapping is prefilled for the fields that exist on the list. Contacts are matched on email or mobile number, and a customer without a value in the field you match on is skipped.

Field on the list	Field in Loby	Contents
`email`	`email`	The customer’s email address. Can be used to match contacts.
`mobile`	`mobileNumber`	Country code and phone number combined into one number with digits only, for example 4512345678. Can be used to match contacts.
`firstname`	`firstName`	First name.
`lastname`	`lastName`	Last name.
`address`	`address`	First address line.
`postalcode`	`postalCode`	Postcode.
`city`	`city`	City.
`country`	`country`	Country.
`birthdate`	`birthdate`	Date of birth.

Loby fields

The Loby fields are created on the list when you save the integration.

Field on the list	Field in Loby	Contents
Loby Customer id (`loby_id`)	`id`	The customer’s id in Loby. Locked, as the integration uses it to recognise the contact.
Loby Encrypted id (`loby_encrypted_id`)	`encryptedId`	The customer’s encrypted id in Loby.
Loby Phone country code (`loby_phone_country`)	`phoneCountryCode`	The country code of the customer’s phone number.
Loby Address 2 (`loby_address2`)	`address2`	Second address line.
Loby Birthyear (`loby_birthyear`)	`birthyear`	Year of birth. Number field.
Loby Member number (`loby_member_number`)	`memberNumber`	The customer’s member number in Loby. Number field.
Loby QR code (`loby_qr_code`)	`qrCode`	The customer’s QR code in Loby.
Loby Avatar (`loby_avatar`)	`avatarUrl`	A link to the customer’s profile picture in Loby.
Loby Created (`loby_created_at`)	`createdAt`	When the customer was created in Loby. Date field.
Loby Newsletter consent (`loby_newsletter_consent`)	`subscribedToNewsletter`	Yes if the customer has subscribed to the newsletter in Loby, otherwise No. Also corrected during the nightly reconciliation.

Membership fields

The membership fields are created on the list when you save the integration, but they are only filled in when Include memberships is set to Yes. The fields are filled in with the contact’s most recent membership in Loby, meaning the one with the latest expiry date.

Field on the list	Field in Loby	Contents
Loby Membership id (`loby_membership_id`)	`membership.id`	The membership’s id in Loby.
Loby Membership type id (`loby_membership_type_id`)	`membership.typeId`	The membership type’s id in Loby.
Loby Membership type (`loby_membership_type`)	`membership.type`	The name of the membership type. The options are the membership types in Loby.
Loby Membership cycle (`loby_membership_cycle`)	`membership.cycle`	YEARLY, MONTHLY or INFINITE.
Loby Membership status (`loby_membership_status`)	`membership.status`	active, expiring, lapsed or never. See the explanation below the table.
Loby Membership active (`loby_membership_active`)	`membership.active`	Yes if the membership is active.
Loby Membership valid from (`loby_membership_valid_from`)	`membership.validFrom`	The membership’s start date. Date field.
Loby Membership valid to (`loby_membership_valid_to`)	`membership.validTo`	The membership’s expiry date. Date field.
Loby Membership auto renew (`loby_membership_auto_renew`)	`membership.autoRenew`	Yes if the membership renews automatically.
Loby Membership auto renewed (`loby_membership_auto_renewed`)	`membership.autoRenewed`	Yes if the membership has been renewed automatically.
Loby Membership is renewal (`loby_membership_is_renewal`)	`membership.isRenewal`	Yes if the membership is a renewal of an earlier membership.
Loby Previous membership id (`loby_previous_membership_id`)	`membership.previousMembershipId`	The id of the earlier membership that was renewed.
Loby Preferred renewal type (`loby_preferred_renewal_type`)	`membership.preferredRenewalTypeId`	The id of the membership type the membership should preferably be renewed to.
Loby Payer id (`loby_payer_id`)	`membership.payerId`	The id of the customer in Loby who pays for the membership.
Loby Secondary customer id (`loby_secondary_customer_id`)	`membership.secondaryCustomerId`	The id of a secondary customer on the membership, if there is one.
Loby Membership channel (`loby_membership_channel`)	`membership.channel`	Where the membership was sold: POS, WEB, BACKOFFICE or RECURRING.
Loby Membership order id (`loby_membership_order_id`)	`membership.orderId`	The id of the order in Loby.

The field Loby Membership status is calculated from the membership:

active: The membership is active.
expiring: The membership is active but expires within 30 days.
lapsed: The membership is no longer active.
never: The customer has never had a membership in Loby.

Note: The status is calculated when the contact is retrieved from Loby, and it is only updated when the customer or the membership changes in Loby. Use the date field Loby Membership valid to when a flow should be sent relative to the expiry date.

Ticket fields in the tracking

Tickets and event tickets are imported as purchases in the list’s tracking, and each ticket is its own purchase. The purchase date is the time the ticket was created in Loby, and the contact is found through the field you match on. The tracking fields starting with loby_ and the fields kind, ticket_type, ticket_number, event_start and event_end are created in the tracking when you save the integration.

Tracking field	Field on the Loby ticket	Contents
`order_number`	`id`	The ticket’s id. Each ticket is its own purchase.
`product_id`	`productId`	For event tickets the event’s id, otherwise the ticket type’s id.
`product_name`	`productName`	For event tickets the event’s name, otherwise the ticket type’s name.
`product_price`	`ticketType.price`	The ticket type’s price in kroner.
`product_url`	`event.checkoutUrl`	A link to buy tickets for the event. Event tickets only.
`kind`	`kind`	`ticket` for tickets and `event` for event tickets.
`ticket_type`	`ticketType.name`	The ticket type’s name.
`ticket_number`	`number`	The ticket number.
`event_start`	`event.startDate`	The event’s start date. Event tickets only.
`event_end`	`event.endDate`	The event’s end date. Event tickets only.
`loby_ticket_id`	`id`	The ticket’s id in Loby. Locked field in the tracking.
`loby_customer_id`	`customerId`	The customer’s id in Loby. Locked field in the tracking.

The Loby events product feed

The product feed Loby events is created when you save the integration and contains all published events in your Loby account. Ticket types that are not published are not included in the prices or in TicketTypes.

Field in the feed	From the event in Loby	Contents
`productId`	`id`	The event’s id.
`name`	`name`	The event’s name.
`description`	`description`	The event’s description as plain text.
`imageUrl`	`imageId`	A link to the event’s image.
`url`	`checkoutUrl`	A link to buy tickets.
`salePrice`	The ticket types’ prices	The lowest ticket price in kroner.
`originalPrice`	The ticket types’ prices	The highest ticket price in kroner.
`StartDate`	`startDate`	The event’s start date.
`EndDate`	`endDate`	The event’s end date.
`SaleEndsAt`	`saleEndsAt`	When ticket sales end.
`OnSale`	`onSale`	`yes` if the event is on sale, otherwise `no`.
`SoldOut`	`soldOut`	`yes` if the event is sold out, otherwise `no`.
`TicketTypes`	The ticket types’ names	The event’s ticket types, separated by commas.
`Language`	`masterLanguage`	The event’s language.

Use the fields in Heyloyalty

You now know where data from Loby lands in Heyloyalty. Use the fields in your segments and flows, for example the membership fields for reminders before expiry and the tracking fields for follow-up after an event. See examples and the full setup in Set up the Loby integration.