Skip to content
Documentation
DropUI homepage
Topics

Where your DropUI contacts come from

The same person can submit a form, place an order and later appear in an import. Before adding them again or changing their details, check their profile's sources and history. This helps distinguish another customer action from another person.

Check sources in the list

Open Contacts -> Contacts. Each row shows associated bases, sources and consent. Search finds people by name, email or phone number.

To narrow the sources, open Filters, choose Source and click Apply filters. Available options depend on the account's data and permissions.

Contact filters include source, email consent, group, segment and identity. Purchase conditions depend on the available store history.
SourceWhat to check
FormsThe campaign, submitted details and separately recorded consent
StoreLinks to the customer, purchases or carts in the correct store
ImportThe completed import and the data that was approved
Added manuallyDetails saved by someone working on the account

Source describes where the data came from, not consent status. A form contact without appropriate consent or a customer with an order does not automatically become a marketing recipient.

Open the person's history

Open the contact, then expand Contact history. Check the date, event and source. Activity type filters the history to forms, orders and carts, or other available activity.

Anna Demo's history combines manual entry, a form, a purchase and two separate email decisions. All events are local demo data.

The example order DEMO-1042 and form belong to the same person. Submission and event counts are not counts of new contacts. One interaction can also create different kinds of history entries, such as a contact signup and the form submission itself.

If a form did not supply identifying details, its submission may have no matching contact profile. Check Submissions without a contact profile when that section appears in the contact list.

Check the store match

Expand Purchases and carts in the profile. Store connections shows the store, customer ID and matching method.

Anna Demo is linked to customer DEMO-C1042 in DEMO STORE by email address. This is a sample match using local store data.

Purchase data requires an appropriate integration; the website script alone does not fetch order history. Check the scope of store data or find a specific order.

If a review warning appears, compare the email and phone with the source data. Do not assume that records with overlapping or conflicting identifiers describe the same person. When asking for help, include the store, order number or form name and explain the difference.

Have questions after reading this guide?

Get in touch. We’ll answer your questions and help you with setup, free of charge.

Patryk Surmacz

I’ll walk you through the settings, step by step.