Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Overview

  • Used to add data to an AWS queue

  • A prerequisite to using the plugin is that a queue is setup within AWS first

Plugin Configuration

Within the plugin:

The following settings can be configured:

Setting

Description

Selected queue

The AWS queue to add data to. To select the required queue:

1. Select Browse

2. Select the DDE client which the queue is associated to

3. Enter the access key and select OK

4. Select the queue you wish to add to and select OK:

Selected Queue Schema

Select a preconfigured schema where appropriate.

Write only If

Choose to skip passiugn information into the queue if the data has been flagged as Invalid

Bundle Messages

Bundle Messages togather to improve perfromance when using our non FIFO queues and ensure key events occur in the correct order. Please check with Alterian support before altering these values

Field Mapping

The queue columns that are required to be mapped to fields within the kettle stream:

Include data from cache

This allows you to automatically append data stored in a single table to the event being created. Alterian will use this to append your Persona and Customer Attribute values to the events created. See Cache configuration below and How Customer Attributes are added to events

So the expiry times ( TTLs) of the cache values are updated each read will also write to update the expiry time)

Cache Configuration

Here you can stipulate the Keyspace, Table and Key that should be looked up to append the data to the events. If the Journey Analytics has not been configured to accept the data selected it will fail so please talk to Alterian support if you would like this configured.

See this article on configuring the Customer Attribute Table addition to events.

How Customer Attributes are added to events

  • No labels