Postcodes in Analytics

I too have seen counts that I can not explain in scatter maps.  (I've not reported this in a Support Ticket, I've got, other more important issues open with support right now.)

My sense (and this is only anecdotal), is that:

• the scatter map may have some undisclosed limit on the number of postal codes that it can display. For example, if I try to map all members ever in my system, things start to get sketchy, in some of the same ways you are describing here.
• I've also got the sense that you have to include Country, State, City and Zipcode in the geographic area to get it to display correctly.  

Again both of those are very incomplete report backs.  Would love to hear more about your findings.  And if you have not put a support ticket in, I encourage you / your organization to do so.  I know that the Analytics team is actively working on squashing a few bugs right now for upcoming Service Packs.  And the sooner we can surface issues the sooner all of us can reap the benefits of a smoothly working Tessitura Analytics.

Thanks for sharing, hope that's a bit of help.  

P.S. if you would like to share a .dash file here, I'd like to see what you are doing.  (.dash files don't share data, they share the setup of tessitura analytics dashboards.)

Hi Leslie and Tom,

I've got a Ticket open about Analytics Scatter Map which was submitted as a Defect.  Some of it has to do with some Australian GPO box codes not being mapped yet but there is a thing where the scatter map is not honouring the dashboard filters correctly.  There is this work around I got from Support that seems to help a lot 

In your scatter map widget use both Primary Address Country and Primary Address Postcode for the location and add a widget level filter of Primary Address Country set to Australia.  

Perhaps give that a try and see if that helps.

Cheers,

Heath

Hi Heath, thanks for the response. I tried adding the Primary Address Country per your suggestion, and while it cleaned up the larger map (where I was looking at all postcodes), the other map is still not respecting the filter to 6 postcodes, and the numbers still aren't matching up. Sounds like I should probably put in a support ticket, too.

And Tom (or anyone else interested), here's the dashboard:

4353.FOLG-MembershipsbyZip.dash

So I broke down and opened a Support ticket.

I believe that it may have to do with the number of records you are throwing at the map.  It feels like you only ### number of records that can be shown.  I don't know what the ### number is.

I'd encourage you to put in a support ticket as well in case the cause of our two problems are different.

Yep, I just opened a ticket!

When I ran your file I can really see the problems as well.

So I turned the Map into a pivot Table and discovered the following.

Note we have the "Primary Address Postcode" in your map that I've turned into a Pivot Table.  However, in your pivot table, you are showing the short postal code.  If you use the Regular Postcode it looks like the map throws out any Zip + 4 records.   

So if I change the map to "Primary Address Postcode Short" the numbers in the pivot table match the numbers in the pivot table, here in the states.  We clearly have a few zip + 4 showing up in our data.

Here is an updated version of your file.

3362.FOLG-MembershipsbyZip (TGB).dash

See if this works better for you?

--Tom

P.S. Now all I have to do is go back and update my current Maps.  However, I don't think that this is going to fix my problem with too many records.

So my situation with droped postal codes also looks better when using postcode short.

Aha! I didn't even think to see if it was possible to use postcode short in the map after it switched to postcode from postcode short in the switch from pivot to map. That does seem to fix this issue, thank you!