Your CRM knows which leads were real. Now your ad spend does too.

Ad platforms optimise for the events you send them. Send them lead submissions and they get very good at finding people who submit forms. But a form fill is not a customer, and the distance between the two is where lead-generation budgets quietly die.

The record of which leads were real already exists. Your CRM knows which leads a salesperson qualified, which deals progressed, and what they were finally worth. It just has never been connected to the machine deciding where tomorrow’s ad money goes. Tapper Vantage now closes that loop, and Salesforce is the supported connector today.

What actually happens when you connect

The integration is read-only and deliberately narrow. It reads a named core set across five CRM objects, covering funnel stage and its history, deal value and currency, campaign linkage and the ad click id, plus a short set of qualification fields agreed with you at onboarding and fixed in configuration. One backfill of the last 12 months, then a poll every 15 minutes reading only changed records.

Email and phone are hashed at ingest so a deal can be matched to the click that produced it, and the raw values are never stored. No free-text fields, no billing or payment objects, no writes of any kind to your CRM. Every line of that scope is written down in a signed disclosure a security reviewer can read before anything is connected.

Deal value goes to Google Ads, and it gets corrected

When a deal closes, its recorded value is uploaded to Google Ads against the click that produced it, de-duplicated per person, so bidding can favour the clicks that produced revenue rather than the clicks that produced forms.

The part most pipelines skip: deals fall through. A reservation gets cancelled, financing gets declined, a lead resolves to a status your team maps as disqualified. When that happens after a value was uploaded, Tapper sends a conversion adjustment that reduces or retracts it. The numbers your campaigns optimise against follow your sales reality in both directions, not just the flattering one.

What it teaches Vantage

Vantage predicts customer value from first-party behaviour. CRM outcomes give those predictions business context: the model learns against what your sales team actually concluded, not against proxies. Two numbers stay strictly separate here. The recorded deal value is what this integration uploads. Predicted lifetime value is what Vantage learns to estimate, and where predicted value is activated for an account, that is an explicit configuration choice, never a side effect of connecting a CRM.

Built to pass a security review

Salesforce data is held per customer and never pooled, so one customer’s outcomes never inform another customer’s models. Credentials are encrypted at rest and deleted on disconnect. Read-only is enforced by the permission set your admin assigns, on top of an integration that never issues a write. The full data boundary, object by object, is published in our Security, Data & Privacy Report.

See it

The integration, the data boundary and the FAQ security teams ask are all on the CRM integration page. We walk through the field set, the status mapping and the security review with your team before anything is connected.