Skip to main content
PUT
Update Data Point
Updates a Customer Value data point. Two things differ from most Everflow update endpoints:
  • The ID goes in the body, not the path. Send network_usm_data_point_id inside the JSON object; the path is the same /networks/usm/datapoints you POST to.
  • It is a full replace, not a merge. Any field you leave out is reset to its empty value — omit description and it becomes an empty string. Send the complete object every time.
Changing an identifier does not rewrite rule goals that reference the old value, so update those rules too.

Authorizations

X-Eflow-Api-Key
string
header
required

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

Body

application/json
network_usm_data_point_id
integer
required

The data point to update.

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

The updated data point.

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