Pound sterling is the currency of the United Kingdom, written with the symbol £ and identified by the international currency code GBP under the ISO 4217 standard. A pound is divided into 100 pence. In marketing systems, GBP is the value you choose or send wherever a platform asks for a currency.
One note on naming: in this glossary and across digital marketing, GBP is also the usual abbreviation for Google Business Profile. The context nearly always makes it clear, but it is worth knowing when you read a report that mentions both.
How GBP works across your marketing tools
The same currency appears in several places, each with its own format:
- Prices shown to shoppers. The UK convention is the symbol before the number with no space, a comma for thousands and a full stop for pence: £1,250.00. Small amounts are often written in pence, as in 99p. Customer-facing copy should use £ rather than “GBP 1,250”.
- Structured data. In Product schema, the offer’s price is a plain number such as 1250.00 and the currency goes in a separate field, priceCurrency, as “GBP”. The symbol does not belong in either.
- Product feeds. Google Merchant Center expects a price followed by the code, such as 1250.00 GBP, and it must match the price on the landing page. Prices for UK consumers should include VAT.
- GA4. Each property has a reporting currency set in its admin settings. Every ecommerce event, such as purchase, should send a value and a currency parameter. GA4 converts other currencies into the reporting currency, but if the currency is missing, revenue may not be recorded properly.
- Ad accounts. Google Ads and Meta ad accounts are given a currency when they are created, and that sets how you are billed and how costs and conversion values are reported. Google Ads does not allow the currency to be changed afterwards, and changing it on Meta is also disruptive, so getting it right at setup matters.
Why it matters
A currency mismatch rarely causes an error message. It just makes the numbers wrong. If a site’s data layer sends purchases in US dollars because of a theme default, and GA4 reports in pounds, every order is converted at the exchange rate and revenue is understated. If the ad account is in dollars, your bank may add conversion fees to every bill, and ROAS comparisons with GA4 stop lining up.
For UK retailers, the price shown also has to be the total a consumer pays, which is why feeds and pages should show VAT-inclusive prices rather than net figures.
Common mistakes
- Creating a Google Ads or Meta account in US dollars by accepting a default.
- A GA4 property left on the currency it offered at setup rather than GBP.
- Purchase events with a value but no currency parameter.
- Schema prices written as “£1,250.00”, which tools cannot read as a number.
- Feed prices without VAT, leading to price mismatch disapprovals.
- A report that uses “GBP” for both revenue and Google Business Profile metrics without saying which is which.
How to act on it
Run a short audit. Check the currency in GA4’s property settings and in every ad account’s settings, along with the time zone set alongside it. Place a test order and inspect the purchase event in GA4’s DebugView to confirm currency is “GBP” and the value is correct. Run a product page through the Rich Results Test and look at the price and priceCurrency fields. In Merchant Center, check for price mismatch warnings.
If an ad account was created in the wrong currency, plan the move to a new GBP account at a quiet time, because its history does not come with it. I check these settings at the start of any PPC management engagement, before judging any campaign on its figures.