Visit count spikes when using s.tl for campaign tracking

It's certainly possible they're running those scripts on their end too. Have you checked to see if there are any common dimensions that might contribute to this spike, like pageName, geographical location, or anything else? You can also getting additional visitor information via Data Warehouse (like IP address and visitor ID).

Hi mforemanmc,

I suspect what's happening is that you're getting more 'visits' because you're firing a beacon call from another domain. You could look in the server report and see if that domain's traffic amounts to the increase in your visits/uniques. I would suggest that in Everage instead of calling s.tl you use that script to set a cookie for your campaign/experience and then scrape that cookie value into your normal page level tracking.

I've looked for other common dimensions, but I haven't found any -- including the two you mentioned. I don't have Data Warehouse, so that's not an option; however, our unique visitor count shoots up when the script is running, so it doesn't appear that it's the same IP/visitor generating all the new visits.

That's my guess as well. My server report doesn't show anything unusual, but that's not surprising. I'm not firing the server variable in my s.tl call.

One detail I didn't mention: The visit counts on the variables I'm firing don't match the increase in visits. The visit count on the eVars being fired is higher. These variables aren't being fired from anywhere else. My conclusion: I'm not getting an extra visit every time the script fires -- only some of the time.

I like your cookie solution. I'd been planning on doing something similar if I couldn't find a way to fix the s.tl method. Unfortunately, the way my CMS is set up makes it impractical, so I want to explore other possibilities first before I go down that road.

Can you see the requests going to your tracking server if you use the developer tools built into the browser? If so you should look for the s_vi or Marketing Cloud Visitor ID value getting sent from the custom link server call vs. the page load call.

I've checked this a number of times, and it's always shown the same visitor ID for both my page-level s.code and the extra Evergage s.tl code.

It's hard to say whether that's the case for every visitor, since it's not double-counting every time.

I should also add: Different browsers behave differently. Chrome and Firefox are getting visit spikes, but Edge/IE and Safari are staying normal.

I've tried to duplicate the problem on my end in Chrome, and I've been unsuccessful.