דלג לתוכן הראשי

WebitNow AI

Digital marketing agency · Givat Shmuel, Israel

Who we are

WebitNow AI is a digital marketing agency based in Israel. We build and run lead generation for small and medium Israeli businesses — dentists, contractors, clinics, local service companies — across Google Ads, Facebook and organic search.

Our public website is written in Hebrew because every one of our clients and every visitor to it is an Israeli business owner. This page is in English for reviewers.

Company
WebitNow AI
Website
https://webitnow.ai
Address
HaArava 1, Givat Shmuel, Israel
Email
webitnow1@gmail.com
Phone
+972-53-322-3356

What we do for our clients

We are a marketing agency. Our clients are small and medium Israeli businesses who hire us to run their advertising and handle the leads it produces. For each client we:

  • Manage their Google Ads account. Campaign strategy, budgets, creative and optimisation. Their account is linked to our manager account 234-649-2388 with their authorisation — the standard agency arrangement.
  • Run the landing pages the ads point at.
  • Answer and qualify the leads. A visitor who fills in a form or messages our WhatsApp number is answered within seconds, qualified, and passed to the business owner with a transcript.
  • Record which leads became paying customers, in the CRM we operate for them. That fact is what the API is needed for.

The platform is built and hosted by us, and operated by our own team on behalf of the clients who engage us. It is not a self-serve product. No third party signs up for it, connects their own Google Ads account to it, or uses it to manage an account we do not manage ourselves.

Which Google Ads accounts this covers

Manager account (MCC)
234-649-2388 — WebitNow AI
Our own advertiser account
577-994-0344
Google account
webitnow1@gmail.com

The API would be used against accounts linked to our manager account — today our own, and as we take on clients, theirs. A client account is linked only after that client engages us and accepts the manager link from inside their own Google Ads account, and it is unlinked when the engagement ends.

We never access an account that is not linked to the manager account above, and we do not ask clients for their Google credentials.

How we intend to use the Google Ads API

One use case: uploading offline conversions.

Today our campaigns optimise on form submissions, because that is the last event Google can see. But a form submission is not a customer. Roughly speaking, only some of the people who fill in a form ever become paying clients, and Smart Bidding has no way of telling those two groups apart — so it buys more of whatever produces form fills, which is not the same as what produces revenue.

We already store the click identifier (gclid) with every lead, and we already know weeks later which of those leads became customers, because that is recorded in our own CRM. The API lets us send that outcome back:

  • ConversionUploadService — upload click conversions for leads that became customers, against an import from clicks conversion action, keyed on the stored gclid.
  • ConversionActionService / GoogleAdsService (read) — read the conversion action's resource name and verify our uploads were accepted.

That is the whole of it today. We are not requesting the API in order to create campaigns, change budgets or generate keywords — campaign management stays in the Google Ads UI, done by our team.

What we expect to add later, stated now rather than found by you later: read-only reporting for the client dashboard we already operate, so a client can see spend, clicks and cost per lead beside the leads themselves (GoogleAdsService.SearchStream). That is a read, on accounts already linked to our manager account, and it changes nothing about who the tool serves.

Access level requested

Basic access, against manager account 234-649-2388.

The tool has no external users. It is operated by our own team, on behalf of the advertisers who have engaged us and linked their accounts to that manager account. It is not distributed, resold, or made available for anyone to connect their own account to.

Expected volume sits well inside Basic access limits: in the order of tens of conversion uploads per month per account, from a single scheduled job.

Compliance

  • Conversion data is derived from leads who contacted us or our clients directly through our own forms and phone numbers.
  • Our privacy policy and terms of service are published at /privacy and /terms (Hebrew).
  • We do not resell API access, and we do not expose the API to end users in any form.
  • Where we upload conversions for a client account, the underlying lead was generated by campaigns we run for that client, through forms and phone numbers we operate on their behalf under our engagement with them.

Contact