Replaces your account's known-merchants list used by Merchant Intelligence for merchant-name standardisation and location matching. Review what's currently stored with Export Known Merchants.
Uploads replace, not mergeEach upload replaces your entire stored known-merchants list — merchants missing from the file are removed. Always upload the complete list.
A minimal sample CSV or TSV — merchantName is the only required column; add address fields or coordinates for location matching, and locationId to have your own store ID returned on a match:
merchantName,merchantAddress,merchantCity,merchantState,merchantPostalCode,merchantCountryCode,merchantCoordinates.x,merchantCoordinates.y,locationId
Fresh Market,1 Market Street,Auckland,,1010,NZ,174.7633,-36.8485,store-001
Large imports can be slowWhen a row has no
merchantCoordinates, Taggun calculates them from its address during import; this can take a long time for large lists. Supplying ArcGIS-compatible coordinates (x= longitude,y= latitude) keeps large imports fast — see Merchant Intelligence.
AvailabilityAvailable on Startup plans and above. Access is account-configured; if this operation is unavailable, contact [email protected]. See Plans & Feature Access.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
413Request body exceeds the 20 MiB (20,971,520-byte) HTTP body limit. See Document Types & File Requirements.