Following are some of the terms that are most commonly used in the application, as well as their respective description.
A
C
D
E
F
G
I
An injection rule is used to collect information linked to an email or the recipient who clicks a link in that email. Afterwards, this information is added to the end of the clicked URL in the form of parameters. These parameters, often used to measure the performance of a campaign, transfer data or an external system, such as Google Analytics. The parameters are applied only if click statistics are enabled.
Injection Rules in DI
Several injection rules are configured by default in Dialog Insight depending on the activated modules:
You could also create a custom injection rule in which you specify the destination URL and the parameters to inject.
Example With Google Analytics
Here is an example of the mechanism of a parameter of the default Google Analytics rule:
- The parameter automatically associates "utm_medium" to the value "Email" when the link includes "dialoginsight.com".
- The link http://www.dialoginsight.com/fr/solutions will be automatically replaced by http://www.dialoginsight.com/fr/solutions?utm_medium=Email.
- The website for which statistics are used, Google Analytics, will receive this parameter to identify the source of the visitor. In this example, the source is an email message. You will then be able to evaluate the performance of your communications.
The Google Analytics rule is configured to apply to all links, regardless of their destination. However, if special restrictions need to apply to parameters to inject on some destination sites, you can configure the rule to restrict destination sites.
K
L
M
P
Each project has a primary key that is composed of only one or multiple fields which is/are used to identify each contact. This key prevents the existence of duplicate contacts in your database and ensures that a contact does not receive the same message twice. The email address is most commonly used as the primary key, but you can choose any other field, such as a client number, or a combination of fields. Some other fields might be set to be mandatory, so that when a new contact is created, both primary key and mandatory fields must be filled.
In Dialog Insight, a project is your database, where you find all your contact information, the structure your database, and various parameters that apply to the entire project. In a project, all the information about contacts is presented into fields.
Also, depending on your account's configuration, enabled modules and granted permissions, a project can be associated to messages, campaigns, Web sites and various statistical and configuration options.
When a user logs into Dialog Insight, he must necessarily open a project, and if none exist, start by creating one.
Each project can only have one contact list. However, it is possible to create, for one project, multiple groups (for targeting) from the contact list.
In most cases, you'll have a main project, for all your contacts, and maybe a few others, smaller, to manage contacts for other purposes, such as contests or events. You could have multiple projects, for collecting different contact information. For example, you could have a project for employees, and another for your newsletter subscribers, as the information to collect is different.