Skip to the main content.
Skip to the main content.
recipe-card-tab-label-tag-yellow

De-dupe Your Database

Makes: Clean, accurate audience data you can trust 

 

Prep time: 5 mins | Cooking time: 1-2 hours over multiple weeks | Maintenance time: 30 mins / week

indigo-spektrix-collaboration-logo-01

This recipe card was created in collaboration with Indigo-Ltd 

dedupe-your-database-recipe-card-hands-typing-keyboard-800w-1200h

 

The Tomorrow’s Audience research by Indigo-Ltd in partnership with Spektrix shows that an average of 54% of audiences in 2023 were new, and that new audiences look for different types of communication.

This store cupboard recipe will remove duplicates from your database to help give you an accurate account of your own audience and ensure customers flagged as first-time bookers are actually first timers.

 

READ THE TOMORROW'S AUDIENCE REPORT

Outcomes 

  • Be able to benchmark your data against the Tomorrow’s Audience data
  • Know you’re sending targeted communications to the right people
  • Avoid spamming people so that they disengage from your communications

 

Ingredients

 
‘Potential duplicate’ metric: a calculated metric that sits against customer records in Spektrix
 
Autotags: ways of labelling your customer records automatically based on specific criteria, e.g. potential duplicate = true
 
Normal tag: a label you can manually add to a customer record
 
Customer groups: a way of highlighting certain customer records in the sales interface based on specific criteria, e.g. tags applied

 Prep

 

  1. Create a normal tag named ‘Not a duplicate’. You will use this to mark any records that have been flagged as a potential duplicate, but that have been verified as not a duplicate.
  2. Use an autotag to apply a tag to all customer records that meet the criteria of ‘potential duplicate = true’ and do not have the ‘not a duplicate’ tag
  3. Set up a customer group with the ‘potential duplicate’ autotag as its criteria. This will add a coloured box in the sales interface to any customer records with this tag, making them easy to spot for your sales team
  4. Apply the ‘not a duplicate’ normal tag when you verify a customer is, in fact, not a duplicate. This will turn off the ‘potential duplicate’ autotag on that record, and subsequently automatically remove the coloured box on the record.

 

 

pot-with-veggies-tickets-arts-dance-music

 

Cook

 

  1. Run an advanced search in the sales interface for customers with the ‘potential duplicate’ autotag
  2. Click into corresponding customer records to assess if they are, in fact, duplicates
    • If they are duplicates, merge the records
    • Otherwise, apply the ‘not a duplicate’ tag to their records
  3. Work through these records in your database regularly. Use the coloured customer group box to verify duplicates with customers during their purchase.

Keep it up

To maintain a healthy database, set up a weekly task to check for any new records. 

Bon appétit!

Learn more about finding potential duplicates for clean CRM data on our Support Centre. Plus, keep exploring our recipe box to fill your store cupboard with more ideas and insights on how to reach tomorrow's audiences. 

 

TRY MORE RECIPES