Learn the enhancements included in Give Lively’s Salesforce app v1.3

A helpful overview of the new custom objects and fields in version 1.3 of Give Lively’s Salesforce app. They allow greater access to Give Lively data without ever leaving Salesforce. Additionally, this new version of the app bundles a pair of permission sets that facilitate the process of granting access to users, and fully supports the syncing of donations from peer-to-peer and team fundraising pages.

No items found.

Before You Get Started

Video Overview

Text Walkthrough

NOTE: For a full list of fields, as well as a detailed walkthrough of the sync process, refer to this article.

Ticket tiers

The app will sync ticket tier information and relate tiers to ticket purchases whenever they are made.

Example fields:

  • Price
  • Seats Per Ticket
  • Availability Start
  • Availability End

Ticket purchases

As before, Opportunity records will be created when donors purchase one or more tickets, representing the total purchase amount. Beginning with version 1.3, individual ticket purchases will be tracked in their own custom object, and related both to the Opportunity as well as their respective tier(s).

Example fields:

  • Ticket Tier
  • Date of purchase
  • Price
  • Opportunity

Opportunities

In addition to syncing with standard Salesforce Opportunity fields, version 1.3 bundles many new Opportunity-level fields, surfacing data previously only available on the Give Lively portal.

Example fields:

  • Net Amount
  • Transaction Fee Covered by Donor
  • Page Type
  • Page URL
  • Text Code
  • Anonymous to Public
  • UTM Source
  • Honoree Contact (existing NPSP fields now supported)

Campaign hierarchy

Give Lively campaigns, events, and team and peer-to-peer fundraisers now sync using Salesforce’s campaign hierarchy model. Organizations will be able to use Salesforce’s built-in summary fields to see how donations from individual fundraisers and events roll up to parent campaign totals.

Permission sets

Two permission sets are now bundled with the app. One provides full access to all fields and app elements, and is intended to be assigned to the integration user, minimizing the potential for access-related syncing issues. A second more limited permission set provides access for end-users, granting access to newly added fields.

Downloads

Get Inspired

No items found.

Related Articles