Which tools does Roccai integrate with?

Roccai is not another place to log in and check for leads. An enriched lead lands in the CRM your sales team already opens and the email tool your campaigns already run from — with the preference data attached, so your existing segments and automations have something real to work with.

Roccai does not hand your CRM another email address. It hands over the answers behind it — including what the person said no to.

Every connector sends three layers of data. First, the contact fields someone typed into the guide — email, name, phone, whatever your input card asks for — each one mapped to a field you pick in the destination tool. Second, the decisions: every question the guide asked, the option they chose, and the options they rejected. Third, an optional AI summary — a plain-language paragraph describing what the person was looking for and what they leaned toward.

The rejected options are the half most tools throw away, and usually the more useful half in a sales call. A lead who said no to city breaks and yes to coastal trips is a different conversation from one who only gave you an email address.

Field mapping, per tool

Each connector has its own mapping table: you pair a Roccai source field with the destination's own field — a HubSpot property, a Mailchimp merge field, a Klaviyo or ActiveCampaign field, an Ortto target, or any key you like in a webhook payload. Nothing arrives as an unlabelled blob, and you do not have to accept Roccai's field names.

Routing by campaign

Every connector is scoped to campaigns. One guide running across a newsletter, a paid social ad and an in-store screen can send each campaign's leads to a different destination — or send the fair leads to your CRM and the newsletter leads to Mailchimp — without building a second guide.

When it arrives

On submission, not on a nightly sync. An enriched lead reaches your CRM or email tool in real time, so a welcome flow or a sales task can fire while the person is still on the page.

Power BI, Make, Google Analytics and CSV are supported — but through the API, the webhook and the data layer rather than as one-click connectors.

Power BI reads from the Roccai API, so guide engagement and preference data can sit in the same dashboard as the rest of your reporting. Make connects through the custom webhook or Zapier, the same way any other automation platform does. Google Analytics is different again: guide events are pushed to your data layer as GA4 events, so you track starts, completions and lead submissions alongside the rest of your site. And CSV export covers the cases where you just want the rows — including straight into WordPress.

Product data comes in the other direction: point Roccai at a JSON or XML feed URL, or upload a CSV. Shopify and WooCommerce both generate a feed Roccai can read, so the guide recommends your real catalogue rather than generic results.