Skip to main content

Helix Data Enrichment Sync

Luke Nofsinger
  • Updated

Overview

This feature is designed to augment the standard ticketing integration provided as part of KORE's Fan Engagement product. The Helix Enrichment sync will run in parallel with the ticketing integration and enrich existing CRM Contacts/Person Accounts with Helix Tag & Attribute data.

Included below is a diagram that outlines the flow for the sync.

 

 

 

Important Information:

  • This feature only updates existing CRM records. If Helix Golden Record does not contain a corresponding CRM customer record(s), it will not create a new record with in the CRM.

  • KORE’s standard ticketing integration must be implemented prior to enabling this feature.

  • If a golden record grouping has more than one CRM record associated with it, then all CRM records in the group will be updated with the Tag and Attribute values.

  • Tag and attributes values are aggregated at the golden record level first prior to pushing them into CRM.

    • Sample Scenario #1: A golden record group has two or more ticketing IDs and you create an Attribute for season ticketing spend, then Helix will first calculate that value for each ticketing ID and then aggregate it across all ticketing IDs in the golden record grouping before pushing the value into CRM. The aggregation method is defined when you create the Attribute.

    • Sample Scenario #2: A golden record has two or more ticketing IDs and only one of those ticketing IDs meets the Tag criteria for a current season ticket holder, then that Tag will be pushed to all CRM IDs on the golden record group. This will happen even if the ticketing ID that qualifies for the Tag is not the primary ticketing ID on the CRM record.

  • To enable this feature please reach out to your Customer Success Manager.

Feature Configuration

Selecting your sync Audience

Helix will not automatically enrich every record within CRM. Instead the platform will ask you to define a criteria for which records you'd like to append. You can do this be creating a Helix Audience and defining the criteria for which a golden records should qualify for enrichment. When defining the audience criteria, keep in mind that you can only configure one Audience to sync into CRM. For example, you may want your criteria to look like this:

  • All ticketing customers who have purchased a ticket in the last 5 years
  • Plus anyone who has purchased a merchandise in the last two years and lives within your market (determine by zip code or miles from stadium)
  • Plus anyone who has requested more information on purchases tickets via a webform
  • Plus anyone who has subscribe to a specific set of marketing communication
  • Minus anyone who has specifically opted out of marketing communication.
  • Once you have your Helix Audience created, you will be able to select the audience in the CRM sync configuration page.

image-20240520-145342.png

Additionally, you will need to tell helix which data set is your CRM data set so Helix knows which source IDs to use in order to match to your CRM contact records.

image-20240520-145551.png

Users can only configure one audience to sync into CRM at a time.

Mapping Fields

The final step to configuring this feature is mapping your tags and attributes to their respective fields within CRM. When mapping each tag and attribute please be sure the data type in Helix matches the data type for the associated field in CRM. For example configure an attribute to return a date you’ll want to be sure map that to a date field in CRM.

image-20240520-151034.png

Supported Data Types

Not all CRM field types are supported. Below is a list of supported CRM Field types for each Helix field.

Please Note:

Person Accounts map Person account fields, which are virtual hybrid of Account and Contact fields. Otherwise contact fields are mapped.

 

Helix field Supported CRM types

TAGS
  • any boolean

ATTRIBUTES (numeric)
  • any integer
  • any money
  • any decimal
  • any double
  • any long
  • any percent

ATTRIBUTES (date)
  • any date
  • any datetime

ATTRIBUTES (string)
  • any string
  • any memo

Important Information: The following fields are explicitly hidden:

Dynamics

  • kore_externalcontatid
  • kore_primaryarchticsid
  • kore_archticsids
  • statecode
  • statuscode

SFDC / Person Accounts

  • kores__External_contactId__pc
  • koreps__Primary_Ticketing_account__pc
  • koreps__Ticketing_Accounts__pc
  • CreatedById
  • IndividualId
  • LastModifiedById
  • MasterRecordId
  • OwnerId
  • ReportsToId
  • DandbCompanyId
  • koreps2__SponsorshipIndustry__c
  • PersonContactId
  • PersonIndividualId
  • RecordTypeId

SFDC / Contacts

  • koreps2__External_Contact_Id__c
  • koreps2__Primary_Ticketing_Account__c
  • koreps2__Ticketing_Accounts__c
  • koreps2__Primary_Archtics_Id__c
  • koreps2__Archtics_IDs__c
  • koreps__External_Contact_Id__c
  • koreps__Primary_Ticketing_Account__c
  • koreps__Ticketing_Accounts__c
  • koreps__Primary_Archtics_Id__c
  • koreps__Archtics_IDs__c
  • CreatedById
  • IndividualId
  • LastModifiedById
  • MasterRecordId
  • OwnerId
  • ReportsToId

Refresh Frequency

When creating a Tag or Attribute you can set the refresh schedule to be either once a day or every 2 hours. Each time Helix refreshes the Tag or Attribute and the value changes then Helix will automatically push the updated value to CRM.

image-20240520-151354.png