I am trying to work out the discrepancies between Data View and the exported file from My Tracking for hard bounces.
1 - I extracted a list of hard bounce by running the following query:
FROM _bounce b
WHERE s.JobID = [The_Job_ID]
AND b.BounceCategory = 'Hard bounce'
The last WHERE clause can also be
b.BounceCategoryID = '1'
2 - Meanwhile, I exported the hard bounce CSV file from My Tracking > [The Job], then clicked on the count next to 'Hard Bounce' and exported the CSV file. (by the way, the hard bounce count showed on Tracking page was incorrect as well. I was told by SF Support the exported file provides the most accurate bounce records. They are treating this as a known issue.)
The Data View result contained about 60 more records than the exported file from My Tracking. I contacted SF Support and they said this is because the Bounce Data View includes records which are 'false bounces'. I was told that the following query will give the correct set of bounce records, the only catch we can't use it because 'isfalsebounce' isn't available via Data View:
select * from _bounce a (nolock)
where jobid = [The_Job_ID]
and BounceCategoryID = 1
and isfalsebounce = 0
To add to the confusion, I checked one of the 'false bounces' subscriber in All Subscribers (History tab), a Hard Bounce is showed in History. At this point, I don't know which method(s) give me the most accurate hard bounce count anymore.
I tried to lookup but can't find much about 'false bounce'. What is false bounce?
If 'false bounces' are excluded from My Tracking, why does it showed in Bounce Data View and All Subscribers?
What is the purpose of Bounce Date View if we can't query Hard Bounce records for a job matching My Tracking?
For automated reporting, are there other queries/ better way to extract the same set of hard bounce records for a job?