The Count setting controls how conversions from an interaction contribute to a conversion action. Every is useful when each additional transaction has value, such as two separate purchases. One is often appropriate for leads when repeated submissions after the same interaction should count as one acquisition.
Count isn't a person-level deduplication system across all campaigns and time. A repeat visitor can create a different interaction, and separate conversion actions still have separate counting rules. Duplicate event delivery also needs its own protection, such as transaction identifiers for purchase events. The browser separates counting from a deduplication switch so you can see those decisions independently. Real collection must be tested in the website or import pipeline.