Create a Rule to bulk load data

If you want more information on how to load Customer Attributes you will find out more here

If you’re using Customer Attributes or Personas, Alterian may have already set up data load or Autoloader rules for easy data ingestion. To load your data, simply send it to the Autoloader RESTful endpoint in clean JSON format.

If you’d like to simplify the process further, Alterian can create an SFTP site where you can drop your file. We’ll automatically pick up the file and process it through the required rule. For more details and any associated costs, please reach out to Alterian support.

Your use cases might involve bulk data loading for various purposes. You could enhance your rules by adding new data such as email addresses or phone numbers to expand your reach. Additionally, consider updating stock levels for products in your emails or incorporating “churn risk” data to tailor messages more effectively.

Creating a rule in template Builder for bulk data loading is straightforward

Create Endpoint

In Template Builder create a new transformation. Then add a Realtime Input step that will create the RESTful endpoint. Most Rules start with a Realtime Input.

In this example I’ll be loading attributes to enhance the contact information for existing users in my system. Specifically, I’ll update email, mobile number, and LinkedIn details, using the customer ID (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 records.

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. This allows then to flow along the rule as separate fields.

Matching the values in the data to existing users.

Lookup CXID

When using the Alterian CXID identifier as the key for users in your system, obtaining a CXID is essential for matching. However, if you’re not utilizing the CXID as the key, ensure that the relevant key (such as “Custid” or “CustomerNumber”) exists in the originating data. In cases where you’re loading stock information, the CXID is unnecessary since the data is not linked to an individual.

When bulk loading data select “optimise for bulk loading” and add your identification field. When this is selected the CXID Processor looks up the individual based on a single identification field and provides back the related CXID. It will do no merging and will not update last seen values for the individual. This step is used in the.

Using the Tracking field in the data we will lookup any linked CXIDs and pass them into the flow 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. In our example we will be using the CXID gathered in the previous step.

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

You can now publish this as a Rule and create the endpoint. You can now push data to the endpoint and it will load the records into your chosen table.

Loading a file (rather than one by one insertion)

Rather than loading the data one by one you may choose to pass in a file to be split by the rule.

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

In that example we need to use the split fields step.

In Review

This page should explain the processes required to create a rule that will load data into Journey Orchestration. You can now create rules that will pull the data back out again. In the examples provide above you should be able to obtain more email addresses for your abandon browse campaigns.

Product Documentation