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

Standard Operating Procedures

Live Ad and Page Error Response SOP

A standard procedure for an error in a live ad, landing page or post: confirm it, contain it, correct it through approval, tell the right people and log it.
SOPintermediate10 min readUpdated

Owner, trigger and scope

The campaign owner runs the response from the first report to the log entry. They can pause, revert and unpublish in their own channels and know where the asset runs. The approver who signed off the original asset approves the correction; where the error touches a claim or a price, the compliance reviewer named in the creative approval SOP approves it too. The customer service lead hears about the error, and what customers will be offered, before customers start asking.

The trigger is a report from anyone, inside or outside the team, that a live ad, Landing Page, social post or other live asset is wrong: a wrong price or date, an expired code, a broken link, a wrong audience or a claim that no longer holds. Treat every report as real until the first step shows otherwise.

The guide to reviewing a marketing error holds a routing table that sends each kind of error to the page owning its immediate response. Live ads and pages had no procedure of their own; this is it. The other rows keep their owners:

Where the error isWhere the immediate response lives
A marketing email already sentFixing a mistake in a sent email
Output produced with AI toolsHandling an AI mistake
Conversions or events stopped recordingTracking outage response SOP
Public criticism on social channelsSocial media crisis plan
An automated journey sending the wrong thingAutomation governance
An asset withdrawn on purpose: a licence ends, a claim is retired, a product changesWithdrawing an asset from every channel

An error can belong to more than one row. A wrong price in an ad that also went out by email runs this procedure for the ad and the sent email guide for the email, with the campaign owner keeping both in one log entry. The SOP library routes the other recurring jobs. The academy checkpoint on hijacked accounts, live errors and incident programmes tests routing errors another procedure owns, customer remedies and approvals, and briefing service before a correction goes out.

Before you start: inputs and access

InputOwnerNotes
The report and the evidenceWhoever reported it, then the campaign ownerA screenshot or link of the error as it appears, with where and when it was seen
Where the asset runsCampaign ownerFrom the campaign brief or the launch record of the paid campaign launch SOP
Edit accessCampaign owner and channel ownersThe ad platforms, the site and the social scheduler
The approval route and its fast laneApproverWho can approve an urgent correction, and how to reach them
The error logMarketing operationsThe shared log the review guide describes

If the campaign owner cannot reach edit access for a channel, the first call is to whoever can, before anything else. An error nobody can switch off is the one that grows.

The procedure

  1. Confirm the error and capture it as customers see it

    Look at the asset where customers see it, not in the build or the file: the live ad preview, the published page, the post on the profile. Confirm what is wrong and what it should say. Capture it with screenshots and links, the time, the placement and, for an ad, the campaign and ad names. The review guide builds its timeline from records rather than memory, and the evidence gathered now is what it will use. If the report turns out to be a misunderstanding, note it in a line and close.

  2. Route errors that another procedure owns

    Check the routing table above. If the error is in a sent email, AI output, tracking, an automated journey or a public conversation that is turning into criticism, hand that part to its owning page now and keep only the live ad, page or post here. A broken page that also stops a Conversion Action from recording is two problems: correct the page here and let the tracking outage SOP own the measurement. Write down who took each part, so the log can join them up later.

  3. Find everywhere the wrong version runs

    The ad that was reported is rarely the only copy. List every place the wrong version runs: other ads and ad sets using the same creative, the platform's creative library, the landing page and any duplicates of it, scheduled and pinned posts, email templates, partner and affiliate pages, printed material and translations. The tutorial on withdrawing an asset from every channel lists where assets hide and how to find each one. Use its list; do not rely on memory of where the campaign ran.

  4. Contain it: pause, revert or unpublish the wrong version

    Stop the wrong version from reaching more people, choosing the smallest action that does it. Pause the ad or ad set, revert the page to its last approved version, unpublish or hide the post, take the scheduled posts out of the queue. The launch check in the campaign workflow guide confirms what was approved, which tells you what to revert to. Leave correct work running. Record the time each copy was contained; the log asks for the date found and the date contained, and the gap between them is what the review will try to shorten.

  5. Decide with the commercial owner what customers who acted on it receive

    Some people will have acted on the error: ordered at the wrong price, tried an expired code, booked the wrong date. Decide with whoever owns pricing or the offer what they receive. The tutorial on setting remedies and goodwill limits separates what a customer may be entitled to from goodwill on top, and asks for the entitlement column to be checked by someone qualified for the sector and country. The regulators the site's claims and promotions pages cite, the ASA and the CMA in the UK and the FTC in the US, share the principle that advertising must not mislead and that prices and offers must be honest. As general direction rather than legal advice, that is why the decision is taken deliberately, written down and applied the same way to everyone.

  6. Correct it through the approval fast lane

    The correction is a new version of an approved asset, so it goes back through the creative approval SOP, using the team's fast lane for urgent work so it is not stuck in the queue. The campaign workflow guide's fast lane still uses the launch check; the social approval workflow adds that anything touching a claim, a price or a sensitive subject leaves the fast lane and gets its normal check. Fast does not mean unchecked. If the error was a claim, confirm the corrected wording against the claims library before it goes out. Someone other than the person who made the error approves it.

  7. Brief customer service and answer people who saw it

    Before the correction goes live, give the customer service lead what happened, what is corrected, the remedy and the wording to use, in the shape the tutorial on briefing customer service before a campaign uses for a one-page brief. Then answer the people who saw the error: replies under the post or ad, messages and emails. The service recovery guide sets the sequence, from acknowledging and apologising to fixing and following up; write in the Brand Voice and name the specific mistake. If comments are turning into criticism, the crisis plan's holding statements and approval route take over that conversation.

  8. Check the correction is live everywhere and log the error

    Go back through the list from the find-everywhere step and confirm each copy is corrected or removed, including scheduled posts, the creative library and cached pages. Click through the corrected ad to the page and complete the conversion to confirm it still records. Then add an entry to the error log the review guide describes, and decide against its triggers whether the error needs a full review: customers saw it, money was lost, a price or claim was involved, or the same kind of error has happened before. The review asks why until the cause is a process rather than a person, using the five whys; this procedure hands it the evidence.

A garden furniture retailer's wrong sale price (illustrative)

Illustrative example — not a real result

Last season's price on this season's bench

Holtzibar Garden Furniture, an invented garden furniture retailer, hears from a customer at 9:40 on a Saturday that a teak bench is advertised at £249 in a social ad, against a current price of £389. The campaign owner confirms it in the live ad preview and captures it: the price belonged to last autumn's sale and had been carried into new creative from an old template.

The routing check finds no email or automation involved. The find-everywhere list turns up 3 ads in 2 ad sets, the bench's landing page banner and a pinned post on the brand profile. By 10:15 both ad sets are paused, the banner is reverted to its last approved version and the pinned post is hidden.

Eleven orders were placed at the wrong price. The commercial owner decides to honour all 11 and to offer a £20 voucher to anyone who contacts the shop about the advertised price after the correction. The customer service lead receives the brief and 2 saved replies before anything is republished.

The corrected ad goes through the fast lane; because it carries a price, the compliance reviewer approves it as well as the original approver. The campaign owner checks all 5 copies, completes a test order through the corrected ad and logs the error. It meets the review triggers, and the review later traces the cause to creative templates that keep old prices in their layers.

QA checks

The campaign owner runs these checks before the response is closed. A check that fails reopens the step it belongs to; it is not left for the review to find.

  • The wrong version is gone from every channel on the list, including scheduled and cached copies.
  • The correction went through an approver, not only the person who made the error.
  • Customer service has the wording and the remedy before the correction goes out.
  • The error log has the dates found and contained and where it ran.
  • A decision on whether the error needs a full review is recorded.

Hand-offs and records

The procedure hands on to four places. The customer service lead receives the brief and the remedy, and reports back any contacts that do not fit it. The commercial owner receives the list of customers who acted on the error and what each was given. Any part routed elsewhere, such as a sent email or a broken tracking tag, stays with its owner, with the log entry joining the parts. If the error meets the review triggers, the person running the error review receives the evidence, the timeline of containment and the correction, and the review's actions go back to whoever owns the gap it finds.

The lasting record is an entry in the error log: what was wrong, where it ran, when it was found and contained, who saw it, the remedy decided, who approved the correction and whether a review follows. The academy exercise on handling a hijacked account and a wrong ad price for a climbing centre practises running this response for a paid ad still showing last season's membership price, beside a hijacked account on the same weekend.

Common mistakes

Most of them come from fixing the copy that was reported and stopping there.

  • Fixing the reported copy only. The same creative usually runs in other ads, posts and pages.
  • Correcting before containing. While the correction is drafted, the wrong version keeps running.
  • Pausing far more than the error. Containment should stop the wrong version, not every campaign near it.
  • Skipping the approver because it is urgent. Errors are often repeated in a correction nobody else read.
  • Letting customer service find out from customers. Brief them first, with the remedy and the wording.
  • Deciding the remedy case by case. Agree it once with the commercial owner and apply it to everyone.
  • Deleting the evidence with the error. Capture the error before removing it, or the review has nothing to use.
  • Not logging small errors. The log is how the same error, repeated, becomes visible.

Frequently asked questions

Should we pause the whole campaign when one ad is wrong?

Contain the wrong version, not more than that. Pause the ad, ad set or post that carries the error, or revert the page to its last approved version, and leave correct work running. Pausing a whole campaign can cost more than the error did, and it makes it harder to tell later what the error itself affected. If the error sits in something every ad shares, such as the landing page or a feed, containing it may mean pausing everything that points there.

Do we have to honour a wrong price that customers saw in an ad?

That is a commercial decision taken with whoever owns pricing, and where rights are involved, with someone qualified to advise for your sector and country. The procedure does not answer it for you. What it does is make sure the decision is taken once, written down, given to customer service before anyone asks, and applied in the same way to everyone who acted on the error.

Who should fix the error: the person who made it or someone else?

The person closest to the work can usually make the correction fastest, but someone else approves it before it goes live. Errors are often repeated in the correction because the person who made them reads what they meant rather than what they wrote. The approver who signed off the original asset is the natural choice, because they already know what it was meant to say.

Terms used on this page

Frameworks

Where this page is used

Part of these learning paths

Also related

Sources

  1. Advertising Standards Authority — ASA
  2. Competition and Markets Authority — GOV.UK
  3. FTC business guidance — Federal Trade Commission

Related