Marketing Data
PolicyEmma Groups
- Files should NEVER be uploaded to an Emma Group that has "(Salesforce)" in the title. Groups with this designation are synced directly with Salesforce reports, meaning any new Contacts uploaded to these groups will be created in Salesforce as well.
- If a new Emma Group is created, Marketing must go into Salesforce > Emma Setup > and deselect the new group BEFORE uploading any Contact data from a file.
- New Emma Groups must be created for any data provided by special request.
- These groups should NOT be synced with Salesforce:
- Degree Plus prospectives (undergraduates)
- HB60
- Return to the U students
- Youth students/parents
- Opt-In lists (new subscriptions from web)
- Marketing should not update any data in the fields imported from Salesforce. Should units needs updates to this data, it will need to be updated in Salesforce, or in PeopleSoft when applicable.
Emma Contacts
- Archived Contacts do not count against Contact limits, and will retain the Contacts opt-out preferences
Sources
| Lucidchart | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Emma Groups
| Emma Group | Data Source | Emma Group parameters | Data points | Emma Group Refresh |
|---|
| Interval | Maintenance | Notes | ||
|---|---|---|---|---|
| 1 | Academic Credit Current Students (Salesforce) | Salesforce | Credit students Past 2 years | First name, last name, uNID, email, zip code, age |
Include Contract? | |||
| 2 | Academic Credit Prior Students | Emma |
|---|
| 3 | Academic Credit Opted-In | Web/Emma |
|---|
| Opt-in from web | ||||
| 4 | Academic Noncredit Current Students (Salesforce) | Salesforce | Non-Credit students Past 2 years | First name, last name, uNID, email, zip code, age |
|---|
| 5 | Academic Noncredit Prior Students | Emma |
|---|
| 6 | Academic Noncredit Opted-In | Web/Emma | Opt-in from web | ||||
|---|---|---|---|---|---|---|---|
| 7 | CECE Staff (Salesforce) | Salesforce | Current CECE staff |
| 8 | ELI |
|---|
| Agent Leads (Salesforce) | Salesforce | First name, last name, email, company, country |
| *Needs to be maintained in Salesforce prior to sync with Emma | ||
| 9 | ELI Partners Leads (Salesforce) | Salesforce |
|---|
| First name, last name, email, company, country | *Needs to be maintained in Salesforce prior to sync with Emma | ||||
| 10 | Go Learn Past Travelers (Salesforce) |
|---|
| Data Team | Any prior participant | First name, last name, uNID, email, zip code, age |
| 11 | Go Learn Opt-In | Web/Emma | Interest form Engaged with Go Learn event | ||||
|---|---|---|---|---|---|---|---|
| 12 | Lifelong Learning Current Students (Salesforce) | Salesforce | LL students Past 2 years | First name, last name, uNID, email, zip code, age |
| 13 | Lifelong Learning Prior Students | Emma | LL students Older than 2 years |
|---|
| 14 | Lifelong Learning Opted-In | Web/Emma | Opt-in from web | ||||
|---|---|---|---|---|---|---|---|
| 15 | Osher Current students (Salesforce) | Salesforce | Enrolled in Osher course Past 2 years Not deceased | First name, last name, uNID, email, zip code, age | |||
| 16 | Osher Past Members | Emma | Prior Osher members |
| 17 | Osher Opted-In | Web/Emma | Opt-in from web | ||||
|---|---|---|---|---|---|---|---|
| 18 | Professional Education Current Students (Salesforce) | Salesforce | ProEd students Past 2 years | First name, last name, uNID, email, zip code, age |
| 19 | Professional Education Prior Students | Emma |
|---|
| 20 | Professional Education Degree Plus |
|---|
| Data Team | |||||||
| 21 | Professional Education Partner List | External Partners | |||||
|---|---|---|---|---|---|---|---|
| 22 | Professional Education Opted-In | Web/Emma | Opt-in from web | ||||
| 23 | Return to the U | Lower Campus | |||||
| 24 | Return to the U Opted-In | Web/Emma | Opt-in from web | ||||
| 25 | Sandy Current Students (Salesforce) | Salesforce | Students taking classes at the Sandy Site Current Term | First name, last name, uNID, email, zip code, age |
| 26 | Test Prep Current Students (Salesforce) | Salesforce | Test Prep students Past 2 years | First name, last name, uNID, email, zip code, age |
|---|
Does not include ACT. | |||||||
| 27 | Test Prep Opted-In | Web/Emma | Opt-in from web | ||||
|---|---|---|---|---|---|---|---|
| 28 | Youth Education | Tableau |
Tableau Data
Catalog Mailing Lists
*All exclude DO NOT MAILS & DECEASED
Subject code (past ESSF)
Date range
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Not Faculty/Staff?
Subject code
Date range
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Osher members 65 and younger that have not taken a LL class?
Calculate # classes per subject area?
Past LL students
Past ANC students
Past GOLRN travelers
Age (>65)
Osher Current Membership (TRUE/FALSE)
Osher Any Membership record (TRUE/FALSE)
Date range based on membership begin date (new this year)
Date range based on membership expiration
Date range
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Subject code
Date range
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Past Youth Ed Class
Subject code
Date range
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
C/O address thing
One per household
- Do we pull lists of faculty/staff for those mailings, or are we just leveraging Campus Mail?
- Unique values?
- Exclude emails?
Additional Data
All undergraduate students without degrees
Applied/Approved for graduation
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Past HB60 students (academic plan)
Age
Zip Codes
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Creating New Emma Groups
| Lucidchart | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Marketing Data Policy
Emma Groups
Data Source = Salesforce
- Do not upload data to any Emma Group that is synced with Salesforce.
- Additional data points coming from Salesforce (such as Age, Zip Code, etc.) should NEVER be edited in Emma. Should units needs updates to this data, it will need to be updated in Salesforce, or in PeopleSoft when applicable.
- Contacts for these groups should NOT be uploaded to any Emma Group synced with Salesforce:
- Degree Plus prospectives (undergraduates)
- HB60
- Return to the U students
- Youth students/parents
- Opt-In lists (new subscriptions from web)
- Data from external sources (Partners, Tableau, Excel files from the Data Team) should NEVER be uploaded to an Emma Group that is synced with Salesforce.
- If new Salesforce reports are needed to connect with an Emma Group, this request must be submitted through the Help Center with the following data points:
- Criteria
- Data Points
- Refresh Schedule
Data Source = Other
- All web forms collecting new subscriptions must be generated and maintained by Marketing through Emma forms.
- New Emma Groups must be created for any data provided by special request or from an external source.
- If a new Emma Group is created, Marketing must go into Salesforce > Emma Setup > and deselect the new group BEFORE uploading any Contact data from a file.
Emma Group Maintenance
- Need to discuss with Marketing how this data in Emma Groups is maintained
Emma Contacts
- Emma Contacts should Archived and not Deleted
- Archived Contacts do not count against Contact limits, and will retain the Contacts opt-out preferences
- New email list subscribers will be synced with Emma Groups created specifically for managing this list. This data will not be synced with Salesforce.