Virtuous Integration - Peer-to-Peer

When a donation is made through a Peer-to-Peer (P2P) fundraising page, the integration determines which communication and segment the donation should be attributed to based on the campaign hierarchy and campaign configuration.

This ensures that donations are reported correctly for individual fundraisers, teams, and parent campaigns.

Key Concepts

Campaign hierarchy
- Parent (Master) campaign
- Child campaign (individual fundraiser or team page)
- Grandchild campaign (team member under a team page)
Communication
- Represents the high-level P2P campaign or team in Virtuous
Segment
- Represents the specific fundraiser or team page within a communication.
- Donations are always assigned to a segment.

When P2P Processing Occurs

P2P logic is applied when:

The donation is associated with a team or an individual fundraiser campaign

If the donation did not originate from a P2P page, standard (non-P2P) processing applies instead.

TL;DR

If “Allow Grandchildren” / "Fundraiser Teams" option is enabled:
Teams get their own communications, and individual fundraisers get their own segments under the team’s communication.
If “Grandchildren” is disabled:
All fundraiser pages are under the master campaign and all P2P donations use one master communication, and segments alone distinguish individual pages.

P2P Attribution Decision Table

Campaign Setting	Donation Origin	Communication Used	Segment Created / Used	Resulting Attribution
Allow Grandchildren = Yes	Child campaign (team or individual page)	Dedicated communication for the child campaign (created if missing)	Segment named after the child campaign	Donation attributed directly to the child’s communication and segment
Allow Grandchildren = Yes	Grandchild campaign (individual under a team)	Parent (child) campaign’s communication	Segment named after the grandchild campaign	Donation attributed to the individual fundraiser while rolling up under the team communication
Allow Grandchildren = No	Child campaign	Master campaign communication	Segment named after the child campaign	Donation attributed at the segment level only
Allow Grandchildren = No	Grandchild campaign	Master campaign communication	Segment named after the grandchild campaign	Donation attributed at the segment level only

Scenario 1: Campaign Allows Grandchildren / Fundraiser Teams

In this configuration, the campaign supports multi-level P2P fundraising (teams and individual fundraisers under teams).

Child Campaign (Top-Level P2P Page)

A dedicated communication is created for the child campaign (if one does not already exist).
A segment is created under that communication using the child campaign’s name.
Donations from this page are assigned to that segment.

Grandchild Campaign (Team Member Page)

The donation inherits the communication from its parent (child) campaign.
A separate segment is created for the grandchild campaign under the parent’s communication.
Donations are attributed to the grandchild’s segment while remaining grouped under the team’s communication.

Result:
Each team has its own communication, and each individual fundraiser has their own segment within that team.

Scenario 2: Campaign Does Not Allow Grandchildren (No Fundraiser Teams)

In this configuration, multi-level P2P pages are not treated as separate communications.

All P2P donations use the existing master communication for the campaign.
A segment is created per P2P page (child or grandchild) under that master communication.
Donations are attributed only at the segment level.

Result:
All P2P activity rolls up into a single communication, with segmentation used to distinguish individual pages.

How the Final Attribution Works

For every qualifying P2P donation:

The system determines the correct communication based on campaign hierarchy and configuration.
It looks for a matching segment by campaign name under that communication.
If the segment does not exist, it is created automatically.
The donation is assigned to that segment for reporting and downstream processing.

Examples to clarify mappings:

3 fundraiser pages:

1) Master Campaign: Fall Marathon

2) Child Campaign (someone created a team under Master Campaign): The Microsoft Team

3) Grandchild Campaign (someone created a campaign under the "The Microsoft Team" child campaign): The Smith Family Team

Example Mappings:

Master Campaign mapped to Virtuous:

Campaign -> Campaign 1

Communication -> Communication 1_1

Segment -> Segment 1_1_1

Donation & Sync Scenarios:

1) A direct $100 donation on the Fall Marathon page:

Virtuous Gift:

Campaign -> Campaign 1

Segment -> Segment 1_1_1

2) A donation to The Microsoft Team page ("child campaign"):

Virtuous Gift:

Campaign -> Campaign 1

Communication -> "The Microsoft Team" (created or used - under Campaign 1)

Segment -> "The Microsoft Team" (created or used - under "The Microsoft Team" communication)

3) A donation to The Smith Family Team page ("grandchild campaign"):

Virtuous Gift:

Campaign -> Campaign 1

Communication -> "The Microsoft Team" (i.e. parent campaign - created or used - under Campaign 1)

Segment -> "The Smith Family Team" (created or used - under "The Microsoft Team" communication above)