Integrations
Does Roccai integrate with Ortto?
Yes. Roccai pushes customer and lead data into Ortto as an activity, using your API key and an activity ID. Because it arrives as an activity rather than a quiet contact update, an enriched lead can trigger an Ortto journey immediately — so the follow-up starts while the person is still interested.
How the Ortto connection works
Roccai data lands in Ortto as an activity — the event type Ortto journeys are built to listen for.
Ortto needs two values: an API key and an activity ID (the identifier of the custom activity Roccai should write, in the form act:my_ortto_activity_id). Add both to the Ortto integration in Roccai, pick the campaigns that should feed it, and map each Roccai source field to the Ortto target it belongs in.
The activity model is what makes this different from a plain contact sync. An activity is a timestamped event against a person, so Ortto can use it as a journey entry condition. An enriched lead becomes something Ortto can react to, not just something stored on the profile.
Ortto integration at a glance
| How it works | |
|---|---|
| What you need | An Ortto API key and an activity ID |
| What Roccai creates | An Ortto activity recorded against the person, with their contact data |
| Where the answers land | Ortto targets you choose in the mapping table |
| Scoping | Per campaign — you pick which campaigns feed Ortto |
| Timing | On guide submission, in real time |
| Optional extras | The decisions layer (every answer, including rejected options) and an AI summary |
What you can do with it
Use an enriched lead as a journey entry condition, so someone who has just told you what they want enters a relevant journey rather than a generic welcome sequence.
Branch a journey on a stated preference. The answers arrive as mapped fields, so a condition can read what the person actually chose instead of inferring it from opens and clicks.
Build audiences from declared intent rather than behavioural guesswork — useful for a first-time visitor who has no history in Ortto at all.
Keep channel attribution intact: the campaign the guide was shared under arrives with the activity.
Frequently asked questions
How do I connect Roccai to Ortto?
Paste your Ortto API key and the activity ID you want Roccai to write into the Ortto integration in Roccai, choose which campaigns feed it, and map your Roccai fields to Ortto targets. Setup takes minutes and needs no developer.
What is the activity ID for?
It tells Roccai which Ortto custom activity to write, in the form act:my_ortto_activity_id. Because the data lands as an activity rather than a plain profile update, Ortto can use it as a trigger — which is what makes journeys possible.
Can a Roccai guide trigger an Ortto journey?
Yes. The enriched lead arrives as an Ortto activity in real time, so you can set it as a journey entry condition. Someone finishing a guide can be in a tailored journey within moments of telling you what they want.
Which Roccai fields can I map to Ortto?
Any of them. The integration has a mapping table pairing each Roccai source field with an Ortto target, so contact details and guide answers both land where you want them rather than in an unlabelled blob.
Can I use Ortto and another integration at the same time?
Yes. Connectors are independent and each is scoped to its own set of campaigns, so you can send everything to Ortto and simultaneously push a subset to a CRM, an email tool or your own webhook.
Other Roccai integrations
Roccai also connects natively to HubSpot, Mailchimp, Klaviyo, ActiveCampaign and Zapier & custom webhook. For the full list, the data that flows and the payload reference, see all Roccai integrations.
See it triggering an Ortto journey