As explained here, a contact is a user for which we know at least an email address.
Every contact has other attributes, other information you can play with:
-
Attended event XXX: Filter contacts who attended a specific event. Given that a contact may have attended several events, we don’t display a list of attended events in the contacts list. But you can filter on this attribute anyway to segment your community.
-
💡 You can still access the list of all tickets and events attended by any contact by clicking on them in the contacts list
-
-
Area: Geographical zones (slightly bigger than cities). Based on the ip address during sign up, updated at every purchase
-
Age: Birthdate asked on first purchase
-
Gender: Male, Female or Other / Non-binary
-
Tickets bought: How many of your events’ tickets did this user ever hold? (bought or received invitation, or group ticket)
-
Total spent: How much did this user spend on your events tickets?
-
Is follower: Does this contact follow your organiser page on Shotgun? 💡 We highly recommend you to share it on your website, social media and communications to attract more contacts to your community!
-
Is subscribed to newsletter: Is this contact subscribed to your newsletter? i.e: will s·he receive any marketing email you're sending out? 💡 When importing contact via csv file, you can consider them as subscribed or not.
🇪🇺 In Europe, you need explicit consent from contacts to consider sending them emails (GDPR regulation)
💡 We prompt users to subscribe to newsletters and push notifications when they follow your organiser page or buy tickets
🇺🇸 In US & 🇧🇷 Brasil, contacts are automatically subscribed to your newsletter when they buy a ticket.
-
Is subscribed to push: Is this contact subscribed to your push notifications?
💡 We prompt users to subscribe to newsletters and push notifications when follow your organiser page or buy tickets.
-
Contact added date: When was this contact added to your community? (ticket received at, date at which followed page, date of csv import)
-
User language: Locale defined by the user on his app or desktop
Any question, comment, feedback on this feature? Please let us know here, we’ll get back to you very shortly!
