Kevel
Use GrowthLoop audiences for Kevel User Segments and optional UserDB membership.
Connect this destination to export audience membership as a Kevel User Segment, or to write membership through Kevel UserDB, for use in Kevel targeting rules and bid modifiers.
This destination writes to your Kevel account and is a good fit when you want to:
- Use a Kevel User Segment in targeting or bid modifiers
- Create or reuse a segment without delivering audience members
This maps to GrowthLoop Audiences:
| Use it for | Audiences |
|---|---|
| Creating or selecting a Kevel User Segment and optionally syncing membership | ✓ |
Prerequisites
Make sure you have:
- A Kevel account with a Management API key. See Kevel's API key documentation.
- Your Kevel network ID from the same account as the Management API key.
- For member exports, a dataset column containing the Kevel
userKeyfor each profile you want to synchronize.
Set up Kevel as a destination
- In GrowthLoop, click the Destinations tab on the left sidebar.
- Click New Destination in the upper right corner.
- Search for Kevel and click Add Kevel.
- Enter the required information, then click Create.
| Field | Description |
|---|---|
| Destination Name | Name this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Kevel Ads". |
| Sync Frequency | Set the default export frequency (for example, daily or weekly). You can override this setting for individual exports. |
| API key | Kevel Management API key. GrowthLoop sends it as the X-Adzerk-ApiKey header. |
| Network ID | Kevel network ID for UserDB membership. Use the network that belongs to the same account as the API key. |
GrowthLoop validates the API key against Kevel's Management API. Kevel then appears in your list of connected destinations.
WarningAPI key and Network ID must come from the same Kevel account. UserDB uses
network_idand is not checked against the Management API key. If they do not match, membership writes to the wrong network with no error.
Export to Kevel
From within GrowthLoop, export from an audience. See Export an audience if you need more information on these steps.
After building or selecting an audience, click Export, then search for Kevel.
Choose how members are sent
Under Export Inclusion Criteria, choose how GrowthLoop should handle audience members:
- Select a member-export option to synchronize audience membership through Kevel UserDB.
- Select No exports to create or reuse the Kevel segment, store its external ID, and deliver no audience-member data. This option does not require a match field and does not create a recurring member-export schedule.
Map identifiers
For member exports, map Kevel User Key to the dataset column that contains each profile's Kevel userKey.
No exports does not require a match field.
Resolve the User Segment
Under User Segment Status, choose how GrowthLoop should resolve the Kevel segment:
- New: GrowthLoop looks for a segment with the audience name. If it does not find one, GrowthLoop creates a segment using the Kevel Create Segment API. On later runs, GrowthLoop can rename a segment it created so the name stays in step with the GrowthLoop audience.
- Existing: Enter the existing Kevel Segment ID. GrowthLoop uses the selected segment as-is and does not rename or modify it.
Kevel networks support up to 1,000 segments. When your network has reached that limit, choose Existing and provide the ID of a segment you want to use. After the export is created, you can view the resulting Kevel Segment ID in the export's Manage modal in GrowthLoop.
Configure the export
| Setting | Member export | No exports |
|---|---|---|
| Export Name | Defaults to the audience name. | Defaults to the audience name. |
| Campaign type | Choose a one-time or ongoing export. | One-time segment setup. It does not recur for member delivery. |
| Schedule | Set frequency, start date, end date, and days of the week for ongoing exports. | Not used for member delivery. |
Export behavior
This is what GrowthLoop writes when you export an audience.
| Behavior | What happens |
|---|---|
| What GrowthLoop writes | A Kevel User Segment, and for member exports, UserDB membership. Direction is GrowthLoop → Kevel. |
| When it runs | GrowthLoop sends the export as a batch on the next successful run. An export that starts Now runs within about 15 minutes. No exports is a one-time segment setup. |
| New segment | GrowthLoop looks up a segment by audience name and creates one if it does not exist. Later runs can rename a GrowthLoop-created segment to match the audience name. |
| Existing segment | GrowthLoop uses the Segment ID you enter and does not rename or modify the segment. |
| Match field | Kevel User Key for member exports. The userKey is passed exactly as it appears in your dataset. Kevel does not normalize it. |
| Rows without a userKey | Skipped. |
| Member adds and removals | Member exports add profiles that enter the audience and remove profiles that leave the selected segment. |
| No exports | GrowthLoop does not send member data to Kevel UserDB. The export only creates or reuses the segment and stores its external ID. |
| userKey generation | GrowthLoop does not generate or discover Kevel userKey values. Your dataset must already contain the identifier used by your Kevel ad-serving or personalization workflow. |
| Deletes | GrowthLoop does not delete the Kevel segment if you delete the audience. |
Confirm the export was successful
When the run finishes, confirm you can use the data in Kevel.
- Audience export: Open User Segments and look up the segment associated with your GrowthLoop audience. Confirm that the segment ID matches the ID selected or created during export.
- Member export: Verify that a test profile's segment membership is present in Kevel UserDB.
- No exports: Confirm the User Segment exists. Do not expect audience members to appear in UserDB.
To use the segment for delivery decisions, configure it in the relevant Kevel targeting or bid-modifier rule after the export completes.
In GrowthLoop, review counts on the audience Exports tab. See Export an audience for more information.
Congrats on successfully exporting to Kevel!
Troubleshooting
These are the issues we see most often. You can always email us at [email protected] for help.
| Problem | Cause | Resolution |
|---|---|---|
| Connection fails to validate | The API key or network ID is wrong | Confirm the Management API key. Validation checks the API key, not that Network ID matches that account |
| Members appear on the wrong network | API key and Network ID are from different Kevel accounts | Use the Network ID that belongs to the same account as the API key |
| You cannot create a new segment | The network has reached the 1,000 segment limit | Choose Existing and enter the ID of a segment you want to reuse |
| Rows are skipped on a member export | The row has no userKey | Map Kevel User Key to a dataset column that already contains the Kevel identifier |
| No members appear in UserDB | The export used No exports | Use a member-export option if you need UserDB membership |
Updated 17 days ago
