Entities and entity relationships

Client

A client in the system represents one of our real-life clients. A client must have a DV360 account with at least one active line item to set up signal campaigns. Clients can run multiple campaigns through business units.

Business units

Business units are groups that always belong to a client. Therefore, you need to create and associate at least one business unit with the client to manage client campaigns.

Users

User entities exist individually in the system. However, to manage campaigns and recipes, a user must be associated with the client.

Signals

Signals are different event sources that we can use to modify the campaign settings runtime. At the moment, we have three signals built and integrated into the system: Google trends, Wheather, and Travel restrictions.

Signal configurations

Based on signals, you can create signal configurations. You can think about these as refined descriptions.

Example: weather configuration.

You can create a weather configuration by specifying the geo-location and the forecast period on that specific location. For example, when you set the period to 3, all future recipes based on the signal will behave based on the weather forecast from three days to the current date.

Recipes

A recipe is a conditional statement that describes what should happen with a line item when a specific condition meets. Each recipe must refer to a signal source.

Campaigns

Campaigns and recipes can be connected to the client through business units. Since the line item connection is happening on the client level, seamless campaigns have access to the line item through the client-business unit relationship.