Treatment type: Heart Transplant/VAD
Service email recipient: cttransplant@upmc.edu
Treatment type: Lung Transplant
Service email recipient: cttransplant@upmc.edu
Treatment type: Intestinal (small bowel) Transplant
Service email recipient: transplant@upmc.edu
Treatment type: Liver Transplant
Service email recipient: transplant@upmc.edu
Treatment type: Pancreas Transplant
Service email recipient: transplant@upmc.edu
Treatment type: Kidney Transplant
Kidney transplant location: UPMC Montefiore
Service email recipient: transplant@upmc.edu
Treatment type: Kidney Transplant
Kidney transplant location: UPMC Harrisburg
Service email recipient: transplanthbg@upmc.edu
Treatment type: Kidney Transplant
Kidney transplant location: UPMC Hamot
Service email recipient: hamottransplant@upmc.edu
Flying Cork (2025 api verification process): https://3.basecamp.com/4154990/buckets/10887235/todos/8727330374
N/A
#1: “Verification” Pixel
This pixel fires the confirmation email upon initial form submission, allowing the user to “verify” that they filled out the form. Please share this pixel with the client for implementation.
<img src=”https://pages.upmc.com/transplant-contact-us-api-verification” height=”1″ width=”1″>
#2: “Confirmed” Pixel
This pixel executes when the user selects the “Confirm” button in the confirmation email (meaning the user has “confirmed” their information), firing the TY Email, the Service Email, and writing to all additional DEs (journeys, newsletters, domo, causway, etc). Users will be redirected to the Sitecore-built, UPMC Thank You Page.This pixel does not get shared with the client.
<img src=”https://pages.upmc.com/transplant-contact-us-api-confirmed” height=”1″ width=”1″>
OUTSTANDING DELIVERABLE: In order to complete this pixel, we will need the UPMC TYP URL from the client.
#3: “Did Not Submit” Pixel
This pixel executes when the user selects the “Did Not Submit” button in the confirmation email. The user will be redirected to a Flying Cork-built landing page where they are given the option to update their email preferences. This pixel does not get shared with the client.
<img src=”https://pages.upmc.com/transplant-contact-us-api-did-not-submit” height=”1″ width=”1″>
Thank You Email: Content Builder\Transplant Contact Form\Transplant Services – Transplant Contact Form – Thank You
Service Email: Content Builder\Transplant Contact Form\Transplant Services – Transplant Contact Form – Service
Email Creation Basecamp Task: n/a
Thank You Email: Triggered Sends > Contact Us > Transplant Services – Transplant Contact Form – Thank You (external key: 2910)
Service Email: Triggered Sends > Contact Us > Transplant Services – Transplant Contact Form – Service (external key: 2909)
A simple cloudpage form to test the API configuration internally. Click here for an internal testing form code template.
Here is the (api verification process june 2025) internal testing form:
https://pages.upmc.com/transplant-contact-us-api-verification-internal-testing-form
I submitted a few tests and everything is looking good on my end.
Development version of the UPMC form used for testing.
Staging Form: Request an Appointment | UPMC Transplant Services | Pittsburgh, PA
Staging Confirmation w/ new pixel: Form Submit Confirmation | UPMC
Staging Final step: Thank You | UPMC
Production version of the UPMC form.
A (google sheet) checklist utilized by the flying cork team to keep track of API tasks and deliverables.
n/a