Technical Guide

This page contains technical information for experienced Salesforce Administrators who are looking for a deeper explanation of the key jobs that run as part of the Eventbrite for Salesforce application.

Our integration does NOT use API limits. All syncing to and from Eventbrite is done via outbound calls, these do not count against your salesforce API limit.All syncing to and from Eventbrite is done via outbound calls, these do not count against your salesforce API limit.

Background Jobs

The following table provides a list of Eventbrite for Salesforce batch jobs that can run in the background within Salesforce.

AttendeesBatch

Syncs Eventbrite Attendee and Eventbrite Answers to Salesforce. The data is stored in custom objects Eventbrite_Attendee__c and Eventbrite_Answer__c. It also stores the total orders and events on the Eventbrite Organization object (I.e. Eventbrite_Org__c).

The information in these tables is later processed by RuleBatch which is responsible for created and updating Leads, Contacts and Accounts.

CampaignBatch

Update any linked Salesforce Campaigns with Eventbrite Events for any mapped fields that may have changed since the last sync. It can also auto create Salesforce Campaigns based on Eventbrite Events.

ConfigBatch

This is typically the first job to run as part of the primary sync - it gathers meta data that is used throughout the rest of the sync.

CampaignMembersBatch

Depending on general settings, this can auto create Campaign Member statuses and link and create Salesforce Campaign Members against a Salesforce Campaign based on the Eventbrite Attendee records.

EventsBatch

Responsible for syncing Eventbrite Events, Venues, Ticket Classes and Questions to Salesforce.

OrdersBatch

Syncing Eventbrite Orders to Salesforce (Eventbrite_Order__c) and links them to Events. The Salesforce object Eventbrite_Order__c contains valuable Eventbrite data such as order amount, contact details for the order, tax details etc.

RuleBatch

After the main records have been synced from Eventbrite to Salesforce, this job runs. It determines if Salesforce Leads, Contacts and Accounts are created. By default it won't create any Salesforce records (Leads etc) - this needs to be configured via the Mappings page.

Salesforce Domain Name

If you are using Salesforce Lightning but don't have a Domain set up, you may receive the error similar to this: No CONTROLLER named js://eb4sf.pagination found

Salesforce requires a domain to be set up in order to use Lightning Components (which are used as part of the Eventbrite for Salesforce application). See Enable My Domain To Use Lightning Components

Setting up a Salesforce Domain will remove this message.

This video walks you through setting up a Domain Name.

In this article