Type to search. Use the up and down arrow keys to choose a result and Enter to open it. Press / anywhere on the page to jump here.

Documentation

Tracking

When your client opens a proposal link, Declario records how the proposal is read, so you can see what happened after you pressed Send.

What is recorded

While a client has a proposal open, the page sends small batches of events every few seconds, and once more when the page is hidden or closed. For each visit Declario records:

  • Opens: each time the proposal is loaded.
  • Time per block type: how many seconds each kind of block, such as Pricing, was on screen. A block counts once it has been visible for at least a second.
  • Scroll depth: the furthest point reached, as a percentage of the page.
  • Device type: desktop, tablet or mobile, worked out from the browser's user agent.
  • A visit id: a random id created when the page loads and kept only in the page's memory. Every page load is a new visit.

Your own visits are not recorded when you open a proposal while signed in to its workspace.

The first open

The first time a client opens a sent proposal, Declario:

  • changes its status to Viewed;
  • sends an in-app notification and an email to the person who created the proposal;
  • posts a message to Slack, if a Slack webhook is set up;
  • sends the proposal.viewed event to your webhooks and to HubSpot.

What is not recorded

  • No cookies, local storage or session storage are set for the people who read your proposals.
  • The IP address is not stored with view events. Declario keeps only a keyed hash of it (HMAC-SHA-256 with a server-side secret), used to limit abusive traffic.
  • The full user agent is not stored, only the device type.
  • Location is not recorded.
  • YouTube videos are embedded from youtube-nocookie.com.

The one place where an IP address is stored as it is: the audit record created when a client signs. See Signatures.

Engagement score

Each proposal has an engagement score between 0 and 100 that helps you decide which proposals to follow up first. The database recalculates it every time a new event arrives:

Formula
score = min(100,
    opens × 10
  + visits × 15
  + pricing_seconds × 0.5
  + max_scroll_percent × 0.3)
Score inputs
InputWhat it countsPoints
OpensEach time the proposal is loaded10 per open
VisitsSeparate visits, the first one included15 per visit
Time on pricingSeconds spent on Pricing and Pricing Table blocks0.5 per second
Scroll depthThe furthest point reached, in percent0.3 per percent

The total is capped at 100.

Bands

  • Hot: above 70
  • Warm: above 40, up to 70
  • Cool: 40 or below

Example

A single visit in which the client spends 40 seconds on pricing and scrolls 80% of the way down adds:

  • Scroll depth: 24
  • Time on pricing: 20
  • Visits: 15
  • Opens: 10

Score: 69, Warm.

What the score is for

The score sorts proposals by how much attention they have had. It is not a prediction that a client will buy, and a low score does not mean a lost deal: a client who reads the proposal once, carefully, scores lower than one who opens it many times.

Use it to decide whom to call first, together with what you know about the client.