Web Services Documentation

Introduction

ACTITO is a marketing automation tool.

It is built on top of a generic model, and therefore allows its users to adapt the conceptual structures to their specific business.

Entity

Entities allow data to be compartmented within a license.

For example: the B2C and B2B departments may use the same license, but not use the same data, processes, workflows...

The entity being worked with should always by specified: Consequently, if data is available for all users and not tied to a specific entity, the dash sign '-' must be used.

An entity list can be reached via the "ENTITY" web service.

Profile

The ‘Profile’ table in ACTITO allows to manage data tables to which it will be possible to communicate.

For example, a ‘Profile’ is a customer, a potential customer, a partner …, which would have received a communication via ‘interaction’ channels available in ACTITO (e-mail, SMS, paper campaign…)

These Profiles tables could be structured thanks to 3 types of data:

• attributes (representing client data or customer sheet)
• subscriptions (representing opt-ins)
• segments (for example: 'Gold'/'Silver'/'Bronze', or part of a listing)

An attribute may be a reference (business key) to a 'business' object (see section V). When reading the data, the entire business object is returned.

A license may contain several profile databases, whose structures may or may not be similar. For example, the B2B and B2C databases may be different.

The profile database list, their structure and the manipulation of profiles are available via the "PROFILE" web service.

Information related to a mass import in these tables is available in ‘IMPORT’ Webservice.

Interactions

Interactions represent the history of contacts with a profile.

There are two major sources of interaction:

• ACTITO "built-in" interaction
• • tied to communication (email, SMS sending...)
  • tied to automation (execution of a scenario...)
  • tied to client interaction (unsubscription, goal...)
  • tied to web forms More information in section IV
• Specific business interactions of ‘ACTITO Customer’ (Orders, PhoneCalls, testDrives, abandoned basket...) These can be stored in specific tables called ‘customtable’

The history for a profile (its entire interaction list) is available via the "PROFILE" web service.

The business interactions can be handled via the ‘CUSTOMTABLE’ web service.

Forms

‘Form’ allows to create a form and to make it available (e.g. online subscribing to an event, requesting a brochure or a test drive, participating to a contest...).

A form is made of a series of questions and may be linked to a profile database, but this is not mandatory.

If the form is linked to a database, a person may either :

• reply as many times as he wishes (multi participation)
• reply only once and choose to modify his answer afterwards (single participation)
• Only reply once without any possibility to update his answer (unique participation)

In that event, it is also possible to enrich a profile data (only ‘attributes’) with all or only a part of data collected in the form.

The list of forms, their structure and participation manipulation are available via the "FORM" web service.

CustomTable

‘CustomTable’ allows to model the specific business activity of an ACTITO Customer.

In a license, there could be several specific tables of different nature and structure (for example: an offer, an order, a meeting request…).

Each of these tables could be composed of attributes allowing to store information needed for the table purpose.

The table list and the manipulation of data (‘record’) is available under ‘CUSTOMTABLE’ webservice.

Data related to the mass import of these tables is available via ‘IMPORT’ Webservice.

Campaign : e-mail, SMS

A campaign is a communication, customized or not, sent to a selection of profiles.

There are two types of campaigns:

• Mass campaigns: the whole campaign is sent at once to the entire target
• Continuous campaigns: once activated, target profiles are contacted individually (for example via a scenario).

The definition, launch, activation and reporting of campaigns are available via the ‘MAIL’, ‘SMS’ and ‘PRINT’ web services.

Scenario

A scenario is a chain of actions to be applied to a profile.

The execution of a scenario can be triggered:

• by a business event (unsubscription, new order...)
• by a planified task (computation of profiles to submit to the scenario (e.g. anniversary, invitation...))
• by an external trigger (call via api or web service)

Scenario executions may be triggered via the ‘AUTOMATION’ web service.