Skip to main content
ProposifyCRMs and lead management

Proposify conversion tracking: your ads see the inquiry, Proposify sees the win

Google Ads and Meta get credit for a contact form, then your rep builds the proposal in Proposify days later and the client signs on a Proposify link the ad platforms never see. We carry the original ad click onto the Proposify document and send won proposals back with their value, so bidding learns from contracts you closed instead of every form fill.

Free30 minutesNo obligation

Proposify · what breaks

What goes wrong when you sell through Proposify

  1. 01

    "Google Ads thinks every form fill is a win"

    The only conversion your ad accounts see is the website inquiry, so bidding keeps buying people who never get past a first call. Nothing tells it which inquiries became a Proposify proposal you won.

  2. 02

    "The proposal has no idea which ad started it"

    Your rep creates the Proposify document from a CRM deal, often a week after the click. The gclid or fbclid stayed on your website, so a won proposal can't be tied to a campaign.

  3. 03

    "Signed, won and paid mean different things on our team"

    Proposify fires separate signed and won events, and a rep can also mark a document won by hand from the pipeline. Count both, or the wrong one, and a single contract shows up twice in your ad reports or not at all.

  4. 04

    "A one-off logo job and a two-year guard contract look the same"

    Proposify keeps one-time, monthly and annual totals apart. Send only the one-time figure and a recurring guard or retainer contract reports at a fraction of its worth, so budget drifts toward your smallest jobs.

Proposify · the fix

What changes after we fix it — Proposify

  • Campaigns judged on proposals you won

    Google Ads and Meta receive the won proposal matched to the original click, so bidding chases clients who sign.

  • A value rule your team agreed to

    One-time fees and recurring totals combined the way you price contracts, applied to every won document.

  • One conversion per deal

    Each Proposify document reports once, with lost and test proposals kept out of every ad platform.

Proposify · architecture

What Proposify actually lets you hook into

All of this comes from Proposify's API reference and integration pages. Anything their docs don't cover, we test on your account.

  1. 1

    Connect API webhooks

    OAuth-based API with webhooks for document created, sent, viewed, signed, won, lost and commented.

  2. 2

    Document custom fields

    Custom fields can be set on a document through the API, by name. The click ID lives here.

  3. 3

    Totals on the document

    Documents carry a total, separate hourly, monthly and annual totals, and a won date.

  4. 4

    CRM integrations

    HubSpot lets reps create proposals from a deal and logs Proposify activity, including wins, on the timeline. Salesforce, Pipedrive and Zoho are listed too. Deal-amount sync is something we confirm.

  5. 5

    Zapier and Stripe

    Proposify lists Zapier for other apps and Stripe for payment inside the proposal at sign-off. Exact Zapier triggers get checked in your account.

  6. 6

    No ad pixel on the proposal

    We found no documented Google Analytics, Tag Manager or Meta Pixel setting for proposals, so wins go server-side.

Proposify · diagnose

Where Proposify tracking breaks, in the order we check

Most of the damage happens before the proposal exists, so we start at your form.

  1. 01

    Does the lead record keep the click ID?

    Fill in your own quote form from a URL carrying a test gclid, then check the lead HubSpot, Pipedrive or Salesforce creates.

  2. 02

    Does the click ID reach the Proposify document?

    Create a proposal from that deal and check its custom fields.

  3. 03

    Which status does your team treat as the sale?

    Look at which webhooks fire on recent documents, signed, won or both, and find any proposals a rep marked won by hand after a PDF or offline signature.

  4. 04

    Is the value the right total?

    Check recurring deals for monthly or annual amounts that never reached the reported value.

  5. 05

    Is anything else already reporting the deal?

    HubSpot offline conversions, an old Zap or a thank-you page tag can all claim the same client.

Proposify · prove

How we prove it on your Proposify account

Run on a real proposal from a real ad inquiry, sent to a test signee and marked won.

Source of truth

Proposify documents marked won, with won date, client and document totals, plus Stripe payments where you collect in the proposal

  • One inquiry submitted with a test gclid, and that click ID found on both the CRM deal and the Proposify document's custom field.
  • The won webhook received once, and exactly one conversion per document in Google Ads and Meta, matched one by one over a closed window.
  • Reported value checked against the agreed rule on one one-time deal and one recurring deal.
  • A lost proposal and a tutorial document confirmed absent from every platform.
  • Rechecked after 30 days, and again whenever your CRM connection or proposal templates change.

Proposify · free audit

What we check in the free audit

  • Does the lead record keep the click ID?
  • Does the click ID reach the Proposify document?
  • Which status does your team treat as the sale?
  • Is the value the right total?
  • Is anything else already reporting the deal?

Checked against

Proposify documents marked won, with won date, client and document totals, plus Stripe payments where you collect in the proposal

Get my free conversion tracking audit

Free30 minutesNo obligation

Proposify · when not to buy

When Proposify tracking isn't worth paying for

Plenty of Proposify accounts are fine without us.

  • If most proposals go to referrals and repeat clients and ads bring only a few deals a quarter, review those by hand.
  • If HubSpot or Salesforce already sends closed deals to Google Ads with the original click ID and the numbers match your won proposals, leave it.
  • If you don't run Google or Meta ads at all, Proposify's own pipeline reports tell you what you need.
  • If a stale Zap is double-reporting signatures and nothing else is wrong, turn that Zap off yourself; it takes five minutes.

Proposify · what we deliver

The event map on Proposify

  • Website inquiry captured

    Form submit with gclid, fbclid and UTMs saved to the CRM lead, so the click survives until a proposal exists.

  • Proposal sent

    Proposify's sent event, the qualified-lead signal for campaigns with too few wins to bid on.

  • Proposal signed

    Kept for reporting, and the fallback conversion if your team doesn't use won consistently.

  • Proposal won, with value

    The main conversion, sent from the won event with totals combined under your value rule.

  • Stripe payment inside the proposal

    Where you collect at sign-off, reconciled against Stripe so paid deals report apart from signed ones.

  • Excluded on purpose

    Views, comments, lost proposals and tutorial or internal test documents never reach Google Ads or Meta.

Written guarantee

95%+ tracking accuracy

Measured against Proposify documents marked won, with won date, client and document totals, plus Stripe payments where you collect in the proposal. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Proposify questions, answered

Proposify's public docs don't describe one, and the proposal opens on a Proposify link, not your site. So the win is sent server-side from Proposify's webhooks instead of the client's browser.

Free · 30 min

Find out which ads actually win you Proposify deals

Free30 minutesNo obligation