Support

Making the case for Vantage to your team

On this page

Forward this page to anyone who has to say yes to Vantage.

In one line: Vantage sends Google Ads what each customer is worth to you, so bidding follows revenue instead of counting every conversion the same.

For your CFO

  • Measured on your money. The result is read from your own orders without tax and after refunds, or from your CRM outcomes. What Google reports sits beside it as context, never as the result.
  • Against a control. Vantage runs against your current setup at the same time, on the same budget share. You get the difference, its range and the probability Vantage is ahead, at 80% confidence unless you set your own level.
  • No work without a fit. Before anything is built, the Tapper Fit Check tells you in writing whether Vantage can help. If it cannot, Tapper says so.
  • Your current setup stays as it is. The test never edits the campaign it compares against.

For your marketing lead

  • Google bids on what each customer is worth, not on a count of conversions.
  • Campaigns, ads, budgets and your agency stay as they are.
  • Part of the work is cleaning what Google counts: each purchase once, tax and refunds out. Both halves of the test get those fixes, so the result shows what Vantage adds on top.
  • The readout splits brand and non-brand campaigns, because people who search your brand mostly buy anyway.

For your agency

  • You keep running the account.
  • Tapper adds one conversion action and one custom goal. The conversion action is secondary, so nothing changes until a campaign is attached to the goal.
  • Before values start: one primary purchase action. Before the test: test campaigns on value-based bidding, without a budget limit.
  • During the test: the same budget share in both halves, and no edits to either.

Your data

Salesforce and BigQuery connect read-only. Vantage sends Google a value and the ad click it belongs to. How Tapper protects your data: How Tapper secures your data.

Still need help?

Chat with our team and mention this article.