Knowledge Base

Customizing Forms as a Service with Connect Campaign Alias

If you are using FaaS, you may want to switch the node WID with the Campaign, so the transactions no longer post to the old WID's reference. If you use the new nodes for FaaS then transactions can post to a set Connect campaign. If you received that notice it means we are seeing transactions posted to the old WID's.

Forms-as-a-Service (FaaS) platform takes advantage of Connect Campaign Alias to minimize the amount of information needed for generating receipts. Through passing the Connect Campaign Alias of a campaign page, various attributes of the Campaign page will be used when generating the receipt through the FaaS forms.

The following links provides the complete list of all form elements needed for processing through FaaS:

it should be like this:

<input type="hidden" name="ConnectCampaignAlias" id="ConnectCampaignAlias" value="WHATEVER"/>

Where "WHATEVER" is the campaign alias as set in the Connect for the campaign.

This ensures that you are using the fraud and receipt setting as set by the Campaign in Connect.

You also do not need this line:

<input type="hidden" name="Campaign1" id="Campaign1" value=" ">

since the above line may easily be adjusted using the SKU you have set, inside Salesforce.

NOTE: To know the Connect Campaign Alias, login to Connect and click on Launcher > Fundraising > Campaigns.