How to track visitors on Yolabi.

Yolabi is a hosted, no-code store builder, so this is one pasted tag and nothing to deploy. Five minutes.

What you need

• A Yolabi store you can edit and publish.
• A VisitorPing site key, in the form vp_ABC23456 — the prefix vp_ and eight characters. The alphabet leaves out I, O, 0 and 1, so there is nothing to misread when copying it.

Install it

1
Get your site key
Add the store's domain as a website in VisitorPing. The site key appears with the installation instructions. Use one key per store — reusing a key across two stores merges their visitors into a single stream.
2
Open the store's tracking settings
Yolabi holds five tracking settings for a store:
- • Google Analytics ID
- • Google Tag Manager ID
- • Facebook Pixel ID
- • Custom head scripts — the one you want
- • Custom body scripts
They are independent of one another, so adding VisitorPing does not disturb an analytics or pixel value already set.
3
Paste the tag into head scripts
Put this in the custom head scripts field, with your own key in place of vp_ABC23456:
```
<script defer crossorigin="anonymous" src="https://cdn.visitorping.com/site/vp_ABC23456.js"></script>
```
Head placement matters — the tracker should load with the page rather than after it. The tag is deferred, so it does not hold up rendering.
4
Save, publish, and check
Publish the store, then open it and view the page source. The tag should be in the <head>. A visit should reach your dashboard within a couple of seconds.

You will see your own visits

Worth knowing up front, because it differs from our WordPress plugin.

A pasted tag has no idea who is looking at the store. On WordPress the plugin skips logged-in users who can edit posts, so owners do not ping themselves. Here there is no such thing: every time you open your own storefront to check something, that is a visit.

Expect the first day of data to include a lot of you. Use your VisitorPing settings to filter your own traffic rather than reading the raw first-day numbers as demand.

If the tag is not there

The store was not republished: Saving a setting and publishing the store are separate actions on hosted builders. Publish, then reload the live domain rather than a preview.
You are looking at a preview URL: Check the live custom domain. Preview and editor views do not always carry store settings.
The key is wrong: Look for a copied trailing space, and for characters outside the key alphabet. An O or a 1 means you have misread a lookalike — real keys never contain them.
You cannot find the head scripts field: It may not be exposed on every plan. Yolabi supports custom domains, so the store can instead be tracked from the edge: proxy the domain through Cloudflare and deploy our Cloudflare Worker, which injects the same tag into every HTML response without touching the store. Check the Cloudflare SSL mode against the certificate Yolabi issues for the domain first.

What you will actually see

Per visit: the city and region the network resolves to, where the visitor came from, the page they landed on, their device and browser, and whether they have been before.

You do not get a name, an email address, or an identity. Nobody can give you that from a page view, whatever the marketing says. Geolocation resolves a network rather than a doorstep, so a visitor on a VPN or a mobile network can appear in the wrong city entirely. Treat location as a hint.

Yolabi ships its own analytics; VisitorPing runs alongside it and neither displaces the other. You are collecting visitor data either way, so say so in your privacy notice and check which consent rules apply where your customers are — a question for your own legal advice, not for a setup guide.

Find what is costing you search clicks, then watch the fix work.

VisitorPing reads your own Search Console data for the pages losing clicks, then rings your phone the moment someone lands on your website.

Start Free Trial See how it works

Install it

Get your site key

Add the store's domain as a website in VisitorPing. The site key appears with the installation instructions. Use one key per store — reusing a key across two stores merges their visitors into a single stream.

Open the store's tracking settings

Yolabi holds five tracking settings for a store:

• Google Analytics ID
• Google Tag Manager ID
• Facebook Pixel ID
• Custom head scripts — the one you want
• Custom body scripts

They are independent of one another, so adding VisitorPing does not disturb an analytics or pixel value already set.

Paste the tag into head scripts

Put this in the custom head scripts field, with your own key in place of vp_ABC23456:

<script defer crossorigin="anonymous" src="https://cdn.visitorping.com/site/vp_ABC23456.js"></script>

Head placement matters — the tracker should load with the page rather than after it. The tag is deferred, so it does not hold up rendering.

Save, publish, and check

Publish the store, then open it and view the page source. The tag should be in the <head>. A visit should reach your dashboard within a couple of seconds.

You will see your own visits

Worth knowing up front, because it differs from our WordPress plugin.

Expect the first day of data to include a lot of you. Use your VisitorPing settings to filter your own traffic rather than reading the raw first-day numbers as demand.

If the tag is not there

The store was not republished

Saving a setting and publishing the store are separate actions on hosted builders. Publish, then reload the live domain rather than a preview.

You are looking at a preview URL

Check the live custom domain. Preview and editor views do not always carry store settings.

The key is wrong

Look for a copied trailing space, and for characters outside the key alphabet. An O or a 1 means you have misread a lookalike — real keys never contain them.

You cannot find the head scripts field

It may not be exposed on every plan. Yolabi supports custom domains, so the store can instead be tracked from the edge: proxy the domain through Cloudflare and deploy our Cloudflare Worker, which injects the same tag into every HTML response without touching the store. Check the Cloudflare SSL mode against the certificate Yolabi issues for the domain first.

What you will actually see

Per visit: the city and region the network resolves to, where the visitor came from, the page they landed on, their device and browser, and whether they have been before.