When you import contacts to MarketHype, you get to decide which subscription type they should be imported to. So, before you continue with the import, we want you to consider the questions mentioned below and read our example of different types of imports;
How do you want to communicate with these contacts?
Should they be stored separately from the rest of your contacts in MarketHype, or can they be imported into the rest of the crowd?
When manually importing contacts to MarketHype, there are two different options helping you divide and maintain a good structure amongst your audience; Subscription types and Custom attributes. These can be used separately or together.
From the start, you have one subscription type, Marketing, where all your audience has been imported from your ticketing/booking system. But you can create new ones depending on your organization's needs.
We have set up different scenarios that we hope will guide you in how to think regarding different types of lists.
Examples
1. Newsletter subscribers
1. Newsletter subscribers
A list of subscribers with freely given consent that have opted-in to receive news from you. You want to import them to the same subscription type as all your customers from the ticketing/booking system since you will communicate with all of them using the MarketHype filter to segment.
Subscription type to import them to: Marketing
Legal basis: Freely given
2. Newsletter subscribers that you want to communicate with separately
2. Newsletter subscribers that you want to communicate with separately
The same list as mentioned above, but instead, you want to keep these separated from the rest of your audience (those with legitimate interest as their legal basis) since you want to communicate more frequently with those who actively chose to receive news from you.
Subscription type to import them to: Create a new subscription type, for example, "Newsletter"
Legal basis: Freely given
3. Professional contacts
3. Professional contacts
A group of professional contacts, for example, sponsors or teachers. They need to be kept separated from others since they take part in another type of communication, only meant for them. You do not have any legal basis from them since they never really opt-ed in, but you have the right to communicate with them.
Subscription type to import them to: Create a new subscription type, for example, "Sponsors"
Legal basis: Freely given
4. Professional contacts with custom attributes
4. Professional contacts with custom attributes
This one goes a bit further than the previous example. Let's say that you have a list of teachers, and not only do you want to import them to their own subscription type, but you also want to communicate separately within the list, for example, depending on what school district they work for. This is done by using both a subscription type and a custom attribute.
When communicating with all teachers, you choose their subscription type in the filter. But, when you want to communicate with specific school districts, you go through Contact attributes in the filter.
Subscription type to import them to: Create a new subscription type, for example, "Teachers"
Custom attribute: Create a new one, for example, "School district"
Legal basis: Freely given
ℹ️ The values for custom attributes are not updated automatically when a contact (as in our example above, starts working for another district). The attribute value is updated once you import another value for the specific contact.
5. Customers for external events
5. Customers for external events
Sometimes you partner up with another venue etc., and they sell the tickets. So, you end up with an external list of customers outside of your ticketing/booking system. For these types, we recommend that you create a custom attribute so you can easily select customers for specific external events instead of having to create separate subscription types for each event.
Before you import the list, you need to create a new Custom attribute. We recommend that you choose the attributes data type to be Multiple choice since a customer might have bought tickets to several external events of yours.
You then need to open your file and add the value for the custom attribute; for this example, it could be "Event name + date" on each contacts row in your file. Making it possible for you to go through Contact attributes in the filter and select the right external event for the right purpose.
Some want to keep external customers separated from their audience and only talk to them regarding their visit. If this is the case, you need to create a new subscription type. You then import all these types of lists to this subscription type and use the custom attribute "External events" to make it possible to choose the right event customers, thanks to the filter.
Subscription type to import them to: Marketing if you want them together with the rest of your audience, or you create a new one that works for all external events.
Custom attribute: Create a new one for all your external events, for example, "External events"
Legal basis: Legitimate interest