S120 S-Tags for ECards used in a Donation Form

Hi Jason,

Looks like there is a bug that was discovered after the summer release that is causing some troubles showing those tags you have listed on the Thank You page of the donation form. It might be related to what you are experiancing. I suggest opening a Support ticket and reference bug number 57979 to ask them to confirm if it is related to what you are trying to do or if you just can't use those particular tags in the stationary of an ecard.

To find out what S120 tags work on any particular page (S120 tags are used in autoresponders after transactions) you can drop in this code ] and then process a transaction or view the page and it will render a list of all available S120 tags that can be used on that page. I dropped this into an ecard stationary and the processed a donation where I chose that ecard and below is what appeared in my inbox. I don't see any of the tags you have listed so it could just be that the tags you want to use aren't available but like I said, Support can confirm that for you for sure.

A message from Mr. Ken Cantu

Message

S120:help sees the following valid arguments:

S120:dc:additionalGift

S120:dc:cVSHeader

S120:dc:campaignName

S120:dc:campaignType

S120:dc:city

S120:dc:class

S120:dc:contactInfo

S120:dc:country

S120:dc:designatedAddonFmv

S120:dc:designatedAddonPrice

S120:dc:donationInfo

S120:dc:donationLevelName

S120:dc:donationLevelValue

S120:dc:donorAddress

S120:dc:donorCity

S120:dc:donorCountry

S120:dc:donorFirstName

S120:dc:donorLastName

S120:dc:donorName

S120:dc:donorSpecifiedAmount

S120:dc:donorState

S120:dc:donorStreet1

S120:dc:donorStreet2

S120:dc:donorStreet3

S120:dc:donorSuffix

S120:dc:donorTitle

S120:dc:donorZip

S120:dc:email

S120:dc:employer

S120:dc:firstName

S120:dc:giftAmount

S120:dc:goodsAndServicesValue

S120:dc:honoreeFullName

S120:dc:honoreeName

S120:dc:honoreeTitle

S120:dc:includeGiftAmountInNotification

S120:dc:jointDonation

S120:dc:jointDonorName

S120:dc:lastName

S120:dc:lastPledgePaymentDate

S120:dc:matchEmail

S120:dc:matchFormUrl

S120:dc:matchInstructions

S120:dc:matchPhone

S120:dc:matchingGiftCompany

S120:dc:membershipRenewal

S120:dc:memorialDonation

S120:dc:name

S120:dc:newMembership

S120:dc:nextPledgePaymentAmount

S120:dc:nextPledgePaymentDate

S120:dc:nextPledgePaymentUrlServletPart

S120:dc:numberOfItems

S120:dcriginalTransAmount

S120:dctherAmount

S120:dcaymentAmount

S120:dcaymentMode

S120:dcledgeAmount

S120:dcledgeAmountPaid

S120:dcostalCode

S120:dcremiumName

S120:dcremiumSelected

S120:dcremiumShippingCharge

S120:dcremiumValue

S120:dc:recurringCurrentPaymentNumber

S120:dc:recurringCurrentStatusString

S120:dc:recurringFrequencyLabel

S120:dc:recurringLastPaymentDate

S120:dc:recurringNextPaymentDate

S120:dc:recurringNumberPaymentsCompleted

S120:dc:recurringNumberPaymentsOutstanding

S120:dc:recurringServiceCenterLinkForAR

S120:dc:recurringTotalAmountPaid

S120:dc:recurringTotalNumberOfPayments

S120:dc:recurringTotalPaymentAmount

S120:dc:refundAmount

S120:dc:rewardPointsEarned

S120:dc:salutation

S120:dc:shippingCity

S120:dc:shippingCountry

S120:dc:shippingFirstName

S120:dc:shippingFullName

S120:dc:shippingLastName

S120:dc:shippingPostalCode

S120:dc:shippingStateProvince

S120:dc:shippingStreet1

S120:dc:shippingStreet2

S120:dc:shippingTitle

S120:dc:sponsoreeName

S120:dc:stateProvince

S120:dc:stdDonationThankYouMessage

S120:dc:stdPledgeCompleteMessage

S120:dc:stdPledgePaymentMessage

S120:dc:stdPledgeThankYouMessage

S120:dc:street1 S120:dc:street2

S120:dc:suffix

S120:dc:taxDeductibleValue

S120:dc:taxID

S120:dc:teamRaiser

S120:dc:teamraiserEventName

S120:dc:teamraiserName

S120:dc:teamraiserParticipantName

S120:dc:title S120:dc:trackingCode

S120:dc:transactionDate

S120:dc:transactionID

S120:dc:transactionProcessor

S120:dc:transactionRefNumber

S120:dc:tribute

S120:dc:tributeDonation

Thanks,

Ken

Jason Roberts:

Not the answer I wanted, Ken, but it is pretty much what I figured was the case. Thank you for givng such a detailed response. Based on the output of your S120:help, I'm just going to assume you've hit the nail on the head.

So, here's a follow-up: Is there any way to remove the "A message from John Doe johndoe@doe.com." which gets prepended to the actual message in the e-card? That seems to be hard-coded to the S63 text placeholder when text is dropped into the e-card stationery, and it really ruins the appearance of the e-card. What we're really trying to accomplish is removing that line.

-J.

P.S. I'll go back and mark your above response as the correct answer. Just want to leave it open for now in case there's another workaround we haven't considered.

Hi Jason,

I had to check with one of our web developers but he said he was able to remove the lines you are talking about through the Message Catalog . If you go to Setup > Product Configuration > Message Catalog Editor and in the dropdown application list please choose All Products (at the bottom of the list) and click Refresh List. Then in the search choose "A Message from" and you should find two entries at the top. Choose the one called 'tellafriend:ecard_from_text' and you can modify what is displayed instead of that message or I think you can just put in a HTML comment if you want it blank.

Note: Whatever you change in message catagory will apply site-wide to all ecards.

Hope that works for you,

Ken

Jason Roberts:

Ken-

That's great information. Thank you so much for following-up on this for us.

Nobody on our end has access to Product Configuration, but I've already shot a message to our account rep.

Again, thanks.

-J.

Sure thing.

Also, I should have mentioned that some admin persmissions don't allow access to Message Cat but Support can help you update anything there if you need to or they can set you up with Advanced Site Administrator access if you feel like you want access to those more advanced options.

Ken

Bo Bell:

Howdy Jason/Ken,

I found this thread in looking for more info on gift memberships. I am wondering how you create the records for the gift membership recipients in Convio? I can't find a way to make the honoree a constituent automatically - it looks like I'd have to manuall create those constituents and assign them the membership that was purchased for them. The data sync betyween Convio and our offline DB (PledgeMaker) is making it even more difficult.

Do either of you know a way to make a *true* gift membership, on in which the recipient is not only notified via ecard but has their constituent info properly populated by the form (or one of its elements) (or a script or module or something else)?

Bo

Hey Bo,

Yeah, you can't create 2 accounts at the same time unfortunately which limits what you can automate for gift membership. What I believe I've done for orgs in the past was capture the information in fields on the donation form, then had a fullfillment person run the donations by transaction report and contact those people directly to 'activate' their gift membership. It's been a long time since I've done a project like so I'm a bit fuzzy on why that hasn't been made but the limitation might have to do with one person not being able to opt another person in to receiving email from an organization. I'll try and ask around to clarify.

Ken