Personalized links using CRM record IDs

Personalized links using CRM record IDs can be either static or dynamic, but most often are used as dynamic links. Different from Personalized links (URL parameters), these links include a CRM record ID instead of actual Customer information. The record ID is used to retrieve Customer information from your CRM via an API. The Booking form is skipped by default as the Customer information is available during the booking process, but pre-population of the form can be used if you want your Customers to provide additional information on the form. Learn more about prepopulated Booking forms

It's important to note that in order for skipping and pre-population to work properly, you need to make sure that your CRM fields are mapped correctly to your ScheduleOnce fields (learn how to set up skipping and pre-population in Salesforce | learn how to set up skipping and pre-population in Infusionsoft).

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 or redirecting booking confirmation data.

Let’s look at an example. Let’s assume we use Salesforce as our CRM and email marketing app and want to send an email broadcast to all of our leads, inviting them to book a discovery call with us. We would create this type of link and place it in our email template. The link might look like this:{!Lead.Id}&sosfContactId={!Contact.Id}&sosfCaseId={!Case.Id}. In this example, the ‘sosfLeadId’ and ‘sosfContactId’ refer to the lead and contact identifiers in Salesforce, respectively. The ‘{!Lead.Id}’ and ‘{!Contact.Id}’ are replaced with actual lead and contact identifiers, respectively, during an email broadcast, thus, creating a personalized email for each lead in our list.

This feature is available when using a Salesforce or Infusionsoft CRM integration. You can find more information on setting up these links by visiting the articles below.

Salesforce articles:

Infusionsoft articles:

Was this article helpful?
Thank you for your feedback!