Product Insights source FAQs

Updated 

2 days ago

Below are some of the frequently asked questions about the sources supported in Product Insights –

The review websites, news, blogs, owned accounts, and listening data from which we get client-specific data into Sprinklr to run AI models, are known as sources.

Data is sourced into Sprinklr via 3 different methods.

  • Review Page Sources

  • First Party Data Ingestion (FPDI) First Party Data Ingestion | Product Insights

  • Social Listening Mapping Listening Data to Products | Product Insights

  • Owned Accounts

Sprinklr currently supports 600+ sources for Product Insights. To get detailed knowledge, please check this KB article – Source Coverage | Product Insights.

The average latency varies anywhere between 0 to 72 hrs from the time the review is posted on native to it appearing in Sprinklr. To get the detailed knowledge, please check this KB article – Web Sources | Product Insights.

The data sourcing is dependent on various factors like permissions to source, limitations imposed on the website, availability of public data etc. Please refer to this KB article for more information – Source Coverage | Product Insights.

Any first party data like offline surveys, news, blogs, internal reports, etc. can be uploaded to the Sprinklr platform via First Party Data Ingestion (FPDI). The FPDI data can be linked to any product and an AI model will generate insights on the data.

Yes, custom sources (websites) can be added to Product Insights coverage as per the client requirement. Please contact the Success Team for any such requests.

  • Title

  • Review Message

  • Star Rating

  • Publish date

  • User Name

Product Insights provides additional information associated with reviews through meta-tags based filters. Below are the name/description of the standard fields exposed with the reviews.

S. No.

Field Name

Description

1

Is review syndicated

Identifier if a review is syndicated or not. This field is marked as True only for cases where a review is picked from another website. Cases where a review is posted for a different color/size variant of the same product is captured in Variant field.

2

Syndicated Website

Indicates from which website the review was picked up. This field can be used to get distribution of syndication by different domains.

3

Variant

Identifier if the review grabbed is for the same product or for a different variant (color/size) of the product

4

Does review recommend product

Identifier if the reviewer recommends the product

5

Is verified review

Identifier if the review is posted by a verified purchaser

6

Is partner review

Identifier if the review is marked as partner review – applicable for johnlewis.com only.

​

Definition: Tag for Reviews posted by Johnlewis partner who bought the products personally.

7

Purchase

Indicates purchasing time (only for bestbuy.com)

8

Is Neighbors program review

Identifier if the review is marked as neighbors program review (only for wayfair.com).

9

Is partner of competition

Identifier if the review is marked as partner of competition review (only for aeg.de).

10

Is prize draw participant

Identifier if the review is written by prize draw participants (only for bosch-home domains)

11

Is reviewer program review

Identifier if the review is written under reviewer program (only for homedepot.com).

12

Is reviewer seed member

Identifier if the review is written by a seed member (only for homedepot.com)

13

Is sponsored review

Identifier if the review is sponsored (only for aeg.de)

14

Is sweepstakes entry

Identifier if the review is marked as sweepstakes

15

Is Incentivized Review

Identifier if the review is marked as incentivized

16

Was product tried by reviewer

This reviewer was invited to try the product in exchange for their honest opinion (only for currys.co.uk)

17

Promotional Context

Marked as true if any of field #7 – #16 is marked as True or if review contains [This review was collected as part of a promotion]

No. There is no cost associated with adding a custom source.

The expected latency of review availability in Sprinklr varies from 0 to 72 Hrs after the review is natively posted on the website

Link for raising the domain addition request –

https://docs.google.com/forms/d/16sKHdW5yz-ChV8fQiVUNoFrhKMSFc1u0lQCVJ4P5Ees/edit#responses

Contact product team for further details.

7 to 10 working days, depending upon the number of the websites on which the search is performed.

It takes 5 to 7 working days for a new URL to be registered for reviews fetching after it is added on the product page.

4 to 5 weeks, from the day of submitting the source addition request.

Was this article helpful?

Related Articles

Loading...