Connect Campaign Salesforce Campaign vs Form Salesforce Campaign

[kwclick5]

I'm not sure if this would fit better in the Salesforce forum, but since it deals with Connect set-up, I thought I'd put it here.

When you create a campaign in Connect, there is a place to add a Salesforce Campaign. Then, when you create a form based on that campaign you can also set the Salesforce Campaign data for that form. If you give a gift through the form, which Salesforce Campaign is supposed to attach to the donation (if they are different)? Our settings in Salesforce state to use Transaction Campaign for all donations (criteria Any or Blank SKU).

We were testing payment scheduling yesterday (10/14) on a form that had a different SF campaign in the Connect campaign than in the Form. For the future date recurring gift (started 10/15) and the one-time gift that we set to run the same day (10/14), the SF campaign used was the form campaign (as expected). However, we also entered a future-date one-time gift (to run 10/15) and it came through with the SF campaign on the Connect campaign (not the form). Is that expected behavior?

The future-date one-time gift that came through with the unexpected campaign was 60820-211015091049542. I’ve now updated the opportunity itself to have the right campaign (because of our deposit process), but in the underlying C&P data record you can still see the original campaign.

The future-date recurring gift that campaign through with the correct campaign was 60820-211015091527879.

The form we used is here: https://connect.clickandpledge.com/w...c-ca5b2fca40de

[CnP.LiveSupport.AB]

Hi kwclick5,

When there's a conflict in Campaign assignment, the most granular typically takes precedence:

• CONNECT Campaign Salesforce Setting (one Campaign can have multiple forms)
  • CONNECT Form Salesforce Setting (think of this as representing the transaction as a whole- since filling out a form and submitting it is one transaction)
    • SKU Assignment (representing line items on a transaction)

For the top 2 to work, you have to have a rule set in C&P Settings > Opportunities to "Use the Transaction Campaign". This is because the C&P Transaction record (parent to the Opportunities) is also related to SF Campaigns via a Lookup field. You don't think about it because you don't see roll-up tallies for the C&P Transactions on the SF Campaign like you do for Opportunities.

The other thing to keep in mind is that SF Campaigns get assigned is "when" a transaction arrives in Salesforce and is processed.

CONNECT Campaigns (with their SF setting), Forms (with their SF setting), and SKUs are all "assigned" when the patron submits the transaction
All three get their SF Campaign assignment when the transaction arrives in Salesforce based on C&P Settings > Opportunities.

The easiest way to predict the Opportunity's SF Campaign is to check the rules in C&P Settings > Opportunities.

If you have "Use Transaction Campaign" rules set here, then that rule uses your CONNECT Campaign or CONNECT Form Campaign to assign the Opportunity SF Campaign.
If you have an applicable SKU rule here - then that rule sets the Opportunity SF Campaign.

If you have BOTH ("Use Transaction Campaign" and applicable SKU rules), it depends on the order of the rules. The first applicable rule determines the value.

Make sense?

~ Amanda
C&P Customer Advocate

[CnP.LiveSupport.AB]

kwclick5

As far as the discrepancy between one-time gifts and recurring ones - one-time gifts can have separate SKUs from Recurring - check those in CONNECT Campaign Details > Payment Options.

There can also be a "SKU Suffix" assigned by custom questions - this is appended to the initial SKU. When the transaction arrives in Salesforce - its "SKU" is the "SKU" + the "SKU Suffix".
So that can impact your C&P Settings > Opportunities rules as well.

[kwclick5]

That's how I thought it worked. We have Use Transaction Campaign checked for Any or Blank SKU. We don't have any other rules to assign a Primary Campaign Source in C&P Settings > Opportunities (see screenshot). We also don't have anything set in Custom Mapping to assign a campaign (or other flow automation that would change the campaign).

I also checked the SKUs on the form and they appear to be the same for both one time and recurring gifts. We do have a different SKU for the additional fee and the weird donation was the only one with an additional fee, but as far as I know (and double-checked), we don't have any settings anywhere to change that additional fee SKU to a different campaign. They all use the transaction campaign.

The Connect Campaign SF Campaign was one value (I'll call it Test Campaign 1 for easy reference even though that's not the actual name) and the Form SF campaign was a different value (likewise: Test Campaign 2 for easy reference).

We submitted a total of 3 test donations through that same form (with Test Campaign 2). One ran yesterday and had Test Campaign 2. Two ran today (the regular recurring had Test Campaign 2 and the future date one-time gift had Test Campaign 1). I hadn't made any changes to the form and they both automatically processed within a few minutes of each other this morning. I guess they were both for the same donor, so maybe there was some kind of problem because they were running at almost the same time.

I'm not sure when the rules for Custom Mapping or Primary Campaign Source get run, but the C&P Data record for the strange donation that ran today shows Test Campaign 2 and its ID while the other C&P Data record shows Test Campaign 1 and its ID. Does the C&P data value contain the Campaign Id after the Custom Mapping/Primary Campaign Source rules are run or before?

Is it possible that there is some kind of logic on the C&P side that just affects the campaign of future-date one-time gifts (or future date one-time gifts with additional fee selected)? I suppose I could do another test donation next week to see if it comes through strangely again - if not it might have just been some kind of random glitch.

Thanks for your help!

[CnP.LiveSupport.AB]

kwclick5 ,

That is strange. I reviewed the scheduled payment, and the pre-authorization (60820-2110141511066833988) was correctly assigned to the form's Salesforce Campaign, but the payment associated with it (60820-211015091049542) was assigned to the CONNECT campaign's SF Campaign.

I'm reviewing with our Chief System Architect to see what happened.

[kwclick5]

CnP.LiveSupport.AB Thanks for checking for us! As I said this was just a test donation and generally the Salesforce campaign on the Connect campaign does match the SF campaign on the form in our use cases, so I don't anticipate it being a big problem for us.

But, I wanted to check and see if there was anything I was doing that made it happen that way. I'm pretty sure I didn't make any changes in between that would have made the campaign change, but maybe I did...

[CnP.LiveSupport.AB]

kwclick5 ,

Just an update - I am still looking into this for you. The situation spawned several other conversations, but I should be able to get you a final comment by tomorrow.

[CnP.LiveSupport.AB]

kwclick5 ,

This was identified as a bug, and should be rectified later today. Both the pre-authorization transaction and the scheduled payment are intended to go to the Salesforce Campaign specified on the Form.

~ Amanda

C&P Customer Advocate

[kwclick5]

Great, thanks so much!

[CnP.LiveSupport.AB]

Thank you for bringing it to our attention!