Managing contact data accurately is key to effective email marketing. In Delivra, handling duplicate email addresses is built into your account settings by default. This ensures a clean contact database and helps prevent unintended sends or reporting errors.

Default Behavior: Email Address as the Unique Identifier

By default, each Delivra account uses the email address as the unique key. This means:

• Only one contact record will be created per unique email address.
• Any attempts to import the same email address again will not create a duplicate record, but instead update or ignore the existing one, depending on your settings.

How Imports Handle Duplicates

When importing contacts via CSV, you’ll see a setting labeled "Update existing contact records". This option controls how duplicate email addresses are treated during the import:

1. Update Existing Contact Records (Box Checked)

• The system checks if the email already exists.
• If it does, Delivra will compare field data and update the existing contact with any new or changed information.
• No new contact is created.

2. Do Not Update (Box Unchecked)

• The system still checks if the email already exists.
• If it does, that row in your import file is skipped.
• Only brand-new email addresses will be added as new contacts.

Notes on Advanced Duplicate Handling

• Custom Tables Support Multiple Records per Email Address: If your use case requires storing multiple records that share the same email address (e.g., managing different campaigns, orders, or form submissions), this can be achieved using Delivra’s Custom Tables feature.

  • Availability of Custom Tables depends on your license plan.
  • Contact your Client Success Manager for details and access.

• Campaigns and Automation with Unique ID Logic: For advanced automation workflows, Delivra allows the use of a unique ID (other than the email address) to differentiate records.

  • This enables multiple automation passes or multiple sends to the same email address.
  • This setup requires the use of Custom Tables.

Best Practices and Tips

• Always preview your import settings to ensure duplicates are handled as intended.
• Use custom tables strategically when your business logic requires flexibility beyond the default email-unique setup.
• Coordinate with your Customer Success Manager when planning to store or work with duplicate email addresses—this ensures optimal setup and feature availability.

If you have any questions about handling duplicates or setting up custom tables, reach out to our Support team at support@delivra.com.