Send query results to Bazaarvoice¶
Bazaarvoice allows retailers to manage user-generated content on their website.
You can send data about brands, product categories, and products to support features that are powered by the product catalog in Bazaarvoice, such as:
Updating the product catalog
Supporting downstream syndication of user-generated content based on product matches
Identifying content for post-interaction email (PIE) messages
Integrating with other downstream workflows
This topic describes the steps that are required to send CSV, TSV, or PSV files to Bazaarvoice from Amperity:
Note
Bazaarvoice must be enabled before you can configure an orchestration to send query results.
Build query¶
You must build a query that shapes the data so that fields in the output are mapped to the fields required by Bazaarvoice. Data shaping is typically required only one time.
You can do this in the following ways:
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.
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.
Bazaarvoice and PII data¶
Bazaarvoice recommends to not include PII data.
Map to product catalog¶
A SQL query can return results for use with the product catalog in Bazaarvoice. Add a SQL table with a SELECT statement similar to:
SELECT
amperity_id AS ExternalId
,product_name AS Name
,product_description AS Description
,product_brand AS Brand
,product_id AS BrandExternalId
,product_category_name AS Category
,product_base_id AS CategoryExternalId
,product_url AS ProductUrl
,image_url AS ImageUrl
FROM customer360
LIMIT 2000
and then assign this query to a destination that sends results to Bazaarvoice.
Note
When building this query:
Do not include instances of a delimiter (commas, pipes, or tabs) within the field values, such as Name or Description.
Do not use double-quotes around field values.
Avoid including leading and trailing spaces in field values because they will be included with the value when stored in the Bazaarvoice database.
Refer to product catalog for additional details.
Important
Bazaarvoice requires the ExternalId, ProductUrl, and ImageURL fields to be in the results. The Brand, BrandExternalId, Category, and CategoryExternalId fields are recommended. Refer to the column definitions for complete details.
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.
Important
Sending data to Bazaarvoice should follow recommendations for the product catalog. Bazaarvoice supports the following file formats:
CSV
PSV
TSV
Use a single file for each product catalog to which Amperity will send data.
Enable the Include header row in output files option for the Amperity destination.
To add an orchestration
From the Destinations tab, click Add Orchestration. This opens the Add Orchestration dialog box.
From the Object Type drop-down, select Query.
From the Object drop-down, select the query for which results will be sent to Bazaarvoice.
From the Destination drop-down, select a destination that is configured for sending data to Bazaarvoice.
From the Data Template drop-down, select a data template.
Verify all settings.
Set the workflow to Manual. (You can change this to automatic later, after verifying the end-to-end workflow.)
Click Save.
Run orchestration¶
Run the orchestration manually to validate that it works.
To run the orchestration
From the Destinations tab, under Orchestrations, open the menu for the Bazaarvoice orchestration, and then select Run.
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.
When the orchestration has run successfully, the status is updated to “Completed”.