Verify
Prove the install works, and find out what is wrong when it does not.
Load any page with ?vibiz_debug=1 and every event is logged to the console as
it is sent.
https://yoursite.com/?vibiz_debug=1In the Network tab you should see requests to /api/ingest returning 204.
A 204 alone does not prove it works
204 is the only answer this endpoint ever gives, including for a wrong key and for a domain that is not allowed. A visitor page must never see an error from us, which is right for your visitors and unhelpful for you: it means the console can show an event was sent while nothing was stored. Confirm the events also appear in your workspace.
If nothing arrives, both likely causes are in your workspace rather than in the code you just wrote: the key belongs to a different site, or this domain was never added to the site's allowed origins.
The six ways an install goes wrong
Vibiz classifies every site it tracks, and reports the classification back in your workspace. Knowing the vocabulary is worth more than the check itself, because half of these look like success.
| status | meaning |
|---|---|
healthy | Everything worth checking passed. |
not_installed | No event has ever arrived. The tag is missing, or the key is wrong. |
stale | It worked and then stopped. A deploy probably dropped the tag. |
no_conversions | Page views arrive but nothing a campaign can optimise toward. |
attribution_blind | Nothing carries a campaign signal, so ads cannot be credited. |
no_identity | Conversions arrive with nobody attached, so they cannot be matched. |
The middle three matter most, because they all pass a naive check. Data is arriving, the install looks correct, and the numbers will still be wrong a month later.
Ad blockers do not block your own domain. Pointing t.yoursite.com at us and
setting data-vibiz-endpoint typically recovers the 20 to 40 percent of events
blockers would otherwise remove. Ask us to set it up.