Customers

A customer is Siren’s record of one shopper. It gathers the ways your stores know that person, such as a store account and a guest checkout, which Siren calls identities. It also holds their visits, the sales credited from those visits, and any collaborators they’re linked to for life. Every edition keeps customers.

Siren > Customers lists them. The screen is in the Siren menu once an integration that records customers is active, or once customers exist. Administrators and Platform Managers can open it.

On Siren Cloud, the screen is Track > Customers. A WordPress site connected to Siren Cloud sends its customers there and has no Customers screen of its own.

When Siren keeps a customer

Siren keeps a customer only for a shopper who touches its data:

• A sale that names the shopper. WooCommerce, Easy Digital Downloads, LifterLMS, and LearnDash purchases add the buyer, whether they check out as a guest or with an account.
• A sign-in or a new account after a referral. A shopper who arrived through a collaborator and then signs in or registers becomes a customer. A sign-in without a referral doesn’t add anyone new.
• A lifetime link. Linking a shopper to a collaborator keeps them as a customer.

NorthCommerce, Gravity Forms, and Ninja Forms don’t record customers. Siren never stores a customer’s email address. It keeps a keyed hash of it, which lets it spot the same email again without keeping the address.

On Siren Cloud, a Stripe or Shopify order that Siren records adds its shopper, under the store’s customer ID.

Read the list

Each row is one customer:

• Customer is the newest name a store reported, or “Customer #” and a number when no store named them. A “Possible match” badge means Siren thinks another customer is the same person.
• Identities lists how each store knows them.
• Linked collaborator names the collaborators linked to them, or “Not linked”.
• Last seen is when Siren last saw them.

Search by customer number, a store’s ID for the customer, or an exact email. The integration menu narrows the list to one source, such as WordPress accounts or WooCommerce, and the link menu to customers who are “Linked” or “Not linked”. Tick “Has a possible match” to see customers with a suggested match. On Siren Cloud, the store menu narrows it to one Property.

When no active integration records customers, a banner says so. Customers kept from before stay listed, and their links still credit collaborators.

A customer’s page

Click a customer to open their page:

• Identities shows each way a store knows them, such as “WooCommerce guest” or “WordPress account #12”, with the name and when Siren last saw it. An account the store deleted shows “Deleted at the store”.
• Linked collaborators lists the collaborators who earn from their later purchases. Linking needs Siren Plus or Pro, as Lifetime Commissions describes.
• Possible matches lists customers Siren thinks are the same person.
• Sales lists up to 50 sales credited from this customer’s visits.

The “Activity” button shows the customer’s links, unlinks, merges, and splits.

Merge and split

Siren never merges customers on its own. When two customers at one store share an email, such as a guest checkout and an account, Siren suggests them as a possible match. The “Possible matches” section at the top of the list, and the card on a customer’s page, offer “Merge” and “Not the same”. “Not the same” stops Siren suggesting that pair again.

To merge customers Siren didn’t suggest, choose “Merge with…” on a row or on the customer’s page and find the other customer by number, store ID, or exact email. Or tick two or more rows and click “Merge”. You can merge up to 20 at a time. Choose the customer to keep, and everything moves to it: identities, visits, and sales. Each visit stays its own. When the customers are linked to different collaborators, the dialog asks “Which collaborators stay linked?”, and at least one must stay. A merge only keeps links. It never adds a collaborator who wasn’t linked already. Opening a merged customer’s page takes you to the one you kept.

To undo a merge, open the customer and click “Split off” on an identity. A split doesn’t bring back links the merge dropped. The button shows when the customer has more than one identity. The identity becomes a new customer, with the visits and sales that came through it and no collaborator linked.

On Siren Cloud, Siren matches customers within each store to start with, and refuses to merge customers at different Properties. If your stores are one business, an Admin can click “My stores are one business” on the Customers screen and confirm. Siren then suggests matches by email across your stores, and you can merge them. Confirm only when your stores’ privacy notices say customer records may be linked across them.

Check customer records

On WordPress, Siren’s “Utilities” tab, beside Import, Export, and Logs, has a “Customer records” check. It compares your lifetime links and customer accounts with Siren’s customer records, and warns when any are missing a match. Its rows are “Lifetime links”, “Customer store ids”, “Upgrade import”, and “Opportunities to check”, which lists up to 20 visits to look at.

When a customer asks for their data

WordPress’s Export Personal Data and Erase Personal Data tools cover Siren’s records. Erasing a customer unlinks them from every collaborator, who then won’t earn from their future purchases. Answer a Customer’s Data Request explains what each tool covers.