Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Performance Marketing › Expert

Combining Two Paid Programmes After an Acquisition for a Cloth Nappy Maker

An invented cloth nappy maker has bought a smaller rival whose ad account bids on the buyer's own name, whose analytics double counts purchases and whose customers sit in a separate CRM. Starting from both inventories and the analytics scorecard as given, you work the overlaps, set the freeze, keep two baselines, gate the new CRM connector and order the moves channel by channel so each one can be read.
ExerciseExpert levelModule 3: Combining programmes after an acquisition5 minUpdated

Why this matters

The advanced performance marketing level aligned signals, proved channels and set profit targets inside one business. An acquisition adds a second programme whose numbers follow other rules and whose accounts may work against yours. The danger is quiet: a loss in the acquired business vanishes inside the combined totals, and a hurried connector makes someone reachable who asked not to be.

The nappy maker and the business it bought

Faemaern Nappies is an invented maker of reusable cloth nappies that sells online through Google Ads, Meta and email. It has bought a smaller rival with its own website, ad accounts and customer list, whose name the board will keep for now. Both inventories are taken and the rival's analytics is scored.

Illustrative example — not a real result

Faemaern Nappies: what the inventories and the scorecard show

AreaFaemaernThe acquired rival
Google AdsBrand and generic campaignsRun by a freelancer; bids on Faemaern's name and on 60 of the same generic terms
MetaProspecting and remarketingProspecting only, optimising for purchases from its own pixel
AnalyticsScorecard greenKey events gate missing: a duplicate tag sends the purchase event twice on some orders; Google Ads counts that imported event and its own purchase tag, both primary
Customers21,000 contacts in the marketing platform6,800 in a separate CRM with its own email tool
CalendarSummer saleA spring trade-in offer, already announced
  • Monthly orders, last full quarter: Faemaern 2,300 from its order system; the rival 960 in its back office and 1,240 in its analytics.
  • 1,150 people appear in both customer lists; 70 of them opted out of one business while subscribed to the other.
  • Both businesses run a review tool and an email tool.
  • Day-one requests: the freelancer wants the Google Ads accounts merged next week; sales wants the rival's CRM connected to Faemaern's marketing platform now and its whole list sent the welcome series.

What two programmes add to one inventory

The tutorial on combining marketing after a merger begins with an inventory of each business, which Faemaern has. The work here is the rows that exist only because there are two programmes: searches both accounts buy, people in both lists, tools doing one job twice and each business's promises. They decide what waits and what every later move is read against.

Task

  1. List the overlap rows and say what each one puts at risk.
  2. Set the freeze: what stops, what carries on and who approves an exception.
  3. Record both baselines and say where the rival's figures come from, and for how long.
  4. Gate the connector between the rival's CRM and Faemaern's marketing platform.
  5. Order the moves channel by channel and say how each will be read.

Worked answer

The overlap rows. The rival bidding on Faemaern's name is the first: on branded search the two accounts compete for people who already chose Faemaern, and on the shared generic terms they bid against each other. The people in both lists come next, the conflicting permissions first, because a merge on the default rule could make an objector reachable again. Two email and two review tools form the third row, and the announced trade-in offer is a promise the combined calendar keeps.

The freeze. A change freeze covers both programmes: no new campaigns beyond the calendar, no new tools, no account merges and no list imports until each area's move is planned. Live campaigns, agreed budgets and the trade-in offer carry on. Faemaern's head of marketing is the one person who approves an exception, and each one enters the change log. Both day-one requests wait.

Two baselines. Faemaern's Baseline comes from its order system and its analytics. The rival's cannot come from analytics: the analytics implementation scorecard rates duplicated key events as a missing gate, its red band, so its purchase figures are flagged unreliable and decisions resting on them pause. The rival's baseline is read from its back office until the duplicate is fixed and a complete reconciliation window agrees. Brand searches for each name are recorded beside both.

The connector. The CRM sync change checklist gates it. An integration register row names its owner. Which records cross is set as a condition on CRM fields, keeping test and service-only records out. Each synced field gets one owner and one direction, and matching on the agreed key turns the shared customers into single records. The strictest consent value wins in both directions, opted-out people stay as suppressed records and the customer flag crosses so buyers skip prospect sequences. A contact who opted out, a past buyer and a record someone corrected by hand are seeded and read in a test account before go-live. The welcome series waits for whoever handles data protection to decide who may be mailed at all.

The order. Paid search moves first, because its fault distorts bidding: the Google Ads account audit checklist is run on the rival's account, tracking first, and its imported analytics purchase is the duplicate it looks for. Each channel move gets a go or no-go review and a fortnight on its own, read against both baselines.

Illustrative example — not a real result

Faemaern Nappies: the arithmetic and the order

Rival analytics against its back office: 1,240 ÷ 960 ≈ 1.29, about 29% more purchases than happened. Shared customers: 1,150 ÷ 6,800 ≈ 17% of the rival's list.

FortnightMoveRead against
1Both baselines recorded; freeze starts—
2Rival's Google Ads audited; imported purchase set to secondary, its own tag primaryBoth baselines
3Rival stops bidding on Faemaern's nameBoth: Faemaern brand cost and orders; rival orders
4 to 5Rival analytics fixed and rescored after a complete reconciliation windowRival back-office orders
6Connector live after seeded records passSynced and suppressed counts on both sides
7Rival's Meta account reviewed and its future decidedBoth baselines

A fall confined to the rival after one move points at that move, and is fixed before the next starts.

Common mistakes

  • Merging accounts before either baseline exists. No loss can then be seen or attributed.
  • Reading the rival from its analytics. A failed gate makes its figures unsafe for decisions.
  • Letting the connector's defaults decide consent. The default rule can restore a subscription a later opt-out removed.
  • Keeping only the combined baseline. The parent's numbers hide a loss in the business it bought.

Pages this lesson applies

Terms used on this page

Also related

Related