Force24 Transactional Emails and Custom Objects

Transactional Emails are those that get sent as part of the service, as a result of a transaction or interaction, and normally contains data specific to that event, e.g.

• Order Confirmation – sent after Order is placed, containing details of that Order.
• Invoice Payment Reminder – sent X days after Invoice date, containing the Invoice details.
• Training Course Reminder – sent X days before Training Course date, containing details of the Course.
• Subscription Renewal Reminder – sent X days before Subscription End Date, contains details of the renewal.
• Event Registration Confirmation – sent when someone registers for an Event, containing details of the Event.

Force24 supports the sending of emails like this with their Custom Objects functionality. Custom Objects allow you to store additional details about the contact’s transactions or interactions, which then make this data available to use in filters when building mailing lists, when building journeys, and available to pull into email templates.

Custom Objects are related to a Contact. You can have more than one of an Object attached to a Contact, for example, multiple Event Registrations, each for a different Event and each tracking the Contact’s status for that Event. You can also have more than one Custom Object Type against a Contact, for example, tracking their Event Registrations and the Orders they have placed.

Custom Objects is an additional feature for Force24, speak to your Account Manager about licensing.

The data needs to be synchronised from Workbooks to Force24. To give you control over which records to synchronise and which fields to map, a report is used to drive the sync process. The report contains the record type to be synchronised, the fields to map, and any criteria to restrict which records are sent.

Initially, you’ll need to synchronise all historic data, but on an ongoing basis, you only need to synchronise the records that have been most recent created or updated, so the report limits the results to only the most recently updated. The process will fetch the results from the report and create or update the corresponding Custom Objects accordingly. The Id of the Custom Object will be mapped back onto the Workbooks Record.

The process also handles deletions, if the Workbooks record is deleted the process will delete the corresponding Custom Object record from Force24.

You will need to set up multiple syncs if you have more than one Custom Object type to sync.

1. Create a Force24 Custom Object

First set up the Custom Object in Force24, using this guide Force24 Custom Object FAQs to do so. You’ll need to make note of the id of the new Object and field names for later.

2. Create a Workbooks Report

There are some Template Reports set up to get you started:

• TEMPLATE – Force24 Custom Object Sync – Event Registrations
• TEMPLATE – Force24 Custom Object Sync – Subscriptions

If one of these doesn’t cover your scenario, you need to build a report that contains:

• The Id of the Person that the Custom Object should be related to
• The Id and Lock Version of the Record you are synchronising
• The Updated At of the Record you are synchronising
• Columns for each of the fields that you want to map to the Custom Object
• A criterion to limit the report to only the most recently updated records
• Any other criteria to restrict the data to what’s relevant, e.g. if you only want Event Attendees from certain types of Events, or only Line items for certain Products.

3. Create a field in Workbooks

On the Record Type that you are synchronising, create a Text Custom Field, for storing the Force24 Custom Object Id.

4. Set up a Scheduled Process

Create a new Scheduled Process, using the ‘Force24 Integration’ Script Library script.

Set the Parameters as follows:

• Mode = send_custom_objects
• Custom Objects Report View Name = the name of the report set up in Step 2, including the view name, e.g. “Event Attendees to sync to F24:Details”
• Custom Objects Type Id = the id of the Object you set up in Step 1, e.g. “4145d01f4a”
• Custom Objects Mapping = the mappings between the Force24 field name and the report column api name, with a new line for each field, e.g.
  Event Name : event_name
  • Event Attendee Id : attendee_id
  • Attendee Status : attendee_status
  • Event Date : event_date
• Person Id Column = the api name of the report column that contains the Person Id, e.g. “person_id”
• Record Endpoint = the Workbooks API endpoint for the record type you are synchronising, e.g. “email/mailing_list_entries”
• Record Force24 Identifier Field = the field name of the field created in Step 3, e.g. “cf_mailing_list_member_f24_object_id”
• Record Id Column = the api name of the report column that contains the Id of the record you are synchronising, e.g. “attendee_id”
• Record Lock Version Column = the api name of the report column that contains the Lock Version of the record you are synchronising, e.g. “attendee_lock_version”

Set the Schedule of the process depending on how often the records are updated in Workbooks and how immediately the data needs to be reflected in Force24.

5. Create your Force24 Journeys

The data will now be available in Force24 for you to use in filters when building your Audience, adding Decisions into the Journey, and to pull into Email Templates.

Please see the following pages for examples on setting up a journey for:

• Event Invitation Journey
• Event Attendance Journey
• Subscription/Membership Renewal Journey