Google and Meta Ads Tracking: A Pre-Agency Checklist

Google and Meta Ads Tracking: What to Check Before Hiring an Agency

A campaign can report plenty of conversions while your sales team struggles to find genuine buyers. The problem may be weak targeting, but it can also be faulty measurement: duplicate submissions, WhatsApp clicks counted as enquiries, or sales that never reach the advertising platforms.

Before hiring an agency, establish what your accounts actually measure. Reliable Google and Meta Ads tracking helps you judge campaign performance, set sensible budgets and distinguish a reporting problem from a lead-quality problem.

1. Define the Business Outcome Before Checking Tags

Ask what the campaign should produce: an enquiry, a qualified appointment, a paid order or a completed sale. These are different outcomes and should not share an undifferentiated conversion total.

• Activity: A phone-link click, WhatsApp click or brochure download.
• Enquiry: A successfully submitted form or recorded customer conversation.
• Qualified lead: A prospect meeting agreed criteria, such as service area, requirement and budget.
• Sale: A confirmed transaction with a defined revenue value.

A WhatsApp button click does not prove that someone sent a message. Similarly, a click-to-call event does not establish that a call connected or produced a valid enquiry.

Agree on these definitions before discussing a target cost per lead.

2. Check Whether Conversions Fire Correctly

Ask the agency to demonstrate a complete customer journey using debugging tools and test submissions. Seeing a tag installed is not enough; it must fire at the correct point, with the correct data.

For lead-generation websites

• Trigger the lead event after a confirmed successful submission, not merely when someone presses Submit.
• Test failed validation, repeated submissions, mobile forms and embedded forms.
• Check whether refreshing a thank-you page creates another conversion.
• Keep contact-button clicks separate from confirmed enquiries.

For ecommerce websites

Verify that purchase events contain the correct currency, order value and unique transaction or order identifier. Test failed payments and order-confirmation page reloads. Document whether reported revenue includes GST, shipping and discounts so it can be reconciled with your accounts.

For Indian stores using cash on delivery, distinguish an order placed from an order delivered. Cancellations, returns and failed deliveries can make order-based ROAS look healthier than realised revenue.

3. Remove Duplicate Signals and Misleading Totals

One sale can appear in several reports without representing several sales. Google Ads, Meta and analytics tools may each attribute the same purchase to their own touchpoints. Do not add their conversion totals together and call that total business revenue.

Within Google Ads, inspect conversion actions and campaign goals. If the same lead is measured through both a direct Google Ads tag and an imported GA4 event, check whether both are being used for bidding. Keep duplicate or diagnostic actions out of the campaign’s bidding goals.

On Meta, browser Pixel events and Conversions API events need appropriate deduplication. Matching event names and event IDs are central to deduplicating the same event sent through both methods.

Ask for an event map showing each event’s trigger, destination and purpose. This should be part of the measurement scope for Google Ads and Meta Ads management, not an unexplained technical extra.

4. Connect Advertising Data to Lead Quality

Platforms cannot reliably optimise towards your definition of a good lead if they only receive form submissions. Your sales process needs to return useful outcomes.

Start with consistent CRM stages: new, contacted, qualified, appointment booked, won and lost. Define why leads are rejected, including spam, wrong location, unavailable service or duplicate enquiry.

For Google Ads, ask whether eligible offline conversion imports or enhanced conversions for leads can connect later outcomes to advertising interactions. For Meta, ask whether supported CRM or Conversions API integrations can send meaningful downstream events.

These setups depend on eligibility, implementation, consent and available identifiers. They improve measurement inputs; they do not guarantee perfect attribution.

Hypothetical example: ₹30,000 spent on 150 enquiries gives a ₹200 cost per enquiry. If only 30 are qualified, the cost per qualified lead is ₹1,000. The second figure is usually more useful for judging lead-generation economics.

5. Reconcile ROAS Before Raising Budgets

ROAS is attributed revenue divided by ad spend. It is not profit, and it does not automatically account for agency fees, product costs, fulfilment or returns.

Before scaling, compare platform reports with CRM or order-system records for the same period. Allow for conversion delays and check attribution windows, time zones and reporting definitions.

For lead-generation businesses, avoid presenting estimated pipeline value as completed sales revenue. If reporting uses projected values, label the assumptions clearly.

Budget decisions should combine acquisition cost, lead quality, sales conversion rate and contribution margin—not a platform ROAS screenshot alone.

6. Confirm Ownership, Consent and Handover

Your business should retain appropriate administrative access to its advertising accounts, analytics, tag manager, Meta business assets and CRM integrations. Give agencies role-based access rather than sharing passwords.

Ask how consent requirements, privacy disclosures and customer-data handling are addressed. Hashing customer identifiers does not remove your responsibility to collect and use data lawfully. Server-side tracking is not a way to bypass consent or platform policies.

Practical Pre-Agency Checklist

• Business outcomes and qualified-lead criteria are documented.
• Successful forms and purchases have been tested on mobile.
• Duplicate conversion actions and events have been reviewed.
• Primary bidding goals match the campaign objective.
• CRM stages and rejection reasons are consistently recorded.
• Revenue definitions, attribution windows and reporting delays are explained.
• Business ownership, access and privacy responsibilities are clear.
• The proposal separates setup work, ongoing management, media spend and tool costs.

Frequently Asked Questions

Is GA4 enough for Google and Meta Ads tracking?

No. GA4 supports analysis, but platform conversion setup, CRM outcomes and business records also matter. The right configuration depends on your sales journey.

Do we need Meta Conversions API immediately?

Not necessarily. First establish accurate events and appropriate consent handling. Evaluate Conversions API against your website platform, integration options and measurement needs.

Why do Google Ads and Meta report different revenue?

They use different attribution rules and may both claim credit for one sale. Check business revenue separately rather than adding platform totals.

Should tracking be fixed before increasing ad spend?

Fix major errors first, especially duplicate purchases or incorrect bidding goals. Minor reporting gaps need not stop every campaign, but document the uncertainty.

Ask for Measurement Clarity Before Campaign Promises

When evaluating ROI-focused Google and Meta Ads management, ask what will be measured, tested and reconciled. To discuss your current setup with IPrix Media, share your campaign goals and tracking concerns.