CRM
Zoho runs in five separate data centres and Attribi connects to whichever one holds your org, so an EU or India tenant is never routed through a US host to make attribution work. Once connected, Attribi reads your Deals on a schedule and turns the ones that reach a qualified stage or Closed Won into offline conversions on every ad platform you have connected, with the deal amount attached. Campaign history travels the other way, onto the Contact record your salespeople already open.
No credit card required · 5-minute setup
A Deal that reaches Closed Won becomes a closed-won conversion carrying its amount and currency. Attribi looks for Zoho’s own default won stage by name, so this works out of the box on a standard pipeline and does not work if your team renamed that stage.
Type the Deal stage names that mean qualified for your team, exactly as they appear in Zoho, and every Deal that reaches one fires a qualified conversion. Leave the list empty and qualified detection is simply off while closed-won reporting continues.
One button creates 16 custom fields on your Contacts module. As leads convert, Attribi fills the visitor id, the first touch source, campaign and time, the last touch source and campaign, and the touch count, so a rep opening the record can see where the person came from.
A Zoho form can drop the ad click ID into the MTA Click ID and MTA Click ID Type fields with two hidden inputs. Attribi reads that pair back off the Contact when the Deal moves, so uploads can be matched on the click even though no script ever ran on your site.
Global, Europe, India, Australia, and Japan are each a different Zoho host, and picking yours at connect time points both the sign-in and the API calls at it. Nothing has to be migrated and no request crosses into a region your org does not live in.
Planned, not live today. Listed so you can see what this integration does not do yet, before you sign up.
Detecting a won stage your team renamed, the way Attribi already does for Salesforce and HubSpot by reading the flag the CRM itself keeps. Until it lands, a renamed won stage means Attribi sees no revenue at all from Zoho and does not warn you.
Not yet available.
Pick your data centre from the Connections page and authorize Zoho there. Also choose whether Attribi may create contacts that Zoho does not already hold, or should only enrich records you already own and never create one.
One button creates the 16 custom fields on the Contacts module. Standard edition or above is required for programmatic field creation. On Free and Trial orgs Zoho refuses, and Attribi stops and lists every field name so you can add them by hand rather than half-finishing.
Paste the Deal stage names that mean qualified, comma separated, exactly as Zoho spells them. Closed Won needs no configuration provided your pipeline still uses that stage name. From then on the pull runs on a schedule and uploads on its own.
Stages Attribi supports for Zoho CRM.
CRM
Pipedrive attribution that reads won deals by status rather than stage name, uploads the deal value to your ad platforms, and writes campaign data on the person.
CRM
Salesforce offline conversion tracking: won Opportunities upload to your ad platforms as revenue, matched on email and phone, using your own stage names.
Ad platform
Google Ads offline conversion tracking: send qualified leads and closed-won revenue from your CRM, so your account sees CRM-verified outcomes, not just form fills.
Attribi will not see your revenue. Unlike the Salesforce and HubSpot connections, which read the won flag those systems keep on the record, the Zoho pull matches the stage literally named Closed Won. A pipeline that calls it Signed, or Booked, or Won, produces no closed-won conversions and no error message. If you have renamed it, either rename it back before connecting or tell us, because reading Zoho’s own won definition is on the roadmap rather than in the product today.
Seven of the sixteen it creates: the visitor id, first touch source, first touch campaign, first touch time, last touch source, last touch campaign, and the touchpoint count. The other nine, including the attribution path, the landing page, the referrer, and the two click ID fields, are created so the schema is complete but are not written by Attribi today. The two click ID fields are the deliberate case, because those are meant to be filled by your own Zoho form and read back by Attribi, which is how the pixel-less path works.
Standard, Professional, Enterprise, and Ultimate. Programmatic custom field creation is not available on Free and Trial orgs, where Zoho returns a permission error. Attribi surfaces that as a warning rather than blocking the connection, and it names all 16 fields so you can create them under Setup, Customization, Modules and Fields. Once they exist, everything else behaves identically.
Only if you choose that at connect time. Full mode matches by email and creates the contact when Zoho does not have one. Attribution only mode never creates a record: it searches by email, writes attribution onto the contact if one is found, and does nothing at all if it is not. Either way, the only fields Attribi writes are the ones it created.
Not for revenue. Qualified and closed-won outcomes are read out of Zoho and uploaded to your ad platforms whether or not any script is installed, and a Zoho form that captures the click ID keeps click-level matching alive too. What you give up without the script is the visit history: no page views, no multi-touch path, only what Zoho holds. One thing to know either way, a won Deal with a blank or zero Amount is recorded but uploads no revenue conversion, because there is no figure to send.
Updated
Sign up and connect it from the Connections page.
Start FreeNo credit card · Free forever up to 1,000 visitors