Tracking Method: how events reach each destination
Every destination can get events from the visitor’s browser, from Upstack’s servers, or both. What each option means and when to change it.
Every destination has a Tracking Method setting. It controls how that one destination receives your events. There are three options.Browser + Server (default, recommended). Upstack does two things. It loads the destination’s own tracking tag on your store, and it sends the same events to the destination from Upstack’s servers. The destination sees the event twice, matches the two copies, and counts one conversion.Server. Upstack sends events to the destination from its servers. The destination’s tag never loads on your store.Browser. Upstack only loads the destination’s tag. The tag reports events from the visitor’s browser, the same way it would if you had installed it yourself.Not every destination offers all three options. The main destinations have all three modes; some have fewer. Check the destination’s page in the destinations catalog to see which options it supports.
Changing this setting never turns off Upstack tracking. Your dashboards, reports, and every other destination keep working exactly as before. It only changes how this one destination gets its events.
Browser + Server is the recommended way to run every destination, and it is the default. The browser path can be blocked by ad blockers and browser privacy settings. The server path cannot. With both running, a blocked browser event still arrives from the server.Switch to Server if you don’t want the destination’s tag loading in the browser.
I changed the setting but my store still loads the tag.
It takes some time for the change to fully roll out to your store. Wait, reload your store, and check again. If it still hasn’t changed, contact support.
