ProveSource is a social proof platform, that lets you show recent activities and reviews that happen on your website - signups, purchases, positive reviews and more, this helps build trust with your visitors and ultimately increases your conversions rates.
This is an Event Cloud Source which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.
This source is maintained by ProveSource. For any issues with the source, please reach out to their team.
NOTE: The ProveSource Source is currently in beta, which means that they are still actively developing the source. This doc was last updated on June 14, 2019. If you are interested in joining their beta program or have any feedback to help improve the ProveSource Source and its documentation, please let their team know!
- From your Segment UI’s Sources page click on “Add Source”.
- Search for “ProveSource” within the Sources Catalog and confirm by clicking “Connect”.
- Give the Source a nickname and follow the setup flow to “Add Source”. The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you’ll be querying against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
- Copy the Write key from the Segment UI and log in to your ProveSource account - navigate to Settings > Integrations > Click Edit next to Segment Integration and paste the key to connect.
Below is a table of events that ProveSource sends to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations. ProveSource will send through the
userId if available.
|Notification Viewed||A notification has been viewed|
|Notification Hovered||The user hovered his mouse over the notification|
|Notification Clicked||The user clicked the notification|
|Goal Completed||The user has completed a goal (e.g. signed up)|
Below are tables outlining the properties included in the events listed above.
||ID of the notification viewed/hovered/clicked|
||name of the notification viewed/hovered/clicked|
||ID of goal completed|
||name of the goal completed|
||Array of notification events related to Goal Complete|
||ID of the notification for which the event occurred before Goal Complete|
||true/false if the notification viewed|
||true/false if the notification hovered|
||true/false if the notification clicked|
Now that your Source is set up, you can connect it with Destinations.
Log into your downstream tools and check to see that your events are populating and they contains all the properties you expect. If all your events and properties are not showing up, refer to the Destination docs for troubleshooting.
If there are any issues with how the events are arriving to Segment, please contact the ProveSource team.
Questions? Problems? Need more info? Contact us, and we can help!