Proof Experiences Destination

Proof Experiences helps B2B SaaS businesses increase new trials and demos by creating delightfully personalized experiences for their visitors and customers.

This destination is maintained by Proof. For any issues with the destination, please reach out to their team.

NOTE: Proof Experiences is currently in beta, which means that there may still be some bugs for us to iron out. This doc was last updated on February 21, 2019, and we’d love to hear your feedback. If you are interested in joining our beta program or have any feedback to help us improve the Proof Experiences Destination and its documentation, please let us know!

Getting Started

The first step is to make sure Proof Experiences supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

WebMobileServer
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Proof Experiences” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the “API Key” into your Segment Settings UI which you can find from your Proof Experiences dashboard.
  4. You should see data flowing into your Proof dashboard in the event debugger within 1 minute of creating your API key and activating your Proof Experiences integration.

Page

If you haven’t had a chance to review our spec, please take a look to understand what the Page method does. An example call would look like:

analytics.page()

Page calls will be sent to Proof Experiences as a pageview.

Identify

If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@segment.com',
  role: 'Software Engineer',
  company: 'Segment'
});

Identify calls will be sent to Proof Experiences as an identify call along with any included traits (optional).

Track

If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

analytics.track('Clicked Login Button', {
    btnText: 'Sign in here'
})

Track calls will be sent to Proof Experiences as a track call along with any included properties (optional).


Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

API Key

The keys to the kingdom, generally found under “settings” in the destination’s website.

Adding Proof Experiences to the integrations object

To add Proof Experiences to the integrations JSON object (for example, to filter data from a specific source), use one of the 2 valid names for this integration:
  • Proof
  • Proof Experiences


  • Questions? Need help? Contact us!
    Can we improve this doc?
    Email us: docs-feedback@segment.com!