Events: Represent specific performances, workshops, movie screenings, or fundraisers with date/time and attendance tracking.
Campaigns: Represent broader marketing, fundraising, or outreach efforts that can include multiple events. Relationship: Events can be linked to Campaigns when applicable (e.g., a Campaign to promote ticket sales for a set of Events).
How can I store this in NPSP Salesforce which objects can i used to store these information.
Events has ticket price also which need to be calculated on contact suppose one patron purchase 100 ticket for different events so all the events cost must be calculated on contact.
@Nonprofit Hub #Nonprofit Success Pack ##nonprofit #NonprofitHelp #Nonprofit
Some starting out thoughts:
Roughly: Campaigns, Opportunities, and GAU
I would approach the problem from the perspectives of reporting and user requirements. What data do you need to be able to report on, and what data do users need to see? What goals does the organization want to achieve over time, and how will that be measured?
What software manages event registration, and does it/could it connect to SF? Someone will need to manage a fair amount of data entry otherwise.
Your campaign hierarchy could have parent campaigns based on performance season or something similar, allowing marketing campaigns supporting multiple events to live within the same parent structure as those events. Spend some time working out a hierarchy and testing it against what you have now and how it would look a year or two from now.
Campaign member statuses for attended, etc
Opportunities for ticket sales
GAU on the Campaign
Roll-ups on the Contact
