Peer to Peer - Transaction Types & Rows
In the updated peer-to-peer platform, we have developed a new set of campaign types to clearly distinguish them from other campaigns within the system. These transaction types will be included in all export processes (ex. Query Export, Financial Export, API and so on…) within Engaging Networks, making it easy to identify which transactions were created or completed by a supporter or fundraiser in your account.
Each transaction item includes the four-letter Campaign type, reference name of the transaction (such as site name or page name). The table below illustrates what these different Campaign Types are how they are created on a record for Peer To Peer Transactions.
Campaign Type | Name | Occurence | Primary Use |
---|---|---|---|
PSTE | Peer-to-Peer Site | On creation or update of a site | Representing a primary Peer-to-Peer campaign object. Would represent a Peer-to-Peer site inside Salesforce or other CRM. The Site name, fundraising goal and currency, structure (team options of IND | BOTH) and type (EVENT | DIY) are indicated, allowing the primary campaign to be kept current and up to date. |
PFRP | Peer-to-Peer Registration - Primary | When a fundraiser registers. | Indicates a fundraiser's registration, calling out the Page ID, Page Name, Site Id, Site Name. This allows Salesforce to setup a campaign representation for the fundraiser, against a site and link a CampaignMember + Contact record to it. |
PFRA | Peer-to-Peer Registration - Associated | Additional members are associated with a registration. | When a person is registering themselves and family members, PFRA would represent the associated participants in the cart |
PPAY | Peer-to-Peer Registration Payment | When a fundraiser registers and pays for participation type. | If the organization is running a site which requires a fundraiser to pay an initial amount to take part, then this transaction represents that payment for that participation type. Note that this payment would also help with ‘minimum commitment’ fundraising, where an organization sets an expectation upfront that the fundraiser will need to meet a minimum fundraising commitment. |
PACS | Peer-to-Peer Self Additional Donation | When a fundraiser registers and chooses to make an additional donation (single). | During the registration, a fundraiser can choose to make an additional donation. Fundraisers who make donations to themselves are often seen as more committed to the fundraising efforts and have a greater chance of being more engaged. Note that Engaging Networks processes one payment to the gateway during registration, which means that the transaction id will be the same for both the registration payment and the additional donation, even though they are represented separately here. |
PACR | Peer-to-Peer Registration Additional Donation Recurring | When a fundraiser registers and chooses to make an additional donation (recurring). Noted for future development. | At this time, only a single donation is supported during registration. A recurring donation transaction would be occur according to a schedule set up by the supporter, represented by a transaction row such as this. |
PFTC | Peer-to-Peer Team Create | When a team is created. | When a team is created at the site level, this row indicates this occurrence and allows Salesforce to create a team page representation. Notable values includes the team’s page id, page name, team goal, site id and site name. |
PFTA | Peer-to-Peer Team Member Addition | When a member joins a team. | When a team captain/member is added to a team, this row allows Salesforce to roll members of a team onto the team page representation. Notable values includes the page id of the fundraiser, and whether this fundraiser is the captain or an ordinary member of the team. During registration, if a fundraiser decides to create a team, expect both the Team Create and Team Member Addition row to be indicated. |
PFTE | Peer-to-Peer Team Member Exit | When a member leaves a team. | When a team captain or member is removed from a team, this row allows Salesforce to remove these fundraisers from the team page representation. |
PORG | Peer-to-Peer Organization | When an organization is created at the account level. | Organizations (such as Companies, Departments, etc.) are created at the account level, and can be enabled for sites through registration selection options. These entities exist at the account level, and once associated with a specific site, they are assigned a page ID corresponding to that particular site. As each organization has its own ID at the account level, associated pages roll up to enable cross-site and year-on-year reporting of organizational data. |
PFOC | Peer-to-Peer Site Organization Create | When an organization is associated in a site. | When an organization is associated at the site level, this row indicates this occurrence and allows Salesforce to create an organizational page representation. Notable values includes the page id, site id and site name, organization entity name and id as well as goal pulled from the account level. It is important to understand that at the site level, this page is a reflection of the account level entity. Meaning, the logic grabs the snapshots of the default values from the account object. |
PFOA | Peer-to-Peer Site Organization Association | When a team or fundraiser is linked to a site’s organization page. | When a team, team captain/member or fundraiser select the organization, this row allows Salesforce to roll page ids to the organization’s page representation. |
PFOE | Peer-to-Peer Site Organization Exit | When a team or fundraiser leaves a site’s organization page. | When a page is unassociated from an organizations page , this row allows Salesforce to remove page of a team from the organization’s page representation. |
TPPU | Team Peer-to-Peer Page Update | A team captain updates the team’s page in the fundraisers dashboard | Inside the fundraisers dashboard, when a team captain saves the team page details (which include goal, team story, title etc) this rows allows Salesforce to keep updated details of the team’s page. A good example here would be goal - if the team’s page goal changes, this can be additionally reflected in Salesforce. |
IPPU | Individual Peer-to-Peer Page Update | When a fundraiser updates their page in the fundraisers dashboard | Inside the fundraisers dashboard, when a fundraiser (which could include a captain, member or individual) saves the team page details this rows allows Salesforce to keep updated details of the fundraiser’s page. A good example here would be goal - if the fundraiser updates their goal, this can be additionally reflected in Salesforce. |
OPPU | Organization Peer-to-Peer Page Update | When an administrator updates the organization’s page, at the site level. | From the administrator tile, when an administrator updates the site page details, this rows allows Salesforce to keep updated details of the organization’s page . Note that organization pages are not accessible to fundraisers. They are currently controlled by administrators. |
PFCS | Peer-to-Peer Credit Single | When a donation is made as a single gift | A donor making a single gift. Notable values includes the page id of the fundraiser that his gift should be associated with. As this is the page id, this could link either a site’s organization page, team page, team captain/member page or a fundraiser’s page. |
PFCR | Peer-to-Peer Credit Recurring | When a donation is made as a recurring gift. | A donor making a recurring gift. Notable values includes the page id of the fundraiser that his gift should be associated with. As this is the page id, this could link either a site’s organization page, team page, team captain/member page or a fundraiser’s page. |
PFCA | Peer-to-Peer Fundraising - Cash | When a donation is made as a offline cash gift. | A site administrator or donor making a single cash gift. Notable values includes the page id of the fundraiser that his gift should be associated with. As this is the page id, this could link either a site’s organization page, team page, team captain/member page or a fundraiser’s page. |
PFCH | Peer-to-Peer Fundraising - Check | When a donation is made as a offline check gift. | A site administrator or donor making a single check gift. Notable values includes the page id of the fundraiser that his gift should be associated with. As this is the page id, this could link either a site’s organization page, team page, team captain/member page or a fundraiser’s page. |
PRFD | Fundraising - Refund Single/Recurring | When a donation is refunded. | |
PFIM | Peer-to-Peer Fundraising - In Memoriam | When a donation includes 'In Memory' information. | When a donor indicates that the gift is made in memory of a person, then this additional row indicates the individuals details. The Opportunity in Salesforce can be updated to reflect a tribute gift and the Honoree Name being written to the sObject. Note that this row should not be used to represent a transaction - even those it has donation data included. |
PITM | Peer-to-Peer Fundraising - Incentive Item | When a fundraiser accepts or declines a premium reward in their fundraisers dashboard. | Allows Salesforce to keep track of premium rewards that have been accepted and/or declined for fulfillment purposes. |
You can see more about these Campaign Types in a supporter’s Transaction History Gadget or in the Export Transaction Data Template.