Three ways to attribute a Manchester new-build enquiry, with proof limits

What to take away

Three attribution methods for a Manchester regeneration campaign

Manchester is a testbed for creator-led new-build campaigns. The city has a fast-growing media and proptech cluster, strong regional agency networks, and a pipeline of regeneration schemes in areas such as Ancoats, Holt Town and the Northern Gateway, now badged Victoria North. Manchester City Council has set out a development framework for Holt Town.

A campaign for one of those schemes will usually produce enquiries through three routes. A creator posts a walkthrough of a show apartment and the platform reports clicks. A viewer taps a tracked link to a landing page and registers interest. A buyer turns up at the marketing suite and says a video brought them in.

Each route answers a different question. Platform data answers how many people saw and tapped. Landing-page data answers who gave details after a specific touch. Self-reported data answers what buyers remember. None of them answers the same question, so none can be swapped for another.

Agency marketers often collapse the three into one number. That is where a Manchester regeneration campaign starts to overclaim, and where a claim about creator performance becomes hard to defend if a developer or a compliance reviewer asks for the evidence.

Method one: platform-reported enquiries and what they miss

Platform-reported enquiries are the numbers a creator or platform supplies: views, reach, link taps, saves, and sometimes a count of direct messages. They arrive quickly and cost little to collect.

They are useful for judging whether a hook worked. A video about a two-bed apartment at a Manchester regeneration scheme may earn strong saves and shares, which tells you the creative landed. That is a reach measure, not an enquiry measure.

What the method misses is identity. A platform count cannot tell you whether the person who tapped is the person who later registered, or whether the same person tapped five times. Duplicate taps, bot traffic and out-of-area viewers all inflate the total.

The method also misses consent. A tap is not a lawful basis for sending a follow-up email or text about the development. That step needs its own basis, which is why a property lead attribution plan should separate the platform count from the contactable lead.

Use platform numbers to compare creative, not to credit sales. When you report them, label them as reach and engagement, and keep them apart from enquiries you can name. The difference between the two is the difference between a metric and a lead.

Method two: tracked landing pages and consent under PECR

A tracked landing page is the method most agency marketers trust. A creator links to a page built for the scheme, the page sets a unique parameter, and the registration is stored against that source. You can then name the person, the scheme and the touch.

The rules bite before the click. Any cookie or similar storage on that landing page, including analytics and video embeds, falls under the rules on storage and access technologies. Consent must be freely given, specific and informed, and it must be as easy to refuse as to accept.

Electronic marketing then needs a lawful basis. The Guide to PECR sets out when you may send electronic marketing and what consent has to look like. A registration form that buries consent in small print will not carry a follow-up campaign.

Choosing that basis is a deliberate decision, not a default. The ICO's guidance on choosing your lawful basis explains how the basis you pick changes what you may do with the data and how long you may keep it.

A practical route is to keep the landing page lean, ask for one clear consent, and record the source parameter alongside it. Then the enquiry is attributable and the follow-up is defensible. This is the same discipline that sits behind metrics defined down to the event, where the denominator is fixed before the campaign starts.

Method three: self-reported 'how did you hear' at viewing

Self-reported attribution asks the buyer, at viewing or reservation, how they heard about the scheme. It is cheap, it needs no tracking, and it captures influences that leave no digital trace, such as a friend's recommendation or a poster on a hoarding.

In a Manchester regeneration campaign it often produces the most interesting answers. Buyers describe a creator's video, a local news piece and a walk past the site in the same breath. That mix is real, and no click log will show it.

Its weakness is memory. People forget, compress several sources into one, or name the creator they watched most recently. Answers also shift depending on who asks the question and how the options are worded.

A single answer cannot prove that a creator caused an enquiry. It proves that the buyer recalls a creator, which is a different claim. Treat the field as a qualitative signal that explains the mix, and keep it out of any per-enquiry credit calculation.

Where you do use it, ask the question before the buyer is influenced by a sales conversation. Record the answer verbatim, with the date, so the pattern across a scheme can be reviewed later rather than reconstructed from memory.

A proof-limits table: what each method can and cannot show

The table below is the one to keep beside any Manchester campaign report. Read each row as a boundary, not a score.

Two limits run across the whole table. No method proves causation. Nor does any row prove a price effect or a scheme-level return.

Here is a worked example, with illustrative figures. Three creator posts report 120,000 combined views and 3,400 link taps. The tracked landing pages log 40 consented registrations against named source parameters. At viewing, 11 buyers answer the recall question, and two name a creator unprompted. The three figures are different populations and cannot be added together.

There is also a regulatory boundary. The Direct marketing checklist is a sensible pre-campaign pass for any agency running creator lead capture, covering consent records, opt-outs and retention.

Scheme claims need their own care. If a campaign describes regeneration powers or local housing delivery, the Localism Act 2011 is the reference for the local powers involved. Keep planning claims separate from attribution claims.

The wider failure this table guards against is attribution called impact. That is the boundary stated at the top, and a report that blurs the two will not survive a developer's questions. A dashboard that makes its joins explicit, and states its attribution limits, is easier to defend than one that reports a single blended figure.

Example: attributing a Manchester new-build enquiry without overclaiming

A North West agency runs a creator campaign for a regeneration scheme in east Manchester. Three creators post show-apartment walkthroughs over four weeks. The agency wants to know what the campaign produced, and what it can honestly say.

Using the worked example above, the honest report says: forty consented registrations came through tracked pages, platform reach was strong, and two buyers recalled creator content. It does not say the creators generated forty leads.

That wording is duller than a headline figure, and it is the version that holds up. It also gives the next campaign something to improve: better consent capture, cleaner source parameters, a viewing question asked the same way every time, and a report that states what the campaign cannot prove.

For teams comparing this approach with other channels, Four ways to attribute a property enquiry applies the same test across four routes rather than the three creator routes set out here.

Common questions