Create a Rule to bulk load data

If you are using Customer Attributes or Personas it’s likely that Alterian have already setup some data load or Autoloader rules to allow you to easily load in this data. You simply need to send the information through as to the Autoloader restful endpoint in clean JSON.

If you need Alterian to make this process even easier it is possible for Alterian to setup a SFTP site where you can simply drop your file.

We can then automatically pickup the file and feed it through the required Rule. Please contact Alterian support for more information on this process and any costs to setup.

Your use cases may require bulk data to be loaded for other purpuses.

This might involve, enhancing your rules with new data like email addresses or phone numbers to enable you ro contact more individuals.

You may want to update stock levels for the products in your emails to remove those no longer available or you may want to add “churn risk” data to an individual so you can better tailor the messages a user gets from your rules.

Creating a Rule to bulk load data is simple.

Create Endpoint

In Template Builder Create a Realtime Input step that contains that wil create the restful endpoint.

In this example I’m going to be loading attributes to improve the contact information I have on the users I have already have in my system. In this case email, mobilenumber and Linkedin will be loaded with custid as the key.

{
    "email": "developer@projectteam.com",
    "mobilenumber": "+81 90-1234-5678",
    "linkedin": "Project Team",
    "custid": "11223"
}

Remember you will get the best matches using an identifier that is high quality but commonly found in your users.

Next you will need to setup your JSON decoder to separate out the field.

Decode the Fields you Require

Use Get Fields to pull the fields from the test data into the JSON Decoder.

Lookup CXID

Where you are using the Alterian CXID identifier as a key for the users in your system you need to obtain a CXID. If you are not using the CXID as a key the key should obviously exist in the originating data i.e “Custid”, “CustomerNumber”

If this is the case you can skip this field. If you are loading stock information then CXID will not be required as the data is not linked to an individual.

When bulk loading data select “optimise for bulk loading” and add your identification field. when bulk loading we only lookup a single identifier. Using the Tracking field in the data we will lookup any linked CXIDs and pass them into the cflow of the rule. This can then be used as the key when loading the data.

Add Data to Cache / Journey Orchestration

Choose the Cache Table you want the data to be loaded into. Select your chosen key.

Get Fields will pull in the fields in the flow of the rule and all you to set them to be written.