Meta and Google ads setup and tracking, done before you spend

When ads disappoint, the cause often sits upstream of the creative: an ad account in someone else’s name, a lead event that fires twice, a form that never reaches sales. Here is the setup we complete before launch.

You own every account; we get access

An ad account builds value you cannot buy back: conversion history, audiences, billing records. So every asset is created in your business’s name, and we work through access you can withdraw.

On Meta, assets live in a business portfolio (formerly Business Manager). Each asset belongs to one portfolio, and an ad account created inside one stays there permanently, so yours is created in your portfolio, never ours. Our portfolio gets partner access, full or partial, to the assets you choose.

On Google, the Ads account sits under a Google account your business controls. Our manager account sends a link request, and your admin accepts it.

The access checklist: what we need from you

Setup moves fastest when access is ready, so this is the list we share on day one. None of it means sharing a password: wherever we need access, you add us as a separate user or partner that you can remove.

Decide before you create accounts

Settle these before any account exists: the settings that lock, then billing and GST.

Settings you can’t change later

Some choices are locked once an account exists. Fixing them later means a new account, which starts without the old one’s history.

US Pacific time runs 12.5 to 13.5 hours behind India, so an account left on Meta’s default starts each day around lunchtime here.

Billing and GST in India

Your ad budget is paid straight to Meta and Google in rupees, and Meta bills through Facebook India. The tax rules differ:

Meta setup, step by step

This is the plumbing behind Facebook, Instagram and WhatsApp ads; strategy lives in our Meta Ads guide.

Accounts and access

1. Business portfolio and security

   You create the portfolio from your own Facebook profile while we guide you, using your public business name. One person can create only two, so we first check whether you already have one. Everyone with access turns on two-factor authentication, which Meta can require before ads publish.

2. Business verification

   Meta asks for official documents, such as a business registration or licence, and can reject applications from websites that fail to load or lack HTTPS.

   Verification is not the blue tick

   Meta Verified for businesses is a separate paid subscription, and Meta alone decides who gets the badge.

3. Page, Instagram and WhatsApp

   Ads Manager needs a Facebook Page, or a role on one. We connect your Page, Instagram account and, for click-to-WhatsApp ads, your WhatsApp number (on the Business app or the Business Platform), which must be linked to your Page or portfolio.

4. Ad account and spending limit

   You create the ad account inside your portfolio while we guide you, with currency and time zone set as shown in the locked-settings table. A new portfolio starts with one ad account, rising to three after a campaign delivers and a payment clears. On automatic billing, an account spending limit is our safety net: once reached, every campaign pauses (prepaid accounts cannot set one).

5. Partner access

   You add our portfolio as a partner, using the ID we send, and assign the ad account, Page, Instagram account, dataset and catalogue.

Tracking

1. Pixel, dataset and Conversions API

   The Meta Pixel is code on your site that reports visits and actions; Events Manager now shows it inside a dataset with the same ID. Browser tracking loses events to ad blockers, network problems and failed page loads, so Meta recommends running the Conversions API (CAPI) alongside it, sending the same events from your server. We aim for the 75% event coverage Meta suggests (the share of Pixel events that also arrive from your server), using one of four routes:

   • Meta-enabled Conversions API: free and one click for sites already running the Pixel, web events only, where your account offers it.
   • Your platform’s integration: Shopify, WooCommerce and Wix, among others, have one.
   • Conversions API Gateway: Meta’s codeless option, hosted in your own Amazon Web Services or Google Cloud account.
   • A direct build by a developer, the only route for app and in-store events.

2. Domain verification

   We verify your root domain with a meta tag, HTML file or DNS record; all are free and cover subdomains. Meta no longer needs it for event setup, but it still controls who can edit your link previews.

3. Events and custom conversions

   We agree which actions count before tagging anything, starting from Meta’s standard events below. Event names are case-sensitive (Lead is not lead). Where no standard event fits, a custom conversion on a “URL contains” rule fills the gap, up to 100 per ad account.

   Event	Meta’s definition	Where we fire it
   Lead	A sign-up is completed	Thank-you page or success message
   Contact	Contact starts by phone, SMS, email or chat	A tap on a WhatsApp or call button
   Schedule	An appointment to visit you is booked	A confirmed site visit or consultation
   SubmitApplication	Someone applies for a product, service or programme	An admission, loan or dealership form
   Purchase	A purchase is made; value and currency are required	An online store’s order confirmation

   Source: Meta Pixel reference for standard events, checked October 2026. Swipe sideways to see where we fire each event.

4. Testing and Event Match Quality

   Test leads must reach the Test Events tool from browser and server, with Diagnostics clear. Event Match Quality (EMQ), Meta’s 0–10 score for how well server events match people on Meta, rises as you send more customer information: email and click ID have the highest priority, then phone, external ID and browser ID. Email and phone are hashed; click and browser IDs are sent as they are.

Google setup, step by step

Fewer accounts, more moving parts in measurement. Campaign types and bidding live in our Google Ads guide.

Account and tags

1. Account and manager link

   The account sits under a Google account your business controls, with currency and time zone set as shown in the locked-settings table and your GSTIN in the payments profile. Our manager account sends a link request for your admin to accept. Of Google’s five access levels, keep at least one Admin login yourself.

2. Advertiser verification

   Google will eventually require it of every advertiser, and your business name and logo appear in Search ads only after it, so we start early.

3. Tag Manager and the Google tag

   Your developer installs the Google Tag Manager (GTM) container once; after that, tags change without touching site code. Inside go the Google tag (formerly the global site tag), one tag for Google Ads and Analytics, and the Meta Pixel. Every change is tested in GTM’s preview mode with Tag Assistant before publishing.

Conversions and data

1. GA4 and key events

   GA4 calls important actions key events (renamed from “conversions” in 2024). We mark your lead actions as key events, link GA4 to Google Ads and raise data retention to 14 months, the maximum for standard properties.

2. Primary and secondary conversions

   Primary actions feed bidding and the Conversions column; secondary actions are only observed.

   The classic double count

   One enquiry recorded by the Google Ads tag and again by a GA4 import, both set as primary. One of them must become secondary.

3. Enhanced conversions and auto-tagging

   Enhanced conversions add hashed (SHA-256) form details, such as email or phone, so Google matches more conversions to clicks. From June 2026, Google has been merging the web and leads settings into one on/off switch. Auto-tagging, on by default for new accounts, adds the GCLID click ID that offline uploads rely on.

4. Consent mode

   Consent mode passes each visitor’s choice to Google’s tags. In basic mode, tags wait for your banner and stay blocked if the visitor declines. In advanced mode, they load at once and send only cookieless pings (signals sent without cookies) while consent is denied, which gives Google an advertiser-specific model of missed conversions; basic mode gets only a general model. India’s own consent rules are covered below.

5. Calls, Business Profile, Merchant Center, YouTube

   • Calls: Google forwarding numbers work in India, so calls from ads can count as conversions (caller numbers are not shown for India).
   • Local: a linked Google Business Profile enables location assets and Performance Max for store goals.
   • Online stores: Shopping ads need Merchant Center, which supports India and rupees.
   • Video: a linked YouTube channel lets Google build audiences from your viewers.

Website and landing page readiness

The ad ends at the click; the page decides whether it becomes a lead. Every landing page passes these checks before paid traffic, and our Website Development service fixes any that fail.

• Fast on a mid-range phone. Google’s “good” Core Web Vitals: Largest Contentful Paint (main content shown) of 2.5 seconds or less, Interaction to Next Paint (response to a tap) of 200 milliseconds or less, and Cumulative Layout Shift (layout jumps) of 0.1 or less.
• HTTPS on every page, which Meta’s verification expects.
• WhatsApp and call buttons visible on mobile and tracked as Contact events.
• One lead event per lead, fired after a successful submission, never on the button click.
• Instant follow-up: each submission reaches your CRM and alerts whoever calls back.
• Hidden fields store UTMs and click IDs (gclid, fbclid), so the CRM knows which ad produced each lead.
• A privacy policy page: Meta instant forms and Google lead form assets both require one.

Consent under India’s data protection law

India’s Digital Personal Data Protection (DPDP) Act, 2023 and DPDP Rules, 2025 (notified in November 2025, with most obligations applying from May 2027 after an 18-month phase-in) call for a clear, standalone consent notice that states the purpose. People must be able to withdraw consent at any time, and tracking and targeted advertising directed at children under 18 are barred. On your forms, that means:

• An unticked consent box beside the submit button.
• A link to your privacy policy.
• No pre-ticked marketing opt-ins.
• An easy way to withdraw consent later.

For ad tags, we recommend a cookie banner with consent mode.

UTMs and naming conventions

UTM parameters are tags at the end of an ad link that tell your analytics and CRM where a visitor came from. They only help when written the same way every time.

utm_source={{site_source_name}}&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_term={{adset.name}}&utm_content={{ad.name}}

Meta fixes name-based values such as {{campaign.name}} at the name used when the ad was first published. Renaming later does not change them, and editing URL parameters after publishing can restart the learning phase, so names are final before launch.

On Google, the same tags go in the final URL suffix: text that Google adds to the end of every ad link.

utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_term={keyword}&utm_content={creative}&matchtype={matchtype}&device={device}

Auto-tagging already serves GA4, which gives the GCLID priority over manual tags; this suffix is for your CRM.

# Campaign: GOAL-Type_Market_Offer_YYYY-MM
LEADS-Form_Nagpur_3BHK_2026-11
LEADS-Search_Nagpur_2BHK_2026-11

# Ad set or ad group: Audience_Detail
Prospecting_Broad-15km
Retarget_Visitors-30d

# Ad: Format_Hook_Version
Reel_PriceReveal_v1
Carousel_FloorPlans_v2

The goal comes first (Leads, Sales, Traffic), then the type: the conversion location on Meta (Form, WhatsApp, Website) or the campaign type on Google (Search, PMax for Performance Max). No spaces (links turn them into %20), underscores between parts, hyphens inside them, dates as YYYY-MM, and one pattern for both platforms.

How the tracking fits together

The browser and your CRM each have a route to both platforms; your server adds a second route to Meta. The server and CRM routes matter more every year: Safari blocks third-party cookies and shortens script-set ones, iPhone apps must ask before tracking across other companies’ apps and sites, and Chrome leaves third-party cookies to each user’s choice.

Server-side events recover part of what browsers lose, but they are no way around a visitor’s choices; Meta says the Conversions API is not designed to bypass rules like Apple’s App Tracking Transparency. The same events build the audiences in our retargeting playbook.

Deduplication: one lead, counted once

Browser and server both report the same lead. Meta keeps one copy when the event name and event ID match and both arrive within 48 hours.

// Browser: Meta Pixel. The event ID is the fourth argument.
fbq('track', 'Lead', {}, {eventID: 'lead-4821'});

// Server: the same lead through the Conversions API
{
  "event_name": "Lead",
  "event_time": 1793263200,
  "event_id": "lead-4821",
  "action_source": "website",
  "event_source_url": "https://www.example.com/thank-you/",
  "user_data": {
    "em": ["<SHA-256 of the email>"],
    "ph": ["<SHA-256 of 91 + mobile number>"],
    "client_user_agent": "<visitor's browser>",
    "fbp": "<_fbp cookie>",
    "fbc": "<_fbc cookie>"
  }
}

The CRM feedback loop

A form fill is not a customer. Platforms that only see form fills find more form-fillers, including people who never answer the phone; sending outcomes back from your CRM helps fix that. Our CRM (Chatbots & AI Agents) service can build the pipeline.

Meta: Conversions API for CRM

Lead status (intake, qualified, converted, lost) goes back to your dataset through a CRM integration, a connector such as Zapier, or a Google Sheets connection with a lead_status column. Meta’s fit guidelines for optimising on these stages:

Leads a month

200 or more

Data uploads

Daily

Target stage reached

Within 28 days

Leads that reach it

1% to 40%

Since April 2026, new campaigns can use the “Maximize number of qualified leads” goal only with a Conversions API integration of this kind, and existing campaigns have been affected since August 2026. Smaller accounts still gain: the same CRM stages drive your reporting and the uploads to Google described below.

For WhatsApp leads, Business Platform partners can send chat outcomes through the Conversions API for business messaging; we plan it with your WhatsApp Marketing setup.

Google: Data Manager

Google calls classic offline conversion import a legacy feature and recommends enhanced conversions for leads through Data Manager, which connects CRMs such as Salesforce and HubSpot, BigQuery, files or a Google Sheet. Mind the deadlines:

The launch checklist

We tick every line before the first campaign spends. Use it to check your own setup.

Reporting dashboard setup

Each platform marks its own homework. Meta credits the last ad someone clicked or engaged with, otherwise the last ad they saw, and reports each conversion on the day the ad was shown. Most ad sets report on a 7-day click window plus short windows for engage-through (interactions other than link clicks) and view-through (people who only saw the ad); we check the setting in each ad set.

Google Ads uses data-driven attribution by default for most conversion actions, sharing credit across the ads someone interacted with, based on your account’s own data. The two rarely agree, so your CRM is the tie-breaker.

We build the dashboard under your business’s own login and share it with your team, so it stays with you if we stop working together. It reads from each platform and your CRM, so nobody retypes numbers, and we review the numbers with you, typically every month.

Since March 2026, Meta has been rolling out a change to click-through attribution (crediting a conversion to an ad someone clicked): for website and in-store conversions, only link clicks count, and other clicks move to engage-through. Some accounts may still use the old definition, so compare periods with care. Next comes budget structure: see our guide to Advantage+ campaign budget vs ad set budget (CBO vs ABO).

A typical setup timeline

Most of the waiting is for access and platform reviews, not the work itself.

Questions we get asked

Official references

1. About business portfoliosMeta · Business Help Center
2. How to change the time zone for your ad account in Meta Ads ManagerMeta · Business Help Center
3. Handling Duplicate Pixel and Conversions API EventsMeta for Developers
4. Specifications for dynamic URL parameters in Meta Ads ManagerMeta · Business Help Center
5. Updates to your enhanced conversions settingsGoogle · Google Ads Help
6. About consent modeGoogle · Google Ads Help
7. Taxes in your countryGoogle · Google Ads Help
8. DPDP Rules, 2025 NotifiedPress Information Bureau · Government of India