Snowplow: Warning: No tracker configured

For engineers Tracking SDKs
1

How can we prevent this warning?
We have events that are invoked, but Snowplow Inspector browser plugin does not see them, and no data is logged to the database.
When I say invoked, I mean that this code is being called

snowplow('trackSelfDescribingEvent', {
    schema,
    data: payload,
});
2

How are you initialising the Snowplow tracker? (e.g., the full Javascript snippet) This warning is raised if an instance of the tracker can’t be found.

3

As Mike suggests, this means a tracker hasn’t been initialized.

If you’re getting that error, that means you have installed the snippet but you haven’t called newTracker.

e.g.

snowplow('newTracker', 'sp', '{{collector_url_here}}', {
  appId: 'my-app-id',
  discoverRootDomain: true,
  cookieSameSite: 'Lax', // Recommended
  contexts: {
    webPage: true
  }
});

Full docs on initialization: Initialization options - Snowplow Docs

1 Like
4

How can I print the snowplow’s app_id? I think the prop is tna, tracker name.

It is initialized as such

window.snowplow('newTracker', 'sidetracker', getDomain(), {
    appId: 'side',
    discoverRootDomain: true,
    forceSecureTracker: true,
    postPath: '/path/to/post',
    eventMethod: 'post',
    contexts: {
        webPage: true,
        performanceTiming: true,
    },
});
5

Any thoughts? Is my init incorrect?

6

This initialisation looks mostly correct. The tracker doesn’t have a get method for app_id - but if you use something like the Chrome extension you should be able to see what the app_id is for each event sent.

7

That looks ok. Maybe they are firing in the wrong order? If you’re using GTM could your track call be happening before newTracker has fired? If you are using GTM, then using the trigger ordering will help here.