Integration
Your own measurement. With consent.
The gift card page is a sales page, and you should be able to see what happens on it — in your own Google Analytics, not in ours. Put your container ID into the dashboard, and your own Google Tag Manager runs on the page, with Kuvert telling it what the customer does: every step from opening the shop to a paid purchase.
Status
Ready
Works today. You set it up yourself, and there's nothing to wait for.
How it works
Three steps
- 01
Copy your container ID
It is in Google Tag Manager and looks like GTM followed by some characters.
- 02
Put it in under settings
One field. There is no script to insert and nothing to do to the side.
- 03
Build your triggers on our events
Everything you have already set up in the container runs on the gift card page — and on top of that, Kuvert puts every step into your dataLayer: shop opened, gift card chosen, went to payment, bought. The dashboard shows you the whole list with the names you need.
Details
What to know
- It is loaded only after consent
- The container is not fetched until the customer has agreed to statistics. If the customer says no, it is never fetched — not fetched and then switched off afterwards.
- It is your container, not ours
- The measurements land in your own account, and you can see and change everything in it yourself. Kuvert is not in the middle of your figures.
- One container, not a catalogue
- The field takes one container ID. If other things should go in, they belong inside the container where you have control over them yourself — that is what a tag manager is for.
- Google's names where they fit
- We use Google's own names — view_item_list, select_item, begin_checkout — where they mean the same thing as they do here, so an ordinary GA4 tag understands them by itself. The steps Google has no name for are called kuvert_ something. We do not dress them up as something they are not.
- The purchase is sent to two places
- It lands in your dataLayer as purchase on the page between the payment and the receipt — a brief «we are getting your gift card ready» page with not a single code on it — so your own tags can fire on it. And it is sent straight from our server to your Google Analytics once the payment is confirmed, so a sale counts even if the customer closed the tab. Both carry the same transaction_id, so GA4 counts it as one purchase. The server side needs a measurement ID and an API secret, which you set in the same place.
- Your container never runs on the receipt
- The receipt page shows the customer’s live gift card and ticket codes, and a tag on a page can read the page. That is why the purchase fires on the page before it — and it is a rule you cannot switch off, because what it protects is your customer’s card.
- You can see whether it works
- Under Integrations it says what the last real browser experienced: does it work, does the container not exist, was it blocked, or did the customer say no thanks. A container ID sitting in a field is not the same as a container ID that works.
Questions
Frequently asked questions
Can I put a Facebook pixel in?
Yes, through your own container — that is how a pixel is normally set up. Kuvert has no pixel function of its own, and we would rather say it straight than let a logo imply something else.
What about consent and GDPR?
The container is loaded only when the customer has agreed to statistics in the consent box on the page. What happens inside your container after that is your own responsibility — it is your account and your tags.
I cannot see any events in my Tag Manager. What is wrong?
Usually nothing — you simply have not said yes to statistics. The container is not loaded until consent is given, so if you open your own shop in Tag Assistant without clicking «Allow», the debugger never gets hold of the page and the container looks dead. Click yes and reload. If there is still nothing, look at Integrations in the dashboard: it says whether the container could be loaded at all.
Do you send the customer's name or email along?
No. There is no field for it. Your container can pull in any tag at any time, and then the greeting the customer wrote to their mother-in-law would end up with a third party nobody gave permission to. We send the step, the shop, what was looked at, and what it cost.
Can I pass the purchase on to Meta?
Yes. purchase goes into your dataLayer just like the other events, so an ordinary Meta tag in your container can fire on it without anyone having to translate anything. It is in Google’s ecommerce format — transaction_id, value, currency and items — and it happens on the page between the payment and the receipt, where no code is shown.
Why is there an extra page after the payment?
Because the receipt shows the customer’s gift card code, and your container must never run on a page with a code on it. That small page in between is the only place the purchase can be told to your own measurement. It shows «we are getting your receipt ready» for a moment and sends the customer on by itself — and shops with no container never see it at all.
Other integrations
Features
- Gift cardsAn amount, a greeting and a code
- Punch cardTen punches on one card, not an amount
- TicketsA date, a table, a ceiling
- Table bookingFrom 0 kr.: tables, times and guest book
- CampaignsA bonus percentage over a fixed period
- On your websiteThe purchase opens in an overlay on your site
- MobilePayMobilePay alongside the cards
- Scheduled deliveryThe card is sent on the chosen date
- Redemption and scannerScan the code, or enter it
- AccountingFigures your accountant can reconcile
- All features
Get started on your own site.
Create a shop, connect Stripe and add your products. You pay only when you sell.