Overview

When ingesting data from your CRM, it will typically feed into two reports within Ruler:

Opportunity Report

Reports on milestone stages a lead reaches after the initial enquiry (e.g. qualified, meeting booked).

Revenue Report

Reports on new customer revenue once a sale is closed.

Ingestion Methods

There are four ways to bring CRM and revenue/opportunity data into Ruler. Review the options below and discuss with your onboarding manager which method is most suitable.

Direct API Connection

Ruler can integrate directly with many out of the box CRM systems including:

Salesforce
HubSpot
Pipedrive
Zoho CRM
Microsoft Dynamics

To allow us to integrate directly with your CRM we require authentication via an OAuth link to connect to your account. Ruler will then build your workflow based on your setup and reporting requirements.

📘
Note
If your CRM is not listed above, please speak to your onboarding manager who can advise on the best alternative ingestion method for your setup.

Ruler API (Direct POST)

Send data directly to Ruler's Revenue or Opportunity API endpoints using a PUT request.

Documentation:

Store Revenue
Store Opportunity

Outbound Webhook

Ruler can provide a dedicated webhook endpoint during onboarding.

Configure your CRM or data platform to send event data via POST requests to this endpoint with all required variables.

CSV Import

Upload a CSV file manually through the Ruler UI, or send files to a configured inbox for scheduled automated imports. If using scheduled CSV you should confirm your upload format with your onboarding manager before your first upload. More information on CSV upload methods here.

SFTP / FTP

Connect Ruler to an SFTP or FTP server to allow us to retrieve data files on a scheduled basis using a consistent file format.

Please confirm setup requirements with your onboarding manager.

Required Data Fields

The following variables are required regardless of which ingestion method is used.

Important

Email, Phone, RaId, Cookie Value, and Payload Value are identifier keys used for matching.

You must provide at least one of these identifiers to allow Ruler to attempt a match against an existing online visitor event.

Variable	Description	Required
`email`	The email address associated with the closed sale/deal	No
`phone`	The caller's phone number associated with the closed sale/deal	No
`RaId`	The Ruler Cookie ID associated with the closed sale/deal	No
`Cookie Value`	The GA-captured Cookie ID associated with the closed sale/deal	No
`Payload Value`	A unique identifier captured on form submissions associated with the closed sale/deal	No
`date`	Date the opportunity was closed/won or revenue was received. Format: `2019-03-15T13:14:00`	Yes
`value`	The total revenue value for the sale/deal	Yes
`label`	A custom reference value such as deal name, product type, or category	Yes
`currency_code`	Currency code for the sale value being uploaded. Supported currencies: GBP, EUR, USD, CAD, NZD, SGD, ZAR, AUD	Yes
`unique_record_id`	A unique reference for the sale or opportunity record, used for deduplication and updates	Yes

Matching & Attribution

When data is uploaded, Ruler attempts to match the provided identifier to a lead previously captured in the Forms or Calls report from your website or offline lead sources.

A successful match links the revenue or opportunity data to the visitor's complete online journey and associated marketing source.

A higher volume of unmatched records is expected during the first one to two months after implementation, particularly when the lead-to-sale cycle exceeds the amount of time Ruler has been active.

If you have any questions on what is the best method to use, please get in touch with a member of the team today.