Verify your setup
Three layers confirm your setup, from your browser outward: debug: true shows
events leaving the page, the Fidero Data Viewer shows what happened to each one,
and delivery monitoring watches everything after go-live. Work through them in
order the first time. After that, the viewer is usually the only stop.
In the browser
Section titled “In the browser”Initialise with the debug option while you’re setting up:
fidero.init("YOUR_PROJECT_ID", { debug: true });With debug on, the SDK logs each stage to the console: boot, integration loading
and the full payload of every event it dispatches. Each track call also appears
as a request in your browser’s Network tab, which confirms events are going out.
Take the option out again once you’re done.
Configuration documents it in full.
In the Fidero Data Viewer
Section titled “In the Fidero Data Viewer”Every project includes the Fidero Data Viewer, and your link to it is provisioned
when the project is. It shows every track event, browser and server alike, with
its processing flow: received, enriched, then one status per destination.
| Status | Meaning |
|---|---|
success |
Delivered – the destination accepted the event |
skipped |
Not sent, on purpose – the event doesn’t apply to this destination (wrong channel, no mapping) |
blocked |
Withheld – consent or filtering rules stopped delivery |
failed |
An error – open the event to see what went wrong |
Open an event and each destination shows the request it was sent and the response it came back with, so you can see exactly why something failed. You can filter by event name, destination or date, and the view defaults to the last 24 hours.
After go-live
Section titled “After go-live”Verification doesn’t end when the install checks out. Fidero monitors delivery continuously and flags integration failures and data anomalies proactively, so a break reaches you before it reaches a report. The numbers the platform holds itself to are on Guarantees & coverage.