Skip to main content
POST
Create Data Point
Creates a Customer Value data point. Customer Value was previously called User Management, which is where the usm in the path comes from. The identifier is the contract between your conversions and your rules: you send it with conversion data, and rule goals reference it through metric_data_point_identifier. It must be unique within the network — reusing one returns 400 Duplicate identifiers are not allowed. Pick type to match how you intend to compare the value. A number data point works with the greater_than and less_than goal operators; a text one works with exact_match, contains, begins_with and ends_with. Writing data points needs an API key with Offers → write access. Read-only keys and Reporting-only keys are rejected.

Authorizations

X-Eflow-Api-Key
string
header
required

The Everflow API key generated from the Control Center > Security.

Body

application/json
identifier
string
required

The key you send with conversions and reference from rule goals. Required, and unique within the network.

Maximum string length: 255
Example:

"ltv_90d"

name
string
required

The display name shown in the Everflow UI.

Maximum string length: 255
Example:

"90-Day LTV"

type
enum<string>
required

The value type. Use number for data points compared with greater_than or less_than, and text for those matched with exact_match, contains, begins_with or ends_with.

Available options:
text,
number
status
enum<string>
required

Whether the data point is collected and evaluated.

Available options:
active,
inactive
description
string

Optional free-text note about what the data point holds.

Maximum string length: 500

Response

identifier
string
required

The key you send with conversions and reference from rule goals. Required, and unique within the network.

Maximum string length: 255
Example:

"ltv_90d"

name
string
required

The display name shown in the Everflow UI.

Maximum string length: 255
Example:

"90-Day LTV"

type
enum<string>
required

The value type. Use number for data points compared with greater_than or less_than, and text for those matched with exact_match, contains, begins_with or ends_with.

Available options:
text,
number
status
enum<string>
required

Whether the data point is collected and evaluated.

Available options:
active,
inactive
network_usm_data_point_id
integer

Unique data point ID.

Example:

1

network_id
integer

Network ID.

Example:

1

description
string

Optional free-text note about what the data point holds.

Maximum string length: 500
time_created
integer

Unix timestamp of creation.

Example:

1788398582

time_saved
integer

Unix timestamp of last update.

Example:

1788398592