The Campaigns section shows the marketing status of the contact.
There are two types of marketing campaigns available in iPoint. A Marketing campaign is designed to be sent to a specific subset of contacts. When the campaign is built contacts are selected to receive that communication. Event-based campaigns are sent to an ever-changing, dynamic email list. This list is adjusted as contacts pass through certain events, like buying a specific product or having a work order advance to a certain status. For more details on campaigns, visit the Marketing section of the manual. 
Mobile: Campaign DefaultsDefaults
On the first tab, you will find information about the contact’s email preferences. An individual contact can opt-out of receiving marketing emails by clicking on the unsubscribe link in marketing emails they receive. Additionally, an employee can manually mark the opt-out checkbox. This makes it possible for you to enter a contact’s preferences when they call in rather than responding to the email themselves.
![]()
OPT-OUT of Marketing Campaigns – a check in this box will keep the contact from receiving marketing emails.
![]()
OPT-OUT of Event-based Campaigns – a check in this box will keep a contact from receiving an email even if they match the rules for the event-based campaign.
.
.
.
.
.
Mobile: Campaign SubscriptionsSubscriptions
The Subscriptions tab shows what email the contact will receive.
Subscriptions with a calendar icon are Marketing campaigns
Subscriptions with a light bulb icon are Event-Driven campaigns
Tap on an individual campaign to open the campaign details. At this point, campaigns are not optimized for mobile devices, so the campaign details open in the standard computer version.
.
.
.
.
.
Mobile: Campaign List MembershipList Membership
This tab shows you which email lists the contact is a part of. If the list is a dynamic email list, you’ll see the recycle icon.
Tapping on an email list will open the list in the Marketing module. Keep in mind that lists are not optimized for mobile devices.
.
.
.
.
.
.
.