How to sync opt-ins between Peppered platform and ticketing

Introduction

• In the Peppered account, when your website has an integrated purchase path.

• In a stand-alone newsletter subscribe flow This can be used if you don’t have website accounts, or in combination with website accounts for visitors who did not (yet) create an account. As soon as a newsletter subscriber creates an account on Peppered, their opt-in will be added automatically to their new account, and the opt-ins will be available in the account environment.

Opt-in sync

• Opt-ins can still be offered on the Peppered website

• Additional opt-ins might be offered within the purchase path of the ticketing system

• If a visitor enables/disables an opt-in in Peppered, they should see that reflected in the ticketing purchase path as well to avoid confusion.

• If a visitor enables/disables an opt-in in the ticketing purchase path, that change needs to be synced to Peppered so the Peppered mailings use accurate opt-in data.

• If a visitor enables/disables an opt-in in the ticketing purchase path, they should be able to see it in Peppered as well in order to change it without having to go into the purchase path.

Opt-in sync details

• Opt-ins set in the Tixly account are synced to Peppered every hour (Opt-in change date-time is compared with Peppered opt-in change date-time. Most recent change is leading). Opt-in logs are also added per visitor in the dashboard.

• Opt-ins can be changed in Peppered by using the “unsubscribe/change preferences” link in the mailing

• Changes in Peppered opt-ins will be synced back to Tixly to update the Tixly account opt-in settings when a Tixly account box-office ID is found in Peppered.

• Stand alone Peppered “Newsletter subscribe” form can be active too, and uses the same opt-ins. If an e-mail address doesn’t have a Tixly account, opt-in settings are not synced back to Tixly

Setup an opt-in sync

• First we need to create an opt-in API connection in the System > API-connections Dashboard module. Click “add” and configure the new connector as follows:

• Now go to marketing -> optins

• click 'display boxoffice optins' in the top of your module to see which opt-ins exist in the ticketing system. The ID’s shown next to each opt-in will be used in the next step in the configuration of the sync:

• Staying in the Opt-in module, decide which existing Peppered Opt-ins you want to use to connect to a Tixly Opt-in. The general “Newsletter” opt-in is usually a good start point. But you can also create new opt-ins in Peppered and link them to Tixly.

• create / edit an optin, set the type to hybrid, set the provider to boxoffice and put a valid remote opt-in ID in the optin code field (see “display boxoffice optins”). Now you are done.

Additional opt-in settings

• check the Visible in subscription management checkbox to show the opt-in on the website.

• Make sure to set all unused opt-ins to “inactive”.

• The Service mail opt-in in Peppered should not sync with Tixly in this way. Just leave it alone, as this opt-in will automatically be set anyway during the offline order import process that runs daily.

• Go to control panel > optins and check if you are using the correct opt-in for your newsletter and servicemails.

• The Peppered system needs to know which opt-in you consider to be the general “newsletter” opt-in. This opt-in will allow all public mailinglists to be shown as preferences within the opt-in.

• The Peppered system needs to know which opt-in you consider to be the general “service mails” opt-in. This opt-in data will be used together with specific event sales data to create service mails mailing lists.