Product
BookingsNewClasses, appointments and packs on one calendarSales and moneyNewCheckout, invoices and what came in todayClientsNewEvery client's history, forms and visitsEmail marketingNewNewsletters and automations that bring clients backAI AgentAnswers and books on WhatsApp, Instagram, Messenger, web chat and emailLeadsNewEvery enquiry on one board, with the next step and when it's dueTasksNewYour team's to-dos, made for you when leads and bookings changeSocialNewPlan and publish your postsReportsNewSales, bookings and clients at a glanceAI AutomationsWorkflows that run themselves, without losing qualityAI-Powered CreativeSenior creative, faster, with AI in the loop
Performance
Google AdsSearch, PMax and YouTube, priced by the workMeta AdsFacebook and Instagram with creative that keeps winningDigital AdsMeta, Google and TikTok campaigns that convertSocial Media CreativeReels, carousels and content for every platformKOL ManagementInfluencer strategy and execution, end to endSEOOrganic growth that compounds month over month
Creative and brand
Video and Media ProductionBrand films, reels and content at speedBranding and StrategyPositioning, messaging, identity and guidelinesEmail CreationEmails people open, read and buy fromWeb DevelopmentWebsites and landing pages built to sellApp DevelopmentMVP to store-ready, fixed price and date
Try it now
doTask ChatbotTalk to the AI AgentAsk it anything about doTask — it answers from our own pages and hands over to a person when it should.Open the chat →Book a demo
Customers

Google Ads: send results back and keep customer lists

Tell Google Ads which ad clicks became bookings, sales and new clients, and keep a segment as a customer list.

Zack Lam
Authored by Zack LamFounder, doTask
A shop counter with a customer being served
Customers
Read it in the appThe same article opens from Help inside app.dotask.io, beside the screen it describes.

When someone clicks your Google ad, lands on your site and then books, buys or becomes a client, doTask tells your Google Ads account. Google then shows your ads to more people like the ones who became clients, and Google Ads shows which ads, keywords and campaigns brought in bookings and sales, not just clicks.

  1. Settings → Google Ads → Connect Google Ads, and sign in with the Google account you use for Google Ads. Tick both boxes Google shows: managing your Google Ads, and sending your results and customer lists.
  2. Pick the Google Ads account. doTask makes three conversion goals there: “doTask: booking made”, “doTask: sale” and “doTask: new client”.
  3. Choose what is sent: bookings (with the price), sales (Checkout and invoices paid in full, with the amount) and new clients (a lead whose stage turns Customer).
  4. In Google Ads, the goals show under Goals → Conversions within a few hours of the first result.
  • Only people who came from a Google ad click in the last 90 days are sent, with the click itself. No name, email or phone goes with a result.
  • doTask keeps the click from the chat widget on your site: the gclid Google adds to the link. Auto-tagging must be on in Google Ads (it is by default).
  • Results go every quarter hour. Recent results on the page show which were sent; one Google refuses is tried three times.
  • Customer lists: open a segment under Customers and press Sync to Google Ads. doTask makes a list in your account, adds everyone in the segment who agreed to marketing (emails and phone numbers hashed first), and on each sync takes off people who left the segment or stopped agreeing. People who reached you on WhatsApp, Instagram or Messenger go in by email only, as Meta requires.
  • Google lets a customer list be used to target ads only once an account has spent over US$50,000 on Google Ads; below that, a list can still be used to observe how those people respond and to leave them out of a campaign.
  • Disconnecting deletes doTask’s Google sign-in. The goals and lists stay in your Google Ads account. To remove doTask from your Google account as well, go to your Google account’s Security, then Third-party access.
See also:All documentationFAQ