Send data to PebblePost

PebblePost offers a full-stack solution that leverages scaled proprietary data, algorithmic optimization, advanced measurement and analytics, along with a print and mail logistics network.

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

  1. Get details

  2. Add destination

  3. Add data template

Get details

The PebblePost destination requires the following configuration details:

  1. The username.

  2. The passphrase.

  3. The remote folder to which Amperity will send data. For example: /incoming/customers or /incoming/transactions.

  4. The public key to use for PGP encryption, if required.

Add destination

Configure Amperity to send CSV files directly to PebblePost.

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: “PebblePost” and “This sends query results to “PebblePost”.

  3. From the Plugin drop-down, select PebblePost.

    This automatically selects pebblepost as the Credential Type and assigns sftp.pebblepost.com as the location to which data is sent.

  4. From the Credential drop-down, select Create a new credential. This opens the Create New Credential dialog box. Enter a name for the credential (typically “PebblePost”), and then enter the username and password required to access this SFTP location.

  5. Under Settings, enter the path to the remote folder.

    Tip

    For remote folders that contain spaces, use a backslash (\) character to escape the space. For example, a folder named “From ACME” should be entered as “FromACME”.

  6. From the File Format drop-down, select CSV.

  7. Add a single character to be used as an escape character in the output file. (This should match the escape character required by PebblePost.)

    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.

  8. Specify the encoding method. Encoding method options include “Tar”, “Tgz”, “Zip”, “GZip”, and “None”.

  9. Optional. Add the PGP public key that is used to encrypt files sent to PebblePost.

  10. Optional. Specify the line ending type: LF or CRLF.

  11. Optional. 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 “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. (A business user with limited PII access is someone who has been assigned the Restrict PII Access policy option.)

  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.

To add a data template

Step 1.

From the Destinations tab, open the menu for a destination that is configured for PebblePost, and then select Add data template.

This opens the Add Data Template dialog box.

Step 1

From the Destinations tab, open the menu for a destination that is configured for PebblePost, and then select Add data template.

This opens the Add Data Template dialog box.

Step 2.

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.

Step 2.

If business user access was not configured as part of the destination, you may configure access from the data template.

Important

To allow business users to use this destination with campaigns, you must enable the Make available to campaigns option. This allows users to send campaign results from Amperity to PebblePost.

If you enable this option, the data extension settings require using campaign name and group name template variables to associate the name of the data extension to your campaign.

Step 3.

Verify all configuration settings.

Verify settings for the data template.

Note

When the settings required by the SFTP site 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.

Step 4.

Review all settings, and then click Save.

Save the data template.

After you have saved the data template, and depending on how you configured it, business users can send query results to PebblePost and/or send campaign results to PebblePost to PebblePost.