User guide

Several shops

With PrestaShop’s multistore, every shop has its own visits, its own order sources and its own settings. The shop selector at the top of the back office decides which shop you are looking at.

Visits, orders and the dashboard

A visit belongs to the shop it happened in, and an order source to the shop of the order.
The Dashboard, the Orders tab and the Visits tab show the shop chosen in the shop selector. Choose a group of shops, or all shops, to see them together.
The Source column and the Order source card are part of PrestaShop’s own pages and follow them.
Revenue is shown in the default currency, whatever currency each shop sells in.

Settings

A section of the settings is saved for the shop chosen in the shop selector. So one shop can record visits with Script only because it sits behind a cache, and another can wait for consent because it sells in another country.

Three things belong to the whole installation, not to one shop, and their help texts say so: Keep data when uninstalling, the Maintenance address, and Hide these steps on the Overview.

The domains of all your shops are always excluded as sources, in every shop: a customer who moves from one of your shops to another does not make the first shop a source (Excluded sites: pages a customer only comes back from).

Shops on one domain share their visitors

How separate two shops are depends on their addresses. A browser sends the cookies of a domain to every address below it; that is how cookies work, and no module can change it.

Each shop on its own domain

www.shop-one.example
www.shop-two.example
or fr.shop.example and de.shop.example

Fully separate. A visitor of one shop is a new visitor in the other.

A shop in a folder of another shop

www.shop.example
www.shop.example/outlet/

A visitor who goes from the main shop to the folder shop within 30 minutes continues the same visit there. An order in the folder shop gets the source the visitor arrived with. In the other direction a new visit starts.

Two ways to give several shops their addresses, and what each means for the visits.

Visits from version 1

Version 1 did not store the shop of a visit. After an upgrade, old visits that led to an order are in the shop of that order. Old visits that led to no order are all in the default shop (Coming from version 1).

Privacy

The module stores as little as it can, and everything it stores stays in your shop’s own database. This chapter lists what is stored, gives you the two cookies for your cookie policy, and shows how a customer’s data is exported or erased.

What is stored, and what is not

Stored for each visit

A random number that stands for the browser
The shop, the date and the time
Source, medium and campaign, and the term and content of the link when it had them
The kind of ad click, when there was one
The page the visitor landed on, without the part after the question mark
The domain of the site the visitor came from
The order the visit led to, and whether it was a test visit

Never stored

The IP address
The browser and the device
The pages the visitor looked at
The part of an address after the question mark, which can hold an e-mail address or a token
The code of an ad click
A name or an e-mail address: a visit knows a customer only through the cart and the order it led to

What one line of the Visits tab holds, and what the module leaves out on purpose.

Nothing leaves your shop. The module sends no data to PrestaChamps or to any other company. Its script in your shop reports only to your shop, and the scripts and styles it adds to the back office come from your shop too.
One short-lived exception, stated openly. To stop a flood of fake visits, the module counts new visits per address and minute. For that it keeps a scrambled fingerprint of the address (a salted hash), not the address itself. The daily housekeeping deletes these fingerprints, so one is kept for two days at most, as long as the housekeeping runs every day (Data and upkeep: how long visits are kept).
Test addresses. The IP addresses you enter under Test IP addresses are a setting of yours. A visit from one of them is marked as a test; the address is not stored with the visit.

The two cookies, for your cookie policy

The module sets two cookies in the visitor’s browser. Both are first-party cookies of your own shop. You can copy this table into your cookie policy.

Cookie	Purpose	Lifetime	Content
`pch_os_v`	Recognises the browser when it comes back, so that an order can be linked to the visits before it.	The attribution window: 30 days unless you changed it. Renewed at each new visit.	A random number. Scripts on the page cannot read it.
`pch_os_s`	Marks the visit that is running, so that it is counted once.	30 minutes after the last page view.	The time the visit was last seen and a short note of its campaign.

Neither cookie is shared with another site, and neither holds a name, an e-mail address or anything the visitor typed. Whether they need the visitor’s consent depends on the law where you sell:

With When recording starts set to Immediately, both cookies are set on the first page.
With After the visitor accepts cookies, no cookie is set and nothing is stored until your banner reports consent. When the visitor withdraws consent, both cookies are removed (Consent: when recording may start).

How long data is kept

Data	Kept for
Visits	The time in Keep visits for: 396 days, about 13 months, unless you changed it. Older visits are deleted every day (Data and upkeep: how long visits are kept).
The first and last touch of an order	As long as the order exists.
The fingerprint of an address	Until the next daily housekeeping: two days at most, as long as the housekeeping runs every day.
After an uninstall	Nothing: uninstalling the module deletes all visits, order sources and settings, unless Keep data when uninstalling is on.

Export and erase a customer’s data

The module works with PrestaShop’s official GDPR module. You need nothing else, and you set up nothing: when that module is installed, its two tools include the data of Order Source Pro.

Export. The export of a customer’s personal data contains the sources of their orders and their visits.
Erase. Erasing a customer deletes the visits of every browser that was linked to one of their carts. The source written on an order stays with the order; it holds nothing about the person.

Withdrawing consent in the cookie banner is not the same as an erase request: it stops the recording and removes the cookies, and the visits already stored stay until they are erased or grow too old.

↑