The customer is always one. Every system around them needs the same context.
SocialScore improves every data layer and gives each system the context it needs: the merchant, logistics, the payment provider, the chat agent, support, omnichannel and personalization.
What customer data a business has today, and who supplies it.
Data sources, grouped by when they start working. The third column says what each one needs from the customer before it knows anything.
| Data type | Supplied by | Needs from the customer | SocialScore |
|---|---|---|---|
| Works before the customer paysFrom a visit, or from an email or phone number | |||
| Web and app behavior | Analytics, pixels, CDPs | A visit | Pixel |
| Device and fraud intelligence | Fraud vendors | A visit | In the Pixel |
| Third-party and ad-platform audiences | Brokers, Meta, Google | Nothing: the platform holds it | Ready segments |
| Contact validation | Verification vendors | An email or phone | Included |
| External digital data | SocialScore | An email or phone | Core |
| Works once the customer shares moreA sign-up, answers, consent or a legal basis | |||
| First-party data | Shop, CRM, ERP | A sign-up or an order | We process |
| Zero-party data | Forms, quizzes | Their answers | We process |
| Open banking data | Open banking providers | Their consent | Via partner |
| Works at paymentOnce a card payment has happened | |||
| Payment and transaction data | PSPs, card networks | A card payment | We combine |
One customer, step by step: what you know at each moment.
Four journeys. Each lane shows what a layer knows at that step, and the last lane shows what the layers achieve together. Dashed means there is nothing to act on yet. Tap ? for the detail.
See the whole customer, not just the order.
Your store knows a name, an address and a phone. SocialScore adds who that person is, from one email or phone in under 5 seconds.
Pablo Dias
- pablo.d***@gmail.com
- +359 88* *** *41
- Sofia 1000, Bulgaria
- 3 orders, €214 total, cash on delivery
Not available for this customer: they paid cash on delivery. For card payments it arrives at the final step, usually when the customer is already leaving, not while you can still sell more through a custom layout and checkout.
Illustrative profile built from a real API response. Personal data is masked by role in the platform.
-
A plain-language picture of every customer, plus the signals that matter for selling: real person or bot, digital presence, contact quality and likely spend.
Personal summaryHuman / agent / botDigital presenceSpend signalsSource & confidence -
Occupation, industry, company size and education where public, to set the right tone, offer and price point.
OccupationIndustryCompany sizeEducation -
Where the customer lives online: platforms registered by email and phone, preferred chat channels, and depth of presence against your country.
SocialShopping & travelMessaging appsLocal platformsCountry benchmark -
30+ interest categories, each compared with the average customer in your country, so you know what to offer before they tell you.
TravelFashionE-commerceSportsTechvs country average -
What the SocialScore Pixel sees: traffic class, source and campaign, viewed products and carts, joined to the person the moment they identify.
Traffic classUTM & campaignViewed productsCartsReturning visits -
Valid or disposable contacts, exposure records and bot signals, so risky cash-on-delivery orders get reviewed before they ship, plus the segments the customer matches.
Email & phone healthExposure recordsBot signalsCOD reviewSegment match -
The verified spend, when there is one. It arrives at the final step, often as the customer is leaving, and not at all for payments outside the card schemes, such as cash on delivery, wallets or crypto.
Arrives lastCard payments onlyPartner data
One customer, and every system around them gets the same context.
Used before the payment and after it, at profile level, wherever a model or a person has to decide what to show, say or flag.
What each layer does best, and what the others add to it.
Transaction and behavioral data are the best-known layers. Each is strongest at something different, and each gets stronger when it is joined to the others.
Transaction data
- Verified spend, the ground truth
- What, where and how often
- Long histories at scale
- A profile before the first payment
- The who and why behind the spend
- Context for payments outside the card schemes
Behavioral data
- What visitors do on your site
- Intent in the moment
- From the first visit
- A person attached to the session
- Interests beyond your own site
- Verified spend as the outcome
SocialScore external data
- Real time from the first identifier
- Very broad, with local data per country
- The whole person, not one payment
- Joins with every other layer
- Verified spend as ground truth for the segments
- On-site behavior from the Pixel
- Your own customer data
A high-spender solution your merchants will want.
Transactions confirm who spends. SocialScore knows who they are before they pay. Stacked, merchants find high spenders earlier and understand them better.