By Ontraport

Ontraport

What it does

Ontraport combines a customer database, CRM and marketing automation. A team can capture a contact through a form, let an event enter that contact into a visual automation map, then send follow-up or update the record. The map shows the journey and its results, while email and SMS use needs permission and plan checks.

Last updated
Oct 18, 2026
Ontraport · Editorial illustration
Conceptual editorial illustration of a blank form leading a contact token into branched follow-up and record actions for Ontraport.

Work at Ontraport?

Help customers find accurate information about your software.

Manage this listing →

Find your fit

Who it is for

It suits a small or midsize organization that wants lead follow-up, sales pipeline context and customer messaging in one database. A buyer with several handoffs can map form entry, a follow-up email, a field change and a later goal before committing to a wider rollout.

A marketing team can use a prebuilt map as a starting point or build its own flow. The practical setup work is deciding which events start a journey, which contacts qualify, when a branch should pause, and which outcome should count as a goal.

Back to sections

The work it supports

Core capabilities

Keep contact context. Ontraport's CRM tracks customer activity on one record and supports pipeline work and shared team visibility. Contact creation, field changes and tags can start or change an automation path.

Design a journey. Automation maps resemble flowcharts. Teams can start from a blank map or adapt a prebuilt one, then choose triggers, actions, filters and goals to describe what happens next.

Choose an entry event. A submitted form, landing-page visit, email open or purchase can start a path. Contact-record updates can also trigger a path, with conditions to narrow a field-change event to a value.

Act and branch. An action can send email or update a contact record. Filters can pause a contact or direct the record down another path; a goal can move it after a desired event such as a purchase or sign-up.

Read the map. Ontraport says results appear on a launched map, and goals support performance review. Check whether the chosen goal represents the business outcome you actually want before interpreting the map's results.

Manage email preferences. Automated sends are treated as bulk email. The vendor requires permission for the requested topics, and Bulk Email Status controls which marketing or transactional messages a contact may receive. A subscription page can expose map-specific opt-out.

Use SMS with care. Contacts must opt in by form or by texting the Ontraport number. After a STOP-style opt-out, only an incoming START text restores bulk SMS status. Twilio filtering can block a message, and the vendor warns that filtered or blocked texts can still be charged.

Back to sections

Understand the offer

Pricing and getting started

The pricing page offers a 14-day trial for all plans without a card at sign-up and says an account will not be charged if it is not upgraded. The home-page trial defaults to Pro; starting from pricing lets a buyer choose a level and trial add-ons. Compare the intended paid level, rather than treating trial access as every plan's entitlement.

Paid subscriptions can be monthly or annual, with an annual commitment. Ontraport describes a separate Done-with-you Setup and Training Package and other account add-ons. The captured pricing page did not expose a stable plan grid, so confirm current plan rates, contact limits and feature entitlements with the vendor before purchase.

High-volume use may change the bill: extra bulk-email packages are recurring monthly purchases, and text sending requires an active SMS plan. Confirm both included volume and overage or message charges for the specific account before migrating a large list.

Back to sections

Look a little closer

Before you choose

Pilot a consented test contact from form submission through an email action, a filter, a goal and map reporting. Check that field changes, repeat visits and an unexpected purchase do not send a duplicate or irrelevant follow-up.

Before importing contacts, document which topics and channels each person consented to. Test bulk-email status, map-level unsubscribe and SMS opt-out handling; the vendor's rules do not treat a later form or API call as an SMS re-opt-in after STOP.

Estimate account level, contact count, extra email volume, SMS usage and any setup help separately. Use the 14-day trial at the intended level to test the actual workflow, then obtain a current quote for the paid configuration.

Back to sections

9 distinct sources behind this profile. Research observed Oct 18, 2026. Features and offers can change.
View sources and research →

Help keep this profile useful

Spotted an outdated detail? Send the correction with a supporting source. A verified account is needed to submit.

Suggest a correction ↗