A segregated account within your Intilery instance with nothing shared between accounts.
A brand is a way to differentiate different products or brands used by the same set of customers. If you don't have multiple products, when using the API your brand ID will be the same as your client ID but in all upper case.
You are the client. If you have multiple segregated groups of customers you will have multiple accounts.
When using the API your account ID will the same as your client ID if you only have one account.
The act of recording what your visitors and customers do on a tagged channel.
A message template to send to a customer through a channel. This will contain your merge tags to generate personalisation when the message is sent.
Reusable blocks of content that can be build for use in the asset editor.
An instance of an asset send to a customer through a channel. e.g. an email or SMS.
A row of columns in an asset
A rule to display or hide a row.
The status of an asset
A new asset or edit to an exiting asset starts in Draft status. Once the draft is ready, you can Request Approval
An asset with a change that is waiting to be reviewed and approved. A reviewer can add comments and chose to Reject, or can Approve the asset.
A change to an asset can be rejected with a comment, so the editor can fix and re-submit for approval.
You can choose to Archive a live asset.
If no version of an asset is live, then the asset cannot be sent.
A version of an asset that is no longer being sent.
The version number given to an asset. This will increment with each change to the asset.
List of email or SMS that can be applied to an asset to restrict who can be sent that asset.
A customer you cannot identify yet. Also known as a visitor.
A set of customers based on static (an upload) or dynamic (a query) rules.
Traits to apply to customers based on aggregation or calculations against events and properties that track customer behaviour for reuse in multiple audience definitions.
A single identifiable customer record.
Shown in the Intilery Platform Customer details page. This is your User ID passed in through the API.
Your unique identifier for a customer. This will not change over time.
Events and their properties that you send to Intilery.
The standard events and properties defined and tracked by Intilery.
The customer properties that are set using and identify event. These are facts that you pass to Intilery about the customer and are not expected to change frequently.
Synonym for an anonymous user.
Identification details for someone who have access to the platform.
Allows or denies access to a specific action in the platform.
A policy groups a set of permissions for use in creating roles, or escalating a user's access.
A user has a role which determines what access to the platform they have.
You can define and manage which users are in which roles.
There are two roles defined to start with, and Administrator for you and an Intilery Support role for our support team if they need to access your account. You cannot change the policies assigned to these default roles.
Any errors that have occurred are reported here. This will indicate reasons why e.g. an asset didn't send if the merge data didn't match what was set up.
Live view of the events as you send them to Intilery.
Configuration for calling out to other systems through an API (REST) call.
A set of automated activities that are triggered on the actions of a customer.
An instance of the journey as applied to an individual customer.
Where you can setup rules to block tracking for a User ID or carry out GDPR right to access/right to be forgotton requests.
Advanced campaign/journey reporting and dashboards
The Intilery Tag to add to your website.