When to use Connect vs Salesforce C&P app?

[Susanna]

I struggle a lot with understanding the relationship between the Connect platform and the Salesforce C&P app. Can you give me a clear distinction between the two? Can we do everything in both places? If I need to do mapping, it looks like that is only in SF, but if I need to create a receipt, that is in two places. How do I know when and where to do the different things I need to do?

For example, we just tried building a receipt in Connect and then when I had questions I can only find information about how to build it in C&P Designer, and now I wonder if we wasted our time. I'd love to read an article that clearly explains when we use which part of C&P. thanks!

[CnP.Support.AM]

Good day @Susanna

Connect is the customer portal for Click & Pledge customers allowing customers the ability to manage their account and fundraisers all in one place. It offers you to create Campaigns and build the forms to raise the funds which also includes the customizable receipts and many more features.

Apart from that we do also have our products in SF. Our app in SF is fully integrated with Connect, all transactions through any Connect forms or API call will post to Salesforce automatically without any user intervention in real time.

Using Autoresponder and C&P Designer, an organization may create an unlimited number of emails eg: Thank You email, Acknowledgement..etc and send them based on the conditions set in C&P Settings. Yes, mapping can be done in SF only not in Connect.

[Susanna]

This is helpful, thanks. Is there an article that goes into more detail about the distinction?

Still confused regarding receipts. It appears that around June our old receipt was automatically replaced by your new gray System Default that appears in Connect. Right now, we've created a Giving Tuesday form that we will embed on our web site. Do we create the receipt in Connect, or do we create it in C&P Designer? Or are they the same? Does it matter?

[CnP.LiveSupport.AB]

Click&Pledge products are available to all nonprofits. Many of our clients do not use Salesforce. Our Donor Management platform in Salesforce is designed to bring in the transaction data, and based on the SF C&P Settings, record it into the correct objects. It's not a sync- it's a data push.

There are many,many ways of creating C&P transaction forms -

• Connect
  • Form Builder - embed donation forms on your site
  • Connect Community forms - an organization home page with the default campaign form and listing of organization Campaigns, allowing for peer-to-peer fundraising.
  • Publish & Post - a way to integrate peer-to-peer fundraising embedded on the organization website without the C&P branding in the C&P Connect Community
  • Connect VT- a way for Organizations can process transactions internally
• Swiper1
• API (uses receipt defined in Connect > Receipt > Receipt Settings > API)
  • Embedded VT (eVT) - typically used to take payments using Auctions for Salesforce.
  • Custom FaaS forms - consultants design web forms that integrate directly with our API
  • GiveBig platform - Method for parent nonprofit organization to run
  • Third party integrations - WooCommerce, Salesforce VT, Salesforce E
  • Events, etc.

All these forms post their data to Salesforce in the same way, with (mostly) the same fields:

The data is sent to the C&P Server to process the transaction. An XML file with transaction data is sent to Salesforce. It creates a C&P Data record with this block of data, and, if needed, a Temp Contact is created. Then it waits to be matched to a Salesforce Contact record. This can happen immediately, or if a match is not found, will happen when the Temp Contact is processed. Once assigned to a Contact, C&P Donor Management (PaaS) creates the Transaction record, allows NPSP to manage Account creation, and creates the Opportunity. The rules for how these are created are set in C&P Settings> Contacts & Accounts, and C&P Settings Opportunity. Once created, Donor Management waits for NPSP to do any updates, and then it comes back in and updates any custom mapping (also set in C&P Settings).


Receipts vs Autoresponders

Receipts and Autoresponders operate independently of each other.

Receipts
Receipt Templates are created in Connect Settings > Receipt > Receipt Builder. The organization's default receipt templates are chosen in Connect > Receipt > Receipt Settings.

A general rule with Click & Pledge is that if settings have conflicting values- the 'more granular' one takes precedent. This is also true of Receipts.

For example -

• You have a Connect > Receipt Settings > API Receipts (the Organization level) set to your 'Salesforce Receipt' template you built in Connect > Settings > Receipt > Receipt Builder
• You have a C&P Event in Salesforce that is assigned to a Connect Campaign on the Basic Information page (Campaign is 'more granular' than Organization). That Connect campaign is set to send out the 'Salesforce Event' receipt you created in Connect Receipt Builder.
• 3rd party applications use the Connect > Receipt Settings > API Receipts setting as the Organization-wide default, whether or not the receipt is sent is set inside the 3rd party app. Thus, sending the receipt is controlled by the 'Send Receipt' checkbox in Events.

RESULT: Registrants buying tickets to the event will receive the Salesforce Event receipt.
If no campaign had been assigned for the event, it would have used the Connect > Receipt Settings > API Receipt template as the Organization default.

AutoResponders
Autoresponder templates are designed in SF C&P Donor Management (PaaS) > C&P Designer. They allow Salesforce users to include fields from the Contact record. The drawback here is that the transaction must be assigned to a Contact in order for an Autoresponder to go out- and it will use the Email (or with NPSP, the field set as Preferred Email) to send the Autoresponder. Autoresponder scenarios that trigger the email are created in C&P Settings > Autoresponder > Email. If a transaction meets multiple scenarios, multiple emails will be sent. If a Receipt is set to go for that kind of transaction- that will go too.

Registration Emails
Registration emails are sent from C&P Events. They allow organizations to include event information not available in the transaction sent to the C&P server (and then posted back to Salesforce). Event management information pretty much stays within the C&P Event objects.

Registration emails do go out immediately, and cannot include information from the Contact record.

I hope this helps- I know there are a lot of places to look for Receipts, and it can be confusing, but this design does allow for a lot of custom flexibility. I do have an article in the works to explain these concepts that will at some point be added to the Knowledgebase.

Regards, ~ C&P Live Support