Ontraport Integration

How LeadSync Creates Ontraport Contacts

Ontraport is built around Contacts, Tags, Sequences, and Rules -- Contacts hold the person's data, Tags drive segmentation and Rule triggers, Sequences are the drip-campaign engine that schedules messages over time, and Rules are the automation system that fires actions in response to events. LeadSync connects via your Ontraport App ID and API Key (paired as request headers Api-Appid and Api-Key) and posts each Facebook, Google, LinkedIn, or TikTok lead to POST /1/objects with objectID=0 -- the Contact object.

Setup is two values from your Ontraport account (Administration › Integrations › Ontraport API Instructions). LeadSync stores them as a semicolon-delimited pair, then enumerates your drip Sequences via objectID=5 and your Tags via objectID=14 so you can pick which Sequence the lead enrolls in and which Tags get applied.

Sequence Enrollment and Tag Assignment in One Call

When LeadSync creates the Contact, it includes the updateSequence field with your selected Sequence IDs (formatted in Ontraport's */*id1*/*id2*/* delimiter) and the contact_cat field with your selected Tag IDs in the same format. This means a single API call creates the Contact, enrolls them in the drip Sequence, and applies the Tags -- no chained calls, no race conditions where the Sequence step runs before the Tag is applied.

Because Tag application fires Rule triggers, this also means any "When tag is applied" Rule you have configured runs automatically on lead arrival. Use this for SMS dispatch, internal task assignment, custom field updates, or webhook-out to your CRM -- the Rule engine treats the LeadSync-created Contact identically to a Contact added via your own Ontraport SmartForm.

SMS Number Capture for Multi-Channel Follow-up

Ontraport has a dedicated sms_number field on the Contact object that's separate from the regular phone field -- it's the field Ontraport SMS sends actually use. LeadSync writes the lead's phone (or phone_number) directly into sms_number at create time, so any SMS step in your enrolled Sequence (or any "send SMS" Rule action) can dispatch immediately without waiting for a manual cleanup pass.

For multi-step nurture flows that combine email and SMS -- "email day 0, SMS day 2 if no email click, email day 5 with discount" -- this matters because Ontraport will silently skip SMS steps when sms_number is empty. Populating it on creation means the first lead through your funnel doesn't accidentally miss the SMS leg of your sequence.

Frequently Asked Questions

In Ontraport, go to Administration > Integrations > Ontraport API Instructions and copy your App ID and API Key. Paste both into LeadSync when adding Ontraport as a destination. The pair is sent as Api-Appid and Api-Key headers on every API call -- there is no OAuth flow.

Yes. The connection settings let you pick which Sequence(s) the lead enrolls in, and LeadSync includes that as updateSequence on the create call. The Sequence starts immediately after the Contact is created -- no manual enrollment step, no chained API calls.

Yes. The connection settings list every Tag in your Ontraport account (LeadSync paginates through up to 50 per page so even large Tag libraries are covered). Pick all the Tags that should fire on lead arrival and they are applied in the same API call that creates the Contact.

Yes. Tag application fires "When tag is applied" Rule triggers exactly the same way as if the Tag were applied via the Ontraport UI. Use Rules for SMS dispatch, internal task creation, custom field updates, or webhook-out to your CRM -- the lead is treated identically to a Contact added via your own Ontraport SmartForm.

Yes. The phone (or phone_number) field from the lead form is written directly into Ontraport's sms_number field at create time. This is the field Ontraport SMS sends actually use, so any SMS step in your enrolled Sequence dispatches without a manual cleanup pass.

Ontraport de-duplicates Contacts by email when a duplicate-handling rule is configured (Administration > Settings > Duplicate Settings). With the default merge-on-email rule, a repeat submission updates the existing Contact and applies the Tags or Sequences additively rather than creating a duplicate.

Yes. Create one LeadSync connection per source and pick a different Sequence on each. Facebook leads enroll in your paid-social welcome Sequence while LinkedIn leads enroll in a B2B-specific drip -- each with its own Tag set, its own Rules, and its own messaging cadence.

Yes. LeadSync supports Ontraport as a destination for lead forms from Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own connection so you can route channels independently.

LeadSync sends the full name into Ontraport's firstname field and leaves lastname empty. If you specifically need a clean first/last split for personalisation, the cleanest pattern is an Ontraport Rule that runs on Contact creation and parses firstname into firstname + lastname -- this keeps the LeadSync side simple and lets your Ontraport-side logic handle the data shaping.

Available Integrations

How It Works

How LeadSync Creates Ontraport Contacts

Sequence Enrollment and Tag Assignment in One Call

SMS Number Capture for Multi-Channel Follow-up

Frequently Asked Questions

Start Syncing Leads to Ontraport