Connect your Peak Payment account to Referrizer and keep your member and check-in data in sync automatically – no manual double entry.
By integrating Peak with Referrizer, you eliminate the need for redundant data entry and manual syncing. This means you can focus on your tasks within Peak, knowing that Referrizer is handling the rest.
Getting started
Activate Peak Payment Integration
To activate the integration follow the steps below:
- Click on the Integrations option from the drop-down menu next to your name in the top navigation bar
- Find Peak in the list of all available integrations and click START
- Enter the Peak API Key – this key is available in your Peak Payment account
NOTE!
- Engage through texts – enables automated texts to trigger via customer check-ins
- Engage through emails – enables automated emails to trigger via customer check-ins
- Confirm integration by pressing Activate Integration blue button.
Congratulations! You’ve just fully integrated Peak with Referrizer.
NOTE!
- The progress bar for synching your data from Peak to Referrizer will be available on the Contacts page
- Peak data is pulled on a schedule rather than in real time, so changes made in Peak can take up to one hour to appear in Referrizer
Which data will be synchronized?
The list below provides a comprehensive reference of the data synchronization between Referrizer and Peak. The following table outlines all data attributes that are synchronized between the two platforms.
Use this document to understand which specific data elements are transferred in this integration, helping you maximize the functionality of your connected systems. The table shows exactly which fields are supported and in which direction data flows.
This integration includes an Initial sync as well as an Hourly sync.
Peak to Referrizer
The following attributes are synced over to Referrizer from Peak.
Contacts
| First name | Synced initially, Hourly sync |
| Last name | Synced initially, Hourly sync |
| Phone | Synced initially, Hourly sync |
| Synced initially, Hourly sync | |
| Birthday | Synced initially, Hourly sync |
| Peak Source | Synced initially, Hourly sync |
| Contact type (Lead / Current Customer) | Synced initially, Hourly sync |
| Address (Street) | N/A |
| Address (City) | N/A |
| Address (State) | N/A |
| Address (Zip) | N/A |
| Address (Country) | N/A |
| Gender | N/A |
Subscriptions
| Email subscription | Synced initially, Hourly sync |
| Text subscription | Synced initially, Hourly sync |
Visits and bookings
| Checkins (visits) | Hourly sync |
| Last Visit Date | Hourly sync |
| Last Check-in | Hourly sync |
| Peak Member (Y/N) | Synced initially, Hourly sync |
| Number of visits | N/A |
| Referred by | N/A |
| Appointments | N/A |
| Services | N/A |
| Classes | N/A |
| Purchases | N/A |
| Last Purchases Service/Item | N/A |
| Last Purchases Date | N/A |
| Last Booking Name | N/A |
| Last Booking Date | N/A |
| Segmentation (Last Visit) | N/A |
| Membership Comments | N/A |
| Contract Start Date | N/A |
| Contract Name | N/A |
| Contract Expiry | N/A |
| Contract Ended | N/A |
NOTE!
- Peak Source turns your Peak market source code into a readable label on the contact, so you can see where each contact came from.
- Contact type is set from Peak. Anyone whose Peak member type is member comes in as a Current Customer, and everyone else comes in as a Lead.
- Peak Member shows as Yes when the contact is an active member in Peak with a sign date, and No otherwise.
- Text subscription follows the mobile phone texting consent recorded in Peak. Contacts imported from Peak come in as subscribed to email.
- A person in Peak must have at least a phone number or an email address to be imported. Deleted Peak members are skipped on the initial import.
Referrizer to Peak
The following attributes are synced over to Peak from Referrizer. Only contacts newly created in Referrizer that are not already linked to Peak are sent over.
| First Name | Sync on every 10 minutes |
| Last Name | Sync on every 10 minutes |
| Phone | Sync on every 10 minutes |
| Sync on every 10 minutes | |
| Address (Street) | Sync on every 10 minutes |
| Address (City) | Sync on every 10 minutes |
| Address (State) | Sync on every 10 minutes |
| Address (Zip) | Sync on every 10 minutes |
| Address (Country) | N/A |
| Gender | Sync on every 10 minutes |
| Birthday | N/A |
| Tags | N/A |
| Email subscription | N/A |
| Text subscription | Sync on every 10 minutes |
| Input source | N/A |
| Referral type | N/A |
Sync timing
| Initial member import | Once at activation, pulls members from January 1, 2022 through today |
| Member updates from Peak | Every 1 hour |
| Check-in and visit updates from Peak | Every 1 hour |
| New contacts sent to Peak | Every 10 minutes |
Where you’ll see your Peak data
Go to Contacts on the left-hand side of your account and click on the contact’s name to enter their profile. You’ll see Peak Member: Yes or No. Peak Source appears as a custom field, not in that same Peak block. Last visit shows in the contact’s standard visit info.
In Pipeline, accounts connected to Peak can use the Peak Member column and filter, and can build automations that trigger on it. Peak does not support booking, purchase, or contract based Pipeline triggers.
What to do if data isn’t syncing
- Your integration shows as invalid. This usually means the API key is no longer correct. Syncing stops until the key is updated. Re-enter your Peak API Key on the integration page to restore the connection.
- A member from Peak is missing in Referrizer. Check that they have a phone number or an email address in Peak, and that they haven’t been deleted there.
- Your automated campaigns aren’t firing on check-ins. Check that Engage through texts and Engage through emails are switched on. With those toggles off, check-ins still import, but they won’t trigger campaigns.
- A change you made in Peak isn’t showing yet. Peak data syncs hourly rather than instantly. Give it up to an hour before reporting an issue.