Approach

Every business is different, so we always start with a conversation.

How we work
  1. 15 minA quick callYour goals, your numbers, and whether we're a good fit.
  2. 1 hourDiscoveryWhere you're losing enquiries, and what's already working.
  3. ThenA clear planPaid ads, a custom build or both, as a one-off project or ongoing.
About

We're a small London team of marketers, and we use AI to go faster.

About us
  • Cam BowenCam BowenCo-founder
  • Ben PowerBen PowerCo-founder
  • ElectraElectra
  • MahirMahir
  • NatashaNatasha
  • RahabaRahaba
  • ZobaerZobaer
  • EmilyEmily
FAQ answer

How do you set up Stape for your website?

Short answer

We create a server container in Google Tag Manager, host it on Stape, and connect it to your site on your own domain. Depending on the build, that's one or two DNS records on your side (often in Cloudflare), or a path on your main domain with no new records. The rest happens in GTM and Stape. Create the server container and the Stape container, in an EU zone if you want one. Point your domain at Stape, with DNS records or a path on your main domain. Serve GTM from your domain through Stape's custom loader. Send each event to GA4, Google Ads and Meta from the server, with one shared event ID. Test in GTM Preview, then check the data the next day. Our technical tracking service covers it all.

1 min read

What you do

Depending on the build, add one or two DNS records. We tell you what they are and you add them (or give us access to your DNS, which is often Cloudflare). On some builds we use a path on your main domain instead, which is set up on your hosting side (our own site does it with a Cloudflare Worker), so we agree it with whoever looks after that.

What we do

1. The containers

We create a server container in Google Tag Manager and a matching container on Stape, and pick the region. EU zones are available.

2. The subdomains (or a path)

On a subdomain build, one subdomain receives the events and, depending on the build, a second serves the GTM loader. The alternative is a path on your main domain, which needs no new records. Stape's default address is only for testing, because cookies set there aren't first-party, so we use your own domain.

3. The tags

The page sends each event once. In the server container we pass it on to GA4, Google Ads, Meta and, when we want the raw events, BigQuery. The same event ID goes to every platform.

Your consent tool still decides what gets sent. Consent is built per project, so we agree with you how the server container follows it.

5. Testing

We check each event in GTM Preview and the Stape logs. Preview alone isn't proof, so we also look at the next day's data, in particular that the click IDs are real ones.

See the technical tracking service for how this fits with your existing GTM setup.

Similar questions

Also worth asking

Other answers about the same tools.

What is technical and tracking infrastructure?

It's the set-up that counts what happens on your site and sends it where it needs to go: tracking tags, analytics, ad-platform conversions, your CRM connection and cookie consent, plus the hosting and security around your website.

Read the full answer : What is technical and tracking infrastructure?
How do you set up website analytics and tracking?

We agree with you what counts as a conversion, then set up Google Tag Manager and GA4, plus server-side tracking through Stape for sites that spend on ads. Before we hand over, we check the data is actually arriving.

Read the full answer : How do you set up website analytics and tracking?
What is server-side tracking, and why do we use Stape?

Server-side tracking means your site sends each event once, to a server container, and that server passes it on to GA4, Google Ads and Meta, instead of every platform running its own script in the visitor's browser. We use Stape to host that container so you don't have to run a server. It reduces lost conversions. It doesn't get them all back, and it doesn't get round consent.

Read the full answer : What is server-side tracking, and why do we use Stape?
How do you handle compliance management for my website?

We work with your cookie consent tool, or suggest one we've worked with, and connect it to your tags so they follow the visitor's choice. How that's wired depends on the project, so we test what your tags actually do. We don't write legal text or give legal advice, so your privacy policy needs sign-off from someone qualified.

Read the full answer : How do you handle compliance management for my website?
What is ad platform integration and why does it matter?

Ad platform integration means joining your website, tracking and CRM to the ad platforms, so they receive the leads and sales that came from their ads. Without it, bidding learns from clicks and form fills instead of customers.

Read the full answer : What is ad platform integration and why does it matter?

Still have questions?Talk to us

Next step

Bring your numbers.

We'll tell you if the spend makes sense.

  1. A 15-minute callYour goals, your challenges, and whether we're the right fit.
  2. A 1-hour discovery callWe dig into your numbers. Worth a hundred emails.
  3. A concrete planAds, a custom build or both, as a one-off project or ongoing.
15 minutes · No pitch deck · A straight answer