Why use a match key?

Optional add-on for buyers who run more than one order and need device key consistency across outputs (traffic.csv).

The problem

Each order’s traffic.csv includes an anonymized device id (device_id_masked). By default that mask is unique to that order. The same mobile device in two different orders looks like two different ids — so you cannot join traffic.csv files to spot repeat visiting devices across areas or date ranges.

What the match key does

When you enable the add-on and supply a key (generate one or paste your own), masks are derived using your key. Use the same key on later orders and the same devices keep the same device_id_masked across traffic.csv files — ready to join in Excel, Python, or your BI tool.

What it is not

Not a login or account — VisitsInPoly stays anonymous; you hold the key.
Not a raw advertising id (MAID) — you still only get a masked value.
Not a one-time purchase — the small add-on is charged on each order where you enable it.

When it is worth it

Buy once for a single listing check? You can skip it. Planning several areas or date windows and want to compare overlap or returning visiting devices? Turn it on, save the key, and reuse it.

← Back to order