--- title: "Personalizing scheduling on landing pages with Salesforce IDs" description: "You can use Salesforce Record IDs to personalize the booking process on your landing pages. Recognizing the Customer by their record ID provides two key bene..." url: "https://help.staticso2.com/scheduleonce/account-integrations/crm/salesforce/personalizing-scheduling-on-landing-pages-with-salesforce-ids" --- You can use Salesforce Record IDs to personalize the booking process on your landing pages. Recognizing the Customer by their record ID provides two key benefits: * On the User side, it allows you to update the correct record, eliminating any chances of updating the wrong record. * On the Customer side, it allows you to [prepopulate the Booking form step with Salesforce record data or completely skip the Booking form step](https://help.staticso2.com/scheduleonce/account-integrations/crm/salesforce/prepopulate-or-skip-booking-form-step-in-salesforce-integration "How to prepopulate or skip the Booking form step in Salesforce integration"). This eliminates the need to ask Customers for information you already have, improving conversion rates and moving leads through the funnel more efficiently. In this article, you’ll learn how to pass the Salesforce Record ID to your landing pages. Then, you’ll learn how to generate the personalized website [embed](https://help.staticso2.com/scheduleonce/sharing-publishing/publishing-on-websites/website-embed "Website embed") or [button](https://help.staticso2.com/scheduleonce/sharing-publishing/publishing-on-websites/website-button "Website button") code for your landing pages. Note If the Customer is not recognized based on the Salesforce Record ID, OnceHub will use the Customer’s email address to check if the record already exists in your CRM. [Learn more about integrating with Salesforce](https://help.staticso2.com/scheduleonce/account-integrations/crm/salesforce/salesforce-integration "The ScheduleOnce connector for Salesforce") ## Requirements [Section titled “Requirements”](#requirements) To use Salesforce Record IDs with your landing pages, you must: * Be a [OnceHub Administrator](https://help.staticso2.com/account-administration/user-management/user-roles-overview "Differences between Administrator and Member"). * Have a[ completed Salesforce connector setup in OnceHub](https://help.staticso2.com/scheduleonce/account-integrations/crm/salesforce/connecting-salesforce-api-user "How to connect a Salesforce API User"). * Have a [OnceHub User connected to Salesforce](https://help.staticso2.com/scheduleonce/account-integrations/crm/salesforce/connecting-to-salesforce "Connecting to Salesforce")**.** Note For security and privacy reasons, using CRM record IDs to skip or pre-populate the Booking form is not compatible with [collecting data from an embedded Booking page](https://developers.oncehub.com/docs/client-side-api/collecting-data-from-embedded-booking-page/) or [redirecting booking confirmation data](https://developers.oncehub.com/docs/client-side-api/redirecting-booking-confirmation-data/). ## OnceHub parameters for Salesforce [Section titled “OnceHub parameters for Salesforce”](#oncehub-parameters-for-salesforce) To recognize the Customer by the Salesforce Record ID, you need to pass the OnceHub parameters for Salesforce to your landing page: * Lead Record ID: *sosfleadid* * Contact Record ID: *sosfcontactid* * Case Record ID: *sosfCaseId* You can also add an additional variable to your landing page to skip the Booking form step: * Hiding the Booking form: *soSkip=1* Caution When [working with Salesforce Person Accounts](https://help.staticso2.com/scheduleonce/account-integrations/crm/salesforce/working-with-salesforce-person-accounts "Working with Salesforce Person accounts"), you will need to pass the related Contact Record ID and ensure that the Person Account includes a Contact ID lookup field. ### Step 1: Constructing the landing page’s URL parameters [Section titled “Step 1: Constructing the landing page’s URL parameters”](#step-1-constructing-the-landing-pages-url-parameters) There are different operators used in the syntax of your URL: * **?** - You must add the question mark to separate your URL from the variables. * **&** - You can pass multiple variables by separating the variables with the ampersand * **=** - The equal sign separates the variable from the value assigned to that variable. Take the following example landing page link: ```plaintext http://www.example.com ``` If you wanted to pass a Salesforce Lead Record ID with a value which is E9888900, you can add the following to the webpage link: ```plaintext http://www.example.com?sosfleadid=E9888900 ``` If you wanted to pass the variable to skip the Booking form step as well, you could add the skip variable to the link: ```plaintext http://www.example.com?sosfcontactid=E9888900&soSkip=1 ``` ### Step 2: Generate the personalized code for your landing pages [Section titled “Step 2: Generate the personalized code for your landing pages”](#step-2-generate-the-personalized-code-for-your-landing-pages) Now that you have passed the Salesforce Record Id to your landing page, you need to ensure that you have placed the personalized website [embed](https://help.staticso2.com/scheduleonce/sharing-publishing/publishing-on-websites/website-embed "Website embed") or [button](https://help.staticso2.com/scheduleonce/sharing-publishing/publishing-on-websites/website-button "Website button") code on your landing page. 1. In OnceHub, go to **Share & Publish**. 2. Select the **Website embed** tab or **Website button** tab. 3. Select **Customer data is passed using the Salesforce record ID (web form integration)** from the **Customer data** step. 4. Copy and paste the relevant code in your landing page. Caution If the Website [embed](https://help.staticso2.com/scheduleonce/sharing-publishing/publishing-on-websites/website-embed "Website embed") or [button](https://help.staticso2.com/scheduleonce/sharing-publishing/publishing-on-websites/website-button "Website button") code placed on your webpage was added prior to November 7, 2015, you will need to replace it with the updated OnceHub code.