Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

ProveSource Source


Source Info
  • The ProveSource Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
  • This integration is partner owned. Please reach out to the partner's support for any issues.
(warning)

This Source is supported in US data processing regions.

This Source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.

ProveSource(link takes you to an external page) 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.

ProveSource maintains this source. For any issues with the source, contact the ProveSouce Support team.

(new)

ProveSource is in beta

This means the source is actively being developed, and some functionality may change before it becomes generally available.


Getting started

getting-started page anchor
  1. From your Segment UI's Sources page click on Add Source.
  2. Search for "ProveSource" within the Sources Catalog and confirm by clicking Connect.
  3. Give the Source a nickname and follow the set up 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 (for example, SourceName_Prod, SourceName_Staging, SourceName_Dev).
  4. Copy the Write key from the Segment UI and log in to your ProveSource account. Navigate to Settings(link takes you to an external page) > Integrations and click Edit next to the 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 ViewedA notification has been viewed
Notification HoveredThe user hovered their mouse over the notification
Notification ClickedThe user clicked the notification
Goal CompletedThe user has completed a goal (for example, signed up)

Below are tables outlining the properties included in the events listed above.

Property NameDescription
notificationIdID of the notification viewed/hovered/clicked
notificationNameName of the notification viewed/hovered/clicked
goalIdID of goal completed
goalNameName of the goal completed
eventsArray of notification events related to Goal Complete
events.notificationIdID of the notification for which the event occurred before Goal Complete
events.viewTrue/false if the notification was viewed
events.hoverTrue/false if the notification was hovered
events.clickTrue/false if the notification was 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 aren't showing up, refer to the Destination docs for troubleshooting.

If you experience any issues with how the events arrive in Segment, contact the ProveSource team.