Skip to content
Documentation
DropUI homepage
Topics

DropUI glossary

Not sure whether a setting belongs to the store, campaign or contact list? These terms describe different parts of working in DropUI. Each group includes an example and a link to the relevant guide.

Store and connection

Store is where you associate addresses, campaigns and available purchase data. One account can distinguish DEMO STORE from its outlet, for example.

Store address is a specific website address, such as https://store.example. A www version or another subdomain may be a separate address. Choose where each campaign appears. Check addresses and domains.

Installation means running the DropUI script on your website so it can show campaigns. Check its status at the address customers use.

Data integration connects DropUI to a store platform to provide supported data, such as products and orders. A working popup does not confirm this connection. Compare installation and data access.

People, groups and consent

Contact is a person's profile, for example with email, phone number and activity history. A later signup can update an existing contact.

Contact list defines the context in which you collect and manage contacts. One person can belong to more than one list.

Segment is a selected group of contacts, such as people matching purchase criteria. It helps choose recipients; it does not replace consent.

Consent applies to a particular channel and context. An email recorded with an order is not, by itself, marketing consent. Compare contacts, lists, segments and consent.

Sender is the configuration used to send messages in a channel, such as an email sender name and address. Having a contact list does not mean sending is ready.

From design to a working campaign

Campaign is a specific communication activity: a signup popup, announcement bar or message to recipients.

Template is a starting point for a design. Adjust its copy and appearance to match your store's offer.

Preview lets you check a design before launch. Submitting a form in preview does not create a real contact.

Publication makes a prepared campaign version available. For an on-site campaign, also check selected addresses and display conditions. Saving design changes alone is not enough. Check saving and publication.

Display conditions determine when and to whom a campaign appears, such as after a set time on a page. Follow a campaign through to a store test.

Automations and purchase data

Automation runs a planned sequence of actions when configured conditions are met. It needs the relevant data and channel configuration.

Scenario describes an automation's use, such as reminding customers about unfinished purchases. Not every scenario fits every store and channel.

Event is a recorded action, such as a form signup or cart status change. An automation can use it to trigger an action.

Cart describes products and activity before a purchase. An order is a separate purchase record. Cart abandonment and order status answer different questions. Check carts or orders.

Reading the numbers

A view records a campaign appearing; a click records an interaction. These are not interchangeable counts of people or signups.

CTR is the percentage of views that led to a click. Compare it using the same period and bot traffic setting.

Contact source helps identify where data came from, such as a form or store. It does not confirm consent. Check sources and contact history.

Attributed revenue is an amount associated with an activity under the report's attribution rules. It is not profit or proof that the purchase would not have happened without the campaign.

To find a particular screen, use the dashboard map.

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.