Reporting

in this workshop, we will:  outline the categories of reporting available and provide a general overview of the reporting tools  review the reports currently available in the dashboard  review the filters available to segment reports  discuss ‘use cases’ for reporting and how to implement them  discuss the reports being added and ask for your contribution

four levels of data reporting  individual constituent record  manage supporter page lists transactions  transactions to be added  other aggregate data to be added  single page  donation page  advocacy page  data capture (all sub-types)  groups of pages (campaigns)  ‘attributes’ can be assigned to a page that ties it to other pages  ‘attributes’ being added to report filtering in 3 weeks  account level  overall account, account level by functional area (e.g. fundraising)

reporting options  the focus today is on ‘dashboard reporting’ – as opposed to exporting reports as transactional or constituent data (often used for custom reports)  we recently released a new ‘finance’ tab that allows for quick reports to be generated for download (the same data can also be viewed as a dashboard report)

what’s available now?  account level reports not specific to a functional area  account level and page level data for fundraising  account level and page level data for advocacy  custom filters for: profiles, tracking, and referrer  the attributes filter is being added in the current development cycle  reporting is being moved over in the next development cycle

‘profiles’ filter  the ‘profiles’ feature in your dashboard is used to build segments of supporters based on behavioral and / or constituent data  for example, you may build a ‘profile’ in your account to identify high level donors based on your own criteria  data in the dashboard reports can be filtered to display only data for constituent records that match a specific ‘profile’ you have setup  the ‘profiles’ feature therefore becomes one of the places where you go to build segments for custom reports

‘tracking’ filter  tracking values are identical to ‘source codes’ – they are used to help you measure ROI for marketing channels and generally track transactions by source  tracking values have also been used by clients to associate supporters with specific types of campaigns (e.g. someone interested in health issues in Asia)  a single, or multiple, tracking values, an be added to a page URL  each transaction processed from a tracked URL will store the tracking values in the log data for each supporter

‘attributes’ filter  an ‘attribute’ is something that you assign to a page in order to associate it to other similar pages  for example, you may want to create 6 different fundraising appeals (pages) at year-end and assign them the same ‘attribute’ of 2014_YEAR_END because you want to see report on your ‘year-end’ campaign performance  so assigning ‘attributes’ allows you to roll-up reporting data for a pages that share the same ‘attribute’  the ‘attribute’ function is live in your accounts, even if the reporting filter is not yet available  ‘attributes’ are also being introduced for campaigns in the re-design of the service starting November 1 st

‘referrer’ filter  we are able to track the results of the social sharing done by your supporters through our social sharing icons  for example, if Bob shares your page on Facebook, and his friend Sally clicks through the link shared by Bob; Bob’s Oracle ID is stored along with Sally’s transactional data when Sally converts the page that was shared  this allows you to see the results of social sharing as a percentage of all transactions, and to identify your most influential sharers

let’s dive in! #ENCC15