What Eva does with Meta Ads and Google Ads

Only an owner or admin of your Eva account can connect. They sign in on Meta's or Google's official screen, with their own user, and approve the permissions Eva asks for.

On Meta, Eva asks to read and manage your ads. On Google it asks for two: Google Ads, to read your campaigns and apply the changes you approve, and Data Manager, to send your sales.

Then you choose which ad accounts Eva uses. You can disconnect at any time from Integrations, and Eva stops reading and sending. On Google you can also remove access from your Google Account settings.

Every day Eva reads the spend, campaigns and ads of the accounts you chose. It puts them next to the conversations, qualified prospects and sales Eva records in its CRM.

You see it by campaign and by region, with cost per sale. With fewer than five sales, Eva marks that cost as too small a sample.

A sale is the CRM stage you mark as a sale, a quote or a qualified prospect. The figures each platform reports sit on a separate line and are never added to Eva's. Each currency gets its own block.

When a deal reaches a sale, quote or qualified-prospect stage, Eva tells the platform the ad came from. That way Meta and Google optimize on real sales, not just clicks.

Meta receives sales from conversations that started on an ad that opens WhatsApp, through the Conversions API for business messaging. Each event carries the click identifier, your WhatsApp Business account identifier and the amount when there is one. It carries no phone number, email or messages.

Google receives them through the Data Manager API. Eva uses the Google click identifier captured by your site's chat, or a SHA-256 hash of the verified email or phone. It never sends the readable value or the messages.

When you choose a Google Ads account, Eva creates there the conversion actions it needs for sale, quote and qualified prospect. Before sending, it checks that Customer data use is on in Google Ads.

Each platform has its own switch in Ads › Settings. If you turn it back on, Eva does not send earlier sales. Sending sales uses no credits.

Every week Eva reviews your campaigns and proposes specific changes: raise or lower a daily budget, pause an ad, or change a line of ad text.

Eva only proposes on what has at least five sales measured in the last 28 days, and each suggestion says how many it is based on.

An owner or admin sees the exact change, before and after, and applies it in one click or dismisses it. When a change cannot be applied from Eva, such as ad text on Meta, Eva shows the steps to make it in Meta.

The weekly review uses credits. What credits cost is on the pricing page.

By default, Eva only suggests. If the business turns on Automatic, Eva applies daily budget changes on its own, within a weekly range and the monthly cap the business sets for each account.

If the month's spend is on track to pass that cap, Eva reverts its own increases or pauses campaigns until it fits again. For the first 24 hours it only watches.

Automatic never changes ad text and never creates or deletes campaigns. Going back to Suggestions takes one click.

The Changes tab lists what was applied from Eva, what Automatic did and what someone changed directly in Meta or Google.

A change made from Eva can be reverted in one click. First, Eva checks that nobody moved it on the platform since.

On Meta you can also pause an active campaign, ad set or ad from Eva, and resume it from Changes.

Eva reads from your accounts what it needs to show reports and prepare suggestions: accounts, campaigns, ads and their text, budgets, daily metrics and change history. For weekly suggestions, it sends part of that to OpenAI's model service.

EvaAI does not use information received from Google APIs to train AI models.

The details are in the privacy policy, section "Measurement of our business customers' ads".