I was trying to look at members by (short) postcode, and I built a pivot table that shows that information (Count of Constituent IDs in values, Primary Address Postcode Short in rows, with a widget filter limiting to six Primary Address Postcode Short selections and dashboard filters limiting to several Membership Levels and Current Status in active or pending). I then copied the pivot table and changed the widget type to a scatter map. But the scatter map shows a smaller number of memberships in each postcode than the pivot table shows, and the scatter map does not seem to respect the Primary Address Postcode Short filter that I have on the widget limiting it to only 6 postcodes. Is there a way to filter the scatter map ? And why is it showing different counts for each zipcode? Is it because it's not including 9-digit zip codes? (So 20002-1234 isn't getting included in 20002, for example?) Thanks!
Leslie Gehring
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!