Announcement

Collapse

Information Needed

See more
See less

Linking Donation Form to a Salesforce Campaign

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linking Donation Form to a Salesforce Campaign

    There seems to be many places on the Donation form, the Campaign setup and/or the C&P settings where you can link a donation page to a Salesforce Campaign. However, the only one I can get to work is in the C&P settings where you map a SKU to a Campaign. Is that the only place that works? Because often times we have a lot of campaigns and I would prefer to just link forms to a Campaign. But it seems like that feature does not work and I have to create a new SKU for each payment type for every Campaign I create...seems like a lot. Is this the right way to do it?

  • #2
    Good day @OneTenthConsulting

    Would you please share the link URL of your donation page so that we can better assist you?

    Looking forward to hearing back from you.
    Regards,
    Click & Pledge Support Department

    On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

    Join us @ the educational webinars: https://clickandpledge.com/webinars/
    Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
    Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

    Comment


    • #3
      The pages are not live yet, but my question is more broad. Where do we establish a link between the Salesforce Campaign and the C&P Campaign:
      Is it here: https://www.screencast.com/t/oZ2huCxrkTr
      Is it here: https://www.screencast.com/t/Qw9eMTk7HV
      Is it here: https://www.screencast.com/t/vcpnfyDL0

      Right now only the last one seems to be working, but that seems cumbersome to have to create a new set of SKUs every time I want to point a page to a different Salesforce campaign.

      Comment


      • #4
        Yes, there are a couple of ways that you can assign the SF campaign. The first one you mentioned above is where you can assign the SF Campaign to the Connect Campaign so that all the transaction processed through that Connect Campaign includes that SF Campaign. The second one is specifically for a particular Form and it doesn't apply to the whole Connect Campaign/other forms. The third one is where you can map through SKU.

        If you want to assign the same SF Campaign to all of the forms which comes under that Campaign then you NO need to define the SF Campaign in Form Builder (second image). When you assign the SF Campaign in the form builder then that will be the priority over the Campaign Details(first image).

        Hope that makes sense. Please let us know if you have any questions.

        Regards,
        Click & Pledge Support Department

        On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

        Join us @ the educational webinars: https://clickandpledge.com/webinars/
        Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
        Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

        Comment


        • #5
          I'm still not clear.
          1. If I want all transactions from a from to be attributed to the same SF campaign, which approach should I use - 1, 2, or 3?
          1. Do I need to take the SKU approach at all then (3)? Does that take precedence over approach 1 or 2?

          Comment


          • #6
            SKUs are really the best way, once you understand the concept of them. Think of them like the code on a grocery receipt that tells you what you bought.
            Basically, you assign the SKU when you are tagging the price choices on your form with a code, and in Salesforce C&P Settings you create rules for how to handle transactions that come in with that SKU.

            Tutorial: http://tutorial.productions.clickand...ideo/209074427

            If you start with a SKU 'schema' then you can just manage all your Salesforce campaign stuff in Salesforce > C&P Settings, and it makes it easier to map fields into Salesforce too.

            Samples of nonprofit SKUs:
            • DON-GEN : think General Donation. You might use this for all your Amount buttons ($10, $25, $50) and "Other" on your Connect Campaign.
              • In SF, you might set up rules like:
                • If SKU starts with 'DON', assign the Opportunity a Donation Record Type
                • If SKU is 'DON-GEN', assign it to the 'Website Donation' Campaign
            • DON-HON, DON-MEM : an 'in Honor' Donation. You might set this on a Campaign specifically for donating in honor of someone, adding custom questions to collect information about the Honoree. In Salesforce, the Opportunity. For your Connect Campaign amounts, you'd set the SKU to 'DON', and then your custom questions might ask if the donation is in honor or in memory and collect the information of the person to notify. In this case, you'd make use of the custom question SKU Suffix feature, which adds the SKU suffix to the end of the SKU. So your question to select "in Honor" or "in Memory" would have a SKU Suffix of "-HON" or "-MEM"
              • Rules in SF
                • If SKU starts with 'DON', assign the Opportunity a Donation Record Type
                • If SKU is 'DON-HON', set your custom Opportunity Tribute Type field to "in honor"
                • If SKU is 'DON-MEM', set your custom Opportunity Tribute Type field to "in memory"
                • If the custom question is "Who should we notify about your gift?", assign the answer to the "Notifyee" field
                • If SKU is 'DON-MEM', set your custom Opportunity Tribute Type field to "in memory"
            • DON-MEMBER : use for selling Memberships
              • Rules in SF
                • SKU is 'DON MEMBER', assign the Membership Record type and add to the Membership campaign.
            • DON-DirectMail-Winter: for your December Mailing
              • Rules in SF
                • Assign Donation Record Type, and assign to the 2019 Winter Campaign
                • Note that by creating a Connect campaign that doesn't specify the year, next year you can just use the same form, and change your SF rule to the 2020 Winter Campaign.
            ​​​​​​​
            So I highly recommend going the SKU route, and just ignore the Salesforce Campaign settings in Connect.

            Regards,
            Click & Pledge Support Department

            On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

            Join us @ the educational webinars: https://clickandpledge.com/webinars/
            Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
            Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

            Comment


            • #7
              This is just a copy and paste from your documentation. It is not helpful. I am asking a specific question:
              1. If I want all transactions from a from to be attributed to the same SF campaign, which approach should I use - 1, 2, or 3?
              2. Do I need to take the SKU approach at all then (3)? Does that take precedence over approach 1 or 2?

              Comment


              • #8
                Yes, in case of SKU mapping, it will take precedence over approach 1 and 2. The best way in all the cases is to go with approach 3.
                Regards,
                Click & Pledge Support Department

                On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

                Join us @ the educational webinars: https://clickandpledge.com/webinars/
                Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
                Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

                Comment

                Working...
                X