Data and Personalisation Readiness

Eight questions on whether your customer data can support Data 360 and real-time personalisation, scored in your browser.

This Data 360 readiness assessment asks eight questions about whether your customer data can support Data 360 and real-time personalisation. It looks at six areas: sources and ingestion, identity and keys, data quality, consent and governance, real-time events, and use cases and measurement. Your answers stay in your browser. It is most useful before you buy licences or start an implementation.

Before you start: list the systems that hold customer data, such as CRM, ecommerce, the marketing platform and support tools, and invite someone who knows how consent is collected. Many readiness gaps sit between teams rather than inside one system.

Data and personalisation readiness

Eight questions on whether your customer data can support Data 360 and real-time personalisation. Your answers stay in your browser.

01 How many systems hold customer data you would want in one profile?
02 Do your systems share a common customer identifier?
03 How would you describe duplicate and incomplete records?
04 Can you tell, per person and channel, whether you may contact them?
05 Do you capture website or app behaviour as events tied to known people?
06 How quickly must a personalised experience react to a visitor action?
07 Have you written down the first use cases and how you will measure them?
08 Who will own the data model after launch?

How to use the result

You get an overall band (Early stage, Developing or Established) and a score for each area, weakest first, with a link to the related service where a score is low.

  • Identity and quality come before real-time. Data 360 identity resolution uses match and reconciliation rules to build unified profiles, and it can only be as good as the keys and records it is given.
  • Be specific about speed. Salesforce documents a sub-second real-time layer, while standard web and mobile streams load engagement data every 15 minutes and profile data hourly. Decide which use cases truly need the faster path.
  • Fix consent before tracking. The Salesforce Interactions SDK sends events only when a person has consented to tracking, so your consent model shapes what you can personalise.
  • Write down two or three use cases with owners, baselines and a holdout plan before design starts.

Read the real-time personalization guide next, or use the Data 360 readiness checklist for a longer list.

Questions we hear

Do we need Data 360 already to use this?
No. It is designed for teams planning Data 360 or personalisation as well as those already using it.
What does a low events score mean?
Usually that website or app behaviour is not yet captured as events tied to known, consenting people.
Is the score a recommendation to buy?
No. It reflects your answers only. Licensing decisions need a proper look at your use cases.
Which area should we fix first?
Usually identity and consent, because every later use case depends on knowing who a person is and whether you may personalise for them.

Turn your score into a plan

Share your readiness result and we can suggest the first steps for your data and use cases.

Discuss the result →

Tell us what you are trying to fix.

Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.

Talk to a Salesforce Expert
Book a Consultation