Archive > API > Transplant Contact Us API (Updated June 2025 – Verification Process Implementation)

Basecamp Tasks

Flowchart

Data Extensions

Holding Table
  • Transplant_Contact_HOLDING
  • Transplant_Contact_HOLDING_TEST
  • Transplant_Contact_CONFIRMATION 
  • Transplant_Contact_DID_NOT_SUBMIT
Triggered Send Data Extension(s)
> Interactions > 
  • Transplant_Contact_Us_TY_Email_TSD
  • Transplant_Contact_Us_Service_Email_TSD (UTMs added)
  • Transplant_Contact_Us_Confirmation_TSDE
Journey Entry Data Extension(s)

N/A

Newsletters/All Other Data Extension(s)
If the user selects the Confirm button in their Confirmation Email, the “Confirmed” Pixel will fire and the user will be added to the following newsletters (in additional to domo and causeway):
  • Transplant_Services_Master_DE
  • LDLT_Newsletter_Master_DE (ONLY IF treatment_type = ‘Liver Transplant’ OR ‘Kidney Transplant’)
Shared Items > Shared Data Extensions > _Reporting > DOMO Arigato > DOMO_025_CampaignLeads
Shared Items > Shared Data Extensions > Causeway > Causeway Export Holding SDE

Conversion Pixel CloudPages > _External Conversion Pixels > 

Conversion pixels (3):

#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″>
 

Triggered Emails

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

Triggered Send (TS) Definitions

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)

Internal Testing Form URL

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.

 

Here is what you should expect from testing:

  1. On form submit, the “Verification” Pixel will fire you should receive either the Self or Other Confirmation Email, depending on which option you selected from the appointment_for field. Be sure to only fill out the fields that go with your selection. On the UPMC form, these extra fields will show and hide dynamically. I skipped that step here to save time. Make sure all other fields are filled out as they apply to anybody filling out the form, regardless of Self or Other. Your records will be added to Transplant_Contact_CONFIRMATION and Transplant_Contact_Us_Confirmation_TSDE.
  2. Open the Confirmation Email(s) and check to make sure all of your information is correct.
    • If you select the Confirm button in the email, the “Confirmed” Pixel will fire and you should receive the TY email. The service email will be sent to one of my testing email addresses for now, depending on your treatment selection. See below for the current PROD and TEST service email address mapping in the “Confirmed” Pixel – pulled from the original api pixel.
      • Important: At this time, you will be redirected to a UPMC.com page that says “Our Apologies”. This is not an error. Once we receive the UPMC Thank You Page URL from the client, I will update the “Confirmed” Pixel with that URL and the user will be redirected to the TYP instead.
  3. If you select the Resubmit my information button, you will be redirected to the prod form. No pixels fire when this button is selected, just a simple redirect.
  4. If you select the I didn’t submit this form button, the “Did Not Submit” Pixel will fire and you will be redirected to an internally built landing page where you are given the option to update your email preferences. Your records will be added to Transplant_Contact_DID_NOT_SUBMIT.

UPMC Sitecore Form URL (Dev)

Development version of the UPMC form used for testing.

In order to test in dev, I added the UPMC DEV Thank You Page URL (provided by the client), to the redirect code in the “confirmed” pixel.

UPMC (DEV) TYP URL: https://ca.upmc.com/services/transplant/contact/thank-you-contact

“Confirmed” Pixel:
<img src=”https://pages.upmc.com/transplant-contact-us-api-confirmed” height=”1″ width=”1″>

UPMC Sitecore Form URL (Prod)

Production version of the UPMC form.

Internal API Checklist

A (google sheet) checklist utilized by the flying cork team to keep track of API tasks and deliverables.

Notes/Comments:

n/a

Your email address will not be published. Required fields are marked *