Brickstream Sensor Connectivity Document

Version 2.1

Revision Date January 24, 2022

Table of Contents

BRICKSTREAM SENSOR CONNECTIVITY DOCUMENT ....................................................................................... 1

OVERVIEW ............................................................................................................................................................. 4
BRICKSTREAM EQUIPMENT MATRIX ......................................................................................................................... 5
Brickstream Traffic Sensors ............................................................................................................................... 6
Local Site Communications ............................................................................................................................... 6
Internet Communications .................................................................................................................................. 7
REQUIREMENTS .................................................................................................................................................... 8
Physical ............................................................................................................................................................. 8
Logical .............................................................................................................................................................. 8
Access controls (Required Traffic Flows) ............................................................................................................ 8
Considerations .................................................................................................................................................. 8
APPENDIX I – FAQ’S ................................................................................................................................................ 9
REVISION CONTROL ...................................................................................................................................... 10

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 1 of 10

INTRODUCTION

This document covers the requirements needed for ShopperTrak’s sensing solution to work when utilizing Brickstream
sensors. Brickstream sensors are a third-party sensor provider that we have adopted into our portfolio as a viable traffic
counting sensor to be used with our turnkey platform. This document provides an outline of the connectivity product, the
services, and the network components necessary to establish a working connection when utilizing Brickstream sensors.
To start things moving, you will need to:
§ Review this document and be familiar with the contents,
§ Fill out the IP Map or Site Survey Form provided by your ShopperTrak Implementation Project manager, to request
a build for your implementation,
§ Provide your network set-up (i.e. Where is Internet provided?, Is DHCP supported?, What and where are you
controlling how ShopperTrak sensors could reach over the Internet?, etc.) prior to any provisioning or deployment
of any ShopperTrak sensors. Additionally, a conversation between ShopperTrak’s Solutions Delivery Team and your
network/security team members should be facilitated to ensure understanding and requirements for ShopperTrak
Sensors to communicate properly.

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 2 of 10

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 3 of 10
SINGLE SITE CONNECTIVITY SOLUTION

OVERVIEW
This document describes ShopperTrak’s adoption of the Brickstream developed communication methods required to allow
for both data acquisition and management of Brickstream manufactured sensors. It contains the communication
requirements needed in order for ShopperTrak to deploy Brickstream sensors within your properties for the purposes of
collecting your shopper traffic information.
ShopperTrak may use different sensor equipment based on the results of the site survey to ensure accuracy. ShopperTrak
has multiple types of perimeter sensing equipment that could be used. Each property is unique and may use different
ShopperTrak qualified equipment depending on what’s best to count the property ShopperTrak is to deploy sensors into as
part of our turnkey solution. To accomplish this, ShopperTrak conducts site surveys to gather a property’s sensor
requirements and configuration.
These services are responsible for providing an organized, redundant way of receiving data from ShopperTrak qualified
sensors, as well as providing a management path for each sensor. Brickstream sensors can receive configuration and flash-
firmware updates through this service. These services communicate with the Brickstream sensors at sites connected
through the use of Transport Layer Security (TLS) (formerly known as Secure shell (SSL) protocol).

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 4 of 10

BRICKSTREAM EQUIPMENT MATRIX
Table 1
The following table shows all ShopperTrak supported Brickstream manufactured equipment along with features and
functions they support.

Device Image / Ethernet Traffic DHCP Proxy Power Realtime

Model Outdoor
Configuration Attached Sensor Client Support Source Support

PoE
2500
Yes Yes Yes Yes Yes Injector Yes
Series
/ Switch

Configured prior to
shipment

PoE
2300
Yes No Yes Yes Yes Injector Yes
Series
/ Switch
Configured prior to
shipment

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 5 of 10

Brickstream EQUIPMENT FUNCTION
A ShopperTrak traffic system using Brickstream sensors consists of the following functions, in some cases, a sensor can be
multifunctional. (see Diagram 1 - A simple representation of possible physical configurations for a property)

Diagram 1 – ShopperTrak Site Equipment Connectivity

Brickstream Traffic Sensors

Brickstream overhead sensors are responsible for counting people passing through foot traffic entrances and exits.
There are many possible Brickstream supported hardware configurations that could be used to count a property.
ShopperTrak works with customers to determine the optimal number of sensors based on property. Each installed
sensor requires an IP address on the customer LAN network.
Model’s: 2310 and 2510 (including sub models) – 2200 or 2100 (legacy models) support currently NOT available
VENDOR MAC’s: 00:B0:9D:xx:xx:xx

Local Site Communications

A ShopperTrak installed Brickstream sensor system deployed at a site will consist of one to many sensors depending on the
counting needs and site survey’s that are conducted prior. Each sensor will require IP addressing, typically gathered from a
clients DHCP server. The Brickstream sensor system deployed at a site act independent of one another. Also note, that in
some cases ShopperTrak will utilize our installers to perform configurations of the equipment locally on-site.

Diagram 2 – Brickstream Local LAN

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 6 of 10

 Internet Communications
A ShopperTrak Brickstream sensor system deployed at a site will consist of one to many sensors depending on the counting
needs and site survey’s that are conducted prior. This system functions like most IoT sensor solutions requiring IP
addressing and Internet access to properly function. The following is a simple diagram showing the traffic flows between a
ShopperTrak Brickstream sensor system deployed at a site and ShopperTrak. It should be noted that the Customer Network
may or may not be part of this path. This is typically identified during a connectivity call held between your IT Team and
ShopperTrak’s Solutions Delivery team.

Diagram 3 – Internet traffic flows

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 7 of 10

REQUIREMENTS
The following identifies what is needed for proper functionality of the SSC service:

Physical
§ Ethernet port
§ PoE (IEEE 802.3af) Ethernet port per installed Brickstream sensor(see Table 1) – If PoE is required and
isn’t available ShopperTrak can provide either an unmanaged PoE switch or PoE injector
§ Identification of specific equipment and port ShopperTrak should be terminated into (i.e. Switch,
Router, Firewall, ISP provided equipment, specific nomenclature, ports, etc.)
§ Power receptacle
§ Should provide 24/7 power
§ ShopperTrak provides the required global power adaptors per the install location

Logical
§ IP addressing
§ Dynamic (DHCP) – PREFERRED
§ Static
§ A single IP address for each Brickstream sensor (no matter how many Brickstream sensors are
installed)
§ Default Gateway for provided IP address
§ Subnet Mask for provided IP address
§ Primary DNS IP address
§ IF Normal/Direct Proxy request is required – NOTE: Not required with Transparent Proxy PREFERRED
§ Proxy IP/Proxy DNS Name
§ Proxy Port
§ Username/password if proxy authentication is required
§ ShopperTrak DOES NOT support auto-proxy configuration scripts (i.e. PAC or WPAD)

Access controls (Required Traffic Flows)

Destination
Description Protocol Service Destination Name(s) IP(s)
Port
ssflrdm.shoppertrak.com
3.129.198.57
DNS Whitelisting (if used) flrdm.strct.com
Name Resolution types dataacquisition.shoppertrak.com 35.224.187.189
* Service Record (SRV), da.strct.com 35.196.131.209
*CNAME, & A Record
de3p.shoppertrak.com 34.73.177.103

Transport TCP HTTP / HTTPS 2374 - 2377

NTP and HTTP, HTTPS, 2010, 2012, 5052, 5053, See Above Destination Name(s) See Above IP(s)
TCP
Data Delivery & TCPTime 5054, 5055, & 443

o ShopperTrak STRONGLY SUGGESTS use of *.shoppertrak.com, *.strct.com & *.footfall.com for your Destination Name controls
l Destination used for Realtime Traffic

SPECIAL NOTE: If your access controls perform reverse DNS (rDNS) as part of the validation/verification/approval process please note that the returned CNAME may
not match the forward DNS lookup for the above Destination Name(s) due to respective data center instances and cloud based redundancy,

Considerations
Site Internet access varies greatly, from a direct connection through a cable modem or DSL/ADSL circuit, to a complex
corporate network infrastructure. With any Internet connectivity there are devices, both logical and physical, that can
control, prohibit, police, or allow communication. In addition, other factors can inhibit Internet access including, but not
limited to, corporate network and security, governmental regulations, and/or Internet service provider controls,
Manipulations to such equipment may be required to allow proper communication flow. Examples of such equipment
include: Proxy servers, OpenDNS, DNS blacklisting, Websense, SecureLink, Access Control Lists, Intrusion Prevention, and
Firewall Policies.

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 8 of 10

APPENDIX I – FAQ’s

What is a Brickstream device?

§ A Brickstream is a highly accurate traffic counter. It is not affected by heated environments or height filtering (the
device will not count children or trollies/buggies, etc.)

Are there any security benefits?

§ Uses TLS/SSLv3, an Internet industry accepted standard for secure communications

§ All connections source from within the store
§ No inbound connections to store equipment
§ All devices will be upgraded to the latest software code available

What operating system is on the device?

§ The Brickstream runs Linux

Is this connectivity type PCI compliant?

§ This connectivity solution only processes traffic counts, it does not collect any credit card or PII information

What type of IP addressing is supported?

§ Either static/fixed or dynamic (DHCP) addressing is supported. It is strongly suggested to use of DHCP
§ Addressing provided should be LAN addressing, generally uses private addressing

What are my in-store physical requirements?

§ An open, available Ethernet port with the proper access controls ideally on a non-PCI segment
§ 24/7 power source
§ Cat5e/Cat6 cabling (this installed as part of our standard installation)

Where is the equipment placed in my store?

§ Brickstream counters are mounted in or on the ceiling near the store entrances

How much data can be stored locally on the device?

§ The Brickstream can hold up to 80 days of traffic counts

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 9 of 10

REVISION CONTROL
Modification Modified By Description Date Update Information
History
Document Creation Mike Tamsevicius Revision 1.0 October 20, 2020 Initial Document
Access Control Update (TCP 2375, 2010,
Document Revision Mike Tamsevicius Revision 1.0 October 23, 2020
2012)
Document Revision Mike Tamsevicius Revision 1.1 December 2, 2020 Change of protocol 1012 to 2012
Document Revision David Schmidt Revision 1.2 January 27, 2020 Revised Access Control table & Diagram 3
Revised Access Control Table, Diagram 2, &
Document Revision David Schmidt Revision 2.0 January 7, 2022
Diagram 3
Document Revision David Schmidt Revision 2.1 January 24, 2022 Revised Access Control Table & Diagram 3

ShopperTrak, Inc. ShopperTrak Sensor Connectivity Document Version 2.1 Page 10 of 10