Annesha Basu works in content and paid media. Their LinkedIn posts share practical advice on setting up ads, keeping campaign tracking consistent, and reconciling platform results with CRM records.
Annesha Basu is useful for hands-on paid media tracking, UTM hygiene, and reconciling platform ad results with CRM records.
Best for
A B2B marketing agency needing someone to own tracking hygiene and CRM reconciliation across client accounts.
Not for
Campaigns needing documented sponsorship formats, a media kit, or verified audience demographics.
Key takeaways
Use a UTM convention: source, medium, campaign, content.
Build URLs in a shared sheet and check CRM after first week.
Explain platform versus CRM lead gaps rather than force a single total.
Check first: Ask for a named client case study showing their role and results.
Main ideas
Make measurement choices before spending · Use consistent UTMs so campaign data stays readable · Explain the gap between platform and CRM counts instead of forcing a single total
Annesha Basu writes about the practical work of paid media: setting up campaigns, keeping tracking consistent, and understanding why ad-platform results may differ from CRM records. Their posts trace a move from five years in content into paid media, while continuing to value writing.
Basu connects specific operating rules to the reporting problems they are meant to prevent.
Their UTM guidance, for example, explains how inconsistent capitalization can split one channel into several CRM lines, then recommends a shared URL sheet and an early CRM check.
Their lead-count post adds a useful qualification: platform and CRM totals may differ because they count different events, so the goal is to understand the expected gap and spot what’s new.
Alongside the pre-launch checklist, these posts offer practical tracking guidance that considers what happens after an ad click—not just what the platform reports.
They also show a willingness to describe learning a new discipline rather than presenting every tactic as settled expertise.
Across four posts, Annesha Basu treats paid-media measurement as a matter of clear definitions and repeatable checks, not a hunt for one perfect number.
Read more
Their advice is to make tracking choices before launch, keep naming consistent and distinguish expected reporting gaps from new problems. They also write about carrying lessons from content into a new discipline while accepting the discomfort of being a beginner.
Make measurement choices before spending
Basu’s launch advice starts with deciding what counts as a conversion and where it should be recorded.
Read more
They recommend setting up pixel checks, consistent UTMs, a useful landing-page next step, CRM comparison and a capped learning budget before campaign data accumulates.
For a ChatGPT Ads test, Basu recommends checking the GTM pixel on both the landing and thank-you pages in preview mode, then comparing platform conversions with CRM records from day one. They say someone arriving from a ChatGPT conversation is often still researching, so the landing page should offer a clear next step.
Use consistent UTMs so campaign data stays readable
Basu says inconsistent source and medium values split one channel into several CRM lines, making reports harder to trust.
Read more
Their remedy is a fixed naming convention and a shared process for building URLs, followed by an early check of what reaches the CRM.
They define source as the platform, medium as the paid channel, campaign as the platform campaign name and content as the variation being tested. They recommend building URLs in a shared sheet rather than typing them by hand, then checking CRM records after the first week of spend.
Explain the gap between platform and CRM counts instead of forcing a single total
Basu says two systems may count different events, so a mismatch is not automatically a tracking fault.
Read more
They recommend learning which part of the difference is normal and investigating what changes, rather than treating either system’s total as the only true number.
Basu contrasts a platform’s 40 leads with 31 in the CRM. Possible structural causes include a form submission that never reaches the CRM, a lead merged into an existing contact or a conversion firing on page load rather than on submission.
Treat starting over as a way to grow, not proof you are unsuited to the work
Basu describes adding paid media after five years in content while continuing to value writing.
Read more
They say marketing fundamentals can carry across disciplines and that being uncomfortable as a beginner can be worthwhile.
They write that earlier experiences with paid media had gone badly, motivating them to learn it. After about a year, they say they had grown beyond their starting point, though they do not claim to be a pro.
If you want to know who Annesha Basu is and why their writing returns to ad tracking and reporting, start here.
After five years in content, Basu decided to add paid media to their work.
They describe it not as a break from writing but as a second discipline they pursued because they had been bad at it and that bothered them.
The transition meant going from knowing what they were doing to genuinely not knowing, and sitting with that discomfort.
After about a year of practice, they conclude that marketers grow faster from a standing start than they expect, that fundamentals carry over more than they think, and that the part of marketing they avoid because they feel unsuited to it may be worth entering.
For brands planning a campaign
Read this as a snapshot of where this person is in their paid media career: roughly a year in, learning on live accounts, with a content background.
For a hiring decision, ask what carried over from content, what they still consider their weak spot in paid media, and how they get up to speed on an unfamiliar client account.
The tactical posts reflect an early-career media buyer, not someone with long tenure.
It shows what this person checks before turning on spend in a new channel, with a concrete sequence to compare against your own process.
Read more
Basu describes running ChatGPT Ads for one account and lists the checks they used before launch: confirm the GTM pixel fires on the pages that matter, testing in preview mode on the landing page and thank-you page rather than the homepage alone; put UTMs on every ad, with the source and medium written as they should appear in the CRM; map conversion events to the specific actions that should count, since a demo request and a pricing page visit are different events; make sure the landing page gives visitors a next step, on the reasoning that someone arriving from a ChatGPT conversation is usually still researching; compare platform reporting with the CRM from day one and know which number is reported to the client; and keep spend caps small while learning the channel. They say the channel is converting for them and that acquisition costs on new placements do not stay low for long.
For brands planning a campaign
This is the closest thing in the set to an audit checklist, and it maps onto a first-30-days plan for a new client account: pixel placement, UTM build, conversion definitions, landing page action, dual reporting, and a learning budget.
The claim that the channel is converting is a personal observation with no figures attached; ask for results before treating it as a benchmark.
A useful interview prompt is which of these six checks they have seen go wrong on a takeover account.
It shows how this person keeps tracking consistent across accounts and offers the clearest example of their writing style: a rule set with reasons attached.
Read more
Basu argues that most reporting problems on paid media accounts trace back to UTMs: inconsistent source and medium settings split one channel into three or four lines in the CRM, leaving no one confident in the numbers.
Their convention: source is the platform (google, linkedin, bing — lowercase, always spelled the same way); medium is how it was paid for (cpc for search, paid_social for LinkedIn, one word per channel, never varied); campaign matches the campaign name in the platform so a deal can be traced back without a lookup table; and content carries the variation being tested — ad variant, audience, creative — so a CRM record can be tied to a specific test.
Two operating rules follow: build URLs in a shared sheet rather than by hand in the ad editor, because one person typing LinkedIn instead of linkedin creates a second channel in reports; and check what actually lands in the CRM after the first week of spend, while a mistake is still cheap to fix.
For brands planning a campaign
This is the most directly relevant post for a brief focused on tracking hygiene and CRM reconciliation.
In an interview, ask who owns the shared naming sheet, how the convention is enforced across people and agencies, and what happens when a client's CRM contains several years of inconsistently tagged history.
Their rule to check the CRM in week one also suggests a cheap, testable first deliverable for a new engagement.
It shows how this person thinks about mismatches between platform and CRM numbers, the reasoning behind the tracking work in the other posts.
Read more
Basu opens with the gap: the ad platform reports 40 leads for the month, while the CRM reports 31.
They argue that the gap is not automatically a tracking error to hunt down and fix.
Some of it is structural: a form submission that bounces before reaching the CRM, a lead merged into an existing contact and no longer counted as new, or a conversion that fires on page load instead of on submit.
In their framing, each system counts a different event but uses the same word for it.
Chasing one "true" number is the wrong instinct; what matters is knowing which part of the gap to expect every month and which part is new.
For brands planning a campaign
Probe this reconciliation stance in an interview.
Ask how they set an expected monthly gap with a client, who signs off on which number goes in the report, and how they distinguish a structural difference from a new fault.
This pairs naturally with the UTM post: the same person sets the URL convention and explains why totals will still differ.
Basu describes running ChatGPT Ads for a client account and the checks they make before switching on a campaign: confirm the GTM pixel fires on the pages that matter by testing in preview mode on the landing and thank-you pages, not just the homepage; put UTMs on every ad, with the source and medium set as they should appear in the CRM; map conversion events to specific actions, since a demo request and a pricing-page visit are different events; give the landing page a clear next step, because someone arriving from a ChatGPT conversation is usually still researching; compare platform-reported conversions with CRM records from day one and decide which number to report to the client; and keep spend caps low while learning the channel.
Read more
A pre-launch checklist covering tracking, attribution, conversion definitions, landing-page tasks, reporting reconciliation and budget control—all cheaper to fix before data starts flowing.
For brands planning a campaign
A useful template for a first campaign on an unfamiliar placement: Basu's checklist is a launch-readiness audit a brand could run before spending, showing where they expect new-channel tests to break. They say the channel is converting and acquisition costs on new placements rise over time; ask for the underlying results before using those claims as planning benchmarks.
A UTM convention for keeping paid traffic readable
Basu traces most paid media reporting problems to inconsistent UTMs: when source and medium vary across campaigns, the CRM splits one channel into three or four lines and trust in the numbers collapses.
Read more
Their convention: source names the platform (google, linkedin, bing), in lowercase and always spelled the same way; medium describes how it was paid for (cpc for search, paid_social for LinkedIn), with one word per channel and no variation; campaign matches the campaign name in the ad platform so a deal can be traced without a lookup table; and content identifies the variation under test, whether an ad variant, audience or creative. They recommend two practices: build URLs in a shared sheet instead of typing them into the ad editor, and check what lands in the CRM after the first week of spend, while mistakes are still cheap to correct.
A fixed naming convention plus two process controls: one to prevent hand-typed inconsistencies and one to catch them early.
For brands planning a campaign
This is directly testable in an interview or paid audit: ask a candidate to name their source/medium convention and explain how they enforce it across a team. Basu's answer points to centralised URL building and a first-week CRM check as enforcement points, which map onto a 30-day tracking audit plan.
Explaining the gap between platform and CRM lead counts
Basu opens with a concrete discrepancy: an ad platform reporting 40 leads against 31 in the CRM.
Read more
They argue the gap is not automatically a tracking error to hunt down.
Some of it is structural: a form submission that bounces before reaching the CRM, a lead merged into an existing contact and no longer counted as new, or a conversion that fires on page load instead of on submit.
Each system is counting a different event and calling it the same thing, so chasing a single true number is the wrong instinct.
What matters, in their framing, is knowing which portion of the gap is expected every month and which is new.
Reframes reconciliation as an expected-variance question rather than a defect to eliminate, separating structural causes from new anomalies.
For brands planning a campaign
For a brief centred on CRM reconciliation, this is the clearest signal of how Basu thinks: they would build an expected-variance baseline and flag departures from it, rather than promise a zero-variance number. Ask in an interview how they would explain the variance to a client who expects exact parity between platforms and the CRM.
Basu writes that after five years in content, they chose to add paid media—not because they were finished with writing, but because every earlier encounter with paid media had gone badly and that bothered them.
Read more
The post is about starting over in a new part of marketing: going from knowing what you are doing to genuinely not knowing, the difficulty of sitting with that gap, and what they say they learned in the following year—that people grow faster than expected when starting from scratch, fundamentals built elsewhere carry over, and the discomfort of being a beginner is worth it. Their closing advice: the part of marketing you have been avoiding because you think you are not built for it is probably the one worth entering.
This is a career-change reflection rather than a technique, and it makes no claim about how much paid media work Basu has delivered or for how long in total.
For brands planning a campaign
Basu writes their own briefs and commentary and came to paid media deliberately after a content background. Ask in an interview about their experience delivering paid media work and their seniority in the field.
The four LinkedIn posts reviewed document no sponsorships, affiliate arrangements, investments, employers or named client brands for Annesha Basu.
Read more
The only visible commercial relationship is on the buying side: Basu says their team has been running ChatGPT Ads for one account. Elsewhere, they refer to unnamed client accounts and mention Google, LinkedIn and Bing only as examples of UTM source values.
OpenAI
Mention
Basu says their team has been running ChatGPT Ads for one account and lists the checks they make before launch: pixel firing, UTMs, conversion event mapping, landing-page next steps, platform-to-CRM comparison and spend caps while learning the channel.
Read more
They say the channel is converting for them. The post shows OpenAI's ad platform as a channel their team buys on for a client, not a partnership, sponsorship or endorsement.
Annesha Basu's posts read as working notes from someone running paid media inside client accounts.
Read more
The pre-launch list for a new ad placement sets out what to confirm about pixels, UTMs, conversion definitions, and reporting before any spend starts.
The UTM naming post gives a source/medium/campaign/content convention and two habits to keep it intact.
Another post examines a platform reporting 40 leads against 31 in the CRM, arguing that part of the difference is structural and worth learning to expect rather than chasing to zero.
The career post stands apart: it describes choosing to move from content into paid media and what that felt like, rather than offering a technique.
All four are short, concrete, and free of product pitches, making them useful to readers looking for checks they can apply this week.
Before choosing Basu, ask for account walkthroughs, named-client examples, budget figures, and details of any service offer; none appear in these posts.
Both writers treat measurement as a chain that has to connect a campaign to a business outcome, and give readers checks rather than opinions.
Read more
Akash separates traffic-source reporting from revenue attribution and gives three checks for tracing a conversion event back to the campaign that influenced it; Basu does similar work at a smaller scale, separating platform-reported leads from what reaches the CRM. Both warn against set-and-forget tracking and prescribe a periodic audit.
Akash writes longer essays aimed at a leadership budget conversation, with scenarios, figures, and a GA4-to-Salesforce framing, and covers Google Ads setup step by step. Basu works in shorter operational notes centred on UTM hygiene and lead-count gaps, stating conventions to adopt rather than rehearsing a scenario.
Roy's Shopify-versus-Meta purchase counts reflect the same problem Basu describes with 40 platform leads against 31 in the CRM.
Read more
Both start by questioning the assumption that the ad platform is overcounting. Each separates whether the event was captured correctly from whether platforms credit the same outcome the same way, and lists specific mechanics, such as duplicate events or attribution windows, that produce the gap.
Roy works in ecommerce tracking: Meta Pixel and Conversions API deduplication, external payment flows, and EU consent limits.
Their posts are heavily formatted and include an open invitation to connect.
Basu applies similar reasoning to B2B lead reporting and CRM reconciliation, using plain formatting and no contact invitation.
Rowe argues that LinkedIn optimises only toward the events it can see, so form fills get optimised instead of deals.
Read more
The same concern runs through Basu's writing about what happens between the click and the CRM record. Both describe wiring post-click lifecycle data back to the ad platform so the reported number reflects a business outcome, and both draw on hands-on client work rather than theory.
Rowe's posts build toward a named product with a trial link, and each ends on that offer; Basu's four posts focus on process and carry no product or service offer. Rowe writes specifically about LinkedIn, while Basu ranges across placements and general naming rules.
Annesha Basu's posts show a practical focus on paid-media setup, tracking, and CRM reporting.
Read more
For a campaign requiring a particular professional audience, ask for recent audience survey results or another documented source on viewers’ roles and seniority.
Annesha Basu’s posts describe no partnership or sponsorship offering: no published rate card, media kit, sponsored-format examples or inquiry route.
Read more
They do explain how Basu approaches paid media execution, which could shape a sponsored arrangement.
Their writing calls for completing setup before launch: verifying the pixel and conversion events on landing and thank-you pages, not just the homepage; keeping UTM conventions consistent in a shared sheet; agreeing on what counts as a conversion; and comparing platform-reported conversions with CRM records from the first day of spend.
Basu also writes about setting small spend caps during a new channel’s learning period.
A brand considering a paid collaboration should ask Basu directly whether they offer sponsorships and on what terms.
For a brief where a B2B marketing agency needs someone to own tracking hygiene and CRM reconciliation across client accounts, Annesha Basu is a credible fit.
Read more
The available posts show a working method.
In the UTM post, they set out a convention: source for the platform, medium for how it was paid for, campaign matching the platform campaign name, and content for the variation under test.
Two controls come with it: build URLs in a shared sheet rather than by hand, and check what lands in the CRM after the first week of spend.
In the platform-versus-CRM post, they treat a 40-versus-31 lead gap as partly structural and argue the job is to know which part of the gap is expected every month and which part is new.
The ChatGPT Ads post adds a pre-launch checklist: pixel fires on landing and thank-you pages, UTMs written for CRM readability, conversion events mapped to specific actions, a landing page with a clear next step, platform-to-CRM comparison from day one, and small spend caps while learning.
That maps closely to tracking hygiene and reconciliation work.
The posts describe roughly a year in paid media after five years in content, and the client work is unnamed.
Before hiring, ask for a named client case study that demonstrates their role and results.
The fit is for a hands-on tracking and reporting role with clear scope, not for someone presented as a long-tenured media buyer.
When to choose a specialist
Basu is a poor fit for a campaign that needs a creator with documented sponsorship formats and a verified professional audience.
Read more
The posts contain no published rate card, media kit, sponsored-format example, inquiry route, or audience-demographic information. For a campaign whose main requirement is reach into a defined buying audience or an existing paid-collaboration product, ask for a media kit and audience data before considering them.
A worked campaign example
Worked campaign angle for the agency brief: sell a 30-day paid-media tracking audit before any spend increase.
The angle is to fix attribution before scaling the account, using Basu's own sequence.
Week one: inventory every active campaign's UTMs against one naming convention and check what lands in the CRM after the first week of spend.
Week two: map conversion events to the actions that count, separating a demo request from a pricing-page visit, and verify pixel fires on landing and thank-you pages in preview mode, not just the homepage.
Week three: build a platform-versus-CRM reconciliation baseline, document the expected structural gap, and agree which number gets reported to the client.
Week four: write the shared URL-building sheet and the conversion-definition memo, then set small learning spend caps for the next channel test.
Interview questions: how would you enforce a source and medium convention when several people build URLs; how do you tell a structural lead-count gap from a new tracking fault; who owns the reported number when the ad platform and CRM disagree; what is your first-week check after spend starts; and how would you audit an account with years of inconsistently tagged history?
Choose Md Kamrul Islam Akash if the agency needs someone who can explain and audit platform-level conversion tracking, especially in Google Ads, and distinguish traffic-source reporting from revenue attribution for clients.
Read more
The Google Ads post lays out a step-by-step sequence: define the conversion action, install the tag, add value tracking, test before launching, and monitor monthly.
It also lists hidden mistakes, including tag manager changes that break tags and JavaScript form submissions that miss thank-you page tracking.
The revenue attribution post offers three checks: trace a conversion event to a business outcome, verify the attribution path across a 30-day customer timeline, and identify where the reporting chain breaks.
Choose Akash when the deliverable is an audit framework or training material on conversion tracking and attribution.
Compared with Annesha Basu, these posts offer broader educational walkthroughs, with less focus on a specific live account or a team-wide URL-building convention.
They do not show hands-on reconciliation of platform and CRM lead counts or a first-week check after spend starts.
Choose Akash to teach conversion tracking and attribution; choose Basu to enforce UTM naming consistency and reconcile live lead counts.
Choose Bivas Kumar Roy if the agency needs someone focused on diagnosing purchase-count discrepancies between Meta Ads and ecommerce platforms such as Shopify, including pixel and Conversions API deduplication, event IDs, test or internal orders, payment redirects, consent, and attribution windows.
Read more
The posts give a structured audit sequence: check attribution first, check deduplication, audit the purchase event, inspect external payment flows, review consent and measurement limitations, then separate tracking issues from attribution issues. Choose Roy when the account is ecommerce-heavy and the live problem is Meta versus Shopify purchase counts, rather than B2B CRM lead-count reconciliation.
The material is narrower on B2B lead workflows.
It does not cover UTM governance for a multi-client agency, a platform-versus-CRM lead gap method, a shared URL sheet, or a conversion-definition memo.
The posts assume an ecommerce purchase event as the outcome, so the 30-day audit plan would need adapting for B2B lead stages.
Choose Roy for ecommerce tracking cleanup; choose Basu for B2B lead-count reconciliation and UTM governance.
Choose Justin Rowe if the agency's problem is LinkedIn-specific: sending downstream CRM events such as MQL, SQL, opportunity, and closed-won back into LinkedIn so the platform optimises toward deals rather than form fills.
Read more
The posts explain that LinkedIn can optimise only for events it can see, describe the gap in a four-month B2B sales cycle, and outline the Conversions API route for passing CRM events back.
The cost-per-click post reframes the issue as a request for evidence about which companies are engaging and moving through the CRM, which suits an agency answering client questions about pipeline influence, not just lead counts.
Choose Rowe when the channel is LinkedIn and the deliverable is a CRM-to-platform conversion feedback loop.
The posts point to DemandSense to connect CRM events, tying the operational detail to that product rather than a platform-neutral method.
They do not cover UTM naming conventions, Google Ads conversion tracking, or multi-platform reconciliation.
The recommended setup may not fit an agency seeking a tool-agnostic audit plan.
Choose Rowe for LinkedIn CRM-event optimisation; choose Basu for cross-channel tracking hygiene and lead-count reconciliation.
Annesha Basu's LinkedIn posts include a note on moving from five years in content into paid media, a ChatGPT Ads pre-launch checklist, a UTM naming convention, and a post on reconciling ad-platform and CRM lead counts.
The posts are undated, and the material spans May to September 2026, so sequence and recency are approximate rather than established.
This profile covers those four posts.
No other channels, longer-form writing, named client results, audience demographics, or sponsorship material are available, so a signature book, show, or earlier body of work remains an open question rather than an assumption.
Similar-creator comparisons use two posts each from Md Kamrul Islam Akash, Bivas Kumar Roy, and Justin Rowe, dated September and October 2026.
