| Info |
|---|
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 it’s likely that , Alterian may have already setup some set up data load or Autoloader rules to allow you to easily load in this data. You simply need to send the information through as for easy data ingestion. To load your data, simply send it to the Autoloader restful RESTful endpoint in clean JSON format.
If you need Alterian to make this process even easier it is possible for Alterian to setup a you’d like to simplify the process further, Alterian can create an SFTP site where you can simply drop your file. We can then automatically pickup We’ll automatically pick up the file and feed process it through the required Rule. Please contact Alterian support for more information on this process rule. For more details and any associated costs to setup, please reach out to Alterian support.
Your use cases may require might involve bulk data to be loaded for other purpuses. This might involve, enhancing your rules with new data like loading for various purposes. You could enhance your rules by adding new data such as email addresses or phone numbers to enable you ro contact more individuals.You may want to update expand your reach. Additionally, consider updating stock levels for the products in your emails to remove those no longer available or you may want to add or incorporating “churn risk” data to an individual so you can better tailor the messages a user gets from your rulesmessages more effectively.
Creating a Rule to bulk load data is simple. rule in template Builder for bulk data loading is straightforward
Create Endpoint
In Template Builder Create create a new transformation. Then add a Realtime Input step that contains that wil will create the restful RESTful endpoint. Most Rules start with a Realtime Input.
...
In this example I’m going to I’ll be loading attributes to improve enhance the contact information I have on the users I have already have for existing users in my system. In this case email, mobilenumber and Linkedin will be loaded with custid Specifically, I’ll update email, mobile number, and LinkedIn details, using the customer ID (custid) as the key.
| Code Block |
|---|
{
"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 “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
...
Where you are When using the Alterian CXID identifier as a the key for the users in your system you need to obtain , obtaining a CXID . If you are not using is essential for matching. However, if you’re not utilizing the CXID as a the key, ensure that the key should obviously exist relevant key (such as “Custid” or “CustomerNumber”) exists in the originating data i.e “Custid”, “CustomerNumber” If this is the case you can skip this field. If you are . In cases where you’re loading stock information then CXID will not be required as , 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 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.
...
Setting
...
Description
...
Key Space
...
Allows you to set the Cache Keyspace you want this step to run against.
...
Tracking Fields
...
Allows you to enter the tracking fields you want to use to identify the individual. See Identification mapping fields here to learn more
...
Optimise for Bulk Loading
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 “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.
| Code Block |
|---|
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.