Send results 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. Build a query

  2. Add orchestration

  3. Run orchestration

Note

PebblePost must be enabled before you can configure an orchestration to send query results. Ask your DataGrid Operator or Amperity representative to enable PebblePost for your tenant.

Build query

You may need to build a query that shapes the data so that fields in the output are mapped to the fields required by PebblePost. Data shaping is typically required only one time.

You can do this in the following ways:

  1. Add a SQL table (using Spark SQL) to the customer 360 database that selects PII fields from the Customer_360 table, and then outputs them to a table with columns that map to the required naming patterns.

    Note

    PII fields may require SHA-256 hashing or conversion to a UUID using the CAST() function.

  2. Add a SQL query (using Presto SQL) that filters within the query, and then outputs results that map to the required patterns.

    Note

    PII fields may require SHA-256 hashing or conversion to a UUID using the CAST() function.

The correct approach here depends on the data and the desired use case (or cases) for downstream workflows.

Map to customer data

A SQL query built using Presto SQL as a query can return results that map to customer data as required for use with direct mail campaigns managed from PebblePost. Be sure to verify all of the fields required by PebblePost and any field requirements for downstream workflows and use cases:

SELECT DISTINCT
  amperity_id AS ID
  ,given_name AS FIRST_NAME
  ,surname AS LAST_NAME
  ,address AS ADDR1
  ,address2 AS ADDR2
  ,city AS CITY
  ,state AS REGION
  ,postal AS POSTAL_CODE
  ,phone AS PHONE
  ,date_format(order_date, '%Y-%m-%d') AS LAST_PURCHASE_DATE
  ,CASE
    WHEN order_date < (current_date - interval '2' month) THEN 'True'
    ELSE NULL
    END AS RECENT_CUSTOMER
FROM Customer_360 c

WHERE c.email_work = false
AND c.amperity_id IS NOT NULL
AND given_name IS NOT NULL
AND last_name IS NOT NULL
AND street IS NOT NULL
AND postal IS NOT NULL
AND email IS NOT NULL
AND c.customer_status <> 'Loyalty'

Add orchestration

An orchestration defines the relationship between query results and a destination, including the location to which those query results will be sent and the frequency at which the orchestration will be run.

To add an orchestration

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

  2. From the Object Type drop-down, select Query.

  3. From the Object drop-down, select the query for which results will be sent to PebblePost.

  4. From the Destination drop-down, select a destination that is configured for sending data to PebblePost.

  5. From the Data Template drop-down, select a data template.

  6. Verify all settings.

  7. Set the workflow to Manual. (You can change this to automatic later, after verifying the end-to-end workflow.)

  8. Click Save.

Run orchestration

Run the orchestration manually to validate that it works.

To run the orchestration

  1. From the Destinations tab, under Orchestrations, open the    menu for the PebblePost orchestration, and then select Run.

  2. The Status column for the orchestration will update to say “Waiting to start…”, after which the notifications pane will update to include a notification that shows the current status.

  3. When the orchestration has run successfully, the status is updated to “Completed”.