This Getting Started Guide covers the following topics:
- Introduction: Getting started with Connect
- Lesson 1: The CSV import path
- Lesson 2: The API integration path
- Lesson 3: Common use cases for Connect
When implementing the API calls from 2.3: Choosing a library, you will need to specify an environment key. All Connect accounts have two environments: Development and Production.
- Development is intended for all of your test users
- Production is used for all of your real users
For this step, we will be using the Development environment.
To locate your account’s environment keys
- In Connect, click the Settings icon (), then click Settings > Environments.
Once you add the identify calls to your code as well as some events, you can sign in to Connect and visit the Users tab to see the full timeline of your users. Try triggering some of the API calls from your test app, and the visit the development tab in the user search document:
If you click on a user’s profile, you can see their attributes on the right and side and the full history of api calls in the middle column:
If you don’t have a staging or development app, you can choose to initially test on their development environment by making API calls directly. For example, you can use a tool like Postman to make post calls directly to Connect development environment:
If you’re not seeing your test data appear in the development environment while testing, please contact firstname.lastname@example.org and we’re happy to help troubleshoot.