Send query results to PowerReviews

PowerReviews is an ecosystem of consumers, advocates and influencers who create and curate authentic content to accelerate sales.

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

  1. Build a query

  2. Add orchestration

  3. Run orchestration


PowerReviews must be enabled before you can configure an orchestration to send query results. Ask your DataGrid Operator or Amperity representative to enable PowerReviews 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 PowerReviews. 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.


    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.


    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 PowerReviews

You can send reviews data to PowerReviews from a query that maps data in the customer 360 database to required and optional fields in the PowerReviews data schema, as described in the review import process .

A SQL query built using Presto SQL as a query can return results for use with PowerReviews. Add a SQL table with a SELECT statement similar to:

  amperity_id AS "User ID"
  reviews_id AS "Review Id"
  reviews_page_id AS "Page Id"
  reviews_display AS "Review Display"
  reviews_title AS "Review Title"
  reviews_datetime AS "Review Date"
  reviews_location AS "Review Location"
  reviews_text AS "Review Text"
  reviews_rating AS "Rating"
  reviews_source AS "Review Source"
  reviews_status AS "Review Status"
  email AS "User Email"
FROM customer360
LIMIT 2000


The fields in the example above represent custom fields in the customer 360 database that are built from data sources that contain reviews data for customers. This output must be mapped to the schema that is required by the PowerReviews review import process .

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 PowerReviews.

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

  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 PowerReviews 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”.