CopyPlug - high-converting website design for restaurants, local shops, DTC and ecommerce brands, from one-page sites to full custom builds

• Meta pixel, installed and firing

  This is what tells Facebook and Instagram who visited your site, so your ads can go back to those people instead of starting over with strangers. It runs on your own Meta account, counting visits from the day you go live, and we watch it fire before we hand the site over.

• Google Analytics 4, wired to your property

  The report that tells you how many people came, where they came from and what they looked at. We connect it to your own Google account before launch, so the numbers are already there waiting for you, instead of starting from zero the day you finally set it up.

• Server-side Conversions API

  The pixel lives in the browser, and browsers drop some of what it sends. This is a second route that reports the same actions straight from your server, so Meta can still tell which of your ads brought you a customer. We scramble the email address before it leaves your server, so Meta never sees the real one, and every action carries its own tag so nothing is counted twice.

  It runs on the same host as your site, so there is no second server to rent. We connect it to your own Meta account with you at handover and watch the events land in your Events Manager before you put a dollar behind an ad.

• Consent, honoured in the code

  Some browsers carry a privacy setting called Global Privacy Control. When a visitor has it switched on, we do not track them for ads. Nothing is anonymised, nothing is stripped, nothing is sent: the ad and analytics scripts never load at all, and the server route to Meta refuses that visitor too.

  If that same person hands you their email address, it still reaches your list, because that is something they asked for rather than something you took. It is built into every site we make, not a setting someone has to remember to switch on.

• Structured data

  Search engines do not only read your words, they read a summary written for them in code. We write yours into the pages you want found: what you do, where you work, how to reach you, and what you sell with its price. So Google gets a clear description of your business instead of piecing one together itself. Schema markup, clean headings, real page titles, a sitemap that tells Google every page exists. It is the half nobody looks at, and it is in every build.

• Open Graph, so the link looks right

  When somebody pastes your link into a message, a group chat or a post, it should come up as a proper card with an image, your name and a line about you, not a bare grey link. We set that on every page worth sharing, so every time a customer passes you on, you look like a real business.

• A lead capture path that does not drop anyone

  Every form saves the lead on your own site before it goes anywhere else, not straight out to somebody else’s service. Then the person is added to your email list, where they said yes to it, and if that hand-off ever fails the lead is held and sent again rather than lost.

  A form that quietly loses leads is the most expensive thing on a small site, because nothing ever tells you it happened.

For context on what a server-side setup normally carries: Google's own documentation puts a production server-side tagging container at roughly $45 per server per month, with a minimum of two servers recommended, before anyone is paid to configure it. Ours is a smaller thing than a full tagging container. It carries your Meta conversions and nothing else, and it costs you nothing on top of the build. Source: Google for Developers, Set up server-side tagging with Cloud Run, updated May 2026

All of it is in the build price on this page. None of it is an add-on, none of it is a monthly fee, and none of it is a reason to put you on a retainer.