Kevel is excited to announce our new integration with Segment, one of the leading customer data platforms. Our new integration allows you to leverage the first-party customer data you have in Segment to create user-targeted ads within Kevel.
Customer data platforms (CDPs) are extremely powerful tools. They allow you to aggregate your customer data from multiple sources in a single place, and, in the case of Segment, they allow you to send that data into downstream tools.
This enables some interesting possibilities. You can do everything from send event data into AWS Kineses Firehose to create a data analytics warehouse for your customer data to enabling your support and customer acquisition teams with more detailed customer data in the tools that they're familiar with.
Segment also offers Personas, which allow you to use your data to build Computed Traits and Audiences.
With the Segment/Kevel partnership, you can now push these Segment Personas directly into Kevel's Data Management Platform (UserDB). This enables you to do user-level targeting, such as showing ads just to users tagged as a specific Persona.
From your Segment account, search for Kevel's Destination Integration and click "Configure Kevel".
Next, you'll need to configure your Segment Sources for the Kevel Destination. Once you select a Source, it's time to configure your credentials. You should see an interface similar to this:
To get your API Key, log in to the Kevel app and navigate to ""Settings" -> "API Keys"" via the top navigation. You'll see all your API Keys listed there.
You can find your Network ID using the ""Information"" bubble next to your username in the top right corner of the Kevel app.
After entering your credentials, configuration is done! The only thing left is to watch your first-party customer data flow into Kevel's UserDB.
You'll probably want to verify that the integration is working.
When user data is sent into Kevel's UserDB, we use Segment's "userId" as the UserDB "userKey". To test if this is working, first query UserDB via the API for a user's record:
If all is working, you should get back a UserDB record with any boolean Traits stored as Interests and everything else stored as Custom Properties:
Now that you've verified that data is successfully flowing into Kevel, you're ready to target users based on your data.
The following snippet will create a flight targeting the sample user from earlier:
You're now ready to request Decisions from Kevel with your custom user targeting. The only thing needed is to properly set the user key on the request:
That's it! If you are running into any issues, please reach out to support or contact your customer support manager.