Hey guys,
This is my first week on STM and what a load of information! I don't want to be boring and say what all newbies already have said but: big thumbs up for all contributors here
I'm learning a lot and it will cost me at least one more week to get through all the good stuff! (I've been reading A LOT this week)
I also started my first campaign in
The thing I can not figure out is why the stats from Exoclick and
What am I missing here?
This could probably be the result of unique clicks vs raw visits (same user visiting the lander several times).
If so, do you guys calculate the landing's CTR by uniques/clicks or raw/clicks?
I just discovered the campaign stats in Exoclick are in New York times. Only in the 'Hours' tab you can select time zone.
This means that here in The Netherlands you see a time difference of 6 hours.
I'm still looking into this difference. In
I see the same type of thing. Depending upon the country and type of traffic, I've seen
I'm having the exact same problem. I contacted
That's normal behaviour with Exoclick, nothing wrong with
I don't know what the exact reason is for the big discrepancy, but could be something like impressions that you don't get billed for from people outside of your targeting (different GEO, outside of frequency cap etc.)
What I do to still get a somewhat accurate CPC is to compare the
E.g.: 1000 impressions on Exo vs. 1500 impressions in Voluum at a $0.1 CPC
1000 / 1500 = 66.66 %
CPC that I put into Voluum: $0.1 * 66.66 % = $0.066
In addition to that you can use Voluum's "update cost" feature for stats from previous days (don't forget to set the correct timezone, for Exo it's NYC Time meaning UTC - 4 during summer time and UTC - 5 during winter time)
I just got this response from
"Hi,
The reason why you see the discrepancies is due to the fact that we recently updated our reporting servers.
Therefore, you may see a temporary miscorrelation of data across different reports.
For your peace of mind, none of the data is lost.
The alternating stats which are shown on front end is due to a miscommunication between the GUI and our backend reporting schemas.
This has been resolved.
Apologies for the inconvenience."
Start of a new day and I just checked my stats again. There still way off. SMH