Send data to Dynamic Yield

Dynamic Yield helps companies quickly build and test personalized, optimized, and synchronized digital customer experiences.

Note

This topic explains how to configure Amperity to send data to a password-protected Amazon S3 bucket that is managed by Dynamic Yield. You must configure Dynamic Yield to pull data from an an Amazon S3 bucket bucket that is managed from Dynamic Yield.

This topic describes the steps that are required to send CSV files to Dynamic Yield from Amperity:

1. Get details

2. Add destination

3. Add data template

Get details

Amperity can be configured to send data to a Dynamic Yield-managed Amazon S3 bucket.

Dynamic Yield requires the following configuration details:

1. The IAM access key.

2. The IAM secret key.

3. The Amazon Resource Name (ARN) for a role with cross-account access. (This is the recommended way to define access to customer-managed Amazon S3 buckets.)

4. The name of the Amazon S3 bucket to which Amperity will send data and its prefix.

5. The public key to use for PGP encryption.

Note

Amperity supports using cross-account role assumption with Amazon S3 buckets when Dynamic Yield supports the use of cross-account roles and your tenant uses the Amazon S3 destination.

Add destination

Configure Amperity to send CSV files directly to Dynamic Yield.

Important

Leave the S3 Prefix field empty.

To add a destination

1. From the Destinations tab, click Add Destination. This opens the Add Destination dialog box.

2. Enter the name of the destination and a description. For example: “Dynamic Yield” and “This sends query results to Dynamic Yield”.

3. From the Plugin drop-down, select Amazon S3.

4. The “iam-credential” credential type is selected automatically.

5. From the Credential drop-down, select a credential that has already been configured for this destination or click Create a new credential, which opens the Create New Credential dialog box. For new credentials, enter a name for the credential, the IAM access key, and the IAM secret key. Click Save.

6. Under Amazon S3 settings, add the name of the Amazon S3 bucket and the prefix. For example: “dynamic-yield” and “outbound/dynamicyield/”.

7. From the File Format drop-down, select Apache Parquet.

8. Add a single character to be used as an escape character in the output file.

   Note

   If an escape character is not specified and quote mode is set to “None” this may result in unescaped, unquoted files. When an escape character is not specified, you should select a non-“None” option from the Quote Mode setting.

9. Specify the encoding method. “None”.

10. Add the PGP public key that is used to encrypt files sent to Dynamic Yield.

11. Set the quote mode.

    Note

    If the quote mode is set to “None” and the Escape Character setting is empty this may result in unescaped, unquoted files. When quote mode is not set to “None”, you should specify an escape character.

12. Optional. Select Include success file upon completion to add a .DONE file to indicate when an orchestration has finished sending data.

    Tip

    If a downstream sensor is listening for files sent from Amperity, configure that sensor to listen for the presence of the .DONE file.

13. Optional. Select Include header row in output files if headers are included in the output.

14. Select Allow business users to use this destination.

    This allows users who have been assigned to the Amp360 User and/or AmpIQ User policies to use this destination with orchestrations and/or campaigns.

15. Select Allow business users with limited PII access to send data.

    This allows users who have been assigned to the Restrict PII Access policy option to use this destination with orchestrations and/or campaigns.

16. Click Save.

Add data template

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

Important

The name of the file must be “productfeed.csv”.

To add a data template

	From the Destinations tab, open the menu for a destination that is configured for Dynamic Yield, and then select Add data template. This opens the Add Data Template dialog box. From the Destinations tab, open the menu for a destination that is configured for Dynamic Yield, and then select Add data template. This opens the Add Data Template dialog box.
	Verify business user access to queries and orchestrations and access to segments and campaigns. A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data. If business user access was not configured as part of the destination, you may configure access from the data template.
	Verify all configuration settings. Note When the settings required by Dynamic Yield were are not configured as part of the destination, you must configure them as part of the data template before making this destination available to campaigns.
	Review all settings, and then click Save.